GNOME Bugzilla – Bug 627685
gnome-settings-daemon can only start when two monitors are connected
Last modified: 2012-10-10 04:03:55 UTC
When running on a computer with ATI X1250 (radeon driver) and two outputs (DVI and HDMI), modeset activated and kernel 2.6.34 or 2.6.35 (Ubuntu 10.04), gnome-settings-daemon will refuse to start _unless_ the two outputs are connected to a monitor. If only one output is connected to a monitor (either DVI or HDMI), then gnome-settings-daemon and gnome-display-properties both refuse to start with the following error message: ERROR:gnome-rr-config.c:622:gnome_rr_config_new_current: assertion failed: (gnome_rr_config_match (config, config)) The Gnome session however can still be used properly and xrandr used successfully. It seems that gnome-settings-daemon will detect the the two outputs even if only one of them is connected (thanks to modesetting), and try to match them when initializing randr, only to fail because one of the outputs is unconnected. Everything works properly in either those scenarios: - modeset=1 and both DVI and HDMI outputs connected to a monitor - modeset=0, with a single or two monitors connected While this may be linked to modesetting options in the kernel, I believe this is also a bug/design flaw in the gnome software proper. This is very very similar to http://www.mail-archive.com/desktop-bugs@lists.ubuntu.com/msg361681.html
Moving to gnome-desktop... Please state your versions of g-s-d, gnome-control-center and gnome-desktop.
Please find the info below: gnome-desktop: 2.30.2 gnome-settings-daemon: 2.30.1 gnome-control-center: 2.30.1 Please let me know if more info is required, I'll be happy to provide it. Thank you very much
Which patches does Ubuntu put in gnome-desktop?
Hi Frederico, I'm sorry I don't have that kind of knowledge - I can try to use any live CD that has kernel >= 2.6.34 to see if I can reproduce the behavior, if you can point me to one whose gnome-desktop patches are familiar to you. Thank you very much, Yannick
Does this still happen with a recent version?
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!