Summary: | kde-base/kdm: unable to start with media-libs/jpeg-7 [solved] | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Darren Dale <dsdale24> |
Component: | Current packages | Assignee: | Gentoo KDE team <kde> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Darren Dale
2009-09-01 12:57:53 UTC
No useful information provided. Need specific information on which file in which package is needing old jpeg. Or backtrace. Or linking information. Any date that would help solving the issue since kdm is working fine here. (In reply to comment #1) > date that would help solving the issue since kdm is working fine here. *data (In reply to comment #1) > No useful information provided. Need specific information on which file in > which package is needing old jpeg. Or backtrace. Or linking information. Any > date that would help solving the issue since kdm is working fine here. Classic. No suggestion on how I can provide it? Just mark it resolved and look the other way? I protest. Now that someone else on the forum seems to have had the same problem as I reported (see comment #4), I would like to request that the bug be reopened long enough for others to find it and post the requested data. as requested, I have upgraded to version 7, had some breakage, revdep-rebuild had fixed it, the only thing I can see different is that I don't use Portage 2.2, I use the latest stable one. I can guess that using the sets won't repair the breakage in some way. Darren can you re-install jpeg-7 and this time run revdep-rebuild from app-portage/gentoolkit package instead of "emerge @preserved-rebuild"? Pleaase report your success/failures back here. revdep-rebuild seemed to iron out all these related issues for me (apologies if this is not true for others). I would have thought the need for this step should have been einfo'd in jpeg-7.ebuild... (In reply to comment #7) > Darren can you re-install jpeg-7 and this time run > > revdep-rebuild > > from app-portage/gentoolkit package instead of "emerge @preserved-rebuild"? > Pleaase report your success/failures back here. I will do so, but don't understand why that would work when running "emerge @preserved-rebuild" and then "emerge -e @system @world" did not. I'll report my results. (In reply to comment #9) > (In reply to comment #7) > > Darren can you re-install jpeg-7 and this time run > > > > revdep-rebuild > > > > from app-portage/gentoolkit package instead of "emerge @preserved-rebuild"? > > Pleaase report your success/failures back here. > > I will do so, but don't understand why that would work when running "emerge > @preserved-rebuild" and then "emerge -e @system @world" did not. > > I'll report my results. > I unmasked ">=jpeg-7", ran "emerge -uDN @system @world", and then ran "revdep-rebuild -p" which yielded no packages that need to be rebuilt. I don't think this is surprising, since libjpeg.so.62.0.0 and libjpeg.so are still present on my system. At this point, I think I should try to reboot, I don't think there will be problems until I run "emerge @preserved-rebuild". If the reboot works, I'll do preserved-rebuild and revdep-rebuild again, reboot, and report back. rebooting was successful, now I will run preserved-rebuild again: $ sudo emerge @preserved-rebuild -p Password: These are the packages that would be merged, in order: Calculating dependencies... done! [ebuild R ] media-libs/tiff-3.8.2-r8 [ebuild R ] media-libs/jasper-1.900.1-r3 [ebuild R ] media-libs/gd-2.0.35 [ebuild R ] media-libs/libmng-1.0.10 [ebuild R ] net-libs/libvncserver-0.9.7 [ebuild R ] dev-python/imaging-1.1.6-r1 [ebuild R ] media-video/mplayer-1.0_rc2_p20090731-r1 [ebuild R ] media-gfx/sane-backends-1.0.20-r1 [ebuild R ] media-libs/libgphoto2-2.4.7 [ebuild R ] dev-python/pygame-1.8.1-r1 [ebuild R ] dev-libs/poppler-0.10.7 [ebuild R ] media-gfx/imagemagick-6.5.4.10 [ebuild R ] media-libs/lcms-1.18-r1 [ebuild R ] www-client/links-2.2 [ebuild R ] media-gfx/blender-2.49a [ebuild R ] media-libs/imlib2-1.4.2-r1 [ebuild R ] media-libs/vigra-1.6.0 [ebuild R ] net-print/cups-1.3.11 [ebuild R ] x11-libs/gtk+-2.16.5 [ebuild R ] x11-libs/qt-gui-4.5.2-r2 [ebuild R ] app-text/ghostscript-gpl-8.70-r1 [ebuild R ] net-libs/webkit-gtk-1.1.10 [ebuild R ] media-libs/libquicktime-1.1.3 [ebuild R ] media-libs/gegl-0.1.0 [ebuild R ] net-libs/xulrunner-1.9.1.2-r2 [ebuild R ] media-gfx/graphviz-2.24.0 [ebuild R ] kde-base/kdelibs-4.3.0 [ebuild R ] media-gfx/gimp-2.6.7 [ebuild R ] net-libs/libproxy-0.2.3-r2 [ebuild R ] media-video/transcode-1.1.4 [ebuild R ] net-print/gutenprint-5.2.3 [ebuild R ] media-gfx/pstoedit-3.45 [ebuild R ] net-print/hplip-3.9.4b-r1 [ebuild R ] kde-base/libkdcraw-4.3.0 [ebuild R ] kde-base/gwenview-4.3.0 [ebuild R ] kde-base/kdebase-kioslaves-4.3.0 [ebuild R ] kde-base/krdc-4.3.0 [ebuild R ] kde-base/okular-4.3.0 [ebuild R ] kde-base/krfb-4.3.0 Ok, I tried running emerge @preserved-rebuild, as portage suggested. When it was done, portage again said it had to run @preserved-rebuild for dev-python/imaging, no matter how many times I ran it. So I deleted libjpeg.so.6* from my libs, ran "emerge -1 imaging", ran revdep-rebuild (which found no problems) and rebooted. Again, kdm segfaults before I see the login screen. Here is all the information the crash report provides: Application: unknown (kdmgreet), signal: Segmentation fault [KCrash Handler] #4 0x00007fffac2e3cdc in jpeg_CreateDecompress () from /usr/lib64/libjpeg.so.7 #5 0x00007fffab08456f in ?? () from /usr/lib64/qt4/plugins/imageformats/libqjpeg.so #6 0x00007fffb35392b4 in QImageReader::read () from /usr/lib64/qt4/libQtGui.so.4 #7 0x00007fffb353980c in QImageReader::read () from /usr/lib64/qt4/libQtGui.so.4 #8 0x00007fffb3528ad6 in QImage::load () from /usr/lib64/qt4/libQtGui.so.4 #9 0x000000000044294b in ?? () #10 0x0000000000442e69 in ?? () #11 0x000000000043bf93 in ?? () #12 0x000000000043c1c5 in ?? () #13 0x000000000043c66c in ?? () #14 0x00000000004416ce in ?? () #15 0x000000000044d0d3 in ?? () #16 0x000000000043cb38 in ?? () #17 0x0000000000438c87 in ?? () #18 0x0000000000436a35 in ?? () #19 0x00007fffb2824a2d in __libc_start_main () from /lib/libc.so.6 #20 0x0000000000418829 in _start () Just hint: if you see in your backtrace more 0 or ? than any other character it is worthless :] Based on comments toward the end of https://bugs.kde.org/show_bug.cgi?id=204232, I went looking for jpeg-6 headers that may have been lingering an my system. I found a complete jpeg-6 installation in /usr/local, including headers. I don't know how they got there, but I'm guessing that some package picked up headers from usr/local and libjpeg.so.7 from /usr. I'm cleaning out my /usr/local and upgrading to jpeg-7 again, I'm almost certain this was the problem. I'll mark this as resolved/invalid and beg the forum's pardon. I've just confirmed that the jpeg-6 installation in /usr/local was indeed the problem. I also tracked down the package that put it there, a scientific application not supported by portage. Just an information for other people searching for the backtrace message: You have been linking against the wrong media-libs/jpeg version. If you re-emerge it, then you should see the following post-install message: * Old versions of installed libraries were detected on your system. * In order to avoid breaking packages that depend on these old libs, * the libraries are not being removed. You need to run revdep-rebuild * in order to remove these old dependencies. If you do not have this * helper program, simply emerge the 'gentoolkit' package. * * # revdep-rebuild --library libjpeg.so.62 * * Once you've finished running revdep-rebuild, it should be safe to * delete the old libraries. Here is a copy & paste for the lazy: * # rm '/usr/lib/libjpeg.so.62' |