Bug 1883621
| Summary: | snapd apps won't run or crash on launch | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | itrymybest80 |
| Component: | snapd | Assignee: | Zygmunt Krynicki <me> |
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 33 | CC: | balay, go-sig, maciek.borzecki, me, ngompa13 |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-11-30 16:28:36 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
itrymybest80
2020-09-29 17:52:58 UTC
project error I tried a bunch more snapd apps and run into similar problems. I did reboot after installing snapd and ran hello-world to test, where I got my first warning. snap list Name Version Rev Tracking Publisher Notes chromium 85.0.4183.121 1328 latest/stable canonical✓ - core 16-2.46.1 9993 latest/stable canonical✓ core core18 20200724 1885 latest/stable canonical✓ base core20 20 634 latest/stable canonical✓ base foliate 2.4.2 1119 latest/stable johnfactotum - gnome-3-28-1804 3.28.0-17-gde3d74c.de3d74c 128 latest/stable canonical✓ - gnome-3-34-1804 0+git.3556cb3 60 latest/stable canonical✓ - gtk-common-themes 0.1-36-gc75f853 1506 latest/stable canonical✓ - hello-world 6.4 29 latest/stable canonical✓ - losslesscut 3.22.3 35 latest/stable mifino - xonotic 0.8.2 53 latest/stable snapcrafters - yuzu 0-394 104 latest/stable nightmayr - chromium WARNING: cgroup v2 is not fully supported yet, proceeding with partial confinement [13347:13347:1001/020349.706270:ERROR:browser_main_loop.cc(1417)] Unable to open X display. foliate WARNING: cgroup v2 is not fully supported yet, proceeding with partial confinement Cannot get default EGL display: EGL_BAD_PARAMETER WaylandCompositor requires eglCreateImage and eglDestroyImage. Nested Wayland compositor could not initialize EGL losslesscut WARNING: cgroup v2 is not fully supported yet, proceeding with partial confinement (losslesscut:13963): Gtk-WARNING **: 02:05:20.967: cannot open display: :0 xonotic WARNING: cgroup v2 is not fully supported yet, proceeding with partial confinement Game is Xonotic using base gamedir data gamename for server filtering: Xonotic Xonotic Linux 22:06:02 Mar 31 2017 - release Current nice level is below the soft limit - cannot use niceness Skeletal animation uses SSE code path DPSOFTRAST available (SSE2 instructions detected) Quake Error: Failed to init SDL video subsystem: No available video device yuzu WARNING: cgroup v2 is not fully supported yet, proceeding with partial confinement Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway. qt.qpa.xcb: could not connect to display :0 qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found. This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, wayland-egl, wayland, wayland-xcomposite-egl, wayland-xcomposite-glx, xcb. Avbruten (SIGABRT) (minnesutskrift skapad) The warning you see is unrelated to the issue. I suspect you are running a wayland session, all the snaps that you tired seem to be expecting/trying to use X11. Is Xwayland running? I'm currently logged in to the default Fedora 33 gnome/wayland session on my system. echo $XDG_SESSION_TYPE wayland echo $WAYLAND_DISPLAY wayland-0 /usr/bin/gnome-shell --wayland --display-server (gnome-shell:25361): mutter-WARNING **: 17:02:27.628: Failed to create backend: Could not take control: GDBus.Error:System.Error.EBUSY: Device or resource busy lspci -k | grep -A 2 VGA 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] (rev e7) Subsystem: Micro-Star International Co., Ltd. [MSI] Device 3417 Kernel driver in use: amdgpu That's interesting. I can reproduce this on Arch in a Gnome Wayland session too. It's as if the apps try to use wayland, but fail for some reason. Setting DISPLAY=:0 successfully redirects them to Xwayland though and ones that I tried start correctly. I don't know much about apps being clients to a wayland compositor but if you can, try to open a topic at https://forum.snapcraft.io/ there should be some folks with actual hands-on knowledge of wayland who may be able to debug this further. Some additional information was collected here: https://gitlab.gnome.org/GNOME/mutter/-/issues/1454 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1897224 Looks like a problem is related to mutter, where it no longer exposes an abstract socket for Xwayland. The GNOME bug tracker report contains more details. This message is a reminder that Fedora 33 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30. 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 Fedora 'version' of '33'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 33 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, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 33 changed to end-of-life (EOL) status on 2021-11-30. Fedora 33 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. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |