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.

Similar Messages

[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

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)

HT201263 my phone is in recovery mode and wont restore. instead i receive the error message 1604. i have used alternative usb cables and am at a loss. has anyone else had this problem?

Hi,
my phone is in recovery mode and wont restore. instead i receive the error message 1604. i have used alternative usb cables and am at a loss. has anyone else had this problem?

Hi there hstear93,
You may find the information in the article below helpful.
iOS: Not responding or does not turn on
http://support.apple.com/kb/ts3281
-Griff W.

Alternating mac face and question mark after i tried to install OS X 10.3

I have a Powerbook G4 and I tried to update my operating sytem from 10.2.8 to 10.3 but it froze. After I restarted it I got an alternating mac face and question mark. It just ejects the CDs I try to put into it except for the installation disk for OS X 10.1.3. When I put that one in a smiling mac computer come up then all this type comes across the screen, something about kernels and panic.
Please help me, I've got a project due soon.

Could someone please help me,
when i open my power book g4, an alternating Mac face and question mark appears, and no matter what I do it is still there.
it only changes when I insert the installtion CD of MAC OS X 10.3, but after the Apple logo appears, the screen went white and sometimes just blue, and it just won't work. Then after restarting, the alternating Mac face and question mark still appear.
i also tried the hardware test, after doing both of the tests, the result is consistently "passed". But after restarting, the same problem happens.
what should i do?
please help me
thanx in advanced

XDMCP and GDM Start of a later session problem.

I'm currently running Archlinux on one computer (PC1) and Windows Vista on another (PC2). I have X11 and GDM installed and they work perfectly. On PC2 I use Xming to connect to PC1 via the XDMCP protocol and everything works perfectly the first time this occurs after a reboot of PC1 or restart of GDM on PC1. But if I log out of the session and try to reconnect to it later via Xming, Xming starts up then immediately crashes. Only if I reboot PC1 or restart GDM will it connect again. I'm not trying to resume a session or anything like that, that would be nice but all I want to do is to be able to use the desktop at a later time. If any more information is needed it can be supplied. I have a feeling either this can't be done, there's a config setting I missed somewhere or GDM and the XServer are being ran in an incorrect manner. Any help is greatly appeciated.

Delete downloads.sqlite (plus downloads.rdf, if it exists) in the [http://kb.mozillazine.org/Profile_folder_-_Firefox Profile Folder]
See http://kb.mozillazine.org/Unable_to_save_or_download_files#Manually_delete_download_history

[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

Working alternating with iPhoto and FCE tgrying to import pictures from iPhoto into FCE suddenly all my 22300 pictures disappeared leaving empty frames. Does somebody know where the pictures could have gone and how can I get them back into iPhoto? Lothar

Working alternating with iPhoto and FCE tgrying to import pictures from iPhoto into FCE suddenly all my 22300 pictures disappeared leaving empty frames. Does somebody know where the pictures could have gone and how can I get them back into iPhoto? Lothar

The ! turns up when iPhoto loses the connection between the thumbnail in the iPhoto Window and the file it represents.
Option 1
Back Up and try rebuild the library: hold down the command and option (or alt) keys while launching iPhoto. Use the resulting dialogue to rebuild. Choose to Rebuild iPhoto Library Database from automatic backup.
If that fails:
Option 2
Download iPhoto Library Manager and use its rebuild function. This will create a new library based on data in the albumdata.xml file. Not everything will be brought over - no slideshows, books or calendars, for instance - but it should get all your albums and keywords back.
Because this process creates an entirely new library and leaves your old one untouched, it is non-destructive, and if you're not happy with the results you can simply return to your old one. .
Regards
TD

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"

Are there any alternatives for mseg and mkpf

I had to display from table S032...following fields.
S032-LETZTABG --> Date: last (i.e. most recent) goods issue
S032-LETZTVER --> Date: last (i.e. most recent) consumption
However the data was not properly filled in s032 table. So I went for mseg and mkpf table to get budat based on moment types.
 SELECT MSEG~MATNR
 MSEG~WERKS
 MSEG~LGORT
 MSEG~BWART
 MKPF~BUDAT
 INTO TABLE IT_MSEG
 FROM MKPF AS MKPF INNER JOIN MSEG AS MSEG
 ON
 MKPFMBLNR = MSEGMBLNR AND
 MKPFMJAHR = MSEGMJAHR
 FOR ALL ENTRIES IN T_OUT_TMP
 WHERE MSEG~MATNR EQ T_OUT_TMP-MATNR
 AND MSEG~WERKS EQ T_OUT_TMP-WERKS.
Are there any other alternative table for mseg and mkpf...
Because my above coding ( which includes above SELECT of mseg and mkpf )got performance issue...
Could you please suggest me anyu other alternative for mseg and mkpf ...

Try to include the BUDAT in the selection of the MKPF.. if you don't have any restriction in MKPF than just pass an empty range.
RANGES: S_BUDAT FOR MKPF-BUDAT.
SELECT
MKPF~BUDAT "<<<
MSEG~MATNR
MSEG~WERKS
MSEG~LGORT
MSEG~BWART
INTO TABLE IT_MSEG
FROM MKPF AS MKPF INNER JOIN MSEG AS MSEG
ON
MKPF~MBLNR = MSEG~MBLNR AND
MKPF~MJAHR = MSEG~MJAHR
FOR ALL ENTRIES IN T_OUT_TMP
WHERE
MKPF~BUDAT IN S_BUDAT " <<<
MSEG~MATNR EQ T_OUT_TMP-MATNR
AND MSEG~WERKS EQ T_OUT_TMP-WERKS.
Regards,
Naimesh Patel

Alternative condition type and base value

hi
gurus i am very much confused with this
alternative condition type and base value plzz clear me from this confusion
give me with realtime example and tel me in simple way
they will fully rewarded. and also a gud help to me
thanks
srinivask.

Hi
hope it is Alternative Calculation Type and Alternative Condition Base value
if so pls refer below
Alternative Calculation Type:
Normally if you want to calculate a value you have to use a calculation type for determination the value. This calculation type is either addition, subtraction or multiplication. Similarly SAP also has got a default calculation type in the control data of the condition type. There you have the options of either Qty based , Fixed Amount Based or Percentage based.
Here what happens is suppose if you define Your condition type that calculates the base price of a material on Qty based. Then the calculation will be done based on the quantity of the material. If the customer orders 10 Nos and you have maintained a unit price of 100 Rs for each material then the value determined is 1000 INR. Similarly if the discount condition type , you maintain the calculation type as %. This means if you maintain the value of 10 % in the condition record. Then this percentage is taken as the calculation type and the condition value is determined.
In some cases you have to forego the default calculation types and use the customer specific method for calculating a value. For ex if you are calculating the Freight charges for a Material . it depends on so many criteria like, the weight, volume and also the minimum amount etc etc, in those cases, you forego the default value and then use the alternative calculation type in calculating the condition value against the particular condition.

Alternative Condition Base value :
If you have to calculate any value then you have to have a base value for it. For ex if you want to calculate the discount of 10 % for a material then you have to have a base value on which this 10% is calculated. Normally you take the condition value of the base price of the material to calculate the value.
Now you don't want to take the base value and take other values as base value which are derived on some formulae. So you create a routine which will do the mathematical operations in the routine and derive you a value which is now used as the base value for calculating the condition value for a particular condition type

Alternative calculation type and alternative condition base value

In pricing procedure what is the difference between alternative calculation type and alternative condition base value?Kindly help

Hi,
Please check the forum before you post your questions as this question was answered a number of times earlier.
Please check the below link which discusses in detail regarding the same.
[Alt Cal Type and Cond Base Value|Alternative calculation type and alterantive condition base value in pricin;
Regards,
Phani Prasad

Requirement type, alternative calculation type and alternative base value?

Hi guys pls can any body experts in pricing
Can u pls explain requirement type, alternative calculation type and alternative base value?
Not theory Any of Ur real time experience

Requirement:
It is a routine that is written by an ABAP consultant according to the business requirement.
By defining Requirement in condition technique we can restrict the access of condition type.
To understand the concept, we will take the example of the Rebates. Rebates are to be included during the billing document processing and not in the sales document processing. As rebates are given on the delivered quantity and not on the ordered quantity (in case of cut-off period for rebates).
For rebates we use the condition types BO01 to BO05, and in the Requirement column we give the value 24 which is "Only in Billing Document".
This Requirement will ensure that these condition types will appear only during the billing document processing.
If new Requirements are to be defined we follow the procedure given below.
Go to T.Code: VOFM. - Maintain Requirements & Formulas
Click on the "Requirements" in the top menu and then click on "pricing".
We have a list of requirements, we can ask ABAP consultant to create new requirement based on the client requests.
And we assign the application type like V - Sales/Distribution etc.
AltCty - Condition formula for alternative calculation type:
It is again a Routine that is written by ABAP Consultant.
It is an alternative formula for the condition type that can be used instead of standard formulas.
For example, let us take the Profit Margin which can be both + / - , so here this routine will help us in generating the value which can be either + or -. Profit margin is not a condition type so it cannot be classified as +ve or -ve in the V/06.
Ex.: 950 0 Profit Margin 11.
So we assign 11 - Profit Margin.
If new routines are to be defined we follow the procedure given below.
Go to T.Code: VOFM. - Maintain Requirements & Formulas
Click on the "Formulas" and then on the "Condition Values".
We have a list of routines, we can ask ABAP consultant to create new routines based on the client requests.
And we assign the application type.
AltCBV - Alternative formula for condition base value:
Formula for determining the condition basis as an alternative to the standard.
It is again a Routine that is written by ABAP Consultant.
It is used as a basis to calculate value of the condition type instead of using it from the "FROM" column.
Ex.: Freight - KF00.
Freight is calculated based on weight, volume etc. and not on the base price. In pricing there is no entry of weight from which the value can be referred like we do for discounts using base price. We have to get the value from the Material master.
In this column we can mention the value as 12 - Gross Weight or 13 - Net Weight.
During pricing, the system will consider the value that is mentioned in this column and determine the freight based on this value.
Suppose we have Net weight: 100 kgs and Gross Weight: 150 kgs. And if we mention 13 in this column then the Freight condition KF00 will be calculated using the weight as 100 kgs.
Regards
AK

I have some old pagemaker files that I need to open so I have bought a G3 on ebay. It turns on OK but all that comes uo on the screen is an envelope with alternating question mark and apple logo. Any ideas?

I have some old pagemaker files that I need to open so I have bought a G3 on ebay. It turns on OK but all that comes uo on the screen is an envelope with alternating question mark and apple logo. Any ideas?

I suggest you get 9.2. You need to install the same or later version of the OS. One some computer the shipped version has extra drivers. The drivers will not be in the official release in this case 9.1. They would be in 9.2.
Mac OS 9.1 (Mac OS ROM 7.5.1) and Mac OS X 10.0.4 (4P13)
*blinking question mark*
The blinking question mark means that your mac firmware could not find a valid operating system
on one of your disk volumes.
Somethings to do to resolve the blinking question mark.
http://docs.info.apple.com/article.html?artnum=58042
Try holding down the option key then power on. This brings up the startup manager. Click on your hd. Click on right arrow key.
You need to figure out the level of your firmware before installing 10.2 or greater. ( The PC name for firmware is BIOS. ) Installing 10.2 with a down level firmware will most likely make your iMac unusable and difficult to fix.
What is firmware?
The firmware software receives control when you poweron your machine. It does some hardware testing and some hardware configuration then passes control to your version of Mac OS. It reside on a PROM ( program read only memory ) chip on the logic board.
Figuring out what level of firmware you have?
Open Firmware, boot into Open Firmware.
Power on your iMac while holding down command+option+o+f
The first output line contains the firmware level. Mine reads:
Apple PowerMac4,1 4.1.9f1 BootRom built on 09/14/01 at 13.18.04
Copyright 1994-2001 Apple Computer Inc.
On my machine, I have 4.1.9f1.
What firmware do you need?
http://docs.info.apple.com/article.html?artnum=86117
For a slot loading iMac, this article indicates that you need to be running 9.1 or later version of Mac OS Classic.
http://docs.info.apple.com/article.html?artnum=75130
"The iMac Firmware Update 4.1.9 will only run on iMac computers with lot-loading CD or DVD drives running Mac OS 9.1 or later from a local drive. If you are using Mac OS X you must boot from a local Mac OS 9.1 or later writeable partition (not a CD, or network disk) prior to following the update instructions."
You can download the Mac OS 9 updates from the Apple site.
http://support.apple.com/kb/HT1387?viewlocale=en_US

Need to know alternative country Key and Vehicle country Key

Hi Experts,
I am defining new country codes in SAP ECC and GTS System. Can someone help me to find out Alternative country key and Vehicle country key for the below mentioned country Codes.
AX
Åland Islands
GG
Guernsey
IM
Isle Of Man
JE
Jersey
PS
Palestinian Territory, Occupied
TL
Timor-Leste
Please assist me in this regard as this is very urgent.
Thank you
Vinod Kakarla

Hi,
Use Tcode - VI78 to find alternative country key
T coe - OY01 for vehicle country key
001 (European standard formatting), 002 (Italy), 011 (Switzerland) and 014 (Austria) use the vehicle country key of the relevant country. If no vehicle country key has been maintained in Customizing, the country key of table T005 is used instead. If, for the sender country, the indicator for printing the country name in foreign addresses is set in table T005 , the system does not use the country key, but generally prints the country name in the last address line. Check the sap Note: 1509425.
Ashish

Alternative to slim and gdm?

Similar Messages

Maybe you are looking for