!rGlCMuXgAhgEpdvJUz:nixos.org

NixOS KDE

206 Members
57 Servers

Load older messages

SenderMessageTime
8 Apr 2025
@shapr:cofree.coffeeshapr
In reply to @mjm:midna.dev
and supported multiple displays
I'm using KDE because it does a great job of setting up my two external monitors when I plugin my laptop. 		17:47:55
@shapr:cofree.coffeeshaprI previously used and loved xmonad, but had a shell script I ran when I plugged my laptop into my thunderbolt dock.17:49:32
@shapr:cofree.coffeeshaprGnome did the right thing most of the time, but KDE has always done the right thing for the past year.17:50:04
@shapr:cofree.coffeeshaprI have a third question, why do I have xwaylandbridge running by default? I'm mostly sure I switched entirely to wayland last month.17:50:46
@shapr:cofree.coffeeshaprI can't share my screen in jitsi unless I explicitly stop xwaylandbridge, no idea why.17:51:06
@k900:0upti.meK900 ⚡️That sounds extremely wrong17:51:17
@k900:0upti.meK900 ⚡️Is jitsi running under xwayland?17:51:21
@k900:0upti.meK900 ⚡️If it's running xwayland, it needs to use the bridge17:51:29
@k900:0upti.meK900 ⚡️If it's native wayland, it should not care about the bridge17:51:36
@shapr:cofree.coffeeshaprJitsi runs in firefox17:54:29
@k900:0upti.meK900 ⚡️Firefox should be native Wayland and should not care about the bridge17:54:42
@k900:0upti.meK900 ⚡️Do you have Pipewire running?17:54:50
@shapr:cofree.coffeeshaprYes17:54:57
@shapr:cofree.coffeeshapr I do see Xwayland from ps ux|grep X 17:56:41
@shapr:cofree.coffeeshaprI couldn't find any docs describing how to tell if I'm on "native Wayland" without X11 at all.17:57:13
@k900:0upti.meK900 ⚡️That's not a thing17:57:42
@k900:0upti.meK900 ⚡️xwayland will ~always exist17:57:47
@shapr:cofree.coffeeshaprOk, good to know.17:58:50
@shapr:cofree.coffeeshaprAnyway, I've been having fun installing all the kdePackages and trying them out, KSystemLog is the only one that's behaved strangely so far.18:01:43
@shapr:cofree.coffeeshaprIf anyone has a nifty KDE package they suggest I try out, I'd love to hear about it.19:12:16
9 Apr 2025
@eliasp:kde.orgeliasp anyone running NixOS/Plasma6 on a Raspberry Pi 4B? the desktop performance is extremely sluggish, there are rendering artifacts when moving windows, etc.
Armbian runs quite nicely... 		08:05:27
@k900:0upti.meK900 ⚡️Mainline or vendor kernel? How much CMA? Mesa enabled? 08:09:51
@k900:0upti.meK900 ⚡️Oh yeah, UEFI or uboot? If UEFI, ACPI or DT? 08:13:34
@eliasp:kde.orgeliasp

using the raspberry-pi-4 module from nixos-hardware - all other hardware customizations are only related to enabling fkms-3d and fixing 802.11/bluetooth, so:

  • Kernel: pkgs.linuxKernel.packages.linux_rpi4
  • CMA: 512
  • uboot
  • Mesa is enabled

kinfo output:

Operating System: NixOS 25.05
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.12.0
Qt Version: 6.8.2
Kernel Version: 6.6.51 (64-bit)
Graphics Platform: Wayland
Processors: 4 × ARM Cortex-A72
Memory: 7.6 GiB of RAM
Graphics Processor 1: V3D 4.2.14.0
Graphics Processor 2: llvmpipe
Product Name: Raspberry Pi 4 Model B Rev 1.4�
U-Boot Version: 2025.01�
08:35:10
@eliasp:kde.orgeliasp

…and Alt+TAB crashes the kwin wayland compositor 😬

Apr 09 11:08:13 moria-rpi4 kwin_wayland_wrapper[6714]: DRM_IOCTL_MODE_CREATE_DUMB failed: Cannot allocate memory
Apr 09 11:08:13 moria-rpi4 kwin_wayland_wrapper[6714]: Failed to create scanout resource
Apr 09 11:08:13 moria-rpi4 kwin_wayland_wrapper[6714]: DRM_IOCTL_MODE_CREATE_DUMB failed: Cannot allocate memory
Apr 09 11:08:13 moria-rpi4 kwin_wayland_wrapper[6714]: Failed to create scanout resource
Apr 09 11:08:13 moria-rpi4 kwin_wayland_wrapper[6714]: DRM_IOCTL_MODE_CREATE_DUMB failed: Cannot allocate memory
Apr 09 11:08:13 moria-rpi4 kwin_wayland_wrapper[6714]: Failed to create scanout resource
Apr 09 11:08:13 moria-rpi4 kwin_wayland_wrapper[6714]: DRM_IOCTL_MODE_CREATE_DUMB failed: Cannot allocate memory
Apr 09 11:08:13 moria-rpi4 kwin_wayland_wrapper[6714]: Failed to create scanout resource
Apr 09 11:08:13 moria-rpi4 kwin_wayland_wrapper[6714]: KCrash: Application '.kwin_wayland-wrapped' crashing... crashRecursionCounter = 2
Apr 09 11:08:13 moria-rpi4 kwin_wayland[6714]: QRhiGles2: Failed to make context current. Expect bad things to happen.
Apr 09 11:08:13 moria-rpi4 kwin_wayland[6714]: Failed to create RHI (backend 2)
Apr 09 11:08:13 moria-rpi4 kwin_wayland[6714]: Failed to initialize graphics backend for OpenGL.
Apr 09 11:08:13 moria-rpi4 plasmashell[6727]: QQmlVMEMetaObject: Internal error - attempted to evaluate a function in an invalid context
Apr 09 11:08:13 moria-rpi4 plasmashell[6727]: file:///nix/store/5ffb7vi05bd0q774fmd5h0vmlpyj25hp-plasma-desktop-6.3.4/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/main.qml:240: TypeError: Property 'modelIndex' of object Task_QMLTYPE_624(0x3011c00) is not a function
09:11:49
@eliasp:kde.orgeliasp I might temporarily switch to 24.11 to see whether this changes anything 09:50:35
@k900:0upti.meK900 ⚡️ Yeah don't do any of that 10:47:34
@k900:0upti.meK900 ⚡️Just run mainline10:47:36
@k900:0upti.meK900 ⚡️ With cma=256M or cma=512M on the command line 10:47:44
@k900:0upti.meK900 ⚡️ And linuxPackages_latest 10:47:53

Show newer messages

Back to Room ListRoom Version: 9