double click desktop calendar opens wrong day in evolution

By the way I don't think this happened in dapper but it definitely does in Edgy.

I am trying to replicate the behaviour that you are seeing.

- When you single click, does the calender pop and show you 'todays date' highlighted? (or is it the next day)

- Which timezone are you in? (See - adjust date & time)

Cheers,
Paul

I have a similar problem in Dapper, but it is reversed: if I double-click on a day in the applet-calendar, I get the PREVIOUS day in evolution. Single click only show that day inside the applet.

But that's in Dapper. Is Edgy, it works fine. I'm in the "America/Vancouver" time zone.

I'm in Pacific/Auckland time zone, which is correct.

When I click the applet button, todays date is always correctly highlighted.

I've provided the info that this bug was waiting on.

That's probably a side effect of the fix for bug #42115

Do you have the same timezone configured for evolution and GNOME?

Yes they are the same in both. Evolution has a tick for "compensate for daylight saving automatically." If I tick that, it still doesn't fix the problem. The time & date are correct in both apps.

yup, it's caused by the kludge for #42115. the reasoning was that this problem affects far fewer people (only those in UTC+12 or greater) than the previous problem. the fix is to change the code to open Evolution with the UTC equivalent to the current local time.

> yup, it's caused by the kludge for #42115. the reasoning was that this problem affects
> far fewer people (only those in UTC+12 or greater) than the previous problem.

Since I'm UTC-7 (west coast time of North America), I would suggest that possibly this problem affects more people than originally planned.

ignore my previous comment: I now get it (42115 in Dapper affected more people than 66028 in Edgy...)

Still waiting for a patch...

This bug was fixed in the package gnome-panel - 1:2.22.1-0ubuntu1

---------------
gnome-panel (1:2.22.1-0ubuntu1) hardy; urgency=low

  * New upstream version:
    Panel
    - Convert username/login to UTF-8 in logout dialog
    - Fix applet processes not quitting when the applet is removed (lp: #195915)
    Misc
    - Remove old and useless files
    - Require gweather 2.22.1
    - Don't explicitly require libxml for the weather applet anymore
    Clock Applet
    - Fix crash when there are no locations available
    - Fix locations not appearing in the preferences dialog
    - Make find location window larger
    - Handle escape to close the dialog in the time/timezone dialogs
    - Fix various issues with adding/removing locations
    - Fix crash when PolicyKit helper can't be called (lp: #208791)
    - Fix crash when closing the calendar popup when a city is blinking
      on the map (lp: #200881, ##207954)
    - Improve the blinking on the map when clicking on various locations
    - Cleanups
    - Correctly redraw the map outline on expose events
    - Fix crash when the location doesn't have coordinates (lp: #201102)
    - Fix crash when updating locations while calendar popup is not shown
      (lp: #210470)
    - Fix initial visibility of the appointments to actually follow the
      state of the expander (lp: #206118)
    - Make sure we always use data from the right country (lp: #185190)
    - Show caldav appointments in the calendar
    - Ignore dbus errors when setting the time and there's no reply on the bus
      (lp: #207890)
    - Open evolution on the right day, in all timezones (lp: #66028)
    - Fix crash when an evolution-data-server dies (lp: #122590)
    - Correctly set time, even when DST is on (lp: #208598)
    - Handle multiple locations in the same timezone in a better way
    - Fix weather tooltip to show the real temperature and the apparent
      temperature, instead of only the apparent one (lp: #188183)
    - Do not lose the weather location information when changing the
      timezone of a location (lp: #200911)
    - Don't show weather information of the last location once it has been
      removed
    - Remove empty space on the left of the clock when there's no location
      (lp: #203691)
    - Potential fix for another crash in the calendar code
    - When adding a location, make it the current one if it makes sense
  * debian/control.in:
    - updated libgweather requirement
  * debian/patches/17_expose_wm_keybindings.patch:
    - dropped, the current version has some issues and need to be rework
      during next cycle (lp: #211112)
  * debian/patches/80_from_bugzilla_use_correct_current_timezone.patch:
    - dropped, fixed in the new version

 -- Sebastien Bacher <email address hidden> Tue, 08 Apr 2008 01:47:12 +0200

I reopen the bug because the same thing happens to me in Maverick now.

Is somebody working on this problem? It is really annoying and it seems to be a general problem of the latest linux distributions. This bug happens in fedora 14 too.

This happens to me as well in Maverick.

I don't think it used to happen before.

For me evolution starts and opens the _previous_ day instead of the day I double clicked at.

Is this still a gnome panel bug or is it evolution?
How can I find out and debug these things?

I think I found the piece of code that opens up evolution when we double-click a day in the calendar:

http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/maverick/gnome-panel/maverick/view/head:/applets/clock/calendar-window.c

The function is called: calendar_day_activated() and it composes a string of the date picked in the calendar "broken down to UTC". (I'm in TZ CET)

There is a peculiar comment:

/* FIXME: once bug 409200 is fixed, we'll have to make this hh:mm:ss
 * instead of hhmmss */

Maybe it has something to do with the bug?
What is the bug 409200?

This seems to be related to the selected time zone!

If I double click on Feb 22 my evolution starts up and shows Feb 21.

If I then go into /proc/[evolutionpid]/ and checks its command line it is:

evolution calendar:///?startdate=20110221T230000Z

Which means: Feb 21st, 11 pm. Since my time zone (CET) is +1 hour that forces it into the wrong date!

I don't understand why the date picked in the calendar needs to be converted into UTC for this.
Can someone enlighten me?

I've submitted bug 642603 upstream at gnome.org https://bugzilla.gnome.org/show_bug.cgi?id=642603

I also included a patch that suggests a possible way to solve this.
If the patch does work I hope it will be accepted into the next release or so.

The patch has been accepted upstream and the upstream bug has been set to fixed.
I expect this problem to be gone in the next release.

commit http://git.gnome.org/browse/gnome-panel/commit/?id=b130f26195efba8a1c3f8bd40f34ed45563635b7

thank you for your work

sorry to resurrect this by i am getting the same behaviour in 11.10 , when i click on a date the calendar opens with 1st of january 1970 , if i do add event i get calendar poping up with todays date.

Amias, the same thing is happening here.

@amias and wribeiro, please see bug 919157 for the 1 January 1970 issue.