crashing Librewolf after switching between programs since pkg upgrade last week

James777 · Mar 24, 2025

On FreeBSD 14.2-RELEASE with GNOME I have problem on my desktop (AMD Phenom II X4 B45 + Nvidia GTX750 Ti) with crashing Librewolf when I switch between programs, Librewolf -> some another program(s) -> back to Librewolf which then shows dialog that must be closed. But Librewolf wasn't in the pkg upgrade last week (wednesday), so I think that problem is somewhere else. I tried to build in ports the newest version (570.133.07) of nvidia-driver if it helps, then the previous version before update (570.86.16) and neither helped.

when I run Librewolf from terminal it gives error after crashing:
Exiting due to channel error.

or when I run Librewolf with LIBGL_ALWAYS_SOFTWARE=1 MOZ_WEBRENDER=0 LIBREWOLF_HEADLESS=1 librewolf:
[Parent 33412, ProcessHangMon] WARNING: pipe error: Socket is not connected: file /wrkdirs/usr/ports/www/librewolf/work/librewolf-136.0.1-1/ipc/chromium/src/chrome/common/ipc_channel_posix.cc:664
Exiting due to channel error.

EDIT: it also crash after unlock lockscreen

jb_fvwm2 · Mar 25, 2025

======================================================
Librewolf runs here but youtube, while showing a video, has no sound, neither does youtube on firefox. On some other browsers [ chrome if I recall ] there is a spinner and the actual video never starts.
Just posting here in case the issue there fixed fixes the sound issue here by some quirk.
====================================================
sh /usr/local/etc/rc.d/sndiod onestart

** found that fix from another thread soon after this post!! So this post can be ignored...

NapoleonWils0n · Mar 25, 2025

Post in thread 'Your web browsing environment in 2025 - self-hosted Firefox sync?'

Mar 25, 2025

youtube has no sound

Firefox uses Pulseaudio by default

so you have to start pulseaudio before opening Firefox

Code:

pulseaudio --start --daemonize 2>/dev/null

but you can change the audio backend to oss

To force a specific backend open

Code:

about:config

and create

Code:

media.cubeb.backend

set the option to string and

Code:

oss

fmc000 · Mar 26, 2025

FWIW, I am not experiencing these problems using Librewolf under labwc (Wayland). I never had a single crash and I don't use any software mixer, audio works just fine.

James777 · Apr 6, 2025

Fixed with Librewolf 136.0.4-1.

fmc000 · Tuesday at 3:55 PM

Latest update decided for some reason that my profile directory had to be moved from ~/.librewolf to ~/.mozilla/librewolf and thus Librewolf started with a fresh empty profile. Did this happen to anyone else?

gotnull · Tuesday at 4:52 PM

fmc000 said:
Latest update decided for some reason that my profile directory had to be moved from ~/.librewolf to ~/.mozilla/librewolf and thus Librewolf started with a fresh empty profile. Did this happen to anyone else?

It seems to be known issue, I found this:

137.0 blocker: profile / user_dir path broken

We are currently unable to release `137.0-1` due to some rather heavy breakage: releases built on the upstream `137.0` base look for profiles in `~/.mozilla` instead of `~/.librewolf`, which is quite a bit of a mess. (which is why I've pulled the `137.0-1` source release again, too) Thanks a ...

codeberg.org

fmc000 · Tuesday at 5:12 PM

Yes, that's exactly this. It seems that they decided to ship LW137 nonetheless... For reference:

My solution was just to close the browser, remove everything from ~/.mozilla/librewolf and then move all the contents from ~/.librewolf there. Optionally the old directory can be removed.