[SOLVED]Slim and gdm questions

Hi all,
I just installed slim cause I wanted to try something new and faster than gdm login manager for gnome, I have it working right now but with a few hiccups:
1- I login using slim, but after I am logged in the system if I lock the screen, the gdm login shows (instead of the slim one)
2- System bootup is a LOT slower, after I login the system stays with just the background for a few seconds, then loads the desktop.
So, here are my questions:
a) If I remove gdm will I have this same issues? maybe the increased boot time is because I have 2 login managers installed?
b) I disabled the gdm daemon from rc.conf (put a ! before it), should I remove it from there completely? because apparently it is still loading.
Also I dont know much about login managers so I wanted a little enlightenment in this matter.
regards and thanks in advance
Last edited by 655321 (2010-06-13 20:57:35)

BKLive
Here is the info:
slim.conf
# Path, X server and arguments (if needed)
# Note: -xauth $authfile is automatically appended
default_path        ./:/bin:/usr/bin:/usr/local/bin
default_xserver     /usr/bin/X
xserver_arguments   -nolisten tcp vt07
# Commands for halt, login, etc.
halt_cmd            /sbin/shutdown -h now
reboot_cmd          /sbin/shutdown -r now
console_cmd         /usr/bin/xterm -C -fg white -bg black +sb -T "Console login" -e /bin/sh -c "/bin/cat /etc/issue; exec /bin/login"
#suspend_cmd        /usr/sbin/suspend
# Full path to the xauth binary
xauth_path         /usr/bin/xauth
# Xauth file for server
authfile           /var/run/slim.auth
# Activate numlock when slim starts. Valid values: on|off
# numlock             on
# Hide the mouse cursor (note: does not work with some WMs).
# Valid values: true|false
# hidecursor          false
# This command is executed after a succesful login.
# you can place the %session and %theme variables
# to handle launching of specific commands in .xinitrc
# depending of chosen session and slim theme
# NOTE: if your system does not have bash you need
# to adjust the command according to your preferred shell,
# i.e. for freebsd use:
# login_cmd           exec /bin/sh - ~/.xinitrc %session
login_cmd           exec /bin/bash -login ~/.xinitrc %session
# Commands executed when starting and exiting a session.
# They can be used for registering a X11 session with
# sessreg. You can use the %user variable
# sessionstart_cmd    some command
# sessionstop_cmd    some command
# Start in daemon mode. Valid values: yes | no
# Note that this can be overriden by the command line
# options "-d" and "-nodaemon"
# daemon    yes
# Available sessions (first one is the default).
# The current chosen session name is replaced in the login_cmd
# above, so your login command can handle different sessions.
# see the xinitrc.sample file shipped with slim sources
sessions            xfce4,icewm,wmaker,blackbox
# Executed when pressing F11 (requires imagemagick)
screenshot_cmd      import -window root /slim.png
# welcome message. Available variables: %host, %domain
welcome_msg         Welcome to %host
# Session message. Prepended to the session name when pressing F1
# session_msg         Session:
# shutdown / reboot messages
shutdown_msg       The system is halting...
reboot_msg         The system is rebooting...
# default user, leave blank or remove this line
# for avoid pre-loading the username.
#default_user        simone
# Focus the password field on start when default_user is set
# Set to "yes" to enable this feature
#focus_password      no
# Automatically login the default user (without entering
# the password. Set to "yes" to enable this feature
#auto_login          no
# current theme, use comma separated list to specify a set to
# randomly choose from
#current_theme       default
current_theme        archlinux-darch-white
# Lock file
lockfile            /var/lock/slim.lock
# Log file
logfile             /var/log/slim.log
~/.xinitrc:
#!/bin/sh
# ~/.xinitrc
# Executed by startx (run your window manager from here)
# exec gnome-session
# exec startkde
# exec startxfce4
# ...or the Window Manager of your choice
#exec xterm
setxkbmap -option terminate:ctrl_alt_bksp
exec ck-launch-session gnome-session
Regarding whats runs at bootup, I guess you want to see my daemons array in rc.conf, here it is:
DAEMONS=(syslog-ng dbus hal network netfs crond alsa @cups slim !gdm)
Notice gdm is disabled.
Also, would you advice to reinstall gdm? removing it didnt do anything for the problem im experiencing.
thanks for the help

Similar Messages

  • [SOLVED]SliM and .xinitrc

    Hey guys me again
    Ive just installed Slim. and changed my rc.conf putting slim in the correct area, slim boots up fine. and then when i login it says that it failed to load session. so i checked my ~/.xinitrc
    exec ck-launch-session dbus-launch openbox-session
    and it all seems proper. so im not sure what im missing
    Last edited by nankura (2012-04-28 03:41:38)

    adamrehard wrote:It looks good to me too. Hmmm.
    Do you need to use consolekit and dbus?
    Have you tried it using just startx or xinit?
    Is .xinitrc executable?
    That's all I've got. Hope it helps.
    Problem solved. i was missing xorg-xinit from the repos. pacman installation fixed the issue and XAUTH
    Last edited by nankura (2012-04-28 03:41:25)

  • [solved]Slim and new consolekit

    Hey all. Just wondering if the the newest version of Slim that came out on January 31st, Slim 1.3.2.-3, works completely fine now with the newest version of consolekit?
    EDIT:
    Just installed slim again and everything seems to be fixed. Working with consolekit again!
    Last edited by orlfman (2011-02-03 05:02:17)

    Using Slim and LXDE. Suspend and hibernate from lxde-logout didn't work and an unpriviledged account I created coudn't access mixer device or mount removable drives without being added to the 'audio' and 'storage' groups after the initial upgrade to new consolekit. But after the very latest upgrades of packages 'slim' and 'consolekit' everything is AFAIK back to working just as before. Unless I stumble over something new I'd say stuff are just OK as of today.
    (Remember to merge any /etc/pam.d/login.pacnew to /etc/pam.d/login. Threads suggests that those that forgot got real problems.)

  • Alternative to slim and gdm?

    Hello
    I'm looking for an alternative to gdm and slim, the issue is that slim is to simple, if I log out of the xserver session I'm just getting thrown out to the terminal and the classic login screen, while gdm gets to big and bloated and gnomish.
    Are there any alternatives at all?

    B wrote:Using inittab instead of putting it in your DAEMONS=() array is the most versatile solution. Rc.conf is executed no matter whether you boot in runlevel 3 or 5, and there's no difference between it. Inittab, on the other hand, can deal with the different runlevels, so if you actually decide to boot into runlevel 3, it will not start your login manager (and X).
    OTOH it's slightly slower via inittab on boot. 5-10 seconds.

  • [SOLVED] Gnome and gdm is not themed after reinstall

    Hi all.
    I messed up my Arch install yesterday, so today I reinstalled my system. I normally use Gnome, so I installed everything I normally install. (only things not installed from group gnome is epiphany and gnome-termial, as I use lxterminal instead)
    But as I reboot into GDM I find myself surprised: normally GDM will display the green leaf background on me, and after I log in this will be the desktop background. However, this is not the case now. GDM presents a plain black background, and what's more, when I try to change the background in gnome-appearance-preferences, the background image does not change! The only changes I get are the background colors belonging to each background. What has happened since the last time I installed??
    Thank you for any help
    EDIT: Seems a missing HAL was the problem. Even though GDM no longer depends on HAL, installing HAL and adding it to DAEMONS in rc.conf solved everything for me.
    Last edited by mariusmeyer (2010-11-09 06:05:29)

    Problem solved. I took gdm out of rc.conf, and uncommented it in in /etc/inittab. Then reinstalled glib2. After that it worked like a charm. Some warning message about wicd not starting D-Bus something, but I can deal with that later. Now typing in Chromium instead of elinks. Mission accomplished. Thanks community!

  • [SOLVED]OSS4 and lib32 question

    Well... I'm thinking about installing arch64 on my new notebook with some lib32 packages and in the wiki I noticed the for sound in 32bit application is needed lib32-alsa. In case I use oss4 is there something else needed for using sound in 32 bit applications?
    Also a quiestion: I noticed that if arch=i686 the oss-linux-free package compiles libflashsupport.so and puts it in /usr/lib/. Will I have sound in flashplugin wiht oss4 if that step is not complited.
    The PKGBUILD:
    pkgname=oss-linux-free
    pkgver=4.0_1016
    pkgrel=1
    _realname=oss-v4.0-build1016-src-gpl
    pkgdesc="OSS/Open source driver"
    arch=('i686' 'x86_64')
    url="http://www.opensound.com/"
    license=('GPL2')
    depends=('gcc' 'make' 'gtk2' 'libtool' 'bc' 'sed')
    makedepends=('gawk' 'pkgconfig')
    conflicts=('oss-linux')
    provides=('oss')
    install=oss.install
    source=(rc.oss-linux-free http://www.4front-tech.com/developer/sources/stable/gpl/$_realname.tar.bz2)
    md5sums=('f343bb70a4dbd1aabefabbea0f76e886'
    'b8c3409b477387dbe87118caf46773ed')
    build() {
    rm -rf build ; mkdir build ; cd build
    sed -i "s|export HAVE_ALSA=1|# export HAVE_ALSA=1|g" $srcdir/$_realname/configure
    sed -i "s|700|755|g" $srcdir/$_realname/setup/Linux/build.sh
    unset CFLAGS
    $srcdir/$_realname/configure || return 1
    make build || return 1
    cp -r prototype/{etc,usr} $pkgdir/
    install -Dm755 ../rc.oss-linux-free $pkgdir/etc/rc.d/oss-linux-free
    if [ `uname -m` == "i686" ]; then
    cd setup/Linux/oss/lib
    gcc -m32 -shared -fPIC -O2 -Wall -Werror -lssl flashsupport.c -o libflashsupport.so || return 1
    cp libflashsupport.so $pkgdir/usr/lib/oss/lib/
    fi
    NVM I sticked to the chroot approach and I have no trouble with oss4 audio output.
    Last edited by Dheart (2008-07-16 10:13:13)

    Yes, I have PHP5.2.5 and Apache 2.2
    But I have solved the problem. It was with windows. Under windows explorer --> tools --> Folder Options --> view tab. Uncheck the Hide extensions for known file types. This fixed my problem
    Thank you all for taking time to help me.
    Thank you very much
    Message was edited by:
    pransuj

  • [Solved] installation and setup question - gummiboot and EFI

    Hi,
    This is the first time i'm installing arch. i hit the below issues. hope someone can help me out. my understanding of uefi is just about an hour worth of reading or less..
    (the wiki didn't mention the kernel requirement when I started installing it... now it does and i updated the beginner's guide wiki post.)
    Problem
    Gummiboot#Installing says that "If you are still running kernel 3.7 or have not booted in EFI mode, creating the boot entry will fail. You should however still be able to boot gummiboot as it copies the binary to the default EFI binary location on your ESP (/boot/EFI/BOOT/BOOTX64.EFI on x64 systems). "
    the gummiboot part fails. gummiboot gives this error at install  saying file system is not FAT EFI, so first I got gummiboot and gummiboot-efi both using pacman. then, I provided the --path to install and now it coughs up because the latest iso isn't 3.8 yet.
    Failed to access EFI variables. Is the "efivarfs" filesystem mounted?
    I can see efivars but this is asking for efivarfs.
    so instead I did,
    # cp /usr/lib/gummiboot/gummibootx64.efi /boot/efi/EFI/gummiboot/gummiboot.efi
    # efibootmgr -c -d /dev/sda -p 1 -w -L "Gummiboot" -l '\EFI\gummiboot\gummiboot.efi'
    how do I set this up? I'm afraid if I overwrite /boot/efi/EFI/BOOT/BOOTX64.EFI  windows might not boot.
    after the installation (of course without gummiboot stuff) now when I reboot, I don't see any gummiboot menu at all because i didn't copy it to EFI/BOOT. it goes straight to windows 8 boot. during boot if I press F12 and see the menu option on thinkpad, I see gummiboot as the first entry(must be because of efibootmgr) followed by windows boot manager. When I select the gummiboot and enter, it just circles back to the same menu. I have setup the loader.conf and arch.conf as described in the wiki.
    how do I set gummiboot to work? i dont mind pressing F12 and then going to gumiboot-> arch until 3.8 is out.
    If this isn't possible, can I install rEFInd without messing gummiboot? looking at the dir structure of FAT EFI I think it should be possible but not 100% sure until i try it out. Also, to get rid of gummiboot, i should delete the directories, uninstall using pacman and get rid of the efibootmgr change I made, right?
    Last edited by lobo2 (2013-03-15 04:07:47)

    srs5694 wrote:
    sidneyk wrote:Maybe not, I use rEFInd and mount ESP on /boot/efi and copy over updated kernels and initramfs. Maybe if you are mounting ESP at /boot the kernel and initramfs get written to both places at once, I don't know. I also don't know if /boot is where gummiboot expects them to be.
    I realize this has been at least partially addressed by others, but I want to make two points very explicit:
    In Linux, partitions (or more precisely, the filesystems that most of them contain) are accessed by mounting them at a mount point (a directory). Thus, when you mount the ESP at /boot, the contents of /boot are the ESP. Put another way, mounting the ESP at /boot means that to read or write the ESP, you read or write files and directories under /boot. You can test this yourself by mounting and unmounting a partition that's not basic to the minute-to-minute functioning of the computer. The ESP will actually work fine for this. Unmount it from /boot or /boot/efi and then issue a mount command to mount it elsewhere (say, "mount /dev/sda1 /mnt"). Then check the files under your temporary mount point, and even copy a file there. You can then unmount it and mount it back where you normally do and look for the file you copied -- it should be there. Play with this until you fully grok it.
    Gummiboot runs before Linux, and it has no conception of Linux mount points. Thus, whether you mount the ESP at /boot, at /boot/efi, at /home/fred/abadmountpointforanesp is irrelevant, so long as the files on the ESP are laid out in the way that gummiboot expects. The trickiest aspect of this for those unfamiliar with the Linux mount system is that you do not include the Linux mount point in filename references for pre-boot programs like gummiboot. That is, if you mount the ESP at /boot and place the kernel at /boot/vmlinuz, then in gummiboot, the kernel would be \vmlinuz.
    Yeah, I figured this out based on the OP's response to that and thinking it through, I just never really thought about it much before now. But I will argue that the mount point /boot and the EFI partition are indeed 2 different locations. I know that once the ESP is mounted at /boot that this distinction disappears until it is umounted and something written to /boot, but while mounted as such, /boot and ESP are virtually the same, at least to the Linux system. I realize the EFI programs are ran before any OS and therefore don't really care about any OS specifics.
    I wonder if the OP has confused the info between gummiboot and rEFInd (possibly from the Beginners Guide) because to me, after reading the gummiboot wiki, it just seems that it would be much simpler to just give gummiboot what it wants, i.e. ESP mounted at /boot, whether it's a separate partion or not. I'll have to take a look again at the Beginners Guide to see again the order of things there, but if it isn't, maybe it should be having the user ensure that pacman has completely updated the new system and then go on to the boot loader specifics. I was just thinking though, that the way the install medium is now, that it was automatically pulling the latest stuff down as part of the install process. I know it's not pulling testing or multilib without user intervention, but the core, stable stuff it is. That seems to be part of the confusion here maybe, 2 different versions of gummiboot with gummiboot changing some things between the 2 and maybe the kernels, too.
    [EDIT] I took another look at the Beginner's Guide and it says that most users will probably want to use the [core], [extra], and [community] repos, which are enabled by default. It goes on to recommend that [multilib] be enabled for users wanting to run 32 bit programs and then reminds you to run #pacman -Sy to update the package lists, but not #pacman -Syu which would apply any changes from the repos since starting the install. Shouldn't matter much, even if the [multilib] repo was enabled because at that point no 32 bit libs have been installed, but it would matter if a user decided to enable the testing repos.
    I wouldn't ordinarily recommend it, but in this case, if the OP is comfortable with the risk, then it might be useful to, at least temporarily, enable the [testing] repo and do #pacman -Syu to pull in the 3.8 kernel. Note that this is likely to also pull in other packages from [testing], but if you haven't installed X yet or any desktop environment, then what is pulled in shouldn't be too overwhelming. He can then immediately go back and disable [testing] if desired. I'm currently using testing without any issues, but there are risks to doing so.
    Last edited by sidneyk (2013-03-14 18:13:43)

  • [SOLVED] GNOME3: gnome-session and GDM won't start

    Whoops, had to -Syu.
    I'm trying to start GNOME3 in two ways,
    1) exec ck-launch-session dbus-launch gnome-session in .xinitrc
    2) Through GDM (/etc/rc.d/gdm start)
    When I try to startx I get this error
    gnome-session: symbol lookup error: /usr/lib/gio/modules/libdconfsettings.so: undefined symbol: g_main_context_invoke
    When I try to use GDM I get a number of these lines
    gdm-binary[5891]: WARNING: GdmDisplay: display lasted 1.784000 seconds
    and
    gdm-binary[5891]: WARNING: GdmLocalDisplayFactory: maximum number of X display failures reached: check X server log for errors
    Xorg.0.log:
    [ 21116.638]
    This is a pre-release version of the X server from The X.Org Foundation.
    It is not supported in any way.
    Bugs may be filed in the bugzilla at http://bugs.freedesktop.org/.
    Select the "xorg" product for bugs you find in this release.
    Before reporting bugs in pre-release versions please check the
    latest version in the X.Org Foundation git repository.
    See http://wiki.x.org/wiki/GitPage for git access instructions.
    [ 21116.638]
    X.Org X Server 1.9.4.901 (1.9.5 RC 1)
    Release Date: 2011-03-04
    [ 21116.638] X Protocol Version 11, Revision 0
    [ 21116.638] Build Operating System: Linux 2.6.37-ARCH x86_64
    [ 21116.638] Current Operating System: Linux zhuangzi 2.6.37-ARCH #1 SMP PREEMPT Fri Mar 25 15:10:00 CET 2011 x86_64
    [ 21116.638] Kernel command line: root=/dev/disk/by-uuid/61d7dd62-c596-4158-8338-4d542869d305 ro vga=795
    [ 21116.638] Build Date: 14 March 2011 10:38:06AM
    [ 21116.638]
    [ 21116.638] Current version of pixman: 0.20.2
    [ 21116.638] Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    [ 21116.638] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 21116.638] (==) Log file: "/var/log/Xorg.0.log", Time: Fri Apr 8 18:49:52 2011
    [ 21116.638] (==) Using config file: "/etc/X11/xorg.conf"
    [ 21116.638] (==) Using config directory: "/etc/X11/xorg.conf.d"
    [ 21116.638] (==) ServerLayout "Layout0"
    [ 21116.638] (**) |-->Screen "Screen0" (0)
    [ 21116.638] (**) | |-->Monitor "Monitor0"
    [ 21116.639] (**) | |-->Device "Device0"
    [ 21116.639] (**) |-->Input Device "Keyboard0"
    [ 21116.639] (**) |-->Input Device "Mouse0"
    [ 21116.639] (**) Option "Xinerama" "0"
    [ 21116.639] (==) Automatically adding devices
    [ 21116.639] (==) Automatically enabling devices
    [ 21116.639] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
    [ 21116.639] Entry deleted from font path.
    [ 21116.639] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
    [ 21116.639] Entry deleted from font path.
    [ 21116.639] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
    [ 21116.639] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
    [ 21116.639] Entry deleted from font path.
    [ 21116.639] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
    [ 21116.639] (==) FontPath set to:
    /usr/share/fonts/misc/,
    /usr/share/fonts/TTF/,
    /usr/share/fonts/Type1/
    [ 21116.639] (==) ModulePath set to "/usr/lib/xorg/modules"
    [ 21116.639] (WW) AllowEmptyInput is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
    [ 21116.639] (WW) Disabling Keyboard0
    [ 21116.639] (WW) Disabling Mouse0
    [ 21116.639] (II) Loader magic: 0x7d42e0
    [ 21116.639] (II) Module ABI versions:
    [ 21116.639] X.Org ANSI C Emulation: 0.4
    [ 21116.639] X.Org Video Driver: 8.0
    [ 21116.639] X.Org XInput driver : 11.0
    [ 21116.639] X.Org Server Extension : 4.0
    [ 21116.640] (--) PCI:*(0:2:0:0) 10de:0402:1462:0910 rev 161, Mem @ 0xdf000000/16777216, 0xc0000000/268435456, 0xdc000000/33554432, I/O @ 0x0000ec00/128, BIOS @ 0x????????/131072
    [ 21116.640] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
    [ 21116.640] (II) LoadModule: "extmod"
    [ 21116.640] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
    [ 21116.640] (II) Module extmod: vendor="X.Org Foundation"
    [ 21116.640] compiled for 1.9.4.901, module version = 1.0.0
    [ 21116.640] Module class: X.Org Server Extension
    [ 21116.640] ABI class: X.Org Server Extension, version 4.0
    [ 21116.640] (II) Loading extension MIT-SCREEN-SAVER
    [ 21116.640] (II) Loading extension XFree86-VidModeExtension
    [ 21116.640] (II) Loading extension XFree86-DGA
    [ 21116.640] (II) Loading extension DPMS
    [ 21116.640] (II) Loading extension XVideo
    [ 21116.640] (II) Loading extension XVideo-MotionCompensation
    [ 21116.640] (II) Loading extension X-Resource
    [ 21116.640] (II) LoadModule: "dbe"
    [ 21116.641] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
    [ 21116.641] (II) Module dbe: vendor="X.Org Foundation"
    [ 21116.641] compiled for 1.9.4.901, module version = 1.0.0
    [ 21116.641] Module class: X.Org Server Extension
    [ 21116.641] ABI class: X.Org Server Extension, version 4.0
    [ 21116.641] (II) Loading extension DOUBLE-BUFFER
    [ 21116.641] (II) LoadModule: "glx"
    [ 21116.641] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    [ 21116.657] (II) Module glx: vendor="NVIDIA Corporation"
    [ 21116.657] compiled for 4.0.2, module version = 1.0.0
    [ 21116.657] Module class: X.Org Server Extension
    [ 21116.657] (II) NVIDIA GLX Module 270.30 Fri Feb 25 14:51:13 PST 2011
    [ 21116.657] (II) Loading extension GLX
    [ 21116.657] (II) LoadModule: "record"
    [ 21116.658] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so
    [ 21116.658] (II) Module record: vendor="X.Org Foundation"
    [ 21116.658] compiled for 1.9.4.901, module version = 1.13.0
    [ 21116.658] Module class: X.Org Server Extension
    [ 21116.658] ABI class: X.Org Server Extension, version 4.0
    [ 21116.658] (II) Loading extension RECORD
    [ 21116.658] (II) LoadModule: "dri"
    [ 21116.658] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
    [ 21116.658] (II) Module dri: vendor="X.Org Foundation"
    [ 21116.658] compiled for 1.9.4.901, module version = 1.0.0
    [ 21116.658] ABI class: X.Org Server Extension, version 4.0
    [ 21116.658] (II) Loading extension XFree86-DRI
    [ 21116.658] (II) LoadModule: "dri2"
    [ 21116.658] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
    [ 21116.659] (II) Module dri2: vendor="X.Org Foundation"
    [ 21116.659] compiled for 1.9.4.901, module version = 1.2.0
    [ 21116.659] ABI class: X.Org Server Extension, version 4.0
    [ 21116.659] (II) Loading extension DRI2
    [ 21116.659] (II) LoadModule: "nvidia"
    [ 21116.659] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
    [ 21116.659] (II) Module nvidia: vendor="NVIDIA Corporation"
    [ 21116.659] compiled for 4.0.2, module version = 1.0.0
    [ 21116.659] Module class: X.Org Video Driver
    [ 21116.660] (II) NVIDIA dlloader X Driver 270.30 Fri Feb 25 14:36:22 PST 2011
    [ 21116.660] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
    [ 21116.660] (++) using VT number 7
    [ 21116.678] (II) Loading sub module "fb"
    [ 21116.678] (II) LoadModule: "fb"
    [ 21116.679] (II) Loading /usr/lib/xorg/modules/libfb.so
    [ 21116.679] (II) Module fb: vendor="X.Org Foundation"
    [ 21116.679] compiled for 1.9.4.901, module version = 1.0.0
    [ 21116.679] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 21116.679] (II) Loading sub module "wfb"
    [ 21116.679] (II) LoadModule: "wfb"
    [ 21116.679] (II) Loading /usr/lib/xorg/modules/libwfb.so
    [ 21116.679] (II) Module wfb: vendor="X.Org Foundation"
    [ 21116.679] compiled for 1.9.4.901, module version = 1.0.0
    [ 21116.679] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 21116.679] (II) Loading sub module "ramdac"
    [ 21116.679] (II) LoadModule: "ramdac"
    [ 21116.679] (II) Module "ramdac" already built-in
    [ 21116.679] (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
    [ 21116.680] (==) NVIDIA(0): RGB weight 888
    [ 21116.680] (==) NVIDIA(0): Default visual is TrueColor
    [ 21116.680] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
    [ 21116.680] (**) NVIDIA(0): Option "TwinView" "0"
    [ 21116.680] (**) NVIDIA(0): Option "MetaModes" "1280x1024_75 +0+0"
    [ 21116.680] (**) NVIDIA(0): Option "TwinViewXineramaInfoOrder" "CRT-0"
    [ 21117.280] (WW) NVIDIA(GPU-0): The EDID read for display device CRT-0 is invalid:
    [ 21117.280] (WW) NVIDIA(GPU-0): unrecognized EDID Header.
    [ 21117.283] (II) NVIDIA(0): NVIDIA GPU GeForce 8600 GT (G84) at PCI:2:0:0 (GPU-0)
    [ 21117.283] (--) NVIDIA(0): Memory: 524288 kBytes
    [ 21117.283] (--) NVIDIA(0): VideoBIOS: 60.84.49.00.00
    [ 21117.283] (II) NVIDIA(0): Detected PCI Express Link width: 8X
    [ 21117.283] (--) NVIDIA(0): Interlaced video modes are supported on this GPU
    [ 21117.283] (--) NVIDIA(0): Connected display device(s) on GeForce 8600 GT at PCI:2:0:0
    [ 21117.283] (--) NVIDIA(0): CRT-0
    [ 21117.283] (--) NVIDIA(0): CRT-0: 400.0 MHz maximum pixel clock
    [ 21117.393] (II) NVIDIA(0): Assigned Display Device: CRT-0
    [ 21117.393] (II) NVIDIA(0): Validated modes:
    [ 21117.393] (II) NVIDIA(0): "1280x1024_75+0+0"
    [ 21117.393] (II) NVIDIA(0): Virtual screen size determined to be 1280 x 1024
    [ 21117.414] (WW) NVIDIA(0): Unable to get display device CRT-0's EDID; cannot compute DPI
    [ 21117.414] (WW) NVIDIA(0): from CRT-0's EDID.
    [ 21117.414] (==) NVIDIA(0): DPI set to (75, 75); computed from built-in default
    [ 21117.414] (--) Depth 24 pixmap format is 32 bpp
    [ 21117.415] (II) NVIDIA: Using 768.00 MB of virtual memory for indirect memory access.
    [ 21117.420] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
    [ 21117.420] (II) NVIDIA(0): may not be running or the "AcpidSocketPath" X
    [ 21117.420] (II) NVIDIA(0): configuration option may not be set correctly. When the
    [ 21117.420] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
    [ 21117.420] (II) NVIDIA(0): try to use it to receive ACPI event notifications. For
    [ 21117.420] (II) NVIDIA(0): details, please see the "ConnectToAcpid" and
    [ 21117.420] (II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
    [ 21117.420] (II) NVIDIA(0): Config Options in the README.
    [ 21117.422] (II) NVIDIA(0): Setting mode "1280x1024_75+0+0"
    [ 21117.461] (II) Loading extension NV-GLX
    [ 21117.491] (==) NVIDIA(0): Disabling shared memory pixmaps
    [ 21117.491] (==) NVIDIA(0): Backing store disabled
    [ 21117.491] (==) NVIDIA(0): Silken mouse enabled
    [ 21117.492] (**) NVIDIA(0): DPMS enabled
    [ 21117.492] (II) Loading extension NV-CONTROL
    [ 21117.493] (II) Loading extension XINERAMA
    [ 21117.493] (II) Loading sub module "dri2"
    [ 21117.493] (II) LoadModule: "dri2"
    [ 21117.493] (II) Reloading /usr/lib/xorg/modules/extensions/libdri2.so
    [ 21117.493] (II) NVIDIA(0): [DRI2] Setup complete
    [ 21117.493] (==) RandR enabled
    [ 21117.493] (II) Initializing built-in extension Generic Event Extension
    [ 21117.493] (II) Initializing built-in extension SHAPE
    [ 21117.493] (II) Initializing built-in extension MIT-SHM
    [ 21117.493] (II) Initializing built-in extension XInputExtension
    [ 21117.493] (II) Initializing built-in extension XTEST
    [ 21117.493] (II) Initializing built-in extension BIG-REQUESTS
    [ 21117.493] (II) Initializing built-in extension SYNC
    [ 21117.493] (II) Initializing built-in extension XKEYBOARD
    [ 21117.493] (II) Initializing built-in extension XC-MISC
    [ 21117.493] (II) Initializing built-in extension SECURITY
    [ 21117.493] (II) Initializing built-in extension XINERAMA
    [ 21117.493] (II) Initializing built-in extension XFIXES
    [ 21117.493] (II) Initializing built-in extension RENDER
    [ 21117.493] (II) Initializing built-in extension RANDR
    [ 21117.493] (II) Initializing built-in extension COMPOSITE
    [ 21117.493] (II) Initializing built-in extension DAMAGE
    [ 21117.496] (II) Initializing extension GLX
    [ 21117.589] (II) config/udev: Adding input device Power Button (/dev/input/event3)
    [ 21117.589] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 21117.589] (II) LoadModule: "evdev"
    [ 21117.589] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [ 21117.589] (II) Module evdev: vendor="X.Org Foundation"
    [ 21117.589] compiled for 1.9.4, module version = 2.6.0
    [ 21117.589] Module class: X.Org XInput Driver
    [ 21117.589] ABI class: X.Org XInput driver, version 11.0
    [ 21117.589] (**) Power Button: always reports core events
    [ 21117.589] (**) Power Button: Device: "/dev/input/event3"
    [ 21117.604] (--) Power Button: Found keys
    [ 21117.604] (II) Power Button: Configuring as keyboard
    [ 21117.604] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD)
    [ 21117.604] (**) Option "xkb_rules" "evdev"
    [ 21117.604] (**) Option "xkb_model" "evdev"
    [ 21117.604] (**) Option "xkb_layout" "us"
    [ 21117.646] (II) config/udev: Adding input device Power Button (/dev/input/event2)
    [ 21117.646] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 21117.646] (**) Power Button: always reports core events
    [ 21117.646] (**) Power Button: Device: "/dev/input/event2"
    [ 21117.657] (--) Power Button: Found keys
    [ 21117.657] (II) Power Button: Configuring as keyboard
    [ 21117.657] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD)
    [ 21117.658] (**) Option "xkb_rules" "evdev"
    [ 21117.658] (**) Option "xkb_model" "evdev"
    [ 21117.658] (**) Option "xkb_layout" "us"
    [ 21117.660] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event5)
    [ 21117.660] (II) No input driver/identifier specified (ignoring)
    [ 21117.660] (II) config/udev: Adding input device HDA NVidia Headphone (/dev/input/event6)
    [ 21117.660] (II) No input driver/identifier specified (ignoring)
    [ 21117.666] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
    [ 21117.666] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
    [ 21117.666] (**) AT Translated Set 2 keyboard: always reports core events
    [ 21117.666] (**) AT Translated Set 2 keyboard: Device: "/dev/input/event0"
    [ 21117.684] (--) AT Translated Set 2 keyboard: Found keys
    [ 21117.684] (II) AT Translated Set 2 keyboard: Configuring as keyboard
    [ 21117.684] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD)
    [ 21117.684] (**) Option "xkb_rules" "evdev"
    [ 21117.684] (**) Option "xkb_model" "evdev"
    [ 21117.684] (**) Option "xkb_layout" "us"
    [ 21117.685] (II) config/udev: Adding input device ImPS/2 Generic Wheel Mouse (/dev/input/event4)
    [ 21117.685] (**) ImPS/2 Generic Wheel Mouse: Applying InputClass "evdev pointer catchall"
    [ 21117.685] (**) ImPS/2 Generic Wheel Mouse: always reports core events
    [ 21117.685] (**) ImPS/2 Generic Wheel Mouse: Device: "/dev/input/event4"
    [ 21117.707] (--) ImPS/2 Generic Wheel Mouse: Found 3 mouse buttons
    [ 21117.707] (--) ImPS/2 Generic Wheel Mouse: Found scroll wheel(s)
    [ 21117.707] (--) ImPS/2 Generic Wheel Mouse: Found relative axes
    [ 21117.708] (--) ImPS/2 Generic Wheel Mouse: Found x and y relative axes
    [ 21117.708] (II) ImPS/2 Generic Wheel Mouse: Configuring as mouse
    [ 21117.708] (II) ImPS/2 Generic Wheel Mouse: Adding scrollwheel support
    [ 21117.708] (**) ImPS/2 Generic Wheel Mouse: YAxisMapping: buttons 4 and 5
    [ 21117.708] (**) ImPS/2 Generic Wheel Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [ 21117.708] (II) XINPUT: Adding extended input device "ImPS/2 Generic Wheel Mouse" (type: MOUSE)
    [ 21117.708] (**) ImPS/2 Generic Wheel Mouse: (accel) keeping acceleration scheme 1
    [ 21117.708] (**) ImPS/2 Generic Wheel Mouse: (accel) acceleration profile 0
    [ 21117.708] (**) ImPS/2 Generic Wheel Mouse: (accel) acceleration factor: 2.000
    [ 21117.708] (**) ImPS/2 Generic Wheel Mouse: (accel) acceleration threshold: 4
    [ 21117.708] (II) ImPS/2 Generic Wheel Mouse: initialized for relative axes.
    [ 21117.708] (II) config/udev: Adding input device ImPS/2 Generic Wheel Mouse (/dev/input/mouse0)
    [ 21117.708] (II) No input driver/identifier specified (ignoring)
    [ 21117.709] (II) config/udev: Adding input device PC Speaker (/dev/input/event1)
    [ 21117.709] (II) No input driver/identifier specified (ignoring)
    [ 21117.847] (II) Power Button: Close
    [ 21117.848] (II) UnloadModule: "evdev"
    [ 21117.871] (II) Power Button: Close
    [ 21117.871] (II) UnloadModule: "evdev"
    [ 21117.917] (II) AT Translated Set 2 keyboard: Close
    [ 21117.917] (II) UnloadModule: "evdev"
    [ 21117.971] (II) ImPS/2 Generic Wheel Mouse: Close
    [ 21117.971] (II) UnloadModule: "evdev"
    Last edited by arthd (2011-04-09 18:03:52)

    pacman -Syu

  • [SOLVED] Dwm and slim problem.

    i installed dwm and slim in my arch and now i cant go back to the terminal to do changes, it puts me on the log in (slim) and i cant close it, i want to do changes in ~/xinitrc.
    Please help me.
    Thanks.
    Last edited by Iason (2010-09-13 07:47:02)

    Alt-F2
    If that doesn't work, Alt-F3
    If that doesn't work, Alt-F4
    If that doesn't work try again but with Ctrl-Alt-F2, etc.
    If that doesn't work come back here.
    edit: *shakes fist at jasonwryan* *sticks out tongue at thayer*
    Last edited by fsckd (2010-09-12 21:47:51)

  • Switching between VTs kills Xorg and GDM restarts

    Hi,
    since yesterday I noticed some sort of severe problem of my system.  I am still trying to locate the reason why this all happens.
    My problem looks like this: Every time I switch from X to a VT everything looks fine. But once I want to switch back to X, it dies completely and GDM restarts.
    So far so bad, first I thought GDM is creating this and downgraded it to 2.22. That didn't help, so back up to date.
    But I activated its debug modus to receive this output:
    Oct 5 10:05:10 t23 acpid: client 3785[0:0] has disconnected
    Oct 5 10:05:10 t23 acpid: client connected from 3785[0:0]
    Oct 5 10:05:10 t23 acpid: 1 client rule loaded
    Oct 5 10:05:11 t23 gdm-simple-slave[3784]: DEBUG(+): GdmWelcomeSession: child (pid:3808) done (status:1)
    Oct 5 10:05:11 t23 gdm-simple-slave[3784]: DEBUG(+): GdmSimpleSlave: Greeter exited: 1
    Oct 5 10:05:11 t23 gdm-simple-slave[3784]: DEBUG(+): slave finished
    Oct 5 10:05:11 t23 gdm-simple-slave[3784]: DEBUG(+): GdmWelcomeSession: De-registering session from ConsoleKit
    Oct 5 10:05:11 t23 gdm-simple-slave[3784]: DEBUG(+): GdmWelcomeSession: Stopping D-Bus daemon
    Oct 5 10:05:11 t23 gdm-simple-slave[3784]: DEBUG(+): GdmCommon: sending signal 15 to process -3807
    Oct 5 10:05:11 t23 gdm-simple-slave[3784]: DEBUG(+): GdmSimpleSlave: Stopping simple_slave
    Oct 5 10:05:11 t23 gdm-simple-slave[3784]: DEBUG(+): GdmSlave: Stopping slave
    Oct 5 10:05:11 t23 gdm-simple-slave[3784]: DEBUG(+): GdmSlave: Disconnected from display
    Oct 5 10:05:11 t23 gdm-simple-slave[3784]: DEBUG(+): GdmSimpleSlave: Stopping greeter
    Oct 5 10:05:11 t23 gdm-simple-slave[3784]: DEBUG(+): GreeterServer: Stopping greeter server...
    Oct 5 10:05:11 t23 gdm-simple-slave[3784]: DEBUG(+): GdmSessionDirect: Closing session
    Oct 5 10:05:11 t23 gdm-simple-slave[3784]: DEBUG(+): GdmSessionWorkerJob: Stopping job pid:3833
    Oct 5 10:05:11 t23 gdm-simple-slave[3784]: DEBUG(+): GdmCommon: sending signal 15 to process 3833
    Oct 5 10:05:11 t23 gdm-simple-slave[3784]: DEBUG(+): GdmSessionWorkerJob: Waiting on process 3833
    Oct 5 10:05:11 t23 gdm-simple-slave[3784]: DEBUG(+): GdmCommon: process (pid:3833) done (status:1)
    Oct 5 10:05:11 t23 gdm-simple-slave[3784]: DEBUG(+): GdmSessionWorkerJob: Wait on child process failed
    Oct 5 10:05:11 t23 gdm-simple-slave[3784]: DEBUG(+): GdmSessionWorkerJob: SessionWorkerJob died
    Oct 5 10:05:11 t23 gdm-simple-slave[3784]: DEBUG(+): GdmSessionDirect: Disposing session
    Oct 5 10:05:11 t23 gdm-simple-slave[3784]: DEBUG(+): GdmSessionDirect: Closing session
    Oct 5 10:05:11 t23 gdm-simple-slave[3784]: DEBUG(+): GdmServer: Stopping server
    Oct 5 10:05:11 t23 gdm-simple-slave[3784]: DEBUG(+): GdmCommon: sending signal 15 to process 3785
    Oct 5 10:05:11 t23 gdm-simple-slave[3784]: DEBUG(+): GdmServer: Waiting on process 3785
    Oct 5 10:05:11 t23 gdm-simple-slave[3784]: DEBUG(+): GdmCommon: process (pid:3785) done (signal:6)
    Oct 5 10:05:11 t23 gdm-simple-slave[3784]: DEBUG(+): GdmServer: Server died
    Oct 5 10:05:11 t23 gdm-session-worker[3833]: DEBUG(+): GdmSessionWorker: obj_path=/org/freedesktop/DBus/Local interface=org.freedesktop.DBus.Local method=Disconnected
    Oct 5 10:05:11 t23 gdm-session-worker[3833]: DEBUG(+): GdmSessionWorker: Got disconnected from the server
    Oct 5 10:05:11 t23 gdm-simple-slave[3784]: DEBUG(+): GdmSignalHandler: Removing handler 10: signum=11 0x80536e0
    Oct 5 10:05:11 t23 gdm-simple-slave[3784]: DEBUG(+): GdmSlave: Stopping slave
    Oct 5 10:05:11 t23 gdm-simple-slave[3784]: DEBUG(+): GdmSignalHandler: Finalizing signal handler
    Oct 5 10:05:11 t23 gdm-simple-slave[3784]: DEBUG(+): Slave finished
    Oct 5 10:05:11 t23 gdm-binary[3373]: DEBUG(+): GdmSlaveProxy: slave (pid:3784) done (status:0)
    Oct 5 10:05:11 t23 gdm-binary[3373]: DEBUG(+): GdmDisplay: Slave exited: 0
    Oct 5 10:05:11 t23 gdm-binary[3373]: DEBUG(+): GdmDisplay: Finishing display: /org/gnome/DisplayManager/Display1
    Oct 5 10:05:11 t23 gdm-binary[3373]: DEBUG(+): GdmDisplay: Unmanaging display
    Oct 5 10:05:11 t23 gdm-binary[3373]: DEBUG(+): GdmDisplay: unmanage display
    Oct 5 10:05:11 t23 gdm-binary[3373]: DEBUG(+): GdmSlaveProxy: Killing slave
    Oct 5 10:05:11 t23 gdm-binary[3373]: DEBUG(+): GdmSlaveProxy: Disposing slave proxy
    Oct 5 10:05:11 t23 gdm-binary[3373]: DEBUG(+): GdmSlaveProxy: Killing slave
    Oct 5 10:05:11 t23 gdm-binary[3373]: DEBUG(+): GdmLocalDisplayFactory: static display status changed: 0
    Oct 5 10:05:11 t23 gdm-binary[3373]: DEBUG(+): GdmDisplay: Managing display: /org/gnome/DisplayManager/Display1
    Oct 5 10:05:11 t23 gdm-binary[3373]: DEBUG(+): GdmDisplay: manage display
    Oct 5 10:05:11 t23 gdm-binary[3373]: DEBUG(+): GdmDisplay: Preparing display: /org/gnome/DisplayManager/Display1
    Oct 5 10:05:11 t23 gdm-binary[3373]: DEBUG(+): GdmDisplay: prepare display
    Oct 5 10:05:11 t23 gdm-binary[3373]: DEBUG(+): GdmDisplayAccessFile: creating xauth directory /var/run/gdm/auth-for-gdm-XXXXXX
    Oct 5 10:05:11 t23 gdm-binary[3373]: DEBUG(+): GdmDisplayAccessFile: chowning /var/run/gdm/auth-for-gdm-XBcN2s to 120:120
    Oct 5 10:05:11 t23 gdm-binary[3373]: DEBUG(+): GdmDisplayAccessFile: creating /var/run/gdm/auth-for-gdm-XBcN2s/database
    Oct 5 10:05:11 t23 gdm-binary[3373]: DEBUG(+): GdmDisplayAccessFile: chowning /var/run/gdm/auth-for-gdm-XBcN2s/database to 120:120
    Oct 5 10:05:11 t23 gdm-binary[3373]: DEBUG(+): GdmDisplayAccessFile: chmoding /var/run/gdm/auth-for-gdm-XBcN2s to 0711
    Oct 5 10:05:11 t23 gdm-binary[3373]: DEBUG(+): GdmLocalDisplayFactory: static display status changed: 1
    Oct 5 10:05:11 t23 gdm-binary[3373]: DEBUG(+): GdmSlaveProxy: Running command: /usr/lib/gdm/gdm-simple-slave --display-id /org/gnome/DisplayManager/Display1
    Oct 5 10:05:11 t23 gdm-binary[3373]: DEBUG(+): GdmSlaveProxy: Started slave with pid 3859
    Oct 5 10:05:12 t23 gdm-simple-slave[3859]: DEBUG(+): Enabling debugging
    Oct 5 10:05:12 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSignalHandler: Adding handler 1: signum=15 0x804d1b0
    Oct 5 10:05:12 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSignalHandler: Registering for 15 signals
    Oct 5 10:05:12 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSignalHandler: Adding handler 2: signum=2 0x804d1b0
    Oct 5 10:05:12 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSignalHandler: Registering for 2 signals
    Oct 5 10:05:12 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSignalHandler: Adding handler 3: signum=4 0x804d1b0
    Oct 5 10:05:12 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSignalHandler: Registering for 4 signals
    Oct 5 10:05:12 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSignalHandler: Adding handler 4: signum=7 0x804d1b0
    Oct 5 10:05:12 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSignalHandler: Registering for 7 signals
    Oct 5 10:05:12 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSignalHandler: Adding handler 5: signum=8 0x804d1b0
    Oct 5 10:05:12 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSignalHandler: Registering for 8 signals
    Oct 5 10:05:12 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSignalHandler: Adding handler 6: signum=1 0x804d1b0
    Oct 5 10:05:12 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSignalHandler: Registering for 1 signals
    Oct 5 10:05:12 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSignalHandler: Adding handler 7: signum=11 0x804d1b0
    Oct 5 10:05:12 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSignalHandler: Registering for 11 signals
    Oct 5 10:05:12 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSignalHandler: Adding handler 8: signum=6 0x804d1b0
    Oct 5 10:05:12 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSignalHandler: Registering for 6 signals
    Oct 5 10:05:12 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSignalHandler: Adding handler 9: signum=10 0x804d1b0
    Oct 5 10:05:12 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSignalHandler: Registering for 10 signals
    Oct 5 10:05:12 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSignalHandler: Adding handler 10: signum=12 0x804d1b0
    Oct 5 10:05:12 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSignalHandler: Registering for 12 signals
    Oct 5 10:05:12 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSlave: Registering /org/gnome/DisplayManager/Slave1
    Oct 5 10:05:12 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSlave: starting slave
    Oct 5 10:05:12 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSlave: Starting slave
    Oct 5 10:05:12 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSlave: Creating proxy for /org/gnome/DisplayManager/Display1
    Oct 5 10:05:12 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSlave: Got display ID: /org/gnome/DisplayManager/Display1
    Oct 5 10:05:12 t23 gdm-binary[3373]: DEBUG(+): GdmDisplay: Setting slave bus name::1.50 on display :0
    Oct 5 10:05:12 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSignalHandler: Adding handler 11: signum=10 0x80536e0
    Oct 5 10:05:12 t23 gdm-simple-slave[3859]: DEBUG(+): GdmServer: Starting X server process: /usr/bin/Xorg :0 -br -verbose -auth /var/run/gdm/auth-for-gdm-XBcN2s/database -nolisten tcp vt9
    Oct 5 10:05:12 t23 gdm-simple-slave[3860]: DEBUG(+): GdmServer: Opening logfile for server /var/log/gdm/:0.log
    Oct 5 10:05:12 t23 gdm-simple-slave[3859]: DEBUG(+): GdmServer: Started X server process 3860 - waiting for READY
    Oct 5 10:05:12 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSimpleSlave: Started X server
    Oct 5 10:05:12 t23 acpid: client 3785[0:0] has disconnected
    Oct 5 10:05:12 t23 acpid: client connected from 3860[0:0]
    Oct 5 10:05:12 t23 acpid: 1 client rule loaded
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSignalHandler: handling signal 10
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSignalHandler: Found 2 callbacks
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSignalHandler: running 10 handler: 0x80536e0
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSignalHandler: running 10 handler: 0x804d1b0
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): Got callback for signal 10
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): Got USR1 signal
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSignalHandler: Done handling signals
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmServer: Got USR1 from X server - emitting READY
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSlave: Server is ready - opening display :0
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSlave: Connected to display :0
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSlave: Requesting timed login details
    Oct 5 10:05:14 t23 gdm-binary[3373]: DEBUG(+): GdmSlave: Got timed login details for display :0: 0 '(null)' 0
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSlave: Got timed login details: 0 0
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSimpleSlave: Running greeter
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSimpleSlave: Creating greeter for :0
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmServer: Running helper /usr/lib/ConsoleKit/ck-get-x11-display-device --display :0
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmServer: Got tty: '/dev/tty9'
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSlave: Trying script /etc/gdm/Init/:0
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSlave: script /etc/gdm/Init/:0 not found; skipping
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSlave: Trying script /etc/gdm/Init/Default
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSlave: Running process: /etc/gdm/Init/Default
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSlave: script environment: XAUTHORITY=/var/run/gdm/auth-for-gdm-XBcN2s/database
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSlave: script environment: X_SERVERS=/var/gdm/:0.Xservers
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSlave: script environment: LOGNAME=gdm
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSlave: script environment: PWD=/var/lib/gdm
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSlave: script environment: HOME=/var/lib/gdm
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSlave: script environment: DISPLAY=:0
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSlave: script environment: PATH=/usr/local/bin:/usr/bin:/bin
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSlave: script environment: SHELL=/sbin/nologin
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSlave: script environment: RUNNING_UNDER_GDM=true
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSlave: script environment: USER=gdm
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSlave: script environment: USERNAME=gdm
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSlave: Process exit status: 0
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GreeterServer: Creating D-Bus server for greeter
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GreeterServer: D-Bus server listening on unix:abstract=/tmp/gdm-greeter-LPWxSRoX,guid=6a268b231fa1c460f956c0f500000198
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSimpleSlave: Creating greeter on :0 /dev/tty9
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: Starting welcome...
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: Running welcome_session process: /usr/bin/gnome-session --autostart=/usr/share/gdm/autostart/LoginWindow/
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: Registering session with ConsoleKit
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: Opening ConsoleKit session for user:120 x11-display:':0' x11-display-device:'/dev/tty9' remote-host-name:'' is-local:1
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: Starting D-Bus daemon
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): Cannot access '/etc/sysconfig/i18n'
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: WINDOWPATH=9
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: DISPLAY=:0
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: XAUTHORITY=/var/run/gdm/auth-for-gdm-XBcN2s/database
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: LOGNAME=gdm
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: GDM_VERSION=2.32.0
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: HOME=/var/lib/gdm
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: LANG=en_GB.utf8
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: PATH=/bin:/usr/bin:/sbin:/usr/sbin:/usr/lib/perl5/core_perl/bin
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: PWD=/var/lib/gdm
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: SHELL=/sbin/nologin
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: GVFS_DISABLE_FUSE=1
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: RUNNING_UNDER_GDM=true
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: USER=gdm
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: USERNAME=gdm
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: XDG_SESSION_COOKIE=55a05d047ffc8a00c35d0e0047eda69e-1286269514.940105-1594411165
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: GDM_GREETER_DBUS_ADDRESS=unix:abstract=/tmp/gdm-greeter-LPWxSRoX,guid=6a268b231fa1c460f956c0f500000198
    Oct 5 10:05:14 t23 gdm-simple-slave[3878]: DEBUG(+): GdmWelcomeSession: Setting up run time dir /var/run/gdm/greeter
    Oct 5 10:05:14 t23 gdm-simple-slave[3878]: DEBUG(+): GdmWelcomeSession: Changing (uid:gid) for child process to (120:120)
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: Started D-Bus daemon on pid 3882
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): Cannot access '/etc/sysconfig/i18n'
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: GDM_SEAT_ID=Seat1
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: WINDOWPATH=9
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: DISPLAY=:0
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: XAUTHORITY=/var/run/gdm/auth-for-gdm-XBcN2s/database
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: LOGNAME=gdm
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: GDM_VERSION=2.32.0
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: HOME=/var/lib/gdm
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: LANG=en_GB.utf8
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: PATH=/bin:/usr/bin:/sbin:/usr/sbin:/usr/lib/perl5/core_perl/bin
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: PWD=/var/lib/gdm
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: SHELL=/sbin/nologin
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: GVFS_DISABLE_FUSE=1
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-ZckquHbw5o,guid=bb2af808d623ae703f9916fa00000198
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: GCONF_DEFAULT_SOURCE_PATH=/etc/gconf/2/path
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: RUNNING_UNDER_GDM=true
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: USER=gdm
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: USERNAME=gdm
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: XDG_SESSION_COOKIE=55a05d047ffc8a00c35d0e0047eda69e-1286269514.940105-1594411165
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: welcome environment: GDM_GREETER_DBUS_ADDRESS=unix:abstract=/tmp/gdm-greeter-LPWxSRoX,guid=6a268b231fa1c460f956c0f500000198
    Oct 5 10:05:14 t23 gdm-simple-slave[3883]: DEBUG(+): GdmWelcomeSession: Setting up run time dir /var/run/gdm/greeter
    Oct 5 10:05:14 t23 gdm-simple-slave[3883]: DEBUG(+): GdmWelcomeSession: Changing (uid:gid) for child process to (120:120)
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmWelcomeSession: WelcomeSession on pid 3883
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSimpleSlave: Creating new session
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSessionDirect: Creating D-Bus server for session
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSessionDirect: D-Bus server listening on unix:abstract=/tmp/gdm-session-UgKEyrlf,guid=3f8d34c80542f206f87332a000000198
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSessionDirect: Setting display device: /dev/tty9
    Oct 5 10:05:14 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSessionDirect: Registering /org/gnome/DisplayManager/Session1
    Oct 5 10:05:15 t23 gnome-session[3883]: Bonobo-WARNING: Bonobo must be initialized before use
    Oct 5 10:05:15 t23 gdm-simple-greeter[3905]: DEBUG(+): Enabling debugging
    Oct 5 10:05:16 t23 gdm-simple-slave[3859]: DEBUG(+): GreeterServer: Handing new connection
    Oct 5 10:05:16 t23 gdm-simple-slave[3859]: DEBUG(+): GreeterServer: greeter connection is 0x9699308
    Oct 5 10:05:16 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSimpleSlave: Greeter connected
    Oct 5 10:05:16 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSessionDirect: Starting conversation
    Oct 5 10:05:16 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSessionWorkerJob: Starting worker...
    Oct 5 10:05:16 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSessionWorkerJob: Running session_worker_job process: /usr/lib/gdm/gdm-session-worker
    Oct 5 10:05:16 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSessionWorkerJob: : SessionWorkerJob on pid 3908
    Oct 5 10:05:16 t23 gdm-simple-slave[3859]: DEBUG(+): GreeterServer: obj_path=/org/gnome/DisplayManager/GreeterServer interface=org.gnome.DisplayManager.GreeterServer method=GetDisplayId
    Oct 5 10:05:16 t23 gdm-simple-slave[3859]: DEBUG(+): greeter_server_message_handler: destination=(null) obj_path=/org/gnome/DisplayManager/GreeterServer interface=org.gnome.DisplayManager.GreeterServer method=GetDisplayId
    Oct 5 10:05:16 t23 gdm-session-worker[3908]: DEBUG(+): Enabling debugging
    Oct 5 10:05:16 t23 gdm-session-worker[3908]: DEBUG(+): GdmSessionWorker: connecting to address: unix:abstract=/tmp/gdm-session-UgKEyrlf,guid=3f8d34c80542f206f87332a000000198
    Oct 5 10:05:16 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSessionDirect: Handing new connection
    Oct 5 10:05:16 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSessionDirect: worker connection is 0x969ac90
    Oct 5 10:05:16 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSessionDirect: Emitting conversation-started signal
    Oct 5 10:05:16 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSimpleSlave: session conversation started
    Oct 5 10:05:16 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSlave: Requesting timed login details
    Oct 5 10:05:16 t23 gdm-session-worker[3908]: DEBUG(+): GdmSignalHandler: Adding handler 1: signum=15 0x804ba60
    Oct 5 10:05:16 t23 gdm-session-worker[3908]: DEBUG(+): GdmSignalHandler: Registering for 15 signals
    Oct 5 10:05:16 t23 gdm-session-worker[3908]: DEBUG(+): GdmSignalHandler: Adding handler 2: signum=2 0x804ba60
    Oct 5 10:05:16 t23 gdm-session-worker[3908]: DEBUG(+): GdmSignalHandler: Registering for 2 signals
    Oct 5 10:05:16 t23 gdm-session-worker[3908]: DEBUG(+): GdmSignalHandler: Adding handler 3: signum=4 0x804ba60
    Oct 5 10:05:16 t23 gdm-session-worker[3908]: DEBUG(+): GdmSignalHandler: Registering for 4 signals
    Oct 5 10:05:16 t23 gdm-session-worker[3908]: DEBUG(+): GdmSignalHandler: Adding handler 4: signum=7 0x804ba60
    Oct 5 10:05:16 t23 gdm-session-worker[3908]: DEBUG(+): GdmSignalHandler: Registering for 7 signals
    Oct 5 10:05:16 t23 gdm-session-worker[3908]: DEBUG(+): GdmSignalHandler: Adding handler 5: signum=8 0x804ba60
    Oct 5 10:05:16 t23 gdm-session-worker[3908]: DEBUG(+): GdmSignalHandler: Registering for 8 signals
    Oct 5 10:05:16 t23 gdm-session-worker[3908]: DEBUG(+): GdmSignalHandler: Adding handler 6: signum=1 0x804ba60
    Oct 5 10:05:16 t23 gdm-session-worker[3908]: DEBUG(+): GdmSignalHandler: Registering for 1 signals
    Oct 5 10:05:16 t23 gdm-session-worker[3908]: DEBUG(+): GdmSignalHandler: Adding handler 7: signum=11 0x804ba60
    Oct 5 10:05:16 t23 gdm-session-worker[3908]: DEBUG(+): GdmSignalHandler: Registering for 11 signals
    Oct 5 10:05:16 t23 gdm-session-worker[3908]: DEBUG(+): GdmSignalHandler: Adding handler 8: signum=6 0x804ba60
    Oct 5 10:05:16 t23 gdm-session-worker[3908]: DEBUG(+): GdmSignalHandler: Registering for 6 signals
    Oct 5 10:05:16 t23 gdm-session-worker[3908]: DEBUG(+): GdmSignalHandler: Adding handler 9: signum=10 0x804ba60
    Oct 5 10:05:16 t23 gdm-session-worker[3908]: DEBUG(+): GdmSignalHandler: Registering for 10 signals
    Oct 5 10:05:16 t23 gdm-binary[3373]: DEBUG(+): GdmSlave: Got timed login details for display :0: 0 '(null)' 0
    Oct 5 10:05:16 t23 gdm-simple-slave[3859]: DEBUG(+): GdmSlave: Got timed login details: 0 0
    Oct 5 10:05:16 t23 gdm-simple-slave[3859]: DEBUG(+): Invalid NULL username for auto/timed login
    Once I switch back, GDM reloads and I get the same output with GDM stating nothing why this happened.
    I looked through all log files without finding anything obvious. My problem is, that I am not sure if it is GDM doing this or some buggy configuration of a programme doing rubbish...
    Some helpful advice will be nice.
    Regards,
    Simon

    Problem solved temporarily:
    I downgraded all X.org packages related to the recent update for xorg-server 1.9. Since then GDM doesn't seam to crash. Otherwise I noted that 1.9 is not much of a matured release yet. I read many instability issues here.
    Btw, would a mod like to move this thread to update issues? This thread will better fit in that section.
    Thanks
    Last edited by ss2 (2010-10-07 14:40:32)

  • [SOLVED:] SLIM not reading slim.conf (no password auto-focus)

    Yesterday I began having issues with SLIM.  I'm not sure if they're related, but  while running Puppy , I inadvertently deleted the desktop icon for my Arch home directory on /dev/sda8.  I rebooted Puppy and it reappeared.  After running Puppy, something went wrong with my clocks (system and hardware) and the times were all wrong.  I fixed that with NTPD.  I currently dual boot Arch and Windows 7 from the hard drive, and occasionally from a USB stick, Puppy Linux.  I'm using an ASUS K50IJ laptop.  I run Xfce4.  I do not have any disk encryption enabled.
    When I boot up, the SLIM login appears as normal, but rather than password auto-focus, I'm prompted for a username.  If I enter the username and hit return, I'm still staring at the username prompt.  After three or four iterations of entering a username + enter, I finally get a password prompt and can log in.
    I have tried:
    1.  Reinstalling archlinux-themes-slim
    2.  Uninstalling archlinux-themes-slim and slim, then reinstalling slim
    3.  Removing old Xfce4 & Xfwm sessions
    4.  Removing slim.conf and entering a pristine version.
    5.  Reviewing /var/log/slim.log files for oddities.  I found one:
    Before the trouble started, I the message in the log was:
    slim: waiting for X server to begin accepting connections
    X.Org X Server 1.12.2
    Release Date: 2012-05-29
    X Protocol Version 11, Revision 0
    Build Operating System: Linux 3.0.32-1-lts x86_64
    Current Operating System: Linux asus 3.4.4-2-ARCH #1 SMP PREEMPT Sun Jun 24 18:5
    9:47 CEST 2012 x86_64
    Kernel command line: root=/dev/sda4 ro
    Build Date: 30 May 2012 07:24:13PM
    Current version of pixman: 0.26.2
    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: Sun Jul 8 15:30:48 2012
    (==) Using config directory: "/etc/X11/xorg.conf.d"
    /usr/bin/xauth: file /home/rasteenb/.Xauthority does not exist
    /usr/bin/startxfce4: X server already running on display :0.0
    Now I get:
    slim: waiting for X server to begin accepting connections.slim: unexpected signal 15
    slim: waiting for X server to begin accepting connections.
    slim: System is booting up.
    slim: pam_authentication(): Authentication failure
    slim: System is booting up.
    slim: pam_authentication(): Authentication failure
    slim: System is booting up.
    slim: pam_authentication(): Authentication failure
    slim: System is booting up.
    slim: pam_authentication(): Authentication failure
    slim: System is booting up.
    slim: pam_authentication(): Authentication failure
    Now I'm stumped.
    Rob
    Last edited by rasteenb (2012-07-17 11:16:03)

    I solved this - slim was not the last daemon I started in rc.conf.  By moving it to the end, I get password auto-focus and everything works.
    Now my rc.conf looks like
    # DAEMONS
    DAEMONS=(syslog-ng dbus acpid @network @wicd @openntpd @cupsd @crond slim)
    I found this recommendation in the Display Manager wiki page while researching the problem:
    Ensure you start the display manager last in the DAEMONS array, otherwise X will later allocate a tty device which was previously claimed by Getty (see /etc/inittab). Not placing the display manager at the end can cause X crashes, and is therefore unsupported.
    I'd just been lucky before that there wasn't a conflict.
    There is a "flicker" during login where I'm shown the XFCE splash, then the SLIM splash again, then the XFCE desktop.  Not sure what's going on there, but it's no big deal.
    Cheers,
    Rob

  • [SOLVED] SLiM locked in Virtual Box

    So I installed the newest iso, got things ok in terminal and installed SLiM, but I'm stuck at the SLiM login. Neither root nor user works. I've tried console as username to force xterm, but all I get is a black screen with an X for a mouse. tried exit and nothing happened. I really need to get back to no GUI so I can edit the options for SLiM and get myself started. I'm going to be running Razor-QT on top of Openbox and SliM as login. Problem is I can't install Razor until I can visit the AUR..... Anyway, if someone can get me the hell out of slim I'd appreciate it.
    Last edited by al0ngcam3asp1d3r (2012-08-01 00:25:50)

    TheCuban wrote:Type "console" as a username, should give you a console. If it doesn't, it it kinda "freezes" on you, then hit ALT + F1 and you should be good to go!
    You freaking rock bro. I'm sorry to be a pain in the ass to everyone, but most of my experience is in Ubuntu (I know that's like the f word) but I've run arch before and adored it, and have decided to use it as the base of a new distro which is like Bugtraq (I'm the graphics developer for the new version in dev) built on Arch for speed, so I'm I'm going to probably ask a lot of questions, however I am good at RTFM so I'll try not to ask any stupid questions.

  • Hey, i have a ps3 slim and when i try to update always my ps3 stop in 99% help please

    hey, i have a ps3 slim and when i try to update always my ps3 stop in 99% help please

    Please post your concern on Sony PlayStation Community here for further assistance. Thank you! 
    If my post answers your question, please mark it as "Accept as Solution"

  • Human Task Auto Release Default  and configuration question in 11g

    Is there anyway to turn off the auto release feature of a human task if you do not put an expiration date on a task? Also the documentation says the default is 12 hours. If there is not a way to turn off the auto release feature, can the 12 hour default be changed? The documentation is not fully clear to me and then when I look at the UI from the console I do not understand what the identifiers of P5D, P4D, etc mean under the Default Duration column. I get the use of percentage but it is unclear what Default Duration is and how to use that field.
    I saw in 10.1.2 there was a way to turn off the auto release feature of task via restrictedActions but I did not see this in 11g.
    And last question is does anyone know if human task is stored to a database if it runs for too long similar to the concept discussed around bpel processes of hydration and dehydration?
    Thanks,
    Diane

    I am able to fix this issue. After a series of R & D I was able to find that the root cause is %APPDATA%\jdeveloper. Deleting the relevant directory will solve this issue. In fact, I tried to delete the entire jdeveloper directory under %APPDATA% and the jdev 11.1.1.7 form generation issue got resolved. Those who find "referential integrity" issue may follow this approach.
    This solution also applies to this thread
    Auto Generate task Form

  • Macbook pro starts up but i see picture of some files and a question mark

    So I was on my laptop today and it just outta nowhere froze , the song i was listening stopped and i couldn't change the page, i could move the trackpad but nothing else.
    so i clicked on the off button and turned it off.
    then i tried to turn it on again but while loading it just stayed blank and this picture of some files and a question mark on them appeared, i have no idea what's going on.
    I turned it off again and turned it back on and the little apple appeared and it was loading but then a sign appeared like one of prohibited (the one that's a circle and has a slash across it) and idk what to do! i'm so frustrated all my school files are there and idk why this happened in the first place.
    i turned it off and just put it to charge.
    lately i've been using it a lot and i had a few things on when it froze , so im just gonna leave it off for a while but what can i do?
    how do u solve this? has anyone had this happened to their macbook pro already? i bought it just last year idk why this is happening.

    The folder and question mark means it cannot find a valid OSX Boot Volume, you need to Boot from your original install DVD (hold c at start) and then run Disc Utility from the top menu bar and run both 'Repair Disc' and 'Repair Permissions'. If it still doesn't boot from the internal hard drive then you need to boot from that install DVD again and do an archive (re)install of the operating system. (Your User data will be saved that way)

Maybe you are looking for