remmina assert failure: remmina: ../../src/xcb_io.c:273: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.

[bperkey]

I was connected to Ubuntu Server 10.04 via Remmina SSH, when the crash occurred. Specifically, I had just typed exit at the command prompt to end my SSH connection with one Ubuntu server and then double clicked another Ubuntu 10.04 server session in Remmina when the crash occurred. My guess is that the issue occurred in the background when I exited the first ssh session prior to attempting to access the second connection.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: remmina 0.9.3-2
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic i686
NonfreeKernelModules: fglrx
ApportVersion: 1.23-0ubuntu2
Architecture: i386
AssertionMessage: remmina: ../../src/xcb_io.c:273: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
Date: Wed Oct 5 16:05:59 2011
ExecutablePath: /usr/bin/remmina
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110921.2)
ProcCmdline: remmina
ProcEnviron:
 LANGUAGE=en_CA:en
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: remmina
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/i386-linux-gnu/libc.so.6
 abort () from /lib/i386-linux-gnu/libc.so.6
 __assert_fail () from /lib/i386-linux-gnu/libc.so.6
 ?? () from /usr/lib/i386-linux-gnu/libX11.so.6
Title: remmina assert failure: remmina: ../../src/xcb_io.c:273: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 __GI___assert_fail (assertion=0x7aa130 "!xcb_xlib_threads_sequence_lost", file=0x7aa38a "../../src/xcb_io.c", line=273, function=0x7aa478 "poll_for_event") at assert.c:81
 poll_for_event (dpy=0x829e0b0) at ../../src/xcb_io.c:270
 poll_for_response (dpy=0x829e0b0) at ../../src/xcb_io.c:288
 _XEventsQueued (dpy=0x829e0b0, mode=2) at ../../src/xcb_io.c:362
 XPending (dpy=0x829e0b0) at ../../src/Pending.c:55

[Launchpad Janitor (janitor)]

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

[Pierre van der Riet (pierre-vanderriet)]

also affects 12.04 installs

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)"

(sorry I cannot provide any backtrace)

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

[Pierre van der Riet (pierre-vanderriet)]

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

[Roland Giesler (lifeboy)]

I can confirm that changing the keyboard to English US allows remmina to run.

[Roland Giesler (lifeboy)]

Just to clarify my comment #8. When I start remmina I get the core dump scenario described in comment #6.

[Liam (bell-liam)]

This is affecting me on Ubuntu 13.04, almost an identical output as posted in comment 6. The main issue being a core dump which seems to be affecting the application running effectively.

[Boris Baelen (sjimmie)]

Same problem for me in ubuntu 13.04.

This is my output.
If any more debugging is nessecary please let me know, i really want to fix this.

boris@werk-laptop:~$ remmina
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.
Remmina plugin SFTP (type=Protocol) registered.
Remmina plugin SSH (type=Protocol) registered.
connected to 10.160.25.33:3389
null server certificate
*** Error in `remmina': free(): invalid next size (normal): 0x00007ff0bc0e01c0 ***
======= Backtrace: =========
/lib/x86_64-linux-gnu/libc.so.6(+0x80a46)[0x7ff0f9db5a46]
/usr/lib/x86_64-linux-gnu/libfreerdp-gdi.so.1.0(gdi_DeleteObject+0x3e)[0x7ff0ecfd494e]
/usr/lib/x86_64-linux-gnu/libfreerdp-gdi.so.1.0(gdi_Bitmap_Free+0x28)[0x7ff0ecfd58e8]
/usr/lib/x86_64-linux-gnu/libfreerdp-core.so.1.0(Bitmap_Free+0xc)[0x7ff0ed2006fc]
/usr/lib/x86_64-linux-gnu/libfreerdp-cache.so.1.0(update_gdi_cache_bitmap_v2+0xa5)[0x7ff0ec32e625]
/usr/lib/x86_64-linux-gnu/libfreerdp-core.so.1.0(update_recv_secondary_order+0xb8)[0x7ff0ed1ffd28]
/usr/lib/x86_64-linux-gnu/libfreerdp-core.so.1.0(fastpath_recv_updates+0x3eb)[0x7ff0ed208a7b]
/usr/lib/x86_64-linux-gnu/libfreerdp-core.so.1.0(+0x2a98a)[0x7ff0ed20698a]
/usr/lib/x86_64-linux-gnu/libfreerdp-core.so.1.0(+0x2abd0)[0x7ff0ed206bd0]
/usr/lib/x86_64-linux-gnu/libfreerdp-core.so.1.0(transport_check_fds+0x122)[0x7ff0ed209e52]
/usr/lib/x86_64-linux-gnu/libfreerdp-core.so.1.0(freerdp_check_fds+0x13)[0x7ff0ed2003f3]
/usr/lib/remmina/plugins/remmina-plugin-rdp.so(+0x7cc1)[0x7ff0ed427cc1]
/usr/lib/remmina/plugins/remmina-plugin-rdp.so(+0x801a)[0x7ff0ed42801a]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x7f8e)[0x7ff0faa71f8e]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7ff0f9e2ee1d]
======= Memory map: ========
00400000-00449000 r-xp 00000000 08:01 3146747 /usr/bin/remmina
00649000-0064a000 r--p 00049000 08:01 3146747 /usr/bin/remmina
0064a000-0064d000 rw-p 0004a000 08:01 3146747 /usr/bin/remmina
0070f000-00c0a000 rw-p 00000000 00:00 0 [heap]
7ff0b3816000-7ff0b4000000 rw-p 00000000 00:00 0
7ff0b4000000-7ff0b4021000 rw-p 00000000 00:00 0
7ff0b4021000-7ff0b8000000 ---p 00000000 00:00 0
7ff0b8000000-7ff0b8021000 rw-p 00000000 00:00 0
7ff0b8021000-7ff0bc000000 ---p 00000000 00:00 0
7ff0bc000000-7ff0bc0e8000 rw-p 00000000 00:00 0
7ff0bc0e8000-7ff0c0000000 ---p 00000000 00:00 0
7ff0c03de000-7ff0c03df000 ---p 00000000 00:00 0
7ff0c03df000-7ff0c0bdf000 rw-p 00000000 00:00 0 [stack:9628]
7ff0c0bdf000-7ff0c0be0000 ---p 00000000 00:00 0
7ff0c0be0000-7ff0c13e0000 rw-p 00000000 00:00 0 [stack:9627]
7ff0c13e0000-7ff0c9a8a000 r--p 00000000 08:01 4344349 /usr/share/icons/hicolor/icon-theme.cache
7ff0c9a8a000-7ff0d2134000 r--p 00000000 08:01 4344349 /usr/share/icons/hicolor/icon-theme.cache
7ff0d2134000-7ff0d709a000 r--p 00000000 08:01 4349759 /usr/share/icons/gnome/icon-theme....

[psypher (psypher246)]

Is this bug in any way related to this one:
https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/753520

[penalvch (penalvch)]

bperkey, thank you for reporting this bug to Ubuntu. Oneric reached EOL on May 9, 2013.
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