Installing Xojo on linux/KDE neon

I can’t get xojo to work. Used the ubuntu installer to install xojo but immediately get an error. I have used Xojo/Realbasic earlier on mac os but now trying to try it again on Linux… Does anyone have any experience of Xojo with KDE Neon… ?

I don’t use KDE, but check here for notes. Also better use X11 than Wayland. your distro supports X11?

https://documentation.xojo.com/resources/system_requirements_for_current_release.html

Unfortunately, I don’t know anything about UNBUNTU.

I use Arch Linux with GNOME. I’ve never tried KDE.

In my setup, I initially ran XOJO under X11, but now I’m running it under Wayland. Everything works perfectly.

Unfortunately, I can’t use an installer in Arch Linux, so I’m installing XOJO manually.
Installing XOJO (Example: XOJO Version 2024 R3):

sudo -s
cd /opt/xojo
tar -zxvf /home/<myUserName>/Downloads/xojo2024r3.tgz

cd xojo2024r3
mv 2024r3_63767.desktop /usr/share/applications/2024r3_63767.desktop

After that, there are a few more adjustments:

Then edit the desktop file: All the directories in this file have the suffix “_63767”. However, the new directory in “/opt/xojo” is named “xojo2024r3”, not “xojo2024r3_63767”.

Then set the correct icon: Replace the PNG file with “xojo.xpm”

Now all you have to do is copy the required plugins into the plugin folder. In this example, that would be “/opt/xojo/xojo2024r3/Plugins”.

You should now be able to use XOJO on Arch Linux.

1 Like

It would be immensely helpful if you told everyone what the error was, instead of leaving us to guess.

My first thought was… did you install all of the prerequisites from the system requirements page?

1 Like

On this page select the one for your distro ……ubuntu would be the “debian” one .

that is the one that I used with Linux Mint Xojo: Downloads

I tried reinstalling the .deb installer. Of course I do not totally know what I am doing, I started using CrossBasic long time ago, then it was renamed into RealBasic and then Xojo and then family happened :slight_smile:… Now after many years I would like to try programming a bit on this linux computer (mac is outdated, at work Win11, at home I now prefer linux, so much nicer desktop experience and no ads, works perfect on my mini laptop which only supports win10 –> now better on linux).

I will try to figure out if I can get it to work but am quite time-limited (work + kids) and post here if I manage to get it running.

I am running KDE Neon which is based on Ubuntu LTS 24.04 (Xojo Linux requirements states “Linux (x86_64/ARM64) Current LTS versions of Ubuntu 20.04 or later”). When trying to start Xojo, I get the following error message:

Trying to click “Report Now” opens the same error message again and I get a message that the application has encountered an error. On clicking details I get the following:

PID: 30219 (Xojo)

UID: 1000 (shr)

GID: 1000 (shr)

Signal: 11 (SEGV)

Timestamp: Sun 2026-05-17 22:45:18 EEST (7s ago)

Command Line: /opt/xojo/xojo2026r1.2/Xojo

Executable: /opt/xojo/xojo2026r1.2/Xojo

Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-xojo2026r1.2@cb2759bb0b31473784cc731d3aa75fb1.service

Unit: user@1000.service

User Unit: app-xojo2026r1.2@cb2759bb0b31473784cc731d3aa75fb1.service

Slice: user-1000.slice

Owner UID: 1000 (shr)

Boot ID: 78eb6f3f0f3a48a0973641bfbdb25afd

Machine ID: f6f17c34796941a092366e53f025939e

Hostname: minisforum-BD790i

Storage: /var/lib/systemd/coredump/core.Xojo.1000.78eb6f3f0f3a48a0973641bfbdb25afd.30219.1779047118000000.zst (present)

Size on Disk: 4.5M

Message: Process 30219 (Xojo) of user 1000 dumped core.

Module libstdc++.so.6 from deb gcc-14-14.2.0-4ubuntu2~24.04.1.amd64

Module libzstd.so.1 from deb libzstd-1.5.5+dfsg2-2build1.1.amd64

Module libsystemd.so.0 from deb systemd-255.4-1ubuntu8.15.amd64

Module libgcc_s.so.1 from deb gcc-14-14.2.0-4ubuntu2~24.04.1.amd64

Module Xojo without build-id.

Stack trace of thread 30219:

#0 0x000079e40b403b20 main_arena (libc.so.6 + 0x203b20)

#1 0x000079e40a5ee747 g_hook_free (libglib-2.0.so.0 + 0x4b747)

#2 0x000079e40b482ed9 n/a (libgobject-2.0.so.0 + 0x44ed9)

#3 0x000079e40b473591 n/a (libgobject-2.0.so.0 + 0x35591)

#4 0x000079e40b4737c1 g_signal_emit_valist (libgobject-2.0.so.0 + 0x357c1)

#5 0x000079e40b473883 g_signal_emit (libgobject-2.0.so.0 + 0x35883)

#6 0x000079e40ad60f7f gtk_widget_map (libgtk-3.so.0 + 0x360f7f)

#7 0x000079e40aac8158 n/a (libgtk-3.so.0 + 0xc8158)

#8 0x000079e40ab18e8b n/a (libgtk-3.so.0 + 0x118e8b)

#9 0x000079e40b45325c g_closure_invoke (libgobject-2.0.so.0 + 0x1525c)

#10 0x000079e40b482a50 n/a (libgobject-2.0.so.0 + 0x44a50)

#11 0x000079e40b473591 n/a (libgobject-2.0.so.0 + 0x35591)

#12 0x000079e40b4737c1 g_signal_emit_valist (libgobject-2.0.so.0 + 0x357c1)

#13 0x000079e40b473883 g_signal_emit (libgobject-2.0.so.0 + 0x35883)

#14 0x000079e40ad60f7f gtk_widget_map (libgtk-3.so.0 + 0x360f7f)

#15 0x000079e40aac8158 n/a (libgtk-3.so.0 + 0xc8158)

#16 0x000079e40ab18e8b n/a (libgtk-3.so.0 + 0x118e8b)

#17 0x000079e40b45325c g_closure_invoke (libgobject-2.0.so.0 + 0x1525c)

#18 0x000079e40b482a50 n/a (libgobject-2.0.so.0 + 0x44a50)

#19 0x000079e40b473591 n/a (libgobject-2.0.so.0 + 0x35591)

#20 0x000079e40b4737c1 g_signal_emit_valist (libgobject-2.0.so.0 + 0x357c1)

#21 0x000079e40b473883 g_signal_emit (libgobject-2.0.so.0 + 0x35883)

#22 0x000079e40ad60f7f gtk_widget_map (libgtk-3.so.0 + 0x360f7f)

#23 0x000079e40ad78570 n/a (libgtk-3.so.0 + 0x378570)

#24 0x000079e40ab5ff25 n/a (libgtk-3.so.0 + 0x15ff25)

#25 0x000079e40b4532fa g_closure_invoke (libgobject-2.0.so.0 + 0x152fa)

#26 0x000079e40b482a50 n/a (libgobject-2.0.so.0 + 0x44a50)

#27 0x000079e40b473591 n/a (libgobject-2.0.so.0 + 0x35591)

#28 0x000079e40b4737c1 g_signal_emit_valist (libgobject-2.0.so.0 + 0x357c1)

#29 0x000079e40b473883 g_signal_emit (libgobject-2.0.so.0 + 0x35883)

#30 0x000079e40ad60f7f gtk_widget_map (libgtk-3.so.0 + 0x360f7f)

#31 0x000079e40ad7cf5b n/a (libgtk-3.so.0 + 0x37cf5b)

#32 0x000079e40b4532fa g_closure_invoke (libgobject-2.0.so.0 + 0x152fa)

#33 0x000079e40b482a50 n/a (libgobject-2.0.so.0 + 0x44a50)

#34 0x000079e40b473591 n/a (libgobject-2.0.so.0 + 0x35591)

#35 0x000079e40b4737c1 g_signal_emit_valist (libgobject-2.0.so.0 + 0x357c1)

#36 0x000079e40b473883 g_signal_emit (libgobject-2.0.so.0 + 0x35883)

#37 0x000079e40ad58330 gtk_widget_show (libgtk-3.so.0 + 0x358330)

#38 0x000079e40ab60e70 gtk_dialog_run (libgtk-3.so.0 + 0x160e70)

#39 0x000079e40b9249a7 n/a (XojoGUIFramework64.so + 0x3249a7)

#40 0x000079e40b9c321e UnhandledException (XojoGUIFramework64.so + 0x3c321e)

#41 0x0000000001731b26 REALbasic._UnhandledException%%o (Xojo + 0x1531b26)

#42 0x0000000016e48785 _Main (Xojo + 0x16c48785)

#43 0x0000000016e03d03 main (Xojo + 0x16c03d03)

#44 0x000079e40b22a1ca __libc_start_call_main (libc.so.6 + 0x2a1ca)

#45 0x000079e40b22a28b __libc_start_main_impl (libc.so.6 + 0x2a28b)

#46 0x0000000000647029 __init_array_start (Xojo + 0x447029)

ELF object binary architecture: AMD x86-64

Forgot to mention that I was using Wayland. I switched to X11 and get exactly the same error message on X11 (at least to me it looks identical to the error message I got on Wayland). Also trying to click the “Report Now” button gives the same error message again…

       PID: 32896 (Xojo)
       UID: 1000 (shr)
       GID: 1000 (shr)
    Signal: 11 (SEGV)
 Timestamp: Sun 2026-05-17 22:58:15 EEST (6s ago)

Command Line: /opt/xojo/xojo2026r1.2/Xojo
Executable: /opt/xojo/xojo2026r1.2/Xojo
Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-xojo2026r1.2@9373333bb34d48de941cd9207f5bb512.service
Unit: user@1000.service
User Unit: app-xojo2026r1.2@9373333bb34d48de941cd9207f5bb512.service
Slice: user-1000.slice
Owner UID: 1000 (shr)
Boot ID: 78eb6f3f0f3a48a0973641bfbdb25afd
Machine ID: f6f17c34796941a092366e53f025939e
Hostname: minisforum-BD790i
Storage: /var/lib/systemd/coredump/core.Xojo.1000.78eb6f3f0f3a48a0973641bfbdb25afd.32896.1779047895000000.zst (present)
Size on Disk: 4.4M
Message: Process 32896 (Xojo) of user 1000 dumped core.

            Module libstdc++.so.6 from deb gcc-14-14.2.0-4ubuntu2~24.04.1.amd64
            Module libzstd.so.1 from deb libzstd-1.5.5+dfsg2-2build1.1.amd64
            Module libsystemd.so.0 from deb systemd-255.4-1ubuntu8.15.amd64
            Module libgcc_s.so.1 from deb gcc-14-14.2.0-4ubuntu2~24.04.1.amd64
            Module Xojo without build-id.
            Stack trace of thread 32896:
            #0  0x0000756f72403b20 main_arena (libc.so.6 + 0x203b20)
            #1  0x0000756f715ee747 g_hook_free (libglib-2.0.so.0 + 0x4b747)
            #2  0x0000756f724aced9 n/a (libgobject-2.0.so.0 + 0x44ed9)
            #3  0x0000756f7249d591 n/a (libgobject-2.0.so.0 + 0x35591)
            #4  0x0000756f7249d7c1 g_signal_emit_valist (libgobject-2.0.so.0 + 0x357c1)
            #5  0x0000756f7249d883 g_signal_emit (libgobject-2.0.so.0 + 0x35883)
            #6  0x0000756f71d60f7f gtk_widget_map (libgtk-3.so.0 + 0x360f7f)
            #7  0x0000756f71ac8158 n/a (libgtk-3.so.0 + 0xc8158)
            #8  0x0000756f71b18e8b n/a (libgtk-3.so.0 + 0x118e8b)
            #9  0x0000756f7247d25c g_closure_invoke (libgobject-2.0.so.0 + 0x1525c)
            #10 0x0000756f724aca50 n/a (libgobject-2.0.so.0 + 0x44a50)
            #11 0x0000756f7249d591 n/a (libgobject-2.0.so.0 + 0x35591)
            #12 0x0000756f7249d7c1 g_signal_emit_valist (libgobject-2.0.so.0 + 0x357c1)
            #13 0x0000756f7249d883 g_signal_emit (libgobject-2.0.so.0 + 0x35883)
            #14 0x0000756f71d60f7f gtk_widget_map (libgtk-3.so.0 + 0x360f7f)
            #15 0x0000756f71ac8158 n/a (libgtk-3.so.0 + 0xc8158)
            #16 0x0000756f71b18e8b n/a (libgtk-3.so.0 + 0x118e8b)
            #17 0x0000756f7247d25c g_closure_invoke (libgobject-2.0.so.0 + 0x1525c)
            #18 0x0000756f724aca50 n/a (libgobject-2.0.so.0 + 0x44a50)
            #19 0x0000756f7249d591 n/a (libgobject-2.0.so.0 + 0x35591)
            #20 0x0000756f7249d7c1 g_signal_emit_valist (libgobject-2.0.so.0 + 0x357c1)
            #21 0x0000756f7249d883 g_signal_emit (libgobject-2.0.so.0 + 0x35883)
            #22 0x0000756f71d60f7f gtk_widget_map (libgtk-3.so.0 + 0x360f7f)
            #23 0x0000756f71d78570 n/a (libgtk-3.so.0 + 0x378570)
            #24 0x0000756f71b5ff25 n/a (libgtk-3.so.0 + 0x15ff25)
            #25 0x0000756f7247d2fa g_closure_invoke (libgobject-2.0.so.0 + 0x152fa)
            #26 0x0000756f724aca50 n/a (libgobject-2.0.so.0 + 0x44a50)
            #27 0x0000756f7249d591 n/a (libgobject-2.0.so.0 + 0x35591)
            #28 0x0000756f7249d7c1 g_signal_emit_valist (libgobject-2.0.so.0 + 0x357c1)
            #29 0x0000756f7249d883 g_signal_emit (libgobject-2.0.so.0 + 0x35883)
            #30 0x0000756f71d60f7f gtk_widget_map (libgtk-3.so.0 + 0x360f7f)
            #31 0x0000756f71d7cf5b n/a (libgtk-3.so.0 + 0x37cf5b)
            #32 0x0000756f7247d2fa g_closure_invoke (libgobject-2.0.so.0 + 0x152fa)
            #33 0x0000756f724aca50 n/a (libgobject-2.0.so.0 + 0x44a50)
            #34 0x0000756f7249d591 n/a (libgobject-2.0.so.0 + 0x35591)
            #35 0x0000756f7249d7c1 g_signal_emit_valist (libgobject-2.0.so.0 + 0x357c1)
            #36 0x0000756f7249d883 g_signal_emit (libgobject-2.0.so.0 + 0x35883)
            #37 0x0000756f71d58330 gtk_widget_show (libgtk-3.so.0 + 0x358330)
            #38 0x0000756f71b60e70 gtk_dialog_run (libgtk-3.so.0 + 0x160e70)
            #39 0x0000756f729249a7 n/a (XojoGUIFramework64.so + 0x3249a7)
            #40 0x0000756f729c321e UnhandledException (XojoGUIFramework64.so + 0x3c321e)
            #41 0x0000000001731b26 REALbasic._UnhandledException%%o<RuntimeException> (Xojo + 0x1531b26)
            #42 0x0000000016e48785 _Main (Xojo + 0x16c48785)
            #43 0x0000000016e03d03 main (Xojo + 0x16c03d03)
            #44 0x0000756f7222a1ca __libc_start_call_main (libc.so.6 + 0x2a1ca)
            #45 0x0000756f7222a28b __libc_start_main_impl (libc.so.6 + 0x2a28b)
            #46 0x0000000000647029 __init_array_start (Xojo + 0x447029)
            ELF object binary architecture: AMD x86-64

Just like on macOS, start Xojo from within a Terminal and you will see why it fails (in most cases).

I tried to launch it from the terminal but got the same error dialog and this output in the terminal. I am not much wiser now (and not an expert in linux)…

I am afraid only someone from xojo can solve this if it is an error within Xojo…? Of course it can be related to KDE Neon too :slight_smile:

Thank you for everyone for your tips and answers!

shr@minisforum-BD790i:/media/homedisk/shr$ cd /opt/xojo/xojo2026r1.2/
shr@minisforum-BD790i:/opt/xojo/xojo2026r1.2$ ls
 2026r1.2_67271.desktop   Extensions   Extras   Plugins  'Project Templates'  'Read Mes'   Scripts   Xojo  'Xojo Libs'  'Xojo Resources'   xojo.xpm
shr@minisforum-BD790i:/opt/xojo/xojo2026r1.2$ ls -l
total 381304
-rw-r--r--  1 root root       486 huhti  28 02:01  2026r1.2_67271.desktop
drwxr-xr-x  2 root root      4096 touko  17 22:44  Extensions
drwxr-xr-x 10 root root      4096 touko  17 22:44  Extras
drwxr-xr-x  2 root root      4096 touko  17 22:44  Plugins
drwxr-xr-x  2 root root      4096 touko  17 22:44 'Project Templates'
drwxr-xr-x  2 root root      4096 touko  17 22:44 'Read Mes'
drwxr-xr-x  2 root root      4096 huhti  28 02:01  Scripts
-rwxr-xr-x  1 root root 390182696 huhti  28 02:01  Xojo
drwxr-xr-x  2 root root      4096 touko  17 22:44 'Xojo Libs'
drwxr-xr-x 21 root root    163840 touko  17 22:44 'Xojo Resources'
-rwxr-xr-x  1 root root     61839 huhti  28 02:02  xojo.xpm
shr@minisforum-BD790i:/opt/xojo/xojo2026r1.2$ ./Xojo
Segmentation fault (core dumped)
shr@minisforum-BD790i:/opt/xojo/xojo2026r1.2$ 

And in the file /var/log/syslog I found the following:

2026-05-18T23:05:54.155789+03:00 minisforum-BD790i kernel: Xojo[60823]: segfault at 70aaab803b20 ip 000070aaab803b20 sp 00007ffcae4b0078 error 15 in libc.so.6[202b20,70aaab803000+2000] likely on CPU 0 (core 0, socket 0)
2026-05-18T23:05:54.155805+03:00 minisforum-BD790i kernel: Code: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 <e0> 97 23 1f 00 00 00 00 b0 99 08 1f 00 00 00 00 20 3b 80 ab aa 70
2026-05-18T23:05:54.179119+03:00 minisforum-BD790i systemd[1]: Started systemd-coredump@8-60865-0.service - Process Core Dump (PID 60865/UID 0).
2026-05-18T23:05:54.180746+03:00 minisforum-BD790i systemd[1]: Started drkonqi-coredump-processor@8-60865-0.service - Pass systemd-coredump journal entries to relevant user for potential DrKonqi handling.
2026-05-18T23:05:54.474968+03:00 minisforum-BD790i systemd-coredump[60866]: Process 60823 (Xojo) of user 1000 dumped core.#012#012Module libstdc++.so.6 from deb gcc-14-14.2.0-4ubuntu2~24.04.1.amd64#012Module libzstd.so.1 from deb libzstd-1.5.5+dfsg2-2build1.1.amd64#012Module libsystemd.so.0 from deb systemd-255.4-1ubuntu8.15.amd64#012Module libgcc_s.so.1 from deb gcc-14-14.2.0-4ubuntu2~24.04.1.amd64#012Module Xojo without build-id.#012Stack trace of thread 60823:#012#0  0x000070aaab803b20 main_arena (libc.so.6 + 0x203b20)#012#1  0x000070aaaaacf747 g_hook_free (libglib-2.0.so.0 + 0x4b747)#012#2  0x000070aaaac11ed9 n/a (libgobject-2.0.so.0 + 0x44ed9)#012#3  0x000070aaaac02591 n/a (libgobject-2.0.so.0 + 0x35591)#012#4  0x000070aaaac027c1 g_signal_emit_valist (libgobject-2.0.so.0 + 0x357c1)#012#5  0x000070aaaac02883 g_signal_emit (libgobject-2.0.so.0 + 0x35883)#012#6  0x000070aaab160f7f gtk_widget_map (libgtk-3.so.0 + 0x360f7f)#012#7  0x000070aaaaec8158 n/a (libgtk-3.so.0 + 0xc8158)#012#8  0x000070aaaaf18e8b n/a (libgtk-3.so.0 + 0x118e8b)#012#9  0x000070aaaabe225c g_closure_invoke (libgobject-2.0.so.0 + 0x1525c)#012#10 0x000070aaaac11a50 n/a (libgobject-2.0.so.0 + 0x44a50)#012#11 0x000070aaaac02591 n/a (libgobject-2.0.so.0 + 0x35591)#012#12 0x000070aaaac027c1 g_signal_emit_valist (libgobject-2.0.so.0 + 0x357c1)#012#13 0x000070aaaac02883 g_signal_emit (libgobject-2.0.so.0 + 0x35883)#012#14 0x000070aaab160f7f gtk_widget_map (libgtk-3.so.0 + 0x360f7f)#012#15 0x000070aaaaec8158 n/a (libgtk-3.so.0 + 0xc8158)#012#16 0x000070aaaaf18e8b n/a (libgtk-3.so.0 + 0x118e8b)#012#17 0x000070aaaabe225c g_closure_invoke (libgobject-2.0.so.0 + 0x1525c)#012#18 0x000070aaaac11a50 n/a (libgobject-2.0.so.0 + 0x44a50)#012#19 0x000070aaaac02591 n/a (libgobject-2.0.so.0 + 0x35591)#012#20 0x000070aaaac027c1 g_signal_emit_valist (libgobject-2.0.so.0 + 0x357c1)#012#21 0x000070aaaac02883 g_signal_emit (libgobject-2.0.so.0 + 0x35883)#012#22 0x000070aaab160f7f gtk_widget_map (libgtk-3.so.0 + 0x360f7f)#012#23 0x000070aaab178570 n/a (libgtk-3.so.0 + 0x378570)#012#24 0x000070aaaaf5ff25 n/a (libgtk-3.so.0 + 0x15ff25)#012#25 0x000070aaaabe22fa g_closure_invoke (libgobject-2.0.so.0 + 0x152fa)#012#26 0x000070aaaac11a50 n/a (libgobject-2.0.so.0 + 0x44a50)#012#27 0x000070aaaac02591 n/a (libgobject-2.0.so.0 + 0x35591)#012#28 0x000070aaaac027c1 g_signal_emit_valist (libgobject-2.0.so.0 + 0x357c1)#012#29 0x000070aaaac02883 g_signal_emit (libgobject-2.0.so.0 + 0x35883)#012#30 0x000070aaab160f7f gtk_widget_map (libgtk-3.so.0 + 0x360f7f)#012#31 0x000070aaab17cf5b n/a (libgtk-3.so.0 + 0x37cf5b)#012#32 0x000070aaaabe22fa g_closure_invoke (libgobject-2.0.so.0 + 0x152fa)#012#33 0x000070aaaac11a50 n/a (libgobject-2.0.so.0 + 0x44a50)#012#34 0x000070aaaac02591 n/a (libgobject-2.0.so.0 + 0x35591)#012#35 0x000070aaaac027c1 g_signal_emit_valist (libgobject-2.0.so.0 + 0x357c1)#012#36 0x000070aaaac02883 g_signal_emit (libgobject-2.0.so.0 + 0x35883)#012#37 0x000070aaab158330 gtk_widget_show (libgtk-3.so.0 + 0x358330)#012#38 0x000070aaaaf60e70 gtk_dialog_run (libgtk-3.so.0 + 0x160e70)#012#39 0x000070aaabd249a7 n/a (XojoGUIFramework64.so + 0x3249a7)#012#40 0x000070aaabdc321e UnhandledException (XojoGUIFramework64.so + 0x3c321e)#012#41 0x0000000001731b26 REALbasic._UnhandledException%%o<RuntimeException> (Xojo + 0x1531b26)#012#42 0x0000000016e48785 _Main (Xojo + 0x16c48785)#012#43 0x0000000016e03d03 main (Xojo + 0x16c03d03)#012#44 0x000070aaab62a1ca __libc_start_call_main (libc.so.6 + 0x2a1ca)#012#45 0x000070aaab62a28b __libc_start_main_impl (libc.so.6 + 0x2a28b)#012#46 0x0000000000647029 __init_array_start (Xojo + 0x447029)#012ELF object binary architecture: AMD x86-64
2026-05-18T23:05:54.492208+03:00 minisforum-BD790i systemd[1]: systemd-coredump@8-60865-0.service: Deactivated successfully.
2026-05-18T23:05:54.767244+03:00 minisforum-BD790i drkonqi-coredump-processor[60867]: "/opt/xojo/xojo2026r1.2/Xojo" 60823 "/var/lib/systemd/coredump/core.Xojo.1000.78eb6f3f0f3a48a0973641bfbdb25afd.60823.1779134754000000.zst"
2026-05-18T23:05:54.771167+03:00 minisforum-BD790i systemd[1]: drkonqi-coredump-processor@8-60865-0.service: Deactivated successfully.
2026-05-18T23:05:54.784151+03:00 minisforum-BD790i systemd[35667]: Started drkonqi-coredump-launcher@6-60867-0.service - Launch DrKonqi for a systemd-coredump crash (PID 60867/UID 0).
2026-05-18T23:05:54.806968+03:00 minisforum-BD790i drkonqi-coredump-launcher[60879]: Unable to find file for pid 60823 expected at "kcrash-metadata/Xojo.78eb6f3f0f3a48a0973641bfbdb25afd.60823.ini"
2026-05-18T23:05:54.807325+03:00 minisforum-BD790i drkonqi-coredump-launcher[60879]: KCrash metadata not marked complete. Please file a bug at bugs.kde.org giving as much detail about the crash as possible and maybe include the file ""

Maybe there are missing libs? You can check this by doing a:

ldd ./Xojo | grep "not found"

If this does not help, make sure the most important libs are installed:

sudo apt update
sudo apt install libgtk-3-0 libwebkit2gtk-4.0-37 libsecret-1-0 libunwind8

If it still fails, start it using strace:

strace -o xojo_trace.txt ./Xojo

and then check the xojo_trace.txt file after the crash.

1 Like

I tried the following:

sudo apt install libunwind8 – success
sudo apt install libsecret-1-0 – success
sudo apt install libgtk-3-0 – success

FAIL:
sudo apt install libwebkit2gtk-4.0-37
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
Package libwebkit2gtk-4.0-37 is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package ‘libwebkit2gtk-4.0-37’ has no installation candidate

RESOLVE:
edit the file /etc/apt/sources.list: add the line “deb http://gb.archive.ubuntu.com/ubuntu jammy main”

sudo apt update
sudo apt install libwebkit2gtk-4.0-37

Then I tried

./Xojo

and got the same error as ever: “This application has encountered a fatal problem and must be shut down…

Then I tried (like recommended)

shr@minisforum-BD790i:/opt/xojo/xojo2026r1.2$ strace -o xojo_trace.txt ./Xojo
strace: Can't fopen 'xojo_trace.txt': Permission denied

…and I thought I never get it running. But then after a moment of thinking (without really knowing what I am doing I tried…

shr@minisforum-BD790i:/opt/xojo/xojo2026r1.2$ sudo strace -o xojo_trace.txt ./Xojo

And after entering the password…

So now I can get Xojo to start if I start it with sudo ./xojo but just ./xojo does not work. Should it be like that? Anyway, now I can start exploring a bit (but first have to go to sleep, wake up, go to work, be with kids, so story will be continued tomorrow).

Sorry for the long post but I tried to gather my steps here in case I have to do it again or someone else finds any help from my and other peoples replies. Thank you for everyone who was helping, I would not have got so far (to the splash screen!!!) without your help!!!

1 Like

This clearly indicates that this is a permissions issue.

First, grant your user read and execute permissions for the entire folder:

sudo chmod -R 755 /opt/xojo/xojo2026r1.2/

Then correct the ownership of all hidden Xojo configuration folders in your home dir using the following command (replace [username] with your actual username):

sudo chown -R [username]:[username] ~/.Xojo ~/.config/Xojo ~/.cache/Xojo 2>/dev/null

During startup, Xojo makes heavy use of the systems temporary directory to unpack libraries. If any folders/files from your sudo launch are still there, they will block you.
Better delete them doing a:

sudo rm -rf /tmp/Xojo*
sudo rm -rf /tmp/com.xojo*

Now test it again as normal (non sudo) user. :slight_smile:

Hello again, thank again for the advice. I guess the chown command should be like chown -R [username]:[groupname] …

Anyway, I still cannot start Xojo without doing “sudo ./Xojo”.

Maybe I have messed up my system. I will try to install it on my tablet computer or laptop (also KDE Neon) to see if I get it running properly there. Otherwise I just try to use it as superuser to see to be able to start doing what I really want to try to do (an app for myself helping calculate intraocular lens powers for cataract surgery, I am an eye doctor).

I will report my results here in case someone else is going to try Xojo…

2 Likes

Update: I installed KDE Neon on my tablet computer and installed Xojo on it and it works (at least starts and a small test app runs). However, this with this computer the IDE seems very slow and laggy (my son took the powerful computer to be a flight/racing sim). So maybe reinstalling the OS would resolve the problem on the other computer. Maybe I just have to get a faster computer to program on (but have no time)…