[Bug 1968131] Re: Starting VM with UEFI firmware fails with swtpm

2022-04-07 Thread Martin Pitt
I tested the PPA, and it works like a charm now. Thanks Christian and Simon! For once, kicking some{thing,one} out of their $HOME does something good..  ** Changed in: swtpm (Ubuntu Jammy) Status: Confirmed => In Progress -- You received this bug notification because you are a member

[Bug 1968131] Re: Starting VM with UEFI firmware fails with swtpm

2022-04-07 Thread Martin Pitt
Our CI uses a Jammy Ubuntu cloud image, but with quite a large list of extra installed packages. To make sure it's not something specific to that environment, I tried this: autopkgtest-buildvm-ubuntu-cloud qemu-system-x86_64 -enable-kvm -nographic -m 2048 -device virtio-rng-pci -drive

[Bug 1968131] Re: Starting VM with UEFI firmware fails with swtpm

2022-04-07 Thread Martin Pitt
Right, I understand -- but introducing the dependency was an explicit decision (#1948748), and it seems it is broken for its main use case. So in the simplest case the recommends: could be reverted, and reintroduced once this is understood? -- You received this bug notification because you are a

[Bug 1968131] [NEW] Starting VM with UEFI firmware fails with swtpm

2022-04-07 Thread Martin Pitt
Public bug reported: https://launchpad.net/ubuntu/+source/libvirt/8.0.0-1ubuntu6 introduced a recommendation to "swtpm", so this package now gets installed by default when installing libvirt. But this broke UEFI: touch /var/lib/libvirt/empty.iso virt-install --name t1 --os-variant fedora28

[Bug 1948748] Re: [MIR] swtpm

2022-04-07 Thread Martin Pitt
This broke VMs with UEFI, reported as bug 1968131. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1948748 Title: [MIR] swtpm To manage notifications about this bug go to:

[Bug 1966416] Re: pam_faillock does not actually deny login after given number of failures

2022-03-31 Thread Martin Pitt
Ouch, thanks Marc! Indeed our previous seddery was broken, it should have left the pam_deny/pam_permit lines. With this it works just fine: --- /tmp/common-auth.orig 2022-04-01 07:16:26.072608984 +0200 +++ /tmp/common-auth.faillock 2022-04-01 07:14:20.246707861 +0200 @@ -16,6 +16,8 @@ #

[Bug 1802005] Re: socket is inaccessible for libvirt-dbus

2022-03-31 Thread Martin Pitt
Timeout -- I uploaded the patch of the salsa PR to Jammy now. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802005 Title: socket is inaccessible for libvirt-dbus To manage notifications about

[Bug 1966416] [NEW] pam_faillock does not actually deny login after given number of failures

2022-03-25 Thread Martin Pitt
Public bug reported: ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: libpam-modules 1.4.0-11ubuntu1 I just noticed that Ubuntu 22.04 changed from the old pam_tally2 module to the more widespread pam_faillock one. \o/ However, locking (denying logins) does not actually seem to work.

[Bug 1946244] Re: When installing/uninstalling with realmd, uninstalling crashes with ScriptError

2022-03-25 Thread Martin Pitt
Confirmed in jammy as well. https://logs.cockpit- project.org/logs/pull-17182-20220325-080131-1b8abf94-ubuntu-2204/log.html#303-2 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1946244 Title: When

[Bug 1802005] Re: socket is inaccessible for libvirt-dbus

2022-03-25 Thread Martin Pitt
I sent a fix to Debian: https://salsa.debian.org/libvirt-team/libvirt- dbus/-/merge_requests/14 I'll give it a few days, if I can get that landed soon, we can just sync. Otherwise I'll upload it to Jammy directly. ** Changed in: libvirt-dbus (Ubuntu Jammy) Status: Triaged => Fix Committed

[Bug 1802005] Re: socket is inaccessible for libvirt-dbus

2022-03-25 Thread Martin Pitt
The image build log shows why: Setting up libvirt-dbus (1.4.1-1) ... /var/lib/dpkg/info/libvirt-dbus.postinst: 54: dpkg-vendor: not found dpkg-vendor is in the "dpkg-dev" package, so it should not be used in postinst scripts. libvirt-dbus could depend on dpkg-dev, but that's highly undesirable.

[Bug 1802005] Re: socket is inaccessible for libvirt-dbus

2022-03-25 Thread Martin Pitt
hanged in: libvirt-dbus (Ubuntu) Assignee: (unassigned) => Martin Pitt (pitti) ** Also affects: libvirt (Ubuntu Jammy) Importance: Medium Status: Won't Fix ** Also affects: libvirt-dbus (Ubuntu Jammy) Importance: High Assignee: Martin Pitt (pitti) Status: Triaged -- You

[Bug 1946244] Re: When installing/uninstalling with realmd, uninstalling crashes with ScriptError

2022-03-24 Thread Martin Pitt
Still confirmed on 21.10, and also Debian testing; I filed a Debian bug and linked it. ** Bug watch added: Debian Bug tracker #1008209 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008209 ** Also affects: freeipa (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1008209

[Bug 1966181] Re: ipa-client-install fails on restarting non-existing chrony.service

2022-03-24 Thread Martin Pitt
A-ha! I wasn't seeing things after all. Our test images install the "systemd-timesyncd" package (as we also run tests against that), and that removes the chrony package and installs the mask: # apt install systemd-timesyncd Reading package lists... Done Building dependency tree... Done Reading

[Bug 1966181] Re: ipa-client-install fails on restarting non-existing chrony.service

2022-03-24 Thread Martin Pitt
Hello Timo, I'm not actually sure where these /etc/systemd/system/chrony* files come from (in particular the mask). They are not owned by any package, nor does chrony's postinst seem to create it (but maybe through a helper, they are not exactly simple -- some weird interaction with the SysV

[Bug 1890786] Re: ipa-client-install fails on restarting non-existing chronyd.service

2022-03-24 Thread Martin Pitt
This is *still* broken on Ubuntu 21.10 and Debian testing. However, it is subtly different, I filed bug 1966181 about it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890786 Title:

[Bug 1966181] [NEW] ipa-client-install fails on restarting non-existing chrony.service

2022-03-24 Thread Martin Pitt
Public bug reported: DistroRelease: Ubuntu 21.10 Package: freeipa-client 4.8.6-1ubuntu6 This is a bug that just doesn't want to die -- the package *really* should grow an autopkgtest that checks if a basic ipa-client-install actually works. It's very similar to bug 1890786 except that it now

[Bug 1890786] Re: ipa-client-install fails on restarting non-existing chronyd.service

2022-03-24 Thread Martin Pitt
** Also affects: freeipa (Ubuntu Focal) 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/1890786 Title: ipa-client-install fails on restarting non-existing

[Bug 1913231] Re: ipa-client-install fails on restarting non-existing chronyd.service

2022-03-24 Thread Martin Pitt
*** This bug is a duplicate of bug 1890786 *** https://bugs.launchpad.net/bugs/1890786 Let's handle this in bug 1890786 instead, I added a focal task and will close this as a duplicate. ** This bug has been marked a duplicate of bug 1890786 ipa-client-install fails on restarting

[Bug 1962035] Re: apparmor blocks VM installation when automatic UEFI firmware is set

2022-03-09 Thread Martin Pitt
I did a test build in my PPA: https://launchpad.net/~pitti/+archive/ubuntu/fixes I re-ran the reproducer on current Jammy to confirm the bug, then updated to the PPA, and re-ran the last virt-install command. That succeeded. ** Changed in: libvirt (Ubuntu) Status: Triaged => Fix Committed

[Bug 1962035] Re: apparmor blocks VM installation when automatic UEFI firmware is set

2022-03-09 Thread Martin Pitt
I sent https://salsa.debian.org/libvirt- team/libvirt/-/merge_requests/135 to update Debian. Unfortunately that does not build right now due to the inconsistent state of the packaging git. But the patch itself backports fairly cleanly. I'll upload to Jammy next. -- You received this bug

[Bug 1962035] Re: apparmor blocks VM installation when automatic UEFI firmware is set

2022-03-09 Thread Martin Pitt
Fix landed upstream: https://gitlab.com/libvirt/libvirt/-/commit/7aec69b7fb9d0cfe8b7203473764c205b28d2905 ** Changed in: libvirt Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1962035] Re: apparmor blocks VM installation when automatic UEFI firmware is set

2022-03-07 Thread Martin Pitt
Thanks Christian. I updated the upstream PR. I just don't want to apply a patch just to Ubuntu. Once it lands upstream, I backport it, send it to Debian, and *then* I'm happy to apply it to Jammy -- there should still be enough time before the freeze, right? (Would be nice to have that in the LTS,

[Bug 1962035] Re: apparmor blocks VM installation when automatic UEFI firmware is set

2022-02-25 Thread Martin Pitt
** Changed in: libvirt Status: New => In Progress ** Changed in: libvirt Assignee: (unassigned) => Martin Pitt (pitti) ** Package changed: apparmor (Debian) => libvirt (Debian) -- You received this bug notification because you are a member of Ubuntu Bugs, which is s

[Bug 1962035] Re: apparmor blocks VM installation when automatic UEFI firmware is set

2022-02-25 Thread Martin Pitt
I sent the proposed and tested fix upstream: https://gitlab.com/libvirt/libvirt/-/merge_requests/140 ** Also affects: libvirt Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1962035] Re: apparmor blocks VM installation when automatic UEFI firmware is set

2022-02-25 Thread Martin Pitt
I came up with this patch: --- /etc/apparmor.d/abstractions/libvirt-qemu.orig 2022-01-22 18:22:57.0 + +++ /etc/apparmor.d/abstractions/libvirt-qemu 2022-02-25 13:54:22.075405809 + @@ -85,7 +85,7 @@ /usr/share/misc/sgabios.bin r, /usr/share/openbios/** r,

[Bug 1962035] Re: apparmor blocks VM installation when automatic UEFI firmware is set

2022-02-25 Thread Martin Pitt
it -1 --noautoconsole --cdrom /var/lib/libvirt/novell.iso --autostart ** Package changed: apparmor (Ubuntu) => libvirt (Ubuntu) ** Changed in: libvirt (Ubuntu) Status: New => Triaged ** Changed in: libvirt (Ubuntu) Assignee: (unassigned) => Martin Pitt (pitti) -- You received this bu

[Bug 1962035] Re: apparmor blocks VM installation when automatic UEFI firmware is set

2022-02-23 Thread Martin Pitt
** Bug watch added: Debian Bug tracker #1006324 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006324 ** Also affects: apparmor (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1006324 Importance: Unknown Status: Unknown -- You received this bug notification

[Bug 1958392] Re: pam_sss_gss crashes with Communication error [3, 32]: Error in service module; Broken pipe

2022-01-24 Thread Martin Pitt
Paride, many thanks for digging out the upstream fix! The patch does apply cleanly. It just need a round of "quilt refresh" to get over dpkg-source: error: diff 'sssd-2.4.1/debian/patches/5572.patch' patches files multiple times; split the diff in multiple files or merge the hunks into a

[Bug 1958392] Re: pam_sss_gss crashes with Communication error [3, 32]: Error in service module; Broken pipe

2022-01-21 Thread Martin Pitt
> I'll do a no-change rebuild of impish's sssd now and try with that. Done, but the bug is still the same. So not some weird build-time issue. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958392

[Bug 1958392] Re: pam_sss_gss crashes with Communication error [3, 32]: Error in service module; Broken pipe

2022-01-21 Thread Martin Pitt
Thanks Paride! I confirm that updating to your PPA fixes the issue, which confirms that it's sssd. I'll do a no-change rebuild of impish's sssd now and try with that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1958392] Re: pam_sss_gss crashes with Communication error [3, 32]: Error in service module; Broken pipe

2022-01-19 Thread Martin Pitt
I upgraded my test VM to current Jammy, with sssd 2.6.1-1ubuntu3. This works fine, so this only applies to impish. *phew* I.e. I figure/expect pretty well nothing will happen on this bug, and that's fine -- I just need it as downstream reference for our OS bug tracker. :-) ** Also affects: sssd

[Bug 1958392] Re: pam_sss_gss crashes with Communication error [3, 32]: Error in service module; Broken pipe

2022-01-19 Thread Martin Pitt
** Tags added: impish -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1958392 Title: pam_sss_gss crashes with Communication error [3, 32]: Error in service module; Broken pipe To manage

[Bug 1958392] Re: pam_sss_gss crashes with Communication error [3, 32]: Error in service module; Broken pipe

2022-01-19 Thread Martin Pitt
This is confirmed to work on Debian 11 (current stable), Debian testing, Fedora 34/35, CentOS 8, RHEL 8/9, so it does not smell like an upstream issue. Ubuntu 20.04 LTS does not yet have pam_sss_gss, so this does not apply there. ** Description changed: I am trying to set up pam_sss_gss to

[Bug 1958392] [NEW] pam_sss_gss crashes with Communication error [3, 32]: Error in service module; Broken pipe

2022-01-19 Thread Martin Pitt
Public bug reported: I am trying to set up pam_sss_gss to authenticate to sudo with Kerberos. I am fairly sure that this worked in the past, but stopped recently. Reproducer:  - Join a FreeIPA domain, with "ipa-client-install". I use "COCKPIT.LAN" here in our tests.  - Enable GSS for sudo in

[Bug 1799095] Re: Firewalld nftables backend breaks networking of libvirt

2021-11-30 Thread Martin Pitt
This is fixed in current Ubuntu 21.04. I dropped our hacks in our projects: https://github.com/cockpit- project/cockpit-machines/pull/465 and https://github.com/cockpit- project/bots/pull/2676 ** Changed in: firewalld (Ubuntu) Status: Confirmed => Fix Released -- You received this bug

[Bug 1853266] Re: Xorg/Xwayland segfaults in OsLookupColor() from funlockfile() from glamor_get_pixmap_texture() from glamor_create_gc()

2021-11-11 Thread Martin Pitt
> Xorg -config tests/xorg-dummy.conf -logfile /tmp/log -once :5 The -once was an attempt to work around this, but it doesn't help, nor change the behaviour of this bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1853266] Re: Xorg/Xwayland segfaults in OsLookupColor() from funlockfile() from glamor_get_pixmap_texture() from glamor_create_gc()

2021-11-11 Thread Martin Pitt
umockdev's test suite now started to see this crash in current Ubuntu jammy. Simple reproducer: $ cat tests/xorg-dummy.conf Section "Device" Identifier "test" Driver "dummy" EndSection $ Xorg -config tests/xorg-dummy.conf -logfile /tmp/log -once :5 Then, run at least one

[Bug 1949715] Re: [BPO] Backport cockpit-machines to stable releases

2021-11-10 Thread Martin Pitt
Thanks Dan! Reuploaded with s/ubuntu/bpo/. So far I used the "backportpackage" script from ubuntu-dev-tools (0.186), can this be fixed there then, please? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1949248] Re: does not show any VMs

2021-11-04 Thread Martin Pitt
Right, cockpit-machines only shows libvirt machines. So if `virsh list` is empty, so will be c-machines. ** Changed in: cockpit-machines (Ubuntu) Status: Incomplete => Won't Fix ** Summary changed: - does not show any VMs + does not show VMWare VMs -- You received this bug notification

[Bug 1949715] [NEW] [BPO] Backport cockpit-machines to stable releases

2021-11-04 Thread Martin Pitt
kpit-project/cockpit/issues/16438 ** Affects: cockpit-machines (Ubuntu) Importance: Undecided Status: Invalid ** Affects: cockpit-machines (Ubuntu Focal) Importance: Undecided Assignee: Martin Pitt (pitti) Status: In Progress ** Affects: cockpit-machines (Ubuntu Imp

[Bug 1949715] Re: [BPO] Backport cockpit-machines to stable releases

2021-11-04 Thread Martin Pitt
Uploaded to https://launchpad.net/ubuntu/impish/+queue?queue_state=1 and https://launchpad.net/ubuntu/focal/+queue?queue_state=1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1949715 Title: [BPO]

[Bug 1949248] Re: cockpit packages are not at the same version

2021-10-30 Thread Martin Pitt
cockpit-dashboard was removed in 234 [1], its functionality got integrated into cockpit-shell and cockpit-system. cockpit-machines got split into its own source package and thus now has an independent version number. [1] https://cockpit-project.org/blog/cockpit-234.html So devoting this to the

[Bug 1946244] [NEW] When installing/uninstalling with realmd, uninstalling crashes with ScriptError

2021-10-06 Thread Martin Pitt
Public bug reported: ProblemType: Crash DistroRelease: Ubuntu 21.04 PackageVersion: python3-ipaclient 4.8.6-1ubuntu5 SourcePackage: freeipa Architecture: amd64 Joining a FreeIPA domain with plain ipa-client-install works well: # ipa-client-install -p admin --password=SECRET --no-ntp [...] The

[Bug 1946244] Re: When installing/uninstalling with realmd, uninstalling crashes with

2021-10-06 Thread Martin Pitt
For completeness, this is /var/log/ipaclient-install from the successful "realm join". ** Attachment added: "ipaclient-install.log from realmd join" https://bugs.launchpad.net/ubuntu/+source/freeipa/+bug/1946244/+attachment/5531110/+files/ipaclient-install.log ** Summary changed: - When

[Bug 1945321] Re: umockdev 0.16.3-1 breaks autopkgtest of bolt

2021-09-28 Thread Martin Pitt
Christian, as I write above I believe this really needs to be fixed in bolt's tests. The umockdev change was a bug fix which bolt's tests (incorrectly) worked around. So I hope you don't mind that I flipped the affected package around? I am in contact with Christian now, and hope to sort this out

[Bug 1945321] Re: umockdev 0.16.3-1 breaks autopkgtest of bolt

2021-09-28 Thread Martin Pitt
> I am in contact with Christian now, and hope to sort this out soon. Sorry -- I meant Christian Kellner, bolt's upstream, not you :-) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1945321 Title:

[Bug 1945321] Re: umockdev 0.16.3-1 breaks autopkgtest of bolt

2021-09-28 Thread Martin Pitt
) Status: New => In Progress ** Changed in: bolt (Ubuntu) Assignee: (unassigned) => Martin Pitt (pitti) ** Changed in: umockdev (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubun

[Bug 1934995] Re: Broken on ppc64el (toolchain bug?)

2021-07-25 Thread Martin Pitt
Indeed the open(2) manpage is misleading in that regard. The actual definition in fcntl.h is like this: extern int open (const char *__file, int __oflag, ...) __nonnull ((1)); (with a few variants, but they all use varargs). So I did the same in umockdev for full header compatibility. --

[Bug 1934995] Re: Broken on ppc64el (toolchain bug?)

2021-07-08 Thread Martin Pitt
Dang, we already found a ppc64el SIGBUS issue in 0.16.0, which got fixed in https://github.com/martinpitt/umockdev/commit/277c80243a . But this is reported against 0.16.1 already. There is a tiny chance that https://github.com/martinpitt/umockdev/commit/264cabbb will magically fix this, but

[Bug 1925822] Re: [21.04 regression] formatting vfat times out

2021-05-10 Thread Martin Pitt
I installed udisks2 2.9.2-1ubuntu1 from hirsute-proposed, and confirm that both the manual test case above as well as cockpit's automatic TestStorageFormat.testFormatTypes now succeed. Thank you Sebastien and Robie! ** Tags removed: verification-needed verification-needed-hirsute ** Tags added:

[Bug 1802005] Re: socket is inaccessible for libvirt-dbus

2021-04-28 Thread Martin Pitt
** Changed in: libvirt (Ubuntu Hirsute) Status: New => 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/1802005 Title: socket is inaccessible for libvirt-dbus To manage notifications

[Bug 1925822] Re: [21.04 regression] formatting vfat times out

2021-04-27 Thread Martin Pitt
Argh indeed, forgot about that one already -- I even looked at that before, it's tracked here: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=983751 But you knew that as well, in comment #4 -- So I hope this didn't take too much time to track down. Merci beaucoup ! ** Bug watch added: Debian

[Bug 1925822] Re: [21.04 regression] formatting vfat times out

2021-04-26 Thread Martin Pitt
Direct mkfs works: # mkfs.vfat -I -n label /dev/vdb mkfs.fat 4.2 (2021-01-31) mkfs.fat: Warning: lowercase labels might not work properly on some systems # blkid -p /dev/vdb /dev/vdb: PTUUID="892240dd" PTTYPE="dos" ** Changed in: udisks2 (Ubuntu) Status: Incomplete => New -- You

[Bug 1925822] Re: [21.04 regression] formatting vfat times out

2021-04-26 Thread Martin Pitt
Reproducer from scratch: # download current cloud image curl -L -O https://cloud-images.ubuntu.com/daily/server/hirsute/current/hirsute-server-cloudimg-amd64.img # nothing fancy, just admin:foobar and root:foobar curl -L -O

[Bug 1925765] Re: [21.04 regression] networking broken in containers

2021-04-24 Thread Martin Pitt
@Reinhard: > Unfortunately, I cannot confirm this on a freshly installed Ubuntu 20.04 I assume this was a typo and you really meant 21.04. > and see what's the one that breaks podman. That was easy, it's tuned. Full reproducer: apt install -y tuned podman run -it --rm -p 5000:5000 --name

[Bug 1925765] Re: [21.04 regression] networking broken in containers

2021-04-24 Thread Martin Pitt
Thanks Reinhard for trying! I'm running a standard cloud image (https ://cloud-images.ubuntu.com/daily/server/hirsute/current/hirsute-server- cloudimg-amd64.img), but with some additional packages installed. I'll go through them with a fine comb and see what's the one that breaks podman. (But

[Bug 1925822] Re: [21.04 regression] formatting vfat times out

2021-04-23 Thread Martin Pitt
Forgot to mention, there is nothing useful in the journal. The only message is this when the timeout happens: Apr 23 15:12:35 ubuntu udisksd[3116]: Error synchronizing after formatting with type `vfat': Timed out waiting for object ** Description changed: There is a regression somewhere

[Bug 1925822] Re: [21.04 regression] formatting vfat times out

2021-04-23 Thread Martin Pitt
I tried to run it in the foreground with G_MESSAGES_DEBUG=all /usr/libexec/udisks2/udisksd but still no messages aside from the timeout. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1925822

[Bug 1925822] [NEW] [21.04 regression] formatting vfat times out

2021-04-23 Thread Martin Pitt
Public bug reported: There is a regression somewhere between udisks, udev, and dosfstools. Formatting a device with vfat hangs and fails: # blkid -p /dev/sda (nothing) # busctl call org.freedesktop.UDisks2 /org/freedesktop/UDisks2/block_devices/sda org.freedesktop.UDisks2.Block Format

[Bug 1802005] Re: socket is inaccessible for libvirt-dbus

2021-04-23 Thread Martin Pitt
Thanks Christian! Lesson learned -- for 21.10 I'll update our images a few weeks *before* the release. (I found a handful of regressions so far..) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802005

[Bug 1802005] Re: socket is inaccessible for libvirt-dbus

2021-04-23 Thread Martin Pitt
This regressed in 21.04 (hirsute) again. 1.4.0-2 was synced from Debian (https://launchpad.net/ubuntu/+source/libvirt-dbus/+changelog) instead of merged. ** Tags added: hirsute regression-release ** Changed in: libvirt-dbus (Ubuntu) Status: Fix Released => Triaged ** Also affects:

[Bug 1925765] [NEW] [21.04 regression] networking broken in containers

2021-04-23 Thread Martin Pitt
Public bug reported: This stopped working in 21.04:   podman run -it --rm -p 5000:5000 --name registry docker.io/registry:2   curl http://localhost:5000/v2/ The curl just hangs forever. This works fine in Ubuntu 20.10 with podman 2.0.6+dfsg1-1ubuntu1. Outbound direction is also broken: #

[Bug 1861053] Re: no fatrace output in focal

2021-03-12 Thread Martin Pitt
** Changed in: fatrace (Ubuntu) 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/1861053 Title: no fatrace output in focal To manage notifications about this bug go

[Bug 1916485] Re: test -x fails inside shell scripts in containers

2021-02-26 Thread Martin Pitt
I've been scratching my head over this regression [1] for a while now, in the context of running a hirsute container on a 20.04 host (in particular, a GitHub workflow machine) In my case, the symptom is that after upgrading glibc, `which` is broken; that of course also uses faccessat(), similar to

[Bug 1848923] Re: pollinate.service fails to start: ERROR: should execute as the [pollinate] user -- missing CacheDirectory=

2021-02-15 Thread Martin Pitt
I now did exactly the same steps as above on an Ubuntu 20.04 VM, with exactly the same results. This verifies 4.33-3ubuntu1.20.04.1. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 1848923] Re: pollinate.service fails to start: ERROR: should execute as the [pollinate] user -- missing CacheDirectory=

2021-02-15 Thread Martin Pitt
Verification for groovy: I took a 20.10 VM with current pollinate 4.33-3ubuntu1, and after booting, pollinate.service is in state failed as per the bug description. I then updated to 4.33-3ubuntu1.20.10.1. The package update auto- restarted pollinate.service, and it looked successful: #

[Bug 1848923] Re: pollinate.service fails to start: ERROR: should execute as the [pollinate] user -- missing CacheDirectory=

2021-02-11 Thread Martin Pitt
@Christian: Debian still needs/wants to support sysvinit. Of course init.d scripts ought to create cache directories too (like munin, mopidy, and others already do, but probably not all of them), but that will be a bit more work. FHS applies to SysV init as well, so the same reasoning still holds.

[Bug 1848923] Re: pollinate.service fails to start: ERROR: should execute as the [pollinate] user -- missing CacheDirectory=

2021-02-09 Thread Martin Pitt
** Changed in: pollinate (Ubuntu) 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/1848923 Title: pollinate.service fails to start: ERROR: should execute as the

[Bug 1848923] Re: pollinate.service fails to start: ERROR: should execute as the [pollinate] user -- missing CacheDirectory=

2021-02-08 Thread Martin Pitt
> Where could we download one of them to check the state of that path in there? See comment #7: git clone https://github.com/cockpit-project/bots/ bots/vm-run ubuntu-stable But I suppose that's moot now :) -- You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 1848923] Re: pollinate.service fails to start: ERROR: should execute as the [pollinate] user -- missing CacheDirectory=

2021-02-08 Thread Martin Pitt
Indeed all our images clear up /var/cache [1]. Sorry, I forgot about this bit before! An admin should always be able to rm -rf /var/cache, reboot, and get a fully working system [2]. So if the pollinate data is in any way precious, it should better be in /var/lib/pollinate then (similar to

[Bug 1848923] Re: pollinate.service fails to start: ERROR: should execute as the [pollinate] user

2021-02-07 Thread Martin Pitt
Thanks Christian! Interesting, the "ERROR: should execute as the [pollinate] user" looks quite unrelated to any networking setup and smelled like a package postinst/systemd unit bug. I started trying to reproduce this outside of the Ubuntu CI, with a most naïve curl -O

[Bug 1848923] Re: pollinate.service fails to start: ERROR: should execute as the [pollinate] user

2021-02-04 Thread Martin Pitt
I just tested on current 20.04 and 20.10 cloud images, still the same bug. There was exactly one upload since then [1] which was trivial (just updating the watch file). [1] https://launchpad.net/ubuntu/+source/pollinate/+changelog ** Changed in: pollinate (Ubuntu) Status: Incomplete =>

[Bug 1848923] Re: pollinate.service fails to start: ERROR: should execute as the [pollinate] user

2021-02-04 Thread Martin Pitt
One more thing: That package hasn't worked in literally years, and is also obsolete. QEMU has had `-device virtio-rng-pci` for a long time now, libvirt uses it by default, and apparently most cloud providers use that, too. So I suggest to remove the package from Ubuntu, but *at least* from the

[Bug 1906320] Re: fake-device-wrapper should bind-mount efivars

2020-11-30 Thread Martin Pitt
FTR, I would strongly advise against that, see https://github.com/martinpitt/umockdev/issues/110#issuecomment-736224503 . You want the tests to work independently on the hardware it's running on, so that you can run it on e.g. standard autopkgtest infra. You could create

[Bug 1905212] Re: On 20.04 arm64 (raspberry) can't install cockpit from focal-backports

2020-11-24 Thread Martin Pitt
Sorry, it wasn't built on armhf/arm64 yet: https://launchpad.net/ubuntu/+source/cockpit/231-1~ubuntu20.04.1 There's currently some hw maintenance going on: https://lists.ubuntu.com/archives/launchpad- announce/2020-November/000107.html -- You received this bug notification because you are a

[Bug 1905212] Re: On 20.04 arm64 (raspberry) can't install cockpit from focal-backports

2020-11-24 Thread Martin Pitt
This is the wrong way to invoke apt, as the package/release syntax will install *only* that package from backports, but resolve all dependencies from main. Please try this: sudo apt install -t focal-backports cockpit ** Changed in: cockpit (Ubuntu) Status: New => Invalid -- You

[Bug 1892756] Re: System libvirt-dbus broken after changing libvirtd.socket SocketMode to 0660

2020-08-25 Thread Martin Pitt
ISTM that adding the libvirt-dbus user into the libvirt group is the right fix here. According to /usr/share/dbus-1/system.d/org.libvirt.conf only root and libvirt group users can call its interface. So that useradd seems correct to me, and it should be put into the Debian package. Unfortunately

[Bug 1885188] Re: fatrace autopkgtest failure due to rename test

2020-08-22 Thread Martin Pitt
https://github.com/martinpitt/fatrace/releases/tag/0.16 I uploaded this to Debian as well, from where it should get auto- imported into groovy. ** Changed in: fatrace Status: Fix Committed => Fix Released ** Changed in: fatrace (Ubuntu) Status: In Progress => Fix Committed --

[Bug 1861053] Re: no fatrace output in focal

2020-08-22 Thread Martin Pitt
FTR, I just ran fatrace a lot in a current Ubuntu 20.04 VM to debug #1885188, and it seems fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1861053 Title: no fatrace output in focal To manage

[Bug 1885188] Re: fatrace autopkgtest failure due to rename test

2020-08-22 Thread Martin Pitt
anged in: fatrace (Ubuntu) Assignee: (unassigned) => Martin Pitt (pitti) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885188 Title: fatrace autopkgtest failure due to rename test To manag

[Bug 1885188] Re: fatrace autopkgtest failure due to rename test

2020-08-22 Thread Martin Pitt
** Changed in: fatrace Assignee: (unassigned) => Martin Pitt (pitti) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1885188 Title: fatrace autopkgtest failure due to rename test To man

[Bug 1885188] Re: fatrace autopkgtest failure due to rename test

2020-08-22 Thread Martin Pitt
Thanks Christian for your initial investigations! I'm back from vacation, looking into this now. Observations: * The 0.13 tests still work fine , so this is indeed a problem with the "new" FAN_REPORT_FID mode. * I finally moved

[Bug 1890786] [NEW] ipa-client-install fails on restarting non-existing chronyd.service

2020-08-07 Thread Martin Pitt
Public bug reported: DistroRelease: Ubuntu 20.10 Package: freeipa-client 4.8.6-1ubuntu2 Client install fails: * LANG=C /usr/sbin/ipa-client-install --domain cockpit.lan --realm COCKPIT.LAN --mkhomedir --enable-dns-updates --unattended --force-join --principal admin -W --force-ntpd Option

[Bug 1799095] Re: Firewalld nftables backend breaks networking of libvirt

2020-08-07 Thread Martin Pitt
This somehow does not affect Ubuntu 20.04 LTS, but it does affect the current "groovy" release again: # virsh net-start default error: Failed to start network default error: internal error: firewalld is set to use the nftables backend, but the required firewalld 'libvirt' zone is missing. Either

[Bug 1831467] Re: test-umockdev tests flaky on armhf (and sometimes other archs)

2020-07-29 Thread Martin Pitt
https://salsa.debian.org/debian/umockdev/-/commit/87b476aee2 should hopefully help. I uploaded 0.14.2 to Debian unstable now, it should auto-sync into Groovy soon. Thanks Dan for tackling this! ** Changed in: umockdev (Ubuntu Groovy) Status: In Progress => Fix Committed -- You received

[Bug 1875028] Re: Package cockpit-docker cannot be found

2020-04-25 Thread Martin Pitt
Right, this is intended, we stopped supporting cockpit-docker upstream: https://cockpit-project.org/blog/cockpit-215.html The older package still works for the time being, if you install it manually. ** Changed in: cockpit (Ubuntu) Status: New => Won't Fix -- You received this bug

[Bug 1802005] Re: socket is inaccessible for libvirt-dbus

2020-02-24 Thread Martin Pitt
@Christian: Wontfix WFM, I'm glad that the default works in focal (the next LTS). For the non-LTS ones it can be worked around (write a systemd unit drop-in or so), but apparently it's not such a big issue. Thanks! -- You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 1802005] Re: socket is inaccessible for libvirt-dbus

2020-02-24 Thread Martin Pitt
Nice, thanks Christian! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802005 Title: socket is inaccessible for libvirt-dbus To manage notifications about this bug go to:

[Bug 1802005] Re: D-Bus socket is inaccessible

2020-02-18 Thread Martin Pitt
The socket is actually owned by libvirt ** Package changed: libvirt-dbus (Ubuntu) => libvirt (Ubuntu) ** Summary changed: - D-Bus socket is inaccessible + socket is inaccessible for libvirt-dbus -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed

[Bug 1802005] Re: D-Bus socket is inaccessible

2019-12-29 Thread Martin Pitt
Here as well: https://www.reddit.com/r/linuxquestions/comments/c7hcfe/whack_issues_with_cockpit_and_ubuntu_server_1904/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802005 Title: D-Bus socket is

[Bug 1802005] Re: D-Bus socket is inaccessible

2019-12-29 Thread Martin Pitt
Other users run into this as well: https://github.com/cockpit- project/cockpit/issues/13339 ** Bug watch added: github.com/cockpit-project/cockpit/issues #13339 https://github.com/cockpit-project/cockpit/issues/13339 ** Changed in: libvirt-dbus (Ubuntu) Status: New => Confirmed --

[Bug 1850281] Re: package pcp 4.3.4-1build1 failed to install/upgrade: installed pcp package post-installation script subprocess returned error exit status 1

2019-11-07 Thread Martin Pitt
We see this in our Cockpit test image creation as well. ** Bug watch added: Red Hat Bugzilla #1721223 https://bugzilla.redhat.com/show_bug.cgi?id=1721223 ** Also affects: pcp (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=1721223 Importance: Unknown Status: Unknown **

[Bug 1802005] Re: D-Bus socket is inaccessible

2019-10-28 Thread Martin Pitt
** Tags added: disco eoan -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1802005 Title: D-Bus socket is inaccessible To manage notifications about this bug go to:

[Bug 1848923] [NEW] pollinate.service fails to start: ERROR: should execute as the [pollinate] user

2019-10-20 Thread Martin Pitt
Public bug reported: In a standard Ubuntu 19.10 cloud image install, pollinate fails to start: ● pollinate.service - Pollinate to seed the pseudo random number generator    Loaded: loaded (/lib/systemd/system/pollinate.service; enabled; vendor preset: enabled)    Active: failed (Result:

[Bug 1845157] Re: runner/autopkgtest fails to setup env with binary packages moved to another packge, and different source/binary versions

2019-10-02 Thread Martin Pitt
Fix landed in autopkgtest master. Thanks Dan! ** Changed in: autopkgtest (Ubuntu) Status: New => 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/1845157 Title:

[Bug 1826187] Re: firewalld fails to start: FATAL ERROR: No IPv4 and IPv6 firewall: looks for binaries in wrong paths

2019-09-10 Thread Martin Pitt
This magically went away on the most recent daily cloud images. @wvengen, does it work for you again as well? If so, we can close this. Thanks! ** Changed in: firewalld (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 1837233] Re: [bionic] Manual IPv6 routes are not set

2019-07-19 Thread Martin Pitt
Nevermind then, this is working well enough for a stable release. ** Changed in: network-manager (Ubuntu Bionic) Status: New => 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/1837233

[Bug 1837233] Re: [bionic] Manual IPv6 routes are not set

2019-07-19 Thread Martin Pitt
I confirm that using a valid IP works better: In the config: route1=fe80:2::/60,fe80::99,42 # ip -6 route show dev eth2 fe80::/64 proto kernel metric 101 pref medium fe80::/64 proto kernel metric 256 pref medium fe80:2::/60 via fe80::99 proto static metric 42 pref medium It's still missing the

[Bug 1837233] Re: [bionic] Manual IPv6 routes are not set

2019-07-19 Thread Martin Pitt
The journal says why: NetworkManager[1295]: [1563552648.1667] platform: route-sync: failure to add IPv6 route: 1:2::/60 via 1:2::3 dev 6 metric 42 mss 0 rt-src user: No route to host (113) NetworkManager[1295]: [1563552648.1672] device (eth2): failed to apply manual IPv6 configuration

  1   2   3   4   5   6   7   8   9   10   >