Bug 367830 - Plasma hangs after selecting text on PhpStorm terminal
Summary: Plasma hangs after selecting text on PhpStorm terminal
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (show other bugs)
Version: 5.7.3
Platform: Neon Linux
: NOR crash
Target Milestone: 1.0
Assignee: David Edmundson
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2016-08-26 06:14 UTC by Märt Rang
Modified: 2018-10-27 02:24 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
partial xsession-errors log (6.41 KB, text/plain)
2016-09-04 11:02 UTC, Märt Rang
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Märt Rang 2016-08-26 06:14:56 UTC
This is really weird bug, but yeah, if I select text on PhpStorm terminal, plasma hangs for about minute, only thing I can do is to alt+tab, everything else is unresponsive.

Reproducible: Always

Steps to Reproduce:
1. Select text on PhpStorm terminal
2.
3.

Actual Results:  
Plasma hangs, can't click on panel or icons on desktop. If I close a window, taskbar entry is not removed until it starts to be responsive again.

Expected Results:  
Does not hang when selecting text on terminal.

Two monitor setup. PhpStorm 2016.2.1
I have not tried yet other Intellij products or similar java IDE-s (i.e eclipse).
Comment 1 Märt Rang 2016-09-04 07:51:57 UTC
Installed KDE Neon packages, I can still reproduce it.
Comment 2 Kai Uwe Broulik 2016-09-04 07:58:23 UTC
Can you provide a backtrace?
Comment 3 Märt Rang 2016-09-04 11:02:23 UTC
Created attachment 100925 [details]
partial xsession-errors log

Tried to reproduce this issue and xsession-errors log seem to give a hint:
QXcbClipboard::setMimeData: Cannot set X11 selection owner
Comment 4 Ondřej Hruška 2016-11-01 22:08:37 UTC
I also have this issue, 100% repro rate. I'm on Arch Linux with 5.8.3, PhpStorm 2016.2.2

The freeze depends on how much text I select in the terminal, few chars = 10s, few lines = few minutes. 

Current workaround is a hotkey bound to "killall plasmashell && plasmashell", but it's a super dirty fix & takes a few secs.

Is there anything I can try to hasten the fixing of this bug? I can provide any logs etc, if you tell me how.
Comment 5 David Edmundson 2016-11-02 14:46:21 UTC
What we need is to know what on Earth phpstorm is putting into the clipboard (and which clipboard)

xclip -o    

after seelcting text might be enough to narrow this down.

Ideally for all -selection options.


btw, if you need to work round it, disable klipper
Comment 6 Ondřej Hruška 2016-11-02 18:07:15 UTC
Here is the output of xclip with various options - nothing out of line from the looks of it:

~ $ xclip -o

~ $ xclip -selection primary -o

~ $ xclip -selection secondary -o
Error: target STRING not available
~ $ xclip -selection clipboard -o
  PID TTY          TIME CMD
 9567 pts/1    00:00:00 bash
16565 pts/1    00:00:00 ps
~ $ xclip -selection buffer-cut -o
~ $


And here's a plasmashell backtrace I captured with gdb while it was frozen:

#0  0x00007fbf9cf910b3 in select () at /usr/lib/libc.so.6
#1  0x00007fbf90175351 in  () at /usr/lib/libQt5XcbQpa.so.5
#2  0x00007fbf9017596f in  () at /usr/lib/libQt5XcbQpa.so.5
#3  0x00007fbf90177438 in  () at /usr/lib/libQt5XcbQpa.so.5
#4  0x00007fbf9ddbc6ab in QInternalMimeData::formats() const () at /usr/lib/libQt5Gui.so.5
#5  0x00007fbf90177125 in  () at /usr/lib/libQt5XcbQpa.so.5
#6  0x00007fbf9ddbc5c6 in QInternalMimeData::hasFormat(QString const&) const () at /usr/lib/libQt5Gui.so.5
#7  0x00007fbf9d882693 in QMimeData::hasUrls() const () at /usr/lib/libQt5Core.so.5
#8  0x00007fbf9d882742 in QMimeData::hasText() const () at /usr/lib/libQt5Core.so.5
#9  0x00007fbfa1665d18 in QQuickTextInput::q_canPasteChanged() () at /usr/lib/libQt5Quick.so.5
#10 0x00007fbfa1756779 in  () at /usr/lib/libQt5Quick.so.5
#11 0x00007fbf9d888659 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/libQt5Core.so.5
#12 0x00007fbf9ddb88e9 in QClipboard::emitChanged(QClipboard::Mode) () at /usr/lib/libQt5Gui.so.5
#13 0x00007fbf901747ae in  () at /usr/lib/libQt5XcbQpa.so.5
#14 0x00007fbf9ddb8677 in QClipboard::setMimeData(QMimeData*, QClipboard::Mode) () at /usr/lib/libQt5Gui.so.5
#15 0x00007fbed524178a in  () at /usr/lib/qt/plugins/plasma/dataengine/plasma_engine_clipboard.so
#16 0x00007fbf9d8889ce in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/libQt5Core.so.5
#17 0x00007fbf9e10889e in QClipboard::changed(QClipboard::Mode) () at /usr/lib/libQt5Gui.so.5
#18 0x00007fbf90175bb0 in  () at /usr/lib/libQt5XcbQpa.so.5
#19 0x00007fbf9017bd98 in QXcbConnection::handleXcbEvent(xcb_generic_event_t*) () at /usr/lib/libQt5XcbQpa.so.5
#20 0x00007fbf9017c8a5 in QXcbConnection::processXcbEvents() () at /usr/lib/libQt5XcbQpa.so.5
#21 0x00007fbf9d8894b9 in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5
#22 0x00007fbf9e7c7e0c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5
#23 0x00007fbf9e7cf581 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5
#24 0x00007fbf9d85cde0 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5
#25 0x00007fbf9d85f56d in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt5Core.so.5
#26 0x00007fbf9d8b1303 in  () at /usr/lib/libQt5Core.so.5
#27 0x00007fbf98252587 in g_main_context_dispatch () at /usr/lib/libglib-2.0.so.0
#28 0x00007fbf982527f0 in  () at /usr/lib/libglib-2.0.so.0
#29 0x00007fbf9825289c in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0
#30 0x00007fbf9d8b170f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5
#31 0x00007fbf9d85b23a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5
#32 0x00007fbf9d86373c in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5
#33 0x000000000041c8b2 in  ()
#34 0x00007fbf9ced0291 in __libc_start_main () at /usr/lib/libc.so.6
#35 0x000000000041cc3a in _start ()
Comment 7 Andrew Crouthamel 2018-09-26 22:21:42 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 set the bug status 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 8 Andrew Crouthamel 2018-10-27 02:24:13 UTC
Dear Bug Submitter,

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!