** Description changed:
[Summary]
For the test case 'Drag-n-drop' of testscreen,the Finger touch is failed.
[Steps to reproduce]
1. Install the 22.04
2. Boot and login
3. Open a folder
- 4. Drag-n-drop the folder with finger touch
- 5. Drag-n-drop the folder with the Wacom Pen
+ 4.
Public bug reported:
Release: Lunar
Version: 0.10.0-1
Failure due to the upstream gpgme-config script not being shipped by
debian with gpgme1.0 1.18.0-2
Related bugs:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1023601
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1022348
[gpgme-sys
build successful
https://launchpad.net/ubuntu/+source/pulseaudio/1:13.99.1-1ubuntu3.14/+build/23853226
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
all autopkgtests now pass https://people.canonical.com/~ubuntu-
archive/proposed-migration/focal/update_excuses.html#systemd
now testing if the new testcase is fixed with v5.15 kernels in focal.
Test request submitted.
Result history
https://autopkgtest.ubuntu.com/packages/systemd/focal/amd64
ar
imho focal users on riscv64 deserve new pulseaudio
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1973734
Title:
FTBFS on riscv64 in focal
Status in pulseaudio package
** Description changed:
[SRU]
[ Impact ]
- Sometimes dnsmasq is incorrectly converting NXDOMAIN responses from
- authoritative dns servers into NODATA. This prevents the name resolution
- for normally working records fails in third party plugins/applications,
- as autopath (coredns).
+ S
Turns of that rust-gpgme-sys 0.10.0-2 in proposed has a fix, but was
FTBFS when synced. On poking the builds again, they built. Tests now
pass when the trigger for 0.10.0-2 is added.
https://autopkgtest.ubuntu.com/packages/r/rust-gpgme-sys/lunar/amd64
** Changed in: gpgme1.0 (Ubuntu)
Statu
Public bug reported:
python-apt FTBFS with Python 3.11 as a supported version:
https://launchpad.net/ubuntu/+source/python-apt/2.3.0ubuntu3
I've copied what I hope is the relevant part of the log below.
I: pybuild base:240: env
PYTHONPATH=/<>/.pybuild/cpython3_3.11_dbg_apt/build python3.11-dbg
Public bug reported:
Installing gnupg will also install and depend on gpg-agent(-ssh) which
will replace ssh-agent.
This is bad due to the fact that gpg-agent-ssh takes an exclusive lock
on all smartcards incorrectly yet does not actually support neither PIV
or opensc-pkcs11 integration. Until gn
Also confirmed five years ago in this issue
https://github.com/OpenSC/OpenSC/issues/953
** Changed in: gnupg (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gnupg in Ubuntu.
https://bu
In the triggered logs
PASS: test-execute
is present with new kernel and new systemd
-env=ADT_TEST_TRIGGERS=linux-meta-hwe-5.15/5.15.0.53.59~20.04.21 linux-
hwe-5.15/5.15.0-53.59~20.04.1 linux-signed-hwe-5.15/5.15.0-53.59~20.04.1
systemd/245.4-4ubuntu3.19'
https://autopkgtest.ubuntu.com/results/
Hi, any update on this bug, we are facing this issue in OpenStack CI
jobs. For error, logs see here [1]. let me know if more info. is
required.
I have opened a new bug in openstack/horizon as well to track it and
added more details there [2].
[1]
https://zuul.opendev.org/t/openstack/build/e17d10
Public bug reported:
For some reason, when the test is executed using bash 5.2 on Debian
experimental/Kinetic/Lunar, the `eval` [0] in the `counter_delta_`
function misinterprets successful execution of commands [1], leading to
a false negative for the 'ovn-controller incremental processing' test
** Description changed:
[Impact]
Azure 18.04 has issue with /dev/disk/by-path/ has the same path name when vm
has multiple disks.
[Test Plan]
1. launch 18.04 on azure
2. add extra disk to #1 vm
3. check the path
xtrusia@test-canonical:~$ udevadm info --name=/dev/sda | grep ID_
** Changed in: kbd (Ubuntu)
Assignee: (unassigned) => dann frazier (dannf)
** Changed in: kbd (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to kbd in Ubuntu.
https://bugs.launc
** Description changed:
[Impact]
Azure 18.04 has issue with /dev/disk/by-path/ has the same path name when vm
has multiple disks.
[Test Plan]
1. launch 18.04 on azure
2. add extra disk to #1 vm
3. check the path
xtrusia@test-canonical:~$ udevadm info --name=/dev/sda | grep ID_
** Description changed:
[Impact]
- Azure 18.04 has issue with /dev/disk/by-path/ has the same path name when vm
has multiple disks.
+
+ * The PATH_ID for SCSI disks on Azure/Hyper-V might not be unique
+with the systemd/udev version in Ubuntu 18.04 LTS (Bionic Beaver).
+
+ * This cause
I have verified the scenario that Seyeong mentioned
where the patch apparently dit not make a difference
(SCSI disks with LUN numbers greater than 1, eg, 5).
My observation is it indeed works/makes a difference.
He went out on vacation (so I'm reassigning the bug), and
cannot confirm this, but pe
Hello Jeremy, or anyone else affected,
Accepted evolution-data-server into kinetic-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/evolution-data-
server/3.46.1-0ubuntu1 in a few hours, and then in the -proposed
repository.
Please help us by testing t
> The fixes are each limited to one line, hence there are not many
issues to expect
Except that one of these one-line changes is stated to enable a new
optimization path in the shared library which was accidentally not
enabled before. Since almost everything in Ubuntu uses the shared
library and
The command-not-found package is responsible for showing that
information. I'm not sure how the internals work though, so it's
possible there's something wonky with the systemd package that confuses
command-not-found.
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
** Also affect
Test packages on ppa:mfo/lp1996958 [1].
Initial tests show positive results (next comments).
Waiting on feedback from the original reporter.
[1] https://launchpad.net/~mfo/+archive/ubuntu/lp1996958
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, w
Scenario 1) LUN numbers 0 and 1 only.
$ dmesg | grep Hypervisor
[0.00] Hypervisor detected: Microsoft Hyper-V
$ uname -r
5.4.0-1094-azure
$ lsscsi | grep sd
[0:0:0:0]diskMsft Virtual Disk 1.0 /dev/sdc
[0:0:0:1]
Scenario 2) LUN numbers 0, 1, and 5 (non-0/1 test).
$ dmesg | grep Hypervisor
[0.00] Hypervisor detected: Microsoft Hyper-V
$ uname -r
5.4.0-1094-azure
$ lsscsi | grep sd
[0:0:0:0]diskMsft Virtual Disk 1.0 /dev/sda
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1587142
Title:
Shutdown hangs in md kworker after "Reached target Shutdown."
Status in systemd package in Ubuntu:
Confirme
** Changed in: openldap (Ubuntu)
Status: New => In Progress
** Merge proposal linked:
https://code.launchpad.net/~sergiodj/ubuntu/+source/openldap/+git/openldap/+merge/433313
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subsc
sascha, are you able to provide information about a reproducer
environment for this? I'd like to see this fixed but we need to have a
way to make sure the change actually fixes things.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscr
> The message queue rules support could cause issues for AppArmor
> policies that were developed before there was support for mqueues,
Please explain in more detail why this is a risk. reading the
'mqueue1-' patch, the documentation reads to me as the default being
full access allowed:
AppArmo
Uploaded.
heimdal | 7.7.0+dfsg-4ubuntu1 | lunar/universe
heimdal | 7.7.0+dfsg-6ubuntu1 | lunar-proposed/universe
** Changed in: heimdal (Ubuntu)
Status: In Progress => Fix Committed
** Merge proposal linked:
https://code.launchpad.net/~bryce/ubuntu/+source/heimdal/+git/hei
> Separately we really ought to port networkd from dbus communication to
varlink such that it can be used safely on critical boot path. The rest
of the Systemd critical components are already using varlink.
+1
> did you mean to mark Ubuntu(Systemd) as affected?
Yes, I'll update that thanks.
**
** Description changed:
For some reason, when the test is executed using bash 5.2 on Debian
- experimental/Kinetic/Lunar, the `eval` [0] in the `counter_delta_`
- function misinterprets successful execution of commands [1], leading to
- a false negative for the 'ovn-controller incremental proces
https://lists.gnu.org/archive/html/bug-bash/2022-11/msg00078.html
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bash in Ubuntu.
https://bugs.launchpad.net/bugs/1997093
Title:
bash 5.2 regression in optimize_connection_for
32 matches
Mail list logo
