Bug 105508 - mounting /proc with hidepid causes: Fatal server error: (EE) xf86OpenConsole: Cannot open virtual console 1 (Permission denied)
Summary: mounting /proc with hidepid causes: Fatal server error: (EE) xf86OpenConsole:...
Status: RESOLVED MOVED
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/General (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
URL: https://bugs.launchpad.net/ubuntu/+so...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-03-14 15:04 UTC by Simon Deziel
Modified: 2018-12-13 18:34 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
/var/lib/gdm3/.local/share/xorg/Xorg.0.log (5.71 KB, text/x-log)
2018-03-14 15:04 UTC, Simon Deziel
no flags Details

Description Simon Deziel 2018-03-14 15:04:03 UTC
Created attachment 138109 [details]
/var/lib/gdm3/.local/share/xorg/Xorg.0.log

Mounting /proc with hidepid=2,gid=sudo prevents X from starting properly. I originally reported the issue to Ubuntu in [1]. I'm using those mount options for added security/privacy.

On older releases this used to work fine.

1: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1754401
Comment 1 Adam Jackson 2018-06-13 19:48:13 UTC
Booting with hidepid=2 on a Fedora 28 machine, X starts with no problem. Presumably some other part of Ubuntu's setup is getting confused by this. It would be helpful if you could strace X startup to see why it doesn't think it can find the console.
Comment 2 GitLab Migration User 2018-12-13 18:34:25 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/xorg/xserver/issues/243.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.