ark crashed while creating a file

Bug #350734 reported by sputnik
26
This bug affects 2 people
Affects Status Importance Assigned to Milestone
kdelibs
Fix Released
High
kde4libs (Ubuntu)
Invalid
Low
Unassigned

Bug Description

ark:
  installierte Version: 4:4.2.1-0ubuntu1~intrepid1

Anwendung: Ark (ark), Signal SIGSEGV
[Current thread is 0 (LWP 9780)]

Thread 2 (Thread 0xb42ccb90 (LWP 9844)):
#0 0xb62bd54a in clock_gettime () from /lib/tls/i686/cmov/librt.so.1
#1 0xb6b450ab in ?? () from /usr/lib/libQtCore.so.4
#2 0xb6b45281 in ?? () from /usr/lib/libQtCore.so.4
#3 0xb6b46e3c in ?? () from /usr/lib/libQtCore.so.4
#4 0xb6b4365a in ?? () from /usr/lib/libQtCore.so.4
#5 0xb63de622 in IA__g_main_context_prepare (context=0x84c20c8, priority=0xb42cbfa8) at /build/buildd/glib2.0-2.18.2/glib/gmain.c:2464
#6 0xb63deaaa in g_main_context_iterate (context=0x84c20c8, block=1, dispatch=1, self=0xb3911af8) at /build/buildd/glib2.0-2.18.2/glib/gmain.c:2758
#7 0xb63def81 in IA__g_main_context_iteration (context=0x84c20c8, may_block=1) at /build/buildd/glib2.0-2.18.2/glib/gmain.c:2841
#8 0xb6b43497 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#9 0xb6b1752a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#10 0xb6b176ea in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#11 0xb6d3c051 in KJob::exec (this=0xb3911080) at /build/buildd/kde4libs-4.2.1a/kdecore/jobs/kjob.cpp:195
#12 0xb7fd97da in Kerfuffle::RecursiveLister::run (this=0xb42cc1b0) at /build/buildd/kdeutils-4.2.1/ark/kerfuffle/recursivelister.cpp:52
#13 0xb3ac7ad0 in LibArchiveInterface::addFiles (this=0x826a598, files=@0x84e8e2c, options=@0x84e8e30) at /build/buildd/kdeutils-4.2.1/ark/plugins/libarchive/libarchivehandler.cpp:526
#14 0xb7fd3100 in Kerfuffle::AddJob::doWork (this=0x84e8e18) at /build/buildd/kdeutils-4.2.1/ark/kerfuffle/jobs.cpp:185
#15 0xb7fd4fd4 in Kerfuffle::ThreadExecution::run (this=0x8239120) at /build/buildd/kdeutils-4.2.1/ark/kerfuffle/threading.cpp:39
#16 0xb6a286ae in ?? () from /usr/lib/libQtCore.so.4
#17 0xb649e50f in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#18 0xb6831a0e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread 0xb60ae8d0 (LWP 9780)):
[KCrash Handler]
#6 0xb6ad3ef0 in QUrl::host () from /usr/lib/libQtCore.so.4
#7 0xb7df5a8b in searchIdleList (idleSlaves=@0x8270584, url=@0x60, protocol=@0xbf821c40, exact=@0xbf821ceb) at /build/buildd/kde4libs-4.2.1a/kio/kio/scheduler.cpp:609
#8 0xb7dfa9e4 in KIO::SchedulerPrivate::findIdleSlave (this=0x8270530, job=0xb39645c0, exact=@0xbf821ceb) at /build/buildd/kde4libs-4.2.1a/kio/kio/scheduler.cpp:683
#9 0xb7dfb26f in KIO::SchedulerPrivate::startJobScheduled (this=0x8270530, protInfo=0x8310f88) at /build/buildd/kde4libs-4.2.1a/kio/kio/scheduler.cpp:522
#10 0xb7dfb815 in KIO::SchedulerPrivate::startStep (this=0x8270530) at /build/buildd/kde4libs-4.2.1a/kio/kio/scheduler.cpp:439
#11 0xb7dfb9f6 in KIO::Scheduler::qt_metacall (this=0x826b078, _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0xbf821dc8) at /build/buildd/kde4libs-4.2.1a/obj-i486-linux-gnu/kio/scheduler.moc:101
#12 0xb6b2da60 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#13 0xb6b2e7e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#14 0xb6b687a7 in QTimer::timeout () from /usr/lib/libQtCore.so.4
#15 0xb6b3440e in QTimer::timerEvent () from /usr/lib/libQtCore.so.4
#16 0xb6b2853f in QObject::event () from /usr/lib/libQtCore.so.4
#17 0xb6fcb8ec in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#18 0xb6fd372e in QApplication::notify () from /usr/lib/libQtGui.so.4
#19 0xb7ae510d in KApplication::notify (this=0xbf822514, receiver=0x8270534, event=0xbf82225c) at /build/buildd/kde4libs-4.2.1a/kdeui/kernel/kapplication.cpp:307
#20 0xb6b18e61 in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#21 0xb6b46d81 in ?? () from /usr/lib/libQtCore.so.4
#22 0xb6b43520 in ?? () from /usr/lib/libQtCore.so.4
#23 0xb63db718 in IA__g_main_context_dispatch (context=0x813ac58) at /build/buildd/glib2.0-2.18.2/glib/gmain.c:2144
#24 0xb63dedc3 in g_main_context_iterate (context=0x813ac58, block=1, dispatch=1, self=0x8137e30) at /build/buildd/glib2.0-2.18.2/glib/gmain.c:2778
#25 0xb63def81 in IA__g_main_context_iteration (context=0x813ac58, may_block=1) at /build/buildd/glib2.0-2.18.2/glib/gmain.c:2841
#26 0xb6b43478 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#27 0xb7065ea5 in ?? () from /usr/lib/libQtGui.so.4
#28 0xb6b1752a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#29 0xb6b176ea in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#30 0xb6b19da5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#31 0xb6fcb767 in QApplication::exec () from /usr/lib/libQtGui.so.4
#32 0x0805228f in main (argc=5, argv=0xbf8228d4) at /build/buildd/kdeutils-4.2.1/ark/app/main.cpp:222

Revision history for this message
Jon Charge (seropith) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we can't fix it because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures

At a minimum, we need:
1. the specific steps or actions you took that caused you to encounter the problem,
2. the behavior you expected, and
3. the behavior you actually encountered (in as much detail as possible).
Thanks!

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

Hi John!

thanks for the quick reply!

... I just can't figure out what you exactly need from theses steps. Sorry!

I already installed a big bunch of dbg-packages. I would install a new one as Ark is really often used and it isn't very good in the moment.

Or does my description not fit?

Thank you for a reply! :)

Revision history for this message
Jon Charge (seropith) wrote :

Hi. No problem. :) I want to reproduce your bug so I need to know... how exactly you were creating / compressing the file. Did you right click on a file on the desktop and compress it there, or did you open ark manually and do it form within ark? I need the step by step so it can be reproduced.

Thanks again,

Jon

Revision history for this message
sputnik (sputnik) wrote :

Ah. Great! - Now I know! :)

... I tried to compress a folder in Dolphin.

Right click - context menue "compress to archieve"
I choose the filename.
Extension tar.bz2

The sysem notifier showed the begin of the compression. After ~3 seconds the crash manager appeared.

I could just reproduce this bug here.

Thanks for your attention! :)

Jon Charge (seropith)
Changed in kdeutils:
assignee: nobody → seropith
Revision history for this message
Jon Charge (seropith) wrote :

I am able to reproduce this bug exactly and have uploaded debugging files to #350753

Jon

Revision history for this message
Jon Charge (seropith) wrote :
Changed in kdeutils:
assignee: seropith → nobody
status: Incomplete → Confirmed
Revision history for this message
Jon Charge (seropith) wrote : apport-collect data

Architecture: i386
Dependencies:

DistroRelease: Ubuntu 9.04
Package: kdeutils None [modified: /var/lib/dpkg/info/kdeutils.list]
PackageArchitecture: all
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.UTF-8
Uname: Linux 2.6.28-11-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev root sambashare

affects: kdeutils (Ubuntu) → kde4libs (Ubuntu)
Changed in kde4libs (Ubuntu):
importance: Undecided → Low
status: Confirmed → Triaged
Changed in kdelibs:
status: Unknown → New
Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Hi there!

Thanks for reporting this bug! Your bug seems to be a problem with the KDE program itself, and not with our KDE packages. But don't worry! This issue is being tracked by the KDE developers at: http://bugs.kde.org/show_bug.cgi?id=163171
Once fixed in KDE, it will be included in Kubuntu once the KDE version the fix is in in reaches Kubuntu.

Thanks!

Changed in kde4libs (Ubuntu):
status: Triaged → Invalid
Changed in kdelibs:
importance: Unknown → High
Changed in kdelibs:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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