needs_root_rights=yes
allowed_users=console

I'm using slim-1.3.6-5+devuan4rc5a1

I just did update/upgrade, and everything is still working correctly.

Update: I upgraded another installation. This one was a refracta jessie that got upgraded to ascii, and then I replaced lightdm with the same version of slim I named above. The Xwrapper.config in this system only has the one line (like yours) and everything still works.

allowed_users=console

This is on ceres

# Xwrapper.config (Debian X Window System server wrapper configuration file)
#
# This file was generated by the post-installation script of the x11-common
# package using values from the debconf database.
#
# See the Xwrapper.config(5) manual page for more information.
#
# This file is automatically updated on upgrades of the x11-common package
# *only* if it has not been modified since the last upgrade of that package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command as root:
#   dpkg-reconfigure x11-common
allowed_users=console

This is on ascii

# Xwrapper.config (Debian X Window System server wrapper configuration file)
#
# This file was generated by the post-installation script of the x11-common
# package using values from the debconf database.
#
# See the Xwrapper.config(5) manual page for more information.
#
# This file is automatically updated on upgrades of the x11-common package
# *only* if it has not been modified since the last upgrade of that package.
#
# If you have edited this file but would like it to be automatically updated
# again, run the following command as root:
#   dpkg-reconfigure x11-common
allowed_users=console

I would suspect evdev (comes from X "freedesktop" world) or more likely one of the udev alternatives is not past unstable yet. (ceres)
So on ascii (testing) there will be issues.

Unless of course your trying to use wayland alone in which case good luck.
Wayland doesn't do anything but render stuff. (short version).

See if you have an /etc/X11/Xwrapper ?
( there are auth and legacy packages for X )

__the rest of this is just rambling nonsense that may or may not be useful correct or even english_

These days I short circuit all that "system initialisation" total nonsense by testing startx (as root).
If that works then work backwards.
(essentially all is well )

Permission / access / initialisation of pointers graphics cards and so on,  are not the task of a Display Manager. Sure loading a module or driver or protocol can be a handy *side effect* but in a "normal" work station / desktop / thin client  set of use cases other subsystems are meant to handle access to lumps of plastic, metal and wishes.

Pointer and keyboard may not be fully initialised (no mouse required for example) until you get all the way to your desktop / window manager.
Because:
The Display Manager is usually *and quite rightly* allowed access to a minimal set of files and  normally hosts.

Some go further than others in allowing access some do less, its impossible to guess our preferred security needs. So less is best here. The minimum required to get you logged into whatever desktop you use on whatever operating environment.

Slim more or less assumes you are on your own host.
It doesn't even allow you to select a locale  TZ or alternative set of languages.

Just puzzled.

https://github.com/PeteGozz/slim

Some of these thing  I will merge into the Devuan GitLAB version
   For packaging tests etc.

The INSTALL file should get you on your way.

Which of course means that there are build issues with the package.

quilt push -a   AOK

dpkg-source --commit     not so much .

So normal really.

I look again with fresh eyes tomorrow.

So anyway a test build or three I did went well enough
(except for the /etc/slim.conf file)
But hand edits made that all work
essentially it falls over to failsafe OK

This now should be "f i x e d"  will see tomorrow.

^<edit>^^^ done ^^^^^
Copied over from the link.
Changes:
Moved messages to an informative position.
Above the entry box
(Where users eye line is
   (room for any longer messages))

Maybe a white space or two and a comment.

There appears to be no canonical source for themes ???
</edit>
I will also move it under debian/
   so that it only gets installed if there is no previous theme.
   Which means its functionally a failsafe.

See also the config file
  -simpler(ish) to change screen messages there

git (lightweight) tagged Kafka to remove message layout

Yeah, it's BIG . . .

https://drive.google.com/file/d/0B6DOd- … sp=sharing

There are configure file changes.
I also need to detect if the desktop set is in place at install time.
(and not set this in the configure file or even not install it ...?)

I have not built a working deb yet.

(there may be quilt patch issues)

https://git.devuan.org/PeteGozz/slim/tree/tribulate0

fsmithred wrote:

PeteGozz wrote:

   
    type -  exit                                                           exits

Can't find the smiley with the big-eyed look of shock. Damn. Thanks for that. I didn't know.

Maybe the text over the entry box should say "username or command" instead of just "username". Check with the boss (a.k.a. She who has command over all things visual.)

If I am not mistaken in the other system that would log in user exit and activate the exit daemon and open an exit shocket.

Don't mind me, I may not know what I am talking about, I just skipped to devuan out of pure intuition

Note that F11 at slim login screen takes a screenshot with scrot and puts it in /root/slim.png.  Thanks to fsr for figuring that out.  Should make things easy for you.

Positioning items on the slim screen is challenging to say the least.  You have my sympathy.  That's why the layout is currently so sparse.

This is why in the upstream (not devuan not debian) version I will do a visually basic theme that exposes the engine  more.

Not because its pretty or  tasked with branding but so that there is a template to do all that design stuff with.

I have the debian 8+ (?)  examples as well now to look at.
The first observation is that there are too many release specific directories of themes.
2  should be plenty.  We have already dumped all that

They put the instructions greyed out in the entry field. Which is nice.
My thought would be: Icons (generic)  first then text as an adjunct.

But not my call ! (and I don't want or think it should be).
Though I'm so _bad_ with GUI things ... maybe

So I'm looking at the incoming ceres/sid  stuff later today...

With a view to ascii.
(there is not much at all so far that I have seen)

... Butterflys ... I'm seeing butterfys ... and planets ....