[Regression] gnome-settings-daemon fails to start on Gutsy RC

Bug #151937 reported by Stefan Güls
2
Affects Status Importance Assigned to Milestone
gnome-control-center (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gnome-control-center

Reopening https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/136320 and https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/138277

Doesn't work on Gutsy RC after fresh installation, *not* fixed

Revision history for this message
Stefan Güls (sguels) wrote :

i will provide additional information if needed and asked to do so

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem.

How do you know that the other bugs are duplicate, your description has no detail. Usually the new bug is marked duplicate of the old bug opened to not encourage opening duplicates and not the other way around

Changed in gnome-control-center:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Sebastien Bacher (seb128) wrote :

unduplicating the other bugs, there is no indication they are the same issue

Revision history for this message
Stefan Güls (sguels) wrote :

Ok, here's the error i get:

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.

Duplicating the bug was meant to help you to get a reference, as you wrote in https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/138277

> closing the bug, if somebody still get an issue you should open a new bug about it

So here it is. Backtrace will follow soon

Revision history for this message
Sebastien Bacher (seb128) wrote :

opening a new bug is alright, just don't mark old closed bug duplicates or mails will be sent to the people who opened those bugs which they might don't want

Revision history for this message
Stefan Güls (sguels) wrote :

Ok, i figured that one out:

i copied over some files (/etc/hosts) from my feisty install, ipv6 on lo interface was disabled.
A look at .xsession-erros was the hit with the cluebat i needed.

Marking invalid bug and moving to /dev/null

Changed in gnome-control-center:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.