[opensuse] gnome-settings-daemon crashing
Hi, Everyone. Lately, when I've started OpenSuse (10.2), I'm getting an error that /opt/lib/control-center-2.0/gnome-settings-daemon crashed with error 127. I can boot into X, but things like my fonts are not what I want, and even though I can start gnome-settings-daemon manually, any changes that I make don't get saved. In addition, I can see that the correct fonts are already in Control Center, but they're ignored. Can anyone give me some guidance? Thanks! -- bhartman36@gmail.com http://brianswebpagehome.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Actually, that should be "status 127" instead of error 127. Any ideas?
On 9/22/07, Brian Hartman
Hi, Everyone.
Lately, when I've started OpenSuse (10.2), I'm getting an error that /opt/lib/control-center-2.0/gnome-settings-daemon crashed with error 127.
I can boot into X, but things like my fonts are not what I want, and even though I can start gnome-settings-daemon manually, any changes that I make don't get saved. In addition, I can see that the correct fonts are already in Control Center, but they're ignored.
Can anyone give me some guidance? Thanks!
-- bhartman36@gmail.com http://brianswebpagehome.com
-- bhartman36@gmail.com http://brianswebpagehome.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sun, 2007-09-23 at 10:40 -0400, Brian Hartman wrote:
Actually, that should be "status 127" instead of error 127. Any ideas?
On 9/22/07, Brian Hartman
wrote: Hi, Everyone.
Lately, when I've started OpenSuse (10.2), I'm getting an error that /opt/lib/control-center-2.0/gnome-settings-daemon crashed with error 127.
I can boot into X, but things like my fonts are not what I want, and even though I can start gnome-settings-daemon manually, any changes that I make don't get saved. In addition, I can see that the correct fonts are already in Control Center, but they're ignored.
Can anyone give me some guidance? Thanks!
you'd better file a bug into Bugzilla, with all relevant info, like
output on the terminal when starting g-s-d from the command line, a
backtrace of the crash, if possible and any other thing you might think
are important.
It's very hard to know what's going on with just that error message.
--
Rodrigo Moya
On Sun, 2007-09-23 at 10:40 -0400, Brian Hartman wrote:
Actually, that should be "status 127" instead of error 127. Any ideas?
On 9/22/07, Brian Hartman
wrote: Hi, Everyone.
Lately, when I've started OpenSuse (10.2), I'm getting an error that /opt/lib/control-center-2.0/gnome-settings-daemon crashed with error 127.
I can boot into X, but things like my fonts are not what I want, and even though I can start gnome-settings-daemon manually, any changes that I make don't get saved. In addition, I can see that the correct fonts are already in Control Center, but they're ignored.
Can anyone give me some guidance? Thanks!
Try running /opt/gnome/lib/control-center-2.0/gnome-settings-daemon on
the command line and see if it spits out any errors. If you're using
packman with gstreamer I believe that was causing some other people
errors.
-JP
--
JP Rosevear
On Tue, 2007-09-25 at 09:26 -0400, JP Rosevear wrote:
On Sun, 2007-09-23 at 10:40 -0400, Brian Hartman wrote:
Actually, that should be "status 127" instead of error 127. Any ideas?
On 9/22/07, Brian Hartman
wrote: Hi, Everyone.
Lately, when I've started OpenSuse (10.2), I'm getting an error that /opt/lib/control-center-2.0/gnome-settings-daemon crashed with error 127.
I can boot into X, but things like my fonts are not what I want, and even though I can start gnome-settings-daemon manually, any changes that I make don't get saved. In addition, I can see that the correct fonts are already in Control Center, but they're ignored.
Can anyone give me some guidance? Thanks!
Try running /opt/gnome/lib/control-center-2.0/gnome-settings-daemon on the command line and see if it spits out any errors. If you're using packman with gstreamer I believe that was causing some other people errors.
other people have reported reinstalling control-center2 package made the
problem go away. Not sure exactly what might be going on, so please get
any error messages spit to the console.
--
Rodrigo Moya
participants (3)
-
Brian Hartman
-
JP Rosevear
-
Rodrigo Moya