remmina crashs when coping an image

[Mike]

This began about a week ago. I use Remmana to RDP into Windows 7. When using the Windows Snipping Tool, or when I select a region in MSPAINT and try to copy it into my clipboard buffer, Remmana locks up. I usually have to force-quit the application. Other times it just dies. After this happens I am unable to RDP back into the W7 box for up to five minutes as Windows complains that it is processing another user logon. This is quite disruptive to my work.

For the record, I do not use the clipboard in Remmina to copy images from W7 to my host OS because it is entirely unreliable. I onlt copy images within W7 to be pasted within W7. Copy/Paste generally works very poorly within Remmina so I'm lucky to get text to copy between the remote and host systems.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: remmina 1.0.0-1ubuntu6.1
ProcVersionSignature: Ubuntu 3.2.0-45.70-generic 3.2.44
Uname: Linux 3.2.0-45-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.2
Architecture: amd64
Date: Tue Jun 11 08:26:11 2013
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120822.4)
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: remmina
UpgradeStatus: No upgrade log present (probably fresh install)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Mikael Hjelm (j-m-hjelm)]

I have a vague feeling that this affects other things like undo as well.
The problem seems to be mitigated by disabling clipboard sync under the advanced tab in the connection profile.

[penalvch (penalvch)]

Mike, thank you for reporting this and helping make Ubuntu better. However, your crash report is missing. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer. First, execute at a terminal:
cd /var/crash && sudo rm * ; sudo apt-get update && sudo apt-get -y upgrade && sudo service apport start force_start=1

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

Now reproduce the crash, then open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'. If you run the command against the crash report and a window pops up asking you to report this, but then never opens a new report, you would be affected by https://bugs.launchpad.net/ubuntu/+source/apport/+bug/994921 . In order to WORKAROUND this, one would need to open the following file via a command line:
sudo nano /etc/apport/crashdb.conf

and comment out the line:
'problem_types': ['Bug', 'Package'],

by changing it to:
# 'problem_types': ['Bug', 'Package'],

Save, close, and try to file the crash report again via:
ubuntu-bug /var/crash/_my_crash_report.crash

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently.

Please do not attach your crash report manually to this report and reopen it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs