Bug 568479

Summary: [abrt] crash in kdebase-workspace-4.4.0-7.fc12: Process /usr/bin/plasma-desktop was killed by signal 7 (SIGBUS)
Product: [Fedora] Fedora Reporter: Mohamed M. Hagag <mohamedhagag1981>
Component: kdebase-workspaceAssignee: Than Ngo <than>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: fedora, fedora, jreznik, kevin, lorenzo, ltinkl, prower2000, rdieter, smparrish, than
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:7584a82a4580c13b2989f674b6a1a3d46f2b1504
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-02-26 09:59:31 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Mohamed M. Hagag 2010-02-25 19:50:09 UTC 
abrt 1.0.7 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/plasma-desktop
component: kdebase-workspace
executable: /usr/bin/plasma-desktop
kernel: 2.6.31.12-174.2.22.fc12.x86_64
package: kdebase-workspace-4.4.0-7.fc12
rating: 4
reason: Process /usr/bin/plasma-desktop was killed by signal 7 (SIGBUS)
release: Fedora release 12 (Constantine)
Comment 1 Mohamed M. Hagag 2010-02-25 19:50:12 UTC 
Created attachment 396374 [details]
File: backtrace
Comment 2 prower2000 2010-02-25 22:22:03 UTC 
This one occurs for me if I have the weather plasmoid running, then disable and re-enable networking via nm-applet in KDE 4.4.0. If I turn the weather plasmoid off I don't see the crash any more if I take the above steps.
Comment 3 prower2000 2010-02-25 22:22:36 UTC 
Incidentally I'm experiencing this bug with the 32-bit version, not the 64-bit version of F12 and KDE.
Comment 4 Kevin Kofler 2010-02-26 09:59:31 UTC 
Same KPixmapCache issue.

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