| 14 Dec 2025 |
 Brisingr | No error is displayed, no other window is shown. Based on the vids I've seen, the Ubisoft Connect window is supposed to show, asking to sign in. | 11:01:37 |
 hustlerone | try running it with protontricks and sign in? | 11:08:11 |
| Brisingr | As in, run the installed Ubisoft Launcher executable using Protontricks? Tried that as well. Ubisoft Connect does not show up. Only the Protontricks window is displayed again. | 11:37:32 |
 Atemu | What if you run the installer again via protontricks? | 13:34:10 |
| Atemu | That's how I did it with TrackMania Turbo which ships an ancient Uplay that does not work. | 13:35:12 |
| Atemu | * | 13:35:27 |
 niklaskorz | do you have ntsync enabled? because that is currently incompatible with the ubisoft launcher | 13:36:35 |
| Brisingr | Will try that when I'm at my PC. | 13:39:22 |
| niklaskorz | (I'm not sure if Proton Experimental can even use ntsync yet though, I've only seen it in Proton GE and Proton CachyOS) | 13:39:35 |
| Brisingr | I'll need to check that as well. | 13:40:32 |
| niklaskorz | unrelated drivers question... is there any downside to not having mesa drivers installed globally? I occasionally see race conditions where mesa llvmpipe gets picked instead of nvidia (even at the compositor level, i.e. kwin6), which I can fix by setting some env vars (__GLX_VENDOR_LIBARY_NAME etc), then noticed that the nvidia module only adds the nvidia drivers as a hardware.graphics.extraPackages instead of setting it as hardware.graphics.package, meaning the mesa driver still gets put into /run/opengl even when nvidia drivers are enabled | 13:42:58 |
| niklaskorz | setting the nvidia driver as hardware.graphics.package instead seemingly does not break anything | 13:43:20 |
| niklaskorz | * unrelated drivers question... is there any downside to not having mesa drivers installed globally? I occasionally see race conditions where mesa llvmpipe gets picked instead of nvidia (even at the compositor level, i.e. kwin6), which I can fix by setting some env vars (__GLX_VENDOR_LIBARY_NAME etc), but I then noticed that the nvidia module only adds the nvidia drivers as a hardware.graphics.extraPackages instead of setting it as hardware.graphics.package, meaning the mesa driver still gets put into /run/opengl even when nvidia drivers are enabled | 13:43:42 |
| niklaskorz | the race condition only happens occassionally, but it's annoying having to reboot when it does | 13:44:22 |
| niklaskorz | * unrelated drivers question... is there any downside to not having mesa drivers installed globally? I occasionally see race conditions where mesa llvmpipe gets picked instead of nvidia (even at the compositor level, i.e. kwin6), which I can fix by setting some env vars (__GLX_VENDOR_LIBARY_NAME etc), but I then noticed that the nvidia module only adds the nvidia drivers as a hardware.graphics.extraPackages instead of setting it as hardware.graphics.package, meaning the mesa opengl and vulkan drivers still get put into /run/opengl even when nvidia drivers are enabled | 13:45:10 |
| niklaskorz | I've seen it happen in both mutter and kwin6 too, so it does not seem to be a compositor-specific bug | 13:48:45 |
 K900 | This should absolutely not race | 13:51:11 |
| niklaskorz | I too wish it did not 🥴 | 13:55:23 |
| K900 | As in I don't think there's ever a situation in which it will race | 13:55:57 |
| K900 | Is this a single GPU system? | 13:56:11 |
| niklaskorz | My ryzen has an integrated GPU but I've disabled the amdgpu Kernel module | 13:56:44 |
| niklaskorz | Also the issues only started occuring about a month or two ago 🤔 | 13:57:30 |
| K900 | Yeah that shouldn't matter | 13:57:34 |
| niklaskorz | But it's at least once a week now | 13:57:39 |
| K900 | Can you ping me when it does happen | 13:57:46 |
| K900 | I want to see what state your system is in | 13:57:52 |
| K900 | Because it's definitely not JUST that | 13:58:01 |
| Brisingr | The kernel module doesn't show up when greping lsmod. I assume that means it's not enabled? | 14:00:53 |
| niklaskorz | In reply to @k900:0upti.me
Can you ping me when it does happen Rebooted just now for testing and it happened again | 14:05:19 |
| K900 | OK so you're running llvmpipe right now? | 14:07:13 |
