Bug 398772 - copying text crashes kwin_wayland, then black screen
Summary: copying text crashes kwin_wayland, then black screen
Status: RESOLVED FIXED
Alias: None
Product: kwin
Classification: Plasma
Component: platform-wayland-nested (show other bugs)
Version: 5.13.90
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-09-17 19:14 UTC by youduda
Modified: 2018-10-22 20:11 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
systemd-journal and gdb backtrace (35.96 KB, application/x-xz)
2018-09-17 19:14 UTC, youduda
Details
Backtrace with debug symbols (21.30 KB, text/x-log)
2018-09-18 19:40 UTC, youduda
Details

Note You need to log in before you can comment on or make changes to this bug.
Description youduda 2018-09-17 19:14:42 UTC
Created attachment 115048 [details]
systemd-journal and gdb backtrace

Copying any text in any application (tested: Console, Kate, Vivaldi, Dolphin) crashes kwin_wayland, then plasmashell, powerdevil and maybe more.

Tested versions: 5.13.5, 5.13.90

Sep 17 20:04:06: the usual crash of plasmashell immediately after login
Sep 17 20:05:19: copied some arbitrary letters with ctrl+c in Console, kwin_wayland crashes

generated full crashdumps:
20:04:07 plasmashell
20:05:21 org_kde_powerdevil
20:05:22 kwin_wayland
20:05:24 vivaldi_bin
If they are helpful, I can provide them.
Comment 1 Martin Flöser 2018-09-18 07:48:12 UTC
Please copy the backtrace of kwin into a comment of this report.
Comment 2 youduda 2018-09-18 15:18:25 UTC
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00007f4bc5fcc280 in KWayland::Server::DataSourceInterface::d_func() const () at /usr/lib/libKF5WaylandServer.so.5
#1  0x00007f4bc5fcc433 in KWayland::Server::DataSourceInterface::requestData(QString const&, int) () at /usr/lib/libKF5WaylandServer.so.5
#2  0x00007f4bc5fcb85e in  () at /usr/lib/libKF5WaylandServer.so.5
#3  0x00007f4bbdc331c8 in ffi_call_unix64 () at /usr/lib/libffi.so.6
#4  0x00007f4bbdc32c2a in ffi_call () at /usr/lib/libffi.so.6
#5  0x00007f4bc10e16ff in  () at /usr/lib/libwayland-server.so.0
#6  0x00007f4bc10de0a3 in  () at /usr/lib/libwayland-server.so.0
#7  0x00007f4bc10df702 in wl_event_loop_dispatch () at /usr/lib/libwayland-server.so.0
#8  0x00007f4bc5fcd32f in KWayland::Server::Display::Private::dispatch() () at /usr/lib/libKF5WaylandServer.so.5
#9  0x00007f4bc55960c0 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/libQt5Core.so.5
#10 0x00007f4bc55a1b7a in QSocketNotifier::activated(int, QSocketNotifier::QPrivateSignal) () at /usr/lib/libQt5Core.so.5
#11 0x00007f4bc55a1ed2 in QSocketNotifier::event(QEvent*) () at /usr/lib/libQt5Core.so.5
#12 0x00007f4bc5953e14 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5
#13 0x00007f4bc595b6e1 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5
#14 0x00007f4bc556c129 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5
#15 0x00007f4bc55bc635 in QEventDispatcherUNIXPrivate::activateSocketNotifiers() () at /usr/lib/libQt5Core.so.5
#16 0x00007f4bc55bc949 in QEventDispatcherUNIX::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5
#17 0x00007f4bb961c85e in  () at /usr/lib/qt/plugins/platforms/KWinQpaPlugin.so
#18 0x00007f4bc556adbc in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5
#19 0x00007f4bc55730b6 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5
#20 0x00005596c6adcd77 in  ()
#21 0x00007f4bc4da0223 in __libc_start_main () at /usr/lib/libc.so.6
#22 0x00005596c6add19e in _start ()
Comment 3 Martin Flöser 2018-09-18 17:07:35 UTC
Unfortunately the backtrace is lacking debug symbols. If you are able to reproduce please install debug packages and attach a new backtrace
Comment 4 youduda 2018-09-18 19:40:59 UTC
Created attachment 115086 [details]
Backtrace with debug symbols

I attached the backtrace as a file as currently there is not one of those rare moments, when copy/paste works.
kwin_wayland04.log: ctrl+c in konsole the word "debugging"

The coredumps from the past week (built version 5.13.5, 5.13.90 and master) have something in common in KWayland::Server::DataOfferInterface::Private::receiveCallback(): always mimeType="text/uri-list" and mostly fd=100.

One other thing I recognized: clearing the clipboard history in the taskbar clipboard widget crashes the system as reliable as copying text.
Comment 5 Patrick Silva 2018-09-20 15:14:20 UTC
it also crashes randomly on neon dev unstable when I copy files in dolphin by presing ctrl+c.
Comment 6 youduda 2018-10-01 17:10:14 UTC
It looks like the latest Qt 5.11.2 update fixed the issue. Now 2 weeks without crash on copy+paste.
Comment 7 Patrick Silva 2018-10-01 17:16:44 UTC
Yesterday Wayland session crashed on my Arch Linux running Qt 5.11.2
after I copied text in Opera internet browser.
Comment 8 Patrick Silva 2018-10-10 15:24:11 UTC
same problem reported again as bug 399605
Comment 9 Patrick Silva 2018-10-22 20:11:57 UTC
today wayland session crashed twice after I copy text in konsole and info center.


SOFTWARE VERSIONS
Operating System: Arch Linux 
KDE Plasma Version: 5.14.1
Qt Version: 5.12.0 beta2
KDE Frameworks Version: 5.51.0