remmina crashed with SIGABRT in __malloc_assert()

[Daniel Richard G.]

A remote connection had been active, but unresponsive. I Alt-Tabbed a couple times, switched away to another desktop and back, and BOOM.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: remmina 0.9.3-2
ProcVersionSignature: Ubuntu 3.0.0-17.30-generic 3.0.22
Uname: Linux 3.0.0-17-generic x86_64
NonfreeKernelModules: openafs
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
Date: Mon Apr 30 12:35:07 2012
ExecutablePath: /usr/bin/remmina
ProcCmdline: remmina
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: remmina
StacktraceTop:
 __malloc_assert (assertion=<optimized out>, file=<optimized out>, line=<optimized out>, function=<optimized out>) at malloc.c:351
 mremap_chunk (p=<optimized out>, new_size=<optimized out>) at malloc.c:3574
 __GI___libc_realloc (oldmem=0x1768540, bytes=16) at malloc.c:3790
 g_realloc () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: remmina crashed with SIGABRT in __malloc_assert()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout floppy plugdev scanner vboxusers video
XsessionErrors:
 (check-new-release-gtk:2467): Gtk-WARNING **: Unknown property: GtkMessageDialog.has-separator
 (xfce4-indicator-plugin:2491): Gtk-CRITICAL **: IA__gtk_widget_set_name: assertion `GTK_IS_WIDGET (widget)' failed
 (xfce4-indicator-plugin:2491): libindicator-WARNING **: IndicatorObject class does not have an accessible description.
 (xfce4-indicator-plugin:2491): libxfce4panel-CRITICAL **: IA__xfce_panel_plugin_add_action_widget: assertion `GTK_IS_WIDGET (widget)' failed

[Apport retracing service (apport)]

StacktraceTop:
 __malloc_assert (assertion=<optimized out>, file=<optimized out>, line=<optimized out>, function=<optimized out>) at malloc.c:351
 mremap_chunk (p=<optimized out>, new_size=<optimized out>) at malloc.c:3574
 __GI___libc_realloc (oldmem=0x1768540, bytes=16) at malloc.c:3790
 g_realloc (mem=<optimized out>, n_bytes=16) at /build/buildd/glib2.0-2.30.0/./glib/gmem.c:233
 g_array_maybe_expand (array=0x15a0140, len=<optimized out>) at /build/buildd/glib2.0-2.30.0/./glib/garray.c:689

[Lacyc3 (lacyc3)]

Remmina still crashes with the same "remmina crashed with sigabrt in malloc assert()" message while connecting to Windows 8.1.

Ubuntu 14.04.1
3.13.0-35-generic x86_64
Remmina: Remmina: 1.0.0-4ubuntu3

[Launchpad Janitor (janitor)]

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

[Svivi (svivi)]

I have the same issue with Remmina 1.0.0-4ubuntu3 on Ubuntu 14.04.1. It keeps crashing while try to connect to Windows 7.
Kernel version is 3.13.0-35-generic x86_64.

[penalvch (penalvch)]

Daniel Richard G., thank you for reporting this bug to Ubuntu. Oneiric reached EOL on May 9, 2013.
See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases

If this reproducible in a supported release, 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