Bug 640392

Summary: [abrt] xfce4-xkb-plugin-0.5.3.3-3.fc13: raise: Process /usr/libexec/xfce4/panel-plugins/xfce4-xkb-plugin was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Martin Edlman <martin.edlman>
Component: xfce4-xkb-pluginAssignee: Christoph Wickert <christoph.wickert>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: christoph.wickert
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:99b68d15c121477c4c05a1865b45b461e326b43d
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-10-05 22:31:26 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 Martin Edlman 2010-10-05 18:03:53 UTC 
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/xfce4/panel-plugins/xfce4-xkb-plugin socket_id 33554465 name xkb-plugin id 12840970470 display_name 'Rozlo\xc5\xbeen\xc3\xad kl\xc3\xa1vesnice' size 64 screen_position 8
component: xfce4-xkb-plugin
crash_function: raise
executable: /usr/libexec/xfce4/panel-plugins/xfce4-xkb-plugin
kernel: 2.6.34.7-56.fc13.x86_64
package: xfce4-xkb-plugin-0.5.3.3-3.fc13
rating: 4
reason: Process /usr/libexec/xfce4/panel-plugins/xfce4-xkb-plugin was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
time: 1286301305
uid: 500

How to reproduce
-----
1. Nothing special - this time I run grip and xfce4-xkb-plugin crashed.
When I tried to add it again to panel it crashed immediatelly.
I was able to add it back to panel only after logout/login.
Sometime it crashed when running other apps (not grip).
Comment 1 Martin Edlman 2010-10-05 18:03:55 UTC 
Created attachment 451740 [details]
File: backtrace
Comment 2 Christoph Wickert 2010-10-05 22:31:26 UTC 

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