Bug 387063 - Apper crashes on launch on Fedora 27
Summary: Apper crashes on launch on Fedora 27
Status: RESOLVED FIXED
Alias: None
Product: apper
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Daniel Nicoletti
URL:
Keywords: drkonqi
: 387902 (view as bug list)
Depends on:
Blocks:
 
Reported: 2017-11-18 09:57 UTC by Arcadiy Ivanov
Modified: 2018-02-23 14:31 UTC (History)
10 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
New crash information added by DrKonqi (3.90 KB, text/plain)
2017-11-19 09:11 UTC, Mattia
Details
New crash information added by DrKonqi (4.92 KB, text/plain)
2017-11-28 10:02 UTC, Tomáš Neuberg
Details
New crash information added by DrKonqi (4.07 KB, text/plain)
2018-01-01 20:41 UTC, Alexander Potashev
Details
New crash information added by DrKonqi (3.96 KB, text/plain)
2018-02-05 00:06 UTC, Arcadiy Ivanov
Details
New crash information added by DrKonqi (3.92 KB, text/plain)
2018-02-07 08:59 UTC, Tomáš Neuberg
Details
Fix for 0.9.3 version of Apper (639 bytes, patch)
2018-02-07 21:50 UTC, Aurélien Normand
Details
New crash information added by DrKonqi (6.14 KB, text/plain)
2018-02-10 16:33 UTC, JNoake
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Arcadiy Ivanov 2017-11-18 09:57:26 UTC
Application: apper (0.9.3)

Qt Version: 5.9.2
Frameworks Version: 5.39.0
Operating System: Linux 4.13.12-300.fc27.x86_64 x86_64
Distribution: "Fedora release 27 (Twenty Seven)"

-- Information about the crash:
- What I was doing when the application crashed:

Launching the application. This bug is always reproducible on Fedora 27.

The crash can be reproduced every time.

-- Backtrace:
Application: apper (apper), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f0fb08d7940 (LWP 6491))]

Thread 3 (Thread 0x7f0f8bfff700 (LWP 6493)):
#0  0x00007f0fa7c318bb in poll () from /lib64/libc.so.6
#1  0x00007f0f9fd19ed9 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0
#2  0x00007f0f9fd19fec in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#3  0x00007f0fa8a9c35b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#4  0x00007f0fa8a4a0ea in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#5  0x00007f0fa889b8ba in QThread::exec() () from /lib64/libQt5Core.so.5
#6  0x00007f0fac56c479 in QDBusConnectionManager::run() () from /lib64/libQt5DBus.so.5
#7  0x00007f0fa889fb92 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5
#8  0x00007f0fa4eed609 in start_thread () from /lib64/libpthread.so.0
#9  0x00007f0fa7c3de6f in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f0f92362700 (LWP 6492)):
#0  0x00007f0fa7c318bb in poll () from /lib64/libc.so.6
#1  0x00007f0fa45d5fe7 in _xcb_conn_wait () from /lib64/libxcb.so.1
#2  0x00007f0fa45d7dda in xcb_wait_for_event () from /lib64/libxcb.so.1
#3  0x00007f0f944c4a49 in QXcbEventReader::run() () from /lib64/libQt5XcbQpa.so.5
#4  0x00007f0fa889fb92 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5
#5  0x00007f0fa4eed609 in start_thread () from /lib64/libpthread.so.0
#6  0x00007f0fa7c3de6f in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f0fb08d7940 (LWP 6491)):
[KCrash Handler]
#6  KCModuleProxy::realModule (this=0x5616028aad60) at /usr/src/debug/kf5-kcmutils-5.39.0-1.fc27.x86_64/src/kcmoduleproxy.cpp:73
#7  0x000056160066f8bb in MainUi::MainUi (this=0x561602848fc0, parent=<optimized out>) at /usr/src/debug/apper-0.9.3-0.10.20170226.fc27.x86_64/Apper/MainUi.cpp:48
#8  0x000056160067402a in Apper::showUi (this=0x7ffe84d1ca90) at /usr/src/debug/apper-0.9.3-0.10.20170226.fc27.x86_64/Apper/Apper.cpp:171
#9  0x00007f0fa8a7491a in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5
#10 0x00007f0faa8c64df in QApplication::event(QEvent*) () from /lib64/libQt5Widgets.so.5
#11 0x00007f0faa8c06ac in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5
#12 0x00007f0faa8c7ef4 in QApplication::notify(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5
#13 0x00007f0fa8a4b367 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5
#14 0x00007f0fa8a4daeb in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5
#15 0x00007f0fa8a9c553 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5
#16 0x00007f0f9fd19bb7 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#17 0x00007f0f9fd19f60 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0
#18 0x00007f0f9fd19fec in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#19 0x00007f0fa8a9c33f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#20 0x00007f0fa8a4a0ea in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#21 0x00007f0fa8a52744 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5
#22 0x000056160066f2b8 in main (argc=<optimized out>, argv=0x7ffe84d1cbd8) at /usr/src/debug/apper-0.9.3-0.10.20170226.fc27.x86_64/Apper/main.cpp:54

Reported using DrKonqi
Comment 1 Mattia 2017-11-19 09:11:03 UTC
Created attachment 108959 [details]
New crash information added by DrKonqi

apper (0.9.3) using Qt 5.9.2

- What I was doing when the application crashed:

Apper crashes on launch.
Fedora 27 x86_64

-- Backtrace (Reduced):
#6  0x00007f49f9f0e61a in KCModuleProxy::realModule() const () from /lib64/libKF5KCMUtils.so.5
#7  0x0000560f0d2a08bb in MainUi::MainUi (this=0x560f0e1c1950, parent=<optimized out>) at /usr/src/debug/apper-0.9.3-0.10.20170226.fc27.x86_64/Apper/MainUi.cpp:48
#8  0x0000560f0d2a502a in Apper::showUi (this=0x7ffebf616220) at /usr/src/debug/apper-0.9.3-0.10.20170226.fc27.x86_64/Apper/Apper.cpp:171
#9  0x00007f49f240491a in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5
#10 0x00007f49f42624df in QApplication::event(QEvent*) () from /lib64/libQt5Widgets.so.5
Comment 2 Nick Cross 2017-11-24 13:49:04 UTC
I am also seeing this:

Application: apper (apper), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f37852eb940 (LWP 14007))]

Thread 3 (Thread 0x7f376506c700 (LWP 14009)):
#0  0x00007f377c6358bb in poll () from /lib64/libc.so.6
#1  0x00007f377471ded9 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0
#2  0x00007f377471dfec in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#3  0x00007f377d4a035b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#4  0x00007f377d44e0ea in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#5  0x00007f377d29f8ba in QThread::exec() () from /lib64/libQt5Core.so.5
#6  0x00007f3780f71479 in QDBusConnectionManager::run() () from /lib64/libQt5DBus.so.5
#7  0x00007f377d2a3b92 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5
#8  0x00007f37798f1609 in start_thread () from /lib64/libpthread.so.0
#9  0x00007f377c641e6f in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f3766e72700 (LWP 14008)):
#0  0x00007f377c6358bb in poll () from /lib64/libc.so.6
#1  0x00007f3778fd9fe7 in _xcb_conn_wait () from /lib64/libxcb.so.1
#2  0x00007f3778fdbdda in xcb_wait_for_event () from /lib64/libxcb.so.1
#3  0x00007f3768fd4a49 in QXcbEventReader::run() () from /lib64/libQt5XcbQpa.so.5
#4  0x00007f377d2a3b92 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5
#5  0x00007f37798f1609 in start_thread () from /lib64/libpthread.so.0
#6  0x00007f377c641e6f in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f37852eb940 (LWP 14007)):
[KCrash Handler]
#6  0x00007f3784eff6da in KCModuleProxy::realModule() const () from /lib64/libKF5KCMUtils.so.5
#7  0x00005616b47e58bb in MainUi::MainUi(QWidget*) ()
#8  0x00005616b47ea02a in Apper::showUi() ()
#9  0x00007f377d47891a in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5
#10 0x00007f377f2ca4df in QApplication::event(QEvent*) () from /lib64/libQt5Widgets.so.5
#11 0x00007f377f2c46ac in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5
#12 0x00007f377f2cbef4 in QApplication::notify(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5
#13 0x00007f377d44f367 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5
#14 0x00007f377d451aeb in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5
#15 0x00007f377d4a0553 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5
#16 0x00007f377471dbb7 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#17 0x00007f377471df60 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0
#18 0x00007f377471dfec in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#19 0x00007f377d4a033f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#20 0x00007f377d44e0ea in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQt5Core.so.5
#21 0x00007f377d456744 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5
#22 0x00005616b47e52b8 in main ()
Comment 3 Nick Cross 2017-11-24 16:57:20 UTC
I've installed a fresh Fedora 27 KDE Spin in a VM and this still happens. Intriguingly running "/usr/bin/kcmshell5 kcm_apper" starts it up fine (sound this by starting "Software Management" from krunner.
Comment 4 Tomáš Neuberg 2017-11-28 10:02:41 UTC
Created attachment 109091 [details]
New crash information added by DrKonqi

apper (0.9.3) using Qt 5.9.2

- What I was doing when the application crashed:

Apper crashes during lunch after upgrading to Fedora 27. It works OK on Fedora 26.

-- Backtrace (Reduced):
#6  KCModuleProxy::realModule (this=0x55cead951790) at /usr/src/debug/kf5-kcmutils-5.40.0-1.fc27.x86_64/src/kcmoduleproxy.cpp:73
#7  0x000055ceab91d8bb in MainUi::MainUi (this=0x55cead906f00, parent=<optimized out>) at /usr/src/debug/apper-0.9.3-0.10.20170226.fc27.x86_64/Apper/MainUi.cpp:48
#8  0x000055ceab92202a in Apper::showUi (this=0x7ffd5490bd90) at /usr/src/debug/apper-0.9.3-0.10.20170226.fc27.x86_64/Apper/Apper.cpp:171
#9  0x00007f728384791a in QObject::event (this=0x7ffd5490bd90, e=<optimized out>) at kernel/qobject.cpp:1246
#10 0x00007f728382568c in QCoreApplication::event (this=<optimized out>, e=<optimized out>) at kernel/qcoreapplication.cpp:1813
Comment 5 Rex Dieter 2017-12-14 17:09:32 UTC
*** Bug 387902 has been marked as a duplicate of this bug. ***
Comment 6 Alexander Potashev 2018-01-01 20:41:07 UTC
Created attachment 109619 [details]
New crash information added by DrKonqi

apper (0.9.3) using Qt 5.9.1

- What I was doing when the application crashed:

start apper (apper-0.9.3-0.10.20170226.fc27.x86_64) on Fedora 27.

-- Backtrace (Reduced):
#6  KCModuleProxy::realModule (this=0x563b17a15b60) at /usr/src/debug/kf5-kcmutils-5.40.0-1.fc27.x86_64/src/kcmoduleproxy.cpp:73
#7  0x0000563b16a618bb in MainUi::MainUi (this=0x563b179da9a0, parent=<optimized out>) at /usr/src/debug/apper-0.9.3-0.10.20170226.fc27.x86_64/Apper/MainUi.cpp:48
#8  0x0000563b16a6602a in Apper::showUi (this=0x7ffee1eaa620) at /usr/src/debug/apper-0.9.3-0.10.20170226.fc27.x86_64/Apper/Apper.cpp:171
#9  0x00007fcbedc6812a in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5
#10 0x00007fcbefa9382b in QApplication::event(QEvent*) () from /lib64/libQt5Widgets.so.5
Comment 7 Arcadiy Ivanov 2018-02-05 00:06:37 UTC
Created attachment 110341 [details]
New crash information added by DrKonqi

apper (0.9.3) using Qt 5.9.4

- What I was doing when the application crashed:
Still crashing on Fedora 27 with latest updates.

-- Backtrace (Reduced):
#6  0x00007fa6d3d41b5a in KCModuleProxy::realModule() const () from /lib64/libKF5KCMUtils.so.5
#7  0x000055e9498048bb in MainUi::MainUi (this=0x55e949bb92e0, parent=<optimized out>) at /usr/src/debug/apper-0.9.3-0.10.20170226.fc27.x86_64/Apper/MainUi.cpp:48
#8  0x000055e94980902a in Apper::showUi (this=0x7fff26c365f0) at /usr/src/debug/apper-0.9.3-0.10.20170226.fc27.x86_64/Apper/Apper.cpp:171
#9  0x00007fa6cc2a1f2a in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5
#10 0x00007fa6ce0fe6cf in QApplication::event(QEvent*) () from /lib64/libQt5Widgets.so.5
Comment 8 Tomáš Neuberg 2018-02-07 08:59:12 UTC
Created attachment 110387 [details]
New crash information added by DrKonqi

apper (0.9.3) using Qt 5.9.4

- What I was doing when the application crashed:

Launching the application from main manu. It starts OK if I start it from System settings (Software Management)

-- Backtrace (Reduced):
#6  0x00007f9f087cfb5a in KCModuleProxy::realModule() const () from /lib64/libKF5KCMUtils.so.5
#7  0x000056134ab5b8bb in MainUi::MainUi (this=0x56134b559a00, parent=<optimized out>) at /usr/src/debug/apper-0.9.3-0.10.20170226.fc27.x86_64/Apper/MainUi.cpp:48
#8  0x000056134ab6002a in Apper::showUi (this=0x7ffec4be58e0) at /usr/src/debug/apper-0.9.3-0.10.20170226.fc27.x86_64/Apper/Apper.cpp:171
#9  0x00007f9f00d2ff2a in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5
#10 0x00007f9f02b8c6cf in QApplication::event(QEvent*) () from /lib64/libQt5Widgets.so.5
Comment 9 Aurélien Normand 2018-02-07 21:50:21 UTC
Created attachment 110417 [details]
Fix for 0.9.3 version of Apper

Providing patch which should normally fix this issue.
I was able to run and use properly Apper via the command line or the menu with this.
Comment 10 JNoake 2018-02-10 16:33:00 UTC
Created attachment 110513 [details]
New crash information added by DrKonqi

apper (0.9.3) using Qt 5.9.4

System recently upgraded from fc25.

Apper crashes when launched from the (KDE) Application Menu->Administration-Apper shortcut.

When apper is started from the console, the following output is produced before the crash:
QCommandLineParser: option not defined: "install-mime-type"
QCommandLineParser: option not defined: "install-package-name"
QCommandLineParser: option not defined: "install-provide-file"
QCommandLineParser: option not defined: "install-catalog"
QCommandLineParser: option not defined: "remove-package-by-file"
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
KCrash: Application 'apper' crashing...
KCrash: Attempting to start /usr/libexec/drkonqi from kdeinit
sock_file=/run/user/1000/kdeinit5__0
QSocketNotifier: Invalid socket 8 and type 'Read', disabling...
QSocketNotifier: Invalid socket 9 and type 'Read', disabling...


Apper can be launched from Application Menu->Settings->System Settings->Software Management
 but crashes (with NO 'details' !) whenever *any*  'Group' is clicked, with a dialog quoting 'A problem that we were not expecting has occured. Please report this bug with the error description.'

'Installed software' link produces a list.
'Updates' link searches and indicates that all is up to date.

Tried with Nvidia proprietry drivers and nouveau drivers same result.

-- Backtrace (Reduced):
#6  KCModuleProxy::realModule (this=0x5573caeae820) at /usr/src/debug/kf5-kcmutils-5.42.0-1.fc27.x86_64/src/kcmoduleproxy.cpp:73
#7  0x00005573cab618bb in MainUi::MainUi (this=0x5573caea52e0, parent=<optimized out>) at /usr/src/debug/apper-0.9.3-0.10.20170226.fc27.x86_64/Apper/MainUi.cpp:48
#8  0x00005573cab6602a in Apper::showUi (this=0x7ffed71babf0) at /usr/src/debug/apper-0.9.3-0.10.20170226.fc27.x86_64/Apper/Apper.cpp:171
#9  0x00007f1d32035f2a in QObject::event (this=0x7ffed71babf0, e=<optimized out>) at kernel/qobject.cpp:1246
#10 0x00007f1d32013c9c in QCoreApplication::event (this=<optimized out>, e=<optimized out>) at kernel/qcoreapplication.cpp:1811
Comment 11 Christoph Feck 2018-02-23 00:16:25 UTC
Daniel, could you check if the patch from comment #9 still is applicable for Apper 1.0.0? From quickly looking at it, it makes sense, because a static_cast never returns a nullptr.
Comment 12 Daniel Nicoletti 2018-02-23 04:08:15 UTC
No this bug is fixed with Apper 1.0.0, since it's not a KCM anymore, and that code doesn't exist anymore.
Comment 13 Rex Dieter 2018-02-23 14:30:47 UTC
So, it's effectively fixed => closing
Comment 14 Rex Dieter 2018-02-23 14:31:31 UTC
In the short-term, a patched build for f27:
https://bodhi.fedoraproject.org/updates/FEDORA-2018-a3e221c79d