compiz hangs on startup in XWindowEvent() from PrivateScreen::initDisplay()

Bug #966814 reported by Daniel van Vugt
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Compiz
New
Medium
Unassigned
Compiz Core
New
Medium
Unassigned
compiz (Ubuntu)
New
Undecided
Unassigned

Bug Description

(gdb) bt
#0 0x00007f8326185b03 in __GI___poll (fds=<optimised out>, nfds=<optimised out>, timeout=<optimised out>) at ../sysdeps/unix/sysv/linux/poll.c:87
#1 0x00007f8324091862 in ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#2 0x00007f8324092fff in xcb_wait_for_event () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
#3 0x00007f8325b8bce8 in _XReadEvents () from /usr/lib/x86_64-linux-gnu/libX11.so.6
#4 0x00007f8325b8a27d in XWindowEvent () from /usr/lib/x86_64-linux-gnu/libX11.so.6
#5 0x00007f83269b253c in PrivateScreen::initDisplay (this=0x11d0ab0, name=<optimised out>) at /tmp/buildd/compiz-0.9.7.2/src/screen.cpp:4790
#6 0x00007f83269afb2d in compiz::private_screen::EventManager::init (this=0x11d0ab0, name=0x0) at /tmp/buildd/compiz-0.9.7.2/src/screen.cpp:4596
#7 0x000000000040356c in CompManager::init (this=0x7fffe5c24990) at /tmp/buildd/compiz-0.9.7.2/src/main.cpp:169
#8 0x0000000000402989 in main (argc=<optimised out>, argv=0x7fffe5c24ac8) at /tmp/buildd/compiz-0.9.7.2/src/main.cpp:234

The hang happens on compiz restart after an earlier instance has crashed or exited.

Changed in compiz-core:
status: New → In Progress
assignee: nobody → Daniel van Vugt (vanvugt)
importance: Undecided → High
description: updated
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Actually this looks like it might be an unavoidable consequence of constantly starting/stopping/crashing from a different VT to X.

Changed in compiz-core:
status: In Progress → New
importance: High → Medium
Changed in compiz:
assignee: nobody → Daniel van Vugt (vanvugt)
importance: Undecided → Medium
Changed in compiz:
assignee: Daniel van Vugt (vanvugt) → nobody
Changed in compiz-core:
assignee: Daniel van Vugt (vanvugt) → nobody
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.