Slim to XDM

Hi,
I've tried this using slim from extra, slim-plus and slim-cursor from AUR, but these features have never worked for me. So I'm guessing I'm doing something wrong?
1. Welcome message doesn't appear. It just says "Login" and a text field for entering username and password. I have this in slim.conf:
welcome_msg Welcome to %host
2. Halt, reboot doesn't work from slim.
halt_cmd /sbin/shutdown -h now
reboot_cmd /sbin/shutdown -r now
How do I do these?
Regards
Last edited by sHyLoCk (2010-01-07 12:46:15)

I'm not sure about the welcome message,  but for for the others are you entering 'halt' or 'reboot' in the username and then entering you root password?
I could never get the 'console' command working with slim, but switching to another tty was easier and possibly more useful.
Because I was having a few probs and after seeing this thread http://bbs.archlinux.org/viewtopic.php?id=69299 I switched to xdm

Similar Messages

  • XDM has problems with consolekit

    I recently switched from SLIM to XDM, and now when I shutdown the computer in gnome (launched using ck-launch-session), the computer sometimes restarts instead, even though I pressed 'shutdown'.
    This didn't occur with GDM or SLIM.
    /etc/inittab line
    x:5:respawn:/usr/bin/xdm -nodaemon -config /etc/X11/xdm/arch-xdm/xdm-config
    I use http://aur.archlinux.org/packages.php?ID=27463 for the config

    my .xsession is :
    exec ck-launch-session startlxde
    and everything works as it should how does your .xsession look ?
    Last edited by parintachin (2010-02-06 17:09:43)

  • Gnome blocks keyboard

    Hi
    I have a HUGE problem: Gnome  blocks my keyboard. I can login with GDM (keyboard works) but as soon as gnome starts up the keyboard doesn't work anymore. I can't even change to another tty with CTRL+ALT+F1 F2 or any other tty. I managed to start a minimal xserver with openbox using a tty before i log in with gnome and everything works perfectly there, so it's definetively a gnome problem and probably not HAL related.
    PLEASE help me to solve this problem as soon as possible because I'm kind of overstrained with that. Tell me what you need to know about my setup or log files and I'll provide them to you.
    I didn't change any configurations in the last few days and the problem started after using GIMP, Firefox and Geany. After changing from one TTY to another one I was only able to move the mouse but couldn't even click anywhere on the desktop. The keyboard didn't work either. I did a hard reboot and everything seemed to work again except the keyboard. I tried it a few times but that didn't help. My system is up-to-date.
    Thank you very much in advance.
    schneida

    Ok, this problem is really weird. Openbox is working fine when I start it on a tty with
    xinit /usr/bin/xterm -- :1
    and then openbox &. Still when I start it with GDM (in the dropdown select openbox) it has the same issue that gnome-session has. So I tried slim and xdm and they don't work either. The keyboard works to login but as soon as the load either openbox or gnome-session the keyboard doesn't work anymore. Therefor I tried to load gnome-session directly from the xterm I started but then the keyboard in gnome doesn't work either again.
    After a reboot a get a error message from firefox. Sorry that it's mostly german:
    "Der Konfigurationsserver konnte nicht kontaktiert werden; mögliche Fehlerquellen sind, dass TCP/IP für ORBit nicht aktiviert ist oder auf Grund eines Systemabsturzes alte NFS-Sperren gesetzt sind. Unter http://projects.gnome.org/gconf/ erhalten Sie weitere Informationen (Details –  1: Verbindung zur Sitzung konnte nicht abgerufen werden: Failed to connect to socket /tmp/dbus-2WWHpd9zZO: Verbindungsaufbau abgelehnt)"
    Translation:
    "The configuration server could not be contacted; possible error sources is that the TCP/IP for ORBit is not activated or is locked because of a crash on an old NFS-lock. Find more information under http://projects.gnome.org/gconf/. (Details - 1: Connection to the session could not be loaded: Failed to connect to socket /tmp/dbus-2WWHpd9zZO: Connection rejected)"
    EDIT: Ok, that new error also shows up when I try to start nautilus in my openbox session and nautilus doesn't start anymore. I guess my system is screwd... ARGH!!
    EDIT 2: Ok I created a new user and now it works. Seems that some configuration is broken for my original user. Would be very interesting whats actually not working. I copied most of the configuration folders (like .local .gnome2 .config) into my new account but after I copied .gconfd and .gconf the keyboard stopped working again. Resetting those to folder made everything work again. The problem is somehow solved for me, still I would be very interested what caused the problem and how to avoid that. I installed exactly the same setup on a friends machine and I would like to save him from such a day. Should I open a bug for the problem and providing those two folders?
    Last edited by schneida (2010-05-18 19:00:03)

  • Audio in Youtube

    When playing youtube videos, the sound will cut out as if it needs to be buffered. but if I instantly pause and unpause the video it will play the sound again. To get a feel for my problem, watch a video and cover your ears for random amounts of time at random intervals. The vast majority of the video's sound gets lost.
    I use:
    DWM, with slim
    external speakers, wired to an audio jack
    latest flash (10.0.34?, have tried AUR prerelease)
    Google Chrome Beta, AUR (same on firefox)
    Sound works perfectly outside of Youtube, and only fails on Youtube videos
    I don't know what caused it as it has been happening for since the beginning of my arch linux.
    side question, if you have used slim and xdm, which was faster and less memory offensive. But above it more important

    Mr.Macdonald wrote:Only on youtube, but if it doesn't happen with others then there would be a problem with my computer
    Sorry, I don't understand your comment. Do you mean that it doesn't happen with other websites/flash videos, or that it doesn't happen with other operating systems? Or maybe you mean that it doesn't happen with other people?
    If you mean the first, that it doesn't happen with other websites/flash videos, then I repeat my first comment: if this is ONLY occuring with the videos on youtube, and you have tested with flash videos from other websites, then there is nothing wrong with your computer/your operating system, that is a problem with youtube. As a test, does the problem occur when watching this video: http://www.graspr.com/videos/Creating-a … ash-Part-2
    If you mean that it doesn't happen with other operating systems (Windows, Ubuntu, or something else), then it is a problem with the setup of your current operating system. Please be as specific as possible when describing what does/does not work if this is your problem.
    If you mean that it doesn't happen with other people, then please answer the following questions:
    1. Can you view flash videos from other websites without problems?
    2. If you have other computers in the house, or if you have used other computers in the house, do you have the same problem with those computers?
    3. If you have used used another operating system with this computer (Windows, Ubuntu, or something else) did you have the same problem?
    I understand English is not you primary language, but please try to be as specific as possible in describing your problem. Say more if you are unsure if you are specific enough. I speak bad Chinese and bad Spanish, believe me I understand.
    Last edited by alex_dc (2010-01-20 01:14:22)

  • [Solved] Unable to log in (xdm), or access tty's (nVidia bug).

    Ok, this is kind of long winded, but I'm really stuck on this one.
    To start, I use xdm as my display manager, which I modified the appearance of (following this: https://wiki.archlinux.org/index.php/XDM) and then later installed xdm-archlinux.
    I also installed the nvidia drivers (via pacman), which resulted in me not being able to see any of my other tty's, however at the time it didn't really bother me and I presumed it would be fixed one day anyway.
    After updating (5th Feb); when I boot up I reach a black screen (presumably a broken xdm) and no way of getting into the system on an alternative tty.
    I've tried starting in runlevel 3, but nvidia modules presumably are still starting and I still can't see anything.
    Any ideas?
    Last edited by NixonInnes (2012-02-07 20:10:46)

    Thanks very much guys, i solved the problem.
    For reference, here's how:
    booted into a live disk
    modified inittab to not fire up a dm
    blacklisted nvidia and nvidia-utils
    removed nouveau from the blacklist
    rebooted
    removed xdm and all settings
    installed slim
    logged in with eye-candy
    switched nvidia and nouveau back around
    reboot
    job done.

  • Slim "Id "x" respawning too fast: disabled for 5 minutes"

    Hello Everyone,
    Slim "Id "x" respawning too fast: disabled for 5 minutes"
    This error drives my crazy I changed to slim after the recent change of gdm.
    Since I changed, when I boot my PC this error always occurs. Only solution so far is either to wait for 5 minutes  or to change to another TTY#, login and try init 3 and then init 5 (which only works sometimes but most of the time delivers the same error).
    The error doesn't occur when I REboot the PC.
    I start slim via inittab with "x:5:respawn:/usr/bin/slim >& /dev/null"
    I already tried the German Arch-Forum but got no reply.
    There is a topic http://bbs.archlinux.org/viewtopic.php?id=81159 with the "solution" to change inittab
    "x:5:respawn:/usr/bin/slim >& /dev/null"
    to
    "x:5:once:/usr/bin/slim >& /dev/null"
    but this doesn't work for me, slim then refuses completly to start.
    I'd prefer to use the inittab method and not the daemon method...
    Thank you in advance
    cl10k
    PS: Sry for bad English...
    Last edited by cl10k (2009-11-24 21:54:18)

    Hi,
    "generally" X seems to work fine. I use Openbox without any problems. If I try /usr/bin/slim from init 3 it says: "Stale lockfile found, removing it" and then nothing happens - the console just stays on.
    I haven't changed my Xorg for ages, I still use the same X configuration (besides updates) that I had years ago with kdm and then with gdm. Even when I switched from gdm to slim I just follwed to wiki and changed the Inittab line from gdm to slim.
    Heres my Inittab and my Xorg.conf (to be honest I'm not really fit with Xorg configuration...)
    To be sure, I just created a (very basic) new Xorg.conf with nvidia-xconfig.
    # /etc/inittab
    # Runlevels:
    # 0 Halt
    # 1(S) Single-user
    # 2 Not used
    # 3 Multi-user
    # 4 Not used
    # 5 X11
    # 6 Reboot
    ## Only one of the following two lines can be uncommented!
    # Boot to console
    #id:3:initdefault:
    # Boot to X11
    id:5:initdefault:
    rc::sysinit:/etc/rc.sysinit
    rs:S1:wait:/etc/rc.single
    rm:2345:wait:/etc/rc.multi
    rh:06:wait:/etc/rc.shutdown
    su:S:wait:/sbin/sulogin -p
    # -8 options fixes umlauts problem on login
    c1:2345:respawn:/sbin/agetty -8 38400 tty1 linux
    c2:2345:respawn:/sbin/agetty -8 38400 tty2 linux
    c3:2345:respawn:/sbin/agetty -8 38400 tty3 linux
    c4:2345:respawn:/sbin/agetty -8 38400 tty4 linux
    c5:2345:respawn:/sbin/agetty -8 38400 tty5 linux
    c6:2345:respawn:/sbin/agetty -8 38400 tty6 linux
    ca::ctrlaltdel:/sbin/shutdown -t3 -r now
    # 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
    # End of file
    # nvidia-settings: X configuration file generated by nvidia-settings
    # nvidia-settings: version 1.0 (buildmeister@builder63) Tue Oct 20 21:01:12 PDT 2009
    Section "ServerLayout"
    Identifier "Layout0"
    Screen 0 "Screen0" 0 0
    InputDevice "Keyboard0" "CoreKeyboard"
    InputDevice "Mouse0" "CorePointer"
    Option "Xinerama" "0"
    EndSection
    Section "Files"
    EndSection
    Section "InputDevice"
    # generated from default
    Identifier "Mouse0"
    Driver "mouse"
    Option "Protocol" "auto"
    Option "Device" "/dev/psaux"
    Option "Emulate3Buttons" "no"
    Option "ZAxisMapping" "4 5"
    EndSection
    Section "InputDevice"
    # generated from default
    Identifier "Keyboard0"
    Driver "kbd"
    EndSection
    Section "Monitor"
    # HorizSync source: edid, VertRefresh source: edid
    Identifier "Monitor0"
    VendorName "Unknown"
    ModelName "LG F900B"
    HorizSync 30.0 - 98.0
    VertRefresh 50.0 - 160.0
    Option "DPMS"
    EndSection
    Section "Device"
    Identifier "Device0"
    Driver "nvidia"
    VendorName "NVIDIA Corporation"
    BoardName "GeForce 7600 GS"
    EndSection
    Section "Screen"
    Identifier "Screen0"
    Device "Device0"
    Monitor "Monitor0"
    DefaultDepth 24
    Option "TwinView" "1"
    Option "TwinViewXineramaInfoOrder" "CRT-0"
    Option "metamodes" "CRT-0: 1280x1024_85 +1280+0, CRT-1: 1280x1024_85 +0+0"
    SubSection "Display"
    Depth 24
    EndSubSection
    EndSection
    EDIT: It seems to work now! Slim started without any errors. I will test that for some days to see if the problem is really gone now.
    Just out of curiosity:
    A lot seems to have changed in Xorg.conf since my old ~2years old config was made.
    I had to turnoff boot logo manually and set Option "Composite" "Enable" but now everything seems to work by default?
    Do you see any flaws in my xorg.conf? Any ideas for improvements (except metamodes)?
    Last edited by cl10k (2009-11-25 10:47:02)

  • Issue with Slim and OpenBox

    Hi to everyone:
    I've installed Slim + OpenBox in one machine PIII-450 MHz., 256 MB RAM, HD 8.5 GB.
    I've one issue now: when the system is starting, I can see the login prompt at the console, after one black screen by 20 seconds and appears the screen login from Slim.
    Someone else with the same problem ... anyone knows how to fix it?

    pyther wrote:How are you starting slim? What are you expecting it to show while X/Slim is loading?
    This is the /etc/inittab file:
    # /etc/inittab
    # Runlevels:
    # 0 Halt
    # 1(S) Single-user
    # 2 Not used
    # 3 Multi-user
    # 4 Not used
    # 5 X11
    # 6 Reboot
    ## Only one of the following two lines can be uncommented!
    # Boot to console
    #id:3:initdefault:
    # Boot to X11
    id:5:initdefault:
    rc::sysinit:/etc/rc.sysinit
    rs:S1:wait:/etc/rc.single
    rm:2345:wait:/etc/rc.multi
    rh:06:wait:/etc/rc.shutdown
    su:S:wait:/sbin/sulogin -p
    # -8 options fixes umlauts problem on login
    c1:2345:respawn:/sbin/agetty -8 38400 tty1 linux
    c2:2345:respawn:/sbin/agetty -8 38400 tty2 linux
    c3:2345:respawn:/sbin/agetty -8 38400 tty3 linux
    c4:2345:respawn:/sbin/agetty -8 38400 tty4 linux
    c5:2345:respawn:/sbin/agetty -8 38400 tty5 linux
    c6:2345:respawn:/sbin/agetty -8 38400 tty6 linux
    ca::ctrlaltdel:/sbin/shutdown -t3 -r now
    # 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
    # End of file
    This the /home/user/.xinitrc file:
    #!/bin/sh
    # ~/.xinitrc
    # Executed by startx (run your window manager from here)
    exec openbox-session
    # exec gnome-session
    # exec startkde
    # exec startxfce4
    # ...or the Window Manager of your choice
    If I compare KDM + KDE vs Slim + OpenBox, this last mix is slowest.
    Could be fastest or I need another Login Manager for OpenBox?

  • Xdm: sessreg not configured properly?

    Hi All,
    I've been experimenting with xdm recently and I've found that sessreg does not seem to be configured properly.  When I login using xdm, no user sessions are recorded, using "w" or "last" reports that no one is logged in, even though I am logged in!  If I revert to slim, it works fine, logins and logouts are recorded properly.
    I've tried swapping the sessreg commands in /etc/X11/xdm/Xstartup and /etc/X11/xdm/Xreset with those in /etc/slim.conf, but it hasn't helped.
    Does anyone else have this problem?  Or a solution?
    Thanks,
    Rob

    i can assure you that it works in lxdm,
    > cat /etc/pam.d/lxdm
    #%PAM-1.0
    auth requisite pam_nologin.so
    auth required pam_env.so
    auth required pam_unix.so
    account required pam_unix.so
    session required pam_limits.so
    session required pam_unix.so
    password required pam_unix.so
    session optional pam_lastlog.so
    session optional pam_loginuid.so
    -session optional pam_ck_connector.so nox11
    cybertorture@freeman ~
    > who
    cybertorture pts/0 2011-11-29 00:57 (:0.0)
    cybertorture@freeman ~
    > lastlog
    Username Port From Latest
    root tty1 чт ное 24 16:45:11 +0200 2011
    cybertorture tty3 вт ное 29 00:19:41 +0200 2011
    Last edited by cybertorture (2011-11-28 23:21:56)

  • SLiM only starts twice then exits to tty1

    Hi... i've installed arch yesterday following this guide https://wiki.archlinux.org/index.php/Beginners'_Guide i
    After that i started to set up a new desktop using openbox and slim.
    Basically everything works fine... except that after exiting openbox 2 times slim won't start and i end at tty1.
    systemctl status slim... after boot
    slim.service - SLiM Simple Login Manager
    Loaded: loaded (/usr/lib/systemd/system/slim.service; enabled)
    Active: active (running) since Di 2013-03-19 19:05:10 CET; 1min 10s ago
    Main PID: 241 (slim)
    CGroup: name=systemd:/system/slim.service
    └─264 /usr/bin/X -nolisten tcp vt07 -auth /var/run/slim.auth
    ‣ 241 /usr/bin/slim -nodaemon
    ... after 1st "openbox logout"
    slim.service - SLiM Simple Login Manager
    Loaded: loaded (/usr/lib/systemd/system/slim.service; enabled)
    Active: active (running) since Di 2013-03-19 19:05:10 CET; 1min 50s ago
    Main PID: 241 (slim)
    CGroup: name=systemd:/system/slim.service
    ...after 2nt logout on tty1
    slim.service - SLiM Simple Login Manager
    Loaded: loaded (/usr/lib/systemd/system/slim.service; enabled)
    Active: failed (Result: exit-code) since Di 2013-03-19 19:07:04 CET; 23s ago
    Process: 241 ExecStart=/usr/bin/slim -nodaemon (code=exited, status=1/FAILURE)
    /var/log/slim.log
    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.
    systemctl list-units
    UNIT LOAD ACTIVE SUB DESCRIPTION
    proc-sys...t_misc.automount loaded active running Arbitrary Executable File Formats File System Automount Point
    sys-devi...-sda-sda1.device loaded active plugged IC25N080ATMR04-0
    sys-devi...-sda-sda2.device loaded active plugged IC25N080ATMR04-0
    sys-devi...-sda-sda3.device loaded active plugged IC25N080ATMR04-0
    sys-devi...-sda-sda4.device loaded active plugged IC25N080ATMR04-0
    sys-devi...block-sda.device loaded active plugged IC25N080ATMR04-0
    sys-devi...block-sr0.device loaded active plugged _NEC_DVD+_-RW_ND-6500A
    sys-devi...und-card0.device loaded active plugged /sys/devices/pci0000:00/0000:00:02.7/sound/card0
    sys-devi...et-enp0s4.device loaded active plugged /sys/devices/pci0000:00/0000:00:04.0/net/enp0s4
    sys-devi...et-wlp2s0.device loaded active plugged /sys/devices/pci0000:00/0000:00:09.0/0000:02:00.0/net/wlp2s0
    sys-devi...tty-ttyS0.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS0
    sys-devi...tty-ttyS1.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS1
    sys-devi...tty-ttyS2.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS2
    sys-devi...tty-ttyS3.device loaded active plugged /sys/devices/platform/serial8250/tty/ttyS3
    sys-module-configfs.device loaded active plugged /sys/module/configfs
    sys-subs...es-enp0s4.device loaded active plugged /sys/subsystem/net/devices/enp0s4
    sys-subs...es-wlp2s0.device loaded active plugged /sys/subsystem/net/devices/wlp2s0
    -.mount loaded active mounted /
    boot.mount loaded active mounted /boot
    dev-hugepages.mount loaded active mounted Huge Pages File System
    dev-mqueue.mount loaded active mounted POSIX Message Queue File System
    home.mount loaded active mounted /home
    proc-sys...infmt_misc.mount loaded active mounted Arbitrary Executable File Formats File System
    sys-kernel-config.mount loaded active mounted Configuration File System
    sys-kernel-debug.mount loaded active mounted Debug File System
    tmp.mount loaded active mounted Temporary Directory
    systemd-...ord-console.path loaded active waiting Dispatch Password Requests to Console Directory Watch
    systemd-...ssword-wall.path loaded active waiting Forward Password Requests to Wall Directory Watch
    dbus.service loaded active running D-Bus System Message Bus
    [email protected] loaded active running Getty on tty1
    net-auto-wireless.service loaded active running Provides automatic netcfg wireless connection
    ntpd.service loaded active running Network Time Service
    slim.service loaded failed failed SLiM Simple Login Manager
    systemd-binfmt.service loaded active exited Set Up Additional Binary Formats
    systemd-journald.service loaded active running Journal Service
    systemd-logind.service loaded active running Login Service
    systemd-remount-fs.service loaded active exited Remount Root and Kernel File Systems
    systemd-sysctl.service loaded active exited Apply Kernel Variables
    systemd-...es-setup.service loaded active exited Recreate Volatile Files and Directories
    systemd-...-trigger.service loaded active exited udev Coldplug all Devices
    systemd-udevd.service loaded active running udev Kernel Device Manager
    systemd-...sessions.service loaded active exited Permit User Sessions
    systemd-...le-setup.service loaded active exited Setup Virtual Console
    dbus.socket loaded active running D-Bus System Message Bus Socket
    dmeventd.socket loaded active listening Device-mapper event daemon FIFOs
    lvmetad.socket loaded active listening LVM2 metadata daemon socket
    systemd-initctl.socket loaded active listening /dev/initctl Compatibility Named Pipe
    systemd-journald.socket loaded active running Journal Socket
    systemd-shutdownd.socket loaded active listening Delayed Shutdown Socket
    systemd-...d-control.socket loaded active listening udev Control Socket
    systemd-udevd-kernel.socket loaded active running udev Kernel Socket
    dev-sda2.swap loaded active active /dev/sda2
    basic.target loaded active active Basic System
    cryptsetup.target loaded active active Encrypted Volumes
    getty.target loaded active active Login Prompts
    graphical.target loaded active active Graphical Interface
    local-fs-pre.target loaded active active Local File Systems (Pre)
    local-fs.target loaded active active Local File Systems
    multi-user.target loaded active active Multi-User
    network.target loaded active active Network
    remote-fs.target loaded active active Remote File Systems
    sockets.target loaded active active Sockets
    sound.target loaded active active Sound Card
    swap.target loaded active active Swap
    sysinit.target loaded active active System Initialization
    systemd-...iles-clean.timer loaded active waiting Daily Cleanup of Temporary Directories
    /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 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
    # Lock file
    lockfile /var/run/lock/slim.lock
    # Log file
    logfile /var/log/slim.log
    When i run "systemctl start slim" on tty1 slim starts again and after exiting openbox twice i'm back on tty1.
    ...But when i run "slim" on tty1 slim starts and i can exit openbox as often as i want.
    Any ideas ?
    Edit:
    Running /usr/bin/slim from tty1 gives me this logfile.
    /var/log/slim.log
    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: waiting for X server to shut down
    slim: waiting for X server to begin accepting connections.
    Somehow the second "slim: waiting for X server to shut down" does not happen when running "systemctl start slim"
    Last edited by Synth (2013-03-19 19:39:10)

    Ok, I was able to workaround parts of the bug:
    I changed slim.conf and and set daemon = true (so slim runs as a daemon). Furthermore changed the slim.service file for systemd:
    [Service]
    Type = forking
    PIDFile = /var/lock/slim.lock
    ExecStart=/usr/bin/slim
    Now I can log in and out as often as I want. Seems to work. However, nm-applet only shows up in odd numbers of logins:
    1st login --> nm-applet is shown
    2nd login --> nm-applet is not shown (but running --> htop)
    3rd login --> nm-applet is shown
    4th login --> nm-applet is not shown (but running --> htop)
    ...and so on...
    I search the web, it seems to be a problem with dbus and the order how the services get started. Don't know if that is true...any ideas from anyone?

  • [SOLVED] New slim, can't shutdown|reboot|suspend anymore

    Hi!
    I just upgraded slim, and i notice that i cannot suspend, shutdown and reboot anymore.
    And to mount usb drive, i am asked for my password.
    After the upgrade i changed /etc/slim.conf,pacnew to suit my needs and then sudo mv /etc/slim.conf.pacnew /etc/slim.conf .
    My .xinitrc is the same, so, where is the problem?
    here there are my 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 federico
    # 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
    and my .xinitrc:
    #!/bin/bash
    export BROWSER=chromium
    export DE=xfce
    exec ck-launch-session dbus-launch startxfce4
    Thanks!
    Last edited by nierro (2012-05-08 18:42:44)

    From later in this thread:
    Solution
    Ok, do:
    ck-list-sessions
    There were two sessions for myself.  So, the new slim is starting your exec line already with a console kit session.  This is new behavior.  It didn't before.
    So, I modified my exec line to remove "ck-launch-session" in .xinitrc to:
    exec dbus-launch --exit-with-session startxfce4
    Reverted the changes I made to the shutdown/restart policy and rebooted.  Shutdown, restart, mounting USB drive: they all work again now.
    Edit: from even later on in this thread, just:
    exec startxfce4
    As your .xinitrc exec line should be sufficient for practically anyone.  "startxfce4" does the dbus-launch itself.
    Original post here:
    Changed in my /etc/slim.conf:
    default_path        /bin:/usr/bin:/usr/local/bin:/sbin:/usr/sbin
    Same issue, in Action buttons Shutdown and Restart grayed out.
    in .xinitrc, launch line:
    exec ck-launch-session startxfce4
    Launch line was:
    exec ck-launch-session dbus-launch --exit-with-session startxfce4
    But, same issue with that launch line.  Was googling and I found results saying dbus-launch is contained within startxfce4.
    Last edited by headkase (2012-05-09 02:23:48)

  • How do I use an external hard drive to back up my laptop?  I bought a G Drive Slim from Apple.

    I have a G Drive Slim external hard drive that was purchased from an Apple store.  I need to back up my laptop.  I've forgotten the procedure.  It's not as easy as "plug it in and follow the instructions."  Can anyone help?

    It should be plug and play and if it isn't it is probably because your new drive isn't formatted for the Mac. Plug in the drive and run Disk Utility - it is in the Utilities folder inside the Applications folder. You should see the drive in the DU window. Click on the drive and look at the bottom of the DU program. You'll see a Drive Description and other information. The last item in the second column is Partition Map Scheme. If it says GUID Partition Table you are good to go. If it doesn't the drive needs to be partitioned to be GUID.
    Partition the drive:
    Select the drive device in the list of devices. For each physical drive you'll see a drive device and then indented under that you'll see a drive name. For example looking at DU on my computer I see two devices: Macintosh HD at the top and indented beneath it "Yosemite" then 2TB OWC Elite and indented beneath it "TM". I'd select 2TB OWC Elite
    Choose the "Partition" tab that appears.
    Select "1 Partition" from the drop-down menu (or more, if you have specific need for more than one volume). When you select a new partition layout from the drop-down menu, each new partition will be formatted to Mac OS Extended (Journaled) by default, but be sure to double-check this by selecting each in the partition diagram and then choosing the format for it.
    Click the Options button and ensure "GUID" is selected as the partition scheme.
    Click Apply to save the changes.
    Open Time Machine Preferences and click on Select Disk. Choose your newly partitioned and formatted drive. Make sure TM is turned on. That's it.

  • Venue 11 Pro - Slim Keyboard not behaving as expected or it should.

    I recently received the slim keyboard from dell for my Venue 11 Pro - Baytrail tablet.    Overall I like the quality and functionality, although I too like others have encountered the intermittent non-functional keyboard, but that's not the subject of this post.
    I have noticed a couple items in its behavior that don't work as you would expect and I hope can be corrected via software. 
    1. When the keyboard is attached but folded back behind the tablet (ie the keyboard is not in use) the on screen keyboard will not appear.  This makes it hard to use the device as a tablet as anytime data entry is required you need to unfold the keyboard and hold it somehow while you type then fold it back behind the screen to continue tablet use.   When folding the keyboard behind the unit its just as important to make the on screen keyboard available as it is to stop the keyboard itself from functioning,  right now the keyboard stops working as it should be no alternative input is available. 
    2. In much the same way as item #1.  When the keyboard is attached but folded back behind the tablet orientation is locked so the screen will not rotate to portrait or landscape mode at need.  So if you were carrying it with the cover / slim keyboard on and opened it up, folding the keyboard behind the screen the screen is stuck in landscape mode.   The only method ive found to change its orientation is to go to desktop and run the intel graphics app to edit the orientation.
    Combined this makes the slim keyboard worse than useless in several usage scenarios.   I want the slim keyboard for the occasional need to input more data than is practical on the touch screen AND to protect the tablet.... but if your usage is more tablet than notebook you will find yourself constantly working around these limitations.   
    You have a great product here, but you really need to take a page from the surface playbook here.   They kind of set the standard and expectations for how keyboard covers on tablets should work and while I really like the hardware the usage is awkward as it stands. 

    Just got our first Venue 11 into the office and was very disappointed to find this thread already active.  Yes, this is a very simple use-case where someone will have the slim keyboard connected and then flip it back to use the onscreen keyboard for the modern UI.  Auto screen rotation and pop-up onscreen keyboard really are a must when the keyboard is flipped back.  Not sure how that very basic behavior could have been missed in testing.  Hoping for a resolution soon...

  • Two Dell venue 11 pro + dell slim keyboard = one - work, one - not

    Have two Dell Venue 11 Pro - i5 8gb ram 256gb and i5 4gb ram 128gb
    And one dell slim keyboard.
    It works fine just with one tablet! Second device don't see keyboard - like it dead
    How can i connect it? what i need to do? or install some driver maybe?

    which port do you mean? 
    there are two same tablets and one slim keyboard. it works with one tablet, but not working with other
    i just unplugged it from one and plug-in to second tablet
    here is video
    cs_setInnerHtml('video_b26d630e-77c7-4a6d-b4bd-49606efd7cfd','');

  • [Solved] "slim: failed to execute login command" after awesomewm updat

    Hi,
    i updated some weeks ago via pacman -Syu, where also awesome wm was updated from 3.4.* to 3.5.* so I updated my rc.lua as it is told on their wiki, but i cant login with my rc.lua anymore i got the failed to execute login command error from slime. If i use the shipped efault rc.lua it works fine, can someone help me to figure out whats wrong with my rc.lua?
    -- Standard awesome library
    local gears = require("gears")
    local awful = require("awful")
    awful.rules = require("awful.rules")
    require("awful.autofocus")
    -- Widget and layout library
    local wibox = require("wibox")
    -- Theme handling library
    local beautiful = require("beautiful")
    -- Notification library
    local naughty = require("naughty")
    local menubar = require("menubar")
    local vicious = require("vicious")
    function fullscreens(c)
    awful.client.floating.toggle(c)
    if awful.client.floating.get(c) then
    local clientX = screen[1].workarea.x
    local clientY = screen[1].workarea.y
    local clientWidth = 0
    -- look at http://www.rpm.org/api/4.4.2.2/llimits_8h-source.html
    local clientHeight = 2147483640
    for s = 1, screen.count() do
    clientHeight = math.min(clientHeight, screen[s].workarea.height)
    clientWidth = clientWidth + screen[s].workarea.width
    end
    local t = c:geometry({x = clientX, y = clientY, width = clientWidth, height = clientHeight})
    else
    --apply the rules to this client so he can return to the right tag if there is a rule for that.
    awful.rules.apply(c)
    end
    -- focus our client
    client.focus = c
    end
    -- {{{ Error handling
    -- Check if awesome encountered an error during startup and fell back to
    -- another config (This code will only ever execute for the fallback config)
    if awesome.startup_errors then
    naughty.notify({ preset = naughty.config.presets.critical,
    title = "Oops, there were errors during startup!",
    text = awesome.startup_errors })
    end
    -- Handle runtime errors after startup
    do
    local in_error = false
    awesome.connect_signal("debug::error", function (err)
    -- Make sure we don't go into an endless error loop
    if in_error then return end
    in_error = true
    naughty.notify({ preset = naughty.config.presets.critical,
    title = "Oops, an error happened!",
    text = err })
    in_error = false
    end)
    end
    -- {{{ Variable definitions
    -- Themes define colours, icons, and wallpapers
    -- beautiful.init("/home/kili/Repositories/awesome-themes/arch/theme.lua")
    beautiful.init("/usr/share/awesome/themes/default/theme.lua")
    -- This is used later as the default terminal and editor to run.
    terminal = "urxvt"
    editor = os.getenv("EDITOR") or "nano"
    editor_cmd = terminal .. " -e " .. editor
    -- Default modkey.
    -- Usually, Mod4 is the key with a logo between Control and Alt.
    -- If you do not like this or do not have such a key,
    -- I suggest you to remap Mod4 to another key using xmodmap or other tools.
    -- However, you can use another modifier like Mod1, but it may interact with others.
    modkey = "Mod4"
    -- Table of layouts to cover with awful.layout.inc, order matters.
    layouts =
    awful.layout.suit.tile,
    awful.layout.suit.tile.left,
    awful.layout.suit.tile.bottom,
    awful.layout.suit.tile.top,
    awful.layout.suit.floating,
    awful.layout.suit.fair,
    awful.layout.suit.fair.horizontal,
    awful.layout.suit.spiral,
    awful.layout.suit.spiral.dwindle,
    awful.layout.suit.max,
    awful.layout.suit.max.fullscreen,
    awful.layout.suit.magnifier
    -- {{{ Tags
    -- Define a tag table which hold all screen tags.
    tags = {}
    for s = 1, screen.count() do
    -- Each screen has its own tag table.
    tags[s] = awful.tag({ 1, 2, 3, 4, 5}, s, layouts[1])
    end
    -- {{{ Menu
    -- Create a laucher widget and a main menu
    myawesomemenu = {
    { "manual", terminal .. " -e man awesome" },
    { "edit config", editor_cmd .. " " .. awesome.conffile },
    { "restart", awesome.restart },
    { "quit", awesome.quit }
    mymainmenu = awful.menu({ items = { { "awesome", myawesomemenu, beautiful.awesome_icon },
    { "open terminal", terminal }
    mylauncher = awful.widget.launcher({ image = beautiful.awesome_icon, menu = mymainmenu })
    -- {{{ Wibox
    -- Create a textclock widget
    batwidget = wibox.widget.textbox()
    vicious.register(batwidget, vicious.widgets.bat,
    function(widget,args)
    local formatstring = " Bat: "..args[1]..args[2] .."%".. " "..args[3] .. " "
    if args[2] <= 25 and args[1] == "-" then
    return "<span color=\"red\">".. formatstring .. "</span>"
    end
    return formatstring
    end, 60, "BAT0")
    netwidgetETH = wibox.widget.textbox()
    netwidgetWIFI = wibox.widget.textbox()
    vicious.register(netwidgetETH, vicious.widgets.net, ' eth0:<span color="#CC9393">${eth0 down_kb}</span> <span color="#7F9F7F">${eth0 up_kb}</span>', 3)
    vicious.register(netwidgetWIFI, vicious.widgets.net,' wlan0:<span color="#CC9393">${wlan0 down_kb}</span> <span color="#7F9F7F">${wlan0 up_kb}</span>', 3)
    menubar.utils.terminal = terminal
    mytextclock = awful.widget.textclock()--{ align = "right" })
    -- Create a systray
    mysystray = wibox.widget.systray()
    -- Create a wibox for each screen and add it
    mywibox = {}
    mypromptbox = {}
    mylayoutbox = {}
    mytaglist = {}
    mytaglist.buttons = awful.util.table.join(
    awful.button({ }, 1, awful.tag.viewonly),
    awful.button({ modkey }, 1, awful.client.movetotag),
    awful.button({ }, 3, awful.tag.viewtoggle),
    awful.button({ modkey }, 3, awful.client.toggletag),
    awful.button({ }, 4, function(t) awful.tag.viewnext(aweful.tag.getscreen(t)) end),
    awful.button({ }, 5, function(t) awful.tag.viewprev(aweful.tag.getscreen(t)) end)
    mytasklist = {}
    mytasklist.buttons = awful.util.table.join(
    awful.button({ }, 1, function (c)
    if c == client.focus then
    c.minimized = true
    else
    c.minimized = false
    if not c:isvisible() then
    awful.tag.viewonly(c:tags()[1])
    end
    -- This will also un-minimize
    -- the client, if needed
    client.focus = c
    c:raise()
    end
    end),
    awful.button({ }, 3, function ()
    if instance then
    instance:hide()
    instance = nil
    else
    instance = awful.menu.clients({ width=250 })
    end
    end),
    awful.button({ }, 4, function ()
    awful.client.focus.byidx(1)
    if client.focus then client.focus:raise() end
    end),
    awful.button({ }, 5, function ()
    awful.client.focus.byidx(-1)
    if client.focus then client.focus:raise() end
    end))
    for s = 1, screen.count() do
    -- Create a promptbox for each screen
    mypromptbox[s] = awful.widget.prompt()--{ layout = awful.widget.layout.horizontal.leftright })
    -- Create an imagebox widget which will contains an icon indicating which layout we're using.
    -- We need one layoutbox per screen.
    mylayoutbox[s] = awful.widget.layoutbox(s)
    mylayoutbox[s]:buttons(awful.util.table.join(
    awful.button({ }, 1, function () awful.layout.inc(layouts, 1) end),
    awful.button({ }, 3, function () awful.layout.inc(layouts, -1) end),
    awful.button({ }, 4, function () awful.layout.inc(layouts, 1) end),
    awful.button({ }, 5, function () awful.layout.inc(layouts, -1) end)))
    -- Create a taglist widget
    mytaglist[s] = awful.widget.taglist(s, awful.widget.taglist.filter.all, mytaglist.buttons)
    -- Create a tasklist widget
    mytasklist[s] = awful.widget.tasklist(s, awful.widget.tasklist.filter.currenttags, mytasklist.buttons)
    -- Create the wibox
    mywibox[s] = awful.wibox({ position = "top", screen = s })
    -- Widgets that are aligned to the left
    local left_layout = wibox.layout.fixed.horizontal()
    left_layout:add(mylauncher)
    left_layout:add(mytaglist[s])
    left_layout:add(mypromptbox[s])
    -- Widgets that are aligned to the right
    local right_layout = wibox.layout.fixed.horizontal()
    if s == 1 then right_layout:add(wibox.widget.systray()) end
    right_layout:add(netwidgetWIFI)
    right_layout:add(netwidgetETH)
    right_layout:add(batwidget)
    right_layout:add(mytextclock)
    right_layout:add(mylayoutbox[s])
    -- Now bring it all together (with the tasklist in the middle)
    local layout = wibox.layout.align.horizontal()
    layout:set_left(left_layout)
    layout:set_middle(mytasklist[s])
    layout:set_right(right_layout)
    mywibox[s]:set_widget(layout)
    -- Add widgets to the wibox - order matters
    --mywibox[s].widgets = {
    -- mylauncher,
    -- mytaglist[s],
    -- mypromptbox[s],
    --layout = awful.widget.layout.horizontal.leftright
    -- mylayoutbox[s],
    -- mytextclock,
    -- batwidget,
    -- netwidgetETH,
    -- netwidgetWIFI,
    -- s == 1 and mysystray or nil,
    -- mytasklist[s],
    -- layout = awful.widget.layout.horizontal.rightleft
    end
    -- {{{ Mouse bindings
    root.buttons(awful.util.table.join(
    awful.button({ }, 3, function () mymainmenu:toggle() end),
    awful.button({ }, 4, awful.tag.viewnext),
    awful.button({ }, 5, awful.tag.viewprev)
    -- {{{ Key bindings
    globalkeys = awful.util.table.join(
    awful.key({ modkey, }, "Left", awful.tag.viewprev ),
    awful.key({ modkey, }, "Right", awful.tag.viewnext ),
    awful.key({ modkey, }, "Escape", awful.tag.history.restore),
    awful.key({ modkey, }, "j",
    function ()
    awful.client.focus.byidx( 1)
    if client.focus then client.focus:raise() end
    end),
    awful.key({ modkey, }, "k",
    function ()
    awful.client.focus.byidx(-1)
    if client.focus then client.focus:raise() end
    end),
    awful.key({ modkey, }, "w", function () mymainmenu:show() end),
    -- Layout manipulation
    awful.key({ modkey, "Shift" }, "j", function () awful.client.swap.byidx( 1) end),
    awful.key({ modkey, "Shift" }, "k", function () awful.client.swap.byidx( -1) end),
    awful.key({ modkey, "Control" }, "j", function () awful.screen.focus_relative( 1) end),
    awful.key({ modkey, "Control" }, "k", function () awful.screen.focus_relative(-1) end),
    awful.key({ modkey, }, "u", awful.client.urgent.jumpto),
    awful.key({ modkey, }, "Tab",
    function ()
    awful.client.focus.history.previous()
    if client.focus then
    client.focus:raise()
    end
    end),
    -- Standard program
    awful.key({ modkey, }, "Return", function () awful.util.spawn(terminal) end),
    awful.key({ modkey, "Control" }, "r", awesome.restart),
    awful.key({ modkey, "Shift" }, "q", awesome.quit),
    awful.key({ modkey, }, "l", function () awful.tag.incmwfact( 0.05) end),
    awful.key({ modkey, }, "h", function () awful.tag.incmwfact(-0.05) end),
    awful.key({ modkey, "Shift" }, "h", function () awful.tag.incnmaster( 1) end),
    awful.key({ modkey, "Shift" }, "l", function () awful.tag.incnmaster(-1) end),
    awful.key({ modkey, "Control" }, "h", function () awful.tag.incncol( 1) end),
    awful.key({ modkey, "Control" }, "l", function () awful.tag.incncol(-1) end),
    awful.key({ modkey, }, "space", function () awful.layout.inc(layouts, 1) end),
    awful.key({ modkey, "Shift" }, "space", function () awful.layout.inc(layouts, -1) end),
    awful.key({ modkey, "Control" }, "n", awful.client.restore),
    -- Prompt
    awful.key({ modkey }, "r", function () mypromptbox[mouse.screen]:run() end),
    awful.key({ modkey }, "x",
    function ()
    awful.prompt.run({ prompt = "Run Lua code: " },
    mypromptbox[mouse.screen].widget,
    awful.util.eval, nil,
    awful.util.getdir("cache") .. "/history_eval")
    end),
    -- Multimedia
    awful.key({ }, "XF86AudioLowerVolume", function () awful.util.spawn("amixer -q sset Master 2dB-") end),
    awful.key({ }, "XF86AudioRaiseVolume", function () awful.util.spawn("amixer -q sset Master 2dB+") end),
    awful.key({ }, "XF86AudioNext",function () awful.util.spawn( "mocp -f" ) end),
    awful.key({ }, "XF86AudioPrev",function () awful.util.spawn( "mocp -r" ) end),
    awful.key({ }, "XF86AudioPlay",function () awful.util.spawn( "mocp -G" ) end),
    awful.key({ }, "Print", function () awful.util.spawn("ksnapshot") end),
    awful.key({ }, "", function () awful.util.spawn("slimlock") end)
    clientkeys = awful.util.table.join(
    awful.key({ modkey, }, "f", function (c) c.fullscreen = not c.fullscreen end),
    awful.key({ modkey, "Shift" }, "c", function (c) c:kill() end),
    awful.key({ modkey, "Control" }, "space", awful.client.floating.toggle ),
    awful.key({ modkey, "Control" }, "Return", function (c) c:swap(awful.client.getmaster()) end),
    awful.key({ modkey, }, "o", awful.client.movetoscreen ),
    -- awful.key({ modkey, "Shift" }, "r", function (c) c:redraw() end),
    awful.key({ modkey, }, "t", function (c) c.ontop = not c.ontop end),
    awful.key({ modkey, }, "n",
    function (c)
    -- The client currently has the input focus, so it cannot be
    -- minimized, since minimized clients can't have the focus.
    c.minimized = true
    end),
    awful.key({ modkey, }, "m",
    function (c)
    c.maximized_horizontal = not c.maximized_horizontal
    c.maximized_vertical = not c.maximized_vertical
    end),
    awful.key({ modkey, "Shift" }, "f", fullscreens)
    -- Compute the maximum number of digit we need, limited to 9
    keynumber = 0
    for s = 1, screen.count() do
    keynumber = math.min(9, math.max(#tags[s], keynumber))
    end
    -- Bind all key numbers to tags.
    -- Be careful: we use keycodes to make it works on any keyboard layout.
    -- This should map on the top row of your keyboard, usually 1 to 9.
    for i = 1, keynumber do
    globalkeys = awful.util.table.join(globalkeys,
    awful.key({ modkey }, "#" .. i + 9,
    function ()
    local screen = mouse.screen
    if tags[screen][i] then
    awful.tag.viewonly(tags[screen][i])
    end
    end),
    awful.key({ modkey, "Control" }, "#" .. i + 9,
    function ()
    local screen = mouse.screen
    if tags[screen][i] then
    awful.tag.viewtoggle(tags[screen][i])
    end
    end),
    awful.key({ modkey, "Shift" }, "#" .. i + 9,
    function ()
    if client.focus and tags[client.focus.screen][i] then
    awful.client.movetotag(tags[client.focus.screen][i])
    end
    end),
    awful.key({ modkey, "Control", "Shift" }, "#" .. i + 9,
    function ()
    if client.focus and tags[client.focus.screen][i] then
    awful.client.toggletag(tags[client.focus.screen][i])
    end
    end))
    end
    clientbuttons = awful.util.table.join(
    awful.button({ }, 1, function (c) client.focus = c; c:raise() end),
    awful.button({ modkey }, 1, awful.mouse.client.move),
    awful.button({ modkey }, 3, awful.mouse.client.resize))
    -- Set keys
    root.keys(globalkeys)
    -- Set Firefox to always map on tags number 2 of screen 1.
    -- { rule = { class = "Firefox" },
    -- properties = { tag = tags[1][2] } },
    -- {{{ Rules
    if screen.count() > 1 then
    awful.rules.rules = {
    -- All clients will match this rule.
    { rule = { },
    properties = { border_width = beautiful.border_width,
    -- border_color = beautiful.border_normal,
    focus = true,
    keys = clientkeys,
    buttons = clientbuttons } },
    { rule = { class = "MPlayer" },
    properties = { floating = true } },
    { rule = { class = "gimp" },
    properties = { floating = true } },
    { rule = { class = "Xdialog" },
    properties = { floating = true } },
    { rule = { class = "Firefox" },
    properties = { tag = tags[1][1] } },
    { rule = { name = "Thunderbird" },
    properties = { tag = tags[1][2] } },
    { rule = { instance = "plugin-container" },
    properties = { floating = true } },
    { rule = { class = "Luakit" },
    properties = { floating = true } }
    else
    awful.rules.rules = {
    -- All clients will match this rule.
    { rule = { },
    properties = { border_width = beautiful.border_width,
    -- border_color = beautiful.border_normal,
    focus = true,
    keys = clientkeys,
    buttons = clientbuttons } },
    { rule = { class = "MPlayer" },
    properties = { floating = true } },
    { rule = { class = "gimp" },
    properties = { floating = true } },
    { rule = { class = "Firefox" },
    properties = { tag = tags[1][2] } },
    { rule = { name = "Thunderbird" },
    properties = { tag = tags[1][3] } },
    { rule = { instance = "plugin-container" },
    properties = { floating = true, fullscreen = true } },
    { rule = { class = "Dolphin" },
    properties = { floating = false, fullscreen = false, tag = tags[1][4] } },
    { rule = { class = "Luakit" },
    properties = { floating = true } },
    { rule = { class = "Pidgin" },
    properties = { tag = tags[1][5] } }
    end
    -- {{{ Signals
    -- Signal function to execute when a new client appears.
    client.connect_signal("manage", function (c, startup)
    -- Add a titlebar
    -- awful.titlebar.add(c, { modkey = modkey })
    -- Enable sloppy focus
    c:connect_signal("mouse::enter", function(c)
    if awful.layout.get(c.screen) ~= awful.layout.suit.magnifier
    and awful.client.focus.filter(c) then
    client.focus = c
    end
    end)
    if not startup then
    -- Set the windows at the slave,
    -- i.e. put it at the end of others instead of setting it master.
    -- awful.client.setslave(c)
    -- Put windows in a smart way, only if they does not set an initial position.
    if not c.size_hints.user_position and not c.size_hints.program_position then
    awful.placement.no_overlap(c)
    awful.placement.no_offscreen(c)
    end
    end
    local titlebars_enabled = false
    if titlebars_enabled and (c.type == "normal" or c.type == "dialog") then
    -- Widgets that are aligned to the left
    local left_layout = wibox.layout.fixed.horizontal()
    left_layout:add(awful.titlebar.widget.iconwidget(c))
    -- Widgets that are aligned to the right
    local right_layout = wibox.layout.fixed.horizontal()
    right_layout:add(awful.titlebar.widget.floatingbutton(c))
    right_layout:add(awful.titlebar.widget.maximizedbutton(c))
    right_layout:add(awful.titlebar.widget.stickybutton(c))
    right_layout:add(awful.titlebar.widget.ontopbutton(c))
    right_layout:add(awful.titlebar.widget.closebutton(c))
    -- The title goes in the middle
    local title = awful.titlebar.widget.titlewidget(c)
    title:buttons(awful.util.table.join(
    awful.button({ }, 1, function()
    client.focus = c
    c:raise()
    awful.mouse.client.move(c)
    end),
    awful.button({ }, 3, function()
    client.focus = c
    c:raise()
    awful.mouse.client.resize(c)
    end)
    -- Now bring it all together
    local layout = wibox.layout.align.horizontal()
    layout:set_left(left_layout)
    layout:set_right(right_layout)
    layout:set_middle(title)
    awful.titlebar(c):set_widget(layout)
    end
    end)
    client.connect_signal("focus", function(c) c.border_color = beautiful.border_focus end)
    client.connect_signal("unfocus", function(c) c.border_color = beautiful.border_normal end)
    Here is also my slime config and my initrc
    ls -lisa .xinitrc
    3276814 4 -rwxr-xr-x ...
    #!/bin/sh
    xrdb -merge ~/.Xresources
    wicd-client --tray &
    exec awesome #>> ~/.cache/awesome/stdout 2>> ~/.cache/awesome/stderr
    # 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 awesome,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 kili
    # Focus the password field on start when default_user is set
    # Set to "yes" to enable this feature
    focus_password yes
    # 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 archlinux-simplyblack
    # Lock file
    lockfile /var/lock/slim.lock
    # Log file
    logfile /var/log/slim.log
    Thanks in advance!
    Edit:
    Besides a lot of other errors the problem was the systray. It was created 2 times, now login works again. I figured that out via enabling logging for awesome in the xinitrc again.
    Last edited by stubb (2013-01-08 23:20:05)

    Hi,
    I have the same kind of issue after updated slim from v1.3.4-4 to v1.3.5-1.
    see my topic  here :
    https://bbs.archlinux.org/viewtopic.php?id=156792
    Last edited by cedricl (2013-01-24 17:16:42)

  • Shockwave Player updates, gives 2 options, full or slim - nothing explains the difference How do I know what to use

    McAfee program searches for programs that are susceptible to malware and automatically searched for updates and installs them. For some Reason, when it comes to Adobe products it requires myself to have to perform a manual update.  
    When I followed the link McAfee provides to the Adobe website and follow the steps to install the update....at one point it give you and option of an update that as the word "Full" in the middle of the Update Choice, and the 2nd option is exactly the same except instead of the word "Full", it has the word "Slim".
    Nowhere (FAQs, etc) can I find the difference between the two, so how do I know which I need?
    I have a Dell Laptop with Windows 8.1 operating system.  
    8GB Ram  and I think its one of those Quad Drive things
    1 TB Memory
    I use Firefox as my internet operating system.  
    I started with Internet Explorer, but a problem existed that had something to do with that program not being loaded properly initially,
    I tried to Get Microsoft Help but they wanted $149 to fix it, So I abandoned use of Internet Explorer and loaded Fire Fox.
    I will note, I don't know if its germane or note,  Since switching to Fire Fox,   my system stalls quite frequently and I get a popup that says something about a Flash Program (maybe shockwave flash) and it states it is not responding.  It gives me the option to continue or cancel and a check box to not ask me again.   Though I select that check box I do get asked often.
    When this Popup occurs, I can't use any of the internet windows I have open or any of the internet window Tabs I have open.  It also seems to affect the one game I play (Spider) and it stalls that game also.  I sense it has something to do with anything that has pictures on it possibly.  After several minutes 3 to 5 plus it seems to recover
    I'm sorry I am not real computer literate
    Thank you for any help you can provide
    Keith
    PS  All I am trying to do is get hold of Adobe to ask about their program, why I have to do all this registering and go into a Forum or Community (whatever those are) is confusing to me.

    The Full version includes all xtras and the Slim version just the bare essentials. I would recommend using the full version as your experience of using the plugin will be more seamless (no pausing while required xtras are downloaded on demand)

Maybe you are looking for