Bug 576289 - [abrt] crash in xfce4-clipman-plugin-1.1.3-2.fc13: Process /usr/libexec/xfce4/panel-plugins/xfce4-clipman-plugin was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in xfce4-clipman-plugin-1.1.3-2.fc13: Process /usr/libexec/xfce4...
Keywords:
Status: CLOSED DUPLICATE of bug 574899
Alias: None
Product: Fedora
Classification: Fedora
Component: xfce4-clipman-plugin
Version: rawhide
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Christoph Wickert
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:ff928ae4cb5481439f37d7b55b0...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-03-23 18:05 UTC by Pavel Alexeev
Modified: 2010-03-23 20:07 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-03-23 20:07:40 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (24.52 KB, text/plain)
2010-03-23 18:05 UTC, Pavel Alexeev 		no flags Details
View All

Description Pavel Alexeev 2010-03-23 18:05:18 UTC 
abrt 1.0.8 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/libexec/xfce4/panel-plugins/xfce4-clipman-plugin socket_id 25165859 name xfce4-clipman-plugin id 126850739910 display_name '\xd0\x9c\xd0\xb5\xd0\xbd\xd0\xb5\xd0\xb4\xd0\xb6\xd0\xb5\xd1\x80 \xd0\xb1\xd1\x83\xd1\x84\xd0\xb5\xd1\x80\xd0\xb0 \xd0\xbe\xd0\xb1\xd0\xbc\xd0\xb5\xd0\xbd\xd0\xb0 (Clipman)' size 28 screen_position 11
component: xfce4-clipman-plugin
executable: /usr/libexec/xfce4/panel-plugins/xfce4-clipman-plugin
kernel: 2.6.33-1.fc13.i686
package: xfce4-clipman-plugin-1.1.3-2.fc13
rating: 4
reason: Process /usr/libexec/xfce4/panel-plugins/xfce4-clipman-plugin was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Rawhide)
Comment 1 Pavel Alexeev 2010-03-23 18:05:24 UTC 
Created attachment 402109 [details]
File: backtrace
Comment 2 Christoph Wickert 2010-03-23 20:07:40 UTC 
This is a duplicate of the bug you filed 5 days ago,

*** This bug has been marked as a duplicate of bug 574899 ***
Note You need to log in before you can comment on or make changes to this bug.