On Fri, Nov 13, 2020 at 09:37:34AM -, Sebastien Bacher wrote:
>@Matthieu, @Dave, thanks for the comments and details.
>
>I'm not blocking work to land, the 20.10 SRU could be accepted now and I
>didn't revert in that serie.
>The SRU team tries to ensure the fix is in the new serie so it
Thank you for reporting this bug to Ubuntu.
Ubuntu 19.04 (disco) reached end-of-life on January 23, 2020.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
Solved by removing -Werror flag
** Also affects: 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/1904259
Title:
include/qemu/atomic.h:495:5: error:
Public bug reported:
Running apt-get update; apt-get upgrade for the first time in a few
months, I get an error
```
Writing GRUB to boot device failed - continue
GRUB failed to install to the following devices:
[*] /dev/nvme1n1p1 (104 MB; /boot/efi) 1000204 MB WDC WDS100T2B0C-00PXH0
```
** Summary changed:
- Sorry, I dont speak English
+ Installer crashed and sent this report (Программа установки аварийно
завершила свою работу и отправила отчет)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Likely the same as
https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1872212.
Note that:
1) drive uses gpt, not mbr
2) EFI partition is not logical partition AFAICS
3) there are no dump files as described in $ root parted /dev/nvme1n1
GNU Parted 3.3
Using /dev/nvme1n1
Welcome to GNU
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: midori (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/1898175
Title:
I can confirm that this still occurs on 20.10. Is there a workaround to
remove the icon from the dash after ejecting?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1856032
Title:
Removable media
Thanks for the suggestion, but my /etc/apt/apt.conf.d/ looks like:
cassiopeia:~# ls /etc/apt/apt.conf.d/
00aptitude01-vendor-ubuntu 50apt-file.conf60icons-hidpi
00trustcdrom 20auto-upgrades 50command-not-found60icons-large
01autoremove 20packagekit
Hi Sebastien:
Thanks for the reply. Attached is the output.
It happens on any location.
** Attachment added: "outputnautilusbug"
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1904101/+attachment/5434160/+files/outputnautilusbug
--
You received this bug notification because you
Using dbus-monitor, and the test site given ( https://web-push-
book.gauntface.com/demos/notification-examples/ )
output:
string "Chromium"
uint32 0
string "file:///tmp/.org.chromium.Chromium.kuprxj"
string "Web Push Book"
string "web-push-book.gauntface.com
The file does not seem
There is no intend here to block any fix for stable serie but in case
that was not clear enough or if the SRU team didn't feel comfortable
with hirsute lacking behind and I uploaded back the patches but I'm
tagging the bug as 'block-proposed' instead which should be enough
incensitive to sort out
Unsubscribing sponsors for now, Alex are you still working on that?
Please subscribe the team back if you get something ready for upload
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887910
Title:
Public bug reported:
unable to lauch ubuntu
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15.2
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion:
This is not a bug in apt. dpkg cleans up its database and removes hold
states for non-installed packages following an operation.
** Changed in: apt (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Whether it's a bug in apt or in something used by apt doesn't really
make a difference from an end user perspective. Can this bug be reopened
as a dpkg bug, then, or should I report that as a new bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Please see attachment.
** Attachment added: "journal.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/remmina/+bug/1903986/+attachment/5434168/+files/journal.tar.gz
** Changed in: remmina (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a
Is anything going on with this? It's been quite a while. I recently
retested and the r8169 still will not wake for 80+ seconds upon wake.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1752772
Title:
Public bug reported:
When a package is not installed and apt dist-upgrade offers to install
it, if this is not desired, it is possible to hold the package using
multiple tools, which puts it in a state documented in dpkg.1 as:
hold
A package marked to be on hold is kept on the
Today happened again.
I executed "journalctl -b X" where X is the number I was searching today's date.
Executing "journalctl -b 167" I have got:
Data from the specified boot (+167) is not available: No such boot ID in journal
Then I executed:
"journalctl -b 166" > journalctl_166.txt
"journalctl
> That upload apparently wouldn't have worked anyway
yeah, i'm not very happy that bug 1864571 was pushed through against my
(and mapreri's) objections. This (and probably more) breakage is the
result, and I don't particularly want to be the one to clean up the
mess.
--
You received this bug
Sorry, I do not have any idea.
Now that there is a description of what happened,
perhaps someone who is an expert on the installation
can study the problem. That may not happen quickly.
>From my own experience, if the system is basically
working despite the installer being upset, then the
** Patch added: "debdiff between sysdig 0.26.4-1 and 0.26.4-1ubuntu0.2"
https://bugs.launchpad.net/ubuntu/+source/sysdig/+bug/1901734/+attachment/5434188/+files/sysdig_0.26.4-1ubuntu0.2-1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Patch added: "debdiff between sysdig 0.26.4-1ubuntu0.1 and 0.26.4-1ubuntu0.2"
https://bugs.launchpad.net/ubuntu/+source/sysdig/+bug/1901734/+attachment/5434189/+files/sysdig_0.26.4-1ubuntu0.2-2.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
[Impact]
Some platforms may keep USB power in S3/S4/S5, so Realtek 8821C retains
its firmware even with a cold boot.
[Fix]
Use vendor command to drop firmware if the version is old.
[Test case]
Use dmesg to check if new firmware is loaded.
With the patch applied, we can
Note also, I expect this does not affect MAAS, so removing that line
item, feel free to correct if someone disagrees.
** Changed in: maas
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This doesn't seem to be related to the previous bugs.
I tried to reproduce this on 18.04.4 (I don't have 20.04) and a fresh
build of GDB master, and I couldn't.
(gdb) disass _start
Dump of assembler code for function _start:
0x00010074 <+0>: mov r7, #4
0x00010078 <+4>: mov
Doing some experiments this seems to be working with netplan.io 0.100 in
Groovy. No matter if 'match.macaddress' is set or not on my local eth
interface.
As far as I can tell the fix was released with netplan 0.99 in Focal
final and was SRU'ed to Bionic as well.
** Also affects: maas-images
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/1900668
Title:
MAAS PXE Boot stalls with grub 2.02
To manage notifications
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: glibc (Ubuntu Cosmic)
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/1821677
any information when the package will be released to -updates
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902832
Title:
duplicity's lftp support broken - exits with error_code -11 on Bionic
To
@tmolloy, thank you for circling back around. I'm glad the patches worked for
you :-)
Note that there are other (unrelated) packages in @waveform's PPA that may get
installed with an apt upgrade. I don't know what the state of those packages
are. I disabled the PPA after installing bluez, just
I am experiencing this same issue on LIBC 2.27-3ubuntu1.3 and it
appears to be the same dll. I did not see it with GLIBC 2.27-3ubuntu1.2
$ lsb_release -a
Distributor ID: Ubuntu
Description:Ubuntu 18.04.5 LTS
Release:18.04
Codename: bionic
$ ldd --version
ldd (Ubuntu GLIBC
I now managed to get a working PXE setup for Groovy that runs the
Subiquity installer with an autoinstall configuration.
I documented my findings in detail at https://askubuntu.com/q/1292032.
My solution can be used both for UEFI and BIOS systems and also mentions
how to install a desktop
Can you please attach output of `prime-select query`?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1903200
Title:
Ubuntu is unable to detect one of my GPUs
To manage notifications about this bug
I just setup a Thinkpad P14s with Ubuntu 20.04 and have the exact same
problem as with the T440p. Here is the journalctl output
** Attachment added: "P14s_journalctl.txt"
Apologies, I forget: You may want to change the title from
Sorry, I dont speak English
to something about the problem. As an example:
Программа установки завершила работу и отправила отчет (Installer
crashed and sent this report)
To change the title click on yellow circle next to the
** Bug watch added: bugzilla.netfilter.org/ #1481
http://bugzilla.netfilter.org/show_bug.cgi?id=1481
** Also affects: iptables via
http://bugzilla.netfilter.org/show_bug.cgi?id=1481
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a
Reported upstream here:
https://bugzilla.netfilter.org/show_bug.cgi?id=1481
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1904192
Title:
ebtables can not rename just created chain
To manage
Dropping the crit subscription as a working fix has been found.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902944
Title:
Cannot create a swift container, mandatory "Storage Policy" dropdown
** Tags added: kernel-fixed-upstream
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1903397
Title:
Groovy 5.8 kernel hangs on boot on CPUs with eLLC
To manage notifications about this bug go to:
I just wanted to chime in and say I have the same problem, also with a
T490, although the processor is i7-8565U CPU @ 1.80GHz and I am running
Kubuntu 20.10. Currently running kernel 5.8.0-28.
If there's any way I can help, let me know.
--
You received this bug notification because you are a
Public bug reported:
After installing current 20.04 release on ThinkBook 13s IML with Intel
audio card built-in microphone is not working - I'm unable to record
anything.
I could confirm that it was working in Windows 10 (previously installed
on that laptop), and when I'm using headphones their
Scratch that, it's broken again. :(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902768
Title:
Upgrade to 20/10 broke sound
To manage notifications about this bug go to:
Update on the initial report: currently with 5.4.0-53 sound card is
initialized without any workarounds. But only output dynamics works,
reported microphone issue here:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1904213
--
You received this bug notification because you are a
Just to make it clear: I did uninstall snapd, and any snapd packages I
know of. Since I'm using Kubuntu, I only know of chromium-browser.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1902352
Title:
As this workaround requires doctoring ubuntu images and turning off
ubuntu image updates, setting to critical.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1900668
Title:
MAAS PXE Boot stalls with
I recharged the mouse, but:
$ solaar show
Unifying Receiver
Device path : /dev/hidraw0
USB id : 046d:c52b
Serial : 23FF9429
Firmware : 12.10.B0032
Bootloader : 02.15
Other : AA.AA
Has 3 paired device(s) out of a maximum of 6.
Notifications: wireless
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: iptables (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/1904192
Title:
You're right btw that it's a dpkg bug, but it's a bit more subtle. The
cleanup that dpkg performs after installation is meant to preserve the
hold state for non-installed packages. This is handled by the
pkg_is_informative function, which classifies everything with "pkg->want
!= PKG_WANT_UNKNOWN"
Public bug reported:
Ubuntu 20.04 (with all updates on 13.11.2020)
● direvent.service - monitors events in the file system directories
Loaded: loaded (/lib/systemd/system/direvent.service; enabled; vendor
preset: enabled)
Active: failed (Result: core-dump) since Fri 2020-11-13 15:57:19
UlfZibis:
Interesting to note that your issue also relates to EFI partition, which
somewhere several months back I posted that that seemed to be a
"commonality" to many of the posters in this bug report . . . .
On Fri, Nov 13, 2020 at 4:41 AM UlfZibis <1863...@bugs.launchpad.net>
wrote:
> I had
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: wammu (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/1853107
Title:
I confirm the problem and confirm that it's a dependencies problem.
The python-six is not install with wammu.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1853107
Title:
Crash in starting
To
201 - 254 of 254 matches
Mail list logo
