You are not logged in.
I have KDE 4.3 RC installed, and, as I read here, we have to have libjpeg from [testing] installed. But after I installed it, jpg images, mainly in forums, become too ... big in Konqueror, they aren't shrinked properly
Has anyone else seen such an issue ?
Offline
libjpeg hasn't been updated for a long time and a lot of programs need to be compiled against it. Try recompiling konqueror from abs or downgrading libjpeg.
"I'm Winston Wolfe. I solve problems."
~ Need moar games? [arch-games] ~ [aurcheck] AUR haz updates? ~
Offline
I don't think the [kde-unstable] packages have been updated to the libjpeg version yet (well, you results suggest they have not). I did warn people not to upgrade to [testing] for a couple of days unless the liked broken stuff...
Offline
So, I should downgrade to the stable one I suppose ?
--------
I think Konqueror (so... kdebase) is rebuilt with the new libjpeg, since after I downgraded to the stable libjpeg, a pop-error window appeared that requested the new .so provided by the latest libjpeg.
Last edited by flamelab (2009-07-02 10:59:06)
Offline
For x86_64 you should use the new libjpeg; i686 should follow soon.
Offline
Yes, I have a x86_64 system. But that problem (with jpeg images that aren't shrinking and become large) exists (KDE 4.3 RC + the [testing] libjpeg).
Offline
OK, I see. Lokks like KDE is not compatible with new libjpeg. Seems like they don't only changed the ABI; so a rebuild did not help.
Offline
Someone ought to inform them upstream, so that they will be informed (if they aren't aware of this issue already).
Offline
OK, I see. Lokks like KDE is not compatible with new libjpeg. Seems like they don't only changed the ABI; so a rebuild did not help.
libjpeg7 is _supposed_ API compatible so this is a bit weird... I'd be interested to know what is causing the breakage.
Offline
I'd propose that you should fall back to the stable libjpeg for most packages, since the new one *breaks* a lot of things. Even svn versions of some programs (amarok), kde or not, can't just be rebuilt with the new libjpeg in order to (just) work. Amarok crashes for example.
If you won't find a patch or something till the day KDE 4.3 arrives in [extra], I think that you should build it with the current libjpeg, and not the testing one, because a lot of users (all those that use KDE, and will update to 4.3), will face problems.
---
Some programs won't work with new libjpeg (for example: filezilla, which I use a lot). Symlinking is TOO messy (and not standard), but I did it in order to have it work, since it can't be built with the new libjpeg.
Last edited by flamelab (2009-07-03 06:58:10)
Offline
filezilla is not even on the list of packages that need rebuilt and runs fine here. Are you sure that amarok from svn not building is from libjpeg? The API did not change, just the ABI so that seems wrong...
Offline
filezila doesn't work for me.
so did amsn, but i compiled it using abs PKGBUILD and now runs fine.
up to now im rebuilding filezilla, also from abs, in order to see if it works.
Last edited by mechmg93 (2009-07-03 07:31:49)
Mikes on AUR
Offline
filezilla is not even on the list of packages that need rebuilt and runs fine here. Are you sure that amarok from svn not building is from libjpeg? The API did not change, just the ABI so that seems wrong...
Nope, it's not working. It can't be built with the new libjpeg, can't work with the new libjpeg. If you have already installed filezilla, you have to make *dirty* symlinks, which is too wrong, in my opinion.
Amarok-svn can be built with new libjpeg (even though I 'll try to rebuild it with VERBOSE=1, so that I find out if there are any hidden errors during compiling), and if try to open it, it crashes and in the error window, I find libjpeg errors.
I strongly propose: please don't rebuild packages with the newest libjpeg, since many of them aren't newest-libjpeg aware, even if they are built with it.
Offline
i had no problems building amarok2-svn from aur with the new libjpeg.
Mikes on AUR
Offline
Can you run amarok ?
Application: Amarok (amarok), signal: Segmentation fault
[KCrash Handler]
#5 0x0000000001dcd9e1 in ?? ()
#6 0x00007fff1ada8480 in ?? ()
#7 0x00007f246dddb9b5 in jpeg_CreateDecompress () from /usr/lib/libjpeg.so.7
#8 0x00007f24684cf7ff in ?? () from /usr/lib/qt/plugins/imageformats/libqjpeg.so
#9 0x00007f2477446a83 in QImageReader::read () from /usr/lib/libQtGui.so.4
#10 0x00007f2477446fec in QImageReader::read () from /usr/lib/libQtGui.so.4
#11 0x00007f24774563f1 in QPixmap::load () from /usr/lib/libQtGui.so.4
#12 0x00007f2477456b37 in QPixmap::QPixmap () from /usr/lib/libQtGui.so.4
#13 0x00007f24783788f6 in App::App () from /usr/lib/libamaroklib.so.1
#14 0x000000000040404d in _start ()
I have only libjpeg from [testing] installed, nothing else. If there is any package that I should install, please tell me, I'd be grateful.
Last edited by flamelab (2009-07-03 07:41:46)
Offline
i also have qt from testing. maybe this is your problem but i am not sure.
Mikes on AUR
Offline
I'll try it, thank you.
-----
OK, amarok runs OK now. I hoped that this jpeg issue on Konqueror would be solved with this Qt, but it persists.
Last edited by flamelab (2009-07-03 07:48:21)
Offline
I'll try to upgrade to [testing], in order to check if these problems persist.
________
It does . Filezilla now works, since I think that it needed wxgtk from testing.
Last edited by flamelab (2009-07-03 08:09:29)
Offline
I'll try to upgrade to [testing], in order to check if these problems persist.
________
It does . Filezilla now works, since I think that it needed wxgtk from testing.
*mikes is testing the wxgtk thing....
It seems that most of the problems are solved with testing packages. I also needed xulrunner from testing in order to make firefox work..
edit:
filezilla also runs fine here with wxgtk from testing.
Last edited by mechmg93 (2009-07-03 08:16:00)
Mikes on AUR
Offline
*$^#%^&.... don't complain if you are not fully updated or mixing and matching from [testing]. That is not how [testing] works. It is an all or none situation.
Offline
*$^#%^&.... don't complain if you are not fully updated or mixing and matching from [testing]. That is not how [testing] works. It is an all or none situation.
Allan, i am not complaining at all. Choosing to use kde-unstable, means that i know what i am doing, and that its normal to have problems as the above.
The one i'm trying to do is not have testing always enabled, but just install whatever is needed from testing repo, so that i do not have any problems with kde-unstable.
Mikes on AUR
Offline
@mechmg93: That post was not directed at you, but the post above your...
Offline
Allan, check this out yourself. Kdebase is a very crucial system package that will enter extra very soon. This issue occurs mainly in forums where jpeg images exist in signatures, avatars ...
If you want, I can post screenshots.
Last edited by flamelab (2009-07-03 11:06:27)
Offline
I have created a bug report: https://bugs.kde.org/show_bug.cgi?id=198779
Offline
Speaking of libjpeg, testing/digikam (0.10.0-3) has unreasonable requirements:
$ ldd `which digikam` | grep libjpeg
libjpeg.so.62 => not found
libjpeg.so.7 => /usr/lib/libjpeg.so.7 (0x00007f57013a8000)
Any ideas how to make it happy?
Also, some stuff in kdemod-core still needs libjpeg.so.62 to run (most notably gwenview, konqueror and desktop wallpaper). Sigh.
Offline