Bug 528177

Summary: [abrt] crash detected in gpodder-2.0-1.fc12
Product: [Fedora] Fedora Reporter: Matěj Cepl <mcepl>
Component: gpodderAssignee: Jef Spaleta <jspaleta>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: jspaleta, marty, mcepl
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:23e9c9e9
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-12-04 07:31:34 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 Flags
File: backtrace none

Description Matěj Cepl 2009-10-09 15:02:20 UTC
abrt detected a crash.


How to reproduce
-----
1.
2.
3.


Comment
-----
Starting gpodder

Additional information
======


Attached files
----
backtrace

cmdline
-----
/usr/bin/python /usr/bin/gpodder 


component
-----
gpodder


executable
-----
/usr/bin/gpodder


kernel
-----
2.6.31.1-58.fc12.x86_64


package
-----
gpodder-2.0-1.fc12


uuid
-----
23e9c9e9

Comment 1 Matěj Cepl 2009-10-09 15:02:23 UTC
Created attachment 364256 [details]
File: backtrace

Comment 2 Jef Spaleta 2009-10-09 17:52:04 UTC
I'm really at a loss here.  The traceback suggests that python is unable to send output to sys.stderr .   

Now I can of course wrap this call in a way that will not traceback by handling the IO exception. But I have a deeper question. Should stderr always be available for output?  And if so, why isn't it available on your system? Is this a deeper problem than gpodder?

Hmm.....

-jef

Comment 3 Matěj Cepl 2009-10-12 06:36:14 UTC
(In reply to comment #2)
> I'm really at a loss here.  The traceback suggests that python is unable to
> send output to sys.stderr .   
> 
> Now I can of course wrap this call in a way that will not traceback by handling
> the IO exception. But I have a deeper question. Should stderr always be
> available for output?  And if so, why isn't it available on your system? Is
> this a deeper problem than gpodder?

This seems to be really silly, but OTOH there must be something weird around stderr ... gpodder crashes when run from Alt+F2 dialog, but works flawlessly when running from gnome-terminal. No idea.

Comment 4 Bug Zapper 2009-11-16 13:27:25 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 5 Bug Zapper 2010-11-04 09:33:51 UTC
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

Comment 6 Bug Zapper 2010-12-04 07:31:34 UTC
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.