Public bug reported:
I have a VPS upgraded to Ubuntu 22.04 with a rather peculiar network
setup. My /etc/netplan/90-vz-ens3.yaml is
network:
ethernets:
ens3:
addresses:
- 80.209.x.y/32
- 10.209.x.y/8
- 2a02:7b40:x:y::1/128
dhcp4
I can reproduce the pairing loss by suspending my laptop. The
kernel: Bluetooth: hci0: Invalid link address type 1 for
60:ab:d2:43:49:4d
message appears on resume, even when the headset is not connected at
that moment (and is in fact switched off).
Also, the link key changed after my last p
That stackexchange link suggests
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=aae6b81260fd9a7224f7eb4fc440d625852245bb
might be to blame for this. I'm not sure how to test that.
Also, this bug might be a duplicate of
https://bugs.launchpad.net/ubuntu/+source/bluez
One notable difference between 24.04 (kernel 6.8.0) and 24.10 (kernel
6.11.0) is that the new kernel is outputting
spal. 11 09:44:52 blynas kernel: Bluetooth: hci0: Invalid link
address type 1 for 60:ab:d2:43:49:4d
These messages never showed up on 24.04.
Searching for that message led me to
Public bug reported:
I've Bose QuietComfort 35 II bluetooth headphones/headset that I've been
using with Ubuntu for several years now. Since I upgraded to Ubuntu
24.10 yesterday, the headset refuses to connect to Ubuntu until I pair
it again, every time.
This is how things worked with 24.04 LTS:
This might be https://github.com/weechat/weechat/issues/2046, caused by
a bug in Python 3.12.
I have both Perl and Python plugins loaded, and my Valgrind log shows
that the memory that the Perl plugin is trying to free during unload was
freed by _PyObject_Free earlier.
** Bug watch added: github.
> Everyone from Russian translators team can fix this issue by simply
changing translation to '24h' at https://translations.launchpad.net/
It would also be a good idea to fix the upstream translations as well,
at https://l10n.gnome.org/.
(I've done so for the Lithuanian translation.)
--
You rec
Public bug reported:
I've used weechat twice after upgrading to Ubuntu 24.04 LTS. Both times
I got a segfault when I tried to /quit it.
coredumpctl gdb weechat gives me this stack trace:
Core was generated by `/usr/bin/weechat'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0
Yeah, that makes sense.
(Of course constant spamming is more likely to result in a translation
fix ;)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2064656
Title:
gnome-shell spams the journal with
Probably a duplicate of bug 2061687, given the empty pw-dump output.
Does systemctl --user restart wireplumber.service fix it for the
remainder of the login session?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpa
Public bug reported:
After upgrading to Ubuntu 24.04 LTS I ran journalctl -f and noticed that
gnome-shell was spamming errors at the rate of 12 lines every second:
geg. 02 18:29:19 blynas gnome-shell[3980]: Failed to parse translated string
'„24h“' for key 'clock-format' in schema 'org.gnome.de
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #3451
https://gitlab.gnome.org/GNOME/mutter/-/issues/3451
** Also affects: mutter via
https://gitlab.gnome.org/GNOME/mutter/-/issues/3451
Importance: Unknown
Status: Unknown
--
You received this bug notification because y
*** This bug is a duplicate of bug 2063049 ***
https://bugs.launchpad.net/bugs/2063049
(Confirming that I have ozone-platform-hint set to Auto instead of
Default in chrome://flags.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The syscall=330, the mknod denial, the /etc/vulkan/ denials are also
produced by the working chromium snap.
The /etc/igfx_user_feature.txt denial only shows up with the broken
chromium snap.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
(sorry, copy/paste fail)
> dmesg has a bunch of repeated
bal. 24 09:40:04 blynas kernel: audit: type=1400 audit(1713940804.105:20243):
apparmor="DENIED" operation="open" class="file"
profile="snap.firefox.firefox" name="/etc/igfx_user_feature.txt" pid=7070
comm="FSBroker7944" requested_mask="r
dmesg has a bunch of repeated
`snap revert chromium` reverted to 123.0.6312.122, which works fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063304
Title:
chromium 124.0.6367.60 fails to draw
apport information
** Attachment added: "Snap.Info.gtk-common-themes.txt"
https://bugs.launchpad.net/bugs/2063304/+attachment/5769956/+files/Snap.Info.gtk-common-themes.txt
** Tags added: snap
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
apport information
** Attachment added: "Snap.Info.gnome-42-2204.txt"
https://bugs.launchpad.net/bugs/2063304/+attachment/5769955/+files/Snap.Info.gnome-42-2204.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
apport information
** Attachment added: "Snap.Info.cups.txt"
https://bugs.launchpad.net/bugs/2063304/+attachment/5769954/+files/Snap.Info.cups.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/206
apport information
** Attachment added: "Snap.Info.core.txt"
https://bugs.launchpad.net/bugs/2063304/+attachment/5769952/+files/Snap.Info.core.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/206
apport information
** Attachment added: "Snap.Info.chromium.txt"
https://bugs.launchpad.net/bugs/2063304/+attachment/5769951/+files/Snap.Info.chromium.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
apport information
** Attachment added: "Snap.Connections.txt"
https://bugs.launchpad.net/bugs/2063304/+attachment/5769950/+files/Snap.Connections.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
apport information
** Attachment added: "Snap.Info.core20.txt"
https://bugs.launchpad.net/bugs/2063304/+attachment/5769953/+files/Snap.Info.core20.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/2063304/+attachment/5769948/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063304
apport information
** Attachment added: "Snap.ChromiumPrefs.txt"
https://bugs.launchpad.net/bugs/2063304/+attachment/5769949/+files/Snap.ChromiumPrefs.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/2063304/+attachment/5769947/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/
apport information
** Attachment added: "HookError_chromium_browser.txt"
https://bugs.launchpad.net/bugs/2063304/+attachment/5769946/+files/HookError_chromium_browser.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
Public bug reported:
Since the last snap update to 124.0.6367.60, I cannot use chromium. It
launches fine, but the window itself is fully transparent (e.g.
triggering the Overview makes it look like a piece of my wallpaper).
I have Intel graphics and use a Wayland session on Ubuntu 23.10.
At fi
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/2063304/+attachment/5769945/+files/Dependencies.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2063304
I have the same problem but with Intel video. Chromium 124.0.6367.60
shows up camouflaged as my desktop wallpaper after the last snap update.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1967488
Tit
Happened to me today, when I unplugged the USB C cable connecting my
ThinkPad to the dock with an external monitor plugged in, and then
closed the laptop lid to put it to sleep.
journalctl shows
```
geg. 27 15:53:39 blynas gnome-shell[3815]:
meta_monitor_manager_get_logical_monitor_from_number:
I can no longer observe this on Ubuntu 22.04 LTS (Wayland session) with
chromium snap 101.0.4951.64 (1993).
(An xeyes test confirms that the selenium-driven chromium is using
Xwayland.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug also affects 21.10, FWIW.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1930371
Title:
top bar displayed on top of a fullscreen window that gets moved from
one monitor to another
To mana
Public bug reported:
Nothing very interesting here, the /boot partition on this server is
very small (240M) and the upgrade ran out of space while generating an
initramfs image.
I was able to recover by removing the oldest linux-image package.
I was surprised that do-release-upgrade didn't check
I've seen this three times now on Ubuntu 21.10 (GNOME 40). I don't
recall ever seeing it on Ubuntu 20.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1532508
Title:
Screen contents revealed brief
https://launchpad.net/ubuntu/+archivemirrors shows four mirrors in
Lithuania, all "up to date".
Two of them actually are. One (Vilnius University) has a focal-
updates/Packages.gz from 2021-05-04 with libssl-dev version
1.1.1f-1ubuntu2.3, one (LitNET) has a focal-updates/Packages.gz from
2021-07-
On a closer look it may just be a mirror inconsistency.
There's no Phased-Update-Percentage field in
/var/lib/apt/lists/lt.archive.ubuntu.com_ubuntu_dists_focal-
updates_main_binary-amd64_Packages for the libssl-dev entry, and the
only available version is 1.1.1f-1ubuntu2.4.
** Changed in: apt (U
Public bug reported:
I have two Vagrant boxes: one with Ubuntu 18.04 LTS, one with Ubuntu
20.04 LTS. Both currently refuse to install libssl-dev for me:
vagrant@ubuntu2004:~$ sudo apt install libssl-dev
Reading package lists... Done
Building dependency tree
Reading state information... Do
Ideally, I'd wish it not to stop sshd when /boot/efi becomes
unavailable. Or at least bring back the services it stopped when the
emergency shell is canceled.
More practically, and more on topic to the original reason for this bug
report, I'd like it if stopping the emergency shell would print a
Looking at the journal, I think the sequence of events is:
- SSD fails last Friday
- I log in today over ssh, start messing around
- I notice that collectd is not running (since Friday), try to `sudo systemctl
start collectd`
- systemd tries to bring up collectd's dependency local-fs.target, whic
Public bug reported:
An SSD that held my /boot/efi partition failed, took down local-fs.target,
which brought up emergency.target. I ended up with no ssh access, and a
message on the local console telling me
to press Enter to get a root shell, or press Ctrl-D to continue booting
normally. The
Filed upstream at https://gitlab.gnome.org/GNOME/gnome-
shell/-/issues/4351
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #4351
https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4351
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
Public bug reported:
I have two monitors: the laptop's internal one (primary), and an
external LCD positioned above the it.
I have configured mpv to be the default video player in Nautilus. I
have also configured ~/.config/mpv/mpv.conf to have 'fullscreen=yes'.
Steps to reproduce:
- click on a
Bug still there in 18.04.5 LTS. Had an unattended security upgrade of
openvpn on May 5, which shut down the old ovpn-server:
| May 05 06:14:19 fridge ovpn-server[3384]: event_wait : Interrupted system
call (code=4)
| May 05 06:14:19 fridge ovpn-server[3384]: /sbin/ip route del 10.8.0.0/2
Forwarded upstream to https://github.com/fwupd/fwupd/issues/3186
** Bug watch added: github.com/fwupd/fwupd/issues #3186
https://github.com/fwupd/fwupd/issues/3186
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
/usr/share/ecryptfs-utils/ecryptfs-record-passphrase appears to be a
text file:
_Name: Record your encryption passphrase
Priority: High
OnlyAdminUsers: False
DisplayIf: test -e $HOME/.ecryptfs/wrapped-passphrase -a ! -e
$HOME/.ecryptfs/.wrapped-passphrase.recorded
Terminal: True
GettextDomain: ec
Public bug reported:
Upgraded my Ubuntu 20.10 to 21.04 with sudo do-release-upgrade -d,
rebooted, and got this window in my face a couple of minutes after
booting (see attached image).
It is shown by update-notifier and says (null), then gives me an option
to [Perform this action].
lsof -p $(pid
I did a fundamental mistake and changed two things at a time:
1. deleted the duplicate Linux-Firmware-Updater boot entry with efibootmgr -B
-b 0002
2. decided to apply the two firmware upgrades separately
I ran fwupdmgr upgrade twice, selected the Intel ME upgrade first,
rejected the System Firm
I'm now reliably in this situation:
efibootmgr shows
| BootCurrent: 0003
| Timeout: 0 seconds
| BootOrder:
0003,001A,,0018,0019,001B,001C,001D,001E,001F,0020,0021,0002,0027
| Boot* Windows Boot Manager
| Boot0002* Linux-Firmware-Updater
| Boot0003* ubuntu
...
This happened again, while trying to upgrade the Lenovo ThinkPad X390
system firmware from version 1.70 to 1.71. I missed the initial details
again, unfortunately -- didn't see what the computer was doing while
rebooting, came back to see it booted into Windows with the 'ubuntu'
boot menu entry mi
Public bug reported:
== Introduction ==
This is going to sound very similar to bug 1900121, but I believe it's a
different bug.
Today I tried to upgrade the system firmware and the Intel ME firmware
on my ThinkPad X390 with `fwupdmgr upgrade` (after attempting to upgrade
with snap-store failed w
Thank you for the reproducer!
I was about to comment suggesting a race condition, since I have clamav-
freshclam installed on several machines but only one of them reported a
failure. Then I looked closer and realized that my monitoring is
incomplete.
I have clamav-freshclam installed on two bio
My laptop with Ubuntu 20.10 automatically switches to the HDMI output
when I plug in my monitor (via a USB C cable connected to a dock station
connected to the monitor via a HDMI cable).
And then, a second later, it switches to the USB dock's audio output
(which has nothing plugged in), but that's
Public bug reported:
An unattended upgrade upgraded clamav last night, after which clamav-
freshclam failed to start:
# systemctl status clamav-freshclam
● clamav-freshclam.service - ClamAV virus database u
Public bug reported:
A server I have stopped being able to resolve DNS queries. According to
resolvectl status, no DNS servers have been configured.
/etc/netplan/01-netcfg.yaml has networking configuration that looks
correct to me, and if I do 'netplan try', I get working a network.
Somehow syst
Public bug reported:
I've noticed today that collectd tracks disk usage of every version of
every snap, since those are squashfs mounts. There are rather a lot of
those:
$ ls -ld /var/lib/collectd/rrd/$(hostname -f)/df-snap*|wc -l
262
I suggest adding
FSType squashfs
to the block in the
Still a problem in 20.04 LTS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1842432
Title:
service postgrey reload fails
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubu
> After charging battery to 12% and updating by "fwupdmgr upgrade",
computer restart -> show "Check power failure,please insert the power
source or charge the power" -> power on normally.
The error message give the impression that you had the power cable
disconnected and battery at 12% while tryin
If it helps, I have in my notes the full output of `efibootmgr -v` from
Oct 16 with the 'ubuntu' entry missing, and then the full output after I
ran grub-install to recover.
I do not have a full output of `efibootmgr -v` from earlier, but I do
have just the `ubuntu` entry from February, after a li
1. My notes say "LENOVO System firmware 0.1.67 -> 0.1.70, also described
as Lenovo ThinkPad T490s/ThinkPad X390 (W-BIOS) System Firmware 1.70".
I have recorded in my notes that after I attempted the update from snap-
store (at 7% battery), I ran fwupdmgr get-upgrades in a terminal and saw
│ U
It's 2020 and I'm still trying to fix this. Upstream moved to GitHub
so:
- https://github.com/scop/bash-completion/pull/463
- https://github.com/scop/bash-completion/pull/465
fix mutt -f +foo and mutt -f =foo for me on Ubuntu 20.10. On
Ubuntu 18.04 LTS, though, mutt -f =foo remains broken, and
Today this happened again. I installed a bunch of updates with update-
manager, was prompted to reboot, checked with 'snap refresh --list' to
see if there were any snap updates pending (there weren't), and let
update-manager do the reboot.
snapd took 1m30s to shut down.
lapkr. 11 09:08:29 blyna
Public bug reported:
There was a bug in a weechat script in my ~/.weechat/python/autoload,
which triggered apport's exception hook. The apport hook failed with
Error in sys.excepthook:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport_python_hook.py", line 72, in
This is fixed in upstream version 1.0.5, with this commit:
https://git.sesse.net/?p=plocate;a=commitdiff;h=f7dddf5cd31d26be12c4c4d718d257fe012fe368
Looking at https://sources.debian.org/src/plocate/1.0.7-1/debian/changelog/ I
think there may be some other changes worth SRUing:
- make /etc/cron.da
Public bug reported:
$ plocate --help
...
-r, --regexp interpret patterns as basic regexps (slow)
...
$ plocate -r xyzzy
plocate: invalid option -- 'r'
Note that `plocate --regexp xyzzy` works fine.
This is fixed in some upstream version (I tested by pulling in a docker
image of deb
I don't know if you need more confirmations, but upgrading to mutter +
libmitter from groovy-proposed fixed my chromium problem too.
(The only weird bit was how I was unconsensually logged out during the
upgrade, but that could've been plymouth or some other package.)
--
You received this bug no
I do not currently have access to the machine, due to COVID lockdowns.
I haven't changed the theme, so it _should_ be the default for Ubuntu
sessions, i.e. Yaru.
(My current machine doesn't exhibit the problem. Firefox also didn't
have the problem on the machine where I took this screenshot.)
--
It would be nice if snapd would log something about what it's doing to
the journal.
I did run a `snap refresh --list` before rebooting and I saw that a
chromium update was being delayed since chromium was running. I closed
chromium a few seconds before initiating the reboot. Perhaps snapd
thought
Public bug reported:
I installed some updated and was prompted to reboot. The shutdown part
of the reboot took a long time (over 1 minute 30 seconds), and I saw
that systemd was waiting for snapd to shut down cleanly before killing
it with SIGKILL 90 seconds later.
journalctl -b -1 -e shows this
Feels fixed to me too!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1858636
Title:
snapd generates incomplete fontconfig caches, result in emoji
rendering issue in Chromium (and non-snap browsers
I've just upgraded to groovy and hit this bug. For now I'm using socat
as a workaround:
socat abstract-listen:/tmp/.X11-unix/X0,reuseaddr,fork
unix:/tmp/.X11-unix/X0
This works, but is rather slow (and probably also opens a security hole
on multiuser machines).
--
You received this bug not
No crash file in /var/crash, unfortunately.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900107
Title:
fwupd is eating 100% CPU for 30 minutes
To manage notifications about this bug go to:
https:
I wish snap wouldn't lie to me by saying "all snaps are up to date" when
it means "there's an outdated snap but I cannot update it because the
application is running".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
Yes, but I assumed that in order to stop snap-store it was enough to
close its window. Your question made me doubt that, and I see that
pgrep snap-store finds it running.
This probably explains everything, except for one question: how is a
regular user expected to update snap-store? Running pkil
Public bug reported:
snap-store tells me there's an update available for snap-store. I tried
to tell it to update itself, but it says it can't because the
application is currently running. Fair enough, that's not the bug I'm
reporting here, just some background information.
snap refresh --list
A strange thing happened today: snap-software told me there are
important system upgrades available, and one of those was the same
firmware upgrade for the x390 (1.67 -> 1.70) that I was sure I'd already
installed yesterday.
fwupdmgr get-updates and /sys/class/dmi/id/bios_version confirmed that
no
Definitely no custom stuff in /usr/local. This was a fresh install of
20.04 in a loaner laptop while mine was getting its keyboard repaired.
I'll have to boot it up and check /var/crash on Monday. I killed the
misbehaving process with `kill` at the gdb prompt, IIRC. I don't know
what signal it
Public bug reported:
snap-store offered me a system firmware upgrade for my Lenovo ThinkPad
X390. I installed it with fwmgr upgrade [*], which prompted me to
reboot, which I did, and I saw the firmware upgrade go through, and then
it rebooted again -- into Windows.
The UEFI boot menu I get on F1
Public bug reported:
The fan of my laptop started going full-throttle and I ran htop to see
why. I see a /usr/libexec/fwupd/fwupd eating 100% CPU for 29:55
minutes.
According to ps -o pid,lstart,etime,cmd the process was started
yesterday at 22:44. The laptop was suspended yesterday at 23:15 an
So, apport didn't attach the journal, therefore
spal. 16 09:09:34 bigas systemd[1]: Finished Refresh fwupd metadata and update
motd.
...
spal. 16 10:55:37 bigas fwupd[86826]: 07:55:37:0051 GLib-GObject
invalid uninstantiatable type 'GParamInt64' in cast to 'FwupdDevice'
spal. 16 10:55:37
gdb is useless without debug symbols:
__pthread_rwlock_wrlock_full (abstime=0x0, clockid=0, rwlock=0x55af956f1a60) at
pthread_rwlock_common.c:720
720 pthread_rwlock_common.c: No such file or directory.
(gdb) bt
#0 __pthread_rwlock_wrlock_full (abstime=0x0, clockid=0,
rwlock=0x55af956f1a60)
Public bug reported:
When I upgrade Firefox via apt upgrade (or, more often, Update Manager)
and open a new tab, Firefox shows a page telling me that it's been
upgraded and I need to restart it before I can continue browsing.
There's a "Restart Firefox" button. I press it, Firefox quits, and the
Public bug reported:
This is a freshly installed Ubuntu 20.04 LTS system. I apt installed
chromium-browser, which pulled in the snap. I'm in an Ubuntu on Wayland
session.
The file chooser (accessible e.g. by Ctrl+O) in Chromium is missing all
of the icons (see screenshot).
ProblemType: Bug
Dis
Public bug reported:
This looks like a network error:
Download snap "snapd" (9279) from channel "stable" (received an
unexpected http response code (503) when trying to download
https://api.snapcraft.io/api/v1/snaps/download/PMrrV4ml8uWuEUDBT8dSGnKUYbevVhc4_9279.snap)
that happened during do
I once had trouble getting full native resolution on an external
2560x1080 monitor. It turned out to be a problem with the DisplayPort
-> HDMI monitor cable I had (not enough bandwidth without using a custom
reduced frequency mode via xrandr/way harded custom EDID hacks for
wayland), and switching
Public bug reported:
I'm using docker-compose to wrangle a bunch of containers, and quite
often one of my containers hangs.
When I inspect the process with strace, I see it's blocked on write(2,
"...").
/proc/$container_pid/fd/2 is a pipe, the other end of which is managed
by a containerd-shim p
I ended up adding
if [ -n "$PS1" ]; then
# only for interactive sessions please
if [ -f /var/cache/fontconfig/0bd3dc0958fa22058ebb13e2872b-le64.cache-7
]; then
echo "color emoji will be broken in Chromium again (LP: #1858636) unless
you"
echo "sudo rm
/var/cache/fontco
Curiously, fc-cat /var/cache/fontconfig
/0bd3dc0958fa22058ebb13e2872b-le64.cache-7.bork does not complain
about the cache file being invalid. It shows information about a bunch
of Noto fonts BUT! not the ColorEmoji one!
diff -u <(fc-cat /var/cache/fontconfig/*.bork|cut -d'"' -f2|sort) <(ls
/u
Maybe not.
ls -ld /snap/*/current/usr/share/fonts/truetype/noto shows that only one
snap has that directory (gnome-3-34-1804), and instead of containing all
the fonts but NotoColorEmoji.ttf it's the exact opposite: it contains
one font only, and that is NotoColorEmoji.ttf.
--
You received this b
FWIW 0bd3dc0958fa22058ebb13e2872b is MD5 of
"/usr/share/fonts/truetype/noto". fontconfig keeps one cache file per
font directory.
The timestamp of the broken fontconfig cache file is May 15, 10:37. I
wonder what my computer was doing at the time.
'last reboot' indicates that I rebooted on M
This time I successfully resurrected color emoji by manually removing
the file that fc-cache used to complain about. Or, rather, I moved it
aside, for study:
sudo mv /var/cache/fontconfig/0bd3dc0958fa22058ebb13e2872b-
le64.cache-7{,.bork}
Then I restarted Chromium and emoji are now colorful
FWIW rebooting also makes the problem reappear. snap info shows that I
last refreshed chromium 13 days ago, but I rebooted today to install a
kernel update, and color emoji disappeared.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Another experiment: while emoji are broken, I can do sudo fc-cache -s
-v, and it doesn't find any invalid cache files, and when I restart
chromium, I don't get color emoji.
But then I do sudo apt install --reinstall fonts-noto-color-emoji, and I
see a /var/log/fontconfig.log with an up-to-date tim
Yesterday I saw a notification about chromium being auto-refreshed,
restarted it, and today I noticed that color emoji are gone again.
I suspect the two facts are related.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
I tired to figure out what exactly happens when I reinstall fonts-noto-
color-emoji. According to dpkg's output, fontconfig's triggers run.
fontconfig's postinst runs
# Force regeneration of all fontconfig cache files.
mkdir -p /var/cache/fontconfig
fc-cache -s -v 1>/var/log/fontconfig.log
Unfortunately the workaround is temporary. I rebooted and the emoji are
gone again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1858636
Title:
[snap] color emoji not rendered; many bw emoji rende
The workaround worked for me too. I used the simplified version
sudo apt install --reinstall fonts-noto-color-emoji
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1858636
Title:
[snap] color em
This is interesting information!
I have the chromium and chromium-chromedriver packages installed via
apt. I wonder if that is why my example (headless) can work without
overriding executable_path? chromium-chromedriver ships a
/usr/bin/chromedriver that's a shell script that exec's
/snap/bin/ch
*** This bug is a duplicate of bug 1868520 ***
https://bugs.launchpad.net/bugs/1868520
Apparently the root cause is mesa bug 1868520.
** This bug has been marked a duplicate of bug 1868520
Clients fail to run with zwp_linux_dmabuf error (failed to import supplied
dmabufs: Unsupported buff
*** This bug is a duplicate of bug 1868520 ***
https://bugs.launchpad.net/bugs/1868520
The workaround mentioned in the mpv upstream issue works for me:
export MESA_LOADER_DRIVER_OVERRIDE=i965
mpv ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
1 - 100 of 1521 matches
Mail list logo
