AppAmour prevents load on startup on Ubuntu 25.04 #480
Replies: 3 comments 3 replies
-
|
So just to make sure I got it right:
Is this correct? |
Beta Was this translation helpful? Give feedback.
-
|
Yes. I believe this started with Ubuntu 24.10, and I am presently on 25.04. So, if memory serves, it worked on 24.04 LTS, but it has been this way ever since upgrading. I end up with a bunch of these entries when I look in my autostart: 
This is the specific command that I presently use to bypass AppArmor: |
Beta Was this translation helpful? Give feedback.
-
|
This is a known bug and its being worked on by Cononical https://www.omgubuntu.co.uk/2025/10/flatpak-broken-ubuntu-25-10-apparmor-bug |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for your response. However, my situation is different in two ways. Flatpak DOES work. It just needs to have AppArmor turned off/limited in some way to do so. I am on version 25.04 (not 25.10, which is what this article refers to), and this problem existed on 24.10 as well, to my recollection. I was not realizing that 25.10 was so close to being released, and I am glad that you shared this, because if I were to foolishly jump into an upgrade...only to find Flatpak was completely inoperable, that would have been quite problematic. Again, thank you for your response, but my question remains... While "It's Canonical's fault" or "Just disable AppArmor" are still easy answers. I do believe if there were a proper AppArmor profile that I could use, I could give StreamController the permissions it needs without giving everything free reign. |
Beta Was this translation helpful? Give feedback.
-
|
Ubuntu's AppArmor now blocks unprivileged user namespaces, preventing Flatpak apps from starting. Here's the recommended solution: Create Bubblewrap AppArmor Profile
sudo nano /etc/apparmor.d/local-bwrap
sudo systemctl reload apparmor
ls ~/.config/autostart/ | grep -i stream
cat > ~/.config/autostart/streamcontroller.desktop << 'EOF'
[Desktop Entry]
Type=Application
Name=StreamController
Exec=flatpak run com.core447.StreamController
X-GNOME-Autostart-enabled=true
EOF
|
Beta Was this translation helpful? Give feedback.
-
|
First of all, thank you very much for your assistance. I very much appreciate it, and I really want to get this working properly. Unfortunately, after doing the above, I got the same results. My already-existing streamcontroller.desktop entry reads as follows (which is not the same as what you have above): My guess is that the differences have to do with me running Ubuntu Studio/KDE Plasma vs. vanilla Ubuntu/Gnome. If there is something that I am missing, please let me know. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I have been quite glad to find this program. Before it, I found using my Stream Deck borderline useless. However, for the last few versions of Ubuntu Studio (I would presume any flavor of Ubuntu), the program will not auto launch at startup. This a quite frustrating, since my primary way to use the Stream Deck had become to use it to startup most of the things that I use when I turn the machine on.
At this point, I need to go to the command line and basically turn off AppArmour or something equivalent before it will open (sadly, this goes for anything Flatpak/App Image, etc.). I know that, in theory, that using bubblewrap, I should be able to setup a profile that will let StreamController do what it needs to do (and presumably, that would include launching on startup). However, I have made some attempts to figure this out, and I have failed.
If anyone has done this, or if anyone has any advice on how to manage this, I'd be much obliged. Having to go to the command line before I can launch it is quite a bit less efficient than it just starting up automatically. Thank you.
Beta Was this translation helpful? Give feedback.
All reactions