[Bug 947734] New: GNOME does not start
http://bugzilla.suse.com/show_bug.cgi?id=947734 Bug ID: 947734 Summary: GNOME does not start Classification: openSUSE Product: openSUSE Distribution Version: 42.1 Beta 1 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: bnc-team-gnome@forge.provo.novell.com Reporter: hguo@suse.com QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- Created attachment 649206 --> http://bugzilla.suse.com/attachment.cgi?id=649206&action=edit System journal Grab openSUSE-Leap-42.1-DVD-x86_64-Build0186-Media.iso. Install the ISO on KVM, choose GNOME as default desktop, do not enable autologin. After system reboots, enter password at SDBM login prompt. Observe that GNOME desktop does not start. System journal is attached. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=947734
http://bugzilla.suse.com/show_bug.cgi?id=947734#c1
Dominique Leuenberger
http://bugzilla.suse.com/show_bug.cgi?id=947734
http://bugzilla.suse.com/show_bug.cgi?id=947734#c2
Howard Guo
http://bugzilla.suse.com/show_bug.cgi?id=947734
http://bugzilla.suse.com/show_bug.cgi?id=947734#c3
--- Comment #3 from Howard Guo
http://bugzilla.suse.com/show_bug.cgi?id=947734
http://bugzilla.suse.com/show_bug.cgi?id=947734#c4
Dominique Leuenberger
http://bugzilla.suse.com/show_bug.cgi?id=947734
http://bugzilla.suse.com/show_bug.cgi?id=947734#c5
--- Comment #5 from Howard Guo
http://bugzilla.suse.com/show_bug.cgi?id=947734
http://bugzilla.suse.com/show_bug.cgi?id=947734#c8
--- Comment #8 from Howard Guo
http://bugzilla.suse.com/show_bug.cgi?id=947734
http://bugzilla.suse.com/show_bug.cgi?id=947734#c9
--- Comment #9 from Dominique Leuenberger
Doesn't help, sorry.
Could you or any other developer install Leap on KVM and try it out?
https://openqa.opensuse.org/group_overview/7 every single test runs in qemu-kvm -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=947734
http://bugzilla.suse.com/show_bug.cgi?id=947734#c10
Dr. Werner Fink
http://bugzilla.suse.com/show_bug.cgi?id=947734
http://bugzilla.suse.com/show_bug.cgi?id=947734#c11
--- Comment #11 from Egbert Eich
http://bugzilla.suse.com/show_bug.cgi?id=947734
http://bugzilla.suse.com/show_bug.cgi?id=947734#c13
--- Comment #13 from Dr. Werner Fink
http://bugzilla.suse.com/show_bug.cgi?id=947734
http://bugzilla.suse.com/show_bug.cgi?id=947734#c14
--- Comment #14 from Dominique Leuenberger
(In reply to Dominique Leuenberger from comment #12)
The QA for the maintenance update for SLES12 as well as for SLES12-SP1 is pending. The maintaineres of systemd do have no influence on that.
I'm having some trouble following your train of thoughts: * I state that the user claimed that there were no updates running on his machine, thus there is no reason why systemd-logind would have undergone a restart; that has nothing to do if there are pending updates to systemd, if QA is on vacation or if there is not even a systemd submission pending. The system simply did not perform an update at this moment - and systemd-logind 'disappeared from the BUS, tearing X down' * In comment 7, I asked howard to test your systemd package from Base:System:Legacy/systemd; in comment 8 he confirmed having tested that, without success Do you realistically see that what is currently in maintenance review will make any change to Howards case? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=947734
Dr. Werner Fink
http://bugzilla.suse.com/show_bug.cgi?id=947734
Dr. Werner Fink
http://bugzilla.suse.com/show_bug.cgi?id=947734
http://bugzilla.suse.com/show_bug.cgi?id=947734#c15
--- Comment #15 from Dr. Werner Fink
The system simply did not perform an update at this moment - and systemd-logind 'disappeared from the BUS, tearing X down'
I never ever had seen a disappearing systemd-logind, also the journals do not show any warning/error from the side of systemd and/or systemd-logind. Therefore I'd like to see the *complete* journal outout as well as the results of systemctl status --all systemd-logind.service systemctl status --all dbus-org.freedesktop.login1.service systemctl status --all dbus.service -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=947734
http://bugzilla.suse.com/show_bug.cgi?id=947734#c16
--- Comment #16 from Dr. Werner Fink
http://bugzilla.suse.com/show_bug.cgi?id=947734
http://bugzilla.suse.com/show_bug.cgi?id=947734#c17
Howard Guo
http://bugzilla.suse.com/show_bug.cgi?id=947734
http://bugzilla.suse.com/show_bug.cgi?id=947734#c18
Franck Bui
The image is freshly installed and never booted.
I gave your image a test and this is what I got from my testings: - SDDM + Gnome : KO - SDDM + KDE : OK - SDDM + icewm : OK - GDM + Gnome : OK So it doesn't match entirely what you described earlier since GDM can start gnome just fine. There's no issue related to systemd-logind in the failing case (SDDM + Gnome).
From what I could see the gnome session was created just fine but the screen just display the X screen without the DE.
Also after installing Leap (NET install version) with Gnome as default desktop, the system rebooted just fine, since by default SDDM is not used. How SDDM was installed initially on your system ? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=947734
http://bugzilla.suse.com/show_bug.cgi?id=947734#c19
--- Comment #19 from Franck Bui
http://bugzilla.suse.com/show_bug.cgi?id=947734
http://bugzilla.suse.com/show_bug.cgi?id=947734#c20
--- Comment #20 from Howard Guo
http://bugzilla.suse.com/show_bug.cgi?id=947734
http://bugzilla.suse.com/show_bug.cgi?id=947734#c21
--- Comment #21 from Franck Bui
Thanks for your feedback Franck.
SDDM is the default choice of installer.
The image was produced simply by clicking Next in all installation steps, except that Gnome softwares were chosen to be installed as well.
I did a that and choose Gnome as default desktop and GDM was automatically chosen and used during the next reboot. SDDM would be an odd choice as default DM when Gnome is selected.
I run the image in KVM on Tumbleweed, neither SDDM nor GDM is not able to start Gnome.
"systemd-logind disappeared" comes from GDM log, you have to try GDM + Gnome combination to see it.
As I mentionned in my comment #17, I tried all combinations and only SDDM + Gnome is actually failing but it's a known problem. How did you switch from SDDM to GDM exactly ? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=947734
http://bugzilla.suse.com/show_bug.cgi?id=947734#c22
--- Comment #22 from Howard Guo
http://bugzilla.suse.com/show_bug.cgi?id=947734
http://bugzilla.suse.com/show_bug.cgi?id=947734#c23
--- Comment #23 from Franck Bui
Switch from SDDM to GDM by editing /etc/sysconfig/displaymanager file.
When using the image you provided, this works perfectly fine (GDM + Gnome/KDE). -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=947734
http://bugzilla.suse.com/show_bug.cgi?id=947734#c24
--- Comment #24 from Howard Guo
http://bugzilla.suse.com/show_bug.cgi?id=947734
http://bugzilla.suse.com/show_bug.cgi?id=947734#c25
--- Comment #25 from Franck Bui
Are you on tumbleweed ?
Yes, my host is Tumbleweed. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=947734
http://bugzilla.suse.com/show_bug.cgi?id=947734#c26
--- Comment #26 from Howard Guo
http://bugzilla.suse.com/show_bug.cgi?id=947734
http://bugzilla.suse.com/show_bug.cgi?id=947734#c27
--- Comment #27 from Franck Bui
http://bugzilla.suse.com/show_bug.cgi?id=947734
http://bugzilla.suse.com/show_bug.cgi?id=947734#c28
--- Comment #28 from Howard Guo
http://bugzilla.suse.com/show_bug.cgi?id=947734
http://bugzilla.suse.com/show_bug.cgi?id=947734#c29
Dr. Werner Fink
http://bugzilla.suse.com/show_bug.cgi?id=947734
http://bugzilla.suse.com/show_bug.cgi?id=947734#c30
Howard Guo
http://bugzilla.suse.com/show_bug.cgi?id=947734
http://bugzilla.suse.com/show_bug.cgi?id=947734#c31
Dr. Werner Fink
http://bugzilla.suse.com/show_bug.cgi?id=947734
http://bugzilla.suse.com/show_bug.cgi?id=947734#c32
--- Comment #32 from Howard Guo
http://bugzilla.suse.com/show_bug.cgi?id=947734
http://bugzilla.suse.com/show_bug.cgi?id=947734#c33
--- Comment #33 from Dr. Werner Fink
http://bugzilla.suse.com/show_bug.cgi?id=947734
http://bugzilla.suse.com/show_bug.cgi?id=947734#c34
--- Comment #34 from Dominique Leuenberger
Sorry, there's no such file.
the 'current' xdm package was switching to sysv style (so it used /etc/init.d/xdm), as somebody messed up version checks... the new xdm (fixed with both plsces for permission) will be in the next ftp release (I guess somewhen later today) -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.suse.com/show_bug.cgi?id=947734
http://bugzilla.suse.com/show_bug.cgi?id=947734#c35
--- Comment #35 from Howard Guo
http://bugzilla.suse.com/show_bug.cgi?id=947734
http://bugzilla.suse.com/show_bug.cgi?id=947734#c39
--- Comment #39 from Howard Guo
http://bugzilla.suse.com/show_bug.cgi?id=947734
http://bugzilla.suse.com/show_bug.cgi?id=947734#c42
Howard Guo
http://bugzilla.suse.com/show_bug.cgi?id=947734
http://bugzilla.suse.com/show_bug.cgi?id=947734#c43
Dominique Leuenberger
Thanks very much DimStar.
GDM can now successfully launch Gnome
Previously Lxde and Xfce were not starting with SDDM, now they are able to start successfully.
SDDM however still cannot launch Gnome.
Thanks for your testing.. in this case I'd say we are safe closing this bug.. the main issues have all been resolved. The sddm/gnome interaction is already tracked in https://bugzilla.opensuse.org/show_bug.cgi?id=931314 -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com