Bug 249371 - K3b crashed when trying to open from kmenu/application launcher menu
Summary: K3b crashed when trying to open from kmenu/application launcher menu
Status: RESOLVED FIXED
Alias: None
Product: k3b
Classification: Applications
Component: general (show other bugs)
Version: 2.0.1
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Michał Małek
URL:
Keywords:
: 250931 251964 257975 258573 258627 258707 258756 258969 259195 259213 259341 261709 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-08-29 01:51 UTC by N.M
Modified: 2010-12-31 17:23 UTC (History)
14 users (show)

See Also:
Latest Commit:
Version Fixed In: 2.0.2
Sentry Crash Report:


Attachments
New crash information added by DrKonqi (5.43 KB, text/plain)
2010-11-27 17:05 UTC, Jaime Torres
Details
New crash information added by DrKonqi (7.75 KB, text/plain)
2010-12-26 08:16 UTC, Alexander O. Anisimov
Details

Note You need to log in before you can comment on or make changes to this bug.
Description N.M 2010-08-29 01:51:38 UTC
Application: k3b (2.0.1)
KDE Platform Version: 4.5.66 (KDE 4.5.66 (KDE 4.6 >= 20100825)) "release 5"
Qt Version: 4.6.3
Operating System: Linux 2.6.34-12-default x86_64
Distribution: "openSUSE 11.3 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed: Just attempting to start the application from the start menu/application launcher menu always reproduces this error.

The crash can be reproduced every time.

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

Thread 2 (Thread 0x7f1e50afd710 (LWP 20793)):
#0  0x00007f1e630576b3 in poll () from /lib64/libc.so.6
#1  0x00007f1e5cb4efd4 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x00007f1e5cb4f510 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#3  0x00007f1e643f16d6 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#4  0x00007f1e643c8292 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#5  0x00007f1e643c8495 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#6  0x00007f1e642df2cf in QThread::exec() () from /usr/lib64/libQtCore.so.4
#7  0x00007f1e643aa458 in ?? () from /usr/lib64/libQtCore.so.4
#8  0x00007f1e642e1bf5 in ?? () from /usr/lib64/libQtCore.so.4
#9  0x00007f1e62b03a4f in start_thread () from /lib64/libpthread.so.0
#10 0x00007f1e6306082d in clone () from /lib64/libc.so.6
#11 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f1e688c6780 (LWP 20792)):
[KCrash Handler]
#6  Solid::Block::device (this=0x0) at /usr/src/debug/kdelibs-4.5.66svn1167746/solid/solid/block.cpp:51
#7  0x00007f1e684db72d in K3b::Device::DeviceManager::addDevice (this=0xa54a30, solidDevice=...) at /usr/src/debug/k3b-2.0.1/libk3bdevice/k3bdevicemanager.cpp:357
#8  0x0000000000539e7d in K3b::AppDeviceManager::addDevice (this=0xa54a30, solidDev=<value optimized out>) at /usr/src/debug/k3b-2.0.1/src/k3bappdevicemanager.cpp:119
#9  0x00007f1e684da5f1 in K3b::Device::DeviceManager::checkDevice (this=0xa54a30, dev=<value optimized out>) at /usr/src/debug/k3b-2.0.1/libk3bdevice/k3bdevicemanager.cpp:249
#10 0x00007f1e684dc98b in K3b::Device::DeviceManager::scanBus (this=0xa54a30) at /usr/src/debug/k3b-2.0.1/libk3bdevice/k3bdevicemanager.cpp:237
#11 0x00007f1e68167ed8 in K3b::Core::init (this=0x96b110) at /usr/src/debug/k3b-2.0.1/libk3b/core/k3bcore.cpp:200
#12 0x00000000004f93da in K3b::Application::Core::init (this=0x96b110) at /usr/src/debug/k3b-2.0.1/src/k3bapplication.cpp:318
#13 0x00000000004fa4bf in K3b::Application::init (this=0x7fff69debb10) at /usr/src/debug/k3b-2.0.1/src/k3bapplication.cpp:117
#14 0x00000000004faa7c in K3b::Application::qt_metacall (this=0x7fff69debb10, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff69deaf20)
    at /usr/src/debug/k3b-2.0.1/build/src/k3bapplication.moc:80
#15 0x00007f1e643dca1f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/libQtCore.so.4
#16 0x00007f1e643e1dbf in ?? () from /usr/lib64/libQtCore.so.4
#17 0x00007f1e643da22e in QObject::event(QEvent*) () from /usr/lib64/libQtCore.so.4
#18 0x00007f1e637ba4d4 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#19 0x00007f1e637c2aca in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#20 0x00007f1e64db52f6 in KApplication::notify (this=0x7fff69debb10, receiver=0x94ad20, event=0x7fff69deb6d0) at /usr/src/debug/kdelibs-4.5.66svn1167746/kdeui/kernel/kapplication.cpp:310
#21 0x00007f1e643c8e4c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4
#22 0x00007f1e643f40c9 in ?? () from /usr/lib64/libQtCore.so.4
#23 0x00007f1e643f0fd4 in ?? () from /usr/lib64/libQtCore.so.4
#24 0x00007f1e5cb4ea93 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#25 0x00007f1e5cb4f270 in ?? () from /usr/lib64/libglib-2.0.so.0
#26 0x00007f1e5cb4f510 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#27 0x00007f1e643f167f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#28 0x00007f1e6385b14e in ?? () from /usr/lib64/libQtGui.so.4
#29 0x00007f1e643c8292 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#30 0x00007f1e643c8495 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#31 0x00007f1e643cc88b in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4
#32 0x0000000000512f72 in main (argc=1, argv=0x7fff69dec6f8) at /usr/src/debug/k3b-2.0.1/src/main.cpp:151

Reported using DrKonqi
Comment 1 Michał Małek 2010-09-09 20:54:08 UTC
SVN commit 1173575 by mmalek:

Don't assume optical Solid device has also Solid::Block interface. For some reason it can lack it (hardware issue or Solid bug)
BUG: 249371

 M  +1 -0      ChangeLog  
 M  +10 -6     libk3bdevice/k3bdevicemanager.cpp  
 M  +4 -1      src/k3bappdevicemanager.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=1173575
Comment 2 Michał Małek 2010-09-09 20:54:13 UTC
SVN commit 1173576 by mmalek:

Don't assume optical Solid device has also Solid::Block interface. For some reason it can lack it (hardware issue or Solid bug)
BUG: 249371


 M  +1 -0      ChangeLog  
 M  +10 -6     libk3bdevice/k3bdevicemanager.cpp  
 M  +4 -1      src/k3bappdevicemanager.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=1173576
Comment 3 Pino Toscano 2010-09-12 09:25:08 UTC
*** Bug 250931 has been marked as a duplicate of this bug. ***
Comment 4 Nicolas L. 2010-11-26 16:52:08 UTC
*** Bug 257975 has been marked as a duplicate of this bug. ***
Comment 5 Jaime Torres 2010-11-27 17:05:31 UTC
Created attachment 53799 [details]
New crash information added by DrKonqi

k3b (2.0.1) on KDE Platform 4.5.81 (4.6 >=20101125) "release 1" using Qt 4.7.2

- What I was doing when the application crashed:

Launching k3b without any dvd inserted.
Trying to reproduce bug 257349

The problem is still there with kde 4.6 beta 1.

-- Backtrace (Reduced):
#6  Solid::Block::device (this=0x0) at /usr/src/debug/kdelibs-4.5.81svn1200771/solid/solid/block.cpp:52
#7  0x00007f07bba953ed in K3b::Device::DeviceManager::addDevice (this=0x2a1ced0, solidDevice=<value optimized out>) at /usr/src/debug/k3b-2.0.1/libk3bdevice/k3bdevicemanager.cpp:357
#8  0x000000000053f70d in K3b::AppDeviceManager::addDevice (this=0x2a1ced0, solidDev=<value optimized out>) at /usr/src/debug/k3b-2.0.1/src/k3bappdevicemanager.cpp:119
#9  0x00007f07bba94a61 in K3b::Device::DeviceManager::checkDevice (this=0x2a1ced0, dev=...) at /usr/src/debug/k3b-2.0.1/libk3bdevice/k3bdevicemanager.cpp:249
#10 0x00007f07bba96e0b in K3b::Device::DeviceManager::scanBus (this=0x2a1ced0) at /usr/src/debug/k3b-2.0.1/libk3bdevice/k3bdevicemanager.cpp:237
Comment 6 Jaime Torres 2010-11-27 17:16:25 UTC
Sorry, it is fixed, but opensuse still pushes 2.0.1.
Comment 7 Christoph Feck 2010-12-02 22:12:20 UTC
*** Bug 258573 has been marked as a duplicate of this bug. ***
Comment 8 Christoph Feck 2010-12-03 00:59:10 UTC
*** Bug 258627 has been marked as a duplicate of this bug. ***
Comment 9 Ralph Moenchmeyer 2010-12-03 14:42:59 UTC
I am using Opensuse 11.3 (x86_64), KDE 4.6 beta (from Opensuse's Factory Repository), Qt 4.7.1 and with the latest RPM 2.0.1-44.1 for K3b in the Factory Repo K3b obviously to work again. 

No crash when starting from KDE's menu or Opensuse's menu. Neither any crash when opening the settings dialog (which was also a bug reported for KDE 4.5 and Qt 4.7).
Comment 10 Christoph Feck 2010-12-03 21:41:48 UTC
*** Bug 258707 has been marked as a duplicate of this bug. ***
Comment 11 Christoph Feck 2010-12-04 03:51:33 UTC
*** Bug 258756 has been marked as a duplicate of this bug. ***
Comment 12 Pino Toscano 2010-12-06 10:08:49 UTC
*** Bug 258969 has been marked as a duplicate of this bug. ***
Comment 13 Pino Toscano 2010-12-08 15:04:25 UTC
*** Bug 259195 has been marked as a duplicate of this bug. ***
Comment 14 Pino Toscano 2010-12-08 15:08:22 UTC
*** Bug 259213 has been marked as a duplicate of this bug. ***
Comment 15 Pino Toscano 2010-12-09 16:45:01 UTC
*** Bug 259341 has been marked as a duplicate of this bug. ***
Comment 16 Michał Małek 2010-12-21 23:44:39 UTC
*** Bug 251964 has been marked as a duplicate of this bug. ***
Comment 17 Alexander O. Anisimov 2010-12-26 08:16:20 UTC
Created attachment 55252 [details]
New crash information added by DrKonqi

k3b (2.0.1) on KDE Platform 4.5.80 (4.6 Beta1) using Qt 4.7.0

- What I was doing when the application crashed:
I just start k3b from gnome menu, but it crashed.

-- Backtrace (Reduced):
#7  0x04166239 in Solid::Block::device() const () from /usr/lib/libsolid.so.4
#8  0x020fa1c1 in K3b::Device::DeviceManager::addDevice (this=0x8cbbda0, solidDevice=...) at /build/buildd/k3b-2.0.1/libk3bdevice/k3bdevicemanager.cpp:357
#9  0x081a9a29 in K3b::AppDeviceManager::addDevice (this=0x8cbbda0, solidDev=...) at /build/buildd/k3b-2.0.1/src/k3bappdevicemanager.cpp:119
#10 0x020f7eaa in K3b::Device::DeviceManager::checkDevice (this=0x8cbbda0, dev=...) at /build/buildd/k3b-2.0.1/libk3bdevice/k3bdevicemanager.cpp:249
#11 0x020f82b6 in K3b::Device::DeviceManager::scanBus (this=0x8cbbda0) at /build/buildd/k3b-2.0.1/libk3bdevice/k3bdevicemanager.cpp:237
Comment 18 Pino Toscano 2010-12-31 17:23:15 UTC
*** Bug 261709 has been marked as a duplicate of this bug. ***