-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wired DualShock4 controller no longer being recognized after upgrade to retroarch 1.10 on Ubuntu 20.04 #52
Comments
Hi, Is it still an issue with latest stable ? |
Unfortunately, it appears so. I've been on on |
For anyone else inconvenienced by this issue, here is my workaround in Ubuntu 20.04:
|
Hello, I've encountered this same issue with any game controllers since the version 1.10.0 update and the 1.10.2 update unfortunately did not fix this either. I also have the preload library error on startup and I can confirm that the library is placed in incorrect place inside the snap filesystem:
However as a not so great mitigation I can get controllers to work by unplugging and plugging them in while the retroarch is running. I think that might be related to something the preload is supposed to do but can't at the moment. |
I have the same issue. A Wii U Pro Controller works if I reconnect while the emulator is running, but I just can't get a Switch Pro Controller to be detected at all. Both controllers work with an old apt-get installable Retroarch version in Ubuntu. |
I too have the extract same issues with a Bluetooth PS3 controller. Controller is not detected if retro arch is launched and the controller is already on. Turning it off and on connects it. Then when running a core the controller is disconnected again. Turning it off and on again reconnects. Same when exiting a core. Seems only related to snap. I have plugged usb-raw, joystick, bluez no luck. |
I'm quite sure the root cause of this issue is tied to the preload library put in incorrect location. Shame that snap filesystems are immutable by design and debugging this issue would require installing the whole snap development and packaging environment which considerably raises the effort needed for casual debugging. |
Hi, Can you try to install it from edge channel (in about one hour) as we have just added one export ? It might help to solve this issue.
Thank you. |
Well,
Uh oh... if I go through the removal route it sounds very much like it's going to destroy my configuration (yet again). Fortunately refreshing (probably) did the trick:
The core version is now 1.10.3 but the problem is still present:
And the game controllers are not detected. |
You can backup your config files, mine are under USER/snap/retroarch/latest/.confg. I haven't had a chance to test the edge version. |
I pushed some more updates to the edge channel. It seems to have gotten rid of the preload error, so if the ds4 is still not working, they were probably not related. I'm going to hold off pushing these builds to the stable channel until I get confirmation that they help (or at least don't hurt) EDIT: anybody had a chance to test the latest edge build? |
I have just tested using a Wii U Pro Controller connected via Bluetooth. It still wasn't detected until reconnected. |
Ok, thanks for testing/reporting. I think we can safely assume the preload stuff is/was unrelated. As a bit of a sanity check, can anyone roll back to a previous version and verify that this is indeed a problem on our end and not something upstream (i.e., via snapcraft-core, etc.)? To do so, you need to list the versions installed on your system and then select one to roll back to:
|
Can confirm the preload stuff was unrelated. Just tested 1.10.3 and the preload error is now gone but the issue with controllers remains. I was unable to get a previous version list to rollback to using
The options available are 1.10.2 and 1.10.3. .2 is already to confirmed to have the issue. If anyone else has older versions previously installed to test that would be great. |
Yes, I can also confirm this. The preload error is now fixed 1.10.3 - 1365 build but the controller issue remains.
If there is a way to rollback to a version 1.9.x snap then this could be tested but so far the rollback does not promising:
|
I was wondering if this could have any connection to the connected interfaces, does it? For testing, I ran this command to get all interfaces that Yuzu uses but Retroarch doesn't:
The only interesting entries here would be hardware-observe and mount-observe, even though I do not know their exact purposes. |
desktop-legacy could be another possibility, I guess /shrug You could try connecting them and see if it improves anything. |
When I try to manually connect any interface, I get errors:
|
I just added desktop-legacy to the plugs. It should be available in the next edge build: https://github.com/libretro/retroarch-snap/blob/master/snapcraft.yaml#L58 |
Also I noticed that the "reconnecting controller after starting retroarch" mitigation is not that great as the controller is lost every time you launch content using a core. |
Is there an estimate of when a new build will be uploaded? |
It looks like it does them automatically every 3 days and they just did a new build yesterday, but I went ahead and triggered a new one. It'll probably publish in the next 30 min to an hour. |
So a build was released and I was able to connect If it helps in any way, here's the Yuzu yaml file for reference/comparison: https://github.com/Nightmayr-snaps/yuzu-snap/blob/master/snap/snapcraft.yaml |
Now that a new permission was mentioned I wonder if something broke in the retroarch or the snap itself? |
Hmm... retroarch does not have |
alright, i tried adding hardware-observe, mount-observe and browser-support. None of those sound at all related based on their documentation, but whatever. We'll give it a shot :) New builds should publish in an hour or so. |
Yeah, no changes coming from the connections... :( |
Thanks for checking. |
I migrated to Ubuntu 22.04 and I can say that this issue is at least consistent: same controller problem with the snap. I finally gave up and installed the PPA version and everything just worked nicely out of the box and the settings were easy to migrate. |
Yeah this is still occurring. I've just given up on retroarch and am not using it. Not sure even where to start looking to resolve this. |
I can't reproduce the issue with fresh install on Ubuntu 22.04. Some logs
|
@exerf @haydnjonesdesign @xard-dev Do you reproduce the issue using Ubuntu 22.04 ? |
Negative. Debian Buster. |
@haydnjonesdesign I made some test on Debian Buster and it is working if you unplug then plug the controller when RetroArch is launched. I enabled the
Here is the log for the Apparmor when I unplug and plug the controller when RA is launched :
Moreover, the profile for RetroArch snap is well activated
|
Thanks Gouchi. I’m a bit busy these days but will eventually get around to testing it. Obviously, I guess the end goal is to have it work without the need to unplug/plug.
… On 2 Oct 2022, at 9:53 pm, gouchi ***@***.***> wrote:
@haydnjonesdesign <https://github.com/haydnjonesdesign> I made some test on Debian Buster and it is working if you unplug then plug the controller when RetroArch is launched.
<https://user-images.githubusercontent.com/7869503/193450400-498950f4-71b5-4130-8e8e-7432c3112514.png>
I enabled the raw-usb interface but it did not help.
snap connections retroarch
Interface Plug Slot Notes
alsa retroarch:alsa - -
audio-playback retroarch:audio-playback :audio-playback -
bluez retroarch:bluez - -
browser-support retroarch:browser-support :browser-support -
desktop retroarch:desktop :desktop -
desktop-legacy retroarch:desktop-legacy :desktop-legacy -
hardware-observe retroarch:hardware-observe - -
home retroarch:home :home -
joystick retroarch:joystick :joystick -
mount-observe retroarch:mount-observe - -
network retroarch:network :network -
network-bind retroarch:network-bind :network-bind -
opengl retroarch:opengl :opengl -
raw-usb retroarch:raw-usb - -
removable-media retroarch:removable-media - -
screen-inhibit-control retroarch:screen-inhibit-control :screen-inhibit-control -
unity7 retroarch:unity7 :unity7 -
wayland retroarch:wayland :wayland -
x11 retroarch:x11 :x11 -
sudo snap connect retroarch:raw-usb
snap connections retroarch
Interface Plug Slot Notes
alsa retroarch:alsa - -
audio-playback retroarch:audio-playback :audio-playback -
bluez retroarch:bluez - -
browser-support retroarch:browser-support :browser-support -
desktop retroarch:desktop :desktop -
desktop-legacy retroarch:desktop-legacy :desktop-legacy -
hardware-observe retroarch:hardware-observe - -
home retroarch:home :home -
joystick retroarch:joystick :joystick -
mount-observe retroarch:mount-observe - -
network retroarch:network :network -
network-bind retroarch:network-bind :network-bind -
opengl retroarch:opengl :opengl -
raw-usb retroarch:raw-usb :raw-usb manual
removable-media retroarch:removable-media - -
screen-inhibit-control retroarch:screen-inhibit-control :screen-inhibit-control -
unity7 retroarch:unity7 :unity7 -
wayland retroarch:wayland :wayland -
x11 retroarch:x11 :x11 -
Here is the log for the Apparmor when I unplug and plug the controller when RA is launched :
Oct 02 09:56:42 debian kernel: usb 2-1.2.4.3.1: USB disconnect, device number 14
Oct 02 09:56:44 debian kernel: usb 2-1.2.4.3: reset high-speed USB device number 13 using ehci-pci
Oct 02 09:56:44 debian kernel: usb 2-1.2.4.3: USB disconnect, device number 13
Oct 02 09:56:44 debian kernel: usb 2-1.2.4.3: new high-speed USB device number 15 using ehci-pci
Oct 02 09:56:44 debian kernel: usb 2-1.2.4.3: New USB device found, idVendor=05e3, idProduct=0608, bcdDevice=88.32
Oct 02 09:56:44 debian kernel: usb 2-1.2.4.3: New USB device strings: Mfr=0, Product=1, SerialNumber=0
Oct 02 09:56:44 debian kernel: usb 2-1.2.4.3: Product: USB2.0 Hub
Oct 02 09:56:44 debian kernel: hub 2-1.2.4.3:1.0: USB hub found
Oct 02 09:56:44 debian kernel: hub 2-1.2.4.3:1.0: 4 ports detected
Oct 02 09:56:44 debian upowerd[1752]: treating change event as add on /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2.4/2-1.2.4.3
Oct 02 09:56:45 debian upowerd[1752]: treating change event as add on /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2.4/2-1.2.4.3
Oct 02 09:56:45 debian upowerd[1752]: treating change event as add on /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2.4/2-1.2.4.3
Oct 02 09:56:45 debian kernel: usb 2-1.2.4.3.1: new full-speed USB device number 16 using ehci-pci
Oct 02 09:56:45 debian kernel: usb 2-1.2.4.3.1: New USB device found, idVendor=054c, idProduct=09cc, bcdDevice= 1.00
Oct 02 09:56:45 debian kernel: usb 2-1.2.4.3.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Oct 02 09:56:45 debian kernel: usb 2-1.2.4.3.1: Product: Wireless Controller
Oct 02 09:56:45 debian kernel: usb 2-1.2.4.3.1: Manufacturer: Sony Interactive Entertainment
Oct 02 09:56:45 debian kernel: input: Sony Interactive Entertainment Wireless Controller Touchpad as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2.4/2-1.2.4.3/2-1.2.4.3.1/2-1.2.4.3.1:1.3/0003:054C:09CC.0007/input/input29
Oct 02 09:56:45 debian kernel: input: Sony Interactive Entertainment Wireless Controller Motion Sensors as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2.4/2-1.2.4.3/2-1.2.4.3.1/2-1.2.4.3.1:1.3/0003:054C:09CC.0007/input/input30
Oct 02 09:56:45 debian kernel: input: Sony Interactive Entertainment Wireless Controller as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2.4/2-1.2.4.3/2-1.2.4.3.1/2-1.2.4.3.1:1.3/0003:054C:09CC.0007/input/input28
Oct 02 09:56:45 debian kernel: sony 0003:054C:09CC.0007: input,hidraw3: USB HID v81.11 Gamepad [Sony Interactive Entertainment Wireless Controller] on usb-0000:00:1d.0-1.2.4.3.1/input3
Oct 02 09:56:45 debian mtp-probe[4641]: checking bus 2, device 16: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2.4/2-1.2.4.3/2-1.2.4.3.1"
Oct 02 09:56:45 debian mtp-probe[4641]: bus: 2, device: 16 was not an MTP device
Oct 02 09:56:45 debian systemd[1]: Starting IIO Sensor Proxy service...
Oct 02 09:56:45 debian systemd[1]: Started IIO Sensor Proxy service.
Oct 02 09:56:45 debian systemd-udevd[4616]: controlC1: Process '/usr/sbin/alsactl -E HOME=/run/alsa -E XDG_RUNTIME_DIR=/run/alsa/runtime restore 1' failed with exit code 99.
Oct 02 09:56:45 debian systemd[1]: iio-sensor-proxy.service: Succeeded.
Oct 02 09:56:45 debian mtp-probe[4672]: checking bus 2, device 16: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2.4/2-1.2.4.3/2-1.2.4.3.1"
Oct 02 09:56:45 debian mtp-probe[4672]: bus: 2, device: 16 was not an MTP device
Oct 02 09:56:45 debian upowerd[1752]: treating change event as add on /sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2.4/2-1.2.4.3/2-1.2.4.3.1/2-1.2.4.3.1:1.3/0003:054C:09CC.0007/power_supply/sony_controller_battery_a4:53:85:62:9e:a9
Oct 02 09:56:45 debian rtkit-daemon[1480]: Supervising 7 threads of 3 processes of 1 users.
Oct 02 09:56:45 debian rtkit-daemon[1480]: Successfully made thread 4673 of process 1431 owned by '1000' RT at priority 5.
Oct 02 09:56:45 debian rtkit-daemon[1480]: Supervising 8 threads of 3 processes of 1 users.
Oct 02 09:56:45 debian rtkit-daemon[1480]: Supervising 8 threads of 3 processes of 1 users.
Oct 02 09:56:45 debian rtkit-daemon[1480]: Successfully made thread 4674 of process 1431 owned by '1000' RT at priority 5.
Oct 02 09:56:45 debian rtkit-daemon[1480]: Supervising 9 threads of 3 processes of 1 users.
Oct 02 09:56:51 debian audit[4512]: AVC apparmor="DENIED" operation="open" profile="snap.retroarch.retroarch" name="/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2.4/2-1.2.4.3/2-1.2.4.3.1/2-1.2.4.3.1:1.3/0003:054C:09CC.0007/power_supply/sony_controller_battery_a4:53:85:62:9e:a9/scope" pid=4512 comm="retroarch" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Oct 02 09:56:51 debian audit[4512]: AVC apparmor="DENIED" operation="open" profile="snap.retroarch.retroarch" name="/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2.4/2-1.2.4.3/2-1.2.4.3.1/2-1.2.4.3.1:1.3/0003:054C:09CC.0007/power_supply/sony_controller_battery_a4:53:85:62:9e:a9/status" pid=4512 comm="retroarch" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Oct 02 09:56:51 debian kernel: audit: type=1400 audit(1664704611.640:49): apparmor="DENIED" operation="open" profile="snap.retroarch.retroarch" name="/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2.4/2-1.2.4.3/2-1.2.4.3.1/2-1.2.4.3.1:1.3/0003:054C:09CC.0007/power_supply/sony_controller_battery_a4:53:85:62:9e:a9/scope" pid=4512 comm="retroarch" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Oct 02 09:56:51 debian kernel: audit: type=1400 audit(1664704611.640:50): apparmor="DENIED" operation="open" profile="snap.retroarch.retroarch" name="/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2/2-1.2.4/2-1.2.4.3/2-1.2.4.3.1/2-1.2.4.3.1:1.3/0003:054C:09CC.0007/power_supply/sony_controller_battery_a4:53:85:62:9e:a9/status" pid=4512 comm="retroarch" requested_mask="r" denied_mask="r" fsuid=1000 ouid=0
Moreover, the profile for RetroArch snap is well activated
sudo aa-status
apparmor module is loaded.
6 profiles are loaded.
6 profiles are in enforce mode.
/snap/snapd/17029/usr/lib/snapd/snap-confine
/snap/snapd/17029/usr/lib/snapd/snap-confine//mount-namespace-capture-helper
/usr/lib/snapd/snap-confine
/usr/lib/snapd/snap-confine//mount-namespace-capture-helper
snap-update-ns.retroarch
snap.retroarch.retroarch
0 profiles are in complain mode.
0 processes have profiles defined.
0 processes are in enforce mode.
0 processes are in complain mode.
0 processes are unconfined but have a profile defined.
—
Reply to this email directly, view it on GitHub <#52 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKC564R6HVTHJY3PNZE7E53WBFSTJANCNFSM5MSFOXDA>.
You are receiving this because you were mentioned.
|
FWIW, I'm still having the same behavior after updating to 22.04.1. |
Ok, I finally got a setup where I can build snaps on-demand and I went all the way back to 1.9.3 and it's still doing this controller thing, so I'm beginning to suspect that it' s nothing inside of RetroArch and is instead related to something within snap/craft. |
Thanks Hizzlekizzle. I think I felt that it was related to an interface issue but it's all above my knowledge. |
Hmm, I just learned that this issue is affecting the FlatPak package, as well, and that switching the controller driver to sdl2 prevents the disconnection in between games (though it doesn't prevent having to unplug/replug at first launch). |
This should minimize the impact of #52
Doesn't work for me (snap package, Ubuntu 22.04). Still need to replug every time with sdl2 input driver. |
I will comment in this thread, because it is not closed. It stopped recognizing the Xbox 360 controller. This happened recently, maybe 20 days ago. I have Ubuntu 22.04 and RetroArch 1.16.0 on snap. Log:
|
After
snapd
automatically updated my version ofretroarch
to 1.10.0, my gamepad stopped working. I use a DualShock4 controller wired into USB. Historically, I have always used the "x" input driver and "udev" controller driver.Here is how the problem manifests:
In previous versions of
retroarch
(1.9.x), upon launchingretroarch
I would get a notification at the bottom of the screen stating that my DualShock4 controller had been detected. That notification no longer appears.Previously, I could use my controller to navigate the retroarch GUI, but now I can't.
In Settings -> Input -> Port 1 Controls, the Device Index is "Disabled" with no other available options.
When I try to re-map the buttons on the controller, the dialog box times out.
More observations:
I know that Ubuntu still recognizes my DS4 because I can use it outside of
retroarch
, which rules out something like a problem with my USB cable.I did a
diff
of the current activeretroarch.cfg
file against a recent backup copy, and the only changes appear to be new lines corresponding to new settings introduced by 1.10.0.I tried using other controller drivers. The only one I could get to work -- that is, the only one that allowed me to re-map buttons via the Settings -> Input -> Port 1 Controls screen -- was "linuxraw". But I couldn't get "linuxraw" to allow me to use my left analog stick to act as a D-pad, which is how the controller just naturally worked before (or perhaps because of the Analog to Digital Type setting). And using "linuxraw" didn't cause the controller notifications to reappear upon launching
retroarch
.Previous versions of
retroarch
would print the following lines to the log:But now, the log only contains:
After the update to 1.10.0, I tried running both the Update Assets and Update Controller Profiles commands. Neither had any noticeable effect.
Any idea what might have caused the problem, or how I might troubleshoot or fix?
Thanks in advance.
UPDATE: Oh, and one more thing. Ever since the upgrade to 1.10.0, when launching
retroarch
I now get the following error message on the command line (although it doesn't seem to preventretroarch
from running):It may be unrelated to the controller detection issue, but I thought I'd mention it anyway.
UPDATE2: To the extent that the above
ld.so
error is something that needs to be fixed, it would appear that something is looking forlibsnapcraft-preload.so
in the wrong location. It appears to reside inusr/lib/libsnapcraft-preload.so
, notlib/libsnapcraft-preload.so
.The text was updated successfully, but these errors were encountered: