Summary: | When selecting Leave and then Switch User in the kde menu there is no list of users but instead a run dialog is shown | ||
---|---|---|---|
Product: | [Unmaintained] plasma4 | Reporter: | Rik <rfe.gen> |
Component: | general | Assignee: | Plasma Bugs List <plasma-bugs> |
Status: | RESOLVED DUPLICATE | ||
Severity: | wishlist | CC: | danxuliu, rdieter |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Rik
2008-07-19 11:50:36 UTC
*** Bug 167024 has been marked as a duplicate of this bug. *** Can someone please explain what the consequences of changing Severity from 'normal' to 'wishlist' are ??? Or maybe even better... send me a link to information on the subject of bug classification that is used here. Thank you. I don't think there are any consequences, per se. it just helps developers to sort the reports. I think wishlist items are unlikely to be worked on during a feature freeze (which we won't have for a few months)... but even that isn't always the case ;) with fc9 and KDE 4.1.0 "switch user" simply locks the current user out, exactly like "lock". I can confirm, that "switch user" does not provide a dialog with which you can start a new session how it used to work in kde 3.5. I really miss this feature. and yet i use this feature at least weekly, sometimes several times a week. i know this works in trunk due to that; please report this upstream. I opened a bug for fedora 9 https://bugzilla.redhat.com/show_bug.cgi?id=458616 works fine here too (... I cannot reproduce the problem anyway) problem solved Solution: make sure you use kdm and NOT gdm ;) I see, This seems to solve the problem and thus indeed WORKSFORME as well. Rik Forgot to say thanks to Martin, For I now also (think I) understand now what reporting upstream means... |-) This got implemented for GDM in kdebase-workspace trunk (for 4.6) now, see bug 186198. *** This bug has been marked as a duplicate of bug 186198 *** |