Bug 1017309 - line endings are wrong when copying from 3.3 windows client to 3.2 windows guest
Summary: line endings are wrong when copying from 3.3 windows client to 3.2 windows guest
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: mingw-virt-viewer
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: Marc-Andre Lureau
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-09 15:33 UTC by David Jaša
Modified: 2013-10-10 10:45 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-10-09 15:49:37 UTC
oVirt Team: ---
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description David Jaša 2013-10-09 15:33:37 UTC 
Description of problem:
when copying text from 3.3 client to a guest with 3.2 tools, line endings are wrong (presumably lf). The opposite direction works correctly.

Version-Release number of selected component (if applicable):
agent from RHEV Tools 3.2 
mingw-virt-viewer-0.5.6-6.el6_64 (windows 7 32b)

How reproducible:
always

Steps to Reproduce:
1. copy some text with line breaks in a 3.3 client
2. paste it using Windows guest with 3.2 tools
3.

Actual results:
line endings are not displayed (but after that pasted text is selected & copied again & pasted back to the client, line endings are correct again)

Expected results:
line endings are correct

Additional info:
Comment 1 Marc-Andre Lureau 2013-10-09 15:49:37 UTC 
This is expected, and should be fixed with the new agent and crlf conversion.

The windows client with old agent will not perform \n  -> crlf conversion and sends \n-ending text (windows gtk+ always use utf8 \n ending clipboard text data).

Imho, it's not interesting changing this in old agent, as you will break the case windows->linux/utf8 when fixing the windows->windows case.

closing as wontfix for now
Note You need to log in before you can comment on or make changes to this bug.