unity-2d-places assert failure: unity-2d-places: ../../src/xcb_io.c:221: poll_for_event: A(z) „(((long) (event_sequence) - (long) (dpy->request)) <= 0)” kijelentés meghiúsult.

Bug #756407 reported by Balazs Pere
This bug report is a duplicate of:  Bug #745964: [dash] crashes in event loop. Edit Remove
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
unity-2d
New
Critical
Unassigned
unity-2d (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: unity-2d

A crash report window appeared on the screen. I don't know why? I cannot see any problem in unity2D after that message.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: unity-2d-places 3.8.2-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-8.41-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
Architecture: i386
AssertionMessage: unity-2d-places: ../../src/xcb_io.c:221: poll_for_event: A(z) „(((long) (event_sequence) - (long) (dpy->request)) <= 0)” kijelentés meghiúsult.
Date: Sun Apr 10 11:22:43 2011
ExecutablePath: /usr/bin/unity-2d-places
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110330)
ProcCmdline: /usr/bin/unity-2d-places
ProcEnviron:
 SHELL=/bin/bash
 LANGUAGE=hu:en
 LANG=hu_HU.UTF-8
Signal: 6
SourcePackage: unity-2d
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: unity-2d-places assert failure: unity-2d-places: ../../src/xcb_io.c:221: poll_for_event: A(z) „(((long) (event_sequence) - (long) (dpy->request)) <= 0)” kijelentés meghiúsult.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors: (nautilus:1142): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed

Revision history for this message
Balazs Pere (perebal-sze) wrote :
Changed in unity-2d:
importance: Undecided → Critical
milestone: none → 3.10
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.