[Touch-packages] [Bug 1953052] Re: In Jammy sound level reset after reboot

[corrado venturini]

On my desktop after a lot of new updates the sound level is NOT reset at
reboot.

I see pipewire and pulseaudio are both installed but i don't know if
they are active.

corrado@corrado-p5-jj-0203:~$ dpkg -l | grep pipewire
ii  gstreamer1.0-pipewire:amd640.3.45-1 
 amd64GStreamer 1.0 plugin for the PipeWire multimedia server
ii  libpipewire-0.3-0:amd640.3.45-1 
 amd64libraries for the PipeWire multimedia server
ii  libpipewire-0.3-common 0.3.45-1 
 all  libraries for the PipeWire multimedia server - common files
ii  libpipewire-0.3-modules:amd64  0.3.45-1 
 amd64libraries for the PipeWire multimedia server - modules
ii  pipewire:amd64 0.3.45-1 
 amd64audio and video processing engine multimedia server
ii  pipewire-bin   0.3.45-1 
 amd64PipeWire multimedia server - programs
ii  pipewire-media-session 0.4.1-2  
 amd64example session manager for PipeWire
corrado@corrado-p5-jj-0203:~$ apt policy pipewire pulseaudio
pipewire:
  Installed: 0.3.45-1
  Candidate: 0.3.45-1
  Version table:
 *** 0.3.45-1 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
100 /var/lib/dpkg/status
pulseaudio:
  Installed: 1:15.0+dfsg1-1ubuntu6
  Candidate: 1:15.0+dfsg1-1ubuntu6
  Version table:
 *** 1:15.0+dfsg1-1ubuntu6 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
100 /var/lib/dpkg/status
corrado@corrado-p5-jj-0203:~$ 

and from system monitor i see both are active. see attachment


** Attachment added: "Screenshot from 2022-02-18 08-46-29.png"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1953052/+attachment/5561750/+files/Screenshot%20from%202022-02-18%2008-46-29.png

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

Title:
  In Jammy sound level reset after reboot

Status in alsa-utils package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After reboot sound level is reset ignoring the level set in previous
  session.

  I manually set the sound output level 
  at next boot the sound is set at a different level (about 70%)

  Expected: the sound level is persistent across power off/on

  What happens : sound level is set at a different level (about 70%)

  Note: this problem does not occur on different partitions of same PC
  running Ubuntu 20.04 or 21.10

  corrado@corrado-p3-jj-1130:~$ apt policy gnome-control-center
  gnome-control-center:
Installed: 1:41.1-1ubuntu1
Candidate: 1:41.1-1ubuntu1
Version table:
   *** 1:41.1-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-p3-jj-1130:~$ inxi -Fx
  System:Host: corrado-p3-jj-1130 Kernel: 5.13.0-19-generic x86_64 bits: 64 
compiler: gcc v: 11.2.0
 Desktop: GNOME 40.5 Distro: Ubuntu 22.04 (Jammy Jellyfish)
  Machine:   Type: Laptop System: Dell product: Inspiron 3793 v: N/A serial: 

 Mobo: Dell model: 0C1PF2 v: A00 serial:  UEFI: 
Dell v: 1.5.0 date: 12/17/2019
  Battery:   ID-1: BAT0 charge: 13.9 Wh (42.1%) condition: 33.0/42.0 Wh (78.7%) 
volts: 11.3 min: 11.4
 model: SWD-ATL3.618 DELL WJPC403 status: Discharging
  CPU:   Info: Quad Core model: Intel Core i5-1035G1 bits: 64 type: MT MCP 
arch: Ice Lake rev: 5 cache:
 L2: 6 MiB
 flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 19046
 Speed: 968 MHz min/max: 400/1000 MHz Core speeds (MHz): 1: 968 2: 
710 3: 706 4: 714 5: 966 6: 712
 7: 724 8: 821
  Graphics:  Device-1: Intel Iris Plus Graphics G1 vendor: Dell driver: i915 v: 
kernel bus-ID: 00:02.0
 Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo 
bus-ID: 1-6:3
 Display: wayland server: X.Org 1.21.1.2 compositor: gnome-shell 
driver: loaded: i915
 note: n/a (using device driver) resolution: 1920x1080~60Hz
 OpenGL: renderer: Mesa Intel UHD Graphics (ICL GT1) v: 4.6 Mesa 
21.2.2 direct render: Yes
  Audio: Device-1: Intel Ice Lake-LP Smart Sound Audio vendor: Dell driver: 
snd_hda_intel v: kernel
 bus-ID: 00:1f.3
 Sound Server-1: ALSA v: k5.13.0-19-generic running: yes
 Sound Server-2: PulseAudio v: 15.0 running: yes
 Sound Server-3: PipeWire v: 0.3.40 running: yes
  Network:   Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell 
driver: r8169 v: kernel port: 3000
 bus-ID: 01:00.0
 IF: enp1s0 st

[Touch-packages] [Bug 1953052] Re: In Jammy sound level reset after reboot

[Igor V. Kovalenko]

Sebastien, if distribution is intended to provide pipewire function for
video only, there is no need to install audio parts. At very least
'with-pulse' 'with-jack' and other files directly or transitively
enabling 'with-audio' pipewire parts should not be installed so pipewire
media session daemon does not get hold of hardware controls.

Alternatively, if distribution is intended to provide pulseaudio
interface via pipewire, that should be properly switching pulseaudio
activation socket to pipewire-pulse, and/or disabling or uninstalling
pulseaudio daemon and maybe disabling pulseaudio autospawn in
client.conf

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

Title:
  In Jammy sound level reset after reboot

Status in alsa-utils package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After reboot sound level is reset ignoring the level set in previous
  session.

  I manually set the sound output level 
  at next boot the sound is set at a different level (about 70%)

  Expected: the sound level is persistent across power off/on

  What happens : sound level is set at a different level (about 70%)

  Note: this problem does not occur on different partitions of same PC
  running Ubuntu 20.04 or 21.10

  corrado@corrado-p3-jj-1130:~$ apt policy gnome-control-center
  gnome-control-center:
Installed: 1:41.1-1ubuntu1
Candidate: 1:41.1-1ubuntu1
Version table:
   *** 1:41.1-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-p3-jj-1130:~$ inxi -Fx
  System:Host: corrado-p3-jj-1130 Kernel: 5.13.0-19-generic x86_64 bits: 64 
compiler: gcc v: 11.2.0
 Desktop: GNOME 40.5 Distro: Ubuntu 22.04 (Jammy Jellyfish)
  Machine:   Type: Laptop System: Dell product: Inspiron 3793 v: N/A serial: 

 Mobo: Dell model: 0C1PF2 v: A00 serial:  UEFI: 
Dell v: 1.5.0 date: 12/17/2019
  Battery:   ID-1: BAT0 charge: 13.9 Wh (42.1%) condition: 33.0/42.0 Wh (78.7%) 
volts: 11.3 min: 11.4
 model: SWD-ATL3.618 DELL WJPC403 status: Discharging
  CPU:   Info: Quad Core model: Intel Core i5-1035G1 bits: 64 type: MT MCP 
arch: Ice Lake rev: 5 cache:
 L2: 6 MiB
 flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 19046
 Speed: 968 MHz min/max: 400/1000 MHz Core speeds (MHz): 1: 968 2: 
710 3: 706 4: 714 5: 966 6: 712
 7: 724 8: 821
  Graphics:  Device-1: Intel Iris Plus Graphics G1 vendor: Dell driver: i915 v: 
kernel bus-ID: 00:02.0
 Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo 
bus-ID: 1-6:3
 Display: wayland server: X.Org 1.21.1.2 compositor: gnome-shell 
driver: loaded: i915
 note: n/a (using device driver) resolution: 1920x1080~60Hz
 OpenGL: renderer: Mesa Intel UHD Graphics (ICL GT1) v: 4.6 Mesa 
21.2.2 direct render: Yes
  Audio: Device-1: Intel Ice Lake-LP Smart Sound Audio vendor: Dell driver: 
snd_hda_intel v: kernel
 bus-ID: 00:1f.3
 Sound Server-1: ALSA v: k5.13.0-19-generic running: yes
 Sound Server-2: PulseAudio v: 15.0 running: yes
 Sound Server-3: PipeWire v: 0.3.40 running: yes
  Network:   Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell 
driver: r8169 v: kernel port: 3000
 bus-ID: 01:00.0
 IF: enp1s0 state: down mac: 98:e7:43:59:19:19
 Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network 
Adapter vendor: Dell driver: ath10k_pci
 v: kernel bus-ID: 02:00.0
 IF: wlp2s0 state: up mac: d8:12:65:b8:21:b9
  Bluetooth: Device-1: Qualcomm Atheros type: USB driver: btusb v: 0.8 bus-ID: 
1-10:4
 Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: 
enabled,running rfk-block: hardware: no
 software: yes address: D8:12:65:B8:21:BA
  Drives:Local Storage: total: 942.7 GiB used: 11.77 GiB (1.2%)
 ID-1: /dev/nvme0n1 vendor: Toshiba model: KBG40ZNS512G NVMe KIOXIA 
512GB size: 476.94 GiB temp: 24.9 C
 ID-2: /dev/sda vendor: Crucial model: CT500MX500SSD1 size: 465.76 
GiB
  Partition: ID-1: / size: 46.95 GiB used: 11.73 GiB (25.0%) fs: ext4 dev: 
/dev/nvme0n1p3
 ID-2: /boot/efi size: 246 MiB used: 46.4 MiB (18.9%) fs: vfat dev: 
/dev/nvme0n1p1
  Swap:  Alert: No swap data was found.
  Sensors:   System Temperatures: cpu: 27.8 C mobo: N/A
 Fan Speeds (RPM): cpu: 0
  Info:  Processes: 263 Uptime: 31m Memory: 15.4 GiB used: 2.45 GiB (15.9%) 
Init: systemd runlevel: 5 Compilers:
 gcc: N/A Packages: 1785 Shell: Bash v: 5.1.12 inxi: 3.3.07
  corrado@corrado-p3-jj-1130:~$
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  Ca

[Touch-packages] [Bug 1953052] Re: In Jammy sound level reset after reboot

[Nobuto Murata]

I can confirm that after stopping pipewire temporarily by:
$ systemctl --user stop pipewire.socket pipewire.service
The volume level is properly recovered across plugging in and out a headset for 
example, which is good.

Both pulseaudio and pipewire are installed out of the box and running if
I'm not mistaken.

$ apt show pulseaudio |& grep Task:
Task: ubuntu-desktop-minimal, ubuntu-desktop, ubuntu-desktop-raspi, 
kubuntu-desktop, xubuntu-core, xubuntu-desktop, lubuntu-desktop, 
ubuntustudio-desktop-core, ubuntustudio-desktop, ubuntukylin-desktop, 
ubuntu-mate-core, ubuntu-mate-desktop, ubuntu-budgie-desktop, 
ubuntu-budgie-desktop-raspi

$ apt show pipewire |& grep Task:
Task: ubuntu-desktop-minimal, ubuntu-desktop, ubuntu-desktop-raspi, 
kubuntu-desktop, xubuntu-core, xubuntu-desktop, lubuntu-desktop, 
ubuntustudio-desktop-core, ubuntustudio-desktop, ubuntukylin-desktop, 
ubuntu-mate-core, ubuntu-mate-desktop, ubuntu-budgie-desktop, 
ubuntu-budgie-desktop-raspi

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

Title:
  In Jammy sound level reset after reboot

Status in alsa-utils package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After reboot sound level is reset ignoring the level set in previous
  session.

  I manually set the sound output level 
  at next boot the sound is set at a different level (about 70%)

  Expected: the sound level is persistent across power off/on

  What happens : sound level is set at a different level (about 70%)

  Note: this problem does not occur on different partitions of same PC
  running Ubuntu 20.04 or 21.10

  corrado@corrado-p3-jj-1130:~$ apt policy gnome-control-center
  gnome-control-center:
Installed: 1:41.1-1ubuntu1
Candidate: 1:41.1-1ubuntu1
Version table:
   *** 1:41.1-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-p3-jj-1130:~$ inxi -Fx
  System:Host: corrado-p3-jj-1130 Kernel: 5.13.0-19-generic x86_64 bits: 64 
compiler: gcc v: 11.2.0
 Desktop: GNOME 40.5 Distro: Ubuntu 22.04 (Jammy Jellyfish)
  Machine:   Type: Laptop System: Dell product: Inspiron 3793 v: N/A serial: 

 Mobo: Dell model: 0C1PF2 v: A00 serial:  UEFI: 
Dell v: 1.5.0 date: 12/17/2019
  Battery:   ID-1: BAT0 charge: 13.9 Wh (42.1%) condition: 33.0/42.0 Wh (78.7%) 
volts: 11.3 min: 11.4
 model: SWD-ATL3.618 DELL WJPC403 status: Discharging
  CPU:   Info: Quad Core model: Intel Core i5-1035G1 bits: 64 type: MT MCP 
arch: Ice Lake rev: 5 cache:
 L2: 6 MiB
 flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 19046
 Speed: 968 MHz min/max: 400/1000 MHz Core speeds (MHz): 1: 968 2: 
710 3: 706 4: 714 5: 966 6: 712
 7: 724 8: 821
  Graphics:  Device-1: Intel Iris Plus Graphics G1 vendor: Dell driver: i915 v: 
kernel bus-ID: 00:02.0
 Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo 
bus-ID: 1-6:3
 Display: wayland server: X.Org 1.21.1.2 compositor: gnome-shell 
driver: loaded: i915
 note: n/a (using device driver) resolution: 1920x1080~60Hz
 OpenGL: renderer: Mesa Intel UHD Graphics (ICL GT1) v: 4.6 Mesa 
21.2.2 direct render: Yes
  Audio: Device-1: Intel Ice Lake-LP Smart Sound Audio vendor: Dell driver: 
snd_hda_intel v: kernel
 bus-ID: 00:1f.3
 Sound Server-1: ALSA v: k5.13.0-19-generic running: yes
 Sound Server-2: PulseAudio v: 15.0 running: yes
 Sound Server-3: PipeWire v: 0.3.40 running: yes
  Network:   Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell 
driver: r8169 v: kernel port: 3000
 bus-ID: 01:00.0
 IF: enp1s0 state: down mac: 98:e7:43:59:19:19
 Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network 
Adapter vendor: Dell driver: ath10k_pci
 v: kernel bus-ID: 02:00.0
 IF: wlp2s0 state: up mac: d8:12:65:b8:21:b9
  Bluetooth: Device-1: Qualcomm Atheros type: USB driver: btusb v: 0.8 bus-ID: 
1-10:4
 Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: 
enabled,running rfk-block: hardware: no
 software: yes address: D8:12:65:B8:21:BA
  Drives:Local Storage: total: 942.7 GiB used: 11.77 GiB (1.2%)
 ID-1: /dev/nvme0n1 vendor: Toshiba model: KBG40ZNS512G NVMe KIOXIA 
512GB size: 476.94 GiB temp: 24.9 C
 ID-2: /dev/sda vendor: Crucial model: CT500MX500SSD1 size: 465.76 
GiB
  Partition: ID-1: / size: 46.95 GiB used: 11.73 GiB (25.0%) fs: ext4 dev: 
/dev/nvme0n1p3
 ID-2: /boot/efi size: 246 MiB used: 46.4 MiB (18.9%) fs: vfat dev: 
/dev/nvme0n1p1
  Swap:  Alert: No swap data was found.
  Sensors:   System Temperatures: cpu: 27.

[Touch-packages] [Bug 1958266] Re: package python3 3.9.7-4 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4

[shemgp]

The fix was the same:

cd /usr/share/python3/runtime.d
sudo mkdir temp
sudo mv * temp

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

Title:
  package python3 3.9.7-4 failed to install/upgrade: installed python3
  package post-installation script subprocess returned error exit status
  4

Status in python3-defaults package in Ubuntu:
  Invalid

Bug description:
  Upgraded to jammy and this crash showed up.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: python3 3.9.7-4
  ProcVersionSignature: Ubuntu 5.13.0-25.26-generic 5.13.19
  Uname: Linux 5.13.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Tue Jan 18 23:57:23 2022
  ErrorMessage: installed python3 package post-installation script subprocess 
returned error exit status 4
  InstallationDate: Installed on 2021-10-05 (105 days ago)
  InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Beta amd64 (20211004)
  Python3Details: /usr/bin/python3.9, Python 3.9.9, python3-minimal, 3.9.7-4
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.20.9ubuntu3
   apt  2.3.14
  SourcePackage: python3-defaults
  Title: package python3 3.9.7-4 failed to install/upgrade: installed python3 
package post-installation script subprocess returned error exit status 4
  UpgradeStatus: Upgraded to jammy on 2022-01-18 (0 days ago)

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

Re: [Touch-packages] [Bug 1958266] Re: package python3 3.9.7-4 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4

[shemgp]

Another office mate upgraded to jammy jellyfish development and this error
showed up:

Setting up python3 (3.9.7-4) ...
running python rtupdate hooks for python3.9...
E: py3compile:212: cannot create directory
/usr/share/sqlmap/thirdparty/gprof2dot/__pycache__: FileNotFoundError(2,
'No such
file or directory')
E: py3compile:212: cannot create directory
/usr/share/sqlmap/thirdparty/xdot/__pycache__: FileNotFoundError(2, 'No
such file
or directory')
[Errno 2] No such file or directory:
'/usr/share/sqlmap/thirdparty/gprof2dot/gprof2dot.py'
[Errno 2] No such file or directory:
'/usr/share/sqlmap/thirdparty/xdot/xdot.py'
error running python rtupdate hook sqlmap

On Thu, Jan 20, 2022 at 1:45 AM Stefano Rivera <1958...@bugs.launchpad.net>
wrote:

> Given the inconsistency, marking as invalid. Unless that was caused by
> something in the archive, there's not much we can do here.
>
> ** Changed in: python3-defaults (Ubuntu)
>Status: New => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1958266
>
> Title:
>   package python3 3.9.7-4 failed to install/upgrade: installed python3
>   package post-installation script subprocess returned error exit status
>   4
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1958266/+subscriptions
>
>

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

Title:
  package python3 3.9.7-4 failed to install/upgrade: installed python3
  package post-installation script subprocess returned error exit status
  4

Status in python3-defaults package in Ubuntu:
  Invalid

Bug description:
  Upgraded to jammy and this crash showed up.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: python3 3.9.7-4
  ProcVersionSignature: Ubuntu 5.13.0-25.26-generic 5.13.19
  Uname: Linux 5.13.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Tue Jan 18 23:57:23 2022
  ErrorMessage: installed python3 package post-installation script subprocess 
returned error exit status 4
  InstallationDate: Installed on 2021-10-05 (105 days ago)
  InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Beta amd64 (20211004)
  Python3Details: /usr/bin/python3.9, Python 3.9.9, python3-minimal, 3.9.7-4
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.20.9ubuntu3
   apt  2.3.14
  SourcePackage: python3-defaults
  Title: package python3 3.9.7-4 failed to install/upgrade: installed python3 
package post-installation script subprocess returned error exit status 4
  UpgradeStatus: Upgraded to jammy on 2022-01-18 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1958266/+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 1961196] Re: apparmor autotest failure on jammy with linux 5.15

[Alex Murray]

FYI I am working on merging apparmor-3.0.4 from debian unstable to jammy
at the moment which should resolve this.

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

Title:
  apparmor autotest failure on jammy with linux 5.15

Status in apparmor package in Ubuntu:
  New
Status in apparmor source package in Jammy:
  New

Bug description:
  [Impact]

  test-aa-notify is also checking if the output of `aa-notify --help`
  matches a specific text. However it looks like this output has changed
  in jammy so the autopkgtest is reporting errors like this:

  05:17:31 ERROR| [stderr] === test-aa-notify.py ===
  05:17:31 ERROR| [stderr] .ssF.
  05:17:31 ERROR| [stderr] 
==
  05:17:31 ERROR| [stderr] FAIL: test_help_contents (__main__.AANotifyTest)
  05:17:31 ERROR| [stderr] Test output of help text
  05:17:31 ERROR| [stderr] 
--
  05:17:31 ERROR| [stderr] Traceback (most recent call last):
  05:17:31 ERROR| [stderr]   File 
"/tmp/testlibmse00lib/source/jammy/apparmor-3.0.3/utils/test/test-aa-notify.py",
 line 178, in test_help_contents
  05:17:31 ERROR| [stderr] self.assertEqual(expected_output_is, output, 
result + output)
  05:17:31 ERROR| [stderr] AssertionError: 'usag[189 chars]ptional arguments:\n 
 -h, --helpsh[746 chars]de\n' != 'usag[189 chars]ptions:\n  -h, 
--helpshow this hel[735 chars]de\n'
  05:17:31 ERROR| [stderr]   usage: aa-notify [-h] [-p] [--display DISPLAY] [-f 
FILE] [-l] [-s NUM] [-v]
  05:17:31 ERROR| [stderr][-u USER] [-w NUM] [--debug]
  05:17:31 ERROR| [stderr]
  05:17:31 ERROR| [stderr]   Display AppArmor notifications or messages for 
DENIED entries.
  05:17:31 ERROR| [stderr]
  05:17:31 ERROR| [stderr] - optional arguments:
  05:17:31 ERROR| [stderr] + options:
  05:17:31 ERROR| [stderr] -h, --helpshow this help message and 
exit
  05:17:31 ERROR| [stderr] -p, --pollpoll AppArmor logs and 
display notifications
  05:17:31 ERROR| [stderr] --display DISPLAY set the DISPLAY 
environment variable (might be needed if
  05:17:31 ERROR| [stderr]   sudo resets $DISPLAY)
  05:17:31 ERROR| [stderr] -f FILE, --file FILE  search FILE for AppArmor 
messages
  05:17:31 ERROR| [stderr] -l, --since-last  display stats since last 
login
  05:17:31 ERROR| [stderr] -s NUM, --since-days NUM
  05:17:31 ERROR| [stderr]   show stats for last NUM 
days (can be used alone or with
  05:17:31 ERROR| [stderr]   -p)
  05:17:31 ERROR| [stderr] -v, --verbose show messages with stats
  05:17:31 ERROR| [stderr] -u USER, --user USER  user to drop privileges to 
when not using sudo
  05:17:31 ERROR| [stderr] -w NUM, --wait NUMwait NUM seconds before 
displaying notifications (with
  05:17:31 ERROR| [stderr]   -p)
  05:17:31 ERROR| [stderr] --debug   debug mode
  05:17:31 ERROR| [stderr]  : Got output "usage: aa-notify [-h] [-p] [--display 
DISPLAY] [-f FILE] [-l] [-s NUM] [-v]
  05:17:31 ERROR| [stderr]  [-u USER] [-w NUM] [--debug]

  [Test case]

  Simply run test-aa-notify.py from the autopkgtests.

  [Fix]

  Update the expected output returned by `aa-notify --help` in test-aa-
  notify.py.

  [Regression potential]

  This is just an autopkgtest, we may see regressions if the test is
  used with older version of apparmor-notify. With newer versions
  there's no risk of regressions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1961196/+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 1961344] [NEW] Sound works in LIVE cd but not in Installation

[Brandon Delgado]

Public bug reported:

Hello, I am using a Nextbook Flexx 10.1 I have attempted to use multiple
fixes described online to no avail. It seems that when using the live
mode off of the boot flash drive audio works fine. Alsamixer reports
bytcr-rt5640 as sound card. however once installed no audio. alsamixer
reports sof-bytcht rt5640 as card selected

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-30-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  delgadb2   1271 F pulseaudio
 /dev/snd/controlC0:  delgadb2   1271 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Feb 17 12:51:34 2022
InstallationDate: Installed on 2022-02-17 (0 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:rt5640 failed
Symptom_Card: Built-in Audio - sof-bytcht rt5640
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  delgadb2   1271 F pulseaudio
 /dev/snd/controlC0:  delgadb2   1271 F pulseaudio
Symptom_Type: No sound at all
Title: [SOF - sof-bytcht rt5640, playback] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/09/2015
dmi.bios.release: 18.18
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: NX1015.2.02.017
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: NXM1015BFP
dmi.board.vendor: YIFANG
dmi.board.version: 1.2
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 0.0
dmi.modalias: 
dmi:bvnINSYDECorp.:bvrNX1015.2.02.017:bd11/09/2015:br18.18:efr0.0:svnYIFANG:pnNXW101QC232T:pvrType1-TBDbyOEM:rvnYIFANG:rnNXM1015BFP:rvr1.2:cvnChassisManufacturer:ct10:cvrChassisVersion:skuType1-SKU0:
dmi.product.family: M1015BFP T10220300
dmi.product.name: NXW101QC232T
dmi.product.sku: Type1 - SKU0
dmi.product.version: Type1 - TBD by OEM
dmi.sys.vendor: YIFANG

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

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

Title:
  Sound works in LIVE cd but not in Installation

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hello, I am using a Nextbook Flexx 10.1 I have attempted to use
  multiple fixes described online to no avail. It seems that when using
  the live mode off of the boot flash drive audio works fine. Alsamixer
  reports bytcr-rt5640 as sound card. however once installed no audio.
  alsamixer reports sof-bytcht rt5640 as card selected

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  delgadb2   1271 F pulseaudio
   /dev/snd/controlC0:  delgadb2   1271 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 17 12:51:34 2022
  InstallationDate: Installed on 2022-02-17 (0 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:rt5640 failed
  Symptom_Card: Built-in Audio - sof-bytcht rt5640
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  delgadb2   1271 F pulseaudio
   /dev/snd/controlC0:  delgadb2   1271 F pulseaudio
  Symptom_Type: No sound at all
  Title: [SOF - sof-bytcht rt5640, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/09/2015
  dmi.bios.release: 18.18
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: NX1015.2.02.017
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: NXM1015BFP
  dmi.board.vendor: YIFANG
  dmi.board.version: 1.2
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvrNX1015.2.02.017:bd11/09/2015:br18.18:efr0.0:svnYIFANG:pnNXW101QC232T:pvrType1-TBDbyOE

[Touch-packages] [Bug 1953052] Re: In Jammy sound level reset after reboot

[Sebastien Bacher]

what's the output of
$ dpkg -l | grep pipewire
?

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

Title:
  In Jammy sound level reset after reboot

Status in alsa-utils package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After reboot sound level is reset ignoring the level set in previous
  session.

  I manually set the sound output level 
  at next boot the sound is set at a different level (about 70%)

  Expected: the sound level is persistent across power off/on

  What happens : sound level is set at a different level (about 70%)

  Note: this problem does not occur on different partitions of same PC
  running Ubuntu 20.04 or 21.10

  corrado@corrado-p3-jj-1130:~$ apt policy gnome-control-center
  gnome-control-center:
Installed: 1:41.1-1ubuntu1
Candidate: 1:41.1-1ubuntu1
Version table:
   *** 1:41.1-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-p3-jj-1130:~$ inxi -Fx
  System:Host: corrado-p3-jj-1130 Kernel: 5.13.0-19-generic x86_64 bits: 64 
compiler: gcc v: 11.2.0
 Desktop: GNOME 40.5 Distro: Ubuntu 22.04 (Jammy Jellyfish)
  Machine:   Type: Laptop System: Dell product: Inspiron 3793 v: N/A serial: 

 Mobo: Dell model: 0C1PF2 v: A00 serial:  UEFI: 
Dell v: 1.5.0 date: 12/17/2019
  Battery:   ID-1: BAT0 charge: 13.9 Wh (42.1%) condition: 33.0/42.0 Wh (78.7%) 
volts: 11.3 min: 11.4
 model: SWD-ATL3.618 DELL WJPC403 status: Discharging
  CPU:   Info: Quad Core model: Intel Core i5-1035G1 bits: 64 type: MT MCP 
arch: Ice Lake rev: 5 cache:
 L2: 6 MiB
 flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 19046
 Speed: 968 MHz min/max: 400/1000 MHz Core speeds (MHz): 1: 968 2: 
710 3: 706 4: 714 5: 966 6: 712
 7: 724 8: 821
  Graphics:  Device-1: Intel Iris Plus Graphics G1 vendor: Dell driver: i915 v: 
kernel bus-ID: 00:02.0
 Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo 
bus-ID: 1-6:3
 Display: wayland server: X.Org 1.21.1.2 compositor: gnome-shell 
driver: loaded: i915
 note: n/a (using device driver) resolution: 1920x1080~60Hz
 OpenGL: renderer: Mesa Intel UHD Graphics (ICL GT1) v: 4.6 Mesa 
21.2.2 direct render: Yes
  Audio: Device-1: Intel Ice Lake-LP Smart Sound Audio vendor: Dell driver: 
snd_hda_intel v: kernel
 bus-ID: 00:1f.3
 Sound Server-1: ALSA v: k5.13.0-19-generic running: yes
 Sound Server-2: PulseAudio v: 15.0 running: yes
 Sound Server-3: PipeWire v: 0.3.40 running: yes
  Network:   Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell 
driver: r8169 v: kernel port: 3000
 bus-ID: 01:00.0
 IF: enp1s0 state: down mac: 98:e7:43:59:19:19
 Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network 
Adapter vendor: Dell driver: ath10k_pci
 v: kernel bus-ID: 02:00.0
 IF: wlp2s0 state: up mac: d8:12:65:b8:21:b9
  Bluetooth: Device-1: Qualcomm Atheros type: USB driver: btusb v: 0.8 bus-ID: 
1-10:4
 Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: 
enabled,running rfk-block: hardware: no
 software: yes address: D8:12:65:B8:21:BA
  Drives:Local Storage: total: 942.7 GiB used: 11.77 GiB (1.2%)
 ID-1: /dev/nvme0n1 vendor: Toshiba model: KBG40ZNS512G NVMe KIOXIA 
512GB size: 476.94 GiB temp: 24.9 C
 ID-2: /dev/sda vendor: Crucial model: CT500MX500SSD1 size: 465.76 
GiB
  Partition: ID-1: / size: 46.95 GiB used: 11.73 GiB (25.0%) fs: ext4 dev: 
/dev/nvme0n1p3
 ID-2: /boot/efi size: 246 MiB used: 46.4 MiB (18.9%) fs: vfat dev: 
/dev/nvme0n1p1
  Swap:  Alert: No swap data was found.
  Sensors:   System Temperatures: cpu: 27.8 C mobo: N/A
 Fan Speeds (RPM): cpu: 0
  Info:  Processes: 263 Uptime: 31m Memory: 15.4 GiB used: 2.45 GiB (15.9%) 
Init: systemd runlevel: 5 Compilers:
 gcc: N/A Packages: 1785 Shell: Bash v: 5.1.12 inxi: 3.3.07
  corrado@corrado-p3-jj-1130:~$
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2021-11-30 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  Package: gnome-control-center 1:41.1-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Tags:  wayland-session jammy
  Uname: Linux 5.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkF

[Touch-packages] [Bug 1960608] Re: python-pip >= 21.3.1+dfsg-3 fails pip3-root.sh autopkgtest with python3.10

[Stefano Rivera]

Yes, it's required. My fix was resolving the python-pip FTBFS you
reported with that patch.

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

Title:
  python-pip >= 21.3.1+dfsg-3 fails pip3-root.sh autopkgtest with
  python3.10

Status in dh-python package in Ubuntu:
  Fix Released
Status in python-pip package in Ubuntu:
  New
Status in python3.10 package in Ubuntu:
  Confirmed

Bug description:
  pip3-root.sh expects world package to be installed in
  /usr/local/lib/python3.*/dist-packages whereas it is actually
  installed into /usr/lib/python3.10/site-packages/.

  It even fails to uninstall the package right after installing it:

  ubuntu@autopkgtest:~$ sudo python3 -m pip install world
  Collecting world
Using cached world-4.1.1-py3-none-any.whl
  Collecting atpublic
Using cached atpublic-3.0.1-py3-none-any.whl (4.8 kB)
  Installing collected packages: atpublic, world
  Successfully installed atpublic-3.0.1 world-4.1.1
  WARNING: Running pip as the 'root' user can result in broken permissions and 
conflicting behaviour with the system package manager. It is recommended to use 
a virtual environment instead: https://pip.pypa.io/warnings/venv
  ubuntu@autopkgtest:~$ sudo python3 -m pip uninstall world
  WARNING: Skipping world as it is not installed.
  WARNING: Running pip as the 'root' user can result in broken permissions and 
conflicting behaviour with the system package manager. It is recommended to use 
a virtual environment instead: https://pip.pypa.io/warnings/venv

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/1960608/+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 1953052] Re: In Jammy sound level reset after reboot

[corrado venturini]

how can i tell if i have pulseaudio and pipewire activated?

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

Title:
  In Jammy sound level reset after reboot

Status in alsa-utils package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After reboot sound level is reset ignoring the level set in previous
  session.

  I manually set the sound output level 
  at next boot the sound is set at a different level (about 70%)

  Expected: the sound level is persistent across power off/on

  What happens : sound level is set at a different level (about 70%)

  Note: this problem does not occur on different partitions of same PC
  running Ubuntu 20.04 or 21.10

  corrado@corrado-p3-jj-1130:~$ apt policy gnome-control-center
  gnome-control-center:
Installed: 1:41.1-1ubuntu1
Candidate: 1:41.1-1ubuntu1
Version table:
   *** 1:41.1-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-p3-jj-1130:~$ inxi -Fx
  System:Host: corrado-p3-jj-1130 Kernel: 5.13.0-19-generic x86_64 bits: 64 
compiler: gcc v: 11.2.0
 Desktop: GNOME 40.5 Distro: Ubuntu 22.04 (Jammy Jellyfish)
  Machine:   Type: Laptop System: Dell product: Inspiron 3793 v: N/A serial: 

 Mobo: Dell model: 0C1PF2 v: A00 serial:  UEFI: 
Dell v: 1.5.0 date: 12/17/2019
  Battery:   ID-1: BAT0 charge: 13.9 Wh (42.1%) condition: 33.0/42.0 Wh (78.7%) 
volts: 11.3 min: 11.4
 model: SWD-ATL3.618 DELL WJPC403 status: Discharging
  CPU:   Info: Quad Core model: Intel Core i5-1035G1 bits: 64 type: MT MCP 
arch: Ice Lake rev: 5 cache:
 L2: 6 MiB
 flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 19046
 Speed: 968 MHz min/max: 400/1000 MHz Core speeds (MHz): 1: 968 2: 
710 3: 706 4: 714 5: 966 6: 712
 7: 724 8: 821
  Graphics:  Device-1: Intel Iris Plus Graphics G1 vendor: Dell driver: i915 v: 
kernel bus-ID: 00:02.0
 Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo 
bus-ID: 1-6:3
 Display: wayland server: X.Org 1.21.1.2 compositor: gnome-shell 
driver: loaded: i915
 note: n/a (using device driver) resolution: 1920x1080~60Hz
 OpenGL: renderer: Mesa Intel UHD Graphics (ICL GT1) v: 4.6 Mesa 
21.2.2 direct render: Yes
  Audio: Device-1: Intel Ice Lake-LP Smart Sound Audio vendor: Dell driver: 
snd_hda_intel v: kernel
 bus-ID: 00:1f.3
 Sound Server-1: ALSA v: k5.13.0-19-generic running: yes
 Sound Server-2: PulseAudio v: 15.0 running: yes
 Sound Server-3: PipeWire v: 0.3.40 running: yes
  Network:   Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell 
driver: r8169 v: kernel port: 3000
 bus-ID: 01:00.0
 IF: enp1s0 state: down mac: 98:e7:43:59:19:19
 Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network 
Adapter vendor: Dell driver: ath10k_pci
 v: kernel bus-ID: 02:00.0
 IF: wlp2s0 state: up mac: d8:12:65:b8:21:b9
  Bluetooth: Device-1: Qualcomm Atheros type: USB driver: btusb v: 0.8 bus-ID: 
1-10:4
 Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: 
enabled,running rfk-block: hardware: no
 software: yes address: D8:12:65:B8:21:BA
  Drives:Local Storage: total: 942.7 GiB used: 11.77 GiB (1.2%)
 ID-1: /dev/nvme0n1 vendor: Toshiba model: KBG40ZNS512G NVMe KIOXIA 
512GB size: 476.94 GiB temp: 24.9 C
 ID-2: /dev/sda vendor: Crucial model: CT500MX500SSD1 size: 465.76 
GiB
  Partition: ID-1: / size: 46.95 GiB used: 11.73 GiB (25.0%) fs: ext4 dev: 
/dev/nvme0n1p3
 ID-2: /boot/efi size: 246 MiB used: 46.4 MiB (18.9%) fs: vfat dev: 
/dev/nvme0n1p1
  Swap:  Alert: No swap data was found.
  Sensors:   System Temperatures: cpu: 27.8 C mobo: N/A
 Fan Speeds (RPM): cpu: 0
  Info:  Processes: 263 Uptime: 31m Memory: 15.4 GiB used: 2.45 GiB (15.9%) 
Init: systemd runlevel: 5 Compilers:
 gcc: N/A Packages: 1785 Shell: Bash v: 5.1.12 inxi: 3.3.07
  corrado@corrado-p3-jj-1130:~$
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2021-11-30 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  Package: gnome-control-center 1:41.1-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Tags:  wayland-session jammy
  Uname: Linux 5.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare su

[Touch-packages] [Bug 1914278] Re: Kernel updates marked as "manually installed", prevents old kernels cleanup

[Brian Murray]

** Tags removed: rls-jj-incoming

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

Title:
  Kernel updates marked as "manually installed", prevents old kernels
  cleanup

Status in apt package in Ubuntu:
  Invalid
Status in discover package in Ubuntu:
  Invalid
Status in packagekit package in Ubuntu:
  In Progress
Status in unattended-upgrades package in Ubuntu:
  Invalid
Status in apt source package in Jammy:
  Invalid
Status in discover source package in Jammy:
  Invalid
Status in packagekit source package in Jammy:
  In Progress
Status in unattended-upgrades source package in Jammy:
  Invalid

Bug description:
  With the machines I help administer, we have been finding situations
  where the /boot directory is filling-up beyond 3 kernels on LUKS
  encrypted systems. apt autoremove is not removing old kernels as
  expected.

  This may also be an issue with unattended-upgrades since I found the
  following line commented-out by default:

  // Remove unused automatically installed kernel-related packages
  // (kernel images, kernel headers and kernel version locked tools).
  // Unattended-Upgrade::Remove-Unused-Kernel-Packages "true";

  We have had a system with as many as 15 kernel packages installed as a
  result of this not working as expected.

  The majority of these machines are using Discover to do their package
  upgrading, which uses PackageKit as its backend.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apt 2.0.4
  ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Tue Feb  2 09:29:01 2021
  InstallationDate: Installed on 2020-11-07 (87 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1914278/+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 1961333] [NEW] Netbook display is turned off on login screen on startup

[Leonardo Soares Müller]

Public bug reported:

On the netbook model Positivo Mobo 5800, it was noticed that, on the end
of the boot process, the LightDM greeter won't appear and the screen
will turn off, disabling the backlight too. To be able to log in to the
graphical interface, it's required to go to a tty (for example, tty1)
and then back to the LightDM greeter (which is tty7 on this case).

When going back to the tty7, it's noticed that there are text still from
the boot for a few seconds, until the greeter finally appears.

The CPU is an Intel(R) Atom(TM) CPU N2600 @ 1.60GHz, it has a gma500
GPU. While gma500 is limiting, I've not observed this LightDM bug with,
for example, the Positivo Mobo 5900, which has the same CPU and same GPU
with the same revision and, even when applying the same image to both,
the 5900 works while the 5800 fails.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: lightdm 1.30.0-0ubuntu4~20.04.2
ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166
Uname: Linux 5.4.0-100-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Feb 17 15:30:44 2022
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal

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

Title:
  Netbook display is turned off on login screen on startup

Status in lightdm package in Ubuntu:
  New

Bug description:
  On the netbook model Positivo Mobo 5800, it was noticed that, on the
  end of the boot process, the LightDM greeter won't appear and the
  screen will turn off, disabling the backlight too. To be able to log
  in to the graphical interface, it's required to go to a tty (for
  example, tty1) and then back to the LightDM greeter (which is tty7 on
  this case).

  When going back to the tty7, it's noticed that there are text still
  from the boot for a few seconds, until the greeter finally appears.

  The CPU is an Intel(R) Atom(TM) CPU N2600 @ 1.60GHz, it has a gma500
  GPU. While gma500 is limiting, I've not observed this LightDM bug
  with, for example, the Positivo Mobo 5900, which has the same CPU and
  same GPU with the same revision and, even when applying the same image
  to both, the 5900 works while the 5800 fails.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: lightdm 1.30.0-0ubuntu4~20.04.2
  ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166
  Uname: Linux 5.4.0-100-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Feb 17 15:30:44 2022
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1961333/+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 1959085] Re: Ubuntu 21.10 boot stuck in initramfs

[Launchpad Bug Tracker]

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

** Changed in: zfs-linux (Ubuntu)
   Status: New => Confirmed

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

Title:
  Ubuntu 21.10 boot stuck in initramfs

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in zfs-linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I just installed the latest Ubuntu desktop from iso file
  ubuntu-21.10-desktop-amd64.iso inside of VMWare workstation. I chose
  ZFS and native ZFS encryption of the filesystem. The installation went
  fine. Everything worked as expected.

  Then I upgraded the packages to the latest version via the Software
  updater. After reboot I'm stuck in the initramfs prompt. The following
  command fails:

  mount -o zfsutil -t zfs rpool/ROOT/ubuntu_gtw63h /root//

  Permission denied.

  And the system never asks me for the password to unlock the root fs.

  So, I'm guessing that there is something wrong with the new initramfs
  disk: initrd.img-5.13.0-27-generic

  When I reboot and select the previous version in grub:
  initrd.img-5.13.0-27-generic, the system asks for the password and
  boots without a problem.

  Thanks.

  To summarize:

  1. Installed new VM using the Ubuntu iso image. Chose ZFS native encryption. 
Minimal install.
  2. As soon as the system came up, I hit the update/upgrade prompt. Rebooted 
and failed to boot the new version.

  I didn't customize anything or installed anything extra.

  root@ubud01:/var# lsb_release -rd
  Description:  Ubuntu 21.10
  Release:  21.10

  root@ubud01:/var# dpkg -l | grep zfs
  ii  libzfs4linux   2.0.6-1ubuntu2 
amd64OpenZFS filesystem library for Linux
  ii  zfs-initramfs  2.0.6-1ubuntu2 
amd64OpenZFS root filesystem capabilities for Linux - 
initramfs
  ii  zfs-zed2.0.6-1ubuntu2 
amd64OpenZFS Event Daemon
  ii  zfsutils-linux 2.0.6-1ubuntu2 
amd64command-line tools to manage OpenZFS filesystems

  root@ubud01:/var# dpkg -l | grep init
  ii  busybox-initramfs  1:1.30.1-6ubuntu3.1
amd64Standalone shell setup for initramfs
  ii  cryptsetup-initramfs   2:2.3.6-0ubuntu1   
all  disk encryption support - initramfs integration
  ii  gnome-initial-setup40.4-1ubuntu1  
amd64Initial GNOME system setup helper
  ii  init   1.60build1 
amd64metapackage ensuring an init system is installed
  ii  init-system-helpers1.60build1 
all  helper tools for all init systems
  ii  initramfs-tools0.140ubuntu6   
all  generic modular initramfs generator (automation)
  ii  initramfs-tools-bin0.140ubuntu6   
amd64binaries used by initramfs-tools
  ii  initramfs-tools-core   0.140ubuntu6   
all  generic modular initramfs generator (core tools)
  ii  libatopology2:amd641.2.4-1.1ubuntu3.1 
amd64shared library for handling ALSA topology definitions
  ii  libklibc:amd64 2.0.8-6.1ubuntu2   
amd64minimal libc subset for use with initramfs
  ii  lsb-base   11.1.0ubuntu3  
all  Linux Standard Base init script functionality
  ii  ncurses-base   6.2+20201114-2build1   
all  basic terminal type definitions
  ii  sysvinit-utils 2.96-7ubuntu1  
amd64System-V-like utilities
  ii  xinit  1.4.1-0ubuntu3 
amd64X server initialisation tool
  ii  zfs-initramfs  2.0.6-1ubuntu2 
amd64OpenZFS root filesystem capabilities for Linux - 
initramfs

  root@ubud01:/var# zfs list
  NAME   USED  AVAIL REFER  
MOUNTPOINT
  bpool  290M   542M   96K  
/boot
  bpool/BOOT 289M   542M   96K  none
  bpool/BOOT/ubuntu_gtw63h   288M   542M  156M  
/boot
  rpool

[Touch-packages] [Bug 1960425] Re: package linux-image-5.13.0-28-generic 5.13.0-28.31~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Dana Sawyer]

Error message appeared a few minutes after exiting Suspend mode.

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

Title:
  package linux-image-5.13.0-28-generic 5.13.0-28.31~20.04.1 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  Not sure - submitting crash record

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-28-generic 5.13.0-28.31~20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Feb  9 11:10:21 2022
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2021-11-30 (70 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: initramfs-tools
  Title: package linux-image-5.13.0-28-generic 5.13.0-28.31~20.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1960425/+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 1960425] Re: package linux-image-5.13.0-28-generic 5.13.0-28.31~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Launchpad Bug Tracker]

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

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Confirmed

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

Title:
  package linux-image-5.13.0-28-generic 5.13.0-28.31~20.04.1 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  Not sure - submitting crash record

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.13.0-28-generic 5.13.0-28.31~20.04.1
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Feb  9 11:10:21 2022
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2021-11-30 (70 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: initramfs-tools
  Title: package linux-image-5.13.0-28-generic 5.13.0-28.31~20.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1960425/+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 1961327] [NEW] Audio drops when switiching applications

[A S]

Public bug reported:

The audio on my laptop drops when I open a new application (or switch to
a different one). Sometimes it happens when switching tabs. It does not
matter which application is playing audio, the audio usually stops when
the application is switched.

The typical workaround is to kill pulseaudio and start it again but that
requires me to restart the application which is playing the audio. I
found a better workaround which is to open PulseAudio Volume Control
(pavucontrol) and toggle the profile from "Play HiFi quality music" ->
"Off" -> "Play HiFi quality music".

➜ lsb_release -rd
Description:Ubuntu 21.10
Release:21.10

➜ apt-cache policy pulseaudio
pulseaudio:
  Installed: 1:15.0+dfsg1-1ubuntu2.2
  Candidate: 1:15.0+dfsg1-1ubuntu2.2
  Version table:
 *** 1:15.0+dfsg1-1ubuntu2.2 500
500 http://ca.archive.ubuntu.com/ubuntu impish-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 1:15.0+dfsg1-1ubuntu2 500
500 http://ca.archive.ubuntu.com/ubuntu impish/main amd64 Packages

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

** Description changed:

  The audio on my laptop drops when I open a new application (or switch to
  a different one). Sometimes it happens when switching tabs. It does not
  matter which application is playing audio, the audio usually stops when
  the application is switched.
  
  The typical workaround is to kill pulseaudio and start it again but that
  requires me to restart the application which is playing the audio. I
  found a better workaround which is to open PulseAudio Volume Control
  (pavucontrol) and toggle the profile from "Play HiFi quality music" ->
  "Off" -> "Play HiFi quality music".
  
- 
- ```
+ `
  ➜ lsb_release -rd
  Description:  Ubuntu 21.10
  Release:  21.10
- ```
+ `
  
- ```
+ `
  apt-cache policy pulseaudio
  pulseaudio:
-   Installed: 1:15.0+dfsg1-1ubuntu2.2
-   Candidate: 1:15.0+dfsg1-1ubuntu2.2
-   Version table:
-  *** 1:15.0+dfsg1-1ubuntu2.2 500
- 500 http://ca.archive.ubuntu.com/ubuntu impish-updates/main amd64 
Packages
- 100 /var/lib/dpkg/status
-  1:15.0+dfsg1-1ubuntu2 500
- 500 http://ca.archive.ubuntu.com/ubuntu impish/main amd64 Packages
- ```
+   Installed: 1:15.0+dfsg1-1ubuntu2.2
+   Candidate: 1:15.0+dfsg1-1ubuntu2.2
+   Version table:
+  *** 1:15.0+dfsg1-1ubuntu2.2 500
+ 500 http://ca.archive.ubuntu.com/ubuntu impish-updates/main amd64 
Packages
+ 100 /var/lib/dpkg/status
+  1:15.0+dfsg1-1ubuntu2 500
+ 500 http://ca.archive.ubuntu.com/ubuntu impish/main amd64 Packages
+ `

** Description changed:

  The audio on my laptop drops when I open a new application (or switch to
  a different one). Sometimes it happens when switching tabs. It does not
  matter which application is playing audio, the audio usually stops when
  the application is switched.
  
  The typical workaround is to kill pulseaudio and start it again but that
  requires me to restart the application which is playing the audio. I
  found a better workaround which is to open PulseAudio Volume Control
  (pavucontrol) and toggle the profile from "Play HiFi quality music" ->
  "Off" -> "Play HiFi quality music".
  
- `
+ 
  ➜ lsb_release -rd
  Description:  Ubuntu 21.10
  Release:  21.10
  `
  
- `
- apt-cache policy pulseaudio
+ 
+ ➜ apt-cache policy pulseaudio
  pulseaudio:
    Installed: 1:15.0+dfsg1-1ubuntu2.2
    Candidate: 1:15.0+dfsg1-1ubuntu2.2
    Version table:
   *** 1:15.0+dfsg1-1ubuntu2.2 500
  500 http://ca.archive.ubuntu.com/ubuntu impish-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:15.0+dfsg1-1ubuntu2 500
  500 http://ca.archive.ubuntu.com/ubuntu impish/main amd64 Packages
- `

** Description changed:

  The audio on my laptop drops when I open a new application (or switch to
  a different one). Sometimes it happens when switching tabs. It does not
  matter which application is playing audio, the audio usually stops when
  the application is switched.
  
  The typical workaround is to kill pulseaudio and start it again but that
  requires me to restart the application which is playing the audio. I
  found a better workaround which is to open PulseAudio Volume Control
  (pavucontrol) and toggle the profile from "Play HiFi quality music" ->
  "Off" -> "Play HiFi quality music".
  
- 
  ➜ lsb_release -rd
  Description:  Ubuntu 21.10
  Release:  21.10
- `
- 
  
  ➜ apt-cache policy pulseaudio
  pulseaudio:
    Installed: 1:15.0+dfsg1-1ubuntu2.2
    Candidate: 1:15.0+dfsg1-1ubuntu2.2
    Version table:
   *** 1:15.0+dfsg1-1ubuntu2.2 500
  500 http://ca.archive.ubuntu.com/ubuntu impish-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:15.0+dfsg1-1ubuntu2 500
  500 http://ca.archive.ubuntu.com/ubuntu impish/main amd64 Packages

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscri

[Touch-packages] [Bug 1953052] Re: In Jammy sound level reset after reboot

[Igor V. Kovalenko]

Do you have both pulseaudio and pipewire audio enabled simultaneously?
At least system log suggests pipewire with session manager is also being
activated, this could cause issues if both attempt to restore volumes
for some reason.

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

Title:
  In Jammy sound level reset after reboot

Status in alsa-utils package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After reboot sound level is reset ignoring the level set in previous
  session.

  I manually set the sound output level 
  at next boot the sound is set at a different level (about 70%)

  Expected: the sound level is persistent across power off/on

  What happens : sound level is set at a different level (about 70%)

  Note: this problem does not occur on different partitions of same PC
  running Ubuntu 20.04 or 21.10

  corrado@corrado-p3-jj-1130:~$ apt policy gnome-control-center
  gnome-control-center:
Installed: 1:41.1-1ubuntu1
Candidate: 1:41.1-1ubuntu1
Version table:
   *** 1:41.1-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-p3-jj-1130:~$ inxi -Fx
  System:Host: corrado-p3-jj-1130 Kernel: 5.13.0-19-generic x86_64 bits: 64 
compiler: gcc v: 11.2.0
 Desktop: GNOME 40.5 Distro: Ubuntu 22.04 (Jammy Jellyfish)
  Machine:   Type: Laptop System: Dell product: Inspiron 3793 v: N/A serial: 

 Mobo: Dell model: 0C1PF2 v: A00 serial:  UEFI: 
Dell v: 1.5.0 date: 12/17/2019
  Battery:   ID-1: BAT0 charge: 13.9 Wh (42.1%) condition: 33.0/42.0 Wh (78.7%) 
volts: 11.3 min: 11.4
 model: SWD-ATL3.618 DELL WJPC403 status: Discharging
  CPU:   Info: Quad Core model: Intel Core i5-1035G1 bits: 64 type: MT MCP 
arch: Ice Lake rev: 5 cache:
 L2: 6 MiB
 flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 19046
 Speed: 968 MHz min/max: 400/1000 MHz Core speeds (MHz): 1: 968 2: 
710 3: 706 4: 714 5: 966 6: 712
 7: 724 8: 821
  Graphics:  Device-1: Intel Iris Plus Graphics G1 vendor: Dell driver: i915 v: 
kernel bus-ID: 00:02.0
 Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo 
bus-ID: 1-6:3
 Display: wayland server: X.Org 1.21.1.2 compositor: gnome-shell 
driver: loaded: i915
 note: n/a (using device driver) resolution: 1920x1080~60Hz
 OpenGL: renderer: Mesa Intel UHD Graphics (ICL GT1) v: 4.6 Mesa 
21.2.2 direct render: Yes
  Audio: Device-1: Intel Ice Lake-LP Smart Sound Audio vendor: Dell driver: 
snd_hda_intel v: kernel
 bus-ID: 00:1f.3
 Sound Server-1: ALSA v: k5.13.0-19-generic running: yes
 Sound Server-2: PulseAudio v: 15.0 running: yes
 Sound Server-3: PipeWire v: 0.3.40 running: yes
  Network:   Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell 
driver: r8169 v: kernel port: 3000
 bus-ID: 01:00.0
 IF: enp1s0 state: down mac: 98:e7:43:59:19:19
 Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network 
Adapter vendor: Dell driver: ath10k_pci
 v: kernel bus-ID: 02:00.0
 IF: wlp2s0 state: up mac: d8:12:65:b8:21:b9
  Bluetooth: Device-1: Qualcomm Atheros type: USB driver: btusb v: 0.8 bus-ID: 
1-10:4
 Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: 
enabled,running rfk-block: hardware: no
 software: yes address: D8:12:65:B8:21:BA
  Drives:Local Storage: total: 942.7 GiB used: 11.77 GiB (1.2%)
 ID-1: /dev/nvme0n1 vendor: Toshiba model: KBG40ZNS512G NVMe KIOXIA 
512GB size: 476.94 GiB temp: 24.9 C
 ID-2: /dev/sda vendor: Crucial model: CT500MX500SSD1 size: 465.76 
GiB
  Partition: ID-1: / size: 46.95 GiB used: 11.73 GiB (25.0%) fs: ext4 dev: 
/dev/nvme0n1p3
 ID-2: /boot/efi size: 246 MiB used: 46.4 MiB (18.9%) fs: vfat dev: 
/dev/nvme0n1p1
  Swap:  Alert: No swap data was found.
  Sensors:   System Temperatures: cpu: 27.8 C mobo: N/A
 Fan Speeds (RPM): cpu: 0
  Info:  Processes: 263 Uptime: 31m Memory: 15.4 GiB used: 2.45 GiB (15.9%) 
Init: systemd runlevel: 5 Compilers:
 gcc: N/A Packages: 1785 Shell: Bash v: 5.1.12 inxi: 3.3.07
  corrado@corrado-p3-jj-1130:~$
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2021-11-30 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  Package: gnome-control-center 1:41.1-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Tags:  wayland-session j

[Touch-packages] [Bug 1956202] Re: `libexpat1-dev` CMake configuration error

[Andrew Aitchison]

https://github.com/OSGeo/gdal/issues/5324 is a result of this and the
upstream https://github.com/libexpat/libexpat/issues/501

** Bug watch added: github.com/OSGeo/gdal/issues #5324
   https://github.com/OSGeo/gdal/issues/5324

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

Title:
  `libexpat1-dev` CMake configuration error

Status in Expat:
  Unknown
Status in expat package in Ubuntu:
  Confirmed

Bug description:
  Using the package provided by Ubuntu Impish results in the following
  CMake configuration error when trying to build OpenColorIO:

  ```
  […]
  CMake Error in src/OpenColorIO/CMakeLists.txt:
    Imported target "expat::expat" includes non-existent path

  "/usr/lib/include"

    in its INTERFACE_INCLUDE_DIRECTORIES.  Possible reasons include:

    * The path was deleted, renamed, or moved to another location.

    * An install or uninstall procedure did not complete successfully.

    * The installation package was faulty and references files it does not
    provide.
  […]
  ```

  This wasn't an issue in Ubuntu Hirsute as far as I can recall and is
  not an issue when using the ASWF-provided packages — CMake flag
  `-DOCIO_INSTALL_EXT_PACKAGES=ALL`. A patch is attached that allows
  OpenColorIO to build using system-provided packages.

  Further information in the related ticket in the OpenColorIO
  repository:
  
https://github.com/AcademySoftwareFoundation/OpenColorIO/issues/1415#issuecomment-1003826550

To manage notifications about this bug go to:
https://bugs.launchpad.net/expat/+bug/1956202/+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 1956202] Re: `libexpat1-dev` CMake configuration error

[Launchpad Bug Tracker]

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

** Changed in: expat (Ubuntu)
   Status: New => Confirmed

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

Title:
  `libexpat1-dev` CMake configuration error

Status in Expat:
  Unknown
Status in expat package in Ubuntu:
  Confirmed

Bug description:
  Using the package provided by Ubuntu Impish results in the following
  CMake configuration error when trying to build OpenColorIO:

  ```
  […]
  CMake Error in src/OpenColorIO/CMakeLists.txt:
    Imported target "expat::expat" includes non-existent path

  "/usr/lib/include"

    in its INTERFACE_INCLUDE_DIRECTORIES.  Possible reasons include:

    * The path was deleted, renamed, or moved to another location.

    * An install or uninstall procedure did not complete successfully.

    * The installation package was faulty and references files it does not
    provide.
  […]
  ```

  This wasn't an issue in Ubuntu Hirsute as far as I can recall and is
  not an issue when using the ASWF-provided packages — CMake flag
  `-DOCIO_INSTALL_EXT_PACKAGES=ALL`. A patch is attached that allows
  OpenColorIO to build using system-provided packages.

  Further information in the related ticket in the OpenColorIO
  repository:
  
https://github.com/AcademySoftwareFoundation/OpenColorIO/issues/1415#issuecomment-1003826550

To manage notifications about this bug go to:
https://bugs.launchpad.net/expat/+bug/1956202/+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 1956202] Re: `libexpat1-dev` CMake configuration error

[Andrew Aitchison]

** Bug watch added: github.com/libexpat/libexpat/issues #501
   https://github.com/libexpat/libexpat/issues/501

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

Title:
  `libexpat1-dev` CMake configuration error

Status in Expat:
  Unknown
Status in expat package in Ubuntu:
  Confirmed

Bug description:
  Using the package provided by Ubuntu Impish results in the following
  CMake configuration error when trying to build OpenColorIO:

  ```
  […]
  CMake Error in src/OpenColorIO/CMakeLists.txt:
    Imported target "expat::expat" includes non-existent path

  "/usr/lib/include"

    in its INTERFACE_INCLUDE_DIRECTORIES.  Possible reasons include:

    * The path was deleted, renamed, or moved to another location.

    * An install or uninstall procedure did not complete successfully.

    * The installation package was faulty and references files it does not
    provide.
  […]
  ```

  This wasn't an issue in Ubuntu Hirsute as far as I can recall and is
  not an issue when using the ASWF-provided packages — CMake flag
  `-DOCIO_INSTALL_EXT_PACKAGES=ALL`. A patch is attached that allows
  OpenColorIO to build using system-provided packages.

  Further information in the related ticket in the OpenColorIO
  repository:
  
https://github.com/AcademySoftwareFoundation/OpenColorIO/issues/1415#issuecomment-1003826550

To manage notifications about this bug go to:
https://bugs.launchpad.net/expat/+bug/1956202/+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 1960947] Autopkgtest regression report (gtk+3.0/3.24.20-0ubuntu1.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted gtk+3.0 (3.24.20-0ubuntu1.1) for focal 
have finished running.
The following regressions have been reported in tests triggered by the package:

aptdaemon/1.1.1+bzr982-0ubuntu32.3 (arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/focal/update_excuses.html#gtk+3.0

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Graphical issues for GtKGL in software rendering

Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Focal:
  Fix Committed

Bug description:
  * Issue

  GTK applications using GL graphic show corruption problems under
  software rendering

  
  * Test case

  1. install gtk-3-examples
  2. $ LIBGL_ALWAYS_SOFTWARE=1 gtk3-demo
  3. select the gl example, it should render without issues

  * Regression potentiel

  The change is in the GL backend so check for rendering issues in GTK
  softwares using GL, including flutter applications

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1960947/+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 1956202] Re: `libexpat1-dev` CMake configuration error

[Andrew Aitchison]

** Also affects: expat via
   https://github.com/libexpat/libexpat/issues/501
   Importance: Unknown
   Status: Unknown

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

Title:
  `libexpat1-dev` CMake configuration error

Status in Expat:
  Unknown
Status in expat package in Ubuntu:
  New

Bug description:
  Using the package provided by Ubuntu Impish results in the following
  CMake configuration error when trying to build OpenColorIO:

  ```
  […]
  CMake Error in src/OpenColorIO/CMakeLists.txt:
    Imported target "expat::expat" includes non-existent path

  "/usr/lib/include"

    in its INTERFACE_INCLUDE_DIRECTORIES.  Possible reasons include:

    * The path was deleted, renamed, or moved to another location.

    * An install or uninstall procedure did not complete successfully.

    * The installation package was faulty and references files it does not
    provide.
  […]
  ```

  This wasn't an issue in Ubuntu Hirsute as far as I can recall and is
  not an issue when using the ASWF-provided packages — CMake flag
  `-DOCIO_INSTALL_EXT_PACKAGES=ALL`. A patch is attached that allows
  OpenColorIO to build using system-provided packages.

  Further information in the related ticket in the OpenColorIO
  repository:
  
https://github.com/AcademySoftwareFoundation/OpenColorIO/issues/1415#issuecomment-1003826550

To manage notifications about this bug go to:
https://bugs.launchpad.net/expat/+bug/1956202/+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 1914278] Re: Kernel updates marked as "manually installed", prevents old kernels cleanup

[Julian Andres Klode]

1.2.5 is out now, I'll go grab that directly rather than try to
reconstruct the correct ugit tarball for the git snapshot :)

** Changed in: packagekit (Ubuntu Jammy)
 Assignee: (unassigned) => Julian Andres Klode (juliank)

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

Title:
  Kernel updates marked as "manually installed", prevents old kernels
  cleanup

Status in apt package in Ubuntu:
  Invalid
Status in discover package in Ubuntu:
  Invalid
Status in packagekit package in Ubuntu:
  In Progress
Status in unattended-upgrades package in Ubuntu:
  Invalid
Status in apt source package in Jammy:
  Invalid
Status in discover source package in Jammy:
  Invalid
Status in packagekit source package in Jammy:
  In Progress
Status in unattended-upgrades source package in Jammy:
  Invalid

Bug description:
  With the machines I help administer, we have been finding situations
  where the /boot directory is filling-up beyond 3 kernels on LUKS
  encrypted systems. apt autoremove is not removing old kernels as
  expected.

  This may also be an issue with unattended-upgrades since I found the
  following line commented-out by default:

  // Remove unused automatically installed kernel-related packages
  // (kernel images, kernel headers and kernel version locked tools).
  // Unattended-Upgrade::Remove-Unused-Kernel-Packages "true";

  We have had a system with as many as 15 kernel packages installed as a
  result of this not working as expected.

  The majority of these machines are using Discover to do their package
  upgrading, which uses PackageKit as its backend.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apt 2.0.4
  ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Tue Feb  2 09:29:01 2021
  InstallationDate: Installed on 2020-11-07 (87 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1914278/+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 1914278] Re: Kernel updates marked as "manually installed", prevents old kernels cleanup

[Matthieu Clemenceau]

** Tags added: fr-2064

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

Title:
  Kernel updates marked as "manually installed", prevents old kernels
  cleanup

Status in apt package in Ubuntu:
  Invalid
Status in discover package in Ubuntu:
  Invalid
Status in packagekit package in Ubuntu:
  In Progress
Status in unattended-upgrades package in Ubuntu:
  Invalid
Status in apt source package in Jammy:
  Invalid
Status in discover source package in Jammy:
  Invalid
Status in packagekit source package in Jammy:
  In Progress
Status in unattended-upgrades source package in Jammy:
  Invalid

Bug description:
  With the machines I help administer, we have been finding situations
  where the /boot directory is filling-up beyond 3 kernels on LUKS
  encrypted systems. apt autoremove is not removing old kernels as
  expected.

  This may also be an issue with unattended-upgrades since I found the
  following line commented-out by default:

  // Remove unused automatically installed kernel-related packages
  // (kernel images, kernel headers and kernel version locked tools).
  // Unattended-Upgrade::Remove-Unused-Kernel-Packages "true";

  We have had a system with as many as 15 kernel packages installed as a
  result of this not working as expected.

  The majority of these machines are using Discover to do their package
  upgrading, which uses PackageKit as its backend.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apt 2.0.4
  ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Tue Feb  2 09:29:01 2021
  InstallationDate: Installed on 2020-11-07 (87 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1914278/+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 1961305] [NEW] Cannot boot into Xen dom0

[Thomas Walther]

Public bug reported:

Description:Ubuntu 20.04.3 LTS
Release:20.04

The linux-generic-hwe-20.04 5.13 Kernels are compiled with

#CONFIG_KERNEL_GZIP is not set
CONFIG_KERNEL_ZSTD=y

preventing Xen 4.13.x / 4.14.x from booting into Dom0. After compiling
the kernel by myself using

CONFIG_KERNEL_GZIP=y
#CONFIG_KERNEL_ZSTD is not set

it works as expected. Kernel boots and Xen is working as intended.
Please revert to CONFIG_KERNEL_GZIP=y like in the former HWE (5.11?)
series not having this problem.

Thank you

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Cannot boot into Xen dom0

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 20.04.3 LTS
  Release:  20.04

  The linux-generic-hwe-20.04 5.13 Kernels are compiled with

  #CONFIG_KERNEL_GZIP is not set
  CONFIG_KERNEL_ZSTD=y

  preventing Xen 4.13.x / 4.14.x from booting into Dom0. After compiling
  the kernel by myself using

  CONFIG_KERNEL_GZIP=y
  #CONFIG_KERNEL_ZSTD is not set

  it works as expected. Kernel boots and Xen is working as intended.
  Please revert to CONFIG_KERNEL_GZIP=y like in the former HWE (5.11?)
  series not having this problem.

  Thank you

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1961305/+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 1960608] Re: python-pip >= 21.3.1+dfsg-3 fails pip3-root.sh autopkgtest with python3.10

[Alexandre Ghiti]

I'm not sure I understand: do I need to enable the sysconfig patch for
python3.10 in addition to your fix?

Thanks

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

Title:
  python-pip >= 21.3.1+dfsg-3 fails pip3-root.sh autopkgtest with
  python3.10

Status in dh-python package in Ubuntu:
  Fix Released
Status in python-pip package in Ubuntu:
  New
Status in python3.10 package in Ubuntu:
  Confirmed

Bug description:
  pip3-root.sh expects world package to be installed in
  /usr/local/lib/python3.*/dist-packages whereas it is actually
  installed into /usr/lib/python3.10/site-packages/.

  It even fails to uninstall the package right after installing it:

  ubuntu@autopkgtest:~$ sudo python3 -m pip install world
  Collecting world
Using cached world-4.1.1-py3-none-any.whl
  Collecting atpublic
Using cached atpublic-3.0.1-py3-none-any.whl (4.8 kB)
  Installing collected packages: atpublic, world
  Successfully installed atpublic-3.0.1 world-4.1.1
  WARNING: Running pip as the 'root' user can result in broken permissions and 
conflicting behaviour with the system package manager. It is recommended to use 
a virtual environment instead: https://pip.pypa.io/warnings/venv
  ubuntu@autopkgtest:~$ sudo python3 -m pip uninstall world
  WARNING: Skipping world as it is not installed.
  WARNING: Running pip as the 'root' user can result in broken permissions and 
conflicting behaviour with the system package manager. It is recommended to use 
a virtual environment instead: https://pip.pypa.io/warnings/venv

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dh-python/+bug/1960608/+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 1957909] Re: NetworkManager connectivity check fails

[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/1957909

Title:
  NetworkManager connectivity check fails

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I randomly receive "No internet connection available" notification,
  even if my internet connection is stable. (Not the exact term)

  In /usr/lib/NetworkManager/conf.d/20-connectivity-ubuntu.conf the endpoint 
  http://connectivity-check.ubuntu.com./
  is used. I manually pinged the endpoint.
  I live in europe and the server is located in the US. The latency is about 
160ms. Usually I have an approximate latency of 15ms.
  It is not a problem of my ISP, I receive this notification on different 
locations in Germany and Switzerland.

  I propose to use another endpoint or provide another server for the same 
endpoint for europe.
  So the DNS servers in europe provide the IP of a server located in europe.

  The config comes from the package "network-manager-config-
  connectivity-ubuntu" version 1.32.12-0ubuntu1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1957909/+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 1961196] Re: apparmor autotest failure on jammy with linux 5.15

[Christian Boltz]

This was already fixed upstream with
https://gitlab.com/apparmor/apparmor/-/merge_requests/848 (with a
slightly different patch that works for all python versions).

AppArmor >= 3.0.5 will include the fix.

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

Title:
  apparmor autotest failure on jammy with linux 5.15

Status in apparmor package in Ubuntu:
  New
Status in apparmor source package in Jammy:
  New

Bug description:
  [Impact]

  test-aa-notify is also checking if the output of `aa-notify --help`
  matches a specific text. However it looks like this output has changed
  in jammy so the autopkgtest is reporting errors like this:

  05:17:31 ERROR| [stderr] === test-aa-notify.py ===
  05:17:31 ERROR| [stderr] .ssF.
  05:17:31 ERROR| [stderr] 
==
  05:17:31 ERROR| [stderr] FAIL: test_help_contents (__main__.AANotifyTest)
  05:17:31 ERROR| [stderr] Test output of help text
  05:17:31 ERROR| [stderr] 
--
  05:17:31 ERROR| [stderr] Traceback (most recent call last):
  05:17:31 ERROR| [stderr]   File 
"/tmp/testlibmse00lib/source/jammy/apparmor-3.0.3/utils/test/test-aa-notify.py",
 line 178, in test_help_contents
  05:17:31 ERROR| [stderr] self.assertEqual(expected_output_is, output, 
result + output)
  05:17:31 ERROR| [stderr] AssertionError: 'usag[189 chars]ptional arguments:\n 
 -h, --helpsh[746 chars]de\n' != 'usag[189 chars]ptions:\n  -h, 
--helpshow this hel[735 chars]de\n'
  05:17:31 ERROR| [stderr]   usage: aa-notify [-h] [-p] [--display DISPLAY] [-f 
FILE] [-l] [-s NUM] [-v]
  05:17:31 ERROR| [stderr][-u USER] [-w NUM] [--debug]
  05:17:31 ERROR| [stderr]
  05:17:31 ERROR| [stderr]   Display AppArmor notifications or messages for 
DENIED entries.
  05:17:31 ERROR| [stderr]
  05:17:31 ERROR| [stderr] - optional arguments:
  05:17:31 ERROR| [stderr] + options:
  05:17:31 ERROR| [stderr] -h, --helpshow this help message and 
exit
  05:17:31 ERROR| [stderr] -p, --pollpoll AppArmor logs and 
display notifications
  05:17:31 ERROR| [stderr] --display DISPLAY set the DISPLAY 
environment variable (might be needed if
  05:17:31 ERROR| [stderr]   sudo resets $DISPLAY)
  05:17:31 ERROR| [stderr] -f FILE, --file FILE  search FILE for AppArmor 
messages
  05:17:31 ERROR| [stderr] -l, --since-last  display stats since last 
login
  05:17:31 ERROR| [stderr] -s NUM, --since-days NUM
  05:17:31 ERROR| [stderr]   show stats for last NUM 
days (can be used alone or with
  05:17:31 ERROR| [stderr]   -p)
  05:17:31 ERROR| [stderr] -v, --verbose show messages with stats
  05:17:31 ERROR| [stderr] -u USER, --user USER  user to drop privileges to 
when not using sudo
  05:17:31 ERROR| [stderr] -w NUM, --wait NUMwait NUM seconds before 
displaying notifications (with
  05:17:31 ERROR| [stderr]   -p)
  05:17:31 ERROR| [stderr] --debug   debug mode
  05:17:31 ERROR| [stderr]  : Got output "usage: aa-notify [-h] [-p] [--display 
DISPLAY] [-f FILE] [-l] [-s NUM] [-v]
  05:17:31 ERROR| [stderr]  [-u USER] [-w NUM] [--debug]

  [Test case]

  Simply run test-aa-notify.py from the autopkgtests.

  [Fix]

  Update the expected output returned by `aa-notify --help` in test-aa-
  notify.py.

  [Regression potential]

  This is just an autopkgtest, we may see regressions if the test is
  used with older version of apparmor-notify. With newer versions
  there's no risk of regressions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1961196/+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 1961196] Re: apparmor autotest failure on jammy with linux 5.15

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  apparmor autotest failure on jammy with linux 5.15

Status in apparmor package in Ubuntu:
  New
Status in apparmor source package in Jammy:
  New

Bug description:
  [Impact]

  test-aa-notify is also checking if the output of `aa-notify --help`
  matches a specific text. However it looks like this output has changed
  in jammy so the autopkgtest is reporting errors like this:

  05:17:31 ERROR| [stderr] === test-aa-notify.py ===
  05:17:31 ERROR| [stderr] .ssF.
  05:17:31 ERROR| [stderr] 
==
  05:17:31 ERROR| [stderr] FAIL: test_help_contents (__main__.AANotifyTest)
  05:17:31 ERROR| [stderr] Test output of help text
  05:17:31 ERROR| [stderr] 
--
  05:17:31 ERROR| [stderr] Traceback (most recent call last):
  05:17:31 ERROR| [stderr]   File 
"/tmp/testlibmse00lib/source/jammy/apparmor-3.0.3/utils/test/test-aa-notify.py",
 line 178, in test_help_contents
  05:17:31 ERROR| [stderr] self.assertEqual(expected_output_is, output, 
result + output)
  05:17:31 ERROR| [stderr] AssertionError: 'usag[189 chars]ptional arguments:\n 
 -h, --helpsh[746 chars]de\n' != 'usag[189 chars]ptions:\n  -h, 
--helpshow this hel[735 chars]de\n'
  05:17:31 ERROR| [stderr]   usage: aa-notify [-h] [-p] [--display DISPLAY] [-f 
FILE] [-l] [-s NUM] [-v]
  05:17:31 ERROR| [stderr][-u USER] [-w NUM] [--debug]
  05:17:31 ERROR| [stderr]
  05:17:31 ERROR| [stderr]   Display AppArmor notifications or messages for 
DENIED entries.
  05:17:31 ERROR| [stderr]
  05:17:31 ERROR| [stderr] - optional arguments:
  05:17:31 ERROR| [stderr] + options:
  05:17:31 ERROR| [stderr] -h, --helpshow this help message and 
exit
  05:17:31 ERROR| [stderr] -p, --pollpoll AppArmor logs and 
display notifications
  05:17:31 ERROR| [stderr] --display DISPLAY set the DISPLAY 
environment variable (might be needed if
  05:17:31 ERROR| [stderr]   sudo resets $DISPLAY)
  05:17:31 ERROR| [stderr] -f FILE, --file FILE  search FILE for AppArmor 
messages
  05:17:31 ERROR| [stderr] -l, --since-last  display stats since last 
login
  05:17:31 ERROR| [stderr] -s NUM, --since-days NUM
  05:17:31 ERROR| [stderr]   show stats for last NUM 
days (can be used alone or with
  05:17:31 ERROR| [stderr]   -p)
  05:17:31 ERROR| [stderr] -v, --verbose show messages with stats
  05:17:31 ERROR| [stderr] -u USER, --user USER  user to drop privileges to 
when not using sudo
  05:17:31 ERROR| [stderr] -w NUM, --wait NUMwait NUM seconds before 
displaying notifications (with
  05:17:31 ERROR| [stderr]   -p)
  05:17:31 ERROR| [stderr] --debug   debug mode
  05:17:31 ERROR| [stderr]  : Got output "usage: aa-notify [-h] [-p] [--display 
DISPLAY] [-f FILE] [-l] [-s NUM] [-v]
  05:17:31 ERROR| [stderr]  [-u USER] [-w NUM] [--debug]

  [Test case]

  Simply run test-aa-notify.py from the autopkgtests.

  [Fix]

  Update the expected output returned by `aa-notify --help` in test-aa-
  notify.py.

  [Regression potential]

  This is just an autopkgtest, we may see regressions if the test is
  used with older version of apparmor-notify. With newer versions
  there's no risk of regressions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1961196/+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 1961196] Re: apparmor autotest failure on jammy with linux 5.15

[Andrea Righi]

Simple fix in the attached debdiff

** Patch added: "apparmor-fix-test-aa-notify.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1961196/+attachment/5561612/+files/apparmor-fix-test-aa-notify.debdiff

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

Title:
  apparmor autotest failure on jammy with linux 5.15

Status in apparmor package in Ubuntu:
  New
Status in apparmor source package in Jammy:
  New

Bug description:
  [Impact]

  test-aa-notify is also checking if the output of `aa-notify --help`
  matches a specific text. However it looks like this output has changed
  in jammy so the autopkgtest is reporting errors like this:

  05:17:31 ERROR| [stderr] === test-aa-notify.py ===
  05:17:31 ERROR| [stderr] .ssF.
  05:17:31 ERROR| [stderr] 
==
  05:17:31 ERROR| [stderr] FAIL: test_help_contents (__main__.AANotifyTest)
  05:17:31 ERROR| [stderr] Test output of help text
  05:17:31 ERROR| [stderr] 
--
  05:17:31 ERROR| [stderr] Traceback (most recent call last):
  05:17:31 ERROR| [stderr]   File 
"/tmp/testlibmse00lib/source/jammy/apparmor-3.0.3/utils/test/test-aa-notify.py",
 line 178, in test_help_contents
  05:17:31 ERROR| [stderr] self.assertEqual(expected_output_is, output, 
result + output)
  05:17:31 ERROR| [stderr] AssertionError: 'usag[189 chars]ptional arguments:\n 
 -h, --helpsh[746 chars]de\n' != 'usag[189 chars]ptions:\n  -h, 
--helpshow this hel[735 chars]de\n'
  05:17:31 ERROR| [stderr]   usage: aa-notify [-h] [-p] [--display DISPLAY] [-f 
FILE] [-l] [-s NUM] [-v]
  05:17:31 ERROR| [stderr][-u USER] [-w NUM] [--debug]
  05:17:31 ERROR| [stderr]
  05:17:31 ERROR| [stderr]   Display AppArmor notifications or messages for 
DENIED entries.
  05:17:31 ERROR| [stderr]
  05:17:31 ERROR| [stderr] - optional arguments:
  05:17:31 ERROR| [stderr] + options:
  05:17:31 ERROR| [stderr] -h, --helpshow this help message and 
exit
  05:17:31 ERROR| [stderr] -p, --pollpoll AppArmor logs and 
display notifications
  05:17:31 ERROR| [stderr] --display DISPLAY set the DISPLAY 
environment variable (might be needed if
  05:17:31 ERROR| [stderr]   sudo resets $DISPLAY)
  05:17:31 ERROR| [stderr] -f FILE, --file FILE  search FILE for AppArmor 
messages
  05:17:31 ERROR| [stderr] -l, --since-last  display stats since last 
login
  05:17:31 ERROR| [stderr] -s NUM, --since-days NUM
  05:17:31 ERROR| [stderr]   show stats for last NUM 
days (can be used alone or with
  05:17:31 ERROR| [stderr]   -p)
  05:17:31 ERROR| [stderr] -v, --verbose show messages with stats
  05:17:31 ERROR| [stderr] -u USER, --user USER  user to drop privileges to 
when not using sudo
  05:17:31 ERROR| [stderr] -w NUM, --wait NUMwait NUM seconds before 
displaying notifications (with
  05:17:31 ERROR| [stderr]   -p)
  05:17:31 ERROR| [stderr] --debug   debug mode
  05:17:31 ERROR| [stderr]  : Got output "usage: aa-notify [-h] [-p] [--display 
DISPLAY] [-f FILE] [-l] [-s NUM] [-v]
  05:17:31 ERROR| [stderr]  [-u USER] [-w NUM] [--debug]

  [Test case]

  Simply run test-aa-notify.py from the autopkgtests.

  [Fix]

  Update the expected output returned by `aa-notify --help` in test-aa-
  notify.py.

  [Regression potential]

  This is just an autopkgtest, we may see regressions if the test is
  used with older version of apparmor-notify. With newer versions
  there's no risk of regressions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1961196/+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 1961196] Re: apparmor autotest failure on jammy with linux 5.15

[Andrea Righi]

** Description changed:

+ [Impact]
+ 
+ test-aa-notify is also checking if the output of `aa-notify --help`
+ matches a specific text. However it looks like this output has changed
+ in jammy so the autopkgtest is reporting errors like this:
+ 
  05:17:31 ERROR| [stderr] === test-aa-notify.py ===
  05:17:31 ERROR| [stderr] .ssF.
  05:17:31 ERROR| [stderr] 
==
  05:17:31 ERROR| [stderr] FAIL: test_help_contents (__main__.AANotifyTest)
  05:17:31 ERROR| [stderr] Test output of help text
  05:17:31 ERROR| [stderr] 
--
  05:17:31 ERROR| [stderr] Traceback (most recent call last):
  05:17:31 ERROR| [stderr]   File 
"/tmp/testlibmse00lib/source/jammy/apparmor-3.0.3/utils/test/test-aa-notify.py",
 line 178, in test_help_contents
  05:17:31 ERROR| [stderr] self.assertEqual(expected_output_is, output, 
result + output)
  05:17:31 ERROR| [stderr] AssertionError: 'usag[189 chars]ptional arguments:\n 
 -h, --helpsh[746 chars]de\n' != 'usag[189 chars]ptions:\n  -h, 
--helpshow this hel[735 chars]de\n'
  05:17:31 ERROR| [stderr]   usage: aa-notify [-h] [-p] [--display DISPLAY] [-f 
FILE] [-l] [-s NUM] [-v]
  05:17:31 ERROR| [stderr][-u USER] [-w NUM] [--debug]
- 05:17:31 ERROR| [stderr]   
+ 05:17:31 ERROR| [stderr]
  05:17:31 ERROR| [stderr]   Display AppArmor notifications or messages for 
DENIED entries.
- 05:17:31 ERROR| [stderr]   
+ 05:17:31 ERROR| [stderr]
  05:17:31 ERROR| [stderr] - optional arguments:
  05:17:31 ERROR| [stderr] + options:
  05:17:31 ERROR| [stderr] -h, --helpshow this help message and 
exit
  05:17:31 ERROR| [stderr] -p, --pollpoll AppArmor logs and 
display notifications
  05:17:31 ERROR| [stderr] --display DISPLAY set the DISPLAY 
environment variable (might be needed if
  05:17:31 ERROR| [stderr]   sudo resets $DISPLAY)
  05:17:31 ERROR| [stderr] -f FILE, --file FILE  search FILE for AppArmor 
messages
  05:17:31 ERROR| [stderr] -l, --since-last  display stats since last 
login
  05:17:31 ERROR| [stderr] -s NUM, --since-days NUM
  05:17:31 ERROR| [stderr]   show stats for last NUM 
days (can be used alone or with
  05:17:31 ERROR| [stderr]   -p)
  05:17:31 ERROR| [stderr] -v, --verbose show messages with stats
  05:17:31 ERROR| [stderr] -u USER, --user USER  user to drop privileges to 
when not using sudo
  05:17:31 ERROR| [stderr] -w NUM, --wait NUMwait NUM seconds before 
displaying notifications (with
  05:17:31 ERROR| [stderr]   -p)
  05:17:31 ERROR| [stderr] --debug   debug mode
  05:17:31 ERROR| [stderr]  : Got output "usage: aa-notify [-h] [-p] [--display 
DISPLAY] [-f FILE] [-l] [-s NUM] [-v]
  05:17:31 ERROR| [stderr]  [-u USER] [-w NUM] [--debug]
+ 
+ [Test case]
+ 
+ Simply run test-aa-notify.py from the autopkgtests.
+ 
+ [Fix]
+ 
+ Update the expected output returned by `aa-notify --help` in test-aa-
+ notify.py.
+ 
+ [Regression potential]
+ 
+ This is just an autopkgtest, we may see regressions if the test is used
+ with older version of apparmor-notify. With newer versions there's no
+ risk of regressions.

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

Title:
  apparmor autotest failure on jammy with linux 5.15

Status in apparmor package in Ubuntu:
  New
Status in apparmor source package in Jammy:
  New

Bug description:
  [Impact]

  test-aa-notify is also checking if the output of `aa-notify --help`
  matches a specific text. However it looks like this output has changed
  in jammy so the autopkgtest is reporting errors like this:

  05:17:31 ERROR| [stderr] === test-aa-notify.py ===
  05:17:31 ERROR| [stderr] .ssF.
  05:17:31 ERROR| [stderr] 
==
  05:17:31 ERROR| [stderr] FAIL: test_help_contents (__main__.AANotifyTest)
  05:17:31 ERROR| [stderr] Test output of help text
  05:17:31 ERROR| [stderr] 
--
  05:17:31 ERROR| [stderr] Traceback (most recent call last):
  05:17:31 ERROR| [stderr]   File 
"/tmp/testlibmse00lib/source/jammy/apparmor-3.0.3/utils/test/test-aa-notify.py",
 line 178, in test_help_contents
  05:17:31 ERROR| [stderr] self.assertEqual(expected_output_is, output, 
result + output)
  05:17:31 ERROR| [stderr] AssertionError: 'usag[189 chars]ptional arguments:\n 
 -h, --helpsh[746 chars]de\n' != 'usag[189 chars]ptions:\n  -h, 
--helpshow this hel[735 chars]de\n'
  05:17:31 ERROR| [stderr]   usage: aa-notify [-h] [-p] [--display DISPLAY] [-f 
FILE] [-l] [-s NUM] [-v]
  05:17:31 ER

[Touch-packages] [Bug 1961196] [NEW] apparmor autotest failure on jammy with linux 5.15

[Andrea Righi]

Public bug reported:

05:17:31 ERROR| [stderr] === test-aa-notify.py ===
05:17:31 ERROR| [stderr] .ssF.
05:17:31 ERROR| [stderr] 
==
05:17:31 ERROR| [stderr] FAIL: test_help_contents (__main__.AANotifyTest)
05:17:31 ERROR| [stderr] Test output of help text
05:17:31 ERROR| [stderr] 
--
05:17:31 ERROR| [stderr] Traceback (most recent call last):
05:17:31 ERROR| [stderr]   File 
"/tmp/testlibmse00lib/source/jammy/apparmor-3.0.3/utils/test/test-aa-notify.py",
 line 178, in test_help_contents
05:17:31 ERROR| [stderr] self.assertEqual(expected_output_is, output, 
result + output)
05:17:31 ERROR| [stderr] AssertionError: 'usag[189 chars]ptional arguments:\n  
-h, --helpsh[746 chars]de\n' != 'usag[189 chars]ptions:\n  -h, 
--helpshow this hel[735 chars]de\n'
05:17:31 ERROR| [stderr]   usage: aa-notify [-h] [-p] [--display DISPLAY] [-f 
FILE] [-l] [-s NUM] [-v]
05:17:31 ERROR| [stderr][-u USER] [-w NUM] [--debug]
05:17:31 ERROR| [stderr]   
05:17:31 ERROR| [stderr]   Display AppArmor notifications or messages for 
DENIED entries.
05:17:31 ERROR| [stderr]   
05:17:31 ERROR| [stderr] - optional arguments:
05:17:31 ERROR| [stderr] + options:
05:17:31 ERROR| [stderr] -h, --helpshow this help message and 
exit
05:17:31 ERROR| [stderr] -p, --pollpoll AppArmor logs and 
display notifications
05:17:31 ERROR| [stderr] --display DISPLAY set the DISPLAY environment 
variable (might be needed if
05:17:31 ERROR| [stderr]   sudo resets $DISPLAY)
05:17:31 ERROR| [stderr] -f FILE, --file FILE  search FILE for AppArmor 
messages
05:17:31 ERROR| [stderr] -l, --since-last  display stats since last 
login
05:17:31 ERROR| [stderr] -s NUM, --since-days NUM
05:17:31 ERROR| [stderr]   show stats for last NUM days 
(can be used alone or with
05:17:31 ERROR| [stderr]   -p)
05:17:31 ERROR| [stderr] -v, --verbose show messages with stats
05:17:31 ERROR| [stderr] -u USER, --user USER  user to drop privileges to 
when not using sudo
05:17:31 ERROR| [stderr] -w NUM, --wait NUMwait NUM seconds before 
displaying notifications (with
05:17:31 ERROR| [stderr]   -p)
05:17:31 ERROR| [stderr] --debug   debug mode
05:17:31 ERROR| [stderr]  : Got output "usage: aa-notify [-h] [-p] [--display 
DISPLAY] [-f FILE] [-l] [-s NUM] [-v]
05:17:31 ERROR| [stderr]  [-u USER] [-w NUM] [--debug]

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

** Affects: apparmor (Ubuntu Jammy)
 Importance: Undecided
 Status: New

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

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

Title:
  apparmor autotest failure on jammy with linux 5.15

Status in apparmor package in Ubuntu:
  New
Status in apparmor source package in Jammy:
  New

Bug description:
  05:17:31 ERROR| [stderr] === test-aa-notify.py ===
  05:17:31 ERROR| [stderr] .ssF.
  05:17:31 ERROR| [stderr] 
==
  05:17:31 ERROR| [stderr] FAIL: test_help_contents (__main__.AANotifyTest)
  05:17:31 ERROR| [stderr] Test output of help text
  05:17:31 ERROR| [stderr] 
--
  05:17:31 ERROR| [stderr] Traceback (most recent call last):
  05:17:31 ERROR| [stderr]   File 
"/tmp/testlibmse00lib/source/jammy/apparmor-3.0.3/utils/test/test-aa-notify.py",
 line 178, in test_help_contents
  05:17:31 ERROR| [stderr] self.assertEqual(expected_output_is, output, 
result + output)
  05:17:31 ERROR| [stderr] AssertionError: 'usag[189 chars]ptional arguments:\n 
 -h, --helpsh[746 chars]de\n' != 'usag[189 chars]ptions:\n  -h, 
--helpshow this hel[735 chars]de\n'
  05:17:31 ERROR| [stderr]   usage: aa-notify [-h] [-p] [--display DISPLAY] [-f 
FILE] [-l] [-s NUM] [-v]
  05:17:31 ERROR| [stderr][-u USER] [-w NUM] [--debug]
  05:17:31 ERROR| [stderr]   
  05:17:31 ERROR| [stderr]   Display AppArmor notifications or messages for 
DENIED entries.
  05:17:31 ERROR| [stderr]   
  05:17:31 ERROR| [stderr] - optional arguments:
  05:17:31 ERROR| [stderr] + options:
  05:17:31 ERROR| [stderr] -h, --helpshow this help message and 
exit
  05:17:31 ERROR| [stderr] -p, --pollpoll AppArmor logs and 
display notifications
  05:17:31 ERROR| [stderr] --display DISPLAY set the DISPLAY 
environment variable (might be needed if
  05:17:31 ERROR| [stderr]   sudo resets $DISPLAY)
  05:17:31 

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

[Ilia Kichev]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1960448/+attachment/5561600/+files/ProcInterrupts.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/1960448

Title:
  Sony WF-XB700 Bluetooth headset not detected

Status in bluez package in Ubuntu:
  New
Status in gnome-bluetooth package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Gnome-bluetooth does not detect Sony WF-XB700 bluetooth headset.
  Installed blueman to try to figure out if this is related to gnome-
  bluetooth - the results are the same.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-bluetooth 3.34.5-4
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Feb  9 22:01:56 2022
  InstallationDate: Installed on 2021-09-09 (153 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: gnome-bluetooth
  UpgradeStatus: Upgraded to jammy on 2022-01-13 (27 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2021-09-09 (160 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. G3 3579
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic 
root=UUID=fd3be223-e609-4a8d-97fb-31ee2f754766 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Tags:  jammy
  Uname: Linux 5.15.0-22-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-01-13 (34 days ago)
  UserGroups: adm bluetooth cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/20/2021
  dmi.bios.release: 1.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 0M5H57
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd04/20/2021:br1.15:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn0M5H57:rvrA05:cvnDellInc.:ct10:cvr:sku086F:
  dmi.product.family: GSeries
  dmi.product.name: G3 3579
  dmi.product.sku: 086F
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 98:2C:BC:33:92:E8  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:17341 acl:0 sco:0 events:2806 errors:0
TX bytes:689073 acl:0 sco:0 commands:2804 errors:0

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

[Ilia Kichev]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1960448/+attachment/5561602/+files/UdevDb.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/1960448

Title:
  Sony WF-XB700 Bluetooth headset not detected

Status in bluez package in Ubuntu:
  New
Status in gnome-bluetooth package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Gnome-bluetooth does not detect Sony WF-XB700 bluetooth headset.
  Installed blueman to try to figure out if this is related to gnome-
  bluetooth - the results are the same.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-bluetooth 3.34.5-4
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Feb  9 22:01:56 2022
  InstallationDate: Installed on 2021-09-09 (153 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: gnome-bluetooth
  UpgradeStatus: Upgraded to jammy on 2022-01-13 (27 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2021-09-09 (160 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. G3 3579
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic 
root=UUID=fd3be223-e609-4a8d-97fb-31ee2f754766 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Tags:  jammy
  Uname: Linux 5.15.0-22-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-01-13 (34 days ago)
  UserGroups: adm bluetooth cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/20/2021
  dmi.bios.release: 1.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 0M5H57
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd04/20/2021:br1.15:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn0M5H57:rvrA05:cvnDellInc.:ct10:cvr:sku086F:
  dmi.product.family: GSeries
  dmi.product.name: G3 3579
  dmi.product.sku: 086F
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 98:2C:BC:33:92:E8  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:17341 acl:0 sco:0 events:2806 errors:0
TX bytes:689073 acl:0 sco:0 commands:2804 errors:0

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

[Ilia Kichev]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1960448/+attachment/5561601/+files/ProcModules.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/1960448

Title:
  Sony WF-XB700 Bluetooth headset not detected

Status in bluez package in Ubuntu:
  New
Status in gnome-bluetooth package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Gnome-bluetooth does not detect Sony WF-XB700 bluetooth headset.
  Installed blueman to try to figure out if this is related to gnome-
  bluetooth - the results are the same.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-bluetooth 3.34.5-4
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Feb  9 22:01:56 2022
  InstallationDate: Installed on 2021-09-09 (153 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: gnome-bluetooth
  UpgradeStatus: Upgraded to jammy on 2022-01-13 (27 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2021-09-09 (160 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. G3 3579
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic 
root=UUID=fd3be223-e609-4a8d-97fb-31ee2f754766 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Tags:  jammy
  Uname: Linux 5.15.0-22-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-01-13 (34 days ago)
  UserGroups: adm bluetooth cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/20/2021
  dmi.bios.release: 1.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 0M5H57
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd04/20/2021:br1.15:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn0M5H57:rvrA05:cvnDellInc.:ct10:cvr:sku086F:
  dmi.product.family: GSeries
  dmi.product.name: G3 3579
  dmi.product.sku: 086F
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 98:2C:BC:33:92:E8  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:17341 acl:0 sco:0 events:2806 errors:0
TX bytes:689073 acl:0 sco:0 commands:2804 errors:0

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

[Ilia Kichev]

apport information

** Attachment added: "getfacl.txt"
   
https://bugs.launchpad.net/bugs/1960448/+attachment/5561604/+files/getfacl.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/1960448

Title:
  Sony WF-XB700 Bluetooth headset not detected

Status in bluez package in Ubuntu:
  New
Status in gnome-bluetooth package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Gnome-bluetooth does not detect Sony WF-XB700 bluetooth headset.
  Installed blueman to try to figure out if this is related to gnome-
  bluetooth - the results are the same.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-bluetooth 3.34.5-4
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Feb  9 22:01:56 2022
  InstallationDate: Installed on 2021-09-09 (153 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: gnome-bluetooth
  UpgradeStatus: Upgraded to jammy on 2022-01-13 (27 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2021-09-09 (160 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. G3 3579
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic 
root=UUID=fd3be223-e609-4a8d-97fb-31ee2f754766 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Tags:  jammy
  Uname: Linux 5.15.0-22-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-01-13 (34 days ago)
  UserGroups: adm bluetooth cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/20/2021
  dmi.bios.release: 1.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 0M5H57
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd04/20/2021:br1.15:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn0M5H57:rvrA05:cvnDellInc.:ct10:cvr:sku086F:
  dmi.product.family: GSeries
  dmi.product.name: G3 3579
  dmi.product.sku: 086F
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 98:2C:BC:33:92:E8  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:17341 acl:0 sco:0 events:2806 errors:0
TX bytes:689073 acl:0 sco:0 commands:2804 errors:0

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

[Ilia Kichev]

apport information

** Attachment added: "syslog.txt"
   https://bugs.launchpad.net/bugs/1960448/+attachment/5561606/+files/syslog.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/1960448

Title:
  Sony WF-XB700 Bluetooth headset not detected

Status in bluez package in Ubuntu:
  New
Status in gnome-bluetooth package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Gnome-bluetooth does not detect Sony WF-XB700 bluetooth headset.
  Installed blueman to try to figure out if this is related to gnome-
  bluetooth - the results are the same.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-bluetooth 3.34.5-4
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Feb  9 22:01:56 2022
  InstallationDate: Installed on 2021-09-09 (153 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: gnome-bluetooth
  UpgradeStatus: Upgraded to jammy on 2022-01-13 (27 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2021-09-09 (160 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. G3 3579
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic 
root=UUID=fd3be223-e609-4a8d-97fb-31ee2f754766 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Tags:  jammy
  Uname: Linux 5.15.0-22-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-01-13 (34 days ago)
  UserGroups: adm bluetooth cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/20/2021
  dmi.bios.release: 1.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 0M5H57
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd04/20/2021:br1.15:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn0M5H57:rvrA05:cvnDellInc.:ct10:cvr:sku086F:
  dmi.product.family: GSeries
  dmi.product.name: G3 3579
  dmi.product.sku: 086F
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 98:2C:BC:33:92:E8  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:17341 acl:0 sco:0 events:2806 errors:0
TX bytes:689073 acl:0 sco:0 commands:2804 errors:0

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

[Ilia Kichev]

apport information

** Attachment added: "rfkill.txt"
   https://bugs.launchpad.net/bugs/1960448/+attachment/5561605/+files/rfkill.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/1960448

Title:
  Sony WF-XB700 Bluetooth headset not detected

Status in bluez package in Ubuntu:
  New
Status in gnome-bluetooth package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Gnome-bluetooth does not detect Sony WF-XB700 bluetooth headset.
  Installed blueman to try to figure out if this is related to gnome-
  bluetooth - the results are the same.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-bluetooth 3.34.5-4
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Feb  9 22:01:56 2022
  InstallationDate: Installed on 2021-09-09 (153 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: gnome-bluetooth
  UpgradeStatus: Upgraded to jammy on 2022-01-13 (27 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2021-09-09 (160 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. G3 3579
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic 
root=UUID=fd3be223-e609-4a8d-97fb-31ee2f754766 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Tags:  jammy
  Uname: Linux 5.15.0-22-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-01-13 (34 days ago)
  UserGroups: adm bluetooth cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/20/2021
  dmi.bios.release: 1.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 0M5H57
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd04/20/2021:br1.15:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn0M5H57:rvrA05:cvnDellInc.:ct10:cvr:sku086F:
  dmi.product.family: GSeries
  dmi.product.name: G3 3579
  dmi.product.sku: 086F
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 98:2C:BC:33:92:E8  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:17341 acl:0 sco:0 events:2806 errors:0
TX bytes:689073 acl:0 sco:0 commands:2804 errors:0

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

[Ilia Kichev]

apport information

** Attachment added: "acpidump.txt"
   
https://bugs.launchpad.net/bugs/1960448/+attachment/5561603/+files/acpidump.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/1960448

Title:
  Sony WF-XB700 Bluetooth headset not detected

Status in bluez package in Ubuntu:
  New
Status in gnome-bluetooth package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Gnome-bluetooth does not detect Sony WF-XB700 bluetooth headset.
  Installed blueman to try to figure out if this is related to gnome-
  bluetooth - the results are the same.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-bluetooth 3.34.5-4
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Feb  9 22:01:56 2022
  InstallationDate: Installed on 2021-09-09 (153 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: gnome-bluetooth
  UpgradeStatus: Upgraded to jammy on 2022-01-13 (27 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2021-09-09 (160 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. G3 3579
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic 
root=UUID=fd3be223-e609-4a8d-97fb-31ee2f754766 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Tags:  jammy
  Uname: Linux 5.15.0-22-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-01-13 (34 days ago)
  UserGroups: adm bluetooth cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/20/2021
  dmi.bios.release: 1.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 0M5H57
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd04/20/2021:br1.15:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn0M5H57:rvrA05:cvnDellInc.:ct10:cvr:sku086F:
  dmi.product.family: GSeries
  dmi.product.name: G3 3579
  dmi.product.sku: 086F
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 98:2C:BC:33:92:E8  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:17341 acl:0 sco:0 events:2806 errors:0
TX bytes:689073 acl:0 sco:0 commands:2804 errors:0

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

[Ilia Kichev]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1960448/+attachment/5561599/+files/ProcEnviron.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/1960448

Title:
  Sony WF-XB700 Bluetooth headset not detected

Status in bluez package in Ubuntu:
  New
Status in gnome-bluetooth package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Gnome-bluetooth does not detect Sony WF-XB700 bluetooth headset.
  Installed blueman to try to figure out if this is related to gnome-
  bluetooth - the results are the same.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-bluetooth 3.34.5-4
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Feb  9 22:01:56 2022
  InstallationDate: Installed on 2021-09-09 (153 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: gnome-bluetooth
  UpgradeStatus: Upgraded to jammy on 2022-01-13 (27 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2021-09-09 (160 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. G3 3579
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic 
root=UUID=fd3be223-e609-4a8d-97fb-31ee2f754766 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Tags:  jammy
  Uname: Linux 5.15.0-22-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-01-13 (34 days ago)
  UserGroups: adm bluetooth cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/20/2021
  dmi.bios.release: 1.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 0M5H57
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd04/20/2021:br1.15:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn0M5H57:rvrA05:cvnDellInc.:ct10:cvr:sku086F:
  dmi.product.family: GSeries
  dmi.product.name: G3 3579
  dmi.product.sku: 086F
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 98:2C:BC:33:92:E8  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:17341 acl:0 sco:0 events:2806 errors:0
TX bytes:689073 acl:0 sco:0 commands:2804 errors:0

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

[Ilia Kichev]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1960448/+attachment/5561598/+files/ProcCpuinfoMinimal.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/1960448

Title:
  Sony WF-XB700 Bluetooth headset not detected

Status in bluez package in Ubuntu:
  New
Status in gnome-bluetooth package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Gnome-bluetooth does not detect Sony WF-XB700 bluetooth headset.
  Installed blueman to try to figure out if this is related to gnome-
  bluetooth - the results are the same.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-bluetooth 3.34.5-4
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Feb  9 22:01:56 2022
  InstallationDate: Installed on 2021-09-09 (153 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: gnome-bluetooth
  UpgradeStatus: Upgraded to jammy on 2022-01-13 (27 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2021-09-09 (160 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. G3 3579
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic 
root=UUID=fd3be223-e609-4a8d-97fb-31ee2f754766 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Tags:  jammy
  Uname: Linux 5.15.0-22-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-01-13 (34 days ago)
  UserGroups: adm bluetooth cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/20/2021
  dmi.bios.release: 1.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 0M5H57
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd04/20/2021:br1.15:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn0M5H57:rvrA05:cvnDellInc.:ct10:cvr:sku086F:
  dmi.product.family: GSeries
  dmi.product.name: G3 3579
  dmi.product.sku: 086F
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 98:2C:BC:33:92:E8  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:17341 acl:0 sco:0 events:2806 errors:0
TX bytes:689073 acl:0 sco:0 commands:2804 errors:0

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

[Ilia Kichev]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1960448/+attachment/5561597/+files/ProcCpuinfo.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/1960448

Title:
  Sony WF-XB700 Bluetooth headset not detected

Status in bluez package in Ubuntu:
  New
Status in gnome-bluetooth package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Gnome-bluetooth does not detect Sony WF-XB700 bluetooth headset.
  Installed blueman to try to figure out if this is related to gnome-
  bluetooth - the results are the same.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-bluetooth 3.34.5-4
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Feb  9 22:01:56 2022
  InstallationDate: Installed on 2021-09-09 (153 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: gnome-bluetooth
  UpgradeStatus: Upgraded to jammy on 2022-01-13 (27 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2021-09-09 (160 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. G3 3579
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic 
root=UUID=fd3be223-e609-4a8d-97fb-31ee2f754766 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Tags:  jammy
  Uname: Linux 5.15.0-22-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-01-13 (34 days ago)
  UserGroups: adm bluetooth cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/20/2021
  dmi.bios.release: 1.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 0M5H57
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd04/20/2021:br1.15:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn0M5H57:rvrA05:cvnDellInc.:ct10:cvr:sku086F:
  dmi.product.family: GSeries
  dmi.product.name: G3 3579
  dmi.product.sku: 086F
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 98:2C:BC:33:92:E8  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:17341 acl:0 sco:0 events:2806 errors:0
TX bytes:689073 acl:0 sco:0 commands:2804 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1960448/+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 1960448] Lsusb-v.txt

[Ilia Kichev]

apport information

** Attachment added: "Lsusb-v.txt"
   
https://bugs.launchpad.net/bugs/1960448/+attachment/5561596/+files/Lsusb-v.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/1960448

Title:
  Sony WF-XB700 Bluetooth headset not detected

Status in bluez package in Ubuntu:
  New
Status in gnome-bluetooth package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Gnome-bluetooth does not detect Sony WF-XB700 bluetooth headset.
  Installed blueman to try to figure out if this is related to gnome-
  bluetooth - the results are the same.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-bluetooth 3.34.5-4
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Feb  9 22:01:56 2022
  InstallationDate: Installed on 2021-09-09 (153 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: gnome-bluetooth
  UpgradeStatus: Upgraded to jammy on 2022-01-13 (27 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2021-09-09 (160 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. G3 3579
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic 
root=UUID=fd3be223-e609-4a8d-97fb-31ee2f754766 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Tags:  jammy
  Uname: Linux 5.15.0-22-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-01-13 (34 days ago)
  UserGroups: adm bluetooth cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/20/2021
  dmi.bios.release: 1.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 0M5H57
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd04/20/2021:br1.15:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn0M5H57:rvrA05:cvnDellInc.:ct10:cvr:sku086F:
  dmi.product.family: GSeries
  dmi.product.name: G3 3579
  dmi.product.sku: 086F
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 98:2C:BC:33:92:E8  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:17341 acl:0 sco:0 events:2806 errors:0
TX bytes:689073 acl:0 sco:0 commands:2804 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1960448/+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 1960448] Lsusb-t.txt

[Ilia Kichev]

apport information

** Attachment added: "Lsusb-t.txt"
   
https://bugs.launchpad.net/bugs/1960448/+attachment/5561595/+files/Lsusb-t.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/1960448

Title:
  Sony WF-XB700 Bluetooth headset not detected

Status in bluez package in Ubuntu:
  New
Status in gnome-bluetooth package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Gnome-bluetooth does not detect Sony WF-XB700 bluetooth headset.
  Installed blueman to try to figure out if this is related to gnome-
  bluetooth - the results are the same.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-bluetooth 3.34.5-4
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Feb  9 22:01:56 2022
  InstallationDate: Installed on 2021-09-09 (153 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: gnome-bluetooth
  UpgradeStatus: Upgraded to jammy on 2022-01-13 (27 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2021-09-09 (160 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. G3 3579
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic 
root=UUID=fd3be223-e609-4a8d-97fb-31ee2f754766 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Tags:  jammy
  Uname: Linux 5.15.0-22-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-01-13 (34 days ago)
  UserGroups: adm bluetooth cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/20/2021
  dmi.bios.release: 1.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 0M5H57
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd04/20/2021:br1.15:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn0M5H57:rvrA05:cvnDellInc.:ct10:cvr:sku086F:
  dmi.product.family: GSeries
  dmi.product.name: G3 3579
  dmi.product.sku: 086F
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 98:2C:BC:33:92:E8  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:17341 acl:0 sco:0 events:2806 errors:0
TX bytes:689073 acl:0 sco:0 commands:2804 errors:0

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

[Ilia Kichev]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1960448/+attachment/5561594/+files/Lsusb.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/1960448

Title:
  Sony WF-XB700 Bluetooth headset not detected

Status in bluez package in Ubuntu:
  New
Status in gnome-bluetooth package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Gnome-bluetooth does not detect Sony WF-XB700 bluetooth headset.
  Installed blueman to try to figure out if this is related to gnome-
  bluetooth - the results are the same.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-bluetooth 3.34.5-4
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Feb  9 22:01:56 2022
  InstallationDate: Installed on 2021-09-09 (153 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: gnome-bluetooth
  UpgradeStatus: Upgraded to jammy on 2022-01-13 (27 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2021-09-09 (160 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. G3 3579
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic 
root=UUID=fd3be223-e609-4a8d-97fb-31ee2f754766 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Tags:  jammy
  Uname: Linux 5.15.0-22-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-01-13 (34 days ago)
  UserGroups: adm bluetooth cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/20/2021
  dmi.bios.release: 1.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 0M5H57
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd04/20/2021:br1.15:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn0M5H57:rvrA05:cvnDellInc.:ct10:cvr:sku086F:
  dmi.product.family: GSeries
  dmi.product.name: G3 3579
  dmi.product.sku: 086F
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 98:2C:BC:33:92:E8  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:17341 acl:0 sco:0 events:2806 errors:0
TX bytes:689073 acl:0 sco:0 commands:2804 errors:0

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

[Ilia Kichev]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1960448/+attachment/5561592/+files/Lspci.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/1960448

Title:
  Sony WF-XB700 Bluetooth headset not detected

Status in bluez package in Ubuntu:
  New
Status in gnome-bluetooth package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Gnome-bluetooth does not detect Sony WF-XB700 bluetooth headset.
  Installed blueman to try to figure out if this is related to gnome-
  bluetooth - the results are the same.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-bluetooth 3.34.5-4
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Feb  9 22:01:56 2022
  InstallationDate: Installed on 2021-09-09 (153 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: gnome-bluetooth
  UpgradeStatus: Upgraded to jammy on 2022-01-13 (27 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2021-09-09 (160 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. G3 3579
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic 
root=UUID=fd3be223-e609-4a8d-97fb-31ee2f754766 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Tags:  jammy
  Uname: Linux 5.15.0-22-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-01-13 (34 days ago)
  UserGroups: adm bluetooth cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/20/2021
  dmi.bios.release: 1.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 0M5H57
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd04/20/2021:br1.15:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn0M5H57:rvrA05:cvnDellInc.:ct10:cvr:sku086F:
  dmi.product.family: GSeries
  dmi.product.name: G3 3579
  dmi.product.sku: 086F
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 98:2C:BC:33:92:E8  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:17341 acl:0 sco:0 events:2806 errors:0
TX bytes:689073 acl:0 sco:0 commands:2804 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1960448/+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 1960448] Lspci-vt.txt

[Ilia Kichev]

apport information

** Attachment added: "Lspci-vt.txt"
   
https://bugs.launchpad.net/bugs/1960448/+attachment/5561593/+files/Lspci-vt.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/1960448

Title:
  Sony WF-XB700 Bluetooth headset not detected

Status in bluez package in Ubuntu:
  New
Status in gnome-bluetooth package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Gnome-bluetooth does not detect Sony WF-XB700 bluetooth headset.
  Installed blueman to try to figure out if this is related to gnome-
  bluetooth - the results are the same.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-bluetooth 3.34.5-4
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Feb  9 22:01:56 2022
  InstallationDate: Installed on 2021-09-09 (153 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: gnome-bluetooth
  UpgradeStatus: Upgraded to jammy on 2022-01-13 (27 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2021-09-09 (160 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. G3 3579
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic 
root=UUID=fd3be223-e609-4a8d-97fb-31ee2f754766 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Tags:  jammy
  Uname: Linux 5.15.0-22-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-01-13 (34 days ago)
  UserGroups: adm bluetooth cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/20/2021
  dmi.bios.release: 1.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 0M5H57
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd04/20/2021:br1.15:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn0M5H57:rvrA05:cvnDellInc.:ct10:cvr:sku086F:
  dmi.product.family: GSeries
  dmi.product.name: G3 3579
  dmi.product.sku: 086F
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 98:2C:BC:33:92:E8  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:17341 acl:0 sco:0 events:2806 errors:0
TX bytes:689073 acl:0 sco:0 commands:2804 errors:0

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

[Ilia Kichev]

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1960448/+attachment/5561591/+files/Dependencies.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/1960448

Title:
  Sony WF-XB700 Bluetooth headset not detected

Status in bluez package in Ubuntu:
  New
Status in gnome-bluetooth package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Gnome-bluetooth does not detect Sony WF-XB700 bluetooth headset.
  Installed blueman to try to figure out if this is related to gnome-
  bluetooth - the results are the same.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-bluetooth 3.34.5-4
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Feb  9 22:01:56 2022
  InstallationDate: Installed on 2021-09-09 (153 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: gnome-bluetooth
  UpgradeStatus: Upgraded to jammy on 2022-01-13 (27 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2021-09-09 (160 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. G3 3579
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic 
root=UUID=fd3be223-e609-4a8d-97fb-31ee2f754766 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Tags:  jammy
  Uname: Linux 5.15.0-22-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-01-13 (34 days ago)
  UserGroups: adm bluetooth cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/20/2021
  dmi.bios.release: 1.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 0M5H57
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd04/20/2021:br1.15:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn0M5H57:rvrA05:cvnDellInc.:ct10:cvr:sku086F:
  dmi.product.family: GSeries
  dmi.product.name: G3 3579
  dmi.product.sku: 086F
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 98:2C:BC:33:92:E8  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING 
RX bytes:17341 acl:0 sco:0 events:2806 errors:0
TX bytes:689073 acl:0 sco:0 commands:2804 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1960448/+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 1960448] Re: Sony WF-XB700 Bluetooth headset not detected

[Ilia Kichev]

apport information

** Tags added: apport-collected

** Description changed:

  Gnome-bluetooth does not detect Sony WF-XB700 bluetooth headset.
  Installed blueman to try to figure out if this is related to gnome-
  bluetooth - the results are the same.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-bluetooth 3.34.5-4
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Feb  9 22:01:56 2022
  InstallationDate: Installed on 2021-09-09 (153 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: gnome-bluetooth
  UpgradeStatus: Upgraded to jammy on 2022-01-13 (27 days ago)
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu76
+ Architecture: amd64
+ CasperMD5CheckResult: unknown
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 22.04
+ InstallationDate: Installed on 2021-09-09 (160 days ago)
+ InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
+ InterestingModules: rfcomm bnep btusb bluetooth
+ MachineType: Dell Inc. G3 3579
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: linux
+ PackageArchitecture: amd64
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic 
root=UUID=fd3be223-e609-4a8d-97fb-31ee2f754766 ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
+ Tags:  jammy
+ Uname: Linux 5.15.0-22-generic x86_64
+ UpgradeStatus: Upgraded to jammy on 2022-01-13 (34 days ago)
+ UserGroups: adm bluetooth cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 04/20/2021
+ dmi.bios.release: 1.15
+ dmi.bios.vendor: Dell Inc.
+ dmi.bios.version: 1.15.0
+ dmi.board.name: 0M5H57
+ dmi.board.vendor: Dell Inc.
+ dmi.board.version: A05
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: Dell Inc.
+ dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd04/20/2021:br1.15:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn0M5H57:rvrA05:cvnDellInc.:ct10:cvr:sku086F:
+ dmi.product.family: GSeries
+ dmi.product.name: G3 3579
+ dmi.product.sku: 086F
+ dmi.sys.vendor: Dell Inc.
+ hciconfig:
+  hci0:Type: Primary  Bus: USB
+   BD Address: 98:2C:BC:33:92:E8  ACL MTU: 1021:4  SCO MTU: 96:6
+   UP RUNNING 
+   RX bytes:17341 acl:0 sco:0 events:2806 errors:0
+   TX bytes:689073 acl:0 sco:0 commands:2804 errors:0

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1960448/+attachment/5561590/+files/CurrentDmesg.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/1960448

Title:
  Sony WF-XB700 Bluetooth headset not detected

Status in bluez package in Ubuntu:
  New
Status in gnome-bluetooth package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Gnome-bluetooth does not detect Sony WF-XB700 bluetooth headset.
  Installed blueman to try to figure out if this is related to gnome-
  bluetooth - the results are the same.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-bluetooth 3.34.5-4
  ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12
  Uname: Linux 5.15.0-18-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed Feb  9 22:01:56 2022
  InstallationDate: Installed on 2021-09-09 (153 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: gnome-bluetooth
  UpgradeStatus: Upgraded to jammy on 2022-01-13 (27 days ago)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu76
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2021-09-09 (160 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. G3 3579
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic 
root=UUID=fd3be223-e609-4a8d-97fb-31ee2f754766 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Tags:  jammy
  Uname: Linux 5.15.0-22-generic x86_64
  UpgradeStatus: Upgraded to jammy on 2022-01-13 (34 days ago)
  UserGroups: adm bluetooth cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/20/2021
  dmi.bios.release: 1.15
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.0
  dmi.board.name: 0M5H57
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.0:bd

[Touch-packages] [Bug 1960034] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for linux-hwe-5.13 has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  systemd/248.3-1ubuntu8.2 ADT test failure with linux/5.13.0-29.32

Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in linux source package in Impish:
  Fix Committed
Status in systemd source package in Impish:
  Invalid

Bug description:
  This is a scripted bug report about ADT failures while running systemd
  tests for linux/5.13.0-29.32 on impish. Whether this is caused by the
  dep8 tests of the tested source or the kernel has yet to be
  determined.

  Testing failed on:
  amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/s/systemd/20220204_114518_6b600@/log.gz
  arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/arm64/s/systemd/20220201_135548_7f169@/log.gz
  ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/s/systemd/20220201_110103_b02e4@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960034/+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 1960964] Re: Gather additional info when creating a bug about a snap

[Olivier Tilloy]

For reference, the chromium-browser package in focal and upwards is a
simple wrapper that installs the chromium snap, and it has a custom
apport hook that attaches some of this information. The names of the
keys there are:

 - Snap.Changes
 - Snap.Connections
 - Snap.Info.chromium
 - Snap.Info.core
 - Snap.Info.core18 (this needs to be updated because it is currently hardcoded 
in the hook, but the snap has since been rebased on core20)
 - Snap.Info.gtk-common-themes

See bug #1958810 for an example.

There isn't any tooling that expects these specific names though, so as
far as I'm concerned they can be changed.

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

Title:
  Gather additional info when creating a bug about a snap

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  On the ubuntu-devel mailing list[1] it was suggested that apport
  should collect the following additional information when reporting a
  bug about a snap:

- snap changes --abs-time $SNAPNAME 
 
- snap connections $SNAPNAME
 
- snap info --abs-time $SNAPNAME
 
- for PROVIDER in $(grep default-provider 
/snap/$SNAPNAME/current/meta/snap.yaml | uniq | cut -d: -f2); do snap info 
--abs-time $PROVIDER; done  
  
- snap info --abs-time $(grep base: /snap/$SNAPNAME/current/meta/snap.yaml 
| cut -d: -f2)  

  This should be fairly straightforward we just need to decide on names
  for the keys in the report.

  [1] https://lists.ubuntu.com/archives/ubuntu-
  devel/2022-February/041836.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1960964/+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 47958] Re: ssh-agent clobbers LD_LIBRARY_PATH and other environment variables

[Anders Kaseorg]

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

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

Title:
  ssh-agent clobbers LD_LIBRARY_PATH and other environment variables

Status in openssh package in Ubuntu:
  Confirmed
Status in openssh package in Debian:
  New

Bug description:
  Since /usr/bin/ssh-agent is setgid ssh, it unsets LD_LIBRARY_PATH.
  This made it impossible to set this variable in my dotfiles
  (.gnomerc).

  My solution was to write a wrapper script that prefixes the command with 
/usr/bin/env VAR=val ... for each variable that gets unset:


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