Bug 8593 - qlipper does not synchronise clipboards correctly
Summary: qlipper does not synchronise clipboards correctly
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-03 23:58 CET by Derek Jennings
Modified: 2013-01-06 22:48 CET (History)
1 user (show)

See Also:
Source RPM: qlipper-2.0.0-2.mga3
CVE:
Status comment:


Attachments
qlipper.spec for 2.0.1 (1.08 KB, text/plain)
2013-01-04 00:13 CET, Derek Jennings
Details

Description Derek Jennings 2013-01-03 23:58:02 CET
With qlipper it is not possible to copy to clipboard by mouse highlight/Control C and paste with centre button click/Control V interchangeably the way that Klipper can.

This upstream bug report describes the issue
http://code.google.com/p/qlipper/issues/detail?id=5

A fix was included in the latest stable release 2.0.1 but Cauldron is still on 2.0.0

I have compiled 2.0.1 myself and can confirm that the bug is fixed.
Comment 1 Derek Jennings 2013-01-04 00:13:57 CET
Created attachment 3308 [details]
qlipper.spec for 2.0.1

This is the spec file I used to compile qlipper-2.0.1 just in case it is any use to anyone.

The spec file for 2.0.0 did not work
Thierry Vignaud 2013-01-06 16:04:09 CET

CC: (none) => balcaen.john, nicolas.lecureuil

John Balcaen 2013-01-06 16:56:07 CET

CC: balcaen.john, nicolas.lecureuil => matteo.pasotti

Comment 2 Matteo Pasotti 2013-01-06 17:07:28 CET
work in progress

Status: NEW => ASSIGNED

Comment 3 Matteo Pasotti 2013-01-06 18:44:09 CET
Hello, qlipper-2.0.1-1.mga3 is now available from the repositories.

Closing this bug report as resolved fixed.
Thank you for reporting.

Status: ASSIGNED => RESOLVED
Resolution: (none) => FIXED

Comment 4 Derek Jennings 2013-01-06 22:48:25 CET
Confirmed qlipper-2.0.1-1.mga3 works great. Thats another bug fixed. Thanks..

Note You need to log in before you can comment on or make changes to this bug.