Application: k3b (2.0.2) KDE Platform Version: 4.5.5 (KDE 4.5.5) Qt Version: 4.6.3 Operating System: Linux 2.6.34.7-66.fc13.i686.PAE i686 Distribution: "Fedora release 13 (Goddard)" -- Information about the crash: - What I was doing when the application crashed: I simply launched the program, clicking on the icon I found after having installed the program. The crash happens every time, no matter what I'm doing. On request I can provide You with any information You deem useful. The crash can be reproduced every time. -- Backtrace: Application: K3b (k3b), signal: Aborted [KCrash Handler] #7 0x0016c416 in __kernel_vsyscall () #8 0x0089abd1 in raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 #9 0x0089c4aa in abort () at abort.c:92 #10 0x008d86ed in __libc_message (do_abort=2, fmt=0x9bd5ac "*** glibc detected *** %s: %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:186 #11 0x008deb41 in malloc_printerr (action=<value optimized out>, str=<value optimized out>, ptr=0x9b5c3a0) at malloc.c:6283 #12 0x002a6532 in operator delete (ptr=0x9b5c3a0) at ../../../../libstdc++-v3/libsupc++/del_op.cc:44 #13 0x002a658e in operator delete[] (ptr=0x9b5c3a0) at ../../../../libstdc++-v3/libsupc++/del_opv.cc:32 #14 0x00ef21b8 in K3b::Device::Device::checkWritingModes (this=0x9a583f8) at /usr/src/debug/k3b-2.0.2/libk3bdevice/k3bdevice.cpp:3185 #15 0x00efa590 in K3b::Device::Device::init (this=0x9a583f8, bCheckWritingModes=true) at /usr/src/debug/k3b-2.0.2/libk3bdevice/k3bdevice.cpp:406 #16 0x00f03521 in K3b::Device::DeviceManager::addDevice (this=0x9a38c70, device=0x9a583f8) at /usr/src/debug/k3b-2.0.2/libk3bdevice/k3bdevicemanager.cpp:372 #17 0x00f04b92 in K3b::Device::DeviceManager::addDevice (this=0x9a38c70, solidDevice=...) at /usr/src/debug/k3b-2.0.2/libk3bdevice/k3bdevicemanager.cpp:360 #18 0x0818420a in K3b::AppDeviceManager::addDevice (this=0x9a38c70, solidDev=...) at /usr/src/debug/k3b-2.0.2/src/k3bappdevicemanager.cpp:120 #19 0x00f02a5b in K3b::Device::DeviceManager::checkDevice (this=0x9a38c70, dev=...) at /usr/src/debug/k3b-2.0.2/libk3bdevice/k3bdevicemanager.cpp:250 #20 0x00f03216 in K3b::Device::DeviceManager::scanBus (this=0x9a38c70) at /usr/src/debug/k3b-2.0.2/libk3bdevice/k3bdevicemanager.cpp:238 #21 0x005adeee in K3b::Core::init (this=0x9a31480) at /usr/src/debug/k3b-2.0.2/libk3b/core/k3bcore.cpp:200 #22 0x0813e1c0 in K3b::Application::Core::init (this=0x9a31480) at /usr/src/debug/k3b-2.0.2/src/k3bapplication.cpp:317 #23 0x0813f476 in K3b::Application::init (this=0xbffe21c8) at /usr/src/debug/k3b-2.0.2/src/k3bapplication.cpp:116 #24 0x0813faab in K3b::Application::qt_metacall (this=0xbffe21c8, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0xbffe191c) at /usr/src/debug/k3b-2.0.2/i686-redhat-linux-gnu/src/k3bapplication.moc:80 #25 0x01078bcb in QMetaObject::metacall (object=0xbffe21c8, cl=QMetaObject::InvokeMetaMethod, idx=29, argv=0xbffe191c) at kernel/qmetaobject.cpp:237 #26 0x01087a75 in QMetaObject::activate (sender=0x9a30d80, m=0x1188628, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3295 #27 0x0108d538 in QSingleShotTimer::timeout (this=0x9a30d80) at .moc/release-shared/qtimer.moc:82 #28 0x0108d65d in QSingleShotTimer::timerEvent (this=0x9a30d80) at kernel/qtimer.cpp:308 #29 0x01083ee4 in QObject::event (this=0x9a30d80, e=0xbffe1e50) at kernel/qobject.cpp:1212 #30 0x048e177c in QApplicationPrivate::notify_helper (this=0x98ef8c8, receiver=0x9a30d80, e=0xbffe1e50) at kernel/qapplication.cpp:4306 #31 0x048e81d6 in QApplication::notify (this=0xbffe21c8, receiver=0x9a30d80, e=0xbffe1e50) at kernel/qapplication.cpp:3710 #32 0x03ce4a5b in KApplication::notify (this=0xbffe21c8, receiver=0x9a30d80, event=0xbffe1e50) at /usr/src/debug/kdelibs-4.5.5/kdeui/kernel/kapplication.cpp:310 #33 0x01074133 in QCoreApplication::notifyInternal (this=0xbffe21c8, receiver=0x9a30d80, event=0xbffe1e50) at kernel/qcoreapplication.cpp:726 #34 0x0109f1fe in sendEvent (this=0x98f3f84) at kernel/qcoreapplication.h:215 #35 QTimerInfoList::activateTimers (this=0x98f3f84) at kernel/qeventdispatcher_unix.cpp:603 #36 0x0109c745 in timerSourceDispatch (source=0x98f3f50) at kernel/qeventdispatcher_glib.cpp:184 #37 0x00aaa525 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #38 0x00aae268 in ?? () from /lib/libglib-2.0.so.0 #39 0x00aae449 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #40 0x0109c446 in QEventDispatcherGlib::processEvents (this=0x98cea20, flags=...) at kernel/qeventdispatcher_glib.cpp:412 #41 0x04990336 in QGuiEventDispatcherGlib::processEvents (this=0x98cea20, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #42 0x0107280a in QEventLoop::processEvents (this=0xbffe2114, flags=...) at kernel/qeventloop.cpp:149 #43 0x01072b4a in QEventLoop::exec (this=0xbffe2114, flags=...) at kernel/qeventloop.cpp:201 #44 0x01076807 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1003 #45 0x048e1828 in QApplication::exec () at kernel/qapplication.cpp:3585 #46 0x0815c94f in main (argc=) at /usr/src/debug/k3b-2.0.2/src/main.cpp:151 Possible duplicates by query: bug 263711, bug 263492, bug 257944, bug 255680, bug 253841. Reported using DrKonqi
I found that the Bug 246822 seems to be loosely related, but under Fedora 13 and K3b 2.0.2 the crash still happens. It is as if it's a new bug. V.P.L.F.
I think I found what was wrong! I had a pendrive on which there was a udf partition that was seen by Fedora 13 like a cd/dvd drive. The following command, given like normal user, gave me : $ wodim -scanbus scsibus0: 0,0,0 0) 'SONY ' 'DVD RW AW-G170A ' '1.61' Removable CD-ROM 0,1,0 1) * ... 0,7,0 7) * scsibus4: 4,0,0 400) * ... 4,7,0 407) * Without the pendrive I got: $ wodim -scanbus scsibus0: 0,0,0 0) 'SONY ' 'DVD RW AW-G170A ' '1.61' Removable CD-ROM 0,1,0 1) * ... 0,7,0 7) * and K3b started to work properly. For me the problem, as far as now, is solved, but if one of You (developers) want me to do more checks, I'll be happy to help. Is up to You decide if this bug is closed/solved. Bye. V.P.L.F.
Created attachment 77493 [details] New crash information added by DrKonqi k3b (2.0.2) on KDE Platform 4.8.5 (4.8.5) using Qt 4.8.1 - What I was doing when the application crashed: When my Clickfree USB hard drive is connected K3B won't stat and crashes while opening. When the Clickfree USB hard drive is not connected K3B runs normally. This probably has something to do with an extra memory partition in the Clickfree USB drive, the extra partition contain some software for the Microsoft Windows operating system. I am using Linux Mint 13, which sees the extra partition as /dev/sr2 as I already have /dev/sr0 and /dev/sr1 on my system. Below is a copy of my dmesg buffer lines which are generated when I connect the Clickfree drive to my computer. dmesg [ 667.236018] usb 1-2: new high-speed USB device number 7 using ehci_hcd [ 667.304197] hub 1-0:1.0: unable to enumerate USB device on port 2 [ 668.952019] usb 1-2: new high-speed USB device number 8 using ehci_hcd [ 669.090158] scsi6 : usb-storage 1-2:1.0 [ 672.103367] scsi 6:0:0:0: CD-ROM Clikfree Backup Drive 0.11 PQ: 0 ANSI: 0 [ 674.123365] scsi 6:0:0:1: Direct-Access Clikfree Backup Drive 0.11 PQ: 0 ANSI: 6 [ 676.144224] sr2: scsi-1 drive [ 676.145522] sr 6:0:0:0: Attached scsi CD-ROM sr2 [ 676.145769] sr 6:0:0:0: Attached scsi generic sg3 type 5 [ 676.147246] sd 6:0:0:1: Attached scsi generic sg4 type 0 [ 676.264024] usb 1-2: reset high-speed USB device number 8 using ehci_hcd [ 678.417215] sd 6:0:0:1: [sdb] 3906598912 512-byte logical blocks: (2.00 TB/1.81 TiB) [ 678.420482] sd 6:0:0:1: [sdb] Write Protect is off [ 678.420489] sd 6:0:0:1: [sdb] Mode Sense: 27 00 00 00 [ 678.421591] sd 6:0:0:1: [sdb] No Caching mode page present [ 678.421597] sd 6:0:0:1: [sdb] Assuming drive cache: write through [ 678.427097] sd 6:0:0:1: [sdb] No Caching mode page present [ 678.427105] sd 6:0:0:1: [sdb] Assuming drive cache: write through [ 678.435444] sdb: sdb1 [ 678.440509] sd 6:0:0:1: [sdb] No Caching mode page present [ 678.440516] sd 6:0:0:1: [sdb] Assuming drive cache: write through [ 678.440521] sd 6:0:0:1: [sdb] Attached SCSI removable disk -- Backtrace (Reduced): #14 0x00d72998 in K3b::Device::Device::checkWritingModes (this=0x9e00530) at /build/buildd/k3b-2.0.2/libk3bdevice/k3bdevice.cpp:3185 #15 0x00d7dbe8 in K3b::Device::Device::init (this=0x9e00530, bCheckWritingModes=true) at /build/buildd/k3b-2.0.2/libk3bdevice/k3bdevice.cpp:406 #16 0x00d8a4ba in K3b::Device::DeviceManager::addDevice (this=0x9da0178, device=0x9e00530) at /build/buildd/k3b-2.0.2/libk3bdevice/k3bdevicemanager.cpp:372 #17 0x00d8a9be in K3b::Device::DeviceManager::addDevice (this=0x9da0178, solidDevice=...) at /build/buildd/k3b-2.0.2/libk3bdevice/k3bdevicemanager.cpp:360 #18 0x0818cc58 in K3b::AppDeviceManager::addDevice (this=0x9da0178, solidDev=...) at /build/buildd/k3b-2.0.2/src/k3bappdevicemanager.cpp:120
This bug has had its resolution changed, but accidentally has been left in NEEDSINFO status. I am thus closing this bug and setting the status as RESOLVED to reflect the resolution change.