!rGlCMuXgAhgEpdvJUz:nixos.org

NixOS KDE

186 Members
54 Servers

Load older messages


SenderMessageTime
22 Aug 2025
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)lol08:46:16
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)have fun08:46:19
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)this sounds exciting08:46:22
@k900:0upti.meK900I'll just delete the bits that are broken and not touch anything else08:46:39
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)anyways, my config evals again (i just disabled that shit), now time to build on current staging-next08:49:13
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)i'll also need to start porting some stuff to qt6... Opensnitch has a new release with qt6 support, and krita technically already supports qt6, we just don't build it that way08:55:46
@emilazy:matrix.orgemilyI see you guys have been having fun10:53:17
23 Aug 2025
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)

Hey uh, i need the eldritch knowledge of Qt people:
https://github.com/NixOS/nixpkgs/pull/434327#issuecomment-3216591422

This backport is weird - freecad is built against qt6 on master and works just fine on wayland, but on this backport PR, it gets stuck and never actually opens the freecad window (the loading screen works fine, but after that closes it gets stuck on a bunch of ppoll calls and never progresses). Any idea why 25.05 qt6 wayland might behave that way?

09:09:53
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all) *

Hey uh, i need the eldritch knowledge of Qt people:
https://github.com/NixOS/nixpkgs/pull/434327#issuecomment-3216591422

This backport is weird - freecad is built against qt6 on master and works just fine on wayland, but on this backport PR, it (freecad-qt6) gets stuck and never actually opens the freecad window (the loading screen works fine, but after that closes it gets stuck on a bunch of ppoll calls and never progresses). Any idea why 25.05 qt6 wayland might behave that way?

09:10:10
@k900:0upti.meK900Uhh09:12:23
@k900:0upti.meK900Our Qt versions are identical at least09:12:31
@k900:0upti.meK900 Try running it with QTLOGGINGRULES=qt.qpa.*=true 09:12:40
@k900:0upti.meK900 Try running it with QT_LOGGING_RULES=qt.qpa.*=true 09:12:45
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)
(qt.qpa.wayland) EGL not available
QOpenGLWidget is not supported on this platform.
QRhiGles2: Failed to create temporary context
QRhiGles2: Failed to create context
Failed to create QRhi for QBackingStoreRhiSupport
QOpenGLWidget: Failed to create context

huh

09:13:51
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)how does the one on master work and this explodes?09:14:02
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all) like, egl should be available 09:14:21
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all) like, the version on master just succeeds, no log messages or anyhting 09:15:20
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)do i need to explicitly add qtwayland or something?09:16:15
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)no, thats there already, what09:16:47
@k900:0upti.meK900Uhhh09:37:24
@k900:0upti.meK900Driver mismatch?09:37:31
@k900:0upti.meK900I don't remember the state of Mesa split on 25.0509:37:37
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)maybe? So you are telling me i need a 25.05 VM to test this backport?09:40:31
@k900:0upti.meK900OK no our Mesa should be split09:41:47
@k900:0upti.meK900On 25.0509:41:49
@k900:0upti.meK900Can you try running eglinfo from 25.05?09:41:57
@grimmauld:grapevine.grimmauld.deGrimmauld (any/all)i don't have a 25.05 machine around09:42:11
@k900:0upti.meK900Well you have a 25.05 nixpkgs09:42:27
@k900:0upti.meK900Presumably09:42:28
@k900:0upti.meK900I mean run it on the same setup you're running this on09:42:40

Show newer messages


Back to Room ListRoom Version: 9