gtimelog does not recognise a new month for reporting

Bug #1638253 reported by Raphael Mankin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gtimelog (Ubuntu)
New
Undecided
Unassigned

Bug Description

This is a supplementary to a bug I reported earlier, but I cannot now find the bug number.

1. At the start of a new month asking for a report for 'last month' gets the report for 2 months ago. e.g. on 1 Nov I get the report for September and not for October.

2. Closing and restarting gtimelog does not reset gtimelog's notion of what month it is.

3. Logging out and in again does reset the 'current month'.

lsb_release -rd
Description: Ubuntu 14.04.5 LTS
Release: 14.04

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: gtimelog 0.9.1-2
ProcVersionSignature: Ubuntu 4.4.0-45.66~14.04.1-generic 4.4.21
Uname: Linux 4.4.0-45-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
CurrentDesktop: XFCE
Date: Tue Nov 1 10:58:53 2016
InstallationDate: Installed on 2016-08-07 (85 days ago)
InstallationMedia: Xubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
PackageArchitecture: all
SourcePackage: gtimelog
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Raphael Mankin (raph-p) wrote :
Revision history for this message
Marius Gedminas (mgedmin) wrote :

> This is a supplementary to a bug I reported earlier, but I cannot now find the bug number.

Was it https://github.com/gtimelog/gtimelog/issues/87 ?

> 2. Closing and restarting gtimelog does not reset gtimelog's notion of what month it is.
>
> 3. Logging out and in again does reset the 'current month'.

This is probably because closing gtimelog just minimizes it to the system tray instead of actually making it exit. You could try Ctrl+Q instead to really make it quit.

Revision history for this message
Raphael Mankin (raph-p) wrote : Re: [Bug 1638253] Re: gtimelog does not recognise a new month for reporting

On Mon, 2016-11-07 at 08:44 +0000, Marius Gedminas wrote:
> > This is a supplementary to a bug I reported earlier, but I cannot now
> find the bug number.
>
> Was it https://github.com/gtimelog/gtimelog/issues/87 ?
Yes, That's the bunny.

>
> > 2. Closing and restarting gtimelog does not reset gtimelog's notion of what month it is.
> >
> > 3. Logging out and in again does reset the 'current month'.
>
> This is probably because closing gtimelog just minimizes it to the
> system tray instead of actually making it exit. You could try Ctrl+Q
> instead to really make it quit.
Thank you.

I suppose that at some point Ubuntu will give us a newer version in its
updates :)

>
>
> ** Bug watch added: github.com/gtimelog/gtimelog/issues #87
> https://github.com/gtimelog/gtimelog/issues/87
>

Revision history for this message
Marius Gedminas (mgedmin) wrote :

There's a PPA (https://launchpad.net/~gtimelog-dev/+archive/ubuntu/ppa) with a slightly newer version than the one in the current Ubuntu release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.