[SOLVED] "Unclean" X (xfce4) & how about wayland?

business_kid · 05-23-2020, 12:33 PM

I have a new install of ~Current on a RazPi 4, and ran X as a new user. A very poor default config, firefox won't start, but it has wifi

It reminded me of those with leprosy in Bible times that had to go round shouting "Unclean" when anyone approached.
I did my usual trick of piping screen output to a file, and copying the Xorg.0.log. Here's some of the juicy bits you may have ideas on. Here's screen output:

Code:

(xfce4-session:1414): xfce4-session-WARNING **: 13:18:29.383: gpg-agent returned no PID in the variables.

> Internal error:   Could not resolve keysym XF86FullScreen

(xfwm4:1422): xfwm4-WARNING **: 13:18:29.531: Error opening /dev/dri/card0: No such file or directory

/usr/libexec/polkit-gnome-authentication-agent-1: error while loading shared libraries: libwayland-client.so.0: cannot open shared object file: No such file or directory

** (process:1485): WARNING **: 13:18:30.947: Failed to load shared library 'libgdk-3.so.0' referenced by the typelib: libwayland-client.so.0: cannot open shared object file: No such file or directory

Some of these I know. I don't need gpg; Bluetooth & hplip always seem to fall over in a mess of python hysteria until they get personal attention. XF86FullScreen is in /etc/X11/xkb/symbols/inet and '//' at the beginning of the line fixes that (comments it out).

Do I need wayland (as well as some of gnome) to run that sucky xfce WM? Is wayland better on the RazPi 4? What about /dev/dri/card0? Where's that gone?

From Xorg.0.log:

Code:

[  1441.188] (==) No screen section available. Using defaults.
        Using the first device section listed.
[  1441.189] (**) |   |-->Device "Allwinner A10/A13 FBDEV"
[  1441.197] (II) FBTURBO: driver for framebuffer: fbturbo … …
… …
[  1441.206] (WW) Falling back to old probe method for fbturbo

Is that right for X? Is there a sample /etc/X11/xorg.conf.d/video.conf online anywhere or should I cobble up one of my own?

That's about it, except for the usual "Lanigan's Ball" act by libinput
I stepped out, I stepped in again
I stepped out again, I stepped in again It loads and unloads half a dozen times

business_kid · 05-23-2020, 02:20 PM

Kinda sorted the rough stuff, by installing wayland and sqlite-3.x. I also had to add /usr/lib/firefox to /etc/ld.so.conf, which I shouldn't have to technically, but it's there now.The python errors from hplip and bluetooth (which I probably spared you) I can make go away by a battle of attrition, usually. I'm posting from the unfortunate Razpi 4 atm which is online via init scripts

. That at least spares me the python drama (usually a tragedy) with NetworkManager. Polkit, d-bus, glib & gtk are their usual hysterical selves, so all is well in the world.

I'd love to know if you can use wayland, or is it just a protocol?

Poprocks · 06-02-2020, 05:28 PM

I'd highly recommend trying Weston on Slackware Arm. I'm using it as my near-daily-driver on RPi4, 4GB RAM model. On a full install of a PAMified Slackware Current (excluding the kde package-group in my case) there are are no additional dependencies required.

I've submitted a current-specific Slackbuild to ponce for his SBo-git repo. Hopefully it will be added soon.

Assuming you're using the Raspbian kernel fork 5.4.x as packaged by SARPi, You'll want to change your config.txt to add

Code:

dtoverlay=vc4-kms-v3d-pi4

to run in pure (non-fake) KMS mode to allow for accelerated OpenGL support. Optionally, you'll also want to follow the instructions here:

https://www.raspberrypi.org/forums/v...69769#p1636828

Otherwise sound will not work properly (if at all) while using vc4-kms-v3d-pi4.

You can launch wayland by running (as root) in the console:

Code:

exec weston-launch -u $USER

(replacing $USER with the "normal user" you'd like Weston to be run by.)

You can then run firefox as packaged by Slackware Arm out of the box by running:

Code:

MOZ_ENABLE_WAYLAND=1 firefox

business_kid · 06-03-2020, 05:11 AM

Thanks for the fully detailed explanation.

I will certainly try that in the future. I've quite a slow workrate due to various issues, so I may not get to it immediately.