[SOLVED]SliM and .xinitrc

Hey guys me again
Ive just installed Slim. and changed my rc.conf putting slim in the correct area, slim boots up fine. and then when i login it says that it failed to load session. so i checked my ~/.xinitrc
exec ck-launch-session dbus-launch openbox-session
and it all seems proper. so im not sure what im missing
Last edited by nankura (2012-04-28 03:41:38)

adamrehard wrote:It looks good to me too. Hmmm.
Do you need to use consolekit and dbus?
Have you tried it using just startx or xinit?
Is .xinitrc executable?
That's all I've got. Hope it helps.
Problem solved. i was missing xorg-xinit from the repos. pacman installation fixed the issue and XAUTH
Last edited by nankura (2012-04-28 03:41:25)

Similar Messages

[SOLVED]Slim and gdm questions

Hi all,
I just installed slim cause I wanted to try something new and faster than gdm login manager for gnome, I have it working right now but with a few hiccups:
1- I login using slim, but after I am logged in the system if I lock the screen, the gdm login shows (instead of the slim one)
2- System bootup is a LOT slower, after I login the system stays with just the background for a few seconds, then loads the desktop.
So, here are my questions:
a) If I remove gdm will I have this same issues? maybe the increased boot time is because I have 2 login managers installed?
b) I disabled the gdm daemon from rc.conf (put a ! before it), should I remove it from there completely? because apparently it is still loading.
Also I dont know much about login managers so I wanted a little enlightenment in this matter.
regards and thanks in advance
Last edited by 655321 (2010-06-13 20:57:35)

BKLive
Here is the info:
slim.conf
# Path, X server and arguments (if needed)
# Note: -xauth $authfile is automatically appended
default_path ./:/bin:/usr/bin:/usr/local/bin
default_xserver /usr/bin/X
xserver_arguments -nolisten tcp vt07
# Commands for halt, login, etc.
halt_cmd /sbin/shutdown -h now
reboot_cmd /sbin/shutdown -r now
console_cmd /usr/bin/xterm -C -fg white -bg black +sb -T "Console login" -e /bin/sh -c "/bin/cat /etc/issue; exec /bin/login"
#suspend_cmd /usr/sbin/suspend
# Full path to the xauth binary
xauth_path /usr/bin/xauth
# Xauth file for server
authfile /var/run/slim.auth
# Activate numlock when slim starts. Valid values: on|off
# numlock on
# Hide the mouse cursor (note: does not work with some WMs).
# Valid values: true|false
# hidecursor false
# This command is executed after a succesful login.
# you can place the %session and %theme variables
# to handle launching of specific commands in .xinitrc
# depending of chosen session and slim theme
# NOTE: if your system does not have bash you need
# to adjust the command according to your preferred shell,
# i.e. for freebsd use:
# login_cmd exec /bin/sh - ~/.xinitrc %session
login_cmd exec /bin/bash -login ~/.xinitrc %session
# Commands executed when starting and exiting a session.
# They can be used for registering a X11 session with
# sessreg. You can use the %user variable
# sessionstart_cmd some command
# sessionstop_cmd some command
# Start in daemon mode. Valid values: yes | no
# Note that this can be overriden by the command line
# options "-d" and "-nodaemon"
# daemon yes
# Available sessions (first one is the default).
# The current chosen session name is replaced in the login_cmd
# above, so your login command can handle different sessions.
# see the xinitrc.sample file shipped with slim sources
sessions xfce4,icewm,wmaker,blackbox
# Executed when pressing F11 (requires imagemagick)
screenshot_cmd import -window root /slim.png
# welcome message. Available variables: %host, %domain
welcome_msg Welcome to %host
# Session message. Prepended to the session name when pressing F1
# session_msg Session:
# shutdown / reboot messages
shutdown_msg The system is halting...
reboot_msg The system is rebooting...
# default user, leave blank or remove this line
# for avoid pre-loading the username.
#default_user simone
# Focus the password field on start when default_user is set
# Set to "yes" to enable this feature
#focus_password no
# Automatically login the default user (without entering
# the password. Set to "yes" to enable this feature
#auto_login no
# current theme, use comma separated list to specify a set to
# randomly choose from
#current_theme default
current_theme archlinux-darch-white
# Lock file
lockfile /var/lock/slim.lock
# Log file
logfile /var/log/slim.log
~/.xinitrc:
#!/bin/sh
# ~/.xinitrc
# Executed by startx (run your window manager from here)
# exec gnome-session
# exec startkde
# exec startxfce4
# ...or the Window Manager of your choice
#exec xterm
setxkbmap -option terminate:ctrl_alt_bksp
exec ck-launch-session gnome-session
Regarding whats runs at bootup, I guess you want to see my daemons array in rc.conf, here it is:
DAEMONS=(syslog-ng dbus hal network netfs crond alsa @cups slim !gdm)
Notice gdm is disabled.
Also, would you advice to reinstall gdm? removing it didnt do anything for the problem im experiencing.
thanks for the help

[solved]Slim and new consolekit

Hey all. Just wondering if the the newest version of Slim that came out on January 31st, Slim 1.3.2.-3, works completely fine now with the newest version of consolekit?
EDIT:
Just installed slim again and everything seems to be fixed. Working with consolekit again!
Last edited by orlfman (2011-02-03 05:02:17)

Using Slim and LXDE. Suspend and hibernate from lxde-logout didn't work and an unpriviledged account I created coudn't access mixer device or mount removable drives without being added to the 'audio' and 'storage' groups after the initial upgrade to new consolekit. But after the very latest upgrades of packages 'slim' and 'consolekit' everything is AFAIK back to working just as before. Unless I stumble over something new I'd say stuff are just OK as of today.
(Remember to merge any /etc/pam.d/login.pacnew to /etc/pam.d/login. Threads suggests that those that forgot got real problems.)

[SOLVED] Dwm and slim problem.

i installed dwm and slim in my arch and now i cant go back to the terminal to do changes, it puts me on the log in (slim) and i cant close it, i want to do changes in ~/xinitrc.
Please help me.
Thanks.
Last edited by Iason (2010-09-13 07:47:02)

Alt-F2
If that doesn't work, Alt-F3
If that doesn't work, Alt-F4
If that doesn't work try again but with Ctrl-Alt-F2, etc.
If that doesn't work come back here.
edit: *shakes fist at jasonwryan* *sticks out tongue at thayer*
Last edited by fsckd (2010-09-12 21:47:51)

[SOLVED] Slim not starting Openbox

Hi :)
I've run a search through this forum and all, and I can't seem to solve my problem...
I've installed Arch on VirtualBox (so that I can try it out) and I installed Slim and Openbox.
The problem is that when I log in, the screen flickers, and Slim comes back up, as if openbox wasn't executed at all
Any of you guys has this setup? (slim and ob)
If so, please tell me how you configured it...
Thanks in advance
Last edited by pedro-kun (2007-08-05 18:09:56)

Here it is:
# Path, X server and arguments (if needed)
# Note: -xauth $authfile is automatically appended
default_path ./:/bin:/usr/bin:/usr/local/bin:/usr/bin
default_xserver /usr/bin/X
xserver_arguments -nolisten tcp vt07
# Commands for halt, login, etc.
halt_cmd /sbin/shutdown -h now
reboot_cmd /sbin/shutdown -r now
console_cmd /usr/bin/xterm -C -fg white -bg black +sb -T "Console login" -e /bin/sh -c "/bin/cat /etc/issue; exec /bin/login"
#suspend_cmd /usr/sbin/suspend
# Full path to the xauth binary
xauth_path /usr/bin/xauth
# Xauth file for server
authfile /var/run/slim.auth
# Activate numlock when slim starts. Valid values: on|off
# numlock on
# Hide the mouse cursor (note: does not work with some WMs).
# Valid values: true|false
# hidecursor false
# This command is executed after a succesful login.
# you can place the %session and %theme variables
# to handle launching of specific commands in .xinitrc
# depending of chosen session and slim theme
# NOTE: if your system does not have bash you need
# to adjust the command according to your preferred shell,
# i.e. for freebsd use:
# login_cmd exec /bin/sh - ~/.xinitrc %session
login_cmd exec /bin/bash -login ~/.xinitrc
# Commands executed when starting and exiting a session.
# They can be used for registering a X11 session with
# sessreg. You can use the %user variable
# sessionstart_cmd some command
# sessionstop_cmd some command
# Start in daemon mode. Valid values: yes | no
# Note that this can overridden by the command line
# option "-d"
# daemon yes
# Available sessions (first one is the default).
# The current chosen session name is replaced in the login_cmd
# above, so your login command can handle different sessions.
# see the xinitrc.sample file shipped with slim sources
# sessions xfce4,icewm,wmaker,blackbox
# Executed when pressing F11 (requires imagemagick)
screenshot_cmd import -window root /slim.png
# welcome message. Available variables: %host, %domain
welcome_msg Welcome to %host
# shutdown / reboot messages
shutdown_msg The system is halting...
reboot_msg The system is rebooting...
# default user, leave blank or remove this line
# for avoid pre-loading the username.
#default_user pedro
# current theme, use comma separated list to specify a set to
# randomly choose from
current_theme default
# Lock file
lockfile /var/lock/slim.lock
# Log file
logfile /var/log/slim.log
i got rid of the %session bit, and the sessions, because i'm gonna use only openbox. Either way, i don't think doing that has anything to do with the problem, because i think i tried it with the default slim.conf and it didn't work anyway.

[SOLVED] SLIM not boot to LXDE

Hello,
I have installed LXDE and I am able to load it via startx. (so I have .xinitrc properly configured [exec startlxde]).
I Have just installed slim and put it as daemon into rc.conf. Slim shows me his screen after sturtup, but I am not able to login with my user/name - it only blinks and shows slim screen again.
I thought there could be problem with file .xinitrc permissions so I have set it to 777, but it didn't help. (I am not sure - is it sufficient to have this file only in home directory of that user?)
Any idea?
Last edited by rhadesan (2011-05-04 07:29:40)

rhadesan wrote:It helps to remove pcmanfm. I do not understand what is the problem with tis package?
Well, the desktop in LXDE is managed by pcmanfm.. So, if pcmanfm crashes, maybe that causes problems.. Anyway, as noted in the other thread, this could be a bug in pcmanfm. We will have to wait for a fix in pcmanfm.. For now, either uninstall pcmanfm and use SLiM or else use a different DM/WM or login manager
If your problem is solved, please add "[SOLVED]" to the subject

[SOLVED] SLiM env switching doesn't work

Hello,
so today I wanted to try a different desktop environment, I already had set everything up a while ago in the slim.conf and xinitrc but the F1 doesn't do anything and it always starts a xfce session.
The thing is though, that back then when I actually changed the 2 configs the switching worked fine and according to the SLiM article on the arch wiki nothing has changed in the way how you configure this.
So is this a bug in recent version or did the config file format change or the files you need to modify?
thanks in advance!
Last edited by pfannkuchen_gesicht (2014-01-04 00:08:52)

there is nothing listed at all and when pressing F1 nothing happens either, when in the past the selected DEs name showed up on screen.
my .xinitrc looks exactly like the example on the SLiM archwiki page, just without the entries of the other DEs I don't have installed. I am also pretty sure it's not even an issue of the xinitrc since SLiM doesn't even display any DEs, it just starts xfce after entering the password.
EDIT: hm, I think the "sessiondir" setting was just missing, readded that and now it works. Odd though that it wasn't there anymore.
Last edited by pfannkuchen_gesicht (2014-01-03 23:14:35)

[SOLVED:] SLIM not reading slim.conf (no password auto-focus)

Yesterday I began having issues with SLIM. I'm not sure if they're related, but while running Puppy , I inadvertently deleted the desktop icon for my Arch home directory on /dev/sda8. I rebooted Puppy and it reappeared. After running Puppy, something went wrong with my clocks (system and hardware) and the times were all wrong. I fixed that with NTPD. I currently dual boot Arch and Windows 7 from the hard drive, and occasionally from a USB stick, Puppy Linux. I'm using an ASUS K50IJ laptop. I run Xfce4. I do not have any disk encryption enabled.
When I boot up, the SLIM login appears as normal, but rather than password auto-focus, I'm prompted for a username. If I enter the username and hit return, I'm still staring at the username prompt. After three or four iterations of entering a username + enter, I finally get a password prompt and can log in.
I have tried:
1. Reinstalling archlinux-themes-slim
2. Uninstalling archlinux-themes-slim and slim, then reinstalling slim
3. Removing old Xfce4 & Xfwm sessions
4. Removing slim.conf and entering a pristine version.
5. Reviewing /var/log/slim.log files for oddities. I found one:
Before the trouble started, I the message in the log was:
slim: waiting for X server to begin accepting connections
X.Org X Server 1.12.2
Release Date: 2012-05-29
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.0.32-1-lts x86_64
Current Operating System: Linux asus 3.4.4-2-ARCH #1 SMP PREEMPT Sun Jun 24 18:5
9:47 CEST 2012 x86_64
Kernel command line: root=/dev/sda4 ro
Build Date: 30 May 2012 07:24:13PM
Current version of pixman: 0.26.2
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sun Jul 8 15:30:48 2012
(==) Using config directory: "/etc/X11/xorg.conf.d"
/usr/bin/xauth: file /home/rasteenb/.Xauthority does not exist
/usr/bin/startxfce4: X server already running on display :0.0
Now I get:
slim: waiting for X server to begin accepting connections.slim: unexpected signal 15
slim: waiting for X server to begin accepting connections.
slim: System is booting up.
slim: pam_authentication(): Authentication failure
slim: System is booting up.
slim: pam_authentication(): Authentication failure
slim: System is booting up.
slim: pam_authentication(): Authentication failure
slim: System is booting up.
slim: pam_authentication(): Authentication failure
slim: System is booting up.
slim: pam_authentication(): Authentication failure
Now I'm stumped.
Rob
Last edited by rasteenb (2012-07-17 11:16:03)

I solved this - slim was not the last daemon I started in rc.conf. By moving it to the end, I get password auto-focus and everything works.
Now my rc.conf looks like
# DAEMONS
DAEMONS=(syslog-ng dbus acpid @network @wicd @openntpd @cupsd @crond slim)
I found this recommendation in the Display Manager wiki page while researching the problem:
Ensure you start the display manager last in the DAEMONS array, otherwise X will later allocate a tty device which was previously claimed by Getty (see /etc/inittab). Not placing the display manager at the end can cause X crashes, and is therefore unsupported.
I'd just been lucky before that there wasn't a conflict.
There is a "flicker" during login where I'm shown the XFCE splash, then the SLIM splash again, then the XFCE desktop. Not sure what's going on there, but it's no big deal.
Cheers,
Rob

[SOLVED] Slim 1.3.2 & Xfce - shutdown buttons doesn't work

I'm running Xfce & Slim, and my Shutdown/restart/hibernate buttons are greyed out..
~/.xinitrc:
#!/bin/sh
# ~/.xinitrc
# Executed by startx (run your window manager from here)
if [ -d /etc/X11/xinit/xinitrc.d ]; then
for f in /etc/X11/xinit/xinitrc.d/*; do
[ -x "$f" ] && . "$f"
done
unset f
fi
exec startxfce4 --with-ck-launch
I'm in group power, and I have dbus in damons section in rc.conf...
#ps aux |grep -i dbus
ps aux |grep -i dbus
dbus 500 0.0 0.0 13724 1696 ? Ss 11:45 0:01 /usr/bin/dbus-daemon --system
drtic 9311 0.0 0.0 20112 516 ? S< 12:47 0:00 dbus-launch --autolaunch faf5e40fa2b384a828c369bb000001c0 --binary-syntax --close-stderr
drtic 9312 0.0 0.0 13092 1148 ? S<s 12:47 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
drtic 9329 0.0 0.0 20112 592 ? S 12:47 0:00 /usr/bin/dbus-launch --sh-syntax --exit-with-session
drtic 9330 0.0 0.0 14480 1948 ? Ss 12:47 0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
drtic 9928 0.1 0.0 13364 1576 ? S 13:03 0:02 /usr/bin/dbus-daemon --config-file=/etc/at-spi2/accessibility.conf --nofork --print-address 3
drtic 14037 0.0 0.0 8788 1052 pts/2 S+ 13:27 0:00 grep -i dbus
any ideas?
Last edited by drtic_cz (2012-06-21 13:21:00)

Terminator wrote:Since it's your first post:
Change the final line of your .xinitrc into 'exec startxfce' (without the --with-ck-launch).
Thanks, that worked for me.. I just read an article on archwiki, that ck-launch is not required since slim 1.3.3.
I'm using Slim 1.3.2, so I didn't try to remove it....
And of course, I searched a lot this forum, it occured after last upgrade, so I searched only few last pages.
Thanks again, marking it as solved

[SOLVED] systemd and ConsoleKit - I'm a little confused

I'm using SLIM and Openbox and am in the process of converting to systemd.
I've added the needed configuration files for systemd.
I can boot using the wiki instructions here https://wiki.archlinux.org/index.php/Sy … stallation
I've added SLIM as a service using https://wiki.archlinux.org/index.php/Sy … er_systemd
My question is: Do I still need ConsoleKit? So far this seems to be working for me but I'm not sure if I need to add ConsoleKit somehow.
BTW: I start Openbox with the usual
exec ck-launch-session openbox-session
when using initscripts.
Last edited by bergersau (2012-10-11 05:31:52)

Thanks WonderWoofy, I just double checked my ~/.xinitrc and found I had commented out ck-launch-session when I installed SLIM many moons ago - Sorry My Bad, I was working from my 'obviously flawed' memory.
As ConsoleKit is a dependency of SLIM I'll obviously need to keep it around for the time being. One final question - Do I need to do anything more with it than just have it installed on the system?

GS-60 SLIM AND MIGHTY WAR MACHINE

The reason GS-60 been classified as "SLIM AND MIGHTY WAR MACHINE" is because its has a slim and thin outlook while the inner spec is equip with a mighty war machine which you can use it to hunt down every enemy in your way no matter how strong or how big they are. Although the outlook is slim and thin but the inner is equip with a high graphic card which is GTX 860M 2 GB DDR 5 and a 16 GB ram which makes it much more stronger when you use it for gaming or even when you use it for graphic design. This war machine is very suitable for lady because it is light and have high spec while other MSI notebook might be too bulky for a lady. The reason we suggest GS-60 instead off GS-70 is because off the screen size, some lady feel that 17 inch is too big for them but GS-60 is much more suitable for them. This is a feed back we get from most of our female customer that GS-60 is a mighty war machine which they are looking for. From most off the MSI laptop that we set up most off it is GS-60,so we were recommending this MSI laptop.
A simple packaging with MSI name on it, but the beast hiding behind the box is a monster which everyone is looking for no matter the user is guy or female.
An inner protection to protect the beast from injury before it starts its war with u.
A simple and fancy look box been use with a phrase "TOP PLAYER TOP CHOICE". This box is like a cave where a dragon stay.
In addition a better looking back pack comes together with this dragon which will makes u feel proud when u bring it out no matter for what the usage is. This bag only comes with GS series for all MSI laptop. It is a MSI priceless bag pack.
This dragon is been demo at our outlet and most off the feed back we receive from our customer which have try it at our outlet. Most off the feed back we get from our customer is, GS-60 is a laptop which have a sexy and hot body with inner beauty which will makes every one impress with it, no matter a guy or a lady is using it.
Our customer likes the new design for the MSI logo. Our customer feel that the logo makes it looks more high class because this logo looks a bit like Lambogini logo.
MSI laptop comes with steelseries keyboard which means steelseries has certified MSI as a professional gaming laptop brand which makes them cooperate with them.
In addition this laptop is equip with steelseries engine which we didn't get to download from steelseries official website. This program helps most off the player to solve their problem which is miss the key for a skill combo. For example, Street Fighter game most off the people miss their key for a special skill, sometimes because you miss the special skill you didn't get to win that match.
The new sound system is equip with this laptop, Dynaudio sound system mostly been use in Bugatti car and also Volkswagen car. This means that MSI laptop have been certified by Dynaudio sound system also which you can check it out at Dynaudio official website.
In conclusion, GS-60 is a dragon which is SLIM BUT HAVE MIGHTY POWER WHICH WILL HELP YOU TO HUNT DOWN YOUR ENEMY. The only phrase that can be use to express this laptop is "A HOT AND SEXY LADY WITH INNER BEAUTY".

Make sure you run the speedtest of the Killer network manager.
If so, try to install the driver only version of the LAN driver and see if the situation gets improved.
http://dragonarmy.msi.com/forum/showthread.php?t=64228#.VFx2H_mUePs

[Solved] $LANG and zsh prompt color problems

Hi,
I recently discovered, trying to use Newsbeuter, that, in X, certain parts of my profile aren't set. Until now it only seemed to be $LANG, which is empty if I echo it from urxvt in XMonad, but yields the correct setting if I do the same in a tty.
To make things worse now, my zsh seems to be acting up. I have differently colored prompts for my normal user and root. But since a few days ago, the root colors aren't applied unless I source .zshrc again after sudo-ing.
I updated a lot recently and it's gotten hard to track these issues, especially the $LANG one, to a specific update. The only thing I know is that my desktop, running Kdemod, doesn't have these problems.
I'm using Slim and XMonad. Neither issue is limited to a certain terminal.
Most of my configs can be found in my GitHub dotfiles repository. If anything's missing to get a clear picture, ask for it.
My rc.conf can be found here [Gist].
Last edited by count-corrupt (2010-08-22 13:33:06)

jac wrote:
I finally went through the new sudoers file and got mine to work, see this thread for details. Using that, and using a workaround for libetc, your prompt works for me.
You appear not to use libetc, but if you do and don't also have root set up to use libetc, you will need to create a link to/from ~/.zshrc from/to ~/.config/zshrc
I actually just solved it in another way. Your original point, that sudo changed it's default behavior was the key. In the official zsh documentation somewhere it says that all settings that are wanted for root should be put into /root/.zshrc. I just did that and it works.
Your solution works too by the way. Just enabling
Defaults env_keep += "HOME"
does the trick and also (logically) re-enables other things that I hadn't even realized were gone yet like syntax highlighting in vim. I guess I should read into the nature of said privilige escalation problems. Maybe there's a way to selectively keep parts of HOME.
So thank you very much for the help.

[SOLVED] slim does not set a default session

Hi everybody
I think slim does not set the default session (first entry in sessions in /etc/slim.conf):
My /etc/slim.conf:
login_cmd exec /bin/bash -login ~/.xinitrc %session
sessions openbox
So the default session (and %session) should be openbox.
My ~/.xinitrc:
DEFAULT_SESSION=openbox
# urxvt -e screen &
(sleep 1;
eval `cat ~/.fehbg`;
conky &
xbindkeys &
volwheel &
pidgin &
case $1 in
awesome|fluxbox|icewm|i3|dwm|wmii|fvwm|twm|wmfs)
exec ck-launch-session $1
openbox)
/usr/bin/tint2 &
exec ck-launch-session openbox-session
exec ck-launch-session $DEFAULT_SESSION
esac
So. When my sessions option is only "openbox" and .xinitrc is started with $1 = "openbox", it should execute tint2. But it doesn't.
Workaround 1:
When I set openbox directly in login_cmd, it works and tint2 is executed.
login_cmd exec /bin/bash -login ~/.xinitrc openbox
Workaround 2:
In slim, when I hit F1 to change the session and the words "openbox" appears at the screen, it does also work fine.
That means, that slim does not set the default session correctly. Or am I wrong?
I think this is since the last update.
Thanks for your feedback.
mindfuckup
Last edited by mindfuckup (2013-02-12 19:24:39)

Slim never set the default session, but there always was a comment in the default config suggesting that it would. This was well known and everybody simply set their own default (I'll get back to this in a second). Instead of simply modifying this comment, Arch included a patch to change Slim's behavior, but this led to new unexpected behavior so it was removed (recently).
You could also have found this in the wiki, which also provides a solution. Another way to fix your .xinitrc is to replace $1 in the case statement by ${1:-openbox}.
Edit: I just noticed you actually had the DEFAULT_SESSION as used in the wiki example. I think the solution in the wiki is a bit strange, and your .xinitrc (where tint2 should only be started for openbox) is an example where the alternative I suggested is simpler. Yet another way is to use the *) case for the default session (so you would not include openbox as a separate case and just start tint2 and openbox unless the $1 is set to awesome).
Last edited by Raynman (2013-02-12 17:52:33)

[Solved] slim not working after installing nvidia 331.20

Hello Arch Community!
I recently joined your ranks and already have some problems with the graphics driver from Nvidia.
my system has been running perfectly for a week now and until today i used the nouveau drivers, but im not very happy with the performance, so i deinstalled them and installed nvidia + nvidia-utils.
no problems so far, in configured everything to my liking with nvidia-settings.
problem: after reboot slim does not start anymore, i just get to tty1. funny thing is i can either use startx and my cinnamon will fire up or i can just use "sudo slim" and slim will start normally.
i already tried
sudo systemctl disable slim
and
sudo systemctl enable slim
to see if its still starting at boot and it does, so im quite confused here.
Last edited by Oedner (2013-11-25 17:55:42)

Scimmia wrote:Probably related to https://bbs.archlinux.org/viewtopic.php?id=173153
thank you very much, i didnt know i can add modules=nvidia in mkinitcpio.conf too. i always thought this was for opensource drivers only
anyway that fixed my problem. in a way. can i instruct slim to show the login prompt on only one monitor? because now the login field is "between" the two monitors. in other words slim uses both monitors like they are one big screen.
it looks like this now: http://abload.de/img/img_20131125_1801054ii4l.jpg
solved it by editing /usr/share/slim/themes/mytheme/slim.theme the line:
input_panel_x 50%
to
input_panel_x 25%
Last edited by Oedner (2013-11-25 17:55:25)

I want to install Photoshop but everytime I get an ERROR CODE: A12E1.How do I solve that and what is it?

Hello,
I want to install Photoshop but everytime I get an ERROR CODE: A12E1.How do I solve that and what is it?

A12E1 error installing Creative Cloud products | CC
Mylenium

[SOLVED]SliM and .xinitrc

Similar Messages

Maybe you are looking for