Documentation on client switches from Informatica to ODI?

Hi,
Any documentation out there that describes the process of how to upgrade from an existing Informatica ETL to ODI ETL in BI Apps? (A client already has BI apps implemented and wants to switch from informatica to ODI.)
Thanks

Right now, there is only one BI Apps version which utilizes ODI: 7.9.5.2.
This version is constrained to Oracle EBS sources and contains none of the Siebel mappings for example. There isn't anything official yet (path, process, documentation, tools, etc...) for moving from Informatica to ODI.
Cheers,
C.

Similar Messages

Outlook Email Client Switch from Mac to Windows

Switching from outlook windows to outlook for mac seems quite an easy task but the vide versa is not the same.
I have downloaded email files in outlook for mac that I need to import to outlook for windows.
The main issue is that I have deleted all the mails from the server and have saved emails in outlook 2011. Now uploaing these emails is taking ages and I am running out of time.
How can I transfer all these files from outlook 2011 for mac to outlook 2013 for windows???
helpful answers will be really appreciated

Hi,
Generally, we can export the mailbox data to an Outlook for Mac Date file(.olm file) in Outlook 2011 for Mac. As for Outlook for Windows, the default Outlook Data file is .PST file. If so, we need to find some third-party tools to convert OLM file to PST
file for Windows Outlook using.
Personal suggestion, we can consider to create a new imap account acted as a transfer mailbox. To do it, please follow:
1. Create a new IMAP account, such as a Hotmail.com account.
2. Configure the Hotmail account in your Outlook 2011 for Mac and import the exported OLM file to this account.
3. The imported data file will synced to IMAP account in mail server. We can login to the Web mail page to double check it.
4. If the data has been synced complete in Hotmail mail server, we can configure this Hotmail account in your Outlook for Windows. Then all mailbox data can be download to the local Outlook in Windows machine.
5. Now, we can drag the messages from this Hotmail account to your main account. Or we can export Hotmail mailbox to PST file for other Windows Outlook using.
Additionally, here is a similar thread about your issue:
http://social.technet.microsoft.com/Forums/en-US/03082e4b-70de-4faa-a02c-77eb52d8781c/convert-olm-to-pst
Hope it helps.
Regards,
Winnie Liang
TechNet Community Support

Old clients won't switch from Self-Signed Certs to PKI.

Greetings.
I am wondering if anyone can give me advise on problem I am having with some of my sccm clients.
When I originally deployed SCCM i used self signed certs on clients.
We needed to add MAC and Linux support and MAC clients won't work without PKI, so I following this http://technet.microsoft.com/en-us/library/gg682023.aspx to configure Certificate Authority.
It all seemed work well, I can now join MAC client with auto-enroll and all machines are requesting client certificates and I had couple of machine with new push on windows site installed with PKI.
So right now I have about 250 windows clients, only 22 of them use PKI and the rest keeps using self-signed certs.
I foolishly switched main site settings, MP settings and DP point settings to use https only.
As a result I lost all self-signed clients and have full log for mpcontrol saying that it's rejecting clients cause they certificate cannot be validated.
I logged in to couple of those machines and MMC i can see that it did enroll machine with valid Client Cert but Configuration Manager client itself still saying that it's using self signed one.
Am I missing a step that I need to do to make sure that all those clients switch to PKI?

It is. but how can i redeploy them?
I was under impression auto push won't reinstall them. If i do deployment - that seem to reuse existing configuration and still use self signed on old machines.
How can i verify that it does push clients to machine that already have it correctly and start using new config and not reuse old one.
I even tried removing clients from couple of machines and see if it gets pushed again on them with proper config and those machines don't seem to get client but used to get it fine before. I keep getting new machines being added to domain and they get client
pushed to them, but anything that had client with self signed doesn't seem to be happy.

How to switch from "Disconnected" to "Online" in Client Version?

I'm using UPK 3.6.1 Client version. Sometimes I launch UPK when I'm not on the corporate network, I am "Disconnected" (the status appears at the bottom right corner). Then, I'd realize I need to check out a document and I would get on the VPN, but I can never figure out how to switch to "Online" without shutting down UPK and relaunching it.
Is there a way to switch from "Disconnected" to "Online" without having to shut down UPK?
Thanks.

Hello,
When I VPN back in and it still reads disconnected, typically mine goes online automatically after a few seconds. However, when it doesn-t I either double click the icon in the bottom right where it states disconnected or I go offline by going to the File, work offline entry and immediately uncheck it again. Have you tried that? Going from disconnected to offline to then hopefully online.
Sorry nothing more helpful. Good Luck!

Move a switch from VTP client mode to VTP transparent mode

Hi,
Does anybody have an experience / knowledge if I move a switch from VTP client mode to VTP transparent mode, should I re-create all the VLANs on this switch?
Thank you!

Hi there,
The VTP and the VLANs are seperate beasts.
The switch has a vlan database which is held in a seperate file to the config. If you type "sh flash" you'll see it in there.
VTP passes around the VLAN information and the switch stores it in the vlan database. If you remove the switch from the VTP domain, then VTP will not be able to update this file and it will remain exactly as it was.
In short - if you've got 20 vlans, when you go to VTP transparent, you'll still have 20 vlans
Regards,
LH
Please rate all posts

I just switched from a PC and am installing googlemail on my macbook. it has successfully connected my calendar and contacts. But my mail is not linking. i get a unable to connect to the server message. any ideas wise ones pls

i have just switched from a PC and installing my googlemail account onto my Macbook pro. I can successfully see my calendar and contacts but my mail will not connect. i get an error message - can not connect to the server. Any ideas please?

Neil,
I don't use Apple's Mail client (I use MS Outlook) but setting up your Gmail account should be fairly straightforward. Just make certain that you have your settings correct.
For your incoming server, be sure to use the "map.gmail.com" server, using SSL, using port "993" (usually the default).
For your outgoing server, be sure to use the "smtp.gmail.com" server, override the default port and use port "465" and use SSL to connect and make sure that you enter your email address and password to access the SMTP server.
If you've already set up your account with these settings, you may need to Google "gmail setup apple mail" and find the Google document relating to same.
Good luck,
Clinton
MacBook Pro (15” Late 2011), OS X Yosemite 10.10, 16GB Crucial RAM, 960GB M500 Crucial SSD, 27” Apple Thunderbolt Display

Trying to switch from nvidia to nouveau; startx freezes system

I'm having high cpu issues, possibly related to nvidia and want to switch to nouveau to test this out. I followed the Arch Wiki for nouveau but am having issues being able to startx. My process:
- Logout of openbox
- Remove nvidia stuff:
# pacman -Rsc nvidia nvidia-utils opencl-nvidia
# pacman -S xf86-video-nouveau
Installing nouveau also prompted the removal of nvidia-libgl and replaced it with mesa-libgl, as well as the installation of nouvea-dri.
- Removed my existing monitor config file:
# mv /etc/X11/xorg.conf.d/10-monitor.conf /etc/X11/xorg.conf.d/10-monitor.conf.bk
- Verified that I have no modeset options specified to kernel options via syslinux, nor blacklisting of nouveau in /etc/modprobe.d/ files.
$ cat /etc/modprobe.d/modprobe.conf
# /etc/modprobe.d/modprobe.conf
blacklist uvcvideo
blacklist pcspkr
$ ls /etc/X11/xorg.conf.d/
10-evdev.conf 10-monitor.conf.bk 10-quirks.conf 50-synaptics.conf
Nothing related to monitors or screens in 10-evdev, 10-quirks or 50-synaptics, and the 10-monitor.conf.bk file has the following contents (just in the event it *is* picked up by Xorg):
$ cat /etc/X11/xorg.conf.d/10-monitor.conf.bk
Section "Monitor"
Identifier "Monitor0"
ModelName "LGD"
HorizSync 28.0 - 33.0
VertRefresh 43.0 - 72.0
Option "DPMS"
# Option "Enable" "True"
# Option "PreferredMode" "1600x900"
EndSection
Section "Device"
Identifier "Device0"
Driver "nouveau"
# Driver "nvidia"
VendorName "NVIDIA Corporation"
BoardName "Quadro FX 1800M"
BusID "PCI:1:0:0"
EndSection
Section "Screen"
Identifier "Screen0"
Device "Device0"
Monitor "Monitor0"
DefaultDepth 24
SubSection "Display"
Depth 24
Modes "1600x900"
EndSubSection
# Option "SLI" "Auto"
# Option "AddARGBGLXVisuals" "True"
EndSection
- Reboot
I am at work and have my computer docked. Nouveau seemed to be active, observed by the fact that it auto-switched to KMS during boot. It also picked up my external monitor, which was off, and started duplicating the display on my external monitor and laptop during text boot (which nvidia does not do). The laptop had what I'll call "screen artifacts" on the lower right (white lines, jumbled pixels) after switching to KMS, but not a huge deal. I went to startx and it just froze after spitting out the various initialization lines. I have to hard kill and reboot. From there, I uninstall nouveau, re-install nvidia (which replaces mesa-libgl with nvidia-libgl), and reboot again to a working system.
Any suggestions?
Last edited by jwhendy (2013-10-24 16:36:15)

Here's the recent Xorg.log:
X.Org X Server 1.14.3
Release Date: 2013-09-12
[ 102.581] X Protocol Version 11, Revision 0
[ 102.581] Build Operating System: Linux 3.11.1-1-ARCH x86_64
[ 102.581] Current Operating System: Linux bigBang 3.11.6-1-ARCH #1 SMP PREEMPT Fri Oct 18 23:22:36 CEST 2013 x86_64
[ 102.581] Kernel command line: root=/dev/mapper/root cryptdevice=/dev/sda3:root ro initrd=../initramfs-linux.img BOOT_IMAGE=../vmlinuz-linux
[ 102.581] Build Date: 08 October 2013 08:48:10PM
[ 102.581]
[ 102.581] Current version of pixman: 0.30.2
[ 102.581] Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[ 102.581] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 102.582] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Oct 24 19:46:30 2013
[ 102.599] (==) Using config directory: "/etc/X11/xorg.conf.d"
[ 102.618] (==) No Layout section. Using the first Screen section.
[ 102.618] (==) No screen section available. Using defaults.
[ 102.618] (**) |-->Screen "Default Screen Section" (0)
[ 102.618] (**) | |-->Monitor "<default monitor>"
[ 102.618] (==) No monitor specified for screen "Default Screen Section".
Using a default monitor configuration.
[ 102.618] (==) Automatically adding devices
[ 102.618] (==) Automatically enabling devices
[ 102.618] (==) Automatically adding GPU devices
[ 102.666] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/100dpi/".
[ 102.666] Entry deleted from font path.
[ 102.666] (Run 'mkfontdir' on "/usr/share/fonts/100dpi/").
[ 102.667] (WW) `fonts.dir' not found (or not valid) in "/usr/share/fonts/75dpi/".
[ 102.667] Entry deleted from font path.
[ 102.667] (Run 'mkfontdir' on "/usr/share/fonts/75dpi/").
[ 102.667] (==) FontPath set to:
/usr/share/fonts/misc/,
/usr/share/fonts/TTF/,
/usr/share/fonts/OTF/,
/usr/share/fonts/Type1/
[ 102.667] (==) ModulePath set to "/usr/lib/xorg/modules"
[ 102.667] (II) The server relies on udev to provide the list of input devices.
If no devices become available, reconfigure udev or disable AutoAddDevices.
[ 102.667] (II) Loader magic: 0x7fdc20
[ 102.667] (II) Module ABI versions:
[ 102.667] X.Org ANSI C Emulation: 0.4
[ 102.667] X.Org Video Driver: 14.1
[ 102.667] X.Org XInput driver : 19.1
[ 102.667] X.Org Server Extension : 7.0
[ 102.667] (II) xfree86: Adding drm device (/dev/dri/card0)
[ 102.671] (--) PCI:*(0:1:0:0) 10de:0cbc:103c:1521 rev 162, Mem @ 0xd2000000/16777216, 0xc0000000/268435456, 0xd0000000/33554432, I/O @ 0x00005000/128, BIOS @ 0x????????/524288
[ 102.671] Initializing built-in extension Generic Event Extension
[ 102.672] Initializing built-in extension SHAPE
[ 102.672] Initializing built-in extension MIT-SHM
[ 102.672] Initializing built-in extension XInputExtension
[ 102.672] Initializing built-in extension XTEST
[ 102.672] Initializing built-in extension BIG-REQUESTS
[ 102.672] Initializing built-in extension SYNC
[ 102.672] Initializing built-in extension XKEYBOARD
[ 102.673] Initializing built-in extension XC-MISC
[ 102.674] Initializing built-in extension SECURITY
[ 102.675] Initializing built-in extension XINERAMA
[ 102.676] Initializing built-in extension XFIXES
[ 102.677] Initializing built-in extension RENDER
[ 102.678] Initializing built-in extension RANDR
[ 102.679] Initializing built-in extension COMPOSITE
[ 102.680] Initializing built-in extension DAMAGE
[ 102.681] Initializing built-in extension MIT-SCREEN-SAVER
[ 102.682] Initializing built-in extension DOUBLE-BUFFER
[ 102.683] Initializing built-in extension RECORD
[ 102.684] Initializing built-in extension DPMS
[ 102.684] Initializing built-in extension X-Resource
[ 102.685] Initializing built-in extension XVideo
[ 102.686] Initializing built-in extension XVideo-MotionCompensation
[ 102.687] Initializing built-in extension XFree86-VidModeExtension
[ 102.688] Initializing built-in extension XFree86-DGA
[ 102.689] Initializing built-in extension XFree86-DRI
[ 102.690] Initializing built-in extension DRI2
[ 102.690] (II) LoadModule: "glx"
[ 102.691] (II) Loading /usr/lib/xorg/modules/extensions/libglx.so
[ 102.719] (II) Module glx: vendor="X.Org Foundation"
[ 102.719] compiled for 1.14.3, module version = 1.0.0
[ 102.719] ABI class: X.Org Server Extension, version 7.0
[ 102.719] (==) AIGLX enabled
[ 102.721] Loading extension GLX
[ 102.721] (==) Matched nouveau as autoconfigured driver 0
[ 102.721] (==) Matched nvidia as autoconfigured driver 1
[ 102.721] (==) Matched nv as autoconfigured driver 2
[ 102.721] (==) Matched nouveau as autoconfigured driver 3
[ 102.721] (==) Matched nvidia as autoconfigured driver 4
[ 102.721] (==) Matched nv as autoconfigured driver 5
[ 102.721] (==) Matched vesa as autoconfigured driver 6
[ 102.721] (==) Matched modesetting as autoconfigured driver 7
[ 102.721] (==) Matched fbdev as autoconfigured driver 8
[ 102.721] (==) Assigned the driver to the xf86ConfigLayout
[ 102.721] (II) LoadModule: "nouveau"
[ 102.721] (II) Loading /usr/lib/xorg/modules/drivers/nouveau_drv.so
[ 102.751] (II) Module nouveau: vendor="X.Org Foundation"
[ 102.751] compiled for 1.14.2, module version = 1.0.9
[ 102.751] Module class: X.Org Video Driver
[ 102.751] ABI class: X.Org Video Driver, version 14.1
[ 102.751] (II) LoadModule: "nvidia"
[ 102.765] (WW) Warning, couldn't open module nvidia
[ 102.765] (II) UnloadModule: "nvidia"
[ 102.765] (II) Unloading nvidia
[ 102.765] (EE) Failed to load module "nvidia" (module does not exist, 0)
[ 102.765] (II) LoadModule: "nv"
[ 102.765] (WW) Warning, couldn't open module nv
[ 102.765] (II) UnloadModule: "nv"
[ 102.765] (II) Unloading nv
[ 102.765] (EE) Failed to load module "nv" (module does not exist, 0)
[ 102.765] (II) LoadModule: "vesa"
[ 102.765] (II) Loading /usr/lib/xorg/modules/drivers/vesa_drv.so
[ 102.776] (II) Module vesa: vendor="X.Org Foundation"
[ 102.776] compiled for 1.14.0, module version = 2.3.2
[ 102.776] Module class: X.Org Video Driver
[ 102.776] ABI class: X.Org Video Driver, version 14.1
[ 102.776] (II) LoadModule: "modesetting"
[ 102.776] (WW) Warning, couldn't open module modesetting
[ 102.776] (II) UnloadModule: "modesetting"
[ 102.776] (II) Unloading modesetting
[ 102.776] (EE) Failed to load module "modesetting" (module does not exist, 0)
[ 102.776] (II) LoadModule: "fbdev"
[ 102.776] (WW) Warning, couldn't open module fbdev
[ 102.776] (II) UnloadModule: "fbdev"
[ 102.776] (II) Unloading fbdev
[ 102.776] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 102.776] (II) NOUVEAU driver
[ 102.776] (II) NOUVEAU driver for NVIDIA chipset families :
[ 102.776] RIVA TNT (NV04)
[ 102.776] RIVA TNT2 (NV05)
[ 102.776] GeForce 256 (NV10)
[ 102.776] GeForce 2 (NV11, NV15)
[ 102.776] GeForce 4MX (NV17, NV18)
[ 102.776] GeForce 3 (NV20)
[ 102.776] GeForce 4Ti (NV25, NV28)
[ 102.776] GeForce FX (NV3x)
[ 102.776] GeForce 6 (NV4x)
[ 102.776] GeForce 7 (G7x)
[ 102.776] GeForce 8 (G8x)
[ 102.776] GeForce GTX 200 (NVA0)
[ 102.776] GeForce GTX 400 (NVC0)
[ 102.776] (II) VESA: driver for VESA chipsets: vesa
[ 102.776] (++) using VT number 1
[ 102.776] (II) [drm] nouveau interface version: 1.1.1
[ 102.777] (WW) Falling back to old probe method for vesa
[ 102.777] (II) Loading sub module "dri2"
[ 102.777] (II) LoadModule: "dri2"
[ 102.777] (II) Module "dri2" already built-in
[ 102.777] (--) NOUVEAU(0): Chipset: "NVIDIA NVA3"
[ 102.777] (II) NOUVEAU(0): Creating default Display subsection in Screen section
"Default Screen Section" for depth/fbbpp 24/32
[ 102.777] (==) NOUVEAU(0): Depth 24, (--) framebuffer bpp 32
[ 102.777] (==) NOUVEAU(0): RGB weight 888
[ 102.777] (==) NOUVEAU(0): Default visual is TrueColor
[ 102.777] (==) NOUVEAU(0): Using HW cursor
[ 102.777] (==) NOUVEAU(0): GLX sync to VBlank disabled.
[ 102.777] (==) NOUVEAU(0): Page flipping enabled
[ 102.777] (==) NOUVEAU(0): Swap limit set to 2 [Max allowed 2]
[ 102.845] (II) NOUVEAU(0): Output LVDS-1 has no monitor section
[ 102.950] (II) NOUVEAU(0): Output DP-1 has no monitor section
[ 103.056] (II) NOUVEAU(0): Output DP-2 has no monitor section
[ 103.056] (II) NOUVEAU(0): Output eDP-1 has no monitor section
[ 103.163] (II) NOUVEAU(0): Output DP-3 has no monitor section
[ 103.184] (II) NOUVEAU(0): Output VGA-1 has no monitor section
[ 103.211] (II) NOUVEAU(0): EDID for output LVDS-1
[ 103.211] (II) NOUVEAU(0): Manufacturer: CMO Model: 1595 Serial#: 0
[ 103.211] (II) NOUVEAU(0): Year: 2009 Week: 12
[ 103.211] (II) NOUVEAU(0): EDID Version: 1.3
[ 103.211] (II) NOUVEAU(0): Digital Display Input
[ 103.211] (II) NOUVEAU(0): Max Image Size [cm]: horiz.: 34 vert.: 19
[ 103.211] (II) NOUVEAU(0): Gamma: 2.20
[ 103.211] (II) NOUVEAU(0): No DPMS capabilities specified
[ 103.211] (II) NOUVEAU(0): Supported color encodings: RGB 4:4:4 YCrCb 4:4:4
[ 103.211] (II) NOUVEAU(0): First detailed timing is preferred mode
[ 103.211] (II) NOUVEAU(0): redX: 0.610 redY: 0.343 greenX: 0.342 greenY: 0.581
[ 103.211] (II) NOUVEAU(0): blueX: 0.162 blueY: 0.083 whiteX: 0.313 whiteY: 0.329
[ 103.211] (II) NOUVEAU(0): Manufacturer's mask: 0
[ 103.211] (II) NOUVEAU(0): Supported detailed timing:
[ 103.211] (II) NOUVEAU(0): clock: 107.8 MHz Image Size: 344 x 193 mm
[ 103.211] (II) NOUVEAU(0): h_active: 1600 h_sync: 1626 h_sync_end 1686 h_blank_end 1892 h_border: 0
[ 103.211] (II) NOUVEAU(0): v_active: 900 v_sync: 909 v_sync_end 919 v_blanking: 949 v_border: 0
[ 103.212] (II) NOUVEAU(0): N156O6-L01
[ 103.212] (II) NOUVEAU(0): CMO
[ 103.212] (II) NOUVEAU(0): N156O6-L01
[ 103.212] (II) NOUVEAU(0): EDID (in hex):
[ 103.212] (II) NOUVEAU(0): 00ffffffffffff000daf951500000000
[ 103.212] (II) NOUVEAU(0): 0c130103802213780a7b959c57579429
[ 103.212] (II) NOUVEAU(0): 15505400000001010101010101010101
[ 103.212] (II) NOUVEAU(0): 0101010101011c2a4024618431301a3c
[ 103.212] (II) NOUVEAU(0): 9a0058c110000018000000fe004e3135
[ 103.212] (II) NOUVEAU(0): 364f362d4c30310a2020000000fe0043
[ 103.212] (II) NOUVEAU(0): 4d4f0a202020202020202020000000fe
[ 103.212] (II) NOUVEAU(0): 004e3135364f362d4c30310a2020001c
[ 103.212] (II) NOUVEAU(0): Printing probed modes for output LVDS-1
[ 103.212] (II) NOUVEAU(0): Modeline "1600x900"x60.0 107.80 1600 1626 1686 1892 900 909 919 949 -hsync -vsync (57.0 kHz eP)
[ 103.212] (II) NOUVEAU(0): Modeline "1152x864"x60.0 81.75 1152 1216 1336 1520 864 867 871 897 -hsync +vsync (53.8 kHz e)
[ 103.212] (II) NOUVEAU(0): Modeline "1024x768"x59.9 63.50 1024 1072 1176 1328 768 771 775 798 -hsync +vsync (47.8 kHz e)
[ 103.212] (II) NOUVEAU(0): Modeline "800x600"x59.9 38.25 800 832 912 1024 600 603 607 624 -hsync +vsync (37.4 kHz e)
[ 103.212] (II) NOUVEAU(0): Modeline "640x480"x59.4 23.75 640 664 720 800 480 483 487 500 -hsync +vsync (29.7 kHz e)
[ 103.212] (II) NOUVEAU(0): Modeline "720x400"x59.6 22.25 720 744 808 896 400 403 413 417 -hsync +vsync (24.8 kHz e)
[ 103.212] (II) NOUVEAU(0): Modeline "640x400"x60.0 20.00 640 664 720 800 400 403 409 417 -hsync +vsync (25.0 kHz e)
[ 103.212] (II) NOUVEAU(0): Modeline "640x350"x59.8 17.50 640 664 720 800 350 353 363 366 -hsync +vsync (21.9 kHz e)
[ 103.316] (II) NOUVEAU(0): EDID for output DP-1
[ 103.423] (II) NOUVEAU(0): EDID for output DP-2
[ 103.423] (II) NOUVEAU(0): EDID for output eDP-1
[ 103.530] (II) NOUVEAU(0): EDID for output DP-3
[ 103.550] (II) NOUVEAU(0): EDID for output VGA-1
[ 103.550] (II) NOUVEAU(0): Output LVDS-1 connected
[ 103.550] (II) NOUVEAU(0): Output DP-1 disconnected
[ 103.550] (II) NOUVEAU(0): Output DP-2 disconnected
[ 103.551] (II) NOUVEAU(0): Output eDP-1 disconnected
[ 103.551] (II) NOUVEAU(0): Output DP-3 disconnected
[ 103.551] (II) NOUVEAU(0): Output VGA-1 disconnected
[ 103.551] (II) NOUVEAU(0): Using exact sizes for initial modes
[ 103.551] (II) NOUVEAU(0): Output LVDS-1 using initial mode 1600x900
[ 103.551] (II) NOUVEAU(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
[ 103.551] (--) NOUVEAU(0): Virtual size is 1600x900 (pitch 0)
[ 103.551] (**) NOUVEAU(0): Driver mode "1600x900": 107.8 MHz (scaled from 0.0 MHz), 57.0 kHz, 60.0 Hz
[ 103.551] (II) NOUVEAU(0): Modeline "1600x900"x60.0 107.80 1600 1626 1686 1892 900 909 919 949 -hsync -vsync (57.0 kHz eP)
[ 103.551] (**) NOUVEAU(0): Driver mode "1152x864": 81.8 MHz (scaled from 0.0 MHz), 53.8 kHz, 60.0 Hz
[ 103.551] (II) NOUVEAU(0): Modeline "1152x864"x60.0 81.75 1152 1216 1336 1520 864 867 871 897 -hsync +vsync (53.8 kHz e)
[ 103.551] (**) NOUVEAU(0): Driver mode "1024x768": 63.5 MHz (scaled from 0.0 MHz), 47.8 kHz, 59.9 Hz
[ 103.551] (II) NOUVEAU(0): Modeline "1024x768"x59.9 63.50 1024 1072 1176 1328 768 771 775 798 -hsync +vsync (47.8 kHz e)
[ 103.551] (**) NOUVEAU(0): Driver mode "800x600": 38.2 MHz (scaled from 0.0 MHz), 37.4 kHz, 59.9 Hz
[ 103.551] (II) NOUVEAU(0): Modeline "800x600"x59.9 38.25 800 832 912 1024 600 603 607 624 -hsync +vsync (37.4 kHz e)
[ 103.551] (**) NOUVEAU(0): Driver mode "640x480": 23.8 MHz (scaled from 0.0 MHz), 29.7 kHz, 59.4 Hz
[ 103.551] (II) NOUVEAU(0): Modeline "640x480"x59.4 23.75 640 664 720 800 480 483 487 500 -hsync +vsync (29.7 kHz e)
[ 103.551] (**) NOUVEAU(0): Driver mode "720x400": 22.2 MHz (scaled from 0.0 MHz), 24.8 kHz, 59.6 Hz
[ 103.551] (II) NOUVEAU(0): Modeline "720x400"x59.6 22.25 720 744 808 896 400 403 413 417 -hsync +vsync (24.8 kHz e)
[ 103.551] (**) NOUVEAU(0): Driver mode "640x400": 20.0 MHz (scaled from 0.0 MHz), 25.0 kHz, 60.0 Hz
[ 103.551] (II) NOUVEAU(0): Modeline "640x400"x60.0 20.00 640 664 720 800 400 403 409 417 -hsync +vsync (25.0 kHz e)
[ 103.551] (**) NOUVEAU(0): Driver mode "640x350": 17.5 MHz (scaled from 0.0 MHz), 21.9 kHz, 59.8 Hz
[ 103.551] (II) NOUVEAU(0): Modeline "640x350"x59.8 17.50 640 664 720 800 350 353 363 366 -hsync +vsync (21.9 kHz e)
[ 103.551] (==) NOUVEAU(0): DPI set to (96, 96)
[ 103.551] (II) Loading sub module "fb"
[ 103.551] (II) LoadModule: "fb"
[ 103.551] (II) Loading /usr/lib/xorg/modules/libfb.so
[ 105.504] (II) Module fb: vendor="X.Org Foundation"
[ 105.504] compiled for 1.14.3, module version = 1.0.0
[ 105.504] ABI class: X.Org ANSI C Emulation, version 0.4
[ 105.504] (II) Loading sub module "exa"
[ 105.504] (II) LoadModule: "exa"
[ 105.504] (II) Loading /usr/lib/xorg/modules/libexa.so
[ 105.508] (II) Module exa: vendor="X.Org Foundation"
[ 105.508] compiled for 1.14.3, module version = 2.6.0
[ 105.508] ABI class: X.Org Video Driver, version 14.1
[ 105.508] (II) Loading sub module "shadowfb"
[ 105.508] (II) LoadModule: "shadowfb"
[ 105.508] (II) Loading /usr/lib/xorg/modules/libshadowfb.so
[ 105.518] (II) Module shadowfb: vendor="X.Org Foundation"
[ 105.518] compiled for 1.14.3, module version = 1.0.0
[ 105.518] ABI class: X.Org ANSI C Emulation, version 0.4
[ 105.518] (II) UnloadModule: "vesa"
[ 105.518] (II) Unloading vesa
[ 105.518] (--) Depth 24 pixmap format is 32 bpp
[ 105.521] (II) NOUVEAU(0): Opened GPU channel 0
[ 105.547] (II) NOUVEAU(0): [DRI2] Setup complete
[ 105.547] (II) NOUVEAU(0): [DRI2] DRI driver: nouveau
[ 105.547] (II) NOUVEAU(0): [DRI2] VDPAU driver: nouveau
[ 108.224] (II) EXA(0): Driver allocated offscreen pixmaps
[ 108.224] (II) EXA(0): Driver registered support for the following operations:
[ 108.224] (II) Solid
[ 108.224] (II) Copy
[ 108.224] (II) Composite (RENDER acceleration)
[ 108.224] (II) UploadToScreen
[ 108.224] (II) DownloadFromScreen
[ 108.224] (==) NOUVEAU(0): Backing store disabled
[ 108.224] (==) NOUVEAU(0): Silken mouse enabled
[ 108.226] (II) NOUVEAU(0): [XvMC] Associated with Nouveau GeForce 8/9 Textured Video.
[ 108.226] (II) NOUVEAU(0): [XvMC] Extension initialized.
[ 108.226] (==) NOUVEAU(0): DPMS enabled
[ 108.226] (II) NOUVEAU(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[ 108.228] (--) RandR disabled
[ 142.503] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[ 142.503] (II) AIGLX: enabled GLX_INTEL_swap_event
[ 142.504] (II) AIGLX: enabled GLX_ARB_create_context
[ 142.504] (II) AIGLX: enabled GLX_ARB_create_context_profile
[ 142.504] (II) AIGLX: enabled GLX_EXT_create_context_es2_profile
[ 142.504] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
[ 142.504] (II) AIGLX: GLX_EXT_texture_from_pixmap backed by buffer objects
[ 142.505] (II) AIGLX: Loaded and initialized nouveau
[ 142.505] (II) GLX: Initialized DRI2 GL provider for screen 0
[ 159.503] (II) NOUVEAU(0): NVEnterVT is called.
[ 159.532] (II) NOUVEAU(0): Setting screen physical size to 423 x 238
[ 159.532] resize called 1600 900
[ 160.324] (II) config/udev: Adding input device Power Button (/dev/input/event3)
[ 160.324] (**) Power Button: Applying InputClass "evdev keyboard catchall"
[ 160.324] (II) LoadModule: "evdev"
[ 160.324] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
[ 160.355] (II) Module evdev: vendor="X.Org Foundation"
[ 160.355] compiled for 1.14.3, module version = 2.8.2
[ 160.355] Module class: X.Org XInput Driver
[ 160.355] ABI class: X.Org XInput driver, version 19.1
[ 160.355] (II) Using input driver 'evdev' for 'Power Button'
[ 160.355] (**) Power Button: always reports core events
[ 160.355] (**) evdev: Power Button: Device: "/dev/input/event3"
[ 160.355] (--) evdev: Power Button: Vendor 0 Product 0x1
[ 160.355] (--) evdev: Power Button: Found keys
[ 160.355] (II) evdev: Power Button: Configuring as keyboard
[ 160.355] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3/event3"
[ 160.355] (II) XINPUT: Adding extended input device "Power Button" (type: KEYBOARD, id 6)
[ 160.355] (**) Option "xkb_rules" "evdev"
[ 160.355] (**) Option "xkb_model" "pc104"
[ 160.355] (**) Option "xkb_layout" "us"
[ 160.392] (II) config/udev: Adding input device Video Bus (/dev/input/event4)
[ 160.392] (**) Video Bus: Applying InputClass "evdev keyboard catchall"
[ 160.392] (II) Using input driver 'evdev' for 'Video Bus'
[ 160.392] (**) Video Bus: always reports core events
[ 160.392] (**) evdev: Video Bus: Device: "/dev/input/event4"
[ 160.392] (--) evdev: Video Bus: Vendor 0 Product 0x6
[ 160.392] (--) evdev: Video Bus: Found keys
[ 160.392] (II) evdev: Video Bus: Configuring as keyboard
[ 160.392] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:03/LNXVIDEO:00/input/input4/event4"
[ 160.392] (II) XINPUT: Adding extended input device "Video Bus" (type: KEYBOARD, id 7)
[ 160.392] (**) Option "xkb_rules" "evdev"
[ 160.392] (**) Option "xkb_model" "pc104"
[ 160.393] (**) Option "xkb_layout" "us"
[ 160.393] (II) config/udev: Adding input device Lid Switch (/dev/input/event2)
[ 160.393] (II) No input driver specified, ignoring this device.
[ 160.393] (II) This device may have been added with another device file.
[ 160.394] (II) config/udev: Adding input device Sleep Button (/dev/input/event1)
[ 160.394] (**) Sleep Button: Applying InputClass "evdev keyboard catchall"
[ 160.394] (II) Using input driver 'evdev' for 'Sleep Button'
[ 160.394] (**) Sleep Button: always reports core events
[ 160.394] (**) evdev: Sleep Button: Device: "/dev/input/event1"
[ 160.394] (--) evdev: Sleep Button: Vendor 0 Product 0x3
[ 160.394] (--) evdev: Sleep Button: Found keys
[ 160.394] (II) evdev: Sleep Button: Configuring as keyboard
[ 160.394] (**) Option "config_info" "udev:/sys/devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input1/event1"
[ 160.394] (II) XINPUT: Adding extended input device "Sleep Button" (type: KEYBOARD, id 8)
[ 160.394] (**) Option "xkb_rules" "evdev"
[ 160.394] (**) Option "xkb_model" "pc104"
[ 160.394] (**) Option "xkb_layout" "us"
[ 160.395] (II) config/udev: Adding drm device (/dev/dri/card0)
[ 160.396] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=9 (/dev/input/event13)
[ 160.396] (II) No input driver specified, ignoring this device.
[ 160.396] (II) This device may have been added with another device file.
[ 160.396] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=8 (/dev/input/event14)
[ 160.396] (II) No input driver specified, ignoring this device.
[ 160.396] (II) This device may have been added with another device file.
[ 160.397] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=7 (/dev/input/event15)
[ 160.397] (II) No input driver specified, ignoring this device.
[ 160.397] (II) This device may have been added with another device file.
[ 160.397] (II) config/udev: Adding input device HDA NVidia HDMI/DP,pcm=3 (/dev/input/event16)
[ 160.397] (II) No input driver specified, ignoring this device.
[ 160.397] (II) This device may have been added with another device file.
[ 160.398] (II) config/udev: Adding input device HDA Digital PCBeep (/dev/input/event6)
[ 160.398] (II) No input driver specified, ignoring this device.
[ 160.398] (II) This device may have been added with another device file.
[ 160.398] (II) config/udev: Adding input device HDA Intel MID Mic (/dev/input/event10)
[ 160.398] (II) No input driver specified, ignoring this device.
[ 160.398] (II) This device may have been added with another device file.
[ 160.399] (II) config/udev: Adding input device HDA Intel MID Dock Headphone (/dev/input/event7)
[ 160.399] (II) No input driver specified, ignoring this device.
[ 160.399] (II) This device may have been added with another device file.
[ 160.399] (II) config/udev: Adding input device HDA Intel MID Headphone (/dev/input/event8)
[ 160.399] (II) No input driver specified, ignoring this device.
[ 160.399] (II) This device may have been added with another device file.
[ 160.400] (II) config/udev: Adding input device HDA Intel MID Line (/dev/input/event9)
[ 160.400] (II) No input driver specified, ignoring this device.
[ 160.400] (II) This device may have been added with another device file.
[ 160.400] (II) config/udev: Adding input device AT Translated Set 2 keyboard (/dev/input/event0)
[ 160.400] (**) AT Translated Set 2 keyboard: Applying InputClass "evdev keyboard catchall"
[ 160.401] (II) Using input driver 'evdev' for 'AT Translated Set 2 keyboard'
[ 160.401] (**) AT Translated Set 2 keyboard: always reports core events
[ 160.401] (**) evdev: AT Translated Set 2 keyboard: Device: "/dev/input/event0"
[ 160.401] (--) evdev: AT Translated Set 2 keyboard: Vendor 0x1 Product 0x1
[ 160.401] (--) evdev: AT Translated Set 2 keyboard: Found keys
[ 160.401] (II) evdev: AT Translated Set 2 keyboard: Configuring as keyboard
[ 160.401] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio0/input/input0/event0"
[ 160.401] (II) XINPUT: Adding extended input device "AT Translated Set 2 keyboard" (type: KEYBOARD, id 9)
[ 160.401] (**) Option "xkb_rules" "evdev"
[ 160.401] (**) Option "xkb_model" "pc104"
[ 160.401] (**) Option "xkb_layout" "us"
[ 160.402] (II) config/udev: Adding input device PS/2 Generic Mouse (/dev/input/event11)
[ 160.402] (**) PS/2 Generic Mouse: Applying InputClass "evdev pointer catchall"
[ 160.402] (II) Using input driver 'evdev' for 'PS/2 Generic Mouse'
[ 160.402] (**) PS/2 Generic Mouse: always reports core events
[ 160.402] (**) evdev: PS/2 Generic Mouse: Device: "/dev/input/event11"
[ 160.402] (--) evdev: PS/2 Generic Mouse: Vendor 0x2 Product 0x1
[ 160.402] (--) evdev: PS/2 Generic Mouse: Found 3 mouse buttons
[ 160.402] (--) evdev: PS/2 Generic Mouse: Found relative axes
[ 160.402] (--) evdev: PS/2 Generic Mouse: Found x and y relative axes
[ 160.402] (II) evdev: PS/2 Generic Mouse: Configuring as mouse
[ 160.402] (**) evdev: PS/2 Generic Mouse: YAxisMapping: buttons 4 and 5
[ 160.402] (**) evdev: PS/2 Generic Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 160.402] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio1/input/input11/event11"
[ 160.402] (II) XINPUT: Adding extended input device "PS/2 Generic Mouse" (type: MOUSE, id 10)
[ 160.402] (II) evdev: PS/2 Generic Mouse: initialized for relative axes.
[ 160.402] (**) PS/2 Generic Mouse: (accel) keeping acceleration scheme 1
[ 160.403] (**) PS/2 Generic Mouse: (accel) acceleration profile 0
[ 160.403] (**) PS/2 Generic Mouse: (accel) acceleration factor: 2.000
[ 160.403] (**) PS/2 Generic Mouse: (accel) acceleration threshold: 4
[ 160.403] (II) config/udev: Adding input device PS/2 Generic Mouse (/dev/input/mouse0)
[ 160.403] (II) No input driver specified, ignoring this device.
[ 160.403] (II) This device may have been added with another device file.
[ 160.403] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/event17)
[ 160.403] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "evdev touchpad catchall"
[ 160.403] (**) SynPS/2 Synaptics TouchPad: Applying InputClass "touchpad catchall"
[ 160.403] (II) LoadModule: "synaptics"
[ 160.403] (II) Loading /usr/lib/xorg/modules/input/synaptics_drv.so
[ 160.415] (II) Module synaptics: vendor="X.Org Foundation"
[ 160.415] compiled for 1.14.1, module version = 1.7.1
[ 160.415] Module class: X.Org XInput Driver
[ 160.415] ABI class: X.Org XInput driver, version 19.1
[ 160.415] (II) Using input driver 'synaptics' for 'SynPS/2 Synaptics TouchPad'
[ 160.415] (**) SynPS/2 Synaptics TouchPad: always reports core events
[ 160.415] (**) Option "Device" "/dev/input/event17"
[ 160.503] (II) synaptics: SynPS/2 Synaptics TouchPad: ignoring touch events for semi-multitouch device
[ 160.503] (--) synaptics: SynPS/2 Synaptics TouchPad: x-axis range 1472 - 5600 (res 57)
[ 160.503] (--) synaptics: SynPS/2 Synaptics TouchPad: y-axis range 1408 - 4884 (res 123)
[ 160.503] (--) synaptics: SynPS/2 Synaptics TouchPad: pressure range 0 - 255
[ 160.503] (--) synaptics: SynPS/2 Synaptics TouchPad: finger width range 0 - 15
[ 160.503] (--) synaptics: SynPS/2 Synaptics TouchPad: buttons: left right middle double triple
[ 160.503] (--) synaptics: SynPS/2 Synaptics TouchPad: Vendor 0x2 Product 0x7
[ 160.503] (**) Option "VertScrollDelta" "250"
[ 160.503] (**) Option "VertTwoFingerScroll" "on"
[ 160.504] (**) Option "HorizTwoFingerScroll" "off"
[ 160.504] (**) Option "TapButton1" "1"
[ 160.504] (**) Option "TapButton2" "2"
[ 160.504] (**) Option "TapButton3" "3"
[ 160.504] (**) Option "CoastingSpeed" "0"
[ 160.504] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[ 160.504] (**) SynPS/2 Synaptics TouchPad: always reports core events
[ 160.530] (**) Option "config_info" "udev:/sys/devices/platform/i8042/serio4/input/input17/event17"
[ 160.530] (II) XINPUT: Adding extended input device "SynPS/2 Synaptics TouchPad" (type: TOUCHPAD, id 11)
[ 160.530] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MinSpeed is now constant deceleration 2.5
[ 160.530] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) MaxSpeed is now 1.75
[ 160.530] (**) synaptics: SynPS/2 Synaptics TouchPad: (accel) AccelFactor is now 0.037
[ 160.531] (**) SynPS/2 Synaptics TouchPad: (accel) keeping acceleration scheme 1
[ 160.531] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration profile 1
[ 160.531] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration factor: 2.000
[ 160.531] (**) SynPS/2 Synaptics TouchPad: (accel) acceleration threshold: 4
[ 160.531] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[ 160.531] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse1)
[ 160.531] (II) No input driver specified, ignoring this device.
[ 160.531] (II) This device may have been added with another device file.
[ 160.532] (II) config/udev: Adding input device ST LIS3LV02DL Accelerometer (/dev/input/event5)
[ 160.532] (II) No input driver specified, ignoring this device.
[ 160.532] (II) This device may have been added with another device file.
[ 160.532] (II) config/udev: Adding input device ST LIS3LV02DL Accelerometer (/dev/input/js0)
[ 160.532] (II) No input driver specified, ignoring this device.
[ 160.532] (II) This device may have been added with another device file.
[ 160.533] (II) config/udev: Adding input device HP WMI hotkeys (/dev/input/event12)
[ 160.533] (**) HP WMI hotkeys: Applying InputClass "evdev keyboard catchall"
[ 160.533] (II) Using input driver 'evdev' for 'HP WMI hotkeys'
[ 160.533] (**) HP WMI hotkeys: always reports core events
[ 160.533] (**) evdev: HP WMI hotkeys: Device: "/dev/input/event12"
[ 160.533] (--) evdev: HP WMI hotkeys: Vendor 0 Product 0
[ 160.533] (--) evdev: HP WMI hotkeys: Found keys
[ 160.533] (II) evdev: HP WMI hotkeys: Configuring as keyboard
[ 160.533] (**) Option "config_info" "udev:/sys/devices/virtual/input/input12/event12"
[ 160.533] (II) XINPUT: Adding extended input device "HP WMI hotkeys" (type: KEYBOARD, id 12)
[ 160.533] (**) Option "xkb_rules" "evdev"
[ 160.533] (**) Option "xkb_model" "pc104"
[ 160.533] (**) Option "xkb_layout" "us"
[ 164.083] (II) AIGLX: Suspending AIGLX clients for VT switch
[ 164.083] (II) NOUVEAU(0): NVLeaveVT is called.
[ 181.123] (II) AIGLX: Resuming AIGLX clients after VT switch
[ 181.123] (II) NOUVEAU(0): NVEnterVT is called.
[ 181.179] (II) NOUVEAU(0): EDID vendor "CMO", prod id 5525
[ 181.179] (II) NOUVEAU(0): Printing DDC gathered Modelines:
[ 181.179] (II) NOUVEAU(0): Modeline "1600x900"x0.0 107.80 1600 1626 1686 1892 900 909 919 949 -hsync -vsync (57.0 kHz eP)
[ 181.517] (--) synaptics: SynPS/2 Synaptics TouchPad: touchpad found
[ 181.517] setversion 1.4 failed
(EE) [mi] EQ overflowing. Additional events will be discarded until existing events are processed.
(EE)
(EE) Backtrace:
(EE) 0: /usr/bin/X (xorg_backtrace+0x3d) [0x57f67d]
(EE) 1: /usr/bin/X (mieqEnqueue+0x22b) [0x5615bb]
(EE) 2: /usr/bin/X (QueueKeyboardEvents+0x52) [0x44d452]
(EE) 3: /usr/bin/X (xf86PostKeyboardEvent+0x44) [0x483e84]
(EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f4f79e94000+0x5591) [0x7f4f79e99591]
(EE) 5: /usr/bin/X (0x400000+0x73da8) [0x473da8]
(EE) 6: /usr/bin/X (0x400000+0x9c330) [0x49c330]
(EE) 7: /usr/lib/libpthread.so.0 (0x7f4f7f8af000+0xf870) [0x7f4f7f8be870]
(EE) 8: /usr/lib/libc.so.6 (ioctl+0x7) [0x7f4f7e9eef17]
(EE) 9: /usr/lib/libdrm.so.2 (drmCommandWrite+0x5d) [0x7f4f8055e9fd]
(EE) 10: /usr/lib/libdrm_nouveau.so.2 (nouveau_bo_wait+0x8a) [0x7f4f8058446a]
(EE) 11: /usr/lib/xorg/modules/drivers/nouveau_drv.so (0x7f4f7d349000+0x716b) [0x7f4f7d35016b]
(EE) 12: /usr/lib/xorg/modules/libexa.so (0x7f4f7cd05000+0xb308) [0x7f4f7cd10308]
(EE) 13: /usr/bin/X (0x400000+0x170563) [0x570563]
(EE) 14: /usr/bin/X (0x400000+0xc0f95) [0x4c0f95]
(EE) 15: /usr/bin/X (0x400000+0x104193) [0x504193]
(EE) 16: /usr/bin/X (0x400000+0x373be) [0x4373be]
(EE) 17: /usr/bin/X (0x400000+0x2693a) [0x42693a]
(EE) 18: /usr/lib/libc.so.6 (__libc_start_main+0xf5) [0x7f4f7e932bc5]
(EE) 19: /usr/bin/X (0x400000+0x26c81) [0x426c81]
(EE)
(EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up the stack.
(EE) [mi] mieq is *NOT* the cause. It is a victim.
(EE) [mi] EQ overflow continuing. 100 events have been dropped.
(EE)
(EE) Backtrace:
(EE) 0: /usr/bin/X (xorg_backtrace+0x3d) [0x57f67d]
(EE) 1: /usr/bin/X (QueueKeyboardEvents+0x52) [0x44d452]
(EE) 2: /usr/bin/X (xf86PostKeyboardEvent+0x44) [0x483e84]
(EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f4f79e94000+0x5591) [0x7f4f79e99591]
(EE) 4: /usr/bin/X (0x400000+0x73da8) [0x473da8]
(EE) 5: /usr/bin/X (0x400000+0x9c330) [0x49c330]
(EE) 6: /usr/lib/libpthread.so.0 (0x7f4f7f8af000+0xf870) [0x7f4f7f8be870]
(EE) 7: /usr/lib/libc.so.6 (ioctl+0x7) [0x7f4f7e9eef17]
(EE) 8: /usr/lib/libdrm.so.2 (drmCommandWrite+0x5d) [0x7f4f8055e9fd]
(EE) 9: /usr/lib/libdrm_nouveau.so.2 (nouveau_bo_wait+0x8a) [0x7f4f8058446a]
(EE) 10: /usr/lib/xorg/modules/drivers/nouveau_drv.so (0x7f4f7d349000+0x716b) [0x7f4f7d35016b]
(EE) 11: /usr/lib/xorg/modules/libexa.so (0x7f4f7cd05000+0xb308) [0x7f4f7cd10308]
(EE) 12: /usr/bin/X (0x400000+0x170563) [0x570563]
(EE) 13: /usr/bin/X (0x400000+0xc0f95) [0x4c0f95]
(EE) 14: /usr/bin/X (0x400000+0x104193) [0x504193]
(EE) 15: /usr/bin/X (0x400000+0x373be) [0x4373be]
(EE) 16: /usr/bin/X (0x400000+0x2693a) [0x42693a]
(EE) 17: /usr/lib/libc.so.6 (__libc_start_main+0xf5) [0x7f4f7e932bc5]
(EE) 18: /usr/bin/X (0x400000+0x26c81) [0x426c81]
(EE)
[ 216.437] [mi] Increasing EQ size to 512 to prevent dropped events.
[ 216.438] [mi] EQ processing has resumed after 188 dropped events.
[ 216.438] [mi] This may be caused my a misbehaving driver monopolizing the server's resources.
[ 216.438] Failed to switch from vt01 to vt06: Input/output error
[ 216.438] Failed to switch from vt01 to vt06: Input/output error
[ 216.438] Failed to switch from vt01 to vt06: Input/output error
[ 216.438] Failed to switch from vt01 to vt02: Input/output error
[ 216.438] Failed to switch from vt01 to vt03: Input/output error
[ 216.438] Failed to switch from vt01 to vt04: Input/output error
[ 216.438] Failed to switch from vt01 to vt05: Input/output error
[ 216.438] Failed to switch from vt01 to vt06: Input/output error
[ 216.438] Failed to switch from vt01 to vt07: Input/output error
[ 216.438] Failed to switch from vt01 to vt08: Input/output error
[ 216.438] Failed to switch from vt01 to vt09: Input/output error
[ 216.438] Failed to switch from vt01 to vt10: Input/output error
[ 216.438] Failed to switch from vt01 to vt11: Input/output error
[ 216.438] Failed to switch from vt01 to vt02: Input/output error
[ 216.810] (II) evdev: HP WMI hotkeys: Close
[ 216.811] (II) UnloadModule: "evdev"
[ 216.811] (II) UnloadModule: "synaptics"
[ 216.811] (II) evdev: PS/2 Generic Mouse: Close
[ 216.811] (II) UnloadModule: "evdev"
[ 216.811] (II) evdev: AT Translated Set 2 keyboard: Close
[ 216.811] (II) UnloadModule: "evdev"
[ 216.811] (II) evdev: Sleep Button: Close
[ 216.811] (II) UnloadModule: "evdev"
[ 216.811] (II) evdev: Video Bus: Close
[ 216.811] (II) UnloadModule: "evdev"
[ 216.811] (II) evdev: Power Button: Close
[ 216.811] (II) UnloadModule: "evdev"
In addition, I can't seem to find any other files related nvidia that seem like they would matter, except for ~/.nvidia-settings-rc, which I moved to ~/.nvidia-settings-rc.bk (prior to the attempt which created the log above). Keep in mind that this is after re-installing nvidia so I can startx and have a working system... Is there anything that looks like it wouldn't be removed by the nvidia package?
# find / -name *nvidia*
/proc/irq/63/nvidia
/proc/driver/nvidia
/home/jwhendy/.nvidia-settings-rc.bk
[hits from /usr/share/icons excluded]
[hits from /usr/share/ excluded]
/usr/lib/libnvidia-tls.so
/usr/lib/modules/extramodules-3.11-ARCH/nvidia.ko.gz
/usr/lib/modules/3.11.6-1-ARCH/kernel/drivers/net/ethernet/nvidia
/usr/lib/nvidia
/usr/lib/libnvidia-tls.so.325.15
/usr/lib/libnvidia-ml.so
/usr/lib/libnvidia-glcore.so
/usr/lib/vdpau/libvdpau_nvidia.so
/usr/lib/vdpau/libvdpau_nvidia.so.1
/usr/lib/vdpau/libvdpau_nvidia.so.325.15
/usr/lib/libnvidia-glcore.so.325.15
/usr/lib/libnvidia-ml.so.325.15
/usr/lib/libnvidia-cfg.so
/usr/lib/xorg/modules/drivers/nvidia_drv.so
/usr/lib/libnvidia-cfg.so.325.15
/usr/lib/modprobe.d/nvidia.conf # owned by nvidia; removed when I switch to nouveau
/usr/lib/libnvidia-cfg.so.1
/usr/lib/libnvidia-ml.so.1
/usr/bin/nvidia-settings
/usr/bin/nvidia-xconfig
/usr/bin/nvidia-smi
/usr/bin/nvidia-bug-report.sh
/usr/bin/nvidia-debugdump
/root/.nvidia-settings-rc
[hits from /var/abs/ removed]
/dev/nvidia0
/dev/nvidiactl
/sys/bus/pci/drivers/nvidia
/sys/kernel/slab/nvidia_p2p_page_t
/sys/module/drm/holders/nvidia
/sys/module/i2c_core/holders/nvidia
/sys/module/nvidia
/sys/module/nvidia/drivers/pci:nvidia
Anything look odd in the log or the files?
As always, feel free to suggest other things to try -- I can pipe ls into files to show what files are available when I'm pre-startx with nouveau installed, or more Xorg logs... My computer is not happy wtih nvidia at all and is nearly unusable. I really need to solve this until nvidia is compatible with 3.11 kernels again.

Switching from Flash to Flash Catalyst/Flex

For the last few years I have been developing applications for project reporting. To explain this in simplest terms, my clients give me hundreds of reports and supporting documents, graphics, videos, etc. which I then condense and reorganize into a presentation/application in Flash. The project is then published as an .exe to be burned to CD ROM or DVD along with any supporting files and is then distributed to project stake holders, investors, etc.
I'm considering the possibility of a switch from Flash to Flash Catalyst/Flex and want to outline what my needs are, here in the forum, in hopes that others now using Catalyst/Flex can help me decide if this is an appropriate move.
Features needed:
1. Basic animation, transitions, etc.
2. Full Navigation (up to 3 levels) for up to 300 slides.
3. Keyboard navigation (PageUp/PageDown) to navigate sequentially through the entire presentation.
4. Linking into other applications and documents - Word, Excel, Power Point, etc.
5. Full Screen Mode
6. Slide Show Mode
7. Search Features
8. Slide sharing (via email)
9. Video and audio w/controls
10. Pan and Zoom w/controls (panning and zooming of graphics and .swf files)
11. Scrolling (scrolling of text, graphics and .swf files)
12. Interactive forms
Can anyone please comment specifically on these features and wether or not they are possible using Catalyst and/or Catalyst/Flex in combination.
Thank you all for any insight or suggestions.
John

With the exception of making fre-form animations (like a cartoon for example), everything you can do in Flash can be done in Flex considerably faster.
The downside is that Flex applications (especially ones designed in Catalyst) are generally larger, and consume more memory. Personally, I never publish anything made in Catalyst without optimizing it in Flash Builder first.
If the drop in operating performance isn't a deal breaker (most of the time you can't even notice it), then I would certainly consider moving to Flex going forward on new projects.

IPod classic - switching from Windows to Mac

I have an iPod classic and am switching from Windows to Mac - what's the best way to retain my iPod library? Thanks!

If you just want to connect and use the iPod on the Mac then set it to manual update on your PC first. The content of iTunes and the iPod are not syncronised in this mode so the two can be different. You can directly access the content of the iPod and play it through iTunes and you can drag and drop whatever you want to the iPod from either library:
Using iPod with Multiple computers
Managing content manually on iPod and iPhone
Syncing Music to iPod
Something else to be aware of when using an iPod in manual mode is that the "Do Not Disconnect" message will remain on the display until you physically eject the device: Safely Disconnect IPod
Macs can read Windows drives, the iPod shuffle for instance comes Windows formatted and is fully supported (you can update the firmware or restore it on the Mac and it retains it's Windows formatting). Other iPods (such as a 5th Generation or Classic for example) can be used in Windows format on a Mac but have to have the firmware updated or be restored on a PC to maintain the formatting. If however you don't intend using the iPod on a PC again you'll need to transfer your library from your PC so you can restore and reformat the iPod and keep it's firmware updated.
Once you are safely connected there are a few things you can do to restore your new iTunes directly from the iPod. If you have any iTunes Music Store purchases the transfer of purchased content from the iPod to authorised computers was introduced with iTunes 7. You'll find details in this article: Copying iTunes Store purchases from your iPod or iPhone to a computer
The transfer of content from sources such as songs imported from CD is designed by default to be one way from iTunes to iPod. However there are a number of third party utilities that you can use to retrieve music files and playlists from your iPod. I use Senuti but have a look at the web pages and documentation for the others too, you'll find that they have varying degrees of functionality and some will transfer movies, videos, photos and games as well. This is just a small selection of what's available, you can read reviews and comparisons of some of them here:
Wired News - Rescue Your Stranded Tunes
Comparison of iPod managers
Senuti Mac Only (Currently only the beta version is iPod Touch & iPhone compatible)
PodView Mac Only
PodWorks Mac Only
iPodDisk PPC Mac Only (experimental version available for Intel Macs)
TuneAid Mac only (iPhone and iPod Touch compatible)
iPodRip Mac & Windows
YamiPod Mac & Windows
Music Rescue Mac & Windows
iPod Music Liberator Mac & Windows
iGadget Mac & Windows (iPhone and iPod Touch compatible)
Floola Mac & Windows
iRepo Mac & Windows (iPhone and iPod Touch compatible)
iPod Access Mac & Windows (iPhone and iPod Touch compatible)
TouchCopy Mac & Windows (iPhone and iPod Touch compatible)
There's also a manual method of copying songs from your iPod to a Mac or PC. The procedure is a bit involved and won't recover playlists but if you're interested it's available on page 2 at this link: Copying Content from your iPod to your Computer - The Definitive Guide

How to remove switches from a fabric.

We have a couple of MDS9120's and a SUP1 9509 in our fabric that we want to retire.   I'm pretty sure that I don't want to just shut down these switches, unplug the cables and call it good.   Also the 9509 is the principal for two of our larger VSAN's and one of the 9120's is a principal for another that we are still using. Also, this same used to have an IVR zoneset which I think is gone, at least I don't see it when I look at IVR. Current all the switches in the fabric are running 3.31c code. Since we are planning moving to the 4.x we want remove these since they will not be supported.
So, what is the procedure to make another switch the principal of a VSAN, and once a switch is no longer a principal what is the procedure for cleanly removing it from the fabric?     If someone has some insights or can point to me to documentation that covers this, it would be greatly appreciated.
Thanks,
Jeff Blomendahl
University of Kansas Medical Center

In case anyone is still interested, I opened a TAC case on this because I could see that the information was all out there, but I wanted to make sure that I didn't miss anything that would bite me. It turnes out that it wasn't that big of a deal if you do it correctly.
To remove a switch that is the principal for a VSAN, as was mention earlier in this thread, you need to give it a lower priority and give the switch that you want to make the principal the highest priority. In our case, the "old" switch had a priority of 1 for 3 of our VSANs, so I changed it to the default of 128 and on the switch that was to be the "new" principal, the priority was set to 1. Assuming that you are in config mode on the switch, the commands from the CLI looked like this:
On the "old" switch:
fcdomain priority 128 vsan xx   (xx being the number of the VSAN, this sets the switch priority to the default of 128)
fcdomain restart xx     (again, xx being the number of the VSAN, This will non-disruptively restart the vsan on the switch and change the priority. Be aware that if you are using static domain ID's the restart may be disruptive on the switch, check the documention for more on this)
On the "new" switch:
fcdomain priority 1 vsan xx   (xx being the number of the VSAN, this sets the switch priority to the highest priority, 1)
fcdomain restart xx     (again, xx being the number of the VSAN, This will non-disruptively restart the vsan on the switch and change the priority. Be aware that if you are using static domain ID's the restart may be disruptive on the switch, check the documention for more on this)
Do this for every VSAN that the "old" switch is the principal and also on the "new" switch that is to be the principal. From what I saw in the Domain Manager this will change the priority but won't necessarily change the principal assignment. At this point the "old" switch is ready to be removed from the fabric. Obviously, since this switch was the principal, you'll want to make sure that all of the zoneset information for those zones has been replicated to the other switches in the fabric, particularly to the switch that is to become the new principal. Other than an ISL to the rest of the fabric and the connections to the management ports, there was nothing connected to the "old" switch.
At this point you can shutdown the ISL to the "old" switch from the switch that is on the other end of the ISL. At this point you will see the fabric segment (as viewed from Fabric Manager) At this point, I unplugged the management cables from the "old" switch, since I didn't want it talking to the Fabric Manager anymore. I purged the switch and after about 5 or 10 minutes the segmentation went away and the fabric returned to normal, less the "old" switch.    There was no disruption to any of the 240+ hosts that were on the affected VSANs and the switch with the priority of 1 became the principal just like it was supposed to.
I think that once the ISL has been brought down, you want to take the switch off of the network or shut it down so that it can't continue to talk to the FM. If this isn't done, FM will see that there are VSANs on that switch that are disconnected from the rest of the fabric and will show that the fabric is segmented. I went through this procedure successfully on a SUP1 MDS 9509 and a MDS 9120 that were running 3.3.1 code. One thing that did make my heart stop for a second was when I went to look at the zonesets after the segmentation cleared up. The zonesets were there, but the zones were gone!   Since my pager wasn't vibrating out of the holster, I reasoned that the zones were still there.   A quick look at the configs on the switches confirmed this. What had happened, was that the switch that I removed was the seed switch for FM when it discovered the fabric. To correct this I restarted FM and rediscovered the fabric using the "new" principal switch as the seed switch, and all of the zones were back were they were supposed to be.
Just for your piece of mind (read CYA), I recommend opening a TAC case just to have them look over your configs and make any recommendations. In our case, we had to remove IVR from one of our switches and the engineer pointed out a bug that can occur when removing IVR, and a work around for this bug.
Sorry for the long post, but I hope that this information is helpful to someone else that has to do this.
Jeff Blomendahl
Enterprise Systems Engineer
University of Kansas Medical Center

Switching from write through to write behind automatically

Hi,
We are considering a Coherence solution to protect a customer facing application from outages due to database failures. This is for a financial company and the monetary value of each transaction is large and we want to provide 100% guarantee against data loss while not incurring any outages. We want to provide a write-through persistence to the database through Coherence which can switch to a write-behind automatically at runtime if the database persistence fails. Is this doable automatically and would it solve the problem I am trying to solve without losing any inflight transactions? Are there any real customer cases that were successful in achieving this using Coherence?
Thanks
Sairam
Edited by: SKR on Feb 16, 2012 3:14 PM
Edited by: SKR on Feb 16, 2012 3:15 PM

SKR wrote:
Jonathan.Knight wrote:
Hi Sairam
I know you can change the write-delay in JMX for a cache using write-behind but I pretty certauin you cannot make a write-through cache suddenly become a write-behind cache.
I'm not sure why you think changing from write-through to write-behind will allow you to guarantee 100% no data loss - do you mean no loss of updates to the DB or no loss of data in the cache cluster? There are certainly scenarios that can occur where you can loose data from either the cluster or the DB that write-through or write-behind will not save you from. Presumably you want to use write-behind to allow for the DB to go down, although you will still need to configure Coherence to properly retry failed write-behind calls CacheStore behaviour on failure. What happens to your data if you are using write-behind and you loose a partition from you cluster (i.e. you loose a physical machine or two or more JVMs in a short space of time) - you have data loss - you cannot guarantee against this you can only mitigate it and have a recovery policy/procedure.
JKJK,
Thanks for your reply. I must have explained the scenario better. What we are trying to do is to have our transactions commit to the database synchronously using write-through, so that during normal operation, the data will be committed, persisted and durable in the database. But our RW database becomes a single point of failure and if some problem occurs to the database during the peak load time, we run the risk of an outage till we fix the database problem or failover to the standby (We don't have RAC architecture or automatic failover and the manual switchover takes about 10 - 15 mins minimum). We want to avoid this by providing a cache-only operation mode during such a failure, where the customers can continue to transact and the writes will get queued in the cache. I do understand that losing both the database and the cache or losing the primary and the backup in the cache would result in a data loss. But I am assuming such a dual failure is rare.
We do not want to run write-behind all the time but only during the database failure window. From what you mentioned, it seems the runtime switching from write-through to write-behind is not available as an option.
SairamHi Sairam,
I would suggest that you configure write-behind to have a fairly short write-delay, and you only return a confirmation to the client
- either after the write-behind succeeded (you can use a backing map listener to listen for the removal of the decoration which meant that the entry was dirty)
- or if the database went down (noticeable from the failure), then it is up to you whether you send a confirmation which also mentions that it is not persisted to disk yet, or not at all
Best regards,
Robert

ECC Client switch to SCM 7.0

Hello,
We are planning to switch our ECC Development client from 120 to 130 which is already connected to SCM system and has data related to ECC 120.
When switch the ECC client from 120 to 130 and run the Integration Models again, what are possibilities of SCM system data to become junk or Inconsistent?
1). SCM data needs to be scrambled before we run the Integraion Models from New client?
2). SCM data gets appended with new Data from new client?
Kindly provide your views...
Thanks,
Arjun

Arjun
It depends on which modules of SCM you are using. If you are using DP integrated with a BI system, the Infocubes/ Time Series Data could be inconsistent after switching. If you are using GATP with Product Allocation (again due to DP/ BI linkage), you could have the same issue.
Other than that you might be ok if you simply do CIF initialize (RIMODINI) and also do a Transaction data reconciliation (/SAPAPO/CCR).
As far as possible, my opinion is that it is always better to rebuild the SCM system everytime the connected ECC client changes rather than attempt to clean it. The reason is that should anything look funny in Development (either due to an enhancement or while testing standard functionality), you will always be thinking in the back of your mind that it might be due to the client switching. The fewer wild cards you introduce in your development environment, the better off your testing.
Rishi Menon

How to switch from legacy to native Android app with minimal interruption

It's gotten to the point where I'm recommending that my client switch their DPS app for Android from legacy to native. Can anyone offer any insight into the process of changing that over for an existing app? Most of the Adobe support documents are written for starting a new app in native format. I need to give the client an idea of how the transition will affect existing subscribers on the Android platform (i.e. will they need to download a new app, or will it work as an update) and what we can do to retain readers if they do need to download an entirely new app.
Complicating the situation is that the client likely will want to keep the legacy app as long as we can to continue offering it on Amazon, because Kindle devices account for 60 percent of our non-iOS downloads.
Thank you!

To replace the existing legacy viewer, simply use the same Bundle ID used in the legacy app when you build the native Android viewer, and then submit the app as a new version in the Google Play Developer Portal. To locate the Bundle ID for the legacy viewer, open the desktop version of DPS App Builder and look at the list of apps. It might include a .air prefix, depending on when the app was built. If it does, use the .air prefix when you specify the Bundle ID for the native viewer, even though it's not an AIR app. The Bundle ID just needs to be the same. If you want two separate apps--which I don't recommend--use a different Bundle ID and submit it in the Developer Portal as a new app.
The Amazon app is a different app that's unrelated to the Google Play app. You can continue to leave the app in the Amazon Appstore.

Switch from MS exchange to OS X server 10.5.4 running mail

we have switched from MS Exchange server 2003 to mac os x 10.5.4 server.
I have set up mail on this. The client connects ok, and the server gets mail, but no mail gets through the server, neither in nor out.
Reason: Remote SMTP server has rejected address
Diagnostic code: smtp;554 5.7.1 <[email protected]>: Relay access denied
command_directory = /usr/sbin
config_directory = /etc/postfix
content_filter = smtp-amavis:[127.0.0.1]:10024
daemon_directory = /usr/libexec/postfix
debugpeerlevel = 2
enableserveroptions = yes
html_directory = no
inet_interfaces = all
mail_owner = _postfix
mailboxsizelimit = 0
mailbox_transport = cyrus
mailq_path = /usr/bin/mailq
manpage_directory = /usr/share/man
messagesizelimit = 10485760
mydestination = $myhostname,localhost.$mydomain,localhost,metropolis.local
mydomain = metropolis.no
mydomain_fallback = localhost
myhostname = bigapple.metropolis
mynetworks = 127.0.0.0/8,192.168.168.0/24,127.0.0.0/24
newaliases_path = /usr/bin/newaliases
queue_directory = /private/var/spool/postfix
readme_directory = /usr/share/doc/postfix
relayhost =
sample_directory = /usr/share/doc/postfix/examples
sendmail_path = /usr/sbin/sendmail
setgid_group = _postdrop
smtpdpw_server_securityoptions = gssapi
smtpdrecipientrestrictions = permitsasl_authenticated,permit_mynetworks,reject_unauthdestination,permit
smtpdsasl_authenable = yes
smtpduse_pwserver = yes
unknownlocal_recipient_rejectcode = 550

In Server Admin -> Mail -> Settings change the hostname from bigapple.metropolis to bigapple.metropolis.no
Next add metropolis.no to local host aliases in Server Admin -> Mail -> Settings -> Advanced -> Hosting
HTH,
Alex

Painless switch from PC to MAC

As many people do so, i will be making the switch from PC to MAC in 2009.
Since i want to do this as painless as possible, i want to be prepared as good as possible. I already found some information about licensing but i'm also much concerned about the technical issues.
- Creative Suite CS2 / Photoshop CS3 : can i take all my actions, custom settings, brushes etc to the other side? All compatible. Concerning third-party plugins i know i will have to contact them seperately
Working a lot in Indesign and Illustrator, i expect to have many Font issues. Any advice on this?
- Lightroom: i have 5 collections and some 100,000 photos in DNG, JPEG and PSD format on 3 different (internal and external) drives. I backup on another external drive. I'm concerned making the switch, Lightroom's database will either not be compatible or will not take along all settings (presets, keywords, sets, etc).
- color consistency / calibration. I know the colors displayed on my current monitor are correct. Can I expect differences when displaying my photos on a mac?
Anything else I have to think about? I don't want to lose years of work neither spend weeks switching from one platform to the other. Any advice is really welcome.

Mr. Isaacs,
Please note this definition of the word misinformation:
"False or inaccurate information, esp. that which is deliberately intended to deceive..."
I am not a lawyer, and you might not be either: but when I am repeatedly given misinformation by representatives of a corporation, I must consider the possibility of fraudulent behavior. Whether or not the persons giving out the misinformation are employees or outsourced contractors is immaterial to me; the ultimate responsibility lies with Adobe's management.
Here's another example for you of misinformation. I discovered yesterday (after quite a bit of searching) that Adobe Acrobat Pro for Mac does not include the application LiveCycle Designer. However, when I looked at the product description on the Store page, I saw no mention that this is a Windows-only feature:
From http://www.adobe.com/products/acrobatpro/features/:
"Create dynamic forms
Use Adobe LiveCycle Designer, a professional form design tool included with Acrobat 9 Pro, to further customize and automate dynamic XML forms."
I have several forms that I have created for clients using LiveCycle Designer. However, now that I have a Mac, I will be unable to edit those forms in Acrobat Pro, which I purchased as part of Creative Suite. From Help files http://help.adobe.com/en_US/Acrobat/8.0/Professional/help.html?content=WS58a04a822e3e50102 bd615109794195ff-7dfd.html:
In Windows, you can use LiveCycle Designer to edit forms that were created in Acrobat, but Acrobat can’t edit form fields that have been opened and saved in LiveCycle Designer.
So now I will need to purchase a full copy of Acrobat Pro for Windows ($449.00 USD) in order to continue to use the forms that I have created for my paying clients.
Just out of curiosity, I decided to ask a sales representative about whether or not LiveCycle Designer is included in the Mac version. I clicked the Chat button on the Acrobat Pro product page, and initiated a chat with "Randy." Here's the important bit of our conversation:
"Adrienne: Just to clarify, the Mac version of Acrobat Pro 9 does have LiveCycle designer included?
Randy: Yes."
"Randy" was only too eager to take my money then and there. Of course, if I had purchased Acrobat Pro 9, and once I opened, installed, and ran the software, I would have discovered that I did not in fact have LiveCycle Designer. I could then initiate a return, which would hopefully be completed within the three-week time frame specified.
I repeatedly requested that I be given an ID for the chat, either the representative's ID or a reference number for the chat. "Randy" told me he couldn't give me any "personal information," (I did not ask for his last name, just a way to identify him) but said I could email myself a copy of the chat. I entered my email address as instructed but never received a transcript of the chat.
I can only conclude two things from this experience:
One: Adobe's management of its Customer Service and Sales departments is incompetent;
OR
Two: Adobe is deliberately trying to deceive me, the customer, with "bait and switch" tactics.
If it's the first case, then I am only too eager to stop buying products from a company that cannot manage its Support and Sales teams. If it's the second case, I must consider filing a complaint with the FTC.
Mr. Isaacs, if you were in my position, what do you think you would do?

Documentation on client switches from Informatica to ODI?

Similar Messages

Maybe you are looking for