Created attachment 1799477 [details] Backtrace as exported from `abrt-cli gdb` Description of problem: Epiphany shows a tab crashes. Abrt shows the crash but refuses to report the issue due to the error message shown above. Version-Release number of selected component (if applicable): libreport-2.15.2-2.fc34.x86_64 gnome-abrt-1.3.6-7.fc34.x86_64 webkit2gtk3-2.32.1-1.fc34.x86_64 epiphany-40.1-1.fc34.x86_64 gtk3-3.24.29-1.fc34.x86_64 glib2-2.68.2-1.fc34.x86_64 How reproducible: Multiple times on my computer Steps to Reproduce: 1. Open Epiphany 2. Play Instagram videos 3. Observe Epiphany crash 4. Open GNOME ABRT 5. Try to report issue Actual results: Reporting aborted. Error message: > Der Server hat mit einer Fehlermeldung geantwortet: »Server is not accepting problems from unpackaged files.« (rough translation of the first sentence: "The server has responded with an error message") Expected results: Be able to report crash in webkit2gtk3 Additional info: I'm unsure whether this is an issue caused by libreport or webkit2gtk3 or something else, but as it is a package installed as ordinary RPM package, "blaming" libreport is my best guess. Feel free to reassign since you probably know better.
I've reported the original crash itself to https://gitlab.gnome.org/GNOME/glib/-/issues/2438. This bug report is about the fact that abrt shows an error instead of reporting the crash.
Thanks for the bug report. Is it possible that Epiphany is installed from Flatpak?
(In reply to Michal Srb from comment #2) > Thanks for the bug report. Is it possible that Epiphany is installed from > Flatpak? No, it is not. However, epiphany runs some of its child processes (including several instances of /usr/libexec/webkit2gtk-4.0/WebKitWebProcess) as child of bwrap, i.e. in a container with separate namespace. Example process hierarchy: epiphany /usr/libexec/webkit2gtk-4.0/WebKitNetworkProcess /usr/bin/bwrap --args 50 -- /usr/bin/xdg-dbus-proxy --args=47 /usr/bin/bwrap --args 50 -- /usr/bin/xdg-dbus-proxy --args=47 /usr/bin/xdg-dbus-proxy --args=47 /usr/bin/bwrap --args 51 -- /usr/bin/xdg-dbus-proxy --args=48 /usr/bin/bwrap --args 51 -- /usr/bin/xdg-dbus-proxy --args=48 /usr/bin/xdg-dbus-proxy --args=48 /usr/bin/bwrap --args 48 -- /usr/libexec/webkit2gtk-4.0/WebKitWebProcess 10 41 /usr/bin/bwrap --args 48 -- /usr/libexec/webkit2gtk-4.0/WebKitWebProcess 10 41 /usr/libexec/webkit2gtk-4.0/WebKitWebProcess 10 41 /usr/bin/bwrap --args 63 -- /usr/libexec/webkit2gtk-4.0/WebKitWebProcess 18 30 /usr/bin/bwrap --args 63 -- /usr/libexec/webkit2gtk-4.0/WebKitWebProcess 18 30 /usr/libexec/webkit2gtk-4.0/WebKitWebProcess 18 30 /usr/bin/bwrap --args 72 -- /usr/libexec/webkit2gtk-4.0/WebKitWebProcess 22 68 /usr/bin/bwrap --args 72 -- /usr/libexec/webkit2gtk-4.0/WebKitWebProcess 22 68 /usr/libexec/webkit2gtk-4.0/WebKitWebProcess 22 68
Thank you for the update. I think that might explain why ABRT thinks that the file is not packaged in Fedora. We will try to dig deeper into this, but right now we don't know how to fix this problem. We will need to do some investigation first. Therefore we are not able to give any ETA on when the fix might land in Fedora. Thanks for the bug report and the follow up.
This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '34'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07. Fedora Linux 34 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. Thank you for reporting this bug and we are sorry it could not be fixed.