Bug 317645 - K3B was closed unexpectedly before it start
Summary: K3B was closed unexpectedly before it start
Status: RESOLVED WORKSFORME
Alias: None
Product: k3b
Classification: Applications
Component: general (show other bugs)
Version: 2.0.2
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: k3b developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-03-31 17:23 UTC by Luis Vidrio
Modified: 2018-11-30 03:52 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
jpwhiting: gardening-


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Luis Vidrio 2013-03-31 17:23:20 UTC
Application: k3b (2.0.2)
KDE Platform Version: 4.8.5 (4.8.5) (Compiled from sources)
Qt Version: 4.8.4
Operating System: Linux 3.4.34-desktop-1.mga2 i686
Distribution: "Mageia 2"

-- Information about the crash:
- What I was doing when the application crashed:I was trying to open the K3B program, but I could not because it was closed unexpectedly.

- Unusual behavior I noticed: This never has happened to me before.

- Custom settings of the application: None of them

The crash can be reproduced every time.

-- Backtrace:
Application: K3b (k3b), signal: Aborted
Using host libthread_db library "/lib/i686/libthread_db.so.1".
[Current thread is 1 (Thread 0xb1dfa6f0 (LWP 3672))]

Thread 2 (Thread 0xb0974b70 (LWP 3673)):
#0  0xb3e3dd70 in __libc_disable_asynccancel () from /lib/i686/libc.so.6
#1  0xb3e1f1f4 in read () from /lib/i686/libc.so.6
#2  0xb2f7974e in ?? () from /lib/libglib-2.0.so.0
#3  0xb2f3aa52 in g_main_context_check () from /lib/libglib-2.0.so.0
#4  0xb2f3aec2 in ?? () from /lib/libglib-2.0.so.0
#5  0xb2f3b081 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#6  0xb4c596b7 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#7  0xb4c2547d in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#8  0xb4c25719 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#9  0xb4b0d81c in QThread::exec() () from /usr/lib/libQtCore.so.4
#10 0xb4c0274d in ?? () from /usr/lib/libQtCore.so.4
#11 0xb4b10d48 in ?? () from /usr/lib/libQtCore.so.4
#12 0xb3cc5a37 in start_thread () from /lib/i686/libpthread.so.0
#13 0xb3e2f98e in clone () from /lib/i686/libc.so.6
Backtrace stopped: Not enough registers or memory available to unwind further

Thread 1 (Thread 0xb1dfa6f0 (LWP 3672)):
[KCrash Handler]
#7  0xffffe424 in __kernel_vsyscall ()
#8  0xb3d87a7f in raise () from /lib/i686/libc.so.6
#9  0xb3d894a5 in abort () from /lib/i686/libc.so.6
#10 0xb3dc133a in __libc_message () from /lib/i686/libc.so.6
#11 0xb3dc7be2 in malloc_printerr () from /lib/i686/libc.so.6
#12 0xb3f9fc7f in operator delete(void*) () from /usr/lib/libstdc++.so.6
#13 0xb3f9fcdb in operator delete[](void*) () from /usr/lib/libstdc++.so.6
#14 0xb7719e98 in K3b::Device::Device::checkWritingModes() () from /usr/lib/libk3bdevice.so.6
#15 0xb7725118 in K3b::Device::Device::init(bool) () from /usr/lib/libk3bdevice.so.6
#16 0xb7731c6a in K3b::Device::DeviceManager::addDevice(K3b::Device::Device*) () from /usr/lib/libk3bdevice.so.6
#17 0xb773216e in K3b::Device::DeviceManager::addDevice(Solid::Device const&) () from /usr/lib/libk3bdevice.so.6
#18 0x0818e2c8 in _start ()

Possible duplicates by query: bug 265211, bug 255680, bug 254011, bug 247306, bug 246822.

Reported using DrKonqi
Comment 1 Jekyll Wu 2013-04-01 01:59:36 UTC
>  #14 0xb7719e98 in K3b::Device::Device::checkWritingModes() () from /usr/lib/libk3bdevice.so.6

Could you install debug symbols for k3b and provide a better backtrace ?
Comment 2 Christoph Feck 2013-04-14 20:23:14 UTC
Did you try to start k3b with some USB stick attached? If yes, this is probably a duplicate of bug 265211 (see bug 265211 comment #2).
Comment 3 Andrew Crouthamel 2018-10-31 03:53:50 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Bug Janitor Service 2018-11-15 10:40:12 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Bug Janitor Service 2018-11-30 03:52:58 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!