Closed Bug 1535121 Opened 7 years ago Closed 5 years ago

Unrecognized command line flag --UILocale

Categories

(Thunderbird :: General, defect)

defect

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: mbndr, Unassigned)

References

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:65.0) Gecko/20100101 Firefox/65.0

Steps to reproduce:

System: Archlinux 64bit, Thunderbird: 60.5.3
A German Language Pack is installed

I wanted to start Thunderbird with the German (de) locale setting:
thunderbird --UILocale de

Actual results:

Following warning was shown:
Warning: unrecognized command line flag -UILocale
The program started in English.

Expected results:

The German language should've been used.

This line is displayed in the help text (thunderbird --help):
--UILocale <locale> Start with <locale> resources as UI Locale.

If it's my fault and I misunderstood the usage of the flag UILocale there should be another warning because the help text says this flag exists.

TB68.0a1 (2019-04-13) (64-bit), OpenSUSE 15.0
Starting Thunderbird from a shell with the --UIlocale de command line option doesn't produce an error message here.
/opt/thunderbird_daily/thunderbird -P daily --UIlocale de

I'm not exactly sure though what that is supposed to do with an en-us version of Thunderbird.
Can you try with the daily version?

Flags: needinfo?(mbndr)

mbndr?

Component: Preferences → General
Whiteboard: [closeme 2019-05-15]

Resolved per whiteboard

Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Flags: needinfo?(mbndr)
Resolution: --- → INCOMPLETE
Whiteboard: [closeme 2019-05-15]

I am able to reproduce this issue with Thunderbird daily:

$ thunderbird --UILocale hu
Warning: unrecognized command line flag -UILocale

I am using up-to-date daily build on 64-bit Ubuntu Linux.

I am also able to reproduce this problem with the Thunderbird 60.7 shipped with Ubuntu.

I have tried all permutations I could think of for the command line option -- one hyphen or two, "UILocale" vs "uilocale", and none of them work.

Status: RESOLVED → REOPENED
Ever confirmed: true
Resolution: INCOMPLETE → ---
Status: REOPENED → NEW

It seems that this option was removed in bug 1347306.

See Also: → 1658191

OP's problem and bug 1658191 are gone in my testing of 85 beta

Severity: normal → S4
Status: NEW → RESOLVED
Closed: 7 years ago5 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.