Slim Failed To Execute Login Command Freebsd
Offline #24 2014-12-24 04:20:23 kenizl86 Member Registered: 2014-12-10 Posts: 33 Re: [SOLVED] Login in #! not working ("failed to execute login command") hello kenizl, i think the solution to your problem is to find out why you got "failed to execute login" in the first place.the I followed the following doc without any problems in Slackware64 14.1: http://docs.slackware.com/howtos:win...m?s=slim However, running 'xwmconfig' as suggested in the doc, does not generate either an .xinitrc and/or an .xsession in Slackware As far as I can tell this file is supposed to be created by xorg-xinit, which I have already installed. have a peek at this web-site
How do you remove .deb installs?I'll take a look at that thread that Head_on_a_Stick gave me also................. Die Hard From: Heavener, OK Registered: 2014-12-09 Posts: 777 Re: [SOLVED] Login in #! Ubuntu Logo, Ubuntu and Canonical © Canonical Ltd. Debian is a registered trademark of Software in the Public Interest, Inc.
Slim Failed To Execute Login Command Freebsd
Offline Help fund CrunchBang, donate to the project! #25 2014-12-24 04:35:50 damo #! Prepended to the session name when pressing F1 # session_msg Session: # shutdown / reboot messages shutdown_msg The system is halting... Prepended to the session name when pressing F1 # session_msg Session: # shutdown / reboot messages shutdown_msg The system is halting...
Run:sudo update-alternatives --config x-session-managerand make sure the session is openbox2. My understanding having read the wiki was that display managers were used to provide a graphical login screen instead of booting to the command line. After attempting a login the new user /home has been populated. Slim Arch Linux Offline #16 2014-12-18 16:52:16 damo #!
I have openbox as window manager, cairodock, and SLiM as my display manager. Slim Failed To Execute Login Command Arch gimpbanger From: N51.5 W002.8 (mostly) Registered: 2011-11-24 Posts: 5,433 Re: [SOLVED] Login in #! permalinkembedsavegive gold[â€“][deleted] 0 points1 point2 points 2 years ago(2 children)I'm a bit new to this sorry, what's the framebuffer? https://www.reddit.com/r/archlinux/comments/2gaba1/slim_failed_to_execute_login_command/ Using Debian ~ Debian Reference ~ CrunchBang FAQAdvice For New Users On Not Breaking Their Debian SystemForum Moderator Offline #13 2014-12-14 11:00:51 ohnonot ...again Registered: 2012-05-22 Posts: 2,205 Re: [SOLVED] Login
Offline #20 2014-12-23 18:10:27 kenizl86 Member Registered: 2014-12-10 Posts: 33 Re: [SOLVED] Login in #! Freebsd Slim Last edited by zippy morocco (2013-10-21 10:18:02) Offline #8 2013-10-21 10:13:51 oliver Administrator Registered: 2010-11-04 Posts: 2,209 Re: [Solved] Slim wont allow login Failed to execute login.... not working ("failed to execute login command") Pages: 1 2 Next #1 2014-12-10 16:43:24 kenizl86 Member Registered: 2014-12-10 Posts: 33 [SOLVED] Login in #! Offline #4 2014-12-12 03:59:20 kenizl86 Member Registered: 2014-12-10 Posts: 33 Re: [SOLVED] Login in #!
Slim Failed To Execute Login Command Arch
Search this Thread 02-11-2016, 02:54 PM #1 globetrotterdk Member Registered: Nov 2006 Posts: 52 Rep: SLiM - Failed to execute login command. The following two tabs change content below.BioLatest Posts Eugen MihailescuFounder/programmer/one-man-show at Cubique Software Always looking to learn more about *nix world, about the fundamental concepts of math, physics, electronics. Slim Failed To Execute Login Command Freebsd slim: waiting for X server to begin accepting connections. Failed To Execute Login Command Arch Linux Are you new to LinuxQuestions.org?
not working ("failed to execute login command") So I installed #! Check This Out Openbox doesn't seem present at least none of the windows are there. If I choose something else then %session="something else". User Name Remember Me? Freebsd Mate Failed To Execute Login Command
Make a file .xsession in home folder with this content:#! /bin/bash /bin/bash --login -i ~/.xinitrc Last edited by kenizl86 (2014-12-26 02:08:18) When life gives you lemons, chuck 'em at people. I enabled SLiM on startup using systemctl, and now the computer boots to the login screen instead of the command line. Not being part of that group will cause your sudo command to fail.You can check it by just running groups. Source for freebsd use: # login_cmd exec /bin/sh - ~/.xinitrc %session login_cmd exec /bin/bash -login /etc/X11/Xsession %session # Commands executed when starting and exiting a session. # They can be used for
A heads up for the Slackware developers. Freebsd Install Mate It still did it after I put it in there when I did it. I did use the useradd command following the wiki.
I'll boot up my SeaTools and check and write back the results.
sudo cp /home/zippy/.xinitrc /home/
My advice would be using another one. Copied the default script into my home directory and added exec cinnamon-session to it, which seems to let it load Cinnamon. Proudly powered by Debian. have a peek here LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware [SOLVED] SLiM - Failed to execute login command.
ha. Offline #7 2013-01-25 13:37:11 cedricl Member Registered: 2012-10-16 Posts: 16 Re: [SOLVED] slim v1.3.5-1: "failed to execute login command" Solved :In v1.3.5 slim probably not preset any default session name unlike So I renamed the file back to .xsession, and lo-and-behold I can login again.Thanks for the help by the way! not working ("failed to execute login command") Also, to help with the shutdown, would what this article says work?
not working ("failed to execute login command") Here's my sources.list:## CRUNCHBANG ## Compatible with Debian Wheezy, but use at your own risk. When life gives you lemons, chuck 'em at people. yars View Public Profile View LQ Blog View Review Entries View HCL Entries Find More Posts by yars 02-13-2016, 09:41 AM #4 globetrotterdk Member Registered: Nov 2006 Posts: 52 Offline #3 2013-10-20 21:16:12 zippy morocco Member Registered: 2012-12-08 Posts: 19 Re: [Solved] Slim wont allow login Failed to execute login....
Or do I have to do something about the fact that I enabled it on startup using systemctl as well?