[SOLVED] RPi 3B after update: graphic applications crash

Ask questions about Arch Linux ARM. Please search before making a new topic.

[SOLVED] RPi 3B after update: graphic applications crash

Postby Iszzy » Fri Sep 17, 2021 3:12 pm

Hi all,

I have a raspberry pi model 3B with the official touchscreen display. On it, I start sddm, which automatically logs in a user to start sway. Logging in via ssh I can see that this part still works: sddm is running as root, sway is running as the expected user.

After that, the user starts a graphic application via systemd. This part stopped working after my recent system update (linux-raspberrypi went from 5.10.25-4 -> 5.10.63-7).

Now, the graphic application crashes. This is the relevant excerpt from systemd's log:

$this->bbcode_second_pass_code('', '
Sep 17 15:08:50 AlarmClock python[352]: Failed to create wl_display (No such file or directory)
Sep 17 15:08:50 AlarmClock kernel: kauditd_printk_skb: 5 callbacks suppressed
Sep 17 15:08:52 AlarmClock kernel: audit: type=1701 audit(1631884130.772:46): auid=1000 uid=1000 gid=1000 ses=2 pid=352 comm="PengClock" exe="/usr/bin/python3.9" sig=6 res=1
Sep 17 15:08:50 AlarmClock audit[352]: ANOM_ABEND auid=1000 uid=1000 gid=1000 ses=2 pid=352 comm="PengClock" exe="/usr/bin/python3.9" sig=6 res=1
Sep 17 15:08:50 AlarmClock python[352]: qt.qpa.plugin: Could not load the Qt platform plugin "wayland" in "" even though it was found.
Sep 17 15:08:50 AlarmClock python[352]: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb.
Sep 17 15:08:52 AlarmClock systemd[1]: Created slice Slice /system/systemd-coredump.
')

Suspecting it could be a Python/Qt/application problem, I have already tried starting another wayland app (alacritty). Since the RPi doesn't have a keyboard attached, I tried starting it through $this->bbcode_second_pass_code('', 'sway "exec alacritty"'). This way, I can't see error messages, but I can see that the application isn't running afterwards.

Unfortunately, I wasn't successful googling for a solution :(

Does anyone have an idea what might be going wrong?

Thanks in advance!
Last edited by Iszzy on Sun Sep 19, 2021 10:30 am, edited 1 time in total.
Iszzy
 
Posts: 11
Joined: Fri Jul 13, 2018 8:42 pm

Re: RPi 3B after update: graphic applications crash

Postby Iszzy » Sat Sep 18, 2021 4:53 pm

I finally managed to start sway manually, capturing its output. When starting alacritty, I now see this error output:

$this->bbcode_second_pass_code('', '
2021-09-18 18:33:46.741286717] [ERROR] [alacritty] Alacritty encountered an unrecoverable error:

There was an error initializing the shaders: Failed compiling shader: 0:1(10): error: GLSL 3.30 is not supported. Supported versions are: 1.10, 1.20, and 1.00 ES
')

So it seems it's a problem with the graphics driver? Maybe my /boot/config.txt is configured wrongly? For reference, this is it:

$this->bbcode_second_pass_code('', '
dtoverlay=vc4-fkms-v3d
initramfs initramfs-linux.img followkernel
dtparam=audio=on
')
Iszzy
 
Posts: 11
Joined: Fri Jul 13, 2018 8:42 pm

Re: RPi 3B after update: graphic applications crash

Postby Iszzy » Sat Sep 18, 2021 9:49 pm

OK, I made surprising progress :shock:

Although alacritty cannot be started via swaysock, my Python application can! And that is the important one, alacritty was only for testing...

This means, the whole problem now looks like a systemd issue: If I try to start my Python application via systemd, it crashes, because it cannot create a wayland display. If I start it via swaymsg, everything is fine.

Could the problem be that systemd (--user) suddenly needs more information when starting a graphic application?
Iszzy
 
Posts: 11
Joined: Fri Jul 13, 2018 8:42 pm

Re: [SOLVED] RPi 3B after update: graphic applications crash

Postby Iszzy » Sun Sep 19, 2021 10:35 am

I'm pretty sure now that the whole problem was that the systemd user session didn't have enough information about the running wayland instance. I could have researched more and probably could have set up more environment variables for the systemd user session (maybe WAYLAND_DISPLAY?) to make this work.

However, for the sake of simplicity, I have now resigned to start the application directly from sway. This way, I lose systemd's dependency and restarting mechanisms, unfortunately. But I think re-implementing those in a small shell script will save me some headaches over trying to get the systemd approach working :roll:

Marking the thread as [SOLVED]...
Iszzy
 
Posts: 11
Joined: Fri Jul 13, 2018 8:42 pm

Re: [SOLVED] RPi 3B after update: graphic applications crash

Postby komeyria55 » Thu Oct 07, 2021 7:41 pm

Hi,
It is solved or not?? myfiosgateway

Regards, spice money
Last edited by komeyria55 on Wed Oct 20, 2021 11:17 am, edited 1 time in total.
komeyria55
 
Posts: 1
Joined: Thu Oct 07, 2021 7:36 pm

Re: [SOLVED] RPi 3B after update: graphic applications crash

Postby Iszzy » Fri Oct 08, 2021 1:13 pm

$this->bbcode_second_pass_quote('komeyria55', 'H')i,
It is solved or not??


Well, I found a solution for myself (as explained in my previous post), so yes, for me, it is solved :)
Iszzy
 
Posts: 11
Joined: Fri Jul 13, 2018 8:42 pm


Return to User Questions

Who is online

Users browsing this forum: No registered users and 7 guests