dolphin crash

(Please keep kde-devel in the reply list, as I am not subscribed to
kfm-devel, and personal e-mail is both a pain to reply to, and currently
a pain to read as well.)

Seems I killed dolphin, thereby making it impossible to manage files
with KDE. As best I can tell, problems started when I tried to turn on
previews.

Thoughts?

Here's the backtrace:
#0 KDirModel::setData (this=0x8cf150, index=@0x7fff2f8ee370,
value=@0x7fff2f8ee450, role=1) at
/
#1 0x00002aaaac5b1c82 in IconManager::replaceIcon (this=0x8d18f0,
item=@0xb04150, pixmap=@0xb04158) at
/
#2 0x00002aaaac5b1d81 in
(this=0x8d18f0) at
/

#3 0x00002aaaac5b23c9 in IconManager::qt_metacall (this=0x8d18f0,
_c=QM::InvokeMetaMethod, _id=4, _a=0x7fff2f8ee5a0)

at
/


#4 0x00002aaaaac17617 in QM::activate (sender=0x8d1c80,
from_signal_index=4, to_signal_index=4, argv=0x0) at
/
#5 0x00002aaaaac17a7b in QM::activate (sender=0x8d1c80,
m=0x2aaaaaf03740, local_signal_index=0, argv=0x0) at
/
#6 0x00002aaaaac54328 in QTimer::timeout (this=0x8d1c80) at


#7 0x00002aaaaac21c16 in QTimer::timerEvent (this=0x8d1c80,
e=0x7fff2f8eeed0) at
/

#8 0x00002aaaaac1674a in Q::event (this=0x8d1c80,
e=0x7fff2f8eeed0) at
/

#9 0x00002aaaad40a439 in
(this=0x6a2f30, receiver=0x8d1c80, e=0x7fff2f8eeed0) at
/
#10 0x00002aaaad40a75b in QApplication::notify (this=0x7fff2f8ef2a0,
receiver=0x8d1c80, e=0x7fff2f8eeed0) at
/

#11 0x00002aaaab55a280 in KApplication::notify (this=0x7fff2f8ef2a0,
receiver=0x8d1c80, event=0x7fff2f8eeed0) at
/

#12 0x00002aaaaac038fa in
(this=0x7fff2f8ef2a0, receiver=0x8d1c80, event=0x7fff2f8eeed0)

at
/


#13 0x00002aaaaac07197 in QCoreApplication::sendEvent
(receiver=0x8d1c80, event=0x7fff2f8eeed0) at
/

#14 0x00002aaaaac33e0d in QTimerInfoList::activateTimers (this=0x6a6480)
at
/

#15 0x00002aaaaac30ec5 in timerSourceDispatch (source=0x6a6420) at
/

#16 0x0000003798a2ef53 in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0

#17 0x0000003798a3224d in ()
at
/
#18 0x0000003798a3277e in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#19 0x00002aaaaac308ac in
(this=0x695e70, flags=@0x7fff2f8ef0f0) at
/
#20 0x00002aaaad4a8f6f in
(this=0x695e70, flags=@0x7fff2f8ef150) at
/
#21 0x00002aaaaac00878 in QEventLoop::processEvents
(this=0x7fff2f8ef200, flags=@0x7fff2f8ef1b0) at
/
#22 0x00002aaaaac00a74 in QEventLoop::exec (this=0x7fff2f8ef200,
flags=@0x7fff2f8ef210) at
/
#23 0x00002aaaaac04186 in QCoreApplication::exec () at
/
#24 0x00002aaaad40a19a in QApplication::exec () at
/
#25 0x0000000000445aab in main (argc=2, argv=0x7fff2f8ef778) at
/


--
Matthew
Yesterday, I thought of the best .sig that has ever been contemplated.
Alas, I forgot it before I could write it down.

Hi Matthew,

Tuesday, 29. April 2008 23:41:10 Matthew Woehlke wrote:
[]
Seems I killed dolphin, thereby making it impossible to manage files
with KDE. As best I can tell, problems started when I tried to turn on
previews.
>
Thoughts?

I could not reproduce such kind of crash yet :-( Judging from the backtrace it
seems to be related to preview functionality of Dolphin. Removing
the .directory file from the directory where the crash occurs should help
(assuming that the activated preview is not default for all directories in
your configuration).

If it's only a specific kind of directory: would it be possible that you zip
the directory and send it to me per e-mail, so that I (hopefully) can
reproduce the crash?

Thanks!
Peter

>
Here's the backtrace:
#0 KDirModel::setData (this=0x8cf150, index=@0x7fff2f8ee370,
value=@0x7fff2f8ee450, role=1) at
/
#1 0x00002aaaac5b1c82 in IconManager::replaceIcon (this=0x8d18f0,
item=@0xb04150, pixmap=@0xb04158) at
/
#2 0x00002aaaac5b1d81 in
(this=0x8d18f0) at
/
>
#3 0x00002aaaac5b23c9 in IconManager::qt_metacall (this=0x8d18f0,
_c=QM::InvokeMetaMethod, _id=4, _a=0x7fff2f8ee5a0)
>
at
/
>
>
#4 0x00002aaaaac17617 in QM::activate (sender=0x8d1c80,
from_signal_index=4, to_signal_index=4, argv=0x0) at
/
#5 0x00002aaaaac17a7b in QM::activate (sender=0x8d1c80,
m=0x2aaaaaf03740, local_signal_index=0, argv=0x0) at
/
#6 0x00002aaaaac54328 in QTimer::timeout (this=0x8d1c80) at

>
#7 0x00002aaaaac21c16 in QTimer::timerEvent (this=0x8d1c80,
e=0x7fff2f8eeed0) at
/
>
#8 0x00002aaaaac1674a in Q::event (this=0x8d1c80,
e=0x7fff2f8eeed0) at
/
>
#9 0x00002aaaad40a439 in
(this=0x6a2f30, receiver=0x8d1c80, e=0x7fff2f8eeed0) at
/
#10 0x00002aaaad40a75b in QApplication::notify (this=0x7fff2f8ef2a0,
receiver=0x8d1c80, e=0x7fff2f8eeed0) at
/
>
#11 0x00002aaaab55a280 in KApplication::notify (this=0x7fff2f8ef2a0,
receiver=0x8d1c80, event=0x7fff2f8eeed0) at
/
>
#12 0x00002aaaaac038fa in
(this=0x7fff2f8ef2a0, receiver=0x8d1c80, event=0x7fff2f8eeed0)
>
at
/
>p:583
>
>
#13 0x00002aaaaac07197 in QCoreApplication::sendEvent
(receiver=0x8d1c80, event=0x7fff2f8eeed0) at
/
>215
>
#14 0x00002aaaaac33e0d in QTimerInfoList::activateTimers (this=0x6a6480)
at
/
>ix.cpp:563
>
#15 0x00002aaaaac30ec5 in timerSourceDispatch (source=0x6a6420) at
/
>ib.cpp:166
>
#16 0x0000003798a2ef53 in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
>
#17 0x0000003798a3224d in ()
at
/
>p:2357 #18 0x0000003798a3277e in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#19 0x00002aaaaac308ac in
(this=0x695e70, flags=@0x7fff2f8ef0f0) at
/
>ib.cpp:325 #20 0x00002aaaad4a8f6f in
(this=0x695e70, flags=@0x7fff2f8ef150) at
/
>b.cpp:204 #21 0x00002aaaaac00878 in QEventLoop::processEvents
(this=0x7fff2f8ef200, flags=@0x7fff2f8ef1b0) at
/
#22 0x00002aaaaac00a74 in QEventLoop::exec (this=0x7fff2f8ef200,
flags=@0x7fff2f8ef210) at
/
#23 0x00002aaaaac04186 in QCoreApplication::exec () at
/
>p:845 #24 0x00002aaaad40a19a in QApplication::exec () at
/
#25 0x0000000000445aab in main (argc=2, argv=0x7fff2f8ef778) at
/

Monday, 5. May 2008 02:19:06 David Faure wrote:
Tuesday 29 April 2008, Matthew Woehlke wrote:
#0 *KDirModel::setData (this=0x8cf150, index=@0x7fff2f8ee370,
value=@0x7fff2f8ee450, role=1) at
/
>
I guess it could crash if the index was invalid by the time
IconManager::replaceIcon was called, e.g. due to a file being deleted
meanwhile. If IconManager stores indexes then it should use
QPersistentModelIndex.

Ah, good hint :-) The IconManager uses KFileItem instances, but I guess the
same problem occurs here too. I'll check this issue

Thanks!
Peter

Peter Penz wrote:
Tuesday, 29. April 2008 23:41:10 Matthew Woehlke wrote:
[]
>Seems I killed dolphin, thereby making it impossible to manage files
>with KDE. As best I can tell, problems started when I tried to turn on
>previews.
>>
>Thoughts?

I could not reproduce such kind of crash yet :-( Judging from the backtrace it
seems to be related to preview functionality of Dolphin. Removing
the .directory file from the directory where the crash occurs should help
(assuming that the activated preview is not default for all directories in
your configuration).

I finally took a second look at this, and I either can't reproduce or
can't find an offending folder. Hopefully it was a transient bug that is
now fixed :-). If not, and if I hit it again, I'll post again.

I *think* it was "any folder", so hopefully that means it's fixed.

--
Matthew
In the beginning, there were not enough colors. -- Guy Keren