[Touch-packages] [Bug 1918855] Re: Xorg xserver got signal 6 to abort

[Mathew Hodson]

** Bug watch removed: gitlab.freedesktop.org/mesa/mesa/-/issues #2859
   https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859

** Changed in: mesa (Ubuntu Focal)
   Importance: Undecided => Medium

** Changed in: mesa (Ubuntu Hirsute)
   Importance: Undecided => Medium

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

Title:
  Xorg xserver got signal 6 to abort

Status in OEM Priority Project:
  In Progress
Status in Provider for Plainbox - Checkbox:
  New
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Focal:
  New
Status in mesa source package in Hirsute:
  New

Bug description:
  == SRU Justification ==
  [Impact]
  When the system is under memory pressure, the entire desktop session may 
crash.

  [Fix]
  Commit f9d8d9acbb6a620684fb4dac4affe25816587d92 ("iris: Avoid abort() if 
kernel can't allocate memory")

  [Test]
  Run memory stress and the session crashed in less than 5 minutes.
  With the fix applied, run memory stress for 24 hours and the desktop session 
is still alive.

  [Where problems could occur]
  Doing a reset might make the system even more sluggish when under memory 
pressure.

  
  == Original bug report ==
  I run checkbox job com.canonical.certification::memory/memory_stress_ng on 
focal, and the xserver stops unexpectedly with the following stacktrace:

  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg 
(OsLookupColor+0x13c) [0x5619f3a4d59c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: 
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 
(gsignal+0xcb) [0x7fae476a418b]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 
(abort+0x12b) [0x7fae47683859]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind 
info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) 
[0x7fae46529c9c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so 
(__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: 
/usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) 
[0x7fae47007480]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind 
info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: 
/usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg 
(BlockHandler+0xa5) [0x5619f38f0995]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg 
(WaitForSomething+0x122) [0x5619f3a46c12]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg 
(SendErrorToClient+0x117) [0x5619f38ebcf7]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg 
(InitFonts+0x3b4) [0x5619f38effc4]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf3) [0x7fae476850b3]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) 
[0x5619f38d9a2e]

  More info:
  I searched the Internet and got a bug with the same stacktrace:
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1918855/+subscriptions

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

[Touch-packages] [Bug 1932291] Re: dhcp client resets IP address every few minutes

[Yevhen Ivanchenko]

The reason why dhcp client reset connection was an ICMP message
When the client send a REQUEST, the gateway replied with ICMP code 10 (Host 
administratively prohibited)
Then dhcp server replied with ACK 
--
It happened because iptables on the server did not allow incoming connections 
to port 67 of the dhcp server and it responded with an ICMP (Host 
administratively prohibited).
But it seems the requests came to the dhcp server anyway and dhcp server 
responded with ACK.


I sent only dhcp packets in the dump file but there no ICMP messages were 
included.

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

Title:
  dhcp client resets IP address every few minutes

Status in network-manager package in Ubuntu:
  New

Bug description:
  Hello,
  Network manager resets IP address every 30 minutes (perhaps this time depends 
on default-lease-time)

  This issue affects at least the latest package Network Manager in
  Ubuntu 20.04.2 - network-manager 1.22.10-1ubuntu2.2.

  It seems this issue has been occuring more than a year (perhaps from release 
Ubuntu 20.04) and is not fixed yet.
  It is possible that this issue occurs only with our dhcp server. We have not 
checked if the issue occurs with other dhcp servers.

  
  lsb_release -rd
  Description:Ubuntu 20.04.2 LTS
  Release:20.04
  
  apt-cache policy network-manager
  network-manager:
    Installed: 1.22.10-1ubuntu2.2
    Candidate: 1.22.10-1ubuntu2.2
    Version table:
   *** 1.22.10-1ubuntu2.2 500
  500 http://ua.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.22.10-1ubuntu1 500
  500 http://ua.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  -

  STR:
  Install Ubuntu 20.04.2 (update if needed) and connect to network with dhcp 
server.

  AR:
  Connection drops every few minutes, then NetworkManager reconnects again.
  On screen we can see message "Network disconnect" and right away "Network 
connect"

  ER:
  Connection should be stable.

  We have found the similar bug here - 
https://bugzilla.redhat.com/show_bug.cgi?id=1817788
  It is possible that in my case the root of issue is the same and the isue is 
fixed in network manager 1.22.12

  We need a new networkmanager package in Ubuntu 20.04 repository which
  has not got this bug.

  There is a part of /var/log/syslog
  Here we can see error "error -113 dispatching events"
  
  Jun 16 16:01:40 user-System-Product-Name NetworkManager[589]:  
[1623848500.8092] dhcp4 (enp3s0): send REQUEST of 192.168.61.156 to 192.168.61.2
  Jun 16 16:01:40 user-System-Product-Name NetworkManager[589]:  
[1623848500.8225] dhcp4 (enp3s0): error -113 dispatching events
  Jun 16 16:01:40 user-System-Product-Name NetworkManager[589]:   
[1623848500.8226] dhcp4 (enp3s0): state changed bound -> fail
  Jun 16 16:01:40 user-System-Product-Name NetworkManager[589]:  
[1623848500.8226] device[5565e4c243c020e9] (enp3s0): new DHCPv4 client state 6
  Jun 16 16:01:40 user-System-Product-Name NetworkManager[589]:  
[1623848500.8227] device[5565e4c243c020e9] (enp3s0): DHCPv4 failed (ip_state 
done, was_active 0)
  Jun 16 16:01:40 user-System-Product-Name NetworkManager[589]:   
[1623848500.8228] device (enp3s0): DHCPv4: trying to acquire a new lease within 
90 seconds
  Jun 16 16:01:40 user-System-Product-Name NetworkManager[589]:  
[1623848500.8228] dbus-object[cffc3e670403e5f9]: unexport: 
"/org/freedesktop/NetworkManager/DHCP4Config/8"
  Jun 16 16:01:40 user-System-Product-Name NetworkManager[589]:  
[1623848500.8232] dbus-object[e4f7ca28a56cb5dc]: export: 
"/org/freedesktop/NetworkManager/DHCP4Config/9"
  Jun 16 16:02:18 user-System-Product-Name NetworkManager[589]:  
[1623848538.4785] device[5565e4c243c020e9] (enp3s0): connectivity: [IPv6] 
periodic-check: re-scheduled in 299970 milliseconds (300 se
  conds interval)
  Jun 16 16:02:18 user-System-Product-Name NetworkManager[589]:  
[1623848538.4787] device[5565e4c243c020e9] (enp3s0): connectivity: [IPv6] start 
check (seq:86, periodic-check)
  Jun 16 16:02:18 user-System-Product-Name NetworkManager[589]:  
[1623848538.4790] connectivity: (enp3s0,IPv6,86) start request to 
'http://connectivity-check.ubuntu.com/' (try resolving 'connectivit
  y-check.ubuntu.com' using systemd-resolved)
  Jun 16 16:02:18 user-System-Product-Name NetworkManager[589]:  
[1623848538.4833] connectivity: (enp3s0,IPv6,86) can't resolve a name via 
systemd-resolved: GDBus.Error:org.freedesktop.resolve1.NoSu
  chRR: 'connectivity-check.ubuntu.com' does not have any RR of the requested 
type
  Jun 16 16:02:18 user-System-Product-Name systemd-resolved[549]: Server 
returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, 
retrying transaction with reduced feature level UDP.
  Jun 16 16:02:18 user-System-Product-Name systemd-resolved[549]: message 

[Touch-packages] [Bug 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off

[Daniel van Vugt]

** Also affects: oem-priority
   Importance: Undecided
   Status: New

** Changed in: oem-priority
 Assignee: (unassigned) => Andy Chi (andch)

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

Title:
  [hirsute/impish] Can't turn bluetooth on again after turning it off

Status in GNOME Bluetooth:
  Unknown
Status in OEM Priority Project:
  New
Status in bluez package in Ubuntu:
  Fix Committed
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in bluez source package in Focal:
  In Progress
Status in bluez source package in Hirsute:
  In Progress
Status in bluez source package in Impish:
  Fix Committed
Status in gnome-settings-daemon source package in Impish:
  Fix Released

Bug description:
  [Impact]

  On/off of Bluetooth in gnome-control-center will not work properly in kernels 
5.11 (approximately) onward. Devices are not refreshed in the list anymore.
   
  [Test Plan]

  1. Open gnome-control-center and select Bluetooth
  2. Turn off Bluetooth via UI
  3. Turn on Bluetooth via UI

  Expect: Device list appears, so Bluetooth really is on.

  [Where problems could occur]

  Since the fix involves the 'rfkill' logic it has the potential to
  affect any Bluetooth or Wifi on/off setting.

  [Other info]

  Upstream bug in gnome-bluetooth:
  https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38

  Discussion in linux-bluetooth:
  https://marc.info/?t=16200475893=1=2

  [Original bug report]

  When ever i Turn on my system or restart bluetooth is open any it
  connects to any device. But when i turn off bluetooth and try to turn
  it on again. it neither turns on nor scans/connects to any device.
  This is happening since I updated my system to ubuntu 21.04 LTS

    Bluetooth: hci0: HCI reset during shutdown failed

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 25 15:09:23 2021
  InstallationDate: Installed on 2020-12-15 (130 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 80TR
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago)
  dmi.bios.date: 07/31/2017
  dmi.bios.release: 1.29
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 3UCN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Nano 5B1
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 110-15AST
  dmi.ec.firmware.release: 1.29
  dmi.modalias: 
dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80TR
  dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST
  dmi.product.version: Lenovo ideapad 110-15AST
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: C8:3D:D4:84:E0:06  ACL MTU: 820:8  SCO MTU: 255:16
    DOWN
    RX bytes:744804 acl:76 sco:0 events:105989 errors:0
    TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-bluetooth/+bug/1926062/+subscriptions

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

[Touch-packages] [Bug 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off

[Andy Chi]

** Changed in: oem-priority
   Importance: Undecided => Critical

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

Title:
  [hirsute/impish] Can't turn bluetooth on again after turning it off

Status in GNOME Bluetooth:
  Unknown
Status in OEM Priority Project:
  New
Status in bluez package in Ubuntu:
  Fix Committed
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in bluez source package in Focal:
  In Progress
Status in bluez source package in Hirsute:
  In Progress
Status in bluez source package in Impish:
  Fix Committed
Status in gnome-settings-daemon source package in Impish:
  Fix Released

Bug description:
  [Impact]

  On/off of Bluetooth in gnome-control-center will not work properly in kernels 
5.11 (approximately) onward. Devices are not refreshed in the list anymore.
   
  [Test Plan]

  1. Open gnome-control-center and select Bluetooth
  2. Turn off Bluetooth via UI
  3. Turn on Bluetooth via UI

  Expect: Device list appears, so Bluetooth really is on.

  [Where problems could occur]

  Since the fix involves the 'rfkill' logic it has the potential to
  affect any Bluetooth or Wifi on/off setting.

  [Other info]

  Upstream bug in gnome-bluetooth:
  https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38

  Discussion in linux-bluetooth:
  https://marc.info/?t=16200475893=1=2

  [Original bug report]

  When ever i Turn on my system or restart bluetooth is open any it
  connects to any device. But when i turn off bluetooth and try to turn
  it on again. it neither turns on nor scans/connects to any device.
  This is happening since I updated my system to ubuntu 21.04 LTS

    Bluetooth: hci0: HCI reset during shutdown failed

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 25 15:09:23 2021
  InstallationDate: Installed on 2020-12-15 (130 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 80TR
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago)
  dmi.bios.date: 07/31/2017
  dmi.bios.release: 1.29
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 3UCN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Nano 5B1
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 110-15AST
  dmi.ec.firmware.release: 1.29
  dmi.modalias: 
dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80TR
  dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST
  dmi.product.version: Lenovo ideapad 110-15AST
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: C8:3D:D4:84:E0:06  ACL MTU: 820:8  SCO MTU: 255:16
    DOWN
    RX bytes:744804 acl:76 sco:0 events:105989 errors:0
    TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-bluetooth/+bug/1926062/+subscriptions

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

[Touch-packages] [Bug 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off

[Robie Basak]

Also, the current upload references bug 1933221 which is a dupe. I'm not
sure how SRU tooling will handle this. Unless you can confirm that it
will work, please could you reference the master bug in your upload
instead?

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

Title:
  [hirsute/impish] Can't turn bluetooth on again after turning it off

Status in GNOME Bluetooth:
  Unknown
Status in OEM Priority Project:
  New
Status in bluez package in Ubuntu:
  Fix Committed
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in bluez source package in Focal:
  In Progress
Status in bluez source package in Hirsute:
  In Progress
Status in bluez source package in Impish:
  Fix Committed
Status in gnome-settings-daemon source package in Impish:
  Fix Released

Bug description:
  [Impact]

  On/off of Bluetooth in gnome-control-center will not work properly in kernels 
5.11 (approximately) onward. Devices are not refreshed in the list anymore.
   
  [Test Plan]

  1. Open gnome-control-center and select Bluetooth
  2. Turn off Bluetooth via UI
  3. Turn on Bluetooth via UI

  Expect: Device list appears, so Bluetooth really is on.

  [Where problems could occur]

  Since the fix involves the 'rfkill' logic it has the potential to
  affect any Bluetooth or Wifi on/off setting.

  [Other info]

  Upstream bug in gnome-bluetooth:
  https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38

  Discussion in linux-bluetooth:
  https://marc.info/?t=16200475893=1=2

  [Original bug report]

  When ever i Turn on my system or restart bluetooth is open any it
  connects to any device. But when i turn off bluetooth and try to turn
  it on again. it neither turns on nor scans/connects to any device.
  This is happening since I updated my system to ubuntu 21.04 LTS

    Bluetooth: hci0: HCI reset during shutdown failed

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 25 15:09:23 2021
  InstallationDate: Installed on 2020-12-15 (130 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 80TR
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago)
  dmi.bios.date: 07/31/2017
  dmi.bios.release: 1.29
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 3UCN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Nano 5B1
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 110-15AST
  dmi.ec.firmware.release: 1.29
  dmi.modalias: 
dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80TR
  dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST
  dmi.product.version: Lenovo ideapad 110-15AST
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: C8:3D:D4:84:E0:06  ACL MTU: 820:8  SCO MTU: 255:16
    DOWN
    RX bytes:744804 acl:76 sco:0 events:105989 errors:0
    TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-bluetooth/+bug/1926062/+subscriptions

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

[Touch-packages] [Bug 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off

[Robie Basak]

The fix for this seems missing in Impish. What does "Fix Committed" mean
here? What are your plans to fix this in Impish?

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

Title:
  [hirsute/impish] Can't turn bluetooth on again after turning it off

Status in GNOME Bluetooth:
  Unknown
Status in OEM Priority Project:
  New
Status in bluez package in Ubuntu:
  Fix Committed
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in bluez source package in Focal:
  In Progress
Status in bluez source package in Hirsute:
  In Progress
Status in bluez source package in Impish:
  Fix Committed
Status in gnome-settings-daemon source package in Impish:
  Fix Released

Bug description:
  [Impact]

  On/off of Bluetooth in gnome-control-center will not work properly in kernels 
5.11 (approximately) onward. Devices are not refreshed in the list anymore.
   
  [Test Plan]

  1. Open gnome-control-center and select Bluetooth
  2. Turn off Bluetooth via UI
  3. Turn on Bluetooth via UI

  Expect: Device list appears, so Bluetooth really is on.

  [Where problems could occur]

  Since the fix involves the 'rfkill' logic it has the potential to
  affect any Bluetooth or Wifi on/off setting.

  [Other info]

  Upstream bug in gnome-bluetooth:
  https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38

  Discussion in linux-bluetooth:
  https://marc.info/?t=16200475893=1=2

  [Original bug report]

  When ever i Turn on my system or restart bluetooth is open any it
  connects to any device. But when i turn off bluetooth and try to turn
  it on again. it neither turns on nor scans/connects to any device.
  This is happening since I updated my system to ubuntu 21.04 LTS

    Bluetooth: hci0: HCI reset during shutdown failed

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 25 15:09:23 2021
  InstallationDate: Installed on 2020-12-15 (130 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 80TR
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago)
  dmi.bios.date: 07/31/2017
  dmi.bios.release: 1.29
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 3UCN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Nano 5B1
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 110-15AST
  dmi.ec.firmware.release: 1.29
  dmi.modalias: 
dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80TR
  dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST
  dmi.product.version: Lenovo ideapad 110-15AST
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: C8:3D:D4:84:E0:06  ACL MTU: 820:8  SCO MTU: 255:16
    DOWN
    RX bytes:744804 acl:76 sco:0 events:105989 errors:0
    TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-bluetooth/+bug/1926062/+subscriptions

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

[Touch-packages] [Bug 1933188] Re: package libpam-fprintd:amd64 1.90.9-1~ubuntu20.04.1 failed to install/upgrade: installed libpam-fprintd:amd64 package post-installation script subprocess returned er

[Dan Streetman]

** Package changed: systemd (Ubuntu) => fprintd (Ubuntu)

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

Title:
  package libpam-fprintd:amd64 1.90.9-1~ubuntu20.04.1 failed to
  install/upgrade: installed libpam-fprintd:amd64 package post-
  installation script subprocess returned error exit status 2

Status in fprintd package in Ubuntu:
  New

Bug description:
  Got this problem when doing a regular "Update/upgrade" from shell

  /usr/bin/deb-systemd-invoke: 32 =head1: not found
  /usr/bin/deb-systemd-invoke: 39: Syntax error: newline unexpected

  Endless loop of these two lines in bash before the crash.

  June 22 sentout uopdate

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libpam-fprintd:amd64 1.90.9-1~ubuntu20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-74.83-lowlatency 5.4.114
  Uname: Linux 5.4.0-74-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  AptOrdering:
   alsa-ucm-conf:amd64: Install
   libpam-fprintd:amd64: Install
   fprintd:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Jun 22 06:52:05 2021
  ErrorMessage: installed libpam-fprintd:amd64 package post-installation script 
subprocess returned error exit status 2
  InstallationDate: Installed on 2021-03-29 (84 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.5
  SourcePackage: fprintd
  Title: package libpam-fprintd:amd64 1.90.9-1~ubuntu20.04.1 failed to 
install/upgrade: installed libpam-fprintd:amd64 package post-installation 
script subprocess returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1901922] Re: [SRU][Lenovo ThinkPad T14 Gen 1] No sound output device on startup

[Ladislav Petrus]

This bug occurs sporadically after upgrade to Ubuntu 21.04.  The vlc
workaround works as on 20.10 when the bug occurs.

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

Title:
  [SRU][Lenovo ThinkPad T14 Gen 1] No sound output device on startup

Status in ALSA Libraries:
  Fix Released
Status in alsa-lib package in Ubuntu:
  Fix Released
Status in alsa-ucm-conf package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Focal:
  Fix Released
Status in alsa-ucm-conf source package in Focal:
  Fix Released
Status in alsa-lib source package in Groovy:
  Fix Released
Status in alsa-ucm-conf source package in Groovy:
  Fix Released
Status in alsa-lib source package in Hirsute:
  Fix Released
Status in alsa-ucm-conf source package in Hirsute:
  Fix Released

Bug description:
  [Impact]
  On the machines with AMD Ryzen acp audio design, the audio can't work
  anymore after upgrading the libasound2 to ubuntu3(groovy)/ubuntu2.1(
  focal), this is a regression on libasound2 for those machines. the AMD
  Ryzen acp audio card needs to load ucm to work with pulseaudio, but
  this audio card doesn't have an independant ucm for it, it needs to
  link to an existing HDA-Intel ucm, the check_empty_configuration() needs
  to cover the situation that Linked is true, otherwise it will fail
  to load the ucm for the audio card. Even the audio card could load the
  ucm, the output is muted and the init output volume is too low if
  freshly install the OS on these machines.

  [Fix]
  Backport 1 alsa-lib patch to fix the failure of loading ucm on AMD
  Ryzen acp audio machines. Backport 4 alsa-ucm-conf patches to fix
  init mute and init output volume problem.

  [Test Case]
  Install the updated libasuond2, rm ~/.config/pulse/*; sudo rm -rf
  /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger' and run pacmd
  list-cards, we could see the pulseaudio load the ucm successfully and we 
could see
  the sound card is generated and all output and input devices are listed
  under sound card, but the init output is muted and the volume is very low
  if we manually unumte it. Now install the updated alsa-ucm-conf, rm 
~/.config/pulse/*; sudo rm -rf
  /var/lib/alsa/*; sudo sh -c 'echo b > /proc/sysrq-trigger', the output is
  not muted anymore and the output volume is OK to most users.

  [Regression Risk]
  This could make the machines with sof audio driver fail to load ucm
  , then all audio function can't work as before, like the speaker can't
  output sound or the internal mic can't be found or can't record sound.
  But this possibility is very low, I tested this SRU on some machines with or
  without sof audio driver, all worked as well as before.

  
  After logging in, only a dummy device is available for audio playback 
(resulting in no audible playback). When running "pactl load-module 
module-detect" the sound card shows up, and playback works as expected.

  If pulseaudio is restarted with "pulseaudio -k" the playback device
  disappears again. Running the above command get things working again.

  If I change the following section in /etc/pulse/default.pa from:

  ### Automatically load driver modules depending on the hardware available
  .ifexists module-udev-detect.so
  load-module module-udev-detect
  .else
  ### Use the static hardware detection module (for systems that lack udev 
support)
  load-module module-detect
  .endif

  To:

  ### Automatically load driver modules depending on the hardware available
  #.ifexists module-udev-detect.so
  #load-module module-udev-detect
  #.else
  ### Use the static hardware detection module (for systems that lack udev 
support)
  load-module module-detect
  #.endif

  Things start working as they should after running "pulseaudio -k".

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: pulseaudio 1:13.99.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-26.27-generic 5.8.14
  Uname: Linux 5.8.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Wed Oct 28 17:21:02 2020
  InstallationDate: Installed on 2020-10-23 (4 days ago)
  InstallationMedia: Kubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2020
  dmi.bios.release: 1.9
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1BET40W(1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20UDCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.9
  dmi.modalias: 

[Touch-packages] [Bug 1933188] [NEW] package libpam-fprintd:amd64 1.90.9-1~ubuntu20.04.1 failed to install/upgrade: installed libpam-fprintd:amd64 package post-installation script subprocess returned

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Got this problem when doing a regular "Update/upgrade" from shell

/usr/bin/deb-systemd-invoke: 32 =head1: not found
/usr/bin/deb-systemd-invoke: 39: Syntax error: newline unexpected

Endless loop of these two lines in bash before the crash.

June 22 sentout uopdate

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libpam-fprintd:amd64 1.90.9-1~ubuntu20.04.1
ProcVersionSignature: Ubuntu 5.4.0-74.83-lowlatency 5.4.114
Uname: Linux 5.4.0-74-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu27.18
AptOrdering:
 alsa-ucm-conf:amd64: Install
 libpam-fprintd:amd64: Install
 fprintd:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: skip
Date: Tue Jun 22 06:52:05 2021
ErrorMessage: installed libpam-fprintd:amd64 package post-installation script 
subprocess returned error exit status 2
InstallationDate: Installed on 2021-03-29 (84 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.5
SourcePackage: fprintd
Title: package libpam-fprintd:amd64 1.90.9-1~ubuntu20.04.1 failed to 
install/upgrade: installed libpam-fprintd:amd64 package post-installation 
script subprocess returned error exit status 2
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: init-system-helpers (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal
-- 
package libpam-fprintd:amd64 1.90.9-1~ubuntu20.04.1 failed to install/upgrade: 
installed libpam-fprintd:amd64 package post-installation script subprocess 
returned error exit status 2
https://bugs.launchpad.net/bugs/1933188
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to init-system-helpers in Ubuntu.

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

[Touch-packages] [Bug 1933188] Re: package libpam-fprintd:amd64 1.90.9-1~ubuntu20.04.1 failed to install/upgrade: installed libpam-fprintd:amd64 package post-installation script subprocess returned er

[Dan Streetman]

you seem to have some problem with /usr/bin/deb-systemd-invoke, which is
a perl script, but it seems to be getting called by /bin/sh. You should
try reinstalling init-system-helpers to fix any problem with your
script, and/or if you made any changes yourself manually that may be
causing the problem.

$ sudo apt --reinstall install init-system-helpers

** Package changed: fprintd (Ubuntu) => init-system-helpers (Ubuntu)

** Changed in: init-system-helpers (Ubuntu)
   Status: New => Incomplete

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

Title:
  package libpam-fprintd:amd64 1.90.9-1~ubuntu20.04.1 failed to
  install/upgrade: installed libpam-fprintd:amd64 package post-
  installation script subprocess returned error exit status 2

Status in init-system-helpers package in Ubuntu:
  Incomplete

Bug description:
  Got this problem when doing a regular "Update/upgrade" from shell

  /usr/bin/deb-systemd-invoke: 32 =head1: not found
  /usr/bin/deb-systemd-invoke: 39: Syntax error: newline unexpected

  Endless loop of these two lines in bash before the crash.

  June 22 sentout uopdate

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libpam-fprintd:amd64 1.90.9-1~ubuntu20.04.1
  ProcVersionSignature: Ubuntu 5.4.0-74.83-lowlatency 5.4.114
  Uname: Linux 5.4.0-74-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  AptOrdering:
   alsa-ucm-conf:amd64: Install
   libpam-fprintd:amd64: Install
   fprintd:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Jun 22 06:52:05 2021
  ErrorMessage: installed libpam-fprintd:amd64 package post-installation script 
subprocess returned error exit status 2
  InstallationDate: Installed on 2021-03-29 (84 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.5
  SourcePackage: fprintd
  Title: package libpam-fprintd:amd64 1.90.9-1~ubuntu20.04.1 failed to 
install/upgrade: installed libpam-fprintd:amd64 package post-installation 
script subprocess returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()

[Mathew Hodson]

** Bug watch removed: gitlab.freedesktop.org/mesa/mesa/issues #1358
   https://gitlab.freedesktop.org/mesa/mesa/issues/1358

** Bug watch removed: gitlab.freedesktop.org/mesa/mesa/-/issues #4275
   https://gitlab.freedesktop.org/mesa/mesa/-/issues/4275

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

Title:
  Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()

Status in Mesa:
  Unknown
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf
  https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a
  https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f

  ---

  nothing particular done to trigger this, just opening the lid
  apparently crashed the x server (ubuntu 20.04); then after reboot
  apport prompted me to report a crash

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.7-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Apr 10 00:50:52 2020
  DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56
  DistroCodename: focal
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
     Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9]
  InstallationDate: Installed on 2019-11-27 (134 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 003: ID 8087:0029 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 5500
  ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth 
/run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet 
splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
   __GI_abort () at abort.c:79
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  Title: Xorg crashed with SIGABRT in __GI_raise()
  UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago)
  UserGroups:

  dmi.bios.date: 08/21/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 0M14W7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5500
  dmi.product.sku: 08B9
  dmi.sys.vendor: Dell Inc.
  separator:

  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1918855] Re: Xorg xserver got signal 6 to abort

[Mathew Hodson]

** Merge proposal unlinked:
   
https://code.launchpad.net/~os369510/plainbox-provider-checkbox/+git/plainbox-provider-checkbox/+merge/403448

** Project changed: plainbox-provider-checkbox => ubuntu-translations

** No longer affects: ubuntu-translations

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

Title:
  Xorg xserver got signal 6 to abort

Status in OEM Priority Project:
  In Progress
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Focal:
  New
Status in mesa source package in Hirsute:
  New

Bug description:
  == SRU Justification ==
  [Impact]
  When the system is under memory pressure, the entire desktop session may 
crash.

  [Fix]
  Commit f9d8d9acbb6a620684fb4dac4affe25816587d92 ("iris: Avoid abort() if 
kernel can't allocate memory")

  [Test]
  Run memory stress and the session crashed in less than 5 minutes.
  With the fix applied, run memory stress for 24 hours and the desktop session 
is still alive.

  [Where problems could occur]
  Doing a reset might make the system even more sluggish when under memory 
pressure.

  
  == Original bug report ==
  I run checkbox job com.canonical.certification::memory/memory_stress_ng on 
focal, and the xserver stops unexpectedly with the following stacktrace:

  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 0: /usr/lib/xorg/Xorg 
(OsLookupColor+0x13c) [0x5619f3a4d59c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 1: 
/lib/x86_64-linux-gnu/libpthread.so.0 (funlockfile+0x60) [0x7fae4786741f]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 
(gsignal+0xcb) [0x7fae476a418b]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 3: /lib/x86_64-linux-gnu/libc.so.6 
(abort+0x12b) [0x7fae47683859]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind 
info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 4: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (?+0x0) [0x7fae457d7aec]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 5: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so (nouveau_drm_screen_create+0x25c8ec) 
[0x7fae46529c9c]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 6: 
/usr/lib/x86_64-linux-gnu/dri/iris_dri.so 
(__driDriverGetExtensions_zink+0x2561d) [0x7fae4582c74d]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 7: 
/usr/lib/xorg/modules/libglamoregl.so (glamor_destroy_pixmap+0x150) 
[0x7fae47007480]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) unw_get_proc_name failed: no unwind 
info found [-10]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 8: 
/usr/lib/xorg/modules/drivers/modesetting_drv.so (?+0x0) [0x7fae47040a30]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 9: /usr/lib/xorg/Xorg 
(BlockHandler+0xa5) [0x5619f38f0995]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 10: /usr/lib/xorg/Xorg 
(WaitForSomething+0x122) [0x5619f3a46c12]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 11: /usr/lib/xorg/Xorg 
(SendErrorToClient+0x117) [0x5619f38ebcf7]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 12: /usr/lib/xorg/Xorg 
(InitFonts+0x3b4) [0x5619f38effc4]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf3) [0x7fae476850b3]
  /usr/lib/gdm3/gdm-x-session[1425]: (EE) 14: /usr/lib/xorg/Xorg (_start+0x2e) 
[0x5619f38d9a2e]

  More info:
  I searched the Internet and got a bug with the same stacktrace:
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/3468
  https://gitlab.freedesktop.org/mesa/mesa/-/issues/2859

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1918855/+subscriptions

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

[Touch-packages] [Bug 1918955] Re: SRU network: fix LXC_NET_NONE cleanup

[Scott Moser]

Marking this fix-released in focal as bug 1923232 was released to focal.
So this should be fixed in '1:4.0.6-0ubuntu1~20.04.1'.


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

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

Title:
  SRU network: fix LXC_NET_NONE cleanup

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Focal:
  Fix Released
Status in lxc source package in Groovy:
  Confirmed
Status in lxc source package in Hirsute:
  Fix Released

Bug description:
  Hi.  I'm using 20.04, and I need a fix for
  https://github.com/lxc/lxc/pull/3589

  I think my only options to get that via packaging are
   a.) https://launchpad.net/~ubuntu-lxc/+archive/ubuntu/lxc-git-master
   b.) build my own.

  I don't love either of those options.

  Can we please get a SRU update to 20.04 of an lxc with that fix?

  The fix is not in 4.0.5, so I marked this as affecting Groovy
  (currently 1:4.0.4-0ubuntu3) without testing.

  Related bugs:
   * bug 1923232:  SRU of LXC 4.0.6 to focal (upstream bugfix release)

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

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

[Touch-packages] [Bug 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off

[Andy Chi]

Hi @Daniel,
I created a public bug in github/bluez, mp is sent by maintainer.
https://github.com/bluez/bluez/issues/162

** Bug watch added: github.com/bluez/bluez/issues #162
   https://github.com/bluez/bluez/issues/162

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

Title:
  [hirsute/impish] Can't turn bluetooth on again after turning it off

Status in GNOME Bluetooth:
  Unknown
Status in OEM Priority Project:
  New
Status in bluez package in Ubuntu:
  Fix Committed
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in bluez source package in Focal:
  In Progress
Status in bluez source package in Hirsute:
  In Progress
Status in bluez source package in Impish:
  Fix Committed
Status in gnome-settings-daemon source package in Impish:
  Fix Released

Bug description:
  [Impact]

  On/off of Bluetooth in gnome-control-center will not work properly in kernels 
5.11 (approximately) onward. Devices are not refreshed in the list anymore.
   
  [Test Plan]

  1. Open gnome-control-center and select Bluetooth
  2. Turn off Bluetooth via UI
  3. Turn on Bluetooth via UI

  Expect: Device list appears, so Bluetooth really is on.

  [Where problems could occur]

  Since the fix involves the 'rfkill' logic it has the potential to
  affect any Bluetooth or Wifi on/off setting.

  [Other info]

  Upstream bug in gnome-bluetooth:
  https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38

  Discussion in linux-bluetooth:
  https://marc.info/?t=16200475893=1=2

  [Original bug report]

  When ever i Turn on my system or restart bluetooth is open any it
  connects to any device. But when i turn off bluetooth and try to turn
  it on again. it neither turns on nor scans/connects to any device.
  This is happening since I updated my system to ubuntu 21.04 LTS

    Bluetooth: hci0: HCI reset during shutdown failed

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 25 15:09:23 2021
  InstallationDate: Installed on 2020-12-15 (130 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 80TR
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago)
  dmi.bios.date: 07/31/2017
  dmi.bios.release: 1.29
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 3UCN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Nano 5B1
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 110-15AST
  dmi.ec.firmware.release: 1.29
  dmi.modalias: 
dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80TR
  dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST
  dmi.product.version: Lenovo ideapad 110-15AST
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: C8:3D:D4:84:E0:06  ACL MTU: 820:8  SCO MTU: 255:16
    DOWN
    RX bytes:744804 acl:76 sco:0 events:105989 errors:0
    TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-bluetooth/+bug/1926062/+subscriptions

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

[Touch-packages] [Bug 1871959] Re: Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()

[paquin pierre]

Well, maybe or not but I don't understand how to install the patch

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

Title:
  Xorg crashed with SIGABRT in _iris_batch_flush from iris_fence_flush()

Status in Mesa:
  Unknown
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/23a23997d8d3287584722beeaee600306df3a1bf
  https://errors.ubuntu.com/problem/d9ee437c6ea3330d18aecaa0d3e07f71ca0c8d1a
  https://errors.ubuntu.com/problem/a960bab710b867c695551df03b8207cdc0da9a6f

  ---

  nothing particular done to trigger this, just opening the lid
  apparently crashed the x server (ubuntu 20.04); then after reboot
  apport prompted me to report a crash

  ProblemType: Crash
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.7-2ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu25
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: GNOME-Greeter:GNOME
  Date: Fri Apr 10 00:50:52 2020
  DistUpgraded: 2019-12-20 18:35:39,979 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-bionic-amd64-20180608-47+north-bay-14-15-15p+X56
  DistroCodename: focal
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
     Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08b9]
  InstallationDate: Installed on 2019-11-27 (134 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:5532 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 003: ID 8087:0029 Intel Corp.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude 5500
  ProcCmdline: /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth 
/run/user/120/gdm/Xauthority -background none -noreset -keeptty -verbose 3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic 
root=UUID=559b7a9d-8198-424b-8812-ea72c10f013e ro mem_sleep_default=deep quiet 
splash vt.handoff=7
  Signal: 6
  SourcePackage: xorg-server
  StacktraceTop:
   __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
   __GI_abort () at abort.c:79
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so
  Title: Xorg crashed with SIGABRT in __GI_raise()
  UpgradeStatus: Upgraded to focal on 2019-12-20 (111 days ago)
  UserGroups:

  dmi.bios.date: 08/21/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.1
  dmi.board.name: 0M14W7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnLatitude5500:pvr:rvnDellInc.:rn0M14W7:rvrA01:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 5500
  dmi.product.sku: 08B9
  dmi.sys.vendor: Dell Inc.
  separator:

  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1929657] Re: [Ubuntu 20.4.2] vLan not getting static IP assigned (on s390x)

[Lukas Märdian]

After crushing the logs a bit more, I found a few interesting things and
also have a few open questions. Thank you very much for your `date`
timestamps in between the different steps, those are very helpful in
linking the order of events!

Open questions:
1) The "udevadm-monitor.txt" log shows that there is a manual 
"/etc/systemd/network/10-enP53p0s0.link" configuration file, while all other 
interfaces make use of "/usr/lib/systemd/network/99-default.link". Can you show 
us what is inside this file?

2) In comment #22 you show the output of "networkctl":
root@ilabg13:~# netplan apply
root@ilabg13:~# networkctl status enP53p0s0.171 --no-pager
? 7: enP53p0s0.171
Link File: n/a
Network File: n/a
Type: vlan
State: degraded (pending)
HW Address: 82:0c:9b:c9:78:f8

=> I wonder why "Link File: n/a" and "Network File: n/a" is set.. The
Link state is still "(pending)", would you mind executing the same steps
again and re-executing the "networkctl status enP53p0s0.171 --no-pager"
a bit later again (like 10sec after and 30sec after)?

3) Does the workaround from
https://github.com/systemd/systemd/issues/15445#issuecomment-776856604
work for you? E.g.:

# netplan apply
- wait 15 sec
# networkctl reload
- wait 15 sec
# networkctl renew enP53p0s0.171
- wait 15 sec  
# networkctl reconfigure enP53p0s0.171
- wait 15 sec
# networkctl reconfigure enP53p0s0.171
- wait 30 sec
# networkctl status enP53p0s0.171 --no-pager
# ip a

=== Findings from comment #33 (journalctl_udev_monitor.txt) ===
You executed "netplan apply" between 08:10:29 - 08:10:59 and it looks like 
systemd-networkd found the correct netplan-*.network configuration and applied 
it (assigned the IP) at 08:10:57. See "***" lines:

Jun 15 08:10:57 systemd-networkd[182847]: enP53p0s0.171: Link state is 
up-to-date
*** Jun 15 08:10:57 systemd-networkd[182847]: enP53p0s0.171: found matching 
network '/run/systemd/network/10-netplan-enP53p0s0.171.network'
Jun 15 08:10:57 systemd-networkd[182847]: Setting 
'/proc/sys/net/ipv6/conf/enP53p0s0.171/disable_ipv6' to '0'
Jun 15 08:10:57 systemd-networkd[182847]: enP53p0s0.171: IPv6 successfully 
enabled
Jun 15 08:10:57 systemd-networkd[182847]: Setting 
'/proc/sys/net/ipv6/conf/enP53p0s0.171/proxy_ndp' to '0'
Jun 15 08:10:57 systemd-networkd[182847]: Setting 
'/proc/sys/net/ipv6/conf/enP53p0s0.171/use_tempaddr' to '0'
Jun 15 08:10:57 systemd-networkd[182847]: Setting 
'/proc/sys/net/ipv6/conf/enP53p0s0.171/accept_ra' to '0'
Jun 15 08:10:57 systemd-networkd[182847]: LLDP: Started LLDP client
Jun 15 08:10:57 systemd-networkd[182847]: enP53p0s0.171: Started LLDP.
Jun 15 08:10:57 systemd-networkd[182847]: enP53p0s0.171: Setting address 
genmode for link
[...]
*** Jun 15 08:10:57 systemd-networkd[182847]: enP53p0s0.171: Remembering 
updated address: 192.168.171.53/24 (valid forever)
Jun 15 08:10:57 systemd-networkd[182847]: Sent message type=signal sender=n/a 
destination=n/a path=/org/freedesktop/network1/link/_37 
interface=org.freedesktop.DBus.Properties member=PropertiesChanged cookie=45 
reply_cookie=0 signature=sa{sv}as error-name=n/a error-message=n/a
Jun 15 08:10:57 systemd-networkd[182847]: enP53p0s0.171: Remembering route: 
dst: 192.168.171.53/32, src: n/a, gw: n/a, prefsrc: 192.168.171.53, scope: 
host, table: local, proto: kernel, type: local
Jun 15 08:10:57 systemd-networkd[182847]: enP53p0s0.171: Remembering route: 
dst: 192.168.171.255/32, src: n/a, gw: n/a, prefsrc: 192.168.171.53, scope: 
link, table: local, proto: kernel, type: broadcast
Jun 15 08:10:57 systemd-networkd[182847]: enP53p0s0.171: Remembering route: 
dst: 192.168.171.0/24, src: n/a, gw: n/a, prefsrc: 192.168.171.53, scope: link, 
table: main, proto: kernel, type: unicast
Jun 15 08:10:57 systemd-networkd[182847]: enP53p0s0.171: Remembering route: 
dst: 192.168.171.0/32, src: n/a, gw: n/a, prefsrc: 192.168.171.53, scope: link, 
table: local, proto: kernel, type: broadcast
*** Jun 15 08:10:57 systemd-networkd[182847]: enP53p0s0.171: Addresses set
*** Jun 15 08:10:57 systemd-networkd[182847]: enP53p0s0.171: State changed: 
configuring -> configured
[...]
Jun 15 08:11:28 systemd-udevd[182946]: enP53p0s0.171: Processing device 
(SEQNUM=87120, ACTION=change) 
Jun 15 08:11:28 systemd-udevd[182940]: enP50s3832: 
/usr/lib/udev/rules.d/75-net-description.rules:12 Importing properties from 
results of builtin command 'hwdb --subsystem=pci' 
Jun 15 08:11:28 systemd-udevd[182946]: enP53p0s0.171: 
/usr/lib/udev/rules.d/75-net-description.rules:6 Importing properties from 
results of builtin command 'net_id' 
Jun 15 08:11:28 systemd-udevd[182946]: enP53p0s0.171: 
/usr/lib/udev/rules.d/80-net-setup-link.rules:5 Importing properties from 
results of builtin command 'path_id' 
Jun 15 08:11:28 systemd-udevd[182946]: enP53p0s0.171: 
/usr/lib/udev/rules.d/80-net-setup-link.rules:5 Failed to run builtin 
'path_id': No such file or directory 
Jun 15 08:11:28 systemd-udevd[182946]: enP53p0s0.171: 
/usr/lib/udev/rules.d/80-net-setup-link.rules:9 Importing properties from 

[Touch-packages] [Bug 1933361] Re: Audio Problem, soundcard not detected

[Víctor]

Added aditional info.

** Attachment added: "lspcik.txt"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1933361/+attachment/5506502/+files/lspcik.txt

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

Title:
  Audio Problem, soundcard not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hi,

  After last patch in Ubuntu 20.04.2 LTS, I have lost my audio.

  I have got an Asus monitor with speakers inside the monitor. The sound
  come to the monitor from the HDMI cable.

  My GPU is an GTX 1080 Ti.

  I have got a KVM Switch in which is connected my monitor, Keyboard and
  Mouse.

  Before the last update of Ubuntu, all worked well.

  When I go to settings in Ubuntu, I couldn't watch any audio device
  check the image attached.

  Regards.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-22.23~20.04.1-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 23 17:30:22 2021
  InstallationDate: Installed on 2021-01-14 (159 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/04/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3001
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X570-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3001:bd12/04/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1933361/+subscriptions

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

[Touch-packages] [Bug 1925742] Re: Recent iCloud versions trigger an issue in IMAP x

[Marian Rainer-Harbach]

I tested evolution-data-server version 3.40.0-1ubuntu1.1 from proposed
in Hirsute. I can confirm that iCloud accounts can be accessed again.

Thanks for your work, Brian, Sebastien and Iain!

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

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

Title:
  Recent iCloud versions trigger an issue in IMAP x

Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in evolution-data-server source package in Focal:
  Fix Released
Status in evolution-data-server source package in Hirsute:
  Fix Committed

Bug description:
  * Impact

  The Icloud service introduced changes that are confusing evolution-
  data-server which means evolution is now failing to connect to the
  email server

  * Test case

  Set up an iCloud account and try to use it for emails in evolution

  * Regression potential

  The change is in the imapx connection code, it could create problems
  with other type of servers so we should try to test on different
  providers.

  
  -


  The bug has been fixed yesterday by Evolution's developer:
  https://gitlab.gnome.org/GNOME/evolution/-/issues/1468

  However, the package in Ubuntu (at least in Focal Fosa) still needs to
  be updated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1925742/+subscriptions

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

[Touch-packages] [Bug 1925745] Re: Hirsute: Cannot install ubuntu-desktop due to unmet dependencies

[Marian Rainer-Harbach]

Similar to what Dan wrote in comment #10, my original test case of
installing ubuntu-desktop now works even without enabling the proposed
repository. So unfortunately I cannot verify the fix now since I cannot
reproduce the original error.

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

Title:
  Hirsute: Cannot install ubuntu-desktop due to unmet dependencies

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Hirsute:
  Fix Committed
Status in apt source package in Impish:
  Fix Released

Bug description:
  [Impact]
  Phased upgrades were only applied to already installed packages, so if we had 
a source package foo building foo-core and foo-extra, and foo-core=1 was 
installed, and we tried to install foo-extra, it would fail because it would 
try to install 0% foo-extra=2 while blocking foo-core as it's "not for us".

  [Test Plan]
  The autopkgtests ensure we don't regress and they kind of check this by 
checking the policy output to see that "foo-extra=2" above is also not the 
candidate, but foo-extra=1 is (so installing it alongside foo-core=1 would work 
fine) but they don't install it, so it might be nice to verify this too:

  Find a package that is phased, but not for us (maybe just setting the
  never-include-phased flag?), install one binary from it from the
  release pocket, and then try to install another from the updates
  pocket.

  At the moment, installing libsystemd-dev would trigger it.

  [Where problems could occur]
  This is a change in behavior when installing new packages that might cause 
regression in image building tools for example, if those don't use a chroot 
(chroots being detected).

  Apart from that risk, the change is just removing a flag check inside
  an if, so not much else.

  [Original bug report]

  I'm using the ubuntu-21.04-live-server-amd64 ISO to install my hirsute
  desktop machines so I can automate the installation.

  After installation, I'm trying to install the desktop via "apt install
  ubuntu-desktop".

  This fails with:
  "Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   ubuntu-release-upgrader-gtk : Depends: ubuntu-release-upgrader-core (= 
1:21.04.11) but 1:21.04.10 is to be installed
     Depends: python3-distupgrade (= 1:21.04.11) 
but 1:21.04.10 is to be installed
  E: Unable to correct problems, you have held broken packages."

  "apt policy ubuntu-release-upgrader-core" shows:
  "ubuntu-release-upgrader-core:
    Installed: 1:21.04.10
    Candidate: 1:21.04.10
    Version table:
   1:21.04.11 1 (phased 20%)
  500 http://at.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 
Packages
   *** 1:21.04.10 500
  500 http://at.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
  100 /var/lib/dpkg/status"

  I could not find any information what "phased 20%" means. It's
  obviously a major problem not being able to install the desktop on a
  fresh installation.

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

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

[Touch-packages] [Bug 1933359] [NEW] [Ubuntu 21.10][Broadcom] mpi3mr driver submission request

[Sumit Saxena]

Public bug reported:

Broadcom is coming up with next generation high performance Storage IO and RAID 
controllers. For details, follow: 
https://www.spinics.net/lists/linux-scsi/msg147868.html
This family of controllers is managed by "mpi3mr" Linux device driver(written 
from scratch). First patchset of the driver is accepted by Linux upstream.
The driver is available in git branch - 5.14/scsi-staging of Linux SCSI tree: 
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git
The driver will be part of 5.14 mainline Linux kernel release. Here is the list 
of commit ids:

9fc4abfe5a5f scsi: mpi3mr: Add event handling debug prints
74e1f30a2868 scsi: mpi3mr: Add EEDP DIF DIX support
28cbe2f420d3 scsi: mpi3mr: Add support for DSN secure firmware check
2f9c4d520aa6 scsi: mpi3mr: Add support for PM suspend and resume
44dc724f5eec scsi: mpi3mr: Wait for pending I/O completions upon detection of 
VD I/O timeout
71e80106d059 scsi: mpi3mr: Print pending host I/Os for debugging
f061178e0762 scsi: mpi3mr: Complete support for soft reset
463429f8dd5c scsi: mpi3mr: Add support for threaded ISR
392bbeb85b2a scsi: mpi3mr: Hardware workaround for UNMAP commands to NVMe drives
82141ddba90a scsi: mpi3mr: Allow certain commands during pci-remove hook
0ea177343f1f scsi: mpi3mr: Add change queue depth support
e844adb1fbdc scsi: mpi3mr: Implement SCSI error handler hooks
8f9c6173ca46 scsi: mpi3mr: Add bios_param SCSI host template hook
ff9561e910fc scsi: mpi3mr: Print IOC info for debugging
54dfcffb4191 scsi: mpi3mr: Add support for timestamp sync with firmware
fb9b04574f14 scsi: mpi3mr: Add support for recovering controller
e36710dc06e3 scsi: mpi3mr: Additional event handling
8e653455547a scsi: mpi3mr: Add support for PCIe device event handling
13ef29ea4aa0 scsi: mpi3mr: Add support for device add/remove event handling
672ae26c8216 scsi: mpi3mr: Add support for internal watchdog thread
023ab2a9b4ed scsi: mpi3mr: Add support for queue command processing
c9566231cfaf scsi: mpi3mr: Create operational request and reply queue pair
824a156633df scsi: mpi3mr: Base driver code
c4f7ac64616e scsi: mpi3mr: Add mpi30 Rev-R headers and Kconfig

Please include this driver in Ubuntu 21.10 release.
Let me know for any questions.

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

** Summary changed:

- Broadcom latest IO and RAID storage controller driver mpi3mr inclusion in 
Ubuntu 21.10
+ [Ubuntu 21.10][Broadcom] mpi3mr driver submission request

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

Title:
  [Ubuntu 21.10][Broadcom] mpi3mr driver submission request

Status in lxc package in Ubuntu:
  New

Bug description:
  Broadcom is coming up with next generation high performance Storage IO and 
RAID controllers. For details, follow: 
https://www.spinics.net/lists/linux-scsi/msg147868.html
  This family of controllers is managed by "mpi3mr" Linux device driver(written 
from scratch). First patchset of the driver is accepted by Linux upstream.
  The driver is available in git branch - 5.14/scsi-staging of Linux SCSI tree: 
https://git.kernel.org/pub/scm/linux/kernel/git/mkp/scsi.git
  The driver will be part of 5.14 mainline Linux kernel release. Here is the 
list of commit ids:

  9fc4abfe5a5f scsi: mpi3mr: Add event handling debug prints
  74e1f30a2868 scsi: mpi3mr: Add EEDP DIF DIX support
  28cbe2f420d3 scsi: mpi3mr: Add support for DSN secure firmware check
  2f9c4d520aa6 scsi: mpi3mr: Add support for PM suspend and resume
  44dc724f5eec scsi: mpi3mr: Wait for pending I/O completions upon detection of 
VD I/O timeout
  71e80106d059 scsi: mpi3mr: Print pending host I/Os for debugging
  f061178e0762 scsi: mpi3mr: Complete support for soft reset
  463429f8dd5c scsi: mpi3mr: Add support for threaded ISR
  392bbeb85b2a scsi: mpi3mr: Hardware workaround for UNMAP commands to NVMe 
drives
  82141ddba90a scsi: mpi3mr: Allow certain commands during pci-remove hook
  0ea177343f1f scsi: mpi3mr: Add change queue depth support
  e844adb1fbdc scsi: mpi3mr: Implement SCSI error handler hooks
  8f9c6173ca46 scsi: mpi3mr: Add bios_param SCSI host template hook
  ff9561e910fc scsi: mpi3mr: Print IOC info for debugging
  54dfcffb4191 scsi: mpi3mr: Add support for timestamp sync with firmware
  fb9b04574f14 scsi: mpi3mr: Add support for recovering controller
  e36710dc06e3 scsi: mpi3mr: Additional event handling
  8e653455547a scsi: mpi3mr: Add support for PCIe device event handling
  13ef29ea4aa0 scsi: mpi3mr: Add support for device add/remove event handling
  672ae26c8216 scsi: mpi3mr: Add support for internal watchdog thread
  023ab2a9b4ed scsi: mpi3mr: Add support for queue command processing
  c9566231cfaf scsi: mpi3mr: Create operational request and reply queue pair
  824a156633df scsi: mpi3mr: Base driver code
  c4f7ac64616e scsi: mpi3mr: Add mpi30 Rev-R headers and Kconfig

  Please include this 

[Touch-packages] [Bug 1933361] [NEW] Audio Problem, soundcard not detected

[Víctor]

Public bug reported:

Hi,

After last patch in Ubuntu 20.04.2 LTS, I have lost my audio.

I have got an Asus monitor with speakers inside the monitor. The sound
come to the monitor from the HDMI cable.

My GPU is an GTX 1080 Ti.

I have got a KVM Switch in which is connected my monitor, Keyboard and
Mouse.

Before the last update of Ubuntu, all worked well.

When I go to settings in Ubuntu, I couldn't watch any audio device check
the image attached.

Regards.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.11.0-22.23~20.04.1-generic 5.11.21
Uname: Linux 5.11.0-22-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Jun 23 17:30:22 2021
InstallationDate: Installed on 2021-01-14 (159 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Title: PCI/internal sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/04/2020
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3001
dmi.board.asset.tag: Default string
dmi.board.name: PRIME X570-PRO
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3001:bd12/04/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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


** Tags: amd64 apport-bug focal third-party-packages

** Attachment added: "Captura de pantalla de 2021-06-23 17-35-37.png"
   
https://bugs.launchpad.net/bugs/1933361/+attachment/5506495/+files/Captura%20de%20pantalla%20de%202021-06-23%2017-35-37.png

** Description changed:

  Hi,
  
  After last patch in Ubuntu 20.04.2 LTS, I have lost my audio.
  
  I have got an Asus monitor with speakers inside the monitor. The sound
  come to the monitor from the HDMI cable.
  
  My GPU is an GTX 1080 Ti.
  
+ I have got a KVM Switch in which is connected my Screen, Keyboard and
+ Mouse.
+ 
+ Before the last update of Ubuntu, all worked well.
+ 
  When I go to settings in Ubuntu, I couldn't watch any audio device check
  the image attached.
- 
  
  Regards.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-22.23~20.04.1-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 23 17:30:22 2021
  InstallationDate: Installed on 2021-01-14 (159 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  ProcEnviron:
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=es_ES.UTF-8
-  SHELL=/bin/bash
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=es_ES.UTF-8
+  SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/04/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3001
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X570-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3001:bd12/04/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

** Description changed:

  Hi,
  
  After last patch in Ubuntu 20.04.2 LTS, I have lost my audio.
  
  I have got an Asus monitor with speakers inside the monitor. The sound
  come to the monitor from 

[Touch-packages] [Bug 1933361] Re: Audio Problem, soundcard not detected

[Víctor]

Added aditional info.

** Attachment added: "prevboot.txt"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1933361/+attachment/5506501/+files/prevboot.txt

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

Title:
  Audio Problem, soundcard not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hi,

  After last patch in Ubuntu 20.04.2 LTS, I have lost my audio.

  I have got an Asus monitor with speakers inside the monitor. The sound
  come to the monitor from the HDMI cable.

  My GPU is an GTX 1080 Ti.

  I have got a KVM Switch in which is connected my monitor, Keyboard and
  Mouse.

  Before the last update of Ubuntu, all worked well.

  When I go to settings in Ubuntu, I couldn't watch any audio device
  check the image attached.

  Regards.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-22.23~20.04.1-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 23 17:30:22 2021
  InstallationDate: Installed on 2021-01-14 (159 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/04/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3001
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X570-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3001:bd12/04/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1933361/+subscriptions

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

[Touch-packages] [Bug 1933361] Re: Audio Problem, soundcard not detected

[Hui Wang]

You forgot to install linux-modules-extra package, the audio driver is
in that package.

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

Title:
  Audio Problem, soundcard not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hi,

  After last patch in Ubuntu 20.04.2 LTS, I have lost my audio.

  I have got an Asus monitor with speakers inside the monitor. The sound
  come to the monitor from the HDMI cable.

  My GPU is an GTX 1080 Ti.

  I have got a KVM Switch in which is connected my monitor, Keyboard and
  Mouse.

  Before the last update of Ubuntu, all worked well.

  When I go to settings in Ubuntu, I couldn't watch any audio device
  check the image attached.

  Regards.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-22.23~20.04.1-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun 23 17:30:22 2021
  InstallationDate: Installed on 2021-01-14 (159 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/04/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3001
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X570-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3001:bd12/04/2020:br5.17:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX570-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1933361/+subscriptions

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

[Touch-packages] [Bug 1931088] Re: boot-and-services tests fails in impish on armhf (248.3)

[Lukas Märdian]

Looks like I can at least reproduce the issue on an arm64 Canonistack
machine, utilizing an armhf container:

ubuntu@focal-arm64:~$ time autopkgtest systemd --test-name=boot-and-services -U 
-- lxd autopkgtest/ubuntu/impish/armhf
[...]
autopkgtest [15:59:21]: test boot-and-services: [---
lxc
Created symlink /etc/systemd/system/default.target → 
/lib/systemd/system/graphical.target.
bash: line 1:  3532 Killed  
/tmp/autopkgtest.OAYOpR/build.yrL/src/debian/tests/boot-and-services 2> >(tee 
-a /tmp/autopkgtest.OAYOpR/boot-and-services-stderr >&2) > >(tee -a 
/tmp/autopkgtest.OAYOpR/boot-and-services-stdout)
autopkgtest [15:59:24]: test process requested reboot with marker boot1
Unexpected error:
Traceback (most recent call last):
  File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 738, in mainloop
command()
  File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 667, in command
r = f(c, ce)
  File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 363, in cmd_reboot
caller.hook_wait_reboot()
  File "/usr/bin/autopkgtest-virt-lxd", line 231, in hook_wait_reboot
wait_booted()
  File "/usr/bin/autopkgtest-virt-lxd", line 104, in wait_booted
VirtSubproc.check_exec(['lxc', 'exec', container_name, '--', 'sh', '-ec', 
'[ ! -d /run/systemd/system ] || systemctl start network-online.target'], 
timeout=60)
  File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 182, in check_exec
(status, out, err) = execute_timeout(None, timeout, real_argv,
  File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 144, in execute_timeout
(out, err) = sp.communicate(instr)
  File "/usr/lib/python3.8/subprocess.py", line 1014, in communicate
stderr = self.stderr.read()
  File "/usr/share/autopkgtest/lib/VirtSubproc.py", line 64, in alarm_handler
raise Timeout()
VirtSubproc.Timeout
autopkgtest [16:01:18]: ERROR: testbed failure: unexpected eof from the testbed

real8m29.354s
user0m8.866s
sys 0m8.141s


Let's see what we can do about it. It looks like a dnsmasq (security-)update 
was pushed to Bionic++ on 2021-06-02 – about the same time that this test 
started failing on Bionic++ ... I wonder if this might somehow be related? ... 
need to further investigate.

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

Title:
  boot-and-services tests fails in impish on armhf (248.3)

Status in Auto Package Testing:
  Incomplete
Status in dnsmasq package in Ubuntu:
  Incomplete
Status in gdm3 package in Ubuntu:
  Incomplete
Status in glibc package in Ubuntu:
  Incomplete
Status in isc-dhcp package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  Confirmed
Status in dnsmasq source package in Impish:
  Incomplete
Status in gdm3 source package in Impish:
  Incomplete
Status in glibc source package in Impish:
  Incomplete
Status in isc-dhcp source package in Impish:
  Incomplete
Status in systemd source package in Impish:
  Confirmed

Bug description:
  Systemd 248.3-1ubuntu1 is rather new, but had 5 successful tests on armhf
  before now slipping into a bad mode.

  Now it seems all tests failed in boot-and-services by hanging until killed by
  VirtSubproc.Timeout of autokgtest.

  The last [1] test log has a bit more, it shows a python stack overflow
  ```
 VirtSubproc.Timeout
 Fatal Python error: Cannot recover from stack overflow.
 Python runtime state: initialized

 Current thread 0x7f108e840740 (most recent call first):
   File "/home/ubuntu/autopkgtest/lib/adtlog.py", line 36 in log
   File "/home/ubuntu/autopkgtest/lib/adtlog.py", line 86 in debug
   File "/home/ubuntu/autopkgtest/lib/adt_testbed.py", line 472 in send
   File "/home/ubuntu/autopkgtest/lib/adt_testbed.py", line 521 in command
  ```

  I have seen a bunch of packages including even gdm3 and glibc being blocked by
  that so I wanted to at least track down the issue until we can put it on
  someones task list to resolve.
  No one replied to my pings yet, but maybe that means someone is already
  debugging this and had enabled some debugging?

  By running the same in armhf container on arm64 VM on canonistack I've seen
  no issues. The test worked fine and had no hang/issues.

  root@systemd-test-fail:~/systemd-248.3# ./debian/tests/boot-and-services
  lxc
  1
  test_profile (__main__.AppArmorTest)
  AppArmor confined unit ... skipped 'fails on armhf testbeds, see LP: #1842352'
  test_help (__main__.CLITest)
  --help works and succeeds ... ok
  test_invalid_option (__main__.CLITest)
  Calling with invalid option fails ... ok
  test_version (__main__.CLITest)
  --version works and succeeds ... ok
  test_cpushares (__main__.CgroupsTest)
  service with CPUShares ... ok
  test_simple (__main__.CgroupsTest)
  simple service ... ok
  test_bash_crash (__main__.CoredumpTest) ... skipped 'systemd-coredump does 
not work in 

[Touch-packages] [Bug 591823] Re: "File descriptor \d+ (\S+) leaked on lvs invocation."

[Mikko Rantalainen]

I got this same warning:

$ sudo apt autoremove
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages will be REMOVED
  linux-headers-5.4.0-66-lowlatency linux-headers-5.4.0-73-lowlatency 
linux-hwe-5.4-headers-5.4.0-66
  linux-hwe-5.4-headers-5.4.0-73 linux-image-5.4.0-66-lowlatency 
linux-image-5.4.0-73-lowlatency
  linux-modules-5.4.0-66-lowlatency linux-modules-5.4.0-73-lowlatency
0 to upgrade, 0 to newly install, 8 to remove and 0 not to upgrade.
After this operation, 714 MB disk space will be freed.
Do you want to continue? [Y/n] 
(Reading database ... 492639 files and directories currently installed.)
Removing linux-headers-5.4.0-66-lowlatency (5.4.0-66.74~18.04.2) ...
Removing linux-headers-5.4.0-73-lowlatency (5.4.0-73.82~18.04.1) ...
Removing linux-hwe-5.4-headers-5.4.0-66 (5.4.0-66.74~18.04.2) ...
Removing linux-hwe-5.4-headers-5.4.0-73 (5.4.0-73.82~18.04.1) ...
Removing linux-image-5.4.0-66-lowlatency (5.4.0-66.74~18.04.2) ...
/etc/kernel/postrm.d/initramfs-tools:
update-initramfs: Deleting /boot/initrd.img-5.4.0-66-lowlatency
/etc/kernel/postrm.d/zz-update-grub:
Sourcing file `/etc/default/grub'
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.4.0-77-lowlatency
Found initrd image: /boot/initrd.img-5.4.0-77-lowlatency
Found linux image: /boot/vmlinuz-5.4.0-74-lowlatency
Found initrd image: /boot/initrd.img-5.4.0-74-lowlatency
Found linux image: /boot/vmlinuz-5.4.0-73-lowlatency
Found initrd image: /boot/initrd.img-5.4.0-73-lowlatency
done
Removing linux-image-5.4.0-73-lowlatency (5.4.0-73.82~18.04.1) ...
/etc/kernel/postrm.d/initramfs-tools:
update-initramfs: Deleting /boot/initrd.img-5.4.0-73-lowlatency
/etc/kernel/postrm.d/zz-update-grub:
Sourcing file `/etc/default/grub'
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.4.0-77-lowlatency
Found initrd image: /boot/initrd.img-5.4.0-77-lowlatency
Found linux image: /boot/vmlinuz-5.4.0-74-lowlatency
Found initrd image: /boot/initrd.img-5.4.0-74-lowlatency
File descriptor 10 (/var/lib/dpkg/triggers/linux-update-5.4.0-66-lowlatency 
(deleted)) leaked on lvs invocation. Parent PID 12476: /bin/sh
done
Removing linux-modules-5.4.0-66-lowlatency (5.4.0-66.74~18.04.2) ...
Removing linux-modules-5.4.0-73-lowlatency (5.4.0-73.82~18.04.1) ...

$ lsb_release -a
LSB Version:
core-9.20170808ubuntu1-noarch:printing-9.20170808ubuntu1-noarch:security-9.20170808ubuntu1-noarch
Distributor ID: Ubuntu
Description:Ubuntu 18.04.5 LTS
Release:18.04
Codename:   bionic

I would guess this is actually a bug in grub-probe.

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

Title:
  "File descriptor \d+ (\S+) leaked on lvs invocation."

Status in aptitude:
  Fix Released
Status in lvm2:
  Fix Released
Status in lvm2 package in Ubuntu:
  Opinion

Bug description:
  If you see messages like these:

  File descriptor 40 (/var/lib/dpkg/status) leaked on lvs invocation. Parent 
PID 1854: /bin/sh
  File descriptor 41 (/var/lib/dpkg/status) leaked on lvs invocation. Parent 
PID 1854: /bin/sh
  File descriptor 42 (/var/lib/dpkg/status) leaked on lvs invocation. Parent 
PID 1854: /bin/sh
  File descriptor 43 (/var/lib/dpkg/status) leaked on lvs invocation. Parent 
PID 1854: /bin/sh

  You can set LVM_SUPPRESS_FD_WARNINGS to suppress these warnings.

  Reference:
  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=581339
  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=432986
  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=466138

  This is a slightly controversial bug and it's not yet fixed either way
  (aka fix not to leak file descriptors or stop warning by default)

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

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

[Touch-packages] [Bug 591823] Re: "File descriptor \d+ (\S+) leaked on lvs invocation."

[Mikko Rantalainen]

I would guess some files are left open when
grub_util_pull_lvm_by_command() calls grub_util_exec_pipe() in grub2
/grub-core/osdep/unix/getroot.c

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

Title:
  "File descriptor \d+ (\S+) leaked on lvs invocation."

Status in aptitude:
  Fix Released
Status in lvm2:
  Fix Released
Status in lvm2 package in Ubuntu:
  Opinion

Bug description:
  If you see messages like these:

  File descriptor 40 (/var/lib/dpkg/status) leaked on lvs invocation. Parent 
PID 1854: /bin/sh
  File descriptor 41 (/var/lib/dpkg/status) leaked on lvs invocation. Parent 
PID 1854: /bin/sh
  File descriptor 42 (/var/lib/dpkg/status) leaked on lvs invocation. Parent 
PID 1854: /bin/sh
  File descriptor 43 (/var/lib/dpkg/status) leaked on lvs invocation. Parent 
PID 1854: /bin/sh

  You can set LVM_SUPPRESS_FD_WARNINGS to suppress these warnings.

  Reference:
  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=581339
  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=432986
  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=466138

  This is a slightly controversial bug and it's not yet fixed either way
  (aka fix not to leak file descriptors or stop warning by default)

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

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

[Touch-packages] [Bug 1926265] Re: slapd enter in infinite loop on sched_yield syscall

[Sergio Durigan Junior]

Hi lincvz,

Unfortunately I don't plan to maintain the packages on the PPA; it would
be too cumbersome to keep monitoring security updates and rebuilding the
package every time.  My intention with the PPA was to facilitate the
diagnostic of the bug, and also to provide a hotfix for you.

I will try to talk to the SRU team again and see if we can reach some
sort of consensus on how to deal with this bug, but unfortunately I
cannot make promises here.  Sorry about that.

** Changed in: openldap (Ubuntu Bionic)
   Importance: High => Medium

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

Title:
  slapd enter in infinite loop on sched_yield syscall

Status in openldap package in Ubuntu:
  Confirmed
Status in openldap source package in Bionic:
  Triaged

Bug description:
  On a production server, sometimes slapd become unbresponsive, some threads 
loops in sched_yield syscall and consumme all CPU.
  To recover, slapd needs to restart.
  No related information is reported in log file.
  All same issues in OpenLDAP upstream project are old and fixed.
  So maybe this issue affects only Ubuntu package.
  It occurs randomly, so I have no steps to reproduce.

  
  OS : Bionic

  Openldap version:

  libldap-2.4-2:amd642.4.45+dfsg-1ubuntu1.10
 
  libldap-common 2.4.45+dfsg-1ubuntu1.10
 
  slapd  2.4.45+dfsg-1ubuntu1.10
 

  Modules loaded:

  olcModuleLoad: {0}back_bdb
  olcModuleLoad: {1}syncprov
  olcModuleLoad: {2}back_monitor
  olcModuleLoad: {3}memberof.la
  olcModuleLoad: {4}refint.la
  olcModuleLoad: {5}rwm
  olcModuleload: {6}back_ldap

  
  Backend is BDB. slapd run in (single) master - (multi) slave mode.

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

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

[Touch-packages] [Bug 1932980] Re: window title in mate terminal not change after I logout from ssh

[Sergio Durigan Junior]

Thank you for the bug report.

It seems to me that this is a MATE-specific configuration, and not
something related to openssh.  When you ssh into a host, ssh takes
control of the terminal and the PS1 variable becomes something else,
which is reflected on the window title.  When you log out of the ssh
connection, PS1 doesn't get overwritten again because the control is now
back to your shell.

Maybe there are ways to force the window title to be "refreshed" when
you disconnect, but I don't know offhand, sorry.

I'm setting the bug as Invalid for openssh.

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

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

Title:
  window title in mate terminal not change after I logout from ssh

Status in Ubuntu MATE:
  New
Status in mate-terminal package in Ubuntu:
  New
Status in openssh package in Ubuntu:
  Invalid

Bug description:
  I use Ubuntu Mate 20.04. I always update my system. When, I open mate
  terminal and login into my server via ssh, the window title is change
  to my server @. But, its not change after I
  logout. In this report I attach a proof. Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1932980/+subscriptions

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

[Touch-packages] [Bug 1916651] Re: asks about irc user home directory during upgrade

[Brian Murray]

** Changed in: base-passwd (Ubuntu Hirsute)
   Status: Confirmed => In Progress

** Changed in: base-passwd (Ubuntu Hirsute)
 Assignee: (unassigned) => Brian Murray (brian-murray)

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

Title:
  asks about irc user home directory during upgrade

Status in base-passwd package in Ubuntu:
  Confirmed
Status in base-passwd source package in Hirsute:
  In Progress

Bug description:
  Upgrading from groovy to hirsuite, base-passwd asks if the `irc`
  user's home directory should be moved from `/var/run/ircd` to
  `/run/ircd`.  Having no IRC server installed makes this very
  confusing, but appears harmless
  (https://askubuntu.com/questions/876975/user-irc-inside-of-default-
  ubuntu-16-04-server).  Possibly caused by https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=946884, but can this not prompt the user for a
  decision?

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: base-passwd 3.5.49
  ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu59
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Tue Feb 23 12:02:59 2021
  InstallationDate: Installed on 2019-08-17 (556 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
  RebootRequiredPkgs:
   libc6
   libc6
   libssl1.1
   libssl1.1
  SourcePackage: base-passwd
  UpgradeStatus: Upgraded to hirsute on 2021-02-23 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-passwd/+bug/1916651/+subscriptions

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

[Touch-packages] [Bug 1929657] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From mario.alberto.gali...@ibm.com 2021-06-23 18:19 EDT---
Files content:
root@ilabg13:~# cat /etc/systemd/network/10-enP53p0s0.link
[Match]
MACAddress=82:0c:9b:c9:78:f8

[Link]
Name=enP53p0s0
root@ilabg13:~# cat /usr/lib/systemd/network/99-default.link
#  SPDX-License-Identifier: LGPL-2.1+
#
#  This file is part of systemd.
#
#  systemd is free software; you can redistribute it and/or modify it
#  under the terms of the GNU Lesser General Public License as published by
#  the Free Software Foundation; either version 2.1 of the License, or
#  (at your option) any later version.

[Match]
OriginalName=*

[Link]
NamePolicy=keep kernel database onboard slot path
AlternativeNamesPolicy=database onboard slot path
MACAddressPolicy=persistent

Steeps followed to retrieve logs:
- Manually remove the IP
root@ilabg13:~# date
Wed Jun 23 15:08:41 MST 2021
root@ilabg13:~# ip addr del 192.168.171.53/24 dev enP53p0s0.171

- Try to assign ip via netplan
root@ilabg13:~# date
Wed Jun 23 15:10:14 MST 2021
root@ilabg13:~# netplan apply

- Checking networkctl 10sec and 30sec after
root@ilabg13:~# date
Wed Jun 23 15:11:19 MST 2021
root@ilabg13:~# networkctl status enP53p0s0.171 --no-pager
? 9: enP53p0s0.171
Link File: n/a
Network File: n/a
Type: vlan
State: degraded (pending)
HW Address: 82:0c:9b:c9:78:f8
MTU: 9000 (max: 65535)
Queue Length (Tx/Rx): 1/1
Auto negotiation: yes
Speed: 25Gbps
Duplex: full
Address: fe80::800c:9bff:fec9:78f8
Activation Policy: up

Jun 23 15:10:25 ilabg13.tuc.stglabs.ibm.com systemd-networkd[9805]: 
enP53p0s0.171: Flags change: +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST
Jun 23 15:10:25 ilabg13.tuc.stglabs.ibm.com systemd-networkd[9805]: 
enP53p0s0.171: Link 9 added
Jun 23 15:10:25 ilabg13.tuc.stglabs.ibm.com systemd-networkd[9805]: 
enP53p0s0.171: link pending udev initialization...
Jun 23 15:10:25 ilabg13.tuc.stglabs.ibm.com systemd-networkd[9805]: 
enP53p0s0.171: netdev has index 9
Jun 23 15:10:25 ilabg13.tuc.stglabs.ibm.com systemd-networkd[9805]: 
enP53p0s0.171: Saved original MTU: 9000
Jun 23 15:10:25 ilabg13.tuc.stglabs.ibm.com systemd-networkd[9805]: 
enP53p0s0.171: Remembering foreign address: fe80::800c:9bff:fec9:78f8/64 (valid 
forever)
Jun 23 15:10:25 ilabg13.tuc.stglabs.ibm.com systemd-networkd[9805]: 
enP53p0s0.171: Gained IPv6LL
Jun 23 15:10:25 ilabg13.tuc.stglabs.ibm.com systemd-networkd[9805]: 
enP53p0s0.171: Remembering route: dst: ff00::/8, src: n/a, gw: n/a, prefsrc: 
n/a, scope: global, table: loc?e: multicast
Jun 23 15:10:25 ilabg13.tuc.stglabs.ibm.com systemd-networkd[9805]: 
enP53p0s0.171: Remembering route: dst: fe80::800c:9bff:fec9:78f8/128, src: n/a, 
gw: n/a, prefsrc: n/a, scop? type: local
Jun 23 15:10:25 ilabg13.tuc.stglabs.ibm.com systemd-networkd[9805]: 
enP53p0s0.171: Remembering route: dst: fe80::/64, src: n/a, gw: n/a, prefsrc: 
n/a, scope: global, table: ma?ype: unicast
root@ilabg13:~#
root@ilabg13:~#
root@ilabg13:~# date
Wed Jun 23 15:11:44 MST 2021
root@ilabg13:~# networkctl status enP53p0s0.171 --no-pager
? 9: enP53p0s0.171
Link File: n/a
Network File: n/a
Type: vlan
State: degraded (pending)
HW Address: 82:0c:9b:c9:78:f8
MTU: 9000 (max: 65535)
Queue Length (Tx/Rx): 1/1
Auto negotiation: yes
Speed: 25Gbps
Duplex: full
Address: fe80::800c:9bff:fec9:78f8
Activation Policy: up

Jun 23 15:10:25 ilabg13.tuc.stglabs.ibm.com systemd-networkd[9805]: 
enP53p0s0.171: Flags change: +UP +LOWER_UP +RUNNING +MULTICAST +BROADCAST
Jun 23 15:10:25 ilabg13.tuc.stglabs.ibm.com systemd-networkd[9805]: 
enP53p0s0.171: Link 9 added
Jun 23 15:10:25 ilabg13.tuc.stglabs.ibm.com systemd-networkd[9805]: 
enP53p0s0.171: link pending udev initialization...
Jun 23 15:10:25 ilabg13.tuc.stglabs.ibm.com systemd-networkd[9805]: 
enP53p0s0.171: netdev has index 9
Jun 23 15:10:25 ilabg13.tuc.stglabs.ibm.com systemd-networkd[9805]: 
enP53p0s0.171: Saved original MTU: 9000
Jun 23 15:10:25 ilabg13.tuc.stglabs.ibm.com systemd-networkd[9805]: 
enP53p0s0.171: Remembering foreign address: fe80::800c:9bff:fec9:78f8/64 (valid 
forever)
Jun 23 15:10:25 ilabg13.tuc.stglabs.ibm.com systemd-networkd[9805]: 
enP53p0s0.171: Gained IPv6LL
Jun 23 15:10:25 ilabg13.tuc.stglabs.ibm.com systemd-networkd[9805]: 
enP53p0s0.171: Remembering route: dst: ff00::/8, src: n/a, gw: n/a, prefsrc: 
n/a, scope: global, table: loc?e: multicast
Jun 23 15:10:25 ilabg13.tuc.stglabs.ibm.com systemd-networkd[9805]: 
enP53p0s0.171: Remembering route: dst: fe80::800c:9bff:fec9:78f8/128, src: n/a, 
gw: n/a, prefsrc: n/a, scop? type: local
Jun 23 15:10:25 ilabg13.tuc.stglabs.ibm.com systemd-networkd[9805]: 
enP53p0s0.171: Remembering route: dst: fe80::/64, src: n/a, gw: n/a, prefsrc: 
n/a, scope: global, table: ma?ype: unicast
root@ilabg13:~#

- Trying workaround 15445:
root@ilabg13:~# date
Wed Jun 23 15:12:49 MST 2021
root@ilabg13:~# netplan apply
root@ilabg13:~# date
Wed Jun 23 15:13:08 MST 2021
root@ilabg13:~# networkctl reload
root@ilabg13:~# date
Wed Jun 23 15:13:34 MST 2021
root@ilabg13:~# networkctl renew 

[Touch-packages] [Bug 1929657] journalctl delay

[bugproxy]

--- Comment (attachment only) From mario.alberto.gali...@ibm.com 2021-06-23 
18:25 EDT---


** Attachment added: "journalctl delay"
   
https://bugs.launchpad.net/bugs/1929657/+attachment/5506551/+files/journalctl_udev_monitor_delay.txt.zip

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

Title:
  [Ubuntu 20.4.2]  vLan not getting static IP assigned (on s390x)

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in linux package in Ubuntu:
  New
Status in netplan.io package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  Doing vLAN configuration one of the vLANs is not getting static IP assigned 
when the rest are workin without problems
   
  Contact Information = Mario Alvarado/mario.alberto.gali...@ibm.com 
   
  ---uname output---
  Linux ilabg13.tuc.stglabs.ibm.com 5.4.0-73-generic #82-Ubuntu SMP Wed Apr 14 
17:29:32 UTC 2021 s390x s390x s390x GNU/Linux
   
  Machine Type = z15 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1)Configure the netplan file as follow:
  root@ilabg13:~# cat /etc/netplan/01-iscsi-config.yaml

  # This is the network config written by 'subiquity'

  network:

ethernets:

  encdb0:

addresses:

- 11.111.114.213/22

macaddress: 02:76:54:00:00:03

  encdc0:

addresses:

- 11.111.112.213/22

macaddress: 02:76:54:00:00:04

  enP50s3832 :

addresses:

- 11.111.112.214/22

  enP53p0s0:

addresses:

- 11.111.112.215/22

vlans:

  encdb0.160:

id: 160

link: encdb0

mtu: 9000

addresses:

- 192.168.160.53/24

  encdc0.150:

id: 150

link: encdc0

mtu: 9000

addresses:

- 192.168.150.53/24

  enP50s3832.170:

id: 170

link: enP50s3832

mtu: 9000

addresses:

- 192.168.170.53/24

  enP53p0s0.171:

id: 171

link: enP53p0s0

mtu: 9000

addresses:

- 192.168.171.53/24

version: 2

  2)run net plan apply:
  root@ilabg13:~# netplan --debug apply

  ** (generate:59965): DEBUG: 14:55:15.046: Processing input file
  /etc/netplan/00-installer-config.yaml..

  ** (generate:59965): DEBUG: 14:55:15.046: starting new processing pass

  ** (generate:59965): DEBUG: 14:55:15.046: Processing input file
  /etc/netplan/01-iscsi-config.yaml..

  ** (generate:59965): DEBUG: 14:55:15.046: starting new processing pass

  ** (generate:59965): DEBUG: 14:55:15.046: We have some netdefs, pass
  them through a final round of validation

  ** (generate:59965): DEBUG: 14:55:15.046: encdc0: setting default
  backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: encdb0: setting default
  backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: ence0f: setting default
  backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: encdb0.160: setting default
  backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: enP50s3832: setting default
  backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: enP53p0s0.171: setting
  default backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: enP50s3832.170: setting
  default backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: enP53p0s0: setting default
  backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: encdc0.150: setting default
  backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.047: Generating output files..

  ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition
  ence0f is not for us (backend 1)

  ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition
  ence0f is not for us (backend 1)

  ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition
  encdb0 is not for us (backend 1)

  ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition
  encdb0 is not for us (backend 1)

  ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition
  encdc0 is not for us (backend 1)

  ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition
  encdc0 is not for us (backend 1)

  ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition
  enP50s3832 is not for us 

[Touch-packages] [Bug 1916651] Re: asks about irc user home directory during upgrade

[Brian Murray]

** Description changed:

- Upgrading from groovy to hirsuite, base-passwd asks if the `irc` user's
- home directory should be moved from `/var/run/ircd` to `/run/ircd`.
- Having no IRC server installed makes this very confusing, but appears
- harmless (https://askubuntu.com/questions/876975/user-irc-inside-of-
- default-ubuntu-16-04-server).  Possibly caused by
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946884, but can this
- not prompt the user for a decision?
+ [Test Case]
+ 1) On an Ubuntu 20.10 system edit your /etc/apt/sources.list file to have 
hirsute instead of groovy
+ 2) Run apt-get update
+ 3) Execute 'sudo apt-get install base-passwd'
  
- ProblemType: Bug
- DistroRelease: Ubuntu 21.04
+ With the version of base-passwd you'll receive a prompt about moving the
+ 'irc' user's home directory from '/var/run/ircd' to '/run/ircd'.
+ 
+ 
+ [Original Description]
+ Upgrading from groovy to hirsuite, base-passwd asks if the `irc` user's home 
directory should be moved from `/var/run/ircd` to `/run/ircd`.  Having no IRC 
server installed makes this very confusing, but appears harmless 
(https://askubuntu.com/questions/876975/user-irc-inside-of-default-ubuntu-16-04-server).
  Possibly caused by https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946884, 
but can this not prompt the user for a decision?
+ 
+ ProblemType: BugDistroRelease: Ubuntu 21.04
  Package: base-passwd 3.5.49
  ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu59
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Tue Feb 23 12:02:59 2021
  InstallationDate: Installed on 2019-08-17 (556 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
  RebootRequiredPkgs:
-  libc6
-  libc6
-  libssl1.1
-  libssl1.1
- SourcePackage: base-passwd
+  libc6
+  libc6
+  libssl1.1
+  libssl1.1SourcePackage: base-passwd
  UpgradeStatus: Upgraded to hirsute on 2021-02-23 (0 days ago)

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

Title:
  asks about irc user home directory during upgrade

Status in base-passwd package in Ubuntu:
  Confirmed
Status in base-passwd source package in Hirsute:
  In Progress

Bug description:
  [Test Case]
  1) On an Ubuntu 20.10 system edit your /etc/apt/sources.list file to have 
hirsute instead of groovy
  2) Run apt-get update
  3) Execute 'sudo apt-get install base-passwd'

  With the version of base-passwd you'll receive a prompt about moving
  the 'irc' user's home directory from '/var/run/ircd' to '/run/ircd'.

  
  [Original Description]
  Upgrading from groovy to hirsuite, base-passwd asks if the `irc` user's home 
directory should be moved from `/var/run/ircd` to `/run/ircd`.  Having no IRC 
server installed makes this very confusing, but appears harmless 
(https://askubuntu.com/questions/876975/user-irc-inside-of-default-ubuntu-16-04-server).
  Possibly caused by https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946884, 
but can this not prompt the user for a decision?

  ProblemType: BugDistroRelease: Ubuntu 21.04
  Package: base-passwd 3.5.49
  ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu59
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: GNOME
  Date: Tue Feb 23 12:02:59 2021
  InstallationDate: Installed on 2019-08-17 (556 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
  RebootRequiredPkgs:
   libc6
   libc6
   libssl1.1
   libssl1.1SourcePackage: base-passwd
  UpgradeStatus: Upgraded to hirsute on 2021-02-23 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-passwd/+bug/1916651/+subscriptions

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

[Touch-packages] [Bug 1929657] udevadm monitor delay

[bugproxy]

--- Comment (attachment only) From mario.alberto.gali...@ibm.com 2021-06-23 
18:26 EDT---


** Attachment added: "udevadm monitor delay"
   
https://bugs.launchpad.net/bugs/1929657/+attachment/5506552/+files/udevadm_monitor_delay.txt

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

Title:
  [Ubuntu 20.4.2]  vLan not getting static IP assigned (on s390x)

Status in Ubuntu on IBM z Systems:
  Incomplete
Status in linux package in Ubuntu:
  New
Status in netplan.io package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  ---Problem Description---
  Doing vLAN configuration one of the vLANs is not getting static IP assigned 
when the rest are workin without problems
   
  Contact Information = Mario Alvarado/mario.alberto.gali...@ibm.com 
   
  ---uname output---
  Linux ilabg13.tuc.stglabs.ibm.com 5.4.0-73-generic #82-Ubuntu SMP Wed Apr 14 
17:29:32 UTC 2021 s390x s390x s390x GNU/Linux
   
  Machine Type = z15 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1)Configure the netplan file as follow:
  root@ilabg13:~# cat /etc/netplan/01-iscsi-config.yaml

  # This is the network config written by 'subiquity'

  network:

ethernets:

  encdb0:

addresses:

- 11.111.114.213/22

macaddress: 02:76:54:00:00:03

  encdc0:

addresses:

- 11.111.112.213/22

macaddress: 02:76:54:00:00:04

  enP50s3832 :

addresses:

- 11.111.112.214/22

  enP53p0s0:

addresses:

- 11.111.112.215/22

vlans:

  encdb0.160:

id: 160

link: encdb0

mtu: 9000

addresses:

- 192.168.160.53/24

  encdc0.150:

id: 150

link: encdc0

mtu: 9000

addresses:

- 192.168.150.53/24

  enP50s3832.170:

id: 170

link: enP50s3832

mtu: 9000

addresses:

- 192.168.170.53/24

  enP53p0s0.171:

id: 171

link: enP53p0s0

mtu: 9000

addresses:

- 192.168.171.53/24

version: 2

  2)run net plan apply:
  root@ilabg13:~# netplan --debug apply

  ** (generate:59965): DEBUG: 14:55:15.046: Processing input file
  /etc/netplan/00-installer-config.yaml..

  ** (generate:59965): DEBUG: 14:55:15.046: starting new processing pass

  ** (generate:59965): DEBUG: 14:55:15.046: Processing input file
  /etc/netplan/01-iscsi-config.yaml..

  ** (generate:59965): DEBUG: 14:55:15.046: starting new processing pass

  ** (generate:59965): DEBUG: 14:55:15.046: We have some netdefs, pass
  them through a final round of validation

  ** (generate:59965): DEBUG: 14:55:15.046: encdc0: setting default
  backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: encdb0: setting default
  backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: ence0f: setting default
  backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: encdb0.160: setting default
  backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: enP50s3832: setting default
  backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: enP53p0s0.171: setting
  default backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: enP50s3832.170: setting
  default backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: enP53p0s0: setting default
  backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.046: encdc0.150: setting default
  backend to 1

  ** (generate:59965): DEBUG: 14:55:15.046: Configuration is valid

  ** (generate:59965): DEBUG: 14:55:15.047: Generating output files..

  ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition
  ence0f is not for us (backend 1)

  ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition
  ence0f is not for us (backend 1)

  ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition
  encdb0 is not for us (backend 1)

  ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition
  encdb0 is not for us (backend 1)

  ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition
  encdc0 is not for us (backend 1)

  ** (generate:59965): DEBUG: 14:55:15.047: NetworkManager: definition
  encdc0 is not for us (backend 1)

  ** (generate:59965): DEBUG: 14:55:15.047: openvswitch: definition
  enP50s3832 is not for us (backend 1)

[Touch-packages] [Bug 1100326]

[Erikjensen-l]

Doesn't look like I have permission to re-open, but I'd love to see this
or some alternatively to allow integrating with any system geolocation
methods I have set up, such as a Bluetooth GPS.

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

Title:
  Location requested by websites should be able to use GPS/mobile
  positioning

Status in Chromium Browser:
  Fix Committed
Status in Mozilla Firefox:
  Unknown
Status in GeoClue:
  Won't Fix
Status in WebKit:
  Fix Released
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in firefox package in Ubuntu:
  Confirmed
Status in geoclue-2.0 package in Ubuntu:
  Fix Released
Status in geoclue-providers package in Ubuntu:
  Invalid

Bug description:
  It would be nice if location requested by websites could use location
  found from GPS or GSM/CDMA positioning.

To manage notifications about this bug go to:
https://bugs.launchpad.net/chromium-browser/+bug/1100326/+subscriptions

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

[Touch-packages] [Bug 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off

[Daniel van Vugt]

Robie, "Fix Committed" means the fix is committed here:

  https://git.launchpad.net/~bluetooth/bluez/commit/?id=04298c5e46

It's part of the 5.59 release for Impish that is awaiting sponsorship
(bug 1933078).

Declaring "Fix Committed" when a fix exists in an upstream tributary
before anything has reached proposed is a procedure requested by seb128
and we now follow on the desktop team.


** Also affects: bluez via
   https://github.com/bluez/bluez/issues/162
   Importance: Unknown
   Status: Unknown

** Tags added: fixed-in-bluez-5.60 fixed-upstream

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

Title:
  [hirsute/impish] Can't turn bluetooth on again after turning it off

Status in Bluez Utilities:
  Unknown
Status in GNOME Bluetooth:
  Unknown
Status in OEM Priority Project:
  New
Status in bluez package in Ubuntu:
  Fix Committed
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in bluez source package in Focal:
  In Progress
Status in bluez source package in Hirsute:
  In Progress
Status in bluez source package in Impish:
  Fix Committed
Status in gnome-settings-daemon source package in Impish:
  Fix Released

Bug description:
  [Impact]

  On/off of Bluetooth in gnome-control-center will not work properly in kernels 
5.11 (approximately) onward. Devices are not refreshed in the list anymore.
   
  [Test Plan]

  1. Open gnome-control-center and select Bluetooth
  2. Turn off Bluetooth via UI
  3. Turn on Bluetooth via UI

  Expect: Device list appears, so Bluetooth really is on.

  [Where problems could occur]

  Since the fix involves the 'rfkill' logic it has the potential to
  affect any Bluetooth or Wifi on/off setting.

  [Other info]

  Upstream bug in gnome-bluetooth:
  https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38

  Discussion in linux-bluetooth:
  https://marc.info/?t=16200475893=1=2

  [Original bug report]

  When ever i Turn on my system or restart bluetooth is open any it
  connects to any device. But when i turn off bluetooth and try to turn
  it on again. it neither turns on nor scans/connects to any device.
  This is happening since I updated my system to ubuntu 21.04 LTS

    Bluetooth: hci0: HCI reset during shutdown failed

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 25 15:09:23 2021
  InstallationDate: Installed on 2020-12-15 (130 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 80TR
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago)
  dmi.bios.date: 07/31/2017
  dmi.bios.release: 1.29
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 3UCN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Nano 5B1
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 110-15AST
  dmi.ec.firmware.release: 1.29
  dmi.modalias: 
dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80TR
  dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST
  dmi.product.version: Lenovo ideapad 110-15AST
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: C8:3D:D4:84:E0:06  ACL MTU: 820:8  SCO MTU: 255:16
    DOWN
    RX bytes:744804 acl:76 sco:0 events:105989 errors:0
    TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0

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

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

[Touch-packages] [Bug 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off

[Andy Chi]

Bluez bug (https://github.com/bluez/bluez/issues/162) closed and fix merged in 
bluez.
https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?id=c939747f543a76ffd556312f753cf9d36c047c94

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

Title:
  [hirsute/impish] Can't turn bluetooth on again after turning it off

Status in Bluez Utilities:
  Unknown
Status in GNOME Bluetooth:
  Unknown
Status in OEM Priority Project:
  New
Status in bluez package in Ubuntu:
  Fix Committed
Status in gnome-settings-daemon package in Ubuntu:
  Fix Released
Status in bluez source package in Focal:
  In Progress
Status in bluez source package in Hirsute:
  In Progress
Status in bluez source package in Impish:
  Fix Committed
Status in gnome-settings-daemon source package in Impish:
  Fix Released

Bug description:
  [Impact]

  On/off of Bluetooth in gnome-control-center will not work properly in kernels 
5.11 (approximately) onward. Devices are not refreshed in the list anymore.
   
  [Test Plan]

  1. Open gnome-control-center and select Bluetooth
  2. Turn off Bluetooth via UI
  3. Turn on Bluetooth via UI

  Expect: Device list appears, so Bluetooth really is on.

  [Where problems could occur]

  Since the fix involves the 'rfkill' logic it has the potential to
  affect any Bluetooth or Wifi on/off setting.

  [Other info]

  Upstream bug in gnome-bluetooth:
  https://gitlab.gnome.org/GNOME/gnome-bluetooth/-/issues/38

  Discussion in linux-bluetooth:
  https://marc.info/?t=16200475893=1=2

  [Original bug report]

  When ever i Turn on my system or restart bluetooth is open any it
  connects to any device. But when i turn off bluetooth and try to turn
  it on again. it neither turns on nor scans/connects to any device.
  This is happening since I updated my system to ubuntu 21.04 LTS

    Bluetooth: hci0: HCI reset during shutdown failed

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: bluetooth (not installed)
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  Uname: Linux 5.11.0-16-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 25 15:09:23 2021
  InstallationDate: Installed on 2020-12-15 (130 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 80TR
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago)
  dmi.bios.date: 07/31/2017
  dmi.bios.release: 1.29
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 3UCN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Nano 5B1
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 110-15AST
  dmi.ec.firmware.release: 1.29
  dmi.modalias: 
dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80TR
  dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST
  dmi.product.version: Lenovo ideapad 110-15AST
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: C8:3D:D4:84:E0:06  ACL MTU: 820:8  SCO MTU: 255:16
    DOWN
    RX bytes:744804 acl:76 sco:0 events:105989 errors:0
    TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0

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

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