Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#28052 - [gnome-packagekit] continually asking for root password

Attached to Project: Community Packages
Opened by Mike (asphantix) - Sunday, 22 January 2012, 17:26 GMT
Last edited by Jonathan Conder (PirateJonno) - Tuesday, 24 January 2012, 10:48 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Jonathan Conder (PirateJonno)
Architecture x86_64
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

1.) When I try to add software a popup will show which claims "the software is not from a trusted source".
2.) It's asking me whether I want to force the install and when I do so I have to type in my root pasword - and thats where the loop begins and it goes back to 1.)

I can't install anything. With pacman all is fine.

This task depends upon

Closed by  Jonathan Conder (PirateJonno)
Tuesday, 24 January 2012, 10:48 GMT
Reason for closing:  Fixed
Comment by Karol Błażewicz (karol) - Sunday, 22 January 2012, 17:57 GMT
What popup? What app are you using?
Comment by Mike (asphantix) - Sunday, 22 January 2012, 19:28 GMT
I'm talking about gpk-application (gnome-packagekit). I found out that apper (http://aur.archlinux.org/packages.php?ID=53061) has the same problem (see the comments).

I'm sorry that I missed to mention the package name in the ticket's title.
Comment by Jonathan Conder (PirateJonno) - Monday, 23 January 2012, 09:45 GMT
I know about this issue and think I have a fix, but I'm waiting for the next upstream packagekit release (which should be in a day or two) to package it. If you want the fix now, apply these two patches on top of the one already in the packagekit PKGBUILD:

https://gitorious.org/packagekit/packagekit/commit/521ca65e075c831f91cf6f20c466d7b497394dfd
https://gitorious.org/packagekit/packagekit/commit/1a44d2e0b493b334d9720d0b0e4ff3963a7f9dc3

The first one will allow you to use "SigLevel = Never" to avoid signature checking. The second will allow the force install option to work. However, if you see the force install dialogue it is probably because you haven't imported someone's key yet, so I suggest you use pacman from the command line (for now) to avoid seeing these messages in future.

In the future I intend to allow you to import signatures from within packagekit, but it is tricky because packagekit assumes this process works a bit differently than how alpm actually handles it.
Comment by Jonathan Conder (PirateJonno) - Tuesday, 24 January 2012, 02:05 GMT
should be fixed in packagekit 0.6.21-2
Comment by Mike (asphantix) - Tuesday, 24 January 2012, 09:45 GMT
I can confirm: Works like a charm now. many thanks!
Comment by Jonathan Conder (PirateJonno) - Tuesday, 24 January 2012, 10:48 GMT
Cool, no problem. Thanks for testing as I don't have much time at the moment. Please let me know if you find any other issues.

Loading...