Crash at loading session since update

[RoterFuchs621]

Hi, first I wanna say thank you for your work on this project.
I tried hyprsession at version 0.1.6 and it worked, but it couldn't record all my clients properly so I didn't used it again.
Now in the Version 0.2.1 the record of the active Clients in "clients.json" works way better and the old issues with missing clients are gone.
But now it couln't reopen my saved session after reboot so I tested it with the console. When I do "hyprsession load" all my current active clients get closed and the console with the hyprsession programm crashes also.
I wrote the output of "hyprsession load" to a file to get some information:

"Using session path: ~/.local/share/hyprsession
Loading session: default"

that's all what is printed, looks like it crashes before any client gets opened.

Can you reproduce this behavior?

Thanks a lot!

[RoterFuchs621]

Sorry I must have done something wrong with my exec-once config before, it now works on startup as it should, the command line behavior remains but that's not really the way this software is supposed to be used anyway.

[erikvanzijst]

Same problem. Instead of restoring the session, it kills everything and leaves me with an empty desktop.

[veivataan]

Instead of restoring the session, it kills everything and leaves me with an empty desktop.
Same here.

[joshurtree]

This could be an issue with migration from 0.1.x to 0.2.x. I changed the structure of the data files to support multiple sessions with each session now going into it's own sub directory. The files in the old structure (held in the ~/.local/share/hyprsession directory by default) should be moved into the default sub directory. There's two things that could help me get to the bottom of what's causing it.

1. Giving me a file listing of the ~/.local/share/hyprsession directory and the ~/.local/share/hyprsession/default if it exists.
2. Is this problem persisting on subsequent reboots or just after an upgrade from 0.1.x?

Assuming it is just a migration issue then a workaround would be to create the default directory and move the exec.conf file there manually.

[veivataan]

Oh nah I'm just stupid: Of course it nukes the window it has been run from so it needs to be run somewhere else: for me running from vicinae launcher as a command worked.