Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
O
orbital
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 5
    • Issues 5
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 1
    • Merge Requests 1
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • redox-os
  • orbital
  • Issues
  • #28

Closed
Open
Opened Nov 04, 2020 by Colin Dean@colindean

Orbital fails to launch on ~fresh Redox build installation

I tried both orbital display:3 orblogin launcher as suggested here and orbital display:3/activate orblogin launcher as present in /etc/init.d/20_orbital, but both yield the same behavior on a redox-os/redox master branch build as of commit f30e25f.

They both panic with "called Result::unwrap() on an Err value: Function not implemented' with a pointer to orbital-core/src/lib.rs:79:8. Looks like there's a syscall returning an unexpected Err.

I was logged in as root, but also tried as user, which yielded only permission errors.

orbital --version fails with "no login manager present".

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: redox-os/orbital#28