You are not logged in.
Pages: 1
Apparently this error isn't common so I figure I better post about it here
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.
The last error message was:
System exception: IDL:Bonobo/GeneralError:1.0 : Child process did not give an error message, unknown failure occurred
GNOME will still try to restart the Settings Daemon next time you log in.I installed gnome simply using pacman -S gnome and started it up according the instructions in the wiki. I don't have any idea where to start.
Here is an error from when I run gnome-settings-daemon from the terminal:
[~]: sudo /opt/gnome/libexec/gnome-settings-daemon
The program 'gnome-settings-daemon' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadValue (integer parameter out of range for operation)'.
(Details: serial 1056 error_code 2 request_code 145 minor_code 29)
(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.)
[1158650197,000,xklavier.c:XklStartListen/] The backend does not require man[~]: ayout management - but it is provided by the application[Offline
I found people having similar problems caused by using evdev. Are you by coincidence also using evdev mouse driver ?
Offline
Ahh...yes, I have. That rings a bell, it's the xklavier thing isn't it? Let me search for that.
Offline
I believe this patch has been applied upstream, too bad it does not help for everyone.
Another patch is attached to this bug report, not sure if it is applied upstream already.
Another possible solution I came across
A quickfix for this bug is to make sure that you mouse button mapping is set to:
"pointer = 1 2 3 4 5 6 7 8 ...."
before launching gnome-settings-daemon.
Note the order '1,2,3' for the first three buttons, anything else seems to tick off gnome-settings-daemon.
You can do this with 'xmodmap -e "pointer = 1 2 3 ....(how many ever buttons your mouse has)" '
Once gnome-settings-daemon is launched you can remap your mouse buttons to your own mapping.
Well, that's all I could find with a quick google
Offline
Same error here. After the entering in the gdm username and password gnome takes forever to start. Finally it starts and it pops up the error message.
Is there a solution for that?
Powered by Arch Linux
Offline
Pages: 1