Bug 390978 - Apper crashes just after start
Summary: Apper crashes just after start
Status: RESOLVED WORKSFORME
Alias: None
Product: apper
Classification: Applications
Component: general (show other bugs)
Version: 0.9.0
Platform: Debian testing Linux
: NOR crash
Target Milestone: ---
Assignee: Daniel Nicoletti
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-02-24 02:34 UTC by Sebastian Dicke
Modified: 2021-01-16 04:37 UTC (History)
0 users

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 Sebastian Dicke 2018-02-24 02:34:15 UTC
Application: apper (0.9.3)

Qt Version: 5.9.2
Frameworks Version: 5.42.0
Operating System: Linux 4.14.0-3-amd64 x86_64
Distribution: Debian GNU/Linux testing (buster)

-- Information about the crash:
I started apper with no arguments or options, the application crashes without show it main window. The problems occurred after restarting the system and reinstall the application, too.

If I rund it from terminal emulator sometimes it outputs something like this:
„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"
kf5.kwidgetsaddons: Invalid pixmap specified.
kf5.kwidgetsaddons: Invalid pixmap specified.
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = apper path = /usr/bin pid = 32159
KCrash: Arguments: /usr/bin/apper 
KCrash: Attempting to start /usr/lib/x86_64-linux-gnu/libexec/drkonqi from kdeinit
sock_file=/run/user/1000/kdeinit5__0”

And sometimes something like this:
„QSocketNotifier: Invalid socket 8 and type 'Read', disabling...
QSocketNotifier: Invalid socket 12 and type 'Read', disabling...
QSocketNotifier: Invalid socket 9 and type 'Read', disabling...”

Followed by bash output

„[1]+  Exit 253                apper“

The crash can be reproduced every time.

-- Backtrace:
Application: apper (apper), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f3af4ac0940 (LWP 29029))]

Thread 3 (Thread 0x7f3ada234700 (LWP 29031)):
#0  0x00007f3aeb1f7908 in read () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x00007f3aedc57230 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f3aedc12c07 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f3aedc130c0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007f3aedc1322c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007f3aec09210b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#6  0x00007f3aec0372aa in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x00007f3aebe5635a in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x00007f3af0756e45 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#9  0x00007f3aebe5b22d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x00007f3ae8f7951a in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
#11 0x00007f3aeb2063ef in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 2 (Thread 0x7f3adc764700 (LWP 29030)):
#0  0x00007f3aeb1fbe6b in poll () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x00007f3ae8495150 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2  0x00007f3ae8496ee9 in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#3  0x00007f3ade8c7029 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#4  0x00007f3aebe5b22d in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007f3ae8f7951a in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
#6  0x00007f3aeb2063ef in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 1 (Thread 0x7f3af4ac0940 (LWP 29029)):
[KCrash Handler]
#6  0x00007f3af46e4aea in KCModuleProxy::realModule() const () from /usr/lib/x86_64-linux-gnu/libKF5KCMUtils.so.5
#7  0x0000557fe23849a6 in MainUi::MainUi(QWidget*) ()
#8  0x0000557fe23891b7 in Apper::showUi() ()
#9  0x00007f3aec0688c2 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#10 0x00007f3aecf198d4 in QGuiApplication::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5
#11 0x00007f3aeeab34ef in QApplication::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#12 0x00007f3aeeaad63c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#13 0x00007f3aeeab4f04 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#14 0x00007f3aec039258 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x00007f3aec03b9cd in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x00007f3aec092ac3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x00007f3aedc12f67 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#18 0x00007f3aedc131a0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#19 0x00007f3aedc1322c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#20 0x00007f3aec0920ef in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#21 0x00007f3aec0372aa in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#22 0x00007f3aec040214 in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#23 0x0000557fe23843e7 in main ()
Comment 1 Justin Zobel 2020-12-17 05:35:32 UTC
Thank you for the crash report.

As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved.

I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved/worksforme" when you respond, thank you.
Comment 2 Bug Janitor Service 2021-01-01 04:38:09 UTC
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!
Comment 3 Bug Janitor Service 2021-01-16 04:37:00 UTC
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!