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 133674 - frequent crashes after toying with the themes and look
frequent crashes after toying with the themes and look
Status: RESOLVED DUPLICATE of bug 136011
Product: gnome-panel
Classification: Other
Component: panel
2.4.x
Other Linux
: Normal normal
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks: 133684
 
 
Reported: 2004-02-06 19:34 UTC by Robert
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.0



Description Robert 2004-02-06 19:34:17 UTC
Description of Problem:


Steps to reproduce the problem:
1.trying different themes 
2.logout and login 
3.clicking the gnome menu makes it crash
4. trying to add another main menu makes it crash
all the time gnome can not be used anymore

Actual Results:
gnome-panel causes crashes and makes it impossible
to use gnome

Expected Results:
Gnome to work

How often does this happen? 
all the time even after reinstalling packages with yum

Additional Information:
causes other aplications like rhythmbox to crash
too so the can't be used in KDE
Comment 1 Vincent Untz 2004-02-06 19:47:28 UTC
Thanks for the bug report. Without a stack trace from the crash it's
very hard to determine what caused the crash. Please see
http://bugzilla.gnome.org/getting-traces.cgi for more information
about getting a useful stack trace.
Comment 2 Robert 2004-02-06 21:27:37 UTC
Starting program: /usr/bin/gnome-panel
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...[Thread
debugging using libthread_db enabled]
[New Thread -1085075328 (LWP 25443)]

(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread -1085075328 (LWP 25443)]
0x0019c043 in strlen () from /lib/tls/libc.so.6
(gdb) thread apply all bt

Thread 1 (Thread -1085075328 (LWP 25443))

  • #0 strlen
    from /lib/tls/libc.so.6
  • #1 FAMDebugLevel
    from /usr/lib/libfam.so.0
  • #2 FAMMonitorFile
    from /usr/lib/libfam.so.0
  • #3 ??
    from /usr/lib/gnome-vfs-2.0/modules/libfile.so
  • #4 ??

Comment 3 Vincent Untz 2004-03-07 14:13:46 UTC
Robert: does it still happen? If so, can you install the gnome-panel
debug package?
Comment 4 Robert 2004-03-11 06:24:18 UTC
Yes it still happens the gnome panel just crashes when I start it. Not
sure if some configuration file is the cause for this or some borged
theme. I'll see if I can install the required package and get it to work.

What information do you then require?
Comment 5 Vincent Untz 2004-03-11 09:31:42 UTC
It'd be great if you could install the package corresponding to your
version of gnome-panel:
http://download.fedora.redhat.com/pub/fedora/linux/core/updates/1/i386/debug/gnome-panel-debuginfo-2.4.2-3.i386.rpm
http://download.fedora.redhat.com/pub/fedora/linux/core/1/i386/debug/gnome-panel-debuginfo-2.4.0-3.i386.rpm

And then just copy and paste the stack trace you'll get in bug-buddy.
The new stack trace will be more useful.

Thanks
Comment 6 Robert 2004-03-11 16:51:47 UTC
Lets hope this helps! ;o)

Thread 1 (Thread -1084895104 (LWP 16207))

  • #0 _dl_sysinfo_int80
    from /lib/ld-linux.so.2
  • #1 __waitpid_nocancel
    from /lib/tls/libpthread.so.0
  • #2 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 strlen
    from /lib/tls/libc.so.6
  • #5 FAMDebugLevel
    from /usr/lib/libfam.so.0
  • #6 FAMMonitorFile
    from /usr/lib/libfam.so.0
  • #7 ??
    from /usr/lib/gnome-vfs-2.0/modules/libfile.so
  • #8 ??
  • #0 _dl_sysinfo_int80
    from /lib/ld-linux.so.2

Comment 7 Vincent Untz 2004-03-11 17:19:10 UTC
Hrm... Did you restart the panel?
Can you try renaming ~/.recently-used and see if it still happens?
Comment 8 Robert 2004-03-11 17:28:25 UTC
You've got to be kidding! I renamed ~/.recently-used and voila the
bloody thing works. Is this some known bug erm I mean feature? ;o)
Comment 9 Vincent Untz 2004-03-11 17:34:41 UTC
Known gnome-vfs bug. Fedora people need to upgrade to the latest
gnome-vfs 4.2.x
Comment 10 Vincent Untz 2004-03-11 17:35:39 UTC

*** This bug has been marked as a duplicate of 136011 ***