updated libjpeg broke amarok

broch · 2009-07-14 15:22:37

amarok: error while loading shared libraries: libjpeg.so.62: cannot open shared object file: No such file or directory

installed previous version of libjpeg and amarok works

with old libjpeg I can have amarok, desktop background and so on, but I will loose firefox:
as it generates error:
Couldn't load XPCOM

with new libjpeg I can have firefox but not kde relates stuff.

did abyone actually checked if libjpeg update will work?

so temporary fix is:
downgrade libjpeg and downgrade xulrunner

Last edited by broch (2009-07-14 15:35:27)

Rokixz · 2009-07-14 16:32:41

nexuiz not working too Wrong JPEG library version: library is 70, caller expects 62

wonder · 2009-07-14 16:36:30

nexuiz is in community. if you know we don't have a testing community repo. we have to wait packages from testing to be moved in core/extra before we can do something.

we are working on it.

rson451 · 2009-07-14 16:41:32

broch wrote:

did abyone actually checked if libjpeg update will work?

It looks like amarok has been flagged out of date, so the maintainer probably just hasn't had time to rebuild it yet. If you need it, rebuild it with abs against the new libjpeg.

Nexuiz has not been flagged out of date. If you are running the latest version available in community, then it probably needs a rebuild as well.

wonder · 2009-07-14 16:42:46

btw. don't flag of date packages if needs rebuild. file bug reports. but be sure that isn't reported before doing something.

broch · 2009-07-14 16:51:09

nevermind kdemod, but updating like this one generates a lot of problems. I am talking only about officially supported software.

Snowman · 2009-07-14 20:24:33

amarok works fine here. Make sure that your mirror has fully sync (it takes more time as usual for big updates like this) and that you are doing a full system update (pacman -Syu)

broch · 2009-07-14 22:24:28

latest version of amarok
2.1-1
latest version installed:
pacman -Q | grep amarok
amarok 2.1-1

latest version of libjpeg
7-1
latest version installed
pacman -Q libjpeg
libjpeg 7-1

amarok error (loading amarok from console)
$ amarok
amarok: error while loading shared libraries: libjpeg.so.62: cannot open shared object file: No such file or directory

when I downgrade libjpeg to the version 6b-6 amarok works, so I don't know how your amarok (same version) works with libjpeg 7-1

Last edited by broch (2009-07-14 22:27:18)

ok_computer · 2009-07-14 22:36:46

I second the problem.

djgera · 2009-07-14 22:37:34

run with
LD_DEBUG=files amarok

and see what is the library that tries to load the old libjpeg.

Allan · 2009-07-15 00:09:14

Amarok works fine here on i686 and given Snowman uses x86_64, I say we have all bases covered....

Are you using the Arch KDE or KDEmod? KDEmod probably does not work yet.

1LordAnubis · 2009-07-15 01:51:01

my amarok is broken as well, i use amarok-svn from the kdemod-playground repo, but i only noticed that from this thread...
which I was led to when my urxvt wouldn't work

$ urxvt
urxvt: error while loading shared libraries: libjpeg.so.62: cannot open shared object file: No such file or directory

Skripka · 2009-07-15 02:15:49

Allan wrote:

Amarok works fine here on i686 and given Snowman uses x86_64, I say we have all bases covered....
Are you using the Arch KDE or KDEmod? KDEmod probably does not work yet.

Allan,

FYI-I just did a pacman -Syu...I got the following error:

( 8/34) upgrading gtk2                              [#####################] 100%
g_module_open() failed for /usr/lib/gtk-2.0/2.10.0/loaders/io-wmf.so: libjpeg.so.62: cannot open shared object file: No such file or directory

EDIT: Upgrade appears to have gone smoothly though with Arch64 Vanilla KDE4.2.4 from Extra, Vanilla Amarok is fine too Gtk apps seem normal also.

Last edited by Skripka (2009-07-15 02:22:11)

firecat53 · 2009-07-15 02:58:52

Same error with Amarok1 and gpicview. Recompiled Amarok1 from AUR and gpicview from community (via abs). Fixed both issues.

Scott

Snowman · 2009-07-15 03:00:53

1LordAnubis wrote:

my amarok is broken as well, i use amarok-svn from the kdemod-playground repo, but i only noticed that from this thread...

AFAIK, the kdemod repo have not been rebuilt yet. If you use packages from these repo, expect some breakage until they rebuild their packages.

1LordAnubis wrote:

which I was led to when my urxvt wouldn't work
$ urxvt
urxvt: error while loading shared libraries: libjpeg.so.62: cannot open shared object file: No such file or directory

urxvt from the rxvt-unicode package in [extra] start fine. Are you using it or are you using another package (from community/AUR)?

Snowman · 2009-07-15 03:04:44

Skripka wrote:

FYI-I just did a pacman -Syu...I got the following error:
( 8/34) upgrading gtk2                              [#####################] 100%
g_module_open() failed for /usr/lib/gtk-2.0/2.10.0/loaders/io-wmf.so: libjpeg.so.62: cannot open shared object file: No such file or directory
EDIT: Upgrade appears to have gone smoothly though with Arch64 Vanilla KDE4.2.4 from Extra, Vanilla Amarok is fine too Gtk apps seem normal also.

I saw that error somewhere else. It happened because of a race condition: gtk2 was updated before libwmf. Just reinstall gtk2 to make sure that it is installed correctly.

1LordAnubis · 2009-07-15 03:39:55

Snowman wrote:

urxvt from the rxvt-unicode package in [extra] start fine. Are you using it or are you using another package (from community/AUR)?

ahh, I suppose I'm using the package from the aur

however, ln -s /usr/lib/libjpeg.so.7.0.0 /usr/lib/libjpeg.so.62 is a temporary fix until the packages get rebuilt

Allan · 2009-07-15 04:22:41

Symlink = bad and likely to cause interesting crashes. For an AUR package, you need to recompile it...

Lazer · 2009-07-15 05:31:02

GQView is acting strange after the libjpeg update. Some images are displayed ok but some others are shown as a black picture.
Already tried downgrading libjpeg or rebuilding gqview, none of them worked.
I thought of creating a new thread but it seems my problem is framed in this general one and there are at least 2 threads with the same issue active.
thanks.

Edar · 2009-07-16 13:44:08

hello gentlemen excuse my English, but not as good as my Spanish, now I had the same problem and you solve it as follows:

libjpeg 7-1 because it should not downgrade other units of importance here is the list at least mine:

:: gnash-common: necesita libjpeg>=7
:: jasper: necesita libjpeg>=7
:: libdjvu: necesita libjpeg>=7
:: libgphoto2: necesita libjpeg>=7
:: libmng: necesita libjpeg>=7
:: libtiff: necesita libjpeg>=7
:: mplayer: necesita libjpeg>=7
:: poppler: necesita libjpeg>=7
:: sane: necesita libjpeg>=7

Now with the previous version libjpeg-6b-6 only have to extract the files and copy them libjpeg.so.62 libjpeg.so.62.0.0 in place / usr / lib / with this problem will be solved at least my and other colleagues who use arch has worked

see you from Cuba Edar

DarkMind · 2009-07-16 23:37:05

use packages from testing , they are compiled with the new libjpeg

theringmaster · 2009-07-17 02:19:05

Savage and Savage 2 from the aur won't start anymore because of this same issue. I don't know what to do though, because they are precompiled binaries.

hbekel · 2009-07-17 04:01:25

theringmaster wrote:

Savage and Savage 2 from the aur won't start anymore because of this same issue. I don't know what to do though, because they are precompiled binaries.

Try to persuade the creators of the binaries to rebuild against libjpeg-7. If that doesn't work:

Keep a libjpeg.so.62.0.0 around (outside of */lib/) and use LD_PRELOAD to feed it to the binaries that require it:

LD_PRELOAD=/somewhere/outside/lib/libjpeg.so.62.0.0 binary

This is the cleanest solution since you will use the deprecated library explicitly and only for binaries that need them.

You may of course decide to keep libjpeg.so.62 system-wide alongside the new libjpeg.so.7. Just copy libjpeg.so.62.0.0 to /usr/lib and create the necessary symlinks. Beware though that any package that remains on your system and is not rebuild against libjpeg-7 will continue to use the old library (which may be a problem because it will not get any updates or security fixes). Use this method at your own risk, especially if you tend to forget about packages you build yourself.

As it has been mentioned before, simply pretending the old lib is still around by symlinking the new library under the old name is strongly advised against. It's a "solution" suggested only by people who simply don't know any better. It's most likely to fail anyways.

manouchk · 2009-07-17 21:42:28

Lazer wrote:

GQView is acting strange after the libjpeg update. Some images are displayed ok but some others are shown as a black picture.
Already tried downgrading libjpeg or rebuilding gqview, none of them worked.
I thought of creating a new thread but it seems my problem is framed in this general one and there are at least 2 threads with the same issue active.
thanks.

Same problem here with gqview and libjpeg 7.0. Never had this problem with gqview before. I built it again running
yaourt -Sb gqview --export /home/manu/abs

No chance, same problem after!!

(/home/manu/abs is where I'm used to recompile some few software using abs)

jorpheus · 2009-07-19 16:46:06

broch wrote:

amarok: error while loading shared libraries: libjpeg.so.62: cannot open shared object file: No such file or directory
installed previous version of libjpeg and amarok works
with old libjpeg I can have amarok, desktop background and so on, but I will loose firefox:
as it generates error:
Couldn't load XPCOM
with new libjpeg I can have firefox but not kde relates stuff.
did abyone actually checked if libjpeg update will work?
so temporary fix is:
downgrade libjpeg and downgrade xulrunner

Thanks, you saved me from (a even more) torturous experience. I upgraded everything but Firefox and Xulrunner, and then it stopped working, of course. The torture was downgrading all the packages that require libjpeg and all the packages that require those packages. Urgh.

Naturally, this broke other stuff, and I am now just waiting to see what exactly will malfunction. Hm.

Edit: It broke Gqview. So after some messing with symbolic links, I managed to get everything to work - except FF wouldn't show JPEG. Finally, I upgraded to 3.5, and found a dev version of Tab mix plus and Fast dial, so I only had to find a suitable theme to replace Abstract classic. Yaay.

Last edited by jorpheus (2009-07-20 15:21:05)

Arch Linux

#1 2009-07-14 15:22:37

updated libjpeg broke amarok

#2 2009-07-14 16:32:41

Re: updated libjpeg broke amarok

#3 2009-07-14 16:36:30

Re: updated libjpeg broke amarok

#4 2009-07-14 16:41:32

Re: updated libjpeg broke amarok

#5 2009-07-14 16:42:46

Re: updated libjpeg broke amarok

#6 2009-07-14 16:51:09

Re: updated libjpeg broke amarok

#7 2009-07-14 20:24:33

Re: updated libjpeg broke amarok

#8 2009-07-14 22:24:28

Re: updated libjpeg broke amarok

#9 2009-07-14 22:36:46

Re: updated libjpeg broke amarok

#10 2009-07-14 22:37:34

Re: updated libjpeg broke amarok

#11 2009-07-15 00:09:14

Re: updated libjpeg broke amarok

#12 2009-07-15 01:51:01

Re: updated libjpeg broke amarok

#13 2009-07-15 02:15:49

Re: updated libjpeg broke amarok

#14 2009-07-15 02:58:52

Re: updated libjpeg broke amarok

#15 2009-07-15 03:00:53

Re: updated libjpeg broke amarok

#16 2009-07-15 03:04:44

Re: updated libjpeg broke amarok

#17 2009-07-15 03:39:55

Re: updated libjpeg broke amarok

#18 2009-07-15 04:22:41

Re: updated libjpeg broke amarok

#19 2009-07-15 05:31:02

Re: updated libjpeg broke amarok

#20 2009-07-16 13:44:08

Re: updated libjpeg broke amarok

#21 2009-07-16 23:37:05

Re: updated libjpeg broke amarok

#22 2009-07-17 02:19:05

Re: updated libjpeg broke amarok

#23 2009-07-17 04:01:25

Re: updated libjpeg broke amarok

#24 2009-07-17 21:42:28

Re: updated libjpeg broke amarok

#25 2009-07-19 16:46:06

Re: updated libjpeg broke amarok

Board footer