Simple Console Display Manager

I created a forked project from "The Console Display Manager" CDM,
thanks Ghost1227 for your work
I simplified its interface and added new options.
It has all its initial features (less theming):
   - Multiple X sessions (user logins are all handled through tty1)
   - Any DE/WM
   - Configurable console logins
   - Users restricted to a single environment bypass the menu on login
   - Root is automatically dropped to console
   - All settings are configurable on a per-user basis
And I added:
   - Uses a common .xinitrc script to start the X programs.
        You can specify a common init script for all your X and I will create a new .xinitrc adding it the command line to execute your X.
   - Supports a default selection and with timeout.
        You can choose a default selection when enter or space is pressed, and you can add a timeout to auto-select the default selection.
        You can press Esc to cancel too.
   - Doesn't clear the screen.
        I like to see the boot messages
   - Doesn't depend on dialog/ncurses.
        Now you have a simpler menu that doesn't clear your screen.
   - Removed themes.
        More gigabytes free on your hdd
CDM-Simple is in AUR
No Wiki yet, the help is on the installed configuration file /etc/cdmrc
Enjoy!
Last edited by jhcasado (2013-09-13 15:11:18)

nice work. gonna test it right now..
im reading the wiki, and found out the config file is in /etc/cdmrc, since everything is being migrated to /etc/name.d/something shouldnt cdm use the same hierarchy just for consistency? or am i missing something else here?
anyway, just cosmetics
EDIT: and....im back..... bravo. gotta love the simplicity!
im not sure if this was thought of yet, but maybe it source a per user config that should override the global one, instead of having the special settings in /etc/cdmrc, there should be a ~/.cdm/ dir with user settings.
Last edited by eldragon (2009-11-10 23:13:16)

Similar Messages

  • Console Display Manager doesn't initiate

    CDM crashes when I log into my username. Am I doing something wrong? Is there anything that conflicts with cdm? I don't have another login manager installed.
    Edited:
    I tried  reinstalling and checking out the pkgbuild. Nothing seems to be out of place.
    Edited:
    I tried the git version and still nothing...
    Here are some of my files
    xinitrc:
    http://pastebin.com/WmGW91kJ
    cdmrc:
    http://pastebin.com/VUwW4g3n
    initab:
    http://pastebin.com/mNXcTNDL
    grep -E '\((WW|EE)' /var/log/Xorg.0.log :
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 1786.099] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
    [ 1786.099] (WW) AllowEmptyInput is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
    [ 1786.099] (WW) Disabling Keyboard0
    [ 1786.099] (WW) Disabling Mouse0
    [ 1786.101] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
    [ 1787.300] (EE) Logitech G9 Laser Mouse: failed to initialize for relative axes
    Edited:
    Guess I need to remove CDM. Here is a list of all my installed programs. Just to let you know, I've recently deleted CDM and installed Slim.
    Pacman -Q
    http://pastebin.com/mQDEaMXz
    Xorg.conf:
    http://pastebin.com/nYBFxLcx
    Last edited by Oblitus (2011-01-29 10:19:50)

    brittyazel: yes I did
    I disabled intel GPU in BIOS and X wasn't able to start. Here is log: http://pastebin.com/jJqksmyS. I think there may be something wrong with my nvidia card. Before arch I used bbswitch to turn it off during startup so I don't even know if it was working earlier or not.
    I'm going to try bbswitch and see what happens.
    [Edit]
    So I tried two ways to turn off dedicated card: acpi_call as it is described in https://wiki.archlinux.org/index.php/hy … screte_GPU and bumblebee with bbswitch https://wiki.archlinux.org/index.php/bumblebee. There was some problems with acpi_call but bumblebee seems to work well and my nvidia GPU is turned of by bbswitch module during startup, but display manager still  doesn't show up. Now I'm absolutely clueless.
    Last edited by jwrona (2014-10-29 20:28:37)

  • How to setup CDM (Console Display Manager)

    Hi there,
    I installed CDM and to check if this is working I installed 3 WM, fluxbox (my default), compiz, awesome.
    Now, after logging into console, when I run "cdm /etc/cdmrc", it throws a black screen and then returns back to console. I believe there is something wrong with my cdmrc. Please suggest.
    Here is my cdmrc:
    #!/bin/bash
    # Example config file for cdm(1).
    # Values set here is the default as in cdm(1).
    # List of programs, commands with whitespaces should be quoted or escaped.
    # If unset, all sessions in /etc/X11/Sessions are offered as choices.
    # (An example:)
    # binlist=(
    # '~/.xsession' # Launch your X session,
    # '/bin/bash --login' # or just execute your shell,
    # '/usr/bin/fbterm' # or start a frame buffer console,
    # '/usr/bin/cdm ~/.submenu.cdmrc' # or go to a submenu :)
    binlist=("~/.xsession")
    # List all program display names, one-by-one matched with $binlist.
    # Names with whitespaces should be quoted or escaped.
    # (Continued example:)
    # namelist=('X session' Console FBTerm 'Sub menu')
    namelist=("X session")
    # Type of the programs, one-by-one matched with $binlist.
    # `C' for *C*onsole programs, which would be `exec'ed.
    # `X' for *X* programs, which would be run with cdm-xlaunch(1).
    # (Continued example:)
    # flaglist=(X C C C)
    flaglist=(X)
    # Style for the cdm dialog, which is printed with dialog(1).
    # Default to unset, causing dialog(1) to use the system wide default.
    # See /usr/share/doc/cdm/themes for some nice choices.
    dialogrc="default"
    # Index of the first item in the menu.
    countfrom=0
    # Set default display.
    display=0
    # Where should the first X tty be spawned?
    # special value `keep' causes to run X in current tty.
    xtty="keep"
    # Should cdm(1) stick to the specified display?
    locktty=no
    # Use ConsoleKit for X session?
    consolekit=no
    # Timeout for waiting for X session to register with ConsoleKit.
    cktimeout=30
    # Additional arguments to pass to X server, which is usually called as:
    # /usr/bin/X :$display "${serverargs[@]}" vt$((xtty+display))
    # Arguments with whitespaces should be quoted or escaped.
    serverargs=(-nolisten tcp)

    bgc1954 wrote:Have you actually read the cdm wiki page?  I don't use cdm but the wiki looks straightforwared enough.
    Yes, I did.  The wiki, https://wiki.archlinux.org/index.php/CDM is asking to edit cdmrc as was recommended in the previous thread.
    To be frank, I could not understand what it means by "If you use systemd, see Systemd#Power_Management."
    https://wiki.archlinux.org/index.php/Sy … management
    I don't see  anything there.

  • [Solved] Installation of SDDM (Simple Desktop Display Manager)

    After installing the package SDDM (not the qt5 version but the qt4 one) and starting the service via systemd, I get a blank screen.
    If a try to run sddm-greeter from the terminal, I have the same.
    What am I missing ?
    I read somewhere that you need to create a user sddm and give it a specific home directory ? Shouldn't this be done by installing the package ?
    Last edited by Strider (2014-06-19 20:08:46)

    After looking in the systemd log, the problem seems as I said to be with the sddm user. It is indeed not created on my system :
    journalctl | grep sddm
    jun 18 23:46:29 Megatron sddm[724]: Initializing...
    jun 18 23:46:29 Megatron sddm[724]: Starting...
    jun 18 23:46:29 Megatron sddm[724]: Adding new display : 0 on vt 1 ...
    jun 18 23:46:29 Megatron sddm[724]: Adding cookie to "/var/lib/sddm/:0"
    jun 18 23:46:29 Megatron sddm[724]: Failed to find the sddm user. Owner of the auth file will not be changed.
    jun 18 23:46:29 Megatron sddm[724]: Display server starting...
    jun 18 23:46:29 Megatron sddm[724]: Display server started.
    jun 18 23:46:29 Megatron sddm[724]: Socket server starting...
    jun 18 23:46:29 Megatron sddm[724]: Socket server started.
    jun 18 23:46:29 Megatron sddm[724]: Unable to find the sddm user, cannot continue
    jun 18 23:47:08 Megatron sddm[724]: Signal received: SIGTERM
    jun 18 23:47:08 Megatron sddm[724]: Socket server stopping...
    jun 18 23:47:08 Megatron sddm[724]: Socket server stopped.
    jun 18 23:47:08 Megatron sddm[724]: Display server stopping...
    jun 18 23:47:08 Megatron sddm[724]: Display server stopped.
    jun 18 23:53:42 Megatron sudo[1449]: chris : TTY=pts/0 ; PWD=/home/chris ; USER=root ; COMMAND=/usr/sbin//nano /etc/sddm.conf
    jun 18 23:55:34 Megatron sudo[1454]: chris : TTY=pts/0 ; PWD=/home/chris ; USER=root ; COMMAND=/usr/sbin//nano /etc/sddm.conf
    jun 18 23:56:02 Megatron sudo[1458]: chris : TTY=pts/0 ; PWD=/home/chris ; USER=root ; COMMAND=/usr/sbin//nano /etc/sddm.conf
    jun 18 23:56:29 Megatron sudo[1460]: chris : TTY=pts/0 ; PWD=/home/chris ; USER=root ; COMMAND=/usr/sbin//sddm-greeter
    jun 18 23:59:28 Megatron sudo[1509]: chris : TTY=pts/0 ; PWD=/home/chris ; USER=root ; COMMAND=/usr/sbin//cat /usr/lib/systemd/system/sddm.service
    jun 19 00:30:11 Megatron sudo[3902]: chris : TTY=pts/0 ; PWD=/home/chris ; USER=root ; COMMAND=/usr/sbin//pacman -R sddm-git
    jun 19 00:31:47 Megatron sudo[5270]: chris : TTY=pts/0 ; PWD=/tmp/packerbuild-1003/sddm/sddm ; USER=root ; COMMAND=validate
    jun 19 00:31:47 Megatron sudo[5271]: chris : TTY=pts/0 ; PWD=/tmp/packerbuild-1003/sddm/sddm ; USER=root ; COMMAND=list /usr/sbin//pacman -U sddm-0.1.0-1-x86_64.pkg.tar.xz
    jun 19 00:31:47 Megatron sudo[5272]: chris : TTY=pts/0 ; PWD=/tmp/packerbuild-1003/sddm/sddm ; USER=root ; COMMAND=/usr/sbin//pacman -U sddm-0.1.0-1-x86_64.pkg.tar.xz

  • 'Failed to start Light Display Manager'

    Introduction removed
    I'm having some trouble with xorg, 'startx' refused to work (I have xorg-server obviously). I read symlinks and configs that are meant to be present in /etc and /usr, and I can't detect anything abnormal. I have the non-proprietary xf86-video-intel drivers installed, and I don't think any config is required on those.
    And of course, the PC won't boot directly into the OS now, with the message:
    [FAILED] Failed to start Light Display Manager.
    See 'systemctl status lightdm.service' for details.
    [OK] Reached target Graphical Interface.
    I have no way of typing into the console, and therefore logging on, when this error is present.
    Last edited by Paspie (2014-04-12 19:48:56)

    https://wiki.archlinux.org/index.php/Sy … _boot_into
    EDIT: you'd want to specify the multi-user target.  If you need help adding this to your kernel line while booting up, this would depend on which boot loader you use.  With grub legacy you'd hit 'e' on the menu screen to edit the kernel parameters.  With syslinux it is tab ... I think.  With the new grub, I'm not sure, it may still be 'e'.
    Last edited by Trilby (2014-05-27 12:08:53)

  • Installing another display manager and then rescue mode

    Hello, I proceed by this manual on wiki: https://wiki.archlinux.org/index.php/display_manager and then after reboot I got rescue mode and error:  "Failed to start default.target:Operation refused, unit may not be isolated."
    So I restored the symbolic link and it still doesnt work. Can somebody help or I have to reinstall arch?

    you could try executing
    systemctl isolate graphical.target
    If that doesn't work, try systemctl isolate multi-user.target , which should transfer you to a console login.
    edit
    re-installing is rarely needed on arch, but you may have done something wrong in setting up the display manager.
    which DM did you try to enable ?
    Last edited by Lone_Wolf (2014-04-09 11:59:38)

  • 1 Admin console to manage OSB and SOA installed on different servers

    Dear All,
    We are planning to have OSB installed on Host 1 and SOA server installed on Host 2. But there will be one Admin console to manage these 2 for the ease of maintenance. When i was trying to install this configuration I had few issues. Hope SOA experts can help me with the configuration.
    1)
    As SOA and OSB are installed on 2 different host both the servers must have weblogic installed as pre requisite. So I will have
    on host 1:
    http://host1:7001/console
    http://host1:7001/sbconsole
    On host 2:
    http://host2:7001/console (this is redundant)
    http://host2:8001/soa-infra
    2) Is it possible to inactivate http://host2:7001/console ? and add SOA server running on host2 to http://host1:7001/console. In the sense, I would like to control the SOA server from host 1.
    Issue No :2
    When I create a domain on Host 1 I just get the options for OSB and not SOA. It is obvious as SOA is not installed on Host1. but if that is the case, Is it possible to add SOA server running on host2 to host1. Is it going to be a cluster?
    Is this configuration seems realistic? Has anyone implemented. Any pointers please.
    Reagrds,
    Aani

    Hi Aani,
    Please go through the blog series -
    http://blogs.oracle.com/reynolds/2010/09/installing_an_11g_soa_cluster.html
    You may also refer EDG -
    http://download.oracle.com/docs/cd/E17904_01/core.1111/e12036/toc.htm
    Regards,
    Anuj
    Edited by: Anuj Dwivedi on Feb 23, 2011 9:14 PM

  • Oracle application display manager

    Hi all,
    Can any one provide me material for OADM.I am new to oracle application display manager.
    Thanks in advance
    Thanks
    Elias

    I had to google to find this info :-) OADM was de-supported in 1998. It was used as the presetation layer in release 10.7 and prior.
    I am not sure what you need it for - can you please elaborate :-)
    HTH
    Srini Chavali

  • Logitech F310 Gamepad only works with Display Manager [SOLVED]

    So I bought a couple Logitech F310 gamepads, for, well, gaming, and I had a hell of a time trying to get my games to respond to them. I run XMonad, and boot it directly via xinit. On a whim, I tried activating gdm and logging into a gnome session, and presto, my controllers worked. I got a bare bones xmonad session file going, and eventually switched over to lxdm just for testing purposes, and the controllers would continue to work like a charm.
    Now, I would prefer to not to have to use a display manager, though it's not a deal breaker (though they seem to introduce other problems -- now systemd hangs on shutdown when I'm using lxdm). Still, I'm curious as to what kind of an effect the mere activation of a display manager could have on the system which would cause it to properly recognize the gamepads. To be clear, without a display manager, the pads are detected, are correctly listed in /dev/input. and I can even run jstest and see that they respond well (though they seem oddly configured), but games will not recognize their existence, and so they're effectively useless.
    Any help would be appreciated.
    Last edited by alex404 (2014-04-08 21:16:07)

    It would appear that this is related to this post as well:
    https://bbs.archlinux.org/viewtopic.php?pid=1368721
    Here's a list of processes that run when I'm using LXDM, versus XMonad:
    kworker/u16:8
    kworker/6:2
    irq/46-iwlwifi
    login
    xinit
    irq/44-iwlwifi
    kworker/2:2
    kworker/2:3
    lxdm-binary
    lxdm-session
    gnome-keyring-d
    pulseaudio
    rtkit-daemon
    gconf-helper
    gconfd-2
    The modules being listed are the same. Definitely an odd problem. I'm just resorting to using LXDM for now, even though I'd rather not.

  • [SOLVED] Display manager

    I am new to Arch. I have installed Arch, X, Mate (as the DE) and Lightdm as the display manager.  Lightdm will only start in X, with the sudo lightdm command. From there, you can get into Mate.
    Mate seems to work just fine. However, it would be nice to be able to boot successfully to a display manager and then into a desktop environment.
    Before Lightdm, I had installed gdm with xfce. Gdm starts up properly but will not properly start either xfce or Mate. Gdm goes to a screen that is akin to the login screen but with nothing else. I just tried slim, which will not start up, either on boot up or from x.
    I am not sure what to post for logs on this. In any event, my computer is an old Dell Dimension 2400, with a pentium 4 processor, intel graphics and 2 gb of memory. I am not sure what log would be helpful here but, if someone could help me with my issue, it would be appreciated.
    My x-0-greeter.log reads:
    ** (process:290): WARNING **: Failed to open CK session: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.ConsoleKit was not provided by any .service files
    (lightdm-gtk-greeter:331): GLib-CRITICAL **: g_shell_parse_argv: assertion `command_line != NULL' failed
    ** (lightdm-gtk-greeter:331): WARNING **: Failed to open sessions directory: Error opening directory '/usr/share/lightdm/remote-sessions': No such file or directory
    ** (lightdm-gtk-greeter:331): WARNING **: Failed to load user image: Failed to open file '/home/allen/.face': Permission denied
    ** (lightdm-gtk-greeter:331): WARNING **: Could not get accounts property XKeyboardLayouts
    ** (lightdm-gtk-greeter:331): WARNING **: Could not get accounts property XHasMessages
    (lightdm-gtk-greeter:331): GLib-CRITICAL **: g_variant_get_type: assertion `value != NULL' failed
    (lightdm-gtk-greeter:331): GLib-CRITICAL **: g_variant_type_is_subtype_of: assertion `g_variant_type_check (type)' failed
    (lightdm-gtk-greeter:331): GLib-CRITICAL **: g_variant_get_type_string: assertion `value != NULL' failed
    ** (lightdm-gtk-greeter:331): WARNING **: Unexpected accounts property type for XHasMessages: (null)
    (lightdm-gtk-greeter:331): GLib-CRITICAL **: g_variant_unref: assertion `value != NULL' failed
    ** (lightdm-gtk-greeter:331): WARNING **: Could not get accounts property XKeyboardLayouts
    ** (lightdm-gtk-greeter:331): WARNING **: Could not get accounts property XHasMessages
    (lightdm-gtk-greeter:331): GLib-CRITICAL **: g_variant_get_type: assertion `value != NULL' failed
    (lightdm-gtk-greeter:331): GLib-CRITICAL **: g_variant_type_is_subtype_of: assertion `g_variant_type_check (type)' failed
    (lightdm-gtk-greeter:331): GLib-CRITICAL **: g_variant_get_type_string: assertion `value != NULL' failed
    ** (lightdm-gtk-greeter:331): WARNING **: Unexpected accounts property type for XHasMessages: (null)
    (lightdm-gtk-greeter:331): GLib-CRITICAL **: g_variant_unref: assertion `value != NULL' failed
    That seems to include some errors. The x-0.log reads:
    X.Org X Server 1.14.2
    Release Date: 2013-06-25
    X Protocol Version 11, Revision 0
    Build Operating System: Linux 3.9.7-1-ARCH i686
    Current Operating System: Linux archbox 3.9.9-1-ARCH #1 SMP PREEMPT Wed Jul 3 22:52:05 CEST 2013 i686
    Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=5eec6b5e-dd19-4f9d-8e3b-39b950052c48 ro quiet
    Build Date: 01 July 2013 10:52:25AM
    Current version of pixman: 0.30.0
    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: Wed Jul 24 22:13:55 2013
    (==) Using config directory: "/etc/X11/xorg.conf.d"
    Initializing built-in extension Generic Event Extension
    Initializing built-in extension SHAPE
    Initializing built-in extension MIT-SHM
    Initializing built-in extension XInputExtension
    Initializing built-in extension XTEST
    Initializing built-in extension BIG-REQUESTS
    Initializing built-in extension SYNC
    Initializing built-in extension XKEYBOARD
    Initializing built-in extension XC-MISC
    Initializing built-in extension SECURITY
    Initializing built-in extension XINERAMA
    Initializing built-in extension XFIXES
    Initializing built-in extension RENDER
    Initializing built-in extension RANDR
    Initializing built-in extension COMPOSITE
    Initializing built-in extension DAMAGE
    Initializing built-in extension MIT-SCREEN-SAVER
    Initializing built-in extension DOUBLE-BUFFER
    Initializing built-in extension RECORD
    Initializing built-in extension DPMS
    Initializing built-in extension X-Resource
    Initializing built-in extension XVideo
    Initializing built-in extension XVideo-MotionCompensation
    Initializing built-in extension XFree86-VidModeExtension
    Initializing built-in extension XFree86-DGA
    Initializing built-in extension XFree86-DRI
    Initializing built-in extension DRI2
    Loading extension GLX
    (II) AIGLX: Suspending AIGLX clients for VT switch
    setversion 1.4 failed
    The lightdm.log reads:
    [+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log
    [+0.00s] DEBUG: Starting Light Display Manager 1.6.0, UID=0 PID=532
    [+0.00s] DEBUG: Loaded configuration from /etc/lightdm/lightdm.conf
    [+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager
    [+0.00s] DEBUG: Using Xephyr for X servers
    [+0.00s] DEBUG: Registered seat module xlocal
    [+0.00s] DEBUG: Registered seat module xremote
    [+0.00s] DEBUG: Adding default seat
    [+0.00s] DEBUG: Starting seat
    [+0.00s] DEBUG: Starting new display for greeter
    [+0.00s] DEBUG: Starting local X display
    [+0.02s] DEBUG: Could not run plymouth --ping: Failed to execute child process "plymouth" (No such file or directory)
    [+0.02s] DEBUG: Using VT 7
    [+0.02s] DEBUG: Activating VT 7
    [+0.03s] DEBUG: Logging to /var/log/lightdm/x-2.log
    [+0.03s] DEBUG: Writing X server authority to /run/lightdm/root/:2
    [+0.03s] DEBUG: Launching X Server
    [+0.03s] DEBUG: Launching process 536: /usr/bin/Xephyr :2 -auth /run/lightdm/root/:2 -nolisten tcp vt7 -novtswitch
    [+0.06s] DEBUG: Waiting for ready signal from X server :2
    [+0.06s] DEBUG: Acquired bus name org.freedesktop.DisplayManager
    [+0.06s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0
    The log from slim reads:
    slim: waiting for X server to begin accepting connections.
    slim: pam_authentication(): Authentication failure
    slim: waiting for X server to shut down
    slim: waiting for X server to begin accepting connections.
    The xorg.0.log reads:
    [ 6.928]
    X.Org X Server 1.14.2
    Release Date: 2013-06-25
    [ 6.928] X Protocol Version 11, Revision 0
    [ 6.928] Build Operating System: Linux 3.9.7-1-ARCH i686
    [ 6.928] Current Operating System: Linux archbox 3.9.9-1-ARCH #1 SMP PREEMPT Wed Jul 3 22:52:05 CEST 2013 i686
    [ 6.929] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=5eec6b5e-dd19-4f9d-8e3b-39b950052c48 ro quiet
    [ 6.929] Build Date: 01 July 2013 10:52:25AM
    [ 6.929]
    [ 6.929] Current version of pixman: 0.30.0
    [ 6.929] Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    [ 6.929] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 6.929] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Jul 24 22:13:55 2013
    [ 6.958] (==) Using config directory: "/etc/X11/xorg.conf.d"
    [ 6.978] (==) No Layout section. Using the first Screen section.
    [ 6.978] (==) No screen section available. Using defaults.
    [ 6.978] (**) |-->Screen "Default Screen Section" (0)
    [ 6.978] (**) | |-->Monitor "<default monitor>"
    [ 6.985] (==) No monitor specified for screen "Default Screen Section".
    Using a default monitor configuration.
    [ 6.985] (==) Automatically adding devices
    [ 6.985] (==) Automatically enabling devices
    [ 6.985] (==) Automatically adding GPU devices
    [ 7.000] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
    [ 7.000] Entry deleted from font path.
    [ 7.000] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
    [ 7.000] Entry deleted from font path.
    [ 7.000] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
    [ 7.000] Entry deleted from font path.
    [ 7.000] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
    [ 7.000] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
    [ 7.000] Entry deleted from font path.
    [ 7.000] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
    [ 7.000] (==) FontPath set to:
    /usr/share/fonts/misc/,
    /usr/share/fonts/TTF/
    [ 7.000] (==) ModulePath set to "/usr/lib/xorg/modules"
    [ 7.000] (II) The server relies on udev to provide the list of input devices.
    If no devices become available, reconfigure udev or disable AutoAddDevices.
    [ 7.005] (II) Loader magic: 0x8258620
    [ 7.005] (II) Module ABI versions:
    [ 7.005] X.Org ANSI C Emulation: 0.4
    [ 7.005] X.Org Video Driver: 14.1
    [ 7.005] X.Org XInput driver : 19.1
    [ 7.005] X.Org Server Extension : 7.0
    [ 7.006] (II) xfree86: Adding drm device (/dev/dri/card0)
    [ 7.007] (--) PCI:*(0:0:2:0) 8086:2562:1028:0160 rev 1, Mem @ 0xe8000000/134217728, 0xfeb80000/524288
    [ 7.008] Initializing built-in extension Generic Event Extension
    [ 7.008] Initializing built-in extension SHAPE
    [ 7.008] Initializing built-in extension MIT-SHM
    [ 7.008] Initializing built-in extension XInputExtension
    [ 7.008] Initializing built-in extension XTEST
    [ 7.008] Initializing built-in extension BIG-REQUESTS
    [ 7.008] Initializing built-in extension SYNC
    [ 7.008] Initializing built-in extension XKEYBOARD
    [ 7.008] Initializing built-in extension XC-MISC
    [ 7.008] Initializing built-in extension SECURITY
    [ 7.008] Initializing built-in extension XINERAMA
    [ 7.008] Initializing built-in extension XFIXES
    [ 7.008] Initializing built-in extension RENDER
    [ 7.008] Initializing built-in extension RANDR
    [ 7.008] Initializing built-in extension COMPOSITE
    [ 7.008] Initializing built-in extension DAMAGE
    [ 7.008] Initializing built-in extension MIT-SCREEN-SAVER
    [ 7.008] Initializing built-in extension DOUBLE-BUFFER
    [ 7.008] Initializing built-in extension RECORD
    [ 7.008] Initializing built-in extension DPMS
    [ 7.008] Initializing built-in extension X-Resource
    [ 7.008] Initializing built-in extension XVideo
    [ 7.008] Initializing built-in extension XVideo-MotionCompensation
    [ 7.008] Initializing built-in extension XFree86-VidModeExtension
    [ 7.008] Initializing built-in extension XFree86-DGA
    [ 7.008] Initializing built-in extension XFree86-DRI
    [ 7.008] Initializing built-in extension DRI2
    [ 7.008] (II) LoadModule: "glx"
    [ 7.027] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    [ 7.042] (II) Module glx: vendor="X.Org Foundation"
    [ 7.042] compiled for 1.14.2, module version = 1.0.0
    [ 7.042] ABI class: X.Org Server Extension, version 7.0
    [ 7.042] (==) AIGLX enabled
    [ 7.042] Loading extension GLX
    [ 7.042] (==) Matched intel as autoconfigured driver 0
    [ 7.042] (==) Matched intel as autoconfigured driver 1
    [ 7.042] (==) Matched vesa as autoconfigured driver 2
    [ 7.042] (==) Matched modesetting as autoconfigured driver 3
    [ 7.043] (==) Matched fbdev as autoconfigured driver 4
    [ 7.043] (==) Assigned the driver to the xf86ConfigLayout
    [ 7.043] (II) LoadModule: "intel"
    [ 7.044] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
    [ 7.098] (II) Module intel: vendor="X.Org Foundation"
    [ 7.098] compiled for 1.14.2, module version = 2.21.12
    [ 7.098] Module class: X.Org Video Driver
    [ 7.098] ABI class: X.Org Video Driver, version 14.1
    [ 7.098] (II) LoadModule: "vesa"
    [ 7.098] (WW) Warning, couldn't open module vesa
    [ 7.098] (II) UnloadModule: "vesa"
    [ 7.098] (II) Unloading vesa
    [ 7.098] (EE) Failed to load module "vesa" (module does not exist, 0)
    [ 7.098] (II) LoadModule: "modesetting"
    [ 7.099] (WW) Warning, couldn't open module modesetting
    [ 7.099] (II) UnloadModule: "modesetting"
    [ 7.099] (II) Unloading modesetting
    [ 7.099] (EE) Failed to load module "modesetting" (module does not exist, 0)
    [ 7.099] (II) LoadModule: "fbdev"
    [ 7.099] (WW) Warning, couldn't open module fbdev
    [ 7.099] (II) UnloadModule: "fbdev"
    [ 7.099] (II) Unloading fbdev
    [ 7.099] (EE) Failed to load module "fbdev" (module does not exist, 0)
    [ 7.099] (II) intel: Driver for Intel Integrated Graphics Chipsets: i810,
    i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G, 915G,
    E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM, Pineview G,
    965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33, GM45,
    4 Series, G45/G43, Q45/Q43, G41, B43, B43, Clarkdale, Arrandale,
    Sandybridge Desktop (GT1), Sandybridge Desktop (GT2),
    Sandybridge Desktop (GT2+), Sandybridge Mobile (GT1),
    Sandybridge Mobile (GT2), Sandybridge Mobile (GT2+),
    Sandybridge Server, Ivybridge Mobile (GT1), Ivybridge Mobile (GT2),
    Ivybridge Desktop (GT1), Ivybridge Desktop (GT2), Ivybridge Server,
    Ivybridge Server (GT2), HD Graphics, HD Graphics 4600,
    Haswell Desktop (GT3), HD Graphics, HD Graphics 4600,
    Haswell Mobile (GT3), HD Graphics, HD Graphics P4600/P4700,
    Haswell Server (GT3), Haswell (GT1), Haswell (GT2), Haswell (GT3),
    HD Graphics, Haswell (GT2), Haswell (GT3), Haswell SDV Desktop (GT1),
    Haswell SDV Desktop (GT2), Haswell SDV Desktop (GT3),
    Haswell SDV Mobile (GT1), Haswell SDV Mobile (GT2),
    Haswell SDV Mobile (GT3), Haswell SDV Server (GT1),
    Haswell SDV Server (GT2), Haswell SDV Server (GT3),
    Haswell SDV (GT1), Haswell SDV (GT2), Haswell SDV (GT3),
    Haswell SDV (GT1), Haswell SDV (GT2), Haswell SDV (GT3),
    Haswell ULT Desktop (GT1), Haswell ULT Desktop (GT2),
    Iris(TM) Graphics 5100, HD Graphics, HD Graphics 4400,
    HD Graphics 5000, Haswell ULT Server (GT1), Haswell ULT Server (GT2),
    Iris(TM) Graphics 5100, Haswell ULT (GT1), Haswell ULT (GT2),
    Iris(TM) Graphics 5100, HD Graphics, HD Graphics 4200,
    Iris(TM) Graphics 5100, Haswell CRW Desktop (GT1), HD Graphics 4600,
    Iris(TM) Pro Graphics 5200, Haswell CRW Mobile (GT1),
    HD Graphics 4600, Iris(TM) Pro Graphics 5200,
    Haswell CRW Server (GT1), Haswell CRW Server (GT2),
    Iris(TM) Pro Graphics 5200, Haswell CRW (GT1), Haswell CRW (GT2),
    Iris(TM) Pro Graphics 5200, Haswell CRW (GT1), Haswell CRW (GT2),
    Iris(TM) Pro Graphics 5200, ValleyView PO board
    [ 7.101] (++) using VT number 7
    [ 7.101] (II) intel(0): Creating default Display subsection in Screen section
    "Default Screen Section" for depth/fbbpp 24/32
    [ 7.101] (==) intel(0): Depth 24, (--) framebuffer bpp 32
    [ 7.101] (==) intel(0): RGB weight 888
    [ 7.101] (==) intel(0): Default visual is TrueColor
    [ 7.101] (--) intel(0): Integrated Graphics Chipset: Intel(R) 845G
    [ 7.101] (**) intel(0): Relaxed fencing disabled
    [ 7.102] (**) intel(0): Wait on SwapBuffers? enabled
    [ 7.102] (**) intel(0): Triple buffering? enabled
    [ 7.102] (**) intel(0): Framebuffer tiled
    [ 7.102] (**) intel(0): Pixmaps tiled
    [ 7.102] (**) intel(0): 3D buffers tiled
    [ 7.102] (**) intel(0): SwapBuffers wait enabled
    [ 7.103] (==) intel(0): video overlay key set to 0x101fe
    [ 7.303] (II) intel(0): Output VGA1 has no monitor section
    [ 7.443] (II) intel(0): EDID for output VGA1
    [ 7.443] (II) intel(0): Manufacturer: DEL Model: 3142 Serial#: 894121267
    [ 7.443] (II) intel(0): Year: 1999 Week: 29
    [ 7.443] (II) intel(0): EDID Version: 1.2
    [ 7.443] (II) intel(0): Analog Display Input, Input Voltage Level: 0.700/0.300 V
    [ 7.443] (II) intel(0): Sync: Separate
    [ 7.443] (II) intel(0): Max Image Size [cm]: horiz.: 32 vert.: 24
    [ 7.443] (II) intel(0): Gamma: 2.27
    [ 7.443] (II) intel(0): DPMS capabilities: StandBy Suspend Off; RGB/Color Display
    [ 7.443] (II) intel(0): First detailed timing is preferred mode
    [ 7.443] (II) intel(0): redX: 0.645 redY: 0.321 greenX: 0.285 greenY: 0.600
    [ 7.443] (II) intel(0): blueX: 0.142 blueY: 0.057 whiteX: 0.283 whiteY: 0.298
    [ 7.443] (II) intel(0): Supported established timings:
    [ 7.443] (II) intel(0): 720x400@70Hz
    [ 7.443] (II) intel(0): 640x480@60Hz
    [ 7.443] (II) intel(0): 640x480@75Hz
    [ 7.443] (II) intel(0): 800x600@60Hz
    [ 7.443] (II) intel(0): 800x600@75Hz
    [ 7.443] (II) intel(0): 1024x768@60Hz
    [ 7.443] (II) intel(0): 1024x768@75Hz
    [ 7.443] (II) intel(0): 1280x1024@75Hz
    [ 7.443] (II) intel(0): Manufacturer's mask: 0
    [ 7.443] (II) intel(0): Supported standard timings:
    [ 7.443] (II) intel(0): #0: hsize: 1024 vsize 768 refresh: 85 vid: 22881
    [ 7.443] (II) intel(0): #1: hsize: 800 vsize 600 refresh: 85 vid: 22853
    [ 7.443] (II) intel(0): #2: hsize: 640 vsize 480 refresh: 85 vid: 22833
    [ 7.443] (II) intel(0): Supported detailed timing:
    [ 7.443] (II) intel(0): clock: 94.5 MHz Image Size: 306 x 230 mm
    [ 7.444] (II) intel(0): h_active: 1024 h_sync: 1072 h_sync_end 1168 h_blank_end 1376 h_border: 0
    [ 7.444] (II) intel(0): v_active: 768 v_sync: 769 v_sync_end 772 v_blanking: 808 v_border: 0
    [ 7.444] (II) intel(0): Serial No: 5322DE5K5379
    [ 7.444] (II) intel(0): Monitor name: DELL M780
    [ 7.444] (II) intel(0): Ranges: V min: 50 V max: 160 Hz, H min: 30 H max: 85 kHz,
    [ 7.444] (II) intel(0): EDID (in hex):
    [ 7.444] (II) intel(0): 00ffffffffffff0010ac423133354b35
    [ 7.444] (II) intel(0): 1d0901020820187fea1269a552499924
    [ 7.444] (II) intel(0): 0e484ca54b0061594559315901010101
    [ 7.444] (II) intel(0): 010101010101ea240060410028303060
    [ 7.444] (II) intel(0): 130032e61000001e000000ff00353332
    [ 7.444] (II) intel(0): 324445354b353337390a000000fc0044
    [ 7.444] (II) intel(0): 454c4c204d3738300a202020000000fd
    [ 7.444] (II) intel(0): 0032a01e55ff000a20202020202000e3
    [ 7.444] (II) intel(0): Printing probed modes for output VGA1
    [ 7.444] (II) intel(0): Modeline "1024x768"x85.0 94.50 1024 1072 1168 1376 768 769 772 808 +hsync +vsync (68.7 kHz eP)
    [ 7.444] (II) intel(0): Modeline "1280x1024"x75.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
    [ 7.444] (II) intel(0): Modeline "1024x768"x75.1 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.1 kHz e)
    [ 7.444] (II) intel(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 7.444] (II) intel(0): Modeline "800x600"x85.1 56.25 800 832 896 1048 600 601 604 631 +hsync +vsync (53.7 kHz e)
    [ 7.444] (II) intel(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
    [ 7.444] (II) intel(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 7.444] (II) intel(0): Modeline "640x480"x85.0 36.00 640 696 752 832 480 481 484 509 -hsync -vsync (43.3 kHz e)
    [ 7.444] (II) intel(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
    [ 7.444] (II) intel(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 7.444] (II) intel(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
    [ 7.444] (II) intel(0): Output VGA1 connected
    [ 7.444] (II) intel(0): Using exact sizes for initial modes
    [ 7.444] (II) intel(0): Output VGA1 using initial mode 1024x768
    [ 7.444] (II) intel(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
    [ 7.444] (II) intel(0): Kernel page flipping support detected, enabling
    [ 7.444] (==) intel(0): DPI set to (96, 96)
    [ 7.444] (II) Loading sub module "fb"
    [ 7.444] (II) LoadModule: "fb"
    [ 7.444] (II) Loading /usr/lib/xorg/modules/libfb.so
    [ 7.458] (II) Module fb: vendor="X.Org Foundation"
    [ 7.458] compiled for 1.14.2, module version = 1.0.0
    [ 7.458] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 7.458] (II) Loading sub module "dri2"
    [ 7.458] (II) LoadModule: "dri2"
    [ 7.458] (II) Module "dri2" already built-in
    [ 7.458] (==) Depth 24 pixmap format is 32 bpp
    [ 7.466] (II) intel(0): [DRI2] Setup complete
    [ 7.466] (II) intel(0): [DRI2] DRI driver: i915
    [ 7.466] (II) intel(0): Allocated new frame buffer 1024x768 stride 4096, tiled
    [ 7.478] (II) UXA(0): Driver registered support for the following operations:
    [ 7.478] (II) solid
    [ 7.478] (II) copy
    [ 7.478] (II) composite (RENDER acceleration)
    [ 7.478] (II) put_image
    [ 7.478] (II) get_image
    [ 7.478] (==) intel(0): Backing store disabled
    [ 7.478] (==) intel(0): Silken mouse enabled
    [ 7.478] (II) intel(0): Initializing HW Cursor
    [ 7.478] (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
    [ 7.480] (==) intel(0): DPMS enabled
    [ 7.480] (==) intel(0): Intel XvMC decoder disabled
    [ 7.480] (II) intel(0): Set up overlay video
    [ 7.480] (II) intel(0): direct rendering: DRI2 Enabled
    [ 7.480] (==) intel(0): hotplug detection: "enabled"
    [ 7.540] (--) RandR disabled
    [ 7.689] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
    [ 7.689] (II) AIGLX: enabled GLX_INTEL_swap_event
    [ 7.689] (II) AIGLX: enabled GLX_ARB_create_context
    [ 7.689] (II) AIGLX: enabled GLX_ARB_create_context_profile
    [ 7.689] (II) AIGLX: enabled GLX_EXT_create_context_es2_profile
    [ 7.689] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
    [ 7.689] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
    [ 7.689] (II) AIGLX: Loaded and initialized i915
    [ 7.689] (II) GLX: Initialized DRI2 GL provider for screen 0
    [ 7.690] (II) intel(0): Setting screen physical size to 270 x 203
    [ 7.924] (II) config/udev: Adding input device Power Button (/dev/input/event3)
    [ 7.924] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 7.924] (II) LoadModule: "evdev"
    [ 7.925] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [ 7.943] (II) Module evdev: vendor="X.Org Foundation"
    [ 7.943] compiled for 1.14.2, module version = 2.8.1
    [ 7.943] Module class: X.Org XInput Driver
    [ 7.943] ABI class: X.Org XInput driver, version 19.1
    [ 7.943] (II) Using input driver 'evdev' for 'Power Button'
    [ 7.943] (**) Power Button: always reports core events
    [ 7.943] (**) evdev: Power Button: Device: "/dev/input/event3"
    [ 7.943] (--) evdev: Power Button: Vendor 0 Product 0x1
    [ 7.943] (--) evdev: Power Button: Found keys
    [ 7.943] (II) evdev: Power Button: Configuring as keyboard
    [ 7.943] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3/event3"
    [ 7.943] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
    [ 7.943] (**) Option "xkb_rules" "evdev"
    [ 7.943] (**) Option "xkb_model" "pc104"
    [ 7.943] (**) Option "xkb_layout" "us"
    [ 7.980] (II) config/udev: Adding input device Power Button (/dev/input/event2)
    [ 7.980] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 7.980] (II) Using input driver 'evdev' for 'Power Button'
    [ 7.980] (**) Power Button: always reports core events
    [ 7.980] (**) evdev: Power Button: Device: "/dev/input/event2"
    [ 7.980] (--) evdev: Power Button: Vendor 0 Product 0x1
    [ 7.980] (--) evdev: Power Button: Found keys
    [ 7.980] (II) evdev: Power Button: Configuring as keyboard
    [ 7.981] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input2/event2"
    [ 7.981] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
    [ 7.981] (**) Option "xkb_rules" "evdev"
    [ 7.981] (**) Option "xkb_model" "pc104"
    [ 7.981] (**) Option "xkb_layout" "us"
    [ 7.981] (II) config/udev: Adding drm device (/dev/dri/card0)
    [ 7.982] (II) config/udev: Adding input device OM (/dev/input/event1)
    [ 7.982] (**) OM: Applying InputClass "evdev pointer catchall"
    [ 7.982] (II) Using input driver 'evdev' for 'OM'
    [ 7.982] (**) OM: always reports core events
    [ 7.982] (**) evdev: OM: Device: "/dev/input/event1"
    [ 7.982] (--) evdev: OM: Vendor 0x4f3 Product 0x232
    [ 7.982] (--) evdev: OM: Found 3 mouse buttons
    [ 7.982] (--) evdev: OM: Found scroll wheel(s)
    [ 7.982] (--) evdev: OM: Found relative axes
    [ 7.982] (--) evdev: OM: Found x and y relative axes
    [ 7.982] (II) evdev: OM: Configuring as mouse
    [ 7.982] (II) evdev: OM: Adding scrollwheel support
    [ 7.982] (**) evdev: OM: YAxisMapping: buttons 4 and 5
    [ 7.982] (**) evdev: OM: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [ 7.982] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.1/usb2/2-2/2-2:1.0/input/input1/event1"
    [ 7.982] (II) XINPUT: Adding extended input device "OM" (type: MOUSE, id 8)
    [ 7.982] (II) evdev: OM: initialized for relative axes.
    [ 7.983] (**) OM: (accel) keeping acceleration scheme 1
    [ 7.983] (**) OM: (accel) acceleration profile 0
    [ 7.983] (**) OM: (accel) acceleration factor: 2.000
    [ 7.983] (**) OM: (accel) acceleration threshold: 4
    [ 7.983] (II) config/udev: Adding input device OM (/dev/input/mouse0)
    [ 7.983] (II) No input driver specified, ignoring this device.
    [ 7.983] (II) This device may have been added with another device file.
    [ 7.984] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
    [ 7.984] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
    [ 7.984] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
    [ 7.984] (**) AT Translated Set 2 keyboard: always reports core events
    [ 7.984] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event0"
    [ 7.984] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
    [ 7.984] (--) evdev: AT Translated Set 2 keyboard: Found keys
    [ 7.984] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
    [ 7.984] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
    [ 7.984] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 9)
    [ 7.984] (**) Option "xkb_rules" "evdev"
    [ 7.984] (**) Option "xkb_model" "pc104"
    [ 7.984] (**) Option "xkb_layout" "us"
    [ 7.985] (II) config/udev: Adding input device PC Speaker (/dev/input/event4)
    [ 7.985] (II) No input driver specified, ignoring this device.
    [ 7.985] (II) This device may have been added with another device file.
    [ 29.826] (II) AIGLX: Suspending AIGLX clients for VT switch
    [ 53.275] (II) AIGLX: Resuming AIGLX clients after VT switch
    [ 53.426] (II) intel(0): EDID vendor "DEL", prod id 12610
    [ 53.427] (II) intel(0): Using EDID range info for horizontal sync
    [ 53.427] (II) intel(0): Using EDID range info for vertical refresh
    [ 53.427] (II) intel(0): Printing DDC gathered Modelines:
    [ 53.427] (II) intel(0): Modeline "1024x768"x0.0 94.50 1024 1072 1168 1376 768 769 772 808 +hsync +vsync (68.7 kHz eP)
    [ 53.427] (II) intel(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 53.427] (II) intel(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
    [ 53.427] (II) intel(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 53.427] (II) intel(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
    [ 53.427] (II) intel(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
    [ 53.427] (II) intel(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
    [ 53.427] (II) intel(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 53.427] (II) intel(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
    [ 53.427] (II) intel(0): Modeline "800x600"x0.0 56.25 800 832 896 1048 600 601 604 631 +hsync +vsync (53.7 kHz e)
    [ 53.427] (II) intel(0): Modeline "640x480"x0.0 36.00 640 696 752 832 480 481 484 509 -hsync -vsync (43.3 kHz e)
    [ 53.433] setversion 1.4 failed
    [ 57.450] (II) intel(0): EDID vendor "DEL", prod id 12610
    [ 57.450] (II) intel(0): Using hsync ranges from config file
    [ 57.450] (II) intel(0): Using vrefresh ranges from config file
    [ 57.450] (II) intel(0): Printing DDC gathered Modelines:
    [ 57.450] (II) intel(0): Modeline "1024x768"x0.0 94.50 1024 1072 1168 1376 768 769 772 808 +hsync +vsync (68.7 kHz eP)
    [ 57.450] (II) intel(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 57.450] (II) intel(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
    [ 57.450] (II) intel(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 57.450] (II) intel(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
    [ 57.450] (II) intel(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
    [ 57.450] (II) intel(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
    [ 57.450] (II) intel(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 57.450] (II) intel(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
    [ 57.450] (II) intel(0): Modeline "800x600"x0.0 56.25 800 832 896 1048 600 601 604 631 +hsync +vsync (53.7 kHz e)
    [ 57.450] (II) intel(0): Modeline "640x480"x0.0 36.00 640 696 752 832 480 481 484 509 -hsync -vsync (43.3 kHz e)
    [ 57.590] (II) intel(0): EDID vendor "DEL", prod id 12610
    [ 57.590] (II) intel(0): Using hsync ranges from config file
    [ 57.590] (II) intel(0): Using vrefresh ranges from config file
    [ 57.590] (II) intel(0): Printing DDC gathered Modelines:
    [ 57.590] (II) intel(0): Modeline "1024x768"x0.0 94.50 1024 1072 1168 1376 768 769 772 808 +hsync +vsync (68.7 kHz eP)
    [ 57.590] (II) intel(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 57.590] (II) intel(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
    [ 57.590] (II) intel(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 57.590] (II) intel(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
    [ 57.590] (II) intel(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
    [ 57.590] (II) intel(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
    [ 57.590] (II) intel(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 57.590] (II) intel(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
    [ 57.590] (II) intel(0): Modeline "800x600"x0.0 56.25 800 832 896 1048 600 601 604 631 +hsync +vsync (53.7 kHz e)
    [ 57.590] (II) intel(0): Modeline "640x480"x0.0 36.00 640 696 752 832 480 481 484 509 -hsync -vsync (43.3 kHz e)
    [ 57.763] (II) intel(0): EDID vendor "DEL", prod id 12610
    [ 57.763] (II) intel(0): Using hsync ranges from config file
    [ 57.763] (II) intel(0): Using vrefresh ranges from config file
    [ 57.763] (II) intel(0): Printing DDC gathered Modelines:
    [ 57.763] (II) intel(0): Modeline "1024x768"x0.0 94.50 1024 1072 1168 1376 768 769 772 808 +hsync +vsync (68.7 kHz eP)
    [ 57.763] (II) intel(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 57.763] (II) intel(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
    [ 57.763] (II) intel(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 57.763] (II) intel(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
    [ 57.763] (II) intel(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
    [ 57.763] (II) intel(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
    [ 57.763] (II) intel(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 57.763] (II) intel(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
    [ 57.763] (II) intel(0): Modeline "800x600"x0.0 56.25 800 832 896 1048 600 601 604 631 +hsync +vsync (53.7 kHz e)
    [ 57.763] (II) intel(0): Modeline "640x480"x0.0 36.00 640 696 752 832 480 481 484 509 -hsync -vsync (43.3 kHz e)
    [ 57.903] (II) intel(0): EDID vendor "DEL", prod id 12610
    [ 57.903] (II) intel(0): Using hsync ranges from config file
    [ 57.903] (II) intel(0): Using vrefresh ranges from config file
    [ 57.903] (II) intel(0): Printing DDC gathered Modelines:
    [ 57.903] (II) intel(0): Modeline "1024x768"x0.0 94.50 1024 1072 1168 1376 768 769 772 808 +hsync +vsync (68.7 kHz eP)
    [ 57.903] (II) intel(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [ 57.903] (II) intel(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
    [ 57.903] (II) intel(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [ 57.903] (II) intel(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
    [ 57.903] (II) intel(0): Modeline "1280x1024"x0.0 135.00 1280 1296 1440 1688 1024 1025 1028 1066 +hsync +vsync (80.0 kHz e)
    [ 57.903] (II) intel(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
    [ 57.903] (II) intel(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [ 57.903] (II) intel(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
    [ 57.903] (II) intel(0): Modeline "800x600"x0.0 56.25 800 832 896 1048 600 601 604 631 +hsync +vsync (53.7 kHz e)
    [ 57.903] (II) intel(0): Modeline "640x480"x0.0 36.00 640 696 752 832 480 481 484 509 -hsync -vsync (43.3 kHz e)
    No doubt I have missed the pertinent log.
    Last edited by nef131 (2013-07-31 12:47:23)

    Oxyd,
    The current state of things, after removing gdm, slim and reinstalling lightdm, is that nothing has changed. In any event, below is the results of pacman -Qs lightdm:
    [allen@archbox ~]$ pacman -Qs lightdm
    local/lightdm 1:1.6.0-5 (lightdm)
    A lightweight display manager
    local/lightdm-gtk3-greeter 1:1.6.0-1
    GTK+ greeter for LightDM
    [allen@archbox ~]$
    The result of is cat /etc/lightdm/lightdm.conf:
    [allen@archbox ~]$ cat /etc/lightdm/lightdm.conf
    # General configuration
    # start-default-seat = True to always start one seat if none are defined in the configuration
    # greeter-user = User to run greeter as
    # minimum-display-number = Minimum display number to use for X servers
    # minimum-vt = First VT to run displays on
    # lock-memory = True to prevent memory from being paged to disk
    # user-authority-in-system-dir = True if session authority should be in the system location
    # guest-account-script = Script to be run to setup guest account
    # log-directory = Directory to log information to
    # run-directory = Directory to put running state in
    # cache-directory = Directory to cache to
    # xsessions-directory = Directory to find X sessions
    # remote-sessions-directory = Directory to find remote sessions
    # xgreeters-directory = Directory to find X greeters
    [LightDM]
    #start-default-seat=true
    #greeter-user=lightdm
    #minimum-display-number=0
    #minimum-vt=7
    #lock-memory=true
    #user-authority-in-system-dir=false
    #guest-account-script=guest-account
    #log-directory=/var/log/lightdm
    run-directory=/run/lightdm
    #cache-directory=/var/cache/lightdm
    #xsessions-directory=/usr/share/xsessions
    #remote-sessions-directory=/usr/share/lightdm/remote-sessions
    #xgreeters-directory=/usr/share/xgreeters
    # Seat defaults
    # type = Seat type (xlocal, xremote)
    # xserver-command = X server command to run (can also contain arguments e.g. X -special-option)
    # xserver-layout = Layout to pass to X server
    # xserver-config = Config file to pass to X server
    # xserver-allow-tcp = True if TCP/IP connections are allowed to this X server
    # xdmcp-manager = XDMCP manager to connect to (implies xserver-allow-tcp=true)
    # xdmcp-port = XDMCP UDP/IP port to communicate on
    # xdmcp-key = Authentication key to use for XDM-AUTHENTICATION-1 (stored in keys.conf)
    # greeter-session = Session to load for greeter
    # greeter-hide-users = True to hide the user list
    # greeter-allow-guest = True if the greeter should show a guest login option
    # greeter-show-manual-login = True if the greeter should offer a manual login option
    # greeter-show-remote-login = True if the greeter should offer a remote login option
    # user-session = Session to load for users
    # allow-guest = True if guest login is allowed
    # guest-session = Session to load for guests (overrides user-session)
    # session-wrapper = Wrapper script to run session with
    # display-setup-script = Script to run when starting a greeter session (runs as root)
    # greeter-setup-script = Script to run when starting a greeter (runs as root)
    # session-setup-script = Script to run when starting a user session (runs as root)
    # session-cleanup-script = Script to run when quitting a user session (runs as root)
    # autologin-guest = True to log in as guest by default
    # autologin-user = User to log in with by default (overrides autologin-guest)
    # autologin-user-timeout = Number of seconds to wait before loading default user
    # autologin-session = Session to load for automatic login (overrides user-session)
    # exit-on-failure = True if the daemon should exit if this seat fails
    [SeatDefaults]
    #type=xlocal
    #xserver-command=X
    #xserver-layout=
    #xserver-config=
    #xserver-allow-tcp=false
    #xdmcp-manager=
    #xdmcp-port=177
    #xdmcp-key=
    #greeter-session=example-gtk-gnome
    #greeter-hide-users=false
    #greeter-allow-guest=true
    #greeter-show-manual-login=false
    #greeter-show-remote-login=true
    #user-session=default
    #allow-guest=true
    #guest-session=UNIMPLEMENTED
    session-wrapper=/etc/lightdm/xsession
    #display-setup-script=
    #greeter-setup-script=
    #session-setup-script=
    #session-cleanup-script=
    #autologin-guest=false
    #autologin-user=
    #autologin-user-timeout=0
    #autologin-session=UNIMPLEMENTED
    pam-service=lightdm-autologin
    #exit-on-failure=false
    # Seat configuration
    # Each seat must start with "Seat:".
    # Uses settings from [SeatDefaults], any of these can be overriden by setting them in this section.
    #[Seat:0]
    # XDMCP Server configuration
    # enabled = True if XDMCP connections should be allowed
    # port = UDP/IP port to listen for connections on
    # key = Authentication key to use for XDM-AUTHENTICATION-1 or blank to not use authentication (stored in keys.conf)
    # The authentication key is a 56 bit DES key specified in hex as 0xnnnnnnnnnnnnnn. Alternatively
    # it can be a word and the first 7 characters are used as the key.
    [XDMCPServer]
    #enabled=false
    #port=177
    #key=
    # VNC Server configuration
    # enabled = True if VNC connections should be allowed
    # command = Command to run Xvnc server with
    # port = TCP/IP port to listen for connections on
    # width = Width of display to use
    # height = Height of display to use
    # depth = Color depth of display to use
    [VNCServer]
    #enabled=false
    #command=Xvnc
    #port=5900
    #width=1024
    #height=768
    #depth=8
    The result of cat /etc/lightdm/lightdm-gtk-greeter.conf is :
    [allen@archbox ~]$ cat /etc/lightdm/lightdm-gtk-greeter.conf
    # background = Background file to use, either an image path or a color (e.g. #772953)
    # theme-name = GTK+ theme to use
    # icon-theme-name = Icon theme to use
    # font-name = Font to use
    # xft-antialias = Whether to antialias Xft fonts (true or false)
    # xft-dpi = Resolution for Xft in dots per inch (e.g. 96)
    # xft-hintstyle = What degree of hinting to use (none, slight, medium, or full)
    # xft-rgba = Type of subpixel antialiasing (none, rgb, bgr, vrgb or vbgr)
    # show-language-selector (true or false)
    # show-indicators = semi-colon ";" separated list of allowed indicator modules (e.g. libsoundmenu.so)
    # show-clock (true or false)
    # clock-format = strftime-format string, e.g. %H:%M
    # keyboard = command to launch on-screen keyboard
    [greeter]
    #background=
    #theme-name=
    #icon-theme-name=
    #font-name=
    #xft-antialias=
    #xft-dpi=
    #xft-hintstyle=
    #xft-rgba=
    #show-language-selector=
    #show-indicators=
    #show-clock=
    #clock-format=
    #keyboard=
    Cfr: "Did you test X following the Beginners' Guide?"
    Yes. I tested X. I believe that I followed the Beginner's Guide to the letter. Of course, I am new to Arch, so it is possible I misunderstood something. I believe what I did was to enter the following command to install X: pacman -S xorg-server xorg-server-utils xorg-xinit and then, as provided in the guide, I installed mesa.
    I have, per your suggestion, removed xorg-server-xephyr. I note, however, that the guide for installing lightdm indicates that the package should be installed initially, in order to test to see if lightdm works. In any event, removing it does not alter how the system starts up.
    You are correct that I am starting the computer directly to lightdm - and not starting lightdm from X - but lightdm leaves a blank page, as I noted. I can click around on the blank page and stuff pops up. On looking at Oxyd's suggested outputs, I wonder if my problem is that nearly everything in the configuration file has been commented out.

  • Wrong display manager resolution

    Hi!
    I installed Arch with LXDE as desktop environment and LXDM as display manager (as I did on two other machines before with perfect result).
    Strangely enough, on this machine the screen resolution was not set automatically to the monitor's default (I am using the xf86-video-nouveau driver for my mx440 nvidia card). But chosing "default" in LXDE for the resolution changed it successfully from 1024x768 to 1680x1050 (so the native screen resolution is recognized, if not set, automatically). But LXDM or rather its login screen still comes in 1024x768 and looks aweful.
    I suspected an Xorg issue and changed the 10-monitor.conf as proposed in the Xorg Arch wiki to my desired resolution. But that does not have any effect on LXDM's login screen.
    Any ideas what might be wrong? Thanks
    Best

    Back up the file somewhere, then you should remove the comments (everything after the "#" symbol, including the "#" itself), and remove the pseudo-mode (the "Modes" line). You don't need it. Xorg will set your desktop to the native resolution based on your monitor's EDID information.
    This is my 10-monitor.conf:
    Section "Monitor"
    Identifier "Monitor0"
    VendorName "DELL"
    ModelName "U2311H"
    HorizSync 30.0 - 83.0
    VertRefresh 56.0 - 76.0
    Option "DPMS"
    EndSection
    Section "Device"
    Identifier "Device0"
    Driver "nouveau"
    VendorName "NVIDIA Corporation"
    EndSection
    Section "Screen"
    Identifier "Screen0"
    Device "Device0"
    Monitor "Monitor0"
    DefaultDepth 24
    SubSection "Display"
    Depth 24
    EndSubSection
    EndSection
    Is there any reason you want 16 bit colour depth? See: https://wiki.archlinux.org/index.php/FA … a_video.3F

  • Gnome-Shell logs in as Gnome Display Manager

    Hello,
    My gnome-shell decided to crap out on me after working perfectly for the past few days. It wouldn't boot into the session even with extensions off. I tried everything(removing old configuration files, setting an autostart on Gnome-shell in ~/.config/autostart. Now my Gnome-shell starts but it logs in as Gnome Display Manager. Terminals do not start up(they come up and dissapear). I can't log in to XFCE anymore as a fallback because GDM autostarts into itself. I tried switching display managers to slim but it errors starting in there also.
    This behavior happened after a symlinked a file but I'm not sure which. The page I was browsing it on was on my other user.
    Thanks, I am really bummed that I can't even get into my XFCE session right now and this GDM as user is nearly unuseable.
    Edit: https://bbs.archlinux.org/viewtopic.php?id=118651
    #3 is the post I followed, will try to remove the sym link and see what happens.
    Last edited by 6msj (2011-10-26 18:55:36)

    Looks like removing the sym link did it, but now my previews are screwed up.
    http://dl.dropbox.com/u/11400324/Screen … 0%3A09.png

  • Brief about Console, data manager and Import manager

    Hi,
    Iam new to MDM we just started installing our MDM components and iam a MM functional guy Can you any one tell me about console, data manager and import manger i need to know the following,
    1. what is it
    2. How the 3 is interlinked
    3. can the data manager be loaded directly without a import
    4. is there a std way of creating repository
    5. I need to do samples on vendor, customer harmonisation and the spend analysis and matl master harmonisation..
    Iam asking too much in this forum but i knw you guys are there to help me out.
    Thanks in advance,
    Suresh

    MDM Console
    The MDM Console allows the system manager to administer and monitor the MDM Server, and to create, maintain the structure of, and control access to the MDM repositories themselves. Records are not entered or managed with the MDM Console, but rather with client apps such as the MDM Client.
    MDM Client(data manager)
    The MDM Client is the primary client of the MDM Server, and is the program most users see on their PCs. It allows users to store, manage and update master data consisting of text, images, and other rich content, and to create taxonomies, families, and relationships. Other clients include the Import Manager, the Image Manager, and the Syndicator.
    Import Manager
    Allows you to import master data from most types of flat or relational electronic
    source files (e.g. Excel, delimited text, SQL, XML, and any ODBC-compliant source),
    and to restructure, cleanse, and normalize master data as part of the import process.
    <i>2. How the 3 is interlinked</i>
    --->
    Suppose you are sending vendor information to MDM repository be sending IDOC from R/3. Then the whole process can go as... IDOC will be sent to XI, so XI will generate XML file that contains data. Then import manager can import this file and will so place the data in repository.
    Now if you want to send data in MDM repository, the process goes reverse way. Syndicator will generate flat/xml file. This file will be given to XI so that XI will generate IDOC out of it and will send it to XI. This whole process ensures data consistancy
    For details refer this link
    http://help.sap.com/saphelp_mdm550/helpdata/en/43/D7AED5058201B4E10000000A11466F/frameset.htm

  • Slim display manager & twinview

    Hello,
    Does anybody know how to get the Slim display manager to only display on one monitor instead of stretching across both? Other display managers put the login screen on one monitor and the background on the other. Slim stretches it across both by default, putting the login box right in the middle of the two screens, kind of annoying.
    Using a nvidia card with twinview...
    Thanks for the help,
    Nate

    Slim doesn't support twinview yet, although this feature is considered for future releases, AFAIK.  You can see the feature request and the slim devs answer here:
    http://developer.berlios.de/bugs/?func= … up_id=2663
    I use GDM on my twinview setup and slim on my laptop at the moment.

  • [New package] Pywinery, a simple wine-prefix manager

    Hello world!
    I have just uploaded my first package , It's an application that I find very useful,especially when using different prefixes for different apps.
    PyWinery is a graphical and simple wine-prefix manager which allows you to launch apps and manage configuration of separate prefixes, also have a button to open winetricks in the same prefix, also have buttons to open prefix dir, winecfg, application uninstaller and wineDOS. I recommend using winetricks by default to open. exe files, so you can choose between any wine configuration you have.
    I sent an email to the developer to discuss the integration with python 3 (now the package depends on Python2) and adding the possibility to choose between wine32 and wine64 as the arch package of wine let us.
    I'd love to hear from you any suggestions on the PKGBUILD

    Hi, any progress on this?
    I am using Arch linux (updated to the latest repository snapshot), the DE is LXDE, WM: Compiz.
    This is the error the I am getting:
    [dir2cas@X41 ~]> pywinery
    Traceback (most recent call last):
    File "/usr/bin/pywinery", line 727, in <module>
    app = Main(sys_argv)
    File "/usr/bin/pywinery", line 267, in __init__
    iconview.set_model(getTools())
    File "/usr/bin/pywinery", line 166, in getTools
    (theme.load_icon(tools[i][0], 24, 0), i,
    glib.GError: Icon 'wine-uninstaller' not present in theme
    Last edited by dir2cas (2011-07-14 09:40:33)

Maybe you are looking for

  • How can I test if a given DisplayObject is obscured by any other DisplayObject on the same stage?

    I'm trying to write a function     internal function isObscured(o: DisplayObject, p: DisplayObject): Boolean; which tells whether the given object o is partially or completely obscured by the object p. I already tried using hitTestObject and hitTestP

  • Have Multiple monitor problem

    I dont know why but my second video card will not configure and work. It is a pci bus dual head ATI card and the other card is a dual head MSI Nvidia 8600GT Pcie card. The pcie card works fine by itself but the ati card causes system crash on boot af

  • Button Link Transitions with Audio?

    Ive got a question on what can be used as a Button Transition. I have a 10 sec. AV in PP2, that I want to use. In general, no problems. Ive Exported the Video to DV-AVI (silent), and it works beautifully. I only have to do a blend from the Menu for t

  • MMS "OFF" feature disabled or not working in OS 4.0?!?

    Anyone else experiencing this issue? I live in Vancouver Canada, & routinely travel to the USA, however I don't like the HUGE AT&T roaming bill for text messages so I usually just TURN OFF the MMS feature in my GENERAL settings. I did this today afte

  • URGENT HELP: procedure exit

    Hi All I have the following presssing problem. I am running a program where I require users to enter input. When they click on a button certain actions are performed. If the input is incorrect a NumberFormatException is thrown. This is fine since I h