Bug 172146

Summary:	Dolphin crashes in columns view
Product:	[Applications] dolphin	Reporter:	Adam Drojewski <adamoki>
Component:	general	Assignee:	Peter Penz <peter.penz19>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	frank78ac
Priority:	NOR
Version First Reported In:	16.12.2
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Adam Drojewski 2008-10-04 14:09:50 UTC

Version:            (using KDE 4.1.2)
OS:                Linux
Installed from:    Ubuntu Packages

It always crashes after I open i (it starts in my home directory), here is 
contents of .directory file:

[Dolphin]
ShowPreview=true
Timestamp=2008,10,4,14,6,51
ViewMode=2

it is switched to columns view - after I delete .directory file it's OK till I switch to columns view again.

Here is dump:

Program: Dolphin (dolphin), sygnał SIGABRT
(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 0xb5fbb720 (LWP 9780)]
(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)
(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]
#6  0xb7fd7410 in __kernel_vsyscall ()
#7  0xb6815085 in raise () from /lib/tls/i686/cmov/libc.so.6
#8  0xb6816a01 in abort () from /lib/tls/i686/cmov/libc.so.6
#9  0xb761b367 in qt_message_output () from /usr/lib/libQtCore.so.4
#10 0xb761b458 in qFatal () from /usr/lib/libQtCore.so.4
#11 0xb761b505 in qt_assert () from /usr/lib/libQtCore.so.4
#12 0xb7e017c9 in KDirModel::setData () from /usr/lib/kde4/lib/libkio.so.5
#13 0xb7fb2d95 in ?? () from /usr/lib/kde4/lib/libdolphinprivate.so.4
#14 0xb7fb37fa in ?? () from /usr/lib/kde4/lib/libdolphinprivate.so.4
#15 0xb7723f79 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#16 0xb7724642 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#17 0xb7761817 in QTimer::timeout () from /usr/lib/libQtCore.so.4
#18 0xb772b0fe in QTimer::timerEvent () from /usr/lib/libQtCore.so.4
#19 0xb771e9fa in QObject::event () from /usr/lib/libQtCore.so.4
#20 0xb6c8cf9c in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#21 0xb6c91bf9 in QApplication::notify () from /usr/lib/libQtGui.so.4
#22 0xb7baa483 in KApplication::notify () from /usr/lib/kde4/lib/libkdeui.so.5
#23 0xb770f0b9 in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#24 0xb773cc01 in ?? () from /usr/lib/libQtCore.so.4
#25 0xb773a4a0 in ?? () from /usr/lib/libQtCore.so.4
#26 0xb6359dd6 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#27 0xb635d193 in ?? () from /usr/lib/libglib-2.0.so.0
#28 0xb635d74e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#29 0xb773a9f8 in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#30 0xb6d20a25 in ?? () from /usr/lib/libQtGui.so.4
#31 0xb770e33d in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#32 0xb770e4cd in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#33 0xb771074d in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#34 0xb6c8c897 in QApplication::exec () from /usr/lib/libQtGui.so.4
#35 0x08080a89 in ?? ()
#36 0xb6800450 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#37 0x080619d1 in _start ()
#0  0xb7fd7410 in __kernel_vsyscall ()

Comment 1 Frank Reininghaus 2008-10-04 17:52:34 UTC

Thanks for the bug report. This looks like a duplicate of bug 170547 to me. Just to be sure: Do you have an image that is either very broad or very high (i.e., quite far away from square-shape) in the directory where you get the crash?

Comment 2 Adam Drojewski 2008-10-05 19:10:57 UTC

That's right, I removed all images from my home directory and now it's OK

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