E-Filing GB : problem

XI ver: 7
ERP ver: 2006
E-Filing ver: 1.0
I am trying to configure e-filing for GB based on the configuration guide. After importing the latest XI content for E-Filing and HR, I tried to configure the outbound and inbound interfaces in ID. But I received errors about missing message interface. When I go into IR and go to menu Component View->Check Configurability, I get errors that outbound interfaces HR_GB_EFO_EOYR_OUT and HR_GB_EFO_RESP_OUT do not exist.
I read the thread
E-Filing GB - Outbound interfaces do not exist
Do i have to do something on pi sap basis ?
Any help would be appreciated.
Regards.
Jean-Philippe
Edited by: Jean-Philippe PAIN on Feb 15, 2008 3:39 PM

John,
We are getting an communication Error in E-Filing (Outgoing)
Please help us to fix it.
The error is
Find below the trace from BC.
2008-04-15 17:10:10 GMT+05:30 com.wm.app.b2b.server.ServiceException: java.io.EOFException: Connection closed by remote host.
        at com.wm.util.LocalizedException.<init>(LocalizedException.java:95)
        at com.wm.app.b2b.server.ServerException.<init>(ServerException.java:30)
        at com.wm.app.b2b.server.ServiceException.<init>(ServiceException.java:24)
        at pub.sap.transport.RFC.InboundProcess(RFC.java:239)
        at java.lang.reflect.Method.invoke(Native Method)
        at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:281)
        at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:716)
        at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:473)
        at com.wm.app.b2b.server.Service.doInvoke(Service.java:495)
        at com.wm.app.b2b.server.Service.doInvoke(Service.java:392)
        at com.wm.pkg.sap.rfc.RFCApi.InboundProcess(RFCApi.java:61)
        at com.wm.pkg.sap.rfc.Listener.handleRequest(Listener.java:184)
        at com.sap.mw.jco.JCO$Server.dispatchRequest(Unknown Source)
        at com.sap.mw.jco.rfc.MiddlewareRFC$Server.nativeListen(Native Method)
        at com.sap.mw.jco.rfc.MiddlewareRFC$Server.listen(Unknown Source)
        at com.sap.mw.jco.JCO$Server.listen(Unknown Source)
        at com.sap.mw.jco.JCO$Server.run(Unknown Source)
        at com.wm.pkg.sap.rfc.Listener.run(Listener.java:92)
        at java.lang.Thread.run(Thread.java:498)

Similar Messages

Help required for Hilbert Space Filing Curve problem

Can someone suggest the algorithm for the following problem:
Given an N � N array A, generate the index of each location A[i][j] according to Hilbert Space Filling curve. The Hilbert curve generates the indices recursively as follows - for a 2 � 2 square the numbering is
2 3
1 4
For a 2^i � 2^i array, the array is first partitioned into 4 subsquares of 2^(i-1) � 2^(i-1). Then the indices of each sub-square is generated recursively such that the lower-left array has the lowest indices followed by upper-left array and then the upper-right and the lower-right array. Moreover, consecutive indices should be in neighbouring squares. For a 4 � 4 array, the indices are
6 7 10 11
5 8 9 12
4 3 14 13
1 2 15 16
Thanks

HeadSwipe wrote:
Can someone suggest the algorithm for the following problem:
Given an N � N array A, generate the index of each location A[i][j] according to Hilbert Space Filling curve. The Hilbert curve generates the indices recursively as follows - for a 2 � 2 square the numbering is
2 3
1 4
I'd recommend one that features recursion.
For a 2^i � 2^i array, the array is first partitioned into 4 subsquares of 2^(i-1) � 2^(i-1). Then the indices of each sub-square is generated recursively such that the lower-left array has the lowest indices followed by upper-left array and then the upper-right and the lower-right array. Moreover, consecutive indices should be in neighbouring squares. This IS the algorithm. You've been given it. You either don't understand it or can't code it.
I'd start wih a Matrix class that would make it easy to do the partitioning into submatricies. Then I'd write a method that would take a Matrix as an argument and call it recursively until I reached my 2x2 Matrix stopping condition.
For a 4 � 4 array, the indices are
6 7 10 11
5 8 9 12
4 3 14 13
1 2 15 16
ThanksSounds like you've been given the algorithm, now all you have to do is implement. That's where you come in.
%

Problem with changing layouts in xorg

Hi,
After installing new system (latest) i cant change layouts from keyboard
/etc/X11/xorg.conf
# nvidia-xconfig: X configuration file generated by nvidia-xconfig
# nvidia-xconfig: version 304.60 ([email protected]) Sun Oct 14 21:34:47 PDT 2012
Section "ServerLayout"
Identifier "Layout0"
Screen 0 "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"
Option "XkbOptions" "grp:ctrl_shift_toggle"
EndSection
Section "Monitor"
Identifier "Monitor0"
VendorName "Unknown"
ModelName "Unknown"
HorizSync 28.0 - 33.0
VertRefresh 43.0 - 72.0
Option "DPMS"
EndSection
Section "Device"
Identifier "Device0"
Driver "nvidia"
VendorName "NVIDIA Corporation"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Depth 24
EndSubSection
EndSection
/etc/X11/xorg.conf.d/10-evdev.conf
Section "InputClass"
Identifier "evdev pointer catchall"
MatchIsPointer "on"
MatchDevicePath "/dev/input/event*"
Driver "evdev"
EndSection
Section "InputClass"
Identifier "evdev keyboard catchall"
MatchIsKeyboard "on"
MatchDevicePath "/dev/input/event*"
Driver "evdev"
Option "XkbVariant" ","
Option "XkbLayout" "us,ru"
Option "XkbOptions" "grp:ctrl_shift_toggle"
# Option "XkbOptions" "grp:caps_toggle,grp_led:scroll"
EndSection
Xorg log
[ 3949.901]
X.Org X Server 1.13.0
Release Date: 2012-09-05
[ 3949.901] X Protocol Version 11, Revision 0
[ 3949.901] Build Operating System: Linux 3.6.2-1-ARCH x86_64
[ 3949.901] Current Operating System: Linux Hybrid 3.6.6-1-ARCH #1 SMP PREEMPT Mon Nov 5 11:57:22 CET 2012 x86_64
[ 3949.901] Kernel command line: BOOT_IMAGE=/vmlinuz-linux root=UUID=34540cd4-1fc1-4e6d-815f-f26b49fd0ffd ro quiet
[ 3949.901] Build Date: 19 October 2012 03:54:56PM
[ 3949.902]
[ 3949.902] Current version of pixman: 0.26.2
[ 3949.902] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 3949.902] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 3949.902] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Nov 7 15:47:17 2012
[ 3949.902] (==) Using config file: "/etc/X11/xorg.conf"
[ 3949.902] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 3949.902] (==) ServerLayout "Layout0"
[ 3949.902] (**) |-->Screen "Screen0" (0)
[ 3949.902] (**) | |-->Monitor "Monitor0"
[ 3949.902] (**) | |-->Device "Device0"
[ 3949.902] (**) |-->Input Device "Keyboard0"
[ 3949.902] (**) |-->Input Device "Mouse0"
[ 3949.902] (==) Automatically adding devices
[ 3949.902] (==) Automatically enabling devices
[ 3949.902] (==) Automatically adding GPU devices
[ 3949.902] (WW) The directory "/usr/share/fonts/OTF/" does not exist.
[ 3949.902] Entry deleted from font path.
[ 3949.902] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 3949.902] Entry deleted from font path.
[ 3949.902] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 3949.902] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 3949.902] Entry deleted from font path.
[ 3949.902] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 3949.902] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/Type1/
[ 3949.902] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 3949.902] (WW) Hotplugging is on, devices using drivers 'kbd', 'mouse' or 'vmmouse' will be disabled.
[ 3949.902] (WW) Disabling Keyboard0
[ 3949.902] (WW) Disabling Mouse0
[ 3949.902] (II) Module ABI versions:
[ 3949.902] X.Org ANSI C Emulation: 0.4
[ 3949.902] X.Org Video Driver: 13.0
[ 3949.902] X.Org XInput driver : 18.0
[ 3949.902] X.Org Server Extension : 7.0
[ 3949.904] (--) PCI:*(0:1:0:0) 10de:11c0:1043:8423 rev 161, Mem @ 0xf6000000/16777216, 0xe8000000/134217728, 0xf0000000/33554432, I/O @ 0x0000e000/128, BIOS @ 0x????????/524288
[ 3949.904] (WW) Open ACPI failed (/var/run/acpid.socket) (No such file or directory)
[ 3949.904] Initializing built-in extension Generic Event Extension
[ 3949.904] Initializing built-in extension SHAPE
[ 3949.904] Initializing built-in extension MIT-SHM
[ 3949.904] Initializing built-in extension XInputExtension
[ 3949.904] Initializing built-in extension XTEST
[ 3949.904] Initializing built-in extension BIG-REQUESTS
[ 3949.904] Initializing built-in extension SYNC
[ 3949.904] Initializing built-in extension XKEYBOARD
[ 3949.904] Initializing built-in extension XC-MISC
[ 3949.904] Initializing built-in extension SECURITY
[ 3949.904] Initializing built-in extension XINERAMA
[ 3949.904] Initializing built-in extension XFIXES
[ 3949.904] Initializing built-in extension RENDER
[ 3949.904] Initializing built-in extension RANDR
[ 3949.904] Initializing built-in extension COMPOSITE
[ 3949.904] Initializing built-in extension DAMAGE
[ 3949.904] Initializing built-in extension MIT-SCREEN-SAVER
[ 3949.904] Initializing built-in extension DOUBLE-BUFFER
[ 3949.904] Initializing built-in extension RECORD
[ 3949.904] Initializing built-in extension DPMS
[ 3949.904] Initializing built-in extension X-Resource
[ 3949.904] Initializing built-in extension XVideo
[ 3949.904] Initializing built-in extension XVideo-MotionCompensation
[ 3949.904] Initializing built-in extension XFree86-VidModeExtension
[ 3949.904] Initializing built-in extension XFree86-DGA
[ 3949.904] Initializing built-in extension XFree86-DRI
[ 3949.904] Initializing built-in extension DRI2
[ 3949.904] (II) LoadModule: "glx"
[ 3949.904] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 3949.914] (II) Module glx: vendor="NVIDIA Corporation"
[ 3949.914] compiled for 4.0.2, module version = 1.0.0
[ 3949.914] Module class: X.Org Server Extension
[ 3949.914] (II) NVIDIA GLX Module 304.60 Sun Oct 14 20:44:54 PDT 2012
[ 3949.914] Loading extension GLX
[ 3949.914] (II) LoadModule: "nvidia"
[ 3949.915] (II) Loading /usr/lib/xorg/modules/drivers/nvidia_drv.so
[ 3949.915] (II) Module nvidia: vendor="NVIDIA Corporation"
[ 3949.915] compiled for 4.0.2, module version = 1.0.0
[ 3949.915] Module class: X.Org Video Driver
[ 3949.915] (II) NVIDIA dlloader X Driver 304.60 Sun Oct 14 20:24:42 PDT 2012
[ 3949.915] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 3949.915] (++) using VT number 1
[ 3949.915] (II) Loading sub module "fb"
[ 3949.915] (II) LoadModule: "fb"
[ 3949.915] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 3949.916] (II) Module fb: vendor="X.Org Foundation"
[ 3949.916] compiled for 1.13.0, module version = 1.0.0
[ 3949.916] ABI class: X.Org ANSI C Emulation, version 0.4
[ 3949.916] (II) Loading sub module "wfb"
[ 3949.916] (II) LoadModule: "wfb"
[ 3949.916] (II) Loading /usr/lib/xorg/modules/libwfb.so
[ 3949.916] (II) Module wfb: vendor="X.Org Foundation"
[ 3949.916] compiled for 1.13.0, module version = 1.0.0
[ 3949.916] ABI class: X.Org ANSI C Emulation, version 0.4
[ 3949.916] (II) Loading sub module "ramdac"
[ 3949.916] (II) LoadModule: "ramdac"
[ 3949.916] (II) Module "ramdac" already built-in
[ 3949.916] (**) NVIDIA(0): Depth 24, (--) framebuffer bpp 32
[ 3949.916] (==) NVIDIA(0): RGB weight 888
[ 3949.916] (==) NVIDIA(0): Default visual is TrueColor
[ 3949.916] (==) NVIDIA(0): Using gamma correction (1.0, 1.0, 1.0)
[ 3949.916] (**) NVIDIA(0): Enabling 2D acceleration
[ 3950.393] (II) NVIDIA(GPU-0): Display (Samsung SMBX2331 (DFP-0)) does not support NVIDIA 3D
[ 3950.393] (II) NVIDIA(GPU-0): Vision stereo.
[ 3950.403] (II) NVIDIA(GPU-0): Display (Samsung SMBX2331 (DFP-3)) does not support NVIDIA 3D
[ 3950.403] (II) NVIDIA(GPU-0): Vision stereo.
[ 3950.403] (II) NVIDIA(0): NVIDIA GPU GeForce GTX 660 (GK106) at PCI:1:0:0 (GPU-0)
[ 3950.403] (--) NVIDIA(0): Memory: 2097152 kBytes
[ 3950.403] (--) NVIDIA(0): VideoBIOS: 80.06.10.00.0e
[ 3950.403] (II) NVIDIA(0): Detected PCI Express Link width: 16X
[ 3950.403] (--) NVIDIA(0): Interlaced video modes are supported on this GPU
[ 3950.406] (--) NVIDIA(0): Valid display device(s) on GeForce GTX 660 at PCI:1:0:0
[ 3950.406] (--) NVIDIA(0): CRT-0
[ 3950.406] (--) NVIDIA(0): Samsung SMBX2331 (DFP-0) (connected)
[ 3950.406] (--) NVIDIA(0): DFP-1
[ 3950.406] (--) NVIDIA(0): DFP-2
[ 3950.406] (--) NVIDIA(0): Samsung SMBX2331 (DFP-3) (connected)
[ 3950.406] (--) NVIDIA(0): DFP-4
[ 3950.406] (--) NVIDIA(0): CRT-0: 400.0 MHz maximum pixel clock
[ 3950.406] (--) NVIDIA(0): Samsung SMBX2331 (DFP-0): 330.0 MHz maximum pixel clock
[ 3950.406] (--) NVIDIA(0): Samsung SMBX2331 (DFP-0): Internal Dual Link TMDS
[ 3950.406] (--) NVIDIA(0): DFP-1: 165.0 MHz maximum pixel clock
[ 3950.406] (--) NVIDIA(0): DFP-1: Internal Single Link TMDS
[ 3950.406] (--) NVIDIA(0): DFP-2: 165.0 MHz maximum pixel clock
[ 3950.406] (--) NVIDIA(0): DFP-2: Internal Single Link TMDS
[ 3950.406] (--) NVIDIA(0): Samsung SMBX2331 (DFP-3): 330.0 MHz maximum pixel clock
[ 3950.406] (--) NVIDIA(0): Samsung SMBX2331 (DFP-3): Internal Dual Link TMDS
[ 3950.406] (--) NVIDIA(0): DFP-4: 960.0 MHz maximum pixel clock
[ 3950.406] (--) NVIDIA(0): DFP-4: Internal DisplayPort
[ 3950.406] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 3950.406] (**) NVIDIA(0): device Samsung SMBX2331 (DFP-0) (Using EDID frequencies
[ 3950.406] (**) NVIDIA(0): has been enabled on all display devices.)
[ 3950.407] (WW) NVIDIA(GPU-0): The EDID for Samsung SMBX2331 (DFP-0) contradicts itself: mode
[ 3950.407] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[ 3950.407] (WW) NVIDIA(GPU-0): valid HorizSync range (31.000-81.000 kHz) would exclude
[ 3950.407] (WW) NVIDIA(GPU-0): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 3950.407] (WW) NVIDIA(GPU-0): for mode "1920x1080".
[ 3950.407] (WW) NVIDIA(GPU-0): The EDID for Samsung SMBX2331 (DFP-0) contradicts itself: mode
[ 3950.407] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[ 3950.407] (WW) NVIDIA(GPU-0): valid HorizSync range (31.000-81.000 kHz) would exclude
[ 3950.407] (WW) NVIDIA(GPU-0): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 3950.407] (WW) NVIDIA(GPU-0): for mode "1920x1080".
[ 3950.408] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 3950.408] (**) NVIDIA(0): device Samsung SMBX2331 (DFP-3) (Using EDID frequencies
[ 3950.408] (**) NVIDIA(0): has been enabled on all display devices.)
[ 3950.408] (WW) NVIDIA(GPU-0): The EDID for Samsung SMBX2331 (DFP-3) contradicts itself: mode
[ 3950.408] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[ 3950.408] (WW) NVIDIA(GPU-0): valid HorizSync range (31.000-81.000 kHz) would exclude
[ 3950.408] (WW) NVIDIA(GPU-0): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 3950.408] (WW) NVIDIA(GPU-0): for mode "1920x1080".
[ 3950.409] (WW) NVIDIA(GPU-0): The EDID for Samsung SMBX2331 (DFP-3) contradicts itself: mode
[ 3950.409] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[ 3950.409] (WW) NVIDIA(GPU-0): valid HorizSync range (31.000-81.000 kHz) would exclude
[ 3950.409] (WW) NVIDIA(GPU-0): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 3950.409] (WW) NVIDIA(GPU-0): for mode "1920x1080".
[ 3950.410] (==) NVIDIA(0):
[ 3950.410] (==) NVIDIA(0): No modes were requested; the default mode "nvidia-auto-select"
[ 3950.410] (==) NVIDIA(0): will be used as the requested mode.
[ 3950.410] (==) NVIDIA(0):
[ 3950.410] (II) NVIDIA(0): Validated MetaModes:
[ 3950.410] (II) NVIDIA(0): "DFP-0:nvidia-auto-select,DFP-3:nvidia-auto-select"
[ 3950.410] (II) NVIDIA(0): Virtual screen size determined to be 3840 x 1080
[ 3950.443] (--) NVIDIA(0): DPI set to (95, 94); computed from "UseEdidDpi" X config
[ 3950.443] (--) NVIDIA(0): option
[ 3950.443] (--) Depth 24 pixmap format is 32 bpp
[ 3950.443] (II) NVIDIA: Using 3072.00 MB of virtual memory for indirect memory
[ 3950.443] (II) NVIDIA: access.
[ 3950.445] (II) NVIDIA(0): ACPI: failed to connect to the ACPI event daemon; the daemon
[ 3950.445] (II) NVIDIA(0): may not be running or the "AcpidSocketPath" X
[ 3950.445] (II) NVIDIA(0): configuration option may not be set correctly. When the
[ 3950.445] (II) NVIDIA(0): ACPI event daemon is available, the NVIDIA X driver will
[ 3950.445] (II) NVIDIA(0): try to use it to receive ACPI event notifications. For
[ 3950.445] (II) NVIDIA(0): details, please see the "ConnectToAcpid" and
[ 3950.445] (II) NVIDIA(0): "AcpidSocketPath" X configuration options in Appendix B: X
[ 3950.445] (II) NVIDIA(0): Config Options in the README.
[ 3950.448] (II) NVIDIA(0): Setting mode "DFP-0:nvidia-auto-select,DFP-3:nvidia-auto-select"
[ 3950.551] Loading extension NV-GLX
[ 3950.608] (==) NVIDIA(0): Disabling shared memory pixmaps
[ 3950.608] (==) NVIDIA(0): Backing store disabled
[ 3950.608] (==) NVIDIA(0): Silken mouse enabled
[ 3950.608] (**) NVIDIA(0): DPMS enabled
[ 3950.608] Loading extension NV-CONTROL
[ 3950.609] Loading extension XINERAMA
[ 3950.609] (II) Loading sub module "dri2"
[ 3950.609] (II) LoadModule: "dri2"
[ 3950.609] (II) Module "dri2" already built-in
[ 3950.609] (II) NVIDIA(0): [DRI2] Setup complete
[ 3950.609] (II) NVIDIA(0): [DRI2] VDPAU driver: nvidia
[ 3950.609] (--) RandR disabled
[ 3950.611] (II) Initializing extension GLX
[ 3950.643] (II) config/udev: Adding input device Power Button (/dev/input/event1)
[ 3950.643] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 3950.643] (II) LoadModule: "evdev"
[ 3950.643] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 3950.643] (II) Module evdev: vendor="X.Org Foundation"
[ 3950.643] compiled for 1.13.0, module version = 2.7.3
[ 3950.643] Module class: X.Org XInput Driver
[ 3950.643] ABI class: X.Org XInput driver, version 18.0
[ 3950.643] (II) Using input driver 'evdev' for 'Power Button'
[ 3950.643] (**) Power Button: always reports core events
[ 3950.643] (**) evdev: Power Button: Device: "/dev/input/event1"
[ 3950.643] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 3950.644] (--) evdev: Power Button: Found keys
[ 3950.644] (II) evdev: Power Button: Configuring as keyboard
[ 3950.644] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input1/event1"
[ 3950.644] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 3950.644] (**) Option "xkb_rules" "evdev"
[ 3950.644] (**) Option "xkb_model" "evdev"
[ 3950.644] (**) Option "xkb_layout" "us,ru"
[ 3950.644] (**) Option "xkb_options" "grp:ctrl_shift_toggle"
[ 3950.663] (II) config/udev: Adding input device Power Button (/dev/input/event0)
[ 3950.663] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 3950.663] (II) Using input driver 'evdev' for 'Power Button'
[ 3950.663] (**) Power Button: always reports core events
[ 3950.663] (**) evdev: Power Button: Device: "/dev/input/event0"
[ 3950.663] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 3950.663] (--) evdev: Power Button: Found keys
[ 3950.663] (II) evdev: Power Button: Configuring as keyboard
[ 3950.663] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input0/event0"
[ 3950.663] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 7)
[ 3950.663] (**) Option "xkb_rules" "evdev"
[ 3950.663] (**) Option "xkb_model" "evdev"
[ 3950.663] (**) Option "xkb_layout" "us,ru"
[ 3950.663] (**) Option "xkb_options" "grp:ctrl_shift_toggle"
[ 3950.663] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=9 (/dev/input/event13)
[ 3950.663] (II) No input driver specified, ignoring this device.
[ 3950.663] (II) This device may have been added with another device file.
[ 3950.664] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event14)
[ 3950.664] (II) No input driver specified, ignoring this device.
[ 3950.664] (II) This device may have been added with another device file.
[ 3950.664] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event15)
[ 3950.664] (II) No input driver specified, ignoring this device.
[ 3950.664] (II) This device may have been added with another device file.
[ 3950.664] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event16)
[ 3950.664] (II) No input driver specified, ignoring this device.
[ 3950.664] (II) This device may have been added with another device file.
[ 3950.664] (II) config/udev: Adding input device UVC Camera (046d:0821) (/dev/input/event6)
[ 3950.664] (**) UVC Camera (046d:0821): Applying InputClass "evdev keyboard catchall"
[ 3950.664] (II) Using input driver 'evdev' for 'UVC Camera (046d:0821)'
[ 3950.664] (**) UVC Camera (046d:0821): always reports core events
[ 3950.664] (**) evdev: UVC Camera (046d:0821): Device: "/dev/input/event6"
[ 3950.664] (--) evdev: UVC Camera (046d:0821): Vendor 0x46d Product 0x821
[ 3950.664] (--) evdev: UVC Camera (046d:0821): Found keys
[ 3950.664] (II) evdev: UVC Camera (046d:0821): Configuring as keyboard
[ 3950.664] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4:1.2/input/input6/event6"
[ 3950.664] (II) XINPUT: Adding extended input device "UVC Camera (046d:0821)" (type: KEYBOARD, id 8)
[ 3950.664] (**) Option "xkb_rules" "evdev"
[ 3950.664] (**) Option "xkb_model" "evdev"
[ 3950.664] (**) Option "xkb_layout" "us,ru"
[ 3950.664] (**) Option "xkb_options" "grp:ctrl_shift_toggle"
[ 3950.664] (II) config/udev: Adding input device Razer Razer Mamba Charging Dock (/dev/input/event3)
[ 3950.664] (**) Razer Razer Mamba Charging Dock: Applying InputClass "evdev pointer catchall"
[ 3950.664] (II) Using input driver 'evdev' for 'Razer Razer Mamba Charging Dock'
[ 3950.664] (**) Razer Razer Mamba Charging Dock: always reports core events
[ 3950.664] (**) evdev: Razer Razer Mamba Charging Dock: Device: "/dev/input/event3"
[ 3950.664] (--) evdev: Razer Razer Mamba Charging Dock: Vendor 0x1532 Product 0xf
[ 3950.664] (--) evdev: Razer Razer Mamba Charging Dock: Found 11 mouse buttons
[ 3950.664] (--) evdev: Razer Razer Mamba Charging Dock: Found scroll wheel(s)
[ 3950.664] (--) evdev: Razer Razer Mamba Charging Dock: Found relative axes
[ 3950.664] (--) evdev: Razer Razer Mamba Charging Dock: Found x and y relative axes
[ 3950.664] (II) evdev: Razer Razer Mamba Charging Dock: Configuring as mouse
[ 3950.664] (II) evdev: Razer Razer Mamba Charging Dock: Adding scrollwheel support
[ 3950.664] (**) evdev: Razer Razer Mamba Charging Dock: YAxisMapping: buttons 4 and 5
[ 3950.664] (**) evdev: Razer Razer Mamba Charging Dock: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 3950.664] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.5/3-1.5:1.0/input/input3/event3"
[ 3950.664] (II) XINPUT: Adding extended input device "Razer Razer Mamba Charging Dock" (type: MOUSE, id 9)
[ 3950.664] (II) evdev: Razer Razer Mamba Charging Dock: initialized for relative axes.
[ 3950.665] (**) Razer Razer Mamba Charging Dock: (accel) keeping acceleration scheme 1
[ 3950.665] (**) Razer Razer Mamba Charging Dock: (accel) acceleration profile 0
[ 3950.665] (**) Razer Razer Mamba Charging Dock: (accel) acceleration factor: 2.000
[ 3950.665] (**) Razer Razer Mamba Charging Dock: (accel) acceleration threshold: 4
[ 3950.665] (II) config/udev: Adding input device Razer Razer Mamba Charging Dock (/dev/input/mouse0)
[ 3950.665] (II) No input driver specified, ignoring this device.
[ 3950.665] (II) This device may have been added with another device file.
[ 3950.665] (II) config/udev: Adding input device Razer Razer Mamba Charging Dock (/dev/input/event4)
[ 3950.665] (**) Razer Razer Mamba Charging Dock: Applying InputClass "evdev keyboard catchall"
[ 3950.665] (II) Using input driver 'evdev' for 'Razer Razer Mamba Charging Dock'
[ 3950.665] (**) Razer Razer Mamba Charging Dock: always reports core events
[ 3950.665] (**) evdev: Razer Razer Mamba Charging Dock: Device: "/dev/input/event4"
[ 3950.665] (--) evdev: Razer Razer Mamba Charging Dock: Vendor 0x1532 Product 0xf
[ 3950.665] (--) evdev: Razer Razer Mamba Charging Dock: Found 1 mouse buttons
[ 3950.665] (--) evdev: Razer Razer Mamba Charging Dock: Found scroll wheel(s)
[ 3950.665] (--) evdev: Razer Razer Mamba Charging Dock: Found relative axes
[ 3950.665] (II) evdev: Razer Razer Mamba Charging Dock: Forcing relative x/y axes to exist.
[ 3950.665] (--) evdev: Razer Razer Mamba Charging Dock: Found absolute axes
[ 3950.665] (II) evdev: Razer Razer Mamba Charging Dock: Forcing absolute x/y axes to exist.
[ 3950.665] (--) evdev: Razer Razer Mamba Charging Dock: Found keys
[ 3950.665] (II) evdev: Razer Razer Mamba Charging Dock: Configuring as mouse
[ 3950.665] (II) evdev: Razer Razer Mamba Charging Dock: Configuring as keyboard
[ 3950.665] (II) evdev: Razer Razer Mamba Charging Dock: Adding scrollwheel support
[ 3950.665] (**) evdev: Razer Razer Mamba Charging Dock: YAxisMapping: buttons 4 and 5
[ 3950.665] (**) evdev: Razer Razer Mamba Charging Dock: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 3950.665] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.5/3-1.5:1.1/input/input4/event4"
[ 3950.665] (II) XINPUT: Adding extended input device "Razer Razer Mamba Charging Dock" (type: KEYBOARD, id 10)
[ 3950.665] (**) Option "xkb_rules" "evdev"
[ 3950.665] (**) Option "xkb_model" "evdev"
[ 3950.665] (**) Option "xkb_layout" "us,ru"
[ 3950.665] (**) Option "xkb_options" "grp:ctrl_shift_toggle"
[ 3950.665] (II) evdev: Razer Razer Mamba Charging Dock: initialized for relative axes.
[ 3950.665] (WW) evdev: Razer Razer Mamba Charging Dock: ignoring absolute axes.
[ 3950.665] (**) Razer Razer Mamba Charging Dock: (accel) keeping acceleration scheme 1
[ 3950.665] (**) Razer Razer Mamba Charging Dock: (accel) acceleration profile 0
[ 3950.665] (**) Razer Razer Mamba Charging Dock: (accel) acceleration factor: 2.000
[ 3950.665] (**) Razer Razer Mamba Charging Dock: (accel) acceleration threshold: 4
[ 3950.665] (II) config/udev: Adding input device Logitech Unifying Device. Wireless PID:2010 (/dev/input/event5)
[ 3950.665] (**) Logitech Unifying Device. Wireless PID:2010: Applying InputClass "evdev keyboard catchall"
[ 3950.665] (II) Using input driver 'evdev' for 'Logitech Unifying Device. Wireless PID:2010'
[ 3950.665] (**) Logitech Unifying Device. Wireless PID:2010: always reports core events
[ 3950.665] (**) evdev: Logitech Unifying Device. Wireless PID:2010: Device: "/dev/input/event5"
[ 3950.665] (--) evdev: Logitech Unifying Device. Wireless PID:2010: Vendor 0x46d Product 0xc52b
[ 3950.665] (--) evdev: Logitech Unifying Device. Wireless PID:2010: Found 1 mouse buttons
[ 3950.665] (--) evdev: Logitech Unifying Device. Wireless PID:2010: Found scroll wheel(s)
[ 3950.665] (--) evdev: Logitech Unifying Device. Wireless PID:2010: Found relative axes
[ 3950.665] (II) evdev: Logitech Unifying Device. Wireless PID:2010: Forcing relative x/y axes to exist.
[ 3950.665] (--) evdev: Logitech Unifying Device. Wireless PID:2010: Found absolute axes
[ 3950.665] (II) evdev: Logitech Unifying Device. Wireless PID:2010: Forcing absolute x/y axes to exist.
[ 3950.665] (--) evdev: Logitech Unifying Device. Wireless PID:2010: Found keys
[ 3950.665] (II) evdev: Logitech Unifying Device. Wireless PID:2010: Configuring as mouse
[ 3950.665] (II) evdev: Logitech Unifying Device. Wireless PID:2010: Configuring as keyboard
[ 3950.665] (II) evdev: Logitech Unifying Device. Wireless PID:2010: Adding scrollwheel support
[ 3950.665] (**) evdev: Logitech Unifying Device. Wireless PID:2010: YAxisMapping: buttons 4 and 5
[ 3950.665] (**) evdev: Logitech Unifying Device. Wireless PID:2010: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 3950.665] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.6/3-1.6:1.2/0003:046D:C52B.0005/input/input5/event5"
[ 3950.665] (II) XINPUT: Adding extended input device "Logitech Unifying Device. Wireless PID:2010" (type: KEYBOARD, id 11)
[ 3950.665] (**) Option "xkb_rules" "evdev"
[ 3950.665] (**) Option "xkb_model" "evdev"
[ 3950.665] (**) Option "xkb_layout" "us,ru"
[ 3950.666] (**) Option "xkb_options" "grp:ctrl_shift_toggle"
[ 3950.666] (II) evdev: Logitech Unifying Device. Wireless PID:2010: initialized for relative axes.
[ 3950.666] (WW) evdev: Logitech Unifying Device. Wireless PID:2010: ignoring absolute axes.
[ 3950.666] (**) Logitech Unifying Device. Wireless PID:2010: (accel) keeping acceleration scheme 1
[ 3950.666] (**) Logitech Unifying Device. Wireless PID:2010: (accel) acceleration profile 0
[ 3950.666] (**) Logitech Unifying Device. Wireless PID:2010: (accel) acceleration factor: 2.000
[ 3950.666] (**) Logitech Unifying Device. Wireless PID:2010: (accel) acceleration threshold: 4
[ 3950.666] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event7)
[ 3950.666] (II) No input driver specified, ignoring this device.
[ 3950.666] (II) This device may have been added with another device file.
[ 3950.666] (II) config/udev: Adding input device HDA Intel PCH Rear Mic (/dev/input/event10)
[ 3950.666] (II) No input driver specified, ignoring this device.
[ 3950.666] (II) This device may have been added with another device file.
[ 3950.666] (II) config/udev: Adding input device HDA Intel PCH Front Headphone (/dev/input/event11)
[ 3950.666] (II) No input driver specified, ignoring this device.
[ 3950.666] (II) This device may have been added with another device file.
[ 3950.667] (II) config/udev: Adding input device HDA Intel PCH Line Out (/dev/input/event12)
[ 3950.667] (II) No input driver specified, ignoring this device.
[ 3950.667] (II) This device may have been added with another device file.
[ 3950.667] (II) config/udev: Adding input device HDA Intel PCH Line (/dev/input/event8)
[ 3950.667] (II) No input driver specified, ignoring this device.
[ 3950.667] (II) This device may have been added with another device file.
[ 3950.667] (II) config/udev: Adding input device HDA Intel PCH Front Mic (/dev/input/event9)
[ 3950.667] (II) No input driver specified, ignoring this device.
[ 3950.667] (II) This device may have been added with another device file.
[ 3950.667] (II) config/udev: Adding input device PC Speaker (/dev/input/event2)
[ 3950.667] (II) No input driver specified, ignoring this device.
[ 3950.667] (II) This device may have been added with another device file.
[ 3950.702] (II) NVIDIA(GPU-0): Display (Samsung SMBX2331 (DFP-0)) does not support NVIDIA 3D
[ 3950.702] (II) NVIDIA(GPU-0): Vision stereo.
[ 3950.702] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 3950.702] (**) NVIDIA(0): device Samsung SMBX2331 (DFP-0) (Using EDID frequencies
[ 3950.702] (**) NVIDIA(0): has been enabled on all display devices.)
[ 3950.702] (WW) NVIDIA(GPU-0): The EDID for Samsung SMBX2331 (DFP-0) contradicts itself: mode
[ 3950.702] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[ 3950.702] (WW) NVIDIA(GPU-0): valid HorizSync range (31.000-81.000 kHz) would exclude
[ 3950.702] (WW) NVIDIA(GPU-0): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 3950.702] (WW) NVIDIA(GPU-0): for mode "1920x1080".
[ 3950.703] (WW) NVIDIA(GPU-0): The EDID for Samsung SMBX2331 (DFP-0) contradicts itself: mode
[ 3950.703] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[ 3950.703] (WW) NVIDIA(GPU-0): valid HorizSync range (31.000-81.000 kHz) would exclude
[ 3950.703] (WW) NVIDIA(GPU-0): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 3950.703] (WW) NVIDIA(GPU-0): for mode "1920x1080".
[ 3950.714] (II) NVIDIA(GPU-0): Display (Samsung SMBX2331 (DFP-3)) does not support NVIDIA 3D
[ 3950.714] (II) NVIDIA(GPU-0): Vision stereo.
[ 3950.714] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 3950.714] (**) NVIDIA(0): device Samsung SMBX2331 (DFP-3) (Using EDID frequencies
[ 3950.714] (**) NVIDIA(0): has been enabled on all display devices.)
[ 3950.714] (WW) NVIDIA(GPU-0): The EDID for Samsung SMBX2331 (DFP-3) contradicts itself: mode
[ 3950.714] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[ 3950.714] (WW) NVIDIA(GPU-0): valid HorizSync range (31.000-81.000 kHz) would exclude
[ 3950.714] (WW) NVIDIA(GPU-0): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 3950.714] (WW) NVIDIA(GPU-0): for mode "1920x1080".
[ 3950.714] (WW) NVIDIA(GPU-0): The EDID for Samsung SMBX2331 (DFP-3) contradicts itself: mode
[ 3950.714] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[ 3950.714] (WW) NVIDIA(GPU-0): valid HorizSync range (31.000-81.000 kHz) would exclude
[ 3950.714] (WW) NVIDIA(GPU-0): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 3950.714] (WW) NVIDIA(GPU-0): for mode "1920x1080".
[ 3951.033] (II) NVIDIA(GPU-0): Display (Samsung SMBX2331 (DFP-0)) does not support NVIDIA 3D
[ 3951.033] (II) NVIDIA(GPU-0): Vision stereo.
[ 3951.033] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 3951.033] (**) NVIDIA(0): device Samsung SMBX2331 (DFP-0) (Using EDID frequencies
[ 3951.033] (**) NVIDIA(0): has been enabled on all display devices.)
[ 3951.033] (WW) NVIDIA(GPU-0): The EDID for Samsung SMBX2331 (DFP-0) contradicts itself: mode
[ 3951.033] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[ 3951.033] (WW) NVIDIA(GPU-0): valid HorizSync range (31.000-81.000 kHz) would exclude
[ 3951.033] (WW) NVIDIA(GPU-0): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 3951.033] (WW) NVIDIA(GPU-0): for mode "1920x1080".
[ 3951.034] (WW) NVIDIA(GPU-0): The EDID for Samsung SMBX2331 (DFP-0) contradicts itself: mode
[ 3951.034] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[ 3951.034] (WW) NVIDIA(GPU-0): valid HorizSync range (31.000-81.000 kHz) would exclude
[ 3951.034] (WW) NVIDIA(GPU-0): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 3951.034] (WW) NVIDIA(GPU-0): for mode "1920x1080".
[ 3951.044] (II) NVIDIA(GPU-0): Display (Samsung SMBX2331 (DFP-3)) does not support NVIDIA 3D
[ 3951.044] (II) NVIDIA(GPU-0): Vision stereo.
[ 3951.044] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 3951.044] (**) NVIDIA(0): device Samsung SMBX2331 (DFP-3) (Using EDID frequencies
[ 3951.044] (**) NVIDIA(0): has been enabled on all display devices.)
[ 3951.044] (WW) NVIDIA(GPU-0): The EDID for Samsung SMBX2331 (DFP-3) contradicts itself: mode
[ 3951.044] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[ 3951.044] (WW) NVIDIA(GPU-0): valid HorizSync range (31.000-81.000 kHz) would exclude
[ 3951.044] (WW) NVIDIA(GPU-0): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 3951.044] (WW) NVIDIA(GPU-0): for mode "1920x1080".
[ 3951.045] (WW) NVIDIA(GPU-0): The EDID for Samsung SMBX2331 (DFP-3) contradicts itself: mode
[ 3951.045] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[ 3951.045] (WW) NVIDIA(GPU-0): valid HorizSync range (31.000-81.000 kHz) would exclude
[ 3951.045] (WW) NVIDIA(GPU-0): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 3951.045] (WW) NVIDIA(GPU-0): for mode "1920x1080".
[ 3961.685] (II) NVIDIA(GPU-0): Display (Samsung SMBX2331 (DFP-0)) does not support NVIDIA 3D
[ 3961.685] (II) NVIDIA(GPU-0): Vision stereo.
[ 3961.685] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 3961.685] (**) NVIDIA(0): device Samsung SMBX2331 (DFP-0) (Using EDID frequencies
[ 3961.685] (**) NVIDIA(0): has been enabled on all display devices.)
[ 3961.686] (WW) NVIDIA(GPU-0): The EDID for Samsung SMBX2331 (DFP-0) contradicts itself: mode
[ 3961.686] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[ 3961.686] (WW) NVIDIA(GPU-0): valid HorizSync range (31.000-81.000 kHz) would exclude
[ 3961.686] (WW) NVIDIA(GPU-0): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 3961.686] (WW) NVIDIA(GPU-0): for mode "1920x1080".
[ 3961.686] (WW) NVIDIA(GPU-0): The EDID for Samsung SMBX2331 (DFP-0) contradicts itself: mode
[ 3961.686] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[ 3961.686] (WW) NVIDIA(GPU-0): valid HorizSync range (31.000-81.000 kHz) would exclude
[ 3961.686] (WW) NVIDIA(GPU-0): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 3961.686] (WW) NVIDIA(GPU-0): for mode "1920x1080".
[ 3961.697] (II) NVIDIA(GPU-0): Display (Samsung SMBX2331 (DFP-3)) does not support NVIDIA 3D
[ 3961.697] (II) NVIDIA(GPU-0): Vision stereo.
[ 3961.697] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 3961.697] (**) NVIDIA(0): device Samsung SMBX2331 (DFP-3) (Using EDID frequencies
[ 3961.697] (**) NVIDIA(0): has been enabled on all display devices.)
[ 3961.697] (WW) NVIDIA(GPU-0): The EDID for Samsung SMBX2331 (DFP-3) contradicts itself: mode
[ 3961.697] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[ 3961.697] (WW) NVIDIA(GPU-0): valid HorizSync range (31.000-81.000 kHz) would exclude
[ 3961.697] (WW) NVIDIA(GPU-0): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 3961.697] (WW) NVIDIA(GPU-0): for mode "1920x1080".
[ 3961.697] (WW) NVIDIA(GPU-0): The EDID for Samsung SMBX2331 (DFP-3) contradicts itself: mode
[ 3961.697] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[ 3961.697] (WW) NVIDIA(GPU-0): valid HorizSync range (31.000-81.000 kHz) would exclude
[ 3961.697] (WW) NVIDIA(GPU-0): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 3961.697] (WW) NVIDIA(GPU-0): for mode "1920x1080".
[ 3963.080] (II) NVIDIA(GPU-0): Display (Samsung SMBX2331 (DFP-0)) does not support NVIDIA 3D
[ 3963.080] (II) NVIDIA(GPU-0): Vision stereo.
[ 3963.080] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 3963.080] (**) NVIDIA(0): device Samsung SMBX2331 (DFP-0) (Using EDID frequencies
[ 3963.080] (**) NVIDIA(0): has been enabled on all display devices.)
[ 3963.080] (WW) NVIDIA(GPU-0): The EDID for Samsung SMBX2331 (DFP-0) contradicts itself: mode
[ 3963.080] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[ 3963.080] (WW) NVIDIA(GPU-0): valid HorizSync range (31.000-81.000 kHz) would exclude
[ 3963.080] (WW) NVIDIA(GPU-0): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 3963.080] (WW) NVIDIA(GPU-0): for mode "1920x1080".
[ 3963.081] (WW) NVIDIA(GPU-0): The EDID for Samsung SMBX2331 (DFP-0) contradicts itself: mode
[ 3963.081] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[ 3963.081] (WW) NVIDIA(GPU-0): valid HorizSync range (31.000-81.000 kHz) would exclude
[ 3963.081] (WW) NVIDIA(GPU-0): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 3963.081] (WW) NVIDIA(GPU-0): for mode "1920x1080".
[ 3963.091] (II) NVIDIA(GPU-0): Display (Samsung SMBX2331 (DFP-3)) does not support NVIDIA 3D
[ 3963.091] (II) NVIDIA(GPU-0): Vision stereo.
[ 3963.091] (**) NVIDIA(0): Using HorizSync/VertRefresh ranges from the EDID for display
[ 3963.091] (**) NVIDIA(0): device Samsung SMBX2331 (DFP-3) (Using EDID frequencies
[ 3963.091] (**) NVIDIA(0): has been enabled on all display devices.)
[ 3963.091] (WW) NVIDIA(GPU-0): The EDID for Samsung SMBX2331 (DFP-3) contradicts itself: mode
[ 3963.091] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[ 3963.091] (WW) NVIDIA(GPU-0): valid HorizSync range (31.000-81.000 kHz) would exclude
[ 3963.091] (WW) NVIDIA(GPU-0): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 3963.091] (WW) NVIDIA(GPU-0): for mode "1920x1080".
[ 3963.092] (WW) NVIDIA(GPU-0): The EDID for Samsung SMBX2331 (DFP-3) contradicts itself: mode
[ 3963.092] (WW) NVIDIA(GPU-0): "1920x1080" is specified in the EDID; however, the EDID's
[ 3963.092] (WW) NVIDIA(GPU-0): valid HorizSync range (31.000-81.000 kHz) would exclude
[ 3963.092] (WW) NVIDIA(GPU-0): this mode's HorizSync (28.1 kHz); ignoring HorizSync check
[ 3963.092] (WW) NVIDIA(GPU-0): for mode "1920x1080".
Output of setxkbmap -print -verbose 10
Setting verbose level to 10
locale is C
Trying to load rules file ./rules/evdev...
Trying to load rules file /usr/share/X11/xkb/rules/evdev...
Success.
Applied rules from evdev:
rules: evdev
model: evdev
layout: us,ru
variant: ,
Trying to build keymap using the following components:
keycodes: evdev+aliases(qwerty)
types: complete
compat: complete
symbols: pc+us+ru:2+inet(evdev)
geometry: pc(pc104)
xkb_keymap {
xkb_keycodes { include "evdev+aliases(qwerty)" };
xkb_types { include "complete" };
xkb_compat { include "complete" };
xkb_symbols { include "pc+us+ru:2+inet(evdev)" };
xkb_geometry { include "pc(pc104)" };
But this comand helps:
setxkbmap -layout "us,ru" -option "grp:ctrl_shift_toggle"
New output of setxkbmap -print -verbose 10
Setting verbose level to 10
locale is C
Trying to load rules file ./rules/evdev...
Trying to load rules file /usr/share/X11/xkb/rules/evdev...
Success.
Applied rules from evdev:
rules: evdev
model: evdev
layout: us,ru
options: grp:ctrl_shift_toggle
Trying to build keymap using the following components:
keycodes: evdev+aliases(qwerty)
types: complete
compat: complete
symbols: pc+us+ru:2+inet(evdev)+group(ctrl_shift_toggle)
geometry: pc(pc104)
xkb_keymap {
xkb_keycodes { include "evdev+aliases(qwerty)" };
xkb_types { include "complete" };
xkb_compat { include "complete" };
xkb_symbols { include "pc+us+ru:2+inet(evdev)+group(ctrl_shift_toggle)" };
xkb_geometry { include "pc(pc104)" };
This config is still not changing visualistaion of layout (right top corner of gnome), but triggering is ok
If it helps - keyboard is Logitech K800, desktop - gnome 3
Thanks for attention and sorry for my bad english
UPD: Solved by Gnome settings, not Xorg
Last edited by fu2re (2012-11-12 09:44:01)

I have re-checked the issue and I found that the problem is with JPG file.
I wasn't even aware you could save a path to a jpeg file (always use PSD because of wanting to keep the Alpha Channel, jpeg only can contain 1 layer and no alpha channels and/or transparency).
However I tried it on a file with a simple path and one with a complex path. It seems indeed you have found a bug. The simple path is no problem but the more complex path is indeed disappearing.
It is not only label but also rate or adding IPTC in the description field. The moment metadata is saved to this jpeg file and reopened the earlier present work path of a more complex path is gone.
Despite the fact that to my opinion a jpeg is not the most suitable file format for saving a work path this should not happen. If a work path is saved to a jpeg then it should be kept saved after just altering metadata in Bridge.
It still is the same behavior in Bridge CC because that is what I use. Don't know when it started but it still needs to be repaired
Here is the link for filing a problem or bug:
http://feedback.photoshop.com/photoshop_family/

Problems with AEBS recognising MAC OS Extended USB hard drive

I've just bought the AEBS(n) and connected a hard drive via the usb port. Everything works fine - however when I get info it shows that the format is Appleshare! The hard drive is actually formatted as a MAC OS Extended (journaled) as this is confirmed if I connect the drive directly to my iMac.
Although this may not seem to be a problem as I can read and write to the disk, if I use iMovie it does not recognise the disk and therefore not show my iMovie events, even though there are on the drive and states that i must have a MAC OS extended drive.
I don't know how to ensure that AEBS shows the correct format of the drive so I won't have this problem?
The other thing is that when I use the Aiport Disk Utility it does not show the name of my hard drive in the window, instead the name of the AEBS shows!!??

I think there are a number of problems with the AEBS USB disk support.
- I have a 1 GB flash drive (solid state) that works fine on the AEBS.
- however I also have a 75 GB 2.5 inch Hitachi external USB drive that works fine on all my macs but can not connect to the AEBS. After talking to Apple there seems to be a list of 'supported drives' for AEBS USB drives but I've never seen it and nobody at Apple has it (or at least could send it to me).
- my AEBS has crashed several times when I hook up the Hitachi drive, forcing me to attach the drive to a mac and run disk utility for a disk repair (I guess the AEBS has no disk repair function).
- and it is slooowwww ....
- if you use a USB hub there seems to be a lot more issues -- especially if the hub is USB 1.1 and not USB 2.0.
maybe there will be a firmware update. I know I have filed Radar problems on all these issues....

Problem with changing Label in Bridge CS3 and CS6

Hi there,
I am having some problem with changing Label in Bridge CS3 and CS6 in windows.
1. In Bridge CS3 (Windows XP), most of the time with most of the files, there is no problem. But I found that in some files, the Label does not get changed. I usually change Label by right clicking on the picture, then Label and select any Label. When I do so in those files, nothing happens. But when I rename the file by changing or adding just a single character, then it works. And if I again rename to original name, it still works. But without renaming the Label does not change. Again this does not happen with all pictures, but occationally with some. We usually receive pictures from different clients for editing purpose.
2. In Bridge CS6 (Windows 7), if you create lot of Path using Pen tool in Photoshop for the purpose of removing background, you save the file, close, and change Label in Bridge, again open the file in Photoshop, you see no Path in the Path Pallette. So that means, changing Label works, but it removes the Path from the file. But if there is small amount of path, then no prboblem. But if there is lot of path, like you need to create for a necklace to remove background, then the problem arises.
I am using Bridge for a purpose where it is very helpful so I really need to use Bridge, and Labeling feature is the most important to me, but after feaguring out this problem, I am really tensed as to whether or not I will find a solution to this. So any help, guidance will really be appreciated.
Thanks very much in advance for any solution.
Best regards

I have re-checked the issue and I found that the problem is with JPG file.
I wasn't even aware you could save a path to a jpeg file (always use PSD because of wanting to keep the Alpha Channel, jpeg only can contain 1 layer and no alpha channels and/or transparency).
However I tried it on a file with a simple path and one with a complex path. It seems indeed you have found a bug. The simple path is no problem but the more complex path is indeed disappearing.
It is not only label but also rate or adding IPTC in the description field. The moment metadata is saved to this jpeg file and reopened the earlier present work path of a more complex path is gone.
Despite the fact that to my opinion a jpeg is not the most suitable file format for saving a work path this should not happen. If a work path is saved to a jpeg then it should be kept saved after just altering metadata in Bridge.
It still is the same behavior in Bridge CC because that is what I use. Don't know when it started but it still needs to be repaired
Here is the link for filing a problem or bug:
http://feedback.photoshop.com/photoshop_family/

MacBook shutdown problem

My friends MacBook will not shutdown if he closes the lid. He first tells the computer to shutdown, then if he closes the lid it will keep running till it exhausts the battery. Is there some perferance for this?

I'm not a Genius but in both my jobs I perform some of the same functions of the Genius. (I teach IT and I work part time for an Apple reseller.) My take here on the board is different from lots of peoples' because I can see so many sides of the issue. I've been an angry customer (white spots on my 15" alBook display and 2 dead logic boards on an iBook). I've been the stumped techy who gave the user some canned advice hoping it would work whilst filing the problem away in my "Hope this one gets a definitive answer soon box." And I've been the retailer who seriously suspects the computer user has abused his machine. And I've seen that Apple generally gets it right in the end, even though it sometimes takes longer than I'd like.
I came across this shut down problem here on the discussion group sometime last week through a post where the user complained that his MacBook spontaneously started up while in his bag and he found it burning hot hours later. I didn't post anything because I had nothing constructive to say but to be completely honest about it, my first assumption was user error.
Then suddenly I was reading lots of 'my computer doesn't shut down right' and 'my computer doesn't stay shut down' posts. Now my attention was grabbed and naturally the first thing I did try shutting mine down. No problem. I asked my boss and the head tech (they both bought MacBooks) and both of them could shut down okay. So now I'm no longer thinking it is user error but I'm stumped as to what's going on. Then I read the post that put it all in place. The user indicated that her computer's shutdown was messed up if she shut the lid. Now I had something to test...mine shut down. Darn! But I took that information to the shop with me and Ken was able to reproduce it very reliably on his MacBook. But the boss couldn't at all and I can't reliably. But other than this, Ken's computer is fine and so is mine.
So from my point of view we have to give the Genius the benefit of the doubt. I was a believer last week - I was certain a problem existed but I didn't know what was going on. By the end of the week I knew how it could be caused and was pretty certain I'd found two reliable work arounds. But we don't have any clue as to the root cause. As of Monday there was no word from Apple on the matter. The fastest I've ever gotten a repair box from Apple is 2 business days and with the holiday l-o-n-g weekend I wouldn't get antsy until Thursday.
Are you right to be upset? Heck yes, you paid some serious money expecting to get a good computer. But it is a complex piece of equipment and no matter how hard and reliably you test issues turn up once it reaches the consumer. If we had no reliable work around I'd be upset but at present I put this issue in the annoying but can live with it for now box. Now if I had a MacBook that mooed it would be an entire different herd of cattle!

Slideshow focus problem lightroom 6/CC

I updated to lightroom 6/CC yesterday and started using slideshow function today and was horrified when the first 10 images all seemed out of focus, I went to the develop mode and they are all sharp, so it seems that slideshow is the issue. Anyone know how to fix this?

In Lightroom 6/CC, there is a new "Quality" setting for slideshows, at the very bottom of the "Playback" section of the settings (at the bottom of the right-hand sidebar in the Slideshow module). It has three settings: low / standard / high .
The new setting defaults to "Standard," which on a decent resolution monitor results in blurriness. The "High" setting is equivalent to how Lightroom 5 used to display slideshows.
So, try changing it to "High" and see if that fixes the problem for you.
Unfortunately, for me, the Slideshow Quality setting resets to "Standard" every time I quit Lightroom 6.0, when I want it to stay on "High." Very annoying.
I filed a problem report about it here:
Lightroom 6: Quality setting not remembered after quitting and relaunching
--Scott

"Load files into Photoshop layers" fails to complete CS6

Hi all,
Hoping someone can help with the folling problem with Photoshop & Bridge CS6
When in Bridge, after selecting 6 images (CR2) using the command TOOLS>LOAD FILES INTO PHOTOSHOP LAYERS the first file will load into Photoshop, Photoshop will then generate a second blank layer and then read the second file. At this point the "script" will stop. I am left with a document with 2 layers. The top layer has my first image, the bottom layer is empty.
At this point when I quit Photoshop I am prompted to save this open document which appears to be the only open document. I choose not to save this as a file. I then get a dialogue box prompting to save another open document. Photoshop has loaded the second file to place as a layer but as the "script" has aborted I am left with an open, but invisible file.
When I first loaded CS6 on Snow Leopard, it would demonstrate this behaviour every time I attempted to run this command from Bridge.
I did a clean install on a blank HDD of OSX Lion. Installed CS6. The command worked without fail for about a month.
Then I would get the command aborting occasionally. Restarting Photoshop would let me continue for a few hours before this aborted script problem would happen again.
Over the last week it has become more frequent, to a point where this workflow is unusable.
A restart of Photoshop may fix the problem for the next batch of images, only to fail again soon after, or fail on the first attempt after a relaunch of Photoshop.
A reboot of my computer will allow my to load one or two sets of files before again failing to complete the command.
I have tried the following:
In Photoshop preferences:
disabling the "Use graphics Processor"
Increasing or decreasing the amount of RAM available to Photoshop
Changing the cache levels or changing the cache tile size
changing the scratch disk
Trashing the Photoshop preferences file (Photoshop Settings.psp)
In Bridge
Purging the cache
Increasing or decreasing the cache size
Resetting Bridge preferences (holding Command on launch) and deleting all cache files.
In general system
Quitting extra programs (Safari, Thunderbird, iTunes)
Sometimes this will seem to then allow Photoshop to load a full set of images, only to abort again after a few sets.
Rebooting the computer - again will work for a few images sets before again failing.
Now the fact that it worked fine for several weeks without presenting a problem would indicate that it is not a bug.
The fact that is slowly started happening then became more frequent would indicate something changing slowly over time - a larger cache folder perhaps, although purging known Bridge cache folders has not filed the problem.
Really at the end of my tether here. Even considering downgrading to CS5 - but don't want to have to use the older Adobe Camera Raw.
System is as follows:
Mac Pro 2 x 2.66 Quad Core
24GB RAM
ATI Radeon HD 4870 512
OSX Lion 10.7.4
I have seen a couple of others have posted having a the same problem, both with CS5 and CS6.
Hoping someone has an answer.
Thanks.

Hi JJMack - I just re-read your post. For some reason I thought you were suggesting to make sure "Open documents in Tabs" was selected, it was. Now I realize you were suggesting to turn it off! As another attemp to solve this problem I did de-select it today. Seemed to work for a good while. I was getting very excited, then, on the last set of images I had to do it displayed the same problem. But, it did go for quite a while without failing, and when it did I was thrashing about trying to make another app active. When loading documents like this - with "Open documents in Tabs" de-selected, Photoshop wants to put the loading images as the front-most window, no matter what other apps (Bridge, email, web etc) I click on in the dock. I think it is related to the bug you described effecting the "load files to stack" command.
Hopefully Adobe is looking at this - mind you, I have read reports of people having this problem in CS5! Looks like that was never resolved sadly.
I'll keep testing and post back.
I am looking to upgrade my video card to see if it's a video memory thing.
What is very weird though is the fact that this problem didn't present itself until after several weeks of working with this command with no problem. No additional apps installed, nothing changed. Why would it start happening only after a while?
Thanks again for your suggestion.

Attaching files as Attachments, not INLINE attachments

I'm sending images to a client who's on Lotus Notes (7.02). We have discovered an issue with inline attachments in Lotus, where attachments can only be drag and dropped out of Lotus if the attachment was NOT sent as an inline attachment.
This was tested in Thunderbird by changing the mail.contentdispositiontype preference as per this article:
http://kb.mozillazine.org/Sendattachments_as_realattachments
In any event, the client is not able to switch from Lotus to OS X mail or any other client– as this is a large organization.
The issue is easily fixed on my end by using Thunderbird– but that's not the path that I'd like to take–I'd like to know how to address this in OS X Mail.
I've already clicked on windows friendly, send at end of message, and tried right clicking and setting the attachment to 'show as icon'– all in an attempt to get OS X Mail to send 'real' attachments, as opposed to inline.
Does anyone know of a .plist file, or a hidden preference that can be enabled to address this?
Thanks!

exactly the same with on of my clients (Lotus, blocker, large org...). I have filed an problem case on this.
http://www.ietf.org/rfc/rfc2183.txt
http://www.iana.org/assignments/mail-cont-disp
My understanding is Apple Mail has no outgoing option (GUI) to set the "Mail Content Disposition Value" to "attachment" (RFC2183 2.2) to have an "user controlled display" as opposed to "inline" (RFC2183 2.1) and "displayed automatically" on the side of the recipient.
In short the Summary (RFC2183 4.):
+"Content-Disposition takes one of two values, `inline' and `attachment'. `Inline' indicates that the entity should be immediately displayed to the user, whereas `attachment' means that the user should take additional action to view the entity."+
I also suggest we should also have a preference for incoming mail to not display content at all as "inline" regardless of the Content-Disposition Value if we want to.
Btw. I am also missing the option (MDN) to request a notification that a message is delivered/read.
http://www.ietf.org/rfc/rfc3798.txt

Conf of production order

Hi guyes,
I am trying confirmation of production order (co15) but at the time of saving the order i get error message that" field selection for movmt type 261/acct 790000 differ for cost center(010), i have ckecked g/l account also all are perfect so plz let me know where i am wrong? final product is in batch.
Regards,
jaiswin.

Hi
It seems some filed selection problem related to the movement type 261 and the G/L account combination.
Go to SE38 - in the Program field write RM07CUFA-- Execute--Enter the movement type company code and G/L account-Execute-Additional Account assignments G001- Cost center
There cost center should be optional entry.. please check the fields there.
Regards
Bala

Suggestion: add the option "auto restore last session on program start"

I know about "reopen all the windows from the last session" in the History menu. I would like to have the option of automatic reopen.
And would be more convenient to swap buttons "Add to favorites" and "Refresh page" (screenshot: http://img198.imageshack.us/i/clip6s.jpg/)

And a few Apple employees from time to time
I filed <rdar://problem/6985427>, feel free to reference this number if you want to file a separate bug on bugreport.apple.com

[Solved] File "Save As" takes more than 20s before dialogue box opens

Whenever I use File "Save As" in any non-kde application (eg firefox, medit, kino), the dialogue box opens immediately but then takes more than 20 seconds to display the contents of the initial directory, after which I can then save the file. Alternative directories can then be selected instantly without problem. Starting File Save As again, causes the same long delay, so its not a caching issue. This occurs in XFCE4, LXDE & KDE.
KDE apps, however, list the contents virtually immediately, indicating that its not a disk or filing system problem.
The XFCE4 theme (under Appearance > Style) is Foresight, and the icon theme is Nuvola. Changing these does not make any apparent difference.
This is on a SATA drive with 84 GB free running Arch 64.
Can anyone suggest how this can be rectified?
Last edited by Cotton (2010-01-01 19:19:12)

Many thanks for that - problem solved.
The file contained 323 lines pointing to a single directory with multiple subdirectories, none of which was a removable device.
Moving the file to another location, resulted in the File Save As operation functioning properly.
Not sure if I actually use gtk-bookmarks as it hadn't been modified in over 6 months.
Anyway, thanks again - its made a big difference.

Error 2330 on Itunes 8 install on vista log attatched... I need some help

I can't tell if this is quicktime or itunes, but I really could use some help here. I think I have spent 10 hours trying various fixes on this. Does anyone know of a fix?
these are some of the errors in the log
MSI (c) (18:00) [16:20:51:016]: PROPERTY CHANGE: Modifying IAcceptLicense property. Its current value is 'No'. Its new value: 'Yes'.
DEBUG: Error 2826: Control LangCombo on dialog DestinationOptions extends beyond the boundaries of the dialog on the bottom by 7 pixels
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2826. The arguments are: DestinationOptions, LangCombo, on the bottom
Action 16:20:51: DestinationOptions. Dialog created
DEBUG: Error 2330: Error getting file attributes: C:\Program Files\Java\jre6\lib\ext. GetLastError: 1392
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2330.
MSI (c) (18!38) [16:21:52:446]: Product: iTunes -- The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2330.
DEBUG: Error 2769: Custom Action InstallPackages did not close 2 MSIHANDLEs.
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2769. The arguments are: InstallPackages, 2,
Action ended 16:22:11: InstallPackages. Return value 3
Action start 16:22:11: SetupCompleteError.
DEBUG: Error 2836: The control Back on the dialog SetupCompleteError can not take focus
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2836. The arguments are: SetupCompleteError, Back,
Action 16:22:11: SetupCompleteError. Dialog created
Action ended 16:22:13: SetupCompleteError. Return value 2.
Action ended 16:22:13: INSTALL. Return value 3.
MSI (c) (18:10) [16:22:13:141]: Destroying RemoteAPI object.
MSI (c) (18:20) [16:22:13:141]: Custom Action Manager thread ending.
Property(C): UpgradeCode = {0880A3FD-2A1E-43C5-B020-09930E075D34}
Property(C): EXISTINGIPODINSTALLDIR = C:\Program Files\iPod\
Property(C): AUTORUN = #1
Property(C): PROGRAMMENUNAME = iTunes\

I can't make sense of all that, there seem to be several things going on.
What error to you get from the installer itself rather than the event viewer?
In general, 2330 errors can be due to filing system problems so, a good start would be to run a disk check.
Then try again if it finds errors.
If it still doesn't work try the general install troubleshooting in this article:
http://support.apple.com/kb/TS1717
It would help if you say what you have tried and what the results were if you have been working on this for some time.

No sound when iTunes continues to play

06-May-2007 08:07 AM Erin Dalzell:
I have a Summer 2001 iMac with 768M of RAM running OSX 10.4.9 with all the updates applied. I have an Airport Express with FW 6.3 (the latest).
When I play the music through two outputs (local iMac speakers and APX attached speakers), no sound is heard occasionally.
It happens when moving from one song to another. iTunes is still playing when this happens, just no sound is heard out of either set of speakers.
To resolve it, I can pause the music, then start it again. But it will stop laster when changing songs again.
If I only play music through one output (either local speaker OR APX), then this problem doesn't occur.
It also doesn't occur on my MacBook when remotely access the iMac's iTunes library.
I have filed rdar://problem/5184218 for this issue, but I thought I would check this forum for ideas as well.

I'm having the same identical problem. Thanks for describing it! The only thing that I is different for me is that it will happen when only 1 set of speakers is checked on. Has anyone been able to help you figure this out? What strange about this is the randomness in which it occurs.
MacPro 2.66 GHz dual Mac OS X (10.4.9)

No Response from Adobe Case #180841426.

I had filed the problem to technical support about activation problem since March 29. I cannot activate my account, so I am unable to open my e-book. It kept saying:
E_ACT_TOO_MANY_ACTIVATIONS
http://adeactivate.adobe.com/adept/Activate 121:6121:6121
urn:uuid:4fc133e0-75bc-4f03-8762-59ef4415d9c8#
I really need to use the book. I got the response 1 day later. I was impressed by quick response from technical support.
HOWEVER, when I replied back to them, they have not contacted me back. I frequently check the status of my case and it still states that pending for Adobe Response.
I am really disappointed about this. What should I do? Any problem faced the same problem. Please let me know what to do.
Thanks

I just did a double check, and you should be able to activate.
Jim Lester
Adobe Systems

E-Filing GB : problem

Similar Messages

Maybe you are looking for