Summary: | firefox (and other apps) fail to start with x11-libs/pixman-0.17.4 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | infobox.oleg |
Component: | [OLD] Library | Assignee: | Gentoo X packagers <x11> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | ben, kinbot, maciek.joziewicz, mmokrejs, siarhei.siamashka |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
infobox.oleg
2010-01-23 10:13:37 UTC
Oh, btw, downgrading to pixman 0.17.2 solved the problem. Oleg (In reply to comment #1) > Oh, btw, downgrading to pixman 0.17.2 solved the problem. > > Oleg > Unable to reproduce, did you ensure you ran a revdep-rebuild after install? Yes, I've ran revdep-rebuild immediately after having problems - nothing was found. I've repeated this now - upgrade pixman to 0.17.4, observe failure, revdep-rebuild, no problems found. Oleg Same problem here after today's update... revdep-rebuild finds nothing, downgrading to pixman-0.17.2 doesn't help. Firefox isn't affected, some kde apps are: okular, konversation, quassel... Oops, sorry :) Downgrading to pixman-0.17.2 DOES help. pixman 0.17 is development release series, and now has asserts() enabled by default. I will personally hunt down and slap whoever put it in portage. Cheers I also experienced many problems after upgrading to pixman-0.17.4. In /var/log/gdm/:0.log: *** BUG *** pixman_region_copy: Malformed region src Set a breakpoint on 'log_region_error' to debug In /var/log/messages: Jan 26 16:20:28 supra gdm[14203]: WARNING: gdm_slave_xioerror_handler: Fatal X e rror - Restarting :0 Downgrading to pixman-0.17.2 solved the problems. Masked until we figure this out. Thanks Maybe bug #302517 has a relevant stacktrace and a link to a crashing testcase from Redhat? I think it makes sense to submit a bugreport to bugs.freedesktop.org once the initial investigation is done. It looks like the result of this patch: http://cgit.freedesktop.org/pixman/commit/?id=1435c8aa3db3b6bde26216e260cc94baba225664 And it is quite possible that it catches a (minor) bug in xserver which was unnoticed earlier (pixman was silently ignoring it). *** Bug 302517 has been marked as a duplicate of this bug. *** It works just fine for me (actually I was quite surprised, when asked to downgrade today...). So I'm just gonna unmask it on my system and if there is anything you'd like me to check (output to provide, etc.) for comparison, then just ask away :) BTW I've done a couple of restarts since upgrading to that pixman version, so there is no way I'm still using the cached old version or sth. BTW2 got a stable keyword amd64 system here (will be happy to supply details, just don't wanna spam) and Rémi, about that slapping, don't you think that the old system (fun stuff in the x11 overlay, sort of tested in unstable portage) would work out good? Recently I see only live ebuilds in the overlay... (In reply to comment #12) > It works just fine for me (actually I was quite surprised, when asked to > downgrade today...). So I'm just gonna unmask it on my system and if there is > anything you'd like me to check (output to provide, etc.) for comparison, then > just ask away :) > > BTW I've done a couple of restarts since upgrading to that pixman version, so > there is no way I'm still using the cached old version or sth. Look into bug #302517, run "revdep-rebuild-i", try opera, compile the crashing application xcrash.c if you want to play with the broken version. I don't think we want to have a broken system. For me "unstable" == "testing" but I really want to use the system and not just have dozens of bugreports opened and pending. We are all short on time. (In reply to comment #12) > and Rémi, about that slapping, don't you think that the old system (fun stuff > in the x11 overlay, sort of tested in unstable portage) would work out good? > Recently I see only live ebuilds in the overlay... That's what _should_ have happened. But since I'm only doing bugmail until Real Life (tm) settles down, 0.17 got added to portage by someone else. That wasn't meant to happen. I explained myself on bug 302517 comment 10. Plz read, and sorry for the issues. This is fixed for now, and newer versions of pixman no longer enable fatal asserts by default. Closing. |