Not opening on Fedora Workstation 44
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 38/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Quiet
- Tech stack
- fedora, linux
- Domain
- desktop, operating-systems
Research direction
Start by reproducing the failure with flatpak run io.github.gamingdoom.Datcord on Fedora Workstation 44 and compare the Wayland protocol, GTK, sandbox, and headless-mode messages. The issue also notes the cache path /home/user/.var/app/io.github.gamingdoom.Datcord/cache, which was already tested. Done means Datcord opens a normal window from the icon and CLI instead of remaining a background task.
Written by the indexing model from the issue text.
Description
Just upgraded to Fedora Workstation 44 and Datcord does no longer open.
When I click the icon it does not open a window and I get a crash notification after a few seconds. It shows under background tasks though. And I can hear discord sounds etc.
If I try to run it from the cli I get this:
user@host ~> flatpak run io.github.gamingdoom.Datcord
This instance is first.
[9] Sandbox: CanCreateUserNamespace() clone() failure: EPERM
[GFX1-]: (gnome) Wayland protocol error: interface 'wp_image_description_v1' has no event 2
(datcord:2): Gtk-CRITICAL **: 16:42:00.521: gtk_widget_get_scale_factor: assertion 'GTK_IS_WIDGET (widget)' failed
Window -> Headless
[60] Sandbox: CanCreateUserNamespace() clone() failure: EPERM
*** You are running in headless mode.
*** You are running in headless mode.
Tried to delete the cache folder (/home/user/.var/app/io.github.gamingdoom.Datcord/cache) but that didn't work either.
- Dominant language
- Shell
- Stars
- 0
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Similar issues
-
`helios / deploy`: switch zone wait in `deploy.sh` has almost no headroom over healthy startup timesPossibly taken A pull request linked to this issue is open or already merged. OpenTest Flake
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
oxidecomputer/omicron#11453 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
gnosis/gnosis_vpn#540 ·
Maintainers usually reply within 1 day