Bug 75542 – k3b crashes when the burn button is pressed

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description David Holm (RETIRED) 2004-12-24 05:37:23 UTC]

K3B will crash when either the burn button is pressed or when you select burn from one of the menus. 
K3B:      0.11.18
kdelibs:  3.3.2-r1
cdrtools: 2.01.01_alpha01
I have the same problem on both ~ppc and ~x86.

emerge info:
Portage 2.0.51-r8 (default-linux/ppc/2004.3, gcc-3.4.3, glibc-2.3.4.20041102-r0, 2.6.9-pegasos-r3 ppc)
=================================================================
System uname: 2.6.9-pegasos-r3 ppc 7447/7457, altivec supported
Gentoo Base System version 1.6.8
Python:              dev-lang/python-2.3.4 [2.3.4 (#1, Dec  6 2004, 13:54:36)]
dev-lang/python:     2.3.4
sys-devel/autoconf:  2.59-r6, 2.13
sys-devel/automake:  1.6.3, 1.7.9, 1.4_p6, 1.9.3, 1.5, 1.8.5-r2
sys-devel/binutils:  2.15.90.0.3-r3
sys-devel/libtool:   1.5.10-r2
virtual/os-headers:  2.6.8.1-r1
ACCEPT_KEYWORDS="ppc ~ppc"
AUTOCLEAN="yes"
CFLAGS="-O3 -mcpu=G4 -maltivec -mabi=altivec -fno-strict-aliasing -fsigned-char -pipe"
CHOST="powerpc-unknown-linux-gnu"
CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.3/env /usr/kde/3.3/share/config /usr/kde/3.3/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/lib/mozilla/defaults/pref /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control"
CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d"
CXXFLAGS="-O3 -mcpu=G4 -maltivec -mabi=altivec -fno-strict-aliasing -fsigned-char -pipe"
DISTDIR="/usr/portage/distfiles"
FEATURES="autoaddcvs autoconfig ccache distlocks sfperms"
GENTOO_MIRRORS="ftp://trumpetti.atm.tut.fi/gentoo/ ftp://ftp.tu-clausthal.de/pub/linux/gentoo/ ftp://sunsite.informatik.rwth-aachen.de/pub/Linux/gentoo ftp://mirror.nutsmaas.nl/gentoo/ ftp://ftp-stud.fht-esslingen.de/pub/Mirrors/gentoo/"
MAKEOPTS="-j2"
PKGDIR="/usr/portage/packages"
PORTAGE_TMPDIR="/var/tmp"
PORTDIR="/usr/portage"
PORTDIR_OVERLAY="/usr/local/portage"
SYNC="rsync://rsync.gentoo.org/gentoo-portage"
USE="X aalib alsa altivec artworkextra audiofile berkdb bitmap-fonts blas bonobo bzlib cairo cdparanoia cdr crypt cscope cups divx4linux dv dvd dvdread edl eep encode esd extensions f77 faac faad fam fbcon flac fortran fpx gdbm gif gnome gnomedb gnutls gphoto2 graphviz gstreamer gtk gtk2 gtkhtml hal howl idea imagemagick imlib ipv6 java jbig jpeg lapack lcms ldap libcaca libgda libwww live lzo lzw-tiff mad matroska mikmod mmap mng mono motif mozcalendar mozdevelop mozilla mpeg mpi mysql ncurses network nptl objc offensive oggvorbis opengl oss pcre perl physfs pic png ppc ppds python qt quicktime readline rtc ruby samba sdl slang slp sndfile snortsam speex spell sqlite ssl svg tcltk tcpd tetex tga theora threads tiff timidity truetype truetype-fonts type1-fonts videos vnc wmf xine xml xml2 xmms xprint xv xvid yv12 zlib video_cards_radeon"

[Comment 1 Gregorio Guidi (RETIRED) 2004-12-24 06:58:26 UTC]

Have you got a backtrace, or at least some errors when you run k3b in a console?
You can also look for similar bugs on bugs.kde.org (there are many), some of
them caused by multiple kdelibs, or by stale libraries (e.g. 
http://bugs.kde.org/show_bug.cgi?id=88095)

[Comment 2 David Holm (RETIRED) 2004-12-25 03:12:19 UTC]

I don't have Dr Konqi installed on the ppc box, the only output I get in a console is that "Dr Konqi" isn't installed.
On the x86 I get the following backtrace:
Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 16384 (LWP 14225)]
0xb69231e8 in waitpid () from /lib/libpthread.so.0
#0  0xb69231e8 in waitpid () from /lib/libpthread.so.0
#1  0xb752eee8 in ?? () from /usr/kde/3.3/lib/libkdecore.so.4
#2  0xb745902c in KCrash::defaultCrashHandler ()
   from /usr/kde/3.3/lib/libkdecore.so.4
#3  0x00003791 in ?? ()
#4  0xbfffe600 in ?? ()
#5  0x00000122 in ?? ()
#6  0x00000010 in ?? ()
#7  0x00000010 in ?? ()
#8  0x00000010 in ?? ()
#9  0x00000020 in ?? ()
#10 0xb6c21960 in QApplication::style () from /usr/qt/3/lib/libqt-mt.so.3

I don't see an obvious problem in that backtrace :/

[Comment 3 Gregorio Guidi (RETIRED) 2004-12-26 06:23:36 UTC]

Yes, that's not much helpful, probably k3b should be compiled with
FEATURES="nostrip" USE="debug" to provide a valid backtrace, hoping that the 
crash is in k3b code and not in qt or in some underlying library.

[Comment 4 Daniel Black (RETIRED) 2005-01-02 15:31:19 UTC]

Message-ID: <[e-mail]>
Date: Sun, 02 Jan 2005 17:41:37 -0500
From: Kenton Groombridge <[e-mail]>
To: [e-mail]
Subject: Re: [gentoo-user] k3b crashes

I had these crashes as well and moving the the 2.6.10 kernel fixed it 
for me.

Ken


Makurin Roman wrote:

>Hi All!
>I`ve got a problem with k3b. When I press "Burn" button k3b crashes every 
>time.
>How can I solve this problem ?
>
>About my system:
>gentoo-dev-sources-2.6.9-r13
>k3b-0.11.18
>cdrtools-2.01
>cdrdao-1.1.9
>
>
>Thanks
>  
>

[Comment 5 Roman Dilken 2005-01-10 05:41:40 UTC]

I can't agree with you that moving to 2.6.10 solves the problem...

[Comment 6 Andrew Williams 2005-01-16 11:10:39 UTC]

Same here - 2.6.10 and still crashes when I hit burn.

System is an amd64

[Comment 7 David Holm (RETIRED) 2005-01-31 03:57:30 UTC]

0.11.19 is working for me.

[Comment 8 Makurin Roman 2005-01-31 18:51:32 UTC]

k3b-0.11.19 fix this problem...
Here`s link to KDE bugzilla: http://bugs.kde.org/show_bug.cgi?id=97816

[Comment 9 Gregorio Guidi (RETIRED) 2005-02-01 02:18:15 UTC]

Closing.