Session scope variables and weird behaviour of AdfContext()

Hello,
what is the best method and correct API to create a session scope variable?
I am currently using ADFContext().getCurrent().getSessionScope().get()/put(), but it looks like it has some problems: for some unkown reasons I loose the variable, that is get() returns null when called from a method of a (overridden)ViewRowImpl. Why does this happen?
Thanks you in advance

There are a couple of ways you can set values on a sessions scope but I would have to question if you really need a scope as high as session to accomplish what you want to do. At any rate, you should be able to store the value using the method you described but you could also try setting it using EL by using the setExpressionValue and resolveExpression methods in JSFUtils.java (you can find this in the latest fusion demo application). JSFUtils also has a getFromSession and storeOnSession that you could try.
With all that said I don't think it is good practice to access scope variables from your model layer. You should write your method in the ViewRowImpl class to accept the value as a method parameter and then pass the value in through the binding layer or when invoking the method from your bean class.

Similar Messages

  • Session-scope variable for JSP page used in a frame

    Hi,
    I don't know if there's a way to do this at the same time:
    (1)- assign session scope to a variable (in order to be able to retrieve recurrently the previous value each time the JSP is called);
    (2)- set its visibility in a way that it could be accessed only by the page that defines it. The JSP is used in a frameset along with an other JSP that can potentially define identical session-scoped variable (You understand why I want to keep them separate)
    session.setAttribute():
    seems not to be the thing I need
    pageContext.setAttribute():
    with SESSION_SCOPE, it behaves the same way as session.setAttribute(). with PAGE_SCOPE, condition (1) can't be satisfied.
    Does anybody have an idea ?
    Thanx in advance.

    I can see that you will not want to maintain two different files for every possible page on the site!
    It may be possible to do something like <frameset rows="*" cols="50%,*">
      <frame name="content1" src="file.jsp?frame=one" >
      <frame name="content2" src="file.jsp?frame=two" >
    </frameset>and then in the jsp<%
    String frame=request.getParameter("frame");
    session.setAttribute(frame+"AttributeName",attributeValue);
    %>This will set up two session attributes - "oneAttributeName" and "twoAttributeName". Depending on how many variables you have, this may prove just as difficult to maintain.
    You may end up having to simply pass url parameters between pages to maintain state within the individual frames, which is far from elegant also.
    I am interested in how you end up solving this one.

  • Error and weird behaviour in executable launch

    Hello folks,
    This post is regarding a weird behaviour i am experiencing with an executable i built. 
    LABVIEW version(Includes Runtime engine) LV2012 SP1 f3
    DAQmx: 9.6.1
    The behaviour is listed below in detail. 
    In a nutshell, the exectuable runs on the development computer but does not run on the Target computer. Also, Irresepctive of which PC i run the executable on, i cannot access the block diagram even after enabling debugging everywhere. 
    On the target PC, the app fires up but does not run further, no error codes appear on the screen, it's like the app freezes after firing up. And to add to the misery, i cannot access the block diagram to debug and know what's going on. 
    Also, I have tried including the dynamic vis to my build script. No bueno. 
    What I see on running the app is addressed below:
    TARGET COMPUTER:
    DAQmx 9.7 and LV2012 SP1 f4 RTE have been installed manually.
    App does not run: No broken run button, the app launches but does nothing when the vi is run. No error messages.
    The block diagram is still inaccessible, even after selecting the “Enable debugging” option in the build specifications.
    DEVELOPMENT COMPUTER:
    The app launches and runs perfectly.
    The block diagram is still inaccessible, even after selecting the “Enable debugging” option in the build specifications.
    DAQmx 9.7 and LV2012 SP1 f4 RTE were not installed as the app recognized the already installed Labview environment.
    Additional steps that I have tried,
     Created and ran only an executable on the target PC, the attempt was unsuccessful. The vi showed similar characteristics as mentioned above in the target PC section.
     Created and ran an installer with additional install options(LV2012 f4 RTE and DAQmx 9.7)on the target PC, the attempt was again unsuccessful. The vi showed similar characteristics as mentioned above in the target PC section.  No error messages.
     Tried both the steps mentioned above on the development computer and the attempts were successful. .
    To the best of my knowledge, I believe, the issue here is with the environment I am creating for the executable and the installer to run with/off of. After having carefully followed the installation procedure for the Run-Time Engine and the DAQmx drivers, I still do not know what I am missing. 
    Please advise.
    Thanks guys, 
    RP.

    Hey guys, 
    So, got the application to work. Almost. 
    The problem was that the executable was missing the hardware config from the Device. 
    Now, the new issue is as following: 
    The goal of the vi is to generate a report of the test conducted. So, the way the vi works is that, the second the vi is run, an empty word file is created with only the company logo,  
    Field headings, which are populated after the test is conducted. 
    The logo is a .jpg file, which has a relative path into the executable.
    The field heading are String constants wired into a 'concatenate strings.vi' which are in turn wired to into the report generation vis.
    What's happening is that when i run the app on the target pc, Only the logo appears on the word template. Even when i conduct the whole test and stop the vi, the results aren't populated in the word file. Which is a little weird.
    Does any one know whats doing that?
    Please refer to the attached word files.
    Right - It is the file format desired. 
    Wrong - It is the file format achieved. 
    Please advise.
    Thanks,
    RP. 
    Attachments:
    Right.docx ‏17 KB
    Wrong.docx ‏16 KB

  • Suggestion: JavaScript scope variables and event listeners

    Invoking Java from JavaScript in ADF Mobile is surprisingly efficient although it is still relatively expensive compared to plain HTML5/JavaScript/CSS stuff in the native UIWebView. But whenever you want to do something "dynamic" you have to revert to invoking Java, even for simple use cases. As far as I can see it as soon as you use listeners on components, managed beans or data controls you're in the Java world.
    Why not add similar concepts that are pure JavaScript implementations for performance. As an example I want to have a SelectOneButton component and depending on its state I want to enable/disable an InputText component. As far as I can see it I would need Java to make this happen. First, I would need a Java managed bean to keep the enabled/disabled state. Then I would set the value property of the SelectOneButton with an EL expression to this managed bean property, or for other scenarios use a Java based ActionListener to change the state. Then the InputText component could use an EL expression in its Disabled property.
    For this simple use case this would still perform fast, but real applications grow more complex.
    Why not have the option of creating JavaScript based managed "beans"? The could live on javaScriptPageFlowScope or javaScriptViewScope. Then the AMX components could reference this from EL and it would be even better if we can create pure javascript ActionListeners (or other listeners). This would make it similar to the choice with ADF Faces application between doing a server roundtrip with partial-page-rendering and using pure clientListeners and clientAttributes for optimal performance.
    For situations where we do need to power of Java, it would be great if we can access these javascript scope variables from Java.

    This is a good suggestion, Wilfred. We haven't gotten to this level of optimization in the framework yet. At some point it's likely we'll have an option for the developer to specify the layer to handle the method.
    Thanks

  • Access session scope variables from a filter

    I have a filter I am using to check if 2 people are loged in with the same user name.
    When my web app loads I store the user name in a class that has session scope.
    Is there a way for me to access this class from the Filter class?
    How do I access the session instance from this class?
    How do I pass parameters to the Filter class?
    Thank you,
    Al

    http://forum.java.sun.com/thread.jspa?threadID=5122925&tstart=0

  • Jsf session scope variables

    Hi All,
    How to set a variable which should be available throughout the session, I dont want to use session scoped managed beans for this.
    Using the following method is not working
    FacesContext.getCurrentInstance().getExternalContext().getRequestMap().put("variableName","value");is there any other way to set session scoped variables ?

    Got it working
    FacesContext.getCurrentInstance().getExternalContext().getSessionMap().put("variableName","value");This will make the variable session scoped
    Regards,
    Sai Krishna

  • JRE 1.4.x Plugin - Signed Applets and Weird Behaviour (Policy)

    Hello.
    I have recently experienced some strange behaviour related to signed applets and policy files in JRE 1.4.2-b28 ( a friend got the same behaviour in a flavour of 1.4.1-xx as well ). Both tests were on Windows 2000 Professional platforms.
    Initially my unsigned applet, which attempts socket connections to a server different from the download location, fails with security exceptions ( as expected ). Then I did the following to sign the applet jar and configure my environment
    Steps: 1) Import "trusted CA" certificate into ${java.home}/lib/security/cacerts. (JRE home outside the JDK)
    2) Signed the jar using jarsigner and a certificate generated from the "trusted CA" (Entrust CA and certificate).
    3) Imported the signing certificate into the Java plugin using import in the plugin control panel.
    4) Created a new keystore (keytool,jks) and imported the signing certificate into the keystore with alias "developer". The keystore is stored in the user home as .keystore.
    5) Created a .java.policy for the user and attaching the keystore in 4) to it. ( also stored in user home ).
    6) Used the policy tool to grant socketpermissions to the specific codebase ( testing with file:/C:/test/* initially ) signed by "developer"
    After this, when I ran the test page under IE 5.5SP2 and Netscape 7.1 it worked without any security exception. Ditto for using the appletviewer and the policy file I created for the user.
    The weird part occurred when I removed the policy entry from the user policy file. After doing this, Netscape and IE still allow the applet to execute - somehow remembering that it was granted permissions at some point. The appletviewer does not allow it to execute, generating security exceptions.
    It appears the old policy is being cached somewhere, but I cannot find where. If I replace the applet jar with an unsigned version it does fail in IE and Netscape. I tried cleaning the plugin cache and removing the "deployment.certs" files related to the users but still get the same behaviour.
    Does anyone know where the old policy information is being stored ? Does anyone know how to revoke the permissions so that I am restored to my original base environment ( no permissions for "designer" signed applets ) ? Would attempting to utilize the AccessController.doPriveleged( xxxx ) operations in JDK 1.4 avoid all of this confusion with policy files, keystores and certificate storage ? After all the messing about I would like a zero-footprint alternative ( or minimzed footprint anyway ).
    Any ideas would be most welcome.
    Regards,
    James.

    Hello Again.
    I am either enlightened or confused at this point. I found that as long as all of my related Jars are signed ( even by self-signed certificates ) I am granted SocketPermissions for calls outside of the originating server. Unsigned code is refused, but even when the Jars were signed using a self-signed certificate the Socket calls were allowed.
    Am I experiencing the appropriate behaviour in this case ( which would mean not having to utilize policy files to distribute an applet that uses calls to arbitrary servers - e.g. JavaMail ) or am I suffering from something damaged in my environment ?
    It has been a long time since I played with signed applets and I am having difficulty determining what operations require policy file entries/AccessController.doPrivileged() calls and which are granted when a user elects to trust a signed applet without policy.
    Any assistance in clearing up my confusion would be appreciated.
    Regards,
    James.

  • Random display switching and weird behaviour. [Solved]

    Hey guys and girls
    Have had Arch running smoothly for a few months now and have avoided posting for minor issues, because your forums are so ace and have been able to find everything I need. Have to say out of all the distros that I've tried Arch simply rocks, especially the AUR!
    Anyway, point of post is this. I'm running KDE and have had similar problems with all the distros I've tried. My machine is a Dell L501X with a Nvidia GT435 graphics card. When I plug my external monitor in (via DisplayPort) it is detected and I can extend it to that monitor, both via randr and via TwinView.
    The problem is that it randomly switches off extended monitor and either mirrors display or switches between 1 active monitor on either laptop or external. This behaviour can be provoked by a random key press, waking up from sleep, or a butterfly flapping its wings on the far side of the galaxy.
    I'm using the Nvidia 319 drivers which I understand have RandR 1.4 support.
    Can anyone suggest what might cause this behaviour? Where would be a good start to debug this? How I might stop it? 
    My xorg.conf :
    # nvidia-xconfig: X configuration file generated by nvidia-xconfig
    # nvidia-xconfig: version 319.17 (buildmeister@swio-display-x86-rhel47-06) Thu Apr 25 22:28:25 PDT 2013
    Section "ServerLayout"
    Identifier "Layout0"
    Screen 0 "Screen0" 0 0
    Screen 1 "Screen1" RightOf "Screen0"
    InputDevice "Keyboard0" "CoreKeyboard"
    InputDevice "Mouse0" "CorePointer"
    EndSection
    Section "Files"
    EndSection
    Section "InputDevice"
    # generated from default
    Identifier "Mouse0"
    Driver "mouse"
    Option "Protocol" "auto"
    Option "Device" "/dev/psaux"
    Option "Emulate3Buttons" "no"
    Option "ZAxisMapping" "4 5"
    EndSection
    Section "InputDevice"
    # generated from default
    Identifier "Keyboard0"
    Driver "kbd"
    EndSection
    Section "Monitor"
    Identifier "Monitor0"
    VendorName "Unknown"
    ModelName "Unknown"
    HorizSync 28.0 - 33.0
    VertRefresh 43.0 - 72.0
    Option "DFP-0"
    EndSection
    Section "Monitor"
    Identifier "Monitor1"
    VendorName "Unknown"
    ModelName "Unknown"
    HorizSync 30.0 - 83.0
    VertRefresh 56.0 - 76.0
    Option "DFP-3"
    EndSection
    Section "Device"
    Identifier "Device0"
    Driver "nvidia"
    Option "ConnectedMonitor" "DFP-0, DFP-3"
    Option "UseEdidDpi" "FALSE"
    Option "DPI" "96 x 96"
    VendorName "NVIDIA Corporation"
    BoardName "GeForce GT 435M"
    EndSection
    Section "Device"
    Identifier "Device1"
    Driver "nvidia"
    Option "ConnectedMonitor" "DFP-0, DFP-3"
    Option "UseEdidDpi" "FALSE"
    Option "DPI" "96 x 96"
    VendorName "NVIDIA Corporation"
    BoardName "GeForce GT 435M"
    EndSection
    Section "Screen"
    Identifier "Screen0"
    Device "Device0"
    Monitor "Monitor0"
    DefaultDepth 24
    SubSection "Display"
    Depth 24
    EndSubSection
    EndSection
    Section "Screen"
    Identifier "Screen1"
    Device "Device1"
    Monitor "Monitor1"
    DefaultDepth 24
    SubSection "Display"
    Depth 24
    EndSubSection
    EndSection
    EDIT:
    I've tracked either the cause, or symptom of problem to some entries in journalctl. This seems to happen accross all KDE installations and is sporadic. When this behavious is present I also notice that double tapping the brightness buttons on keyboard causes the monitors to switch.
    Journalctl entries:
    May 09 14:27:07 ianarch dbus[344]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper)
    May 09 14:27:07 ianarch org.kde.powerdevil.backlighthelper[1639]: QDBusConnection: system D-Bus connection created before QCoreApplication. Application may misbehave.
    May 09 14:27:07 ianarch dbus-daemon[344]: dbus[344]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
    May 09 14:27:07 ianarch dbus[344]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
    May 09 14:29:57 ianarch dbus-daemon[344]: dbus[344]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper)
    May 09 14:29:57 ianarch dbus[344]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper)
    May 09 14:29:57 ianarch org.kde.powerdevil.backlighthelper[1648]: QDBusConnection: system D-Bus connection created before QCoreApplication. Application may misbehave.
    May 09 14:29:57 ianarch dbus-daemon[344]: dbus[344]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
    May 09 14:29:57 ianarch dbus[344]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
    May 09 14:30:11 ianarch dbus-daemon[344]: dbus[344]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper)
    May 09 14:30:11 ianarch dbus[344]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper)
    May 09 14:30:11 ianarch org.kde.powerdevil.backlighthelper[1654]: QDBusConnection: system D-Bus connection created before QCoreApplication. Application may misbehave.
    May 09 14:30:11 ianarch dbus[344]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
    May 09 14:30:11 ianarch dbus-daemon[344]: dbus[344]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
    May 09 14:31:30 ianarch dbus-daemon[344]: dbus[344]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper)
    May 09 14:31:30 ianarch dbus[344]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper)
    May 09 14:31:30 ianarch org.kde.powerdevil.backlighthelper[1667]: QDBusConnection: system D-Bus connection created before QCoreApplication. Application may misbehave.
    May 09 14:31:30 ianarch dbus-daemon[344]: dbus[344]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
    May 09 14:31:30 ianarch dbus[344]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper'
    Last edited by Hutchism (2013-05-30 14:28:12)

    Ok, I'm still in KDE at the moment as I had quite a bit to do and e17 was slowing me down.
    Here's an updated xorg log. Scroll down to the bottom to see the random display changes. They're in the log, but no sign of what calls it...
    [ 45574.101]
    X.Org X Server 1.14.1
    Release Date: 2013-04-17
    [ 45574.101] X Protocol Version 11, Revision 0
    [ 45574.101] Build Operating System: Linux 3.8.7-1-ARCH x86_64
    [ 45574.101] Current Operating System: Linux ianarch 3.9.0-2-ARCH #1 SMP PREEMPT Tue Apr 30 09:48:29 CEST 2013 x86_64
    [ 45574.101] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=5c06846e-4730-4382-afa1-3b2bdea7d716 ro quiet
    [ 45574.101] Build Date: 17 April 2013 02:37:06PM
    [ 45574.101]
    [ 45574.101] Current version of pixman: 0.28.2
    [ 45574.101] Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    [ 45574.101] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 45574.101] (==) Log file: "/var/log/Xorg.0.log", Time: Wed May 8 09:03:03 2013
    [ 45574.132] (==) Using config file: "/etc/X11/xorg.conf"
    [ 45574.132] (==) Using config directory: "/etc/X11/xorg.conf.d"
    [ 45574.180] (==) ServerLayout "Layout0"
    [ 45574.180] (**) |-->Screen "Screen0" (0)
    [ 45574.180] (**) | |-->Monitor "Monitor0"
    [ 45574.180] (**) | |-->Device "Device0"
    [ 45574.180] (**) |-->Input Device "Keyboard0"
    [ 45574.180] (**) |-->Input Device "Mouse0"
    [ 45574.180] (**) Option "Xinerama" "0"
    [ 45574.180] (==) Automatically adding devices
    [ 45574.180] (==) Automatically enabling devices
    [ 45574.180] (==) Automatically adding GPU devices
    [ 45574.180] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
    [ 45574.180] Entry deleted from font path.
    [ 45574.245] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
    [ 45574.245] Entry deleted from font path.
    [ 45574.245] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
    [ 45574.245] (==) FontPath set to:
    /usr/share/fonts/misc/,
    /usr/share/fonts/TTF/,
    /usr/share/fonts/Type1/,
    /usr/share/fonts/100dpi/
    [ 45574.245] (==) ModulePath set to "/usr/lib/xorg/modules"
    [ 45574.245] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
    [ 45574.245] (WW) Disabling Keyboard0
    [ 45574.245] (WW) Disabling Mouse0
    [ 45574.245] (II) Loader magic: 0x7fcc20
    [ 45574.245] (II) Module ABI versions:
    [ 45574.245] X.Org ANSI C Emulation: 0.4
    [ 45574.245] X.Org Video Driver: 14.1
    [ 45574.245] X.Org XInput driver : 19.1
    [ 45574.246] X.Org Server Extension : 7.0
    [ 45574.246] (II) config/udev: Adding drm device (/dev/dri/card0)
    [ 45574.249] (--) PCI:*(0:2:0:0) 10de:0df2:1028:046e rev 161, Mem @ 0xcc000000/16777216, 0xd0000000/268435456, 0xce000000/33554432, I/O @ 0x00002000/128, BIOS @ 0x????????/524288
    [ 45574.249] Initializing built-in extension Generic Event Extension
    [ 45574.249] Initializing built-in extension SHAPE
    [ 45574.249] Initializing built-in extension MIT-SHM
    [ 45574.249] Initializing built-in extension XInputExtension
    [ 45574.249] Initializing built-in extension XTEST
    [ 45574.249] Initializing built-in extension BIG-REQUESTS
    [ 45574.249] Initializing built-in extension SYNC
    [ 45574.249] Initializing built-in extension XKEYBOARD
    [ 45574.249] Initializing built-in extension XC-MISC
    [ 45574.249] Initializing built-in extension SECURITY
    [ 45574.249] Initializing built-in extension XINERAMA
    [ 45574.249] Initializing built-in extension XFIXES
    [ 45574.264] Initializing built-in extension RENDER
    [ 45574.264] Initializing built-in extension RANDR
    [ 45574.264] Initializing built-in extension COMPOSITE
    [ 45574.264] Initializing built-in extension DAMAGE
    [ 45574.264] Initializing built-in extension MIT-SCREEN-SAVER
    [ 45574.264] Initializing built-in extension DOUBLE-BUFFER
    [ 45574.264] Initializing built-in extension RECORD
    [ 45574.264] Initializing built-in extension DPMS
    [ 45574.264] Initializing built-in extension X-Resource
    [ 45574.264] Initializing built-in extension XVideo
    [ 45574.264] Initializing built-in extension XVideo-MotionCompensation
    [ 45574.264] Initializing built-in extension XFree86-VidModeExtension
    [ 45574.264] Initializing built-in extension XFree86-DGA
    [ 45574.264] Initializing built-in extension XFree86-DRI
    [ 45574.265] Initializing built-in extension DRI2
    [ 45574.265] (II) LoadModule: "glx"
    [ 45574.331] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    [ 45574.495] (II) Module glx: vendor="NVIDIA Corporation"
    [ 45574.495] compiled for 4.0.2, module version = 1.0.0
    [ 45574.495] Module class: X.Org Server Extension
    [ 45574.495] (II) NVIDIA GLX Module 319.17 Thu Apr 25 21:41:50 PDT 2013
    [ 45574.495] Loading extension GLX
    [ 45574.495] (II) LoadModule: "nvidia"
    [ 45574.652] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
    [ 45574.700] (II) Module nvidia: vendor="NVIDIA Corporation"
    [ 45574.700] compiled for 4.0.2, module version = 1.0.0
    [ 45574.700] Module class: X.Org Video Driver
    [ 45574.745] (II) NVIDIA dlloader X Driver 319.17 Thu Apr 25 21:23:57 PDT 2013
    [ 45574.745] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
    [ 45574.745] (++) using VT number 7
    [ 45574.747] (II) Loading sub module "fb"
    [ 45574.747] (II) LoadModule: "fb"
    [ 45574.747] (II) Loading /usr/lib/xorg/modules/libfb.so
    [ 45574.811] (II) Module fb: vendor="X.Org Foundation"
    [ 45574.811] compiled for 1.14.1, module version = 1.0.0
    [ 45574.811] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 45574.811] (WW) Unresolved symbol: fbGetGCPrivateKey
    [ 45574.811] (II) Loading sub module "wfb"
    [ 45574.811] (II) LoadModule: "wfb"
    [ 45574.811] (II) Loading /usr/lib/xorg/modules/libwfb.so
    [ 45574.835] (II) Module wfb: vendor="X.Org Foundation"
    [ 45574.835] compiled for 1.14.1, module version = 1.0.0
    [ 45574.835] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 45574.835] (II) Loading sub module "shadow"
    [ 45574.835] (II) LoadModule: "shadow"
    [ 45574.856] (II) Loading /usr/lib/xorg/modules/libshadow.so
    [ 45574.856] (II) Module shadow: vendor="X.Org Foundation"
    [ 45574.856] compiled for 1.14.1, module version = 1.1.0
    [ 45574.856] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 45574.856] (II) Loading sub module "ramdac"
    [ 45574.856] (II) LoadModule: "ramdac"
    [ 45574.856] (II) Module "ramdac" already built-in
    [ 45574.856] (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
    [ 45574.856] (==) NVIDIA(0): RGB weight 888
    [ 45574.856] (==) NVIDIA(0): Default visual is TrueColor
    [ 45574.856] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
    [ 45574.856] (**) NVIDIA(0): Option "Stereo" "0"
    [ 45574.856] (**) NVIDIA(0): Option "nvidiaXineramaInfoOrder" "DFP-0"
    [ 45574.856] (**) NVIDIA(0): Option "UseEdidDpi" "FALSE"
    [ 45574.856] (**) NVIDIA(0): Option "DPI" "96 x 96"
    [ 45574.856] (**) NVIDIA(0): Stereo disabled by request
    [ 45574.856] (**) NVIDIA(0): Option "MetaModes" "DFP-0: nvidia-auto-select +0+0, DFP-3: 1920x1080 +1920+0"
    [ 45574.856] (**) NVIDIA(0): Enabling 2D acceleration
    [ 45575.121] (II) NVIDIA(GPU-0): Display (AU Optronics Corporation (DFP-0)) does not support
    [ 45575.121] (II) NVIDIA(GPU-0): NVIDIA 3D Vision stereo.
    [ 45575.121] (WW) NVIDIA(GPU-0): Unable to read EDID for display device DFP-3
    [ 45575.126] (II) NVIDIA(GPU-0): Display (DELL U2311H (DFP-3)) does not support NVIDIA 3D
    [ 45575.126] (II) NVIDIA(GPU-0): Vision stereo.
    [ 45575.128] (II) NVIDIA(0): NVIDIA GPU GeForce GT 435M (GF108) at PCI:2:0:0 (GPU-0)
    [ 45575.128] (--) NVIDIA(0): Memory: 2097152 kBytes
    [ 45575.128] (--) NVIDIA(0): VideoBIOS: 70.08.19.00.5d
    [ 45575.128] (II) NVIDIA(0): Detected PCI Express Link width: 16X
    [ 45575.150] (II) NVIDIA(GPU-0): Display (DELL U2311H (DFP-3)) does not support NVIDIA 3D
    [ 45575.150] (II) NVIDIA(GPU-0): Vision stereo.
    [ 45575.150] (--) NVIDIA(0): Valid display device(s) on GeForce GT 435M at PCI:2:0:0
    [ 45575.150] (--) NVIDIA(0): AU Optronics Corporation (DFP-0) (boot, connected)
    [ 45575.150] (--) NVIDIA(0): DFP-1
    [ 45575.150] (--) NVIDIA(0): DFP-2
    [ 45575.150] (--) NVIDIA(0): DELL U2311H (DFP-3) (connected)
    [ 45575.150] (--) NVIDIA(0): AU Optronics Corporation (DFP-0): 330.0 MHz maximum pixel clock
    [ 45575.150] (--) NVIDIA(0): AU Optronics Corporation (DFP-0): Internal Dual Link LVDS
    [ 45575.150] (--) NVIDIA(0): DFP-1: 165.0 MHz maximum pixel clock
    [ 45575.150] (--) NVIDIA(0): DFP-1: Internal Single Link TMDS
    [ 45575.150] (--) NVIDIA(0): DFP-2: 165.0 MHz maximum pixel clock
    [ 45575.150] (--) NVIDIA(0): DFP-2: Internal Single Link TMDS
    [ 45575.150] (--) NVIDIA(0): DELL U2311H (DFP-3): 480.0 MHz maximum pixel clock
    [ 45575.150] (--) NVIDIA(0): DELL U2311H (DFP-3): Internal DisplayPort
    [ 45575.150] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45575.150] (**) NVIDIA(0): device AU Optronics Corporation (DFP-0) (Using EDID
    [ 45575.150] (**) NVIDIA(0): frequencies has been enabled on all display devices.)
    [ 45575.150] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45575.150] (**) NVIDIA(0): device DELL U2311H (DFP-3) (Using EDID frequencies has
    [ 45575.150] (**) NVIDIA(0): been enabled on all display devices.)
    [ 45575.151] (II) NVIDIA(0): Validated MetaModes:
    [ 45575.151] (II) NVIDIA(0): "DFP-0:nvidia-auto-select+0+0,DFP-3:1920x1080+1920+0"
    [ 45575.151] (II) NVIDIA(0): Virtual screen size determined to be 3840 x 1080
    [ 45576.221] (**) NVIDIA(0): DPI set to (96, 96); computed from "DPI" X config option
    [ 45576.221] (--) Depth 24 pixmap format is 32 bpp
    [ 45576.221] (II) NVIDIA: Using 3072.00 MB of virtual memory for indirect memory
    [ 45576.221] (II) NVIDIA: access.
    [ 45576.325] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
    [ 45576.325] (II) NVIDIA(0): may not be running or the "AcpidSocketPath" X
    [ 45576.325] (II) NVIDIA(0): configuration option may not be set correctly. When the
    [ 45576.325] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
    [ 45576.326] (II) NVIDIA(0): try to use it to receive ACPI event notifications. For
    [ 45576.326] (II) NVIDIA(0): details, please see the "ConnectToAcpid" and
    [ 45576.326] (II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
    [ 45576.326] (II) NVIDIA(0): Config Options in the README.
    [ 45576.347] (II) NVIDIA(0): Setting mode "DFP-0:nvidia-auto-select+0+0,DFP-3:1920x1080+1920+0"
    [ 45576.690] Loading extension NV-GLX
    [ 45576.789] (==) NVIDIA(0): Disabling shared memory pixmaps
    [ 45576.789] (==) NVIDIA(0): Backing store disabled
    [ 45576.789] (==) NVIDIA(0): Silken mouse enabled
    [ 45576.789] (**) NVIDIA(0): DPMS enabled
    [ 45576.797] Loading extension NV-CONTROL
    [ 45576.797] Loading extension XINERAMA
    [ 45576.797] (II) Loading sub module "dri2"
    [ 45576.797] (II) LoadModule: "dri2"
    [ 45576.797] (II) Module "dri2" already built-in
    [ 45576.801] (II) NVIDIA(0): [DRI2] Setup complete
    [ 45576.801] (II) NVIDIA(0): [DRI2] VDPAU driver: nvidia
    [ 45576.801] (--) RandR disabled
    [ 45576.805] (II) Initializing extension GLX
    [ 45577.087] (II) config/udev: Adding input device Power Button (/dev/input/event6)
    [ 45577.087] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 45577.087] (II) LoadModule: "evdev"
    [ 45577.087] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [ 45577.095] (II) Module evdev: vendor="X.Org Foundation"
    [ 45577.095] compiled for 1.14.0, module version = 2.8.0
    [ 45577.095] Module class: X.Org XInput Driver
    [ 45577.095] ABI class: X.Org XInput driver, version 19.1
    [ 45577.095] (II) Using input driver 'evdev' for 'Power Button'
    [ 45577.095] (**) Power Button: always reports core events
    [ 45577.095] (**) evdev: Power Button: Device: "/dev/input/event6"
    [ 45577.096] (--) evdev: Power Button: Vendor 0 Product 0x1
    [ 45577.096] (--) evdev: Power Button: Found keys
    [ 45577.096] (II) evdev: Power Button: Configuring as keyboard
    [ 45577.096] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input6/event6"
    [ 45577.096] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
    [ 45577.096] (**) Option "xkb_rules" "evdev"
    [ 45577.096] (**) Option "xkb_model" "evdev"
    [ 45577.096] (**) Option "xkb_layout" "us"
    [ 45577.131] (II) config/udev: Adding input device Video Bus (/dev/input/event2)
    [ 45577.131] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
    [ 45577.131] (II) Using input driver 'evdev' for 'Video Bus'
    [ 45577.131] (**) Video Bus: always reports core events
    [ 45577.131] (**) evdev: Video Bus: Device: "/dev/input/event2"
    [ 45577.131] (--) evdev: Video Bus: Vendor 0 Product 0x6
    [ 45577.131] (--) evdev: Video Bus: Found keys
    [ 45577.131] (II) evdev: Video Bus: Configuring as keyboard
    [ 45577.131] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:00/LNXVIDEO:00/input/input2/event2"
    [ 45577.131] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
    [ 45577.131] (**) Option "xkb_rules" "evdev"
    [ 45577.131] (**) Option "xkb_model" "evdev"
    [ 45577.131] (**) Option "xkb_layout" "us"
    [ 45577.132] (II) config/udev: Adding input device Power Button (/dev/input/event3)
    [ 45577.132] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 45577.132] (II) Using input driver 'evdev' for 'Power Button'
    [ 45577.132] (**) Power Button: always reports core events
    [ 45577.132] (**) evdev: Power Button: Device: "/dev/input/event3"
    [ 45577.132] (--) evdev: Power Button: Vendor 0 Product 0x1
    [ 45577.132] (--) evdev: Power Button: Found keys
    [ 45577.132] (II) evdev: Power Button: Configuring as keyboard
    [ 45577.132] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input3/event3"
    [ 45577.132] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 8)
    [ 45577.132] (**) Option "xkb_rules" "evdev"
    [ 45577.132] (**) Option "xkb_model" "evdev"
    [ 45577.132] (**) Option "xkb_layout" "us"
    [ 45577.133] (II) config/udev: Adding input device Lid Switch (/dev/input/event5)
    [ 45577.133] (II) No input driver specified, ignoring this device.
    [ 45577.133] (II) This device may have been added with another device file.
    [ 45577.134] (II) config/udev: Adding input device Sleep Button (/dev/input/event4)
    [ 45577.134] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
    [ 45577.134] (II) Using input driver 'evdev' for 'Sleep Button'
    [ 45577.134] (**) Sleep Button: always reports core events
    [ 45577.134] (**) evdev: Sleep Button: Device: "/dev/input/event4"
    [ 45577.134] (--) evdev: Sleep Button: Vendor 0 Product 0x3
    [ 45577.134] (--) evdev: Sleep Button: Found keys
    [ 45577.134] (II) evdev: Sleep Button: Configuring as keyboard
    [ 45577.134] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input4/event4"
    [ 45577.134] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 9)
    [ 45577.134] (**) Option "xkb_rules" "evdev"
    [ 45577.134] (**) Option "xkb_model" "evdev"
    [ 45577.134] (**) Option "xkb_layout" "us"
    [ 45577.135] (II) config/udev: Adding drm device (/dev/dri/card0)
    [ 45577.135] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=9 (/dev/input/event13)
    [ 45577.135] (II) No input driver specified, ignoring this device.
    [ 45577.135] (II) This device may have been added with another device file.
    [ 45577.135] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event14)
    [ 45577.135] (II) No input driver specified, ignoring this device.
    [ 45577.135] (II) This device may have been added with another device file.
    [ 45577.136] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event15)
    [ 45577.136] (II) No input driver specified, ignoring this device.
    [ 45577.136] (II) This device may have been added with another device file.
    [ 45577.136] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event16)
    [ 45577.136] (II) No input driver specified, ignoring this device.
    [ 45577.136] (II) This device may have been added with another device file.
    [ 45577.136] (II) config/udev: Adding input device Laptop_Integrated_Webcam_2HDM (/dev/input/event17)
    [ 45577.136] (**) Laptop_Integrated_Webcam_2HDM: Applying InputClass "evdev keyboard catchall"
    [ 45577.136] (II) Using input driver 'evdev' for 'Laptop_Integrated_Webcam_2HDM'
    [ 45577.136] (**) Laptop_Integrated_Webcam_2HDM: always reports core events
    [ 45577.136] (**) evdev: Laptop_Integrated_Webcam_2HDM: Device: "/dev/input/event17"
    [ 45577.136] (--) evdev: Laptop_Integrated_Webcam_2HDM: Vendor 0x408 Product 0x2fb1
    [ 45577.136] (--) evdev: Laptop_Integrated_Webcam_2HDM: Found keys
    [ 45577.136] (II) evdev: Laptop_Integrated_Webcam_2HDM: Configuring as keyboard
    [ 45577.136] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/input/input17/event17"
    [ 45577.136] (II) XINPUT: Adding extended input device "Laptop_Integrated_Webcam_2HDM" (type: KEYBOARD, id 10)
    [ 45577.136] (**) Option "xkb_rules" "evdev"
    [ 45577.136] (**) Option "xkb_model" "evdev"
    [ 45577.136] (**) Option "xkb_layout" "us"
    [ 45577.137] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event8)
    [ 45577.137] (II) No input driver specified, ignoring this device.
    [ 45577.137] (II) This device may have been added with another device file.
    [ 45577.137] (II) config/udev: Adding input device HDA Intel MID Headphone (/dev/input/event10)
    [ 45577.137] (II) No input driver specified, ignoring this device.
    [ 45577.137] (II) This device may have been added with another device file.
    [ 45577.138] (II) config/udev: Adding input device HDA Intel MID Headphone (/dev/input/event11)
    [ 45577.138] (II) No input driver specified, ignoring this device.
    [ 45577.138] (II) This device may have been added with another device file.
    [ 45577.138] (II) config/udev: Adding input device HDA Intel MID Mic (/dev/input/event9)
    [ 45577.138] (II) No input driver specified, ignoring this device.
    [ 45577.138] (II) This device may have been added with another device file.
    [ 45577.139] (II) config/udev: Adding input device Logitech Gaming Mouse G400 (/dev/input/event1)
    [ 45577.139] (**) Logitech Gaming Mouse G400: Applying InputClass "evdev pointer catchall"
    [ 45577.139] (II) Using input driver 'evdev' for 'Logitech Gaming Mouse G400'
    [ 45577.139] (**) Logitech Gaming Mouse G400: always reports core events
    [ 45577.139] (**) evdev: Logitech Gaming Mouse G400: Device: "/dev/input/event1"
    [ 45577.139] (--) evdev: Logitech Gaming Mouse G400: Vendor 0x46d Product 0xc245
    [ 45577.139] (--) evdev: Logitech Gaming Mouse G400: Found 12 mouse buttons
    [ 45577.139] (--) evdev: Logitech Gaming Mouse G400: Found scroll wheel(s)
    [ 45577.139] (--) evdev: Logitech Gaming Mouse G400: Found relative axes
    [ 45577.139] (--) evdev: Logitech Gaming Mouse G400: Found x and y relative axes
    [ 45577.139] (II) evdev: Logitech Gaming Mouse G400: Configuring as mouse
    [ 45577.139] (II) evdev: Logitech Gaming Mouse G400: Adding scrollwheel support
    [ 45577.139] (**) evdev: Logitech Gaming Mouse G400: YAxisMapping: buttons 4 and 5
    [ 45577.139] (**) evdev: Logitech Gaming Mouse G400: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [ 45577.139] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1c.3/0000:05:00.0/usb2/2-2/2-2.4/2-2.4:1.0/input/input20/event1"
    [ 45577.139] (II) XINPUT: Adding extended input device "Logitech Gaming Mouse G400" (type: MOUSE, id 11)
    [ 45577.139] (II) evdev: Logitech Gaming Mouse G400: initialized for relative axes.
    [ 45577.140] (**) Logitech Gaming Mouse G400: (accel) keeping acceleration scheme 1
    [ 45577.140] (**) Logitech Gaming Mouse G400: (accel) acceleration profile 0
    [ 45577.140] (**) Logitech Gaming Mouse G400: (accel) acceleration factor: 2.000
    [ 45577.140] (**) Logitech Gaming Mouse G400: (accel) acceleration threshold: 4
    [ 45577.140] (II) config/udev: Adding input device Logitech Gaming Mouse G400 (/dev/input/mouse0)
    [ 45577.140] (II) No input driver specified, ignoring this device.
    [ 45577.140] (II) This device may have been added with another device file.
    [ 45577.141] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
    [ 45577.141] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
    [ 45577.141] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
    [ 45577.141] (**) AT Translated Set 2 keyboard: always reports core events
    [ 45577.141] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event0"
    [ 45577.141] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
    [ 45577.141] (--) evdev: AT Translated Set 2 keyboard: Found keys
    [ 45577.141] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
    [ 45577.141] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
    [ 45577.141] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 12)
    [ 45577.141] (**) Option "xkb_rules" "evdev"
    [ 45577.141] (**) Option "xkb_model" "evdev"
    [ 45577.141] (**) Option "xkb_layout" "us"
    [ 45577.142] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event12)
    [ 45577.142] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "evdev touchpad catchall"
    [ 45577.142] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad catchall"
    [ 45577.142] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "Default clickpad buttons"
    [ 45577.142] (II) LoadModule: "synaptics"
    [ 45577.142] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
    [ 45577.155] (II) Module synaptics: vendor="X.Org Foundation"
    [ 45577.156] compiled for 1.14.0, module version = 1.7.0
    [ 45577.156] Module class: X.Org XInput Driver
    [ 45577.156] ABI class: X.Org XInput driver, version 19.1
    [ 45577.156] (II) Using input driver 'synaptics' for 'SynPS/2 Synaptics TouchPad'
    [ 45577.156] (**) SynPS/2 Synaptics TouchPad: always reports core events
    [ 45577.156] (**) Option "Device" "/dev/input/event12"
    [ 45577.182] (II) synaptics: SynPS/2 Synaptics TouchPad: ignoring touch events for semi-multitouch device
    [ 45577.182] (--) synaptics: SynPS/2 Synaptics TouchPad: x-axis range 1472 - 5398 (res 42)
    [ 45577.182] (--) synaptics: SynPS/2 Synaptics TouchPad: y-axis range 1408 - 4728 (res 70)
    [ 45577.182] (--) synaptics: SynPS/2 Synaptics TouchPad: pressure range 0 - 255
    [ 45577.182] (--) synaptics: SynPS/2 Synaptics TouchPad: finger width range 0 - 15
    [ 45577.182] (--) synaptics: SynPS/2 Synaptics TouchPad: buttons: left right double triple
    [ 45577.182] (--) synaptics: SynPS/2 Synaptics TouchPad: Vendor 0x2 Product 0x7
    [ 45577.182] (**) Option "TapButton1" "1"
    [ 45577.182] (**) Option "TapButton2" "2"
    [ 45577.182] (**) Option "TapButton3" "3"
    [ 45577.182] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
    [ 45577.182] (**) SynPS/2 Synaptics TouchPad: always reports core events
    [ 45577.185] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input12/event12"
    [ 45577.185] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD, id 13)
    [ 45577.185] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MinSpeed is now constant deceleration 2.5
    [ 45577.185] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MaxSpeed is now 1.75
    [ 45577.185] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) AccelFactor is now 0.039
    [ 45577.186] (**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
    [ 45577.186] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration profile 1
    [ 45577.186] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
    [ 45577.186] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
    [ 45577.186] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
    [ 45577.186] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse1)
    [ 45577.186] (**) SynPS/2 Synaptics TouchPad: Ignoring device from InputClass "touchpad ignore duplicates"
    [ 45577.187] (II) config/udev: Adding input device Dell WMI hotkeys (/dev/input/event7)
    [ 45577.187] (**) Dell WMI hotkeys: Applying InputClass "evdev keyboard catchall"
    [ 45577.187] (II) Using input driver 'evdev' for 'Dell WMI hotkeys'
    [ 45577.187] (**) Dell WMI hotkeys: always reports core events
    [ 45577.187] (**) evdev: Dell WMI hotkeys: Device: "/dev/input/event7"
    [ 45577.187] (--) evdev: Dell WMI hotkeys: Vendor 0 Product 0
    [ 45577.187] (--) evdev: Dell WMI hotkeys: Found keys
    [ 45577.187] (II) evdev: Dell WMI hotkeys: Configuring as keyboard
    [ 45577.187] (**) Option "config_info" "udev:/sys/devices/virtual/input/input7/event7"
    [ 45577.187] (II) XINPUT: Adding extended input device "Dell WMI hotkeys" (type: KEYBOARD, id 14)
    [ 45577.187] (**) Option "xkb_rules" "evdev"
    [ 45577.187] (**) Option "xkb_model" "evdev"
    [ 45577.187] (**) Option "xkb_layout" "us"
    [ 45614.071] (II) NVIDIA(GPU-0): Display (AU Optronics Corporation (DFP-0)) does not support
    [ 45614.071] (II) NVIDIA(GPU-0): NVIDIA 3D Vision stereo.
    [ 45614.072] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45614.072] (**) NVIDIA(0): device AU Optronics Corporation (DFP-0) (Using EDID
    [ 45614.072] (**) NVIDIA(0): frequencies has been enabled on all display devices.)
    [ 45614.072] (II) NVIDIA(GPU-0): Display (DELL U2311H (DFP-3)) does not support NVIDIA 3D
    [ 45614.072] (II) NVIDIA(GPU-0): Vision stereo.
    [ 45614.072] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45614.072] (**) NVIDIA(0): device DELL U2311H (DFP-3) (Using EDID frequencies has
    [ 45614.072] (**) NVIDIA(0): been enabled on all display devices.)
    [ 45738.889] (II) NVIDIA(GPU-0): Display (AU Optronics Corporation (DFP-0)) does not support
    [ 45738.889] (II) NVIDIA(GPU-0): NVIDIA 3D Vision stereo.
    [ 45738.889] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45738.889] (**) NVIDIA(0): device AU Optronics Corporation (DFP-0) (Using EDID
    [ 45738.889] (**) NVIDIA(0): frequencies has been enabled on all display devices.)
    [ 45738.890] (II) NVIDIA(GPU-0): Display (DELL U2311H (DFP-3)) does not support NVIDIA 3D
    [ 45738.890] (II) NVIDIA(GPU-0): Vision stereo.
    [ 45738.890] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45738.890] (**) NVIDIA(0): device DELL U2311H (DFP-3) (Using EDID frequencies has
    [ 45738.890] (**) NVIDIA(0): been enabled on all display devices.)
    [ 45738.958] (II) NVIDIA(GPU-0): Display (AU Optronics Corporation (DFP-0)) does not support
    [ 45738.958] (II) NVIDIA(GPU-0): NVIDIA 3D Vision stereo.
    [ 45738.958] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45738.958] (**) NVIDIA(0): device AU Optronics Corporation (DFP-0) (Using EDID
    [ 45738.958] (**) NVIDIA(0): frequencies has been enabled on all display devices.)
    [ 45738.958] (II) NVIDIA(GPU-0): Display (DELL U2311H (DFP-3)) does not support NVIDIA 3D
    [ 45738.958] (II) NVIDIA(GPU-0): Vision stereo.
    [ 45738.958] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45738.958] (**) NVIDIA(0): device DELL U2311H (DFP-3) (Using EDID frequencies has
    [ 45738.958] (**) NVIDIA(0): been enabled on all display devices.)
    [ 45738.984] (II) NVIDIA(GPU-0): Display (AU Optronics Corporation (DFP-0)) does not support
    [ 45738.984] (II) NVIDIA(GPU-0): NVIDIA 3D Vision stereo.
    [ 45738.984] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45738.984] (**) NVIDIA(0): device AU Optronics Corporation (DFP-0) (Using EDID
    [ 45738.984] (**) NVIDIA(0): frequencies has been enabled on all display devices.)
    [ 45738.984] (II) NVIDIA(GPU-0): Display (DELL U2311H (DFP-3)) does not support NVIDIA 3D
    [ 45738.984] (II) NVIDIA(GPU-0): Vision stereo.
    [ 45738.984] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45738.984] (**) NVIDIA(0): device DELL U2311H (DFP-3) (Using EDID frequencies has
    [ 45738.984] (**) NVIDIA(0): been enabled on all display devices.)
    [ 45739.077] (II) NVIDIA(0): Setting mode "LVDS-0: nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}"
    [ 45740.602] (II) NVIDIA(GPU-0): Display (AU Optronics Corporation (DFP-0)) does not support
    [ 45740.602] (II) NVIDIA(GPU-0): NVIDIA 3D Vision stereo.
    [ 45740.602] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45740.602] (**) NVIDIA(0): device AU Optronics Corporation (DFP-0) (Using EDID
    [ 45740.602] (**) NVIDIA(0): frequencies has been enabled on all display devices.)
    [ 45740.603] (II) NVIDIA(GPU-0): Display (DELL U2311H (DFP-3)) does not support NVIDIA 3D
    [ 45740.603] (II) NVIDIA(GPU-0): Vision stereo.
    [ 45740.603] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45740.603] (**) NVIDIA(0): device DELL U2311H (DFP-3) (Using EDID frequencies has
    [ 45740.603] (**) NVIDIA(0): been enabled on all display devices.)
    [ 45740.633] (II) NVIDIA(GPU-0): Display (AU Optronics Corporation (DFP-0)) does not support
    [ 45740.633] (II) NVIDIA(GPU-0): NVIDIA 3D Vision stereo.
    [ 45740.633] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45740.633] (**) NVIDIA(0): device AU Optronics Corporation (DFP-0) (Using EDID
    [ 45740.633] (**) NVIDIA(0): frequencies has been enabled on all display devices.)
    [ 45740.633] (II) NVIDIA(GPU-0): Display (DELL U2311H (DFP-3)) does not support NVIDIA 3D
    [ 45740.633] (II) NVIDIA(GPU-0): Vision stereo.
    [ 45740.633] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45740.633] (**) NVIDIA(0): device DELL U2311H (DFP-3) (Using EDID frequencies has
    [ 45740.633] (**) NVIDIA(0): been enabled on all display devices.)
    [ 45740.644] (II) NVIDIA(GPU-0): Display (AU Optronics Corporation (DFP-0)) does not support
    [ 45740.644] (II) NVIDIA(GPU-0): NVIDIA 3D Vision stereo.
    [ 45740.644] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45740.644] (**) NVIDIA(0): device AU Optronics Corporation (DFP-0) (Using EDID
    [ 45740.644] (**) NVIDIA(0): frequencies has been enabled on all display devices.)
    [ 45740.645] (II) NVIDIA(GPU-0): Display (DELL U2311H (DFP-3)) does not support NVIDIA 3D
    [ 45740.645] (II) NVIDIA(GPU-0): Vision stereo.
    [ 45740.645] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45740.645] (**) NVIDIA(0): device DELL U2311H (DFP-3) (Using EDID frequencies has
    [ 45740.645] (**) NVIDIA(0): been enabled on all display devices.)
    [ 45740.652] (II) NVIDIA(GPU-0): Display (AU Optronics Corporation (DFP-0)) does not support
    [ 45740.652] (II) NVIDIA(GPU-0): NVIDIA 3D Vision stereo.
    [ 45740.652] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45740.652] (**) NVIDIA(0): device AU Optronics Corporation (DFP-0) (Using EDID
    [ 45740.652] (**) NVIDIA(0): frequencies has been enabled on all display devices.)
    [ 45740.653] (II) NVIDIA(GPU-0): Display (DELL U2311H (DFP-3)) does not support NVIDIA 3D
    [ 45740.653] (II) NVIDIA(GPU-0): Vision stereo.
    [ 45740.653] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45740.653] (**) NVIDIA(0): device DELL U2311H (DFP-3) (Using EDID frequencies has
    [ 45740.653] (**) NVIDIA(0): been enabled on all display devices.)
    [ 45740.656] (II) NVIDIA(GPU-0): Display (AU Optronics Corporation (DFP-0)) does not support
    [ 45740.656] (II) NVIDIA(GPU-0): NVIDIA 3D Vision stereo.
    [ 45740.656] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45740.656] (**) NVIDIA(0): device AU Optronics Corporation (DFP-0) (Using EDID
    [ 45740.656] (**) NVIDIA(0): frequencies has been enabled on all display devices.)
    [ 45740.657] (II) NVIDIA(GPU-0): Display (DELL U2311H (DFP-3)) does not support NVIDIA 3D
    [ 45740.657] (II) NVIDIA(GPU-0): Vision stereo.
    [ 45740.657] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45740.657] (**) NVIDIA(0): device DELL U2311H (DFP-3) (Using EDID frequencies has
    [ 45740.657] (**) NVIDIA(0): been enabled on all display devices.)
    [ 45740.660] (II) NVIDIA(GPU-0): Display (AU Optronics Corporation (DFP-0)) does not support
    [ 45740.660] (II) NVIDIA(GPU-0): NVIDIA 3D Vision stereo.
    [ 45740.660] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45740.660] (**) NVIDIA(0): device AU Optronics Corporation (DFP-0) (Using EDID
    [ 45740.660] (**) NVIDIA(0): frequencies has been enabled on all display devices.)
    [ 45740.661] (II) NVIDIA(GPU-0): Display (DELL U2311H (DFP-3)) does not support NVIDIA 3D
    [ 45740.661] (II) NVIDIA(GPU-0): Vision stereo.
    [ 45740.661] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45740.661] (**) NVIDIA(0): device DELL U2311H (DFP-3) (Using EDID frequencies has
    [ 45740.661] (**) NVIDIA(0): been enabled on all display devices.)
    [ 45740.663] (II) NVIDIA(GPU-0): Display (AU Optronics Corporation (DFP-0)) does not support
    [ 45740.663] (II) NVIDIA(GPU-0): NVIDIA 3D Vision stereo.
    [ 45740.663] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45740.663] (**) NVIDIA(0): device AU Optronics Corporation (DFP-0) (Using EDID
    [ 45740.663] (**) NVIDIA(0): frequencies has been enabled on all display devices.)
    [ 45740.664] (II) NVIDIA(GPU-0): Display (DELL U2311H (DFP-3)) does not support NVIDIA 3D
    [ 45740.664] (II) NVIDIA(GPU-0): Vision stereo.
    [ 45740.664] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45740.664] (**) NVIDIA(0): device DELL U2311H (DFP-3) (Using EDID frequencies has
    [ 45740.664] (**) NVIDIA(0): been enabled on all display devices.)
    [ 45740.667] (II) NVIDIA(GPU-0): Display (AU Optronics Corporation (DFP-0)) does not support
    [ 45740.667] (II) NVIDIA(GPU-0): NVIDIA 3D Vision stereo.
    [ 45740.667] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45740.667] (**) NVIDIA(0): device AU Optronics Corporation (DFP-0) (Using EDID
    [ 45740.667] (**) NVIDIA(0): frequencies has been enabled on all display devices.)
    [ 45740.672] (II) NVIDIA(GPU-0): Display (DELL U2311H (DFP-3)) does not support NVIDIA 3D
    [ 45740.672] (II) NVIDIA(GPU-0): Vision stereo.
    [ 45740.672] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45740.672] (**) NVIDIA(0): device DELL U2311H (DFP-3) (Using EDID frequencies has
    [ 45740.672] (**) NVIDIA(0): been enabled on all display devices.)
    [ 45740.681] (II) NVIDIA(GPU-0): Display (AU Optronics Corporation (DFP-0)) does not support
    [ 45740.681] (II) NVIDIA(GPU-0): NVIDIA 3D Vision stereo.
    [ 45740.681] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45740.681] (**) NVIDIA(0): device AU Optronics Corporation (DFP-0) (Using EDID
    [ 45740.681] (**) NVIDIA(0): frequencies has been enabled on all display devices.)
    [ 45740.686] (II) NVIDIA(GPU-0): Display (DELL U2311H (DFP-3)) does not support NVIDIA 3D
    [ 45740.686] (II) NVIDIA(GPU-0): Vision stereo.
    [ 45740.686] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45740.686] (**) NVIDIA(0): device DELL U2311H (DFP-3) (Using EDID frequencies has
    [ 45740.686] (**) NVIDIA(0): been enabled on all display devices.)
    [ 45740.693] (II) NVIDIA(GPU-0): Display (AU Optronics Corporation (DFP-0)) does not support
    [ 45740.693] (II) NVIDIA(GPU-0): NVIDIA 3D Vision stereo.
    [ 45740.693] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45740.693] (**) NVIDIA(0): device AU Optronics Corporation (DFP-0) (Using EDID
    [ 45740.693] (**) NVIDIA(0): frequencies has been enabled on all display devices.)
    [ 45740.693] (II) NVIDIA(GPU-0): Display (DELL U2311H (DFP-3)) does not support NVIDIA 3D
    [ 45740.693] (II) NVIDIA(GPU-0): Vision stereo.
    [ 45740.694] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45740.694] (**) NVIDIA(0): device DELL U2311H (DFP-3) (Using EDID frequencies has
    [ 45740.694] (**) NVIDIA(0): been enabled on all display devices.)
    [ 45963.920] (II) NVIDIA(GPU-0): Display (AU Optronics Corporation (DFP-0)) does not support
    [ 45963.920] (II) NVIDIA(GPU-0): NVIDIA 3D Vision stereo.
    [ 45963.920] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45963.920] (**) NVIDIA(0): device AU Optronics Corporation (DFP-0) (Using EDID
    [ 45963.920] (**) NVIDIA(0): frequencies has been enabled on all display devices.)
    [ 45963.920] (II) NVIDIA(GPU-0): Display (DELL U2311H (DFP-3)) does not support NVIDIA 3D
    [ 45963.920] (II) NVIDIA(GPU-0): Vision stereo.
    [ 45963.920] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45963.920] (**) NVIDIA(0): device DELL U2311H (DFP-3) (Using EDID frequencies has
    [ 45963.920] (**) NVIDIA(0): been enabled on all display devices.)
    [ 45963.938] (II) NVIDIA(GPU-0): Display (AU Optronics Corporation (DFP-0)) does not support
    [ 45963.938] (II) NVIDIA(GPU-0): NVIDIA 3D Vision stereo.
    [ 45963.938] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45963.938] (**) NVIDIA(0): device AU Optronics Corporation (DFP-0) (Using EDID
    [ 45963.938] (**) NVIDIA(0): frequencies has been enabled on all display devices.)
    [ 45963.939] (II) NVIDIA(GPU-0): Display (DELL U2311H (DFP-3)) does not support NVIDIA 3D
    [ 45963.939] (II) NVIDIA(GPU-0): Vision stereo.
    [ 45963.939] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45963.939] (**) NVIDIA(0): device DELL U2311H (DFP-3) (Using EDID frequencies has
    [ 45963.939] (**) NVIDIA(0): been enabled on all display devices.)
    [ 45964.051] (II) NVIDIA(0): Setting mode "LVDS-0: nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}, DP-1: nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}"
    [ 45965.538] (II) NVIDIA(GPU-0): Display (AU Optronics Corporation (DFP-0)) does not support
    [ 45965.538] (II) NVIDIA(GPU-0): NVIDIA 3D Vision stereo.
    [ 45965.538] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45965.538] (**) NVIDIA(0): device AU Optronics Corporation (DFP-0) (Using EDID
    [ 45965.538] (**) NVIDIA(0): frequencies has been enabled on all display devices.)
    [ 45965.539] (II) NVIDIA(GPU-0): Display (DELL U2311H (DFP-3)) does not support NVIDIA 3D
    [ 45965.539] (II) NVIDIA(GPU-0): Vision stereo.
    [ 45965.539] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45965.539] (**) NVIDIA(0): device DELL U2311H (DFP-3) (Using EDID frequencies has
    [ 45965.539] (**) NVIDIA(0): been enabled on all display devices.)
    [ 45965.554] (II) NVIDIA(0): Setting mode "DP-1: nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}"
    [ 45966.777] (II) NVIDIA(GPU-0): Display (AU Optronics Corporation (DFP-0)) does not support
    [ 45966.777] (II) NVIDIA(GPU-0): NVIDIA 3D Vision stereo.
    [ 45966.777] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45966.777] (**) NVIDIA(0): device AU Optronics Corporation (DFP-0) (Using EDID
    [ 45966.777] (**) NVIDIA(0): frequencies has been enabled on all display devices.)
    [ 45966.777] (II) NVIDIA(GPU-0): Display (DELL U2311H (DFP-3)) does not support NVIDIA 3D
    [ 45966.777] (II) NVIDIA(GPU-0): Vision stereo.
    [ 45966.777] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45966.777] (**) NVIDIA(0): device DELL U2311H (DFP-3) (Using EDID frequencies has
    [ 45966.777] (**) NVIDIA(0): been enabled on all display devices.)
    [ 45966.792] (II) NVIDIA(GPU-0): Display (AU Optronics Corporation (DFP-0)) does not support
    [ 45966.792] (II) NVIDIA(GPU-0): NVIDIA 3D Vision stereo.
    [ 45966.792] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45966.792] (**) NVIDIA(0): device AU Optronics Corporation (DFP-0) (Using EDID
    [ 45966.792] (**) NVIDIA(0): frequencies has been enabled on all display devices.)
    [ 45966.792] (II) NVIDIA(GPU-0): Display (DELL U2311H (DFP-3)) does not support NVIDIA 3D
    [ 45966.792] (II) NVIDIA(GPU-0): Vision stereo.
    [ 45966.792] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45966.792] (**) NVIDIA(0): device DELL U2311H (DFP-3) (Using EDID frequencies has
    [ 45966.792] (**) NVIDIA(0): been enabled on all display devices.)
    [ 45966.799] (II) NVIDIA(GPU-0): Display (AU Optronics Corporation (DFP-0)) does not support
    [ 45966.799] (II) NVIDIA(GPU-0): NVIDIA 3D Vision stereo.
    [ 45966.799] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45966.799] (**) NVIDIA(0): device AU Optronics Corporation (DFP-0) (Using EDID
    [ 45966.799] (**) NVIDIA(0): frequencies has been enabled on all display devices.)
    [ 45966.800] (II) NVIDIA(GPU-0): Display (DELL U2311H (DFP-3)) does not support NVIDIA 3D
    [ 45966.800] (II) NVIDIA(GPU-0): Vision stereo.
    [ 45966.800] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45966.800] (**) NVIDIA(0): device DELL U2311H (DFP-3) (Using EDID frequencies has
    [ 45966.800] (**) NVIDIA(0): been enabled on all display devices.)
    [ 45966.804] (II) NVIDIA(GPU-0): Display (AU Optronics Corporation (DFP-0)) does not support
    [ 45966.804] (II) NVIDIA(GPU-0): NVIDIA 3D Vision stereo.
    [ 45966.804] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45966.804] (**) NVIDIA(0): device AU Optronics Corporation (DFP-0) (Using EDID
    [ 45966.804] (**) NVIDIA(0): frequencies has been enabled on all display devices.)
    [ 45966.804] (II) NVIDIA(GPU-0): Display (DELL U2311H (DFP-3)) does not support NVIDIA 3D
    [ 45966.804] (II) NVIDIA(GPU-0): Vision stereo.
    [ 45966.804] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45966.804] (**) NVIDIA(0): device DELL U2311H (DFP-3) (Using EDID frequencies has
    [ 45966.804] (**) NVIDIA(0): been enabled on all display devices.)
    [ 45966.807] (II) NVIDIA(GPU-0): Display (AU Optronics Corporation (DFP-0)) does not support
    [ 45966.807] (II) NVIDIA(GPU-0): NVIDIA 3D Vision stereo.
    [ 45966.807] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45966.807] (**) NVIDIA(0): device AU Optronics Corporation (DFP-0) (Using EDID
    [ 45966.807] (**) NVIDIA(0): frequencies has been enabled on all display devices.)
    [ 45966.807] (II) NVIDIA(GPU-0): Display (DELL U2311H (DFP-3)) does not support NVIDIA 3D
    [ 45966.807] (II) NVIDIA(GPU-0): Vision stereo.
    [ 45966.807] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45966.807] (**) NVIDIA(0): device DELL U2311H (DFP-3) (Using EDID frequencies has
    [ 45966.807] (**) NVIDIA(0): been enabled on all display devices.)
    [ 45966.811] (II) NVIDIA(GPU-0): Display (AU Optronics Corporation (DFP-0)) does not support
    [ 45966.811] (II) NVIDIA(GPU-0): NVIDIA 3D Vision stereo.
    [ 45966.811] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45966.811] (**) NVIDIA(0): device AU Optronics Corporation (DFP-0) (Using EDID
    [ 45966.811] (**) NVIDIA(0): frequencies has been enabled on all display devices.)
    [ 45966.811] (II) NVIDIA(GPU-0): Display (DELL U2311H (DFP-3)) does not support NVIDIA 3D
    [ 45966.812] (II) NVIDIA(GPU-0): Vision stereo.
    [ 45966.812] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45966.812] (**) NVIDIA(0): device DELL U2311H (DFP-3) (Using EDID frequencies has
    [ 45966.812] (**) NVIDIA(0): been enabled on all display devices.)
    [ 45966.814] (II) NVIDIA(GPU-0): Display (AU Optronics Corporation (DFP-0)) does not support
    [ 45966.814] (II) NVIDIA(GPU-0): NVIDIA 3D Vision stereo.
    [ 45966.814] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45966.814] (**) NVIDIA(0): device AU Optronics Corporation (DFP-0) (Using EDID
    [ 45966.814] (**) NVIDIA(0): frequencies has been enabled on all display devices.)
    [ 45966.815] (II) NVIDIA(GPU-0): Display (DELL U2311H (DFP-3)) does not support NVIDIA 3D
    [ 45966.815] (II) NVIDIA(GPU-0): Vision stereo.
    [ 45966.815] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45966.815] (**) NVIDIA(0): device DELL U2311H (DFP-3) (Using EDID frequencies has
    [ 45966.815] (**) NVIDIA(0): been enabled on all display devices.)
    [ 45966.818] (II) NVIDIA(GPU-0): Display (AU Optronics Corporation (DFP-0)) does not support
    [ 45966.818] (II) NVIDIA(GPU-0): NVIDIA 3D Vision stereo.
    [ 45966.818] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45966.818] (**) NVIDIA(0): device AU Optronics Corporation (DFP-0) (Using EDID
    [ 45966.818] (**) NVIDIA(0): frequencies has been enabled on all display devices.)
    [ 45966.818] (II) NVIDIA(GPU-0): Display (DELL U2311H (DFP-3)) does not support NVIDIA 3D
    [ 45966.818] (II) NVIDIA(GPU-0): Vision stereo.
    [ 45966.818] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45966.818] (**) NVIDIA(0): device DELL U2311H (DFP-3) (Using EDID frequencies has
    [ 45966.818] (**) NVIDIA(0): been enabled on all display devices.)
    [ 45966.823] (II) NVIDIA(GPU-0): Display (AU Optronics Corporation (DFP-0)) does not support
    [ 45966.823] (II) NVIDIA(GPU-0): NVIDIA 3D Vision stereo.
    [ 45966.823] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45966.823] (**) NVIDIA(0): device AU Optronics Corporation (DFP-0) (Using EDID
    [ 45966.823] (**) NVIDIA(0): frequencies has been enabled on all display devices.)
    [ 45966.823] (II) NVIDIA(GPU-0): Display (DELL U2311H (DFP-3)) does not support NVIDIA 3D
    [ 45966.823] (II) NVIDIA(GPU-0): Vision stereo.
    [ 45966.823] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45966.823] (**) NVIDIA(0): device DELL U2311H (DFP-3) (Using EDID frequencies has
    [ 45966.823] (**) NVIDIA(0): been enabled on all display devices.)
    [ 45966.826] (II) NVIDIA(GPU-0): Display (AU Optronics Corporation (DFP-0)) does not support
    [ 45966.826] (II) NVIDIA(GPU-0): NVIDIA 3D Vision stereo.
    [ 45966.826] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45966.826] (**) NVIDIA(0): device AU Optronics Corporation (DFP-0) (Using EDID
    [ 45966.826] (**) NVIDIA(0): frequencies has been enabled on all display devices.)
    [ 45966.827] (II) NVIDIA(GPU-0): Display (DELL U2311H (DFP-3)) does not support NVIDIA 3D
    [ 45966.827] (II) NVIDIA(GPU-0): Vision stereo.
    [ 45966.827] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45966.827] (**) NVIDIA(0): device DELL U2311H (DFP-3) (Using EDID frequencies has
    [ 45966.827] (**) NVIDIA(0): been enabled on all display devices.)
    [ 45966.829] (II) NVIDIA(GPU-0): Display (AU Optronics Corporation (DFP-0)) does not support
    [ 45966.829] (II) NVIDIA(GPU-0): NVIDIA 3D Vision stereo.
    [ 45966.829] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45966.829] (**) NVIDIA(0): device AU Optronics Corporation (DFP-0) (Using EDID
    [ 45966.829] (**) NVIDIA(0): frequencies has been enabled on all display devices.)
    [ 45966.830] (II) NVIDIA(GPU-0): Display (DELL U2311H (DFP-3)) does not support NVIDIA 3D
    [ 45966.830] (II) NVIDIA(GPU-0): Vision stereo.
    [ 45966.830] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45966.830] (**) NVIDIA(0): device DELL U2311H (DFP-3) (Using EDID frequencies has
    [ 45966.830] (**) NVIDIA(0): been enabled on all display devices.)
    [ 45966.837] (II) NVIDIA(GPU-0): Display (AU Optronics Corporation (DFP-0)) does not support
    [ 45966.837] (II) NVIDIA(GPU-0): NVIDIA 3D Vision stereo.
    [ 45966.837] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45966.837] (**) NVIDIA(0): device AU Optronics Corporation (DFP-0) (Using EDID
    [ 45966.837] (**) NVIDIA(0): frequencies has been enabled on all display devices.)
    [ 45966.837] (II) NVIDIA(GPU-0): Display (DELL U2311H (DFP-3)) does not support NVIDIA 3D
    [ 45966.837] (II) NVIDIA(GPU-0): Vision stereo.
    [ 45966.837] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45966.837] (**) NVIDIA(0): device DELL U2311H (DFP-3) (Using EDID frequencies has
    [ 45966.837] (**) NVIDIA(0): been enabled on all display devices.)
    [ 45966.839] (II) NVIDIA(GPU-0): Display (AU Optronics Corporation (DFP-0)) does not support
    [ 45966.839] (II) NVIDIA(GPU-0): NVIDIA 3D Vision stereo.
    [ 45966.839] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45966.839] (**) NVIDIA(0): device AU Optronics Corporation (DFP-0) (Using EDID
    [ 45966.839] (**) NVIDIA(0): frequencies has been enabled on all display devices.)
    [ 45966.839] (II) NVIDIA(GPU-0): Display (DELL U2311H (DFP-3)) does not support NVIDIA 3D
    [ 45966.839] (II) NVIDIA(GPU-0): Vision stereo.
    [ 45966.839] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45966.839] (**) NVIDIA(0): device DELL U2311H (DFP-3) (Using EDID frequencies has
    [ 45966.839] (**) NVIDIA(0): been enabled on all display devices.)
    [ 45966.842] (II) NVIDIA(GPU-0): Display (AU Optronics Corporation (DFP-0)) does not support
    [ 45966.842] (II) NVIDIA(GPU-0): NVIDIA 3D Vision stereo.
    [ 45966.842] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45966.842] (**) NVIDIA(0): device AU Optronics Corporation (DFP-0) (Using EDID
    [ 45966.842] (**) NVIDIA(0): frequencies has been enabled on all display devices.)
    [ 45966.842] (II) NVIDIA(GPU-0): Display (DELL U2311H (DFP-3)) does not support NVIDIA 3D
    [ 45966.842] (II) NVIDIA(GPU-0): Vision stereo.
    [ 45966.842] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45966.842] (**) NVIDIA(0): device DELL U2311H (DFP-3) (Using EDID frequencies has
    [ 45966.842] (**) NVIDIA(0): been enabled on all display devices.)
    [ 45966.846] (II) NVIDIA(GPU-0): Display (AU Optronics Corporation (DFP-0)) does not support
    [ 45966.846] (II) NVIDIA(GPU-0): NVIDIA 3D Vision stereo.
    [ 45966.846] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45966.846] (**) NVIDIA(0): device AU Optronics Corporation (DFP-0) (Using EDID
    [ 45966.846] (**) NVIDIA(0): frequencies has been enabled on all display devices.)
    [ 45966.846] (II) NVIDIA(GPU-0): Display (DELL U2311H (DFP-3)) does not support NVIDIA 3D
    [ 45966.846] (II) NVIDIA(GPU-0): Vision stereo.
    [ 45966.846] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45966.846] (**) NVIDIA(0): device DELL U2311H (DFP-3) (Using EDID frequencies has
    [ 45966.846] (**) NVIDIA(0): been enabled on all display devices.)
    [ 45966.849] (II) NVIDIA(GPU-0): Display (AU Optronics Corporation (DFP-0)) does not support
    [ 45966.849] (II) NVIDIA(GPU-0): NVIDIA 3D Vision stereo.
    [ 45966.849] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45966.849] (**) NVIDIA(0): device AU Optronics Corporation (DFP-0) (Using EDID
    [ 45966.849] (**) NVIDIA(0): frequencies has been enabled on all display devices.)
    [ 45966.850] (II) NVIDIA(GPU-0): Display (DELL U2311H (DFP-3)) does not support NVIDIA 3D
    [ 45966.850] (II) NVIDIA(GPU-0): Vision stereo.
    [ 45966.850] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 45966.850] (**) NVIDIA(0): device DELL U2311H (DFP-3) (Using EDID frequencies has
    [ 45966.850] (**) NVIDIA(0): been enabled on all display devices.)
    [ 46113.976] (II) NVIDIA(GPU-0): Display (AU Optronics Corporation (DFP-0)) does not support
    [ 46113.976] (II) NVIDIA(GPU-0): NVIDIA 3D Vision stereo.
    [ 46113.976] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 46113.976] (**) NVIDIA(0): device AU Optronics Corporation (DFP-0) (Using EDID
    [ 46113.976] (**) NVIDIA(0): frequencies has been enabled on all display devices.)
    [ 46113.977] (II) NVIDIA(GPU-0): Display (DELL U2311H (DFP-3)) does not support NVIDIA 3D
    [ 46113.977] (II) NVIDIA(GPU-0): Vision stereo.
    [ 46113.977] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 46113.977] (**) NVIDIA(0): device DELL U2311H (DFP-3) (Using EDID frequencies has
    [ 46113.977] (**) NVIDIA(0): been enabled on all display devices.)
    [ 46113.996] (II) NVIDIA(GPU-0): Display (AU Optronics Corporation (DFP-0)) does not support
    [ 46113.997] (II) NVIDIA(GPU-0): NVIDIA 3D Vision stereo.
    [ 46113.997] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 46113.997] (**) NVIDIA(0): device AU Optronics Corporation (DFP-0) (Using EDID
    [ 46113.997] (**) NVIDIA(0): frequencies has been enabled on all display devices.)
    [ 46113.998] (II) NVIDIA(GPU-0): Display (DELL U2311H (DFP-3)) does not support NVIDIA 3D
    [ 46113.998] (II) NVIDIA(GPU-0): Vision stereo.
    [ 46113.998] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 46113.998] (**) NVIDIA(0): device DELL U2311H (DFP-3) (Using EDID frequencies has
    [ 46113.998] (**) NVIDIA(0): been enabled on all display devices.)
    [ 46114.018] (II) NVIDIA(GPU-0): Display (AU Optronics Corporation (DFP-0)) does not support
    [ 46114.018] (II) NVIDIA(GPU-0): NVIDIA 3D Vision stereo.
    [ 46114.018] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 46114.018] (**) NVIDIA(0): device AU Optronics Corporation (DFP-0) (Using EDID
    [ 46114.018] (**) NVIDIA(0): frequencies has been enabled on all display devices.)
    [ 46114.019] (II) NVIDIA(GPU-0): Display (DELL U2311H (DFP-3)) does not support NVIDIA 3D
    [ 46114.019] (II) NVIDIA(GPU-0): Vision stereo.
    [ 46114.019] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 46114.019] (**) NVIDIA(0): device DELL U2311H (DFP-3) (Using EDID frequencies has
    [ 46114.019] (**) NVIDIA(0): been enabled on all display devices.)
    [ 46114.120] (II) NVIDIA(0): Setting mode "LVDS-0: nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}, DP-1: nvidia-auto-select @1920x1080 +0+0 {ViewPortIn=1920x1080, ViewPortOut=1920x1080+0+0}"
    [ 46114.574] (II) NVIDIA(GPU-0): Display (AU Optronics Corporation (DFP-0)) does not support
    [ 46114.574] (II) NVIDIA(GPU-0): NVIDIA 3D Vision stereo.
    [ 46114.574] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 46114.574] (**) NVIDIA(0): device AU Optronics Corporation (DFP-0) (Using EDID
    [ 46114.574] (**) NVIDIA(0): frequencies has been enabled on all display devices.)
    [ 46114.574] (II) NVIDIA(GPU-0): Display (DELL U2311H (DFP-3)) does not support NVIDIA 3D
    [ 46114.574] (II) NVIDIA(GPU-0): Vision stereo.
    [ 46114.574] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 46114.574] (**) NVIDIA(0): device DELL U2311H (DFP-3) (Using EDID frequencies has
    [ 46114.574] (**) NVIDIA(0): been enabled on all display devices.)
    [ 46114.577] (II) NVIDIA(GPU-0): Display (AU Optronics Corporation (DFP-0)) does not support
    [ 46114.577] (II) NVIDIA(GPU-0): NVIDIA 3D Vision stereo.
    [ 46114.577] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 46114.577] (**) NVIDIA(0): device AU Optronics Corporation (DFP-0) (Using EDID
    [ 46114.577] (**) NVIDIA(0): frequencies has been enabled on all display devices.)
    [ 46114.578] (II) NVIDIA(GPU-0): Display (DELL U2311H (DFP-3)) does not support NVIDIA 3D
    [ 46114.578] (II) NVIDIA(GPU-0): Vision stereo.
    [ 46114.578] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 46114.578] (**) NVIDIA(0): device DELL U2311H (DFP-3) (Using EDID frequencies has
    [ 46114.578] (**) NVIDIA(0): been enabled on all display devices.)
    [ 46114.580] (II) NVIDIA(GPU-0): Display (AU Optronics Corporation (DFP-0)) does not support
    [ 46114.580] (II) NVIDIA(GPU-0): NVIDIA 3D Vision stereo.
    [ 46114.580] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 46114.580] (**) NVIDIA(0): device AU Optronics Corporation (DFP-0) (Using EDID
    [ 46114.580] (**) NVIDIA(0): frequencies has been enabled on all display devices.)
    [ 46114.580] (II) NVIDIA(GPU-0): Display (DELL U2311H (DFP-3)) does not support NVIDIA 3D
    [ 46114.580] (II) NVIDIA(GPU-0): Vision stereo.
    [ 46114.580] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 46114.580] (**) NVIDIA(0): device DELL U2311H (DFP-3) (Using EDID frequencies has
    [ 46114.580] (**) NVIDIA(0): been enabled on all display devices.)
    [ 46114.583] (II) NVIDIA(GPU-0): Display (AU Optronics Corporation (DFP-0)) does not support
    [ 46114.583] (II) NVIDIA(GPU-0): NVIDIA 3D Vision stereo.
    [ 46114.584] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 46114.584] (**) NVIDIA(0): device AU Optronics Corporation (DFP-0) (Using EDID
    [ 46114.584] (**) NVIDIA(0): frequencies has been enabled on all display devices.)
    [ 46114.584] (II) NVIDIA(GPU-0): Display (DELL U2311H (DFP-3)) does not support NVIDIA 3D
    [ 46114.584] (II) NVIDIA(GPU-0): Vision stereo.
    [ 46114.584] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 46114.584] (**) NVIDIA(0): device DELL U2311H (DFP-3) (Using EDID frequencies has
    [ 46114.584] (**) NVIDIA(0): been enabled on all display devices.)
    [ 46114.588] (II) NVIDIA(GPU-0): Display (AU Optronics Corporation (DFP-0)) does not support
    [ 46114.588] (II) NVIDIA(GPU-0): NVIDIA 3D Vision stereo.
    [ 46114.588] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 46114.588] (**) NVIDIA(0): device AU Optronics Corporation (DFP-0) (Using EDID
    [ 46114.588] (**) NVIDIA(0): frequencies has been enabled on all display devices.)
    [ 46114.588] (II) NVIDIA(GPU-0): Display (DELL U2311H (DFP-3)) does not support NVIDIA 3D
    [ 46114.588] (II) NVIDIA(GPU-0): Vision stereo.
    [ 46114.588] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 46114.588] (**) NVIDIA(0): device DELL U2311H (DFP-3) (Using EDID frequencies has
    [ 46114.588] (**) NVIDIA(0): been enabled on all display devices.)
    [ 46114.591] (II) NVIDIA(GPU-0): Display (AU Optronics Corporation (DFP-0)) does not support
    [ 46114.591] (II) NVIDIA(GPU-0): NVIDIA 3D Vision stereo.
    [ 46114.591] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 46114.591] (**) NVIDIA(0): device AU Optronics Corporation (DFP-0) (Using EDID
    [ 46114.591] (**) NVIDIA(0): frequencies has been enabled on all display devices.)
    [ 46114.592] (II) NVIDIA(GPU-0): Display (DELL U2311H (DFP-3)) does not support NVIDIA 3D
    [ 46114.592] (II) NVIDIA(GPU-0): Vision stereo.
    [ 46114.592] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 46114.592] (**) NVIDIA(0): device DELL U2311H (DFP-3) (Using EDID frequencies has
    [ 46114.592] (**) NVIDIA(0): been enabled on all display devices.)
    [ 46114.596] (II) NVIDIA(GPU-0): Display (AU Optronics Corporation (DFP-0)) does not support
    [ 46114.596] (II) NVIDIA(GPU-0): NVIDIA 3D Vision stereo.
    [ 46114.596] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 46114.596] (**) NVIDIA(0): device AU Optronics Corporation (DFP-0) (Using EDID
    [ 46114.596] (**) NVIDIA(0): frequencies has been enabled on all display devices.)
    [ 46114.597] (II) NVIDIA(GPU-0): Display (DELL U2311H (DFP-3)) does not support NVIDIA 3D
    [ 46114.597] (II) NVIDIA(GPU-0): Vision stereo.
    [ 46114.597] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 46114.597] (**) NVIDIA(0): device DELL U2311H (DFP-3) (Using EDID frequencies has
    [ 46114.597] (**) NVIDIA(0): been enabled on all display devices.)
    [ 46114.608] (II) NVIDIA(GPU-0): Display (AU Optronics Corporation (DFP-0)) does not support
    [ 46114.608] (II) NVIDIA(GPU-0): NVIDIA 3D Vision stereo.
    [ 46114.608] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 46114.608] (**) NVIDIA(0): device AU Optronics Corporation (DFP-0) (Using EDID
    [ 46114.608] (**) NVIDIA(0): frequencies has been enabled on all display devices.)
    [ 46114.609] (II) NVIDIA(GPU-0): Display (DELL U2311H (DFP-3)) does not support NVIDIA 3D
    [ 46114.609] (II) NVIDIA(GPU-0): Vision stereo.
    [ 46114.609] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 46114.609] (**) NVIDIA(0): device DELL U2311H (DFP-3) (Using EDID frequencies has
    [ 46114.609] (**) NVIDIA(0): been enabled on all display devices.)
    [ 46114.611] (II) NVIDIA(GPU-0): Display (AU Optronics Corporation (DFP-0)) does not support
    [ 46114.611] (II) NVIDIA(GPU-0): NVIDIA 3D Vision stereo.
    [ 46114.611] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 46114.611] (**) NVIDIA(0): device AU Optronics Corporation (DFP-0) (Using EDID
    [ 46114.611] (**) NVIDIA(0): frequencies has been enabled on all display devices.)
    [ 46114.612] (II) NVIDIA(GPU-0): Display (DELL U2311H (DFP-3)) does not support NVIDIA 3D
    [ 46114.612] (II) NVIDIA(GPU-0): Vision stereo.
    [ 46114.612] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 46114.612] (**) NVIDIA(0): device DELL U2311H (DFP-3) (Using EDID frequencies has
    [ 46114.612] (**) NVIDIA(0): been enabled on all display devices.)
    [ 46114.616] (II) NVIDIA(GPU-0): Display (AU Optronics Corporation (DFP-0)) does not support
    [ 46114.616] (II) NVIDIA(GPU-0): NVIDIA 3D Vision stereo.
    [ 46114.616] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 46114.616] (**) NVIDIA(0): device AU Optronics Corporation (DFP-0) (Using EDID
    [ 46114.616] (**) NVIDIA(0): frequencies has been enabled on all display devices.)
    [ 46114.616] (II) NVIDIA(GPU-0): Display (DELL U2311H (DFP-3)) does not support NVIDIA 3D
    [ 46114.616] (II) NVIDIA(GPU-0): Vision stereo.
    [ 46114.616] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 46114.616] (**) NVIDIA(0): device DELL U2311H (DFP-3) (Using EDID frequencies has
    [ 46114.616] (**) NVIDIA(0): been enabled on all display devices.)
    [ 46114.625] (II) NVIDIA(GPU-0): Display (AU Optronics Corporation (DFP-0)) does not support
    [ 46114.625] (II) NVIDIA(GPU-0): NVIDIA 3D Vision stereo.
    [ 46114.625] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 46114.625] (**) NVIDIA(0): device AU Optronics Corporation (DFP-0) (Using EDID
    [ 46114.625] (**) NVIDIA(0): frequencies has been enabled on all display devices.)
    [ 46114.625] (II) NVIDIA(GPU-0): Display (DELL U2311H (DFP-3)) does not support NVIDIA 3D
    [ 46114.625] (II) NVIDIA(GPU-0): Vision stereo.
    [ 46114.625] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 46114.625] (**) NVIDIA(0): device DELL U2311H (DFP-3) (Using EDID frequencies has
    [ 46114.625] (**) NVIDIA(0): been enabled on all display devices.)
    [ 46114.630] (II) NVIDIA(GPU-0): Display (AU Optronics Corporation (DFP-0)) does not support
    [ 46114.630] (II) NVIDIA(GPU-0): NVIDIA 3D Vision stereo.
    [ 46114.630] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 46114.630] (**) NVIDIA(0): device AU Optronics Corporation (DFP-0) (Using EDID
    [ 46114.630] (**) NVIDIA(0): frequencies has been enabled on all display devices.)
    [ 46114.630] (II) NVIDIA(GPU-0): Display (DELL U2311H (DFP-3)) does not support NVIDIA 3D
    [ 46114.630] (II) NVIDIA(GPU-0): Vision stereo.
    [ 46114.630] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 46114.630] (**) NVIDIA(0): device DELL U2311H (DFP-3) (Using EDID frequencies has
    [ 46114.630] (**) NVIDIA(0): been enabled on all display devices.)
    [ 46264.057] (II) NVIDIA(GPU-0): Display (AU Optronics Corporation (DFP-0)) does not support
    [ 46264.057] (II) NVIDIA(GPU-0): NVIDIA 3D Vision stereo.
    [ 46264.057] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 46264.057] (**) NVIDIA(0): device AU Optronics Corporation (DFP-0) (Using EDID
    [ 46264.057] (**) NVIDIA(0): frequencies has been enabled on all display devices.)
    [ 46264.058] (II) NVIDIA(GPU-0): Display (DELL U2311H (DFP-3)) does not support NVIDIA 3D
    [ 46264.058] (II) NVIDIA(GPU-0): Vision stereo.
    [ 46264.058] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 46264.058] (**) NVIDIA(0): device DELL U2311H (DFP-3) (Using EDID frequencies has
    [ 46264.058] (**) NVIDIA(0): been enabled on all display devices.)
    [ 46264.076] (II) NVIDIA(GPU-0): Display (AU Optronics Corporation (DFP-0)) does not support
    [ 46264.076] (II) NVIDIA(GPU-0): NVIDIA

  • Session Context Variable and Order by clause

    Hi All,
    Im using Oracle 11g R2.
    Is it somehow possible to use Context variable (to store column name) in ORDER BY clause? My ultimate aim is to construct Order by at runtime without using concatenation.
    e.g. i created context as my_ctx for some pkg and its variable as v_ctx having value set as "TABLE_NAME"
    so is it possible to use it as
    select * from all_tables
    order by sys_context('my_ctx', 'v_ctx');
    if no, is there any work around??
    Thanks,
    Vivek

    its better to post here
    Oracle Discussion Forums » Oracle Database » SQL and PL/SQL

  • C# SSIS Script component - Save List String to Object package-scope variable and read it in Script Task

    before posting this i was searching this on internet but was not able to find info regarding my specific case:
    i have a DataFlow Task with "Error output" pointing from FlatFile to
    Script Component that does below (variable "ErrorMessageList" is listed under ReadWriteVariables property):
    List<string> lsErrors = new List<string>();
    public override void Input0_ProcessInputRow(Input0Buffer Row)
    lsErrors.Add("test1");
    lsErrors.Add("test2");
        void PostExecute()
            base.PostExecute();
            Variables.ErrorMessageList = lsErrors;
    Then the DataFlow points to a ScriptComponent where this object variable is listed under ReadOnlyVariables property and does the below:
    public void Main()
    List<string> lsErrors = (List<string>)Dts.Variables["ErrorMessageList"].Value;
    and that is where i get exception-has-been-thrown-by-the-target-of-an-invocation
    What is wrong here?
    (i have mistakenly edited this first post before, so i tried to manually put it back to original version)

    i have missed the "override" keyword...
    public class ScriptMain : UserComponent
    public class UserComponent: ScriptComponent
    namespace Microsoft.SqlServer.Dts.Pipeline
    public class ScriptComponent
    // i should have seen this before
    public virtual void PostExecute();
    i believe i must have deleted the PostExecute method definition right after the ScriptComponent generated the script for me... and then when i've realized that i can't change ReadWriteVariables as a part of:
    public override void Input0_ProcessInputRow(Input0Buffer Row)
    // --- can't change ReadWriteVariables here
    then i had to add the method back but forgot that the base method is virtual
    thanks for this hint, Russ!

  • Must command link parameter variable SESSION Scope??

    I add a EJB Session Bean Method to my page which returns an array:
    public Province[] getProvinces();
    When you place the Session Bean to the page, it automatically creates a REQUEST SCOPE VARIABLE called "provinceRemoteGetProvincesResultBean" in the type of Province array. And it automatically creates a Data Table to display the results.
    Up to this point every thing's cool!! I can call the method properly, get the results and display without any problem.
    However when I try to create a COMMAND LINK to one of the columns of the TABLE (e.g. Province has a NAME column) I have a problem:
    <h:commandLink styleClass="commandLink" id="lnkName" action="#{pc_ProvinceManagement.doLnkNameAction}">
    <h:outputText id="otxName" value="#{varprovinceRemoteGetProvincesResultBean.name}" styleClass="outputText">
    </h:outputText>
    <f:param name="provinceId" value="#varprovinceRemoteGetProvincesResultBean.id}"></f:param>
    </h:commandLink>
    The problem is that this "provinceRemoteGetProvincesResultBean" is REQUEST scope and Command Link does not work with REQUEST Scope variables!!!
    I had similar examples before, when I used the command link with a REQUEST SCOPE variable, it didn't work. When I use it with a SESSION Scope variable it works.
    In this particular case, I cannot make the Province[] a SESSION SCOPE variable, because it's not a class!!! Therefore I need to create a new class containing a Province[] and make that class a SESSION SCOPE variable, which makes things quite complicated!!
    IS IT TRUE THAT COMMAND LINK PARAMETERS MUST BE SESSION SCOPE?????

    Line 4: <f:param name="provinceId" value="#varprovinceRemoteGetProvincesResultBean.id}"></f:param>
    value="#varpro... >>> value="#{varpro...                                                                                                                                                                                                                                                                                       

  • Accessing Session scope attributes in ADF BC

    Is there any groovy script for accessing session scope variables in ADF BC?

    Let me put forward my use case:
    My VO's in my application has a bind variable which is bound to currently logged in user (adf.context.securityContext.userName). Also my application has couple of AM's
    But now i'm adding complexity to my application where i'm implementing super user concept, a super user can login to the application, select a username (say 'user1'), and see the application as if 'user1' is logged in.
    So i'm trying to solve the problem by setting a session attribute for the user ('user1') and make it use in VO's
    Do you guys have any better solution to this problem?

  • Cannot lock session scope

    Coldfusion 6.1, Dreamweaver 8.0, access 2003
    All code is being written by Dreamweaver in this discussion.
    I am not writing this code on my own.
    I am new to both Dreamweaver and Coldfusion. I am setting up
    the company intranet site. I want some parts restricted. I started
    by creating a login page by using dreamweaver. My first problem was
    when i was being directed towards the page for unsuccessful login
    even though I know I typed in the correct username and password. I
    have an access database holding this information. I am not using
    security level. While researching this with another forum, I
    decided to go to the next step and start putting the Restricted
    Page code. This is when I discovered my second problem. When I
    render the page, I get
    CANNOT LOCK SESSION SCOPE - CFLock cannot be used to lock the
    application or sessions shared scopes without these scopes being
    established through the use of the CFAPplication tag. ....
    My research tells me my problems are the result of same
    problem.
    In coldfusion Administrator, under Memory variables, I have
    check marks for Enable Application Variables and Enable Session
    Variables.
    Then I found this article
    http://kb.adobe.com/selfservice/viewContent.do?externalId=tn_16564&sliceId=2.
    I did what it said and it still does not work.
    I have the file in two places
    One at the root: C:\Inetpub\wwwroot\_mmServerScripts
    One within the site:
    C:\Inetpub\wwwroot\GIInet\_mmServerScripts
    Do you know which one should have this tag? Should I have
    both folders?
    <CFAPPLICATION NAME="Name" SESSIONMANAGEMENT="Yes" >
    Where it says "Name", do I leave Name there or do I put in a
    name that is relative to my site and what is this .. the root
    folder name?
    Why do I have to pay for support for something that is not
    obviously working?!?!

    "Do you know which one should have this tag? Should I have
    both folders?
    <CFAPPLICATION NAME="Name" SESSIONMANAGEMENT="Yes" >"
    Neither. It should be in the root folder of YOUR web
    application.
    'C:\\Inetpub\wwwroot' is a common web root for beginners. It
    must be
    included in every file that will be part of the same
    application as
    defined by the 'Name' parameter. The easiest way to do this
    is the use
    the Application.cfm|Application.cfc files that are
    automatically part of
    every file in the same and all sub directories.
    "Where it says "Name", do I leave Name there or do I put in a
    name that
    is relative to my site and what is this .. the root folder
    name?"
    It is whatever string you want to use to define an
    "Application" that
    all files that share it will belong to. All files that have
    the same
    "Name" will share Application, Session and other common scope
    variables
    and other functionality. Again this must be included in every
    file that
    you want to be part of the same "Application". That is what
    the
    Application.cfm and|or Application.cfc files are for, so one
    does not
    have to hard code this line in every file, thought that would
    be a
    functional, if impractical, option.
    "Why do I have to pay for support for something that is not
    obviously
    working?!?!"
    Well, this is all explained in quite some detail in the
    documentation
    included with Dreamweaver and|or ColdFusion as well as online
    at Adobe
    and many other sites. The details and ins and outs are also
    well
    discussed on numerous blogs, forums and discussion lists. And
    all those
    resources are free.
    But if one wants someone else to do the work for them, they
    generally
    need to pay for that help.

  • Coldfusion session/client variables?

    We have multiple users using VPN to get to our intranet.  When the second user gets on they get the first person's session/client variables?
    I have tried looking for the session/client variables and where they are stored but I can't seem to find them.  I have tried searching out the cookies.
    I would appreciate any help.

    There are not too many people on this forum that have dabbled with ColdFusion. I used to, but that was more than one decade ago.
    Your best bet on getting assistance with your problem, is to go to the ColdFusion forum.

  • Print memory scope variables value

    All,
    How do i print all the memory scope variable and their values that are set via the MB or the taskflow or the UI page using setAction/PropertyListener ?
    I mean where should i write the code ?
    thnks
    Jdev11.1.1.5
    Edited by: in the line of fire on Oct 13, 2011 9:50 AM

    @Frank
    if you can detail this +"If the managed bean uses a HashMap to store values then the bean itself can be used to expose an interface for all of what you want it to do. So its an architecture decision to make (which you should do when designing the application)"+
    As of now what i am doing is
        public void printMemoryVariables(){
            logger.info("inside printMemoryVariables");
            AdfFacesContext adfFacesCtx = AdfFacesContext.getCurrentInstance();
            // get the PageFlowScope Params
            Map<String, Object> scopePageFlowScopeVar= adfFacesCtx.getPageFlowScope();
            // get the requestScope Params
            Map<String, Object> scopeRequestScopeVar= adfFacesCtx.getViewScope();
            Collection scopePageFlowScopeVarValues = scopePageFlowScopeVar.values();
            Collection scopePageFlowScopeVarKeys = scopePageFlowScopeVar.keySet();
            //obtain an Iterator for Collection
            Iterator itrValues = scopePageFlowScopeVarValues.iterator();
            Iterator itrKeys = scopePageFlowScopeVarKeys.iterator();
            //iterate through HashMap values iterator
            while(itrValues.hasNext() && itrKeys.hasNext()){
                logger.info("Key : " + itrKeys.next() +  "Values: " + itrValues.next());
        }And calling this in the initializer of the taskflow. But is it possible to get the values during the task flow execution

Maybe you are looking for

  • Using a Mac and a Surface Pro with the same catalog?

    I am using CC on my Mac as my primary computer. I'm thinking of getting a Surface Pro to use as a second computer. 1. Are there any issues with opening and saving a catalog back-and-forth between a Mac and a PC? I'm thinking of doing it via Dropbox.

  • IPod Nano and iPod Shuffle not recognized by my iMac

    I'm new to Mac and just purchased a Nano and a Shuffle.  I spent the weekend transferring music from iTunes to both devices without any issues.  A few hours later I went to transfer additional songs and my Mac would not recognize either device.  The

  • Quickfinder and Windows 7

    We have quickfinder running on an OES Linux machine indexing two Netware 6.5 volumes which is working fine. We have started upgrading our workstations to Windows 7. We are using Internet Explorer 8 on both XP and W7. The search of the volumes still w

  • WL 5.1 and IIS - HTTP Error 403 - Access Forbidden problems

    I'm trying to hook IIS up to the evaluation version of WebLogic Server 5.1 that I installed... I followed the instructions that I found on the Installing the Microsoft-IIS (proxy) plug-in page. I then copied HelloWorld.jsp into the d:\weblogic\myserv

  • How to make available certain features available to a particular user group in APEX.

    Hi I am trying to make available certain features like (updating/viewing some fields) to a particular set of users. Our requirement is to use SSO for signing in. So when a particular user logs in she/he will be allowed to update or view only certain