Bug 184068 - file extraction crash down of tar.gz file 1,6 GB
Summary: file extraction crash down of tar.gz file 1,6 GB
Status: RESOLVED WORKSFORME
Alias: None
Product: ark
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Harald Hvaal
URL:
Keywords: investigated, triaged
Depends on:
Blocks:
 
Reported: 2009-02-11 22:59 UTC by Christian Sutor
Modified: 2018-10-21 04:58 UTC (History)
1 user (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 Christian Sutor 2009-02-11 22:59:45 UTC
Version:           2.10.999 (using KDE 4.1.3)
OS:                Linux
Installed from:    SuSE RPMs

Right-klick on file ..tar.gz in Krusader, ark application opened.
during loading file-content program crashed down with following message:
<<begin error message>>
Anwendung: Ark (ark), Signal SIGSEGV
[?1034h(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0x7f0c4abba950 (LWP 6679)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#5  0x00007f0c4f40bfa2 in ?? () from /usr/lib64/kde4/libarkpart.so
#6  0x00007f0c4f40a664 in ?? () from /usr/lib64/kde4/libarkpart.so
#7  0x00007f0c4f40b3c5 in ?? () from /usr/lib64/kde4/libarkpart.so
#8  0x00007f0c4f40163d in ?? () from /usr/lib64/kde4/libarkpart.so
#9  0x00007f0c58ff1454 in QMetaObject::activate(QObject*, int, int, void**) ()
   from /usr/lib64/libQtCore.so.4
#10 0x00007f0c4f1cc852 in Kerfuffle::ListJob::newEntry(QHash<int, QVariant> const&) () from /usr/lib64/libkerfuffle.so.4
#11 0x00007f0c4f1ccccd in Kerfuffle::ListJob::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libkerfuffle.so.4
#12 0x00007f0c58ff1454 in QMetaObject::activate(QObject*, int, int, void**) ()
   from /usr/lib64/libQtCore.so.4
#13 0x00007f0c4f1cf322 in ?? () from /usr/lib64/libkerfuffle.so.4
#14 0x00007f0c4f1cf687 in ?? () from /usr/lib64/libkerfuffle.so.4
#15 0x00007f0c58fec105 in QObject::event(QEvent*) ()
   from /usr/lib64/libQtCore.so.4
#16 0x00007f0c5433f1bd in QApplicationPrivate::notify_helper(QObject*, QEvent*)
    () from /usr/lib64/libQtGui.so.4
#17 0x00007f0c54346f8a in QApplication::notify(QObject*, QEvent*) ()
   from /usr/lib64/libQtGui.so.4
#18 0x00007f0c5848ebab in KApplication::notify(QObject*, QEvent*) ()
   from /usr/lib64/libkdeui.so.5
#19 0x00007f0c58fdd091 in QCoreApplication::notifyInternal(QObject*, QEvent*)
    () from /usr/lib64/libQtCore.so.4
#20 0x00007f0c58fddd3a in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQtCore.so.4
#21 0x00007f0c59005863 in ?? () from /usr/lib64/libQtCore.so.4
#22 0x00007f0c52c290db in g_main_context_dispatch ()
   from /usr/lib64/libglib-2.0.so.0
#23 0x00007f0c52c2c8ad in ?? () from /usr/lib64/libglib-2.0.so.0
#24 0x00007f0c52c2ca6b in g_main_context_iteration ()
   from /usr/lib64/libglib-2.0.so.0
#25 0x00007f0c590054ef in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#26 0x00007f0c543cf97f in ?? () from /usr/lib64/libQtGui.so.4
#27 0x00007f0c58fdb9a2 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#28 0x00007f0c58fdbb2d in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#29 0x00007f0c58fddffd in QCoreApplication::exec() ()
   from /usr/lib64/libQtCore.so.4
#30 0x0000000000407b8f in _start ()

<<end error message>>

Many thanks for any hint or response
sincerly yours
Christian
Comment 1 Pino Toscano 2009-02-11 23:02:58 UTC
Hi,

unfortunately, the backtrace is not completely helpful.
You can get a better one by following the instructions on:
http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

Thanks!
Comment 2 Raphael Kubo da Costa 2009-04-11 23:57:44 UTC
The reporter didn't provide any additional information as requested. Closing it.
Comment 3 Andrew Crouthamel 2018-09-19 04:34:27 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 4 Andrew Crouthamel 2018-10-21 04:58:15 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!