[opensuse-factory] plasma 5 and sddm, graphical target fails
Installed sddm onto my laptops, a dell and an acer, and after one successful boot, am getting only a green (layered) background screen an no display or possible keyboard input. Cannot go to virtual terminal. Only <ctrl><alt><backspace> gives me the terminal output and last lines are: Started Permit Suer Sessions. Starting Wait for Plymouth Boot Screen to Quit... Starting Terminate Plymouth Boot Screen... Am able to ssh to laptops over ssh, htop reveals little to no action other than itself. What to do? tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Patrick Shanahan wrote:
over ssh, htop reveals little to no action other than itself. What to do?
Kill plymouthd and sddm (it should be stuck so you may need SIGKILL), then restart sddm. See if this fixes the issue. -- Luca Beltrame - KDE Forums team KDE Science supporter GPG key ID: 6E1A4E79 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* Luca Beltrame <lbeltrame@kde.org> [05-21-15 05:26]:
Patrick Shanahan wrote:
over ssh, htop reveals little to no action other than itself. What to do?
Kill plymouthd and sddm (it should be stuck so you may need SIGKILL), then restart sddm. See if this fixes the issue.
Have not yet tried, will when opportunity presents. But this makes system usable and does not make "init 5" usable, ie: a work-a-round(!Tm) rather than a solution/fix. tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Patrick Shanahan wrote:
But this makes system usable and does not make "init 5" usable, ie: a work-a-round(!Tm) rather than a solution/fix.
It means that somehow plymouth is not quitting before sddm starts - I think however this only occurs if you use sddm's own unit file, and not display- manager.service. -- Luca Beltrame - KDE Forums team KDE Science supporter GPG key ID: 6E1A4E79 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* Luca Beltrame <lbeltrame@kde.org> [05-21-15 15:23]:
Patrick Shanahan wrote:
But this makes system usable and does not make "init 5" usable, ie: a work-a-round(!Tm) rather than a solution/fix.
It means that somehow plymouth is not quitting before sddm starts - I think however this only occurs if you use sddm's own unit file, and not display- manager.service.
killing instances of sddm and plymouth allow system to complete booting to graphical.target. using "init 5" causes this, "systemctl start sddm" doesn't ??? And I have one machine, desktop, where init 5 works. ??? tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Patrick Shanahan wrote:
using "init 5" causes this, "systemctl start sddm" doesn't ??? And I have one machine, desktop, where init 5 works. ???
Don't use sddm.service. Set sddm in /etc/sysconfig/displaymanager and use display-manager.service. This should fix the plymouth-sddm race condition. -- Luca Beltrame - KDE Forums team KDE Science supporter GPG key ID: 6E1A4E79 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* Luca Beltrame <lbeltrame@kde.org> [05-22-15 01:38]:
Patrick Shanahan wrote:
using "init 5" causes this, "systemctl start sddm" doesn't ??? And I have one machine, desktop, where init 5 works. ???
Don't use sddm.service. Set sddm in /etc/sysconfig/displaymanager and use display-manager.service. This should fix the plymouth-sddm race condition.
OK, did this. But switching to runlevel 3 works, switching from 3 to 5 does not and "systemctl isolate graphical.target" leaves the same layered green screen and a ?? stuck keyboard ?? or otherwise unresponsive system. 10:25 dell: ~ # systemctl status graphical.target ● graphical.target - Graphical Interface Loaded: loaded (/usr/lib/systemd/system/graphical.target; enabled; vendor preset: disabled) Active: active since Sat 2015-05-23 10:23:02 EDT; 2min 44s ago Docs: man:systemd.special(7) May 23 10:23:02 dell systemd[1]: Reached target Graphical Interface. May 23 10:23:02 dell systemd[1]: Starting Graphical Interface. I can ssh into the system, kill plymouthd and sddm, and am presented with the new kde login screen. or, possibly: systemctl isolate graphical;kill `pidof plymouthd`;kill `pidof sddm` Really seems somewhat convoluted :^/ Also I now have a desktop which will not accept a valid password to unlock the new kde geo-shapes display. Only recoverable by <ctrl><alt><backspace><backspace>. The user password has not been changed in some years and works on ttyX. I do have one desktop that does not currently appear to have problems with init 5. tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Patrick Shanahan composed on 2015-05-21 08:10 (UTC-0400):
over ssh, htop reveals little to no action other than itself. What to do?
Kill plymouthd and sddm (it should be stuck so you may need SIGKILL), then restart sddm. See if this fixes the issue.
Have not yet tried, will when opportunity presents.
But this makes system usable and does not make "init 5" usable, ie: a work-a-round(!Tm) rather than a solution/fix.
If default.target == graphical.target, maybe try changing default.target to multi-user.target and setting 5 on Grub cmdline if and when graphical.target is actual desire for initial boot state. TW had, or maybe still has, a problem if the reverse of above is the overall state (one that does not appear to be or have been present in bugzilla.opensuse.org). I think I have all my TWs switched over to multi-user.target == default.target. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* Felix Miata <mrmazda@earthlink.net> [05-21-15 17:57]:
Patrick Shanahan composed on 2015-05-21 08:10 (UTC-0400):
over ssh, htop reveals little to no action other than itself. What to do?
Kill plymouthd and sddm (it should be stuck so you may need SIGKILL), then restart sddm. See if this fixes the issue.
Have not yet tried, will when opportunity presents.
But this makes system usable and does not make "init 5" usable, ie: a work-a-round(!Tm) rather than a solution/fix.
If default.target == graphical.target, maybe try changing default.target to multi-user.target and setting 5 on Grub cmdline if and when graphical.target is actual desire for initial boot state.
TW had, or maybe still has, a problem if the reverse of above is the overall state (one that does not appear to be or have been present in bugzilla.opensuse.org). I think I have all my TWs switched over to multi-user.target == default.target.
My boxes have always been set to boot to "runlevel 3"/multi-user.target. And the problem as I have observed it is only with/since sddm. tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (3)
-
Felix Miata -
Luca Beltrame -
Patrick Shanahan