Application: karbon (2.4 Beta 6) KDE Platform Version: 4.7.4 (4.7.4) Qt Version: 4.7.4 Operating System: Linux 3.0.0-16-generic x86_64 Distribution: Ubuntu 11.10 -- Information about the crash: - What I was doing when the application crashed: I was trying to edit one SVG image... trying to change the color of some vectorized lines. When I tryed to change the palette (the color list below the page?) Karbon Crashed -- Backtrace: Application: Karbon14 (karbon), signal: Segmentation fault [Current thread is 1 (Thread 0x7f0bc705c7c0 (LWP 2917))] Thread 3 (Thread 0x7f0ba2ed9700 (LWP 2922)): #0 0xffffffffff60017b in ?? () #1 0x00007f0ba2ed89f0 in ?? () #2 0x00007fff887ff7e7 in ?? () Backtrace stopped: previous frame identical to this frame (corrupt stack?) Thread 2 (Thread 0x7f0ba1ed7700 (LWP 3632)): #0 0xffffffffff60017b in ?? () #1 0x00007f0ba1ed69f0 in ?? () #2 0x00007fff887ff7e7 in ?? () Backtrace stopped: previous frame identical to this frame (corrupt stack?) Thread 1 (Thread 0x7f0bc705c7c0 (LWP 2917)): [KCrash Handler] #6 0x00007f0bc4267d17 in KoResource::name() const () from /usr/lib/libpigmentcms.so.9 #7 0x00007f0bc66d0e71 in ?? () from /usr/lib/libkarbonui.so.9 #8 0x00007f0bc66d13a8 in ?? () from /usr/lib/libkarbonui.so.9 #9 0x00007f0bc4e3eeba in QMetaObject::activate (sender=0x604ede0, m=<optimized out>, local_signal_index=<optimized out>, argv=0x7fff8862c0d0) at kernel/qobject.cpp:3278 #10 0x00007f0bc5e9d642 in QAbstractButton::clicked (this=<optimized out>, _t1=false) at .moc/release-shared/moc_qabstractbutton.cpp:206 #11 0x00007f0bc5be31fe in QAbstractButtonPrivate::emitClicked (this=<optimized out>) at widgets/qabstractbutton.cpp:546 #12 0x00007f0bc5be453b in QAbstractButtonPrivate::click (this=0x6111460) at widgets/qabstractbutton.cpp:539 #13 0x00007f0bc5be47ac in QAbstractButton::mouseReleaseEvent (this=0x604ede0, e=0x7fff8862c7f0) at widgets/qabstractbutton.cpp:1121 #14 0x00007f0bc5ca139a in QToolButton::mouseReleaseEvent (this=<optimized out>, e=<optimized out>) at widgets/qtoolbutton.cpp:721 #15 0x00007f0bc587ccea in QWidget::event (this=0x604ede0, event=0x7fff8862c7f0) at kernel/qwidget.cpp:8295 #16 0x00007f0bc582c474 in notify_helper (e=0x7fff8862c7f0, receiver=0x604ede0, this=0x1a73b00) at kernel/qapplication.cpp:4486 #17 QApplicationPrivate::notify_helper (this=0x1a73b00, receiver=0x604ede0, e=0x7fff8862c7f0) at kernel/qapplication.cpp:4458 #18 0x00007f0bc5831cbb in QApplication::notify (this=<optimized out>, receiver=0x604ede0, e=0x7fff8862c7f0) at kernel/qapplication.cpp:4047 #19 0x00007f0bc2f4e466 in KApplication::notify (this=0x7fff8862d420, receiver=0x604ede0, event=0x7fff8862c7f0) at ../../kdeui/kernel/kapplication.cpp:311 #20 0x00007f0bc4e2bafc in QCoreApplication::notifyInternal (this=0x7fff8862d420, receiver=0x604ede0, event=0x7fff8862c7f0) at kernel/qcoreapplication.cpp:787 #21 0x00007f0bc582d442 in sendEvent (event=<optimized out>, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215 #22 QApplicationPrivate::sendMouseEvent (receiver=0x604ede0, event=0x7fff8862c7f0, alienWidget=0x604ede0, nativeWidget=0x6255a10, buttonDown=0x604ede0, lastMouseReceiver=..., spontaneous=true) at kernel/qapplication.cpp:3146 #23 0x00007f0bc58ac9d5 in QETWidget::translateMouseEvent (this=0x6255a10, event=<optimized out>) at kernel/qapplication_x11.cpp:4571 #24 0x00007f0bc58ab94e in QApplication::x11ProcessEvent (this=0x7fff8862d420, event=0x7fff8862d010) at kernel/qapplication_x11.cpp:3693 #25 0x00007f0bc58d44a2 in x11EventSourceDispatch (s=0x1a70920, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146 #26 0x00007f0bc08d8a5d in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #27 0x00007f0bc08d9258 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #28 0x00007f0bc08d9429 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #29 0x00007f0bc4e56ed6 in QEventDispatcherGlib::processEvents (this=0x1976f40, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:422 #30 0x00007f0bc58d410e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=<optimized out>) at kernel/qguieventdispatcher_glib.cpp:204 #31 0x00007f0bc4e2acf2 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149 #32 0x00007f0bc4e2aef7 in QEventLoop::exec (this=0x7fff8862d3e0, flags=...) at kernel/qeventloop.cpp:201 #33 0x00007f0bc4e2f789 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1064 #34 0x00007f0bc6c89d95 in kdemain () from /usr/lib/kde4/libkdeinit/libkdeinit4_karbon.so #35 0x00007f0bc690b30d in __libc_start_main (main=0x400630, argc=2, ubp_av=0x7fff8862d5b8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff8862d5a8) at libc-start.c:226 #36 0x0000000000400661 in _start () Reported using DrKonqi
Created attachment 68963 [details] the file I was working with
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!
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!
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!