Ubuntu
remmina package

Remmina crashed under connection via RDP

Bug #985645 reported by Bjorn Ryborg on 2012-04-19

This bug affects 7 people

Affects		Status	Importance	Assigned to	Milestone
	remmina (Ubuntu)	Invalid	Undecided	Unassigned

Bug Description

Crashed when trying to connect via RDP:

Color dept 32 bit. Using client resolution. Best quality and Security set to RDP.

From terminal;

bjorn@bjorn-virtual-machine:~$ remmina
Remmina plugin RDP (type=Protokol) registered.
Remmina plugin RDPF (type=fil) registered.
Remmina plugin RDPS (type=Præference) registered.
Remmina plugin VNC (type=Protokol) registered.
Remmina plugin VNCI (type=Protokol) registered.
Remmina plugin SFTP (type=Protokol) registered.
Remmina plugin SSH (type=Protokol) registered.
connected to sccm40:3389
invalid glyph at cache index: 9 in cache id: 6
invalid glyph at cache index: 9 in cache id: 6
invalid glyph at cache index: 9 in cache id: 6
invalid glyph at cache index: 9 in cache id: 6
invalid glyph at cache index: 9 in cache id: 6
invalid glyph at cache index: 10 in cache id: 6
invalid glyph at cache index: 10 in cache id: 6
invalid glyph at cache index: 10 in cache id: 6
invalid glyph at cache index: 10 in cache id: 6
invalid glyph at cache index: 10 in cache id: 6
invalid glyph at cache index: 11 in cache id: 6
invalid glyph at cache index: 12 in cache id: 6
invalid glyph at cache index: 13 in cache id: 6
invalid glyph at cache index: 14 in cache id: 6
invalid glyph at cache index: 14 in cache id: 6
invalid glyph at cache index: 14 in cache id: 6
invalid glyph at cache index: 14 in cache id: 6
invalid glyph at cache index: 15 in cache id: 6
invalid glyph at cache index: 15 in cache id: 6
invalid glyph at cache index: 15 in cache id: 6
invalid glyph at cache index: 15 in cache id: 6
invalid glyph at cache index: 16 in cache id: 6
invalid glyph at cache index: 17 in cache id: 6
invalid glyph at cache index: 18 in cache id: 6
invalid glyph at cache index: 19 in cache id: 6
invalid glyph at cache index: 20 in cache id: 6
invalid glyph at cache index: 21 in cache id: 6
invalid glyph at cache index: 22 in cache id: 6
invalid glyph at cache index: 23 in cache id: 6
invalid glyph at cache index: 24 in cache id: 6
invalid glyph at cache index: 25 in cache id: 6
invalid glyph at cache index: 21 in cache id: 6
invalid glyph at cache index: 22 in cache id: 6
invalid glyph at cache index: 23 in cache id: 6
invalid glyph at cache index: 24 in cache id: 6
invalid glyph at cache index: 25 in cache id: 6
invalid glyph at cache index: 26 in cache id: 6
invalid glyph at cache index: 21 in cache id: 6
invalid glyph at cache index: 22 in cache id: 6
invalid glyph at cache index: 23 in cache id: 6
invalid glyph at cache index: 24 in cache id: 6
invalid glyph at cache index: 25 in cache id: 6
invalid glyph at cache index: 21 in cache id: 6
invalid glyph at cache index: 22 in cache id: 6
invalid glyph at cache index: 23 in cache id: 6
invalid glyph at cache index: 24 in cache id: 6
invalid glyph at cache index: 25 in cache id: 6
invalid glyph at cache index: 26 in cache id: 6
invalid glyph at cache index: 21 in cache id: 6
invalid glyph at cache index: 22 in cache id: 6
invalid glyph at cache index: 23 in cache id: 6
invalid glyph at cache index: 24 in cache id: 6
invalid glyph at cache index: 25 in cache id: 6
invalid glyph at cache index: 26 in cache id: 6
invalid glyph at cache index: 16 in cache id: 6
invalid glyph at cache index: 17 in cache id: 6
invalid glyph at cache index: 18 in cache id: 6
invalid glyph at cache index: 19 in cache id: 6
invalid glyph at cache index: 20 in cache id: 6
invalid glyph at cache index: 16 in cache id: 6
invalid glyph at cache index: 17 in cache id: 6
invalid glyph at cache index: 18 in cache id: 6
invalid glyph at cache index: 19 in cache id: 6
invalid glyph at cache index: 20 in cache id: 6
invalid glyph at cache index: 27 in cache id: 6
invalid glyph at cache index: 16 in cache id: 6
invalid glyph at cache index: 17 in cache id: 6
invalid glyph at cache index: 18 in cache id: 6
invalid glyph at cache index: 19 in cache id: 6
invalid glyph at cache index: 20 in cache id: 6
invalid glyph at cache index: 16 in cache id: 6
invalid glyph at cache index: 17 in cache id: 6
invalid glyph at cache index: 18 in cache id: 6
invalid glyph at cache index: 19 in cache id: 6
invalid glyph at cache index: 20 in cache id: 6
invalid glyph at cache index: 27 in cache id: 6
invalid glyph at cache index: 16 in cache id: 6
invalid glyph at cache index: 17 in cache id: 6
invalid glyph at cache index: 18 in cache id: 6
invalid glyph at cache index: 19 in cache id: 6
invalid glyph at cache index: 20 in cache id: 6
invalid glyph at cache index: 27 in cache id: 6
invalid brush (0 bpp) at index: 0x0000
Segmentfejl (core dumped)
bjorn@bjorn-virtual-machine:~$

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: remmina 1.0.0-1ubuntu5
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic x86_64
ApportVersion: 2.0.1-0ubuntu5
Architecture: amd64
Date: Thu Apr 19 15:08:07 2012
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
ProcEnviron:
PATH=(custom, no user)
LANG=da_DK.UTF-8
SHELL=/bin/bash
SourcePackage: remmina
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

Bjorn Ryborg (bjorn-ryborg) wrote on 2012-04-19:

Dependencies.txt Edit (2.5 KiB, text/plain; charset="utf-8")

Revision history for this message

Bjorn Ryborg (bjorn-ryborg) wrote on 2012-04-19:

The problem apears in screen resolutions over 1280x960 and full screen.
1280x960 in windowed mode works well.

Revision history for this message

Launchpad Janitor (janitor) wrote on 2012-06-26:

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

Changed in remmina (Ubuntu):
status:	New → Confirmed

Revision history for this message

Damir Butmir (d4m1r2) wrote on 2012-06-26:

I am seeing this same issue. Using Ubuntu 12.04 LTS to connect to a windows XP machine over RDP using Remmina and it crashes randomly (both remote and local machine set to us 1920x1080).

Linux damir-ubuntu 3.2.0-25-generic #40-Ubuntu SMP Wed May 23 20:30:51 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

Revision history for this message

Andy Barr (ajbarr) wrote on 2012-09-08:

I also noticed the same issue on Ubuntu 12.04 LTS. I had even installed remmina from 1.0.0-1ubuntu6.2 from precise-proposed but still had the problem.

As a work around I uninstalled all of remmina and manually downloaded the debs for remmina 0.9.3. I don't have any issues now. These are the files I installed for 12.04LST x64.

libfreerdp0_0.8.2-2_amd64.deb
libfreerdp-plugins-standard_0.8.2-2_amd64.deb
remmina_0.9.3-2_amd64.deb
remmina-dev_0.9.3-2_all.deb
remmina-plugin-data_0.9.2-2_all.deb
remmina-plugin-rdp_0.9.2-2_amd64.deb

You can download these debs from here, https://launchpad.net/ubuntu/oneiric/amd64

Last after they are downloaded you should lock these versions otherwise they will get upgraded the next time you upgrade your machine. Install synaptic if it isn't already installed. Then follow this procedure making sure to lock all the files you manually installed,
http://www.ubuntugeek.com/how-to-lock-package-versions-from-synaptic-package-manager.html

Revision history for this message

Damir Butmir (d4m1r2) wrote on 2012-09-11:

Thanks so much Andy!! I can confirm doing what you explain above has fixed all my Remmina issues....My remote keyboard shortcuts now work AND it hasn't even disconnected once yet....Thanks again!

Damir

Revision history for this message

Aaron Roydhouse (aaron-roydhouse) wrote on 2012-09-21:

Sweet! Thanks Andy. 'Upgrading' to 0.9.3 has fix all the Remmina problem I was having; the black on launch, the copy and paste, the constant lock-ups, disconnections, and crashing. It was so bad I had already switched back to rdesktop. All fixed now!

I should have known as soon as Ubuntu chose Remmina as its official app I was in trouble; a syndrome now know as the 'Unity Effect' :-)

Revision history for this message

Mustafa (alajal) wrote on 2012-11-01:

Hi,

I'm using updated version 0.9.99.1 but still I encounter the crash issue. It was workgin perfectly when it suddently crashed. Changing the resolutions makes it work but it again crashes randomly.

Revision history for this message

Mustafa (alajal) wrote on 2012-11-01:

Download full text (5.8 KiB)

I'm using Ubuntu 12.04

My crash info from terminal

I'm using Ubuntu 12.04

My crash info from terminal

invalid glyph at cache index: 29 in cache id: 6
invalid glyph at cache index: 0 in cache id: 6
invalid glyph at cache index: 0 in cache id: 6
invalid glyph at cache index: 0 in cache id: 6
invalid glyph at cache index: 0 in cache id: 6
invalid glyph at cache index: 0 in cache id: 6
invalid glyph at cache index: 1 in cache id: 6
invalid glyph at cache index: 1 in cache id: 6
invalid glyph at cache index: 1 in cache id: 6
invalid glyph at cache index: 1 in cache id: 6
invalid glyph at cache index: 1 in cache id: 6
invalid glyph at cache index: 2 in cache id: 6
invalid glyph at cache index: 2 in cache id: 6
invalid glyph at cache index: 2 in cache id: 6
invalid glyph at cache index: 3 in cache id: 6
invalid glyph at cache index: 3 in cache id: 6
invalid glyph at cache index: 3 in cache id: 6
invalid glyph at cache index: 4 in cache id: 6
invalid glyph at cache index: 4 in cache id: 6
invalid glyph at cache index: 4 in cache id: 6
invalid glyph at cache index: 4 in cache id: 6
invalid glyph at cache index: 4 in cache id: 6
invalid glyph at cache index: 0 in cache id: 5
invalid glyph at cache index: 0 in cache id: 5
invalid glyph at cache index: 0 in cache id: 5
invalid glyph at cache index: 0 in cache id: 5
invalid glyph at cache index: 0 in cache id: 5
invalid glyph at cache index: 5 in cache id: 6
invalid glyph at cache index: 6 in cache id: 6
invalid glyph at cache index: 7 in cache id: 6
invalid glyph at cache index: 7 in cache id: 6
invalid glyph at cache index: 7 in cache id: 6
invalid glyph at cache index: 7 in cache id: 6
invalid glyph at cache index: 7 in cache id: 6
invalid glyph at cache index: 8 in cache id: 6
invalid glyph at cache index: 8 in cache id: 6
invalid glyph at cache index: 8 in cache id: 6
invalid glyph at cache index: 8 in cache id: 6
invalid glyph at cache index: 8 in cache id: 6
invalid glyph at cache index: 9 in cache id: 6
invalid glyph at cache index: 9 in cache id: 6
invalid glyph at cache index: 9 in cache id: 6
invalid glyph at cache index: 9 in cache id: 6
invalid glyph at cache index: 9 in cache id: 6
invalid glyph at cache index: 10 in cache id: 6
invalid glyph at cache index: 10 in cache id: 6
invalid glyph at cache index: 10 in cache id: 6
invalid glyph at cache index: 10 in cache id: 6
invalid glyph at cache index: 10 in cache id: 6
invalid glyph at cache index: 11 in cache id: 6
invalid glyph at cache index: 12 in cache id: 6
invalid glyph at cache index: 13 in cache id: 6
invalid glyph at cache index: 14 in cache id: 6
invalid glyph at cache index: 14 in cache id: 6
invalid glyph at cache index: 14 in cache id: 6
invalid glyph at cache index: 14 in cache id: 6
invalid glyph at cache index: 15 in cache id: 6
invalid glyph at cache index: 15 in cache id: 6
invalid glyph at cache index: 15 in cache id: 6
invalid glyph at cache index: 15 in cache id: 6
invalid glyph at cache index: 16 in cache id: 6
invalid glyph at cache index: 17 in cache id: 6
invalid glyph at cache index: 18 in cache id: 6
invalid glyph at cache index: 19 in cache id: 6
invalid glyph at cache index: 20 in cache id: 6
invalid glyph at cache index: 21 in cache id: 6
invalid glyph at cache index: 22 in cache id: 6
invalid glyph at cache index: 23 in cache id: 6
invalid glyph at cache index: 24 in cache id: 6
invalid glyph at cache index: 25 in cache id: 6
invalid glyph at cache index: 21 in cache id: 6
invalid glyph at cache index: 22 in cache id: 6
invalid glyph at cache index: 23 in cache id: 6
invalid glyph at cache index: 24 in cache id: 6
invalid glyph at cache index: 25 in cache id: 6
invalid glyph at cache index: 26 in cache id: 6
invalid glyph at cache index: 21 in cache id: 6
invalid glyph at cache index: 22 in cache id: 6
invalid glyph at cache index: 23 in cache id: 6
invalid glyph at cache index: 24 in cache id: 6
invalid glyph at cache index: 25 in cache id: 6
invalid glyph at cache index: 21 in cache id: 6
invalid glyph at cache index: 22 in cache id: 6
invalid glyph at cache index: 23 in cache id: 6
invalid glyph at cache index: 24 in cache id: 6
invalid glyph at cache index: 25 in cache id: 6
invalid glyph at cache index: 26 in cache id: 6
invalid glyph at cache index: 21 in cache id: 6
invalid glyph at cache index: 22 in cache id: 6
invalid glyph at cache index: 23 in cache id: 6
invalid glyph at cache index: 24 in cache id: 6
invalid glyph at cache index: 25 in cache id: 6
invalid glyph at cache index: 26 in cache id: 6
invalid glyph at cache index: 16 in cache id: 6
invalid glyph at cache index: 17 in cache id: 6
invalid glyph at cache index: 18 in cache id: 6
invalid glyph at cache index: 19 in cache id: 6
invalid glyph at cache index: 20 in cache id: 6
invalid glyph at cache index: 16 in cache id: 6
invalid glyph at cache index: 17 in cache id: 6
invalid glyph at cache index: 18 in cache id: 6
invalid glyph at cache index: 19 in cache id: 6
invalid glyph at cache index: 20 in cache id: 6
invalid glyph at cache index: 27 in cache id: 6
invalid glyph at cache index: 16 in cache id: 6
invalid glyph at cache index: 17 in cache id: 6
invalid glyph at cache index: 18 in cache id: 6
invalid glyph at cache index: 19 in cache id: 6
invalid glyph at cache index: 20 in cache id: 6
invalid glyph at cache index: 16 in cache id: 6
invalid glyph at cache index: 17 in cache id: 6
invalid glyph at cache index: 18 in cache id: 6
invalid glyph at cache index: 19 in cache id: 6
invalid glyph at cache index: 20 in cache id: 6
invalid glyph at cache index: 27 in cache id: 6
invalid glyph at cache index: 16 in cache id: 6
invalid glyph at cache index: 17 in cache id: 6
invalid glyph at cache index: 18 in cache id: 6
invalid glyph at cache index: 19 in cache id: 6
invalid glyph at cache index: 20 in cache id: 6
invalid glyph at cache index: 27 in cache id: 6
invalid brush (0 bpp) at index: 0x0000
Segmentation fault (core dumped)

Revision history for this message

Sean DS (se4n-1) wrote on 2013-03-02:

#10

This affects me in 12.04 in 1920x1080 full screen mode, I have to do crtl+sysrq+REISUB every time.

Andy, your fix worked very well for me, thanks very much, hopefully this will be fixed by the devs as it's a pretty catastrophic issue!

Revision history for this message

itvrd (itvrd2) wrote on 2013-12-06:

#11

still actual

Revision history for this message

penalvch (penalvch) wrote on 2014-12-15:

#12

Bjorn Ryborg, 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

Changed in remmina (Ubuntu):
status:	Confirmed → Invalid

Revision history for this message

Bjorn Ryborg (bjorn-ryborg) wrote on 2014-12-15: Re: [Bug 985645] Re: Remmina crashed under connection via RDP

#13

Hi
I do not have this bug in my current system. Ubuntu 14.04 LTS (X64), so it
must have been fixed :)

Med Venlig Hilsen
Bjørn Ryborg

Gammel Skolevej 8, Tandslet, DK-6470 Sydals
Tlf: +45 3694 9898 - E-mail: <email address hidden>

2014-12-15 9:03 GMT+01:00 Christopher M. Penalver <
<email address hidden>>:
>
> Bjorn Ryborg, 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
>
> ** Changed in: remmina (Ubuntu)
> Status: Confirmed => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/985645
>
> Title:
> Remmina crashed under connection via RDP
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/985645/+subscriptions
>

Hi
I do not have this bug in my current system. Ubuntu 14.04 LTS (X64), so it
must have been fixed :)

Med Venlig Hilsen
Bjørn Ryborg

Gammel Skolevej 8, Tandslet, DK-6470 Sydals
Tlf: +45 3694 9898 - E-mail: Bjorn.Ryborg@gmail.com

2014-12-15 9:03 GMT+01:00 Christopher M. Penalver <
christopher.m.penalver@gmail.com>:
>
> Bjorn Ryborg, 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
>
> ** Changed in: remmina (Ubuntu)
>        Status: Confirmed => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/985645
>
> Title:
>   Remmina crashed under connection via RDP
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/985645/+subscriptions
>