psensor does not start any more : Attempt to unlock mutex that was not locked
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
psensor (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
I am using Ubuntu 14.04 64 bits with all updates. Since 2 days, when I start psensor I get :
[2014-07-
(psensor:1279): GLib-GObject-
(psensor:1279): GLib-GObject-
Attempt to unlock mutex that was not locked
Abandon
Jean-Philippe Orsini (jfi) wrote : | #1 |
Declaix (jean-declaix) wrote : Re: [Bug 1346299] Re: psensor does not start any more : Attempt to unlock mutex that was not locked | #2 |
- image.png Edit (48.8 KiB, image/png; name="image.png")
- log Edit (939 bytes, application/octet-stream; name=log)
- gdb Edit (2.8 KiB, application/octet-stream; name=gdb)
Hi,
thanks for your fast answer.
I obviously ran with 14.04/Unity:
- ensure that all instances of psensor are stopped: killall -9 psensor
- remove the log file: rm $HOME/.psensor/log
- start psensor with full logging: psensor -d 3
- attach the log: $HOME/.psensor/log
[image: Images intégrées 1]
and I attach the file $HOME/.psensor.log
I ran as you requested:
- gdb psensor
- run
- wait until it crash
- bt
the result is in the attached file gdb
Thanks again and best regards
2014-07-22 9:22 GMT+02:00 Jean-Philippe Orsini <email address hidden>:
> Are you using the stock release of psensor or a release from a PPA?
> Could you please give the output of the 'apt-cache policy psensor'
> command?
>
> Do you reproduce systematically this issue?
>
> Could you please:
> - ensure that all instances of psensor are stopped: killall -9 psensor
> - remove the log file: rm $HOME/.psensor/log
> - start psensor with full logging: psensor -d 3
> - attach the log: $HOME/.psensor/log
>
> Which DE are you using? Unity? KDE?
>
> Could you please run psensor under gdb:
> - gdb psensor
> - run
> - wait until it crash
> - bt
>
> And send me the output.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> psensor does not start any more : Attempt to unlock mutex that was not
> locked
>
> Status in “psensor” package in Ubuntu:
> New
>
> Bug description:
> I am using Ubuntu 14.04 64 bits with all updates. Since 2 days, when I
> start psensor I get :
>
> [2014-07-
> NVIDIA.
>
> (psensor:1279): GLib-GObject-
> :use-stock is deprecated and shouldn't be used anymore. It will be
> removed in a future version.
>
> (psensor:1279): GLib-GObject-
> GtkSettings:
> will be removed in a future version.
> Attempt to unlock mutex that was not locked
> Abandon
>
> To manage notifications about this bug go to:
>
> https:/
>
Jean-Philippe Orsini (jfi) wrote : | #3 |
@Jean, thanks for the useful information.
You forget the output of "apt-cache policy psensor", I would like to know which version of psensor is concerned to try to spot the cause of your bug that I don't actually reproduce.
Declaix (jean-declaix) wrote : | #4 |
Sorry,
output of "apt-cache policy psensor":
maj@majquad:~$ apt-cache policy psensor
psensor:
Installé : 1.0.2-1ppatrusty1
Candidat : 1.0.2-1ppatrusty1
Table de version :
*** 1.0.2-1ppatrusty1 0
500 http://
trusty/main amd64 Packages
100 /var/lib/
0.
500 http://
Packages
maj@majquad:~$
Version:
maj@majquad:~$ psensor -v
psensor 1.0.2
Thanks again
2014-07-24 9:22 GMT+02:00 Jean-Philippe Orsini <email address hidden>:
> @Jean, thanks for the useful information.
>
> You forget the output of "apt-cache policy psensor", I would like to
> know which version of psensor is concerned to try to spot the cause of
> your bug that I don't actually reproduce.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> psensor does not start any more : Attempt to unlock mutex that was not
> locked
>
> Status in “psensor” package in Ubuntu:
> New
>
> Bug description:
> I am using Ubuntu 14.04 64 bits with all updates. Since 2 days, when I
> start psensor I get :
>
> [2014-07-
> NVIDIA.
>
> (psensor:1279): GLib-GObject-
> :use-stock is deprecated and shouldn't be used anymore. It will be
> removed in a future version.
>
> (psensor:1279): GLib-GObject-
> GtkSettings:
> will be removed in a future version.
> Attempt to unlock mutex that was not locked
> Abandon
>
> To manage notifications about this bug go to:
>
> https:/
>
Jean-Philippe Orsini (jfi) wrote : | #5 |
I have another report from somebody else (directly send to my email), so I turn it into 'confirmed'.
Are you using the trusty-proposed channel?
I am still interested by the gdb information if possible. Unlike previous instructions it might be more useful to use the gdb
command 'thread apply all bt' instead of just 'bt'.
Thanks for your help.
Changed in psensor (Ubuntu): | |
status: | New → Confirmed |
Jean-Philippe Orsini (jfi) wrote : | #6 |
Reporter appears to use a glib version from a ppa and not from ubuntu stock repositories.
The result of my investigation is that it is the consequence of a new check in the glib since 2.41.
It is caused by the use of the deprecated function gdk_threads_init which is only needed to workaround
a bug of appindicator < 0.2.9. The root cause is probably a bug in GTK itself as psensor does not directly
use any gdk_thread_
Fixed by http://
Jean-Philippe Orsini (jfi) wrote : | #7 |
The fix has been included in the v1.0.3 release. You can use the PPA: ppa:jfi/
Declaix (jean-declaix) wrote : | #8 |
Thanks a lot.
I sent you the gdb.
I made no modification concerning the trusty-proposed channel.
I will try to undestand what you need to-morrow (I am just coming back).
Best regards
2014-08-02 16:53 GMT+02:00 Jean-Philippe Orsini <email address hidden>
:
> I have another report from somebody else (directly send to my email), so
> I turn it into 'confirmed'.
>
> Are you using the trusty-proposed channel?
>
> I am still interested by the gdb information if possible. Unlike previous
> instructions it might be more useful to use the gdb
> command 'thread apply all bt' instead of just 'bt'.
>
> Thanks for your help.
>
> ** Changed in: psensor (Ubuntu)
> Status: New => Confirmed
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> psensor does not start any more : Attempt to unlock mutex that was not
> locked
>
> Status in “psensor” package in Ubuntu:
> Confirmed
>
> Bug description:
> I am using Ubuntu 14.04 64 bits with all updates. Since 2 days, when I
> start psensor I get :
>
> [2014-07-
> NVIDIA.
>
> (psensor:1279): GLib-GObject-
> :use-stock is deprecated and shouldn't be used anymore. It will be
> removed in a future version.
>
> (psensor:1279): GLib-GObject-
> GtkSettings:
> will be removed in a future version.
> Attempt to unlock mutex that was not locked
> Abandon
>
> To manage notifications about this bug go to:
>
> https:/
>
Declaix (jean-declaix) wrote : | #9 |
... I just launched psensor and it is working. I updated Ubuntu just before.
Best regards
2014-08-05 19:55 GMT+02:00 Jean-Philippe Orsini <email address hidden>
:
> The fix has been included in the v1.0.3 release. You can use the PPA:
> ppa:jfi/
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> psensor does not start any more : Attempt to unlock mutex that was not
> locked
>
> Status in “psensor” package in Ubuntu:
> Confirmed
>
> Bug description:
> I am using Ubuntu 14.04 64 bits with all updates. Since 2 days, when I
> start psensor I get :
>
> [2014-07-
> NVIDIA.
>
> (psensor:1279): GLib-GObject-
> :use-stock is deprecated and shouldn't be used anymore. It will be
> removed in a future version.
>
> (psensor:1279): GLib-GObject-
> GtkSettings:
> will be removed in a future version.
> Attempt to unlock mutex that was not locked
> Abandon
>
> To manage notifications about this bug go to:
>
> https:/
>
Jean-Philippe Orsini (jfi) wrote : | #10 |
The glib package causing this issue has reached the utopic repository which means that psensor is no more working on utopic now.
The very bad news is that I cannot branch the utopic version of psensor to submit the trivial fix. It appears to be due to http://
Jean-Philippe Orsini (jfi) wrote : | #11 |
- Fix #1346299 Edit (1.8 KiB, text/plain)
As I am unable to checkout the utopic branch of psensor, submit the fix as a debdiff.
Launchpad Janitor (janitor) wrote : | #12 |
This bug was fixed in the package psensor - 1.0.2-1ubuntu4
---------------
psensor (1.0.2-1ubuntu4) utopic; urgency=medium
* debian/
+ Fixed crash during startup. (LP: #1346299)
-- Jean-Philippe Orsini <email address hidden> Fri, 22 Aug 2014 10:45:25 +0200
Changed in psensor (Ubuntu): | |
status: | Confirmed → Fix Released |
Declaix (jean-declaix) wrote : | #13 |
... it was OK with recent Ubuntu updates, but since yesterday "no graphs
ebled..." (I am running version 1.1.1).
Best regards
2014-08-22 10:56 GMT+02:00 Jean-Philippe Orsini <email address hidden>
:
> As I am unable to checkout the utopic branch of psensor, submit the fix
> as a debdiff.
>
> ** Patch added: "Fix #1346299"
>
> https:/
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> psensor does not start any more : Attempt to unlock mutex that was not
> locked
>
> Status in “psensor” package in Ubuntu:
> Confirmed
>
> Bug description:
> I am using Ubuntu 14.04 64 bits with all updates. Since 2 days, when I
> start psensor I get :
>
> [2014-07-
> NVIDIA.
>
> (psensor:1279): GLib-GObject-
> :use-stock is deprecated and shouldn't be used anymore. It will be
> removed in a future version.
>
> (psensor:1279): GLib-GObject-
> GtkSettings:
> will be removed in a future version.
> Attempt to unlock mutex that was not locked
> Abandon
>
> To manage notifications about this bug go to:
>
> https:/
>
Jean-Philippe Orsini (jfi) wrote : | #14 |
v1.1.1 is using Gsettings instead of GConf2 (1.0.x) and the settings is not migrated so you have to redo the psensor setup. By default graph are not draw, you just have to click on the 'graph' toggle at the right of the sensor (main window).
v1.1.1 is not in the official repository and not concerned by this bug report, so I recommend to contact in another way (like send me an email to <email address hidden> or post to https:/
Declaix (jean-declaix) wrote : | #15 |
thanks
2014-09-04 20:19 GMT+02:00 Jean-Philippe Orsini <email address hidden>
:
> v1.1.1 is using Gsettings instead of GConf2 (1.0.x) and the settings is
> not migrated so you have to redo the psensor setup. By default graph are
> not draw, you just have to click on the 'graph' toggle at the right of
> the sensor (main window).
>
> v1.1.1 is not in the official repository and not concerned by this bug
> report, so I recommend to contact in another way (like send me an email
> to <email address hidden> or post to
> https:/
> if you have questions. It is better to keep this bug report "clean".
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https:/
>
> Title:
> psensor does not start any more : Attempt to unlock mutex that was not
> locked
>
> Status in “psensor” package in Ubuntu:
> Fix Released
>
> Bug description:
> I am using Ubuntu 14.04 64 bits with all updates. Since 2 days, when I
> start psensor I get :
>
> [2014-07-
> NVIDIA.
>
> (psensor:1279): GLib-GObject-
> :use-stock is deprecated and shouldn't be used anymore. It will be
> removed in a future version.
>
> (psensor:1279): GLib-GObject-
> GtkSettings:
> will be removed in a future version.
> Attempt to unlock mutex that was not locked
> Abandon
>
> To manage notifications about this bug go to:
>
> https:/
>
Are you using the stock release of psensor or a release from a PPA? Could you please give the output of the 'apt-cache policy psensor' command?
Do you reproduce systematically this issue?
Could you please:
- ensure that all instances of psensor are stopped: killall -9 psensor
- remove the log file: rm $HOME/.psensor/log
- start psensor with full logging: psensor -d 3
- attach the log: $HOME/.psensor/log
Which DE are you using? Unity? KDE?
Could you please run psensor under gdb:
- gdb psensor
- run
- wait until it crash
- bt
And send me the output.