!rGlCMuXgAhgEpdvJUz:nixos.org

NixOS KDE

203 Members
57 Servers

Load older messages


SenderMessageTime
24 Mar 2025
@emilazy:matrix.orgemily why does gst-plugins-bad have to be like that 17:51:28
@k900:0upti.meK900Like what?17:52:35
@emilazy:matrix.orgemily depending on something called wildmidi that includes a bunch of instrument patches freepats that nothing else on the ISO uses 17:54:29
@emilazy:matrix.orgemilythat kind of thing.17:55:43
25 Mar 2025
@aidalgol:matrix.orgaidalgolAm I just losing my mind, or did Plasma previously have a section in System Settings where you could selectively disable background services?21:20:38
@sigmasquadron:matrix.orgSigmaSquadron
In reply to @aidalgol:matrix.org
Am I just losing my mind, or did Plasma previously have a section in System Settings where you could selectively disable background services?
I'm so happy that someone else remembers that page
21:31:19
@sigmasquadron:matrix.orgSigmaSquadronNo idea what happened to it; at some point between Plasma 6.1 and 6.2 it just disappeared from my settings.21:31:50
@fliegendewurst:matrix.orgFliegendeWurst try kcmshell6 kcm_kded 22:27:45
@fliegendewurst:matrix.orgFliegendeWurstI can also still find the page via the kickoff search22:28:35
26 Mar 2025
@k900:0upti.meK900Intentionally hidden upstream 01:46:33
@k900:0upti.meK900As it's not intended to be user facing 01:46:45
@k900:0upti.meK900Which is to say You Should Not Fuck With It 01:46:56
@raboof:matrix.orgraboof left the room.02:18:10
@k900:0upti.meK900Qt 6.9 is hopefully next week10:13:27
@k900:0upti.meK900It should line up with the staging cycles roughly10:13:36
@k900:0upti.meK900The question is do we go for it this close to freeze10:14:14
@k900:0upti.meK900I think yes10:14:23
@k900:0upti.meK900But if they delay again 10:15:35
@k900:0upti.meK900Then we're not going to have a good time 10:15:44
@marie:marie.cologneMarie joined the room.12:16:08
@ilya-fedin:matrix.orgπ™Όπš›. π™±πš˜πš πš•πšŽπš› πš π™·πšŠπšI was asking about it when I wanted to disable kde-gtk-settings due to going from normal scaling to dpi scaling (Qt's upstream unwillingness to rework font rendering doesn't really leave any other option to my eyes) and the answer was it's to prevent uneducated users from ruinng their systems when they try to make the system more lightweight14:40:17
@ilya-fedin:matrix.orgπ™Όπš›. π™±πš˜πš πš•πšŽπš› πš π™·πšŠπš* I was asking about it when I wanted to disable kde-gtk-settings due to going from normal scaling to dpi scaling (Qt's upstream unwillingness to rework font rendering doesn't really leave any other option to my eyes) and the answer was it's to prevent uneducated users from ruining their systems when they try to make the system more lightweight14:41:36
@ilya-fedin:matrix.orgπ™Όπš›. π™±πš˜πš πš•πšŽπš› πš π™·πšŠπši'd expect build failures and QThread-related crashes14:42:17
@ilya-fedin:matrix.orgπ™Όπš›. π™±πš˜πš πš•πšŽπš› πš π™·πšŠπšBut if you want, you can still do it via configs14:50:53
@ilya-fedin:matrix.orgπ™Όπš›. π™±πš˜πš πš•πšŽπš› πš π™·πšŠπšI don't remember exactly which config it is though, as the machine where I was doing this is broken14:51:38
@k900:0upti.meK900 Well KDE folks at least run 6.9 betas in CI 15:34:21
@ilya-fedin:matrix.orgπ™Όπš›. π™±πš˜πš πš•πšŽπš› πš π™·πšŠπšhttps://lists.qt-project.org/pipermail/development/2025-March/046250.html15:35:15
@ilya-fedin:matrix.orgπ™Όπš›. π™±πš˜πš πš•πšŽπš› πš π™·πšŠπš

[17:07:52] <jaheikki3_> Qt 6.9.0 release blocker list is empty and Qt 6.9.0 release content is frozen
[17:08:03] <jaheikki3_> Release package creation is ongoing
[17:08:06] <thiago> sorry, I found one yesterday
[17:08:18] <jaheikki3_> thiago: ID?
[17:08:22] <thiago> the qthread changes ended up with a no-op
[17:08:51] <thiago> https://codereview.qt-project.org/c/qt/qtbase/+/634258
[17:09:25] <thiago> the task itself was reported as a memory leak, but a) the leak can't be fixed in the library and b) it was a symptom that led me to find the real issue
[17:11:10] <jaheikki3_> and this is really must have for Qt 6.9.0? Because re-creating packages at this point causes a risk for the release schedule...
[17:11:24] <jaheikki3_> vohi[M]: any opinion?
[17:11:29] <thiago> I would prefer
[17:11:42] <thiago> because we're leaking the main thread QAdoptedThread, so we'll get a bunch of bug reports about that
[17:11:54] <thiago> more importantly, the fix may introduce issues and I'd rather people see them in .0 than in 6.9.1
[17:12:39] <vohi[M]> yeah, would be nice to get this in; autotests should catch if this breaks something, I think
[17:12:51] <vohi[M]> thiago: move the change to 6.9.0 and pick it to dev
[17:13:34] <jaheikki3_> yeah, that way we can speed up the progress.
[17:14:18] <thiago> I can do that
[17:14:20] <thiago> moving all three changes
[17:15:28] <jaheikki3_> Ok, so let's take that still in. Hoping CI behaves and we can get packages for testing tomorrow
[17:15:51] <jaheikki3_> vohi[M]: please review changes and I'll stage those in after approval

15:35:35
@ilya-fedin:matrix.orgπ™Όπš›. π™±πš˜πš πš•πšŽπš› πš π™·πšŠπšGNOME nixpkgs PRs seem to get open early at beta releases of gtk and other components15:40:05
@k900:0upti.meK900Yeah I tried building 6.9 locally and it was fine16:33:45

Show newer messages


Back to Room ListRoom Version: 9