Bug 345790 - k3b crashes immediately upon launch
Summary: k3b crashes immediately upon launch
Status: RESOLVED NOT A BUG
Alias: None
Product: k3b
Classification: Applications
Component: general (show other bugs)
Version: 2.0.80
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: k3b developers
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2015-04-02 06:12 UTC by Richard Engkraf
Modified: 2015-04-03 17:13 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
attachment-24007-0.html (2.69 KB, text/html)
2015-04-03 16:34 UTC, Richard Engkraf
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Richard Engkraf 2015-04-02 06:12:11 UTC
Application: k3b (2.0.80)
KDE Platform Version: 4.14.6
Qt Version: 4.8.6
Operating System: Linux 3.16.7-7-desktop x86_64
Distribution: "openSUSE 13.2 (Harlequin) (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed: Crashes immediately upon launch, and with every subsequent try. I removed, then re-installed it from official sources, and the same repeated. I had used it successfully within the past two days.

The crash can be reproduced every time.

-- Backtrace:
Application: K3b (k3b), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f7da7163900 (LWP 2503))]

Thread 2 (Thread 0x7f7d8a504700 (LWP 2504)):
#0  0x00007f7da09cec3d in poll () from /lib64/libc.so.6
#1  0x00007f7d9af83be4 in ?? () from /usr/lib64/libglib-2.0.so.0
#2  0x00007f7d9af83cec in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#3  0x00007f7da208f0de in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#4  0x00007f7da2060e6f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#5  0x00007f7da2061165 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#6  0x00007f7da1f5e0bf in QThread::exec() () from /usr/lib64/libQtCore.so.4
#7  0x00007f7da2042783 in ?? () from /usr/lib64/libQtCore.so.4
#8  0x00007f7da1f6079f in ?? () from /usr/lib64/libQtCore.so.4
#9  0x00007f7da06dd0a4 in start_thread () from /lib64/libpthread.so.0
#10 0x00007f7da09d706d in clone () from /lib64/libc.so.6

Thread 1 (Thread 0x7f7da7163900 (LWP 2503)):
[KCrash Handler]
#5  K3b::Device::from2Byte (d=d@entry=0x7fff21318002 <error: Cannot access memory at address 0x7fff21318002>) at /usr/src/debug/k3b/libk3bdevice/k3bdeviceglobals.cpp:218
#6  0x00007f7da6dc73d8 in K3b::Device::Device::getSupportedWriteSpeedsVia2A (this=this@entry=0x24309f0, list=..., mediaType=mediaType@entry=K3b::Device::MEDIA_UNKNOWN) at /usr/src/debug/k3b/libk3bdevice/k3bdevice.cpp:3254
#7  0x00007f7da6dc7e5b in K3b::Device::Device::determineSupportedWriteSpeeds (this=this@entry=0x24309f0) at /usr/src/debug/k3b/libk3bdevice/k3bdevice.cpp:3213
#8  0x00007f7da6dc7f90 in K3b::Device::Device::determineMaximalWriteSpeed (this=this@entry=0x24309f0) at /usr/src/debug/k3b/libk3bdevice/k3bdevice.cpp:3164
#9  0x00007f7da6dc90b9 in K3b::Device::Device::init (this=0x24309f0, bCheckWritingModes=bCheckWritingModes@entry=true) at /usr/src/debug/k3b/libk3bdevice/k3bdevice.cpp:427
#10 0x00007f7da6dd0d90 in K3b::Device::DeviceManager::addDevice (this=this@entry=0x21afcc0, device=device@entry=0x24309f0) at /usr/src/debug/k3b/libk3bdevice/k3bdevicemanager.cpp:379
#11 0x00007f7da6dd1173 in K3b::Device::DeviceManager::addDevice (this=this@entry=0x21afcc0, solidDevice=...) at /usr/src/debug/k3b/libk3bdevice/k3bdevicemanager.cpp:367
#12 0x000000000054dffd in K3b::AppDeviceManager::addDevice (this=0x21afcc0, solidDev=...) at /usr/src/debug/k3b/src/k3bappdevicemanager.cpp:120
#13 0x00007f7da6dd0089 in K3b::Device::DeviceManager::checkDevice (this=this@entry=0x21afcc0, dev=...) at /usr/src/debug/k3b/libk3bdevice/k3bdevicemanager.cpp:253
#14 0x00007f7da6dd02a2 in K3b::Device::DeviceManager::scanBus (this=0x21afcc0) at /usr/src/debug/k3b/libk3bdevice/k3bdevicemanager.cpp:241
#15 0x00007f7da6a68387 in K3b::Core::init (this=this@entry=0x207abf0) at /usr/src/debug/k3b/libk3b/core/k3bcore.cpp:208
#16 0x000000000050f131 in K3b::Application::Core::init (this=0x207abf0) at /usr/src/debug/k3b/src/k3bapplication.cpp:273
#17 0x000000000050db06 in K3b::Application::Core::qt_static_metacall (_o=<optimized out>, _id=<optimized out>, _a=<optimized out>, _c=<optimized out>) at /usr/src/debug/k3b/build/src/k3bapplication.moc:141
#18 0x00007f7da207a59e in QObject::event(QEvent*) () from /usr/lib64/libQtCore.so.4
#19 0x00007f7da117e76c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#20 0x00007f7da1184cad in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#21 0x00007f7da6368cea in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
#22 0x00007f7da20622ad in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4
#23 0x00007f7da206557d in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQtCore.so.4
#24 0x00007f7da208f8fe in ?? () from /usr/lib64/libQtCore.so.4
#25 0x00007f7d9af83a04 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#26 0x00007f7d9af83c48 in ?? () from /usr/lib64/libglib-2.0.so.0
#27 0x00007f7d9af83cec in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#28 0x00007f7da208f0be in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#29 0x00007f7da121b676 in ?? () from /usr/lib64/libQtGui.so.4
#30 0x00007f7da2060e6f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#31 0x00007f7da2061165 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#32 0x00007f7da20665b9 in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4
#33 0x0000000000449d6f in main (argc=<optimized out>, argv=<optimized out>) at /usr/src/debug/k3b/src/main.cpp:146

The reporter indicates this bug may be a duplicate of or related to bug 343746.

Possible duplicates by query: bug 343746, bug 336782.

Reported using DrKonqi
Comment 1 Albert Astals Cid 2015-04-03 12:26:26 UTC
Why are you using an unstable version? Maybe you want to use a non unsatble one?
Comment 2 Richard Engkraf 2015-04-03 16:34:30 UTC
Created attachment 91870 [details]
attachment-24007-0.html

I tried 2 different versions. I  have solved the problem by switching to
Chakra Linux. I am new to the GNU game, and was unable to get Chakra to
install on my first attempt ( or the 2nd, 3rd, etc.). The version of k3b
that blew up was, to the best of my knowledge, the same one that I had been
using previously. Chakra was my preferred distro, so I kept with it until I
learned enough to be able to make it install. Not the easiest thing I have
ever done, by the way. The KDE/Plasma desktop worked very well in openSUSE,
but as far as I could tell, the apps were unstable. I only ran openSUSE for
about a week, but I had several little nagging problems that were just
that, and did not lead to a productive learning experience like the rest of
what I have so far tried. I am coming to GNU/Linux from the Mac world (I
gave up windows years ago), and I am impressed with what I have found here.
I went from just wanting some non-Windows way to run my largely abandoned
desktop, to now realizing that GNU/Linnux distributions are as much better
that OS X as OS X is superior to Windows. Thank you for responding, but k3b
works on Chakra, so I no longer need any help (at least on that front), and
I suspect that I will not be able to help you in any way. I am sure that
this was in some way caused by something that I did, but it is no longer an
issue. Once again, thanks!

On Fri, Apr 3, 2015 at 5:26 AM, Albert Astals Cid <aacid@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=345790
>
> Albert Astals Cid <aacid@kde.org> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>              Status|UNCONFIRMED                 |NEEDSINFO
>          Resolution|---                         |WAITINGFORINFO
>                  CC|                            |aacid@kde.org
>
> --- Comment #1 from Albert Astals Cid <aacid@kde.org> ---
> Why are you using an unstable version? Maybe you want to use a non unsatble
> one?
>
> --
> You are receiving this mail because:
> You reported the bug.
>
Comment 3 Albert Astals Cid 2015-04-03 17:13:24 UTC
Crash is on 2.0.80 an unrelesed version and reported can't help anymore