Error Reference: Shared SteamUI_7834012_9305e8ac929cc2f3 unreachable

[chesii]

Please confirm

• I have searched existing issues
• This issue is not a duplicate of an existing one
• I will fill this out to the best of my ability

Expected Behaviour

I open version 1.1.0 and expect it to open but come across the listed behavior. 2nd latest version works.

Actual Behaviour

Something went wrong while displaying this content. Refresh

Error Reference: Shared SteamUI_7834012_9305e8ac929cc2f3
unreachable

Steps To Reproduce

click •••
scroll down to PowerTools
click on it
get referenced error

Anything else?

No response

Version

1.1.0 (Latest stable)

Platform

Steam Deck

OS

SteamOS 3 (Stable)

[NGnius (Graham)]

If a full system restart doesn't fix it, Decky and PowerTools logs would be appreciated.

Decky logs can be saved to /home/deck/decky.log by running cd ~ && journalctl -u plugin_loader.service > decky.log. PowerTools logged are saved at /tmp/powertools-rs.log.

[chesii]

What would be the best method of sending them? I get a popup saying the file is less than 0 bytes when dragging and dropping it here and copy/paste crashes it.

…

On Fri, Feb 10, 2023 at 10:40 PM NGnius (Graham) ***@***.***> wrote: If a full system restart doesn't fix it, Decky and PowerTools logs would be appreciated. Decky logs can be saved to /home/deck/decky.log by running cd ~ && journalctl -u plugin_loader.service > decky.log. PowerTools logged are saved at /tmp/powertools-rs.log. — Reply to this email directly, view it on GitHub <#71 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A3YMPPL67WJ2MAMZUVGOLCDWW4J3TANCNFSM6AAAAAAUYO4BBA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[chesii]

Also I can't find what you mean by " /tmp/powertools-rs.log." I tried searching it in Dolphin and found nothing. But I do currently have issues regarding my btrfs home drive making my steamgames and WIndows partitions "unknown" if that would have anything to do with why it's missing..? On Fri, Feb 10, 2023 at 11:05 PM Parmesan ***@***.***> wrote:

…

What would be the best method of sending them? I get a popup saying the file is less than 0 bytes when dragging and dropping it here and copy/paste crashes it. On Fri, Feb 10, 2023 at 10:40 PM NGnius (Graham) ***@***.***> wrote: > If a full system restart doesn't fix it, Decky and PowerTools logs would > be appreciated. > > Decky logs can be saved to /home/deck/decky.log by running cd ~ && > journalctl -u plugin_loader.service > decky.log. PowerTools logged are > saved at /tmp/powertools-rs.log. > > — > Reply to this email directly, view it on GitHub > <#71 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/A3YMPPL67WJ2MAMZUVGOLCDWW4J3TANCNFSM6AAAAAAUYO4BBA> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >

[Ben]

Also had this issue on a fresh SteamOS installation (had to factory reset due to other issues), but its now working.

Series of events:

1. Was running v1.0.6.
2. Downloaded the v1.1.0 update.
3. Presented with the 'Something went wrong while displaying this content.' error whenever loading the PowerTools UI.
4. Tried reboots, reinstalls, etc. nothing appeared to fix it, it would always show that error.
5. Reinstalled v1.0.6, worked absolutely fine again.
6. < played some games, left it at that overnight >
7. < rebooted Steam Deck a few times for other misc reasons >
8. Came to this thread, and for the sake of debugging tried to install and use v1.1.0 again so I could pull the logs.
9. Installed the v1.1.0 update again, everything is working fine. 🤷

As its now working, and I've rebooted between now and the error happening, I can't provide any useful logs unfortunately.

Also, I have no idea what the reproducable scenario is, which is even more annoying. So far, from the experience I've been through;

1. Install a fresh SteamOS installation.
2. Install Decky Loader.
3. Install PowerTools v1.0.6.
4. Install PowerTools v1.1.0 update.
5. < issue occurs >

But I have no idea if that scenario is actually reliably reproducable.

[LPDawid]

I had this too after 1.1.0 update. Standard reboot didn't help. Forced reboot followed by SteamOS auto verification fixed it. I've attached my logs if needed.
decky.log
powertools-rs.log

[NGnius (Graham)]

I'm still not sure what's causing this and I'm unable to reproduce it. Therefore I have no way of fixing this. Be prepared to wait a while if you can't fix it yourself. I can almost guarantee I am more frustrated than you on this: I wanted to focus on other projects this weekend.

Here's what I've figured out so far:

• The PowerTools back-end (the Rust binary) is failing to start (why?)
• The UI is crashing because vital information is "undefined" (because the back-end isn't running)

I don't have any information to even correlate cases where it is happening. All I can offer is generic troubleshooting advice like make sure everything is up to date, reboot, reinstall, sacrifice some blood to the PC gods, etc.

Also I can't find what you mean by " /tmp/powertools-rs.log." [sic]

Don't worry about it, powertools-rs.log won't exist if the back-end can't start. Though that sounds like the least of your worries if your system can't even upload files. The rest of what you're describing sounds like corruption. I can't help but wonder if your non-standard setup is causing this problem.

[chesii]

Another user mentioned forced reboot, or holding the power button until the screen shuts off, and after the steam verification popped boot up it started working! I haven't figured anything out regarding my issue but contacted the person who made the btrfs home conversion hoping they'd have an idea.

…

On Sat, Feb 11, 2023 at 6:36 PM NGnius (Graham) ***@***.***> wrote: I'm still not sure what's causing this and I'm unable to reproduce it. Therefore I have no way of fixing this. Be prepared to wait a while if you can't fix it yourself. I can almost guarantee I am more frustrated than you on this: I wanted to focus on other projects this weekend. Here's what I've figured out so far: - The PowerTools back-end (the Rust binary) is failing to start (why?) - The UI is crashing because vital information is "undefined" (because the back-end isn't running) I don't have any information to even correlate cases where it is happening. All I can offer is generic troubleshooting advice like make sure everything is up to date, reboot, reinstall, sacrifice some blood to the PC gods, etc. Also I can't find what you mean by " /tmp/powertools-rs.log." [sic] Don't worry about it, powertools-rs.log won't exist if the back-end can't start. Though that sounds like the least of your worries if your system can't even upload files. The rest of what you're describing sounds like corruption. I can't help but wonder if your non-standard setup is causing this problem. — Reply to this email directly, view it on GitHub <#71 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A3YMPPPOC7VF5KJ6CYG5G7TWXAWBZANCNFSM6AAAAAAUYO4BBA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[phush0]

For me update from 1.0.6 to 1.1.0 made decky crash all together and tab with plug disappear completely. Restart fixed it.

[Pilcrow182]

Can confirm, same as phush0.

I updated from 1.0.6 to 1.1.0, and then running PowerTools brought me to a screen with this exact error and a 'refresh to continue' button. Upon clicking the button I was dropped back into the Deck's main menu and Decky was no longer loaded.

I tried selecting 'restart steam' from the power menu, which restored Decky, but the bug persisted upon trying to use PowerTools again.

I then tried a shutdown from the power menu, started the Deck again a few minutes later, and PowerTools 1.1.0 was suddenly working fine. I am now using it with no issues.

[Kai]

I had this issue, too.
From 1.0.6 to 1.1.0, it crashed instantly when I tried clicking PowerTools in Decky.
I waited until 1.1.1 and the issue wasn't solved. Then I uninstalled & re-installed Decky with PowerTools 1.1.1.
It looks like an outdated config or cache caused this issue.

[NGnius (Graham)]

I haven't heard of this happening recently (and I think I fixed it), so I'm going to close this.