Bug 173651 - KPackageKit crashed and caused the signal 6 (SIGABRT).
Summary: KPackageKit crashed and caused the signal 6 (SIGABRT).
Status: RESOLVED NOT A BUG
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: Mandriva RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-10-27 01:44 UTC by Stewart
Modified: 2009-02-01 16:49 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stewart 2008-10-27 01:44:07 UTC
Version:            (using KDE 4.1.1)
OS:                Linux
Installed from:    Mandriva RPMs

kpackagekit crashes every time Mandriva One starts up,and will crash at least
2 more times with in 3-4 minutes. After that it will not crash intill next start up.

Backtrace:Application: KPackageKit (kpackagekit), signal SIGABRT
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb5f4f6d0 (LWP 11823)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6  0xffffe430 in __kernel_vsyscall ()
#7  0xb6c12d90 in raise () from /lib/i686/libc.so.6
#8  0xb6c147f8 in abort () from /lib/i686/libc.so.6
#9  0xb6341795 in ?? () from /lib/libdbus-1.so.3
#10 0xb633cf31 in ?? () from /lib/libdbus-1.so.3
#11 0xb6326224 in dbus_set_error () from /lib/libdbus-1.so.3
#12 0xb635b0dc in ?? () from /usr/lib/libpolkit-dbus.so.2
#13 0xb635b354 in polkit_auth_obtain () from /usr/lib/libpolkit-dbus.so.2
#14 0xb6e52ed7 in PackageKit::PolkitClient::getAuth ()
   from /usr/lib/libpackagekit-qt.so.2
#15 0xb6e39bec in PackageKit::Client::updatePackages ()
   from /usr/lib/libpackagekit-qt.so.2
#16 0x08050ec4 in _start ()
Comment 1 Bram Schoenmakers 2008-10-27 19:50:54 UTC
We don't handle KPackageKit bugs, please refer to this page instead: http://www.packagekit.org/pk-bugs.html
Comment 2 boziercan 2009-02-01 16:45:56 UTC
Same bug was happened three times when my home index was open and I was passing up/down of next indexes.
Comment 3 boziercan 2009-02-01 16:49:16 UTC
Same bug was happened three times when my home index was open and I was passing up/down of next indexes. 

LINUX
O.S: PARDUS 2008
Version:KDE 3.5.10