Runit hangs at system reboot
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 20/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Domain
- operating-systems
Research direction
The issue provides only a screenshot and the title, with no file, test, or reproduction steps. Start by examining the attached image and reproducing the reboot hang in a Void Linux environment; done means identifying the affected init script or shutdown path, fixing the hang, and verifying that system reboot completes.
Written by the indexing model from the issue text.
Description
- Dominant language
- C
- Stars
- 247
- Forks
- 67
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 1
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
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.
More from void-linux/void-runit
-
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
void-linux/void-runit#141 · 1 reaction ·
-
elogind service starts after sound device initialization, causing permission failuresPossibly taken @eholzbach claimed this 21 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 45/100
void-linux/void-runit#135 · 10 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
void-linux/void-runit#127 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
void-linux/void-runit#125 · 4 comments ·
-
key file and source not passed to keyscriptPossibly taken @shaohme claimed this 834 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
void-linux/void-runit#120 ·
All issues in void-linux/void-runit
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
KalicoCrew/kalico#1012 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
joncampbell123/dosbox-x#6664 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
bug good first issue please retest
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
eclipse-tinydtls/tinydtls#298 · 2 comments ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100