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 101939 - During login gnome-settings-daemon continues to crash
During login gnome-settings-daemon continues to crash
Status: RESOLVED NOTABUG
Product: gnome-control-center
Classification: Core
Component: general
2.0.x
Other Linux
: Normal normal
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Resolved
: 111427 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2002-12-25 13:24 UTC by Toni Schlichting
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Toni Schlichting 2002-12-25 11:20:57 UTC
Package: gnome-desktop
Severity: normal
Version: 2.0.0
Synopsis: During login gnome-settings-daemon continues to crash
Bugzilla-Product: gnome-desktop
Bugzilla-Component: general
BugBuddy-GnomeVersion: 2.0 (2.0.3)

Description:
Description of Problem:
During login gnome-settings-daeome continously pops up alert-boxes with
a text like this:

"The gnome-settings-daemon (process <pid>) has crashed due to a fatal
error"
At present I cant see the real message because the graphics on the
alert-box does not refresh so the left half remains grey after it has
been covered by this editor, into which I am right now entering this
text

Steps to reproduce the problem:
1. I have freshly installed SuSE Linux 8.1
2. created a user account "l1l8"
3. logged in as this user to get this problems

Actual Results:
A number of services does not work

Expected Results:
normal gnome desktop. I additionally must say, that I originally
expected a different lookalike but SuSE continues to misconfigure the
desktops since they prefer KDE.

How often does this happen?
allways

Additional Information:




Debugging Information:

Backtrace was generated from '/opt/gnome2/bin/gnome-settings-daemon'

(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 1024 (LWP 2472)]

(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)...
0x40a95449 in wait4 () from /lib/libc.so.6

Thread 1 (Thread 1024 (LWP 2472))

  • #0 wait4
    from /lib/libc.so.6
  • #1 __DTOR_END__
    from /lib/libc.so.6
  • #2 waitpid
    from /lib/libpthread.so.0
  • #3 libgnomeui_module_info_get
    from /opt/gnome2/lib/libgnomeui-2.so.0
  • #4 pthread_sighandler
    from /lib/libpthread.so.0
  • #5 <signal handler called>
  • #6 kill
    from /lib/libc.so.6
  • #7 pthread_kill
    from /lib/libpthread.so.0
  • #8 raise
    from /lib/libpthread.so.0
  • #9 abort
    from /lib/libc.so.6
  • #10 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #11 g_log
    from /usr/lib/libglib-2.0.so.0
  • #12 bonobo_activation_timeout_reg_check
    from /opt/gnome2/lib/libbonobo-activation.so.4
  • #13 g_timeout_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #14 g_main_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #15 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #16 g_main_context_iterate
    from /usr/lib/libglib-2.0.so.0
  • #17 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #18 bonobo_activation_server_by_forking
    from /opt/gnome2/lib/libbonobo-activation.so.4
  • #19 local_activator
    from /opt/gnome2/lib/libbonobo-activation.so.4
  • #20 bonobo_activation_activators_use
    from /opt/gnome2/lib/libbonobo-activation.so.4
  • #21 bonobo_activation_internal_service_get_extended
    from /opt/gnome2/lib/libbonobo-activation.so.4
  • #22 bonobo_activation_service_get
    from /opt/gnome2/lib/libbonobo-activation.so.4
  • #23 bonobo_activation_activation_context_get
    from /opt/gnome2/lib/libbonobo-activation.so.4
  • #24 ac_check
    from /opt/gnome2/lib/libbonobo-activation.so.4
  • #25 bonobo_activation_base_service_check
    from /opt/gnome2/lib/libbonobo-activation.so.4
  • #26 bonobo_activation_internal_service_get_extended
    from /opt/gnome2/lib/libbonobo-activation.so.4
  • #27 bonobo_activation_service_get
    from /opt/gnome2/lib/libbonobo-activation.so.4
  • #28 bonobo_activation_object_directory_get
    from /opt/gnome2/lib/libbonobo-activation.so.4
  • #29 bonobo_activation_active_server_register
    from /opt/gnome2/lib/libbonobo-activation.so.4
  • #30 main
  • #31 __libc_start_main
    from /lib/libc.so.6
  • #0 wait4
    from /lib/libc.so.6




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

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

Comment 1 Alex Duggan 2002-12-25 16:38:14 UTC
moving to control center and re-assigning
Comment 2 Alex Duggan 2002-12-25 16:38:45 UTC
What version of control-center are you using?
Comment 3 Toni Schlichting 2002-12-26 13:33:02 UTC
I finally found, that gnome seems to create directories in /tmp things
like "orbit-<user-name>" In this case there where two users, 'user_a'
and 'user_b'. In This case 'ls -l' showed something like this:

drwx------+   2 user_b   users         136 2002-12-26 11:11 orbit-user_a

So user_a did not own its orbit-directory. After changing the
ownership, it worked. I have no idea how this happened, since I did
not touch the files. I just found this by accident.

It happened on a freshly installed SuSE 8.1
Comment 4 Elijah Newren 2003-04-23 15:11:18 UTC
*** Bug 111427 has been marked as a duplicate of this bug. ***