On Monday 23 October 2006 19:22, Duncan wrote: > I've been having all /sorts/ of problems with formerly stable audio and > video apps crashing recently. The pattern is a crash at launch most (but > not all) of the time, often with some memory error. However, if it > /does/ start and works more than a few minutes, it's fully stable and > will play for hours without issue. xmms, kaffeine, amarok, all affected.
nope > > I didn't notice it until the upgrade to kde-3.5.5, which was my first big > set of apps built using the experimental CFLAG -ftree-vectorize as > discussed here a month or so ago, so I thought it was KDE. However, after > recompiling a bunch of stuff several different times/ways, nothing seemed > to be working. > which I am using for some time now. I get konqueror crashes once in a while. Nothing else. (I can make crash konqueror, when I move the mouse over a mpeg and wait for the popup - bang, segfault). > Then I chanced across some ongoing discussion about nptl/linux-threads in > glibc-2.5 and forward on the dev list, while I was taking a break from > troubleshooting, and the thought occurred to me that glibc had been > upgraded at about the same time. > > VWALLA! I try to downgrade to glibc-2.4-r4, and get hit with its sanity > downgrade blocker. It won't let me do it. So a quick reboot to my backup > image (still on glibc-2.4-r3) and a quick ROOT=<backup> (which is main > working, since I'm no /on/ backup) export later, I'm emerging glibc-2.4-r4 > (which I have binpkged, thanks to FEATURES=buildpkg) over top of what I'm > now convinced is a bad glibc-2.5. DO NEVER downgrade glibc! I have been there, bitten by it very, very hard. A nonbooting system, because not even udev runs, is a big problem (I solved it, but it cost me time, sweat and tears). > Meanwhile a potentially useful trick to keep up your sleeve, just in case > you ever find yourself needing to downgrade glibc but the glibc ebuild > failing to let you do so. Reboot to your emergency image, be that a > LiveCD or a backup set of partitions on your hard drive, mount your normal > working filesystem image, set ROOT= to point portage at the normal system > (not the backup), and /then/ do your glibc downgrade. Then boot back to > your regular system and hope the downgrade works, as it did here. =8^) > and rebuilt EVERYTHING that was built against the new glibc! Every single app, every lib, everything. You miss something and you will suffer. -- [email protected] mailing list
