[Bug]: Flatpak on Pop!_OS Linux is broken #1324

LiamDawe · 2022-07-27T09:50:21Z

Describe the Bug

I updated Pop!_OS Linux today and now it won't run via the Flatpak

Steps to Reproduce

actually try it?

Environment Information

OS: Pop!_OS
App Version and/or Commit ID:

Anything else?

Log of it:

liamdawe@pop-os:~$ flatpak run sh.cider.Cider
[10:48:12.068] [info] [AppEvents] App started
LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings
[10:48:12.225] [info] [PluginHandler] Loaded plugins: [
'chromecast.js',
'discordrpc.js',
'lastfm.js',
'menubar.js',
'mpris.js',
'raop.js',
'thumbar.js',
'webNowPlaying.js'
]
Gtk-Message: 10:48:12.230: Failed to load module "appmenu-gtk-module"
Gtk-Message: 10:48:12.265: Failed to load module "canberra-gtk-module"
Gtk-Message: 10:48:12.265: Failed to load module "canberra-gtk-module"
[0727/104812.276907:ERROR:scoped_ptrace_attach.cc(27)] ptrace: Operation not permitted (1)
/app/bin/cider-wrapper: line 7: 13 Trace/breakpoint trap (core dumped) cider "$@"

Code of Conduct

I agree to follow this project's Code of Conduct

habeasdata404 · 2022-07-27T12:08:36Z

The same problem with flatpak in Ubuntu 20.04 LTS. The message is the following.

[13 zypak-helper] Portal v4 is not available
[09:01:59.795] [info] [AppEvents] App started
LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings
[09:02:00.142] [info] [PluginHandler] Loaded plugins: [
'chromecast.js',
'discordrpc.js',
'lastfm.js',
'menubar.js',
'mpris.js',
'raop.js',
'thumbar.js',
'webNowPlaying.js'
]
Gtk-Message: 09:02:00.186: Failed to load module "canberra-gtk-module"
Gtk-Message: 09:02:00.186: Failed to load module "canberra-gtk-module"
[0727/090200.212813:ERROR:scoped_ptrace_attach.cc(27)] ptrace: Operation not permitted (1)
[21 zypak-sandbox] Dropping 0x55b131f24300 (3) because of connection closed
[21 zypak-sandbox] Host is gone, preparing to exit...
[21 zypak-sandbox] Quitting Zygote...
/app/bin/cider-wrapper, linha 7: 13 Trace/breakpoint trap (imagem do núcleo gravada)cider "$@"

geodro · 2022-07-27T12:54:44Z

The same problem with flatpak in Fedora 36

[15:53:50.309] [info] [AppEvents] App started
[15:53:50.313] [info] Hardware acceleration is disabled.
LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings
[15:53:50.506] [info] [PluginHandler] Loaded plugins: [
'chromecast.js',
'discordrpc.js',
'lastfm.js',
'menubar.js',
'mpris.js',
'raop.js',
'thumbar.js',
'webNowPlaying.js'
]
Gtk-Message: 15:53:50.553: Failed to load module "canberra-gtk-module"
Gtk-Message: 15:53:50.553: Failed to load module "canberra-gtk-module"
[0727/155350.567869:ERROR:scoped_ptrace_attach.cc(27)] ptrace: Operation not permitted (1)
/app/bin/cider-wrapper: line 7: 13 Trace/breakpoint trap (core dumped) cider "$@"

streetsamurai00mi · 2022-07-27T13:07:55Z

v1.5.1-beta..455 (https://github.com/ciderapp/Cider/tree/ab76c3c82dc6c4297f658824e400add9744f583e) works.
There are some changes after this making it core dumped

vapormusic · 2022-07-27T13:25:34Z

I suspect electron 20 beta 11 has something to do with this

rowbawts · 2022-07-27T17:41:02Z

It works for me (which is odd), I maintain the Flatpak version I test all builds before I publish them.

Fedora 36 Silverblue

I'm using AMD graphics using the free drivers.

rowbawts · 2022-07-27T17:42:29Z

Should I revert to 1.5?

mattmilano · 2022-07-27T17:53:59Z

Not working for me either on Pop OS. Tried running flatpak repair and uninstalled and reinstalled it. No go with version 1.5.1.

rowbawts · 2022-07-27T18:00:07Z

Ok, for everyone else did the issue begin after the 1.5.1 update or a system update? Because I find it odd that it works for me but not others.

@mattmilano If you're willing to try something out navigate to ~/.var/app/sh.cider.Cider/config/Cider/ and delete the cider-config.json file and try again. Uninstalling and reinstalling wouldn't have cleared this directory or any of its contents so it's worth a shot.

rowbawts · 2022-07-27T18:17:17Z

~~Also try this build flatpak install --user https://dl.flathub.org/build-repo/100199/sh.cider.Cider.flatpakref~~

Edit: This build has been pushed to the public channels report back with results.

mattmilano · 2022-07-27T18:21:34Z

@rowbawts Deleted the file and no effect.

rowbawts · 2022-07-27T18:29:03Z

@rowbawts Deleted the file and no effect.

Try the build I posted as well.

habeasdata404 · 2022-07-28T00:36:13Z

Ok, for everyone else did the issue begin after the 1.5.1 update or a system update? Because I find it odd that it works for me but not others.

@mattmilano If you're willing to try something out navigate to ~/.var/app/sh.cider.Cider/config/Cider/ and delete the cider-config.json file and try again. Uninstalling and reinstalling wouldn't have cleared this directory or any of its contents so it's worth a shot.

The issue began after the Cider 1.5.1 update. My other flatpaks are working fine.

rowbawts · 2022-07-28T00:58:07Z

Ok, for everyone else did the issue begin after the 1.5.1 update or a system update? Because I find it odd that it works for me but not others.
@mattmilano If you're willing to try something out navigate to ~/.var/app/sh.cider.Cider/config/Cider/ and delete the cider-config.json file and try again. Uninstalling and reinstalling wouldn't have cleared this directory or any of its contents so it's worth a shot.

The issue began after the Cider 1.5.1 update. My other flatpaks are working fine.

Can you also try the build I posted above and report back? If that one works I'll push that to everyone.

I can't test it myself as the current one works for me already.

geodro · 2022-07-28T07:01:52Z

It works for me (which is odd), I maintain the Flatpak version I test all builds before I publish them.

Fedora 36 Silverblue

I'm using AMD graphics using the free drivers.

I am also using Silverblue, but is not working.

This is my deployment:

● fedora:fedora/36/x86_64/silverblue (index: 0)
Version: 36.20220727.0 (2022-07-27T01:16:38Z)
BaseCommit: df3b6b99f3e9204859e6d9c0971636e94c2a5d2b8e63c1796f18b82db9962c47
├─ repo-0 (2022-05-04T21:16:11Z)
├─ repo-1 (2022-07-27T00:46:42Z)
└─ repo-2 (2022-07-27T00:53:25Z)
Commit: 0bcf00d115c67c12e6f5e38cc800dcf5cd06b1119a2747c6d73ab54370d9f104
├─ copr:copr.fedorainfracloud.org:lukenukem:asus-linux (2022-07-21T07:59:46Z)
├─ fedora (2022-05-04T21:16:11Z)
├─ fedora-cisco-openh264 (2022-04-07T16:52:38Z)
├─ fedora-modular (2022-05-04T21:12:01Z)
├─ rpmfusion-nonfree-nvidia-driver (2022-07-05T12:27:49Z)
├─ rpmfusion-nonfree-steam (2022-02-13T17:48:12Z)
├─ updates (2022-07-27T02:04:11Z)
├─ updates-archive (2022-07-27T04:18:29Z)
└─ updates-modular (2022-07-27T02:38:12Z)
Staged: no
StateRoot: fedora
GPGSignature: 1 signature
Signature made Mi 27 iul 2022 04:16:45 +0300 using RSA key ID 999F7CBF38AB71F4
Good signature from "Fedora fedora-36-primary@fedoraproject.org"
RemovedBasePackages: firefox 102.0-1.fc36
LayeredPackages: akmod-nvidia asusctl containernetworking-plugins docker-compose podman-docker
podman-plugins steam-devices supergfxctl tilix xorg-x11-drv-nvidia-cuda
xorg-x11-drv-nvidia-power xprop zsh

habeasdata404 · 2022-07-28T11:31:03Z

Ok, for everyone else did the issue begin after the 1.5.1 update or a system update? Because I find it odd that it works for me but not others.
@mattmilano If you're willing to try something out navigate to ~/.var/app/sh.cider.Cider/config/Cider/ and delete the cider-config.json file and try again. Uninstalling and reinstalling wouldn't have cleared this directory or any of its contents so it's worth a shot.

The issue began after the Cider 1.5.1 update. My other flatpaks are working fine.

Can you also try the build I posted above and report back? If that one works I'll push that to everyone.

I can't test it myself as the current one works for me already.

@rowbawts, I've just updated to 1.5.2, but the problem remains:

[13 zypak-helper] Portal v4 is not available
[08:25:20.195] [info] [AppEvents] App started
LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings
[08:25:20.575] [info] [PluginHandler] Loaded plugins: [
'chromecast.js',
'discordrpc.js',
'lastfm.js',
'menubar.js',
'mpris.js',
'raop.js',
'thumbar.js',
'webNowPlaying.js'
]
Gtk-Message: 08:25:20.673: Failed to load module "canberra-gtk-module"
Gtk-Message: 08:25:20.673: Failed to load module "canberra-gtk-module"
[0728/082520.724451:ERROR:scoped_ptrace_attach.cc(27)] ptrace: Operation not permitted (1)
[21 zypak-sandbox] Dropping 0x560dd0220300 (3) because of connection closed
[21 zypak-sandbox] Host is gone, preparing to exit...
[21 zypak-sandbox] Quitting Zygote...
/app/bin/cider-wrapper, linha 7: 13 Trace/breakpoint trap (imagem do núcleo gravada)cider "$@"

mattmilano · 2022-07-28T13:43:26Z

@rowbawts Sorry, got tied up with work and meeting yesterday and didn't get to try out the test build.

Just logged in and saw the updated to 1.5.2. Installed it and still no go.

juanejot · 2022-07-28T20:46:58Z

My experience has been similar on another Ubuntu 22.04 derivative, Linux Mint 21 beta. The latest Cider 1.5.2 still appears to work on Arch (on separate hardware). Of note, xapp won't (re?)install via apt on Linux Mint, and Arch has it installed (via pacman).

rowbawts · 2022-07-29T00:39:34Z

My experience has been similar on another Ubuntu 22.04 derivative, Linux Mint 21 beta. The latest Cider 1.5.2 still appears to work on Arch (on separate hardware). Of note, xapp won't (re?)install via apt on Linux Mint, and Arch has it installed (via pacman).

Yeah this builds confidence in my theory a newer Electron version shipped with these newer Cider builds has a bug with certain hardware/driver stacks.

What hardware are in the 2 machines?

juanejot · 2022-07-29T02:21:56Z

Yeah this builds confidence in my theory a newer Electron version shipped with these newer Cider builds has a bug with certain hardware/driver stacks.

What hardware are in the 2 machines?

The one running Arch has an i7-9700K and an RX 6600 XT. The one running Linux Mint 21 beta* has a dinosaur of a T9900 Core 2 Duo and GeForce 9400 M/9600M GT (an old MacBookPro5,3).

*As an experiment, I also installed Arch on a USB to run on the MBP5,3, and the latest version of Cider doesn't start on it, whether xapp is installed (via pacman; don't see an install candidate for flatpak) or not.

rowbawts · 2022-07-29T05:58:39Z

Yeah this builds confidence in my theory a newer Electron version shipped with these newer Cider builds has a bug with certain hardware/driver stacks.
What hardware are in the 2 machines?

The one running Arch has an i7-9700K and an RX 6600 XT. The one running Linux Mint 21 beta* has a dinosaur of a T9900 Core 2 Duo and GeForce 9400 M/9600M GT (an old MacBookPro5,3).

*As an experiment, I also installed Arch on a USB to run on the MBP5,3, and the latest version of Cider doesn't start on it, whether xapp is installed (via pacman; don't see an install candidate for flatpak) or not.

Ok yeah this goes along with what I'm thinking somehow on Nvidia the newer Electron provided with this new release is broken somehow.

Because I'm not having any issues either and I'm using a 6700 XT. But most of the people that are having issues (if not all) are reporting to be using Nvidia which most likely explains why I can't replicate it.

Can anyone with Nvidia try launching it with this command flatpak run sh.cider.Cider --disable-gpu just to see what happens.

rowbawts · 2022-07-29T06:06:10Z

Ok for everyone following this thread we are going to release a new build rolling back Electron to a previously know good release and test that. If anyone affected can help me test I would greatly appreciate it.

mattmilano · 2022-07-29T06:14:43Z

@rowbawts I can help.

Also, I don't have Nvidia. AMD with integrated Radeon graphics. So the theory that it's an Nvidia problem is not correct.

geodro · 2022-07-29T06:42:51Z

I have nvidia. still does not work

➜ ~ flatpak run sh.cider.Cider --disable-gpu
[09:42:04.374] [info] [AppEvents] App started
[09:42:04.377] [info] Hardware acceleration is disabled.
LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings
[09:42:04.533] [info] [PluginHandler] Loaded plugins: [
'chromecast.js',
'discordrpc.js',
'lastfm.js',
'menubar.js',
'mpris.js',
'raop.js',
'thumbar.js',
'webNowPlaying.js'
]
Gtk-Message: 09:42:04.567: Failed to load module "canberra-gtk-module"
Gtk-Message: 09:42:04.568: Failed to load module "canberra-gtk-module"
[0729/094204.578953:ERROR:scoped_ptrace_attach.cc(27)] ptrace: Operation not permitted (1)

juanejot · 2022-07-29T06:45:33Z

Ok yeah this goes along with what I'm thinking somehow on Nvidia the newer Electron provided with this new release is broken somehow.

Because I'm not having any issues either and I'm using a 6700 XT. But most of the people that are having issues (if not all) are reporting to be using Nvidia which most likely explains why I can't replicate it.

Can anyone with Nvidia try launching it with this command flatpak run sh.cider.Cider --disable-gpu just to see what happens.

It didn't work on my MBP5,3 under Linux Mint, but then without the GPU its rendering performance may be awful to non-existent, as a 13 year old laptop. The resulting output was as follows, which looks like that quoted above to my eye:

[23:35:29.942] [info] [AppEvents] App started
LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings
[23:35:30.619] [info] [PluginHandler] Loaded plugins: [
'chromecast.js',
'discordrpc.js',
'lastfm.js',
'menubar.js',
'mpris.js',
'raop.js',
'thumbar.js',
'webNowPlaying.js'
]
Gtk-Message: 23:35:30.672: Failed to load module "xapp-gtk3-module"
[0728/233530.940465:ERROR:scoped_ptrace_attach.cc(27)] ptrace: Operation not permitted (1)
/app/bin/cider-wrapper: line 7: 13 Trace/breakpoint trap (core dumped) cider "$@"

Gonna go try it on the same hardware under Arch now, will update only if the result is different there.

UPDATE: The only difference with the same hardware on Arch is what module it attempted to load rather than xapp-gtk3-module:

Gtk-Message: 23:51:01.617: Failed to load module "canberra-gtk-module"
Gtk-Message: 23:51:01.618: Failed to load module "canberra-gtk-module"

The rest of the lines show up the same.

rowbawts · 2022-07-29T07:11:46Z

@rowbawts I can help.

Also, I don't have Nvidia. AMD with integrated Radeon graphics. So the theory that it's an Nvidia problem is not correct.

Yeah it's definitely odd then, anyway it's really late for me now I'm going to post the test build tomorrow sometime.

Thanks for offering to help with this and being patient with this, it's only making it difficult to trace because I'm the only tester for the Flatpak releases atm and it's not an issue for me for some reason.

habeasdata404 · 2022-07-29T12:03:43Z

Yeah this builds confidence in my theory a newer Electron version shipped with these newer Cider builds has a bug with certain hardware/driver stacks.
What hardware are in the 2 machines?

The one running Arch has an i7-9700K and an RX 6600 XT. The one running Linux Mint 21 beta* has a dinosaur of a T9900 Core 2 Duo and GeForce 9400 M/9600M GT (an old MacBookPro5,3).
*As an experiment, I also installed Arch on a USB to run on the MBP5,3, and the latest version of Cider doesn't start on it, whether xapp is installed (via pacman; don't see an install candidate for flatpak) or not.

Ok yeah this goes along with what I'm thinking somehow on Nvidia the newer Electron provided with this new release is broken somehow.

Because I'm not having any issues either and I'm using a 6700 XT. But most of the people that are having issues (if not all) are reporting to be using Nvidia which most likely explains why I can't replicate it.

Can anyone with Nvidia try launching it with this command flatpak run sh.cider.Cider --disable-gpu just to see what happens.

@rowbawts, my GPU is NVIDIA GeForce GT 640M LE. The result of flatpak run sh.cider.Cider --disable-gpu:

[13 zypak-helper] Portal v4 is not available
[08:59:57.120] [info] [AppEvents] App started
LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings
[08:59:57.523] [info] [PluginHandler] Loaded plugins: [
'chromecast.js',
'discordrpc.js',
'lastfm.js',
'menubar.js',
'mpris.js',
'raop.js',
'thumbar.js',
'webNowPlaying.js'
]
Gtk-Message: 08:59:57.607: Failed to load module "canberra-gtk-module"
Gtk-Message: 08:59:57.607: Failed to load module "canberra-gtk-module"
[0729/085957.650137:ERROR:scoped_ptrace_attach.cc(27)] ptrace: Operation not permitted (1)
[21 zypak-sandbox] Dropping 0x561ab2963300 (3) because of connection closed
[21 zypak-sandbox] Host is gone, preparing to exit...
[21 zypak-sandbox] Quitting Zygote...
/app/bin/cider-wrapper, linha 7: 13 Trace/breakpoint trap (imagem do núcleo gravada)cider "$@"

I can help with the tests.

rowbawts · 2022-07-29T20:25:23Z

Here's a test build for you guys to try flatpak install --user https://dl.flathub.org/build-repo/100482/sh.cider.Cider.flatpakref

juanejot · 2022-07-29T20:58:51Z

Here's a test build for you guys to try flatpak install --user https://dl.flathub.org/build-repo/100482/sh.cider.Cider.flatpakref

On Linux Mint 21 beta on the affected MBP5,3 hardware, this version of Cider does not start by selecting the app's icon. When run from the command line with command flatpak run sh.cider.Cider [that's right, I let it use the GPU], it does successfully start up, play selected music & quit (ie. run as expected), with the following terminal output:

[13:55:12.820] [info] [AppEvents] App started

LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings
[13:55:13.183] [info] [PluginHandler] Loaded plugins: [
'chromecast.js',
'discordrpc.js',
'lastfm.js',
'menubar.js',
'mpris.js',
'raop.js',
'thumbar.js',
'webNowPlaying.js'
]
Gtk-Message: 13:55:13.195: Failed to load module "xapp-gtk3-module"
[13:55:13.418] [info] [AppEvents] App ready
[13:55:13.441] [info] [Cider] Application is Ready. Creating Window.
[13:55:13.488] [info] Setting up handlers for local files
[13:55:13.497] [info] [Connect] Auth URL: https://connect.cidercollective.dev/callback/discord?app=cider&appPort=9000
[13:55:13.593] [info] WebSocketServer started on port: 26369
[13:55:13.636] [info] [Cider][Widevine] Status: {
oimompecagnajdejgnnjijobebaeigek: {
name: 'Widevine Content Decryption Module',
status: 'new',
version: '4.10.2449.0'
}
}
[74:0729/135513.658010:ERROR:gpu_memory_buffer_support_x11.cc(44)] dri3 extension not supported.
[13:55:13.708] [info] {
auxAttributes: {
amdSwitchable: false,
canSupportThreadedTextureMailbox: false,
glResetNotificationStrategy: 0,
inProcessGpu: true,
initializationTime: 0,
isAsan: false,
jpegDecodeAcceleratorSupported: false,
optimus: false,
passthroughCmdDecoder: false,
sandboxed: false,
softwareRendering: false,
subpixelFontRendering: true,
videoDecodeAcceleratorFlags: 0,
visibilityCallbackCallCount: 0
},
gpuDevice: [
{
active: true,
cudaComputeCapabilityMajor: 0,
deviceId: 1607,
driverVendor: 'Nvidia',
driverVersion: '340.108',
vendorId: 4318
},
{
active: false,
cudaComputeCapabilityMajor: 0,
deviceId: 2147,
driverVendor: 'Nvidia',
driverVersion: '340.108',
vendorId: 4318
}
]
}
[13:55:13.710] [info] From here can you check for real changes, the initial scan has been completed.
[13:55:13.710] [info] Cider client port: 9000
[13:55:13.714] [info] Cider remote port: 6942
[13:55:13.717] [info] remote broadcasted
[13:55:16.639] [info] folders []
[13:55:45.950] [warn] Cider exited.

I'm off next to test it under Arch on the same hardware, will update with any salient differences in behavior/terminal output.

UPDATE: This new build starts, runs & quits normally from the app icon (in GNOME) on Arch, though I did see the icon "cycle" an old one out and a new one in, as I went to click on it. Running flatpak run sh.cider.Cider from the command line does not provide appreciably (to me) different output, but you're welcome to request it if you think any detail may be salient.

It might still have the issue with the icon because you still have the "stable" build installed and the icon is for some reason still triggering the "stable" one that's still installed.

I'll go back to Linux Mint 21 beta & see whether potentially a similar reload/relink of icons (in Cinnamon) allows it to run based on a click. If not & the "stable" flatpak gets updated, then I'll be happy to wait for that.

Thanks for your work & help on this!

UPDATE 2: As somewhat expected, a reboot into Linux Mint 21 beta/Cinnamon gets the icon to work. When the "stable" comes out, I'll make sure to remove the dl repo & reinstall the stable flatpak, then reboot before clicking the icon again.

rowbawts · 2022-07-29T21:08:39Z

Here's a test build for you guys to try flatpak install --user https://dl.flathub.org/build-repo/100482/sh.cider.Cider.flatpakref

On Linux Mint 21 beta on the affected MBP5,3 hardware, this version of Cider does not start by selecting the app's icon. When run from the command line with command flatpak run sh.cider.Cider [that's right, I let it use the GPU], it does successfully start up, play selected music & quit (ie. run as expected), with the following terminal output:

[13:55:12.820] [info] [AppEvents] App started

LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings
[13:55:13.183] [info] [PluginHandler] Loaded plugins: [
'chromecast.js',
'discordrpc.js',
'lastfm.js',
'menubar.js',
'mpris.js',
'raop.js',
'thumbar.js',
'webNowPlaying.js'
]
Gtk-Message: 13:55:13.195: Failed to load module "xapp-gtk3-module"
[13:55:13.418] [info] [AppEvents] App ready
[13:55:13.441] [info] [Cider] Application is Ready. Creating Window.
[13:55:13.488] [info] Setting up handlers for local files
[13:55:13.497] [info] [Connect] Auth URL: https://connect.cidercollective.dev/callback/discord?app=cider&appPort=9000
[13:55:13.593] [info] WebSocketServer started on port: 26369
[13:55:13.636] [info] [Cider][Widevine] Status: {
oimompecagnajdejgnnjijobebaeigek: {
name: 'Widevine Content Decryption Module',
status: 'new',
version: '4.10.2449.0'
}
}
[74:0729/135513.658010:ERROR:gpu_memory_buffer_support_x11.cc(44)] dri3 extension not supported.
[13:55:13.708] [info] {
auxAttributes: {
amdSwitchable: false,
canSupportThreadedTextureMailbox: false,
glResetNotificationStrategy: 0,
inProcessGpu: true,
initializationTime: 0,
isAsan: false,
jpegDecodeAcceleratorSupported: false,
optimus: false,
passthroughCmdDecoder: false,
sandboxed: false,
softwareRendering: false,
subpixelFontRendering: true,
videoDecodeAcceleratorFlags: 0,
visibilityCallbackCallCount: 0
},
gpuDevice: [
{
active: true,
cudaComputeCapabilityMajor: 0,
deviceId: 1607,
driverVendor: 'Nvidia',
driverVersion: '340.108',
vendorId: 4318
},
{
active: false,
cudaComputeCapabilityMajor: 0,
deviceId: 2147,
driverVendor: 'Nvidia',
driverVersion: '340.108',
vendorId: 4318
}
]
}
[13:55:13.710] [info] From here can you check for real changes, the initial scan has been completed.
[13:55:13.710] [info] Cider client port: 9000
[13:55:13.714] [info] Cider remote port: 6942
[13:55:13.717] [info] remote broadcasted
[13:55:16.639] [info] folders []
[13:55:45.950] [warn] Cider exited.

I'm off next to test it under Arch on the same hardware, will update with any salient differences in behavior/terminal output.

It might still have the issue with the icon because you still have the "stable" build installed and the icon is for some reason still triggering the "stable" one that's still installed.

habeasdata404 · 2022-08-02T15:15:52Z

@rowbawts, I updated to 1.5.2-beta.24, as a regular update on Flatpak, and it's working.

[13 zypak-helper] Portal v4 is not available
[12:12:45.950] [info] [AppEvents] App started
LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings
[12:12:46.318] [info] [PluginHandler] Loaded plugins: [
'chromecast.js',
'discordrpc.js',
'lastfm.js',
'menubar.js',
'mpris.js',
'raop.js',
'thumbar.js',
'webNowPlaying.js'
]
Gtk-Message: 12:12:46.394: Failed to load module "canberra-gtk-module"
Gtk-Message: 12:12:46.394: Failed to load module "canberra-gtk-module"
[12:12:46.484] [info] [AppEvents] App ready
[12:12:46.486] [info] [Cider] Application is Ready. Creating Window.
[12:12:46.510] [info] Setting up handlers for local files
[12:12:46.518] [info] [Connect] Auth URL: https://connect.cidercollective.dev/callback/discord?app=cider&appPort=9000
[12:12:46.577] [info] WebSocketServer started on port: 26369
[12:12:46.597] [info] [Cider][Widevine] Status: {
oimompecagnajdejgnnjijobebaeigek: {
name: 'Widevine Content Decryption Module',
status: 'new',
version: '4.10.2449.0'
}
}
[12:12:46.663] [info] {
auxAttributes: {
amdSwitchable: false,
canSupportThreadedTextureMailbox: false,
glResetNotificationStrategy: 0,
inProcessGpu: true,
initializationTime: 0,
isAsan: false,
jpegDecodeAcceleratorSupported: false,
optimus: true,
passthroughCmdDecoder: false,
sandboxed: false,
softwareRendering: false,
subpixelFontRendering: true,
videoDecodeAcceleratorFlags: 0,
visibilityCallbackCallCount: 0
},
gpuDevice: [
{
active: true,
cudaComputeCapabilityMajor: 0,
deviceId: 4051,
vendorId: 4318
},
{
active: false,
cudaComputeCapabilityMajor: 0,
deviceId: 358,
vendorId: 32902
}
]
}
[12:12:46.665] [info] From here can you check for real changes, the initial scan has been completed.
[12:12:46.665] [info] Cider client port: 9000
[12:12:46.668] [info] Cider remote port: 6942
[12:12:46.675] [info] remote broadcasted
libva error: /usr/lib/x86_64-linux-gnu/dri/intel-vaapi-driver/iHD_drv_video.so init failed
[57:0802/121246.871162:ERROR:sandbox_linux.cc(377)] InitializeSandbox() called with multiple threads in process gpu-process.
[12:12:50.034] [info] folders []

rowbawts · 2022-08-03T02:41:46Z

@rowbawts, I updated to 1.5.2-beta.24, as a regular update on Flatpak, and it's working.

Yeah that's the build with the reverted Electron so I guess Electron 20 has some weird bug with certain hardware configurations. Weird.

Edit: good to know it's resolved for you though!

juanejot · 2022-08-03T05:19:12Z

Yeah that's the build with the reverted Electron so I guess Electron 20 has some weird bug with certain hardware configurations. Weird.

What is the incidence of X11 vs. Wayland? I know Nvidia & Wayland don’t always mix well yet, but AMD seems fine with Wayland. Anecdotally, I think any Linux OS I’ve ever run on the MBP (with oo~old Nvidia) sticks to X11, but the newer rig (with, as above, an RX 6600 XT) automatically runs Wayland in my current configuration.
1.5.2b24 from flathub stable is working fine right now on both of them (Thanks!), but it was the old Nvidia/X11 system that had a problem, never the more current AMD/Wayland one.

rowbawts · 2022-08-03T07:31:58Z

Yeah that's the build with the reverted Electron so I guess Electron 20 has some weird bug with certain hardware configurations. Weird.

What is the incidence of X11 vs. Wayland? I know Nvidia & Wayland don’t always mix well yet, but AMD seems fine with Wayland. Anecdotally, I think any Linux OS I’ve ever run on the MBP (with oo~old Nvidia) sticks to X11, but the newer rig (with, as above, an RX 6600 XT) automatically runs Wayland in my current configuration. 1.5.2b24 from flathub stable is working fine right now on both of them (Thanks!), but it was the old Nvidia/X11 system that had a problem, never the more current AMD/Wayland one.

This is honestly something I've wanted to look into as some people have been wanting me to make Wayland the default but I honestly don't have enough resources to test a bunch of different configurations to make sure these types of changes break things on anything other than on my end. (6700XT)

ellyq · 2022-08-04T18:56:02Z

Hi, this issue really is strange.

Also running Fedora 36 with Navi 23 (RX6600XT, amdgpu) and X11 (because xsetwacom).
However, I've tested on both X11 and Wayland, no luck. Neither Flatpak or AppImage work (process doesn't die, but GUI doesn't initialize).

Newest AppImage from repo:

AppImages % ./Cider-1.5.4-beta.6_c329e6b2540dba7d69af2b5c285047d0.AppImage --trace-warnings
/usr/bin/AppImageLauncher: /lib64/libcurl.so.4: no version information available (required by /usr/bin/../lib/x86_64-linux-gnu/appimagelauncher/libappimageupdate.so)
[20:35:23.105] [info]  [AppEvents] App started
[20:35:27.637] [info]  [PluginHandler] Loaded plugins: [
  'chromecast.js',
  'discordrpc.js',
  'lastfm.js',
  'menubar.js',
  'mpris.js',
  'playbackNotifications.js',
  'raop.js',
  'thumbar.js',
  'webNowPlaying.js'
]
[20:35:27.970] [info]  [AppEvents] App ready
[20:35:27.971] [info]  [Cider] Application is Ready. Creating Window.
[20:35:28.085] [warn]  This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
[20:35:28.086] [error] Error: Update check error
[20:35:28.087] [error] (node:4464) UnhandledPromiseRejectionWarning: Error: Update check error
(Use `cider --trace-warnings ...` to show where the warning was created)
[20:35:28.087] [error] (node:4464) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 4)
[5233:0804/203528.118835:ERROR:sandbox_linux.cc(377)] InitializeSandbox() called with multiple threads in process gpu-process.
^C
[20:35:55.101] [warn]  Cider exited.

And flatpak version:

AppImages % flatpak run sh.cider.Cider                                                               
[20:51:45.574] [info]  [AppEvents] App started
LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings
[20:51:45.771] [info]  [PluginHandler] Loaded plugins: [
  'chromecast.js',
  'discordrpc.js',
  'lastfm.js',
  'menubar.js',
  'mpris.js',
  'raop.js',
  'thumbar.js',
  'webNowPlaying.js'
]
[20:51:45.844] [info]  [AppEvents] App ready
[20:51:45.844] [info]  [Cider] Application is Ready. Creating Window.
[20:51:45.897] [warn]  This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
[20:51:45.897] [error] Error: Update check error
[20:51:45.898] [error] (node:13) UnhandledPromiseRejectionWarning: Error: Update check error
(Use `cider --trace-warnings ...` to show where the warning was created)
[20:51:45.898] [error] (node:13) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 4)
[73:0804/205145.940716:ERROR:sandbox_linux.cc(377)] InitializeSandbox() called with multiple threads in process gpu-process.
^C
/app/bin/cider-wrapper: line 7:    13 Trace/breakpoint trap   (core dumped) cider "$@"

Unfortunately I can't say whether it's a new or old problem, because I just distrohopped from Gentoo.
Feel free to ask if you need any tests to isolate this issue :)

rowbawts · 2022-08-24T20:38:26Z

So I'm getting ready to release 1.5.6 on Flathub and it's using a different version of Electron again. I'd like to get some feedback from this thread before I release it to make sure we don't have a repeat issue.

You can try that build out here:
flatpak install --user https://dl.flathub.org/build-repo/104149/sh.cider.Cider.flatpakref

habeasdata404 · 2022-08-29T13:00:51Z

So I'm getting ready to release 1.5.6 on Flathub and it's using a different version of Electron again. I'd like to get some feedback from this thread before I release it to make sure we don't have a repeat issue.

You can try that build out here: flatpak install --user https://dl.flathub.org/build-repo/104149/sh.cider.Cider.flatpakref

@rowbawts, sorry for my delay, but I couldn't test Cider before.
Cider 1.5.6 is working for me on Ubuntu 22.04.1.

cryptofyre · 2022-08-29T13:01:51Z

Going to close this issue and assume this is working again then, feel free to notify me if more issues arise.

kode54 · 2022-10-06T07:02:41Z

v1.5.7-beta.230 from flathub-beta is now broken.

$ flatpak run sh.cider.Cider
[13 zypak-helper] Wait found events, but sd-event found none
[00:02:12.398] [info]  [AppEvents] App started
LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings
LaunchProcess: failed to execvp:
xdg-settings
[00:02:12.627] [info]  [PluginHandler] Loaded plugins: [
  'chromecast.js',
  'discordrpc.js',
  'lastfm.js',
  'menubar.js',
  'mpris.js',
  'playbackNotifications.js',
  'raop.js',
  'thumbar.js',
  'webNowPlaying.js'
]
[81:1006/000212.726668:ERROR:angle_platform_impl.cc(43)] Display.cpp:997 (initialize): ANGLE Display::initialize error 12289: Could not open the default X display.
ERR: Display.cpp:997 (initialize): ANGLE Display::initialize error 12289: Could not open the default X display.
[81:1006/000212.726879:ERROR:gl_display.cc(508)] EGL Driver message (Critical) eglInitialize: Could not open the default X display.
[81:1006/000212.726953:ERROR:gl_display.cc(920)] eglInitialize OpenGL failed with error EGL_NOT_INITIALIZED, trying next display type
[81:1006/000212.727044:ERROR:angle_platform_impl.cc(43)] Display.cpp:997 (initialize): ANGLE Display::initialize error 12289: Could not open the default X display.
ERR: Display.cpp:997 (initialize): ANGLE Display::initialize error 12289: Could not open the default X display.
[81:1006/000212.727112:ERROR:gl_display.cc(508)] EGL Driver message (Critical) eglInitialize: Could not open the default X display.
[81:1006/000212.727167:ERROR:gl_display.cc(920)] eglInitialize OpenGLES failed with error EGL_NOT_INITIALIZED
[81:1006/000212.727225:ERROR:gl_ozone_egl.cc(23)] GLDisplayEGL::Initialize failed.
[81:1006/000212.727688:ERROR:gpu_memory_buffer_support_x11.cc(44)] dri3 extension not supported.
[81:1006/000212.728993:ERROR:viz_main_impl.cc(186)] Exiting GPU process due to errors during initialization
[00:02:12.740] [info]  [AppEvents] App ready
[00:02:12.741] [info]  [Cider] Application is Ready. Creating Window.
[95:1006/000212.759382:ERROR:angle_platform_impl.cc(43)] Display.cpp:997 (initialize): ANGLE Display::initialize error 12289: Could not open the default X display.
ERR: Display.cpp:997 (initialize): ANGLE Display::initialize error 12289: Could not open the default X display.
[95:1006/000212.759487:ERROR:gl_display.cc(508)] EGL Driver message (Critical) eglInitialize: Could not open the default X display.
[95:1006/000212.759520:ERROR:gl_display.cc(920)] eglInitialize OpenGL failed with error EGL_NOT_INITIALIZED, trying next display type
[95:1006/000212.759563:ERROR:angle_platform_impl.cc(43)] Display.cpp:997 (initialize): ANGLE Display::initialize error 12289: Could not open the default X display.
ERR: Display.cpp:997 (initialize): ANGLE Display::initialize error 12289: Could not open the default X display.
[95:1006/000212.759636:ERROR:gl_display.cc(508)] EGL Driver message (Critical) eglInitialize: Could not open the default X display.
[95:1006/000212.759676:ERROR:gl_display.cc(920)] eglInitialize OpenGLES failed with error EGL_NOT_INITIALIZED
[95:1006/000212.759710:ERROR:gl_ozone_egl.cc(23)] GLDisplayEGL::Initialize failed.
[95:1006/000212.760113:ERROR:gpu_memory_buffer_support_x11.cc(44)] dri3 extension not supported.
[95:1006/000212.761108:ERROR:viz_main_impl.cc(186)] Exiting GPU process due to errors during initialization
[00:02:12.766] [info]  Setting up handlers for local files
[00:02:12.768] [info]  [Connect] Auth URL: https://connect.cidercollective.dev/callback/discord?app=cider&appPort=9000
[00:02:12.781] [info]  WebSocketServer started on port: 26369
[00:02:12.790] [info]  [Cider][Widevine] Status: {
  oimompecagnajdejgnnjijobebaeigek: {
    name: 'Widevine Content Decryption Module',
    status: 'new',
    version: '4.10.2449.0'
  }
}
[00:02:12.823] [info]  {
  auxAttributes: {
    amdSwitchable: false,
    canSupportThreadedTextureMailbox: false,
    glResetNotificationStrategy: 0,
    inProcessGpu: true,
    initializationTime: 0,
    isAsan: false,
    jpegDecodeAcceleratorSupported: false,
    optimus: false,
    passthroughCmdDecoder: false,
    sandboxed: false,
    softwareRendering: false,
    subpixelFontRendering: true,
    visibilityCallbackCallCount: 0
  },
  gpuDevice: [
    {
      active: true,
      cudaComputeCapabilityMajor: 0,
      deviceId: 26591,
      gpuPreference: 0,
      vendorId: 4098
    }
  ]
}
[00:02:12.824] [info]  From here can you check for real changes, the initial scan has been completed.
[00:02:12.824] [info]  Cider client port: 9000
[00:02:12.826] [info]  Cider remote port: 6942
[00:02:12.828] [info]  remote broadcasted
[127:1006/000212.844241:ERROR:angle_platform_impl.cc(43)] Display.cpp:997 (initialize): ANGLE Display::initialize error 12289: Could not open the default X display.
ERR: Display.cpp:997 (initialize): ANGLE Display::initialize error 12289: Could not open the default X display.
[127:1006/000212.844355:ERROR:gl_display.cc(508)] EGL Driver message (Critical) eglInitialize: Could not open the default X display.
[127:1006/000212.844458:ERROR:gl_display.cc(920)] eglInitialize OpenGL failed with error EGL_NOT_INITIALIZED, trying next display type
[127:1006/000212.844588:ERROR:angle_platform_impl.cc(43)] Display.cpp:997 (initialize): ANGLE Display::initialize error 12289: Could not open the default X display.
ERR: Display.cpp:997 (initialize): ANGLE Display::initialize error 12289: Could not open the default X display.
[127:1006/000212.844689:ERROR:gl_display.cc(508)] EGL Driver message (Critical) eglInitialize: Could not open the default X display.
[127:1006/000212.844759:ERROR:gl_display.cc(920)] eglInitialize OpenGLES failed with error EGL_NOT_INITIALIZED
[127:1006/000212.844824:ERROR:gl_ozone_egl.cc(23)] GLDisplayEGL::Initialize failed.
[127:1006/000212.845362:ERROR:gpu_memory_buffer_support_x11.cc(44)] dri3 extension not supported.
[127:1006/000212.846465:ERROR:viz_main_impl.cc(186)] Exiting GPU process due to errors during initialization
[143:1006/000212.857080:ERROR:angle_platform_impl.cc(43)] Display.cpp:997 (initialize): ANGLE Display::initialize error 12289: Could not open the default X display.
ERR: Display.cpp:997 (initialize): ANGLE Display::initialize error 12289: Could not open the default X display.
[143:1006/000212.857174:ERROR:gl_display.cc(508)] EGL Driver message (Critical) eglInitialize: Could not open the default X display.
[143:1006/000212.857204:ERROR:gl_display.cc(920)] eglInitialize OpenGL failed with error EGL_NOT_INITIALIZED, trying next display type
[143:1006/000212.857247:ERROR:angle_platform_impl.cc(43)] Display.cpp:997 (initialize): ANGLE Display::initialize error 12289: Could not open the default X display.
ERR: Display.cpp:997 (initialize): ANGLE Display::initialize error 12289: Could not open the default X display.
[143:1006/000212.857277:ERROR:gl_display.cc(508)] EGL Driver message (Critical) eglInitialize: Could not open the default X display.
[143:1006/000212.857303:ERROR:gl_display.cc(920)] eglInitialize OpenGLES failed with error EGL_NOT_INITIALIZED
[143:1006/000212.857328:ERROR:gl_ozone_egl.cc(23)] GLDisplayEGL::Initialize failed.
[143:1006/000212.857650:ERROR:gpu_memory_buffer_support_x11.cc(44)] dri3 extension not supported.
[143:1006/000212.858306:ERROR:viz_main_impl.cc(186)] Exiting GPU process due to errors during initialization
[154:1006/000212.872740:ERROR:gl_display.cc(508)] EGL Driver message (Error) eglCreateContext: Requested GLES version (3.0) is greater than max supported (2, 0).
[154:1006/000212.872819:ERROR:gl_context_egl.cc(371)] eglCreateContext failed with error EGL_SUCCESS
[154:1006/000212.873732:ERROR:vaapi_wrapper.cc(832)] Could not get a valid VA display
[154:1006/000212.874792:ERROR:gpu_memory_buffer_support_x11.cc(44)] dri3 extension not supported.
[154:1006/000212.937725:ERROR:x11_software_bitmap_presenter.cc(142)] XGetWindowAttributes failed for window 1
[116:1006/000212.940692:ERROR:command_buffer_proxy_impl.cc(128)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.

rowbawts · 2022-10-06T07:33:55Z

Edit: Flatpaks were broken due to Wayland issues I removed it on beta and master and they should be working now.

LiamDawe added bug Something isn't working needs-triage Awaiting triage. labels Jul 27, 2022

coredev-uk added release: Flatpak Issues known to occur on the Flatpak release of Cider. and removed needs-triage Awaiting triage. labels Aug 3, 2022

coredev-uk assigned rowbawts Aug 3, 2022

cryptofyre closed this as completed Aug 29, 2022

[Bug]: Flatpak on Pop!_OS Linux is broken #1324

[Bug]: Flatpak on Pop!_OS Linux is broken #1324

Comments

LiamDawe commented Jul 27, 2022

Describe the Bug

Steps to Reproduce

Environment Information

Anything else?

Code of Conduct

habeasdata404 commented Jul 27, 2022

geodro commented Jul 27, 2022

streetsamurai00mi commented Jul 27, 2022

vapormusic commented Jul 27, 2022

rowbawts commented Jul 27, 2022 • edited

rowbawts commented Jul 27, 2022

mattmilano commented Jul 27, 2022

rowbawts commented Jul 27, 2022

rowbawts commented Jul 27, 2022 • edited

mattmilano commented Jul 27, 2022

rowbawts commented Jul 27, 2022

habeasdata404 commented Jul 28, 2022

rowbawts commented Jul 28, 2022 • edited

geodro commented Jul 28, 2022 • edited

habeasdata404 commented Jul 28, 2022

mattmilano commented Jul 28, 2022

juanejot commented Jul 28, 2022

rowbawts commented Jul 29, 2022 • edited

juanejot commented Jul 29, 2022 • edited

rowbawts commented Jul 29, 2022

rowbawts commented Jul 29, 2022

mattmilano commented Jul 29, 2022

geodro commented Jul 29, 2022

juanejot commented Jul 29, 2022 • edited

rowbawts commented Jul 29, 2022 • edited

habeasdata404 commented Jul 29, 2022

rowbawts commented Jul 29, 2022

juanejot commented Jul 29, 2022 • edited

rowbawts commented Jul 29, 2022

habeasdata404 commented Aug 2, 2022

rowbawts commented Aug 3, 2022 • edited

juanejot commented Aug 3, 2022

rowbawts commented Aug 3, 2022

ellyq commented Aug 4, 2022

rowbawts commented Aug 24, 2022

habeasdata404 commented Aug 29, 2022

cryptofyre commented Aug 29, 2022

kode54 commented Oct 6, 2022

rowbawts commented Oct 6, 2022 • edited

rowbawts commented Jul 27, 2022 •

edited

rowbawts commented Jul 27, 2022 •

edited

rowbawts commented Jul 28, 2022 •

edited

geodro commented Jul 28, 2022 •

edited

rowbawts commented Jul 29, 2022 •

edited

juanejot commented Jul 29, 2022 •

edited

juanejot commented Jul 29, 2022 •

edited

rowbawts commented Jul 29, 2022 •

edited

juanejot commented Jul 29, 2022 •

edited

rowbawts commented Aug 3, 2022 •

edited

rowbawts commented Oct 6, 2022 •

edited