Apport needs administrator privileges when screen saver has locked the screen (password)

[A.H.M. Donkers]

Binary package hint: apport

When the screen saver has locked the screen and a password is required to unlock it, apport displays a dialog 'administrative privileges needed'. This dialog is not accessible because of the screen saver lock; the screen saver cannot be unlocked because of the dialog...

The only way to get out is to use e.g. CTRL &ALT & F1 or a network login, to get a command prompt, and kill the apport process responsible for the dialog.

[A.H.M. Donkers (a-h-m-donkers)]

Intrepid beta

Linux vapulo 2.6.27-7-generic #1 SMP Fri Oct 17 22:24:30 UTC 2008 x86_64 GNU/Linux

Linux version 2.6.27-7-generic (buildd@crested) (gcc version 4.3.2 (Ubuntu 4.3.2-1ubuntu10) ) #1 SMP Fri Oct 17 22:24:30 UTC 2008

root@vapulo:~# dpkg -l *apport*
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name Version Description
+++-=========================-=========================-==================================================================
ii apport 0.117 automatically generate crash reports for debugging
un apport-cli <none> (no description available)
un apport-gtk <none> (no description available)
ii apport-qt 0.117 Qt4 frontend for the apport crash report system
un apport-retrace <none> (no description available)
ii python-apport 0.117 apport crash report handling library
un python-apport-utils <none> (no description available)
root@vapulo:~#

[Martin Pitt (pitti)]

Can you please describe exactly how you got into this situation? apport doesn't automatically bring up that "admin priv needed" dialog, you have to click on the crash icon in the panel tray. Did you do that, and lock your screen at the same time or so?

[Sebastien Bacher (seb128)]

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.