[Improvement] Window Closes Immediately if Shell is Misconfigured (in certain cases)
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 7.5k
- Forks
- 353
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 15
Description
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.rpmpackage installed via DNF - Shell: ZSH and bash
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue by installing the Wayland x86_64 RPM on Fedora 42 under GNOME and running Rio with the logfile flag, testing both zsh and bash. Inspect the empty log and determine why the window closes after about 1.5 seconds; done means the terminal remains open and displays a prompt, with useful logging if the shell is misconfigured.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- bash, linux, rust, zsh
- Domain
- cli, desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100