@tigerknee That seems an over complicated stuff to do. The problem with ES running at same time as X.org was because input devices losing controll. I don't know if that is still true. Does it work fine, while the desktop is still running, like playing games and return to the desktop?

@dankcushions Thanks so much!

@markyh444 said in Pi 3B. Installed Pixel UI but 'SD Card Copier' is missing under Accessories? Help please.:

@njweb Win32DiskImager is perfect for backing up your Pi. Most people on here use it, and I've made about 10 copies of my SD cards over the years when building and testing new things out in various projects.

I'd highly recommend ditching whatever image came with your Pi though and starting with the base Retropie from the site. If you run into more problems and ask for help here it wont be supported, plus nobody will know what has been done to the image before it was sold to you to try and help you if we can.

If you are happy with tinkering and exploring things for yourself though, you wont be disappointed with starting from the image on this site and making it your own!

Good point, thanks. Just concerned with potential compatibility issues with EmulationStation and installed emulators, settings etc. if I upgrade Retropie (will look up steps again).

@doubleeuroz It's been a while since I installed this way but I'm almost sure that synaptic is included when you install the LXDE/PIXEL Desktop on top of Raspbian Lite.

I switched to CrunchBang... works fine now.

@buzz The main reason I wasn't using the official image is so that I can use the box for multiple purposes--I can launch mate desktop with startx or launch retropie after I've logged in. I'm building a palmtop/portable emulator. If it's pretty easy to set up the official image to do so, maybe I will just use the image--sure beats installing and compiling all the packages.

@raibura hi, did you ever find a solution for this?

Sorry for asking in such an old thread but you are the only person I have found with the same problem as me. Thank you

@mitu Oh I'm aware it's just a front end, I've tried doing RetroPie for my brother in law as a Christmas gift (which I got working easily enough).

And I didn't think to try Github's instructions, I guess I just assumed the main page would work. Tired and ready for bed. Thanks, I'll give it a shot later.

@jpod1003

Good to hear. What was the issue?

Hi, i'll just post the full list of edits that need to be completed, just in case someone stumbles on this thread in the future.

#i did the following not through ssh, but with a physical keyboard #enable root user sudo passwd root #logout of the user pi logout #Log back in as root #Rename user pi usermod -l newname pi #Rename the user's home directory usermod -m -d /home/newname newname #Rename group pi groupmod --new-name newname pi #Now logout and log back in as newname #Disable password prompt for sudo cd /etc/sudoers.d/ sudo mv 010_pi-nopasswd 010_newname-nopasswd sudo nano 010_Name-nopasswd # edit the name pi to newname #Double check newname has sudo privileges sudo visudo #Disable Root sudo passwd -l root #fix the getty autologin username or else stuck at boot sudo nano /etc/systemd/system/autologin@.service #search for the following line ExecStart=-/sbin/agetty --autologin pi --noclear %I $TERM. #smb.conf has pi user in the share definitions sudo nano /etc/samba/smb.conf #Change the es_systems.cfg folder paths cd /opt/retropie/configs/all/emulationstation/ cp es_systems.cfg es_systems.cfg.pi.bak sudo nano es_systems.cfg #Folder configs and everything below /opt/retropie/configs/ sudo chown -R newname:newname /opt/retropie/configs/ #Paths for game image files also need editing #Look in /opt/retropie/configs/all/emulationstation/gamelists/ #check fstab if you have mounted anything sudo nano /etc/fstab # If you installed Drastic all the containing files of /opt/retropie/emulators/drastic/ sudo chown -R Name:Name /opt/retropie/emulators/drastic/*

Figured I'd share the error I was getting. Firstly, you need to be using Python 3+ for the version of ansible.

sudo pip install ansible

Downloading/unpacking ansible Downloading ansible-2.4.1.0.tar.gz (6.7MB): 6.7MB downloaded Running setup.py (path:/tmp/pip-build-f2xlqxxd/ansible/setup.py) egg_info for package ansible no previously-included directories found matching 'ticket_stubs' no previously-included directories found matching 'hacking' Requirement already satisfied (use --upgrade to upgrade): jinja2 in /usr/local/lib/python3.4/dist-packages (from ansible) Requirement already satisfied (use --upgrade to upgrade): PyYAML in /usr/local/lib/python3.4/dist-packages (from ansible) Requirement already satisfied (use --upgrade to upgrade): paramiko in /usr/local/lib/python3.4/dist-packages (from ansible) Requirement already satisfied (use --upgrade to upgrade): cryptography in /usr/local/lib/python3.4/dist-packages (from ansible) Requirement already satisfied (use --upgrade to upgrade): setuptools in /usr/local/lib/python3.4/dist-packages (from ansible) Requirement already satisfied (use --upgrade to upgrade): idna>=2.1 in /usr/local/lib/python3.4/dist-packages (from cryptography->ansible) Requirement already satisfied (use --upgrade to upgrade): asn1crypto>=0.21.0 in /usr/local/lib/python3.4/dist-packages (from cryptography->ansible) Requirement already satisfied (use --upgrade to upgrade): six>=1.4.1 in /usr/local/lib/python3.4/dist-packages (from cryptography->ansible) Installing collected packages: ansible Running setup.py install for ansible changing mode of build/scripts-3.4/ansible from 644 to 755 changing mode of build/scripts-3.4/ansible-playbook from 644 to 755 changing mode of build/scripts-3.4/ansible-pull from 644 to 755 changing mode of build/scripts-3.4/ansible-doc from 644 to 755 changing mode of build/scripts-3.4/ansible-galaxy from 644 to 755 changing mode of build/scripts-3.4/ansible-console from 644 to 755 changing mode of build/scripts-3.4/ansible-connection from 644 to 755 changing mode of build/scripts-3.4/ansible-vault from 644 to 755 no previously-included directories found matching 'ticket_stubs' no previously-included directories found matching 'hacking' changing mode of /usr/local/bin/ansible to 755 changing mode of /usr/local/bin/ansible-doc to 755 changing mode of /usr/local/bin/ansible-galaxy to 755 changing mode of /usr/local/bin/ansible-connection to 755 changing mode of /usr/local/bin/ansible-console to 755 changing mode of /usr/local/bin/ansible-inventory to 755 changing mode of /usr/local/bin/ansible-vault to 755 changing mode of /usr/local/bin/ansible-playbook to 755 changing mode of /usr/local/bin/ansible-config to 755 changing mode of /usr/local/bin/ansible-pull to 755 Could not find .egg-info directory in install record for ansible Successfully installed ansible Cleaning up...

Looks good so far, but...

ansible --version

ERROR! Unexpected Exception, this is probably a bug: unsupported operand type(s) for %: 'bytes' and 'bytes' the full traceback was: Traceback (most recent call last): File "/usr/local/bin/ansible", line 85, in <module> mycli = getattr(__import__("ansible.cli.%s" % sub, fromlist=[myclass]), myclass) File "/usr/local/lib/python3.4/dist-packages/ansible/cli/__init__.py", line 38, in <module> from ansible.inventory.manager import InventoryManager File "/usr/local/lib/python3.4/dist-packages/ansible/inventory/manager.py", line 44, in <module> IGNORED_EXTS = [b'%s$' % to_bytes(re.escape(x)) for x in C.INVENTORY_IGNORE_EXTS] File "/usr/local/lib/python3.4/dist-packages/ansible/inventory/manager.py", line 44, in <listcomp> IGNORED_EXTS = [b'%s$' % to_bytes(re.escape(x)) for x in C.INVENTORY_IGNORE_EXTS] TypeError: unsupported operand type(s) for %: 'bytes' and 'bytes'

@kalimah You say you tried "a couple of ways" but don't detail these. Please provide more information. There is only one reliable way to manually install RetroPie on top of Raspbian and that is the official way. Please see docs

Thank you.

@buzz Awesome, thank you Buzz!

@dankcushions aah thanks so its just waiting for me now haha

@nowarrivinghere there is no ETA.

https://github.com/retropie/retropie-setup/wiki/Manual-Installation

Problem Solved:
It turns out it was a wiring problem: the A and B Buttons were crossed on the 2nd controller. It seems the system has no way of differentiating between the two otherwise identical controllers. So the config for controller 2 probably overwrote the config for controller 1 and vice versa each time a new controller config was put in.

@bengdahl Did you ever find a solution for this? I'm having the exact same problem.