6 replies

Error in SSH MOTD after updating to Bazzite Stable (F41.20241210)

Hi,

Have just updated to the latest stable and now get this error when logging in via SSH

"Error: invalid character '}' looking for beginning of object key string"

Is there somewhere better I should be posting issues?

Thanks very much.

HikariKnight•12/10/24, 6:16 PM

already being worked on thanks

its an error related to accent colors for the motd and the issue has already been found.

Robert•12/10/24, 8:07 PM

Yeah there’s an extra , in the json. It’s happening to me too. Just waiting on an update.

Yojimbosan•12/11/24, 5:50 AM

You can workaround by choosing a different accent-color in gnome settings; the theme files for purple (default), pink and red are broken, but blue, green, orange, slate, teal or yellow are OK.
gsettings set org.gnome.desktop.interface accent-color greengsettings set org.gnome.desktop.interface accent-color green would fix the error at the cost of possibly switching other elements to green (but I'm not aware of this setting being used anywhere else)

Yojimbosan•12/11/24, 5:51 AM

I logged https://github.com/ublue-os/bazzite/issues/1974 but I didn't see https://github.com/ublue-os/bazzite/issues/1972 as it was already closed

GitHub

MOTD display error; Error: invalid character '}' looking for beginn...

Describe the bug When I start a terminal to run bash, I receive an error message Error: invalid character '}' looking for beginning of object key string Or, you can invoke /usr/libexec/ublu...

GitHub

Error when booting terminal / TTY · Issue #1972 · ublue-os/bazzite

Describe the bug Getting the following error whenever I open my terminal in Gnome. Error: invalid character '}' looking for beginning of object key string I tested and I also see this under...

Yojimbosan•12/11/24, 5:54 AM

Ironically I had to fix the error locally before getting the MOTD to tell me where to report issues to

Error in SSH MOTD after updating to Bazzite Stable (F41.20241210)

Similar Threads

Similar Threads

Similar Threads