Description of problem: Tried to start an Epiphany web app. Version-Release number of selected component: epiphany-runtime-1:44.6-1.fc38 Additional info: reporter: libreport-2.17.11 backtrace_rating: 4 rootdir: / runlevel: N 5 executable: /usr/bin/epiphany cgroup: 0::/user.slice/user-4051.slice/user/app.slice/app-gnome-org.gnome.Epiphany.WebApp_6b1f893805e29582969095a741d60a5f43734af8-2067439.scope type: CCpp dso_list: /usr/bin/epiphany epiphany-runtime-1:44.6-1.fc38.x86_64 (Fedora Project) 1691998805 uid: 4051 reason: epiphany killed by SIGTRAP kernel: 6.6.4-100.fc38.x86_64 crash_function: trap_handler package: epiphany-runtime-1:44.6-1.fc38 journald_cursor: s=2c7de5b121464f098a29ca163d211c4a;i=c4952;b=c6ac733c2e464cba9fdf86e2021bbd73;m=72eee6d408;t=60cc46aa1d930;x=ec7c76249d8e395b comment: Tried to start an Epiphany web app. cmdline: /usr/bin/epiphany --application-mode --profile=/home/ossman/.local/share/org.gnome.Epiphany.WebApp_6b1f893805e29582969095a741d60a5f43734af8 https://cendio.flexhosting.se/Mobile/#startPage Truncated backtrace: Thread no. 1 (20 frames) #2 trap_handler at ../lib/ephy-debug.c:104 #5 WebKit::waitUntilSyncedOrDie at /usr/src/debug/webkitgtk-2.42.3-1.fc38.x86_64/Source/WebKit/UIProcess/Launcher/glib/XDGDBusProxy.cpp:180 #6 WebKit::XDGDBusProxy::launch() at /usr/src/debug/webkitgtk-2.42.3-1.fc38.x86_64/Source/WebKit/UIProcess/Launcher/glib/XDGDBusProxy.cpp:241 #7 WebKit::bubblewrapSpawn(_GSubprocessLauncher*, WebKit::ProcessLauncher::LaunchOptions const&, char**, _GError**) at /usr/src/debug/webkitgtk-2.42.3-1.fc38.x86_64/Source/WebKit/UIProcess/Launcher/glib/BubblewrapLauncher.cpp:902 #8 WebKit::ProcessLauncher::launchProcess() at /usr/src/debug/webkitgtk-2.42.3-1.fc38.x86_64/Source/WebKit/UIProcess/Launcher/glib/ProcessLauncherGLib.cpp:226 #9 WebKit::ProcessLauncher::ProcessLauncher(WebKit::ProcessLauncher::Client*, WebKit::ProcessLauncher::LaunchOptions&&) at /usr/src/debug/webkitgtk-2.42.3-1.fc38.x86_64/Source/WebKit/UIProcess/Launcher/ProcessLauncher.cpp:45 #10 WebKit::ProcessLauncher::create(WebKit::ProcessLauncher::Client*, WebKit::ProcessLauncher::LaunchOptions&&) at /usr/src/debug/webkitgtk-2.42.3-1.fc38.x86_64/Source/WebKit/UIProcess/Launcher/ProcessLauncher.h:105 #11 WebKit::AuxiliaryProcessProxy::connect() at /usr/src/debug/webkitgtk-2.42.3-1.fc38.x86_64/Source/WebKit/UIProcess/AuxiliaryProcessProxy.cpp:141 #12 WebKit::WebProcessProxy::create(WebKit::WebProcessPool&, WebKit::WebsiteDataStore*, WebKit::WebProcessProxy::LockdownMode, WebKit::WebProcessProxy::IsPrewarmed, WebCore::CrossOriginMode, WebKit::WebProcessProxy::ShouldLaunchProcess) at /usr/src/debug/webkitgtk-2.42.3-1.fc38.x86_64/redhat-linux-build/webkitgtk-6.0/WTF/Headers/wtf/RawPtrTraits.h:44 #13 WebKit::WebProcessPool::createNewWebProcess(WebKit::WebsiteDataStore*, WebKit::WebProcessProxy::LockdownMode, WebKit::WebProcessProxy::IsPrewarmed, WebCore::CrossOriginMode) at /usr/src/debug/webkitgtk-2.42.3-1.fc38.x86_64/Source/WebKit/UIProcess/WebProcessPool.cpp:672 #14 WebKit::WebProcessPool::processForRegistrableDomain(WebKit::WebsiteDataStore&, WebCore::RegistrableDomain const&, WebKit::WebProcessProxy::LockdownMode) at /usr/src/debug/webkitgtk-2.42.3-1.fc38.x86_64/Source/WebKit/UIProcess/WebProcessPool.cpp:1102 #15 WebKit::WebPageProxy::launchProcess(WebCore::RegistrableDomain const&, WebKit::WebPageProxy::ProcessLaunchReason) at /usr/src/debug/webkitgtk-2.42.3-1.fc38.x86_64/Source/WebKit/UIProcess/WebPageProxy.cpp:1018 #16 WebKit::WebPageProxy::loadRequest(WebCore::ResourceRequest&&, WebCore::ShouldOpenExternalURLsPolicy, API::Object*) at /usr/src/debug/webkitgtk-2.42.3-1.fc38.x86_64/Source/WebKit/UIProcess/WebPageProxy.cpp:1605 #17 WebKit::WebPageProxy::loadRequest(WebCore::ResourceRequest&&) at /usr/src/debug/webkitgtk-2.42.3-1.fc38.x86_64/Source/WebKit/UIProcess/WebPageProxy.cpp:1622 #18 webkit_web_view_load_uri(WebKitWebView*, gchar const*) at /usr/src/debug/webkitgtk-2.42.3-1.fc38.x86_64/Source/WebKit/UIProcess/API/glib/WebKitWebView.cpp:3187 #19 ephy_web_view_load_url at ../embed/ephy-web-view.c:2601 #20 ephy_shell_open_uris_idle at ../src/ephy-shell.c:1482 #24 g_main_context_iterate.isra.0 at ../glib/gmain.c:4276 #25 g_main_context_iteration at ../glib/gmain.c:4343 #26 g_application_run at ../gio/gapplication.c:2573
Created attachment 2004779 [details] File: environ
Created attachment 2004780 [details] File: open_fds
Created attachment 2004781 [details] File: limits
Created attachment 2004782 [details] File: os_info
Created attachment 2004783 [details] File: proc_pid_status
Created attachment 2004784 [details] File: backtrace
Created attachment 2004785 [details] File: cpuinfo
Created attachment 2004786 [details] File: var_log_messages
Created attachment 2004787 [details] File: mountinfo
Created attachment 2004788 [details] File: maps
Created attachment 2004789 [details] File: core_backtrace
I see xdg-dbus-proxy exited with status 1, which is bad. Are there no other interesting messages in the system journal? We need to figure out why that is happening.
Presumably this is related to https://gitlab.gnome.org/GNOME/epiphany/-/issues/1780#note_1946293 right?
Yes, that was at the same time, so it is a likely cause. The journal has this to say: > Dec 18 09:20:00 ossman.lkpg.cendio.se systemd[2645]: Started app-gnome-org.gnome.Epiphany.WebApp_6b1f893805e29582969095a741d60a5f43734af8-2067439.scope - Application launched by gnome-shell. > Dec 18 09:20:00 ossman.lkpg.cendio.se org.gnome.Epiphany.WebApp_6b1f893805e29582969095a741d60a5f43734af8.desktop[2067515]: bwrap: Can't find source path /root/.cache/at-spi: Permission denied > Dec 18 09:20:00 ossman.lkpg.cendio.se epiphany[2067439]: Failed to fully launch dbus-proxy: Child process exited with code 1 > Dec 18 09:20:01 ossman.lkpg.cendio.se systemd[2645]: Started app-gnome-org.gnome.Epiphany.WebApp_430b38bf6daa7f9164b164b2ffd540b5a3afe2fd-2067519.scope - Application launched by gnome-shell. > Dec 18 09:20:01 ossman.lkpg.cendio.se org.gnome.Epiphany.WebApp_430b38bf6daa7f9164b164b2ffd540b5a3afe2fd.desktop[2067599]: bwrap: Can't find source path /root/.cache/at-spi: Permission denied > Dec 18 09:20:01 ossman.lkpg.cendio.se epiphany[2067519]: Failed to fully launch dbus-proxy: Child process exited with code 1 > Dec 18 09:20:02 ossman.lkpg.cendio.se systemd-coredump[2067517]: [🡕] Process 2067439 (epiphany) of user 4051 dumped core. > ...
(In reply to Pierre Ossman from comment #14) > > Dec 18 09:20:01 ossman.lkpg.cendio.se org.gnome.Epiphany.WebApp_430b38bf6daa7f9164b164b2ffd540b5a3afe2fd.desktop[2067599]: bwrap: Can't find source path /root/.cache/at-spi: Permission denied I think that's coming from: $ gdbus call --session --dest org.a11y.Bus --object-path /org/a11y/bus --method org.a11y.Bus.GetAddress Which is supposed to return something like: ('unix:path=/run/user/1000/at-spi/bus',) I think that paths under /root should never be returned when calling this method on the session bus, unless perhaps the session bus corresponds to the root user. But in this case, you're not running Epiphany as root, so it's strange to see this result. Maybe we need more safety checks to ensure the a11y bus doesn't get started as root? I think this should be fatal and I don't think we can do any better error message than what is already printing, so I don't see any need to change WebKit's behavior here.
The message was just in a log, so it wasn't terribly helpful as a user, since I got no visible response clicking the Epiphany icon. Would it be possible to start without accessibility and a warning? I would assume most users would be fine without those features.
No, if the a11y bus socket is not readable, that's a serious error and we should refuse to start. Checking the system journal or running the app in a terminal is just what you need to do when an app fails to start.
Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21. Fedora Linux 38 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 Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.
*** This bug has been marked as a duplicate of bug 2162351 ***