Ticket #132 (closed defect: fixed)

Opened 20 months ago

Last modified 19 months ago

Journal - selecting 'today' filter hides all/recent content

Reported by: mungewell Owned by: tomeu
Priority: blocker Milestone:
Component: journal Version: Git as of bugdate
Severity: Keywords:
Cc: Distribution/OS:
Bug Status:

Description

In Jhbuild 20081217 Journal

If the 'today' filter is selected all my journal items are hidden.

I only have items ranging from 1s to 56mins ago, so all should remained displayed. I am on UTC-7 if that makes a difference, although I have not specifically set that anywhere within sugar.

'date' in terminal activity gives UTC time, not local time.
Clock in XFCE panel shows correct local time.

Change History

Changed 20 months ago by mungewell

Setting correct local (to Edmonton from UTC) in 'sugar settings' and restarting fixes problem(s). Journal items are still '1s' -> ago, but are correctly filtered and 'date' gives correct MST time.

However I still consider this a bug because most of the world is not UTC and it is not a forced parameter. Default value is going to cause confusion.

Note this may be specific to sugar 'add on' to normal Linux/Ubuntu system, which may miss out on configuring something sugar relies on....

Changed 20 months ago by mungewell

I should add that localtime is currently around 23:00 MST (UTC-7), so UTC today is actually tomorrow.

Changed 20 months ago by mungewell

  • priority changed from minor to major

Changed 20 months ago by erikos

  • owner changed from marcopg to tomeu
  • version set to Git as of bugdate
  • component changed from sugar to journal

Thanks Mungwell for the report.

That is the query I get - there are no entries displayed.

ListView.refresh query {'mountpoints': ['/'], 'mtime': {'start': '2008-12-22T00:00:00.386651', 'end': '2008-12-22T15:13:19.386730'}}

Changed 19 months ago by tomeu

  • priority changed from major to blocker

Changed 19 months ago by tomeu

  • status changed from new to closed
  • resolution set to fixed

Should be fixed now, thanks!

Note: See TracTickets for help on using tickets.