Bug 222959 - ark crashed unexpectedly (after closing?)
Summary: ark crashed unexpectedly (after closing?)
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: 2010-01-16 12:03 UTC by T. Columbus
Modified: 2018-10-21 04:21 UTC (History)
2 users (show)

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


Attachments
New crash information added by DrKonqi (3.53 KB, text/plain)
2010-02-25 01:29 UTC, lerdo
Details

Note You need to log in before you can comment on or make changes to this bug.
Description T. Columbus 2010-01-16 12:03:31 UTC
Application that crashed: ark
Version of the application: 2.13
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-17-generic x86_64
Distribution: Ubuntu 9.10

 -- Backtrace:
Application: Ark (ark), signal: Segmentation fault
The current source language is "auto; currently c".
[KCrash Handler]
#5  0x000000000244e150 in ?? ()
#6  0x00007fb6a0b2ca40 in QWidget::hide (this=0x2416720) at /usr/include/qt4/QtGui/qwidget.h:477
#7  JobTracker::resetUi (this=0x2416720) at ../../../ark/part/jobtracker.cpp:92
#8  0x00007fb6a0b15c34 in JobTracker::qt_metacall (this=0x2416720, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff4652a770) at moc_jobtracker.cpp:128
#9  0x00007fb6a93feddc in QMetaObject::activate (sender=0x244e210, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv=0xfffffffffffe8528) at kernel/qobject.cpp:3113
#10 0x00007fb6a9403e1f in QSingleShotTimer::timerEvent (this=0x244e210) at kernel/qtimer.cpp:298
#11 0x00007fb6a93f8d83 in QObject::event (this=0x244e210, e=0x0) at kernel/qobject.cpp:1075
#12 0x00007fb6a9d09efc in QApplicationPrivate::notify_helper (this=0x2105030, receiver=0x244e210, e=0x7fff4652ad80) at kernel/qapplication.cpp:4056
#13 0x00007fb6a9d111ce in QApplication::notify (this=0x7fff4652b0d0, receiver=0x244e210, e=0x7fff4652ad80) at kernel/qapplication.cpp:4021
#14 0x00007fb6aa940ab6 in KApplication::notify (this=0x7fff4652b0d0, receiver=0x244e210, event=0x7fff4652ad80) at ../../kdeui/kernel/kapplication.cpp:302
#15 0x00007fb6a93e9c2c in QCoreApplication::notifyInternal (this=0x7fff4652b0d0, receiver=0x244e210, event=0x7fff4652ad80) at kernel/qcoreapplication.cpp:610
#16 0x00007fb6a9414862 in QCoreApplication::sendEvent (this=0x2108ca0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#17 QTimerInfoList::activateTimers (this=0x2108ca0) at kernel/qeventdispatcher_unix.cpp:572
#18 0x00007fb6a941225d in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:165
#19 0x00007fb6a569cbce in g_main_dispatch (context=0x2107d20) at /build/buildd/glib2.0-2.22.3/glib/gmain.c:1960
#20 IA__g_main_context_dispatch (context=0x2107d20) at /build/buildd/glib2.0-2.22.3/glib/gmain.c:2513
#21 0x00007fb6a56a0598 in g_main_context_iterate (context=0x2107d20, block=<value optimized out>, dispatch=<value optimized out>, self=<value optimized out>)
    at /build/buildd/glib2.0-2.22.3/glib/gmain.c:2591
#22 0x00007fb6a56a06c0 in IA__g_main_context_iteration (context=0x2107d20, may_block=1) at /build/buildd/glib2.0-2.22.3/glib/gmain.c:2654
#23 0x00007fb6a94121a6 in QEventDispatcherGlib::processEvents (this=0x20e9c80, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327
#24 0x00007fb6a9d9e4be in QGuiEventDispatcherGlib::processEvents (this=0x241a020, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#25 0x00007fb6a93e8532 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#26 0x00007fb6a93e8904 in QEventLoop::exec (this=0x7fff4652b020, flags=) at kernel/qeventloop.cpp:201
#27 0x00007fb6a93eaab9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#28 0x0000000000409996 in main (argc=<value optimized out>, argv=<value optimized out>) at ../../../ark/app/main.cpp:209

Reported using DrKonqi
Comment 1 Raphael Kubo da Costa 2010-01-16 18:35:43 UTC
Can you describe more precisely what you were doing? What archive type were you viewing? Were you previewing something? Had you already closed Ark when the crash happened?
Comment 2 T. Columbus 2010-01-16 18:57:56 UTC
I was creating a zip archive of several files. Apart from that I can give no more precise information. Actually I already couldn't remember the exact circumstances when I was creating the bug report ;( ... Sorry
Comment 3 Raphael Kubo da Costa 2010-01-16 19:21:06 UTC
It _could_ be related to bug 222392 and bug 221643, but the backtrace looks a little different.

Since you it isn't possible for you to give more details or reproduce the issue reliably, I'm closing the report. If you ever have this crash again and have more information, please don't hesitate to reopen this report.

Thanks!
Comment 4 lerdo 2010-02-25 01:29:45 UTC
Created attachment 41082 [details]
New crash information added by DrKonqi

I opened a zip file, containing a folder with pictures.
After sucessfully extracting those files I closed the application, which then crashed
Comment 5 Raphael Kubo da Costa 2010-02-25 03:39:48 UTC
Can you reliably reproduce this crash?
Comment 6 lerdo 2010-02-25 04:35:08 UTC
I actually can't reproduce this crash. A few moments ago I extracted a pair of RAR archives split in several parts, none of them caused any trouble at all.

Today I upgraded to 4.4.0 SC from the Fedora Update Repository, just after that I experienced crashes of plasma workspace, KPackagekit, this one with Ark and weird graphics artifacts on windows decorations. None of those crashes happened more than once, in fact only the first time i used the aforementioned applications.
Comment 7 Andrew Crouthamel 2018-09-20 22:04:55 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 8 Andrew Crouthamel 2018-10-21 04:21:14 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!