Bug 350055 - Konsole crash after incomplete system suspend
Summary: Konsole crash after incomplete system suspend
Status: RESOLVED UPSTREAM
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: 15.04.0
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2015-07-09 15:23 UTC by Kenneth Ingham
Modified: 2015-10-05 13:07 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 Kenneth Ingham 2015-07-09 15:23:38 UTC
Application: konsole (15.04.0)

Qt Version: 5.4.2
Operating System: Linux 4.0.5-3-desktop x86_64
Distribution: "openSUSE 20150630 (Tumbleweed) (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:
I closed teh laptop lid.  However, the system did not properly suspend.  The primary display apparently was disconnected, but the secondary (VGA-connected) one was not.  Everything had moved to the secondary display.  When I opened the lid of the laptop and moved the window from the secondary screen to the primary one, konsole crashed (krashed? :-).


- Unusual behavior I noticed:
Described above.

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

Thread 3 (Thread 0x7f71b957b700 (LWP 3802)):
#0  0x00007f71ceaf300d in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007f71c617a332 in _xcb_conn_wait (__timeout=-1, __nfds=1, __fds=0x7f71b957ac00) at /usr/include/bits/poll2.h:46
#2  0x00007f71c617a332 in _xcb_conn_wait (c=c@entry=0x1ce9a20, cond=cond@entry=0x1ce9a60, vector=vector@entry=0x0, count=count@entry=0x0) at xcb_conn.c:459
#3  0x00007f71c617be17 in xcb_wait_for_event (c=0x1ce9a20) at xcb_in.c:623
#4  0x00007f71bb4dd7f9 in  () at /usr/lib64/qt5/plugins/platforms/libqxcb.so
#5  0x00007f71caf6feaf in  () at /usr/lib64/libQt5Core.so.5
#6  0x00007f71c5d56324 in start_thread (arg=0x7f71b957b700) at pthread_create.c:333
#7  0x00007f71ceafb75d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f71ad0d3700 (LWP 3804)):
#0  0x00007f71c5d5b93f in pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007f71b3013b6a in  () at /usr/lib64/dri/r600_dri.so
#2  0x00007f71b30134b7 in  () at /usr/lib64/dri/r600_dri.so
#3  0x00007f71c5d56324 in start_thread (arg=0x7f71ad0d3700) at pthread_create.c:333
#4  0x00007f71ceafb75d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f71cf19c8c0 (LWP 3801)):
[KCrash Handler]
#6  0x00007f71bb4d8228 in  () at /usr/lib64/qt5/plugins/platforms/libqxcb.so
#7  0x00007f71bb4d97fc in  () at /usr/lib64/qt5/plugins/platforms/libqxcb.so
#8  0x00007f71bb4df491 in  () at /usr/lib64/qt5/plugins/platforms/libqxcb.so
#9  0x00007f71bb4e010b in  () at /usr/lib64/qt5/plugins/platforms/libqxcb.so
#10 0x00007f71cb16fca9 in QObject::event(QEvent*) () at /usr/lib64/libQt5Core.so.5
#11 0x00007f71cbdfd86c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5
#12 0x00007f71cbe02b80 in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5
#13 0x00007f71cb13fbf3 in QCoreApplication::notifyInternal(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5
#14 0x00007f71cb141c37 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQt5Core.so.5
#15 0x00007f71cb193f53 in  () at /usr/lib64/libQt5Core.so.5
#16 0x00007f71c5620cc7 in g_main_context_dispatch (context=0x7f71b40016f0) at gmain.c:3122
#17 0x00007f71c5620cc7 in g_main_context_dispatch (context=context@entry=0x7f71b40016f0) at gmain.c:3737
#18 0x00007f71c5620ef8 in g_main_context_iterate (context=context@entry=0x7f71b40016f0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3808
#19 0x00007f71c5620f9c in g_main_context_iteration (context=0x7f71b40016f0, may_block=1) at gmain.c:3869
#20 0x00007f71cb19435f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#21 0x00007f71cb13d5ea in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#22 0x00007f71cb144d6d in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5
#23 0x00007f71cedd88bc in kdemain () at /usr/lib64/libkdeinit5_konsole.so
#24 0x00007f71cea34790 in __libc_start_main (main=0x4007c0 <main>, argc=1, argv=0x7ffd197d1c58, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffd197d1c48) at libc-start.c:289
#25 0x00000000004007f9 in _start ()

Reported using DrKonqi
Comment 1 Christoph Cullmann 2015-10-05 13:07:30 UTC
That is a known Qt bug, display got turned off => bam


https://bugreports.qt.io/browse/QTBUG-42985