Bug 341094 - Crash when unpacking rar archive
Summary: Crash when unpacking rar archive
Status: RESOLVED DUPLICATE of bug 340991
Alias: None
Product: ark
Classification: Applications
Component: general (show other bugs)
Version: 2.19
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Raphael Kubo da Costa
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2014-11-19 11:52 UTC by Viktor Matveenko
Modified: 2014-11-19 13:49 UTC (History)
0 users

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 Viktor Matveenko 2014-11-19 11:52:54 UTC
Application: ark (2.19)
KDE Platform Version: 4.14.3
Qt Version: 4.8.6
Operating System: Linux 3.17.2-200.fc20.x86_64 x86_64
Distribution: "Fedora release 20 (Heisenbug)"

-- Information about the crash:
- What I was doing when the application crashed:
I tried to open rar archive. Opened ark and an error of impossibility to open rar archive. Closes the error. There crash ark.

The crash can be reproduced every time.

-- Backtrace:
Application: Ark (ark), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[KCrash Handler]
#6  KXMLGUIFactory::removeClient (this=0x0, client=0xf9cdb8) at /usr/src/debug/kdelibs-4.14.3/kdeui/xmlgui/kxmlguifactory.cpp:419
#7  0x00007fcae38a71d4 in Ark::Part::~Part() () from /usr/lib64/kde4/arkpart.so
#8  0x00007fcae38a7269 in Ark::Part::~Part() () from /usr/lib64/kde4/arkpart.so
#9  0x000000373959dd48 in QObjectPrivate::deleteChildren() () from /lib64/libQtCore.so.4
#10 0x0000003739c19fc7 in QWidget::~QWidget() () from /lib64/libQtGui.so.4
#11 0x000000000040e1ad in MainWindow::~MainWindow() ()
#12 0x000000000040e239 in MainWindow::~MainWindow() ()
#13 0x000000373959f938 in QObject::event(QEvent*) () from /lib64/libQtCore.so.4
#14 0x0000003739c1dd43 in QWidget::event(QEvent*) () from /lib64/libQtGui.so.4
#15 0x0000003739fee423 in QMainWindow::event(QEvent*) () from /lib64/libQtGui.so.4
#16 0x0000003741108d21 in KMainWindow::event (this=<optimized out>, ev=<optimized out>) at /usr/src/debug/kdelibs-4.14.3/kdeui/widgets/kmainwindow.cpp:1084
#17 0x0000003741144369 in KXmlGuiWindow::event (this=0xe24fd0, ev=0x10b6330) at /usr/src/debug/kdelibs-4.14.3/kdeui/xmlgui/kxmlguiwindow.cpp:126
#18 0x0000003739bcae5c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQtGui.so.4
#19 0x0000003739bd17b5 in QApplication::notify(QObject*, QEvent*) () from /lib64/libQtGui.so.4
#20 0x000000374104a4fa in KApplication::notify (this=0x7fff20314d60, receiver=0xe24fd0, event=0x10b6330) at /usr/src/debug/kdelibs-4.14.3/kdeui/kernel/kapplication.cpp:311
#21 0x00000037395868fd in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /lib64/libQtCore.so.4
#22 0x0000003739589ae5 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQtCore.so.4
#23 0x00000037395b5c9e in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQtCore.so.4
#24 0x00000037330492a6 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0
#25 0x0000003733049628 in g_main_context_iterate.isra () from /lib64/libglib-2.0.so.0
#26 0x00000037330496dc in g_main_context_iteration () from /lib64/libglib-2.0.so.0
#27 0x00000037395b541e in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQtCore.so.4
#28 0x0000003739c6cc46 in QGuiEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQtGui.so.4
#29 0x000000373958538f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQtCore.so.4
#30 0x00000037395856dd in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib64/libQtCore.so.4
#31 0x000000373958ada9 in QCoreApplication::exec() () from /lib64/libQtCore.so.4
#32 0x000000000040a84c in main ()

Possible duplicates by query: bug 340991.

Reported using DrKonqi
Comment 1 Raphael Kubo da Costa 2014-11-19 13:49:25 UTC
This was a bug in the Fedora package that should have been fixed yesterday. Please make sure your system is up to date.

*** This bug has been marked as a duplicate of bug 340991 ***