GNOME 3.10 Startup Applications

I have a lot of commands specified in the Startup Applications program of GNOME, or gnome-session-properties. These commands execute whenever I start a GNOME session. However, after I upgraded today to GNOME 3.10, these startup applications aren't being executed. How can I fix this?

aport wrote:
Texas wrote:
gsingh93 wrote: However, after I upgraded today to GNOME 3.10...
This update seems to have caused issues in several applications according to numerous forum posts.  Deadbeef is one.  Guayadeque as well?  Others?
What is wrong with DeadBeef? It's working as awesomely as usual for me on 3.10.
edit: Oh, it's not. It segfaults when I go to Preferences. Nice!
Well gtk3 has been updated so why don't you try a rebuild?

Similar Messages

  • Mpd and gnome startup applications [SOLVED]

    i am using mpd as a regular user (i couldnt get the permissions right when trying to follow the wiki's instructions)
    so to start mpd i must execute:
    mpd ~/.mpd/config
    however, that doesnt work when pasted into gnome's startup applications, it also doesnt work when put under Exec= in a .desktop entry.
    how can i make this executable so i dont have to type it? i'd rather not put it in .xinitrc
    thanks.
    Last edited by originalsurfmex (2010-02-04 17:43:01)

    THANKS! the
    bash -c "mpd ~/.mpd/config"
    worked great.  i just put it in gnome startup applications.

  • Startup application doesn't start on cRIO (work fine on the target with LV RT)

    Hello!
    I have a application (running on a cRIO-9075) that is communicating with a GPS via RS-323 (using NI-9870).
    I can run the code without problems with LabVIEW RT on the target but when I build the executable and setting it up to run at startup it doesn't run.
    If I remove the GPS code, the startup application will run fine. As soon as I put back the GPS code, it will not... I see that looking at a Heartbeat shared variable (no heartbeat when the GPS code is there). Also, the startup application will not run if the GPS code is there even if that code is disabled...
    I have attached a screenshot of the code and one of the software installed on the cRIO for more clarity.
    I'm using LabVIEW 2011.
    Thanks in advance!
    Vincent
    Attachments:
    GPS Code.PNG ‏10 KB
    Software on cRIO.PNG ‏22 KB

    Hello,
    Sorry for the late response.
    I was able to make the application work for some time and for an unknown reason, it's not starting anymore. I made a change in the code and the problem is now back.
    The code still work as expected when launched using LabVIEW (arrow button).
    The output from the console is attached to this message, everything seems fine to me but maybe I'm missing something.
    I've looked at my code and I can't find any unreachable code (case structure or disable structure).
    I don't know if it might be related but I'm also getting the famous 1502 error (cannot save bad VI without block diagram) so I have to enable debugging to be able to build my application (which doesn't start afterwards).
    Any ideas?
    Thanks
    Vincent
    Attachments:
    App_NOT_Starting_Correctly.txt ‏3 KB

  • BP-Search as Startup Application in CRM Webclient?

    Hi folks,
    do you have any idea if it is possible not change the startup-page in CRM 7.0.
    We want to design a basic business role that can only search accounts.
    So it would be nice that after login the bupa-search will be displayed right away.
    In the technical profile I found a field for startup-application and start-page but I don't know how to use this.
    Best regards
    Stefan

    Hi Stefan
    have you found a solution for your issue?
    I have the very same problem.
    Thank you
    Pierluigi

  • Gnome menu has no applications

    So, the gnome menu has no applications. I've never had this problem before.
    Here's a picture, so you know what I mean:

    I'm not a gnome guy, but have you tried https://bbs.archlinux.org/viewtopic.php?id=127651 ?

  • The connecting of a different project to the target interferes with the startup application setting

    Hi folk,
    I have developed an application that runs on a WSN gateway 9792 and accesses the nodes dynamically. The application is compiled and deployed as startup application. Everything works fine and the application starts on boot.
    Now, I am trying to test the effects of different settings of the nodes, for that I have created a new project on which I have added the gateway with all the nodes of the compiled application.
    Step 1
    As I connect to the target, a pop up windows opens to resolve the conflict due to the presence of a running application. On the windows I press OK and all VIs on the target are closed, and the connection is applied and deployed.
    Without other actions on the target or nodes, I disconnect and reboot the WSN gateway 9792.
    The real-time application installed on the gateway, as startup application, does not starts on boot !!!
    Step 2
    If I do the following:
    - open the project who belongs the real-time application;
    - connect and disconnect the gateway (without actively deploy the code);
    - and reboot,
    this time, the real-time application, installed on the gateway, starts on boot.
    How I have to operate to have the real-time application running on the end of Step 1, without have to perform Step 2?
    Thanks,
    Asper

    Hi,
    these links could help you.
    http://digital.ni.com/public.nsf/allkb/8B0772F1E926C55D86256EE900778BDE?OpenDocument
    http://digital.ni.com/public.nsf/allkb/B37FA04A1CB84B6C862571A30060EF03?OpenDocument
    Best regards,
    Enzo 

  • Gnome System Settings and Applications Icons Disappeared

    Some icons of gnome system settings and Applications disappeared after i reinstalled gnome.
    Last edited by j0c1323 (2011-09-29 16:51:28)

    I installed the catalyst-driver yesterday on my HTPC and in the gnome systems settings i see "Graphics: VESA: WRESTLER", so it seems to be normal.

  • JDS and Gnome start, but all applications become fixed in upper left hand

    Problem:
    Java Desktop and Gnome start, but all applications are fixed in the upper left hand corner and become stacked on top of each other.
    Multi-panel JDS does not start up, and I am forced into one window, which makes the above problem critical.
    Conditions: New installation (not an upgrade) I experienced this problem. Attempted to connect from SGD. Using the following command
    /usr/dt/config/Xsession.jds
    Environment Variable: LD_LIBRARY_PATH=/usr/openwin/lib:/usr/dt/lib
    ERROR MESSAGE:
    There was an error starting the GNOME Settings Daemon.
    Some things, such as themes, sounds, or background settings may not work correctly.
    The Settings Daemon restarted too many times.
    The last error message was:
    Child process did not give an error message, unknown failure occurred
    GNOME will still try to restart the Settings Daemon next time you log in.
    SOLARIS Version:
    SunOS ITK-EDS1-IS 5.10 Generic_137137-09 sun4u sparc SUNW,Sun-Fire-V210
    Window Manager:
    Sun Java Desktop System, Release 3
    Build Date: 12/15/04
    After Problem Encountered I did the following:
    Insured all X, DT, and OPENWIN bins were in my path.
    Cleaned out the /var/tmp directory
    Cleared out the user directory except for the .dtprofile with the Sessionlog commented out, and the .profile.
    Rebooted the united and tried again.
    All .dt and JDS .directories are rebuilt, and the welcome to JDS comes up.
    The following is from the log files located in the .dt directory.
    Results of .dt/startlog (Note: only anomaly reported for brevity)
    --- starting /usr/dt/bin/dsdm &
    dsdm: another DSDM is already running
    Results of .dt/sessionlogs
    GNOME Desktop Environment
    using xinitrc file: /usr/dt/config/Xinitrc.jds
    Cleaned 0 files 0 still live
    Starting GNOME
    X_mkdir: Not owner
    (Message REPEATS)
    SESSION_MANAGER=local/ITK-EDS1-IS:/tmp/.ICE-unix/12329,inet6/ITK-EDS1-IS:34993,inet/ITK-EDS1-IS:34994
    Window manager warning: Log level 32: could not find XKB extension.
    Window manager warning: Screen 0 on display "10.70.10.21:11.0" already has a window manager; try using the --replace option to replace the current window manager.
    (Message REPEATS)
    (nautilus:12375): libgnomevfs-CRITICAL **: file gnome-vfs-volume.c: line 261: assertion `home_volume != NULL' failed
    (Message REPEATS 13 more times)
    Anyone have any idea of what this problem could be,

    Your main problem is that the JDS window manager (metacity) isn't starting up, because it thinks there is already another window manager running on that display:
    >
    Window manager warning: Screen 0 on display "10.70.10.21:11.0" already has a window manager; try using the --replace option to replace the current window manager.
    >
    I obviously don't know if there really is or not (I'm guessing not, if all the windows are stuck in the top left of the screen), but running "metacity --replace &" in a terminal should force it to start up.
    The gnome-settings-daemon warning is annoying, but non-fatal. It will usually just cause some icons and fonts to look incorrect. You can try running "/usr/lib/gnome-settings-daemon" again manually in a terminal, which will sometimes clear it up straight away. If not, I see you attempted to clean up some things in the home directory manually, but running "/usr/bin/gnome-cleanup" in a terminal (while not logged into JDS) might be a better thing to try.

  • Gnome Startup Application Preferenences - Are These Needed?

    Since it's been ages that I've used Gnome, not sure these preferences are needed for anything in Gnome or Arch.
    I personally don't have a need so can someone please tell me if Gnome or Arch depends on them for something, or some reason?
    Certificate and Key Storage
    GPG Password Agent
    Secret Storage Service
    THANKS
    Last edited by DasFox (2010-11-26 05:27:03)

    jasonwryan wrote:
    DasFox wrote:You know what, you're the second MOD that has told me to be on my way and go research before posting.
    A reasonable person might conclude, based on being told twice in as many days, that the problem is not with the moderators. You have already been asked to read the Forum Etiquette; to save you some effort, I will post a relevant section for you here:
    Forum Etiquette wrote:When asking for help, read the manual, do your research and provide details for those you are asking for help.
    DasFox wrote:You MODS need to knock off the attitude of telling people to go research before posting, because I'm starting to not like this place!
    I would suggest that you might like to reflect on your own behaviour and think seriously about what your combatative attitude is bringing to the community.
    I have read the manual/WIKI, Google and anything else you can think of and I have done my research, so now I come here and ask a question, what's the problem?
    No, you're not getting it, I don't have an attitude, when you made an assumption based on my questions you formed an attitude towards me, ASSUMING I'm not doing things.
    Because if you didn't assume, then you wouldn't of told me to go and research would you? Therefore you made an assumption, it's that simple, so please don't sit there and tell me you didn't.
    That assumption where I live is an insult towards someone and you should understand that on a forum as this it's a WORLD WIDE community with people that come from all walks of life and beliefs and ideas and the way in which you choose your words is of importance towards others, so as to not offend.
    Basically without realizing it, you were basically telling me I'm a newbie that should go research before posting and should know better.
    Now NO I'm not saying you actually are telling me these words, but by your actions towards this is how it is perceived that I'm some idiot that needs to be told what to do.
    The truth is I'm a guest in your house, I don't work here or get paid here, I come here as an outsider, so think about how you would treat a guest in your own house. Because in mine we would not use these words.
    This is what you said;
    and start doing the basic amount of research yourself before posting here...
    I'm sorry but in different parts of the world those words come across different to different people.
    In my world you might as well said, Go RTFM before coming here ok!!!
    So choose your words better if you don't want people to be upset...
    THANKS
    Last edited by DasFox (2010-11-28 03:53:31)

  • Gnome Errors ad startup and mouse arrow hungs

    Today I've updated all the system using pacman -Syu
    then I've installed ALSA
    pacman -Sy alsa-lib alsa-utils
    pacman -S alsa-oss
    pacman -S alsa-plugins
    setting the alsa deamon on startup on /etc/rc.conf file
    now when I start Gnome with xinit, I get all the errors below (actually some of them where also before) and the mouse is not recognized anymore, so I cannot move the mouse pointer.
    I've looked around but I didn't find any good info about fix them
    [miky@artemide ~]$ xinit
    X.Org X Server 1.12.2
    Release Date: 2012-05-29
    X Protocol Version 11, Revision 0
    Build Operating System: Linux 3.0.32-1-lts x86_64
    Current Operating System: Linux artemide 3.3.8-1-ARCH #1 SMP PREEMPT Tue Jun 5 15:20:32 CEST 2012 x86_64
    Kernel command line: root=/dev/sda3 ro initrd=../initramfs-linux.img BOOT_IMAGE=../vmlinuz-linux
    Build Date: 30 May 2012 07:24:13PM
    Current version of pixman: 0.26.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: Sat Jun 9 17:03:05 2012
    (==) Using config directory: "/etc/X11/xorg.conf.d"
    gnome-keyring-daemon: insufficient process capabilities, unsecure memory might get used
    GNOME_KEYRING_CONTROL=/home/miky/.cache/keyring-TvdLuD
    GPG_AGENT_INFO=/home/miky/.cache/keyring-TvdLuD/gpg:0:1
    GNOME_KEYRING_PID=1136
    gnome-keyring-daemon: insufficient process capabilities, unsecure memory might get used
    gnome-keyring-daemon: insufficient process capabilities, unsecure memory might get used
    GNOME_KEYRING_CONTROL=/home/miky/.cache/keyring-TvdLuD
    GPG_AGENT_INFO=/home/miky/.cache/keyring-TvdLuD/gpg:0:1
    gnome-keyring-daemon: insufficient process capabilities, unsecure memory might get used
    GNOME_KEYRING_CONTROL=/home/miky/.cache/keyring-TvdLuD
    GPG_AGENT_INFO=/home/miky/.cache/keyring-TvdLuD/gpg:0:1
    SSH_AUTH_SOCK=/home/miky/.cache/keyring-TvdLuD/ssh
    GNOME_KEYRING_CONTROL=/home/miky/.cache/keyring-TvdLuD
    GPG_AGENT_INFO=/home/miky/.cache/keyring-TvdLuD/gpg:0:1
    SSH_AUTH_SOCK=/home/miky/.cache/keyring-TvdLuD/ssh
    [1339254187,000,xklavier.c:xkl_engine_start_listen/] The backend does not require manual layout management - but it is provided by the application
    (gnome-settings-daemon:1134): color-plugin-WARNING **: failed to create device: GDBus.Error:org.freedesktop.ColorManager.Failed: failed to obtain org.freedesktop.col or-manager.create-device auth
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Warning: Compat map for group 2 redefined
    > Using new definition
    > Warning: Compat map for group 3 redefined
    > Using new definition
    > Warning: Compat map for group 4 redefined
    > Using new definition
    Errors from xkbcomp are not fatal to the X server
    N: [pulseaudio] main.c: User-configured server at {63971c7ac37392e6e112710d00000308}unix:/tmp/pulse-K2Eo3ctJETpV/native, which appears to be local. Probing deeper.
    Failed to play sound: File or data not found
    ** (nm-applet:1162): WARNING **: Could not initialize NMClient /org/freedesktop/NetworkManager: Launch helper exited with unknown return code 1
    ** Message: applet now removed from the notification area
    (gnome-shell-calendar-server:1186): GLib-GIO-ERROR **: Settings schema 'org.gnome.evolution.calendar' is not installed
    (gnome-shell:1154): Bluetooth-WARNING **: Could not open RFKILL control device, please verify your installation
    Window manager warning: Log level 16: Could not initialize NMClient /org/freedesktop/NetworkManager: Launch helper exited with unknown return code 1
    ** (nm-applet:1162): WARNING **: fetch_connections_done: error fetching connections: (25) Launch helper exited with unknown return code 1.
    ** (nm-applet:1162): WARNING **: Failed to register as an agent: (25) Launch helper exited with unknown return code 1
    ** Message: applet now embedded in the notification area
    Window manager warning: CurrentTime used to choose focus window; focus window may not be correct.
    Window manager warning: Got a request to focus the no_focus_window with a timestamp of 0. This shouldn't happen!
    (gnome-shell:1154): folks-WARNING **: Failed to find primary PersonaStore with type ID 'eds' and ID 'system'.
    Individuals will not be linked properly and creating new links between Personas will not work.
    The configured primary PersonaStore's backend may not be installed. If you are unsure, check with your distribution.
    Window manager warning: Log level 16: fetch_connections_done: error fetching connections: (25) Launch helper exited with unknown return code 1.
    Window manager warning: Log level 16: _nm_remote_settings_ensure_inited: (NMRemoteSettings) error initializing: Launch helper exited with unknown return code 1
    The XKEYBOARD keymap compiler (xkbcomp) reports:
    > Warning: Compat map for group 2 redefined
    > Using new definition
    > Warning: Compat map for group 3 redefined
    > Using new definition
    > Warning: Compat map for group 4 redefined
    > Using new definition
    Errors from xkbcomp are not fatal to the X server
    ^Cxinit: connection to X server lost
    waiting for X server to shut down gnome-session[1099]: Gdk-WARNING: gnome-session: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.

    I've reinstalle ALSA e rebooted and now the mouse work fine (i'm not sure why)
    the errors are still there
    my rc.conf
    # KEYMAP: keymaps are found in /usr/share/kbd/keymaps
    # CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
    # CONSOLEMAP: found in /usr/share/kbd/consoletrans
    # USECOLOR: use ANSI color sequences in startup messages
    LOCALE="en_US.UTF-8"
    DAEMON_LOCALE="no"
    HARDWARECLOCK="UTC"
    TIMEZONE="Europe/Rome"
    KEYMAP="us"
    CONSOLEFONT=
    CONSOLEMAP=
    USECOLOR="yes"
    # HARDWARE
    # MODULES: Modules to load at boot-up. Blacklisting is no longer supported.
    # Replace every !module by an entry as on the following line in a file in
    # /etc/modprobe.d:
    # blacklist module
    # See "man modprobe.conf" for details.
    MODULES=(fuse)
    # Udev settle timeout (default to 30)
    UDEV_TIMEOUT=30
    # Scan for FakeRAID (dmraid) Volumes at startup
    USEDMRAID="no"
    # Scan for BTRFS volumes at startup
    USEBTRFS="no"
    # Scan for LVM volume groups at startup, required if you use LVM
    USELVM="yes"
    # NETWORKING
    # HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
    HOSTNAME="artemide"
    # Use 'ip addr' or 'ls /sys/class/net/' to see all available interfaces.
    # Wired network setup
    # - interface: name of device (required)
    # - address: IP address (leave blank for DHCP)
    # - netmask: subnet mask (ignored for DHCP) (optional, defaults to 255.255.255.0)
    # - broadcast: broadcast address (ignored for DHCP) (optional)
    # - gateway: default route (ignored for DHCP)
    # Static IP example
    # interface=eth0
    # address=192.168.0.2
    # netmask=255.255.255.0
    # broadcast=192.168.0.255
    # gateway=192.168.0.1
    # DHCP example
    # interface=eth0
    # address=
    # netmask=
    # gateway=
    interface="eth0"
    address=10.40.50.95
    netmask=255.255.248.0
    broadcast=
    gateway=10.40.48.1
    # Setting this to "yes" will skip network shutdown.
    # This is required if your root device is on NFS.
    NETWORK_PERSIST="no"
    # Enable these netcfg profiles at boot-up. These are useful if you happen to
    # need more advanced network features than the simple network service
    # supports, such as multiple network configurations (ie, laptop users)
    # - set to 'menu' to present a menu during boot-up (dialog package required)
    # - prefix an entry with a ! to disable it
    # Network profiles are found in /etc/network.d
    # This requires the netcfg package
    #NETWORKS=(main)
    # DAEMONS
    # Daemons to start at boot-up (in this order)
    # - prefix a daemon with a ! to disable it
    # - prefix a daemon with a @ to start it up in the background
    # If something other takes care of your hardware clock (ntpd, dual-boot...)
    # you should disable 'hwclock' here.
    DAEMONS=(!hwclock @ntpd samba alsa syslog-ng dbus @network netfs crond tg3 @sshd appset-helper transmissiond)
    my /var/log/Xorg.0.log
    [224851.203]
    X.Org X Server 1.12.2
    Release Date: 2012-05-29
    [224851.203] X Protocol Version 11, Revision 0
    [224851.203] Build Operating System: Linux 3.0.32-1-lts x86_64
    [224851.203] Current Operating System: Linux artemide 3.3.8-1-ARCH #1 SMP PREEMPT Tue Jun 5 15:20:32 CEST 2012 x86_64
    [224851.203] Kernel command line: root=/dev/sda3 ro initrd=../initramfs-linux.img BOOT_IMAGE=../vmlinuz-linux
    [224851.203] Build Date: 30 May 2012 07:24:13PM
    [224851.203]
    [224851.203] Current version of pixman: 0.26.0
    [224851.203] Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    [224851.203] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [224851.203] (==) Log file: "/var/log/Xorg.0.log", Time: Tue Jun 12 14:09:41 2012
    [224851.216] (==) Using config directory: "/etc/X11/xorg.conf.d"
    [224851.219] (==) No Layout section. Using the first Screen section.
    [224851.220] (==) No screen section available. Using defaults.
    [224851.220] (**) |-->Screen "Default Screen Section" (0)
    [224851.220] (**) | |-->Monitor "<default monitor>"
    [224851.220] (==) No monitor specified for screen "Default Screen Section".
    Using a default monitor configuration.
    [224851.220] (==) Automatically adding devices
    [224851.220] (==) Automatically enabling devices
    [224851.240] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
    [224851.240] Entry deleted from font path.
    [224851.240] (WW) The directory "/usr/share/fonts/Type1/" does not exist.
    [224851.240] Entry deleted from font path.
    [224851.240] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
    [224851.241] Entry deleted from font path.
    [224851.241] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
    [224851.241] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
    [224851.241] Entry deleted from font path.
    [224851.241] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
    [224851.241] (==) FontPath set to:
    /usr/share/fonts/misc/,
    /usr/share/fonts/TTF/
    /usr/share/fonts/TTF/
    [224851.241] (==) ModulePath set to "/usr/lib/xorg/modules"
    [224851.241] (II) The server relies on udev to provide the list of input devices.
    If no devices become available, reconfigure udev or disable AutoAddDevices.
    [224851.241] (II) Loader magic: 0x7c58e0
    [224851.241] (II) Module ABI versions:
    [224851.241] X.Org ANSI C Emulation: 0.4
    [224851.241] X.Org Video Driver: 12.0
    [224851.241] X.Org XInput driver : 16.0
    [224851.241] X.Org Server Extension : 6.0
    [224851.242] (--) PCI:*(0:0:2:0) 8086:0102:1043:844d rev 9, Mem @ 0xfe000000/4194304, 0xc0000000/268435456, I/O @ 0x0000f000/64
    [224851.242] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
    [224851.242] (II) LoadModule: "extmod"
    [224851.247] (II) Loading /usr/lib/xorg/modules/extensions/libextmod.so
    [224851.257] (II) Module extmod: vendor="X.Org Foundation"
    [224851.257] compiled for 1.12.2, module version = 1.0.0
    [224851.257] Module class: X.Org Server Extension
    [224851.257] ABI class: X.Org Server Extension, version 6.0
    [224851.257] (II) Loading extension MIT-SCREEN-SAVER
    [224851.257] (II) Loading extension XFree86-VidModeExtension
    [224851.257] (II) Loading extension XFree86-DGA
    [224851.257] (II) Loading extension DPMS
    [224851.257] (II) Loading extension XVideo
    [224851.257] (II) Loading extension XVideo-MotionCompensation
    [224851.257] (II) Loading extension X-Resource
    [224851.257] (II) LoadModule: "dbe"
    [224851.257] (II) Loading /usr/lib/xorg/modules/extensions/libdbe.so
    [224851.257] (II) Module dbe: vendor="X.Org Foundation"
    [224851.257] compiled for 1.12.2, module version = 1.0.0
    [224851.257] Module class: X.Org Server Extension
    [224851.257] ABI class: X.Org Server Extension, version 6.0
    [224851.257] (II) Loading extension DOUBLE-BUFFER
    [224851.257] (II) LoadModule: "glx"
    [224851.260] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    [224851.278] (II) Module glx: vendor="X.Org Foundation"
    [224851.278] compiled for 1.12.2, module version = 1.0.0
    [224851.278] ABI class: X.Org Server Extension, version 6.0
    [224851.278] ABI class: X.Org Server Extension, version 6.0
    [224851.278] (==) AIGLX enabled
    [224851.278] (II) Loading extension GLX
    [224851.278] (II) LoadModule: "record"
    [224851.278] (II) Loading /usr/lib/xorg/modules/extensions/librecord.so
    [224851.279] (II) Module record: vendor="X.Org Foundation"
    [224851.279] compiled for 1.12.2, module version = 1.13.0
    [224851.279] Module class: X.Org Server Extension
    [224851.279] ABI class: X.Org Server Extension, version 6.0
    [224851.279] (II) Loading extension RECORD
    [224851.279] (II) LoadModule: "dri"
    [224851.279] (II) Loading /usr/lib/xorg/modules/extensions/libdri.so
    [224851.287] (II) Module dri: vendor="X.Org Foundation"
    [224851.287] compiled for 1.12.2, module version = 1.0.0
    [224851.287] ABI class: X.Org Server Extension, version 6.0
    [224851.287] (II) Loading extension XFree86-DRI
    [224851.287] (II) LoadModule: "dri2"
    [224851.287] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
    [224851.288] (II) Module dri2: vendor="X.Org Foundation"
    [224851.288] compiled for 1.12.2, module version = 1.2.0
    [224851.288] ABI class: X.Org Server Extension, version 6.0
    [224851.288] (II) Loading extension DRI2
    [224851.288] (==) Matched intel as autoconfigured driver 0
    [224851.288] (==) Matched vesa as autoconfigured driver 1
    [224851.288] (==) Matched fbdev as autoconfigured driver 2
    [224851.288] (==) Assigned the driver to the xf86ConfigLayout
    [224851.288] (II) LoadModule: "intel"
    [224851.294] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
    [224851.308] (II) Module intel: vendor="X.Org Foundation"
    [224851.308] compiled for 1.12.2, module version = 2.19.0
    [224851.308] Module class: X.Org Video Driver
    [224851.308] ABI class: X.Org Video Driver, version 12.0
    [224851.308] (II) LoadModule: "vesa"
    [224851.317] (WW) Warning, couldn't open module vesa
    [224851.317] (II) UnloadModule: "vesa"
    [224851.317] (II) Unloading vesa
    [224851.317] (EE) Failed to load module "vesa" (module does not exist, 0)
    [224851.317] (II) Unloading vesa
    [224851.317] (EE) Failed to load module "vesa" (module does not exist, 0)
    [224851.317] (II) LoadModule: "fbdev"
    [224851.317] (WW) Warning, couldn't open module fbdev
    [224851.317] (II) UnloadModule: "fbdev"
    [224851.317] (II) Unloading fbdev
    [224851.317] (EE) Failed to load module "fbdev" (module does not exist, 0)
    [224851.317] (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)
    [224851.317] (--) using VT number 7
    [224851.425] drmOpenDevice: node name is /dev/dri/card0
    [224851.425] drmOpenDevice: open result is 10, (OK)
    [224851.425] drmOpenByBusid: Searching for BusID pci:0000:00:02.0
    [224851.425] drmOpenDevice: node name is /dev/dri/card0
    [224851.425] drmOpenDevice: open result is 10, (OK)
    [224851.425] drmOpenByBusid: drmOpenMinor returns 10
    [224851.425] drmOpenByBusid: drmGetBusid reports pci:0000:00:02.0
    [224851.425] (II) intel(0): Creating default Display subsection in Screen section
    "Default Screen Section" for depth/fbbpp 24/32
    [224851.425] (==) intel(0): Depth 24, (--) framebuffer bpp 32
    [224851.425] (==) intel(0): RGB weight 888
    [224851.425] (==) intel(0): Default visual is TrueColor
    [224851.425] (II) intel(0): Integrated Graphics Chipset: Intel(R) Sandybridge Desktop (GT1)
    [224851.425] (--) intel(0): Chipset: "Sandybridge Desktop (GT1)"
    [224851.425] (**) intel(0): Relaxed fencing enabled
    [224851.425] (**) intel(0): Wait on SwapBuffers? enabled
    [224851.425] (**) intel(0): Triple buffering? enabled
    [224851.425] (**) intel(0): Framebuffer tiled
    [224851.425] (**) intel(0): Pixmaps tiled
    [224851.425] (**) intel(0): 3D buffers tiled
    [224851.425] (**) intel(0): SwapBuffers wait enabled
    [224851.425] (==) intel(0): video overlay key set to 0x101fe
    [224851.426] (II) intel(0): Output VGA1 has no monitor section
    [224851.447] (II) intel(0): Output HDMI1 has no monitor section
    [224851.487] (II) intel(0): Output DP1 has no monitor section
    [224851.721] (II) intel(0): Output HDMI2 has no monitor section
    [224851.760] (II) intel(0): Output DP2 has no monitor section
    [224851.760] (II) intel(0): EDID for output VGA1
    [224851.782] (II) intel(0): EDID for output HDMI1
    [224851.820] (II) intel(0): EDID for output DP1
    [224852.054] (II) intel(0): EDID for output HDMI2
    [224852.054] (II) intel(0): Manufacturer: SHP Model: 105d Serial#: 0
    [224852.054] (II) intel(0): Year: 2010 Week: 255
    [224852.054] (II) intel(0): EDID Version: 1.3
    [224852.054] (II) intel(0): Digital Display Input
    [224852.054] (II) intel(0): Max Image Size [cm]: horiz.: 102 vert.: 57
    [224852.054] (II) intel(0): Gamma: 2.20
    [224852.054] (II) intel(0): DPMS capabilities: Off
    [224852.054] (II) intel(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
    [224852.054] (II) intel(0): First detailed timing is preferred mode
    [224852.054] (II) intel(0): redX: 0.633 redY: 0.333 greenX: 0.205 greenY: 0.702
    [224852.054] (II) intel(0): blueX: 0.150 blueY: 0.081 whiteX: 0.292 whiteY: 0.322
    [224852.054] (II) intel(0): Supported established timings:
    [224852.054] (II) intel(0): 720x400@70Hz
    [224852.054] (II) intel(0): 640x480@60Hz
    [224852.054] (II) intel(0): 640x480@72Hz
    [224852.054] (II) intel(0): 640x480@75Hz
    [224852.054] (II) intel(0): 800x600@56Hz
    [224852.054] (II) intel(0): 800x600@60Hz
    [224852.054] (II) intel(0): 800x600@72Hz
    [224852.054] (II) intel(0): 800x600@75Hz
    [224852.054] (II) intel(0): 1024x768@60Hz
    [224852.054] (II) intel(0): 1024x768@70Hz
    [224852.054] (II) intel(0): 1024x768@75Hz
    [224852.054] (II) intel(0): Manufacturer's mask: 0
    [224852.054] (II) intel(0): Supported standard timings:
    [224852.054] (II) intel(0): #0: hsize: 1600 vsize 1200 refresh: 60 vid: 16553
    [224852.054] (II) intel(0): #1: hsize: 1400 vsize 1050 refresh: 60 vid: 16528
    [224852.054] (II) intel(0): #2: hsize: 1280 vsize 1024 refresh: 60 vid: 32897
    [224852.054] (II) intel(0): Supported detailed timing:
    [224852.054] (II) intel(0): clock: 148.5 MHz Image Size: 1018 x 573 mm
    [224852.054] (II) intel(0): h_active: 1920 h_sync: 2448 h_sync_end 2492 h_blank_end 2640 h_border: 0
    [224852.054] (II) intel(0): v_active: 1080 v_sync: 1084 v_sync_end 1089 v_blanking: 1125 v_border: 0
    [224852.054] (II) intel(0): Supported detailed timing:
    [224852.054] (II) intel(0): clock: 85.5 MHz Image Size: 0 x 0 mm
    [224852.054] (II) intel(0): h_active: 1360 h_sync: 1424 h_sync_end 1536 h_blank_end 1792 h_border: 0
    [224852.054] (II) intel(0): v_active: 768 v_sync: 771 v_sync_end 777 v_blanking: 795 v_border: 0
    [224852.054] (II) intel(0): Monitor name: SHARP HDMI
    [224852.054] (II) intel(0): Ranges: V min: 23 V max: 76 Hz, H min: 15 H max: 75 kHz, PixClock max 175 MHz
    [224852.054] (II) intel(0): Supported detailed timing:
    [224852.054] (II) intel(0): clock: 148.5 MHz Image Size: 1018 x 573 mm
    [224852.054] (II) intel(0): h_active: 1920 h_sync: 2008 h_sync_end 2052 h_blank_end 2200 h_border: 0
    [224852.054] (II) intel(0): v_active: 1080 v_sync: 1084 v_sync_end 1089 v_blanking: 1125 v_border: 0
    [224852.054] (II) intel(0): Supported detailed timing:
    [224852.054] (II) intel(0): clock: 74.2 MHz Image Size: 1018 x 573 mm
    [224852.054] (II) intel(0): h_active: 1920 h_sync: 2448 h_sync_end 2492 h_blank_end 2640 h_border: 0
    [224852.054] (II) intel(0): v_active: 540 v_sync: 542 v_sync_end 547 v_blanking: 562 v_border: 0
    [224852.054] (II) intel(0): Supported detailed timing:
    [224852.054] (II) intel(0): clock: 74.2 MHz Image Size: 1018 x 573 mm
    [224852.054] (II) intel(0): h_active: 1920 h_sync: 2008 h_sync_end 2052 h_blank_end 2200 h_border: 0
    [224852.054] (II) intel(0): v_active: 540 v_sync: 542 v_sync_end 547 v_blanking: 562 v_border: 0
    [224852.054] (II) intel(0): Supported detailed timing:
    [224852.054] (II) intel(0): clock: 74.2 MHz Image Size: 1018 x 573 mm
    [224852.054] (II) intel(0): h_active: 1280 h_sync: 1720 h_sync_end 1760 h_blank_end 1980 h_border: 0
    [224852.054] (II) intel(0): v_active: 720 v_sync: 725 v_sync_end 730 v_blanking: 750 v_border: 0
    [224852.054] (II) intel(0): Number of EDID sections to follow: 1
    [224852.054] (II) intel(0): EDID (in hex):
    [224852.054] (II) intel(0): 00ffffffffffff004d105d1000000000
    [224852.054] (II) intel(0): ff140103806639782a1bbea25534b326
    [224852.054] (II) intel(0): 144a52afce00a9409040818001010101
    [224852.054] (II) intel(0): 010101010101023a80d072382d40102c
    [224852.054] (II) intel(0): 4580fa3d3200001e662150b051001b30
    [224852.054] (II) intel(0): 4070360000000000001e000000fc0053
    [224852.054] (II) intel(0): 484152502048444d490a2020000000fd
    [224852.054] (II) intel(0): 00174c0f4b11000a20202020202001a8
    [224852.054] (II) intel(0): 02033172509f90201405130412031102
    [224852.054] (II) intel(0): 16071506012309070783010000e30503
    [224852.054] (II) intel(0): 016f030c001000b82d20a00501402050
    [224852.054] (II) intel(0): 60023a801871382d40582c4500fa3d32
    [224852.054] (II) intel(0): 00001e011d80d0721c1620102c2580fa
    [224852.054] (II) intel(0): 3d3200009e011d8018711c1620582c25
    [224852.054] (II) intel(0): 00fa3d3200009e011d00bc52d01e20b8
    [224852.055] (II) intel(0): 285540fa3d3200001e00000000000082
    [224852.055] (II) intel(0): Printing probed modes for output HDMI2
    [224852.055] (II) intel(0): Modeline "1920x1080"x50.0 148.50 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync (56.2 kHz eP)
    [224852.055] (II) intel(0): Modeline "1920x1080"x60.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz e)
    [224852.055] (II) intel(0): Modeline "1920x1080"x24.0 74.25 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync (27.0 kHz e)
    [224852.055] (II) intel(0): Modeline "1600x1200"x60.0 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (75.0 kHz e)
    [224852.055] (II) intel(0): Modeline "1400x1050"x60.0 121.75 1400 1488 1632 1864 1050 1053 1057 1089 -hsync +vsync (65.3 kHz e)
    [224852.055] (II) intel(0): Modeline "1280x1024"x60.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
    [224852.055] (II) intel(0): Modeline "1360x768"x60.0 85.50 1360 1424 1536 1792 768 771 777 795 +hsync +vsync (47.7 kHz e)
    [224852.055] (II) intel(0): Modeline "1280x720"x60.0 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e)
    [224852.055] (II) intel(0): Modeline "1280x720"x50.0 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync (37.5 kHz e)
    [224852.055] (II) intel(0): Modeline "1024x768"x75.1 78.80 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.1 kHz e)
    [224852.055] (II) intel(0): Modeline "1024x768"x70.1 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
    [224852.055] (II) intel(0): Modeline "1024x768"x60.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [224852.055] (II) intel(0): Modeline "800x600"x72.2 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
    [224852.055] (II) intel(0): Modeline "800x600"x75.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
    [224852.055] (II) intel(0): Modeline "800x600"x60.3 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [224852.055] (II) intel(0): Modeline "800x600"x56.2 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
    [224852.055] (II) intel(0): Modeline "720x576"x50.0 27.00 720 732 796 864 576 581 586 625 -hsync -vsync (31.2 kHz e)
    [224852.055] (II) intel(0): Modeline "720x480"x59.9 27.00 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e)
    [224852.055] (II) intel(0): Modeline "640x480"x72.8 31.50 640 664 704 832 480 489 491 520 -hsync -vsync (37.9 kHz e)
    [224852.055] (II) intel(0): Modeline "640x480"x75.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
    [224852.055] (II) intel(0): Modeline "640x480"x60.0 25.20 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [224852.055] (II) intel(0): Modeline "640x480"x59.9 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [224852.055] (II) intel(0): Modeline "720x400"x70.1 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
    [224852.094] (II) intel(0): EDID for output DP2
    [224852.094] (II) intel(0): Output VGA1 disconnected
    [224852.094] (II) intel(0): Output HDMI1 disconnected
    [224852.094] (II) intel(0): Output DP1 disconnected
    [224852.094] (II) intel(0): Output HDMI2 connected
    [224852.094] (II) intel(0): Output DP2 disconnected
    [224852.094] (II) intel(0): Using exact sizes for initial modes
    [224852.094] (II) intel(0): Output HDMI2 using initial mode 1920x1080
    [224852.094] (II) intel(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
    [224852.094] (II) intel(0): Kernel page flipping support detected, enabling
    [224852.094] (==) intel(0): DPI set to (96, 96)
    [224852.094] (II) Loading sub module "fb"
    [224852.094] (II) LoadModule: "fb"
    [224852.094] (II) Loading /usr/lib/xorg/modules/libfb.so
    [224852.095] (II) Module fb: vendor="X.Org Foundation"
    [224852.095] compiled for 1.12.2, module version = 1.0.0
    [224852.095] ABI class: X.Org ANSI C Emulation, version 0.4
    [224852.095] (II) Loading sub module "dri2"
    [224852.095] (II) LoadModule: "dri2"
    [224852.095] (II) Loading /usr/lib/xorg/modules/extensions/libdri2.so
    [224852.095] (II) Module dri2: vendor="X.Org Foundation"
    [224852.095] compiled for 1.12.2, module version = 1.2.0
    [224852.095] ABI class: X.Org Server Extension, version 6.0
    [224852.095] (==) Depth 24 pixmap format is 32 bpp
    [224852.095] (II) intel(0): [DRI2] Setup complete
    [224852.095] (II) intel(0): [DRI2] DRI driver: i965
    [224852.095] (II) intel(0): Allocated new frame buffer 1920x1080 stride 7680, tiled
    [224852.097] (II) UXA(0): Driver registered support for the following operations:
    [224852.097] (II) solid
    [224852.097] (II) copy
    [224852.097] (II) composite (RENDER acceleration)
    [224852.097] (II) put_image
    [224852.097] (II) get_image
    [224852.097] (==) intel(0): Backing store disabled
    [224852.097] (==) intel(0): Silken mouse enabled
    [224852.097] (II) intel(0): Initializing HW Cursor
    [224852.097] (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
    [224852.097] (==) intel(0): DPMS enabled
    [224852.097] (==) intel(0): Intel XvMC decoder enabled
    [224852.097] (II) intel(0): Set up textured video
    [224852.097] (II) intel(0): [XvMC] xvmc_vld driver initialized.
    [224852.097] (II) intel(0): direct rendering: DRI2 Enabled
    [224852.097] (==) intel(0): hotplug detection: "enabled"
    [224852.160] (--) RandR disabled
    [224852.160] (II) Initializing built-in extension Generic Event Extension
    [224852.160] (II) Initializing built-in extension SHAPE
    [224852.160] (II) Initializing built-in extension MIT-SHM
    [224852.161] (II) Initializing built-in extension XInputExtension
    [224852.161] (II) Initializing built-in extension XTEST
    [224852.161] (II) Initializing built-in extension BIG-REQUESTS
    [224852.161] (II) Initializing built-in extension SYNC
    [224852.161] (II) Initializing built-in extension XKEYBOARD
    [224852.161] (II) Initializing built-in extension XC-MISC
    [224852.161] (II) Initializing built-in extension SECURITY
    [224852.161] (II) Initializing built-in extension XINERAMA
    [224852.161] (II) Initializing built-in extension XFIXES
    [224852.161] (II) Initializing built-in extension RENDER
    [224852.161] (II) Initializing built-in extension RANDR
    [224852.161] (II) Initializing built-in extension COMPOSITE
    [224852.161] (II) Initializing built-in extension DAMAGE
    [224852.257] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
    [224852.257] (II) AIGLX: enabled GLX_INTEL_swap_event
    [224852.257] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
    [224852.257] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
    [224852.257] (II) AIGLX: Loaded and initialized i965
    [224852.257] (II) GLX: Initialized DRI2 GL provider for screen 0
    [224852.257] (II) intel(0): Setting screen physical size to 508 x 285
    [224852.451] (II) config/udev: Adding input device Power Button (/dev/input/event1)
    [224852.451] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [224852.451] (II) LoadModule: "evdev"
    [224852.451] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [224852.461] (II) Module evdev: vendor="X.Org Foundation"
    [224852.461] compiled for 1.12.0, module version = 2.7.0
    [224852.461] Module class: X.Org XInput Driver
    [224852.461] ABI class: X.Org XInput driver, version 16.0
    [224852.461] (II) Using input driver 'evdev' for 'Power Button'
    [224852.461] (**) Power Button: always reports core events
    [224852.461] (**) evdev: Power Button: Device: "/dev/input/event1"
    [224852.461] (--) evdev: Power Button: Vendor 0 Product 0x1
    [224852.461] (--) evdev: Power Button: Found keys
    [224852.461] (II) evdev: Power Button: Configuring as keyboard
    [224852.461] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1/event1"
    [224852.461] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
    [224852.461] (**) Option "xkb_rules" "evdev"
    [224852.461] (**) Option "xkb_model" "evdev"
    [224852.461] (**) Option "xkb_layout" "us"
    [224852.482] (II) config/udev: Adding input device Video Bus (/dev/input/event13)
    [224852.482] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
    [224852.482] (II) Using input driver 'evdev' for 'Video Bus'
    [224852.482] (**) Video Bus: always reports core events
    [224852.482] (**) evdev: Video Bus: Device: "/dev/input/event13"
    [224852.482] (--) evdev: Video Bus: Vendor 0 Product 0x6
    [224852.482] (--) evdev: Video Bus: Found keys
    [224852.482] (II) evdev: Video Bus: Configuring as keyboard
    [224852.482] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/LNXVIDEO:00/input/input13/event13"
    [224852.482] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
    [224852.482] (**) Option "xkb_rules" "evdev"
    [224852.482] (**) Option "xkb_model" "evdev"
    [224852.482] (**) Option "xkb_layout" "us"
    [224852.482] (II) config/udev: Adding input device Power Button (/dev/input/event0)
    [224852.482] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [224852.482] (II) Using input driver 'evdev' for 'Power Button'
    [224852.482] (**) Power Button: always reports core events
    [224852.482] (**) evdev: Power Button: Device: "/dev/input/event0"
    [224852.482] (--) evdev: Power Button: Vendor 0 Product 0x1
    [224852.482] (--) evdev: Power Button: Found keys
    [224852.482] (II) evdev: Power Button: Configuring as keyboard
    [224852.482] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0/event0"
    [224852.482] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 8)
    [224852.482] (**) Option "xkb_rules" "evdev"
    [224852.482] (**) Option "xkb_model" "evdev"
    [224852.482] (**) Option "xkb_layout" "us"
    [224852.483] (II) config/udev: Adding input device HDA Intel PCH Rear Mic (/dev/input/event10)
    [224852.483] (II) No input driver specified, ignoring this device.
    [224852.483] (II) This device may have been added with another device file.
    [224852.483] (II) config/udev: Adding input device HDA Intel PCH Front Headphone (/dev/input/event11)
    [224852.483] (II) No input driver specified, ignoring this device.
    [224852.483] (II) This device may have been added with another device file.
    [224852.483] (II) config/udev: Adding input device HDA Intel PCH Line Out (/dev/input/event12)
    [224852.483] (II) No input driver specified, ignoring this device.
    [224852.483] (II) This device may have been added with another device file.
    [224852.483] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=3 (/dev/input/event7)
    [224852.483] (II) No input driver specified, ignoring this device.
    [224852.483] (II) This device may have been added with another device file.
    [224852.483] (II) config/udev: Adding input device HDA Intel PCH Line (/dev/input/event8)
    [224852.483] (II) No input driver specified, ignoring this device.
    [224852.483] (II) This device may have been added with another device file.
    [224852.484] (II) config/udev: Adding input device HDA Intel PCH Front Mic (/dev/input/event9)
    [224852.484] (II) No input driver specified, ignoring this device.
    [224852.484] (II) This device may have been added with another device file.
    [224852.484] (II) config/udev: Adding input device USB Keyboard (/dev/input/event4)
    [224852.484] (**) USB Keyboard: Applying InputClass "evdev keyboard catchall"
    [224852.484] (II) Using input driver 'evdev' for ' USB Keyboard'
    [224852.484] (**) USB Keyboard: always reports core events
    [224852.484] (**) evdev: USB Keyboard: Device: "/dev/input/event4"
    [224852.484] (--) evdev: USB Keyboard: Vendor 0x4d9 Product 0x1603
    [224852.484] (--) evdev: USB Keyboard: Found keys
    [224852.484] (II) evdev: USB Keyboard: Configuring as keyboard
    [224852.484] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.3/4-1.3:1.0/input/input4/event4"
    [224852.484] (II) XINPUT: Adding extended input device " USB Keyboard" (type: KEYBOARD, id 9)
    [224852.484] (**) Option "xkb_rules" "evdev"
    [224852.484] (**) Option "xkb_model" "evdev"
    [224852.484] (**) Option "xkb_layout" "us"
    [224852.484] (II) config/udev: Adding input device USB Keyboard (/dev/input/event5)
    [224852.484] (**) USB Keyboard: Applying InputClass "evdev keyboard catchall"
    [224852.484] (II) Using input driver 'evdev' for ' USB Keyboard'
    [224852.484] (**) USB Keyboard: always reports core events
    [224852.485] (**) evdev: USB Keyboard: Device: "/dev/input/event5"
    [224852.485] (--) evdev: USB Keyboard: Vendor 0x4d9 Product 0x1603
    [224852.485] (--) evdev: USB Keyboard: Found keys
    [224852.485] (II) evdev: USB Keyboard: Configuring as keyboard
    [224852.485] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.3/4-1.3:1.1/input/input5/event5"
    [224852.485] (II) XINPUT: Adding extended input device " USB Keyboard" (type: KEYBOARD, id 10)
    [224852.485] (**) Option "xkb_rules" "evdev"
    [224852.485] (**) Option "xkb_model" "evdev"
    [224852.485] (**) Option "xkb_layout" "us"
    [224852.485] (II) config/udev: Adding input device HID 04b3:3107 (/dev/input/event6)
    [224852.485] (**) HID 04b3:3107: Applying InputClass "evdev pointer catchall"
    [224852.485] (II) Using input driver 'evdev' for 'HID 04b3:3107'
    [224852.485] (**) HID 04b3:3107: always reports core events
    [224852.485] (**) evdev: HID 04b3:3107: Device: "/dev/input/event6"
    [224852.485] (--) evdev: HID 04b3:3107: Vendor 0x4b3 Product 0x3107
    [224852.485] (--) evdev: HID 04b3:3107: Found 3 mouse buttons
    [224852.485] (--) evdev: HID 04b3:3107: Found scroll wheel(s)
    [224852.485] (--) evdev: HID 04b3:3107: Found relative axes
    [224852.485] (--) evdev: HID 04b3:3107: Found x and y relative axes
    [224852.485] (II) evdev: HID 04b3:3107: Configuring as mouse
    [224852.485] (II) evdev: HID 04b3:3107: Adding scrollwheel support
    [224852.485] (**) evdev: HID 04b3:3107: YAxisMapping: buttons 4 and 5
    [224852.485] (**) evdev: HID 04b3:3107: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [224852.485] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.4/4-1.4:1.0/input/input6/event6"
    [224852.485] (II) XINPUT: Adding extended input device "HID 04b3:3107" (type: MOUSE, id 11)
    [224852.485] (II) evdev: HID 04b3:3107: initialized for relative axes.
    [224852.485] (**) HID 04b3:3107: (accel) keeping acceleration scheme 1
    [224852.485] (**) HID 04b3:3107: (accel) acceleration profile 0
    [224852.485] (**) HID 04b3:3107: (accel) acceleration factor: 2.000
    [224852.485] (**) HID 04b3:3107: (accel) acceleration threshold: 4
    [224852.486] (II) config/udev: Adding input device HID 04b3:3107 (/dev/input/mouse0)
    [224852.486] (II) No input driver specified, ignoring this device.
    [224852.486] (II) This device may have been added with another device file.
    [224852.486] (II) config/udev: Adding input device Eee PC WMI hotkeys (/dev/input/event3)
    [224852.486] (**) Eee PC WMI hotkeys: Applying InputClass "evdev keyboard catchall"
    [224852.486] (II) Using input driver 'evdev' for 'Eee PC WMI hotkeys'
    [224852.486] (**) Eee PC WMI hotkeys: always reports core events
    [224852.486] (**) evdev: Eee PC WMI hotkeys: Device: "/dev/input/event3"
    [224852.486] (--) evdev: Eee PC WMI hotkeys: Vendor 0 Product 0
    [224852.486] (--) evdev: Eee PC WMI hotkeys: Found keys
    [224852.486] (II) evdev: Eee PC WMI hotkeys: Configuring as keyboard
    [224852.486] (**) Option "config_info" "udev:/sys/devices/platform/eeepc-wmi/input/input3/event3"
    [224852.486] (II) XINPUT: Adding extended input device "Eee PC WMI hotkeys" (type: KEYBOARD, id 12)
    [224852.486] (**) Option "xkb_rules" "evdev"
    [224852.486] (**) Option "xkb_model" "evdev"
    [224852.486] (**) Option "xkb_layout" "us"
    [224852.486] (II) config/udev: Adding input device PC Speaker (/dev/input/event2)
    [224852.486] (II) No input driver specified, ignoring this device.
    [224852.486] (II) This device may have been added with another device file.
    [224855.291] (II) intel(0): EDID vendor "SHP", prod id 4189
    [224855.291] (II) intel(0): Using EDID range info for horizontal sync
    [224855.291] (II) intel(0): Using EDID range info for vertical refresh
    [224855.291] (II) intel(0): Printing DDC gathered Modelines:
    [224855.291] (II) intel(0): Modeline "1920x1080"x0.0 148.50 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync (56.2 kHz eP)
    [224855.291] (II) intel(0): Modeline "1360x768"x0.0 85.50 1360 1424 1536 1792 768 771 777 795 +hsync +vsync (47.7 kHz e)
    [224855.291] (II) intel(0): Modeline "1920x1080"x0.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz e)
    [224855.291] (II) intel(0): Modeline "1920x1080i"x0.0 74.25 1920 2448 2492 2640 1080 1084 1094 1125 interlace +hsync +vsync (28.1 kHz e)
    [224855.291] (II) intel(0): Modeline "1920x1080i"x0.0 74.25 1920 2008 2052 2200 1080 1084 1094 1125 interlace +hsync +vsync (33.8 kHz e)
    [224855.291] (II) intel(0): Modeline "1280x720"x0.0 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync (37.5 kHz e)
    [224855.291] (II) intel(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [224855.291] (II) intel(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
    [224855.291] (II) intel(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
    [224855.291] (II) intel(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e)
    [224855.291] (II) intel(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [224855.291] (II) intel(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
    [224855.291] (II) intel(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
    [224855.291] (II) intel(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
    [224855.291] (II) intel(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [224855.291] (II) intel(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
    [224855.291] (II) intel(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
    [224855.291] (II) intel(0): Modeline "1600x1200"x0.0 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (75.0 kHz e)
    [224855.291] (II) intel(0): Modeline "1400x1050"x0.0 101.00 1400 1448 1480 1560 1050 1053 1057 1080 +hsync -vsync (64.7 kHz e)
    [224855.291] (II) intel(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
    [224855.291] (II) intel(0): Modeline "1920x1080"x0.0 74.25 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync (27.0 kHz e)
    [224855.291] (II) intel(0): Modeline "720x576"x0.0 27.00 720 732 796 864 576 581 586 625 -hsync -vsync (31.2 kHz e)
    [224855.291] (II) intel(0): Modeline "1920x1080"x0.0 74.25 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync (28.1 kHz e)
    [224855.291] (II) intel(0): Modeline "1440x576i"x0.0 27.00 1440 1464 1590 1728 576 580 586 625 interlace -hsync -vsync (15.6 kHz e)
    [224855.291] (II) intel(0): Modeline "1440x480i"x0.0 27.00 1440 1478 1602 1716 480 488 494 525 interlace -hsync -vsync (15.7 kHz e)
    [224855.291] (II) intel(0): Modeline "1280x720"x0.0 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e)
    [224855.291] (II) intel(0): Modeline "720x480"x0.0 27.00 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e)
    [224855.291] (II) intel(0): Modeline "1440x288"x0.0 27.00 1440 1464 1590 1728 288 290 293 312 -hsync -vsync (15.6 kHz e)
    [224855.291] (II) intel(0): Modeline "1440x240"x0.0 27.00 1440 1478 1602 1716 240 244 247 262 -hsync -vsync (15.7 kHz e)
    [224858.794] (II) intel(0): EDID vendor "SHP", prod id 4189
    [224858.794] (II) intel(0): Using hsync ranges from config file
    [224858.794] (II) intel(0): Using vrefresh ranges from config file
    [224858.794] (II) intel(0): Printing DDC gathered Modelines:
    [224858.794] (II) intel(0): Modeline "1920x1080"x0.0 148.50 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync (56.2 kHz eP)
    [224858.794] (II) intel(0): Modeline "1360x768"x0.0 85.50 1360 1424 1536 1792 768 771 777 795 +hsync +vsync (47.7 kHz e)
    [224858.794] (II) intel(0): Modeline "1920x1080"x0.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz e)
    [224858.794] (II) intel(0): Modeline "1920x1080i"x0.0 74.25 1920 2448 2492 2640 1080 1084 1094 1125 interlace +hsync +vsync (28.1 kHz e)
    [224858.794] (II) intel(0): Modeline "1920x1080i"x0.0 74.25 1920 2008 2052 2200 1080 1084 1094 1125 interlace +hsync +vsync (33.8 kHz e)
    [224858.794] (II) intel(0): Modeline "1280x720"x0.0 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync (37.5 kHz e)
    [224858.794] (II) intel(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [224858.795] (II) intel(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
    [224858.795] (II) intel(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
    [224858.795] (II) intel(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e)
    [224858.795] (II) intel(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [224858.795] (II) intel(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
    [224858.795] (II) intel(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
    [224858.795] (II) intel(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
    [224858.795] (II) intel(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [224858.795] (II) intel(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
    [224858.795] (II) intel(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
    [224858.795] (II) intel(0): Modeline "1600x1200"x0.0 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (75.0 kHz e)
    [224858.795] (II) intel(0): Modeline "1400x1050"x0.0 101.00 1400 1448 1480 1560 1050 1053 1057 1080 +hsync -vsync (64.7 kHz e)
    [224858.795] (II) intel(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
    [224858.795] (II) intel(0): Modeline "1920x1080"x0.0 74.25 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync (27.0 kHz e)
    [224858.795] (II) intel(0): Modeline "720x576"x0.0 27.00 720 732 796 864 576 581 586 625 -hsync -vsync (31.2 kHz e)
    [224858.795] (II) intel(0): Modeline "1920x1080"x0.0 74.25 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync (28.1 kHz e)
    [224858.795] (II) intel(0): Modeline "1440x576i"x0.0 27.00 1440 1464 1590 1728 576 580 586 625 interlace -hsync -vsync (15.6 kHz e)
    [224858.795] (II) intel(0): Modeline "1440x480i"x0.0 27.00 1440 1478 1602 1716 480 488 494 525 interlace -hsync -vsync (15.7 kHz e)
    [224858.795] (II) intel(0): Modeline "1280x720"x0.0 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e)
    [224858.795] (II) intel(0): Modeline "720x480"x0.0 27.00 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e)
    [224858.795] (II) intel(0): Modeline "1440x288"x0.0 27.00 1440 1464 1590 1728 288 290 293 312 -hsync -vsync (15.6 kHz e)
    [224858.795] (II) intel(0): Modeline "1440x240"x0.0 27.00 1440 1478 1602 1716 240 244 247 262 -hsync -vsync (15.7 kHz e)
    [224859.171] (II) intel(0): EDID vendor "SHP", prod id 4189
    [224859.171] (II) intel(0): Using hsync ranges from config file
    [224859.171] (II) intel(0): Using vrefresh ranges from config file
    [224859.171] (II) intel(0): Printing DDC gathered Modelines:
    [224859.171] (II) intel(0): Modeline "1920x1080"x0.0 148.50 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync (56.2 kHz eP)
    [224859.171] (II) intel(0): Modeline "1360x768"x0.0 85.50 1360 1424 1536 1792 768 771 777 795 +hsync +vsync (47.7 kHz e)
    [224859.171] (II) intel(0): Modeline "1920x1080"x0.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync (67.5 kHz e)
    [224859.171] (II) intel(0): Modeline "1920x1080i"x0.0 74.25 1920 2448 2492 2640 1080 1084 1094 1125 interlace +hsync +vsync (28.1 kHz e)
    [224859.171] (II) intel(0): Modeline "1920x1080i"x0.0 74.25 1920 2008 2052 2200 1080 1084 1094 1125 interlace +hsync +vsync (33.8 kHz e)
    [224859.171] (II) intel(0): Modeline "1280x720"x0.0 74.25 1280 1720 1760 1980 720 725 730 750 +hsync +vsync (37.5 kHz e)
    [224859.171] (II) intel(0): Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync (37.9 kHz e)
    [224859.171] (II) intel(0): Modeline "800x600"x0.0 36.00 800 824 896 1024 600 601 603 625 +hsync +vsync (35.2 kHz e)
    [224859.171] (II) intel(0): Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync (37.5 kHz e)
    [224859.171] (II) intel(0): Modeline "640x480"x0.0 31.50 640 664 704 832 480 489 492 520 -hsync -vsync (37.9 kHz e)
    [224859.171] (II) intel(0): Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync (31.5 kHz e)
    [224859.171] (II) intel(0): Modeline "720x400"x0.0 28.32 720 738 846 900 400 412 414 449 -hsync +vsync (31.5 kHz e)
    [224859.171] (II) intel(0): Modeline "1024x768"x0.0 78.75 1024 1040 1136 1312 768 769 772 800 +hsync +vsync (60.0 kHz e)
    [224859.171] (II) intel(0): Modeline "1024x768"x0.0 75.00 1024 1048 1184 1328 768 771 777 806 -hsync -vsync (56.5 kHz e)
    [224859.171] (II) intel(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz e)
    [224859.171] (II) intel(0): Modeline "800x600"x0.0 49.50 800 816 896 1056 600 601 604 625 +hsync +vsync (46.9 kHz e)
    [224859.171] (II) intel(0): Modeline "800x600"x0.0 50.00 800 856 976 1040 600 637 643 666 +hsync +vsync (48.1 kHz e)
    [224859.171] (II) intel(0): Modeline "1600x1200"x0.0 162.00 1600 1664 1856 2160 1200 1201 1204 1250 +hsync +vsync (75.0 kHz e)
    [224859.171] (II) intel(0): Modeline "1400x1050"x0.0 101.00 1400 1448 1480 1560 1050 1053 1057 1080 +hsync -vsync (64.7 kHz e)
    [224859.171] (II) intel(0): Modeline "1280x1024"x0.0 108.00 1280 1328 1440 1688 1024 1025 1028 1066 +hsync +vsync (64.0 kHz e)
    [224859.171] (II) intel(0): Modeline "1920x1080"x0.0 74.25 1920 2558 2602 2750 1080 1084 1089 1125 +hsync +vsync (27.0 kHz e)
    [224859.171] (II) intel(0): Modeline "720x576"x0.0 27.00 720 732 796 864 576 581 586 625 -hsync -vsync (31.2 kHz e)
    [224859.171] (II) intel(0): Modeline "1920x1080"x0.0 74.25 1920 2448 2492 2640 1080 1084 1089 1125 +hsync +vsync (28.1 kHz e)
    [224859.171] (II) intel(0): Modeline "1440x576i"x0.0 27.00 1440 1464 1590 1728 576 580 586 625 interlace -hsync -vsync (15.6 kHz e)
    [224859.171] (II) intel(0): Modeline "1440x480i"x0.0 27.00 1440 1478 1602 1716 480 488 494 525 interlace -hsync -vsync (15.7 kHz e)
    [224859.171] (II) intel(0): Modeline "1280x720"x0.0 74.25 1280 1390 1430 1650 720 725 730 750 +hsync +vsync (45.0 kHz e)
    [224859.171] (II) intel(0): Modeline "720x480"x0.0 27.00 720 736 798 858 480 489 495 525 -hsync -vsync (31.5 kHz e)
    [224859.171] (II) intel(0): Modeline "1440x288"x0.0 27.00 1440 1464 1590 1728 288 290 293 312 -hsync -vsync (15.6 kHz e)
    [224859.171] (II) intel(0): Modeline "1440x240"x0.0 27.00 1440 1478 1602 1716 240 244 247 262 -hsync -vsync (15.7 kHz e)
    this is the .initrc
    #!/bin/sh
    # ~/.xinitrc
    # Executed by startx (run your window manager from here)
    if [ -d /etc/X11/xinit/xinitrc.d ]; then
    for f in /etc/X11/xinit/xinitrc.d/*; do
    [ -x "$f" ] && . "$f"
    done
    unset f
    fi
    exec gnome-session
    # exec startkde
    # exec startxfce4
    # ...or the Window Manager of your choice

  • **SOLUTION** DLLML.exe Fails to load at startup (application error)

    Hello everyone!
    I purchased the SB X-Fi Fatalty Champion Edition soon after release, and think this is the best card I have ever used to date. Absolutely love it, unbelievable sound.
    Now a year or two ago I noticed a certain file failing to load when I started windows.
    This file, DLLML.exe. To my understanding this file is used to load EAX emulation support into older games/modules (essential loads a "middle-man" file between the game's sound files/.dll's, and the hardware SPU [Sound Processing Unit, not a real acronym, but that's what I call it since GPU and CPU are similar distincti've acronyms so if you see it used anywhere, it came from me ] to allow EAX support in non-EAX enabled games), and/or to add EAX effects in your audio files using the Wave Studio app.
    I've pinpointed this issue to either a Windows Update, or the Creative auto-update (which could mean it is an error caused by an installaion combination of multiple apps at once) because this issue did not arise until I did these two things (did Windows Update, then Creative Auto-Update, then restarted computer).
    Now I've primarily had this issue with Windows XP x64 but I have had this issue at times with Windows XP x86 as well.
    After you install the software suite, it adds an entry in your Windows Startup to load the module (Start/Run. msconfig. Startup tab. Look for STARTUP ITEM: DLLML). The entry looks like this:
    WinXPx86 looks like: "C:\Program Files\Creative\Shared Files\Module Loader\DLLML.exe" RCSystem * -Startup
    WinXPx64 looks like: "C:\Program Files (x86)\Creative\Shared Files\Module Loader\DLLML.exe" RCSystem * -Startup
    Under most circumstances this module loads fine, but because Creative, for reasons why I have not delved into, loads some of their DLL files differently than the Windows standard, which may also be a cause of this issue (extremely unlikely, I believe it is one of the 2 things i mentioned above).
    Either way, after I did those 2 things, the DLLML.exe startup entry failed to load every time.
    But I fixed it.
    Now what you have to do to resolve this issue, involves editing the startup entry in the Windows Registry.
    If you are scared to go into it, have no idea what I am talking about, or never edited the Registry before, don't worry. If you follow these steps EXACTLY, you have nothing to fear.
    I will be using default installation parameters for file pathing, so if your Operating System is installed in a different dri've letter other than C:\, then just change the letter to the one your OS is installed onto.
    Capitals used for emphesis on actions to take:
    -Hit the START button, then select RUN
    --------If RUN is not in your start menu, you need to enable it by right-clicking and open area of your TASKBAR, select PROPERTIES. --------Click the START MENU tab, then the CUSTOMIZE button. Click the ADVANCED tab. In the START MENU ITEMS box, scroll down to the entry that says SHOW RUN. Check the checkbox to fill it. Then OK/APPLY/OK, and you should be back to the desktop. Then go to START/RUN
    -type the word REGEDIT
    --------This opens the Windows Registry.
    --------DO NOT change ANYTHING in this other than the exact directions I specify or you may corrupt your registry or even worse, corrupt your system, which means F&R time (Format & Reinstall). Treat it like a stripper. You can look all you want but don't touch or there could be dire consequences.
    --------Now the fastest way to find this is to manually navigate to the specific "key" or "entry" you need to modify. Mouse-click the +'s to navitage further into the "hi've" following these maps:
    -FOR WINDOWS XP x86 USERS NAVIGATE TO: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Run
    -FOR WINDOWS XP x64 USERS NAVITAGE TO: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432\Microsoft\Wind ows\CurrentVersion\Run
    --------Now you are looking for a specific entry NAME called RCSYSTEM. Depending on which version you are running. They are:
    -FOR WINDOWS XP x86 USERS: "C:\Program Files\Creative\Shared Files\Module Loader\DLLML.exe" RCSystem * -Startup
    -FOR WINDOWS XP x64 USERS: "C:\Program Files (x86)\Creative\Shared Files\Module Loader\DLLML.exe" RCSystem * -Startup
    -------Now we are going to edit the entry. What we need to do is get rid of that * (asterix) character in the name. I don't know why it is there, I'm thinking it may be a coding error. But in my WinXPx64, this was the culprit.
    -Double-click the RCSYSTEM key to edit it, and edit it so it looks EXACTLY LIKE THIS (If you're paranoid about doing something bad, COPY and PASTE this line pertaining to your installed OS. KEEP IN MIND THE INSTALLATION DRIVE LETTER, CHANGE FIRST LETTER IF NESCESSARY)
    -FOR WINDOWS XP x86 USERS: "C:\Program Files\Creative\Shared Files\Module Loader\DLLML.exe" RCSystem -Startup
    -FOR WINDOWS XP x64 USERS: "C:\Program Files (x86)\Creative\Shared Files\Module Loader\DLLML.exe" RCSystem -Startup
    -click OK button. Now it is changed.
    -------And we're DONE EDITING the Registry entry!
    -now go to FILE in the top-left menu, then select EXIT
    -RESTART your computer
    -------You should not receive the "DLLML.exe failed to load" (application error) again!!
    To check to see if it loaded into your system properly (as if not getting the error message anymore was proof enough it loaded properly), when you reboot back to the desktop, do the "three-fingered salute" (ctrl-alt-delete), then select the PROCESSES tab. Click on the IMAGE NAME heading to sort it alphabetically, and look for the name (WinXPx86) DLLML.exe or (WinXPx64) DLLML.exe *32.
    If you see it listed, it loaded!! CONGRATS, IT BE FIXED!!
    If this did not work for you, then your system is posessed, get a priest. I don't think a witchdoctor would give your comp good vibes O_o
    Hope this resolved it for you. Enjoy your EAX with Duke Nukem 3d again!
    EDIT: As a side note, I also noticed that since after this fix, my computer doesn't hang after sending the restart/shutdown killsignal, so I am wondering with people having similar hanging issues, if their issue could be resolved something similar to this.
    Just a thought for any admins/mods/users out there that know what they are doing that maybe wanna test that out.
    Sincerely,
    Jason Ostapyk
    3yr degree, MCP, CCNA, A+ certified, Specialised Electrician Class M Licensed

    G Kudos for a brilliant finding! After a Windows Hotfix on my XP SP3, when shutting down my PC I would wait for a program and then get an error that EAX was not responding before finally shutting down. On next reboot I lost sound on my PC. After running tests, the Direct Sound test failed pointing at EAX.
    This solution cured the problem. Again, kudos, job really well done!!!

  • Auto-update of 2120 startup application using compact flash

    Just getting started with a 2120, but have one "tricky" question.  I want to have my executable run off the controller's memory, not the compact flash; however I also want the executable to check for software updates on a compact flash card.  In other words, if there is a compact flash card present when the app (controller) starts, and the executable on it appears correct (size, name check), then copy the file to that controller's startup folder to replace the existing app...  The executable would bypass normal operation at that point, provide LED feedback to alert the user to reset the controller (& remove card), and "voilà"!  We have an almost automatic compact-flash updatable, self-starting application...
    Question(s):
    - do I need to worry about whether I'm building the app to the controller's memory, to compact flash, or locally (to later copy onto compact flash)?
    - are there any issues with having a program copy an update over itself in this way (different types of memory, when used, etc...)? Alternative would be to have a 2-stage app: 1 checks for update, launches the 2nd if no update (single app would be cleaner)
    - am I missing anything else?
    Thanks,
    Phil

    Hi!
      If I understand correctly... You can do following steps:
       - you develop your application for cFP2120, and download it to cFP's C: disk, then you can copy it to a compact flash. I am referring to a "developing" cFP2120.
       - in field, you have another cFP2120, running an application that you created before, and you insert compact flash with new exe.  You reboot controller.
       - the resident application checks for updates, and find it on CF card.  This boot application copies executable from CF to C: disk, (maybe better if you use .par extentions until opy does not finish!).
       - You manually (or programmatically) reboot controller with new application.
       This was my idea, but, because of customer doesn't asked me to proceed in implementing it, so I stopped, but I'm always interested in knowing if this can work.
       Some problems with this may be the coerence of libraries.....  Please, if you find this way succesful, let me know....
       Another possible solution is to use the "open VI reference" method, but I am not used with it.....
       Hope I wasn't too confusing
    graziano

  • Gnome 3.2 no applications

    Hello,
    after upgrading to gnome 3.2, all my applications are gone. But only in list of all applications. I have no categories and no applications in Activities list. I can run some app only when I write its name. Can anybody help me? I tried copy file from /etc/xdg.... but nothing.

    I'm not a gnome guy, but have you tried https://bbs.archlinux.org/viewtopic.php?id=127651 ?

  • Gnome won't refresh applications or date

    I read the Gnome documentation, and have installed Gnome and Gdm.
    I have gdm enabled to start with the system, and it loads and lets me login just fine.  However, I have been unable to change the date with gsettings or add applications to the menu (using .desktop files).
    As for the gsettings command, I ran it, and for a brief flash it changed, then it reverted back to the original format without the day of the month.  I checked the `get` version of the command, and it was still set to true, so I do not know how or why it reverted.
    I am totally stumped about adding applications as well.  I tried adding them to `~/.local/share/applications` as well as `/usr/share/applications`.  I couldn't find a way to refresh the list.  I tried restarting both gdm and gnome, as well as rebooting the system, and it still doesn't display my newly added .desktop files.
    I haven't seen anything in my logs that would explain the cause.  What am I missing?

    Gnome/Gdm are still not working right, and I still cannot:
    - Get the time displayed to include the day of the month
    - Add my own .desktop files to my ~/.local
    - Get Gdm to mirror the login to both monitors (I multipurpose one of them so having it on both is desirable)
    It'd be super if anyone could acknowledge any of these as being a problem in general, even if no fix is available.

  • Where can i find and edit startup applications

    After installing Word on my macbook pro, the application starts automatically when at startup. I would like to know where to find the list of startup items so I can edit this and others out.

    I have tried this, but when I go to the system preferences, user groups then log in items....THERE AREN'T ANY APPLICATIONS LISTED! Although I am only to prevent Word from opening, several other applications open, too- MAIL, iphoto ect. I'm usually pretty tech savvy, but this has me stumped! Every discussion I have seen regarding this says to do the same thing.
    I also tried your second recommendation regarding re-opening windows, but I don't think that relates to this, simply because I haven't even USED word AT ALL since I purchased and installed it.
    ...any other suggestions?

Maybe you are looking for

  • Background Processing, Selection Screens and Variants

    Hi All, I am having a little trouble Background Processing with Selection Screens and Variants. When a user runs my report and selects the option of background processing, then they select a checkbox. Once this is checked, they should go and fill in

  • Error 2014 during iSight recording

    I have been trying to record video through iSight on my Macbook Pro, but after a while (maybe roughly 20-30 minutes into the recording) the video starts getting choppy and it gives the error # 2014. Any ideas?

  • Final Cut Pro laggs my mac pro???

    Hey guys wats up...Well im new to Mac/Video I have a Mac Pro and using a Canon XH-G1 and I just got final cut studio 2 last week just getting use to it... Im an absolute newb to all of this. Im just wondering, when i shot my HD footage and was editin

  • Entry point is not defined

    Hi all, Im doing an File to Proxy scenario, in the R/3 side im getting the error as "Entry point is not defined", can anyone suggest as  what to do to resolve this issue. Regards Archanaa

  • Just what IS the procedure for App Store review (and resubmit)?

    So when I submit an app for the first time I understand why there would be a 1 week, even 2 week wait for someone at Apple to review it. Actually, it's quite a luxury to have Apple experts to review and test an app for me. Last time I did this, in ab