Bug 267497 - Realtime error: Could not map pid: Could not determine pid namespace
Summary: Realtime error: Could not map pid: Could not determine pid namespace
Status: RESOLVED DUPLICATE of bug 238403
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKitGTK (show other bugs)
Version: Other
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-01-13 08:16 PST by tekstryder
Modified: 2024-01-22 10:26 PST (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description tekstryder 2024-01-13 08:16:13 PST
• Arch Linux | Kernel 6.6.11
• Gnome-shell | Mutter 45.3
• Wayland (`gnome-shell --no-x11`)
• Evolution: 3.50.3
• Xdg-desktop-portal 1.18.2
• webkit2gtk 2.42.4

Originally reported against xdg-desktop-portal here:
https://github.com/flatpak/xdg-desktop-portal/issues/1167

Subsequently reported against evolution here:
https://gitlab.gnome.org/GNOME/evolution/-/issues/2582

Third time's a charm, right?

Each time the Evolution Mail app is launched the following error is emmitted:

Jan 11 10:14:12 xdg-desktop-por[8439]: Realtime error: Could not map pid: Could not determine pid namespace: Could not find instance-id in process's /.flatpak-info

To quote Milan's (Evolution developer) comment after investigation...
https://gitlab.gnome.org/GNOME/evolution/-/issues/2582#note_1921965

"For what it's worth, when I run Evolution from a terminal as:

   WEBKIT_DISABLE_SANDBOX_THIS_IS_DANGEROUS=1 evolution

there is no such warning added into the journal, which I consider as a proof that the problem is related to the WebKit's sandbox. There's not much Evolution can do about it.

Furthermore, when I run devhelp, which also uses WebKitGTK, there is added the same warning into the journal. And the same when I run Epiphany, a WebKitGTK based web browser."
Comment 1 Michael Catanzaro 2024-01-13 09:59:24 PST
Hm, pretty sure this is impossible to fix on our end. We don't have a real flatpak instance. We could add a fake instance ID to the flatpak-info file, but this seems worse than doing nothing. At least with the ID missing, xdg-desktop-portal has a chance to detect that there is no ID and take a fallback codepath instead of trying to work with a bogus ID and failing later on.

I would reopen that xdg-desktop-portal bug report.
Comment 2 Michael Catanzaro 2024-01-13 10:00:22 PST
(BTW I presume you are using a non-flatpak version of Evolution. If you're using it via flatpak, then further investigation is required.)
Comment 3 tekstryder 2024-01-13 10:05:44 PST
Correct, non-flatpak evolution.

Okay, thanks. Back to xdg-desktop-portal I go. Full circle!
Comment 4 Michael Catanzaro 2024-01-13 16:15:50 PST
(Alternatively, if xdg-desktop-portal doesn't want us to create a fake flatpak-info anymore, it would be welcome to define some alternative format we could switch to instead. But currently flatpak-info is the only game in town.)
Comment 5 Michael Catanzaro 2024-01-22 10:26:02 PST

*** This bug has been marked as a duplicate of bug 238403 ***