[Improvement] Window Closes Immediately if Shell is Misconfigured (in certain cases)

[kmandarin-orange]

I've only tried this with the two most recent versions (0.2.14 & 0.2.15), but installing Rio from the Wayland .rpm for x86 via dnf and running it results in the window appearing for ~1.5 seconds, then closing on its own. The window is empty, shows the min+max+close controls, and shows the cursor, but otherwise doesn't load a prompt.

After running with the logfile flag enabled, it creates the log file in the default directory, but the file is completely empty.

Here's my basic system information, I can provide more info if I've missed anything important:

• Hardware
  • CPU: Ryzen 7 7040U
  • GPU: Radeon 780M integrated graphics
  • RAM: 32GB
• Software
  • OS: Fedora 42 Workstation
  • GNOME desktop, Wayland session
  • Rio: rioterm-0.2.15-1.x86_64_wayland.rpm package installed via DNF
  • Shell: ZSH and bash

[raphamorim]

Hi @kmandarin-orange thank you for the issue,

could you try running with make dev and tell the error you got?

Thanks again

[kmandarin-orange]

Ah lord I realized what the issue was, an old config for Rio was left from the last time I tried it, and it was set to use a shell I no longer use, so after setting the log level to ERROR, I was able to get this output before it closed:

So this was a silly issue on my end. However, I do think this does pose a good question of UX and how Rio can handle stupid misconfigs like that. If the window could stay open and continue to show the errors, or even have a slightly clearer message describing the shell being unavailable, that would be a better experience.

Since this changes the context of this issue report, I can change the title to reflect the real problem here, or I can close it and open a more relevant issue if you'd like!

[raphamorim]

Yes, make sense. Rio should get better on it, could change the title. Will keep this issue on until fix