Closed Bug 1638218 Opened 4 years ago Closed 4 years ago

Search Service fails to start for LANG=zh_CN.gb18030

Categories

(Firefox :: Search, defect, P3)

76 Branch
defect

Tracking

()

VERIFIED FIXED
Firefox 79
Tracking Status
firefox78 --- wontfix
firefox79 --- verified

People

(Reporter: aswjh, Unassigned)

References

Details

(Whiteboard: [fixed by bug 1640131])

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

Steps to reproduce:

LANG=zh_CN.gb18030 firefox

Actual results:

no search.json* file generated in .mozilla/firefox/5cvlt8zl.default-release
and type the url "163.com", type enter, nothing is done.
must type "https://www.163.com", works well.

but LANG=C firefox or LANG=zh_CN.utf8 firefox works well.

my locale:
locale -a
C
en_US.utf8
POSIX
zh_CN.gb18030
zh_CN.utf8

Expected results:

an search.json* file generated in .mozilla/firefox/5cvlt8zl.default-releaseand
type the url 163.com, and type enter, will connect the url.

Summary: search.json → no search.json* file generated

Hi, aswjh!

Thanks for your contribution!

Could you be more specific on what are you trying to achieve and what are the exact steps to reproduce this?

Regards,

Flags: needinfo?(aswjh)

manjaro-xfce-20.0.1-200511-linux56.iso on virtualbox, vi /etc/locale.gen, then locale-gen:

an empty firefox profile dir, run LANG=zh_CN.gb18030 firefox

Flags: needinfo?(aswjh)

Hi, aswjh!

Thanks for your quick response!

I've tried entering the mentioned URL on Ubuntu 20, Ubuntu 18 and Windows 10, using Firefox Nightly 78.0a1 (2020-05-21) (64-bit)

On all OSs I'm having the same results. Also, I went ahead and tested the URL on Chrome, where I could also reproduce the issue.

The URL doesn't get saved till you enter the full URL, (with either http or www). Beyond that, I couldn't find the search.json file which I assume is the one that saves the re-direction to avoid writing the full URL each time you want to get into any site.

Since this is also reproducible on Chrome I'm led to believe this issue may be related to the URL itself but just to be safe I'll add product and component to this ticket in the hope that someone with specific knowledge on the matter can give some advice on this. Please, feel free to add any other information here on a thread.

Also, please let us know if this issue is reproduced in the latest Nightly edition. You can download it from here: https://nightly.mozilla.org/
Once you have all this information, please let us know so we can continue investigating.

Regards,

Severity: -- → S4
Component: Untriaged → Widget: Gtk
Product: Firefox → Core

This seems more related to the url bar than gtk. Marco do you know the right component for this?

Flags: needinfo?(mak)
Component: Widget: Gtk → Search
Flags: needinfo?(mak)
Product: Core → Firefox

66.0.5 is ok. has problem since 67.0, until 78

if copy search.json from 66 profile, 67 works well too.

Depends on: 1640131

Thank you for the report, I tested this out on my linux set-up and found the following error in the browser console on startup:

_init: failure initializing search: TypeError: malformed UTF-8 character sequence at offset 2
toString@resource://gre/modules/osfile/osfile_unix_allthreads.jsm:113:43
_readCacheFile@resource://gre/modules/SearchService.jsm:1686:7

What's happening is that we're failing to correctly handle the error message for logging about the cache file not being present on startup. This then causes the search service to break, causing the effect you see.

I've filed bug 1640131 about the specific issue, as this could cause more errors across Firefox. Keeping this one here so that we can keep the specific issue in a relevant area to make it easier to find.

Status: UNCONFIRMED → NEW
Ever confirmed: true
Priority: -- → P3
Summary: no search.json* file generated → Search Service fails to start for LANG=zh_CN.gb18030

Reporter, how did you end up running with zh_CN.gb18030? Surely it has never been the default in any Manjaro configuration and cannot have been reached by upgrading since the beginning of Manjaro, since Manjaro didn't even exist at the time when the older distros migrated to UTF-8 locales.

Flags: needinfo?(aswjh)

I have been used to using gb18030, because of the poor utf8 support on windows in the past.

Flags: needinfo?(aswjh)
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
Whiteboard: [fixed by bug 1640131]
Target Milestone: --- → Firefox 79

thanks

Hi, sorry I couldn´t reproduce this! Still getting stuck after trying to reach 163.com. I don´t know if I'm hitting the wrong version.

Since we could not reproduce this issue, aswjh, would you please confirm the fix?

Thank you!

Flags: needinfo?(aswjh)

yes, fixed, 79.0a1

Flags: needinfo?(aswjh)

Thank you for the confirmation!

Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.