Skip to content
Snippets Groups Projects
Commit 3dd18c4d authored by Recolic's avatar Recolic :house_with_garden:
Browse files

Update README.md

parent 061f8863
No related branches found
No related tags found
No related merge requests found
...@@ -165,14 +165,10 @@ Install seahorse, create a "password keyring". You MUST set a password (because ...@@ -165,14 +165,10 @@ Install seahorse, create a "password keyring". You MUST set a password (because
This is not the root cause. ArchLinux has the same error message, and everything works. `journalctl -xe` shows no error message at all. This is not the root cause. ArchLinux has the same error message, and everything works. `journalctl -xe` shows no error message at all.
I resolved this problem by setting correct `/etc/os-release` file.
- intune-portal white screen: glx: failed to create drisw screen; failed to load driver: zink - intune-portal white screen: glx: failed to create drisw screen; failed to load driver: zink
This is not the root cause. ArchLinux has the same error message, and everything works. `journalctl -xe` shows no error message at all. This is not the root cause. ArchLinux has the same error message, and everything works. `journalctl -xe` shows no error message at all.
I resolved this problem by setting correct `/etc/os-release` file.
- intune-portal says not compliant: Upgrade to a supported distributions... - intune-portal says not compliant: Upgrade to a supported distributions...
Run `journalctl | grep intune-agent | grep Reporting` to check what is intune-agent telling intune-portal. If you already updated `/etc/os-release` but intune-portal is not updated, please run `systemctl enable --user --now intune-agent.timer` manually. Run `journalctl | grep intune-agent | grep Reporting` to check what is intune-agent telling intune-portal. If you already updated `/etc/os-release` but intune-portal is not updated, please run `systemctl enable --user --now intune-agent.timer` manually.
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment