On 2019-01-18 12:10 p.m., Patrick Shanahan wrote:

* Patrick Shanahan [01-18-19 11:32]:

...

I have a Toshiba laptop with intel graphics and Tumbleweed which just started presenting a black logon screen for tty7.

this just started but the laptop had not been updated for about a month, was out of town.

toshiba: ~ # inxi -G Graphics: Device-1: Intel HD Graphics 5500 driver: i915 v: kernel Display: server: X.Org 1.20.3 driver: intel unloaded: fbdev,modesetting,vesa resolution: 1920x1080~60Hz, 1920x1080~60Hz OpenGL: renderer: N/A v: N/A

more info: I can access graphical environment using startx as <user> from either runlevel 3 or 5, multi-user/graphical.target

and all appears *normal*.

Are you saying it is specifically the LOGON screen that is black? When you 'startx' I presume there is no login screen since you are already logged in. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

Carlos E. R. composed on 2019-01-18 18:19 (UTC+0100):

Patrick Shanahan wrote:

...

where to start debugging?

Did you try removing xf86-video-intel?

Same question. + + + -- Evolution as taught in public schools is religion, not science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

* Anton Aylward [01-18-19 12:15]:

On 2019-01-18 12:10 p.m., Patrick Shanahan wrote:

...

* Patrick Shanahan [01-18-19 11:32]:

...

I have a Toshiba laptop with intel graphics and Tumbleweed which just started presenting a black logon screen for tty7.

this just started but the laptop had not been updated for about a month, was out of town.

toshiba: ~ # inxi -G Graphics: Device-1: Intel HD Graphics 5500 driver: i915 v: kernel Display: server: X.Org 1.20.3 driver: intel unloaded: fbdev,modesetting,vesa resolution: 1920x1080~60Hz, 1920x1080~60Hz OpenGL: renderer: N/A v: N/A

more info: I can access graphical environment using startx as <user> from either runlevel 3 or 5, multi-user/graphical.target

and all appears *normal*.

Are you saying it is specifically the LOGON screen that is black? When you 'startx' I presume there is no login screen since you are already logged in.

correct. booting to graphical.target present black logon screen and restarting sddm doesn't change it nor does <ctrl><alt><backspace> twice. startx as <user> present the same environment/display I had previously booting to graphical.target and does so from either multi-user or graphical.target -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday, 2019-01-18 at 15:43 -0500, Patrick Shanahan wrote:

* Felix Miata <> [01-18-19 12:54]:

...

Carlos E. R. composed on 2019-01-18 18:19 (UTC+0100):

...

Patrick Shanahan wrote:

...

...

where to start debugging?

...

Did you try removing xf86-video-intel?

Same question. + + +

yes, same outcome, black login screen

...

toshiba: ~ # rpm -q xf86-video-intel package xf86-video-intel is not installed

Yes, it does not seem related to the video driver, if you can start it with startx. - -- Cheers, Carlos E. R. (from openSUSE 15.0 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCXEI/XBwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVNA0AnR3gUl0ejUoTdOCDd4Zw QzMKBxCcAJ9vBURabJLlGzm0CiAD6Dlp/dnqZg== =juvL -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

* Anton Aylward [01-18-19 16:09]:

On 2019-01-18 1:00 p.m., Patrick Shanahan wrote:

...

...

Are you saying it is specifically the LOGON screen that is black? When you 'startx' I presume there is no login screen since you are already logged in. correct. booting to graphical.target present black logon screen and restarting sddm doesn't change it nor does <ctrl><alt><backspace> twice.

startx as <user> present the same environment/display I had previously booting to graphical.target and does so from either multi-user or graphical.target

Perhaps, just perhaps, something has corrupted, removed or otherwise affected the files concerned with the display of the graphical image and the overlay of the dialogue box.

I use to know about these things for KDE3, played with trying to customise/create one of my own, but for the current system, SDDM and all, I don't know where to begin.

Perhaps other might give you a clue what to look for, what to verify?

Or perhaps the best thing is to investigate using yast/zypper/rpm and the man pages what is involved and reinstall. Which is a memory fart as to how I found out for KDE3 ...

Oh, wait, this is Tumbleweed ...

ran: btrfs scrub start /dev/sda6 found two errors ran: dmesg | sed -n -r 's#.*BTRFS.*i/o error.*path: (.*)\)#\1#p' |sort -u (found on internet) displayed two files. deleted sub files, one cache and other log restarted system to multi-user.target reran: btrfs scrub start /dev/sda no errors changed to graphical.target login screen correct jeshhhhh tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

* Carlos E. R. [01-18-19 16:47]:

On 18/01/2019 22.35, Patrick Shanahan wrote:

...

...

ran: btrfs scrub start /dev/sda6 found two errors ran: dmesg | sed -n -r 's#.*BTRFS.*i/o error.*path: (.*)\)#\1#p' |sort -u (found on internet) displayed two files.

deleted sub files, one cache and other log

What files were those?

/var/lib/sddm/.cache/icon-cache.kcache /var/log/snapper.log -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

* Carlos E. R. [01-18-19 17:00]:

On 18/01/2019 22.49, Patrick Shanahan wrote:

...

* Carlos E. R. [01-18-19 16:47]:

...

On 18/01/2019 22.35, Patrick Shanahan wrote:

...

...

ran: btrfs scrub start /dev/sda6 found two errors ran: dmesg | sed -n -r 's#.*BTRFS.*i/o error.*path: (.*)\)#\1#p' |sort -u (found on internet) displayed two files.

deleted sub files, one cache and other log

What files were those?

/var/lib/sddm/.cache/icon-cache.kcache /var/log/snapper.log

I think the culprit was the first one. I guess that deleting the contents of "/var/lib/sddm/" would have worked. It is its home directory:

Isengard:~ # grep sddm /etc/passwd sddm:x:479:477:SDDM daemon:/var/lib/sddm:/bin/false Isengard:~ #

probably, but would have left the btrfs file system with errors. now they are corrected or the sectors blocked. system now reports no errors. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

* Carlos E. R. [01-18-19 23:35]:

On 18/01/2019 23.11, Patrick Shanahan wrote:

...

* Carlos E. R. <> [01-18-19 17:00]:

...

...

...

/var/lib/sddm/.cache/icon-cache.kcache /var/log/snapper.log

I think the culprit was the first one. I guess that deleting the contents of "/var/lib/sddm/" would have worked. It is its home directory:

Isengard:~ # grep sddm /etc/passwd sddm:x:479:477:SDDM daemon:/var/lib/sddm:/bin/false Isengard:~ #

probably, but would have left the btrfs file system with errors. now they are corrected or the sectors blocked. system now reports no errors.

Well, filesystem errors should be detected automatically on boot.

it may have and I didn't notice until after I first posted. I ran the btrfs scrub after noticing the errors. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org

* Peter Suetterlin [01-19-19 12:54]:

Patrick Shanahan wrote:

...

* Carlos E. R. [01-18-19 16:47]:

...

On 18/01/2019 22.35, Patrick Shanahan wrote:

...

...

ran: btrfs scrub start /dev/sda6 found two errors ran: dmesg | sed -n -r 's#.*BTRFS.*i/o error.*path: (.*)\)#\1#p' |sort -u (found on internet) displayed two files.

deleted sub files, one cache and other log

What files were those?

/var/lib/sddm/.cache/icon-cache.kcache

sddm cache would have been my guess, yes. There had been bad issues with that last year (?) Seems it's solved now, yes?

for me, for this case, yes. solved for the rest-of-the-world, ??? -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org