Starship config warnings

When I start my Alacritty, these errors showed up.

[WARN] - (starship::configs::starship_root): Unknown config key 'docker'
[WARN] - (starship::configs::starship_root): Did you mean 'docker_context'?
[WARN] - (starship::configs::starship_root): Unknown config key 'haskell'
[WARN] - (starship::configs::starship_root): Did you mean 'shell'?
[WARN] - (starship::configs::starship_root): Unknown config key 'docker'
[WARN] - (starship::configs::starship_root): Did you mean 'docker_context'?
[WARN] - (starship::configs::starship_root): Unknown config key 'haskell'
[WARN] - (starship::configs::starship_root): Did you mean 'shell'?
[WARN] - (starship::configs::starship_root): Unknown config key 'docker'
[WARN] - (starship::configs::starship_root): Did you mean 'docker_context'?
[WARN] - (starship::configs::starship_root): Unknown config key 'haskell'
[WARN] - (starship::configs::starship_root): Did you mean 'shell'?
[WARN] - (starship::configs::character): Unknown config key 'use_symbol_for_status

I reinstalled starship and replaced it with starship-git two times to be sure, but no luck. Updated my config through Garuda Assistant, discovered that paleofetch was replaced with neofetch, installed it, and this output remains. When I echo $STARSHIP_CONFIG there is no output. I discovered that there were no Starship.toml in my .config directory. Copied starship config from Garuda's Gitlab and now I'm fine. Posted this just in case somebody is unable to handle it by themselves.

6 Likes

Config syntax changed in 0.52, the shipped starship.toml was fixed already some time ago so you did just right by getting the new default one :grin:

3 Likes

Thanks for your help.

2 Likes

Hello everybody. Im on a fresh install of Garuda Linux. Im having problems with the Terminal. Everytime i open up a new Terminal i get these specific errors everytime

[WARN] - (starship::configs::starship_root): Unknown config key 'docker'
[WARN] - (starship::configs::starship_root): Did you mean 'docker_context'?
[WARN] - (starship::configs::starship_root): Unknown config key 'haskell'
[WARN] - (starship::configs::starship_root): Did you mean 'shell'?
[WARN] - (starship::configs::starship_root): Unknown config key 'docker'
[WARN] - (starship::configs::starship_root): Did you mean 'docker_context'?
[WARN] - (starship::configs::starship_root): Unknown config key 'haskell'
[WARN] - (starship::configs::starship_root): Did you mean 'shell'?
[WARN] - (starship::configs::starship_root): Unknown config key 'docker'
[WARN] - (starship::configs::starship_root): Did you mean 'docker_context'?
[WARN] - (starship::configs::starship_root): Unknown config key 'haskell'
[WARN] - (starship::configs::starship_root): Did you mean 'shell'?
[WARN] - (starship::configs::character): Unknown config key 'use_symbol_for_status'

Is there a fix for that? I already searched the forum.

sudo pacman -Syu starship 

did nothing for me.

1 Like

Alright guys, something in the starship syntax changed introduced in the new update 0.52 (the reason why starship-git had this a while back in fact), a fixed version of the prompt config can be found in /etc/skel/.
Apply the changes:

cp /etc/skel/.config/starship.toml ~/.config/starship.toml

That applies instantly, no need to relog. :slight_smile:

36 Likes

Nope :frowning:

cp /etc/skel/.config/starship.toml ~/.config/starship.toml
cp: '/home/sgs/.config/starship.toml' ├╝berschreiben?

IDK, y,j, yes, ja.
I rename old .toml
cp and same Warnings in konsole.

6 Likes

Doesn't do anything for me :confused:

1 Like

It should now though, after updating :face_with_monocle:

5 Likes

Thank you very much. :slight_smile:

1 Like

I used config from Gitlab directly. Forgot that /etc/skel exists, oops

2 Likes

didn't worked for me

1 Like

This worked for me but a couple of things might help it work for you. do the sudo pacman -Syu starship first. Then copy the /etc/skel file. Then it will work (at least it did for me) Thanks for the quick fix guys!

8 Likes

Yeah this helped!

thanks work for me