search

latter-bolden / port

A ship runner and manager for Urbit OS
180 stars 12 forks source link

[bug]Boot fresh ID: Can't choose keyfile due to illegible font display. #179

Closed julesss-coder closed 2 years ago

julesss-coder commented 2 years ago

*Bug Description

  1. After starting Port and clicking "Boot a fresh ID", I click "Choose keyfile". The file manager opens, but all characters are replaced with rectangles, so I can't find the file. See screenshot: Urbit screenshot

  2. Then, Port crashes. The terminal shows many "fontconfig errors" and "fontconfig warnings", see screenshot: Port fontconfig errors

To Reproduce Steps to reproduce the behavior:

  1. Start Port
  2. Click on 'Boot a fresh ID.'
  3. Click on "Choose keyfile".
  4. See illegible characters in file explorer window
  5. See Port crash and - if you started Port in the terminal - check terminal for error messages.

Expected Behavior File explorer opens, characters are legible, I can find and choose the keyfile.

Screenshots See above.

Environment:

Context I don't know how to install Port on Linux any other way than via Snap, as I lack the technical knowledge. I hope you can help me boot my planet even though I'm a newbie to all this!

lycurgus commented 2 years ago

Based on an issue thread from another project (https://github.com/iced-rs/iced/issues/386) it seems like you might need to install the libfontconfig-dev package. Might also need to log out and in, or restart the machine, to get it to reload the fonts after installing that package.

julesss-coder commented 2 years ago

Hi there, thank you! I installed libfontconfig-dev and restarted my computer, but the problem persists. (I was able to boot my urbit planet anyway, using some guesswork.)

lycurgus commented 2 years ago

Glad to hear you got the planet booted; sorry my advice wasn't helpful. I also found this reddit thread which mentions moving the fonts folder and reinstalling fontconfig as a possible solution: https://www.reddit.com/r/Ubuntu/comments/t7rgij/cant_install_most_of_the_snap_packages_recently/

I don't know if that's an actual solution or just a workaround - it might be something @arthyn needs to modify/update in the Port snap itself instead.