-
Notifications
You must be signed in to change notification settings - Fork 597
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: app not working on clean install ubuntu 24.04 and kubuntu 24.04 #2123
Comments
Did you use this application in virtual env? (e.g. docker) |
no i am not using any virtual env. just clean flasher ubuntu 24.04 tried kubuntu too but not worked |
my ubuntu 24.04 not working too. |
I tried it with my friend's laptop, the application was installed on him for a long time and when he upgraded to ubuntu 24.04, the application continued to work. The application was working on my computer before I reset my laptop, but since I reset and did a clean installation, the application has not been opening. |
Same behavior here, I tried with |
@falconnnx @huiqiangyang @mihaistana Caused by Ubuntu 24.04's AppArmor |
Duplicate of #2007 |
Preflight Checklist
YouTube Music (Application) Version
3.3.10 .deb
Checklists
What operating system are you using?
Ubuntu
Operating System Version
Ubuntu 24.04
What CPU architecture are you using?
x64
Last Known Working YouTube Music (Application) version
nope on clean flash ubuntu 24.04
Reproduction steps
just trying to open the app
Expected Behavior
opening the app
Actual Behavior
When I try to open the application, it does not open. When I try to open it from the terminal, I get the following output:
$ youtube-music
LaunchProcess: failed to execvp:
/opt/YouTube
[9730:0605/110120.260550:FATAL:zygote_host_impl_linux.cc(201)] Check failed: . : Geçersiz bağımsız değişken (22)
İzleme/kesme noktası yakalayıcı (çekirdek döküldü)
Enabled plugins
i dont know because app doesnt work. Its your 3.3.10 build.
Additional Information
tried .deb, .snap, .appimage but no one is worked for me
The text was updated successfully, but these errors were encountered: