[kmix] [Bug 370650] Crash on session restore
https://bugs.kde.org/show_bug.cgi?id=370650 Maarten ter Huurne changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #8 from Maarten ter Huurne --- This issue doesn't happen anymore for me. I don't remember exactly when it stopped happening though. -- You are receiving this mail because: You are watching all bug changes.
[kmix] [Bug 370650] Crash on session restore
https://bugs.kde.org/show_bug.cgi?id=370650 Andrew Crouthamel changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #7 from Andrew Crouthamel --- 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! -- You are receiving this mail because: You are watching all bug changes.
[kmix] [Bug 370650] Crash on session restore
https://bugs.kde.org/show_bug.cgi?id=370650 --- Comment #6 from Maarten ter Huurne--- 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. -- You are receiving this mail because: You are watching all bug changes.
[kmix] [Bug 370650] Crash on session restore
https://bugs.kde.org/show_bug.cgi?id=370650 --- Comment #5 from Jeff Hodd--- (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. -- You are receiving this mail because: You are watching all bug changes.
[kmix] [Bug 370650] Crash on session restore
https://bugs.kde.org/show_bug.cgi?id=370650 --- Comment #4 from Maarten ter Huurne--- (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. -- You are receiving this mail because: You are watching all bug changes.
[kmix] [Bug 370650] Crash on session restore
https://bugs.kde.org/show_bug.cgi?id=370650 --- Comment #3 from Jeff Hodd--- 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. -- You are receiving this mail because: You are watching all bug changes.
[kmix] [Bug 370650] Crash on session restore
https://bugs.kde.org/show_bug.cgi?id=370650 --- Comment #2 from Jeff Hodd--- 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 -- You are receiving this mail because: You are watching all bug changes.
[kmix] [Bug 370650] Crash on session restore
https://bugs.kde.org/show_bug.cgi?id=370650 Jeff Hoddchanged: What|Removed |Added CC||jgh...@gmail.com --- Comment #1 from Jeff Hodd --- 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, 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: https://bugs.kde.org/show_bug.cgi?id=369325;>bug 369325 -- You are receiving this mail because: You are watching all bug changes.