Bug 296425 - ARk crash estracting a .doc from a .zip
Summary: ARk crash estracting a .doc from a .zip
Status: RESOLVED WORKSFORME
Alias: None
Product: ark
Classification: Applications
Component: general (show other bugs)
Version: 2.17
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Raphael Kubo da Costa
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2012-03-20 11:16 UTC by Andres Cañadas
Modified: 2018-10-27 03:44 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andres Cañadas 2012-03-20 11:16:17 UTC
Application: ark (2.17)
KDE Platform Version: 4.7.4 (4.7.4)
Qt Version: 4.7.4
Operating System: Linux 3.0.0-16-generic x86_64
Distribution: Ubuntu 11.10

-- Information about the crash:
- What I was doing when the application crashed:
I was trying to stract a .doc froma a zip file. It was fully downloaded by firefox, it  was not a tmp file.
I hope to usefull. Thanks.

-- Backtrace:
Application: Ark (ark), signal: Aborted
[Current thread is 1 (Thread 0x7ff08e910780 (LWP 3070))]

Thread 2 (Thread 0x7ff07aa66700 (LWP 3074)):
#0  0x00007ff08b8cc473 in __GI___poll (fds=<optimized out>, nfds=<optimized out>, timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007ff088335f68 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007ff088336429 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007ff08c034f3e in QEventDispatcherGlib::processEvents (this=0x2361580, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:424
#4  0x00007ff08c008cf2 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007ff08c008ef7 in QEventLoop::exec (this=0x7ff07aa65dd0, flags=...) at kernel/qeventloop.cpp:201
#6  0x00007ff08bf2027f in QThread::exec (this=<optimized out>) at thread/qthread.cpp:498
#7  0x00007ff08bfebcbf in QInotifyFileSystemWatcherEngine::run (this=0x245adc0) at io/qfilesystemwatcher_inotify.cpp:248
#8  0x00007ff08bf22d05 in QThreadPrivate::start (arg=0x245adc0) at thread/qthread_unix.cpp:331
#9  0x00007ff088807efc in start_thread (arg=0x7ff07aa66700) at pthread_create.c:304
#10 0x00007ff08b8d859d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#11 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7ff08e910780 (LWP 3070)):
[KCrash Handler]
#6  0x00007ff08b82b3a5 in __GI_raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#7  0x00007ff08b82eb0b in __GI_abort () at abort.c:92
#8  0x00007ff08bc51d7d in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#9  0x00007ff08bc4ff26 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#10 0x00007ff08bc4ff53 in std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#11 0x00007ff08bc50096 in __cxa_rethrow () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#12 0x00007ff08c00902e in QEventLoop::exec (this=<optimized out>, flags=<optimized out>) at kernel/qeventloop.cpp:214
#13 0x00007ff08c00d789 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1064
#14 0x000000000040a748 in main (argc=4, argv=0x7fff5750c3b8) at ../../../ark/app/main.cpp:209

This bug may be a duplicate of or related to bug 230639.

Possible duplicates by query: bug 296407, bug 295404, bug 294766, bug 294262, bug 294109.

Reported using DrKonqi
Comment 1 Raphael Kubo da Costa 2012-03-25 04:58:25 UTC
Is this crash reproducible? If so, can you attach a file that causes it?
Comment 2 Raphael Kubo da Costa 2012-04-03 13:34:07 UTC
Closing while waiting for feedback from the reporter.
Comment 3 Andrew Crouthamel 2018-09-23 02:28:11 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 set the bug status 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-27 03:44:26 UTC
Dear Bug Submitter,

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!