Bug 294845

Summary: polkit-kde silently ignores authentication requests
Product: [Plasma] policykit-kde-agent-1 Reporter: Jakub Schmidtke <sjakub>
Component: generalAssignee: Jaroslav Reznik <jreznik>
Status: CONFIRMED ---    
Severity: normal CC: mbriza, sitter, sjakub, thomas.luebking
Priority: NOR    
Version: 5.5.4   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:

Description Jakub Schmidtke 2012-02-26 07:00:34 UTC 
Version:           unspecified (using KDE 4.8.0) 
OS:                Linux

I just installed apper, and I am unable to install any new packages using it.
It just says "Waiting for authentication", and stays like that for a long time.
I started investigating further, and when I try to install anything using
pkcon from packagekit the same thing happens - it just says
"Waiting for authentication", shows a moving progress bar
and nothing else happens.
When I kill /usr/lib/kde4/libexec/polkit-kde-authentication-agent-1,
run /usr/lib/polkit-gnome/polkit-gnome-authentication-agent-1
and try to use pkcon again, the authentication dialog pops up
and I am able to authenticate.
Can anybody confirm whether it's a problem with my setup,
or the polkit-kde is simply broken?
I'm running these versions of relevant packages:
dbus 1.4.16-1
dbus-core 1.4.16-1
dbus-glib 0.98-1
dbus-python 0.84.0-1
kdelibs 4.8.0-3
kdebase-workspace 4.8.0-2
polkit 0.104-1
polkit-gnome 0.105-1
polkit-kde 0.99.0-2
polkit-qt 0.103.0-1packagekit 0.6.21-2
packagekit-qt2 0.6.21-2
apper 0.7.1-2


Reproducible: Always

Steps to Reproduce:
run 'pkcon install package'


Actual Results:  
pkcon waits for authentication and doesn't get it, nothing shows up, no popup windows, no activity visible

Expected Results:  
dialog window shows up, asking for password
Comment 1 Jakub Schmidtke 2012-02-28 07:27:18 UTC 
I figured out what was wrong.
I had QT_NO_GLIB=1 set in the environment (in /etc/profile.d/ script).

I still think that this is an issue.
If it is impossible to get polkit agent working without glib loop events,
then it should not run at all. Or at the very least display an error...
Comment 2 Jakub Schmidtke 2012-02-28 07:28:36 UTC 
(In reply to comment #1)
> I figured out what was wrong.
> I had QT_NO_GLIB=1 set in the environment (in /etc/profile.d/ script).

I meant that unseting QT_NO_GLIB makes the problem go away.
Comment 3 Martin Bříza 2013-03-27 12:42:36 UTC 
Confirming, it ignores impossibility to authenticate silently when QT_NO_GLIB is set.
Comment 4 Thomas Lübking 2016-02-17 12:44:02 UTC 
*** Bug 334009 has been marked as a duplicate of this bug. ***
Comment 5 Thomas Lübking 2016-02-17 12:49:45 UTC 
simply needs
   setenv("QT_NO_GLIB", "0", true);
before creating the Q*Application instance (in main.cpp or however the source is organized)
Comment 6 Justin Zobel 2021-03-09 07:30:33 UTC 
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.