Bug 789625 - Gdeskcal hangs when crossing from one year to another
Summary: Gdeskcal hangs when crossing from one year to another
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gdeskcal
Version: 16
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Orphan Owner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-11 20:56 UTC by Joe Zeff
Modified: 2013-02-13 14:22 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-13 14:22:40 UTC
Type: ---


Attachments (Terms of Use)

Description Joe Zeff 2012-02-11 20:56:54 UTC
Description of problem:

Gdeskcal hangs for up to five minutes, using at least 60% of my CPU when I try to cross a year boundary, either when I go from December to January, or from January to December.

Version-Release number of selected component (if applicable):

1.01

How reproducible:

100%

Steps to Reproduce:
1. Have Gdeskcal running on your desktop
2. Try to change the month to one in a different year
3.
  
Actual results:

The program sits there, completely unresponsive, for several minutes, before suddenly updating.  Once it's in a different year, moving from one month to another within that year works fine.

Expected results:

The display updates to show the new month and year as quickly as it would if the year didn't change.

Additional info:

I don't know if it matters, but I run XFCE.  Also, when I start the program, nothing shows at first other than a thin vertical line.  The calendar doesn't display for at least five or ten minutes.  This, however, isn't related to XFCE because it did the same thing under Gnome2.  I mention it only because I don't know what is or isn't important, and too much info is always better than not enough.

Comment 1 Joe Zeff 2012-06-05 02:19:10 UTC
More information: while gdeskcal is chugging along, it stays on the top, covering part of any window (such as a browser) that would normally overlay it.  Just now, I tried to add a medical appointment for next February and the program hung completely when I tried to close the appointment window.  Not only that, the Edit Appointment window followed me from one workspace to the next, again putting itself on top.  When I clicked the X to close the windwo, I was told that it wasn't responding and when I confirmed that I wanted it closed, it closed gdeskcal completely.

Comment 2 Fedora End Of Life 2013-01-16 13:32:40 UTC
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: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 3 Fedora End Of Life 2013-02-13 14:22:43 UTC
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.