XFCE login manager

In the wiki of XFCE it recommends to use Slim as the login manager: I use it via inittab, but the same wiki states that Slim's development has been dropped and suggests to use LXDE for this... how can we setup a login manager via inittab with LXDE? Its not really clearly explained..... and i'm a bit lost in this.

Have a look at these links:
    https://wiki.archlinux.org/index.php/Xinitrc
    https://wiki.archlinux.org/index.php/Login_manager

Similar Messages

  • Login manager

    So I think I finally got most everything Installed and working, and I can finally say that Arch is the distro for me.  There are however some things I'd like to workout.  I want to use a login manager instead of having to login and typing startx.  I use xfce and I don't really want to have to install all of KDE or gnome just to get a login manager.  From what I can tell Kdm(KDE), Gdm(Gnome), and Xdm are my only choices.  What is Xdm and is it worth it?  If so please give me links on a guide to install it.

    This might interest you:
    http://wiki2.archlinux.org/index.php/Ad … %20startup
    http://wiki2.archlinux.org/index.php/Ad … 20to%20XDM

  • [SOLVED] Lid doesn't suspend anymore with xfce power manager

    The options "When laptop lid is closed" are set to suspend (and used to work), but still, when I close my lid, nothing happens. Using the logout dialog or the suspend button my keyboard works. Is it a problem with xfce-power-manager, or ACPI not registering the lid event anymore? Any idea how to fix that?
    [edit]
    I solved that problem by removing ~/.config/xfce4/xfconf/xfce-perchannel-xml/xfce4-power-manager.xml, killing the power manager and reloging in my session to flush the settings. Then I reconfigured the lid closed action to suspend (and everything else to my liking).
    Last edited by benob (2009-07-08 17:36:47)

    Sorry to bother you again, but for some reason it doesn't work anymore...
    Somehow it can't lock the GNOME session, because when I enter the above line from /etc/acpi/handler.sh manually as root in TTY1, I get this error:
    ** Message: Failed to get session bus: Befehlszeile »dbus-launch --autolaunch=c9375f4ea0008d92177b28db000009ae --binary-syntax --close-stderr« brach mit von Null verschiedenem Beenden-Status 1 ab: No protocol specified\nAutolaunch error: X11 initialization failed.\n
    If I enter this command inside GNOME, everything works just fine, it locks the screen and suspends.
    EDIT:
    Setting the XAUTHORITY environment variable properly did the trick. Therefore, I borrowed some lines from here: https://wiki.archlinux.org/index.php/Su … losing_lid
    Thread marked as SOLVED again.
    Last edited by perpetrator (2011-10-17 14:25:11)

  • The GNOME login manager crashes upon booting

    Every time I start up Arch, I get a window with a sad face in a computer saying that there was a problem and I have the option to log out which does nothing. The only way I am able to access my desktop is to open another terminal, manually log in, and run "startx." The login manager appeared one time but I have no clue how it happened. This is a fresh install of Arch that I installed yesterday. I am not familiar with troubleshooting so could you tell me what logs to post here? Here is a log file named :0.log which was located in the GDM log folder. This might say something about my issue.
    X.Org X Server 1.15.0
    Release Date: 2013-12-27
    X Protocol Version 11, Revision 0
    Build Operating System: Linux 3.12.5-1-ARCH x86_64
    Current Operating System: Linux SERN 3.13.8-1-ARCH #1 SMP PREEMPT Tue Apr 1 12:19:51 CEST 2014 x86_64
    Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=ae1186fc-165e-4d4d-949a-ccf939e3da53 rw quiet elevator=deadline
    Build Date: 09 January 2014 08:47:24AM
    Current version of pixman: 0.32.4
    Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    (==) Log file: "/var/log/Xorg.0.log", Time: Sat Apr 5 11:55:11 2014
    (==) Using config directory: "/etc/X11/xorg.conf.d"
    (==) No Layout section. Using the first Screen section.
    (==) No screen section available. Using defaults.
    (**) |-->Screen "Default Screen Section" (0)
    (**) | |-->Monitor "<default monitor>"
    (==) No monitor specified for screen "Default Screen Section".
    Using a default monitor configuration.
    (==) Automatically adding devices
    (==) Automatically enabling devices
    (==) Automatically adding GPU devices
    (WW) The directory "/usr/share/fonts/OTF/" does not exist.
    Entry deleted from font path.
    (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
    Entry deleted from font path.
    (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
    (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
    Entry deleted from font path.
    (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
    (==) FontPath set to:
    /usr/share/fonts/misc/,
    /usr/share/fonts/TTF/,
    /usr/share/fonts/Type1/
    (==) ModulePath set to "/usr/lib/xorg/modules"
    (II) The server relies on udev to provide the list of input devices.
    If no devices become available, reconfigure udev or disable AutoAddDevices.
    (--) PCI:*(0:1:0:0) 10de:1187:1462:2847 rev 161, Mem @ 0xfd000000/16777216, 0xf0000000/134217728, 0xf8000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/524288
    Initializing built-in extension Generic Event Extension
    Initializing built-in extension SHAPE
    Initializing built-in extension MIT-SHM
    Initializing built-in extension XInputExtension
    Initializing built-in extension XTEST
    Initializing built-in extension BIG-REQUESTS
    Initializing built-in extension SYNC
    Initializing built-in extension XKEYBOARD
    Initializing built-in extension XC-MISC
    Initializing built-in extension SECURITY
    Initializing built-in extension XINERAMA
    Initializing built-in extension XFIXES
    Initializing built-in extension RENDER
    Initializing built-in extension RANDR
    Initializing built-in extension COMPOSITE
    Initializing built-in extension DAMAGE
    Initializing built-in extension MIT-SCREEN-SAVER
    Initializing built-in extension DOUBLE-BUFFER
    Initializing built-in extension RECORD
    Initializing built-in extension DPMS
    Initializing built-in extension Present
    Initializing built-in extension DRI3
    Initializing built-in extension X-Resource
    Initializing built-in extension XVideo
    Initializing built-in extension XVideo-MotionCompensation
    Initializing built-in extension XFree86-VidModeExtension
    Initializing built-in extension XFree86-DGA
    Initializing built-in extension XFree86-DRI
    Initializing built-in extension DRI2
    (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    (II) Module glx: vendor="NVIDIA Corporation"
    compiled for 4.0.2, module version = 1.0.0
    (II) NVIDIA GLX Module 334.21 Thu Feb 27 13:54:04 PST 2014
    Loading extension GLX
    (==) Matched nouveau as autoconfigured driver 0
    (==) Matched nvidia as autoconfigured driver 1
    (==) Matched nv as autoconfigured driver 2
    (==) Matched modesetting as autoconfigured driver 3
    (==) Matched fbdev as autoconfigured driver 4
    (==) Matched vesa as autoconfigured driver 5
    (==) Assigned the driver to the xf86ConfigLayout
    (WW) Warning, couldn't open module nouveau
    (II) Unloading nouveau
    (EE) Failed to load module "nouveau" (module does not exist, 0)
    (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
    (II) Module nvidia: vendor="NVIDIA Corporation"
    compiled for 4.0.2, module version = 1.0.0
    (WW) Warning, couldn't open module nv
    (II) Unloading nv
    (EE) Failed to load module "nv" (module does not exist, 0)
    (WW) Warning, couldn't open module modesetting
    (II) Unloading modesetting
    (EE) Failed to load module "modesetting" (module does not exist, 0)
    (WW) Warning, couldn't open module fbdev
    (II) Unloading fbdev
    (EE) Failed to load module "fbdev" (module does not exist, 0)
    (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
    (II) Module vesa: vendor="X.Org Foundation"
    compiled for 1.15.0, module version = 2.3.2
    (II) NVIDIA dlloader X Driver 334.21 Thu Feb 27 13:34:35 PST 2014
    (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
    (II) VESA: driver for VESA chipsets: vesa
    (++) using VT number 1
    (II) Loading /usr/lib/xorg/modules/libfb.so
    (II) Module fb: vendor="X.Org Foundation"
    compiled for 1.15.0, module version = 1.0.0
    (WW) Unresolved symbol: fbGetGCPrivateKey
    (II) Loading /usr/lib/xorg/modules/libwfb.so
    (II) Module wfb: vendor="X.Org Foundation"
    compiled for 1.15.0, module version = 1.0.0
    (EE) NVIDIA: Failed to initialize the NVIDIA kernel module. Please see the
    (EE) NVIDIA: system's kernel log for additional error messages and
    (EE) NVIDIA: consult the NVIDIA README for details.
    (II) Loading /usr/lib/xorg/modules/libvbe.so
    (II) Module vbe: vendor="X.Org Foundation"
    compiled for 1.15.0, module version = 1.1.0
    (II) Loading /usr/lib/xorg/modules/libint10.so
    (II) Module int10: vendor="X.Org Foundation"
    compiled for 1.15.0, module version = 1.0.0
    (II) VESA(0): initializing int10
    (II) VESA(0): Primary V_BIOS segment is: 0xc000
    (II) VESA(0): VESA BIOS detected
    (II) VESA(0): Creating default Display subsection in Screen section
    "Default Screen Section" for depth/fbbpp 24/32
    (==) VESA(0): Depth 24, (--) framebuffer bpp 32
    (==) VESA(0): RGB weight 888
    (==) VESA(0): Default visual is TrueColor
    (==) VESA(0): Using gamma correction (1.0, 1.0, 1.0)
    (II) VESA(0): VESA VBE DDC supported
    (II) VESA(0): <default monitor>: Using default hsync range of 31.50-48.00 kHz
    (II) VESA(0): <default monitor>: Using default vrefresh range of 50.00-70.00 Hz
    (II) VESA(0): <default monitor>: Using default maximum pixel clock of 65.00 MHz
    (WW) VESA(0): Unable to estimate virtual size
    (II) VESA(0): Not using built-in mode "1920x1080" (no mode of this name)
    (II) VESA(0): Not using built-in mode "1280x1024" (no mode of this name)
    (II) VESA(0): Not using built-in mode "1280x800" (no mode of this name)
    (II) VESA(0): Not using built-in mode "1024x768" (no mode of this name)
    (II) VESA(0): Not using built-in mode "800x600" (no mode of this name)
    (II) VESA(0): Not using built-in mode "640x480" (no mode of this name)
    (II) VESA(0): Not using built-in mode "640x400" (no mode of this name)
    (II) VESA(0): Not using built-in mode "320x400" (no mode of this name)
    (II) VESA(0): Not using built-in mode "320x240" (no mode of this name)
    (II) VESA(0): Not using built-in mode "320x200" (no mode of this name)
    (WW) VESA(0): No valid modes left. Trying less strict filter...
    (II) VESA(0): <default monitor>: Using hsync range of 31.50-48.00 kHz
    (II) VESA(0): <default monitor>: Using vrefresh range of 50.00-70.00 Hz
    (II) VESA(0): <default monitor>: Using maximum pixel clock of 65.00 MHz
    (WW) VESA(0): Unable to estimate virtual size
    (II) VESA(0): Not using built-in mode "1920x1080" (hsync out of range)
    (II) VESA(0): Not using built-in mode "1280x1024" (hsync out of range)
    (II) VESA(0): Not using built-in mode "1280x800" (hsync out of range)
    (II) VESA(0): Not using built-in mode "640x400" (hsync out of range)
    (II) VESA(0): Not using built-in mode "320x400" (hsync out of range)
    (II) VESA(0): Not using built-in mode "320x240" (illegal horizontal timings)
    (II) VESA(0): Not using built-in mode "320x200" (illegal horizontal timings)
    (--) VESA(0): Virtual size is 1024x768 (pitch 1024)
    (**) VESA(0): *Built-in mode "1024x768"
    (**) VESA(0): *Built-in mode "800x600"
    (**) VESA(0): *Built-in mode "640x480"
    (==) VESA(0): DPI set to (96, 96)
    (II) VESA(0): Attempting to use 60Hz refresh for mode "1024x768" (118)
    (II) VESA(0): Attempting to use 60Hz refresh for mode "800x600" (115)
    (II) VESA(0): Attempting to use 60Hz refresh for mode "640x480" (112)
    (**) VESA(0): Using "Shadow Framebuffer"
    (II) Loading /usr/lib/xorg/modules/libshadow.so
    (II) Module shadow: vendor="X.Org Foundation"
    compiled for 1.15.0, module version = 1.1.0
    (II) Loading /usr/lib/xorg/modules/libfb.so
    (II) Module fb: vendor="X.Org Foundation"
    compiled for 1.15.0, module version = 1.0.0
    (==) Depth 24 pixmap format is 32 bpp
    (II) Loading /usr/lib/xorg/modules/libint10.so
    (II) Module int10: vendor="X.Org Foundation"
    compiled for 1.15.0, module version = 1.0.0
    (II) VESA(0): initializing int10
    (II) VESA(0): Primary V_BIOS segment is: 0xc000
    (II) VESA(0): VESA BIOS detected
    (II) VESA(0): Setting up VESA Mode 0x118 (1024x768)
    (==) VESA(0): Default visual is TrueColor
    (==) VESA(0): Backing store enabled
    (==) VESA(0): DPMS enabled
    (==) RandR enabled
    (EE) Failed to initialize GLX extension (Compatible NVIDIA X driver not found)
    (II) config/udev: Adding input device Power Button (/dev/input/event2)
    (**) Power Button: Applying InputClass "evdev keyboard catchall"
    (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    (II) Module evdev: vendor="X.Org Foundation"
    compiled for 1.15.0, module version = 2.8.2
    (II) Using input driver 'evdev' for 'Power Button'
    (**) Power Button: always reports core events
    (**) evdev: Power Button: Device: "/dev/input/event2"
    (--) evdev: Power Button: Vendor 0 Product 0x1
    (--) evdev: Power Button: Found keys
    (II) evdev: Power Button: Configuring as keyboard
    (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
    (II) config/udev: Adding input device Power Button (/dev/input/event1)
    (**) Power Button: Applying InputClass "evdev keyboard catchall"
    (II) Using input driver 'evdev' for 'Power Button'
    (**) Power Button: always reports core events
    (**) evdev: Power Button: Device: "/dev/input/event1"
    (--) evdev: Power Button: Vendor 0 Product 0x1
    (--) evdev: Power Button: Found keys
    (II) evdev: Power Button: Configuring as keyboard
    (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
    (II) config/udev: Adding drm device (/dev/dri/card0)
    (II) xfree86: Adding drm device (/dev/dri/card0)
    (WW) Warning, couldn't open module modesetting
    (II) Unloading modesetting
    (EE) Failed to load module "modesetting" (module does not exist, 0)
    xf86: found device 0
    (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event17)
    (II) No input driver specified, ignoring this device.
    (II) This device may have been added with another device file.
    (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event16)
    (II) No input driver specified, ignoring this device.
    (II) This device may have been added with another device file.
    (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event15)
    (II) No input driver specified, ignoring this device.
    (II) This device may have been added with another device file.
    (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=9 (/dev/input/event14)
    (II) No input driver specified, ignoring this device.
    (II) This device may have been added with another device file.
    (II) config/udev: Adding input device Audio-Technica ATR USB microphone (/dev/input/event0)
    (**) Audio-Technica ATR USB microphone : Applying InputClass "evdev keyboard catchall"
    (II) Using input driver 'evdev' for 'Audio-Technica ATR USB microphone '
    (**) Audio-Technica ATR USB microphone : always reports core events
    (**) evdev: Audio-Technica ATR USB microphone : Device: "/dev/input/event0"
    (--) evdev: Audio-Technica ATR USB microphone : Vendor 0x909 Product 0x1a
    (--) evdev: Audio-Technica ATR USB microphone : Found 1 mouse buttons
    (--) evdev: Audio-Technica ATR USB microphone : Found absolute axes
    (--) evdev: Audio-Technica ATR USB microphone : Found absolute multitouch axes
    (II) evdev: Audio-Technica ATR USB microphone : Forcing absolute x/y axes to exist.
    (--) evdev: Audio-Technica ATR USB microphone : Found keys
    (II) evdev: Audio-Technica ATR USB microphone : Forcing relative x/y axes to exist.
    (II) evdev: Audio-Technica ATR USB microphone : Configuring as mouse
    (II) evdev: Audio-Technica ATR USB microphone : Configuring as keyboard
    (**) evdev: Audio-Technica ATR USB microphone : YAxisMapping: buttons 4 and 5
    (**) evdev: Audio-Technica ATR USB microphone : EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    (II) XINPUT: Adding extended input device "Audio-Technica ATR USB microphone " (type: KEYBOARD, id 8)
    (II) evdev: Audio-Technica ATR USB microphone : initialized for absolute axes.
    (**) Audio-Technica ATR USB microphone : (accel) keeping acceleration scheme 1
    (**) Audio-Technica ATR USB microphone : (accel) acceleration profile 0
    (**) Audio-Technica ATR USB microphone : (accel) acceleration factor: 2.000
    (**) Audio-Technica ATR USB microphone : (accel) acceleration threshold: 4
    (II) config/udev: Adding input device HDA ATI SB Line Out Side (/dev/input/event5)
    (II) No input driver specified, ignoring this device.
    (II) This device may have been added with another device file.
    (II) config/udev: Adding input device HDA ATI SB Front Headphone (/dev/input/event4)
    (II) No input driver specified, ignoring this device.
    (II) This device may have been added with another device file.
    (II) config/udev: Adding input device HDA ATI SB Front Mic (/dev/input/event11)
    (II) No input driver specified, ignoring this device.
    (II) This device may have been added with another device file.
    (II) config/udev: Adding input device HDA ATI SB Rear Mic (/dev/input/event10)
    (II) No input driver specified, ignoring this device.
    (II) This device may have been added with another device file.
    (II) config/udev: Adding input device HDA ATI SB Line (/dev/input/event9)
    (II) No input driver specified, ignoring this device.
    (II) This device may have been added with another device file.
    (II) config/udev: Adding input device HDA ATI SB Line Out Front (/dev/input/event8)
    (II) No input driver specified, ignoring this device.
    (II) This device may have been added with another device file.
    (II) config/udev: Adding input device HDA ATI SB Line Out Surround (/dev/input/event7)
    (II) No input driver specified, ignoring this device.
    (II) This device may have been added with another device file.
    (II) config/udev: Adding input device HDA ATI SB Line Out CLFE (/dev/input/event6)
    (II) No input driver specified, ignoring this device.
    (II) This device may have been added with another device file.
    (II) config/udev: Adding input device Logitech Unifying Device. Wireless PID:1025 (/dev/input/event12)
    (**) Logitech Unifying Device. Wireless PID:1025: Applying InputClass "evdev pointer catchall"
    (II) Using input driver 'evdev' for 'Logitech Unifying Device. Wireless PID:1025'
    (**) Logitech Unifying Device. Wireless PID:1025: always reports core events
    (**) evdev: Logitech Unifying Device. Wireless PID:1025: Device: "/dev/input/event12"
    (--) evdev: Logitech Unifying Device. Wireless PID:1025: Vendor 0x46d Product 0xc52b
    (--) evdev: Logitech Unifying Device. Wireless PID:1025: Found 20 mouse buttons
    (--) evdev: Logitech Unifying Device. Wireless PID:1025: Found scroll wheel(s)
    (--) evdev: Logitech Unifying Device. Wireless PID:1025: Found relative axes
    (--) evdev: Logitech Unifying Device. Wireless PID:1025: Found x and y relative axes
    (II) evdev: Logitech Unifying Device. Wireless PID:1025: Configuring as mouse
    (II) evdev: Logitech Unifying Device. Wireless PID:1025: Adding scrollwheel support
    (**) evdev: Logitech Unifying Device. Wireless PID:1025: YAxisMapping: buttons 4 and 5
    (**) evdev: Logitech Unifying Device. Wireless PID:1025: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    (II) XINPUT: Adding extended input device "Logitech Unifying Device. Wireless PID:1025" (type: MOUSE, id 9)
    (II) evdev: Logitech Unifying Device. Wireless PID:1025: initialized for relative axes.
    (**) Logitech Unifying Device. Wireless PID:1025: (accel) keeping acceleration scheme 1
    (**) Logitech Unifying Device. Wireless PID:1025: (accel) acceleration profile 0
    (**) Logitech Unifying Device. Wireless PID:1025: (accel) acceleration factor: 2.000
    (**) Logitech Unifying Device. Wireless PID:1025: (accel) acceleration threshold: 4
    (II) config/udev: Adding input device Logitech Unifying Device. Wireless PID:1025 (/dev/input/mouse0)
    (II) No input driver specified, ignoring this device.
    (II) This device may have been added with another device file.
    (II) config/udev: Adding input device Logitech Unifying Device. Wireless PID:2016 (/dev/input/event13)
    (**) Logitech Unifying Device. Wireless PID:2016: Applying InputClass "evdev keyboard catchall"
    (II) Using input driver 'evdev' for 'Logitech Unifying Device. Wireless PID:2016'
    (**) Logitech Unifying Device. Wireless PID:2016: always reports core events
    (**) evdev: Logitech Unifying Device. Wireless PID:2016: Device: "/dev/input/event13"
    (--) evdev: Logitech Unifying Device. Wireless PID:2016: Vendor 0x46d Product 0xc52b
    (--) evdev: Logitech Unifying Device. Wireless PID:2016: Found 1 mouse buttons
    (--) evdev: Logitech Unifying Device. Wireless PID:2016: Found scroll wheel(s)
    (--) evdev: Logitech Unifying Device. Wireless PID:2016: Found relative axes
    (II) evdev: Logitech Unifying Device. Wireless PID:2016: Forcing relative x/y axes to exist.
    (--) evdev: Logitech Unifying Device. Wireless PID:2016: Found absolute axes
    (II) evdev: Logitech Unifying Device. Wireless PID:2016: Forcing absolute x/y axes to exist.
    (--) evdev: Logitech Unifying Device. Wireless PID:2016: Found keys
    (II) evdev: Logitech Unifying Device. Wireless PID:2016: Configuring as mouse
    (II) evdev: Logitech Unifying Device. Wireless PID:2016: Configuring as keyboard
    (II) evdev: Logitech Unifying Device. Wireless PID:2016: Adding scrollwheel support
    (**) evdev: Logitech Unifying Device. Wireless PID:2016: YAxisMapping: buttons 4 and 5
    (**) evdev: Logitech Unifying Device. Wireless PID:2016: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    (II) XINPUT: Adding extended input device "Logitech Unifying Device. Wireless PID:2016" (type: KEYBOARD, id 10)
    (II) evdev: Logitech Unifying Device. Wireless PID:2016: initialized for relative axes.
    (WW) evdev: Logitech Unifying Device. Wireless PID:2016: ignoring absolute axes.
    (**) Logitech Unifying Device. Wireless PID:2016: (accel) keeping acceleration scheme 1
    (**) Logitech Unifying Device. Wireless PID:2016: (accel) acceleration profile 0
    (**) Logitech Unifying Device. Wireless PID:2016: (accel) acceleration factor: 2.000
    (**) Logitech Unifying Device. Wireless PID:2016: (accel) acceleration threshold: 4
    (II) config/udev: Adding input device PC Speaker (/dev/input/event3)
    (II) No input driver specified, ignoring this device.
    (II) This device may have been added with another device file.
    (II) config/udev: Adding input device HDA ATI SB Front Headphone (/dev/input/event4)
    (II) No input driver specified, ignoring this device.
    (II) This device may have been added with another device file.
    removing GPU device /sys/devices/pci0000:00/0000:00:02.0/0000:01:00.0/drm/card0 /dev/dri/card0
    (II) config/udev: Adding drm device (/dev/dri/card0)
    (II) xfree86: Adding drm device (/dev/dri/card0)
    (WW) Warning, couldn't open module modesetting
    (II) Unloading modesetting
    (EE) Failed to load module "modesetting" (module does not exist, 0)
    xf86: found device 0
    (II) config/udev: Adding input device HDA ATI SB Line Out Surround (/dev/input/event7)
    (II) No input driver specified, ignoring this device.
    (II) This device may have been added with another device file.
    (II) config/udev: Adding input device HDA ATI SB Line (/dev/input/event9)
    (II) No input driver specified, ignoring this device.
    (II) This device may have been added with another device file.
    (II) config/udev: Adding input device HDA ATI SB Rear Mic (/dev/input/event10)
    (II) No input driver specified, ignoring this device.
    (II) This device may have been added with another device file.
    (II) config/udev: Adding input device HDA ATI SB Line Out Front (/dev/input/event8)
    (II) No input driver specified, ignoring this device.
    (II) This device may have been added with another device file.
    (II) config/udev: Adding input device HDA ATI SB Front Mic (/dev/input/event11)
    (II) No input driver specified, ignoring this device.
    (II) This device may have been added with another device file.
    (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event15)
    (II) No input driver specified, ignoring this device.
    (II) This device may have been added with another device file.
    (II) config/udev: Adding input device HDA ATI SB Line Out Side (/dev/input/event5)
    (II) No input driver specified, ignoring this device.
    (II) This device may have been added with another device file.
    (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event17)
    (II) No input driver specified, ignoring this device.
    (II) This device may have been added with another device file.
    (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event16)
    (II) No input driver specified, ignoring this device.
    (II) This device may have been added with another device file.
    (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=9 (/dev/input/event14)
    (II) No input driver specified, ignoring this device.
    (II) This device may have been added with another device file.
    (II) config/udev: Adding input device HDA ATI SB Line Out CLFE (/dev/input/event6)
    (II) No input driver specified, ignoring this device.
    (II) This device may have been added with another device file.
    I have Mesa, Vesa, and the "nvidia" drivers installed.
    Last edited by kensclark16 (2014-04-05 19:19:25)

    Please edit your post and use code tags, like this:
    X.Org X Server 1.15.0
    Release Date: 2013-12-27
    X Protocol Version 11, Revision 0
    Build Operating System: Linux 3.12.5-1-ARCH x86_64
    Current Operating System: Linux SERN 3.13.8-1-ARCH #1 SMP PREEMPT Tue Apr 1 12:19:51 CEST 2014 x86_64
    Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=ae1186fc-165e-4d4d-949a-ccf939e3da53 rw quiet elevator=deadline
    Build Date: 09 January 2014 08:47:24AM
    Current version of pixman: 0.32.4
    Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    (==) Log file: "/var/log/Xorg.0.log", Time: Sat Apr 5 11:55:11 2014
    (==) Using config directory: "/etc/X11/xorg.conf.d"
    (==) No Layout section. Using the first Screen section.
    (==) No screen section available. Using defaults.
    (**) |-->Screen "Default Screen Section" (0)
    (**) | |-->Monitor "<default monitor>"
    (==) No monitor specified for screen "Default Screen Section".
    Using a default monitor configuration...
    This makes it A LOT easier to read.

  • Can't get Login Manager (xdm) to work

    I would like to boot directly into a login maqnager such as xdm or wdm. 
    I have read the wiki on "Adding a login manager" but can't get xdm to work.
    I have the following line in my /etc/inittab
    x:5:respawn:/usr/bin/xdm  -nodaemon
    I have the following in .xsession
    /bin/bash  --login -i ~/.xinitrc
    But I don't have a .xinitrc file.  That is probably the problem.
    I would like to boot into xdm and then after logging in go to xfce4. 
    What do I need to do?
    Rob

    Thanks.  That log does not show anything.  However, there is a log in /var/log/xdm-errors.log.  It shows:
    Cannot open config file.  Using builtin defaults.
    FreeFontPath:  FPE "/usr/sg=hare/fonts/misc" refcount is 2, should be 1: fixing.
    I also tried using wdm.  wdm does work.  But no matter what window managaer I choose, it always opens startxfce4.  Strange...
    But I am perplexed that I can't get xdm to work.  My setup is very simple.
    Here is my latest attempt:
    .xsession reads:
    /bin/bash --login -i ~/.xinitrc
    .xinitrc reads:
    /opt/xfce4/bin/startxfce4
    Any ideas?
    Rob

  • Archiso login-manager autologin

    Hi!
    I'm playing with archiso to create a custom .iso and i'm not able to autologin user in lightdm ,
    i've to enter username and password to enter the gnome session.
    I've added autologin entries in lightdm.conf,
    added the user to the autologin group
    and created .dmrc in /etc/skel with gnome session entry.
    Once installed the iso to the hd the autologin works as expected but it doesn't work in live. 
    any hint?

    lucazade wrote:at the moment i'm trying to startx without the login manager using .xinitrc
    but i'd like to keep lightdm also in the live session
    PolyBender wrote:Make sure that you've enabled the service using systemctl maybe?
    systemctl enable lightdm
    If you want to start X without the login manager, then I wouldn't enable it...
    Just leave it installed is enough.

  • Enter login manager and X respawn issue

    Wondering if anyone else has this. I have a login for myself and one for my wife and 'normal' people who don't want/know how to use a tiling WM and firefox-pentadacytl, and want to have a graphical login manager. SLiM caused too many hard crashes where I'd lose the keyboard. GDM and KDM have too much cruft and LXDM is even less stable. Enter looked good, but on logout from openbox (not ScrotWM), tty7 locks up and I'll get the "X respawning too fast: disabled for 5 minutes message" in my logs/tty1.
    With SLiM it looks like this is an auth. file and/or xorg.conf error from what I've read. I've been relying on X to auto-config and don't have an xorg.conf.
    Where do I want to start to work around this?
    I'll post my initab and Xorg logs in a second or two.
    Relevant inittab lines:
    # 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 -i -8 38400 tty1 linux
    c2:2345:respawn:/sbin/agetty -8 -s 38400 tty2 linux
    c3:2345:respawn:/sbin/agetty -8 -s 38400 tty3 linux
    c4:2345:respawn:/sbin/agetty -8 -s 38400 tty4 linux
    c5:2345:respawn:/sbin/agetty -8 -s 38400 tty5 linux
    c6:2345:respawn:/sbin/agetty -8 -s 38400 tty6 linux
    ca::ctrlaltdel:/sbin/shutdown -t3 -r now
    x:5:respawn:/usr/bin/enter >/dev/null 2>&1
    Xorg.0.log:
    Oct 23 15:53:35 thimkbrick init: Switching to runlevel: 5
    ...skipping...
    Oct 29 19:14:00 thimkbrick dhcpcd[621]: wlan0: leased 192.168.5.11 for infinity
    Oct 29 19:14:00 thimkbrick dhcpcd[621]: forked to background, child pid 645
    Oct 29 19:18:12 thimkbrick init: Switching to runlevel: 5
    Oct 29 19:18:12 thimkbrick enter: Starting X server. [...x7 more]
    Oct 29 19:18:12 thimkbrick init: Id "x" respawning too fast: disabled for 5 minutes
    Oct 29 19:18:12 thimkbrick enter: Starting X server.
    Oct 29 19:18:18 thimkbrick enter: Server timed out [...x8 more]
    Oct 29 19:18:23 thimkbrick enter: Logging in user
    Oct 29 19:23:13 thimkbrick enter: Starting X server. [...x8 more]
    Oct 29 19:23:13 thimkbrick init: Id "x" respawning too fast: disabled for 5 minutes
    Oct 29 19:23:13 thimkbrick enter: Starting X server.
    Oct 29 19:23:19 thimkbrick enter: Server timed out [...x8 more]
    Last edited by nathan28 (2011-10-29 23:28:56)

    Took another pass at the login manager thing again today. Just tried to re-install xorg-xkbcomp, to little apparent effect.
    Logging out of ScrotWM works. Logging into Openbox (via my other user's login) works. Attempting to log out of openbox, either with the r-click logout or with $ openbox --exit, drops me to an X root window and enter does not reappear without # killall X or #telinit 3 followed by #telinit 5.
    Is is possible that this is a result of the
    exec ck-launch-session dbus-launch --exit-with-session openbox-session
    line in the regular user .xinitrc? Otherwise I'm at a loss for ideas besides hacking the Enter code.
    Mostly giving up on this for now.
    Last edited by nathan28 (2011-12-26 19:04:48)

  • Gnome Login Manager??

    I have installed gnome extras and cant find the package with Login Manager. How do i changed themes and edit it so i dont have to enter password each time i log on? I have gnome-system-tools installed. Is there another package that contains the Login manager?

    The package is gdm. As for customizing, you may want to read this:
    http://wiki.archlinux.org/index.php/Gno … g_gdm_2.28

  • Setting monitor resolution in the login manager, before session launch

    Hey guys,
    I want to have SLiM set the resolution to "auto" once it boots. At the moment, it seems like it boots directly into 800x600, and not into my native resolution, 1366x768. Sometimes I have an external monitor connected as well, and it's a good deal larger.
    I was thinking it would be possible to run "xrandr --auto" which does this for me, but I am unable to see how exactly this is done through SLiM.
    If it becomes necessary, I'm willing to change login manager to something else. gdm, xdm, kdm, you name it.
    Thanks,
    gonX

    Are you using a /etc/X11/xorg.conf file?
    If not,  then you may want to try setting up a basic one with settings for your video card, monitor, and screen that includes the resolution that you want slim to use.
    Before XRandR, it was set up in the xorg.conf file.
    Though, now that I think about it, if it's an issue with size of the fonts, I think that you can adjust that in the slim theme.   I don't use slim or any login manager.
    I find that it's easier for me to log in via the console and startx manually.  That way if I break my X....      It's happened. 
    Anyway, HTH

  • Console TDM - A CDM-like login manager

    Inspired by CDM, I wrote a login manager called TDM. TDM is also written in pure bash, and it has a config tool tdmctl, whose usage is similar to systemctl.
    TDM has the following features:
      Use links or scripts to set up the X sessions
      Use tdminit file to configure TDM
      Use tdmexit file to autostart some X programs
      Can set the default session
      Can be used with xdm (yet it sucks ^_^)
      Dialog and text user interface
    If you're intrested, you can have a try. Console TDM is on AUR and wiki.
    Have fun!

    mytbk wrote:
    Dialog UI
    http://t-display-manager.googlecode.com … dialog.png
    Text UI
    http://t-display-manager.googlecode.com … m_text.png
    Please don't do that.
    Thank you
    All the best,
    -HG
    Last edited by HalosGhost (2013-05-02 10:25:25)

  • Minimalist LogIn Manager

    Hey!
    I'm a little bit tired of my text-login, so I think I will look after a new login-manager are there something others than GDM/KDM/XDM? I'll think it could be nice if it's in GTK - I'm using Xfce4.4

    Kris wrote:Where does the theme files lay?
    /usr/share/slim/themes - if you're still interested.
    BTW - a quick glance at slim's filelist would have told you that. There's a slim-themes package available, but it's also very easy to make your own.

  • Login manager neeeded for PAM to work properly?

    I just caught a comment on an AUR kernel package that warned that a login manager must be used in order for PAM to function. Can some on verify this? Is there a way to verify PAM is running properly? To clarify: I do not need a login manager and have been using startx. My only concern with PAM is the limits.conf is used correctly.
    EDIT: Ok I think I got this straight now. I was looking for the slim_pam package in aur, which has been deleted and replaced with slim-pam.
    Last edited by btartsa (2008-06-03 16:57:21)

    In article <[email protected]>,
    [email protected] says...
    > I have an MSI application that is set to FORCE CACHE as well as FORCE
    > RUN
    >
    > I'm using a MACRO to specify the UNC path for the files (common ->
    > sources as well as the transforms).
    >
    > I have two app objects (two copies, really). One in our main site,
    > another in a remote site.
    >
    > The GUIDs have been synced
    >
    > I setup the "site list" as per the docs (pointed "remote site app" to
    > the "main site app")
    >
    > I have my Novell Client 4.91 SP2 using IP Address costing =2 (ping
    > time).
    >
    > When I login as the "remote" user, it tries to cache the application.
    > Only 51 minutes remaining (should be 5 minutes as I'm on the "main" site
    > subnet and the ping should've responded the quickest from here).
    >
    > Am I doing something wrong?
    >
    I'm doing something wrong. I guess it only works with NON-Cached apps
    that are distributed.

  • Start X to Login Manager

    I found out using startx was deprecated so I wanted to look for a simple lm. I found lightdm which seems to work fine, but there seems to be some differences in startx vs a login manager. The login managers boot off of these xsession files which has the wm executable. I have awesome and dwm installed and the default .desktop files simply starts the vanilla wm without any configurations. I have two problems with this. One, my .xinitrc is never run. Is there a new place where I can put all my scripts? Two, my config's for wm's are completely ignored. How can I fix this? For now, I created a .desktop file that calls my .xinitrc directly. I don't think I'm doing that right...

    ewaller wrote:
    Hspasta wrote:I found out using startx was deprecated .
    Reference, please?
    I remember reading maybe on the irc or mailing list something about it. Idk, maybe I took it wrong.
    DSpider wrote:
    Post your ~/.xinitrc.
    You better not have stuff bellow the "exec wm" line in there.
    Also, why do you need a login manager for anyway? Using a tiling wm basically guarantees to keep away the common folk. Just use: https://wiki.archlinux.org/index.php/Start_X_at_Boot
    There is nothing under the "exec ..." line.

  • Power managament / Graphical Login Manager / ...

    Hi all,
    I'm new to arch, coming from ubuntu (which is a noob distro compared to this ).
    I have several questions:
    I'm running arch (with fluxbox)  on a laptop and I wanted to place a wmpower  thingy in my slit.
    Install was succesfull but when I ran the program, I got a message:
    Cpu frequency scaling is not available
    No power management subsystem detected
    wmpower: No power management support...
    I searched forums, installed acpi (pacman -s acpi ), put acpid in my daemon list but when I ran wmpower again cpu frequency is available but I still get this error.
    No power management subsystem detected
    wmpower: No power management support...
    What else should I install?
    Other question:
    How can I install a graphical login manager, and when I'm logged in,  fluxbox must start ( startx has to be executed automatically).
    Last question: Which file manager should I use, I find rox a bit simple imo, and konqueror is to much for me
    Thx in advance
    Greetz Daan

    Hi Daan,
    Please see the wiki page regarding SpeedStep: http://wiki.archlinux.org/index.php/SpeedStep
    There are links for AMD based systems on this page as well, but only the necessary modules differ from this explanation.
    Briefly: Load the correct modules (add them to the modules array in /etc/rc.conf) for your CPU and install (and add it to the daemon section in /etc/rc.conf) cpufreq/another daemon to administer frequency scaling.
    nice regards

  • Dependency free login manager?

    deleted
    Last edited by Misbah (2012-02-14 05:54:38)

    Misbah wrote:
    The only suggestion I've gotten so far is Slim, which looks nice, but I was wondering if there are any other relatively dependency-free login managers out there?
    Also just to make sure, I don't HAVE to use a login manager right? I can just log in vc1 and have startx run automatically after login right? A login manager would be nice though, to have graphical settings selections n stuff as opposed to knowing all the options and doing it textually. That's kind of why I was looking for an alternative to Slim as well, because you simply use different username logins to achieve different options, ie) shut down and stuff.
    There is also Enter its in AUR, but it's still very early devolopment. And you need to make the rc-script yourself. But it does work. More simple than SLiM but not faster.

Maybe you are looking for