** Changed in: kernel-sru-workflow/prepare-package
Status: New => Confirmed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-eoan
** Tags added: block-proposed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For
Happened again.
Bug did not seem to submit report once more.
Screenshot as per comment #2
Report was produced which I managed to see the details but sending report did
not return a bug ID.
See this from terminal where I carried out action 1a in comment #3.
Still no bug ID.
dave@dave-ThinkPad-T4
** Changed in: kernel-sru-workflow/prepare-package
Status: New => Confirmed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https
Public bug reported:
After upgrading my Surface Go to Focal from Eoan, the touchscreen has
stopped working.
A snippet from journalctl:
12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (II) systemd-logind: got fd for
/dev/input/event4 13:68 fd 28 paused 0
12:43:15 /usr/lib/gdm3/gdm-x-session[1586]: (
I think bug 1864992 and this one are duplicates.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864436
Title:
depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
not open builtin f
*** This bug is a duplicate of bug 1865493 ***
https://bugs.launchpad.net/bugs/1865493
** This bug has been marked a duplicate of bug 1865493
eoan/linux-oracle: 5.3.0-1011.12 -proposed tracker
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
kernel-sta
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-eoan
** Tags added: block-proposed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For
*** This bug is a duplicate of bug 1865491 ***
https://bugs.launchpad.net/bugs/1865491
** This bug has been marked a duplicate of bug 1865491
eoan/linux-gcp: 5.3.0-1014.15 -proposed tracker
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Public bug reported:
from journalctl, gdm-fingerprint shows error there after retried 5 times
of fingerprint login failed, so I open this issue here.
Steps to reproduce issue:
1. enroll fingerprint for your right index finger.
2. logout
3. login and try login by incorrect finger e.g. middle finge
Yeah ok it is inverted logic, ok then modify it to that ...
"For each character in string , if the character is not in valid_chars ,
replaces the character with substitutor."
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
Nothing but i misexplained, bug isn't related to the fact that account exists
or not.
Please try to enter in a tty that exact login :
'username.lastnamelastnamelastn...@domain.fr'
It reset without asking for password, and the error line is added to
auth.log
Then try :
'username.lastn...@domain
## Test ##
1. I have a qemu with the experimental patch applied
# dpkg -l qemu-system-x86
1:4.2-3ubuntu2~ppa3
2. prep disk xml to load curl.so
# cat > curldisk.xml << EOF
EOF
3. check not being loaded
# lsof -p $(pidof qemu-system-x86_64) | grep bloc
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1865837
** Tags added: iso-testing
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is
I believe this is a bug in snapd. I have a local fix I need to spend
some more time on.
** Changed in: snapd
Status: Confirmed => In Progress
** Changed in: snapd
Assignee: (unassigned) => Zygmunt Krynicki (zyga)
--
You received this bug notification because you are a member of Ubun
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
kernel-sta
** Description changed:
First boot after new install; Lubuntu 20.04 QA-test install
NOTE: I re-used partitions, /dev/sda8 (/) was empty, but /dev/sda9 (/home)
contained data
sddm wasn't used as DM before Lubuntu 20.04 installs, so I doubt it's related
to a conf/config issue relating to
I have re-compiled gcc-9 from Focal after adding it to the list of
releases which do not enable cf-protection by default. Then compiled Xen
from Focal with that compiler. And it does boot!
# xen info
host : argabuthon
release: 5.4.0-14-generic
version
@ChavTha Chau (chavtha),
thank you for information. I confirm: BIOS update CJCN26WW solves the issue.
Actual vendor change to ACPI table is:
- Name (_HID, "") // _HID: Hardware ID
+ Name (_HID, "ELAN0632") // _HID: Hardware ID
--
You received this bug notification because you are a memb
Public bug reported:
First boot after new install; Lubuntu 20.04 QA-test install
NOTE: I re-used partitions, /dev/sda8 (/) was empty, but /dev/sda9
(/home) contained data. sddm wasn't used as DM before Lubuntu 20.04
installs, so I doubt it's related to a conf/config issue relating to
sddm.
Des
All Ubuntu systems are affected.
That's not related to a personal configuration, booting live latest ubuntu let
me reproduce this.
Its more clear on tty, as you see username field resets, but it's the
same from ligthdm
So should i open a bug for agetty package instead ?
--
You received this bu
** Summary changed:
- bionic/linux-azure-5.3: -proposed tracker
+ bionic/linux-azure-5.3: 5.3.0-1015.16~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonica
** Description changed:
First boot after new install; Lubuntu 20.04 QA-test install
- NOTE: I re-used partitions, /dev/sda8 (/) was empty, but /dev/sda9 (/home)
contained data
- sddm wasn't used as DM before Lubuntu 20.04 installs, so I doubt it's related
to a conf/config issue relating to
Advice how to disable cf-protaction when enabled by default was taken
from: https://wiki.ubuntu.com/ToolChain/CompilerFlags#A-fcf-protection
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863260
Title
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testi
While modifying gcc I had the feeling that maybe -fno-cf-protection
might be a valid flag, too. Should that be the same as -fcf-
protection=none?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863260
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-focal
** Tags added: block-proposed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
Fo
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Committed
** Changed in: kernel-sru-workflow/prepare-package
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-lrm
Status: In Progress => Fix Committed
** Cha
FYI: to test with just one version things like the following will trigger the
prerm logic (not sure if that is still true with remove/upgrade being split as
it will be on the next build)
$ apt install --reinstall qemu-system-gui
--
You received this bug notification because you are a member of
I think that it happens to me, and it's regression going from eoan to
focal. Firmware updates are downloaded and installed, and even if I set
BootNext by hand, it is bypassed.
Linux-Firmware-Updater looks suspicious to me:
# efibootmgr -v|grep Linux-Firmware-Updater
Boot0002* Linux-Firmware-Updat
Updates:
- (hopefully) fixed the replacement logic
- adapted d/rules to the new logic
- added all the special handling of remove/purge mentioned above
- fixup of some minor issues and adding comments
-> New build qemu_4.2-3ubuntu2~ppa4 in PPA (just started to build)
-> force pushed both branches t
the message in journalctl shows that fprintd and gdm-fingerprint know
user is trying on incorrect finger.
https://paste.ubuntu.com/p/QkySMYzVmC/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865838
** Tags added: radeon
** Summary changed:
- Dual monitor loop login
+ [radeon] Dual monitor loop login
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865444
Title:
[radeon] Dual monitor loop login
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:
1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell
Yes
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864223
Title:
shim 15+1552672080.a4a1fbe-0ubuntu1 fails to load fwupd
To manage notifications about this bug go to:
https://bugs.launchpad.net/ub
As I said earlier I totally agree with the comment above :
Manual whitelisting from the snap team will always be a blocker for such
a widely adopted use of an important browser.
That will push people to use chrome which IMO a failure on the libre
software side.
--
You received this bug notifica
Confirmed, was able to reproduce this, using the kernel as stated in the
bug. This also appears to break the networking after the failure.
transaction with reduced feature level UDP.
Mar 3 02:55:01 s2lp4 CRON[4294]: (root) CMD (command -v debian-sa1 > /dev/null
&& debian-sa1 1 1)
Mar 3 02:55:20
** Changed in: coccinelle (Ubuntu)
Assignee: Emmanuel Arias (eamanu) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864684
Title:
RM coccinelle, again
To manage notifications a
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a member
Thanks. The only relevant error I can find in there is strange:
Mar 02 11:49:30 mel-Aspire-M5600-AM3600 gnome-shell[3916]: gnome-shell:
Fatal IO error 0 (Success) on X server :0.
and
Feb 29 20:58:53 mel-Aspire-M5600-AM3600 gnome-shell[3068]: gnome-shell:
Fatal IO error 11 (Resource temporarily u
** Changed in: kernel-sru-workflow/security-signoff
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/security-signoff
Assignee: Canonical Security Team (canonical-security) => Steve Beattie
(sbeattie)
--
You received this bug notification because you are a member
On P8 node witchita, with Eoan 5.3 kernel + git branch from upstream:
$ time sudo ./futex_bench
test: futex_bench
tags: git_version:v5.6-rc4-0-g98d54f81e
time = 46.302199
success: futex_bench
real0m46.313s
user0m9.172s
sys 0m37.138s
$ time sudo ./tm-unavailable
test: tm_unavailable_
Public bug reported:
there is no progress information shows to user while enrolling fingerprint.
It might confuse user thinking it as freeze failure.
steps:
1. enroll fingerprint in gnome-control-center
2. click 'Next' on the enrolling page
3. There is no message tell user that it need at least 1
user page in setting failed forever after fingerprint enrolling time
out.
** Attachment added: "Screenshot from 2020-03-03 16-49-54.png"
https://bugs.launchpad.net/oem-priority/+bug/1865845/+attachment/5332968/+files/Screenshot%20from%202020-03-03%2016-49-54.png
--
You received this bug noti
after user click 'Next', there is no message remind user the progress of
fingerprint enrollment.
And also no reminder for the necessary of 12 times finger pressing.
** Attachment added: "Screenshot from 2020-03-03 11-13-25.png"
https://bugs.launchpad.net/oem-priority/+bug/1865845/+attachment
** Package changed: gdm3 (Ubuntu) => gnome-shell (Ubuntu)
** Also affects: yaru-theme (Ubuntu)
Importance: Undecided
Status: New
** Changed in: yaru-theme (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is s
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.
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testi
To clarify my comment #1: update files are installed in
/boot/efi/EFI/ubuntu/fw, but on reboot, there is no sign of fwupdx64.efi
ever running, boot process goes straight to grub.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gdm3 (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/1865563
Title:
passw
In addition to the patches necessary, the following also applies:
--
** This already exists in Focal
- nvme cli rev 1.9 or later must be installed in their system as well, so that
auto-connect scripts for systemd are installed.
see https://github.com/lin
** Summary changed:
- xenial/linux-aws-hwe: -proposed tracker
+ xenial/linux-aws-hwe: 4.15.0-1063.67~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical K
I upgraded from 18.04 to focal and had the same problem. Purging
timidity got audio back for me as well.
** Tags added: champagne focal
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1793640
Title:
** Tags added: champagne
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864052
Title:
gnome-shell crashed with SIGABRT in
src/core/window.c:1591:meta_window_unmanage: assertion failed:
(g_list_f
Hello,
same problem for me
Kernel 5.3.0.40 Ubuntu 19.10 WiFi not working
Kernel 5.3.0.28 and before, no problem at all.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863769
Title:
Ubuntu 18.04: Wif
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/promote-to-proposed
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz
Zemczak (sil2100)
--
You received this bug notification because you are
Maybe this could be useful...
steph@steph-X55A:~$ sudo lspci -k -nn | grep -A 3 -i net
[sudo] Mot de passe de steph :
02:00.0 Network controller [0280]: Ralink corp. RT5390 Wireless 802.11n 1T/1R
PCIe [1814:5390]
Subsystem: Foxconn International, Inc. RT5390 Wireless 802.11n 1T/1R
PCIe
** Summary changed:
- no fingerprint enrolling progress information
+ No UI indication for fingerprint enrolling progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865845
Title:
No UI indicati
Right, tracking this in https://github.com/rhboot/shim/issues/194
** Bug watch added: github.com/rhboot/shim/issues #194
https://github.com/rhboot/shim/issues/194
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testi
** Description changed:
- This is a massive number of updates by Broadcom to the lpfc driver that
- didn't make 5.4 in time. As 20.04 is an LTS release with expected
- hardware support for 5 years, we need to ensure as much hardware support
- lands as possible to support server vendors over the n
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/promote-to-proposed
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz
Zemczak (sil2100)
--
You received this bug notification because you are
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
kernel-sta
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865491
Title:
eoan/linux-gcp: 5.3.0-1014.15 -propose
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testi
Public bug reported:
lubuntu 19.10
pcmanfm-qt 0.14.1
when pcmanfm-qt is configured to use single-click mode...
1)when the pcmanfm window is given focus
Currently, when placing the focus on pcmanfm the item clicked would be
activated.
I suggest the first click anywhere on pcmanfm when given focu
** Tags added: rls-ff-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865845
Title:
No UI indication for fingerprint enrolling progress
To manage notifications about this bug go to:
https:/
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865493
Title:
eoan/linux-oracle: 5.3.0-1011.12 -prop
** Tags added: rls-ff-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865838
Title:
no error popup while exceed maximal fingerprint retry during login
To manage notifications about this bug
Public bug reported:
Lubuntu 19.10
After adding QuickLaunch widget onto a Panel using the panel dialog, the
configuration button is disabled. Hence, I'm not able to add other
applications to it.
** Affects: lubuntu-meta (Ubuntu)
Importance: Undecided
Status: New
--
You received t
Public bug reported:
using lubuntu 19.10
** Affects: lubuntu-meta (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/1865853
Title:
lxqt desktop
The quirk of auto selection also affects item selection (single or
multiple), renaming, copying and pasting.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865851
Title:
pcmanfm-qt item selection fe
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testi
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Assignee: Ike Panhc (ikepanhc)
Status: In Progress
** Also affects: linux (Ubuntu Eoan)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Eoan)
Status: New => In Progress
** Changed in: linux
** Tags added: ikeradar
** Changed in: kunpeng920/ubuntu-19.10
Status: New => In Progress
** Changed in: kunpeng920
Status: New => In Progress
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Assignee: Ike Panhc (ikepanhc)
Status: In Progress
** Also affe
Public bug reported:
In lxde, the desktop switcher widget shows an outline of windows
currently on each desktop. In lxqt, the desktop switcher widget only
show a label
** Affects: lubuntu-meta (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because
Hi.
This is fixed in the latest Yaru master :) Thanks for taking the time to report
this
** Changed in: yaru-theme (Ubuntu)
Status: Confirmed => Fix Committed
** Changed in: gnome-shell (Ubuntu)
Status: Confirmed => Fix Committed
--
You received this bug notification because you
** Description changed:
[Bug Description]
hns3 patchset have merged into mainline 5.6rc1 kernel.
[Steps to Reproduce]
1)
2)
3)
[Actual Results]
[Expected Results]
[Reproducibility]
[Additional information]
(Firmware version, kernel version, affected ha
Public bug reported:
lubuntu 19.10
I'm trying to create a vpn entry by importing a vpn configuration file.
There is no option in the Network Configuration application to allow me
to do so. The only option provided by this application dealing with vpn
is PPTP.
** Affects: lubuntu-meta (Ubuntu)
** Description changed:
[Bug Description]
hns3 patchset have merged into mainline 5.4rc7 kernel.
[Steps to Reproduce]
1)
2)
3)
[Actual Results]
[Expected Results]
[Reproducibility]
[Additional information]
(Firmware version, kernel version, affected hardw
** Description changed:
[Bug Description]
hns3 patchset have merged into mainline 5.4rc5 kernel. Pls backport ubuntu
18.04.5 kernel version
[Steps to Reproduce]
1)
2)
3)
[Actual Results]
[Expected Results]
[Reproducibility]
[Additional information]
(Firm
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testi
** Changed in: gnome-shell (Ubuntu)
Status: Fix Committed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865563
Title:
password box not centered
To manage notifications about this
This has now been removed from unstable in addition to testing.
https://tracker.debian.org/news/1106350/removed-425-7-from-unstable/
Please remove src and binaries from focal archive.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
h
Hello Dan, or anyone else affected,
Accepted network-manager into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/network-
manager/1.10.6-2ubuntu1.4 in a few hours, and then in the -proposed
repository.
Please help us by testing this new packag
Hello bugproxy, or anyone else affected,
Accepted network-manager into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/network-
manager/1.10.6-2ubuntu1.4 in a few hours, and then in the -proposed
repository.
Please help us by testing this new p
Hello Dan, or anyone else affected,
Accepted network-manager into bionic-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/network-
manager/1.10.6-2ubuntu1.4 in a few hours, and then in the -proposed
repository.
Please help us by testing this new packag
Just tested with Ubuntu 20.04, the problem does not occur in the live
session.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865499
Title:
pulseaudio doesn't detect (new) USB headset
To manage not
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
kernel-sta
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testi
This bug was fixed in the package cargo - 0.42.0-0ubuntu1
---
cargo (0.42.0-0ubuntu1) focal; urgency=medium
* New upstream version. (LP: #1864174)
* d/scripts/debian-cargo-vendor: use python3 not python.
* d/patches/2002_disable-net-tests.patch: delete, tests no longer run
a
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testi
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testi
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testi
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
boot-testi
Got feedback from one of my colleagues that running Ubuntu 18.04.4 with
Kernel 5.3.0-40, "pkill -U $USER pulseaudio" does not resolve the
problem, only a full restart of the system.
Is there anything I can do to provide additional logs? Running a
debugger when plugging in the headset, logfiles wit
Thanks. If you can then please also try Ubuntu 19.10
(https://ubuntu.com/download/desktop) so we can get a slightly better
idea of which PulseAudio version introduced the fix.
** Changed in: pulseaudio (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification becau
Public bug reported:
I have two actual audio devices plugged in: 1. speaker under my monitor
plugged into the 3.5mm headphone jack, 2. a set of USB headphones.
The 'Sound' settings panel shows three devices:
1. Headphones - built in audio
2. Digital output (s/pdif) - Jambra UC Voice 750 MS
3. Hea
** Tags removed: hwcert-server
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1089389
Title:
juju bootstrap fail behind a proxy when a gpg key must be imported
To manage notifications about this bug
1 - 100 of 774 matches
Mail list logo
