[BUG] <title> decky 3.0.4 Delete screenshot pop-up error in game mode

[lzq960605]

Please confirm

• I have searched existing issues
• This issue is not a duplicate of an existing one
• I have checked the common issues section in the readme file
• I have attached logs to this bug report (failure to include logs will mean your issue may not be responded to).

Bug Report Description

Expected Behaviour

3.0.0 official version Game mode error ，Steam client is the latest beta version

SteamOS version

steam os 3.6.13

Selected Update Channel

Stable

Decky Loader Version

3.0.0

Plugin Info

deckylog.txt

Have you modified the read-only filesystem at any point?

No response

Backend Logs

deckylog.txt

Frontend Logs

cef_log.previous.txt
cef_log.txt

[TrainDoctor]

@lzq960605 please give the latest pre-release a run and see if you continue to encounter this issue.

[lzq960605]

@lzq960605 please give the latest pre-release a run and see if you continue to encounter this issue.

OK, I'll try.

[lzq960605]

@lzq960605 please give the latest pre-release a run and see if you continue to encounter this issue.

This issue has not yet been reproduced

[mgnsk]

I still get the error with Decky v3.0.1-pre3. It happens when deleting a screenshot. I think it might be related to Steam's new screenshot UI

[AAGaming00]

try again without decky, this is probably a steam bug

[mgnsk]

try again without decky, this is probably a steam bug

I selected disable decky until next boot and then I was able to delete screenshots.

[TrainDoctor]

try again without decky, this is probably a steam bug

I selected disable decky until next boot and then I was able to delete screenshots.

If you can collect CEF logs at performing the actions with decky enabled and decky disabled and distinguish the two we can hopefully trace the issue. Otherwise we can't do much with this information as I've been unable to recreate the issue you've described.

[TrainDoctor]

try again without decky, this is probably a steam bug

I selected disable decky until next boot and then I was able to delete screenshots.

manged to recreate the issue myself

CEF logs:
cef_log.txt
cef_log.previous.txt

[lzq960605]

try again without decky, this is probably a steam bug

I selected disable decky until next boot and then I was able to delete screenshots.

It is true that this bug will appear when deleting the screenshots. It will also appear in decky3.0.1. I will try to reproduce it later.

[lzq960605]

cef_log.previous.txt
cef_log.txt

Just delete the screenshot to reproduce the bug 100%

[carrot117]

I have the same issue.This problem arises if the screenshot is deleted.

[lzq960605]

3.0.2

[eXhumer]

Decky-Recorder_2024-10-01_13-24-35.mp4

Does anyone know how exactly is one supposed to reproduce this? I haven't been able to repro on v3.0.1 or v3.0.2-pre1.

[lzq960605]

Decky-Recorder_2024-10-01_13-24-35.mp4
Does anyone know how exactly is one supposed to reproduce this? I haven't been able to repro on v3.0.1 or v3.0.2-pre1.

v3.0.2-pre2 fixed this problem, but the latest steam beta client has this problem again

[pchristod]

I can reproduce this pretty easily as well with latest Beta Release and latest Decky Pre. Take a screenshot ingame, exit game normally, try to open the just snapped Screenshot from the Game Page directly. This will trigger that same error as well each time.

[TrainDoctor]

I am no longer able to replicate this issue myself. If anyone can replicate it I will continue to keep this issue open.

[lzq960605]

I am no longer able to replicate this issue myself. If anyone can replicate it I will continue to keep this issue open.

This problem still exists in v3.0.3-pre1

[eXhumer]

Confirmed reproducible with 3.0.3-pre1.

Looking through the component stack trace in Steam Deck, the following two functions from Decky Loader seems to be attaching to the component before erroring.

[eXhumer]

This is the function inside which it is failing.

        function F(e) {
            const {handle: t, controlsVisible: r, fnOnContentWidth: i} = e
              , a = (0,
            C.FD)(t)
              , [s,o] = (0,
            n.useState)(!1);
            (0,
            n.useEffect)(( () => o(!1)), [t]);
            const c = a.data
              , m = n.useCallback((e => {
                const t = e.target;
                i(t.clientWidth)
            }
            ), [i])
              , u = (0,
            y.wY)(m);
            if (a.isLoading)
                return n.createElement(g.O0, {
                    className: f.FocusedScreenshotSkeleton
                });
            if (a.isError || s)
                return n.createElement(le, {
                    className: f.FocusedScreenshotError
                }, n.createElement(A.Z, {
                    className: f.Message
                }, (0,
                l.we)("#ScreenshotUploader_FailedToLoadScreenshot")));
            const {strUrl: d} = c;
            return n.createElement(g.Kz, {
                direction: "column",
                space: "md",
                grow: !0
            }, n.createElement(A.Z, {
                className: f.FocusedScreenshotContainer
            }, n.createElement("div", {
                className: f.FocusedScreenshotImageContainer
            }, n.createElement("img", {
                ref: u,
                onError: () => o(!0),
                src: d,
                className: f.FocusedScreenshot
            })), n.createElement(G, {
                handle: t,
                screenshot: c,
                key: t,
                controlsVisible: r
            })))
        }

This is the destructing line that fails

            const {strUrl: d} = c;

[Vegas7]

Decky-Recorder_2024-10-01_13-24-35.mp4
Does anyone know how exactly is one supposed to reproduce this? I haven't been able to repro on v3.0.1 or v3.0.2-pre1.

View the screenshot, then delete it in the viewing mode (or full screen mode?), that will trigger the issue.

[lzq960605]

decky 3.0.4 ,Steam stable version client，The problem still exists

[lzq960605]

[lzq960605]

cef_log.txt
cef_log.previous.txt

[AAGaming00]

Confirmed reproducible with 3.0.3-pre1.

Looking through the component stack trace in Steam Deck, the following two functions from Decky Loader seems to be attaching to the component before erroring.

those two don't matter, they'll always be there for all routes