I have created Bug 1907814 to complain about apport refusing to report
bugs about unknown updates with an unhelpful message.
I believe these remain two separate concerns:
a) Retracting security upgrades on purpose after releasing them to non-proposed
channels needs a better workflow, reverting in
Public bug reported:
Useful for monitoring HDD health via SMART
https://www.phoronix.com/scan.php?page=news_item&px=Plasma-5.20-SMART-
More
Also preinstalled by neon
https://invent.kde.org/neon/neon/seeds/-/blob/9375a4e2572f87d57ed15a44d26908d0b0c6ef41/desktop#L89
** Affects: kubuntu-meta (Ubunt
please reboot with this kernel boot parameter added:
systemd.log_level=debug
Then let the system boot up, and then perform a shutdown, to reproduce
the problem. Then start the system back up (you can remove the kernel
boot parameter) and capture the previous boot's journal, which should
include t
** Changed in: ubuntu-z-systems
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1892367
Title:
[UBUNTU 20.04] udev rule change did not get applied
To manage notificat
This affects multiple GA and HWE (including -edge) stacks.
These are the notices announcing the now missing package versions as
intentional releases:
https://ubuntu.com/security/notices/USN-4658-1
https://ubuntu.com/security/notices/USN-4659-1
https://ubuntu.com/security/notices/USN-4660-1
https:
Public bug reported:
not sure what to report, not much information, during the do-release-
upgrade
--
Calculating the changes
Calculating the changes
Could not calculate the upgrade
An unresolvable problem occurred while calculating the upgrade.
If none of this applies, then pleas
can you boot with the kernel param 'systemd.log_level=debug' and
recreate the problem, and then provide the full journal logs, e.g.:
$ journalctl -b > /tmp/lp1891358.log
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a mem
** Also affects: linux-azure-4.15 (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/1904458
Title:
[linux-azure] Batch hibernate and resume IO reques
** Tags added: resolved-resolvconf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1874337
Title:
resolvconf should never touch /etc/resolv.conf in Ubuntu; all DNS
configuration from resolvconf, ifu
>"it looks like the user installed the driver through
>the nvidia installer, and then used our packages.
>The perfect recipe for disaster."
Thanks for continuing to look into this. I don't believe I have an
nvidia installer, only nvidia settings.
I can't test with a live disk, because the nvidia
Plasma disks is not in the Ubuntu or debian archive yet. When it is, it
will likely be installed by default.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1907815
Title:
preinstall `plasma-disks` by
There was also a recent linux-firmware update that I applied with no
luck. At this point is another ubuntu-bug report needed?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906095
Title:
Fails to bo
All looks good with the PPA build.
After patch/build partman-crypto, and updating its sources
in ubiquity (adding an apt source to the PPA, of course),
the ubiquitu .deb package includes the partman-crypto changes
in '/lib/partman/lib/crypto-base.sh' as expected.
--
You received this bug notific
Next Steps:
1) Upload partman-crypto to focal.
2) Wait for it to be available in focal-proposed.
3) Upload ubiquity to focal (gets focal-proposed.)
We could upload both and coordinate the time that
they are accepted and published (ubiquity must be
after partman-crypto), but plans might go wrong :
** Merge proposal linked:
https://code.launchpad.net/~lucaskanashiro/ubuntu/+source/containerd/+git/containerd/+merge/395229
** Merge proposal linked:
https://code.launchpad.net/~lucaskanashiro/ubuntu/+source/containerd/+git/containerd/+merge/395230
** Merge proposal linked:
https://c
it sounds like this bug is a dup of bug 1872159? I'm assuming so, and
marking this invalid for systemd.
** Changed in: systemd (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
Something like `sudo apt install nvidia-drivers-455` should do.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900584
Title:
Regression: suspend/wake-up no longer working properly
To manage notific
A few things that may help with this, these were noted under bug 1897185. In
looking at logs when this occurred (observed on ThinkPads including T440s,
T570, T480 all docked and running lid-down with external display, keyboard,
etc); this behavior occurred when:
-using a third-party nVidia drive
Just to follow up, a quick read of the upstream bug seems to indicate
there are kernel patch(es) involved in fixing this as well as systemd
patch(es). The upstream bug isn't yet marked fixed, so hopefully we can
check back in the new year to start backporting.
--
You received this bug notificatio
please boot with kernel boot parameter 'systemd.log_level=debug' and
reproduce this, then provide the journal logs (before rebooting) with:
$ journalctl -k -b > /tmp/lp1830955.log
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you
Three additional points:
-This occurs with ONE external HDMI monitor connected to the dock and running
as the primary display. Need not be multi-monitor. All cases I've seen involve
one external monitor.
-I put log information in the notes for 1897185 to show the events that
preceded the suspend
xournalpp does not have the problem, btw.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1907805
Title:
Text annotation exported to pdf not readable on iPad
To manage notifications about this bug go
marking as invalid for systemd as i believe the bug was in maas, per
previous comments.
** Changed in: systemd (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
$ sudo apt update
...
$ sudo apt install nvidia-drivers-455
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Unable to locate package nvidia-drivers-455
$ sudo apt install nvidia-driver-455
Reading package lists... Done
Building dependency tree
This has been happening for ages now.
18.04 to 20.10 are all affected
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1846334
Title:
cupsd assert failure: free(): invalid pointer
To manage notificati
marking this as invalid for systemd as arbitrary code can be run using
networkd-dispatcher and/or suggestions from comment 4.
** Changed in: systemd (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
focal-updates only has nvidia-driver-450.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900584
Title:
Regression: suspend/wake-up no longer working properly
To manage notifications about this bug
Yes. I changed my NVMe slot. But the change
'nvme_core.default_ps_max_latency_us=5500' has proven stable on both
slots.
attached dmesg.
below the output of the lspci -tv command.
-[:00]-+-00.0 Advanced Micro Devices, Inc. [AMD] Starship/Matisse Root
Complex
+-01.0 Advanced Mic
Has there been any movement on this? We get asked about Secure Boot in
MAAS periodically by various hardware partners.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865515
Title:
Chainbooting from
I'm hesitant to backport, because the change causes significant issues on
upgrade, e.g.:
https://github.com/systemd/systemd/issues/17605
if we do backport the 'sticky' udev tags, we'll need to make sure to also pull
back the proper commits to handle the new udev format across daemon-reexec,
e.g
FYI:
- pgl-ddl-deploy resolved
- postgres-logical + logical-ticker resolved
=> All migrated to -release
The one thing that is left is powa-archivist which has the fix that we
discussed and tracked upstream and waits in the new queue.
=> https://ftp-master.debian.org/new/powa-archivist_4.1.0-1.htm
--- Comment From s...@de.ibm.com 2020-12-11 10:43 EDT---
It has nothing to do with a performance improvement. It's just broken. Thus
your Ubuntu 20.10 has a regression compared to Ubuntu 20.04! The issues were
reported via glibc-upstream bugzillas:
- "Bug 26636 - 32-bit shmctl(IPC_INFO) c
** Description changed:
More generally, desktop mis-displays
3 Variations:
a)
0) open a window/app
1) minimise a window/application, causing Desktop to be visible
2) move cursor to dock (to open new app)
As soon as cursor hits dock, the graphic of the minimised window
(gra
Public bug reported:
Automatic bug report generated
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: yaru-theme-icon 20.04.8
ProcVersionSignature: Ubuntu 5.4.0-52.57-generic 5.4.65
Uname: Linux 5.4.0-52-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.13
Architecture: amd64
CasperMD5Check
Public bug reported:
It is not possible to receive mail using the POP3 protocol if the server
supports the UTF8 Unicode capability. It is required to remove the flag to the
"Enable UTF-8 Extension, when the server supports it" option in server
configuration.
The problem seems to be that Evoluti
r11-5879 - bad 8 of 10
So we know:
a) the bug has not been fixed yet
b) as we've seen with later GCC-10 runs, the chances to trigger further
increased
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/18
This is incomplete, APT deduplicates descriptions based on the
description hash, so if the description is the same, barring a bug in
apt, it should be available for both versions. Without seeing an apt-
cache showpkg of the affected package, we can't really tell. It seems to
work for me, but I also
This bug was fixed in the package fprintd - 1.90.7-1
---
fprintd (1.90.7-1) unstable; urgency=medium
* New upstream release
- Fix fprintd DBus configuration (Closes: #976990)
- Change details of what requires authorization
- Fix various race conditions in pam_fprintd
There is no movement and there will be no movement for some more months
at least.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865515
Title:
Chainbooting from grub over the network to local shim b
Does this issue only happen after suspend?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906949
Title:
ext4_find_entry:1531
To manage notifications about this bug go to:
https://bugs.launchpad.net
Adding this bug as that seems to be the exact issue here -
https://github.com/openzfs/zfs/issues/10140
Solution is "Use zfs-mount-generator instead of zfs-mount.service" ...
** Bug watch added: github.com/openzfs/zfs/issues #10140
https://github.com/openzfs/zfs/issues/10140
--
You received t
This is not a problem we can fix on our side. It is an upstream shim
problem. Every distribution you want to boot will need a fixed shim, and
it's not a priority right now, given that we have a moratorium on new
shims being signed.
We have the ability to secure boot Ubuntu already, by not chainloa
@Julian: Today, after the latest apt update, it behaves differently
compared to what I wrote in comment #8 and #10. Now I'm not able to even
work around the issue to make apt-cache use the Swedish description.
Anyway, I attached a file with some commands to demonstrate the issue.
** Attachment ad
I tried to replicate the problem several times with different systems
(Thankfully, I have three laptops with three different OS installed.),
and concluded that the symptom doesn't need to be provoked with macOS. I
can reproduce the error with these steps with the files from any OS.
1) Write a cert
Thank you for your email. I went back to reinstall 20.04.LTS without any
problem.
On Fri 11 Dec, 2020, 3:20 PM Plurtu, <1901...@bugs.launchpad.net> wrote:
> Even the most straight-forward option "Erase disk and install Ubuntu"
> failed for me on non-UEFI system when installing from USB. I noticed
I cannot reproduce that issue from #11
# apt install locales-all # get the locale
# export LANG=sv_SE.UTF-8
# locale
LANG=sv_SE.UTF-8
LANGUAGE=
LC_CTYPE="sv_SE.UTF-8"
LC_NUMERIC="sv_SE.UTF-8"
LC_TIME="sv_SE.UTF-8"
LC_COLLATE="sv_SE.UTF-8"
LC_MONETARY="sv_SE.UTF-8"
LC_MESSAGES="sv_SE.UTF-8"
LC_PAPE
no. it happened:
when i was installing a steam game,
when i was transfering files between external hdd and onboard nvme,
when i was checking my code in vscode,
when i was opening a new tab in firefox..
in the first 2 days after building my pc it happened anywhere from 30
min into using the cpu
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1907832
Title:
package yaru-theme-icon 20.04.8 failed to install/upgrade: unable to
open '/usr/share/icons/Yaru/
This bug was fixed in the package fprintd - 1.90.7-1
---
fprintd (1.90.7-1) unstable; urgency=medium
* New upstream release
- Fix fprintd DBus configuration (Closes: #976990)
- Change details of what requires authorization
- Fix various race conditions in pam_fprintd
OK I believe what has happened here is that you are running mixed-locale
systems, and the cache was generated with en_US or C locales. If you run
mixed language systems, you have to set
Acquire::Languages { "language code 1"; "language code 2"; ... };
e.g.
Acquire::Languages { "sv_SE"; "sv"; en"
** Description changed:
This is a special case of Bug 559345 somewhere between a question and a
request for better/more discoverable error message/documentation.
In apport, because thats what people encountering bugs are going to use.
In USN, because the one thing worse than no security
per comment in bug description, marking as affecting only focal
** Also affects: systemd (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
@sampie you have a reference to the upstream issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902891
Title:
"Too many levels of symbolic links” error when using systemd to mount
sshfs
To man
Public bug reported:
[Impact]
* focal users will gain the addition and refinement of more mimetype-
icons, scalable-icons, devices-icons that were previously not present
* will make it consistent with the icons present in gtk-common-themes
snap
* Backporting them to focal would greatly increa
** Also affects: ceph (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: ceph (Ubuntu Hirsute)
Importance: High
Assignee: Ponnuvel Palaniyappan (pponnuvel)
Status: Fix Released
** Also affects: ceph (Ubuntu Focal)
Importance: Undecided
Status: Ne
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verificati
2020-12-09, tr, 08:26 Daniel van Vugt <1872...@bugs.launchpad.net> rašė:
> It seems almost always, maybe always, to be Ubuntu 20.04 suffering from
> this bug. There's only one report from 20.10 and that might not even be
> the same bug. So it's possible the issue was fixed in 20.10...
>
> I've bee
I'm new to this. Si, this bug is invalid? What does this mean? I'm
affected. At the raspberry pi forum others too, so was my report a waste
of time? It took 1 day for me to try reporting this as correct as
possible.
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
So, what kind of support do I need? I just installed ubuntu as
described, on an SSD. I think this was my first and my lasr bug report.
I think that this procedure us a mess. Bye!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
@kaihengfeng, can we skip Xenial since that goes ESM soon?
** Description changed:
[Impact]
Micmute hotkey on many HP EliteBooks don't work.
[Fix]
Commit b6eb208b29ae ("hwdb: Add EliteBook to use micmute hotkey"), to map AT
keyboard's scancode to micmute hotkey.
[Test]
With the
OK I have now officially had enough of this ToyTown Distro.
You make a severe CRITICAL mistake and then try to triage it away by
insisting we use a tool that simply does not work.
This bug is not even assigned to anyone yet.
That tells me everything I need to know about whether to persist with
t
For the record we had an IRC conversation here:
https://irclogs.ubuntu.com/2020/12/11/%23launchpad.html
I think it makes more sense to open a new apt bug. Not quite sure at the
moment what the issue is, though...
As said on IRC, I'll do some tests later. If you already know what a
proper bug sum
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verificati
Public bug reported:
I can't connect to Wi-Fi after update of this particular package to
version 2020.11.20-0ubuntu1~20.10.1 yesterday (10 XII 2020). If I
finally connect, Internet is not reliable and soon I can't load any
webpage even if I'm connected. When I downgraded this package, Wi-Fi
works.
Ok, just wanted to be sure - this will justify a glibc SRU.
(clicking the bug number earlier opened it as LP bug, which is
wrong and is usually an indicator for me that it's an internal IBM BZ number -
but I've found the glibc upstream BZs now
thx ...)
I've created a first SRU justification ba
@kaihengfeng can you review this bug to see if you can tell what the
correct change to the hwdb should be?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1890186
Title:
Failed to call EVIOCSKEYCODE w
OK, I got to thinking about this other bug I had seen a while back. Initially
thought it was not related, but maybe it is after all?
https://bugs.launchpad.net/qemu/+bug/1694808
Perhaps we are using different USB controllers, and that's why we see different
results? I have the following ... matc
try disabling the 'ondemand' service and install cpufrequtils package.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1889668
Title:
set-cpufreq error when cpu is offline
To manage notifications abo
*** This bug is a duplicate of bug 1905245 ***
https://bugs.launchpad.net/bugs/1905245
you didn't say specifically what's causing ansible to fail, but the fix
you referenced suggests this is a dup of 1905245, so i'll mark it as
such.
** This bug has been marked a duplicate of bug 1905245
"
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: fonts-liberation (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1804431
Ti
Public bug reported:
[Impact]
In bug 1161743 we discovered that if a system is configured with multiple
locales, only the locales of the user who generated the apt-cache will be
available for translated descriptions.
[Test case]
# apt install locales-all # get the locale
# export LANG=sv_SE.UT
** Changed in: skiboot (Ubuntu Hirsute)
Status: New => Confirmed
** Changed in: skiboot (Ubuntu Hirsute)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/19
For reference, the PR that Zygmunt had which was planned to fix this was
https://github.com/snapcore/snapd/pull/8219, but there were issues with
that approach. We need to pick it up again and rework to get an approach
which matches the comments from Jamie there.
--
You received this bug notificat
** Description changed:
I can't connect to Wi-Fi after update of this particular package to
version 2020.11.20-0ubuntu1~20.10.1 yesterday (10 XII 2020). If I
finally connect, Internet is not reliable and soon I can't load any
- webpage even if I'm connected.
+ webpage even if I'm connected.
had same issue with vscode
added Ernst ppa and updated (cheers for that mate)
all good
fix should be added asap imo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1897765
Title:
gnome-shell crashed w
** Changed in: skiboot (Ubuntu Hirsute)
Status: New => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905393
Title:
Ubuntu 20.04: opal-prd fails to start on 20.04
To manage notif
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verificati
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verificati
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verificati
Public bug reported:
An unresolvable problem occurred while calculating the upgrade.
This was likely caused by:
* Unofficial software packages not provided by Ubuntu
Please use the tool 'ppa-purge' from the ppa-purge
package to remove software from a Launchpad PPA and
try the upgrade again.
Quick note on a workaround: I've found on my pi400 that reverting to
kernel 1007 works around the issue. If you've still got 1007 installed
(a quick "ls /boot" should confirm that if you see lots of *-1007-raspi
files lying around) you can temporarily switch to it like so:
$ sudo flash-kernel --fo
Just tried it, the problem remains even with these two modules unloaded.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1906691
Title:
Laptop wakes up immediatly from suspend to RAM
To manage notifi
That's interesting, I just performed your suggested test, and I couldn't
reproduce - it's a fresh Ubuntu 20.04 install, running MATE (not KDE!)
and GNU screen 4.8.0-1. After closing the terminal, I've opened another
one and "screen -x" worked fine, as expected.
Could you try to use MATE / Gnome to
Is this what you are seeing?
[ 77.591737] systemd-shutdown[1]: All filesystems, swaps, loop devices and DM
devices detached.
[ 77.631493] systemd-shutdown[1]: Syncing filesystems and block devices.
[ 77.638423] systemd-shutdown[1]: Powering off.
[ 77.656068] kvm: exiting hardware virtuali
The crux of the problem is an API mismatch between the kernel module and
the nvidia driver. The problem arises in the normal course of applying
updates and not from user tinkering (see #1).
$ uname -a
Linux OptiPlex-380 5.4.0-47-generic #51-Ubuntu SMP Fri Sep 4 19:50:52 UTC 2020
x86_64 x86_64 x86
Public bug reported:
After update zfsutils-linux, the update process tries to mount zfs file
in /mnt but since in /mnt there are another disk mount fails with:
Setting up zfsutils-linux (0.8.3-1ubuntu12.5) ...
zfs-import-scan.service is a disabled or a static unit, not starting it.
zfs-import-sca
I've come to install nzbget 3 or 4 times in the past 5 years. Each time,
I forget about this workaround and almost give up ...
> nzbget not eligible for universe anymore (it has to be moved to
multiverse)
I'd sooner see it in multiverse and working properly.
Alternatively, I think we might be go
I tested the change on Azure using Standard L8s_v2 (8 vcpus, 64 GiB
memory) VMs using the 5.4 linux-azure kernel on bionic and the 5.8
kernel on groovy.
During my tests the VMs continued to successfully hibernate with the
patch and the time needed to save the VM state went down from 25 seconds
to
Hi, first of all I don' t know why I did' t receive any notification of
this bug report.
Second, and to clarify, I being using screen command since 2000 (which
Is my beginning as Linux admin). This being said, I know how it works.
All my other Ubuntu upgrades from 18.04 to 20.04, this does not ha
Targeting only 5.4 and 5.8 since 4.15 will not support hibernation.
** No longer affects: linux-azure-4.15 (Ubuntu)
** Also affects: linux-azure (Ubuntu Groovy)
Importance: Undecided
Status: New
** Also affects: linux-azure (Ubuntu Focal)
Importance: Undecided
Status: New
**
Sorry, muscle memory kicked in. This problem is confirmed and on my list
of things to look at.
** Changed in: linux-raspi (Ubuntu)
Status: Invalid => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
Julian filed bug #1907850 to continue the investigation of the apt-
cache/locale issue discussed above as from comment #7.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1161743
Title:
Typos in russi
** Summary changed:
- Can't connect to Wi-Fi after update
+ Can't connect to Wi-Fi after update [Atheros AR9565]
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1907848
Title:
Can't connect to Wi-Fi
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1907854
Title:
package zfsutils-linux 0.8.3-1ubuntu12.5 failed to install/upgrade:
installed zfsutils-linux pack
@waveform: I'll get an error-message:
sudo flash-kernel --force 5.8.0-1007-raspi
Using DTB: bcm2711-rpi-4-b.dtb
Couldn't find DTB bcm2711-rpi-4-b.dtb on the following paths:
/etc/flash-kernel/dtbs /usr/lib/linux-image-5.8.0-1007-raspi
/lib/firmware/5.8.0-1007-raspi/device-tree/
Installing into
@Juergh, no. In your dump the wording "Kernel Panic" never appears.
A pity... I cannot log this. If I could, I'd able to do include a copy
of it.
@waveform, I'll try it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.la
Well, is a really close (or same) behaviur like exposed in
https://bugs.debian.org/825394 (shared by Axel).
Screen version 4.8.0-1. The system (or either systemd) has modifications
at all, so is really weird.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
So, I took 1007 from the repository and repeated the force-command
suggested by @waveform. Thx for the workaround, yes, this Kernel does
not lead to a Panic. Thx.
@Juerg, the output is starting with the "shutting down" line, and after
about 10 minutes, the non blinking cursor is replaced by a few
To my knowledge, networkd-dispatcher has no way to do 'pre' hooks on
systemd-networkd events, so this is still a valid feature request.
** Changed in: systemd (Ubuntu)
Status: Invalid => Triaged
** Changed in: systemd (Ubuntu)
Milestone: ubuntu-17.05 => None
** Changed in: systemd (Ub
SRU submission: https://lists.ubuntu.com/archives/kernel-
team/2020-December/115552.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904458
Title:
[linux-azure] Batch hibernate and resume IO requ
101 - 200 of 258 matches
Mail list logo
