apport information
** Attachment added: "acpidump.txt"
https://bugs.launchpad.net/bugs/1905179/+attachment/5438020/+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/1905179
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1905179/+attachment/5438019/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905179
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1905179/+attachment/5438018/+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/1905179
Title:
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1905179/+attachment/5438017/+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/1905179
Title:
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1905179/+attachment/5438016/+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/1905179
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1905179/+attachment/5438015/+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/1905179
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1905179/+attachment/5438014/+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/1905179/+attachment/5438013/+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/1905179
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1905179/+attachment/5438012/+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/1905179/+attachment/5438011/+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/1905179
apport information
** Attachment added: "Lsusb-v.txt"
https://bugs.launchpad.net/bugs/1905179/+attachment/5438010/+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/1905179
Title:
apport information
** Attachment added: "Lsusb-t.txt"
https://bugs.launchpad.net/bugs/1905179/+attachment/5438009/+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/1905179
Title:
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1905179/+attachment/5438008/+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/1905179
Title:
apport information
** Attachment added: "Lspci-vt.txt"
https://bugs.launchpad.net/bugs/1905179/+attachment/5438007/+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/1905179
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1905179/+attachment/5438006/+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/1905179
Title:
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1905179/+attachment/5438005/+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/1905179
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1905179/+attachment/5438004/+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/1905179/+attachment/5438003/+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/1905179
Title:
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly
apport information
** Tags added: staging
** Description changed:
When mount an SD card date is wrong shown on SD-card (it is shown as to be
one month ahead). Very strange.
There is already some report about here, but I don't find a bug here in
launchpad.
Backported
https://launchpad.net/~lizthegrey/+archive/ubuntu/misc/+build/20333280
-- and it does work with a 5.8 kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883721
Title:
*** This bug is a duplicate of bug 1883721 ***
https://bugs.launchpad.net/bugs/1883721
** This bug has been marked a duplicate of bug 1883721
v4l2loopback-dkms 0.12.3-1: v4l2loopback kernel module failed to build
--
You received this bug notification because you are a member of Ubuntu
The additional rule should probably be:
owner /{dev,run}/shm/wayland.mozilla.ipc.[0-9]* rw,
** Changed in: firefox (Ubuntu)
Assignee: (unassigned) => Olivier Tilloy (osomon)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have removed NetworkManager
configure netplan and use renderer: networkd
My wifi connection is go from 0,5 Gb to 5GB
and seams more stable.
next day I check better.
best regards,
Leonardo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
*** This bug is a duplicate of bug 1883721 ***
https://bugs.launchpad.net/bugs/1883721
** This bug is no longer a duplicate of bug 1880598
package v4l2loopback-dkms 0.12.3-1 failed to install/upgrade: installed
v4l2loopback-dkms package post-installation script subprocess returned error
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: flash-kernel (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/1904024
** Changed in: cinnamon-session (Ubuntu Focal)
Assignee: (unassigned) => Joshua Peisach (itzswirlz)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887312
Title:
[SRU] Cinnamon session doesn't
I can reproduce with firefox 83 on Ubuntu 20.04, and I can confirm that
the suggested addition to the apparmor profile fixes the problem.
** Changed in: firefox (Ubuntu)
Status: New => Confirmed
** Changed in: firefox (Ubuntu)
Importance: Undecided => Medium
--
You received this bug
** Summary changed:
- firefox crashes with MOZ_WAYLAND_ENABLE=1
+ firefox crashes with MOZ_ENABLE_WAYLAND=1
** Summary changed:
- firefox crashes with MOZ_ENABLE_WAYLAND=1
+ firefox crashes with MOZ_ENABLE_WAYLAND=1 when apparmor profile is enforced
--
You received this bug notification
** Package changed: ubuntu-release-upgrader (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/1904455
Title:
impossible de créer «
My apologies for sidetracking this far trying to explain differences
between discovery and browsing but there seems to be a lot of mixing the
2 as one. The fact that you have "discovered" a server you wish to
"browse" is irrelivant for this bug (afaik you shouldn't have been able
to discover it as
I should also note that attaching my Android phone isn't detected/showed
in Nautilus, but not sure if this has anything to do with systemd-udevd.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905167
as this is needed only for the debian experimental branch (with
v247-rc2), marking this as invalid for ubuntu.
** Description changed:
[impact]
when upgrading, all serial devices are changed to 'dead' and thus all
serial consoles are stopped
[test case]
on a system configured
Please try removing the kalzium package and trying the upgrade again. If
the upgrade completes then you should be able to reinstall the package.
Thanks and good luck!
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because
** Changed in: libfprint (Ubuntu)
Status: New => In Progress
** Changed in: libfprint (Ubuntu)
Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)
** Changed in: libfprint (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a
use_vaapi is enabled by default (on amd64 and i386) starting with chromium 88
(currently dev channel).
snaps in the edge channel already have this, as do the bionic builds in
ppa:chromium-team/dev. Chromium depends on a version of libva that's too recent
for xenial, so I have disabled it for
Public bug reported:
[Impact]
On Ubuntu 20.04, with Synaptics fingerprint reader, users can use one
fingerprint to login system, but if users add more fingerprints, they
still can only one of those to login, other fingerprints do not work.
To fix this issue, we need support fingerprint
Public bug reported:
Version 1.7.0-3 has a missing comma in a list declaration:
$ python3 -c "import pykwalify.rule; pykwalify.rule.Rule().keywords()"
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python3/dist-packages/pykwalify/rule.py", line 343, in keywords
Public bug reported:
None
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: ubiquity 20.10.13
ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
Uname: Linux 5.8.0-25-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu50
Public bug reported:
[ Impact ]
Fingerprint devices that we know are not supported, aren't properly put
in power-state mode
[ Test case ]
- Ensure you've a non-supported device from this list:
https://gitlab.freedesktop.org/libfprint/wiki/-/wikis/Unsupported%20Devices#usb-devices
-
** Changed in: glibc (Ubuntu Cosmic)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821677
Title:
dl_open segment fault in ubuntu18.10 glibc2.28
To manage
Based on my comment above, and no reply from Sebastian, I am marking
this as verification-failed.
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-failed verification-failed-focal
--
You received this bug notification because you are a member of Ubuntu
** Description changed:
== Begin SRU Template ==
[Impact]
This release sports both bug-fixes and new features and we would like to
make sure all of our supported customers have access to these
improvements. The notable ones are:
- Explicit set IPV6_AUTOCONF and IPV6_FORCE_ACCEPT_RA
** Description changed:
[Impact]
* Ubuntu 18.04 is missing various stability and performance fixes that
have been added to upstream's 2.27 branch. The accumulated changes are
known to fix various issues already reported to Launchpad.
[Test Case]
* Observe that
** Changed in: firefox (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1896722
Title:
Mozilla Firefox Multiple Arbitrary Code Execution
Comment #14 in
https://bugs.chromium.org/p/chromium/issues/detail?id=1128405 suggests
that this might be a hardware issue. Are you able to observe the problem
with other mouses?
** Changed in: chromium-browser (Ubuntu)
Status: New => Incomplete
--
You received this bug notification
** Summary changed:
- sru cloud-init (20.3-2 to 20.4-0) Xenial, Bionic, Focal, and Groovy
+ sru cloud-init (20.3-2 to 20.4-0ubuntu1) Xenial, Bionic, Focal, and Groovy
** Description changed:
== Begin SRU Template ==
[Impact]
This release sports both bug-fixes and new features and we would
** Summary changed:
- sru cloud-init (20.3-2 to 20.4-2) Xenial, Bionic, Focal, and Groovy
+ sru cloud-init (20.3-2 to 20.4-0) Xenial, Bionic, Focal, and Groovy
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: glibc (Ubuntu Bionic)
Status: New => Confirmed
** Tags added: regression-update rls-bb-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821677
Title:
dl_open segment
@Pedro Ribeiro
Same problem. Couldn't manage it to make it work
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1887190
Title:
MSFT Touchpad not working on Lenovo Legion-5 15ARH05
To manage
Can you share the output of running the following command in a terminal?
find ~/.mozilla/firefox -name *.xpi
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905122
Title:
firefox
Public bug reported:
== Begin SRU Template ==
[Impact]
This release sports both bug-fixes and new features and we would like to
make sure all of our supported customers have access to these
improvements. The notable ones are:
- Explicit set IPV6_AUTOCONF and IPV6_FORCE_ACCEPT_RA on static6
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: dpkg (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/1836298
Title:
Public bug reported:
[ Impact ]
[13359.449610] fprintd[355436]: segfault at 0 ip 7ffb9f375385 sp
7ffddc26ba90 error 4 in libfprint-2.so.2.0.0[7ffb9f36+3e000]
See upstream bug:
https://gitlab.freedesktop.org/libfprint/libfprint/-/issues/320
[ Test case ]
Build and run the tests
"does it work without the langpack extension manually installed? the system
package is supposed to be enough to provide the translations..."
I don't know, the language pack is installed automatically, but Firefox starts
in English.
--
You received this bug notification because you are a member
Thank you for your message. Your hint about the *esp* flag was all that
was needed. There is still an issue: the diagnostic "A partition ..." is
worse than useless and should be changed. As an ex-compiler writer, I
can only stress that *all* diagnostics *must* be accurate and not
misleading!
Removing packages from hirsute:
pyspeex 0.2-1ubuntu9 in hirsute
python-speex 0.2-1ubuntu9 in hirsute amd64
python-speex 0.2-1ubuntu9 in hirsute arm64
python-speex 0.2-1ubuntu9 in hirsute armhf
python-speex 0.2-1ubuntu9 in
So I'm wondering if some other fixes are needed as well do fix the
testcase.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905044
Title:
systemd 245.4-4ubuntu3.3 ADT test failure with
@ddstreet thanks for pointing to that other bug report.
After applying the fix from
https://github.com/systemd/systemd/pull/16424 to
systemd_245.4-4ubuntu3.3, 'systemd show' does work:
$ ./systemctl show -p CapabilityBoundingSet apparmor
CapabilityBoundingSet=cap_chown cap_dac_override
Public bug reported:
[impact]
when upgrading, all serial devices are changed to 'dead' and thus all
serial consoles are stopped
[test case]
on a system configured with a serial console, upgrade from focal to the
latest systemd package from upstream, and check the serial console. the
state of
Yes, @Jack Christensen (jchristensen), it’s the same for me too.
I found it interesting to read the explanation given at this link:
https://askubuntu.com/questions/1170347/what-does-no-nvram-do-while-installing-grub
I hope it’s useful to everyone.
--
You received this bug notification because
Public bug reported:
[Impact]
* We were advised by Synaptics to upgrade the existing libfprint in the
archive to include sensor support for 0xF9, 0xFC, 0xC2 as highlighted in
the following commits:
https://gitlab.freedesktop.org/libfprint/libfprint/-/commit/31319d9c6fe03f
[Test Case]
* We
I can reproduce this issue with 5.4.0 version of the client. Is this
fixed in later version?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1880019
Title:
ussuri 'openstack security group list' gets
Sponsored to focal-proposed. Had to change the changelog entry to
contain a proper LP bug link (the # was missing), but other than that it
was fine. Let's wait for the SRU team to pick it up from the queue and
review.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Description changed:
On my Lenovo X1 Extreme with GPU: NVIDIA Corporation GP107M [GeForce GTX
1050 Ti Mobile]
Updating to nvidia-driver-455 results in loss of brightness control. On
boot, the laptop display brightness is somewhat less than fully bright
and cannot be changed.
As per upstream decision...
** Changed in: libfprint (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819406
Title:
Found broken a feature for
Removing packages from hirsute:
mp3splt 2.6.2+20170630-3 in hirsute
libmp3splt 0.9.2-3 in hirsute amd64
libmp3splt 0.9.2-3 in hirsute arm64
libmp3splt 0.9.2-3 in hirsute armhf
libmp3splt 0.9.2-3 in hirsute ppc64el
Removing packages from hirsute:
florence 0.6.3-1.2 in hirsute
florence 0.6.3-1.2 in hirsute amd64
florence 0.6.3-1.2 in hirsute arm64
florence 0.6.3-1.2 in hirsute armhf
florence 0.6.3-1.2 in hirsute ppc64el
Public bug reported:
Today on 20.04 if one wants to reach the hidden grub2 menu , it's harder
than hercule's work
- Hit ESC at Boot
- Pray that you don't hit ESC one time too much or you will get the >
Bash Prompt and cannot do anything
Solution : We would need to change Grub2 so the user
** Changed in: nvidia-graphics-drivers-455 (Ubuntu)
Status: New => Triaged
** Changed in: nvidia-graphics-drivers-455 (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
On my Lenovo X1 Extreme with GPU: NVIDIA Corporation GP107M [GeForce GTX
1050 Ti Mobile]
Updating to nvidia-driver-455 results in loss of brightness control. On
boot, the laptop display brightness is somewhat less than fully bright
and cannot be changed. The brightness
** Description changed:
+ [ Impact ]
+
+ fprintd hangs after first finger scan (fprintd-enroll or g-c-c)
+
+ [ Test case ]
+
+ - Launch fprintd-enroll (or g-c-c) to start enrolling your finger
+ - Enrollment should continue and complete successfully
+
+ [ Regression potential ]
+
+ USB
If I were to speculate, someone tried to fix the "blocked by env" errors
in Firefox 82, in the process actually making that statement true with
some kind of fail code. In 84 they may have actually fixed whatever the
root problem reporting that message.
--
You received this bug notification
This is now invalid as libfprint changed a lot, open a new bug if
needed.
** Changed in: libfprint (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1653000
Title:
This is should not be an issue anymore as fprintd saves the prints in
/var/lib/fprintd
** Changed in: libfprint (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: fingerprint-gui
Status: Confirmed => Invalid
** Changed in: lightdm
Status: Confirmed => Invalid
--
*** This bug is a duplicate of bug 602071 ***
https://bugs.launchpad.net/bugs/602071
** This bug has been marked a duplicate of bug 602071
[0a5c:5801] Broadcom fingerprint reader not working
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Package changed: ubuntu => xorg (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1905576
Title:
I cannot drag icons above to a particular region of my desktop
To manage notifications
Drivers requests are upstream issues and as such should be redirected to
the official wiki:
- https://gitlab.freedesktop.org/libfprint/wiki/-/wikis/Unsupported-
Devices
As per this, I'm closing all the requests, I please you to update that
wiki page if needed.
** Changed in: libfprint (Ubuntu)
** Also affects: glibc (Ubuntu Bionic)
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/1821677
Title:
dl_open segment fault in ubuntu18.10 glibc2.28
To
That error doesn't seem related (looks more like something the bypass-
lan plugin would log). So please post the complete log.
Also, your manual config creates two CHILD_SAs, one for each family.
That's not how the NM plugin operates. It assumes the responder is able
to narrow the traffic
** 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/1905584
Title:
package grub-pc 2.04-1ubuntu35.1 failed to install/upgrade: installed
grub-pc package
Just please note that that wiki is not freely editable.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1397067
Title:
ID 138a:003f Validity Sensors, Inc. on HP EliteBook 840G1
To manage
Actually, it looks like there's been a queued fix for this in the bionic
SRU queue for several months now. See bug 1884788.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1858590
Title:
fwupaa64.efi
So, this is an issue that depends on device.
For MOH (match-on-host) devices there's no other option than doing this,
however the images are saved in a place where only root can access, so
are safe in a non-compromised system.
For MOC (match-on-chip) this is not the case so the issue is not
** Summary changed:
- Update simple-scan in Ubuntu 20.04 to 3.36.6 (fixes cannot scan a page using
EPSON V39 scanner)
+ Update simple-scan in Ubuntu 20.04 to 3.36.7 (fixes cannot scan a page using
EPSON V39 scanner)
** Description changed:
[ Description ]
GNOME upstream have released a
** Merge proposal linked:
https://code.launchpad.net/~chad.smith/ubuntu/+source/update-notifier/+git/update-notifier/+merge/394468
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1901627
Title:
** Attachment added: "libvirt debug log - native (new) mode being slow"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1904584/+attachment/5437960/+files/vol-download.native.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The upstream discussion helped to eliminate migration as well as networking
from the equation.
It seems the new virt-ssh-helper mode is just rather slow and thereby
stalling/hanging.
Here are logs of:
virsh -c qemu+ssh://127.0.0.1/system?proxy=netcat vol-download --pool uvtool
h-migr-test.qcow
** Attachment added: "libvirt debug log - netcat (classic) mode being fast"
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1904584/+attachment/5437959/+files/vol-download.netcat.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
While installing as an OEM PC
ProblemType: Package
DistroRelease: Ubuntu 20.10
Package: grub-pc 2.04-1ubuntu35.1
ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
Uname: Linux 5.8.0-25-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
** Changed in: libfprint (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/657031
Title:
[08ff:2810] AuthenTec, Inc. AES2810 fingerprint reader not
** Changed in: libfprint (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/736793
Title:
[08ff:1680] AuthenTec, Inc. Fingerprint Sensor doesn't work
To
** Changed in: libfprint (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/744310
Title:
[138a:0005] [138a:0008] Fingerprint Validity reader devices
** Changed in: libfprint (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1065493
Title:
The "08ff:168f AuthenTec, Inc. Fingerprint Sensor does not
** Changed in: libfprint (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/bugs/1101647
Title:
ID 138a:003d Validity Sensors, Inc.
To manage notifications about
Drivers requests are upstream issues and as such should be redirected to
the official wiki:
- https://gitlab.freedesktop.org/libfprint/wiki/-/wikis/Unsupported-
Devices
As per this, I'm closing all the requests, I please you to update that
wiki page if needed.
** Changed in: libfprint (Ubuntu)
This should be supported by latest libfprint.
** Changed in: libfprint (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1835522
Title:
04f3:0c03 Elan
Drivers requests are upstream issues and as such should be redirected to
the official wiki:
- https://gitlab.freedesktop.org/libfprint/wiki/-/wikis/Unsupported-
Devices
As per this, I'm closing all the requests, I please you to update that
wiki page if needed.
** Changed in: libfprint (Ubuntu)
On Wed, Nov 25, 2020 at 12:41 AM Ike Panhc <1858...@bugs.launchpad.net> wrote:
>
> The fix[1] is simple but since we already backport fwupd from eoan to
> bionic. Shall we backport 1.3.11 from focal to bionic?
While this package has been granted an SRU special case exception:
Repeatable on dual-boot. The expected behaviour for dual-boot is that
the grub menu will show.
Whatever process detects dual-boot during reconfiguration of grub is failing as
of 20.04.1
grub-mkconfig ??
This also occurs when using boot-repair, if boot-repair performs a reinstall of
grub, then
201 - 300 of 486 matches
Mail list logo