After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 67047 - panel keeps crashing (panel Crash at 213.77.64.92)
panel keeps crashing (panel Crash at 213.77.64.92)
Status: RESOLVED DUPLICATE of bug 53866
Product: gnome-core
Classification: Deprecated
Component: panel
1.4.x
Other other
: Normal critical
: 1.4.1
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2001-12-16 13:55 UTC by Grzegorz Prokopski
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.0


Attachments
configuration which causes panel crash (14.02 KB, application/octet-stream)
2001-12-16 14:30 UTC, Grzegorz Prokopski
Details
ltrace while panel crashes (87.05 KB, application/octet-stream)
2001-12-16 14:33 UTC, Grzegorz Prokopski
Details
strace while panel crashes (34.26 KB, application/octet-stream)
2001-12-16 14:34 UTC, Grzegorz Prokopski
Details

Description Grzegorz Prokopski 2001-12-16 13:55:53 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.

Comment 1 Grzegorz Prokopski 2001-12-16 14:30:15 UTC
Created attachment 6229 [details]
configuration which causes panel crash
Comment 2 Grzegorz Prokopski 2001-12-16 14:33:44 UTC
Created attachment 6230 [details]
ltrace while panel crashes
Comment 3 Grzegorz Prokopski 2001-12-16 14:34:32 UTC
Created attachment 6231 [details]
strace while panel crashes
Comment 4 Wayne Schuller 2002-01-10 10:11:29 UTC
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
Comment 5 Kjartan Maraas 2002-01-20 16:17:45 UTC
Please try 1.4.0.5. just released.
Comment 6 Grzegorz Prokopski 2002-01-20 17:24:57 UTC
here it comes:

(no debugging symbols found)...
Program received signal SIGSEGV, Segmentation fault.
0x0805d162 in gstc_parent_delete_watch ()
(gdb) bt
  • #0 gstc_parent_delete_watch
  • #1 main
  • #2 __libc_start_main
    from /lib/libc.so.6

it is still 1.4.0.4
will try 1.4.0.5 as soon as it comes into unstable
Comment 7 Luis Villa 2002-01-22 20:09:15 UTC
Crashes are critical by definition; not sure if this code has been
reworked in 1.5.x or not.
Comment 8 Luis Villa 2002-01-22 21:24:08 UTC
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.
Comment 9 Grzegorz Prokopski 2002-01-23 16:35:26 UTC
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
  • #0 start_screen_check
  • #1 main
  • #2 __libc_start_main
    from /lib/libc.so.6

So it is still NOT fixed :-(

HTH
Comment 10 Wayne Schuller 2002-01-31 01:27:52 UTC
it must be time to remove this easter egg.
Comment 11 Luis Villa 2002-01-31 19:36:24 UTC
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 ***