Ark crashes with seg fault when opening zip file

Bug #380278 reported by Chris
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
kdeutils (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Ark crashes every time I try to open / decompress zip file. With tar, tar.gz everything works fine.
Crash handler reports Seg fault, but fails to create a backtrace because of missing debug packages.
Which debugging packages should I install?

Application that crashed: ark
Version of the application: 2.13
KDE Version: 4.2.85 (KDE 4.2.85 (KDE 4.3 Beta1))
Qt Version: 4.5.1
Operating System: Linux 2.6.30-5-generic x86_64
Distribution: Ubuntu karmic (development branch)

What I was doing when the application crashed:
<In detail, tell us what you were doing when the application crashed.>

 -- Backtrace:
An useful backtrace could not be generated

Report to https://bugs.kde.org

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Could you please install kdeutils-dbg and paste the backtrace from the KDE crash handler? Thanks.

Changed in kdeutils (Ubuntu):
status: New → Incomplete
Revision history for this message
Chris (cpeter1) wrote :

I already have had installed kdeutils-dbg, but no backtrace is generated, except the seg fault feedback I have posted above. Which other information would help for debugging?

Revision history for this message
Adam Reeve (adreeve) wrote :

I get similar behaviour. Ark crashes sometimes when opening zip files, but other times it doesn't. When it does open them, extracting has no effect. It's as if everything works fine but no files are actually extracted. Extracting the files from Nautilus in Ubuntu works fine.

I'll try and generate a backtrace later with the -dbg package.

Revision history for this message
Adam Reeve (adreeve) wrote :

I couldn't generate a backtrace either. I get this output on the terminal when opening a zip file from ark:

KCrash: Application 'ark' crashing...
sock_file=/home/adam/.kde/socket-adam-desktop/kdeinit4__0
QFile::at: Cannot set file position 0
ark: Fatal IO error: client killed

I don't know if that "Cannot set file position 0" is related to ark or KCrash and if it's helpful at all.

I get this in my ~/.xsession-errors:

kded(3868) Mollet::KioSlaveNotifier::onDirectoryEntered: "file:///home/adam/Downloads"
"KConfigIni: In file /home/adam/.kde/share/apps/RecentDocuments/laplace_inversion_gavsteh.zip.desktop.lock, line 1: " Invalid entry (missing '=')
"KConfigIni: In file /home/adam/.kde/share/apps/RecentDocuments/laplace_inversion_gavsteh.zip.desktop.lock, line 2: " Invalid entry (missing '=')
"KConfigIni: In file /home/adam/.kde/share/apps/RecentDocuments/laplace_inversion_gavsteh.zip.desktop.lock, line 3: " Invalid entry (missing '=')
findServiceByDesktopPath: /home/adam/.kde/share/apps/RecentDocuments/laplace_inversion_gavsteh.zip.desktop not found
kdeinit4: preparing to launch /usr/lib/kde4/libexec/drkonqi
ptrace: No such process.
/tmp/kde-adam/drkonqihc5778.tmp:2: Error in sourced command file:
No stack.

The laplace_inversion_gavsteh.zip file is what I'm trying to open, I'm not sure why it's looking in the RecentDocuments directory, I opened it from ~/Downloads.

Revision history for this message
Adam Reeve (adreeve) wrote :
Download full text (4.8 KiB)

I tried to generate a backtrace in gdb and got this:

#0 0x007de9f6 in memcpy () from /lib/tls/i686/cmov/libc.so.6
#1 0xb67652fc in ?? ()
#2 0x04f44b12 in QTextStreamPrivate::putString (this=0x95bf6e6c, s=@0xb676551c, number=false)
    at ../../include/QtCore/../../src/corelib/tools/qstring.h:269
#3 0x04f4048b in QTextStream::operator<< (this=0x992cbe8, string=@0xb676551c) at io/qtextstream.cpp:2509
#4 0x04fbec66 in streamDebug (dbg=DWARF-2 expression error: DW_OP_reg operations must be used either alone or in conjuction with DW_OP_piece.
) at ../../include/QtCore/../../src/corelib/io/qdebug.h:108
#5 0x00f0afae in streamDebug (dbg={stream = 0x992cbe8}, v=@0x99c5348) at kernel/qguivariant.cpp:517
#6 0x04fbdc7b in operator<< (dbg=DWARF-2 expression error: DW_OP_reg operations must be used either alone or in conjuction with DW_OP_piece.
) at kernel/qvariant.cpp:2774
#7 0x08806082 in CliPlugin::readListLine (this=0x996fc08, line=
      {static null = {<No data fields>}, static shared_null = {ref = {_q_value = 7202}, alloc = 0, size = 0, data = 0x80574e2, clean = 0, simpletext = 0, righttoleft = 0, asciiCache = 0, capacity = 0, reserved = 0, array = {0}}, static shared_empty = {ref = {_q_value = 229}, alloc = 0, size = 0, data = 0x508d46e, clean = 0, simpletext = 0, righttoleft = 0, asciiCache = 0, capacity = 0, reserved = 0, array = {0}}, d = 0x9934be8, static codecForCStrings = 0x0}) at /usr/include/qt4/QtCore/qdebug.h:211
#8 0x009bede4 in Kerfuffle::CliInterface::handleLine (this=0x996fc08, line=@0xb67659b0) at ../../../ark/kerfuffle/cliinterface.cpp:529
#9 0x009bf40d in Kerfuffle::CliInterface::readStdout (this=0x996fc08) at ../../../ark/kerfuffle/cliinterface.cpp:487
#10 0x009bf83b in Kerfuffle::CliInterface::qt_metacall (this=0x996fc08, _c=QMetaObject::InvokeMetaMethod, _id=5, _a=0xb6765a8c)
    at ./cliinterface.moc:71
#11 0x04fafd78 in QMetaObject::activate (sender=0x988fd70, from_signal_index=13, to_signal_index=13, argv=0x0) at kernel/qobject.cpp:3120
#12 0x04fb0a12 in QMetaObject::activate (sender=0x988fd70, m=0x508ae8c, local_signal_index=5, argv=0x0) at kernel/qobject.cpp:3194
#13 0x04f35fd7 in QProcess::readyReadStandardOutput (this=0x988fd70) at .moc/release-shared/moc_qprocess.cpp:156
#14 0x04f38b7a in QProcessPrivate::_q_canReadStandardOutput (this=0x98be518) at io/qprocess.cpp:564
#15 0x04f3bf06 in QProcess::qt_metacall (this=0x988fd70, _c=QMetaObject::InvokeMetaMethod, _id=9, _a=0xb6765c88)
    at .moc/release-shared/moc_qprocess.cpp:101
#16 0x081e490a in KProcess::qt_metacall (this=0x988fd70, _c=QMetaObject::InvokeMetaMethod, _id=17, _a=0xb6765c88) at ./kprocess.moc:63
#17 0x04fafd78 in QMetaObject::activate (sender=0x9927b68, from_signal_index=4, to_signal_index=4, argv=0xb6765c88)
    at kernel/qobject.cpp:3120
#18 0x04fb0a12 in QMetaObject::activate (sender=0x9927b68, m=0x508c8b0, local_signal_index=0, argv=0xb6765c88) at kernel/qobject.cpp:3194
#19 0x04feabe3 in QSocketNotifier::activated (this=0x9927b68, _t1=27) at .moc/release-shared/moc_qsocketnotifier.cpp:83
#20 0x04fb4817 in QSocketNotifier::event (this=0x9927b68, e=0xb6766044) at kernel/qsock...

Read more...

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Thanks. This looks like https://bugs.kde.org/show_bug.cgi?id=192798 which should be fixed in KDE 4.3 beta2 coming this week. :)

Changed in kdeutils (Ubuntu):
importance: Undecided → Medium
status: Incomplete → Fix Committed
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Fix released to the development version of Kubuntu 9.10.

Changed in kdeutils (Ubuntu):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.