Timeline for Is systemd's logind or Gnome-wayland-session incompatible with hidepid=2?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 13, 2017 at 12:47 | comment | added | sourcejedi | @humanityANDpeace the updated question should show the specific exemption you made, the fact that you are using arch linux, and absolutely needs to include an indication of the versions or at least date that the relevant software comes from. (One reason is that QAs are a reference to be referred to by others in future). | |
| Jun 13, 2017 at 8:37 | comment | added | sourcejedi | @humanityANDpeace weird! I can't think of anything, but if you want to narrow things down you should post the actual error messages :). | |
| Jun 13, 2017 at 6:52 | comment | added | humanityANDpeace |
Indeed arch can boot alright. Looking at the error messages in journalctl it seems that gnome-session cannot get the logind sessin id, in case the hidepid=2 is set, even when I granted the exception to the procfs. It can be that systemd is not even the culprit but hence Gnome.
|
|
| Jun 12, 2017 at 8:28 | history | edited | sourcejedi | CC BY-SA 3.0 |
added 173 characters in body
|
| Jun 12, 2017 at 8:23 | history | edited | sourcejedi | CC BY-SA 3.0 |
added 173 characters in body
|
| Jun 12, 2017 at 8:15 | history | edited | sourcejedi | CC BY-SA 3.0 |
added 173 characters in body
|
| Jun 12, 2017 at 8:09 | history | answered | sourcejedi | CC BY-SA 3.0 |