GNOME Bugzilla – Bug 352970
Alacarte crashes when trying to go to a menu entry's properties
Last modified: 2006-10-22 14:28:28 UTC
Steps to reproduce: 1. Start Alacarte 2. Go into a folder 3. Right click an program's launcher 4. Click Properties Stack trace: Starting program: /usr/bin/python /usr/bin/alacarte (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 47321013009152 (LWP 6858)] (no debugging symbols found) <snip - repeated lots of times> GLib-GObject-CRITICAL **: g_signal_handler_block: assertion `handler_id > 0' failed aborting... Program received signal SIGABRT, Aborted. [Switching to Thread 47321013009152 (LWP 6858)] 0x00002b09c80bd535 in raise () from /lib/libc.so.6 (gdb) thread apply all bt
+ Trace 71030
Thread 1 (Thread 47321013009152 (LWP 6858))
Other information:
I am seeing the same issue with the CVS code as of 24-aug-06. When "properties" is selected for an item that is a member of a folder, alacarte crashes. Runing from a terminal window reveals a complaint about a missing attribute as shown below. -Joseph ========================= % alacarte Traceback (most recent call last):
+ Trace 71082
self.saveItem(self.item_original_values, True)
Traceback (most recent call last):
GLib-GObject-CRITICAL **: g_signal_handler_block: assertion `handler_id > 0' failed aborting...
Right, we have 5 days until Gnome 2.16. I reported this bug a week ago, it has been confirmed by somebody else. Are you just gonna sit by and release buggy software as "stable"? Not a good idea... I don't mean to be rude by the way, I just don't want Gnome 2.16 to be buggy
Alex, this is a Critical Warning crasher. These are enabled by default for the unstable GNOME branches, to easily spot those issues, and make GNOME even more stable. Note that these warnings generally do not result in a crash for *stable* GNOME releases. They may affect other code later, though, and therefore lead to crashes (that's why the yneed to be spotted and eliminated). While the developers and the entire GNOME user community does appreciate your caring about bugs and smoketesting, please keep in mind that developers usually are pretty busy folks, and there may be more urgent issues to fix. Anyway, thanks for smoketesting and caring about GNOME. :)
Also, if you want to check how the app behaves in a stable GNOME branch, you can change the G_DEBUG env var, which is set to fatal_criticals in unstable releases. You should be able to 'unset G_DEBUG' in your session script for the entire Desktop, or on a per app basis: $ G_DEBUG= application
Bah, sorry for bugging you then ><
No problem, Alex. You just showed that you are interested in GNOME and got some strong opinions about it. That's good. And yes, sometimes developers *need* some poking on their bugs. :)
Let's hope... I have the same issue here. I've dealt with this guy before and his answer to me was to switch distro's. Hopefully now that this is part of gnome he'll be much easier to work with..
Fixed in CVS. The fix will go into the next patch release. Thank you for your bug report. 2006-10-01 Travis Watkins <alleykat@gmail.com> * Alacarte/DialogHandler.py: fix crash bug with command entry
*** Bug 352882 has been marked as a duplicate of this bug. ***
*** Bug 364080 has been marked as a duplicate of this bug. ***