Announcement

Collapse
No announcement yet.

systemctl status masked - dead

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    [CONFIGURATION] systemctl status masked - dead

    18.04 LTS
    nvidia-driver-415

    do I have to worry about or simply ignore the systemctl status of x11-common and sudo?

    Code:
    systemctl status x11-common
    ● x11-common.service
    Loaded: masked (/dev/null; bad)
    Active: inactive (dead)
    
    systemctl status sudo
    ● sudo.service
    Loaded: masked (/dev/null; bad)
    Active: inactive (dead)

    #2
    Only if you have no video and are unable to use sudo. systemctl is showing a specific and very narrow condition at a specific point in time, which only is a problem with other evidence.

    If you have some specific evidence of either, come back.
    The next brick house on the left
    Intel i7 11th Gen | 16GB | 1TB | KDE Plasma 5.24.7 | Kubuntu 22.04.4 | 6.5.0-28-generic


    Comment


      #3
      Originally posted by jglen490 View Post
      Only if you have no video and are unable to use sudo. systemctl is showing a specific and very narrow condition at a specific point in time, which only is a problem with other evidence.

      If you have some specific evidence of either, come back.
      many thanks!
      yeah, it looks strange ... but same thing on a newly installed system also w/ apparmor:
      Code:
      systemctl status apparmor
      ● apparmor.service - AppArmor initialization
        Loaded: loaded (/lib/systemd/system/apparmor.service; enabled; vendor preset: enabled)
        Active: inactive (dead)
      Condition: start condition failed at Tue 2018-12-25 08:00:16 CET; 49min ago
                └─ ConditionSecurity=apparmor was not met
          Docs: man:apparmor(7)
                http://wiki.apparmor.net/

      Comment

      Working...
      X