error in gnome settings (gutsy)

Bug #130703 reported by Grzegorz Galezowski
4
Affects Status Importance Assigned to Milestone
gnome-control-center (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

When restarting Ubuntu few minutes ago after getting all updates, Gnome graphical template refused to load and there was an error message saying, that the last message was:

Failed to connect to socket /tmp/dbus-f5COmuDbyo: Connection refused.

I'm using Blubuntu Gnome theme.

Revision history for this message
Justin M. Wray (wray-justin) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" [WWW] http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems. [WWW] http://wiki.ubuntu.com/DebuggingProcedures

In addition, can you reproduce this bug? Or does it continually occur?

At a minimum, we need:
1. the specific steps or actions you took that caused you to encounter the problem,
2. the behavior you expected, and
3. the behavior you actually encountered (in as much detail as possible).
Thanks!

Changed in gnome-control-center:
assignee: nobody → wray-justin
status: New → Incomplete
Revision history for this message
Grzegorz Galezowski (spectral) wrote :

Hi, sorry if my info was too incomplete. Here's (I hope) more detailed description:

First of all, the bug occured once and does not reproduce.

When I turned up my computer (HP nx7400 EY 252EA model), Ubuntu booted as usual (newest rt kernel). I clicked on update manager icon and checked for updates. When the download was over (successfully), I chose to download all the updates that were available. Then I restarted my computer (standard way - by clicking on the icon places on upper panel and choosing "reboot").

The system booted up again. I chose once again rt kernel from GRUB list, then it came to black screen with ubuntu logo and orange indicator (I have all disk checking disabled, so there was no disk checking). After the indicator was filled, the bluebuntu blue login screen appeared. I clicked on login textfield, entered my login, pressed enter, entered my password and pressed enter again. The login screen dissapeared, and the screen filled with desktop colour appeared as usual. Then, before anyting else was visible, a message box appeared, saying, that (I don't remember the message clearly, sorry...) something wrong was with Gnome configuration and some settings were not loaded. Also, there was this message I wrote in the report, about socket. When i clicked on "close", Gnome loaded with it's default gray theme (not the Ubuntu or blubuntu one). Everything else seemed to be working allright. Then I opened firefox and reported it as a bug.

Revision history for this message
Grzegorz Galezowski (spectral) wrote :

It happened again, just when I got back from work and turned on my PC. I was using rt kernel and the rest went the same way. Here's the screenshot of what appeared visible after logging in.

Revision history for this message
Justin M. Wray (wray-justin) wrote :

Confirmed.

Thanks,
Justin M. Wray

Changed in gnome-control-center:
assignee: wray-justin → nobody
status: Incomplete → Confirmed
Revision history for this message
Grzegorz Galezowski (spectral) wrote :

Today I got all updates and now it happens to me time after time.

When I try to manually call gnome-settings-deamon, I get:

** (gnome-settings-daemon:5955): WARNING **: Unable to connect to dbus: Failed to connect to socket /tmp/dbus-plJpCl77pi: Connection refused

(gnome-settings-daemon:5955): GnomeKbdIndicator-WARNING **: Unable to connect to dbus: Failed to connect to socket /tmp/dbus-plJpCl77pi: Connection refused

(gnome-settings-daemon:5955): GnomeKbdIndicator-WARNING **: Not connected to dbus, will not register the object
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 727 error_code 2 request_code 147 minor_code 35)
  (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.)
[1190058191,000,xklavier.c:xkl_engine_start_listen/] The backend does not require manual layout management - but it is provided by the application

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

Thanks for your comments. This does not appear to be a bug report as such. We appreciate the difficulties you are facing, but it would make more sense to raise your question in the support tracker. http://launchpad.net/support

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

Other bug subscribers

Bug attachments

Remote bug watches

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