!rGlCMuXgAhgEpdvJUz:nixos.org

NixOS KDE

226 Members
64 Servers

Load older messages


SenderMessageTime
31 May 2026
@k900:0upti.meK900 It's either dock related or whatever specific flavor of DP-over-USB it's doing 06:29:30
@k900:0upti.meK900 But seeing the three display outputs on that dock 06:29:37
@k900:0upti.meK900 There's probably an MST splitter inside or something 06:29:45
@k900:0upti.meK900This may sound stupid as all hell06:29:53
@k900:0upti.meK900 But have you tried the other DP port 06:29:59
@aktaboot:tchncs.deaktabooti think i did, lemme try again06:30:12
@aktaboot:tchncs.deaktabootyeah monitor wakes up and then sleeps06:31:08
@aktaboot:tchncs.deaktabootas it does with kscreen-doctor enable/disable06:31:40
@aktaboot:tchncs.deaktabootIg that's also even if it works when i switch tty?06:33:10
@k900:0upti.meK900 It's really weird tbh 06:33:28
@aktaboot:tchncs.deaktabootsorry, english06:33:35
@k900:0upti.meK900 It may be a kernel driver thing 06:33:37
@k900:0upti.meK900 It may also be a dock thing 06:33:44
@aktaboot:tchncs.deaktaboot

fwiw that's what i get from kwin_wayland

May 31 08:30:23 ninux kwin_wayland[2815]: Failed to open drm device
May 31 08:30:23 ninux kwin_wayland[2815]: Failed to open drm device
May 31 08:30:23 ninux kwin_wayland[2815]: Failed to open drm device
May 31 08:33:13 ninux kwin_wayland[2815]: Failed to find a working output layer configuration! Enabled layers:
May 31 08:33:13 ninux kwin_wayland[2815]: src KWin::RectF(0,0 2256x1504) -> dst KWin::Rect(0,0 2256x1504)
May 31 08:33:13 ninux kwin_wayland[2815]: Atomic modeset test failed! Permission denied
May 31 08:33:13 ninux kwin_wayland[2815]: Applying output configuration failed!
May 31 08:34:32 ninux kwin_wayland[2815]: Failed to open drm device
May 31 08:34:32 ninux kwin_wayland[2815]: Failed to open drm device
May 31 08:34:33 ninux kwin_wayland[2815]: Failed to open drm device
06:36:16
@aktaboot:tchncs.deaktabootnot too bothersome for me anw, wanted to see if its a bug that i could report :)06:36:41
@aktaboot:tchncs.deaktabootooh, could it possibly be BIOS related in any way? the last firmware update broke booting with Dock connected07:02:47
@aktaboot:tchncs.deaktaboot🤷07:03:28
@k900:0upti.meK900 Uhhh 07:07:21
@k900:0upti.meK900 I mean potentially yes 07:07:34
2 Jun 2026
@k900:0upti.meK900 https://blog.davidedmundson.co.uk/blog/596/ 15:40:15
@k900:0upti.meK900It is official now15:40:18
@k900:0upti.meK900X11 will be gone in 6.815:40:22
@elisaado:elisaado.comEli Saado I have not had to use it, at all, since I installed Asahi on my daily driver a year ago, so not bad 15:49:25
@elisaado:elisaado.comEli Saado I hope it will lift the maintenance burden for everyone involved 15:49:50
@k900:0upti.meK900 I'm not looking forward to the screaming 15:52:53
@elisaado:elisaado.comEli Saadoeveryone is free to stay on 🫴 6.7 🫴16:07:34
@elisaado:elisaado.comEli Saadocan we bet on how many KDE forks will be spawned because of this?16:07:47
@silverhadch07:matrix.orgHadi 🤒
In reply to @elisaado:elisaado.com
can we bet on how many KDE forks will be spawned because of this?
6 or 7? All of which will die after a couple of weeks.
16:50:22
@aloisw:kde.orgaloisw
In reply to @elisaado:elisaado.com
everyone is free to stay on 🫴 6.7 🫴
AlmaLinux 9 (with Plasma 5.25) was suggested by KDE at some point as the backup option.
19:17:05
3 Jun 2026
@sigmanificient:matrix.orgSigmanificient

When using pyside6 it's seems that the icon are not showing up unless i explicitely add something like

  postFixup = ''
    wrapProgram $out/bin/ilo-detection \
      --prefix QT_PLUGIN_PATH : "${qt6.qtsvg}/lib/qt-6/plugins"
  '';

to my derivation. Is this an known issue?

14:19:19

Show newer messages


Back to Room ListRoom Version: 9