#asahi · 2023-06-06 15:04
mkurzI am using wayland also#asahi · 2023-06-06 15:02
mkurzIf is set always on an apply that the screen switches to night color. Using macbook pro 14" with the pro cpu#asahi · 2023-06-06 15:02
mkurzSystem Settings - Display and Monitor - Night color#asahi · 2023-06-06 15:01
mkurzkde settings#asahi · 2023-06-06 15:00
mkurzmps: night color works forme#asahi · 2023-06-06 14:55
mkurzUsing Firefox and chromium: Is it just me or is https://www.google.com/maps a bit laggy? https://earth.google.com/web on the other handy is very very responsive and works great. Is it possible google maps not using webgl?#asahi · 2023-05-26 07:32
mkurzpatwid: I am not using the AUR package, but just download IntelliJ from the Jetbrains website#asahi · 2023-05-26 07:31
mkurzpatwid: If you run the edge kernel + edge mesa also take a look at this comment https://github.com/AsahiLinux/linux/issues/73#issuecomment-1344680802 you need to add some flags so everything runs smooth#asahi · 2023-05-26 07:30
mkurzpatwid: I am running Intellij since around Summer last year already, no problem. The 2022.3 release finally officially added arch64 support as well, see "Other": https://www.jetbrains.com/idea/whatsnew/2022-3/#page__content-other#asahi · 2023-05-17 15:39
mkurzdylanchapell: thanks, for the links, I am on the edge kernel. I did suspend my machine yesterday, so that's probably the reason. At least there is a workaround. Thanks!#asahi · 2023-05-12 19:00
mkurzFor chromium I am able to use "chromium --force-device-scale-factor=1" but it looks blurry#asahi · 2023-05-12 18:47
mkurzSo chromium 113 is broken if screen is scaled up more than 100% on wayland (using --ozone-platform-hint=auto or wayland), just in case someone else is bumping into that...#asahi · 2023-05-12 18:45
mkurzAlso another patch was necessary: https://chromium-review.googlesource.com/c/chromium/src/+/4370087#asahi · 2023-05-12 18:45
mkurzHowever it's fixed only in chromiuim 114...#asahi · 2023-05-12 18:44
mkurzAnd then landed it again after fixing it: https://chromium-review.googlesource.com/c/chromium/src/+/4370091#asahi · 2023-05-12 18:44
mkurzSo they reverted it: https://chromium-review.googlesource.com/c/chromium/src/+/4400980#asahi · 2023-05-12 18:44
mkurzTurns out the fractional scale patch was broken: https://chromium-review.googlesource.com/c/chromium/src/+/4322839?tab=comments#asahi · 2023-05-12 15:40
mkurzwaldi: yes#asahi · 2023-05-12 14:55
mkurzok, seems like I am not the only one: https://www.reddit.com/r/kde/comments/136wxuk/chrome_version_113_scaling_issue_under_wayland/#asahi · 2023-05-12 14:54
mkurznever had this problem before#asahi · 2023-05-12 14:54
mkurzLike scaling is totally of#asahi · 2023-05-12 14:52
mkurzsomeone experienced that?#asahi · 2023-05-12 14:52
mkurzI upgraded chromium to version 113 and after restarting the whole system the windows are totally zoomed in, like huge#asahi · 2023-05-05 11:32
mkurzThanks for the explanation!#asahi · 2023-05-05 07:07
mkurzSeems like WebGPU isn't currently supported on Linux anyway: https://twitter.com/Tojiro/status/1653509459602452481#asahi · 2023-05-03 22:29
mkurzI am totally ignorant, but will mesa and/or the asahi linux gpu kernel driver support WebGPU which just shipped in Chromium? Or does it already? Or how likely will it in future? Thanks, just curious.#asahi · 2023-04-07 20:45
mkurzas400: using chromium 111 I wasn't able to make it work but never tried the --use-gl=egl flag#asahi · 2023-04-07 20:06
mkurzas400: I think it's called blocklist now not blacklist see chrome://flags/#ignore-gpu-blocklist#asahi · 2023-04-07 17:23
mkurzas400: ok, however which flags/configs do you use for chromium 111?#asahi · 2023-04-07 15:20
mkurzas400: Did you use any flags to start chromium?#asahi · 2023-04-07 15:19
mkurzas400: Was it working in 111?#asahi · 2023-03-29 10:21
mkurzLike now I am unable to even run https://webglsamples.org/aquarium/aquarium.html which was working perfectly in xorg before in chromium#asahi · 2023-03-29 10:19
mkurzSo I am wondering if there are some other flags necessary#asahi · 2023-03-29 10:18
mkurzbut not gpu accel.#asahi · 2023-03-29 10:18
mkurzso in chrome://version/ I have now: Command Line: /usr/lib/chromium/chromium --flag-switches-begin --ozone-platform-hint=auto --flag-switches-end --ozone-platform=wayland#asahi · 2023-03-29 10:17
mkurzwaldi: yeah that's what I did#asahi · 2023-03-29 10:11
mkurzLike which flags or env vars to set#asahi · 2023-03-29 10:11
mkurzWould be nice to know konw what the best practice is to run chromium on Asahi (using the edge kernel). Also I am not sure what best practice is to run firefox...#asahi · 2023-03-29 10:10
mkurzTaken from https://wiki.archlinux.org/title/chromium#Force_GPU_acceleration#asahi · 2023-03-29 10:09
mkurzDoes anyone run chromium? If so, which flags do you use? Having `--ozone-platform-hint=auto` now disabled gpu acceleration in chrome://gpu/. Tried to pass things like --ignore-gpu-blocklist --enable-gpu-rasterization --enable-zero-copy --disable-gpu-driver-bug-workarounds but nothing helps.#asahi · 2023-03-29 09:54
mkurzBecause I was switching from xorg... I wasn't using these flags#asahi · 2023-03-29 09:53
mkurzWait, is it possible this happens because I was not using "--ozone-platform-hint=auto" and also not "--ozone-platform=wayland"?#asahi · 2023-03-29 09:36
mkurz"Mär 29 09:12:32 mkurz-macbook-pro krunner[607199]: [607199:7:0329/091232.742641:ERROR:command_buffer_proxy_impl.cc(325)] GPU state invalid after WaitForGetOffsetInRange."#asahi · 2023-03-29 09:34
mkurzAlso stuff from apple-dcp#asahi · 2023-03-29 09:32
mkurz(At least it seems there are things logged I didn't see before)#asahi · 2023-03-29 09:32
mkurzjannau: The thing happened again, this time I think I have more information in the logs, see https://github.com/AsahiLinux/linux/issues/126#issuecomment-1488260640#asahi · 2023-03-28 21:27
mkurzbut I started chromium again before #asahi · 2023-03-28 21:27
mkurzjannau: logged out/in, posted the updated output #asahi · 2023-03-28 21:19
mkurzok no, tried to start IntelliJ, looks very bad#asahi · 2023-03-28 21:19
mkurzmay only chromium affected