remmina crashed with SIGSEGV in remmina_plugin_rdpui_rect()

[Aurimas Fišeras]

Binary package hint: remmina

How to reproduce:
Desktop resolution 1440x900.
Connect to Windows 2003 TS with Remmina using full screen.
Open Terminal Services Manager.
Try to Remote control other session with higher resolution (1280x1024).
Crash.

Trying to remote control other session with lower resolution (1024x768) works.

Both scenarios work with tsclient.

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: remmina 0.8.0-1
ProcVersionSignature: Ubuntu 2.6.35-20.29-generic 2.6.35.4
Uname: Linux 2.6.35-20-generic x86_64
Architecture: amd64
CheckboxSubmission: 73777fa81c317293f664ff2d22bf7673
CheckboxSystem: bb422ca46d02494cdbc459927a98bc2f
CrashCounter: 1
Date: Thu Sep 9 13:47:38 2010
ExecutablePath: /usr/bin/remmina
ProcCmdline: remmina -c /home/username/.remmina/srvu.remmina
ProcEnviron:
 LANG=lt_LT.UTF-8
 LANGUAGE=lt_LT:lt:en_GB:en
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f20040a7d16 <remmina_plugin_rdpui_rect+246>: mov %cx,(%rax)
 PC (0x7f20040a7d16) ok
 source "%cx" ok
 destination "(%rax)" (0x7f1ffc567470) in non-writable VMA region: 0x7f1ffc567000-0x7f1ffc568000 ---p None
 Stack memory exhausted (SP below stack segment)
SegvReason: writing VMA None
Signal: 11
SourcePackage: remmina
StacktraceTop:
 remmina_plugin_rdpui_rect (inst=<value optimised out>, x=0, y=144, cx=1, cy=806, colour=<value optimised out>) at //usr/include/bits/string3.h:52
 process_rect (orders=0x18a0f70, s=0x18a0e10, num_orders=<value optimised out>) at orders.c:377
 process_orders (orders=0x18a0f70, s=0x18a0e10, num_orders=<value optimised out>) at orders.c:1665
 process_update_pdu (rdp=0x1a00470, deactivated=<value optimised out>) at rdp.c:1192
 process_data_pdu (rdp=0x1a00470, deactivated=<value optimised out>) at rdp.c:1259
Title: remmina crashed with SIGSEGV in remmina_plugin_rdpui_rect()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 remmina_plugin_rdpui_rect (inst=<value optimized out>, x=0, y=144, cx=1,
 process_orders (orders=0x18a0f70, s=0x18a0e10,
 rdp_loop (rdp=0x1a00470,
 l_rdp_check_fds (inst=<value optimized out>)
 remmina_plugin_rdp_main_loop (

[Launchpad Janitor (janitor)]

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

[penalvch (penalvch)]

Aurimas Fišeras, thank you for reporting this bug to Ubuntu. Mavericks reached EOL on April 10, 2012.
See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases

Is this an issue on a supported release? If so, 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