** Also affects: mir
Importance: Undecided
Status: New
** Changed in: mir
Status: New => In Progress
** Changed in: mir
Milestone: None => 0.10.0
** Changed in: mir
Assignee: (unassigned) => Michael Terry (mterry)
** Changed in: mir (Ubuntu)
Status: In Progress
** Branch linked: lp:~mterry/mir/fix-turkish
--
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching subscriptions: Ubuntu Translations bug mail
https://bugs.launchpad.net/bugs/1398984
Title:
Bootl
** Changed in: mir (Ubuntu)
Status: New => In Progress
** Changed in: mir (Ubuntu)
Assignee: (unassigned) => Michael Terry (mterry)
--
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching
This is from Mir's conversion of environment variables into program
options. It takes MIR_SERVER_PROMPT_FILE from unity8's upstart job and
converts it into "prompt-fIle" which causes the following error:
terminate called after throwing an instance of
'boost::exception_detail::clone_impl
>'
wh
I'm going to change this but to unity8, since that is what is failing to
come up, not the system settings. I'm betting that the system
settings/wizard are correctly setting Turkish locale, then unity8 can't
deal with it.
** Package changed: ubuntu-system-settings (Ubuntu) => unity8 (Ubuntu)
** P
The fact that this happens in Turkish makes me think it is due
(somewhere) to a common problem with Turkish localization: the "Turkish
i problem" [1].
Basically, tolower() or toupper() may not work like someone is
expecting, because they take locale into account.
[1] http://haacked.com/archive/20
** Description changed:
Lately, a member (Ümit) of the XDA Developers forum reported that his Nexus 4
always goes into a bootloop when he sets the system language to Turkish.
It doesn't matter whether he sets it in the system settings wizard which is
shown on first boot or in the system sett
7 matches
Mail list logo