Description of problem: When booting with kernel 3.13.3-201, multi-seat does not work anymore. The primary seat opens up correctly. The secondary screen is blank (the display stays in "eco" mode waiting for a signal). Nothing particular appears in journalctl. Reverting to previous version (3.12.10-300) works I tried with both systemd 208-14 (from update-testing) and 208-9 Version-Release number of selected component (if applicable): yum info kernel : >Name : kernel >Arch : x86_64 >Version : 3.13.3 >Release : 201.fc20 Working version : yum info kernel : >Name : kernel >Arch : x86_64 >Version : 3.12.10 >Release : 300.fc20 How reproducible: Always Steps to Reproduce: 1. set up a multiseat configuration, under kernel 3.12 2. update kernel to 3.13 Actual results: 3. the secondary screen does not start Expected results: 3. the secondary screen should start with gdm and login screen Additional info: # rpm -qa | egrep "(systemd|gdm)" systemd-libs-208-14.fc20.x86_64 pulseaudio-gdm-hooks-4.0-9.gitf81e3.fc20.x86_64 systemd-python-208-14.fc20.x86_64 gdm-libs-3.10.0.1-1.fc20.x86_64 systemd-208-14.fc20.x86_64 gdm-3.10.0.1-1.fc20.x86_64 systemd-devel-208-14.fc20.x86_64 systemd-libs-208-14.fc20.i686 "ps aux | grep X" or "ps aux | grep gdm" does not return anything related to the secondary screen. I didn't try to get Xorg.log, I will soon. I have opened another bug regarding systemd/multiseat, the problems may be related : https://bugzilla.redhat.com/show_bug.cgi?id=1052747 Frédéric.
Created attachment 867849 [details] Xorg.0.log (working session) this is the Xorg log of the working seat (seat 0)
Created attachment 867850 [details] /var/log/gdm/:0.log (working session)
Created attachment 867851 [details] Xorg.1.log (failing session)
Created attachment 867852 [details] /var/log/gdm/:1.log (failing session)
Created attachment 867854 [details] bootup journalctl
I did not see that kernel 3.13.4-200.fc20.x86_64 appeared in the repository before posting the bug. So I updated my kernel and did my homework : it still fails. This time, I fetched the logs from Xorg, gdm and journalctl. As you can see, gdm does not detect any screen for seat1, and thus does not start... Of course, there are several other similar logs (:2, :3....) since Xorg/gdm tries to start several times. FYI, I tried to delete the seat and recreate it with loginctl : in normal case, it should dynamically popup GDM on the newly created screen, but it didn't. Hope this'll help! Frédéric.
Still no change with kernel-3.13.5-202.fc20 : anyone had time to look at this? Maybe I should change the package to systemd?
I tried a few things with kernel 3.13.6-200.fc20.x86_64 The main difference that I see it that, with this kernel, I have the following lines in Xorg.O.log (the working display) : [ 21.469] (==) Matched ati as autoconfigured driver 0 [ 21.469] (==) Matched ati as autoconfigured driver 1 [ 21.469] (==) Matched modesetting as autoconfigured driver 2 [ 21.469] (==) Matched fbdev as autoconfigured driver 3 [ 21.469] (==) Matched vesa as autoconfigured driver 4 While in Xorg.1.log (failing display), I only get : [ 21.033] (==) Matched modesetting as autoconfigured driver 0 [ 21.033] (==) Matched fbdev as autoconfigured driver 1 [ 21.033] (==) Matched vesa as autoconfigured driver 2 Using kernel 3.12 however, I get this in Xorg.0.log : [ 19.812] (==) Matched ati as autoconfigured driver 0 [ 19.812] (==) Matched ati as autoconfigured driver 1 [ 19.812] (==) Matched ati as autoconfigured driver 2 [ 19.812] (==) Matched modesetting as autoconfigured driver 3 [ 19.812] (==) Matched fbdev as autoconfigured driver 4 [ 19.812] (==) Matched vesa as autoconfigured driver 5 As you can see, ati matches 3 times instead of 2 (I don't known why...). And in Xorg.1.log, I get the expected : [ 19.809] (==) Matched ati as autoconfigured driver 0 [ 19.809] (==) Matched modesetting as autoconfigured driver 1 [ 19.809] (==) Matched fbdev as autoconfigured driver 2 [ 19.809] (==) Matched vesa as autoconfigured driver 3 In every cases (3.12 and 3.13), I also get the following lines in Xorg.0.log : [ 19.803] (II) xfree86: Adding drm device (/dev/dri/card0) [ 19.804] (II) xfree86: Adding drm device (/dev/dri/card1) [ 19.810] (--) PCI:*(0:1:0:0) 1002:6758:174b:e194 rev 0, Mem @ 0xc0000000/268435456, 0xfea20000/131072, I/O @ 0x0000e000/256, BIOS @ 0x????????/131072 [ 19.810] (--) PCI: (0:5:0:0) 1002:68b9:174b:e144 rev 0, Mem @ 0xb0000000/268435456, 0xfe820000/131072, I/O @ 0x0000c000/256, BIOS @ 0x????????/131072 and only the following line in Xorg.1.log : [ 19.806] (II) xfree86: Adding drm device (/dev/dri/card1) I also tried putting a pci-stub for card1 at startup (using pci-stub.ids=XXXX:XXXX), which prevented Xorg (display :0) to try to attach to it. I then unbound the card from pci-stub, rebound it to radeon, but it did not change anything (I tried to detach/re-attach the display to seat1, and used "udevadm trigger" to ensure everything was set properly : Xorg.*.log was created as expected, but was the same as before) So, I'm still stuck with 3.12... Goulou.
Ditto. Experienced the same issue after upgrading off 3.12.10-300. Have tried 3.13.5-202 and 3.13.6-200 -- no good. When examining the difference between Xorg.1.log files (working, not working) noted this: < (==) Matched ati as autoconfigured driver 0 < (==) Matched modesetting as autoconfigured driver 1 < (==) Matched fbdev as autoconfigured driver 2 < (==) Matched vesa as autoconfigured driver 3 --- > (==) Matched modesetting as autoconfigured driver 0 > (==) Matched fbdev as autoconfigured driver 1 > (==) Matched vesa as autoconfigured driver 2
Tried 3.13.8-200.fc20 -- now multiseat appears to work fine!
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.