Description of problem: With using TOSHIBA LX3516 laptop with another monitor connented with VGA, when I - boot the computer (now using init=/sbin/upstart for some reason) with runlevel 3 - On tty1 login as root - type init 5 Then - GUI launches. At first display is shown on both laptop window and the monitor connected with VGA - But with another few seconds, suddenly display on the monitor connected with VGA disappears and it becomes totally black - And gdm login window only appears on LVDS window Version-Release number of selected component (if applicable): gnome-settings-daemon-2.31.6-1.fc14 (actually 2.31.2? - 2.31.6) How reproducible: 100% Additional info: gnome-settings-daemon-2.30.1-6.fc13 works. Note that I still use F-13 packages for kernel, xorg-x11-server-XXX, xorg-x11-drv-XXX and mesa. The rest rpms are F-14 ones.
Created attachment 438536 [details] Xorg.0.log
Created attachment 438537 [details] dmesg
Created attachment 438538 [details] xorg.conf
Created attachment 438539 [details] xrandr output with g-s-d 2.30.1
Still reproducible with gnome-settings-daemon-2.31.6-1.fc14 and kernel-2.6.35.2-9.fc14.i686 xorg-x11-server-Xorg-1.9.0-1.fc14.i686 xorg-x11-drv-intel-2.12.0-4.fc14.i686
Still no good with gnome-settings-daemon-2.31.91-1.fc14 gnome-settings-daemon-2.30.1-6.fc13 works.
If you're using the F13 packages for everything that could possibly have to do with output setup, then there's no possible way we can tell if it works in F14. Removing from F14Blocker.
What I am saying is that - I am now using F-14 branch - "Only" F-14 gnome-settings-daemon does not work (i.e. again I use F-14 packages except for gnome-settings-daemon).
Still no good with xorg-x11-server-Xorg-1.9.0-4.fc14.i686 gdm-2.31.90-4.fc14.i686 gnome-settings-daemon-2.31.91-2.fc14.i686 kernel-2.6.35.4-18.fc14.i686
Created attachment 447023 [details] dmesg (2.6.35.4-18.fc14.i686)
Created attachment 447024 [details] Xorg.0.log (1.9.0-4.fc14) Now xorg.conf does not exist
(In reply to comment #7) > If you're using the F13 packages for everything that could possibly have to do > with output setup, Now xorg.conf does not exist, and I don't think I am doing some special setup for output.
Okay, now I tried Fedora 14 Beta Live Image and this issue still remains. Using F-14beta Live + downloading gnome-setings-daemon to 2.30.1-8.fc13.i686 solves my problem.
This was discussed at the blocker review meeting of 2010-10-01. We agreed it is not a blocker as we do not cover multi-head configurations, and this seems to be a single system issue (several of us have dual head configs and they work fine).
Created attachment 452598 [details] Patch to make external display on by default So I compared the source of gnome-settings-daemon between 2.30.1 and 2.31.2, and it seems that actually with gnome-settings-daemon >= 2.31.2 external display is explicity disabled by default, in ./data/apps_gnome_settings_daemon_xrandr.schemas.in : ---------------------------------------------------- 17 <schema> 18 <key>/schemas/apps/gnome_settings_daemon/xrandr/turn_on_external_monitors_at_startup</key> 19 <applyto>/apps/gnome_settings_daemon/xrandr/turn_on_external_monitors_at_startup</applyto> 20 <owner>gnome</owner> 21 <type>bool</type> <==================================== 22 <default>false</default> 23 <locale name="C"> 24 <short>Turn on external monitor after system boot</short> 25 <long>Turn on external monitor after system boot if user plugs in 26 external monitor on system boot. 27 </long> 28 </locale> 29 </schema> ---------------------------------------------------- Changing this value to true, i.e. applying the following patch works for me. Would you consider to add this? (Well, I think it is preferable to make external display on by default...)
Bug 639144 is a possible duplicate of this one.
*** Bug 639144 has been marked as a duplicate of this bug. ***
given Mamoru's diagnosis this obviously isn't single-system; those of us who don't have this problem obviously have stored configs which pre-date it. So I re-propose this for NTH status; I don't think this counts as a blocker but I *do* think we should make sure the dual-head policy we have in the release is actually the one we want, and if it's not, we should take a fix for it through the freeze, since it's just a gconf key change and logically *can't* cause new blockers since multi-head configuration isn't a blocker issue. I'll flag this issue up for the desktop team to look at, CCing mclasen. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Discussed at the 2010-10-15 review meeting. We agreed that if the desktop team decides to change this setting to match our previous default behaviour, we would take the fix, so this is accepted as an NTH bug. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
FYI: Ubuntu bug: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/640807 and upstreamed bug into GNOME site: https://bugzilla.gnome.org/show_bug.cgi?id=631388 especially: https://bugzilla.gnome.org/show_bug.cgi?id=631388#c2 http://bugzilla-attachments.gnome.org/attachment.cgi?id=171747 Ubuntu introduced a new key "use_xorg_monitor_settings" which disables gnome-settings-daemon to touch monitor settings and set this key (use_xorg_monitor_settings) as true. With this patch applied and with the key "use_xorg_monitor_settings" set to true, now I get "spanned" mode on gdm (as was in F-13) instead of "clonned" mode (with turn_on_external_monitors_at_startup set as true).
note that today is the deadline for RC1, if we want to change this behaviour for F14 you need to submit the build to implement this to Bodhi today and have it reach the karma threshold. After that this can only be changed if we hit blocker bugs that require further RCs to be built. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Adam, can this issue be the candidate for "Common bug"? http://fedoraproject.org/wiki/Common_F14_bugs
Yup, indeed, we should document it there now it hasn't been changed. To propose an issue for a common bugs note, add the CommonBugs keyword. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
Removing F14 NTH status as F14 is now out. Remaining open nice-to-have issues do NOT automatically become nice-to-have issues for Fedora 15. If you believe a Fedora 14 issue which was accepted as nice-to-have but not resolved in time for release should also qualify for nice-to-have status for Fedora 15, please re-propose it as nice-to-have for Fedora 15. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
-- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
gnome-settings-daemon-2.32.0-2.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/gnome-settings-daemon-2.32.0-2.fc14
(In reply to comment #26) > gnome-settings-daemon-2.32.0-2.fc14 has been submitted as an update for Fedora > 14. > https://admin.fedoraproject.org/updates/gnome-settings-daemon-2.32.0-2.fc14 As I wrote in bodhi, this rpm fixes the issue, thank you. Adam, if this new gnome-settings-daemon hits testing, would you update F14 common bug wiki? (Or, as g-s-d is in critpath and as I already put +1 vote, another +1 vote by proventester will make this g-s-d go into stable directly, if I am correct)
gnome-settings-daemon-2.32.0-2.fc14 has been pushed to the Fedora 14 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update gnome-settings-daemon'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/gnome-settings-daemon-2.32.0-2.fc14
gnome-settings-daemon-2.32.0-2.fc14 fixes this issue.
gnome-settings-daemon-2.32.0-2.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 651378 has been marked as a duplicate of this bug. ***
*** Bug 651706 has been marked as a duplicate of this bug. ***