Skip to main content

The Saga of EA Customer support part 4

So the last email said 48 hours for a response, So I waited a week, and honestly I'm starting to get a bit irate.

Jan 4, 2017 (13 days after the first contact)

So a week after my last communication, time for a new ticket.  In retrospect I should have updated one of the previous ones, maybe, but in so far the only response I received were the initial reply from the CSR that also closed the ticket. At 3:00 PM I put in a new ticket, again I don't have the language used but it was either a recap of the issue, or a request for an update on the previous tickets.

At 4:33 PM I received an exact copy of the previous message from EA, so no need to quote it here.

At 4:49 PM I replied with the following:
Thanks for the time it took to copy and paste a canned reply.  
It seems apparent after being dismissed twice that I will need to become a nuisance customer for this issue to be addressed.  
I will continue to re open this issue, submit duplicate issues, and fill out customer satisfaction surveys with the lowest marks possible until the original issue is addressed.
I look forward to our future business relationship of having many tickets dismissed, and clicking many dissatisfied radio buttons.
At this time I took the time to fill out the customer service surveys with the worst marks possible, and use the web interface to make sure that the tickets were still open.  I think I had made up in my mind that I would be opening a new ticket every 48 hours until this was resolved, it didn't quite work out that way.
Labels:

Comments

Post a Comment

Popular posts from this blog

8Bitdo NES 30 Pro on linux

This post will go over the setup I had to do to get my   8Bitdo  NES30 Pro controller working on my Arch linux desktop with steam.  This results in the system loading the xboxdrv automatically when the controller is connected, and unloading once finished. Firmware Update The first thing to tackle was the firmware update on the controller,  This may not be needed, but I like to keep my devices up to date. After some googling, I was able to find a program called fwupd  that's able to update the controller via a USB connection.  It's available for Arch in the community repo. The basic syntax of the command is: fwupdmgr get-devices fwupdmgr refresh fwupdmgr get-updatessudo fwupdmgr update The controller will need to be put into 'Firmware update mode'.  Be aware that the final command will also update all eligible firmware on your system, so If you don't want that, please dig into the documentation Bluetooth Connection Getting the controller co
1 comment
Read more

Craftware 1.17 on Arch Linux -- notes

Craftware a slicer for 3d printers is available for linux here .  It looks pretty good, and is supposedly multi threaded with support for hardware acceleration. I can only find it  as a deb file, and there's nothing in the AUR for it. I tried a few of the common methods for installing debs: debtap While it was able to create a package, upon installing it I got this error loading packages... error: failed to prepare transaction (package architecture is not valid) :: package craftware-1.17.1-1-i686 does not have a valid architecture So.. No good. I tried just extracting the package content, and running the binary: ./craftware: error while loading shared libraries: libomp.so: cannot open shared object file: No such file or directory and yes, it is installed. $ ldconfig -v           libomptarget.so -> libomptarget.so          libomp.so -> libomp.so          libzita-alsa-pcmi.so.0 -> libzita-alsa-pcmi.so.0.2.0 There is one thing that I
1 comment
Read more

Dropbox Nov 2018 workaround

So Dropbox is no longer supporting anything besides ext4 on linux as of Nov 7th 2018.  Here's how to work around that WITHOUT superuser permissions. First, create a sparse file of whatever size you'd like for your Dropbox folder. $ truncate -s 5G ~/.Dropbox.img Now we need to format this as ext4, But we want to make sure that we own the created file system, not the default of root. $ mkfs.ext4 -E root_owner=$(id -u $USER):$(id -g $USER) ~/.Dropbox.img Setup the loopback device with our EXT4 image $ udisksctl loop-setup -f ~/.Dropbox.img You may need to mount the device if it hasn't been already: $ udisksctl mount -b $CREATED_LOOP_DEVICE Check where our filesystem is mounted: $ mount | grep Dropbox.img Move any existing data from the previous dropbox folder to the new location: $ mv ~/Dropbox/{.,}* /$MOUNTPOINT/OF/DROPBOX/IMAGE/UUID$ Link our new folder back to the dropbox folder $ ln -s  /$MOUNTPOINT/OF/DROPBOX/IMAGE/UUID$/ ~/Dropbox You can now star
Post a Comment
Read more