I'm running Ubuntu 23.10 on a I9 cpu + Nvidia Geforce RTX 2080 ti and the driver 545 right now. Everything works great,but not snap. I've tried to remove it as soon as I have installed Ubuntu from scratch,but something went wrong and now I see the following errors during boot : /var/lib/snapd/snaps/bare_5.snap: Can't open blockdev /var/lib/snapd/snaps/core22_607.snap: Can't open blockdev /var/lib/snapd/snaps/core22_864.snap: Can't open blockdev /var/lib/snapd/snaps/firefox_2517.snap: Can't open blockdev /var/lib/snapd/snaps/firmware-updater_109.snap: Can't open blockdev /var/lib/snapd/snaps/gnome-42-2204_141.snap: Can't open blockdev /var/lib/snapd/snaps/gnome-42-2204_87.snap: Can't open blockdev /var/lib/snapd/snaps/gtk-common-themes_1535.snap: Can't open blockdev /var/lib/snapd/snaps/snap-store_1046.snap: Can't open blockdev /var/lib/snapd/snaps/snap-store_959.snap: Can't open blockdev /var/lib/snapd/snaps/snapd_18933.snap: Can't open blockdev /var/lib/snapd/snaps/snapd_20290.snap: Can't open blockdev /var/lib/snapd/snaps/snapd-desktop-integration_83.snap: Can't open blockdev Anyway,snap seems to work ok (because I've reinstalled it with the purpose to remove it again when I was able to fix the errors) : # snap list Name Version Rev Tracking Publisher Notes core 16-2.60.4 16202 latest/stable canonical✓ core hello-world 6.4 29 latest/stable canonical✓ - What I want to do really is to remove snap totally,including the errors that you see above. I tried different approaches,but none worked,errors keep coming back.

My ambition is to reinstall my system and then, in the fresh installation, restore the home-folder of my current main-user from its backup created with borg. But before I boot the live USB stick, format the drive to commence this, I thought that I first wanted to make sure that I will be able to properly access my firefox profile as well as my mail profiles in thunderbird. In preparation I created a new user, let's call it user2 in possession of its' own /home/-folder and set up the file permissions between main-user and user2 such that I can create backups through the user2-account into that user's home-folder of files and folders owned by my actual main-user-account. (because they both are in group borg and chown -R 750 ... and chown -R 770 ... respectively) But NOW to solutions for my actual problem. My approach was to simply try to copy the firefox profile folder in /home/main-user/firefox/current/ to /home/user1/firefox/current/ with rsync and adjust the profile.ini file accordingly. This doesn't work with the sandboxing of the /snap-directory very well obviously ! Either snapd seems to prevent these sort of things as the folder is only a SquashFS mountpoint for stuff that is actually maintained in /var/lib/snapd/snaps/ Through issuing readlink /home/main-user/snap/firefox/current I found out that the firefox version in current points to the 3779-Version and thus probably either to /home/main-user/snap/firefox/3779 or to /var/lib/snapd/snaps/firefox_3779.snap (as mount source or something?) Could you please tell me how I properly get my current firefox profile to work in another snap sandbox / mounted package either after re-installation or simply because I want in another user's /home/userX/snap/ directory ? Big Thanks

I have an Ubuntu 22.04 node, which used to have lxd v5 installed through snap. It used to have 3 containers, at the moment of remove the lxd using the snap remove lxd it did take a snapshot of all the containers , but when I try to import those snapshoted containers I got some errors. First, the snapshots were deliver to me in .zip format, which when I try to import using the lxc import file_name.zip I get the *Importing instance: 100% (108.71MB/s)Error: Unsupported compression* error, weird because as I pointed I got the snapshots in .zip format. So I needed to extract it and then compress it again using tar (tar -czvf containers.tar.gz file_contains_extracteds/) Once I got the correct format, then I try to import it, but I get the following error: lxc import containers.tar.gz Importing instance: 100% (701.66MB/s)Error: Backup is missing at "backup/index.yaml" When I look into the extracted .zip file I get: ls 25112 archive.tgz common meta.json meta.sha3_384 user And inside the common there are all the container's folder: ls common/lxd/storage-pools/default/containers/ monitor orch1 vrouter How can I import lxc containers back from the snapshots the lxc create just before the lxc snap is removed?

I'm running Visual Studio Code on Ubuntu, installed as a Snap package. If I open the terminal in Visual Studio Code and use it to run a podman container - everything works fine, except that if I run podman on a local terminal, it doesn't see anything running:

$ podman ps -aq | wc -l
0

I can see the processes running in ps, with my user ID:

$ ps auxfw
...
odeda      39121  0.0  0.0  12216  2724 ?        Ss   10:16   0:00  \_ /usr/bin/conmon --api-version 1 -c 7cd9293c0ed384bbebda322d366cefa2890502be3ca
odeda      39123  0.0  0.0  11444  6720 pts/0    Ss+  10:16   0:00  |   \_ nginx: master process nginx -g daemon off;
100100     39156  0.0  0.0  11912  3204 pts/0    S+   10:16   0:00  |       \_ nginx: worker process
100100     39157  0.0  0.0  11912  2884 pts/0    S+   10:16   0:00  |       \_ nginx: worker process
...

And I can see the storage files for podman in the Snap's tree:

ls -la ~/snap/code/current/.local/share/containers/storage/overlay-containers/
total 8
drwx------ 1 odeda odeda 206 Dec 27 10:16 .
drwx------ 1 odeda odeda 236 Dec 27 10:36 ..
drwx------ 1 odeda odeda  16 Dec 27 10:16 7cd9293c0ed384bbebda322d366cefa2890502be3caa60854207968a31d4bf08
-rw-r--r-- 1 odeda odeda  64 Dec 27 10:16 containers.lock
-rw------- 1 odeda odeda 533 Dec 27 10:16 volatile-containers.json

I want to work on the running container using podman exec and such - but the podman on the host doesn't see the container:

$ podman exec -ti somecontainer /bin/bash
Error: no container with name or ID "somecontainer" found: no such container

I can run such things fine from the Visual Studio Code's terminal view - but as it is otherwise pretty terrible for serious terminal work, I'd rather not. I'm guessing this is an artifact of the Snap containment. How do I tell the host's podman to see the podman inside the Snap containment?

My PC fails to run snap packages, when I try I get: 2021/07/31 20:56:38.255535 cmd_run.go:576: WARNING: XAUTHORITY environment value is not a clean path: "/mnt/e664d184-8567-4278-93ce-c986567c66af/home/iaquobe/.Xauthority" cannot create user data directory: /home/iaquobe/snap/shapezio/2: Not a directory The directories do however exist. So far the packages I tested are 0ad shapezio whatsdesk, all of them had the same issue. Those packages do run on my laptop. One thing that is different is that on my PC /home/iaquobe is a symbolic link to a drive at /mnt/[...]/home. This is the only cause for this error I could think of, what do you think? And what could I do to fix it? Thanks in advance :)

I'm trying to use sshfs to open a remote directory in the Spotify snap application on Linux Mint. sshfs -o allow_other user@example.com:/remote/dir /local/dir I've mounted my directory using the "allow_other" fuse option, and the directory opens without having to use sudo in terminal and file explorer. However, when I try adding it as a directory in Spotify for local files, the file explorer gives me this message: Any advice on fixing this? I've tried modifying the permissions of the folder and "default_permissions" option, no luck yet.

So I was trying to debug some stuff, and noticed that my snap installation of Discord seems to fill my kernel ring buffer with the same request which is being "DENIED" by the AppArmor. Message in question:

[ 1044.201470] audit: type=1400 audit(1732616387.440:44954): apparmor="DENIED" operation="ptrace" class="ptrace" profile="snap.discord.discord" pid=5626 comm="Utils" requested_mask="read" denied_mask="read" peer="unconfined"
[ 1044.201478] audit: type=1400 audit(1732616387.440:44955): apparmor="DENIED" operation="ptrace" class="ptrace" profile="snap.discord.discord" pid=5626 comm="Utils" requested_mask="read" denied_mask="read" peer="unconfined"
[ 1044.201491] audit: type=1400 audit(1732616387.440:44956): apparmor="DENIED" operation="ptrace" class="ptrace" profile="snap.discord.discord" pid=5626 comm="Utils" requested_mask="read" denied_mask="read" peer="unconfined"
[ 1044.201499] audit: type=1400 audit(1732616387.440:44957): apparmor="DENIED" operation="ptrace" class="ptrace" profile="snap.discord.discord" pid=5626 comm="Utils" requested_mask="read" denied_mask="read" peer="unconfined"
[ 1044.201514] audit: type=1400 audit(1732616387.440:44958): apparmor="DENIED" operation="ptrace" class="ptrace" profile="snap.discord.discord" pid=5626 comm="Utils" requested_mask="read" denied_mask="read" peer="unconfined"
[ 1044.201522] audit: type=1400 audit(1732616387.440:44959): apparmor="DENIED" operation="ptrace" class="ptrace" profile="snap.discord.discord" pid=5626 comm="Utils" requested_mask="read" denied_mask="read" peer="unconfined"
[ 1044.201535] audit: type=1400 audit(1732616387.440:44960): apparmor="DENIED" operation="ptrace" class="ptrace" profile="snap.discord.discord" pid=5626 comm="Utils" requested_mask="read" denied_mask="read" peer="unconfined"

(the spam is at a point where its very difficult to find any message which isn't this one...) I was wondering if people know what might cause this, and if this is harmful behaviour I should seek to fix (my machine has been a bit unstable, but I'm still unsure if that's a hardware or a software issue...)

I have quite basic knowledge regarding my goal. I have both apache2 installed on port 80, and Nextcloud installed on port 82. At the moment I can access "Apache2 Default Page" at 10.1.1.171, and I can access Nextcloud at 10.1.1.171:82. What I would like to do on the home network is enter "nextcloud"or "nextcloud.local", or whatever, into a browser, and be directed to 10.1.1.171:82. I have the following code as a template

ServerName your_domain.com  # Replace with your domain name
    ServerAlias www.your_domain.com

    ProxyPass / http://your_nextcloud_ip:your_nextcloud_port/ 
    ProxyPassReverse / http://your_nextcloud_ip:your_nextcloud_port/ 

    ProxyPreserveHost On
    ProxyPassReverseCookiePath /

    
        Require all granted

and I have modified the easy bits so I now looks like

ServerName your_domain.com  # Replace with your domain name
    ServerAlias www.your_domain.com

    ProxyPass / http://10.1.1.171:82/ 
    ProxyPassReverse / http://10.1.1.171:82/ 

    ProxyPreserveHost On
    ProxyPassReverseCookiePath /

    
        Require all granted

but I can go no further, without help. I don't know what "your_domain.com" should be replaced with given that it is only a local network. I assume that the working code should be placed in /etc/apache2/sites-available and then enabled, but I have been wrong before. Thanks.

I was dual booting Bazzite (Fedora Atomic) and PopOS on my laptop and would always get to each of the login screens in seconds. Never actually checked it, but I'm sure it was like 5-10s. Today after deleting the Bazzite partitions (as the one game I play started crashing there for some reason), the time to login screen was alarmingly slow.

das@pop-os:~$ systemd-analyze
Startup finished in 4.479s (firmware) + 672ms (loader) + 9.313s (kernel) + 1min 34.944s (userspace) = 1min 49.410s 
graphical.target reached after 1min 34.932s in userspace

Below are some more details I have seen people in similar situations provide. snapd appears to have something to do with it.

das@pop-os:~$ systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.

graphical.target @1min 34.932s
└─multi-user.target @1min 34.932s
  └─virtualbox.service @1min 34.858s +73ms
    └─network-online.target @1min 34.841s
      └─NetworkManager-wait-online.service @1min 30.773s +4.068s
        └─NetworkManager.service @1min 30.695s +73ms
          └─basic.target @1min 30.668s
            └─dbus-broker.service @1min 30.608s +56ms
              └─dbus.socket @1min 30.588s
                └─sysinit.target @1min 30.580s
                  └─snapd.apparmor.service @1.254s +75ms
                    └─apparmor.service @1.157s +79ms
                      └─local-fs.target @1.086s
                        └─run-snapd-ns-cups.mnt.mount @1min 31.179s
                          └─run-snapd-ns.mount @1min 31.077s
                            └─local-fs-pre.target @530ms
                              └─systemd-tmpfiles-setup-dev.service @515ms +15ms
                                └─systemd-sysusers.service @497ms +16ms
                                  └─systemd-remount-fs.service @469ms +26ms
                                    └─systemd-journald.socket @439ms
                                      └─-.mount @422ms
                                        └─-.slice @422ms

das@pop-os:~$ snap version
snap    2.65.3+22.04
snapd   2.65.3+22.04
series  16
pop     22.04
kernel  6.9.3-76060903-generic

das@pop-os:~$ lsblk
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
loop0         7:0    0     4K  1 loop /snap/bare/5
loop1         7:1    0  74.2M  1 loop /snap/core22/1621
loop2         7:2    0  73.9M  1 loop /snap/core22/1663
loop3         7:3    0  67.8M  1 loop /snap/cups/1058
loop4         7:4    0  67.8M  1 loop /snap/cups/1067
loop5         7:5    0 505.1M  1 loop /snap/gnome-42-2204/176
loop6         7:6    0  91.7M  1 loop /snap/gtk-common-themes/1535
loop7         7:7    0  38.8M  1 loop /snap/snapd/21759
loop8         7:8    0  44.1M  1 loop /snap/snapd/22991
zram0       251:0    0   7.6G  0 disk [SWAP]
nvme0n1     259:0    0 465.8G  0 disk 
├─nvme0n1p1 259:1    0  1022M  0 part /boot/efi
├─nvme0n1p2 259:2    0     4G  0 part /recovery
└─nvme0n1p3 259:3    0 460.8G  0 part /

dmesg output

Whenever I try to download anything, for instance, yay -S visual-studio-code-bin, it returns the following error

warning: database file for 'snapd' does not exist (use '-Sy' to download)
error: failed to prepare transaction (could not find database)
 -> Failed to install layer, rolling up to next layer.error:error installing repo packages
warning: database file for 'snapd' does not exist (use '-Sy' to download)
error: failed to prepare transaction (could not find database)
 -> error installing repo packages
error installing repo packages"

Then I try to install snapd:

$ sudo pacman -Sy
:: Synchronizing package databases...
 core                                                                                           116.7 KiB   120 KiB/s 00:01 [###########################################################################] 100%
 extra                                                                                            7.5 MiB  1353 KiB/s 00:06 [###########################################################################] 100%
 snapd.db failed to download
error: failed retrieving file 'snapd.db' from dl-cdn.alpin : Could not resolve host: dl-cdn.alpin
warning: fatal error from dl-cdn.alpin, skipping for the remainder of this transaction
error: failed to synchronize all databases (failed to retrieve some files)

The issue seems to be with dl-cdn.alpin, and chatgpt suggests a network issue, which isn't the problem, neither is DNS or any sort of firewall. It also suggests a change in mirror, but I don't really know how to do that. What am I doing wrong? Last time I posted this problem I articulated it poorly and didn't give enough information, I apologize for that. If there are any other clarifications I will try to answer asap.

I've only just got Arch Linux and hyprland. Anytime I try to sudo install just about anything, in this case vscode, it gives me this error:

snapd.db failed to download
error: failed retrieving file 'snapd.db' from dl-cdn.alpin : Could not resolve host: dl-cdn.alpin
warning: fatal error from dl-cdn.alpin, skipping for the remainder of this transaction
error: failed to synchronize all databases (failed to retrieve some files)

I just did an upgrade (using Software Updater) from UbuntuMATE 20.04 to 22.04. Linux hostname 5.15.0-113-generic #123-Ubuntu SMP Mon Jun 10 08:16:17 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux Firefox 128.0 (64-bit) Mozilla Firefox Snap for Ubuntu canonical-002 - 1.0 I have not managed to open any HTML page saved to local directory outside of user's SNAP tree. To reproduce the bug, do the following: mkdir /tmp/Downloads2 PATH1="${HOME}" PATH2="${HOME}/snap/firefox/common/" cd "${PATH1}" ln -s /tmp/Downloads2 Downloads2 ls -lLd Downloads2 # lrwxrwxrwx 1 ericthered ericthered 15 Jul 16 16:06 Downloads2 -> /tmp/Downloads2 # drwxr-x--- 2 ericthered ericthered 4096 Jul 16 15:51 Downloads2 cd "${PATH2}" ln -s /tmp/Downloads2 Downloads2 ls -lLd Downloads2 # lrwxrwxrwx 1 ericthered ericthered 15 Jul 16 15:52 Downloads2 -> /tmp/Downloads2 # drwxr-x--- 2 ericthered ericthered 4096 Jul 16 15:51 Downloads2 (same as from ${HOME} directory) **Open SNAP Firefox**. Open the **Settings tab** and navigate to: General / Files and Applications / Downloads **Attempt #1**: Click on the "Browse" button to work thru the PATH2 directories to make that selection of "**Downloads2**" (image of path progress in selection window) (image of path displayed after selection confirmed) *As you can all agree*, **there is a discrepancy here** regarding what I expect to see, namely the path as selected using the "browse directory tree" tool. In another tab, Open URL: https://en.wikipedia.org/wiki/Polaris Select the option to save that page to disk. **NOTE:** The path presented as the destination **is NOT** the path selected for the Downloads destination: (image of path offered at time of save-to-disk) Saving to that location does not seem to make the file available (unable to locate that file). (image of "Save As" dialog for full system path location) (image of Caja listing showing saved file in Downloads2) Exit Firefox browser. Restart Firefox browser. Visually confirm the previous selection for the default Downloads destination is still the same as before. Open the Caja window and display the Downloads2 folder contents. Double-click on the file saved above. Firefox reports an error that the file is not found: **WHY** is that happening ??? **WHAT** do I need to do to fix it ??? I **need** to be able to open/read all the previously saved HTML files that I have stored on disk across 7 other partitions! I hope I don't have to reinstall the new OS from scratch. There was NO error during the install or startup of Firefox as SNAP, so I don't see the need to do that. The behaviour **seems** like there is a Firefox setting that is **restricting use of pages outside of the "scope" of the personal snap tree** for Firefox. Not sure why such a setting would even be required. I don't believe that it is relevant, because the problem existed before I "reclaimed" my old Firefox profile for use under the SNAP installation, but here is what I did, a straight "swap" of the directories using the sequence outline here and using tar to replicate under the personal SNAP tree.

After upgrading to Ubuntu 24.04 two extra users appeared on my login screen: snap_daemon and snapd-range-524288-root It seems like this is an error of sorts and they are not supposed to be there. My "Settings" is very slow to open, System->Users shows some error and almost crashes, so I can't remove them from here. I also fear that snap will break if I remove them using userdel from the terminal. Do you know if it is safe to remove those users?

I wrote a script that generates a PDF and an HTML file on RAM-disk: - The PDF file can be opened as expected. - The HTML file can be opened with an editor, but not with a browser. This is the error message I get from the browser (Chrome, Firefox) on Ubuntu Linux 24.04: Access to the file was denied The file at file:///dev/shm/test.html is not readable. It may have been removed, moved or file permissions may be preventing access. ERR_ACCESS_DENIED These are the file details: /dev/shm> ll -rw-rw-r-- 1 11K 2024-08-30 11:06 test.html If I copy the file to the hard disk, it can be opened as expected: /dev/shm> cp ./test.html ~ ------- If I build Chromium from source as explained here , will I be able to open files stored on RAM-disk like /dev/shm?

I run **Ubuntu 20.04 LTS** on an **HP Elitebook 8460P** with 8GB RAM and 250GB HDD storage space. I use **Proton VPN** and login after Ubuntu boots to my desktop. (I have the Kill switch set to the *Advanced* setting so that my WIFI will not connect to the internet if the VPN is not running or is disconnected.) Immediately afterward the ***Livepatch shield*** symbol displays a red exclamation point, and an error message that says *error loading updates*. When I check the SNAP STORE from the ~Ubuntu Software~ "installed" list, it's blank! Once I have been on-line for 10-20 minutes, the ***Livepatch shield*** symbol displays a green checkmark... BUT I am still unable to see a list of my "installed" apps or see a list of apps that I can "Explore". Is the problem seeing these files listed/available because "Ubuntu Pro" is enabled through the Software & Updates app that comes with Ubuntu 20.04 LTS? I hope this is enough info to help answer my questions. Thank you Will Black

I am trying to install flutter on Manjaro but am receiving the following error from the pamac gui: (null): cannot install "flutter": classic confinement requires snaps under /snap or symlink from

This is after installation using apt-get on my Raspberry Pi 4B running Debian Bookworm:

root@rpi4:/root# apt-cache policy snapd
snapd:
  Installed: 2.57.6-1+b5
  Candidate: 2.57.6-1+b5
  Version table:
 *** 2.57.6-1+b5 500
        500 http://deb.debian.org/debian  bookworm/main arm64 Packages
        100 /var/lib/dpkg/status

and this is the output from my Linux Mint 21.3 Cinnamon:

$ apt-cache policy snapd
snapd:
  Installed: 2.45.1+20.04
  Candidate: (none)
  Version table:
     2.63+22.04 -10
        500 http://archive.ubuntu.com/ubuntu  jammy-updates/main amd64 Packages
     2.58+22.04.1 -10
        500 http://security.ubuntu.com/ubuntu  jammy-security/main amd64 Packages
     2.55.3+22.04 -10
        500 http://archive.ubuntu.com/ubuntu  jammy/main amd64 Packages
 *** 2.45.1+20.04 -10
        100 /var/lib/dpkg/status

$ sudo apt-get install snapd
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package snapd is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'snapd' has no installation candidate

Is there some problem which needs to be addressed on my Mint, or there is some possibly transient error?

I am trying to install snap on my rhel 8.4 machine and it throws the following error Error: Problem: package snapd-2.54.1-1.el8.x86_64 requires snapd-selinux = 2.54.1-1.el8, but none of the providers can be installed - conflicting requests - nothing provides selinux-policy-base >= 3.14.3-80.el8_5.2 needed by snapd-selinux-2.54.1-1.el8.noarch I have selinux-policy-3.14.3-67.el8_4.2 on my machine.

After successfully installing the latest Ubuntu Linux, I am having issues installing more programs, e.g. VS Codium and more. This is what happens: > sudo snap install codium --classic snap "codium" is already installed, see 'snap help refresh' > /snap/bin/codium Nothing happens when I launch the installed program. I just get the prompt back after a fraction of a second. No error messages. > ll /snap/bin/codium lrwxrwxrwx 1 13 2024-06-13 11:37 /snap/bin/codium -> /usr/bin/snap* The file is a link to a common snap file. I make a search for "codium" of my whole system, and I find a few more interesting files: /snap/codium/394/usr/share/codium/codium /snap/codium/394/usr/share/codium/bin/codium None of them works. This is what I get from the type and readlink commands: > type -a codium codium is /snap/bin/codium > readlink -f $(which codium) /usr/bin/snap What does this mean? Is it a bug or am I doing anything wrong? Thank you. OS: Ubuntu Linux 24.04 ------------------ Running codium in verbose mode I get plenty of interesting info: ~> codium --verbose Gtk-Message: 15:49:25.662: Failed to load module "colorreload-gtk-module" [153343:0614/154925.672591:ERROR:proxy_config_service_linux.cc(620)] inotify_init failed: Too many open files (24) [153343:0614/154925.672752:ERROR:file_path_watcher_inotify.cc(315)] inotify_init() failed: Too many open files (24) [153343:0614/154925.695972:WARNING:bluez_dbus_manager.cc(248)] Floss manager not present, cannot set Floss enable/disable. [153372:0614/154925.715262:ERROR:file_path_watcher_inotify.cc(315)] inotify_init() failed: Too many open files (24) libGL error: MESA-LOADER: failed to open radeonsi: /usr/lib/dri/radeonsi_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri) libGL error: failed to load driver: radeonsi libGL error: MESA-LOADER: failed to open radeonsi: /usr/lib/dri/radeonsi_dri.so: cannot open shared object file: No such file or directory (search paths /usr/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:/usr/lib/dri, suffix _dri) libGL error: failed to load driver: radeonsi ... [153365:0614/154925.788326:ERROR:viz_main_impl.cc(196)] Exiting GPU process due to errors during initialization [main 2024-06-14T14:49:25.787Z] args: { _: [], diff: false, merge: false, add: false, goto: false, 'new-window': false, 'reuse-window': false, wait: false, help: false, 'list-extensions': false, 'show-versions': false, 'pre-release': false, 'update-extensions': false, version: false, verbose: true, status: false, 'prof-startup': false, 'no-cached-data': false, 'prof-v8-extensions': false, 'disable-extensions': false, 'disable-gpu': false, 'disable-chromium-sandbox': false, sandbox: false, telemetry: false, debugRenderer: false, 'enable-smoke-test-driver': false, logExtensionHostCommunication: false, 'skip-release-notes': false, 'skip-welcome': false, 'disable-telemetry': false, 'disable-updates': false, 'use-inmemory-secretstorage': false, 'disable-workspace-trust': false, 'disable-crash-reporter': false, 'skip-add-to-recently-opened': false, 'open-url': false, 'file-write': false, 'file-chmod': false, force: false, 'do-not-sync': false, trace: false, 'preserve-env': false, 'force-user-env': false, 'force-disable-user-env': false, 'open-devtools': false, 'disable-gpu-sandbox': false, '__enable-file-policy': false, 'enable-coi': false, 'no-proxy-server': false, 'no-sandbox': false, nolazy: false, 'force-renderer-accessibility': false, 'ignore-certificate-errors': false, 'allow-insecure-localhost': false, 'disable-dev-shm-usage': false, 'profile-temp': false, logsPath: '/home/pietrom/.config/VSCodium/logs/20240614T154925' } [main 2024-06-14T14:49:25.788Z] Resolving machine identifier... [main 2024-06-14T14:49:25.789Z] Resolved machine identifier: 5d824ba39346432401d759b3964a6149554e3b747050fb1498b8010fd55e2862 [main 2024-06-14T14:49:25.789Z] Main->SharedProcess#connect [main 2024-06-14T14:49:25.797Z] StorageMainService: creating application storage [main 2024-06-14T14:49:25.798Z] update#setState idle [main 2024-06-14T14:49:25.799Z] Error: EMFILE: too many open files, watch '/snap/codium' at FSWatcher. (node:internal/original-fs/watchers:247:19) at watch (node:original-fs:2418:34) at new g (/snap/codium/394/usr/share/codium/resources/app/out/vs/code/electron-main/main.js:109:56471) at b._createInstance (/snap/codium/394/usr/share/codium/resources/app/out/vs/code/electron-main/main.js:57:2092) at b._createServiceInstance (/snap/codium/394/usr/share/codium/resources/app/out/vs/code/electron-main/main.js:57:5374) at b._createServiceInstanceWithOwner (/snap/codium/394/usr/share/codium/resources/app/out/vs/code/electron-main/main.js:57:4226) at b._createAndCacheServiceInstance (/snap/codium/394/usr/share/codium/resources/app/out/vs/code/electron-main/main.js:57:3894) at b._safeCreateAndCacheServiceInstance (/snap/codium/394/usr/share/codium/resources/app/out/vs/code/electron-main/main.js:57:3035) at b._getOrCreateServiceInstance (/snap/codium/394/usr/share/codium/resources/app/out/vs/code/electron-main/main.js:57:2756) at Object.get (/snap/codium/394/usr/share/codium/resources/app/out/vs/code/electron-main/main.js:57:1129) at ft.initChannels (/snap/codium/394/usr/share/codium/resources/app/out/vs/code/electron-main/main.js:110:86205) at /snap/codium/394/usr/share/codium/resources/app/out/vs/code/electron-main/main.js:110:73357 at b.invokeFunction (/snap/codium/394/usr/share/codium/resources/app/out/vs/code/electron-main/main.js:57:999) at ft.startup (/snap/codium/394/usr/share/codium/resources/app/out/vs/code/electron-main/main.js:110:73333) at async Ee.startup (/snap/codium/394/usr/share/codium/resources/app/out/vs/code/electron-main/main.js:112:1436) [main 2024-06-14T14:49:25.800Z] Lifecycle#kill() [main 2024-06-14T14:49:25.800Z] Lifecycle#onWillShutdown.fire() [main 2024-06-14T14:49:25.800Z] Lifecycle#onWillShutdown - begin 'instanceLockfile' [main 2024-06-14T14:49:25.800Z] storageMainService#onWillShutdown() [main 2024-06-14T14:49:25.800Z] Lifecycle#onWillShutdown - begin 'applicationStorage' [main 2024-06-14T14:49:25.800Z] StorageMainService: closed application storage [main 2024-06-14T14:49:25.800Z] Lifecycle#onWillShutdown - end 'applicationStorage' [main 2024-06-14T14:49:25.801Z] Lifecycle#onWillShutdown - end 'instanceLockfile' [main 2024-06-14T14:49:25.801Z] [File Watcher (node.js)] Failed to watch /home/pietrom/.config/VSCodium/User for changes using fs.watch() (Error: EMFILE: too many open files, watch '/home/pietrom/.config/VSCodium/User') [main 2024-06-14T14:49:25.802Z] [File Watcher (node.js)] Request to stop watching: /home/pietrom/.config/VSCodium/User (excludes: , includes: , filter: , correlationId: ),/home/pietrom/.config/VSCodium/User/settings.json (excludes: , includes: , filter: , correlationId: ) [main 2024-06-14T14:49:25.802Z] [File Watcher (node.js)] stopping file watcher (/home/pietrom/.config/VSCodium/User (excludes: , includes: , filter: , correlationId: )) [main 2024-06-14T14:49:25.802Z] [File Watcher (node.js)] stopping file watcher (/home/pietrom/.config/VSCodium/User/settings.json (excludes: , includes: , filter: , correlationId: ))

I've been using Kubuntu with Snap for quite a while and no bigger issues so far. Today all my snap apps stopped launching, reporting the following error:

/user.slice/user-1000.slice/session-3.scope is not a snap cgroup

How can I fix this?