Mailinglist Archive: opensuse-kde (352 mails)

< Previous Next >
Re: [opensuse-kde] Apper in openSUSE 12.1?
  • From: todd rme <toddrme2178@xxxxxxxxx>
  • Date: Tue, 11 Oct 2011 13:37:58 +0200
  • Message-id: <>
On Tue, Oct 11, 2011 at 1:34 PM, Graham Anderson
<graham.anderson@xxxxxxxxx> wrote:
On Tuesday 11 Oct 2011 12:25:42 Raymond Wooninck wrote:
The package should be available in
the next hour and I would appreciate feedback on missing translations and
other issues people are experiencing.

For me Apper 0.7.0 from KDF is usable but annoying,

System Settings -> Software Management -> Updates

Now I am prompted for a root login with:

"Authentication is required to set the network proxy used for downloading

This does not repsect my KDE network proxy settings which are: "Connect to the
Internet directly"

I shouldn't be seeing this request at all. So I cancel this root auth request,
and now packagekitd seems to hang in some loop while slowly consuming RAM
until it's killed.

Additionally, If I ignore the request, the request dialogue will eventually

If I continue in the update workflow by entering my root auth in the proxy
settings request, the list of updates are shown. I can then select the updates
I want and an entering another root auth to install them the installation
procceeds successfully.

If I perform an update workflow using the Apper systray icon, I experience the
same issue with an extraaneous request to set my proxy settings in addition to
the request to auth for the actuall update; but the update does at least
process and is successfull.

Additionally, the KDE polkit auth agent segfaulted when I relogged to test the
update from systray applet workflow, I don't have symbols installed but here's
the trace anyway:

Application: PolicyKit1-KDE (polkit-kde-authentication-agent-1), signal:
Segmentation fault
[Current thread is 1 (Thread 0x7fbc368ce800 (LWP 6822))]

Thread 3 (Thread 0x7fbc26c8e700 (LWP 6860)):
#0  0x00007fbc33dfb133 in poll () from /lib64/
#1  0x00007fbc31773a38 in ?? () from /usr/lib64/
#2  0x00007fbc31774262 in g_main_loop_run () from /usr/lib64/
#3  0x00007fbc3125a7d6 in ?? () from /usr/lib64/
#4  0x00007fbc31798d56 in ?? () from /usr/lib64/
#5  0x00007fbc31e9df05 in start_thread () from /lib64/
#6  0x00007fbc33e0424d in clone () from /lib64/

Thread 2 (Thread 0x7fbc26463700 (LWP 7356)):
#0  0x00007fbc33dd2c5d in nanosleep () from /lib64/
#1  0x00007fbc3179c172 in g_usleep () from /usr/lib64/
#2  0x00007fbc3176f7cc in ?? () from /usr/lib64/
#3  0x00007fbc31798d56 in ?? () from /usr/lib64/
#4  0x00007fbc31e9df05 in start_thread () from /lib64/
#5  0x00007fbc33e0424d in clone () from /lib64/

Thread 1 (Thread 0x7fbc368ce800 (LWP 6822)):
[KCrash Handler]
#6  0x00007fbc3150f840 in g_type_check_instance_is_a () from
#7  0x00007fbc314ee1ed in g_object_unref () from
#8  0x00007fbc30d7be1a in ?? () from /usr/lib64/
#9  0x00007fbc314ee310 in g_object_unref () from
#10 0x00007fbc35c4de64 in PolkitQt1::Agent::Session::~Session() () from
#11 0x00007fbc35c4dea9 in PolkitQt1::Agent::Session::~Session() () from
#12 0x00007fbc351d9fd8 in QObject::event(QEvent*) () from
#13 0x00007fbc34593be4 in QApplicationPrivate::notify_helper(QObject*,
QEvent*) () from /usr/lib64/
#14 0x00007fbc34598a71 in QApplication::notify(QObject*, QEvent*) () from
#15 0x00007fbc362b2de6 in KApplication::notify(QObject*, QEvent*) () from
#16 0x00007fbc351c367c in QCoreApplication::notifyInternal(QObject*, QEvent*)
() from /usr/lib64/
#17 0x00007fbc351c6a58 in QCoreApplicationPrivate::sendPostedEvents(QObject*,
int, QThreadData*) () from /usr/lib64/
#18 0x00007fbc351c6c7e in QCoreApplication::exec() () from
#19 0x0000000000408e3e in ?? ()
#20 0x00007fbc33d4c23d in __libc_start_main () from /lib64/
#21 0x0000000000408ea5 in _start ()

So yeah it's a bit annoying to use with the double auth request, but at least
the updates actually work.


Are you using 11.4? The proxy authentication issue is a problem with
policykit rather than apper. Policykit should not ask for a password
for this, but it does (at least for 11.4, I haven't seen the issue in

To unsubscribe, e-mail: opensuse-kde+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-kde+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups