Bug 641649 - [abrt] kdebase-workspace-4.4.5-1.fc12: TaskManager::Task::icon: Process /usr/bin/plasma-desktop was killed by signal 11 (SIGSEGV)
Summary: [abrt] kdebase-workspace-4.4.5-1.fc12: TaskManager::Task::icon: Process /usr/...
Keywords:
Status: CLOSED DUPLICATE of bug 637412
Alias: None
Product: Fedora
Classification: Fedora
Component: kde-plasma-daisy
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Julian Aloofi
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:e605a1dba7718cc41c6cc125656...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-10-09 23:41 UTC by Niels Mayer
Modified: 2010-10-10 12:59 UTC (History)
11 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-10-10 12:59:23 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (39.28 KB, text/plain)
2010-10-09 23:41 UTC, Niels Mayer
no flags Details

Description Niels Mayer 2010-10-09 23:41:40 UTC
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: plasma-desktop --nocrashhandler
component: kdebase-workspace
crash_function: TaskManager::Task::icon
executable: /usr/bin/plasma-desktop
kernel: 2.6.32.21-168.fc12.x86_64
package: kdebase-workspace-4.4.5-1.fc12
rating: 4
reason: Process /usr/bin/plasma-desktop was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)
time: 1286666850
uid: 571

comment
-----
I was able to reproduce this problem enough times to implicate "daisy". I am uninstalling kde-plasma-daisy-0.0.4.23-2.fc12.x86_64
as a result as it is the source of these problems.

How to reproduce
-----
1. Installed and tried out kde-plasma-daisy-0.0.4.23-2.fc12.x86_64
2. Many actions in "daisy" seem to cause it to crash and take the entire desktop with it
3. Blank screen is result. Alt-F2 is responsive, but ultimately logout/login required to get back to work.

Comment 1 Niels Mayer 2010-10-09 23:41:44 UTC
Created attachment 452558 [details]
File: backtrace

Comment 2 Julian Aloofi 2010-10-10 12:59:23 UTC
Thanks for reporting, this looks similar to bug 637412 .
If you want to keep updated about the status, just add yourself to its CC list.
I will also forward the reports to upstream.

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


Note You need to log in before you can comment on or make changes to this bug.