Bug 767036
| Summary: | [abrt] anjuta-3.2.0-1.fc16: g_file_equal: Process /usr/bin/anjuta was killed by signal 11 (SIGSEGV) | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Insang Ryu <ryu.insang> | ||||||||||||
| Component: | anjuta | Assignee: | Cosimo Cecchi <ccecchi> | ||||||||||||
| Status: | CLOSED DUPLICATE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||
| Priority: | unspecified | ||||||||||||||
| Version: | 16 | CC: | bugs.michael, ccecchi, jhs, mclasen, rpandit | ||||||||||||
| Target Milestone: | --- | ||||||||||||||
| Target Release: | --- | ||||||||||||||
| Hardware: | x86_64 | ||||||||||||||
| OS: | Unspecified | ||||||||||||||
| Whiteboard: | abrt_hash:4e6df95082b60ad037362d0464d8d2ff5801956d | ||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||
| Clone Of: | Environment: | ||||||||||||||
| Last Closed: | 2011-12-16 11:00: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
Insang Ryu
2011-12-13 03:02:22 UTC
Created attachment 546043 [details]
File: dso_list
Created attachment 546044 [details]
File: build_ids
Created attachment 546045 [details]
File: xsession_errors
Created attachment 546046 [details]
File: maps
Created attachment 546047 [details]
File: backtrace
Could you give some details what you did when anjuta crashed? Thanks! I believe that I was adding a targets. Thanks! gtk3-3.2.2-4.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/gtk3-3.2.2-4.fc16 *** This bug has been marked as a duplicate of bug 766352 *** |