[Touch-packages] [Bug 2056517] Re: VS Code profile still broken.
A similar issue is found in Foliate ebook reader in Ubuntu 24.04 https://github.com/johnfactotum/foliate/issues/1262 ** Bug watch added: Bug tracker for Foliate #1262 https://github.com/johnfactotum/foliate/issues/1262 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2056517 Title: VS Code profile still broken. Status in apparmor package in Ubuntu: Confirmed Bug description: Ubuntu 24.04, VSCode installed via their repo (https://packages.microsoft.com/repos/code) Some updates ago apparmor gained an exception for /usr/bin/code to work again. The desktop file uses `/usr/share/code/code` though (see /usr/share/applications/code.desktop), so starting vscode from the dock, or from the app search results in a crash: /usr/share/code/code [88564:0308/080414.682744:FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) zsh: trace trap (core dumped) /usr/share/code/code Could the profile be fixed to include all common ways to start vscode? My current workaround is to run this on every boot: sudo sysctl -w kernel.apparmor_restrict_unprivileged_unconfined=0 sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0 thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2056517/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2056517] Re: VS Code profile still broken.
This is now moving forward and should show up in proposed soon. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2056517 Title: VS Code profile still broken. Status in apparmor package in Ubuntu: Confirmed Bug description: Ubuntu 24.04, VSCode installed via their repo (https://packages.microsoft.com/repos/code) Some updates ago apparmor gained an exception for /usr/bin/code to work again. The desktop file uses `/usr/share/code/code` though (see /usr/share/applications/code.desktop), so starting vscode from the dock, or from the app search results in a crash: /usr/share/code/code [88564:0308/080414.682744:FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) zsh: trace trap (core dumped) /usr/share/code/code Could the profile be fixed to include all common ways to start vscode? My current workaround is to run this on every boot: sudo sysctl -w kernel.apparmor_restrict_unprivileged_unconfined=0 sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0 thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2056517/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 2056517] Re: VS Code profile still broken.
** Summary changed: - vsode profile still broken + VS Code profile still broken. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/2056517 Title: VS Code profile still broken. Status in apparmor package in Ubuntu: Confirmed Bug description: Ubuntu 24.04, VSCode installed via their repo (https://packages.microsoft.com/repos/code) Some updates ago apparmor gained an exception for /usr/bin/code to work again. The desktop file uses `/usr/share/code/code` though (see /usr/share/applications/code.desktop), so starting vscode from the dock, or from the app search results in a crash: /usr/share/code/code [88564:0308/080414.682744:FATAL:credentials.cc(127)] Check failed: . : Permission denied (13) zsh: trace trap (core dumped) /usr/share/code/code Could the profile be fixed to include all common ways to start vscode? My current workaround is to run this on every boot: sudo sysctl -w kernel.apparmor_restrict_unprivileged_unconfined=0 sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0 thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2056517/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
