SCN_TO_TIMESTAMP and TIMESTAMP_TO_SCN Behaviour

Dear all,
I'm trying to understand how both SCN_TO_TIMESTAMP and TIMESTAMP_TO_SCN work by executing the following:
SQL> select scn_to_timestamp(ora_rowscn) test, last_name from employees where la
st_name='King';
TEST                 LAST_NAME
16-DEC-10 01.34.23.0 King
00000000 PM
16-DEC-10 01.34.23.0 King
00000000 PM
SQL> select ora_rowscn, last_name from employees where last_name='King';
ORA_ROWSCN LAST_NAME
    559374 King
    559374 King
SQL> select timestamp_to_scn('16-DEC-10 01.34.23.000000000 PM') from dual;
TIMESTAMP_TO_SCN('16-DEC-1001.34.23.000000000PM')
                                           559370why doesn't the last query resulting 559374 but instead 559370?
best regards,
valerie

Hi,
From the documentation :
SCN_TO_TIMESTAMP takes as an argument a number that evaluates to a system
change number (SCN), and returns the approximate timestamp associated with that
SCN.The important word being approximate.
You cannot rely on it to be as precise as a systimestamp.
timestamp_to_scn(scn_to_timestamp(SCN)) == SCN is FALSE
(even if it might happen to be true sometime...)

Similar Messages

  • Scn_to_timestamp and timestamp_to_scn

    Hello,
    I have such strange(?) behaviour in my database
    SQL> select to_timestamp('09.10.2008','dd.mm.yyyy') from dual;
    08/10/09 00:00:00,000000000
    SQL> select timestamp_to_scn(to_timestamp('09.10.2008','dd.mm.yyyy')) from dual;
    612168
    SQL> select scn_to_timestamp(612168) from dual;
    08/10/08 16:19:02,000000000
    I thought that since timestamp_to_scn returns an SCN for the given timestamp, scn_to_timestamp returns the same timestamp for that SCN, but it doesn't. Is it because there's no hour in the timestamp? When I enter a timestamp in 'dd.mm.yyyy hh24:mi:ss' format everything is as it should be.
    Regards,
    Olimpia

    SCN_TO_TIMESTAMP give the timestamp of the given SCN.
    TIMESTAMP_TO_SCN give the highest SCN below the given timestamp.
    Here an example :
    SQL> select scn_to_timestamp(2025400+rownum) tm, timestamp_to_scn(scn_to_timestamp(2025400+rownum)) scn
      2  from   dual
      3  connect by level<=5;
    TM                                                                                 SCN
    09-OCT-08 07.59.16.000000000 PM                                                2025401
    09-OCT-08 07.59.19.000000000 PM                                                2025402
    09-OCT-08 07.59.22.000000000 PM                                                2025403
    09-OCT-08 07.59.25.000000000 PM                                                2025404
    09-OCT-08 07.59.28.000000000 PM                                                2025405Have a look to the last two rows, 3 seconds difference.
    Let's try to see what SCN is given by the a timestamp equal to the last minus one second :
    SQL> select timestamp_to_scn(to_timestamp('09-OCT-08 07.59.27 PM','DD-MON-YY HH12.MI.SS PM')) from dual;
    TIMESTAMP_TO_SCN(TO_TIMESTAMP('09-OCT-0807.59.27PM','DD-MON-YYHH12.MI.SSPM'))
                                                                          2025404It is the second last, the highest SCN below the given timestamp.
    Ok, let's confirm the date given by that SCN:
    SQL> select scn_to_timestamp(2025404) from dual;
    SCN_TO_TIMESTAMP(2025404)
    09-OCT-08 07.59.25.000000000 PMThis is the good one.
    HTH,
    Nicolas.

  • Payment scheme and its behaviour in FPL9

    Hi Experts,
    I have a concern,
    Anybody can explain Payment schem Request and its behaviour?
    As statistical line item impact and real item impact and when it will go to down payments tab?
    some times i can see same document in few situtions, i am quite confuse. Can you anybody can hlpe on this please?
    Thanks,
    Abash

    Hi Abash,
    Payment scheme is a budget billing plan that is offered in SAP for customers accounts where customers wants to pay a constant amount for yearly consumption, so for this the SAP extrapolates the billing line item and gives a amount based on payment frequency , for .e.g $50 per week
    Now as customer is not going to pay  the invoice amount as customer is on payment scheme, customer will pay the payment scheme amount will settle his invoice,so to take payment scheme payment a line item is required against which customer will be charged its a statistical line item, now when customer pays this amount statistical item gets cleared and payment will reside as down payment , which in turn will clear invoice in account maintenance
    Hope it helps.
    Regards,
    Lalit

  • Are Adobe promoting the alternatives to Database and Server Behaviours

    The apparently disastrous depreciation of Database and Server Behaviours in Dreaweaver CC seem to have left a nasty taste in the mouth for many users. I am not a very experienced web developer, to the point where I cringe when describing myself as such, and I assume, possibly naively, that if Adobe have made them optional now, that there is an alternative; if not, the decision seems dimwitted in the extreme, and I did not expect that to be the case with a company who's software I have admired and found useful for so long.
    So, assuming there is an alternative method to create dynamic data driven websites in Dreamweaver, can people please suggest what they are, and possibly point me towards the Adobe support and tutorials that encourage and explain their use. It must be in Adobe's interest to to get Dreamweaver's users to adopt the new technologies, and, at the moment, I cannot believe there is no adequate alternative.
    I have seen many complaints about the depreciation of the support, but no one seems to be saying "don't use those, this is what you need to do the job". If anyone can do that for me, it would be greatly appreciated, and I imagine others would also benefit.
    And if the alternatives are inadequate, then perhaps we could discuss how to get Adobe to repair a broken product.

    Rob Hecker2 wrote:
    As the web has evolved it makes sense that websites are no longer created by one person using one tool (DreamWeaver).
    I agree with you there, depending at what level you are. A large design company will have specialists in all areas whilst a small one man set up will not. These small one-man band businesses usually attract low paying clients who will not have a budget to employ 'specialists' which is where DW server behaviours fitted in perfectly. Although it's benefited me enormously by learning how to manually connect and query databases I still think it was and is pretty lazy on the part of Adobe NOT to update the behaviours which were an important part of the program for many.  3rd party developers have produced extensions at a considerable cost, over and above what it costs to run DW. They quickly rolled out these extensions when it became clear Adobe had decided to upset many of its customers by not including any alternative in CC/CC 2014 - so don't tell me it would have taken many hours development and financial resources which Adobe just could not afford. That's bollocks. This is purely a decision by some wanker at top level in Adobe that is probably smoking crack and don't know their *** from their elbow, or what their customers really want.
    Rob Hecker2 wrote:
    It always seemed to me that by adding support for PHP/MySQL at all, Adobe was just going to frustrate people.
    NO, the frustration is that Adobe introduce components and then doesn't develop them any further preferring to introduce a bag of dog poo into their programs like fluid grids instead of concentrating on what they do best.
    Rob Hecker2 wrote:
    PHP programmers do not use Dreamweaver for PHP Development. I recall a questionnaire on a website where the question was "What tools do you use for PHP development?" Dreamweaver was not even on the list of choices.
    Serious php developers don't  - you're right - but for those who don't program php/mysql on a daily or even weekly basis, but occasionally have the need for it, they do. Most websites can benefit from having a backend database these days and at a time when databases are main stream Adobe decide to ditch what was a premium attraction of the software, completely senseless decision. A few years ago when static sites were main stream Macromedia were ahead of the game an introduced the Server Behaviours. I guess the top brass in charge at the time (Macromedia) weren't smoking crack all day and instead listening to what their customers wanted.

  • 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

  • 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

  • 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.

  • JAXB, Castor and extending behaviour

    I need to do XML data binding and have been evaluating Castor and JAXB. One of the main differences seems to be Castor is class based while JAXB is interface based.
    The ability to generate classes to marshal, unmarshal, and validate is really great but a schema can't define all the behaviour your class may want to have.
    Given that the auto-generated classes dont have all the methods I need what do I do? Well in Castor its easy, I just subclass the auto-generated classes and add the behaviour as required. It works well. How can I do a similar thing in JAXB? Extending the interface isnt enough because you need to extend a class to implement the new interface However, in JAXB the implementation class is not supposed to be used directly by the application.
    Can anyone suggest the best way to solve this problem?
    Thanks,
    Paul

    One thing I am doing now is generating all the classes initially using the default behaviour. Then I take the one of the generated classes and modify it. Then I create an entry in the binding file specifying the class as the impl class for that node. You can then rerun the generator and it will not write over the class you have changed. I don't see why you couldn't just extend the class and set the extended class name in the binding file. That's actually better than what I've got now because I can keep my methods separate from the generated class and it's easier to regenerate that class too.
    My question is whether there is a way to get JAXB to create bound properties the way that you can with Castor?

  • .obj files and simple behaviour classes

    Hello,
    How come when i load up my .obj file in java 3d it loads up with no color? Is there any other type of file that java can load up and it will display the color?
    Also, is it possible to attach a simple behaviour to another transformgroup? or would i need to create another branch graph for the transformgroup i want my simple behaviour to affect?
    thanks very much.

    You could use a file loader from
    http://www.j3d.org/utilities/loaders.html

  • Server Name VS Outlook Anywhere Proxy Server and the behaviour I should expect when using SAN certificates...

    (I'll upload screen captures if needed once my account gets verified)
    I have a basic (as in freshly installed single exchange server 2010 SP3) Exchange Server installation. I've setup Outlook Anywhere. I've also setup a SAN (SubjectAltName) certificate.
    My setup:
    ex01.eci.XXXX.XX = is the server name and also the CN of my SAN certificate
    mail.eci.XXXX.XX = an A record I've setup to access my exchange server. It is also a subjectAltName in my SAN certificate
    When setting up Outlook, I enter the server name and specify the Outlook Anywhere proxy server in the Outlook Anywhere section. This works fine and I connect to my exchange server using RPC over HTTPS.
    Now, I was under the impression that specifying SANs in the certificate would allow me to enter the SAN alt name (mail.eci.XXXX.XX) in the field reserved for the Server Name, in Outlook..
    But it does not work. The proxy will give me an error each time, like that:
    HTTP    544    RPC_IN_DATA /rpc/rpcproxy.dll?mail.eci.XXXX.XX:6002 HTTP/1.1 , NTLMSSP_NEGOTIATE
    HTTP    635    HTTP/1.1 401 Unauthorized , NTLMSSP_CHALLENGE (text/html)
    HTTP    123    HTTP/1.0 503 RPC Error: 6ba
    My question is: is this the behaviour I should expect? Or should I be able to specify the SAN alt name in the Server Name in Outlook?
    Thanks!

    Hi,
    Firstly, I’d like to explain, the server name tab should be filled with your mailbox server name in the process of configuring Exchange 2010 account.
    And the Outlook Anywhere proxy server is configured at the server side and cannot be randomly defined at the client side. To check it, we can run: get-outlookanywhere |fl externalhostname
    Thus, it’s an expected behavior that we would get error if we randomly enter name in the server name tab when we configure an account. If I misunderstand your meaning, please feel free to let me know.
    Additionally, Autodiscover service can help us automatically complete the configuration of the Outlook account. And how about the result if you use the Autodiscover to automatically configure the account?
    If you have any question, please feel free to let me know.
    Thanks,
    Angela Shi
    TechNet Community Support

  • Facet  and rendered behaviour

    This fragment works as expected
    <h:column>
    <h:outputText value="Step #{navigation.currentStep}" rendered="#{navigation.stepLabelVisible}" style="color: White;"/>
    </h:column>
    whereas that one doesn't ( always invisible )
    <h:column>
    <f:facet>
    <h:outputText value="Step #{navigation.currentStep}" rendered="#{navigation.stepLabelVisible}" style="color: White;"/>
    </f:facet>
    </h:column>
    Is this expected behaviour ?

    Hi,
    you need to make sure the af:switcher "FacetName" property is set to the name of the current visible facet. If do this e.g from a managed bean in request scope, then pressing the command button clears this information and the default facet is shown. The reason it works for the other button only seems to be because its the default.
    http://download.oracle.com/docs/cd/E17904_01/apirefs.1111/e12419/tagdoc/af_switcher.html
    Frank

  • Keyframes and Custom Behaviours

    Hi,
    I am having a great deal of trouble with this application. I have over 100 jpegs which i want to effectively float down past the camera and land in a specific shape (a map) so they look a little like pieces of paper being dropped onto a surface.
    Now, to achieve this i thought of using a custom behaviour. Animate just once then apply the behaviour to all other pictures, then offset them to happen over a time, not all at once. Thing is, when i copy the behaviour and paste it to anther jpeg, the keyframes jump to an unspecific place in the timeline. Unspecific being the operative word as there is no shortcut to get them back into place.
    Why would this happen? Motion seems TOTALLY out of it's depth once keyframing is introduced to the project.
    Any help would be great.
    thanks
    Celf

    Rather than copy-pasting, try duplicating the layer to which you've applied effects (behaviors, filters, masks, keyframes), then replace the content of the layer by dragging new content from the File Browser onto it, wait for the hooked arrow, and release.
    Or, drag the keyframed parameters from the Keyframe Editor to the Favorites folder in the Library, save as one file, then drag them onto any layer in the Layers tab to apply them to a different layer. You can do this with behavior, filters, and masks as well.

  • BootCamp and Battery behaviour

    Hello everybody. I just have two "little questions"
    First I noticed a few days ago that after 13 cycles my battery capacity has droped to 4200 mAh. What do you think about that? Does anybody else got the same behaviour?
    Second, I just wanted you to ask what you think about the possibility to install windows vista beta2 on an external firwire 400 or USB harddisk. Should that be possible? Does BootCamp support extern USB oder Firewire 400 drives?
    Thank you for replying.

    I don't know if bootcamp supports booting from external drives generally. But windows probably won't unless Microsoft radically changed something. I know that XP vigorously refuses to be installed on an usb-device even on pc systems that support booting from usb-sticks. It absolutely thinks it has to put some files on the first harddrive in the system. I have not yet found anyone who successfully installed xp on an usb-device. I can't imagine that they'll change that in vista. Microsoft Windows wants to own you. Installing their OS on external drives and switching freely is probably not their "cup of tea".

  • Fk validation and delete behaviour??

    I've many Fk in my application (no cascade).
    When I insert a row wich violates the fk BC4J doesn't show any error and I get the error when I commit.
    This is a very bad behaviour because if I execute a transaction wich inserts many rows I'd loose all my work if I need to rollback.
    On the other side if I try to delete a master wich has childs I get in run into the reversed problem : I can delete it until commit when I get an error.
    Is there any workaround or any suggestion for this very bad problem ???
    TIA
    Tullio

    I'm not using composition because conposition is not supported by multiple tables (JBO-25030) but database supports mani FK.
    Stating the problem with Emp Dept I need :
    . receive an error if I try to delete a dept wich as details before the commit.
    . receive an error if I try to insert e row into Emp if I set a wrong Deptno.
    Sometime I can do the second operation using the master/detail ViewLink but sometime I can't and I'm forced to insert into EmpView and not into EmpViewDeptno.
    TIA
    Tullio

  • Safari and Firefox Behaviour on website

    Hello,
    I have been struggling to discover by myself why Safari and Firefox both perform the following bizarre activity when trying to click on a link in a div. The site is my own and I have run the pages through w3.org's validation services both for XHTML and CSS. The following occurs:
    When I click anywhere on any of the div's in the website the font turns green and becomes larger. When there are links and one tries to click the link the previous effect occurs and the link is moved along with the text from under the mouse making it impossible to select the link. It has been making me crazy for quite some time and now I have exhausted all other resources to solve this problem.
    The site is my own work and to assist in solving the problem the sites address is:
    site
    This bizare behaviour also occurs on some other sites that use div in their web pages. The page header for my index page is the following:
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
    <html xmlns="http://www.w3.org/1999/xhtml">

    For the past 12 years I have used the free BBEdit Light for mass edits across hundreds of web pages at once. It comes with separate historic and OS X versions packaged together. It is no longer supported and Bare Bones no longer list it on their site but it continues to work exceptionally well on my G4 with Leopard. It may be the fastest text editor you will ever use. It can also open large files - I have used it on 100 MB log files. It comes with excellent documentation which I still refer to for grep search and replace.
    At the time of writing it can still be downloaded from at least one site at:
    http://www.google.co.uk/search?q=%22BBEditLite6.1.2.smi%22
    With a little thought and care it is surprising how many server-wide edits can be done in seconds with BBEdit. Don't forget to do a full backup of server pages before you start and perhaps at regular intervals.

Maybe you are looking for

  • Integration Server Queues Stopping

    Hi People, We are doing a FCC scenario (.CSV to XML), with the content conversion parameters as follows: Recordset Name: Recordset Recordset Structure: DataTable1,1 Recordsets per message: 1 As it is clear from the configuration, <b>when the source f

  • How to add attachments to appointment?

    appointment.Attachments.AddFileAttachment(file.Name, stream); //appointment.Attachments[0].IsInline = true; disabled in Outlook 2007 appointment.Save(WellKnownFolderName.Calendar, SendInvitationsMode.SendToAllAndSaveCopy); The recipient can't see the

  • AP Impersonation on WLC

    Has anyone seen the WLC reporting its own APs as impersonating APs? I checked the forum and found one conversation relating to this and my 802.11a is set to Country already. But I am see ing this on the B/G side. Any thoughts?

  • Report which gives all the manullay released salesorders - VKM2

    User want to run a selected date range to run a report, to lists all the sales orders that have been manually released via T-code: VKM2 But I can not find the related display variant, or do you have any other related report ? Thanks Srikanth

  • Assistance requested in configuring VLANs

    I have VLAN A with Server A1, Server A2, etc. on it. I have VLAN B with Server B1, Server B2, etc. on it. I need Server A1 (on VLAN A) to see Server B1 (on VLAN B) only ? no other devices. While there may be multiple ways to accomplish this, I?m hopi