remmina crashed with Segmentation fault (core dumped)

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #868677, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

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

Similar behaviour although no theme error is reported in my case just Core Dumped:
"Remmina plugin VNC (type=Protocol) registered.
Remmina plugin VNCI (type=Protocol) registered.
Remmina plugin RDP (type=Protocol) registered.
Remmina plugin RDPF (type=File) registered.
Remmina plugin RDPS (type=Preference) registered.
Segmentation fault (core dumped)"

This was after a clean install as well as clearing out the config dir

If its a solution that can work for some users, simply setting my Keyboard Settings to use US Locale [English (US)] solved it for me:
1. you can even set it to use this locale only for reminna and
2. not sure, but you may have to log out / log back in for it to take effect

Uroš Gaber, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue?

If so, please provide the missing information following https://help.ubuntu.com/community/Remmina .

As well, please execute the following via a terminal:
apport-collect 982526

Thank you for your understanding.

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

Hello Christopher,

I'm experiencing the same crash at startup on Ubuntu 14.04.1 LTS with lxdm
I've tried purging and reinstalling remmina.

I'm willing to provide further feedback.
I will run apport-collect 982526 and ubuntu-bug remmina after posting this.

GChr, in general, it is best not to run apport-collect against a report you are not the original reporter of. Especially in this case, it won't be gathering the information necessary to debug your problem (a program crash).

Instead, 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 file the crash report again via:
ubuntu-bug /var/crash/_my_crash_report.crash

Please feel free to subscribe me to the new report you create.

As well, please do not attach your crash report manually to this report.

Thank you for your understanding.

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

[Expired for remmina (Ubuntu) because there has been no activity for 60 days.]

Currently running on 12.04LTS. All of a sudden this is happening. Seems to be related to a bad *.remmina file? any ideas how I could chase this down?

Or is there a newer version with this issue resolved in PPA? I am aware that PPA's are outside of the base distro. I need a solution.

I confirm the segmentation error appears when you have a corrupted .remmina file
To know which remmina file is the problem, run the command
strace remmina
from command line

You will get for example

open("/home/xxx/.remmina/1360539812291.remmina", O_RDONLY) = 10
fstat(10, {st_mode=S_IFREG|0644, st_size=281, ...}) = 0
read(10, "[remmina]\nssh_auth=2\nssh_charset"..., 4096) = 281
read(10, "", 4096) = 0
close(10) = 0
brk(0x10bd000) = 0x10bd000
open("/home/xxx/.remmina/1488616014869.remmina", O_RDONLY) = 10
fstat(10, {st_mode=S_IFREG|0644, st_size=291, ...}) = 0
read(10, "[remmina]\nssh_auth=2\nssh_charset"..., 4096) = 291
read(10, "", 4096) = 0
close(10) = 0
open("/home/xxx/.remmina/1565454518302.remmina", O_RDONLY) = 10
fstat(10, {st_mode=S_IFREG|0644, st_size=219, ...}) = 0
read(10, "\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 4096) = 219
read(10, "", 4096) = 0
close(10) = 0
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0} ---
+++ killed by SIGSEGV +++
Erreur de segmentation

The file as parameter of last open is the file corrupted that remmina is not able to read.
Just remove the file /home/xxx/.remmina/1565454518302.remmina
Then you can run remmina again.

Laurent Destailleur (eldy):

1) Could you please attach the file so folks may attempt reproduce and see if in fact it is a duplicate?

2) To clarify, how did you confirm the file is corrupted versus Remmina is not handling a properly formatted file?

3) It would be helpful if you filed a new report via a terminal to review debugging logs:
ubuntu-bug remmina

Please feel free to subscribe me to it.

Unfortunately, i removed the file before reporting the turnaround to check the theory was good. I forgot to make a backup. But you can see in the strace into the "read" line that the content of the file si not a content of a .remmina file compared to other files that start with "[remmina]\nssh_..."

This track is for me enough to say that the file was corrupted (it has a binary content of \0 instead of text content).