Bug 196856 - crash extracting rar file with ark
Summary: crash extracting rar file with ark
Status: RESOLVED WORKSFORME
Alias: None
Product: ark
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Harald Hvaal
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2009-06-17 09:57 UTC by JamesDHolby
Modified: 2018-10-21 05:06 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description JamesDHolby 2009-06-17 09:57:43 UTC
Application that crashed: ark
Version of the application: 2.13
KDE Version: 4.2.90 (KDE 4.2.90 (KDE 4.3 Beta2))
Qt Version: 4.5.1
Operating System: Linux 2.6.30-9-generic x86_64
Distribution: Ubuntu karmic (development branch)

What I was doing when the application crashed:
Attempting to unarchive a .rar file by double clicking on the file in Dolphin.

 -- Backtrace:
Application: Ark (ark), signal: Segmentation fault
[KCrash Handler]
#5  QThread::wait (this=0x0, time=18446744073709551615) at thread/qthread.h:130
#6  0x00007fd73f819dbc in Kerfuffle::Job::~Job () from /usr/lib/libkerfuffle.so.4
#7  0x00007fd73f81d3b0 in ?? () from /usr/lib/libkerfuffle.so.4
#8  0x00007fd73db696de in ~KCompositeJobPrivate (this=0xf4f920) at /usr/include/qt4/QtCore/qalgorithms.h:350
#9  0x00007fd73db6a2ca in ~KJob (this=0xf4e280) at ../../kdecore/jobs/kjob.cpp:69
#10 0x00007fd73f82669f in Kerfuffle::BatchExtract::~BatchExtract () from /usr/lib/libkerfuffle.so.4
#11 0x00007fd73d78f9bd in QObject::event (this=0xf4e280, e=0xffffffffffffffff) at kernel/qobject.cpp:1101
#12 0x00007fd73e09727c in QApplicationPrivate::notify_helper (this=0xdff7c0, receiver=0xf4e280, e=0xfc0620) at kernel/qapplication.cpp:4057
#13 0x00007fd73e09e54e in QApplication::notify (this=0x7fffa09f32f0, receiver=0xf4e280, e=0xfc0620) at kernel/qapplication.cpp:4022
#14 0x00007fd73ecf4c16 in KApplication::notify (this=0x7fffa09f32f0, receiver=0xf4e280, event=0xfc0620) at ../../kdeui/kernel/kapplication.cpp:302
#15 0x00007fd73d78020c in QCoreApplication::notifyInternal (this=0x7fffa09f32f0, receiver=0xf4e280, event=0xfc0620) at kernel/qcoreapplication.cpp:610
#16 0x00007fd73d780cdc in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=<value optimized out>, data=0xde2c30)
    at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#17 0x00007fd73d780fcc in QCoreApplication::exec () at kernel/qcoreapplication.cpp:895
#18 0x0000000000409afb in _start ()

Reported using DrKonqi
Comment 1 Dario Andres 2009-06-17 14:29:41 UTC
If you can reproduce the crash at will, may you read http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports and post a complete backtrace here? You need to install the "kdeutils-dbg" package. Thanks
Comment 2 Raphael Kubo da Costa 2009-06-17 16:16:42 UTC
Does it always happen to you? Can you attach a file that causes this crash?
Comment 3 Raphael Kubo da Costa 2009-06-25 06:22:48 UTC
Closing as WAITINGFORINFO.
Comment 4 Andrew Crouthamel 2018-09-19 04:40: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 Andrew Crouthamel 2018-10-21 05:06:41 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!