Bug 465586 – x11-wm/awesome-3.5.1 - awesome exits at startup after: awesome: cairo-xcb-connection-core.c:429: _cairo_xcb_connection_put_subimage: Assertion `!"reached"' failed.

• Product: Gentoo Linux
• Status: RESOLVED OBSOLETE

[Description Tim Roes 2013-04-11 21:08:57 UTC]

Starting awesome (using Slim as login manager) will result in awesome stopping immediately leaving the sole following line in its log file:

awesome: cairo-xcb-connection-core.c:429: _cairo_xcb_connection_put_subimage: Assertion `!"reached"' failed.

Since happens since the update 3.5-r1 to 3.5.1 every time. (USE flags: dbus -doc -elibc_FreeBSD -gnome)

awesome compiled without errors (also tried recompiling several times).

Cairo is installed in version 1.10.2-r3 and libxcb in 1.9.

Reproducible: Always

Steps to Reproduce:
1. Emerge awesome-3.5.1
2. Try using it as the window manager
3. crash..

I guess this is somewhat related to special configuration on my pc, so I would be glad to give more information to help tracking that down.
Actual Results:  
Awesome isn't running with above mentioned error line in log file.

Expected Results:  
Awesome should be running.

Let me know what package versions or configuration could be usefull to track this down.

[Comment 1 Nikolaj Šujskij 2013-04-12 16:25:18 UTC]

Well, well, that is unfortunate. Please attach `emerge --info` for reference.

It seems that the problem is in cairo, which is stable. We, maintainers, had tested 3.5.1 on ~arch.

So, 3.5 worked fine? It would be nice if you could `git bisect` the issue between 3.5 and 3.5.1. Or check with cairo 1.12.

Meanwhile I'll try to find stable system and to reproduce the issue.

[Comment 2 Nikolaj Šujskij 2013-04-13 15:51:00 UTC]

*Not* confirming this on a stable amd64 system with cairo 1.10.2-r3.

[Comment 3 Tim Roes 2013-04-13 17:35:32 UTC]

Works for me with cairo ~1.12.10-r2, but still not with 1.10.2-r3. 
If I find some spare time, I will try to bisect it, but that's for now a good enough workaround for me :-)

[Comment 4 Nikolaj Šujskij 2013-04-13 17:56:01 UTC]

Looks like there was something wrong with your cairo. It could very well be that rebuilding stable cairo would have issue fixed as well.

Let this hang for a while, if there'd be no details, we'll close that when cairo 1.12 goes stable.

[Comment 5 Tim Roes 2013-04-13 18:20:24 UTC]

I rebuilt cairo several times beforehand already and also now after it worked with 1.12. It always had the same error with the old cairo version.
Might I need special USE-flags for cairo? Have it installed with 

X glib opengl svg xcb -aqua -debug -directfb -doc -drm -gallium -legacy-drivers -openvg -qt4 -static-libs

Anyways I am fine with using 1.12 cairo, and as soon as it becomes stable this won't be an issue anymore.

[Comment 6 Nikolaj Šujskij 2013-04-13 18:59:55 UTC]

(In reply to comment #5)
> I rebuilt cairo several times beforehand already and also now after it
> worked with 1.12. It always had the same error with the old cairo version.
> Might I need special USE-flags for cairo? Have it installed with 
> 
> X glib opengl svg xcb -aqua -debug -directfb -doc -drm -gallium
> -legacy-drivers -openvg -qt4 -static-libs

 The only difference with my setup is directfb.

> Anyways I am fine with using 1.12 cairo, and as soon as it becomes stable
> this won't be an issue anymore.

Fine, let's keep it open for a while though. Just in case :)

[Comment 7 Gino McCarty 2014-02-10 17:27:54 UTC]

can anyone confirm this still exists with awesome-3.5.2-r1 ? I haven't experienced this issue.

I am on cairo-1.12.14-r4 for a bit now... with directfb..


It might be nice to have this closed if you all don't mind. 
I'm getting ready to file a stable request against awesome 3.5.2-r1 and I don't want this blocking it.

[Comment 8 Nikolaj Šujskij 2014-02-10 17:47:20 UTC]

I suppose it's time we close it for real.

[Comment 9 Sergey Popov (RETIRED) 2014-02-12 12:00:46 UTC]

Closing as OBSOLETE per request, feel free to reopen if issue still there