Bug 120769

Summary: Krusader Krashes upon selecting user home directory and from then on.
Product: [Applications] krusader Reporter: Scott <geekboy>
Component: generalAssignee: Shie Erlich <manson>
Status: RESOLVED DUPLICATE    
Severity: crash    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Debian testing   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Scott 2006-01-25 10:34:38 UTC
Version:            (using KDE KDE 3.5.0)
Installed from:    Debian testing/unstable Packages
Compiler:          gcc 3.4 
OS:                Linux

I opened Krusader for it's first run. When I got to the actual regular paned interface. I went to change to my home directory in the left pane and the program crashed.

It won't even start without crashing at this point. I've tried it several times.

Here is the initial backtrace:

----------------------------------------------------------------------------
(no debugging symbols found)
Using host libthread_db library "/lib/tls/libthread_db.so.1".
(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)
(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)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1237325088 (LWP 27056)]
(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)
[KCrash handler]
#3  0x08126c66 in QStrList::~QStrList ()
#4  0xb6d1a2df in QListViewPrivate::SortableItem::cmp ()
   from /usr/lib/libqt-mt.so.3
#5  0xb6d1a327 in QListViewPrivate::SortableItem::operator< ()
   from /usr/lib/libqt-mt.so.3
#6  0xb6d1b3a6 in qHeapSortPushDown<QListViewPrivate::SortableItem> ()
   from /usr/lib/libqt-mt.so.3
#7  0xb6d1b5ff in qHeapSortHelper<QListViewPrivate::SortableItem*, 
QListViewPrivate::SortableItem> () from /usr/lib/libqt-mt.so.3
#8  0xb6d1b6a0 in qHeapSort<QListViewPrivate::SortableItem*> ()
   from /usr/lib/libqt-mt.so.3
#9  0xb6d177c6 in QListViewItem::sortChildItems () from 
/usr/lib/libqt-mt.so.3
#10 0xb6d0220b in QListViewItem::enforceSortOrder ()
   from /usr/lib/libqt-mt.so.3
#11 0xb6d01448 in QListView::firstChild () from /usr/lib/libqt-mt.so.3
#12 0xb751ba54 in KListView::setSorting () from /usr/lib/libkdeui.so.4
#13 0x08129da0 in QStrList::~QStrList ()
#14 0x0811260c in QPtrList<KFileItem>::~QPtrList ()
#15 0x08113bfe in QPtrList<KFileItem>::~QPtrList ()
#16 0x0811c71d in QPtrList<KFileItem>::~QPtrList ()
#17 0xb6c0db57 in QObject::activate_signal () from 
/usr/lib/libqt-mt.so.3
#18 0xb6c0e63b in QObject::activate_signal () from 
/usr/lib/libqt-mt.so.3
#19 0x0813bf9d in QValueListPrivate<KURL>::remove ()
#20 0x0813c0b8 in QValueListPrivate<KURL>::remove ()
#21 0x08109be7 in QBitmap::~QBitmap ()
#22 0x0810a0c8 in QBitmap::~QBitmap ()
#23 0x0810b7aa in QBitmap::~QBitmap ()
#24 0xb6c0db57 in QObject::activate_signal () from 
/usr/lib/libqt-mt.so.3
#25 0xb6c0e63b in QObject::activate_signal () from 
/usr/lib/libqt-mt.so.3
#26 0xb6f9fd55 in QTimer::timeout () from /usr/lib/libqt-mt.so.3
#27 0xb6c330b4 in QTimer::event () from /usr/lib/libqt-mt.so.3
#28 0xb6ba3698 in QApplication::internalNotify () from 
/usr/lib/libqt-mt.so.3
#29 0xb6ba38b6 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#30 0xb73338ae in KApplication::notify () from /usr/lib/libkdecore.so.4
#31 0xb6b335e5 in QApplication::sendEvent () from 
/usr/lib/libqt-mt.so.3
#32 0xb6b9498c in QEventLoop::activateTimers () from 
/usr/lib/libqt-mt.so.3
#33 0xb6b4735c in QEventLoop::processEvents () from 
/usr/lib/libqt-mt.so.3
#34 0xb6bbbda2 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#35 0xb6bbbccb in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#36 0xb6ba2225 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#37 0x08081db0 in QMapPrivate<QString, QString>::QMapPrivate ()
#38 0xb6435ed0 in __libc_start_main () from /lib/tls/libc.so.6
#39 0x0807b631 in ?? ()
----------------------------------------------------------------------------
Comment 1 activescott 2006-02-06 08:29:12 UTC
I have what appears to be an identical callstack from suse10 & Krusader 1.60.0. it was working fine, then suddenly it crashed and I cannot go to my home directory any longer. 
Comment 2 activescott 2006-02-06 08:31:04 UTC
I was just viewing bug "114483" and found a comment that says  "More generally, Krusader crashes always when entering a folder which has two files with the same, but differently capitalized filenames." I had just tried to copy a folder into my home directory on top of another folder with the same name (expecting it to combine the contents of two folders). It is possible they were capitalized differently.
Comment 3 Andreas Kling 2006-08-30 20:06:25 UTC

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