<sewn>
<ruivlea> "i tried to build firefox 114. it..." <- sounds awfully familiar
<sewn>
ayo testuser: check that out
testuser[m] has quit [Server closed connection]
testuser[m] has joined #kisslinux
ElKowar has quit [Server closed connection]
ElKowar has joined #kisslinux
shokara has quit [Remote host closed the connection]
shokara has joined #kisslinux
ruivlea has joined #kisslinux
<ruivlea>
so, am i the only one that experience this firefox segfault issue?
<ruivlea>
today i built firefox esr 102.13.0. And seems ok. no problem currently.
angerisagift has quit [Ping timeout: 260 seconds]
angerisagift has joined #kisslinux
pbsds has quit [Server closed connection]
pbsds has joined #kisslinux
ruivlea has quit [Ping timeout: 246 seconds]
<sewn>
no i used to face it as well mate
ruivlea has joined #kisslinux
<sewn>
lemme try building firefox 115
<sewn>
116.0b2*
ruivlea has quit [Ping timeout: 245 seconds]
<sewn>
seems to be fine but i get seccomp sandbox violations
<sewn>
firefox would segfault if i had built it without debug info
<sewn>
i believe its because of my vaapi setup
<xdream8[m]>
I install firefox using nix
ruivlea has joined #kisslinux
<ruivlea>
do you mean not using export RUSTFLAGS="$RUSTFLAGS -Cdebuginfo=0" in build script?
<sewn>
<ruivlea> "do you mean not using export..." <- if i have a bad firefox build that may crash and i build it with debuginfo, it no longer works and segfaults
<sewn>
so im not really sure anymore
floorcrawler has quit [Ping timeout: 246 seconds]
<ruivlea>
i just tried build 115 without RUSTFLAGS="$RUSTFLAGS -Cdebuginfo=0" and still segfault
<ruivlea>
i will stick to esr 102 at this moment. and see if mozilla keep maintains it or not. at least it's security