chromebrew icon indicating copy to clipboard operation
chromebrew copied to clipboard

🐞 Bug Remmina giving errors about not being able to load `libjxl.so.0.8`

Open VenomousSteam81 opened this issue 10 months ago • 11 comments

Describe the bug Remmina gives errors about not being able to load some of its plugins because it cannot open libjxl.so.0.8.

To Reproduce Steps to reproduce the behavior:

  1. Please indicate where the command(s) were executed.

My environment was (crosh, bash or VT-2): crosh (with a patch that re-enables sudo by using a minioverride.so file) and is confirmed not working in VT-2 as well.

  1. I executed the command(s) below:

    remmina
    

    Output:

remmina-Message: 21:30:26.958: Remmina does not log all output statements. Turn on more verbose output by using "G_MESSAGES_DEBUG=remmina" as an environment variable. More info available on the Remmina wiki at: https://gitlab.com/Remmina/Remmina/-/wikis/Usage/Remmina-debugging Failed to load plugin: /usr/local/lib/remmina/plugins/remmina-plugin-rdp.so. Error: libjxl.so.0.8: cannot open shared object file: No such file or directory Failed to load plugin: /usr/local/lib/remmina/plugins/remmina-plugin-www.so. Error: libjxl.so.0.8: cannot open shared object file: No such file or directory [glibsecret] unable to get secret service: Error spawning command line “dbus-launch --autolaunch=57509399dab0b36b58adcc5b678fe143 --binary-syntax --close-stderr”: Child process exited with code 1

(org.remmina.Remmina:7372): Gtk-WARNING **: 21:30:27.274: Unknown key monospace-font-name in /usr/local/.config/gtk-3.0/settings.ini :0: Warning: g_ascii_strdown: assertion 'str != NULL' failed :0: Warning: g_strrstr: assertion 'haystack != NULL' failed Warning: Remmina is running without a secret plugin. Passwords will be saved in a less secure way.

(org.remmina.Remmina:7372): Gtk-WARNING **: 21:30:27.584: gtk_menu_attach_to_widget(): menu already attached to GtkMenuItem

(org.remmina.Remmina:7372): libappindicator-WARNING **: 21:30:27.915: Unable to get the session bus: Error spawning command line “dbus-launch --autolaunch=57509399dab0b36b58adcc5b678fe143 --binary-syntax --close-stderr”: Child process exited with code 1

(org.remmina.Remmina:7372): LIBDBUSMENU-GLIB-WARNING **: 21:30:27.915: Unable to get session bus: Error spawning command line “dbus-launch --autolaunch=57509399dab0b36b58adcc5b678fe143 --binary-syntax --close-stderr”: Child process exited with code 1 ``` Expected behavior Remmina should run fine without any issues

Screenshots N/A

System Information: Paste the output of crew sysinfo -v between the two *** below. If you cannot execute crew, display the output of cat /etc/lsb-release instead.


/usr/local/bin/crew:1898:

:The last update was 1 hr, 7 min, 3 seconds ago.

Expand
  • Architecture: aarch64 (armv7l)

  • Processor vendor: ARM

  • User space: 32-bit

  • Chromebrew Kernel version: 5.15

  • Chromebrew Running in Container: false

  • Chromebrew version: 1.57.2

  • Chromebrew prefix: /usr/local

  • Chromebrew libdir: /usr/local/lib

  • Last update in local repository: 55d715205 Add pystring package (#11407) (75 minutes ago)

  • OS variant: Chrome OS

  • OS version: hana-release/R132-16093.92.0

  • OS channel: stable-channel

***

Additional context Add any other context about the problem here.

What I think needs to be done:

  - [ ] Update `libjxl` if necessary

VenomousSteam81 avatar Feb 24 '25 03:02 VenomousSteam81

Also can we get some remmina plugins added? I want to use spice but I don't know how to add it

VenomousSteam81 avatar Feb 24 '25 03:02 VenomousSteam81

try crew install libjxl?

Zopolis4 avatar Feb 24 '25 03:02 Zopolis4

I have. It is in fact installed

VenomousSteam81 avatar Feb 24 '25 03:02 VenomousSteam81

The libjxl dependency chain is remmina -> freerdp -> ffmpeg -> libjxl. Remmina has been updated recently, as has freerdp, so it looks like the issue is ffmpeg. We currently ship libjxl 0.11.1, so presumably ffmpeg has not been rebuilt against a newer version and so is looking for version 0.8. As I understand it, building ffmpeg is a significant effort, and is normally done by @satmandu. Admittedly, we currently ship the latest version of ffmpeg, so perhaps a rebuild is all that is required.

Zopolis4 avatar Feb 24 '25 04:02 Zopolis4

Is there a guide or anything so I can rebuilt it myself? I'd like to give it a try

VenomousSteam81 avatar Feb 24 '25 04:02 VenomousSteam81

iirc this should rebuild it locally:

yes | crew install $(crew deps -b ffmpeg)
crew remove ffmpeg
crew install -s ffmpeg

do note that if you're trying to rebuild it on a chromebook, the build will probably take somewhere between eight hours and two days, so unfortunately you might be better off waiting.

Zopolis4 avatar Feb 24 '25 04:02 Zopolis4

Oh wow, ok. Yeah I don't want to wait.

Also I figured out that you can just download remmina plugins!

Should this be closed?

VenomousSteam81 avatar Feb 24 '25 04:02 VenomousSteam81

the libjxl loading errors are still present and point to an issue with one of our packages, so I think it makes sense to leave the issue open until they are fixed.

Zopolis4 avatar Feb 24 '25 04:02 Zopolis4

Ok. Thank you

VenomousSteam81 avatar Feb 24 '25 05:02 VenomousSteam81

Also encountering this loading issue in an attempted rebuild of fceux, although its fatal this time.

Zopolis4 avatar Mar 24 '25 02:03 Zopolis4

Just rebuilt ffmpeg, which hopefully resolved that libjxl issue?

If not we need to rebuild the package to build against this newer ffmpeg.

satmandu avatar Mar 27 '25 08:03 satmandu

This issue has gone 120 days without comment. To avoid abandoned issues, it will be closed in 21 days if there are no new comments. If you're the original submitter of this issue, please comment confirming if this issue still affects you in the latest release with crew update && yes | crew upgrade, or close the issue if it has been fixed. If you're another user also affected by this bug, please comment confirming so. Either action will remove the stale label. This bot exists to prevent issues from becoming stale and forgotten. Chromebrew is always moving forward, and bugs are often fixed as side effects of other changes. We therefore ask that bug report authors remain vigilant about their issues to ensure they are closed if fixed, or re-confirmed - perhaps with fresh logs or reproduction examples - regularly.

github-actions[bot] avatar Jul 26 '25 03:07 github-actions[bot]