Ubuntu
command-not-found package

command-not-found gets stuck on locales with non-English-like collation rules

Bug #1886618 reported by Erkin Alp Güney
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
command-not-found (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

The bug in question: https://askubuntu.com/q/1142923/162831
Namely, cnf-update-db takes forever and eats almost all your disk time if your locale has different collation rules from English such as different sorting and/or case conversion.
A workaround by supplying a C locale: https://askubuntu.com/a/1147303/162831

See original description
Revision history for this message
Erkin Alp Güney (erkinalp9035) wrote :

Confirmed by me.

Changed in apt (Ubuntu):
status: New → Confirmed
description: updated
Erkin Alp Güney (erkinalp9035)
description: updated
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report, what Ubuntu version and locale do you use? It's a bit weird, it was just broken on some locales there would be other reports about the issue...

Julian Andres Klode (juliank)
affects: apt (Ubuntu) → command-not-found (Ubuntu)
Revision history for this message
Erkin Alp Güney (erkinalp9035) wrote :

20.04 with stock EFI kernel (w.o. secure boot) in tr_TR.UTF-8.

Revision history for this message
Erkin Alp Güney (erkinalp9035) wrote :

The original tester also seems to be Turkish, looking at his name, "Ömer Faruk Doğan" (Ask ubuntu user #403301).

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.