[Touch-packages] [Bug 2056517] Re: vsode profile still broken
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apparmor (Ubuntu) Status: New => Confirmed -- 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: vsode 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: vsode profile still broken
I won't promise we will get to fixing PHPStorm or Jetbrains before release, but without a bug they certainly won't get fixed, so yes it is worth filing a bug for them. -- 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: vsode profile still broken Status in apparmor package in Ubuntu: New 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: vsode profile still broken
Thanks, I'm looking forward to it. a bit unrelated: PHPStorm (and I'd guess all Jetbrains IDEs) is also broken, but that is installed by unpacking a tarball to a location and let it auto-update itself. Is there any point in filing a bug for that too? -- 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: vsode profile still broken Status in apparmor package in Ubuntu: New 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: vsode profile still broken
The fix for vscode is currently in apparmor 4.0.0-beta2-0ubuntu3 pending a Feature Freeze exception. If the feature freeze exception is not granted then the fix will be moved to a bug patch on the current apparmor 4.0.0-alpha4 Atm the fix is available via ppa https://launchpad.net/~apparmor- dev/+archive/ubuntu/apparmor-ffe -- 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: vsode profile still broken Status in apparmor package in Ubuntu: New 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
