[Touch-packages] [Bug 1934888] Re: Resuming from sleep garbles display configuration

[Daniel van Vugt]

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Also affects: nvidia-graphics-drivers-460 (Ubuntu)
   Importance: Undecided
   Status: New

** Summary changed:

- Resuming from sleep garbles display configuration
+ On resuming from sleep the external monitor is activated alone, and the 
laptop screen stays completely black

** Tags added: black-screen suspend-resume

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

** Package changed: mutter (Ubuntu) => kwin (Ubuntu)

** No longer affects: nvidia-graphics-drivers-460 (Ubuntu)

** Summary changed:

- On resuming from sleep the external monitor is activated alone, and the 
laptop screen stays completely black
+ [KDE] On resuming from sleep the external monitor is activated alone, and the 
laptop screen stays completely black

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

Title:
  [KDE] On resuming from sleep the external monitor is activated alone,
  and the laptop screen stays completely black

Status in kwin package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  Hello,

  I'm using a thinkpad as a workstation, with a dual-display configuration: the 
laptop screen and a big external screen.
  The screen is directly connected to the laptop hdmi port, because using it 
through the thunderbolt port is hit-and-miss, but this is another story.

  When I wake my system on after a night sleep, more often than not -
  it's not systematic -, my primary screen - the bigger external Dell
  monitor - is activated alone, and the laptop screen stays completely
  black.

  I have to go to system settings -> Display to activate it again.

  thanks for your support

  /Bruno Hivert

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.10.0-1033.34-oem 5.10.41
  Uname: Linux 5.10.0-1033-oem x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  460.80  Fri May  7 06:55:54 
UTC 2021
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Wed Jul  7 07:48:20 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   acpi-call, 1.1.0, 5.10.0-1034-oem, x86_64: installed
   nvidia, 460.80, 5.10.0-1033-oem, x86_64: installed
   nvidia, 460.80, 5.10.0-1034-oem, x86_64: installed
   nvidia, 460.80, 5.8.0-59-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo Device [17aa:22c0]
   NVIDIA Corporation Device [10de:1f95] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:22c0]
  InstallationDate: Installed on 2021-05-21 (46 days ago)
  InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: LENOVO 20TK001JUS
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.10.0-1033-oem 
root=/dev/mapper/vgkubuntu-root ro
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/15/2021
  dmi.bios.release: 1.15
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2VET30W (1.15 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20TK001JUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T08861 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.8
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2VET30W(1.15):bd04/15/2021:br1.15:efr1.8:svnLENOVO:pn20TK001JUS:pvrThinkPadX1ExtremeGen3:rvnLENOVO:rn20TK001JUS:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Extreme Gen 3
  dmi.product.name: 20TK001JUS
  dmi.product.sku: LENOVO_MT_20TK_BU_Think_FM_ThinkPad X1 Extreme Gen 3
  dmi.product.version: ThinkPad X1 Extreme Gen 3
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~2

[Touch-packages] [Bug 1918458] Re: [Swift SF515-51T, Realtek ALC256, Grey Speaker, Internal] Playback problem, no sound from speakers, headphones ok

[Hui Wang]

OK, let me ask for help from realtek.

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

Title:
  [Swift SF515-51T, Realtek ALC256, Grey Speaker, Internal] Playback
  problem, no sound from speakers, headphones ok

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Expect : sound from speaker
  Instead, obtain : no sound.

  
  Tried various configuration of /etc/modprobe.d/alsa-conf with :

  options snd-hda-intel model= and
  options snd-intel-dspcfg dsp_driver=3 or 1
  and systematic reboot.

  Either I get dummy output, or I get proper output detection, alsamixer
  and pavucontrol seems 100% ok, but no sound comes from the speakers.

  I'm under a dualboot with Windows 10, BIOS fast boot disabled.
  Ubuntu 20.04.2 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  thibauts   1522 F pulseaudio
   /dev/snd/pcmC0D0p:   thibauts   1522 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 10 18:10:30 2021
  InstallationDate: Installed on 2021-03-09 (1 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed
  Symptom_Card: Cannon Point-LP High Definition Audio Controller - sof-hda-dsp
  Symptom_Jack: Grey Speaker, Internal
  Symptom_Type: Only some of outputs are working
  Title: [Swift SF515-51T, Realtek ALC256, Grey Speaker, Internal] Playback 
problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/24/2019
  dmi.bios.release: 1.4
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.04
  dmi.board.asset.tag: Default string
  dmi.board.name: Guinness_WL
  dmi.board.vendor: WL
  dmi.board.version: V1.04
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.04
  dmi.ec.firmware.release: 1.6
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.04:bd05/24/2019:br1.4:efr1.6:svnAcer:pnSwiftSF515-51T:pvrV1.04:rvnWL:rnGuinness_WL:rvrV1.04:cvnAcer:ct10:cvrV1.04:
  dmi.product.family: Swift 5
  dmi.product.name: Swift SF515-51T
  dmi.product.sku: 
  dmi.product.version: V1.04
  dmi.sys.vendor: Acer
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2021-03-10T18:04:19.277254

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1918458/+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 1927078] Re: Don't allow useradd to use fully numeric names

[Seth Arnold]

Beautiful, thanks for the large range of tests :)

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

Title:
  Don't allow useradd to use fully numeric names

Status in shadow package in Ubuntu:
  New
Status in shadow source package in Focal:
  New
Status in shadow source package in Groovy:
  New
Status in shadow source package in Hirsute:
  New
Status in shadow source package in Impish:
  New

Bug description:
  [Description]

  Fully numeric names support in Ubuntu is inconsistent in Focal onwards
  because systemd does not like them[1] but are still allowed by default
  by useradd, leaving the session behavior in hands of the running
  applications. Two examples:

  1. After creating a user named "0", the user can log in via ssh or
  console but loginctl won't create a session for it:

  root@focal:/home/ubuntu# useradd -m 0
  root@focal:/home/ubuntu# id 0
  uid=1005(0) gid=1005(0) groups=1005(0)

  ..

  0@192.168.122.6's password:
  Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.8.0-48-generic x86_64)

  Last login: Thu Apr  8 16:17:06 2021 from 192.168.122.1
  $ loginctl
  No sessions.
  $ w
   16:20:09 up 4 min,  1 user,  load average: 0.03, 0.14, 0.08
  USER TTY  FROM LOGIN@   IDLE   JCPU   PCPU WHAT
  0pts/0192.168.122.116:170.00s  0.00s  0.00s w  

  And pam-systemd shows the following message:

  Apr 08 16:17:06 focal sshd[1584]: pam_unix(sshd:session): session opened for 
user 0 by (uid=0)
  Apr 08 16:17:06 focal sshd[1584]: pam_systemd(sshd:session): pam-systemd 
initializing
  Apr 08 16:17:06 focal sshd[1584]: pam_systemd(sshd:session): Failed to get 
user record: Invalid argument

  
  2. With that same username, every successful authentication in gdm will loop 
back to gdm again instead of starting gnome, making the user unable to login.

  
  Making useradd fail (unless --badnames is set) when a fully numeric name is 
used will make the default OS behavior consistent.

  
  [Other info]

  - Upstream does not support fully numeric usernames
  - useradd has a --badnames parameter that would still allow the use of these 
type of names

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1927078/+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 1918458] Re: [Swift SF515-51T, Realtek ALC256, Grey Speaker, Internal] Playback problem, no sound from speakers, headphones ok

[Hui Wang]

Please try this:

$sudo ./set-verb.sh
check if spk works or not.

thx.


** Attachment added: "set-verb.sh"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1918458/+attachment/5509705/+files/set-verb.sh

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

Title:
  [Swift SF515-51T, Realtek ALC256, Grey Speaker, Internal] Playback
  problem, no sound from speakers, headphones ok

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Expect : sound from speaker
  Instead, obtain : no sound.

  
  Tried various configuration of /etc/modprobe.d/alsa-conf with :

  options snd-hda-intel model= and
  options snd-intel-dspcfg dsp_driver=3 or 1
  and systematic reboot.

  Either I get dummy output, or I get proper output detection, alsamixer
  and pavucontrol seems 100% ok, but no sound comes from the speakers.

  I'm under a dualboot with Windows 10, BIOS fast boot disabled.
  Ubuntu 20.04.2 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  thibauts   1522 F pulseaudio
   /dev/snd/pcmC0D0p:   thibauts   1522 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 10 18:10:30 2021
  InstallationDate: Installed on 2021-03-09 (1 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed
  Symptom_Card: Cannon Point-LP High Definition Audio Controller - sof-hda-dsp
  Symptom_Jack: Grey Speaker, Internal
  Symptom_Type: Only some of outputs are working
  Title: [Swift SF515-51T, Realtek ALC256, Grey Speaker, Internal] Playback 
problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/24/2019
  dmi.bios.release: 1.4
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.04
  dmi.board.asset.tag: Default string
  dmi.board.name: Guinness_WL
  dmi.board.vendor: WL
  dmi.board.version: V1.04
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.04
  dmi.ec.firmware.release: 1.6
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.04:bd05/24/2019:br1.4:efr1.6:svnAcer:pnSwiftSF515-51T:pvrV1.04:rvnWL:rnGuinness_WL:rvrV1.04:cvnAcer:ct10:cvrV1.04:
  dmi.product.family: Swift 5
  dmi.product.name: Swift SF515-51T
  dmi.product.sku: 
  dmi.product.version: V1.04
  dmi.sys.vendor: Acer
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2021-03-10T18:04:19.277254

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1918458/+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 1934439] Re: Add Ubuntu Pro banner to Livepatch page

[Robert Ancell]

** Description changed:

- Add a banner to the Livepatch page to invite users to join the Ubuntu
- Pro for Desktop.
+ [Impact]
+ Add a banner to the Livepatch page to invite users to join the Ubuntu Pro for 
Desktop. Note that this is not shown in current releases, as this feature only 
applies to older versions.
+ 
+ [Test Case]
+ 1. Open Software Properties.
+ 2. Go to Livepatch tab.
+ Expected result:
+ A banner is shown directing the user to Ubuntu Pro.
+ The banner can be dismissed, and doesn't return when restarting 
software-properties.
+ 
+ [Regression Potential]
+ Some risk of introducing a new bug, however the change is quite small and 
doesn't have any complex interactions.

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

Title:
  Add Ubuntu Pro banner to Livepatch page

Status in software-properties package in Ubuntu:
  New
Status in software-properties source package in Xenial:
  New
Status in software-properties source package in Bionic:
  New
Status in software-properties source package in Focal:
  New

Bug description:
  [Impact]
  Add a banner to the Livepatch page to invite users to join the Ubuntu Pro for 
Desktop. Note that this is not shown in current releases, as this feature only 
applies to older versions.

  [Test Case]
  1. Open Software Properties.
  2. Go to Livepatch tab.
  Expected result:
  A banner is shown directing the user to Ubuntu Pro.
  The banner can be dismissed, and doesn't return when restarting 
software-properties.

  [Regression Potential]
  Some risk of introducing a new bug, however the change is quite small and 
doesn't have any complex interactions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1934439/+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 1934439] Re: Add Ubuntu Pro banner to Livepatch page

[Robert Ancell]

Lech - the Xenial version doesn't have a Livepatch page, should it be
placed somewhere else?

** Changed in: software-properties (Ubuntu Bionic)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

** Changed in: software-properties (Ubuntu Focal)
 Assignee: (unassigned) => Robert Ancell (robert-ancell)

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

Title:
  Add Ubuntu Pro banner to Livepatch page

Status in software-properties package in Ubuntu:
  New
Status in software-properties source package in Xenial:
  New
Status in software-properties source package in Bionic:
  New
Status in software-properties source package in Focal:
  New

Bug description:
  [Impact]
  Add a banner to the Livepatch page to invite users to join the Ubuntu Pro for 
Desktop. Note that this is not shown in current releases, as this feature only 
applies to older versions.

  [Test Case]
  1. Open Software Properties.
  2. Go to Livepatch tab.
  Expected result:
  A banner is shown directing the user to Ubuntu Pro.
  The banner can be dismissed, and doesn't return when restarting 
software-properties.

  [Regression Potential]
  Some risk of introducing a new bug, however the change is quite small and 
doesn't have any complex interactions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1934439/+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 1934439] Re: Add Ubuntu Pro banner to Livepatch page

[Robert Ancell]

** No longer affects: software-properties (Ubuntu Hirsute)

** No longer affects: software-properties (Ubuntu Impish)

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

Title:
  Add Ubuntu Pro banner to Livepatch page

Status in software-properties package in Ubuntu:
  New
Status in software-properties source package in Xenial:
  New
Status in software-properties source package in Bionic:
  New
Status in software-properties source package in Focal:
  New

Bug description:
  Add a banner to the Livepatch page to invite users to join the Ubuntu
  Pro for Desktop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1934439/+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 1871268] Re: Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected

[Ministerio Profetico Sal e Luz]

erro no final da instalação via pen drive.

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

Title:
  Installation fails due to useless immediate configuration error when
  "Install Third-Party Drivers" is selected

Status in Ubuntu CD Images:
  Fix Released
Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Bionic:
  Fix Released
Status in apt source package in Focal:
  Fix Released
Status in apt source package in Groovy:
  Fix Released
Status in apt package in Debian:
  Fix Released

Bug description:
  [Impact]
  Installations that really succeeded would then fail because APT could not 
immediately configure a package. Which is a pointless way to fail at that 
point, because everything did work out anyway.

  We have two changes that help address this:

  * The first one stops immediately configuring multi-arch siblings
  (e.g. libc6:i386 when it's configuring libc6:amd64). This was not
  necessary, and caused all the libc6:i386 failures here.

  * The second change sort of also supersedes the first one: It just
  ignores any errors from immediate configuration, relying on the fact
  that it's checked and rectified at a later point if there are
  unconfigured packages (which is what made all those failures happen
  spuriously after having successfully installed everything).

  [Test case]
  We have one test case in EIPP format in the Debian bug 973305 which was only 
helped by the second change, not the first one. Run /usr/lib/apt/planners < 
eipp.log and check there are no errors.

  TODO: It's unclear if the APT from proposed installed in the live
  session will fix the installer, needs investigation, but would make a
  useful test case.

  [Regression potential]
  It's imaginable that we missed something somewhere and some path that checked 
for a set error doesn't check it anymore, and we report success when we hit an 
error, but it seems unlikely.

  Behavior of --simulate changes. This used to fail before as well, and
  will now only produce a warning. We don't believe that is a reason of
  concern.

  [Groovy SRU]
  The groovy SRU is a sync of the 2.1.11 micro release from Debian unstable 
which also incorporates changes to the documentation: A typo fix, replacing 
focal with groovy in examples, and minor Dutch manual pages translation updates.

  We do not have test cases for the documentation changes, and we do not
  consider there to be a huge regression potential. As long as they
  build, they should be readable - maybe some words are wrong in the
  translation, who knows.

  [Original bug report]
  Test Case
  1. Install Ubuntu Desktop on hardware with an nVidia card and select to 
install 3rd party drivers
  2. Proceed with installation

  The following error message is displayed in /var/log/syslog
  /plugininstall.py: Verifying downloads ...
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: 
"Version: '4.4.10-10ubuntu4' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: 
'1.2.11.dfsg-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: 
'1.0.9-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: 
'1.1.3-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: 
'1.3.4-0ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: 
'3.6.0-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: 
'1.1.5-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: 
'5.0.3-1' not found."
  /plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.

[Touch-packages] [Bug 1934943] Re: /usr/libexec/tracker-store:5:g_log_structured_standard:_call_rule_func:translate_PropertyListNotEmpty:_call_rule_func:translate_TriplesSameSubject

[Launchpad Bug Tracker]

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

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

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

Title:
  /usr/libexec/tracker-
  
store:5:g_log_structured_standard:_call_rule_func:translate_PropertyListNotEmpty:_call_rule_func:translate_TriplesSameSubject

Status in tracker package in Ubuntu:
  Confirmed

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1934943/+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 1934943] [NEW] /usr/libexec/tracker-store:5:g_log_structured_standard:_call_rule_func:translate_PropertyListNotEmpty:_call_rule_func:translate_TriplesSameSubject

[errors.ubuntu.com bug bridge]

Public bug reported:

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

** Affects: tracker (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: groovy hirsute impish

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

Title:
  /usr/libexec/tracker-
  
store:5:g_log_structured_standard:_call_rule_func:translate_PropertyListNotEmpty:_call_rule_func:translate_TriplesSameSubject

Status in tracker package in Ubuntu:
  Confirmed

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1934943/+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 1152187] Re: [MIR] systemd

[Steve Langasek]

Override component to main
systemd-container 237-3ubuntu10.48 in bionic amd64: 
universe/admin/optional/100% -> main
systemd-container 237-3ubuntu10.48 in bionic arm64: 
universe/admin/optional/100% -> main
systemd-container 237-3ubuntu10.48 in bionic armhf: 
universe/admin/optional/100% -> main
systemd-container 237-3ubuntu10.48 in bionic i386: universe/admin/optional/100% 
-> main
systemd-container 237-3ubuntu10.48 in bionic ppc64el: 
universe/admin/optional/100% -> main
systemd-container 237-3ubuntu10.48 in bionic s390x: 
universe/admin/optional/100% -> main
6 publications overridden.
Override component to main
systemd-container 237-3ubuntu10.38 in bionic amd64: 
universe/admin/optional/100% -> main
systemd-container 237-3ubuntu10.38 in bionic arm64: 
universe/admin/optional/100% -> main
systemd-container 237-3ubuntu10.38 in bionic armhf: 
universe/admin/optional/100% -> main
systemd-container 237-3ubuntu10.38 in bionic i386: universe/admin/optional/100% 
-> main
systemd-container 237-3ubuntu10.38 in bionic ppc64el: 
universe/admin/optional/100% -> main
systemd-container 237-3ubuntu10.38 in bionic s390x: 
universe/admin/optional/100% -> main
6 publications overridden.


** Changed in: systemd (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  [MIR] systemd

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  * The package is in universe and built on all archs:
  https://launchpad.net/ubuntu/+source/systemd/44-10ubuntu1

  * Rationale:

  - in a first step we want systemd-services promoted to replace ubuntu-
  system-services

  -  We will also want to move from consolekit to logind soon
  (https://blueprints.launchpad.net/ubuntu/+spec/foundations-1303
  -consolekit-logind-migration)

  - udev has been merged in the systemd source upstream so we will want
  to build it from there at some point as well

  we don't plan to use the systemd init system at this point

  * Security:

  there has been some security issues in the past
  http://secunia.com/advisories/search/?search=systemd
  http://secunia.com/advisories/48220/
  http://secunia.com/advisories/48208/
  http://secunia.com/advisories/48331/

  Those are mostly logind issue and have been fixed upstream.

  Our current package is outdated but we do plan to update it before
  starting using logind. There should be no issue with the services

  * Quality:
  - there is no RC bug in debian: 
http://bugs.debian.org/cgi-bin/pkgreport.cgi?repeatmerged=no&src=systemd
  - there is no bug open in launchpad: 
https://launchpad.net/ubuntu/+source/systemd/+bugs
  - upstream is active and responsive to issues

  The desktop bugs team is subscribed to the package in launchpad,
  foundations/desktop will maintain the package and look to the bug
  reports regularly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1152187/+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 1927078] Re: Don't allow useradd to use fully numeric names

[William Wilson]

This patch only disallows usernames that are strictly numeric per
vorlon's comment above. It also adds more test cases for invalid
usernames such as "0123456789" and valid usernames such as "0root" and
"0.o". This time I also remembered that '0' is a digit.

** Patch added: "Fully numeric and more tests patch"
   
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1927078/+attachment/5509701/+files/lp1927078_fully_numeric.debdiff

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

Title:
  Don't allow useradd to use fully numeric names

Status in shadow package in Ubuntu:
  New
Status in shadow source package in Focal:
  New
Status in shadow source package in Groovy:
  New
Status in shadow source package in Hirsute:
  New
Status in shadow source package in Impish:
  New

Bug description:
  [Description]

  Fully numeric names support in Ubuntu is inconsistent in Focal onwards
  because systemd does not like them[1] but are still allowed by default
  by useradd, leaving the session behavior in hands of the running
  applications. Two examples:

  1. After creating a user named "0", the user can log in via ssh or
  console but loginctl won't create a session for it:

  root@focal:/home/ubuntu# useradd -m 0
  root@focal:/home/ubuntu# id 0
  uid=1005(0) gid=1005(0) groups=1005(0)

  ..

  0@192.168.122.6's password:
  Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.8.0-48-generic x86_64)

  Last login: Thu Apr  8 16:17:06 2021 from 192.168.122.1
  $ loginctl
  No sessions.
  $ w
   16:20:09 up 4 min,  1 user,  load average: 0.03, 0.14, 0.08
  USER TTY  FROM LOGIN@   IDLE   JCPU   PCPU WHAT
  0pts/0192.168.122.116:170.00s  0.00s  0.00s w  

  And pam-systemd shows the following message:

  Apr 08 16:17:06 focal sshd[1584]: pam_unix(sshd:session): session opened for 
user 0 by (uid=0)
  Apr 08 16:17:06 focal sshd[1584]: pam_systemd(sshd:session): pam-systemd 
initializing
  Apr 08 16:17:06 focal sshd[1584]: pam_systemd(sshd:session): Failed to get 
user record: Invalid argument

  
  2. With that same username, every successful authentication in gdm will loop 
back to gdm again instead of starting gnome, making the user unable to login.

  
  Making useradd fail (unless --badnames is set) when a fully numeric name is 
used will make the default OS behavior consistent.

  
  [Other info]

  - Upstream does not support fully numeric usernames
  - useradd has a --badnames parameter that would still allow the use of these 
type of names

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1927078/+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 1931064] Re: lxc autotest failure with kernel >= 5.13

[Kelsey Skunberg]

** Tags added: focal sru-20210621

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

Title:
  lxc autotest failure with kernel >= 5.13

Status in ubuntu-kernel-tests:
  New
Status in lxc package in Ubuntu:
  New

Bug description:
  The lxc autotest is failing with the following error(s) on the latest
  kernel linux-unstable 5.13:

  FAIL: lxc-tests: lxc-test-apparmor (1s)
  ---
  failed - opened /sys/kernel/uevent_helper
  ---
  PASS: lxc-tests: lxc-test-apparmor-generated (0s)
  PASS: lxc-tests: lxc-test-apparmor-mount (29s)
  FAIL: lxc-tests: lxc-test-attach (1s)
  ---
  attach.c: 410: main: Using "/tmp/attach_x8lgO2" as temporary log file for 
container lxc-attach-test

  I was able to bisect the problem and found that the offending commit
  is:

  bfb819ea20ce8bbeeba17e1a6418bf8bda91fc28 ("proc: Check
  /proc/$pid/attr/ writes against file opener")

  This commit looks like a sane fix, so simply reverting it in the
  kernel doesn't seem a viable solution.

  I think we should address and understand the issue in the lxc package.

  Detailed log of the failure: https://autopkgtest.ubuntu.com/results
  /autopkgtest-impish-canonical-kernel-team-
  bootstrap/impish/amd64/l/lxc/20210601_082733_a3ae4@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1931064/+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 1927078] Re: Don't allow useradd to use fully numeric names

[Steve Langasek]

It's fine for us to disallow fully-numeric usernames (including octal
and hex syntax).

It would be inappropriate, especially in SRU, to change the policy to
restrict other usernames that happen to begin with a digit.

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

Title:
  Don't allow useradd to use fully numeric names

Status in shadow package in Ubuntu:
  New
Status in shadow source package in Focal:
  New
Status in shadow source package in Groovy:
  New
Status in shadow source package in Hirsute:
  New
Status in shadow source package in Impish:
  New

Bug description:
  [Description]

  Fully numeric names support in Ubuntu is inconsistent in Focal onwards
  because systemd does not like them[1] but are still allowed by default
  by useradd, leaving the session behavior in hands of the running
  applications. Two examples:

  1. After creating a user named "0", the user can log in via ssh or
  console but loginctl won't create a session for it:

  root@focal:/home/ubuntu# useradd -m 0
  root@focal:/home/ubuntu# id 0
  uid=1005(0) gid=1005(0) groups=1005(0)

  ..

  0@192.168.122.6's password:
  Welcome to Ubuntu 20.04.2 LTS (GNU/Linux 5.8.0-48-generic x86_64)

  Last login: Thu Apr  8 16:17:06 2021 from 192.168.122.1
  $ loginctl
  No sessions.
  $ w
   16:20:09 up 4 min,  1 user,  load average: 0.03, 0.14, 0.08
  USER TTY  FROM LOGIN@   IDLE   JCPU   PCPU WHAT
  0pts/0192.168.122.116:170.00s  0.00s  0.00s w  

  And pam-systemd shows the following message:

  Apr 08 16:17:06 focal sshd[1584]: pam_unix(sshd:session): session opened for 
user 0 by (uid=0)
  Apr 08 16:17:06 focal sshd[1584]: pam_systemd(sshd:session): pam-systemd 
initializing
  Apr 08 16:17:06 focal sshd[1584]: pam_systemd(sshd:session): Failed to get 
user record: Invalid argument

  
  2. With that same username, every successful authentication in gdm will loop 
back to gdm again instead of starting gnome, making the user unable to login.

  
  Making useradd fail (unless --badnames is set) when a fully numeric name is 
used will make the default OS behavior consistent.

  
  [Other info]

  - Upstream does not support fully numeric usernames
  - useradd has a --badnames parameter that would still allow the use of these 
type of names

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1927078/+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 1934936] Re: package libwind0-heimdal 7.7.0+dfsg-2build1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is dif

[surajvinay]

Rebooted and tried updating again.  Did not work.
Chose partial update this time and everything downloaded once more with 
5.13.0.11 kernel and all processes completed. Rebooted and got the new look 
with dual desktops showing up.

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

Title:
  package libwind0-heimdal 7.7.0+dfsg-2build1 failed to install/upgrade:
  trying to overwrite shared
  '/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is
  different from other instances of package libwind0-heimdal:i386

Status in heimdal package in Ubuntu:
  New

Bug description:
  fresh 21.10 install and 1 reboot later it said there was additional
  updates and while doing so the error popped up

  ProblemType: Package
  DistroRelease: Ubuntu 21.10
  Package: libwind0-heimdal 7.7.0+dfsg-2build1
  ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Thu Jul  8 01:45:16 2021
  DuplicateSignature:
   package:libwind0-heimdal:7.7.0+dfsg-2build1
   Unpacking libwind0-heimdal:i386 (7.7.0+dfsg-2build1) over (7.7.0+dfsg-2) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-8FDC3J/53-libwind0-heimdal_7.7.0+dfsg-2build1_i386.deb 
(--unpack):
trying to overwrite shared 
'/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is different from 
other instances of package libwind0-heimdal:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is different from 
other instances of package libwind0-heimdal:i386
  InstallationDate: Installed on 2021-06-05 (32 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Python3Details: /usr/bin/python3.9, Python 3.9.6, python3-minimal, 3.9.4-1
  PythonDetails: N/A
  RebootRequiredPkgs:
   libc6
   libc6
  RelatedPackageVersions:
   dpkg 1.20.9ubuntu2
   apt  2.3.6
  SourcePackage: heimdal
  Title: package libwind0-heimdal 7.7.0+dfsg-2build1 failed to install/upgrade: 
trying to overwrite shared 
'/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is different from 
other instances of package libwind0-heimdal:i386
  UpgradeStatus: Upgraded to impish on 2021-07-07 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/1934936/+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 1934931] Re: (X)ubuntu 20.04: GUFW and MS-Teams slow down traffic intermittently

[costales]

Hi,
Gufw can't affect that behavior. I think is an ufw issue.
Best regards.

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

** Changed in: gui-ufw
   Status: New => Invalid

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

Title:
  (X)ubuntu 20.04: GUFW and MS-Teams slow down traffic intermittently

Status in Gufw:
  Invalid
Status in ufw package in Ubuntu:
  New

Bug description:
  Thanks for Gufw!

  inxi -S output: Xubuntu standard LTS installation - Kernel:
  5.4.0-77-generic x86_64 bits: 64 Desktop: Xfce 4.14.2 Distro: Ubuntu
  20.04.2 LTS (Focal Fossa). GUFW 20.04.1, MS Teams 1.4.00.13653
  (64-Bit) (all up to date at the time of this report).

  ** Problem: 250 Mbit LAN connection slowing down *intermittently*, but 
reproducible, to a crawl of 300 kbit or less if Gufw is activated parallel to 
MS teams. 
  * Gufw is used with only basic settings provided after installation 
(in:denied/out:allowed and nothing else set, no further rules).
  * There has not to be any active call in teams, just running it seems to 
cause the problem after a while (<5 minutes).
  * After congestion for some time (minutes), the system may recover to full 
speed again, only to succumb again after a few minutes. 
  * Other parallel running programs' connections are slowed down as well in 
accordance, e.g. parallel samba file sharing download is affected as well.
  * Stopping teams restores the connection speed after a short while (~1 
minute).
  * Parallel connections to the LAN(router) are not inhibited, it is just the 
one computer. 

  Teams seems to switch ports after restarting (UDP6/~34nnn-4). I
  set up a range to be allowed within ports used by teams (e.g.
  3:5, allow in/outbound) to no avail, connections dropped still
  to low speed.

  Thanks and regards,
  Christoph

To manage notifications about this bug go to:
https://bugs.launchpad.net/gui-ufw/+bug/1934931/+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 1934936] Re: package libwind0-heimdal 7.7.0+dfsg-2build1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is dif

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package libwind0-heimdal 7.7.0+dfsg-2build1 failed to install/upgrade:
  trying to overwrite shared
  '/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is
  different from other instances of package libwind0-heimdal:i386

Status in heimdal package in Ubuntu:
  New

Bug description:
  fresh 21.10 install and 1 reboot later it said there was additional
  updates and while doing so the error popped up

  ProblemType: Package
  DistroRelease: Ubuntu 21.10
  Package: libwind0-heimdal 7.7.0+dfsg-2build1
  ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Thu Jul  8 01:45:16 2021
  DuplicateSignature:
   package:libwind0-heimdal:7.7.0+dfsg-2build1
   Unpacking libwind0-heimdal:i386 (7.7.0+dfsg-2build1) over (7.7.0+dfsg-2) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-8FDC3J/53-libwind0-heimdal_7.7.0+dfsg-2build1_i386.deb 
(--unpack):
trying to overwrite shared 
'/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is different from 
other instances of package libwind0-heimdal:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is different from 
other instances of package libwind0-heimdal:i386
  InstallationDate: Installed on 2021-06-05 (32 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Python3Details: /usr/bin/python3.9, Python 3.9.6, python3-minimal, 3.9.4-1
  PythonDetails: N/A
  RebootRequiredPkgs:
   libc6
   libc6
  RelatedPackageVersions:
   dpkg 1.20.9ubuntu2
   apt  2.3.6
  SourcePackage: heimdal
  Title: package libwind0-heimdal 7.7.0+dfsg-2build1 failed to install/upgrade: 
trying to overwrite shared 
'/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is different from 
other instances of package libwind0-heimdal:i386
  UpgradeStatus: Upgraded to impish on 2021-07-07 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/1934936/+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 1934936] [NEW] package libwind0-heimdal 7.7.0+dfsg-2build1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is d

[surajvinay]

Public bug reported:

fresh 21.10 install and 1 reboot later it said there was additional
updates and while doing so the error popped up

ProblemType: Package
DistroRelease: Ubuntu 21.10
Package: libwind0-heimdal 7.7.0+dfsg-2build1
ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
Uname: Linux 5.11.0-22-generic x86_64
ApportVersion: 2.20.11-0ubuntu67
Architecture: amd64
CasperMD5CheckResult: pass
Date: Thu Jul  8 01:45:16 2021
DuplicateSignature:
 package:libwind0-heimdal:7.7.0+dfsg-2build1
 Unpacking libwind0-heimdal:i386 (7.7.0+dfsg-2build1) over (7.7.0+dfsg-2) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-8FDC3J/53-libwind0-heimdal_7.7.0+dfsg-2build1_i386.deb 
(--unpack):
  trying to overwrite shared 
'/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is different from 
other instances of package libwind0-heimdal:i386
ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is different from 
other instances of package libwind0-heimdal:i386
InstallationDate: Installed on 2021-06-05 (32 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
Python3Details: /usr/bin/python3.9, Python 3.9.6, python3-minimal, 3.9.4-1
PythonDetails: N/A
RebootRequiredPkgs:
 libc6
 libc6
RelatedPackageVersions:
 dpkg 1.20.9ubuntu2
 apt  2.3.6
SourcePackage: heimdal
Title: package libwind0-heimdal 7.7.0+dfsg-2build1 failed to install/upgrade: 
trying to overwrite shared 
'/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is different from 
other instances of package libwind0-heimdal:i386
UpgradeStatus: Upgraded to impish on 2021-07-07 (0 days ago)

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


** Tags: amd64 apport-package impish package-conflict package-from-proposed

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

Title:
  package libwind0-heimdal 7.7.0+dfsg-2build1 failed to install/upgrade:
  trying to overwrite shared
  '/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is
  different from other instances of package libwind0-heimdal:i386

Status in heimdal package in Ubuntu:
  New

Bug description:
  fresh 21.10 install and 1 reboot later it said there was additional
  updates and while doing so the error popped up

  ProblemType: Package
  DistroRelease: Ubuntu 21.10
  Package: libwind0-heimdal 7.7.0+dfsg-2build1
  ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Thu Jul  8 01:45:16 2021
  DuplicateSignature:
   package:libwind0-heimdal:7.7.0+dfsg-2build1
   Unpacking libwind0-heimdal:i386 (7.7.0+dfsg-2build1) over (7.7.0+dfsg-2) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-8FDC3J/53-libwind0-heimdal_7.7.0+dfsg-2build1_i386.deb 
(--unpack):
trying to overwrite shared 
'/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is different from 
other instances of package libwind0-heimdal:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is different from 
other instances of package libwind0-heimdal:i386
  InstallationDate: Installed on 2021-06-05 (32 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Python3Details: /usr/bin/python3.9, Python 3.9.6, python3-minimal, 3.9.4-1
  PythonDetails: N/A
  RebootRequiredPkgs:
   libc6
   libc6
  RelatedPackageVersions:
   dpkg 1.20.9ubuntu2
   apt  2.3.6
  SourcePackage: heimdal
  Title: package libwind0-heimdal 7.7.0+dfsg-2build1 failed to install/upgrade: 
trying to overwrite shared 
'/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is different from 
other instances of package libwind0-heimdal:i386
  UpgradeStatus: Upgraded to impish on 2021-07-07 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/heimdal/+bug/1934936/+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 1934933] [NEW] cloud-init dhclient apparmor denied with noexec on /var/tmp

[Tom Kopchak]

Public bug reported:

Hello - we are seeing an issue on multiple Azure hosts where there is a
long delay during bootup.  This appears to be related to an apparmor
issue with dhclient executed via cloud-init when /var is mounted noexec.
Because /var is noexec, the original dhclient is executed rather than
the copy in /var/tmp/cloud-init, which causes the AppArmor profile to be
applied.

This prevents the instance from being able to record the DHCP lease
information to /var/tmp/cloud-init/cloud-init-dhcp-*, which prevents the
instance from being able to obtain goalstate information, and with
cloud-init 21.2-3 or later, results in an extended delay during boot due
to a recent change in azure.py (https://github.com/canonical/cloud-
init/pull/842).

This issue does not occur in default Ubuntu installations (including the
Ubuntu 20.04 default Azure image), as the dhcp.py script in cloud-init
behaves differently, copying /usr/sbin/dhclient to /var/tmp/cloud-init
/cloud-init-dhcp-x/dhclient when /var allows executables, and the
apparmor profiles then do not apply to the copied executable.

The syslog will show the following entry when the instance boots up: 
cloud-init[820]: 2021-07-07 14:50:40,661 - dhcp.py[WARNING]: dhclient did not 
produce expected files: dhcp.leases, dhclient.pid

The cloud-init.log file will show this entry when this issue is occurring. 
Since the instance has no IP address at this stage of the boot process, an 
unreachable network is to be expected:
azure.py[DEBUG]: Failed HTTP request with Azure endpoint 
http://168.63.129.16/machine/?comp=goalstate during attempt 240 with exception: 
HTTPConnectionPool(host='168.63.129.16', port=80): Max retries exceeded with 
url: /machine/?comp=goalstate (Caused by 
NewConnectionError(': Failed to establish a new connection: [Errno 101] Network is 
unreachable'))

With the timeouts in azure.py described above, the instance will not
boot for around 20 minutes until all 240 connection attempts are
completed.

This is logged in /var/log/audit/audit.log, showing that the dhclient process 
executed from cloud-init is unable to write the dhclient.pid and dhcp.leases 
files that are needed to continue the datasource retrieval process:
type=AVC msg=audit(1625678140.496:1898): apparmor="DENIED" operation="open" 
profile="/{,usr/}sbin/dhclient" name="/proc/8537/task/8540/comm" pid=8537 
comm="dhclient" requested_mask="wr" denied_mask="wr" fsuid=0 ouid=0

Adding the following file resolves the issue: 
/etc/apparmor.d/local/sbin.dhclient
/var/tmp/cloud-init/cloud-init-dhcp-*/dhclient.pid lrw,
/var/tmp/cloud-init/cloud-init-dhcp-*/dhcp.leases lrw,

This allows dhclient executed via cloud-init to write the dhclient.pid
and dhcp.leases files to /var/tmp/cloud-init and the instance to boot
normally.

** Affects: isc-dhcp (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  cloud-init dhclient apparmor denied with noexec on /var/tmp

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  Hello - we are seeing an issue on multiple Azure hosts where there is
  a long delay during bootup.  This appears to be related to an apparmor
  issue with dhclient executed via cloud-init when /var is mounted
  noexec.  Because /var is noexec, the original dhclient is executed
  rather than the copy in /var/tmp/cloud-init, which causes the AppArmor
  profile to be applied.

  This prevents the instance from being able to record the DHCP lease
  information to /var/tmp/cloud-init/cloud-init-dhcp-*, which prevents
  the instance from being able to obtain goalstate information, and with
  cloud-init 21.2-3 or later, results in an extended delay during boot
  due to a recent change in azure.py (https://github.com/canonical
  /cloud-init/pull/842).

  This issue does not occur in default Ubuntu installations (including
  the Ubuntu 20.04 default Azure image), as the dhcp.py script in cloud-
  init behaves differently, copying /usr/sbin/dhclient to /var/tmp
  /cloud-init/cloud-init-dhcp-x/dhclient when /var allows
  executables, and the apparmor profiles then do not apply to the copied
  executable.

  The syslog will show the following entry when the instance boots up: 
  cloud-init[820]: 2021-07-07 14:50:40,661 - dhcp.py[WARNING]: dhclient did not 
produce expected files: dhcp.leases, dhclient.pid

  The cloud-init.log file will show this entry when this issue is occurring. 
Since the instance has no IP address at this stage of the boot process, an 
unreachable network is to be expected:
  azure.py[DEBUG]: Failed HTTP request with Azure endpoint 
http://168.63.129.16/machine/?comp=goalstate during attempt 240 with exception: 
HTTPConnectionPool(host='168.63.129.16', port=80): Max retries exceeded with 
url: /machine/?comp=goalstate (Caused by 
NewConnectionError(': Failed to establ

[Touch-packages] [Bug 1785383] Re: missing EDNS0 record confuses systemd-resolved

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 248.3-1ubuntu2

---
systemd (248.3-1ubuntu2) impish; urgency=medium

  [ Kai-Heng Feng ]
  * d/p/hwdb-Add-ProBook-to-use-micmute-hotkey.patch:
- Add ProBook to use micmute hotkey (LP: #1930910)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=30b96fac92d911cb725f7220a9539085a24fe5f7

  [ Jeremy Szu ]
  * d/p/lp1932352-hwdb-Add-mic-mute-key-mapping-for-HP-Elite-Dragonfly.patch:
- Fix micmute hotkeys on HP Elite Dragonfly (LP: #1932352)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=ac93cfcca200644b743deab94f655ccd74ff90a6

  [ Dan Streetman ]
  * 
d/p/debian/UBUNTU-resolved-Mitigate-DVE-2018-0001-by-retrying-NXDOMAIN-with.patch:
Remove no-longer-needed patch for DVE-2018-0001 (LP: #1785383)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=943b2dd5884e67c67d6336c24352b02e17809df0
  * 
d/p/lp1931578/0001-network-default-RequiredForOnline-false-if-Activacti.patch,
d/p/lp1931578/0002-networkctl-add-field-Required-For-Online.patch,

d/p/lp1931578/0003-test-add-test-to-verify-RequiredForOnline-setting-wi.patch:
Adjust default for RequiredForOnline when using ActivationPolicy
(LP: #1931578)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=d0b8629ec14396f1a5d5f7c132c9b687065136b0
  * d/p/lp1894622-Add-systemd-resolve-backwards-compatibility-section-.patch:
Add man page symlink and deprecation notice for systemd-resolve
(LP: #1894622)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=f719185253f989d6708c894150c0878cabee6589
  * d/p/lp1858210/0001-time-simplify-get_timezones.patch,

d/p/lp1858210/0002-time-split-get_timezone-into-main-function-and-zone1.patch,
d/p/lp1858210/0003-time-get-timezones-from-tzdata.zi.patch:
Parse tzdata.zi so timedatectl list-timezones also lists aliases
(LP: #1858210)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=8e5b0a7c7c4e1e29b5e81511a1145633d9b75be5

 -- Dan Streetman   Tue, 06 Jul 2021 13:37:59
-0400

** Changed in: systemd (Ubuntu Impish)
   Status: Fix Committed => Fix Released

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

Title:
  missing EDNS0 record confuses systemd-resolved

Status in systemd:
  Fix Released
Status in dnsmasq package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in dnsmasq source package in Bionic:
  Triaged
Status in systemd source package in Bionic:
  Fix Released
Status in dnsmasq source package in Focal:
  Fix Released
Status in systemd source package in Focal:
  Fix Released
Status in dnsmasq source package in Groovy:
  Fix Released
Status in systemd source package in Groovy:
  Fix Released
Status in dnsmasq source package in Hirsute:
  Fix Released
Status in systemd source package in Hirsute:
  Fix Released
Status in dnsmasq source package in Impish:
  Fix Released
Status in systemd source package in Impish:
  Fix Released

Bug description:
  [Impact]
  dnsmasq 2.79 and below omits EDNS0 OPT records when returning an empty answer 
for a domain it is authoritative for. systemd-resolved seems to get confused by 
this in certain circumstances; when using the stub resolver and requesting an 
address for which there are no  records, there can sometimes be a five 
second hang in resolution.

  [Fix]
  This is fixed by upstream commit 
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commit;h=1682d15a744880b0398af75eadf68fe66128af78

  Not sure if it is worth cherry picking? I imagine the most likely
  trigger will be dnsmasq on routers which are not likely to be running
  Ubuntu, but maybe just in case.

  I also think there are some logic issues in systemd-resolved, upstream
  bug filed:

  https://github.com/systemd/systemd/issues/9785

  [Test Case]
  Simple-ish test case for bionic:

  ---
  IFACE=dummy0
  SUBNET=10.0.0

  ip link add $IFACE type dummy
  ifconfig $IFACE ${SUBNET}.1/24
  dnsmasq -h -R -d -C /dev/null -2 $IFACE -z -i $IFACE -I lo 
--host-record=test.test,${SUBNET}.1 --server=/test/ &

  dig -t a test.test @10.0.0.1 | grep EDNS
  # should return "; EDNS ..."
  dig -t  test.test @10.0.0.1 | grep EDNS
  # again, should return "; EDNS ..." but doesn't
  ---

  To reproduce the systemd-resolved side of the problem

  ---
  # as above, but
  # now configure systemd-resolved to look at only 10.0.0.1, then

  systemd-resolve --reset-server-features
  # should exhibit five second delay then connect, assuming sshd is running :)
  ssh test.test
  ---

  
  More detailed test case for focal and later:

  install dnsmasq on a bionic system and start it, listening to an
  interface that is externally reachable, e.g. for a normal libvirt vm
  with interface name 'ens3':

[Touch-packages] [Bug 1930910] Re: Fix micmute hotkeys on HP ProBooks

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 248.3-1ubuntu2

---
systemd (248.3-1ubuntu2) impish; urgency=medium

  [ Kai-Heng Feng ]
  * d/p/hwdb-Add-ProBook-to-use-micmute-hotkey.patch:
- Add ProBook to use micmute hotkey (LP: #1930910)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=30b96fac92d911cb725f7220a9539085a24fe5f7

  [ Jeremy Szu ]
  * d/p/lp1932352-hwdb-Add-mic-mute-key-mapping-for-HP-Elite-Dragonfly.patch:
- Fix micmute hotkeys on HP Elite Dragonfly (LP: #1932352)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=ac93cfcca200644b743deab94f655ccd74ff90a6

  [ Dan Streetman ]
  * 
d/p/debian/UBUNTU-resolved-Mitigate-DVE-2018-0001-by-retrying-NXDOMAIN-with.patch:
Remove no-longer-needed patch for DVE-2018-0001 (LP: #1785383)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=943b2dd5884e67c67d6336c24352b02e17809df0
  * 
d/p/lp1931578/0001-network-default-RequiredForOnline-false-if-Activacti.patch,
d/p/lp1931578/0002-networkctl-add-field-Required-For-Online.patch,

d/p/lp1931578/0003-test-add-test-to-verify-RequiredForOnline-setting-wi.patch:
Adjust default for RequiredForOnline when using ActivationPolicy
(LP: #1931578)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=d0b8629ec14396f1a5d5f7c132c9b687065136b0
  * d/p/lp1894622-Add-systemd-resolve-backwards-compatibility-section-.patch:
Add man page symlink and deprecation notice for systemd-resolve
(LP: #1894622)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=f719185253f989d6708c894150c0878cabee6589
  * d/p/lp1858210/0001-time-simplify-get_timezones.patch,

d/p/lp1858210/0002-time-split-get_timezone-into-main-function-and-zone1.patch,
d/p/lp1858210/0003-time-get-timezones-from-tzdata.zi.patch:
Parse tzdata.zi so timedatectl list-timezones also lists aliases
(LP: #1858210)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=8e5b0a7c7c4e1e29b5e81511a1145633d9b75be5

 -- Dan Streetman   Tue, 06 Jul 2021 13:37:59
-0400

** Changed in: systemd (Ubuntu Impish)
   Status: Fix Committed => Fix Released

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

Title:
  Fix micmute hotkeys on HP ProBooks

Status in HWE Next:
  New
Status in OEM Priority Project:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Groovy:
  In Progress
Status in systemd source package in Hirsute:
  In Progress
Status in systemd source package in Impish:
  Fix Released

Bug description:
  [Impact]
  Micmute hotkey on many HP ProBooks don't work.

  [Fix]
  Commit a7161e0288d1 ("hwdb: Add ProBook to use micmute hotkey"), to map AT 
keyboard's scancode to micmute hotkey.

  [Test]
  With the one-liner fix, micmute hotkey works on all the ProBooks I tested.

  [Where problems could occur]
  The hwdb originally only matches a few ProBooks, the fix changes that to 
match all ProBook models. So if there's any ProBook that uses the scancode for 
another purpose, there will be a regression.
  However, the risk is rather slim because HP explicitly states that all 
ProBooks use the same scancode for mic mute hotkey.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1930910/+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 1858210] Re: timedatectl doesn't list all timezones

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 248.3-1ubuntu2

---
systemd (248.3-1ubuntu2) impish; urgency=medium

  [ Kai-Heng Feng ]
  * d/p/hwdb-Add-ProBook-to-use-micmute-hotkey.patch:
- Add ProBook to use micmute hotkey (LP: #1930910)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=30b96fac92d911cb725f7220a9539085a24fe5f7

  [ Jeremy Szu ]
  * d/p/lp1932352-hwdb-Add-mic-mute-key-mapping-for-HP-Elite-Dragonfly.patch:
- Fix micmute hotkeys on HP Elite Dragonfly (LP: #1932352)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=ac93cfcca200644b743deab94f655ccd74ff90a6

  [ Dan Streetman ]
  * 
d/p/debian/UBUNTU-resolved-Mitigate-DVE-2018-0001-by-retrying-NXDOMAIN-with.patch:
Remove no-longer-needed patch for DVE-2018-0001 (LP: #1785383)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=943b2dd5884e67c67d6336c24352b02e17809df0
  * 
d/p/lp1931578/0001-network-default-RequiredForOnline-false-if-Activacti.patch,
d/p/lp1931578/0002-networkctl-add-field-Required-For-Online.patch,

d/p/lp1931578/0003-test-add-test-to-verify-RequiredForOnline-setting-wi.patch:
Adjust default for RequiredForOnline when using ActivationPolicy
(LP: #1931578)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=d0b8629ec14396f1a5d5f7c132c9b687065136b0
  * d/p/lp1894622-Add-systemd-resolve-backwards-compatibility-section-.patch:
Add man page symlink and deprecation notice for systemd-resolve
(LP: #1894622)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=f719185253f989d6708c894150c0878cabee6589
  * d/p/lp1858210/0001-time-simplify-get_timezones.patch,

d/p/lp1858210/0002-time-split-get_timezone-into-main-function-and-zone1.patch,
d/p/lp1858210/0003-time-get-timezones-from-tzdata.zi.patch:
Parse tzdata.zi so timedatectl list-timezones also lists aliases
(LP: #1858210)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=8e5b0a7c7c4e1e29b5e81511a1145633d9b75be5

 -- Dan Streetman   Tue, 06 Jul 2021 13:37:59
-0400

** Changed in: systemd (Ubuntu Impish)
   Status: In Progress => Fix Released

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

Title:
  timedatectl doesn't list all timezones

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Won't Fix
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Groovy:
  In Progress
Status in systemd source package in Hirsute:
  In Progress
Status in systemd source package in Impish:
  Fix Released

Bug description:
  [impact]

  timedatectl list-timezones doesn't show many common timezones that are
  actually considered 'aliases', such as Europe/Bratislava or
  US/Eastern.

  [test case]

  $ timedatectl list-timezones | grep Eastern
  $

  [regression potential]

  any regression would likely result in an incorrect list of timezones
  shown from list-timezones, or failure to correctly set a timezone

  [scope]

  this is needed in f and later

  this is fixed upstream with PR 20066 which was just merged, so this is
  needed in all releases in ubuntu

  in bionic, the 'tzdata.zi' file that the new code uses isn't present,
  so this won't work on bionic, thus marking it wontfix

  [original description]

  Is there some filter determining which timezones are displayed by
  `timedatectl list-timezones`? My zone, Europe/Bratislava, is missing.
  Even stranger, it can successfully be set by timedatectl.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: systemd 242-7ubuntu3.2
  ProcVersionSignature: Ubuntu 5.3.0-1014.16-raspi2 5.3.10
  Uname: Linux 5.3.0-1014-raspi2 aarch64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: arm64
  Date: Fri Jan  3 15:36:03 2020
  Lspci:

  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=1 bcm2708_fb.fbwidth=1824 
bcm2708_fb.fbheight=984 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec0 
vc_mem.mem_size=0x4000  net.ifnames=0 dwc_otg.lpm_enable=0 
console=ttyS0,115200 console=tty1 root=LABEL=writable rootfstype=ext4 
elevator=deadline rootwait fixrtc
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.systemd.resolved.conf: 2020-01-03T01:02:47.779343

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1858210/+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 1894622] Re: Missing manpage for systemd-resolve

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 248.3-1ubuntu2

---
systemd (248.3-1ubuntu2) impish; urgency=medium

  [ Kai-Heng Feng ]
  * d/p/hwdb-Add-ProBook-to-use-micmute-hotkey.patch:
- Add ProBook to use micmute hotkey (LP: #1930910)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=30b96fac92d911cb725f7220a9539085a24fe5f7

  [ Jeremy Szu ]
  * d/p/lp1932352-hwdb-Add-mic-mute-key-mapping-for-HP-Elite-Dragonfly.patch:
- Fix micmute hotkeys on HP Elite Dragonfly (LP: #1932352)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=ac93cfcca200644b743deab94f655ccd74ff90a6

  [ Dan Streetman ]
  * 
d/p/debian/UBUNTU-resolved-Mitigate-DVE-2018-0001-by-retrying-NXDOMAIN-with.patch:
Remove no-longer-needed patch for DVE-2018-0001 (LP: #1785383)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=943b2dd5884e67c67d6336c24352b02e17809df0
  * 
d/p/lp1931578/0001-network-default-RequiredForOnline-false-if-Activacti.patch,
d/p/lp1931578/0002-networkctl-add-field-Required-For-Online.patch,

d/p/lp1931578/0003-test-add-test-to-verify-RequiredForOnline-setting-wi.patch:
Adjust default for RequiredForOnline when using ActivationPolicy
(LP: #1931578)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=d0b8629ec14396f1a5d5f7c132c9b687065136b0
  * d/p/lp1894622-Add-systemd-resolve-backwards-compatibility-section-.patch:
Add man page symlink and deprecation notice for systemd-resolve
(LP: #1894622)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=f719185253f989d6708c894150c0878cabee6589
  * d/p/lp1858210/0001-time-simplify-get_timezones.patch,

d/p/lp1858210/0002-time-split-get_timezone-into-main-function-and-zone1.patch,
d/p/lp1858210/0003-time-get-timezones-from-tzdata.zi.patch:
Parse tzdata.zi so timedatectl list-timezones also lists aliases
(LP: #1858210)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=8e5b0a7c7c4e1e29b5e81511a1145633d9b75be5

 -- Dan Streetman   Tue, 06 Jul 2021 13:37:59
-0400

** Changed in: systemd (Ubuntu Impish)
   Status: In Progress => Fix Released

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

Title:
  Missing manpage for systemd-resolve

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Groovy:
  In Progress
Status in systemd source package in Hirsute:
  In Progress
Status in systemd source package in Impish:
  Fix Released

Bug description:
  [impact]

  'man systemd-resolve' fails

  [test case]

  $ man systemd-resolve
  No manual entry for systemd-resolve

  [regression potential]

  incorrect man page result for resolvectl or resolvconf, or possibly
  users using deprecated systemd-resolve longer than they should

  [scope]

  this is needed in f and later

  systemd-resolve was replaced with resolvectl between b and f, so the
  man page exists in b

  [other info]

  the systemd-resolve binary is a symlink to the real binary resolvectl, and 
users should use resolvectl for all new uses. A patch to the upstream man page 
was proposed and merged in this PR:
  https://github.com/systemd/systemd/pull/20064

  however that is being discussed and may be reverted in this PR:
  https://github.com/systemd/systemd/pull/20077

  as discussed in the revert PR, it's ok for upstream to elide docs
  about deprecated tooling; however distros should include deprecation
  info and thus I believe it's appropriate to include the man page
  symlink so users trying 'man systemd-resolve' will get the correct
  'resolvectl' man page, which includes doc about how they shoudl start
  using 'resolvectl' instead

  [original description]

  On my Focal machine there is no file /usr/share/man/man1/systemd-resolve.1.gz
  This means that man systemd-resolve fails.

  http://manpages.ubuntu.com/manpages/bionic/en/man1/systemd-
  resolve.1.html exists and has a link on top to 20.04LTS: it points to
  http://manpages.ubuntu.com/manpages/focal/en/man1/systemd-
  resolve.1.html , that however 404's, and one ends up being redirected
  to Bionic's.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1894622/+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 1931578] Re: ActivationPolicy=down causes delay at boot

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 248.3-1ubuntu2

---
systemd (248.3-1ubuntu2) impish; urgency=medium

  [ Kai-Heng Feng ]
  * d/p/hwdb-Add-ProBook-to-use-micmute-hotkey.patch:
- Add ProBook to use micmute hotkey (LP: #1930910)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=30b96fac92d911cb725f7220a9539085a24fe5f7

  [ Jeremy Szu ]
  * d/p/lp1932352-hwdb-Add-mic-mute-key-mapping-for-HP-Elite-Dragonfly.patch:
- Fix micmute hotkeys on HP Elite Dragonfly (LP: #1932352)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=ac93cfcca200644b743deab94f655ccd74ff90a6

  [ Dan Streetman ]
  * 
d/p/debian/UBUNTU-resolved-Mitigate-DVE-2018-0001-by-retrying-NXDOMAIN-with.patch:
Remove no-longer-needed patch for DVE-2018-0001 (LP: #1785383)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=943b2dd5884e67c67d6336c24352b02e17809df0
  * 
d/p/lp1931578/0001-network-default-RequiredForOnline-false-if-Activacti.patch,
d/p/lp1931578/0002-networkctl-add-field-Required-For-Online.patch,

d/p/lp1931578/0003-test-add-test-to-verify-RequiredForOnline-setting-wi.patch:
Adjust default for RequiredForOnline when using ActivationPolicy
(LP: #1931578)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=d0b8629ec14396f1a5d5f7c132c9b687065136b0
  * d/p/lp1894622-Add-systemd-resolve-backwards-compatibility-section-.patch:
Add man page symlink and deprecation notice for systemd-resolve
(LP: #1894622)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=f719185253f989d6708c894150c0878cabee6589
  * d/p/lp1858210/0001-time-simplify-get_timezones.patch,

d/p/lp1858210/0002-time-split-get_timezone-into-main-function-and-zone1.patch,
d/p/lp1858210/0003-time-get-timezones-from-tzdata.zi.patch:
Parse tzdata.zi so timedatectl list-timezones also lists aliases
(LP: #1858210)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=8e5b0a7c7c4e1e29b5e81511a1145633d9b75be5

 -- Dan Streetman   Tue, 06 Jul 2021 13:37:59
-0400

** Changed in: systemd (Ubuntu Impish)
   Status: In Progress => Fix Released

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

Title:
  ActivationPolicy=down causes delay at boot

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Won't Fix
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Groovy:
  In Progress
Status in systemd source package in Hirsute:
  In Progress
Status in systemd source package in Impish:
  Fix Released

Bug description:
  [impact]

  The ActivationPolicy= parameter was backported in bug 1664844, but
  when this is set to down (or always-down or manual) without also
  specifying RequiredForOnline=no, then there is a hang at boot waiting
  for the network to finish coming online.

  [test case]

  With the latest systemd, which includes support for ActivationPolicy=,
  configure an interface with ActivationPolicy=down and reboot. The boot
  will be delayed waiting for that interface.

  [regression potential]

  any regression would likely cause the system to encounter delay at
  boot, or to boot before configured interface(s) are fully online at
  boot, or to fail to correctly/fully configure interface(s).

  [scope]

  this is needed for all releases

  this is proposed upstream in:
  https://github.com/systemd/systemd/pull/19883

  [other info]

  this is only needed for convenience, as any configuration using
  ActivationPolicy=down can also easily add RequiredForOnline=no

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1931578/+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 1932352] Re: Fix micmute hotkeys on HP Elite Dragonfly

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 248.3-1ubuntu2

---
systemd (248.3-1ubuntu2) impish; urgency=medium

  [ Kai-Heng Feng ]
  * d/p/hwdb-Add-ProBook-to-use-micmute-hotkey.patch:
- Add ProBook to use micmute hotkey (LP: #1930910)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=30b96fac92d911cb725f7220a9539085a24fe5f7

  [ Jeremy Szu ]
  * d/p/lp1932352-hwdb-Add-mic-mute-key-mapping-for-HP-Elite-Dragonfly.patch:
- Fix micmute hotkeys on HP Elite Dragonfly (LP: #1932352)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=ac93cfcca200644b743deab94f655ccd74ff90a6

  [ Dan Streetman ]
  * 
d/p/debian/UBUNTU-resolved-Mitigate-DVE-2018-0001-by-retrying-NXDOMAIN-with.patch:
Remove no-longer-needed patch for DVE-2018-0001 (LP: #1785383)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=943b2dd5884e67c67d6336c24352b02e17809df0
  * 
d/p/lp1931578/0001-network-default-RequiredForOnline-false-if-Activacti.patch,
d/p/lp1931578/0002-networkctl-add-field-Required-For-Online.patch,

d/p/lp1931578/0003-test-add-test-to-verify-RequiredForOnline-setting-wi.patch:
Adjust default for RequiredForOnline when using ActivationPolicy
(LP: #1931578)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=d0b8629ec14396f1a5d5f7c132c9b687065136b0
  * d/p/lp1894622-Add-systemd-resolve-backwards-compatibility-section-.patch:
Add man page symlink and deprecation notice for systemd-resolve
(LP: #1894622)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=f719185253f989d6708c894150c0878cabee6589
  * d/p/lp1858210/0001-time-simplify-get_timezones.patch,

d/p/lp1858210/0002-time-split-get_timezone-into-main-function-and-zone1.patch,
d/p/lp1858210/0003-time-get-timezones-from-tzdata.zi.patch:
Parse tzdata.zi so timedatectl list-timezones also lists aliases
(LP: #1858210)

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=8e5b0a7c7c4e1e29b5e81511a1145633d9b75be5

 -- Dan Streetman   Tue, 06 Jul 2021 13:37:59
-0400

** Changed in: systemd (Ubuntu Impish)
   Status: In Progress => Fix Released

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

Title:
  Fix micmute hotkeys on HP Elite Dragonfly

Status in OEM Priority Project:
  Triaged
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Groovy:
  In Progress
Status in systemd source package in Hirsute:
  In Progress
Status in systemd source package in Impish:
  Fix Released

Bug description:
  [Impact]
  Mic mute key is no function on HP Elite Dragonfly.

  [Fix]
  After confirming with HP, there are two model names for Dragonfly:
  * HP Elite Dragonfly G2 Notebook PC
  * HP Elite Dragonfly Max Notebook PC
  Thus, the commit 
  Commit c1b8c966eccb7be1cae0a30670f5e1fcd88b47fa maps the 81 scan code to mic 
mute key.

  [Test]
  After patching it, the mic mute key could functioned well on my Dragonfly 
laptop.

  [Where problems could occur]
  There is not old rule for Dragonfly dmi string in current hwdb.
  Which means the Dragonfly is using default HP key map:
  ```
  evdev:atkbd:dmi:bvn*:bvr*:bd*:svnHP*:pn*:*

   KEYBOARD_KEY_81=fn_esc
  ```
  This patch will change the HP machine (if product name contains 
pnHPEliteDragonfly*) to map 81 to mic mute key.
  If a machine (pnHPEliteDragonfly*) works good in the past then this patch may 
cause it's mic mute key become malfunction.
  However, this rule is confirmed/provided from HP.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1932352/+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 1933516] Re: gzip: error while loading shared libraries: cannot restore segment prot after reloc: Operation not permitted

[Robie Basak]

Thanks - I had missed the Debian bug link.

** Description changed:

  [impact]
  
  gzip/libgzip fails for systemd services using MemoryDenyWriteExecute=yes
  
  [test case]
  
  note this only fails on ppc64el
  
  create service file /etc/systemd/system/test-localegen.service with
  content:
  
  [Service]
  MemoryDenyWriteExecute=yes
  ExecStart=/usr/sbin/locale-gen
  
- 
  run systemctl daemon-reload, and start the service:
  
- ubuntu@test-ppc-b:~$ sudo systemctl daemon-reload 
- ubuntu@test-ppc-b:~$ sudo systemctl start test-localegen.service 
- ubuntu@test-ppc-b:~$ sudo systemctl status test-localegen.service 
+ ubuntu@test-ppc-b:~$ sudo systemctl daemon-reload
+ ubuntu@test-ppc-b:~$ sudo systemctl start test-localegen.service
+ ubuntu@test-ppc-b:~$ sudo systemctl status test-localegen.service
  ○ test-localegen.service
-  Loaded: loaded 
(8;;file://test-ppc-b/etc/systemd/system/test-localegen.service^G/etc/systemd/system/test-localegen.service8;;^G;
 static)
-  Active: inactive (dead)
+  Loaded: loaded 
(8;;file://test-ppc-b/etc/systemd/system/test-localegen.service^G/etc/systemd/system/test-localegen.service8;;^G;
 static)
+  Active: inactive (dead)
  
  Jun 24 16:44:18 test-ppc-b locale-gen[2737]: gzip: error while loading shared 
libraries: cannot restore segment prot after reloc: Operation not permitted
  Jun 24 16:44:18 test-ppc-b locale-gen[2738]: gzip: error while loading shared 
libraries: cannot restore segment prot after reloc: Operation not permitted
  Jun 24 16:44:18 test-ppc-b locale-gen[2739]: gzip: error while loading shared 
libraries: cannot restore segment prot after reloc: Operation not permitted
  Jun 24 16:44:18 test-ppc-b locale-gen[2740]: gzip: error while loading shared 
libraries: cannot restore segment prot after reloc: Operation not permitted
  Jun 24 16:44:18 test-ppc-b locale-gen[2741]: gzip: error while loading shared 
libraries: cannot restore segment prot after reloc: Operation not permitted
  Jun 24 16:44:18 test-ppc-b locale-gen[2506]: failed to set locale!
  Jun 24 16:44:18 test-ppc-b locale-gen[2506]: [error] default character map 
file `ANSI_X3.4-1968' not found: No such file or directory
  Jun 24 16:44:18 test-ppc-b locale-gen[2489]:  done
  Jun 24 16:44:18 test-ppc-b locale-gen[2483]: Generation complete.
  Jun 24 16:44:18 test-ppc-b systemd[1]: test-localegen.service: Deactivated 
successfully.
  
- 
  [regression potential]
  
  as this sets NO_ASM any regression would likely involve changed
  performance or architecture-specific failures
+ 
+ [racb] As NO_ASM switches code implementations inside gzip, it's
+ possible that this regresses behaviour if a bug exists in the C
+ implementation but not in the assembly implementation. However in
+ mitigation the C implementation has been in use since Focal, and it
+ doesn't look like anything relevant to this change has been changed
+ since Bionic.
  
  [scope]
  
  this is needed only in b
  
  this was fixed in debian at version 1.9-2.1, so this is fixed already in
  f and later

** Changed in: gzip (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-bionic

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

Title:
  gzip: error while loading shared libraries: cannot restore segment
  prot after reloc: Operation not permitted

Status in gzip package in Ubuntu:
  Fix Released
Status in gzip source package in Bionic:
  Fix Committed
Status in gzip package in Debian:
  Fix Released

Bug description:
  [impact]

  gzip/libgzip fails for systemd services using
  MemoryDenyWriteExecute=yes

  [test case]

  note this only fails on ppc64el

  create service file /etc/systemd/system/test-localegen.service with
  content:

  [Service]
  MemoryDenyWriteExecute=yes
  ExecStart=/usr/sbin/locale-gen

  run systemctl daemon-reload, and start the service:

  ubuntu@test-ppc-b:~$ sudo systemctl daemon-reload
  ubuntu@test-ppc-b:~$ sudo systemctl start test-localegen.service
  ubuntu@test-ppc-b:~$ sudo systemctl status test-localegen.service
  ○ test-localegen.service
   Loaded: loaded 
(8;;file://test-ppc-b/etc/systemd/system/test-localegen.service^G/etc/systemd/system/test-localegen.service8;;^G;
 static)
   Active: inactive (dead)

  Jun 24 16:44:18 test-ppc-b locale-gen[2737]: gzip: error while loading shared 
libraries: cannot restore segment prot after reloc: Operation not permitted
  Jun 24 16:44:18 test-ppc-b locale-gen[2738]: gzip: error while loading shared 
libraries: cannot restore segment prot after reloc: Operation not permitted
  Jun 24 16:44:18 test-ppc-b locale-gen[2739]: gzip: error while loading shared 
libraries: cannot restore segment prot after reloc: Operation not permitted
  Jun 24 16:44:18 test-ppc-b locale-gen[2740]: gzip: error while loading shared 
libraries: cannot restore segment prot afte

[Touch-packages] [Bug 1933516] Please test proposed package

[Robie Basak]

Hello Dan, or anyone else affected,

Accepted gzip into bionic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/gzip/1.6-5ubuntu1.1 in
a few hours, and then in the -proposed repository.

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

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

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

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

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

Title:
  gzip: error while loading shared libraries: cannot restore segment
  prot after reloc: Operation not permitted

Status in gzip package in Ubuntu:
  Fix Released
Status in gzip source package in Bionic:
  Fix Committed
Status in gzip package in Debian:
  Fix Released

Bug description:
  [impact]

  gzip/libgzip fails for systemd services using
  MemoryDenyWriteExecute=yes

  [test case]

  note this only fails on ppc64el

  create service file /etc/systemd/system/test-localegen.service with
  content:

  [Service]
  MemoryDenyWriteExecute=yes
  ExecStart=/usr/sbin/locale-gen

  run systemctl daemon-reload, and start the service:

  ubuntu@test-ppc-b:~$ sudo systemctl daemon-reload
  ubuntu@test-ppc-b:~$ sudo systemctl start test-localegen.service
  ubuntu@test-ppc-b:~$ sudo systemctl status test-localegen.service
  ○ test-localegen.service
   Loaded: loaded 
(8;;file://test-ppc-b/etc/systemd/system/test-localegen.service^G/etc/systemd/system/test-localegen.service8;;^G;
 static)
   Active: inactive (dead)

  Jun 24 16:44:18 test-ppc-b locale-gen[2737]: gzip: error while loading shared 
libraries: cannot restore segment prot after reloc: Operation not permitted
  Jun 24 16:44:18 test-ppc-b locale-gen[2738]: gzip: error while loading shared 
libraries: cannot restore segment prot after reloc: Operation not permitted
  Jun 24 16:44:18 test-ppc-b locale-gen[2739]: gzip: error while loading shared 
libraries: cannot restore segment prot after reloc: Operation not permitted
  Jun 24 16:44:18 test-ppc-b locale-gen[2740]: gzip: error while loading shared 
libraries: cannot restore segment prot after reloc: Operation not permitted
  Jun 24 16:44:18 test-ppc-b locale-gen[2741]: gzip: error while loading shared 
libraries: cannot restore segment prot after reloc: Operation not permitted
  Jun 24 16:44:18 test-ppc-b locale-gen[2506]: failed to set locale!
  Jun 24 16:44:18 test-ppc-b locale-gen[2506]: [error] default character map 
file `ANSI_X3.4-1968' not found: No such file or directory
  Jun 24 16:44:18 test-ppc-b locale-gen[2489]:  done
  Jun 24 16:44:18 test-ppc-b locale-gen[2483]: Generation complete.
  Jun 24 16:44:18 test-ppc-b systemd[1]: test-localegen.service: Deactivated 
successfully.

  [regression potential]

  as this sets NO_ASM any regression would likely involve changed
  performance or architecture-specific failures

  [racb] As NO_ASM switches code implementations inside gzip, it's
  possible that this regresses behaviour if a bug exists in the C
  implementation but not in the assembly implementation. However in
  mitigation the C implementation has been in use since Focal, and it
  doesn't look like anything relevant to this change has been changed
  since Bionic.

  [scope]

  this is needed only in b

  this was fixed in debian at version 1.9-2.1, so this is fixed already
  in f and later

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gzip/+bug/1933516/+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 1934439] Re: Add Ubuntu Pro banner to Livepatch page

[Lech Sandecki]

It's for xenial, bionic and focal

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

Title:
  Add Ubuntu Pro banner to Livepatch page

Status in software-properties package in Ubuntu:
  New
Status in software-properties source package in Xenial:
  New
Status in software-properties source package in Bionic:
  New
Status in software-properties source package in Focal:
  New
Status in software-properties source package in Hirsute:
  New
Status in software-properties source package in Impish:
  New

Bug description:
  Add a banner to the Livepatch page to invite users to join the Ubuntu
  Pro for Desktop.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1934439/+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 1925320] Autopkgtest regression report (xorg-server/2:1.20.11-1ubuntu1~20.04.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted xorg-server 
(2:1.20.11-1ubuntu1~20.04.1) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

bambam/1.0.1+dfsg-1 (arm64, armhf)
notepadqq/2.0.0~beta1-1build1 (armhf)
libsoup2.4/2.70.0-1 (amd64)


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

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

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

Thank you!

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

Title:
  Backport packages for 20.04.3 HWE stack

Status in directx-headers package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-12 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in directx-headers source package in Focal:
  Fix Committed
Status in libdrm source package in Focal:
  Fix Committed
Status in llvm-toolchain-12 source package in Focal:
  Fix Released
Status in mesa source package in Focal:
  Fix Committed
Status in xorg-server source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  These are needed for 20.04.3 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  [What could go wrong]

  directx-headers: a new package, nothing can go wrong

  libdrm: adds some new api, no changes to old stuff

  llvm-12: a new package, no regression potential on it's own

  mesa: a new major release, but we'll pull the final stable release of
  21.0.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new point-release, 1.20.x series is in deep maintenance
  mode, so there should be little chance of breakage

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/1925320/+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] Fwd: [Bug 1918458] Re: [Swift SF515-51T, Realtek ALC256, Grey Speaker, Internal] Playback problem, no sound from speakers, headphones ok

[Thibaut Soubrié]

FYI

-- Forwarded message -
De : Alex Gould <1918...@bugs.launchpad.net>
Date: mer. 7 juil. 2021 à 18:26
Subject: [Bug 1918458] Re: [Swift SF515-51T, Realtek ALC256, Grey Speaker,
Internal] Playback problem, no sound from speakers, headphones ok
To: 


Hello,

I also just ran all commands without a restart and none of them caused
sound to come from the speaker. There is still no sound after a restart.

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1918458

Title:
  [Swift SF515-51T, Realtek ALC256, Grey Speaker, Internal] Playback
  problem, no sound from speakers, headphones ok

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Expect : sound from speaker
  Instead, obtain : no sound.


  Tried various configuration of /etc/modprobe.d/alsa-conf with :

  options snd-hda-intel model= and
  options snd-intel-dspcfg dsp_driver=3 or 1
  and systematic reboot.

  Either I get dummy output, or I get proper output detection, alsamixer
  and pavucontrol seems 100% ok, but no sound comes from the speakers.

  I'm under a dualboot with Windows 10, BIOS fast boot disabled.
  Ubuntu 20.04.2 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  thibauts   1522 F pulseaudio
   /dev/snd/pcmC0D0p:   thibauts   1522 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 10 18:10:30 2021
  InstallationDate: Installed on 2021-03-09 (1 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64
(20210209.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp
failed
  Symptom_Card: Cannon Point-LP High Definition Audio Controller -
sof-hda-dsp
  Symptom_Jack: Grey Speaker, Internal
  Symptom_Type: Only some of outputs are working
  Title: [Swift SF515-51T, Realtek ALC256, Grey Speaker, Internal] Playback
problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/24/2019
  dmi.bios.release: 1.4
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.04
  dmi.board.asset.tag: Default string
  dmi.board.name: Guinness_WL
  dmi.board.vendor: WL
  dmi.board.version: V1.04
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.04
  dmi.ec.firmware.release: 1.6
  dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvrV1.04:bd05/24/2019:br1.4:efr1.6:svnAcer:pnSwiftSF515-51T:pvrV1.04:rvnWL:rnGuinness_WL:rvrV1.04:cvnAcer:ct10:cvrV1.04:
  dmi.product.family: Swift 5
  dmi.product.name: Swift SF515-51T
  dmi.product.sku: 
  dmi.product.version: V1.04
  dmi.sys.vendor: Acer
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2021-03-10T18:04:19.277254

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

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

Title:
  [Swift SF515-51T, Realtek ALC256, Grey Speaker, Internal] Playback
  problem, no sound from speakers, headphones ok

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Expect : sound from speaker
  Instead, obtain : no sound.

  
  Tried various configuration of /etc/modprobe.d/alsa-conf with :

  options snd-hda-intel model= and
  options snd-intel-dspcfg dsp_driver=3 or 1
  and systematic reboot.

  Either I get dummy output, or I get proper output detection, alsamixer
  and pavucontrol seems 100% ok, but no sound comes from the speakers.

  I'm under a dualboot with Windows 10, BIOS fast boot disabled.
  Ubuntu 20.04.2 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  thibauts   1522 F pulseaudio
   /dev/snd/pcmC0D0p:   thibauts   1522 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 10 18:10:30 2021
  InstallationDate: Installed on 2021-03-09 (1 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed
  Symptom_Card: Cannon Point-LP High Definition Audio Controller - sof-hda-dsp
  Symptom_Jack: Grey Speaker, In

[Touch-packages] [Bug 1925320] Please test proposed package

[Robie Basak]

Hello Timo, or anyone else affected,

Accepted xorg-server into focal-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/xorg-
server/2:1.20.11-1ubuntu1~20.04.2 in a few hours, and then in the
-proposed repository.

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

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

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

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

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

Title:
  Backport packages for 20.04.3 HWE stack

Status in directx-headers package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-12 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xorg-server package in Ubuntu:
  Invalid
Status in directx-headers source package in Focal:
  Fix Committed
Status in libdrm source package in Focal:
  Fix Committed
Status in llvm-toolchain-12 source package in Focal:
  Fix Released
Status in mesa source package in Focal:
  Fix Committed
Status in xorg-server source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  These are needed for 20.04.3 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  [What could go wrong]

  directx-headers: a new package, nothing can go wrong

  libdrm: adds some new api, no changes to old stuff

  llvm-12: a new package, no regression potential on it's own

  mesa: a new major release, but we'll pull the final stable release of
  21.0.x series, so there shouldn't be any regressions left at that
  point

  xserver: a new point-release, 1.20.x series is in deep maintenance
  mode, so there should be little chance of breakage

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/1925320/+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 1918458] Re: [Swift SF515-51T, Realtek ALC256, Grey Speaker, Internal] Playback problem, no sound from speakers, headphones ok

[Alex Gould]

Hello,

I also just ran all commands without a restart and none of them caused
sound to come from the speaker. There is still no sound after a restart.

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

Title:
  [Swift SF515-51T, Realtek ALC256, Grey Speaker, Internal] Playback
  problem, no sound from speakers, headphones ok

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Expect : sound from speaker
  Instead, obtain : no sound.

  
  Tried various configuration of /etc/modprobe.d/alsa-conf with :

  options snd-hda-intel model= and
  options snd-intel-dspcfg dsp_driver=3 or 1
  and systematic reboot.

  Either I get dummy output, or I get proper output detection, alsamixer
  and pavucontrol seems 100% ok, but no sound comes from the speakers.

  I'm under a dualboot with Windows 10, BIOS fast boot disabled.
  Ubuntu 20.04.2 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  thibauts   1522 F pulseaudio
   /dev/snd/pcmC0D0p:   thibauts   1522 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 10 18:10:30 2021
  InstallationDate: Installed on 2021-03-09 (1 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed
  Symptom_Card: Cannon Point-LP High Definition Audio Controller - sof-hda-dsp
  Symptom_Jack: Grey Speaker, Internal
  Symptom_Type: Only some of outputs are working
  Title: [Swift SF515-51T, Realtek ALC256, Grey Speaker, Internal] Playback 
problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/24/2019
  dmi.bios.release: 1.4
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.04
  dmi.board.asset.tag: Default string
  dmi.board.name: Guinness_WL
  dmi.board.vendor: WL
  dmi.board.version: V1.04
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.04
  dmi.ec.firmware.release: 1.6
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.04:bd05/24/2019:br1.4:efr1.6:svnAcer:pnSwiftSF515-51T:pvrV1.04:rvnWL:rnGuinness_WL:rvrV1.04:cvnAcer:ct10:cvrV1.04:
  dmi.product.family: Swift 5
  dmi.product.name: Swift SF515-51T
  dmi.product.sku: 
  dmi.product.version: V1.04
  dmi.sys.vendor: Acer
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2021-03-10T18:04:19.277254

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1918458/+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 1934783] Re: Graphical glitches with Mesa 21.0.3 on AMD Radeon RX 5600 XT

[Mateusz Stachowski]

Hirsute live image works without problems.

That has mesa versioned as 21.0.1. So it looks like the problem is in
21.0.3

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

Title:
  Graphical glitches with Mesa 21.0.3 on AMD Radeon RX 5600 XT

Status in mesa package in Ubuntu:
  New
Status in mesa source package in Focal:
  New

Bug description:
  Since the update to Mesa 21.0.3 I have graphical glitches in desktop:
  Unity, Gnome Shell both sessions (X.org and Wayland).

  Also most of the programs have glitches. However Firefox seems
  unaffected.

  CPU:
Info: 6-Core AMD Ryzen 5 3600 [MT MCP] speed: 3916 MHz
min/max: 2200/3600 MHz
  Graphics:
Device-1: AMD Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT]
driver: amdgpu v: kernel
Display: x11 server: X.Org 1.20.11 driver: loaded: amdgpu,ati
unloaded: fbdev,modesetting,radeon,vesa resolution: 1920x1080~60Hz
OpenGL: renderer: AMD Radeon RX 5600 XT (NAVI10 DRM 3.35.0
5.4.0-79-generic LLVM 12.0.0)
v: 4.6 Mesa 21.0.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1934783/+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 1934906] [NEW] Inaccurate errno reporting in ptrace attach error messages

[Seth Forshee]

Public bug reported:

Ubuntu carries a patch for gdb, ptrace-error-verbosity.patch, to print
some extra information about why attaching to a process might have
failed. This inserts a fprintf_unfiltered() call between the ptrace()
and the corresponding perror(). Recently something has changed which
causes errno to be set to ENOTTY after the failed ptrace but before
calling perror(). It's clear that the ptrace() errno is EPERM, since
that's the only condition which will print the extra information,
however the error message printed is "Inappropriate ioctl for device".

Using strace I observed failing tty ioctls which seem to be responsible:

ptrace(PTRACE_ATTACH, 11538)= -1 EPERM (Operation not permitted)
ioctl(2, TCGETS, 0x7fff1d9c2590)= -1 ENOTTY (Inappropriate ioctl for 
device)
write(2, "Could not attach to process.  If"..., 221Could not attach to process. 
 If your uid matches the uid of the target
process, check the setting of /proc/sys/kernel/yama/ptrace_scope, or try
again as the root user.  For more details, see /etc/sysctl.d/10-ptrace.conf
) = 221
ioctl(2, TCGETS, 0x7fff1d9c2590)= -1 ENOTTY (Inappropriate ioctl for 
device)
...
ioctl(1, TCSBRK, 1) = -1 ENOTTY (Inappropriate ioctl for 
device)
...
write(2, "ptrace: Inappropriate ioctl for "..., 39ptrace: Inappropriate ioctl 
for device.) = 39


Our qa-regression-testing kernel security tests include some ptrace tests which 
expect attach to fail with an "Operation not permitted" error message. So in 
addition to being inaccurate, this change in behavior is causing kernel 
regression testing to fail.

This behavior can be reproduced using scripts/test-kernel-security.py
from qa-regression-testing.

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

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

Title:
  Inaccurate errno reporting in ptrace attach error messages

Status in gdb package in Ubuntu:
  New

Bug description:
  Ubuntu carries a patch for gdb, ptrace-error-verbosity.patch, to print
  some extra information about why attaching to a process might have
  failed. This inserts a fprintf_unfiltered() call between the ptrace()
  and the corresponding perror(). Recently something has changed which
  causes errno to be set to ENOTTY after the failed ptrace but before
  calling perror(). It's clear that the ptrace() errno is EPERM, since
  that's the only condition which will print the extra information,
  however the error message printed is "Inappropriate ioctl for device".

  Using strace I observed failing tty ioctls which seem to be
  responsible:

  ptrace(PTRACE_ATTACH, 11538)= -1 EPERM (Operation not permitted)
  ioctl(2, TCGETS, 0x7fff1d9c2590)= -1 ENOTTY (Inappropriate ioctl for 
device)
  write(2, "Could not attach to process.  If"..., 221Could not attach to 
process.  If your uid matches the uid of the target
  process, check the setting of /proc/sys/kernel/yama/ptrace_scope, or try
  again as the root user.  For more details, see /etc/sysctl.d/10-ptrace.conf
  ) = 221
  ioctl(2, TCGETS, 0x7fff1d9c2590)= -1 ENOTTY (Inappropriate ioctl for 
device)
  ...
  ioctl(1, TCSBRK, 1) = -1 ENOTTY (Inappropriate ioctl for 
device)
  ...
  write(2, "ptrace: Inappropriate ioctl for "..., 39ptrace: Inappropriate ioctl 
for device.) = 39

  
  Our qa-regression-testing kernel security tests include some ptrace tests 
which expect attach to fail with an "Operation not permitted" error message. So 
in addition to being inaccurate, this change in behavior is causing kernel 
regression testing to fail.

  This behavior can be reproduced using scripts/test-kernel-security.py
  from qa-regression-testing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1934906/+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 1920047] Re: sanlock global lock creation fail

[Heitor Alves de Siqueira]

We've determined this to be due to using disks with mixed sector sizes
(i.e. different physical and logical sector sizes). The mentioned patch
[0] enables lvmlockd to create shared leases in mixed sector sized
disks, but additional support is needed in sanlock for these to work
correctly.

The required sanlock patches are:
* d5e4def0d087 - sanlock: add flags to specify sector size [1]
* 445e86700fa3 - configurable sector size and align size [2]

If we don't have these additional sanlock patches, sanlock isn't able to
find the written leases due to alignment issues and ultimately those are
handled as invalid. Unfortunately, both sanlock patches are extensive
and change a lot of low-level internal structures, so providing them as
SRU updates would be prone to backporting errors and regressions.

Since both lvm2 and sanlock are working as expected with non-mixed
sector sizes, and the current versions actively prevent leases to be
written to mixed sector disks, we can consider that things are working
correctly. Support for mixed sector sizes should be considered a
"feature" instead, which is available starting with the versions below:

- lvm2: 2.03.10
- sanlock: 3.8.0

These versions are available in Ubuntu releases starting with Hirsute,
and have been provided as backports in focal-backports and groovy-
backports. Please refer to bug #1929432 and bug #1928708 for further
details on the -backports versions.

[0] https://sourceware.org/git/?p=lvm2.git;a=commitdiff;h=2d1fe38d84d4
[1] https://pagure.io/sanlock/c/d5e4def0d087
[2] https://pagure.io/sanlock/c/445e86700fa3


** Changed in: lvm2 (Ubuntu Focal)
   Status: Confirmed => Won't Fix

** Changed in: lvm2 (Ubuntu Groovy)
   Status: Confirmed => Won't Fix

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

Title:
  sanlock global lock creation fail

Status in lvm2 package in Ubuntu:
  Fix Released
Status in lvm2 source package in Focal:
  Won't Fix
Status in lvm2 source package in Groovy:
  Won't Fix

Bug description:
  Hello,

  Running Ubuntu server 20.04, I cannot create a shared VG using sanlock
  :

  # vgcreate --shared foo /dev/mapper/vol
Enabling sanlock global lock
Skipping global lock: lockspace not found or started
Logical volume "lvmlock" created.
VG foo init failed: -28
Failed to initialize lock args for lock type sanlock
Volume group "foo" successfully removed

  Messages in /var/log/syslog

  lvmlockd[446807]: 1616089866 WARNING: mixed block sizes physical 4096 logical 
512 (using 4096) for /dev/mapper/foo-lvmlock
  lvmlockd[446807]: 1616089866 S lvm_foo init_vg_san write_resource gl error 
-28 /dev/mapper/foo-lvmlock

  # lsb_release -rd
  Description:Ubuntu 20.04.2 LTS
  Release:20.04

  # dpkg -l | grep lvm
  ii  liblvm2cmd2.03:amd64 2.03.07-1ubuntu1 
 amd64LVM2 command library
  ii  lvm2 2.03.07-1ubuntu1 
 amd64Linux Logical Volume Manager
  ii  lvm2-lockd   2.03.07-1ubuntu1 
 amd64LVM locking daemon

  A similar bug report from RHEL8 :
  https://bugzilla.redhat.com/show_bug.cgi?id=1833837

  Bug has been fixed upstream :
  
https://sourceware.org/git/?p=lvm2.git;a=commit;h=2d1fe38d84d499011d13ae1ea11535398528fc87

  It seems to be included in version 2.03.10 :
  https://sourceware.org/git/?p=lvm2.git;a=shortlog;h=refs/tags/v2_03_10

  How can we get this patch included in Ubuntu 20.04 ?

  King Regards,

  Charles

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

[Simark]

Ok, well can you check what are the calls to linux_init_abi (put a
breakpoint or add a printf) and tell me what the num_disp_step_buffers
argument values are?  I would expect them to be 1.

If you see a call where num_disp_step_buffers is 0, then please provide
the backtrace at that point.

Thanks!

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

Title:
  gdb 11 doesn't work on impish/s390x: internal-error:
  displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*,
  thread_info*, CORE_ADDR&): Assertion
  `gdbarch_data->num_disp_step_buffers > 0' failed.

Status in gdb:
  Confirmed
Status in gdb package in Ubuntu:
  Fix Released

Bug description:
  gdb doesn't work on impish/s390x at the minute. Even if you say 'no'
  to both questions you still can't debug:

  ubuntu@laney-bos01-s390x-2:~/glib-networking-2.66.0/build$ gdb ls
  GNU gdb (Ubuntu 11.0.50.20210630-0ubuntu1) 11.0.50.20210630-git
  Copyright (C) 2021 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.
  Type "show copying" and "show warranty" for details.
  This GDB was configured as "s390x-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .

  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from ls...
  (No debugging symbols found in ls)
  (gdb) run
  Starting program: /usr/bin/ls
  /build/gdb-Ti35un/gdb-11.0.50.20210630/gdb/linux-tdep.c:2550: internal-error: 
displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, 
thread_info*, CORE_ADDR&): Assertion `gdbarch_data->num_disp_step_buffers > 0' 
failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Quit this debugging session? (y or n) n

  This is a bug, please report it.  For instructions, see:
  .

  /build/gdb-Ti35un/gdb-11.0.50.20210630/gdb/linux-tdep.c:2550: internal-error: 
displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, 
thread_info*, CORE_ADDR&): Assertion `gdbarch_data->num_disp_step_buffers > 0' 
failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Create a core file of GDB? (y or n) n
  Command aborted.
  (gdb)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/1934505/+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 1934505]

[Matthias Klose]

looking at a 20210706 build, the fix seems to work.  Unsure what I did
wrong yesterday.  So the fix would be needed on the trunk and the
branch.

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

Title:
  gdb 11 doesn't work on impish/s390x: internal-error:
  displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*,
  thread_info*, CORE_ADDR&): Assertion
  `gdbarch_data->num_disp_step_buffers > 0' failed.

Status in gdb:
  Confirmed
Status in gdb package in Ubuntu:
  Fix Released

Bug description:
  gdb doesn't work on impish/s390x at the minute. Even if you say 'no'
  to both questions you still can't debug:

  ubuntu@laney-bos01-s390x-2:~/glib-networking-2.66.0/build$ gdb ls
  GNU gdb (Ubuntu 11.0.50.20210630-0ubuntu1) 11.0.50.20210630-git
  Copyright (C) 2021 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.
  Type "show copying" and "show warranty" for details.
  This GDB was configured as "s390x-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .

  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from ls...
  (No debugging symbols found in ls)
  (gdb) run
  Starting program: /usr/bin/ls
  /build/gdb-Ti35un/gdb-11.0.50.20210630/gdb/linux-tdep.c:2550: internal-error: 
displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, 
thread_info*, CORE_ADDR&): Assertion `gdbarch_data->num_disp_step_buffers > 0' 
failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Quit this debugging session? (y or n) n

  This is a bug, please report it.  For instructions, see:
  .

  /build/gdb-Ti35un/gdb-11.0.50.20210630/gdb/linux-tdep.c:2550: internal-error: 
displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, 
thread_info*, CORE_ADDR&): Assertion `gdbarch_data->num_disp_step_buffers > 0' 
failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Create a core file of GDB? (y or n) n
  Command aborted.
  (gdb)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/1934505/+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 1934505]

[Matthias Klose]

yes, double checked,
https://launchpad.net/ubuntu/+source/gdb/11.0.90.20210705-0ubuntu2/+build/21752179

Ubuntu's compiler enables a few hardening flags by default,
-D_FORTIFY_SOURCE=2 -fstack-protector-strong -Wformat -Werror=format-security
but that's unchanged from the gdb 10.2 build.

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

Title:
  gdb 11 doesn't work on impish/s390x: internal-error:
  displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*,
  thread_info*, CORE_ADDR&): Assertion
  `gdbarch_data->num_disp_step_buffers > 0' failed.

Status in gdb:
  Confirmed
Status in gdb package in Ubuntu:
  Fix Released

Bug description:
  gdb doesn't work on impish/s390x at the minute. Even if you say 'no'
  to both questions you still can't debug:

  ubuntu@laney-bos01-s390x-2:~/glib-networking-2.66.0/build$ gdb ls
  GNU gdb (Ubuntu 11.0.50.20210630-0ubuntu1) 11.0.50.20210630-git
  Copyright (C) 2021 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.
  Type "show copying" and "show warranty" for details.
  This GDB was configured as "s390x-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .

  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from ls...
  (No debugging symbols found in ls)
  (gdb) run
  Starting program: /usr/bin/ls
  /build/gdb-Ti35un/gdb-11.0.50.20210630/gdb/linux-tdep.c:2550: internal-error: 
displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, 
thread_info*, CORE_ADDR&): Assertion `gdbarch_data->num_disp_step_buffers > 0' 
failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Quit this debugging session? (y or n) n

  This is a bug, please report it.  For instructions, see:
  .

  /build/gdb-Ti35un/gdb-11.0.50.20210630/gdb/linux-tdep.c:2550: internal-error: 
displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, 
thread_info*, CORE_ADDR&): Assertion `gdbarch_data->num_disp_step_buffers > 0' 
failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Create a core file of GDB? (y or n) n
  Command aborted.
  (gdb)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/1934505/+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 1934505]

[Simark]

(In reply to Matthias Klose from comment #4)
> for a s390x setup, maybe see
> https://developer.ibm.com/components/ibm-linuxone/gettingstarted/

Thanks, that works wonderfully.  I tested on a RHEL 8.3 machine, I was
able to reproduce the issue, and the patch fixes it for me there also.
So, can I ask you first to double check that you built and tested the
right thing?  If it still fails, I'll need you to do a bit of assisted
debugging, because I don't know what the problem would be.

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

Title:
  gdb 11 doesn't work on impish/s390x: internal-error:
  displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*,
  thread_info*, CORE_ADDR&): Assertion
  `gdbarch_data->num_disp_step_buffers > 0' failed.

Status in gdb:
  Confirmed
Status in gdb package in Ubuntu:
  Fix Released

Bug description:
  gdb doesn't work on impish/s390x at the minute. Even if you say 'no'
  to both questions you still can't debug:

  ubuntu@laney-bos01-s390x-2:~/glib-networking-2.66.0/build$ gdb ls
  GNU gdb (Ubuntu 11.0.50.20210630-0ubuntu1) 11.0.50.20210630-git
  Copyright (C) 2021 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.
  Type "show copying" and "show warranty" for details.
  This GDB was configured as "s390x-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .

  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from ls...
  (No debugging symbols found in ls)
  (gdb) run
  Starting program: /usr/bin/ls
  /build/gdb-Ti35un/gdb-11.0.50.20210630/gdb/linux-tdep.c:2550: internal-error: 
displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, 
thread_info*, CORE_ADDR&): Assertion `gdbarch_data->num_disp_step_buffers > 0' 
failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Quit this debugging session? (y or n) n

  This is a bug, please report it.  For instructions, see:
  .

  /build/gdb-Ti35un/gdb-11.0.50.20210630/gdb/linux-tdep.c:2550: internal-error: 
displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, 
thread_info*, CORE_ADDR&): Assertion `gdbarch_data->num_disp_step_buffers > 0' 
failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Create a core file of GDB? (y or n) n
  Command aborted.
  (gdb)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/1934505/+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 1791958] Re: iptables-restore is missing -w option

[Andreas Hasenack]

Excellent progress Eric, thanks!

I'll give it a try.

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

Title:
  iptables-restore is missing -w option

Status in iptables package in Ubuntu:
  Confirmed

Bug description:
  For CRIU we need to have iptables version 1.6.2 which includes the
  '-w' option in iptables-restore.

  This is a request to update iptables to 1.6.2 in 18.10 and if possible
  backport the necessary changes to 18.04.

  The CRIU project gets right now many bug reports (mostly in the
  combination LXD + CRIU) due to the missing '-w' option in iptables-
  restore. Especially as 18.04 will be around for some time it would be
  good to have iptables-restore available with '-w'.

  This is one example bug report: https://github.com/checkpoint-
  restore/criu/issues/551

  But not only CRIU would benefit from this change. It seems also
  problematic with Kubernetes:
  https://github.com/kubernetes/kubernetes/pull/60978

  So if possible, please update iptables to 1.6.2 (or backport changes)
  to support -w in iptables-restore.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iptables/+bug/1791958/+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 1934888] [NEW] Resuming from sleep garbles display configuration

[Bruno Hivert]

Public bug reported:

Hello,

I'm using a thinkpad as a workstation, with a dual-display configuration: the 
laptop screen and a big external screen.
The screen is directly connected to the laptop hdmi port, because using it 
through the thunderbolt port is hit-and-miss, but this is another story.

When I wake my system on after a night sleep, more often than not - it's
not systematic -, my primary screen - the bigger external Dell monitor -
is activated alone, and the laptop screen stays completely black.

I have to go to system settings -> Display to activate it again.

thanks for your support

/Bruno Hivert

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.10.0-1033.34-oem 5.10.41
Uname: Linux 5.10.0-1033-oem x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  460.80  Fri May  7 06:55:54 
UTC 2021
 GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: KDE
Date: Wed Jul  7 07:48:20 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 acpi-call, 1.1.0, 5.10.0-1034-oem, x86_64: installed
 nvidia, 460.80, 5.10.0-1033-oem, x86_64: installed
 nvidia, 460.80, 5.10.0-1034-oem, x86_64: installed
 nvidia, 460.80, 5.8.0-59-generic, x86_64: installed
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation UHD Graphics [8086:9bc4] (rev 05) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo Device [17aa:22c0]
 NVIDIA Corporation Device [10de:1f95] (rev a1) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Device [17aa:22c0]
InstallationDate: Installed on 2021-05-21 (46 days ago)
InstallationMedia: Kubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
MachineType: LENOVO 20TK001JUS
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.10.0-1033-oem 
root=/dev/mapper/vgkubuntu-root ro
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/15/2021
dmi.bios.release: 1.15
dmi.bios.vendor: LENOVO
dmi.bios.version: N2VET30W (1.15 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20TK001JUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0T08861 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.8
dmi.modalias: 
dmi:bvnLENOVO:bvrN2VET30W(1.15):bd04/15/2021:br1.15:efr1.8:svnLENOVO:pn20TK001JUS:pvrThinkPadX1ExtremeGen3:rvnLENOVO:rn20TK001JUS:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X1 Extreme Gen 3
dmi.product.name: 20TK001JUS
dmi.product.sku: LENOVO_MT_20TK_BU_Think_FM_ThinkPad X1 Extreme Gen 3
dmi.product.version: ThinkPad X1 Extreme Gen 3
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.2
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+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu

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

Title:
  Resuming from sleep garbles display configuration

Status in xorg package in Ubuntu:
  New

Bug description:
  Hello,

  I'm using a thinkpad as a workstation, with a dual-display configuration: the 
laptop screen and a big external screen.
  The screen is directly connected to the laptop hdmi port, because using it 
through the thunderbolt port is hit-and-miss, but this is another story.

  When I wake my system on after a night sleep, more often than not -
  it's not systematic -, my primary screen - the bigger external Dell
  monitor - is activated alone, and the laptop screen stays completely
  black.

  I have to go to system settings -> Display to activate it again.

  thanks for your support

  /Bruno Hivert

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04

Re: [Touch-packages] [Bug 1934505] Re: gdb 11 doesn't work on impish/s390x: internal-error: displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, thread_info*, CORE_ADDR&): Assertion `g

[Iain Lane]

On Wed, Jul 07, 2021 at 08:30:32AM -, Matthias Klose wrote:
> fixed in 11.0.90.20210705-0ubuntu2

yep, thanks for reproducing and forwarding!

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]

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

Title:
  gdb 11 doesn't work on impish/s390x: internal-error:
  displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*,
  thread_info*, CORE_ADDR&): Assertion
  `gdbarch_data->num_disp_step_buffers > 0' failed.

Status in gdb:
  Confirmed
Status in gdb package in Ubuntu:
  Fix Released

Bug description:
  gdb doesn't work on impish/s390x at the minute. Even if you say 'no'
  to both questions you still can't debug:

  ubuntu@laney-bos01-s390x-2:~/glib-networking-2.66.0/build$ gdb ls
  GNU gdb (Ubuntu 11.0.50.20210630-0ubuntu1) 11.0.50.20210630-git
  Copyright (C) 2021 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.
  Type "show copying" and "show warranty" for details.
  This GDB was configured as "s390x-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .

  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from ls...
  (No debugging symbols found in ls)
  (gdb) run
  Starting program: /usr/bin/ls
  /build/gdb-Ti35un/gdb-11.0.50.20210630/gdb/linux-tdep.c:2550: internal-error: 
displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, 
thread_info*, CORE_ADDR&): Assertion `gdbarch_data->num_disp_step_buffers > 0' 
failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Quit this debugging session? (y or n) n

  This is a bug, please report it.  For instructions, see:
  .

  /build/gdb-Ti35un/gdb-11.0.50.20210630/gdb/linux-tdep.c:2550: internal-error: 
displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, 
thread_info*, CORE_ADDR&): Assertion `gdbarch_data->num_disp_step_buffers > 0' 
failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Create a core file of GDB? (y or n) n
  Command aborted.
  (gdb)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/1934505/+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 1934505] Re: gdb 11 doesn't work on impish/s390x: internal-error: displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, thread_info*, CORE_ADDR&): Assertion `gdbar

[Matthias Klose]

fixed in 11.0.90.20210705-0ubuntu2

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

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

Title:
  gdb 11 doesn't work on impish/s390x: internal-error:
  displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*,
  thread_info*, CORE_ADDR&): Assertion
  `gdbarch_data->num_disp_step_buffers > 0' failed.

Status in gdb:
  Confirmed
Status in gdb package in Ubuntu:
  Fix Released

Bug description:
  gdb doesn't work on impish/s390x at the minute. Even if you say 'no'
  to both questions you still can't debug:

  ubuntu@laney-bos01-s390x-2:~/glib-networking-2.66.0/build$ gdb ls
  GNU gdb (Ubuntu 11.0.50.20210630-0ubuntu1) 11.0.50.20210630-git
  Copyright (C) 2021 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.
  Type "show copying" and "show warranty" for details.
  This GDB was configured as "s390x-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .

  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from ls...
  (No debugging symbols found in ls)
  (gdb) run
  Starting program: /usr/bin/ls
  /build/gdb-Ti35un/gdb-11.0.50.20210630/gdb/linux-tdep.c:2550: internal-error: 
displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, 
thread_info*, CORE_ADDR&): Assertion `gdbarch_data->num_disp_step_buffers > 0' 
failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Quit this debugging session? (y or n) n

  This is a bug, please report it.  For instructions, see:
  .

  /build/gdb-Ti35un/gdb-11.0.50.20210630/gdb/linux-tdep.c:2550: internal-error: 
displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, 
thread_info*, CORE_ADDR&): Assertion `gdbarch_data->num_disp_step_buffers > 0' 
failed.
  A problem internal to GDB has been detected,
  further debugging may prove unreliable.
  Create a core file of GDB? (y or n) n
  Command aborted.
  (gdb)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdb/+bug/1934505/+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 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.

[Jerry Lee]

Attach the Debdiff file for Hirsute (21.04)

** Patch added: "modemmanager_1.16.6-2~21.04-hirsute.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1934286/+attachment/5509579/+files/modemmanager_1.16.6-2~21.04-hirsute.debdiff

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

Title:
  Update the ModemManager to 1.16.6-2 to support some modems in Focal
  and Hirsute releases.

Status in OEM Priority Project:
  Confirmed
Status in modemmanager package in Ubuntu:
  New

Bug description:
  [Impact]

  Some IOT products use wireless modems which can be working only when
  recent versions of the ModemManager suite are used.

  The following 2 modems need the ModemManager suite to be upgraded:
  * Foxconn SDX55 T99W175 5G sub6 PCIE Modem
  * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem 
   
  The main fix requested is to add the FCC unlock mechanism for Foxconn modems.
  * FCC unlock operation for Foxconn modems
  
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/534/commits
  * dms: new 'Foxconn Set FCC authentication' command
  
https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/merge_requests/254/commits

  The minimum versions of the ModemManager suite required to enable the support 
for the above 2 mentioned modems have been verified: (LP: #1928665)
  * ModemManager: 1.16.6
  * libmbim: 1.24.6
  * libqmi : 1.28.6

  The ModemManager suite in the Impish release meets the requirements.

  [Test Plan]

  = How to Reproduce the Bug =

  Execute the following commands to list the modems detected by
  ModemManager in Hirsute and Focal releases:

  $ mmcli --list-modems
  No modems were found

  
  = Test Procedure =

  1. Install the Ubuntu system on the tested hardware

The following images will be used to verify the version of the ModemManager 
suite: 
* Impish: 
https://cdimage.ubuntu.com/daily-live/current/impish-desktop-amd64.iso
* Hirsute: https://releases.ubuntu.com/21.04/ubuntu-21.04-desktop-amd64.iso
* Focal: 
https://releases.ubuntu.com/focal/ubuntu-20.04.2.0-desktop-amd64.iso

  2. Upgrade the kernel and driver  ( for Foxconn and Quectel modem )

The kernel needs to get some patches from 5.13 and includes a back ported 
Quectel driver to support these 2 modems.
We have prepared a kernel packages for testing: 
https://people.canonical.com/~mschiu77/lp1928665/v2/

  3. Install the ModemManager suite ( for Hirsute and Focal releases )

The ModemManager suite will be installed from Impish:

  $ sudo apt update
  $ sudo apt install modemmanager/impish
  $ sudo apt install libqmi-utils/impish

  
  4. Execute the following commands

  4.1 Get the run-time environment

  $ uname -ar
  $ lsb_release -a
  $ mmcli -V
  $ qmicli -V

  4.2 Check the status of the ModemManager service

  $ sudo systemctl status ModemManager.service

  
  4.3 List the detected modems

  $ mmcli --list-modems

  
  4.4 Check the modem’s status

  $ mmcli --modem 0

  
  4.5 Install and execute Lenovo’s FCC unlock app ( for Quectel modem only )

  $ sudo snap install --devmode --dangerous dpr-wwan_1.0-wwan-
  test_amd64.snap

  
  4.6 Enable the detected modem

  $ sudo mmcli --modem 0 --enable

  
  4.7 Check the modem’s status

  $ mmcli --modem 0

  = Analyze the Tested Result =

  1. Check if installed packages are working

The result of test procedure 4.1 and 4.2 can be used to make sure the 
installed packages are working.
If the Modemmanager.service is active(running), the packages are working.

  2. Check if the supported modem can be detected

The result of test procedure 4.3 can be used to see if the modem can be 
detected by ModemManager or not.
The supported modems should be listed.

  3. Check if the modem can be enabled

If the modem can be enabled, the state of the modem in the test
  procedure 4.7 will be set to be registered.

  
  [Where problems could occur]

  There is a risk that modems supported in the old versions of
  ModemManager suite may not be supported in the newer versions.

  
  [Other Info]
   
  We need to upgrade to these 3 packages at the same time:
  * ModemManager: 1.16.6
  * libmbim: 1.24.6
  * libqmi : 1.28.6

  To support the mentioned 2 modems, the system needs to use kernels which 
include specific patches and  kernel config options .
  For ex., there is a patched 5.11 kernel which is working for: 
https://bugs.launchpad.net/austin/+bug/1928665/comments/7

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1934286/+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 1934286] Re: Update the ModemManager to 1.16.6-2 to support some modems in Focal and Hirsute releases.

[Jerry Lee]

The debian package modemmanager 1.16.6-2 can be found in the link:
https://launchpad.net/ubuntu/impish/+package/modemmanager

Attach the Debdiff file for Focal(20.04)

** Patch removed: "modemmanager_1-1.16.6-2-hirsute.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1934286/+attachment/5508440/+files/modemmanager_1-1.16.6-2-hirsute.debdiff

** Patch removed: "modemmanager_1-1.16.6-2-focal.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1934286/+attachment/5508441/+files/modemmanager_1-1.16.6-2-focal.debdiff

** Patch added: "modemmanager_1.16.6-2~20.04.2-focal.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1934286/+attachment/5509578/+files/modemmanager_1.16.6-2~20.04.2-focal.debdiff

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

Title:
  Update the ModemManager to 1.16.6-2 to support some modems in Focal
  and Hirsute releases.

Status in OEM Priority Project:
  Confirmed
Status in modemmanager package in Ubuntu:
  New

Bug description:
  [Impact]

  Some IOT products use wireless modems which can be working only when
  recent versions of the ModemManager suite are used.

  The following 2 modems need the ModemManager suite to be upgraded:
  * Foxconn SDX55 T99W175 5G sub6 PCIE Modem
  * Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem 
   
  The main fix requested is to add the FCC unlock mechanism for Foxconn modems.
  * FCC unlock operation for Foxconn modems
  
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/merge_requests/534/commits
  * dms: new 'Foxconn Set FCC authentication' command
  
https://gitlab.freedesktop.org/mobile-broadband/libqmi/-/merge_requests/254/commits

  The minimum versions of the ModemManager suite required to enable the support 
for the above 2 mentioned modems have been verified: (LP: #1928665)
  * ModemManager: 1.16.6
  * libmbim: 1.24.6
  * libqmi : 1.28.6

  The ModemManager suite in the Impish release meets the requirements.

  [Test Plan]

  = How to Reproduce the Bug =

  Execute the following commands to list the modems detected by
  ModemManager in Hirsute and Focal releases:

  $ mmcli --list-modems
  No modems were found

  
  = Test Procedure =

  1. Install the Ubuntu system on the tested hardware

The following images will be used to verify the version of the ModemManager 
suite: 
* Impish: 
https://cdimage.ubuntu.com/daily-live/current/impish-desktop-amd64.iso
* Hirsute: https://releases.ubuntu.com/21.04/ubuntu-21.04-desktop-amd64.iso
* Focal: 
https://releases.ubuntu.com/focal/ubuntu-20.04.2.0-desktop-amd64.iso

  2. Upgrade the kernel and driver  ( for Foxconn and Quectel modem )

The kernel needs to get some patches from 5.13 and includes a back ported 
Quectel driver to support these 2 modems.
We have prepared a kernel packages for testing: 
https://people.canonical.com/~mschiu77/lp1928665/v2/

  3. Install the ModemManager suite ( for Hirsute and Focal releases )

The ModemManager suite will be installed from Impish:

  $ sudo apt update
  $ sudo apt install modemmanager/impish
  $ sudo apt install libqmi-utils/impish

  
  4. Execute the following commands

  4.1 Get the run-time environment

  $ uname -ar
  $ lsb_release -a
  $ mmcli -V
  $ qmicli -V

  4.2 Check the status of the ModemManager service

  $ sudo systemctl status ModemManager.service

  
  4.3 List the detected modems

  $ mmcli --list-modems

  
  4.4 Check the modem’s status

  $ mmcli --modem 0

  
  4.5 Install and execute Lenovo’s FCC unlock app ( for Quectel modem only )

  $ sudo snap install --devmode --dangerous dpr-wwan_1.0-wwan-
  test_amd64.snap

  
  4.6 Enable the detected modem

  $ sudo mmcli --modem 0 --enable

  
  4.7 Check the modem’s status

  $ mmcli --modem 0

  = Analyze the Tested Result =

  1. Check if installed packages are working

The result of test procedure 4.1 and 4.2 can be used to make sure the 
installed packages are working.
If the Modemmanager.service is active(running), the packages are working.

  2. Check if the supported modem can be detected

The result of test procedure 4.3 can be used to see if the modem can be 
detected by ModemManager or not.
The supported modems should be listed.

  3. Check if the modem can be enabled

If the modem can be enabled, the state of the modem in the test
  procedure 4.7 will be set to be registered.

  
  [Where problems could occur]

  There is a risk that modems supported in the old versions of
  ModemManager suite may not be supported in the newer versions.

  
  [Other Info]
   
  We need to upgrade to these 3 packages at the same time:
  * ModemManager: 1.16.6
  * libmbim: 1.24.6
  * libqmi : 1.28.6

  To support the mentioned 2 modems, the system needs to use kernels which 
include specific patches and  kernel config options .
  For ex.,

Re: [Touch-packages] [Bug 1918458] Re: [Swift SF515-51T, Realtek ALC256, Grey Speaker, Internal] Playback problem, no sound from speakers, headphones ok

[Thibaut Soubrié]

Hello Hui Wang,

Thanks for trying to solve the issue !
I just ran all these commands (without any shutdown, I assumed it was not
needed), none solved the speaker problem.

Best Regards,

Thibaut Soubrié

Le mer. 7 juil. 2021 à 04:05, Hui Wang <1918...@bugs.launchpad.net> a
écrit :

> @Thibaut,
>
> Doesn't matter, Alex already. provided the log.
>
> Please run below commands and test speaker. If those commands don't
> work, I will contact realtek (I guess the spk amplifier is an i2s one,
> need special initialization).
>
>
> sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x10
> sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x0f20
> //please test if speaker works.
>
> sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x1b
> sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x0e4b
> //please test if speaker works.
>
> sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x33
> sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x8c00
> //please test if speaker works.
>
> sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x35
> sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x8d6a
> //please test if speaker works.
>
> sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x36
> sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x5737
> //please test if speaker works.
>
> sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x37
> sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0xfe16
> //please test if speaker works.
>
> sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x38
> sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0x7981
> //please test if speaker works.
>
> sudo hda-verb /dev/snd/hwC0D0 0x20 SET_COEF_INDEX 0x45
> sudo hda-verb /dev/snd/hwC0D0 0x20 SET_PROC_COEF 0xd089
> //please test if speaker works.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1918458
>
> Title:
>   [Swift SF515-51T, Realtek ALC256, Grey Speaker, Internal] Playback
>   problem, no sound from speakers, headphones ok
>
> Status in alsa-driver package in Ubuntu:
>   Confirmed
>
> Bug description:
>   Expect : sound from speaker
>   Instead, obtain : no sound.
>
>
>   Tried various configuration of /etc/modprobe.d/alsa-conf with :
>
>   options snd-hda-intel model= and
>   options snd-intel-dspcfg dsp_driver=3 or 1
>   and systematic reboot.
>
>   Either I get dummy output, or I get proper output detection, alsamixer
>   and pavucontrol seems 100% ok, but no sound comes from the speakers.
>
>   I'm under a dualboot with Windows 10, BIOS fast boot disabled.
>   Ubuntu 20.04.2 LTS
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 20.04
>   Package: alsa-base 1.0.25+dfsg-0ubuntu5
>   ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
>   Uname: Linux 5.8.0-44-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu27.16
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC0:  thibauts   1522 F pulseaudio
>/dev/snd/pcmC0D0p:   thibauts   1522 F...m pulseaudio
>   CasperMD5CheckResult: skip
>   CurrentDesktop: ubuntu:GNOME
>   Date: Wed Mar 10 18:10:30 2021
>   InstallationDate: Installed on 2021-03-09 (1 days ago)
>   InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64
> (20210209.1)
>   PackageArchitecture: all
>   SourcePackage: alsa-driver
>   Symptom: audio
>   Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp
> failed
>   Symptom_Card: Cannon Point-LP High Definition Audio Controller -
> sof-hda-dsp
>   Symptom_Jack: Grey Speaker, Internal
>   Symptom_Type: Only some of outputs are working
>   Title: [Swift SF515-51T, Realtek ALC256, Grey Speaker, Internal]
> Playback problem
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 05/24/2019
>   dmi.bios.release: 1.4
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: V1.04
>   dmi.board.asset.tag: Default string
>   dmi.board.name: Guinness_WL
>   dmi.board.vendor: WL
>   dmi.board.version: V1.04
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: Acer
>   dmi.chassis.version: V1.04
>   dmi.ec.firmware.release: 1.6
>   dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvrV1.04:bd05/24/2019:br1.4:efr1.6:svnAcer:pnSwiftSF515-51T:pvrV1.04:rvnWL:rnGuinness_WL:rvrV1.04:cvnAcer:ct10:cvrV1.04:
>   dmi.product.family: Swift 5
>   dmi.product.name: Swift SF515-51T
>   dmi.product.sku: 
>   dmi.product.version: V1.04
>   dmi.sys.vendor: Acer
>   mtime.conffile..etc.modprobe.d.alsa-base.conf: 2021-03-10T18:04:19.277254
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1918458/+subscriptions
>

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

Title:
  [Swift SF515-51T, Realtek ALC256, Grey Speaker, Internal] Playback
  problem, no sound from speakers, headphones ok