problem starting kdm with jpeg-7 [SOLVED]

paladin-zero · Guru Joined: 19 May 2004 Posts: 322

I recently upgraded to media-libs/jpeg-7 and afterwords ran "emerge @preserved-rebuild". When that was done, I rebooted and was then unable to start kdm, which crashed with a segfault. The crash report claimed that kdmgreet had crashed, and the stack trace indicated that QtGui's libqjpeg had called libjpeg, and libjpeg had crashed. I tried rebuilding kdm, qtgui, kdelibs, and finally I remerged my entire system, and still could not start kdm.

I finally found bug #283241, a tracker for jpeg-7 incompatibilities, and tried masking ">=media-libs/jpeg-7" and updated and ran "emerge @preserved-rebuild" again. Then I rebooted and now I can log in again.

I filed a bug (https://bugs.gentoo.org/show_bug.cgi?id=283406) and the response was to state that I hadn't provided any useful information and to mark the bug as resolved. So I'm posting here in case anyone else sees this problem, please post the requested information at that bug report and reopen it, I don't have time to go and break my system again to provide the information requested.

DaggyStyle · Watchman Joined: 22 Mar 2006 Posts: 5916

I've upgraded to version too and my entire system breaked. I didn't rebooted and rebuilded the breakage.
what kdm are you running? using 4.3.0, my kdm was broken but it still booted.
_________________
Only two things are infinite, the universe and human stupidity and I'm not sure about the former - Albert Einstein

paladin-zero · Guru Joined: 19 May 2004 Posts: 322

I am also using 4.3. I was able to boot, but not able to start kdm until I dropped back to "<media-libs/jpeg-7".

DaggyStyle · Watchman Joined: 22 Mar 2006 Posts: 5916

paladin-zero · Guru Joined: 19 May 2004 Posts: 322

rtomek · Posted: Tue Sep 01, 2009 8:43 pm Post subject:

I had the same problem but couldn't find anything on the forums. I just did an 'emerge -e world' overnight and in the morning everything was working fine, even with jpeg-7.

I don't know what package it was that had to be rebuilt, I tried rebuilding a bunch of packages that I thought could be the culprit with no success. Finally I decided to just rebuild the system and go to bed, and that did it.

Havin_it · Posted: Wed Sep 02, 2009 12:20 pm Post subject:

I had a few problems myself. It is essential to run revdep-rebuild after upgrading to jpeg-7 - and if you're like me, there will be a *lot* of packages needing rebuilt (even quite a few on my server box). I suppose given jpeg's ubiquity it's to be expected, but other ebuilds manage to warn you when a revdep-rebuild will be required. A bad oversight IMO.

paladin-zero · Guru Joined: 19 May 2004 Posts: 322

I found the problem. I had installed a package manually that installed its own jpeg-6 library and headers into /usr/local. Apparently, some package was getting confused by picking up headers from /usr/local and the .so from /usr. I deleted the jpeg-6 files from /usr/local, unmasked and upgraded to jpeg-7, ran "emerge @preserved-rebuild", checked that libjpeg.so.62* had been removed, rebooted, and my system is happy.