Bug 244485 - dolphin crashes when trying to view details on folder on usb-stick
Summary: dolphin crashes when trying to view details on folder on usb-stick
Status: RESOLVED DUPLICATE of bug 238807
Alias: None
Product: dolphin
Classification: Applications
Component: general (other bugs)
Version First Reported In: 16.12.2
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Peter Penz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-13 13:32 UTC by maria.warren
Modified: 2010-07-14 15:32 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description maria.warren 2010-07-13 13:32:32 UTC
Application: dolphin (1.3)
KDE Platform Version: 4.4.92 (KDE 4.4.92 (KDE 4.5 RC2)) "release 2"
Qt Version: 4.6.3
Operating System: Linux 2.6.31.12-0.2-desktop i686
Distribution: "openSUSE 11.2 (i586)"

-- Information about the crash:
- What I was doing when the application crashed:

I was working in a subfolder on the usb-stick. when trying to change from regular view to either details or colums dolphin crashes.
This only happens on the usb-stick, not on hdd.

The crash can be reproduced every time.

-- Backtrace:
Application: Dolphin (dolphin), signal: Aborted
[KCrash Handler]
#7  0xffffe424 in __kernel_vsyscall ()
#8  0xb5a3e0cf in raise () from /lib/libc.so.6
#9  0xb5a3f9e7 in abort () from /lib/libc.so.6
#10 0xb5a7a4ed in ?? () from /lib/libc.so.6
#11 0xb5a8050b in ?? () from /lib/libc.so.6
#12 0xb5a85049 in free () from /lib/libc.so.6
#13 0xb5c4ef4f in operator delete(void*) () from /usr/lib/libstdc++.so.6
#14 0xb73530f5 in DolphinCategoryDrawer::~DolphinCategoryDrawer() () from /usr/lib/libdolphinprivate.so.4
#15 0xb73486fc in DolphinIconsView::~DolphinIconsView() () from /usr/lib/libdolphinprivate.so.4
#16 0xb5e02d73 in qDeleteInEventHandler(QObject*) () from /usr/lib/libQtCore.so.4
#17 0xb5e044f8 in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4
#18 0xb60a1440 in QWidget::event(QEvent*) () from /usr/lib/libQtGui.so.4
#19 0xb648d555 in QFrame::event(QEvent*) () from /usr/lib/libQtGui.so.4
#20 0xb652af34 in QAbstractScrollArea::event(QEvent*) () from /usr/lib/libQtGui.so.4
#21 0xb65dc7cc in QAbstractItemView::event(QEvent*) () from /usr/lib/libQtGui.so.4
#22 0xb65f8d03 in QListView::event(QEvent*) () from /usr/lib/libQtGui.so.4
#23 0xb60412ac in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#24 0xb6048178 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#25 0xb6ebb201 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#26 0xb5df358e in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#27 0xb5df7097 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQtCore.so.4
#28 0xb5df721c in QCoreApplication::sendPostedEvents(QObject*, int) () from /usr/lib/libQtCore.so.4
#29 0xb5e206cd in ?? () from /usr/lib/libQtCore.so.4
#30 0xb533b4c2 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#31 0xb533ed98 in ?? () from /usr/lib/libglib-2.0.so.0
#32 0xb533eebe in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#33 0xb5e201b1 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#34 0xb6101dfa in ?? () from /usr/lib/libQtGui.so.4
#35 0xb5df1bfd in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#36 0xb5df2049 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#37 0xb5df72f0 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#38 0xb6041354 in QApplication::exec() () from /usr/lib/libQtGui.so.4
#39 0x0807b0b5 in _start ()

Possible duplicates by query: bug 242572, bug 240028, bug 238807.

Reported using DrKonqi
Comment 1 Frank Reininghaus 2010-07-14 15:32:37 UTC
Thanks for the bug report! This looks like a crash that has been reported already.

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