You are not logged in.
So this is spin off of another thread about keeping an HDMI screen "awake".
And it is very possibly as 'dumb'.
So I thought I had this understood. Using a mix of LightDM & Xfce to have an account that will show the wallboard page, in Chromium's Kiosk mode, after a reboot seems like something that these are well suited for.
I have read the following wiki pages on LightDM:
The Arch one has the most details as it also points out how to setup the lack of password.
After trying the Arch directions, with modifications for Debian Stable, I reboot and get a TTY for a brief moment, then a black screen.
:sigh: At some point I'll feel not useless with this.
----------
The user: wallboard is part of the autologin & nopasslogin groups
wallboard:x:1001:1002:,,,:/home/wallboard:/bin/bash
----------
conf files ahoy!
/etc/lightdm/lightdm.conf.d/wallboard.conf
[Seat:*]
autologin-user=wallboard
/home/wallboard/.xsession-errors (not a conf file but maybe useful?)
Xsession: X session started for wallboard at Wed May 24 15:50:37 PDT 2017
localuser:wallboard being added to access control list
/usr/bin/x-session-manager: X server already running on display :0
xfce4-session-Message: ssh-agent is already running; starting gpg-agent without ssh support
xfce4-session-Message: Got disconnected from D-Bus. Unless this happened during session shutdown, this is probably a bad thing.
(xfce4-panel:797): Gtk-CRITICAL **: IA__gtk_main_quit: assertion 'main_loops != NULL' failed
(xfwm4:793): Gtk-CRITICAL **: IA__gtk_main_quit: assertion 'main_loops != NULL' failed
xfwm4: Fatal IO error 2 (No such file or directory) on X server :0.0.
/etc/pam.d/lightdm
#%PAM-1.0
# Block login if they are globally disabled
#auth requisite pam_nologin.so
auth sufficient pam_succeed_if.so user ingroup nopasslogin
auth include system-login
# Load environment from /etc/environment and ~/.pam_environment
auth required pam_env.so envfile=/etc/default/locale
@include common-auth
-auth optional pam_gnome_keyring.so
@include common-account
# SELinux needs to be the first session rule. This ensures that any
# lingering context has been cleared. Without out this it is possible
# that a module could execute code in the wrong domain.
# When the module is present, "required" would be sufficient (When SELinux
# is disabled, this returns success.)
session [success=ok ignore=ignore module_unknown=ignore default=bad] pam_selinux.so close
session required pam_limits.so
session required pam_loginuid.so
@include common-session
# SELinux needs to intervene at login time to ensure that the process
# starts in the proper default security context. Only sessions which are
# intended to run in the user's context should be run after this.
session [success=ok ignore=ignore module_unknown=ignore default=bad] pam_selinux.so open
# When the module is present, "required" would be sufficient (When SELinux
# is disabled, this returns success.)
-session optional pam_gnome_keyring.so auto_start
@include common-password
Last edited by Head_on_a_Stick (2017-05-25 21:07:43)
Offline
After trying the Arch directions, with modifications for Debian Stable
For some reason, the surveillance cameras we installed at your house don't seem to be working [1] — what was the *exact* configuration that you tried?
[1] 8o
EDIT: anyway, if you want autologin then LightDM is just bloat...
http://forums.debian.net/viewtopic.php?f=16&t=123694
Last edited by Head_on_a_Stick (2017-05-25 07:19:23)
Offline
if you want autologin then LightDM is just bloat...
agreed, but nevertheless:
shouldn't lightdm have an autologin configuration option?
Offline
^It does, and it works.
...elevator in the Brain Hotel, broken down but just as well...
( a boring Japan blog (currently paused), now on Bluesky, there's also some GitStuff )
Offline
I've edited OP with more detail.
Offline
Can we see the output of:
/usr/sbin/lightdm --show-config
groups wallboard
Does the configuration snippet work if you add it to /etc/lightdm/lightdm.conf instead?
Offline
Can we see the output of:
/usr/sbin/lightdm --show-config groups wallboard
I'm still not skilled in the ways of the chroot and I'm having trouble getting that info while using the system-rescue-cd
Offline
^ Boot from the BunsenLabs GRUB menu then use <Ctrl>+<Alt>+F2 to switch to a TTY and log in from there to run the commands.
Your graphical desktop may be failing but the rest of your machine is working just fine
You can use pastebinit to generate a URL that can be posted here:
/usr/sbin/lightdm --show-config | pastebinit
groups wallboard | pastebinit
EDIT: or just remove the troublesome configuration file from the "live" environment to get your desktop back.
EDIT2: we've been here before, apparently:
https://forums.bunsenlabs.org/viewtopic.php?id=245
Last edited by Head_on_a_Stick (2017-05-25 18:30:20)
Offline
Does the configuration snippet work if you add it to /etc/lightdm/lightdm.conf instead?
Well, hot damn, if that didn't work a peach.
I think that was english. Anyway putting the line into the main lightdm.conf seems to have made the whole thing work as expected!
Thanks to each and every one of you for your input, and for not sh- pooping on me for these noob questions.
Also HoaS, to your point about the LightDM 'bloat', I understand that feel, but I'm trying to also think about the users who will be touching the box when I'm not there. And it seems the LightDM + Xfce would make it fairly easy for them to pick up/fix things should anything go pear shaped.
BTW this post from the fixed boxen.
EDIT2: we've been here before, apparently:
https://forums.bunsenlabs.org/viewtopic.php?id=245
Well ... huh ... :8
Last edited by geekosupremo (2017-05-25 19:04:30)
Offline