Bug 106397 – libexif-0.6.12-r4 gcc4 patch causes digikam-0.8.0 beta1 & beta2 to crash

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Nir Dremer 2005-09-18 12:34:45 UTC]

libexif-0.6.12-r4 gcc4 patch causes digikam-0.8.0 beta & beta2 to crash during
application startup.

i created a test ebuild, removed gcc4 patch and it solves the problem.

Reproducible: Always
Steps to Reproduce:

[Comment 1 Nir Dremer 2005-09-18 12:35:57 UTC]

btw: check 106394, seems like gcc4 patchs impact also digikam 0.7.x.

[Comment 2 Mark Loeser (RETIRED) 2005-09-18 12:46:05 UTC]

Output of `emerge info'?

[Comment 3 Nir Dremer 2005-09-18 12:50:38 UTC]

emerge info
Portage 2.0.52-r1 (default-linux/x86/2005.0, gcc-3.4.4, glibc-2.3.5-r1, 2.6.12.5
i686)
=================================================================
System uname: 2.6.12.5 i686 AMD Athlon(TM) MP 2400+
Gentoo Base System version 1.12.0_pre8
ccache version 2.4 [enabled]
dev-lang/python:     2.3.5-r2, 2.4.1-r1
sys-apps/sandbox:    1.2.13
sys-devel/autoconf:  2.13, 2.59-r7
sys-devel/automake:  1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6
sys-devel/binutils:  2.16.1
sys-devel/libtool:   1.5.20
virtual/os-headers:  2.6.11-r2
ACCEPT_KEYWORDS="x86 ~x86"
AUTOCLEAN="yes"
CBUILD="i686-pc-linux-gnu"
CFLAGS="-O3 -march=athlon-xp -fprefetch-loop-arrays -pipe -fomit-frame-pointer"
CHOST="i686-pc-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.4/env
/usr/kde/3.4/share/config /usr/kde/3.4/shutdown /usr/kde/3/share/config
/usr/lib/X11/xkb /usr/share/config /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O3 -march=athlon-xp -fprefetch-loop-arrays -pipe -fomit-frame-pointer"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoconfig buildpkg ccache distlocks prelink sandbox sfperms strict"
GENTOO_MIRRORS="http://mirror.hamakor.org.il/pub/mirrors/gentoo/
http://ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/ http://gentoo.zie.pg.gda.pl
http://pandemonium.tiscali.de/pub/gentoo/"
LDFLAGS="-Wl,-O1 -Wl,--sort-common"
MAKEOPTS="-j3"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="x86 3dnow X alsa apm avi bash-completion bidi bitmap-fonts cups curl dvd
dvdr eds emboss encode fam firefox flac foomaticdb fortran gd gdbm gif gphoto2
gpm gstreamer gtk gtk2 imagemagick imlib irda jpeg kde lcd libwww mad mmx mmx2
motif mp3 mpeg ncurses nls nptl nvidia ogg oggvorbis opengl pam pdflib pic png
ppds readline samba sdl slang smp spell sqlite sse sse2 ssl tcpd tiff truetype
truetype-fonts type1-fonts unicode usb vorbis wxwindows xine xml xml2 xv zlib
userland_GNU kernel_linux elibc_glibc"
Unset:  ASFLAGS, CTARGET, LANG, LC_ALL, LINGUAS

[Comment 4 Nir Dremer 2005-09-18 13:40:01 UTC]

double-checking all the changes i did find it was something else.

jpeg-6b-r6 is the problem, moving to jpeg-6b-r5 solved the problem.

my entire system is ~x86, while only jpeg-6b-r6 is replaced with jpeg-6b-r5
solves the problem.

[Comment 5 Jakub Moc (RETIRED) 2005-09-18 13:50:59 UTC]

Marking INVALID, open a new bug for jpeg issue, please.

[Comment 6 Nir Dremer 2005-09-18 14:56:22 UTC]

libexif-0.6.12-r4 seems to have strange effects on digikam-0.8.0 beta1 & 2.

It causes in certain scenarions to crash digikam right on startup.

the simplest scenario i've found is creatng one folder inside the pictures
folder and let it contain 1 jpeg file that contains exif information.

moving to media-libs/libexif-0.5.12-r3 solves the problem.

more information can be found at http://bugs.kde.org/show_bug.cgi?id=112845
(originally i thought it's digikam internal bug)

[Comment 7 Nir Dremer 2005-09-27 08:22:13 UTC]

Does not happen with official digikam beta2 (it was repacked).