Bug 9195 - Xlib fails an assertion when used by kompmgr/xcompmgr
Summary: Xlib fails an assertion when used by kompmgr/xcompmgr
Status: RESOLVED DUPLICATE of bug 9154
Alias: None
Product: xorg
Classification: Unclassified
Component: Lib/Xlib (show other bugs)
Version: 7.2 (2007.02)
Hardware: All All
: high normal
Assignee: Jamey Sharp
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-11-29 10:44 UTC by Kai Krakow
Modified: 2006-11-29 11:00 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Kai Krakow 2006-11-29 10:44:40 UTC
Mostly while using konqueror (doesn't matter if browsing the web or local 
files), kombmgr exits with a failed assertion (with the two error lines coming 
some seconds or minutes before): 
 
kakra@ganymed ~ $ kompmgr 
trying '/home/kakra/.xcompmgrrc' as configfile 
 
 
finished parsing the config file 
Started 
error 3 request 20 minor 0 serial 3375176 
error 3 request 20 minor 0 serial 3385782 
kompmgr: xcb_io.c:178: process_responses: Assertion `!wait_for_first_event || 
dpy->head' failed. 
Abgebrochen 
 
--------------- 
 
Recompiled kwin just to be sure kompmgr is rebuilt with XCB-enabled Xlib 
(gentoo packages), but the failure persists: 
 
kakra@ganymed ~ $ kompmgr 
trying '/home/kakra/.xcompmgrrc' as configfile 
 
 
finished parsing the config file 
Started 
error 3 request 20 minor 0 serial 7334486 
error 3 request 20 minor 0 serial 7711794 
kompmgr: xcb_io.c:178: process_responses: Assertion `!wait_for_first_event || 
dpy->head' failed. 
Abgebrochen 
 
--------------------- 
 
Here's my config: 
 
kakra@ganymed ~ $ cat .xcompmgrrc 
[xcompmgr] 
Compmode=CompClientShadows 
DisableARGB=true 
FadeInStep=0.07 
FadeOutStep=0.04 
FadeTrans=false 
FadeWindows=false 
ShadowColor=0x000000 
ShadowOffsetX=0 
ShadowOffsetY=-80 
ShadowRadius=8

These failures also happen when using xcompmgr. Further, it seems to be 
sensible to the values used in the config. Some values make it fail with a 
segfault almost instantly after starting.

I first thought, it would be a KDE kompmgr bug. But the guys from bugs.kde.org 
pointed me here. I could reproduce this bahaviour with xcompmgr, so I reported 
it here. Original report: http://bugs.kde.org/show_bug.cgi?id=137908

Using gentoo packages:
[I--] [ ~] x11-libs/libxcb-1.0 (0)
[I--] [ ~] x11-proto/xcb-proto-1.0 (0)
[I--] [ ~] x11-base/xorg-server-1.1.1-r2 (0)
[I--] [ ~] x11-base/xorg-x11-7.1 (0)
Comment 1 Jamey Sharp 2006-11-29 11:00:16 UTC
This bug has already been reported as #9154 and fixed in libX11 git. As
mentioned in that bug report, you can get the patch we committed here:

http://gitweb.freedesktop.org/?p=xorg/lib/libX11.git;a=commitdiff_plain;h=c6a0b0f18ed1242eeb908f5cf767ab8381edd456

By the way, you shouldn't need to recompile anything, kompmgr included, to use
Xlib/XCB. If that had helped it would be a bug.

Thanks for trying out Xlib/XCB!

*** This bug has been marked as a duplicate of 9154 ***


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.