> 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. ** Bug watch added: github.com/gtimelog/gtimelog/issues #87 https://github.com/gtimelog/gtimelog/issues/87 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1638253 Title: gtimelog does not recognise a new month for reporting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtimelog/+bug/1638253/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
