[Touch-packages] [Bug 1988819] Re: When apt keeps back packages due to phased updates, it should say nothing

[Davison Long]

I for one don't like the idea of hiding the phased update info unless
there is also a flag to show it.  Not showing the info at all just
obscures the issue even more and would lead to a lot of unnecessary
confusion when odd situations might occur.

I also think it would be far better to have a separate non-translated
message for packages held back due to phased updates and then add
translations later.  The current confusion is occurring world-wide; an
English message about in process phased updates is going to provide a
lot more useful info to a non-English speaker than what is happening
now.  Like others have mentioned, I also am a long-time Debian and
Ubuntu user and this issue took WAY longer than it should have for me to
understand what was actually going on since there was absolutely NO
notices or info about phased updates at all in any apt commands or
config files (except for apt policy on a specific package).

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

Title:
  When apt keeps back packages due to phased updates, it should say
  nothing

Status in apt package in Ubuntu:
  Triaged

Bug description:
  After phased updates have been introduced, it may happen that apt
  upgrade shows packages as upgradable but ends up not upgrading them.
  In this case the packages are indicated as being "kept back".

  Unfortunately, the feedback provided about this to the user is not
  very informative. The user sees the packages being kept back and
  thinks something is going wrong on the system.

  When packages are kept back because of phased updates, apt should say
  so e.g., it should say that the upgrade is delayed.

  Incidentally note that aptitude does not respect phased updates.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apt 2.4.7
  ProcVersionSignature: Ubuntu 5.15.0-47.51-generic 5.15.46
  Uname: Linux 5.15.0-47-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Tue Sep  6 10:05:14 2022
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2020-02-16 (933 days ago)
  InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: apt
  UpgradeStatus: Upgraded to jammy on 2022-06-03 (94 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1988819/+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 1937110] Re: dhcp option 121 & 249

[Mauricio Faria de Oliveira]

Uploaded to Jammy/Focal.

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

Title:
  dhcp option 121 & 249

Status in subiquity:
  New
Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Focal:
  In Progress
Status in isc-dhcp source package in Jammy:
  In Progress

Bug description:
  [Impact]

   * DHCP classless static routes aren't applied
 by dhclient at the initramfs (e.g., ip=dhcp).

   * This happens as rfc3442-classless-routes is
 not copied to /etc/dhcp/dhclient-exit-hooks.d/
 in the initramfs.

   * On Jammy, if such DHCP option(s) are present
 in the DHCP server response, the DHCP client
 ignores the 'routers' option from the server,
 thus leaving no routes configured.

   * On Focal, the older code still adds 'routers',
 which is slightly better, but still does not
 add the classless static routes.

  [Test Plan]

   * Use LXD container/VMs for DHCP server/client,
 configure the DHCP server with option 121,
 and some sample classless static routes.
 (see comments #12/jammy and #13/focal).

  [Regression Potential]

   * Acquisition of DHCP leases/routes at initramfs
 with ip=dhcp.

   * The code/script is not new, and is exercised
 normally during on rootfs (ie, post-initramfs)
 when dhclient is run.

   * It's also been in the initramfs in Kinetic
 already, since on Aug 2022; giving it tests.

  [Original Description]
  Hello,

  I'm running into issues with subiquity on a cloud provider.  The cloud
  provider is using an on-link L3 gateway.

  His DHCP response looks like this:

  OPTION:  53 (  1) DHCP message type 5 (DHCPACK)
  OPTION:  54 (  4) Server identifier 172.31.1.1
  OPTION:  51 (  4) IP address leasetime  86400 (24h)
  OPTION:   1 (  4) Subnet mask   255.255.255.255
  OPTION:   3 (  4) Routers   172.31.1.1
  OPTION:   6 ( 12) DNS server
  OPTION: 121 ( 14) Classless Static Route20ac1f010100  ...
   ac1f0101 ..
  OPTION: 249 ( 14) MSFT - Classless route20ac1f010100  ...
   ac1f0101 ..

  Im booting the subiquity process with an patched ipxe
  (https://github.com/ipxe/ipxe/pull/104) like this:

  #!ipxe
  kernel .../vmlinuz initrd=initrd root=/dev/ram0 ramdisk_size=150 ip=dhcp 
url=https://cdimage.ubuntu.com/ubuntu-server/focal/daily-live/current/focal-live-server-amd64.iso
 autoinstall ds=nocloud-net;s=.../...-ad-78/ cloud-config-url=/dev/null
  initrd .../initrd
  boot

  initrd/vmlinuz is extracted right out of focal-live-server-amd64.iso

  Sadly subiquity is stuck with a broken network (because of missing
  dhcp option 121/249 support). It happens when its running the /init
  from the kernel right after kernel is booted, i guess even before the
  subiquity is started(?).

  After further debugging, it looks like the provided kernel 5.4.80 #90
  Ubuntu, is using busybox 1.30.1-4ubuntu~6.3 which includes isc-
  dhclient-4.4.1 which is lacking the given options.

  Would be awesome if this could be fixed.. maybe just a simple busybox
  compile option?

To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/1937110/+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 1937110] Re: dhcp option 121 & 249

[Mauricio Faria de Oliveira]

Reproducer with DHCP server/client on LXD. [Focal]

Bridge
---

sudo ip link add focalbr type bridge
sudo ip link set focalbr up


LXD container for DHCP server with classless static routes option
---

lxc init ubuntu:focal focal-dhcpd
lxc config device add focal-dhcpd eth0 nic nictype=bridged 
parent=focalbr
lxc config device add focal-dhcpd eth1 nic nictype=bridged parent=lxdbr0

lxc start focal-dhcpd
lxc shell focal-dhcpd

dhclient eth1

...

ip addr add 10.11.12.13/24 dev eth0

apt install -y isc-dhcp-server

echo 'INTERFACESv4="eth0"' >>/etc/default/isc-dhcp-server

cat <>/etc/dhcp/dhcpd.conf
option rfc3442-classless-static-routes code 121 = array of integer 8;

subnet 10.11.12.0 netmask 255.255.255.0 {

  range 10.11.12.100 10.11.12.110;

  option routers 10.11.12.13;

  option rfc3442-classless-static-routes
0,  10, 11, 12, 200,
8,  1,  10, 11, 12, 208,
16, 2, 1,   10, 11, 12, 216,
24, 3, 2, 1,10, 11, 12, 224,
32, 4, 3, 2, 1, 10, 11, 12, 232;
}
EOF

systemctl restart isc-dhcp-server.service


LXD VM for DHCP client
---

lxc init ubuntu:focal focal-dhclient --vm
lxc config device add focal-dhclient eth0 nic nictype=bridged 
parent=focalbr
# no regular lxdbr0 bridge / internet access.

lxc start focal-dhclient
lxc shell focal-dhclient

# ip link
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN 
mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp5s0:  mtu 1500 qdisc mq state UP 
mode DEFAULT group default qlen 1000
link/ether 00:16:3e:36:6b:c8 brd ff:ff:ff:ff:ff:ff

# ip addr
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN 
group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
   valid_lft forever preferred_lft forever
2: enp5s0:  mtu 1500 qdisc mq state UP 
group default qlen 1000
link/ether 00:16:3e:36:6b:c8 brd ff:ff:ff:ff:ff:ff
inet 10.11.12.101/24 brd 10.11.12.255 scope global dynamic enp5s0
   valid_lft 582sec preferred_lft 582sec
inet6 fe80::216:3eff:fe36:6bc8/64 scope link
   valid_lft forever preferred_lft forever

# ip route
default via 10.11.12.200 dev enp5s0 proto dhcp src 10.11.12.101 metric 
100
1.0.0.0/8 via 10.11.12.208 dev enp5s0 proto dhcp src 10.11.12.101 
metric 100
2.1.0.0/16 via 10.11.12.216 dev enp5s0 proto dhcp src 10.11.12.101 
metric 100
3.2.1.0/24 via 10.11.12.224 dev enp5s0 proto dhcp src 10.11.12.101 
metric 100
4.3.2.1 via 10.11.12.232 dev enp5s0 proto dhcp src 10.11.12.101 metric 
100
10.11.12.0/24 dev enp5s0 proto kernel scope link src 10.11.12.101

Ok, all good from booted system's perspective.

Let's check at initramfs time, manually.

The classless routes aren't added if you run dhclient at the current
version.

cat 

[Touch-packages] [Bug 1937110] Re: dhcp option 121 & 249

[Mauricio Faria de Oliveira]

Reproducer with DHCP server/client on LXD. [Jammy]

Bridge
---

sudo ip link add jammybr type bridge
sudo ip link set jammybr up


LXD container for DHCP server with classless static routes option
---

lxc init ubuntu:jammy jammy-dhcpd
lxc config device add jammy-dhcpd eth0 nic nictype=bridged 
parent=jammybr
lxc config device add jammy-dhcpd eth1 nic nictype=bridged parent=lxdbr0

lxc start jammy-dhcpd
lxc shell jammy-dhcpd

dhclient eth1

...

ip addr add 10.11.12.13/24 dev eth0

apt install -y isc-dhcp-server

echo 'INTERFACESv4="eth0"' >>/etc/default/isc-dhcp-server

cat <>/etc/dhcp/dhcpd.conf
option rfc3442-classless-static-routes code 121 = array of integer 8;

subnet 10.11.12.0 netmask 255.255.255.0 {

  range 10.11.12.100 10.11.12.110;

  option routers 10.11.12.13;

  option rfc3442-classless-static-routes
0,  10, 11, 12, 200,
8,  1,  10, 11, 12, 208,
16, 2, 1,   10, 11, 12, 216,
24, 3, 2, 1,10, 11, 12, 224,
32, 4, 3, 2, 1, 10, 11, 12, 232;
}
EOF

systemctl restart isc-dhcp-server.service


LXD VM for DHCP client
---

lxc init ubuntu:jammy jammy-dhclient --vm
lxc config device add jammy-dhclient eth0 nic nictype=bridged 
parent=jammybr
# no regular lxdbr0 bridge / internet access.

lxc start jammy-dhclient
lxc shell jammy-dhclient

# ip link
...
2: enp5s0:  mtu 1500 qdisc mq state UP 
mode DEFAULT group default qlen 1000
link/ether 00:16:3e:e8:3e:4d brd ff:ff:ff:ff:ff:ff

# ip addr
...
2: enp5s0:  mtu 1500 qdisc mq state UP 
group default qlen 1000
link/ether 00:16:3e:e8:3e:4d brd ff:ff:ff:ff:ff:ff
inet 10.11.12.102/24 metric 100 brd 10.11.12.255 scope global 
dynamic enp5s0
   valid_lft 551sec preferred_lft 551sec
inet6 fe80::216:3eff:fee8:3e4d/64 scope link
   valid_lft forever preferred_lft forever

# ip route
default via 10.11.12.200 dev enp5s0 proto dhcp src 10.11.12.102 metric 
100
1.0.0.0/8 via 10.11.12.208 dev enp5s0 proto dhcp src 10.11.12.102 
metric 100
2.1.0.0/16 via 10.11.12.216 dev enp5s0 proto dhcp src 10.11.12.102 
metric 100
3.2.1.0/24 via 10.11.12.224 dev enp5s0 proto dhcp src 10.11.12.102 
metric 100
4.3.2.1 via 10.11.12.232 dev enp5s0 proto dhcp src 10.11.12.102 metric 
100
10.11.12.0/24 dev enp5s0 proto kernel scope link src 10.11.12.102 
metric 100
10.11.12.200 dev enp5s0 proto dhcp scope link src 10.11.12.102 metric 
100
10.11.12.208 dev enp5s0 proto dhcp scope link src 10.11.12.102 metric 
100
10.11.12.216 dev enp5s0 proto dhcp scope link src 10.11.12.102 metric 
100
10.11.12.224 dev enp5s0 proto dhcp scope link src 10.11.12.102 metric 
100
10.11.12.232 dev enp5s0 proto dhcp scope link src 10.11.12.102 metric 
100

Ok, all good from booted system's perspective.

Let's check at initramfs time, manually.

The classless routes aren't added if you run dhclient at the current
version.

cat 

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

[Daniel van Vugt]

OTOH, it's a trivial revert in mutter 44 to drop the new glib
dependency.

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

Title:
  Update to glib >= 2.75.1

Status in glib2.0 package in Ubuntu:
  Triaged

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

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


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

[Touch-packages] [Bug 1988730] Re: package libsasl2-modules provides only unsafe SASL bind mechanims

[Chris Halse Rogers]

Hello rdratlos, or anyone else affected,

Accepted cyrus-sasl2 into jammy-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/cyrus-
sasl2/2.1.27+dfsg2-3ubuntu1.2 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: cyrus-sasl2 (Ubuntu Jammy)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-jammy

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

Title:
  package libsasl2-modules provides only unsafe SASL bind mechanims

Status in cyrus-sasl2 package in Ubuntu:
  Fix Released
Status in cyrus-sasl2 source package in Jammy:
  Fix Committed
Status in cyrus-sasl2 package in Debian:
  Fix Released

Bug description:
  [ Impact ]

  The SASL SCRAM mechanism is incorrectly part of the libsasl2-modules-
  gssapi-mit package. It has nothing to do with MIT or GSSAPI, and
  should be in libsasl2-modules.

  Normally this would just be an annoyance, but it just so happens that
  this also prevents to have the SCRAM mechanism coexist with the GSSAPI
  Heimdal one, because libsasl2-modules-gssapi-{mit,heimdal} conflict
  with each other.

  This change is moving a file from one package to another, so
  appropriate breaks/replaces changes have to be made. This move follows
  case #10 from the package transition table[1].

  [ Test Plan ]

  This test plan revolves around dependency checking and upgrades, to make sure 
we don't:
  - have conflicting files which would break an upgrade
  - have no loss of functionality after an upgrade (since a plugin moved 
between packages)

  a) SCRAM remains installed
  # Install the package that provides SCRAM in jammy

  $ sudo apt install libsasl2-modules-gssapi-mit

  # Confirm mechanism is there and belongs to libsasl2-modules-gssapi-
  mit:

  $ ll /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
  lrwxrwxrwx 1 root root 18 Aug 16 20:08 
/usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2 -> libscram.so.2.0.25

  $ dpkg -S /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
  libsasl2-modules-gssapi-mit:amd64: 
/usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2

  # list installed sasl2 packages:
  $ dpkg -l | grep -E "^ii.*sasl2" | awk '{print $2,$3}'
  libsasl2-2:amd64 2.1.27+dfsg2-3ubuntu1.1
  libsasl2-modules:amd64 2.1.27+dfsg2-3ubuntu1.1
  libsasl2-modules-db:amd64 2.1.27+dfsg2-3ubuntu1.1
  libsasl2-modules-gssapi-mit:amd64 2.1.27+dfsg2-3ubuntu1.1

  # dist-upgrade or install the new sasl2 packages from proposed
  # Confirm the same packages are installed as before the upgrade, just at 
their newer versions:
  libsasl2-2:amd64 2.1.27+dfsg2-3ubuntu1.2
  libsasl2-modules:amd64 2.1.27+dfsg2-3ubuntu1.2
  libsasl2-modules-db:amd64 2.1.27+dfsg2-3ubuntu1.2
  libsasl2-modules-gssapi-mit:amd64 2.1.27+dfsg2-3ubuntu1.2

  # Confirm the scram mechanism is still there, as before:

  $ ll /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
  lrwxrwxrwx 1 root root 18 Aug 16 20:08 
/usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2 -> libscram.so.2.0.25

  # But now it belongs to the libsasl2-modules package:
  $ dpkg -S /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
  libsasl2-modules:amd64: /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2

  b) Following (a), perform a release-upgrade to kinetic, and confirm
  that the same sasl2 packages remain installed, but now at the kinetic
  version:

  $ dpkg -l | grep -E "^ii.*sasl2" | awk '{print $2,$3}'
  libsasl2-2:amd64 2.1.28+dfsg-6ubuntu2
  libsasl2-modules:amd64 2.1.28+dfsg-6ubuntu2
  libsasl2-modules-db:amd64 2.1.28+dfsg-6ubuntu2
  libsasl2-modules-gssapi-mit:amd64 2.1.28+dfsg-6ubuntu2

  And that the scram mechanism is there, and still belongs to the
  libsasl2-modules package:

  $ ll /usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2
  lrwxrwxrwx 1 root root 18 Aug 16 20:08 
/usr/lib/x86_64-linux-gnu/sasl2/libscram.so.2 -> 

[Touch-packages] [Bug 1980937] Re: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] No sound except loud crackling (popping) noise

[Avik Topchyan]

Confirming this issue on

Host: HP ENVY x360 2-in-1 Laptop 13-bf0xxx
Kernel: 5.15.0-58-generic 

dmesg | grep -i speak
[5.793393] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC245: 
line_outs=2 (0x17/0x14/0x0/0x0/0x0) type:speaker
[5.793402] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)


I tried (after googling, but not sure what I am doing):

sudo xed /etc/modprobe.d/audiofix.conf

options snd_hda_intel dmic_detect=0
options snd_hda_intel model=laptop-amic enable=yes

and rebooting, but no effect whatsoever on spearkers.
Headphone jack works correctly.

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

Title:
  [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal]
  No sound except loud crackling (popping) noise

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  New laptop with fresh installation of Xubuntu 22.04. Intel Tiger Lake-
  LP audio controller. When playing any audio, the internal speaker
  plays no sound except periodic loud crackling noise. The 3.5mm jack
  does not work either, producing the same craclking noise alongside
  some eletrical noise. HDMI audio skimmishly tested, but also gave no
  sound. Curiously, USB headphone (along with microphone) works
  perfectly, also the internal microphone.

  As attempts to fix the problem, I have tried the following separately, with 
no avail:
  - Installing some Ubuntu OEM version of the 5.17 kernel
  - Updating to the v2.2 firmware from Sound Open Firmware Project 
(thesofproject on github), reverted afterwards

  I found exactly the same problem reported in the Fedora community:
  
https://forums.fedoraforum.org/showthread.php?328627-HP-Elitebook-840-G8-Tiger-Lake-audio-only-produces-popping-sound=1860086

  As the pre-installed Windows has been destroyed, no further test on
  Windows has been done.

  Since USB headphone and internal microphone work, I think that there
  is no problem on the Intel Tiger Lake-LP controller and its driver.
  The bug probably lies elsewhere, like in the handling of ALC245 on
  this new laptop model.

  Thank you very much for your time and effort in advance.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
  Uname: Linux 5.15.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fwjmath2810 F pulseaudio
fwjmath   72467 F alsamixer
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Thu Jul  7 10:59:22 2022
  InstallationDate: Installed on 2022-06-29 (7 days ago)
  InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed
  Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - 
sof-hda-dsp
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fwjmath2810 F pulseaudio
fwjmath   72467 F alsamixer
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] 
No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/05/2022
  dmi.bios.release: 9.1
  dmi.bios.vendor: HP
  dmi.bios.version: T37 Ver. 01.09.01
  dmi.board.name: 8AB8
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 58.03.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 88.3
  dmi.modalias: 
dmi:bvnHP:bvrT37Ver.01.09.01:bd05/05/2022:br9.1:efr88.3:svnHP:pnHPEliteBook840G8NotebookPC:pvr:rvnHP:rn8AB8:rvrKBCVersion58.03.00:cvnHP:ct10:cvr:sku6A3P3AV:
  dmi.product.family: 103C_5336AN HP EliteBook
  dmi.product.name: HP EliteBook 840 G8 Notebook PC
  dmi.product.sku: 6A3P3AV
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-07-02T17:07:35.783239

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1980937/+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 1926139] Re: dhclient: thread concurrency race leads to DHCPOFFER packets not being received

[Mauricio Faria de Oliveira]

>From the 'Where problems could occur' section.
Considerations on regressions and approaches.

[Where problems could occur]

isc-dhcp is a core package, and any change comes with the risk that
users would not be able to receive dhcp leases with dhclient, leaving
their systems with no IP address and unreachable, and could potentially
cripple images that depend on it, e.g. Microsoft Azure uses dhclient
called from cloud-init, instead of systemd-networkd, so a regression
could potentially affect all Ubuntu users on Azure.

Additionally, the code is called whenever sockets are constructed, and
isc-dhcp-server could also be affected.

We have mitigated the risks of regression as best as possible by adding
as much detail as possible to this launchpad bug, so it is clear how the
race operates and how the patch fixes the issue.

Mauricio has additionally added a environment variable and a kernel
command line parameter, that when present, disables the fix from
operating. If a regression were to occur, users can add these parameters
to their deployments to work around any issues.

Mauricio and Matthew have decided that the individual fix route is best
in terms of lessening regression risk, as the alternate solution would
be to disable threading on bind9-libs.

Disabling threading on bind9-libs, while complete as a solution, and
removes the risk of a future regression caused by thread concurrency
issues that are currently undetected, comes with the fact that it
removes publicly exported symbols from bind9-libs, and adds others, and
changes the entire library from multithreaded to single threaded. If any
users happen to use bind9-libs outside of isc-dhcp, they would see their
applications either fail to work due to missing symbols, or performance
would change.

Disabling threading on bind9-libs is shelved, and can be looked at in
the future if necessary.

Back to the individual fix solution, Chris Patterson, has been testing
this solution at scale on Azure, and in 13k instances, has not had a
failure. With the gdb reproducer, we are confident that adding the mutex
will not prevent other parts of the software from functioning correctly.



** Description changed:

  [Impact]
  
- Occasionally, during instance boot or machine start-up, dhclient will
- attempt to acquire a dhcp lease and fail, leaving the instance with no
- IP address and making it unreachable.
+  * Occasionally, during instance boot or machine start-up,
+dhclient will attempt to acquire a dhcp lease and fail,
+leaving the instance with no IP address and making it
+unreachable.
  
- This happens about once every 100 reboots on bare metal, or Chris
- Patterson in comment #2 describes it as affecting between ~0.3% to 2% of
- deployments on Microsoft Azure. Azure uses dhclient called from cloud-
- init instead of systemd-networkd, and this is causing issues with larger
- deployments.
+  * This happens about once every 100 reboots on bare metal,
+or affecting between ~0.3% to 2% of deployments on Azure
+(comment #2).
+
+  * Azure uses dhclient called from cloud-init instead of
+systemd-networkd, and this is causing issues with larger
+deployments.
  
- The logs of an affected dhclient produce the following:
+  * The logs of an affected dhclient produce the following:
  
- Listening on LPF/enp1s0/52:54:00:1c:d7:00
- Sending on   LPF/enp1s0/52:54:00:1c:d7:00
- Sending on   Socket/fallback
- DHCPDISCOVER on enp1s0 to 255.255.255.255 port 67 interval 3 (xid=0xd222950f)
- DHCPDISCOVER on enp1s0 to 255.255.255.255 port 67 interval 5 (xid=0xd222950f)
- ...
- (omitting 20 similar lines)
- ...
- DHCPDISCOVER on enp1s0 to 255.255.255.255 port 67 interval 13 (xid=0xd222950f)
- DHCPDISCOVER on enp1s0 to 255.255.255.255 port 67 interval 8 (xid=0xd222950f)
- DHCPDISCOVER on enp1s0 to 255.255.255.255 port 67 interval 6 (xid=0xd222950f)
- No DHCPOFFERS received.
- No working leases in persistent database - sleeping.
+Listening on LPF/enp1s0/52:54:00:1c:d7:00
+Sending on   LPF/enp1s0/52:54:00:1c:d7:00
+Sending on   Socket/fallback
+DHCPDISCOVER on enp1s0 to 255.255.255.255 port 67 ...
+DHCPDISCOVER on enp1s0 to 255.255.255.255 port 67 ...
+...
+(omitting 20 similar lines)
+...
+DHCPDISCOVER on enp1s0 to 255.255.255.255 port 67 ...
+DHCPDISCOVER on enp1s0 to 255.255.255.255 port 67 ...
+DHCPDISCOVER on enp1s0 to 255.255.255.255 port 67 ...
+No DHCPOFFERS received.
+No working leases in persistent database - sleeping.
  
- Full log: https://paste.ubuntu.com/p/8yBfw2KR5h/
- Log of a working run: https://paste.ubuntu.com/p/N3ZgqrxyQD/
+  * This only impacts Focal and Jammy, where bind9-libs
+are multi-threaded (Bionic/earlier and Kinetic/later
+are single-threaded).
  
- The bizarre thing is when you tcpdump dhclient, we see all DHCPDISOVER
- packets being replied to with DHCPOFFER packets, but the got_one()
- callback is never called, dhclient does not read these DHCPOFFER
- packets, 

[Touch-packages] [Bug 1926139] Re: dhclient: thread concurrency race leads to DHCPOFFER packets not being received

[Mauricio Faria de Oliveira]

From the 'Other Info' section.
Detailed analysis of the issue and more.

[Other Info]

Full log: https://paste.ubuntu.com/p/8yBfw2KR5h/
Log of a working run: https://paste.ubuntu.com/p/N3ZgqrxyQD/

When you tcpdump dhclient, we see all DHCPDISCOVER packets being replied
to with DHCPOFFER packets, but the got_one() callback is never called,
dhclient does not read these DHCPOFFER packets, and continues sending
DHCPDISCOVER packets. Once it reaches 25 DHCPDISCOVER packets sent, it
gives up.

This behaviour led several bug reporters to believe it was a kernel
issue, with the kernel not pushing DHCPOFFER packets to dhclient. This
is not the case, the actual problem is dhclient containing a thread
concurrency race condition, and when the race occurs, the read socket is
closed prematurely, and dhclient does not read any of the DHCPOFFER
replies.

tcpdump: 'Screenshot of Wireshark' attached.

...

I was reading around the upstream issue trackers, and found the
following two bug reports:

https://gitlab.isc.org/isc-projects/dhcp/-/issues/264
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996356

The ISC upstream report was actually quite detailed, and it has the same
symptoms of what we are experiencing.

Let's have a look at the root cause. The code I am using is isc-dhcp
4.4.1-2.1ubuntu5.20.04.4 from Focal.

common/discover.c

 567 void
 568 discover_interfaces(int state) {
...
1002 case AF_INET:
1003 default:
1004 status = omapi_register_io_object((omapi_object_t *)tmp,
1005   if_readsocket,
1006   0, got_one, 0, 0);
1007 break;
1008 }
...

In discover.c, we call discover_interfaces() to iterate over the
interfaces, and attempt to register a raw socket against it. We do this
by calling omapi_register_io_object() which is used for reading data,
and calls the elusive got_one() callback that you instrumented your code
to see if it was being called or not.

omapip/dispatch.c

196 /* Register an I/O handle so that we can do asynchronous I/O on it. */
197
198 isc_result_t omapi_register_io_object (omapi_object_t *h,
199int (*readfd) (omapi_object_t *),
200int (*writefd) (omapi_object_t *),
201isc_result_t (*reader)
202 (omapi_object_t *),
203isc_result_t (*writer)
204 (omapi_object_t *),
205isc_result_t (*reaper)
206 (omapi_object_t *))
207 {
...
241 /*
242  * Attach the I/O object to the isc socket library via the
243  * fdwatch function.  This allows the socket library to watch
244  * over a socket that we built.  If there are both a read and
245  * a write socket we asssume they are the same socket.
246  */
247
248 if (readfd) {
249 fd_flags |= ISC_SOCKFDWATCH_READ;
250 fd = readfd(h);
251 }
...
257
258 if (fd_flags != 0) {
259 status = isc_socket_fdwatchcreate(dhcp_gbl_ctx.socketmgr,
260   fd, fd_flags,
261   omapi_iscsock_cb,
262   obj,
263   dhcp_gbl_ctx.task,
264   >fd);
...
275 }
276
277
278 /* Find the last I/O state, if there are any. */
279 for (p = omapi_io_states.next;
280  p && p -> next; p = p -> next)
281 ;
282 if (p)
283 omapi_io_reference ( -> next, obj, MDL);
284 else
285 omapi_io_reference (_io_states.next, obj, MDL);
...

omapi_register_io_object() is called for each socket created, in this
case, the if_readsocket from discover_interfaces(). The file descriptor
is assigned ISC_SOCKFDWATCH_READ, and we enter the if statement.

The if statement calls isc_socket_fdwatchcreate(), which registers the
socket with the ISC socket manager, and sets up the callback
omapi_iscsock_cb(), to be called.

Once that has been done, we iterate over the omapi_io_states linked
list, which is a global list of registered sockets. We get to the end of
the list (or the beginning, if the list is empty), and add the socket to
the list.

Now, the bug happens between calling isc_socket_fdwatchcreate() to
register the socket with the socket manager, and adding it to the global
linked list.

Sometimes, the callback omapi_iscsock_cb() is called inbetween.

omapip/dispatch.c

101 /*
102  * Callback routine to connect the omapi I/O object and socket with
103  * the isc socket code.  The isc socket code will call this routine
104  * which will then call the correct local routine to process the bytes.
105  *
106  * Currently we are always willing to read more data, this should be 
modified
107  * so that on connections we don't read more if we already have enough.
108  *
109  * If we have more bytes to write we ask the library to call us when
110  * we can write more.  If we indicate we don't have more to write 

[Touch-packages] [Bug 1926139] Re: dhclient: thread concurrency race leads to DHCPOFFER packets not being received

[Mauricio Faria de Oliveira]

Pressing Page Down 17 times to go over the bug description sounds like a
new record! ;-)

Just in case future reviewers don't find that as exciting while going
through reviews, I'll move some text into comments and reference them
from the description.

** Bug watch added: gitlab.isc.org/isc-projects/dhcp/-/issues #264
   https://gitlab.isc.org/isc-projects/dhcp/-/issues/264

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

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

Title:
  dhclient: thread concurrency race leads to DHCPOFFER packets not being
  received

Status in bind9-libs package in Ubuntu:
  Won't Fix
Status in isc-dhcp package in Ubuntu:
  Invalid
Status in isc-dhcp source package in Focal:
  In Progress
Status in isc-dhcp source package in Jammy:
  In Progress

Bug description:
  [Impact]

   * Occasionally, during instance boot or machine start-up,
 dhclient will attempt to acquire a dhcp lease and fail,
 leaving the instance with no IP address and making it
 unreachable.

   * This happens about once every 100 reboots on bare metal,
 or affecting between ~0.3% to 2% of deployments on Azure
 (comment #2).
 
   * Azure uses dhclient called from cloud-init instead of
 systemd-networkd, and this is causing issues with larger
 deployments.

   * The logs of an affected dhclient produce the following:

 Listening on LPF/enp1s0/52:54:00:1c:d7:00
 Sending on   LPF/enp1s0/52:54:00:1c:d7:00
 Sending on   Socket/fallback
 DHCPDISCOVER on enp1s0 to 255.255.255.255 port 67 ...
 DHCPDISCOVER on enp1s0 to 255.255.255.255 port 67 ...
 ...
 (omitting 20 similar lines)
 ...
 DHCPDISCOVER on enp1s0 to 255.255.255.255 port 67 ...
 DHCPDISCOVER on enp1s0 to 255.255.255.255 port 67 ...
 DHCPDISCOVER on enp1s0 to 255.255.255.255 port 67 ...
 No DHCPOFFERS received.
 No working leases in persistent database - sleeping.

   * This only impacts Focal and Jammy, where bind9-libs
 are multi-threaded (Bionic/earlier and Kinetic/later
 are single-threaded).

   * The actual problem is dhclient containing a thread
 concurrency race condition, and when the race occurs,
 the read socket is incorrectly/prematurely unwatched
 because required structures are not yet consistent,
 thus dhclient does not read any DHCPOFFER replies.

   * Detailed analysis of the issue is in comment #17.

  [Fix]

   * Prevent the race condition by starting to watch the
 read socket after required structures are consistent.
   
   * The fix has been tested in Azure w/ 13500 instances,
 and no errors have been observed (previously: 0.4%).
 
   * Anyway, in case regressions are observed, the patch
 introduces 2 switches to revert to previous behavior,
 which can be applied per-process or system-wide:
 - DHCP_FD_FLAGS_POKE=0 environment variable
 - dhcp.fd_flags_poke=0 kernel cmdline option 
   
   * (Previous approaches/discussions included reverting
  bind9-libs to single-threaded, but we concluded it
  would have more regression risk than the expected
  [some bits in comment #8, and some internal chat],
  and remove exported symbols (apparently unused, but).
  We also considered a mutex/spinlock approach, but
  later found a simpler way w/ isc lib; comment #13.)
  
  [Test Plan]

   * Synthetic reproducer with GDB to force the race
 condition, and DHCP server/client/noise injection
 is described in comment #9.
   
   * Test with the original package (problem occurs).
   
   * Test with the modified package (problem fixed).
 - Set DHCP_FD_FLAGS_POKE=0 (problem occurs).
 - Set dhcp.fd_flags_poke=0 (problem occurs).

  [Regression Potential]

   * 1) dhclient failing to acquire DHCP leases.
  
   * 2) dhcpd is also affected by code changes,
 thus failures to handle DHCP lease requests
 also have potential for regressions.
 
   * 3) the functional change added by the fix,
 if a regression were to occur, would likely
 be an issue only under some (unknown) race
 condition as well, thus expected to be rare.

   * Note: this potentially affects Focal/Jammy 
 on Azure as a whole, per usage of dhclient
 in cloud-init instead of systemd-networkd.
 
 Azure provided extensive testing for all 3
 approaches (mostly internal communications,
 and some bug comments), with ~13k instances.
 
 No issues were observed (previously: 0.4%).
 
   * Such testing scale seems to indicate that
 there are no regressions for dhclient to
 acquire DHCP leases (1), nor another race
 condition that hit the fix/new behavior (3).
 
 With that, apparently (2) should be OK too.
 
   * Also, so to mitigate the regression risk
 as 

[Touch-packages] [Bug 2004430] Re: Migrate raspberry pi image hacks from livecd-rootfs

[Dave Jones]

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

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

-- 
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:
  New
Status in ubuntu-settings package in Ubuntu:
  New

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 2004432] Re: GTK 3.2+ Theme mate-applications.css: segfault libcairo .mate-panel-menu-bar background-image: -gtk-gradient

[OwN]

Jan 31 13:17:41 -VirtualBox kernel: [ 3549.055408] traps: mate-
panel[3931] general protection fault ip:7f486e9721dc sp:7ffe38388ac8
error:0 in libcairo.so.2.11600.0[7f486e90d000+d3000]

** Also affects: mate-panel (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: gtk+3.0 (Ubuntu)

** Description changed:

  I maintain and update a GTK2/3+ theme (http://winxp4life.tk), and with
- the latest version of GTK3 in Ubuntu 22.04, my theme no longer works due
- to a segfault caused by this rule:
+ the latest version of GTK3, Mate, and mate-panel in Ubuntu 22.04, my
+ theme no longer works due to a segfault caused by this rule:
  
  .mate-panel-menu-bar {
- background-image: -gtk-gradient (linear,
-   left top,
-   left bottom,
-   from (#3168d5),
-   color-stop (0.15, #4490e6),
-   color-stop (0.30, #235bd9),
-   color-stop (0.90, #2562de),
-   to (#1941a5));
- background-color: @selected_bg_color_top_menu;
- padding: 0px;
- color: @bg_color;
- text-shadow: none;
+ background-image: -gtk-gradient (linear,
+   left top,
+   left bottom,
+   from (#3168d5),
+   color-stop (0.15, #4490e6),
+   color-stop (0.30, #235bd9),
+   color-stop (0.90, #2562de),
+   to (#1941a5));
+ background-color: @selected_bg_color_top_menu;
+ padding: 0px;
+ color: @bg_color;
+ text-shadow: none;
  }
  
  If I remove the background-image property, the theme works and the
  segfault doesn't happen.  It appears that any -gtk-gradient set on
  background-image for .mate-panel-menu-bar doesn't work and causes Mate
  to segfault.  I have to change the theme and restart to get things to
  work again.

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

Title:
  GTK 3.2+ Theme mate-applications.css:  segfault libcairo .mate-panel-
  menu-bar background-image: -gtk-gradient

Status in mate-panel package in Ubuntu:
  New

Bug description:
  I maintain and update a GTK2/3+ theme (http://winxp4life.tk), and with
  the latest version of GTK3, Mate, and mate-panel in Ubuntu 22.04, my
  theme no longer works due to a segfault caused by this rule:

  .mate-panel-menu-bar {
  background-image: -gtk-gradient (linear,
    left top,
    left bottom,
    from (#3168d5),
    color-stop (0.15, #4490e6),
    color-stop (0.30, #235bd9),
    color-stop (0.90, #2562de),
    to (#1941a5));
  background-color: @selected_bg_color_top_menu;
  padding: 0px;
  color: @bg_color;
  text-shadow: none;
  }

  If I remove the background-image property, the theme works and the
  segfault doesn't happen.  It appears that any -gtk-gradient set on
  background-image for .mate-panel-menu-bar doesn't work and causes Mate
  to segfault.  I have to change the theme and restart to get things to
  work again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mate-panel/+bug/2004432/+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 2004432] Re: GTK 3.2+ Theme mate-applications.css: segfault libcairo .mate-panel-menu-bar background-image: -gtk-gradient

[OwN]

Jan 31 13:17:41 -VirtualBox kernel: [ 3548.322902] mate-panel[1703]: segfault 
at 7f32e0027552 ip 7f32dfc671eb sp 7ffc063f08f8 error 7 in 
libcairo.so.2.11600.0[7f32dfc02000+d3000]
Jan 31 13:17:41 -VirtualBox kernel: [ 3548.322912] Code: 52 07 00 e8 87 c9 f9 
ff 0f 1f 80 00 00 00 00 f3 0f 1e fa 48 89 f8 48 85 ff 74 14 8b 57 18 83 fa ff 
74 0c 8b 57 18 85 d2 7e 06  83 47 18 01 c3 50 48 8d 0d 17 56 07 00 ba a2 03 
00 00 48 8d 35

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

Title:
  GTK 3.2+ Theme mate-applications.css:  segfault libcairo .mate-panel-
  menu-bar background-image: -gtk-gradient

Status in mate-panel package in Ubuntu:
  New

Bug description:
  I maintain and update a GTK2/3+ theme (http://winxp4life.tk), and with
  the latest version of GTK3, Mate, and mate-panel in Ubuntu 22.04, my
  theme no longer works due to a segfault caused by this rule:

  .mate-panel-menu-bar {
  background-image: -gtk-gradient (linear,
    left top,
    left bottom,
    from (#3168d5),
    color-stop (0.15, #4490e6),
    color-stop (0.30, #235bd9),
    color-stop (0.90, #2562de),
    to (#1941a5));
  background-color: @selected_bg_color_top_menu;
  padding: 0px;
  color: @bg_color;
  text-shadow: none;
  }

  If I remove the background-image property, the theme works and the
  segfault doesn't happen.  It appears that any -gtk-gradient set on
  background-image for .mate-panel-menu-bar doesn't work and causes Mate
  to segfault.  I have to change the theme and restart to get things to
  work again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mate-panel/+bug/2004432/+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 2004432] [NEW] GTK 3.2+ Theme mate-applications.css: segfault libcairo .mate-panel-menu-bar background-image: -gtk-gradient

[OwN]

Public bug reported:

I maintain and update a GTK2/3+ theme (http://winxp4life.tk), and with
the latest version of GTK3 in Ubuntu 22.04, my theme no longer works due
to a segfault caused by this rule:

.mate-panel-menu-bar {
background-image: -gtk-gradient (linear,
  left top,
  left bottom,
  from (#3168d5),
  color-stop (0.15, #4490e6),
  color-stop (0.30, #235bd9),
  color-stop (0.90, #2562de),
  to (#1941a5));
background-color: @selected_bg_color_top_menu;
padding: 0px;
color: @bg_color;
text-shadow: none;
}

If I remove the background-image property, the theme works and the
segfault doesn't happen.  It appears that any -gtk-gradient set on
background-image for .mate-panel-menu-bar doesn't work and causes Mate
to segfault.  I have to change the theme and restart to get things to
work again.

** Affects: gtk+3.0 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  GTK 3.2+ Theme mate-applications.css:  segfault libcairo .mate-panel-
  menu-bar background-image: -gtk-gradient

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  I maintain and update a GTK2/3+ theme (http://winxp4life.tk), and with
  the latest version of GTK3 in Ubuntu 22.04, my theme no longer works
  due to a segfault caused by this rule:

  .mate-panel-menu-bar {
  background-image: -gtk-gradient (linear,
left top,
left bottom,
from (#3168d5),
color-stop (0.15, #4490e6),
color-stop (0.30, #235bd9),
color-stop (0.90, #2562de),
to (#1941a5));
  background-color: @selected_bg_color_top_menu;
  padding: 0px;
  color: @bg_color;
  text-shadow: none;
  }

  If I remove the background-image property, the theme works and the
  segfault doesn't happen.  It appears that any -gtk-gradient set on
  background-image for .mate-panel-menu-bar doesn't work and causes Mate
  to segfault.  I have to change the theme and restart to get things to
  work again.

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

[Dave Jones]

Public bug reported:

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.

** Affects: livecd-rootfs (Ubuntu)
 Importance: Undecided
 Assignee: Dave Jones (waveform)
 Status: New

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

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

** Changed in: livecd-rootfs (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/2004430

Title:
  Migrate raspberry pi image hacks from livecd-rootfs

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

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 1998263] Re: JPEG ( backing store not supported ) : many pictures won't open.

[Brian Murray]

Hello Coeur, or anyone else affected,

Accepted gdk-pixbuf into kinetic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gdk-
pixbuf/2.42.9+dfsg-1ubuntu1 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
kinetic to verification-done-kinetic. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-kinetic. In either case, without details of your
testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Also affects: gdk-pixbuf (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

** Changed in: gdk-pixbuf (Ubuntu Kinetic)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-kinetic

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

Title:
  JPEG ( backing store not supported ) : many pictures won't open.

Status in Eye of GNOME:
  Fix Released
Status in gdk-pixbuf:
  Fix Released
Status in gdk-pixbuf package in Ubuntu:
  Fix Released
Status in gdk-pixbuf source package in Jammy:
  Invalid
Status in gdk-pixbuf source package in Kinetic:
  Fix Committed
Status in gdk-pixbuf source package in Lunar:
  Fix Released

Bug description:
  * Impact

  Eog can't open high resolution jpg files

  * Test Case

  - download 
https://gitlab.gnome.org/GNOME/gdk-pixbuf/uploads/fcda5bc359fbf55a1b9755ba92c3303d/kwiatek.jpg
  - try to open the image in eog

  * Regression potential

  The change increase the memory usage limit for loading jpg, it could
  lead to put the system under memory pressure. The limit has been added
  in 22.10 though so it isn't a regression compared to the previous
  version of Ubuntu

  -

  
  Hi,

  22.10. Just try to open some .jpg files from my usual storage.

  Error interpreting jpeg file ( Backing store not supported. )

  Those same pictures open in other OSes ( 22.04, 20.04 and else. )

  Can't use those pictures as backgrounds.

  But able to open them in Gimp or Shotwell.

  Maybe related to : https://gitlab.gnome.org/GNOME/gdk-
  pixbuf/-/issues/216

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: eog 43.0-1
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 29 23:31:36 2022
  InstallationDate: Installed on 2022-10-27 (33 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: eog
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/eog/+bug/1998263/+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 1950996] Re: Missing all modules for usb nics in initrd which makes PXE boot impossible

[Franklin Kramer]

Hi, just wanted to follow up here, any progress? This is still an issue
holding up our 20.04 builds.

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

Title:
  Missing all modules for usb nics in initrd which makes PXE boot
  impossible

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Focal:
  Triaged
Status in initramfs-tools source package in Hirsute:
  Won't Fix
Status in initramfs-tools source package in Impish:
  Won't Fix
Status in initramfs-tools source package in Jammy:
  Fix Released
Status in initramfs-tools package in Debian:
  Fix Released

Bug description:
  initrd taken from the live iso for PXE boot does not contain USB NIC
  drivers which makes PXE installation/netboot impossible via usb.

  This is the case on 20.04 server iso (both hwe and normal
  kernel/initrd) and desktop iso.

  "kernel/drivers/net/usb" is empty and needs to be included in the
  initramfs build.

  As most modern thin laptops lack physical rj45 ethernet this is a big
  issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6.6
  ProcVersionSignature: Ubuntu 5.8.0-64.72-generic 5.8.18
  Uname: Linux 5.8.0-64-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 15 16:47:45 2021
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: Upgraded to focal on 2020-05-11 (552 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1950996/+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 2004011] Re: Checks are not skipped when building esm packages package from source

[Lucas Kanashiro]

Thanks for reporting this bug and trying to make it better.

When we are talking about the Debian Policy we need to keep in mind that
it is versioned. You linked a section of the Debian Policy version
4.6.2.0, so packages complaint with that version should do what is
written there (to make sure which version of Debian Policy a package is
complaint you need to check the Standards-Version field in
debian/control). Moreover, the very first sentence of the section is:

"Supporting the standardized environment variable DEB_BUILD_OPTIONS is
recommended."

So those options are recommended, they are not mandatory. It is not an
issue if you find a package that does not support those options.

src:heimdal in xenial (16.04) is compliant with Debian Policy 3.9.6, in
this version we already have the nocheck option added (actually in
version 3.8.1):

https://www.debian.org/doc/debian-policy/upgrading-
checklist.html#version-3-8-1

But again, this is recommended, not mandatory. Due to that, we will not
update a package in ESM just to introduce support to nocheck.

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

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

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

Title:
  Checks are not skipped when building esm packages package from source

Status in heimdal package in Ubuntu:
  Won't Fix

Bug description:
  **Describe the bug**
  Under the policy, building a deb package from source should not run checks 
when provided with env var `DEB_BUILD_OPTIONS="nocheck"`:
  
https://www.debian.org/doc/debian-policy/ch-source.html#debian-rules-and-deb-build-options

  However, this is what `override_dh_auto_test` target in `debian/rules` looks 
like in `heimdal=1.7~git20150920+dfsg-4ubuntu1.16.04.1+esm3`:
  ```
  override_dh_auto_test:
  $(MAKE) check
  ```
  So checks are still run when `nocheck` in `DEB_BUILD_OPTIONS` is provided.

  Apparently, this has been patched:
  
https://salsa.debian.org/debian/heimdal/-/commit/b1a7b04591873e7d0e88acaf24cc76073ee47fc9

  However, the patch did not make its way to ESM packages for 16.04. Is
  it possible to cherry-pick this commit to the ESM packages?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/2004011/+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 1980386] Re: `radeonsi_dri.so` driver missing on riscv64

[Michał Sawicz]

And can confirm this works on jammy now, too \o/.

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

Title:
  `radeonsi_dri.so` driver missing on riscv64

Status in llvm-toolchain-15 package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in llvm-toolchain-15 source package in Jammy:
  In Progress
Status in mesa source package in Jammy:
  Fix Released
Status in llvm-toolchain-15 source package in Kinetic:
  Fix Released
Status in mesa source package in Kinetic:
  Fix Released

Bug description:
  The package is missing the `radeonsi` driver, with the reasoning that
  LLVM is not implemented on the architecture:

  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995618

  That said, it works just fine on focal, where it is still enabled.
  Without this driver there's no way to use AMD graphics cards on
  RISC-V.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libgl1-mesa-dri 22.0.1-1ubuntu2
  ProcVersionSignature: User Name 5.15.0-1007.7-generic 5.15.30
  Uname: Linux 5.15.0-1007-generic riscv64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: riscv64
  CasperMD5CheckResult: unknown
  Date: Thu Jun 30 15:48:11 2022
  ProcCpuinfoMinimal:
   processor: 3
   hart : 4
   isa  : rv64imafdc
   mmu  : sv39
   uarch: sifive,u74-mc
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: mesa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-15/+bug/1980386/+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 1728130] Re: Policy needs improved feature versioning to ensure it is correctly being applied

[Georgia Garcia]

Thank you for validating the test, Heather.

In addition to the ABI validation, I also ran the AppArmor tests using
the QA Regression Test suite (https://git.launchpad.net/qa-regression-
testing/tree/scripts/test-apparmor.py). It includes tests for
LibAppArmor, the parser, and all regression tests. They all worked as
expected.

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

Title:
  Policy needs improved feature versioning to ensure it is correctly
  being applied

Status in apparmor package in Ubuntu:
  Confirmed
Status in apparmor source package in Focal:
  Fix Committed

Bug description:
  [ Impact ]

  Currently allows pinning a single feature abi or running in a
  developer mode where the full abi available of the current kernel is
  enforced.

  However this can result in breaking applications in undesirable ways.

  If an application is shipped with its own policy, that policy might be
  different than the pinned feature abi, which can either result in
  denials because features the policy was not developed for are being
  enforced.

  If the feature version is not pinned then the most recent kernel abi
  is taken and applied to policy, which has not been updated. This can
  result in denials for userspace effectively breaking userspace. This
  is less than ideal for most users as it leads to a bad experience than
  they have not opted into and can lead to them disabling security
  protections.

  [ Test Plan ]

  The test can be done with several features. Here we are using mqueue as an 
example.
  Verify that the kernel that has mqueue mediation support:
  root@ubuntu:~# [ -e /sys/kernel/security/apparmor/features/ipc/posix_mqueue ] 
&& echo "supports mqueue"
  supports mqueue

  cd /tmp
  pull-ppa-source --ppa georgiag/mqueue-sru apparmor focal
  cd apparmor-2.13.3/tests/regression/apparmor/
  USE_SYSTEM=1 make

  Using the parser from the mqueue-sru PPA, load the profile.
  echo "
  abi ,
  include 
  /tmp/apparmor-2.13.3/tests/regression/apparmor/posix_mq_rcv {
include 
/tmp/apparmor-2.13.3/tests/regression/apparmor/posix_mq_snd ux,
  }
  " | apparmor_parser -q -r

  Run the test, which should fail.
  ./posix_mq_rcv -c ./posix_mq_snd
  FAIL - could not open mq: Permission denied

  Now use an abi that does not have mqueue. This simulates a scenario
  where a policy was developed before mqueue support was added, so posix
  message queues should be allowed by default.

  echo "
  abi ,
  include 
  /tmp/apparmor-2.13.3/tests/regression/apparmor/posix_mq_rcv {
include 
/tmp/apparmor-2.13.3/tests/regression/apparmor/posix_mq_snd ux,
  }
  " | apparmor_parser -q -r

  Run the test again, it should pass.
  ./posix_mq_rcv -c ./posix_mq_snd
  PASS

  [ Where problems could occur ]

  ABI pinning forces policies that don't have abi specified in their
  profile to use the ABI pinned in parser.conf. When the ABI is pinned
  and the user is trying to use mediation that is not in the pinned ABI,
  they might be confused why it is always being allowed. This can be
  circumvented by specifying the correct abi in the profile.

  [ Other Info ]

  The patches for focal (apparmor-2.13) can be found at:
  https://launchpad.net/~georgiag/+archive/ubuntu/mqueue-sru/
  apparmor-3.0 already has this feature.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1728130/+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 2004352] [NEW] problema para abrir vídeo

[joao mario]

Public bug reported:

problema para abrir qualquer vídeo seja com o totem ou usando o opencv,
apenas consigo abrir video com ffmpeg ( não se aplica ao opencv )

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: libgstreamer1.0-0 1.20.3-1
ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
Uname: Linux 5.19.0-29-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Jan 31 13:39:12 2023
InstallationDate: Installed on 2022-12-13 (48 days ago)
InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
SourcePackage: gstreamer1.0
UpgradeStatus: No upgrade log present (probably fresh install)
XorgLog: Error: [Errno 2] Arquivo ou diretório inexistente: 
'/var/log/Xorg.0.log'

** Affects: gstreamer1.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug kinetic third-party-packages wayland-session

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

Title:
  problema para abrir vídeo

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  problema para abrir qualquer vídeo seja com o totem ou usando o
  opencv, apenas consigo abrir video com ffmpeg ( não se aplica ao
  opencv )

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: libgstreamer1.0-0 1.20.3-1
  ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
  Uname: Linux 5.19.0-29-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 31 13:39:12 2023
  InstallationDate: Installed on 2022-12-13 (48 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] Arquivo ou diretório inexistente: 
'/var/log/Xorg.0.log'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/2004352/+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 1933090] Re: systemd/245.4-4ubuntu3.6 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1

[Roxana Nicolescu]

Still failing in Focal, for linux-oracle-5.15 this time. And it's been failing 
for some time now
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/s/systemd/20221206_050631_237a8@/log.gz

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

Title:
  systemd/245.4-4ubuntu3.6 ADT test failure with linux-
  hwe-5.11/5.11.0-20.21~20.04.1

Status in linux-hwe-5.11 package in Ubuntu:
  Won't Fix
Status in linux-hwe-5.15 package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New
Status in linux-hwe-5.11 source package in Focal:
  Won't Fix
Status in linux-hwe-5.15 source package in Focal:
  New
Status in systemd source package in Focal:
  New

Bug description:
  This is a scripted bug report about ADT failures while running systemd
  tests for linux-hwe-5.11/5.11.0-20.21~20.04.1 on focal. Whether this
  is caused by the dep8 tests of the tested source or the kernel has yet
  to be determined.

  Testing failed on:
  amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/s/systemd/20210611_220645_bf5b6@/log.gz
  armhf: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20210617_124738_5b554@/log.gz
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/s/systemd/20210611_235629_92856@/log.gz
  s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/s/systemd/20210611_214456_6427f@/log.gz

  In arm64, ppc64el and s390x, 'root-unittests' fails with:

  /* test_protect_sysctl */
  Assertion 'errno == EFAULT' failed at src/test/test-seccomp.c:311, function 
test_protect_sysctl(). A
  borting.
  sysctlseccomp terminated by signal ABRT.
  Assertion 'wait_for_terminate_and_check("sysctlseccomp", pid, WAIT_LOG) == 
EXIT_SUCCESS' failed at s
  rc/test/test-seccomp.c:324, function test_protect_sysctl(). Aborting.
  FAIL: test-seccomp (code: 134)

  In amd64, 'upstream' also fails on 'TEST-24-UNIT-TESTS', which
  apparently is caused by the same 'test-seccomp.c:311' assertion
  failure.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.11/+bug/1933090/+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 2004264] Re: FTBFS against glibc 2.37

[Simon Chopin]

The failure is in a gnulib test. I've bisected it to the following glibc
upstream commit:

https://sourceware.org/git/?p=glibc.git;a=commit;h=642933158e7cf072d873231b1a9bb03291f2b989

The issue has been reported upstream.

** Bug watch added: Sourceware.org Bugzilla #30065
   https://sourceware.org/bugzilla/show_bug.cgi?id=30065

** Also affects: libunistring via
   https://sourceware.org/bugzilla/show_bug.cgi?id=30065
   Importance: Unknown
   Status: Unknown

** Project changed: libunistring => glibc

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

Title:
  FTBFS against glibc 2.37

Status in GLibC:
  Unknown
Status in libunistring package in Ubuntu:
  New

Bug description:
  Hi,

  During a mass rebuild of Lunar, the package libunistring failed to
  build against a snapshot of the upcoming glibc 2.37, while building
  fine using 2.36 as present in the archive.

  
https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20221215-lunar-glibc-2.37-lunar.html
  
https://launchpadlibrarian.net/644139079/buildlog_ubuntu-lunar-amd64.libunistring_1.0-2_BUILDING.txt.gz

  I was able to reproduce this when building against my latest snapshot
  (done this morning), published in this PPA:

  https://launchpad.net/~schopin/+archive/ubuntu/glibc-2.37-snapshot/+packages

  The failing tests appear to be test-strncat and test-u8-strncat.

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


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

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

[Jeremy Bicha]

I was using the latest version of glib 2.75 as packaged in Debian
experimental for a few days, but my sound broke. See
https://gitlab.gnome.org/GNOME/glib/-/issues/2769

There probably are other things that broke because of that behavior
change.

Also, recent changes made glib break on other architectures (endian
issue?) which means it would be stuck in lunar-proposed until that is
fixed.

https://buildd.debian.org/status/package.php?p=glib2.0=experimental

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

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

** Bug watch added: gitlab.gnome.org/GNOME/glib/-/issues #2769
   https://gitlab.gnome.org/GNOME/glib/-/issues/2769

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

Title:
  Update to glib >= 2.75.1

Status in glib2.0 package in Ubuntu:
  Triaged

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

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


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

[Touch-packages] [Bug 1728130] Re: Policy needs improved feature versioning to ensure it is correctly being applied

[Heather Lemon]

### VERIFICATION DONE FOCAL ###

sudo add-apt-repository ppa:apparmor-dev/mqueue-dev
sudo apt update

# exchange keypair ssh 
scp linux-* ubuntu@x.x.x.x:~

sudo dpkg -i linux* 
sudo apt --fix-broken install

# edit /etc/default/grub
GRUB_DEFAULT='Advanced options for Ubuntu>Ubuntu, with Linux 5.4.0-131-generic'
sudo update-grub 

restart/reboot machine

sudo apt-get upgrade apparmor

# go find menu entry and update grub
/boot/boot.cfg
# menuentry 'Ubuntu, with Linux 5.4.0-131-generic' 

# execute command 
GRUB_DEFAULT='Advanced options for Ubuntu>Ubuntu, with Linux 5.4.0-131-generic'

# should output 
supports mqueue

sudo apt install ubuntu-dev-tools -y

pull-ppa-source --ppa georgiag/mqueue-sru apparmor focal

sudo apt-get install autoconf libtool -y

cd ./libraries/libapparmor/

./autogen.sh

export PYTHONPATH=/tmp/apparmor-2.13.3/libraries/libapparmor/swig/python
export PYTHON=/usr/bin/python3
export PYTHON_VERSION=3
export PYTHON_VERSIONS=python3
export USE_SYSTEM=1 make

./configure

sudo apt-get install flex dejagnu

make

sudo make check 
 
sudo make install

cd binutils
make
make check
make install

cd ./libraries/libapparmor
sh ./autogen.sh
sh ./configure
make
make check
make install

cd parser
$ make  # depends on libapparmor having been built first
$ make check

# run unit tests
cd /tests/regession/apparmor/
sudo make tests

sudo su

echo "
abi ,
include 
/tmp/apparmor-2.13.3/tests/regression/apparmor/posix_mq_rcv {
  include 
  /tmp/apparmor-2.13.3/tests/regression/apparmor/posix_mq_snd ux,
}
" | apparmor_parser -q -r

# run command
./posix_mq_rcv -c ./posix_mq_snd
FAIL - could not open mq: Permission denied
# we see this fail error 

# make sure there is enough permissions to execute 
sudo chmod 777 posix_mq_rcv

./posix_mq_rcv -c ./posix_mq_snd
PASS

### VERIFICATION DONE FOCAL ###

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

Title:
  Policy needs improved feature versioning to ensure it is correctly
  being applied

Status in apparmor package in Ubuntu:
  Confirmed
Status in apparmor source package in Focal:
  Fix Committed

Bug description:
  [ Impact ]

  Currently allows pinning a single feature abi or running in a
  developer mode where the full abi available of the current kernel is
  enforced.

  However this can result in breaking applications in undesirable ways.

  If an application is shipped with its own policy, that policy might be
  different than the pinned feature abi, which can either result in
  denials because features the policy was not developed for are being
  enforced.

  If the feature version is not pinned then the most recent kernel abi
  is taken and applied to policy, which has not been updated. This can
  result in denials for userspace effectively breaking userspace. This
  is less than ideal for most users as it leads to a bad experience than
  they have not opted into and can lead to them disabling security
  protections.

  [ Test Plan ]

  The test can be done with several features. Here we are using mqueue as an 
example.
  Verify that the kernel that has mqueue mediation support:
  root@ubuntu:~# [ -e /sys/kernel/security/apparmor/features/ipc/posix_mqueue ] 
&& echo "supports mqueue"
  supports mqueue

  cd /tmp
  pull-ppa-source --ppa georgiag/mqueue-sru apparmor focal
  cd apparmor-2.13.3/tests/regression/apparmor/
  USE_SYSTEM=1 make

  Using the parser from the mqueue-sru PPA, load the profile.
  echo "
  abi ,
  include 
  /tmp/apparmor-2.13.3/tests/regression/apparmor/posix_mq_rcv {
include 
/tmp/apparmor-2.13.3/tests/regression/apparmor/posix_mq_snd ux,
  }
  " | apparmor_parser -q -r

  Run the test, which should fail.
  ./posix_mq_rcv -c ./posix_mq_snd
  FAIL - could not open mq: Permission denied

  Now use an abi that does not have mqueue. This simulates a scenario
  where a policy was developed before mqueue support was added, so posix
  message queues should be allowed by default.

  echo "
  abi ,
  include 
  /tmp/apparmor-2.13.3/tests/regression/apparmor/posix_mq_rcv {
include 
/tmp/apparmor-2.13.3/tests/regression/apparmor/posix_mq_snd ux,
  }
  " | apparmor_parser -q -r

  Run the test again, it should pass.
  ./posix_mq_rcv -c ./posix_mq_snd
  PASS

  [ Where problems could occur ]

  ABI pinning forces policies that don't have abi specified in their
  profile to use the ABI pinned in parser.conf. When the ABI is pinned
  and the user is trying to use mediation that is not in the pinned ABI,
  they might be confused why it is always being allowed. This can be
  circumvented by specifying the correct abi in the profile.

  [ Other Info ]

  The patches for focal (apparmor-2.13) can be found at:
  https://launchpad.net/~georgiag/+archive/ubuntu/mqueue-sru/
  apparmor-3.0 already has this feature.

To manage notifications about this bug go to:

[Touch-packages] [Bug 1728130] Re: Policy needs improved feature versioning to ensure it is correctly being applied

[Heather Lemon]

*Note I have not done any extra testing outside of the testing steps
listed, which it would probably be a good idea to do so.

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

Title:
  Policy needs improved feature versioning to ensure it is correctly
  being applied

Status in apparmor package in Ubuntu:
  Confirmed
Status in apparmor source package in Focal:
  Fix Committed

Bug description:
  [ Impact ]

  Currently allows pinning a single feature abi or running in a
  developer mode where the full abi available of the current kernel is
  enforced.

  However this can result in breaking applications in undesirable ways.

  If an application is shipped with its own policy, that policy might be
  different than the pinned feature abi, which can either result in
  denials because features the policy was not developed for are being
  enforced.

  If the feature version is not pinned then the most recent kernel abi
  is taken and applied to policy, which has not been updated. This can
  result in denials for userspace effectively breaking userspace. This
  is less than ideal for most users as it leads to a bad experience than
  they have not opted into and can lead to them disabling security
  protections.

  [ Test Plan ]

  The test can be done with several features. Here we are using mqueue as an 
example.
  Verify that the kernel that has mqueue mediation support:
  root@ubuntu:~# [ -e /sys/kernel/security/apparmor/features/ipc/posix_mqueue ] 
&& echo "supports mqueue"
  supports mqueue

  cd /tmp
  pull-ppa-source --ppa georgiag/mqueue-sru apparmor focal
  cd apparmor-2.13.3/tests/regression/apparmor/
  USE_SYSTEM=1 make

  Using the parser from the mqueue-sru PPA, load the profile.
  echo "
  abi ,
  include 
  /tmp/apparmor-2.13.3/tests/regression/apparmor/posix_mq_rcv {
include 
/tmp/apparmor-2.13.3/tests/regression/apparmor/posix_mq_snd ux,
  }
  " | apparmor_parser -q -r

  Run the test, which should fail.
  ./posix_mq_rcv -c ./posix_mq_snd
  FAIL - could not open mq: Permission denied

  Now use an abi that does not have mqueue. This simulates a scenario
  where a policy was developed before mqueue support was added, so posix
  message queues should be allowed by default.

  echo "
  abi ,
  include 
  /tmp/apparmor-2.13.3/tests/regression/apparmor/posix_mq_rcv {
include 
/tmp/apparmor-2.13.3/tests/regression/apparmor/posix_mq_snd ux,
  }
  " | apparmor_parser -q -r

  Run the test again, it should pass.
  ./posix_mq_rcv -c ./posix_mq_snd
  PASS

  [ Where problems could occur ]

  ABI pinning forces policies that don't have abi specified in their
  profile to use the ABI pinned in parser.conf. When the ABI is pinned
  and the user is trying to use mediation that is not in the pinned ABI,
  they might be confused why it is always being allowed. This can be
  circumvented by specifying the correct abi in the profile.

  [ Other Info ]

  The patches for focal (apparmor-2.13) can be found at:
  https://launchpad.net/~georgiag/+archive/ubuntu/mqueue-sru/
  apparmor-3.0 already has this feature.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1728130/+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 2004092] Re: casper fails to add any users because GID 999 is already taken

[Dan Bungert]

** Merge proposal linked:
   https://code.launchpad.net/~tsimonq2/casper/+git/casper/+merge/436490

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

Title:
  casper fails to add any users because GID 999 is already taken

Status in casper package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in systemd package in Debian:
  Unknown

Bug description:
  This bug is due to the latest systemd upload in Ubuntu. systemd-
  journald now uses GID 999, when casper explicitly sets the live user
  to that UID and GID.

  Rather than going through the painstaking task of updating systemd to
  use a *different* user, let's just update casper to use 1000, which is
  the first dynamically-allocated user account per Debian Policy[1].

  [1] https://www.debian.org/doc/debian-policy/ch-opersys.html#uid-and-
  gid-classes

  [ Original Report ]

  Normally, when one first boots a live ISO, a desktop automatically
  appears, asking users if they want to try or install Ubuntu (or, in
  the case of Lubuntu, they are simply dropped into a working desktop
  with an installation desktop icon available). As of the Lubuntu ISO on
  January 27, 2023, this has stopped occuring. Plymouth shows the
  initial boot animation, but the user is then dropped to a solid black
  screen. No user input is accepted. Attempting to switch to a TTY and
  sign in fails with the default "lubuntu" username and a blank password
  (the error "Login incorrect" is displayed).

  On Ubuntu Desktop, the behavior is even stranger. Rather than being
  shown a "Try or Install Ubuntu" screen, an initial system setup wizard
  appears that takes the user through the process of creating a user
  account. On a live ISO. Only after this wizard is finished does the
  "Try or Install Ubuntu" screen appear. Attempting to log into a TTY
  using the default "ubuntu" username and a blank password fails the
  same way as Lubuntu does, if done before the wizard is finished.
  However, one can log into a TTY if they finish the wizard and then
  attempt to log into the TTY using the credentials provided during user
  account setup.

  This issue affects at least the Lubuntu ISOs as of January 27, 2023,
  and the Ubuntu Desktop ISO at least as of January 28, 2023 (it is
  assumed that the 27th ISO for Ubuntu Desktop is also broken). The ISO
  from the 26th is most likely unaffected as there is successful testing
  information for Lubuntu on the 26th, so something likely happened
  between the 26th and the 27th to cause this breakage.

  Steps to reproduce:

  1. Download the latest Lunar daily ISO of Ubuntu Desktop or Lubuntu.
  2. Boot the ISO (hardware is irrelevant - this appears to occur on both 
physical and virtual hardware).

  For Lubuntu:

  3. Wait until you are dropped to a black, blank screen.
  4. Wait a while, then attempt to switch to a TTY and attempt to log in using 
"lubuntu" as the username and a blank password. The login attempt will be 
denied.

  For Ubuntu Desktop:

  3. Wait until you are provided with an initial system setup wizard.
  4. Switch to a TTY and attempt to log in using "ubuntu" as the username and a 
blank password. The login attempt will be denied.
  5. Switch back to the system setup wizard, and complete it.
  6. After completing the wizard, switch to a TTY again and attempt to log in 
using the credentials provided to the wizard. The login attempt will be 
successful.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/2004092/+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 2004246] Re: /usr/bin/software-properties-gtk:gi.repository.GLib.GError:/usr/bin/software-properties-gtk@100:__init__:init_ubuntu_pro:__init__

[Nathan Teodosio]

Could it be https://gitlab.gnome.org/GNOME/gdk-
pixbuf/-/issues/159#note_1125929 + https://sources.debian.org/src/gdk-
pixbuf/2.42.10%2Bdfsg-1/debian/libgdk-pixbuf-2.0-0.postinst.in/#L18?

** Bug watch added: gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues #159
   https://gitlab.gnome.org/GNOME/gdk-pixbuf/-/issues/159

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

Title:
  /usr/bin/software-properties-
  gtk:gi.repository.GLib.GError:/usr/bin/software-properties-
  gtk@100:__init__:init_ubuntu_pro:__init__

Status in software-properties package in Ubuntu:
  New

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2004246/+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 2004264] [NEW] FTBFS against glibc 2.37

[Simon Chopin]

Public bug reported:

Hi,

During a mass rebuild of Lunar, the package libunistring failed to build
against a snapshot of the upcoming glibc 2.37, while building fine using
2.36 as present in the archive.

https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20221215-lunar-glibc-2.37-lunar.html
https://launchpadlibrarian.net/644139079/buildlog_ubuntu-lunar-amd64.libunistring_1.0-2_BUILDING.txt.gz

I was able to reproduce this when building against my latest snapshot
(done this morning), published in this PPA:

https://launchpad.net/~schopin/+archive/ubuntu/glibc-2.37-snapshot/+packages

The failing tests appear to be test-strncat and test-u8-strncat.

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

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

Title:
  FTBFS against glibc 2.37

Status in libunistring package in Ubuntu:
  New

Bug description:
  Hi,

  During a mass rebuild of Lunar, the package libunistring failed to
  build against a snapshot of the upcoming glibc 2.37, while building
  fine using 2.36 as present in the archive.

  
https://people.canonical.com/~ginggs/ftbfs-report/test-rebuild-20221215-lunar-glibc-2.37-lunar.html
  
https://launchpadlibrarian.net/644139079/buildlog_ubuntu-lunar-amd64.libunistring_1.0-2_BUILDING.txt.gz

  I was able to reproduce this when building against my latest snapshot
  (done this morning), published in this PPA:

  https://launchpad.net/~schopin/+archive/ubuntu/glibc-2.37-snapshot/+packages

  The failing tests appear to be test-strncat and test-u8-strncat.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libunistring/+bug/2004264/+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 2004245] Re: /usr/bin/software-properties-gtk:AttributeError:on_radio_toggled:update_state

[Nathan Teodosio]

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

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

Title:
  /usr/bin/software-properties-
  gtk:AttributeError:on_radio_toggled:update_state

Status in software-properties package in Ubuntu:
  Triaged

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2004245/+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 2004245] Re: /usr/bin/software-properties-gtk:AttributeError:on_radio_toggled:update_state

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~nteodosio/software-properties/+git/software-properties/+merge/436589

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

Title:
  /usr/bin/software-properties-
  gtk:AttributeError:on_radio_toggled:update_state

Status in software-properties package in Ubuntu:
  Triaged

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2004245/+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 2004246] Re: /usr/bin/software-properties-gtk:gi.repository.GLib.GError:/usr/bin/software-properties-gtk@100:__init__:init_ubuntu_pro:__init__

[Sebastien Bacher]

Hum, it seems some users don't have a gdk pixbuf loader for svg? Unsure
how can that happens since libgtk-3-0 Depends on librsvg

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

Title:
  /usr/bin/software-properties-
  gtk:gi.repository.GLib.GError:/usr/bin/software-properties-
  gtk@100:__init__:init_ubuntu_pro:__init__

Status in software-properties package in Ubuntu:
  New

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2004246/+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 2004245] Re: /usr/bin/software-properties-gtk:AttributeError:on_radio_toggled:update_state

[Sebastien Bacher]

Nathan, any idea what's going on there?

** Changed in: software-properties (Ubuntu)
   Importance: Undecided => High

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

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

Title:
  /usr/bin/software-properties-
  gtk:AttributeError:on_radio_toggled:update_state

Status in software-properties package in Ubuntu:
  New

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2004245/+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 2004245] [NEW] /usr/bin/software-properties-gtk:AttributeError:on_radio_toggled:update_state

[errors.ubuntu.com bug bridge]

Public bug reported:

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

** Affects: software-properties (Ubuntu)
 Importance: High
 Assignee: Nathan Teodosio (nteodosio)
 Status: New


** Tags: bionic focal jammy

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

Title:
  /usr/bin/software-properties-
  gtk:AttributeError:on_radio_toggled:update_state

Status in software-properties package in Ubuntu:
  New

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2004245/+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 2004246] [NEW] /usr/bin/software-properties-gtk:gi.repository.GLib.GError:/usr/bin/software-properties-gtk@100:__init__:init_ubuntu_pro:__init__

[errors.ubuntu.com bug bridge]

Public bug reported:

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

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


** Tags: focal jammy kinetic

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

Title:
  /usr/bin/software-properties-
  gtk:gi.repository.GLib.GError:/usr/bin/software-properties-
  gtk@100:__init__:init_ubuntu_pro:__init__

Status in software-properties package in Ubuntu:
  New

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2004246/+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 1991606] Re: Invalid PEP440 package version breaking setuptools >= 60

[Benjamin Drung]

** Also affects: python-debian (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Invalid PEP440 package version breaking setuptools >= 60

Status in devscripts package in Ubuntu:
  New
Status in distro-info package in Ubuntu:
  Fix Released
Status in drslib package in Ubuntu:
  New
Status in duecredit package in Ubuntu:
  New
Status in python-debian package in Ubuntu:
  New
Status in reportbug package in Ubuntu:
  New
Status in ubuntu-dev-tools package in Ubuntu:
  New
Status in devscripts source package in Bionic:
  New
Status in distro-info source package in Bionic:
  New
Status in drslib source package in Bionic:
  New
Status in duecredit source package in Bionic:
  New
Status in python-debian source package in Bionic:
  New
Status in reportbug source package in Bionic:
  New
Status in ubuntu-dev-tools source package in Bionic:
  New
Status in devscripts source package in Focal:
  New
Status in distro-info source package in Focal:
  New
Status in drslib source package in Focal:
  New
Status in duecredit source package in Focal:
  New
Status in python-debian source package in Focal:
  New
Status in reportbug source package in Focal:
  New
Status in ubuntu-dev-tools source package in Focal:
  New
Status in devscripts source package in Jammy:
  New
Status in distro-info source package in Jammy:
  New
Status in drslib source package in Jammy:
  New
Status in duecredit source package in Jammy:
  New
Status in python-debian source package in Jammy:
  New
Status in reportbug source package in Jammy:
  New
Status in ubuntu-dev-tools source package in Jammy:
  Invalid
Status in devscripts source package in Kinetic:
  New
Status in distro-info source package in Kinetic:
  New
Status in drslib source package in Kinetic:
  New
Status in duecredit source package in Kinetic:
  New
Status in python-debian source package in Kinetic:
  New
Status in reportbug source package in Kinetic:
  New
Status in ubuntu-dev-tools source package in Kinetic:
  Invalid

Bug description:
  With setuptools 66, the versions of all packages visible in the Python
  environment *must* obey PEP440 .
  Otherwise, attempts to use pip to install a package with a setup.py-
  based build system, or other attempts to use the `pkg-resources`
  module, can produce errors like this:

    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 844, in _resolve_dist
  env = Environment(self.entries)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1044, in __init__
  self.scan(search_path)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1077, in scan
  self.add(dist)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1096, in add
  dists.sort(key=operator.attrgetter('hashcmp'), reverse=True)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2631, in hashcmp
  self.parsed_version,
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2678, in parsed_version
  self._parsed_version = parse_version(self.version)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/_vendor/packaging/version.py",
 line 266, in __init__
  raise InvalidVersion(f"Invalid version: '{version}'")
  pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: 
'0.23ubuntu1'

  The official opinion of the setuptools maintainers seems to be that
  version strings of this form haven't *really* been allowed since about
  2014, and distributions need to change their package version naming
  scheme for Python packages they install, so that the resulting version
  strings obey PEP440. See for example
  .

  suffix 1build1 is invalid.

  Some python building tools, that verifies if version strings are
  compatible with PEP440, are failing.

  Example: python poetry: Invalid PEP 440 version: '1.1build1'

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


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

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

[Benjamin Drung]

The new master bug for all affected packages is bug #1991606.

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

Title:
  python-debian has invalid version

Status in python-debian package in Ubuntu:
  Confirmed

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

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

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

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

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

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

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

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

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


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

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

[Daniel van Vugt]

Public bug reported:

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

** Affects: glib2.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: lunar upgrade-software-version

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

Title:
  Update to glib >= 2.75.1

Status in glib2.0 package in Ubuntu:
  New

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

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


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

[Touch-packages] [Bug 1999098] Re: Update glib to 2.74.3

[Daniel van Vugt]

** Changed in: glib2.0 (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 glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1999098

Title:
  Update glib to 2.74.3

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Kinetic:
  Fix Released

Bug description:
  Impact
  --
  There is a new bugfix release in the stable 2.74 series

  The current release in Ubuntu 22.10 is 2.74.0

  https://gitlab.gnome.org/GNOME/glib/-/blob/2.74.3/NEWS

  Test Case 1
  ---
  glib has an extensive test suite.

  Failing tests will fail the build.
  This update will also trigger a lot of autopkgtests.

  Ensure that there aren't autopgktest regressions triggered by this
  update and that the builds complete successfully

  Test Case 2
  ---
  Pretty much all parts of GNOME use GLib, so test anything in the desktop that 
you can. If you reboot the machine and can get to the desktop, that's already 
tested GLib extensively. But also run applications like the terminal, the file 
browser and epiphany-browser

  Test Case 3 (Extra)
  --
  Install gnome-characters 43.1. (This is being SRU'd, but the version from 
Lunar also works.)
  Open the Characters app.
  Use the search feature to search for "moose"
  A moose emoji should show up. This is one of the new Emoji 15.
  https://blog.emojipedia.org/whats-new-in-unicode-15-0/

  With glib 2.74.0, the moose emoji won't be searchable but it does show
  in the Animals category.

  What Could Go Wrong
  ---
  This update contains fixes in multiple places so multiple apps could be 
affected. The consequences of a broken GLib can range from some functions 
returning bad results sometimes, which have minimal runtime implications, up to 
the system simply crashing all the time.

  Other Info
  --
  Unicode 15 enablement was granted a User Interface Freeze Exception for 
Ubuntu 22.10: https://launchpad.net/bugs/1989626

  glib and gnome-characters are the only 2 late pieces that the Ubuntu
  Desktop team plans to SRU for Ubuntu 22.10.

  Ubuntu 23.04 has 2.74.2 with the commits from 2.74.3 backported so
  they are functionally equivalent. Ubuntu 23.04 will get newer glib
  versions before 23.04 is released.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1999098/+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