gnome-panel calls evolution incorrectly

[Alvin Thompson]

Binary package hint: gnome-panel

the calendar applet in gnome panel needs to include the time in the command line used to open evolution's calendar. otherwise, evolution may be opened to the wrong date. see my comment in bug #42115 for more information.

[Alvin Thompson (alvint-deactivatedaccount)]

to be more specific, the command used to open evolution is probably something like this:

evolution calendar:///?startdate=20060608

in this example, i believe that evolution is assuming the specific time to open is 8 june 2006, 00:00 zulu time. this gets translated to the previous day to those of us in a "minus" time zone.

so, Bug #42115 is not a bug, rather gnome-panel needs to specify the specific time zone in its command.

[Sebastien Bacher (seb128)]

Thank you for your interest to that. Launchpad has that nice feature that you can ask several tasks on a bug, so no need to open a new bug, I'm rejecting that one as duplicate then, please open a gnome-panel task on bug #42115 rather

[Alvin Thompson (alvint-deactivatedaccount)]

there's probably a way, but i haven't figured out the syntax for specifying the time zone with the command line. a kludge is always using noon zulu time:

evolution calendar:///?startdate=20060608T120000

[Alvin Thompson (alvint-deactivatedaccount)]

as i pointed out, this is NOT a duplicate of Bug #42115. Bug #42115 is NOT a valid bug. the problem is that gnome-panel is not specififying the time or time zone.

[Sebastien Bacher (seb128)]

that's a duplicate, please don't play on the settings against the maintainer advice, there is no use for that. If bug #42115 has a wrong description the description can be updated, if the package is wrong it can be changed too, if the issue concerns differents packages corresponding tasks can be opened, etc. The interest is to keep the discussion on one bug, what use do you have to reject the previous one and open a new one instead of updating the description?

[Alvin Thompson (alvint-deactivatedaccount)]

the reason is that bug #42115 is mirrored upstream and the maintainers need to know not to waste their time with it.

[Sebastien Bacher (seb128)]

- upstream don't receive changes made on launchpad
- if the bug is at the wrong place on launchpad it's probably at the wrong place on bugzilla too
- upstream bugs can be moved to the right place too

[Alvin Thompson (alvint-deactivatedaccount)]

fine, i'll change the bugs appropriately.