[Bug 1081469] New: tumbleweed/4.15.4-1.g7169cf1-default/KDE4: user change failing, program start only with konsole
http://bugzilla.opensuse.org/show_bug.cgi?id=1081469 Bug ID: 1081469 Summary: tumbleweed/4.15.4-1.g7169cf1-default/KDE4: user change failing, program start only with konsole Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: SUSE Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE Workspace (Plasma) Assignee: opensuse-kde-bugs@opensuse.org Reporter: kohlhz@unity-mail.de QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:58.0) Gecko/20100101 Firefox/58.0 Build Identifier: Tumbleweed with all updates. Situation: After Energieverwaltung/Sitzung > Benutzer wechseln but the following new login is using the same login name. The login seems to be successful, but then: it's impossible to log out, change user, start a new program or shut down / reboot is only possible using a command shell (if one is open!) Reproducible: Always Steps to Reproduce: 1. select Energieverwaltung/Sitzung > Benutzer wechseln 2. login to same user than before 3. use the Kontrollleiste to try to start a user / logout / reboot Actual Results: strictly reproducible. When the login is using another user name, all is working correctly Expected Results: login to original job -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1081469 http://bugzilla.opensuse.org/show_bug.cgi?id=1081469#c1 Wolfgang Bauer <wbauer@tmo.at> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |wbauer@tmo.at Resolution|--- |DUPLICATE --- Comment #1 from Wolfgang Bauer <wbauer@tmo.at> --- First of all, there is no "KDE4". I suppose you are talking about KDE Plasma 5, that's the only KDE desktop we currently support/ship. But, logging in to a KDE session twice with the same user is not supported and doesn't work (since years, even in KDE4 times already). *** This bug has been marked as a duplicate of bug 1008105 *** -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1081469 http://bugzilla.opensuse.org/show_bug.cgi?id=1081469#c2 --- Comment #2 from Heinz Kohl <kohlhz@unity-mail.de> --- Wolfgang Bauer is writing: "But, logging in to a KDE session twice with the same user is not supported and doesn't work (since years, even in KDE4 times already)." I'm knowing that, but there's a crucial difference to bug http://bugzilla.opensuse.org/show_bug.cgi?id=1008105: In all former times, when by accident I tried to open a new session with the same user, the old session is reopened. That's the expected behavior. But here the reaction is a break down of system functionality. Additionally, it's very easy to accidently get this situation. In my case, it's enough not to select the root user before submitting a password. I think, it should be obvious, that a simple typing error shouldn't make an operating system impotent. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1081469 http://bugzilla.opensuse.org/show_bug.cgi?id=1081469#c3 --- Comment #3 from Wolfgang Bauer <wbauer@tmo.at> --- (In reply to Heinz Kohl from comment #2)
In all former times, when by accident I tried to open a new session with the same user, the old session is reopened. That's the expected behavior.
Sorry, but that's just not true. At least kdm always opened a *new* session if you logged in as an already logged in user (unless you explicitly chose "Switch User" in the menu on the *login screen*). No idea what others like gdm or lightdm do, but that's rather irrelevant here. Anyway, what you describe still is what bug#1008105 is about (i.e. there is *no* crucial difference IMHO). And there are basically two ways to "solve" it: - Prevent a second login (either by switching to the existing session, or aborting with an error message) - Make two simultaneous logins work The latter would mean a total rewrite of the desktop (and/or underlying libraries) though, and is unlikely to happen IMHO. But, SDDM (which we use by default for a KDE installation meanwhile) probably will gain the feature to reopen the running session if you choose an already logged in user at some point, but it's not in any released version yet. https://github.com/sddm/sddm/pull/730 The latter would mean a total rewrite of the desktop (and/or underlying libraries) though, and is unlikely to happen IMHO.
Additionally, it's very easy to accidently get this situation. In my case, it's enough not to select the root user before submitting a password.
How does the root user come into play here? That's not even displayed by default (in SDDM at least). And if you enter a wrong password (or the password of a different user), you should not be logged in a second time anyway. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1081469 http://bugzilla.opensuse.org/show_bug.cgi?id=1081469#c4 --- Comment #4 from Heinz Kohl <kohlhz@unity-mail.de> --- I've checked the situation with my old PC, an AMD Athlon Monoprocessor under Tumbleweed (always kernel 4.14.3-1-default) and Lubuntu. Tumbleweed, after "Benutzer wechseln" without changing owner: Plasma functionality somewhat restricted - "Benutzer wechseln" and logout impossible. All other desktop functionality is o.k. Therefore shutdown is possible by starting and using a command shell. No change of this behavior after updating Tumbleweed. New PC, AMD Ryzen 7, tumbleweed, before and after upgrading to newest updates including 4.15.4-1.g7169cf1-default: after "Benutzer wechseln" without changing owner: no plasma functionality beside mouse button operation. That's maybe the same base error, but the follow up problems are much greater. A simple change for the login procedure - e.g. an error message! - could correct the situation. ------------ To allow more than one indepently running dialog- and batch logins for one user was standard in ancient operating systems like TNS440 (1971-1982), but seems to be nearly impossible for Unix-like systems. For a proper working, it would set up the need to change the background memory management strategy, changing the use of temporary and non temporary memory. OpenSuSE installations: default is same password for root and first user. As a work around it's necessary to use different user names for just one user. It's all but far away to use the same password for all these users. P.S.: Lubuntu (lx session) is working correctly: reentering the actual session. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1081469 http://bugzilla.opensuse.org/show_bug.cgi?id=1081469#c5 --- Comment #5 from Wolfgang Bauer <wbauer@tmo.at> --- (In reply to Heinz Kohl from comment #4)
That's maybe the same base error, but the follow up problems are much greater.
A simple change for the login procedure - e.g. an error message! - could correct the situation.
Right. But I don't see the point in discussing that here. I marked this bug as duplicate, and I do still think it's the same problem. What you write doesn't change that assessment.
OpenSuSE installations: default is same password for root and first user.
That's true, but out of scope of this bug report, or anything that the openSUSE KDE team would decide. If you think that is a bug, please file a report against the Basesystem.
P.S.: Lubuntu (lx session) is working correctly: reentering the actual session.
They probably use a different display manager by default. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1081469 http://bugzilla.opensuse.org/show_bug.cgi?id=1081469#c6 --- Comment #6 from Wolfgang Bauer <wbauer@tmo.at> --- (In reply to Wolfgang Bauer from comment #5)
(In reply to Heinz Kohl from comment #4)
OpenSuSE installations: default is same password for root and first user.
That's true, but out of scope of this bug report, or anything that the openSUSE KDE team would decide.
If you think that is a bug, please file a report against the Basesystem.
Or rather Installation, sorry. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1081469 http://bugzilla.opensuse.org/show_bug.cgi?id=1081469#c7 --- Comment #7 from Heinz Kohl <kohlhz@unity-mail.de> --- My resume: Classical understanding of an error of unclear or interpretable origin: end product is failing -> it's a failure in the end product -> maker of the end product is (at least more) responsible for the failure (than the end user). I'm understanding your interpretation as: our team is making no failure -> our product is o.k., even when it's failing. Times are changing. If I had got such an error message a fifty years ago belonging to the software product I was responsible, I would have had to prove without doubt, that another developer is responsible for this error, and then send an error message to him. The greatest error I could have made would have been to send back an error message for the failing product of my employer back to an instance outside. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1081469 http://bugzilla.opensuse.org/show_bug.cgi?id=1081469#c8 --- Comment #8 from Wolfgang Bauer <wbauer@tmo.at> --- Two things: I don't get paid for this. I am wasting a lot of my spare time trying to improve things. And as already mentioned, I just marked it as duplicate. Again, I still don't see any reason why that was wrong. Yes, times are changing, and *openSUSE* is a community product, JFYI. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1081469 http://bugzilla.opensuse.org/show_bug.cgi?id=1081469#c9 --- Comment #9 from Heinz Kohl <kohlhz@unity-mail.de> --- The case is now opened as kscreenlocker bug https://bugs.kde.org/show_bug.cgi?id=390839 -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com