[Kernel-packages] [Bug 2004416] Re: Bluetooth Headset Loses Audio

2023-02-01 Thread Daniel van Vugt
The full set of messages related to this bug seems to be:

Jan 31 22:26:18 t935 wireplumber[1791]: 0x56370f33ca08: error 24
Jan 31 22:26:18 t935 wireplumber[1791]: RFCOMM write error: Connection reset by 
peer
Jan 31 22:26:18 t935 acpid[876]: input device has been disconnected, fd 18
Jan 31 22:26:18 t935 bluetoothd[885]: src/profile.c:ext_io_disconnected() 
Unable to get io data for Hands-Free Voice gateway: getpeername: Transport 
endpoint is not connected (107)
Jan 31 22:26:18 t935 wireplumber[1791]: (bluez_output.04_5D_4B_29_06_26.1-24) 
running -> error (Received error event)
Jan 31 22:26:18 t935 dbus-daemon[888]: [system] Rejected send message, 0 
matched rules; type="method_return", sender=":1.80" (uid=1000 pid=1791 
comm="/usr/bin/wireplumber" label="unconfined") interface="(unset)" 
member="(unset)" error name="(unset)" requested_reply="0" destination=":1.11" 
(uid=0 pid=885 comm="/usr/lib/bluetooth/bluetoothd" label="unconfined")
Jan 31 22:26:18 t935 pipewire[1789]: pw.node: 
(bluez_output.04_5D_4B_29_06_26.1-60) running -> error (Received error event)
Jan 31 22:26:18 t935 gsd-media-keys[2098]: Unable to get default sink

Although sometimes the first couple are missing. So it seems like a full
Bluetooth stack issue always starting in bluetoothd (BlueZ). That's not
to say it's definitely a software bug because it sounds like the headset
might have disconnected to begin with.

** Summary changed:

- Bluetooth Headset Loses Audio
+ Bluetooth Headset Loses Audio [pw.node: (bluez_output.04_5D_4B_29_06_26.1-80) 
running -> error (Received error event)]

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

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

** Attachment removed: "journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2004416/+attachment/5644345/+files/journal.txt

** Attachment removed: "journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2004416/+attachment/5644337/+files/journal.txt

** Attachment removed: "lspci.txt"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2004416/+attachment/5644338/+files/lspci.txt

** Attachment removed: "lsusb.txt"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2004416/+attachment/5644339/+files/lsusb.txt

** Attachment removed: "rfkill.txt"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2004416/+attachment/5644340/+files/rfkill.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2004416

Title:
  Bluetooth Headset Loses Audio [pw.node:
  (bluez_output.04_5D_4B_29_06_26.1-80) running -> error (Received error
  event)]

Status in bluez package in Ubuntu:
  New

Bug description:
  I keep finding that some time after connecting and listening to audio
  with my Bluetooth headset, the audio fails to play on them.  If I turn
  them off and back on again, it works.  So far, if I am listening, it
  doesn't quit, but if I stop and try to listen to audio again after a
  while, there is no sound.  This error in the logs prompted me to
  submit this bug to pipewire.

  pw.node: (bluez_output.04_5D_4B_29_06_26.1-80) running -> error
  (Received error event)

  I'd be happy to try and help debug this if you need me to try things.

  Rob

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: pipewire 0.3.58-2ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
  Uname: Linux 5.19.0-29-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 31 09:18:37 2023
  InstallationDate: Installed on 2021-05-25 (616 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pipewire
  UpgradeStatus: Upgraded to kinetic on 2022-10-26 (97 days ago)

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


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


[Kernel-packages] [Bug 2004531] Status changed to Confirmed

2023-02-01 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2004531

Title:
  Touchpad stops working after login when using latest kernel
  (5.15.0-58-generic)

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to the latest kernel (5.15.0-58-generic), my laptop’s
  touchpad has stopped working after the login screen. That is, it works
  on the login screen, but as soon as I log in (in fact, the moment I
  press enter after entering my password), the mouse cursor no longer
  responds to touchpad input. (I’ve made sure that my touchpad is
  enabled, both by using the touchpad enable/disable button on my
  laptop, and by checking in “Mouse Preferences” (Preferences → Mouse in
  the main menu) that the “Enable Touchpad” box is checked.) The mouse
  buttons below the touchpad, however, still work, and if I plug in a
  USB mouse, that will work as well.

  When I restart and select the previous kernel version
  (5.15.0-57-generic) on boot, the touchpad works again, on the login
  screen and after. Nevertheless, I’d really appreciate a fix; this
  laptop is dear to me, and I’d like to be able to use it with the
  latest kernel updates.

  I’m using Ubuntu MATE 22.04.01 LTS on a Compaq Presario CQ60.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-58-generic 5.15.0-58.64
  ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
  Uname: Linux 5.15.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tina   2670 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: MATE
  Date: Wed Feb  1 18:36:00 2023
  HibernationDevice: RESUME=UUID=3e371ef8-1061-4c6d-b9ab-a072575893c9
  InstallationDate: Installed on 2018-05-24 (1715 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: Hewlett-Packard Compaq Presario CQ60 Notebook PC
  ProcFB: 0 nouveaudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic 
root=UUID=1e6f5cc4-d098-4aaa-9a26-4f3808cfd68d ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-58-generic N/A
   linux-backports-modules-5.15.0-58-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.9
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2023-01-11 (21 days ago)
  dmi.bios.date: 02/04/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.33
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 3617
  dmi.board.vendor: Wistron
  dmi.board.version: 09.48
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Wistron
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.33:bd02/04/2009:svnHewlett-Packard:pnCompaqPresarioCQ60NotebookPC:pvrF.33:rvnWistron:rn3617:rvr09.48:cvnWistron:ct10:cvrChassisVersion:skuNL058PA#AB2:
  dmi.product.family: 103C_5335KV
  dmi.product.name: Compaq Presario CQ60 Notebook PC
  dmi.product.sku: NL058PA#AB2
  dmi.product.version: F.33
  dmi.sys.vendor: Hewlett-Packard

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


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


[Kernel-packages] [Bug 2004416] Re: [rtl8822be] Bluetooth Headset Loses Audio

2023-02-01 Thread Daniel van Vugt
Thanks. Please ensure you only provide logs from the machine the bug is
about in future.


** Summary changed:

- [rtl8822be] Bluetooth Headset Loses Audio
+ Bluetooth Headset Loses Audio

** Tags removed: rtl8822be

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2004416

Title:
  Bluetooth Headset Loses Audio [pw.node:
  (bluez_output.04_5D_4B_29_06_26.1-80) running -> error (Received error
  event)]

Status in bluez package in Ubuntu:
  New

Bug description:
  I keep finding that some time after connecting and listening to audio
  with my Bluetooth headset, the audio fails to play on them.  If I turn
  them off and back on again, it works.  So far, if I am listening, it
  doesn't quit, but if I stop and try to listen to audio again after a
  while, there is no sound.  This error in the logs prompted me to
  submit this bug to pipewire.

  pw.node: (bluez_output.04_5D_4B_29_06_26.1-80) running -> error
  (Received error event)

  I'd be happy to try and help debug this if you need me to try things.

  Rob

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: pipewire 0.3.58-2ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
  Uname: Linux 5.19.0-29-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 31 09:18:37 2023
  InstallationDate: Installed on 2021-05-25 (616 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pipewire
  UpgradeStatus: Upgraded to kinetic on 2022-10-26 (97 days ago)

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


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


[Kernel-packages] [Bug 2004416] Re: [rtl8822be] Bluetooth Headset Loses Audio

2023-02-01 Thread Rob Frohne
Your comment about RFI on 2.4GHz may be right on.  I recently got
hearing aids (Phonak Marvel M70-R) and they use Bluetooth too.  They
were on the same ears as my headset.  The problems have been happening
about as long as I have had the hearing aids.  I'll try and do some
testing next time to see if I can figure out if they are partly or
wholly to blame.  It is an intermittent problem.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2004416

Title:
  Bluetooth Headset Loses Audio [pw.node:
  (bluez_output.04_5D_4B_29_06_26.1-80) running -> error (Received error
  event)]

Status in bluez package in Ubuntu:
  New

Bug description:
  I keep finding that some time after connecting and listening to audio
  with my Bluetooth headset, the audio fails to play on them.  If I turn
  them off and back on again, it works.  So far, if I am listening, it
  doesn't quit, but if I stop and try to listen to audio again after a
  while, there is no sound.  This error in the logs prompted me to
  submit this bug to pipewire.

  pw.node: (bluez_output.04_5D_4B_29_06_26.1-80) running -> error
  (Received error event)

  I'd be happy to try and help debug this if you need me to try things.

  Rob

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: pipewire 0.3.58-2ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
  Uname: Linux 5.19.0-29-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 31 09:18:37 2023
  InstallationDate: Installed on 2021-05-25 (616 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pipewire
  UpgradeStatus: Upgraded to kinetic on 2022-10-26 (97 days ago)

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


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


[Kernel-packages] [Bug 2004531] [NEW] Touchpad stops working after login when using latest kernel (5.15.0-58-generic)

2023-02-01 Thread Tina Russell
Public bug reported:

After upgrading to the latest kernel (5.15.0-58-generic), my laptop’s
touchpad has stopped working after the login screen. That is, it works
on the login screen, but as soon as I log in (in fact, the moment I
press enter after entering my password), the mouse cursor no longer
responds to touchpad input. (I’ve made sure that my touchpad is enabled,
both by using the touchpad enable/disable button on my laptop, and by
checking in “Mouse Preferences” (Preferences → Mouse in the main menu)
that the “Enable Touchpad” box is checked.) The mouse buttons below the
touchpad, however, still work, and if I plug in a USB mouse, that will
work as well.

When I restart and select the previous kernel version
(5.15.0-57-generic) on boot, the touchpad works again, on the login
screen and after. Nevertheless, I’d really appreciate a fix; this laptop
is dear to me, and I’d like to be able to use it with the latest kernel
updates.

I’m using Ubuntu MATE 22.04.01 LTS on a Compaq Presario CQ60.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-58-generic 5.15.0-58.64
ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
Uname: Linux 5.15.0-58-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  tina   2670 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: MATE
Date: Wed Feb  1 18:36:00 2023
HibernationDevice: RESUME=UUID=3e371ef8-1061-4c6d-b9ab-a072575893c9
InstallationDate: Installed on 2018-05-24 (1715 days ago)
InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
MachineType: Hewlett-Packard Compaq Presario CQ60 Notebook PC
ProcFB: 0 nouveaudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic 
root=UUID=1e6f5cc4-d098-4aaa-9a26-4f3808cfd68d ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-58-generic N/A
 linux-backports-modules-5.15.0-58-generic  N/A
 linux-firmware 20220329.git681281e4-0ubuntu3.9
SourcePackage: linux
UpgradeStatus: Upgraded to jammy on 2023-01-11 (21 days ago)
dmi.bios.date: 02/04/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.33
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 3617
dmi.board.vendor: Wistron
dmi.board.version: 09.48
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Wistron
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.33:bd02/04/2009:svnHewlett-Packard:pnCompaqPresarioCQ60NotebookPC:pvrF.33:rvnWistron:rn3617:rvr09.48:cvnWistron:ct10:cvrChassisVersion:skuNL058PA#AB2:
dmi.product.family: 103C_5335KV
dmi.product.name: Compaq Presario CQ60 Notebook PC
dmi.product.sku: NL058PA#AB2
dmi.product.version: F.33
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apport-bug jammy

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2004531

Title:
  Touchpad stops working after login when using latest kernel
  (5.15.0-58-generic)

Status in linux package in Ubuntu:
  New

Bug description:
  After upgrading to the latest kernel (5.15.0-58-generic), my laptop’s
  touchpad has stopped working after the login screen. That is, it works
  on the login screen, but as soon as I log in (in fact, the moment I
  press enter after entering my password), the mouse cursor no longer
  responds to touchpad input. (I’ve made sure that my touchpad is
  enabled, both by using the touchpad enable/disable button on my
  laptop, and by checking in “Mouse Preferences” (Preferences → Mouse in
  the main menu) that the “Enable Touchpad” box is checked.) The mouse
  buttons below the touchpad, however, still work, and if I plug in a
  USB mouse, that will work as well.

  When I restart and select the previous kernel version
  (5.15.0-57-generic) on boot, the touchpad works again, on the login
  screen and after. Nevertheless, I’d really appreciate a fix; this
  laptop is dear to me, and I’d like to be able to use it with the
  latest kernel updates.

  I’m using Ubuntu MATE 22.04.01 LTS on a Compaq Presario CQ60.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-58-generic 5.15.0-58.64
  ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
  Uname: Linux 5.15.0-58-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  tina   2670 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: MATE
  Date: Wed Feb  1 18:36:00 2023
  HibernationDevice: RESUME=UUID=3e371ef8-1061-4c6d-b9ab-a072575893c9
  InstallationDate: Installed on 2018-05-24 (1715 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: 

Re: [Kernel-packages] [Bug 2003836] Re: package linux-lowlatency-tools-5.19.0-1016 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/libcpupower.so.5.19.0-1016', which is also i

2023-02-01 Thread SanDiego California University
Thank you! Dankeshon

Em qua, 25 de jan de 2023 03:55, Apport retracing service <
2003...@bugs.launchpad.net> escreveu:

> ** Tags removed: need-duplicate-check
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2003836
>
> Title:
>   package linux-lowlatency-tools-5.19.0-1016 (not installed) failed to
>   install/upgrade: trying to overwrite
>   '/usr/lib/libcpupower.so.5.19.0-1016', which is also in package linux-
>   oracle-tools-5.19.0-1016 5.19.0-1016.18
>
> Status in linux-lowlatency package in Ubuntu:
>   New
>
> Bug description:
>   Building dependency tree... Done
>   Reading state information... Done
>   You might want to run 'apt --fix-broken install' to correct these.
>   The following packages have unmet dependencies:
>linux-tools-5.19.0-1016-lowlatency : Depends:
> linux-lowlatency-tools-5.19.0-1016 but it is not going to be installed
>linux-tools-oem-22.04a : Depends: linux-tools-5.17.0-1003-oem but it is
> not going to be installed
>   E: Unmet dependencies. Try 'apt --fix-broken install' with no packages
> (or specify a solution).
>   hlt@hlt-IdeaPad-Gaming-3-15IMH05:~$
>
>   ProblemType: Package
>   DistroRelease: Ubuntu 22.10
>   Package: linux-lowlatency-tools-5.19.0-1016 (not installed)
>   ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17
>   Uname: Linux 5.19.0-31-generic x86_64
>   ApportVersion: 2.23.1-0ubuntu3
>   AptOrdering:
>linux-lowlatency-tools-5.19.0-1016:amd64: Install
>linux-tools-5.19.0-1016-lowlatency:amd64: Install
>linux-tools-lowlatency-hwe-22.04-edge:amd64: Install
>NULL: ConfigurePending
>   Architecture: amd64
>   CasperMD5CheckResult: pass
>   Date: Wed Jan 25 02:39:17 2023
>   DpkgTerminalLog:
>Preparing to unpack
> .../linux-lowlatency-tools-5.19.0-1016_5.19.0-1016.17_amd64.deb ...
>Unpacking linux-lowlatency-tools-5.19.0-1016 (5.19.0-1016.17) ...
>dpkg: error processing archive
> /var/cache/apt/archives/linux-lowlatency-tools-5.19.0-1016_5.19.0-1016.17_amd64.deb
> (--unpack):
> trying to overwrite '/usr/lib/libcpupower.so.5.19.0-1016', which is
> also in package linux-oracle-tools-5.19.0-1016 5.19.0-1016.18
>   DuplicateSignature:
>package:linux-lowlatency-tools-5.19.0-1016:(not installed)
>Unpacking linux-lowlatency-tools-5.19.0-1016 (5.19.0-1016.17) ...
>dpkg: error processing archive
> /var/cache/apt/archives/linux-lowlatency-tools-5.19.0-1016_5.19.0-1016.17_amd64.deb
> (--unpack):
> trying to overwrite '/usr/lib/libcpupower.so.5.19.0-1016', which is
> also in package linux-oracle-tools-5.19.0-1016 5.19.0-1016.18
>   ErrorMessage: trying to overwrite '/usr/lib/libcpupower.so.5.19.0-1016',
> which is also in package linux-oracle-tools-5.19.0-1016 5.19.0-1016.18
>   InstallationDate: Installed on 2023-01-24 (0 days ago)
>   InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
>   Python3Details: /usr/bin/python3.10, Python 3.10.7, python3-minimal,
> 3.10.6-1
>   PythonDetails: N/A
>   RebootRequiredPkgs: Error: path contained symlinks.
>   RelatedPackageVersions:
>dpkg 1.21.9ubuntu1
>apt  2.5.3ubuntu0.1
>   SourcePackage: linux-lowlatency
>   Title: package linux-lowlatency-tools-5.19.0-1016 (not installed) failed
> to install/upgrade: trying to overwrite
> '/usr/lib/libcpupower.so.5.19.0-1016', which is also in package
> linux-oracle-tools-5.19.0-1016 5.19.0-1016.18
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/linux-lowlatency/+bug/2003836/+subscriptions
>
>

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-lowlatency in Ubuntu.
https://bugs.launchpad.net/bugs/2003836

Title:
  package linux-lowlatency-tools-5.19.0-1016 (not installed) failed to
  install/upgrade: trying to overwrite
  '/usr/lib/libcpupower.so.5.19.0-1016', which is also in package linux-
  oracle-tools-5.19.0-1016 5.19.0-1016.18

Status in linux-lowlatency package in Ubuntu:
  New

Bug description:
  Building dependency tree... Done
  Reading state information... Done
  You might want to run 'apt --fix-broken install' to correct these.
  The following packages have unmet dependencies:
   linux-tools-5.19.0-1016-lowlatency : Depends: 
linux-lowlatency-tools-5.19.0-1016 but it is not going to be installed
   linux-tools-oem-22.04a : Depends: linux-tools-5.17.0-1003-oem but it is not 
going to be installed
  E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or 
specify a solution).
  hlt@hlt-IdeaPad-Gaming-3-15IMH05:~$

  ProblemType: Package
  DistroRelease: Ubuntu 22.10
  Package: linux-lowlatency-tools-5.19.0-1016 (not installed)
  ProcVersionSignature: Ubuntu 5.19.0-31.32-generic 5.19.17
  Uname: Linux 5.19.0-31-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  AptOrdering:
   linux-lowlatency-tools-5.19.0-1016:amd64: 

Re: [Kernel-packages] [Bug 2003838] Re: package linux-lowlatency-tools-5.19.0-1016 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/libcpupower.so.5.19.0-1016', which is also i

2023-02-01 Thread SanDiego California University
*** This bug is a duplicate of bug 2003836 ***
https://bugs.launchpad.net/bugs/2003836

That mess.. fire that file manager tdha Guy. Dummie ppl. From Isle of
Isabelle Drummond

Em qui, 26 de jan de 2023 01:40, Seth Arnold <2003...@bugs.launchpad.net>
escreveu:

> ** Information type changed from Private Security to Public
>
> ** Also affects: linux (Ubuntu)
>Importance: Undecided
>Status: New
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/2003838
>
> Title:
>   package linux-lowlatency-tools-5.19.0-1016 (not installed) failed to
>   install/upgrade: trying to overwrite
>   '/usr/lib/libcpupower.so.5.19.0-1016', which is also in package linux-
>   oracle-tools-5.19.0-1016 5.19.0-1016.18
>
> Status in linux package in Ubuntu:
>   New
> Status in linux-lowlatency package in Ubuntu:
>   New
>
> Bug description:
>   1 hlt hlt5 jan 24 19:15 user-dirs.locale
>   -rw-rw-r--  1 hlt hlt   36 jan 24 19:15 user-dirs.locale.md5sum
>
>   ./snap/snapd-desktop-integration/14/.config/dconf:
>   total 8
>   drwxrwxr-x 2 hlt hlt 4096 jan 24 19:56 .
>   drwx-- 7 hlt hlt 4096 jan 24 19:56 ..
>   lrwxrwxrwx 1 hlt hlt   28 jan 24 19:56 user ->
> /home/hlt/.config/dconf/user
>
>   ./snap/snapd-desktop-integration/14/.config/fontconfig:
>   total 12
>   drwxrwxr-x 2 hlt hlt 4096 jan 24 19:15 .
>   drwx-- 7 hlt hlt 4096 jan 24 19:56 ..
>   -rw-rw-r-- 1 hlt hlt  407 jan 24 19:15 fonts.conf
>
>   ./snap/snapd-desktop-integration/14/.config/gtk-2.0:
>   total 8
>   drwxrwxr-x 2 hlt hlt 4096 jan 24 19:15 .
>   drwx-- 7 hlt hlt 4096 jan 24 19:56 ..
>   lrwxrwxrwx 1 hlt hlt   44 jan 24 19:15 gtkfilechooser.ini ->
> /home/hlt/.config/gtk-2.0/gtkfilechooser.ini
>
>   ./snap/snapd-desktop-integration/14/.config/gtk-3.0:
>   total 8
>   drwxrwxr-x 2 hlt hlt 4096 jan 24 19:15 .
>   drwx-- 7 hlt hlt 4096 jan 24 19:56 ..
>   lrwxrwxrwx 1 hlt hlt   35 jan 24 19:15 bookmarks ->
> /home/hlt/.config/gtk-3.0/bookmarks
>   lrwxrwxrwx 1 hlt hlt   38 jan 24 19:15 settings.ini ->
> /home/hlt/.config/gtk-3.0/settings.ini
>
>   ./snap/snapd-desktop-integration/14/.config/ibus:
>   total 8
>   drwxrwxr-x 2 hlt hlt 4096 jan 25 02:10 .
>   drwx-- 7 hlt hlt 4096 jan 24 19:56 ..
>   lrwxrwxrwx 1 hlt hlt   26 jan 25 02:10 bus -> /home/hlt/.config/ibus/bus
>
>   ./snap/snapd-desktop-integration/14/Desktop:
>   total 8
>   drwxr-xr-x  2 hlt hlt 4096 jan 24 19:15 .
>   drwxr-xr-x 10 hlt hlt 4096 jan 24 19:15 ..
>
>   ./snap/snapd-desktop-integration/14/Documents:
>   total 8
>   drwxr-xr-x  2 hlt hlt 4096 jan 24 19:15 .
>   drwxr-xr-x 10 hlt hlt 4096 jan 24 19:15 ..
>
>   ./snap/snapd-desktop-integration/14/Downloads:
>   total 8
>   drwxr-xr-x  2 hlt hlt 4096 jan 24 19:15 .
>   drwxr-xr-x 10 hlt hlt 4096 jan 24 19:15 ..
>
>   ./snap/snapd-desktop-integration/14/.local:
>   total 12
>   drwxrwxr-x  3 hlt hlt 4096 jan 24 19:15 .
>   drwxr-xr-x 10 hlt hlt 4096 jan 24 19:15 ..
>   drwxrwxr-x  4 hlt hlt 4096 jan 24 19:15 share
>
>   ./snap/snapd-desktop-integration/14/.local/share:
>   total 16
>   drwxrwxr-x 4 hlt hlt 4096 jan 24 19:15 .
>   drwxrwxr-x 3 hlt hlt 4096 jan 24 19:15 ..
>   drwxrwxr-x 3 hlt hlt 4096 jan 24 19:15 glib-2.0
>   drwxrwxr-x 2 hlt hlt 4096 jan 24 19:15 icons
>   lrwxrwxrwx 1 hlt hlt   50 jan 24 19:15 themes ->
> /snap/snapd-desktop-integration/14/data-dir/themes
>
>   ./snap/snapd-desktop-integration/14/.local/share/glib-2.0:
>   total 12
>   drwxrwxr-x 3 hlt hlt 4096 jan 24 19:15 .
>   drwxrwxr-x 4 hlt hlt 4096 jan 24 19:15 ..
>   drwxrwxr-x 2 hlt hlt 4096 jan 24 19:15 schemas
>
>   ./snap/snapd-desktop-integration/14/.local/share/glib-2.0/schemas:
>   total 8
>   drwxrwxr-x 2 hlt hlt 4096 jan 24 19:15 .
>   drwxrwxr-x 3 hlt hlt 4096 jan 24 19:15 ..
>
>   ./snap/snapd-desktop-integration/14/.local/share/icons:
>   total 8
>   drwxrwxr-x 2 hlt hlt 4096 jan 24 19:15 .
>   drwxrwxr-x 4 hlt hlt 4096 jan 24 19:15 ..
>
>   ./snap/snapd-desktop-integration/14/Music:
>   total 8
>   drwxr-xr-x  2 hlt hlt 4096 jan 24 19:15 .
>   drwxr-xr-x 10 hlt hlt 4096 jan 24 19:15 ..
>
>   ./snap/snapd-desktop-integration/14/Pictures:
>   total 8
>   drwxr-xr-x  2 hlt hlt 4096 jan 24 19:15 .
>   drwxr-xr-x 10 hlt hlt 4096 jan 24 19:15 ..
>
>   ./snap/snapd-desktop-integration/14/Videos:
>   total 8
>   drwxr-xr-x  2 hlt hlt 4096 jan 24 19:15 .
>   drwxr-xr-x 10 hlt hlt 4096 jan 24 19:15 ..
>
>   ./snap/snapd-desktop-integration/49:
>   total 44
>   drwxr-xr-x 10 hlt hlt 4096 jan 25 02:16 .
>   drwxr-xr-x  5 hlt hlt 4096 jan 25 02:16 ..
>   drwx--  7 hlt hlt 4096 jan 24 19:56 .config
>   drwxr-xr-x  2 hlt hlt 4096 jan 24 19:15 Desktop
>   drwxr-xr-x  2 hlt hlt 4096 jan 24 19:15 Documents
>   drwxr-xr-x  2 hlt hlt 4096 jan 24 19:15 Downloads
>   -rw-rw-r--  1 hlt hlt   30 jan 25 02:16 .last_revision
>   drwxrwxr-x  3 hlt hlt 4096 jan 24 19:15 .local
>   drwxr-xr-x  2 hlt hlt 4096 jan 24 19:15 Music
>   drwxr-xr-x  2 hlt hlt 4096 jan 24 19:15 

[Kernel-packages] [Bug 2004416] Re: [rtl8822be] Bluetooth Headset Loses Audio

2023-02-01 Thread Rob Frohne
and rfkill.

** Attachment added: "rfkill_correct.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004416/+attachment/5644349/+files/rfkill_correct.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2004416

Title:
  [rtl8822be] Bluetooth Headset Loses Audio

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I keep finding that some time after connecting and listening to audio
  with my Bluetooth headset, the audio fails to play on them.  If I turn
  them off and back on again, it works.  So far, if I am listening, it
  doesn't quit, but if I stop and try to listen to audio again after a
  while, there is no sound.  This error in the logs prompted me to
  submit this bug to pipewire.

  pw.node: (bluez_output.04_5D_4B_29_06_26.1-80) running -> error
  (Received error event)

  I'd be happy to try and help debug this if you need me to try things.

  Rob

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: pipewire 0.3.58-2ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
  Uname: Linux 5.19.0-29-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 31 09:18:37 2023
  InstallationDate: Installed on 2021-05-25 (616 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pipewire
  UpgradeStatus: Upgraded to kinetic on 2022-10-26 (97 days ago)

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


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


[Kernel-packages] [Bug 2004416] Re: [rtl8822be] Bluetooth Headset Loses Audio

2023-02-01 Thread Rob Frohne
and the lspci...

** Attachment added: "lspci_correct.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004416/+attachment/5644347/+files/lspci_correct.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2004416

Title:
  [rtl8822be] Bluetooth Headset Loses Audio

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I keep finding that some time after connecting and listening to audio
  with my Bluetooth headset, the audio fails to play on them.  If I turn
  them off and back on again, it works.  So far, if I am listening, it
  doesn't quit, but if I stop and try to listen to audio again after a
  while, there is no sound.  This error in the logs prompted me to
  submit this bug to pipewire.

  pw.node: (bluez_output.04_5D_4B_29_06_26.1-80) running -> error
  (Received error event)

  I'd be happy to try and help debug this if you need me to try things.

  Rob

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: pipewire 0.3.58-2ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
  Uname: Linux 5.19.0-29-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 31 09:18:37 2023
  InstallationDate: Installed on 2021-05-25 (616 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pipewire
  UpgradeStatus: Upgraded to kinetic on 2022-10-26 (97 days ago)

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


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


[Kernel-packages] [Bug 2004416] Re: [rtl8822be] Bluetooth Headset Loses Audio

2023-02-01 Thread Rob Frohne
and the lsusb...

** Attachment added: "lsusb_correct.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004416/+attachment/5644348/+files/lsusb_correct.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2004416

Title:
  [rtl8822be] Bluetooth Headset Loses Audio

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I keep finding that some time after connecting and listening to audio
  with my Bluetooth headset, the audio fails to play on them.  If I turn
  them off and back on again, it works.  So far, if I am listening, it
  doesn't quit, but if I stop and try to listen to audio again after a
  while, there is no sound.  This error in the logs prompted me to
  submit this bug to pipewire.

  pw.node: (bluez_output.04_5D_4B_29_06_26.1-80) running -> error
  (Received error event)

  I'd be happy to try and help debug this if you need me to try things.

  Rob

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: pipewire 0.3.58-2ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
  Uname: Linux 5.19.0-29-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 31 09:18:37 2023
  InstallationDate: Installed on 2021-05-25 (616 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pipewire
  UpgradeStatus: Upgraded to kinetic on 2022-10-26 (97 days ago)

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


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


[Kernel-packages] [Bug 2004416] Re: [rtl8822be] Bluetooth Headset Loses Audio

2023-02-01 Thread Rob Frohne
So sorry!  I really messed up.  The original laptop is a Fujitsu and the
one I did the testing on above was a Thinkpad.  Here are the correct
files for the original bug.

** Attachment added: "journal_correct.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004416/+attachment/5644346/+files/journal_correct.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2004416

Title:
  [rtl8822be] Bluetooth Headset Loses Audio

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I keep finding that some time after connecting and listening to audio
  with my Bluetooth headset, the audio fails to play on them.  If I turn
  them off and back on again, it works.  So far, if I am listening, it
  doesn't quit, but if I stop and try to listen to audio again after a
  while, there is no sound.  This error in the logs prompted me to
  submit this bug to pipewire.

  pw.node: (bluez_output.04_5D_4B_29_06_26.1-80) running -> error
  (Received error event)

  I'd be happy to try and help debug this if you need me to try things.

  Rob

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: pipewire 0.3.58-2ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
  Uname: Linux 5.19.0-29-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 31 09:18:37 2023
  InstallationDate: Installed on 2021-05-25 (616 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pipewire
  UpgradeStatus: Upgraded to kinetic on 2022-10-26 (97 days ago)

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


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


[Kernel-packages] [Bug 2004416] Re: [rtl8822be] Bluetooth Headset Loses Audio

2023-02-01 Thread Rob Frohne
The original journal goes back to before when I'm sure the original
problem was occurring.  The interesting thing is that this has been
working for a while, and I only noticed the problem fairly recently
(probably the last month).  The new problem (not reported yet elsewhere)
is a different headset and different laptop, but I kind of think I
remember it happening on it as well.  And this makes me remember that
the journal, etc I sent you were on the wrong laptop!  So sorry!  Let me
get you the right ones.

Rob

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2004416

Title:
  [rtl8822be] Bluetooth Headset Loses Audio

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I keep finding that some time after connecting and listening to audio
  with my Bluetooth headset, the audio fails to play on them.  If I turn
  them off and back on again, it works.  So far, if I am listening, it
  doesn't quit, but if I stop and try to listen to audio again after a
  while, there is no sound.  This error in the logs prompted me to
  submit this bug to pipewire.

  pw.node: (bluez_output.04_5D_4B_29_06_26.1-80) running -> error
  (Received error event)

  I'd be happy to try and help debug this if you need me to try things.

  Rob

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: pipewire 0.3.58-2ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
  Uname: Linux 5.19.0-29-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 31 09:18:37 2023
  InstallationDate: Installed on 2021-05-25 (616 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pipewire
  UpgradeStatus: Upgraded to kinetic on 2022-10-26 (97 days ago)

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


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


[Kernel-packages] [Bug 2004416] Re: [rtl8822be] Bluetooth Headset Loses Audio

2023-02-01 Thread Rob Frohne
Here is a more recent journalctl (after re-pairing, and connecting
successfully so I could watch some youtube.  :-)

** Attachment added: "journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2004416/+attachment/5644345/+files/journal.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2004416

Title:
  [rtl8822be] Bluetooth Headset Loses Audio

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I keep finding that some time after connecting and listening to audio
  with my Bluetooth headset, the audio fails to play on them.  If I turn
  them off and back on again, it works.  So far, if I am listening, it
  doesn't quit, but if I stop and try to listen to audio again after a
  while, there is no sound.  This error in the logs prompted me to
  submit this bug to pipewire.

  pw.node: (bluez_output.04_5D_4B_29_06_26.1-80) running -> error
  (Received error event)

  I'd be happy to try and help debug this if you need me to try things.

  Rob

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: pipewire 0.3.58-2ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
  Uname: Linux 5.19.0-29-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 31 09:18:37 2023
  InstallationDate: Installed on 2021-05-25 (616 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pipewire
  UpgradeStatus: Upgraded to kinetic on 2022-10-26 (97 days ago)

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


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


[Kernel-packages] [Bug 2004416] Re: [rtl8822be] Bluetooth Headset Loses Audio

2023-02-01 Thread Daniel van Vugt
Please also try eliminating sources of 2.4GHz interference such as wifi
networks. Changing your network and devices to use 5GHz instead should
help to avoid interfering with Bluetooth which is around 2.4GHz.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2004416

Title:
  [rtl8822be] Bluetooth Headset Loses Audio

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I keep finding that some time after connecting and listening to audio
  with my Bluetooth headset, the audio fails to play on them.  If I turn
  them off and back on again, it works.  So far, if I am listening, it
  doesn't quit, but if I stop and try to listen to audio again after a
  while, there is no sound.  This error in the logs prompted me to
  submit this bug to pipewire.

  pw.node: (bluez_output.04_5D_4B_29_06_26.1-80) running -> error
  (Received error event)

  I'd be happy to try and help debug this if you need me to try things.

  Rob

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: pipewire 0.3.58-2ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
  Uname: Linux 5.19.0-29-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 31 09:18:37 2023
  InstallationDate: Installed on 2021-05-25 (616 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pipewire
  UpgradeStatus: Upgraded to kinetic on 2022-10-26 (97 days ago)

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


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


[Kernel-packages] [Bug 2004416] Re: Bluetooth Headset Loses Audio

2023-02-01 Thread Daniel van Vugt
It sounds like the log in comment #3 is now describing a new bug instead
of the original bug here. Please ensure you provide a log from when the
original bug occurred.

What I can see in the log is that the Realtek kernel driver (and
possibly the hardware) has failed just before Bluetooth audio has
problems. So it seems likely the issues are originating in the hardware
or in the kernel driver and we don't need to track this in pipewire.

Unfortunately the next step I would recommend here would be to try a USB
dongle that contains an Intel Wifi+Bluetooth chip instead. I know that's
annoying but if the Realtek hardware or kernel driver is buggy then
that's something Canonical can't fix.

You might be able to get around the problem in software however, by
trying a newer (or even an older) kernel.

** Summary changed:

- Bluetooth Headset Loses Audio
+ [rtl8822be] Bluetooth Headset Loses Audio

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2004416

Title:
  [rtl8822be] Bluetooth Headset Loses Audio

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I keep finding that some time after connecting and listening to audio
  with my Bluetooth headset, the audio fails to play on them.  If I turn
  them off and back on again, it works.  So far, if I am listening, it
  doesn't quit, but if I stop and try to listen to audio again after a
  while, there is no sound.  This error in the logs prompted me to
  submit this bug to pipewire.

  pw.node: (bluez_output.04_5D_4B_29_06_26.1-80) running -> error
  (Received error event)

  I'd be happy to try and help debug this if you need me to try things.

  Rob

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: pipewire 0.3.58-2ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
  Uname: Linux 5.19.0-29-generic x86_64
  ApportVersion: 2.23.1-0ubuntu3
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 31 09:18:37 2023
  InstallationDate: Installed on 2021-05-25 (616 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pipewire
  UpgradeStatus: Upgraded to kinetic on 2022-10-26 (97 days ago)

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


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


[Kernel-packages] [Bug 2004416] [NEW] [rtl8822be] Bluetooth Headset Loses Audio

2023-02-01 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I keep finding that some time after connecting and listening to audio
with my Bluetooth headset, the audio fails to play on them.  If I turn
them off and back on again, it works.  So far, if I am listening, it
doesn't quit, but if I stop and try to listen to audio again after a
while, there is no sound.  This error in the logs prompted me to submit
this bug to pipewire.

pw.node: (bluez_output.04_5D_4B_29_06_26.1-80) running -> error
(Received error event)

I'd be happy to try and help debug this if you need me to try things.

Rob

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: pipewire 0.3.58-2ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-29.30-generic 5.19.17
Uname: Linux 5.19.0-29-generic x86_64
ApportVersion: 2.23.1-0ubuntu3
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Jan 31 09:18:37 2023
InstallationDate: Installed on 2021-05-25 (616 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: pipewire
UpgradeStatus: Upgraded to kinetic on 2022-10-26 (97 days ago)

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


** Tags: amd64 apport-bug kinetic rtl8822be wayland-session
-- 
[rtl8822be] Bluetooth Headset Loses Audio
https://bugs.launchpad.net/bugs/2004416
You received this bug notification because you are a member of Kernel Packages, 
which is subscribed to linux in Ubuntu.

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


[Kernel-packages] [Bug 2000778] Re: pmtu.sh in net from ubunut_kernel_selftests crash SUT with K-5.19

2023-02-01 Thread Luke Nowakowski-Krijger
looks like a similar stack trace found here
https://www.spinics.net/lists/kernel/msg4555769.html

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2000778

Title:
  pmtu.sh in net from ubunut_kernel_selftests crash SUT with K-5.19

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in linux source package in Kinetic:
  Incomplete

Bug description:
  Issue found with Kinetic 5.19.0-27.28 and 5.19.0-28.29 in this cycle 
(20221114) on these SUTs
   * P9 baltar
   * ARM64 kuzzle
   * ARM64 howzit-kernel

  This should not be considered as a regression as the net test cannot
  be built in 5.19.0-24.25

  
  Test log:
  
ubuntu@baltar:~/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net$
 sudo ./pmtu.sh
  TEST: ipv4: PMTU exceptions [ OK ]
  TEST: ipv4: PMTU exceptions - nexthop objects   [ OK ]
  TEST: ipv6: PMTU exceptions [ OK ]
  TEST: ipv6: PMTU exceptions - nexthop objects   [ OK ]
  TEST: ICMPv4 with DSCP and ECN: PMTU exceptions [ OK ]
  TEST: ICMPv4 with DSCP and ECN: PMTU exceptions - nexthop objects   [ OK ]
  'socat' command not found; skipping tests
  TEST: UDPv4 with DSCP and ECN: PMTU exceptions  [SKIP]
  TEST: IPv4 over vxlan4: PMTU exceptions [ OK ]
  TEST: IPv4 over vxlan4: PMTU exceptions - nexthop objects   [ OK ]
  TEST: IPv6 over vxlan4: PMTU exceptions [ OK ]
  TEST: IPv6 over vxlan4: PMTU exceptions - nexthop objects   [ OK ]
  TEST: IPv4 over vxlan6: PMTU exceptions [ OK ]
  TEST: IPv4 over vxlan6: PMTU exceptions - nexthop objects   [ OK ]
  TEST: IPv6 over vxlan6: PMTU exceptions [ OK ]
  TEST: IPv6 over vxlan6: PMTU exceptions - nexthop objects   [ OK ]
  TEST: IPv4 over geneve4: PMTU exceptions[ OK ]
  TEST: IPv4 over geneve4: PMTU exceptions - nexthop objects  [ OK ]
  TEST: IPv6 over geneve4: PMTU exceptions[ OK ]
  TEST: IPv6 over geneve4: PMTU exceptions - nexthop objects  [ OK ]
  TEST: IPv4 over geneve6: PMTU exceptions[ OK ]
  TEST: IPv4 over geneve6: PMTU exceptions - nexthop objects  [ OK ]
  TEST: IPv6 over geneve6: PMTU exceptions[ OK ]
  TEST: IPv6 over geneve6: PMTU exceptions - nexthop objects  [ OK ]
  TEST: IPv4, bridged vxlan4: PMTU exceptions [ OK ]
  TEST: IPv4, bridged vxlan4: PMTU exceptions - nexthop objects   [ OK ]
  TEST: IPv6, bridged vxlan4: PMTU exceptions [ OK ]
  TEST: IPv6, bridged vxlan4: PMTU exceptions - nexthop objects   [ OK ]
  TEST: IPv4, bridged vxlan6: PMTU exceptions [ OK ]
  TEST: IPv4, bridged vxlan6: PMTU exceptions - nexthop objects   [ OK ]
  TEST: IPv6, bridged vxlan6: PMTU exceptions [ OK ]
  TEST: IPv6, bridged vxlan6: PMTU exceptions - nexthop objects   [ OK ]
  TEST: IPv4, bridged geneve4: PMTU exceptions[ OK ]
  TEST: IPv4, bridged geneve4: PMTU exceptions - nexthop objects  [ OK ]
  TEST: IPv6, bridged geneve4: PMTU exceptions[ OK ]
  TEST: IPv6, bridged geneve4: PMTU exceptions - nexthop objects  [ OK ]
  TEST: IPv4, bridged geneve6: PMTU exceptions[ OK ]
  TEST: IPv4, bridged geneve6: PMTU exceptions - nexthop objects  [ OK ]
  TEST: IPv6, bridged geneve6: PMTU exceptions[ OK ]
  TEST: IPv6, bridged geneve6: PMTU exceptions - nexthop objects  [ OK ]
ovs_bridge not supported
  TEST: IPv4, OVS vxlan4: PMTU exceptions [SKIP]
ovs_bridge not supported
  TEST: IPv6, OVS vxlan4: PMTU exceptions [SKIP]
ovs_bridge not supported
  TEST: IPv4, OVS vxlan6: PMTU exceptions [SKIP]
ovs_bridge not supported
  TEST: IPv6, OVS vxlan6: PMTU exceptions [SKIP]
ovs_bridge not supported
  TEST: IPv4, OVS geneve4: PMTU exceptions[SKIP]
ovs_bridge not supported
  TEST: IPv6, OVS geneve4: PMTU exceptions[SKIP]
ovs_bridge not supported
  TEST: IPv4, OVS geneve6: PMTU exceptions[SKIP]
ovs_bridge not supported
  TEST: IPv6, OVS geneve6: PMTU exceptions[SKIP]
  TEST: IPv4 over fou4: PMTU exceptions   [ OK ]
  TEST: IPv4 over fou4: PMTU exceptions - nexthop objects [ OK ]
  TEST: IPv6 over fou4: PMTU exceptions 

[Kernel-packages] [Bug 2002601] Re: Wireless: Enable RTL8852BE wifi driver

2023-02-01 Thread Andi
Hi I am also affected by this. I have kernel 6.1.4 under Jammy and my
Wifi card is a RLT8852BE. I installed the amd64 build from the deb
package, but Wifi still isn't working. Not sure if I have to do anything
beyond rebooting. "find /lib/modules/$(uname -r) | grep 8852" returns a
number of kernel modules, with 8852a* and 8852c*, but nothing fitting
the 8852b* category.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/2002601

Title:
  Wireless: Enable RTL8852BE wifi driver

Status in HWE Next:
  New
Status in linux package in Ubuntu:
  In Progress
Status in linux-firmware package in Ubuntu:
  Fix Released
Status in linux-oem-6.1 package in Ubuntu:
  Invalid
Status in linux source package in Jammy:
  Invalid
Status in linux-firmware source package in Jammy:
  Fix Committed
Status in linux-oem-6.1 source package in Jammy:
  Fix Committed
Status in linux source package in Lunar:
  In Progress
Status in linux-firmware source package in Lunar:
  Fix Released
Status in linux-oem-6.1 source package in Lunar:
  Invalid

Bug description:
  [Justification]
  Enable Realtek RLT8852BE WIFI.

  [Test]
  1. put rtw8852b_fw.bin in /lib/firmware/rtw89/
  2. boot-up with kernel enabled RTL8852be.
  3. Connect to WIFI-AP and test with ping.

  * ping -I wlp2s0 8.8.8.8
  ~~~
  PING 8.8.8.8 (8.8.8.8) from 10.102.137.55 wlp2s0: 56(84) bytes of data.
  64 bytes from 8.8.8.8: icmp_seq=1 ttl=116 time=5.86 ms
  64 bytes from 8.8.8.8: icmp_seq=2 ttl=116 time=6.21 ms
  64 bytes from 8.8.8.8: icmp_seq=3 ttl=116 time=18.9 ms
  64 bytes from 8.8.8.8: icmp_seq=4 ttl=116 time=6.09 ms
  64 bytes from 8.8.8.8: icmp_seq=5 ttl=116 time=6.13 ms
  64 bytes from 8.8.8.8: icmp_seq=6 ttl=116 time=5.77 ms
  ~~~
  * Connected to AP
  ~~~
  u@ubuntu:~$ nmcli dev
  DEVICE TYPE STATE CONNECTION
  enp3s0 ethernet connected Wired connection 1
  wlp2s0 wifi connected Canonical
  p2p-dev-wlp2s0 wifi-p2p disconnected --
  lo loopback unmanaged --
  ~~~
  * lsmod | grep 8852
  ~~~
  lsmod | grep 8852
  rtw89_8852be 16384 0
  rtw89_8852b 368640 1 rtw89_8852be
  rtw89_pci 61440 1 rtw89_8852be
  rtw89_core 442368 2 rtw89_8852b,rtw89_pci
  cfg80211 1081344 3 rtw89_8852b,rtw89_core,mac80211
  ~~~

  4. cbd's built result,
  Lunar,
  ~~~
  remote: Resolving deltas: 100% (391/391), completed with 118 local objects.
  remote: *** kernel-cbd 
*
  remote: * Queueing builds (your 'u_lMstrNxt'); ok to interrupt
  remote: * For results:  ssh cbd ls kobako-lunar-0e58018b43c1-ioeM
  remote: * 96/480 cores busy (1/5 hosts), 0 builds queued
  remote: 2023-01-12 03:16:35  kobako-lunar-0e58018b43c1-ioeM/amd64/BUILD-OK
  remote: 2023-01-12 03:17:47  kobako-lunar-0e58018b43c1-ioeM/arm64/BUILD-OK
  remote: 2023-01-12 03:11:36  kobako-lunar-0e58018b43c1-ioeM/armhf/BUILD-OK
  remote: 2023-01-12 03:16:30  kobako-lunar-0e58018b43c1-ioeM/ppc64el/BUILD-OK
  remote: 2023-01-12 03:10:24  kobako-lunar-0e58018b43c1-ioeM/s390x/BUILD-OK
  remote: 

  To cbd:lunar.git
  ~~~
  OEM-6.1,
  remote: Resolving deltas: 100% (399/399), completed with 121 local objects.
  remote: *** kernel-cbd 
*
  remote: * Queueing builds (your 'oem-6.1-next'); ok to interrupt
  remote: * For results:  ssh cbd ls kobako-jammy-c1002f30ccc3-m65z
  remote: * 0/192 cores busy (0/2 hosts), 0 builds queued
  remote: 2023-01-12 05:25:23  kobako-jammy-c1002f30ccc3-m65z/amd64/BUILD-OK
  remote: 

  To cbd:jammy.git

  [Where problems could occur]
  Medium, a new driver so the current driver may have some edge cases didn't 
consider.

  [Misc]
  * For generic Jammy, need more patches to enable RTL8852be so only SRU for 
OEM-6.1.
  * firmware, dae5d4603b07) rtw89: 8852b: update fw to v0.27.32.1 has landed on 
Lunar, so only SRU for Jammy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2002601/+subscriptions


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


[Kernel-packages] [Bug 2003596] Re: Bionic update: upstream stable patchset 2023-01-20

2023-02-01 Thread Luke Nowakowski-Krijger
** Changed in: linux (Ubuntu Bionic)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2003596

Title:
  Bionic update: upstream stable patchset 2023-01-20

Status in linux package in Ubuntu:
  Invalid
Status in linux source package in Bionic:
  Fix Committed

Bug description:
  SRU Justification

  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:

     upstream stable patchset 2023-01-20

  Ported from the following upstream stable releases:
  v4.14.299, v4.19.265
 v4.19.266
  v4.14.300, v4.19.267
  v4.14.301, v4.19.268
  v4.14.302, v4.19.269

     from git://git.kernel.org/

  NFSv4.1: Handle RECLAIM_COMPLETE trunking errors
  NFSv4.1: We must always send RECLAIM_COMPLETE after a reboot
  nfs4: Fix kmemleak when allocate slot failed
  net: dsa: Fix possible memory leaks in dsa_loop_init()
  nfc: s3fwrn5: Fix potential memory leak in s3fwrn5_nci_send()
  nfc: nfcmrvl: Fix potential memory leak in nfcmrvl_i2c_nci_send()
  net: fec: fix improper use of NETDEV_TX_BUSY
  ata: pata_legacy: fix pdc20230_set_piomode()
  net: sched: Fix use after free in red_enqueue()
  ipvs: use explicitly signed chars
  rose: Fix NULL pointer dereference in rose_send_frame()
  mISDN: fix possible memory leak in mISDN_register_device()
  isdn: mISDN: netjet: fix wrong check of device registration
  btrfs: fix inode list leak during backref walking at resolve_indirect_refs()
  btrfs: fix ulist leaks in error paths of qgroup self tests
  Bluetooth: L2CAP: fix use-after-free in l2cap_conn_del()
  net: mdio: fix undefined behavior in bit shift for __mdiobus_register
  net, neigh: Fix null-ptr-deref in neigh_table_clear()
  media: s5p_cec: limit msg.len to CEC_MAX_MSG_SIZE
  media: dvb-frontends/drxk: initialize err to 0
  i2c: xiic: Add platform module alias
  Bluetooth: L2CAP: Fix attempting to access uninitialized memory
  block, bfq: protect 'bfqd->queued' by 'bfqd->lock'
  btrfs: fix type of parameter generation in btrfs_get_dentry
  tcp/udp: Make early_demux back namespacified.
  capabilities: fix potential memleak on error path from vfs_getxattr_alloc()
  ALSA: usb-audio: Add quirks for MacroSilicon MS2100/MS2106 devices
  efi: random: reduce seed size to 32 bytes
  parisc: Make 8250_gsc driver dependend on CONFIG_PARISC
  parisc: Export iosapic_serial_irq() symbol for serial port driver
  ext4: fix warning in 'ext4_da_release_space'
  KVM: x86: Mask off reserved bits in CPUID.8008H
  KVM: x86: emulator: em_sysexit should update ctxt->mode
  KVM: x86: emulator: introduce emulator_recalc_and_set_mode
  KVM: x86: emulator: update the emulation mode after CR0 write
  linux/const.h: prefix include guard of uapi/linux/const.h with _UAPI
  linux/const.h: move UL() macro to include/linux/const.h
  linux/bits.h: make BIT(), GENMASK(), and friends available in assembly
  wifi: brcmfmac: Fix potential buffer overflow in brcmf_fweh_event_worker()
  RDMA/qedr: clean up work queue on failure in qedr_alloc_resources()
  net: tun: fix bugs for oversize packet when napi frags enabled
  ipvs: fix WARNING in __ip_vs_cleanup_batch()
  ipvs: fix WARNING in ip_vs_app_net_cleanup()
  ipv6: fix WARNING in ip6_route_net_exit_late()
  parisc: Avoid printing the hardware path twice
  UBUNTU: Upstream stable to v4.14.299, v4.19.265
  HID: hyperv: fix possible memory leak in mousevsc_probe()
  net: gso: fix panic on frag_list with mixed head alloc types
  bnxt_en: fix potentially incorrect return value for ndo_rx_flow_steer
  net: fman: Unregister ethernet device on removal
  capabilities: fix undefined behavior in bit shift for CAP_TO_MASK
  net: lapbether: fix issue of dev reference count leakage in 
lapbeth_device_event()
  hamradio: fix issue of dev reference count leakage in bpq_device_event()
  drm/vc4: Fix missing platform_unregister_drivers() call in vc4_drm_register()
  ipv6: addrlabel: fix infoleak when sending struct ifaddrlblmsg to network
  tipc: fix the msg->req tlv len check in tipc_nl_compat_name_table_dump_header
  dmaengine: mv_xor_v2: Fix a resource leak in mv_xor_v2_remove()
  drivers: net: xgene: disable napi when register irq failed in 
xgene_enet_open()
  net: cxgb3_main: disable napi when bind qsets failed in cxgb_up()
  ethernet: s2io: disable napi when start nic failed in s2io_card_up()
  net: mv643xx_eth: disable napi when init rxq or txq 

[Kernel-packages] [Bug 2004493] [NEW] dmidecode support for SMBIOS SPEC 3.5 for type 9 EDSFF enumeration

2023-02-01 Thread craig edwards
Public bug reported:

For EDSFF slot type changes no longer indicate the PCIe Generation supported 
nor do they indicate the full formfactor. To accomodate this severa sections 
have been added in the spec as follows 7.10.10 System Slots — Slot Information 
, 7.10.11 System Slots —Slot Physical Width , 7.10.12 System Slots — Slot Pitch
, 7.10.13 System Slots — Slot Height. Currently they do no show up in the 
dmidecode 3.3 / Jammy 
Untested on Kinetic. 

This is related to a previous bug as well.
https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/1986852

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

** Attachment added: "the DMTF spec 3.5"
   
https://bugs.launchpad.net/bugs/2004493/+attachment/5644289/+files/DSP0134_3.5.0.pdf

** Description changed:

  For EDSFF slot type changes no longer indicate the PCIe Generation supported 
nor do they indicate the full formfactor. To accomodate this severa sections 
have been added in the spec as follows 7.10.10 System Slots — Slot Information 
, 7.10.11 System Slots —Slot Physical Width , 7.10.12 System Slots — Slot Pitch
  , 7.10.13 System Slots — Slot Height. Currently they do no show up in the 
dmidecode 3.3
+ 
+ This is related to a previous bug as well. 
+ https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/1986852

** Description changed:

  For EDSFF slot type changes no longer indicate the PCIe Generation supported 
nor do they indicate the full formfactor. To accomodate this severa sections 
have been added in the spec as follows 7.10.10 System Slots — Slot Information 
, 7.10.11 System Slots —Slot Physical Width , 7.10.12 System Slots — Slot Pitch
- , 7.10.13 System Slots — Slot Height. Currently they do no show up in the 
dmidecode 3.3
+ , 7.10.13 System Slots — Slot Height. Currently they do no show up in the 
dmidecode 3.3 / Jammy 
+ Untested on Kinetic. 
  
- This is related to a previous bug as well. 
+ This is related to a previous bug as well.
  https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/1986852

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dmidecode in Ubuntu.
https://bugs.launchpad.net/bugs/2004493

Title:
  dmidecode support for SMBIOS SPEC 3.5 for type 9  EDSFF enumeration

Status in dmidecode package in Ubuntu:
  New

Bug description:
  For EDSFF slot type changes no longer indicate the PCIe Generation supported 
nor do they indicate the full formfactor. To accomodate this severa sections 
have been added in the spec as follows 7.10.10 System Slots — Slot Information 
, 7.10.11 System Slots —Slot Physical Width , 7.10.12 System Slots — Slot Pitch
  , 7.10.13 System Slots — Slot Height. Currently they do no show up in the 
dmidecode 3.3 / Jammy 
  Untested on Kinetic. 

  This is related to a previous bug as well.
  https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/1986852

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


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


[Kernel-packages] [Bug 1933090] Re: systemd/245.4-4ubuntu3.6 ADT test failure with linux-hwe-5.11/5.11.0-20.21~20.04.1

2023-02-01 Thread Roxana Nicolescu
I run the test locally on a vm running linux-oracle-5.15-1029.
It seems `syscall(__NR__sysctl, NULL)` returns ENOSYS(38) -- Function not 
implemented.
Checking `/proc/kallsyms` it seems sysctl is not implemented indeed.

If I take a closer look at jammy-ubuntu tag in systemd source (test that is not 
failing currently)
I can see that it asserts for either EFAULT or ENOSYS:

assert_se(IN_SET(errno, EFAULT, ENOSYS));

This patch will solve the issue:

diff --git a/src/test/test-seccomp.c b/src/test/test-seccomp.c
index 67900d85e..7ebcca4d3 100644
--- a/src/test/test-seccomp.c
+++ b/src/test/test-seccomp.c
@@ -307,7 +307,7 @@ static void test_protect_sysctl(void) {
 if (pid == 0) {
 #if defined __NR__sysctl && __NR__sysctl >= 0
 assert_se(syscall(__NR__sysctl, NULL) < 0);
-assert_se(errno == EFAULT);
+assert_se(IN_SET(errno, EFAULT, ENOSYS));
 #endif

 assert_se(seccomp_protect_sysctl() >= 0);

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-hwe-5.15 in Ubuntu.
https://bugs.launchpad.net/bugs/1933090

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

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

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

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

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

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

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

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


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


[Kernel-packages] [Bug 1993315] Re: md: Replace snprintf with scnprintf

2023-02-01 Thread Tim Gardner
** Tags removed: verification-needed-focal verification-needed-jammy
** Tags added: verification-done-focal verification-done-jammy

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1993315

Title:
  md: Replace snprintf with scnprintf

Status in linux package in Ubuntu:
  In Progress
Status in linux source package in Focal:
  Fix Released
Status in linux source package in Jammy:
  Fix Released
Status in linux source package in Kinetic:
  Fix Released

Bug description:
  SRU Justification

  [Impact]
  Current code produces a warning as shown below when total characters
  in the constituent block device names plus the slashes exceeds 200.
  snprintf() returns the number of characters generated from the given
  input, which could cause the expression “200 – len” to wrap around
  to a large positive number. Fix this by using scnprintf() instead,
  which returns the actual number of characters written into the buffer.

  [ 1513.267938] [ cut here ]
  [ 1513.267943] WARNING: CPU: 15 PID: 37247 at /lib/vsprintf.c:2509 
vsnprintf+0x2c8/0x510
  [ 1513.267944] Modules linked in:  
  [ 1513.267969] CPU: 15 PID: 37247 Comm: mdadm Not tainted 5.4.0-1085-azure 
#90~18.04.1-Ubuntu
  [ 1513.267969] Hardware name: Microsoft Corporation Virtual Machine/Virtual 
Machine, BIOS Hyper-V UEFI Release v4.1 05/09/2022
  [ 1513.267971] RIP: 0010:vsnprintf+0x2c8/0x510
  <-snip->
  [ 1513.267982] Call Trace:
  [ 1513.267986]  snprintf+0x45/0x70
  [ 1513.267990]  ? disk_name+0x71/0xa0
  [ 1513.267993]  dump_zones+0x114/0x240 [raid0]
  [ 1513.267996]  ? _cond_resched+0x19/0x40
  [ 1513.267998]  raid0_run+0x19e/0x270 [raid0]
  [ 1513.268000]  md_run+0x5e0/0xc50
  [ 1513.268003]  ? security_capable+0x3f/0x60
  [ 1513.268005]  do_md_run+0x19/0x110
  [ 1513.268006]  md_ioctl+0x195e/0x1f90
  [ 1513.268007]  blkdev_ioctl+0x91f/0x9f0
  [ 1513.268010]  block_ioctl+0x3d/0x50
  [ 1513.268012]  do_vfs_ioctl+0xa9/0x640
  [ 1513.268014]  ? __fput+0x162/0x260
  [ 1513.268016]  ksys_ioctl+0x75/0x80
  [ 1513.268017]  __x64_sys_ioctl+0x1a/0x20
  [ 1513.268019]  do_syscall_64+0x5e/0x200
  [ 1513.268021]  entry_SYSCALL_64_after_hwframe+0x44/0xa9

  [Fix]

  https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-
  next.git/commit/?id=1727fd5015d8f93474148f94e34cda5aa6ad4a43

  [Where things could go wrong]

  This seems unlikely to cause a regression

  [Other Info]

  SF: #00346036

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


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


[Kernel-packages] [Bug 2003714] Re: Azure: TDX enabled hyper-visors cause segfault

2023-02-01 Thread Tim Gardner
** Tags removed: verification-needed-kinetic
** Tags added: verification-done-kinetic

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/2003714

Title:
  Azure: TDX enabled hyper-visors cause segfault

Status in linux-azure package in Ubuntu:
  In Progress

Bug description:
  SRU Justification

  [Impact]

  Microsoft TDX enabled hyper visors cause a segfault due to an upstream
  glibc bug. This can be worked around with a kernel patch.

  Issue Description:

  When I start an Intel TDX Ubuntu 22.04 (or RHEL 9.0) guest on Hyper-V,
  the guest always hits segfaults and can’t boot up. Here the kernel
  running in the guest is the upstream kernel + my TDX patchset, or the
  5.19.0-azure kernel + the same TDX patchset:

  [Fix]

  We confirmed the segfault also happens to TDX guests on the KVM
  hypervisor. After I checked with more Intel folks, it turns out this
  is indeed a glibc bug
  (https://sourceware.org/bugzilla/show_bug.cgi?id=28784), which has
  been fixed in the upsteram glibc, but Ubuntu 22.04 and newer haven’t
  picked up the glibc fix yet.

  I got a kernel side temporary workarouond from Intel:
  https://github.com/dcui/tdx/commit/16218cf73491e867fd39c16c9e4b8aa926cbda68,
  which is on the same existing branch “decui/upstream-
  kinetic-22.10/master-next/1209”.

  [   21.081453] Run /inits init process
  [   21.086896]   with arguments:
  [   21.095790] /init
  [   21.100982]   with environment:
  [   21.106611] HOME=/
  [   21.112463] TERM=linux
  [   21.119850] BOOT_IMAGE=/boot/vmlinuz-6.1.0-rc7-decui+

  Loading, please wait...

  Starting version 249.11-0ubuntu3.6

  [   21.253908] udevadm[144]: segfault at 56538d61e0c0 ip 7f8f5899efeb sp 
7ffd08fb7648 error 6 in libc.so.6[7f8f5882+195000] likely on CPU 0 
(core 0, socket 0)
  [   21.316549] Code: 07 62 e1 7d 48 e7 4f 01 62 e1 7d 48 e7 67 40 62 e1 7d 48 
e7 6f 41 62 61 7d 48 e7 87 00 20 00 00 62 61 7d 48 e7 8f 40 20 00 00 <62> 61 7d 
48 e7 a7 00 30 00 00 62 61 7d 48 e7 af 40 30 00 00 48 83

  Segmentation fault

  [   22.499317] setfont[153]: segfault at 55ef3b91b000 ip 7f5899899fa4 sp 
7ffc8008f628 error 4 in libc.so.6[7f589971b000+195000] likely on CPU 0 
(core 0, socket 0)
  [   22.602677] Code: 06 62 e1 fe 48 6f 4e 01 62 e1 fe 48 6f 66 40 62 e1 fe 48 
6f 6e 41 62 61 fe 48 6f 86 00 20 00 00 62 61 fe 48 6f 8e 40 20 00 00 <62> 61 fe 
48 6f a6 00 30 00 00 62 61 fe 48 6f ae 40 30 00 00 48 83
  [   22.732413] loadkeys[156]: segfault at 563ffe292000 ip 7fbff957afa4 sp 
7ffe31453808 error 4 in libc.so.6[7fbff93fc000+195000] likely on CPU 0 
(core 0, socket 0)
  [   22.833061] Code: 06 62 e1 fe 48 6f 4e 01 62 e1 fe 48 6f 66 40 62 e1 fe 48 
6f 6e 41 62 61 fe 48 6f 86 00 20 00 00 62 61 fe 48 6f 8e 40 20 00 00 <62> 61 fe 
48 6f a6 00 30 00 00 62 61 fe 48 6f ae 40 30 00 00 48 83

  The segfault only happens to recent glibc versions (e.g. v2.35 in
  Ubuntu 22.04, and v2.34 in RHEL 9.0). It doesn’t happens to v2.31 in
  Ubuntu 20.04, or v2.32 in Ubuntu 20.10. So something in glibc must
  have changed between v2.32 (good) and 2.34+ (not working for TDX). The
  oddity is: when I run the same Ubuntu 22.04/RHEL 9.0 image as a
  regular non-TDX guest, the segfault never happens.

  If I boot up a Ubuntu 20.04 TDX guest (which works fine), mount a
  Ubuntu 22.04 VHD image (“mount /dev/sdd1 /mnt”) and try to run “chroot
  /mnt”, I hit the same segfault:

  [  109.478556] EXT4-fs (sdd1): mounted filesystem with ordered data mode. 
Quota mode: none.
  [  129.22] bash[2112]: segfault at 556987854000 ip 7f88468c4ea4 sp 
7ffc22ecf158 error 6 in libc.so.6[7f8846828000+195000] likely on CPU 48 
(core 0, socket 48)
  [  129.242434] Code: e7 bf 30 10 00 00 66 44 0f e7 87 00 20 00 00 66 44 0f e7 
8f 10 20 00 00 66 44 0f e7 97 20 20 00 00 66 44 0f e7 9f 30 20 00 00 <66> 44 0f 
e7 a7 00 30 00 00 66 44 0f e7 af 10 30 00 00 66 44 0f e7

  It looks like the application is referencing a memory location that
  somehow triggers a page fault, which is converted to a sigal SIGSEGV,
  which causes a segfault and terminates the application (I’m not sure
  where the below “movntdq” instructions come from):

  root@decui-u2004-u28:/opt/linus-0824# echo 'Code: e7 bf 30 10 00 00 66
  44 0f e7 87 00 20 00 00 66 44 0f e7 8f 10 20 00 00 66 44 0f e7 97 20
  20 00 00 66 44 0f e7 9f 30 20 00 00 <66> 44 0f e7 a7 00 30 00 00 66 44
  0f e7 af 10 30 00 00 66 44 0f e7' | scripts/decodecode

  Code: e7 bf 30 10 00 00 66 44 0f e7 87 00 20 00 00 66 44 0f e7 8f 10
  20 00 00 66 44 0f e7 97 20 20 00 00 66 44 0f e7 9f 30 20 00 00 <66> 44
  0f e7 a7 00 30 00 00 66 44 0f e7 af 10 30 00 00 66 44 0f e7

  All code
  
     0:   e7 bf   out%eax,$0xbf
     2:   30 10   xor%dl,(%rax)
     4:   00 00   add%al,(%rax)
     6:   66 44 0f e7 87 00 20movntdq %xmm8,0x2000(%rdi)

[Kernel-packages] [Bug 2004470] Status changed to Confirmed

2023-02-01 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2004470

Title:
  macvlan network mode setting probably broken

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  using Ubuntu 22.04, Kernel 5.15.0-58-generic, LXD 5.10-b392610,
  iproute2 5.15.0-1ubuntu2

  
  I ran into the problem that a virtual LXD container with an macvlan network 
interface mapped to the hosts ethernet adapter works as expected with all other 
machines in the LAN, including getting an IP address assigned by the DHCP 
server. But it cannot be reached from the HOST machine itself.

  
  My first guess was that LXD does not set the macvlan into bridge mode, but 
leaves it in the default private mode, which would explain the problem. But 
LXD's source code showed that it sets the mode to bridge and uses iproute2's  
ip program to set the interface.

  I therefore tried commands like

  ip link add name blubb address 02:4e:a6:27:01:07 link enp4s0 type
  macvlan mode bridge

  ip link add link enp4s0 name sugar type macvlan mode bridge

  which succeed without error message. But ip link show reports

  9: blubb@enp4s0:  mtu 1500 qdisc noop state DOWN mode 
DEFAULT group default qlen 1000
  link/ether 02:4e:a6:27:01:07 brd ff:ff:ff:ff:ff:ff
  10: sugar@enp4s0:  mtu 1500 qdisc noop state DOWN mode 
DEFAULT group default qlen 1000
  link/ether 26:99:d1:52:ba:e0 brd ff:ff:ff:ff:ff:ff

  in both cases "mode DEFAULT", where I would expect „bridge“. Same with
  the interface assigned to the LXD virtual container.

  
  Shouldn't this show the mode used in the ip link add command instead of 
DEFAULT? 

  
  - I reported the problem to the iproute2 maintainer, but he told me to report 
to net...@vger.kernel.org

  - on net...@vger.kernel.org I did not get a response

  - Kernel.org bugzilla tells to report problems not to kernel.org, but
  to the distributions bug system

  
  regards

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-58-generic 5.15.0-58.64
  ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
  Uname: Linux 5.15.0-58-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hadmut 3252 F pulseaudio
  CasperMD5CheckResult: unknown
  CurrentDesktop: LXQt
  Date: Wed Feb  1 11:57:58 2023
  InstallationDate: Installed on 2020-06-12 (963 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Medion G24
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic 
root=UUID=e1e9c4ee-42ab-4be4-9160-7d4d0e23f95c ro quiet 
cryptdevice=UUID=66118fb4-e7e6-4516-872a-67d93f44b554:luks-66118fb4-e7e6-4516-872a-67d93f44b554
 root=/dev/mapper/luks-66118fb4-e7e6-4516-872a-67d93f44b554 
resume=/dev/mapper/luks-66118fb4-e7e6-4516-872a-67d93f44b554 splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-58-generic N/A
   linux-backports-modules-5.15.0-58-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.9
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: Upgraded to jammy on 2022-05-28 (248 days ago)
  dmi.bios.date: 10/12/2012
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: H61TIW08.111
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61H2-TI2
  dmi.board.vendor: Medion
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Medion
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrH61TIW08.111:bd10/12/2012:br4.6:svnMedion:pnG24:pvr1.0:rvnMedion:rnH61H2-TI2:rvr1.0:cvnMedion:ct3:cvr1.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: G24
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Medion

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


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


[Kernel-packages] [Bug 2004470] [NEW] macvlan network mode setting probably broken

2023-02-01 Thread Hadmut Danisch
Public bug reported:

Hi,

using Ubuntu 22.04, Kernel 5.15.0-58-generic, LXD 5.10-b392610, iproute2
5.15.0-1ubuntu2


I ran into the problem that a virtual LXD container with an macvlan network 
interface mapped to the hosts ethernet adapter works as expected with all other 
machines in the LAN, including getting an IP address assigned by the DHCP 
server. But it cannot be reached from the HOST machine itself.


My first guess was that LXD does not set the macvlan into bridge mode, but 
leaves it in the default private mode, which would explain the problem. But 
LXD's source code showed that it sets the mode to bridge and uses iproute2's  
ip program to set the interface.

I therefore tried commands like

ip link add name blubb address 02:4e:a6:27:01:07 link enp4s0 type
macvlan mode bridge

ip link add link enp4s0 name sugar type macvlan mode bridge

which succeed without error message. But ip link show reports

9: blubb@enp4s0:  mtu 1500 qdisc noop state DOWN mode 
DEFAULT group default qlen 1000
link/ether 02:4e:a6:27:01:07 brd ff:ff:ff:ff:ff:ff
10: sugar@enp4s0:  mtu 1500 qdisc noop state DOWN mode 
DEFAULT group default qlen 1000
link/ether 26:99:d1:52:ba:e0 brd ff:ff:ff:ff:ff:ff

in both cases "mode DEFAULT", where I would expect „bridge“. Same with
the interface assigned to the LXD virtual container.


Shouldn't this show the mode used in the ip link add command instead of 
DEFAULT? 


- I reported the problem to the iproute2 maintainer, but he told me to report 
to net...@vger.kernel.org

- on net...@vger.kernel.org I did not get a response

- Kernel.org bugzilla tells to report problems not to kernel.org, but to
the distributions bug system


regards

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-5.15.0-58-generic 5.15.0-58.64
ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74
Uname: Linux 5.15.0-58-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82.3
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  hadmut 3252 F pulseaudio
CasperMD5CheckResult: unknown
CurrentDesktop: LXQt
Date: Wed Feb  1 11:57:58 2023
InstallationDate: Installed on 2020-06-12 (963 days ago)
InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: Medion G24
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic 
root=UUID=e1e9c4ee-42ab-4be4-9160-7d4d0e23f95c ro quiet 
cryptdevice=UUID=66118fb4-e7e6-4516-872a-67d93f44b554:luks-66118fb4-e7e6-4516-872a-67d93f44b554
 root=/dev/mapper/luks-66118fb4-e7e6-4516-872a-67d93f44b554 
resume=/dev/mapper/luks-66118fb4-e7e6-4516-872a-67d93f44b554 splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-58-generic N/A
 linux-backports-modules-5.15.0-58-generic  N/A
 linux-firmware 20220329.git681281e4-0ubuntu3.9
RfKill:
 0: phy0: Wireless LAN
Soft blocked: yes
Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to jammy on 2022-05-28 (248 days ago)
dmi.bios.date: 10/12/2012
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: H61TIW08.111
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H61H2-TI2
dmi.board.vendor: Medion
dmi.board.version: 1.0
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Medion
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrH61TIW08.111:bd10/12/2012:br4.6:svnMedion:pnG24:pvr1.0:rvnMedion:rnH61H2-TI2:rvr1.0:cvnMedion:ct3:cvr1.0:skuTobefilledbyO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: G24
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: Medion

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


** Tags: amd64 apport-bug jammy

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2004470

Title:
  macvlan network mode setting probably broken

Status in linux package in Ubuntu:
  New

Bug description:
  Hi,

  using Ubuntu 22.04, Kernel 5.15.0-58-generic, LXD 5.10-b392610,
  iproute2 5.15.0-1ubuntu2

  
  I ran into the problem that a virtual LXD container with an macvlan network 
interface mapped to the hosts ethernet adapter works as expected with all other 
machines in the LAN, including getting an IP address assigned by the DHCP 
server. But it cannot be reached from the HOST machine itself.

  
  My first guess was that LXD does not set the macvlan into bridge mode, but 
leaves it in the default private mode, which would explain the problem. But 
LXD's source code showed that it sets the mode to bridge and uses iproute2's  
ip program to set the interface.

  I therefore tried commands like

  ip link add name blubb address 02:4e:a6:27:01:07 link enp4s0 type
  macvlan mode bridge

  ip link add link enp4s0 name 

[Kernel-packages] [Bug 2003995] Re: Update the 525 and 525-server NVIDIA driver series in Bionic, Focal, Jammy, and Kinetic

2023-02-01 Thread Alberto Milone
** Also affects: nvidia-graphics-drivers-515-server (Ubuntu)
   Importance: Undecided
   Status: New

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

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

** Also affects: libnvidia-nscq-515 (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-515-server in
Ubuntu.
https://bugs.launchpad.net/bugs/2003995

Title:
  Update the 525 and 525-server NVIDIA driver series in Bionic, Focal,
  Jammy, and Kinetic

Status in fabric-manager-515 package in Ubuntu:
  New
Status in fabric-manager-525 package in Ubuntu:
  New
Status in libnvidia-nscq-515 package in Ubuntu:
  New
Status in nvidia-graphics-drivers-515-server package in Ubuntu:
  New
Status in nvidia-graphics-drivers-525 package in Ubuntu:
  Triaged
Status in nvidia-graphics-drivers-525-server package in Ubuntu:
  Triaged
Status in fabric-manager-515 source package in Bionic:
  New
Status in fabric-manager-525 source package in Bionic:
  New
Status in libnvidia-nscq-515 source package in Bionic:
  New
Status in nvidia-graphics-drivers-515-server source package in Bionic:
  New
Status in nvidia-graphics-drivers-525 source package in Bionic:
  Triaged
Status in nvidia-graphics-drivers-525-server source package in Bionic:
  Triaged
Status in fabric-manager-515 source package in Focal:
  New
Status in fabric-manager-525 source package in Focal:
  New
Status in libnvidia-nscq-515 source package in Focal:
  New
Status in nvidia-graphics-drivers-515-server source package in Focal:
  New
Status in nvidia-graphics-drivers-525 source package in Focal:
  Triaged
Status in nvidia-graphics-drivers-525-server source package in Focal:
  Triaged
Status in fabric-manager-515 source package in Jammy:
  New
Status in fabric-manager-525 source package in Jammy:
  New
Status in libnvidia-nscq-515 source package in Jammy:
  New
Status in nvidia-graphics-drivers-515-server source package in Jammy:
  New
Status in nvidia-graphics-drivers-525 source package in Jammy:
  Triaged
Status in nvidia-graphics-drivers-525-server source package in Jammy:
  Triaged
Status in fabric-manager-515 source package in Kinetic:
  New
Status in fabric-manager-525 source package in Kinetic:
  New
Status in libnvidia-nscq-515 source package in Kinetic:
  New
Status in nvidia-graphics-drivers-515-server source package in Kinetic:
  New
Status in nvidia-graphics-drivers-525 source package in Kinetic:
  Triaged
Status in nvidia-graphics-drivers-525-server source package in Kinetic:
  Triaged

Bug description:
  [Impact]
  These releases provide both bug fixes and new features, and we would like to
  make sure all of our users have access to these improvements.

  See the changelog entry below for a full list of changes and bugs.

  [Test Case]
  The following development and SRU process was followed:
  https://wiki.ubuntu.com/NVidiaUpdates

  Certification test suite must pass on a range of hardware:
  https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu

  The QA team that executed the tests will be in charge of attaching the
  artifacts and console output of the appropriate run to the bug. nVidia
  maintainers team members will not mark ‘verification-done’ until this
  has happened.

  [Regression Potential]
  In order to mitigate the regression potential, the results of the
  aforementioned system level tests are attached to this bug.

  [Discussion]

  [Changelog]

  525.85.05

  Improved the reliability of suspend and resume on UEFI systems when using 
certain display panels.
  Fixed a bug that prevented some controls in the nvidia-settings control panel 
from working when running an X server as an unprivileged user.
  Fixed a bug that could cause VK_ERROR_DEVICE_LOST when using 
VK_MEMORY_ALLOCATE_DEVICE_ADDRESS_CAPTURE_REPLAY_BIT to allocate memory.
  Disabled Fixed Rate Link (FRL) when using passive DisplayPort to HDMI 
dongles, which are incompatible with FRL.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fabric-manager-515/+bug/2003995/+subscriptions


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


[Kernel-packages] [Bug 1990849] Re: LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54

2023-02-01 Thread Stefan Bader
** Changed in: linux (Ubuntu Kinetic)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu Lunar)
   Importance: Undecided => Medium

** Changed in: linux (Ubuntu Jammy)
   Importance: Undecided => Medium

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

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

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1990849

Title:
  LXD containers using shiftfs on ZFS or TMPFS broken on 5.15.0-48.54

Status in linux package in Ubuntu:
  Fix Committed
Status in zfs-linux package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  Confirmed
Status in zfs-linux source package in Jammy:
  Confirmed
Status in linux source package in Kinetic:
  Fix Committed
Status in zfs-linux source package in Kinetic:
  Confirmed
Status in linux source package in Lunar:
  Fix Committed
Status in zfs-linux source package in Lunar:
  Confirmed

Bug description:
  Since 5.15.0-48.54 LXD containers using shiftfs ontop of ZFS or TMPFS
  are broken.

  Reproducer steps:

  ```
  sudo snap install lxd
  sudo snap set lxd shiftfs.enable=true
  sudo lxd init --auto
  lxc storage create zfs zfs
  lxc launch images:ubuntu/jammy c1 -s zfs
  lxc exec c1 -- touch /root/foo
  touch: cannot touch '/root/foo': Value too large for defined data type
  ```

  Expected result can be achieved by disabling shiftfs:

  ```
  sudo snap set lxd shiftfs.enable=false
  sudo systemctl reload snap.lxd.daemon
  lxc launch images:ubuntu/jammy c2 -s zfs
  lxc exec c2 -- touch /root/foo
  lxc exec c2 -- ls -la /root/foo
  -rw-r--r-- 1 root root 0 Sep 26 14:00 /root/foo
  ```

  Kernel 5.15.0-47-generic does not exhibit this issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-48-generic 5.15.0-48.54
  ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53
  Uname: Linux 5.15.0-48-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  user   2240 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 26 14:55:52 2022
  InstallationDate: Installed on 2022-03-04 (205 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220228)
  MachineType: LENOVO 20R1000RUS
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-48-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-48-generic N/A
   linux-backports-modules-5.15.0-48-generic  N/A
   linux-firmware 20220329.git681281e4-0ubuntu3.5
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2021
  dmi.bios.release: 1.34
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2QET40W(1.34 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20R1000RUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.15
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2QET40W(1.34):bd04/15/2021:br1.34:efr1.15:svnLENOVO:pn20R1000RUS:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20R1000RUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20R1_BU_Think_FM_ThinkPadX1Carbon7th:
  dmi.product.family: ThinkPad X1 Carbon 7th
  dmi.product.name: 20R1000RUS
  dmi.product.sku: LENOVO_MT_20R1_BU_Think_FM_ThinkPad X1 Carbon 7th
  dmi.product.version: ThinkPad X1 Carbon 7th
  dmi.sys.vendor: LENOVO

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


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


[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-hwe-5.19/5.19.0.32.33~22.04.9)

2023-02-01 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted linux-meta-hwe-5.19 
(5.19.0.32.33~22.04.9) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

rtl8812au/4.3.8.12175.20140902+dfsg-0ubuntu15 (arm64, amd64)
xtrx-dkms/0.0.1+git20190320.5ae3a3e-2 (armhf, arm64, s390x, amd64, ppc64el)
r8168/8.049.02-1ubuntu1 (armhf, arm64, s390x, amd64, ppc64el)
dahdi-linux/1:2.11.1~dfsg-1ubuntu11 (amd64)
linux-hwe-5.19/5.19.0-32.33~22.04.1 (armhf)
sysdig/0.27.1-0.3build1 (amd64)
r8125/9.007.01-3 (armhf, arm64, s390x, amd64, ppc64el)
nvidia-graphics-drivers-418-server/418.226.00-0ubuntu4 (amd64)
bbswitch/0.8-10ubuntu2 (arm64, amd64)
bcmwl/6.30.223.271+bdcom-0ubuntu8 (amd64)
openafs/1.8.8.1-1 (armhf, arm64, s390x, amd64)
rtl8821ce/5.5.2.1-0ubuntu10 (armhf, arm64, amd64, ppc64el)
broadcom-sta/6.30.223.271-17 (amd64)


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/jammy/update_excuses.html#linux-meta-hwe-5.19

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

Thank you!

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1786013

Title:
  Packaging resync

Status in linux package in Ubuntu:
  Fix Released
Status in linux-azure package in Ubuntu:
  Fix Released
Status in linux-azure-edge package in Ubuntu:
  Fix Released
Status in linux source package in Precise:
  Fix Released
Status in linux-azure source package in Precise:
  Won't Fix
Status in linux-azure-edge source package in Precise:
  Won't Fix
Status in linux source package in Trusty:
  Fix Released
Status in linux-azure source package in Trusty:
  Fix Released
Status in linux-azure-edge source package in Trusty:
  Won't Fix
Status in linux source package in Xenial:
  Fix Released
Status in linux-azure source package in Xenial:
  Fix Released
Status in linux-azure-edge source package in Xenial:
  Fix Released
Status in linux source package in Bionic:
  Fix Released
Status in linux-azure source package in Bionic:
  Fix Released
Status in linux-azure-edge source package in Bionic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in linux-azure source package in Cosmic:
  Fix Released
Status in linux-azure-edge source package in Cosmic:
  Won't Fix
Status in linux source package in Disco:
  Fix Released
Status in linux-azure source package in Disco:
  Fix Released
Status in linux-azure-edge source package in Disco:
  Won't Fix

Bug description:
  Ongoing packing resyncs.

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


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