Summary: | Can't create Icons for Link to Application | ||
---|---|---|---|
Product: | [I don't know] kde | Reporter: | james tate <mickeyboa> |
Component: | general | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | christophe, mklapetek, mumismo |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Fedora RPMs | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
dbg file
crash from Fedora 10 Preview x86_64, KDE 4.1.2 |
Description
james tate
2008-11-06 23:47:54 UTC
Created attachment 28376 [details]
dbg file
This is a dbg file.
Created attachment 28396 [details]
crash from Fedora 10 Preview x86_64, KDE 4.1.2
Comment on attachment 28396 [details]
crash from Fedora 10 Preview x86_64, KDE 4.1.2
I'm confirming this bug on Fedora 10 Preview x86_64, KDE version 4.1.2, after opening the icon select dialog, the icons are loading and then it crashes.
Copy/Paste from comment #1 (the others backtraces are useless without the debug packages) : Application: Plasma Workspace (plasma), signal SIGSEGV (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0xb8084770 (LWP 2686)] [New Thread 0xb5ee0b90 (LWP 2692)] [New Thread 0xb68e1b90 (LWP 2691)] [KCrash handler] #6 0x0766e7c7 in QSvgHandler::characters (this=<value optimized out>, str=<value optimized out>) at qsvghandler.cpp:3569 #7 0x07678829 in QSvgHandler::parse (this=<value optimized out>) at qsvghandler.cpp:3388 #8 0x07678a06 in QSvgHandler (this=<value optimized out>, data=<value optimized out>) at qsvghandler.cpp:3362 #9 0x0768930c in QSvgTinyDocument::load (contents=<value optimized out>) at qsvgtinydocument.cpp:89 #10 0x0768af9a in QSvgRenderer::load (this=<value optimized out>, contents=<value optimized out>) at qsvgrenderer.cpp:315 #11 0x074febc9 in KSvgRenderer::load (this=<value optimized out>, contents=<value optimized out>) at /usr/src/debug/kdelibs-4.1.2/kdeui/util/ksvgrenderer.cpp:68 #12 0x074fec71 in KSvgRenderer::load (this=<value optimized out>, filename=<value optimized out>) at /usr/src/debug/kdelibs-4.1.2/kdeui/util/ksvgrenderer.cpp:50 #13 0x074fee33 in KSvgRenderer (this=) at /usr/src/debug/kdelibs-4.1.2/kdeui/util/ksvgrenderer.cpp:35 #14 0x07919d05 in KIconCanvas::KIconCanvasPrivate::_k_slotLoadFiles ( this=<value optimized out>) at /usr/src/debug/kdelibs-4.1.2/kio/kfile/kicondialog.cpp:150 #15 0x0791a31e in KIconCanvas::qt_metacall (this=<value optimized out>, _c=<value optimized out>, _id=<value optimized out>, _a=<value optimized out>) at /usr/src/debug/kdelibs-4.1.2/i386-redhat-linux-gnu/kio/kicondialog.moc:82 #16 0x0077e690 in QMetaObject::activate (sender=<value optimized out>, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv=<value optimized out>) at kernel/qobject.cpp:3031 #17 0x0077f412 in QMetaObject::activate (sender=<value optimized out>, m=<value optimized out>, local_signal_index=<value optimized out>, argv=) at kernel/qobject.cpp:3101 #18 0x007b9397 in QTimer::timeout (this=) at .moc/release-shared/moc_qtimer.cpp:126 #19 0x0078503e in QTimer::timerEvent (this=<value optimized out>, e=<value optimized out>) at kernel/qtimer.cpp:257 #20 0x0077916f in QObject::event (this=<value optimized out>, e=<value optimized out>) at kernel/qobject.cpp:1120 #21 0x069a362c in QApplicationPrivate::notify_helper ( this=<value optimized out>, receiver=<value optimized out>, e=<value optimized out>) at kernel/qapplication.cpp:3803 #22 0x069ab46e in QApplication::notify (this=<value optimized out>, receiver=<value optimized out>, e=<value optimized out>) at kernel/qapplication.cpp:3393 #23 0x0748731d in KApplication::notify (this=<value optimized out>, receiver=<value optimized out>, event=<value optimized out>) at /usr/src/debug/kdelibs-4.1.2/kdeui/kernel/kapplication.cpp:311 #24 0x00769a91 in QCoreApplication::notifyInternal ( this=<value optimized out>, receiver=<value optimized out>, event=<value optimized out>) at kernel/qcoreapplication.cpp:587 #25 0x00797921 in QCoreApplication::sendEvent () at ../../src/corelib/kernel/qcoreapplication.h:209 #26 QTimerInfoList::activateTimers (this=<value optimized out>) at kernel/qeventdispatcher_unix.cpp:557 #27 0x00794140 in timerSourceDispatch (source=) at kernel/qeventdispatcher_glib.cpp:160 #28 0x00c50208 in g_main_dispatch () at gmain.c:2144 #29 IA__g_main_context_dispatch (context=<value optimized out>) at gmain.c:2697 #30 0x00c538b3 in g_main_context_iterate (context=<value optimized out>, block=<value optimized out>, dispatch=<value optimized out>, self=) at gmain.c:2778 #31 0x00c53a71 in IA__g_main_context_iteration ( context=<value optimized out>, may_block=<value optimized out>) at gmain.c:2841 #32 0x00794098 in QEventDispatcherGlib::processEvents ( this=<value optimized out>, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:319 #33 0x06a3c485 in QGuiEventDispatcherGlib::processEvents (this=) at kernel/qguieventdispatcher_glib.cpp:198 #34 0x0076815a in QEventLoop::processEvents (this=<value optimized out>, flags=<value optimized out>) at kernel/qeventloop.cpp:143 #35 0x0076831a in QEventLoop::exec (this=<value optimized out>, flags=<value optimized out>) at kernel/qeventloop.cpp:194 #36 0x0076a9d5 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:845 #37 0x069a34a7 in QApplication::exec () at kernel/qapplication.cpp:3331 #38 0x00146e21 in kdemain () from /usr/lib/libkdeinit4_plasma.so #39 0x080487d2 in _start () After some (standard) fedora updates it's working again for me Attaching my kdebase versions: kdebase-workspace-4.1.2-14.fc10.x86_64 kdebase-4.1.2-5.fc10.x86_64 kdebase-libs-4.1.2-5.fc10.x86_64 kdebase-runtime-libs-4.1.2-5.fc10.x86_64 kdebase-workspace-libs-4.1.2-14.fc10.x86_64 kdebase-workspace-devel-4.1.2-14.fc10.x86_64 kdebase-runtime-4.1.2-5.fc10.x86_64 So this bug can be closed? I'd say yes as it is working for me now, but I guess that the original reporter should make that call :) The bug report can be closed . It is working as it should be Thanks Jim |