Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 980342 - [abrt] memaker-20100110-4.fc18: [Errno 2] No such file or directory: '/usr/share/doc/memaker/AUTHORS'
Summary: [abrt] memaker-20100110-4.fc18:
Alias: None
Product: Fedora
Classification: Fedora
Component: memaker
Version: 18
Hardware: i686
OS: Unspecified
Target Milestone: ---
Assignee: Ankur Sinha (FranciscoD)
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:b9e7ef49e28ac8f4bdbced1fb29...
Depends On:
TreeView+ depends on / blocked
Reported: 2013-07-02 06:33 UTC by shialeweb
Modified: 2014-02-05 23:12 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2014-02-05 23:12:42 UTC

Attachments (Terms of Use)
File: backtrace (deleted)
2013-07-02 06:33 UTC, shialeweb
no flags Details
File: environ (deleted)
2013-07-02 06:33 UTC, shialeweb
no flags Details

Description shialeweb 2013-07-02 06:33:49 UTC
Version-Release number of selected component:

Additional info:
reporter:       libreport-2.1.4
cmdline:        /usr/bin/python /usr/bin/memaker
core_backtrace: 4a865b6f837369bfd34856c4f925bdfa1c837c05 0x97 on_menuitem_about_activate /usr/lib/python2.7/site-packages/MeMaker/ -
executable:     /usr/bin/memaker
kernel:         3.9.6-200.fc18.i686
runlevel:       N 5
uid:            1000

Truncated backtrace: [Errno 2] No such file or directory: '/usr/share/doc/memaker/AUTHORS'

Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/MeMaker/", line 151, in on_menuitem_about_activate
    file = open(AUTHORSFILE, 'r')
IOError: [Errno 2] No such file or directory: '/usr/share/doc/memaker/AUTHORS'

Local variables in innermost frame:
widget: <gtk.ImageMenuItem object at 0x879543c (GtkImageMenuItem at 0x8850810)>
self: < instance at 0xb7442d0c>

Comment 1 shialeweb 2013-07-02 06:33:52 UTC
Created attachment 767635 [details]
File: backtrace

Comment 2 shialeweb 2013-07-02 06:33:54 UTC
Created attachment 767636 [details]
File: environ

Comment 3 Ankur Sinha (FranciscoD) 2013-07-03 10:39:24 UTC

Thank you for filing this bug report. It's a tiny issue. The AUTHORS file is in 


I'll fix it and push an update sometime soon. 

Warm regards,

Comment 4 Fedora End Of Life 2013-12-21 15:34:52 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 '18'.

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 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

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.

Comment 5 Fedora End Of Life 2014-02-05 23:12:42 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.