Remmina crashes when trying to connect to a users rdp session in w28k

[Alexander Marx]

When i use remmina 1.0.0-1ubuntu6 and connect to a w2k8 Terminalserver as admin and i want to remotesteer a users rdp session remina crashes without any logs or entries in /var/log/messages.
Simple rdp Connection to the server is working. (But it hangs often when trying to connect through openvpn)

Seems to be a bug in remmina with libfreerdp 1.0.1-1ubuntu2.

[Kyle (kolinuxtech)]

I can confirm that this is also the case with Windows Server 2003 Terminal Servers. This is called "shadowing" another user's session to help them with a problem or to view another administrator's session so both professionals can view the issue at hand. I do this nearly everyday and every single time I try it Reminna crashes immediately and usually doesn't come up with a crash dialog asking to send the details to the developers. This bug exists in Reminna since Ubuntu Precise' release until now with all updates in between applied as I regularly apply updates to see if certain issues are repaired.

This is an extemely simply issue to reproduce as all it takes is shadowing another user's terminal server session on either Windows Server 2003 or Windows Server 2008 and reminna crashes instantly or within seconds after hanging for a moment.

[Kyle (kolinuxtech)]

Also, I'd like to add then when rdesktop is used just by itself it IS possible to shadow a session in terminal services albeit very slow and clumsy. These problems didn't exist in the original rdesktop...I'm all for forks of a project when it isn't keeping up with the times but stability and usability still have to be at the top of the list.

[Kyle (kolinuxtech)]

I am easily able confirm this bug and easily reproduce it.

[penalvch (penalvch)]

Alexander Marx, 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