Bug 367827

Summary: Desktop session crash caused by kdeconnect
Product: [Applications] kdeconnect Reporter: lithi
Component: commonAssignee: Albert Vaca Cintora <albertvaka>
Status: RESOLVED FIXED    
Severity: grave CC: aleixpol, kde
Priority: NOR    
Version First Reported In: 0.4.2   
Target Milestone: ---   
Platform: Kubuntu   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description lithi 2016-08-26 02:21:11 UTC
When performing cutting/pasting operations in a desktop session it triggers something with kdeconnect and I see entries like this in syslog:

Aug 25 11:50:48 bodhi org.kde.kdeconnect[10441]: QXcbClipboard: SelectionRequest too old
Aug 25 11:52:11 bodhi org.kde.kdeconnect[10441]: message repeated 4902 times: [ QXcbClipboard: SelectionRequest too old]

The desktop system essentially freezes at this point and the system must be rebooted.  I solved the problem by uninstalling kdeconnect kdeconnect-plasma and rebooting.

Reproducible: Always

Steps to Reproduce:
1.  Set up KDEConnect to connect with other devices
2.  Perform copy/paste operations in a desktop session


Actual Results:  
Session freezes.

Expected Results:  
Session should not freeze.  Copy/paste operations should not cause crash.

I listed this as Grave as it kills the desktop session.
Comment 1 lithi 2016-08-26 02:24:27 UTC
Note that this seems related to this bug:  Bug 357885 - QXcbClipboard: SelectionRequest too old 
https://bugs.kde.org/show_bug.cgi?id=357885
Comment 2 lithi 2016-11-05 23:19:27 UTC
Am now using Ubuntu 16.10 "Yakkety" which has kdeconnect version 0.8-0ubuntu5 and this issue no longer occurs.
Comment 3 lithi 2016-11-05 23:21:35 UTC
I did not mark status as "resolved" since users on 16.04 LTS release may still be affected by it.
Comment 4 Benedikt Geißler 2016-11-05 23:27:30 UTC
Since summer I am using openSUSE Tumbleweed (currently with kdeconnect 1.0.1, 'kdeconnect-cli' says 1.0) now and did not experience this issue during the last weeks, too.
Comment 5 Aleix Pol 2018-01-16 22:43:46 UTC
Issue is fixed.