Bug#412662: jpilot: Alarms are not removed timely when a calendar appointment is removed.
-- sorry for the delay, for some reason, the below email got stuck in my Drafts folder... Eric Hi Ludovic, it was not easy but at last I found the issue: the appointment needs to be recurring! i.e. the steps are: - create a recurring alarm which first occurrence will ring like 5 minutes in the future. - remove this first occurrence - wait a little while -> it rings! Eric Ludovic Rousseau said: Le 27.02.2007, à 18:34:07, Ludovic Rousseau a écrit: Le 27.02.2007, à 10:41:45, Eric Lavarde a écrit: > if one removes an appointment with an alarm from the calendar, the alarm will > still ring if Jpilot is not restarted inbetween. > e.g. yesterday I created a meeting for today noon; at 10:00 today I remove the > meeting; jpilot will still send an alarm at noon, even if the meeting > doesn't exist anymore. Thanks. I reported the bug upstream. upstream said: " Unable to reproduce on jpilot-0.99.9 or CVS code. Steps: 1) Created an appt. with alarm ten minutes in the future 2) Deleted appt. 3) No alarm after ten minutes had passed. In order to debug this I need a test case which fails repeatedly. " You can answer here or in the upsteam bug tracker at http://bugs.jpilot.org/1794 Thanks -- Dr. Ludovic Rousseau[EMAIL PROTECTED] -- Normaliser Unix c'est comme pasteuriser le camembert, L.R. -- --
Bug#412662: jpilot: Alarms are not removed timely when a calendar appointment is removed.
Hi, after a few tests, the issue in deed seem to appear under specific circumstances; but I'm still convinced that there is a bug, just give me some time to find out how to reproduce it. Read me soon (hopefully) ;-) Eric Ludovic Rousseau said: > Le 27.02.2007, à 18:34:07, Ludovic Rousseau a écrit: >> Le 27.02.2007, à 10:41:45, Eric Lavarde a écrit: >> > if one removes an appointment with an alarm from the calendar, the >> alarm will >> > still ring if Jpilot is not restarted inbetween. >> > e.g. yesterday I created a meeting for today noon; at 10:00 today I >> remove the >> > meeting; jpilot will still send an alarm at noon, even if the meeting >> > doesn't exist anymore. >> >> Thanks. I reported the bug upstream. > > upstream said: > > " Unable to reproduce on jpilot-0.99.9 or CVS code. > > Steps: > 1) Created an appt. with alarm ten minutes in the future > 2) Deleted appt. > 3) No alarm after ten minutes had passed. > > In order to debug this I need a test case which fails repeatedly. " > > You can answer here or in the upsteam bug tracker at > http://bugs.jpilot.org/1794 > > Thanks > > -- > Dr. Ludovic Rousseau[EMAIL PROTECTED] > -- Normaliser Unix c'est comme pasteuriser le camembert, L.R. -- > --
Bug#412662: jpilot: Alarms are not removed timely when a calendar appointment is removed.
Le 27.02.2007, à 18:34:07, Ludovic Rousseau a écrit: > Le 27.02.2007, à 10:41:45, Eric Lavarde a écrit: > > if one removes an appointment with an alarm from the calendar, the alarm > > will > > still ring if Jpilot is not restarted inbetween. > > e.g. yesterday I created a meeting for today noon; at 10:00 today I remove > > the > > meeting; jpilot will still send an alarm at noon, even if the meeting > > doesn't exist anymore. > > Thanks. I reported the bug upstream. upstream said: " Unable to reproduce on jpilot-0.99.9 or CVS code. Steps: 1) Created an appt. with alarm ten minutes in the future 2) Deleted appt. 3) No alarm after ten minutes had passed. In order to debug this I need a test case which fails repeatedly. " You can answer here or in the upsteam bug tracker at http://bugs.jpilot.org/1794 Thanks -- Dr. Ludovic Rousseau[EMAIL PROTECTED] -- Normaliser Unix c'est comme pasteuriser le camembert, L.R. --
Bug#412662: jpilot: Alarms are not removed timely when a calendar appointment is removed.
forwarded 412662 http://bugs.jpilot.org/1794 tags 412662 upstream thanks Le 27.02.2007, à 10:41:45, Eric Lavarde a écrit: > if one removes an appointment with an alarm from the calendar, the alarm will > still ring if Jpilot is not restarted inbetween. > e.g. yesterday I created a meeting for today noon; at 10:00 today I remove the > meeting; jpilot will still send an alarm at noon, even if the meeting > doesn't exist anymore. Thanks. I reported the bug upstream. -- Dr. Ludovic Rousseau[EMAIL PROTECTED] -- Normaliser Unix c'est comme pasteuriser le camembert, L.R. --
Bug#412662: jpilot: Alarms are not removed timely when a calendar appointment is removed.
Package: jpilot Version: 0.99.9.2-1 Severity: minor Hello, if one removes an appointment with an alarm from the calendar, the alarm will still ring if Jpilot is not restarted inbetween. e.g. yesterday I created a meeting for today noon; at 10:00 today I remove the meeting; jpilot will still send an alarm at noon, even if the meeting doesn't exist anymore. Thanks, Eric -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-3-686 Locale: LANG=en_IE.UTF-8, LC_CTYPE=en_IE.UTF-8 (charmap=UTF-8) Versions of packages jpilot depends on: ii libatk1.0-0 1.12.4-2 The ATK accessibility toolkit ii libc6 2.3.6.ds1-11 GNU C Library: Shared libraries ii libcairo2 1.2.4-4 The Cairo 2D vector graphics libra ii libfontconfig1 2.4.2-1 generic font configuration library ii libglib2.0-02.12.4-2 The GLib library of C routines ii libgtk2.0-0 2.8.20-5 The GTK+ graphical user interface ii libpango1.0-0 1.14.8-5 Layout and rendering of internatio ii libpisock9 0.12.1-5 library for communicating with a P ii libx11-62:1.0.3-5X11 client-side library ii libxcursor1 1.1.7-4 X cursor management library ii libxext61:1.0.1-2X11 miscellaneous extension librar ii libxfixes3 1:4.0.1-5X11 miscellaneous 'fixes' extensio ii libxi6 1:1.0.1-4X11 Input extension library ii libxinerama11:1.0.1-4.1 X11 Xinerama extension library ii libxrandr2 2:1.1.0.2-5 X11 RandR extension library ii libxrender1 1:0.9.1-3X Rendering Extension client libra Versions of packages jpilot recommends: ii jpilot-plugins0.99.9.2-1 plugins for jpilot (Palm Pilot des -- debconf information: * shared/pilot/port: ttyS0 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
