Hi, 
Guest
Pic
Sign In

jpilot@lists.jpilot.org

General support, questions, patches for J-Pilot.

View all threads

Further / more complex problems.

S
sawbona@gmx.net
Fri, Jun 21, 2024 1:34 PM

Hello:

Forced to upgrade my Linux Devuan Beowulf to Chimaera, I was then boxed into a corner by problems with the native nouveau driver and had no choice but to upgrade Daedalus (stable) which seems to have solved my twin video cards/multiple monitor problems.

:~$ uname -a

Linux devuan 6.1.0-21-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.90-1 (2024-05-03) x86_64 GNU/Linux

:~$

Hello: Forced to upgrade my Linux Devuan Beowulf to Chimaera, I was then boxed into a corner by problems with the native nouveau driver and had no choice but to upgrade Daedalus (stable) which seems to have solved my twin video cards/multiple monitor problems. `:~$ uname -a` `Linux devuan 6.1.0-21-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.90-1 (2024-05-03) x86_64 GNU/Linux` `:~$`
S
sawbona@gmx.net
Fri, Jun 21, 2024 2:00 PM

Hello (again):

—-> Did I ever mention that not being able to edit posts is a real PITA? 8^/

That said, I have come across another problem, apparently more complex than the previous one I posted.

If I add a new appointment, eg: Flag Day, a holiday that by definition repeats itself every year with no end, J-pilot 1.8.2 will crash, keeping the appointment but not the event repeat setting.

Curiously enough, this will not happen if the event is set to repeat every day, every week or every month.

Only every year.

When this happens, a rolling dmesg printout reads thus:

[Jun21 10:51] jpilot[17451]: segfault at 9 ip 00007fb599c9acb6 sp 00007ffd539ee408 error 4 in libc.so.6[7fb599c17000+155000] likely on CPU 0 (core 0, socket 0)

[ +0.000023] Code: 00 00 66 90 66 0f ef c0 66 0f ef c9 66 0f ef d2 66 0f ef db 48 89 f8 48 89 f9 48 81 e1 ff 0f 00 00 48 81 f9 cf 0f 00 00 77 6a <f3> 0f 6f 20 66 0f 74 e0 66 0f d7 d4 85 d2 74 04 0f bc c2 c3 48 83

—- snip —-

Same thing happens if I choose to end it the next day, next month or in 2030: J-Pilot will still crash in the same manner.

I’d appreciate some input on this.

Thanks in advance.

Best,

JHM

Hello (again): —-> Did I ever mention that not being able to edit posts is a real PITA? 8^/ That said, I have come across another problem, apparently more complex than the previous one I posted. If I add a new appointment, eg: Flag Day, a holiday that by definition repeats itself every year with no end, `J-pilot 1.8.2` will crash, keeping the appointment but *not* the event repeat setting. Curiously enough, this will not happen if the event is set to repeat every **day**, every **week** or every **month**. Only every **year**. When this happens, a rolling `dmesg` printout reads thus: `[Jun21 10:51] jpilot[17451]: segfault at 9 ip 00007fb599c9acb6 sp 00007ffd539ee408 error 4 in libc.so.6[7fb599c17000+155000] likely on CPU 0 (core 0, socket 0)` `[ +0.000023] Code: 00 00 66 90 66 0f ef c0 66 0f ef c9 66 0f ef d2 66 0f ef db 48 89 f8 48 89 f9 48 81 e1 ff 0f 00 00 48 81 f9 cf 0f 00 00 77 6a <f3> 0f 6f 20 66 0f 74 e0 66 0f d7 d4 85 d2 74 04 0f bc c2 c3 48 83` `—- snip —-` Same thing happens if I choose to end it the next day, next month or in 2030: J-Pilot will still crash in the same manner. I’d appreciate some input on this. Thanks in advance. Best, JHM
EK
Elmar Klausmeier
Sat, Jun 22, 2024 9:31 AM

Hello,

I tried to replicate your problem with yearly repeating events.
Unfortunately, I cannot, see attached screenshot. The only difference I see
is in the versions used: I use 2.0.1, you use 1.8.2. However I do not
remember that there was a change in handling repeating events between those
two versions.

What I did: export JPILOT_HOME=/mp, then start jpilot.

Regards,

Elmar.

On Fri, Jun 21, 2024 at 4:00 PM Julius Henry Marx via Jpilot <
jpilot@lists.jpilot.org> wrote:

Hello (again):

—-> Did I ever mention that not being able to edit posts is a real PITA?
8^/

That said, I have come across another problem, apparently more complex
than the previous one I posted.

If I add a new appointment, eg: Flag Day, a holiday that by definition
repeats itself every year with no end, J-pilot 1.8.2 will crash, keeping
the appointment but not the event repeat setting.

Curiously enough, this will not happen if the event is set to repeat every
day, every week or every month.

Only every year.

When this happens, a rolling dmesg printout reads thus:

[Jun21 10:51] jpilot[17451]: segfault at 9 ip 00007fb599c9acb6 sp 00007ffd539ee408 error 4 in libc.so.6[7fb599c17000+155000] likely on CPU 0 (core 0, socket 0)

[ +0.000023] Code: 00 00 66 90 66 0f ef c0 66 0f ef c9 66 0f ef d2 66 0f ef db 48 89 f8 48 89 f9 48 81 e1 ff 0f 00 00 48 81 f9 cf 0f 00 00 77 6a <f3> 0f 6f 20 66 0f 74 e0 66 0f d7 d4 85 d2 74 04 0f bc c2 c3 48 83

—- snip —-

Same thing happens if I choose to end it the next day, next month or in
2030: J-Pilot will still crash in the same manner.

I’d appreciate some input on this.

Thanks in advance.

Best,

JHM

Jpilot mailing list -- jpilot@lists.jpilot.org
To unsubscribe send an email to jpilot-leave@lists.jpilot.org

Hello, I tried to replicate your problem with yearly repeating events. Unfortunately, I cannot, see attached screenshot. The only difference I see is in the versions used: I use 2.0.1, you use 1.8.2. However I do not remember that there was a change in handling repeating events between those two versions. What I did: export JPILOT_HOME=/mp, then start jpilot. Regards, Elmar. On Fri, Jun 21, 2024 at 4:00 PM Julius Henry Marx via Jpilot < jpilot@lists.jpilot.org> wrote: > Hello (again): > > —-> Did I ever mention that not being able to edit posts is a real PITA? > 8^/ > > That said, I have come across another problem, apparently more complex > than the previous one I posted. > > If I add a new appointment, eg: Flag Day, a holiday that by definition > repeats itself every year with no end, `J-pilot 1.8.2` will crash, keeping > the appointment but *not* the event repeat setting. > > Curiously enough, this will not happen if the event is set to repeat every > **day**, every **week** or every **month**. > > Only every **year**. > > When this happens, a rolling `dmesg` printout reads thus: > > `[Jun21 10:51] jpilot[17451]: segfault at 9 ip 00007fb599c9acb6 sp > 00007ffd539ee408 error 4 in libc.so.6[7fb599c17000+155000] likely on CPU 0 > (core 0, socket 0)` > > `[ +0.000023] Code: 00 00 66 90 66 0f ef c0 66 0f ef c9 66 0f ef d2 66 0f > ef db 48 89 f8 48 89 f9 48 81 e1 ff 0f 00 00 48 81 f9 cf 0f 00 00 77 6a > <f3> 0f 6f 20 66 0f 74 e0 66 0f d7 d4 85 d2 74 04 0f bc c2 c3 48 83` > > `—- snip —-` > > Same thing happens if I choose to end it the next day, next month or in > 2030: J-Pilot will still crash in the same manner. > > I’d appreciate some input on this. > > Thanks in advance. > > Best, > > JHM > _______________________________________________ > Jpilot mailing list -- jpilot@lists.jpilot.org > To unsubscribe send an email to jpilot-leave@lists.jpilot.org >
S
sawbona@gmx.net
Sat, Jun 22, 2024 12:43 PM

Hello:

… appreciate some input on this.

The plot thickens …

I have been going over my J-Pilot installation, something I have not had to do more than a couple of times in quite a few years.

It just worked, always, including when I upgraded kernels so there was no need to do anything much.

There are two things that caught my attention:

One is that my current J-Pilot starts not with a *.desktop file but with a shell script.

Cannot recall *exactly* how that got to be so, but here it is:

#!/bin/bash

export JPILOT_HOME="/home/groucho/.jpilot"

jpilot -d

Seeing that this was so, I set up a regular *.desktop file for my Xfce desktop (via ‘Create Launcher’) like this:

[Desktop Entry]

Version=1.0

Type=Application

Name=J-Pilot

Comment=Palm Pilot

Exec=jpilot -d

Icon=jpilot

Path=/home/groucho/.jpilot/.jpilot

Terminal=false

StartupNotify=true

But it does not open the same J-Pilot instance. ie: it is empty of any data, unlike the one opened with the script.

Setting up the *desktop file made me notice that, besides /home/groucho/.jpilot there is also a /home/groucho/.jpilot/.jpilot which seems to be the one opened by the script.

Again, I cannot recall how that got to be that way but one of them is not right.

Unfortunately, I found something else:

For whatever reason, in both directories, there are J-Pilot files with very strange dates:

~/.jpilot$ ls -lt

total 60

-rw------- 1 groucho groucho 2518 Jun 22 08:49 jpilot.log

-rw------- 1 groucho groucho 11 Jun 22 08:49 jpilot.next_id

-rw------- 1 groucho groucho 1878 Jun 22 08:49 jpilot.rc

-rw------- 1 groucho groucho 126 Jun 22 08:49 jpilot.alarms

-rw------- 1 groucho groucho 0 Sep 19 2022 AddressDB.pc3

-rw------- 1 groucho groucho 0 Sep 19 2022 ExpenseDB.pc3

-rw------- 1 groucho groucho 0 Sep 19 2022 Keys-Gtkr.pc3

-rw------- 1 groucho groucho 0 Sep 19 2022 MemoDB.pc3

-rw------- 1 groucho groucho 0 Sep 19 2022 DatebookDB.pc3

-rw------- 1 groucho groucho 0 Sep 19 2022 ToDoDB.pc3

-rw------- 1 groucho groucho 0 Sep 19 2022 jpilot.plugins

-rw------- 1 groucho groucho 718 Dec 31 1969 AddressDB.pdb

-rw------- 1 groucho groucho 378 Dec 31 1969 CalendarDB-PDat.pdb

-rw------- 1 groucho groucho 1172 Dec 31 1969 ContactsDB-PAdd.pdb

-rw------- 1 groucho groucho 360 Dec 31 1969 DatebookDB.pdb

-rw------- 1 groucho groucho 472 Dec 31 1969 ExpenseDB.pdb

-rw------- 1 groucho groucho 362 Dec 31 1969 MananaDB.pdb

-rw------- 1 groucho groucho 362 Dec 31 1969 Memo32DB.pdb

-rw------- 1 groucho groucho 362 Dec 31 1969 MemoDB.pdb

-rw------- 1 groucho groucho 380 Dec 31 1969 MemosDB-PMem.pdb

-rw------- 1 groucho groucho 380 Dec 31 1969 TasksDB-PTod.pdb

-rw------- 1 groucho groucho 362 Dec 31 1969 ToDoDB.pdb

~/.jpilot$

~/.jpilot$ cd .jpilot

~/.jpilot/.jpilot$

~/.jpilot/.jpilot$ ls -lt

total 476

-rw------- 1 groucho groucho 14 Jun 22 08:48 jpilot.next_id

-rw------- 1 groucho groucho 28260 Jun 22 08:48 jpilot.log

-rw------- 1 groucho groucho 1873 Jun 22 08:48 jpilot.rc

-rw------- 1 groucho groucho 126 Jun 22 08:48 jpilot.alarms

-rw------- 1 groucho groucho 2331 Jun 21 22:01 AddressDB.pc3

-rw------- 1 groucho groucho 306 Jun 21 11:01 DatebookDB.pc3

-rw------- 1 groucho groucho 0 Jun 21 10:31 sync_pid

-rw------- 1 groucho groucho 0 Jun 21 10:31 jpilot.install

-rw------- 1 groucho groucho 18739 Jun 21 10:30 'Saved Preferences.prc'

drwx------ 2 groucho groucho 16384 Jun 21 10:10 backup06211009

lrwxrwxrwx 1 groucho groucho 14 Jun 21 10:09 backup -> backup06211009

-rw------- 1 groucho groucho 102533 Jun 21 10:09 AddressDB.pdb

-rw------- 1 groucho groucho 162492 Jun 21 10:09 DatebookDB.pdb

drwx------ 2 groucho groucho 16384 Jun 7 07:12 backup06070711

-rw------- 1 groucho groucho 37202 May 27 11:29 MemoDB.pdb

-rw------- 1 groucho groucho 0 May 15 08:37 Keys-Gtkr.pc3

-rw------- 1 groucho groucho 0 May 15 08:37 MemoDB.pc3

-rw------- 1 groucho groucho 830 May 12 18:13 Keys-Gtkr.pdb

drwx------ 2 groucho groucho 4096 May 12 17:52 backup_removed

-rw------- 1 groucho groucho 362 Apr 20 08:53 ToDoDB.pdb

-rw------- 1 groucho groucho 544 Apr 20 08:53 ExpenseDB.pdb

-rw------- 1 groucho groucho 18047 Sep 29 2020 AddressDB.old

-rw------- 1 groucho groucho 0 Jan 20 2020 ToDoDB.pc3

-rw------- 1 groucho groucho 0 Jan 17 2020 ContactsDB-PAdd.pc3

-rw------- 1 groucho groucho 0 Jan 17 2020 ContactsDB-PAdd.pc3.nouse

-rw------- 1 groucho groucho 0 Jan 16 2020 ExpenseDB.pc3

-rw------- 1 groucho groucho 0 Jan 15 2020 jpilot.plugins

-rw------- 1 groucho groucho 378 Dec 31 1969 CalendarDB-PDat.nouse

-rw------- 1 groucho groucho 378 Dec 31 1969 CalendarDB-PDat.pdb

-rw------- 1 groucho groucho 1172 Dec 31 1969 ContactsDB-PAdd.pdb

-rw------- 1 groucho groucho 1172 Dec 31 1969 ContactsDB-PAdd.pdb.nouse

-rw------- 1 groucho groucho 362 Dec 31 1969 MananaDB.pdb

-rw------- 1 groucho groucho 362 Dec 31 1969 Memo32DB.pdb

-rw------- 1 groucho groucho 362 Dec 31 1969 Memo32DB.pdb.nouse

-rw------- 1 groucho groucho 380 Dec 31 1969 MemosDB-PMem.pdb

-rw------- 1 groucho groucho 380 Dec 31 1969 TasksDB-PTod.pdb

~/.jpilot/.jpilot$

Evidently, the files with a 1969 date are / have been somehow mangled and that may hold (?) a clue as to the previously reported problem.

But I have no idea as to how it may have happened.

Maybe during the upgrade from Beowulf to Chimaera to Daedalus? Seems unlikely as J-Pilot should not have been touched as Debian/Devuan do not have that package in their repositories.

ie: jpilot, jpilot-plugins and pilot-link are listed as [installed, local] by apt.

And then there is the issue of having two .jpilot directories, one of which has to go.

Q: how can I fix all this?

Thanks in advance.

Best,

JHM

Hello: > … appreciate some input on this. The plot thickens … I have been going over my J-Pilot installation, something I have not had to do more than a couple of times in quite a few years. It just worked, always, including when I upgraded kernels so there was no need to do anything much. There are two things that caught my attention: One is that my current J-Pilot starts not with a `*.desktop` file but with a shell script. Cannot recall \*exactly\* how that got to be so, but here it is: `#!/bin/bash` `export JPILOT_HOME="/home/groucho/.jpilot"` `jpilot -d` Seeing that this was so, I set up a regular `*.desktop` file for my Xfce desktop (via ‘Create Launcher’) like this: `[Desktop Entry]` `Version=1.0` `Type=Application` `Name=J-Pilot` `Comment=Palm Pilot` `Exec=jpilot -d` `Icon=jpilot` `Path=/home/groucho/.jpilot/.jpilot` `Terminal=false` `StartupNotify=true` But it does not open the same J-Pilot instance. ie: it is empty of any data, unlike the one opened with the script. Setting up the \*desktop file made me notice that, besides `/home/groucho/.jpilot` there is also a `/home/groucho/.jpilot/.jpilot` which seems to be the one opened by the script. Again, I cannot recall how that got to be that way but one of them is not right. Unfortunately, I found something else: For whatever reason, in both directories, there are J-Pilot files with *very* strange dates: `~/.jpilot$ ls -lt` `total 60` `-rw------- 1 groucho groucho 2518 Jun 22 08:49 jpilot.log` `-rw------- 1 groucho groucho 11 Jun 22 08:49 jpilot.next_id` `-rw------- 1 groucho groucho 1878 Jun 22 08:49 jpilot.rc` `-rw------- 1 groucho groucho 126 Jun 22 08:49 jpilot.alarms` `-rw------- 1 groucho groucho 0 Sep 19 2022 AddressDB.pc3` `-rw------- 1 groucho groucho 0 Sep 19 2022 ExpenseDB.pc3` `-rw------- 1 groucho groucho 0 Sep 19 2022 Keys-Gtkr.pc3` `-rw------- 1 groucho groucho 0 Sep 19 2022 MemoDB.pc3` `-rw------- 1 groucho groucho 0 Sep 19 2022 DatebookDB.pc3` `-rw------- 1 groucho groucho 0 Sep 19 2022 ToDoDB.pc3` `-rw------- 1 groucho groucho 0 Sep 19 2022 jpilot.plugins` `-rw------- 1 groucho groucho 718 Dec 31 1969 AddressDB.pdb` `-rw------- 1 groucho groucho 378 Dec 31 1969 CalendarDB-PDat.pdb` `-rw------- 1 groucho groucho 1172 Dec 31 1969 ContactsDB-PAdd.pdb` `-rw------- 1 groucho groucho 360 Dec 31 1969 DatebookDB.pdb` `-rw------- 1 groucho groucho 472 Dec 31 1969 ExpenseDB.pdb` `-rw------- 1 groucho groucho 362 Dec 31 1969 MananaDB.pdb` `-rw------- 1 groucho groucho 362 Dec 31 1969 Memo32DB.pdb` `-rw------- 1 groucho groucho 362 Dec 31 1969 MemoDB.pdb` `-rw------- 1 groucho groucho 380 Dec 31 1969 MemosDB-PMem.pdb` `-rw------- 1 groucho groucho 380 Dec 31 1969 TasksDB-PTod.pdb` `-rw------- 1 groucho groucho 362 Dec 31 1969 ToDoDB.pdb` `~/.jpilot$ ` `~/.jpilot$ cd .jpilot` `~/.jpilot/.jpilot$ ` `~/.jpilot/.jpilot$ ls -lt` `total 476` `-rw------- 1 groucho groucho 14 Jun 22 08:48 jpilot.next_id` `-rw------- 1 groucho groucho 28260 Jun 22 08:48 jpilot.log` `-rw------- 1 groucho groucho 1873 Jun 22 08:48 jpilot.rc` `-rw------- 1 groucho groucho 126 Jun 22 08:48 jpilot.alarms` `-rw------- 1 groucho groucho 2331 Jun 21 22:01 AddressDB.pc3` `-rw------- 1 groucho groucho 306 Jun 21 11:01 DatebookDB.pc3` `-rw------- 1 groucho groucho 0 Jun 21 10:31 sync_pid` `-rw------- 1 groucho groucho 0 Jun 21 10:31 jpilot.install` `-rw------- 1 groucho groucho 18739 Jun 21 10:30 'Saved Preferences.prc'` `drwx------ 2 groucho groucho 16384 Jun 21 10:10 backup06211009` `lrwxrwxrwx 1 groucho groucho 14 Jun 21 10:09 backup -> backup06211009` `-rw------- 1 groucho groucho 102533 Jun 21 10:09 AddressDB.pdb` `-rw------- 1 groucho groucho 162492 Jun 21 10:09 DatebookDB.pdb` `drwx------ 2 groucho groucho 16384 Jun 7 07:12 backup06070711` `-rw------- 1 groucho groucho 37202 May 27 11:29 MemoDB.pdb` `-rw------- 1 groucho groucho 0 May 15 08:37 Keys-Gtkr.pc3` `-rw------- 1 groucho groucho 0 May 15 08:37 MemoDB.pc3` `-rw------- 1 groucho groucho 830 May 12 18:13 Keys-Gtkr.pdb` `drwx------ 2 groucho groucho 4096 May 12 17:52 backup_removed` `-rw------- 1 groucho groucho 362 Apr 20 08:53 ToDoDB.pdb` `-rw------- 1 groucho groucho 544 Apr 20 08:53 ExpenseDB.pdb` `-rw------- 1 groucho groucho 18047 Sep 29 2020 AddressDB.old` `-rw------- 1 groucho groucho 0 Jan 20 2020 ToDoDB.pc3` `-rw------- 1 groucho groucho 0 Jan 17 2020 ContactsDB-PAdd.pc3` `-rw------- 1 groucho groucho 0 Jan 17 2020 ContactsDB-PAdd.pc3.nouse` `-rw------- 1 groucho groucho 0 Jan 16 2020 ExpenseDB.pc3` `-rw------- 1 groucho groucho 0 Jan 15 2020 jpilot.plugins` `-rw------- 1 groucho groucho 378 Dec 31 1969 CalendarDB-PDat.nouse` `-rw------- 1 groucho groucho 378 Dec 31 1969 CalendarDB-PDat.pdb` `-rw------- 1 groucho groucho 1172 Dec 31 1969 ContactsDB-PAdd.pdb` `-rw------- 1 groucho groucho 1172 Dec 31 1969 ContactsDB-PAdd.pdb.nouse` `-rw------- 1 groucho groucho 362 Dec 31 1969 MananaDB.pdb` `-rw------- 1 groucho groucho 362 Dec 31 1969 Memo32DB.pdb` `-rw------- 1 groucho groucho 362 Dec 31 1969 Memo32DB.pdb.nouse` `-rw------- 1 groucho groucho 380 Dec 31 1969 MemosDB-PMem.pdb` `-rw------- 1 groucho groucho 380 Dec 31 1969 TasksDB-PTod.pdb` `~/.jpilot/.jpilot$` Evidently, the files with a 1969 date are / have been somehow mangled and that may hold (?) a clue as to the previously reported problem. But I have no idea as to how it may have happened. Maybe during the upgrade from Beowulf to Chimaera to Daedalus? Seems unlikely as J-Pilot should not have been touched as Debian/Devuan do not have that package in their repositories. ie: `jpilot`, `jpilot-plugins` and `pilot-link` are listed as \[installed, local\] by `apt`. And then there is the issue of having two `.jpilot` directories, one of which has to go. Q: how can I fix all this? Thanks in advance. Best, JHM
JM
Judd Montgomery
Sat, Jun 22, 2024 4:12 PM

On 6/22/24 08:43, Julius Henry Marx via Jpilot wrote:

One is that my current J-Pilot starts not with a *.desktop file but with a shell script.

Cannot recall *exactly* how that got to be so, but here it is:

#!/bin/bash

export JPILOT_HOME="/home/groucho/.jpilot"

jpilot -d

JPILOT_HOME tells jpilot to use that directory to store its files. If you didn't export that variable it would use the .jpilot in your home dir.

The -d is debug mode.

Seeing that this was so, I set up a regular *.desktop file for my Xfce desktop (via ‘Create Launcher’) like this:

[Desktop Entry]

Version=1.0

Type=Application

Name=J-Pilot

Comment=Palm Pilot

Exec=jpilot -d

If you want to use the JPILOT_HOME variable I think this will work:

Exec='JPILOT_HOME=/home/groucho/.jpilot jpilot"

You could also have the Exec run a script.

Icon=jpilot

Path=/home/groucho/.jpilot/.jpilot

I don't know you you got double .jpilot paths.
I am not seeing PATH in the docs. Perhaps I am missing it.
https://specifications.freedesktop.org/desktop-entry-spec/latest/

Terminal=false

StartupNotify=true

But it does not open the same J-Pilot instance. ie: it is empty of any data, unlike the one opened with the script.

Because JPILOT_HOME is different.

Setting up the *desktop file made me notice that, besides /home/groucho/.jpilot there is also a /home/groucho/.jpilot/.jpilot which seems to be the one opened by the script.

Again, I cannot recall how that got to be that way but one of them is not right.

Unfortunately, I found something else:

For whatever reason, in both directories, there are J-Pilot files with very strange dates:

~/.jpilot$ ls -lt

total 60

-rw------- 1 groucho groucho 2518 Jun 22 08:49 jpilot.log

-rw------- 1 groucho groucho 11 Jun 22 08:49 jpilot.next_id

-rw------- 1 groucho groucho 1878 Jun 22 08:49 jpilot.rc

-rw------- 1 groucho groucho 126 Jun 22 08:49 jpilot.alarms

-rw------- 1 groucho groucho 0 Sep 19 2022 AddressDB.pc3

-rw------- 1 groucho groucho 0 Sep 19 2022 ExpenseDB.pc3

-rw------- 1 groucho groucho 0 Sep 19 2022 Keys-Gtkr.pc3

-rw------- 1 groucho groucho 0 Sep 19 2022 MemoDB.pc3

-rw------- 1 groucho groucho 0 Sep 19 2022 DatebookDB.pc3

-rw------- 1 groucho groucho 0 Sep 19 2022 ToDoDB.pc3

-rw------- 1 groucho groucho 0 Sep 19 2022 jpilot.plugins

-rw------- 1 groucho groucho 718 Dec 31 1969 AddressDB.pdb

-rw------- 1 groucho groucho 378 Dec 31 1969 CalendarDB-PDat.pdb

-rw------- 1 groucho groucho 1172 Dec 31 1969 ContactsDB-PAdd.pdb

-rw------- 1 groucho groucho 360 Dec 31 1969 DatebookDB.pdb

-rw------- 1 groucho groucho 472 Dec 31 1969 ExpenseDB.pdb

-rw------- 1 groucho groucho 362 Dec 31 1969 MananaDB.pdb

-rw------- 1 groucho groucho 362 Dec 31 1969 Memo32DB.pdb

-rw------- 1 groucho groucho 362 Dec 31 1969 MemoDB.pdb

-rw------- 1 groucho groucho 380 Dec 31 1969 MemosDB-PMem.pdb

-rw------- 1 groucho groucho 380 Dec 31 1969 TasksDB-PTod.pdb

-rw------- 1 groucho groucho 362 Dec 31 1969 ToDoDB.pdb

~/.jpilot$

~/.jpilot$ cd .jpilot

~/.jpilot/.jpilot$

~/.jpilot/.jpilot$ ls -lt

total 476

-rw------- 1 groucho groucho 14 Jun 22 08:48 jpilot.next_id

-rw------- 1 groucho groucho 28260 Jun 22 08:48 jpilot.log

-rw------- 1 groucho groucho 1873 Jun 22 08:48 jpilot.rc

-rw------- 1 groucho groucho 126 Jun 22 08:48 jpilot.alarms

-rw------- 1 groucho groucho 2331 Jun 21 22:01 AddressDB.pc3

-rw------- 1 groucho groucho 306 Jun 21 11:01 DatebookDB.pc3

-rw------- 1 groucho groucho 0 Jun 21 10:31 sync_pid

-rw------- 1 groucho groucho 0 Jun 21 10:31 jpilot.install

-rw------- 1 groucho groucho 18739 Jun 21 10:30 'Saved Preferences.prc'

drwx------ 2 groucho groucho 16384 Jun 21 10:10 backup06211009

lrwxrwxrwx 1 groucho groucho 14 Jun 21 10:09 backup -> backup06211009

-rw------- 1 groucho groucho 102533 Jun 21 10:09 AddressDB.pdb

-rw------- 1 groucho groucho 162492 Jun 21 10:09 DatebookDB.pdb

drwx------ 2 groucho groucho 16384 Jun 7 07:12 backup06070711

-rw------- 1 groucho groucho 37202 May 27 11:29 MemoDB.pdb

-rw------- 1 groucho groucho 0 May 15 08:37 Keys-Gtkr.pc3

-rw------- 1 groucho groucho 0 May 15 08:37 MemoDB.pc3

-rw------- 1 groucho groucho 830 May 12 18:13 Keys-Gtkr.pdb

drwx------ 2 groucho groucho 4096 May 12 17:52 backup_removed

-rw------- 1 groucho groucho 362 Apr 20 08:53 ToDoDB.pdb

-rw------- 1 groucho groucho 544 Apr 20 08:53 ExpenseDB.pdb

-rw------- 1 groucho groucho 18047 Sep 29 2020 AddressDB.old

-rw------- 1 groucho groucho 0 Jan 20 2020 ToDoDB.pc3

-rw------- 1 groucho groucho 0 Jan 17 2020 ContactsDB-PAdd.pc3

-rw------- 1 groucho groucho 0 Jan 17 2020 ContactsDB-PAdd.pc3.nouse

-rw------- 1 groucho groucho 0 Jan 16 2020 ExpenseDB.pc3

-rw------- 1 groucho groucho 0 Jan 15 2020 jpilot.plugins

-rw------- 1 groucho groucho 378 Dec 31 1969 CalendarDB-PDat.nouse

-rw------- 1 groucho groucho 378 Dec 31 1969 CalendarDB-PDat.pdb

-rw------- 1 groucho groucho 1172 Dec 31 1969 ContactsDB-PAdd.pdb

-rw------- 1 groucho groucho 1172 Dec 31 1969 ContactsDB-PAdd.pdb.nouse

-rw------- 1 groucho groucho 362 Dec 31 1969 MananaDB.pdb

-rw------- 1 groucho groucho 362 Dec 31 1969 Memo32DB.pdb

-rw------- 1 groucho groucho 362 Dec 31 1969 Memo32DB.pdb.nouse

-rw------- 1 groucho groucho 380 Dec 31 1969 MemosDB-PMem.pdb

-rw------- 1 groucho groucho 380 Dec 31 1969 TasksDB-PTod.pdb

~/.jpilot/.jpilot$

Evidently, the files with a 1969 date are / have been somehow mangled and that may hold (?) a clue as to the previously reported problem.

But I have no idea as to how it may have happened.

The dates are not strange. They are the dates from the PalmOS and when you sync the dates are compared. If you didn't sync then jpilot is probably using the date of the Unix Epoch.

The extra .jpilot was probably created when you had JPILOT_HOME set to point to /home/groucho/.jpilot/.jpilot You can probably just delete that dir. Back it up if you are worried. ls -ld  /home/groucho/.jpilot/.jpilot will tell you when that directory was created.

Maybe during the upgrade from Beowulf to Chimaera to Daedalus? Seems unlikely as J-Pilot should not have been touched as Debian/Devuan do not have that package in their repositories.

ie: jpilot, jpilot-plugins and pilot-link are listed as [installed, local] by apt.

And then there is the issue of having two .jpilot directories, one of which has to go.

Q: how can I fix all this?

Delete the new one.

Thanks in advance.

Best,

JHM

Jpilot mailing list --
jpilot@lists.jpilot.org
To unsubscribe send an email to
jpilot-leave@lists.jpilot.org

On 6/22/24 08:43, Julius Henry Marx via Jpilot wrote: > One is that my current J-Pilot starts not with a `*.desktop` file but with a shell script. > > Cannot recall \*exactly\* how that got to be so, but here it is: > > `#!/bin/bash` > > `export JPILOT_HOME="/home/groucho/.jpilot"` > > `jpilot -d` JPILOT_HOME tells jpilot to use that directory to store its files. If you didn't export that variable it would use the .jpilot in your home dir. The -d is debug mode. > Seeing that this was so, I set up a regular `*.desktop` file for my Xfce desktop (via ‘Create Launcher’) like this: > > `[Desktop Entry]` > > `Version=1.0` > > `Type=Application` > > `Name=J-Pilot` > > `Comment=Palm Pilot` > > `Exec=jpilot -d` If you want to use the JPILOT_HOME variable I think this will work: Exec='JPILOT_HOME=/home/groucho/.jpilot jpilot" You could also have the Exec run a script. > `Icon=jpilot` > > `Path=/home/groucho/.jpilot/.jpilot` I don't know you you got double .jpilot paths. I am not seeing PATH in the docs. Perhaps I am missing it. https://specifications.freedesktop.org/desktop-entry-spec/latest/ > `Terminal=false` > > `StartupNotify=true` > > But it does not open the same J-Pilot instance. ie: it is empty of any data, unlike the one opened with the script. Because JPILOT_HOME is different. > Setting up the \*desktop file made me notice that, besides `/home/groucho/.jpilot` there is also a `/home/groucho/.jpilot/.jpilot` which seems to be the one opened by the script. > > Again, I cannot recall how that got to be that way but one of them is not right. > > Unfortunately, I found something else: > > For whatever reason, in both directories, there are J-Pilot files with *very* strange dates: > > `~/.jpilot$ ls -lt` > > `total 60` > > `-rw------- 1 groucho groucho 2518 Jun 22 08:49 jpilot.log` > > `-rw------- 1 groucho groucho 11 Jun 22 08:49 jpilot.next_id` > > `-rw------- 1 groucho groucho 1878 Jun 22 08:49 jpilot.rc` > > `-rw------- 1 groucho groucho 126 Jun 22 08:49 jpilot.alarms` > > `-rw------- 1 groucho groucho 0 Sep 19 2022 AddressDB.pc3` > > `-rw------- 1 groucho groucho 0 Sep 19 2022 ExpenseDB.pc3` > > `-rw------- 1 groucho groucho 0 Sep 19 2022 Keys-Gtkr.pc3` > > `-rw------- 1 groucho groucho 0 Sep 19 2022 MemoDB.pc3` > > `-rw------- 1 groucho groucho 0 Sep 19 2022 DatebookDB.pc3` > > `-rw------- 1 groucho groucho 0 Sep 19 2022 ToDoDB.pc3` > > `-rw------- 1 groucho groucho 0 Sep 19 2022 jpilot.plugins` > > `-rw------- 1 groucho groucho 718 Dec 31 1969 AddressDB.pdb` > > `-rw------- 1 groucho groucho 378 Dec 31 1969 CalendarDB-PDat.pdb` > > `-rw------- 1 groucho groucho 1172 Dec 31 1969 ContactsDB-PAdd.pdb` > > `-rw------- 1 groucho groucho 360 Dec 31 1969 DatebookDB.pdb` > > `-rw------- 1 groucho groucho 472 Dec 31 1969 ExpenseDB.pdb` > > `-rw------- 1 groucho groucho 362 Dec 31 1969 MananaDB.pdb` > > `-rw------- 1 groucho groucho 362 Dec 31 1969 Memo32DB.pdb` > > `-rw------- 1 groucho groucho 362 Dec 31 1969 MemoDB.pdb` > > `-rw------- 1 groucho groucho 380 Dec 31 1969 MemosDB-PMem.pdb` > > `-rw------- 1 groucho groucho 380 Dec 31 1969 TasksDB-PTod.pdb` > > `-rw------- 1 groucho groucho 362 Dec 31 1969 ToDoDB.pdb` > > `~/.jpilot$ ` > > `~/.jpilot$ cd .jpilot` > > `~/.jpilot/.jpilot$ ` > > `~/.jpilot/.jpilot$ ls -lt` > > `total 476` > > `-rw------- 1 groucho groucho 14 Jun 22 08:48 jpilot.next_id` > > `-rw------- 1 groucho groucho 28260 Jun 22 08:48 jpilot.log` > > `-rw------- 1 groucho groucho 1873 Jun 22 08:48 jpilot.rc` > > `-rw------- 1 groucho groucho 126 Jun 22 08:48 jpilot.alarms` > > `-rw------- 1 groucho groucho 2331 Jun 21 22:01 AddressDB.pc3` > > `-rw------- 1 groucho groucho 306 Jun 21 11:01 DatebookDB.pc3` > > `-rw------- 1 groucho groucho 0 Jun 21 10:31 sync_pid` > > `-rw------- 1 groucho groucho 0 Jun 21 10:31 jpilot.install` > > `-rw------- 1 groucho groucho 18739 Jun 21 10:30 'Saved Preferences.prc'` > > `drwx------ 2 groucho groucho 16384 Jun 21 10:10 backup06211009` > > `lrwxrwxrwx 1 groucho groucho 14 Jun 21 10:09 backup -> backup06211009` > > `-rw------- 1 groucho groucho 102533 Jun 21 10:09 AddressDB.pdb` > > `-rw------- 1 groucho groucho 162492 Jun 21 10:09 DatebookDB.pdb` > > `drwx------ 2 groucho groucho 16384 Jun 7 07:12 backup06070711` > > `-rw------- 1 groucho groucho 37202 May 27 11:29 MemoDB.pdb` > > `-rw------- 1 groucho groucho 0 May 15 08:37 Keys-Gtkr.pc3` > > `-rw------- 1 groucho groucho 0 May 15 08:37 MemoDB.pc3` > > `-rw------- 1 groucho groucho 830 May 12 18:13 Keys-Gtkr.pdb` > > `drwx------ 2 groucho groucho 4096 May 12 17:52 backup_removed` > > `-rw------- 1 groucho groucho 362 Apr 20 08:53 ToDoDB.pdb` > > `-rw------- 1 groucho groucho 544 Apr 20 08:53 ExpenseDB.pdb` > > `-rw------- 1 groucho groucho 18047 Sep 29 2020 AddressDB.old` > > `-rw------- 1 groucho groucho 0 Jan 20 2020 ToDoDB.pc3` > > `-rw------- 1 groucho groucho 0 Jan 17 2020 ContactsDB-PAdd.pc3` > > `-rw------- 1 groucho groucho 0 Jan 17 2020 ContactsDB-PAdd.pc3.nouse` > > `-rw------- 1 groucho groucho 0 Jan 16 2020 ExpenseDB.pc3` > > `-rw------- 1 groucho groucho 0 Jan 15 2020 jpilot.plugins` > > `-rw------- 1 groucho groucho 378 Dec 31 1969 CalendarDB-PDat.nouse` > > `-rw------- 1 groucho groucho 378 Dec 31 1969 CalendarDB-PDat.pdb` > > `-rw------- 1 groucho groucho 1172 Dec 31 1969 ContactsDB-PAdd.pdb` > > `-rw------- 1 groucho groucho 1172 Dec 31 1969 ContactsDB-PAdd.pdb.nouse` > > `-rw------- 1 groucho groucho 362 Dec 31 1969 MananaDB.pdb` > > `-rw------- 1 groucho groucho 362 Dec 31 1969 Memo32DB.pdb` > > `-rw------- 1 groucho groucho 362 Dec 31 1969 Memo32DB.pdb.nouse` > > `-rw------- 1 groucho groucho 380 Dec 31 1969 MemosDB-PMem.pdb` > > `-rw------- 1 groucho groucho 380 Dec 31 1969 TasksDB-PTod.pdb` > > `~/.jpilot/.jpilot$` > > Evidently, the files with a 1969 date are / have been somehow mangled and that may hold (?) a clue as to the previously reported problem. > > But I have no idea as to how it may have happened. The dates are not strange. They are the dates from the PalmOS and when you sync the dates are compared. If you didn't sync then jpilot is probably using the date of the Unix Epoch. The extra .jpilot was probably created when you had JPILOT_HOME set to point to /home/groucho/.jpilot/.jpilot You can probably just delete that dir. Back it up if you are worried. ls -ld /home/groucho/.jpilot/.jpilot will tell you when that directory was created. > Maybe during the upgrade from Beowulf to Chimaera to Daedalus? Seems unlikely as J-Pilot should not have been touched as Debian/Devuan do not have that package in their repositories. > > ie: `jpilot`, `jpilot-plugins` and `pilot-link` are listed as \[installed, local\] by `apt`. > > And then there is the issue of having two `.jpilot` directories, one of which has to go. > > Q: how can I fix all this? Delete the new one. > Thanks in advance. > > Best, > > JHM > _______________________________________________ > Jpilot mailing list -- > jpilot@lists.jpilot.org > To unsubscribe send an email to > jpilot-leave@lists.jpilot.org
S
sawbona@gmx.net
Sat, Jun 22, 2024 7:28 PM

Hello:

… tried to replicate your problem …

… cannot see attached screenshot.

There’s no screenshot attached.

Just the copy+paste from the terminal, from [Jun21 10:51] jpilot[17451] … to where it reads —- snip —-.

That said, what is happening is new and export JPILOT_HOME="/home/groucho/.jpilot" has been there for the longest while, so I do not think it is related.

What the terminal prints out is the segfault when j-pilot crashes.

Thank you for your input.

Best,

JHM

Hello: > … tried to replicate your problem … > > … cannot see attached screenshot. There’s no screenshot attached. Just the copy+paste from the terminal, from `[Jun21 10:51] jpilot[17451] … `to where it reads `—- snip —-`. That said, what is happening is *new* and `export JPILOT_HOME="/home/groucho/.jpilot"` has been there for the longest while, so I do not think it is related. What the terminal prints out is the `segfault` when j-pilot crashes. Thank you for your input. Best, JHM` `
S
sawbona@gmx.net
Sat, Jun 22, 2024 8:41 PM

Hello Judd:

Both .jpilot directories are in my /home/groucho directory:

ie: /home/groucho/.jpilot and /home/groucho/.jpilot/.jpilot

If I start jpilot with the *.desktop file I get an empty instance.

ie: no data

So I deleted all the files in the first .jpilot directory, copied over the contents of the second .jpilot directory (deleting it afterwards) and started jpilot with the *.desktop file.

This solved that problem and now I have just one working .pilot directory.

—-

What remains is the segfault described in my previous post.

The dmesg printout would indicate that it is the same in both cases:

[Jun21 10:51] jpilot[17451]: segfault at 9 ip 00007fb599c9acb6 sp 00007ffd539ee408 error 4 in libc.so.6[7fb599c17000+155000] likely on CPU 0 (core 0, socket 0)

[ +0.000023] Code: 00 00 66 90 66 0f ef c0 66 0f ef c9 66 0f ef d2 66 0f ef db 48 89 f8 48 89 f9 48 81 e1 ff 0f 00 00 48 81 f9 cf 0f 00 00 77 6a <f3> 0f 6f 20 66 0f 74 e0 66 0f d7 d4 85 d2 74 04 0f bc c2 c3 48 83

—- snip —-

[Jun22 17:03] jpilot[7108]: segfault at 9 ip 00007f9e63717cb6 sp 00007ffe7a714eb8 error 4 in

libc.so.6[7f9e63694000+155000] likely on CPU 1 (core 1, socket 0)

[ +0.000030] Code: 00 00 66 90 66 0f ef c0 66 0f ef c9 66 0f ef d2 66 0f ef db 48 89 f8 48 89 f9 48 81 e1 ff 0f 00 00 48 81 f9 cf 0f 00 00 77 6a <f3> 0f 6f 20 66 0f 74 e0 66 0f d7 d4 85 d2 74 04 0f bc c2 c3 48 83

—- snip —-

ie:

segfault at 9 ip 00007f9e63717cb6 sp 00007ffe7a714eb8 error 4 in libc.so.6

segfault at 9 ip 00007fb599c9acb6 sp 00007ffd539ee408 error 4 in libc.so.6

The J-Pilot log files do not say anything about the crash, which makes sense: it crashed.

On a hunch, I edited the *.desktop file so that J-Pilot would start ‘plain vanilla’ ie: not in debug mode.

Problem solved, no crash.

For whatever reason related libc.so.6 and whatevr it does, starting J-Pilot in debug mode will cause it to crash when an event is created or edited to have a yearly frequency.

As mentioned in my previous post, this only happens with the yearly frequency: creation or edition of daily, weekly or monthly frequencies do not cause a crash.

If you need me to run any tests, please let me know.

Thank you for taking the time to write back.

Best,

JHM

Hello Judd: Both `.jpilot` directories are in my `/home/groucho` directory: ie: `/home/groucho/.jpilot` and `/home/groucho/.jpilot/.jpilot` If I start `jpilot` with the `*.desktop` file I get an empty instance. ie: no data So I deleted all the files in the first `.jpilot` directory, copied over the contents of the second `.jpilot` directory (deleting it afterwards) and started jpilot with the `*.desktop `file. This solved *that* problem and now I have just one working `.pilot` directory. —- What remains is the segfault described in my previous post. The `dmesg `printout would indicate that it is the same in both cases: `[Jun21 10:51] jpilot[17451]: segfault at 9 ip 00007fb599c9acb6 sp 00007ffd539ee408 error 4 in libc.so.6[7fb599c17000+155000] likely on CPU 0 (core 0, socket 0)` `[ +0.000023] Code: 00 00 66 90 66 0f ef c0 66 0f ef c9 66 0f ef d2 66 0f ef db 48 89 f8 48 89 f9 48 81 e1 ff 0f 00 00 48 81 f9 cf 0f 00 00 77 6a <f3> 0f 6f 20 66 0f 74 e0 66 0f d7 d4 85 d2 74 04 0f bc c2 c3 48 83` `—- snip —-` `[Jun22 17:03] jpilot[7108]: segfault at 9 ip 00007f9e63717cb6 sp 00007ffe7a714eb8 error 4 in` `libc.so.6[7f9e63694000+155000] likely on CPU 1 (core 1, socket 0)` `[ +0.000030] Code: 00 00 66 90 66 0f ef c0 66 0f ef c9 66 0f ef d2 66 0f ef db 48 89 f8 48 89 f9 48 81 e1 ff 0f 00 00 48 81 f9 cf 0f 00 00 77 6a <f3> 0f 6f 20 66 0f 74 e0 66 0f d7 d4 85 d2 74 04 0f bc c2 c3 48 83` ` —- snip —-` ie: `segfault at 9 ip 00007f9e63717cb6 sp 00007ffe7a714eb8 error 4 in libc.so.6` `segfault at 9 ip 00007fb599c9acb6 sp 00007ffd539ee408 error 4 in libc.so.6` The J-Pilot log files do not say anything about the crash, which makes sense: it crashed. On a hunch, I edited the `*.desktop` file so that J-Pilot would start ‘plain vanilla’ ie: *not* in debug mode. Problem solved, no crash. For whatever reason related `libc.so.6` and whatevr it does, starting J-Pilot in debug mode will cause it to crash when an event is created or edited to have a **yearly** frequency. As mentioned in my previous post, this only happens with the yearly frequency: creation or edition of daily, weekly or monthly frequencies do not cause a crash. If you need me to run any tests, please let me know. Thank you for taking the time to write back. Best, JHM
Empathy v1.0   2024 ©Harmonylists.com