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 121225 - various segementation faults when logging in to X window
various segementation faults when logging in to X window
Status: RESOLVED DUPLICATE of bug 109853
Product: gnome-panel
Classification: Other
Component: panel
unspecified
Other other
: Normal critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-09-01 23:30 UTC by dennis.lewis2
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description dennis.lewis2 2003-09-02 00:30:28 UTC
Package: gnome-panel
Severity: critical
Version: 2.2.1
Synopsis: various segementation faults when logging in to X window
Bugzilla-Product: gnome-panel
Bugzilla-Component: Panel
BugBuddy-GnomeVersion: 2.0 (2.2.0.1)

Description:
Description of Problem:
Getting several different critical segementation faults when running
startx with any other login but root. I can run startX using root.
Errors : gnome-settings-daemon Segmentation fault. Application
"gnome-panel"  has crashed due to Segmentation fault

Steps to reproduce the problem:
1. Logout user root
2. Login dennis 
3. startx

Actual Results:
Crash. If I keep trying I can get in but the desktop doesn't display and
gnome continues to give me segmetation errors on everything.

Expected Results:
Successful execution of startx 

How often does this happen?
every time I run startx with user "dennis" & not user "root"

Additional Information:




Debugging Information:

Backtrace was generated from '/usr/bin/nautilus'

(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)...[New Thread 1087955264 (LWP 5678)]
(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)...0xffffe002 in ?? ()

Thread 1 (Thread 1087955264 (LWP 5678))

  • #0 ??
  • #1 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 FAMClose
    from /usr/lib/libfam.so.0
  • #4 FAMMonitorDirectory
    from /usr/lib/libfam.so.0
  • #5 _init
    from /usr/lib/gnome-vfs-2.0/modules/libfile.so
  • #6 _gnome_vfs_monitor_do_add
    from /usr/lib/libgnomevfs-2.so.0
  • #7 gnome_vfs_monitor_add
    from /usr/lib/libgnomevfs-2.so.0
  • #8 nautilus_monitor_active
    from /usr/lib/libnautilus-private.so.2
  • #9 nautilus_monitor_directory
    from /usr/lib/libnautilus-private.so.2
  • #10 nautilus_monitor_active
    from /usr/lib/libnautilus-private.so.2
  • #11 nautilus_window_content_view_matches_iid
  • #12 nautilus_window_open_location
  • #13 nautilus_desktop_window_update_directory
  • #14 nautilus_desktop_window_new
  • #15 nautilus_application_startup
  • #16 Nautilus_Shell_start_desktop
  • #17 nautilus_application_startup
  • #18 main
  • #19 __libc_start_main
    from /lib/tls/libc.so.6
  • #0 ??




------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-09-01 20:30 -------

The original reporter (dennis.lewis2@comcast.net) 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, gnome-panel-maint@bugzilla.gnome.org.

Comment 1 Vincent Untz 2003-09-02 23:00:54 UTC
Please submit a stack trace for each crash. The stack trace you
provided is from a gnome-vfs bug which is already resolved.

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