[Bug 1002865] New: Cannot login as user thru kdm
http://bugzilla.opensuse.org/show_bug.cgi?id=1002865 Bug ID: 1002865 Summary: Cannot login as user thru kdm Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Critical Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs@opensuse.org Reporter: a_bock@gmx.de QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- I cannot log in as a normal user, only a black screen with mouse is showing. I created a new user with empty home dir: same as above As root a 'startx -- :1' works In journal I have the following messages: Okt 04 19:04:10 andy sddm-greeter[10710]: QObject::installEventFilter(): Cannot filter events for objects in a different thread. Okt 04 19:04:10 andy sddm-greeter[10710]: QObject: Cannot create children for a parent that is in a different thread. (Parent is SDDM::GreeterApp(0x7ffff0524460), parent's thread is QThread(0x18360f0), current thread is QThread(0x1b54810) The problem occured after yesterdays update to Tumbleweed 20160928 I can reproduce the problem on both a hardware machine and a xen DomU -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1002865 http://bugzilla.opensuse.org/show_bug.cgi?id=1002865#c1 Wolfgang Bauer <wbauer@tmo.at> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |a_bock@gmx.de, | |wbauer@tmo.at Summary|Cannot login as user thru |Cannot login as user thru |kdm |sddm Flags| |needinfo?(a_bock@gmx.de) --- Comment #1 from Wolfgang Bauer <wbauer@tmo.at> --- (In reply to Andreas Bock from comment #0)
SDDM::GreeterApp(0x7ffff0524460), parent's thread is QThread(0x18360f0), current thread is QThread(0x1b54810)
I suppose this is about SDDM then, not kdm... ;-)
The problem occured after yesterdays update to Tumbleweed 20160928 I can reproduce the problem on both a hardware machine and a xen DomU
Hm, I just did a fresh Tumbleweed installation in VirtualBox today, and it worked fine (except that Xorg didn't start at all with the vboxvideo driver, not even via xdm or startx, that's a completely different problem though, after uninstalling that it was "fixed"). Just for clarification: you get the black screen instead of the login screen, or when you actually try to login? If it's the latter, it would actually be a problem with the desktop you tried to login to I suppose. And related: do you have Auto-login enabled? Do you get back to the login screen if you press Ctrl+Alt+Backspace twice? Do you use any additional repos? -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1002865 http://bugzilla.opensuse.org/show_bug.cgi?id=1002865#c2 --- Comment #2 from Andreas Bock <a_bock@gmx.de> ---
Just for clarification: you get the black screen instead of the login screen, or when you actually try to login?
I get the black screen after login. The login screen shows just fine.
If it's the latter, it would actually be a problem with the desktop you tried to login to I suppose.
I tried all available selections icewm, twm, kodi kde5, kde plasma : they all bevave the same. After I enter the password I get that black screen with mouse.
And related: do you have Auto-login enabled?
I don't have autologin enabled.
Do you get back to the login screen if you press Ctrl+Alt+Backspace twice?
Yes, after that, the login screens shows up again. Some googling showed me that: https://bugs.kde.org/show_bug.cgi?id=358171 Seems that bug was build in again? But as root I can use breeze theme and all works fine with the desktop -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1002865 http://bugzilla.opensuse.org/show_bug.cgi?id=1002865#c3 --- Comment #3 from Andreas Bock <a_bock@gmx.de> --- additional hint: Today there were over 200 updates to version 20161003 nothing changed And I forgot additional repos: Packman with URL http://ftp.uni-erlangen.de/packman/suse/openSUSE_Tumbleweed/ and Mozilla with URL http://download.opensuse.org/repositories/mozilla/openSUSE_Tumbleweed/ Packman has Prio 98 all others 99 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1002865 http://bugzilla.opensuse.org/show_bug.cgi?id=1002865#c4 --- Comment #4 from Wolfgang Bauer <wbauer@tmo.at> --- (In reply to Andreas Bock from comment #2)
I tried all available selections icewm, twm, kodi kde5, kde plasma : they all bevave the same. After I enter the password I get that black screen with mouse.
Hm, that's strange. Then it's rather not a problem with all those desktops... Reminds me of bug#997294 though. Does the desktop appear if you press Ctrl+Alt+F1 (to switch to a text mode console) and then Ctrl+Alt+F7 to switch back?
Some googling showed me that: https://bugs.kde.org/show_bug.cgi?id=358171
Well, it doesn't sound exactly like your problem, but it may have a similar root (intel's SNA acceleration). So, does it work if you switch to a different sddm theme? E.g. set Theme=maui in /etc/sddm.conf. Are you using intel? If yes: Does it help to switch to the older (but more stable) UXA acceleration? https://en.opensuse.org/SDB:Switch_xf86-video-intel_to_UXA You may also try to disable the intel driver completely by adding "nomodeset" to the boot options (press 'e' at the boot menu and append "nomodeset" to the line starting with "linux" or "linuxefi", then press F10 to boot, this way it will only apply to the current boot and not permanently alter your system). Also maybe try to use the generic "modesetting" driver too, by just uninstalling xf86-video-intel. ("modesetting" will still use intel's OpenGL hardware support so you shouldn't loose much, actually it's reported to be more stable and even faster on some intel systems at least) The latter two suggestions would also apply to other (open source) drivers like nouveau or radeon (of course you should uninstall xf86-video-nouveau or xf86-video-ati then, not xf86-video-intel).
Seems that bug was build in again?
That bug was never fixed in Plasma/the breeze theme, as it was (is?) a bug in the intel graphics driver. intel didn't release a new driver in years though AFAIK, so distributions started shipping random git versions, that may have random bugs too.
But as root I can use breeze theme and all works fine with the desktop
Well, it's not a general problem with the breeze theme, it only happens with sddm as I understand it. So the question is if you can login via sddm as root... Root login is disabled by default though, you'd have to set MinimumUid=0 in /etc/sddm.conf (this will display all system users too though, Plasma 5.8's sddm theme will have an option to manually enter the user name as well). I suppose you will have the same problem then as when logging in as user. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1002865 http://bugzilla.opensuse.org/show_bug.cgi?id=1002865#c5 Andreas Bock <a_bock@gmx.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |NORESPONSE --- Comment #5 from Andreas Bock <a_bock@gmx.de> --- I didn't see, that that was a intel bug. I don't use Intel hardwarem I use AMD and Nvidia. Yesterdays update to 20161003 must have fixed it. I haven't realized that, because the lockd on my nfs server had crashed :-( (yes the files were accessible) After a reboot of that machine everything worked fine again. Thank you for your help! -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1002865 http://bugzilla.opensuse.org/show_bug.cgi?id=1002865#c6 Wolfgang Bauer <wbauer@tmo.at> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|NORESPONSE |WORKSFORME Flags|needinfo?(a_bock@gmx.de) | --- Comment #6 from Wolfgang Bauer <wbauer@tmo.at> --- (In reply to Andreas Bock from comment #5)
Yesterdays update to 20161003 must have fixed it. I haven't realized that, because the lockd on my nfs server had crashed :-( (yes the files were accessible) After a reboot of that machine everything worked fine again.
Oh. But thanks for the status update. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com