← Back to team overview

touch-packages team mailing list archive

[Bug 1485913] [NEW] Attempt to unlock mutex that was not locked.

 

Public bug reported:

After successfully installed blueproximity, this package unable to
start.

lycanthropus:~$ blueproximity 
Using config file 'standard.conf'.
Attempt to unlock mutex that was not locked
Aborted (core dumped)

After searching everywhere, I have done following steps:

- installing libcanberra-gtk-module:i386
- installing libcanberra-gtk3-module
- editing /usr/share/blueproximity/proximity.glade 

but none are successful.

Any ideas? Thanks.

** Affects: blueproximity (Ubuntu)
     Importance: Undecided
         Status: New

** Package changed: upstart (Ubuntu) => blueproximity (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to upstart in Ubuntu.
https://bugs.launchpad.net/bugs/1485913

Title:
  Attempt to unlock mutex that was not locked.

Status in blueproximity package in Ubuntu:
  New

Bug description:
  After successfully installed blueproximity, this package unable to
  start.

  lycanthropus:~$ blueproximity 
  Using config file 'standard.conf'.
  Attempt to unlock mutex that was not locked
  Aborted (core dumped)

  After searching everywhere, I have done following steps:

  - installing libcanberra-gtk-module:i386
  - installing libcanberra-gtk3-module
  - editing /usr/share/blueproximity/proximity.glade 

  but none are successful.

  Any ideas? Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/blueproximity/+bug/1485913/+subscriptions