Bug 445880 - User is prompted for root password to logoff, reboot or halt the system
Summary: User is prompted for root password to logoff, reboot or halt the system
Status: RESOLVED DUPLICATE of bug 445408
Alias: None
Product: openSUSE 11.1
Classification: openSUSE
Component: KDE4 Workspace (show other bugs)
Version: Beta 5
Hardware: x86-64 openSUSE 11.1
: P5 - None : Major (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-11-18 03:14 UTC by Forgotten User CxVz4LpaB5
Modified: 2009-01-09 17:55 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Forgotten User CxVz4LpaB5 2008-11-18 03:14:27 UTC 
Like the title says, when the user wants to logoff, reboot or halt the system when he is logged a normal user, KDE prompts for the root password.
This is new in Beta5
Comment 1 Stephan Binner 2008-11-18 08:12:08 UTC 
Please read http://en.opensuse.org/Bugs:Most_Annoying_Bugs_11.1_dev

*** This bug has been marked as a duplicate of bug 445048 ***
Comment 2 Christoph Resch 2009-01-08 01:44:33 UTC 
i think looping back to the overview and closing is no status for this ticket .. i run OS 11.1 (latest) and feel very annoyed with this "feature" (as some may see it) .. in fact i fosted all yast and kde4 settings to disabled it .. no way so far :-( .. also check at many of them countless crossreferences about dups in other dups aso. that issue is called to be fixed .. but it isnt.. please at least somebody know how to disabled this .. thank you.. br c-:


kde4-kdm-4.1.3-10.1
Linux zion 2.6.27.7-9-default #1 SMP 2008-12-04 18:10:04 +0100 x86_64 x86_64 x86_64 GNU/Linux
Comment 3 Christoph Resch 2009-01-08 01:47:14 UTC 
yes - just because
Comment 4 JP Rosevear 2009-01-09 17:55:23 UTC 
I don't see any reason for this not to be marked as a duplicate in #2 - if the root cause is the same the developers can definitely mark it as a dupe other wise bug list monitoring is impossible.

*** This bug has been marked as a duplicate of bug 445408 ***