Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • O orbterm
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 4
    • Issues 4
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • redox-os
  • orbterm
  • Issues
  • #13
Closed
Open
Created Oct 17, 2020 by Perry Thompson@rypervenche

Fails to start: Cannot find a regular monospace font

I get this error when trying to run orbterm on Gentoo Testing. I built it from the latest master ( d8566de4 ). Please let me know if you need any extra information from my system.

RUST_BACKTRACE=full orbterm
thread 'main' panicked at 'Cannot find a regular monospace font: "failed to open font: No such file or directory (os error 2)"', src/console.rs:70:61
stack backtrace:
   0:     0x55f754312ec0 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::he0dca9d3067097dc
   1:     0x55f75433646c - core::fmt::write::h608e5553fba47137
   2:     0x55f754310b17 - std::io::Write::write_fmt::h1302a4f903faf2d2
   3:     0x55f754315100 - std::panicking::default_hook::{{closure}}::h56b1cc96c7e70a8b
   4:     0x55f754314e4c - std::panicking::default_hook::h51ada1af445d445b
   5:     0x55f754315763 - std::panicking::rust_panic_with_hook::heb2d3564c4fb0e62
   6:     0x55f754315339 - std::panicking::begin_panic_handler::{{closure}}::h076f60f957528d12
   7:     0x55f75431334c - std::sys_common::backtrace::__rust_end_short_backtrace::h8323f9327f4fd987
   8:     0x55f7543152f9 - rust_begin_unwind
   9:     0x55f754334d21 - core::panicking::panic_fmt::h0cd18c88a0b60345
  10:     0x55f754334b43 - core::option::expect_none_failed::h19193ed4a6583777
  11:     0x55f7542d5a21 - orbterm::console::Console::new::h9d6322974447f902
  12:     0x55f7542c9d8d - orbterm::main::h220cd90f2657795b
  13:     0x55f7542c8333 - std::sys_common::backtrace::__rust_begin_short_backtrace::hdcac8c359225292f
  14:     0x55f7542c8349 - std::rt::lang_start::{{closure}}::h9e35022678f94400
  15:     0x55f754315b61 - std::rt::lang_start_internal::h770fd74051812747
  16:     0x55f7542ca1f2 - main
  17:     0x7f30ff548e6b - __libc_start_main
  18:     0x55f7542bb0aa - _start
  19:                0x0 - <unknown>
Assignee
Assign to
Time tracking