Red Hat Bugzilla – Bug 867970
eterm 0.9.6-5.fc16 x86_64 errors out when starting from Enlightenment -- yum downgrade solves.
Last modified: 2013-03-07 19:07:06 EST
Description of problem: eterm errors on start
Version-Release number of selected component (if applicable): Most recent update - 0.9.6-5.fc16 x86_64
How reproducible: update, attempt to run eterm from withing enlightenment.
Steps to Reproduce:
1.log into Enlightenment
2.update eterm 0.9.6-5.fc16
3.attempt to start eterm by icon in iBar
Actual results: Enlightenment error message pops saying, "failure to change to :Home."
Expected results: Open terminal
Additional info: yum downgrade eterm (to eterm 0.9.5-8.fc15 x86_64) solves problem.
Thanks for your report.
Related to the change in #860326.
I am unable to reproduce this with e16-1.0.10-1.fc16.x86_64 . Are you using e17?
What is the value of variable $HOME in your context?
I was using F16. However, the same issue now occurs in F17.
Please see attached error message illustration.
Created attachment 630230 [details]
Enlightenment error message.
Created attachment 630231 [details]
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:
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.
Reverting change in #860326 to fix the issue.
See https://bugzilla.redhat.com/show_bug.cgi?id=841471 for reference.
eterm-0.9.6-7.fc17 has been submitted as an update for Fedora 17.
eterm-0.9.6-7.fc18 has been submitted as an update for Fedora 18.
* should fix your issue,
* was pushed to the Fedora 17 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing eterm-0.9.6-7.fc17'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
*** Bug 915648 has been marked as a duplicate of this bug. ***
The fix works. Thanks for the help.
eterm-0.9.6-7.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
eterm-0.9.6-7.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.