Bug 225926 - K3b segfaults after displaying splash screen
Summary: K3b segfaults after displaying splash screen
Status: RESOLVED DUPLICATE of bug 204614
Alias: None
Product: k3b
Classification: Applications
Component: general (show other bugs)
Version: 1.70.0
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Sebastian Trueg
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-08 17:09 UTC by ralfgesellensetter
Modified: 2010-02-08 19:45 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
2 strace logs: crash vs. nocrash (11.07 KB, application/x-gzip)
2010-02-08 17:35 UTC, ralfgesellensetter
Details

Note You need to log in before you can comment on or make changes to this bug.
Description ralfgesellensetter 2010-02-08 17:09:56 UTC
Application that crashed: k3b
Version of the application: 1.70.0
KDE Version: 4.3.4 (KDE 4.3.4)
Qt Version: 4.5.3
Operating System: Linux 2.6.32-3.slh.3-sidux-686 i686
Distribution: Debian GNU/Linux unstable (sid)

What I was doing when the application crashed:
There is a segmentation fault, splash screen is displayed. 

Additionally to genuine debug log, I quote here outputs to stderr:

$ k3b
K3bQProcess::QProcess(0x0)
K3bQProcess::QProcess(0x0)
KCrash: Application 'k3b' crashing...
sock_file=/home/ralf/.kde/socket-siduxbox/kdeinit4__0
kdeinit4: preparing to launch /usr/lib/kde4/libexec/drkonqi
kdeinit4: preparing to launch /usr/bin/kwalletmanager
QSystemTrayIcon::setVisible: No Icon set
kdeinit4: preparing to launch /usr/lib/kde4/kio_http.so
kdeinit4: preparing to launch /usr/lib/libkdeinit4_kio_http_cache_cleaner.so
kdeinit4: preparing to launch /usr/lib/kde4/kio_pop3.so


 -- Backtrace:
Application: K3b (k3b), signal: Segmentation fault
[Current thread is 1 (Thread 0xb3ee1960 (LWP 4518))]

Thread 3 (Thread 0xb0fdbb70 (LWP 4545)):
[KCrash Handler]
#6  0xb77224c7 in K3b::Device::from4Byte(unsigned char*) () from /usr/lib/libk3bdevice.so.6
#7  0xb77055e3 in K3b::Device::Device::determineSupportedWriteSpeeds() const () from /usr/lib/libk3bdevice.so.6
#8  0xb75caffc in K3b::Medium::update() () from /usr/lib/libk3blib.so.6
#9  0xb75ce6ca in K3b::MediaCache::PollThread::run() () from /usr/lib/libk3blib.so.6
#10 0xb54975e2 in QThreadPrivate::start (arg=0x9173aa0) at thread/qthread_unix.cpp:188
#11 0xb43c7585 in start_thread () from /lib/i686/cmov/libpthread.so.0
#12 0xb48d826e in clone () from /lib/i686/cmov/libc.so.6

Thread 2 (Thread 0xb07dab70 (LWP 4546)):
#0  0xb7752424 in __kernel_vsyscall ()
#1  0xb43cb3d2 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/i686/cmov/libpthread.so.0
#2  0xb48e5834 in pthread_cond_timedwait () from /lib/i686/cmov/libc.so.6
#3  0xb5496fee in thread_sleep (ti=0xb07da2e0) at thread/qthread_unix.cpp:297
#4  0xb5497175 in QThread::sleep (secs=1265645148) at thread/qthread_unix.cpp:311
#5  0xb75ce759 in K3b::MediaCache::PollThread::run() () from /usr/lib/libk3blib.so.6
#6  0xb54975e2 in QThreadPrivate::start (arg=0x9010138) at thread/qthread_unix.cpp:188
#7  0xb43c7585 in start_thread () from /lib/i686/cmov/libpthread.so.0
#8  0xb48d826e in clone () from /lib/i686/cmov/libc.so.6

Thread 1 (Thread 0xb3ee1960 (LWP 4518)):
#0  0xb48e597b in pthread_mutex_lock () from /lib/i686/cmov/libc.so.6
#1  0xb3f8915c in ?? () from /usr/lib/libxcb.so.1
#2  0xb3f896ee in ?? () from /usr/lib/libxcb.so.1
#3  0xb3f89a97 in xcb_writev () from /usr/lib/libxcb.so.1
#4  0xb4504549 in _XSend () from /usr/lib/libX11.so.6
#5  0xb44f0c62 in ?? () from /usr/lib/libX11.so.6
#6  0xb44f00ef in ?? () from /usr/lib/libX11.so.6
#7  0xb44f0e6a in XPutImage () from /usr/lib/libX11.so.6
#8  0xb4ca9cbc in QX11PixmapData::fromImage (this=0x91a6bb0, img=..., flags=...) at image/qpixmap_x11.cpp:563
#9  0xb4c957a9 in QPixmap::fromImage (image=..., flags=...) at image/qpixmap.cpp:1968
#10 0xb4c98434 in QPixmap::load (this=0xbfcc1988, fileName=..., format=0x0, flags=...) at image/qpixmap.cpp:804
#11 0xb4c98bcd in QPixmap (this=0xbfcc1988, fileName=..., format=0x0, flags=...) at image/qpixmap.cpp:267
#12 0x081a4075 in _start ()

This bug may be a duplicate of or related to bug 225539

Reported using DrKonqi
Comment 1 ralfgesellensetter 2010-02-08 17:35:02 UTC
Created attachment 40603 [details]
2 strace logs: crash vs. nocrash

To support debugging, I add two outputs of strace:

k3b-strace.log stems from a call that did not lead to segfault
k3b-strace.log.1 is from a crashing call slightly later.

k3b seems to crash two or three times, when trying to launch, and then, again, it doesn't crash for two times or so. I hope that a diff on these logs can help more experienced developers to single out the source of this problem.
Comment 2 Michał Małek 2010-02-08 19:45:25 UTC

*** This bug has been marked as a duplicate of bug 204614 ***