Ulf, Thank you. Your instructions worked. Regards, John On Mon, Jun 22, 2026 at 5:08 AM Ulf Zibis <Ulf.Zibis@cosoco.de> wrote: > Hi John, > > 1. Copy your data from /root/.jpilot/ to $HOME/.jpilot/ > > 2. Correct the owner of all files inside by context menu in file manager or > sudo chown -hR user:user $HOME/.jpilot > or > sudo chown -hR 1000:1000 $HOME/.jpilot > > Hope, that helps. > -Ulf > > Am 22.06.26 um 06:10 schrieb John Morrow: > > Ulf, > > > > I tried your suggestion and unfortunately I can still only see my data > if I > > start jpilot as root. I now see > > > > john@Lenovo-ideapad-320-15ABR:~$ id > > uid=1000(john) gid=1000(john) > > > groups=1000(john),4(adm),20(dialout),24(cdrom),27(sudo),30(dip),46(plugdev),100(users),105(lpadmin),124(sambashare) > > > > and when I start jpilot from the command line I get the following error > > messages: > > > > john@Lenovo-ideapad-320-15ABR:~$ jpilot > > > > (jpilot:2134): Gtk-CRITICAL **: 20:42:56.126: gtk_list_store_get_path: > > assertion 'iter->stamp == priv->stamp' failed > > > > (jpilot:2134): Gtk-CRITICAL **: 20:42:56.126: > > gtk_tree_selection_select_path: assertion 'path != NULL' failed > > > > I have no idea what to do with that, so any and all help is greatly > > appreciated. > > > > Regards, > > John > > > > > > On Wed, Jun 3, 2026 at 12:55 AM Ulf Zibis <Ulf.Zibis@cosoco.de> wrote: > > > >> @ Judd ... > >> > >> Hi Judd, > >> could you add such hint on your web site www.JPilot.org ? > >> > >> Also it cold be useful, if the JPilot application would show this in > case, > >> sync doesn't work. > >> > >> Regards, > >> Ulf > >> > >> Am 03.06.26 um 01:21 schrieb Ulf Zibis: > >>> Hi John and Paul, > >>> > >>> if you run JPilot as root, your data will be stored in /root/.jpilot. > >>> If you later run JPilot as user it will look into $HOME/.jpilot. That's > >> why you don't see anything. > >>> In standard configuration the user has no rights to sync, because it > >> needs the rights of group `dialout`. > >>> You can check if your user has `dialout` rights with the command `id`. > >>> If not, on Ubuntu you need to run `sudo usermod -a -G dialout $USER` to > >> add this group rights to your user account. > >>> Then reboot your machine to make the command aktive. > >>> After, you should be able to sync your Palm device as normal user. > >>> > >>> Note: It is not recommended to run graphical applications as root on > >> Ubuntu, because it can cause corruption of your file in $HOME/. > >>> -Ulf > >>> > >>> Am 01.06.26 um 09:12 schrieb John Morrow: > >>>> Paul, > >>>> > >>>> I took your suggestion and started JPilot as root, installed my > username > >>>> and synced. After a few attempts it worked. I had to close and re-open > >> the > >>>> terminal window but in the end, all my data from the PDA is now > visible > >> in > >>>> JPilot. I don't know what a "dialout group" is, but apparently I > >>>> didn't need to change it. Interesting, if I don't use the sudo > command, > >>>> the program opens without displaying any data. > >>>> > >>>> Thanks to all! > >>>> John Morrow > >>>> > >>>> On Sat, Mar 14, 2026 at 5:48 AM Ulf Zibis <Ulf.Zibis@cosoco.de> > wrote: > >>>> > >>>>> Hi Paul, > >>>>> > >>>>> I do not understand, why running JPilot as root should be good for. I > >> more > >>>>> think, it could be dangerous. > >>>>> > >>>>> For synching it's enough to add group `dialout` to the normal user. > >>>>> > >>>>> -Ulf > >>>>> > >>>>> Am 13.03.26 um 01:38 schrieb Paul Donlan: > >>>>>> Try opening Palm Pilot on *Command Line*: sudo jpilot > >>>>>> Then your password > >>>>>> Then open "File" and Press "Install User" > >>>>>> After you have installed your user name, *Sync* handheld. > >>>>>> It should work > >>>>>> > >>>>>> _______________________________________________ > >>>>>> Jpilot mailing list -- jpilot@lists.jpilot.org > >>>>>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org > >>>>> _______________________________________________ > >>>>> Jpilot mailing list -- jpilot@lists.jpilot.org > >>>>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org > >>>>> > >>>> _______________________________________________ > >>>> Jpilot mailing list -- jpilot@lists.jpilot.org > >>>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org > >>> _______________________________________________ > >>> Jpilot mailing list -- jpilot@lists.jpilot.org > >>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org > >> _______________________________________________ > >> Jpilot mailing list -- jpilot@lists.jpilot.org > >> To unsubscribe send an email to jpilot-leave@lists.jpilot.org > >> > > _______________________________________________ > > Jpilot mailing list -- jpilot@lists.jpilot.org > > To unsubscribe send an email to jpilot-leave@lists.jpilot.org > _______________________________________________ > Jpilot mailing list -- jpilot@lists.jpilot.org > To unsubscribe send an email to jpilot-leave@lists.jpilot.org >

Hello, Having trouble building v2.0.3  on a Slack 15 system. This, an initial step to resuscitating / adopting the currently orphaned Slackbuild. I see there's no configure script, but configure.in is there, so I tried autoconf. And got many errors along the lines of "error: possibly undefined macro" It did produce a configure script, though, and I gave it a try. It gives me an error: ./configure: line 2194: `AM_INIT_AUTOMAKE(1.8)' So I gave up on that. Next try: start with fresh source, and run: autoreconf -fi It repeatedly told me that the autoconf input should be named 'configure.ac', not 'configure.in' ... but it didn't seem to be a showstopper so I pushed on. Of  concern: it made a po/Makefile.in.in .... that can't be right. But pushing on: ./configure is there. I run it, and get one error: config.status: error: po/Makefile.in.in was not created by intltoolize. But push on! make Starts out OK but bombs with an error when running msgfmt on ru.po: ru.po:170: number of format specifications in 'msgid' and 'msgstr' does not match /usr/bin/msgfmt: found 1 fatal error So I'm stuck. Anyone recognize this problem, or have any tips? I rather suspect all due to a single problem early on in the process, perhaps in one of the files that autoreconf uses. thanks! v/r Judah milgram@cgpp.com On 7/7/26 02:30, John Morrow wrote: > Ulf, > Thank you. Your instructions worked. > Regards, > John > > On Mon, Jun 22, 2026 at 5:08 AM Ulf Zibis <Ulf.Zibis@cosoco.de> wrote: > >> Hi John, >> >> 1. Copy your data from /root/.jpilot/ to $HOME/.jpilot/ >> >> 2. Correct the owner of all files inside by context menu in file manager or >> sudo chown -hR user:user $HOME/.jpilot >> or >> sudo chown -hR 1000:1000 $HOME/.jpilot >> >> Hope, that helps. >> -Ulf >> >> Am 22.06.26 um 06:10 schrieb John Morrow: >>> Ulf, >>> >>> I tried your suggestion and unfortunately I can still only see my data >> if I >>> start jpilot as root. I now see >>> >>> john@Lenovo-ideapad-320-15ABR:~$ id >>> uid=1000(john) gid=1000(john) >>> >> groups=1000(john),4(adm),20(dialout),24(cdrom),27(sudo),30(dip),46(plugdev),100(users),105(lpadmin),124(sambashare) >>> and when I start jpilot from the command line I get the following error >>> messages: >>> >>> john@Lenovo-ideapad-320-15ABR:~$ jpilot >>> >>> (jpilot:2134): Gtk-CRITICAL **: 20:42:56.126: gtk_list_store_get_path: >>> assertion 'iter->stamp == priv->stamp' failed >>> >>> (jpilot:2134): Gtk-CRITICAL **: 20:42:56.126: >>> gtk_tree_selection_select_path: assertion 'path != NULL' failed >>> >>> I have no idea what to do with that, so any and all help is greatly >>> appreciated. >>> >>> Regards, >>> John >>> >>> >>> On Wed, Jun 3, 2026 at 12:55 AM Ulf Zibis <Ulf.Zibis@cosoco.de> wrote: >>> >>>> @ Judd ... >>>> >>>> Hi Judd, >>>> could you add such hint on your web site www.JPilot.org ? >>>> >>>> Also it cold be useful, if the JPilot application would show this in >> case, >>>> sync doesn't work. >>>> >>>> Regards, >>>> Ulf >>>> >>>> Am 03.06.26 um 01:21 schrieb Ulf Zibis: >>>>> Hi John and Paul, >>>>> >>>>> if you run JPilot as root, your data will be stored in /root/.jpilot. >>>>> If you later run JPilot as user it will look into $HOME/.jpilot. That's >>>> why you don't see anything. >>>>> In standard configuration the user has no rights to sync, because it >>>> needs the rights of group `dialout`. >>>>> You can check if your user has `dialout` rights with the command `id`. >>>>> If not, on Ubuntu you need to run `sudo usermod -a -G dialout $USER` to >>>> add this group rights to your user account. >>>>> Then reboot your machine to make the command aktive. >>>>> After, you should be able to sync your Palm device as normal user. >>>>> >>>>> Note: It is not recommended to run graphical applications as root on >>>> Ubuntu, because it can cause corruption of your file in $HOME/. >>>>> -Ulf >>>>> >>>>> Am 01.06.26 um 09:12 schrieb John Morrow: >>>>>> Paul, >>>>>> >>>>>> I took your suggestion and started JPilot as root, installed my >> username >>>>>> and synced. After a few attempts it worked. I had to close and re-open >>>> the >>>>>> terminal window but in the end, all my data from the PDA is now >> visible >>>> in >>>>>> JPilot. I don't know what a "dialout group" is, but apparently I >>>>>> didn't need to change it. Interesting, if I don't use the sudo >> command, >>>>>> the program opens without displaying any data. >>>>>> >>>>>> Thanks to all! >>>>>> John Morrow >>>>>> >>>>>> On Sat, Mar 14, 2026 at 5:48 AM Ulf Zibis <Ulf.Zibis@cosoco.de> >> wrote: >>>>>>> Hi Paul, >>>>>>> >>>>>>> I do not understand, why running JPilot as root should be good for. I >>>> more >>>>>>> think, it could be dangerous. >>>>>>> >>>>>>> For synching it's enough to add group `dialout` to the normal user. >>>>>>> >>>>>>> -Ulf >>>>>>> >>>>>>> Am 13.03.26 um 01:38 schrieb Paul Donlan: >>>>>>>> Try opening Palm Pilot on *Command Line*: sudo jpilot >>>>>>>> Then your password >>>>>>>> Then open "File" and Press "Install User" >>>>>>>> After you have installed your user name, *Sync* handheld. >>>>>>>> It should work >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Jpilot mailing list -- jpilot@lists.jpilot.org >>>>>>>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org >>>>>>> _______________________________________________ >>>>>>> Jpilot mailing list -- jpilot@lists.jpilot.org >>>>>>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org >>>>>>> >>>>>> _______________________________________________ >>>>>> Jpilot mailing list -- jpilot@lists.jpilot.org >>>>>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org >>>>> _______________________________________________ >>>>> Jpilot mailing list -- jpilot@lists.jpilot.org >>>>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org >>>> _______________________________________________ >>>> Jpilot mailing list -- jpilot@lists.jpilot.org >>>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org >>>> >>> _______________________________________________ >>> Jpilot mailing list -- jpilot@lists.jpilot.org >>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org >> _______________________________________________ >> Jpilot mailing list -- jpilot@lists.jpilot.org >> To unsubscribe send an email to jpilot-leave@lists.jpilot.org >> > _______________________________________________ > Jpilot mailing list -- jpilot@lists.jpilot.org > To unsubscribe send an email to jpilot-leave@lists.jpilot.org -- ===== milgram@cgpp.com 301-257-7069

Hello Judah, maybe this helps: https://eklausmeier.goip.de/blog/2025/03-06-building-j-pilot-and-pilot-link-on-linux Regards, Elmar. On Sun, Jul 26, 2026 at 10:01 PM J. Milgram via Jpilot < jpilot@lists.jpilot.org> wrote: > > Hello, > > Having trouble building v2.0.3 on a Slack 15 system. This, an initial > step to resuscitating / adopting the currently orphaned Slackbuild. > > I see there's no configure script, but configure.in is there, so I tried > autoconf. And got many errors along the lines of "error: possibly > undefined macro" > > It did produce a configure script, though, and I gave it a try. It gives > me an error: ./configure: line 2194: `AM_INIT_AUTOMAKE(1.8)' > > So I gave up on that. Next try: start with fresh source, and run: > > autoreconf -fi > > It repeatedly told me that the autoconf input should be named > 'configure.ac', not 'configure.in' ... but it didn't seem to be a > showstopper so I pushed on. > > Of concern: it made a po/Makefile.in.in .... that can't be right. But > pushing on: > > ./configure is there. I run it, and get one error: > > config.status: error: po/Makefile.in.in was not created by intltoolize. > > But push on! > > make > > Starts out OK but bombs with an error when running msgfmt on ru.po: > > ru.po:170: number of format specifications in 'msgid' and 'msgstr' does > not match > /usr/bin/msgfmt: found 1 fatal error > > So I'm stuck. Anyone recognize this problem, or have any tips? I rather > suspect all due to a single problem early on in the process, perhaps in > one of the files that autoreconf uses. > > thanks! > > v/r > Judah > > milgram@cgpp.com > > > On 7/7/26 02:30, John Morrow wrote: > > Ulf, > > Thank you. Your instructions worked. > > Regards, > > John > > > > On Mon, Jun 22, 2026 at 5:08 AM Ulf Zibis <Ulf.Zibis@cosoco.de> wrote: > > > >> Hi John, > >> > >> 1. Copy your data from /root/.jpilot/ to $HOME/.jpilot/ > >> > >> 2. Correct the owner of all files inside by context menu in file > manager or > >> sudo chown -hR user:user $HOME/.jpilot > >> or > >> sudo chown -hR 1000:1000 $HOME/.jpilot > >> > >> Hope, that helps. > >> -Ulf > >> > >> Am 22.06.26 um 06:10 schrieb John Morrow: > >>> Ulf, > >>> > >>> I tried your suggestion and unfortunately I can still only see my data > >> if I > >>> start jpilot as root. I now see > >>> > >>> john@Lenovo-ideapad-320-15ABR:~$ id > >>> uid=1000(john) gid=1000(john) > >>> > >> > groups=1000(john),4(adm),20(dialout),24(cdrom),27(sudo),30(dip),46(plugdev),100(users),105(lpadmin),124(sambashare) > >>> and when I start jpilot from the command line I get the following error > >>> messages: > >>> > >>> john@Lenovo-ideapad-320-15ABR:~$ jpilot > >>> > >>> (jpilot:2134): Gtk-CRITICAL **: 20:42:56.126: gtk_list_store_get_path: > >>> assertion 'iter->stamp == priv->stamp' failed > >>> > >>> (jpilot:2134): Gtk-CRITICAL **: 20:42:56.126: > >>> gtk_tree_selection_select_path: assertion 'path != NULL' failed > >>> > >>> I have no idea what to do with that, so any and all help is greatly > >>> appreciated. > >>> > >>> Regards, > >>> John > >>> > >>> > >>> On Wed, Jun 3, 2026 at 12:55 AM Ulf Zibis <Ulf.Zibis@cosoco.de> wrote: > >>> > >>>> @ Judd ... > >>>> > >>>> Hi Judd, > >>>> could you add such hint on your web site www.JPilot.org ? > >>>> > >>>> Also it cold be useful, if the JPilot application would show this in > >> case, > >>>> sync doesn't work. > >>>> > >>>> Regards, > >>>> Ulf > >>>> > >>>> Am 03.06.26 um 01:21 schrieb Ulf Zibis: > >>>>> Hi John and Paul, > >>>>> > >>>>> if you run JPilot as root, your data will be stored in /root/.jpilot. > >>>>> If you later run JPilot as user it will look into $HOME/.jpilot. > That's > >>>> why you don't see anything. > >>>>> In standard configuration the user has no rights to sync, because it > >>>> needs the rights of group `dialout`. > >>>>> You can check if your user has `dialout` rights with the command > `id`. > >>>>> If not, on Ubuntu you need to run `sudo usermod -a -G dialout $USER` > to > >>>> add this group rights to your user account. > >>>>> Then reboot your machine to make the command aktive. > >>>>> After, you should be able to sync your Palm device as normal user. > >>>>> > >>>>> Note: It is not recommended to run graphical applications as root on > >>>> Ubuntu, because it can cause corruption of your file in $HOME/. > >>>>> -Ulf > >>>>> > >>>>> Am 01.06.26 um 09:12 schrieb John Morrow: > >>>>>> Paul, > >>>>>> > >>>>>> I took your suggestion and started JPilot as root, installed my > >> username > >>>>>> and synced. After a few attempts it worked. I had to close and > re-open > >>>> the > >>>>>> terminal window but in the end, all my data from the PDA is now > >> visible > >>>> in > >>>>>> JPilot. I don't know what a "dialout group" is, but apparently I > >>>>>> didn't need to change it. Interesting, if I don't use the sudo > >> command, > >>>>>> the program opens without displaying any data. > >>>>>> > >>>>>> Thanks to all! > >>>>>> John Morrow > >>>>>> > >>>>>> On Sat, Mar 14, 2026 at 5:48 AM Ulf Zibis <Ulf.Zibis@cosoco.de> > >> wrote: > >>>>>>> Hi Paul, > >>>>>>> > >>>>>>> I do not understand, why running JPilot as root should be good > for. I > >>>> more > >>>>>>> think, it could be dangerous. > >>>>>>> > >>>>>>> For synching it's enough to add group `dialout` to the normal user. > >>>>>>> > >>>>>>> -Ulf > >>>>>>> > >>>>>>> Am 13.03.26 um 01:38 schrieb Paul Donlan: > >>>>>>>> Try opening Palm Pilot on *Command Line*: sudo jpilot > >>>>>>>> Then your password > >>>>>>>> Then open "File" and Press "Install User" > >>>>>>>> After you have installed your user name, *Sync* handheld. > >>>>>>>> It should work > >>>>>>>> > >>>>>>>> _______________________________________________ > >>>>>>>> Jpilot mailing list -- jpilot@lists.jpilot.org > >>>>>>>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org > >>>>>>> _______________________________________________ > >>>>>>> Jpilot mailing list -- jpilot@lists.jpilot.org > >>>>>>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org > >>>>>>> > >>>>>> _______________________________________________ > >>>>>> Jpilot mailing list -- jpilot@lists.jpilot.org > >>>>>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org > >>>>> _______________________________________________ > >>>>> Jpilot mailing list -- jpilot@lists.jpilot.org > >>>>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org > >>>> _______________________________________________ > >>>> Jpilot mailing list -- jpilot@lists.jpilot.org > >>>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org > >>>> > >>> _______________________________________________ > >>> Jpilot mailing list -- jpilot@lists.jpilot.org > >>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org > >> _______________________________________________ > >> Jpilot mailing list -- jpilot@lists.jpilot.org > >> To unsubscribe send an email to jpilot-leave@lists.jpilot.org > >> > > _______________________________________________ > > Jpilot mailing list -- jpilot@lists.jpilot.org > > To unsubscribe send an email to jpilot-leave@lists.jpilot.org > > -- > ===== > milgram@cgpp.com > 301-257-7069 > > > _______________________________________________ > Jpilot mailing list -- jpilot@lists.jpilot.org > To unsubscribe send an email to jpilot-leave@lists.jpilot.org >

Hi Elmar, Thank you! running autogen.sh did the trick. Very helpful. So I have 2.0.3 up and running. One minor thing: under "help->about jpilot" it reports v. 2.0.2 vs expected 2.0.3 ... FWIW, I see in configure.in (from https://github.com/juddmon/jpilot/archive/refs/tags/v2_0_3.tar.gz) AC_INIT(jpilot, 2.0.2) Which version is it, actually? Can the reported version be brought in alignment with the actual version? Thanks! v/r Judah On 7/27/26 03:49, Elmar Klausmeier wrote: > Hello Judah, > > maybe this helps: > https://eklausmeier.goip.de/blog/2025/03-06-building-j-pilot-and-pilot-link-on-linux > > Regards, > > Elmar. > > On Sun, Jul 26, 2026 at 10:01 PM J. Milgram via Jpilot < > jpilot@lists.jpilot.org> wrote: > >> Hello, >> >> Having trouble building v2.0.3 on a Slack 15 system. This, an initial >> step to resuscitating / adopting the currently orphaned Slackbuild. >> >> I see there's no configure script, but configure.in is there, so I tried >> autoconf. And got many errors along the lines of "error: possibly >> undefined macro" >> >> It did produce a configure script, though, and I gave it a try. It gives >> me an error: ./configure: line 2194: `AM_INIT_AUTOMAKE(1.8)' >> >> So I gave up on that. Next try: start with fresh source, and run: >> >> autoreconf -fi >> >> It repeatedly told me that the autoconf input should be named >> 'configure.ac', not 'configure.in' ... but it didn't seem to be a >> showstopper so I pushed on. >> >> Of concern: it made a po/Makefile.in.in .... that can't be right. But >> pushing on: >> >> ./configure is there. I run it, and get one error: >> >> config.status: error: po/Makefile.in.in was not created by intltoolize. >> >> But push on! >> >> make >> >> Starts out OK but bombs with an error when running msgfmt on ru.po: >> >> ru.po:170: number of format specifications in 'msgid' and 'msgstr' does >> not match >> /usr/bin/msgfmt: found 1 fatal error >> >> So I'm stuck. Anyone recognize this problem, or have any tips? I rather >> suspect all due to a single problem early on in the process, perhaps in >> one of the files that autoreconf uses. >> >> thanks! >> >> v/r >> Judah >> >> milgram@cgpp.com >> >> >> On 7/7/26 02:30, John Morrow wrote: >>> Ulf, >>> Thank you. Your instructions worked. >>> Regards, >>> John >>> >>> On Mon, Jun 22, 2026 at 5:08 AM Ulf Zibis <Ulf.Zibis@cosoco.de> wrote: >>> >>>> Hi John, >>>> >>>> 1. Copy your data from /root/.jpilot/ to $HOME/.jpilot/ >>>> >>>> 2. Correct the owner of all files inside by context menu in file >> manager or >>>> sudo chown -hR user:user $HOME/.jpilot >>>> or >>>> sudo chown -hR 1000:1000 $HOME/.jpilot >>>> >>>> Hope, that helps. >>>> -Ulf >>>> >>>> Am 22.06.26 um 06:10 schrieb John Morrow: >>>>> Ulf, >>>>> >>>>> I tried your suggestion and unfortunately I can still only see my data >>>> if I >>>>> start jpilot as root. I now see >>>>> >>>>> john@Lenovo-ideapad-320-15ABR:~$ id >>>>> uid=1000(john) gid=1000(john) >>>>> >> groups=1000(john),4(adm),20(dialout),24(cdrom),27(sudo),30(dip),46(plugdev),100(users),105(lpadmin),124(sambashare) >>>>> and when I start jpilot from the command line I get the following error >>>>> messages: >>>>> >>>>> john@Lenovo-ideapad-320-15ABR:~$ jpilot >>>>> >>>>> (jpilot:2134): Gtk-CRITICAL **: 20:42:56.126: gtk_list_store_get_path: >>>>> assertion 'iter->stamp == priv->stamp' failed >>>>> >>>>> (jpilot:2134): Gtk-CRITICAL **: 20:42:56.126: >>>>> gtk_tree_selection_select_path: assertion 'path != NULL' failed >>>>> >>>>> I have no idea what to do with that, so any and all help is greatly >>>>> appreciated. >>>>> >>>>> Regards, >>>>> John >>>>> >>>>> >>>>> On Wed, Jun 3, 2026 at 12:55 AM Ulf Zibis <Ulf.Zibis@cosoco.de> wrote: >>>>> >>>>>> @ Judd ... >>>>>> >>>>>> Hi Judd, >>>>>> could you add such hint on your web site www.JPilot.org ? >>>>>> >>>>>> Also it cold be useful, if the JPilot application would show this in >>>> case, >>>>>> sync doesn't work. >>>>>> >>>>>> Regards, >>>>>> Ulf >>>>>> >>>>>> Am 03.06.26 um 01:21 schrieb Ulf Zibis: >>>>>>> Hi John and Paul, >>>>>>> >>>>>>> if you run JPilot as root, your data will be stored in /root/.jpilot. >>>>>>> If you later run JPilot as user it will look into $HOME/.jpilot. >> That's >>>>>> why you don't see anything. >>>>>>> In standard configuration the user has no rights to sync, because it >>>>>> needs the rights of group `dialout`. >>>>>>> You can check if your user has `dialout` rights with the command >> `id`. >>>>>>> If not, on Ubuntu you need to run `sudo usermod -a -G dialout $USER` >> to >>>>>> add this group rights to your user account. >>>>>>> Then reboot your machine to make the command aktive. >>>>>>> After, you should be able to sync your Palm device as normal user. >>>>>>> >>>>>>> Note: It is not recommended to run graphical applications as root on >>>>>> Ubuntu, because it can cause corruption of your file in $HOME/. >>>>>>> -Ulf >>>>>>> >>>>>>> Am 01.06.26 um 09:12 schrieb John Morrow: >>>>>>>> Paul, >>>>>>>> >>>>>>>> I took your suggestion and started JPilot as root, installed my >>>> username >>>>>>>> and synced. After a few attempts it worked. I had to close and >> re-open >>>>>> the >>>>>>>> terminal window but in the end, all my data from the PDA is now >>>> visible >>>>>> in >>>>>>>> JPilot. I don't know what a "dialout group" is, but apparently I >>>>>>>> didn't need to change it. Interesting, if I don't use the sudo >>>> command, >>>>>>>> the program opens without displaying any data. >>>>>>>> >>>>>>>> Thanks to all! >>>>>>>> John Morrow >>>>>>>> >>>>>>>> On Sat, Mar 14, 2026 at 5:48 AM Ulf Zibis <Ulf.Zibis@cosoco.de> >>>> wrote: >>>>>>>>> Hi Paul, >>>>>>>>> >>>>>>>>> I do not understand, why running JPilot as root should be good >> for. I >>>>>> more >>>>>>>>> think, it could be dangerous. >>>>>>>>> >>>>>>>>> For synching it's enough to add group `dialout` to the normal user. >>>>>>>>> >>>>>>>>> -Ulf >>>>>>>>> >>>>>>>>> Am 13.03.26 um 01:38 schrieb Paul Donlan: >>>>>>>>>> Try opening Palm Pilot on *Command Line*: sudo jpilot >>>>>>>>>> Then your password >>>>>>>>>> Then open "File" and Press "Install User" >>>>>>>>>> After you have installed your user name, *Sync* handheld. >>>>>>>>>> It should work >>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> Jpilot mailing list -- jpilot@lists.jpilot.org >>>>>>>>>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org >>>>>>>>> _______________________________________________ >>>>>>>>> Jpilot mailing list -- jpilot@lists.jpilot.org >>>>>>>>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org >>>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Jpilot mailing list -- jpilot@lists.jpilot.org >>>>>>>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org >>>>>>> _______________________________________________ >>>>>>> Jpilot mailing list -- jpilot@lists.jpilot.org >>>>>>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org >>>>>> _______________________________________________ >>>>>> Jpilot mailing list -- jpilot@lists.jpilot.org >>>>>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org >>>>>> >>>>> _______________________________________________ >>>>> Jpilot mailing list -- jpilot@lists.jpilot.org >>>>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org >>>> _______________________________________________ >>>> Jpilot mailing list -- jpilot@lists.jpilot.org >>>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org >>>> >>> _______________________________________________ >>> Jpilot mailing list -- jpilot@lists.jpilot.org >>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org >> -- >> ===== >> milgram@cgpp.com >> 301-257-7069 >> >> >> _______________________________________________ >> Jpilot mailing list -- jpilot@lists.jpilot.org >> To unsubscribe send an email to jpilot-leave@lists.jpilot.org >> > _______________________________________________ > Jpilot mailing list -- jpilot@lists.jpilot.org > To unsubscribe send an email to jpilot-leave@lists.jpilot.org -- ===== milgram@cgpp.com 301-257-7069

I'm not sure if 2.0.3 was ever an official release.  Elmar tagged that one in git.  I put some packages up on package cloud and asked people to test it to make sure I didn't break things when migrating code to Ubuntu 26.04. Anyway, I have been working hard on getting a new release of pilot-link and jpilot out and will probably call that one 2.1.0. Pilot-link will probably be 0.15.0. Judd On 7/28/26 13:40, J. Milgram via Jpilot wrote: > Hi Elmar, > > Thank you! running autogen.sh did the trick. Very helpful. > > So I have 2.0.3 up and running. One minor thing: under "help->about > jpilot" it reports v. 2.0.2 vs expected 2.0.3 ... > > FWIW, I see in configure.in (from > https://github.com/juddmon/jpilot/archive/refs/tags/v2_0_3.tar.gz) > > AC_INIT(jpilot, 2.0.2) > > Which version is it, actually? Can the reported version be brought in > alignment with the actual version? > > Thanks! > > v/r > Judah > > > On 7/27/26 03:49, Elmar Klausmeier wrote: >> Hello Judah, >> >> maybe this helps: >> https://eklausmeier.goip.de/blog/2025/03-06-building-j-pilot-and-pilot-link-on-linux >> >> Regards, >> >> Elmar. >> >> On Sun, Jul 26, 2026 at 10:01 PM J. Milgram via Jpilot < >> jpilot@lists.jpilot.org> wrote: >> >>> Hello, >>> >>> Having trouble building v2.0.3 on a Slack 15 system. This, an initial >>> step to resuscitating / adopting the currently orphaned Slackbuild. >>> >>> I see there's no configure script, but configure.in is there, so I tried >>> autoconf. And got many errors along the lines of "error: possibly >>> undefined macro" >>> >>> It did produce a configure script, though, and I gave it a try. It gives >>> me an error: ./configure: line 2194: `AM_INIT_AUTOMAKE(1.8)' >>> >>> So I gave up on that. Next try: start with fresh source, and run: >>> >>> autoreconf -fi >>> >>> It repeatedly told me that the autoconf input should be named >>> 'configure.ac', not 'configure.in' ... but it didn't seem to be a >>> showstopper so I pushed on. >>> >>> Of concern: it made a po/Makefile.in.in .... that can't be right. But >>> pushing on: >>> >>> ./configure is there. I run it, and get one error: >>> >>> config.status: error: po/Makefile.in.in was not created by intltoolize. >>> >>> But push on! >>> >>> make >>> >>> Starts out OK but bombs with an error when running msgfmt on ru.po: >>> >>> ru.po:170: number of format specifications in 'msgid' and 'msgstr' does >>> not match >>> /usr/bin/msgfmt: found 1 fatal error >>> >>> So I'm stuck. Anyone recognize this problem, or have any tips? I rather >>> suspect all due to a single problem early on in the process, perhaps in >>> one of the files that autoreconf uses. >>> >>> thanks! >>> >>> v/r >>> Judah >>> >>> milgram@cgpp.com >>> >>> >>> On 7/7/26 02:30, John Morrow wrote: >>>> Ulf, >>>> Thank you. Your instructions worked. >>>> Regards, >>>> John >>>> >>>> On Mon, Jun 22, 2026 at 5:08 AM Ulf Zibis <Ulf.Zibis@cosoco.de> wrote: >>>> >>>>> Hi John, >>>>> >>>>> 1. Copy your data from /root/.jpilot/ to $HOME/.jpilot/ >>>>> >>>>> 2. Correct the owner of all files inside by context menu in file >>> manager or >>>>> sudo chown -hR user:user $HOME/.jpilot >>>>> or >>>>> sudo chown -hR 1000:1000 $HOME/.jpilot >>>>> >>>>> Hope, that helps. >>>>> -Ulf >>>>> >>>>> Am 22.06.26 um 06:10 schrieb John Morrow: >>>>>> Ulf, >>>>>> >>>>>> I tried your suggestion and unfortunately I can still only see my data >>>>> if I >>>>>> start jpilot as root. I now see >>>>>> >>>>>> john@Lenovo-ideapad-320-15ABR:~$ id >>>>>> uid=1000(john) gid=1000(john) >>>>>> >>> groups=1000(john),4(adm),20(dialout),24(cdrom),27(sudo),30(dip),46(plugdev),100(users),105(lpadmin),124(sambashare) >>>>>> and when I start jpilot from the command line I get the following error >>>>>> messages: >>>>>> >>>>>> john@Lenovo-ideapad-320-15ABR:~$ jpilot >>>>>> >>>>>> (jpilot:2134): Gtk-CRITICAL **: 20:42:56.126: gtk_list_store_get_path: >>>>>> assertion 'iter->stamp == priv->stamp' failed >>>>>> >>>>>> (jpilot:2134): Gtk-CRITICAL **: 20:42:56.126: >>>>>> gtk_tree_selection_select_path: assertion 'path != NULL' failed >>>>>> >>>>>> I have no idea what to do with that, so any and all help is greatly >>>>>> appreciated. >>>>>> >>>>>> Regards, >>>>>> John >>>>>> >>>>>> >>>>>> On Wed, Jun 3, 2026 at 12:55 AM Ulf Zibis <Ulf.Zibis@cosoco.de> wrote: >>>>>> >>>>>>> @ Judd ... >>>>>>> >>>>>>> Hi Judd, >>>>>>> could you add such hint on your web site www.JPilot.org ? >>>>>>> >>>>>>> Also it cold be useful, if the JPilot application would show this in >>>>> case, >>>>>>> sync doesn't work. >>>>>>> >>>>>>> Regards, >>>>>>> Ulf >>>>>>> >>>>>>> Am 03.06.26 um 01:21 schrieb Ulf Zibis: >>>>>>>> Hi John and Paul, >>>>>>>> >>>>>>>> if you run JPilot as root, your data will be stored in /root/.jpilot. >>>>>>>> If you later run JPilot as user it will look into $HOME/.jpilot. >>> That's >>>>>>> why you don't see anything. >>>>>>>> In standard configuration the user has no rights to sync, because it >>>>>>> needs the rights of group `dialout`. >>>>>>>> You can check if your user has `dialout` rights with the command >>> `id`. >>>>>>>> If not, on Ubuntu you need to run `sudo usermod -a -G dialout $USER` >>> to >>>>>>> add this group rights to your user account. >>>>>>>> Then reboot your machine to make the command aktive. >>>>>>>> After, you should be able to sync your Palm device as normal user. >>>>>>>> >>>>>>>> Note: It is not recommended to run graphical applications as root on >>>>>>> Ubuntu, because it can cause corruption of your file in $HOME/. >>>>>>>> -Ulf >>>>>>>> >>>>>>>> Am 01.06.26 um 09:12 schrieb John Morrow: >>>>>>>>> Paul, >>>>>>>>> >>>>>>>>> I took your suggestion and started JPilot as root, installed my >>>>> username >>>>>>>>> and synced. After a few attempts it worked. I had to close and >>> re-open >>>>>>> the >>>>>>>>> terminal window but in the end, all my data from the PDA is now >>>>> visible >>>>>>> in >>>>>>>>> JPilot. I don't know what a "dialout group" is, but apparently I >>>>>>>>> didn't need to change it. Interesting, if I don't use the sudo >>>>> command, >>>>>>>>> the program opens without displaying any data. >>>>>>>>> >>>>>>>>> Thanks to all! >>>>>>>>> John Morrow >>>>>>>>> >>>>>>>>> On Sat, Mar 14, 2026 at 5:48 AM Ulf Zibis <Ulf.Zibis@cosoco.de> >>>>> wrote: >>>>>>>>>> Hi Paul, >>>>>>>>>> >>>>>>>>>> I do not understand, why running JPilot as root should be good >>> for. I >>>>>>> more >>>>>>>>>> think, it could be dangerous. >>>>>>>>>> >>>>>>>>>> For synching it's enough to add group `dialout` to the normal user. >>>>>>>>>> >>>>>>>>>> -Ulf >>>>>>>>>> >>>>>>>>>> Am 13.03.26 um 01:38 schrieb Paul Donlan: >>>>>>>>>>> Try opening Palm Pilot on *Command Line*: sudo jpilot >>>>>>>>>>> Then your password >>>>>>>>>>> Then open "File" and Press "Install User" >>>>>>>>>>> After you have installed your user name, *Sync* handheld. >>>>>>>>>>> It should work >>>>>>>>>>> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> Jpilot mailing list -- jpilot@lists.jpilot.org >>>>>>>>>>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org >>>>>>>>>> _______________________________________________ >>>>>>>>>> Jpilot mailing list -- jpilot@lists.jpilot.org >>>>>>>>>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org >>>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> Jpilot mailing list -- jpilot@lists.jpilot.org >>>>>>>>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org >>>>>>>> _______________________________________________ >>>>>>>> Jpilot mailing list -- jpilot@lists.jpilot.org >>>>>>>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org >>>>>>> _______________________________________________ >>>>>>> Jpilot mailing list -- jpilot@lists.jpilot.org >>>>>>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org >>>>>>> >>>>>> _______________________________________________ >>>>>> Jpilot mailing list -- jpilot@lists.jpilot.org >>>>>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org >>>>> _______________________________________________ >>>>> Jpilot mailing list -- jpilot@lists.jpilot.org >>>>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org >>>>> >>>> _______________________________________________ >>>> Jpilot mailing list -- jpilot@lists.jpilot.org >>>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org >>> -- >>> ===== >>> milgram@cgpp.com >>> 301-257-7069 >>> >>> >>> _______________________________________________ >>> Jpilot mailing list -- jpilot@lists.jpilot.org >>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org >>> >> _______________________________________________ >> Jpilot mailing list -- jpilot@lists.jpilot.org >> To unsubscribe send an email to jpilot-leave@lists.jpilot.org > -- > ===== > milgram@cgpp.com > 301-257-7069 > > > _______________________________________________ > Jpilot mailing list -- jpilot@lists.jpilot.org > To unsubscribe send an email to jpilot-leave@lists.jpilot.org

Understood. The  source tarball was xxx-2_0_3.tar.gz so I called the version 2.0.3 in the Slackbuild (will be up on slackbuilds.org soon). It includes a step: sed  -i -e 's/AC_INIT(jpilot, 2.0.2)/AC_INIT(jpilot, 2.0.3)/' configure.in ... and that's all it took to get it to report itself as 2.0.3. So I guess v 2.0.3 is official now :) Sorry. I can undo that, if necessary. BTW additional gymnastics were required to deal with underscore-style version numbers (2_0_3 and 2.0.3) ... but it all worked out in the end. I'll keep an eye out for the next jpilot. I don't know if there's ever been a SlackBuild for pilot-link but no reason not to make one. Unfortunately my Z22 is in extremis so beyond a successful build and making a package, I can test only the functionality of jpilot desktop features. Thanks for keeping  this  project going! I will get a new battery into my Z22  one of these  days. v/r Judah On 7/28/26 18:28, Judd Montgomery wrote: > I'm not sure if 2.0.3 was ever an official release.  Elmar tagged that > one in git.  I put some packages up on package cloud and asked people to > test it to make sure I didn't break things when migrating code to Ubuntu > 26.04. > > Anyway, I have been working hard on getting a new release of pilot-link > and jpilot out and will probably call that one 2.1.0. Pilot-link will > probably be 0.15.0. > > Judd > > On 7/28/26 13:40, J. Milgram via Jpilot wrote: >> Hi Elmar, >> >> Thank you! running autogen.sh did the trick. Very helpful. >> >> So I have 2.0.3 up and running. One minor thing: under "help->about >> jpilot" it reports v. 2.0.2 vs expected 2.0.3 ... >> >> FWIW, I see in configure.in (from >> https://github.com/juddmon/jpilot/archive/refs/tags/v2_0_3.tar.gz) >> >> AC_INIT(jpilot, 2.0.2) >> >> Which version is it, actually? Can the reported version be brought in >> alignment with the actual version? >> >> Thanks! >> >> v/r >> Judah >> >> >> On 7/27/26 03:49, Elmar Klausmeier wrote: >>> Hello Judah, >>> >>> maybe this helps: >>> https://eklausmeier.goip.de/blog/2025/03-06-building-j-pilot-and-pilot-link-on-linux >>> >>> Regards, >>> >>> Elmar. >>> >>> On Sun, Jul 26, 2026 at 10:01 PM J. Milgram via Jpilot < >>> jpilot@lists.jpilot.org> wrote: >>> >>>> Hello, >>>> >>>> Having trouble building v2.0.3 on a Slack 15 system. This, an initial >>>> step to resuscitating / adopting the currently orphaned Slackbuild. >>>> >>>> I see there's no configure script, but configure.in is there, so I tried >>>> autoconf. And got many errors along the lines of "error: possibly >>>> undefined macro" >>>> >>>> It did produce a configure script, though, and I gave it a try. It gives >>>> me an error: ./configure: line 2194: `AM_INIT_AUTOMAKE(1.8)' >>>> >>>> So I gave up on that. Next try: start with fresh source, and run: >>>> >>>> autoreconf -fi >>>> >>>> It repeatedly told me that the autoconf input should be named >>>> 'configure.ac', not 'configure.in' ... but it didn't seem to be a >>>> showstopper so I pushed on. >>>> >>>> Of concern: it made a po/Makefile.in.in .... that can't be right. But >>>> pushing on: >>>> >>>> ./configure is there. I run it, and get one error: >>>> >>>> config.status: error: po/Makefile.in.in was not created by intltoolize. >>>> >>>> But push on! >>>> >>>> make >>>> >>>> Starts out OK but bombs with an error when running msgfmt on ru.po: >>>> >>>> ru.po:170: number of format specifications in 'msgid' and 'msgstr' does >>>> not match >>>> /usr/bin/msgfmt: found 1 fatal error >>>> >>>> So I'm stuck. Anyone recognize this problem, or have any tips? I rather >>>> suspect all due to a single problem early on in the process, perhaps in >>>> one of the files that autoreconf uses. >>>> >>>> thanks! >>>> >>>> v/r >>>> Judah >>>> >>>> milgram@cgpp.com >>>> >>>> >>>> On 7/7/26 02:30, John Morrow wrote: >>>>> Ulf, >>>>> Thank you. Your instructions worked. >>>>> Regards, >>>>> John >>>>> >>>>> On Mon, Jun 22, 2026 at 5:08 AM Ulf Zibis <Ulf.Zibis@cosoco.de> wrote: >>>>> >>>>>> Hi John, >>>>>> >>>>>> 1. Copy your data from /root/.jpilot/ to $HOME/.jpilot/ >>>>>> >>>>>> 2. Correct the owner of all files inside by context menu in file >>>> manager or >>>>>> sudo chown -hR user:user $HOME/.jpilot >>>>>> or >>>>>> sudo chown -hR 1000:1000 $HOME/.jpilot >>>>>> >>>>>> Hope, that helps. >>>>>> -Ulf >>>>>> >>>>>> Am 22.06.26 um 06:10 schrieb John Morrow: >>>>>>> Ulf, >>>>>>> >>>>>>> I tried your suggestion and unfortunately I can still only see my data >>>>>> if I >>>>>>> start jpilot as root. I now see >>>>>>> >>>>>>> john@Lenovo-ideapad-320-15ABR:~$ id >>>>>>> uid=1000(john) gid=1000(john) >>>>>>> >>>> groups=1000(john),4(adm),20(dialout),24(cdrom),27(sudo),30(dip),46(plugdev),100(users),105(lpadmin),124(sambashare) >>>>>>> and when I start jpilot from the command line I get the following error >>>>>>> messages: >>>>>>> >>>>>>> john@Lenovo-ideapad-320-15ABR:~$ jpilot >>>>>>> >>>>>>> (jpilot:2134): Gtk-CRITICAL **: 20:42:56.126: gtk_list_store_get_path: >>>>>>> assertion 'iter->stamp == priv->stamp' failed >>>>>>> >>>>>>> (jpilot:2134): Gtk-CRITICAL **: 20:42:56.126: >>>>>>> gtk_tree_selection_select_path: assertion 'path != NULL' failed >>>>>>> >>>>>>> I have no idea what to do with that, so any and all help is greatly >>>>>>> appreciated. >>>>>>> >>>>>>> Regards, >>>>>>> John >>>>>>> >>>>>>> >>>>>>> On Wed, Jun 3, 2026 at 12:55 AM Ulf Zibis <Ulf.Zibis@cosoco.de> wrote: >>>>>>> >>>>>>>> @ Judd ... >>>>>>>> >>>>>>>> Hi Judd, >>>>>>>> could you add such hint on your web site www.JPilot.org ? >>>>>>>> >>>>>>>> Also it cold be useful, if the JPilot application would show this in >>>>>> case, >>>>>>>> sync doesn't work. >>>>>>>> >>>>>>>> Regards, >>>>>>>> Ulf >>>>>>>> >>>>>>>> Am 03.06.26 um 01:21 schrieb Ulf Zibis: >>>>>>>>> Hi John and Paul, >>>>>>>>> >>>>>>>>> if you run JPilot as root, your data will be stored in /root/.jpilot. >>>>>>>>> If you later run JPilot as user it will look into $HOME/.jpilot. >>>> That's >>>>>>>> why you don't see anything. >>>>>>>>> In standard configuration the user has no rights to sync, because it >>>>>>>> needs the rights of group `dialout`. >>>>>>>>> You can check if your user has `dialout` rights with the command >>>> `id`. >>>>>>>>> If not, on Ubuntu you need to run `sudo usermod -a -G dialout $USER` >>>> to >>>>>>>> add this group rights to your user account. >>>>>>>>> Then reboot your machine to make the command aktive. >>>>>>>>> After, you should be able to sync your Palm device as normal user. >>>>>>>>> >>>>>>>>> Note: It is not recommended to run graphical applications as root on >>>>>>>> Ubuntu, because it can cause corruption of your file in $HOME/. >>>>>>>>> -Ulf >>>>>>>>> >>>>>>>>> Am 01.06.26 um 09:12 schrieb John Morrow: >>>>>>>>>> Paul, >>>>>>>>>> >>>>>>>>>> I took your suggestion and started JPilot as root, installed my >>>>>> username >>>>>>>>>> and synced. After a few attempts it worked. I had to close and >>>> re-open >>>>>>>> the >>>>>>>>>> terminal window but in the end, all my data from the PDA is now >>>>>> visible >>>>>>>> in >>>>>>>>>> JPilot. I don't know what a "dialout group" is, but apparently I >>>>>>>>>> didn't need to change it. Interesting, if I don't use the sudo >>>>>> command, >>>>>>>>>> the program opens without displaying any data. >>>>>>>>>> >>>>>>>>>> Thanks to all! >>>>>>>>>> John Morrow >>>>>>>>>> >>>>>>>>>> On Sat, Mar 14, 2026 at 5:48 AM Ulf Zibis <Ulf.Zibis@cosoco.de> >>>>>> wrote: >>>>>>>>>>> Hi Paul, >>>>>>>>>>> >>>>>>>>>>> I do not understand, why running JPilot as root should be good >>>> for. I >>>>>>>> more >>>>>>>>>>> think, it could be dangerous. >>>>>>>>>>> >>>>>>>>>>> For synching it's enough to add group `dialout` to the normal user. >>>>>>>>>>> >>>>>>>>>>> -Ulf >>>>>>>>>>> >>>>>>>>>>> Am 13.03.26 um 01:38 schrieb Paul Donlan: >>>>>>>>>>>> Try opening Palm Pilot on *Command Line*: sudo jpilot >>>>>>>>>>>> Then your password >>>>>>>>>>>> Then open "File" and Press "Install User" >>>>>>>>>>>> After you have installed your user name, *Sync* handheld. >>>>>>>>>>>> It should work >>>>>>>>>>>> >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> Jpilot mailing list -- jpilot@lists.jpilot.org >>>>>>>>>>>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> Jpilot mailing list -- jpilot@lists.jpilot.org >>>>>>>>>>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org >>>>>>>>>>> >>>>>>>>>> _______________________________________________ >>>>>>>>>> Jpilot mailing list -- jpilot@lists.jpilot.org >>>>>>>>>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org >>>>>>>>> _______________________________________________ >>>>>>>>> Jpilot mailing list -- jpilot@lists.jpilot.org >>>>>>>>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org >>>>>>>> _______________________________________________ >>>>>>>> Jpilot mailing list -- jpilot@lists.jpilot.org >>>>>>>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org >>>>>>>> >>>>>>> _______________________________________________ >>>>>>> Jpilot mailing list -- jpilot@lists.jpilot.org >>>>>>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org >>>>>> _______________________________________________ >>>>>> Jpilot mailing list -- jpilot@lists.jpilot.org >>>>>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org >>>>>> >>>>> _______________________________________________ >>>>> Jpilot mailing list -- jpilot@lists.jpilot.org >>>>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org >>>> -- >>>> ===== >>>> milgram@cgpp.com >>>> 301-257-7069 >>>> >>>> >>>> _______________________________________________ >>>> Jpilot mailing list -- jpilot@lists.jpilot.org >>>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org >>>> >>> _______________________________________________ >>> Jpilot mailing list -- jpilot@lists.jpilot.org >>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org >> -- >> ===== >> milgram@cgpp.com >> 301-257-7069 >> >> >> _______________________________________________ >> Jpilot mailing list -- jpilot@lists.jpilot.org >> To unsubscribe send an email to jpilot-leave@lists.jpilot.org > -- ===== milgram@cgpp.com 301-257-7069

Nah, what you did was fine, and good job and getting it packaged!  I don't know where you got that tarball and if it was made from the github tag v2.0.3 or what.  I'm not worried about it because I'll try to get something newer out soon. I used to run Slackware from '94 or so until around 2007 and I built pilot-link and jpilot packages for it.  There is even a SlackBuild script in the repo.  David Malia updated it in 2020! https://github.com/juddmon/jpilot/blob/master/SlackBuild.in You can take it over if you'd like.  I know there is at lease one other Slackware user on this email list.  I can help you get code committed to pilot-link also. Judd On 7/28/26 19:02, J. Milgram via Jpilot wrote: > Understood. > > The  source tarball was xxx-2_0_3.tar.gz so I called the version 2.0.3 > in the Slackbuild (will be up on slackbuilds.org soon). It includes a step: > > sed  -i -e 's/AC_INIT(jpilot, 2.0.2)/AC_INIT(jpilot, 2.0.3)/' configure.in > > ... and that's all it took to get it to report itself as 2.0.3. So I > guess v 2.0.3 is official now :) Sorry. I can undo that, if necessary. > > BTW additional gymnastics were required to deal with underscore-style > version numbers (2_0_3 and 2.0.3) ... but it all worked out in the end. > > I'll keep an eye out for the next jpilot. I don't know if there's ever > been a SlackBuild for pilot-link but no reason not to make one. > Unfortunately my Z22 is in extremis so beyond a successful build and > making a package, I can test only the functionality of jpilot desktop > features. > > Thanks for keeping  this  project going! I will get a new battery into > my Z22  one of these  days. > > v/r > Judah > > > > > On 7/28/26 18:28, Judd Montgomery wrote: >> I'm not sure if 2.0.3 was ever an official release.  Elmar tagged that >> one in git.  I put some packages up on package cloud and asked people to >> test it to make sure I didn't break things when migrating code to Ubuntu >> 26.04. >> >> Anyway, I have been working hard on getting a new release of pilot-link >> and jpilot out and will probably call that one 2.1.0. Pilot-link will >> probably be 0.15.0. >> >> Judd >> >> On 7/28/26 13:40, J. Milgram via Jpilot wrote: >>> Hi Elmar, >>> >>> Thank you! running autogen.sh did the trick. Very helpful. >>> >>> So I have 2.0.3 up and running. One minor thing: under "help->about >>> jpilot" it reports v. 2.0.2 vs expected 2.0.3 ... >>> >>> FWIW, I see in configure.in (from >>> https://github.com/juddmon/jpilot/archive/refs/tags/v2_0_3.tar.gz) >>> >>> AC_INIT(jpilot, 2.0.2) >>> >>> Which version is it, actually? Can the reported version be brought in >>> alignment with the actual version? >>> >>> Thanks! >>> >>> v/r >>> Judah >>> >>> >>> On 7/27/26 03:49, Elmar Klausmeier wrote: >>>> Hello Judah, >>>> >>>> maybe this helps: >>>> https://eklausmeier.goip.de/blog/2025/03-06-building-j-pilot-and-pilot-link-on-linux >>>> >>>> Regards, >>>> >>>> Elmar. >>>> >>>> On Sun, Jul 26, 2026 at 10:01 PM J. Milgram via Jpilot < >>>> jpilot@lists.jpilot.org> wrote: >>>> >>>>> Hello, >>>>> >>>>> Having trouble building v2.0.3 on a Slack 15 system. This, an initial >>>>> step to resuscitating / adopting the currently orphaned Slackbuild. >>>>> >>>>> I see there's no configure script, but configure.in is there, so I tried >>>>> autoconf. And got many errors along the lines of "error: possibly >>>>> undefined macro" >>>>> >>>>> It did produce a configure script, though, and I gave it a try. It gives >>>>> me an error: ./configure: line 2194: `AM_INIT_AUTOMAKE(1.8)' >>>>> >>>>> So I gave up on that. Next try: start with fresh source, and run: >>>>> >>>>> autoreconf -fi >>>>> >>>>> It repeatedly told me that the autoconf input should be named >>>>> 'configure.ac', not 'configure.in' ... but it didn't seem to be a >>>>> showstopper so I pushed on. >>>>> >>>>> Of concern: it made a po/Makefile.in.in .... that can't be right. But >>>>> pushing on: >>>>> >>>>> ./configure is there. I run it, and get one error: >>>>> >>>>> config.status: error: po/Makefile.in.in was not created by intltoolize. >>>>> >>>>> But push on! >>>>> >>>>> make >>>>> >>>>> Starts out OK but bombs with an error when running msgfmt on ru.po: >>>>> >>>>> ru.po:170: number of format specifications in 'msgid' and 'msgstr' does >>>>> not match >>>>> /usr/bin/msgfmt: found 1 fatal error >>>>> >>>>> So I'm stuck. Anyone recognize this problem, or have any tips? I rather >>>>> suspect all due to a single problem early on in the process, perhaps in >>>>> one of the files that autoreconf uses. >>>>> >>>>> thanks! >>>>> >>>>> v/r >>>>> Judah >>>>> >>>>> milgram@cgpp.com >>>>> >>>>> >>>>> On 7/7/26 02:30, John Morrow wrote: >>>>>> Ulf, >>>>>> Thank you. Your instructions worked. >>>>>> Regards, >>>>>> John >>>>>> >>>>>> On Mon, Jun 22, 2026 at 5:08 AM Ulf Zibis <Ulf.Zibis@cosoco.de> wrote: >>>>>> >>>>>>> Hi John, >>>>>>> >>>>>>> 1. Copy your data from /root/.jpilot/ to $HOME/.jpilot/ >>>>>>> >>>>>>> 2. Correct the owner of all files inside by context menu in file >>>>> manager or >>>>>>> sudo chown -hR user:user $HOME/.jpilot >>>>>>> or >>>>>>> sudo chown -hR 1000:1000 $HOME/.jpilot >>>>>>> >>>>>>> Hope, that helps. >>>>>>> -Ulf >>>>>>> >>>>>>> Am 22.06.26 um 06:10 schrieb John Morrow: >>>>>>>> Ulf, >>>>>>>> >>>>>>>> I tried your suggestion and unfortunately I can still only see my data >>>>>>> if I >>>>>>>> start jpilot as root. I now see >>>>>>>> >>>>>>>> john@Lenovo-ideapad-320-15ABR:~$ id >>>>>>>> uid=1000(john) gid=1000(john) >>>>>>>> >>>>> groups=1000(john),4(adm),20(dialout),24(cdrom),27(sudo),30(dip),46(plugdev),100(users),105(lpadmin),124(sambashare) >>>>>>>> and when I start jpilot from the command line I get the following error >>>>>>>> messages: >>>>>>>> >>>>>>>> john@Lenovo-ideapad-320-15ABR:~$ jpilot >>>>>>>> >>>>>>>> (jpilot:2134): Gtk-CRITICAL **: 20:42:56.126: gtk_list_store_get_path: >>>>>>>> assertion 'iter->stamp == priv->stamp' failed >>>>>>>> >>>>>>>> (jpilot:2134): Gtk-CRITICAL **: 20:42:56.126: >>>>>>>> gtk_tree_selection_select_path: assertion 'path != NULL' failed >>>>>>>> >>>>>>>> I have no idea what to do with that, so any and all help is greatly >>>>>>>> appreciated. >>>>>>>> >>>>>>>> Regards, >>>>>>>> John >>>>>>>> >>>>>>>> >>>>>>>> On Wed, Jun 3, 2026 at 12:55 AM Ulf Zibis <Ulf.Zibis@cosoco.de> wrote: >>>>>>>> >>>>>>>>> @ Judd ... >>>>>>>>> >>>>>>>>> Hi Judd, >>>>>>>>> could you add such hint on your web site www.JPilot.org ? >>>>>>>>> >>>>>>>>> Also it cold be useful, if the JPilot application would show this in >>>>>>> case, >>>>>>>>> sync doesn't work. >>>>>>>>> >>>>>>>>> Regards, >>>>>>>>> Ulf >>>>>>>>> >>>>>>>>> Am 03.06.26 um 01:21 schrieb Ulf Zibis: >>>>>>>>>> Hi John and Paul, >>>>>>>>>> >>>>>>>>>> if you run JPilot as root, your data will be stored in /root/.jpilot. >>>>>>>>>> If you later run JPilot as user it will look into $HOME/.jpilot. >>>>> That's >>>>>>>>> why you don't see anything. >>>>>>>>>> In standard configuration the user has no rights to sync, because it >>>>>>>>> needs the rights of group `dialout`. >>>>>>>>>> You can check if your user has `dialout` rights with the command >>>>> `id`. >>>>>>>>>> If not, on Ubuntu you need to run `sudo usermod -a -G dialout $USER` >>>>> to >>>>>>>>> add this group rights to your user account. >>>>>>>>>> Then reboot your machine to make the command aktive. >>>>>>>>>> After, you should be able to sync your Palm device as normal user. >>>>>>>>>> >>>>>>>>>> Note: It is not recommended to run graphical applications as root on >>>>>>>>> Ubuntu, because it can cause corruption of your file in $HOME/. >>>>>>>>>> -Ulf >>>>>>>>>> >>>>>>>>>> Am 01.06.26 um 09:12 schrieb John Morrow: >>>>>>>>>>> Paul, >>>>>>>>>>> >>>>>>>>>>> I took your suggestion and started JPilot as root, installed my >>>>>>> username >>>>>>>>>>> and synced. After a few attempts it worked. I had to close and >>>>> re-open >>>>>>>>> the >>>>>>>>>>> terminal window but in the end, all my data from the PDA is now >>>>>>> visible >>>>>>>>> in >>>>>>>>>>> JPilot. I don't know what a "dialout group" is, but apparently I >>>>>>>>>>> didn't need to change it. Interesting, if I don't use the sudo >>>>>>> command, >>>>>>>>>>> the program opens without displaying any data. >>>>>>>>>>> >>>>>>>>>>> Thanks to all! >>>>>>>>>>> John Morrow >>>>>>>>>>> >>>>>>>>>>> On Sat, Mar 14, 2026 at 5:48 AM Ulf Zibis <Ulf.Zibis@cosoco.de> >>>>>>> wrote: >>>>>>>>>>>> Hi Paul, >>>>>>>>>>>> >>>>>>>>>>>> I do not understand, why running JPilot as root should be good >>>>> for. I >>>>>>>>> more >>>>>>>>>>>> think, it could be dangerous. >>>>>>>>>>>> >>>>>>>>>>>> For synching it's enough to add group `dialout` to the normal user. >>>>>>>>>>>> >>>>>>>>>>>> -Ulf >>>>>>>>>>>> >>>>>>>>>>>> Am 13.03.26 um 01:38 schrieb Paul Donlan: >>>>>>>>>>>>> Try opening Palm Pilot on *Command Line*: sudo jpilot >>>>>>>>>>>>> Then your password >>>>>>>>>>>>> Then open "File" and Press "Install User" >>>>>>>>>>>>> After you have installed your user name, *Sync* handheld. >>>>>>>>>>>>> It should work >>>>>>>>>>>>> >>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>> Jpilot mailing list -- jpilot@lists.jpilot.org >>>>>>>>>>>>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> Jpilot mailing list -- jpilot@lists.jpilot.org >>>>>>>>>>>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org >>>>>>>>>>>> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> Jpilot mailing list -- jpilot@lists.jpilot.org >>>>>>>>>>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org >>>>>>>>>> _______________________________________________ >>>>>>>>>> Jpilot mailing list -- jpilot@lists.jpilot.org >>>>>>>>>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org >>>>>>>>> _______________________________________________ >>>>>>>>> Jpilot mailing list -- jpilot@lists.jpilot.org >>>>>>>>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org >>>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Jpilot mailing list -- jpilot@lists.jpilot.org >>>>>>>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org >>>>>>> _______________________________________________ >>>>>>> Jpilot mailing list -- jpilot@lists.jpilot.org >>>>>>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org >>>>>>> >>>>>> _______________________________________________ >>>>>> Jpilot mailing list -- jpilot@lists.jpilot.org >>>>>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org >>>>> -- >>>>> ===== >>>>> milgram@cgpp.com >>>>> 301-257-7069 >>>>> >>>>> >>>>> _______________________________________________ >>>>> Jpilot mailing list -- jpilot@lists.jpilot.org >>>>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org >>>>> >>>> _______________________________________________ >>>> Jpilot mailing list -- jpilot@lists.jpilot.org >>>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org >>> -- >>> ===== >>> milgram@cgpp.com >>> 301-257-7069 >>> >>> >>> _______________________________________________ >>> Jpilot mailing list -- jpilot@lists.jpilot.org >>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org > -- > ===== > milgram@cgpp.com > 301-257-7069 > > > _______________________________________________ > Jpilot mailing list -- jpilot@lists.jpilot.org > To unsubscribe send an email to jpilot-leave@lists.jpilot.org

On Tue, 28 Jul 2026, Judd Montgomery wrote: > You can take it over if you'd like. I know there is at lease one other > Slackware user on this email list. I can help you get code committed to > pilot-link also. Judd, That includes me. I used Red Had from 1997 to 2003 and Slackware since then. Jpilot is a core business and personal application. Many thanks for your continued support. Best regards, Rich

Slackbuilds  seems to be getting serious about marking scripts "orphaned" when there's no maintainer, so I figured why not. Even after my Palm went dark, I still find the desktop app very useful. I got the tarball from: https://github.com/juddmon/jpilot/archive/v2_0_3/jpilot-2_0_3.tar.gz ... and that's the URL I provided in the SBo .info file. This seems to be a bit of Slackbuilds secret sauce - git, undocumentedly, seems always to provide a release tarball named "project-version.tar.gz" at that owner/repo/archive/version URL. Otherwise downloading from the "tags" page: https://github.com/juddmon/jpilot/archive/refs/tags/v2_0_3.tar.gz brings down a file called simply "v{version}.tar.gz" which doesn't play well with the standard SlackBuild scripts (at least not the template I'm using). I'm just trying to do it the way all the other SlackBuilds do it. BTW yes, the tarballs at those two URLs are identical. Obviously grabbing the "v2_0_3.tar.gz" version and renaming it would work but I don't think there's a way to do that when using the sbotools install scripts. Historical info: as of 1.8.2 the Slackbuild copyright notice lists author as "alkos333" in 2007. The update to 1.8.2 was in 2022, if I saw right. Other than fixing a declaration in jp-contact.c, no changes to the codebase were required for Slack 15. That "patch" was: sed -i -e 's/return Contact_add_blob(c, blob);/return Contact_add_blob(c, (void*)blob);/' jp-contact.c Perhaps I could have left it as is and used a more appropriate -std=gnuXX CFLAG. (I switched to gnu99 to fix something else, don't remember what.) If this is a dumb change, let me know and I'll see if there's another route. I didn't  think to look at the SlackBuild script in the repo - just assumed it would be the same as the one currently provided at slackbuilds.org I just saw they approved the package and it will be in the next SBo update, this weekend probably. BTW for some reason SBo categorizes it as "accessibility" but personally I think it should be "office" ... before I recommend a change, any history there I should know about? thanks! r/ Judah On 7/28/26 19:21, Judd Montgomery wrote: > Nah, what you did was fine, and good job and getting it packaged!  I > don't know where you got that tarball and if it was made from the github > tag v2.0.3 or what.  I'm not worried about it because I'll try to get > something newer out soon. > > I used to run Slackware from '94 or so until around 2007 and I built > pilot-link and jpilot packages for it.  There is even a SlackBuild > script in the repo.  David Malia updated it in 2020! > https://github.com/juddmon/jpilot/blob/master/SlackBuild.in > > You can take it over if you'd like.  I know there is at lease one other > Slackware user on this email list.  I can help you get code committed to > pilot-link also. > > Judd > > On 7/28/26 19:02, J. Milgram via Jpilot wrote: >> Understood. >> >> The  source tarball was xxx-2_0_3.tar.gz so I called the version 2.0.3 >> in the Slackbuild (will be up on slackbuilds.org soon). It includes a step: >> >> sed  -i -e 's/AC_INIT(jpilot, 2.0.2)/AC_INIT(jpilot, 2.0.3)/' configure.in >> >> ... and that's all it took to get it to report itself as 2.0.3. So I >> guess v 2.0.3 is official now :) Sorry. I can undo that, if necessary. >> >> BTW additional gymnastics were required to deal with underscore-style >> version numbers (2_0_3 and 2.0.3) ... but it all worked out in the end. >> >> I'll keep an eye out for the next jpilot. I don't know if there's ever >> been a SlackBuild for pilot-link but no reason not to make one. >> Unfortunately my Z22 is in extremis so beyond a successful build and >> making a package, I can test only the functionality of jpilot desktop >> features. >> >> Thanks for keeping  this  project going! I will get a new battery into >> my Z22  one of these  days. >> >> v/r >> Judah >> >> >> >> >> On 7/28/26 18:28, Judd Montgomery wrote: >>> I'm not sure if 2.0.3 was ever an official release.  Elmar tagged that >>> one in git.  I put some packages up on package cloud and asked people to >>> test it to make sure I didn't break things when migrating code to Ubuntu >>> 26.04. >>> >>> Anyway, I have been working hard on getting a new release of pilot-link >>> and jpilot out and will probably call that one 2.1.0. Pilot-link will >>> probably be 0.15.0. >>> >>> Judd >>> >>> On 7/28/26 13:40, J. Milgram via Jpilot wrote: >>>> Hi Elmar, >>>> >>>> Thank you! running autogen.sh did the trick. Very helpful. >>>> >>>> So I have 2.0.3 up and running. One minor thing: under "help->about >>>> jpilot" it reports v. 2.0.2 vs expected 2.0.3 ... >>>> >>>> FWIW, I see in configure.in (from >>>> https://github.com/juddmon/jpilot/archive/refs/tags/v2_0_3.tar.gz) >>>> >>>> AC_INIT(jpilot, 2.0.2) >>>> >>>> Which version is it, actually? Can the reported version be brought in >>>> alignment with the actual version? >>>> >>>> Thanks! >>>> >>>> v/r >>>> Judah >>>> >>>> >>>> On 7/27/26 03:49, Elmar Klausmeier wrote: >>>>> Hello Judah, >>>>> >>>>> maybe this helps: >>>>> https://eklausmeier.goip.de/blog/2025/03-06-building-j-pilot-and-pilot-link-on-linux >>>>> >>>>> Regards, >>>>> >>>>> Elmar. >>>>> >>>>> On Sun, Jul 26, 2026 at 10:01 PM J. Milgram via Jpilot < >>>>> jpilot@lists.jpilot.org> wrote: >>>>> >>>>>> Hello, >>>>>> >>>>>> Having trouble building v2.0.3 on a Slack 15 system. This, an initial >>>>>> step to resuscitating / adopting the currently orphaned Slackbuild. >>>>>> >>>>>> I see there's no configure script, but configure.in is there, so I tried >>>>>> autoconf. And got many errors along the lines of "error: possibly >>>>>> undefined macro" >>>>>> >>>>>> It did produce a configure script, though, and I gave it a try. It gives >>>>>> me an error: ./configure: line 2194: `AM_INIT_AUTOMAKE(1.8)' >>>>>> >>>>>> So I gave up on that. Next try: start with fresh source, and run: >>>>>> >>>>>> autoreconf -fi >>>>>> >>>>>> It repeatedly told me that the autoconf input should be named >>>>>> 'configure.ac', not 'configure.in' ... but it didn't seem to be a >>>>>> showstopper so I pushed on. >>>>>> >>>>>> Of concern: it made a po/Makefile.in.in .... that can't be right. But >>>>>> pushing on: >>>>>> >>>>>> ./configure is there. I run it, and get one error: >>>>>> >>>>>> config.status: error: po/Makefile.in.in was not created by intltoolize. >>>>>> >>>>>> But push on! >>>>>> >>>>>> make >>>>>> >>>>>> Starts out OK but bombs with an error when running msgfmt on ru.po: >>>>>> >>>>>> ru.po:170: number of format specifications in 'msgid' and 'msgstr' does >>>>>> not match >>>>>> /usr/bin/msgfmt: found 1 fatal error >>>>>> >>>>>> So I'm stuck. Anyone recognize this problem, or have any tips? I rather >>>>>> suspect all due to a single problem early on in the process, perhaps in >>>>>> one of the files that autoreconf uses. >>>>>> >>>>>> thanks! >>>>>> >>>>>> v/r >>>>>> Judah >>>>>> >>>>>> milgram@cgpp.com >>>>>> >>>>>> >>>>>> On 7/7/26 02:30, John Morrow wrote: >>>>>>> Ulf, >>>>>>> Thank you. Your instructions worked. >>>>>>> Regards, >>>>>>> John >>>>>>> >>>>>>> On Mon, Jun 22, 2026 at 5:08 AM Ulf Zibis <Ulf.Zibis@cosoco.de> wrote: >>>>>>> >>>>>>>> Hi John, >>>>>>>> >>>>>>>> 1. Copy your data from /root/.jpilot/ to $HOME/.jpilot/ >>>>>>>> >>>>>>>> 2. Correct the owner of all files inside by context menu in file >>>>>> manager or >>>>>>>> sudo chown -hR user:user $HOME/.jpilot >>>>>>>> or >>>>>>>> sudo chown -hR 1000:1000 $HOME/.jpilot >>>>>>>> >>>>>>>> Hope, that helps. >>>>>>>> -Ulf >>>>>>>> >>>>>>>> Am 22.06.26 um 06:10 schrieb John Morrow: >>>>>>>>> Ulf, >>>>>>>>> >>>>>>>>> I tried your suggestion and unfortunately I can still only see my data >>>>>>>> if I >>>>>>>>> start jpilot as root. I now see >>>>>>>>> >>>>>>>>> john@Lenovo-ideapad-320-15ABR:~$ id >>>>>>>>> uid=1000(john) gid=1000(john) >>>>>>>>> >>>>>> groups=1000(john),4(adm),20(dialout),24(cdrom),27(sudo),30(dip),46(plugdev),100(users),105(lpadmin),124(sambashare) >>>>>>>>> and when I start jpilot from the command line I get the following error >>>>>>>>> messages: >>>>>>>>> >>>>>>>>> john@Lenovo-ideapad-320-15ABR:~$ jpilot >>>>>>>>> >>>>>>>>> (jpilot:2134): Gtk-CRITICAL **: 20:42:56.126: gtk_list_store_get_path: >>>>>>>>> assertion 'iter->stamp == priv->stamp' failed >>>>>>>>> >>>>>>>>> (jpilot:2134): Gtk-CRITICAL **: 20:42:56.126: >>>>>>>>> gtk_tree_selection_select_path: assertion 'path != NULL' failed >>>>>>>>> >>>>>>>>> I have no idea what to do with that, so any and all help is greatly >>>>>>>>> appreciated. >>>>>>>>> >>>>>>>>> Regards, >>>>>>>>> John >>>>>>>>> >>>>>>>>> >>>>>>>>> On Wed, Jun 3, 2026 at 12:55 AM Ulf Zibis <Ulf.Zibis@cosoco.de> wrote: >>>>>>>>> >>>>>>>>>> @ Judd ... >>>>>>>>>> >>>>>>>>>> Hi Judd, >>>>>>>>>> could you add such hint on your web site www.JPilot.org ? >>>>>>>>>> >>>>>>>>>> Also it cold be useful, if the JPilot application would show this in >>>>>>>> case, >>>>>>>>>> sync doesn't work. >>>>>>>>>> >>>>>>>>>> Regards, >>>>>>>>>> Ulf >>>>>>>>>> >>>>>>>>>> Am 03.06.26 um 01:21 schrieb Ulf Zibis: >>>>>>>>>>> Hi John and Paul, >>>>>>>>>>> >>>>>>>>>>> if you run JPilot as root, your data will be stored in /root/.jpilot. >>>>>>>>>>> If you later run JPilot as user it will look into $HOME/.jpilot. >>>>>> That's >>>>>>>>>> why you don't see anything. >>>>>>>>>>> In standard configuration the user has no rights to sync, because it >>>>>>>>>> needs the rights of group `dialout`. >>>>>>>>>>> You can check if your user has `dialout` rights with the command >>>>>> `id`. >>>>>>>>>>> If not, on Ubuntu you need to run `sudo usermod -a -G dialout $USER` >>>>>> to >>>>>>>>>> add this group rights to your user account. >>>>>>>>>>> Then reboot your machine to make the command aktive. >>>>>>>>>>> After, you should be able to sync your Palm device as normal user. >>>>>>>>>>> >>>>>>>>>>> Note: It is not recommended to run graphical applications as root on >>>>>>>>>> Ubuntu, because it can cause corruption of your file in $HOME/. >>>>>>>>>>> -Ulf >>>>>>>>>>> >>>>>>>>>>> Am 01.06.26 um 09:12 schrieb John Morrow: >>>>>>>>>>>> Paul, >>>>>>>>>>>> >>>>>>>>>>>> I took your suggestion and started JPilot as root, installed my >>>>>>>> username >>>>>>>>>>>> and synced. After a few attempts it worked. I had to close and >>>>>> re-open >>>>>>>>>> the >>>>>>>>>>>> terminal window but in the end, all my data from the PDA is now >>>>>>>> visible >>>>>>>>>> in >>>>>>>>>>>> JPilot. I don't know what a "dialout group" is, but apparently I >>>>>>>>>>>> didn't need to change it. Interesting, if I don't use the sudo >>>>>>>> command, >>>>>>>>>>>> the program opens without displaying any data. >>>>>>>>>>>> >>>>>>>>>>>> Thanks to all! >>>>>>>>>>>> John Morrow >>>>>>>>>>>> >>>>>>>>>>>> On Sat, Mar 14, 2026 at 5:48 AM Ulf Zibis <Ulf.Zibis@cosoco.de> >>>>>>>> wrote: >>>>>>>>>>>>> Hi Paul, >>>>>>>>>>>>> >>>>>>>>>>>>> I do not understand, why running JPilot as root should be good >>>>>> for. I >>>>>>>>>> more >>>>>>>>>>>>> think, it could be dangerous. >>>>>>>>>>>>> >>>>>>>>>>>>> For synching it's enough to add group `dialout` to the normal user. >>>>>>>>>>>>> >>>>>>>>>>>>> -Ulf >>>>>>>>>>>>> >>>>>>>>>>>>> Am 13.03.26 um 01:38 schrieb Paul Donlan: >>>>>>>>>>>>>> Try opening Palm Pilot on *Command Line*: sudo jpilot >>>>>>>>>>>>>> Then your password >>>>>>>>>>>>>> Then open "File" and Press "Install User" >>>>>>>>>>>>>> After you have installed your user name, *Sync* handheld. >>>>>>>>>>>>>> It should work >>>>>>>>>>>>>> >>>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>>> Jpilot mailing list -- jpilot@lists.jpilot.org >>>>>>>>>>>>>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org >>>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>>> Jpilot mailing list -- jpilot@lists.jpilot.org >>>>>>>>>>>>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org >>>>>>>>>>>>> >>>>>>>>>>>> _______________________________________________ >>>>>>>>>>>> Jpilot mailing list -- jpilot@lists.jpilot.org >>>>>>>>>>>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> Jpilot mailing list -- jpilot@lists.jpilot.org >>>>>>>>>>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org >>>>>>>>>> _______________________________________________ >>>>>>>>>> Jpilot mailing list -- jpilot@lists.jpilot.org >>>>>>>>>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org >>>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> Jpilot mailing list -- jpilot@lists.jpilot.org >>>>>>>>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org >>>>>>>> _______________________________________________ >>>>>>>> Jpilot mailing list -- jpilot@lists.jpilot.org >>>>>>>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org >>>>>>>> >>>>>>> _______________________________________________ >>>>>>> Jpilot mailing list -- jpilot@lists.jpilot.org >>>>>>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org >>>>>> -- >>>>>> ===== >>>>>> milgram@cgpp.com >>>>>> 301-257-7069 >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Jpilot mailing list -- jpilot@lists.jpilot.org >>>>>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org >>>>>> >>>>> _______________________________________________ >>>>> Jpilot mailing list -- jpilot@lists.jpilot.org >>>>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org >>>> -- >>>> ===== >>>> milgram@cgpp.com >>>> 301-257-7069 >>>> >>>> >>>> _______________________________________________ >>>> Jpilot mailing list -- jpilot@lists.jpilot.org >>>> To unsubscribe send an email to jpilot-leave@lists.jpilot.org >> -- >> ===== >> milgram@cgpp.com >> 301-257-7069 >> >> >> _______________________________________________ >> Jpilot mailing list -- jpilot@lists.jpilot.org >> To unsubscribe send an email to jpilot-leave@lists.jpilot.org > _______________________________________________ > Jpilot mailing list -- jpilot@lists.jpilot.org > To unsubscribe send an email to jpilot-leave@lists.jpilot.org -- ===== milgram@cgpp.com 301-257-7069

On Thu, 30 Jul 2026, J. Milgram via Jpilot wrote: > BTW for some reason SBo categorizes it as "accessibility" but personally I > think it should be "office" ... before I recommend a change, any history > there I should know about? office +1 Rich