| Summary: | [abrt] gedit-3.2.2-1.fc16: Process /usr/bin/gedit was killed by signal 11 (SIGSEGV) | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Tomasz Sterna <tomek> | ||||||||||||||
| Component: | gedit | Assignee: | Ray Strode [halfline] <rstrode> | ||||||||||||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||
| Severity: | unspecified | Docs Contact: | |||||||||||||||
| Priority: | unspecified | ||||||||||||||||
| Version: | 16 | CC: | hpfeil, luya, renich, rstrode, sgtnasty, vdanielmo | ||||||||||||||
| Target Milestone: | --- | ||||||||||||||||
| Target Release: | --- | ||||||||||||||||
| Hardware: | x86_64 | ||||||||||||||||
| OS: | Unspecified | ||||||||||||||||
| Whiteboard: | abrt_hash:f3cc7c253aa2a09177688cc85a93f6c580ac7707 | ||||||||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||
| Last Closed: | 2013-02-13 21:52:07 UTC | Type: | --- | ||||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||||
| Documentation: | --- | CRM: | |||||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||
| Attachments: |
|
||||||||||||||||
|
Description
Tomasz Sterna
2011-11-20 22:16:18 UTC
Created attachment 534688 [details]
File: maps
Created attachment 534689 [details]
File: backtrace
It crashes when trying to save. backtrace_rating: 4 Package: gedit-3.2.5-1.fc16 OS Release: Fedora release 16 (Verne) Created attachment 555386 [details]
File: backtrace
It randomly crashes when saving. It happens a lot! backtrace_rating: 4 Package: gedit-3.2.6-1.fc16 OS Release: Fedora release 16 (Verne) Created attachment 557741 [details]
File: backtrace
Saving file. backtrace_rating: 4 Package: gedit-3.2.6-1.fc16 OS Release: Fedora release 16 (Verne) Created attachment 561338 [details]
File: backtrace
Crash occurred after saving some works. backtrace_rating: 4 Package: gedit-3.2.6-1.fc16 OS Release: Fedora release 16 (Verne) Created attachment 565986 [details]
File: backtrace
I've been working on a solution to similar gedit behaviour for a few weeks. I finally traced the problem to the gedit-plugins package. I could invoke a gedit segfault simply by opening a file with its char encoding different from the default. For example, with default encoding set to UTF-8, opening a file created with ISO-8859-1 caused gedit to appear for less than a second before vanishing with a libc segfault. Simply removing gedit-plugins restored the default behaviour of presenting a pop-up warning banner at the top of the page: "The file you opened has some invalid characters" Choose ISO-8859-1 from the menu, Retry, proceed as advertised. I also tested opening a file that contains control chars, such as a .info file with 0x1F (US - Unit Separator) at the top of each info chapter. With gedit-plugins installed, that guaranteed a segfault 11 crash. I suspect something in the python files, but have yet to test that supposition. opening one of the files in an abrt report via the reporting interface. i may have already had a gedit window open containing some files from a gvfs mount which hadn't yet been re-established following a suspend-resume. backtrace_rating: 4 Package: gedit-3.2.6-1.fc16 OS Release: Fedora release 16 (Verne) This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |