jpilot@lists.jpilot.org

General support, questions, patches for J-Pilot.

View all threads

Jpilot on Ubuntu 24.04

KJ
Kevin Jaspan
Fri, Dec 27, 2024 8:06 PM

I had to reinstall Jpilot after clobbering my boot partition when it was
full. I used the new installation method, with the curl .... and it
installed with ease. However it won't launch and I get an error message:
(jpilot:5438): Gtk-WARNING **: 15:04:06.916: cannot open display: :0.0
when trying to invoke it from the command line, which I never had to do
ever before.

Has anybody else had this peculiar issue? I have never had this on any
other of my desktops, including another running Ubuntu 24.04, as is this
one.

Kevin

Sent from my 64 bit AMD® Ryzen 5 5600g 6 core hp Pavilion desktop
running Ubuntu Linux 22.04

I had to reinstall Jpilot after clobbering my boot partition when it was full. I used the new installation method, with the curl .... and it installed with ease. However it won't launch and I get an error message: (jpilot:5438): Gtk-WARNING **: 15:04:06.916: cannot open display: :0.0 when trying to invoke it from the command line, which I never had to do ever before. Has anybody else had this peculiar issue? I have never had this on any other of my desktops, including another running Ubuntu 24.04, as is this one. Kevin -- Sent from my 64 bit AMD® Ryzen 5 5600g 6 core hp Pavilion desktop running Ubuntu Linux 22.04
B
Bob
Fri, Dec 27, 2024 10:35 PM

I have had a similar problem with another package, seems it opened but on
a different desktop??

if this doesn't work let me know how you installed it as I was just
getting ready to reinstall it after putting in a new hard drive and
upgrading to 24.04 myself.

Bob

On Fri, 27 Dec 2024, Kevin Jaspan wrote:

I had to reinstall Jpilot after clobbering my boot partition when it was
full. I used the new installation method, with the curl .... and it
installed with ease. However it won't launch and I get an error message:
(jpilot:5438): Gtk-WARNING **: 15:04:06.916: cannot open display: :0.0
when trying to invoke it from the command line, which I never had to do
ever before.

Has anybody else had this peculiar issue? I have never had this on any
other of my desktops, including another running Ubuntu 24.04, as is this
one.

Kevin

Sent from my 64 bit AMD® Ryzen 5 5600g 6 core hp Pavilion desktop
running Ubuntu Linux 22.04


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

I have had a similar problem with another package, seems it opened but on a different desktop?? if this doesn't work let me know how you installed it as I was just getting ready to reinstall it after putting in a new hard drive and upgrading to 24.04 myself. Bob On Fri, 27 Dec 2024, Kevin Jaspan wrote: > I had to reinstall Jpilot after clobbering my boot partition when it was > full. I used the new installation method, with the curl .... and it > installed with ease. However it won't launch and I get an error message: > (jpilot:5438): Gtk-WARNING **: 15:04:06.916: cannot open display: :0.0 > when trying to invoke it from the command line, which I never had to do > ever before. > > Has anybody else had this peculiar issue? I have never had this on any > other of my desktops, including another running Ubuntu 24.04, as is this > one. > > Kevin > -- > > Sent from my 64 bit AMD® Ryzen 5 5600g 6 core hp Pavilion desktop > running Ubuntu Linux 22.04 > _______________________________________________ > Jpilot mailing list -- jpilot@lists.jpilot.org > To unsubscribe send an email to jpilot-leave@lists.jpilot.org > >
KJ
Kevin Jaspan
Fri, Dec 27, 2024 10:38 PM

I installed it with the instructions on the main Jpilot.org page:

curl -s https://packagecloud.io/install/repositories/judd/jpilot/script.deb.sh
| sudo bash
sudo apt install jpilot jpilot-plugins

On Fri, Dec 27, 2024 at 5:35 PM Bob accessys@smart.net wrote:

I have had a similar problem with another package, seems it opened but on
a different desktop??

if this doesn't work let me know how you installed it as I was just
getting ready to reinstall it after putting in a new hard drive and
upgrading to 24.04 myself.

Bob

On Fri, 27 Dec 2024, Kevin Jaspan wrote:

I had to reinstall Jpilot after clobbering my boot partition when it was
full. I used the new installation method, with the curl .... and it
installed with ease. However it won't launch and I get an error message:
(jpilot:5438): Gtk-WARNING **: 15:04:06.916: cannot open display: :0.0
when trying to invoke it from the command line, which I never had to do
ever before.

Has anybody else had this peculiar issue? I have never had this on any
other of my desktops, including another running Ubuntu 24.04, as is this
one.

Kevin

Sent from my 64 bit AMD® Ryzen 5 5600g 6 core hp Pavilion desktop
running Ubuntu Linux 22.04


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

--

Sent from my 64 bit AMD® Ryzen 5 5600g 6 core hp Pavilion desktop
running Ubuntu Linux 22.04

I installed it with the instructions on the main Jpilot.org page: curl -s https://packagecloud.io/install/repositories/judd/jpilot/script.deb.sh | sudo bash sudo apt install jpilot jpilot-plugins On Fri, Dec 27, 2024 at 5:35 PM Bob <accessys@smart.net> wrote: > > I have had a similar problem with another package, seems it opened but on > a different desktop?? > > if this doesn't work let me know how you installed it as I was just > getting ready to reinstall it after putting in a new hard drive and > upgrading to 24.04 myself. > > > Bob > > > > On Fri, 27 Dec 2024, Kevin Jaspan wrote: > > > I had to reinstall Jpilot after clobbering my boot partition when it was > > full. I used the new installation method, with the curl .... and it > > installed with ease. However it won't launch and I get an error message: > > (jpilot:5438): Gtk-WARNING **: 15:04:06.916: cannot open display: :0.0 > > when trying to invoke it from the command line, which I never had to do > > ever before. > > > > Has anybody else had this peculiar issue? I have never had this on any > > other of my desktops, including another running Ubuntu 24.04, as is this > > one. > > > > Kevin > > -- > > > > Sent from my 64 bit AMD® Ryzen 5 5600g 6 core hp Pavilion desktop > > running Ubuntu Linux 22.04 > > _______________________________________________ > > 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 > -- Sent from my 64 bit AMD® Ryzen 5 5600g 6 core hp Pavilion desktop running Ubuntu Linux 22.04
DH
D. Hugh Redelmeier
Sat, Dec 28, 2024 4:04 PM

From: Kevin Jaspan kjaspan@gmail.com

However it won't launch and I get an error message:
(jpilot:5438): Gtk-WARNING **: 15:04:06.916: cannot open display: :0.0
when trying to invoke it from the command line, which I never had to do
ever before.

I assume that you are trying to launch jpilot from a terminal window on
your Ubuntu GNOME (or KDE) desktop.

Is your new desktop using Wayland?  Was your old one running X?  Wayland
has replaced X in many Linux distros.  What does this say, when run from a
terminal window on your desktop:
$ xisxwayland -v

Look at the value of $DISPLAY in a terminal window on your desktop
$ echo $DISPLAY

That environment variable tells X programs what display server to use.

If your new system's display is being run by Wayland instead of X, I think
that $DISPLAY is meaningless (I'm not sure).  It certainly isn't as
powerful as under X: X protocol could cross network links and display on a
different machine but Wayland cannot.

This might be useful to explain the X side of the story:
https://stackoverflow.com/questions/784404/how-can-i-specify-a-display

> From: Kevin Jaspan <kjaspan@gmail.com> > However it won't launch and I get an error message: > (jpilot:5438): Gtk-WARNING **: 15:04:06.916: cannot open display: :0.0 > when trying to invoke it from the command line, which I never had to do > ever before. I assume that you are trying to launch jpilot from a terminal window on your Ubuntu GNOME (or KDE) desktop. Is your new desktop using Wayland? Was your old one running X? Wayland has replaced X in many Linux distros. What does this say, when run from a terminal window on your desktop: $ xisxwayland -v Look at the value of $DISPLAY in a terminal window on your desktop $ echo $DISPLAY That environment variable tells X programs what display server to use. If your new system's display is being run by Wayland instead of X, I think that $DISPLAY is meaningless (I'm not sure). It certainly isn't as powerful as under X: X protocol could cross network links and display on a different machine but Wayland cannot. This might be useful to explain the X side of the story: <https://stackoverflow.com/questions/784404/how-can-i-specify-a-display>
KJ
Kevin Jaspan
Sat, Dec 28, 2024 5:41 PM

Hugh,
The xisxwayland -v command gives:
Command not found.
echo $DISPLAY gives nothing.
I'm pretty certain I'm running Wayland or, at least, gdm3. What mystifies
me is that I've never had this problem before until I rebuilt Ubuntu 24.04.

Thanks for your help,

Kevin

On Sat, Dec 28, 2024 at 11:04 AM D. Hugh Redelmeier hugh@mimosa.com wrote:

From: Kevin Jaspan kjaspan@gmail.com

However it won't launch and I get an error message:
(jpilot:5438): Gtk-WARNING **: 15:04:06.916: cannot open display: :0.0
when trying to invoke it from the command line, which I never had to do
ever before.

I assume that you are trying to launch jpilot from a terminal window on
your Ubuntu GNOME (or KDE) desktop.

Is your new desktop using Wayland?  Was your old one running X?  Wayland
has replaced X in many Linux distros.  What does this say, when run from a
terminal window on your desktop:
$ xisxwayland -v

Look at the value of $DISPLAY in a terminal window on your desktop
$ echo $DISPLAY

That environment variable tells X programs what display server to use.

If your new system's display is being run by Wayland instead of X, I think
that $DISPLAY is meaningless (I'm not sure).  It certainly isn't as
powerful as under X: X protocol could cross network links and display on a
different machine but Wayland cannot.

This might be useful to explain the X side of the story:
https://stackoverflow.com/questions/784404/how-can-i-specify-a-display


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

--

Sent from my 64 bit AMD® Ryzen 5 5600g 6 core hp Pavilion desktop
running Ubuntu Linux 22.04

Hugh, The xisxwayland -v command gives: Command not found. echo $DISPLAY gives nothing. I'm pretty certain I'm running Wayland or, at least, gdm3. What mystifies me is that I've never had this problem before until I rebuilt Ubuntu 24.04. Thanks for your help, Kevin On Sat, Dec 28, 2024 at 11:04 AM D. Hugh Redelmeier <hugh@mimosa.com> wrote: > > From: Kevin Jaspan <kjaspan@gmail.com> > > > However it won't launch and I get an error message: > > (jpilot:5438): Gtk-WARNING **: 15:04:06.916: cannot open display: :0.0 > > when trying to invoke it from the command line, which I never had to do > > ever before. > > I assume that you are trying to launch jpilot from a terminal window on > your Ubuntu GNOME (or KDE) desktop. > > Is your new desktop using Wayland? Was your old one running X? Wayland > has replaced X in many Linux distros. What does this say, when run from a > terminal window on your desktop: > $ xisxwayland -v > > Look at the value of $DISPLAY in a terminal window on your desktop > $ echo $DISPLAY > > That environment variable tells X programs what display server to use. > > If your new system's display is being run by Wayland instead of X, I think > that $DISPLAY is meaningless (I'm not sure). It certainly isn't as > powerful as under X: X protocol could cross network links and display on a > different machine but Wayland cannot. > > This might be useful to explain the X side of the story: > <https://stackoverflow.com/questions/784404/how-can-i-specify-a-display> > _______________________________________________ > Jpilot mailing list -- jpilot@lists.jpilot.org > To unsubscribe send an email to jpilot-leave@lists.jpilot.org > -- Sent from my 64 bit AMD® Ryzen 5 5600g 6 core hp Pavilion desktop running Ubuntu Linux 22.04
TC
Tom Chiverton
Sun, Dec 29, 2024 3:32 PM

On Friday, 27 December 2024 22:38:27 GMT Kevin Jaspan wrote:

I installed it with the instructions on the main Jpilot.org page:

curl -s https://packagecloud.io/install/repositories/judd/jpilot/script.deb.sh
| sudo bash
sudo apt install jpilot jpilot-plugins

Hmm, So I'm not sure why you are trying to start J-Pilot from the command line. Is your Linux machine remote to you (in which case, how is the Palm connected ?!) ?

Assuming your Palm is connected to you local Linux machine, either with the serial cable or Bluetooth, you should have a file /usr/share/applications/jpilot.desktop. This is what populates the standard desktop "start" menu's application list.
You don't start J-Pilot from the command line.

With this file in place, you should be able to find "j-Pilot" in your menu in the same place as all your other applications and/or in the quick launcher (ALT-F2 in Kde I think?).
If this file is missing, you can create it by running sudoedit /usr/share/applications/jpilot.desktop and entering the following:

--------------do not include this line-----------
[Desktop Entry]
Name=J-Pilot
Comment=Desktop organizer application for the Palm Pilot
Exec=jpilot
Icon=jpilot.xpm
Terminal=false
Type=Application
Categories=Office;PDA;
--------------do not include this line-----------

--
Tom

On Friday, 27 December 2024 22:38:27 GMT Kevin Jaspan wrote: > I installed it with the instructions on the main Jpilot.org page: > > curl -s https://packagecloud.io/install/repositories/judd/jpilot/script.deb.sh > | sudo bash > sudo apt install jpilot jpilot-plugins Hmm, So I'm not sure why you are trying to start J-Pilot from the command line. Is your Linux machine remote to you (in which case, how is the Palm connected ?!) ? Assuming your Palm is connected to you local Linux machine, either with the serial cable or Bluetooth, you should have a file `/usr/share/applications/jpilot.desktop`. This is what populates the standard desktop "start" menu's application list. You don't start J-Pilot from the command line. With this file in place, you should be able to find "j-Pilot" in your menu in the same place as all your other applications and/or in the quick launcher (ALT-F2 in Kde I think?). If this file is missing, you can create it by running `sudoedit /usr/share/applications/jpilot.desktop` and entering the following: --------------do not include this line----------- [Desktop Entry] Name=J-Pilot Comment=Desktop organizer application for the Palm Pilot Exec=jpilot Icon=jpilot.xpm Terminal=false Type=Application Categories=Office;PDA; --------------do not include this line----------- -- Tom
KJ
Kevin Jaspan
Sun, Dec 29, 2024 3:35 PM

I am not trying to start from the command line. It was just a suggestion I was given. When I click on the icon it flashes briefly but nothing opens.
Sent from my iPad

On Dec 29, 2024, at 10:32 AM, Tom Chiverton tom+jpilot@falkensweb.com wrote:

On Friday, 27 December 2024 22:38:27 GMT Kevin Jaspan wrote:

I installed it with the instructions on the main Jpilot.org page:

curl -s https://packagecloud.io/install/repositories/judd/jpilot/script.deb.sh
| sudo bash
sudo apt install jpilot jpilot-plugins

Hmm, So I'm not sure why you are trying to start J-Pilot from the command line. Is your Linux machine remote to you (in which case, how is the Palm connected ?!) ?

Assuming your Palm is connected to you local Linux machine, either with the serial cable or Bluetooth, you should have a file /usr/share/applications/jpilot.desktop. This is what populates the standard desktop "start" menu's application list.
You don't start J-Pilot from the command line.

With this file in place, you should be able to find "j-Pilot" in your menu in the same place as all your other applications and/or in the quick launcher (ALT-F2 in Kde I think?).
If this file is missing, you can create it by running sudoedit /usr/share/applications/jpilot.desktop and entering the following:

--------------do not include this line-----------
[Desktop Entry]
Name=J-Pilot
Comment=Desktop organizer application for the Palm Pilot
Exec=jpilot
Icon=jpilot.xpm
Terminal=false
Type=Application
Categories=Office;PDA;
--------------do not include this line-----------

--
Tom


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

I am not trying to start from the command line. It was just a suggestion I was given. When I click on the icon it flashes briefly but nothing opens. Sent from my iPad > On Dec 29, 2024, at 10:32 AM, Tom Chiverton <tom+jpilot@falkensweb.com> wrote: > > On Friday, 27 December 2024 22:38:27 GMT Kevin Jaspan wrote: >> I installed it with the instructions on the main Jpilot.org page: >> >> curl -s https://packagecloud.io/install/repositories/judd/jpilot/script.deb.sh >> | sudo bash >> sudo apt install jpilot jpilot-plugins > > Hmm, So I'm not sure why you are trying to start J-Pilot from the command line. Is your Linux machine remote to you (in which case, how is the Palm connected ?!) ? > > Assuming your Palm is connected to you local Linux machine, either with the serial cable or Bluetooth, you should have a file `/usr/share/applications/jpilot.desktop`. This is what populates the standard desktop "start" menu's application list. > You don't start J-Pilot from the command line. > > With this file in place, you should be able to find "j-Pilot" in your menu in the same place as all your other applications and/or in the quick launcher (ALT-F2 in Kde I think?). > If this file is missing, you can create it by running `sudoedit /usr/share/applications/jpilot.desktop` and entering the following: > > --------------do not include this line----------- > [Desktop Entry] > Name=J-Pilot > Comment=Desktop organizer application for the Palm Pilot > Exec=jpilot > Icon=jpilot.xpm > Terminal=false > Type=Application > Categories=Office;PDA; > --------------do not include this line----------- > > > -- > Tom > _______________________________________________ > Jpilot mailing list -- jpilot@lists.jpilot.org > To unsubscribe send an email to jpilot-leave@lists.jpilot.org
TC
Tom Chiverton
Sun, Dec 29, 2024 4:54 PM

On Sunday, 29 December 2024 15:35:27 GMT Kevin Jaspan wrote:

I am not trying to start from the command line. It was just a suggestion I was given. When I click on the icon it flashes briefly but nothing opens.

Ah ha. So it's failing to start for some reason, exiting really quickly. Maybe someone else knows where jpilot keeps it's logs in this case ?

You can try a couple of tricks too.

  • replace Exec=jpilot with Exec=...whatever the output of "which jpilot" is such as Exec=/usr/bin/jpilot. If it's just an off path issue, this might fix it.
  • create a new application menu entry (KDE has a "Menu Editor"). Program should "konsole --noclose -e ...which jpilot output...". This should launch the command, but keep a window open to see the logs, per https://askubuntu.com/a/1126049[1]

I'm on Kubuntu 24.10, installed J-Pilot the same way, and do not have this issue. It'd be helpful if you could confirm if you are on X or Wayland. There should be an option on the login screen. It's a little subtle here...

Tom


[1] https://askubuntu.com/a/1126049

On Sunday, 29 December 2024 15:35:27 GMT Kevin Jaspan wrote: > I am not trying to start from the command line. It was just a suggestion I was given. When I click on the icon it flashes briefly but nothing opens. Ah ha. So it's failing to start for some reason, exiting really quickly. Maybe someone else knows where jpilot keeps it's logs in this case ? You can try a couple of tricks too. * replace `Exec=jpilot` with `Exec=...whatever the output of "which jpilot" is` such as `Exec=/usr/bin/jpilot`. If it's just an off path issue, this might fix it. * create a new application menu entry (KDE has a "Menu Editor"). Program should "konsole --noclose -e ...which jpilot output...". This should launch the command, but keep a window open to see the logs, per https://askubuntu.com/a/1126049[1] I'm on Kubuntu 24.10, installed J-Pilot the same way, and do not have this issue. It'd be helpful if you could confirm if you are on X or Wayland. There should be an option on the login screen. It's a little subtle here... -- Tom -------- [1] https://askubuntu.com/a/1126049
KJ
Kevin Jaspan
Sun, Dec 29, 2024 5:12 PM

Tom,
I’m pretty sure I’m on gdm3 on Wayland. We’ve had yet another power failure so I cannot explore further. Ubuntu 24.04.1

Kevin
Sent from my iPad

On Dec 29, 2024, at 11:54 AM, Tom Chiverton tom+jpilot@falkensweb.com wrote:

On Sunday, 29 December 2024 15:35:27 GMT Kevin Jaspan wrote:

I am not trying to start from the command line. It was just a suggestion I was given. When I click on the icon it flashes briefly but nothing opens.

Ah ha. So it's failing to start for some reason, exiting really quickly. Maybe someone else knows where jpilot keeps it's logs in this case ?

You can try a couple of tricks too.

  • replace Exec=jpilot with Exec=...whatever the output of "which jpilot" is such as Exec=/usr/bin/jpilot. If it's just an off path issue, this might fix it.
  • create a new application menu entry (KDE has a "Menu Editor"). Program should "konsole --noclose -e ...which jpilot output...". This should launch the command, but keep a window open to see the logs, per https://askubuntu.com/a/1126049[1]

I'm on Kubuntu 24.10, installed J-Pilot the same way, and do not have this issue. It'd be helpful if you could confirm if you are on X or Wayland. There should be an option on the login screen. It's a little subtle here...

Tom


[1] https://askubuntu.com/a/1126049


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

Tom, I’m pretty sure I’m on gdm3 on Wayland. We’ve had yet another power failure so I cannot explore further. Ubuntu 24.04.1 Kevin Sent from my iPad > On Dec 29, 2024, at 11:54 AM, Tom Chiverton <tom+jpilot@falkensweb.com> wrote: > > On Sunday, 29 December 2024 15:35:27 GMT Kevin Jaspan wrote: >> I am not trying to start from the command line. It was just a suggestion I was given. When I click on the icon it flashes briefly but nothing opens. > > > Ah ha. So it's failing to start for some reason, exiting really quickly. Maybe someone else knows where jpilot keeps it's logs in this case ? > > > You can try a couple of tricks too. > > > * replace `Exec=jpilot` with `Exec=...whatever the output of "which jpilot" is` such as `Exec=/usr/bin/jpilot`. If it's just an off path issue, this might fix it. > * create a new application menu entry (KDE has a "Menu Editor"). Program should "konsole --noclose -e ...which jpilot output...". This should launch the command, but keep a window open to see the logs, per https://askubuntu.com/a/1126049[1] > > > I'm on Kubuntu 24.10, installed J-Pilot the same way, and do not have this issue. It'd be helpful if you could confirm if you are on X or Wayland. There should be an option on the login screen. It's a little subtle here... > -- > Tom > > -------- > [1] https://askubuntu.com/a/1126049 > _______________________________________________ > Jpilot mailing list -- jpilot@lists.jpilot.org > To unsubscribe send an email to jpilot-leave@lists.jpilot.org
KJ
Kevin Jaspan
Sun, Dec 29, 2024 6:53 PM

Tom,
The Jpilot service file was exactly as you suggested it should be.
I assume you mean, in the second bullet, to create a startup application,
and put some command there. Should that command be:
konsole --noclose -e
?
Anyway, I had Jpilot as an application I could select from the Apps menu,
with an icon I could click on. The problem is, as described before, it just
flashes and doesn't launch.

Kevin

On Sun, Dec 29, 2024 at 12:12 PM Kevin Jaspan kjaspan@gmail.com wrote:

Tom,
I’m pretty sure I’m on gdm3 on Wayland. We’ve had yet another power
failure so I cannot explore further. Ubuntu 24.04.1

Kevin
Sent from my iPad

On Dec 29, 2024, at 11:54 AM, Tom Chiverton tom+jpilot@falkensweb.com

wrote:

On Sunday, 29 December 2024 15:35:27 GMT Kevin Jaspan wrote:

I am not trying to start from the command line. It was just a

suggestion I was given. When I click on the icon it flashes briefly but
nothing opens.

Ah ha. So it's failing to start for some reason, exiting really quickly.

Maybe someone else knows where jpilot keeps it's logs in this case ?

You can try a couple of tricks too.

  • replace Exec=jpilot with `Exec=...whatever the output of "which

jpilot" issuch asExec=/usr/bin/jpilot`. If it's just an off path issue,
this might fix it.

  • create a new application menu entry (KDE has a "Menu Editor"). Program

should "konsole --noclose -e ...which jpilot output...". This should launch
the command, but keep a window open to see the logs, per
https://askubuntu.com/a/1126049[1]

I'm on Kubuntu 24.10, installed J-Pilot the same way, and do not have

this issue. It'd be helpful if you could confirm if you are on X or
Wayland. There should be an option on the login screen. It's a little
subtle here...

--
Tom


[1] https://askubuntu.com/a/1126049


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

--

Sent from my 64 bit AMD® Ryzen 5 5600g 6 core hp Pavilion desktop
running Ubuntu Linux 22.04

Tom, The Jpilot service file was exactly as you suggested it should be. I assume you mean, in the second bullet, to create a startup application, and put some command there. Should that command be: konsole --noclose -e ? Anyway, I had Jpilot as an application I could select from the Apps menu, with an icon I could click on. The problem is, as described before, it just flashes and doesn't launch. Kevin On Sun, Dec 29, 2024 at 12:12 PM Kevin Jaspan <kjaspan@gmail.com> wrote: > Tom, > I’m pretty sure I’m on gdm3 on Wayland. We’ve had yet another power > failure so I cannot explore further. Ubuntu 24.04.1 > > Kevin > Sent from my iPad > > > On Dec 29, 2024, at 11:54 AM, Tom Chiverton <tom+jpilot@falkensweb.com> > wrote: > > > > On Sunday, 29 December 2024 15:35:27 GMT Kevin Jaspan wrote: > >> I am not trying to start from the command line. It was just a > suggestion I was given. When I click on the icon it flashes briefly but > nothing opens. > > > > > > Ah ha. So it's failing to start for some reason, exiting really quickly. > Maybe someone else knows where jpilot keeps it's logs in this case ? > > > > > > You can try a couple of tricks too. > > > > > > * replace `Exec=jpilot` with `Exec=...whatever the output of "which > jpilot" is` such as `Exec=/usr/bin/jpilot`. If it's just an off path issue, > this might fix it. > > * create a new application menu entry (KDE has a "Menu Editor"). Program > should "konsole --noclose -e ...which jpilot output...". This should launch > the command, but keep a window open to see the logs, per > https://askubuntu.com/a/1126049[1] > > > > > > I'm on Kubuntu 24.10, installed J-Pilot the same way, and do not have > this issue. It'd be helpful if you could confirm if you are on X or > Wayland. There should be an option on the login screen. It's a little > subtle here... > > -- > > Tom > > > > -------- > > [1] https://askubuntu.com/a/1126049 > > _______________________________________________ > > Jpilot mailing list -- jpilot@lists.jpilot.org > > To unsubscribe send an email to jpilot-leave@lists.jpilot.org > -- Sent from my 64 bit AMD® Ryzen 5 5600g 6 core hp Pavilion desktop running Ubuntu Linux 22.04