Bug 838588 - Hamster freezes upon entering a time
Hamster freezes upon entering a time
Product: Fedora
Classification: Fedora
Component: hamster-applet (Show other bugs)
x86_64 Linux
unspecified Severity high
: ---
: ---
Assigned To: Mads Villadsen
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2012-07-09 10:32 EDT by Brian Sipos
Modified: 2013-02-13 11:36 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2013-02-13 11:35:58 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Brian Sipos 2012-07-09 10:32:03 EDT
Description of problem:
My hamster configuration was recently upgraded from Fedora 14 to Fedora 16, and now if I attempt to create a new entry in the hamster program the program freezes.

Version-Release number of selected component (if applicable):
This is hamster-applet version 2.32.1-1.fc16

How reproducible:

Steps to Reproduce:
1. Open hamster-time-tracker program.
2. Type number 0 (e.g. beginning of time string "0900").
3. Observe that the program is frozen.
Actual results:
Program freezes.

Expected results:
Program should display an error, if appropriate, or ignore a failed calendar.

Additional info:
Here is the console log from the program (I replaced my email server URL with example):
$ hamster-time-tracker 
** (hamster-time-tracker:24593): DEBUG: Opening calendar source uri: local:system

** (hamster-time-tracker:24593): DEBUG: Opening calendar source uri: exchange://BSipos;auth=Basic@example.com/;personal/Tasks

** (hamster-time-tracker:24593): WARNING **: Failed to open calendar (type 1): Authentication required
** (hamster-time-tracker:24593): DEBUG: Opening calendar source uri: local:system

Comment 1 Fedora End Of Life 2013-01-16 10:13:25 EST
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: 
Comment 2 Fedora End Of Life 2013-02-13 11:36:01 EST
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.

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