[Bug 196663] New: PolicyKit-kde crashed when running Updater Applet (yast?)

johnb_atl M8R-3a63cd at mailinator.com
Mon Jun 15 20:50:19 BST 2009


https://bugs.kde.org/show_bug.cgi?id=196663

           Summary: PolicyKit-kde crashed when running Updater Applet
                    (yast?)
           Product: kde
           Version: unspecified
          Platform: SuSE RPMs
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: general
        AssignedTo: unassigned-bugs at kde.org
        ReportedBy: M8R-3a63cd at mailinator.com


Version:            (using KDE 4.1.3)
OS:                Linux
Installed from:    SuSE RPMs

To reproduce:
1. Started updater applet from main panel in kde4.  2. Canceled updater before
it was finished.
3. Restarted updater applet as in #1.
4. PolicyKit-kde crashed and raised SIGABRT.

BACKTRACE INCLUDED BELOW:
-------------------------------
Application: PolicyKit-kde (policykit-kde), signal SIGABRT
[Current thread is 1 (Thread 0xb61ae750 (LWP 23151))]

Thread 2 (Thread 0xb4790b90 (LWP 23567)):
#0  0xffffe430 in __kernel_vsyscall ()
#1  0xb6581411 in select () from /lib/libc.so.6
#2  0x08055175 in _start ()

Thread 1 (Thread 0xb61ae750 (LWP 23151)):
[KCrash Handler]
#6  0xffffe430 in __kernel_vsyscall ()
#7  0xb64e1990 in raise () from /lib/libc.so.6
#8  0xb64e32c8 in abort () from /lib/libc.so.6
#9  0xb64a1245 in ?? () from /lib/libdbus-1.so.3
#10 0xb649cc59 in ?? () from /lib/libdbus-1.so.3
#11 0xb648dc6c in dbus_message_set_error_name () from /lib/libdbus-1.so.3
#12 0xb67a2a50 in ?? () from /usr/lib/libQtDBus.so.4
#13 0xb6798288 in ?? () from /usr/lib/libQtDBus.so.4
#14 0xb678a5e9 in QDBusConnection::send(QDBusMessage const&) const () from
/usr/lib/libQtDBus.so.4
#15 0xb67cdc24 in QDBusContext::sendErrorReply(QString const&, QString const&)
const () from /usr/lib/libQtDBus.so.4
#16 0x080535b1 in _start ()

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the Unassigned-bugs mailing list