KoBruh
2023-02-20, 15:40
I use GNOME with kali linux. While I boot into the system, for about a second system GUI shows up and shuts down again. (-> tty screen comes) I can manually start it with
`sudo systemctl start gdm`
this is my `sudo systemctl status gdm` results: (just after boot)
```
● gdm.service - GNOME Display Manager
Loaded: loaded (/lib/systemd/system/gdm.service; enabled; preset: enabled)
Drop-In: /usr/lib/systemd/system/gdm.service.d
└─disable-wayland.conf
Active: active (running) since Mon 2023-02-20 18:30:19 +03; 54s ago
Process: 2547 ExecStartPre=/usr/share/gdm/generate-config (code=exited, status=0/SUCCESS)
Process: 2570 ExecStartPre=/usr/libexec/gdm-runtime-config set daemon WaylandEnable false (code=exited, status=0/SUCCESS)
Main PID: 2571 (gdm3)
Tasks: 3 (limit: 18993)
Memory: 7.1M
CPU: 149ms
CGroup: /system.slice/gdm.service
└─2571 /usr/sbin/gdm3
Feb 20 18:30:19 kobruh systemd[1]: Starting gdm.service - GNOME Display Manager...
Feb 20 18:30:19 kobruh systemd[1]: Started gdm.service - GNOME Display Manager.
Feb 20 18:30:19 kobruh gdm-launch-environment][2575]: pam_unix(gdm-launch-environment:session): session opened for user Debian-gdm(uid=126) by kobruh(uid=0)
Feb 20 18:30:25 kobruh gdm-password][3096]: gkr-pam: unable to locate daemon control file
Feb 20 18:30:25 kobruh gdm-password][3096]: gkr-pam: stashed password to try later in open session
Feb 20 18:30:25 kobruh gdm-password][3096]: pam_unix(gdm-password:session): session opened for user kobruh(uid=1000) by (uid=0)
Feb 20 18:30:25 kobruh gdm-password][3096]: gkr-pam: unlocked login keyring
Feb 20 18:30:31 kobruh gdm3[2571]: Gdm: Child process -2601 was already dead.
```
`sudo systemctl enable gdm` does not work and gives this error:
```
The unit files have no installation config (WantedBy=, RequiredBy=, Also=,
Alias= settings in the [Install] section, and DefaultInstance= for template
units). This means they are not meant to be enabled using systemctl.
Possible reasons for having this kind of units are:
? A unit may be statically enabled by being symlinked from another unit's
.wants/ or .requires/ directory.
? A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
? A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).
? In case of template units, the unit is meant to be enabled with some
instance name specified.
```
`sudo systemctl start gdm`
this is my `sudo systemctl status gdm` results: (just after boot)
```
● gdm.service - GNOME Display Manager
Loaded: loaded (/lib/systemd/system/gdm.service; enabled; preset: enabled)
Drop-In: /usr/lib/systemd/system/gdm.service.d
└─disable-wayland.conf
Active: active (running) since Mon 2023-02-20 18:30:19 +03; 54s ago
Process: 2547 ExecStartPre=/usr/share/gdm/generate-config (code=exited, status=0/SUCCESS)
Process: 2570 ExecStartPre=/usr/libexec/gdm-runtime-config set daemon WaylandEnable false (code=exited, status=0/SUCCESS)
Main PID: 2571 (gdm3)
Tasks: 3 (limit: 18993)
Memory: 7.1M
CPU: 149ms
CGroup: /system.slice/gdm.service
└─2571 /usr/sbin/gdm3
Feb 20 18:30:19 kobruh systemd[1]: Starting gdm.service - GNOME Display Manager...
Feb 20 18:30:19 kobruh systemd[1]: Started gdm.service - GNOME Display Manager.
Feb 20 18:30:19 kobruh gdm-launch-environment][2575]: pam_unix(gdm-launch-environment:session): session opened for user Debian-gdm(uid=126) by kobruh(uid=0)
Feb 20 18:30:25 kobruh gdm-password][3096]: gkr-pam: unable to locate daemon control file
Feb 20 18:30:25 kobruh gdm-password][3096]: gkr-pam: stashed password to try later in open session
Feb 20 18:30:25 kobruh gdm-password][3096]: pam_unix(gdm-password:session): session opened for user kobruh(uid=1000) by (uid=0)
Feb 20 18:30:25 kobruh gdm-password][3096]: gkr-pam: unlocked login keyring
Feb 20 18:30:31 kobruh gdm3[2571]: Gdm: Child process -2601 was already dead.
```
`sudo systemctl enable gdm` does not work and gives this error:
```
The unit files have no installation config (WantedBy=, RequiredBy=, Also=,
Alias= settings in the [Install] section, and DefaultInstance= for template
units). This means they are not meant to be enabled using systemctl.
Possible reasons for having this kind of units are:
? A unit may be statically enabled by being symlinked from another unit's
.wants/ or .requires/ directory.
? A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
? A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).
? In case of template units, the unit is meant to be enabled with some
instance name specified.
```