linux cant detect my remote

40 minutes ago, OnSteamDeck said:

linux cant detect my remote

Use sudo

 

11 hours ago, jason said:

Use sudo

 

(skip-app:75918): GLib-GIO-CRITICAL **: 09:07:40.517: g_dbus_proxy_new_sync: assert
ion 'G_IS_DBUS_CONNECTION (connection)' failed
/usr/lib/libproxy/libpxbackend-1.0.so: undefined symbol: g_strv_builder_unref
Failed to load module: /usr/lib/gio/modules/libgiolibproxy.so
/usr/lib/gio/modules/libgiognomeproxy.so: undefined symbol: g_task_set_name
Failed to load module: /usr/lib/gio/modules/libgiognomeproxy.so
/tmp/.mount_skip_aG37KMr/usr/lib/libgnutls.so.30: version `GNUTLS_3_6_3' not found
(required by /usr/lib/gio/modules/libgiognutls.so)
Failed to load module: /usr/lib/gio/modules/libgiognutls.so

** (WebKitWebProcess:75960): WARNING **: 09:08:05.913: atk-bridge: get_device_event
s_reply: unknown signature

** (skip-app:75918): WARNING **: 09:08:07.889: atk-bridge: get_device_events_reply:
unknown signature
Gtk-Message: 09:10:00.085: GtkDialog mapped without a transient parent. This is dis
couraged.

 

3 hours ago, jason said:

Did the public version work and not this one? Are you on a steam deck?

Neither version. newest beta or the public release are working properly.

Yes, As my user name says on Steam Deck.

5 minutes ago, OnSteamDeck said:

Neither version. newest beta or the public release are working properly.

Yes, As my user name says on Steam Deck.

My primary linux machine is a steamdeck. I don't have any issues. Did you change anything, are you running a a different desktop environment than the default KDE? etc.

 

2 hours ago, jason said:

My primary linux machine is a steamdeck. I don't have any issues. Did you change anything, are you running a a different desktop environment than the default KDE? etc.

 

I haven't changed anything to my knowledge. The only thing I had to do is reinstall steam OS once.

6 hours ago, OnSteamDeck said:

I haven't changed anything to my knowledge. The only thing I had to do is reinstall steam OS once.

@jasonam I missing important libs to run and connect the Skip 1s remote somehow? How do I fix?

59 minutes ago, OnSteamDeck said:

@jasonam I missing important libs to run and connect the Skip 1s remote somehow? How do I fix?

I think the lib errors and warnings you can ignore, it's normal. Just to be clear, if you double click it, does it launch the GUI?

If it does, can you attach the remote. Then create support files and attach them here. I'll look at the logs. It should have an error that will give us a clue.

12 hours ago, jason said:

I think the lib errors and warnings you can ignore, it's normal. Just to be clear, if you double click it, does it launch the GUI?

If it does, can you attach the remote. Then create support files and attach them here. I'll look at the logs. It should have an error that will give us a clue.

it launches the GUI. how do i create support files?

flirc20250314.logflirc20251120.logflirc20251121.logWill these work?

2 hours ago, OnSteamDeck said:

flirc20250314.logflirc20251120.logflirc20251121.logWill these work?

In the terminal, can you type in lsusb and paste the output?

 

18 minutes ago, jason said:

In the terminal, can you type in lsusb and paste the output?

 

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0
root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0
root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0
root hub
Bus 003 Device 002: ID 28de:1205 Valve Software Steam
Controller
Bus 003 Device 003: ID 13d3:3553 IMC Networks Bluetoot
h Radio
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0
root hub

 

18 minutes ago, OnSteamDeck said:

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0
root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0
root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0
root hub
Bus 003 Device 002: ID 28de:1205 Valve Software Steam
Controller
Bus 003 Device 003: ID 13d3:3553 IMC Networks Bluetoot
h Radio
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0
root hub

 

Remote is not showing up at all.

• Check in another PC. If it doesn't show up, replace the chord.
• Are you using a USB-C to A adapter, maybe it's not good.
• Try reversing the cable
• Check your steamdeck hub, or try without the hub.

If it doesn't show up in linux, it's not going to show up in the app.

I'm using USB C 2 C and it powers the device 

20 minutes ago, OnSteamDeck said:

I'm using USB C 2 C and it powers the device 

Doesn't necessarily mean data is working. If it doesn't show anything in lsusb, it's not connected to the machine. Try another cable. Try reversing the USB-C connector on the remote side. Does it work in another machine with the same cable?  This topic is specifically to help me focus on release candidate issues. I'll create a new thread with these posts and move them there since it's not specific to this release.

3 hours ago, jason said:

Doesn't necessarily mean data is working. If it doesn't show anything in lsusb, it's not connected to the machine. Try another cable. Try reversing the USB-C connector on the remote side. Does it work in another machine with the same cable?  This topic is specifically to help me focus on release candidate issues. I'll create a new thread with these posts and move them there since it's not specific to this release.

I forgot something important my batteries corroded the battery terminals and only works while plugged in with a cable. Does this influence it being detected by devices and the Skip 1s App? I've been told you can clean the terminals somehow ? Any tips?

15 hours ago, OnSteamDeck said:

I forgot something important my batteries corroded the battery terminals and only works while plugged in with a cable. Does this influence it being detected by devices and the Skip 1s App? I've been told you can clean the terminals somehow ? Any tips?

Do you have another machine to test it on?  You set it up at one point, when was the last time you set it up? (meaning it was configured on a machine)

18 minutes ago, jason said:

Do you have another machine to test it on?  You set it up at one point, when was the last time you set it up? (meaning it was configured on a machine)

The machine I set it in does not detect it either.

 

2 hours ago, OnSteamDeck said:

The machine I set it in does not detect it either.

 

I've got to be honest, given the condition of the remote, being that it's an A05 model, ~2-3 years old, and it wont connect to either machine, I don't think it's worth either of our times trying to fix it. Can I send you a 50% off coupon for a new one?

What are the difference between models?

16 minutes ago, jason said:

Can I send you a 50% off coupon for a new one?

Yes.

 I'm sad my original backer remote is not working properly. If I plug it to the wall or USB connector it works on the currently set devices.

PSA: don't use cheap batteries on your remotes!

9 minutes ago, OnSteamDeck said:

Yes.

 I'm sad my original backer remote is not working properly. If I plug it to the wall or USB connector it works on the currently set devices.

PSA: don't use cheap batteries on your remotes!

I can probably repair it if you send it in. 

I caught a bug under extreme conditions. Low voltage, nominal temp, the voltage regulator would get stuck latched. It would only happen if you had batteries and plugged into a computer and unplugged the cable. It was rare where and you'd have to do it over and over to reproduce it. But that doesn't mean it wouldn't happen to yours 40% of the time. These things get multiplied when you mass produce or have subtle variations in chip manufacturing etc. One of the difficult things about hardware. It has to work 100% of the time under all conditions. Some of which you can't imagine to test under.

It would leak current from the battery. Not a lot, but basically a constant drain that will never go away, even if it's asleep. The only remedy was removing the batteries and plugging them back in. It could have been the reason for the corrosion. 

I added a diode to the 6th version of the PCB. I would add one by hand to your board as well as try and replace the springs. But the plastic could get damaged, etc.

16 minutes ago, OnSteamDeck said:

Yes.

 I'm sad my original backer remote is not working properly. If I plug it to the wall or USB connector it works on the currently set devices.

PSA: don't use cheap batteries on your remotes!

Yes, cheap batteries would do it. I use rechargeable. They don't last as long, but it prevents these issues. 

8 hours ago, jason said:

I can probably repair it if you send it in. 

I caught a bug under extreme conditions. Low voltage, nominal temp, the voltage regulator would get stuck latched. It would only happen if you had batteries and plugged into a computer and unplugged the cable. It was rare where and you'd have to do it over and over to reproduce it. But that doesn't mean it wouldn't happen to yours 40% of the time. These things get multiplied when you mass produce or have subtle variations in chip manufacturing etc. One of the difficult things about hardware. It has to work 100% of the time under all conditions. Some of which you can't imagine to test under.

It would leak current from the battery. Not a lot, but basically a constant drain that will never go away, even if it's asleep. The only remedy was removing the batteries and plugging them back in. It could have been the reason for the corrosion. 

I added a diode to the 6th version of the PCB. I would add one by hand to your board as well as try and replace the springs. But the plastic could get damaged, etc.

I think that happened to me on both of my backer remotes. Brand new batteries would die rather quickly and suddenly the controller would loose power and wouldn't work with any button press it'd take one minute or two for both controllers to regain function. 

I'd take your word for the repair and the coupon! 

While you have it update the firmware of the controller to the latest.

You'll DM?