Comment 2 for bug 185157
Revision history for this message
| shanen (Shannon Jacobs) (shanen) wrote | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Here it is as text:
There was an error starting the GNOME Settings Daemon.
Some things, such as themes, sounds, or background settings may not work correctly.
The last error message was:
Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
GNOME will still try to restart the Settings Daemon next time you log in.
I've been seeing it pretty often recently, though I'm not sure when it started. I do see that there have been lots of reports of the problem, going back some months, but the ones I saw were all marked as invalid. Does that mean the Ubuntu people are going to document it as a feature soon? (Really, Gutsy has been a pretty major disappointment and I am unable to recommend the current Ubuntu to new users...)
I am not eager to become a programmer again--I would prefer that it simply work. However, I am willing to collect diagnostic data or even run a reasonable number of diagnostic tools if that will help you and the Ubuntu project. I would probably even be willing to join some kind of regression testing group if it would improve the future reliability of such computers as mine, but...
I currently don't have any solid or even fuzzy hypotheses about the problems that afflict this particular machine. I run Ubuntu on a number of IBM/Lenovo machines, and there are far fewer problems on that hardware. This machine is the only Sharp, and the only one with an AMD CPU. There are some input-related problems that seem to be related to the low level of the graphics stuff and that might be related to GNOME. There is a chronic startup problem (that I've reported separately a long time ago and never gotten any help with) that affects the network. This is a startup problem, too, but I don't see the connection. The most serious problem is the white screen of death, which is becoming increasingly common, but again I don't see any plausible connections to it. (Yes, I've reported that bug, too, and not even received anything I could recognize as a helpful diagnostic suggestion...)