Bug 766901
Summary: | [abrt] gedit-3.2.3-1.fc16: lookup_iface_entry_I: Process /usr/bin/gedit was killed by signal 11 (SIGSEGV) | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | tomfleniken | ||||||||||
Component: | gedit | Assignee: | Ray Strode [halfline] <rstrode> | ||||||||||
Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
Severity: | unspecified | Docs Contact: | |||||||||||
Priority: | unspecified | ||||||||||||
Version: | 16 | CC: | bugs.michael, rstrode | ||||||||||
Target Milestone: | --- | ||||||||||||
Target Release: | --- | ||||||||||||
Hardware: | x86_64 | ||||||||||||
OS: | Unspecified | ||||||||||||
Whiteboard: | abrt_hash:fced3f8504eff4e015ec8ca19f70ee3f47507505 | ||||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||||
Doc Text: | Story Points: | --- | |||||||||||
Clone Of: | Environment: | ||||||||||||
Last Closed: | 2011-12-16 22:19:20 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
tomfleniken
2011-12-12 19:13:11 UTC
Created attachment 545883 [details]
File: dso_list
Created attachment 545884 [details]
File: maps
Created attachment 545885 [details]
File: smolt_data
Created attachment 545886 [details]
File: backtrace
Had it happen to me again today 2011-12-13 but I just wanted to note nautilus had not been opened today so that counts that out. Your quote of xsession-errors is related to a gtk3 file chooser crash. Try the current test-update, which fixes that: https://admin.fedoraproject.org/updates/gtk3-3.2.2-4.fc16 The backtrace of in this ticket is a little bit different, but passes the same code path. confirmed updated gtk3-3.2.2-4.fc16 fixed the issue. Thanks. *** This bug has been marked as a duplicate of bug 766352 *** |