SXMO questions about wayland/X11

[dostoievsky]

It seens sxmo arch img runs with wayland as default.
How can I set X11 as default?
the image even try to install X11 libs?

[ArenM]

It seens sxmo arch img runs with wayland as default.

Correct

How can I set X11 as default?

Install `sxmo-utils-dwm` and then go to `Power -> Toggle WM` in the menu. You can uninstall `sxmo-utils-sway` after that if you want.

the image even try to install X11 libs?

I'm pretty sure xwayland is installed by default, if it's not it should probably be added.

[dostoievsky]

Hello ArenM,
thank you for the response, and also for the hard work that you guys are doing.
I've lost my whole day experimenting both barebone and the sxmo images.

Install sxmo-utils-dwm and then go to Power -> Toggle WM in the menu. You can uninstall sxmo-utils-sway after that if you want.

The Toggle WM button will be generated after the installation of sxmo-utils-dwm?
I searched for that button after reading a bit of the sxmo documentation but couldnt found it on the arch image.

I am trying the postmakerOS right now, and I fould the button there, even without dwm installed. It seens it runs and responds more smoothly thant the arch install, but I'm not sure yet.

This project is in need of something, is there any TODO or something that I could inform myself also?

[ArenM]

The Toggle WM button will be generated after the installation of sxmo-utils-dwm? I searched for that button after reading a bit of the sxmo documentation but couldnt found it on the arch image.

Yup, it's not possible to toggle properly without dwm installed.

I am trying the postmakerOS right now, and I fould the button there, even without dwm installed. It seens it runs and responds more smoothly thant the arch install, but I'm not sure yet.

The pmos packages were less strict, so sometimes it will show up but toggling fails. I believe this was updated to match the behavior on arch, but that might still be only in edge.

This project is in need of something, is there any TODO or something that I could inform myself also?

https://todo.sr.ht/~mil/sxmo-tickets might be a good start. If you could quantify "more smoothly" it would make it easier to to look at what the difference is.

[dostoievsky]

Hello ArenM.

I tried to run X11 on postmarket yesterday as we are exchange here.
I installed sxmo-utils and sxmo-build throught git repos and choosed the right configuration for X11. I had some problems with some packages and debugged then myself and made it right.

Then I pressed the Switch WM button, the cellphone restarted, and I went to TTY. With the messagem "sxmo is not started" or something like that, as I cant exactly remember the message.

But is the same message when I tried to use justine sxmo-alarm yesterday and had some missconfigurations that didnt work.

It seens that the services/systemd process didnt started correctly and maybe a status output message can enrich this conversation futher.

I'll try today to install DWM on the arch-sxmo image and see what will happen. For that, I am with some question yet that I would like to clarify:

Install sxmo-utils-dwm and then go to Power -> Toggle WM in the menu. You can uninstall sxmo-utils-sway after that if you want.

I cant find any reference for this package or repo.

I did find: https://git.sr.ht/~mil/sxmo-dwm

And I know that https://git.sr.ht/~mil/sxmo-build is able to install X11 config throught --X11 argument on sh execution.

But this later, sxmo-build, fails to configure the services in the arch enviroment, so sxmo X11 will never start prorpely because of that.

As I did read right now, https://git.sr.ht/~mil/sxmo-dwm
says to just create an .xinit with exec DWM and maybe that is what I missed in the postmarketOS enviroment, and thus, thats why it failled. I'll try it today on the arch setup and see what happens.

I have checked quickly the https://todo.sr.ht/~mil/sxmo-tickets and I thank you for pointing that out.

I am interessed in contribute to the X11 enviroment, as I dont want to use wayland yet, and spend time learning sway and other things (I think it will be easy) but I like the dwm/st/etc enviroment, and do not see any point to move to wayland yet.

I am also interessed in contribute to the arch ecosystem in that subject, and I think you're maybe one of the most informed ones on that point.
I think, also, a better documentation experience for archieve the X11 maybe would be a nice start point to contribute, what you think about that?

Thank you!

EDIT:

If you could quantify "more smoothly" it would make it easier to to look at what the difference is.

I think it was just a impression.
I noted throught htop that the pmOS install has 100MB less on the bare install, getting something at 250MB of RAM. The arch install is using arround 100MB more, maybe because of any extra daemon running that I didnt really checked.

I noticed the gestures respondend better on pmOS. But maybe it is because I got a little better with that after reading the official documentation.

In both distros, I had issues with the "touch" option being toggled off. I dont know if I did made a gesture that toggled that off. In the arch distro, yet, I could C+P and toggle it on in the config menu with keyboard, but in the pmOS that didnt work. So points for arch in this subject, as I didnt got fully locked. (seens if touch off, we cant use gestures also).

EDIT2:

I just cloned https://git.sr.ht/~mil/sxmo-dwm and instelled it system wide on ALARM. The WM button on power menu didnt showed up. I also did a restart, and even after that, the WM button wont show. Maybe this isnt the right method.

EDIT3:

I tried to use the logout button on power menu, to see if it would move me to TTY so I could 'exec dwm' myself. But after the screen got black, it just logged me again in wayland.

EDIT4:

Maybe, the barebone install + sxmo-build + sxmo-utils would be a better start point for people who want X11 instead of sway? I'll experiment this method and leave here all my impressions, problems and fixes.

[dostoievsky]

Experiment on Barebone:

sudo pacman -Syu
sudo pacman -Syu base-devel git
git clone https://git.sr.ht/~mil/sxmo-build

Edit sxmo_build_all.sh,
change nerd-fonts-fira-code to otf-firamono-nerd
(I dont know if it is the right one)
Also is needed to add: scdoc pnc xorg-server xorg-xinit

remove ~anjan/pnc from repos.

now

sh sxmo_build_all.sh --x11

Now, we will get our first error with clickclack:

clickclack.c: In function ‘vibrate’:
clickclack.c:81:45: error: ‘O_CLOEXEC’ undeclared (first use in this function); did you mean ‘FD_CLOEXEC’?
   81 |         fd = open(vibra_event_dev, O_RDWR | O_CLOEXEC);
      |                                             ^~~~~~~~~
      |                                             FD_CLOEXEC

To resolve:

cd build-sxmo-dev/clickclack

choose your favorite editor and edit the makefile:

at

$(CC) $(CFLAGS) -o clickclack clickclack.c -l SDL2

change it to

$(CC) $(CFLAGS) -D_GNU_SOURCE -o clickclack clickclack.c -l SDL2

run again:

sh sxmo_build_all.sh --x11

And that is it, the packages are installed.

create a .xinitrc on your graphic user ~/

write
exec dwm

and do a startx.

DWM will start.

BUT there isnt any sxmo config or setup yet.

NEXT ROUND:

what must be done to a bare minimum sxmo setup now?

lisgd will return:

libinput error: client bug: Invalid path /dev/input/touchscreen
Couldn't bind event from dev filesystem

I tried to build

https://aur.archlinux.org/packages/sxmo-utils-git

and I am getting the following error:

Hunk #1 FAILED at 16.
1 out of 1 hunk FAILED -- saving rejects to file scripts/core/sxmo_common.sh.rej
patching file scripts/core/sxmo_winit.sh
patching file scripts/core/sxmo_xinit.sh
==> ERROR: A failure occurred in prepare().
    Aborting...

also it seens that this aur is focused just in sway:

make -c "sxmo-utils" DESTDIR="$pkgdir" install-sway

I think i am just beated lol

[ArenM]

I tried to run X11 on postmarket yesterday as we are exchange here. I installed sxmo-utils and sxmo-build throught git repos and choosed the right configuration for X11. I had some problems with some packages and debugged then myself and made it right. Then I pressed the Switch WM button, the cellphone restarted, and I went to TTY. With the messagem "sxmo is not started" or something like that, as I cant exactly remember the message.

That's exactly the behavior that we're trying to avoid by not showing the button at all. You need postmarketos-ui-sxmo-dwm (or something like that).

But is the same message when I tried to use justine sxmo-alarm yesterday and had some missconfigurations that didnt work. [snip] I cant find any reference for this package or repo. I did find: https://git.sr.ht/~mil/sxmo-dwm And I know that https://git.sr.ht/~mil/sxmo-build is able to install X11 config throught --X11 argument on sh execution. But this later, sxmo-build, fails to configure the services in the arch enviroment, so sxmo X11 will never start prorpely because of that.

Justine's scripts and sxmo-build are both quite out of date. On arch, you should be using the sxmo-utils packages provided by this repository. The sxmo-utils-git packages in the aur are also (sometimes) up to date, but it doesn't have the dwm variant. So all you need to do is `sudo pacman -S sxmo-utils-dwm`.

…

--- Sxmo-utils is built from https://git.sr.ht/~mil/sxmo-utils, and it split into sxmo-utils, sxmo-utils-sway, and sxmo-utils-dwm to help keep the dependencies down.

[dostoievsky]

`
[alarm@danctnix yay]$ sudo pacman -S sxmo-utils-dwm
resolving dependencies...
warning: cannot resolve "autocutsel", a dependency of "sxmo-utils-dwm"
:: The following package cannot be upgraded due to unresolvable dependencies:
sxmo-utils-dwm

:: Do you want to skip the above package for this upgrade? [y/N]
`
Why a package only avaliable on AUR would be a dependency for sxmo-utils-dwm?
https://wiki.archlinux.org/title/clipboard#Managers

https://archlinux.org/packages/extra/x86_64/autocutsel/
https://aur.archlinux.org/packages/autocutsel

`
[alarm@danctnix yay]$ yay -S autocutsel
AUR Explicit (1): autocutsel-0.10.1-2
Sync Dependency (1): libxaw-1.0.16-1
:: (1/1) Downloaded PKGBUILD: autocutsel
1 autocutsel (Build Files Exist)
==> Packages to cleanBuild?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==> N
1 autocutsel (Build Files Exist)
==> Diffs to show?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==> N
==> ERROR: autocutsel is not available for the 'aarch64' architecture.
-> error downloading sources: /home/alarm/.cache/yay/autocutsel
context: exit status 12

:: (1/1) Parsing SRCINFO: autocutsel
-> The following packages are not compatible with your architecture:
autocutsel
:: Try to build them anyway? [Y/n]

`

I did try to build anyway and now I am installing sxmo-utils-dwm.
The button appeared and yeah it did work! Thank you.

I have one last question, since we are installing dwm, st, surf and alikes with packages, how could I customize them? Where can I find the basic repositorie that contains the sames defaults of packages so I can customize and build then myself after that?

I think is just use the repos
https://git.sr.ht/~mil/sxmo-dwm
right?

Well, very thanks! Now I can focus on some ricing.

[ArenM]

Why a package only avaliable on AUR would be a dependency for sxmo-utils-dwm?

It seems like it was probably removed since the last time I updated sxmo-utils, I'll need to add a package to the danctnix repos for it.

I have one last question, since we are installing dwm, st, surf and alikes with packages, how could I customize them? Where can I find the basic repositorie that contains the sames defaults of packages so I can customize and build then myself after that?

Oddly enough that's not a question that seems to get asked a lot, I think your options are to modify the sxmo-utils pkgbuild to not depend on dwm, or to modify the dwm pkgbuild to point at your source tree, both of those pkgbuild files are in this repo. (s/dwm/st..etc/g)

[dostoievsky]

Hey ArenM,

About the packages, even if they are firstly downloaded, if we clone the original repos like
https://git.sr.ht/~mil/sxmo-dwm, sxmo-st, etc... when we build they with make install, the original package at /usr/local/bin gets replaced by the new builded one. So this is okay, we can use the ones in sxmo-utils and then rice out using the base repos, since they are the same (I didnt checked if it is really the same, but it seens to be the same base, so it is a go).

Sadly, seens that the X11 option is very buggy:

When the screen rotates, it seens like the window get cuted, the hour goes to left-botton, the middle gots a sliced cut, and works very buggy.

The buttons, volume, power, dosent respond correctly, and none of the commands works. The phone turns on/off, but the locks states dosent work properly.

Also, when I try to open apps (htop, nano, etc) they flash up in the screen and dosent open at all.
But if I do mod1+return with kb, st pops up like in desktop.

For someone like me, thats first needs to learn how sxmo works, it is a hard start point, since those behaviors need to be debbuged before the phone become usable.

I switched back to wayland, and all those behaviors works perfectly on wayland. I'll keep with wayland ATM, to get used with sxmo, before trying to understand why X11 is so buggy ATM.

It seens that X11 has a little better performance than wayland. I got 50MB more running on it than on wayland. I would like also try to understand what was the decision to fully support wayland and cover the X11 option as it was done.

But SXMO is a very nice setup and I thank the effort of everyone involved in the project.

Again thank you for keeping the discussion with me.

EDIT:

About autocutsel, whould be possible to choose betwen xclip and autocutsel, instead of force a dependency upon autocutsel?