[Bug 2277345] New: NotoSansMono[wght].ttf file name causes scripts
with failglob enabled to fail
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2277345
Bug ID: 2277345
Summary: NotoSansMono[wght].ttf file name causes scripts with
failglob enabled to fail
Product: Fedora
Version: 40
Hardware: All
OS: Linux
Status: NEW
Component: google-noto-fonts
Severity: medium
Assignee: tagoh(a)redhat.com
Reporter: hartsjc(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: fonts-bugs(a)lists.fedoraproject.org,
i18n-bugs(a)lists.fedoraproject.org,
petersen(a)redhat.com, pwu(a)redhat.com, tagoh(a)redhat.com
Target Milestone: ---
Classification: Fedora
shopt failglob
If set, patterns which fail to match filenames during pathname expansion result
in an expansion error.
Using this feature is good practice in scripts as helps prevent scripting
mistakes; however, having file name with square brackets causes failures. And
with Fedora 40 upgrade seems
google-noto-sans-mono-vf-fonts-20240301-2.fc40.noarch has added one with:
/usr/share/fonts/google-noto-vf/NotoSansMono[wght].ttf
Reproducible: Always
Steps to Reproduce:
1. Causes globs that don't expand to cause errors
$ shopt -s failglob
2. Try use files from rpm as variable, and fail
$ for file in $(rpm -q --list google-noto-sans-mono-vf-fonts) ; do
[[ -f "/${file}" ]] || echo "${file}"
done
-bash: no match: /usr/share/fonts/google-noto-vf/NotoSansMono[wght].ttf
3. Note the RC
$ echo $?
1
4. Or even command line
$ rpm -qf /usr/share/fonts/google-noto-vf/NotoSansMono[wght].ttf
-bash: no match: /usr/share/fonts/google-noto-vf/NotoSansMono[wght].ttf
$ rpm -qf '/usr/share/fonts/google-noto-vf/NotoSansMono[wght].ttf'
google-noto-sans-mono-vf-fonts-20240301-2.fc40.noarch
Actual Results:
-bash: no match: /usr/share/fonts/google-noto-vf/NotoSansMono[wght].ttf
Expected Results:
no error accessing files with failglob shopt enabled
started fedora 40 upgrade, as daily script of mine fails because this file is
included in initramfs too.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2277345
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-...
1 day, 4 hours
[Bug 2253923] [abrt] setroubleshoot:
_FcObjectLookupOtherTypeByName(): python3.12 killed by SIGABRT
by bugzilla@redhat.com
https://bugzilla.redhat.com/show_bug.cgi?id=2253923
Sylvain Arth <sylvain(a)gwenved.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags|needinfo?(sylvain(a)gwenved.o |
|rg) |
--- Comment #15 from Sylvain Arth <sylvain(a)gwenved.org> ---
I'd like to answer, to the question "How to reproduce" because I really can't.
Nowadays; all my Fedora OS machines are running as virtual machines on two
different Windows servers.
The main purpose of those instances is to act as servers for mails, DNS, NTP
and many other usual servers like that.
Punctually, I use them for comparison about possibly different behaviour about
"mock-up software" of my personal coding in Ada complied with GNAT.
In other words, I usually just check by emails that all those V-machines and
servers are still in good health.
I very rarely fall into the bug I reported, whilst I'm currently doing anything
on.
Most of the time, It's after reboot-startup (clean or dirty because of some
failure of the hosting PC), at login time I get the warning about bugs detected
by Fedora.
I could ignore them, but my thought is that it could help bug solving, with
providing more data, even "raw" ones.
I very know this is not quite at all the best bug reporting way.
But I also know (I was famous about that prior I retired) my "bug catcher"
reputation.
In other words, I tend to fall into bug traps other people never fall in.
I ignore why about this, I just know it's a fact.
I just suspect it's because I've my own way to do things that is often not the
"most common way to do things".
But if my reports are rather totally useless, just tell me that's the actual
case.
If so, I will totally stop top sending such kind of reports, to only report
those I'm able to tell something like a clue about "how to reproduce,
possibly".
Regards
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=2253923
Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-...
1 week, 1 day