Application: konsole (15.08.1) Qt Version: 5.5.0 Operating System: Linux 4.2.3-200.fc22.x86_64 x86_64 Distribution: "Fedora release 22 (Twenty Two)" -- Information about the crash: - What I was doing when the application crashed: Powered on the machine, logged in, found the crash report waiting. -- Backtrace: Application: Konsole (konsole), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f4b5d28b900 (LWP 1980))] Thread 2 (Thread 0x7f4b3dd9a700 (LWP 1983)): #0 0x00007f4b553e1b3d in recvmsg () at /lib64/libc.so.6 #1 0x00007f4b515b0177 in _xcb_in_read () at /lib64/libxcb.so.1 #2 0x00007f4b515ae3f1 in _xcb_conn_wait () at /lib64/libxcb.so.1 #3 0x00007f4b515afc77 in xcb_wait_for_event () at /lib64/libxcb.so.1 #4 0x00007f4b3ff29999 in QXcbEventReader::run() () at /lib64/libQt5XcbQpa.so.5 #5 0x00007f4b55fe154e in QThreadPrivate::start(void*) () at /lib64/libQt5Core.so.5 #6 0x00007f4b53361555 in start_thread () at /lib64/libpthread.so.0 #7 0x00007f4b553e0b9d in clone () at /lib64/libc.so.6 Thread 1 (Thread 0x7f4b5d28b900 (LWP 1980)): [KCrash Handler] #5 0x00007f4b5cc4a3b0 in Konsole::Session::sessionId() const () at /lib64/libkonsoleprivate.so.15 #6 0x00007f4b5cc81a58 in Konsole::ViewManager::createTerminalDisplay(Konsole::Session*) () at /lib64/libkonsoleprivate.so.15 #7 0x00007f4b5cc84969 in Konsole::ViewManager::createView(Konsole::Session*, Konsole::ViewContainer*, int) () at /lib64/libkonsoleprivate.so.15 #8 0x00007f4b5cc84c90 in Konsole::ViewManager::createView(Konsole::Session*) () at /lib64/libkonsoleprivate.so.15 #9 0x00007f4b5cc8808f in Konsole::ViewManager::restoreSessions(KConfigGroup const&) () at /lib64/libkonsoleprivate.so.15 #10 0x00007f4b5b18d5d0 in KMainWindow::readPropertiesInternal(KConfig*, int) () at /lib64/libKF5XmlGui.so.5 #11 0x00007f4b5b18d632 in KMainWindow::restore(int, bool) () at /lib64/libKF5XmlGui.so.5 #12 0x00007f4b5cf09c46 in kdemain () at /lib64/libkdeinit5_konsole.so #13 0x00007f4b552fe700 in __libc_start_main () at /lib64/libc.so.6 #14 0x0000000000400a99 in _start () Reported using DrKonqi
Same thing on Fedora 23, Konsole crashes on session restore. It might be due to frameworks 5.16 update. #5 0x00007f56ad3bf3b0 in Konsole::Session::sessionId() const (this=this@entry=0x0) at ../../src/Session.cpp:872 #6 0x00007f56ad3f6a58 in Konsole::ViewManager::createTerminalDisplay(Konsole::Session*) (this=this@entry=0x5607199bf0c0, session=session@entry=0x0) at ../../src/ViewManager.cpp:752 #7 0x00007f56ad3f9969 in Konsole::ViewManager::createView(Konsole::Session*, Konsole::ViewContainer*, int) (this=this@entry=0x5607199bf0c0, session=session@entry=0x0, container=0x560719b82d40, index=index@entry=-1) at ../../src/ViewManager.cpp:528 #8 0x00007f56ad3f9c90 in Konsole::ViewManager::createView(Konsole::Session*) (this=this@entry=0x5607199bf0c0, session=session@entry=0x0) at ../../src/ViewManager.cpp:588 #9 0x00007f56ad3fd08f in Konsole::ViewManager::restoreSessions(KConfigGroup const&) (this=0x5607199bf0c0, group=...) at ../../src/ViewManager.cpp:945 #10 0x00007f56ab8eb930 in KMainWindow::readPropertiesInternal(KConfig*, int) (this=this@entry=0x5607199753c0, config=0x5607199a6cd0, number=number@entry=1) at ../../src/kmainwindow.cpp:615 #11 0x00007f56ab8eb992 in KMainWindow::restore(int, bool) (this=0x5607199753c0, number=number@entry=1, show=show@entry=true) at ../../src/kmainwindow.cpp:440 #12 0x00007f56ad67ec46 in kdemain(int, char**) (app=...) at ../../src/main.cpp:317 #13 0x00007f56ad67ec46 in kdemain(int, char**) (argc=<optimized out>, argv=<optimized out>) at ../../src/main.cpp:112 #14 0x00007f56a5a25580 in __libc_start_main (main=0x560719437b70 <main(int, char**)>, argc=3, argv=0x7ffe284ccaa8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffe284cca98) at libc-start.c:289 #15 0x0000560719437ba9 in _start ()
The session file (~/.config/sessions/konsole_xxxx) seems to be invalid : [1] Active=7 Sessions=1,5,2,3,4,6,7,0 ... If I remove the ",0", the problem is fixed. When triggering a session save (kickoff -> leave -> save session), the created file is fine, so I don't know how the invalid one was created.
Got this for the first time after logging out and back in to openSUSE 42.1 x86-64 with Plasma 5.5.4 desktop and Konsole 15.12.2 with Qt 5.5.1 (built against 5.5.1 as well) and KDE Frameworks 5.19.0: Application: Konsole (konsole), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f3cd7e37800 (LWP 16763))] Thread 2 (Thread 0x7f3cc263d700 (LWP 16765)): ..... Thread 1 (Thread 0x7f3cd7e37800 (LWP 16763)): [KCrash Handler] #6 0x00007f3cd73fd2d0 in Konsole::Session::sessionId() const () at /usr/lib64/libkonsoleprivate.so.15 #7 0x00007f3cd7430ac8 in Konsole::ViewManager::createTerminalDisplay(Konsole::Session*) () at /usr/lib64/libkonsoleprivate.so.15 #8 0x00007f3cd7436565 in Konsole::ViewManager::createView(Konsole::Session*, Konsole::ViewContainer*, int) () at /usr/lib64/libkonsoleprivate.so.15 #9 0x00007f3cd7437800 in Konsole::ViewManager::createView(Konsole::Session*) () at /usr/lib64/libkonsoleprivate.so.15 #10 0x00007f3cd7438a94 in Konsole::ViewManager::restoreSessions(KConfigGroup const&) () at /usr/lib64/libkonsoleprivate.so.15 #11 0x00007f3cd6a6744d in KMainWindow::readPropertiesInternal(KConfig*, int) () at /usr/lib64/libKF5XmlGui.so.5 #12 0x00007f3cd6a675a2 in KMainWindow::restore(int, bool) () at /usr/lib64/libKF5XmlGui.so.5 #13 0x00007f3cd7a5fe0c in () at /usr/lib64/libkdeinit5_konsole.so #14 0x00007f3cd7a60ddc in kdemain () at /usr/lib64/libkdeinit5_konsole.so #15 0x00007f3cd76b1b05 in __libc_start_main () at /lib64/libc.so.6 #16 0x00000000004007ee in _start () PS. Backtraces in #356270 and #359428 look very similar to those in this one.
*** Bug 356270 has been marked as a duplicate of this bug. ***
*** Bug 359428 has been marked as a duplicate of this bug. ***
*** Bug 361841 has been marked as a duplicate of this bug. ***
*** Bug 364653 has been marked as a duplicate of this bug. ***
*** Bug 364839 has been marked as a duplicate of this bug. ***
Created attachment 100810 [details] New crash information added by DrKonqi konsole (16.04.3) using Qt 5.7.0 - What I was doing when the application crashed: Situation the same as reported by Fedora users. Powered on the machine, logged in, and konsole cashed during Plasma session was restoring. Used componenets: Plasma 5.7.3, KF-5.25, Qt-5.7.0 -- Backtrace (Reduced): #5 0x00007ff0309d9970 in Konsole::Session::sessionId() const () from /usr/lib/libkonsoleprivate.so.16 #6 0x00007ff030a0fb48 in Konsole::ViewManager::createTerminalDisplay(Konsole::Session*) () from /usr/lib/libkonsoleprivate.so.16 #7 0x00007ff030a11bdf in Konsole::ViewManager::createView(Konsole::Session*, Konsole::ViewContainer*, int) () from /usr/lib/libkonsoleprivate.so.16 #8 0x00007ff030a16150 in Konsole::ViewManager::createView(Konsole::Session*) () from /usr/lib/libkonsoleprivate.so.16 #9 0x00007ff030a16c71 in Konsole::ViewManager::restoreSessions(KConfigGroup const&) () from /usr/lib/libkonsoleprivate.so.16
Why is this bug still "Unconfirmed", when it has 5 duplicates?
Because no developer was yet able to confirm where the bug is. Is this 100% reproducible for you? If yes, please add exact steps, ideally for a freshly created user account on a standard distribution.
Hmmm this doesn't seem to be reproducible for me anymore. I guess it was fixed by a change in the code for session-restoring or so (I still have the same version of konsole, but there were many updates related to the desktop recently - Linux Mint 18.1 + KDE Plasma 5 here).
I didn't meet this from very long time. I suppose that has been fixed in meantime. I'm not able to reproduce it.
I'm not able to retest this now, sorry.
I haven't seen this issue since a few months.
please reopen if it shows up agagin
I just saw that crash again on Plasma 5 (Linux Mint 18.2) It was right after I rebooted for the installation of an updated kernel (that shouldn't cause such a crash, though).
Which version of Konsole? I suggest to add an updated backtrace to investigate if this is really the same issue.