Op maandag 30 oktober 2017 00:15:56 CET schreef Foolish Ewe:
Hello Patrick:
I just tried this and there are 2 things and I did the following based on your recommendation: 1) Boot to Linux, see plasma login screen 2) Hot key to a console, check to see if the offending file exists and remove it as follows: 2a) Log in as root 2b) ls /usr/lib/systemd/user/sockets.target.wants/dbus.socket 2c) rm /usr/lib/systemd/user/sockets.target.wants/dbus.socket 3) Hot key back to the plasma window 4) Log in
So that resolved the problem in this e-mail, but it also appears to allow me to login to my wireless network. I rebooted and the offending /usr/lib/systemd/user/sockets.target.wants/dbus.socket was not recreated.
While I can't prove it, I think I typed my password correctly on the initial log in attempt both on the initial and follow up test, but it was rejected. I got in on the 1st retry on each test.
This is a huge improvement, I'll comment on https://bugzilla.opensuse.org/show_bug.cgi?id=1020363.
Bill
From: Patrick Shanahan <ptilopteri@gmail.com> on behalf of Patrick Shanahan <paka@opensuse.org> Sent: Sunday, October 29, 2017 10:05 PM To: opensuse-factory@opensuse.org Subject: Re: [opensuse-factory] Plasma hangs on first login attempt after boot, OpenSuse Tumbleweed recent version (as of 10/29/2017) 64 bit.
* Foolish Ewe <foolishewe@hotmail.com> [10-29-17 17:32]:
Hello All:
I'm experiencing an inconvenience with plasma in OpenSuse Tumbleweed with recent updates (as of this morning, 10/29/2017). The symptom I see is when I enter my password into plasma the plasma screen hangs, but the mouse cursor is responsive. I cannot enter text in the password form, nor does clicking on any of the icons trigger a response. Unlike https://bugzilla.opensuse.org/show_bug.cgi?id=1056950, I am able to hot key into a console window. After I do init 3, and then init 5 I can log in. After logging in the network connection does not work (but that was reported in a different e-mail to this list).
Have other people experienced this recently, is there a known work around, or is this a known problem? What logs would help diagnose this (I need to boot into windows to post here, so any journalctl guidance would help)?
Sorry to post so many e-mails, but I'm trying to keep to one issue per e-mail and I apologize if this is redundant but a previous attempt to post this may have been blocked due to http content, trying plaintext this time. fyi: your editor is not wrapping your lines <78 chars
look at: https://bugzilla.opensuse.org/show_bug.cgi?id=1020363
may help.. do: rm /usr/lib/systemd/user/sockets.target.wants/dbus.socket
Just wondering: how do you update your TW ? -- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org