| View previous topic :: View next topic |
| Author |
Message |
edbch
n00b
Joined: 09 Feb 2008
Posts: 17
|
 Posted: Thu Mar 26, 2009 6:28 pm Post subject: gnome-settings-daemon failing to start |
 |
|
Hello everyone.
First of all, sorry my bad english.
I just installed gentoo on my pc from stage one and get this message when I login in gdm:
| Code: | There was an error starting the GNOME Settings Daemon.
Some things, such as themes, sounds, or background settings may not
work correctly.
The Settings Daemon restarted too many times.
GNOME will still try to restart the Settings Daemon next time you log in. |
Looking at google I found some information and possible causes, but I do not have enough information to isolate the problem.
I am using the latest stable version of gnome, in fact, of everything. Please feel welcome to ask any information.
Please help me.
Now thank you. |
|
| Back to top |
|
 |
Henry78
Apprentice
Joined: 12 Jul 2004
Posts: 186
Location: Austria
|
| Posted: Thu Mar 26, 2009 7:23 pm Post subject: |
|
|
What happens if you run
| Code: | | /usr/libexec/gnome-settings-daemon --debug |
Any useful output? |
|
| Back to top |
|
|
edbch
n00b
Joined: 09 Feb 2008
Posts: 17
|
| Posted: Thu Mar 26, 2009 8:42 pm Post subject: |
|
|
Hi Henry78,
Tanks for the reply;
I was testing the unstable version of gnome-settings-daemon, and now I am not able any more to return to stable version because of an error during compilation.
In this unstable version the error is repeated, with a small change in behavior, but the result is the same.
The output of the command suggested by you is:
| Code: | The program 'gnome-settings-daemon' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadClass, invalid event class'.
(Details: serial 198 error_code 182 request_code 147 minor_code 6)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.) |
I had seen this before, and it dont say much to me.
But, now the errors reported in the file .xsession-errors are different.
Here the contents of the file. Xsession-errors
| Code: | This probably reflects a bug in the program.
The error was 'BadClass, invalid event class'.
(Details: serial 201 error_code 182 request_code 147 minor_code 6)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
26/03/2009 17:11:07 Autoprobing TCP port
26/03/2009 17:11:07 Autoprobing selected port 5900
26/03/2009 17:11:07 Advertising authentication type: 'No Authentication' (1)
26/03/2009 17:11:07 Advertising security type: 'No Authentication' (1)
error: option -s not recognized
HP Linux Imaging and Printing System (ver. 2.8.6b)
System Tray Status Service ver. 0.1
Copyright (c) 2001-8 Hewlett-Packard Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.
Usage: hp-systray [OPTIONS]
[OPTIONS]
Force Qt3: --qt3 (default)
Force Qt4: --qt4
Startup even if no -x or --force-startup
hplip CUPS queues
are present:
Set the logging -l<level> or --logging=<level>
level:
<level>: none, info*, error, warn, debug (*default)
Run in debug mode: -g (same as option: -ldebug)
This help -h or --help
information:
error: option -s not recognized
** (gnome-settings-daemon:9891): WARNING **: Failed to acquire org.gnome.SettingsDaemon
** (gnome-settings-daemon:9891): WARNING **: Could not acquire name
error: option -s not recognized
HP Linux Imaging and Printing System (ver. 2.8.6b)
System Tray Status Service ver. 0.1
Copyright (c) 2001-8 Hewlett-Packard Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.
Usage: hp-systray [OPTIONS]
[OPTIONS]
Force Qt3: --qt3 (default)
Force Qt4: --qt4
Startup even if no -x or --force-startup
hplip CUPS queues
are present:
Set the logging -l<level> or --logging=<level>
level:
<level>: none, info*, error, warn, debug (*default)
Run in debug mode: -g (same as option: -ldebug)
This help -h or --help
information:
HP Linux Imaging and Printing System (ver. 2.8.6b)
System Tray Status Service ver. 0.1
Copyright (c) 2001-8 Hewlett-Packard Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.
Usage: hp-systray [OPTIONS]
[OPTIONS]
Force Qt3: --qt3 (default)
Force Qt4: --qt4
Startup even if no -x or --force-startup
hplip CUPS queues
are present:
Set the logging -l<level> or --logging=<level>
level:
<level>: none, info*, error, warn, debug (*default)
Run in debug mode: -g (same as option: -ldebug)
This help -h or --help
information:
Initializing nautilus-open-terminal extension
Failed to play sound: Sound disabled
The program 'gnome-settings-daemon' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadClass, invalid event class'.
(Details: serial 198 error_code 182 request_code 147 minor_code 6)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
Traceback (most recent call last):
File "/usr/bin/blueman-applet", line 38, in <module>
from blueman.main.applet.Transfer import Transfer
File "//usr/lib/python2.5/site-packages/blueman/main/applet/Transfer.py", line 21, in <module>
from blueman.main.Config import Config
File "//usr/lib/python2.5/site-packages/blueman/main/Config.py", line 22, in <module>
from blueman.Functions import dprint
File "//usr/lib/python2.5/site-packages/blueman/Functions.py", line 33, in <module>
from blueman.Lib import sn_launcher
File "//usr/lib/python2.5/site-packages/blueman/Lib.py", line 2, in <module>
from _blueman import *
ImportError: libbluetooth.so.3: cannot open shared object file: Arquivo ou diretório não encontrado
(gnome-panel:9870): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -23 and height 25
** (nm-applet:9905): CRITICAL **: nmu_security_serialize_wpa_psk: assertion `(key_mgt == IW_AUTH_KEY_MGMT_802_1X) || (key_mgt == IW_AUTH_KEY_MGMT_PSK)' failed
** (nm-applet:9905): WARNING **: <WARN> hal_net_physdev_cb(): dbus returned an error.
(org.freedesktop.Hal.NoSuchProperty) No property net.physical_device on device with id /org/freedesktop/Hal/devices/net_00_13_02_01_7f_77
** (nm-applet:9905): WARNING **: <WARN> hal_net_physdev_cb(): dbus returned an error.
(org.freedesktop.Hal.NoSuchProperty) No property net.physical_device on device with id /org/freedesktop/Hal/devices/net_00_16_36_1e_14_9a
** (nautilus:9871): WARNING **: Unable to add monitor: Não há suporte
The program 'gnome-settings-daemon' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadClass, invalid event class'.
(Details: serial 185 error_code 182 request_code 147 minor_code 6)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
The program 'gnome-settings-daemon' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadClass, invalid event class'.
(Details: serial 185 error_code 182 request_code 147 minor_code 6)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
(gnome-panel:9870): Gdk-WARNING **: gdk_xsettings_watch_cb(): Couldn't find window to unwatch
The program 'gnome-settings-daemon' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadClass, invalid event class'.
(Details: serial 185 error_code 182 request_code 147 minor_code 6)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
The program 'gnome-settings-daemon' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadClass, invalid event class'.
(Details: serial 185 error_code 182 request_code 147 minor_code 6)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
The program 'gnome-settings-daemon' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadClass, invalid event class'.
(Details: serial 185 error_code 182 request_code 147 minor_code 6)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
The program 'gnome-settings-daemon' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadClass, invalid event class'.
(Details: serial 185 error_code 182 request_code 147 minor_code 6)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
The program 'gnome-settings-daemon' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadClass, invalid event class'.
(Details: serial 185 error_code 182 request_code 147 minor_code 6)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
The program 'gnome-settings-daemon' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadClass, invalid event class'.
(Details: serial 185 error_code 182 request_code 147 minor_code 6)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
The program 'gnome-settings-daemon' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadClass, invalid event class'.
(Details: serial 185 error_code 182 request_code 147 minor_code 6)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
Não foi possível abrir o arquivo desktop /usr/share/applications/firefox.desktop para o lançador do painel: Arquivo ou diretório não encontrado
Não foi possível abrir o arquivo desktop /usr/share/applications/thunderbird.desktop para o lançador do painel: Arquivo ou diretório não encontrado
Não foi possível abrir o arquivo desktop /usr/share/applications/blueproximity.desktop para o lançador do painel: Arquivo ou diretório não encontrado
HP Linux Imaging and Printing System (ver. 2.8.6b)
System Tray Status Service ver. 0.1
Copyright (c) 2001-8 Hewlett-Packard Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.
|
Now I'm trying to follow the tracks of this file, but any help will be welcome. |
|
| Back to top |
|
|
Henry78
Apprentice
Joined: 12 Jul 2004
Posts: 186
Location: Austria
|
| Posted: Thu Mar 26, 2009 9:30 pm Post subject: |
|
|
| I'm not quite sure what version you are using. But did you try a 'emerge -uDNa world' and 'revdev-rebuild' after up/downgrade of gnome-settings-daemon? |
|
| Back to top |
|
|
fiolj
n00b
Joined: 17 Mar 2008
Posts: 45
Location: Bariloche, Argentina
|
| Posted: Fri Mar 27, 2009 12:32 pm Post subject: gnome_settings_daemon fails |
|
|
I don't know why but in one of my machines it worked when I deactivate the keyboard plugin for gnome_settings_daemon. You can try. Go to the configuration editor. | Code: | | apps -> gnome_settings_daemon -> plugins -> keyboard |
and uncheck the box that says
It worked in one of my machines though I don't know why. |
|
| Back to top |
|
|
Clad in Sky
l33t
Joined: 04 May 2007
Posts: 894
Location: Germany
|
| Posted: Fri Mar 27, 2009 2:50 pm Post subject: |
|
|
Well, probably if you ran
| Code: | | /usr/libexec/gnome-settings-daemon --debug --no-daemon --sync |
as is suggested by the output above:
The program 'gnome-settings-daemon' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadClass, invalid event class'.
(Details: serial 198 error_code 182 request_code 147 minor_code 6)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line ←
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
You'd get something more revealing.
In my case it revealed, that libxklavier got keyboard layout information that it didn't need. This caused an error.
So downgrading libxkbklavier to version 3.6 helps (because it accepts the settings the daemon is trying to send to it) or deactivating the keyboard plugin, becoause in both cases this little error cannot happen.
This is of course a silly reason for the gnome-settings-daemon to go sulking. But it is also not hard to fix, I guess, so either gnome-settings-daemon or libxklavier will be rewritten accordingly in th enear future.
_________________
Kali Ma
Now it's autumn of the aeons
Dance with your sword
Now it's time for the harvest |
|
| Back to top |
|
|
EvaSDK
Retired Dev
Joined: 12 Jul 2003
Posts: 171
Location: France, Paris
|
|
| Back to top |
|
|
edbch
n00b
Joined: 09 Feb 2008
Posts: 17
|
| Posted: Fri Mar 27, 2009 5:22 pm Post subject: |
|
|
Hello everyone,
Henry78, sorry by the delay in responding, but your last post led-me to the discovery a number of broken packages whose correction took the whole night until just now.
Now, again, I'm using the latest stable version of everything, and specifically, the gnome-settings-daemon is 2.24.1-r1.
Now the contents of the file. Xsession-errors is:
| Code: | /etc/X11/gdm/Xsession: Beginning session setup...
/etc/X11/gdm/Xsession: Setup done, will execute: /usr/bin/ssh-agent -- /usr/bin/seahorse-agent --execute gnome-session
SESSION_MANAGER=local/acer:/tmp/.ICE-unix/15425
** Message: another SSH agent is running at: /tmp/ssh-qDQmo15425/agent.15425
1238172096.406583 Session manager: disconnected...
1238172100.594174 Session manager: disconnected...
27/03/2009 13:41:42 Autoprobing TCP port
27/03/2009 13:41:42 Autoprobing selected port 5900
27/03/2009 13:41:42 Advertising authentication type: 'No Authentication' (1)
27/03/2009 13:41:42 Advertising security type: 'No Authentication' (1)
1238172103.304853 Session manager: disconnected...
1238172108.530377 Session manager: disconnected...
Initializing nautilus-open-terminal extension
** (nautilus:15492): WARNING **: Unable to add monitor: No suport
1238172114.977176 Session manager: disconnected...
** (nm-applet:15524): CRITICAL **: network_device_is_wired: assertion `dev != NULL' failed
** (nm-applet:15524): CRITICAL **: network_device_is_wireless: assertion `dev != NULL' failed
** (nm-applet:15524): CRITICAL **: nma_get_connected_icon: assertion `dev != NULL' failed
(nm-applet:15524): Gdk-WARNING **: gdk_xsettings_watch_cb(): Couldn't find window to unwatch
** (nm-applet:15524): WARNING **: <WARN> hal_net_physdev_cb(): dbus returned an error.
(org.freedesktop.Hal.NoSuchProperty) No property net.physical_device on device with id /org/freedesktop/Hal/devices/net_00_13_02_01_7f_77
** (nm-applet:15524): WARNING **: <WARN> hal_net_physdev_cb(): dbus returned an error.
(org.freedesktop.Hal.NoSuchProperty) No property net.physical_device on device with id /org/freedesktop/Hal/devices/net_00_16_36_1e_14_9a |
fiol, I did your suggestion but the problem persists. I agree that any option can be enabled by default. Occurred to me that perhaps some of the xorg.conf option, and the gnome-settings-daemon can not change it and die. I am wrong?
Clad in Sky, Thanks for responding. This message appears only when I was using the unstable version. Now, as you can see, it no longer appears.
EvaSDK the link that you posted seems broken. You could take a look?
Thanks to all. The error still appearing, but now I will not make any experience before exhaust this forum, so I await instructions. |
|
| Back to top |
|
|
edbch
n00b
Joined: 09 Feb 2008
Posts: 17
|
| Posted: Fri Mar 27, 2009 10:13 pm Post subject: |
|
|
News!!!
Began operating. I am not sure what actually worked, but my guess is that the suggestion of fiolj has worked.
Thank you all for your help. |
|
| Back to top |
|
|
bitozoid
n00b
Joined: 20 Apr 2008
Posts: 67
|
| Posted: Wed Apr 08, 2009 11:10 pm Post subject: |
|
|
I had a similar problem. As said before, the command:
| Code: | | /usr/libexec/gnome-settings-daemon --debug --no-daemon --sync |
helped me to find the problem. A library (gstffmpeg) needed to be rebuild. After rebuilding it, problem gone. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Desktop Environments
