slim service start problem

Bug #2003657 reported by Piotr Skwarna
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
slim (Ubuntu)
New
Undecided
Unassigned

Bug Description

ubunut 22.04 simple server insytallation

after installing slim package (apt install slim)

root@docker:~# service slim status
● slim.service - SLiM Simple Login Manager
     Loaded: loaded (/lib/systemd/system/slim.service; indirect; vendor preset: enabled)
     Active: active (running) since Sun 2023-01-22 19:39:05 UTC; 230ms ago
    Process: 1526 ExecStartPre=/bin/sh -c [ "$(cat /etc/X11/default-display-manager 2>/dev/null)" = "/usr/bin/slim" ] (code=exited, status=0/SUCCESS)
   Main PID: 1528 (slim)
      Tasks: 2 (limit: 14230)
     Memory: 1.1M
        CPU: 19ms
     CGroup: /system.slice/slim.service
             └─1528 /usr/bin/slim -nodaemon

Jan 22 19:39:05 docker systemd[1]: Starting SLiM Simple Login Manager...
Jan 22 19:39:05 docker systemd[1]: Started SLiM Simple Login Manager.
Jan 22 19:39:05 docker slim[1528]: PAM unable to dlopen(pam_gnome_keyring.so): /lib/security/pam_gnome_keyring.so: cannot open shared object file: No such file or directory
Jan 22 19:39:05 docker slim[1528]: PAM adding faulty module: pam_gnome_keyring.so
Jan 22 19:39:05 docker slim[1530]: /usr/bin/X11/xauth: file /var/run/slim.auth does not exist

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: slim 1.3.6-5.3build1
ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
Uname: Linux 5.15.0-58-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
CasperMD5CheckMismatches: ./boot/grub/grub.cfg
CasperMD5CheckResult: fail
Date: Sun Jan 22 19:42:17 2023
InstallationDate: Installed on 2023-01-20 (2 days ago)
InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=C.UTF-8
 SHELL=/bin/bash
SourcePackage: slim
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Piotr Skwarna (piotr-skwarna) wrote :
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.