#
✕ nick:jtolio
#asahi-alt · 2023-07-12 21:34
jtolio@glanzmann I don't suppose it would be easy to have a main/source/Sources in your dpkg repository? `apt-get source libgl1-mesa-dri` would be convenient here, but i'll go get it elsehow :)
#asahi-alt · 2023-07-12 21:30
jtoliopprof also seems to think that __driDriverGetExtensions_d3d12 is calling itself
#asahi-alt · 2023-07-12 21:19
jtoliothis doesn't have the debug symbols (i don't know how to get debug symbols to pprof.host) but https://pprof.host/hw0g/top says that all the time is being spent in apple_dri.so. it doesn't appear that the cpu waste is happening in kwin code
#asahi-alt · 2023-07-12 21:07
jtoliomeanwhile, here's the window sharing version that doesn't spin out: https://github.com/KDE/kwin/blob/Plasma/5.27/src/plugins/screencast/windowscreencastsource.cpp#L43-L50
#asahi-alt · 2023-07-12 21:06
jtolioaccording to pprof, this is the function that is (indirectly) calling __driDriverGetExtensions_d3d12: https://github.com/KDE/kwin/blob/Plasma/5.27/src/plugins/screencast/outputscreencastsource.cpp#L42-L48
#asahi-alt · 2023-07-12 21:03
jtoliomaybe an easier thing to try would be to pull a later build of kwin_wayland from sid, since arch has 5.27.6 kwin and debian bookworm has 5.27.5
#asahi-alt · 2023-07-12 21:01
jtoliosure, though I was hoping to avoid a reinstall of everything or even partition resizing. foolish of me to have set this up as my primary workstation lol. i mean, this seems like a common enough pattern within this IRC group (share fullscreen in firefox on wayland with KDE) that perhaps someone else knows if it works for them before i go and reinstall?
#asahi-alt · 2023-07-12 20:55
jtoliokwin_wayland pegs a core to 100% spending the entire time in __driDriverGetExtensions_d3d12 - 98.5% of the pprof output. So, now what? lol. I don't know if this is KDE, Asahi GPU drivers, or what. Anyone have ideas of what I should look to next to try and fix full screen sharing?
#asahi-alt · 2023-07-12 20:55
jtolioI'm on @glanzmann's Debian distro on an M1 mini, using KDE on Wayland. Whenever I screenshare a window on Firefox, things work fine. However, when I try and screenshare my full screen, the compositor (kwin_wayland) spins out and pegs a core and goes unresponsive, making it pretty hard to interact with windows. I went and added gperftools' CPU profiler to a build of kwin_wayland, and the difference is when trying to share a full screen
#asahi-alt · 2023-02-21 22:08
jtoliodon't worry about me. with chrome in debug logs, i'm getting weird webrtc stun failures, so maybe this is a network issue somehow?
#asahi-alt · 2023-02-21 21:52
jtoliothank you so much! i can't get it to attend any meetings, so that's encouraging!
#asahi-alt · 2023-02-21 21:34
jtolioi suppose the key thing here is i'm looking for an existence proof that google meet has worked for anyone in any asahi linux configuration. it's certainly likely something is broken with my system, but it'd be nice to know the tree i'm barking up is worth it.
#asahi-alt · 2023-02-21 21:27
jtoliothis might be a crazy question, but has anyone been able to get google meet to work at all with asahi? context: i'm using Glanzmann's m1 debian release on an original m1 mini. whenever i start google meet (firefox, chromium), it either can't get the devices at all (firefox), or it does, but then times out connecting.