Bug 639005 - [abrt] crash in gnome-utils-1:2.30.0-1.fc13: __strlen_sse2: Process /usr/bin/gnome-screenshot was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in gnome-utils-1:2.30.0-1.fc13: __strlen_sse2: Process /usr/bin/...
Keywords:
Status: CLOSED DUPLICATE of bug 638940
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-utils
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:3788c5dd87ed1ae4bf0b44712f6...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-30 15:37 UTC by two4two
Modified: 2010-10-26 15:09 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-10-26 15:09:29 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (21.11 KB, text/plain)
2010-09-30 15:37 UTC, two4two 		no flags Details
View All

Description two4two 2010-09-30 15:37:20 UTC 
abrt 1.1.0 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: gnome-screenshot --window
comment: This same library and same part of the program fails in multiple applications.  I believe it is a compatibility issue because I have both i686 and x86_64 versions of the library on this PC.  And this library is in both /lib and /lib64.  And it comes from the fedora updates repo.
component: gnome-utils
crash_function: __strlen_sse2
executable: /usr/bin/gnome-screenshot
global_uuid: 3788c5dd87ed1ae4bf0b44712f64587ba705fa33
kernel: 2.6.33.3-85.fc13.x86_64
package: gnome-utils-1:2.30.0-1.fc13
rating: 4
reason: Process /usr/bin/gnome-screenshot was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1.  Simply try to "take screenshot"  will fail
2.
3.
Comment 1 two4two 2010-09-30 15:37:22 UTC 
Created attachment 450796 [details]
File: backtrace
Comment 2 Ray Strode [halfline] 2010-10-26 15:09:29 UTC 

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