[Bug]: `ocx service install` on Linux always suggests `loginctl enable-linger`, even when linger is already on
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 82/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- linux, typescript
- Domain
- cli
Research direction
Start in src/service/cli.ts around line 339, where the Linux install message is selected. Check how the command can determine whether loginctl show-user $USER -p Linger reports Linger=yes, and look for nearby service CLI tests. Done when the install output gives accurate guidance when linger is already enabled and when it is off.
Written by the indexing model from the issue text.
Description
Client or integration
Other
Area
Service lifecycle
Summary
After a successful ocx service install on Linux, the CLI always prints For auto-start on boot: loginctl enable-linger $USER, including when loginctl show-user $USER -p Linger already reports Linger=yes. The line comes from src/service/cli.ts (around L339), which checks only process.platform === "linux". It reads as if the service will not start at boot.
Reproduction
- On Ubuntu 24.04 with
loginctl show-user $USER -p Linger→Linger=yes. ocx service install.- The output ends with the enable-linger hint.
Expected: print the hint only when linger is off, or say that linger is already enabled.
Version
2.83.0 (Linux deb)
Operating system
Ubuntu 24.04 x86_64
Provider and model
No response
Logs or error output
✅ opencodex service installed and serving on port 10100.
For auto-start on boot: loginctl enable-linger $USER
Screenshots and supporting files
No response
Redacted configuration
No response
Checks
- I searched existing issues and documentation.
- I removed secrets, tokens, account details, request credentials, and personal data.
- Dominant language
- TypeScript
- Stars
- 16.9k
- Forks
- 1.3k
- Avg merge
- 5h 22m
- Merged PRs (30d)
- 627
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 lidge-jun/opencodex
-
[Bug][CI]: shard duration table is three weeks stale and under-weights 678 unrecorded test filesOpenbug platform
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
lidge-jun/opencodex#6982 · 1 comment ·
Maintainers usually reply within 1 day
-
account-pool enhancement needs-design proxy
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
lidge-jun/opencodex#6737 · 1 comment ·
Maintainers usually reply within 1 day
-
account-pool bug
Difficulty 4/5 3-5 days Newbie friendliness 45/100
Maintainers usually reply within 1 day
-
[Bug] routing-history index rebuild runs synchronously on the serving event loop (487 s proxy-wide freeze)Possibly taken A pull request linked to this issue is open or already merged. Openbug proxy
Difficulty 4/5 3-5 days Newbie friendliness 42/100
Maintainers usually reply within 1 day
-
account-pool bug
Difficulty 4/5 3-5 days Newbie friendliness 54/100
Maintainers usually reply within 1 day
All issues in lidge-jun/opencodex
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
-
area:cowork area:desktop documentation enhancement platform:macos
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
anthropics/claude-code#101720 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
apache/rocketmq-dashboard#6610 ·
Maintainers usually reply within 3 days
-
Add: MS NOWOpencheck:passed streams:add
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Global update drops overrideAccess, so Local API updateGlobal fails filterOptions validation (3.90 regression)Possibly taken @PINYOPATTANAWASANPORN claimed this today. Openarea: core Bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
payloadcms/payload#18674 · 1 comment ·
Maintainers usually reply within 1 day