gnome-settings-daemon failes to start with Xgl

Bug #205227 reported by satkata
4
Affects Status Importance Assigned to Milestone
gnome-settings-daemon (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: gnome-settings-daemon

I'm using the latest Hardy Beta with Compiz 0.7.2 and wanted to try Xgl so I installed xserver-xgl package.

After restart xgl started normally but on login I got a message-box, that the gnome-settings-daemon
failed to start several times.
So I got a the fallback gtk1 look. There were another inconsistencies too, but guess these are follow errors because of gnome-settings-daemon not being started.

After I returned back to normal Xorg/aiglx with compiz everything starts normally.

I don't know if this could be a Xgl bug, so if so, I'll report it there if necessary.
If you also need further information, I'd be glad to help, but I couldn't find anything in the logs, so
instructions are welcome.

Revision history for this message
lisael (lisael) wrote :

I run xgl too and I've got exactly the same bug since my Gutsy −> Hardy Beta upgrade (today the 03∕30). When i try to launch gnome−settings−daemon, i get this error message:

Error: X was unable to determine screen size range for window 82
parse error
Error: X was unable to determine screen size range for window 82
Segmentation fault (core dumped)

This seems to be a known bug ( see http://ubuntuforums.org/showthread.php?p=4609834 )

Revision history for this message
lisael (lisael) wrote :

My system:
Ubuntu x86_64 on
Intel Pentium e2180 2.0GHz
1GB DDR2 667 MHz
intel i947 shipset

Revision history for this message
SlowDeath (family-krg) wrote :

Same problem after updating to Hardy. After disabling Xgl, everything works fine.

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

Thanks for the bug report. This particular bug has already been reported, but feel free to report any other bugs you find.

Changed in gnome-settings-daemon:
importance: Undecided → Medium
status: New → 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.