(In reply to comment #0)
> Application: apper-sentinel (0.7.1)
> KDE Platform Version: 4.7.3 (4.7.3)
> Qt Version: 4.8.0
> Operating System: Linux 3.1.5-1.fc16.x86_64 x86_64
> Distribution: "Fedora release 16 (Verne)"
> 
> -- Information about the crash:
> - What I was doing when the application crashed:
> I was sleeping.  Previously, I had about 20 SeaMonkey Suite windows open, with
> one sending streaming video
               ^^^ "streaming audio" 
> from the BBC.  A few small KWrite or gedit editing windows.  
> 
> The crash report mentions a segmentation fault in Apper-Sentinel for a Shared
> Object (*so* file)
> is ?/lib64/    .   I've found that "/sbin/ldconfig - configure dynamic linker
> run-time bindings"
> may be the right way to fix things.  However, I don't fully understand
> `/sbin/ldconfig', and
> for random software I install (e.g. the MPFR math library), I just (as root)
> examine shared
> objects and sylinks and with luck, can fix the Shared Object (*.so.*) problem
               ^^^  symlinks
> ...

I have a wish for Apper debugging:  I had to install debugging packages
to generate the backtrace.  I was logged in as a non-privileged user (not root).

I was then prompted for a password.  The correct password in this case
was root's password, not the unprivileged user `david'.  My wish is for
a user, when required to install debuggings tools in the context of
an ApperSentinel crash, to be informed something like: 
"please enter root's password" .  This requirement is something 
that I guessed .  David Bernier



> 
> -- Backtrace:
> Application: Apper (apper-sentinel), signal: Segmentation fault
> Using host libthread_db library "/lib64/libthread_db.so.1".
> 82    T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
> [KCrash Handler]
> #6  TransactionWatcher::isRunning (this=0x27c63a0) at
> /usr/src/debug/apper-0.7.1/Sentinel/TransactionWatcher.cpp:390
> #7  0x000000000042c63d in ApperSentinel::isRunning (this=0x7fffa9d02fb0) at
> /usr/src/debug/apper-0.7.1/Sentinel/ApperSentinel.cpp:99
> #8  0x000000000042c8f6 in ApperSentinel::prepareToClose (this=0x7fffa9d02fb0)
> at /usr/src/debug/apper-0.7.1/Sentinel/ApperSentinel.cpp:87
> #9  0x00007f124b4e77d1 in QMetaObject::activate (sender=0x27caa30, m=<optimized
> out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3546
> #10 0x000000000041514c in AbstractIsRunning::decreaseRunning (this=0x27caa30)
> at /usr/src/debug/apper-0.7.1/Sentinel/AbstractIsRunning.cpp:47
> #11 0x00007f124b4e77d1 in QMetaObject::activate (sender=0x2759d40, m=<optimized
> out>, local_signal_index=<optimized out>, argv=0x7fffa9d01b60) at
> kernel/qobject.cpp:3546
> #12 0x00007f124bf3f25f in PackageKit::Transaction::finished (this=<optimized
> out>, _t1=PackageKit::Transaction::ExitSuccess, _t2=590) at transaction.moc:591
> #13 0x00007f124bf39e6a in PackageKit::TransactionPrivate::finished
> (this=<optimized out>, exitCode=<optimized out>, runtime=590) at
> transactionprivate.cpp:116
> #14 0x00007f124b4e77d1 in QMetaObject::activate (sender=0x2721d80, m=<optimized
> out>, local_signal_index=<optimized out>, argv=0x7fffa9d01cf0) at
> kernel/qobject.cpp:3546
> #15 0x00007f124bf33df6 in TransactionProxy::Finished (this=<optimized out>,
> _t1=<optimized out>, _t2=590) at transactionproxy.moc:414
> #16 0x00007f124bf36129 in TransactionProxy::qt_static_metacall (_o=0x2721d80,
> _c=<optimized out>, _id=8, _a=0x7fffa9d02580) at transactionproxy.moc:198
> #17 0x00007f124bf36f0f in TransactionProxy::qt_metacall (this=0x2721d80,
> _c=QMetaObject::InvokeMetaMethod, _id=8, _a=0x7fffa9d02580) at
> transactionproxy.moc:317
> #18 0x00007f124bccaccb in QDBusConnectionPrivate::deliverCall (this=0x27af400,
> object=0x2721d80, msg=..., metaTypes=..., slotIdx=13) at
> qdbusintegrator.cpp:947
> #19 0x00007f124b4ec9e6 in QObject::event (this=0x2721d80, e=<optimized out>) at
> kernel/qobject.cpp:1194
> #20 0x00007f1249f896f4 in notify_helper (e=0x293ab30, receiver=0x2721d80,
> this=0x2625ec0) at kernel/qapplication.cpp:4518
> #21 QApplicationPrivate::notify_helper (this=0x2625ec0, receiver=0x2721d80,
> e=0x293ab30) at kernel/qapplication.cpp:4490
> #22 0x00007f1249f8e573 in QApplication::notify (this=0x7fffa9d02fb0,
> receiver=0x2721d80, e=0x293ab30) at kernel/qapplication.cpp:4379
> #23 0x00007f124cb3f396 in KApplication::notify (this=0x7fffa9d02fb0,
> receiver=0x2721d80, event=0x293ab30) at
> /usr/src/debug/kdelibs-4.7.3/kdeui/kernel/kapplication.cpp:311
> #24 0x00007f124b4d3b4c in QCoreApplication::notifyInternal
> (this=0x7fffa9d02fb0, receiver=0x2721d80, event=0x293ab30) at
> kernel/qcoreapplication.cpp:876
> #25 0x00007f124b4d75da in sendEvent (event=0x293ab30, receiver=0x2721d80) at
> kernel/qcoreapplication.h:231
> #26 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0,
> data=0x25fb070) at kernel/qcoreapplication.cpp:1500
> #27 0x00007f124b502403 in sendPostedEvents () at kernel/qcoreapplication.h:236
> #28 postEventSourceDispatch (s=0x262a750) at
> kernel/qeventdispatcher_glib.cpp:279
> #29 0x00007f124461ca7d in g_main_context_dispatch () from
> /lib64/libglib-2.0.so.0
> #30 0x00007f124461d278 in ?? () from /lib64/libglib-2.0.so.0
> #31 0x00007f124461d44c in g_main_context_iteration () from
> /lib64/libglib-2.0.so.0
> #32 0x00007f124b50282f in QEventDispatcherGlib::processEvents (this=0x25fc530,
> flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:424
> #33 0x00007f124a02c43e in QGuiEventDispatcherGlib::processEvents
> (this=<optimized out>, flags=<optimized out>) at
> kernel/qguieventdispatcher_glib.cpp:207
> #34 0x00007f124b4d2c82 in QEventLoop::processEvents (this=<optimized out>,
> flags=...) at kernel/qeventloop.cpp:149
> #35 0x00007f124b4d2ed7 in QEventLoop::exec (this=0x7fffa9d02f40, flags=...) at
> kernel/qeventloop.cpp:204
> #36 0x00007f124b4d78d5 in QCoreApplication::exec () at
> kernel/qcoreapplication.cpp:1148
> #37 0x000000000040f24d in main (argc=1, argv=0x7fffa9d03298) at
> /usr/src/debug/apper-0.7.1/Sentinel/main.cpp:54
> 
> Reported using DrKonqi

> My wish is for a user, when required to install debuggings tools in
> the context of an ApperSentinel crash, to be informed something like:
> "please enter root's password"

Rex, is this handled by policykit?

Not policykit-based, just a mostly horrible distro-specific script (from drkonqi) to run debuginfo-install

See drkonqi/doc/examples/installdbgsymbols_fedora.sh 

Come to think of it, seems replacing
run_in_terminal "su -c \"debuginfo-install $packages\""
with something like
run_in_terminal "pkexec \"debuginfo-install $packages\""
would likely be a good first step.

Created attachment 70216 [details]
New crash information added by DrKonqi

apper-sentinel (0.7.0) on KDE Platform 4.8.2 (4.8.2) using Qt 4.8.1

- What I was doing when the application crashed:

Meanwhile, the system updater detected pending updates.

-- Backtrace (Reduced):
#6  TransactionWatcher::isRunning (this=0x86aa30) at /usr/src/debug/apper-0.7.0/Sentinel/TransactionWatcher.cpp:390
#7  0x000000000042da1d in ApperSentinel::isRunning (this=0x7fff8d635db0) at /usr/src/debug/apper-0.7.0/Sentinel/ApperSentinel.cpp:99
#8  0x000000000042dcd6 in ApperSentinel::prepareToClose (this=0x7fff8d635db0) at /usr/src/debug/apper-0.7.0/Sentinel/ApperSentinel.cpp:87
#9  0x000000000042e250 in ApperSentinel::qt_metacall (this=0x7fff8d635db0, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=<optimized out>) at /usr/src/debug/apper-0.7.0/build/Sentinel/ApperSentinel.moc:73
[...]
#11 0x00000000004162ac in AbstractIsRunning::decreaseRunning (this=0x86eb90) at /usr/src/debug/apper-0.7.0/Sentinel/AbstractIsRunning.cpp:47

Yeah, I definitively need to add DrKonqi support for Apper,
so that it installs packages asking user password...

2012/4/7 Christopher Yeleighton <giecrilj@stegny.2a.pl>:
> https://bugs.kde.org/show_bug.cgi?id=288973
>
> --- Comment #4 from Christopher Yeleighton <giecrilj@stegny.2a.pl> ---
> Created attachment 70216 [details]
>  --> https://bugs.kde.org/attachment.cgi?id=70216&action=edit
> New crash information added by DrKonqi
>
> apper-sentinel (0.7.0) on KDE Platform 4.8.2 (4.8.2) using Qt 4.8.1
>
> - What I was doing when the application crashed:
>
> Meanwhile, the system updater detected pending updates.
>
> -- Backtrace (Reduced):
> #6  TransactionWatcher::isRunning (this=0x86aa30) at
> /usr/src/debug/apper-0.7.0/Sentinel/TransactionWatcher.cpp:390
> #7  0x000000000042da1d in ApperSentinel::isRunning (this=0x7fff8d635db0) at
> /usr/src/debug/apper-0.7.0/Sentinel/ApperSentinel.cpp:99
> #8  0x000000000042dcd6 in ApperSentinel::prepareToClose (this=0x7fff8d635db0)
> at /usr/src/debug/apper-0.7.0/Sentinel/ApperSentinel.cpp:87
> #9  0x000000000042e250 in ApperSentinel::qt_metacall (this=0x7fff8d635db0,
> _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=<optimized out>) at
> /usr/src/debug/apper-0.7.0/build/Sentinel/ApperSentinel.moc:73
> [...]
> #11 0x00000000004162ac in AbstractIsRunning::decreaseRunning (this=0x86eb90) at
> /usr/src/debug/apper-0.7.0/Sentinel/AbstractIsRunning.cpp:47
>
> --
> You are receiving this mail because:
> You are the assignee for the bug.

Can you still reproduce it using Apper 0.7.2? I can't tell what's wrong from the backtrace.