!rGlCMuXgAhgEpdvJUz:nixos.org

NixOS KDE

213 Members
57 Servers

Load older messages


SenderMessageTime
8 Nov 2024
@k900:0upti.meK900Let's see18:37:45
@aidalgol:matrix.orgaidalgol Since updating my system config to rev 18536bf04cd71abd345f9579158841376fdd0c5a (I'm following the nixos-unstable channel), the Plasma crash reporter always says it failed to submit a report. 20:18:12
@k900:0upti.meK900Should be fixed on master20:28:57
9 Nov 2024
@k900:0upti.meK900image.png
Download image.png
09:45:51
@k900:0upti.meK900omg want09:45:52
@k900:0upti.meK900
Fixed a strange issue that would make GTK 4 apps look too dark when using HDR mode. Now they're a bit too light, but this is a GTK 4 bug. (Xaver Hugl, 6.2.4. Link)
09:49:32
@k900:0upti.meK900lol09:49:33
@aktaboot:tchncs.deaktabootprinters? in this economy?09:57:53
@k900:0upti.meK900Unfortunately10:00:33
10 Nov 2024
@eliasp:kde.orgeliasp

I'm on current unstable and it seems, no Plasma user units at all are linked into the current environment...
They're all present in the store, but none of them are present in /etc/systemd/user, none of them are shown in "systemctl --user list-units 'plasma'" ...
This also means, logging in via sddm results in nothing except of a hanging sddm.
Didn't do any changes to my config, just updated my flake inputs (and unfortunately, due to lack of space, deleted old generations...).

Anyone else noticed something similar?

14:15:16
@eliasp:kde.orgeliasp Will revert my flake now manually back to unstable as of 2024-11-02, which I know was my last working generation...
But I'm curious what's going on here!
14:16:40
@k900:0upti.meK900
In reply to@eliasp:kde.org

I'm on current unstable and it seems, no Plasma user units at all are linked into the current environment...
They're all present in the store, but none of them are present in /etc/systemd/user, none of them are shown in "systemctl --user list-units 'plasma'" ...
This also means, logging in via sddm results in nothing except of a hanging sddm.
Didn't do any changes to my config, just updated my flake inputs (and unfortunately, due to lack of space, deleted old generations...).

Anyone else noticed something similar?

That sounds very wrong
14:25:09
@eliasp:kde.orgeliaspDon't have much available time left right now, but I'll try to investigate further/bisect later today...14:27:06
@k900:0upti.meK900
In reply to@eliasp:kde.org

I'm on current unstable and it seems, no Plasma user units at all are linked into the current environment...
They're all present in the store, but none of them are present in /etc/systemd/user, none of them are shown in "systemctl --user list-units 'plasma'" ...
This also means, logging in via sddm results in nothing except of a hanging sddm.
Didn't do any changes to my config, just updated my flake inputs (and unfortunately, due to lack of space, deleted old generations...).

Anyone else noticed something similar?

Oh wait, that's fine
14:36:12
@k900:0upti.meK900They're in /run/current-system/sw/share/systemd/user14:36:20
@eliasp:kde.orgeliasp Oh, you're right. They're there - so I'll have to figure out what else causes my user-session being unable to "see" those units. 14:51:42
@eliasp:kde.orgeliasp But it looks like I've broken something locally/within my user config...
Reverted back to an old flake.lock from my backup and the result is still the same 😜
14:53:21
@eliasp:kde.orgeliasp Hmm, but other local users (that haven't been active for a few weeks) on the same device experience the same issue...
I feel like hunting ghosts
14:54:50
@mjm:midna.devmjmmaybe you have something in your home directory that’s overriding those global ones?14:58:08
@mjm:midna.devmjmyou might if you messed around with systemctl enable/disable14:58:31
@eliasp:kde.orgeliaspThat's why I just also checked with other users...14:58:40
@mjm:midna.devmjmOh I misread that part sorry14:59:46
@eliasp:kde.orgeliaspmust be something stupid on my part... Will have to re-check my flake/flake.lock etc15:00:29
@k900:0upti.meK900 Something unsetting/not setting XDGDATADIRS? 15:02:50
@eliasp:kde.orgeliaspThe last change I did to my config before I saw this breakage, was to customize a user slice, but since I reverted that change I can't imagine where this would've caused a persistent change affecting even users that didn't have a session while this change was active...15:10:07
@eliasp:kde.orgeliaspXDG_DATA_DIRS looks good in an affected session15:11:47
@eliasp:kde.orgeliasp

Oh: displays manager's journal tells me, it starts xserver-wrapper, even though I've selected the Wayland session...
Maybe something wrong within sddm...? Does it persist anything?

Will have to check later... Have to run now

15:14:53
@eliasp:kde.orgeliaspsddm's state.conf looks good...15:15:34
@k900:0upti.meK900SDDM runs X by default15:17:29
@k900:0upti.meK900For the greeter itself15:17:47

Show newer messages


Back to Room ListRoom Version: 9