|
Bugzilla – Full Text Bug Listing |
| Summary: | sddm won't start on a laptop with hybrid graphics (HP EliteBook 850 G1) | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Distribution | Reporter: | Forgotten User l3l1jwfRRz <forgotten_l3l1jwfRRz> |
| Component: | X11 Applications | Assignee: | Forgotten User DV81ZEWZkN <forgotten_DV81ZEWZkN> |
| Status: | RESOLVED WONTFIX | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Major | ||
| Priority: | P5 - None | CC: | chcao, erwin.vandevelde, milan.zimmermann, wbauer |
| Version: | Leap 42.1 | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Forgotten User l3l1jwfRRz
2015-08-02 11:22:29 UTC
Sounds like a dup. *** This bug has been marked as a duplicate of bug 940294 *** Not sure why this is a duplicate of the tracker. I have what appears to be the same problem. Just installed Leap 42.1 m2 today;
I get a black screen after boot about 9 out of 10 reboots.
My Graphics is:
01:05.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] RS880 [Radeon HD 4290] [1002:9714]
Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
Kernel driver in use: radeon
Is there any other info I can provide to help?
hgraeber over at the sddm bug report seems to have found a solution for this problem. It seems that the display setup script gets stuck. He referred to this patch that seems to have solved this problem in Tumbleweed https://github.com/sddm/sddm/commit/7ed4ab11656c4b75f278b34883f4e28598b2b13a In addition there has been a new sddm release 0.12 which seem to fix the problem by killing the display setupscript after 30 seconds. http://plfiorini.blogspot.co.at/2015/09/sddm-0120-released.html "BACKWARDS-INCOMPATIBLE: Display setup script is now killed if it hasn't finished within 30 seconds" by adding this // wait for finished if (!displayScript->waitForFinished(30000)) displayScript->kill(); to https://github.com/sddm/sddm/blob/master/src/daemon/XorgDisplayServer.cpp I hope this helps! Cheers! P.S.: Will sddm be patched / upgraded to 0.12 for Leap or is there any other way we could this if this really fixes our issue? Maintainer of sddm is SUmski. I don't know to which mail address and bugzilla account this user maps. Problem is reproducible on Sony VAIO Pro (Intel HD4000 gfx) Workaround: switch to console (ctrl+alt+F2) and log in as root, then pkill sddm (In reply to Erwin Van de Velde from comment #7) > Problem is reproducible on Sony VAIO Pro (Intel HD4000 gfx) > > Workaround: switch to console (ctrl+alt+F2) and log in as root, then pkill > sddm I recently noticed a similar problem on a minimal X installation in VirtualBox: after installing and enabling SDDM I only got a black screen. Pressing Ctrl+Alt+Backspace twice (to kill the X session) made the SDDM greeter appear. A KDE installation worked fine though, so I'm not sure it is indeed the same issue. Anyway, in my case this was related to Auto-Login. Disabling it made the greeter show up on boot. (set DISPLAYMANAGER_AUTOLOGIN="" in /etc/sysconfig/displaymanager, or disable it in YaST->Security and Users->User and Group Management->Expert Options->Login Settings) Does that help in your case too? (In reply to Wolfgang Bauer from comment #8) > I recently noticed a similar problem on a minimal X installation in > VirtualBox: Forgot to say: in my case this was Tumbleweed. This is automated batch bugzilla cleanup. The openSUSE 42.1 changed to end-of-life (EOL [1]) status. As such it 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 openSUSE, or you can still observe it under openSUSE Leap 15.0, please feel free to reopen this bug against that version (see the "Version" component in the bug fields), or alternatively open a new ticket. Thank you for reporting this bug and we are sorry it could not be fixed during the lifetime of the release. [1] https://en.opensuse.org/Lifetime |