Bug 343746

Summary: k3b crash at start
Product: [Applications] k3b Reporter: sefradre
Component: generalAssignee: k3b developers <k3b>
Status: RESOLVED WORKSFORME    
Severity: crash CC: aacid, michalm, trueg
Priority: NOR Keywords: drkonqi
Version First Reported In: 2.0.80   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description sefradre 2015-02-03 20:48:17 UTC 
Application: k3b (2.0.80)
KDE Platform Version: 4.14.3
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:
I'm just starting k3b. The splash screen comes and some moments later k3b crashs

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

Thread 2 (Thread 0x7f5319c56700 (LWP 4353)):
#0  0x00007f53320583cd in poll () at /lib64/libc.so.6
#1  0x00007f532c60cbe4 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x00007f532c60ccec in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#3  0x00007f53337190de in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4
#4  0x00007f53336eae6f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4
#5  0x00007f53336eb165 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQtCore.so.4
#6  0x00007f53335e80bf in QThread::exec() () at /usr/lib64/libQtCore.so.4
#7  0x00007f53336cc783 in  () at /usr/lib64/libQtCore.so.4
#8  0x00007f53335ea79f in  () at /usr/lib64/libQtCore.so.4
#9  0x00007f5331d660a4 in start_thread () at /lib64/libpthread.so.0
#10 0x00007f53320607fd in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7f53387ec940 (LWP 4352)):
[KCrash Handler]
#5  0x00007f533845f050 in K3b::Device::from2Byte(unsigned char const*) () at /usr/lib64/libk3bdevice.so.6
#6  0x00007f53384513d8 in K3b::Device::Device::getSupportedWriteSpeedsVia2A(QList<int>&, K3b::Device::MediaType) const () at /usr/lib64/libk3bdevice.so.6
#7  0x00007f5338451e5b in K3b::Device::Device::determineSupportedWriteSpeeds() const () at /usr/lib64/libk3bdevice.so.6
#8  0x00007f5338451f90 in K3b::Device::Device::determineMaximalWriteSpeed() const () at /usr/lib64/libk3bdevice.so.6
#9  0x00007f53384530b9 in K3b::Device::Device::init(bool) () at /usr/lib64/libk3bdevice.so.6
#10 0x00007f533845ad90 in K3b::Device::DeviceManager::addDevice(K3b::Device::Device*) () at /usr/lib64/libk3bdevice.so.6
#11 0x00007f533845b173 in K3b::Device::DeviceManager::addDevice(Solid::Device const&) () at /usr/lib64/libk3bdevice.so.6
#12 0x000000000054de3d in _start ()

Possible duplicates by query: bug 336782.

Reported using DrKonqi
Comment 1 Albert Astals Cid 2015-02-03 21:03:30 UTC 
Are you running  suse packages? Any idea why they are shipping 2.0.80, that is, an unstable version? 

Also can you run
valgrind k3b
and attach the output?
Comment 2 sefradre 2015-02-04 18:35:13 UTC 
I'm running this version, as I want to rip CDs to mp3 and it's the
actual version on packman. After the problems I've switched to the
official suse version and everything works. But I can only rip to ogg
vorbis.

Regards
Sebastian

Am 03.02.2015 um 22:03 schrieb Albert Astals Cid:
> https://bugs.kde.org/show_bug.cgi?id=343746
>
> Albert Astals Cid <aacid@kde.org> changed:
>
>             What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                   CC|                            |aacid@kde.org
>
> --- Comment #1 from Albert Astals Cid <aacid@kde.org> ---
> Are you running  suse packages? Any idea why they are shipping 2.0.80, that is,
> an unstable version?
>
> Also can you run
> valgrind k3b
> and attach the output?
>
Comment 3 Andrew Crouthamel 2018-10-31 04:04:18 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:51:07 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 04:03:47 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!