Bug 413608 - Text can't be copied to the clipboard after 30-40 days of uptime.
Summary: Text can't be copied to the clipboard after 30-40 days of uptime.
Status: RESOLVED UPSTREAM
Alias: None
Product: konsole
Classification: Applications
Component: copy-paste (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Konsole Developer
URL: https://bugreports.qt.io/browse/QTBUG...
Keywords:
: 420361 (view as bug list)
Depends on:
Blocks:
 
Reported: 2019-10-29 19:34 UTC by Mike
Modified: 2020-04-21 04:55 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Mike 2019-10-29 19:34:05 UTC 
SUMMARY

After 30-40 days of uptime and having several Konsole windows open for that time, eventually copying text to the clipboard stops working, but only from a Konsole window.

STEPS TO REPRODUCE
1. Open several Konsole windows, each with their own tabs.
2. Use the Konsole windows actively over a period of 30-40 days.
3. Select text in any of the Konsole windows, right-click on it, then click Copy. (using CTRL+SHIFT+C exhibits same behavior)
4. Try to paste copied text into another window, the only thing that is pasted is previously selected text from a different application. 

OBSERVED RESULT

Copying text to the clipboard from Konsole ceases to function after 30-40 days of uptime. 


EXPECTED RESULT

Expected to be able to copy text to the clipboard.



SOFTWARE/OS VERSIONS
Konsole: v17.12.3

Linux/KDE Plasma: Ubuntu 18.04 
KDE Plasma Version: 5.12.9
KDE Frameworks Version: 5.44.0
Qt Version: 5.9.5

ADDITIONAL INFORMATION

This issue has occurred for me for many years, across many versions of KDE. Maybe as long as 5 years.
Comment 1 Nate Graham 2019-10-29 21:37:07 UTC 
This is caused by a Qt bug that was fixed in version 5.12.3: https://bugreports.qt.io/browse/QTBUG-65145
Comment 2 Christoph Feck 2020-04-21 04:55:00 UTC 
*** Bug 420361 has been marked as a duplicate of this bug. ***