[arch-general] Latest updates messed up kdemod3 libjpeg.so.62?
Listmates, Up until this past week kdemod3 and kde4-unstable had lived side-by-side quite harmoniously. However, now kcontol in kdemod3 will not run until the following link is created: ln -s /usr/lib/libjpeg.so.7 /usr/lib/libjpeg.so.62 After the link is made, kcontol will start, but any attempt to access the panel or taskbar settings (among others) results in a complete kcontrol crash. The backtraces are generally the same: [KCrash handler] #5 0x0000000000000000 in ?? () #6 0x00007f3a2e4f29b5 in jpeg_CreateDecompress () from /usr/lib/libjpeg.so.62 #7 0x00007f3a2d92de78 in ?? () from /opt/qt/plugins/imageformats/libqjpeg.so #8 0x00007f3a337d32f9 in QImageIO::read () from /opt/qt/lib/libqt-mt.so.3 #9 0x00007f3a337d3696 in QImage::load () from /opt/qt/lib/libqt-mt.so.3 #10 0x00007f3a2a9e1b3d in KBackgroundRenderer::doWallpaper () from /opt/kde/lib/kde3/kcm_kicker.so #11 0x00007f3a2a9e270a in KBackgroundRenderer::render () from /opt/kde/lib/kde3/kcm_kicker.so #12 0x00007f3a2a9e2a28 in KBackgroundRenderer::qt_invoke () from /opt/kde/lib/kde3/kcm_kicker.so #13 0x00007f3a337fd3cf in QObject::activate_signal () from /opt/qt/lib/libqt-mt.so.3 #14 0x00007f3a337ff726 in QObject::activate_signal () from /opt/qt/lib/libqt-mt.so.3 #15 0x00007f3a3381d8a5 in QTimer::event () from /opt/qt/lib/libqt-mt.so.3 #16 0x00007f3a3379fc75 in QApplication::internalNotify () from /opt/qt/lib/libqt-mt.so.3 #17 0x00007f3a337a0dca in QApplication::notify () from /opt/qt/lib/libqt-mt.so.3 #18 0x00007f3a34f91ee2 in KApplication::notify () from /opt/kde/lib/libkdecore.so.4 #19 0x00007f3a33796353 in QEventLoop::activateTimers () from /opt/qt/lib/libqt-mt.so.3 #20 0x00007f3a337517b8 in QEventLoop::processEvents () from /opt/qt/lib/libqt-mt.so.3 #21 0x00007f3a337b6609 in QEventLoop::enterLoop () from /opt/qt/lib/libqt-mt.so.3 #22 0x00007f3a337b64c2 in QEventLoop::exec () from /opt/qt/lib/libqt-mt.so.3 #23 0x00007f3a2f0555fa in kdemain () from /opt/kde/lib/libkdeinit_kcontrol.so #24 0x00000000004076e8 in ?? () #25 0x0000000000407e85 in ?? () #26 0x0000000000408562 in ?? () #27 0x0000000000408ea4 in ?? () #28 0x00007f3a313d69ed in __libc_start_main () from /lib/libc.so.6 #29 0x0000000000404549 in ?? () #30 0x00007fff9c658818 in ?? () #31 0x000000000000001c in ?? () #32 0x0000000000000005 in ?? () #33 0x00007fff9c659ad5 in ?? () #34 0x0000000000000000 in ?? () Do I need to create another link or a different link to solve this problem. Also, where should this bug report go? Chakra or Arch? -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
On Tue, Jul 28, 2009 at 3:44 PM, David C. Rankin<drankinatty@suddenlinkmail.com> wrote:
Listmates,
Up until this past week kdemod3 and kde4-unstable had lived side-by-side quite harmoniously. However, now kcontol in kdemod3 will not run until the following link is created:
ln -s /usr/lib/libjpeg.so.7 /usr/lib/libjpeg.so.62
After the link is made, kcontol will start, but any attempt to access the panel or taskbar settings (among others) results in a complete kcontrol crash. The backtraces are generally the same:
[KCrash handler] #5 0x0000000000000000 in ?? () #6 0x00007f3a2e4f29b5 in jpeg_CreateDecompress () from /usr/lib/libjpeg.so.62 #7 0x00007f3a2d92de78 in ?? () from /opt/qt/plugins/imageformats/libqjpeg.so #8 0x00007f3a337d32f9 in QImageIO::read () from /opt/qt/lib/libqt-mt.so.3 #9 0x00007f3a337d3696 in QImage::load () from /opt/qt/lib/libqt-mt.so.3 #10 0x00007f3a2a9e1b3d in KBackgroundRenderer::doWallpaper () from /opt/kde/lib/kde3/kcm_kicker.so #11 0x00007f3a2a9e270a in KBackgroundRenderer::render () from /opt/kde/lib/kde3/kcm_kicker.so #12 0x00007f3a2a9e2a28 in KBackgroundRenderer::qt_invoke () from /opt/kde/lib/kde3/kcm_kicker.so #13 0x00007f3a337fd3cf in QObject::activate_signal () from /opt/qt/lib/libqt-mt.so.3 #14 0x00007f3a337ff726 in QObject::activate_signal () from /opt/qt/lib/libqt-mt.so.3 #15 0x00007f3a3381d8a5 in QTimer::event () from /opt/qt/lib/libqt-mt.so.3 #16 0x00007f3a3379fc75 in QApplication::internalNotify () from /opt/qt/lib/libqt-mt.so.3 #17 0x00007f3a337a0dca in QApplication::notify () from /opt/qt/lib/libqt-mt.so.3 #18 0x00007f3a34f91ee2 in KApplication::notify () from /opt/kde/lib/libkdecore.so.4 #19 0x00007f3a33796353 in QEventLoop::activateTimers () from /opt/qt/lib/libqt-mt.so.3 #20 0x00007f3a337517b8 in QEventLoop::processEvents () from /opt/qt/lib/libqt-mt.so.3 #21 0x00007f3a337b6609 in QEventLoop::enterLoop () from /opt/qt/lib/libqt-mt.so.3 #22 0x00007f3a337b64c2 in QEventLoop::exec () from /opt/qt/lib/libqt-mt.so.3 #23 0x00007f3a2f0555fa in kdemain () from /opt/kde/lib/libkdeinit_kcontrol.so #24 0x00000000004076e8 in ?? () #25 0x0000000000407e85 in ?? () #26 0x0000000000408562 in ?? () #27 0x0000000000408ea4 in ?? () #28 0x00007f3a313d69ed in __libc_start_main () from /lib/libc.so.6 #29 0x0000000000404549 in ?? () #30 0x00007fff9c658818 in ?? () #31 0x000000000000001c in ?? () #32 0x0000000000000005 in ?? () #33 0x00007fff9c659ad5 in ?? () #34 0x0000000000000000 in ?? ()
Do I need to create another link or a different link to solve this problem. Also, where should this bug report go? Chakra or Arch?
report that to Chakra. Looks like kdemod3 needs to be rebuilt against libjpeg 7.
On Tuesday 28 July 2009 02:48:14 pm Eric Bélanger wrote:
On Tue, Jul 28, 2009 at 3:44 PM, David C. Rankin<drankinatty@suddenlinkmail.com> wrote:
Do I need to create another link or a different link to solve this problem. Also, where should this bug report go? Chakra or Arch?
report that to Chakra. Looks like kdemod3 needs to be rebuilt against libjpeg 7.
I added to the existing one: http://chakra-project.org/bugs/index.php?do=details&task_id=38 for anyone else interested. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com
Eric Bélanger schrieb:
report that to Chakra. Looks like kdemod3 needs to be rebuilt against libjpeg 7.
Reports about libjpeg+kdemod breakage have been coming in for a while. The SONAME bump was announced on arch-dev-public, then packages went to testing a week later, then the packages stayed in testing for another two weeks - so they had 3 weeks to fix their stuff, thus it really can't be our fault. Given the popularity of kdemod, it is sad that they can't seem to keep up with Arch's development.
Thomas Bächler wrote:
Eric Bélanger schrieb:
report that to Chakra. Looks like kdemod3 needs to be rebuilt against libjpeg 7.
Reports about libjpeg+kdemod breakage have been coming in for a while. The SONAME bump was announced on arch-dev-public, then packages went to testing a week later, then the packages stayed in testing for another two weeks - so they had 3 weeks to fix their stuff, thus it really can't be our fault.
Given the popularity of kdemod, it is sad that they can't seem to keep up with Arch's development.
They're generally pretty good about keeping up to date. I think the package maintainer is just currently buried in some work/school insanity right now. DR
On Dienstag, 28. Juli 2009 23:08 Thomas Bächler wrote:
Given the popularity of kdemod, it is sad that they can't seem to keep up with Arch's development.
I think the problem is more kdemod3 because the packages were built with the older gcc and if they really want to rebuilt them than this could be a very hard work. So from my view using the libjpeg6 from aur would be the best compromise. See you, Attila
2009/7/28 David C. Rankin <drankinatty@suddenlinkmail.com>:
Up until this past week kdemod3 and kde4-unstable had lived side-by-side quite harmoniously. However, now kcontol in kdemod3 will not run until the following link is created:
ln -s /usr/lib/libjpeg.so.7 /usr/lib/libjpeg.so.62
I also use kdemod-legacy on one computer. As the symlink doesn't work I simply untarred ibjpeg.so.62 from the old libjpeg pakage.
José M. Prieto wrote:
2009/7/28 David C. Rankin <drankinatty@suddenlinkmail.com>:
Up until this past week kdemod3 and kde4-unstable had lived side-by-side quite harmoniously. However, now kcontol in kdemod3 will not run until the following link is created:
ln -s /usr/lib/libjpeg.so.7 /usr/lib/libjpeg.so.62
I also use kdemod-legacy on one computer. As the symlink doesn't work I simply untarred ibjpeg.so.62 from the old libjpeg pakage.
Better to install libjpeg6 from aur. It's generally a bad idea to manually install system files. You should let pacman do that. DR
On Wed, Jul 29, 2009 at 11:48, David Rosenstrauch<darose@darose.net> wrote:
Better to install libjpeg6 from aur. It's generally a bad idea to manually install system files. You should let pacman do that.
DR
And best to actually _fix_ the issue: recompile the software against libjpeg7
Daenyth Blank wrote:
On Wed, Jul 29, 2009 at 11:48, David Rosenstrauch<darose@darose.net> wrote:
Better to install libjpeg6 from aur. It's generally a bad idea to manually install system files. You should let pacman do that.
DR
And best to actually _fix_ the issue: recompile the software against libjpeg7
Certainly! But until the maintainer gets around to doing that, this would be the appropriate band-aid. DR
On Tue, 2009-07-28 at 14:44 -0500, David C. Rankin wrote:
ln -s /usr/lib/libjpeg.so.7 /usr/lib/libjpeg.so.62
After the link is made, kcontol will start, but any attempt to access the panel or taskbar settings (among others) results in a complete kcontrol crash. The backtraces are generally the same:
Why do you think the soname was bumped? Just to give us maintainers some extra work, or would there be some other reason? Never symlink libraries like that, unless you are 100% sure that the soname bump was a mistake. In case it's an unused linked library, the symlink will work, but in case it's a library that is in use, like libjpeg, you will face problems. It's better to temporary extract the old lib on your system until the affected packages get updated, though that's also not a warranty for a working binary, as two different versions of a library linked into one program could conflict.
David C. Rankin wrote:
Listmates,
Up until this past week kdemod3 and kde4-unstable had lived side-by-side quite harmoniously. However, now kcontol in kdemod3 will not run until the following link is created:
ln -s /usr/lib/libjpeg.so.7 /usr/lib/libjpeg.so.62
Don't do that. Fix it by installing libjpe6 from AUR. DR
participants (8)
-
Attila
-
Daenyth Blank
-
David C. Rankin
-
David Rosenstrauch
-
Eric Bélanger
-
Jan de Groot
-
José M. Prieto
-
Thomas Bächler