-
-
Notifications
You must be signed in to change notification settings - Fork 274
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] Can't use Google-Chrome anymore after the hardening was done #523
Comments
Hi @madiba237 , I have not in any way tested the script on a client running graphical applications. Can you attach some relevant journal logs as well? |
sorry for the late reply i was overwhelmed by other projects here are lines in my logs that concern google chrome 2024-11-26T15:21:55.301915+01:00 PA-UBUNTU gnome-shell[20638]: Error fetching user unit for own pid: 3 Great thanks for the endeavors |
no worries, but those log messages was included in you issue as well. what does since the script is one-shot, have you tried re-installing Chrome? |
Greeting , |
Could you then list the AppArmor profiles in use? |
here are some google-chrome logs 2024-11-27T13:12:54.925568+01:00 ADM-LAT-171 google-chrome.desktop[30893]: [30885:30910:1127/131254.925529:ERROR:address_tracker_linux.cc(452)] Failed to recv from netlink socket: Permission non accordée (13) |
Try running |
Hi @konstruktoid i was able to launch chrome , after running the commands you suggested , i am going for further investigations |
Describe the bug
Google chrome worked just fine before the hardening, after it impossible to launch it no matter the user (root...)
To Reproduce
launching google-chrome from the terminal result to this message showing up 👍
/usr/bin/google-chrome: error while loading shared libraries: libdl.so.2: cannot open shared object file: Permission denied
Expected behavior
google-chrome browser should be launched .
System (lsb_release -a):
Distributor ID: Ubuntu
Description: Ubuntu 24.04.1 LTS
Release: 24.04
Codename: noble
Additional context
Add any other context about the problem here.
After stoping and disabeling apparmor.service it still doesn't work
The text was updated successfully, but these errors were encountered: