| View previous topic :: View next topic |
| Author |
Message |
bagas
Apprentice
Joined: 29 Jun 2018
Posts: 215
|
 Posted: Sun Nov 15, 2020 12:49 pm Post subject: xfce4 slim black screen if the password is entered incorrect |
 |
|
Hello.
A situation arose.
Please tell me how to solve this problem.
If you enter the wrong password when logging in through slim, a black screen appears.
| Code: | /etc/slim.conf
default_path /bin:/usr/bin:/usr/local/bin
default_xserver /usr/bin/X
xserver_arguments -nolisten tcp -br -deferglyphs 16 vt07
halt_cmd /sbin/shutdown -h now
reboot_cmd /sbin/shutdown -r now
console_cmd /usr/bin/xterm -C -fg white -bg black +sb -T "Console login" -e /bin/sh -c "/bin/cat /etc/issue; exec /bin/login"
xauth_path /usr/bin/xauth
authfile /var/run/slim.auth
numlock on
login_cmd exec /bin/bash -login /usr/share/slim/Xsession %session
sessionstart_cmd /usr/bin/sessreg -a -l :0.0 %user
sessionstop_cmd /usr/bin/sessreg -d -l :0.0 %user
daemon yes
sessiondir /usr/share/xsessions
screenshot_cmd import -window root /slim.png
welcome_msg Welcome to %host
shutdown_msg The system is halting...
reboot_msg The system is rebooting...
current_theme flat
lockfile /run/slim.pid
logfile /var/log/slim.log
|
log messages
| Code: | Nov 15 10:18:27 serv1 slim[5818]: pam_unix(slim:auth): authentication failure; logname= uid=0 euid=0 tty=:0.0 ruser=root rhost= user=bars
Nov 15 10:18:27 serv1 slim[5818]: pam_faillock(slim:auth): Error opening the tally file for bars: No such file or directory |
slim.log
| Code: | slim: waiting for X server to begin accepting connections.
slim: pam_authenticate(): Permission denied |
| Code: | | [ebuild R ] x11-misc/slim-1.3.6-r5::gentoo USE="pam -branding" 0 KiB |
The system is built with flags like this
| Code: | ENABLE_USE="elogind policykit"
DISABLE_USE="-joystick -kde -gnome -samba -cups -consolekit -systemd -arts -ipv6 -sudo -multilib -svg" |
_________________
BSD, Linux systems blog |
|
| Back to top |
|
 |
bagas
Apprentice
Joined: 29 Jun 2018
Posts: 215
|
| Posted: Sun Nov 15, 2020 3:52 pm Post subject: |
|
|
It's strange.
If you enter the login / password of a non-existent user, the slim authorization window is simply reset and allows you to re-enter the login / password.
If you enter the wrong password for an existing user, then a black screen and you have to reboot xdm again.
It seems to me that there is something in the pam palettes.
_________________
BSD, Linux systems blog |
|
| Back to top |
|
|
bagas
Apprentice
Joined: 29 Jun 2018
Posts: 215
|
| Posted: Mon Nov 16, 2020 5:29 am Post subject: |
|
|
Have thoughts, ideas, what is the problem?
_________________
BSD, Linux systems blog |
|
| Back to top |
|
|
bagas
Apprentice
Joined: 29 Jun 2018
Posts: 215
|
| Posted: Mon Nov 16, 2020 3:29 pm Post subject: |
|
|
created the /run/faillock/ directory.
Files started to be created when you enter the password incorrectly.
| Code: | cat /run/faillock/bars
:0.0��_ |
log messages
| Code: | | Nov 16 18:17:41 serv1 slim[3662]: pam_unix(slim:auth): authentication failure; logname= uid=0 euid=0 tty=:0.0 ruser=root rhost= user=bars |
After entering the wrong password, the screen is still black, I can not fix the situation, help.
_________________
BSD, Linux systems blog |
|
| Back to top |
|
|
Ionen
Developer
Joined: 06 Dec 2018
Posts: 2949
|
| Posted: Mon Nov 16, 2020 3:34 pm Post subject: |
|
|
Not sure what's wrong but I'd consider moving away from slim. I've used it long ago but its upstream is dead and hasn't gotten a release in 7 years, and given DMs need to keep up with login/session systems changes it'll likely break completely in time (Edit: also, its primary maintainer in gentoo doesn't seem to have worked on it in 4 years and been getting quick fixes from other maintainers instead, many open bugs).
Hopefully someone else can help if you want to keep using it. |
|
| Back to top |
|
|
bagas
Apprentice
Joined: 29 Jun 2018
Posts: 215
|
| Posted: Mon Nov 16, 2020 3:46 pm Post subject: |
|
|
| Ionen wrote: | Not sure what's wrong but I'd consider moving away from slim. I've used it long ago but its upstream is dead and hasn't gotten a release in 7 years, and given DMs need to keep up with login systems changes it'll likely break completely in time (Edit: also, its primary maintainer in gentoo doesn't seem to have worked on it in 4 years and been getting quick fixes from other maintainers instead, many open bugs).
Hopefully someone else can help if you want to keep using it. |
slim suits everyone, is light and doesn't carry a lot of packages.
What do you recommend?
_________________
BSD, Linux systems blog |
|
| Back to top |
|
|
szatox
Advocate
Joined: 27 Aug 2013
Posts: 3682
|
| Posted: Mon Nov 16, 2020 6:07 pm Post subject: |
|
|
That's weird, slim works just fine on a few of my machines, including ~amd64. I'm using lxde.
One thing that requires manual configuration is session type.
Slim does not provide a sane default. At least not sane enough for me. So the first thing to try is cycling through available session types with F1.
| Quote: | | Nov 16 18:17:41 serv1 slim[3662]: pam_unix(slim:auth): authentication failure; logname= uid=0 euid=0 tty=:0.0 ruser=root rhost= user=bars |
this is disturbing though. Can you login by other means? E.g. does SSH work? I think it currently uses pam by default. |
|
| Back to top |
|
|
bagas
Apprentice
Joined: 29 Jun 2018
Posts: 215
|
| Posted: Tue Nov 17, 2020 8:35 am Post subject: |
|
|
| szatox wrote: | That's weird, slim works just fine on a few of my machines, including ~amd64. I'm using lxde.
One thing that requires manual configuration is session type.
Slim does not provide a sane default. At least not sane enough for me. So the first thing to try is cycling through available session types with F1.
| Quote: | | Nov 16 18:17:41 serv1 slim[3662]: pam_unix(slim:auth): authentication failure; logname= uid=0 euid=0 tty=:0.0 ruser=root rhost= user=bars |
this is disturbing though. Can you login by other means? E.g. does SSH work? I think it currently uses pam by default. |
Installed lightdm.
All is well.
_________________
BSD, Linux systems blog |
|
| Back to top |
|
|
bunder
Bodhisattva
Joined: 10 Apr 2004
Posts: 5956
|
| Posted: Thu Nov 19, 2020 5:38 pm Post subject: |
|
|
me too. pam is broken. i've tried reporting it twice, but they keep shrugging me off. https://bugs.gentoo.org/show_bug.cgi?id=752390
_________________
| Neddyseagoon wrote: | | The problem with leaving is that you can only do it once and it reduces your influence. |
banned from #gentoo since sept 2017 |
|
| Back to top |
|
|
bagas
Apprentice
Joined: 29 Jun 2018
Posts: 215
|
| Posted: Sun Nov 22, 2020 8:37 am Post subject: |
|
|
i think the problem in slim.
_________________
BSD, Linux systems blog |
|
| Back to top |
|
|
bagas
Apprentice
Joined: 29 Jun 2018
Posts: 215
|
|
| Back to top |
|
|
|
Desktop Environments
