Christopher Snowhill
Christopher Snowhill
I'll try the override method, or at least using grep to filter the specific message. It's also a Flatpak app, so I'm not sure if filtering the flatpak binary running...
Yes, now the menu opens.
Yes, that works.
https://youtu.be/IkwUFEK-B3Y I added more. It depends on the display that's 2.0 scale being turned off and disconnecting momentarily. It also depends on Kanshi being set to scale the output to...
Cannot reproduce on sway-git and wlroots-git. Not even if I manually set sway's output to 3840x2160 scale 1.0 and load kanshi to override it like I do with labwc. On...
Step 2. I cannot reproduce it on an empty config, until I use wlr-randr to change DP-1's scale to 2.0. The default desktop layout has DP-1 to the right of...
Okay, wlr-randr setting DP-1 to scale 2.0, DP-2 ends up at 3840,0 and DP-1 ends up at 5760,0. Here's the log: [labwc.debug.stderr.log.txt](https://github.com/user-attachments/files/16975174/labwc.debug.stderr.log.txt)
With "Make bold text brighter", I get this: 
More logs: [journal.log.txt](https://github.com/bluez/bluez/files/15326704/journal.log.txt) And just the bluetooth parts: [journal.log.bluetooth.txt](https://github.com/bluez/bluez/files/15326705/journal.log.bluetooth.txt)
Yes, it does indeed appear to be ray tracing related. So whose bug is this now, Mesa's? Or still the game's for having buggy (and undocumented) ray tracing code?