Slim not working

Hi. I've installed xfce4 and slim. I followed the wiki pages on how to set it up, and I tried about a dozen other suggestions made on other forums. Nothing is working.
I get the slim login screen, but when I try to login, it says "Failed to execute login command". I'd really appreciate it if someone could help me get this working.

Sure. Thanks for your help. It's tough to post files because I can't even log in and cut/paste etc. I'm posting here from a different computer. But I'll try my best.
My ~/.xinitrc looks like this
#!/bin/sh
exec startxfce4
I copied this file to /root/ and to /home/paco/ where paco is my username. There was an if-statement preceeding the exec command (i.e. as in /etc/skel/.xinitrc)
I deleted the slim.lock file (someone on a forum suggested this), and I also commented out the line
lockfile /var/lock/slim.lock
from the file /etc/slim.conf
I also had a look in /var/log/slim.log. It's too long to type out, but the key line seems to be
/usr/bin/xauth: file /var/run/slim.auth does not exist (but it does indeed exist).
Last edited by Pacopag (2011-06-06 16:01:24)

Similar Messages

PC-Cam 920 Slim not working as per what Creative Claim

I had bought a PC-Cam 920 slim. Well yahoo messenger can't detect it and it not working fine with msn messenger. Anyone have PC-Cam 920 slim and it working fine on the messenger as a webcam? Creative claim it working well with it and the technical support personnel refuse to support me.

Anmario,
Check this article out. Look under MSN section and see if it helps.
http://us.creative.com/support/kb/ar...p?l=2&sid=2544
Jason

Slim not working with LXDE after 2.6.38 upgrade

After running -Syu and getting the new kernel slim will no longer login to lxde. awesome works fine. When I tried to start lxde manually with /usr/bin/startlxde it gave the following error:
cp: cannot stat '/usr/share/lxde/pcmanfm/pcmanfm.conf': No such file or directory
creating an empty file there allowed me to run lxde manually but it still won't work with slim. Any ideas? What other info would be useful to you?
I'm running nvidia 270 drivers.

I was getting this error:
cp: cannot stat '/usr/share/lxde/pcmanfm/pcmanfm.conf': No such file or directory
since day one I installed LXDE and I don't think it is related to the issues we are having.
I have 3 almost identical arch boxes (same dd-ed install, identical packages - besides gfx card drivers) with slim, LXDE and NFS mounted homes, and everything was working fine till last update. Only unhelpful segfault output is logged in X's and slim's log. If anybody is interested, I can post ouputs here.
After this update, X segfaults everytime when lxsession is ran. First I thought this is hardware related, but situation is same on all three boxes (2 x radeon, 1x nouveau). I can login sucesfully if I replace lxsession with WM + xterm/terminator combo (also things like Firefox run then) so the error is caused clearly by lxsession. Then I thought it might be NFS related, but there are no NFS errors in either clients or server logs, more over I see that others are also having problems running LXDE.
Funny thing is, I have another notebook with slim+LXDE and I am experiencing no problems whatsoever.
Any idea how to approach this and at least pinpoint the error further (where within lxsession it occurs) ?
EDIT:
After some toying with LXDE componnents and launching them manually, I found the culprit. In my case it is pcmanfm in desktop manager mode.
Launching "pcmanfm --desktop" causes X to die. Once I renamed /usr/bin/pcmanfm to pcmanfm.borked, I can run lxsession without a glitch. Can anybody confirm this?
Last edited by eto (2011-04-13 10:42:57)

[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)

Autologin not working anymore with systemd, xfce, slim

Hi,
I recently upgraded my system to a full systemd setup and since then autologin to xfce with slim does not work anymore.
I was previously running a systemd/initscripts system (updated to 31/07/2012) and things were working fine. Upon updating to current, autologin stopped working. Instead I am presented with the slim login screen. Once I put my username and password in xfce starts as normal.
I searched these forums and others to find a solution but have not been successful so far.
My .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 gnome-session
# exec startkde
exec startxfce4
# ...or the Window Manager of your choice
and my /etc/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-session,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 laffi
# 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 yes
# 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
Any help will be much appreciated

Hi,
I recently upgraded my system to a full systemd setup and since then autologin to xfce with slim does not work anymore.
I was previously running a systemd/initscripts system (updated to 31/07/2012) and things were working fine. Upon updating to current, autologin stopped working. Instead I am presented with the slim login screen. Once I put my username and password in xfce starts as normal.
I searched these forums and others to find a solution but have not been successful so far.
My .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 gnome-session
# exec startkde
exec startxfce4
# ...or the Window Manager of your choice
and my /etc/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-session,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 laffi
# 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 yes
# 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
Any help will be much appreciated

Wall Charger of new iPad is not working

I just got a new Ipad 64GB and I observed that the wall charger adapter is not working.
I checked the cable and it is fine as it charges the iPad when connected to the computer USB and it syncs.
I also tried the wall power adapter of my iPhone and it works perfectly fine. It charges the iPad as expected.
Thus it is the iPad power adapter.
Anyone with this issue?

I have the same problem and found a solution. I have two 16 GB ipads and several ipods around so was able to isolate that when using the sync cable provided with the ipad (the slim ones) the ipad and ipods did not charge correctly (very slowly if not at all). When using one older sync cable (fat connector) on the wall charger, the problem is gone. Unfortunately, I have juste one of those, but at least I am sure that it will work.
I also encounter sync issue with those small connectors : connections goes on and off without a predicable pattern.
So from my experience: the problem is not related to the ipad, the problem is not with the wall charger and using an older ipod sync connector solve the issue. The issue is with both usb connectors included with the ipads, so getting a new similar one is unlikely to solve the issue.

[solved] keyboard not working correctly on vc/1

the behaviour is quite odd.
when i hit ctrl-alt-f1, and switch to the first virtual console, trying to login, or even type doesnt work quite as it should.
example, i try to login: this is what i get:
lappy login: elragn
password:
when the user name should be eldragon, if i type each letter at a time, until i get it to work, i can type correctly, and its not always the same letters that dont work. of course, the password comes in blank, and sometimes, when i get it all right, i can login, and the effect contiues
this is not a hardware issue, other virtual consoles work ok, and the keyboard works fine under Xorg.
so, what could be wrong with this vc? anyone got a clue? ive searched the wiki, bug reports, google, and the forums (not in this order) for an answer but i came up empty.
PD. if im posting in the wrong forum, please move it where it should go
Last edited by eldragon (2009-03-22 18:08:54)

Hi,
Since the problem is in the vc's, and the keymap is loaded "pre Xorg", I'd start by doing some tests there.
I'm still a learner myself, so this might not work, or it might, either way, you've got nothing to loose
First of all check logs for errors, maybe something pops out.
If no errors on logs, than here's what I would do if I were you:
(backup /etc/rc.conf , /etc/inittab , /etc/locale.gen to some directory)
1. Let's start by isolating the problem by not going to gdm->gnome automatically, so you can test vc's themselfs more efficiently and quicker.
take out gdm from the DAEMONS line in /etc/rc.conf (something like this)
DAEMONS=(syslog-ng network netfs crond alsa hal fam)
2. let your /etc/inittab be like you have in this section (id:3)
## Only one of the following two lines can be uncommented!
# Boot to console
id:3:initdefault:
# Boot to X11
#id:5:initdefault:
and comment everything here:
# Example lines for starting a login manager
#x:5:respawn:/usr/bin/xdm -nodaemon
#x:5:respawn:/usr/sbin/gdm -nodaemon
#x:5:respawn:/usr/bin/kdm -nodaemon
#x:5:respawn:/usr/bin/slim >& /dev/null
3. do you use a non-us keyboard?
check your rc.conf for the 1st lines, mainly your KEYMAP
LOCALE="en_US.utf8"
HARDWARECLOCK="UTC"
USEDIRECTISA="no"
TIMEZONE="your.timezone.here"
KEYMAP="your.keymap.here"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
confirm that your keymap exists in /usr/share/kbd/keymaps and double confirm the name is right, example:
for US keyboard the file is 'us.map.gz' so KEYMAP="us" (take out .map.gz); in case your keyboard is not US, check the name, as some have more letters than others
(usually /usr/share/kbd/keymaps/i386/qwerty unless your pc is not i386 or qwerty ofc )
4. reboot pc.
You'll be in vc/1.
Now, instead of jumping in consoles with ctr-alt-Fx, try jumping just with Alt+Fx. (if it doesn't work, go ctrl+alt+fx ofc)
Do Alt+F2 and start typing as normal, anything and manything at any speed and confirm is good. Don't press enter. Just testing keystrokes.
Do Alt+F3, Alt+F4, Alt+F5 and test the same for each vc.
Now for the final and problematic one, go Alt+F1 and test.
If it's good, then probably your problem is on X/gdm/gnome or anything that is loading after vc, or if you changed your keymap, then that was the faulty thing.
If it's not good, keep on reading
5. don't enter in vc/1, rather jump to vc/2 or 3 or something and enter as root, let's edit your /etc/rc.conf again.
copy to a piece of paper your 1st options in case they are different from below:
LOCALE="en_US.utf8"
HARDWARECLOCK="UTC"
USEDIRECTISA="no"
TIMEZONE="your.timezone.here"
KEYMAP="us"
CONSOLEFONT=
CONSOLEMAP=
USECOLOR="yes"
basicly is trying to put it to a default state. Put your options just like they are above, except TIMEZONE, you can put yours, I don't remember default one.
Reboot and test again just like in step 4.
If it doesn't work, you might give a look at /etc/locale.gen and just uncomment these 2 lines:
#en_SG.UTF-8 UTF-8
#en_SG ISO-8859-1
en_US.UTF-8 UTF-8
en_US ISO-8859-1
#en_ZA.UTF-8 UTF-8
#en_ZA ISO-8859-1
leave every other line commented. in case you had some of your own uncommented, copy to a paper wich ones were, and comment them.
write in console
locale-gen
let it end generating the locales, reboot, and step 4 again.
6. Still not working, let's try to put things bad proposedly! Change your KEYMAP to another one, if qwerty, just choose another qwerty language, all letters should be on same place, except for punctuation ofc.
Reboot and try again as step 4.
Still not working? Change the LOCALE and keep your wrong qwerty keyboard. (LOCALE will probably change some words, like password to it's LOCALE language, etc).
Reboot and try again as step 4.
Still not working? ok, final attempt, change back your LOCALE and your KEYMAP to the values you had before, the correct ones.
Reboot and try again as step 4.
7. If still not working, well, for now I don't know much more. Take in consideration that the boot process goes through several steps, the error might be in one of those steps. One last thing you can try, altho I think it works just in DE/WM modes, I've read in some posts (here or not, can't remember) that by pressing Ctrl-Alt-K you can change your keyboard layout, assuming you have a second one, and use them for different things, I think the example I read on the post was something like, you wanna code in english but talk in irc in russian for example.
I kinda doubt it works, but if it also activates in vc's mode, then you could have pressed it accidently (like when doing ctrl-alt-fx, your finger slipped ).
press ctrl-alt-k, type a few letters, press ctrl-alt-k again, type more letters, and you'll see if it does something or not.
Again, just try, you got nothing to loose
One thing I noticed, is that when trying to put some characters on vc as username, it acts as delete, some even erase the all line in one go and some don't do nothing, some of the characters were # @ £ §.
8. Since it didn't work, let's put everything as it was.
8.1. go to /etc/inittab and put like this:
(comment id:3, uncomment id:5 // uncomment x:5:...gdm...)
## Only one of the following two lines can be uncommented!
# Boot to console
#id:3:initdefault:
# Boot to X11
id:5:initdefault:
# Example lines for starting a login manager
#x:5:respawn:/usr/bin/xdm -nodaemon
x:5:respawn:/usr/sbin/gdm -nodaemon
#x:5:respawn:/usr/bin/kdm -nodaemon
#x:5:respawn:/usr/bin/slim >& /dev/null
8.2. edit /etc/rc.conf and DON'T put back the gdm on daemons line.
Alter the 1st lines ranging from LOCALE to USECOLOR to the ones you copied to a paper.
8.3. comment/uncomment the locales on /etc/locale.gen as you have on paper and run in console
locale-gen
8.4. you're set, reboot and you're on gdm->gnome again. (still no vc/1 working tho )
note: in your initial /etc/iniitab you had id:3 uncommented and gdm on daemons, so you would go automatically to gdm as you started your pc, but, what if something happens and you need to go to another mode before gdm runs? you couldn't do it easily with gdm on daemons.
If you put it like I wrote above, when you turn on the pc, it's the same, you go automatically to the gdm, but, in case something happens, you can always go to another mode before gdm runs, by doing the following (read here on wiki or foruns, will put link when I find it)
Pc reboots and you're on GRUB, press 'e', choose the kernel and press 'e' again, go to the end of the line where it says 'ro', and add a 3 to the end, to look like this 'ro 3', press 'b' (boot) and you're on mode 3 without going to gdm
But ofc, this is just a choice, if you prefer to have as you had it, by all means, just put gdm on daemons line, and your /etc/inittab as initially, that's the beauty of Linux, it's to your fit
Good Luck!

CTI - SAP CRM & SAP BCM: ANI does not work in SAP standard

Hello Experts,
our customer wants to work with a CTI in SAP CRM WebUI Role (Non IC; CEBP).
For the CTI the SAP CRM 7.0 (on HANA) and SAP BCM where itegrated.
We are using the Slim Communication Toolbar as recommended by SAP.
The Problem ist that the ANI (Automatic Number Identification) does not work.
The Callers Number is not identified. Function Module BUPA_SEARCH2 is not called.
No Changes were made in this area. We are completely using the SAP standard.
Has anybody experienced issues related to this one?
It would be great if somebody could give me some help and/or information!
Thank you!
Kind Regards
Martin Gaschk

Hello Andrei,
the issue was solved by SAP.
The relevant startup component for ANI in the CMS integration profile (Tx CRM_IC_FW_PROF) was inactive:
Component:
BUSINESS PARTNER IDENTIFICATION
Class:
CL_CRM_IC_FW_BP_SEARCH_SRV
Thanks for your support!
Kind regards
Martin

Repousse not working

Repousse is not working correctly in Photoshop CS5 64-bit
here are my specs:
Open Gl drawling is enabled
when I try to use Repousse I first get this error message:
Then I get this error
Any ideas? I thought my computer was leet :|

Hello,
As already said, your graphical hardware isn't enough to use this kind of features.
There are 2 flavours of the Inspiron 560 : desktop form factor, and a slim one
In the case : you are using slim version you should read the Inspiron 560 slim documentation and see if your computer supports Low-profile PCI adapters and that you have one PCI slot available.
In the case : you are using normal version you should read the Inspiron 560 documentation and see if your computer has a PCI-express extension port available.
In all cases, you will need to use/buy a graphic adapter. If your hardware doesnt allow you to add it, there is no solution except changing the whole computer.
Kind regards,
Arnaud.

Running syndaemon at startup in .xinitrc not working

I'm trying to run syndaemon so I can set my touchpad to turn off when typing. I'm using the command:
syndaemon -i 1 -d
If I issue this after logging into Gnome in a terminal, it works fine and I can see the syndaemon process running in System Monitor.
But if I add the command to my .xinitrc it doesn't work. I followed the instructions in the wiki, to no avail. I also found that another command I wanted to issue in .xinitrc ("xset -dpms") to solve a different problem with gnome-power-manager wasn't working either. I got that to work by issuing the command as a startup program in Gnome's Starup Applications gui.
Anyway, I guess I could do the same thing with syndaemon, but I'm wondering why it's not working in .xinitrc, as it's supposed to. Thanks for any help.

Okay, I tried slim and it did execute the xset and syndaemon commands from .xinitrc.
Then in a Google search this old post from the Arch forums turned up, from way back in 2003: http://bbs.archlinux.org/viewtopic.php?id=726. At the end Xentac explains that GDM does in fact only look to .xinitrc for what window manger to start and ignores everything else (which of course is also what Wilco says above).
Xentac wrote:
If you choose the option to load fluxbox, that's all it will do. It won't load anything in .xinitrc or .xsession.
There should be a Session option in gdm. Add fluxbox to the end of your .xsession (so it should now look exactly like your .xinitrc) and choose the Session option in gdm.
Gdm assumes that your window manager will do all the auto-loading stuff (like gnome and kde do) so if it doesn't there isn't an easy way to add it, apart from hacking up the gdm menu item scripts (if you wanted to they're in like /etc/gdm/Session.d or something).
So I guess using the startup applications gui in Gnome is the right way to do it. Unless anyone objects, I'm going to add a note to the wiki. Reading around, it seems like it might be possible to somehow execute startup processes with GDM reading a .xession file, but I didn't really get it.
Curiously, when I was using Slim it solved a different bug I was having, with my brightness getting dimmed after every shutdown. So at least now I know it's gdm that's doing that. And once again I've learned that I'm more likely to turn up relevant Arch forum posts with google searches than with the Arch forum search function.
And thanks again to everyone for their suggestions and ideas about how to address this issue.

LENOVO Y3000 4CQ Celeron's MAT**bleep**A CD-RW-CW-8124 (SM) not working, Unbale to boot the notebook

Hi,
As per the subject line my laptops CD drive is not working and my system's operating system has just crashed. I had 1 year CCI warranty but it is over. Can anyone tell me the price in Indian or US curency for the new CD RW of the same specification
24x Mat**bleep**a DVD CD RW CW 8124 (SM)
Vivek

the drive shouldn't be expensive, but is difficult to source aftermarket, if you go to the depot they will charge a quotation and labour fee, which is expensive.
So my advice to you is just to get an external dvd burner, if you need to a portable unit get the usb powered slim version, should be pretty cheap.

SLiM not auto loggin in user

I installed SLiM so that I could auto login my user and have used it before but for some reason on this machine it won't auto login my user.
I have made the adjustments to the /etc/slim.conf for the default_user and change the auto_login to yes.
I've been unable to find a reason why it won't login so am hoping someone might be able to assist me to sort this out.

here is the file:
# 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 media
# 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 yes
# 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

Getting SLiM to work... [SOLVED!]

I recently installed Xfce and SLiM, but SLiM refuses to login. When I type in my username and password, it just comes back to the login screen again. Are there some configuration files I need to edit?
Last edited by miggols99 (2007-07-29 12:49:36)

I only have Xfce and don't plan on adding anything else. Will my /etc/slim.conf help? I think I might have done something to it.
# 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 %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 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
# 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 simone
# 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
Last edited by miggols99 (2007-07-28 20:41:14)

Flash CS5 code hinting not working?

Just installed the new Flash CS5 trial and code hinting doesn't appear to be working! I have added all my custom class paths in to the AS3 source paths, but I don't get any code hinting for any of these just the same old code hinting you get in CS4. Am I doing something wrong or does it just not work?
UPDATE: If it helps, in the code editor i get a small yellow triangle with an exclamation mark in, in the bottom right hand corner. When I have over this it advises me:
" *** Unable to build code hint cache. Please save the associated FLA into a different folder. There are too many files on the classpath. *** "
This error message appears no matter what FLA/Class i open, and moving it makes no difference.
UPDATE: Problem solved, the "There are too many files on the classpath" was the clue! Slimmed down my library and all seems to work now.
However, this does bring me on to another question.. does anyone know how many class files flash can comfortably cache? I use some fairly chunky libraries in my work and am wondering if i'm going to find myself constantly slimming them down after a while?

The reason everyone gives for AS3 is that AS2 was buggy.
I don't think so. AS3 is a better language, better designed, more consistent, more powerful. I would switch to AS3 for that, not because of bugs - but I don't know what's the reason behind everyone's choice.
AS2 was not buggy, people were writing buggy scripts
AS2 was buggy. Maybe people were writing buggy scripts too, but believe me it was buggy. However AS3 is at the very least equally buggy. It is better designed, more consistent, but equally buggy in its implementation.
All software have bugs, but programming languages usually undergo a stricter and more thorough revision than other kinds of sofware because the consequences of bugs in a programming language are more disastrous.
But that's not the case of ActionScript. Maybe because of its history and its legacy, or maybe because Adobe was always dedicated to completely different kinds of software, like PhotoShop, Premiere and the like, and suddenly dove into the business of developing a programming language without having the know-how.
The level of bugginess of ActionScript is amazing. I work with actionscript daily and there's no day that I don't run 4 ot 5 times into some problem due to some bug. Not that I discover new bugs every day, just run into them - sometimes they are already reported, other times they are not.
Why should something that took one line of code (clicking on a movieClip
to move to a frame) now take 5 or more lines of code (creating a
listener object, assigning a listener object, writing a function).
It often happens that a language that is in the overall more elegant, consistent and compact, turns out to need a bit more of code for doing the simplest things. Maybe what could be done with 1 line of code now takes 5, but things that took 1000 lines of cumbersome awkward tricky and hacky code can now be done with just 100 of readable and simple-to-understand code.
When I first learned Java I was surprised at the quantity of code I had to write just to make a program that would print "hello world", while in most dialects of Basic it was just:
10 PRINT "Hello world"
Would you say Basic is superior to Java in any sense?
I teach Flash at a university, both beginner and advanced users. [...]
I'll stick to AS2 in my classes.
You should think about the damage you may be doing to your students. If they are going to use ActionScript professionally, they'll have to learn AS3, rather sooner than later. So why not save them the pain to do the effort twice? If instead you are teaching them AS just for didactic purposes (i.e. for learning programming in general) and don't care about practical applications and you don't like the way AS has evolved (i.e. AS3), then consider teaching them another language, instead of an obsolete version of a current one.
AS3 is not more complicated, or difficult to learn, or less designer-friendly or non-programmer-friendly than AS2. Not at all; rather the opposite. It is more complicated and difficult to learn when you already know AS2, because you feel like everything you knew is useless - but the same can be said about learning AS2 when you already know AS3. Starting from scratch, AS3 is indeed simpler.
But this have drifted OT, sorry. Back to the topic:
It's not an app killer, just a minor inconvenience
It's a major inconvenience if writing the same amount of code takes you three times the time it should take. That in 2010 you have to spell every single property/method/class name entirely from the first to the last letter, when most of the time it should be just a matter of typing a couple of characters and hit tab, is simply ridiculous. You may as well write your code with NotePad. Flash is (among other things) an IDE - something Adobe seemed to neglect up to recently; and when they finally decided to take a step into making it work like any other decent IDE, it does not work!!
There are bigger things to complain about.
On this you are definitely right.
Using their pretty remarkable products (where would we be without PS or
DW?) is not a right, it's a (sometimes frustrating) privilege.
It's a privilege you pay for. That's when it becomes a right.
So Adobe mods, we're frustrated but only because we're all loyal users who depend on your products
(emphasis is mine)
Exactly. That's the point.
Note there's been no helpful answer from them yet: that's how much they care about loyal users who depend on their products.

Apple keyboard not working w Iogear KVMP 1644 switch

I have a new Apple keyboard that I am attempting to integrate it into my music setup. It's an Iogear GSC1644 4-Port Dual View Dual Link DVI KVMP Switch with Audio. I have a newer (2012) Apple keyboard that I plugged into my setup and it does not work. It is the same model A1243 as my 2008 Apple keyboard which still works except for 2 keys, the 'Z' and the 'option' keys. I plug it in and nothing - it's like it is not seen. HOWEVER >>>> when I plug it indirectly to the computer - no problem. These Apple keyboards look identical, they are the same model. I have changed USB cables at every connection - I cannot get it to work. I powered down the Iogear GCS1644 per directions from their support desk: this included disconnecting every device and unplugging the power supply and leaving it unplugged for at least 10 minutes. I left it unplugged for over an hour. Then plugged the 4 computers back in, powered on the unit, and only powered on one computer - it still did not work. The older Apple keyboard works perfectly - nothing changed. I am at a loss.
What can this be? Is there a major difference between the two Apple Keyboards even though they carry the same model number? And - barring a quick and simple fix - are there any other older Apple Keyboards out there? If not Apple, are there any other keyboards with a similar small footprint like the Apple that might work? Any help would be greatly appreciated. Thanks!

Are you connecting the keyboard to the keyboard-specific USB port on the back of the unit, as opposed to the front port or the hub on the back?
I have a 4-port DVI IOgear KVM. I have never had a problem with the keyboard not being recognized, although booting through the KVM doesn't allow use of the various "boot" keys (option, S, T, etc.). I have to plug a keyboard directly into the computer for that. The other issue I have had is that the front USB port was always somewhat unreliable, and after a year or two just seemed to conk out.
I am using an older Kensington Slim type keyboard that was discontinued several years ago. I haven't tried the Apple keyboard that came with my 2010 Mac Pro, but will try to do so, just to see if there is an issue.
There may very well be some slight difference between the 2008 and the newer keyboards. With luck, someone here will know.
Is your Mac Pro a 2013 model?

Slim not working

Similar Messages

Maybe you are looking for