date:20210624

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

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

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

Title:
  package linux-image-4.18.0-22-generic 4.18.0-22.23 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  I don't know much

  ProblemType: Package
  DistroRelease: Ubuntu 18.10
  Package: linux-image-4.18.0-22-generic 4.18.0-22.23
  ProcVersionSignature: Ubuntu 4.18.0-21.22-generic 4.18.20
  Uname: Linux 4.18.0-21-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mohitatray   3547 F pulseaudio
  Date: Fri Jun 21 22:20:32 2019
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=d502fd8e-070b-480b-99fe-9ab51216f6b2
  InstallationDate: Installed on 2018-08-16 (309 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 1bcf:2c9b Sunplus Innovation Technology Inc. 
   Bus 001 Device 002: ID 8087:0aa7 Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Laptop 15g-br0xx
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-21-generic 
root=UUID=0dc8b444-0cea-4736-8ec3-6fb7b8a78437 ro 
resume=UUID=d502fd8e-070b-480b-99fe-9ab51216f6b2 quiet splash 
resume=UUID=d502fd8e-070b-480b-99fe-9ab51216f6b2 vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal, 
3.6.7-1~18.10
  PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.15-3
  RelatedPackageVersions: grub-pc 2.02+dfsg1-5ubuntu8.3
  SourcePackage: initramfs-tools
  Title: package linux-image-4.18.0-22-generic 4.18.0-22.23 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.21
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 832B
  dmi.board.vendor: HP
  dmi.board.version: 23.37
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.21:bd07/04/2017:svnHP:pnHPLaptop15g-br0xx:pvrType1ProductConfigId:rvnHP:rn832B:rvr23.37:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 15g-br0xx
  dmi.product.sku: 2JR17PA#ACJ
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1833742/+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 1933078] Re: BlueZ 5.59 release

2021-06-24 Thread Sebastien Bacher

uploaded, thanks Daniel

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

Title:
  BlueZ 5.59 release

Status in bluez package in Ubuntu:
  Fix Committed

Bug description:
  Release BlueZ 5.59 to impish.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1933078/+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 1931874] Re: Failure to download packages with epochs (Regression from 2.1.15)

verified by autopkgtests

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

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

Title:
  Failure to download packages with epochs (Regression from 2.1.15)

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

Bug description:
  [Impact]
  Packages where the epoch is encoded in the filename cannot be retrieved, as 
we overlooked some places when changing the acquire system to always use % 
encoded URLs.

  [Test plan]
  A test is included in the comprehensive test suite.

  [Where problems could occur]
  Regressions could occur in places that download debs with filenames that need 
quoting or are already quoted. You can argue this also changes the API 
slightly, since ArchiveURI() now returns encoded URLs, rather than just 
appending the file path to the host. Although, this could actually improve 
things too.

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

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

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

We do not have any updates phasing in hirsute atm, so will have to hack
in one :)

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

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

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

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

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

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

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

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

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

  [Original bug report]

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1898026] Re: interruption of dist-upgrade can leave you next release in sources.list

focal/2.0.6: The standalone test certainly worked, and the keyboard
interrupts were delivered to do-release-upgrade

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

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

Title:
  interruption of dist-upgrade can leave you next release in
  sources.list

Status in apt package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in apt source package in Bionic:
  Fix Committed
Status in ubuntu-release-upgrader source package in Bionic:
  New
Status in apt source package in Focal:
  Fix Committed
Status in ubuntu-release-upgrader source package in Focal:
  Fix Released
Status in apt source package in Groovy:
  Fix Released
Status in ubuntu-release-upgrader source package in Groovy:
  Fix Released
Status in apt source package in Hirsute:
  Fix Released
Status in ubuntu-release-upgrader source package in Hirsute:
  Fix Released

Bug description:
  [Impact]
  Calling update() or installing packages from apt clients resets their SIGINT 
and SIGQUIT handlers to SIG_DFL, overriding any signal handlers they might have 
set for them.

  In case of ubuntu-release-upgrader, this results in the release
  upgrader being unable to handle interrupts after it did the initial
  update - the default libc handler will run and the program exits.

  [Test plan]

  [[apt]]
  As a standalone test for apt, we can test the following script:

  import apt
  import time

  apt.Cache().update()
  print("WAITING")
  try:
  time.sleep(1)
  except BaseException as e:
  print("Seen", repr(e))
  print("END")

  Pressing Ctrl+C while WAITING is printed should print Seen
  KeyboardInterrupt, and importantly, also the END line.

  [[ubuntu-release-upgrader]]
  1) On an Ubuntu 18.04 system run do-release-upgrade in a terminal.
  2) At the "Do you want to start the upgrade?" question say Y.
  3) When you see the "Lock screen disabled" message you will also see 
"Inhibiting until Ctrl+C is pressed".
  4) Press "Ctrl+C"

  Your /etc/apt/sources.list file will now have focal in it instead of
  bionic although the upgrade has quit. With the version of ubuntu-
  release-upgrader in -proposed you will not see the "Ctrl+C" message.
  For your sources.list file to be restored you'll need the version of
  apt from bionic-proposed installed before starting the upgrade.

  [Where problems could occur]
  apt: This specific change removes the two lines that SIG_DFL the signal 
handlers after running scripts. AFAWCT those lines are unnecessary - the code 
that calls it temporarily sets the handlers to SIG_IGN but restores previous 
handlers at the end; it was wrongly refactored decades ago. A regression could 
occur in that those signals will now continue to be ignored if we missed a spot.

  ubuntu-release-upgrader: The change is wrapping a bunch of code in a
  try: except: block so if the indentation was off the pyflakes /
  pycodestyle tests would fail but autopkgtest will catch that.

  [Original bug report]
  As a long-time-user of ?ubuntu, with apt-get as tool of choice for 
updates/upgrades I wrote a daily script for updates, with 'dist-upgrade'.
  In all earlier years, it wouldn't actually do an upgrade of a ?ubuntu 
version; just all packages including new ones. Version updates had to be 
initiated manually, and I was always asked if I really wanted the new ?ubuntu 
version. Sounds appropriate.

  Last night when it (dist-upgrade), it just gave me 20.04. No questions asked. 
I for one consider this kind of intrusive, though.
  It *might* have to make with me trying 'sudo do-release-upgrade -m desktop' a 
number of times earlier; just to *check* if the upgrade was on offer; but this 
is only a guess.

  In *any* case, a pop-up asking "Are you sure? Are you connected
  through an adequate pipe? Are you sitting with full batteries; better
  a power supply?" would be convenient; since I am using my PC for
  urgent duties, and didn't want to fiddle with unexpected upgrade bugs.

  ProblemType: BugDistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.25
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Thu Oct  1 11:48:39 2020
  InstallationDate: Installed on 2019-03-14 (566 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: allSourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to focal on 2020-09-29 (1 days ago)
  VarLogDistupgradeAptlog:
   Log time: 2020-09-29 19:44:28.696289
   Log time: 2020-09-29 19:44:33.573481

To manage notifications about this bug go to:
https://bugs.lau

[Touch-packages] [Bug 1898026] Re: interruption of dist-upgrade can leave you next release in sources.list

bionic, 1.6.14 is good too.

root@b:~# python3 a.py
WAITING
^C
root@b:~# apt install libapt-pkg5.0
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following package was automatically installed and is no longer required:
  libfreetype6
Use 'apt autoremove' to remove it.
The following additional packages will be installed:
  apt apt-utils
Suggested packages:
  apt-doc aptitude | synaptic | wajig dpkg-dev
The following packages will be upgraded:
  apt apt-utils libapt-pkg5.0
3 upgraded, 0 newly installed, 0 to remove and 29 not upgraded.
Need to get 2224 kB of archives.
After this operation, 16.4 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 libapt-pkg5.0 
amd64 1.6.14 [809 kB]
Get:2 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 apt amd64 
1.6.14 [1207 kB]
Get:3 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 apt-utils 
amd64 1.6.14 [209 kB]
Fetched 2224 kB in 0s (7775 kB/s) 
(Reading database ... 28937 files and directories currently installed.)
Preparing to unpack .../libapt-pkg5.0_1.6.14_amd64.deb ...
Unpacking libapt-pkg5.0:amd64 (1.6.14) over (1.6.13) ...
Setting up libapt-pkg5.0:amd64 (1.6.14) ...
(Reading database ... 28937 files and directories currently installed.)
Preparing to unpack .../archives/apt_1.6.14_amd64.deb ...
Unpacking apt (1.6.14) over (1.6.13) ...
Setting up apt (1.6.14) ...
(Reading database ... 28937 files and directories currently installed.)
Preparing to unpack .../apt-utils_1.6.14_amd64.deb ...
Unpacking apt-utils (1.6.14) over (1.6.13) ...
Setting up apt-utils (1.6.14) ...
Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
Processing triggers for libc-bin (2.27-3ubuntu1.4) ...
root@b:~# python3 a.py
WAITING
^CSeen KeyboardInterrupt()
END

do-release-upgrade was fine too:
Upgrading
Fetched 0 B in 0s (0 B/s)   


   

Restoring original system state


Note that if you Ctrl+C while it's downloading the upgrades, it gets the 
keyboardinterrupt in the wrong spot - inside the progress handler and does not 
restore the correct state, probably should be a different bug, though.

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

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

Title:
  interruption of dist-upgrade can leave you next release in
  sources.list

Status in apt package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in apt source package in Bionic:
  Fix Committed
Status in ubuntu-release-upgrader source package in Bionic:
  New
Status in apt source package in Focal:
  Fix Committed
Status in ubuntu-release-upgrader source package in Focal:
  Fix Released
Status in apt source package in Groovy:
  Fix Released
Status in ubuntu-release-upgrader source package in Groovy:
  Fix Released
Status in apt source package in Hirsute:
  Fix Released
Status in ubuntu-release-upgrader source package in Hirsute:
  Fix Released

Bug description:
  [Impact]
  Calling update() or installing packages from apt clients resets their SIGINT 
and SIGQUIT handlers to SIG_DFL, overriding any signal handlers they might have 
set for them.

  In case of ubuntu-release-upgrader, this results in the release
  upgrader being unable to handle interrupts after it did the initial
  update - the default libc handler will run and the program exits.

  [Test plan]

  [[apt]]
  As a standalone test for apt, we can test the following script:

  import apt
  import time

  apt.Cache().update()
  print("WAITING")
  try:
  time.sleep(1)
  except BaseException as e:
  print("Seen", repr(e))
  print("END")

  Pressing Ctrl+C while WAITING is printed should print Seen
  KeyboardInterrupt, and importantly, also the END line.

  [[ubuntu-release-upgrader]]
  1) On an Ubuntu 18.04 system run do-release-upgrade in a terminal.
  2) At the "Do you want to start the upgrade?" question say Y.
  3) When you see the "Lock screen disabled" message you will also see 
"Inhibiting until Ctrl+C is pressed".
  4) Press "Ctrl+C"

  Your /etc/apt/sources.list file will now have focal in it instead of
  bionic although the upgrade has quit. With the version of ubuntu-
  release-upgrader in -proposed you will not see the "Ctrl+C" message.
  For your sources.list file to be restored you'll need the version of
  apt from bionic-proposed installed before starting the upgrade.

  [Where problems could occur]
  apt: This specific change removes the two lines that SI

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

Verification done.

First I downgraded all systemd packages to the release pocket using

# apt install '?installed?version(247.3-3ubuntu3.1$)=247.3-3ubuntu3'

Then I hacked in Phased-Update-Percentage: 0 fields for all src:systemd
packages in my local hirsute-updates Packages file in /var/lib/apt/lists
using vim, resulting in

# apt install libsystemd-dev
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 libsystemd-dev : Depends: libsystemd0 (= 247.3-3ubuntu3.1) but 247.3-3ubuntu3 
is to be installed
E: Unable to correct problems, you have held broken packages.

I upgraded libapt-pkg6.0 to 2.2.4ubuntu0.1, yielding

root@h:~# apt install libsystemd-dev
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following package was automatically installed and is no longer required:
  libfreetype6
Use 'apt autoremove' to remove it.
The following NEW packages will be installed:
  libsystemd-dev
0 upgraded, 1 newly installed, 0 to remove and 1 not upgraded.
Need to get 299 kB of archives.
After this operation, 1153 kB of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu hirsute/main amd64 libsystemd-dev amd64 
247.3-3ubuntu3 [299 kB]
Fetched 299 kB in 0s (2408 kB/s)  
Selecting previously unselected package libsystemd-dev:amd64.
(Reading database ... 32918 files and directories currently installed.)
Preparing to unpack .../libsystemd-dev_247.3-3ubuntu3_amd64.deb ...
Unpacking libsystemd-dev:amd64 (247.3-3ubuntu3) ...
Setting up libsystemd-dev:amd64 (247.3-3ubuntu3) ...
Processing triggers for man-db (2.9.4-2) ...
Scanning processes...   



Scanning candidates...  




Yay!

Phasing back to 100 made it upgrade to -updates as expected:

root@h:~# sed -i "s#Phased-Update-Percentage: 0#Phased-Update-Percentage: 
100#g" 
/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_hirsute-updates_main_binary-amd64_Packages
root@h:~# apt install libsystemd-dev
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following package was automatically installed and is no longer required:
  libfreetype6
Use 'apt autoremove' to remove it.
The following additional packages will be installed:
  libnss-systemd libpam-systemd libsystemd0 systemd systemd-sysv 
systemd-timesyncd
Suggested packages:
  systemd-container
The following NEW packages will be installed:
  libsystemd-dev
The following packages will be upgraded:
  libnss-systemd libpam-systemd libsystemd0 systemd systemd-sysv 
systemd-timesyncd
6 upgraded, 1 newly installed, 0 to remove and 2 not upgraded.
Need to get 5217 kB of archives.
After this operation, 1159 kB of additional disk space will be used.
Do you want to continue? [Y/n] 


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

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

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

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

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

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

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

[Touch-packages] [Bug 1933221] Re: Blutooth on/off does not work properly from gnome-control-center

See bug 1926062 for previous SRU review.

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

Title:
  Blutooth on/off does not work properly from gnome-control-center

Status in OEM Priority Project:
  New
Status in bluez package in Ubuntu:
  Fix Committed

Bug description:
  [Impact]

   * On/off of Bluetooth in gnome-control-center will not work properly.

   * Devices are not refreshed in the list anymore.

   * The passed struct will depend on the length of the submitted read() and the
 kernel version.

  [Test Plan]

   * Open gnome-control-center and select Bluetooth
 
   * turn off Bluetooth via UI
 
   * turn on Bluetooth via UI

  [Where problems could occur]

   * If user install newer kernel such as 5.13, they may have this
  issue.

   * Tested on Intel AX201 and Intel 6235 with kernel version
  5.13.0-1003-oem.

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1933221/+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 1933491] [NEW] kmod add zstd support

2021-06-24 Thread Dimitri John Ledkov

Public bug reported:

kmod add zstd support

* v27+ needs patches cherrypicked from v28

* v28+ needs new build-time deps adjusted

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

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

Title:
  kmod add zstd support

Status in kmod package in Ubuntu:
  New

Bug description:
  kmod add zstd support

  * v27+ needs patches cherrypicked from v28

  * v28+ needs new build-time deps adjusted

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

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

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

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

I'm not sure what you mean by "upstream tributary", but if the fix
exists in the main Ubuntu packaging branch used by the desktop team (ie.
Vcs-Git in debian/control points to it) then that makes sense, as it was
in this case. If you mean it's just fixed upstream somewhere, then that
doesn't make sense - Launchpad's bug tracker expects to have a separate
task to track upstream status if you want that.

However, from an SRU perspective, I would expect an upload to the
development release *before* an SRU is uploaded. Sometimes we make
concessions (eg. during a development release freeze), but I don't think
a sponsorship delay qualifies. The sponsor should be able to sponsor to
the development release first, so there's no reason not to do it.

I see it's there now, but please could you adjust your processes to make
sure that in the normal case, this happens? This would save me reviewing
the SRU twice.

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

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

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

Bug description:
  [Impact]

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

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

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

  [Where problems could occur]

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

  [Other info]

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

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

  [Original bug report]

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

    Bluetooth: hci0: HCI reset during shutdown failed

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

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to

[Touch-packages] [Bug 1933452] [NEW] secondary portrait monitor is not portrait during boot

You have been subscribed to a public bug:

I'm using Ubuntu 20.04 in my laptop. with that i'm using a secondary
monitor which is portrait. these 2 works fine but in the boot menu,
secondary monitor's screen is wrong. it's not portrait. please fix this
issue.

Thank you.
Regards,
Shehan

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
Uname: Linux 5.4.0-54-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:04:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.138  Thu May 14 01:01:53 
PDT 2020
 GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
ApportVersion: 2.20.11-0ubuntu27.12
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Jun 24 15:49:32 2021
DistUpgraded: 2020-10-11 07:43:44,586 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 390.138, 5.4.0-53-generic, x86_64: installed
 nvidia, 390.138, 5.4.0-54-generic, x86_64: installed
 virtualbox, 6.1.10, 5.4.0-53-generic, x86_64: installed
 virtualbox, 6.1.10, 5.4.0-54-generic, x86_64: installed
DpkgLog:
 
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
   Subsystem: Acer Incorporated [ALI] HD Graphics 5500 [1025:098a]
   Subsystem: Acer Incorporated [ALI] GM108M [GeForce 940M] [1025:098c]
InstallationDate: Installed on 2019-06-23 (731 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: Acer Aspire E5-573G
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic 
root=UUID=2151ff19-8bcb-4ed7-aded-0cfb4745ec95 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to focal on 2020-10-11 (256 days ago)
dmi.bios.date: 03/17/2015
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.07
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: ZORO_BH
dmi.board.vendor: Acer
dmi.board.version: Type2 - A01 Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.07:bd03/17/2015:svnAcer:pnAspireE5-573G:pvrV3.72:rvnAcer:rnZORO_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.family: BDW
dmi.product.name: Aspire E5-573G
dmi.product.sku: Aspire E5-573G_098A_1_07
dmi.product.version: V3.72
dmi.sys.vendor: Acer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
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
-- 
secondary portrait monitor is not portrait during boot
https://bugs.launchpad.net/bugs/1933452
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg in Ubuntu.

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

[Touch-packages] [Bug 1933221] Re: Blutooth on/off does not work properly from gnome-control-center

Hello Andy, or anyone else affected,

Accepted bluez into hirsute-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/bluez/5.56-0ubuntu4.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-
hirsute to verification-done-hirsute. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-hirsute. 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.

** Changed in: bluez (Ubuntu Hirsute)
   Status: New => Fix Committed

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

** Changed in: bluez (Ubuntu Focal)
   Status: New => Fix Committed

** Tags added: verification-needed-focal

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

Title:
  Blutooth on/off does not work properly from gnome-control-center

Status in OEM Priority Project:
  New
Status in bluez package in Ubuntu:
  Fix Committed
Status in bluez source package in Focal:
  Fix Committed
Status in bluez source package in Hirsute:
  Fix Committed

Bug description:
  [Impact]

   * On/off of Bluetooth in gnome-control-center will not work properly.

   * Devices are not refreshed in the list anymore.

   * The passed struct will depend on the length of the submitted read() and the
 kernel version.

  [Test Plan]

   * Open gnome-control-center and select Bluetooth
 
   * turn off Bluetooth via UI
 
   * turn on Bluetooth via UI

  [Where problems could occur]

   * If user install newer kernel such as 5.13, they may have this
  issue.

   * Tested on Intel AX201 and Intel 6235 with kernel version
  5.13.0-1003-oem.

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1933221/+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 1933221] Please test proposed package

Hello Andy, or anyone else affected,

Accepted bluez into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/bluez/5.53-0ubuntu3.3
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 bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1933221

Title:
  Blutooth on/off does not work properly from gnome-control-center

Status in OEM Priority Project:
  New
Status in bluez package in Ubuntu:
  Fix Committed
Status in bluez source package in Focal:
  Fix Committed
Status in bluez source package in Hirsute:
  Fix Committed

Bug description:
  [Impact]

   * On/off of Bluetooth in gnome-control-center will not work properly.

   * Devices are not refreshed in the list anymore.

   * The passed struct will depend on the length of the submitted read() and the
 kernel version.

  [Test Plan]

   * Open gnome-control-center and select Bluetooth
 
   * turn off Bluetooth via UI
 
   * turn on Bluetooth via UI

  [Where problems could occur]

   * If user install newer kernel such as 5.13, they may have this
  issue.

   * Tested on Intel AX201 and Intel 6235 with kernel version
  5.13.0-1003-oem.

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1933221/+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 1933452] Re: secondary portrait monitor is not portrait during boot

2021-06-24 Thread Ubuntu Foundations Team Bug Bot

** Package changed: ubuntu => xorg (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/1933452

Title:
  secondary portrait monitor is not portrait during boot

Status in xorg package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu 20.04 in my laptop. with that i'm using a secondary
  monitor which is portrait. these 2 works fine but in the boot menu,
  secondary monitor's screen is wrong. it's not portrait. please fix
  this issue.

  Thank you.
  Regards,
  Shehan

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-54.60-generic 5.4.65
  Uname: Linux 5.4.0-54-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:04:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.138  Thu May 14 01:01:53 
PDT 2020
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  ApportVersion: 2.20.11-0ubuntu27.12
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 24 15:49:32 2021
  DistUpgraded: 2020-10-11 07:43:44,586 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.138, 5.4.0-53-generic, x86_64: installed
   nvidia, 390.138, 5.4.0-54-generic, x86_64: installed
   virtualbox, 6.1.10, 5.4.0-53-generic, x86_64: installed
   virtualbox, 6.1.10, 5.4.0-54-generic, x86_64: installed
  DpkgLog:
   
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
 Subsystem: Acer Incorporated [ALI] HD Graphics 5500 [1025:098a]
 Subsystem: Acer Incorporated [ALI] GM108M [GeForce 940M] [1025:098c]
  InstallationDate: Installed on 2019-06-23 (731 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Acer Aspire E5-573G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-54-generic 
root=UUID=2151ff19-8bcb-4ed7-aded-0cfb4745ec95 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to focal on 2020-10-11 (256 days ago)
  dmi.bios.date: 03/17/2015
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.07
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: ZORO_BH
  dmi.board.vendor: Acer
  dmi.board.version: Type2 - A01 Board Version
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.07:bd03/17/2015:svnAcer:pnAspireE5-573G:pvrV3.72:rvnAcer:rnZORO_BH:rvrType2-A01BoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: BDW
  dmi.product.name: Aspire E5-573G
  dmi.product.sku: Aspire E5-573G_098A_1_07
  dmi.product.version: V3.72
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
  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

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

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

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

2021-06-24 Thread Lukas Märdian

> Gave some time between netplan apply and check without success, I can leave 
> it for
> hours and the IP never gets assigned

Indeed, I cannot see it being assigned an IPv4 address in your latest
"_delay" run. (Well, there is some assignment of an IP to enP53p0s0.171
at 15:05:29 in the journal logs, but that was before you started the
experiment).

> maybe what you are seeing is the manual assignment that I did with
> ip addr add 192.168.171.53/24 dev enP53p0s0.171

No I don't think so, as the timestamp of your manual "ip addr add"
command (08:13:02++) is after the systemd-networkd assignment in the
logs (08:12:38). Also, your output clearly shows that the IP was already
assigned when you tried to (re-)assign it manually (it shows the
"RTNETLINK answers: File exists" error):

> root@ilabg13:~# ip addr add 192.168.171.53/24 dev enP53p0s0.171
> RTNETLINK answers: File exists

I'm a bit worried about the /etc/systemd/network/10-enP53p0s0.link file (now 
there seems to be another one "10-enP53p0s0.link" as well...) – Is this file 
needed? Why was it created?
It matches on "MACAddress=82:0c:9b:c9:78:f8", which would match enP53p0s0 AND 
enP53p0s0.171 at the same time (they use the same inherited MAC address), 
leading to unspecified behavior, as we cannot rename two interfaces to the same 
"Name=enP53p0s0".

Could you try deleting this file in /etc/systemd/network/10-enP53p0s0.link 
(potentially adopting your netplan YAML config to the name assigned to this 
interface by the kernel/systemd) and check if this makes any difference?
# rm /etc/systemd/network/10-enP53p0s0.link

If for some reason you cannot delete this file, try adding a "Type=!vlan" line 
instead:
# cat /etc/systemd/network/10-enP53p0s0.link
[Match]
MACAddress=82:0c:9b:c9:78:f8
Type=!vlan

[Link]
Name=enP53p0s0

Does this make any difference when running "netplan apply && sleep 30 &&
networkctl status -a --no-pager"?

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

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

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

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

  # This is the network config written by 'subiquity'

  network:

ethernets:

  encdb0:

addresses:

- 11.111.114.213/22

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

  encdc0:

addresses:

- 11.111.112.213/22

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

  enP50s3832 :

addresses:

- 11.111.112.214/22

  enP53p0s0:

addresses:

- 11.111.112.215/22

vlans:

  encdb0.160:

id: 160

link: encdb0

mtu: 9000

addresses:

- 192.168.160.53/24

  encdc0.150:

id: 150

link: encdc0

mtu: 9000

addresses:

- 192.168.150.53/24

  enP50s3832.170:

id: 170

link: enP50s3832

mtu: 9000

addresses:

- 192.168.170.53/24

  enP53p0s0.171:

id: 171

link: enP53p0s0

mtu: 9000

addresses:

- 192.168.171.53/24

version: 2

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

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

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

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

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

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

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

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

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

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

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

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

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

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

2021-06-24 Thread Marian Rainer-Harbach

** Tags added: verification-done

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

Title:
  Recent iCloud versions trigger an issue in IMAP x

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

Bug description:
  * Impact

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

  * Test case

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

  * Regression potential

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

  
  -


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

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

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

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

[Touch-packages] [Bug 1933506] [NEW] ubuntu 20.04 no show cursor in 1 of 3 monitors

2021-06-24 Thread alexandro cruz

Public bug reported:

Install Ubuntu 20.04, I have 3 monitors but I can not make the mouse
work on the monitor 1, stays stuck on the center monitor and does not
pass the cursor.

If I use the option on the title bar and press "Move to the screen on
the left this works without problem" However, it could not access the
window that I sent to that screen.

That is to say everything works but the mouse does not pass, and
attempting by removing the stickers with "Retouch Editor" but it does
not work, also try changing the dock and monitor but the problem with
the monitor 1 persists.

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


** Tags: 3monitor

** Attachment added: "simplescreenrecorder-2021-06-24_08.24.17.mkv"
   
https://bugs.launchpad.net/bugs/1933506/+attachment/5506733/+files/simplescreenrecorder-2021-06-24_08.24.17.mkv

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

Title:
  ubuntu 20.04 no show cursor in 1 of 3 monitors

Status in gpm package in Ubuntu:
  New

Bug description:
  Install Ubuntu 20.04, I have 3 monitors but I can not make the mouse
  work on the monitor 1, stays stuck on the center monitor and does not
  pass the cursor.

  If I use the option on the title bar and press "Move to the screen on
  the left this works without problem" However, it could not access the
  window that I sent to that screen.

  That is to say everything works but the mouse does not pass, and
  attempting by removing the stickers with "Retouch Editor" but it does
  not work, also try changing the dock and monitor but the problem with
  the monitor 1 persists.

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

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

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

2021-06-24 Thread Bug Watch Updater

** Changed in: bluez
   Status: Unknown => Fix Released

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

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

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

Bug description:
  [Impact]

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

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

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

  [Where problems could occur]

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

  [Other info]

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

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

  [Original bug report]

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

    Bluetooth: hci0: HCI reset during shutdown failed

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

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

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

[Touch-packages] [Bug 1933221] Re: Blutooth on/off does not work properly from gnome-control-center

2021-06-24 Thread Andy Chi

[OS version]
Focal

[kernel version]
5.13-oem

[Step]
1. open gnome-settings
2. turn off Bluetooth by toggle
3. turn on Bluetooth by toggle

It works fine.

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

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

Title:
  Blutooth on/off does not work properly from gnome-control-center

Status in OEM Priority Project:
  New
Status in bluez package in Ubuntu:
  Fix Committed
Status in bluez source package in Focal:
  Fix Committed
Status in bluez source package in Hirsute:
  Fix Committed

Bug description:
  [Impact]

   * On/off of Bluetooth in gnome-control-center will not work properly.

   * Devices are not refreshed in the list anymore.

   * The passed struct will depend on the length of the submitted read() and the
 kernel version.

  [Test Plan]

   * Open gnome-control-center and select Bluetooth
 
   * turn off Bluetooth via UI
 
   * turn on Bluetooth via UI

  [Where problems could occur]

   * If user install newer kernel such as 5.13, they may have this
  issue.

   * Tested on Intel AX201 and Intel 6235 with kernel version
  5.13.0-1003-oem.

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1933221/+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 1933221] Re: Blutooth on/off does not work properly from gnome-control-center

2021-06-24 Thread Andy Chi

[OS version]
Hirsute

[kernel version]
5.11.0-16-generic

[Step]
1. open gnome-settings
2. turn off Bluetooth by toggle
3. turn on Bluetooth by toggle

It works fine.

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

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

Title:
  Blutooth on/off does not work properly from gnome-control-center

Status in OEM Priority Project:
  New
Status in bluez package in Ubuntu:
  Fix Committed
Status in bluez source package in Focal:
  Fix Committed
Status in bluez source package in Hirsute:
  Fix Committed

Bug description:
  [Impact]

   * On/off of Bluetooth in gnome-control-center will not work properly.

   * Devices are not refreshed in the list anymore.

   * The passed struct will depend on the length of the submitted read() and the
 kernel version.

  [Test Plan]

   * Open gnome-control-center and select Bluetooth
 
   * turn off Bluetooth via UI
 
   * turn on Bluetooth via UI

  [Where problems could occur]

   * If user install newer kernel such as 5.13, they may have this
  issue.

   * Tested on Intel AX201 and Intel 6235 with kernel version
  5.13.0-1003-oem.

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

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

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

Public bug reported:

[impact]

gzip/libgzip fails for systemd services using MemoryDenyWriteExecute=yes

[test case]

note this only fails on ppc64el for this test case

can be reproduced with systemd localed-locale e.g.:
https://salsa.debian.org/systemd-team/systemd/-/merge_requests/116#note_245685

install upstream systemd from ppa:
https://launchpad.net/~ubuntu-support-team/+archive/ubuntu/systemd

get the upstream autopkgtests:
https://salsa.debian.org/systemd-team/systemd/-/tree/debian/master/debian/tests

run the 'localed-locale' test

[regression potential]

TBD

[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

** Affects: gzip (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: gzip (Ubuntu Bionic)
 Importance: Low
 Assignee: Dan Streetman (ddstreet)
 Status: In Progress

** Also affects: gzip (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: gzip (Ubuntu)
   Status: New => Fix Released

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

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

** Changed in: gzip (Ubuntu Bionic)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

-- 
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:
  In Progress

Bug description:
  [impact]

  gzip/libgzip fails for systemd services using
  MemoryDenyWriteExecute=yes

  [test case]

  note this only fails on ppc64el for this test case

  can be reproduced with systemd localed-locale e.g.:
  https://salsa.debian.org/systemd-team/systemd/-/merge_requests/116#note_245685

  install upstream systemd from ppa:
  https://launchpad.net/~ubuntu-support-team/+archive/ubuntu/systemd

  get the upstream autopkgtests:
  
https://salsa.debian.org/systemd-team/systemd/-/tree/debian/master/debian/tests

  run the 'localed-locale' test

  [regression potential]

  TBD

  [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 1931725] Re: initramfs-tools & kernel: use zstd as the default compression method

2021-06-24 Thread Dimitri John Ledkov

decompression speed only needs to be faster than i/o speed, once that is
reached the best compression ratio results in the fastest bootspped.

for kernel image zstd is used with -22 --ultra, thus I can compare it
with zlib -9.

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

Title:
initramfs-tools & kernel: use zstd as the default compression method

Status in Ubuntu on IBM z Systems:
New
Status in initramfs-tools package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
New

Bug description:
Turns out that loading is always the slow part in loading initramfs
into memory and decompressing it since decompression is always the
final 10-20% or so of the task. It therefore makes sense to use a
good compressor that shrinks the initramfs as much as possible with
little decompression overhead.

Benchmarking zstd vs lz4 shows that while zstd can be ~5x slower in
decompression, the image size is much smaller with zstd than lz4, and
since ~80-90% of the boot time is loading the image it makes sense to
use zstd.

Attached is a libreoffice spread sheet showing typical load and
decompression times for a fairly standard 3.4 GHZ intel box with data
for load times for a 5400 RPM, 7200 RPM and SATA SSD drives.

The conclusions from the test results (attached) show:

1. Loading time is always significantly slower than decompression time.
2. ZSTD is 5x slower than LZ4 in decompression speed but produces far
better compressed images
3. Given that loading time is the major factor in loading +
decompression, ZSTD is best for kernel and initramfs boot timings.

(Also refer to https://kernel.ubuntu.com/~cking/boot-speed-eoan-5.3
/kernel-compression-method.txt for some raw data on drive load speeds
for the same UEFI box I did a couple of years ago).

amd64 supports zstd, but s390x does not. Will use this bug to enable
zstd support on s390x.

Upstream submitted patch

https://lore.kernel.org/linux-s390/20210615114150.325080-1-dimitri.led...@canonical.com/T/#u

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

** Description changed:

  [impact]
  
  gzip/libgzip fails for systemd services using MemoryDenyWriteExecute=yes
  
  [test case]
  
  note this only fails on ppc64el for this test case
  
  can be reproduced with systemd localed-locale e.g.:
  https://salsa.debian.org/systemd-team/systemd/-/merge_requests/116#note_245685
  
  install upstream systemd from ppa:
  https://launchpad.net/~ubuntu-support-team/+archive/ubuntu/systemd
  
  get the upstream autopkgtests:
  
https://salsa.debian.org/systemd-team/systemd/-/tree/debian/master/debian/tests
  
  run the 'localed-locale' test
  
  [regression potential]
  
- TBD
+ as this sets NO_ASM any regression would likely involve changed
+ performance or architecture-specific failures
  
  [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

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

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

-- 
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:
  In Progress
Status in gzip package in Debian:
  Unknown

Bug description:
  [impact]

  gzip/libgzip fails for systemd services using
  MemoryDenyWriteExecute=yes

  [test case]

  note this only fails on ppc64el for this test case

  can be reproduced with systemd localed-locale e.g.:
  https://salsa.debian.org/systemd-team/systemd/-/merge_requests/116#note_245685

  install upstream systemd from ppa:
  https://launchpad.net/~ubuntu-support-team/+archive/ubuntu/systemd

  get the upstream autopkgtests:
  
https://salsa.debian.org/systemd-team/systemd/-/tree/debian/master/debian/tests

  run the 'localed-locale' test

  [regression potential]

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

  [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 1929657] Comment bridged from LTC Bugzilla

2021-06-24 Thread bugproxy

--- Comment From mario.alberto.gali...@ibm.com 2021-06-24 11:53 EDT---
Giving it a try without the /etc/systemd/network/ files

- Checking that it is empty
root@ilabg13:~# ll /etc/systemd/network/
total 8
drwxr-xr-x 2 root root 4096 Jun 24 08:41 ./
drwxr-xr-x 5 root root 4096 Jun 17 06:18 ../

- Try to assign ip via netplan
root@ilabg13:~# date
Thu Jun 24 08:47:45 MST 2021
root@ilabg13:~# netplan apply

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

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

- IP still not being assigned
root@ilabg13:~# ip a
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: encdb0:  mtu 9000 qdisc mq state UP group 
default qlen 1000
link/ether 02:76:54:00:00:03 brd ff:ff:ff:ff:ff:ff
inet 11.111.114.213/22 brd 11.111.115.255 scope global encdb0
valid_lft forever preferred_lft forever
inet6 fe80::76:54ff:fe00:3/64 scope link
valid_lft forever preferred_lft forever
3: ence0f:  mtu 1500 qdisc mq state UP group 
default qlen 1000
link/ether 02:76:54:00:00:04 brd ff:ff:ff:ff:ff:ff
inet 9.11.116.213/24 brd 9.11.116.255 scope global ence0f
valid_lft forever preferred_lft forever
inet6 2002:90b:e006:116:76:54ff:fe00:4/64 scope global dynamic mngtmpaddr 
noprefixroute
valid_lft 2591841sec preferred_lft 604641sec
inet6 fe80::76:54ff:fe00:4/64 scope link
valid_lft forever preferred_lft forever
4: encdc0:  mtu 9000 qdisc mq state UP group 
default qlen 1000
link/ether 02:76:54:00:00:04 brd ff:ff:ff:ff:ff:ff
inet 11.111.112.213/22 brd 11.111.115.255 scope global encdc0
valid_lft forever preferred_lft forever
inet6 fe80::76:54ff:fe00:4/64 scope link
valid_lft forever preferred_lft forever
5: encdc0.150@encdc0:  mtu 9000 qdisc noqueue 
state UP group default qlen 1000
link/ether 02:76:54:00:00:04 brd ff:ff:ff:ff:ff:ff
inet 192.168.150.53/24 brd 192.168.150.255 scope global encdc0.150
valid_lft forever preferred_lft forever
inet6 fe80::76:54ff:fe00:4/64 scope link
valid_lft forever preferred_lft forever
6: encdb0.160@encdb0:  mtu 9000 qdisc noqueue 
state UP group default qlen 1000
link/ether 02:76:54:00:00:03 brd ff:ff:ff:ff:ff:ff
inet 192.168.160.53/24 brd 192.168.160.255 scope global encdb0.160
valid_lft forever preferred_lft forever
inet6 fe80::76:54ff:fe00:3/64 scope link
valid_lft forever preferred_lft forever
7: enP50s3832:  mtu 9000 qdisc mq state UP 
group default qlen 1000
link/ether 82:0c:9b:a8:a1:b2 brd ff:ff:ff:ff:ff:ff
inet6 fe80::800c:9bff:fea8:a1b2/64 scope link
valid_lft forever preferred_lft forever
8: enP53p0s0:  mtu 9000 qdisc mq state UP 
group default qlen 1000
link/ether 82:0c:9b:c9:78:f8 brd ff:ff:ff:ff:ff:ff
inet6 fe80::800c:9bff:fec9:78f8/64 scope link
valid_lft forever preferred_lft forever
9: enP53p0s0.171@enP53p0s0:  mtu 9000 qdisc 
noqueue state UP group default qlen 1000
link/ether 82:0c:9b:c9:78:f8 brd ff:ff:ff:ff:ff:ff
inet6 fe80::800c:9bff:fec9:78f8/64 scope link
valid_lft forever preferred_lft forever
10: enP50s3832.170@enP50s3832:  mtu 9000 qdisc 
noqueue state UP group default qlen 1000
link/ether 82:0c:9b:a8:a1:b2 brd ff:ff:ff:ff:ff:

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

2021-06-24 Thread bugproxy

--- Comment (attachment only) From mario.alberto.gali...@ibm.com 2021-06-24 
11:57 EDT---


** Attachment added: "udevadm monitor nofiles"
   
https://bugs.launchpad.net/bugs/1929657/+attachment/5506750/+files/udevadm_monitor_nofiles.txt

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

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

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

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

  # This is the network config written by 'subiquity'

  network:

ethernets:

  encdb0:

addresses:

- 11.111.114.213/22

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

  encdc0:

addresses:

- 11.111.112.213/22

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

  enP50s3832 :

addresses:

- 11.111.112.214/22

  enP53p0s0:

addresses:

- 11.111.112.215/22

vlans:

  encdb0.160:

id: 160

link: encdb0

mtu: 9000

addresses:

- 192.168.160.53/24

  encdc0.150:

id: 150

link: encdc0

mtu: 9000

addresses:

- 192.168.150.53/24

  enP50s3832.170:

id: 170

link: enP50s3832

mtu: 9000

addresses:

- 192.168.170.53/24

  enP53p0s0.171:

id: 171

link: enP53p0s0

mtu: 9000

addresses:

- 192.168.171.53/24

version: 2

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1929657] journalctl no files

2021-06-24 Thread bugproxy

--- Comment (attachment only) From mario.alberto.gali...@ibm.com 2021-06-24 
11:57 EDT---


** Attachment added: "journalctl no files"
   
https://bugs.launchpad.net/bugs/1929657/+attachment/5506751/+files/journalctl_udev_nofiles.txt.zip

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

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

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

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

  # This is the network config written by 'subiquity'

  network:

ethernets:

  encdb0:

addresses:

- 11.111.114.213/22

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

  encdc0:

addresses:

- 11.111.112.213/22

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

  enP50s3832 :

addresses:

- 11.111.112.214/22

  enP53p0s0:

addresses:

- 11.111.112.215/22

vlans:

  encdb0.160:

id: 160

link: encdb0

mtu: 9000

addresses:

- 192.168.160.53/24

  encdc0.150:

id: 150

link: encdc0

mtu: 9000

addresses:

- 192.168.150.53/24

  enP50s3832.170:

id: 170

link: enP50s3832

mtu: 9000

addresses:

- 192.168.170.53/24

  enP53p0s0.171:

id: 171

link: enP53p0s0

mtu: 9000

addresses:

- 192.168.171.53/24

version: 2

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1933516] Re: gzip: error while loading shared libraries: cannot restore segment prot after reloc: Operation not permitted

2021-06-24 Thread Bug Watch Updater

** Changed in: gzip (Debian)
   Status: Unknown => Fix Released

-- 
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:
  In Progress
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 for this test case

  can be reproduced with systemd localed-locale e.g.:
  https://salsa.debian.org/systemd-team/systemd/-/merge_requests/116#note_245685

  install upstream systemd from ppa:
  https://launchpad.net/~ubuntu-support-team/+archive/ubuntu/systemd

  get the upstream autopkgtests:
  
https://salsa.debian.org/systemd-team/systemd/-/tree/debian/master/debian/tests

  run the 'localed-locale' test

  [regression potential]

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

  [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 1933516] Re: gzip: error while loading shared libraries: cannot restore segment prot after reloc: Operation not permitted

** Description changed:

  [impact]
  
  gzip/libgzip fails for systemd services using MemoryDenyWriteExecute=yes
  
  [test case]
  
- note this only fails on ppc64el for this test case
+ note this only fails on ppc64el
  
- can be reproduced with systemd localed-locale e.g.:
- https://salsa.debian.org/systemd-team/systemd/-/merge_requests/116#note_245685
+ create service file /etc/systemd/system/test-localegen.service with
+ content:
  
- install upstream systemd from ppa:
- https://launchpad.net/~ubuntu-support-team/+archive/ubuntu/systemd
+ [Service]
+ MemoryDenyWriteExecute=yes
+ ExecStart=/usr/sbin/locale-gen
  
- get the upstream autopkgtests:
- 
https://salsa.debian.org/systemd-team/systemd/-/tree/debian/master/debian/tests
  
- run the 'localed-locale' test
+ 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
  
  [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

-- 
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:
  In Progress
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

[Touch-packages] [Bug 1933529] [NEW] package linux-image-5.8.0-59-generic 5.8.0-59.66~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2021-06-24 Thread LadyRascal

Public bug reported:

ok

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-image-5.8.0-59-generic 5.8.0-59.66~20.04.1
ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-55-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Jun 24 20:21:40 2021
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
InstallationDate: Installed on 2021-06-12 (11 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.5
SourcePackage: initramfs-tools
Title: package linux-image-5.8.0-59-generic 5.8.0-59.66~20.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal

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

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

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  ok

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-59-generic 5.8.0-59.66~20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-55-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Jun 24 20:21:40 2021
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2021-06-12 (11 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.5
  SourcePackage: initramfs-tools
  Title: package linux-image-5.8.0-59-generic 5.8.0-59.66~20.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1933529/+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 1933530] [NEW] Translation error with accentuation

2021-06-24 Thread Tonin R. Bolzan

Public bug reported:

An alert is issued when the snap is called

```sh
# LANG=pt_BR snap refresh
2021/05/30 22:22:17.293001 main.go:176: description of prepare-image's 
"" is lowercase: "o directório de destino"
Todos os snaps atualizados.
```sh

In en_US works as expected

```sh
# LANG=en_US snap refresh
All snaps up to date.
```
Patch Attached
Change line 4581 of data/pt/LC_MESSAGES/snappy.po
```
-msgstr "o directório de destino"
+msgstr "O directório de destino"
```


Bug cross posted in https://bugs.launchpad.net/snappy/+bug/1930175

** Affects: language-pack-pt-base (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Translation error with accentuation

Status in language-pack-pt-base package in Ubuntu:
  New

Bug description:
  An alert is issued when the snap is called

  ```sh
  # LANG=pt_BR snap refresh
  2021/05/30 22:22:17.293001 main.go:176: description of prepare-image's 
"" is lowercase: "o directório de destino"
  Todos os snaps atualizados.
  ```sh

  In en_US works as expected

  ```sh
  # LANG=en_US snap refresh
  All snaps up to date.
  ```
  Patch Attached
  Change line 4581 of data/pt/LC_MESSAGES/snappy.po
  ```
  -msgstr "o directório de destino"
  +msgstr "O directório de destino"
  ```

  
  Bug cross posted in https://bugs.launchpad.net/snappy/+bug/1930175

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-pack-pt-base/+bug/1933530/+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 1933530] Re: Translation error with accentuation

2021-06-24 Thread Tonin R. Bolzan

** Description changed:

  An alert is issued when the snap is called
  
  ```sh
  # LANG=pt_BR snap refresh
  2021/05/30 22:22:17.293001 main.go:176: description of prepare-image's 
"" is lowercase: "o directório de destino"
  Todos os snaps atualizados.
  ```sh
  
  In en_US works as expected
  
  ```sh
  # LANG=en_US snap refresh
  All snaps up to date.
  ```
- 
- Affected file
- /usr/share/locale-langpack/pt/LC_MESSAGES/snappy.mo
+ Patch Attached
+ Change line 4581 of data/pt/LC_MESSAGES/snappy.po
+ ```
+ -msgstr "o directório de destino"
+ +msgstr "O directório de destino"
+ ```
  
  
  Bug cross posted in https://bugs.launchpad.net/snappy/+bug/1930175

** Patch added: "snappy.patch"
   
https://bugs.launchpad.net/ubuntu/+source/language-pack-pt-base/+bug/1933530/+attachment/5506768/+files/snappy.patch

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

Title:
  Translation error with accentuation

Status in language-pack-pt-base package in Ubuntu:
  New

Bug description:
  An alert is issued when the snap is called

  ```sh
  # LANG=pt_BR snap refresh
  2021/05/30 22:22:17.293001 main.go:176: description of prepare-image's 
"" is lowercase: "o directório de destino"
  Todos os snaps atualizados.
  ```sh

  In en_US works as expected

  ```sh
  # LANG=en_US snap refresh
  All snaps up to date.
  ```
  Patch Attached
  Change line 4581 of data/pt/LC_MESSAGES/snappy.po
  ```
  -msgstr "o directório de destino"
  +msgstr "O directório de destino"
  ```

  
  Bug cross posted in https://bugs.launchpad.net/snappy/+bug/1930175

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-pack-pt-base/+bug/1933530/+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 1933531] [NEW] mv command deleted source file without moving to destination

2021-06-24 Thread Tom Arons

Public bug reported:

 I mv'd a file to a directory where I had group write permissions, but a
file existed owned by another user.  I was asked if I wanted to override
the permissions.  I said "y". The ownership was changed on the
destination file to me, but the mod time and contents of the file were
not changed and the source file was deleted.  I tried to duplicate the
behavior, but it worked as it should with a test file.

toma@admn1:~$ ls -ld /opt/scripts
drwxrwxr-- 3 ansible ansible 4096 Jun 24 16:25 /opt/scripts
toma@admn1:~$ mv GeneratePortList.pl /opt/scripts/
mv: replace '/opt/scripts/GeneratePortList.pl', overriding mode 0755 
(rwxr-xr-x)? y
toma@admn1:~$ ls -l /opt/scripts/GeneratePortList.pl 
-rwxr-xr-x 1 toma domain users 2855 Jul 16  2018 
/opt/scripts/GeneratePortList.pl

I have mv aliased to mv -i so I can confirm that the existing
destination file was not owned by me since I was not prompted to
overwrite the file.

Both source and destination are in the same file system.  I cannot find
the source file anywhere.


toma@admn1:~$ lsb_release -rd
Description:Ubuntu 20.04.2 LTS
Release:20.04
toma@admn1:~$ uname -a
Linux admn1.aaisdirect.com 5.4.0-1048-aws #50-Ubuntu SMP Mon May 3 21:44:17 UTC 
2021 x86_64 x86_64 x86_64 GNU/Linux
toma@admn1:~$ apt-cache policy coreutils
coreutils:
  Installed: 8.30-3ubuntu2
  Candidate: 8.30-3ubuntu2
  Version table:
 *** 8.30-3ubuntu2 500
500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu focal/main amd64 
Packages
100 /var/lib/dpkg/status
 8.28-1ubuntu1 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages

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

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

Title:
  mv command deleted source file without moving to destination

Status in coreutils package in Ubuntu:
  New

Bug description:
   I mv'd a file to a directory where I had group write permissions, but
  a file existed owned by another user.  I was asked if I wanted to
  override the permissions.  I said "y". The ownership was changed on
  the destination file to me, but the mod time and contents of the file
  were not changed and the source file was deleted.  I tried to
  duplicate the behavior, but it worked as it should with a test file.

  toma@admn1:~$ ls -ld /opt/scripts
  drwxrwxr-- 3 ansible ansible 4096 Jun 24 16:25 /opt/scripts
  toma@admn1:~$ mv GeneratePortList.pl /opt/scripts/
  mv: replace '/opt/scripts/GeneratePortList.pl', overriding mode 0755 
(rwxr-xr-x)? y
  toma@admn1:~$ ls -l /opt/scripts/GeneratePortList.pl 
  -rwxr-xr-x 1 toma domain users 2855 Jul 16  2018 
/opt/scripts/GeneratePortList.pl

  I have mv aliased to mv -i so I can confirm that the existing
  destination file was not owned by me since I was not prompted to
  overwrite the file.

  Both source and destination are in the same file system.  I cannot
  find the source file anywhere.

  
  toma@admn1:~$ lsb_release -rd
  Description:  Ubuntu 20.04.2 LTS
  Release:  20.04
  toma@admn1:~$ uname -a
  Linux admn1.aaisdirect.com 5.4.0-1048-aws #50-Ubuntu SMP Mon May 3 21:44:17 
UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
  toma@admn1:~$ apt-cache policy coreutils
  coreutils:
Installed: 8.30-3ubuntu2
Candidate: 8.30-3ubuntu2
Version table:
   *** 8.30-3ubuntu2 500
  500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu focal/main amd64 
Packages
  100 /var/lib/dpkg/status
   8.28-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1933531/+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 1929560] Re: link mac isn't set if already up

2021-06-24 Thread Jan Graichen

This backport to 18.04 LTS broke all our OpenStack compute nodes. We use
systemd-network to configure interfaces etc. and neutron-linuxbridge-
agent with some flat networks. In this scenario, the neutron agent
creates bridges for the flat networks and assigns them to physical
interfaces based on a mapping.

The backport now sets nomaster on these interfaces, effectively removing
the bridges and cutting of connectivity of all VMs using these flat
networks. This happened already when the systemd package was upgraded
(and systemd-networkd restarted).

Example:

```
10: flat-net1@data:  mtu 1500 qdisc noqueue 
master brq88363244-5f state UP group default qlen 1000
link/ether b0:22:28:1c:f7:12 brd ff:ff:ff:ff:ff:ff
```

The interface (VLAN here) is created and managed by systemd-networkd,
the bridge `brq88363244-5f` is managed by neutron. Of course, systemd-
networkd doesn't know anything about the bridge, this wasn't a problem
until now, but the latest patch update always sets nomaster to `flat-
net1`. We were really surprise by this change in 18.04 LTS.

Is there any recommend workaround to have systemd-networkd not set
nomaster or do we have to not use systemd-network at all?

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

Title:
  link mac isn't set if already up

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

Bug description:
  [impact]

  if link is already up, configured mac isn't set

  this also affects the master/nomaster configuration

  [test case]

  create .network config for the link, for example:

  [Match]
  Name=eth0

  [Link]
  MACAddress=00:16:3e:ff:ff:ff

  [Network]
  DHCP=yes

  
  make sure the link is already up, and restart systemd-networkd:

  root@test-f:/etc/systemd/network# ip l show eth0
  61: eth0@if62:  mtu 1500 qdisc noqueue state DOWN mode 
DEFAULT group default qlen 1000
  link/ether 00:16:3e:fc:b2:00 brd ff:ff:ff:ff:ff:ff link-netnsid 0
  root@test-f:/etc/systemd/network# ip l set dev eth0 up
  root@test-f:/etc/systemd/network# ip l show eth0
  61: eth0@if62:  mtu 1500 qdisc noqueue state 
UP mode DEFAULT group default qlen 1000
  link/ether 00:16:3e:fc:b2:00 brd ff:ff:ff:ff:ff:ff link-netnsid 0
  root@test-f:/etc/systemd/network# systemctl restart systemd-networkd
  root@test-f:/etc/systemd/network# ip l show eth0
  61: eth0@if62:  mtu 1500 qdisc noqueue state 
UP mode DEFAULT group default qlen 1000
  link/ether 00:16:3e:fc:b2:00 brd ff:ff:ff:ff:ff:ff link-netnsid 0
  root@test-f:/etc/systemd/network# ip l set dev eth0 down
  root@test-f:/etc/systemd/network# ip l show eth0
  61: eth0@if62:  mtu 1500 qdisc noqueue state DOWN mode 
DEFAULT group default qlen 1000
  link/ether 00:16:3e:fc:b2:00 brd ff:ff:ff:ff:ff:ff link-netnsid 0
  root@test-f:/etc/systemd/network# systemctl restart systemd-networkd
  root@test-f:/etc/systemd/network# ip l show eth0
  61: eth0@if62:  mtu 1500 qdisc noqueue state 
UP mode DEFAULT group default qlen 1000
  link/ether 00:16:3e:ff:ff:ff brd ff:ff:ff:ff:ff:ff link-netnsid 0

  [regression potential]

  any regression would likely result in incorrectly set link mac and/or
  master, or failure to correctly set mac and/or master

  [scope]

  this is needed for g and earlier

  this is fixed upstream by commit
  e16e4b3bedc57919b3ecb4096e941709a5d39b8a which is included in v247 so
  this is fixed already in h and later

  [other info]

  this moves the configuration of the link mac and master out of the
  link_up() function, so this also allows repeated calls to link_up()
  without reconfiguring the link mac and master. That behavior is useful
  for the commits for bug 1664844

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1929560/+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 1933537] [NEW] add-apt-repository should store PGP keys in /usr/share/keyrings because /etc/apt/trusted.gpg.d is deprecated for third party repos

2021-06-24 Thread m.eik michalke

Public bug reported:

PPAs are third party repositories. for security reasons, PGP keys for
these must not be placed in /etc/apt/trusted.gpg.d, according to this
document:

  https://wiki.debian.org/DebianRepository/UseThirdParty

they should instead be saved to /usr/share/keyrings and the generated
.list file for the repo added should refer to its particular key by
using a [signed-by=/usr/share/keyrings/...] argument. this ensures that
the downloaded PGP key will only be used to verify a particular
repository and is not globally available to verify package lists of all
configured repositories (as are all keys found in
/etc/apt/trusted.gpg.d).

please fix add-apt-repository accordingly.

Ubuntu 20.04.2 LTS
software-properties-common 0.98.9.5

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  add-apt-repository should store PGP keys in /usr/share/keyrings
  because /etc/apt/trusted.gpg.d is deprecated for third party repos

Status in software-properties package in Ubuntu:
  New

Bug description:
  PPAs are third party repositories. for security reasons, PGP keys for
  these must not be placed in /etc/apt/trusted.gpg.d, according to this
  document:

https://wiki.debian.org/DebianRepository/UseThirdParty

  they should instead be saved to /usr/share/keyrings and the generated
  .list file for the repo added should refer to its particular key by
  using a [signed-by=/usr/share/keyrings/...] argument. this ensures
  that the downloaded PGP key will only be used to verify a particular
  repository and is not globally available to verify package lists of
  all configured repositories (as are all keys found in
  /etc/apt/trusted.gpg.d).

  please fix add-apt-repository accordingly.

  Ubuntu 20.04.2 LTS
  software-properties-common 0.98.9.5

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1933537/+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 1929560] Re: link mac isn't set if already up

>Is there any recommend workaround to have systemd-networkd not set
nomaster or do we have to not use systemd-network at all?

open a new bug and provide your specific networkd configuration

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

Title:
  link mac isn't set if already up

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

Bug description:
  [impact]

  if link is already up, configured mac isn't set

  this also affects the master/nomaster configuration

  [test case]

  create .network config for the link, for example:

  [Match]
  Name=eth0

  [Link]
  MACAddress=00:16:3e:ff:ff:ff

  [Network]
  DHCP=yes

  
  make sure the link is already up, and restart systemd-networkd:

  root@test-f:/etc/systemd/network# ip l show eth0
  61: eth0@if62:  mtu 1500 qdisc noqueue state DOWN mode 
DEFAULT group default qlen 1000
  link/ether 00:16:3e:fc:b2:00 brd ff:ff:ff:ff:ff:ff link-netnsid 0
  root@test-f:/etc/systemd/network# ip l set dev eth0 up
  root@test-f:/etc/systemd/network# ip l show eth0
  61: eth0@if62:  mtu 1500 qdisc noqueue state 
UP mode DEFAULT group default qlen 1000
  link/ether 00:16:3e:fc:b2:00 brd ff:ff:ff:ff:ff:ff link-netnsid 0
  root@test-f:/etc/systemd/network# systemctl restart systemd-networkd
  root@test-f:/etc/systemd/network# ip l show eth0
  61: eth0@if62:  mtu 1500 qdisc noqueue state 
UP mode DEFAULT group default qlen 1000
  link/ether 00:16:3e:fc:b2:00 brd ff:ff:ff:ff:ff:ff link-netnsid 0
  root@test-f:/etc/systemd/network# ip l set dev eth0 down
  root@test-f:/etc/systemd/network# ip l show eth0
  61: eth0@if62:  mtu 1500 qdisc noqueue state DOWN mode 
DEFAULT group default qlen 1000
  link/ether 00:16:3e:fc:b2:00 brd ff:ff:ff:ff:ff:ff link-netnsid 0
  root@test-f:/etc/systemd/network# systemctl restart systemd-networkd
  root@test-f:/etc/systemd/network# ip l show eth0
  61: eth0@if62:  mtu 1500 qdisc noqueue state 
UP mode DEFAULT group default qlen 1000
  link/ether 00:16:3e:ff:ff:ff brd ff:ff:ff:ff:ff:ff link-netnsid 0

  [regression potential]

  any regression would likely result in incorrectly set link mac and/or
  master, or failure to correctly set mac and/or master

  [scope]

  this is needed for g and earlier

  this is fixed upstream by commit
  e16e4b3bedc57919b3ecb4096e941709a5d39b8a which is included in v247 so
  this is fixed already in h and later

  [other info]

  this moves the configuration of the link mac and master out of the
  link_up() function, so this also allows repeated calls to link_up()
  without reconfiguring the link mac and master. That behavior is useful
  for the commits for bug 1664844

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

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

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

2021-06-24 Thread Víctor

Why do I need to install nothing when an Ubuntu Update is installed?

It has no sense. The Ubuntu Update must have all the things that the
update need.

I have installed this:

sudo apt install linux-generic
and this:
sudo apt install linux-generic-hwe-20.04

but it doesn't work.

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

Title:
  Audio Problem, soundcard not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hi,

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

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

  My GPU is an GTX 1080 Ti.

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

  Before the last update of Ubuntu, all worked well.

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

  Regards.

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

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

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

[Touch-packages] [Bug 1933530] Re: Translation error with accentuation

2021-06-24 Thread Ubuntu Foundations Team Bug Bot

The attachment "snappy.patch" seems to be a patch.  If it isn't, please
remove the "patch" flag from the attachment, remove the "patch" tag, and
if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  Translation error with accentuation

Status in language-pack-pt-base package in Ubuntu:
  New

Bug description:
  An alert is issued when the snap is called

  ```sh
  # LANG=pt_BR snap refresh
  2021/05/30 22:22:17.293001 main.go:176: description of prepare-image's 
"" is lowercase: "o directório de destino"
  Todos os snaps atualizados.
  ```sh

  In en_US works as expected

  ```sh
  # LANG=en_US snap refresh
  All snaps up to date.
  ```
  Patch Attached
  Change line 4581 of data/pt/LC_MESSAGES/snappy.po
  ```
  -msgstr "o directório de destino"
  +msgstr "O directório de destino"
  ```

  
  Bug cross posted in https://bugs.launchpad.net/snappy/+bug/1930175

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-pack-pt-base/+bug/1933530/+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 1933529] Re: package linux-image-5.8.0-59-generic 5.8.0-59.66~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2021-06-24 Thread Ubuntu Foundations Team Bug Bot

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware.  I recommend
performing a back up and then investigating the situation.  Measures you
might take include checking cable connections and using software tools
to investigate the health of your hardware.  In the event that is is not
in fact an error with your hardware please set the bug's status back to
New.  Thanks and good luck!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: hardware-error

** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided => Low

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

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

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

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  ok

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-59-generic 5.8.0-59.66~20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-55-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Jun 24 20:21:40 2021
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2021-06-12 (11 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.5
  SourcePackage: initramfs-tools
  Title: package linux-image-5.8.0-59-generic 5.8.0-59.66~20.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1933529/+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 1931725] Re: initramfs-tools & kernel: use zstd as the default compression method

2021-06-24 Thread Dimitri John Ledkov

@cborntra

v5.13 ubuntu kernel's s390 configuration with zstd -22 --ultra
compression is 8.5 MB, whereas gzip -9 is 11M.

Thus for gzip to win at bootspeed the decompression speed has to
compensate for 2.5M of i/o and be faster than zstd.

Unaccelerated decompression comparison still gives me faster
decompression with less i/o with zstd compressed kernel image.

At Canonical we still do not have z15 mainframe available for us to
benchmark this.

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

Title:
initramfs-tools & kernel: use zstd as the default compression method

Status in Ubuntu on IBM z Systems:
New
Status in initramfs-tools package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
New

Attached is a libreoffice spread sheet showing typical load and
decompression times for a fairly standard 3.4 GHZ intel box with data
for load times for a 5400 RPM, 7200 RPM and SATA SSD drives.

The conclusions from the test results (attached) show:

(Also refer to https://kernel.ubuntu.com/~cking/boot-speed-eoan-5.3
/kernel-compression-method.txt for some raw data on drive load speeds
for the same UEFI box I did a couple of years ago).

amd64 supports zstd, but s390x does not. Will use this bug to enable
zstd support on s390x.

Upstream submitted patch

https://lore.kernel.org/linux-s390/20210615114150.325080-1-dimitri.led...@canonical.com/T/#u

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1931725/+subscriptions

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

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

2021-06-24 Thread Hui Wang

you installed 20.04 on your machine, but the kernel version in your log
is 5.11.0-generic, how did you install the 5.11 kernel under 20.04, I
remember it is 5.8 kernel under 20.04 if you run update.

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

Title:
  Audio Problem, soundcard not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hi,

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

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

  My GPU is an GTX 1080 Ti.

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

  Before the last update of Ubuntu, all worked well.

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

  Regards.

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

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

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

[Touch-packages] [Bug 1933491] Re: kmod add zstd support

This bug was fixed in the package kmod - 28-1ubuntu4

---
kmod (28-1ubuntu4) impish; urgency=medium

  * Enable testsuite during build.

kmod (28-1ubuntu3) impish; urgency=medium

  * Build with zstd compression enabled. LP: #1933491

 -- Dimitri John Ledkov   Thu, 24 Jun 2021
13:42:47 +0100

** Changed in: kmod (Ubuntu)
   Status: New => Fix Released

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

Title:
  kmod add zstd support

Status in kmod package in Ubuntu:
  Fix Released

Bug description:
  kmod add zstd support

  * v27+ needs patches cherrypicked from v28

  * v28+ needs new build-time deps adjusted

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1933491/+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 1932022] Re: Can you add the btvirt executable to bluez-tests?

This bug was fixed in the package bluez - 5.59-0ubuntu1

---
bluez (5.59-0ubuntu1) impish; urgency=medium

  * New upstream release 5.59 (LP: #1933078):
- Fix issue with string to UUID-32 conversion.
- Fix issue with connect request if SDP search failed.
- Fix issue with accepting invalid AVDTP capabilities.
- Fix issue with unregister handling of AVRCP player.
  * Add new build-dep 'python3-docutils' required for rst2man.
  * Add new package 'bluez-meshd' and --enable-mesh (LP: #1929833).
- Requires new build-dep 'libjson-c-dev'.
  * Cleanups from upstream debian:
- Remove empty packages 'libbluetooth3-dbg' and 'bluez-dbg'.
- Lots of benign formatting changes in debian/control to shrink the diff.
  * Add binaries 'b1ee', 'btvirt', 'hfp' to 'bluez-tests' (LP: #1932022).
  * Add binary 'avinfo' to 'bluez' (LP: #1907886).
  * Add patch Fix-reading-from-rfkill-socket.patch to resolve Bluetooth
on/off toggle issues with newer kernel versions (LP: #1926062).

 -- Daniel van Vugt   Mon, 21 Jun 2021
17:02:38 +0800

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

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

Title:
  Can you add the btvirt executable to bluez-tests?

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  See the Debian package: https://packages.debian.org/buster/i386/bluez-
  test-tools/filelist

  The Ubuntu package contains the same tools, except for btvirt. Would
  it be possible to add this? The buildlog shows that the btvirt
  executable is already built, but just not put into the *.deb package.

  Additions to be done to debian/bluez-tests.install:

  emulator/b1ee usr/bin
  emulator/btvirt usr/bin
  emulator/hfp usr/bin

  Having the btvirt tool available will make testing on CI systems a lot
  easier.

  References:
  https://github.com/hadess/bluez/blob/master/Makefile.tools#L76-L82
  https://answers.launchpad.net/ubuntu/+source/bluez/+question/697542

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1932022/+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 1929833] Re: bluez: meshctl missing

This bug was fixed in the package bluez - 5.59-0ubuntu1

---
bluez (5.59-0ubuntu1) impish; urgency=medium

  * New upstream release 5.59 (LP: #1933078):
- Fix issue with string to UUID-32 conversion.
- Fix issue with connect request if SDP search failed.
- Fix issue with accepting invalid AVDTP capabilities.
- Fix issue with unregister handling of AVRCP player.
  * Add new build-dep 'python3-docutils' required for rst2man.
  * Add new package 'bluez-meshd' and --enable-mesh (LP: #1929833).
- Requires new build-dep 'libjson-c-dev'.
  * Cleanups from upstream debian:
- Remove empty packages 'libbluetooth3-dbg' and 'bluez-dbg'.
- Lots of benign formatting changes in debian/control to shrink the diff.
  * Add binaries 'b1ee', 'btvirt', 'hfp' to 'bluez-tests' (LP: #1932022).
  * Add binary 'avinfo' to 'bluez' (LP: #1907886).
  * Add patch Fix-reading-from-rfkill-socket.patch to resolve Bluetooth
on/off toggle issues with newer kernel versions (LP: #1926062).

 -- Daniel van Vugt   Mon, 21 Jun 2021
17:02:38 +0800

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

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

Title:
  bluez: meshctl missing

Status in bluez package in Ubuntu:
  Fix Released
Status in bluez package in Debian:
  Fix Released

Bug description:
  bluez has added a new tool for BT mesh handling.

  Debian has a new binary package: https://packages.debian.org/bullseye
  /bluez-meshd

  Debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=973579

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1929833/+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 1933078] Re: BlueZ 5.59 release

This bug was fixed in the package bluez - 5.59-0ubuntu1

---
bluez (5.59-0ubuntu1) impish; urgency=medium

  * New upstream release 5.59 (LP: #1933078):
- Fix issue with string to UUID-32 conversion.
- Fix issue with connect request if SDP search failed.
- Fix issue with accepting invalid AVDTP capabilities.
- Fix issue with unregister handling of AVRCP player.
  * Add new build-dep 'python3-docutils' required for rst2man.
  * Add new package 'bluez-meshd' and --enable-mesh (LP: #1929833).
- Requires new build-dep 'libjson-c-dev'.
  * Cleanups from upstream debian:
- Remove empty packages 'libbluetooth3-dbg' and 'bluez-dbg'.
- Lots of benign formatting changes in debian/control to shrink the diff.
  * Add binaries 'b1ee', 'btvirt', 'hfp' to 'bluez-tests' (LP: #1932022).
  * Add binary 'avinfo' to 'bluez' (LP: #1907886).
  * Add patch Fix-reading-from-rfkill-socket.patch to resolve Bluetooth
on/off toggle issues with newer kernel versions (LP: #1926062).

 -- Daniel van Vugt   Mon, 21 Jun 2021
17:02:38 +0800

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

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

Title:
  BlueZ 5.59 release

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  Release BlueZ 5.59 to impish.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1933078/+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 1907886] Re: avinfo is missing

This bug was fixed in the package bluez - 5.59-0ubuntu1

---
bluez (5.59-0ubuntu1) impish; urgency=medium

  * New upstream release 5.59 (LP: #1933078):
- Fix issue with string to UUID-32 conversion.
- Fix issue with connect request if SDP search failed.
- Fix issue with accepting invalid AVDTP capabilities.
- Fix issue with unregister handling of AVRCP player.
  * Add new build-dep 'python3-docutils' required for rst2man.
  * Add new package 'bluez-meshd' and --enable-mesh (LP: #1929833).
- Requires new build-dep 'libjson-c-dev'.
  * Cleanups from upstream debian:
- Remove empty packages 'libbluetooth3-dbg' and 'bluez-dbg'.
- Lots of benign formatting changes in debian/control to shrink the diff.
  * Add binaries 'b1ee', 'btvirt', 'hfp' to 'bluez-tests' (LP: #1932022).
  * Add binary 'avinfo' to 'bluez' (LP: #1907886).
  * Add patch Fix-reading-from-rfkill-socket.patch to resolve Bluetooth
on/off toggle issues with newer kernel versions (LP: #1926062).

 -- Daniel van Vugt   Mon, 21 Jun 2021
17:02:38 +0800

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

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

Title:
  avinfo is missing

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  The "avinfo" command line tools available in bluez/tools
  (https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/tools) is not
  available in the package.

  The package bluez-tools (https://packages.ubuntu.com/groovy/bluez-
  tools) seems to map another project external to bluez
  (https://github.com/khvzak/bluez-tools) and not the "tools" folder of
  bluez.

  "avinfo" is used for example in order to check which codecs are
  supported by a headphone set (see https://github.com/EHfive
  /pulseaudio-modules-bt/issues/31#issuecomment-462717049).

  Maybe have "bluez-tools" map the "tools" folder of bluez, and move the
  other project to another package?

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

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

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