Application: apper (0.9.2) KDE Platform Version: 4.14.14 Qt Version: 4.8.7 Operating System: Linux 4.3.0-2-pae i686 Distribution: "openSUSE Tumbleweed (20151128) (i586)" -- Information about the crash: - What I was doing when the application crashed: Trying to configure software updates through Apper. I am using OpenSuse Tumbleweed / KDE Plasma 5.4.3 / Qt Ver 5.5.1 / Kernel 4.3.0-2-pae / 32-bit - Unusual behavior I noticed: Software update tray applet repeatedly crashes all the time with message about the backend. Apper reported that PackageKit crashed, then that a message from the daemon did not get answered, then apper crashed. - Custom settings of the application: OpenSuse Tumbleweed, installed fresh a few days ago. The crash can be reproduced every time. -- Backtrace: Application: Apper (apper), signal: Segmentation fault Using host libthread_db library "/lib/libthread_db.so.1". [KCrash Handler] #7 0xffffffff in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () at /usr/lib/libQtCore.so.4 #8 0xffffffff in PackageKit::Transaction::finished(PackageKit::Transaction::Exit, unsigned int) () at /usr/lib/libpackagekitqt4.so.0 #9 0xffffffff in PackageKit::TransactionPrivate::finished(unsigned int, unsigned int) () at /usr/lib/libpackagekitqt4.so.0 #10 0xffffffff in PackageKit::TransactionPrivate::daemonQuit() () at /usr/lib/libpackagekitqt4.so.0 #11 0xffffffff in () at /usr/lib/libpackagekitqt4.so.0 #12 0xffffffff in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () at /usr/lib/libQtCore.so.4 #13 0xffffffff in PackageKit::Daemon::daemonQuit() () at /usr/lib/libpackagekitqt4.so.0 #14 0xffffffff in PackageKit::DaemonPrivate::serviceOwnerChanged(QString const&, QString const&, QString const&) () at /usr/lib/libpackagekitqt4.so.0 #15 0xffffffff in () at /usr/lib/libpackagekitqt4.so.0 #16 0xffffffff in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () at /usr/lib/libQtCore.so.4 #17 0xffffffff in QDBusServiceWatcher::serviceOwnerChanged(QString const&, QString const&, QString const&) () at /usr/lib/libQtDBus.so.4 #18 0xffffffff in () at /usr/lib/libQtDBus.so.4 #19 0xffffffff in QDBusServiceWatcher::qt_metacall(QMetaObject::Call, int, void**) () at /usr/lib/libQtDBus.so.4 #20 0xffffffff in () at /usr/lib/libQtDBus.so.4 #21 0xffffffff in () at /usr/lib/libQtDBus.so.4 #22 0xffffffff in QObject::event(QEvent*) () at /usr/lib/libQtCore.so.4 #23 0xffffffff in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQtGui.so.4 #24 0xffffffff in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQtGui.so.4 #25 0xffffffff in KApplication::notify(QObject*, QEvent*) () at /usr/lib/libkdeui.so.5 #26 0xffffffff in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib/libQtCore.so.4 #27 0xffffffff in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQtCore.so.4 #28 0xffffffff in QCoreApplication::sendPostedEvents(QObject*, int) () at /usr/lib/libQtCore.so.4 #29 0xffffffff in () at /usr/lib/libQtCore.so.4 #30 0xffffffff in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0 #31 0xffffffff in () at /usr/lib/libglib-2.0.so.0 #32 0xffffffff in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0 #33 0xffffffff in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQtCore.so.4 #34 0xffffffff in () at /usr/lib/libQtGui.so.4 #35 0xffffffff in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQtCore.so.4 #36 0xffffffff in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQtCore.so.4 #37 0xffffffff in QCoreApplication::exec() () at /usr/lib/libQtCore.so.4 #38 0xffffffff in QApplication::exec() () at /usr/lib/libQtGui.so.4 #39 0x0804de0e in () #40 0xffffffff in __libc_start_main () at /lib/libc.so.6 #41 0x0804de5b in _start () Possible duplicates by query: bug 347780. Reported using DrKonqi
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!