GNOME Bugzilla – Bug 67047
panel keeps crashing (panel Crash at 213.77.64.92)
Last modified: 2004-12-22 21:47:04 UTC
Package: panel Version: 1.4.0.4 Severity: >Synopsis: panel keeps crashing >Class: sw-bug System: current debian unstable >Description: Yesterday everything was OK, I have not installed any new software since then, so I do not suspect it is a problem of runnig unstable version of debian. I also don't think I changed anything in my panel, as this config is the one I used since few months. So after starting gnome the panel keeps crashing. If I run it from command line I get lots of messages: ** WARNING **: Unknown applet type! after removal of panel.d directory the panel starts well. >How-To-Repeat: I just run panel with my config. After submitting this bug I'll try to add gzipded version of my config files and strace result. If I coudn't do it for any reason - contact me directly so that I could send it to You. mailto:greg@sente.pl I don't want to loose all my panel config... If You could help at least with fixing my config files so that they work again... ------- Bug moved to this database by unknown@bugzilla.gnome.org 2001-12-16 08:55 ------- The original reporter (greg@sente.pl) of this bug does not have an account here. Reassigning to the exporter, unknown@bugzilla.gnome.org. Reassigning to the default owner of the component, panel-maint@bugzilla.gnome.org.
Created attachment 6229 [details] configuration which causes panel crash
Created attachment 6230 [details] ltrace while panel crashes
Created attachment 6231 [details] strace while panel crashes
What you must do is simply work trial and error through each of your panel config. Delete a section, and try again. If it doesn't work go back to the original and delete the next section. Post to this bug when you find the section causing the crash. A back trace is much more useful than a 10,000 line ltrace. Can you post one of these? Simply run X windows, and from a terminal run: gdb panel run <wait for crash> bt
Please try 1.4.0.5. just released.
here it comes: (no debugging symbols found)... Program received signal SIGSEGV, Segmentation fault. 0x0805d162 in gstc_parent_delete_watch () (gdb) bt
+ Trace 16501
it is still 1.4.0.4 will try 1.4.0.5 as soon as it comes into unstable
Crashes are critical by definition; not sure if this code has been reworked in 1.5.x or not.
Adding relevant keywords. You can filter on the phrase 'luis doing GNOME2 work' to catch all instances of this so that you can ignore them.
tried it for 1.4.0.5 (it came into unstable) the result looks similar - program finishes this way: ** WARNING **: Unknown applet type! ** WARNING **: Unknown applet type! .... ** WARNING **: Unknown applet type! (no debugging symbols found)... Program received signal SIGSEGV, Segmentation fault. 0x0805e572 in start_screen_check () (gdb) bt
+ Trace 16658
So it is still NOT fixed :-( HTH
it must be time to remove this easter egg.
Still not at all convinced it is actually the easter egg... marking this as a dup of the older bug. *** This bug has been marked as a duplicate of 53866 ***