[Touch-packages] [Bug 1995260] Re: dnsmasq focal 2.80 NODATA instead of NXDOMAIN bug

[Christian Ehrhardt ]

@SRU team - please consider accepting and merging the test hint [1] to
resolve the current blocker for this SRU.

[1]: https://code.launchpad.net/~paelzer/britney/+git/hints-
ubuntu/+merge/433770

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

Title:
  dnsmasq focal 2.80 NODATA instead of NXDOMAIN bug

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in dnsmasq source package in Focal:
  Fix Committed

Bug description:
  [SRU]

  [ Impact ]

  Sometimes dnsmasq is incorrectly returning NODATA instead of NXDOMAIN.
  This can lead to erroneous actions by clients who need to determine
  whether a domain name exists or not.

  [ Test Plan ]

  In a focal VM, install dnsmasq (apt install dnsmasq) if it wasn't
  installed yet.

  #0 Disabling systemd-resolved service and enabling resolution through
  dnsmasq.

  # systemctl disable --now systemd-resolved.service
  # rm -f /etc/resolv.conf
  # cat > /etc/resolv.conf << __EOF__
  nameserver 8.8.8.8
  __EOF__
  # systemctl start dnsmasq.service

  #1 Bad case

  # for i in srv txt  a  a txt srv; do host -t $i test.foo. 127.0.0.1 | 
tail -n 1; done
  Host test.foo. not found: 3(NXDOMAIN)
  Host test.foo. not found: 3(NXDOMAIN)
  Host test.foo. not found: 3(NXDOMAIN)
  test.foo has no A record
  Host test.foo. not found: 3(NXDOMAIN)
  test.foo has no A record
  test.foo has no TXT record
  test.foo has no SRV record

  #2 Good case

  #2.1 Installing new package

  # ls -1 *.deb
  dnsmasq-utils_2.80-1.1ubuntu1.6_amd64.deb
  dnsmasq-base_2.80-1.1ubuntu1.6_amd64.deb
  dnsmasq_2.80-1.1ubuntu1.6_all.deb

  # dpkg -i *.deb
  (Reading database ... 32073 files and directories currently installed.)
  Preparing to unpack dnsmasq-base_2.80-1.1ubuntu1.6_amd64.deb ...
  Unpacking dnsmasq-base (2.80-1.1ubuntu1.6) over (2.80-1.1ubuntu1.5) ...
  Selecting previously unselected package dnsmasq-utils.
  Preparing to unpack dnsmasq-utils_2.80-1.1ubuntu1.6_amd64.deb ...
  Unpacking dnsmasq-utils (2.80-1.1ubuntu1.6) ...
  Preparing to unpack dnsmasq_2.80-1.1ubuntu1.6_all.deb ...
  Unpacking dnsmasq (2.80-1.1ubuntu1.6) over (2.80-1.1ubuntu1.5) ...
  Setting up dnsmasq-base (2.80-1.1ubuntu1.6) ...
  Setting up dnsmasq-utils (2.80-1.1ubuntu1.6) ...
  Setting up dnsmasq (2.80-1.1ubuntu1.6) ...
  Processing triggers for dbus (1.12.16-2ubuntu2.3) ...
  Processing triggers for man-db (2.9.1-1) ...
  Processing triggers for systemd (245.4-4ubuntu3.18) ...

  # dpkg -l | grep dnsmasq
  ii  dnsmasq2.80-1.1ubuntu1.6 all  
Small caching DNS proxy and DHCP/TFTP server
  ii  dnsmasq-base   2.80-1.1ubuntu1.6 amd64
Small caching DNS proxy and DHCP/TFTP server
  ii  dnsmasq-utils  2.80-1.1ubuntu1.6 amd64
Utilities for manipulating DHCP leases

  #2.2 Testing OK

  # for i in srv txt  a  a txt srv; do host -t $i test.foo. 127.0.0.1 | 
tail -n 1; done
  Host test.foo. not found: 3(NXDOMAIN)
  Host test.foo. not found: 3(NXDOMAIN)
  Host test.foo. not found: 3(NXDOMAIN)
  Host test.foo. not found: 3(NXDOMAIN)
  Host test.foo. not found: 3(NXDOMAIN)
  Host test.foo. not found: 3(NXDOMAIN)
  Host test.foo. not found: 3(NXDOMAIN)
  Host test.foo. not found: 3(NXDOMAIN)

  [ Where problems could occur ]

  It changes the program's behaviour by classifying as NXDOMAIN what
  used to be NODATA in some situations, so if a user had a workaround
  for this (in the form of a script or other kind of automatization) it
  will probably start to malfunction.

  The last rebuilding of the package for Focal was in May, so if any new
  dependencies or libs have been upgraded on this Ubuntu series this can
  impact the new rebuild.

  [ Other Info ]

  The patch is applied upstream and originated from a bug filed on
  Fedora side: https://bugzilla.redhat.com/show_bug.cgi?id=1674067

  [Original Report]
  ---
  We upgraded our openstack containers which host dnsmasq services from bionic 
to focal. With this we got an update of dnsmasq from 2.79 to 2.80 which 
introduced a bug in our setup where dnsmasq returns NODATA instead of NXDOMAIN.

  This is already fixed upstream with the following commit [1].

  The Ubuntu dnsmasq 2.80 package should get a backport with a release
  for the focal packages which includes this bug fix.

  [1]
  
https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=162e5e0062ce923c494cc64282f293f0ed64fc10

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1995260/+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 1995260] Re: dnsmasq focal 2.80 NODATA instead of NXDOMAIN bug

[Christian Ehrhardt ]

Great finding Miriam,
I've looked into it and fully agree.
Since I had all the data at that moment I filed bug 1998184 for ubuntu-fan.
Based on that we need to mask the tests and we can ignore them here in regard 
to this SRU (until fixed in ubuntu-fan).

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

Title:
  dnsmasq focal 2.80 NODATA instead of NXDOMAIN bug

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in dnsmasq source package in Focal:
  Fix Committed

Bug description:
  [SRU]

  [ Impact ]

  Sometimes dnsmasq is incorrectly returning NODATA instead of NXDOMAIN.
  This can lead to erroneous actions by clients who need to determine
  whether a domain name exists or not.

  [ Test Plan ]

  In a focal VM, install dnsmasq (apt install dnsmasq) if it wasn't
  installed yet.

  #0 Disabling systemd-resolved service and enabling resolution through
  dnsmasq.

  # systemctl disable --now systemd-resolved.service
  # rm -f /etc/resolv.conf
  # cat > /etc/resolv.conf << __EOF__
  nameserver 8.8.8.8
  __EOF__
  # systemctl start dnsmasq.service

  #1 Bad case

  # for i in srv txt  a  a txt srv; do host -t $i test.foo. 127.0.0.1 | 
tail -n 1; done
  Host test.foo. not found: 3(NXDOMAIN)
  Host test.foo. not found: 3(NXDOMAIN)
  Host test.foo. not found: 3(NXDOMAIN)
  test.foo has no A record
  Host test.foo. not found: 3(NXDOMAIN)
  test.foo has no A record
  test.foo has no TXT record
  test.foo has no SRV record

  #2 Good case

  #2.1 Installing new package

  # ls -1 *.deb
  dnsmasq-utils_2.80-1.1ubuntu1.6_amd64.deb
  dnsmasq-base_2.80-1.1ubuntu1.6_amd64.deb
  dnsmasq_2.80-1.1ubuntu1.6_all.deb

  # dpkg -i *.deb
  (Reading database ... 32073 files and directories currently installed.)
  Preparing to unpack dnsmasq-base_2.80-1.1ubuntu1.6_amd64.deb ...
  Unpacking dnsmasq-base (2.80-1.1ubuntu1.6) over (2.80-1.1ubuntu1.5) ...
  Selecting previously unselected package dnsmasq-utils.
  Preparing to unpack dnsmasq-utils_2.80-1.1ubuntu1.6_amd64.deb ...
  Unpacking dnsmasq-utils (2.80-1.1ubuntu1.6) ...
  Preparing to unpack dnsmasq_2.80-1.1ubuntu1.6_all.deb ...
  Unpacking dnsmasq (2.80-1.1ubuntu1.6) over (2.80-1.1ubuntu1.5) ...
  Setting up dnsmasq-base (2.80-1.1ubuntu1.6) ...
  Setting up dnsmasq-utils (2.80-1.1ubuntu1.6) ...
  Setting up dnsmasq (2.80-1.1ubuntu1.6) ...
  Processing triggers for dbus (1.12.16-2ubuntu2.3) ...
  Processing triggers for man-db (2.9.1-1) ...
  Processing triggers for systemd (245.4-4ubuntu3.18) ...

  # dpkg -l | grep dnsmasq
  ii  dnsmasq2.80-1.1ubuntu1.6 all  
Small caching DNS proxy and DHCP/TFTP server
  ii  dnsmasq-base   2.80-1.1ubuntu1.6 amd64
Small caching DNS proxy and DHCP/TFTP server
  ii  dnsmasq-utils  2.80-1.1ubuntu1.6 amd64
Utilities for manipulating DHCP leases

  #2.2 Testing OK

  # for i in srv txt  a  a txt srv; do host -t $i test.foo. 127.0.0.1 | 
tail -n 1; done
  Host test.foo. not found: 3(NXDOMAIN)
  Host test.foo. not found: 3(NXDOMAIN)
  Host test.foo. not found: 3(NXDOMAIN)
  Host test.foo. not found: 3(NXDOMAIN)
  Host test.foo. not found: 3(NXDOMAIN)
  Host test.foo. not found: 3(NXDOMAIN)
  Host test.foo. not found: 3(NXDOMAIN)
  Host test.foo. not found: 3(NXDOMAIN)

  [ Where problems could occur ]

  It changes the program's behaviour by classifying as NXDOMAIN what
  used to be NODATA in some situations, so if a user had a workaround
  for this (in the form of a script or other kind of automatization) it
  will probably start to malfunction.

  The last rebuilding of the package for Focal was in May, so if any new
  dependencies or libs have been upgraded on this Ubuntu series this can
  impact the new rebuild.

  [ Other Info ]

  The patch is applied upstream and originated from a bug filed on
  Fedora side: https://bugzilla.redhat.com/show_bug.cgi?id=1674067

  [Original Report]
  ---
  We upgraded our openstack containers which host dnsmasq services from bionic 
to focal. With this we got an update of dnsmasq from 2.79 to 2.80 which 
introduced a bug in our setup where dnsmasq returns NODATA instead of NXDOMAIN.

  This is already fixed upstream with the following commit [1].

  The Ubuntu dnsmasq 2.80 package should get a backport with a release
  for the focal packages which includes this bug fix.

  [1]
  
https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=162e5e0062ce923c494cc64282f293f0ed64fc10

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

[Touch-packages] [Bug 1996900] Re: display flashes

[Daniel van Vugt]

Thanks for the bug report. Next time the flashes occur, please run:

  journalctl -b0 > flashes.txt

and attach the resulting text file here.


** Tags added: amdgpu

** Summary changed:

- display flashes
+ [amdgpu] [KDE] Display flashes

** Package changed: xorg (Ubuntu) => linux (Ubuntu)

** Summary changed:

- [amdgpu] [KDE] Display flashes
+ [amdgpu] [KDE] Display flashes black

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

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

Title:
  [amdgpu] [KDE] Display flashes black

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  During normal usage the display sometimes flashes black. In particular
  some websites cause intense flickering with several black frames per
  second.

  This actually seems to happen in both Wayland and xorg sessions and
  flashes the entire screen, so it seems more like a driver bug but I'm
  not sure where to file that.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: xorg 1:7.7+23ubuntu2
  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
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Thu Nov 17 14:00:15 2022
  DistUpgraded: Fresh install
  DistroCodename: kinetic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raphael [1002:164e] (rev c1) (prog-if 
00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raphael [1002:164e]
  InstallationDate: Installed on 2022-10-30 (18 days ago)
  InstallationMedia: Lubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221017.1)
  MachineType: ASUS System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic 
root=UUID=bcf965e4-1a60-42fe-8033-214524d1908b ro quiet 
cryptdevice=UUID=66cc3c7b-e0bd-4535-b634-d56226dd88f1:luks-66cc3c7b-e0bd-4535-b634-d56226dd88f1
 root=/dev/mapper/luks-66cc3c7b-e0bd-4535-b634-d56226dd88f1 splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/08/2022
  dmi.bios.release: 6.3
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0603
  dmi.board.asset.tag: Default string
  dmi.board.name: TUF GAMING X670E-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0603:bd09/08/2022:br6.3:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX670E-PLUS:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996900/+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 1996496] Re: Cannot connect to Ubuntu BLE servers

[Daniel van Vugt]

Thanks for the bug report. Unfortunately we can't support personal
builds of BlueZ here. If you experience any issues with BlueZ that you
built yourself then please report them upstream at
https://github.com/bluez/bluez/issues

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

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

Title:
  Cannot connect to Ubuntu BLE servers

Status in bluez package in Ubuntu:
  Invalid

Bug description:
  I'm on Ubuntu 22.04.1 LTS, using bluez 5.65 (built from sources by this 
guide: https://docs.embeddedts.com/BLE_Examples), and doing the following steps:
  1. Run `python3 /usr/local/lib/bluez/test/example-advertisement`
  2. Run `/usr/local/lib/bluez/test/example-gatt-server`
  3. Use nRF Connect app on Android 9 phone to connect to the 
"TestAdvertisement" device

  The outcome is that the phone app tries to connect, but fails, leaving
  me with a view of the GATT services and characteristics, but with no
  way of accessing (read/write/notify) it. I have tried many other BLE
  server implementations, but for the bug reporting I focused on the
  most trusted reference.

  Full logs are attached. The relevant part of the btmon log is here:
  @ MGMT Event: Device Connected (0x000b) plen 13 {0x0001} [hci0] 945.575247
  LE Address: 4D:2C:9A:88:F1:86 (Resolvable)
  Flags: 0x
  Data length: 0
  < HCI Command: LE Read Remote Used Features (0x08|0x0016) plen 2 #32 [hci0] 
945.575351
  Handle: 3585 Address: 4D:2C:9A:88:F1:86 (Resolvable)
  @ RAW Open: btmon (privileged) version 2.22 {0x0002} 945.575453
  @ RAW Close: btmon {0x0002} 945.575462
  > HCI Event: LE Meta Event (0x3e) plen 4 #33 [hci0] 945.575984
LE Channel Selection Algorithm (0x14)
  Handle: 3585 Address: 4D:2C:9A:88:F1:86 (Resolvable)
  Algorithm: #1 (0x00)
  > HCI Event: LE Meta Event (0x3e) plen 6 #34 [hci0] 945.576990
LE Advertising Set Terminated (0x12)
  Status: Success (0x00)
  Handle: 1
  Connection handle: 3585
  Number of completed extended advertising events: 0
  > HCI Event: Command Status (0x0f) plen 4 #35 [hci0] 945.578094
LE Read Remote Used Features (0x08|0x0016) ncmd 1
  Status: Unsupported Remote Feature / Unsupported LMP Feature (0x1a)
  < HCI Command: Disconnect (0x01|0x0006) plen 3 #36 [hci0] 945.578193
  Handle: 3585 Address: 4D:2C:9A:88:F1:86 (Resolvable)
  Reason: Remote User Terminated Connection (0x13)
  > HCI Event: Command Status (0x0f) plen 4 #37 [hci0] 945.579984
Disconnect (0x01|0x0006) ncmd 1
  Status: Success (0x00)
  > HCI Event: Disconnect Complete (0x05) plen 4 #38 [hci0] 945.652123
  Status: Success (0x00)
  Handle: 3585 Address: 4D:2C:9A:88:F1:86 (Resolvable)
  Reason: Connection Terminated By Local Host (0x16)
  @ MGMT Event: Device Disconnected (0x000c) plen 8 {0x0001} [hci0] 945.652224
  LE Address: 4D:2C:9A:88:F1:86 (Resolvable)
  Reason: Connection terminated by local host (0x02)

  The Additional information:
  $ hciconfig -a
  hci0: Type: Primary Bus: USB
   BD Address: BC:6E:E2:D0:B1:27 ACL MTU: 1021:4 SCO MTU: 96:6
   UP RUNNING PSCAN
   RX bytes:3074 acl:43 sco:0 events:194 errors:0
   TX bytes:7295 acl:42 sco:0 commands:125 errors:0
   Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87
   Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
   Link policy: RSWITCH SNIFF
   Link mode: PERIPHERAL ACCEPT
   Name: 'epitos'
   Class: 0x6c010c
   Service Classes: Rendering, Capturing, Audio, Telephony
   Device Class: Computer, Laptop
   HCI Version: (0xc) Revision: 0x3484
   LMP Version: (0xc) Subversion: 0x3484
   Manufacturer: Intel Corp. (2)

  $ bluetoothctl
  Agent registered
  [CHG] Controller BC:6E:E2:D0:B1:27 Pairable: yes
  [bluetooth]# show
  Controller BC:6E:E2:D0:B1:27 (public)
   Name: epitos
   Alias: epitos
   Class: 0x006c010c
   Powered: yes
   Discoverable: no
   DiscoverableTimeout: 0x00b4
   Pairable: yes
   UUID: A/V Remote Control (110e--1000-8000-00805f9b34fb)
   UUID: Handsfree Audio Gateway (111f--1000-8000-00805f9b34fb)
   UUID: PnP Information (1200--1000-8000-00805f9b34fb)
   UUID: Audio Sink (110b--1000-8000-00805f9b34fb)
   UUID: Headset (1108--1000-8000-00805f9b34fb)
   UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
   UUID: Generic Access Profile (1800--1000-8000-00805f9b34fb)
   UUID: Audio Source (110a--1000-8000-00805f9b34fb)
   UUID: Generic Attribute Profile (1801--1000-8000-00805f9b34fb)
   UUID: Vendor specific (12345678-1234-5678-1234-56789abcdef0)
   UUID: Device Information (180a--1000-8000-00805f9b34fb)
   UUID: Battery Service (180f--1000-8000-00805f9b34fb)
   UUID: Heart Rate (180d--1000-8000-00805f9

[Touch-packages] [Bug 1991235] Re: systemd 237-3ubuntu10.56 times out on getpwuid

[Launchpad Bug Tracker]

[Expired for systemd (Ubuntu) because there has been no activity for 60
days.]

** Changed in: systemd (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  systemd 237-3ubuntu10.56 times out on getpwuid

Status in systemd package in Ubuntu:
  Expired

Bug description:
  We've recently upgraded packages on one of our images from systemd
  237-3ubuntu10.53 to 237-3ubuntu10.56 and are experiencing some
  performance issues. A kernel upgrade also happened (4.15.0.192.177 ->
  4.15.0.193.178) but I thought I'd check here first. Sorry if I'm
  raising this in the wrong place!

  Various operations are very slow:
  * logging in via SSH
  * ps auxf
  * top
  * systemctl
  * + more

  Weirdly, the issue seems to only happen on Amazon EC2 imported
  machines, and not when running under ESXi, although this may be a red
  herring.

  strace-ing ps shows a timeout reading from some kind of DBus socket:

  recvmsg(6, {msg_name=NULL, msg_namelen=0, 
msg_iov=[{iov_base="/org/freedesktop/DBus\0\0\0\2\1s\0\24\0\0\0"..., 
iov_len=146}], msg_iovlen=1, msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, 
MSG_DONTWAIT|MSG_NOSIGNAL|MSG_CMSG_CLOEXEC) = 146
   > /lib/x86_64-linux-gnu/libc-2.27.so(recvmsg+0x14) [0x122934]
   > /lib/x86_64-linux-gnu/libnss_systemd.so.2(_nss_systemd_getpwnam_r+0xf257) 
[0x21df7]
   > /lib/x86_64-linux-gnu/libnss_systemd.so.2() [0x10fd1]
   > /lib/x86_64-linux-gnu/libnss_systemd.so.2(_nss_systemd_getpwuid_r+0x377) 
[0x12b27]
   > /lib/x86_64-linux-gnu/libc-2.27.so(getpwuid_r+0x145) [0xe39e5]
   > /lib/x86_64-linux-gnu/libc-2.27.so(getpwuid+0x98) [0xe3148]
   > /lib/x86_64-linux-gnu/libprocps.so.6.0.0(pwcache_get_user+0x5c) [0x5bfc]
   > /lib/x86_64-linux-gnu/libprocps.so.6.0.0(pwcache_get_user+0x1ebb) [0x7a5b]
   > /lib/x86_64-linux-gnu/libprocps.so.6.0.0(readproc+0x149) [0x8659]
   > /lib/x86_64-linux-gnu/libprocps.so.6.0.0(readproctab2+0x8a) [0x912a]
   > /bin/ps(_init+0xe3b) [0xaef3]
   > /lib/x86_64-linux-gnu/libc-2.27.so(__libc_start_main+0xe7) [0x21c87]
   > /bin/ps(_init+0x1322) [0xb3da]
  recvmsg(6, {msg_namelen=0}, MSG_DONTWAIT|MSG_NOSIGNAL|MSG_CMSG_CLOEXEC) = -1 
EAGAIN (Resource temporarily unavailable)
   > /lib/x86_64-linux-gnu/libc-2.27.so(recvmsg+0x14) [0x122934]
   > /lib/x86_64-linux-gnu/libnss_systemd.so.2(_nss_systemd_getpwnam_r+0xf257) 
[0x21df7]
   > /lib/x86_64-linux-gnu/libnss_systemd.so.2() [0x10fd1]
   > /lib/x86_64-linux-gnu/libnss_systemd.so.2(_nss_systemd_getpwuid_r+0x377) 
[0x12b27]
   > /lib/x86_64-linux-gnu/libc-2.27.so(getpwuid_r+0x145) [0xe39e5]
   > /lib/x86_64-linux-gnu/libc-2.27.so(getpwuid+0x98) [0xe3148]
   > /lib/x86_64-linux-gnu/libprocps.so.6.0.0(pwcache_get_user+0x5c) [0x5bfc]
   > /lib/x86_64-linux-gnu/libprocps.so.6.0.0(pwcache_get_user+0x1ebb) [0x7a5b]
   > /lib/x86_64-linux-gnu/libprocps.so.6.0.0(readproc+0x149) [0x8659]
   > /lib/x86_64-linux-gnu/libprocps.so.6.0.0(readproctab2+0x8a) [0x912a]
   > /bin/ps(_init+0xe3b) [0xaef3]
   > /lib/x86_64-linux-gnu/libc-2.27.so(__libc_start_main+0xe7) [0x21c87]
   > /bin/ps(_init+0x1322) [0xb3da]
  ppoll([{fd=6, events=POLLIN}], 1, {tv_sec=24, tv_nsec=995725000}, NULL, 8) = 
0 (Timeout) <
   > /lib/x86_64-linux-gnu/libc-2.27.so(ppoll+0x4a) [0x114c5a]
   > /lib/x86_64-linux-gnu/libnss_systemd.so.2(_nss_systemd_getpwnam_r+0x1795f) 
[0x2a4ff]
   > /lib/x86_64-linux-gnu/libnss_systemd.so.2() [0x1100a]
   > /lib/x86_64-linux-gnu/libnss_systemd.so.2(_nss_systemd_getpwuid_r+0x377) 
[0x12b27]
   > /lib/x86_64-linux-gnu/libc-2.27.so(getpwuid_r+0x145) [0xe39e5]
   > /lib/x86_64-linux-gnu/libc-2.27.so(getpwuid+0x98) [0xe3148]
   > /lib/x86_64-linux-gnu/libprocps.so.6.0.0(pwcache_get_user+0x5c) [0x5bfc]
   > /lib/x86_64-linux-gnu/libprocps.so.6.0.0(pwcache_get_user+0x1ebb) [0x7a5b]
   > /lib/x86_64-linux-gnu/libprocps.so.6.0.0(readproc+0x149) [0x8659]
   > /lib/x86_64-linux-gnu/libprocps.so.6.0.0(readproctab2+0x8a) [0x912a]
   > /bin/ps(_init+0xe3b) [0xaef3]
   > /lib/x86_64-linux-gnu/libc-2.27.so(__libc_start_main+0xe7) [0x21c87]
   > /bin/ps(_init+0x1322) [0xb3da]


  LSB release output:

  Description:Ubuntu 18.04.6 LTS
  Release:18.04

  Unfortunately I'm unsure how to investigate this further.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1991235/+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 1998169] Re: useradd command does not copy all of /etc/skel

[Chris Deckard]

** Description changed:

  
  I know the useradd command is discouraged, but I wanted to report the bug to 
make the maintainers of the package aware.
  
- Recently there was an update of Ubuntu's passwd which is sourced from
- shadow from version 4.8.1-1ubuntu5.20.04.2 to version
+ Recently there was an update of Ubuntu's passwd package which is sourced
+ from shadow from version 4.8.1-1ubuntu5.20.04.2 to version
  4.8.1-1ubuntu5.20.04.3
  
+ When using the useradd command, the /etc/skel directory with contents
+ below, an only copies in one empty folder.
  
- When using the useradd command, the /etc/skel directory with contents 
  
  ls -lah /etc/skel
  total 60K
  drwxrwxrwx  10 root user 4.0K Nov 28 18:33 .
  drwxr-xr-x 155 root root  12K Nov 28 19:12 ..
  drwxrwxrwx   2 root user 4.0K Nov 28 18:23 .backgrounds
  -rwxrwxrwx   1 root user  220 Nov 28 18:23 .bash_logout
  -rwxrwxrwx   1 root user 3.7K Nov 28 18:23 .bashrc
  drwxrwxrwx   6 root user 4.0K Nov 28 18:23 .config
  drwxrwxrwx   3 root user 4.0K Nov 28 18:23 Desktop
  drwxrwxrwx   2 root user 4.0K Nov 28 18:30 .fonts_stuff
  drwxrwxrwx   2 root user 4.0K Nov 28 18:23 .icons
  -rwxrwxrwx   1 root user  765 Nov 28 18:23 .profile
  drwxrwxrwx   2 root root 4.0K Nov 28 18:32 testfolderempty
  drwxrwxrwx   3 root user 4.0K Nov 28 18:23 .themes
  drwxrwxrwx  14 root user 4.0K Nov 28 18:23 WinAte
- 
- 
- only copies in the one empty folder.
  
  ls -lah /home/user20
  total 12K
  drwx--  3 user20 user 4.0K Nov 28 19:12 .
  drwxr-xr-x 18 root   root 4.0K Nov 28 19:12 ..
  drwx--  2 user20 user 4.0K Nov 28 19:12 WinAte
  
  ls -lah /home/user20/WinAte/
  total 8.0K
  drwx-- 2 user20 user 4.0K Nov 28 19:12 .
  drwx-- 3 user20 user 4.0K Nov 28 19:12 ..
  
  
  I noticed in the strace calls for useradd that the kernel is returning the 
correct count of directories, but the useradd is clearly not copying all of 
them. Below is the strace output.
  
  
- strace useradd -k /etc/skel -g 900 -m -s /bin/bash -p P@ssw0rd! -c User20 
user20
+ strace useradd -k /etc/skel -g 900 -m -s /bin/bash -p a_password -c User20 
user20
  execve("/usr/sbin/useradd", ["useradd", "-k", "/etc/skel", "-g", "900", "-m", 
"-s", "/bin/bash", "-p", "P@ssw0rd!", "-c", "User20", "user20"], 0x7fffe10eba10 
/* 24 vars */) = 0
  brk(NULL)   = 0x5631ba1c2000
  arch_prctl(0x3001 /* ARCH_??? */, 0x7fff0e47bab0) = -1 EINVAL (Invalid 
argument)
  access("/etc/ld.so.preload", R_OK)  = -1 ENOENT (No such file or 
directory)
  openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
  fstat(3, {st_mode=S_IFREG|0644, st_size=98383, ...}) = 0
  mmap(NULL, 98383, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fea9b7bf000
  close(3)= 0
  openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libaudit.so.1", O_RDONLY|O_CLOEXEC) = 
3
  read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\3407\0\0\0\0\0\0"..., 
832) = 832
  fstat(3, {st_mode=S_IFREG|0644, st_size=133200, ...}) = 0
  mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7fea9b7bd000
  mmap(NULL, 176296, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 
0x7fea9b791000
  mprotect(0x7fea9b794000, 118784, PROT_NONE) = 0
  mmap(0x7fea9b794000, 32768, PROT_READ|PROT_EXEC, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x3000) = 0x7fea9b794000
  mmap(0x7fea9b79c000, 81920, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 
3, 0xb000) = 0x7fea9b79c000
  mmap(0x7fea9b7b1000, 8192, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1f000) = 0x7fea9b7b1000
  mmap(0x7fea9b7b3000, 37032, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7fea9b7b3000
  close(3)= 0
  openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libselinux.so.1", O_RDONLY|O_CLOEXEC) 
= 3
  read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0@p\0\0\0\0\0\0"..., 
832) = 832
  fstat(3, {st_mode=S_IFREG|0644, st_size=163200, ...}) = 0
  mmap(NULL, 174600, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 
0x7fea9b766000
  mprotect(0x7fea9b76c000, 135168, PROT_NONE) = 0
  mmap(0x7fea9b76c000, 102400, PROT_READ|PROT_EXEC, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x6000) = 0x7fea9b76c000
  mmap(0x7fea9b785000, 28672, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 
3, 0x1f000) = 0x7fea9b785000
  mmap(0x7fea9b78d000, 8192, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x26000) = 0x7fea9b78d000
  mmap(0x7fea9b78f000, 6664, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7fea9b78f000
  close(3)= 0
  openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libsemanage.so.1", 
O_RDONLY|O_CLOEXEC) = 3
  read(

[Touch-packages] [Bug 1998169] [NEW] useradd command does not copy all of /etc/skel

[Chris Deckard]

Public bug reported:


I know the useradd command is discouraged, but I wanted to report the bug to 
make the maintainers of the package aware.

Recently there was an update of Ubuntu's passwd which is sourced from
shadow from version 4.8.1-1ubuntu5.20.04.2 to version
4.8.1-1ubuntu5.20.04.3


When using the useradd command, the /etc/skel directory with contents 

ls -lah /etc/skel
total 60K
drwxrwxrwx  10 root user 4.0K Nov 28 18:33 .
drwxr-xr-x 155 root root  12K Nov 28 19:12 ..
drwxrwxrwx   2 root user 4.0K Nov 28 18:23 .backgrounds
-rwxrwxrwx   1 root user  220 Nov 28 18:23 .bash_logout
-rwxrwxrwx   1 root user 3.7K Nov 28 18:23 .bashrc
drwxrwxrwx   6 root user 4.0K Nov 28 18:23 .config
drwxrwxrwx   3 root user 4.0K Nov 28 18:23 Desktop
drwxrwxrwx   2 root user 4.0K Nov 28 18:30 .fonts_stuff
drwxrwxrwx   2 root user 4.0K Nov 28 18:23 .icons
-rwxrwxrwx   1 root user  765 Nov 28 18:23 .profile
drwxrwxrwx   2 root root 4.0K Nov 28 18:32 testfolderempty
drwxrwxrwx   3 root user 4.0K Nov 28 18:23 .themes
drwxrwxrwx  14 root user 4.0K Nov 28 18:23 WinAte


only copies in the one empty folder.

ls -lah /home/user20
total 12K
drwx--  3 user20 user 4.0K Nov 28 19:12 .
drwxr-xr-x 18 root   root 4.0K Nov 28 19:12 ..
drwx--  2 user20 user 4.0K Nov 28 19:12 WinAte

ls -lah /home/user20/WinAte/
total 8.0K
drwx-- 2 user20 user 4.0K Nov 28 19:12 .
drwx-- 3 user20 user 4.0K Nov 28 19:12 ..


I noticed in the strace calls for useradd that the kernel is returning the 
correct count of directories, but the useradd is clearly not copying all of 
them. Below is the strace output.


strace useradd -k /etc/skel -g 900 -m -s /bin/bash -p P@ssw0rd! -c User20 user20
execve("/usr/sbin/useradd", ["useradd", "-k", "/etc/skel", "-g", "900", "-m", 
"-s", "/bin/bash", "-p", "P@ssw0rd!", "-c", "User20", "user20"], 0x7fffe10eba10 
/* 24 vars */) = 0
brk(NULL)   = 0x5631ba1c2000
arch_prctl(0x3001 /* ARCH_??? */, 0x7fff0e47bab0) = -1 EINVAL (Invalid argument)
access("/etc/ld.so.preload", R_OK)  = -1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=98383, ...}) = 0
mmap(NULL, 98383, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7fea9b7bf000
close(3)= 0
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libaudit.so.1", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\3407\0\0\0\0\0\0"..., 
832) = 832
fstat(3, {st_mode=S_IFREG|0644, st_size=133200, ...}) = 0
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 
0x7fea9b7bd000
mmap(NULL, 176296, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7fea9b791000
mprotect(0x7fea9b794000, 118784, PROT_NONE) = 0
mmap(0x7fea9b794000, 32768, PROT_READ|PROT_EXEC, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x3000) = 0x7fea9b794000
mmap(0x7fea9b79c000, 81920, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 
0xb000) = 0x7fea9b79c000
mmap(0x7fea9b7b1000, 8192, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1f000) = 0x7fea9b7b1000
mmap(0x7fea9b7b3000, 37032, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7fea9b7b3000
close(3)= 0
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libselinux.so.1", O_RDONLY|O_CLOEXEC) = 
3
read(3, "\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0@p\0\0\0\0\0\0"..., 832) 
= 832
fstat(3, {st_mode=S_IFREG|0644, st_size=163200, ...}) = 0
mmap(NULL, 174600, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7fea9b766000
mprotect(0x7fea9b76c000, 135168, PROT_NONE) = 0
mmap(0x7fea9b76c000, 102400, PROT_READ|PROT_EXEC, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x6000) = 0x7fea9b76c000
mmap(0x7fea9b785000, 28672, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 
0x1f000) = 0x7fea9b785000
mmap(0x7fea9b78d000, 8192, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x26000) = 0x7fea9b78d000
mmap(0x7fea9b78f000, 6664, PROT_READ|PROT_WRITE, 
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7fea9b78f000
close(3)= 0
openat(AT_FDCWD, "/lib/x86_64-linux-gnu/libsemanage.so.1", O_RDONLY|O_CLOEXEC) 
= 3
read(3, 
"\177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0>\0\1\0\0\0\340\364\0\0\0\0\0\0"..., 832) = 
832
fstat(3, {st_mode=S_IFREG|0644, st_size=268920, ...}) = 0
mmap(NULL, 271912, PROT_READ, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0x7fea9b723000
mmap(0x7fea9b73, 143360, PROT_READ|PROT_EXEC, 
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0xd000) = 0x7fea9b73
mmap(0x7fea9b753000, 65536, PROT_READ, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 
0x3) = 0x7fea9b753000
mmap(0x7fea9b763000, 12288, PROT_READ|PROT_WRITE, 

[Touch-packages] [Bug 648212] Re: Connect automatically does nothing for VPN connections

[Bernard Stafford]

https://answers.launchpad.net/ubuntu/+source/network-manager/+question/703893
comment # 4 - "I didn't install the wireguard package"

** Changed in: network-manager (Ubuntu)
   Status: Triaged => Invalid

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

Title:
  Connect automatically does nothing for VPN connections

Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  Checking "Connect automatically" in the configurations tab of VPN connections 
does nothing.
  It's like that for at least a year now.

  I would like to see it connecting to my VPN after a wireless/wired
  internet connection was activated.

  This is still an issue in maverick.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/648212/+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 1988418] Re: Please merge initramfs-tools 0.142 from Debian unstable.

[Steve Langasek]

My standard way of reviewing a merge is to do the merge myself and see
what comes up different.  Here are my observations:

conf/initramfs.conf: the commented COMPRESSLEVEL setting should match
the default, which for us is 1, not 3.

debian/control: upstream has Recommends: ${busybox:Recommends}, zstd,
but you only have Recommends: zstd.  Why?

debian/rules: you caught that there were build-time tests added by us
that should be retained even though upstream dropped their override;
good (I missed this).

hook-functions: upstream landed the change to exclude modems from the
net usb drivers, but we had cdc-phonet.ko in our list but Debian does
not.  I do not know why Debian did not include it; I think we should
include it in the merge and forward to Debian for consideration.

+   elif [ -n "${DEVICE}" ] || [ -n "${DEVICE6}" ]; then

FWIW I would write this as elif [ -n "$DEVICE$DEVICE6" ]; then

Otherwise, this looks good to me.

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

Title:
  Please merge initramfs-tools 0.142 from Debian unstable.

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  Please merge initramfs-tools 0.142 from Debian unstable.

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1988418/+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 1917887] Re: Network Manager OpenVPN nested connections fail to setup routes correctly

[Bug Watch Updater]

** Changed in: openvpn
   Status: Fix Released => New

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

Title:
  Network Manager OpenVPN nested connections fail to setup routes
  correctly

Status in OpenVPN:
  New
Status in network-manager package in Ubuntu:
  Triaged
Status in openvpn package in Ubuntu:
  Invalid

Bug description:
  Setup:
  Host lan: 192.168.0.238/24
  Host Default gw: 192.168.0.1

  ip route:
  default via 192.168.0.1 dev eno1 proto dhcp metric 100 
  169.254.0.0/16 dev eno1 scope link metric 1000 
  192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.238 metric 100 

  
  Primary OpenVPN (check "Use this connection only for resources on its 
network"):
  server ip: public a.b.c.d
  OpenVPN Tunnel: 192.168.1.0/24
  routes pushed: 192.168.100.0/24

  First VPN works OK:
  default via 192.168.0.1 dev eno1 proto dhcp metric 100 
  169.254.0.0/16 dev eno1 scope link metric 1000 
  192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.238 metric 100 
  192.168.0.1 dev eno1 proto static scope link metric 100 
  192.168.100.0/24 via 192.168.10.1 dev tun0 proto static metric 50 
  a.b.c.d via 192.168.0.1 dev eno1 proto static metric 100 

  
  Secondary OpenVPN  (check "Use this connection only for resources on its 
network"):
  server ip: private 192.168.100.10 
  OpenVPN Tunnel: 192.168.20.0/24
  routes pushed: 192.168.200.0/24

  Second VPN Connect OK, routing table is wrong:
  default via 192.168.0.1 dev eno1 proto dhcp metric 100 
  192.168.200.0/24 via 192.168.20.1 dev tun1 
  192.168.20.0/24 dev tun1 proto kernel scope link src 192.168.20.59 
  169.254.0.0/16 dev eno1 scope link metric 1000 
  192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.238 metric 100 
  192.168.0.1 dev eno1 proto static scope link metric 100 
  192.168.100.0/24 via 192.168.10.1 dev tun0 proto static metric 50 
  a.b.c.d via 192.168.0.1 dev eno1 proto static metric 100 
  192.168.100.10 via 192.168.0.1 dev eno1 proto static metric 100 <- this is 
wrong, the openVPN#2 Gateway is not on the local lan

  Correct routing table using "sudo /usr/sbin/openvpn
  /path/to/config.openvpn" (same a Network Manager)

  default via 192.168.0.1 dev eno1 proto dhcp metric 100 
  192.168.200.0/24 via 192.168.20.1 dev tun1 
  192.168.20.0/24 dev tun1 proto kernel scope link src 192.168.20.59 
  169.254.0.0/16 dev eno1 scope link metric 1000 
  192.168.0.0/24 dev eno1 proto kernel scope link src 192.168.0.238 metric 100 
  192.168.0.1 dev eno1 proto static scope link metric 100 
  192.168.100.0/24 via 192.168.10.1 dev tun0 proto static metric 50 
  a.b.c.d via 192.168.0.1 dev eno1 proto static metric 100 

  It seems that Network Manager add a wrong additional route not added
  by the openvpn bin:

  192.168.100.10 via 192.168.0.1 dev eno1 proto static metric 100

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: openvpn 2.4.7-1ubuntu2
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar  5 12:44:39 2021
  InstallationDate: Installed on 2021-02-19 (13 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: openvpn
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/openvpn/+bug/1917887/+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 1964763] Re: QtChooser doesn't support qt6

[Eric Levy]

Adding further configuration for Chooser may support invocation of tools
for Qt 6, but desktop icons, for example, for Designer, are also
unavailable except for Qt 5.

Perhaps the report would be more appropriate for a different package.
Unfortunately, I am not adequately familiar with the system. The
organization of the various packages for Qt 6 is quite chaotic.

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

Title:
  QtChooser doesn't support qt6

Status in qtchooser package in Ubuntu:
  Confirmed

Bug description:
  qtchooser doesn't run qt6 applications because it doesn't have a
  qt6.conf/6.conf file yet.

  In order to work, it must have two files `/usr/lib/x86_64-linux-
  gnu/qtchooser/qt6.conf` and a `/usr/lib/x86_64-linux-
  gnu/qtchooser/6.conf` with this content:

  
  ```
  /usr/lib/qt6/bin
  /usr/lib/x86_64-linux-gnu
  ```

  Without it, lupdate, lrelease, and any other qt6 tools show this
  error: `could not find a Qt installation of ''`

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtchooser/+bug/1964763/+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 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu

[Adrien Nader]

I put together some notes and work-arounds in order to provide a simpler
reference for people hitting this issue. I didn't test everything below
but nothing should be risky.


# Summary

Grub attempts to read the initrd into a memory location that is too
small.

This issue is caused by a combination of several factors:
- Grub not setting aside enough space for the initrd in memory and not at the 
right location,
- Initrds having grown due to holding more modules and more firmware. This is 
especially the case with the nvidia proprietary driver.
- Typical screen resolutions and their associated buffers in memory having 
increased.

A related issue is not having enough space in /boot to hold enough
initrds.

# Solutions

There are four ways to tackle these issues:
- Patch grub,
- Have fewer modules,
- Compress initrds more,
- Lower screen resolution at boot.

## Patch grub
This is being worked on. It’s the trickier option so I’m not going to provide 
details but you can find that in the discussion above.

## Have fewer modules
The default configuration creates initrds that are meant to be universal in 
order to accommodate as many hardware variants as possible. Unsurprisingly this 
makes initrds much bigger.

It is possible to change the value of MODULES to ‘dep’ in
/etc/initramfs-tools/initramfs.conf . This will drastically reduce the
initrd size in virtually every configuration at the cost of not
supporting during boot hardware that is not plugged when the initrd
generation takes place.


## Compress initrds more
Change the value of COMPRESS in /etc/initramfs-tools/initramfs.conf .
In terms of compression level, you will have something along the lines of the 
following:
lz4: 74066711
zstd: 54260379
gzip: 53829310
xz: 29665544

NB: these values are only valid on one specific machine and
configuration; they are only meant to give an idea of compression ratio
that can be obtained but the initrd uses MODULES=dep as outlined above.

With a small hack, it is also possible to make xz compression much faster at a 
small cost in compression by adding the following at the end of initramfs.conf:
export XZ_OPT='--lzma2=preset=0,dict=8M'

In the future, it will be possible to directly set compression levels
for every compression method.

## Lower screen resolution at boot
You can use a lower resolution screen when booting.

You can also edit /etc/default/grub and use the following:
GRUB_GFXMODE=640x480
Remember to run update-grub afterwards.
If you need to do it at boot-time, you will use GFXMODE instead (no ‘GRUB_’ 
prefix).

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

Title:
  Can't boot: "error: out of memory." immediately after the grub menu

Status in grub:
  Unknown
Status in OEM Priority Project:
  Triaged
Status in grub2-signed package in Ubuntu:
  Triaged
Status in grub2-unsigned package in Ubuntu:
  Triaged
Status in initramfs-tools package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

   * In some cases, if the users’ initramfs grow bigger, then it’ll
  likely not be able to be loaded by grub2.

   * Some real cases from OEM projects:

  In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
  puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
  Also the gfxpayload=auto will remain to use 4K resolution since it’s
  what EFI POST passed.

  In this case, the grub isn't able to load initramfs because the
  grub_memalign() won't be able to get suitable memory for the larger
  file:

  ```
  #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
  #1 0x7dd7b074 in grub_malloc (size=592214020) at 
../../../grub-core/kern/mm.c:408
  #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
  at ../../../grub-core/kern/verifiers.c:150
  #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 
"/boot/initrd.img-5.17.0-1011-oem",
  type=131076) at ../../../grub-core/kern/file.c:121
  #4 0x7bcd5a30 in ?? ()
  #5 0x7fe21247 in ?? ()
  #6 0x7bc030c8 in ?? ()
  #7 0x00017fe21238 in ?? ()
  #8 0x7bcd5320 in ?? ()
  #9 0x7fe21250 in ?? ()
  #10 0x in ?? ()
  ```

  Based on grub_mm_dump, we can see the memory fragment (some parts seem
  likely be used because of 4K resolution?) and doesn’t have available
  contiguous memory for larger file as:

  ```
  grub_real_malloc(...)
  ...
  if (cur->size >= n + extra)
  ```

  Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
  guide 4.2.3[2], we can ask 32bits+ on AllocatePages().

  As most X86_64 platforms should support 64 bits addressing, we should
  extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
  memory.

   * When users grown the initramfs, then probably will get initramfs

[Touch-packages] [Bug 1994165] Re: CMS_final: do not ignore CMS_dataFinal result

[Adrien Nader]

We'd need more details about the issue and its actual impact for you
since upstream doesn't consider this a security issue since it only
happens when signing, not when checking signatures (which makes sense).
Without this there is no process for pushing an update to a released
version.

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

Title:
  CMS_final: do not ignore CMS_dataFinal result

Status in openssl package in Ubuntu:
  Triaged
Status in openssl source package in Jammy:
  Triaged
Status in openssl source package in Kinetic:
  Triaged

Bug description:
  https://github.com/openssl/openssl/pull/18876

  The CMS_dataFinal result is important as signature may fail, however, it
  is ignored while returning success from CMS_final.

  Please add this fix to The openssl 3.0.2 "Jammy Jellyfish (supported)"

  Thanks

  Upstream commit:

  ```
  commit 67c0460b89cc1b0644a1a59af78284dfd8d720af
  Author: Alon Bar-Lev 
  Date:   Tue Jul 26 15:17:06 2022 +0300

  Handle SMIME_crlf_copy return code
  
  Currently the SMIME_crlf_copy result is ignored in all usages. It does
  return failure when memory allocation fails.
  
  This patch handles the SMIME_crlf_copy return code in all occurrences.
  
  Signed-off-by: Alon Bar-Lev 
  
  Reviewed-by: Tomas Mraz 
  Reviewed-by: Paul Dale 
  Reviewed-by: Hugo Landau 
  (Merged from https://github.com/openssl/openssl/pull/18876)
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1994165/+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 1998082] Re: Hotspot Login window [gnome-shell-portal-helper] randomly opens with https://help.ubuntu.com

[Jeremy Bicha]

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

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

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

Title:
  Hotspot Login window [gnome-shell-portal-helper] randomly opens with
  https://help.ubuntu.com

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hotspot Login window [gnome-shell-portal-helper] randomly opens with
  https://help.ubuntu.com

  I'm not even using wifi. I don't care about hotspots.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell 43.1-2ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 28 16:40:28 2022
  DisplayManager: gdm3
  ExecutablePath: /usr/libexec/gnome-shell-portal-helper
  GsettingsChanges:
   b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'43.0'"
   b'org.gnome.desktop.app-folders' b'folder-children' b"['Utilities', 'YaST']"
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
   b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
  InstallationDate: Installed on 2022-11-28 (0 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126)
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANGUAGE=en_AU:en
   LANG=en_AU.UTF-8
  RelatedPackageVersions: mutter-common 43.0-1ubuntu5
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1998082/+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 1998082] Re: Hotspot Login window [gnome-shell-portal-helper] randomly opens with https://help.ubuntu.com

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Hotspot Login window [gnome-shell-portal-helper] randomly opens with
  https://help.ubuntu.com

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hotspot Login window [gnome-shell-portal-helper] randomly opens with
  https://help.ubuntu.com

  I'm not even using wifi. I don't care about hotspots.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: gnome-shell 43.1-2ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-21.21-generic 5.19.7
  Uname: Linux 5.19.0-21-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 28 16:40:28 2022
  DisplayManager: gdm3
  ExecutablePath: /usr/libexec/gnome-shell-portal-helper
  GsettingsChanges:
   b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'43.0'"
   b'org.gnome.desktop.app-folders' b'folder-children' b"['Utilities', 'YaST']"
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
   b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
  InstallationDate: Installed on 2022-11-28 (0 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126)
  ProcEnviron:
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
   LANGUAGE=en_AU:en
   LANG=en_AU.UTF-8
  RelatedPackageVersions: mutter-common 43.0-1ubuntu5
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1998082/+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 1997189] Re: [BPO] elfutils/0.188-1 from Lunar

[Sergio Durigan Junior]

Ping.

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

Title:
   [BPO] elfutils/0.188-1 from Lunar

Status in elfutils package in Ubuntu:
  Fix Released
Status in elfutils source package in Jammy:
  New

Bug description:
  [Impact]

   * elfutils ships many ELF/DWARF related tools that are interesting
  for users and developers of low level code.

   * More specifically, elfutils ships the debuginfod library and
  server. The latest upstream version (0.188) introduces many
  interesting features that should make the life of debuginfod users
  easier; one of those features is the ability to serve sections of
  DWARF, instead of the whole file.  I intend to update Ubuntu's
  debuginfod instance to use this new package in the near future.

  [Scope]

   * I will backport elfutils/0.188 from Lunar.

   * I will backport elfutils/0.188 to Jammy.

  [Other Info]

   * None so far.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/elfutils/+bug/1997189/+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 1997533] Re: flac 1.4.2+ds-2 in lunar proposed does not build on i386 - missing pandoc build dep

[Launchpad Bug Tracker]

This bug was fixed in the package flac - 1.4.2+ds-2ubuntu1

---
flac (1.4.2+ds-2ubuntu1) lunar; urgency=medium

  * Do not build and install manpages on i386. Build dep pandoc is
not available in Ubuntu for i386. (LP: #1997533)
- debian/control:
  + Exclude pandoc build dep on i386.
  + Add dh-exec build dep.
- debian/flac.install
  + Make executable and add '#!/usr/bin/dh-exec'.
  + Exclude installing manpages on i386.

 -- Rik Mills   Thu, 24 Nov 2022 18:56:12 +

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

Title:
  flac 1.4.2+ds-2 in lunar proposed does not build on i386 - missing
  pandoc build dep

Status in flac package in Ubuntu:
  Fix Released

Bug description:
  flac 1.4.2+ds-2 in lunar proposed does not build on i386 - missing
  pandoc build dep which is not built in Ubuntu for i386

  https://launchpad.net/ubuntu/+source/flac/1.4.2+ds-2/+build/24644410

  Change made in flac (1.4.1-1) "Replace docbook-to-man with pandoc as
  B-D"

  This prevents migration of flac (if/once tests succeed), and will
  block migration of packages that now build in proposed and depend on
  the bumped libs in flac 1.4 (libflac++10 and libflac12)

  https://people.canonical.com/~ubuntu-archive/proposed-
  migration/update_excuses.html#flac

  e.g.amongst several others so far

  https://people.canonical.com/~ubuntu-archive/proposed-
  migration/update_excuses.html#kwave

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/flac/+bug/1997533/+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 1997579] Re: [Ubuntu22.04] systemd-coredump package not installable via apt install when only OpenSSL 3.0 is available on the system (s390x)

[Frank Heimes]

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

** Changed in: ubuntu-z-systems
   Status: Incomplete => Invalid

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

Title:
  [Ubuntu22.04] systemd-coredump package not installable via apt install
  when only OpenSSL 3.0 is available on the system (s390x)

Status in Ubuntu on IBM z Systems:
  Invalid
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  ---Problem Description---
  Summary
  ===
  IBM z16 LPAR (s390x architecture)
  OS: Ubuntu 20.04.1 LTS (jammy jellyfish) on 5.15.0-53-generic,
  openssl3.0.2-0ubuntu1.7 s390x 
  systemd249.11-0ubuntu3.6 s390x 
  The problem is immediately reproducible.

  
  Details
  ===
  We fail to install the systemd-coredump package on a system where only 
OpenSSL 3.0.2 is available.

  
  Terminal output
  ===
  # apt info systemd-coredump
  Package: systemd-coredump
  Version: 249.11-0ubuntu3.6
  Priority: optional
  Section: universe/admin
  Source: systemd
  Origin: Ubuntu
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Debian systemd Maintainers 

  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 337 kB
  Provides: core-dump-handler
  Depends: libc6 (>= 2.34), libdw1 (>= 0.158), libelf1 (>= 0.144), systemd (= 
249.11-0ubuntu3.6), adduser
  Conflicts: core-dump-handler
  Replaces: core-dump-handler
  Homepage: https://www.freedesktop.org/wiki/Software/systemd
  Download-Size: 56.6 kB
  APT-Sources: http://ports.ubuntu.com/ubuntu-ports jammy-updates/universe 
s390x Packages
  Description: tools for storing and retrieving coredumps
   This package provides systemd tools for storing and retrieving coredumps:
* systemd-coredump
* coredumpctl

  N: There is 1 additional record. Please use the '-a' switch to see it

  
  # apt-get install systemd-coredump
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  You might want to run 'apt --fix-broken install' to correct these.
  The following packages have unmet dependencies:
   apport : Conflicts: core-dump-handler
   libep11 : Depends: libssl1.0.0 but it is not installable or
  libssl1.1 but it is not installable
   systemd-coredump : Depends: libdw1 (>= 0.158) but it is not going to be 
installed
  Conflicts: core-dump-handler
  E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or 
specify a solution).

   
  Contact Information = christian.r...@de.ibm.com 
   
  ---uname output---
  Linux system 5.15.0-53-generic #59-Ubuntu SMP Mon Oct 17 18:54:41 UTC 2022 
s390x s390x s390x GNU/Linux
   
  Machine Type = IBM Type:   3931  Model: 704 A01 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
  1.) Configure the apt repos as shown in the attached sources.list file and run
  apt-get update
  2.) Run: apt install systemd-coredump
  There is no package install available working with openssl version 3.0.N alone
  i.e. when openssl 1.0 or 1.1 are _NOT_ installed
   
  Userspace tool common name: coredumpctl 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace rpm: systemd-coredump

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for christian.r...@de.ibm.com:
  -Attach ltrace and strace of userspace application.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1997579/+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 1996619] Re: Setfont error due to deprecated PIO_FONTX ioctl

[Heather Lemon]

Okay, Thanks Dan B. & Dann F. I started the Jammy SRU this morning.

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

Title:
  Setfont error due to deprecated PIO_FONTX ioctl

Status in subiquity:
  Invalid
Status in kbd package in Ubuntu:
  Fix Released
Status in kbd source package in Jammy:
  In Progress

Bug description:
  There is an error message that get thrown in in syslog.
  There is a suggestion to fix by upgrading the KDB package to version 2.5.1+ 
or 
  to understand the root cause and troubleshoot as to why it's broken and 
resolve 
  it there.

  It is caused by this line in subiquity
  
https://github.com/canonical/subiquity/blob/46f671d14d57a5da6bc3d60b1da6715b43954f0d/bin/subiquity-service#L11

  It's due to PIO_FONTX ioctl removed from kernel since 5.12
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ff2047fb755d4415ec3c70ac799889371151796d

  In 2.4.5 of kbd which provide setfont in user space, they already
  switched over to use KDFONTOP only.

  ### REPRODUCER STEPS ###

  # install libvirt
  sudo apt install qemu qemu-kvm libvirt-clients libvirt-daemon-system virtinst 
bridge-utils

  sudo systemctl enable libvirtd
  sudo systemctl start libvirtd

  # check libvirtd process is running 
  virsh 
  virsh list 

  # get iso
  wget https://releases.ubuntu.com/22.04/ubuntu-22.04.1-live-server-amd64.iso

  # install vm 
  sudo virt-install --cdrom='./ubuntu-22.04.1-live-server-amd64.iso'  
--name=setfont-repo --vcpus=2 --memory=2048 --disk size=20 --serial pty 
--graphics none --boot=uefi --debug

  # you can either do the full install, 
  the error will be in the /var/log/installer.log file 

  # or on the first page of the installer press Tab-> go to Help, -> Shell 
  and cd /var/log/
  grep setfont* syslog

  # to show error message cd to 
  /snap/subiquity/3698

  #execute 
  setfont $SNAP/subiquity.psf
   
  # error
  root@ubuntu-server:/snap/subiquity/3698# setfont $SNAP/subiquity.psf
  setfont: ERROR kdfontop.c:266 put_font_piofontx: ioctl(PIO_FONTX): 512,8x16: 
failed: Inappropriate ioctl for device

  # grep 
  grep setfont* syslog 
  Nov 14 18:22:11 ubuntu-server console-setup.sh[1107]: setfont: ERROR 
kdfontop.c:266 put_font_piofontx: ioctl(PIO_FONTX): 512,8x16: failed: 
Inappropriate ioctl for device
  Nov 14 18:22:29 ubuntu-server subiquity.subiquity-service[1878]: setfont: 
ERROR kdfontop.c:266 put_font_piofontx: ioctl(PIO_FONTX): 512,8x16: failed: 
Inappropriate ioctl for device

To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/1996619/+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 1997579] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From christian.r...@de.ibm.com 2022-11-28 12:42 EDT---
Thanks for having a look Frank and Steve.
I am all right with closing.

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

Title:
  [Ubuntu22.04] systemd-coredump package not installable via apt install
  when only OpenSSL 3.0 is available on the system (s390x)

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  ---Problem Description---
  Summary
  ===
  IBM z16 LPAR (s390x architecture)
  OS: Ubuntu 20.04.1 LTS (jammy jellyfish) on 5.15.0-53-generic,
  openssl3.0.2-0ubuntu1.7 s390x 
  systemd249.11-0ubuntu3.6 s390x 
  The problem is immediately reproducible.

  
  Details
  ===
  We fail to install the systemd-coredump package on a system where only 
OpenSSL 3.0.2 is available.

  
  Terminal output
  ===
  # apt info systemd-coredump
  Package: systemd-coredump
  Version: 249.11-0ubuntu3.6
  Priority: optional
  Section: universe/admin
  Source: systemd
  Origin: Ubuntu
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Debian systemd Maintainers 

  Bugs: https://bugs.launchpad.net/ubuntu/+filebug
  Installed-Size: 337 kB
  Provides: core-dump-handler
  Depends: libc6 (>= 2.34), libdw1 (>= 0.158), libelf1 (>= 0.144), systemd (= 
249.11-0ubuntu3.6), adduser
  Conflicts: core-dump-handler
  Replaces: core-dump-handler
  Homepage: https://www.freedesktop.org/wiki/Software/systemd
  Download-Size: 56.6 kB
  APT-Sources: http://ports.ubuntu.com/ubuntu-ports jammy-updates/universe 
s390x Packages
  Description: tools for storing and retrieving coredumps
   This package provides systemd tools for storing and retrieving coredumps:
* systemd-coredump
* coredumpctl

  N: There is 1 additional record. Please use the '-a' switch to see it

  
  # apt-get install systemd-coredump
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  You might want to run 'apt --fix-broken install' to correct these.
  The following packages have unmet dependencies:
   apport : Conflicts: core-dump-handler
   libep11 : Depends: libssl1.0.0 but it is not installable or
  libssl1.1 but it is not installable
   systemd-coredump : Depends: libdw1 (>= 0.158) but it is not going to be 
installed
  Conflicts: core-dump-handler
  E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or 
specify a solution).

   
  Contact Information = christian.r...@de.ibm.com 
   
  ---uname output---
  Linux system 5.15.0-53-generic #59-Ubuntu SMP Mon Oct 17 18:54:41 UTC 2022 
s390x s390x s390x GNU/Linux
   
  Machine Type = IBM Type:   3931  Model: 704 A01 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
  1.) Configure the apt repos as shown in the attached sources.list file and run
  apt-get update
  2.) Run: apt install systemd-coredump
  There is no package install available working with openssl version 3.0.N alone
  i.e. when openssl 1.0 or 1.1 are _NOT_ installed
   
  Userspace tool common name: coredumpctl 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace rpm: systemd-coredump

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for christian.r...@de.ibm.com:
  -Attach ltrace and strace of userspace application.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1997579/+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 1998129] [NEW] Xorg crash

[Nathaniel Nebel]

Public bug reported:

Hangs prior to crashing for a few seconds, then shows strange colored
pixels all over the screen that change position when I move my mouse.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64
Uname: Linux 5.15.0-53-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov 28 11:42:50 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Tonga PRO [Radeon R9 285/380] 
[1002:6939] (rev f1) (prog-if 00 [VGA controller])
   Subsystem: PC Partner Limited / Sapphire Technology Radeon R9 380 Nitro 4G 
D5 [174b:e308]
InstallationDate: Installed on 2022-09-05 (83 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-53-generic 
root=UUID=9d4f1056-fc09-4d07-9e70-7ccb68bf92fd ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/30/2017
dmi.bios.release: 5.12
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P3.10
dmi.board.name: AB350M Pro4
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP3.10:bd08/30/2017:br5.12:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350MPro4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1
version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.5-0ubuntu0.1
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


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

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  Hangs prior to crashing for a few seconds, then shows strange colored
  pixels all over the screen that change position when I move my mouse.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64
  Uname: Linux 5.15.0-53-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 28 11:42:50 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Tonga PRO [Radeon R9 285/380] 
[1002:6939] (rev f1) (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Radeon R9 380 Nitro 4G 
D5 [174b:e308]
  InstallationDate: Installed on 2022-09-05 (83 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-53-generic 
root=UUID=9d4f1056-fc09-4d07-9e70-7ccb68bf92fd ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/30/2017
  dmi.bios.release: 5.12
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.10
  dmi.board.name: AB350M Pro4
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version:

[Touch-packages] [Bug 1996619] Re: Setfont error due to deprecated PIO_FONTX ioctl

[Heather Lemon]

** Changed in: kbd (Ubuntu Jammy)
 Assignee: (unassigned) => Heather Lemon (hypothetical-lemon)

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

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

Title:
  Setfont error due to deprecated PIO_FONTX ioctl

Status in subiquity:
  Invalid
Status in kbd package in Ubuntu:
  Fix Released
Status in kbd source package in Jammy:
  In Progress

Bug description:
  There is an error message that get thrown in in syslog.
  There is a suggestion to fix by upgrading the KDB package to version 2.5.1+ 
or 
  to understand the root cause and troubleshoot as to why it's broken and 
resolve 
  it there.

  It is caused by this line in subiquity
  
https://github.com/canonical/subiquity/blob/46f671d14d57a5da6bc3d60b1da6715b43954f0d/bin/subiquity-service#L11

  It's due to PIO_FONTX ioctl removed from kernel since 5.12
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ff2047fb755d4415ec3c70ac799889371151796d

  In 2.4.5 of kbd which provide setfont in user space, they already
  switched over to use KDFONTOP only.

  ### REPRODUCER STEPS ###

  # install libvirt
  sudo apt install qemu qemu-kvm libvirt-clients libvirt-daemon-system virtinst 
bridge-utils

  sudo systemctl enable libvirtd
  sudo systemctl start libvirtd

  # check libvirtd process is running 
  virsh 
  virsh list 

  # get iso
  wget https://releases.ubuntu.com/22.04/ubuntu-22.04.1-live-server-amd64.iso

  # install vm 
  sudo virt-install --cdrom='./ubuntu-22.04.1-live-server-amd64.iso'  
--name=setfont-repo --vcpus=2 --memory=2048 --disk size=20 --serial pty 
--graphics none --boot=uefi --debug

  # you can either do the full install, 
  the error will be in the /var/log/installer.log file 

  # or on the first page of the installer press Tab-> go to Help, -> Shell 
  and cd /var/log/
  grep setfont* syslog

  # to show error message cd to 
  /snap/subiquity/3698

  #execute 
  setfont $SNAP/subiquity.psf
   
  # error
  root@ubuntu-server:/snap/subiquity/3698# setfont $SNAP/subiquity.psf
  setfont: ERROR kdfontop.c:266 put_font_piofontx: ioctl(PIO_FONTX): 512,8x16: 
failed: Inappropriate ioctl for device

  # grep 
  grep setfont* syslog 
  Nov 14 18:22:11 ubuntu-server console-setup.sh[1107]: setfont: ERROR 
kdfontop.c:266 put_font_piofontx: ioctl(PIO_FONTX): 512,8x16: failed: 
Inappropriate ioctl for device
  Nov 14 18:22:29 ubuntu-server subiquity.subiquity-service[1878]: setfont: 
ERROR kdfontop.c:266 put_font_piofontx: ioctl(PIO_FONTX): 512,8x16: failed: 
Inappropriate ioctl for device

To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/1996619/+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 1996619] Re: Setfont error due to deprecated PIO_FONTX ioctl

[Dan Bungert]

I am marking this invalid for Subiquity as I believe no changes are
needed there.  When we rebuild for 22.04.2 this change should be picked
up, once that SRU to Jammy is done.

** Changed in: subiquity
   Status: New => Invalid

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

Title:
  Setfont error due to deprecated PIO_FONTX ioctl

Status in subiquity:
  Invalid
Status in kbd package in Ubuntu:
  Fix Released
Status in kbd source package in Jammy:
  In Progress

Bug description:
  There is an error message that get thrown in in syslog.
  There is a suggestion to fix by upgrading the KDB package to version 2.5.1+ 
or 
  to understand the root cause and troubleshoot as to why it's broken and 
resolve 
  it there.

  It is caused by this line in subiquity
  
https://github.com/canonical/subiquity/blob/46f671d14d57a5da6bc3d60b1da6715b43954f0d/bin/subiquity-service#L11

  It's due to PIO_FONTX ioctl removed from kernel since 5.12
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ff2047fb755d4415ec3c70ac799889371151796d

  In 2.4.5 of kbd which provide setfont in user space, they already
  switched over to use KDFONTOP only.

  ### REPRODUCER STEPS ###

  # install libvirt
  sudo apt install qemu qemu-kvm libvirt-clients libvirt-daemon-system virtinst 
bridge-utils

  sudo systemctl enable libvirtd
  sudo systemctl start libvirtd

  # check libvirtd process is running 
  virsh 
  virsh list 

  # get iso
  wget https://releases.ubuntu.com/22.04/ubuntu-22.04.1-live-server-amd64.iso

  # install vm 
  sudo virt-install --cdrom='./ubuntu-22.04.1-live-server-amd64.iso'  
--name=setfont-repo --vcpus=2 --memory=2048 --disk size=20 --serial pty 
--graphics none --boot=uefi --debug

  # you can either do the full install, 
  the error will be in the /var/log/installer.log file 

  # or on the first page of the installer press Tab-> go to Help, -> Shell 
  and cd /var/log/
  grep setfont* syslog

  # to show error message cd to 
  /snap/subiquity/3698

  #execute 
  setfont $SNAP/subiquity.psf
   
  # error
  root@ubuntu-server:/snap/subiquity/3698# setfont $SNAP/subiquity.psf
  setfont: ERROR kdfontop.c:266 put_font_piofontx: ioctl(PIO_FONTX): 512,8x16: 
failed: Inappropriate ioctl for device

  # grep 
  grep setfont* syslog 
  Nov 14 18:22:11 ubuntu-server console-setup.sh[1107]: setfont: ERROR 
kdfontop.c:266 put_font_piofontx: ioctl(PIO_FONTX): 512,8x16: failed: 
Inappropriate ioctl for device
  Nov 14 18:22:29 ubuntu-server subiquity.subiquity-service[1878]: setfont: 
ERROR kdfontop.c:266 put_font_piofontx: ioctl(PIO_FONTX): 512,8x16: failed: 
Inappropriate ioctl for device

To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/1996619/+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 1995260] Re: dnsmasq focal 2.80 NODATA instead of NXDOMAIN bug

[Miriam España Acebal]

I switched the lines from the command above for the local series
variable, and now the test passes:

autopkgtest [17:48:12]: test lxd: [---
II: Auto-init LXD...
qemu-system-x86_64: Slirp: external icmpv6 not supported yet
II: Creating Fan Bridge...
configuring fan underlay:10.0.0.0/16 overlay:250.0.0.0/8
II: Create LXD profile for Fan Bridge...
configuring LXD for underlay:10.0.0.0/16 overlay:250.0.0.0/8 (fan-250)
Profile fan-250 created
II: Test LXD...
master: detected primary route through ens3
master: DNS: systemd(10.0.2.3)
local lxd test: creating test container (Ubuntu:20.04) ...
Creating fanatic-test
Starting fanatic-test   
lxd test: Waiting for addresses on eth0 ...
lxd test: Waiting for addresses on eth0 ...
lxd test: Waiting for addresses on eth0 ...
lxd test: Waiting for addresses on eth0 ...
slave: detected primary route through eth0
slave: waiting for systemd resolver...
sd_bus_open_system: No such file or directory
slave: DNS: systemd(250.2.15.1)
test master: ping test (250.2.15.202) ...
test slave: ping test (250.2.15.1) ...
test master: ping test ... PASS
test master: short data test (250.2.15.1 -> 250.2.15.202) ...
test slave: ping test ... PASS
test slave: short data test (250.2.15.202 -> 250.2.15.1) ...
test master: short data ... PASS
test master: long data test (250.2.15.1 -> 250.2.15.202) ...
test slave: short data ... PASS
test slave: long data test (250.2.15.202 -> 250.2.15.1) ...
test slave: long data ... PASS
test master: long data ... PASS
local lxd test: destroying test container ...
local lxd test: test complete PASS (master=0 slave=0)
II: Undefining LXD profile for Fan Bridge...
de-configuring LXD underlay:10.0.0.0/16 overlay:250.0.0.0/8
Profile fan-250 deleted
fan-250: flags=4163  mtu 1450
inet 250.2.15.1  netmask 255.0.0.0  broadcast 0.0.0.0
inet6 fe80::e493:42ff:fed3:34ec  prefixlen 64  scopeid 0x20
ether e6:93:42:d3:34:ec  txqueuelen 1000  (Ethernet)
RX packets 5684  bytes 166505628 (166.5 MB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 5922  bytes 167845841 (167.8 MB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

II: Removing Fan Bridge...
de-configuring fan underlay:10.0.0.0/16 overlay:250.0.0.0/8
PASS
autopkgtest [17:49:19]: test lxd: ---]
autopkgtest [17:49:20]: test lxd:  - - - - - - - - - - results - - - - - - - - 
- -
lxd  PASS
autopkgtest [17:49:21]:  summary
command1 PASS
lxd  PASS

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

Title:
  dnsmasq focal 2.80 NODATA instead of NXDOMAIN bug

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in dnsmasq source package in Focal:
  Fix Committed

Bug description:
  [SRU]

  [ Impact ]

  Sometimes dnsmasq is incorrectly returning NODATA instead of NXDOMAIN.
  This can lead to erroneous actions by clients who need to determine
  whether a domain name exists or not.

  [ Test Plan ]

  In a focal VM, install dnsmasq (apt install dnsmasq) if it wasn't
  installed yet.

  #0 Disabling systemd-resolved service and enabling resolution through
  dnsmasq.

  # systemctl disable --now systemd-resolved.service
  # rm -f /etc/resolv.conf
  # cat > /etc/resolv.conf << __EOF__
  nameserver 8.8.8.8
  __EOF__
  # systemctl start dnsmasq.service

  #1 Bad case

  # for i in srv txt  a  a txt srv; do host -t $i test.foo. 127.0.0.1 | 
tail -n 1; done
  Host test.foo. not found: 3(NXDOMAIN)
  Host test.foo. not found: 3(NXDOMAIN)
  Host test.foo. not found: 3(NXDOMAIN)
  test.foo has no A record
  Host test.foo. not found: 3(NXDOMAIN)
  test.foo has no A record
  test.foo has no TXT record
  test.foo has no SRV record

  #2 Good case

  #2.1 Installing new package

  # ls -1 *.deb
  dnsmasq-utils_2.80-1.1ubuntu1.6_amd64.deb
  dnsmasq-base_2.80-1.1ubuntu1.6_amd64.deb
  dnsmasq_2.80-1.1ubuntu1.6_all.deb

  # dpkg -i *.deb
  (Reading database ... 32073 files and directories currently installed.)
  Preparing to unpack dnsmasq-base_2.80-1.1ubuntu1.6_amd64.deb ...
  Unpacking dnsmasq-base (2.80-1.1ubuntu1.6) over (2.80-1.1ubuntu1.5) ...
  Selecting previously unselected package dnsmasq-utils.
  Preparing to unpack dnsmasq-utils_2.80-1.1ubuntu1.6_amd64.deb ...
  Unpacking dnsmasq-utils (2.80-1.1ubuntu1.6) ...
  Preparing to unpack dnsmasq_2.80-1.1ubuntu1.6_all.deb ...
  Unpacking dnsmasq (2.80-1.1ubuntu1.6) over (2.80-1.1ubuntu1.5) ...
  Setting up dnsmasq-base (2.80-1.1ubuntu1.6) ...
  Setting up dnsmasq-utils (2.80-1.1ubuntu1.6) ...
  Setting up dnsmasq (2.80-1.1ubuntu1.6) ...
  Processing triggers for dbus (1.12.16-2ubuntu2.3) ...
  Processing triggers for man-db (2.9.1-1) ...
  Processing triggers for systemd (245.4-4ubuntu3.18) ...

  # dpkg -l | grep dnsmasq
  ii  dnsmasq  

[Touch-packages] [Bug 1403758] Re: Unity8 shows black screen with Qt 5.4.0

[Michał Sawicz]

** Changed in: unity8 (Ubuntu)
 Assignee: Albert Astals Cid (aacid) => (unassigned)

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

Title:
  Unity8 shows black screen with Qt 5.4.0

Status in binutils:
  Fix Released
Status in binutils package in Ubuntu:
  Fix Released
Status in gcc-defaults package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in ubuntu-ui-toolkit package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  With bug #1403511 taken care of in Qt, apps do not anymore crash with
  Qt 5.4 and device does not anymore go into reboot loop. However,
  nothing is visible on the screen.

  It seems unity8, unity8-dash etc are all running. unity8.log attached

  Relevant upstream links referring GCC5 as the reason to require -fPIC:
  
http://code.qt.io/cgit/qt/qtbase.git/commit/?id=36d6eb721e7d5997ade75e289d4088dc48678d0d
  
http://code.qt.io/cgit/qt/qtbase.git/commit/?id=3eca75de67b3fd2c890715b30c7899cebc096fe9

To manage notifications about this bug go to:
https://bugs.launchpad.net/binutils/+bug/1403758/+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 1996067] Re: [SRU] Enable support for Antelope Cloud Archive

[Corey Bryant]

I've uploaded this change to the jammy unapproved queue. For Lunar,
software-properties FTBFS due to python-apt 2.3.0ubuntu3 being broken.
Therefore, I've only pushed this change to the master branch. I don't
know that we really need to add this change to the current development
release seeing that it is never applicable to the current dev release,
however, we've historically done it this way.

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

Title:
   [SRU] Enable support for Antelope Cloud Archive

Status in software-properties package in Ubuntu:
  Fix Committed
Status in software-properties source package in Jammy:
  Triaged

Bug description:
  Please add support for:

 cloud-archive:antelope
 cloud-archive:antelope-proposed

  This will also need to be SRU'd back to jammy.

  [Impact]
  End users have to manually enable the antelope cloud archive pockets.

  [Test case]
  sudo add-apt-repository cloud-archive:antelope
  sudo add-apt-repository cloud-archive:antelope-proposed

  [Regression potential]
  Limited - just a data item addition

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1996067/+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 1996067] Re: [SRU] Enable support for Antelope Cloud Archive

[Corey Bryant]

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

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

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

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

Title:
   [SRU] Enable support for Antelope Cloud Archive

Status in software-properties package in Ubuntu:
  Fix Committed
Status in software-properties source package in Jammy:
  Triaged

Bug description:
  Please add support for:

 cloud-archive:antelope
 cloud-archive:antelope-proposed

  This will also need to be SRU'd back to jammy.

  [Impact]
  End users have to manually enable the antelope cloud archive pockets.

  [Test case]
  sudo add-apt-repository cloud-archive:antelope
  sudo add-apt-repository cloud-archive:antelope-proposed

  [Regression potential]
  Limited - just a data item addition

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1996067/+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 1995260] Re: dnsmasq focal 2.80 NODATA instead of NXDOMAIN bug

[Miriam España Acebal]

That's weird, because it seems that systemd-resolve is not present in
the lxd image:

lxd test: Waiting for addresses on eth0 ...
slave: detected primary route through eth0
/bin/sh: 29: systemd-resolve: not found
slave: waiting for systemd resolver...
/bin/sh: 29: systemd-resolve: not found

and the error is happening also with previous dnsmasq version:

Setting up dnsmasq-base (2.80-1.1ubuntu1.5) ...
ERROR: ld.so: object 'libeatmydata.so' from LD_PRELOAD cannot be preloaded 
(cannot open shared object file): ignored.
Setting up ubuntu-fan (0.12.13ubuntu0.1) ...
[...]
FAIL: Error on LXD test

I put +xv to the fanatic script of the ubuntu-fan package to see how the
image was created, and I got this:

+ storage_opt=--storage default
+ echo local lxd test: creating test container (Ubuntu:lts) ...
+ lxc launch ubuntu:lts fanatic-test --storage default -p fan-250
Creating fanatic-test
Starting fanatic-test 

and creating it manually :

❯ lxc launch ubuntu:lts fanatic-test-lts

Creating fanatic-test-lts
Starting fanatic-test-lts 
❯ lxc shell fanatic-test-lts
root@fanatic-test-lts:~# 
root@fanatic-test-lts:~# 
root@fanatic-test-lts:~# 
root@fanatic-test-lts:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 22.04.1 LTS
Release:22.04
Codename:   jammy

It's jammy, not focal. And systemd-resolve is not present on Jammy:


root@fanatic-test-lts:~# systemd-
systemd-analyze systemd-escape  systemd-run
systemd-ask-passwordsystemd-hwdb
systemd-socket-activate
systemd-cat systemd-id128   
systemd-stdio-bridge
systemd-cglssystemd-inhibit systemd-sysext
systemd-cgtop   systemd-machine-id-setupsystemd-sysusers
systemd-cryptenroll systemd-mount   systemd-tmpfiles
systemd-delta   systemd-notify  
systemd-tty-ask-password-agent
systemd-detect-virt systemd-pathsystemd-umount
root@fanatic-test-lts:~# systemd-resolve
systemd-resolve: command not found
root@fanatic-test-lts:~# 

the Ubunutu series is harcoded in the fanatic script at line 1015

#local series=$( lsb_release -sr )
local series='lts'

so it should be modified according to the series to which the package
under test belongs (in this case, focal), but for Jammy and beyond the
use of systemd-resolve in dns_lookup_forwarder() function at line 708
should be changed too.

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

Title:
  dnsmasq focal 2.80 NODATA instead of NXDOMAIN bug

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in dnsmasq source package in Focal:
  Fix Committed

Bug description:
  [SRU]

  [ Impact ]

  Sometimes dnsmasq is incorrectly returning NODATA instead of NXDOMAIN.
  This can lead to erroneous actions by clients who need to determine
  whether a domain name exists or not.

  [ Test Plan ]

  In a focal VM, install dnsmasq (apt install dnsmasq) if it wasn't
  installed yet.

  #0 Disabling systemd-resolved service and enabling resolution through
  dnsmasq.

  # systemctl disable --now systemd-resolved.service
  # rm -f /etc/resolv.conf
  # cat > /etc/resolv.conf << __EOF__
  nameserver 8.8.8.8
  __EOF__
  # systemctl start dnsmasq.service

  #1 Bad case

  # for i in srv txt  a  a txt srv; do host -t $i test.foo. 127.0.0.1 | 
tail -n 1; done
  Host test.foo. not found: 3(NXDOMAIN)
  Host test.foo. not found: 3(NXDOMAIN)
  Host test.foo. not found: 3(NXDOMAIN)
  test.foo has no A record
  Host test.foo. not found: 3(NXDOMAIN)
  test.foo has no A record
  test.foo has no TXT record
  test.foo has no SRV record

  #2 Good case

  #2.1 Installing new package

  # ls -1 *.deb
  dnsmasq-utils_2.80-1.1ubuntu1.6_amd64.deb
  dnsmasq-base_2.80-1.1ubuntu1.6_amd64.deb
  dnsmasq_2.80-1.1ubuntu1.6_all.deb

  # dpkg -i *.deb
  (Reading database ... 32073 files and directories currently installed.)
  Preparing to unpack dnsmasq-base_2.80-1.1ubuntu1.6_amd64.deb ...
  Unpacking dnsmasq-base (2.80-1.1ubuntu1.6) over (2.80-1.1ubuntu1.5) ...
  Selecting previously unselected package dnsmasq-utils.
  Preparing to unpack dnsmasq-utils_2.80-1.1ubuntu1.6_amd64.deb ...
  Unpacking dnsmasq-utils (2.80-1.1ubuntu1.6) ...
  Preparing to unpack dnsmasq_2.80-1.1ubuntu1.6_all.deb ...
  Unpacking dnsmasq (2.80-1.1ubuntu1.6) over (2.80-1.1ubuntu1.5) ...
  Setting up dnsmasq-base (2.80-1.1ubuntu1.6) ...
  Setting up dnsmasq-utils (2.80-1.1ubuntu1.6) ...
  Setting up dnsmasq (2.80-1.1ubuntu1.6) ...
  Processing triggers for dbus (1.12.16-2ubuntu2.3) ...
  Processing triggers for man-db (2.9.1-1) ...
  Processing triggers for systemd (245.4-4ubuntu3.18) ...

  # dpkg -l | grep dnsmasq
  ii  dnsmasq   

[Touch-packages] [Bug 1998103] Re: Intel 8087:07dc Bluetooth highly unreliable

[Rijnhard Hessel]

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

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

Title:
  Intel 8087:07dc Bluetooth highly unreliable

Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've been experiencing all sorts of strange behaviour since upgrading
  to linux mint 21.

  * adapter failing to power on after suspend/resume
  * random errors littering dmesg
  * now it went ballistic and caused my UI to freeze, not from anything I could 
identify that I did.

  inxi -EbA

  System:
    Host: HESSEL-MSI-MINT Kernel: 5.15.0-53-generic x86_64 bits: 64
  Desktop: Cinnamon 5.4.12 Distro: Linux Mint 21 Vanessa
  Machine:
    Type: Desktop System: Micro-Star product: GE70 2PC v: REV:1.0
  serial: 
    Mobo: Micro-Star model: MS-1759 v: REV:0.B serial: 
  UEFI: American Megatrends v: E1759IMS.62D date: 04/13/2015
  CPU:
    Info: quad core Intel Core i7-4710HQ [MT MCP] speed (MHz): avg: 1292
  min/max: 800/3500
  Audio:
    Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio
  driver: snd_hda_intel
    Device-2: Intel 8 Series/C220 Series High Definition Audio
  driver: snd_hda_intel
    Sound Server-1: ALSA v: k5.15.0-53-generic running: yes
    Sound Server-2: PulseAudio v: 15.99.1 running: yes
  Bluetooth:
    Device-1: Intel Bluetooth wireless interface type: USB driver: btusb
    Report: hciconfig ID: hci0 rfk-id: 0 state: down
  bt-service: enabled,running rfk-block: hardware: no software: yes
  address: 30:3A:64:EA:9C:EA

  attached kernel logs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1998103/+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 1982523] Re: error in commented-out NAME_REGEX

[Benjamin Drung]

Fixed in adduser 3.129ubuntu1 in Ubuntu 23.04 (lunar).

** Changed in: adduser (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  error in commented-out NAME_REGEX

Status in adduser package in Ubuntu:
  Fix Released
Status in adduser package in Debian:
  Unknown

Bug description:
  The default /etc/adduser.conf contains the line:

  #NAME_REGEX="^[a-z][-.a-z0-9_]*\$"

  Commenting this out in preparation of updating it does not work as
  expected:

  pra@PABELN-X1E:~$ grep NAME_REGEX /etc/adduser.conf; sudo adduser testuser
  NAME_REGEX="^[a-z][-a-z0-9_]*\$"
  adduser: Please enter a username matching the regular expression 
configured
  via the NAME_REGEX[_SYSTEM] configuration variable.  Use the 
`--force-badname'
  option to relax this check or reconfigure NAME_REGEX.
  pra@PABELN-X1E:~$

  This is due to the overeager escaping of the dollar sign, which has
  the undesired effect of requring that usernames end in `$`:

  pra@PABELN-X1E:~$ sudo adduser testuser$
  Adding user `testuser$' ...
  Adding new group `testuser$' (1002) ...
  Adding new user `testuser$' (1002) with group `testuser$' ...
  Creating home directory `/home/testuser$' ...
  Copying files from `/etc/skel' ...
  New password:

  Removing the backslash escaping the terminal `$` corrects the issue:

  pra@PABELN-X1E:~$ grep NAME_REGEX /etc/adduser.conf; sudo adduser testuser
  NAME_REGEX="^[a-z][-a-z0-9_]*$"
  Adding user `testuser' ...
  Adding new group `testuser' (1002) ...
  Adding new user `testuser' (1002) with group `testuser' ...
  Creating home directory `/home/testuser' ...
  Copying files from `/etc/skel' ...
  New password:

  I reported this for the `adduser` package because it seemed the
  closest match.  The file /etc/adduser.conf is not owned by any
  package.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: adduser 3.118ubuntu5
  Uname: Linux 5.10.102.1-microsoft-standard-WSL2 x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Thu Jul 21 19:56:02 2022
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: adduser
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/1982523/+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 1982523] Re: error in commented-out NAME_REGEX

[Benjamin Drung]

Thanks for reporting this bug. Reporting it against adduser was correct,
since adduser creates and manages /etc/adduser.conf

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

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

Title:
  error in commented-out NAME_REGEX

Status in adduser package in Ubuntu:
  Confirmed
Status in adduser package in Debian:
  Unknown

Bug description:
  The default /etc/adduser.conf contains the line:

  #NAME_REGEX="^[a-z][-.a-z0-9_]*\$"

  Commenting this out in preparation of updating it does not work as
  expected:

  pra@PABELN-X1E:~$ grep NAME_REGEX /etc/adduser.conf; sudo adduser testuser
  NAME_REGEX="^[a-z][-a-z0-9_]*\$"
  adduser: Please enter a username matching the regular expression 
configured
  via the NAME_REGEX[_SYSTEM] configuration variable.  Use the 
`--force-badname'
  option to relax this check or reconfigure NAME_REGEX.
  pra@PABELN-X1E:~$

  This is due to the overeager escaping of the dollar sign, which has
  the undesired effect of requring that usernames end in `$`:

  pra@PABELN-X1E:~$ sudo adduser testuser$
  Adding user `testuser$' ...
  Adding new group `testuser$' (1002) ...
  Adding new user `testuser$' (1002) with group `testuser$' ...
  Creating home directory `/home/testuser$' ...
  Copying files from `/etc/skel' ...
  New password:

  Removing the backslash escaping the terminal `$` corrects the issue:

  pra@PABELN-X1E:~$ grep NAME_REGEX /etc/adduser.conf; sudo adduser testuser
  NAME_REGEX="^[a-z][-a-z0-9_]*$"
  Adding user `testuser' ...
  Adding new group `testuser' (1002) ...
  Adding new user `testuser' (1002) with group `testuser' ...
  Creating home directory `/home/testuser' ...
  Copying files from `/etc/skel' ...
  New password:

  I reported this for the `adduser` package because it seemed the
  closest match.  The file /etc/adduser.conf is not owned by any
  package.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: adduser 3.118ubuntu5
  Uname: Linux 5.10.102.1-microsoft-standard-WSL2 x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Thu Jul 21 19:56:02 2022
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: adduser
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/1982523/+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 1982523] Re: error in commented-out NAME_REGEX

[Benjamin Drung]

Fixed in Debian release 3.119:
https://salsa.debian.org/debian/adduser/-/commit/3982734b7cea35182b15b23945816ce42c001619

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

** Also affects: adduser (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=630750
   Importance: Unknown
   Status: Unknown

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

Title:
  error in commented-out NAME_REGEX

Status in adduser package in Ubuntu:
  Confirmed
Status in adduser package in Debian:
  Unknown

Bug description:
  The default /etc/adduser.conf contains the line:

  #NAME_REGEX="^[a-z][-.a-z0-9_]*\$"

  Commenting this out in preparation of updating it does not work as
  expected:

  pra@PABELN-X1E:~$ grep NAME_REGEX /etc/adduser.conf; sudo adduser testuser
  NAME_REGEX="^[a-z][-a-z0-9_]*\$"
  adduser: Please enter a username matching the regular expression 
configured
  via the NAME_REGEX[_SYSTEM] configuration variable.  Use the 
`--force-badname'
  option to relax this check or reconfigure NAME_REGEX.
  pra@PABELN-X1E:~$

  This is due to the overeager escaping of the dollar sign, which has
  the undesired effect of requring that usernames end in `$`:

  pra@PABELN-X1E:~$ sudo adduser testuser$
  Adding user `testuser$' ...
  Adding new group `testuser$' (1002) ...
  Adding new user `testuser$' (1002) with group `testuser$' ...
  Creating home directory `/home/testuser$' ...
  Copying files from `/etc/skel' ...
  New password:

  Removing the backslash escaping the terminal `$` corrects the issue:

  pra@PABELN-X1E:~$ grep NAME_REGEX /etc/adduser.conf; sudo adduser testuser
  NAME_REGEX="^[a-z][-a-z0-9_]*$"
  Adding user `testuser' ...
  Adding new group `testuser' (1002) ...
  Adding new user `testuser' (1002) with group `testuser' ...
  Creating home directory `/home/testuser' ...
  Copying files from `/etc/skel' ...
  New password:

  I reported this for the `adduser` package because it seemed the
  closest match.  The file /etc/adduser.conf is not owned by any
  package.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: adduser 3.118ubuntu5
  Uname: Linux 5.10.102.1-microsoft-standard-WSL2 x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Thu Jul 21 19:56:02 2022
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: adduser
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/1982523/+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 1997989] Re: Merge new Debian release

[Heinrich Schuchardt]

util-linux - 2.38.1-3ubuntu1 is available in ppa:xypron/merge-from-
debian.

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

Title:
  Merge new Debian release

Status in util-linux package in Ubuntu:
  New

Bug description:
  Debian has provided util-linux 2.38.1-3.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1997989/+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 1997989] Re: Merge new Debian release

[Heinrich Schuchardt]

** Patch added: "util-linux_2.38.1-3..util-linux_2.38.1-3ubuntu1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1997989/+attachment/5632983/+files/util-linux_2.38.1-3..util-linux_2.38.1-3ubuntu1.debdiff

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

Title:
  Merge new Debian release

Status in util-linux package in Ubuntu:
  New

Bug description:
  Debian has provided util-linux 2.38.1-3.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1997989/+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 1997989] Re: Merge new Debian release

[Heinrich Schuchardt]

** Patch added: "util-linux_2.38-4ubuntu1..2.38.1-3ubuntu1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1997989/+attachment/5632982/+files/util-linux_2.38-4ubuntu1..2.38.1-3ubuntu1.debdiff

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

Title:
  Merge new Debian release

Status in util-linux package in Ubuntu:
  New

Bug description:
  Debian has provided util-linux 2.38.1-3.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1997989/+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 1998103] Re: Intel 8087:07dc Bluetooth highly unreliable

[Rijnhard Hessel]

Unforntunately there is no kernel core dump for this error. just the hci
subsystem losing its mind, as attached in the logs.

Happy to see what else I can provide

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

Title:
  Intel 8087:07dc Bluetooth highly unreliable

Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've been experiencing all sorts of strange behaviour since upgrading
  to linux mint 21.

  * adapter failing to power on after suspend/resume
  * random errors littering dmesg
  * now it went ballistic and caused my UI to freeze, not from anything I could 
identify that I did.

  inxi -EbA

  System:
    Host: HESSEL-MSI-MINT Kernel: 5.15.0-53-generic x86_64 bits: 64
  Desktop: Cinnamon 5.4.12 Distro: Linux Mint 21 Vanessa
  Machine:
    Type: Desktop System: Micro-Star product: GE70 2PC v: REV:1.0
  serial: 
    Mobo: Micro-Star model: MS-1759 v: REV:0.B serial: 
  UEFI: American Megatrends v: E1759IMS.62D date: 04/13/2015
  CPU:
    Info: quad core Intel Core i7-4710HQ [MT MCP] speed (MHz): avg: 1292
  min/max: 800/3500
  Audio:
    Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio
  driver: snd_hda_intel
    Device-2: Intel 8 Series/C220 Series High Definition Audio
  driver: snd_hda_intel
    Sound Server-1: ALSA v: k5.15.0-53-generic running: yes
    Sound Server-2: PulseAudio v: 15.99.1 running: yes
  Bluetooth:
    Device-1: Intel Bluetooth wireless interface type: USB driver: btusb
    Report: hciconfig ID: hci0 rfk-id: 0 state: down
  bt-service: enabled,running rfk-block: hardware: no software: yes
  address: 30:3A:64:EA:9C:EA

  attached kernel logs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1998103/+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 1998103] Missing required logs.

[Ubuntu Kernel Bot]

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

apport-collect 1998103

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

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

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

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

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

Title:
  Intel 8087:07dc Bluetooth highly unreliable

Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I've been experiencing all sorts of strange behaviour since upgrading
  to linux mint 21.

  * adapter failing to power on after suspend/resume
  * random errors littering dmesg
  * now it went ballistic and caused my UI to freeze, not from anything I could 
identify that I did.

  inxi -EbA

  System:
    Host: HESSEL-MSI-MINT Kernel: 5.15.0-53-generic x86_64 bits: 64
  Desktop: Cinnamon 5.4.12 Distro: Linux Mint 21 Vanessa
  Machine:
    Type: Desktop System: Micro-Star product: GE70 2PC v: REV:1.0
  serial: 
    Mobo: Micro-Star model: MS-1759 v: REV:0.B serial: 
  UEFI: American Megatrends v: E1759IMS.62D date: 04/13/2015
  CPU:
    Info: quad core Intel Core i7-4710HQ [MT MCP] speed (MHz): avg: 1292
  min/max: 800/3500
  Audio:
    Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio
  driver: snd_hda_intel
    Device-2: Intel 8 Series/C220 Series High Definition Audio
  driver: snd_hda_intel
    Sound Server-1: ALSA v: k5.15.0-53-generic running: yes
    Sound Server-2: PulseAudio v: 15.99.1 running: yes
  Bluetooth:
    Device-1: Intel Bluetooth wireless interface type: USB driver: btusb
    Report: hciconfig ID: hci0 rfk-id: 0 state: down
  bt-service: enabled,running rfk-block: hardware: no software: yes
  address: 30:3A:64:EA:9C:EA

  attached kernel logs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1998103/+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 1998111] [NEW] Quectel EM05-G not being unlocked

[Julian Andres Klode]

Public bug reported:

Despite support being in fcc-unlock.d

Bus 001 Device 003: ID 2c7c:030a Quectel Wireless Solutions Co., Ltd.
Quectel EM05-G

the modem remains locked and enabling it fails:

jak@jak-t14-g3:~:master$ mmcli -m any -e
error: couldn't enable the modem: 
'GDBus.Error:org.freedesktop.ModemManager1.Error.Core.Retry: Invalid transition'


Doing something like

# modprobe -r cdc_mbim
# modprobe cdc_mbim
# mbimcli --device-open-proxy --device="/dev/wwan0mbim0" 
--quectel-set-radio-state=on 
# systemctl RestartModemManager
# mmcli -m any -e

makes it work.

Peculiar it seems that the mbim-proxy process that ModemManager started
is hanging and causing the mbimcli command to time out (if I just run it
manually).


Further investigation warranted, tips welcome.

ProblemType: Bug
DistroRelease: Ubuntu 23.04
Package: modemmanager 1.20.0-1ubuntu1
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: GNOME
Date: Mon Nov 28 13:54:07 2022
InstallationDate: Installed on 2022-11-26 (1 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126)
SourcePackage: modemmanager
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  Quectel EM05-G not being unlocked

Status in modemmanager package in Ubuntu:
  New

Bug description:
  Despite support being in fcc-unlock.d

  Bus 001 Device 003: ID 2c7c:030a Quectel Wireless Solutions Co., Ltd.
  Quectel EM05-G

  the modem remains locked and enabling it fails:

  jak@jak-t14-g3:~:master$ mmcli -m any -e
  error: couldn't enable the modem: 
'GDBus.Error:org.freedesktop.ModemManager1.Error.Core.Retry: Invalid transition'

  
  Doing something like

  # modprobe -r cdc_mbim
  # modprobe cdc_mbim
  # mbimcli --device-open-proxy --device="/dev/wwan0mbim0" 
--quectel-set-radio-state=on 
  # systemctl RestartModemManager
  # mmcli -m any -e

  makes it work.

  Peculiar it seems that the mbim-proxy process that ModemManager
  started is hanging and causing the mbimcli command to time out (if I
  just run it manually).

  
  Further investigation warranted, tips welcome.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: modemmanager 1.20.0-1ubuntu1
  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: GNOME
  Date: Mon Nov 28 13:54:07 2022
  InstallationDate: Installed on 2022-11-26 (1 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Alpha amd64 (20221126)
  SourcePackage: modemmanager
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1998111/+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 1998103] Re: Intel 8087:07dc Bluetooth highly unreliable

[Rijnhard Hessel]

~seb128 I dont think thats fair, this is very likely kernel-related, and
the kernel is AFAIK an ubuntu kernel.

Unless I am misunderstanding something

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

Title:
  Intel 8087:07dc Bluetooth highly unreliable

Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  New

Bug description:
  I've been experiencing all sorts of strange behaviour since upgrading
  to linux mint 21.

  * adapter failing to power on after suspend/resume
  * random errors littering dmesg
  * now it went ballistic and caused my UI to freeze, not from anything I could 
identify that I did.

  inxi -EbA

  System:
    Host: HESSEL-MSI-MINT Kernel: 5.15.0-53-generic x86_64 bits: 64
  Desktop: Cinnamon 5.4.12 Distro: Linux Mint 21 Vanessa
  Machine:
    Type: Desktop System: Micro-Star product: GE70 2PC v: REV:1.0
  serial: 
    Mobo: Micro-Star model: MS-1759 v: REV:0.B serial: 
  UEFI: American Megatrends v: E1759IMS.62D date: 04/13/2015
  CPU:
    Info: quad core Intel Core i7-4710HQ [MT MCP] speed (MHz): avg: 1292
  min/max: 800/3500
  Audio:
    Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio
  driver: snd_hda_intel
    Device-2: Intel 8 Series/C220 Series High Definition Audio
  driver: snd_hda_intel
    Sound Server-1: ALSA v: k5.15.0-53-generic running: yes
    Sound Server-2: PulseAudio v: 15.99.1 running: yes
  Bluetooth:
    Device-1: Intel Bluetooth wireless interface type: USB driver: btusb
    Report: hciconfig ID: hci0 rfk-id: 0 state: down
  bt-service: enabled,running rfk-block: hardware: no software: yes
  address: 30:3A:64:EA:9C:EA

  attached kernel logs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1998103/+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 1998103] Re: Intel 8087:07dc Bluetooth highly unreliable

[Rijnhard Hessel]

** Description changed:

  I've been experiencing all sorts of strange behaviour since upgrading to
  linux mint 21.
  
  * adapter failing to power on after suspend/resume
  * random errors littering dmesg
- * now it went ballistic and caused my UI to freeze, not and not from anything 
I count identify that I did.
+ * now it went ballistic and caused my UI to freeze, not from anything I could 
identify that I did.
  
  inxi -EbA
  
  System:
-   Host: HESSEL-MSI-MINT Kernel: 5.15.0-53-generic x86_64 bits: 64
- Desktop: Cinnamon 5.4.12 Distro: Linux Mint 21 Vanessa
+   Host: HESSEL-MSI-MINT Kernel: 5.15.0-53-generic x86_64 bits: 64
+ Desktop: Cinnamon 5.4.12 Distro: Linux Mint 21 Vanessa
  Machine:
-   Type: Desktop System: Micro-Star product: GE70 2PC v: REV:1.0
- serial: 
-   Mobo: Micro-Star model: MS-1759 v: REV:0.B serial: 
- UEFI: American Megatrends v: E1759IMS.62D date: 04/13/2015
+   Type: Desktop System: Micro-Star product: GE70 2PC v: REV:1.0
+ serial: 
+   Mobo: Micro-Star model: MS-1759 v: REV:0.B serial: 
+ UEFI: American Megatrends v: E1759IMS.62D date: 04/13/2015
  CPU:
-   Info: quad core Intel Core i7-4710HQ [MT MCP] speed (MHz): avg: 1292
- min/max: 800/3500
+   Info: quad core Intel Core i7-4710HQ [MT MCP] speed (MHz): avg: 1292
+ min/max: 800/3500
  Audio:
-   Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio
- driver: snd_hda_intel
-   Device-2: Intel 8 Series/C220 Series High Definition Audio
- driver: snd_hda_intel
-   Sound Server-1: ALSA v: k5.15.0-53-generic running: yes
-   Sound Server-2: PulseAudio v: 15.99.1 running: yes
+   Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio
+ driver: snd_hda_intel
+   Device-2: Intel 8 Series/C220 Series High Definition Audio
+ driver: snd_hda_intel
+   Sound Server-1: ALSA v: k5.15.0-53-generic running: yes
+   Sound Server-2: PulseAudio v: 15.99.1 running: yes
  Bluetooth:
-   Device-1: Intel Bluetooth wireless interface type: USB driver: btusb
-   Report: hciconfig ID: hci0 rfk-id: 0 state: down
- bt-service: enabled,running rfk-block: hardware: no software: yes
- address: 30:3A:64:EA:9C:EA
+   Device-1: Intel Bluetooth wireless interface type: USB driver: btusb
+   Report: hciconfig ID: hci0 rfk-id: 0 state: down
+ bt-service: enabled,running rfk-block: hardware: no software: yes
+ address: 30:3A:64:EA:9C:EA
  
  attached kernel logs

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

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

Title:
  Intel 8087:07dc Bluetooth highly unreliable

Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  New

Bug description:
  I've been experiencing all sorts of strange behaviour since upgrading
  to linux mint 21.

  * adapter failing to power on after suspend/resume
  * random errors littering dmesg
  * now it went ballistic and caused my UI to freeze, not from anything I could 
identify that I did.

  inxi -EbA

  System:
    Host: HESSEL-MSI-MINT Kernel: 5.15.0-53-generic x86_64 bits: 64
  Desktop: Cinnamon 5.4.12 Distro: Linux Mint 21 Vanessa
  Machine:
    Type: Desktop System: Micro-Star product: GE70 2PC v: REV:1.0
  serial: 
    Mobo: Micro-Star model: MS-1759 v: REV:0.B serial: 
  UEFI: American Megatrends v: E1759IMS.62D date: 04/13/2015
  CPU:
    Info: quad core Intel Core i7-4710HQ [MT MCP] speed (MHz): avg: 1292
  min/max: 800/3500
  Audio:
    Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio
  driver: snd_hda_intel
    Device-2: Intel 8 Series/C220 Series High Definition Audio
  driver: snd_hda_intel
    Sound Server-1: ALSA v: k5.15.0-53-generic running: yes
    Sound Server-2: PulseAudio v: 15.99.1 running: yes
  Bluetooth:
    Device-1: Intel Bluetooth wireless interface type: USB driver: btusb
    Report: hciconfig ID: hci0 rfk-id: 0 state: down
  bt-service: enabled,running rfk-block: hardware: no software: yes
  address: 30:3A:64:EA:9C:EA

  attached kernel logs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1998103/+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 1997553] Re: network-manager fails to trigger dispatcher scripts with action dhcp4-change when dhcp lease is renewed

[Sebastien Bacher]

Thanks, the upstream bug reference is
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1147

** Bug watch added: 
gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues #1147
   https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1147

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

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

** Also affects: network-manager via
   https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1147
   Importance: Unknown
   Status: Unknown

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

Title:
  network-manager fails to trigger dispatcher scripts with action
  dhcp4-change when dhcp lease is renewed

Status in NetworkManager:
  Unknown
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  We rely on network-manager dispatcher scripts on our desktop and
  laptop computers. The dispatcher scripts are used to update DNS
  records with nsupdate when the dhcp lease is renewed.

  With jammy this is not working anymore. It seems that dispatcher
  scripts are run only when the interface comes up (with action 'up')
  and with the initial dhcp lease (with action 'dhcp4-change'), but when
  the lease is renewed, the dispatcher scripts are not run with any
  action. The only action the dispatcher scripts are run regularly with
  is 'connectivity-change', which seems to occur twice in a row every
  few hours.

  I have made a simple script to log how the dispatcher scripts are run:
  /etc/NetworkManager/dispatcher.d/99-test:
  #!/bin/bash
  PATH='/bin:/sbin:/usr/bin:/usr/sbin'

  echo $(date) 0: $0 IFACE: $1 ACTION: $2 >> /tmp/nm.log

  This script proves that action 'dhcp4-change' only occurs when I
  manually restart NetworkManager.service or unplug and replug the
  ethernet cable.


  network-manager version: 1.36.6-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1997553/+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 1998103] Re: Intel 8087:07dc Bluetooth highly unreliable

[Sebastien Bacher]

Thank you for your bug report but that's the Ubuntu tracker, report Mint
issues to them

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

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

Title:
  Intel 8087:07dc Bluetooth highly unreliable

Status in bluez package in Ubuntu:
  Invalid

Bug description:
  I've been experiencing all sorts of strange behaviour since upgrading
  to linux mint 21.

  * adapter failing to power on after suspend/resume
  * random errors littering dmesg
  * now it went ballistic and caused my UI to freeze, not and not from anything 
I count identify that I did.

  inxi -EbA

  System:
Host: HESSEL-MSI-MINT Kernel: 5.15.0-53-generic x86_64 bits: 64
  Desktop: Cinnamon 5.4.12 Distro: Linux Mint 21 Vanessa
  Machine:
Type: Desktop System: Micro-Star product: GE70 2PC v: REV:1.0
  serial: 
Mobo: Micro-Star model: MS-1759 v: REV:0.B serial: 
  UEFI: American Megatrends v: E1759IMS.62D date: 04/13/2015
  CPU:
Info: quad core Intel Core i7-4710HQ [MT MCP] speed (MHz): avg: 1292
  min/max: 800/3500
  Audio:
Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio
  driver: snd_hda_intel
Device-2: Intel 8 Series/C220 Series High Definition Audio
  driver: snd_hda_intel
Sound Server-1: ALSA v: k5.15.0-53-generic running: yes
Sound Server-2: PulseAudio v: 15.99.1 running: yes
  Bluetooth:
Device-1: Intel Bluetooth wireless interface type: USB driver: btusb
Report: hciconfig ID: hci0 rfk-id: 0 state: down
  bt-service: enabled,running rfk-block: hardware: no software: yes
  address: 30:3A:64:EA:9C:EA

  attached kernel logs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1998103/+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 1998103] Re: Intel 8087:07dc Bluetooth highly unreliable

[Rijnhard Hessel]

** Attachment added: "lsusb info"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1998103/+attachment/5632972/+files/intel_07dc.txt

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

Title:
  Intel 8087:07dc Bluetooth highly unreliable

Status in bluez package in Ubuntu:
  New

Bug description:
  I've been experiencing all sorts of strange behaviour since upgrading
  to linux mint 21.

  * adapter failing to power on after suspend/resume
  * random errors littering dmesg
  * now it went ballistic and caused my UI to freeze, not and not from anything 
I count identify that I did.

  inxi -EbA

  System:
Host: HESSEL-MSI-MINT Kernel: 5.15.0-53-generic x86_64 bits: 64
  Desktop: Cinnamon 5.4.12 Distro: Linux Mint 21 Vanessa
  Machine:
Type: Desktop System: Micro-Star product: GE70 2PC v: REV:1.0
  serial: 
Mobo: Micro-Star model: MS-1759 v: REV:0.B serial: 
  UEFI: American Megatrends v: E1759IMS.62D date: 04/13/2015
  CPU:
Info: quad core Intel Core i7-4710HQ [MT MCP] speed (MHz): avg: 1292
  min/max: 800/3500
  Audio:
Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio
  driver: snd_hda_intel
Device-2: Intel 8 Series/C220 Series High Definition Audio
  driver: snd_hda_intel
Sound Server-1: ALSA v: k5.15.0-53-generic running: yes
Sound Server-2: PulseAudio v: 15.99.1 running: yes
  Bluetooth:
Device-1: Intel Bluetooth wireless interface type: USB driver: btusb
Report: hciconfig ID: hci0 rfk-id: 0 state: down
  bt-service: enabled,running rfk-block: hardware: no software: yes
  address: 30:3A:64:EA:9C:EA

  attached kernel logs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1998103/+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 1998103] [NEW] Intel 8087:07dc Bluetooth highly unreliable

[Rijnhard Hessel]

Public bug reported:

I've been experiencing all sorts of strange behaviour since upgrading to
linux mint 21.

* adapter failing to power on after suspend/resume
* random errors littering dmesg
* now it went ballistic and caused my UI to freeze, not and not from anything I 
count identify that I did.

inxi -EbA

System:
  Host: HESSEL-MSI-MINT Kernel: 5.15.0-53-generic x86_64 bits: 64
Desktop: Cinnamon 5.4.12 Distro: Linux Mint 21 Vanessa
Machine:
  Type: Desktop System: Micro-Star product: GE70 2PC v: REV:1.0
serial: 
  Mobo: Micro-Star model: MS-1759 v: REV:0.B serial: 
UEFI: American Megatrends v: E1759IMS.62D date: 04/13/2015
CPU:
  Info: quad core Intel Core i7-4710HQ [MT MCP] speed (MHz): avg: 1292
min/max: 800/3500
Audio:
  Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio
driver: snd_hda_intel
  Device-2: Intel 8 Series/C220 Series High Definition Audio
driver: snd_hda_intel
  Sound Server-1: ALSA v: k5.15.0-53-generic running: yes
  Sound Server-2: PulseAudio v: 15.99.1 running: yes
Bluetooth:
  Device-1: Intel Bluetooth wireless interface type: USB driver: btusb
  Report: hciconfig ID: hci0 rfk-id: 0 state: down
bt-service: enabled,running rfk-block: hardware: no software: yes
address: 30:3A:64:EA:9C:EA

attached kernel logs

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

** Attachment added: "kernel logs"
   
https://bugs.launchpad.net/bugs/1998103/+attachment/5632971/+files/bluetooth.log

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

Title:
  Intel 8087:07dc Bluetooth highly unreliable

Status in bluez package in Ubuntu:
  New

Bug description:
  I've been experiencing all sorts of strange behaviour since upgrading
  to linux mint 21.

  * adapter failing to power on after suspend/resume
  * random errors littering dmesg
  * now it went ballistic and caused my UI to freeze, not and not from anything 
I count identify that I did.

  inxi -EbA

  System:
Host: HESSEL-MSI-MINT Kernel: 5.15.0-53-generic x86_64 bits: 64
  Desktop: Cinnamon 5.4.12 Distro: Linux Mint 21 Vanessa
  Machine:
Type: Desktop System: Micro-Star product: GE70 2PC v: REV:1.0
  serial: 
Mobo: Micro-Star model: MS-1759 v: REV:0.B serial: 
  UEFI: American Megatrends v: E1759IMS.62D date: 04/13/2015
  CPU:
Info: quad core Intel Core i7-4710HQ [MT MCP] speed (MHz): avg: 1292
  min/max: 800/3500
  Audio:
Device-1: Intel Xeon E3-1200 v3/4th Gen Core Processor HD Audio
  driver: snd_hda_intel
Device-2: Intel 8 Series/C220 Series High Definition Audio
  driver: snd_hda_intel
Sound Server-1: ALSA v: k5.15.0-53-generic running: yes
Sound Server-2: PulseAudio v: 15.99.1 running: yes
  Bluetooth:
Device-1: Intel Bluetooth wireless interface type: USB driver: btusb
Report: hciconfig ID: hci0 rfk-id: 0 state: down
  bt-service: enabled,running rfk-block: hardware: no software: yes
  address: 30:3A:64:EA:9C:EA

  attached kernel logs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1998103/+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 1977689] Re: Wrong error msg: "state file /var/lib/logrotate/status is world-readable" although it is not

[Alessandro Ratti]

My bad, it seems you have pushed  3.20.1-1ubuntu1 to Lunar and Kinetic after 
all.
When we can expect 3.20.1-1ubuntu1 released for Jammy?

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

Title:
  Wrong error msg: "state file /var/lib/logrotate/status is world-
  readable" although it is not

Status in logrotate package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 22.04
  logrotate 3.19.0-1ubuntu1.1

  Every hour, I receive this wrong message:

  Subject:  Cron >cd / && run-parts --report 
/etc/cron.hourly
  /etc/cron.hourly/logrotate:
  error: state file /var/lib/logrotate/status is world-readable and thus can be 
locked from other unprivileged users. Skipping lock acquisition...

  despite:

  # ls -al /var/lib/logrotate
  total 40
  drwxr-x---  2 root root  4096 Jun  5 17:17 .
  drwxr-xr-x 66 root root  4096 Jun  3 20:02 ..
  -rw-r-  1 root root 31974 Jun  5 17:17 status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1977689/+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 1977689] Re: Wrong error msg: "state file /var/lib/logrotate/status is world-readable" although it is not

[Alessandro Ratti]

Hello,

I think this commit [1] (3.17.0) introduced a security problem to which it was 
assigned CVE-2022-1348 [2].
They fixed it in [3] (3.20.0) and [4] (3.20.1).
Although I see you've pulled from debian/sid the patched version, I don't think 
you have ever pushed those patches to jammy/devel. 

May I request to release a package with the fix?

Thanks

[1]: 
https://github.com/logrotate/logrotate/commit/f46d0bdfc9c53515c13880c501f4d2e1e7dd8b25
[2]: https://github.com/advisories/GHSA-4c4j-w8hm-rjgv
[3]: 
https://github.com/logrotate/logrotate/commit/1f76a381e2caa0603ae3dbc51ed0f1aa0d6658b9
[4]: 
https://github.com/logrotate/logrotate/commit/addbd293242b0b78aa54f054e6c1d249451f137d

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-1348

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

Title:
  Wrong error msg: "state file /var/lib/logrotate/status is world-
  readable" although it is not

Status in logrotate package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 22.04
  logrotate 3.19.0-1ubuntu1.1

  Every hour, I receive this wrong message:

  Subject:  Cron >cd / && run-parts --report 
/etc/cron.hourly
  /etc/cron.hourly/logrotate:
  error: state file /var/lib/logrotate/status is world-readable and thus can be 
locked from other unprivileged users. Skipping lock acquisition...

  despite:

  # ls -al /var/lib/logrotate
  total 40
  drwxr-x---  2 root root  4096 Jun  5 17:17 .
  drwxr-xr-x 66 root root  4096 Jun  3 20:02 ..
  -rw-r-  1 root root 31974 Jun  5 17:17 status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1977689/+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 1959054] Re: debhelper restarts services marked --no-restart-on-upgrade

[Bug Watch Updater]

** Changed in: debconf (Debian)
   Status: New => Fix Released

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

Title:
  debhelper restarts services marked --no-restart-on-upgrade

Status in debconf package in Ubuntu:
  Fix Released
Status in debhelper package in Ubuntu:
  Fix Released
Status in docker.io package in Ubuntu:
  Fix Released
Status in libvirt package in Ubuntu:
  Fix Released
Status in debconf source package in Jammy:
  Fix Released
Status in debhelper source package in Jammy:
  Fix Released
Status in docker.io source package in Jammy:
  Fix Released
Status in libvirt source package in Jammy:
  Fix Released
Status in debconf package in Debian:
  Fix Released
Status in debhelper package in Debian:
  Fix Released

Bug description:
  Debian bug #994204 (https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=994204) describes a flaw in debhelper that
  results in the postinst being generated in such a fashion that
  services marked --no-stop-on-upgrade (or its deprecated alias --no-
  restart-on-upgrade), restart anyway.

  Please note: this is nothing to do with the --no-restart-after-upgrade
  flag (which is, somewhat confusingly IMO, unrelated).

  I've confirmed that the flaw appears to be present in the jammy
  version of debhelper (though not impish) and that packages generated
  with it appear to contain the flawed postinst (I first encountered
  this whilst working on the open-iscsi merge), though I haven't yet
  managed to test that the flaw exhibits itself on upgrade (though I'd
  say from the presence of the flaw in the postinst, that it's a
  reasonable inference that it will).

  In dbus (the merge of which I'm currently working on), Debian has
  worked around this but given I've now run into two affected packages
  (open-iscsi and dbus), only one of which has a work-around, I'd much
  rather we got debhelper fixed up and rebuilt affected packages?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1959054/+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 1995320] Re: [amdgpu] intermittent green static

[Daniel van Vugt]

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

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

Title:
  [amdgpu] intermittent green static

Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  New

Bug description:
  After upgrading from 22.04 to 22.10 I've been seeing some display
  glitches.

  - green static appears, usually when scrolling, regular sized green blocks, 
like giant pixels
  - firefox not refreshing when full screen video plays (separate windows, 
separate screens)

  I would guess I probably have the wrong package here, but there's no
  way for me to tell if it's mesa, the kernel, gnome-shell, or something
  else.

  Radeon 6700XT
  Dual displays
  Wayland

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: gnome-shell 43.0-1ubuntu2
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  Uname: Linux 5.19.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 31 21:46:03 2022
  DisplayManager: gdm3
  InstallationDate: Installed on 2019-06-18 (1231 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=tmux-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 43.0-1ubuntu4
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to kinetic on 2022-10-30 (1 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.10
  InstallationDate: Installed on 2019-06-18 (1232 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=tmux-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-23-generic 
root=/dev/mapper/infodata-root ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7
  RelatedPackageVersions:
   linux-restricted-modules-5.19.0-23-generic N/A
   linux-backports-modules-5.19.0-23-generic  N/A
   linux-firmware 20220923.gitf09bebf3-0ubuntu1
  RfKill:
   
  Tags:  kinetic wayland-session
  Uname: Linux 5.19.0-23-generic x86_64
  UpgradeStatus: Upgraded to kinetic on 2022-10-30 (1 days ago)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo wireshark
  _MarkForUpload: True
  dmi.bios.date: 11/27/2019
  dmi.bios.release: 5.14
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.90
  dmi.board.name: B450M Steel Legend
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.90:bd11/27/2019:br5.14:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB450MSteelLegend:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995320/+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 1997553] Re: network-manager fails to trigger dispatcher scripts with action dhcp4-change when dhcp lease is renewed

[Sami Niemimäki]

OK. I'll report this upstream.

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

Title:
  network-manager fails to trigger dispatcher scripts with action
  dhcp4-change when dhcp lease is renewed

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  We rely on network-manager dispatcher scripts on our desktop and
  laptop computers. The dispatcher scripts are used to update DNS
  records with nsupdate when the dhcp lease is renewed.

  With jammy this is not working anymore. It seems that dispatcher
  scripts are run only when the interface comes up (with action 'up')
  and with the initial dhcp lease (with action 'dhcp4-change'), but when
  the lease is renewed, the dispatcher scripts are not run with any
  action. The only action the dispatcher scripts are run regularly with
  is 'connectivity-change', which seems to occur twice in a row every
  few hours.

  I have made a simple script to log how the dispatcher scripts are run:
  /etc/NetworkManager/dispatcher.d/99-test:
  #!/bin/bash
  PATH='/bin:/sbin:/usr/bin:/usr/sbin'

  echo $(date) 0: $0 IFACE: $1 ACTION: $2 >> /tmp/nm.log

  This script proves that action 'dhcp4-change' only occurs when I
  manually restart NetworkManager.service or unplug and replug the
  ethernet cable.


  network-manager version: 1.36.6-0ubuntu2

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