We don't need no stinkin' display manager...

There is comfort and beauty (sometimes) in a display manager.  Art matters . . .

To start the graphical desktop automatically after login at TTY1 add this line to the end of ~/.profile:

[ "$(tty)" = /dev/tty1 ] && exec startx

We don't need no stinkin' display manager...

So I can confirm the delay problem was coming indeed from Slim.

I didn't tried yet, talking about display manager aka login manager, does someone have any recommendation for one that work well with devuan ? That is gpl ? and lightweight ?

I edited the grub command at boot with key e ->

and added 3 at the end of the line Linux  /boot/vmlinuz..... but this is not working -> it launch slim still.

So I tried with the option: Advanced options for devuan GNU/Linux then (recovery mode) that option have no delay to login with console. But I guess in that mode a lot of services are down ?

How can I login (normally 5) in console without Slim ?

Do you still experience the delay with (for example) GDM? How about a plain console login?

nft list ruleset

table ip6 Tip6 {
         chain chPR{
                   type filter hook prerouting priority filter; policy drop;
         }
}
table ip Tip {
         chain chIN{
                   type filter hook input priority filter; policy drop;
                   ct state established,related accept
                   iifname "lo" accept
         }
}

on the other hand

table ip Tip {
         chain chIN{
                   type filter hook input priority filter; policy drop;
                   ct state established,related accept
                   iifname "lo" accept
         }
}

work !, but WHY slim would require IPv6 🤨 ?

I've cleared /var/log/messages before testing, and nothing generate new messages.

Thanks for your reply,

This is not my final config, but the start. Excluding everythings then make some exceptions. (opening only the necessary)
indeed I plan to add something like ct state {established, related} accept

Hoo that I didn't think about it !! thx !

I will make make some tests and I will update this topics in the following hours.

Thanks again.👍

@OP: what are you trying to achieve with that configuration? It will not be possible to connect to the internet unless you allow tracked connections, like this:

    ct state {established, related} accept

And the loopback device will also be blocked without

    iifname lo accept

I suspect the delay is due to either the loopback or internet block, check /var/log/messages for anything relevant.

backup your original nftables.conf before you do this.

slim: waiting for X server to shut down

slim: waiting for x server to begin accepting connection
slim: Consolekit::open_session: unable to open session: The name org.freedesktop.ConsoleKit was not provided by any .service
slim: falling back to PAM session

chain input {
             type filter hook input priority 0; policy drop;
}

or / and

chain output{
             type filter hook output priority 0; policy drop;
}

has/have policy set to drop...

I just installed nftable on my system (thanks to Head_on_a_Stick )

Now,when I edit the

default /etc/nftables.conf

#!/usr/sbin/nft -f

flush ruleset

table inet filter {
         chain input {
                   type filter hook input priority 0;
         }
         chain forward {
                   type filter hook forward priority 0;
         }
         chain output{
                   type filter hook output priority 0;
         }
}

to

#!/usr/sbin/nft -f

flush ruleset

table inet filter {
         chain input {
                   type filter hook input priority 0; policy drop;
         }
         chain output{
                   type filter hook output priority 0; policy drop;
         }
}

I reboot then my screen is black for 4Min 24Sec before I finally see the login screen.
When I do a /user/sbin/nft -f /etc/nftables.conf the rule apply with no delay.

so I guess something at boot is conflicting with this ruleset, but what ?

Thanks.