Bug 8664 - Authentication error when applying Login Screen options in KDE System Settings
Summary: Authentication error when applying Login Screen options in KDE System Settings
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-11 16:18 CET by Steve
Modified: 2013-01-11 21:36 CET (History)
0 users

See Also:
Source RPM:
CVE:
Status comment:


Attachments
Authentication error (16.53 KB, image/jpeg)
2013-01-11 16:19 CET, Steve
Details

Description Steve 2013-01-11 16:18:31 CET
Description of problem:
When using the KDE System Settings to modify options for the Login Screen (In the System Administration section) I always get an authentication error when I click to apply my changes, and the changes are not applied. I will attach a screenshot of the error.

When I start System Settings as root from a konsole:

[root@localhost ~]# systemsettings
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
kbuildsycoca4 running...

I see this after I've clicked the apply button:
[root@localhost ~]# false 
"Failed to execute program /usr/lib64/dbus-1/dbus-daemon-launch-helper: Success" 
"/org/freedesktop/UDisks2/drives/TSSTcorp_CDDVDW_SH_S203P" : property "Drive" does not exist

This is on a clean install of M3 Beta1 using the iso:
Mageia-3-beta1-LiveDVD-KDE4-x86_64-DVD.iso which I have kept fully updated and so now has the latest KDE version 4.9.97

I've searched the KDE Bug list but cannot see anything related to my issue.

How reproducible: Every time
Comment 1 Steve 2013-01-11 16:19:28 CET
Created attachment 3353 [details]
Authentication error
Comment 2 Steve 2013-01-11 21:36:18 CET
Well, I've been waiting since 21 Dec. to see if updates cure this bug and what do you know, I report the bug and 5 hours later I complete another update and the issue is resolved. Good work.

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.