Web is the browser I would like to use but installing it in Debian 12 with Gnome (flathub) on my desktop and on an MS surface pro 3 have the same result. It is elegant in its simplicity but it crashes sometimes, but not always, when logging into web sites requiring a password. I have two questions.
I can’t find a setting that gives the option of sending crash details back to the developers. Is there something like that?
The other question is whether there are debug options for running it or logs to look at. Any help with that?
The developer suggested this article to collect a stack trace. There is a section titled “Stack traces for Flatpak apps”.
You should usually be able to find a link to report issues with an application below that application’s description in Software or on Flathub website.
I usually try running the application from terminal. While it runs, it may print messages to the terminal.
$ flatpak run org.gnome.Epiphany
Assuming the default options for an installation of Debian, the journal may provide some messages. For example, to print messages in real time, I run journalctl -f and later stop it with Ctrl+C keyboard shortcut.
All GNOME applications (should) have 'Report an issue' link in the application’s About dialog, clicking on which should land in the app’s issue reporting page.
In this case, you can post your stack trace right here in Discourse once you have it. Then I can advise on whether the issue should be reported to Epiphany (on GNOME GitLab) or WebKitGTK (on WebKit Bugzilla).
I tried running Web from the command line. Here is the dialog showing is start with a couple of warnings and then produce a further warning after it crashed:
ken@DualDebian:~$ flatpak run org.gnome.Epiphany
MESA-INTEL: warning: ../src/intel/vulkan/anv_formats.c:763: FINISHME: support YUV colorspace with DRM format modifiers
MESA-INTEL: warning: ../src/intel/vulkan/anv_formats.c:794: FINISHME: support more multi-planar formats with DRM modifiers
(epiphany:2): epiphany-WARNING **: 20:29:35.156: Web process terminated by API request
(WebKitWebProcess:2): GStreamer-CRITICAL **: 20:33:17.005: gst_buffer_pool_acquire_buffer: assertion 'GST_IS_BUFFER_POOL (pool)' failed
(epiphany:2): epiphany-WARNING **: 20:33:17.039: Web process crashed
ken@DualDebian:~$
** (process:2): ERROR **: 20:33:17.275: sendPIDToPeer: Failed to send pid: Broken pipe
ken@DualDebian:~$
I checked to see which route to producing a core dump would apply using the instructions here: https://handbook.gnome.org/issues/stack-traces.html. If I understand this correctly, I think I need to do a core dump manually.
It sounds like you have multiple unrelated crashes here, which is confusing things. Start by picking just one crash to focus on, and one URL where the crash occurs, and attach a stack trace and the terminal output. Then we can tell you which issue tracker to move to.
If you can reproduce a different crash with a different stack trace on a different URL, we can look at that separately.
