The snap newsflash was given custom assertions to auto connect to the webkitgtk content snap. But, users still often face issues where snapd blocks the connection to webkitgtk-6-gnome-2404
. The issue was mailed me again today by a user. It’s generally faced very randomly. The logs can be seen here
opened 06:57PM - 02 Mar 24 UTC
closed 08:51PM - 02 Mar 24 UTC
```
newsflash
13:53:45 - INFO - NewsFlash 3.1.5 (io.gitlab.news_flash.NewsFl… ash) (news_flash_gtk::app:86)
13:53:45 - INFO - Loading backend local_rss (news_flash:119)
13:53:45 - INFO - Successful load from config (news_flash_gtk::app:95)
** (news_flash:185393): WARNING **: 13:53:45.719: Could not open /sys/class/dmi/id/chassis_type: Failed to open file “/sys/class/dmi/id/chassis_type”: Permission denied
** (news_flash:185393): WARNING **: 13:53:45.719: Could not open /sys/firmware/acpi/pm_profile: Failed to open file “/sys/firmware/acpi/pm_profile”: Permission denied
** (news_flash:185393): ERROR **: 13:53:45.722: Unable to spawn a new child process: Failed to spawn child process “/usr/lib/x86_64-linux-gnu/webkitgtk-6.0/WebKitNetworkProcess” (No such file or directory)
Trace/breakpoint trap (core dumped)
```
UPDATE: I downgraded to 3.1.4 and it the problem persists.
Can someone kindly investigate into this snap? I think the old assertions can be a problem.
This request has been added to the queue for review by the @reviewers team.
Hey @soumyaDghosh
I think the custom assertion you mention (snap-declaration) was possibly removed at some point when webkitgtk-6-gnome-2404
received global auto-connection. You can check the snap-declaration for newsflash
here
I have no idea what is this issue related to. @pedronis does it look familiar to you?
Update: might it be related to Something wrong with webkit2 gtk-4.0 ?
(#askForInfo )
@jslarraz have you tried ifacetool with the relevant snaps and assertions?
No, I didn’t know about this tool, what’s that? How to use it?
@pedronis Everything looks ok according to ifacetool
$ ifacetool auto-connections --classic newsflash webkitgtk-6-gnome-2404 ffmpeg-2404 gtk-common-themes gnome-46-2404 mesa-2404
installing webkitgtk-6-gnome-2404: OK
installing ffmpeg-2404: OK
installing gtk-common-themes: OK
installing gnome-46-2404: OK
installing mesa-2404: OK
installing newsflash: OK
ffmpeg-2404:ffmpeg-2404 > ffmpeg-2404
gnome-46-2404:gnome-46-2404 > gnome-46-2404
gtk-common-themes:gtk-3-themes > gtk-3-themes
gtk-common-themes:icon-themes > icon-themes
gtk-common-themes:sound-themes > sound-themes
mesa-2404:gpu-2404 > gpu-2404
snapd:desktop > desktop
snapd:desktop-legacy > desktop-legacy
snapd:gsettings > gsettings
snapd:network > network
snapd:network-status > network-status
snapd:opengl > opengl
snapd:unity7 > unity7
snapd:wayland > wayland
snapd:x11 > x11
webkitgtk-6-gnome-2404:webkitgtk-6-gnome-2404 > webkitgtk-6-gnome-2404
: network-observe
: system-observe
@soumyaDghosh ifacetool allows you to simulate snapd behavior in terms of auto-connections. The git repo is GitHub - pedronis/ifacetool: tooling to work with snap interfaces and it is also packaged as a snap ifacetool
1 Like
Then why does this problem showup randomly?