Jpilot on Ubuntu 24.04
On Sunday, 29 December 2024 18:53:44 GMT Kevin Jaspan wrote:
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.
Yup; the intention is to create (to be safe, though you could modify the existing one), a file that contains
Exec=konsole --noclose -e /usr/bin/jpilot
Or similar. You can run which jpilot in a terminal window to find out what the full location is.
--
Tom
On 12/27/24 15:06, 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
Can you open other executables from the CLI like xeyes or xterm?
Is DISPLAY set? If so, try unsetting it.
Run
$ ls -adl .x* .X*
Do you own those files?
Judd
With
jpilot -d
you may get more debug information on the command line.
Am 27.12.24 um 21:06 schrieb Kevin Jaspan:
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
Tom,
The problem is now moot. I just managed to recover the Ubuntu
installation I thought I clobbered early this week and Jpilot launches
properly there.
Thanks for the help anyway,
Kevin
On Sun, Dec 29, 2024 at 2:26 PM Tom Chiverton tom+jpilot@falkensweb.com
wrote:
On Sunday, 29 December 2024 18:53:44 GMT Kevin Jaspan wrote:
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.
Yup; the intention is to create (to be safe, though you could modify the
existing one), a file that contains
Exec=konsole --noclose -e /usr/bin/jpilot
Or similar. You can run which jpilot in a terminal window to find out
what the full location is.
--
Tom
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
Ulf,
I get messages like unable to open logfile, but the file has one line in
it: removing stale pidfile. When I change permissions to 777 I get 1 error:
(jpilot:5302): Gtk-WARNING **: 23:07:03.260: cannot open display:
Kevin
On Sun, Dec 29, 2024 at 5:54 PM Ulf Zibis Ulf.Zibis@cosoco.de wrote:
With
jpilot -d
you may get more debug information on the command line.
Am 27.12.24 um 21:06 schrieb Kevin Jaspan:
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
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