Don: Thanks for your advice. First on the parameters. I did try the "auth sufficient pam_succeed_if.so user ingroup nopasswdlogin " parameter a while ago and it did not make any difference. I think whoever did the image for the BBB used the timed login to make sure some startup stuff completed. Without it I get a message about something still running (when root is logging in).
In terms of the logs. The one place where something seems relevant is in /var/log/gdm/:0-greeter.log. It shows some permission problems that happen with my user and also with the xuser that came as part of the distribution image. (gnome-settings-daemon:441): GVFS-RemoteVolumeMonitor-WARNING **: cannot open directory /usr/share/gvfs/remote-volume-monitors: Error opening directory '/usr/share/gvfs/remote-volume-monitors': Permission denied (polkit-gnome-authentication-agent-1:444): polkit-gnome-1-WARNING **: Unable to determine the session we are in: No session for pid 444 Xlib: extension "DPMS" missing on display ":0". gdm-simple-greeter[446]: GVFS-RemoteVolumeMonitor-WARNING: cannot open directory /usr/share/gvfs/remote-volume-monitors: Error opening directory '/usr/share/gvfs/remote-volume-monitors': Permission denied gdm-simple-greeter[446]: Gtk-WARNING: gtkwidget.c:5709: widget not within a GtkWindow shell-init: error retrieving current directory: getcwd: cannot access parent directories: Permission denied gdm-simple-greeter[446]: WARNING: Unable to load CK history: no seat-id found I guess that I have been hoping that someone from the BBB team that created their image would see this post. There is either something wrong with the scripts behind gdm or I am just missing some key permission or group? I really, really, really don't want to have to dig into the details of how a gdm login happens if I don't have to. Cheers, Will On Friday, 8 November 2013 19:26:55 UTC, don wrote: > > On 11/08/2013 06:29 AM, Will Kostelecky wrote: > > After a lot more research it does seem like all that should be necessary > is to have these lines... > > [daemon] > TimedLoginEnable=true > TimedLogin=<username> > TimedLoginDelay=10 > > ...in /etc/gdm/custom.conf. I have booted my BBB from a fresh flash, > added my own user, changed the above to reflect the new user, and still the > login greeting panel hangs. When looking at top I do not see anything > obvious that is running. > > PLEASE can someone HELP? > > Will > > On Wednesday, 6 November 2013 23:08:54 UTC, Will Kostelecky wrote: >> >> I want to setup my BBB to have a user other than root login to the gdm >> without entering a password. I have editted the /etc/gdm/custom.conf file >> to replace root with the name of my user but the login does not complete. >> It either hangs at the login window waiting for a password...or it just >> hangs there without asking for a password. I have logged into gdm using >> the new user ID so I know it works. >> >> Thanks, >> Will >> > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to the Google Groups > "BeagleBoard" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] <javascript:>. > For more options, visit https://groups.google.com/groups/opt_out. > > Why are you not checking your logs for what is happening? > > I do not use Angstrom so cant really be of much use other than suggesting > what upstream expects the package to "act" like. > > On one of my arch installs I installed GDM and setup passwordless logins > as the DOCs for GDM suggest. Have you tried the non timed option? > > AutomaticLogin=username > AutomaticLoginEnable=True > > Also have you this this in pam.d/gdm? > > auth sufficient pam_succeed_if.so user ingroup nopasswdlogin > > then add a nopasswdlogin group and add the user to it? Not sure what > version of GDM you're on. > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
