Bug#763625: keepnote fails with Attempt to unlock mutex that was not locked

2014-10-11 Thread Piotr Wnuczek
On Fri, 10 Oct 2014, Vlad Orlov wrote: Hi, Try this new debdiff (in the attachment) and see if it works for you. Hi, I have tested Your last fix. It works fine for me. Thank You. -- Regards -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of

Bug#763625: keepnote fails with Attempt to unlock mutex that was not locked

2014-10-11 Thread Marcel Mushik
Hey, I have to take back my previous email. Because of Piotr I had to recheck what I was checking before. (thanks). The new patch is working for me. I had two problems before that were tainting my testing environment. :) For some reason I had a binary in /usr/local/bin/keepnote and that was in

Bug#763625: keepnote fails with Attempt to unlock mutex that was not locked

2014-10-11 Thread Vlad Orlov
Hi, Glad to hear the new patch is working for you. It is not clear though whether the maintainer will apply it, because, as you can see, this bug report has been closed due to the arrival of the new version of GTK+2. This new version has a workaround for the mutex issue [1], which allows the

Bug#763625: keepnote fails with Attempt to unlock mutex that was not locked

2014-10-10 Thread Vlad Orlov
Hi, Ok, I've managed to reproduce it... to some extent. If I set it to load a notebook on app start (either Default Notebook or Open Last Notebook settings), it crashes with the same mutex-related error message. If I set it to open without any notebooks and then manually open a notebook via the

Bug#763625: keepnote fails with Attempt to unlock mutex that was not locked

2014-10-10 Thread Vlad Orlov
Hi, Try this new debdiff (in the attachment) and see if it works for you. keepnote-new-debdiff Description: Binary data

Bug#763625: keepnote fails with Attempt to unlock mutex that was not locked

2014-10-08 Thread Vlad Orlov
Hi, Guys, thanks for spotting this. Indeed, I haven't tested keepnote with creating a new notebook (my bad). Unfortunately, as I've tried to dig deeper into the issue, I found out that keepnote now simply segfaults on start: keepnote[3028]: segfault at 0 ip   (null) sp 7fff4794a738

Bug#763625: keepnote fails with Attempt to unlock mutex that was not locked

2014-10-08 Thread Vlad Orlov
Follow-up: Ok, I've found out that the segfaults were caused by GTK+3 hack [1] which I've been testing yesterday and haven't turned off afterwards. Now keepnote and other Python apps run fine, so I'll continue investigating the mutex issue. Don't ask me how a GTK+3 hack could possibly affect

Bug#763625: keepnote fails with Attempt to unlock mutex that was not locked

2014-10-07 Thread Piotr Wnuczek
Hello, I think there is a problem with keepnote configuration ($HOME/.config/keepnote/keepnote.xml). If I removed that file, keepnote started successfully. But when I have changed configuration settings (i.e. Edit- Preferences, option Default Notebook Use current notebook) and save it, next

Bug#763625: keepnote fails with Attempt to unlock mutex that was not locked

2014-10-06 Thread Piotr Wnuczek
On Sun, 5 Oct 2014, Vlad Orlov wrote: Hi, I have applied Your patch. Keepnote 0.7.8-1.2 builded successfully, but after package installation problem with starting application still exist. I'm using Debian Testing I've just tried it in another Debian Testing VM, and it worked for me. Note

Bug#763625: keepnote fails with Attempt to unlock mutex that was not locked

2014-10-05 Thread Vlad Orlov
Hi, I have applied Your patch. Keepnote 0.7.8-1.2 builded successfully, but after package installation problem with starting application still exist. I'm using Debian Testing I've just tried it in another Debian Testing VM, and it worked for me. Note that you don't need to use sudo for

Bug#763625: keepnote fails with Attempt to unlock mutex that was not locked

2014-10-05 Thread Kestutis Tamosiunas
Hello, Am I right to say that all the patch does is add two extra lines to /usr/lib/keepnote, so the file looks like this: # begin gtk event loop if need_gui: gtk.gdk.threads_enter() gtk.main() gtk.gdk.threads_leave() ??? if so, I had it done manual way, and it

Bug#763625: keepnote fails with Attempt to unlock mutex that was not locked

2014-10-04 Thread Piotr Wnuczek
Hello, I have applied Your patch. Keepnote 0.7.8-1.2 builded successfully, but after package installation problem with starting application still exist. I'm using Debian Testing Linux thinkdeb 3.16-2-amd64 #1 SMP Debian 3.16.3-2 (2014-09-20) x86_64 GNU/Linux

Bug#763625: keepnote fails with Attempt to unlock mutex that was not locked

2014-10-03 Thread Kestutis Tamosiunas
for those who cannot live without keepnote ,like myself, there is a way to run it in a meantime. I dont understand this debdiff thingy, sorry devs, so I downgraded following packages : gir1.2-glib-2.0_1.40.0-2_i386.deb libglib-perl_1.305-1+b1_i386.deb libglib2.0-data_2.40.0-4_all.deb

Bug#763625: keepnote fails with Attempt to unlock mutex that was not locked

2014-10-02 Thread Vlad Orlov
tags 763625 patch thanks Hi, The crash is due to some recent changes in GLib = 2.41 [1]. I'm attaching the debdiff with the patch for this bug. Hope to see it accepted ASAP. [1] https://bugzilla.gnome.org/show_bug.cgi?id=735428 keepnote-debdiff Description: Binary data

Bug#763625: keepnote fails with Attempt to unlock mutex that was not locked

2014-10-01 Thread Francesco Marchesi
Package: keepnote Version: 0.7.8-1.1 Severity: grave Starting keepnote from terminal, after a few lines in the output KeepNote 0.7.8: Wed Oct 1 15:37:43 2014 /usr/lib/python2.7/dist-packages/keepnote/gui/dialog_app_options.py:853: Warning: The property GtkDialog:has-separator is deprecated and