Re: [opensuse-factory] libjpeg-turbo
Moving to libjpeg-turbo would fix bnc#620175 Opensuse 11.3 Chrome Stable Crashes When Trying to Attach a File. Basically the problem is that Google's build of Chrome is against libjpeg6 (because Ubuntu and Fedora use 6 - Fedora 14 uses libjpeg-turbo, I haven't checked Ubuntu yet). This causes chrome to crash when a gtk filechooser dialog sees a jpeg file (tries to load the pixbuf loader which crashes because the loader is linked to libjpeg8). This mixed jpeg problem will also cause problems for any app or browser plugin compiled for other distros that happens to use gtk for file choosers. For example it causes a crash with Novell's Moonlight plugin on chrome for a similar reason (we use pixbuf loaders for all images, we're looking at switching). The fun part is that our own plugin only crashes in this way on our own distro. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
El 04/11/10 15:10, Andrew Jorgensen escribió:
Moving to libjpeg-turbo would fix bnc#620175 Opensuse 11.3 Chrome Stable Crashes When Trying to Attach a File.
Basically the problem is that Google's build of Chrome is against libjpeg6 (because Ubuntu and Fedora use 6 - Fedora 14 uses libjpeg-turbo, I haven't checked Ubuntu yet). This causes chrome to crash
We have our chrome builds, do not use Google's build, unfortunately vendors, as odd it may sound, having millions of dollars and huge staffing have zero clue about how to deliver working/correct rpms. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Cristian Rodríguez wrote:
El 04/11/10 15:10, Andrew Jorgensen escribió:
Moving to libjpeg-turbo would fix bnc#620175 Opensuse 11.3 Chrome Stable Crashes When Trying to Attach a File.
Basically the problem is that Google's build of Chrome is against libjpeg6 (because Ubuntu and Fedora use 6 - Fedora 14 uses libjpeg-turbo, I haven't checked Ubuntu yet). This causes chrome to crash
We have our chrome builds, do not use Google's build, unfortunately vendors, as odd it may sound, having millions of dollars and huge staffing have zero clue about how to deliver working/correct rpms.
Have you ever tried producing a binary (even for a piece of free software) that works across several releases/distros? Though job. Exchanging perceived core system libraries like libjpeg that never changed the last 100 years with incompatible ones doesn't make the job easier. Including or statically linking such libraries means you have to maintain them yourself, ie track security fixes etc and you potentially lack distro integration. That's not nice either but usually what ISVs do. cu Ludwig -- (o_ Ludwig Nussel //\ V_/_ http://www.suse.de/ SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (3)
-
Andrew Jorgensen -
Cristian Rodríguez -
Ludwig Nussel