Bug 176055 - plasmoid does not work
Summary: plasmoid does not work
Status: RESOLVED NOT A BUG
Alias: None
Product: plasma4
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-11-25 12:31 UTC by Herbivor
Modified: 2008-11-28 18:51 UTC (History)
5 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Herbivor 2008-11-25 12:31:32 UTC
Version:            (using KDE 3.5.10)
OS:                Linux
Installed from:    Ubuntu Packages

Application : Espace de travail Plasma (plasma), signal SIGSEGV
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb558e6c0 (LWP 5637)]
[New Thread 0xb1c2bb90 (LWP 5831)]
[New Thread 0xb25c9b90 (LWP 5761)]
[New Thread 0xb2dcab90 (LWP 5645)]
[New Thread 0xb3892b90 (LWP 5644)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6  0xb6ca5a4c in QWidgetPrivate::setMinimumSize_helper ()
   from /usr/lib/libQtGui.so.4
#7  0xb6cadb56 in QWidget::setMinimumSize () from /usr/lib/libQtGui.so.4
#8  0xb3ae31b3 in ?? () from /usr/lib/kde4/plasma_applet_systemtray.so
#9  0xb6cc98ed in QApplication::x11ProcessEvent () from /usr/lib/libQtGui.so.4
#10 0xb6cf47ea in ?? () from /usr/lib/libQtGui.so.4
#11 0xb5a1f6f8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#12 0xb5a22da3 in ?? () from /usr/lib/libglib-2.0.so.0
#13 0xb5a22f61 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#14 0xb76fb478 in QEventDispatcherGlib::processEvents ()
   from /usr/lib/libQtCore.so.4
#15 0xb6cf3ee5 in ?? () from /usr/lib/libQtGui.so.4
#16 0xb76cf52a in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#17 0xb76cf6ea in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#18 0xb76d1da5 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#19 0xb6c59767 in QApplication::exec () from /usr/lib/libQtGui.so.4
#20 0xb804a491 in kdemain () from /usr/lib/libkdeinit4_plasma.so
#21 0x080485b2 in _start ()
#0  0xb8090430 in __kernel_vsyscall ()
Comment 1 FiNeX 2008-11-25 13:32:51 UTC
Hi! How did you make plasma crashing? If you can reproduce the crash, you should install the debug enabled packages and provide a new backtrace. Read this page for the instructions:

http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

Thanks!
Comment 2 Christophe Marin 2008-11-28 12:17:20 UTC
"Version: (using KDE 3.5.10)"

Are you really trying to make plasma work with KDE 3.5.10 ?


Comment 3 Michael Leupold 2008-11-28 12:18:15 UTC
Are you running plasma on KDE3? If so, did you have the kicker systray and the plasma one running at the same time? If so, try removing the systray from kicker.

On a sidenote: I don't think running plasma on KDE3 is supported.
Comment 4 Herbivor 2008-11-28 13:38:53 UTC
Sorry, it's KDE 4.1 ^^
Comment 5 Aaron J. Seigo 2008-11-28 18:51:03 UTC
systemtray related crash in 4.1 is unfortunate, but not useful anymore as it's been completely re-written for 4.2.

Herbivor: in future, please give more specifics in crash reports, such as when it crashes (at start? while it's running?), what (if anything) is happening when it crashes, whether it is repeatable or just happens once in a while, etc...