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 111427 - gnome settings daemon
gnome settings daemon
Status: RESOLVED DUPLICATE of bug 101939
Product: gnome-control-center
Classification: Core
Component: [obsolete] settings-daemon
2.0.x
Other other
: Normal normal
: ---
Assigned To: Scaffold Maintainers List
Scaffold Maintainers List
Depends on:
Blocks:
 
 
Reported: 2003-04-23 13:47 UTC by aernst
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description aernst 2003-04-23 13:47:52 UTC
From: Andreas Ernst <aernst1@bioc.unizh.ch>
To: submit@bugs.gnome.org
X-Mailer: bug-buddy 2.2.0
Subject:  gnome settings daemon

Package: anjuta2
Severity: normal
Version: 2.0.0
Synopsis:  gnome settings daemon
Bugzilla-Product: anjuta2
Bugzilla-Component: libanjuta
BugBuddy-GnomeVersion: 2.0 (2.0.3)

Description:
Description of Problem:
 gnome settings daemon crashed

Steps to reproduce the problem:
1. create new user with user ID 27001 in yast2 
2. login as new user
3. gnome settings daemon crashed

Actual Results:
can't use this account

Expected Results:


How often does this happen?
always

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 2144)]

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

Thread 1 (Thread 1024 (LWP 2144))

  • #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 2003-04-23 09:47 -------

The original reporter (aernst@access.unizh.ch) 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, anjuta2-maint@bugzilla.gnome.org.

Comment 1 Elijah Newren 2003-04-23 15:11:20 UTC
Please read the comments at the end of bug 101939.  If that doesn't
help you fix this problem (i.e. you somehow ended up with the same
stack trace but it occurred for a slightly different reason), post a
comment here and we can reopen this bug.

*** This bug has been marked as a duplicate of 101939 ***
Comment 2 aernst1 2003-04-23 17:00:10 UTC
I set in the /etc/sysconfig/gconf2 file option to "source" (default is
in Suse 8.1 "distribution") and delete all the directories produced by
gnome (e.g. .gnome/ .gnome2/ ...) in /home/<user_a>/.

Analog to the reported bug 101939 I changed the ownership of the
/tmp/orbit<user_a> to user_a. This didn't worked here. After I removed
the orbit<user_a> directory everything was fine. It was anyway
generated again after the next login (like the .gnome/,.gnome2/
directories in /home/user_a).
cheers