Good afternoon folks,

This community has been around for quite some time on Lemmy, a little over a year and half if i recall correctly with the initial intention of being the next /r/CanadaGuns, the first post made was of my 20" Mossberg 590A1 and (now prohibited) .22Lr Kriss Vector which then divulged into semi-regular news postings from myself, i can only think of a very small handful of posts that didn't come from me.

Nonetheless i had gotten burnt out as i constantly had my head in the political aspect of our sport and hobby, which is why i introduced /u/Canadian_[email protected] to keep this community active and to which if i recall correctly lasted about 24 hours before being banned by the instance admins.

That had immediately prompted the self-hoster in me to spin up a Lemmy instance of my own, throw it behind my reverse-proxy, slap Anubis onto it and begin federating with the intention of not being the next /r/CanadaGuns but to simply be the federated news source for folks with their Firearms Licenses in Canada.

![email protected]

I am more than willing to appoint another moderator who wishes to continue regular posts here, i shall post here only if the news effects licensed firearms owners as a whole but for now have locked this community to moderator only posts as i cannot put my focus into two communities that serve the same purpose.

Apologies if this has been an inconvenience for some.

Please reach out to /u/[email protected] for any questions, concerns or suggestions.

Thanks for reading.

TLDR to the issue

There have been many reports of the new Steam controller failing to update on Linux distros other than SteamOS, I am making this post to document my solution to this issue.

From what I can tell, certain distros place restrictions on what data can be accessed via USB.

Solution

So as many others here I got my Steam controller and was encountering the update errors on my Debian 13 desktop.

I tried updating via a Windows laptop which was successful however did not stop Steam from complaining there was an update on my Debian machine.

I did a little digging in my steamui_system.txt and noticed my error was

[2026-07-09 10:23:55] HardwareUpdate: ------[ stdout ]------
Found Type: Triton USB SN: FXA9961904609
UPDATING TRITON USB - SN:	FXA9961904609
ERROR: Couldn't open BL comport
[2026-07-09 10:23:55] HardwareUpdate: ------[ stderr ]------

more digging I found out that the update script/tool is stored in /home/YourUser/.local/share/Steam/bin/hardwareupdater/ and in that folder the script/tool is called hardwareupdater.x86_64

This script/tool has launch options that should not be missed in your steamui_system.txt, for me it was —update-by-serial “SerialNumberOfController”

Many Linux users will dislike this but run the script/tool as a sudoer or root in a shell like such,

sudo /home/YourUser/.local/share/Steam/bin/hardwareupdater/hardwareupdater.x86_64 --update-by-serial 'FXA9961904609'

Replace the /YourUser/ portion of the directory path with the username of your Linux account and change the serial-number to match your controller.

the script/tool will display progress as it goes and eventually succeed, Steam will prompt you one last time there is an update but then proceed past the actual update itself and instead do a short tutorial on the controller. I guess there are USB permissions issues hence the failures.

The output of the script/tool is as such

sudo /home/YourUser/.local/share/Steam/bin/hardwareupdater/hardwareupdater.x86_64 --update-by-serial 'FXA9961904609

Found Type: Triton USB SN: FXA9961904609
UPDATING TRITON USB - SN:       FXA9961904609
DEBUG: Found TRITON matching SN`
ERASING
PROGRAMMING: IBEX_FW_6A4D85E3.fw
PROGRESS: 9%
PROGRESS: 17%
PROGRESS: 26%
PROGRESS: 34%
PROGRESS: 43%
PROGRESS: 51%
PROGRESS: 60%
PROGRESS: 68%
PROGRESS: 77%
PROGRESS: 85%
PROGRESS: 94%
PROGRESS: 100%
RESETTING
SUCCESS

Disclaimer:

If the script/tool at all stalls or hangs, which it shouldn't as it took less than a minute for me to complete the update, DO NOT unplug the controller, you may damage the firmware doing this essentially bricking your controller, just be patient and wait or Control + C the script/tool to abruptly exit the script, unfortunately the script/tool has been compiled into binary so i cannot verify how it handles abrupt exits!

Edit

I have not tested this on the Steam Puck, only the controller, I suspect they use the same script but cannot confirm that as my Puck was updated on a Windows Laptop and didn’t prompt me to update on my Debian desktop afterwards.

cross-posted from: https://sh.itjust.works/post/63136595

Of course the GSG-16 is on top.

cross-posted from: https://sh.itjust.works/post/61575277

Important update for PAL holders.

---

Amnesty Orders Extension Amnesty Orders for the 2020, 2024, and 2025 prohibitions are in place to protect businesses and individual owners from criminal liability while they take steps to comply with the law, such as participating in the compensation program or disposing of their prohibited firearms without compensation.

In March 2026, the Supreme Court of Canada agreed to hear an appeal challenging the May 2020 prohibition of assault-style firearms. In light of this, the Amnesty Orders have been extended and set to expire 90 days following the date the Supreme Court of Canada renders its decision, which is expected next year. By extending the amnesty period, the Government is providing certainty to individual owners and businesses that they will continue to be protected from criminal liability while the Supreme Court hears the appeal and renders its decision.

The Government of Canada is confident in the decision to prohibit assault-style firearms due to the risk they pose to public safety. The new expiry date for the Amnesty Orders does not impact the ASFCP, which is expected to be completed by October 2026. The program remains the only opportunity for firearm owners to receive compensation for their prohibited firearms.

Important update for PAL holders.

Amnesty Orders Extension

Amnesty Orders for the 2020, 2024, and 2025 prohibitions are in place to protect businesses and individual owners from criminal liability while they take steps to comply with the law, such as participating in the compensation program or disposing of their prohibited firearms without compensation.

In March 2026, the Supreme Court of Canada agreed to hear an appeal challenging the May 2020 prohibition of assault-style firearms. In light of this, the Amnesty Orders have been extended and set to expire 90 days following the date the Supreme Court of Canada renders its decision, which is expected next year. By extending the amnesty period, the Government is providing certainty to individual owners and businesses that they will continue to be protected from criminal liability while the Supreme Court hears the appeal and renders its decision.

The Government of Canada is confident in the decision to prohibit assault-style firearms due to the risk they pose to public safety. The new expiry date for the Amnesty Orders does not impact the ASFCP, which is expected to be completed by October 2026. The program remains the only opportunity for firearm owners to receive compensation for their prohibited firearms.

Morning y’all,

I have a shortcut that I use regularly at work, and it has saved me so much time however, it appears the latest iPadOS update possibly broke file renaming.

The script runs fine until it reaches the renaming portion which used to work perfectly but now claims that “The file does not exist” and ends the script, I can confirm the files are being saved in the directories as intended just failing on the renaming.

https://www.icloud.com/shortcuts/9ecef7e31dc14a3fa9590da6edaef061

By chance does anyone know a workaround that I could use temporarily? Apologies if the shortcut is a mess, I tried to comment along the way as best as I can.

Edit; appears the network drive is the issue here, saving the files locally on the tablet instead seems to work as intended, weird.