Crashes after a few seconds of opening

[Hew-ux]

Simple, the browser crashes after a few seconds of it being opened. During those few seconds, the browser is functional and reactive like usual. When it crashes, there is no error message, it just instantly closes.

The backtrace: backtrace.txt

The backtrace as according to the KDE bug reporter (seems pretty useless):

--- Running report_uReport ---
Error: Unable to open './coredump': No such file or directory

--- Skipping collect_GConf ---
No matching actions found for this event.

--- Skipping collect_vimrc_system ---
No matching actions found for this event.

--- Skipping collect_vimrc_user ---
No matching actions found for this event.

--- Skipping collect_xsession_errors ---
No matching actions found for this event.

--- Running analyze_CCpp ---
Generating backtrace
Backtrace is generated and saved, 108370 bytes
Can't open file 'component' for reading: No such file or directory

--- Running analyze_BodhiUpdates ---
Looking for similar problems in bugzilla

My PC info:

NAME="Nobara Linux"
VERSION="40 (KDE Plasma)"
ID=nobara
ID_LIKE="rhel centos fedora"
VERSION_ID=40
VERSION_CODENAME=""
PLATFORM_ID="platform:f40"
PRETTY_NAME="Nobara Linux 40 (KDE Plasma)"
ANSI_COLOR="0;38;2;60;110;180"
LOGO=nobara-logo-icon
CPE_NAME="cpe:/o:nobaraproject:nobara:40"
DEFAULT_HOSTNAME="nobara"
HOME_URL="https://nobaraproject.org/"
DOCUMENTATION_URL="https://www.nobaraproject.org/"
SUPPORT_URL="https://www.nobaraproject.org/"
BUG_REPORT_URL="https://gitlab.com/gloriouseggroll/nobara-images"
REDHAT_BUGZILLA_PRODUCT="Nobara"
REDHAT_BUGZILLA_PRODUCT_VERSION=40
REDHAT_SUPPORT_PRODUCT="Nobara"
REDHAT_SUPPORT_PRODUCT_VERSION=40
SUPPORT_END=2025-05-13
VARIANT="KDE Plasma"
VARIANT_ID=kde

[FloridaMan7588]

Sorry to get to this after so long, but the provided backtrace.txt gives me a little information. I'm not the upstream developer (and have little understanding of the browser's inner workings :p), so this is just a working theory, but can you just try uninstalling and reinstalling from latest? This might be possibly be related to KDE but I can't say for certain at the moment, looks like a segmentation fault of some kind though. Otherwise I agree, the errors are rather esoteric and I can't really say anything beyond that. I will spin up a Nobara KDE VM and try to reproduce in the mean time.

[FloridaMan7588]

On a fresh install of Nobara in a VM, I cannot replicate this issue. I am able to browse and even YouTube playback works properly. I won't close the issue but I won't be trying to work on this actively until I am able to reproduce it in any way. I would just try reinstalling it like I suggested above, but otherwise I can't really say.

[Hew-ux]

The issue remains after uninstalling and reinstalling Waterfox. I suspect the issue is related to Nvidia + wayland, hence why you did not recreate the issue in a VM. I tried installing and running the Waterfox flatpak on a completely different computer, one powered by an AMD Radeon graphics card, and there are no issues there.

On the computer with the issue on it, I ran the flatpak via terminal and captured the output:

niroku@Room-TV-PC:~$ /usr/bin/flatpak run --branch=stable --arch=x86_64 --command=waterfox --file-forwarding net.waterfox.waterfox @@u %u @@

(waterfox:2): Gtk-WARNING **: 17:23:57.870: Theme directory 32/emblems of theme Eleven-Dark has no size field

(waterfox:2): Gtk-WARNING **: 17:23:57.871: Theme directory 32@2x/emblems of theme Eleven-Dark has no size field

(waterfox:2): Gtk-WARNING **: 17:23:57.872: Theme directory 48/emblems of theme Eleven-Dark has no size field

(waterfox:2): Gtk-WARNING **: 17:23:57.872: Theme directory 48@2x/emblems of theme Eleven-Dark has no size field

... and it didn't crash. This is the same command as what's in my application launcher, so I don't know how or why this was any different. But it's a lead. The browser also attempts to open the page "%u", which of course doesn't exist. Maybe certain elements aren't passed through to the web browser when launching from terminal compared to the application launcher from Plasma? Is there a debug flag I can turn on to see this?

I tried using Firefox's -devtools flag, but that resulted in a quick crash which had the following message:

niroku@Room-TV-PC:~$ /usr/bin/flatpak run --branch=stable --arch=x86_64 --command=waterfox --file-forwarding net.waterfox.waterfox @@u %u @@ -devtools
# same as above until this point
(waterfox:2): Gtk-WARNING **: 17:32:29.815: Theme directory 48@2x/emblems of theme Eleven-Dark has no size field

Crash Annotation GraphicsCriticalError: |[0][GFX1-]: Wayland protocol error: wp_linux_drm_syncobj_surface_v1@59: error 4: explicit sync is used, but no acquire point is set
 (t=3.59521) [GFX1-]: Wayland protocol error: wp_linux_drm_syncobj_surface_v1@59: error 4: explicit sync is used, but no acquire point is set

Gdk-Message: 17:32:33.317: Error flushing display: Protocol error
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Exiting due to channel error.
Crash Annotation GraphicsCriticalError: |[C0][GFX1-]: CompositorBridgeChild receives IPC close with reason=AbnormalShutdown (t=3.1693) niroku@Room-TV-PC:~$ 

It opens for a split-second with the page loaded and interactable before crashing. So an element drawn in the dev tools window seems to instantly trigger the crash. When using the /usr/bin/flatpak run --branch=stable --arch=x86_64 --command=waterfox --file-forwarding net.waterfox.waterfox @@u %u @@ command and opening the dev tools from within the browser's menus, no crash occurs.