apport-gtk crashed with SIGABRT in __assert_fail_base()

[wahab hakeem]

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: apport-gtk 2.9.2-0ubuntu8.5
ProcVersionSignature: Ubuntu 3.8.0-34.49-generic 3.8.13.12
Uname: Linux 3.8.0-34-generic i686
ApportVersion: 2.9.2-0ubuntu8.5
Architecture: i386
Date: Tue Jan 7 01:06:37 2014
ExecutablePath: /usr/share/apport/apport-gtk
InstallationDate: Installed on 2013-04-08 (273 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
InterpreterPath: /usr/bin/python3.3
MarkForUpload: True
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
Signal: 6
SourcePackage: apport
StacktraceTop:
 raise () from /lib/i386-linux-gnu/libc.so.6
 abort () from /lib/i386-linux-gnu/libc.so.6
 ?? () 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: apport-gtk crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to raring on 2013-11-25 (42 days ago)
UserGroups:

[Apport retracing service (apport)]

StacktraceTop:
 __assert_fail_base (fmt=0xb76fc294 "%s%s%s:%u: %s%sAssertion `%s' failed.\n%n", assertion=assertion@entry=0xb6981130 "!xcb_xlib_threads_sequence_lost", file=file@entry=0xb698138a "../../src/xcb_io.c", line=line@entry=274, function=function@entry=0xb6981478 <__PRETTY_FUNCTION__.13991> "poll_for_event") at assert.c:92
 __GI___assert_fail (assertion=assertion@entry=0xb6981130 "!xcb_xlib_threads_sequence_lost", file=file@entry=0xb698138a "../../src/xcb_io.c", line=line@entry=274, function=function@entry=0xb6981478 <__PRETTY_FUNCTION__.13991> "poll_for_event") at assert.c:101
 poll_for_event (dpy=dpy@entry=0x885f400) at ../../src/xcb_io.c:271
 poll_for_response (dpy=dpy@entry=0x885f400) at ../../src/xcb_io.c:289
 _XEventsQueued (dpy=dpy@entry=0x885f400, mode=mode@entry=1) at ../../src/xcb_io.c:363

[Launchpad Janitor (janitor)]

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

[Colin Law (colin-law)]

I am seeing this on trusty.

[Ivo Moelans (ivo-moelans)]

I am seeing this too on trusty (completely updated)

[Anass Eljondy (great-anass)]

seeing this on 14.04 alpha ubuntu gnome(gnome3) amd64

AMD apu E1 E1500 with Ati Radeon HD 7310

Compaq laptop CQ58

[WoolF (woolf911)]

Nautilus crashed when I open dialog for change permissions for folder.
Ubuntu 14.04, Unity
Thank you...

[Paul Oppenheim (pauloppenheim)]

On login

[Abdoulaye Camara (lilbro1062000)]

on login as well on 14 trusty

[Marcos Sanchez (marchezior)]

Happens to me on every boot in Ubuntu 14.04 Beta 1.

[One GSKW (agoldstar101)]

Happened after upgrading from Precise to Trusty. Not sure if it happens every boot.

[Horand (shatroff)]

Happens to me on every boot in Ubuntu 14.04 Beta 1.

[Sivabalan (siva886)]

Happens to me on every boot in Ubuntu 14.04 Beta 1.

[188236 (christian-bernstein)]

crashed right at startup 14.04

[codeslinger (codeslinger)]

this was not happening to me until after I installed updates and or used an external monitor. after a fresh install I was not seeing this. also in the display settings, I see two identical entries for laptop.

see bug 1291927

UbuntuStudio 14.04 amd64 BETA 1 (Alpha) Feb 24

[Emit (amiratez)]

Package operation failed
The installation or removal of a software package failed.
 can't install any apps

[fdwsgds (mubtcez)]

happens on Lubuntu 14.04 too with all updates installed (including latest bios)

[LIU Fuhua (harryfhliu)]

ubuntu 14.04 when boot

[Chris Engen (ceipmask)]

Downloaded PCB Designer, opened the program, resulting in the GUI freezing. I was still able to acces tty1-6 through the CTRL+ALT+F1 and so on. the system bacame responsive almost imediately after the crash.

[Stuart Hine (f-stuart)]

Happened to me just now, 5 times in a row all within about a minute, fun times lol

[James Landrum (james-landrum1)]

too many error messages!

[Anand (acpadhi-1)]

After boot, and also occasionaly when working, very irritating for it to keep popping up frequently and also multiple instances

[Hermann Lang (hermannlang)]

I'm afraid the Bug Description is not correct. I'm using Ubuntu 14.04 64 bits.
"uname -a" output is "Linux hermann-Vostro-3550 3.13.0-19-generic #40-Ubuntu SMP Mon Mar 24 02:36:06 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux"

[fdwsgds (mubtcez)]

.
.
.
.
.
I've just realized that I didn't have any bug reports since many days! Ive no idea why maybe its been fixed in the prerelease updates and beta etc updates? ( I update very often with this command: a

Ive made an alias so a does this: alias a='ap update -y && ap dist-upgrade -y && ap check -y && ap autoremove -y && ap autoclean -y'
and another alias which makes ap into apt-get: alias ap='apt-get'

[userxyz (usernamexyz-deactivatedaccount)]

Gnome-shell, apport, gnome control center, all give me errors at the start up of Gnome 14.04 beta 1. Also, after I install the latest updates, Ubuntu will not load: it gets stuck on the loading screen and doesn't allow me to get to the session manager screen so that I can enter with my user...

[fdwsgds (mubtcez)]

@Pedro can you change to terminal instead of gui by pressing ctrl alt f1 ? if so then read my comment above.It should help you.

[ealthuis (ealthuis)]

 I have no info to add, but the problem shows up when starting

[Mark Murphy (mokmeister)]

Occurred after last dist-upgrade, Trusty.

[ealthuis (ealthuis)]

After checking this report I opened terminal and entered:

Sudo apt-get update

Sudo apt-get upgrade

Problems soved

I have not had any recurring error messages.

[wolfy1339 (wolfy1339)]

Happened after logging in,
Trusty (Final beta, amd64)

[Calin Cerghedean (ccerghe1)]

Same here, just after logging in, Trusty final beta, amd64.

[max pleaner (maxpleaner)]

after logging in and/or opening browser, 14.04, lenovo ideapad s415 amd64.

[Alberto Salvia Novella (es20490446e)]

Please, into the "Terminal" application, enter the following line:
sudo apt-get update && sudo apt-get upgrade -y && sudo apt-get autoremove

Then test if this bug is still there for you. If so change this report status back to "confirmed".

Thank you ;)