carbon-wayland

unklar · 2024-07-04 17:55:02

trixi/sid is prepared for metal to test carbon-wayland

https://forums.bunsenlabs.org/viewtopic … 54#p135554
https://github.com/BunsenLabs/bunsen-ne … on-wayland

I'm a bit irritated to get an x-system instead of wayland(labwc) as desktop first? Can you please enlighten me

johnraff · 2024-07-05 02:47:24

^There's no Wayland infrastructure there yet.

johnraff wrote:

At present the carbon-wayland netinstall script installs the regular carbon X-based setup

At the moment the carbon-wayland branch is a platform where that infrastructure will get built. There is as yet nothing at all anywhere resembling a BunsenLabs Wayland setup.

The people working on Wayland (including yourself!) are kindly requested to send GitHub Pull Requests to help bring that about.

I don't have time to work on Wayland myself right now, but it seems to me that the first thing to do might be to go over the package lists (pkgs-norecs-base and pkgs-recs-base), replacing openbox with labwc, adding necessary packages and removing those that cause problems.
(Micko01's experimental repo is enabled OOTB, so some non-Debian packages will be available as they are added there.)

Other config files etc etc can also be added.

---
I'm sorry that the README on that carbon-wayland branch gives the impression that things are already done:

This is a collection of files intended to install something like BunsenLabs Linux on a basic command-line-only Debian Trixie system, in a Wayland environment using the labwc compositor.

I need to add a note that this is still very much a Work In Progress.

Last edited by johnraff (2024-07-05 02:52:04)

unklar · 2024-07-05 09:58:45

Thank you very much!

My assumption was that carbon-wayland starts with labwc.

I ran the script earlier. It chose 'base' itself.
Since in the meantime the depot "https://01micko.github.io/debian trixie Release" was changed to 'carbon-trixie', there is this error:

    updating apt database...

OK:1 https://packages.siduction.org/extra unstable InRelease
OK:2 https://packages.siduction.org/fixes unstable InRelease
OK:3 https://deb.debian.org/debian unstable InRelease
Holen:4 https://pkg.bunsenlabs.org/debian carbon InRelease [6.359 B]
Ign:5 https://01micko.github.io/debian trixie InRelease
Fehl:6 https://01micko.github.io/debian trixie Release
  404  Not Found [IP: 185.199.110.153 443]
Holen:7 https://pkg.bunsenlabs.org/debian carbon/main amd64 Packages [13,2 kB]
Holen:8 https://pkg.bunsenlabs.org/debian carbon amd64 Contents (deb) [255 kB]
Paketlisten werden gelesen…
E: Das Depot »https://01micko.github.io/debian trixie Release« enthält keine Release-Datei.
######## WARNING ########
'apt-get --quiet update' returned an error

johnraff · 2024-07-05 11:11:30

Thanks - you've found another bug.

I'll fix that repo name tomorrow when I edit README.

And yes, the carbon-wayland branch goes directly to "base" without asking. When a base install is working OK, then checking over the other package lists might not be too difficult.

unklar · 2024-07-05 13:44:47

+1

Thank you for your efforts.

hhh · 2024-07-05 19:33:07

Here's how I setup labwc today on an 8 year old laptop.

I used the amd64-standard bookworm live ISO...

https://cdimage.debian.org/debian-cd/cu … bt-hybrid/

I used the bookworm image because I was installing over wireless and the trixie/sid installers give warnings about missing, non-existent iwlwifi ucodes that result in the network not being configured and apt not getting setup correctly.

As usual, do not set a root password.

When the install is finished...

sudo nano /etc/apt/sources.list

Comment everything out except for the main source. Change that source (and the scr source) to...

sid main contrib non-free non-free-firmware

You can use trixie instead if you want.

Then it's sudo apt update, sudo apt upgrade, sudo apt dist-upgrade, sudo apt --purge autoremove.

You'll get lots of messages about changes in packages, you can skip these by pressing q.

Reboot.

sudo apt install labwc sfwbar foot bemenu swaybg

That's the bare minimum. Next...

sudo apt install firefox thunar thunar-archive-plugin tumbler

sudo apt install mousepad gvfs gnome-keyring lxpolkit pkexec xdg-usr-dirs budgie-backgrounds

Of course you can choose your own text-editor, or choose firefox-esr insted of firefox. budgie-backgrounds I'll explain in the next post.

Reboot. Login and start labwc by running...

labwc

You should have a blue background and a pointer cursor. Your touchpad is already working with tap-to-click thanks to libinput. Click the background and you'll see a small menu that includes an Exit entry. Ctrl+Enter will open foot, a terminal. Alt+F3 will open bemenu, you can open thunar from bemenu and copy /usr/share/doc/labwc to ~/.config, make some edits, and logout/login again.

sudo apt install loupe xdg-user-dirs xdg-desktop-portal-wlr xdg-desktop-portal-gtk

loupe is a wayland image viewer, that will bring in libadwaita/gtk4. xdg-dsktop-portal-wlr will bring in and setup pipewire, pipewire-pulse and wireplumber. You can create home directories by running...

xdg-user-dirs-update

Continued below...

hhh · 2024-07-05 19:55:27

budgie-backgrounds is a small collection of nice wallpapers. Copy some of them from /usr/share/backgrounds/budgie/ to ~/Pictures or ~Pictures/wallpapers (create the wallpapers folder). Then edit ~/.config/labwc/autostart...

# Example autostart file

xhost +SI:localuser:root > /dev/null 2>1 &
lxpolkit  >/dev/null 2>&1 &
thunar --daemon >/dev/null 2>1 &

# Set background image.
swaybg -i ~/Pictures/high-trestle-trail.jpg >/dev/null 2>&1 &

# Configure output directives such as mode, position, scale and transform.
# Use wlr-randr to get your output names
# Example ~/.config/kanshi/config below:
#   profile {
#     output HDMI-A-1 position 1366,0
#     output eDP-1 position 0,0
#   }
#kanshi >/dev/null 2>&1 &

# Launch a panel such as yambar or waybar.
sfwbar >/dev/null 2>&1 &

# Enable notifications. Typically GNOME/KDE application notifications go
# through the org.freedesktop.Notifications D-Bus API and require a client such
# as mako to function correctly. Thunderbird is an example of this.
#mako >/dev/null 2>&1 &

# Lock screen after 5 minutes; turn off display after another 5 minutes.
#
# Note that in the context of idle system power management, it is *NOT* a good
# idea to turn off displays by 'disabling outputs' for example by
# `wlr-randr --output <whatever> --off` because this re-arranges views
# (since a837fef). Instead use a wlr-output-power-management client such as
# https://git.sr.ht/~leon_plickat/wlopm
#swayidle -w \
#	timeout 300 'swaylock -f -c 000000' \
#	timeout 600 'wlopm --off \*' \
#	resume 'wlopm --on \*' \
#	before-sleep 'swaylock -f -c 000000' >/dev/null 2>&1 &

xhost is to get gparted and other GUI apps that need root permission to run. This is not recommended on a multi-user machine, but it's the most practical way I've found to get a normal setup where everything works. I need to do more research on this.

Anyways, that's a pretty good beginning...

sudo apt install grim

You can adjust volume by right-clicking the volume icon in the panel. Right-click again to close the slider.

Lower-left is an applications menu click it to open and run your programs.

johnraff · 2024-07-06 01:08:47

^@hhh I'm going to set aside a trixie VM for the hhh Wayland session.
Many thanks!

or1o9 · 2024-07-06 07:24:17

Could a separate BL-Wayland-labwc development scrot thread be useful at this stage?

Just thought it would be easier for testers to find information, and more room for discussions about the graphics and related stuff that way.

It is still a bit early days for me. I need to read and catch up on everything about it I guess. And the hardest part will probably be to carve out some spare time to actually do it. Real life, sigh.

Anyway, a big thank you for all the work that has been done up til now, and to all of you who have got this going here!

johnraff · 2024-07-07 03:00:04

This is the big mother-thread on BunsenLabs+Wayland: https://forums.bunsenlabs.org/viewtopic.php?id=8843

We will fork off new topics from there if they get big.

unklar · 2024-07-07 09:46:31

Wow, good work!

hhh wrote:

xhost is to get gparted and other GUI apps that need root permission to run. This is not recommended on a multi-user machine, but it's the most practical way I've found to get a normal setup where everything works. I need to do more research on this.

xhost is located in the x11-server-utils package.
Whether single or multi-user system, Debian explicitly warns against using xhost.
Currently in trixie/sid and on my system

apt policy x11-utils x11-server-utils xbase-utils
x11-utils:
  Installiert:           7.7+6+b1
  Installationskandidat: 7.7+6+b1
  Versionstabelle:
 *** 7.7+6+b1 500
        500 https://deb.debian.org/debian unstable/main amd64 Packages
        100 /var/lib/dpkg/status
Notice: Paket x11-server-utils kann nicht gefunden werden.
Notice: Paket xbase-utils kann nicht gefunden werden.

As you know, I use siduction-nox as a base and siduction doas not set up sudo.
The user has to do this either with doas

~$ su
password:
# echo "permit keepenv nopass $USER" > /etc/doas.conf
# exit

or do it yourself with sudo afterwards.

# usermod -aG sudo $USER

My autostart in Labwc

# Example autostart file


# Set background color.
#swaybg -c '#113344' >/dev/null 2>&1 &
#swaybg -i -m fill '~/wallpapers/porsche_1680x1050.jpg' >/dev/null 2>&1 &
swaybg --image ~/wallpapers/labwall2-1920x1080.png --mode fill >/dev/null 2>&1 &
#swaybg --image ~/wallpapers/wUvNXIJ.png --mode fill >/dev/null 2>&1 &
#swaybg --image ~/wallpapers/uioJFFs.png --mode fill >/dev/null 2>&1 &
#swaybg --image ~/wallpapers/sEHjy7h.png --mode fill >/dev/null 2>&1 &

# Configure output directives such as mode, position, scale and transform.
# Use wlr-randr to get your output names
# Example ~/.config/kanshi/config below:
#   profile {
#     output HDMI-A-1 position 1366,0
#     output eDP-1 position 0,0
#   }
kanshi >/dev/null 2>&1 &

lxpolkit >/dev/null 2>&1 &

# Launch a panel such as yambar or waybar.
waybar >/dev/null 2>&1 &

# Enable notifications. Typically GNOME/KDE application notifications go
# through the org.freedesktop.Notifications D-Bus API and require a client such
# as mako to function correctly. Thunderbird is an example of this.
mako >/dev/null 2>&1 &

# Lock screen after 5 minutes; turn off display after another 5 minutes.
#
# Note that in the context of idle system power management, it is *NOT* a good
# idea to turn off displays by 'disabling outputs' for example by
# `wlr-randr --output <whatever> --off` because this re-arranges views
# (since a837fef). Instead use a wlr-output-power-management client such as
# https://git.sr.ht/~leon_plickat/wlopm
swayidle -w \
	timeout 600 'swaylock -f -c 000000' \
	timeout 1200 'wlopm --off \*' \
	resume 'wlopm --on \*' \
	before-sleep 'swaylock -f -c 000000' >/dev/null 2>&1 &

set $gnome-schema org.gnome.desktop.interface >/dev/null 2>&1 &

    gsettings set $gnome-schema gtk-theme 'Yeti' >/dev/null 2>&1 &
    gsettings set $gnome-schema icon-theme 'Obsidian-Gray' >/dev/null 2>&1 &
    gsettings set $gnome-schema cursor-theme 'DMZ-White' >/dev/null 2>&1 &
    gsettings set $gnome-schema font-name 'monospace' >/dev/null 2>&1 &

#conky
#sleep 2 && conky -c ~/.conky/rcmus_conkyrc10 >/dev/null 2>&1 &

applications as root, or mounting in Thunar, it requires the su PW. Voila.

============================
PS: I keep coming back to the idea of setting up labwc in carbon-wayland first and THEN adding the BL base packages...
Not, BL and then labwc. What do you think?

johnraff · 2024-07-08 06:03:34

unklar wrote:

I keep coming back to the idea of setting up labwc in carbon-wayland first and THEN adding the BL base packages...
Not, BL and then labwc. What do you think?

In what context of "carbon-wayland"?

For individual users/testers/developers/hackers this sounds to me like the right way to go, and what people round here seem to be doing right now.

The carbon-wayland branch of the netinstall script... not sure. If it just installed a base labwc system, what would be BunsenLabs Carbon about it? Maybe developers can gradually add packages and config files to it, until some day we can declare it Ready For Testing and people can start using it. It has to be out in public all the time so people can see where development is, and add their own contributions.

Maybe there could be more branches of Carbon netinstall for different development philosophies...

Anyway, the BL base packages are probably better added one at a time - checking for problems at each stage - rather than all at once. But that's something for individuals to play with, perhaps?

But I think it's a good thing to keep possible BL packages' future contributions in mind, even at the early stages. We don't want to arrive at a point when a brand new Wayland system has been created and the existing BL packages have to be forced into it.

unklar · 2024-07-09 10:18:52

So this is the 'Franken-Desktop', carbon-wayland.

https://postimg.cc/bZdyxcpL

I have just re-run the procedure with the bunsen-netinstall-script and, as you can see, the error with micko's repo persists in that it points to 'trixie' and packages cannot be obtained. A manual change does not lead to success either.

Only these packages were installed by bunsen:
bunsen-archive-keyring, bunsen-common, bunsen-os-release, bunsen-themes-base, bunsen-images-base
All other packages pull in dependencies such as lightdm; tint2; nitrogen ect, pp. which are known not to work with wayland.

micko01 · 2024-07-09 12:06:05

^@unklar I have PRs in to rectify the situation for bunsen-netinstall and bunsen-configs but at this stage it's still a bit "chicken before the egg". We'll get there

Oh, and the carbon-wayland netinstall branch should pull in my repo now as I changed the suite name a week or so ago and it is merged by @johnraff

https://github.com/BunsenLabs/bunsen-ne … ee075d5fe7

johnraff · 2024-07-10 04:16:53

unklar wrote:

I have just re-run the procedure with the bunsen-netinstall-script and, as you can see, the error with micko's repo persists in that it points to 'trixie' and packages cannot be obtained.

As Micko says below above, the netinstall script was updated about 4 days ago. Maybe a caching issue?

Only these packages were installed by bunsen:
bunsen-archive-keyring, bunsen-common, bunsen-os-release, bunsen-themes-base, bunsen-images-base
All other packages pull in dependencies such as lightdm; tint2; nitrogen ect, pp. which are known not to work with wayland.

Useful information, thanks.
I think most of the dependencies are in fact Recommends, so for now I'll check over the difficult BL packages and move them to pkgs-norecs-base.

EDIT: I've just looked, and in the netinstall "base" install, all the BL packages are installed without recommends anyway.

Last edited by johnraff (2024-07-10 06:28:28)

johnraff · 2024-07-10 06:27:33

bunsen-configs-base: Depends: none
bunsen-exit: Depends: systemd|elogind, polkitd, polkitd-pkla
bunsen-numix-icon-theme: Depends: numix-icon-theme-circle, librsvg2-common
    librsvg2-common: Depends: librsvg2-2 (= 2.54.7+dfsg-1~deb12u1), libgdk-pixbuf-2.0-0 (>= 2.23.5-2), libglib2.0-0 (>= 2.50.0)
    numix-icon-theme-circle: Depends: numix-icon-theme
        numix-icon-theme:  Depends: none
bunsen-thunar: Depends: libthunarx-3-0
    libthunarx-3-0: Depends: thunar-data, libatk1.0-0 (>= 1.12.4), libc6 (>= 2.4), libexif12 (>= 0.6.21-1~), libexo-2-0 (>= 4.17.0), libgdk-pixbuf-2.0-0 (>= 2.22.0), libglib2.0-0 (>= 2.55.2), libgtk-3-0 (>= 3.21.4), libpango-1.0-0 (>= 1.14.0), libpcre2-8-0 (>= 10.22), libx11-6, libxfce4ui-2-0 (>= 4.17.6), libxfce4util7 (>= 4.17.2), libxfconf-0-3 (>= 4.6.0)

So of the BL base packages, possibly suspicious might be bunsen-thunar because of that long list? Any of those broken on Wayland?

unklar · 2024-07-10 09:07:48

BINGO!
Thanks for the tip with the 'caching', @johnraff.
That's it

These are the currently installed packages

dpkg -l | grep bunsen
ii  bunsen-archive-keyring                2023.01.14+bl13-1                    all          BunsenLabs GnuPG archive key
ii  bunsen-common                         13.0.1-1                             all          Various shared files for BunsenLabs
ii  bunsen-docs                           13.0-1                               all          Documentation for BunsenLabs
ii  bunsen-images                         13.0-1                               all          Alternative images for use with BunsenLabs
ii  bunsen-images-base                    13.0-1                               all          Images for use with BunsenLabs
ii  bunsen-os-release                     13.0-1                               all          Controls OS and vendor identification on BunsenLabs systems
ii  bunsen-python-apt-template            13.0-1                               all          Provides a distribution template for python-apt
ii  bunsen-themes                         13.0-1                               all          GTK, Openbox, and other themes for BunsenLabs on Debian
ii  bunsen-themes-base                    13.0-1                               all          GTK, Openbox, and other themes for BunsenLabs on Debian

I am using 'unstable'. The package 'polkitd-pkla' is already deprecated here:

Die folgenden Pakete haben unerfüllte Abhängigkeiten:
 polkitd-pkla : Hängt ab von: libpolkit-gobject-1-0 (= 124-2) aber 124-3 soll installiert werden
E: Probleme können nicht korrigiert werden, Sie haben zurückgehaltene defekte Pakete.

apt policy libpolkit-gobject-1-0
libpolkit-gobject-1-0:
  Installiert:           124-3
  Installationskandidat: 124-3
  Versionstabelle:
 *** 124-3 500
        500 https://deb.debian.org/debian unstable/main amd64 Packages
        100 /var/lib/dpkg/status

Do you need the whole install.log?

johnraff · 2024-07-11 02:09:25

My impression about polkitd-pkla is that while it is deprecated it is still possible to use it, at least for now. I don't know whether support will still exist in the final Trixie though. That means we'll have to rewrite our pkla rules in the new javascript format.

Meanwhile, the dependency in Sid of polkitd-pkla on libpolkit-gobject-1-0 (= 124-2) looks like a bug, since the Sid version of libpolkit-gobject-1-0 is (mostly) 124-3. Whether the devs will fix the dependency in polkitd-pkla or just drop it, we'll have to wait and see.

EDIT I now see there's no polkitd-pkla in Trixie. Was I hallucinating that I saw it there this morning? Looks like sayonara...

Last edited by johnraff (2024-07-11 07:37:31)

micko01 · 2024-07-11 06:44:35

I believe this is the inaugural boot of carbon-wayland but it isn't quite right. (VM of course)
- missing package from trixie - polkitd-pkla
- no os-release
- had to run bl-user-setup manually

Other than that not too bad

@unklar you can try it right now if you do a trixie netinstall and get the bunsen-netinstall from my github:

wget  https://github.com/01micko/bunsen-netinstall/archive/refs/heads/carbon-13.tar.gz
# force copy pkgs-recs-wbase and pkgs-norecs-wbase over pkgs-recs-base and pkgs-norecs-base

Then comment out polkitd-pkla in pkgs-norecs-base
Run ./install as normal

@johnraff - what logs do you want so we can debug this?

any one else reading this do not try, it isn't even a developer preview yet!

You do so at own risk under the terms of the GPL

unklar · 2024-07-11 07:28:16

johnraff wrote:

My impression about polkitd-pkla is that while it is deprecated it is still possible to use it, at least for now. I don't know whether support will still exist in the final Trixie though. That means we'll have to rewrite our pkla rules in the new javascript format.
Meanwhile, the dependency in Sid of polkitd-pkla on libpolkit-gobject-1-0 (= 124-2) looks like a bug, since the Sid version of libpolkit-gobject-1-0 is (mostly) 124-3. Whether the devs will fix the dependency in polkitd-pkla or just drop it, we'll have to wait and see.

Michael Biebel wrote:

...
* Drop support for the pkla backend.
Drop the legacy polkitd-pkla package.
It is no longer maintained upstream and was only meant as a temporary
measure to ease the migration from .pkla to JS based rules files.
...

https://metadata.ftp-master.debian.org/ … _changelog

#1 2024-07-04 17:55:02

carbon-wayland

#2 2024-07-05 02:47:24

Re: carbon-wayland

#3 2024-07-05 09:58:45

Re: carbon-wayland

#4 2024-07-05 11:11:30

Re: carbon-wayland

#5 2024-07-05 13:44:47

Re: carbon-wayland

#6 2024-07-05 19:33:07

Re: carbon-wayland

#7 2024-07-05 19:55:27

Re: carbon-wayland

#8 2024-07-06 01:08:47

Re: carbon-wayland

#9 2024-07-06 07:24:17

Re: carbon-wayland

#10 2024-07-07 03:00:04

Re: carbon-wayland

#11 2024-07-07 09:46:31

Re: carbon-wayland

#12 2024-07-08 06:03:34

Re: carbon-wayland

#13 2024-07-09 10:18:52

Re: carbon-wayland

#14 2024-07-09 12:06:05

Re: carbon-wayland

#15 2024-07-10 04:16:53

Re: carbon-wayland

#16 2024-07-10 06:27:33

Re: carbon-wayland

#17 2024-07-10 09:07:48

Re: carbon-wayland

#18 2024-07-11 02:09:25

Re: carbon-wayland

#19 2024-07-11 06:44:35

Re: carbon-wayland

any one else reading this do not try, it isn't even a developer preview yet!

#20 2024-07-11 07:28:16

Re: carbon-wayland

Board footer