Bug 225418 - add plasma crash kdeinit change background of notes to different color than theme
Summary: add plasma crash kdeinit change background of notes to different color than t...
Status: RESOLVED DUPLICATE of bug 202378
Alias: None
Product: plasma4
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-03 18:11 UTC by HELLth
Modified: 2010-02-04 02:04 UTC (History)
2 users (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 HELLth 2010-02-03 18:11:07 UTC
Application that crashed: plasma-desktop
Version of the application: 0.3
KDE Version: 4.3.4 (KDE 4.3.4)
Qt Version: 4.5.3
Operating System: Linux 2.6.32-trunk-amd64 x86_64
Distribution: Debian GNU/Linux 5.0.3 (lenny)

What I was doing when the application crashed:
I've added Plasma notes on desktop and when I changed background color of notes diffrent than theme and clicked okay plasma crashed. Than it has restarted and worked well, but didn't change the bg color of notes.

 -- Backtrace:
Application: Plasma Workspace (kdeinit4), signal: Segmentation fault
The current source language is "auto; currently c".
[Current thread is 1 (Thread 0x7fdf2baf4750 (LWP 3993))]

Thread 2 (Thread 0x7fdf080d5910 (LWP 3994)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:261
#1  0x00007fdf2b531499 in QWaitConditionPrivate::wait (this=0x26c37e0, mutex=0x26c37d8, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:87
#2  QWaitCondition::wait (this=0x26c37e0, mutex=0x26c37d8, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:159
#3  0x00007fdf2791f3b4 in QHostInfoAgent::run (this=0x26c37c0) at kernel/qhostinfo.cpp:260
#4  0x00007fdf2b5304a5 in QThreadPrivate::start (arg=0x26c37c0) at thread/qthread_unix.cpp:188
#5  0x00007fdf2825b73a in start_thread (arg=<value optimized out>) at pthread_create.c:300
#6  0x00007fdf28e256dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#7  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7fdf2baf4750 (LWP 3993)):
[KCrash Handler]
#5  QObject::property (this=0x1, name=0x7fdef67f00f6 "color") at kernel/qobject.cpp:3292
#6  0x00007fdef67e9a57 in ?? () from /usr/lib/kde4/plasma_applet_notes.so
#7  0x00007fdef67e9f64 in ?? () from /usr/lib/kde4/plasma_applet_notes.so
#8  0x00007fdf2b62adf2 in QMetaObject::activate (sender=0x6f7fce0, from_signal_index=<value optimized out>, to_signal_index=45, argv=0x0) at kernel/qobject.cpp:3112
#9  0x00007fdf2a162a68 in KDialog::slotButtonClicked (this=0x6f7fce0, button=4) at ../../kdeui/dialogs/kdialog.cpp:853
#10 0x00007fdf2a164c79 in KDialog::qt_metacall (this=0x6f7fce0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7ffff62746a0) at ./kdialog.moc:184
#11 0x00007fdf2a218980 in KPageDialog::qt_metacall (this=0x7ffff6274250, _c=QMetaObject::ReadProperty, _id=-159448842, _a=0x0) at ./kpagedialog.moc:64
#12 0x00007fdf2a151d30 in KConfigDialog::qt_metacall (this=0x7ffff6274250, _c=QMetaObject::ReadProperty, _id=-159448842, _a=0x0) at ./kconfigdialog.moc:78
#13 0x00007fdf2b62adf2 in QMetaObject::activate (sender=0x4bf5a88, from_signal_index=<value optimized out>, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3112
#14 0x00007fdf2b62da6e in QSignalMapper::mapped (this=0x7ffff6274250, _t1=4) at .moc/release-shared/moc_qsignalmapper.cpp:95
#15 0x00007fdf2b62e310 in QSignalMapper::map (this=0x4bf5a88, sender=0x31a3770) at kernel/qsignalmapper.cpp:266
#16 0x00007fdf2b62eef0 in QSignalMapper::qt_metacall (this=0x4bf5a88, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7ffff6274820) at .moc/release-shared/moc_qsignalmapper.cpp:81
#17 0x00007fdf2b62adf2 in QMetaObject::activate (sender=0x31a3770, from_signal_index=<value optimized out>, to_signal_index=30, argv=0x0) at kernel/qobject.cpp:3112
#18 0x00007fdf29ba8037 in QAbstractButton::clicked (this=0x7ffff6274250, _t1=false) at .moc/release-shared/moc_qabstractbutton.cpp:200
#19 0x00007fdf2990730b in QAbstractButtonPrivate::emitClicked (this=0x21abe00) at widgets/qabstractbutton.cpp:543
#20 0x00007fdf29908f1b in QAbstractButtonPrivate::click (this=0x21abe00) at widgets/qabstractbutton.cpp:536
#21 0x00007fdf29909175 in QAbstractButton::mouseReleaseEvent (this=0x31a3770, e=0x7ffff6275170) at widgets/qabstractbutton.cpp:1115
#22 0x00007fdf295e637f in QWidget::event (this=0x31a3770, event=0x7ffff6275170) at kernel/qwidget.cpp:7554
#23 0x00007fdf2959601d in QApplicationPrivate::notify_helper (this=0x1e650d0, receiver=0x31a3770, e=0x7ffff6275170) at kernel/qapplication.cpp:4065
#24 0x00007fdf2959e7ca in QApplication::notify (this=<value optimized out>, receiver=0x31a3770, e=0x7ffff6275170) at kernel/qapplication.cpp:3767
#25 0x00007fdf2a1ede06 in KApplication::notify (this=0x1e5be90, receiver=0x31a3770, event=0x7ffff6275170) at ../../kdeui/kernel/kapplication.cpp:302
#26 0x00007fdf2b615c9c in QCoreApplication::notifyInternal (this=0x1e5be90, receiver=0x31a3770, event=0x7ffff6275170) at kernel/qcoreapplication.cpp:610
#27 0x00007fdf2959da78 in QCoreApplication::sendSpontaneousEvent (receiver=0x31a3770, event=0x7ffff6275170, alienWidget=0x31a3770, nativeWidget=0x6f7fce0, buttonDown=<value optimized out>, 
    lastMouseReceiver=...) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:216
#28 QApplicationPrivate::sendMouseEvent (receiver=0x31a3770, event=0x7ffff6275170, alienWidget=0x31a3770, nativeWidget=0x6f7fce0, buttonDown=<value optimized out>, lastMouseReceiver=...)
    at kernel/qapplication.cpp:2924
#29 0x00007fdf29606659 in QETWidget::translateMouseEvent (this=0x6f7fce0, event=<value optimized out>) at kernel/qapplication_x11.cpp:4411
#30 0x00007fdf2960540f in QApplication::x11ProcessEvent (this=0x1e5be90, event=0x7ffff6276b40) at kernel/qapplication_x11.cpp:3552
#31 0x00007fdf2962d76c in x11EventSourceDispatch (s=0x1e68630, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#32 0x00007fdf284ac90e in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#33 0x00007fdf284b02c8 in ?? () from /lib/libglib-2.0.so.0
#34 0x00007fdf284b03f0 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#35 0x00007fdf2b63e39c in QEventDispatcherGlib::processEvents (this=0x1dd6220, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:407
#36 0x00007fdf2962cf1f in QGuiEventDispatcherGlib::processEvents (this=0x7ffff6274250, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#37 0x00007fdf2b614562 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#38 0x00007fdf2b614934 in QEventLoop::exec (this=0x7ffff6276e70, flags=...) at kernel/qeventloop.cpp:201
#39 0x00007fdf2b616ba4 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#40 0x00007fdf201a82af in kdemain (argc=<value optimized out>, argv=<value optimized out>) at ../../../../plasma/shells/desktop/main.cpp:50
#41 0x0000000000406e9e in launch (argc=1, _name=<value optimized out>, args=<value optimized out>, cwd=<value optimized out>, envc=0, envs=<value optimized out>, reset_env=false, tty=0x0, 
    avoid_loops=false, startup_id_str=0x40a057 "0") at ../../kinit/kinit.cpp:677
#42 0x0000000000407aad in handle_launcher_request (sock=7, who=<value optimized out>) at ../../kinit/kinit.cpp:1169
#43 0x0000000000407f91 in handle_requests (waitForPid=0) at ../../kinit/kinit.cpp:1362
#44 0x00000000004086c6 in main (argc=2, argv=<value optimized out>, envp=<value optimized out>) at ../../kinit/kinit.cpp:1793
The current source language is "auto; currently asm".
The current source language is "auto; currently c".

This bug may be a duplicate of or related to bug 225265

Reported using DrKonqi
Comment 1 Aaron J. Seigo 2010-02-03 18:59:20 UTC
"when I changed background color of notes diffrent than theme"

can you describe what you mean by this more clearly? or perhaps attach a screenshot to this bug report showing the configuration dialog right before you hit "ok"?
Comment 2 Dario Andres 2010-02-04 02:04:06 UTC
BTW, this is being tracked at bug 202378, and so far there are no 4.4/4.5 cases...
Regards

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