Bug 397063 - kwin crashed
Summary: kwin crashed
Status: RESOLVED DUPLICATE of bug 398977
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Neon Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2018-08-01 17:35 UTC by Ivan
Modified: 2019-03-01 21:21 UTC (History)
2 users (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 Ivan 2018-08-01 17:35:12 UTC
Application: kwin_x11 (5.13.4)

Qt Version: 5.11.1
Frameworks Version: 5.48.0
Operating System: Linux 4.15.0-29-generic x86_64
Distribution: KDE neon User Edition 5.13

-- Information about the crash:
- What I was doing when the application crashed:
kwin crashed when using display windows with active screen borders

The crash does not seem to be reproducible.

-- Backtrace:
Application: KWin (kwin_x11), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f5e5930b940 (LWP 1319))]

Thread 6 (Thread 0x7f5e24a05700 (LWP 3457)):
#0  0x00007f5e58d18811 in __GI_ppoll (fds=0x7f5e180009e8, nfds=1, timeout=<optimized out>, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:50
#1  0x00007f5e560ceb21 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x00007f5e560d01b2 in QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x00007f5e5607a5ba in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x00007f5e55eaf5e4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007f5e50a08195 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#6  0x00007f5e55eba727 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x00007f5e51d6b6ba in start_thread (arg=0x7f5e24a05700) at pthread_create.c:333
#8  0x00007f5e58d2441d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 5 (Thread 0x7f5e279d9700 (LWP 1449)):
#0  0x00007f5e58d18811 in __GI_ppoll (fds=0x7f5e20000b38, nfds=1, timeout=<optimized out>, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:50
#1  0x00007f5e560ceb21 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x00007f5e560d01b2 in QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x00007f5e5607a5ba in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x00007f5e55eaf5e4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007f5e50a08195 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#6  0x00007f5e55eba727 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x00007f5e51d6b6ba in start_thread (arg=0x7f5e279d9700) at pthread_create.c:333
#8  0x00007f5e58d2441d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 4 (Thread 0x7f5e1ffff700 (LWP 1386)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
#1  0x00007f5e54fffde4 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#2  0x00007f5e54fffe29 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Script.so.5
#3  0x00007f5e51d6b6ba in start_thread (arg=0x7f5e1ffff700) at pthread_create.c:333
#4  0x00007f5e58d2441d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 3 (Thread 0x7f5e34f51700 (LWP 1375)):
#0  0x00007f5e58d18811 in __GI_ppoll (fds=0x7f5e2c000ac8, nfds=1, timeout=<optimized out>, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:50
#1  0x00007f5e560ceb21 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x00007f5e560d01b2 in QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x00007f5e5607a5ba in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x00007f5e55eaf5e4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007f5e50a08195 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Qml.so.5
#6  0x00007f5e55eba727 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x00007f5e51d6b6ba in start_thread (arg=0x7f5e34f51700) at pthread_create.c:333
#8  0x00007f5e58d2441d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 2 (Thread 0x7f5e3767a700 (LWP 1359)):
#0  0x00007f5e58d18811 in __GI_ppoll (fds=0x7f5e3000bc68, nfds=1, timeout=<optimized out>, sigmask=0x0) at ../sysdeps/unix/sysv/linux/ppoll.c:50
#1  0x00007f5e560ceb21 in qt_safe_poll(pollfd*, unsigned long, timespec const*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#2  0x00007f5e560d01b2 in QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#3  0x00007f5e5607a5ba in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#4  0x00007f5e55eaf5e4 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#5  0x00007f5e4f915f35 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#6  0x00007f5e55eba727 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#7  0x00007f5e51d6b6ba in start_thread (arg=0x7f5e3767a700) at pthread_create.c:333
#8  0x00007f5e58d2441d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:109

Thread 1 (Thread 0x7f5e5930b940 (LWP 1319)):
[KCrash Handler]
#6  0x00007f5e5883e4ce in KWin::Workspace::workspaceEvent(xcb_generic_event_t*) () from /usr/lib/x86_64-linux-gnu/libkwin.so.5
#7  0x00007f5e5607918f in QAbstractEventDispatcher::filterNativeEvent(QByteArray const&, void*, long*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#8  0x00007f5e3e9bb674 in QXcbConnection::handleXcbEvent(xcb_generic_event_t*) () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#9  0x00007f5e3e9bc39b in QXcbConnection::processXcbEvents() () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#10 0x00007f5e560a9fb9 in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#11 0x00007f5e56e4939c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#12 0x00007f5e56e50ab0 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5
#13 0x00007f5e5607c228 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x00007f5e5607ee2e in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#15 0x00007f5e560cffd7 in QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x00007f5e3ea40cad in ?? () from /usr/lib/x86_64-linux-gnu/libQt5XcbQpa.so.5
#17 0x00007f5e5607a5ba in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x00007f5e560836c4 in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
#19 0x00007f5e58ff01f9 in kdemain () from /usr/lib/x86_64-linux-gnu/libkdeinit5_kwin_x11.so
#20 0x00007f5e58c3d830 in __libc_start_main (main=0x4006b0, argc=3, argv=0x7ffc15243738, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffc15243728) at ../csu/libc-start.c:291
#21 0x00000000004006e9 in _start ()

Possible duplicates by query: bug 396975, bug 396555, bug 396506, bug 396431, bug 396365.

Reported using DrKonqi
Comment 1 David Edmundson 2018-09-27 10:16:08 UTC

*** This bug has been marked as a duplicate of bug 398977 ***
Comment 2 Vlad Zahorodnii 2019-02-22 14:09:11 UTC
> display windows

Do you mean "Present Windows" effect? Also, out of curiosity what gpu do you have on your machine?
Comment 3 Ivan Garcia 2019-03-01 21:21:54 UTC
(In reply to Vlad Zagorodniy from comment #2)
> > display windows
> 
> Do you mean "Present Windows" effect? Also, out of curiosity what gpu do you
> have on your machine?

yes present windows sorry for my english, I have a Intel Pentium B950. Anyway that did not happend again