Bug 293959 - In multiseat configuration apper fails to obtain authentication
Summary: In multiseat configuration apper fails to obtain authentication
Status: RESOLVED WAITINGFORINFO
Alias: None
Product: apper
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Daniel Nicoletti
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-13 04:08 UTC by kde
Modified: 2013-01-08 20:58 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description kde 2012-02-13 04:08:24 UTC
Version:           unspecified (using KDE 4.8.0) 
OS:                Linux

I am running 3 seat multiseat configuration. On the 2nd and 3rd seat when running apper to update the system, apper never pops up the dialog to select user and provide password to update the system. Instead when I select to update the system, I get error dialog which says

You have failed to provide correct authentication. Please check any password and account settings. 

When I click on Details I see

Failed to obtain authentication.

I console i see

$ apper 
enumFromString ( Group ) : converted "unknown" to "UnknownGroup" , enum id 1 
enumFromString ( UpdateState ) : converted "unknown" to "UnknownUpdateState" , enum id 2 
enumFromString ( UpdateState ) : converted "unknown" to "UnknownUpdateState" , enum id 2 
enumFromString ( UpdateState ) : converted "unknown" to "UnknownUpdateState" , enum id 2 
enumFromString ( Role ) : converted "unknown" to "UnknownRole" , enum id 0 



Reproducible: Always

Steps to Reproduce:
On multiseat system run apper on seat 2 or 3 and try to update the system

Actual Results:  
It is impossible to update the system from apper because there is no way to provide authentication.

Expected Results:  
I should be able to update the system from any seat.

It is possible to update the system from console by running 

sudo apt-get upgrade

since it asks for my password just fine. It seems the issue is with the component asking for the authorization.
Comment 1 Daniel Nicoletti 2012-02-13 18:29:09 UTC
do you have policykit-kde running on each session?
Comment 2 Daniel Nicoletti 2013-01-08 20:58:17 UTC
I'm closing  due lack of information.