Why is SLiM stuck at the login screen?





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







3















I've recently installed X and SLiM but when I wanted to login it wouldn't let me. It keeps asking for username. (virtualbox)



My /.xinitrc:



DEFAULT_SESSION=ck-launch-session dbus-launch openbox-session
case $1 in
openbox)
exec ck-launch-session dbus-launch openbox-session
xfce4)
exec startxfce4
*)
exec $DEFAULT_SESSION
esac


Log: (1st is username attempt, 2nd is root attempt)



slim: waiting for X server to begin accepting connections

slim: waiting for X server to shut down


slim: waiting for X server to begin accepting connections
slim: pam_authentication(): Authentication failure









share|improve this question

























  • It keeps asking for the password, or it logs in, tries to create the X-Session, then fails and throws you back at the login?

    – Bobby
    Jul 26 '12 at 12:18











  • I enter my username&password but it keeps asking for them. In the logs it says "failed to authenticate"

    – Seven of Nine
    Jul 26 '12 at 12:20











  • And you are sure you are entering the correct credentials?

    – Bobby
    Jul 26 '12 at 12:21











  • Yea, when I press Ctrl+Alt+F1 I can easily log into the console.

    – Seven of Nine
    Jul 26 '12 at 12:22






  • 1





    According to the wiki, login information may be wrong in the logs, so this could be another issue. Check again after correcting this, maybe : wiki.archlinux.org/index.php/SLiM#Login_information_with_SLiM

    – Nicolas Barbey
    Jul 26 '12 at 12:47


















3















I've recently installed X and SLiM but when I wanted to login it wouldn't let me. It keeps asking for username. (virtualbox)



My /.xinitrc:



DEFAULT_SESSION=ck-launch-session dbus-launch openbox-session
case $1 in
openbox)
exec ck-launch-session dbus-launch openbox-session
xfce4)
exec startxfce4
*)
exec $DEFAULT_SESSION
esac


Log: (1st is username attempt, 2nd is root attempt)



slim: waiting for X server to begin accepting connections

slim: waiting for X server to shut down


slim: waiting for X server to begin accepting connections
slim: pam_authentication(): Authentication failure









share|improve this question

























  • It keeps asking for the password, or it logs in, tries to create the X-Session, then fails and throws you back at the login?

    – Bobby
    Jul 26 '12 at 12:18











  • I enter my username&password but it keeps asking for them. In the logs it says "failed to authenticate"

    – Seven of Nine
    Jul 26 '12 at 12:20











  • And you are sure you are entering the correct credentials?

    – Bobby
    Jul 26 '12 at 12:21











  • Yea, when I press Ctrl+Alt+F1 I can easily log into the console.

    – Seven of Nine
    Jul 26 '12 at 12:22






  • 1





    According to the wiki, login information may be wrong in the logs, so this could be another issue. Check again after correcting this, maybe : wiki.archlinux.org/index.php/SLiM#Login_information_with_SLiM

    – Nicolas Barbey
    Jul 26 '12 at 12:47














3












3








3








I've recently installed X and SLiM but when I wanted to login it wouldn't let me. It keeps asking for username. (virtualbox)



My /.xinitrc:



DEFAULT_SESSION=ck-launch-session dbus-launch openbox-session
case $1 in
openbox)
exec ck-launch-session dbus-launch openbox-session
xfce4)
exec startxfce4
*)
exec $DEFAULT_SESSION
esac


Log: (1st is username attempt, 2nd is root attempt)



slim: waiting for X server to begin accepting connections

slim: waiting for X server to shut down


slim: waiting for X server to begin accepting connections
slim: pam_authentication(): Authentication failure









share|improve this question
















I've recently installed X and SLiM but when I wanted to login it wouldn't let me. It keeps asking for username. (virtualbox)



My /.xinitrc:



DEFAULT_SESSION=ck-launch-session dbus-launch openbox-session
case $1 in
openbox)
exec ck-launch-session dbus-launch openbox-session
xfce4)
exec startxfce4
*)
exec $DEFAULT_SESSION
esac


Log: (1st is username attempt, 2nd is root attempt)



slim: waiting for X server to begin accepting connections

slim: waiting for X server to shut down


slim: waiting for X server to begin accepting connections
slim: pam_authentication(): Authentication failure






virtualbox arch-linux






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jul 26 '12 at 14:00







Seven of Nine

















asked Jul 26 '12 at 12:11









Seven of NineSeven of Nine

2628




2628













  • It keeps asking for the password, or it logs in, tries to create the X-Session, then fails and throws you back at the login?

    – Bobby
    Jul 26 '12 at 12:18











  • I enter my username&password but it keeps asking for them. In the logs it says "failed to authenticate"

    – Seven of Nine
    Jul 26 '12 at 12:20











  • And you are sure you are entering the correct credentials?

    – Bobby
    Jul 26 '12 at 12:21











  • Yea, when I press Ctrl+Alt+F1 I can easily log into the console.

    – Seven of Nine
    Jul 26 '12 at 12:22






  • 1





    According to the wiki, login information may be wrong in the logs, so this could be another issue. Check again after correcting this, maybe : wiki.archlinux.org/index.php/SLiM#Login_information_with_SLiM

    – Nicolas Barbey
    Jul 26 '12 at 12:47



















  • It keeps asking for the password, or it logs in, tries to create the X-Session, then fails and throws you back at the login?

    – Bobby
    Jul 26 '12 at 12:18











  • I enter my username&password but it keeps asking for them. In the logs it says "failed to authenticate"

    – Seven of Nine
    Jul 26 '12 at 12:20











  • And you are sure you are entering the correct credentials?

    – Bobby
    Jul 26 '12 at 12:21











  • Yea, when I press Ctrl+Alt+F1 I can easily log into the console.

    – Seven of Nine
    Jul 26 '12 at 12:22






  • 1





    According to the wiki, login information may be wrong in the logs, so this could be another issue. Check again after correcting this, maybe : wiki.archlinux.org/index.php/SLiM#Login_information_with_SLiM

    – Nicolas Barbey
    Jul 26 '12 at 12:47

















It keeps asking for the password, or it logs in, tries to create the X-Session, then fails and throws you back at the login?

– Bobby
Jul 26 '12 at 12:18





It keeps asking for the password, or it logs in, tries to create the X-Session, then fails and throws you back at the login?

– Bobby
Jul 26 '12 at 12:18













I enter my username&password but it keeps asking for them. In the logs it says "failed to authenticate"

– Seven of Nine
Jul 26 '12 at 12:20





I enter my username&password but it keeps asking for them. In the logs it says "failed to authenticate"

– Seven of Nine
Jul 26 '12 at 12:20













And you are sure you are entering the correct credentials?

– Bobby
Jul 26 '12 at 12:21





And you are sure you are entering the correct credentials?

– Bobby
Jul 26 '12 at 12:21













Yea, when I press Ctrl+Alt+F1 I can easily log into the console.

– Seven of Nine
Jul 26 '12 at 12:22





Yea, when I press Ctrl+Alt+F1 I can easily log into the console.

– Seven of Nine
Jul 26 '12 at 12:22




1




1





According to the wiki, login information may be wrong in the logs, so this could be another issue. Check again after correcting this, maybe : wiki.archlinux.org/index.php/SLiM#Login_information_with_SLiM

– Nicolas Barbey
Jul 26 '12 at 12:47





According to the wiki, login information may be wrong in the logs, so this could be another issue. Check again after correcting this, maybe : wiki.archlinux.org/index.php/SLiM#Login_information_with_SLiM

– Nicolas Barbey
Jul 26 '12 at 12:47










3 Answers
3






active

oldest

votes


















0














For reference, the archlinux wiki is a treasure trove :
https://wiki.archlinux.org/index.php/SLiM



There is a typo in your script. All clk-launch-session should read ck-launch-session



Also, did you make .xinitrc executable ?



chmod +x ~/.xinitrc





share|improve this answer
























  • oh sorry, that ck-clk mistype is only here, in the actual file it's alright.

    – Seven of Nine
    Jul 26 '12 at 12:37











  • but this doesnt work :[

    – Seven of Nine
    Jul 26 '12 at 12:52











  • Could you fix the logs issue as asked in my previous comment, show us the logs and fix the typo in the question ?

    – Nicolas Barbey
    Jul 26 '12 at 13:54











  • I tried to but I'm a bit new to Linux. I'm usually able to work out these errors but now..

    – Seven of Nine
    Jul 26 '12 at 14:04











  • From the log, it seems that authentication did not fail on user login, so it may be the window manager.

    – Nicolas Barbey
    Jul 26 '12 at 14:10



















0














You have to do a bit of extra work to start X in virtualbox with archlinux. You can find it on the wiki here, copied and pasted below.



Installing Arch under VirtualBox is straightforward, and additions should be installed through pacman (not through "Install Guest Additions" in VirtualBox, or a mounted ISO.) Follow these instructions after doing a basic install of the X-window system found on the Beginners' Guide.



Guest additions package



Install virtualbox-archlinux-additions.



Kernel modules



Manually load the VirtualBox modules with



# modprobe -a vboxguest vboxsf vboxvideo



Auto-start modules



To autostart these modules each time you boot, you can add the three modules above to the MODULES array in /etc/rc.conf.



MODULES=(... vboxguest vboxsf vboxvideo)



Enable VboxClient-all



The VBoxClient contain these services(/usr/bin/VBoxClient-all) (copy/paste...) :



 --clipboard        start the shared clipboard service
--display start the display management service
--checkhostversion start the host version notifier service
--seamless start the seamless windows service


So you can Enable VBoxClient-all to start all these services.



If you are running something that launches /etc/xdg/autostart/vboxclient.desktop, such as GNOME, then you should be ready to go. If you use .xinitrc to launch things instead, you must add



VBoxClient-all &


to your .xinitrc before launching your WM. You should now be all set, and all guest additions should work properly.






share|improve this answer
























  • I've done that modprobe and MODULES thing but I'm not quite sure how my .xinitrc should look like. I added that line, but it made no difference.

    – Seven of Nine
    Jul 26 '12 at 19:13











  • put VBoxClient-all & a line above the case $1 in. I'll be heading home shortly and can help more when I get home.

    – Rob
    Jul 26 '12 at 19:21











  • I did that and no effect. ><

    – Seven of Nine
    Jul 26 '12 at 19:30











  • You can ask for help in #archlinux on irc.freenode.net with an IRC client, and I'll be back on to give you more information when I get home. What is the host OS?

    – Rob
    Jul 26 '12 at 19:34











  • host OS? You mean the OS that's running VirtualBox? Win7 64

    – Seven of Nine
    Jul 26 '12 at 19:47



















-1














I am using OpenBSD 6.0 and I installed SLIM. I could login with root or my username. I made a huge mistake. I checked the box during logout labeled: "Save session for future logins". I could get in from then only as root but not my regular username. So through much looking around I found that I had a .cache/ folder. so I deleted all the saved sessions in ~/.cache/sessions/ and then I was able to login as my regular user again.
Of course make sure you try a logout and ensure to uncheck that box before going through with the logout. I tried it and got back in no problem and no more sessions were saved in ~/.cache/sessions/ .



I hope this helps you all.



Kevin T






share|improve this answer
























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "3"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f453841%2fwhy-is-slim-stuck-at-the-login-screen%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    3 Answers
    3






    active

    oldest

    votes








    3 Answers
    3






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    For reference, the archlinux wiki is a treasure trove :
    https://wiki.archlinux.org/index.php/SLiM



    There is a typo in your script. All clk-launch-session should read ck-launch-session



    Also, did you make .xinitrc executable ?



    chmod +x ~/.xinitrc





    share|improve this answer
























    • oh sorry, that ck-clk mistype is only here, in the actual file it's alright.

      – Seven of Nine
      Jul 26 '12 at 12:37











    • but this doesnt work :[

      – Seven of Nine
      Jul 26 '12 at 12:52











    • Could you fix the logs issue as asked in my previous comment, show us the logs and fix the typo in the question ?

      – Nicolas Barbey
      Jul 26 '12 at 13:54











    • I tried to but I'm a bit new to Linux. I'm usually able to work out these errors but now..

      – Seven of Nine
      Jul 26 '12 at 14:04











    • From the log, it seems that authentication did not fail on user login, so it may be the window manager.

      – Nicolas Barbey
      Jul 26 '12 at 14:10
















    0














    For reference, the archlinux wiki is a treasure trove :
    https://wiki.archlinux.org/index.php/SLiM



    There is a typo in your script. All clk-launch-session should read ck-launch-session



    Also, did you make .xinitrc executable ?



    chmod +x ~/.xinitrc





    share|improve this answer
























    • oh sorry, that ck-clk mistype is only here, in the actual file it's alright.

      – Seven of Nine
      Jul 26 '12 at 12:37











    • but this doesnt work :[

      – Seven of Nine
      Jul 26 '12 at 12:52











    • Could you fix the logs issue as asked in my previous comment, show us the logs and fix the typo in the question ?

      – Nicolas Barbey
      Jul 26 '12 at 13:54











    • I tried to but I'm a bit new to Linux. I'm usually able to work out these errors but now..

      – Seven of Nine
      Jul 26 '12 at 14:04











    • From the log, it seems that authentication did not fail on user login, so it may be the window manager.

      – Nicolas Barbey
      Jul 26 '12 at 14:10














    0












    0








    0







    For reference, the archlinux wiki is a treasure trove :
    https://wiki.archlinux.org/index.php/SLiM



    There is a typo in your script. All clk-launch-session should read ck-launch-session



    Also, did you make .xinitrc executable ?



    chmod +x ~/.xinitrc





    share|improve this answer













    For reference, the archlinux wiki is a treasure trove :
    https://wiki.archlinux.org/index.php/SLiM



    There is a typo in your script. All clk-launch-session should read ck-launch-session



    Also, did you make .xinitrc executable ?



    chmod +x ~/.xinitrc






    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered Jul 26 '12 at 12:35









    Nicolas BarbeyNicolas Barbey

    1012




    1012













    • oh sorry, that ck-clk mistype is only here, in the actual file it's alright.

      – Seven of Nine
      Jul 26 '12 at 12:37











    • but this doesnt work :[

      – Seven of Nine
      Jul 26 '12 at 12:52











    • Could you fix the logs issue as asked in my previous comment, show us the logs and fix the typo in the question ?

      – Nicolas Barbey
      Jul 26 '12 at 13:54











    • I tried to but I'm a bit new to Linux. I'm usually able to work out these errors but now..

      – Seven of Nine
      Jul 26 '12 at 14:04











    • From the log, it seems that authentication did not fail on user login, so it may be the window manager.

      – Nicolas Barbey
      Jul 26 '12 at 14:10



















    • oh sorry, that ck-clk mistype is only here, in the actual file it's alright.

      – Seven of Nine
      Jul 26 '12 at 12:37











    • but this doesnt work :[

      – Seven of Nine
      Jul 26 '12 at 12:52











    • Could you fix the logs issue as asked in my previous comment, show us the logs and fix the typo in the question ?

      – Nicolas Barbey
      Jul 26 '12 at 13:54











    • I tried to but I'm a bit new to Linux. I'm usually able to work out these errors but now..

      – Seven of Nine
      Jul 26 '12 at 14:04











    • From the log, it seems that authentication did not fail on user login, so it may be the window manager.

      – Nicolas Barbey
      Jul 26 '12 at 14:10

















    oh sorry, that ck-clk mistype is only here, in the actual file it's alright.

    – Seven of Nine
    Jul 26 '12 at 12:37





    oh sorry, that ck-clk mistype is only here, in the actual file it's alright.

    – Seven of Nine
    Jul 26 '12 at 12:37













    but this doesnt work :[

    – Seven of Nine
    Jul 26 '12 at 12:52





    but this doesnt work :[

    – Seven of Nine
    Jul 26 '12 at 12:52













    Could you fix the logs issue as asked in my previous comment, show us the logs and fix the typo in the question ?

    – Nicolas Barbey
    Jul 26 '12 at 13:54





    Could you fix the logs issue as asked in my previous comment, show us the logs and fix the typo in the question ?

    – Nicolas Barbey
    Jul 26 '12 at 13:54













    I tried to but I'm a bit new to Linux. I'm usually able to work out these errors but now..

    – Seven of Nine
    Jul 26 '12 at 14:04





    I tried to but I'm a bit new to Linux. I'm usually able to work out these errors but now..

    – Seven of Nine
    Jul 26 '12 at 14:04













    From the log, it seems that authentication did not fail on user login, so it may be the window manager.

    – Nicolas Barbey
    Jul 26 '12 at 14:10





    From the log, it seems that authentication did not fail on user login, so it may be the window manager.

    – Nicolas Barbey
    Jul 26 '12 at 14:10













    0














    You have to do a bit of extra work to start X in virtualbox with archlinux. You can find it on the wiki here, copied and pasted below.



    Installing Arch under VirtualBox is straightforward, and additions should be installed through pacman (not through "Install Guest Additions" in VirtualBox, or a mounted ISO.) Follow these instructions after doing a basic install of the X-window system found on the Beginners' Guide.



    Guest additions package



    Install virtualbox-archlinux-additions.



    Kernel modules



    Manually load the VirtualBox modules with



    # modprobe -a vboxguest vboxsf vboxvideo



    Auto-start modules



    To autostart these modules each time you boot, you can add the three modules above to the MODULES array in /etc/rc.conf.



    MODULES=(... vboxguest vboxsf vboxvideo)



    Enable VboxClient-all



    The VBoxClient contain these services(/usr/bin/VBoxClient-all) (copy/paste...) :



     --clipboard        start the shared clipboard service
    --display start the display management service
    --checkhostversion start the host version notifier service
    --seamless start the seamless windows service


    So you can Enable VBoxClient-all to start all these services.



    If you are running something that launches /etc/xdg/autostart/vboxclient.desktop, such as GNOME, then you should be ready to go. If you use .xinitrc to launch things instead, you must add



    VBoxClient-all &


    to your .xinitrc before launching your WM. You should now be all set, and all guest additions should work properly.






    share|improve this answer
























    • I've done that modprobe and MODULES thing but I'm not quite sure how my .xinitrc should look like. I added that line, but it made no difference.

      – Seven of Nine
      Jul 26 '12 at 19:13











    • put VBoxClient-all & a line above the case $1 in. I'll be heading home shortly and can help more when I get home.

      – Rob
      Jul 26 '12 at 19:21











    • I did that and no effect. ><

      – Seven of Nine
      Jul 26 '12 at 19:30











    • You can ask for help in #archlinux on irc.freenode.net with an IRC client, and I'll be back on to give you more information when I get home. What is the host OS?

      – Rob
      Jul 26 '12 at 19:34











    • host OS? You mean the OS that's running VirtualBox? Win7 64

      – Seven of Nine
      Jul 26 '12 at 19:47
















    0














    You have to do a bit of extra work to start X in virtualbox with archlinux. You can find it on the wiki here, copied and pasted below.



    Installing Arch under VirtualBox is straightforward, and additions should be installed through pacman (not through "Install Guest Additions" in VirtualBox, or a mounted ISO.) Follow these instructions after doing a basic install of the X-window system found on the Beginners' Guide.



    Guest additions package



    Install virtualbox-archlinux-additions.



    Kernel modules



    Manually load the VirtualBox modules with



    # modprobe -a vboxguest vboxsf vboxvideo



    Auto-start modules



    To autostart these modules each time you boot, you can add the three modules above to the MODULES array in /etc/rc.conf.



    MODULES=(... vboxguest vboxsf vboxvideo)



    Enable VboxClient-all



    The VBoxClient contain these services(/usr/bin/VBoxClient-all) (copy/paste...) :



     --clipboard        start the shared clipboard service
    --display start the display management service
    --checkhostversion start the host version notifier service
    --seamless start the seamless windows service


    So you can Enable VBoxClient-all to start all these services.



    If you are running something that launches /etc/xdg/autostart/vboxclient.desktop, such as GNOME, then you should be ready to go. If you use .xinitrc to launch things instead, you must add



    VBoxClient-all &


    to your .xinitrc before launching your WM. You should now be all set, and all guest additions should work properly.






    share|improve this answer
























    • I've done that modprobe and MODULES thing but I'm not quite sure how my .xinitrc should look like. I added that line, but it made no difference.

      – Seven of Nine
      Jul 26 '12 at 19:13











    • put VBoxClient-all & a line above the case $1 in. I'll be heading home shortly and can help more when I get home.

      – Rob
      Jul 26 '12 at 19:21











    • I did that and no effect. ><

      – Seven of Nine
      Jul 26 '12 at 19:30











    • You can ask for help in #archlinux on irc.freenode.net with an IRC client, and I'll be back on to give you more information when I get home. What is the host OS?

      – Rob
      Jul 26 '12 at 19:34











    • host OS? You mean the OS that's running VirtualBox? Win7 64

      – Seven of Nine
      Jul 26 '12 at 19:47














    0












    0








    0







    You have to do a bit of extra work to start X in virtualbox with archlinux. You can find it on the wiki here, copied and pasted below.



    Installing Arch under VirtualBox is straightforward, and additions should be installed through pacman (not through "Install Guest Additions" in VirtualBox, or a mounted ISO.) Follow these instructions after doing a basic install of the X-window system found on the Beginners' Guide.



    Guest additions package



    Install virtualbox-archlinux-additions.



    Kernel modules



    Manually load the VirtualBox modules with



    # modprobe -a vboxguest vboxsf vboxvideo



    Auto-start modules



    To autostart these modules each time you boot, you can add the three modules above to the MODULES array in /etc/rc.conf.



    MODULES=(... vboxguest vboxsf vboxvideo)



    Enable VboxClient-all



    The VBoxClient contain these services(/usr/bin/VBoxClient-all) (copy/paste...) :



     --clipboard        start the shared clipboard service
    --display start the display management service
    --checkhostversion start the host version notifier service
    --seamless start the seamless windows service


    So you can Enable VBoxClient-all to start all these services.



    If you are running something that launches /etc/xdg/autostart/vboxclient.desktop, such as GNOME, then you should be ready to go. If you use .xinitrc to launch things instead, you must add



    VBoxClient-all &


    to your .xinitrc before launching your WM. You should now be all set, and all guest additions should work properly.






    share|improve this answer













    You have to do a bit of extra work to start X in virtualbox with archlinux. You can find it on the wiki here, copied and pasted below.



    Installing Arch under VirtualBox is straightforward, and additions should be installed through pacman (not through "Install Guest Additions" in VirtualBox, or a mounted ISO.) Follow these instructions after doing a basic install of the X-window system found on the Beginners' Guide.



    Guest additions package



    Install virtualbox-archlinux-additions.



    Kernel modules



    Manually load the VirtualBox modules with



    # modprobe -a vboxguest vboxsf vboxvideo



    Auto-start modules



    To autostart these modules each time you boot, you can add the three modules above to the MODULES array in /etc/rc.conf.



    MODULES=(... vboxguest vboxsf vboxvideo)



    Enable VboxClient-all



    The VBoxClient contain these services(/usr/bin/VBoxClient-all) (copy/paste...) :



     --clipboard        start the shared clipboard service
    --display start the display management service
    --checkhostversion start the host version notifier service
    --seamless start the seamless windows service


    So you can Enable VBoxClient-all to start all these services.



    If you are running something that launches /etc/xdg/autostart/vboxclient.desktop, such as GNOME, then you should be ready to go. If you use .xinitrc to launch things instead, you must add



    VBoxClient-all &


    to your .xinitrc before launching your WM. You should now be all set, and all guest additions should work properly.







    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered Jul 26 '12 at 18:25









    RobRob

    1,79221831




    1,79221831













    • I've done that modprobe and MODULES thing but I'm not quite sure how my .xinitrc should look like. I added that line, but it made no difference.

      – Seven of Nine
      Jul 26 '12 at 19:13











    • put VBoxClient-all & a line above the case $1 in. I'll be heading home shortly and can help more when I get home.

      – Rob
      Jul 26 '12 at 19:21











    • I did that and no effect. ><

      – Seven of Nine
      Jul 26 '12 at 19:30











    • You can ask for help in #archlinux on irc.freenode.net with an IRC client, and I'll be back on to give you more information when I get home. What is the host OS?

      – Rob
      Jul 26 '12 at 19:34











    • host OS? You mean the OS that's running VirtualBox? Win7 64

      – Seven of Nine
      Jul 26 '12 at 19:47



















    • I've done that modprobe and MODULES thing but I'm not quite sure how my .xinitrc should look like. I added that line, but it made no difference.

      – Seven of Nine
      Jul 26 '12 at 19:13











    • put VBoxClient-all & a line above the case $1 in. I'll be heading home shortly and can help more when I get home.

      – Rob
      Jul 26 '12 at 19:21











    • I did that and no effect. ><

      – Seven of Nine
      Jul 26 '12 at 19:30











    • You can ask for help in #archlinux on irc.freenode.net with an IRC client, and I'll be back on to give you more information when I get home. What is the host OS?

      – Rob
      Jul 26 '12 at 19:34











    • host OS? You mean the OS that's running VirtualBox? Win7 64

      – Seven of Nine
      Jul 26 '12 at 19:47

















    I've done that modprobe and MODULES thing but I'm not quite sure how my .xinitrc should look like. I added that line, but it made no difference.

    – Seven of Nine
    Jul 26 '12 at 19:13





    I've done that modprobe and MODULES thing but I'm not quite sure how my .xinitrc should look like. I added that line, but it made no difference.

    – Seven of Nine
    Jul 26 '12 at 19:13













    put VBoxClient-all & a line above the case $1 in. I'll be heading home shortly and can help more when I get home.

    – Rob
    Jul 26 '12 at 19:21





    put VBoxClient-all & a line above the case $1 in. I'll be heading home shortly and can help more when I get home.

    – Rob
    Jul 26 '12 at 19:21













    I did that and no effect. ><

    – Seven of Nine
    Jul 26 '12 at 19:30





    I did that and no effect. ><

    – Seven of Nine
    Jul 26 '12 at 19:30













    You can ask for help in #archlinux on irc.freenode.net with an IRC client, and I'll be back on to give you more information when I get home. What is the host OS?

    – Rob
    Jul 26 '12 at 19:34





    You can ask for help in #archlinux on irc.freenode.net with an IRC client, and I'll be back on to give you more information when I get home. What is the host OS?

    – Rob
    Jul 26 '12 at 19:34













    host OS? You mean the OS that's running VirtualBox? Win7 64

    – Seven of Nine
    Jul 26 '12 at 19:47





    host OS? You mean the OS that's running VirtualBox? Win7 64

    – Seven of Nine
    Jul 26 '12 at 19:47











    -1














    I am using OpenBSD 6.0 and I installed SLIM. I could login with root or my username. I made a huge mistake. I checked the box during logout labeled: "Save session for future logins". I could get in from then only as root but not my regular username. So through much looking around I found that I had a .cache/ folder. so I deleted all the saved sessions in ~/.cache/sessions/ and then I was able to login as my regular user again.
    Of course make sure you try a logout and ensure to uncheck that box before going through with the logout. I tried it and got back in no problem and no more sessions were saved in ~/.cache/sessions/ .



    I hope this helps you all.



    Kevin T






    share|improve this answer




























      -1














      I am using OpenBSD 6.0 and I installed SLIM. I could login with root or my username. I made a huge mistake. I checked the box during logout labeled: "Save session for future logins". I could get in from then only as root but not my regular username. So through much looking around I found that I had a .cache/ folder. so I deleted all the saved sessions in ~/.cache/sessions/ and then I was able to login as my regular user again.
      Of course make sure you try a logout and ensure to uncheck that box before going through with the logout. I tried it and got back in no problem and no more sessions were saved in ~/.cache/sessions/ .



      I hope this helps you all.



      Kevin T






      share|improve this answer


























        -1












        -1








        -1







        I am using OpenBSD 6.0 and I installed SLIM. I could login with root or my username. I made a huge mistake. I checked the box during logout labeled: "Save session for future logins". I could get in from then only as root but not my regular username. So through much looking around I found that I had a .cache/ folder. so I deleted all the saved sessions in ~/.cache/sessions/ and then I was able to login as my regular user again.
        Of course make sure you try a logout and ensure to uncheck that box before going through with the logout. I tried it and got back in no problem and no more sessions were saved in ~/.cache/sessions/ .



        I hope this helps you all.



        Kevin T






        share|improve this answer













        I am using OpenBSD 6.0 and I installed SLIM. I could login with root or my username. I made a huge mistake. I checked the box during logout labeled: "Save session for future logins". I could get in from then only as root but not my regular username. So through much looking around I found that I had a .cache/ folder. so I deleted all the saved sessions in ~/.cache/sessions/ and then I was able to login as my regular user again.
        Of course make sure you try a logout and ensure to uncheck that box before going through with the logout. I tried it and got back in no problem and no more sessions were saved in ~/.cache/sessions/ .



        I hope this helps you all.



        Kevin T







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 12 '16 at 21:56









        TDKTDK

        11




        11






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Super User!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f453841%2fwhy-is-slim-stuck-at-the-login-screen%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            If I really need a card on my start hand, how many mulligans make sense? [duplicate]

            Alcedinidae

            Can an atomic nucleus contain both particles and antiparticles? [duplicate]