I've been using SLiM for my login manager. The error I'm experiencing happens before I even get to X or SLiM.
Hi and welcome to the forum.If the only difference is whether or not you use a login manager, it's probably ConsoleKit related. For example, SLiM (and I think GDM/KDM too and probably others, as well), already start it, so you don't need another ck session in your ~/.xinitrc (see the first note from the SLiM wiki page). Which login manager do you use?
slim-cursor https://aur.archlinux.org/packages/slim-cursor/slim-plus https://aur.archlinux.org/packages/slim-plus/ar outdated, no vanilla and poorly documented clones of slim in repo
Many of these patch applied now are in upstream
Could be possible to merge votes in slim-git
https://aur.archlinux.org/packages/slim-gitor simply delete slim-cursor and slim-plus
Sorry for digging up, but does anyone knows the answer to this problem?I am experiencing the same with Slim:* When I'm using my default laptop monitor, Slim's resolution is the monitor's native but,* When I'm using my external monitor (through hdmi), Slim's resolution isn't the native.Thanks
Hi All, thanks for your time and attention.inittab was untouched, it is the same as packaged one.Slim perfectly supports running from DAEMONS, can be confirmed by wiki https://wiki.archlinux.org/index.php/SLiM#Enabling_SLiMAlso looks like this issue is confirmed for various init styles and display managers.Again, thanks to everyone, waiting for the fix in dbus :-)
I put a few exports in ~/.profile, but when logging in to XFCE4 via slim, the exports aren't present (tested by echo'ing the variables in Bash). If I source it manually, it works, but they're there to establish proxy settings and is useless unless it's in the environment.