[Touch-packages] [Bug 2004241] Re: Update to glib >= 2.75.1

[Daniel van Vugt]

** Changed in: glib2.0 (Ubuntu)
   Importance: Low => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2004241

Title:
  Update to glib >= 2.75.1

Status in glib2.0 package in Ubuntu:
  Fix Committed

Bug description:
  Update to glib >= 2.75.1 because that's what mutter 44 now requires.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2004241/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2004241] Re: Update to glib >= 2.75.1

[Treviño]

Snapd just migrated, we can remove the block.

** Tags removed: block-proposed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2004241

Title:
  Update to glib >= 2.75.1

Status in glib2.0 package in Ubuntu:
  Fix Committed

Bug description:
  Update to glib >= 2.75.1 because that's what mutter 44 now requires.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2004241/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2008279] Re: glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if IBus is turned on

[Launchpad Bug Tracker]

This bug was fixed in the package snapd - 2.58.3+23.04ubuntu1

---
snapd (2.58.3+23.04ubuntu1) lunar; urgency=medium

  * Cherry pick a fix from James Henstridge to grant access to new ibus
socket location in desktop-legacy,fixes text input isn't working anymore
in the firefox snap with glib 2.75 (lp: #2008279)

 -- Sebastien Bacher   Wed, 08 Mar 2023 13:50:10
+0100

** Changed in: snapd (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ibus in Ubuntu.
https://bugs.launchpad.net/bugs/2008279

Title:
  glib2.0 2.75.3-3 breaks text input for Firefox & Chromium snaps if
  IBus is turned on

Status in glib2.0 package in Ubuntu:
  Invalid
Status in ibus package in Ubuntu:
  Invalid
Status in snapd package in Ubuntu:
  Fix Released

Bug description:
  Test Case
  -
  From Ubuntu 23.04, install glib >= 2.75.3-3

  Test 1:
  Log out
  Click your name on the login screen.
  Click the gear button to choose Ubuntu on Xorg
  Enter your password to finish logging in.
  Open Firefox (or Chromium)
  Try to enter text in the address bar.

  Test 2:
  Install the ibus-libpinyin package.
  Log out and log in again.
  Go to Settings -> Keyboard and add "Chinese (Intelligent Pinyin)"
   to your input sources.
  Log out
  Click your name on the login screen.
  Click the gear button to choose Ubuntu (on Wayland).
  Enter your password to finish logging in.
  Open Firefox (or Chromium)
  Try to enter text in the address bar.

  What Happens
  
  No text is inputted

  Other Info
  --
  You see the issue as soon as IBus has been 'turned on'. With the current 
g-s-d version you need to somehow trigger a need to turn IBus on. In an X11 
session IBus is always turned on due to im-config 0.55-1. In a Wayland session 
you need to tell it to turn IBus on by either adding an IBus input method to 
your input sources or make use of the Screen Keyboard feature.

  And I've only seen the issue with the Firefox and Chromium snaps.

  Warning message if you start firefox from terminal:

  [Parent 3792, Main Thread] WARNING: Unable to connect to ibus: Could
  not connect: Permission denied: 'glib warning', file
  /build/firefox/parts/firefox/build/toolkit/xre/nsSigHandlers.cpp:167

  (firefox:3792): IBUS-WARNING **: 15:23:11.814: Unable to connect to
  ibus: Could not connect: Permission denied

  gnome-settings-daemon
  -
  gnome-settings-daemon 44 Beta makes the situation worse since it always turns 
IBus on in both Wayland and X11, but I reverted 
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/27bc0889c so that 
we could continue with the update. See 
https://salsa.debian.org/gnome-team/gnome-settings-daemon/-/commit/baeeed93

  Before I did that, I tested disabling our patches but it didn't make a
  difference.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2008279/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2006517] Re: Bluetooth works on desktop but not on ubuntu core

[Rex Tsai]

The title of the bug seems incorrect, the Bluetooth AdvertisementMonitor
does not work with bluetoohd from bluez 22/stable: 5.64-2 2022-05-03
with Ubuntu Core22 on Dell Precision 5570.

I would assume the rest of bluetooth functions and profile are still working, eg
% bluetoothctl show

If order to isolate the root cause is between kernel hci driver or bluetoothd. 
Could you please run the following commands on core to see if the hci driver 
works as expected? 
% sudo btmgmt version
% sudo btmgmt revision
% sudo btmgmt monitor.features
% sudo btmon --mgmt

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/2006517

Title:
  Bluetooth works on desktop but not on ubuntu core

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  We have built a snap that uses some bluetooth functionality.

  The snap runs well when using Ubuntu desktop 22.04 (all updates applied end 
of Jan 2022).
  We have tried using this same snap on Ubuntu Core 22 running on X86_64.

  On some hardware platforms (thinkpad E15 and x86 Mac) everything works as 
expected.
  We can install the snap on Jammy 22.04 or Core 22 on these platforms and get 
expected functionality regardless of OS.

  
  On our targeted platform (a Dell 5570) things are not working.  When running 
22.04 Jammy, everything works.  When running Core 22, some advanced bluetooth 
functionality is not available.
  Since the Core 22 image installs and runs on other X86_64 hardware we suspect 
a device driver issue.

  Attached are several files taken from the Dell 5570
  1) dmesg from Core 22.
  2) dmesg from Jammy 22.04
  3) output of lspci from Jammy 22.04
  4) Output of lsusb from Jammy 22.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2006517/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2009575] Re: Upgrade to 3.1.3-8ubuntu0.5 causing sync errors

[Haw Loeung]

See also LP:2009756 & https://github.com/bit-team/backintime/issues/1247

** Bug watch added: BackInTime Issues #1247
   https://github.com/bit-team/backintime/issues/1247

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/2009575

Title:
  Upgrade to 3.1.3-8ubuntu0.5 causing sync errors

Status in rsync package in Ubuntu:
  Invalid

Bug description:
  Hi

  Several systems running Ubuntu 20.04 upgraded their rsync package from
  3.1.3-8ubuntu0.4 to 3.1.3-8ubuntu0.5 overnight.

  Automated syncs that connect to a 16.04 ESM server are now failing
  with:

  receiving file list ...
  ERROR: rejecting unrequested file-list name: [redacted]
  rsync error: protocol incompatibility (code 2) at flist.c(916) 
[Receiver=3.1.3]

  Reverting to the previous release (3.1.3-8ubuntu0.4) on the client
  side solves the problem.

  This has been seen on multiple servers running 20.04 on amd64, I'll
  update this bug with details if we find it on other series too.

  The 16.04 ESM server being connected to is using the rsync package
  version 3.1.1-3ubuntu1.3+esm2, so no recent upgrades on that end.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/2009575/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2009738] Re: no lxc manpage

[Simon Déziel]

Did I mentioned it was not convenient? :P

$ d="$(mktemp -d)"
$ lxc manpage "$d"
$ ls -1 "$d"
lxc.1
lxc.alias.1
lxc.alias.add.1
lxc.alias.list.1
lxc.alias.remove.1
lxc.alias.rename.1
lxc.cluster.1
lxc.cluster.add.1
...
$ ls -1 "$d" | wc -l
293

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/2009738

Title:
  no lxc manpage

Status in lxc package in Ubuntu:
  New

Bug description:
  Hello, I don't have an lxc manpage on my focal system:

  $ man lxc
  No manual entry for lxc

  $ dpkg -l lxd | grep lxd ; snap info lxd | grep installed
  un  lxd  (no description available)
  installed:  5.11-ad0b61e (24483) 149MB -

  It looks a bit like none are packaged:

  $ find /snap/lxd -name '*.1.gz' -o -name '*.7.gz' -o -name '*.8.gz'
  $ 

  While I appreciate the online --help output, I also like having
  longer-form documentation available on a system without needing to use
  a web browser.

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: lxc (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-139.156-generic 5.4.224
  Uname: Linux 5.4.0-139-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Mar  8 18:21:08 2023
  SourcePackage: lxc
  UpgradeStatus: Upgraded to focal on 2020-01-24 (1138 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2009738/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1989410] Re: Not able to connect to hotspot because of WPA2 WPA3 security

[Kenichi Usami]

I have been waiting for this fix.
Please kindly assign someone to fix it.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to wpa in Ubuntu.
https://bugs.launchpad.net/bugs/1989410

Title:
  Not able to connect to hotspot because of WPA2 WPA3 security

Status in wpa package in Ubuntu:
  New

Bug description:
  Both security WPA2 and WPA3 displaying on the security section due to
  this not able to connect the hotspot.

  Same device and firmware working properly in ubuntu 20.04 OS, But in
  ubuntu 22.04 we are facing this issue.

  "nmcli dev wifi" on client side:

  On Ubuntu 20.04:

  IN-USE

  SSID  ubuntu_new_golden  
  MODE  Infra
  CHAN  1
  RATE  130Mbit/s
  SECURITY WPA2 

  
  On Ubuntu 22.04:

  IN-USE

  SSID  ubuntu_new_golden  
  MODE  Infra
  CHAN  1
  RATE  130Mbit/s
  SECURITY WPA2 WPA3

  Only difference we can see is SECURITY

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libwpa-client-dev 2:2.10-6ubuntu2
  Uname: Linux 5.19.0-rpl-ww37bkc x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5json:
   {
 "result": "skip"
   }
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep 15 12:23:41 2022
  Dependencies:
   
  InstallationDate: Installed on 2022-09-10 (4 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1989410/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2004241] Re: Update to glib >= 2.75.1

[Daniel van Vugt]

** Changed in: glib2.0 (Ubuntu)
   Status: Triaged => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2004241

Title:
  Update to glib >= 2.75.1

Status in glib2.0 package in Ubuntu:
  Fix Committed

Bug description:
  Update to glib >= 2.75.1 because that's what mutter 44 now requires.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2004241/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2009738] Re: no lxc manpage

[Seth Arnold]

Ah, thanks twice over. I've poked the old bug with a hope for a happier
answer today :) Unfortunately lxc manpage isn't exactly ideal:

$ lxc manpage lxc
Error: open 
/var/lib/snapd/hostfs/home/sarnold/tmp/takehometests/lxc/lxc.alias.add.1: no 
such file or directory

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/2009738

Title:
  no lxc manpage

Status in lxc package in Ubuntu:
  New

Bug description:
  Hello, I don't have an lxc manpage on my focal system:

  $ man lxc
  No manual entry for lxc

  $ dpkg -l lxd | grep lxd ; snap info lxd | grep installed
  un  lxd  (no description available)
  installed:  5.11-ad0b61e (24483) 149MB -

  It looks a bit like none are packaged:

  $ find /snap/lxd -name '*.1.gz' -o -name '*.7.gz' -o -name '*.8.gz'
  $ 

  While I appreciate the online --help output, I also like having
  longer-form documentation available on a system without needing to use
  a web browser.

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: lxc (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-139.156-generic 5.4.224
  Uname: Linux 5.4.0-139-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Mar  8 18:21:08 2023
  SourcePackage: lxc
  UpgradeStatus: Upgraded to focal on 2020-01-24 (1138 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2009738/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2009756] Re: backups fail since latest rsync security update

[Marc Deslauriers]

Oh whoops, sorry about that, I'll upload a fixed version first thing
tomorrow (after at least installing it this time).

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/2009756

Title:
  backups fail since latest rsync security update

Status in backintime package in Ubuntu:
  Fix Released
Status in rsync package in Ubuntu:
  New
Status in backintime source package in Jammy:
  In Progress
Status in rsync source package in Jammy:
  New
Status in backintime source package in Kinetic:
  In Progress
Status in rsync source package in Kinetic:
  New
Status in backintime source package in Lunar:
  Fix Released
Status in rsync source package in Lunar:
  New

Bug description:
  Backintime uses rsync to perform updates. Unfortunately there is an
  incompatibility between the currently released version of backintime
  and rsync >= 3.2.4 (see https://github.com/bit-
  team/backintime/issues/1247)

  Rsync has been updated from 3.2.3 to 3.2.7 on Feb 27. This broke
  backintime backups. The symptom is an error message like this:

  Command "rsync -a --delete --rsh=ssh -o ServerAliveInterval=240 -o
  LogLevel=Error -o IdentityFile=/home/aurelien/.ssh/backintime -p 22
  /tmp/tmpxilwcwk4/
  u...@example.com:"./backintime/switch/aurelien/1/20230308-230517-262""
  returns 3 | rsync: change_dir#3
  "/data/home/user//"./backintime/switch/aurelien/1" failed: No such
  file or directory (2)

  The workaround described in the GitHub issue works (passing `--old-
  args` to rsync), but maybe it would be better if the backintime
  package did this automatically?

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: backintime-common 1.2.1-3ubuntu0.1
  ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Mar  8 23:19:02 2023
  InstallationDate: Installed on 2021-06-23 (623 days ago)
  InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: backintime
  UpgradeStatus: Upgraded to jammy on 2022-08-24 (196 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/backintime/+bug/2009756/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2008952] Re: DNS failure while trying to fetch user-data

[Danilo Egea Gondolfo]

As /etc/resolv.conf is a symlink, is it possible that the nameservers
received via DHCP in the early boot stages are never stored in
/etc/resolv.conf?

cloud-init tries to resolve that address before resolved is started and
there is nothing at /etc/resolv.conf.

Does that make sense?

-- 
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/2008952

Title:
  DNS failure while trying to fetch user-data

Status in cloud-init:
  Triaged
Status in netplan:
  New
Status in subiquity:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  In testing netboot + autoinstall of the new ubuntu desktop subiquity
  based installer for 23.04 I found cloud-init is failing to retrieve
  user-data because it can't resolved the hostname in the URL.  This
  same configuration does work for 22.04 based subiquity, so seems a
  regression.

  From the ipxe config:

  imgargs vmlinuz initrd=initrd \
   ip=dhcp \
   iso-url=http://cdimage.ubuntu.com/daily-live/pending/lunar-desktop-amd64.iso 
\
   fsck.mode=skip \
   layerfs-path=minimal.standard.live.squashfs \
   autoinstall \
   'ds=nocloud-net;s=http://boot.linuxgroove.com/ubuntu/23.04/' \

  That fails, but if we replace boot.linuxgroove.com with the IP it
  works.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/2008952/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2009756] Re: backups fail since latest rsync security update

[Aurélien Gâteau]

Hi Mark,

I just tested it. Unfortunately the package fails to install:

```
Preparing to unpack .../backintime-common_1.2.1-3ubuntu0.2_all.deb ...
Unpacking backintime-common (1.2.1-3ubuntu0.2) over (1.2.1-3ubuntu0.2) ...
Preparing to unpack .../backintime-qt_1.2.1-3ubuntu0.2_all.deb ...
Unpacking backintime-qt (1.2.1-3ubuntu0.2) over (1.2.1-3ubuntu0.2) ...
Setting up backintime-common (1.2.1-3ubuntu0.2) ...
  File "/usr/share/backintime/common/snapshots.py", line 596
sid.path(use_mode = ['ssh', 'ssh_encfs'])
^
SyntaxError: invalid syntax. Perhaps you forgot a comma?
dpkg: error processing package backintime-common (--install):
 installed backintime-common package post-installation script subprocess 
returned error exit status 1
dpkg: dependency problems prevent configuration of backintime-qt:
 backintime-qt depends on backintime-common (= 1.2.1-3ubuntu0.2); however:
  Package backintime-common is not configured yet.
```

After looking at the code, I think line 596 is indeed missing a comma at
the end.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/2009756

Title:
  backups fail since latest rsync security update

Status in backintime package in Ubuntu:
  Fix Released
Status in rsync package in Ubuntu:
  New
Status in backintime source package in Jammy:
  In Progress
Status in rsync source package in Jammy:
  New
Status in backintime source package in Kinetic:
  In Progress
Status in rsync source package in Kinetic:
  New
Status in backintime source package in Lunar:
  Fix Released
Status in rsync source package in Lunar:
  New

Bug description:
  Backintime uses rsync to perform updates. Unfortunately there is an
  incompatibility between the currently released version of backintime
  and rsync >= 3.2.4 (see https://github.com/bit-
  team/backintime/issues/1247)

  Rsync has been updated from 3.2.3 to 3.2.7 on Feb 27. This broke
  backintime backups. The symptom is an error message like this:

  Command "rsync -a --delete --rsh=ssh -o ServerAliveInterval=240 -o
  LogLevel=Error -o IdentityFile=/home/aurelien/.ssh/backintime -p 22
  /tmp/tmpxilwcwk4/
  u...@example.com:"./backintime/switch/aurelien/1/20230308-230517-262""
  returns 3 | rsync: change_dir#3
  "/data/home/user//"./backintime/switch/aurelien/1" failed: No such
  file or directory (2)

  The workaround described in the GitHub issue works (passing `--old-
  args` to rsync), but maybe it would be better if the backintime
  package did this automatically?

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: backintime-common 1.2.1-3ubuntu0.1
  ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Mar  8 23:19:02 2023
  InstallationDate: Installed on 2021-06-23 (623 days ago)
  InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: backintime
  UpgradeStatus: Upgraded to jammy on 2022-08-24 (196 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/backintime/+bug/2009756/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2008952] Re: DNS failure while trying to fetch user-data

[Danilo Egea Gondolfo]

It doesn't seem to be caused by a race between networkd and
NetworkManager.

I reproduced the issue with qemu here and I see the name resolution
failure happening few seconds before NetworkManager started.

>From /var/log/cloud-init.log:

2023-03-09 19:17:58,443 - util.py[DEBUG]: Getting data from  failed
Traceback (most recent call last):
...
cloudinit.url_helper.UrlError: HTTPConnectionPool(host='boot.linuxgroove.com', 
port=80): Max retries exceeded with url: /ubuntu/23.04/meta-data (Caused by 
NewConnectionError(':
Failed to establish a new connection: [Errno -3] Temporary failure in name 
resolution'))

>From systemd's journal
Mar 09 19:18:01 ubuntu systemd[1]: Starting NetworkManager.service - Network 
Manager...

(edit)

resolved wasn't running as well

2023-03-09T19:18:01.712656+00:00 ubuntu systemd[1]: Starting systemd-
resolved.service - Network Name Resolution...

-- 
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/2008952

Title:
  DNS failure while trying to fetch user-data

Status in cloud-init:
  Triaged
Status in netplan:
  New
Status in subiquity:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  In testing netboot + autoinstall of the new ubuntu desktop subiquity
  based installer for 23.04 I found cloud-init is failing to retrieve
  user-data because it can't resolved the hostname in the URL.  This
  same configuration does work for 22.04 based subiquity, so seems a
  regression.

  From the ipxe config:

  imgargs vmlinuz initrd=initrd \
   ip=dhcp \
   iso-url=http://cdimage.ubuntu.com/daily-live/pending/lunar-desktop-amd64.iso 
\
   fsck.mode=skip \
   layerfs-path=minimal.standard.live.squashfs \
   autoinstall \
   'ds=nocloud-net;s=http://boot.linuxgroove.com/ubuntu/23.04/' \

  That fails, but if we replace boot.linuxgroove.com with the IP it
  works.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/2008952/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1741775] Re: bad symlink "/etc/resolvconf/resolv.conf.d/original"

[Lee Maguire]

I see this issue on a fresh install of Ubuntu 22.04, where
"/etc/resolv.conf" exists as a symlink before resolvconf is installed,
creating a dangling symlink in "/etc/resolvconf/resolv.conf.d/original".

I believe the line in resolvconf.postinst that creates the file

   cp -a /etc/resolv.conf /etc/resolvconf/resolv.conf.d/original

could be changed to

   cp -L --preserve=all /etc/resolv.conf
/etc/resolvconf/resolv.conf.d/original

to ensure that, if a symlink, the actual file is preserved.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to resolvconf in Ubuntu.
https://bugs.launchpad.net/bugs/1741775

Title:
  bad symlink "/etc/resolvconf/resolv.conf.d/original"

Status in resolvconf package in Ubuntu:
  Triaged

Bug description:
  Ubuntu 17.10 amd_64
  resolvconf 1.79ubuntu8

  The symlink at "/etc/resolvconf/resolv.conf.d/original" points to
  "../run/systemd/resolve/stub-resolv.conf". This is a broken link as
  the relative path does not exist. This causes resolvconf to improperly
  (re-)generate "/run/resolvconf/resolv.conf". The link should probably
  instead point to the absolute path "/run/systemd/resolve/stub-
  resolv.conf".

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1741775/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2000817] Re: Wrong SHA256-value computed on kinetic

[Launchpad Bug Tracker]

This bug was fixed in the package openldap - 2.6.3+dfsg-1~exp1ubuntu2

---
openldap (2.6.3+dfsg-1~exp1ubuntu2) lunar; urgency=medium

  * Build the passwd/sha2 contrib module with -fno-strict-aliasing to
avoid computing an incorrect SHA256 hash with some versions of the
compiler (LP: #2000817):
- d/t/{control,sha2-contrib}: test to verify the SHA256 hash
  produced by passwd/sha2
- d/rules: set -fno-strict-aliasing only when building the
  passwd/sha2 contrib module
  * d/t/smbk5pwd: Allow the openldap user to read the Heimdal master key in the
smbk5pwd DEP8 test (LP: #2004560)

 -- Andreas Hasenack   Fri, 03 Feb 2023 09:33:14
-0300

** Changed in: openldap (Ubuntu Lunar)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/2000817

Title:
  Wrong SHA256-value computed on kinetic

Status in openldap package in Ubuntu:
  Fix Released
Status in openldap source package in Jammy:
  In Progress
Status in openldap source package in Kinetic:
  In Progress
Status in openldap source package in Lunar:
  Fix Released
Status in openldap package in Debian:
  Unknown

Bug description:
  The OpenLDAP-contrib module sha2 (located in contrib/slapd-
  modules/passwd/sha2/) computes a wrong SHA256/SSHA256-hash on Ubuntu
  kinetic. This breaks our current password-authentication in ldap.

  
  The problematic computation:

  $ slappasswd -s secret -h '{SHA256}' -o module-load=pw-sha2
  {SHA256}WIrrpN3OjEVOUf6yrH1j+o+ODuUuNBo979Od4UXnu54=

  The (correct) reference-value on the same system (or older ubuntu
  Versions):

  $ echo -n "secret" | openssl dgst -sha256 -binary | openssl enc -base64
  K7gNU3sdo+OL0wNhqoVWhr3g6s1xYv72ol/pe/Unols=

  
  We nailed the problem down to a bug in the gcc-optimizer for strict-aliasing. 
so most probably the gcc-version on kinetic (v12.2.0) is the reason. The 
workaround is to compile the sha2-Module with the flag "-fno-strict-aliasing". 
Then the correct value is computed. An example taken from a git-compiled 
version of OpenLDAP 2.5.13:

  $ ./servers/slapd/slappasswd -T passwd -s secret -h '{SHA256}' -o 
module-load=pw-sha2 -o module-path=contrib/slapd-modules/passwd/sha2/.libs
  {SHA256}K7gNU3sdo+OL0wNhqoVWhr3g6s1xYv72ol/pe/Unols=


  
  Ubuntu:

  Description:Ubuntu 22.10
  Release:22.10

  OpenLDAP-Package: 2.5.13+dfsg-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/2000817/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2004560] Re: smbk5pwd test fails due to perms (FS and AppArmor)

[Launchpad Bug Tracker]

This bug was fixed in the package openldap - 2.6.3+dfsg-1~exp1ubuntu2

---
openldap (2.6.3+dfsg-1~exp1ubuntu2) lunar; urgency=medium

  * Build the passwd/sha2 contrib module with -fno-strict-aliasing to
avoid computing an incorrect SHA256 hash with some versions of the
compiler (LP: #2000817):
- d/t/{control,sha2-contrib}: test to verify the SHA256 hash
  produced by passwd/sha2
- d/rules: set -fno-strict-aliasing only when building the
  passwd/sha2 contrib module
  * d/t/smbk5pwd: Allow the openldap user to read the Heimdal master key in the
smbk5pwd DEP8 test (LP: #2004560)

 -- Andreas Hasenack   Fri, 03 Feb 2023 09:33:14
-0300

** Changed in: openldap (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/2004560

Title:
  smbk5pwd test fails due to perms (FS and AppArmor)

Status in openldap package in Ubuntu:
  Fix Released

Bug description:
  https://autopkgtest.ubuntu.com/packages/o/openldap/lunar/amd64

  autopkgtest [16:06:32]: test smbk5pwd: [---
  adding new entry "cn=samba,cn=schema,cn=config"

  SASL/EXTERNAL authentication started
  SASL username: gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth
  SASL SSF: 0
  SASL/EXTERNAL authentication started
  SASL username: gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth
  SASL SSF: 0
  adding new entry "cn=hdb,cn=schema,cn=config"

  SASL/EXTERNAL authentication started
  SASL username: gidNumber=0+uidNumber=0,cn=peercred,cn=external,cn=auth
  SASL SSF: 0
  modifying entry "cn=module{0},cn=config"

  adding new entry "olcOverlay=smbk5pwd,olcDatabase={1}mdb,cn=config"

  ldap_add: Other (e.g., implementation specific) error (80)
additional info:  handler exited with 1
  autopkgtest [16:06:33]: test smbk5pwd: ---]
  autopkgtest [16:06:33]: test smbk5pwd:  - - - - - - - - - - results - - - - - 
- - - - -
  smbk5pwd FAIL non-zero exit status 80

  I reproduced this in a container, and the failure is two-fold:

  a) /var/lib/heimdal-kdc/ is root:root 0700, and the slapd server needs
  FS read access to the key

  b) Then the slapd apparmor profile blocks it:
  [qui fev  2 09:54:02 2023] audit: type=1400 audit(1675342444.436:3242): 
apparmor="DENIED" operation="open" class="file" 
namespace="root//lxd-l-dep8_" 
profile="/usr/sbin/slapd" name="/var/lib/heimdal-kdc/m-key" pid=1161656 
comm="slapd" requested_mask="r" denied_mask="r" fsuid=1000110 ouid=100

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/2004560/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2009738] Re: no lxc manpage

[Simon Déziel]

I've been told that snaps can't ship man pages unfortunately:

https://forum.snapcraft.io/t/support-for-man-pages/2299/24
https://bugs.launchpad.net/snapd/+bug/1575593

You can get something with `lxc manpage` which is basically the builtin
--help formatted for man. However, that's not easy/convenient to access
and looks weirder than the builtin --help stuff.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/2009738

Title:
  no lxc manpage

Status in lxc package in Ubuntu:
  New

Bug description:
  Hello, I don't have an lxc manpage on my focal system:

  $ man lxc
  No manual entry for lxc

  $ dpkg -l lxd | grep lxd ; snap info lxd | grep installed
  un  lxd  (no description available)
  installed:  5.11-ad0b61e (24483) 149MB -

  It looks a bit like none are packaged:

  $ find /snap/lxd -name '*.1.gz' -o -name '*.7.gz' -o -name '*.8.gz'
  $ 

  While I appreciate the online --help output, I also like having
  longer-form documentation available on a system without needing to use
  a web browser.

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: lxc (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-139.156-generic 5.4.224
  Uname: Linux 5.4.0-139-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Mar  8 18:21:08 2023
  SourcePackage: lxc
  UpgradeStatus: Upgraded to focal on 2020-01-24 (1138 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2009738/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2009808] Re: Doesn't display the correct livepatch service status

[Nathan Teodosio]

** Changed in: software-properties (Ubuntu)
 Assignee: (unassigned) => Nathan Teodosio (nteodosio)

** Changed in: software-properties (Ubuntu)
   Status: New => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/2009808

Title:
  Doesn't display the correct livepatch service status

Status in software-properties package in Ubuntu:
  Triaged
Status in ubuntu-advantage-tools package in Ubuntu:
  In Progress

Bug description:
  Starting a focal VM which didn't get updated the livepatch icon in the
  panel shows an orange warning and the popdown display a string saying
  it hit an error fetching the status

  $ canonical-livepatch status
  last check: 58 seconds ago
  kernel: 5.15.0-56.62~20.04.1-generic
  server check-in: failed: livepatch check failed: unauthorized
  patch state: ✗ kernel version not supported

  
  The software-properties tab doesn't give any clue about that though, maybe it 
should?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2009808/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1677668] Re: no GARPs during ephemeral boot

[Mauricio Faria de Oliveira]

** Tags added: se-00140843

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to isc-dhcp in Ubuntu.
https://bugs.launchpad.net/bugs/1677668

Title:
  no GARPs during ephemeral boot

Status in MAAS:
  Incomplete
Status in cloud-init package in Ubuntu:
  Incomplete
Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  Deploys time out with an error on the console that says,

  "Can not apply stage final, no datasource found! Likely bad things to
  come!"

  How to duplicate:
  MAAS Version 2.1.3+bzr5573-0ubuntu1 (16.04.1)
  1) Rack Controller and Region Controller in different VLANs
  2) Use Cisco ASA as the router with "ARP Inspection" enabled
  3) Clear the router ARP cache
  4) Deploy 2 maas machines with interfaces set to "Static assign"
  5) Observe deploys successfully
  6) Release both machines and swap IP's.
  7) Redeploy the same 2 machines
  8) Observe deploy failure with the machine consoles stuck in the "ubuntu 
login" screen with "Can not apply stage final, no datasource Found! Likely bad 
things to come!"
   
  The root cause is that during ephemeral PXE booting, no GARPs are sent, which 
in our environment will cause our router (Cisco ASA) to hold on to ARP table 
entries until it expires (default= 4 hours).  Then combined with ASA feature 
"ARP Inspection" will drop packets from a MaaS machine using the previously 
used IP from a different MaaS machine.

  The ephemeral boot image ephemeral-ubuntu-amd64-ga-16.04-xenial-daily.

  Running tcpdump on the Rack Controller, showed no GARPs from the
  deploying MaaS machine.  If there were GARPs sent, then the router
  would refresh its ARP cache thus avoiding the ARP Inspection dropping.

  [Excerpt from Cisco ASA]
  
http://www.cisco.com/c/en/us/td/docs/security/asa/asa94/config-guides/cli/general/asa-94-general-config/basic-arp-mac.pdf
  When you enable ARP inspection, the ASA compares the MAC address, IP address, 
and source interface in
  all ARP packets to static entries in the ARP table, and takes the following 
actions:
  • If the IP address, MAC address, and source interface match an ARP entry, 
the packet is passed through.
  • If there is a mismatch between the MAC address, the IP address, or the 
interface, then the ASA drops
  the packet.
  • If the ARP packet does not match any entries in the static ARP table, then 
you can set the ASA to either
  forward the packet out all interfaces (flood), or to drop the packet.

To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1677668/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2009859] ProcCpuinfoMinimal.txt

[Nick Rosbrook]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/2009859/+attachment/5653261/+files/ProcCpuinfoMinimal.txt

-- 
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/2009859

Title:
  systemd: networkd-test.py fails with newer kinetic kernels

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid
Status in linux source package in Kinetic:
  Confirmed
Status in systemd source package in Kinetic:
  New

Bug description:
  systemd autopkgtests are failing in kinetic, and they are not
  considered regressions. The failing test is one within networkd-
  test.py:

  ==
  ERROR: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest)
  resolved: domain-restricted DNS servers
  --
  Traceback (most recent call last):
File "/tmp/autopkgtest.wTrLDQ/build.Oa5/src/test/networkd-test.py", line 
680, in test_resolved_domain_restricted_dns
  out = subprocess.check_output(['resolvectl', 'query', 'math.lab'])
File "/usr/lib/python3.10/subprocess.py", line 420, in check_output
  return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
File "/usr/lib/python3.10/subprocess.py", line 524, in run
  raise CalledProcessError(retcode, process.args,
  subprocess.CalledProcessError: Command '['resolvectl', 'query', 'math.lab']' 
returned non-zero exit status 1.

  --
  Ran 35 tests in 161.770s

  FAILED (errors=1, skipped=2)

  The failures started without any changes to the systemd package, i.e.
  it was caused by another package upload. In particular, the failures
  started around 2022-11-17 with linux 5.19.0-24.25. The tests pass fine
  with linux 5.19.0-21.21, i.e. the version in kinetic-release.

  This can be demonstrated locally with autopkgtest:

  $ autopkgtest --shell-fail systemd --test-name networkd-test.py --pin-
  packages=kinetic=src:linux --setup-commands 'apt update' -- qemu
  /home/nr/ubuntu/autopkgtest-testbeds/autopkgtest-kinetic-amd64.img

  Note in the above command I did not pass -U, so no packages in the
  test bed are upgraded. But, with:

  $ autopkgtest --shell-fail systemd --test-name networkd-test.py -U --
  qemu /home/nr/ubuntu/autopkgtest-testbeds/autopkgtest-kinetic-
  amd64.img

  the kernel is upgraded, and the test fails.

  This can also be done manually by grabbing the systemd source on a
  kinetic machine (e.g. pull-lp-source systemd kinetic), and running:

  $ sudo python3 test/networkd-test.py
  DnsmasqClientTest.test_resolved_domain_restricted_dns

  The attached journal.txt shows systemd-resolved logs from when the test is 
run. The failure is caused by the EHOSTUNREACH when trying to resolve math.lab.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  9 11:56 seq
   crw-rw 1 root audio 116, 33 Mar  9 11:56 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.10
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 bochs-drmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic 
root=UUID=7f0aa1bf-59bd-4d77-b092-7244f86e5566 ro console=tty0 console=hvc0 
console=ttyS0
  ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-35-generic N/A
   linux-backports-modules-5.19.0-35-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1.4
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  kinetic
  Uname: Linux 5.19.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 0.0
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.16.0-debian-1.16.0-4
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-kinetic
  dmi.modalias: 

[Touch-packages] [Bug 2009859] acpidump.txt

[Nick Rosbrook]

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/2009859/+attachment/5653266/+files/acpidump.txt

** Changed in: linux (Ubuntu Kinetic)
   Status: Incomplete => Confirmed

** Changed in: linux (Ubuntu)
   Status: Incomplete => Confirmed

-- 
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/2009859

Title:
  systemd: networkd-test.py fails with newer kinetic kernels

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid
Status in linux source package in Kinetic:
  Confirmed
Status in systemd source package in Kinetic:
  New

Bug description:
  systemd autopkgtests are failing in kinetic, and they are not
  considered regressions. The failing test is one within networkd-
  test.py:

  ==
  ERROR: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest)
  resolved: domain-restricted DNS servers
  --
  Traceback (most recent call last):
File "/tmp/autopkgtest.wTrLDQ/build.Oa5/src/test/networkd-test.py", line 
680, in test_resolved_domain_restricted_dns
  out = subprocess.check_output(['resolvectl', 'query', 'math.lab'])
File "/usr/lib/python3.10/subprocess.py", line 420, in check_output
  return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
File "/usr/lib/python3.10/subprocess.py", line 524, in run
  raise CalledProcessError(retcode, process.args,
  subprocess.CalledProcessError: Command '['resolvectl', 'query', 'math.lab']' 
returned non-zero exit status 1.

  --
  Ran 35 tests in 161.770s

  FAILED (errors=1, skipped=2)

  The failures started without any changes to the systemd package, i.e.
  it was caused by another package upload. In particular, the failures
  started around 2022-11-17 with linux 5.19.0-24.25. The tests pass fine
  with linux 5.19.0-21.21, i.e. the version in kinetic-release.

  This can be demonstrated locally with autopkgtest:

  $ autopkgtest --shell-fail systemd --test-name networkd-test.py --pin-
  packages=kinetic=src:linux --setup-commands 'apt update' -- qemu
  /home/nr/ubuntu/autopkgtest-testbeds/autopkgtest-kinetic-amd64.img

  Note in the above command I did not pass -U, so no packages in the
  test bed are upgraded. But, with:

  $ autopkgtest --shell-fail systemd --test-name networkd-test.py -U --
  qemu /home/nr/ubuntu/autopkgtest-testbeds/autopkgtest-kinetic-
  amd64.img

  the kernel is upgraded, and the test fails.

  This can also be done manually by grabbing the systemd source on a
  kinetic machine (e.g. pull-lp-source systemd kinetic), and running:

  $ sudo python3 test/networkd-test.py
  DnsmasqClientTest.test_resolved_domain_restricted_dns

  The attached journal.txt shows systemd-resolved logs from when the test is 
run. The failure is caused by the EHOSTUNREACH when trying to resolve math.lab.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  9 11:56 seq
   crw-rw 1 root audio 116, 33 Mar  9 11:56 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.10
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 bochs-drmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic 
root=UUID=7f0aa1bf-59bd-4d77-b092-7244f86e5566 ro console=tty0 console=hvc0 
console=ttyS0
  ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-35-generic N/A
   linux-backports-modules-5.19.0-35-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1.4
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  kinetic
  Uname: Linux 5.19.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 0.0
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.16.0-debian-1.16.0-4
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-kinetic
  

[Touch-packages] [Bug 2009859] UdevDb.txt

[Nick Rosbrook]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/2009859/+attachment/5653264/+files/UdevDb.txt

-- 
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/2009859

Title:
  systemd: networkd-test.py fails with newer kinetic kernels

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid
Status in linux source package in Kinetic:
  Confirmed
Status in systemd source package in Kinetic:
  New

Bug description:
  systemd autopkgtests are failing in kinetic, and they are not
  considered regressions. The failing test is one within networkd-
  test.py:

  ==
  ERROR: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest)
  resolved: domain-restricted DNS servers
  --
  Traceback (most recent call last):
File "/tmp/autopkgtest.wTrLDQ/build.Oa5/src/test/networkd-test.py", line 
680, in test_resolved_domain_restricted_dns
  out = subprocess.check_output(['resolvectl', 'query', 'math.lab'])
File "/usr/lib/python3.10/subprocess.py", line 420, in check_output
  return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
File "/usr/lib/python3.10/subprocess.py", line 524, in run
  raise CalledProcessError(retcode, process.args,
  subprocess.CalledProcessError: Command '['resolvectl', 'query', 'math.lab']' 
returned non-zero exit status 1.

  --
  Ran 35 tests in 161.770s

  FAILED (errors=1, skipped=2)

  The failures started without any changes to the systemd package, i.e.
  it was caused by another package upload. In particular, the failures
  started around 2022-11-17 with linux 5.19.0-24.25. The tests pass fine
  with linux 5.19.0-21.21, i.e. the version in kinetic-release.

  This can be demonstrated locally with autopkgtest:

  $ autopkgtest --shell-fail systemd --test-name networkd-test.py --pin-
  packages=kinetic=src:linux --setup-commands 'apt update' -- qemu
  /home/nr/ubuntu/autopkgtest-testbeds/autopkgtest-kinetic-amd64.img

  Note in the above command I did not pass -U, so no packages in the
  test bed are upgraded. But, with:

  $ autopkgtest --shell-fail systemd --test-name networkd-test.py -U --
  qemu /home/nr/ubuntu/autopkgtest-testbeds/autopkgtest-kinetic-
  amd64.img

  the kernel is upgraded, and the test fails.

  This can also be done manually by grabbing the systemd source on a
  kinetic machine (e.g. pull-lp-source systemd kinetic), and running:

  $ sudo python3 test/networkd-test.py
  DnsmasqClientTest.test_resolved_domain_restricted_dns

  The attached journal.txt shows systemd-resolved logs from when the test is 
run. The failure is caused by the EHOSTUNREACH when trying to resolve math.lab.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  9 11:56 seq
   crw-rw 1 root audio 116, 33 Mar  9 11:56 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.10
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 bochs-drmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic 
root=UUID=7f0aa1bf-59bd-4d77-b092-7244f86e5566 ro console=tty0 console=hvc0 
console=ttyS0
  ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-35-generic N/A
   linux-backports-modules-5.19.0-35-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1.4
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  kinetic
  Uname: Linux 5.19.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 0.0
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.16.0-debian-1.16.0-4
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-kinetic
  dmi.modalias: 

[Touch-packages] [Bug 2009859] WifiSyslog.txt

[Nick Rosbrook]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/2009859/+attachment/5653265/+files/WifiSyslog.txt

-- 
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/2009859

Title:
  systemd: networkd-test.py fails with newer kinetic kernels

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid
Status in linux source package in Kinetic:
  Confirmed
Status in systemd source package in Kinetic:
  New

Bug description:
  systemd autopkgtests are failing in kinetic, and they are not
  considered regressions. The failing test is one within networkd-
  test.py:

  ==
  ERROR: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest)
  resolved: domain-restricted DNS servers
  --
  Traceback (most recent call last):
File "/tmp/autopkgtest.wTrLDQ/build.Oa5/src/test/networkd-test.py", line 
680, in test_resolved_domain_restricted_dns
  out = subprocess.check_output(['resolvectl', 'query', 'math.lab'])
File "/usr/lib/python3.10/subprocess.py", line 420, in check_output
  return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
File "/usr/lib/python3.10/subprocess.py", line 524, in run
  raise CalledProcessError(retcode, process.args,
  subprocess.CalledProcessError: Command '['resolvectl', 'query', 'math.lab']' 
returned non-zero exit status 1.

  --
  Ran 35 tests in 161.770s

  FAILED (errors=1, skipped=2)

  The failures started without any changes to the systemd package, i.e.
  it was caused by another package upload. In particular, the failures
  started around 2022-11-17 with linux 5.19.0-24.25. The tests pass fine
  with linux 5.19.0-21.21, i.e. the version in kinetic-release.

  This can be demonstrated locally with autopkgtest:

  $ autopkgtest --shell-fail systemd --test-name networkd-test.py --pin-
  packages=kinetic=src:linux --setup-commands 'apt update' -- qemu
  /home/nr/ubuntu/autopkgtest-testbeds/autopkgtest-kinetic-amd64.img

  Note in the above command I did not pass -U, so no packages in the
  test bed are upgraded. But, with:

  $ autopkgtest --shell-fail systemd --test-name networkd-test.py -U --
  qemu /home/nr/ubuntu/autopkgtest-testbeds/autopkgtest-kinetic-
  amd64.img

  the kernel is upgraded, and the test fails.

  This can also be done manually by grabbing the systemd source on a
  kinetic machine (e.g. pull-lp-source systemd kinetic), and running:

  $ sudo python3 test/networkd-test.py
  DnsmasqClientTest.test_resolved_domain_restricted_dns

  The attached journal.txt shows systemd-resolved logs from when the test is 
run. The failure is caused by the EHOSTUNREACH when trying to resolve math.lab.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  9 11:56 seq
   crw-rw 1 root audio 116, 33 Mar  9 11:56 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.10
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 bochs-drmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic 
root=UUID=7f0aa1bf-59bd-4d77-b092-7244f86e5566 ro console=tty0 console=hvc0 
console=ttyS0
  ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-35-generic N/A
   linux-backports-modules-5.19.0-35-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1.4
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  kinetic
  Uname: Linux 5.19.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 0.0
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.16.0-debian-1.16.0-4
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-kinetic
  dmi.modalias: 

[Touch-packages] [Bug 2009859] ProcModules.txt

[Nick Rosbrook]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/2009859/+attachment/5653263/+files/ProcModules.txt

-- 
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/2009859

Title:
  systemd: networkd-test.py fails with newer kinetic kernels

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid
Status in linux source package in Kinetic:
  Confirmed
Status in systemd source package in Kinetic:
  New

Bug description:
  systemd autopkgtests are failing in kinetic, and they are not
  considered regressions. The failing test is one within networkd-
  test.py:

  ==
  ERROR: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest)
  resolved: domain-restricted DNS servers
  --
  Traceback (most recent call last):
File "/tmp/autopkgtest.wTrLDQ/build.Oa5/src/test/networkd-test.py", line 
680, in test_resolved_domain_restricted_dns
  out = subprocess.check_output(['resolvectl', 'query', 'math.lab'])
File "/usr/lib/python3.10/subprocess.py", line 420, in check_output
  return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
File "/usr/lib/python3.10/subprocess.py", line 524, in run
  raise CalledProcessError(retcode, process.args,
  subprocess.CalledProcessError: Command '['resolvectl', 'query', 'math.lab']' 
returned non-zero exit status 1.

  --
  Ran 35 tests in 161.770s

  FAILED (errors=1, skipped=2)

  The failures started without any changes to the systemd package, i.e.
  it was caused by another package upload. In particular, the failures
  started around 2022-11-17 with linux 5.19.0-24.25. The tests pass fine
  with linux 5.19.0-21.21, i.e. the version in kinetic-release.

  This can be demonstrated locally with autopkgtest:

  $ autopkgtest --shell-fail systemd --test-name networkd-test.py --pin-
  packages=kinetic=src:linux --setup-commands 'apt update' -- qemu
  /home/nr/ubuntu/autopkgtest-testbeds/autopkgtest-kinetic-amd64.img

  Note in the above command I did not pass -U, so no packages in the
  test bed are upgraded. But, with:

  $ autopkgtest --shell-fail systemd --test-name networkd-test.py -U --
  qemu /home/nr/ubuntu/autopkgtest-testbeds/autopkgtest-kinetic-
  amd64.img

  the kernel is upgraded, and the test fails.

  This can also be done manually by grabbing the systemd source on a
  kinetic machine (e.g. pull-lp-source systemd kinetic), and running:

  $ sudo python3 test/networkd-test.py
  DnsmasqClientTest.test_resolved_domain_restricted_dns

  The attached journal.txt shows systemd-resolved logs from when the test is 
run. The failure is caused by the EHOSTUNREACH when trying to resolve math.lab.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  9 11:56 seq
   crw-rw 1 root audio 116, 33 Mar  9 11:56 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.10
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 bochs-drmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic 
root=UUID=7f0aa1bf-59bd-4d77-b092-7244f86e5566 ro console=tty0 console=hvc0 
console=ttyS0
  ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-35-generic N/A
   linux-backports-modules-5.19.0-35-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1.4
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  kinetic
  Uname: Linux 5.19.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 0.0
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.16.0-debian-1.16.0-4
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-kinetic
  dmi.modalias: 

[Touch-packages] [Bug 2009859] ProcInterrupts.txt

[Nick Rosbrook]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/2009859/+attachment/5653262/+files/ProcInterrupts.txt

-- 
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/2009859

Title:
  systemd: networkd-test.py fails with newer kinetic kernels

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid
Status in linux source package in Kinetic:
  Confirmed
Status in systemd source package in Kinetic:
  New

Bug description:
  systemd autopkgtests are failing in kinetic, and they are not
  considered regressions. The failing test is one within networkd-
  test.py:

  ==
  ERROR: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest)
  resolved: domain-restricted DNS servers
  --
  Traceback (most recent call last):
File "/tmp/autopkgtest.wTrLDQ/build.Oa5/src/test/networkd-test.py", line 
680, in test_resolved_domain_restricted_dns
  out = subprocess.check_output(['resolvectl', 'query', 'math.lab'])
File "/usr/lib/python3.10/subprocess.py", line 420, in check_output
  return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
File "/usr/lib/python3.10/subprocess.py", line 524, in run
  raise CalledProcessError(retcode, process.args,
  subprocess.CalledProcessError: Command '['resolvectl', 'query', 'math.lab']' 
returned non-zero exit status 1.

  --
  Ran 35 tests in 161.770s

  FAILED (errors=1, skipped=2)

  The failures started without any changes to the systemd package, i.e.
  it was caused by another package upload. In particular, the failures
  started around 2022-11-17 with linux 5.19.0-24.25. The tests pass fine
  with linux 5.19.0-21.21, i.e. the version in kinetic-release.

  This can be demonstrated locally with autopkgtest:

  $ autopkgtest --shell-fail systemd --test-name networkd-test.py --pin-
  packages=kinetic=src:linux --setup-commands 'apt update' -- qemu
  /home/nr/ubuntu/autopkgtest-testbeds/autopkgtest-kinetic-amd64.img

  Note in the above command I did not pass -U, so no packages in the
  test bed are upgraded. But, with:

  $ autopkgtest --shell-fail systemd --test-name networkd-test.py -U --
  qemu /home/nr/ubuntu/autopkgtest-testbeds/autopkgtest-kinetic-
  amd64.img

  the kernel is upgraded, and the test fails.

  This can also be done manually by grabbing the systemd source on a
  kinetic machine (e.g. pull-lp-source systemd kinetic), and running:

  $ sudo python3 test/networkd-test.py
  DnsmasqClientTest.test_resolved_domain_restricted_dns

  The attached journal.txt shows systemd-resolved logs from when the test is 
run. The failure is caused by the EHOSTUNREACH when trying to resolve math.lab.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  9 11:56 seq
   crw-rw 1 root audio 116, 33 Mar  9 11:56 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.10
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 bochs-drmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic 
root=UUID=7f0aa1bf-59bd-4d77-b092-7244f86e5566 ro console=tty0 console=hvc0 
console=ttyS0
  ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-35-generic N/A
   linux-backports-modules-5.19.0-35-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1.4
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  kinetic
  Uname: Linux 5.19.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 0.0
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.16.0-debian-1.16.0-4
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-kinetic
  dmi.modalias: 

[Touch-packages] [Bug 2009859] ProcCpuinfo.txt

[Nick Rosbrook]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/2009859/+attachment/5653260/+files/ProcCpuinfo.txt

-- 
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/2009859

Title:
  systemd: networkd-test.py fails with newer kinetic kernels

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid
Status in linux source package in Kinetic:
  Confirmed
Status in systemd source package in Kinetic:
  New

Bug description:
  systemd autopkgtests are failing in kinetic, and they are not
  considered regressions. The failing test is one within networkd-
  test.py:

  ==
  ERROR: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest)
  resolved: domain-restricted DNS servers
  --
  Traceback (most recent call last):
File "/tmp/autopkgtest.wTrLDQ/build.Oa5/src/test/networkd-test.py", line 
680, in test_resolved_domain_restricted_dns
  out = subprocess.check_output(['resolvectl', 'query', 'math.lab'])
File "/usr/lib/python3.10/subprocess.py", line 420, in check_output
  return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
File "/usr/lib/python3.10/subprocess.py", line 524, in run
  raise CalledProcessError(retcode, process.args,
  subprocess.CalledProcessError: Command '['resolvectl', 'query', 'math.lab']' 
returned non-zero exit status 1.

  --
  Ran 35 tests in 161.770s

  FAILED (errors=1, skipped=2)

  The failures started without any changes to the systemd package, i.e.
  it was caused by another package upload. In particular, the failures
  started around 2022-11-17 with linux 5.19.0-24.25. The tests pass fine
  with linux 5.19.0-21.21, i.e. the version in kinetic-release.

  This can be demonstrated locally with autopkgtest:

  $ autopkgtest --shell-fail systemd --test-name networkd-test.py --pin-
  packages=kinetic=src:linux --setup-commands 'apt update' -- qemu
  /home/nr/ubuntu/autopkgtest-testbeds/autopkgtest-kinetic-amd64.img

  Note in the above command I did not pass -U, so no packages in the
  test bed are upgraded. But, with:

  $ autopkgtest --shell-fail systemd --test-name networkd-test.py -U --
  qemu /home/nr/ubuntu/autopkgtest-testbeds/autopkgtest-kinetic-
  amd64.img

  the kernel is upgraded, and the test fails.

  This can also be done manually by grabbing the systemd source on a
  kinetic machine (e.g. pull-lp-source systemd kinetic), and running:

  $ sudo python3 test/networkd-test.py
  DnsmasqClientTest.test_resolved_domain_restricted_dns

  The attached journal.txt shows systemd-resolved logs from when the test is 
run. The failure is caused by the EHOSTUNREACH when trying to resolve math.lab.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  9 11:56 seq
   crw-rw 1 root audio 116, 33 Mar  9 11:56 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.10
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 bochs-drmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic 
root=UUID=7f0aa1bf-59bd-4d77-b092-7244f86e5566 ro console=tty0 console=hvc0 
console=ttyS0
  ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-35-generic N/A
   linux-backports-modules-5.19.0-35-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1.4
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  kinetic
  Uname: Linux 5.19.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 0.0
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.16.0-debian-1.16.0-4
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-kinetic
  dmi.modalias: 

[Touch-packages] [Bug 2009859] Lspci-vt.txt

[Nick Rosbrook]

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/2009859/+attachment/5653259/+files/Lspci-vt.txt

-- 
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/2009859

Title:
  systemd: networkd-test.py fails with newer kinetic kernels

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid
Status in linux source package in Kinetic:
  Confirmed
Status in systemd source package in Kinetic:
  New

Bug description:
  systemd autopkgtests are failing in kinetic, and they are not
  considered regressions. The failing test is one within networkd-
  test.py:

  ==
  ERROR: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest)
  resolved: domain-restricted DNS servers
  --
  Traceback (most recent call last):
File "/tmp/autopkgtest.wTrLDQ/build.Oa5/src/test/networkd-test.py", line 
680, in test_resolved_domain_restricted_dns
  out = subprocess.check_output(['resolvectl', 'query', 'math.lab'])
File "/usr/lib/python3.10/subprocess.py", line 420, in check_output
  return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
File "/usr/lib/python3.10/subprocess.py", line 524, in run
  raise CalledProcessError(retcode, process.args,
  subprocess.CalledProcessError: Command '['resolvectl', 'query', 'math.lab']' 
returned non-zero exit status 1.

  --
  Ran 35 tests in 161.770s

  FAILED (errors=1, skipped=2)

  The failures started without any changes to the systemd package, i.e.
  it was caused by another package upload. In particular, the failures
  started around 2022-11-17 with linux 5.19.0-24.25. The tests pass fine
  with linux 5.19.0-21.21, i.e. the version in kinetic-release.

  This can be demonstrated locally with autopkgtest:

  $ autopkgtest --shell-fail systemd --test-name networkd-test.py --pin-
  packages=kinetic=src:linux --setup-commands 'apt update' -- qemu
  /home/nr/ubuntu/autopkgtest-testbeds/autopkgtest-kinetic-amd64.img

  Note in the above command I did not pass -U, so no packages in the
  test bed are upgraded. But, with:

  $ autopkgtest --shell-fail systemd --test-name networkd-test.py -U --
  qemu /home/nr/ubuntu/autopkgtest-testbeds/autopkgtest-kinetic-
  amd64.img

  the kernel is upgraded, and the test fails.

  This can also be done manually by grabbing the systemd source on a
  kinetic machine (e.g. pull-lp-source systemd kinetic), and running:

  $ sudo python3 test/networkd-test.py
  DnsmasqClientTest.test_resolved_domain_restricted_dns

  The attached journal.txt shows systemd-resolved logs from when the test is 
run. The failure is caused by the EHOSTUNREACH when trying to resolve math.lab.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  9 11:56 seq
   crw-rw 1 root audio 116, 33 Mar  9 11:56 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.10
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 bochs-drmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic 
root=UUID=7f0aa1bf-59bd-4d77-b092-7244f86e5566 ro console=tty0 console=hvc0 
console=ttyS0
  ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-35-generic N/A
   linux-backports-modules-5.19.0-35-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1.4
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  kinetic
  Uname: Linux 5.19.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 0.0
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.16.0-debian-1.16.0-4
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-kinetic
  dmi.modalias: 

[Touch-packages] [Bug 2009859] Lspci.txt

[Nick Rosbrook]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/2009859/+attachment/5653258/+files/Lspci.txt

-- 
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/2009859

Title:
  systemd: networkd-test.py fails with newer kinetic kernels

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid
Status in linux source package in Kinetic:
  Confirmed
Status in systemd source package in Kinetic:
  New

Bug description:
  systemd autopkgtests are failing in kinetic, and they are not
  considered regressions. The failing test is one within networkd-
  test.py:

  ==
  ERROR: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest)
  resolved: domain-restricted DNS servers
  --
  Traceback (most recent call last):
File "/tmp/autopkgtest.wTrLDQ/build.Oa5/src/test/networkd-test.py", line 
680, in test_resolved_domain_restricted_dns
  out = subprocess.check_output(['resolvectl', 'query', 'math.lab'])
File "/usr/lib/python3.10/subprocess.py", line 420, in check_output
  return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
File "/usr/lib/python3.10/subprocess.py", line 524, in run
  raise CalledProcessError(retcode, process.args,
  subprocess.CalledProcessError: Command '['resolvectl', 'query', 'math.lab']' 
returned non-zero exit status 1.

  --
  Ran 35 tests in 161.770s

  FAILED (errors=1, skipped=2)

  The failures started without any changes to the systemd package, i.e.
  it was caused by another package upload. In particular, the failures
  started around 2022-11-17 with linux 5.19.0-24.25. The tests pass fine
  with linux 5.19.0-21.21, i.e. the version in kinetic-release.

  This can be demonstrated locally with autopkgtest:

  $ autopkgtest --shell-fail systemd --test-name networkd-test.py --pin-
  packages=kinetic=src:linux --setup-commands 'apt update' -- qemu
  /home/nr/ubuntu/autopkgtest-testbeds/autopkgtest-kinetic-amd64.img

  Note in the above command I did not pass -U, so no packages in the
  test bed are upgraded. But, with:

  $ autopkgtest --shell-fail systemd --test-name networkd-test.py -U --
  qemu /home/nr/ubuntu/autopkgtest-testbeds/autopkgtest-kinetic-
  amd64.img

  the kernel is upgraded, and the test fails.

  This can also be done manually by grabbing the systemd source on a
  kinetic machine (e.g. pull-lp-source systemd kinetic), and running:

  $ sudo python3 test/networkd-test.py
  DnsmasqClientTest.test_resolved_domain_restricted_dns

  The attached journal.txt shows systemd-resolved logs from when the test is 
run. The failure is caused by the EHOSTUNREACH when trying to resolve math.lab.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Mar  9 11:56 seq
   crw-rw 1 root audio 116, 33 Mar  9 11:56 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 22.10
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 bochs-drmdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic 
root=UUID=7f0aa1bf-59bd-4d77-b092-7244f86e5566 ro console=tty0 console=hvc0 
console=ttyS0
  ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-35-generic N/A
   linux-backports-modules-5.19.0-35-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1.4
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  kinetic
  Uname: Linux 5.19.0-35-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 04/01/2014
  dmi.bios.release: 0.0
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.16.0-debian-1.16.0-4
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-kinetic
  dmi.modalias: 

[Touch-packages] [Bug 2009859] Re: systemd: networkd-test.py fails with newer kinetic kernels

[Nick Rosbrook]

apport information

** Tags added: apport-collected kinetic

** Description changed:

  systemd autopkgtests are failing in kinetic, and they are not considered
  regressions. The failing test is one within networkd-test.py:
  
  ==
  ERROR: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest)
  resolved: domain-restricted DNS servers
  --
  Traceback (most recent call last):
File "/tmp/autopkgtest.wTrLDQ/build.Oa5/src/test/networkd-test.py", line 
680, in test_resolved_domain_restricted_dns
  out = subprocess.check_output(['resolvectl', 'query', 'math.lab'])
File "/usr/lib/python3.10/subprocess.py", line 420, in check_output
  return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
File "/usr/lib/python3.10/subprocess.py", line 524, in run
  raise CalledProcessError(retcode, process.args,
  subprocess.CalledProcessError: Command '['resolvectl', 'query', 'math.lab']' 
returned non-zero exit status 1.
  
  --
  Ran 35 tests in 161.770s
  
  FAILED (errors=1, skipped=2)
  
  The failures started without any changes to the systemd package, i.e. it
  was caused by another package upload. In particular, the failures
  started around 2022-11-17 with linux 5.19.0-24.25. The tests pass fine
  with linux 5.19.0-21.21, i.e. the version in kinetic-release.
  
  This can be demonstrated locally with autopkgtest:
  
  $ autopkgtest --shell-fail systemd --test-name networkd-test.py --pin-
  packages=kinetic=src:linux --setup-commands 'apt update' -- qemu
  /home/nr/ubuntu/autopkgtest-testbeds/autopkgtest-kinetic-amd64.img
  
  Note in the above command I did not pass -U, so no packages in the test
  bed are upgraded. But, with:
  
  $ autopkgtest --shell-fail systemd --test-name networkd-test.py -U --
  qemu /home/nr/ubuntu/autopkgtest-testbeds/autopkgtest-kinetic-amd64.img
  
  the kernel is upgraded, and the test fails.
  
  This can also be done manually by grabbing the systemd source on a
  kinetic machine (e.g. pull-lp-source systemd kinetic), and running:
  
  $ sudo python3 test/networkd-test.py
  DnsmasqClientTest.test_resolved_domain_restricted_dns
  
- The attached journal.txt shows systemd-resolved logs from when the test
- is run. The failure is caused by the EHOSTUNREACH when trying to resolve
- math.lab.
+ The attached journal.txt shows systemd-resolved logs from when the test is 
run. The failure is caused by the EHOSTUNREACH when trying to resolve math.lab.
+ --- 
+ ProblemType: Bug
+ AlsaDevices:
+  total 0
+  crw-rw 1 root audio 116,  1 Mar  9 11:56 seq
+  crw-rw 1 root audio 116, 33 Mar  9 11:56 timer
+ AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
+ ApportVersion: 2.23.1-0ubuntu3
+ Architecture: amd64
+ ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
+ CRDA: N/A
+ CasperMD5CheckResult: unknown
+ DistroRelease: Ubuntu 22.10
+ IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
+ Lsusb: Error: command ['lsusb'] failed with exit code 1:
+ Lsusb-t:
+  
+ Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
+ MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
+ Package: linux (not installed)
+ PciMultimedia:
+  
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcFB: 0 bochs-drmdrmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-35-generic 
root=UUID=7f0aa1bf-59bd-4d77-b092-7244f86e5566 ro console=tty0 console=hvc0 
console=ttyS0
+ ProcVersionSignature: Ubuntu 5.19.0-35.36-generic 5.19.17
+ RelatedPackageVersions:
+  linux-restricted-modules-5.19.0-35-generic N/A
+  linux-backports-modules-5.19.0-35-generic  N/A
+  linux-firmware 20220923.gitf09bebf3-0ubuntu1.4
+ RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
+ Tags:  kinetic
+ Uname: Linux 5.19.0-35-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: N/A
+ _MarkForUpload: True
+ dmi.bios.date: 04/01/2014
+ dmi.bios.release: 0.0
+ dmi.bios.vendor: SeaBIOS
+ dmi.bios.version: 1.16.0-debian-1.16.0-4
+ dmi.chassis.type: 1
+ dmi.chassis.vendor: QEMU
+ dmi.chassis.version: pc-i440fx-kinetic
+ dmi.modalias: 
dmi:bvnSeaBIOS:bvr1.16.0-debian-1.16.0-4:bd04/01/2014:br0.0:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-kinetic:cvnQEMU:ct1:cvrpc-i440fx-kinetic:sku:
+ dmi.product.name: Standard PC (i440FX + PIIX, 1996)
+ dmi.product.version: pc-i440fx-kinetic
+ dmi.sys.vendor: QEMU

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/2009859/+attachment/5653257/+files/CurrentDmesg.txt

-- 
You received this bug notification because you are a member of Ubuntu
Touch 

[Touch-packages] [Bug 2009808] Re: Doesn't display the correct livepatch service status

[Sebastien Bacher]

Nathan, could you check that have the status as 'warning' isn't going to
confuse the current version of software-properties, we need to ensure
things aren't going to stop working correctly when the new u-a-t lands.

We will need a design for how to display the message in the GUI and then
add the feature to the desktop client to parse the new status and
display the reason

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/2009808

Title:
  Doesn't display the correct livepatch service status

Status in software-properties package in Ubuntu:
  New
Status in ubuntu-advantage-tools package in Ubuntu:
  In Progress

Bug description:
  Starting a focal VM which didn't get updated the livepatch icon in the
  panel shows an orange warning and the popdown display a string saying
  it hit an error fetching the status

  $ canonical-livepatch status
  last check: 58 seconds ago
  kernel: 5.15.0-56.62~20.04.1-generic
  server check-in: failed: livepatch check failed: unauthorized
  patch state: ✗ kernel version not supported

  
  The software-properties tab doesn't give any clue about that though, maybe it 
should?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2009808/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2008952] Re: DNS failure while trying to fetch user-data

[Lukas Märdian]

01-network-manager-all.yaml seems to be shipped by livecd-rootfs

** Changed in: netplan
 Assignee: (unassigned) => Danilo Egea Gondolfo (danilogondolfo)

** Tags removed: rls-ll-incoming
** Tags added: foundations-todo

-- 
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/2008952

Title:
  DNS failure while trying to fetch user-data

Status in cloud-init:
  Triaged
Status in netplan:
  New
Status in subiquity:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  In testing netboot + autoinstall of the new ubuntu desktop subiquity
  based installer for 23.04 I found cloud-init is failing to retrieve
  user-data because it can't resolved the hostname in the URL.  This
  same configuration does work for 22.04 based subiquity, so seems a
  regression.

  From the ipxe config:

  imgargs vmlinuz initrd=initrd \
   ip=dhcp \
   iso-url=http://cdimage.ubuntu.com/daily-live/pending/lunar-desktop-amd64.iso 
\
   fsck.mode=skip \
   layerfs-path=minimal.standard.live.squashfs \
   autoinstall \
   'ds=nocloud-net;s=http://boot.linuxgroove.com/ubuntu/23.04/' \

  That fails, but if we replace boot.linuxgroove.com with the IP it
  works.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/2008952/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1826294] Re: os-prober exits prematurely with "logger: socket /dev/log: Protocol wrong type for socket"

[Andreas Hasenack]

I'm not really looking into syslog-ng. The apparmor profile change I did
was to rsyslog, and that's where I tried to reproduce this issue.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1826294

Title:
  os-prober exits prematurely with "logger: socket /dev/log: Protocol
  wrong type for socket"

Status in AppArmor Profiles:
  New
Status in os-prober package in Ubuntu:
  Fix Released
Status in rsyslog package in Ubuntu:
  New

Bug description:
  Failure occurs on Ubuntu 16.04 with the apparmor-
  profiles-2.10.95-0ubuntu2.10 package installed.

  Running update-grub will run /usr/bin/os-prober, which spews about a
  dozen of the following line to stderr:

  logger: socket /dev/log: Protocol wrong type for socket

  … but fails to report the existence of some installed operating
  systems as expected.

  Furthermore, /var/log/messages contains:

  kernel: audit: type=1400 audit(1556043066.679:11460):
  apparmor="ALLOWED" operation="sendmsg" info="Failed name lookup -
  disconnected path" error=-13 profile="syslog-ng" name="dev/log"
  pid=28566 comm="logger" requested_mask="r" denied_mask="r" fsuid=0
  ouid=0

  
  Here is a stripped-down skeleton of the /usr/bin/os-prober script, which 
demonstrates the problem:

  #!/bin/sh
  set -e -x
  
  newns () {
[ "$OS_PROBER_NEWNS" ] || exec /usr/lib/os-prober/newns "$0" "$@"
  }
  
  log() {
logger -t "$(basename "$0")" "$@"
  }
  
  debug() {
log "debug: $@"
  }
  
  ls -l /dev/log
  debug "Hello world"
  newns "$@"

  The expected behavior is that it should write "debug: os-prober-
  testcase Hello world" to /var/log/messages twice.  However, it only
  succeeds in writing "Hello world" once.  After the script respawns
  itself with /usr/lib/os-prober/newns (which is like `unshare -m`), the
  second attempt to write to /dev/log fails as described above.

  Since the os-prober Bash script runs with the -e flag, any error, even
  just a logging error, causes the script to terminate prematurely.
  (Arguably, the log() function should call `logger -t "$(basename
  "$0")" "$@" || :` so that logging failures aren't fatal.)

  
  The fix, for me, is to edit /etc/apparmor.d/sbin.syslog-ng, and change

  profile syslog-ng /{usr/,}sbin/syslog-ng flags=(complain) {\
…
  }

  to

  profile syslog-ng /{usr/,}sbin/syslog-ng 
flags=(complain,attach_disconnected) {
…
  }

  … then run `aa-complain sbin.syslog-ng` and `service syslog-ng
  restart`, before running update-grub again.  I assume that similar
  fixes would be required for the other logging daemons.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor-profiles/+bug/1826294/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1826294] Re: os-prober exits prematurely with "logger: socket /dev/log: Protocol wrong type for socket"

[Dimitri John Ledkov]

> The syslog-ng profile needs flags=(attach_disconnected) added to it

I failed to reproduce this with syslog-ng, but i guess i didn't
configure syslog-ng correctly to attempt attaching to /dev/log

I am also not sure of os-prober usage of logger is correct, and if it
actually wants to use that all, or if it should simply use journald
only, or nothing at all.

Reading attach_disconnected sounds scary, i'm not sure what os-prober
can do better here. bind-mount /dev/log socket into it's new mount
namespace?

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1826294

Title:
  os-prober exits prematurely with "logger: socket /dev/log: Protocol
  wrong type for socket"

Status in AppArmor Profiles:
  New
Status in os-prober package in Ubuntu:
  Fix Released
Status in rsyslog package in Ubuntu:
  New

Bug description:
  Failure occurs on Ubuntu 16.04 with the apparmor-
  profiles-2.10.95-0ubuntu2.10 package installed.

  Running update-grub will run /usr/bin/os-prober, which spews about a
  dozen of the following line to stderr:

  logger: socket /dev/log: Protocol wrong type for socket

  … but fails to report the existence of some installed operating
  systems as expected.

  Furthermore, /var/log/messages contains:

  kernel: audit: type=1400 audit(1556043066.679:11460):
  apparmor="ALLOWED" operation="sendmsg" info="Failed name lookup -
  disconnected path" error=-13 profile="syslog-ng" name="dev/log"
  pid=28566 comm="logger" requested_mask="r" denied_mask="r" fsuid=0
  ouid=0

  
  Here is a stripped-down skeleton of the /usr/bin/os-prober script, which 
demonstrates the problem:

  #!/bin/sh
  set -e -x
  
  newns () {
[ "$OS_PROBER_NEWNS" ] || exec /usr/lib/os-prober/newns "$0" "$@"
  }
  
  log() {
logger -t "$(basename "$0")" "$@"
  }
  
  debug() {
log "debug: $@"
  }
  
  ls -l /dev/log
  debug "Hello world"
  newns "$@"

  The expected behavior is that it should write "debug: os-prober-
  testcase Hello world" to /var/log/messages twice.  However, it only
  succeeds in writing "Hello world" once.  After the script respawns
  itself with /usr/lib/os-prober/newns (which is like `unshare -m`), the
  second attempt to write to /dev/log fails as described above.

  Since the os-prober Bash script runs with the -e flag, any error, even
  just a logging error, causes the script to terminate prematurely.
  (Arguably, the log() function should call `logger -t "$(basename
  "$0")" "$@" || :` so that logging failures aren't fatal.)

  
  The fix, for me, is to edit /etc/apparmor.d/sbin.syslog-ng, and change

  profile syslog-ng /{usr/,}sbin/syslog-ng flags=(complain) {\
…
  }

  to

  profile syslog-ng /{usr/,}sbin/syslog-ng 
flags=(complain,attach_disconnected) {
…
  }

  … then run `aa-complain sbin.syslog-ng` and `service syslog-ng
  restart`, before running update-grub again.  I assume that similar
  fixes would be required for the other logging daemons.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor-profiles/+bug/1826294/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2009859] Missing required logs.

[Ubuntu Kernel Bot]

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 2009859

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

** Changed in: linux (Ubuntu)
   Status: New => Incomplete

** Changed in: linux (Ubuntu Kinetic)
   Status: New => Incomplete

-- 
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/2009859

Title:
  systemd: networkd-test.py fails with newer kinetic kernels

Status in linux package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Invalid
Status in linux source package in Kinetic:
  Incomplete
Status in systemd source package in Kinetic:
  New

Bug description:
  systemd autopkgtests are failing in kinetic, and they are not
  considered regressions. The failing test is one within networkd-
  test.py:

  ==
  ERROR: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest)
  resolved: domain-restricted DNS servers
  --
  Traceback (most recent call last):
File "/tmp/autopkgtest.wTrLDQ/build.Oa5/src/test/networkd-test.py", line 
680, in test_resolved_domain_restricted_dns
  out = subprocess.check_output(['resolvectl', 'query', 'math.lab'])
File "/usr/lib/python3.10/subprocess.py", line 420, in check_output
  return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
File "/usr/lib/python3.10/subprocess.py", line 524, in run
  raise CalledProcessError(retcode, process.args,
  subprocess.CalledProcessError: Command '['resolvectl', 'query', 'math.lab']' 
returned non-zero exit status 1.

  --
  Ran 35 tests in 161.770s

  FAILED (errors=1, skipped=2)

  The failures started without any changes to the systemd package, i.e.
  it was caused by another package upload. In particular, the failures
  started around 2022-11-17 with linux 5.19.0-24.25. The tests pass fine
  with linux 5.19.0-21.21, i.e. the version in kinetic-release.

  This can be demonstrated locally with autopkgtest:

  $ autopkgtest --shell-fail systemd --test-name networkd-test.py --pin-
  packages=kinetic=src:linux --setup-commands 'apt update' -- qemu
  /home/nr/ubuntu/autopkgtest-testbeds/autopkgtest-kinetic-amd64.img

  Note in the above command I did not pass -U, so no packages in the
  test bed are upgraded. But, with:

  $ autopkgtest --shell-fail systemd --test-name networkd-test.py -U --
  qemu /home/nr/ubuntu/autopkgtest-testbeds/autopkgtest-kinetic-
  amd64.img

  the kernel is upgraded, and the test fails.

  This can also be done manually by grabbing the systemd source on a
  kinetic machine (e.g. pull-lp-source systemd kinetic), and running:

  $ sudo python3 test/networkd-test.py
  DnsmasqClientTest.test_resolved_domain_restricted_dns

  The attached journal.txt shows systemd-resolved logs from when the
  test is run. The failure is caused by the EHOSTUNREACH when trying to
  resolve math.lab.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2009859/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2009808] Re: Doesn't display the correct livepatch service status

[Grant Orndorff]

In the upcoming version of ubuntu-advantage-tools, this will be shown in pro 
status as
SERVICE  ENTITLED  STATUSDESCRIPTION
livepatchyes   warning   Current kernel is not supported

The pro status --format json section for livepatch will look like:
{
  "available": "yes",
  "blocked_by": [],
  "description": "Canonical Livepatch service",
  "description_override": "Current kernel is not supported",
  "entitled": "yes",
  "name": "livepatch",
  "status": "warning",
  "status_details": "",
  "warning": {
"code": "livepatch-kernel-not-supported",
"message": "The current kernel (5.15.0-1028-kvm, x86_64) is not 
supported by livepatch.\nSupported kernels are listed here: 
https://ubuntu.com/security/livepatch/docs/kernels\nEither switch to a 
supported kernel or `pro disable livepatch` to dismiss this warning."
  }
},

I think this will cover the ubuntu-advantage-tools part of the problem.
I'll mark it In Progress to reflect the status that this is implemented
but not yet committed or released to any Ubuntu release. We expect it to
be released in late March.


I think software-properties looks for "status" == "enabled" to show an "on" 
switch for livepatch, so after the above u-a-t status change, it will show 
livepatch as "off" (since "status" == "warning").

softare-properties should probably also display a warning message
describing the situation that `pro status` tells it. I'll leave this as
affecting ubuntu-advantage-tools, but also add it back to software-
properties to represent that portion of the work (propagating the
warning from pro status to the GUI).


** Changed in: ubuntu-advantage-tools (Ubuntu)
   Status: New => In Progress

** Changed in: ubuntu-advantage-tools (Ubuntu)
 Assignee: (unassigned) => Grant Orndorff (orndorffgrant)

** Also affects: software-properties (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/2009808

Title:
  Doesn't display the correct livepatch service status

Status in software-properties package in Ubuntu:
  New
Status in ubuntu-advantage-tools package in Ubuntu:
  In Progress

Bug description:
  Starting a focal VM which didn't get updated the livepatch icon in the
  panel shows an orange warning and the popdown display a string saying
  it hit an error fetching the status

  $ canonical-livepatch status
  last check: 58 seconds ago
  kernel: 5.15.0-56.62~20.04.1-generic
  server check-in: failed: livepatch check failed: unauthorized
  patch state: ✗ kernel version not supported

  
  The software-properties tab doesn't give any clue about that though, maybe it 
should?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2009808/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2009859] [NEW] systemd: networkd-test.py fails with newer kinetic kernels

[Nick Rosbrook]

Public bug reported:

systemd autopkgtests are failing in kinetic, and they are not considered
regressions. The failing test is one within networkd-test.py:

==
ERROR: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest)
resolved: domain-restricted DNS servers
--
Traceback (most recent call last):
  File "/tmp/autopkgtest.wTrLDQ/build.Oa5/src/test/networkd-test.py", line 680, 
in test_resolved_domain_restricted_dns
out = subprocess.check_output(['resolvectl', 'query', 'math.lab'])
  File "/usr/lib/python3.10/subprocess.py", line 420, in check_output
return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
  File "/usr/lib/python3.10/subprocess.py", line 524, in run
raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['resolvectl', 'query', 'math.lab']' 
returned non-zero exit status 1.

--
Ran 35 tests in 161.770s

FAILED (errors=1, skipped=2)

The failures started without any changes to the systemd package, i.e. it
was caused by another package upload. In particular, the failures
started around 2022-11-17 with linux 5.19.0-24.25. The tests pass fine
with linux 5.19.0-21.21, i.e. the version in kinetic-release.

This can be demonstrated locally with autopkgtest:

$ autopkgtest --shell-fail systemd --test-name networkd-test.py --pin-
packages=kinetic=src:linux --setup-commands 'apt update' -- qemu
/home/nr/ubuntu/autopkgtest-testbeds/autopkgtest-kinetic-amd64.img

Note in the above command I did not pass -U, so no packages in the test
bed are upgraded. But, with:

$ autopkgtest --shell-fail systemd --test-name networkd-test.py -U --
qemu /home/nr/ubuntu/autopkgtest-testbeds/autopkgtest-kinetic-amd64.img

the kernel is upgraded, and the test fails.

This can also be done manually by grabbing the systemd source on a
kinetic machine (e.g. pull-lp-source systemd kinetic), and running:

$ sudo python3 test/networkd-test.py
DnsmasqClientTest.test_resolved_domain_restricted_dns

The attached journal.txt shows systemd-resolved logs from when the test
is run. The failure is caused by the EHOSTUNREACH when trying to resolve
math.lab.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: linux (Ubuntu Kinetic)
 Importance: Undecided
 Status: New

** Affects: systemd (Ubuntu Kinetic)
 Importance: Undecided
 Status: New

** Attachment added: "journal.txt"
   
https://bugs.launchpad.net/bugs/2009859/+attachment/5653247/+files/journal.txt

** Also affects: systemd (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

** Changed in: systemd (Ubuntu)
   Status: New => Invalid

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Summary changed:

- systemd: test-networkd.py fails with newer kinetic kernels
+ systemd: networkd-test.py fails with newer kinetic kernels

-- 
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/2009859

Title:
  systemd: networkd-test.py fails with newer kinetic kernels

Status in linux package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Invalid
Status in linux source package in Kinetic:
  New
Status in systemd source package in Kinetic:
  New

Bug description:
  systemd autopkgtests are failing in kinetic, and they are not
  considered regressions. The failing test is one within networkd-
  test.py:

  ==
  ERROR: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest)
  resolved: domain-restricted DNS servers
  --
  Traceback (most recent call last):
File "/tmp/autopkgtest.wTrLDQ/build.Oa5/src/test/networkd-test.py", line 
680, in test_resolved_domain_restricted_dns
  out = subprocess.check_output(['resolvectl', 'query', 'math.lab'])
File "/usr/lib/python3.10/subprocess.py", line 420, in check_output
  return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
File "/usr/lib/python3.10/subprocess.py", line 524, in run
  raise CalledProcessError(retcode, process.args,
  subprocess.CalledProcessError: Command '['resolvectl', 'query', 'math.lab']' 
returned non-zero exit status 1.

  --
  Ran 35 tests in 161.770s

  FAILED (errors=1, skipped=2)

  The failures started without any changes to the systemd package, i.e.
  it was caused by another package upload. In particular, the failures
  started around 2022-11-17 with linux 5.19.0-24.25. The tests pass fine
  with linux 5.19.0-21.21, i.e. 

[Touch-packages] [Bug 2009756] Re: backups fail since latest rsync security update

[Marc Deslauriers]

** Information type changed from Public to Public Security

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/2009756

Title:
  backups fail since latest rsync security update

Status in backintime package in Ubuntu:
  Fix Released
Status in rsync package in Ubuntu:
  New
Status in backintime source package in Jammy:
  In Progress
Status in rsync source package in Jammy:
  New
Status in backintime source package in Kinetic:
  In Progress
Status in rsync source package in Kinetic:
  New
Status in backintime source package in Lunar:
  Fix Released
Status in rsync source package in Lunar:
  New

Bug description:
  Backintime uses rsync to perform updates. Unfortunately there is an
  incompatibility between the currently released version of backintime
  and rsync >= 3.2.4 (see https://github.com/bit-
  team/backintime/issues/1247)

  Rsync has been updated from 3.2.3 to 3.2.7 on Feb 27. This broke
  backintime backups. The symptom is an error message like this:

  Command "rsync -a --delete --rsh=ssh -o ServerAliveInterval=240 -o
  LogLevel=Error -o IdentityFile=/home/aurelien/.ssh/backintime -p 22
  /tmp/tmpxilwcwk4/
  u...@example.com:"./backintime/switch/aurelien/1/20230308-230517-262""
  returns 3 | rsync: change_dir#3
  "/data/home/user//"./backintime/switch/aurelien/1" failed: No such
  file or directory (2)

  The workaround described in the GitHub issue works (passing `--old-
  args` to rsync), but maybe it would be better if the backintime
  package did this automatically?

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: backintime-common 1.2.1-3ubuntu0.1
  ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Mar  8 23:19:02 2023
  InstallationDate: Installed on 2021-06-23 (623 days ago)
  InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: backintime
  UpgradeStatus: Upgraded to jammy on 2022-08-24 (196 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/backintime/+bug/2009756/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2009756] Re: backups fail since latest rsync security update

[buhtz]

Dear Marc,
thanks for explaining and your patience.

I think I'm a bit blinded here because of my "Debian stable" experience.
I also mixed up the terms "stable" and "LTS" which seems not to be the
same.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/2009756

Title:
  backups fail since latest rsync security update

Status in backintime package in Ubuntu:
  Fix Released
Status in rsync package in Ubuntu:
  New
Status in backintime source package in Jammy:
  In Progress
Status in rsync source package in Jammy:
  New
Status in backintime source package in Kinetic:
  In Progress
Status in rsync source package in Kinetic:
  New
Status in backintime source package in Lunar:
  Fix Released
Status in rsync source package in Lunar:
  New

Bug description:
  Backintime uses rsync to perform updates. Unfortunately there is an
  incompatibility between the currently released version of backintime
  and rsync >= 3.2.4 (see https://github.com/bit-
  team/backintime/issues/1247)

  Rsync has been updated from 3.2.3 to 3.2.7 on Feb 27. This broke
  backintime backups. The symptom is an error message like this:

  Command "rsync -a --delete --rsh=ssh -o ServerAliveInterval=240 -o
  LogLevel=Error -o IdentityFile=/home/aurelien/.ssh/backintime -p 22
  /tmp/tmpxilwcwk4/
  u...@example.com:"./backintime/switch/aurelien/1/20230308-230517-262""
  returns 3 | rsync: change_dir#3
  "/data/home/user//"./backintime/switch/aurelien/1" failed: No such
  file or directory (2)

  The workaround described in the GitHub issue works (passing `--old-
  args` to rsync), but maybe it would be better if the backintime
  package did this automatically?

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: backintime-common 1.2.1-3ubuntu0.1
  ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Mar  8 23:19:02 2023
  InstallationDate: Installed on 2021-06-23 (623 days ago)
  InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: backintime
  UpgradeStatus: Upgraded to jammy on 2022-08-24 (196 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/backintime/+bug/2009756/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2009706] Re: rsync 3.1.2-2.1ubuntu1.6 breaks compatibility with unison 2.48.4-1ubuntu1 on Bionic

[Marc Deslauriers]

Looks like the rsync security update doesn't like the way unison is
handling arguments. Perhaps adding --old-args to the command lines here
would help:

copyprog = rsync -a -A -X --rsh=ssh --inplace --compress
copyprogrest = rsync -a -A -X --rsh=ssh --partial --inplace --compress

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/2009706

Title:
  rsync 3.1.2-2.1ubuntu1.6 breaks compatibility with unison
  2.48.4-1ubuntu1 on Bionic

Status in rsync package in Ubuntu:
  New
Status in unison package in Ubuntu:
  New

Bug description:
  Rsync 3.1.2-2.1ubuntu1.6, when used by Unison using the copyprog
  option in Unison, produces an error message and fails to sync files.
  Rsync 3.1.2-2.1ubuntu1 succeeds in syncing files. I believe Rsync
  3.1.2-2.1ubuntu1.5 succeeded but I no longer have the .deb file to
  test with.

  Steps to reproduce:

  Create a unison profile similar to the one given below, to sync a
  folder between a local machine and a remote ssh server. Both client
  and server need the same Ubuntu and Unison versions, and I used
  unpassphrased SSH keys for authentication. Place a test file in the
  folder to be synced, then run 'unison profilename'.

  Note that I have redacted domains in the below.

  Unison profile:

  label = Test Profile
  root = /root/unison-test
  root = ssh://fs2b.our.domain.org.uk//root/unison-test

  # run repeatedly and fully automatically
  auto = true
  batch = true
  copyonconflict = true
  #repeat = 60

  # the copy program must be manually specified in order to sync ACLs
  copythreshold=0
  copyprog = rsync -a -A -X --rsh=ssh --inplace --compress
  copyprogrest = rsync -a -A -X --rsh=ssh --partial --inplace --compress

  # general settings
  group = true
  owner = true
  #path = sharedfolder
  #path = users
  perms = -1
  sortbysize = true
  times = true

  Unison output with rsync 3.1.2-2.1ubuntu1.6
  root@fs72a:~# unison fs2b_unisontest -debug all
  [startup] Preferences:
  ui = graphic
  host =
  server = false
  prefsdocs = false
  doc =
  version = false
  silent = false
  dumbtty = false
  testserver = false
  rest = fs2b_unisontest
  showprev = false
  selftest = false
  confirmmerge = false
  retry = 0
  repeat =
  contactquietly = false
  key =
  label = Syncs P and S drives between fs72a and fs2a
  expert = false
  height = 15
  auto = true
  maxthreads = 0
  maxsizethreshold = -1
  prefer =
  force =
  sortnewfirst = false
  sortbysize = true
  keeptempfilesaftermerge = false
  diff = diff -u CURRENT2 CURRENT1
  copyonconflict = true
  backupdir =
  maxbackups = 2
  backups = false
  backupsuffix =
  backupprefix = .bak.$VERSION.
  backuploc = central
  copymax = 1
  copyquoterem = default
  copythreshold = 0
  copyprogrest = rsync -a -A -X --rsh=ssh --partial --inplace --compress
  copyprog = rsync -a -A -X --rsh=ssh --inplace --compress
  rsync = true
  fastcheck = default
  ignorelocks = false
  dumparchives = false
  showarchive = false
  rootsName =
  ignorearchives = false
  fastercheckUNSAFE = false
  fat = false
  allHostsAreRunningWindows = false
  someHostIsRunningWindows = false
  confirmbigdel = true
  batch = true
  root = ssh://fs2b.our.domain.org.uk//root/unison-test
  root = /root/unison-test
  killserver = false
  halfduplex = false
  stream = true
  addversionno = false
  servercmd =
  sshargs =
  rshargs =
  rshcmd = rsh
  sshcmd = ssh
  xferbycopying = true
  sshversion =
  clientHostName = fs72a
  ignoreinodenumbers = false
  links-aux = true
  links = default
  times = true
  group = true
  owner = true
  numericids = false
  dontchmod = false
  perms = -1
  watch = true
  rsrc-aux = false
  rsrc = default
  maxerrors = 1
  unicodeCS = false
  unicodeEnc = false
  unicode = default
  someHostIsInsensitive = false
  ignorecase = default
  timers = false
  terse = false
  logfile = /root/.unison/unison.log
  log = true
  debugtimes = false
  debug = all
  addprefsto =
  Contacting server...
  [remote] Shell connection: ssh (ssh, fs2b.our.domain.org.uk, -e, none, 
unison, -server)
  [globals] Checking path '' for expansions
  Connected [//fs2b//root/unison-test -> //fs72a//root/unison-test]
  [startup] Roots:
  /root/unison-test
  ssh://fs2b.our.domain.org.uk//root/unison-test
i.e.
  /root/unison-test
  ssh://fs2b.our.domain.org.uk//root/unison-test
i.e. (in canonical order)
 /root/unison-test
 //fs2b//root/unison-test

  [props] Setting permission mask to  (7 and )
  [stasher] initBackupsLocal
  [stasher] d = /
  [stasher] Prefix and suffix regexps for backup filenames have been updated
  [server: stasher] initBackupsLocal
  [server: stasher] d = /
  [server: stasher] Prefix and suffix regexps for backup filenames have been 
updated
  Looking for changes
  [ui] temp: Globals.paths =
  [update] Loading archive from 

[Touch-packages] [Bug 2009756] Re: backups fail since latest rsync security update

[Marc Deslauriers]

Some users only have the -security pocket enabled, and not -updates, so
when a fix is required for a regression introduced by a security update,
it needs to go to the -security pocket. It doesn't in any way mean BIT
had a security issue.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/2009756

Title:
  backups fail since latest rsync security update

Status in backintime package in Ubuntu:
  Fix Released
Status in rsync package in Ubuntu:
  New
Status in backintime source package in Jammy:
  In Progress
Status in rsync source package in Jammy:
  New
Status in backintime source package in Kinetic:
  In Progress
Status in rsync source package in Kinetic:
  New
Status in backintime source package in Lunar:
  Fix Released
Status in rsync source package in Lunar:
  New

Bug description:
  Backintime uses rsync to perform updates. Unfortunately there is an
  incompatibility between the currently released version of backintime
  and rsync >= 3.2.4 (see https://github.com/bit-
  team/backintime/issues/1247)

  Rsync has been updated from 3.2.3 to 3.2.7 on Feb 27. This broke
  backintime backups. The symptom is an error message like this:

  Command "rsync -a --delete --rsh=ssh -o ServerAliveInterval=240 -o
  LogLevel=Error -o IdentityFile=/home/aurelien/.ssh/backintime -p 22
  /tmp/tmpxilwcwk4/
  u...@example.com:"./backintime/switch/aurelien/1/20230308-230517-262""
  returns 3 | rsync: change_dir#3
  "/data/home/user//"./backintime/switch/aurelien/1" failed: No such
  file or directory (2)

  The workaround described in the GitHub issue works (passing `--old-
  args` to rsync), but maybe it would be better if the backintime
  package did this automatically?

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: backintime-common 1.2.1-3ubuntu0.1
  ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Mar  8 23:19:02 2023
  InstallationDate: Installed on 2021-06-23 (623 days ago)
  InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: backintime
  UpgradeStatus: Upgraded to jammy on 2022-08-24 (196 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/backintime/+bug/2009756/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2009756] Re: backups fail since latest rsync security update

[buhtz]

I'm not happy about the situation. But maybe I'm to conservative about
it.

There is no known security problem with BIT. So you shouldn't use the
security repo to update it.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/2009756

Title:
  backups fail since latest rsync security update

Status in backintime package in Ubuntu:
  Fix Released
Status in rsync package in Ubuntu:
  New
Status in backintime source package in Jammy:
  In Progress
Status in rsync source package in Jammy:
  New
Status in backintime source package in Kinetic:
  In Progress
Status in rsync source package in Kinetic:
  New
Status in backintime source package in Lunar:
  Fix Released
Status in rsync source package in Lunar:
  New

Bug description:
  Backintime uses rsync to perform updates. Unfortunately there is an
  incompatibility between the currently released version of backintime
  and rsync >= 3.2.4 (see https://github.com/bit-
  team/backintime/issues/1247)

  Rsync has been updated from 3.2.3 to 3.2.7 on Feb 27. This broke
  backintime backups. The symptom is an error message like this:

  Command "rsync -a --delete --rsh=ssh -o ServerAliveInterval=240 -o
  LogLevel=Error -o IdentityFile=/home/aurelien/.ssh/backintime -p 22
  /tmp/tmpxilwcwk4/
  u...@example.com:"./backintime/switch/aurelien/1/20230308-230517-262""
  returns 3 | rsync: change_dir#3
  "/data/home/user//"./backintime/switch/aurelien/1" failed: No such
  file or directory (2)

  The workaround described in the GitHub issue works (passing `--old-
  args` to rsync), but maybe it would be better if the backintime
  package did this automatically?

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: backintime-common 1.2.1-3ubuntu0.1
  ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Mar  8 23:19:02 2023
  InstallationDate: Installed on 2021-06-23 (623 days ago)
  InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: backintime
  UpgradeStatus: Upgraded to jammy on 2022-08-24 (196 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/backintime/+bug/2009756/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2009756] Re: backups fail since latest rsync security update

[Marc Deslauriers]

Hi @agateau,

I have uploaded fixed backintime packages for jammy and kinetic to the
security team PPA here:

https://launchpad.net/~ubuntu-security-
proposed/+archive/ubuntu/ppa/+packages

Once they are finished building, could you give them a try? If they work
correctly, I will release them.

Thanks!

** Changed in: backintime (Ubuntu)
   Status: Invalid => In Progress

** Changed in: backintime (Ubuntu)
 Assignee: buhtz (buhtz) => Marc Deslauriers (mdeslaur)

** Also affects: rsync (Ubuntu Lunar)
   Importance: Undecided
   Status: New

** Also affects: backintime (Ubuntu Lunar)
   Importance: Undecided
 Assignee: Marc Deslauriers (mdeslaur)
   Status: In Progress

** Also affects: rsync (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

** Also affects: backintime (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

** Also affects: rsync (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: backintime (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Changed in: backintime (Ubuntu Lunar)
   Status: In Progress => Fix Released

** Changed in: backintime (Ubuntu Kinetic)
   Status: New => In Progress

** Changed in: backintime (Ubuntu Jammy)
   Status: New => In Progress

** Changed in: backintime (Ubuntu Jammy)
 Assignee: (unassigned) => Marc Deslauriers (mdeslaur)

** Changed in: backintime (Ubuntu Kinetic)
 Assignee: (unassigned) => Marc Deslauriers (mdeslaur)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/2009756

Title:
  backups fail since latest rsync security update

Status in backintime package in Ubuntu:
  Fix Released
Status in rsync package in Ubuntu:
  New
Status in backintime source package in Jammy:
  In Progress
Status in rsync source package in Jammy:
  New
Status in backintime source package in Kinetic:
  In Progress
Status in rsync source package in Kinetic:
  New
Status in backintime source package in Lunar:
  Fix Released
Status in rsync source package in Lunar:
  New

Bug description:
  Backintime uses rsync to perform updates. Unfortunately there is an
  incompatibility between the currently released version of backintime
  and rsync >= 3.2.4 (see https://github.com/bit-
  team/backintime/issues/1247)

  Rsync has been updated from 3.2.3 to 3.2.7 on Feb 27. This broke
  backintime backups. The symptom is an error message like this:

  Command "rsync -a --delete --rsh=ssh -o ServerAliveInterval=240 -o
  LogLevel=Error -o IdentityFile=/home/aurelien/.ssh/backintime -p 22
  /tmp/tmpxilwcwk4/
  u...@example.com:"./backintime/switch/aurelien/1/20230308-230517-262""
  returns 3 | rsync: change_dir#3
  "/data/home/user//"./backintime/switch/aurelien/1" failed: No such
  file or directory (2)

  The workaround described in the GitHub issue works (passing `--old-
  args` to rsync), but maybe it would be better if the backintime
  package did this automatically?

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: backintime-common 1.2.1-3ubuntu0.1
  ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Mar  8 23:19:02 2023
  InstallationDate: Installed on 2021-06-23 (623 days ago)
  InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: backintime
  UpgradeStatus: Upgraded to jammy on 2022-08-24 (196 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/backintime/+bug/2009756/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2009830] [NEW] no more sounds, speackers are not detected

[Domon Kevin]

Public bug reported:

since the upadating to Ubuntu 22.04.2 LTS, i have no sounds from
internet. Sound works from Rhythm box software or videos. I also don't
have "system" sound. The audio device is not detected

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu2
ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-35-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC1', '/dev/snd/pcmC1D2p', 
'/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar  9 13:09:41 2023
InstallationDate: Installed on 2020-08-18 (932 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
Symptom: audio
UpgradeStatus: Upgraded to jammy on 2022-08-19 (202 days ago)
dmi.bios.date: 01/02/2018
dmi.bios.release: 5.11
dmi.bios.version: HXFZ-14-BI-Y116CR600-CC34O-002-D
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Cherry Trail CR
dmi.board.vendor: AMI Corporation
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 10
dmi.chassis.version: To be filled by O.E.M.
dmi.modalias: 
dmi:bvn:bvrHXFZ-14-BI-Y116CR600-CC34O-002-D:bd01/02/2018:br5.11:svnThomson:pnNEO14A.2WH32:pvrTobefilledbyO.E.M.:rvnAMICorporation:rnCherryTrailCR:rvrTobefilledbyO.E.M.:cvn:ct10:cvrTobefilledbyO.E.M.:skuTobefilledbyO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: NEO14A.2WH32
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Thomson

** Affects: pulseaudio (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy wayland-session

-- 
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/2009830

Title:
  no more sounds, speackers are not detected

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  since the upadating to Ubuntu 22.04.2 LTS, i have no sounds from
  internet. Sound works from Rhythm box software or videos. I also don't
  have "system" sound. The audio device is not detected

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: pulseaudio 1:15.99.1+dfsg1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC1', '/dev/snd/pcmC1D2p', 
'/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0p', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar  9 13:09:41 2023
  InstallationDate: Installed on 2020-08-18 (932 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: Upgraded to jammy on 2022-08-19 (202 days ago)
  dmi.bios.date: 01/02/2018
  dmi.bios.release: 5.11
  dmi.bios.version: HXFZ-14-BI-Y116CR600-CC34O-002-D
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Cherry Trail CR
  dmi.board.vendor: AMI Corporation
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.version: To be filled by O.E.M.
  dmi.modalias: 
dmi:bvn:bvrHXFZ-14-BI-Y116CR600-CC34O-002-D:bd01/02/2018:br5.11:svnThomson:pnNEO14A.2WH32:pvrTobefilledbyO.E.M.:rvnAMICorporation:rnCherryTrailCR:rvrTobefilledbyO.E.M.:cvn:ct10:cvrTobefilledbyO.E.M.:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: NEO14A.2WH32
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Thomson

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2009830/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : 

[Touch-packages] [Bug 2009808] Re: Doesn't display the livepatch service status

[Sebastien Bacher]

Reassigning to ubuntu-advantage-tools since after chat discussion it
seems that the expected behavior would be for the pro client to report
that in its status which it doesn't

$ pro status
SERVICE  ENTITLED  STATUSDESCRIPTION
livepatchyes   enabled   Canonical Livepatch service

** Package changed: software-properties (Ubuntu) => ubuntu-advantage-
tools (Ubuntu)

** Summary changed:

- Doesn't display the livepatch service status
+ Doesn't display the correct livepatch service status

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/2009808

Title:
  Doesn't display the correct livepatch service status

Status in ubuntu-advantage-tools package in Ubuntu:
  New

Bug description:
  Starting a focal VM which didn't get updated the livepatch icon in the
  panel shows an orange warning and the popdown display a string saying
  it hit an error fetching the status

  $ canonical-livepatch status
  last check: 58 seconds ago
  kernel: 5.15.0-56.62~20.04.1-generic
  server check-in: failed: livepatch check failed: unauthorized
  patch state: ✗ kernel version not supported

  
  The software-properties tab doesn't give any clue about that though, maybe it 
should?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/2009808/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1999156] Re: /usr/share/apport/whoopsie-upload-all:FileNotFoundError:/usr/share/apport/whoopsie-upload-all@220:main:collect_info:process_report:add_package_info:add_package:get_v

[Benjamin Drung]

`apt.Cache(progress, rootdir='/')` fails with `FileNotFoundError`. I
consider it a bug in python-apt. If the caller should catch that
failure, please document that in python-apt and assign back to apport.

** Package changed: apport (Ubuntu) => python-apt (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/1999156

Title:
  /usr/share/apport/whoopsie-upload-
  all:FileNotFoundError:/usr/share/apport/whoopsie-upload-
  
all@220:main:collect_info:process_report:add_package_info:add_package:get_version:_apt_pkg:_cache:__init__:_check_and_create_required_dirs:makedirs:makedirs

Status in python-apt package in Ubuntu:
  New

Bug description:
  ```
  Traceback (most recent call last):
File "/usr/share/apport/whoopsie-upload-all", line 220, in 
  main()
File "/usr/share/apport/whoopsie-upload-all", line 202, in main
  stamps = collect_info()
File "/usr/share/apport/whoopsie-upload-all", line 150, in collect_info
  res = process_report(r)
File "/usr/share/apport/whoopsie-upload-all", line 90, in process_report
  r.add_package_info()
File "/usr/lib/python3/dist-packages/apport/report.py", line 351, in 
add_package_info
  version = self.add_package(package)
File "/usr/lib/python3/dist-packages/apport/report.py", line 320, in 
add_package
  version = packaging.get_version(package)
File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 163, 
in get_version
  pkg = self._apt_pkg(package)
File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 156, 
in _apt_pkg
  return self._cache()[package]
File "/usr/lib/python3/dist-packages/apport/packaging_impl.py", line 121, 
in _cache
  self._apt_cache = apt.Cache(progress, rootdir='/')
File "/usr/lib/python3/dist-packages/apt/cache.py", line 143, in __init__
  self._check_and_create_required_dirs(rootdir)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 183, in 
_check_and_create_required_dirs
  os.makedirs(rootdir + d)
File "/usr/lib/python3.10/os.py", line 215, in makedirs
  makedirs(head, exist_ok=exist_ok)
File "/usr/lib/python3.10/os.py", line 225, in makedirs
  mkdir(name, mode)
  FileNotFoundError: [Errno 2] No such file or directory: 
'//var/cache/apt/archives'
  ```

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.11-0ubuntu82.2, the problem page at 
https://errors.ubuntu.com/problem/e3a000aa8a314f9ae9303dcd52a119799a00496f 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1999156/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2008638] Re: apport-gtk crashed with urllib.error.HTTPError in http_error_default(): HTTP Error 502: Bad Gateway

[Ubuntu QA Website]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
https://iso.qa.ubuntu.com/qatracker/reports/bugs/2008638

** Tags added: iso-testing

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/2008638

Title:
  apport-gtk crashed with urllib.error.HTTPError in
  http_error_default(): HTTP Error 502: Bad Gateway

Status in Apport:
  Fix Committed
Status in apport package in Ubuntu:
  Confirmed

Bug description:
  Had a Nautlius crash prior to this error.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: apport-gtk 2.26.0-0ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashReports:
   640:1201:124:38512857:2023-02-24 12:17:00.435185909 -0500:2023-02-24 
12:17:01.435185909 -0500:/var/crash/_usr_bin_gnome-shell.1201.crash
   640:1000:1000:90509:2023-02-26 10:18:25.277171373 -0500:2023-02-26 
10:18:26.277171373 -0500:/var/crash/_usr_share_apport_apport-gtk.1000.crash
   600:116:124:37:2023-02-26 10:18:21.948992294 -0500:2023-02-18 
17:59:57.688578533 -0500:/var/crash/_usr_bin_nautilus.1000.uploaded
   640:1000:124:14955989:2023-02-26 10:16:50.213119506 -0500:2023-02-26 
10:17:03.637664041 -0500:/var/crash/_usr_bin_nautilus.1000.crash
   664:1000:1000:0:2023-02-26 10:17:03.617663168 -0500:2023-02-26 
10:17:03.617663168 -0500:/var/crash/_usr_bin_nautilus.1000.upload
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb 26 10:18:26 2023
  ExecutablePath: /usr/share/apport/apport-gtk
  InstallationDate: Installed on 2023-02-13 (12 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221209)
  InterpreterPath: /usr/bin/python3.11
  JournalErrors:
   Feb 26 10:18:26 hostname systemd[2030]: update-notifier-crash.service: 
Failed with result 'exit-code'.
   Feb 26 10:18:26 hostname systemd[2030]: Failed to start Notification 
regarding a crash report.
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Python3Details: /usr/bin/python3.11, Python 3.11.1, python3-minimal, 3.11.1-3
  PythonArgs: ['/usr/share/apport/apport-gtk']
  PythonDetails: N/A
  SourcePackage: apport
  Title: apport-gtk crashed with urllib.error.HTTPError in 
http_error_default(): HTTP Error 502: Bad Gateway
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/2008638/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1926870] Re: python-debian has invalid version

[Benjamin Drung]

This bug is a duplicate of bug #1991606 but due to bug #2008514 it runs
into a timeout when marking as duplicate. Since python-debian in Ubuntu
23.04 (lunar) is fixed, I am marking this bug is fixed as well. Please
follow bug #1991606 for the updates to the stable releases.

** Changed in: python-debian (Ubuntu)
   Importance: Undecided => High

** Changed in: python-debian (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-debian in Ubuntu.
https://bugs.launchpad.net/bugs/1926870

Title:
  python-debian has invalid version

Status in python-debian package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu: Ubuntu 20.04  (actually it's Linux Mint 20.1)
  Package: python-debian 0.1.36ubuntu1

  Python package version should correspond to PEP 440:
  https://www.python.org/dev/peps/pep-0440/#local-version-identifiers

  It requires + sign before local version identifier, like:
  2.0.0+ubuntu0.20.4.4

  So python-debian should have version like:
  0.1.36+ubuntu1

  Actually if you'll launch pip list, you'll see:
  python-debian   0.1.36ubuntu1

  Why does it matter:
  Some package managers, like Poetry, will fail parsing this version.
  I thought to fix Poetry, but don't think I should handle not PEP 
440-compliant versions
  in PEP 440 version parser.

  Notes:
  This only should apply to version, specified for pip - Python package 
manager, not Apt.
  Version in Apt may stay 0.1.36ubuntu1.

  Corresponding issue for Poetry:
  https://github.com/python-poetry/poetry/issues/4022

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-debian/+bug/1926870/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1996040] Re: apport-unpack cannot load gitkraken crash report - 'ascii' codec can't decode byte 0xfc in position 56

[Benjamin Drung]

I have not enough data to answer that question. Feeding a core dump into
apport-unpack can let it crash (user error). I don't know if *all* of
those crashes were caused by users feeding a crash file into apport-
unpack. The crash reports on errors.ubuntu.com do not contain the input
file and I haven't seen a bug report where a malformed crash report was
attached.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1996040

Title:
  apport-unpack cannot load gitkraken crash report - 'ascii' codec can't
  decode byte 0xfc in position 56

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Kinetic:
  Incomplete

Bug description:
  Impact
  ==

  apport-unpack and whoopsie-upload-all can crash when fed with a
  malformed problem report. They should print a proper error message
  instead of crashing. This bug does not happen that often, but the fix
  for this bug is the foundation for the fix for bug #1995100.

  Test Plan
  =

  1. Create malformed report:
  ```
  printf 'AB\xfc:CD\n' > malformed.crash
  ```
  2. Try to unpack it:
  ```
  apport-unpack malformed.crash unpack
  ```

  It should print an error message instead of a stack trace.

  Where problems could occur
  ==

  The patch touches the problem report handling and therefore can affect
  apport-unpack, apport-bug, whoopsie-upload-all. The change is covered
  with tests and apport has a test suite running during build and as
  autopkgtest.

  Original report
  ===

  The latest GitKraken client (8.10.2 x64) is crashed every minute in
  cycle when you doing a rebase. When I try to inspect crash log to find
  the reason, the apport-unpack is not be able to process it:

  /var/lib/apport/coredump$ sudo apport-unpack 
core._snap_gitkraken_199_usr_share_gitkraken_gitkraken.1000.5de91c04-23ab-45c8-933c-0466d56e9fad.135785.50225891
 unpack
  [sudo] пароль для mingun:
  Traceback (most recent call last):
    File "/usr/bin/apport-unpack", line 59, in 
  pr.load(f, binary=False)
    File "/usr/lib/python3/dist-packages/problem_report.py", line 194, in load
  key = key.decode('ASCII')
  UnicodeDecodeError: 'ascii' codec can't decode byte 0xfc in position 56: 
ordinal not in range(128)

  Unfortunately, crash file is too big (~9GB) and does not compress
  further

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1996040/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2008638] Re: apport-gtk crashed with urllib.error.HTTPError in http_error_default(): HTTP Error 502: Bad Gateway

[Benjamin Drung]

** Changed in: apport (Ubuntu)
   Importance: Medium => High

** Changed in: apport
   Importance: Medium => High

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/2008638

Title:
  apport-gtk crashed with urllib.error.HTTPError in
  http_error_default(): HTTP Error 502: Bad Gateway

Status in Apport:
  Fix Committed
Status in apport package in Ubuntu:
  Confirmed

Bug description:
  Had a Nautlius crash prior to this error.

  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: apport-gtk 2.26.0-0ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashReports:
   640:1201:124:38512857:2023-02-24 12:17:00.435185909 -0500:2023-02-24 
12:17:01.435185909 -0500:/var/crash/_usr_bin_gnome-shell.1201.crash
   640:1000:1000:90509:2023-02-26 10:18:25.277171373 -0500:2023-02-26 
10:18:26.277171373 -0500:/var/crash/_usr_share_apport_apport-gtk.1000.crash
   600:116:124:37:2023-02-26 10:18:21.948992294 -0500:2023-02-18 
17:59:57.688578533 -0500:/var/crash/_usr_bin_nautilus.1000.uploaded
   640:1000:124:14955989:2023-02-26 10:16:50.213119506 -0500:2023-02-26 
10:17:03.637664041 -0500:/var/crash/_usr_bin_nautilus.1000.crash
   664:1000:1000:0:2023-02-26 10:17:03.617663168 -0500:2023-02-26 
10:17:03.617663168 -0500:/var/crash/_usr_bin_nautilus.1000.upload
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb 26 10:18:26 2023
  ExecutablePath: /usr/share/apport/apport-gtk
  InstallationDate: Installed on 2023-02-13 (12 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221209)
  InterpreterPath: /usr/bin/python3.11
  JournalErrors:
   Feb 26 10:18:26 hostname systemd[2030]: update-notifier-crash.service: 
Failed with result 'exit-code'.
   Feb 26 10:18:26 hostname systemd[2030]: Failed to start Notification 
regarding a crash report.
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  Python3Details: /usr/bin/python3.11, Python 3.11.1, python3-minimal, 3.11.1-3
  PythonArgs: ['/usr/share/apport/apport-gtk']
  PythonDetails: N/A
  SourcePackage: apport
  Title: apport-gtk crashed with urllib.error.HTTPError in 
http_error_default(): HTTP Error 502: Bad Gateway
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/2008638/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2009260] Re: apport-gtk crashed with urllib.error.URLError in do_open():

[Benjamin Drung]

*** This bug is a duplicate of bug 2008638 ***
https://bugs.launchpad.net/bugs/2008638

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

Relevant stack trace:

Traceback (most recent call last):
  File "/usr/share/apport/apport-gtk", line 698, in 
app.run_argv()
  File "/usr/lib/python3/dist-packages/apport/ui.py", line 933, in run_argv
return self.run_crashes()
   ^^
  File "/usr/lib/python3/dist-packages/apport/ui.py", line 333, in run_crashes
self.run_crash(f)
  File "/usr/lib/python3/dist-packages/apport/ui.py", line 438, in run_crash
self.file_report()
  File "/usr/lib/python3/dist-packages/apport/ui.py", line 1852, in file_report
upthread.exc_raise()
  File "/usr/lib/python3/dist-packages/apport/REThread.py", line 62, in 
exc_raise
raise self._exception[1].with_traceback(self._exception[2])
  File "/usr/lib/python3/dist-packages/apport/REThread.py", line 37, in run
self._retval = self.__target(*self.__args, **self.__kwargs)
   
  File "/usr/lib/python3/dist-packages/apport/crashdb_impl/launchpad.py", line 
231, in upload
ticket = upload_blob(
 
  File "/usr/lib/python3/dist-packages/apport/crashdb_impl/launchpad.py", line 
1285, in upload_blob
result = opener.open(req)
 
  File "/usr/lib/python3.11/urllib/request.py", line 519, in open
response = self._open(req, data)
   ^
  File "/usr/lib/python3.11/urllib/request.py", line 536, in _open
result = self._call_chain(self.handle_open, protocol, protocol +
 ^^^
  File "/usr/lib/python3.11/urllib/request.py", line 496, in _call_chain
result = func(*args)
 ^^^
  File "/usr/lib/python3/dist-packages/apport/crashdb_impl/launchpad.py", line 
1237, in https_open
return self.do_open(HTTPSProgressConnection, req)
   ^^
  File "/usr/lib/python3.11/urllib/request.py", line 1351, in do_open
raise URLError(err)
urllib.error.URLError: 

This has the same underlying issue than bug #2008638.

** Information type changed from Private to Public

** This bug has been marked a duplicate of bug 2008638
   apport-gtk crashed with urllib.error.HTTPError in http_error_default(): HTTP 
Error 502: Bad Gateway

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/2009260

Title:
  apport-gtk crashed with urllib.error.URLError in do_open(): 

Status in apport package in Ubuntu:
  New

Bug description:
  daily built 04/03

  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: apport-gtk 2.26.0-0ubuntu2
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportLog:
   
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.480
  Date: Sat Mar  4 11:56:30 2023
  ExecutablePath: /usr/share/apport/apport-gtk
  InterpreterPath: /usr/bin/python3.11
  LiveMediaBuild: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20230304)
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.11, Python 3.11.1, python3-minimal, 3.11.1-3
  PythonArgs: ['/usr/share/apport/apport-gtk']
  PythonDetails: N/A
  SourcePackage: apport
  Title: apport-gtk crashed with urllib.error.URLError in do_open(): 
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2009260/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2009578] Re: apport-gtk crashed with urllib.error.URLError in do_open():

[Benjamin Drung]

*** This bug is a duplicate of bug 2008638 ***
https://bugs.launchpad.net/bugs/2008638

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

The GNOME shell crash details can be found in JournalErrors.txt. Can you
open a separate bug report for it? This report is about the crash of
apport-gtk itself. The stack trace:

Traceback (most recent call last):
  File "/usr/share/apport/apport-gtk", line 698, in 
app.run_argv()
  File "/usr/lib/python3/dist-packages/apport/ui.py", line 933, in run_argv
return self.run_crashes()
   ^^
  File "/usr/lib/python3/dist-packages/apport/ui.py", line 333, in run_crashes
self.run_crash(f)
  File "/usr/lib/python3/dist-packages/apport/ui.py", line 438, in run_crash
self.file_report()
  File "/usr/lib/python3/dist-packages/apport/ui.py", line 1852, in file_report
upthread.exc_raise()
  File "/usr/lib/python3/dist-packages/apport/REThread.py", line 62, in 
exc_raise
raise self._exception[1].with_traceback(self._exception[2])
  File "/usr/lib/python3/dist-packages/apport/REThread.py", line 37, in run
self._retval = self.__target(*self.__args, **self.__kwargs)
   
  File "/usr/lib/python3/dist-packages/apport/crashdb_impl/launchpad.py", line 
231, in upload
ticket = upload_blob(
 
  File "/usr/lib/python3/dist-packages/apport/crashdb_impl/launchpad.py", line 
1285, in upload_blob
result = opener.open(req)
 
  File "/usr/lib/python3.11/urllib/request.py", line 519, in open
response = self._open(req, data)
   ^
  File "/usr/lib/python3.11/urllib/request.py", line 536, in _open
result = self._call_chain(self.handle_open, protocol, protocol +
 ^^^
  File "/usr/lib/python3.11/urllib/request.py", line 496, in _call_chain
result = func(*args)
 ^^^
  File "/usr/lib/python3/dist-packages/apport/crashdb_impl/launchpad.py", line 
1237, in https_open
return self.do_open(HTTPSProgressConnection, req)
   ^^
  File "/usr/lib/python3.11/urllib/request.py", line 1351, in do_open
raise URLError(err)
urllib.error.URLError: 

This is a duplicate of bug #2008638 which I fixed a few days ago (no
release yet).

** Information type changed from Private to Public

** This bug has been marked a duplicate of bug 2008638
   apport-gtk crashed with urllib.error.HTTPError in http_error_default(): HTTP 
Error 502: Bad Gateway

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/2009578

Title:
  apport-gtk crashed with urllib.error.URLError in do_open(): 

Status in apport package in Ubuntu:
  New

Bug description:
  Ubuntu lunar daily (LIVE) test on
  - lenovo g560 (i5m-480, 4gb, i915)

  Most of session went well; then screen just went black, a white
  segment (window trying to draw? as large rectangle) then report of
  crash...

  I tried reporting against GNOME-SHELL due to .crash file in
  /var/crash...

  Attempts to `ubuntu-bug _usr_bin_gnom` failed due to 502 PROXY
  ERROR & inability to login...

  message led me to believe report would be
  https://launchpad.net/bugs/2009260 but that maybe wrong)... this was
  filed later on same box..

  This CRASH WITH APPORT maybe related to the 502 PROXY ERROR I
  obtained.. rather than code on the box I was perform test on.. but
  that is GUESS.

  Note: I was having trouble operating device touchpad (esp clicking) so
  user input (me) may have been abnormal..

  ProblemType: Crash
  DistroRelease: Ubuntu 23.04
  Package: apport-gtk 2.26.0-0ubuntu2
  ProcVersionSignature: Ubuntu 6.1.0-16.16-generic 6.1.6
  Uname: Linux 6.1.0-16-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportLog:
   ERROR: apport (pid 9534) 2023-03-07 08:30:45,731: called for pid 2134, 
signal 11, core limit 0, dump mode 1
   ERROR: apport (pid 9534) 2023-03-07 08:30:45,735: executable: 
/usr/bin/gnome-shell (command line "/usr/bin/gnome-shell")
   ERROR: apport (pid 9534) 2023-03-07 08:30:46,755: debug: session gdbus call: 
(true,)

   ERROR: apport (pid 9534) 2023-03-07 08:30:54,302: wrote report 
/var/crash/_usr_bin_gnome-shell.1000.crash
  ApportVersion: 2.26.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.480
  CrashReports:
   640:1000:115:36158144:2023-03-07 08:33:29.403980255 +:2023-03-07 
08:33:30.403980255 +:/var/crash/_usr_bin_gnome-shell.1000.crash
   640:1000:1000:93015:2023-03-07 08:33:33.323980093 +:2023-03-07 
08:33:34.323980093 +:/var/crash/_usr_share_apport_apport-gtk.1000.crash
   664:1000:1000:0:2023-03-07 08:33:30.531980179 +:2023-03-07 
08:33:30.531980179 

[Touch-packages] [Bug 2004241] Re: Update to glib >= 2.75.1

[Gunnar Hjalmarsson]

@Daniel: It's already in -proposed. And there are more packages which
depend on glib >=2.75.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/2004241

Title:
  Update to glib >= 2.75.1

Status in glib2.0 package in Ubuntu:
  Triaged

Bug description:
  Update to glib >= 2.75.1 because that's what mutter 44 now requires.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2004241/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2008076] Re: Drop /usr/share/zoneinfo/posix and move /usr/share/zoneinfo/right into tzdata-right

[Benjamin Drung]

** Changed in: tzdata (Ubuntu)
   Status: New => Fix Committed

** Changed in: tzdata (Ubuntu)
   Importance: Undecided => Low

** Changed in: rdate (Ubuntu)
   Importance: Undecided => Low

** Changed in: moment-timezone.js (Ubuntu)
   Importance: Undecided => Low

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tzdata in Ubuntu.
https://bugs.launchpad.net/bugs/2008076

Title:
  Drop /usr/share/zoneinfo/posix and move /usr/share/zoneinfo/right into
  tzdata-right

Status in moment-timezone.js package in Ubuntu:
  New
Status in rdate package in Ubuntu:
  New
Status in tzdata package in Ubuntu:
  Fix Committed

Bug description:
  The tzdata package ships /usr/share/zoneinfo/posix/ (for Coordinated 
Universal Time) and /usr/share/zoneinfo/right/ (for International Atomic Time). 
The files in /usr/share/zoneinfo/posix/ are identical to their counterpart in 
/usr/share/zoneinfo/. The tzdata package converts the
  configured posix/* and right/* timezones to their unprefixed variant on every 
package upgrade (e.g. it changes "posix/Europe/Berlin" to "Europe/Berlin").

  Drop /usr/share/zoneinfo/right from tzdata and move
  /usr/share/zoneinfo/right into separate tzdata-right package.

  ubuntu-devel discussion: https://lists.ubuntu.com/archives/ubuntu-
  devel/2023-January/042405.html

  Two packages need to be adjusted:

  * moment-timezone.js: uses /usr/share/zoneinfo/posix/ in debian/rules
  * rdate: reads /usr/share/zoneinfo/right/UTC -> depend on tzdata-right

  Following packages were checked and do not need to be touched:

  Only in source code documentation and/or tests suite:

  * mariadb
  * mariadb-10.6

  Copies of tz soure code:

  * rust-chrono-tz (in tz)
  * udm (in tzdatabase)
  * r-cran-tzdb (in inst/tzdata)
  * pike8.0 (in lib/modules/Calendar.pmod/tzdata)

  Referencing only /usr/share/zoneinfo/posixrules:

  * manpages-l10n
  * libdatetime-timezone-perl
  * asterisk
  * mozjs102
  * mozjs78
  * thunderbird

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/moment-timezone.js/+bug/2008076/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2009756] Re: backups fail since latest rsync security update

[buhtz]

I opened a "question" at the rsync package
https://answers.launchpad.net/ubuntu/+source/rsync/+question/705772

And I also informed the rsync upstream maintainer about the situation.

As a workaround until Ubuntu fixed the rsync-update-bug I would advice to use 
Back In Time from upstream (GitHub repo) or using the PPA.
https://github.com/bit-team/backintime#installation

** Also affects: rsync (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/2009756

Title:
  backups fail since latest rsync security update

Status in backintime package in Ubuntu:
  Invalid
Status in rsync package in Ubuntu:
  New

Bug description:
  Backintime uses rsync to perform updates. Unfortunately there is an
  incompatibility between the currently released version of backintime
  and rsync >= 3.2.4 (see https://github.com/bit-
  team/backintime/issues/1247)

  Rsync has been updated from 3.2.3 to 3.2.7 on Feb 27. This broke
  backintime backups. The symptom is an error message like this:

  Command "rsync -a --delete --rsh=ssh -o ServerAliveInterval=240 -o
  LogLevel=Error -o IdentityFile=/home/aurelien/.ssh/backintime -p 22
  /tmp/tmpxilwcwk4/
  u...@example.com:"./backintime/switch/aurelien/1/20230308-230517-262""
  returns 3 | rsync: change_dir#3
  "/data/home/user//"./backintime/switch/aurelien/1" failed: No such
  file or directory (2)

  The workaround described in the GitHub issue works (passing `--old-
  args` to rsync), but maybe it would be better if the backintime
  package did this automatically?

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: backintime-common 1.2.1-3ubuntu0.1
  ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Mar  8 23:19:02 2023
  InstallationDate: Installed on 2021-06-23 (623 days ago)
  InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: backintime
  UpgradeStatus: Upgraded to jammy on 2022-08-24 (196 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/backintime/+bug/2009756/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2009808] Re: Doesn't display the livepatch service status

[Sebastien Bacher]

** Attachment added: "a screenshot showing the issue"
   
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2009808/+attachment/5653109/+files/livepatch.png

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/2009808

Title:
  Doesn't display the livepatch service status

Status in software-properties package in Ubuntu:
  New

Bug description:
  Starting a focal VM which didn't get updated the livepatch icon in the
  panel shows an orange warning and the popdown display a string saying
  it hit an error fetching the status

  $ canonical-livepatch status
  last check: 58 seconds ago
  kernel: 5.15.0-56.62~20.04.1-generic
  server check-in: failed: livepatch check failed: unauthorized
  patch state: ✗ kernel version not supported

  
  The software-properties tab doesn't give any clue about that though, maybe it 
should?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2009808/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 2009808] [NEW] Doesn't display the livepatch service status

[Sebastien Bacher]

Public bug reported:

Starting a focal VM which didn't get updated the livepatch icon in the
panel shows an orange warning and the popdown display a string saying it
hit an error fetching the status

$ canonical-livepatch status
last check: 58 seconds ago
kernel: 5.15.0-56.62~20.04.1-generic
server check-in: failed: livepatch check failed: unauthorized
patch state: ✗ kernel version not supported


The software-properties tab doesn't give any clue about that though, maybe it 
should?

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/2009808

Title:
  Doesn't display the livepatch service status

Status in software-properties package in Ubuntu:
  New

Bug description:
  Starting a focal VM which didn't get updated the livepatch icon in the
  panel shows an orange warning and the popdown display a string saying
  it hit an error fetching the status

  $ canonical-livepatch status
  last check: 58 seconds ago
  kernel: 5.15.0-56.62~20.04.1-generic
  server check-in: failed: livepatch check failed: unauthorized
  patch state: ✗ kernel version not supported

  
  The software-properties tab doesn't give any clue about that though, maybe it 
should?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2009808/+subscriptions


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp