from:"Dave"

Build reference:
https://launchpad.net/ubuntu/+source/busybox/1:1.36.1-6ubuntu2/+build/28036868

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

Title:
  busybox 1.36.1 FTBFS with current kernel headers on noble

Status in busybox package in Ubuntu:
  New

Bug description:
  The networking/tc.c unit in busybox relies upon the CBQ (class based
  queue) UAPI in the kernel. Unfortunately this was removed in [1]. At
  present, there is no upstream patch (or even bug report that I can
  find), and this close to the release patching the kernel to resolve
  things is not going to happen. Will attach a patch re-instating the
  defines from the removed headers.

  [1]: https://git.launchpad.net/~ubuntu-
  
kernel/ubuntu/+source/linux/+git/noble/commit/?id=33241dca486264193ed68167c8eeae1fb197f3df

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/2062414/+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 2062414] Re: busybox 1.36.1 FTBFS with current kernel headers on noble

Revised patch with upstream bug links

** Patch added: "2-2062414.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/2062414/+attachment/5767659/+files/2-2062414.debdiff

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

Title:
  busybox 1.36.1 FTBFS with current kernel headers on noble

Status in busybox package in Ubuntu:
  New

Bug description:
  The networking/tc.c unit in busybox relies upon the CBQ (class based
  queue) UAPI in the kernel. Unfortunately this was removed in [1]. At
  present, there is no upstream patch (or even bug report that I can
  find), and this close to the release patching the kernel to resolve
  things is not going to happen. Will attach a patch re-instating the
  defines from the removed headers.

  [1]: https://git.launchpad.net/~ubuntu-
  
kernel/ubuntu/+source/linux/+git/noble/commit/?id=33241dca486264193ed68167c8eeae1fb197f3df

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/2062414/+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 2062414] Re: busybox 1.36.1 FTBFS with current kernel headers on noble

** Patch added: "1-2062414.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/2062414/+attachment/5767655/+files/1-2062414.debdiff

** Tags added: update-excuse

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

Title:
  busybox 1.36.1 FTBFS with current kernel headers on noble

Status in busybox package in Ubuntu:
  New

Bug description:
  The networking/tc.c unit in busybox relies upon the CBQ (class based
  queue) UAPI in the kernel. Unfortunately this was removed in [1]. At
  present, there is no upstream patch (or even bug report that I can
  find), and this close to the release patching the kernel to resolve
  things is not going to happen. Will attach a patch re-instating the
  defines from the removed headers.

  [1]: https://git.launchpad.net/~ubuntu-
  
kernel/ubuntu/+source/linux/+git/noble/commit/?id=33241dca486264193ed68167c8eeae1fb197f3df

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/2062414/+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 2062414] [NEW] busybox 1.36.1 FTBFS with current kernel headers on noble

Public bug reported:

The networking/tc.c unit in busybox relies upon the CBQ (class based
queue) UAPI in the kernel. Unfortunately this was removed in [1]. At
present, there is no upstream patch (or even bug report that I can
find), and this close to the release patching the kernel to resolve
things is not going to happen. Will attach a patch re-instating the
defines from the removed headers.

[1]: https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/noble/commit/?id=33241dca486264193ed68167c8eeae1fb197f3df

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


** Tags: rls-nn-incoming update-excuse

** Tags added: rls-nn-incoming

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

Title:
  busybox 1.36.1 FTBFS with current kernel headers on noble

Status in busybox package in Ubuntu:
  New

Bug description:
  The networking/tc.c unit in busybox relies upon the CBQ (class based
  queue) UAPI in the kernel. Unfortunately this was removed in [1]. At
  present, there is no upstream patch (or even bug report that I can
  find), and this close to the release patching the kernel to resolve
  things is not going to happen. Will attach a patch re-instating the
  defines from the removed headers.

  [1]: https://git.launchpad.net/~ubuntu-
  
kernel/ubuntu/+source/linux/+git/noble/commit/?id=33241dca486264193ed68167c8eeae1fb197f3df

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/2062414/+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 1097467] Re: bash does not fulfill --rcfile option properly

2024-04-16 Thread Dave Jones

Attaching new debdiff based on the current noble version.

** Patch added: "1097467-3.debdiff"

https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1097467/+attachment/5766422/+files/1097467-3.debdiff

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

Title:
bash does not fulfill --rcfile option properly

Status in Gnu Bash:
New
Status in bash package in Ubuntu:
Confirmed

Bug description:
I am starting a bash shell using

$ bash --noprofile --rcfile my-custom-bash-rc-file

Due to the --rcflag, the newly started bash should *not* execute
commands from /etc/bash.bashrc. That is at least how I interpret `man
bash`:

--rcfile file
Execute commands from file instead of the system wide
initialization file /etc/bash.bashrc and the standard personal initial‐
ization file ~/.bashrc if the shell is interactive (see
INVOCATION below).

However, it seems that the commands in /etc/bash.bashrc are in fact
executed.

To see/reproduce/diagnose this, on Ubuntu I believe one can just
invoke bash like this (as the regular user):

$ touch testrc
$ env -i bash --noprofile --rcfile testrc

The expected result would be that nothing special is printed on the
terminal. However, there is an error message, which is printed from
/etc/bash.bashrc. The "env -i" causes $HOME to not be set in the
invoked shell, which in turn triggers the error. The error message is:

> To run a command as administrator (user "root"), use "sudo ".
> See "man sudo_root" for details.

Another way to see this -- without the "env -i" -- is to add a
command to /etc/bash.bashrc, such as

echo HELLO THERE

To trigger the bug(?), one can then just do

$ touch testrc
$ bash --noprofile --rcfile testrc

The expected result would be that nothing special is shown in the
terminal. However, it turns out that the string

HELLO THERE

is printed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnubash/+bug/1097467/+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 2060730] Re: totem cannot install codecs via packagekit

2024-04-12 Thread Dave Jones

Sorry, I should give a bit more context on this issue to clarify things.
The test for this issue comes from the ISO tests for the Ubuntu Desktop
for Raspberry Pi images. The test intends to check whether a fresh
install can play a video "out of the box". The video used in the test is
https://archive.org/download/BigBuckBunny_124/Content/big_buck_bunny_720p_surround.mp4
which is downloaded and opened normally.

The video deliberately uses a codec that isn't seeded and installed by
default (but is a commonly used format) in the expectation that totem
will guide the user through installing the necessary bits (which it used
to back in groovy, but doesn't since -- incidentally the reason this
wasn't noticed in jammy is because it failed to even open the video at
that point, but that's now been fixed).

Seeding gstreamer1.0-packagekit is probably fine (the whole of
gstreamer's in main). Seeding gnome-software is likely not (given we're
using snap-store for software delivery currently). Is app-center
intended to fill that gap in future?

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

Title:
  totem cannot install codecs via packagekit

Status in App Center:
  Triaged
Status in packagekit package in Ubuntu:
  Invalid
Status in totem package in Ubuntu:
  Invalid

Bug description:
  While attempting to play a video on Ubuntu noble desktop for raspberry
  pi, totem attempts to locate a package for the H.264 codec but cannot
  find a service providing org.freedesktop.PackageKit. This is strange
  given that packagekit is installed, provides packagekit.service, which
  declares that it provides that name over DBus. Specifically, the
  following is output by totem:

  ** Message: 21:13:39.000: Missing plugin: gstreamer|1.0|totem|MPEG-4 AAC 
decoder|decoder-audio/mpeg, mpegversion=(int)4, level=(string)4, 
base-profile=(string)lc, profile=(string)lc (MPEG-4 AAC decoder)
  ** Message: 21:13:39.000: Missing plugin: gstreamer|1.0|totem|H.264 (Main 
Profile) decoder|decoder-video/x-h264, level=(string)3.1, profile=(string)main 
(H.264 (Main Profile) decoder)
  ** Message: 21:13:39.414: PackageKit: xid = 0
  ** Message: 21:13:39.414: PackageKit: desktop_id = org.gnome.Totem.desktop
  ** Message: 21:13:39.414: PackageKit: Codec nice name: MPEG-4 AAC decoder
  ** Message: 21:13:39.414: PackageKit: ignoring field named level
  ** Message: 21:13:39.414: PackageKit: ignoring field named base-profile
  ** Message: 21:13:39.414: PackageKit: ignoring field named profile
  ** Message: 21:13:39.414: PackageKit: field is: mpegversion, type: gint
  ** Message: 21:13:39.414: PackageKit: structure: 
gstreamer1(decoder-audio/mpeg)(mpegversion=4)()(64bit)
  ** Message: 21:13:39.414: PackageKit: Codec nice name: H.264 (Main 
Profile) decoder
  ** Message: 21:13:39.414: PackageKit: ignoring field named level
  ** Message: 21:13:39.414: PackageKit: ignoring field named profile
  ** Message: 21:13:39.414: PackageKit: structure: 
gstreamer1(decoder-video/x-h264)()(64bit)
  ** Message: 21:13:39.434: PackageKit: Did not install codec: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.freedesktop.PackageKit was not provided by any .service files
  ** Message: 21:13:39.441: No installation candidate for missing plugins 
found.

  The packagekit.service is defined as:

  $ systemctl cat packagekit.service
  # /usr/lib/systemd/system/packagekit.service
  [Unit]
  Description=PackageKit Daemon
  # PK doesn't know how to do anything on ostree-managed systems;
  # currently the design is to have dedicated daemons like
  # eos-updater and rpm-ostree, and gnome-software talks to those.
  ConditionPathExists=!/run/ostree-booted
  Wants=network-online.target
  
  [Service]
  Type=dbus
  BusName=org.freedesktop.PackageKit
  User=root
  ExecStart=/usr/libexec/packagekitd

  And just to demonstrate packagekit is actually running:

  $ systemctl status packagekit.service
  ● packagekit.service - PackageKit Daemon
   Loaded: loaded (/usr/lib/systemd/system/packagekit.service; static)
   Active: active (running) since Tue 2024-04-09 21:11:35 BST; 2min 23s 
ago
 Main PID: 1565 (packagekitd)
Tasks: 4 (limit: 3864)
   Memory: 6.2M (peak: 6.7M)
  CPU: 180ms
   CGroup: /system.slice/packagekit.service
   └─1565 /usr/libexec/packagekitd
  
  Apr 09 21:11:34 fozzie systemd[1]: Starting packagekit.service - 
PackageKit Daemon...
  Apr 09 21:11:34 fozzie PackageKit[1565]: daemon start
  Apr 09 21:11:35 fozzie systemd[1]: Started packagekit.service - 
PackageKit Daemon.

To manage notifications about this bug go to:
https://bugs.launchpad.net/app-center/+bug/2060730/+subscriptions


-- 
Mailing

[Touch-packages] [Bug 1097467] Re: bash does not fulfill --rcfile option properly

2024-04-11 Thread Dave Jones

Bah, looks like this upload got accidentally dropped by the subsequent
merge for noble. I'll rebase and re-proposed it when I've got some
time...

** Changed in: bash (Ubuntu)
   Status: Fix Committed => Confirmed

** Changed in: bash (Ubuntu)
 Assignee: Dan Bungert (dbungert) => Dave Jones (waveform)

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

Title:
  bash does not fulfill --rcfile option properly

Status in Gnu Bash:
  New
Status in bash package in Ubuntu:
  Confirmed

Bug description:
  I am starting a bash shell using

  $ bash --noprofile --rcfile my-custom-bash-rc-file

  Due to the --rcflag, the newly started bash should *not* execute
  commands from /etc/bash.bashrc. That is at least how I interpret `man
  bash`:

    --rcfile file
    Execute commands from file instead of the system wide 
initialization file /etc/bash.bashrc and the standard personal initial‐
    ization file ~/.bashrc if the shell is interactive (see 
INVOCATION below).

  However, it seems that the commands in /etc/bash.bashrc are in fact
  executed.

  To see/reproduce/diagnose this, on Ubuntu I believe one can just
  invoke bash like this (as the regular user):

  $ touch testrc
  $ env -i bash --noprofile --rcfile testrc

  The expected result would be that nothing special is printed on the
  terminal. However, there is an error message, which is printed from
  /etc/bash.bashrc. The "env -i" causes $HOME to not be set in the
  invoked shell, which in turn triggers the error. The error message is:

  > To run a command as administrator (user "root"), use "sudo ".
  > See "man sudo_root" for details.

  Another way to see this -- without the "env -i" -- is to add  a
  command to /etc/bash.bashrc, such as

  echo HELLO THERE

  To trigger the bug(?), one can then just do

  $ touch testrc
  $ bash --noprofile --rcfile testrc

  The expected result would be that nothing special is shown in the
  terminal. However, it turns out that the string

  HELLO THERE

  is printed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnubash/+bug/1097467/+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 2060693] Re: No welcome/login sound on Ubuntu desktop

2024-04-11 Thread Dave Jones

** Summary changed:

- No login sound on Ubuntu desktop
+ No welcome/login sound on Ubuntu desktop

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

Title:
  No welcome/login sound on Ubuntu desktop

Status in libcanberra package in Ubuntu:
  New

Bug description:
  Under the Ubuntu desktop for Raspberry Pi, for several recent
  releases, the startup sound from the Yaru sound theme has failed to
  play both at the initial setup (from oem-config, where it used to play
  just before language selection), and at the greeter.

  This worked in Jammy (22.04), but on at least mantic (23.10) and the
  forthcoming noble (24.04) (and possibly earlier), this has failed.
  It's not due to a crash in canberra-gtk-play (used to play the sound).
  The only hint that something has failed appears in the oem-config.log:

Failed to play sound: Not available

  Unfortunately there's nothing else in the log that hints at why
  canberra-gtk-play is failing.

  There are several similar bug report, but I doubt they are related
  given their age (e.g. LP: #1002114 relates to ubuntu 12.04 which had a
  very different sound stack and predates the preinstalled desktop
  images).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libcanberra/+bug/2060693/+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 1942260] Re: compress firmware in /lib/firmware

2024-04-10 Thread Dave Jones

This was fixed with version 11 of linux-firmware-raspi in noble; I don't
see a great deal of point in expending the effort to backport this to
mantic, however, so I'll set that to invalid.

** Changed in: linux-firmware-raspi (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: linux-firmware-raspi (Ubuntu Mantic)
   Status: Confirmed => Won't Fix

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

Title:
  compress firmware in /lib/firmware

Status in firmware-sof package in Ubuntu:
  Fix Released
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-firmware-raspi package in Ubuntu:
  Fix Released
Status in firmware-sof source package in Mantic:
  Fix Released
Status in initramfs-tools source package in Mantic:
  Fix Released
Status in linux-firmware source package in Mantic:
  Fix Released
Status in linux-firmware-raspi source package in Mantic:
  Won't Fix

Bug description:
  -- initramfs-tools

  [Impact]

   * linux supports xz compressed linux-firmware which saves disk space.
  In focal, initramfs-tools only knows how to included uncompressed
  firmware files (even when kernel supports loading compressed ones).
  Newer releases of linux-firmware may use compressed firmware files
  only, in such cases it would be nice for focal's initramfs-tools to
  support compressed firmware files in case of partial or incomplete
  upgrades (i.e. linux-firmware force installed or upgraded, without
  newer initramfs-tools). The proposed changes to initramfs-tools are
  backwards and forwards compatible, they prefer to include uncompressed
  firmware files; and if missing, include compressed firmware files in
  their uncompressed form. Thus maintaining compatibility with any
  kernels, irrespective of compressed/uncompressed firmware inputs.

  [Test Plan]

   * Compress all files shipped by linux-firmware with xz

   * Rebuild initrd

   * Check that all the same firmware files are still included in the
  initramfs, in their uncompressed form as before

  [Where problems could occur]

   * This SRU is precautionary to prevent accidental installation of
  compressed linux-firmware from generating incorrect initramfs. It
  should be noted that whilst initramfs-tools would create a compatible
  initramfs with any kernels, pre-v5.3 kernels do not support xz
  compressed firmware files at runtime. Mixing this new initramfs with
  compressed firmwares and pre 5.3 kernels may lead to expectations of
  supporting compressed firmware files with them only working at initrd
  stage and not at runtime.

  [Other Info]
  Original bug report

  Some facts:
   - The linux kernel has supported loading xz compressed firmware since 5.3
   - The size of /lib/firmware in impish is ~650Mb (and growing)
   - The compressed size of firmware could be ~230Mb

  It would be nice to install compressed firmware to save space.

  Here are the plans from the Fedora project:
  https://fedoraproject.org/wiki/Changes/CompressKernelFirmware

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firmware-sof/+bug/1942260/+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 2060730] Re: totem cannot install codecs via packagekit

2024-04-09 Thread Dave Jones

Adding affects packagekit as I've no idea if this is totem's fault or
packagekit's.

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

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

Title:
  totem cannot install codecs via packagekit

Status in packagekit package in Ubuntu:
  New
Status in totem package in Ubuntu:
  New

Bug description:
  While attempting to play a video on Ubuntu noble desktop for raspberry
  pi, totem attempts to locate a package for the H.264 codec but cannot
  find a service providing org.freedesktop.PackageKit. This is strange
  given that packagekit is installed, provides packagekit.service, which
  declares that it provides that name over DBus. Specifically, the
  following is output by totem:

  ** Message: 21:13:39.000: Missing plugin: gstreamer|1.0|totem|MPEG-4 AAC 
decoder|decoder-audio/mpeg, mpegversion=(int)4, level=(string)4, 
base-profile=(string)lc, profile=(string)lc (MPEG-4 AAC decoder)
  ** Message: 21:13:39.000: Missing plugin: gstreamer|1.0|totem|H.264 (Main 
Profile) decoder|decoder-video/x-h264, level=(string)3.1, profile=(string)main 
(H.264 (Main Profile) decoder)
  ** Message: 21:13:39.414: PackageKit: xid = 0
  ** Message: 21:13:39.414: PackageKit: desktop_id = org.gnome.Totem.desktop
  ** Message: 21:13:39.414: PackageKit: Codec nice name: MPEG-4 AAC decoder
  ** Message: 21:13:39.414: PackageKit: ignoring field named level
  ** Message: 21:13:39.414: PackageKit: ignoring field named base-profile
  ** Message: 21:13:39.414: PackageKit: ignoring field named profile
  ** Message: 21:13:39.414: PackageKit: field is: mpegversion, type: gint
  ** Message: 21:13:39.414: PackageKit: structure: 
gstreamer1(decoder-audio/mpeg)(mpegversion=4)()(64bit)
  ** Message: 21:13:39.414: PackageKit: Codec nice name: H.264 (Main 
Profile) decoder
  ** Message: 21:13:39.414: PackageKit: ignoring field named level
  ** Message: 21:13:39.414: PackageKit: ignoring field named profile
  ** Message: 21:13:39.414: PackageKit: structure: 
gstreamer1(decoder-video/x-h264)()(64bit)
  ** Message: 21:13:39.434: PackageKit: Did not install codec: 
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name 
org.freedesktop.PackageKit was not provided by any .service files
  ** Message: 21:13:39.441: No installation candidate for missing plugins 
found.

  The packagekit.service is defined as:

  $ systemctl cat packagekit.service
  # /usr/lib/systemd/system/packagekit.service
  [Unit]
  Description=PackageKit Daemon
  # PK doesn't know how to do anything on ostree-managed systems;
  # currently the design is to have dedicated daemons like
  # eos-updater and rpm-ostree, and gnome-software talks to those.
  ConditionPathExists=!/run/ostree-booted
  Wants=network-online.target
  
  [Service]
  Type=dbus
  BusName=org.freedesktop.PackageKit
  User=root
  ExecStart=/usr/libexec/packagekitd

  And just to demonstrate packagekit is actually running:

  $ systemctl status packagekit.service
  ● packagekit.service - PackageKit Daemon
   Loaded: loaded (/usr/lib/systemd/system/packagekit.service; static)
   Active: active (running) since Tue 2024-04-09 21:11:35 BST; 2min 23s 
ago
 Main PID: 1565 (packagekitd)
Tasks: 4 (limit: 3864)
   Memory: 6.2M (peak: 6.7M)
  CPU: 180ms
   CGroup: /system.slice/packagekit.service
   └─1565 /usr/libexec/packagekitd
  
  Apr 09 21:11:34 fozzie systemd[1]: Starting packagekit.service - 
PackageKit Daemon...
  Apr 09 21:11:34 fozzie PackageKit[1565]: daemon start
  Apr 09 21:11:35 fozzie systemd[1]: Started packagekit.service - 
PackageKit Daemon.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/2060730/+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 2037015] Re: Screen corruption of slides during install on Raspberry Pi 4

2024-04-09 Thread Dave Jones

There's an intriguingly different style of corruption in the noble
images on the Pi 5. It's still just on the installer's slides, but it's
more ... "chunky"? I'll attach a photo...

** Attachment added: "slide-corruption-2.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/2037015/+attachment/5762908/+files/slide-corruption-2.jpg

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

Title:
  Screen corruption of slides during install on Raspberry Pi 4

Status in mesa package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  Confirmed

Bug description:
  During the initial configuration of the Ubuntu Desktop for Raspberry
  Pi (the oem-config process, derived from ubiquity), on the Mantic beta
  images, after the various pages of information have been filled out
  and the process moves onto configuration, the "slide deck" that is
  usually displayed during the process appeared corrupted as if a
  horizontal stride were incorrectly set somewhere.

  I'm attached a photo of the screen (as, while I could take a
  screenshot during the process, it evidently wasn't saved somewhere
  persistent).

  I originally thought this might be a regression of LP: #1924251 as the
  corruption in the window looks very similar (incorrect horizontal
  stride causing "banding"), but I tested the embedded browser (via the
  help system) after completing setup and it worked perfectly so that's
  *probably* unrelated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2037015/+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 2060693] [NEW] No login sound on Ubuntu desktop

2024-04-09 Thread Dave Jones

Public bug reported:

Under the Ubuntu desktop for Raspberry Pi, for several recent releases,
the startup sound from the Yaru sound theme has failed to play both at
the initial setup (from oem-config, where it used to play just before
language selection), and at the greeter.

This worked in Jammy (22.04), but on at least mantic (23.10) and the
forthcoming noble (24.04) (and possibly earlier), this has failed. It's
not due to a crash in canberra-gtk-play (used to play the sound). The
only hint that something has failed appears in the oem-config.log:

  Failed to play sound: Not available

Unfortunately there's nothing else in the log that hints at why
canberra-gtk-play is failing.

There are several similar bug report, but I doubt they are related given
their age (e.g. LP: #1002114 relates to ubuntu 12.04 which had a very
different sound stack and predates the preinstalled desktop images).

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

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

Title:
  No login sound on Ubuntu desktop

Status in libcanberra package in Ubuntu:
  New

Bug description:
  Under the Ubuntu desktop for Raspberry Pi, for several recent
  releases, the startup sound from the Yaru sound theme has failed to
  play both at the initial setup (from oem-config, where it used to play
  just before language selection), and at the greeter.

  This worked in Jammy (22.04), but on at least mantic (23.10) and the
  forthcoming noble (24.04) (and possibly earlier), this has failed.
  It's not due to a crash in canberra-gtk-play (used to play the sound).
  The only hint that something has failed appears in the oem-config.log:

Failed to play sound: Not available

  Unfortunately there's nothing else in the log that hints at why
  canberra-gtk-play is failing.

  There are several similar bug report, but I doubt they are related
  given their age (e.g. LP: #1002114 relates to ubuntu 12.04 which had a
  very different sound stack and predates the preinstalled desktop
  images).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libcanberra/+bug/2060693/+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 2057927] Re: lxd vga console throws "Operation not permitted" error

2024-03-29 Thread Dave Jones

I see a basically identical message (and dmesg apparmor output) with
"lxc profile edit default":

  unshare: write failed /proc/self/uid_map: Operation not permitted

And the dmesg entry:

  [  194.625507] audit: type=1400 audit(1711709095.424:293):
apparmor="DENIED" operation="capable" class="cap"
profile="unprivileged_userns" pid=6885 comm="unshare" capability=21
capname="sys_admin"

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

Title:
  lxd vga console throws "Operation not permitted" error

Status in apparmor package in Ubuntu:
  Confirmed
Status in lxd package in Ubuntu:
  Confirmed

Bug description:
  Since I upgraded to Noble the lxd vga console doesn't work anymore. I
  am using the lxd latest/stable snap (5.20-f3dd836). When trying to
  attach a vga console to an lxd vm I get:

  unshare: write failed /proc/self/uid_map: Operation not permitted

  It seems to be related to apparmor, I can see a matching DENIAL
  message in dmesg:

  [ 4735.233989] audit: type=1400 audit(1710419600.517:300):
  apparmor="DENIED" operation="capable" class="cap"
  profile="unprivileged_userns" pid=13157 comm="unshare" capability=21
  capname="sys_admin"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2057927/+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 2036358] Re: systemd wait-online now times out after jammy and lunar upgrade

2024-03-26 Thread Dave Jones

> If you have a bunch of unmanaged interfaces, then you should use a
> drop-in configuration to pass the --any flag to
> systemd-networkd-wait-online:
> 
> cat > /etc/systemd/system/systemd-networkd-wait-online.service.d/any.conf << 
> EOF
> [Service]
> ExecStart=
> ExecStart=/lib/systemd/systemd-networkd-wait-online --any
> EOF
> 
> This makes it so that systemd-networkd-wait-online will return success once 
> at least one interface becomes configured.

Unfortunately this doesn't appear to work. I've tried this on the
current noble dailies (which also suffer the 2 minute boot delay on
the server images due to this issue). The default netplan config is
simply:

  network:
version: 2
ethernets:
  eth0:
dhcp4: true
optional: true

This displays the issue, even with --any presumably because wlan0 is
unmanaged so networkctl reports the online state is "unknown" (even
when eth0 is happily configured and routable).

I attempting making wlan0 "managed" but optional. This requires a
mandatory access point to be defined to conform to the YAML schema, so
I added a fake one (I should open a separate issue for this because I
shouldn't have to make up access points just to mark an interface
optional):

  network:
version: 2
ethernets:
  eth0:
dhcp4: true
optional: true
wifis:
  wlan0:
dhcp4: true
optional: true
access-points:
  foo:
password: foobarbaz

Unfortunately this also displays the issue. This time wlan0 is
managed, but "configuring" and the online state is still "unknown". So
far as I can tell, the --any option doesn't match the behaviour
claimed in the man-page (i.e. "exits with success when at least one
interface becomes online").

> There is no workaround for this with the stock netplan config on
> raspberry pi, which trips this bug. But you can customize
> /etc/netplan/ on your system to mark your expected/required network
> interfaces as "optional: false" (which is the default if
> unspecified); AIUI that would avoid this issue with
> systemd-networkd.

This *does* work ... assuming the Pi actually has a network interface.
If the Pi is networkless, it's unfortunately doomed to the 2 minute
delay still. And obviously I don't want to make eth0 mandatory by
default in the images (which would break the 3A+ and Zero 2W, which
lack eth0 entirely).

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

Title:
  systemd wait-online now times out after jammy and lunar upgrade

Status in systemd package in Ubuntu:
  Invalid
Status in systemd source package in Jammy:
  Fix Released
Status in systemd source package in Lunar:
  Fix Released

Bug description:
  [NOTE]

  If you are running a desktop system and you see this issue, you should
  run:

  $ systemctl disable --now systemd-networkd.service

  This will disable systemd-networkd and associated units, including
  systemd-networkd-wait-online.service. NetworkManager and systemd-
  networkd should not be running at the same time. On desktop,
  NetworkManager is the default network stack.

  [Impact]

  When all interfaces are "not required for online", e.g. when they are
  marked "optional: true" in netplan, systemd-networkd-wait-online will
  timeout. Or, in other words, systemd-networkd-wait-online will timeout
  even though all interfaces are ignored, hence none of them will ever
  be marked as "ready." Depending on what units depend on network-
  online.target, this can delay boot by 120 seconds (the default timeout
  for systemd-networkd-wait-online).

  [Test Plan]

  1. Create a new LXD container. These instructions assume jammy is the
  release, but the same can be done for lunar.

  $ lxc launch ubuntu-daily:jammy jammy
  $ lxc exec jammy bash

  2. Once in the container, modify the default /etc/netplan/10-lxc.yaml
  so that eth0 is configured with "optional: true":

  $ vi /etc/netplan/50-cloud-init.yaml # Use whatever editor you like
  $ cat /etc/netplan/50-cloud-init.yaml
  network:
    version: 2
    ethernets:
  eth0:
    dhcp4: true
    dhcp-identifier: mac
    optional: true

  3. Re-generate and apply the netplan configuration.

  $ netplan generate
  $ netplan apply

  4. Manually run systemd-networkd-wait-online, and observe that all
  links are ignored, and the command times out:

  $ SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd-wait-online 
--timeout=10
  Found link lo(1)
  Found link eth0(19)
  lo: link is ignored
  eth0: link is ignored
  Timeout occurred while waiting for network connectivity.

  [Where problems could occur]

  This patch partially re-instates a patch remove in bug 1982218.
  However, instead of exiting if all links are unmanaged, we exit if all
  links are ignored in manager_configured(). If the patch was wrong, we
  may re-introduce bug 1982218, so as part of this

[Touch-packages] [Bug 2055351] Re: [amdgpu] Firefox and Chromium browser windows are corrupt in Xorg

2024-03-06 Thread Dave Zielinski

This looks like it's the same issue as this:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2004532

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

Title:
  [amdgpu] Firefox and Chromium browser windows are corrupt in Xorg

Status in mesa package in Ubuntu:
  New
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  I downloaded the 22.04.4 iso and did a fresh install on an AMD Athlon 200GE 
using built-in graphics.
  (Radeon™ Vega 3 Graphics)

  Firefox and Chromium browsers had their windows corrupted to the point
  where they were unreadable.

  I think this is an xorg bug, because when I installed Wayland and
  logged in with a Wayland session, the browsers displayed correctly.

  Same behaviour with an Athlon 220GE.

  KDE or Ubuntu's Gnome desktop made no difference - it seemed to be xorg vs 
Wayland that was the critical difference.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. PRIME Motherboard [1043:876b]
  InstallationDate: Installed on 2024-02-26 (3 days ago)
  InstallationMedia: Kubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240216.1)
  MachineType: System manufacturer System Product Name
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic 
root=UUID=7e6c3c76-1566-4670-97ab-3755e9a04b18 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
  Tags:  jammy wayland-session ubuntu
  Uname: Linux 6.5.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 09/04/2023
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 6210
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME A320M-K
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6210:bd09/04/2023:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroRelease: Ubuntu 22.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev cb) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. PRIME Motherboard [1043:876b]
  InstallationDate: Installed on 2024-02-26 (3 days ago)
  InstallationMedia: Kubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240216.1)
  MachineType: System manufacturer System Product Name
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-21-generic 
root=UUID=7e6c3c76-1566-4670-97ab-3755e9a04b18 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
  Tags:  jammy ubuntu
  Uname: Linux 6.5.0-21-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

[Touch-packages] [Bug 2054683] Re: Please merge lvm2 2.03.16-3 from Debian unstable.

Created MP as suggested by Bryce on the last merge (LP: #2020464)

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

Title:
  Please merge lvm2 2.03.16-3 from Debian unstable.

Status in lvm2 package in Ubuntu:
  New

Bug description:
  Please merge lvm2 2.03.16-3 from Debian unstable.

  Updated changelog and diff against Debian unstable to be attached
  below.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/2054683/+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 2054683] [NEW] Please merge lvm2 2.03.16-3 from Debian unstable.

Public bug reported:

Please merge lvm2 2.03.16-3 from Debian unstable.

Updated changelog and diff against Debian unstable to be attached below.

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

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

Title:
  Please merge lvm2 2.03.16-3 from Debian unstable.

Status in lvm2 package in Ubuntu:
  New

Bug description:
  Please merge lvm2 2.03.16-3 from Debian unstable.

  Updated changelog and diff against Debian unstable to be attached
  below.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/2054683/+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 2054683] Re: Please merge lvm2 2.03.16-3 from Debian unstable.

Test builds may be found in ppa:waveform/lvm2
(https://launchpad.net/~waveform/+archive/ubuntu/lvm2)

** Merge proposal linked:
   
https://code.launchpad.net/~waveform/ubuntu/+source/lvm2/+git/lvm2/+merge/461016

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

Title:
  Please merge lvm2 2.03.16-3 from Debian unstable.

Status in lvm2 package in Ubuntu:
  New

Bug description:
  Please merge lvm2 2.03.16-3 from Debian unstable.

  Updated changelog and diff against Debian unstable to be attached
  below.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/2054683/+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 2054683] Re: Please merge lvm2 2.03.16-3 from Debian unstable.

Attaching patch against Debian unstable. For ease of review, relevant
commits and tags have been pushed to the following repository:

https://code.launchpad.net/~waveform/ubuntu/+source/lvm2/+git/lvm2

Specifically:

* logical/2.03.16-2ubuntu1 represents our split-out delta on
  top of old/debian (2.03.16-2)
* logical/2.03.16-3ubuntu1 represents our rebased delta on
  top of new/debian (2.03.16-3)
* merge/2.03.16-3ubuntu1 adds changelog and maintainer
  changes on top of logical/2.03.16-3ubuntu1

Hence, the following command may produce output useful to the purposes
of review:

git range-diff --creation-factor=100
old/debian..logical/2.03.16-2ubuntu1
new/debian..logical/2.03.16-3ubuntu1


** Patch added: "1-2054683.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/2054683/+attachment/5748479/+files/1-2054683.debdiff

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

Title:
  Please merge lvm2 2.03.16-3 from Debian unstable.

Status in lvm2 package in Ubuntu:
  New

Bug description:
  Please merge lvm2 2.03.16-3 from Debian unstable.

  Updated changelog and diff against Debian unstable to be attached
  below.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/2054683/+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 2054517] Re: webkit2gtk renders as corrupt in Raspberry Pi Xorg sessions

2024-02-21 Thread Dave Jones

This may be a duplicate of LP: #2037015 -- we saw this on mantic first,
then noble, in the oem-config process (the first-time setup wizard).
Previously it *didn't* affect jammy, but I'm currently running through
the ISO tests for the jammy .4 release and it's cropped up there now as
well.

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

Title:
  webkit2gtk renders as corrupt in Raspberry Pi Xorg sessions

Status in mesa package in Ubuntu:
  New
Status in webkit2gtk package in Ubuntu:
  New

Bug description:
  webkit2gtk renders as corrupt in Raspberry Pi Xorg sessions. Assuming
  it doesn't crash first.

  You first see the corruption in the initial setup wizard on first boot
  of noble-preinstalled-desktop-arm64+raspi.img.xz but the same
  corruption is then visible in the Help app on Xorg.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: libwebkit2gtk-4.1-0 2.43.3-1
  ProcVersionSignature: Ubuntu 6.5.0-1005.7-raspi 6.5.3
  Uname: Linux 6.5.0-1005-raspi aarch64
  ApportVersion: 2.27.0-0ubuntu7
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CloudArchitecture: aarch64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  Date: Wed Feb 21 14:38:56 2024
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: webkit2gtk
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2054517/+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 2039104] Re: ubuntu-settings must drop ubuntu-raspi-settings* from debian/control

2024-01-25 Thread Dave Jones

Tested on mantic install, and as Robie suggested, performed binary
debdiff against old versions to ensure only change was the version
number. Marking verification done.

** Tags removed: verification-needed-mantic
** Tags added: verification-done-mantic

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

Title:
  ubuntu-settings must drop ubuntu-raspi-settings* from debian/control

Status in ubuntu-settings package in Ubuntu:
  Fix Released
Status in ubuntu-settings source package in Mantic:
  Fix Committed

Bug description:
  [SRU Justification]

  In response to LP: #2038964 and due to the timing we have forked
  ubuntu-raspi-settings into a separate source package.

  ubuntu-settings must therefore be updated to drop ubuntu-raspi-
  settings* from debian/control as otherwise binary builds of the
  package will be rejected by the archive (if the version number is <=
  23.10.6) or will wrongly supersede the fixes that have just been
  uploaded to mantic (if the version number is > 23.10.6).

  [Test case]
  No testing is planned beyond any autopkgtests which may be none (the package 
itself doesn't have any).  This should not be released to -updates on its own, 
but should be staged in -proposed so any future SRUs needed don't fail to copy 
due to out-of-date packages.

  [Where problems may occur]
  It is unlikely but possible that the removal of the raspi binary package from 
this source package will have inadvertently modified the contents of the other 
remaining binary packages.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2039104/+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 2039873] Re: [SRU] liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases

2024-01-24 Thread Dave Jones

** Summary changed:

- liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases
+ [SRU] liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases

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

Title:
  [SRU] liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later
  releases

Status in lxc package in Ubuntu:
  Fix Committed
Status in lxc source package in Jammy:
  Confirmed
Status in lxc source package in Mantic:
  Confirmed
Status in lxc source package in Noble:
  Fix Committed

Bug description:
  [ Impact ]

  LXC 5.0.0 was built with LXC_DEVEL=1 set for Jammy. But for release
  build we should have LXC_DEVEL=0.

  LXC_DEVEL is a variable that appears in the /usr/include/lxc/version.h
  and then can be (and actually it is) used by other projects to detect
  if liblxc-dev is a development build or stable.

  Having LXC_DEVEL=1 makes problems for the users who want to build projects 
those are depend on liblxc
  from source (for example, LXD, go-lxc: 
https://github.com/canonical/lxd/pull/12420).

  Q: Why it was not a problem for so long?
  A: Because LXC API was stable for a long time, but recently we have extended 
liblxc API (https://github.com/lxc/lxc/pull/4260) and dependant package go-lxc 
was updated too (https://github.com/lxc/go-lxc/pull/166).
  This change was developed properly to be backward compatible with the old 
versions of liblxc. But, there is a problem. If LXC_DEVEL=1 then the macro 
check VERSION_AT_LEAST 
(https://github.com/lxc/go-lxc/blob/ccae595aa49e779f7ecc9250329967aa546acd31/lxc-binding.h#L7)
 is disabled. That's why we should *not* have LXC_DEVEL=1 for *any* release 
build of LXC.

  [ Test Plan ]

  Install liblxc-dev package and check /usr/include/lxc/version.h file
  LXC_DEVEL should be 0

  [ Where problems could occur ]

  Theoretically, build of a software which depends on liblxc-dev may start to 
fail
  if it assumes that LXC_DEVEL is 1.

  [ Other Info ]

  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2039873/+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 2039873] Re: liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases

2024-01-24 Thread Dave Jones

Noble's now in proposed and looks to have built successfully so I'll
mark that Fix Committed. I'm just uploading the mantic and jammy SRUs
(the jammy one took a little longer as the fix is slightly different
there; appears the build system changed between jammy and mantic).

** Changed in: lxc (Ubuntu Noble)
   Status: Confirmed => Fix Committed

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

Title:
  liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later
  releases

Status in lxc package in Ubuntu:
  Fix Committed
Status in lxc source package in Jammy:
  Confirmed
Status in lxc source package in Mantic:
  Confirmed
Status in lxc source package in Noble:
  Fix Committed

Bug description:
  [ Impact ]

  LXC 5.0.0 was built with LXC_DEVEL=1 set for Jammy. But for release
  build we should have LXC_DEVEL=0.

  LXC_DEVEL is a variable that appears in the /usr/include/lxc/version.h
  and then can be (and actually it is) used by other projects to detect
  if liblxc-dev is a development build or stable.

  Having LXC_DEVEL=1 makes problems for the users who want to build projects 
those are depend on liblxc
  from source (for example, LXD, go-lxc: 
https://github.com/canonical/lxd/pull/12420).

  Q: Why it was not a problem for so long?
  A: Because LXC API was stable for a long time, but recently we have extended 
liblxc API (https://github.com/lxc/lxc/pull/4260) and dependant package go-lxc 
was updated too (https://github.com/lxc/go-lxc/pull/166).
  This change was developed properly to be backward compatible with the old 
versions of liblxc. But, there is a problem. If LXC_DEVEL=1 then the macro 
check VERSION_AT_LEAST 
(https://github.com/lxc/go-lxc/blob/ccae595aa49e779f7ecc9250329967aa546acd31/lxc-binding.h#L7)
 is disabled. That's why we should *not* have LXC_DEVEL=1 for *any* release 
build of LXC.

  [ Test Plan ]

  Install liblxc-dev package and check /usr/include/lxc/version.h file
  LXC_DEVEL should be 0

  [ Where problems could occur ]

  Theoretically, build of a software which depends on liblxc-dev may start to 
fail
  if it assumes that LXC_DEVEL is 1.

  [ Other Info ]

  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2039873/+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 2039873] Re: liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases

2024-01-22 Thread Dave Jones

Okay, good enough for me -- I'll sponsor my aforementioned branch for
noble and have a look at the mantic and jammy SRUs tomorrow, assuming
everything builds happily in noble.

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

Title:
  liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later
  releases

Status in lxc package in Ubuntu:
  Confirmed
Status in lxc source package in Jammy:
  Confirmed
Status in lxc source package in Mantic:
  Confirmed
Status in lxc source package in Noble:
  Confirmed

Bug description:
  [ Impact ]

  LXC 5.0.0 was built with LXC_DEVEL=1 set for Jammy. But for release
  build we should have LXC_DEVEL=0.

  LXC_DEVEL is a variable that appears in the /usr/include/lxc/version.h
  and then can be (and actually it is) used by other projects to detect
  if liblxc-dev is a development build or stable.

  Having LXC_DEVEL=1 makes problems for the users who want to build projects 
those are depend on liblxc
  from source (for example, LXD, go-lxc: 
https://github.com/canonical/lxd/pull/12420).

  Q: Why it was not a problem for so long?
  A: Because LXC API was stable for a long time, but recently we have extended 
liblxc API (https://github.com/lxc/lxc/pull/4260) and dependant package go-lxc 
was updated too (https://github.com/lxc/go-lxc/pull/166).
  This change was developed properly to be backward compatible with the old 
versions of liblxc. But, there is a problem. If LXC_DEVEL=1 then the macro 
check VERSION_AT_LEAST 
(https://github.com/lxc/go-lxc/blob/ccae595aa49e779f7ecc9250329967aa546acd31/lxc-binding.h#L7)
 is disabled. That's why we should *not* have LXC_DEVEL=1 for *any* release 
build of LXC.

  [ Test Plan ]

  Install liblxc-dev package and check /usr/include/lxc/version.h file
  LXC_DEVEL should be 0

  [ Where problems could occur ]

  Theoretically, build of a software which depends on liblxc-dev may start to 
fail
  if it assumes that LXC_DEVEL is 1.

  [ Other Info ]

  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2039873/+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 2039873] Re: liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases

2024-01-22 Thread Dave Jones

I had a little time to look over this again in my patch-pilot shift. I
agree it's almost certainly best to just get LXC_DEVEL set correctly
quickly. Andreas' suggested branch is a good start, but I agree with the
critique that the DEP-8 test should be checking the installed headers
rather than the built source. Due to this, it's probably also best if
the test is named something other than "build". Also, I agree it
shouldn't be marked "superficial".

I've pushed a few commits on top of Andreas' to another clone here,
which also fixes a build-failure on noble (lib/systemd instead of
usr/lib/systemd in d/lxc-utils.install):

https://code.launchpad.net/~waveform/ubuntu/+source/lxc/+git/lxc

I've tested the DEP-8 passes with the branch, and crucially that it
fails when the LXC_DEVEL fix is reverted (which it does). If this looks
sane to someone else, I'm happy to sponsor this into noble (and start
SRU proceedings for mantic and jammy).

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

Title:
  liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later
  releases

Status in lxc package in Ubuntu:
  Confirmed
Status in lxc source package in Jammy:
  Confirmed
Status in lxc source package in Mantic:
  Confirmed
Status in lxc source package in Noble:
  Confirmed

Bug description:
  [ Impact ]

  LXC 5.0.0 was built with LXC_DEVEL=1 set for Jammy. But for release
  build we should have LXC_DEVEL=0.

  LXC_DEVEL is a variable that appears in the /usr/include/lxc/version.h
  and then can be (and actually it is) used by other projects to detect
  if liblxc-dev is a development build or stable.

  Having LXC_DEVEL=1 makes problems for the users who want to build projects 
those are depend on liblxc
  from source (for example, LXD, go-lxc: 
https://github.com/canonical/lxd/pull/12420).

  Q: Why it was not a problem for so long?
  A: Because LXC API was stable for a long time, but recently we have extended 
liblxc API (https://github.com/lxc/lxc/pull/4260) and dependant package go-lxc 
was updated too (https://github.com/lxc/go-lxc/pull/166).
  This change was developed properly to be backward compatible with the old 
versions of liblxc. But, there is a problem. If LXC_DEVEL=1 then the macro 
check VERSION_AT_LEAST 
(https://github.com/lxc/go-lxc/blob/ccae595aa49e779f7ecc9250329967aa546acd31/lxc-binding.h#L7)
 is disabled. That's why we should *not* have LXC_DEVEL=1 for *any* release 
build of LXC.

  [ Test Plan ]

  Install liblxc-dev package and check /usr/include/lxc/version.h file
  LXC_DEVEL should be 0

  [ Where problems could occur ]

  Theoretically, build of a software which depends on liblxc-dev may start to 
fail
  if it assumes that LXC_DEVEL is 1.

  [ Other Info ]

  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2039873/+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 2039873] Re: liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later releases

2023-12-11 Thread Dave Jones

Thanks very much for the updated debdiff. There's a lot of changes here
to look at and unfortunately I've run out of time looking through it all
during my patch-pilot shift, but here's what I've got so far:

The major thing that I think needs correction is that this patch is
built on top of ubuntu/noble-devel by importing the upstream 5.0.3, but
what Stéphane suggested in comment 14 was to take the Debian upstream
(currently 5.0.3-2) and build on top of that. In this case, the commits
in the repo would be based on debian/sid rather than ubuntu/noble-devel.
This would ensure we incorporate the changes Debian has placed on top of
lxc, as well as our own (and means in future we can follow the git-
ubuntu merge process for this package).

The proposed changes also include package renames (which will be
necessary if we're basing off the upstream Debian version). As far as I
can tell they look sane but I haven't dug deep into this bit yet (it's
something I always need to read the policy guides and manuals for!).

The requested autopkgtest to ensure LXC_DEVEL==0 is present, and looks
good.

I have to dash to an appointment now, but I'll try and add some more
notes later this evening.

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

Title:
  liblxc-dev was built with LXC_DEVEL=1 in Ubuntu 22.04 and later
  releases

Status in lxc package in Ubuntu:
  Confirmed

Bug description:
  [ Impact ]

  LXC 5.0.0 was built with LXC_DEVEL=1 set for Jammy. But for release
  build we should have LXC_DEVEL=0.

  LXC_DEVEL is a variable that appears in the /usr/include/lxc/version.h
  and then can be (and actually it is) used by other projects to detect
  if liblxc-dev is a development build or stable.

  Having LXC_DEVEL=1 makes problems for the users who want to build projects 
those are depend on liblxc
  from source (for example, LXD, go-lxc: 
https://github.com/canonical/lxd/pull/12420).

  Q: Why it was not a problem for so long?
  A: Because LXC API was stable for a long time, but recently we have extended 
liblxc API (https://github.com/lxc/lxc/pull/4260) and dependant package go-lxc 
was updated too (https://github.com/lxc/go-lxc/pull/166).
  This change was developed properly to be backward compatible with the old 
versions of liblxc. But, there is a problem. If LXC_DEVEL=1 then the macro 
check VERSION_AT_LEAST 
(https://github.com/lxc/go-lxc/blob/ccae595aa49e779f7ecc9250329967aa546acd31/lxc-binding.h#L7)
 is disabled. That's why we should *not* have LXC_DEVEL=1 for *any* release 
build of LXC.

  [ Test Plan ]

  Install liblxc-dev package and check /usr/include/lxc/version.h file
  LXC_DEVEL should be 0

  [ Where problems could occur ]

  Theoretically, build of a software which depends on liblxc-dev may start to 
fail
  if it assumes that LXC_DEVEL is 1.

  [ Other Info ]

  -

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/2039873/+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 1951586] Re: Need option to specify wifi regulatory domain

2023-11-16 Thread Dave Jones

Setting network-manager back to confirmed as I think the case is made
that this is an issue, despite upstream having reservations about
whether network-manager is quite the right place for this particular
setting. Also setting netplan.io in jammy to fix released as 0.105 was
back-ported there quite a while ago now and the current (22.04.3) image
should support setting this at first-boot. Setting kinetic to won't fix
(as it's EOL).

** Changed in: network-manager (Ubuntu Kinetic)
   Status: Incomplete => Won't Fix

** Changed in: network-manager (Ubuntu Jammy)
   Status: Incomplete => Confirmed

** Changed in: network-manager (Ubuntu)
   Status: Incomplete => Confirmed

** Changed in: netplan.io (Ubuntu Jammy)
   Status: Triaged => Fix Released

** Changed in: netplan
 Assignee: Lukas Märdian (slyon) => (unassigned)

** Also affects: network-manager (Ubuntu Lunar)
   Importance: Undecided
   Status: New

** Also affects: netplan.io (Ubuntu Lunar)
   Importance: Undecided
   Status: New

** Also affects: network-manager (Ubuntu Noble)
   Importance: Low
   Status: Confirmed

** Also affects: netplan.io (Ubuntu Noble)
   Importance: Medium
   Status: Fix Released

** Also affects: network-manager (Ubuntu Mantic)
   Importance: Undecided
   Status: New

** Also affects: netplan.io (Ubuntu Mantic)
   Importance: Undecided
   Status: New

** Changed in: netplan.io (Ubuntu Lunar)
   Status: New => Fix Released

** Changed in: netplan.io (Ubuntu Mantic)
   Status: New => Fix Released

** Changed in: network-manager (Ubuntu Lunar)
   Importance: Undecided => Low

** Changed in: network-manager (Ubuntu Lunar)
   Status: New => Confirmed

** Changed in: network-manager (Ubuntu Mantic)
   Importance: Undecided => Low

** Changed in: network-manager (Ubuntu Mantic)
   Status: New => Confirmed

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

Title:
  Need option to specify wifi regulatory domain

Status in cloud-init:
  Invalid
Status in netplan:
  Fix Released
Status in NetworkManager:
  New
Status in netplan.io package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Confirmed
Status in netplan.io source package in Jammy:
  Fix Released
Status in network-manager source package in Jammy:
  Confirmed
Status in netplan.io source package in Kinetic:
  Fix Released
Status in network-manager source package in Kinetic:
  Won't Fix
Status in netplan.io source package in Lunar:
  Fix Released
Status in network-manager source package in Lunar:
  Confirmed
Status in netplan.io source package in Mantic:
  Fix Released
Status in network-manager source package in Mantic:
  Confirmed
Status in netplan.io source package in Noble:
  Fix Released
Status in network-manager source package in Noble:
  Confirmed

Bug description:
  It would be nice if netplan offered an option to specify the wifi
  regulatory domain (country code).

  
  For devices such as the Raspberry Pi you are currently advertising that users 
can simply setup Ubuntu Server headless by putting the wifi configuration 
details in cloudinit/netplan's "network-config" on the FAT partition of the SD 
card: 
https://ubuntu.com/tutorials/how-to-install-ubuntu-on-your-raspberry-pi#3-wifi-or-ethernet
  But an option to set the wifi country code there does not seem to exist, so 
may not work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1951586/+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 1924251] Re: Embedded browser display corruption under Wayland on Pi desktop

2023-11-15 Thread Dave Jones

This has been fixed for a couple of releases now (since lunar I
believe), and if I recall correctly the issue was indeed the wpe backend
mentioned in comment 17. That would suggest this should be "invalid" for
gtk and yelp, and "fix released" for webkit2gtk.

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

Title:
  Embedded browser display corruption under Wayland on Pi desktop

Status in gtk+3.0 package in Ubuntu:
  Incomplete
Status in webkit2gtk package in Ubuntu:
  Incomplete
Status in yelp package in Ubuntu:
  Incomplete

Bug description:
  On the jammy Pi desktop, under a wayland session, the body of a window
  containing an HTML renderer (e.g. help text or a login page) displays
  corruption.

  These reproduction cases may not be entirely reliable given that
  *some* pages appear to render correctly, but I'll include a couple in
  the hopes of making it reliably reproducible:

  1. Open the Lights Off game
  2. Select "Help" from the menu
  3. In the help window that appears, select any link

  "Basics", "Rules", and "Strategy" all reliably reproduce the issue for
  me, but "Help Translate" doesn't so you may need to click around some
  links until the corruption appears -- however, once it does even
  navigating back to the prior page which rendered happily now displays
  the same corruption.

  Another reproduction case:

  1. Open the Settings application
  2. Select the Online Applications option from the left
  3. Select the Google entry in the list
  4. The login window that appears always displays corruption for me

  The Microsoft option always reliably corrupts for me, but the Facebook
  one doesn't so again I wonder how reproducible this may be for others
  (might be worth trying several options if the first doesn't display
  corruption).

  The corruption appears in the form of "shredded" content as if a
  horizontal stride is set incorrectly somewhere, but only appears in
  the body of the window; the window decorations are unaffected. I'll
  attach a screenshot of the corrupted help window to illustrate.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1924251/+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 1877194] Re: switch-on-connect mistakes startup for USB hotplug, so seemingly ignores the old default device on reboot

2023-11-15 Thread Dave Jones

** Changed in: pulseaudio (Ubuntu)
 Assignee: Dave Jones (waveform) => (unassigned)

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

Title:
  switch-on-connect mistakes startup for USB hotplug, so seemingly
  ignores the old default device on reboot

Status in PulseAudio:
  New
Status in pulseaudio package in Ubuntu:
  Triaged
Status in ubuntu-settings package in Ubuntu:
  Invalid
Status in pulseaudio source package in Jammy:
  Confirmed
Status in ubuntu-settings source package in Jammy:
  Invalid
Status in pulseaudio source package in Kinetic:
  Won't Fix
Status in ubuntu-settings source package in Kinetic:
  Invalid

Bug description:
  Similar to:
  https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570

  Only difference is that it does not reset to HDMI output, but to one
  of my USB-outputs. It does not respect the change I made after reboot.

  In short:
  1. Boot system
  2. "Analogue Output - RODE NT-USB" is selected by default. I want to use 
"Line Out - Built-in Audio", which I choose.
  3. Reboot.
  4 Output device is now back to "Analogue Output - RODE NT-USB".

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  marcus 1604 F pulseaudio
   /dev/snd/controlC0:  marcus 1604 F pulseaudio
   /dev/snd/controlC1:  marcus 1604 F pulseaudio
   /dev/snd/pcmC1D0c:   marcus 1604 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  6 23:40:08 2020
  InstallationDate: Installed on 2020-05-06 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/27/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3703
  dmi.board.asset.tag: Default string
  dmi.board.name: MAXIMUS VIII HERO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3703:bd12/27/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1877194/+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 1097467] Re: bash does not fulfill --rcfile option properly

2023-11-14 Thread Dave Jones

Doh, I always forget something...

** Patch added: "1097467-2.debdiff"

https://bugs.launchpad.net/gnubash/+bug/1097467/+attachment/5719318/+files/1097467-2.debdiff

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

Title:
bash does not fulfill --rcfile option properly

Status in Gnu Bash:
New
Status in bash package in Ubuntu:
Confirmed

Bug description:
I am starting a bash shell using

$ bash --noprofile --rcfile my-custom-bash-rc-file

Due to the --rcflag, the newly started bash should *not* execute
commands from /etc/bash.bashrc. That is at least how I interpret `man
bash`:

However, it seems that the commands in /etc/bash.bashrc are in fact
executed.

To see/reproduce/diagnose this, on Ubuntu I believe one can just
invoke bash like this (as the regular user):

$ touch testrc
$ env -i bash --noprofile --rcfile testrc

> To run a command as administrator (user "root"), use "sudo ".
> See "man sudo_root" for details.

Another way to see this -- without the "env -i" -- is to add a
command to /etc/bash.bashrc, such as

echo HELLO THERE

To trigger the bug(?), one can then just do

$ touch testrc
$ bash --noprofile --rcfile testrc

The expected result would be that nothing special is shown in the
terminal. However, it turns out that the string

HELLO THERE

is printed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnubash/+bug/1097467/+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 1097467] Re: bash does not fulfill --rcfile option properly

2023-11-14 Thread Dave Jones

** Patch added: "1097467-1.debdiff"
   
https://bugs.launchpad.net/gnubash/+bug/1097467/+attachment/5719274/+files/1097467-1.debdiff

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

Title:
  bash does not fulfill --rcfile option properly

Status in Gnu Bash:
  Unknown
Status in bash package in Ubuntu:
  Confirmed

Bug description:
  I am starting a bash shell using

  $ bash --noprofile --rcfile my-custom-bash-rc-file

  Due to the --rcflag, the newly started bash should *not* execute
  commands from /etc/bash.bashrc. That is at least how I interpret `man
  bash`:

    --rcfile file
    Execute commands from file instead of the system wide 
initialization file /etc/bash.bashrc and the standard personal initial‐
    ization file ~/.bashrc if the shell is interactive (see 
INVOCATION below).

  However, it seems that the commands in /etc/bash.bashrc are in fact
  executed.

  To see/reproduce/diagnose this, on Ubuntu I believe one can just
  invoke bash like this (as the regular user):

  $ touch testrc
  $ env -i bash --noprofile --rcfile testrc

  The expected result would be that nothing special is printed on the
  terminal. However, there is an error message, which is printed from
  /etc/bash.bashrc. The "env -i" causes $HOME to not be set in the
  invoked shell, which in turn triggers the error. The error message is:

  > To run a command as administrator (user "root"), use "sudo ".
  > See "man sudo_root" for details.

  Another way to see this -- without the "env -i" -- is to add  a
  command to /etc/bash.bashrc, such as

  echo HELLO THERE

  To trigger the bug(?), one can then just do

  $ touch testrc
  $ bash --noprofile --rcfile testrc

  The expected result would be that nothing special is shown in the
  terminal. However, it turns out that the string

  HELLO THERE

  is printed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnubash/+bug/1097467/+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 1097467] Re: bash does not fulfill --rcfile option properly

2023-11-14 Thread Dave Jones

It appears this has come up before, and was discussed upstream. [1] and
[2] cover discussion of whether --rcfile should ignore the system-wide
bashrc (SYS_BASHRC hereafter), with the conclusion from upstream that it
should not. [3] is an attempt by someone to fix this upstream by
modifying bash's behaviour, which is rejected by the upstream
developers. [4] and [5] are the upstream Debian bugs (which I'll link
this bug to).

At any rate, upstream bash devs have made their position quite clear:
the Debian-patched documentation is wrong, and the behaviour of bash is
as expected. So, the solution to this bug is to fix the documentation.
I'll propose an updated patch here and see if we can't put this decade-
old bug to bed!

I'll also try and rebase the noble patch upstream for Debian (there's
already a patch there, but it's predictably ancient).

[1]: https://lists.gnu.org/archive/html/bug-bash/2018-01/msg3.html

[2]: https://lists.gnu.org/archive/html/bug-bash/2009-05/msg00031.html

[3]: https://savannah.gnu.org/support/index.php?107950

[4]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=516152

[5]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=343673

** Bug watch added: Debian Bug tracker #516152
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=516152

** Bug watch added: Debian Bug tracker #343673
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=343673

** Also affects: gnubash via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=516152
   Importance: Unknown
   Status: Unknown

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

Title:
  bash does not fulfill --rcfile option properly

Status in Gnu Bash:
  Unknown
Status in bash package in Ubuntu:
  Confirmed

Bug description:
  I am starting a bash shell using

  $ bash --noprofile --rcfile my-custom-bash-rc-file

  Due to the --rcflag, the newly started bash should *not* execute
  commands from /etc/bash.bashrc. That is at least how I interpret `man
  bash`:

    --rcfile file
    Execute commands from file instead of the system wide 
initialization file /etc/bash.bashrc and the standard personal initial‐
    ization file ~/.bashrc if the shell is interactive (see 
INVOCATION below).

  However, it seems that the commands in /etc/bash.bashrc are in fact
  executed.

  To see/reproduce/diagnose this, on Ubuntu I believe one can just
  invoke bash like this (as the regular user):

  $ touch testrc
  $ env -i bash --noprofile --rcfile testrc

  The expected result would be that nothing special is printed on the
  terminal. However, there is an error message, which is printed from
  /etc/bash.bashrc. The "env -i" causes $HOME to not be set in the
  invoked shell, which in turn triggers the error. The error message is:

  > To run a command as administrator (user "root"), use "sudo ".
  > See "man sudo_root" for details.

  Another way to see this -- without the "env -i" -- is to add  a
  command to /etc/bash.bashrc, such as

  echo HELLO THERE

  To trigger the bug(?), one can then just do

  $ touch testrc
  $ bash --noprofile --rcfile testrc

  The expected result would be that nothing special is shown in the
  terminal. However, it turns out that the string

  HELLO THERE

  is printed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnubash/+bug/1097467/+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 2039104] Re: ubuntu-settings must drop ubuntu-raspi-settings* from debian/control

2023-11-09 Thread Dave Jones

** Merge proposal linked:
   
https://code.launchpad.net/~waveform/ubuntu/+source/ubuntu-settings/+git/ubuntu-settings/+merge/455407

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

Title:
  ubuntu-settings must drop ubuntu-raspi-settings* from debian/control

Status in ubuntu-settings package in Ubuntu:
  New
Status in ubuntu-settings source package in Mantic:
  New

Bug description:
  In response to LP: #2038964 and due to the timing we have forked
  ubuntu-raspi-settings into a separate source package.

  ubuntu-settings must therefore be updated to drop ubuntu-raspi-
  settings* from debian/control as otherwise binary builds of the
  package will be rejected by the archive (if the version number is <=
  23.10.6) or will wrongly supersede the fixes that have just been
  uploaded to mantic (if the version number is > 23.10.6).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2039104/+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 2039104] Re: ubuntu-settings must drop ubuntu-raspi-settings* from debian/control

2023-11-07 Thread Dave Jones

Thanks for the quick review! Could someone set up a "mantic" branch on
the lp:~ubuntu-desktop/ubuntu/+source/ubuntu-settings repository so I
can propose a merge to fix mantic too? (basically the same commit with a
lower version number)

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

Title:
  ubuntu-settings must drop ubuntu-raspi-settings* from debian/control

Status in ubuntu-settings package in Ubuntu:
  New
Status in ubuntu-settings source package in Mantic:
  New

Bug description:
  In response to LP: #2038964 and due to the timing we have forked
  ubuntu-raspi-settings into a separate source package.

  ubuntu-settings must therefore be updated to drop ubuntu-raspi-
  settings* from debian/control as otherwise binary builds of the
  package will be rejected by the archive (if the version number is <=
  23.10.6) or will wrongly supersede the fixes that have just been
  uploaded to mantic (if the version number is > 23.10.6).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2039104/+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 2039104] Re: ubuntu-settings must drop ubuntu-raspi-settings* from debian/control

2023-11-06 Thread Dave Jones

** Merge proposal linked:
   
https://code.launchpad.net/~waveform/ubuntu/+source/ubuntu-settings/+git/ubuntu-settings/+merge/455178

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

Title:
  ubuntu-settings must drop ubuntu-raspi-settings* from debian/control

Status in ubuntu-settings package in Ubuntu:
  New
Status in ubuntu-settings source package in Mantic:
  New

Bug description:
  In response to LP: #2038964 and due to the timing we have forked
  ubuntu-raspi-settings into a separate source package.

  ubuntu-settings must therefore be updated to drop ubuntu-raspi-
  settings* from debian/control as otherwise binary builds of the
  package will be rejected by the archive (if the version number is <=
  23.10.6) or will wrongly supersede the fixes that have just been
  uploaded to mantic (if the version number is > 23.10.6).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2039104/+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 1951586] Re: Need option to specify wifi regulatory domain

2023-10-31 Thread Dave Jones

Is this fixed in noble now? No. Is this due to be fixed; I've not heard
anything, but happy to be corrected if this is on a roadmap somewhere?

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

Title:
  Need option to specify wifi regulatory domain

Status in cloud-init:
  Invalid
Status in netplan:
  Fix Released
Status in NetworkManager:
  New
Status in netplan.io package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Incomplete
Status in netplan.io source package in Jammy:
  Triaged
Status in network-manager source package in Jammy:
  Incomplete
Status in netplan.io source package in Kinetic:
  Fix Released
Status in network-manager source package in Kinetic:
  Incomplete

Bug description:
  It would be nice if netplan offered an option to specify the wifi
  regulatory domain (country code).

  
  For devices such as the Raspberry Pi you are currently advertising that users 
can simply setup Ubuntu Server headless by putting the wifi configuration 
details in cloudinit/netplan's "network-config" on the FAT partition of the SD 
card: 
https://ubuntu.com/tutorials/how-to-install-ubuntu-on-your-raspberry-pi#3-wifi-or-ethernet
  But an option to set the wifi country code there does not seem to exist, so 
may not work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1951586/+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 2037642] Re: [FFe] Raspberry Pi 5 support

2023-10-13 Thread Dave Jones

** Changed in: ubuntu-release-notes
   Status: In Progress => Fix Released

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

Title:
  [FFe] Raspberry Pi 5 support

Status in Release Notes for Ubuntu:
  Fix Released
Status in libcamera package in Ubuntu:
  Triaged
Status in linux-meta-raspi package in Ubuntu:
  Fix Released
Status in linux-raspi package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in pipewire package in Ubuntu:
  Invalid
Status in rpi-eeprom package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  [ Impact ]

   * HWE for Raspberry Pi 5 https://raspberrypi.com/5

  [ Test Plan ]

   * Private builds tested on all existing/supported Raspberry Pi SKUs
  in armhf & arm64 variants

   * No regressions on any existing SKUs

   * Test that Raspberry Pi 5 boards work

  [ Where problems could occur ]

   * Mesa is upgraded, and there are patches to mesa, the raspberry-pi
  specific provider this has been tested but not as extensively.
  Separately there is mesa FFe granted to upgrade to latest release,
  thus these changes piggy-back on top of it.

   * libcamera has new build-depends on new package libpisp for the
  raspberry-pi specific provider which also affects pipewire to provide
  full webcam support.

   * These dependencies, will need to make their way into gnome platform
  snaps to be usable by default in Firefox.

  [ Other Info ]

   * The proposed code changes have been tested in private, prior to
  public announcement

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/2037642/+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 2038964] Re: raspi ethernet rename is racy

Figured out a work-around: ensure the matching state of the rename rule
matches the end-state of the rename rule so the networkd state machine
stops flopping between the two rules. Linked the MP with the required
change; will tag ubuntu-release to see if it's not too late for a re-
spin.

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

Title:
  raspi ethernet rename is racy

Status in ubuntu-settings package in Ubuntu:
  Confirmed

Bug description:
  The renaming of the ethernet interface (controlled by 10-raspi-
  eth0.link in ubuntu-raspi-settings) turns out to be racy.
  Specifically, in the final mantic server images (but not the desktop
  images), under armhf or arm64, on the Raspberry Pi 3B+ (but not any
  other supported board, including the 3B), the interface renames
  several times during boot. By the end, the interface is left in the
  enxMACMACMAC state and the netplan configuration fails to apply.

  Will attach kern.log from an affected platform, and another from an
  unaffected platform.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2038964/+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 2038964] Re: raspi ethernet rename is racy

** Merge proposal linked:
   
https://code.launchpad.net/~waveform/ubuntu/+source/ubuntu-settings/+git/ubuntu-settings/+merge/453340

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

Title:
  raspi ethernet rename is racy

Status in ubuntu-settings package in Ubuntu:
  Confirmed

Bug description:
  The renaming of the ethernet interface (controlled by 10-raspi-
  eth0.link in ubuntu-raspi-settings) turns out to be racy.
  Specifically, in the final mantic server images (but not the desktop
  images), under armhf or arm64, on the Raspberry Pi 3B+ (but not any
  other supported board, including the 3B), the interface renames
  several times during boot. By the end, the interface is left in the
  enxMACMACMAC state and the netplan configuration fails to apply.

  Will attach kern.log from an affected platform, and another from an
  unaffected platform.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2038964/+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 2038964] Re: raspi ethernet rename is racy

There does seem to be something unusual going on with the lan78xx re-
initializing (or restarting?) part way through the boot sequence,
causing another round of renaming to kick off (and then everything
fails). Bizarre.

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

Title:
  raspi ethernet rename is racy

Status in ubuntu-settings package in Ubuntu:
  Confirmed

Bug description:
  The renaming of the ethernet interface (controlled by 10-raspi-
  eth0.link in ubuntu-raspi-settings) turns out to be racy.
  Specifically, in the final mantic server images (but not the desktop
  images), under armhf or arm64, on the Raspberry Pi 3B+ (but not any
  other supported board, including the 3B), the interface renames
  several times during boot. By the end, the interface is left in the
  enxMACMACMAC state and the netplan configuration fails to apply.

  Will attach kern.log from an affected platform, and another from an
  unaffected platform.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2038964/+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 2038964] Re: raspi ethernet rename is racy

** Changed in: ubuntu-settings (Ubuntu)
   Importance: Undecided => High

** Changed in: ubuntu-settings (Ubuntu)
   Status: New => Confirmed

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

Title:
  raspi ethernet rename is racy

Status in ubuntu-settings package in Ubuntu:
  Confirmed

Bug description:
  The renaming of the ethernet interface (controlled by 10-raspi-
  eth0.link in ubuntu-raspi-settings) turns out to be racy.
  Specifically, in the final mantic server images (but not the desktop
  images), under armhf or arm64, on the Raspberry Pi 3B+ (but not any
  other supported board, including the 3B), the interface renames
  several times during boot. By the end, the interface is left in the
  enxMACMACMAC state and the netplan configuration fails to apply.

  Will attach kern.log from an affected platform, and another from an
  unaffected platform.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2038964/+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 2038964] Re: raspi ethernet rename is racy

** Attachment added: "kern.log from unaffected 2B (rev 1.2)"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2038964/+attachment/5708342/+files/unaffected.log

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

Title:
  raspi ethernet rename is racy

Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  The renaming of the ethernet interface (controlled by 10-raspi-
  eth0.link in ubuntu-raspi-settings) turns out to be racy.
  Specifically, in the final mantic server images (but not the desktop
  images), under armhf or arm64, on the Raspberry Pi 3B+ (but not any
  other supported board, including the 3B), the interface renames
  several times during boot. By the end, the interface is left in the
  enxMACMACMAC state and the netplan configuration fails to apply.

  Will attach kern.log from an affected platform, and another from an
  unaffected platform.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2038964/+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 2038964] Re: raspi ethernet rename is racy

** Attachment added: "kern.log from affected 3B+"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2038964/+attachment/5708341/+files/affected.log

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

Title:
  raspi ethernet rename is racy

Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  The renaming of the ethernet interface (controlled by 10-raspi-
  eth0.link in ubuntu-raspi-settings) turns out to be racy.
  Specifically, in the final mantic server images (but not the desktop
  images), under armhf or arm64, on the Raspberry Pi 3B+ (but not any
  other supported board, including the 3B), the interface renames
  several times during boot. By the end, the interface is left in the
  enxMACMACMAC state and the netplan configuration fails to apply.

  Will attach kern.log from an affected platform, and another from an
  unaffected platform.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2038964/+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 2038964] [NEW] raspi ethernet rename is racy

Public bug reported:

The renaming of the ethernet interface (controlled by 10-raspi-eth0.link
in ubuntu-raspi-settings) turns out to be racy. Specifically, in the
final mantic server images (but not the desktop images), under armhf or
arm64, on the Raspberry Pi 3B+ (but not any other supported board,
including the 3B), the interface renames several times during boot. By
the end, the interface is left in the enxMACMACMAC state and the netplan
configuration fails to apply.

Will attach kern.log from an affected platform, and another from an
unaffected platform.

** Affects: ubuntu-settings (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: raspi-image

** Tags added: raspi-image

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

Title:
  raspi ethernet rename is racy

Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  The renaming of the ethernet interface (controlled by 10-raspi-
  eth0.link in ubuntu-raspi-settings) turns out to be racy.
  Specifically, in the final mantic server images (but not the desktop
  images), under armhf or arm64, on the Raspberry Pi 3B+ (but not any
  other supported board, including the 3B), the interface renames
  several times during boot. By the end, the interface is left in the
  enxMACMACMAC state and the netplan configuration fails to apply.

  Will attach kern.log from an affected platform, and another from an
  unaffected platform.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2038964/+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 2037642] Re: [FFe] Raspberry Pi 5 support

Added text to the release notes [1] detailing Pi 5 support, including
the planned SRU of libcamera support. Can others double-check the
raspberry pi sections look reasonable, and let me know if we want to
mention anything else specific?

I've also updated the "known issues" section, removing a couple of bits
(totem now works and the audio output selection is now sane out of the
box), and adding others (slide corruption on the pi4 during
installation). Again, if there's anything missing that should be
mentioned please either let me know or feel free to add it yourself!

[1]: https://discourse.ubuntu.com/t/mantic-minotaur-release-notes/35534

** Changed in: ubuntu-release-notes
   Status: New => In Progress

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

Title:
  [FFe] Raspberry Pi 5 support

Status in Release Notes for Ubuntu:
  In Progress
Status in libcamera package in Ubuntu:
  Triaged
Status in linux-meta-raspi package in Ubuntu:
  Fix Released
Status in linux-raspi package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in pipewire package in Ubuntu:
  Invalid
Status in rpi-eeprom package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  [ Impact ]

   * HWE for Raspberry Pi 5 https://raspberrypi.com/5

  [ Test Plan ]

   * Private builds tested on all existing/supported Raspberry Pi SKUs
  in armhf & arm64 variants

   * No regressions on any existing SKUs

   * Test that Raspberry Pi 5 boards work

  [ Where problems could occur ]

   * Mesa is upgraded, and there are patches to mesa, the raspberry-pi
  specific provider this has been tested but not as extensively.
  Separately there is mesa FFe granted to upgrade to latest release,
  thus these changes piggy-back on top of it.

   * libcamera has new build-depends on new package libpisp for the
  raspberry-pi specific provider which also affects pipewire to provide
  full webcam support.

   * These dependencies, will need to make their way into gnome platform
  snaps to be usable by default in Firefox.

  [ Other Info ]

   * The proposed code changes have been tested in private, prior to
  public announcement

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/2037642/+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 2036358] Re: systemd wait-online now times out after jammy and lunar upgrade

2023-10-03 Thread Dave Jones

Seeing the same results as comment 27 with the Pi lunar (23.04) image.
After installing -proposed and checking systemd-networkd-wait-online,
with wlan0 undefined in the netplan configuration (but eth0 set as the
default DHCP and optional), it still waits for the full 2 minutes,
presumably because wlan0 is not explicitly marked as "not required" as
it's not a defined interface in the netplan config?

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

Title:
  systemd wait-online now times out after jammy and lunar upgrade

Status in systemd package in Ubuntu:
  Invalid
Status in systemd source package in Jammy:
  Fix Committed
Status in systemd source package in Lunar:
  Fix Committed

Bug description:
  [NOTE]

  If you are running a desktop system and you see this issue, you should
  run:

  $ systemctl disable --now systemd-networkd.service

  This will disable systemd-networkd and associated units, including
  systemd-networkd-wait-online.service. NetworkManager and systemd-
  networkd should not be running at the same time. On desktop,
  NetworkManager is the default network stack.

  [Impact]

  When all interfaces are "not required for online", e.g. when they are
  marked "optional: true" in netplan, systemd-networkd-wait-online will
  timeout. Or, in other words, systemd-networkd-wait-online will timeout
  even though all interfaces are ignored, hence none of them will ever
  be marked as "ready." Depending on what units depend on network-
  online.target, this can delay boot by 120 seconds (the default timeout
  for systemd-networkd-wait-online).

  [Test Plan]

  1. Create a new LXD container. These instructions assume jammy is the
  release, but the same can be done for lunar.

  $ lxc launch ubuntu-daily:jammy jammy
  $ lxc exec jammy bash

  2. Once in the container, modify the default /etc/netplan/10-lxc.yaml
  so that eth0 is configured with "optional: true":

  $ vi /etc/netplan/50-cloud-init.yaml # Use whatever editor you like
  $ cat /etc/netplan/50-cloud-init.yaml
  network:
    version: 2
    ethernets:
  eth0:
    dhcp4: true
    dhcp-identifier: mac
    optional: true

  3. Re-generate and apply the netplan configuration.

  $ netplan generate
  $ netplan apply

  4. Manually run systemd-networkd-wait-online, and observe that all
  links are ignored, and the command times out:

  $ SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd-wait-online 
--timeout=10
  Found link lo(1)
  Found link eth0(19)
  lo: link is ignored
  eth0: link is ignored
  Timeout occurred while waiting for network connectivity.

  [Where problems could occur]

  This patch partially re-instates a patch remove in bug 1982218.
  However, instead of exiting if all links are unmanaged, we exit if all
  links are ignored in manager_configured(). If the patch was wrong, we
  may re-introduce bug 1982218, so as part of this SRU verification,
  that bug should be tested too. Any other regressions would also be
  related to systemd-networkd-wait-online behavior.

  [Original Description]

  On Ubuntu 22.04 desktop system using network-manager and upgrading to
  systemd 249.11-0ubuntu3.10, wait-online now times out which prevents
  logins (GDM, ssh, console) until it does time out. This seems to be
  introduced by the change for
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218.

  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218/comments/21
  also mentioned the problem on Lunar.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036358/+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 1923363] Re: Grant access to hardware (UARTs, I2C, etc.) via custom udev rules

2023-09-29 Thread Dave Jones

** Merge proposal linked:
   
https://code.launchpad.net/~waveform/ubuntu/+source/ubuntu-settings/+git/ubuntu-settings/+merge/452468

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

Title:
  Grant access to hardware (UARTs, I2C, etc.) via custom udev rules

Status in cloud-init package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Invalid
Status in ubuntu-settings package in Ubuntu:
  Confirmed
Status in user-setup package in Ubuntu:
  Invalid
Status in cloud-init source package in Impish:
  Won't Fix
Status in ubiquity source package in Impish:
  Invalid
Status in ubuntu-settings source package in Impish:
  Won't Fix
Status in user-setup source package in Impish:
  Invalid
Status in cloud-init source package in Jammy:
  Confirmed
Status in ubiquity source package in Jammy:
  Invalid
Status in ubuntu-settings source package in Jammy:
  Confirmed
Status in user-setup source package in Jammy:
  Invalid
Status in cloud-init source package in Kinetic:
  Won't Fix
Status in ubiquity source package in Kinetic:
  Invalid
Status in ubuntu-settings source package in Kinetic:
  Won't Fix
Status in user-setup source package in Kinetic:
  Invalid
Status in cloud-init source package in Lunar:
  Won't Fix
Status in ubiquity source package in Lunar:
  Invalid
Status in ubuntu-settings source package in Lunar:
  Won't Fix
Status in user-setup source package in Lunar:
  Invalid
Status in cloud-init source package in Mantic:
  Fix Released
Status in ubiquity source package in Mantic:
  Invalid
Status in ubuntu-settings source package in Mantic:
  Confirmed
Status in user-setup source package in Mantic:
  Invalid

Bug description:
  We're attempting to make the GPIO system on the Raspberry Pi images
  work "out of the box" on the new image. By default, GPIO kernel
  devices are made available to members of the "dialout" group which the
  initial user is added to by default on our server images. However,
  we've noticed that this isn't the case on the desktop images.

  The regression potential is minimal; the group already exists and
  we're simply adding the freshly created user to a new group and not
  removing any existing memberships. The group in question ("dialout")
  is also rarely used these days except for providing access to serial
  consoles, and as mentioned above is already a default membership on
  the server images. The change has been tested on the desktop image
  successfully.

  A test build of the updated image will be made under
  https://launchpad.net/~waveform/+archive/ubuntu/ubiquity and I'll
  attach a debdiff shortly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1923363/+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 2037642] Re: [FFe] Raspberry Pi 5 support

2023-09-29 Thread Dave Jones

** Merge proposal linked:
   
https://code.launchpad.net/~waveform/ubuntu/+source/ubuntu-settings/+git/ubuntu-settings/+merge/452468

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

Title:
  [FFe] Raspberry Pi 5 support

Status in libcamera package in Ubuntu:
  Triaged
Status in linux-meta-raspi package in Ubuntu:
  Triaged
Status in linux-raspi package in Ubuntu:
  Triaged
Status in mesa package in Ubuntu:
  Triaged
Status in pipewire package in Ubuntu:
  Triaged
Status in rpi-eeprom package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  Triaged

Bug description:
  [ Impact ]

   * HWE for Raspberry Pi 5 https://raspberrypi.com/5

  [ Test Plan ]

   * Private builds tested on all existing/supported Raspberry Pi SKUs
  in armhf & arm64 variants

   * No regressions on any existing SKUs

   * Test that Raspberry Pi 5 boards work

  [ Where problems could occur ]

   * Mesa is upgraded, and there are patches to mesa, the raspberry-pi
  specific provider this has been tested but not as extensively.
  Separately there is mesa FFe granted to upgrade to latest release,
  thus these changes piggy-back on top of it.

   * libcamera has new build-depends on new package libpisp for the
  raspberry-pi specific provider which also affects pipewire to provide
  full webcam support.

   * These dependencies, will need to make their way into gnome platform
  snaps to be usable by default in Firefox.

  [ Other Info ]

   * The proposed code changes have been tested in private, prior to
  public announcement

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libcamera/+bug/2037642/+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 2037642] Re: [FFe] Raspberry Pi 5 support

2023-09-29 Thread Dave Jones

** Changed in: rpi-eeprom (Ubuntu)
 Assignee: (unassigned) => Dave Jones (waveform)

** Changed in: ubuntu-settings (Ubuntu)
 Assignee: (unassigned) => Dave Jones (waveform)

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

Title:
  [FFe] Raspberry Pi 5 support

Status in libcamera package in Ubuntu:
  Triaged
Status in linux-meta-raspi package in Ubuntu:
  Triaged
Status in linux-raspi package in Ubuntu:
  Triaged
Status in mesa package in Ubuntu:
  Triaged
Status in pipewire package in Ubuntu:
  Triaged
Status in rpi-eeprom package in Ubuntu:
  Triaged
Status in ubuntu-settings package in Ubuntu:
  Triaged

Bug description:
  [ Impact ]

   * HWE for Raspberry Pi 5 https://raspberrypi.com/5

  [ Test Plan ]

   * Private builds tested on all existing/supported Raspberry Pi SKUs
  in armhf & arm64 variants

   * No regressions on any existing SKUs

   * Test that Raspberry Pi 5 boards work

  [ Where problems could occur ]

   * Mesa is upgraded, and there are patches to mesa, the raspberry-pi
  specific provider this has been tested but not as extensively.
  Separately there is mesa FFe granted to upgrade to latest release,
  thus these changes piggy-back on top of it.

   * libcamera has new build-depends on new package libpisp for the
  raspberry-pi specific provider which also affects pipewire to provide
  full webcam support.

   * These dependencies, will need to make their way into gnome platform
  snaps to be usable by default in Firefox.

  [ Other Info ]

   * The proposed code changes have been tested in private, prior to
  public announcement

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libcamera/+bug/2037642/+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 2037642] Re: [FFe] Raspberry Pi 5 support

2023-09-28 Thread Dave Jones

The rpiboot package can be skipped for now; according to upstream the
updated package won't be ready at release. The separate bug LP: #2032178
will track updates if/when I can get the uploaded.

** No longer affects: rpiboot (Ubuntu)

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

Title:
  [FFe] Raspberry Pi 5 support

Status in libcamera package in Ubuntu:
  Confirmed
Status in linux-firmware-raspi package in Ubuntu:
  Confirmed
Status in linux-meta-raspi package in Ubuntu:
  Confirmed
Status in linux-raspi package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in pipewire package in Ubuntu:
  Confirmed
Status in rpi-eeprom package in Ubuntu:
  Confirmed
Status in ubuntu-settings package in Ubuntu:
  Confirmed

Bug description:
  [ Impact ]

   * HWE for Raspberry Pi 5 https://raspberrypi.com/5

  [ Test Plan ]

   * Private builds tested on all existing/supported Raspberry Pi SKUs
  in armhf & arm64 variants

   * No regressions on any existing SKUs

   * Test that Raspberry Pi 5 boards work

  [ Where problems could occur ]

   * Mesa is upgraded, and there are patches to mesa, the raspberry-pi
  specific provider this has been tested but not as extensively.
  Separately there is mesa FFe granted to upgrade to latest release,
  thus these changes piggy-back on top of it.

   * libcamera has new build-depends on new package libpisp for the
  raspberry-pi specific provider which also affects pipewire to provide
  full webcam support.

   * These dependencies, will need to make their way into gnome platform
  snaps to be usable by default in Firefox.

  [ Other Info ]

   * The proposed code changes have been tested in private, prior to
  public announcement

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libcamera/+bug/2037642/+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 2036358] Re: systemd wait-online now times out after jammy and lunar upgrade

2023-09-18 Thread Dave Jones

Also appears to be affecting the Pi server images (which have no network
manager and only use networkd for networking); I've only checked lunar
so far.

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

Title:
  systemd wait-online now times out after jammy and lunar upgrade

Status in systemd package in Ubuntu:
  New

Bug description:
  On Ubuntu 22.04 desktop system using network-manager and upgrading to
  systemd 249.11-0ubuntu3.10, wait-online now times out which prevents
  logins (GDM, ssh, console) until it does time out. This seems to be
  introduced by the change for
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218.

  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1982218/comments/21
  also mentioned the problem on Lunar.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036358/+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 2026637] Re: [mantic] many useful apps are marked for auto removal

2023-07-20 Thread Dave Jones

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

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

Title:
  [mantic] many useful apps are marked for auto removal

Status in ubuntu-meta package in Ubuntu:
  Triaged
Status in ubuntu-release-upgrader package in Ubuntu:
  Triaged

Bug description:
  Today update want remove a lot of apps.
  This happens on two systems installed from ISO dated 2023-06-07 and 2023-05-21
  corrado@corrado-n03-mm-0607:~$ sudo apt update && sudo apt upgrade
  [sudo] password for corrado: 
  Hit:1 http://archive.ubuntu.com/ubuntu mantic InRelease
  Hit:2 http://archive.ubuntu.com/ubuntu mantic-updates InRelease
  Hit:3 http://archive.ubuntu.com/ubuntu mantic-backports InRelease
  Hit:4 http://archive.ubuntu.com/ubuntu mantic-security InRelease
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  All packages are up to date.
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Calculating upgrade... Done
  The following packages were automatically installed and are no longer 
required:
aisleriot baobab branding-ubuntu cheese cheese-common file-roller
gir1.2-rb-3.0 gnome-mahjongg gnome-mines gnome-sudoku gnome-video-effects
gstreamer1.0-clutter-3.0 guile-3.0-libs libavahi-ui-gtk3-0 libcairomm-1.16-1
libcdr-0.1-1 libchamplain-0.12-0 libchamplain-gtk-0.12-0 libcheese-gtk25
libcheese8 libclutter-gst-3.0-0 libdmapsharing-4.0-3 libevent-2.1-7
libfreehand-0.1-1 libfreerdp-client2-2 libglibmm-2.68-1
libgnome-games-support-1-3 libgnome-games-support-common libgpod-common
libgpod4 libgtkmm-4.0-0 libgupnp-igd-1.0-4 libixml10 liblc3-0 libminiupnpc17
libmspub-0.1-1 libmujs2 libnatpmp1 libpagemaker-0.0-0 libpangomm-2.48-1
libqqwing2v5 libreoffice-calc libreoffice-draw libreoffice-gnome
libreoffice-gtk3 libreoffice-impress librhythmbox-core10 libsdl-image1.2
libsdl1.2debian libsgutils2-1.46-2 libsigc++-3.0-0 libupnp13 libvisio-0.1-1
lp-solve media-player-info python3-mako python3-renderpm
python3-reportlab-accel remmina remmina-common remmina-plugin-rdp
remmina-plugin-secret remmina-plugin-vnc rhythmbox rhythmbox-data
rhythmbox-plugin-alternative-toolbar rhythmbox-plugins shotwell
shotwell-common simple-scan transmission-common transmission-gtk
  Use 'sudo apt autoremove' to remove them.
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  corrado@corrado-n03-mm-0607:

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: ubuntu-desktop 1.505
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  ApportVersion: 2.26.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul  9 08:53:45 2023
  InstallationDate: Installed on 2023-06-07 (31 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230607)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2026637/+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 2027847] Re: Bump minimum /boot size in ubuntu-release-upgrader

2023-07-20 Thread Dave Jones

** 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 apt in Ubuntu.
https://bugs.launchpad.net/bugs/2027847

Title:
  Bump minimum /boot size in ubuntu-release-upgrader

Status in apt package in Ubuntu:
  Won't Fix
Status in dpkg package in Ubuntu:
  Invalid
Status in kernel-package package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux-firmware package in Ubuntu:
  Invalid
Status in linux-kernel-headers package in Ubuntu:
  Invalid
Status in linux-restricted-modules package in Ubuntu:
  Invalid
Status in ubuntu-release-upgrader package in Ubuntu:
  New

Bug description:
  System information:
  ubuntu 23.04 x86_64
  6.2.0-24-generic

  Upgrading the system:

  $ sudo dpkg --configure -a
  Setting up linux-firmware (20230323.gitbcdcfbcf-0ubuntu1.2) ...
  update-initramfs: Generating /boot/initrd.img-6.2.0-24-generic
  I: The initramfs will attempt to resume from /dev/dm-2
  I: (/dev/mapper/ubuntu--vg-swap_1)
  I: Set the RESUME variable to override this.
  zstd: error 70 : Write error : cannot write block : No space left on device 
  E: mkinitramfs failure zstd -q -1 -T0 70

  Check space left (none):
  $ df -h /boot
  Filesystem  Size  Used Avail Use% Mounted on
  /dev/sdb2   707M  693M 0 100% /boot

  What is required is to remove older kernels (and purge them most likely). 
List all the installed kernels except the current one:
  $ dpkg -l 'linux-*' | sed '/^ii/!d;/'"$(uname -r | sed 
"s/\(.*\)-\([^0-9]\+\)/\1/")"'/d;s/^[^ ]* [^ ]* \([^ ]*\).*/\1/;/[0-9]/!d'
  linux-headers-6.2.0-23
  linux-headers-6.2.0-23-generic
  linux-headers-6.2.0-25
  linux-headers-6.2.0-25-generic
  linux-image-6.2.0-23-generic
  linux-libc-dev:amd64
  linux-libc-dev:i386
  linux-modules-6.2.0-23-generic
  linux-modules-6.2.0-25-generic
  linux-modules-extra-6.2.0-23-generic
  linux-modules-extra-6.2.0-25-generic

  Is not possible to uninstall any kernel because fails:
  $ sudo apt purge linux-headers-6.2.0-23
  E: dpkg was interrupted, you must manually run 'sudo dpkg --configure -a' to 
correct the problem.

  Reconfigure fails again so some kernel have to be manually removed to free up 
space:
  $ sudo rm /boot/initrd.img-6.2.0-23-generic
  $ sudo rm -rf /boot/initrd.img-6.2.0-25-generic.new

  Now you can reconfigure:
  $ 

  Remove kernels:
  $ sudo apt purge linux-headers-6.2.0-23 linux-headers-6.2.0-23-generic 
linux-headers-6.2.0-25 linux-headers-6.2.0-25-generic 
linux-image-6.2.0-23-generic linux-modules-6.2.0-23-generic 
linux-modules-6.2.0-25-generic linux-modules-extra-6.2.0-23-generic 
linux-modules-extra-6.2.0-25-generic

  Reboot:
  $ sudo reboot

  Upgrade as usual:
  $ sudo apt update && sudo apt upgrade

  Before upgrading new kernels I need to check for free space and remove
  older kernels manually. Fix this so there's only one kernel left.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2027847/+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 1923363] Re: Grant access to hardware (UARTs, I2C, etc.) via custom udev rules

2023-07-18 Thread Dave Jones

** Changed in: ubuntu-settings (Ubuntu Mantic)
 Assignee: (unassigned) => Dave Jones (waveform)

** Changed in: ubuntu-settings (Ubuntu Jammy)
 Assignee: (unassigned) => Dave Jones (waveform)

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

Title:
  Grant access to hardware (UARTs, I2C, etc.) via custom udev rules

Status in cloud-init package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Invalid
Status in ubuntu-settings package in Ubuntu:
  Confirmed
Status in user-setup package in Ubuntu:
  Invalid
Status in cloud-init source package in Impish:
  Won't Fix
Status in ubiquity source package in Impish:
  Invalid
Status in ubuntu-settings source package in Impish:
  Won't Fix
Status in user-setup source package in Impish:
  Invalid
Status in cloud-init source package in Jammy:
  Confirmed
Status in ubiquity source package in Jammy:
  Invalid
Status in ubuntu-settings source package in Jammy:
  Confirmed
Status in user-setup source package in Jammy:
  Invalid
Status in cloud-init source package in Kinetic:
  Won't Fix
Status in ubiquity source package in Kinetic:
  Invalid
Status in ubuntu-settings source package in Kinetic:
  Won't Fix
Status in user-setup source package in Kinetic:
  Invalid
Status in cloud-init source package in Lunar:
  Won't Fix
Status in ubiquity source package in Lunar:
  Invalid
Status in ubuntu-settings source package in Lunar:
  Won't Fix
Status in user-setup source package in Lunar:
  Invalid
Status in cloud-init source package in Mantic:
  Confirmed
Status in ubiquity source package in Mantic:
  Invalid
Status in ubuntu-settings source package in Mantic:
  Confirmed
Status in user-setup source package in Mantic:
  Invalid

Bug description:
  We're attempting to make the GPIO system on the Raspberry Pi images
  work "out of the box" on the new image. By default, GPIO kernel
  devices are made available to members of the "dialout" group which the
  initial user is added to by default on our server images. However,
  we've noticed that this isn't the case on the desktop images.

  The regression potential is minimal; the group already exists and
  we're simply adding the freshly created user to a new group and not
  removing any existing memberships. The group in question ("dialout")
  is also rarely used these days except for providing access to serial
  consoles, and as mentioned above is already a default membership on
  the server images. The change has been tested on the desktop image
  successfully.

  A test build of the updated image will be made under
  https://launchpad.net/~waveform/+archive/ubuntu/ubiquity and I'll
  attach a debdiff shortly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1923363/+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 1923363] Re: Grant access to hardware (UARTs, I2C, etc.) via custom udev rules

2023-07-18 Thread Dave Jones

Added PR for cloud-init to remove the default groups that were removed
(ages ago) from the desktop image (excepting the lxd group which was
added in a reasonably recent commit and so is presumably wanted):
https://github.com/canonical/cloud-init/pull/4258

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

Title:
  Grant access to hardware (UARTs, I2C, etc.) via custom udev rules

Status in cloud-init package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Invalid
Status in ubuntu-settings package in Ubuntu:
  Confirmed
Status in user-setup package in Ubuntu:
  Invalid
Status in cloud-init source package in Impish:
  Won't Fix
Status in ubiquity source package in Impish:
  Invalid
Status in ubuntu-settings source package in Impish:
  Won't Fix
Status in user-setup source package in Impish:
  Invalid
Status in cloud-init source package in Jammy:
  Confirmed
Status in ubiquity source package in Jammy:
  Invalid
Status in ubuntu-settings source package in Jammy:
  Confirmed
Status in user-setup source package in Jammy:
  Invalid
Status in cloud-init source package in Kinetic:
  Won't Fix
Status in ubiquity source package in Kinetic:
  Invalid
Status in ubuntu-settings source package in Kinetic:
  Won't Fix
Status in user-setup source package in Kinetic:
  Invalid
Status in cloud-init source package in Lunar:
  Won't Fix
Status in ubiquity source package in Lunar:
  Invalid
Status in ubuntu-settings source package in Lunar:
  Won't Fix
Status in user-setup source package in Lunar:
  Invalid
Status in cloud-init source package in Mantic:
  Confirmed
Status in ubiquity source package in Mantic:
  Invalid
Status in ubuntu-settings source package in Mantic:
  Confirmed
Status in user-setup source package in Mantic:
  Invalid

Bug description:
  We're attempting to make the GPIO system on the Raspberry Pi images
  work "out of the box" on the new image. By default, GPIO kernel
  devices are made available to members of the "dialout" group which the
  initial user is added to by default on our server images. However,
  we've noticed that this isn't the case on the desktop images.

  The regression potential is minimal; the group already exists and
  we're simply adding the freshly created user to a new group and not
  removing any existing memberships. The group in question ("dialout")
  is also rarely used these days except for providing access to serial
  consoles, and as mentioned above is already a default membership on
  the server images. The change has been tested on the desktop image
  successfully.

  A test build of the updated image will be made under
  https://launchpad.net/~waveform/+archive/ubuntu/ubiquity and I'll
  attach a debdiff shortly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1923363/+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 1923363] Re: Users are not added to various groups (dialout, video, etc.)

2023-07-17 Thread Dave Jones

Per vorlon's comments on the merge request, I've closed the merge and
will re-submit an alternative method using udev rules instead of group
membership. Adding ubuntu-settings for the udev rules, and cloud-init as
we presumably want to remove membership in those groups from server
instances too.

** Tags added: foundations-todo

** Summary changed:

- Users are not added to various groups (dialout, video, etc.)
+ Grant access to hardware (UARTs, I2C, etc.) via custom udev rules

** Also affects: ubuntu-settings (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: cloud-init (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: cloud-init (Ubuntu Impish)
   Status: New => Won't Fix

** Changed in: cloud-init (Ubuntu Jammy)
   Status: New => Confirmed

** Changed in: cloud-init (Ubuntu Kinetic)
   Status: New => Won't Fix

** Changed in: cloud-init (Ubuntu Lunar)
   Status: New => Won't Fix

** Changed in: cloud-init (Ubuntu Mantic)
   Status: New => Confirmed

** Changed in: ubiquity (Ubuntu Impish)
   Status: Won't Fix => Invalid

** Changed in: ubiquity (Ubuntu Jammy)
   Status: Confirmed => Invalid

** Changed in: ubiquity (Ubuntu Kinetic)
   Status: Won't Fix => Invalid

** Changed in: ubiquity (Ubuntu Lunar)
   Status: Won't Fix => Invalid

** Changed in: ubiquity (Ubuntu Mantic)
   Status: Confirmed => Invalid

** Changed in: ubuntu-settings (Ubuntu Impish)
   Status: New => Won't Fix

** Changed in: ubuntu-settings (Ubuntu Jammy)
   Status: New => Confirmed

** Changed in: ubuntu-settings (Ubuntu Kinetic)
   Status: New => Won't Fix

** Changed in: ubuntu-settings (Ubuntu Lunar)
   Status: New => Won't Fix

** Changed in: ubuntu-settings (Ubuntu Mantic)
   Status: New => Confirmed

** Changed in: user-setup (Ubuntu Impish)
   Status: Won't Fix => Invalid

** Changed in: user-setup (Ubuntu Jammy)
   Status: Confirmed => Invalid

** Changed in: user-setup (Ubuntu Kinetic)
   Status: Won't Fix => Invalid

** Changed in: user-setup (Ubuntu Lunar)
   Status: Won't Fix => Invalid

** Changed in: user-setup (Ubuntu Mantic)
   Status: Confirmed => Invalid

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

Title:
  Grant access to hardware (UARTs, I2C, etc.) via custom udev rules

Status in cloud-init package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Invalid
Status in ubuntu-settings package in Ubuntu:
  Confirmed
Status in user-setup package in Ubuntu:
  Invalid
Status in cloud-init source package in Impish:
  Won't Fix
Status in ubiquity source package in Impish:
  Invalid
Status in ubuntu-settings source package in Impish:
  Won't Fix
Status in user-setup source package in Impish:
  Invalid
Status in cloud-init source package in Jammy:
  Confirmed
Status in ubiquity source package in Jammy:
  Invalid
Status in ubuntu-settings source package in Jammy:
  Confirmed
Status in user-setup source package in Jammy:
  Invalid
Status in cloud-init source package in Kinetic:
  Won't Fix
Status in ubiquity source package in Kinetic:
  Invalid
Status in ubuntu-settings source package in Kinetic:
  Won't Fix
Status in user-setup source package in Kinetic:
  Invalid
Status in cloud-init source package in Lunar:
  Won't Fix
Status in ubiquity source package in Lunar:
  Invalid
Status in ubuntu-settings source package in Lunar:
  Won't Fix
Status in user-setup source package in Lunar:
  Invalid
Status in cloud-init source package in Mantic:
  Confirmed
Status in ubiquity source package in Mantic:
  Invalid
Status in ubuntu-settings source package in Mantic:
  Confirmed
Status in user-setup source package in Mantic:
  Invalid

Bug description:
  We're attempting to make the GPIO system on the Raspberry Pi images
  work "out of the box" on the new image. By default, GPIO kernel
  devices are made available to members of the "dialout" group which the
  initial user is added to by default on our server images. However,
  we've noticed that this isn't the case on the desktop images.

  The regression potential is minimal; the group already exists and
  we're simply adding the freshly created user to a new group and not
  removing any existing memberships. The group in question ("dialout")
  is also rarely used these days except for providing access to serial
  consoles, and as mentioned above is already a default membership on
  the server images. The change has been tested on the desktop image
  successfully.

  A test build of the updated image will be made under
  https://launchpad.net/~waveform/+archive/ubuntu/ubiquity and I'll
  attach a debdiff shortly.

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to :

[Touch-packages] [Bug 1939537] Re: Tests in ubuntu_lxc failed with "ERROR: Couldn't find a matching image." on X-hwe and older releases

2023-06-08 Thread Dave Jones

Is there anything left to do on this bug? Any further series to target
for lxc, and/or anything to do with the ubuntu-kernel-tests?

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

Title:
  Tests in ubuntu_lxc failed with "ERROR: Couldn't find a matching
  image." on X-hwe and older releases

Status in ubuntu-kernel-tests:
  New
Status in lxc package in Ubuntu:
  Confirmed
Status in lxc source package in Bionic:
  Fix Released

Bug description:
  [ Impact ]

   * The following tests fail as they try to use inexistent LXC images:
     * lxc-test-apparmor-mount
     * lxc-test-autostart
     * lxc-test-unpriv
     * lxc-test-usernic

   * Having them fixed for the affected series (for example, Bionic)
  will allow us to run the LXC test suite without maintaining local
  changes for these tests.

  [ Test Plan ]

   * Run the affected tests on an affected series (e.g. Bionic).
   * The tests should pass.

  [ Where problems could occur ]

   * The regression risk is very low and the changes only affect the
  tests so the regression scope is minimal.

  [Other info]

  Original bug report:

  Issue found on node onibi 4.15.0-142-generic #146~16.04.1

  With bug 1916087 resolved, the following tests:
    * lxc-test-apparmor-mount
    * lxc-test-autostart
    * lxc-test-unpriv
    * lxc-test-usernic

  Are now failing with:
    ERROR: Couldn't find a matching image.

  This is because with lxc version 2.0.11-0ubuntu1~16.04.3 the default target 
release is "trusty" or the system release if supported. It will be checked with:
    ubuntu-distro-info --supported

  However Xenial is an ESM series now, it won't use xenial as the target
  release but use trusty instead.

  The attempt to download trusty image will fail with this error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1939537/+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 2020464] Re: Please merge lvm 2.03.16-2 from Debian unstable

2023-06-07 Thread Dave Jones

** Merge proposal linked:
   
https://code.launchpad.net/~waveform/ubuntu/+source/lvm2/+git/lvm2/+merge/444199

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

Title:
  Please merge lvm 2.03.16-2 from Debian unstable

Status in lvm2 package in Ubuntu:
  New

Bug description:
  Please merge lvm2 2.03.16-2 from Debian unstable.
  
  Updated changelog and diff against Debian unstable to be attached below.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/2020464/+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 2020604] Re: After mesa upgrades, Chrome won't show graphics

2023-05-26 Thread Dave Chiluk

As I have multiple profiles, I chose to simply delete all Cache
directories


$ find ~/.config/google-chrome \( -name "*Cache" \) | xargs -d '\n' -L 1 rm -rf

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

Title:
  After mesa upgrades, Chrome won't show graphics

Status in chromium-browser package in Ubuntu:
  Fix Committed
Status in mesa package in Ubuntu:
  Triaged

Bug description:
  After today's Ubuntu 22.04 mesa upgrades many of our users reported
  problems viewing graphics when using Google Chrome (Stable).

  The mesa upgrades we installed were:

  [UPGRADE] libegl-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libegl1-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libgl1-mesa-dri:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libgl1-mesa-glx:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libglapi-mesa:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] libglx-mesa0:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2
  [UPGRADE] mesa-vulkan-drivers:amd64 22.2.5-0ubuntu0.1~22.04.1 -> 
22.2.5-0ubuntu0.1~22.04.2

  We documented the problem in AskUbuntu before we realized it was
  probably related to mesa, so wanted to link to that report here:

  https://askubuntu.com/questions/1469116/since-23-may-2023-ubuntu-22-04-mesa-
  updates-chrome-wont-display-website-graphi

  There are several useful pointers and bypasses listed in that
  AskUbuntu link (one being to remove affected users' GPUCache
  directories, which does not destroy their profiles and seems to work
  in many but not all cases).

  Not sure if this is an issue with mesa or Chrome or specific machine
  graphics or an interaction between them.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2020604/+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 1971425] Re: The "look" cli dictionary only sees capitalized words

2023-05-25 Thread Dave Jones

** Tags removed: regression-release rls-jj-incoming
** Tags added: foundations-todo

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

Title:
  The "look" cli dictionary only sees capitalized words

Status in util-linux package in Ubuntu:
  Confirmed
Status in util-linux package in Debian:
  Unknown

Bug description:
  In Ubuntu 20.04;
  ~ > look accident
  accident
  accident's
  accidental
  accidental's
  accidentally
  accidentals
  accidents
  In Ubuntu 22.04;
  ~ > look accident
  (nothing)
  ~ > look acc
  Accenture
  Accenture's
  Accra
  Accra's
  Digging deeper; the dictionary at /usr/share/dict/words seems OK.
  If I copy the "look" binary from Ubuntu 20.04 and use it on Ubuntu 22.04 it 
works;
  ~ > ./look accident
  accident
  accidental
  accidentally
  accidental's
  accidentals
  accident's
  accidents

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: bsdextrautils 2.37.2-4ubuntu3
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Tue May  3 14:19:57 2022
  InstallationDate: Installed on 2018-09-07 (1334 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: util-linux
  UpgradeStatus: Upgraded to jammy on 2022-05-01 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1971425/+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 2019940] Re: Directly manipulating NetworkManager keyfiles

2023-05-25 Thread Dave Jones

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

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

Title:
  Directly manipulating NetworkManager keyfiles

Status in augeas package in Ubuntu:
  New
Status in calamares package in Ubuntu:
  New
Status in cloud-init package in Ubuntu:
  Invalid
Status in cruft package in Ubuntu:
  Won't Fix
Status in cruft-ng package in Ubuntu:
  New
Status in dracut package in Ubuntu:
  New
Status in forensic-artifacts package in Ubuntu:
  New
Status in guestfs-tools package in Ubuntu:
  New
Status in guix package in Ubuntu:
  New
Status in ltsp package in Ubuntu:
  Invalid
Status in netcfg package in Ubuntu:
  Won't Fix
Status in netplan.io package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  New
Status in refpolicy package in Ubuntu:
  New
Status in sosreport package in Ubuntu:
  Invalid
Status in ubiquity package in Ubuntu:
  New
Status in uhd package in Ubuntu:
  New
Status in vagrant package in Ubuntu:
  New

Bug description:
  The affected packages can manipulate NetworkManager keyfiles directly
  on disk, which might not be appropriate anymore on Ubuntu, since the
  Netplan integration was enabled in NetworkManager (starting with
  Mantic), migrating any keyfile configuration from
  /etc/NetworkManager/system-connections/*[.nmconnection] to
  /etc/netplan/90-NM-*.yaml

  See Netplan's documentation for how connections are handled:
  https://netplan.readthedocs.io/en/latest/netplan-everywhere/

  PS: Packages were queried using:
  
https://codesearch.debian.net/search?q=%2Fsystem-connections=1=1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/augeas/+bug/2019940/+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 2020464] Re: Please merge lvm 2.03.16-2 from Debian unstable

2023-05-23 Thread Dave Jones

Test packages built in ppa:waveform/lvm2
(https://launchpad.net/~waveform/+archive/ubuntu/lvm2)

** Tags added: fr-4283

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

Title:
  Please merge lvm 2.03.16-2 from Debian unstable

Status in lvm2 package in Ubuntu:
  New

Bug description:
  Please merge lvm2 2.03.16-2 from Debian unstable.
  
  Updated changelog and diff against Debian unstable to be attached below.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/2020464/+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 2020464] Re: Please merge lvm 2.03.16-2 from Debian unstable

2023-05-23 Thread Dave Jones

Attaching patch against Debian unstable. For ease of review, relevant
commits and tags have been pushed to the following repository:

https://code.launchpad.net/~waveform/ubuntu/+source/lvm2/+git/lvm2

Specifically:

* logical/2.03.16-1ubuntu1 represents our split-out delta on
  top of old/debian (2.03.16-1)
* logical/2.03.16-2ubuntu1 represents our rebased delta on
  top of new/debian (2.03.16-2)
* merge/2.03.16-2ubuntu1 adds changelog and maintainer
  changes on top of logical/2.03.16-2ubuntu1

Hence, the following command may produce output useful to the purposes
of review:

git range-diff --creation-factor=100
old/debian..logical/2.03.16-1ubuntu1
new/debian..logical/2.03.16-2ubuntu1


** Patch added: "1-2020464.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/2020464/+attachment/5674963/+files/1-2020464.debdiff

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

Title:
  Please merge lvm 2.03.16-2 from Debian unstable

Status in lvm2 package in Ubuntu:
  New

Bug description:
  Please merge lvm2 2.03.16-2 from Debian unstable.
  
  Updated changelog and diff against Debian unstable to be attached below.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/2020464/+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 2020464] [NEW] Please merge lvm 2.03.16-2 from Debian unstable

2023-05-23 Thread Dave Jones

Public bug reported:

Please merge lvm2 2.03.16-2 from Debian unstable.

Updated changelog and diff against Debian unstable to be attached below.

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

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

Title:
  Please merge lvm 2.03.16-2 from Debian unstable

Status in lvm2 package in Ubuntu:
  New

Bug description:
  Please merge lvm2 2.03.16-2 from Debian unstable.
  
  Updated changelog and diff against Debian unstable to be attached below.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/2020464/+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 2020110] Re: Migrate netplan settings to this package

2023-05-18 Thread Dave Jones

** Merge proposal linked:
   
https://code.launchpad.net/~waveform/ubuntu/+source/ubuntu-settings/+git/ubuntu-settings/+merge/443210

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

Title:
  Migrate netplan settings to this package

Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  The current netplan configuration that specifies Network Manager as
  the renderer comes from a livecd-rootfs hack and results in an
  "unowned" file in /etc/netplan/01-use-network-manager.yaml. It was
  decided at the engineering sprint to migrate this to /lib/netplan
  (with a slightly tweaked filename starting 00- for precedence) owned
  by ubuntu-settings which will ease maintenance (and image builds) in
  future.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2020110/+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 2020110] Re: Migrate netplan settings to this package

2023-05-18 Thread Dave Jones

Test package building in ppa:waveform/ubuntu-settings for mantic
(https://launchpad.net/~waveform/+archive/ubuntu/ubuntu-settings)

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

Title:
  Migrate netplan settings to this package

Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  The current netplan configuration that specifies Network Manager as
  the renderer comes from a livecd-rootfs hack and results in an
  "unowned" file in /etc/netplan/01-use-network-manager.yaml. It was
  decided at the engineering sprint to migrate this to /lib/netplan
  (with a slightly tweaked filename starting 00- for precedence) owned
  by ubuntu-settings which will ease maintenance (and image builds) in
  future.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2020110/+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 2020110] [NEW] Migrate netplan settings to this package

2023-05-18 Thread Dave Jones

Public bug reported:

The current netplan configuration that specifies Network Manager as the
renderer comes from a livecd-rootfs hack and results in an "unowned"
file in /etc/netplan/01-use-network-manager.yaml. It was decided at the
engineering sprint to migrate this to /lib/netplan (with a slightly
tweaked filename starting 00- for precedence) owned by ubuntu-settings
which will ease maintenance (and image builds) in future.

** Affects: ubuntu-settings (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Migrate netplan settings to this package

Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  The current netplan configuration that specifies Network Manager as
  the renderer comes from a livecd-rootfs hack and results in an
  "unowned" file in /etc/netplan/01-use-network-manager.yaml. It was
  decided at the engineering sprint to migrate this to /lib/netplan
  (with a slightly tweaked filename starting 00- for precedence) owned
  by ubuntu-settings which will ease maintenance (and image builds) in
  future.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2020110/+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 2015778] Re: conffile prompt during release upgrade

@enr0n ah, that makes sense (and apologies to @zhsj; I suspect I
misinterpreted comment 2!)

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

Title:
  conffile prompt during release upgrade

Status in binutils package in Ubuntu:
  Triaged
Status in binutils source package in Lunar:
  Triaged

Bug description:
  I was upgrading from Kinetic to Lunar today and received a question
  about a configuration file I had not touched.

  Setting up binutils-common:amd64 (2.40-2ubuntu3) ...^M
  ^M
  Configuration file '/etc/gprofng.rc'^M
   ==> File on system created by you or by a script.^M
   ==> File also in package provided by package maintainer.^M
 What would you like to do about it ?  Your options are:^M
  Y or I  : install the package maintainer's version^M
  N or O  : keep your currently-installed version^M
D : show the differences between the versions^M
Z : start a shell to examine the situation^M
   The default action is to keep your current version.^M
  *** gprofng.rc (Y/I/N/O/D/Z) [default=N] ? d^M
  ^[[?1h^[=^M--- /etc/gprofng.rc 2022-12-01 03:11:36.0 -0800^[[m^M
  +++ /etc/gprofng.rc.dpkg-new2023-03-05 00:47:46.0 -0800^[[m^M
  @@ -1,4 +1,4 @@^[[m^M
  -#   Copyright (C) 2021 Free Software Foundation, Inc.^[[m^M
  +#   Copyright (C) 2021-2023 Free Software Foundation, Inc.^[[m^M
   #^[[m^M
   # This file is free software; you can redistribute it and/or modify^[[m^M
   # it under the terms of the GNU General Public License as published by^[[m^M
  ^M^[[K^[[?1l^[>^M 
  Configuration file '/etc/gprofng.rc'^M
   ==> File on system created by you or by a script.^M
   ==> File also in package provided by package maintainer.^M
 What would you like to do about it ?  Your options are:^M
  Y or I  : install the package maintainer's version^M
  N or O  : keep your currently-installed version^M
D : show the differences between the versions^M
Z : start a shell to examine the situation^M
   The default action is to keep your current version.^M
  *** gprofng.rc (Y/I/N/O/D/Z) [default=N] ? i^M
  Installing new version of config file /etc/gprofng.rc ...^M

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/2015778/+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 2016285] Re: Redundant creation of oem user in rpi desktop images

Setting to critical as this currently prevents the creation of the
ubuntu rpi desktop images.

** Changed in: livecd-rootfs (Ubuntu)
   Importance: Undecided => Critical

** Changed in: ubuntu-settings (Ubuntu)
   Importance: Undecided => Critical

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

Title:
  Redundant creation of oem user in rpi desktop images

Status in livecd-rootfs package in Ubuntu:
  New
Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  There are two (semi-related) issues which are currently preventing the
  creation of Ubuntu desktop images for the Raspberry Pi:

  The first is that livecd-rootfs is erroneously trying to create the
  oem user (and run oem-config-prepare) twice in live-
  build/ubuntu/hooks/099-ubuntu-image-customization.chroot.

  The second is that the ubuntu-raspi-settings-desktop package is
  attempt to create the oem user and run oem-config-prepare in its
  postinst. This is the wrong place to accomplish this as there's no
  guarantee that oem-config-prepare is installed at the time that
  ubuntu-raspi-settings-desktop is installed. It cannot be a dependency
  because oem-config is uninstalled after first boot.

  It's likely that the *correct* place to do this configuration is in
  neither of these places, but in oem-config's postinst (along with some
  check that it's being installed in an image that's never been booted,
  e.g. check for the existence of some sentinel created on first boot
  ... maybe /var/log/boot.log or something). Still, that fix can wait
  until it's not release week!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2016285/+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 2016286] [NEW] growroot-almost service failure after upgrade

Public bug reported:

Users upgrading Ubuntu desktop for Raspberry Pi from kinetic to lunar
may notice that the new growroot-almost.service persistently fails as
the root is already resized. The unit should be updated to fail silently
and prevent future runs.

** Affects: ubuntu-settings (Ubuntu)
 Importance: Undecided
 Status: New

** Merge proposal linked:
   
https://code.launchpad.net/~waveform/ubuntu/+source/ubuntu-settings/+git/ubuntu-settings/+merge/441072

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

Title:
  growroot-almost service failure after upgrade

Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  Users upgrading Ubuntu desktop for Raspberry Pi from kinetic to lunar
  may notice that the new growroot-almost.service persistently fails as
  the root is already resized. The unit should be updated to fail
  silently and prevent future runs.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2016286/+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 2016285] Re: Redundant creation of oem user in rpi desktop images

** Merge proposal linked:
   
https://code.launchpad.net/~waveform/ubuntu/+source/ubuntu-settings/+git/ubuntu-settings/+merge/441072

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

Title:
  Redundant creation of oem user in rpi desktop images

Status in livecd-rootfs package in Ubuntu:
  New
Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  There are two (semi-related) issues which are currently preventing the
  creation of Ubuntu desktop images for the Raspberry Pi:

  The first is that livecd-rootfs is erroneously trying to create the
  oem user (and run oem-config-prepare) twice in live-
  build/ubuntu/hooks/099-ubuntu-image-customization.chroot.

  The second is that the ubuntu-raspi-settings-desktop package is
  attempt to create the oem user and run oem-config-prepare in its
  postinst. This is the wrong place to accomplish this as there's no
  guarantee that oem-config-prepare is installed at the time that
  ubuntu-raspi-settings-desktop is installed. It cannot be a dependency
  because oem-config is uninstalled after first boot.

  It's likely that the *correct* place to do this configuration is in
  neither of these places, but in oem-config's postinst (along with some
  check that it's being installed in an image that's never been booted,
  e.g. check for the existence of some sentinel created on first boot
  ... maybe /var/log/boot.log or something). Still, that fix can wait
  until it's not release week!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2016285/+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 2016285] [NEW] Redundant creation of oem user in rpi desktop images

Public bug reported:

There are two (semi-related) issues which are currently preventing the
creation of Ubuntu desktop images for the Raspberry Pi:

The first is that livecd-rootfs is erroneously trying to create the oem
user (and run oem-config-prepare) twice in live-
build/ubuntu/hooks/099-ubuntu-image-customization.chroot.

The second is that the ubuntu-raspi-settings-desktop package is attempt
to create the oem user and run oem-config-prepare in its postinst. This
is the wrong place to accomplish this as there's no guarantee that oem-
config-prepare is installed at the time that ubuntu-raspi-settings-
desktop is installed. It cannot be a dependency because oem-config is
uninstalled after first boot.

It's likely that the *correct* place to do this configuration is in
neither of these places, but in oem-config's postinst (along with some
check that it's being installed in an image that's never been booted,
e.g. check for the existence of some sentinel created on first boot ...
maybe /var/log/boot.log or something). Still, that fix can wait until
it's not release week!

** Affects: livecd-rootfs (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: ubuntu-settings (Ubuntu)
 Importance: Undecided
 Status: New

** Also affects: ubuntu-settings (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: livecd-rootfs (Ubuntu)
Milestone: None => ubuntu-23.04

** Changed in: ubuntu-settings (Ubuntu)
Milestone: None => ubuntu-23.04

** Merge proposal linked:
   
https://code.launchpad.net/~waveform/livecd-rootfs/+git/livecd-rootfs/+merge/441071

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

Title:
  Redundant creation of oem user in rpi desktop images

Status in livecd-rootfs package in Ubuntu:
  New
Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  There are two (semi-related) issues which are currently preventing the
  creation of Ubuntu desktop images for the Raspberry Pi:

  The first is that livecd-rootfs is erroneously trying to create the
  oem user (and run oem-config-prepare) twice in live-
  build/ubuntu/hooks/099-ubuntu-image-customization.chroot.

  The second is that the ubuntu-raspi-settings-desktop package is
  attempt to create the oem user and run oem-config-prepare in its
  postinst. This is the wrong place to accomplish this as there's no
  guarantee that oem-config-prepare is installed at the time that
  ubuntu-raspi-settings-desktop is installed. It cannot be a dependency
  because oem-config is uninstalled after first boot.

  It's likely that the *correct* place to do this configuration is in
  neither of these places, but in oem-config's postinst (along with some
  check that it's being installed in an image that's never been booted,
  e.g. check for the existence of some sentinel created on first boot
  ... maybe /var/log/boot.log or something). Still, that fix can wait
  until it's not release week!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2016285/+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 2004430] Re: Migrate raspberry pi image hacks from livecd-rootfs

Fix-released in livecd-rootfs 2.818

** Changed in: livecd-rootfs (Ubuntu)
   Status: New => Fix Released

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

Title:
  Migrate raspberry pi image hacks from livecd-rootfs

Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  There are currently several "hacks" in livecd-rootfs that introduce
  unpackaged files and/or services. In particular, everything in
  https://git.launchpad.net/ubuntu/+source/livecd-rootfs/tree/live-
  build/ubuntu/hooks/099-ubuntu-image-customization.chroot dealing with
  the fstab and the swapfile needs to go. The new ubuntu-image based
  process for generating images won't be using these; anything to do
  with the fstab needs to go in the image-definition yaml, and the
  swapfile services ought to be owned by the ubuntu-raspi-settings-
  desktop package anyway.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2004430/+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 2013080] Re: On rpi desktop images, grow root leaving slack for LUKS

This was fixed-released in livecd-rootfs 2.818

** Changed in: livecd-rootfs (Ubuntu)
   Status: New => Fix Released

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

Title:
  On rpi desktop images, grow root leaving slack for LUKS

Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in ubuntu-settings package in Ubuntu:
  Fix Released

Bug description:
  To aid in user-implemented FDE we wish to leave 16MB of the file-
  system unexpanded during first boot. The growth of the partition is
  unaffected, but rather than relying on systemd's growfs facility in
  fstab, we should use a service that runs a simple script to handle
  calculating the resize in early boot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2013080/+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 1951586] Re: Need option to specify wifi regulatory domain

2023-04-13 Thread Dave Jones

netplan added support for configuring the regulatory domain in kinetic
and it works pretty nicely (it's one of the things I test before
release). However, that's relying on cloud-init to inject the netplan
configuration and that's only on the server images -- it's not a
solution for the preinstalled desktop images.

Having said that ... it might be if cloud-init gets included in the
preinstalled desktop images, but that's not happening in lunar as it
caused other issues. Still, even if it did that's still a rather
command-line / text-configuration-file interface that's nowhere near as
"good" as having it integrated into the first time GUI setup (as RaspiOS
does).

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

Title:
  Need option to specify wifi regulatory domain

Status in cloud-init:
  Invalid
Status in netplan:
  Fix Released
Status in NetworkManager:
  New
Status in netplan.io package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Incomplete
Status in netplan.io source package in Jammy:
  Triaged
Status in network-manager source package in Jammy:
  Incomplete
Status in netplan.io source package in Kinetic:
  Fix Released
Status in network-manager source package in Kinetic:
  Incomplete

Bug description:
  It would be nice if netplan offered an option to specify the wifi
  regulatory domain (country code).

  
  For devices such as the Raspberry Pi you are currently advertising that users 
can simply setup Ubuntu Server headless by putting the wifi configuration 
details in cloudinit/netplan's "network-config" on the FAT partition of the SD 
card: 
https://ubuntu.com/tutorials/how-to-install-ubuntu-on-your-raspberry-pi#3-wifi-or-ethernet
  But an option to set the wifi country code there does not seem to exist, so 
may not work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1951586/+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 2015778] Re: conffile prompt during release upgrade

2023-04-13 Thread Dave Jones

Just ran into this on a test upgrade of the raspi desktop image. The
card was originally flashed with kinetic and I noted /etc/gprofng.rc was
*not* present initially (@zhsj is correct this doesn't *ship* with
kinetic), but appeared after the initial upgrade required before do-
release-upgrade (in other words /etc/gprofng.rc is introduced by the
version of binutils-common in kinetic-updates).

The /etc/gprofng.rc file was unmodified before proceeding to do-release-
upgrade, yet I was prompted to merge changes during the upgrade (which
was otherwise uneventful), despite there being no local changes to the
file, and the only diff being that shown in the description above (a
change in the copyright notice in the header).

Some issue in the configuration merge mechanism, perhaps? Or maybe
something iffy being done to the config file in the binutils-common
maintscripts (if any)?

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

Title:
  conffile prompt during release upgrade

Status in binutils package in Ubuntu:
  New
Status in binutils source package in Lunar:
  New

Bug description:
  I was upgrading from Kinetic to Lunar today and received a question
  about a configuration file I had not touched.

  Setting up binutils-common:amd64 (2.40-2ubuntu3) ...^M
  ^M
  Configuration file '/etc/gprofng.rc'^M
   ==> File on system created by you or by a script.^M
   ==> File also in package provided by package maintainer.^M
 What would you like to do about it ?  Your options are:^M
  Y or I  : install the package maintainer's version^M
  N or O  : keep your currently-installed version^M
D : show the differences between the versions^M
Z : start a shell to examine the situation^M
   The default action is to keep your current version.^M
  *** gprofng.rc (Y/I/N/O/D/Z) [default=N] ? d^M
  ^[[?1h^[=^M--- /etc/gprofng.rc 2022-12-01 03:11:36.0 -0800^[[m^M
  +++ /etc/gprofng.rc.dpkg-new2023-03-05 00:47:46.0 -0800^[[m^M
  @@ -1,4 +1,4 @@^[[m^M
  -#   Copyright (C) 2021 Free Software Foundation, Inc.^[[m^M
  +#   Copyright (C) 2021-2023 Free Software Foundation, Inc.^[[m^M
   #^[[m^M
   # This file is free software; you can redistribute it and/or modify^[[m^M
   # it under the terms of the GNU General Public License as published by^[[m^M
  ^M^[[K^[[?1l^[>^M 
  Configuration file '/etc/gprofng.rc'^M
   ==> File on system created by you or by a script.^M
   ==> File also in package provided by package maintainer.^M
 What would you like to do about it ?  Your options are:^M
  Y or I  : install the package maintainer's version^M
  N or O  : keep your currently-installed version^M
D : show the differences between the versions^M
Z : start a shell to examine the situation^M
   The default action is to keep your current version.^M
  *** gprofng.rc (Y/I/N/O/D/Z) [default=N] ? i^M
  Installing new version of config file /etc/gprofng.rc ...^M

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/2015778/+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 1951586] Re: Need option to specify wifi regulatory domain

2023-04-13 Thread Dave Jones

Given there doesn't seem much interest in fixing this from the network
manager angle (and there's even a question as to whether that's the
right place to fix this), I'm going to take a leaf out of the RaspiOS
book, and see if I can persuade someone that the installer is the right
place to fix this (or more specifically, the new installer, subiquity).

That's not going to do anything for lunar which won't be using subiquity
on the raspi images, so I'll hold off on adding the project to the
"affected" list until lunar's out, but it should be something I can try
and push for in the m-animal cycle.

@jgneff many thanks for the additional report -- it's extremely useful
to have stuff like this I can point to and say "look! It's actually a
problem!"

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

Title:
  Need option to specify wifi regulatory domain

Status in cloud-init:
  Invalid
Status in netplan:
  Fix Released
Status in NetworkManager:
  New
Status in netplan.io package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Incomplete
Status in netplan.io source package in Jammy:
  Triaged
Status in network-manager source package in Jammy:
  Incomplete
Status in netplan.io source package in Kinetic:
  Fix Released
Status in network-manager source package in Kinetic:
  Incomplete

Bug description:
  It would be nice if netplan offered an option to specify the wifi
  regulatory domain (country code).

  
  For devices such as the Raspberry Pi you are currently advertising that users 
can simply setup Ubuntu Server headless by putting the wifi configuration 
details in cloudinit/netplan's "network-config" on the FAT partition of the SD 
card: 
https://ubuntu.com/tutorials/how-to-install-ubuntu-on-your-raspberry-pi#3-wifi-or-ethernet
  But an option to set the wifi country code there does not seem to exist, so 
may not work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1951586/+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 2013080] Re: On rpi desktop images, grow root leaving slack for LUKS

2023-03-30 Thread Dave Jones

** Also affects: livecd-rootfs (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: livecd-rootfs (Ubuntu)
Milestone: None => ubuntu-23.04

** Changed in: livecd-rootfs (Ubuntu)
 Assignee: (unassigned) => Dave Jones (waveform)

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

Title:
  On rpi desktop images, grow root leaving slack for LUKS

Status in livecd-rootfs package in Ubuntu:
  New
Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  To aid in user-implemented FDE we wish to leave 16MB of the file-
  system unexpanded during first boot. The growth of the partition is
  unaffected, but rather than relying on systemd's growfs facility in
  fstab, we should use a service that runs a simple script to handle
  calculating the resize in early boot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/livecd-rootfs/+bug/2013080/+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 2013080] Re: On rpi desktop images, grow root leaving slack for LUKS

2023-03-28 Thread Dave Jones

This should only be merged once LP: #2004430 as it builds upon those
commits.

** Merge proposal linked:
   
https://code.launchpad.net/~waveform/ubuntu/+source/ubuntu-settings/+git/ubuntu-settings/+merge/439835

** Merge proposal linked:
   
https://code.launchpad.net/~waveform/livecd-rootfs/+git/livecd-rootfs/+merge/439842

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

Title:
  On rpi desktop images, grow root leaving slack for LUKS

Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  To aid in user-implemented FDE we wish to leave 16MB of the file-
  system unexpanded during first boot. The growth of the partition is
  unaffected, but rather than relying on systemd's growfs facility in
  fstab, we should use a service that runs a simple script to handle
  calculating the resize in early boot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2013080/+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 2013080] [NEW] On rpi desktop images, grow root leaving slack for LUKS

2023-03-28 Thread Dave Jones

Public bug reported:

To aid in user-implemented FDE we wish to leave 16MB of the file-system
unexpanded during first boot. The growth of the partition is unaffected,
but rather than relying on systemd's growfs facility in fstab, we should
use a service that runs a simple script to handle calculating the resize
in early boot.

** Affects: ubuntu-settings (Ubuntu)
 Importance: Undecided
 Assignee: Dave Jones (waveform)
 Status: New

** Changed in: ubuntu-settings (Ubuntu)
 Assignee: (unassigned) => Dave Jones (waveform)

** Changed in: ubuntu-settings (Ubuntu)
Milestone: None => ubuntu-23.04

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

Title:
  On rpi desktop images, grow root leaving slack for LUKS

Status in ubuntu-settings package in Ubuntu:
  New

Bug description:
  To aid in user-implemented FDE we wish to leave 16MB of the file-
  system unexpanded during first boot. The growth of the partition is
  unaffected, but rather than relying on systemd's growfs facility in
  fstab, we should use a service that runs a simple script to handle
  calculating the resize in early boot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/2013080/+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 2001568] Re: unattended-upgrades 2.9.1+nmu2ubuntu1 failing autopkgtest on arm64

2023-02-13 Thread Dave Jones

It looks like Debian independently fixed the running_escape_regexp line
in January (in 2.9.1+nmu3 [1]). The d/t/control fix isn't *strictly*
necessary to fix this and is more a matter of fixing semantics -- but
I'll try and forward that change if I can figure out where to submit a
PR (doesn't appear u-u is in salsa, and the GH Vcs-Git repo is way
behind where it's meant to be).

[1]: https://tracker.debian.org/news/1405664/accepted-unattended-
upgrades-291nmu3-source-into-unstable/

** Changed in: unattended-upgrades (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 unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/2001568

Title:
  unattended-upgrades 2.9.1+nmu2ubuntu1 failing autopkgtest on arm64

Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  u-u is currently failing autopkgtest on arm64. It does not look like
  this is a new failure (2.8ubuntu1 appears to have had exactly the same
  failure) but it's due to the kernel-patterns test assuming that kernel
  flavors cannot be a suffix of each other. This is true under Debian,
  and under several architectures on Ubuntu, but the arm64 architecture
  on Ubuntu has -generic and -generic-64k flavors which cause the test
  to fail.

  The attached debdiff corrects the test for this case.

  One may wonder why the test currently passes under armhf, which has
  -generic and -generic-lpae flavors (I certainly did!). It turns out
  this is only because Ubuntu autopkgtest runs armhf in a container so
  the kernel release reported by "uname -r" (used in the test) does not
  meaningfully match anything in the apt cache.

  Given this, the attached debdiff also restricts the kernel-patterns
  test to isolation-machine as the test assumes a meaningful link
  between the running kernel and the packages in the archive which is
  only true in a VM or on the bare metal.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/2001568/+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 2006669] Re: Asynchronous wait on fence ... timed out (hint:intel_atomic_commit_ready [i915])

Looking at mesa git staging/23.0 it looks like 78a75e0d2 and 4c986c58b
may also be required.

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

Title:
  Asynchronous wait on fence ... timed out
  (hint:intel_atomic_commit_ready [i915])

Status in mesa package in Ubuntu:
  New
Status in mesa source package in Jammy:
  New
Status in mesa source package in Kinetic:
  New
Status in mesa source package in Lunar:
  New

Bug description:
  GUI hard lock during zoom session and gnome-terminal

  kern.log shows a mix of errors 
  __
  kernel: [ 3627.948545] Asynchronous wait on fence 
:00:02.0:gnome-shell[4236]:40810 timed out (hint:intel_atomic_commit_ready 
[i915])
  kernel: [ 3631.063832] i915 :00:02.0: [drm] GPU HANG: ecode 
12:1:85db, in chrome [5521]
  kernel: [ 3631.064218] i915 :00:02.0: [drm] Resetting chip for stopped 
heartbeat on rcs0
  kernel: [ 3631.165642] i915 :00:02.0: [drm] chrome[5521] context reset 
due to GPU hang
  kernel: [ 3631.165719] i915 :00:02.0: [drm] GuC firmware 
i915/adlp_guc_70.1.1.bin version 70.1
  kernel: [ 3631.165725] i915 :00:02.0: [drm] HuC firmware 
i915/tgl_huc_7.9.3.bin version 7.9
  kernel: [ 3631.187377] i915 :00:02.0: [drm] HuC authenticated
  kernel: [ 3631.187670] i915 :00:02.0: [drm] GuC submission enabled
  kernel: [ 3631.187672] i915 :00:02.0: [drm] GuC SLPC enabled
  ___

  I suspect this issue to be 
  upstream: https://gitlab.freedesktop.org/mesa/mesa/-/issues/7755
  upstream commit: 
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/20169/commits?commit_id=b9403b1c477e7af04114ae6a4e16ca370e22253c#d6ffde011ad32c6371611e7d64affaeb21b6b217

  Reproducer: Although I don't have my own reproducer, the upstream mesa
  reproducer does trigger a hang on my machine.

  Upstream Reproducer: Open https://kartikmandhang.netlify.app/ when it
  loads, you will see pikachu. Press "S", he will go back.  My whole
  system freezes from this in Wayland, regardless of the browser.

  Kernel: 6.0.0-1008-oem
  Mesa: 22.2.5-0ubuntu0.1~22.04.1

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
  ProcVersionSignature: Ubuntu 6.0.0-1008.8-oem 6.0.9
  Uname: Linux 6.0.0-1008-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb  8 21:40:19 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] 
(rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0b1a]
 Subsystem: Dell Device [1028:0b1a]
  InstallationDate: Installed on 2022-07-13 (211 days ago)
  InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220421)
  MachineType: Dell Inc. Precision 5570
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.0.0-1008-oem 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro pcie_aspm=force quiet splash 
mem_sleep_default=deep vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/21/2022
  dmi.bios.release: 1.9
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.9.1
  dmi.board.name: 03M8N5
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.1:bd11/21/2022:br1.9:svnDellInc.:pnPrecision5570:pvr:rvnDellInc.:rn03M8N5:rvrA00:cvnDellInc.:ct10:cvr:sku0B1A:
  dmi.product.family: Precision
  dmi.product.name: Precision 5570
  dmi.product.sku: 0B1A
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


-- 
Mailing list: https://launchpad.net/~touch-packages
Post to :

[Touch-packages] [Bug 2006669] Re: Asynchronous wait on fence ... timed out (hint:intel_atomic_commit_ready [i915])

The above referenced commits are committed into mesa 23.0.0.   I see
references to backports of this onto stable, but I'm not familiar enough
with mesa as a project just yet.

** Also affects: mesa (Ubuntu Lunar)
   Importance: Undecided
 Assignee: Dave Chiluk (chiluk)
   Status: New

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

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

** Changed in: mesa (Ubuntu Jammy)
 Assignee: (unassigned) => Dave Chiluk (chiluk)

** Changed in: mesa (Ubuntu Lunar)
 Assignee: Dave Chiluk (chiluk) => (unassigned)

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

Title:
  Asynchronous wait on fence ... timed out
  (hint:intel_atomic_commit_ready [i915])

Status in mesa package in Ubuntu:
  New
Status in mesa source package in Jammy:
  New
Status in mesa source package in Kinetic:
  New
Status in mesa source package in Lunar:
  New

Bug description:
  GUI hard lock during zoom session and gnome-terminal

  kern.log shows a mix of errors 
  __
  kernel: [ 3627.948545] Asynchronous wait on fence 
:00:02.0:gnome-shell[4236]:40810 timed out (hint:intel_atomic_commit_ready 
[i915])
  kernel: [ 3631.063832] i915 :00:02.0: [drm] GPU HANG: ecode 
12:1:85db, in chrome [5521]
  kernel: [ 3631.064218] i915 :00:02.0: [drm] Resetting chip for stopped 
heartbeat on rcs0
  kernel: [ 3631.165642] i915 :00:02.0: [drm] chrome[5521] context reset 
due to GPU hang
  kernel: [ 3631.165719] i915 :00:02.0: [drm] GuC firmware 
i915/adlp_guc_70.1.1.bin version 70.1
  kernel: [ 3631.165725] i915 :00:02.0: [drm] HuC firmware 
i915/tgl_huc_7.9.3.bin version 7.9
  kernel: [ 3631.187377] i915 :00:02.0: [drm] HuC authenticated
  kernel: [ 3631.187670] i915 :00:02.0: [drm] GuC submission enabled
  kernel: [ 3631.187672] i915 :00:02.0: [drm] GuC SLPC enabled
  ___

  I suspect this issue to be 
  upstream: https://gitlab.freedesktop.org/mesa/mesa/-/issues/7755
  upstream commit: 
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/20169/commits?commit_id=b9403b1c477e7af04114ae6a4e16ca370e22253c#d6ffde011ad32c6371611e7d64affaeb21b6b217

  Reproducer: Although I don't have my own reproducer, the upstream mesa
  reproducer does trigger a hang on my machine.

  Upstream Reproducer: Open https://kartikmandhang.netlify.app/ when it
  loads, you will see pikachu. Press "S", he will go back.  My whole
  system freezes from this in Wayland, regardless of the browser.

  Kernel: 6.0.0-1008-oem
  Mesa: 22.2.5-0ubuntu0.1~22.04.1

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
  ProcVersionSignature: Ubuntu 6.0.0-1008.8-oem 6.0.9
  Uname: Linux 6.0.0-1008-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb  8 21:40:19 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] 
(rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0b1a]
 Subsystem: Dell Device [1028:0b1a]
  InstallationDate: Installed on 2022-07-13 (211 days ago)
  InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220421)
  MachineType: Dell Inc. Precision 5570
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.0.0-1008-oem 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro pcie_aspm=force quiet splash 
mem_sleep_default=deep vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/21/2022
  dmi.bios.release: 1.9
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.9.1
  dmi.board.name: 03M8N5
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.1:bd11/21/2022:br1.9:svnDellInc.:pnPrecision5570:pvr:rvnDellInc.:rn03M8N5:rvrA00:cvnDellInc.:ct10:cvr:sku0B1A:
  dmi.product.family: Precision
  dmi.product.name: Precision 5570
  dmi.product.sku: 0B1A
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1
  version.xserver-xorg-core:

[Touch-packages] [Bug 2006669] Re: Asynchronous wait on fence ... timed out (hint:intel_atomic_commit_ready [i915])

** Tags added: indeed

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

Title:
  Asynchronous wait on fence ... timed out
  (hint:intel_atomic_commit_ready [i915])

Status in mesa package in Ubuntu:
  New

Bug description:
  GUI hard lock during zoom session and gnome-terminal

  kern.log shows a mix of errors 
  __
  kernel: [ 3627.948545] Asynchronous wait on fence 
:00:02.0:gnome-shell[4236]:40810 timed out (hint:intel_atomic_commit_ready 
[i915])
  kernel: [ 3631.063832] i915 :00:02.0: [drm] GPU HANG: ecode 
12:1:85db, in chrome [5521]
  kernel: [ 3631.064218] i915 :00:02.0: [drm] Resetting chip for stopped 
heartbeat on rcs0
  kernel: [ 3631.165642] i915 :00:02.0: [drm] chrome[5521] context reset 
due to GPU hang
  kernel: [ 3631.165719] i915 :00:02.0: [drm] GuC firmware 
i915/adlp_guc_70.1.1.bin version 70.1
  kernel: [ 3631.165725] i915 :00:02.0: [drm] HuC firmware 
i915/tgl_huc_7.9.3.bin version 7.9
  kernel: [ 3631.187377] i915 :00:02.0: [drm] HuC authenticated
  kernel: [ 3631.187670] i915 :00:02.0: [drm] GuC submission enabled
  kernel: [ 3631.187672] i915 :00:02.0: [drm] GuC SLPC enabled
  ___

  I suspect this issue to be 
  upstream: https://gitlab.freedesktop.org/mesa/mesa/-/issues/7755
  upstream commit: 
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/20169/commits?commit_id=b9403b1c477e7af04114ae6a4e16ca370e22253c#d6ffde011ad32c6371611e7d64affaeb21b6b217

  Reproducer: Although I don't have my own reproducer, the upstream mesa
  reproducer does trigger a hang on my machine.

  Upstream Reproducer: Open https://kartikmandhang.netlify.app/ when it
  loads, you will see pikachu. Press "S", he will go back.  My whole
  system freezes from this in Wayland, regardless of the browser.

  Kernel: 6.0.0-1008-oem
  Mesa: 22.2.5-0ubuntu0.1~22.04.1

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
  ProcVersionSignature: Ubuntu 6.0.0-1008.8-oem 6.0.9
  Uname: Linux 6.0.0-1008-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb  8 21:40:19 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] 
(rev 0c) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:0b1a]
 Subsystem: Dell Device [1028:0b1a]
  InstallationDate: Installed on 2022-07-13 (211 days ago)
  InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220421)
  MachineType: Dell Inc. Precision 5570
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.0.0-1008-oem 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro pcie_aspm=force quiet splash 
mem_sleep_default=deep vt.handoff=7
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/21/2022
  dmi.bios.release: 1.9
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.9.1
  dmi.board.name: 03M8N5
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.1:bd11/21/2022:br1.9:svnDellInc.:pnPrecision5570:pvr:rvnDellInc.:rn03M8N5:rvrA00:cvnDellInc.:ct10:cvr:sku0B1A:
  dmi.product.family: Precision
  dmi.product.name: Precision 5570
  dmi.product.sku: 0B1A
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2006669/+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 2006669] [NEW] Asynchronous wait on fence ... timed out (hint:intel_atomic_commit_ready [i915])

Public bug reported:

GUI hard lock during zoom session and gnome-terminal

kern.log shows a mix of errors 
__
kernel: [ 3627.948545] Asynchronous wait on fence 
:00:02.0:gnome-shell[4236]:40810 timed out (hint:intel_atomic_commit_ready 
[i915])
kernel: [ 3631.063832] i915 :00:02.0: [drm] GPU HANG: ecode 12:1:85db, 
in chrome [5521]
kernel: [ 3631.064218] i915 :00:02.0: [drm] Resetting chip for stopped 
heartbeat on rcs0
kernel: [ 3631.165642] i915 :00:02.0: [drm] chrome[5521] context reset due 
to GPU hang
kernel: [ 3631.165719] i915 :00:02.0: [drm] GuC firmware 
i915/adlp_guc_70.1.1.bin version 70.1
kernel: [ 3631.165725] i915 :00:02.0: [drm] HuC firmware 
i915/tgl_huc_7.9.3.bin version 7.9
kernel: [ 3631.187377] i915 :00:02.0: [drm] HuC authenticated
kernel: [ 3631.187670] i915 :00:02.0: [drm] GuC submission enabled
kernel: [ 3631.187672] i915 :00:02.0: [drm] GuC SLPC enabled
___

I suspect this issue to be 
upstream: https://gitlab.freedesktop.org/mesa/mesa/-/issues/7755
upstream commit: 
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/20169/commits?commit_id=b9403b1c477e7af04114ae6a4e16ca370e22253c#d6ffde011ad32c6371611e7d64affaeb21b6b217

Reproducer: Although I don't have my own reproducer, the upstream mesa
reproducer does trigger a hang on my machine.

Upstream Reproducer: Open https://kartikmandhang.netlify.app/ when it
loads, you will see pikachu. Press "S", he will go back.  My whole
system freezes from this in Wayland, regardless of the browser.

Kernel: 6.0.0-1008-oem
Mesa: 22.2.5-0ubuntu0.1~22.04.1

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
ProcVersionSignature: Ubuntu 6.0.0-1008.8-oem 6.0.9
Uname: Linux 6.0.0-1008-oem x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb  8 21:40:19 2023
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation Alder Lake-P Integrated Graphics Controller [8086:46a6] (rev 
0c) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:0b1a]
   Subsystem: Dell Device [1028:0b1a]
InstallationDate: Installed on 2022-07-13 (211 days ago)
InstallationMedia: Ubuntu-Server 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220421)
MachineType: Dell Inc. Precision 5570
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.0.0-1008-oem 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro pcie_aspm=force quiet splash 
mem_sleep_default=deep vt.handoff=7
SourcePackage: mesa
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/21/2022
dmi.bios.release: 1.9
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.9.1
dmi.board.name: 03M8N5
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.9.1:bd11/21/2022:br1.9:svnDellInc.:pnPrecision5570:pvr:rvnDellInc.:rn03M8N5:rvrA00:cvnDellInc.:ct10:cvr:sku0B1A:
dmi.product.family: Precision
dmi.product.name: Precision 5570
dmi.product.sku: 0B1A
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.5-0ubuntu0.1~22.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 22.2.5-0ubuntu0.1~22.04.1
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

** Affects: mesa (Ubuntu)
 Importance: Undecided
 Assignee: Dave Chiluk (chiluk)
 Status: New


** Tags: amd64 apport-bug jammy ubuntu uec-images wayland-session

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

Title:
  Asynchronous wait on fence ... timed out
  (hint:intel_atomic_commit_ready [i915])

Status in mesa package in Ubuntu:
  New

Bug description:
  GUI hard lock during zoom session and gnome-terminal

  kern.log shows a mix of errors 
  __
  kernel: [ 3627.948545] Asynchronous wait on fence 
:00:02.0:gnome-shell[4236]:40810 timed out (hint:intel_atomic_commit_ready 
[i915])
  kernel: [ 3631.063832] i915 :00:02.0: [drm] GPU HANG: ecode 
12:1:85db, in ch

[Touch-packages] [Bug 1211700] Re: [gallium] EGL clients using a gallium driver (radeon, nouveau, freedreno) that saturate the GPU cause the Mir server to slow, freeze and stutter, displaying very few