Bug 370650 - Crash on session restore
Summary: Crash on session restore
Status: RESOLVED WORKSFORME
Alias: None
Product: kmix
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Christian Esken
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2016-10-13 13:19 UTC by Maarten ter Huurne
Modified: 2018-11-01 13:49 UTC (History)
1 user (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 Maarten ter Huurne 2016-10-13 13:19:29 UTC
Application: kmix (4.6)

Qt Version: 5.7.0
Frameworks Version: 5.27.0
Operating System: Linux 4.1.31-30-default x86_64
Distribution: "openSUSE Leap 42.1 (x86_64)"

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

I have kmix running all the time. In the past this meant that it would get automatically started as part of the session restore. However, since a few months, kmix won't restore for some reason. Today I noticed an icon that indicated that kmix had crashed. I think it may also have crashed those other times it didn't start, but either I didn't notice or crash reporting for system tray apps didn't exist or work back then.

I didn't interact with kmix in any way during the session restore. For example, I didn't press any media keys like volume +/- on my keyboard.

The crash can be reproduced every time.

-- Backtrace:
Application: KMix (kmix), signal: Aborted
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f0b44765800 (LWP 2535))]

Thread 3 (Thread 0x7f0b297eb700 (LWP 2537)):
#0  0x00007f0b44030bfd in poll () from /lib64/libc.so.6
#1  0x00007f0b3a1b8422 in ?? () from /usr/lib64/libxcb.so.1
#2  0x00007f0b3a1ba00f in xcb_wait_for_event () from /usr/lib64/libxcb.so.1
#3  0x00007f0b2bd4e469 in ?? () from /usr/lib64/libQt5XcbQpa.so.5
#4  0x00007f0b3fa65859 in QThreadPrivate::start (arg=0xaea0d0) at thread/qthread_unix.cpp:344
#5  0x00007f0b3bf820a4 in start_thread () from /lib64/libpthread.so.0
#6  0x00007f0b4403902d in clone () from /lib64/libc.so.6

Thread 2 (Thread 0x7f0b30c40700 (LWP 2536)):
#0  0x00007f0b4402cccd in read () from /lib64/libc.so.6
#1  0x00007f0b3562b073 in ?? () from /usr/lib64/tls/libnvidia-tls.so.367.44
#2  0x00007f0b3b422b60 in ?? () from /usr/lib64/libglib-2.0.so.0
#3  0x00007f0b3b3e1999 in g_main_context_check () from /usr/lib64/libglib-2.0.so.0
#4  0x00007f0b3b3e1df8 in ?? () from /usr/lib64/libglib-2.0.so.0
#5  0x00007f0b3b3e1f7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#6  0x00007f0b3fc6af4b in QEventDispatcherGlib::processEvents (this=0x7f0b2c0008e0, flags=...) at kernel/qeventdispatcher_glib.cpp:425
#7  0x00007f0b3fc1a89b in QEventLoop::exec (this=this@entry=0x7f0b30c3fda0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210
#8  0x00007f0b3fa6102a in QThread::exec (this=this@entry=0x7f0b4123ed00 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread.cpp:507
#9  0x00007f0b40fd7aa5 in QDBusConnectionManager::run (this=0x7f0b4123ed00 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at qdbusconnection.cpp:196
#10 0x00007f0b3fa65859 in QThreadPrivate::start (arg=0x7f0b4123ed00 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>) at thread/qthread_unix.cpp:344
#11 0x00007f0b3bf820a4 in start_thread () from /lib64/libpthread.so.0
#12 0x00007f0b4403902d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f0b44765800 (LWP 2535)):
[KCrash Handler]
#6  0x00007f0b43f890c7 in raise () from /lib64/libc.so.6
#7  0x00007f0b43f8a478 in abort () from /lib64/libc.so.6
#8  0x00007f0b3fa50c7e in qt_message_fatal (context=..., message=<synthetic pointer>) at global/qlogging.cpp:1680
#9  QMessageLogger::fatal (this=this@entry=0x7fff5f39f0c0, msg=msg@entry=0x7f0b410287b0 "Internal error: got invalid meta type %d (%s) when trying to convert to meta type %d (%s)") at global/qlogging.cpp:793
#10 0x00007f0b40fe17f4 in QDBusConnectionPrivate::deliverCall (this=0x7f0b2c0039c0, object=0xea5830, msg=..., metaTypes=..., slotIdx=10) at qdbusintegrator.cpp:948
#11 0x00007f0b3fc45dc6 in QObject::event (this=0xea5830, e=<optimized out>) at kernel/qobject.cpp:1263
#12 0x00007f0b408d3a9c in QApplicationPrivate::notify_helper (this=<optimized out>, receiver=0xea5830, e=0x7f0b2c015e00) at kernel/qapplication.cpp:3799
#13 0x00007f0b408daa20 in QApplication::notify (this=0xab2010, receiver=0xea5830, e=0x7f0b2c015e00) at kernel/qapplication.cpp:3556
#14 0x00007f0b3fc1c5c5 in QCoreApplication::notifyInternal2 (receiver=0xea5830, event=event@entry=0x7f0b2c015e00) at kernel/qcoreapplication.cpp:988
#15 0x00007f0b3fc1e623 in QCoreApplication::sendEvent (event=0x7f0b2c015e00, receiver=<optimized out>) at kernel/qcoreapplication.h:231
#16 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0xa9e470) at kernel/qcoreapplication.cpp:1649
#17 0x00007f0b3fc1eb68 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1503
#18 0x00007f0b3fc6b6e3 in postEventSourceDispatch (s=0xb1b040) at kernel/qeventdispatcher_glib.cpp:276
#19 0x00007f0b3b3e1c84 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#20 0x00007f0b3b3e1ed8 in ?? () from /usr/lib64/libglib-2.0.so.0
#21 0x00007f0b3b3e1f7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#22 0x00007f0b3fc6af2c in QEventDispatcherGlib::processEvents (this=0xb1b020, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#23 0x00007f0b3fc1a89b in QEventLoop::exec (this=this@entry=0x7fff5f39f740, flags=..., flags@entry=...) at kernel/qeventloop.cpp:210
#24 0x00007f0b3fc22696 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1261
#25 0x00007f0b443445ba in kdemain () from /usr/lib64/libkdeinit5_kmix.so
#26 0x00007f0b43f75b25 in __libc_start_main () from /lib64/libc.so.6
#27 0x00000000004007de in _start ()

Possible duplicates by query: bug 349162, bug 339964.

Reported using DrKonqi
Comment 1 Jeff Hodd 2016-10-14 19:16:31 UTC
Application: korgac (16.08.2)

Qt Version: 5.7.0
Frameworks Version: 5.27.0
Operating System: Linux 4.7.6-1-ARCH x86_64 GNU/Linux
Distribution: "Arch Linux (x86_64)"

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

Logging in

The crash can be reproduced every time.

-- Backtrace:
Application: korgac (korgac), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0xa945a7c0 (LWP 919))]

Thread 5 (Thread 0xa3c4db40 (LWP 1099)):
#0  0xb7716d41 in __kernel_vsyscall ()
#1  0xb3750c8b in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0
#2  0xa77a7a4a in ?? () from /usr/lib/xorg/modules/dri/swrast_dri.so
#3  0xb374b301 in start_thread () from /usr/lib/libpthread.so.0
#4  0xb4f720ae in clone () from /usr/lib/libc.so.6

Thread 4 (Thread 0xa444eb40 (LWP 1098)):
#0  0xb7716d41 in __kernel_vsyscall ()
#1  0xb3750c8b in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0
#2  0xa77a7a4a in ?? () from /usr/lib/xorg/modules/dri/swrast_dri.so
#3  0xb374b301 in start_thread () from /usr/lib/libpthread.so.0
#4  0xb4f720ae in clone () from /usr/lib/libc.so.6

Thread 3 (Thread 0xa8667b40 (LWP 1087)):
[KCrash Handler]
#7  0xb5475e45 in QObject::disconnect(QObject const*, char const*, QObject const*, char const*) () from /usr/lib/libQt5Core.so.5
#8  0xb56e685d in ?? () from /usr/lib/libQt5DBus.so.5
#9  0xb56d3195 in ?? () from /usr/lib/libQt5DBus.so.5
#10 0xb52736fa in ?? () from /usr/lib/libQt5Core.so.5
#11 0xb374b301 in start_thread () from /usr/lib/libpthread.so.0
#12 0xb4f720ae in clone () from /usr/lib/libc.so.6

Thread 2 (Thread 0xa90e8b40 (LWP 1061)):
#0  0xb7716d41 in __kernel_vsyscall ()
#1  0xb4f6815f in poll () from /usr/lib/libc.so.6
#2  0xb387094d in ?? () from /usr/lib/libxcb.so.1
#3  0xb3872cc3 in xcb_wait_for_event () from /usr/lib/libxcb.so.1
#4  0xa91761e3 in ?? () from /usr/lib/libQt5XcbQpa.so.5
#5  0xb52736fa in ?? () from /usr/lib/libQt5Core.so.5
#6  0xb374b301 in start_thread () from /usr/lib/libpthread.so.0
#7  0xb4f720ae in clone () from /usr/lib/libc.so.6

Thread 1 (Thread 0xa945a7c0 (LWP 919)):
#0  0xb7716d41 in __kernel_vsyscall ()
#1  0xb3750c8b in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0
#2  0xb52745a3 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQt5Core.so.5
#3  0xb5273242 in QThread::wait(unsigned long) () from /usr/lib/libQt5Core.so.5
#4  0xb56d2ebf in ?? () from /usr/lib/libQt5DBus.so.5
#5  0xb56d2f78 in ?? () from /usr/lib/libQt5DBus.so.5
#6  0xb4eb78cb in __run_exit_handlers () from /usr/lib/libc.so.6
#7  0xb4eb7931 in exit () from /usr/lib/libc.so.6
#8  0xb6757937 in KDBusService::KDBusService(QFlags<KDBusService::StartupOption>, QObject*) () from /usr/lib/libKF5DBusAddons.so.5
#9  0x0805572e in ?? ()
#10 0xb4ea1196 in __libc_start_main () from /usr/lib/libc.so.6
#11 0x080559d3 in _start ()


Thus far, the only workarounds I've been able to find for this issue are 1) to turn off session management (SystemSettings->Startup and Shutdown->Desktop Session->On Login->Start with an empty session) OR 2) (SystemSettings->Startup and Shutdown->Desktop Session->On Login->Restore previous session) and add korgac to "Applications to be excluded from sessions".

Possible duplicates by query: <a href="https://bugs.kde.org/show_bug.cgi?id=369325">bug 369325</a>
Comment 2 Jeff Hodd 2016-10-14 19:21:17 UTC
Sorry about the formatting of the duplicate bug line - I can't seem to edit it. It should read:

Possible duplicates by query: bug 369325
Comment 3 Jeff Hodd 2016-10-14 19:25:23 UTC
Please let me know if this should be filed as a new bug for korgac vs. kmix. It's certainly very possible that the issue is related to session management and is not necessarily application-specific.
Comment 4 Maarten ter Huurne 2016-10-14 21:37:38 UTC
(In reply to Jeff Hodd from comment #3)
> Please let me know if this should be filed as a new bug for korgac vs. kmix.
> It's certainly very possible that the issue is related to session management
> and is not necessarily application-specific.

Looking at the backtraces, I think it's a different issue: the cause of the crash is different (abort vs segfault) and the functions on the stack are different as well (event vs disconnect). So please open a separate bug report for it.
Comment 5 Jeff Hodd 2016-10-14 22:34:12 UTC
(In reply to Maarten ter Huurne from comment #4)
> (In reply to Jeff Hodd from comment #3)
> > Please let me know if this should be filed as a new bug for korgac vs. kmix.
> > It's certainly very possible that the issue is related to session management
> > and is not necessarily application-specific.
> 
> Looking at the backtraces, I think it's a different issue: the cause of the
> crash is different (abort vs segfault) and the functions on the stack are
> different as well (event vs disconnect). So please open a separate bug
> report for it.

Thanks. Now submitted as bug 370883.
Comment 6 Maarten ter Huurne 2016-10-22 05:32:28 UTC
I had a crash of Konsole with a very similar backtrace (also "Internal error: got invalid meta type %d (%s) when trying to convert to meta type %d (%s)") and found bug 369050, which reports what looks like the same problem. So I think it's a bug in a library rather than the application, but I don't know which package it should be filed on.
Comment 7 Andrew Crouthamel 2018-11-01 13:41:26 UTC
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!
Comment 8 Maarten ter Huurne 2018-11-01 13:49:25 UTC
This issue doesn't happen anymore for me. I don't remember exactly when it stopped happening though.