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!
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!
FS#32744 - [apper] fails to update unless I run unless I use sudo via terminal
Attached to Project:
Community Packages
Opened by Nicholas Wenclaff (nwenclaff) - Sunday, 18 November 2012, 06:49 GMT
Last edited by Ike Devolder (BlackEagle) - Saturday, 01 December 2012, 23:50 GMT
Opened by Nicholas Wenclaff (nwenclaff) - Sunday, 18 November 2012, 06:49 GMT
Last edited by Ike Devolder (BlackEagle) - Saturday, 01 December 2012, 23:50 GMT
|
DetailsDescription:I recently updated my system with Pacman -Syu and it updated alot of packages....I believe the root of the issue is with polkit.
When I start Apper normnally (type apper in terminal just to see errors in background) it states the following: " QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. " when I select "Updates>>check for updates" a dialog box appears stating: "failed to obtain authentication" and the terminal states: " enumFromString ( Role ) : converted "unknown" to "UnknownRole" , enum id 0 " If I run as sudo Apper everything runs fine....this just started happening about 2 weeks ago. Additional info: * package version(s): apper-0.7.2-5-x86_64 * config and/or log files etc. Steps to reproduce: Install Apper, run via terminal, click updates, select check for updates. |
This task depends upon
Closed by Ike Devolder (BlackEagle)
Saturday, 01 December 2012, 23:50 GMT
Reason for closing: No response
Additional comments about closing: cant reproduce and no more response
Saturday, 01 December 2012, 23:50 GMT
Reason for closing: No response
Additional comments about closing: cant reproduce and no more response
I cannot reproduce the problem to state with a line a saw lately: "It works on my machine!"