Unable to read file selector navigation for ssh key

[IronSinew]

OS

Linux (Ubuntu 24.04 - installed via Snap)

VERSION

1.6.8

ISSUE DESCRIPTION

When I press the private key selector, the fonts don't seem to be rendering in the file navigator

[qishibo]

have you tried sudo snap connect another-redis-desktop-manager:ssh-keys?

[qishibo]

or try to refresh your fonts list by

cd /usr/share/fonts/
sudo fc-cache -fv
sudo reboot

[IronSinew]

have you tried sudo snap connect another-redis-desktop-manager:ssh-keys?

or try to refresh your fonts list by

cd /usr/share/fonts/
sudo fc-cache -fv
sudo reboot

I tried both, and the issue still persists. This is the only application where the file manager does this.

[qishibo]

OK I'll try to reproduce it and fix what's more can you ty the AppImage package? I want to know if this error staill exists in AppImage

[qishibo]

I've tried in Ubuntu 18(may be to old), it works well, so there may be some compatible issue in higher version ubuntu， still trying

[IronSinew]

OK I'll try to reproduce it and fix what's more can you ty the AppImage package? I want to know if this error staill exists in AppImage

I tried AppImage v1.6.8 and it does not have the same issue.

[IronSinew]

Any luck?

[qishibo]

try this latest snap version by sudo snap install xxx.snap --dangerous --classic to install 1.7.0

https://cowtransfer.com/s/cd6fcd4c513944 code=tu53tp

[IronSinew]

I installed 1.7 via snap and the issue persists, sadly.

[qishibo]

I've tried to reproduct this issue but failed… now I've no idea to solve that

[qishibo]

You can use the AppImage instead for temporary

[IronSinew]

It may be applicable that in the settings, it never seems to finish "loading" the font options to select?

[qishibo]

fonts list are got by exec fc-list command, you can exec in cli to test if this works well. The snap package runs in sandbox by default ,this may cause some unknow env issues

[IronSinew]

$ fc-list

/usr/share/fonts/truetype/dejavu/DejaVuSerif-Bold.ttf: DejaVu Serif:style=Bold
/usr/share/fonts/truetype/noto/NotoSansThai-Regular.ttf: Noto Sans Thai:style=Regular
...

In the terminal, it does seem to return a list of the fonts. If it can't load any fonts, would it produce the error I'm experiencing with the file navigator? 🤔

[qishibo]

I'll add the error tips if cannot load fonts. Actually I highly recommand you using the AppImage package instead of snap, because the snap package runs in a sandbox env where there would be many restrictions

[besanek]

Hi, I have the exact same issue. If I try to view the font list in the settings, I get the following error in the terminal.

(node:1747282) UnhandledPromiseRejectionWarning: Error: Command failed: whereis fc-list
/bin/sh: 1: whereis: Permission denied

    at ChildProcess.exithandler (child_process.js:317:12)
    at ChildProcess.emit (events.js:315:20)
    at maybeClose (internal/child_process.js:1048:16)
    at Socket.<anonymous> (internal/child_process.js:439:11)
    at Socket.emit (events.js:315:20)
    at Pipe.<anonymous> (net.js:673:12)
(Use `another-redis-desktop-manager --trace-warnings ...` to show where the warning was created)
(node:1747282) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:1747282) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Does it help?

[qishibo]

Hi, I have the exact same issue. If I try to view the font list in the settings, I get the following error in the terminal.

(node:1747282) UnhandledPromiseRejectionWarning: Error: Command failed: whereis fc-list
/bin/sh: 1: whereis: Permission denied

    at ChildProcess.exithandler (child_process.js:317:12)
    at ChildProcess.emit (events.js:315:20)
    at maybeClose (internal/child_process.js:1048:16)
    at Socket.<anonymous> (internal/child_process.js:439:11)
    at Socket.emit (events.js:315:20)
    at Pipe.<anonymous> (net.js:673:12)
(Use `another-redis-desktop-manager --trace-warnings ...` to show where the warning was created)
(node:1747282) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:1747282) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Does it help?

I got your error, i found that my font lib depends whereis command to locate fc-list, if fc-list missed, it will use fc-list2 instead https://github.com/oldj/node-font-list/blob/dfb34faa78343add4f83a39d7c7e8913ecb0a9c7/libs/linux/index.js#L13

so the snap version may without the permission to exec whereis fc-list, I will fix it and make it return Default Initial if errors like yours, at least it won't be loading always

[qishibo]

6cc2d8a @besanek done.

As for a more perfect solution, I am also testing it

[qishibo]

Recently, a similar issue was found on Fedora, which was caused by the computer not having the corresponding font installed. After installing the font, the display returned to normal

for example

1. Install missing local language fonts, which may vary across different systems, such as sudo dnf install google-noto-sans-cjk-ttc-fonts or sudo apt install ttf-wqy-zenhei ttf-wqy-microhei
2. Refresh font ,such as sudo fc-cache -fv