Bug 54659 - going back while .jar content gets listed causes sig 11
Summary: going back while .jar content gets listed causes sig 11
Status: RESOLVED FIXED
Alias: None
Product: ark
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR crash
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
: 58081 (view as bug list)
Depends on:
Blocks:
 
Reported: 2003-02-15 00:34 UTC by Carsten Lohrke
Modified: 2003-05-03 23:19 UTC (History)
1 user (show)

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 Carsten Lohrke 2003-02-15 00:34:22 UTC
Version:           3.1.0 (using KDE 3.1.0)
Installed from:    Gentoo
Compiler:          gcc version 3.2.1 20021207 (Gentoo Linux 3.2.1-20021207)
OS:          Linux (i686) release 2.4.19-gentoo-r10

(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...[New Thread 16384 (LWP 29801)]

(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...(no debugging symbols found)...
(no debugging symbols found)...0x46334a99 in wait4 () from /lib/libc.so.6
#0  0x46334a99 in wait4 () from /lib/libc.so.6
#1  0x463b120c in __DTOR_END__ () from /lib/libc.so.6
#2  0x46126ba3 in waitpid () from /lib/libpthread.so.0
#3  0x458208db in KCrash::defaultCrashHandler(int) ()
   from /usr/kde/3.1/lib/libkdecore.so.4
#4  0x4792bb3d in Arch::slotReceivedTOC(KProcess*, char*, int) ()
   from /usr/kde/3.1/lib/libarkpart.so
#5  0x4792d9e7 in Arch::qt_invoke(int, QUObject*) ()
   from /usr/kde/3.1/lib/libarkpart.so
#6  0x4792430d in ZipArch::qt_invoke(int, QUObject*) ()
   from /usr/kde/3.1/lib/libarkpart.so
#7  0x45bd4989 in QObject::activate_signal(QConnectionList*, QUObject*) ()
   from /usr/qt/3/lib/libqt-mt.so.3
Comment 1 Georg Robbers 2003-05-01 18:23:54 UTC
This bug has been fixed in CVS. The upcoming KDE 3.1.2 release will contain a fixed 
version of ark. Thanks for reporting this bug ! 
Comment 2 Georg Robbers 2003-05-03 23:19:09 UTC
*** Bug 58081 has been marked as a duplicate of this bug. ***