Bug 170557 - Dolphin crashes after save configuration
Summary: Dolphin crashes after save configuration
Status: RESOLVED DUPLICATE of bug 166921
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Peter Penz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-09-06 20:41 UTC by Michal Kucera
Modified: 2008-09-07 18:59 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 Michal Kucera 2008-09-06 20:41:52 UTC
Version:            (using KDE 4.1.1)
OS:                Linux
Installed from:    Ubuntu Packages

When I go to Settings of Dophin - General and here I check or uncheck option "View Command 'delete'", Doplhin crash. 

Here is debug output: 

Aplikace: Dolphin (dolphin), signál 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 0xb5fbd720 (LWP 22108)]
(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  0xb7fca410 in __kernel_vsyscall ()
#7  0xb6818085 in raise () from /lib/tls/i686/cmov/libc.so.6
#8  0xb6819a01 in abort () from /lib/tls/i686/cmov/libc.so.6
#9  0xb761d367 in qt_message_output () from /usr/lib/libQtCore.so.4
#10 0xb761d458 in qFatal () from /usr/lib/libQtCore.so.4
#11 0xb761d505 in qt_assert () from /usr/lib/libQtCore.so.4
#12 0xb7de7515 in ?? () from /usr/lib/kde4/lib/libkio.so.5
#13 0xb7dedb02 in ?? () from /usr/lib/kde4/lib/libkio.so.5
#14 0xb7dedbcb in KDirLister::Private::CachedItemsJob::done ()
   from /usr/lib/kde4/lib/libkio.so.5
#15 0xb7dedc33 in KDirLister::Private::CachedItemsJob::qt_metacall ()
   from /usr/lib/kde4/lib/libkio.so.5
#16 0xb771f8ab in QMetaCallEvent::placeMetaCall ()
   from /usr/lib/libQtCore.so.4
#17 0xb7720c31 in QObject::event () from /usr/lib/libQtCore.so.4
#18 0xb6c8ff9c in QApplicationPrivate::notify_helper ()
   from /usr/lib/libQtGui.so.4
#19 0xb6c94bf9 in QApplication::notify () from /usr/lib/libQtGui.so.4
#20 0xb7b9f1c3 in KApplication::notify () from /usr/lib/kde4/lib/libkdeui.so.5
#21 0xb77110b9 in QCoreApplication::notifyInternal ()
   from /usr/lib/libQtCore.so.4
#22 0xb7712469 in QCoreApplicationPrivate::sendPostedEvents ()
   from /usr/lib/libQtCore.so.4
#23 0xb771268d in QCoreApplication::sendPostedEvents ()
   from /usr/lib/libQtCore.so.4
#24 0xb773c62f in ?? () from /usr/lib/libQtCore.so.4
#25 0xb635ddd6 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#26 0xb6361193 in ?? () from /usr/lib/libglib-2.0.so.0
#27 0xb636174e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#28 0xb773c9f8 in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#29 0xb6d23a25 in ?? () from /usr/lib/libQtGui.so.4
#30 0xb771033d in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#31 0xb77104cd in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#32 0xb70fc93a in QDialog::exec () from /usr/lib/libQtGui.so.4
#33 0x0806a591 in _start ()
#0  0xb7fca410 in __kernel_vsyscall ()
Comment 1 Frank Reininghaus 2008-09-06 23:40:23 UTC
Thanks for the report. I assume that this only happens in "Split" mode (i.e., when you have two directories open in the same Dolphin window), and the crash occurs when you click "OK" or "Apply" in the configuration dialog? If yes, this looks like bug 167772 which is in turn a duplicate of bug 166921.
Comment 2 Michal Kucera 2008-09-07 17:01:37 UTC
Yes, It rised in split mode of dolphin. Configuration is saved but dolphin crash. In normal mode it works properly. It is the same case as you wrote. 
Comment 3 Frank Reininghaus 2008-09-07 18:59:59 UTC
Thanks for the reply, Michal! It's really a duplicate then.

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