Bug 810479
Summary: | [abrt] gnome-shell-3.2.2.1-1.fc16: _int_free: Process /usr/bin/gnome-shell was killed by signal 11 (SIGSEGV) | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Tim Zorn <timothy.zorn> | ||||||||||||||
Component: | gnome-shell | Assignee: | Owen Taylor <otaylor> | ||||||||||||||
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||
Severity: | unspecified | Docs Contact: | |||||||||||||||
Priority: | unspecified | ||||||||||||||||
Version: | 16 | CC: | maxamillion, otaylor, samkraju, walters | ||||||||||||||
Target Milestone: | --- | ||||||||||||||||
Target Release: | --- | ||||||||||||||||
Hardware: | x86_64 | ||||||||||||||||
OS: | Unspecified | ||||||||||||||||
Whiteboard: | abrt_hash:e0da3c0d27c97fce53601679751cee8435509ae5 | ||||||||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||
Doc Text: | Story Points: | --- | |||||||||||||||
Clone Of: | Environment: | ||||||||||||||||
Last Closed: | 2012-04-06 13:59:46 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
Tim Zorn
2012-04-06 10:43:28 UTC
Created attachment 575698 [details]
File: dso_list
Created attachment 575699 [details]
File: build_ids
Created attachment 575700 [details]
File: maps
Created attachment 575701 [details]
File: xsession_errors
Created attachment 575702 [details]
File: var_log_messages
Created attachment 575703 [details]
File: backtrace
Again this is a "prevous memory corruption" backtrace - I'm dupping it on bug 810426, on the assumption that there's just one frequent memory corruption crasher that is occurring with your configuration. *** This bug has been marked as a duplicate of bug 810426 *** |