Bug 387728

Summary:	Ark segfault when extracting zip
Product:	[Applications] ark	Reporter:	perikrone
Component:	general	Assignee:	Elvis Angelaccio <elvis.angelaccio>
Status:	RESOLVED NOT A BUG
Severity:	crash	CC:	rthomsen6
Priority:	NOR	Keywords:	drkonqi
Version First Reported In:	16.08.2
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description perikrone 2017-12-09 08:17:50 UTC

Application: ark (16.08.2)

Qt Version: 5.6.1
Frameworks Version: 5.26.0
Operating System: Linux 4.4.92-18.36-default x86_64
Distribution: "openSUSE Leap 42.2"

-- Information about the crash:
- What I was doing when the application crashed: trying to extract archive android-studio-ide-171.4443003-linux.zip from Android studio official site (https://developer.android.com/studio/install.html)
Tried to restrart ark several times.

The crash can be reproduced every time.

-- Backtrace:
Application: Ark (ark), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7fd160e0e880 (LWP 4088))]

Thread 3 (Thread 0x7fd145bab700 (LWP 4090)):
#0  0x00007fd15d01120d in poll () at /lib64/libc.so.6
#1  0x00007fd158cf1314 in  () at /usr/lib64/libglib-2.0.so.0
#2  0x00007fd158cf142c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#3  0x00007fd15d91e33b in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#4  0x00007fd15d8cbfeb in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#5  0x00007fd15d706f1a in QThread::exec() () at /usr/lib64/libQt5Core.so.5
#6  0x00007fd15ad66295 in  () at /usr/lib64/libQt5DBus.so.5
#7  0x00007fd15d70b9e9 in  () at /usr/lib64/libQt5Core.so.5
#8  0x00007fd159425744 in start_thread () at /lib64/libpthread.so.0
#9  0x00007fd15d019aad in clone () at /lib64/libc.so.6

Thread 2 (Thread 0x7fd14deee700 (LWP 4089)):
#0  0x00007fd15d01120d in poll () at /lib64/libc.so.6
#1  0x00007fd15658f3e2 in  () at /usr/lib64/libxcb.so.1
#2  0x00007fd156590fcf in xcb_wait_for_event () at /usr/lib64/libxcb.so.1
#3  0x00007fd150448839 in  () at /usr/lib64/libQt5XcbQpa.so.5
#4  0x00007fd15d70b9e9 in  () at /usr/lib64/libQt5Core.so.5
#5  0x00007fd159425744 in start_thread () at /lib64/libpthread.so.0
#6  0x00007fd15d019aad in clone () at /lib64/libc.so.6

Thread 1 (Thread 0x7fd160e0e880 (LWP 4088)):
[KCrash Handler]
#6  0x00000000004113d0 in  ()
#7  0x00007fd15d904eb6 in  () at /usr/lib64/libQt5Core.so.5
#8  0x00007fd15d8f8f44 in QObject::event(QEvent*) () at /usr/lib64/libQt5Core.so.5
#9  0x00007fd15e5d4e3c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5
#10 0x00007fd15e5d949a in QApplication::notify(QObject*, QEvent*) () at /usr/lib64/libQt5Widgets.so.5
#11 0x00007fd15d8cdfd5 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5
#12 0x00007fd15d91dc8e in QTimerInfoList::activateTimers() () at /usr/lib64/libQt5Core.so.5
#13 0x00007fd15d91e051 in  () at /usr/lib64/libQt5Core.so.5
#14 0x00007fd158cf1134 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0
#15 0x00007fd158cf1388 in  () at /usr/lib64/libglib-2.0.so.0
#16 0x00007fd158cf142c in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0
#17 0x00007fd15d91e31c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#18 0x00007fd15d8cbfeb in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib64/libQt5Core.so.5
#19 0x00007fd15d8d3ed6 in QCoreApplication::exec() () at /usr/lib64/libQt5Core.so.5
#20 0x000000000040d368 in  ()
#21 0x00007fd15cf506e5 in __libc_start_main () at /lib64/libc.so.6
#22 0x000000000040e0e9 in _start ()

Reported using DrKonqi

Comment 1 Elvis Angelaccio 2017-12-09 10:34:25 UTC

Does not crash here. Which zip plugin are you using? (You can check it in Settings -> Configure Ark -> Plugin Settings)

Comment 2 Christoph Feck 2017-12-31 08:28:47 UTC

If you can provide the information requested in comment #1, please add it.

Comment 3 Christoph Feck 2018-01-17 16:00:00 UTC

To further investigate this issue, KDE developers need the information requested in comment #1. If you can provide it, or need help with finding that information, please add a comment.

Comment 4 Christoph Feck 2018-01-30 00:36:06 UTC

No response; changing status. If you have new information, please add a comment.