** 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
*** 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
(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"
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
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
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.
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.
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.
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.
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.
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.
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.
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.
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.
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
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.
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
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.
** Package changed: ubuntu => gdm3 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969285
Title:
Wayland session unavailable after upgrade from 21.10
To manage notifications about this bug
Public bug reported:
After upgrading from 21.10 to beta 22.04 the Wayland session is no
longer available. By default, I do not even get the option to select the
session type but if I lock the screen, the login screen changes from the
X11 UI to the Gnome UI and the bottom right button appears.
I downloaded and installed 1.187.26 via browser. I can also confirm that
it fixes the problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958283
Title:
linux-firmware missing renoir_ta
To
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
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
@Aaron, I am not able to find the first bad version because apt tells me
that the specified version for firmware-linux was not found. See the
attached log.
** Attachment added: "find-first-bad-version.txt"
As mentioned in https://bugs.launchpad.net/ubuntu/focal/+source/linux-
firmware/+bug/1958283:
I am able to fix the problem temporarily with a downgrade: sudo apt
install linux-firmware=1.187
After a reboot, I no longer have any graphics errors.
--
You received this bug notification because you
I am able to fix the problem temporarily with a downgrade: sudo apt
install linux-firmware=1.187
After a reboot, I no longer have any graphics errors.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1958343/+attachment/412/+files/acpidump.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958343
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1958343/+attachment/411/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958343
Title:
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1958343/+attachment/410/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958343
Title:
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1958343/+attachment/409/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958343
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1958343/+attachment/408/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958343
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1958343/+attachment/407/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1958343/+attachment/406/+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/1958343
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1958343/+attachment/405/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1958343/+attachment/404/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958343
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1958343/+attachment/403/+files/Lsusb-v.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958343
Title:
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1958343/+attachment/402/+files/Lsusb-t.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958343
Title:
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1958343/+attachment/401/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958343
Title:
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1958343/+attachment/400/+files/Lspci-vt.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958343
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1958343/+attachment/399/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958343
Title:
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1958343/+attachment/398/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958343
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1958343/+attachment/397/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1958343/+attachment/396/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958343
Title:
:
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC1: marius 1618 F pulseaudio
+ /dev/snd/controlC0: marius 1618 F pulseaudio
+ CasperMD5CheckResult: skip
+ CurrentDesktop: Pantheon
+ Dependencies:
+
+ DistroRelease: elementary OS 6.1
+ MachineType: TUXEDO TUXEDO Pulse 14 Gen1
I can also confirm this issue.
I added a "screenshot" in
https://bugs.launchpad.net/ubuntu/+bug/1958343.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958283
Title:
linux-firmware missing
** Package changed: ubuntu => linux-firmware (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958343
Title:
Internal monitor of AMD based laptop not working after update
To manage
I extracted the last updated packages with cat /var/log/dpkg.log | grep
"\ upgrade\ "
** Attachment added: "dpkg.log"
https://bugs.launchpad.net/ubuntu/+bug/1958343/+attachment/394/+files/dpkg.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
After applying the latest updates for focal yesterday and rebooting, the
internal display of my laptop is no longer usable. Only a noisy, snowy
image can be seen on the display. An externally connected display still
works.
I can reproduce this behavior on 2 laptops:
TUXEDO
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
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
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
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...
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,
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.
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
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
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.
/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:
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
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
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
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
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
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
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
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
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
fyi, fixed patch for clucene to keep the ABI constant on s390x is
attached to https://sourceforge.net/p/clucene/bugs/233/.
The patch requires that clucene uses a separate type clucene_float_t in
its API, with multiple yet trivial changes all across the code base.
None of the packages that depend
Indeed, my patch is just broken. I have not received any upstream
feedback about the patch or the proposed alternatives -- unfortunately,
clucene's community appears rather inactive, with 0 emails on the
developer list in the last three months.
--
You received this bug notification because you
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:
> 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
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
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
│
Public bug reported:
No problematic behaviour except for push-up notification showing this
bug.
ProblemType: Package
DistroRelease: Ubuntu 20.10
Package: linux-modules-5.8.0-36-generic (not installed)
ProcVersionSignature: Ubuntu 5.8.0-33.36-generic 5.8.17
Uname: Linux 5.8.0-33-generic x86_64
I tried the patch from #15 but it still hangs for me, albeit after 3min and
not after a few seconds like without the patch.
I tried version 5.31b and it works fine.
Core i5-4570, 16 GiB RAM.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I tried the patch from #15 but it still hangs for me.
I have 16 GiB RAM installed.
Anything else I can try?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1876157
Title:
Memtest86+ in Ubuntu 20.04
version 0.6.4 has been released, including the fix -- https://docs.wand-
py.org/en/0.6.4/changes.html#version-0-6-4
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904899
Title:
pixel color access
Public bug reported:
When using an Imagemagick compiled with HDRI=1 (e.g.,
,libmagickwand-6.q16hdri-6) many color-related test cases in wand fail.
The root cause is that python-wand assumes that ImageMagick's
QuantumType would be float for 16-bit HDRI. However, in that config
QuantumType is
Was solved with
sudo apt --fix-broken install
sudo apt upgrade
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904724
Title:
package linux-modules-extra-5.8.0-29-generic (not installed) failed to
Public bug reported:
New kernel installation 5.8.0-29 was corrupted.
Problem with sudo apt upgrade:
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies.
linux-image-generic : Depends: linux-modules-extra-5.8.0-29-generic but it is
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
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
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
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
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
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
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
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
** Patch added: "update package description to reflect dynamic arch support on
s390x"
https://bugs.launchpad.net/ubuntu/+source/openblas/+bug/1893653/+attachment/5424642/+files/fix-description-dynamic-s390x.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs,
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:
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.
1 - 100 of 4871 matches
Mail list logo
