Menu
▾
▴
#82 ERROR: CLIPRDR error (type=5)
open
nobody
None
5
2012-11-29
2003-09-17
Anonymous
No
I am using latest cvs(9/17) on red hat 9 connecting to
a xp machine.
I noticed that rdesktop kept printing this error sometimes.
It greatly affects the performance of the system.
There is a method to produce this result:
open Excel,
input something in a cell,
copy the cell,
paste the cell anywhere,
save the doc.
Logged In: YES
user_id=10357
I am using 1.3.0 on RH7.3 connecting to xpsp1. I see this
error when copying using "QuickEdit" from a cygwin window.
If you need help testing a fix let me know and I'll grab an
update from cvs.
Logged In: NO
It is still the same for me with 1.3.0
Also, I got the message below while using windows
mediaplayer to play some mp3 on the net:
MIXER_WRITE(SOUND_MIXER_PCM): Invalid argument
It doesn't affect the playing though.
Logged In: YES
user_id=916821
We are running rdesktop 1.3.0 on a NetBSD system and on a
Sun SPARC/Solaris 8 system (compiled using pkgsrc),
connecting to Windows 2000 Terminal Server.
I have been able to reproduce this, with a workaround.
The problem occurs reproducibly if you cut or copy (not just
select)
something within Windows, using either the menu or ^C, then
select some text outside Windows.
The workaround is to copy (not just select) something else
within Windows.
The messages will stop until you next select something
outside Windows.
Further, if you disconnect then reconnect, the messages stop
more permanently (until you repeat the above sequence).
Logged In: YES
user_id=916821
We are running rdesktop 1.3.0 on a NetBSD system and on a
Sun SPARC/Solaris 8 system (compiled using pkgsrc),
connecting to Windows 2000 Terminal Server.
I have been able to reproduce this, with a workaround.
The problem occurs reproducibly if you cut or copy (not just
select)
something within Windows, using either the menu or ^C, then
select some text outside Windows.
The workaround is to copy (not just select) something else
within Windows.
The messages will stop until you next select something
outside Windows.
Further, if you disconnect then reconnect, the messages stop
more permanently (until you repeat the above sequence).
Logged In: YES
user_id=916821
We are running rdesktop 1.3.0 on a NetBSD system and on a
Sun SPARC/Solaris 8 system (compiled using pkgsrc),
connecting to Windows 2000 Terminal Server.
I have been able to reproduce this, with a workaround.
The problem occurs reproducibly if you cut or copy (not just
select)
something within Windows, using either the menu or ^C, then
select some text outside Windows.
The workaround is to copy (not just select) something else
within Windows.
The messages will stop until you next select something
outside Windows.
Further, if you disconnect then reconnect, the messages stop
more permanently (until you repeat the above sequence).
Logged In: YES
user_id=916821
We are running rdesktop 1.3.0 on a NetBSD system and on a
Sun SPARC/Solaris 8 system (compiled using pkgsrc),
connecting to Windows 2000 Terminal Server.
I have been able to reproduce this, with a workaround.
The problem occurs reproducibly if you cut or copy (not just
select)
something within Windows, using either the menu or ^C, then
select some text outside Windows.
The workaround is to copy (not just select) something else
within Windows.
The messages will stop until you next select something
outside Windows.
Further, if you disconnect then reconnect, the messages stop
more permanently (until you repeat the above sequence).
Logged In: YES
user_id=916821
We are running rdesktop 1.3.0 on a NetBSD system and on a
Sun SPARC/Solaris 8 system (compiled using pkgsrc),
connecting to Windows 2000 Terminal Server.
I have been able to reproduce this, with a workaround.
The problem occurs reproducibly if you cut or copy (not just
select)
something within Windows, using either the menu or ^C, then
select some text outside Windows.
The workaround is to copy (not just select) something else
within Windows.
The messages will stop until you next select something
outside Windows.
Further, if you disconnect then reconnect, the messages stop
more permanently (until you repeat the above sequence).