error starting GNOME Settings Daemon

[mattismyname]

Happened after last night's updates to Hardy.

** (gnome-settings-daemon:11172): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/media-keys for changes
** (gnome-settings-daemon:11172): DEBUG: GnomeSettingsModule 0x8080200 initialising
** (gnome-settings-daemon:11172): DEBUG: Loading /usr/lib/gnome-settings-daemon-2.0/libxrandr.so

** (gnome-settings-daemon:11173): WARNING **: Failed to acquire org.gnome.SettingsDaemon

** (gnome-settings-daemon:11173): WARNING **: Could not acquire name
** (gnome-settings-daemon:11173): DEBUG: SettingsDaemon finished
** (gnome-settings-daemon:11172): DEBUG: Registering GsdXrandrPlugin
** (gnome-settings-daemon:11172): DEBUG: Creating object of type GsdXrandrPlugin
** (gnome-settings-daemon:11172): DEBUG: GsdXrandrPlugin initializing
** (gnome-settings-daemon:11172): DEBUG: Activating xrandr plugin
** (gnome-settings-daemon:11172): DEBUG: Starting xrandr manager
The program 'gnome-settings-daemon' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadRequest (invalid request code or no such operation)'.
  (Details: serial 89 error_code 1 request_code 151 minor_code 6)
  (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.)
1205011405.201156 Session manager: disconnected...
** (gnome-settings-daemon:11184): DEBUG: Successfully connected to D-Bus
** (gnome-settings-daemon:11184): DEBUG: Starting settings manager
** (gnome-settings-daemon:11184): DEBUG: Loading settings plugins from dir: /usr/lib/gnome-settings-daemon-2.0/
** (gnome-settings-daemon:11184): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/xrdb.gnome-settings-plugin
** (gnome-settings-daemon:11184): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/xrdb for changes
** (gnome-settings-daemon:11184): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/screensaver.gnome-settings-plugin
** (gnome-settings-daemon:11184): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/screensaver for changes
** (gnome-settings-daemon:11184): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/xsettings.gnome-settings-plugin
** (gnome-settings-daemon:11184): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/xsettings for changes
** (gnome-settings-daemon:11184): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/background.gnome-settings-plugin
** (gnome-settings-daemon:11184): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/background for changes
** (gnome-settings-daemon:11184): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/keybindings.gnome-settings-plugin
** (gnome-settings-daemon:11184): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/keybindings for changes
** (gnome-settings-daemon:11184): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/keyboard.gnome-settings-plugin
** (gnome-settings-daemon:11184): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/keyboard for changes
** (gnome-settings-daemon:11184): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/typing-break.gnome-settings-plugin
** (gnome-settings-daemon:11184): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/typing-break for changes
** (gnome-settings-daemon:11184): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/font.gnome-settings-plugin
** (gnome-settings-daemon:11184): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/font for changes
** (gnome-settings-daemon:11184): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/a11y-keyboard.gnome-settings-plugin
** (gnome-settings-daemon:11184): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/a11y-keyboard for changes
** (gnome-settings-daemon:11184): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/clipboard.gnome-settings-plugin
** (gnome-settings-daemon:11184): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/clipboard for changes
** (gnome-settings-daemon:11184): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/dummy.gnome-settings-plugin
** (gnome-settings-daemon:11184): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/dummy for changes
** (gnome-settings-daemon:11184): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/mouse.gnome-settings-plugin
** (gnome-settings-daemon:11184): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/mouse for changes
** (gnome-settings-daemon:11184): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/sound.gnome-settings-plugin
** (gnome-settings-daemon:11184): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/sound for changes
** (gnome-settings-daemon:11184): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/xrandr.gnome-settings-plugin
** (gnome-settings-daemon:11184): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/xrandr for changes
** (gnome-settings-daemon:11184): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/media-keys.gnome-settings-plugin
** (gnome-settings-daemon:11184): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/media-keys for changes
** (gnome-settings-daemon:11184): DEBUG: GnomeSettingsModule 0x8080200 initialising
** (gnome-settings-daemon:11184): DEBUG: Loading /usr/lib/gnome-settings-daemon-2.0/libxrandr.so
** (gnome-settings-daemon:11184): DEBUG: Registering GsdXrandrPlugin
** (gnome-settings-daemon:11184): DEBUG: Creating object of type GsdXrandrPlugin
** (gnome-settings-daemon:11184): DEBUG: GsdXrandrPlugin initializing
** (gnome-settings-daemon:11184): DEBUG: Activating xrandr plugin
** (gnome-settings-daemon:11184): DEBUG: Starting xrandr manager
The program 'gnome-settings-daemon' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadRequest (invalid request code or no such operation)'.
  (Details: serial 89 error_code 1 request_code 151 minor_code 6)
  (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.)

[Update]
This was happening previously as bug 197153, which was believed fixed, but evidently not. -- bryce

[mattismyname (mattismyname)]

Also, as opposed to the other gsd bugs I could find, this one is repeatable, not random. It happens every time I try to run the program.

[mfsaadi (fahandezh)]

I have the same problem after updating the gnome-settings-daemon to the version 2.21.92-0ubuntu1.

[mfsaadi (fahandezh)]

it seems to be the same bug with xrandr which was fixed with the version 2.21.91-0ubuntu6 of gnome-settings-daemon this week.

[Alex Mayorga (alex-mayorga)]

Confirming this one. It in fact seems the same problem as earlier.

$ sudo gnome-settings-daemon >> manual-run.txt
[sudo] password for osito:
The program 'gnome-settings-daemon' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadRequest (invalid request code or no such operation)'.
  (Details: serial 89 error_code 1 request_code 151 minor_code 6)
  (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.)

[Alex Mayorga (alex-mayorga)]

I can confirm it using xorg-driver-fglrx

[Khashayar Naderehvandi (khashayar)]

Confirming, I see the same problem on a Lifebook P7010, 855GM (intel driver).

[elmarco (marcandre-lureau)]

I am also using xorg-driver-fglrx.

I reported a bug upstream and figured out this bug in launchpad just now.

The bug has been there for at least ~2/3 weeks.
http://bugzilla.gnome.org/show_bug.cgi?id=521371

[asdf (asdf123123-deactivatedaccount-deactivatedaccount)]

Using radeonhd, I get this.. not sure if it's the same bug

 sudo gnome-settings-daemon
** (gnome-settings-daemon:11797): DEBUG: Successfully connected to D-Bus
** (gnome-settings-daemon:11797): DEBUG: Starting settings manager
** (gnome-settings-daemon:11797): DEBUG: Loading settings plugins from dir: /usr/lib/gnome-settings-daemon-2.0/
** (gnome-settings-daemon:11797): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/xrdb.gnome-settings-plugin
** (gnome-settings-daemon:11797): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/xrdb for changes
** (gnome-settings-daemon:11797): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/keyboard.gnome-settings-plugin
** (gnome-settings-daemon:11797): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/keyboard for changes
** (gnome-settings-daemon:11797): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/a11y-keyboard.gnome-settings-plugin
** (gnome-settings-daemon:11797): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/a11y-keyboard for changes
** (gnome-settings-daemon:11797): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/sound.gnome-settings-plugin
** (gnome-settings-daemon:11797): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/sound for changes
** (gnome-settings-daemon:11797): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/keybindings.gnome-settings-plugin
** (gnome-settings-daemon:11797): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/keybindings for changes
** (gnome-settings-daemon:11797): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/background.gnome-settings-plugin
** (gnome-settings-daemon:11797): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/background for changes
** (gnome-settings-daemon:11797): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/dummy.gnome-settings-plugin
** (gnome-settings-daemon:11797): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/dummy for changes
** (gnome-settings-daemon:11797): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/xrandr.gnome-settings-plugin
** (gnome-settings-daemon:11797): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/xrandr for changes
** (gnome-settings-daemon:11797): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/clipboard.gnome-settings-plugin
** (gnome-settings-daemon:11797): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/clipboard for changes
** (gnome-settings-daemon:11797): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/xsettings.gnome-settings-plugin
** (gnome-settings-daemon:11797): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/xsettings for changes
** (gnome-settings-daemon:11797): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/mouse.gnome-settings-plugin
** (gnome-settings-daemon:11797): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/mouse for changes
** (gnome-settings-daemon:11797): DEBUG: Loading plugin: /usr/lib/gnome-settings-daemon-2.0/typing-break.gnome-settings-plugin
** (gnome-settings-daemon:11797): DEBUG: Monitoring dir /apps/gnome_settings_daemon/plugins/typing-break for changes
** (gnome-settings-daemon:...

[Tomasz Sterna (smoku)]

The bug is present in gnome-settings-daemon 2.21.92-0ubuntu1. I'm running nvidia-glx-new 169.12+2.6.24.10-12.30 and gnome-settings-daemon fails on xrandr plugin.

[Jared (jared-thanhandjared)]

Could this possibly be related to https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/198951

[Bryce Harrington (bryce)]

Also, on the off chance that it is an xserver issue, I've packaged some xrandr bug fixes from upstream.

Please install the three X server debs from this url which have been patched with the fixes, re-test, and let me know if it improves things:

  http://people.ubuntu.com/~bryce/Testing/XrandrGui/

If not, can someone experiencing this bug please run gnome-settings-daemon in gdb and get a 'backtrace full'? The error messages provided don't give enough info to go on.

[JD (jacobdorne)]

It's the same here. After first installing Ubuntu 8.04 Alpha6 and doing a complete upgrade and installing codecs etc I restarted and a message appeared that said could not start the gnome settings daemon.

I tried from a terminal and it returned this:

jacob@Jacobs-Laptop-L:~$ gnome-settings-daemon
Resource Timestamp: 37470
Resource Configuration Timestamp: 37470
CRTC 49 Timestamp: 37470
CRTC 4a Timestamp: 37470
Output 4b Timestamp: 37470
Segmentation fault (core dumped)
jacob@Jacobs-Laptop-L:~$

[Bryce Harrington (bryce)]

Jacob, please get a backtrace from the crash. See https://wiki.ubuntu.com/Backtrace and https://wiki.ubuntu.com/DebuggingProgramCrash for directions on how to do this.

[Khashayar Naderehvandi (khashayar)]

I'm trying to run this through gdb, but it seems there are no debugging symbols for gnome-settings-daemon, and I can't find any dbg package that goes with it.

I'll attach the output of gdb anyway, in case there might be something useful, but I doubt it.

[bart (bottenberg)]

I'm have the same error message in .xsession-errors when I try to run compiz-fussion. Running Gnome in 'safe mode' there is no problem.

[Bryce Harrington (bryce)]

Hi guys,

Well, perhaps we can try brute forcing it to stop crashing with a workaround. I've prepared a new version which lets us whitelist the drivers/devices this is allowed to run on. Namely, this limits it to not run on 855 or on drivers other than intel, ati, etc.

Could you please test this deb, and see if it eliminates the gnome-settings-daemon crash when the xrandr plugin is enabled?

 http://people.ubuntu.com/~bryce/Testing/XrandrGui/gnome-settings-daemon_2.21.92-0ubuntu2~bwh1_i386.deb

Note that this does NOT fix gnome-display-properties; it will still either crash, or fail to do anything when Apply is hit. However, if you guys find that this solves the crash in gnome-settings-daemon, I can apply a similar change to gnome-display-properties to make it use the old config tool instead (or at least pop up an error dialog).

Thanks. (Sorry I've been less responsive lately - I came down pretty ill yesterday and have been out of sorts.)

[Jared (jared-thanhandjared)]

This deb has fixed the gnome-settings-daemon crash on login.

However 2.22.0-0ubuntu1 has been released and the bug still exists.

[rbmorse (rbmorse)]

Bryce, the .deb prevents the gnome-settings-dameon crash with radeonhd.

What is the preferred option...downlevel gnome-settings-daemon or disabling xrandr plugin via gconf-editor and using the newer gnome-settings-daemon file? Operationally, it does not make much difference here.

[mattismyname (mattismyname)]

I think this should be a beta milestone blocking bug. Why isn't it?

https://launchpad.net/ubuntu/+milestone/ubuntu-8.04-beta

It's made my desktop pretty ugly and un-configurable for up to a week now. Surprising that more people aren't seeing this issue.

Thanks

[Jared (jared-thanhandjared)]

I concur with mattismyname. Users on (at least intel based laptops) will experience this bug AFAIK. It should be beta blocking unfortunately.

[Tomasz Sterna (smoku)]

I think the problem might be elsewhere that suggested before.

1. On the GDM login screen change your session type to "Failsafe terminal"
    (The one that launches only one, bare xterm window)
2. Log in.
3. In the xterm window type 'gnome-session' and press enter...
4. Voila... GNOME starts correctly, everything works fine. gnome-settings-dameon too.

So... The problem might actually be somewhere in the logon sequence.

[muzzamo (murray-waters)]

I'm getting this too. On 855 based laptop. Running from terminal also gives a
Segmentation fault (core dumped)
If there is any other info I can contribute let me know.

[muzzamo (murray-waters)]

Running gnome-session from failsafe terminal as per instructions from smoku does not work for me.

[Ryan Steele (rgsteele)]

I'm also seeing this error. I'm using the nvidia-glx-new driver. I've run gnome-settings-daemon with the --sync option under gdb as specified in the text of the error message and attached the backtrace.

I tried to install Bryce's .deb file but got an error since a newer version has been released.

[Bryce Harrington (bryce)]

cjwatson passed my patch on to seb128 for inclusion for -beta. seb128 decided to leave it unfixed for beta and prefers a different approach that doesn't involve Xorg.0.log parsing, so leaving to him to patch. The backtraces provided so far lack debugging symbols so are useless for troubleshooting the problem.

[mattismyname (mattismyname)]

Interesting finding: Doing a clean install of alpha6 resolved the issue for me.

[Ryan Steele (rgsteele)]

I've installed the debugging symbols for gnome-settings-daemon and taken another backtrace.

[David Gillies (daveg)]

Like Ryan Steele, I'm using nvidia-glx-new and am getting the same problem too.

[Zaki (asllaskdfjlalaksd)]

I can confirm the same thing happening on fglrx driver (ATI x1150). Video itself is also quite buggy, so first i thought it was a video driver issue, but people with other cards seem to experience the same thing. Before, gnome wouldn't even start, only in safe mode, where bug reporting wasn't working. Now at least I can start it normally, except settings-daemon.

Ryan, which package contains the debugging symbols for gnome-settings-daemon?

[Ryan Steele (rgsteele)]

Hi Zaki, you need to add the ddebs.ubuntu.com repositories. The instructions are here: https://wiki.ubuntu.com/DebuggingProgramCrash.

In reading https://wiki.ubuntu.com/Backtrace I noted that I neglected to do an "info registers". I've done one more backtrace following those instructions and attached it.

[Bryce Harrington (bryce)]

Unfortunately these backtraces are still incomplete (they show debug symbols for Xorg calls but not for gnome-settings-daemon or gnome-desktop), so it is hard to tell where the crash is starting. Please add "deb http://ddebs.ubuntu.com gutsy main universe" to your sources and install the packages libgtk2.0-0-dbgsym libgnome-desktop-2-dbgsym and gnome-settings-daemon-dbgsym.

[Bryce Harrington (bryce)]

mattismyname's issue was resolved by one of the earlier fixes, so everyone else commenting on this bug is likely having an unrelated issue.

For i855 and radeonhd users, I would suspect the fix to 198951 solves that issue.

For the failures with -nvidia and -fglrx, looking at the bug report pointed to in comment#7, the issue is that drivers lacked xrandr 1.2 support. The checks for this are in a gtk patch provided by upstream, that I passed along to seb128 and am attaching here for reference. I doublechecked the source and patches in gtk+2.0-2.12.9, and it appears it is missing these checks, which would explain why it is not handling these two drivers properly.

I've heard from a user of the most recent fglrx binary that they do not experience the crashes and that the screen resolution tool works properly; Zaki did not indicate what version of -fglrx he has installed, but if it's older than the most recent, upgrading it may help, but otherwise I think the attached gtk patch is necessary.

[Sebastien Bacher (seb128)]

libgnome-desktop doesn't use the gtk xrandr api and this patch should not make a difference. we need to make sure libgnome-desktop is testing correctly if the system supports xrandr 1.2, if the drivers are buggy and claim supporting it and don't then we need to trap the xerror and not crash

[Bryce Harrington (bryce)]

Here is a version of gnome-desktop that includes a trap for the X error. gnome-settings-daemon was patched earlier to check for xrandr version 1.2.

gnome-desktop already checks for if xrandr is available, but this was not being checked before calling configuration_apply_stored(), which could result in bug 197645. I've added an extra check in this case.

http://people.ubuntu.com/~bryce/Testing/XrandrGui/gnome-desktop-data_2.22.0-0ubuntu3_all.deb
http://people.ubuntu.com/~bryce/Testing/XrandrGui/libgnome-desktop-2_2.22.0-0ubuntu3_i386.deb

[muzzamo (murray-waters)]

As of the latest updates to hardy, the gnome desktop comes up properly (properly themed etc), but there is still a crash report in the tray related to gnome-settings-daemon.

[Zaki (asllaskdfjlalaksd)]

Hi, Bryce

I've updated today and noticed that gnome-desktop-data 2.22.0ubuntu2 was pushed with the updates.

I'm still experiencing the troubles though with the settings-daemon, but at least now i can start in normal mode (before it would crash the whole session and I could only start in reduced mode, in which backtracing was not working - it wouldn't crash)

Thanks to this update, I've done the backtrace and it seems that this is indeed connected to bug 179645, as I get the crash at rw_screen_list_outputs ().

The version of fglrx I'm using is 7.1.0-8-3+2.6.24.11-12.31 which is the latest according to launchpad.

As for gnome-desktop-data_2.22.0-0ubuntu3, it requires me to remove ubuntu-desktop along with a number of other packages like gnome-panel before installing, which makes gnome non-functional. libgnome-desktop seems to install, but the problem is still present.

Thanks for all the help this far.

[Tomasz Sterna (smoku)]

I have:
gnome-settings-daemon 2.22.0-0ubuntu1
nvidia-glx-new 169.12+2.6.24.11-12.31

I'm attaching output of
$ strace -s 1024 gnome-settings-daemon > gnome-settings-daemon.strace 2>&1

Maybe this would help in resolving the issue.

[elwinvdbeek (elwinvdbeek)]

Hi there, I am following this threat for a couple of days but the solution was not there for me. So it is time for a post ;-) This is how the problem did start for me i heave a Toshiba laptop with a Nvidia go force 420, normally compiz wont run. When enabling the xserver-xgl in the Synaptic package manager compiz works fine, unfortunately the gnome-settings-daemon crashes after rebooting gnome. Any ideas?

Sincerely,

Elwin

[jtuchscherer (jtuchscherer)]

Hi also had a problem with the gnome-setting-manager. For me it was related to a xserver problem. I found the solution to my problem in another bug report. Uninstalling xserver-xgl solved all my problems.
I have an ATI Moblity Radeon 9600. I am now even able to use desktop effects, even without xserver-xgl. I had xserver-xgl installed since dapper. this laptop was updated from breezy-dapper-edgy-feisty-gutsy-hardy. It is probably time for a clean install.
I hope this helps somebody.

[zmb (rpguy96)]

Just wanted to mention that jtuchscherer's solution (uninstall xserver-xgl) worked for me, too, with no apparent effect on my desktop settings (compiz settings, theme, background, etc).

[elwinvdbeek (elwinvdbeek)]

Hi,

When i did disable the xserver-xgl and did enable compiz it WORKS! ;-) unfortunately the bar to close or minimize windows is gone... any ideas?

Grt,

Elwin

[Jimi B (beawolfrocks)]

I tried uninstalling xserver-xgl and it worked a treat for me too. No problems now! :D

[Zaki (asllaskdfjlalaksd)]

Hi

jtuchscherer's solution works like a charm with ati x1150. Even compiz-fusion works properly, I am getting decent framerates too (before it would either crash or give unbearable fps). No crash with gnome-settings-daemon anymore and full 3D acceleration, this is a great day :)

Thank you so much,
Zaki

[Hans Deragon (deragon)]

Quoting http://freedesktop.org/wiki/Software/Xgl

"Xgl is an X server architecture layered on top of OpenGL. It is at an early stage in development and a number of important pieces are still missing. Xglx is the only server currently available that uses this architecture. It requires an already existing X server, and is only intended for testing and development."

Thus, probably an early erroneous meta-package got xserver-xgl installed? An new meta-package should be released to remove this server which seams to be causing problems to many and which is not ready for prime time use anyhow.

[akolahi (akolahi)]

Worked for me too w/ ATI

[Sebastien Bacher (seb128)]

xgl has never been installed by ubuntu, the users who installed it likely wanted to try compiz or something on their configuration which has no correct drivers and installed that buggy software

[Jason Sparshott (line-runner)]

Uninstalling xserver-xgl fixes the problem with Gnome-settings-daemon, but does not allow Compiz to run. I'm using a ATI Radeon Mobility x700, any ideas? Or is it just that my graphics card isn't powerful enough to run Compiz without xgl?

[lazerdye (haddock)]

I had this problem with an NVIDIA GForce 6200, and when I removed xserver-xgl I was not getting 3D effects. Then, I changed to this setting in xorg.conf:

    Option "Composite" "1"

and I was able to enable effects. So far so good!

[Jason Sparshott (line-runner)]

lazerdye, that worked for me also, thanks very much!

[Tomasz Sterna (smoku)]

Uninstalling xserver-xgl is not a solution.
Without Xgl server (running on nVidia drivers only) Compiz is unstable, Emerald leaks memory as hell - this renders Compiz desktop unusable.
You may search launchpad for related bugreports. This is related to buggy off-card texture storage. Nvidia drivers are broken and push testures to system memory, but never frees it back. The more on-card memory you have, the longer it takes this bug to hit you, but it will hit you. So, you cannot count on a stable system with nVidia texture-from-pixmap implementation + Compiz.

So far, the solution was to install xserver-xgl. This gives very fast and stable Compiz desktop.
With this regression, one cannot have stable Compiz desktop on nVidia cards.

You will have many complaints by Gutsy->Hardy adopters if you do not fix this.

So far the overral Hardy experience for me was a major upgrade from havily broken Gutsy and Feisty.
This regression makes Hardy yet another Ubuntu release that breaks things that worked fine before...

[Sebastien Bacher (seb128)]

such comments are not useful, xgl is not a supported ubuntu software and you don't need compiz to use your computer, patches are welcome though to fix the issue, if there is so many people relying on xgl somebody should be able to spend some efforts to try to get it working

[Hans Deragon (deragon)]

Sebastien, IIRC, I believe that Compiz is enabled by default since Gutsy. If Compiz is not stable in any scenario (with our without xserver-xgl), then Compiz should be disabled by default and big warning sign should show up whenever a user enables it, stating that Compiz is experimental. Hardy Herons is an LTS release and above all, it should be stable when installed with defaults. Should we change the title and description of this bug report to have Compiz disabled by default? At least for the video cards for which Compiz is known to be unstable?

BTW, I believe I inadvertently installed xserver-xgl, thus it probably does not show up in a fresh install. Currently, I have Compiz working without xserver-xgl on an Intel GM965/GL960 and seen no stability problems. But I have not played much with the test machine either. I believe that the problem reported might be only related to some video drivers, but I cannot confirm this.

[Owen Llywelyn (owen-llywelyn)]

Uninstalling xserver-xgl solved the problem for me - thanks to everyone here. Compiz working fine also. Tried to point users at the Ubuntu Forums who are having the same problem here.
( http://ubuntuforums.org/showthread.php?t=731312 )

[mattismyname (mattismyname)]

compiz works fine for me on older NV hardware as long as I make sure I DO
NOT install xgl per the instructions above.

[Sebastien Bacher (seb128)]

compiz is installed by default but should be used only on configurations where it's working correctly, there is a list of thing it's trying before running

[Bryce Harrington (bryce)]

@seb128, part of a patch that I sent you earlier included a test for Xgl which I knew would break in this case - you rejected the patch because part of it was parsing Xorg.0.log. However the portion that tests for Xgl is independent and seems still valid. While I agree that xgl is not supported and should be discouraged, it seems like it would risk little to just include a check for it, and terminate xrandr stuff gracefully if they had it installed.

Attached is a short example program to demo the code that would be employed. If you are willing to accept a patch, I can prepare one using this test for gnome-settings-daemon and gnome-control-center. It will also require adding a build-dep against libxv-dev.

Fwiw, I have seen numerous other reports in the past of people who had inadvertently installed xserver-xgl back in Feisty days, which sometimes caused massive performance issues after upgrading to Gutsy. I'm not sure exactly what caused so many people to get xgl turned on, though.

@XGL users - if someone could compile and run this program and check that it does indeed detect Xgl, it would be appreciated.

[Ryan Steele (rgsteele)]

I can confirm that this program did detect Xgl when I had it installed, and after I uninstalled it (which fixed the problem with gnome-settings-daemon, thank you!) it indicates that it is not installed.

(Note for anyone else attempting to compile it, you will need the "libxv-dev" package installed if you don't have it already.)

[Gersprenz (loewenstein)]

Uninstalling xserver-xgl solved the problem for me too - thanks to everyone here. Compiz working fine also. Tried to point users at the Ubuntu Forums who are having the same problem here.
ATI 9600 with envy works also now.

[Hans Deragon (deragon)]

Without xserver-xgl installed, Compiz set to "Visual Effects: Extra" running on an Intel GM965/GL960 graphic card is unstable. As soon as a drag a window, the grabbing mode never stops, even when I release the mouse button. I cannot then type anything and the session does not respond. I have to login from a console to restart gdm. When Compiz is turned off (option "Visual Effects: None"), my desktop works fine.

[Tomasz Sterna (smoku)]

The test program does detect Xgl.

smoku@wing:~$ gcc xorg_xgl_info.c -lX11 -lXv -lXrandr -o xorg_xgl_info
smoku@wing:~$ ./xorg_xgl_info
Xgl: yes
Xrandr: 1.2

And those discouraging Xgl should _really_ read http://lists.freedesktop.org/archives/xorg/2006-February/013306.html

[Sebastien Bacher (seb128)]

this url is not really new, things change quickly in the opensource world, anyway that bug is not the place to discuss why xgl is not installed in most distribution nor supported officially in ubuntu

[mattismyname (mattismyname)]

For those of you reading all of this "aiglx this, xgl that..." mumbo jumbo
and feeling very confused, check out the article below. It has pictures!

http://www.freesoftwaremagazine.com/articles/accelerated_x

After reading it, you will understand libGL, DRI, GL-X, XGL, AIGLX, and
compositing.

Unfortunately it does not touch on Xegl.

[mattismyname (mattismyname)]

Meant to say "Unfortunately it does not touch on full details of Xegl."

[Bryce Harrington (bryce)]

If anyone is still using Xgl, please test with the latest updates. We've put in some checks which we think should handle the crash more gracefully.

If it's still crashing under Xgl, please reopen this bug, and I can look into adding a check specifically for Xgl. Don't think it's necessary though.

[Gersprenz (loewenstein)]

I testet the update: The gnome-settings-manager still crashes. The system sends now an bug report.

[Jamal Fanaian (jamalta)]

Tested the latest update as well. Gnome-settings-daemon seems to still crash. Xgl does seem to work though, and compiz works as well. It is just really slow compared to running Xgl on 7.10.

Thanks for putting time into this bug!

[el es (el-es-poczta)]

Similar problem here, solved by uninstalling the xserver-xgl.
Acer Aspire 3023WLMi ATI Radeon Mobility X700, on fglrx;
Gnome displayed bad GTK theme, no entry chimes, some programs crashing, the catalyst control center didn't work.
With no xserver-xgl now it is all stable.

[shewless (shewless)]

Just wanted to say I'm hoping to use xgl after this bug is fixed. I am running Ubuntu 8.04 with latest ati drivers from EnvyNG. When xgl is installed I get the problem with gnome-settings-manager and performance issues.

Without xgl, compiz works, but the system is choppy (while doing graphical transitions).

In 7.10 I had this working excellent.

Thank you

[shewless (shewless)]

still crashing under xgl.

[mattismyname (mattismyname)]

Shewless: "Incomplete" may not mean what you think it does. ;-) Incomplete means more information is needed from the user in order to confirm the bug. This bug was already confirmed so it should be in status "Confirmed", "In Progress", or "Fix *".

Changed status to In Progress.

[shewless (shewless)]

Ah - sorry I should have looked into that before I changed the status. Thank you for correcting my mistake.

[SlowDeath (family-krg)]

So, is there gonna be a soultion? I don't want to disable Xgl because commpiz becomes really slow.

And what this output means: gnome-settings-daemon
Error: X was unable to determine screen size range for window 82
Error: X was unable to determine screen size range for window 82
Segmentation fault (core dumped)

?

[Kyle138 (kyle138)]

Instead of telling us how unsupported xserver-xgl is, how about telling us what we *should* be using?
I couldn't tell you why I had it installed, I'm pretty sure it comes from my feisty days or earlier, but it seemed to be working until I decided to try out hardy. Without it I don't get the error anymore, and compiz works but is noticeably choppy, but worst of all is none of my 3d games work now! How am I supposed to get any work done without planet penguin racer?

[Bryce Harrington (bryce)]

Kyle, let's please try to keep the discourse civil. Like many of the other commenters have reported in this thread, you should be using xorg-server and AIGLX or NVIDIA's implementation of accelerated indirect rendering. If there exist bugs in it, those should be reported. If Xgl works better for you, that is great, however upstream developers are more likely to spend time looking at xorg-server bugs than Xgl bugs, so getting migrated off of Xgl should be a priority.

[Jamal Fanaian (jamalta)]

@Bryce Harrington,

If I should be migrating off of Xgl, how can I improve my AIGLX experience? I can't get it down to a single bug or problem. The overall performance on my laptop is much lower using AIGLX. Is there something I should be doing to improve it?

I have an ATI Xpress 200 on fglrx. I know fglrx isn't supported too well yet, but at least with Xgl it worked okay, which is why I want to use it instead of AIGLX. At least, until the support for my card is better.

Thanks!
Jamal Fanaian

[Tomasz Sterna (smoku)]

You may try OpenSuSE. AFAIR they do support Xgl.

[shewless (shewless)]

I'm with Jamal,

At the moment I am using AIGLX and fglrx and the only problem is performance - I would be happy to provide information about my system if it would help. I realize this is probably an ati driver problem, but it doesn't change the situation. As of Ubuntu 7.10 I could use glx to solve my problems. I think that many Ubuntu users moving to 8.04 will suffer from performance issues if they use an ati card and want to use compiz.

I'm willing to help test settings for AIGLX and the ati drivers, but if it's a matter of waiting for ati to release better drivers than I think effort should be put into supporting xgl for the time being.

Thank you,

[Sebastien Bacher (seb128)]

the issue is that the current team has a limited number of people and is already way overworked, those comments are not useful in this context, what about trying to give and hand and work on patch to fix the issue rather than complaining that people who work a lot to solve issues for free don't do enough work for your particular usecase?

[shewless (shewless)]

I am offering my hand to reproduce the problem, test potential fixes, and provide information - please let me know if I can help and where it would be useful. Thank you.

[Bryce Harrington (bryce)]

I've been looking into all of the fglrx issues today. Many I suspect are due to AIGLX, but I'm awaiting confirmation of that. Applying help towards confirming and providing extra info on any of those bugs (which are in linux-restricted-modules-2.6.24) would help in moving things forward. Identifying issues that are dupes of other reported issues would be extremely helpful.

Timo is uploading a new -fglrx driver today (8.4 iirc), which I'd encourage you all to test once it becomes available. Identifying issues that have been resolved with this upload would be very helpful at narrowing down the number of bugs that need investigated.

I am in regular contact with the ATI engineering team at AMD, and am bringing some of these bug reports to their attention. So, the higher quality that the -fglrx bug reports can be made, the more likely we can expect AMD to look at and help in resolving them.

[Shaligar (javilol)]

Hello,

When I try to login into gnome, I get an empty brown background, but if I wait long enough (around 2 minutes), the desktop loads, along with an error about gnome-settings-daemon. Because of that, my skins / icons are not configured as they should. After some more time, tho, gnome-settings-daemon seems to load, as my skin and icons change, and the welcome sound is played.

If this the same bug, I'm ready to test any fixes.

[taruj83 (taruj-ansari)]

Yes, i have the problem here.

On Thu, Apr 3, 2008 at 7:43 AM, Shaligar <email address hidden> wrote:

> Hello,
>
> When I try to login into gnome, I get an empty brown background, but if
> I wait long enough (around 2 minutes), the desktop loads, along with an
> error about gnome-settings-daemon. Because of that, my skins / icons are
> not configured as they should. After some more time, tho, gnome-
> settings-daemon seems to load, as my skin and icons change, and the
> welcome sound is played.
>
> If this the same bug, I'm ready to test any fixes.
>
> --
> error starting GNOME Settings Daemon
> https://bugs.launchpad.net/bugs/199960
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Source Package "gnome-settings-daemon" in Ubuntu: Confirmed
>
> Bug description:
> Happened after last night's updates to Hardy.
>
> ** (gnome-settings-daemon:11172): DEBUG: Monitoring dir
> /apps/gnome_settings_daemon/plugins/media-keys for changes
> ** (gnome-settings-daemon:11172): DEBUG: GnomeSettingsModule 0x8080200
> initialising
> ** (gnome-settings-daemon:11172): DEBUG: Loading
> /usr/lib/gnome-settings-daemon-2.0/libxrandr.so
>
> ** (gnome-settings-daemon:11173): WARNING **: Failed to acquire
> org.gnome.SettingsDaemon
>
> ** (gnome-settings-daemon:11173): WARNING **: Could not acquire name
> ** (gnome-settings-daemon:11173): DEBUG: SettingsDaemon finished
> ** (gnome-settings-daemon:11172): DEBUG: Registering GsdXrandrPlugin
> ** (gnome-settings-daemon:11172): DEBUG: Creating object of type
> GsdXrandrPlugin
> ** (gnome-settings-daemon:11172): DEBUG: GsdXrandrPlugin initializing
> ** (gnome-settings-daemon:11172): DEBUG: Activating xrandr plugin
> ** (gnome-settings-daemon:11172): DEBUG: Starting xrandr manager
> The program 'gnome-settings-daemon' received an X Window System error.
> This probably reflects a bug in the program.
> The error was 'BadRequest (invalid request code or no such operation)'.
> (Details: serial 89 error_code 1 request_code 151 minor_code 6)
> (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.)
> 1205011405.201156 Session manager: disconnected...
> ** (gnome-settings-daemon:11184): DEBUG: Successfully connected to D-Bus
> ** (gnome-settings-daemon:11184): DEBUG: Starting settings manager
> ** (gnome-settings-daemon:11184): DEBUG: Loading settings plugins from
> dir: /usr/lib/gnome-settings-daemon-2.0/
> ** (gnome-settings-daemon:11184): DEBUG: Loading plugin:
> /usr/lib/gnome-settings-daemon-2.0/xrdb.gnome-settings-plugin
> ** (gnome-settings-daemon:11184): DEBUG: Monitoring dir
> /apps/gnome_settings_daemon/plugins/xrdb for changes
> ** (gnome-settings-daemon:11184): DEBUG: Loading plugin:
> /usr/lib/gnome-settings-daemon-2.0/screensaver.gnome-settings-plugin
> ** (gnome-settings-daemon:11184): DEBUG: Monitoring dir
> /apps/gnome_settings_daemon/plugins/screensaver for changes
> ** (gnome-se...

[bdowd (bdowd)]

Same problem on a brand new clean install of 8.04B (but I am using a new GeForce 9600 with the proprietary 171.06 NVIDIA driver since there doesn't seem to be any resolution support > 800x600 available for that video card in Hardy.
I can can compile in the nvidia kernel module and run it AOK, (1280x1024) but then, of course, any updating to a new kernel breaks it.
Symptom is blank window upper left that eventually (after 5-10 mins) displays "There was an error starting the GNOME settings daemon". Now the resolution remains 800x600 only.

[Tomasz Sterna (smoku)]

This is a regression, so demanding a fix from users is not the right way.
Just undo what did break it and all will be fine.

[allenmaher (allenmaher-gmail)]

I am still getting this bug in the beta version... it has persisted since I installed Alpha 5. I had this working under Gusty... so I disappointed by the regressive behavior... hoping someone finds this bug soon.

[Bryce Harrington (bryce)]

gnome-desktop (1:2.22.1-0ubuntu5) hardy; urgency=low

  * Fix the randr stuff on Xgl when the screen info can't be retrieved.
    (LP: #199960)

 -- James Westby <email address hidden> Thu, 10 Apr 2008 10:42:50 +0100

[SlowDeath (family-krg)]

It works! Thanks a lot!

[ulugeyik (durduran)]

I have upgraded to Hardy Heron (04/28/08) . I have the same problem on an irregular basis. When problem occurs, I have ~1 min of dark screen, then gnome gives the error described in this bug. Then starts with "unusual" looking icons and such. The system works but slowly. Once in a while, everything goes smoothly, I do not have the error , I see my usual looking icons and such but things like wireless cards (network-manager) do not work.

[Ryan Steele (rgsteele)]

ulugeyik, can you confirm whether removing xgl rectifies the problem? Also, can you specify exactly which error it is you are getting?

[ulugeyik (durduran)]

Hmmm. May be I misspoke. I apologize. Feel free to delete it if it is inappropriate or dublicate.

My error may not be exactly as in this bug (sounded just like it when I read it). I do not have xgl installed. The error I get is as belows.

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.

[Steffen Grøhn (stefgro)]

jtuchscherer's solution works like a charm with ati x1150.
Thank you Jtuchscherer and Saki!

I had this problem on hardy and gutsy, but now it runs much faster, and I can change resolution in the gui! Thank you!

-Steffen

[clutchmm (clutch-boa)]

I'm not sure if my issue is with the settings daemon or not. I am running Hardy on my laptop and desktop. My desktop had feisty AMD64 so I did a clean install of Hardy i386 so I could use the programs that haven't made it to the 64-bit architecture. My laptop was just upgraded to Hardy since it was already running Feisty i386. My desktop hasn't had any problems but my laptop has had this issue since the upgrade. I switched just after the official release so I have been just dealing with it for over a month now. I have applied all updates that have shown up thinking that a fix was coming sooner or later. My laptop has never had XGL installed and compiz has always been disabled because my on-board graphics card doesn't work with compiz. Yet I still have this issue where my gnome session won't start unless I change the session to gnome failsafe (or terminal failsafe and type 'gnome-session'). When I try to log in normally I briefly see a flash of a terminal screen and catch something at the bottom about "startup scripts" and the screen goes black and stays there until I get frustrated and manually turn off the power. Luckily I have still been able to use it in "gnome failsafe" mode or I might have destroyed my laptop by now. So if this issue is fixed how do I do it? None of the released updates have made a difference and nothing here has worked except for the "failsafe terminal" start. Please help me.........

[phyz (phyz2010)]

i've go the same problem too.after i set wicd on the startup session and when i reboot,my gnome setting daemon failure...i still can't work as normal even i reboot or logout.

[mattismyname (mattismyname)]

LinkedIn
------------

Bug,

I'd like to add you to my professional network on LinkedIn.

- Matt

Learn more:
https://www.linkedin.com/e/isd/544944462/EAl-WEf5/

------------------------------------------

What is LinkedIn and why should you join?
http://learn.linkedin.com/what-is-linkedin

------
(c) 2009, LinkedIn Corporation