Bug 267758 - apparent crash while upgrading from 10.04 to 10.10 (x64) but upgrade process still open
Summary: apparent crash while upgrading from 10.04 to 10.10 (x64) but upgrade process ...
Status: RESOLVED DUPLICATE of bug 225494
Alias: None
Product: kpackagekit
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Steven M. Parrish
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-03-06 04:09 UTC by catsailor
Modified: 2011-04-16 23:58 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description catsailor 2011-03-06 04:09:20 UTC
Application: kpackagekit (0.5.4)
KDE Platform Version: 4.4.5 (KDE 4.4.5)
Qt Version: 4.6.2
Operating System: Linux 2.6.31-14-generic x86_64
Distribution: Ubuntu 10.04.2 LTS

-- Information about the crash:
It was in process of getting new packages.  It indicated 99% complete, but appears to have started that process over again (i.e. is now, a few minutes after resuming the upgrade after the 'crash', only reporting 8% complete), but I'm not sure it is in exactly the same process.

 -- Backtrace:
Application: KPackageKit (kpackagekit), signal: Segmentation fault
[Current thread is 1 (Thread 0x7fab5733c760 (LWP 3971))]

Thread 2 (Thread 0x7fab4a75f700 (LWP 3984)):
#0  0x00007fff8a5d082c in clock_gettime ()
#1  0x00007fab5100509f in clock_gettime () from /lib/librt.so.1
#2  0x00007fab55c7599f in ?? () from /usr/lib/libQtCore.so.4
#3  0x00007fab55c7a6ad in ?? () from /usr/lib/libQtCore.so.4
#4  0x00007fab55c7a6d5 in ?? () from /usr/lib/libQtCore.so.4
#5  0x00007fab55c7875d in ?? () from /usr/lib/libQtCore.so.4
#6  0x00007fab55c78805 in ?? () from /usr/lib/libQtCore.so.4
#7  0x00007fab50d64eb1 in g_main_context_prepare () from /lib/libglib-2.0.so.0
#8  0x00007fab50d65318 in ?? () from /lib/libglib-2.0.so.0
#9  0x00007fab50d658fc in g_main_context_iteration () from /lib/libglib-2.0.so.0
#10 0x00007fab55c78566 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#11 0x00007fab55c4d992 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#12 0x00007fab55c4dd6c in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#13 0x00007fab55b57d59 in QThread::exec() () from /usr/lib/libQtCore.so.4
#14 0x00007fab55c2e178 in ?? () from /usr/lib/libQtCore.so.4
#15 0x00007fab55b5a775 in ?? () from /usr/lib/libQtCore.so.4
#16 0x00007fab542f59ca in start_thread () from /lib/libpthread.so.0
#17 0x00007fab538a470d in clone () from /lib/libc.so.6
#18 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7fab5733c760 (LWP 3971)):
[KCrash Handler]
#5  0x00007fab55c620a3 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4
#6  0x00007fab56686d2f in PackageKit::Transaction::finished(PackageKit::Transaction::ExitStatus, unsigned int) () from /usr/lib/libpackagekit-qt.so.12
#7  0x00007fab56682399 in PackageKit::ClientPrivate::serviceOwnerChanged(QString const&, QString const&, QString const&) () from /usr/lib/libpackagekit-qt.so.12
#8  0x00007fab56683e88 in PackageKit::ClientPrivate::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libpackagekit-qt.so.12
#9  0x00007fab55c61e3f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4
#10 0x00007fab5644d09f in QDBusConnectionInterface::serviceOwnerChanged(QString const&, QString const&, QString const&) () from /usr/lib/libQtDBus.so.4
#11 0x00007fab5644d344 in QDBusConnectionInterface::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libQtDBus.so.4
#12 0x00007fab55c61e3f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4
#13 0x00007fab5644cfcf in QDBusConnectionInterface::NameOwnerChanged(QString const&, QString const&, QString const&) () from /usr/lib/libQtDBus.so.4
#14 0x00007fab5644d3ac in QDBusConnectionInterface::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libQtDBus.so.4
#15 0x00007fab56411486 in ?? () from /usr/lib/libQtDBus.so.4
#16 0x00007fab5641c05f in ?? () from /usr/lib/libQtDBus.so.4
#17 0x00007fab55c5ed49 in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4
#18 0x00007fab54b6b22c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#19 0x00007fab54b716fb in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#20 0x00007fab56d3ea16 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#21 0x00007fab55c4f06c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#22 0x00007fab55c517e7 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQtCore.so.4
#23 0x00007fab55c789d3 in ?? () from /usr/lib/libQtCore.so.4
#24 0x00007fab50d618c2 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#25 0x00007fab50d65748 in ?? () from /lib/libglib-2.0.so.0
#26 0x00007fab50d658fc in g_main_context_iteration () from /lib/libglib-2.0.so.0
#27 0x00007fab55c78513 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#28 0x00007fab54c1b46e in ?? () from /usr/lib/libQtGui.so.4
#29 0x00007fab55c4d992 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#30 0x00007fab55c4dd6c in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#31 0x00007fab55c51aab in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#32 0x00000000004067c2 in _start ()

This bug may be a duplicate of or related to bug 259481.

Possible duplicates by query: bug 267573, bug 267321, bug 267181, bug 265931, bug 265355.

Reported using DrKonqi
Comment 1 Dario Andres 2011-04-16 23:58:12 UTC
[Comment from a bug triager]
This issue was fixed some time ago in KPackageKit 0.6 and later: bug 225494.
Regards

*** This bug has been marked as a duplicate of bug 225494 ***