Bug 554018
Summary: | [abrt] crash in scribes-0.3.3.3-5.fc12 | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | jIoSEA3lWwiEaAVy3 | ||||||
Component: | scribes | Assignee: | Peter Gordon <peter> | ||||||
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
Severity: | medium | Docs Contact: | |||||||
Priority: | low | ||||||||
Version: | 12 | CC: | fedora, iptin, it_rom, ivanpacheko, jholton, josephomorrow, linuxnow, mbreitfe, michael, mothlight, peter, tncarrolls, wellspring3 | ||||||
Target Milestone: | --- | ||||||||
Target Release: | --- | ||||||||
Hardware: | x86_64 | ||||||||
OS: | Linux | ||||||||
Whiteboard: | abrt_hash:cdb7f17b96b5432d67cf4a24480ead26f4f8f038 | ||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | Environment: | ||||||||
Last Closed: | 2010-12-04 00:38:18 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
jIoSEA3lWwiEaAVy3
2010-01-10 01:05:21 UTC
Created attachment 382733 [details]
File: backtrace
Created attachment 387221 [details]
File that crashes Scribe
Right click file in Nautilus, open file with Scribe, will always crash.
How to reproduce ----- 1. It Autoloaded text when I opened a text file, then crashed on closing 2. 3. Comment ----- don't know *** Bug 594067 has been marked as a duplicate of this bug. *** Package: scribes-0.3.3.3-5.fc12 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.opened a file within the file roller from smb 2. 3. This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. 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 '12'. 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 12'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 12 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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 I know more recent updates in Fedora 13 also crashed when trying to open files with a wide character set. However, in Fedora 14, I can't even get scribes to start up. $ rpm -q scribes scribes-0.3.3.3-6.fc14.noarch Running it from the command line (either with or without a file), the program never comes up and in the process monitor, it just shows moving towards 100% CPU usage. $ scribes ** (scribes:10065): WARNING **: Failed to send buffer ** (scribes:10065): WARNING **: Failed to send buffer from top: 10065 nice 20 0 49540 16m 9608 R 67.7 0.4 0:35.18 python Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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. |