KDE4 login manager is disabled [SOLVED]

I've updated two of my systems to KDE4.1 and both have the same problem: Login Manager is disabled (grayed out)
With that I cannot change any settings. Does anyone know how to fix this problem? 
R.
Last edited by ralvez (2008-07-30 23:00:25)

Peyton wrote:
It's possible to login as root, but it's disabled by default. You have to edit kdmrc to allow root login.
Try kdesu again. It didn't work for me the first time, either. Or, you could just use sudo for this.
OK. That did the trick!!
I enabled root log in and then I was able to customize the theme and get a whole lot of the other settings working.
Thank you!!
There are yet a number of other things that do not work but ... I got KDE to at least not look ugly.
Quanta, which I use on a daily basis does not work by default but one of the devs was nice enough to put a package build up, so that's fixed ... (sort of, when Quanta starts it complains that a bunch of plug-ins are missing... but the "key" components are running )
Thanks a lot for the help.
R.
Last edited by ralvez (2008-07-30 23:11:19)

Similar Messages

  • Gdm login manager background picture[SOLVED]

    Hello all,
    I use gnome and gdm. I am wondering how I can change the background image of gdm behind the login window so that I can set my wallpaper image of my desktop also as background image for gdm login. Right now, it is somehow strange to have this green default image behind the login window but my wallpaper pciture is really cool.
    Is there any way for proper configuration? I do not want to mess up with the normal configuration. I just want to know whether gdm itself supports this kind of feature.
    Thanks in advance.
    Last edited by Archie_Enthusiasm (2010-11-28 15:49:53)

    Archie_Enthusiasm wrote:
    Is there no other way to do this in gdm or gnome GUI? Is it really normal way to create a soft link for gnome-appearance-properties.desktop and then change the image? It seems like that changing that image was planned not to be supported and thus people found an unusual way to do this.
    Please consult me concerning this. At the moment, I am really happy with my system and do not want to touch the original system by doing things manually.
    Arch, and Linux in general, is about freeing you to be able to make whatever you want of your system. If you are looking for a "supported" method or a GUI, you can either live with the background image you have, or you can get your hands dirty and learn how your system works. It's your choice.

  • [SOLVED]Login manager in KDE 4.3 does not work!

    This is a fresh install (just two days old and installed KDEbase just yesterday), and almost everything is working like a charm the only glitch I have experienced till now is that the login manager module in System Settings is not working as it should be. When I click on its button I know that it should normally ask me for my password but it does not do that and therefore when it opens up all the settings are greyed out and thus unchangable . Is this a bug or am I missing something (Anyone else experienced this!)?
    Also, although not related to this topic, can somebody tell me where to find the setting for making windows shift to different workspace while dragging them through the edges of the screen. I'm sure I found this setting under Window Behavior>Window Behavior module in Kubuntu but it is nowhere to be found on the Arch KDE.
    Last edited by bhadotia (2012-02-16 00:49:32)

    bhadotia wrote:Also, although not related to this topic, can somebody tell me where to find the setting for making windows shift to different workspace while dragging them through the edges of the screen. I'm sure I found this setting under Window Behavior>Window Behavior module in Kubuntu but it is nowhere to be found on the Arch KDE.
    As nobody answered this question, I guess I'll just mark this thread as solved as even after a lot of search I'm unable to find the preference and so none of the arch users here know about it as well. I think that feature was kubuntu specific and as Arch ships vanilla KDE I think its useless trying to find it here.
    Anyways thanks for the help guys

  • Which login manager? [SOLVED]

    I have discovered that I was unable to startxfce4 as a user because I did not install a login manager yet. Would you reccomend xorg-xdm or sLim? Why?
    Last edited by Blake Gideon (2009-09-18 21:03:21)

    Blake Gideon wrote:
    Does root have an ~/.xinitrc?
    EDIT: I'm fine with just having console login.
    Please do not run a window manager as root. But to answer your question, root can have xinitrc too, yes. It's not there if you didn't create it manually...so just create it with any text editor you want.
    [edit] typos
    Last edited by Lich (2009-09-18 20:43:37)

  • [SOLVED] Shutdown not possible without login manager

    When I login using slim as user, everything is fine.
    Automatic login without slim changes the rights of my user.
    When dbus is active as a daemon in rc.conf, wicd works fine (without dbus wicd would not work), but only xfce4 log-out is avaiblable. Xfce4-Shutdown and -restart is inactive.
    I'm not using a login manager, but mingetty, see
    https://wiki.archlinux.org/index.php/Start_X_at_Boot
    (used slim, at that stage I didn't have these kind of problems).
    according to the wiki
    https://wiki.archlinux.org/index.php/Au … al_console
    https://wiki.archlinux.org/index.php/Au … al_console
      /etc/inittab
    id:3: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/mingetty --autologin hk 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
    My ~/.bash_profile
    if [[ -z $DISPLAY && $(tty) = /dev/tty1 ]]; then
    #startx &> /dev/null &
    exec ck-launch-session startxfce4
    #xinit /usr/bin/xfce4-session
    fi
    I have tried different commands in my ~.xinitrc, but no change of behaviour
    1. exec ck-launch-session dbus-launch startxfce4 (I read somewhere that ck must be started before dbus-launch)
    2. exec ck-launch-session startxfce4
    When dbus is inactive in the rc.conf daemon's session, wicd does not work, but I can shut down the computer.
    Last edited by mumpf (2012-02-13 18:27:21)

    it works now with the help of a debian thread, unfortunately in German
    http://debianforum.de/forum/viewtopic.php?f=2&t=131087
    three additional files in /etc/polkit-1/localauthority/50-local have to set up (exactly the way they are in the thread):
    etc/polkit-1/localauthority/50-local.d/org.freedesktop.consolekit.pkla
    etc/polkit-1/localauthority/50-local.d/org.freedesktop.udisks.pkla
    etc/polkit-1/localauthority/50-local.d/org.freedesktop.upower.pkla
    For Archlinux the group powerdev has to be replaced by power and users by storage
    in sudoers /usr/lib/xfce4/session/xfsm-shutdown-helper has to be removed.
    After a restart all should work (mount and restart works on my installation now).

  • 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.

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

  • Login manager doesn't restart

    Hi,
    At the end of my session the login manager (kdm) doesn't restart any more. It starts only when I digit "reboot" or "shutdown -P"
    Thanks

    Ok and here is the kdm.log entry
    X Window System Version 7.1.1
    Release Date: 12 May 2006
    X Protocol Version 11, Revision 0, Release 7.1.1
    Build Operating System: UNKNOWN
    Current Operating System: Linux t23 2.6.18-ck #1 SMP PREEMPT Sun Nov 5 18:54:10 GMT 2006 i686
    Build Date: 19 September 2006
    Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    Module Loader present
    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.1.log", Time: Wed Nov 8 23:52:10 2006
    (==) Using config file: "/etc/X11/xorg.conf"
    [10f] 320 x 200, 70Hz
    [112] 640 x 480, 60Hz, 72Hz, 75Hz, 85Hz, 100Hz
    [115] 800 x 600, 60Hz, 72Hz, 75Hz, 85Hz, 100Hz
    [118] 1024 x 768, 60Hz, 70Hz, 75Hz, 85Hz, 100Hz
    [11b] 1280 x 1024, 60Hz, 75Hz, 85Hz
    [11e] 640 x 400, 70Hz
    [124] 1600 x 1200, 60Hz, 75Hz, 85Hz
    [134] 320 x 240, 72Hz
    [13e] 1400 x 1050, 60Hz, 75Hz
    [144] 400 x 300, 72Hz
    [154] 512 x 384, 70Hz
    [175] 720 x 480, 75Hz
    [17f] 720 x 576, 75Hz
    (EE) SAVAGE(0): DRI isn't enabled
    (EE) AIGLX: DRI module not loaded
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
    > Ignoring extra symbols
    Errors from xkbcomp are not fatal to the X server
    QSettings: error creating /tmp/1281107925/.qt
    QSettings: failed to open file '/tmp/1281107925/.qt/qt_plugins_3.3rc'
    QSettings::sync: filename is null/empty
    QSettings: error creating /tmp/1281107925/.qt
    QSettings: failed to open file '/tmp/1281107925/.qt/qt_plugins_3.3rc'
    QSettings::sync: filename is null/empty
    QSettings: error creating /tmp/1281107925/.qt
    QSettings: failed to open file '/tmp/1281107925/.qt/qt_plugins_3.3rc'
    QSettings::sync: filename is null/empty
    Link points to "/var/tmp/kdecache-root"
    SetClientVersion: 0 9
    SetGrabKeysState - disabled
    AUDIT: Wed Nov 8 23:55:49 2006: 3047 X: client 12 rejected from local host
    AUDIT: Wed Nov 8 23:57:11 2006: 3047 X: client 12 rejected from local host
    SetGrabKeysState - enabled
    AUDIT: Thu Nov 9 00:14:24 2006: 3047 X: client 13 rejected from local host
    SetClientVersion: 0 9
    SetGrabKeysState - disabled
    SetGrabKeysState - enabled
    FreeFontPath: FPE "/usr/share/fonts/misc/" refcount is 2, should be 1; fixing.
    (EE) SAVAGE(0): DRI isn't enabled
    (EE) AIGLX: DRI module not loaded
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
    > Ignoring extra symbols
    Errors from xkbcomp are not fatal to the X server
    Backtrace:
    0: /usr/bin/X(xf86SigHandler+0x84) [0x80c4724]
    1: [0xb7fcf420]
    2: /usr/lib/xorg/modules/libramdac.so(xf86SetCursor+0x10b) [0xafa8f6eb]
    3: /usr/lib/xorg/modules/libramdac.so [0xafa8ed53]
    4: /usr/bin/X(miPointerUpdate+0x164) [0x81127e4]
    5: /usr/bin/X [0x81128f9]
    6: /usr/bin/X [0x8128d3e]
    7: /usr/bin/X [0x814e7a3]
    8: /usr/bin/X(DefineInitialRootWindow+0x11e) [0x808fdae]
    9: /usr/bin/X(main+0x454) [0x806ec04]
    10: /lib/libc.so.6(__libc_start_main+0xd8) [0xb7df5808]
    11: /usr/bin/X(FontFileCompleteXLFD+0xa5) [0x806df61]
    Fatal server error:
    Caught signal 11. Server aborting
    AUDIT: Thu Nov 9 00:26:08 2006: 2916 X: client 18 rejected from local host
    FreeFontPath: FPE "/usr/share/fonts/misc/" refcount is 2, should be 1; fixing.
    Fatal server error is interesting. I don't know what is the problem. I even prepared new xorg.conf again.
    Any ideas?

  • Can I uninstall KDE Login Manager, but keep the KDE Window Manager?

    I like the Window Manager n-workspaces with different wallpaper feature, but I hate the slow GUI Login Manager.
    Help.
    Last edited by knowNothing23 (2014-06-03 04:49:02)

    inittab is long gone, we're on systemd now. Seriously, search the wiki for login manager or display manager.
    You can't uninstall it, but you can easily disable it.

  • No 'system /administration /login manager" in Gnome

    With previous installs I always had login manager.
    so I tried to reinstall GDM and got this--
    warning: directory permissions differ on var/run/gdm/
    filesystem: 1775 package: 1777
    warning: directory permissions differ on var/log/gdm/
    filesystem: 1770 package: 755
    I ran gdmsetup as root and got "command not found"
    This is a new install and everything else is perfect.
    Can someone kindly tell me how to solve this please?
    Thanks

    See the "where is the gdm setup gone" thread, and the wiki page about changes in gnome 2.28.
    http://wiki.archlinux.org/index.php/Gnome_2.28_Changes
    http://bbs.archlinux.org/viewtopic.php?id=82089
    Last edited by Mr.Elendig (2009-10-13 11:45:32)

  • 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.

  • 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

  • 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

Maybe you are looking for

  • Insert or Update data from PROD dc to DEV DB

    We have one instance of a DB in PROD box and another in DEV box [unix] Requirement is to write a script to copy data from PROD to DEV for 10 related tables. Store Procedure will have input argument as Number or FromDt and To Date [date range] Can any

  • Photo sequence on the ipod touch

    Hello, I have a small problem with my new iPod touch. I will use him as electrical photo album, but unfortunately I can not determine under what criterion the iPod images sorted and where to set these criteria. .. If I upload pictures to the iPod the

  • Video Freeze on Version 1.1.  No Radio Function on 1.0

    I've been reading a lot of notice boards and i'm just getting more and more confused! I have just bought a 60GB video Ipod and am experiencing the common video freeze problem. Ok so i restore the Ipod back to Version 1.0 and videos dont freeze, probl

  • How to root Xperia TX on 4.1.2

    after updating to version 4.1.2, I lost root access, how do I recover them? Topic edited by Rickard

  • After login close the login window and open home page in new window

    Hi guys, I want to go to a new window for the "home page" without browser back button etc. after login validation. And also close the login window at the same time. Here is the code I used after the login validation. ExtendedRenderKitService erks =Se