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)

Similar Messages

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)

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

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.

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

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]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

I have Lion and Safari 5.7.1 and my privacy tab in preferences has no options. I'd like to manage cookies. What am I doing wrong?

I have Lion and Safari 5.7.1 and would like to manage cookies. My privacy tab in preferences has no options. What am I doing wrong?
Thanks

Uninstall SIMBL as follows.
Select Go ▹ Go to Folder… from the Finder menu bar, then enter the following text in the box that opens:
/Library
A folder will open. From that folder, delete the items listed below (some may be absent.) You may be prompted for your administrator login password.
Application Support/SIMBL
InputManagers/SIMBL.bundle
LaunchAgents/net.culater.SIMBL.Agent.plist
ScriptingAdditions/SIMBL.osax
Log out and log back in.
Make sure you never reinstall SIMBL. It’s likely to come bundled with another third-party system modfication that depends on it. If you want trouble-free computing, avoid software that makes miraculous changes to other software, especially built-in applications. The only real exception to that rule is Safari extensions, which are mostly safe, and are easy to get rid of when they don’t work. SIMBL and its dependents are not Safari extensions.

Logging into CLI from graphical login manager...possible?

Hey guys, this sounds like a backwards question, but hear me out.
I have two accounts on my computer. One of which is my main account, where do graphical design, sound editing, web surfing, and various LibreOffice tasks. This account, I want to boot straight into my standard Openbox account.
The other account, I'm planning to use solely for writing, and want to use it as a "no distractions, get stuff done," type account where I will just sit and write. I plan on using wordgrinder for word processing on this account, since that's as "no distractions" as they come. Thus, with my no distraction rule, I want to boot this account straight into commandline, and then from there, launch wordgrinder. At the very worst, if I'm going to use another program with this account, it would be mutt. However, I've already set up a GUI login manager.
Right now I'm using LXDM, and am wondering if there's a config I can write to have LXDM send me back out to the CLI after I login using this secondary account. If this is not possible, I have considered using a tiling window manager to emulate the CLI, but really have never used any, so I don't know which would be able to provide the feel of pure CLI without much hassle.
So preferably, what options out of these are available for what I want to do?
1) Create a config file for LXDM that can send me out to CLI.
2) Uninstall LXDM and use a command line-based display manager. (If so, which one?)
3) Use a tiling window manager. (If so, which one?)
4) Ditch the display manager altogether and just use startx when I want to use Openbox.
5) Other (Please state)

loafer wrote:Sorry if I've completely misunderstood but isn't Ctrl + Alt + F2 etc. an option?
It is, and I may have to settle for it (TBH, I hadn't even thought of that, when I had used it before, so thanks for reminding me of that.) However, having an out to go back into openbox anytime I want easily just by doing Ctrl+Alt+F1 may be an issue, but I guess every option I have has a flaw TBH. So C+A+F2 may be the best one. Thanks.

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.

HT1918 Would like to manage more than one iphone on my account

My son now has an iPhone and I would like to manage both accounts under my account. Please tell me how to set this up.

Welcome to the Apple Community.
Simply log into your account on his device.

Is there still a program like mindjet manager

Hello Comminity,
I'm looking for a program like Mindjet-Manager.In the windows Version it's able to send Ideas or Paths to
Outlook as a task with a reminder.
For Example:
I'm creating a mindmap with all my pets. I'm able to create e.g. "Dog" and put a note to it (maybe: "Feeding at 9 am).
After that i can use "Send to -> Microsoft Outlook at task". Then an outlook window opens where i can fill in a
remembering-time, other notes and so on.
What I'm now thinking of, is a mindmap program for apple, which works faultless with the notification center, iCal and tasks.
Is there still someone, who knows how to solve this problem ?

I don't know about Best Buy, Scott. iLife boxed set is no longer in production nor available for normal retail sale, so you'll have to call and ask them if they have any remaining in stock, although you could check the online site.
I don't know if you can reliably run two different versions of iLife, although I know you can install them.

I am currently managing 20 iPads on a macbook. I would like to manage the same 20 iPads on a new macbook pro. I have logged into the iTunes account on the new machine and see our apps but not the devices. How do i get the devices to be shown on new comp?

I am currently managing 20 iPads on a macbook. I would like to manage the same 20 iPads on a new macbook pro. I have logged into the iTunes account on the new machine and see our apps but not the devices. How do i get the devices to be shown on new comp?

Has anyone used apple cpnfigurator for this purpose?

Console TDM - A CDM-like login manager

Similar Messages

Maybe you are looking for