Summary: | Plasma chrashed when try to change activity | ||
---|---|---|---|
Product: | [Unmaintained] plasma4 | Reporter: | uwe.helms |
Component: | general | Assignee: | Plasma Bugs List <plasma-bugs-null> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | knut.tr |
Priority: | NOR | ||
Version First Reported In: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | New crash information added by DrKonqi |
Description
uwe.helms
2013-03-17 07:34:16 UTC
Created attachment 78392 [details]
New crash information added by DrKonqi
plasma-desktop (0.4) on KDE Platform 4.10.1 using Qt 4.8.4
- What I was doing when the application crashed:
Set up new activity yesterday. Logged out. Logged in today and got a default blank activity desktop. Open activity manager (red-blue-green dots near start menu). Klick on desktop icon. Plasma desktop crashes.
- Unusual behavior I noticed:
Did not get my desktop from yesterday loeded when I logged in. Several "blank" desktops available in activity manager.
- Custom settings of the application:
Had set up my desktop as GroupingDesktop with background pictures, and a selection of icons.
-- Backtrace (Reduced):
#7 0x0000003423d8f621 in QObject::disconnect (sender=0x7e31140, signal=0x0, receiver=0x205a860, method=0x0) at kernel/qobject.cpp:2887
#8 0x000000384a6582a5 in PlasmaApp::prepareContainment (this=0x205a860, containment=0x7e31140) at /usr/src/debug/kde-workspace-4.10.1/plasma/desktop/shell/plasmaapp.cpp:1133
#9 0x000000384a637385 in DesktopView::setContainment (this=0x26b5a00, containment=0x7e31140) at /usr/src/debug/kde-workspace-4.10.1/plasma/desktop/shell/desktopview.cpp:285
#10 0x000000384b5e327c in privateInit (this=0x2f14a30) at /usr/src/debug/kdelibs-4.10.1/plasma/view.cpp:71
#11 qt_static_metacall (_a=<optimized out>, _id=<optimized out>, _o=<optimized out>, _c=<optimized out>) at /usr/src/debug/kdelibs-4.10.1/x86_64-redhat-linux-gnu/plasma/view.moc:69
*** This bug has been marked as a duplicate of bug 306556 *** |