Again, my intention was, to make it as painless as possible.
Adding a choice at Cala, the boot menu, and literally any other place, would lead to effort, that is needless pretty much with the very next release.
I think, that the Wayland session seems to be ready enough, to be launched by default.
It is almost as stable as a normal X11, and I consider it production-ready on my machine.
As such, I would be in favor of just shipping Wayland.
I found another issue, that I created an issue on the KDE bug tracker for.
It would be nice if you could confirm it.
Sorry again multiple ISO is not the answer.
I don’t use global menus, sorry.
Tnx for all your tests!
Probably this one. 424485 – GDbus-DBusMenu-Proxy does not work for GTK Wayland apps
Garuda XFCE all good.
bash: alias: big: not found
bash: alias: expac -H M '%m\t%n' | sort -h | nl: not found
╭─heinrichjvr@heinrich in ~ took 16ms
╰─λ garuda-inxi
System:
Kernel: 6.1.56-1-lts arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
clocksource: hpet available: acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-lts
root=UUID=95053f75-39c5-43f2-9db8-a2578c596882 rw rootflags=subvol=@
quiet resume=UUID=d680700b-6c3e-4d5d-a1b6-5dd904431dd3 loglevel=3 ibt=off
Desktop: Xfce v: 4.18.1 tk: Gtk v: 3.24.36 info: xfce4-panel wm: xfwm
v: 4.18.0 vt: 7 dm: LightDM v: 1.32.0 Distro: Garuda Linux base: Arch Linux
Machine:
Type: Desktop Mobo: Micro-Star model: B450 TOMAHAWK (MS-7C02) v: 1.0
serial: <superuser required> UEFI: American Megatrends LLC. v: 1.J1
date: 05/06/2023
CPU:
Info: model: AMD Ryzen 3 2200G with Radeon Vega Graphics bits: 64 type: MCP
arch: Zen level: v3 note: check built: 2017-19 process: GF 14nm
family: 0x17 (23) model-id: 0x11 (17) stepping: 0 microcode: 0x8101016
Topology: cpus: 1x cores: 4 smt: <unsupported> cache: L1: 384 KiB
desc: d-4x32 KiB; i-4x64 KiB L2: 2 MiB desc: 4x512 KiB L3: 4 MiB
desc: 1x4 MiB
Speed (MHz): avg: 3500 min/max: 1600/3500 boost: disabled scaling:
driver: acpi-cpufreq governor: performance cores: 1: 3500 2: 3500 3: 3500
4: 3500 bogomips: 27956
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: AMD Ellesmere [Radeon RX 470/480/570/570X/580/580X/590]
vendor: ASUSTeK driver: amdgpu v: kernel arch: GCN-4 code: Arctic Islands
process: GF 14nm built: 2016-20 pcie: gen: 3 speed: 8 GT/s lanes: 8
link-max: lanes: 16 ports: active: DVI-D-1 empty: DP-1,DVI-D-2,HDMI-A-1
bus-ID: 10:00.0 chip-ID: 1002:67df class-ID: 0300 temp: 34.0 C
Display: x11 server: X.Org v: 21.1.8 compositor: xfwm v: 4.18.0 driver: X:
loaded: amdgpu unloaded: modesetting alternate: fbdev,vesa dri: radeonsi
gpu: amdgpu display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 1600x900 s-dpi: 96 s-size: 423x238mm (16.65x9.37")
s-diag: 485mm (19.11")
Monitor-1: DVI-D-1 mapped: DVI-D-0 model: Samsung SyncMaster
serial: <filter> built: 2009 res: 1600x900 hz: 60 dpi: 92 gamma: 1.2
size: 443x250mm (17.44x9.84") diag: 509mm (20") ratio: 16:9 modes:
max: 1600x900 min: 720x400
API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
device: 1 drv: swrast gbm: drv: kms_swrast surfaceless: drv: radeonsi x11:
drv: radeonsi inactive: wayland
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 23.2.1-arch1.2
glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 570 Series (polaris10
LLVM 16.0.6 DRM 3.49 6.1.56-1-lts) device-ID: 1002:67df memory: 3.91 GiB
unified: no
API: Vulkan v: 1.3.264 layers: 5 device: 0 type: discrete-gpu name: AMD
Radeon RX 570 Series (RADV POLARIS10) driver: mesa radv v: 23.2.1-arch1.2
device-ID: 1002:67df surfaces: xcb,xlib device: 1 type: cpu name: llvmpipe
(LLVM 16.0.6 256 bits) driver: mesa llvmpipe v: 23.2.1-arch1.2 (LLVM
16.0.6) device-ID: 10005:0000 surfaces: xcb,xlib
Audio:
Device-1: AMD Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590]
vendor: ASUSTeK driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s
lanes: 8 link-max: lanes: 16 bus-ID: 10:00.1 chip-ID: 1002:aaf0
class-ID: 0403
Device-2: AMD Family 17h/19h HD Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
bus-ID: 30:00.6 chip-ID: 1022:15e3 class-ID: 0403
API: ALSA v: k6.1.56-1-lts status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: PipeWire v: 0.3.80 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
Message: No PCI device data found.
Drives:
Local Storage: total: 4.78 TiB used: 9.13 GiB (0.2%)
SMART Message: Required tool smartctl not installed. Check --recommends
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Mushkin model: MKNSSDHL250GB-D8
size: 232.89 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: S1111A0L temp: 37.9 C
scheme: GPT
ID-2: /dev/sda maj-min: 8:0 vendor: Western Digital
model: WD50NDZW-11BCSS0 size: 4.55 TiB block-size: physical: 4096 B
logical: 512 B type: USB rev: 3.2 spd: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1
tech: HDD rpm: 4800 serial: <filter> fw-rev: 1034 scheme: GPT
Partition:
ID-1: / raw-size: 223.79 GiB size: 223.79 GiB (100.00%)
used: 9.13 GiB (4.1%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 576 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 223.79 GiB size: 223.79 GiB (100.00%)
used: 9.13 GiB (4.1%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-4: /var/log raw-size: 223.79 GiB size: 223.79 GiB (100.00%)
used: 9.13 GiB (4.1%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-5: /var/tmp raw-size: 223.79 GiB size: 223.79 GiB (100.00%)
used: 9.13 GiB (4.1%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 7.68 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 4 dev: /dev/zram0
ID-2: swap-2 type: partition size: 8.8 GiB used: 0 KiB (0.0%) priority: -2
dev: /dev/nvme0n1p3 maj-min: 259:3
Sensors:
System Temperatures: cpu: 31.1 C mobo: N/A gpu: amdgpu temp: 35.0 C
Fan Speeds (rpm): N/A gpu: amdgpu fan: 3
Info:
Processes: 266 Uptime: 0m wakeups: 0 Memory: total: 8 GiB
available: 7.68 GiB used: 1.19 GiB (15.5%) Init: systemd v: 254
default: graphical tool: systemctl Compilers: gcc: 13.2.1 clang: 16.0.6
Packages: pm: pacman pkgs: 1543 libs: 503
tools: gnome-software,octopi,pamac,paru Shell: Bash v: 5.1.16
running-in: xfce4-terminal inxi: 3.3.30
Garuda (2.6.17-1):
System install date: 2023-10-06
Last full system update: 2023-10-07
Is partially upgraded: No
Relevant software: snapper NetworkManager dracut
Windows dual boot: No/Undetected
Failed units: systemd-vconsole-setup.service
╭─heinrichjvr@heinrich in ~ took 1s
╰─λ
I’m still getting the failed vconsole setup during boot.
What do you have in /etc/vconsole.conf on the KEYMAP= line?
I think we may need to check the way we are populating this file, because it seems to take whatever keymap the user inputs in Calamares (even if it is not in /usr/share/kbd/consolefonts).
Until we fix that, you can do it yourself by changing or removing that line in /etc/vconsole.conf. See this thread for example: Garuda Sway - Failed units: systemd-vconsole-setup.service
I get this error 4 times during boot.
I have:
FONT=ter-220n
KEYMAP=au
I did try changing KEYMAP to “us” and “UK” at one point but it did nothing.
I just deleted the KEYMAP=au line completely, but the error still persists. Only this time it shows the error 3 times instead of 4.
It started showing up since the 202305 iso
Which Desktop Environment?
That does not match ISO timestamp naming convention. Oct 5th?
Sorry, the May ISO 2305.
I use KDE Dr460nized.
Still an issue with the current September and October ISO’s.
230929, 231005,6 and 7
You may need to regenerate the initramfs after changing this file.
sudo dracut-rebuild
Ahhh what a noob. It’s gone after rebuilding.
Thank you.
Nope. As you can see in my video, that I posted together with my bug report, does this happen in Kate.
For Firedragon, I have no Global Menu at all.
And that counts for both X11 and Wayland.
Unfortunately it seems you are part of the people with various Wayland irritants. The good news is none of the showstoppers seem to affect you Plasma/Wayland Showstoppers - KDE Community Wiki
As far as I believe, X11 packages will still be part of Garuda when Plasma 6 gets out, as long it won’t start causing too many showstoppers.
Yes that’s a known issue Firedragon not showing the top Menu Bar options
Plasma 6 will introduce a couple of new bugs, obviously.
Then, regressions of some features will happen, and the switch to Wayland could potentially cause quite a couple of bugs, which only happen on rare combinations of hard and software.
So they happen to be hard to find and debug.
Another interesting topic could be NVK:
All these technologies come with the same kind of trade-off:
The modern, progressive, and arguably more ‘Arch-way’ approach to things.
Plus the established, more stable way of things.
I wonder how many people are aware of the implications the individual decisions.
What do you guys think about an ISO, that is only for development purposes, and is only accessible through threads like this?
I imagine an early Plasma 6 ISO, as an example. So we could test on real hardware today more easily.
I guess you guys might already have such experimental ISOs ready?
Correct or almost, kde-git is still under construction but we do have in mind to make it an ISO. I’m the one who keeps saying “Is it there yet? Is it there ye? Is it there yet?” 
You’re right, just had time to retest this.
Well doesn’t matter, it’ll stay that way until Plasma 6, at least the option to super easily switch between both is there and accessible to anyone.
It’s getting a little complicated here.
As already written, the results are to be communicated with the respective DE’s and requests should be made under Requests
Not all developers/maintainers are permanently active in the forum and read all posts here.
I therefore close here.
If necessary, posts can be moved accordingly.