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 125567 - gnome-panel crash
gnome-panel crash
Status: RESOLVED DUPLICATE of bug 111147
Product: gnome-panel
Classification: Other
Component: panel
unspecified
Other other
: Normal normal
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-10-27 01:27 UTC by Rick Berry
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Rick Berry 2003-10-27 01:27:33 UTC
Package: gnome-panel
Severity: normal
Version: 2.2.0.1
Synopsis: gnome-panel crash
Bugzilla-Product: gnome-panel
Bugzilla-Component: Panel
BugBuddy-GnomeVersion: 2.0 (2.2.0.1)

Description:
Description of Problem:
When trying to login to Gnome I get an error box that says gnome-panel
has crashed due to a fatal error. (Segmentation fault)

Steps to reproduce the problem:
1. login to start gnome
2. 
3. 

Actual Results:
crash


Expected Results:


How often does this happen?
everytime

Additional Information:

Here is what the error box says:

Application "gnome-panel" (process 17406) has crashed due to a fatal
error.
(Segmentation fault)







Debugging Information:

Backtrace was generated from '/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)...
(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)...[New
Thread 16384 (LWP 17406)]

(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)...
0x40929567 in waitpid () from /lib/i686/libpthread.so.0

Thread 1 (Thread 16384 (LWP 17406))

  • #0 waitpid
    from /lib/i686/libpthread.so.0
  • #1 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 __pthread_sighandler
    from /lib/i686/libpthread.so.0
  • #3 <signal handler called>
  • #4 FAMClose
    from /usr/lib/libfam.so.0
  • #5 FAMMonitorDirectory
    from /usr/lib/libfam.so.0
  • #6 _init
    from /usr/lib/gnome-vfs-2.0/modules/libfile.so
  • #7 _gnome_vfs_monitor_do_add
    from /usr/lib/libgnomevfs-2.so.0
  • #8 gnome_vfs_monitor_add
    from /usr/lib/libgnomevfs-2.so.0
  • #9 _init
    from /usr/lib/gnome-vfs-2.0/modules/libvfolder-desktop-old.so
  • #10 _init
    from /usr/lib/gnome-vfs-2.0/modules/libvfolder-desktop-old.so
  • #11 _init
    from /usr/lib/gnome-vfs-2.0/modules/libvfolder-desktop-old.so
  • #12 _init
    from /usr/lib/gnome-vfs-2.0/modules/libvfolder-desktop-old.so
  • #13 _init
    from /usr/lib/gnome-vfs-2.0/modules/libvfolder-desktop-old.so
  • #14 gnome_vfs_get_file_info_uri_cancellable
    from /usr/lib/libgnomevfs-2.so.0
  • #15 gnome_vfs_get_file_info_uri
    from /usr/lib/libgnomevfs-2.so.0
  • #16 gnome_vfs_get_file_info
    from /usr/lib/libgnomevfs-2.so.0
  • #17 fr_read_dir
  • #18 init_menus
  • #19 session_load
  • #20 main
  • #21 __libc_start_main
    from /lib/i686/libc.so.6
  • #0 waitpid
    from /lib/i686/libpthread.so.0




------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-10-26 20:27 -------

Reassigning to the default owner of the component, gnome-panel-maint@bugzilla.gnome.org.

Comment 1 Vincent Untz 2003-10-28 16:57:36 UTC
Thanks for the bug report. This particular bug has already been
reported into our bug tracking system, but please feel free to report
any further bugs you find.

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