Activity log for bug #274747

Date Who What changed Old value New value Message
2008-09-26 11:40:59 ronny bug added bug
2008-09-26 12:13:08 Sebastien Bacher pygtk: status New Incomplete
2008-09-26 12:13:08 Sebastien Bacher pygtk: assignee desktop-bugs
2008-09-26 12:13:08 Sebastien Bacher pygtk: importance Undecided Low
2008-09-26 12:13:08 Sebastien Bacher pygtk: statusexplanation Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions: * Is this reproducible? * If so, what specific steps should we take to recreate this bug? This will help us to find and resolve the problem.
2008-09-28 01:46:41 ronny pygtk: bugtargetdisplayname pygtk (Ubuntu) pida (Ubuntu)
2008-09-28 01:46:41 ronny pygtk: bugtargetname pygtk (Ubuntu) pida (Ubuntu)
2008-09-28 01:46:41 ronny pygtk: statusexplanation Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions: * Is this reproducible? * If so, what specific steps should we take to recreate this bug? This will help us to find and resolve the problem. after some more analysis we came to the conclusion that the removal of the threads enter/leave pair is the best choice given pida's architecture we where unable to figure why the different gtk/pygtk versions act so different on that pair, but the removal of it fixes the issues due to pida's architecture it shouldn't yield any problems
2008-09-28 01:46:41 ronny pygtk: title Bug #274747 in pygtk (Ubuntu): "python-gtk gtk.gdk.threads_enter hangs" Bug #274747 in pida (Ubuntu): "python-gtk gtk.gdk.threads_enter hangs"
2008-09-28 18:11:27 ronny pida: status New Confirmed
2008-09-28 18:11:27 ronny pida: assignee ronny-pfannschmidt
2008-09-28 18:11:27 ronny pida: importance Undecided Critical
2008-09-28 18:11:27 ronny pida: statusexplanation
2008-09-28 20:46:38 ronny pida: status Confirmed Fix Committed
2008-11-05 13:14:59 Sebastien Bacher pida: assignee desktop-bugs
2008-11-05 13:14:59 Sebastien Bacher pida: statusexplanation after some more analysis we came to the conclusion that the removal of the threads enter/leave pair is the best choice given pida's architecture we where unable to figure why the different gtk/pygtk versions act so different on that pair, but the removal of it fixes the issues due to pida's architecture it shouldn't yield any problems
2008-11-16 10:33:48 Markus Korn bug added attachment 'test_gtk_threading.py' (test_gtk_threading.py)
2009-03-08 19:00:48 Ralph Corderoy pida: status Incomplete Confirmed
2009-03-08 19:00:48 Ralph Corderoy pida: statusexplanation Ubuntu 8.10, pida 0.5.1-5. On starting it you get the small gray window appear in the centre of the screen, but it stays empty; the "love" message doesn't appear. Nothing ever happens. Closing the window using the menu on the panel icon results in "it's not responding, force quit" which can kill it. strace suggests it's getting stuck on futex(2). I suspect a race condition as one of the attempts to start it, identical to all the others, succeeded. Note, a separate issue is choosing Emacs for the embedded editor without having Emacs installed. Then it just stops with "[Errno 2] No such file or directory" because a child process tried "execve("/usr/local/sbin/emacs", ["emacs", "--parent-id", "81789128", "-f", "server-start", "-l", "/home/peter/.pida2/pida_emacs_in"...], [/* 22 vars */]) = -1 ENOENT" for every directory in PATH.
2009-03-18 14:26:44 ronny pida: status Fix Committed Fix Released
2012-04-27 04:38:31 JC Hulce pida (Ubuntu): status Confirmed Incomplete