Skip to main content

The Saga of EA Customer support part 3

Dec 27, 2016 (5 days after the original contact)

At this point in the saga I can't recall my resoning at the time, it may be the note at the end of the first contact that the issue was marked as closed on their end, and maybe with the loss of this second hero it was worth another ticket, so I opend a second ticket.  I don't have the language I used in this ticket at hand, from what I recall it was the previous email I had sent with some additonal clarifications. That was sent at at 9:18 AM.

Dec 28, 2016 (5 days after the original contact)

I recieved a reply to my second ticket, Here it is:
Thank you for contacting Electronic Arts Customer Experience.
I’ve checked your contact history, and found that there is another support request awaiting in our queue for the same issue. The reference number on the pre-existing request is #<27726519 >. I would like to inform you that our specialist team is working on the issue, and they will get back to you at the earliest. 
When opening a new support request with the same query which could cause further delays in resolving the issue. Therefore, I am closing this duplicate request. 
In order to get an updated or further assistance on your query/case, please use your pre-existing incident.
For your reference, to access all current support requests associated with your account, please follow the mentioned steps: 
1. Go to help.ea.com
2. Click on the ‘My Questions’ link on the top left-hand corner of the page (under the ‘My Stuff’ section)
3. Our website will prompt you to log in to your EA account.
4. If you have multiple EA accounts, use the screen name associated with this support incident
5. You should now see the ‘My Questions’ page, where all open support requests should be listed. 
Clicking on the subject of the support request will open its details. From the details page, you can update your pre-existing incident if you require further assistance. 
Due to the high number of requests we receive, it often takes 48 hours to respond to requests. If you do not hear from our team, you may re - open your request by replying with the same case number. 
I appreciate your patience on this. 
Should you have any further questions regarding this or any other issues, please do not hesitate to let us know. You can also find answers to common questions on our Help Center at "http://help.ea.com" or ask our community experts by visiting Answer HQ at “http://answers.ea.com"
Okay, fair enough,  I guess I'm being impacient It's still around Christmas and new years and all that, lets give them some time to get things sorted out.  I'm sure I'll get a responce to my original request in short order.

Or well, I was...
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 G...
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          libzit...
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