Bug 289114 - no way to enter apper password
Summary: no way to enter apper password
Status: RESOLVED DUPLICATE of bug 290166
Alias: None
Product: Active
Classification: Unmaintained
Component: Top Bar (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR normal
Target Milestone: unscheduled
Assignee: active
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-16 13:31 UTC by Carl Symons
Modified: 2012-02-28 11:02 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Carl Symons 2011-12-16 13:31:56 UTC
Version:           unspecified (using KDE 4.7.3) 
OS:                Linux

Apper icon appeared in topbar. Clicking button to apply updates brings up authorization prompt. Touching in the text box to enter does not launch keyboard. This makes Apper work as an update notifier, but useless as a full update tool. 

Reproducible: Didn't try

Steps to Reproduce:
apper appeared in Plasma Active top bar and reported that updates were available. When apper updates didn't work, zypper dup. 

Actual Results:  
apper called for password. Unable to provide it without onscreen keyboard. Didn't make sense to hook up external keyboard. Terminal updates worked fine. 

Expected Results:  
Apper authorization would launch keyboard

I think that Terminal + zypper dup isn't the best way for most people to do updates. Apper is a good idea for the less technical user. It should work all the way through to completion.
Comment 1 Lamarque V. Souza 2011-12-17 20:09:26 UTC
Which image are you using? I am using basyskom-plasma-active-two-meego-usb-live.iso and it tries to install the updates without asking for authorization.
Comment 2 Carl Symons 2011-12-20 14:25:10 UTC
I am using the Balsam openSUSE 12.1 image, downloaded from open-slx
Comment 3 Lamarque V. Souza 2012-02-28 11:02:11 UTC
Marking as duplicate because #290166 contains more useful information about this bug.

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