Back In Time

Meaning of "Attempt to unlock mutex that was not locked"

Asked by Laryllian

Heyho,
I just tried to backup my stuff again, but for some reason bit now says "Nothing changed" and on the cli it says "Attempt to unlock mutex that was not locked". What does that mean?

Debian testing, bit 1.0.34, rsync 3.1.1

Thx
Ray

PS: Full output:

INFO: Lock
INFO: on process begins
INFO: [GnomePlugin.Systray.run]
INFO: [GnomePlugin.Systray.run] begin loop
INFO: Profile_id: 1
Attempt to unlock mutex that was not locked
Aborted

Question information

Language:
English Edit question
Status:
Solved
For:
Back In Time Edit question
Assignee:
No assignee Edit question
Solved by:
Germar
Solved:
Last query:
Last reply:
Revision history for this message
Germar (germar) said : 		#1

I wasn't able to reproduce this on a fresh install of Jessie. Could you please post your ~/.config/backintime/config

Revision history for this message
Germar (germar) said : 		#2

Please try out this patch with 'sudo patch /usr/share/backintime/plugins/gnomeplugin.py < gnomeplugin.diff'

http://pastebin.ubuntu.com/8472032/

Revision history for this message
Laryllian (laryllian) said : 		#3

Nope, sorry. Still the same. I now tried with an empty disk with the same name: same result:

WARNING: import keyring failed

Back In Time
Version: 1.0.34

Back In Time comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions; type `backintime --license' for details.

INFO: Lock
INFO: on process begins
INFO: [GnomePlugin.Systray.run]
INFO: [GnomePlugin.Systray.run] begin loop
Attempt to unlock mutex that was not locked
Aborted

Thank you
Lary

Revision history for this message
vai cah (vaicah) said : 		#4

Looks like this problem https://bugzilla.gnome.org/show_bug.cgi?id=735428 .

Revision history for this message
Best Germar (germar) said : 		#5

Thanks vai cah! That's indeed the same problem.

I now was able to reproduce the problem on Debian unstable. Looks like libglib > 2.41 is responsible for this.

http://pastebin.ubuntu.com/8501101/
This patch should fix this for now. @Ray please remove the old patch before.

Revision history for this message
Laryllian (laryllian) said : 		#6

Wohoooo, the second patch really fixed it (I reverted the former one). Thank you so much. ;-D

Revision history for this message
Laryllian (laryllian) said : 		#7

Thanks Germar, that solved my question.

Revision history for this message
Nomer T Gomer (nomer) said : 		#8

I was also experiencing this issue and patch in response #5 resolved the issue.

Revision history for this message
Gabriel_P (gabp) said : 		#9

Confirmed. Back In Time 1.0.34 in elementary OS 0.3 (Freya), same bug, comment #5 was the solution.