[Bug 1849254] [NEW] Noto Sans Mono Bold not available from /etc/fonts/local.conf

2019-10-21 Thread Jeff Zignego
Public bug reported:

I tried to change my monospace font to "Noto Sans Mono Bold" in 
/etc/fonts/local.conf but that didn't have an effect so I did a little digging. 
First I ran 
$ sudo fc-cache -f -v && sudo dpkg-reconfigure fontconfig fontconfig-config

Which succeeded, then: 
$ fc-list :style=bold  | grep -i notosansmono
>/usr/share/fonts/truetype/noto/NotoSansMono-Bold.ttf: Noto Sans Mono:style=Bold

So then:
$fc-query /usr/share/fonts/truetype/noto/NotoSansMono-Bold.ttf | less   
  
which seemed to return a normal looking result similar to:
$fc-query /usr/share/fonts/truetype/noto/NotoSansMono-Regular.ttf | less
  

Then I ran:
$ fc-match -s "monospace" | grep -i bold
>DejaVuSansMono-Bold.ttf: "DejaVu Sans Mono" "Bold"
>MathJax_Fraktur-Bold.otf: "MathJax_Fraktur" "Bold"
>padmaa-Bold.1.1.ttf: "padmaa-Bold.1.1" "Bold.1.1"
>DejaVuSans-BoldOblique.ttf: "DejaVu Sans" "Bold Oblique"

Which obviously isn't right since it isn't in that list. Also:
$fc-match -s "NotoSansMono" | grep -i notosansmono
>NotoSansMono-Regular.ttf: "Noto Sans Mono" "Regular"


My system is up to date and here is my version:
$lsb_release -a
lsb_release:
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.3 LTS
Release:18.04
Codename:   bionic

$uname -a
>Linux 9343 4.15.0-65-generic #74-Ubuntu SMP Tue Sep 17 17:06:04 UTC 2019 
>x86_64 x86_64 x86_64 GNU/Linux

** Affects: fonts-noto (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1849254

Title:
  Noto Sans Mono Bold not available from /etc/fonts/local.conf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-noto/+bug/1849254/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1736808] Re: Changes to overlay lowerdir produce kernel file-caps error

2018-10-22 Thread Jeff Zignego
I think I just ran into this bug on bionic. I was building a yocto distribution 
like this user here:
https://www.spinics.net/lists/linux-unionfs/msg05363.html

I was I was two point releases behind at :
$ uname -a
Linux ses-docker50c 4.15.0-34-generic #37-Ubuntu SMP Mon Aug 27 15:21:48 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux 

So I updated that machine to 4.15.0-36-generic, but I wanted to know
what the status of this was. I think as a workaround I will use a docker
mount for the entire build directory.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1736808

Title:
  Changes to overlay lowerdir produce kernel file-caps error

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736808/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1736808] Re: Changes to overlay lowerdir produce kernel file-caps error

2018-10-22 Thread Jeff Zignego
It looks like the bug was fixed upstream here:

https://github.com/torvalds/linux/commit/355139a8dba446cc11a424cddbf7afebc3041ba1

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1736808

Title:
  Changes to overlay lowerdir produce kernel file-caps error

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1736808/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs