Bug 387202 - Copy and Paste stop working after 47 days
Summary: Copy and Paste stop working after 47 days
Status: RESOLVED UPSTREAM
Alias: None
Product: konsole
Classification: Applications
Component: copy-paste (show other bugs)
Version: 16.12.0
Platform: Debian stable Linux
: NOR normal
Target Milestone: ---
Assignee: Konsole Developer
URL: https://bugreports.qt.io/browse/QTBUG...
Keywords: investigated, triaged
: 402863 (view as bug list)
Depends on:
Blocks:
 
Reported: 2017-11-22 07:45 UTC by hjb
Modified: 2019-01-05 14:13 UTC (History)
6 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 hjb 2017-11-22 07:45:52 UTC
About 47 days after starting Konsole, Copy and Paste stop working. Selecting text by mouse or copying with ctrl+shift+c doesn't put the text into the copy buffer. Copying text in another program and trying to paste it into Konsole also doesn't work anymore. I suspect an overflowing 32 bit millisecond timestamp, although I have a 64 bit system. After restarting Konsole it works fine again for 47 days.
Comment 1 Egmont Koblinger 2017-11-23 22:10:28 UTC
What a beautiful bugreport :)

Windows 95 and 98 crashed after this uptime of the whole operating system. I never thought a desktop app could live for this long.

Note: the 32-bit unsigned overflow of milliseconds is after 49.7 days, not 47.

Could you by any chance check the behavior of some other apps after this long running time? I'm wondering, maybe KDE's (kwin's) Alt+F2 "run application" or something similar dialog box, or something from the desktop's right-click menu, assuming that it's part of a long-running process rather than a newly launched process there.

I blindly suspect that this might be an issue in some lower level component (kdelibs, Qt or X11) rather than konsole itself.

(Disclaimer: I'm not a konsole or kde developer.)
Comment 2 hjb 2017-11-24 06:05:40 UTC
Note that I don't use KDE, but LDXE and Openbox. So I don't have many KDE apps running for a longer time. But I just checked KOrganizer and it seems to have the same problem. I restarted it and the problem was gone. Before that, KOrganizer probably has been running as long as the system is up, currently 151 days.

For non-KDE-apps I didn't notice such problems. JEdit, Eclipse, Palemoon, Audacity and others are OK. So it may be a problem in KDE Frameworks 5.28 or Qt 5.7.

Regarding the time I maybe miscalculated the interval. If I remember correctly, I restarted Konsole on October 4, and the problem occured on Nov 22. That's 49 days. It could just fit although it looks like it happened a few hours too early ;-)
Comment 3 Egmont Koblinger 2017-11-24 08:55:01 UTC
> That's 49 days. It could just fit although it looks like it happened a
> few hours too early ;-)

One hour is from the DST change, the rest is measurement error :)
Comment 4 devsk 2018-01-09 19:32:37 UTC
This is a serious problem. I have VNC sessions that are never restarted unless security issues force a restart, and I used to be able to run them for months on end (one had an uptime of >300 days).

This issue started happening recently (in last one year or may be since I moved to KF5 like 1.5 yrs ago), it wasn't the case earlier.

How can we debug and make progress on it?
Comment 5 Marcin Gryszkalis 2018-01-21 20:32:03 UTC
I can confirm the problem.
konsole 17.08.3
copying died at day 49th :)
Comment 6 Marcin Gryszkalis 2018-01-21 21:54:47 UTC
I just tested other long-running apps and it seems to be the same for krusader, kgpg and krunner (alt-f2) but in clementine it works...

Also - in my case only copy stopped working (paste into these apps works w/o problems).
Comment 7 Kurt Hindenburg 2018-01-21 21:56:36 UTC
For reference:

https://bugreports.qt.io/browse/QTBUG-65145
https://bugs.kde.org/show_bug.cgi?id=377901

Underlying issue
Comment 8 Nate Graham 2018-01-21 22:10:46 UTC
Thanks Kurt. If we can't work around this somehow, should we mark this as RESOLVED UPSTREAM?
Comment 9 Kurt Hindenburg 2018-01-21 22:31:00 UTC
Let's use needsinfo rather than resolved - let's see if/when it is resolved upstream.


Feel free to reopen if there's somehow Konsole can work around.
Comment 10 Andrew Crouthamel 2018-09-19 14:40:41 UTC
This bug has had its resolution changed, but accidentally has been left in NEEDSINFO status. I am thus closing this bug and setting the status as RESOLVED to reflect the resolution change.
Comment 11 Christoph Feck 2019-01-05 14:13:00 UTC
*** Bug 402863 has been marked as a duplicate of this bug. ***