02:05 <sam_> mps: yes, but *others* were quoting glib versions

02:05 <sam_> (2.76 and so on)

02:05 <sam_> my point was there was a mix going on

07:34 <mps> sam_: yes, I noticed after I read your comment that cy8aer probably talking about glibc while I about glib

07:36 <mps> anyway I reverted glib to 2.76.4 (stable release) but still this morning firefox crashed with kernel 6.4-2

07:37 <mps> also yesteday I upgraded firefox to 115.0.3 so this version could be problem

07:37 <mps> yesterday*

07:38 <mps> all other software I use works fine for now with all kernel versions

07:40 <jannau> firefox crashes are most likely a mesa/kernel issue. I have finally a usable backtrace

07:41 <mps> it didn't crashed for me with mesa 20230725 and kernel 6.4-1

07:42 <mps> and all previous mesa and kernels. worked stable for more than a year

07:45 <jannau> are you sure about asahi-6.4-1? How long did you run it. are you sure about asahi-6.4-1? and mesa asahi-20230725 both asahi-6.4-2/3 were tagged before mesa

07:46 <mps> yes, I used 6.4-1 and mesa 20230725 till yesterday. didn't had any issue with firefox

07:48 <mps> iirc around new year I switched to mesa asahi and till yesterday didn't noticed any problem with firefox

07:50 <mps> if firefox crashes again I will install 6.4-1 and will see is that combo is stable

10:40 <cy8aer> jannau: I had the 6.4-1 with 20230706 running, never with 20230725

10:41 <cy8aer> and that was stable, I also never had this ff freezing effect.

10:41 <cy8aer> My actual crash scenario is with both 6.4-3 and 20230725

10:44 <mps> cy8aer: on what model?

10:44 <cy8aer> mbp14 m1 pro

10:45 <mps> interesting, also I use m1pro mbp though I think it is 16"

10:45 <mps> couldn't remember all these sizes

10:46 <mps> currently testing on m1 mbp 13" or 14" from first m1 series

10:47 <mps> j293

10:48 <mps> uptime is 1 hour and FF didn't crashed

10:48 <cy8aer> The problem I have is that you are running the esr and I am running the 115.0.2. I had crash problems before but they were magically fixed with the next ff version. But esr is a different package. The only thing I can see from https://tracker.debian.org is that firefox and firefox-esr were uploaded at the same time. It can be that both ff versions have the same problem - if it is a ff problem.

10:48 <mps> no, I'm running FF 115.0.3

10:49 <cy8aer> and esr is 115.0.3 too (so long term firefox is bleeding edge too today)

10:50 <mps> yrs

10:50 <mps> I'll let it running few hours on j293 and see

10:51 <cy8aer> That is why I wrote that I will wait for the next ff version until I will give some alarm...

10:51 <cy8aer> (for me it is 115.0.3 debian unstable)

10:54 <mps> also upgraded FF to 115.0.3 on my wife notebook, waiting for her questions :)

11:12 <mps> crashed also on j293

14:38 <mikee3000> how do i check if i have the graphics drivers installed correctly? I'm getting an error when i'm trying to run snap installed spectacle

14:38 <mikee3000> libEGL warning: MESA-LOADER: failed to open apple: /snap/spectacle/172/kf5/usr/lib/aarch64-linux-gnu/dri/apple_dri.so:

14:38 <mikee3000> and screen recording is very slow

14:38 <mikee3000> and screen recording is very slow using a different app

14:49 <mikee3000> Actually, i think i just asked a pretty stupid question :/ - i can see the installed packages from Thomas Glanzmann's repo, and they have versions

14:50 <tobhe> mikee3000: snaps and flatpacks are a bit tricky since they often package their own mesa which probably doesn't include the asahi driver

14:54 <mikee3000> tobhe: yeah, that makes sense. I wanted to make a screen recording, but both Kooha and VokoscreenNG were very slow (unusably so). I looked at Asahi's website, and it said that some apps are not expected to work, but Spectacle should. i'm on Debian stable so spectacle is on the version where it doesn't have screen recording, so i was hoping that maybe a snap would work

17:23 <david2> Hi, the install script for ubuntu-asahi failed at setting the ubuntu as the default boot volume (runned it as a non machine owner (marcan)), did it miss important steps (from a glance at the main script that doesn’t seems to be the case), if so, do you confirm it is safe to reboot into it? What should I do now, re-run the script from the machine-owner user?