Default language changed after update

[mrbaloo1337]

@sdetweil
Sorry, it looks good as far as I can see. I the texts in that file is the only workning translations. For example:
“FEELS”: “Känns som {DEGREE}”,

That´s a correct translation and works in Weather module, but weekdays is in Sami. See picture below.

That´s the same problem for every module. Hope you understand what I mean :)
I think that the connection to “sv” is broken and points to Sami instead of Swedish.

[mrbaloo1337]

@sdetweil
Sorry missed, it is version 2.28.0

[sdetweil]

@mrbaloo1337 I meant before this release.

[mrbaloo1337]

@sdetweil

No issues before upgrade, is it possible to downgrade to previous version?

[sdetweil]

@mrbaloo1337 yes, but, I asked you to tell me what that version was.

I am out of the house for another hour

[mrbaloo1337]

@sdetweil

I wrote that earlier, it is 2.28.0.

No worries, if you have any suggestions to my problem I will wait :)
On Saturday I leave for vacation so I hope it will be solved until that, otherwise I can´t sleep

[sdetweil]

@mrbaloo1337
2.28.0 is the current release number
I want to know what version you were running prior to this one

if you upgraded with my upgrade script, you can look in the log file
~/MagicMirror/installers/upgrade.log

[mrbaloo1337]

I was running on 2.27.0
As far as I found out Sami is listed as “SE” and Swedish is “SV” in the ISO list for language. If that is for any help?

This is the log file:

Upgrade started - Wed Jul  3 13:27:27 CEST 2024
system is Linux raspberrypi 6.6.31+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.6.31-1+rpt1 (2024-05-29) aarch64 GNU/Linux
doing test run = true, NO updates will be applied!
the os is Distributor ID: Debian Description: Debian GNU/Linux 12 (bookworm) Release: 12 Codename: bookworm
Check current Node installation ...
Node currently installed. Checking version number.
Minimum Node version: v20.9.0
Installed Node version: v20.8.0
Node should be upgraded.
Node.js upgrade defered, doing test run
Check current NPM installation ...
NPM currently installed. Checking version number.
Minimum npm version: V10.1.0
Installed npm version: V10.1.0
No npm upgrade necessary.

saving custom.css
remote name = origin
upgrading from version 2.27.0 to 2.28.0
fetching latest revisions
git fetch rc=0
current branch = master
On branch master
Your branch is behind 'origin/master' by 1 commit, and can be fast-forwarded.
  (use "git pull" to update your local branch)

Changes not staged for commit:
  (use "git add <file>..." to update what will be committed)
  (use "git restore <file>..." to discard changes in working directory)
	modified:   package-lock.json

Untracked files:
  (use "git add <file>..." to include in what will be committed)
	icscalender/
	run-start.sh

no changes added to commit (use "git add" and/or "git commit -a")
there are 1 local files that are different than the master repo

   package-lock.json

save/restore files selection = n
restoring package-lock.json from repo
skipping restore for package-lock.json, doing test run
test merge result rc='' , if empty, no conflicts
skipping merge, only test run

Checking for modules with removed libraries
downloading dumpactivemodules script


updating dependencies for active modules with package.json files

	processing for module MMM-MQTT please wait

	----------------------------------

	skipped processing for MMM-MQTT, doing test run

	processing complete for module MMM-MQTT

	processing for module MMM-CalendarExt3 please wait

	----------------------------------

	skipped processing for MMM-CalendarExt3, doing test run

	processing complete for module MMM-CalendarExt3
restoring custom.css
removing git alias
Upgrade ended - Wed Jul  3 13:27:53 CEST 2024

[mrbaloo1337]

Hi again, for some magical reason i solved it.
I had a module MMM-jast. Wich is the last one I installed before upgrade. For test, I took a backup of the config without that module.
Everything was in Swedish again, added my config for that module in the backupconfig file. Everything works as before.

I can´t point what caused the error, but now it works again. Maybe the file ended up corrupt in the upgrade…

Thanks for your response and time, have a good day!

[sdetweil]

@mrbaloo1337 very interesting. we don’t touch the config file . I don’t copy/restore it.