Red Hat Bugzilla – Bug 282281
Blam fails to properly recover from hibernate
Last modified: 2008-06-16 22:21:14 EDT
Description of problem:
I hibernated my desktop. After restore from hibernate, one day later, blam
fails to fully update it's windows. However it is still responsive to some
clicks in the window and sometimes updates the list of items in a feed.
Version-Release number of selected component (if applicable):
two times so far. This doesn't happen for a short hibernate.
Steps to Reproduce:
1. start blam
2. hibernate PC (system->shutdown->hibernate)
3. wait a day
4. restart PC with power
The blam window is blank except for the gray regions which divide the three
different panes and even those are just plane. Clicking on a feed (by guessing
where it is) sometimes brings up a list of stories. Refresh buttons etc. are
not visible. The stories headlines, when visible, can lead to display of the
stories, but it seems like the feeds do not refresh.
Blam window continues to operate as normal.
I get a message about HAL failing to recover from hibernate, but I think this
isn't relevant. Certainly other applications such as firefox work fine.
I have no clue about mono debugging. I tried the mono debugger but I get the
Unhandled Exception: System.TypeInitializationException: An exception was thrown
by the type initializer for Mono.Debugger.Frontend.CommandLineInterpreter --->
at (wrapper managed-to-native)
at Mono.Debugger.Frontend.CommandLineInterpreter..cctor () [0x00000] --- End
of inner exception stack trace ---
When you say "short hibernate," about how long does it take for this to occur? A
few hours? A full day? Thanks.
Michael, does this still occur for you with the latest Blam in the repositories
Also, about how long do I need to hibernate to reproduce the error?
It's hard to say. I previously had the problem reliably when hibernating from
day to day (e.g. quite a bit more than 12 hours). I've seen it happen with a
shorter hibernate, but if I hibernate less than 2 hours it doesn't normally seem
to happen. I just tried overnight and didn't trigger the bug. I'm now not
totally sure about the cause, whether it's having it running for a long time or
I'll keep blam running all the time and wait until I trigger it again.
This message is a reminder that Fedora 7 is nearing the end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 7. 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 '7'.
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 7'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 7 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. 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. If possible, it is recommended that you try the newest available Fedora distribution to see if your bug still exists.
Please read the Release Notes for the newest Fedora distribution to make sure it will meet your needs:
The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 7 changed to end-of-life (EOL) status on June 13, 2008.
Fedora 7 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.