Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#52450 - [hidepid] breaks wayland on gnome desktop
Attached to Project:
Community Packages
Opened by bull shit (dontread456) - Sunday, 08 January 2017, 22:57 GMT
Last edited by Daniel Micay (thestinger) - Saturday, 18 March 2017, 06:10 GMT
Opened by bull shit (dontread456) - Sunday, 08 January 2017, 22:57 GMT
Last edited by Daniel Micay (thestinger) - Saturday, 18 March 2017, 06:10 GMT
|
DetailsDescription:
when package hidepid is installed gnome will always launch a Xorg session even when wayland session is requested in gdm. wayland possibly needs something from /proc that comes from different user. (note that gdm launches under user gdm) Additional info: * package version(s) hidepid 1-1 * config and/or log files etc. Steps to reproduce: install hidepid under gdm do not select Xorg session (wayland is now the default option) log-in and see that a Xorg session has been launched anyway and wayland is not being used. |
This task depends upon
Closed by Daniel Micay (thestinger)
Saturday, 18 March 2017, 06:10 GMT
Reason for closing: Not a bug
Additional comments about closing: This isn't a bug in the hidepid package, it's a missing proc group exception elsewhere. The package and existing exceptions by other packages like polkit are only intended to be a starting point.
Saturday, 18 March 2017, 06:10 GMT
Reason for closing: Not a bug
Additional comments about closing: This isn't a bug in the hidepid package, it's a missing proc group exception elsewhere. The package and existing exceptions by other packages like polkit are only intended to be a starting point.
Comment by Daniel Micay (thestinger) -
Monday, 09 January 2017, 16:12 GMT
You'll need to figure out which process needs to be in the proc group. It's usually going to be a problem for that package to solve similar to how polkit is in the proc group. The proc group is part of the base Arch installation.