Re: [Bug 1346299] Re: psensor does not start any more : Attempt to unlock mutex that was not locked

... 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 1346...@bugs.launchpad.net : As I am unable to checkout the utopic branch of psensor, submit the fix as a debdiff. **

[Bug 1346299] Re: psensor does not start any more : Attempt to unlock mutex that was not locked

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

Re: [Bug 1346299] Re: psensor does not start any more : Attempt to unlock mutex that was not locked

thanks 2014-09-04 20:19 GMT+02:00 Jean-Philippe Orsini 1346...@bugs.launchpad.net : 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

[Bug 1346299] Re: psensor does not start any more : Attempt to unlock mutex that was not locked

This bug was fixed in the package psensor - 1.0.2-1ubuntu4 --- psensor (1.0.2-1ubuntu4) utopic; urgency=medium * debian/patches/lp1346299.patch + Fixed crash during startup. (LP: #1346299) -- Jean-Philippe Orsini jea...@gmail.com Fri, 22 Aug 2014 10:45:25 +0200 ** Changed

[Bug 1346299] Re: psensor does not start any more : Attempt to unlock mutex that was not locked

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://package-

[Bug 1346299] Re: psensor does not start any more : Attempt to unlock mutex that was not locked

As I am unable to checkout the utopic branch of psensor, submit the fix as a debdiff. ** Patch added: Fix #1346299 https://bugs.launchpad.net/ubuntu/+source/psensor/+bug/1346299/+attachment/4184317/+files/lp1346299.patch -- You received this bug notification because you are a member of

Re: [Bug 1346299] Re: psensor does not start any more : Attempt to unlock mutex that was not locked

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 1346...@bugs.launchpad.net : I have another report from

Re: [Bug 1346299] Re: psensor does not start any more : Attempt to unlock mutex that was not locked

... 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 1346...@bugs.launchpad.net : The fix has been included in the v1.0.3 release. You can use the PPA: ppa:jfi/psensor-unstable to use it. -- You received

[Bug 1346299] Re: psensor does not start any more : Attempt to unlock mutex that was not locked

The fix has been included in the v1.0.3 release. You can use the PPA: ppa:jfi/psensor-unstable to use it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1346299 Title: psensor does not start any

[Bug 1346299] Re: psensor does not start any more : Attempt to unlock mutex that was not locked

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 1346299] Re: psensor does not start any more : Attempt to unlock mutex that was not locked

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

[Bug 1346299] Re: psensor does not start any more : Attempt to unlock mutex that was not locked

@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 a member of Ubuntu

Re: [Bug 1346299] Re: psensor does not start any more : Attempt to unlock mutex that was not locked

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://ppa.launchpad.net/jfi/psensor-unstable/ubuntu/ trusty/main amd64 Packages

Re: [Bug 1346299] Re: psensor does not start any more : Attempt to unlock mutex that was not locked

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

[Bug 1346299] Re: psensor does not start any more : Attempt to unlock mutex that was not locked

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