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 85014 - gnome-settings-daemon crashes upon login
gnome-settings-daemon crashes upon login
Status: RESOLVED DUPLICATE of bug 85033
Product: gnome-control-center
Classification: Core
Component: [obsolete] settings-daemon
unspecified
Other other
: Normal normal
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2002-06-12 13:36 UTC by Colin Murtaugh
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Colin Murtaugh 2002-06-12 13:37:28 UTC
Package: control-center
Severity: normal
Version: 1.99.10
Synopsis: gnome-settings-daemon crashes upon login
Bugzilla-Product: control-center
Bugzilla-Component: settings-daemon
BugBuddy-GnomeVersion: 2.0 (2.0.1)

Description:
Description of Problem:
g-s-d crashes immediately after login

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

Actual Results:
g-s-d crashes	

Expected Results:
no crash

How often does this happen?
every time

Additional Information:




Debugging Information:

Backtrace was generated from '/usr/bin/gnome-settings-daemon'

[New Thread 1024 (LWP 31482)]
0x408fd319 in __wait4 () from /lib/libc.so.6

Thread 1 (Thread 1024 (LWP 31482))

  • #0 __wait4
    from /lib/libc.so.6
  • #1 __DTOR_END__
    from /lib/libc.so.6
  • #2 waitpid
    at wrapsyscall.c line 172
  • #3 libgnomeui_segv_handle
    at gnome-ui-init.c line 620
  • #4 pthread_sighandler
    at signals.c line 97
  • #5 <signal handler called>
  • #6 g_logv




------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-06-12 09:37 -------

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

Comment 1 Andrew Sobala 2002-06-12 16:41:25 UTC

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