Grey box and "error starting the GNOME Settings Daemon" on login.

Thanks for taking the time to report this bug and helping to make Ubuntu better. Could you please try to reproduce the bug without beryl enabled so we can properly classify the bug? Thanks in advance.

Hi Brian - the same problem is occuring without Beryl running.
It also seems to affect my computer more when I restard X server after booting, however it can also happen on boot - it seems a little random.

Like I said, I can't launch Users and Groups - I've also had trouble launching "Services".

i have the same white / grey box in the top left after loging in but my computer won't get past that part
P.S. i have gusty 7.10 amd64 on a Gateway mx3414 with a nvidia g-force go 6100

ok it went away for me when i installed gusty tribe 2

Hi, I am currently downloading Gutsy T2, but I am totally perplexed and taken aback, since Ubuntu Feisty Fawn used to wok well on my pc.

Now it wont even boot in live-cd mode.

Strange strange..
The cd is perfect and the machine seems okay. I have installed windows and the first tool installed after that was vmware. I tested my downloaded ISO and even stranger, ubuntu failed on vmware as well.

I am using an Acer TravelMate 2350 Laptop. I remember Ubuntu used to freeze when i swapped from LCD to CRT ( i couldnt find a prper answer for this bug, but I fear that this process has affected my hardware, more precisely an over-charge on my chipset.)

However windows runs perfectly well on the machine. All linux tested (kubuntu, ubuntu7.04, ubuntu 6.06, vector linux) failed.

Can the Ubuntu developers out there solve this problem? Polemical.

Shailen please submit a separate as your issue seems quite different bug report after testing with Tribe 3 which should come out this week and assign it to me.

cianclarke - are you still having this issue? Thanks in advance.

I've resolved this issue with a reinstall! No idea what caused it to be honest, but haven't come across it since thankfully.

This bug report is being closed due to your last comment regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the package name in the yellow line and then choosing a new status in the drop down box. You can learn more about bug statuses at http://wiki.ubuntu.com/BugSquad/ManagingStatus . Thanks again for taking the time to report this bug and helping to make Ubuntu better. Feel free to submit any future bugs you may find.

Hi, to everyone who have this problem, I would recommend to follow my steps (last resort, really). I am still unable to explain the reason why Feisty is working anew on my machine, but I will however relate the steps taken.

What you will need: Ubuntu Fesity, Ubuntu Gutsy Gibbon Tribe 2 (hope you have bandwidth to download it- or ask you friend; its free ), Microsoft Windows XP SP2.

Firstly, I have cleaned all partitions, and restored a fresh hard-drive with Ms Windows' Setup. I got the OS running and tested all hardware ( to ensure that there were no problems.)

I then tried Gutsy Gibbon T2. I removed the Windows installation, and instructed Gutsy to format everything and set itself up. That was done with no problems, but took some 2 or 3 hours around. ( Hail I still had some Linux inspiration to wait all that time...Read a book meanwhile.)
Please note that Gutsy Gibbon doesn't come with Live CD functions (at least I haven't seen any). So, install and get it running. After that has been done, you will have to remove Gutsy, because it is highly bugged and unstable.

Then run Feisty in Live CD mode. U should be in. Install and enjoy the ride.

In the limelight of the above short explanation, I think that Microsoft Windows' Setup Formatter did a great job to erase all partitions and clean any tables on my hard drive. (Probably what hindered Feisty's invasion).

Hope it worked for you.

It is an awkward work-around for the problem, i know, but I sincerely hope it would get your Linux back on track. Please follow up any unresolved issues.

Thanks.

And thank also to Brian Murray.

Shailen.

The problem has not been fixed! Don't close it! I'm getting the same problem with Gutsy T3, which I installed by dist-upgrade from Feisty. The problem surfaces rather randomly. Sometimes logging in again fixes it. Just now, I had to reboot because it simply wouldn't work. Running gnome-settings-daemon directly gives me error messages about being unable to connect to the DBus. There is a session dbus running so I don't get it...