Bug 235424 - Crashed while updating favicons
Summary: Crashed while updating favicons
Status: RESOLVED WORKSFORME
Alias: None
Product: keditbookmarks
Classification: Applications
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Konqueror Bugs
URL:
Keywords:
: 243212 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-04-26 11:59 UTC by Leonardo La Malfa
Modified: 2018-11-28 04:54 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Leonardo La Malfa 2010-04-26 11:59:19 UTC
Application: keditbookmarks (4.4.2 (KDE 4.4.2))
KDE Platform Version: 4.4.2 (KDE 4.4.2)
Qt Version: 4.6.2
Operating System: Linux 2.6.32-21-generic i686
Distribution: Ubuntu 10.04 LTS

-- Information about the crash:
Just imported Firefox bookmarks, and hit update favicons. After a couple of seconds, I had this crash.

 -- Backtrace:
Application: Bookmark Editor (keditbookmarks), signal: Segmentation fault
[Current thread is 1 (Thread 0xb776c9f0 (LWP 2755))]

Thread 2 (Thread 0xb5252b70 (LWP 2756)):
#0  0x00b17e16 in clock_gettime () from /lib/tls/i686/cmov/librt.so.1
#1  0x0507a6fb in qt_gettime () at kernel/qcore_unix.cpp:111
#2  0x0507f825 in QTimerInfoList::updateCurrentTime (this=0x8464da4) at kernel/qeventdispatcher_unix.cpp:340
#3  0x0507f86a in QTimerInfoList::timerWait (this=0x8464da4, tm=...) at kernel/qeventdispatcher_unix.cpp:443
#4  0x0507d818 in timerSourcePrepareHelper (src=<value optimized out>, timeout=0xb52520cc) at kernel/qeventdispatcher_glib.cpp:136
#5  0x0507d8a5 in timerSourcePrepare (source=0x0, timeout=0xb1bff4) at kernel/qeventdispatcher_glib.cpp:169
#6  0x069c4aca in g_main_context_prepare () from /lib/libglib-2.0.so.0
#7  0x069c4ee9 in ?? () from /lib/libglib-2.0.so.0
#8  0x069c54b8 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#9  0x0507d60f in QEventDispatcherGlib::processEvents (this=0x84322d0, flags=...) at kernel/qeventdispatcher_glib.cpp:414
#10 0x05050059 in QEventLoop::processEvents (this=0xb5252290, flags=) at kernel/qeventloop.cpp:149
#11 0x050504aa in QEventLoop::exec (this=0xb5252290, flags=...) at kernel/qeventloop.cpp:201
#12 0x04f4c5a8 in QThread::exec (this=0x8433d00) at thread/qthread.cpp:487
#13 0x0502fc1b in QInotifyFileSystemWatcherEngine::run (this=0x8433d00) at io/qfilesystemwatcher_inotify.cpp:248
#14 0x04f4f32e in QThreadPrivate::start (arg=0x8433d00) at thread/qthread_unix.cpp:248
#15 0x0013a96e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#16 0x005a5a0e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread 0xb776c9f0 (LWP 2755)):
[KCrash Handler]
#6  0x00cd5c4c in KBookmarkModel::indexForBookmark (this=0x0, bk=...) at ../../../apps/keditbookmarks/bookmarkmodel.cpp:257
#7  0x00cd60a0 in KBookmarkModel::emitDataChanged (this=0x0, bk=...) at ../../../apps/keditbookmarks/bookmarkmodel.cpp:262
#8  0x00ccbeb2 in FavIconsItr::setStatus (this=0x8cfa998, status=...) at ../../../apps/keditbookmarks/favicons.cpp:76
#9  0x00ccbfab in FavIconsItr::doAction (this=0x8cfa998) at ../../../apps/keditbookmarks/favicons.cpp:93
#10 0x00cc9522 in BookmarkIterator::nextOne (this=0x8cfa998) at ../../../apps/keditbookmarks/bookmarkiterator.cpp:68
#11 0x00cc95e3 in BookmarkIterator::qt_metacall (this=0x8cfa998, _c=QMetaObject::InvokeMetaMethod, _id=5, _a=0xbfb06f4c) at ./bookmarkiterator.moc:80
#12 0x00ccc44a in FavIconsItr::qt_metacall (this=0x8cfa998, _c=QMetaObject::InvokeMetaMethod, _id=5, _a=0xbfb06f4c) at ./favicons.moc:67
#13 0x05056c9a in QMetaObject::metacall (object=0x8cfa998, cl=138438656, idx=5, argv=0xbfb06f4c) at kernel/qmetaobject.cpp:237
#14 0x050653d5 in QMetaObject::activate (sender=0x8ea66b0, m=0x5164188, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3293
#15 0x0506cfe7 in QSingleShotTimer::timeout (this=0x8ea66b0) at .moc/release-shared/qtimer.moc:82
#16 0x0506d0fc in QSingleShotTimer::timerEvent (this=0x8ea66b0) at kernel/qtimer.cpp:308
#17 0x05062254 in QObject::event (this=0x8ea66b0, e=0xbfb06d30) at kernel/qobject.cpp:1212
#18 0x075324dc in QApplicationPrivate::notify_helper (this=0x82e2a90, receiver=0x8ea66b0, e=0xbfb07480) at kernel/qapplication.cpp:4300
#19 0x0753905e in QApplication::notify (this=0xbfb07914, receiver=0x8ea66b0, e=0xbfb07480) at kernel/qapplication.cpp:3704
#20 0x00ec4f2a in KApplication::notify (this=0xbfb07914, receiver=0x8ea66b0, event=0xbfb07480) at ../../kdeui/kernel/kapplication.cpp:302
#21 0x05051a3b in QCoreApplication::notifyInternal (this=0xbfb07914, receiver=0x8ea66b0, event=0xbfb07480) at kernel/qcoreapplication.cpp:704
#22 0x05080d66 in QCoreApplication::sendEvent (this=0x82e5a34) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#23 QTimerInfoList::activateTimers (this=0x82e5a34) at kernel/qeventdispatcher_unix.cpp:603
#24 0x0507d8e4 in timerSourceDispatch (source=0x82e5a00) at kernel/qeventdispatcher_glib.cpp:184
#25 0x069c15e5 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#26 0x069c52d8 in ?? () from /lib/libglib-2.0.so.0
#27 0x069c54b8 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#28 0x0507d5d5 in QEventDispatcherGlib::processEvents (this=0x82cdb60, flags=...) at kernel/qeventdispatcher_glib.cpp:412
#29 0x075f2135 in QGuiEventDispatcherGlib::processEvents (this=0x82cdb60, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#30 0x05050059 in QEventLoop::processEvents (this=0xbfb07744, flags=) at kernel/qeventloop.cpp:149
#31 0x050504aa in QEventLoop::exec (this=0xbfb07744, flags=...) at kernel/qeventloop.cpp:201
#32 0x0505469f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#33 0x07532577 in QApplication::exec () at kernel/qapplication.cpp:3579
#34 0x00cb39e9 in kdemain (argc=6, argv=0xbfb07c84) at ../../../apps/keditbookmarks/main.cpp:204
#35 0x0804860b in main (argc=6, argv=0xbfb07c84) at keditbookmarks_dummy.cpp:3

This bug may be a duplicate of or related to bug 172743.

Possible duplicates by query: bug 172743.

Reported using DrKonqi
Comment 1 Christoph Feck 2010-10-19 03:57:14 UTC
*** Bug 243212 has been marked as a duplicate of this bug. ***
Comment 2 Andrew Crouthamel 2018-10-29 22:29:22 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2018-11-13 14:25:43 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Bug Janitor Service 2018-11-28 04:54:36 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!