remmina/xfreerdp crashes when it becomes a target of 'remote control'

[urusha]

Remmina/xfreerdp session crashes when I'm trying to view/contol it using 'remote control' feature from another session on the same windows server. Tested with rdesktop on the other side which doesn't crash. It happens every time.

Actually, this bug report is a part of https://bugs.launchpad.net/ubuntu/+source/freerdp/+bug/1000356 that was partly fixed.

This issue affected every i386, amd64 (l)ubuntu 12.04 installation I tested.

This is a major issue for our corporate environment which stops us from migrating to the new Ubuntu LTS.

[Test Case]
- Start Remmina
- Connect to a random RDP server
- Start rdesktop or mstsc
- Connect to the same RDP server with another username (must be admin)
- Open taskmgr (Task Manager) with admin rights
- Go to the users, and click 'Remote Control' on the remmina session's user
=> Now Remmina will crash completely.

# LANG=C apt-cache policy libfreerdp1 freerdp-x11 remmina
libfreerdp1:
  Installed: 1.0.1-1ubuntu2.1
  Candidate: 1.0.1-1ubuntu2.1
  Version table:
 *** 1.0.1-1ubuntu2.1 0
        500 http://ru.archive.ubuntu.com/ubuntu/ precise-updates/main i386 Packages
        100 /var/lib/dpkg/status
     1.0.1-1ubuntu2 0
        500 http://ru.archive.ubuntu.com/ubuntu/ precise/main i386 Packages
freerdp-x11:
  Installed: 1.0.1-1ubuntu2.1
  Candidate: 1.0.1-1ubuntu2.1
  Version table:
 *** 1.0.1-1ubuntu2.1 0
        500 http://ru.archive.ubuntu.com/ubuntu/ precise-updates/main i386 Packages
        100 /var/lib/dpkg/status
     1.0.1-1ubuntu2 0
        500 http://ru.archive.ubuntu.com/ubuntu/ precise/main i386 Packages
remmina:
  Installed: 1.0.0-1ubuntu6.1
  Candidate: 1.0.0-1ubuntu6.1
  Version table:
 *** 1.0.0-1ubuntu6.1 0
        500 http://ru.archive.ubuntu.com/ubuntu/ precise-updates/main i386 Packages
        100 /var/lib/dpkg/status
     1.0.0-1ubuntu5 0
        500 http://ru.archive.ubuntu.com/ubuntu/ precise/main i386 Packages

[Jean-Louis Dupond (dupondje)]

Hi,

Any chance you can install freerdp-dbg and repost a backtrace with the debug symbols?
This way debugging should be easier :)

Thanks!
Jean-Louis

[Launchpad Janitor (janitor)]

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

[urusha (urusha)]

Hi! Here is the traces with dbg symbols.

[Stephan Diehl (stephan-diehl-4)]

this version fixes the problem:

https://launchpad.net/~freerdp-team/+archive/freerdp/+packages

freerdp - 1.0.1-1ubuntu2.1freerdp1~1042+27~precise1

[urusha (urusha)]

Confirming it's fixed. While remmina rdp plugin doesn't work at all for this build, freerdp doesn't seem to crash now (tested with defferent resolutions). Thanks. Any chance we'll get this fix in precise?

[penalvch (penalvch)]

urusha, 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