| 11 Feb 2024 |
 @multisn8-idk:matrix.org | aaaah, hmmm, what are the actual pixel and physical dimensions of your internal one? | 22:28:46 |
| @multisn8-idk:matrix.org | iirc xrandr combines them all into one large screen | 22:28:57 |
 @aktaboot:tchncs.de | 2256x1504+0+0 | 22:29:10 |
| @multisn8-idk:matrix.org | alright, then one last question: how does your screen layout look like? | 22:29:29 |
| @aktaboot:tchncs.de | 
Download clipboard.png | 22:29:59 |
 @atemu12:matrix.org | aktaboot: So not 100% scaling then... | 22:31:38 |
| @aktaboot:tchncs.de | it was 100% on the screen I was using, sorry didn't double check on the other one 😅 | 22:32:26 |
| @aktaboot:tchncs.de | * it was 100% on the display I was using, sorry didn't double check on the other one 😅 | 22:32:38 |
| @multisn8-idk:matrix.org | that doesn't quite match up, interesting. 2256 * 1.5 + 1920 results in 5304, not 5136
my rough guess would be that there's weird play between wayland and xwayland going on. wayland scaling basically works such that buffers are rendered at x times the size, and iirc xwayland couldn't handle that well.
sway just ended up marking this as wontfix(TM) https://github.com/swaywm/sway/issues/5548
idk about plasma though | 22:34:00 |
| @multisn8-idk:matrix.org | i doubt this is nixos-specific though | 22:34:40 |
| @aktaboot:tchncs.de | 
Download clipboard.png | 22:35:45 |
| @aktaboot:tchncs.de | yeah, and changing with arandr/xrandr didn't help aswell | 22:36:03 |
| @multisn8-idk:matrix.org | qwq out of ideas then | 22:36:13 |
| @aktaboot:tchncs.de | np thanks a lot! :) | 22:36:42 |
| @aktaboot:tchncs.de | it's definitely not a dealbreaker but it's the first time I get this | 22:37:11 |
| @atemu12:matrix.org | After resetting scaling to 100%, did you restart the compositor? | 22:37:17 |
| @aktaboot:tchncs.de | no, I just have 150% on one display and 100% on another still. I will check with 100% on both | 22:38:13 |
| @aktaboot:tchncs.de | I can restart the KDE compostior without logging out on right ? | 22:38:47 |
| @atemu12:matrix.org | I don't think so | 22:39:22 |
| @aktaboot:tchncs.de | okay yeah just resetting both to 100% does fix the issue 🤔 | 22:41:05 |
| @aktaboot:tchncs.de | thanks Atemu | 22:42:18 |
| @aktaboot:tchncs.de | 125% is still usable though, I can stick to that for now | 22:42:52 |
| @aktaboot:tchncs.de | okay I guess this is way more a Wayland/X issue than a NixOS one | 22:44:00 |
| 12 Feb 2024 |
|  @errant404:matrix.org joined the room. | 07:26:44 |
| @errant404:matrix.org left the room. | 07:27:57 |
| @errant404:matrix.org joined the room. | 07:28:53 |
|  @bujiraso:matrix.org left the room. | 09:31:47 |
 izdihar | Hello, does anyone know why chromium based browser on nixos doesnt support webgpu? | 12:14:37 |
 K900 | It does? | 12:14:45 |
| izdihar | wait really? im using brave right now (chromium fork), already enabled chrome://flags/#enable-unsafe-webgpu and started --enable-features=Vulkan and it still not able to run https://toji.github.io/webgpu-test/ | 12:19:07 |
