Spaces Keyboard Freeze, Possible Insight?

I’m one of the thousands who are struggling with the use of Spaces and the locked up keyboard.  When I use my keyboard to move between spaces, the Spaces image remains on the screen, freezing up my keyboard so that only limited buttons still work.  The most effective way I’ve found to combat this is to open Activity Monitor and quit the Dock, thus giving me full control of my keyboard back again.
However, in the past 24 hours I’ve discovered something that I thought might be of use to someone with more insight into OS X than myself.  I’m a Kensington Mouse user of more than 15 years.  Their Mouseworks software allows one to customize mouse clicks in any way they see fit.  Yesterday I noticed that when I go into the Mouseworks preference panel and indicate that I’d like to define a specific command for this or that button, that once I click in the space that allows me to type this command, my simple click therein immediately publishes anywhere from 1 to a half dozen characters, without my command.  It’s almost as if somehow characters are being stored in my click.  For example, I just clicked in this box and without me touching the keyboard, the letters Q and W suddenly appeared therein.
How does this relate to Spaces?  A few hours ago when Spaces locked my keyboard, I went into Mouseworks and tried this again, and when I clicked in this box which displays any command accompanying my click, only the letter Q appeared on its own.  I then canceled out of this box and pressed the letter Q on my keyboard, and Spaces unlocked!  Suddenly my keyboard was free.  A short time later Spaces locked on me again.  Going back into Mouseworks, the input box displayed, “Q W Up Arrow” after I clicked therein.  I exited out and pressed each of these keys and Spaces freed up again.
While I am a lifelong Mac user, I’m not an expert by any imagination, so I don’t know what any of this means, definitively.  It appears to me, nonetheless, that for some reason, letters and commands, keyboard keys, are somehow lingering into my mouse clicks, and it appears as if Spaces is freezing my keyboard because it’s waiting for those buttons to be pressed.
Is this a keyboard error? A preferences error?  An OS X error?  I don’t know.  But I thought that if I shared my findings here, someone might be able to look into solutions that I can’t conceive.

Okay everyone, let me add to my own post, another piece of insight in the last 24.  First, let me post an image that might help define what I've described above:
According to the instruction I've given the Mouseworks software, this box should just be "command Q", a command I've assigned to that particular mouse button.  But when I click my mouse in this box, rather than just placing the cursor there, the letter “Q” and the symbol “[“ are deposited, without my every touching the keyboard.  I then use my keyboard to change Spaces, and my keyboard get locked out.  But then I type in these two letters, the Spaces image disappears, and my keyboard is free.
If my findings in the last 24 are consistent, then here's what I've surmised: If the only button I press on my mouse is the left button, then the Spaces does not freeze on my screen and my keyboard does not lock me out. But if I hit any other button on my mouse, a button wherein I've told my software to press a keyboard combination, then Spaces does freeze, until I go back into Mouseworks, find out what key combination is lingering, and then type that combination.
One more thing.  If I've gone into Mouseworks and discovered the key combination, and then typed that combination of letters, everything is back to normal. In fact, if I immediately go back to that Mouseworks screen and click my mouse therein, there are no longer any lingering letters.  If at this point I unplug my mouse, I can uses Spaces and my Trackpad all I want, bouncing back and forth between any Space I wish by using the keyboard, and Spaces never hangs.
My conclusion: Is it possible that each of us suffering from Spaces causing our keyboards to freeze is using an external mouse?  That seems totally plausible.  Or is it possible this problem is caused by those of us who are using software to have key commands activated when we click a button?  Doesn't Apple's own Magic Mouse software allow for such?
I can't imagine that finding this for myself is unique to me.  I also can't imagine that everyone with this problem is using a Kensington mouse; that seems WAY too coincidental.  But I can imagine there's a solution somewhere in this revelation.  Is it the mouse software we need to delete?  Is it a keyboard preference that's causing characters to linger in the clicking?  Is this all some evil scheme of Steve Jobs to force all of us to use the Magic Mouse? 
Look into this for yourself!  Tell me what you guys find.

Similar Messages

  • Macbook Keyboard freezing (Possibly a solution)

    Hi all
    after doing some thinking, I believe I may have found a solution to the Macbook Leopard keyboard issue.
    This is what I think maybe possible.
    We need a Macbook and then try and copy the Mac OS X Tiger keyboard driver and overwrite the one in Mac OS X Leopard, thus replacing it with a much more stable one, and possibly making it work without the dreaded crashing

    Lauraford, you seem to be having a similar problem to many other people here. Check out this thread: http://discussions.apple.com/thread.jspa?messageID=5786564

  • Random Track Pad/Keyboard Freezes

    Help!!
    I have a white Mac Book that I just purchased last year. All of a sudden I get random track pad and keyboard freezes. Example, just a few minutes ago I went to see if I had any new e-mail. I moved my finger around on the track pad and nothing happened. Now mind you, I could see my scree and my screen saver was still running but the track pad did not do anything. I tried using the space bar, enter, etc. but NOTHING worked. When I hit the power button it pops up with the message did I want to shut down, but of course I couldn't move the cursor to select anything.
    Now, the totally odd thing about all this is that I had my computer at work when this happened - I had a remote mouse/presentation control hooked up. that continued working! So, I thought maybe IT was interfering with the track pad somehow so I unhooked it. The track pad still didn't work.
    I used to SWEAR by Apple products, but I'm starting to think I was wrong. I hope someone can help me out....

    It sounds like you may have had a peripheral (the "remote mouse") that doesn't play well with other devices. Did your system possibly enter sleep while the remote mouse was connected? Furthermore, did you install any third-party software to allow that remote mouse to operate?
    If this problem continues to happen you may have to disconnect any USB-based peripherals that you have attached to your MacBook and see if the problem goes away. Also, if you installed any third-party software to support the remote mouse you may have to uninstall it to get your MacBook working again. If the latter, check to see if the product came with an uninstaller utility.

  • Need Urgent Help in PM8M-V H problem - keyboard freeze

    Hi everyone,
    I'm a newbie in this forum and I really need urgent help with my motherboard.
    My PC specification:
    Intel Pentium 4 2.4GHz
    MSI PM8M-V H W7104VMS v3.4 022206 14:32:17
    1GB(512MB x 2) Kingston PC3200 400MHz
    Seagate SATA II 320GB ST3320620SV (set with jumper to support SATA I)
    Power Color ATI Radeon 9550 256MB
    Lite-On DVDRW SHM-165P6S
    USB mouse, PS/2 Keyboard
    I really appreciate if anyone can help to guide me in solving my problem. My keyboard tends to freeze at the part where it says "Press any key to boot from CD". This limits me to do anything until I'm totally loaded into Windows.  Thus, disable me to perform any formating and fresh installation of OS. However, the keyboards works fine at the begining of the POST and in BIOS. Is there any settings in BIOS that i should perform?.....
    However, I realise in order to get through the foresaid message without the the keyboard freeze up is by keep on trying to boot up and shut down until it works (but only work once, then hv to try again), but this is not a solution as if what if I wanted to have 2 OS?... I cant use the keyboard to choose either of the OS installed. I have tried to change the RAM, change keyboard, use the build in VGA, or even remove the motherboard from the ATX casing - result: still have the same problem. What should I do??.. I have look around the forum for answers but there isnt any (I hope I didnt miss any). Is there any problem with my motherboard, or its BIOS, or any of the harware compatibility or etc..... what actually can I do?   
    I do not dare to perform any BIOS update Unnecessary (it seems that many have problems with BIOS problem in this forum) and moreover i think my BIOS is the most up-to-date. I cant find any new version in the net. Anyway I will check this topic frequently as possible to hope for any solution. What is the best solutions?
    Thanks.

    But the thing that makes me wonder is, my BIOS version is the latest but why this type of problem occurs??
    What version of BIOS should I use?? Any recommendation ??
    Thanks.

  • My MacBook Air keyboard freezes, very interesting.

    I have a MacBook Air (2010, Oct.) 13" which has keyboard problem.
    Sometimes, keyboards attatched to my Mac - includes USB Mac keyboard - freezes and doesn't respond.
    Mices? They work well.
    It's interesting because when the problem occurs, function keys and specific keys like 'control', 'option' are still alive!
    So I can still move around between spaces by 'control + number', but in this case, there's another problem.
    The 'Spaces indicator' sticks on the screen and never disappear.
    These problems occur almost every time when I'm running Parallels Desktop 6, and rarely occurs even I don't run PD6.
    And once it occur, the problem last until I reboot.
    Complete re-install of MacOS X could not be the cure.
    How can I solve this problem?

    BladeH,
    This problem has been around for awhile now.  Here's some information on the issue and some things you can try.  I don't think anyone has really come up with a good answer.
    http://reviews.cnet.com/8301-13727_7-20015817-263.html
    Regards,
    Captfred

  • LG Lucid keyboard freezing

    I have an LG Lucid and the keyboard freezes when I am texting sometimes. I've tried reboting the phone as well as removing the battery for a few seconds then replacing it and turning the phone back on. How can I fix this problem? Im not due for a phone upgrade until April 2015. The phone and my patience may not last that long.

    I would try the Google Keyboard free in the Play Store.  I know it isn't the same keyboard, but I have found it less cluttered with a larger space bar than my LG G2 keyboard.

  • [SOLVED] Laptop keyboard freezes randomly.

    I have Arch dual booted with Windows 8.1 on an Asus K53SM laptop.
    Laptop specs are:
    * Intel i5 2nd Gen @ 2.5 GHz
    * 8GB RAM
    * 750 GB Hard disk
    * nvidia GT630M 2GB
    Right after installing Arch, I installed GNOME as the DE and everything was working fine. Recently, I uninstalled GNOME and installed KDE. I'm experiencing random keyboard freezes. I've tested it with a USB keyboard, so it is not a hardware issue I guess.
    * The [<Super> + S] combination to display all workspaces works fine.
    * So does the <Alt> + F2, to write commands, but the keys don't work (so can't type anything there).
    These freezes are totally random, and the keyboard works fine after 1-2 minutes. Here is the output for Xorg.0.log ->
    [ 21.228]
    X.Org X Server 1.16.4
    Release Date: 2014-12-20
    [ 21.228] X Protocol Version 11, Revision 0
    [ 21.228] Build Operating System: Linux 3.17.6-1-ARCH x86_64
    [ 21.228] Current Operating System: Linux ape 3.18.6-1-ARCH #1 SMP PREEMPT Sat Feb 7 08:44:05 CET 2015 x86_64
    [ 21.228] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-linux root=UUID=92ae3f1c-0f63-4de9-9323-487d50c0bd60 rw quiet splash usbcore.old_scheme_first=1
    [ 21.228] Build Date: 11 February 2015 08:10:00AM
    [ 21.228]
    [ 21.228] Current version of pixman: 0.32.6
    [ 21.228] Before reporting problems, check http://wiki.x.org
    to make sure that you have the latest version.
    [ 21.228] Markers: (--) probed, (**) from config file, (==) default setting,
    (++) from command line, (!!) notice, (II) informational,
    (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
    [ 21.228] (==) Log file: "/var/log/Xorg.0.log", Time: Sun Feb 15 20:18:09 2015
    [ 21.333] (==) Using config file: "/etc/X11/xorg.conf"
    [ 21.333] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
    [ 21.440] (==) ServerLayout "X.org Configured"
    [ 21.440] (**) |-->Screen "Screen0" (0)
    [ 21.440] (**) | |-->Monitor "Monitor0"
    [ 21.456] (**) | |-->Device "Card0"
    [ 21.456] (**) |-->Screen "Screen1" (1)
    [ 21.456] (**) | |-->Monitor "Monitor1"
    [ 21.456] (**) | |-->Device "Card1"
    [ 21.456] (**) |-->Input Device "Mouse0"
    [ 21.456] (**) |-->Input Device "Keyboard0"
    [ 21.456] (==) Automatically adding devices
    [ 21.456] (==) Automatically enabling devices
    [ 21.456] (==) Automatically adding GPU devices
    [ 21.679] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/OTF/".
    [ 21.679] Entry deleted from font path.
    [ 21.679] (Run 'mkfontdir' on "/usr/share/fonts/OTF/").
    [ 21.718] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
    [ 21.718] Entry deleted from font path.
    [ 21.718] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
    [ 21.728] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
    [ 21.728] Entry deleted from font path.
    [ 21.728] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
    [ 21.728] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/OTF/".
    [ 21.728] Entry deleted from font path.
    [ 21.728] (Run 'mkfontdir' on "/usr/share/fonts/OTF/").
    [ 21.728] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
    [ 21.728] Entry deleted from font path.
    [ 21.728] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
    [ 21.728] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
    [ 21.728] Entry deleted from font path.
    [ 21.728] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
    [ 21.728] (**) FontPath set to:
    /usr/share/fonts/misc/,
    /usr/share/fonts/TTF/,
    /usr/share/fonts/Type1/,
    /usr/share/fonts/misc/,
    /usr/share/fonts/TTF/,
    /usr/share/fonts/Type1/
    [ 21.728] (**) ModulePath set to "/usr/lib/xorg/modules"
    [ 21.728] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
    [ 21.728] (WW) Disabling Mouse0
    [ 21.728] (WW) Disabling Keyboard0
    [ 21.739] (II) Loader magic: 0x819d80
    [ 21.739] (II) Module ABI versions:
    [ 21.739] X.Org ANSI C Emulation: 0.4
    [ 21.739] X.Org Video Driver: 18.0
    [ 21.739] X.Org XInput driver : 21.0
    [ 21.739] X.Org Server Extension : 8.0
    [ 21.742] (EE) systemd-logind: failed to get session: PID 301 does not belong to any known session
    [ 21.743] (II) xfree86: Adding drm device (/dev/dri/card0)
    [ 21.745] (--) PCI:*(0:0:2:0) 8086:0126:1043:212e rev 9, Mem @ 0xdc400000/4194304, 0xb0000000/268435456, I/O @ 0x0000e000/64
    [ 21.746] (--) PCI: (0:1:0:0) 10de:0de9:1043:212e rev 161, Mem @ 0xdb000000/16777216, 0xc0000000/268435456, 0xd0000000/33554432, I/O @ 0x0000d000/128, BIOS @ 0x????????/524288
    [ 21.746] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
    [ 21.763] (II) "glx" will be loaded. This was enabled by default and also specified in the config file.
    [ 21.763] (II) LoadModule: "glx"
    [ 21.856] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
    [ 22.220] (II) Module glx: vendor="X.Org Foundation"
    [ 22.220] compiled for 1.16.4, module version = 1.0.0
    [ 22.220] ABI class: X.Org Server Extension, version 8.0
    [ 22.220] (==) AIGLX enabled
    [ 22.220] (II) LoadModule: "intel"
    [ 22.220] (II) Loading /usr/lib/xorg/modules/drivers/intel_drv.so
    [ 22.286] (II) Module intel: vendor="X.Org Foundation"
    [ 22.286] compiled for 1.16.3, module version = 2.99.917
    [ 22.286] Module class: X.Org Video Driver
    [ 22.286] ABI class: X.Org Video Driver, version 18.0
    [ 22.286] (II) LoadModule: "nvidia"
    [ 22.286] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
    [ 22.367] (II) Module nvidia: vendor="NVIDIA Corporation"
    [ 22.367] compiled for 4.0.2, module version = 1.0.0
    [ 22.367] Module class: X.Org Video Driver
    [ 22.374] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets:
    i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G,
    915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM,
    Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33,
    GM45, 4 Series, G45/G43, Q45/Q43, G41, B43
    [ 22.375] (II) intel: Driver for Intel(R) HD Graphics: 2000-6000
    [ 22.375] (II) intel: Driver for Intel(R) Iris(TM) Graphics: 5100, 6100
    [ 22.375] (II) intel: Driver for Intel(R) Iris(TM) Pro Graphics: 5200, 6200, P6300
    [ 22.375] (II) NVIDIA dlloader X Driver 346.35 Sat Jan 10 20:32:18 PST 2015
    [ 22.375] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
    [ 22.386] (++) using VT number 7
    [ 22.429] (II) intel(0): Using Kernel Mode Setting driver: i915, version 1.6.0 20140905
    [ 22.483] (II) Loading sub module "fb"
    [ 22.483] (II) LoadModule: "fb"
    [ 22.483] (II) Loading /usr/lib/xorg/modules/libfb.so
    [ 22.502] (II) Module fb: vendor="X.Org Foundation"
    [ 22.502] compiled for 1.16.4, module version = 1.0.0
    [ 22.502] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 22.502] (II) Loading sub module "wfb"
    [ 22.502] (II) LoadModule: "wfb"
    [ 22.502] (II) Loading /usr/lib/xorg/modules/libwfb.so
    [ 22.510] (II) Module wfb: vendor="X.Org Foundation"
    [ 22.511] compiled for 1.16.4, module version = 1.0.0
    [ 22.511] ABI class: X.Org ANSI C Emulation, version 0.4
    [ 22.511] (II) Loading sub module "ramdac"
    [ 22.511] (II) LoadModule: "ramdac"
    [ 22.511] (II) Module "ramdac" already built-in
    [ 22.704] (--) intel(0): Integrated Graphics Chipset: Intel(R) HD Graphics 3000
    [ 22.704] (--) intel(0): CPU: x86-64, sse2, sse3, ssse3, sse4.1, sse4.2, avx
    [ 22.704] (==) intel(0): Depth 24, (--) framebuffer bpp 32
    [ 22.704] (==) intel(0): RGB weight 888
    [ 22.704] (==) intel(0): Default visual is TrueColor
    [ 22.705] (II) intel(0): Output LVDS1 using monitor section Monitor0
    [ 22.705] (--) intel(0): Found backlight control interface acpi_video0 (type 'firmware') for output LVDS1
    [ 22.705] (II) intel(0): Enabled output LVDS1
    [ 22.705] (II) intel(0): Output VGA1 has no monitor section
    [ 22.705] (II) intel(0): Enabled output VGA1
    [ 22.705] (II) intel(0): Output HDMI1 has no monitor section
    [ 22.705] (II) intel(0): Enabled output HDMI1
    [ 22.705] (II) intel(0): Output DP1 has no monitor section
    [ 22.705] (II) intel(0): Enabled output DP1
    [ 22.705] (--) intel(0): Using a maximum size of 256x256 for hardware cursors
    [ 22.706] (II) intel(0): Output VIRTUAL1 has no monitor section
    [ 22.706] (II) intel(0): Enabled output VIRTUAL1
    [ 22.706] (--) intel(0): Output LVDS1 using initial mode 1366x768 on pipe 0
    [ 22.706] (==) intel(0): TearFree disabled
    [ 22.706] (==) intel(0): DPI set to (96, 96)
    [ 22.706] (II) Loading sub module "dri2"
    [ 22.706] (II) LoadModule: "dri2"
    [ 22.706] (II) Module "dri2" already built-in
    [ 22.706] (II) Loading sub module "present"
    [ 22.706] (II) LoadModule: "present"
    [ 22.706] (II) Module "present" already built-in
    [ 22.706] (==) NVIDIA(1): Depth 24, (==) framebuffer bpp 32
    [ 22.706] (==) NVIDIA(1): RGB weight 888
    [ 22.706] (==) NVIDIA(1): Default visual is TrueColor
    [ 22.706] (==) NVIDIA(1): Using gamma correction (1.0, 1.0, 1.0)
    [ 22.740] (**) NVIDIA(1): Enabling 2D acceleration
    [ 22.740] (EE) NVIDIA(1): Failed to initialize the GLX module; please check in your X
    [ 22.740] (EE) NVIDIA(1): log file that the GLX module has been loaded in your X
    [ 22.740] (EE) NVIDIA(1): server, and that the module is the NVIDIA GLX module. If
    [ 22.740] (EE) NVIDIA(1): you continue to encounter problems, Please try
    [ 22.740] (EE) NVIDIA(1): reinstalling the NVIDIA driver.
    [ 24.454] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 24.455] (II) NVIDIA(GPU-0): Found DRM driver nvidia-drm (20130102)
    [ 24.456] (II) NVIDIA(1): NVIDIA GPU GeForce GT 630M (GF108) at PCI:1:0:0 (GPU-0)
    [ 24.456] (--) NVIDIA(1): Memory: 2097152 kBytes
    [ 24.456] (--) NVIDIA(1): VideoBIOS: 70.08.92.00.fa
    [ 24.456] (II) NVIDIA(1): Detected PCI Express Link width: 16X
    [ 24.461] (--) NVIDIA(1): Valid display device(s) on GeForce GT 630M at PCI:1:0:0
    [ 24.461] (--) NVIDIA(1): CRT-0 (boot, connected)
    [ 24.461] (--) NVIDIA(GPU-0): CRT-0: 400.0 MHz maximum pixel clock
    [ 24.461] (**) NVIDIA(1): Using HorizSync/VertRefresh ranges from the EDID for display
    [ 24.461] (**) NVIDIA(1): device CRT-0 (Using EDID frequencies has been enabled on
    [ 24.461] (**) NVIDIA(1): all display devices.)
    [ 24.463] (==) NVIDIA(1):
    [ 24.463] (==) NVIDIA(1): No modes were requested; the default mode "nvidia-auto-select"
    [ 24.463] (==) NVIDIA(1): will be used as the requested mode.
    [ 24.463] (==) NVIDIA(1):
    [ 24.463] (II) NVIDIA(1): Validated MetaModes:
    [ 24.463] (II) NVIDIA(1): "CRT-0:nvidia-auto-select"
    [ 24.463] (II) NVIDIA(1): Virtual screen size determined to be 1024 x 768
    [ 24.473] (WW) NVIDIA(1): CRT-0 does not have an EDID, or its EDID does not contain a
    [ 24.473] (WW) NVIDIA(1): maximum image size; cannot compute DPI from CRT-0's EDID.
    [ 24.473] (==) NVIDIA(1): DPI set to (75, 75); computed from built-in default
    [ 24.473] (--) Depth 24 pixmap format is 32 bpp
    [ 24.515] (II) intel(0): SNA initialized with Sandybridge (gen6, gt2) backend
    [ 24.515] (==) intel(0): Backing store enabled
    [ 24.515] (==) intel(0): Silken mouse enabled
    [ 24.516] (II) intel(0): HW Cursor enabled
    [ 24.516] (II) intel(0): RandR 1.2 enabled, ignore the following RandR disabled message.
    [ 24.524] (==) intel(0): DPMS enabled
    [ 24.525] (==) intel(0): display hotplug detection enabled
    [ 24.525] (II) intel(0): [DRI2] Setup complete
    [ 24.525] (II) intel(0): [DRI2] DRI driver: i965
    [ 24.525] (II) intel(0): [DRI2] VDPAU driver: i965
    [ 24.525] (II) intel(0): direct rendering: DRI2 enabled
    [ 24.525] (II) intel(0): hardware support for Present enabled
    [ 24.525] (--) RandR disabled
    [ 24.525] (II) NVIDIA: Using 3072.00 MB of virtual memory for indirect memory
    [ 24.525] (II) NVIDIA: access.
    [ 24.529] (II) NVIDIA(1): ACPI: failed to connect to the ACPI event daemon; the daemon
    [ 24.529] (II) NVIDIA(1): may not be running or the "AcpidSocketPath" X
    [ 24.529] (II) NVIDIA(1): configuration option may not be set correctly. When the
    [ 24.530] (II) NVIDIA(1): ACPI event daemon is available, the NVIDIA X driver will
    [ 24.530] (II) NVIDIA(1): try to use it to receive ACPI event notifications. For
    [ 24.530] (II) NVIDIA(1): details, please see the "ConnectToAcpid" and
    [ 24.530] (II) NVIDIA(1): "AcpidSocketPath" X configuration options in Appendix B: X
    [ 24.530] (II) NVIDIA(1): Config Options in the README.
    [ 24.536] (II) NVIDIA(1): Setting mode "CRT-0:nvidia-auto-select"
    [ 24.649] (==) NVIDIA(1): Disabling shared memory pixmaps
    [ 24.649] (==) NVIDIA(1): Backing store enabled
    [ 24.649] (==) NVIDIA(1): Silken mouse enabled
    [ 24.649] (==) NVIDIA(1): DPMS enabled
    [ 24.663] (II) Loading sub module "dri2"
    [ 24.663] (II) LoadModule: "dri2"
    [ 24.663] (II) Module "dri2" already built-in
    [ 24.663] (II) NVIDIA(1): [DRI2] Setup complete
    [ 24.663] (II) NVIDIA(1): [DRI2] VDPAU driver: nvidia
    [ 24.663] (--) RandR disabled
    [ 24.872] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
    [ 24.872] (II) AIGLX: enabled GLX_ARB_create_context
    [ 24.872] (II) AIGLX: enabled GLX_ARB_create_context_profile
    [ 24.872] (II) AIGLX: enabled GLX_EXT_create_context_es2_profile
    [ 24.872] (II) AIGLX: enabled GLX_INTEL_swap_event
    [ 24.872] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
    [ 24.872] (II) AIGLX: enabled GLX_EXT_framebuffer_sRGB
    [ 24.872] (II) AIGLX: enabled GLX_ARB_fbconfig_float
    [ 24.872] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
    [ 24.872] (II) AIGLX: enabled GLX_ARB_create_context_robustness
    [ 24.872] (II) AIGLX: Loaded and initialized i965
    [ 24.872] (II) GLX: Initialized DRI2 GL provider for screen 0
    [ 24.873] (II) AIGLX: Screen 1 is not DRI2 capable
    [ 24.873] (EE) AIGLX: reverting to software rendering
    [ 25.619] (II) AIGLX: Loaded and initialized swrast
    [ 25.619] (II) GLX: Initialized DRISWRAST GL provider for screen 1
    [ 25.634] (II) intel(0): switch to mode [email protected] on LVDS1 using pipe 0, position (0, 0), rotation normal, reflection none
    [ 25.640] (II) intel(0): Setting screen physical size to 361 x 203
    [ 25.988] (II) config/udev: Adding input device Power Button (/dev/input/event3)
    [ 25.988] (**) Power Button: Applying InputClass "evdev keyboard catchall"
    [ 25.988] (II) LoadModule: "evdev"
    [ 25.988] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
    [ 26.030] (II) Module evdev: vendor="X.Org Foundation"
    [ 26.030] compiled for 1.16.2, module version = 2.9.1
    [ 26.030] Module class: X.Org XInput Driver
    [ 26.030] ABI class: X.Org XInput driver, version 21.0
    [ 26.030] (II) Using input driver 'evdev' for 'Power Button'
    [ 26.030] (**) Power Button: always reports core events
    [ 26.031] (**) evdev: Power Button: Device: "/dev/input/event3"
    [ 26.031] (--) evdev: Power Button: Vendor 0 Product 0x1
    [ 26.031] (--) evdev: Power Button: Found keys
    [ 26.031] (II) evdev: Power Button: Configuring as keyboard
    [ 26.031] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input7/event3"
    [ 26.031] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
    [ 26.031] (**) Option "xkb_rules" "evdev"
    [ 26.031] (**) Option "xkb_model" "pc104"
    [ 26.031] (**) Option "xkb_layout" "us"
    [ 26.086] (II) config/udev: Adding input device Video Bus (/dev/input/event6)
    [ 26.086] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
    [ 26.086] (II) Using input driver 'evdev' for 'Video Bus'
    [ 26.086] (**) Video Bus: always reports core events
    [ 26.086] (**) evdev: Video Bus: Device: "/dev/input/event6"
    [ 26.086] (--) evdev: Video Bus: Vendor 0 Product 0x6
    [ 26.086] (--) evdev: Video Bus: Found keys
    [ 26.086] (II) evdev: Video Bus: Configuring as keyboard
    [ 26.086] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:01/input/input14/event6"
    [ 26.086] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
    [ 26.086] (**) Option "xkb_rules" "evdev"
    [ 26.086] (**) Option "xkb_model" "pc104"
    [ 26.086] (**) Option "xkb_layout" "us"
    [ 26.087] (II) config/udev: Adding input device Video Bus (/dev/input/event5)
    [ 26.087] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
    [ 26.087] (II) Using input driver 'evdev' for 'Video Bus'
    [ 26.087] (**) Video Bus: always reports core events
    [ 26.087] (**) evdev: Video Bus: Device: "/dev/input/event5"
    [ 26.087] (--) evdev: Video Bus: Vendor 0 Product 0x6
    [ 26.087] (--) evdev: Video Bus: Found keys
    [ 26.087] (II) evdev: Video Bus: Configuring as keyboard
    [ 26.087] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:4c/LNXVIDEO:00/input/input13/event5"
    [ 26.087] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 8)
    [ 26.087] (**) Option "xkb_rules" "evdev"
    [ 26.088] (**) Option "xkb_model" "pc104"
    [ 26.088] (**) Option "xkb_layout" "us"
    [ 26.088] (II) config/udev: Adding input device Lid Switch (/dev/input/event1)
    [ 26.088] (II) No input driver specified, ignoring this device.
    [ 26.088] (II) This device may have been added with another device file.
    [ 26.089] (II) config/udev: Adding input device Sleep Button (/dev/input/event2)
    [ 26.089] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
    [ 26.089] (II) Using input driver 'evdev' for 'Sleep Button'
    [ 26.089] (**) Sleep Button: always reports core events
    [ 26.089] (**) evdev: Sleep Button: Device: "/dev/input/event2"
    [ 26.089] (--) evdev: Sleep Button: Vendor 0 Product 0x3
    [ 26.089] (--) evdev: Sleep Button: Found keys
    [ 26.089] (II) evdev: Sleep Button: Configuring as keyboard
    [ 26.089] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input6/event2"
    [ 26.089] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 9)
    [ 26.089] (**) Option "xkb_rules" "evdev"
    [ 26.089] (**) Option "xkb_model" "pc104"
    [ 26.089] (**) Option "xkb_layout" "us"
    [ 26.090] (II) config/udev: Adding drm device (/dev/dri/card1)
    [ 26.090] (II) xfree86: Adding drm device (/dev/dri/card1)
    [ 26.090] (EE) /dev/dri/card1: failed to set DRM interface version 1.4: Permission denied
    [ 26.091] (II) config/udev: Adding input device USB 2.0 UVC VGA WebCam (/dev/input/event12)
    [ 26.091] (**) USB 2.0 UVC VGA WebCam: Applying InputClass "evdev keyboard catchall"
    [ 26.091] (II) Using input driver 'evdev' for 'USB 2.0 UVC VGA WebCam'
    [ 26.091] (**) USB 2.0 UVC VGA WebCam: always reports core events
    [ 26.091] (**) evdev: USB 2.0 UVC VGA WebCam: Device: "/dev/input/event12"
    [ 26.091] (--) evdev: USB 2.0 UVC VGA WebCam: Vendor 0x13d3 Product 0x5710
    [ 26.091] (--) evdev: USB 2.0 UVC VGA WebCam: Found keys
    [ 26.091] (II) evdev: USB 2.0 UVC VGA WebCam: Configuring as keyboard
    [ 26.091] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/input/input19/event12"
    [ 26.091] (II) XINPUT: Adding extended input device "USB 2.0 UVC VGA WebCam" (type: KEYBOARD, id 10)
    [ 26.091] (**) Option "xkb_rules" "evdev"
    [ 26.091] (**) Option "xkb_model" "pc104"
    [ 26.091] (**) Option "xkb_layout" "us"
    [ 26.092] (II) config/udev: Adding input device HDA Intel PCH Mic (/dev/input/event9)
    [ 26.092] (II) No input driver specified, ignoring this device.
    [ 26.092] (II) This device may have been added with another device file.
    [ 26.093] (II) config/udev: Adding input device HDA Intel PCH Headphone (/dev/input/event10)
    [ 26.093] (II) No input driver specified, ignoring this device.
    [ 26.093] (II) This device may have been added with another device file.
    [ 26.093] (II) config/udev: Adding input device HDA Intel PCH HDMI/DP,pcm=3 (/dev/input/event11)
    [ 26.093] (II) No input driver specified, ignoring this device.
    [ 26.093] (II) This device may have been added with another device file.
    [ 26.094] (II) config/udev: Adding input device Logitech USB Optical Mouse (/dev/input/event13)
    [ 26.094] (**) Logitech USB Optical Mouse: Applying InputClass "evdev pointer catchall"
    [ 26.094] (II) Using input driver 'evdev' for 'Logitech USB Optical Mouse'
    [ 26.094] (**) Logitech USB Optical Mouse: always reports core events
    [ 26.094] (**) evdev: Logitech USB Optical Mouse: Device: "/dev/input/event13"
    [ 26.094] (--) evdev: Logitech USB Optical Mouse: Vendor 0x46d Product 0xc05a
    [ 26.094] (--) evdev: Logitech USB Optical Mouse: Found 3 mouse buttons
    [ 26.094] (--) evdev: Logitech USB Optical Mouse: Found scroll wheel(s)
    [ 26.094] (--) evdev: Logitech USB Optical Mouse: Found relative axes
    [ 26.094] (--) evdev: Logitech USB Optical Mouse: Found x and y relative axes
    [ 26.094] (II) evdev: Logitech USB Optical Mouse: Configuring as mouse
    [ 26.094] (II) evdev: Logitech USB Optical Mouse: Adding scrollwheel support
    [ 26.094] (**) evdev: Logitech USB Optical Mouse: YAxisMapping: buttons 4 and 5
    [ 26.094] (**) evdev: Logitech USB Optical Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [ 26.094] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.1/4-1.1:1.0/0003:046D:C05A.0001/input/input20/event13"
    [ 26.094] (II) XINPUT: Adding extended input device "Logitech USB Optical Mouse" (type: MOUSE, id 11)
    [ 26.095] (II) evdev: Logitech USB Optical Mouse: initialized for relative axes.
    [ 26.095] (**) Logitech USB Optical Mouse: (accel) keeping acceleration scheme 1
    [ 26.095] (**) Logitech USB Optical Mouse: (accel) acceleration profile 0
    [ 26.095] (**) Logitech USB Optical Mouse: (accel) acceleration factor: 2.000
    [ 26.095] (**) Logitech USB Optical Mouse: (accel) acceleration threshold: 4
    [ 26.096] (II) config/udev: Adding input device Logitech USB Optical Mouse (/dev/input/mouse1)
    [ 26.096] (II) No input driver specified, ignoring this device.
    [ 26.096] (II) This device may have been added with another device file.
    [ 26.096] (II) config/udev: Adding input device Asus WMI hotkeys (/dev/input/event8)
    [ 26.096] (**) Asus WMI hotkeys: Applying InputClass "evdev keyboard catchall"
    [ 26.096] (II) Using input driver 'evdev' for 'Asus WMI hotkeys'
    [ 26.096] (**) Asus WMI hotkeys: always reports core events
    [ 26.096] (**) evdev: Asus WMI hotkeys: Device: "/dev/input/event8"
    [ 26.096] (--) evdev: Asus WMI hotkeys: Vendor 0 Product 0
    [ 26.096] (--) evdev: Asus WMI hotkeys: Found keys
    [ 26.096] (II) evdev: Asus WMI hotkeys: Configuring as keyboard
    [ 26.096] (**) Option "config_info" "udev:/sys/devices/platform/asus-nb-wmi/input/input15/event8"
    [ 26.096] (II) XINPUT: Adding extended input device "Asus WMI hotkeys" (type: KEYBOARD, id 12)
    [ 26.096] (**) Option "xkb_rules" "evdev"
    [ 26.096] (**) Option "xkb_model" "pc104"
    [ 26.096] (**) Option "xkb_layout" "us"
    [ 26.097] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
    [ 26.097] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
    [ 26.097] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
    [ 26.097] (**) AT Translated Set 2 keyboard: always reports core events
    [ 26.097] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event0"
    [ 26.098] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
    [ 26.098] (--) evdev: AT Translated Set 2 keyboard: Found keys
    [ 26.098] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
    [ 26.098] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
    [ 26.098] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 13)
    [ 26.098] (**) Option "xkb_rules" "evdev"
    [ 26.098] (**) Option "xkb_model" "pc104"
    [ 26.098] (**) Option "xkb_layout" "us"
    [ 26.099] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event7)
    [ 26.099] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "evdev touchpad catchall"
    [ 26.099] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad catchall"
    [ 26.099] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "Default clickpad buttons"
    [ 26.099] (II) LoadModule: "synaptics"
    [ 26.099] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
    [ 26.109] (II) Module synaptics: vendor="X.Org Foundation"
    [ 26.109] compiled for 1.16.0, module version = 1.8.1
    [ 26.109] Module class: X.Org XInput Driver
    [ 26.109] ABI class: X.Org XInput driver, version 21.0
    [ 26.109] (II) Using input driver 'synaptics' for 'SynPS/2 Synaptics TouchPad'
    [ 26.109] (**) SynPS/2 Synaptics TouchPad: always reports core events
    [ 26.109] (**) Option "Device" "/dev/input/event7"
    [ 26.210] (II) synaptics: SynPS/2 Synaptics TouchPad: ignoring touch events for semi-multitouch device
    [ 26.210] (--) synaptics: SynPS/2 Synaptics TouchPad: x-axis range 1472 - 5762 (res 52)
    [ 26.210] (--) synaptics: SynPS/2 Synaptics TouchPad: y-axis range 1408 - 4902 (res 83)
    [ 26.210] (--) synaptics: SynPS/2 Synaptics TouchPad: pressure range 0 - 255
    [ 26.210] (--) synaptics: SynPS/2 Synaptics TouchPad: finger width range 0 - 15
    [ 26.210] (--) synaptics: SynPS/2 Synaptics TouchPad: buttons: left right double triple
    [ 26.210] (--) synaptics: SynPS/2 Synaptics TouchPad: Vendor 0x2 Product 0x7
    [ 26.210] (**) Option "TapButton1" "1"
    [ 26.210] (**) Option "TapButton2" "2"
    [ 26.210] (**) Option "TapButton3" "3"
    [ 26.210] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
    [ 26.210] (**) SynPS/2 Synaptics TouchPad: always reports core events
    [ 26.263] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio4/input/input12/event7"
    [ 26.263] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD, id 14)
    [ 26.263] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MinSpeed is now constant deceleration 2.5
    [ 26.263] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MaxSpeed is now 1.75
    [ 26.263] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) AccelFactor is now 0.036
    [ 26.264] (**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
    [ 26.264] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration profile 1
    [ 26.264] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
    [ 26.264] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
    [ 26.264] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
    [ 26.264] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse0)
    [ 26.265] (**) SynPS/2 Synaptics TouchPad: Ignoring device from InputClass "touchpad ignore duplicates"
    [ 26.265] (II) config/udev: Adding input device PC Speaker (/dev/input/event4)
    [ 26.265] (II) No input driver specified, ignoring this device.
    [ 26.265] (II) This device may have been added with another device file.
    [ 26.282] removing GPU device /sys/devices/pci0000:00/0000:00:01.0/0000:01:00.0/drm/card1 /dev/dri/card1
    [ 26.282] (II) config/udev: Adding drm device (/dev/dri/card1)
    [ 26.282] (II) xfree86: Adding drm device (/dev/dri/card1)
    [ 26.282] (EE) /dev/dri/card1: failed to set DRM interface version 1.4: Permission denied
    [ 81.255] (II) intel(0): EDID vendor "AUO", prod id 9964
    [ 81.255] (II) intel(0): Printing DDC gathered Modelines:
    [ 81.255] (II) intel(0): Modeline "1366x768"x0.0 71.80 1366 1414 1446 1526 768 771 777 784 -hsync -vsync (47.1 kHz eP)
    [ 81.277] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 81.293] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 81.644] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 81.660] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 81.678] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 84.668] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 84.685] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 86.539] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 2962.717] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 2962.734] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 2966.160] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 2966.176] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 3045.352] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 3045.370] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 3066.487] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 3066.504] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 4507.909] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 4507.925] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 4568.870] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 4568.887] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 4749.685] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 4749.702] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 4841.172] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 4841.189] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 5067.684] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 5067.701] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 5098.091] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 5098.108] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 5231.697] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 5231.715] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 7726.903] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 7726.920] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 7989.858] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 7989.875] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 8118.003] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 8118.020] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 8525.573] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 8525.590] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 8645.496] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 8645.513] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 8787.791] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 8787.808] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 10010.206] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 10010.223] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 10511.439] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 10511.456] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 10576.580] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 10576.597] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 10758.287] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 10758.304] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 12833.372] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 12833.389] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 14722.424] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 14722.441] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 15499.091] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 15499.108] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 16138.293] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 16138.309] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 16563.842] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 16563.858] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 17097.871] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 17097.888] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 17958.793] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 17958.810] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 18046.490] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 18046.506] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 18286.639] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 18286.655] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 18857.140] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 18857.157] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 19683.981] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 19683.997] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 19746.465] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 19746.483] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 19801.499] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 19801.516] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 24516.593] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 24516.610] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 24714.424] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 24714.440] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 24733.954] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 24733.970] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 24794.748] (II) AIGLX: Suspending AIGLX clients for VT switch
    [ 24795.935] (II) AIGLX: Resuming AIGLX clients after VT switch
    [ 24795.935] (II) intel(0): switch to mode [email protected] on LVDS1 using pipe 0, position (0, 0), rotation normal, reflection none
    [ 24795.971] (II) NVIDIA(1): Setting mode "CRT-0:nvidia-auto-select"
    [ 24796.039] (II) NVIDIA(1): ACPI: failed to connect to the ACPI event daemon; the daemon
    [ 24796.039] (II) NVIDIA(1): may not be running or the "AcpidSocketPath" X
    [ 24796.039] (II) NVIDIA(1): configuration option may not be set correctly. When the
    [ 24796.039] (II) NVIDIA(1): ACPI event daemon is available, the NVIDIA X driver will
    [ 24796.039] (II) NVIDIA(1): try to use it to receive ACPI event notifications. For
    [ 24796.039] (II) NVIDIA(1): details, please see the "ConnectToAcpid" and
    [ 24796.039] (II) NVIDIA(1): "AcpidSocketPath" X configuration options in Appendix B: X
    [ 24796.040] (II) NVIDIA(1): Config Options in the README.
    [ 24796.057] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 24796.061] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
    [ 25764.817] (II) AIGLX: Suspending AIGLX clients for VT switch
    [ 25766.007] (II) AIGLX: Resuming AIGLX clients after VT switch
    [ 25766.007] (II) intel(0): switch to mode [email protected] on LVDS1 using pipe 0, position (0, 0), rotation normal, reflection none
    [ 25766.036] (II) NVIDIA(1): Setting mode "CRT-0:nvidia-auto-select"
    [ 25766.104] (II) NVIDIA(1): ACPI: failed to connect to the ACPI event daemon; the daemon
    [ 25766.104] (II) NVIDIA(1): may not be running or the "AcpidSocketPath" X
    [ 25766.104] (II) NVIDIA(1): configuration option may not be set correctly. When the
    [ 25766.104] (II) NVIDIA(1): ACPI event daemon is available, the NVIDIA X driver will
    [ 25766.104] (II) NVIDIA(1): try to use it to receive ACPI event notifications. For
    [ 25766.104] (II) NVIDIA(1): details, please see the "ConnectToAcpid" and
    [ 25766.104] (II) NVIDIA(1): "AcpidSocketPath" X configuration options in Appendix B: X
    [ 25766.104] (II) NVIDIA(1): Config Options in the README.
    [ 25766.122] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 25766.129] (EE) evdev: Logitech USB Optical Mouse: Unable to open evdev device "/dev/input/event13".
    [ 25766.129] [dix] couldn't enable device 11
    [ 25766.129] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
    [ 25766.132] (II) config/udev: removing device Logitech USB Optical Mouse
    [ 25766.132] (II) evdev: Logitech USB Optical Mouse: Close
    [ 25766.132] (II) UnloadModule: "evdev"
    [ 27662.047] (II) AIGLX: Suspending AIGLX clients for VT switch
    [ 27663.314] (II) AIGLX: Resuming AIGLX clients after VT switch
    [ 27663.314] (II) intel(0): switch to mode [email protected] on LVDS1 using pipe 0, position (0, 0), rotation normal, reflection none
    [ 27663.345] (II) NVIDIA(1): Setting mode "CRT-0:nvidia-auto-select"
    [ 27663.413] (II) NVIDIA(1): ACPI: failed to connect to the ACPI event daemon; the daemon
    [ 27663.413] (II) NVIDIA(1): may not be running or the "AcpidSocketPath" X
    [ 27663.413] (II) NVIDIA(1): configuration option may not be set correctly. When the
    [ 27663.413] (II) NVIDIA(1): ACPI event daemon is available, the NVIDIA X driver will
    [ 27663.413] (II) NVIDIA(1): try to use it to receive ACPI event notifications. For
    [ 27663.413] (II) NVIDIA(1): details, please see the "ConnectToAcpid" and
    [ 27663.413] (II) NVIDIA(1): "AcpidSocketPath" X configuration options in Appendix B: X
    [ 27663.413] (II) NVIDIA(1): Config Options in the README.
    [ 27663.431] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 27663.439] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
    [ 27694.770] (II) config/udev: Adding input device Logitech USB Optical Mouse (/dev/input/event13)
    [ 27694.770] (**) Logitech USB Optical Mouse: Applying InputClass "evdev pointer catchall"
    [ 27694.770] (II) Using input driver 'evdev' for 'Logitech USB Optical Mouse'
    [ 27694.770] (**) Logitech USB Optical Mouse: always reports core events
    [ 27694.770] (**) evdev: Logitech USB Optical Mouse: Device: "/dev/input/event13"
    [ 27694.770] (--) evdev: Logitech USB Optical Mouse: Vendor 0x46d Product 0xc05a
    [ 27694.770] (--) evdev: Logitech USB Optical Mouse: Found 3 mouse buttons
    [ 27694.770] (--) evdev: Logitech USB Optical Mouse: Found scroll wheel(s)
    [ 27694.770] (--) evdev: Logitech USB Optical Mouse: Found relative axes
    [ 27694.770] (--) evdev: Logitech USB Optical Mouse: Found x and y relative axes
    [ 27694.770] (II) evdev: Logitech USB Optical Mouse: Configuring as mouse
    [ 27694.770] (II) evdev: Logitech USB Optical Mouse: Adding scrollwheel support
    [ 27694.770] (**) evdev: Logitech USB Optical Mouse: YAxisMapping: buttons 4 and 5
    [ 27694.770] (**) evdev: Logitech USB Optical Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    [ 27694.770] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1d.0/usb4/4-1/4-1.1/4-1.1:1.0/0003:046D:C05A.0002/input/input39/event13"
    [ 27694.770] (II) XINPUT: Adding extended input device "Logitech USB Optical Mouse" (type: MOUSE, id 11)
    [ 27694.771] (II) evdev: Logitech USB Optical Mouse: initialized for relative axes.
    [ 27694.771] (**) Logitech USB Optical Mouse: (accel) keeping acceleration scheme 1
    [ 27694.771] (**) Logitech USB Optical Mouse: (accel) acceleration profile 0
    [ 27694.771] (**) Logitech USB Optical Mouse: (accel) acceleration factor: 2.000
    [ 27694.771] (**) Logitech USB Optical Mouse: (accel) acceleration threshold: 4
    [ 27694.771] (II) config/udev: Adding input device Logitech USB Optical Mouse (/dev/input/mouse1)
    [ 27694.771] (II) No input driver specified, ignoring this device.
    [ 27694.771] (II) This device may have been added with another device file.
    [ 28826.102] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 28826.119] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 28869.273] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 28869.290] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 29665.856] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 29665.873] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 29759.751] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 29759.768] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 30246.231] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 30246.248] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 31539.152] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 31539.168] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 33130.297] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 33130.314] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 35115.805] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 35115.822] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 36739.995] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 36740.011] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 37099.972] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 37099.988] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 37115.693] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 37115.709] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 37292.799] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 37292.816] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 37896.583] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 37896.600] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 40947.452] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 40947.469] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 40999.729] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 40999.746] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 41027.146] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 41027.163] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 41198.146] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 41198.162] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 41405.365] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 41405.382] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 43125.113] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 43125.128] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 43212.374] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 43212.391] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 44006.946] (II) AIGLX: Suspending AIGLX clients for VT switch
    [ 44008.163] (II) AIGLX: Resuming AIGLX clients after VT switch
    [ 44008.163] (II) intel(0): switch to mode [email protected] on LVDS1 using pipe 0, position (0, 0), rotation normal, reflection none
    [ 44008.193] (II) NVIDIA(1): Setting mode "CRT-0:nvidia-auto-select"
    [ 44008.262] (II) NVIDIA(1): ACPI: failed to connect to the ACPI event daemon; the daemon
    [ 44008.262] (II) NVIDIA(1): may not be running or the "AcpidSocketPath" X
    [ 44008.262] (II) NVIDIA(1): configuration option may not be set correctly. When the
    [ 44008.262] (II) NVIDIA(1): ACPI event daemon is available, the NVIDIA X driver will
    [ 44008.262] (II) NVIDIA(1): try to use it to receive ACPI event notifications. For
    [ 44008.262] (II) NVIDIA(1): details, please see the "ConnectToAcpid" and
    [ 44008.262] (II) NVIDIA(1): "AcpidSocketPath" X configuration options in Appendix B: X
    [ 44008.262] (II) NVIDIA(1): Config Options in the README.
    [ 44008.280] (WW) NVIDIA(GPU-0): Unable to read EDID for display device CRT-0
    [ 44008.287] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
    Please help me to resolve this.
    Last edited by vortex_ape (2015-02-22 14:39:47)

    I haven't been experiencing the issue for some hours.
    The issue occurred more frequently when I was compiling something. When I tried to reproduce the issue, it didn't occur.
    The interesting thing to note is that I updated the system twice in the past 2 days. I checked the pacman log and saw that xorg-server-common, xorg-server, xorg-server-devel were among the upgraded packages. I guess they were causing the problem.
    I'll need to test for a couple of days though before I consider the issue to be resolved. I'll update if the issue persists.

  • Hello. after updating to Ios 8 my iPhone is terribly! Discharged very quickly, many transitions between applications, the program takes off, ringtones do not work - works a standard call, the keyboard freezes, bad messages are sent, often loses the n

    Hello. after updating to Ios 8 my iPhone is terribly! Discharged very quickly, many transitions between applications, the program takes off, ringtones do not work - works a standard call, the keyboard freezes, bad messages are sent, often loses the network. what have you done with your phone moym ?! solve all these problems! I beg of you!

    Hello. after updating to Ios 8 my iPhone is terribly! Discharged very quickly, many transitions between applications, the program takes off, ringtones do not work - works a standard call, the keyboard freezes, bad messages are sent, often loses the network. what have you done with your phone moym ?! solve all these problems! I beg of you!

  • Macbook Keyboard freezing

    Hi All
    I get my macbook in just under 3 days it is a white 2.00Ghz Core 2 Duo, 1GB RAM, 120GB Hard drive model, it will also be running Mac OS X Leopard
    I was wondering if the keyboard freezing problem occurs on all Macbook's & Macbookpro's models or is it a certain some, of are all of them doomed.
    if we are then will I be able to install my copy of Mac OS X Tiger on the macbook, I'm asking this because I don't think tiger comes with the new X3100 graphics drivers for the Santa Rosa chips in the macbook.
    Can someone explain also why it only seems to be happening only in Leopard and when will we see a fix for it from Apple
    Thanks R Nicholson

    Lauraford, you seem to be having a similar problem to many other people here. Check out this thread: http://discussions.apple.com/thread.jspa?messageID=5786564

  • Keyboard freezing when forwarding a seached mail

    I am on OS 10.1.0.273, device Q10. My email is linked with my enterprise mail (exchange).
    Whenever I do a search, then forward one of the searched emails and start typing a message in the forwarded email, my keyboard freezes and no longer responds. Even after closing the email and trying other applications, the keyboard remains frozen and inactive. I have to restart the device to get the keyboard to work again.
    Is anyone else having this issue?

    DarynThompson wrote:
    this happens to me about 4 times a day. I have to sit and wait to get my keyboard back.
    it also locks up my use of the address bar in teh browser and Contact list, but sometimesit lets me use the keyboard within a webpage if I access it from a bookmark
    Hello DarynThompson and welcome to the BlackBerry Support Community Forums.
    To clarify, your keyboard is freezing when you attempt to search for an email as well or does your keyboard freeze in other applications?
    What is the software version of your device under Settings>About>OS?
    -HMthePirate
    Come follow your BlackBerry Technical Team on twitter! @BlackBerryHelp
    Be sure to click Kudos! for those who have helped you.Click Solution? for posts that have solved your issue(s)!

  • After using the clone tool my keyboard freezes up. Why?

    I am running Mac 10.6.8 and CS 5.5
    Photoshop: CS5.1
    After using the clone tool my keyboard freezes up. Why?
    When I use the clone tool repeadedly i can no loger use my keyboard.
    And that includes use for other applications.
    I have to do everything manually by scrolling down the menu bars.
    Also, I can't even type in any characters from the keyboard.
    Thanks everyone smarter than I.
    Vinny

    Thanks C,
    (Sorry I don;t know your full name.
    I followed your instructions and reset my preferences.
    Crossing my fingers.
    On another topic. I am running Design CS 5.5
    But when I checked "about Photoshop it only reads CS5 12.1 x64.
    Also, my prefs read CS5.1
    Please advise.
    I also seem to have prefs I may not need. I thought when I installed 5.5 my
    old Photoshop version prefs would be deleted but they are still there (see
    my snapshop of my pref files. Should I trash any?
    image: Inline image 1
    Thanks again C,
    Vinny
    On Wed, Jan 15, 2014 at 11:18 PM, c.pfaffenbichler <[email protected]

  • Keyboard freezes when I try to switch users

    Hi, I've run into a vey interesting/perplexing problem.  My PC has two users on it, one is local with no password and the other not local and password protected.  When I try to switch between users my wired USB keyboard becomes unresponsive - if I'm switching to the account that requires a password, I can't type it in.  This problem occurs regardless of which account I'm switching to.
    I've tried uninstalling all the keyboards through device manager and rebooting.  Keyboard works until I try to switch users.
    Interesting development that I stumbled across - if I just unplug the keyboard and plug it back in everything is fine until I try to switch users.
    During my research, I found an article that referenced disabling the XHCI and enabling legacy USB support.  Problem with that, is that I haven't been able to find that setting in the BIOS anywhere.
    Very bizarre!
    Any help would be greatly appreciated.
    Thanks, RG

    Hello @Goose1961,
    Welcome to the HP Forums, I hope you enjoy your experience! To help you get the most out of the HP Forums I would like to direct your attention to the HP Forums Guide First Time Here? Learn How to Post and More.
    I have read your post on how your keyboard freezes when you try to switch users on you desktop computer, and I would be happy to assist you in this matter!
    To ensure your system is able to recognize the keyboard when switching accounts, I recommend following the steps in this document on How to Add or Remove "USB selective suspend setting" in Power Options in Windows. This should help to disable USB selective suspend on both accounts after restarting your computer.
    Please re-post with the results of your troubleshooting, and I look forward to your reply!
    Regards
    MechPilot
    I work on behalf of HP
    Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
    Click the “Kudos, Thumbs Up" on the right to say “Thanks” for helping!

  • IOS 8.3 keyboard freezes - iPhone 6

    Has anyone else experienced the keyboard freezing after using an emoji on the new iOS 8.3? It freezes on the emoji keyboard, showing "emoji added", and I can't get back to the alpha/numeric keyboard to type text.  I touch the globe (and everything else) but nothing happens.

    There have been posts like yours after every update since iOS 1.0.1, 2007.  The problem is corrupted data or settings during the update.  Downgrading, even if supported, wouldn't help at all.
    Assuming the phone was never hacked/jailbroken (the most common cause of your issues), try these steps as needed:
    Reset phone (no data loss): press both the home and lock buttons for at least 10 seconds, releasing when the Apple logo appears
    Settings > General > Reset > Reset All Settings
    Restore to factory settings using iTunes, also restoring a backup
    Restore to factory settings as new (no backup restored)
    Use iTunes to restore your iOS device to factory settings

  • Keyboard freezes up every so often..

    I just purchased a 13" MacBook about 4 days ago and I've been having an issue where I will be on the internet or typing something and my keyboard will suddenly stop working. The keys are pressed but there is no response. It is the entire keyboard that does not work, including the F keys, num keys, etc. After about 3 minutes, the problem fixes itself and everything functions normally. Any suggestions?

    My week old MacBook has the same problem, they keyboard freezes, the keyboard stops working, even the caps lock key fails and dose not toggle.
    I'm totally locked out.
    This brand new mac also has a dodge/faulty ether net connection and only one of the external USB ports works!
    Very disappointing for a new machine! The Apple store will not simply replace it, forcing me to make another long trip their again this week just to see some "Genius".

  • Keyboard freezes in msg app

    Hi
    When typing an sms msg sometimes the keyboard 'freezes' for a couple of seconds. If I keep typing there is no indication of anything happening but after about 10 seconds all the letters I pressed suddenly appear on screen. I tried a back-up and restore, a reset and turning the ph off with the home and off buttons but still no good.
    The keypad in the other apps,(mail etc) are OK, it's only the messages app
    Thanks
    Geoff

    power cycle, reset all settings, if still having problems import photos, transfer purchases, sync contacts calendars and notes. then restore as new. if problem persists get replacement at apple store or call in for mail in repair

Maybe you are looking for

  • Plant to Company Code

    Hi Gurus, I am new to SAP MM. I was asked to re-assign a plant to another company code. I know how to assign(OX18).But do i have to delete the previous one and assign it to the new one. Eg: Plant 25 is assigned to CC 34,now they wanted me to assign i

  • Is OCI (Open Cataloge Interface) supported from MM or SD

    Hello. My customer has installed SAP ERP, but do not have SAP SRM. We plan to implement a punch-out from SAP to a web site of Cisco with use of OCI. I do find a lot of information about OCI related to SRM, but none related to ERP. Does anybody know w

  • Need some info regarding BWA1 transaction in CRM

    Hi,   I am trying to understand few things for the BWA1 transaction. Looks like we need to explore the BWA1 transaction for data source enhancement before trying the classical Data source enhancement method (Append structure in the Data source ) in R

  • Adobe creatpdf desktop printer

    when using adobe creatpdf destop printer, where does the file end up

  • I have Camera Raw 8.7.1 and I don't have camera raw filter and the radial filter tool

    I have Camera Raw 8.7.1 and I don't have camera raw filter or the radial filter tool.  Reading on line says it should be available?  I am confused... why do I not have these tools?