Bug 369551

Summary: Running konsole from .desktop shortcut with --tabs-from-file option
Product: [Applications] konsole Reporter: boogie
Component: generalAssignee: Konsole Developer <konsole-devel>
Status: RESOLVED WORKSFORME    
Severity: crash CC: michaelcpinson
Priority: NOR Keywords: drkonqi
Version: 16.08.1   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description boogie 2016-09-30 07:24:46 UTC 
Application: konsole (16.08.1)

Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.7.4-1-default x86_64
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
If I run konsole from .desktop entry and I have --tabs-from-file with a few tabs automatically open ( tail-f for different logs ) then the following happens : 
1. If I run konsole on login from menu or Alt+F2 it runs OK
2. If I then run konsole from Desktop entry with --tabs form file option, screen flickers, but the console mostly runs ( here and there I have to run it twice ) 
3. If I then run konsole from menu or Alt+F2 it runs the same version as if the --tabs-from-file would be specified
4. If I do this a few more times it crashes as in this BUG report

The crash can be reproduced sometimes.

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

Thread 3 (Thread 0x7faca606b700 (LWP 4853)):
#0  0x00007facc5b3c10f in pthread_cond_wait@@GLIBC_2.3.2 () at /lib64/libpthread.so.0
#1  0x00007facb144c5a3 in  () at /usr/lib64/dri/tls/radeonsi_dri.so
#2  0x00007facb144bce7 in  () at /usr/lib64/dri/tls/radeonsi_dri.so
#3  0x00007facc5b36454 in start_thread () at /lib64/libpthread.so.0
#4  0x00007faccdd1a3ff in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7facb2ee4700 (LWP 4852)):
#0  0x00007faccdd116ed in poll () at /lib64/libc.so.6
#1  0x00007facc5617016 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x00007facc561712c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#3  0x00007facca296aab in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#4  0x00007facca23e6fa in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#5  0x00007facca0643c3 in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x00007facc83ef985 in  () at /usr/lib64/libQt5DBus.so.5
#7  0x00007facca0692e8 in  () at /usr/lib64/libQt5Core.so.5
#8  0x00007facc5b36454 in start_thread () at /lib64/libpthread.so.0
#9  0x00007faccdd1a3ff in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7facce3ca8c0 (LWP 4849)):
[KCrash Handler]
#6  0x00007faccd9768e0 in  () at /usr/lib64/libkonsoleprivate.so.16
#7  0x00007faccd9990d9 in Konsole::Session::getDynamicTitle() () at /usr/lib64/libkonsoleprivate.so.16
#8  0x00007faccd9a3083 in Konsole::SessionController::snapshot() () at /usr/lib64/libkonsoleprivate.so.16
#9  0x00007facca26e1ec in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib64/libQt5Core.so.5
#10 0x00007facca27a6e8 in QTimer::timerEvent(QTimerEvent*) () at /usr/lib64/libQt5Core.so.5
#11 0x00007facca26ec53 in QObject::event(QEvent*) () at /usr/lib64/libQt5Core.so.5
#12 0x00007faccb219acc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5
#13 0x00007faccb21ef6f in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5
#14 0x00007facca2409b0 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5
#15 0x00007facca2959ae in QTimerInfoList::activateTimers() () at /usr/lib64/libQt5Core.so.5
#16 0x00007facca295ed1 in  () at /usr/lib64/libQt5Core.so.5
#17 0x00007facc5616e17 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0
#18 0x00007facc5617080 in  () at /usr/lib64/libglib-2.0.so.0
#19 0x00007facc561712c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#20 0x00007facca296a8f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#21 0x00007facca23e6fa in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#22 0x00007facca246f0c in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5
#23 0x00007faccdff8af3 in kdemain () at /usr/lib64/libkdeinit5_konsole.so
#24 0x00007faccdc51291 in __libc_start_main () at /lib64/libc.so.6
#25 0x000000000040067a in _start ()

Reported using DrKonqi
Comment 1 Michael C. Pinson 2016-10-02 17:28:27 UTC 
I use an autostart-script to run a tabs-from-file setup.

I get the same behavior: desktop menu or Alt-F2 launch include the tabs-from-file tabs, plus a "normal" bash tab at the end.

Using an existing konsole window's File->New Window option does *not* clone all the tabs, but starts normally.

I have not seen the crash.

Konsole 16.08.1
Using:
KDE Frameworks 5.26.0
Qt 5.6.1 (built against 5.6.1)
The xcb windowing system

Distro: Sabayon Linux amd64 16.10
uname -a: Linux obi-wan 4.7.0-sabayon #1 SMP Sun Sep 25 10:02:32 UTC 2016 x86_64 AMD FX(tm)-8150 Eight-Core Processor AuthenticAMD GNU/Linux
kernel: sys-kernel/linux-sabayon-4.7.4 revision4
Comment 2 Andrew Crouthamel 2018-11-01 13:54:03 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 3 Bug Janitor Service 2018-11-16 11:44:39 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 4 Bug Janitor Service 2018-12-02 03:50:29 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!