[Touch-packages] [Bug 2039235] Re: gnome-online-accounts -> when signing into google account, infinite loading after entering password

[Rafael Rodrigues Marquesi]

I had the same problem. I followed the instructions of Nathan Vaughn
(nathanvme) and it worked for me. Thanks.

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

Title:
  gnome-online-accounts -> when signing into google account, infinite
  loading after entering password

Status in gnome-online-accounts package in Ubuntu:
  Confirmed

Bug description:
  1) What you expected to happen
  - sign in is successful, which will allow google services to populate the 
appropriate applications (calendar, mail, google drive)

  2) What actually happened
  - sign in hangs infinitely after entering the password
  - the process is able to detect that the password is correct or incorrect. 
When entering an incorrect password, it will correctly and quickly complain 
that the password is incorrect. When entering the correct password, the bug 
will occur.

  3) Steps to reproduce
    a) start the program
    b) select online accounts
    c) select google
    d) enter email
    e) enter password
    f) loads forever

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-online-accounts 3.48.0-2
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 12 22:27:59 2023
  InstallationDate: Installed on 2023-10-12 (0 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-online-accounts
  UpgradeStatus: No upgrade log present (probably fresh install)

  Hardware info (not sure if relevant):
  cpu: intel
  gpu: nvidia (driver version: "Using NVIDIA driver metapackage from 
nvidia-driver-535(proprietary, tested)")

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/2039235/+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 2009544] Re: OpenSSL 3 performance regression

[Rafael Lopez]

Tested some additional patches, including [1] (PR linked in bug desc)
plus [2] and [3]. PPAs for each at [4], [5] and [6]. All tests on same
hardware and VM 8vcpu/4G.

Baseline:
ubuntu@openssl-jammy:~/openssl_python_ubuntu$ for i in {0..4};do /usr/bin/time 
-f "Real: %e  User: %U" python3 main.py > /dev/null;done
Real: 13.62  User: 24.44
Real: 13.84  User: 22.89
Real: 14.12  User: 23.71
Real: 13.72  User: 23.94
Real: 13.42  User: 24.31
ubuntu@openssl-jammy:~/openssl_python_ubuntu$

PR#18151[1]
ubuntu@openssl-jammy:~/openssl_python_ubuntu$ for i in {0..4};do /usr/bin/time 
-f "Real: %e  User: %U" python3 main.py > /dev/null;done
Real: 3.20  User: 13.89
Real: 2.43  User: 15.29
Real: 2.72  User: 14.88
Real: 2.77  User: 14.56
Real: 2.43  User: 15.46
ubuntu@openssl-jammy:~/openssl_python_ubuntu$


PR#18151[1] + PR#17881[2]
ubuntu@openssl-jammy:~/openssl_python_ubuntu$ for i in {0..4};do /usr/bin/time 
-f "Real: %e  User: %U" python3 main.py > /dev/null;done
Real: 2.02  User: 7.92
Real: 1.93  User: 7.87
Real: 1.89  User: 7.88
Real: 2.09  User: 8.46
Real: 1.89  User: 7.80
ubuntu@openssl-jammy:~/openssl_python_ubuntu$


PR#18151[1] + PR#17921[3]
ubuntu@openssl-jammy:~/openssl_python_ubuntu$ for i in {0..4};do /usr/bin/time 
-f "Real: %e  User: %U" python3 main.py > /dev/null;done
Real: 1.64  User: 5.30
Real: 1.74  User: 6.08
Real: 1.74  User: 5.80
Real: 1.69  User: 6.50
Real: 1.70  User: 5.68
ubuntu@openssl-jammy:~/openssl_python_ubuntu$


PR#18151[1] + PR#17881[2] + PR#17921[3]
ubuntu@openssl-jammy:~/openssl_python_ubuntu$ for i in {0..4};do /usr/bin/time 
-f "Real: %e  User: %U" python3 main.py > /dev/null;done
Real: 1.55  User: 3.79
Real: 1.64  User: 3.78
Real: 1.86  User: 4.36
Real: 1.73  User: 3.81
Real: 1.81  User: 3.72
ubuntu@openssl-jammy:~/openssl_python_ubuntu$


[1] https://github.com/openssl/openssl/pull/18151
[2] https://github.com/openssl/openssl/pull/17881
[3] https://github.com/openssl/openssl/pull/17921
[4] https://launchpad.net/~rafael.lopez/+archive/ubuntu/lp2009544
[5] https://launchpad.net/~rafael.lopez/+archive/ubuntu/lp2009544-2
[6] https://launchpad.net/~rafael.lopez/+archive/ubuntu/lp2009544-3

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

Title:
  OpenSSL 3 performance regression

Status in openssl package in Ubuntu:
  Confirmed

Bug description:
  Hello, it sounds like there's some significant performance regressions
  in OpenSSL 3:

  https://github.com/openssl/openssl/issues/20286#issuecomment-1438826816

  Some we might be able to address with:
  https://github.com/openssl/openssl/pull/18151

  Some of the performance differences may be subject to ongoing work.

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2009544/+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 2009544] Re: OpenSSL 3 performance regression

[Rafael Lopez]

Hi Adrien, see results below - lunar and mantic show similar
performance, both a significant improvement over jammy. All tests were
run using same underlying hardware, 8vcpu/4G VMs.

ubuntu@openssl-jammy:~/openssl_python_ubuntu$ time python3 main.py
Distro: Ubuntu 22.04.3 LTS
Python Version: 3.10.12 (main, Jun 11 2023, 05:26:28) [GCC 11.4.0]
OpenSSL Version: OpenSSL 3.0.2 15 Mar 2022
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 
30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 
56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 
82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
real0m12.751s
user0m20.992s
sys 0m9.746s
ubuntu@openssl-jammy:~/openssl_python_ubuntu$ for i in {0..4};do /usr/bin/time 
-f "Elapsed: %e" python3 main.py > /dev/null;done
Elapsed: 11.76
Elapsed: 12.43
Elapsed: 11.52
Elapsed: 11.92
Elapsed: 12.68
ubuntu@openssl-jammy:~/openssl_python_ubuntu$


ubuntu@openssl-lunar:~/openssl_python_ubuntu$ time python3 main.py
Distro: Ubuntu 23.04
Python Version: 3.11.2 (main, May 30 2023, 17:45:26) [GCC 12.2.0]
OpenSSL Version: OpenSSL 3.0.8 7 Feb 2023
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 
30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 
56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 
82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
real0m2.313s
user0m13.487s
sys 0m0.208s
ubuntu@openssl-lunar:~/openssl_python_ubuntu$ for i in {0..4};do /usr/bin/time 
-f "Elapsed: %e" python3 main.py > /dev/null;done
Elapsed: 2.93
Elapsed: 2.56
Elapsed: 2.39
Elapsed: 2.32
Elapsed: 2.56
ubuntu@openssl-lunar:~/openssl_python_ubuntu$


ubuntu@openssl-mantic:~/openssl_python_ubuntu$ time python3 main.py
Distro: Ubuntu Mantic Minotaur (development branch)
Python Version: 3.11.4 (main, Jun  7 2023, 10:13:09) [GCC 12.3.0]
OpenSSL Version: OpenSSL 3.0.10 1 Aug 2023
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 
30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 
56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 
82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99
real0m2.838s
user0m15.380s
sys 0m0.244s
ubuntu@openssl-mantic:~/openssl_python_ubuntu$ for i in {0..4};do /usr/bin/time 
-f "Elapsed: %e" python3 main.py > /dev/null;done
Elapsed: 2.44
Elapsed: 2.29
Elapsed: 2.63
Elapsed: 2.36
Elapsed: 2.39
ubuntu@openssl-mantic:~/openssl_python_ubuntu$

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

Title:
  OpenSSL 3 performance regression

Status in openssl package in Ubuntu:
  Confirmed

Bug description:
  Hello, it sounds like there's some significant performance regressions
  in OpenSSL 3:

  https://github.com/openssl/openssl/issues/20286#issuecomment-1438826816

  Some we might be able to address with:
  https://github.com/openssl/openssl/pull/18151

  Some of the performance differences may be subject to ongoing work.

  Thanks

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2009544/+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 1988364] Re: Missing the A2DP profile and defaults to low quality

[Rafael K.]

I just removed my WF-1000XM4 from my device list and paired them again.
Now I have "High Fidelity Playback (A2DP Sink, codec LDAC)" and it was selected 
by default.

I have no idea what changed. bluez is still 5.64 since 2022-08-28. Maybe
it's related to the blueman update from 2.3.4 to 2.3.5 on 2023-01-19 or
some pipewire update on 2023-01-12.

These are my current bluez related packages:
bluez-alsa-utils/jammy 3.0.0-2 amd64
bluez-btsco/jammy 1:0.50-0ubuntu7 amd64
bluez-cups/jammy,now 5.64-0ubuntu1 amd64 [installed]
bluez-firmware/jammy,jammy 1.2-7 all
bluez-hcidump/jammy 5.64-0ubuntu1 amd64
bluez-hcidump/jammy 5.64-0ubuntu1 i386
bluez-meshd/jammy 5.64-0ubuntu1 amd64
bluez-meshd/jammy 5.64-0ubuntu1 i386
bluez-obexd/jammy,now 5.64-0ubuntu1 amd64 [installed]
bluez-obexd/jammy 5.64-0ubuntu1 i386
bluez-tests/jammy 5.64-0ubuntu1 amd64
bluez-tests/jammy 5.64-0ubuntu1 i386
bluez-tools/jammy,now 2.0~20170911.0.7cb788c-4 amd64 [installed]
bluez/jammy,now 5.64-0ubuntu1 amd64 [installed]
bluez/jammy 5.64-0ubuntu1 i386
libasound2-plugin-bluez/jammy 3.0.0-2 amd64
libkf5bluezqt-data/jammy,jammy 5.92.0-0ubuntu1 all
libkf5bluezqt-dev/jammy 5.92.0-0ubuntu1 amd64
libkf5bluezqt-doc/jammy,jammy 5.92.0-0ubuntu1 all
libkf5bluezqt6/jammy 5.92.0-0ubuntu1 amd64
python3-bluez/jammy 0.23-4build1 amd64
qml-module-org-kde-bluezqt/jammy 5.92.0-0ubuntu1 amd64

So it seems it's somehow unrelated to bluez 5.65

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

Title:
  Missing the A2DP profile and defaults to low quality

Status in Bluez Utilities:
  Fix Released
Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Jammy:
  In Progress
Status in bluez source package in Kinetic:
  Fix Released
Status in bluez source package in Lunar:
  Fix Released

Bug description:
  [ Impact ]

  Sony WH-1000XM4 missing the A2DP profile and defaults to low quality.
  Probably other headphone types would be affected too.

  https://github.com/bluez/bluez/issues/313

  [ Test Plan ]

  No verifiable test case yet. Will ask the community for testing, and
  if it fails then consider reverting the fix.

  [ Where problems could occur ]

  The fix touches Bluetooth audio logic (only). So anything relating to
  Bluetooth audio (A2DP) is the main risk. A secondary risk is the rest
  of bluetoothd which could suffer side effects.

  [ Other Info ]

  None provided.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/1988364/+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 1980937] Re: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] No sound except loud crackling (popping) noise

[Rafael Filipe Ferreirinha Cardoso]

I'm running on Ubuntu 22.04, kernel 5.15.0-60-generic and this still
happens.

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

Title:
  [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal]
  No sound except loud crackling (popping) noise

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  New laptop with fresh installation of Xubuntu 22.04. Intel Tiger Lake-
  LP audio controller. When playing any audio, the internal speaker
  plays no sound except periodic loud crackling noise. The 3.5mm jack
  does not work either, producing the same craclking noise alongside
  some eletrical noise. HDMI audio skimmishly tested, but also gave no
  sound. Curiously, USB headphone (along with microphone) works
  perfectly, also the internal microphone.

  As attempts to fix the problem, I have tried the following separately, with 
no avail:
  - Installing some Ubuntu OEM version of the 5.17 kernel
  - Updating to the v2.2 firmware from Sound Open Firmware Project 
(thesofproject on github), reverted afterwards

  I found exactly the same problem reported in the Fedora community:
  
https://forums.fedoraforum.org/showthread.php?328627-HP-Elitebook-840-G8-Tiger-Lake-audio-only-produces-popping-sound=1860086

  As the pre-installed Windows has been destroyed, no further test on
  Windows has been done.

  Since USB headphone and internal microphone work, I think that there
  is no problem on the Intel Tiger Lake-LP controller and its driver.
  The bug probably lies elsewhere, like in the handling of ALC245 on
  this new laptop model.

  Thank you very much for your time and effort in advance.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
  Uname: Linux 5.15.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fwjmath2810 F pulseaudio
fwjmath   72467 F alsamixer
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Thu Jul  7 10:59:22 2022
  InstallationDate: Installed on 2022-06-29 (7 days ago)
  InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed
  Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - 
sof-hda-dsp
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fwjmath2810 F pulseaudio
fwjmath   72467 F alsamixer
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] 
No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/05/2022
  dmi.bios.release: 9.1
  dmi.bios.vendor: HP
  dmi.bios.version: T37 Ver. 01.09.01
  dmi.board.name: 8AB8
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 58.03.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 88.3
  dmi.modalias: 
dmi:bvnHP:bvrT37Ver.01.09.01:bd05/05/2022:br9.1:efr88.3:svnHP:pnHPEliteBook840G8NotebookPC:pvr:rvnHP:rn8AB8:rvrKBCVersion58.03.00:cvnHP:ct10:cvr:sku6A3P3AV:
  dmi.product.family: 103C_5336AN HP EliteBook
  dmi.product.name: HP EliteBook 840 G8 Notebook PC
  dmi.product.sku: 6A3P3AV
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-07-02T17:07:35.783239

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1980937/+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 1980937] Re: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] No sound except loud crackling (popping) noise

[Rafael Filipe Ferreirinha Cardoso]

Hello,

I'm having the same problem on a HP ENVY x360 2-in-1 Laptop 15-ew0xxx.

The internal speaker doesn't reproduce any sound but I can use my
headset and headphone jack.

If any info is needed please do tell.

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

Title:
  [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal]
  No sound except loud crackling (popping) noise

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  New laptop with fresh installation of Xubuntu 22.04. Intel Tiger Lake-
  LP audio controller. When playing any audio, the internal speaker
  plays no sound except periodic loud crackling noise. The 3.5mm jack
  does not work either, producing the same craclking noise alongside
  some eletrical noise. HDMI audio skimmishly tested, but also gave no
  sound. Curiously, USB headphone (along with microphone) works
  perfectly, also the internal microphone.

  As attempts to fix the problem, I have tried the following separately, with 
no avail:
  - Installing some Ubuntu OEM version of the 5.17 kernel
  - Updating to the v2.2 firmware from Sound Open Firmware Project 
(thesofproject on github), reverted afterwards

  I found exactly the same problem reported in the Fedora community:
  
https://forums.fedoraforum.org/showthread.php?328627-HP-Elitebook-840-G8-Tiger-Lake-audio-only-produces-popping-sound=1860086

  As the pre-installed Windows has been destroyed, no further test on
  Windows has been done.

  Since USB headphone and internal microphone work, I think that there
  is no problem on the Intel Tiger Lake-LP controller and its driver.
  The bug probably lies elsewhere, like in the handling of ALC245 on
  this new laptop model.

  Thank you very much for your time and effort in advance.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
  Uname: Linux 5.15.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fwjmath2810 F pulseaudio
fwjmath   72467 F alsamixer
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Thu Jul  7 10:59:22 2022
  InstallationDate: Installed on 2022-06-29 (7 days ago)
  InstallationMedia: Xubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed
  Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - 
sof-hda-dsp
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fwjmath2810 F pulseaudio
fwjmath   72467 F alsamixer
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [HP EliteBook 840 G8 Notebook PC, Realtek ALC245, Speaker, Internal] 
No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/05/2022
  dmi.bios.release: 9.1
  dmi.bios.vendor: HP
  dmi.bios.version: T37 Ver. 01.09.01
  dmi.board.name: 8AB8
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 58.03.00
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.ec.firmware.release: 88.3
  dmi.modalias: 
dmi:bvnHP:bvrT37Ver.01.09.01:bd05/05/2022:br9.1:efr88.3:svnHP:pnHPEliteBook840G8NotebookPC:pvr:rvnHP:rn8AB8:rvrKBCVersion58.03.00:cvnHP:ct10:cvr:sku6A3P3AV:
  dmi.product.family: 103C_5336AN HP EliteBook
  dmi.product.name: HP EliteBook 840 G8 Notebook PC
  dmi.product.sku: 6A3P3AV
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-07-02T17:07:35.783239

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1980937/+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 1988364] Re: Missing the A2DP profile and defaults to low quality

[Rafael K.]

IIRC I tried to install it from source back then, but had missing build
dependencies (or versions) which were not in the package repositories. I
could be wrong, though.

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

Title:
  Missing the A2DP profile and defaults to low quality

Status in Bluez Utilities:
  Fix Released
Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Jammy:
  In Progress
Status in bluez source package in Kinetic:
  Fix Released
Status in bluez source package in Lunar:
  Fix Released

Bug description:
  [ Impact ]

  Sony WH-1000XM4 missing the A2DP profile and defaults to low quality.
  Probably other headphone types would be affected too.

  https://github.com/bluez/bluez/issues/313

  [ Test Plan ]

  ANYONE AFFECTED BY THE BUG PLEASE FILL THIS IN

  [ Where problems could occur ]

  The fix touches Bluetooth audio logic (only). So anything relating to
  Bluetooth audio (A2DP) is the main risk. A secondary risk is the rest
  of bluetoothd which could suffer side effects.

  [ Other Info ]

  None provided.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/1988364/+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 1988364] Re: Missing the A2DP profile and defaults to low quality

[Rafael K.]

Hmm, currently when connecting it via blueman it automatically connects with 
the last used profile. 
I just saw it says "High Fidelity Playback (A2DP sink, codec SBC-XQ)". So it 
seems to have A2DP there.
But as soon as I change my Mic Input Device to my headphones it changes to 
"Headset Head Unit (HSP/HFP codec mSBC)". If try to change the profile back to 
the A2DP sink my input device is also switched back to my internal Laptop Mic.

I'm not sure anymore if the A2DP sink was always there or if came back with a 
recent OS update (Linux Mint 21.1) - I'm also not sure if bluez 5.65 can fix 
this behavior.
Is there a more or less easy way I can test this on my machine? Maybe just 
clone it from the GitHub repo, checkout 5.65, compile and install it? Or do I 
need additional steps?

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

Title:
  Missing the A2DP profile and defaults to low quality

Status in Bluez Utilities:
  Fix Released
Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Jammy:
  In Progress
Status in bluez source package in Kinetic:
  Fix Released
Status in bluez source package in Lunar:
  Fix Released

Bug description:
  [ Impact ]

  Sony WH-1000XM4 missing the A2DP profile and defaults to low quality.
  Probably other headphone types would be affected too.

  https://github.com/bluez/bluez/issues/313

  [ Test Plan ]

  ANYONE AFFECTED BY THE BUG PLEASE FILL THIS IN

  [ Where problems could occur ]

  The fix touches Bluetooth audio logic (only). So anything relating to
  Bluetooth audio (A2DP) is the main risk. A secondary risk is the rest
  of bluetoothd which could suffer side effects.

  [ Other Info ]

  None provided.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/1988364/+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 1988364] Re: Missing the A2DP profile and defaults to low quality

[Rafael K.]

Hey @vanvugt, is there maybe any ETA?

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

Title:
  Missing the A2DP profile and defaults to low quality

Status in Bluez Utilities:
  Fix Released
Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  Sony WH-1000XM4 missing the A2DP profile and defaults to low quality

  https://github.com/bluez/bluez/issues/313

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/1988364/+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 1951491] Re: Can't run snaps: .slice/session-1.scope is not a snap cgroup

[Rafael Alves]

Yeah, I know my answer dont solve this issue. But, if you cant wait for
a fix, like me, you can try install chrome without snap. In my case I
thought it was impossible, cause I was running ubuntu 22.04 in a ARM
instance. But after remove the snap version and install a deb version I
found peace and my webscrapping is working fine now.

Follow this link to install deb version oc chromium:
https://fosspost.org/chromium-deb-package-ubuntu-22-04/

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

Title:
  Can't run snaps: .slice/session-1.scope is not a snap cgroup

Status in X2Go:
  New
Status in Xpra Terminal Server:
  New
Status in snapd package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Incomplete
Status in x2goserver package in Ubuntu:
  Confirmed
Status in snapd package in Debian:
  New

Bug description:
  I just upgraded from hirsute to impish using do-release-upgrade. On
  the upgraded system, I can't run either firefox or chromium (both of
  which worked fine under hirsute). Both fail with:

  /user.slice/user-NNN.slice/session-1.scope is not a snap cgroup where
  NNN is my uid

  With firefox, I was able to fix the problem with:

  snap remove --purge firefox
  apt purge firefox
  apt install firefox

  Now firefox works. But I tried the same thing substituting chromium-
  browser for firefox, and it didn't help: chromium fails with the same
  error message.

  I guess there must be something left over from the hirsute version of
  snapd that isn't getting noticed or cleared by the impish version?

  Someone suggested this might be related to bug 1850667, but that bug
  is marked fixed as of a couple months ago, and I just did this upgrade
  today. Also, it doesn't mention the error message I'm seeing.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: snapd 2.53+21.10ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
  Uname: Linux 5.13.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Thu Nov 18 18:12:45 2021
  InstallationDate: Installed on 2020-04-29 (568 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: snapd
  UpgradeStatus: Upgraded to impish on 2021-11-18 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/x2go/+bug/1951491/+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 1988364] Re: Missing the A2DP profile and defaults to low quality

[Rafael K.]

Thanks, good to know :) At least you are listening :P

Do you know about any updates on this topic?

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

Title:
  Missing the A2DP profile and defaults to low quality

Status in Bluez Utilities:
  Fix Released
Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  Sony WH-1000XM4 missing the A2DP profile and defaults to low quality

  https://github.com/bluez/bluez/issues/313

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/1988364/+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 1988364] Re: Missing the A2DP profile and defaults to low quality

[Rafael K.]

Thanks for clarifying, that makes sense now.

Actually I just wanted to thank you, if there would be reactions to
comments that would be great for that. But as I'm writing this comment
now I got one other question: In the sidebar I see many people being
listed under "May be notified". And I'm very sorry if all people listed
there now receive an email because of this comment,  I'm already feeling
a bit guilty writing it just because I wanted to thank Daniel. But what
does "May be notified" mean? Are there going emails out to everyone
there?

Edit: Is there maybe a "Getting Started with Launchpad", maybe even
specific to Ubuntu?

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

Title:
  Missing the A2DP profile and defaults to low quality

Status in Bluez Utilities:
  Fix Released
Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  Sony WH-1000XM4 missing the A2DP profile and defaults to low quality

  https://github.com/bluez/bluez/issues/313

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/1988364/+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 1988364] Re: Missing the A2DP profile and defaults to low quality

[Rafael K.]

But now it looks like a fix is released, no? Sorry, I'm still new to
launchpad and not everything is obvious to me yet.

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

Title:
  Missing the A2DP profile and defaults to low quality

Status in Bluez Utilities:
  Fix Released
Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  Sony WH-1000XM4 missing the A2DP profile and defaults to low quality

  https://github.com/bluez/bluez/issues/313

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/1988364/+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 1988364] Re: Missing the A2DP profile and defaults to low quality

[Rafael K.]

@vanvugt Thank you very much for opening this bug and everyone else for
the quick fix!

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

Title:
  Missing the A2DP profile and defaults to low quality

Status in Bluez Utilities:
  Fix Released
Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Jammy:
  Triaged

Bug description:
  Sony WH-1000XM4 missing the A2DP profile and defaults to low quality

  https://github.com/bluez/bluez/issues/313

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/1988364/+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 1982739] Re: BlueZ 5.65 release

[Rafael K.]

Will this also be released for jammy soon?

I'm running into this issue which should be fixed with 5.65:
https://github.com/bluez/bluez/issues/313

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

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

Title:
  BlueZ 5.65 release

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  Release BlueZ 5.65 to kinetic:

  https://mirrors.edge.kernel.org/pub/linux/bluetooth/bluez-5.65.tar.xz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1982739/+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 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog

[Rafael Medina]

What's happening here is exactly what is mentioned in this Gnome gtk
bug: https://gitlab.gnome.org/GNOME/gtk/-/issues/5087

** Bug watch added: gitlab.gnome.org/GNOME/gtk/-/issues #5087
   https://gitlab.gnome.org/GNOME/gtk/-/issues/5087

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

Title:
  [upstream] Saving downloads or pages is difficult because of unfocused
  file chooser dialog

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in gtk4 package in Ubuntu:
  Confirmed
Status in xdg-desktop-portal-gnome package in Ubuntu:
  Confirmed
Status in xdg-desktop-portal-gtk package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Open Chromium (release does not matter, here deb-packaged version from 
18.04 LTS is used)
  2a. Navigate to some page, press +
  2b. Navigate to some page, with "Ask where to save each file before 
downloading" enabled try to download some file

  Actual result:
  * file chooser dialog is unfocused, user should select the window by mouse 
and then hit  for specified location

  Expected result:
  * file chooser dialog is focused, user can simply hit  to save in 
previously selected location.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1949340/+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 1949340] Re: [upstream] Saving downloads or pages is difficult because of unfocused file chooser dialog

[Rafael Medina]

Ubuntu 22.04.1 LTS x86_64
gnome-flashback: 3.44.0-1ubuntu2
Kernel: 5.19.1

It only happens with Firefox (snap version installed here) and Google Chrome.
Firefox snap:  103.0.2 
Google Chrome: 104.0.5112.79

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

Title:
  [upstream] Saving downloads or pages is difficult because of unfocused
  file chooser dialog

Status in chromium-browser package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in gtk4 package in Ubuntu:
  Confirmed
Status in xdg-desktop-portal-gnome package in Ubuntu:
  Confirmed
Status in xdg-desktop-portal-gtk package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Open Chromium (release does not matter, here deb-packaged version from 
18.04 LTS is used)
  2a. Navigate to some page, press +
  2b. Navigate to some page, with "Ask where to save each file before 
downloading" enabled try to download some file

  Actual result:
  * file chooser dialog is unfocused, user should select the window by mouse 
and then hit  for specified location

  Expected result:
  * file chooser dialog is focused, user can simply hit  to save in 
previously selected location.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1949340/+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 1951877] Re: FTBFS - python-testtools does not support Python 3.10

[Rafael David Tinoco]

I've used your git-ubuntu branch to generate the source package and
upload it. You (server team) will have to break this merge into the 3
commits again during next merge with upstream (debian) as I did not have
permission to upload to pkg/ubuntu/devel (not sure why).

$ dput ubuntu python-testtools_2.5.0-2ubuntu1_source.changes
D: Setting host argument.
Checking signature on .changes
gpg: 
/home/rafaeldtinoco/work/sources/ubuntu/jammy/python-testtools_2.5.0-2ubuntu1_source.changes:
 Valid signature from A93E0E0AD83C0D0F
Checking signature on .dsc
gpg: 
/home/rafaeldtinoco/work/sources/ubuntu/jammy/python-testtools_2.5.0-2ubuntu1.dsc:
 Valid signature from A93E0E0AD83C0D0F
Uploading to ubuntu (via ftp to upload.ubuntu.com):
  Uploading python-testtools_2.5.0-2ubuntu1.dsc: done.
  Uploading python-testtools_2.5.0-2ubuntu1.debian.tar.xz: done.
  Uploading python-testtools_2.5.0-2ubuntu1_source.buildinfo: done.
  Uploading python-testtools_2.5.0-2ubuntu1_source.changes: done.
Successfully uploaded packages.

Please follow migration to check if it migrates good, let me know
otherwise.

PS: I have "quilt refreshed" your patch to avoid hunks (in the other SRU
proposal as well). Make sure your patches apply clean wen you suggest a
merge/fix. Thanks!

** Changed in: python-testtools (Ubuntu)
   Status: New => In Progress

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

Title:
  FTBFS - python-testtools does not support Python 3.10

Status in python-testtools package in Ubuntu:
  In Progress

Bug description:
  As shown in

  https://launchpadlibrarian.net/569859852/buildlog_ubuntu-jammy-
  amd64.python-testtools_2.5.0-2_BUILDING.txt.gz

  python-testtools does not support Python 3.10, and FTBFS for jammy.

  + PYTHONPATH=/<> PYTHON=python3.10 python3.10 -m testtools.run 
testtools.tests.test_suite
  /usr/lib/python3.10/runpy.py:126: RuntimeWarning: 'testtools.run' found in 
sys.modules after import of package 'testtools', but prior to execution of 
'testtools.run'; this may result in unpredictable behaviour
warn(RuntimeWarning(msg))
  No entry for terminal type "unknown";
  using dumb terminal settings.
  Tests running...
  ==
  FAIL: testtools.tests.test_testresult.TestNonAsciiResults.test_syntax_error
  --
  Traceback (most recent call last):
File "/<>/testtools/tests/test_testresult.py", line 2676, in 
test_syntax_error
  self.assertIn(self._as_output(
File "/<>/testtools/testcase.py", line 399, in assertIn
  self.assertThat(haystack, Contains(needle), message)
File "/<>/testtools/testcase.py", line 480, in assertThat
  raise mismatch_error
  testtools.matchers._impl.MismatchError: '  File "", line 1\nf(a, 
b c)\n ^\nSyntaxError: ' not in 'Tests 
running...\n==\nERROR:
 
test_syntax_error.Test.runTest\n--\nTraceback
 (most recent call last):\n  File 
"/tmp/TestNonAsciiResultsa_jvxgt3/test_syntax_error.py", line 6, in runTest\n   
 exec (\'f(a, b c)\')\n  File "", line 1\nf(a, b c)\n 
^^^\nSyntaxError: invalid syntax. Perhaps you forgot a comma?\n\nRan 1 test in 
0.001s\nFAILED (failures=1)\n'
  ==
  FAIL: 
testtools.tests.test_testresult.TestNonAsciiResultsWithUnittest.test_syntax_error
  --
  Traceback (most recent call last):
File "/<>/testtools/tests/test_testresult.py", line 2676, in 
test_syntax_error
  self.assertIn(self._as_output(
File "/<>/testtools/testcase.py", line 399, in assertIn
  self.assertThat(haystack, Contains(needle), message)
File "/<>/testtools/testcase.py", line 480, in assertThat
  raise mismatch_error
  testtools.matchers._impl.MismatchError: '  File "", line 1\nf(a, 
b c)\n ^\nSyntaxError: ' not in 
'E\n==\nERROR:
 runTest 
(test_syntax_error.Test)\ntest_syntax_error.Test.runTest\n--\ntesttools.testresult.real._StringException:
 Traceback (most recent call last):\n  File 
"/tmp/TestNonAsciiResultsWithUnittest3zrnkc8g/test_syntax_error.py", line 6, in 
runTest\nexec (\'f(a, b c)\')\n  File "", line 1\nf(a, b c)\n   
  ^^^\nSyntaxError: invalid syntax. Perhaps you forgot a 
comma?\n\n\n--\nRan
 1 test in 0.000s\n\nFAILED (errors=1)\n'

  Ran 2625 tests in 1.221s
  FAILED (failures=2)
  make[1]: *** [debian/rules:36: override_dh_auto_test] Error 1

[Touch-packages] [Bug 1946475] Re: USB support in intram broken for raspberry 4 after udpate

[Rafael]

the kernel reported by the system in ramdisk is: 5.3.0-1038-raspi2
#40-Ubuntu SMP Mon Mar 22 13:45:02 UTC 2021 aarch64 GNU/Linux

In case that helps.

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

Title:
  USB support in intram broken for raspberry 4 after udpate

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Hi,

  I have a Raspberry PI 4 running Ubuntu 18.04.

  Recently I apt-get upgrade'd it which resulted in new kernel and
  ramdisk.

  My initramdisk now does not recognize USB devices.

  I can see the modules are there (usb-storage uas), and I can load
  them, but no devices come up, in particular USB storage.

  I have looked at the recent commits to this package, and I wonder if
  the following commit may have had something to do, as it is recent and
  deals with device firmware and resuming devices..

  https://git.launchpad.net/ubuntu/+source/initramfs-
  tools/commit/?id=3faf13b2b7217c05a20d649b10920f828b3c83c3

  I really don't understand what is the process until USB devices are
  instantiated as /dev/disk/... so I am a bit lost in finding out
  exactly what is not working.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1946475/+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 1946475] [NEW] USB support in intram broken for raspberry 4 after udpate

[Rafael]

Public bug reported:

Hi,

I have a Raspberry PI 4 running Ubuntu 18.04.

Recently I apt-get upgrade'd it which resulted in new kernel and
ramdisk.

My initramdisk now does not recognize USB devices.

I can see the modules are there (usb-storage uas), and I can load them,
but no devices come up, in particular USB storage.

I have looked at the recent commits to this package, and I wonder if the
following commit may have had something to do, as it is recent and deals
with device firmware and resuming devices..

https://git.launchpad.net/ubuntu/+source/initramfs-
tools/commit/?id=3faf13b2b7217c05a20d649b10920f828b3c83c3

I really don't understand what is the process until USB devices are
instantiated as /dev/disk/... so I am a bit lost in finding out exactly
what is not working.

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


** Tags: iunitram usb

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

Title:
  USB support in intram broken for raspberry 4 after udpate

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Hi,

  I have a Raspberry PI 4 running Ubuntu 18.04.

  Recently I apt-get upgrade'd it which resulted in new kernel and
  ramdisk.

  My initramdisk now does not recognize USB devices.

  I can see the modules are there (usb-storage uas), and I can load
  them, but no devices come up, in particular USB storage.

  I have looked at the recent commits to this package, and I wonder if
  the following commit may have had something to do, as it is recent and
  deals with device firmware and resuming devices..

  https://git.launchpad.net/ubuntu/+source/initramfs-
  tools/commit/?id=3faf13b2b7217c05a20d649b10920f828b3c83c3

  I really don't understand what is the process until USB devices are
  instantiated as /dev/disk/... so I am a bit lost in finding out
  exactly what is not working.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1946475/+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 1922713] [NEW] package initramfs-tools 0.137ubuntu12 failed to install/upgrade: el subproceso instalado paquete initramfs-tools script post-installation devolvió el código de sal

[Rafael Jahziel Luna Bañuelos]

Public bug reported:

Error de GPG: https://brave-browser-apt-beta.s3.brave.com stable
InRelease: Las firmas siguientes no se pudieron verificar porque su
clave pública no está disponible: NO_PUBKEY 0B31DBA06A8A26F9El
repositorio «https://brave-browser-apt-beta.s3.brave.com stable
InRelease» no está firmado.

ProblemType: Package
DistroRelease: Ubuntu 20.10
Package: initramfs-tools 0.137ubuntu12
ProcVersionSignature: Ubuntu 5.8.0-49.55-generic 5.8.18
Uname: Linux 5.8.0-49-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.5
Architecture: amd64
CasperMD5CheckResult: skip
Date: Tue Apr  6 03:55:23 2021
ErrorMessage: el subproceso instalado paquete initramfs-tools script 
post-installation devolvió el código de salida de error 1
InstallationDate: Installed on 2021-04-04 (1 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
PackageArchitecture: all
Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 
3.8.6-0ubuntu1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.20.5ubuntu2
 apt  2.1.10ubuntu0.3
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.137ubuntu12 failed to install/upgrade: el 
subproceso instalado paquete initramfs-tools script post-installation devolvió 
el código de salida de error 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package groovy third-party-packages

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

Title:
  package initramfs-tools 0.137ubuntu12 failed to install/upgrade: el
  subproceso instalado paquete initramfs-tools script post-installation
  devolvió el código de salida de error 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Error de GPG: https://brave-browser-apt-beta.s3.brave.com stable
  InRelease: Las firmas siguientes no se pudieron verificar porque su
  clave pública no está disponible: NO_PUBKEY 0B31DBA06A8A26F9El
  repositorio «https://brave-browser-apt-beta.s3.brave.com stable
  InRelease» no está firmado.

  ProblemType: Package
  DistroRelease: Ubuntu 20.10
  Package: initramfs-tools 0.137ubuntu12
  ProcVersionSignature: Ubuntu 5.8.0-49.55-generic 5.8.18
  Uname: Linux 5.8.0-49-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Tue Apr  6 03:55:23 2021
  ErrorMessage: el subproceso instalado paquete initramfs-tools script 
post-installation devolvió el código de salida de error 1
  InstallationDate: Installed on 2021-04-04 (1 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 
3.8.6-0ubuntu1
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.20.5ubuntu2
   apt  2.1.10ubuntu0.3
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.137ubuntu12 failed to install/upgrade: el 
subproceso instalado paquete initramfs-tools script post-installation devolvió 
el código de salida de error 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/1922713/+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 1913187] Re: iproute2 segfaults when filtering sockets

[Rafael David Tinoco]

# verfication

$ dpkg -l iproute2 | grep ii
ii  iproute2   4.15.0-2ubuntu1.3 amd64networking and traffic 
control tools

$ ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1 && echo 
worked
worked

good to migrate. thank you.

-rafaeldtinoco

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

** Changed in: iproute2 (Ubuntu Bionic)
 Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)

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

Title:
  iproute2 segfaults when filtering sockets

Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

   * The ss tool crashes when a query returns no results (seg fault)

  [Test Case]

   * $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 
127.0.0.1
  Segmentation fault

   * PPA with the fix:
  https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1913187

  [Where problems could occur]

   * The ss tool is impacted and it has its code changed for the fix.

   * The fix is a clean cherry-pick and straightforward (moving
  declaration after a NULL check).

  [Other Info]

  When in Ubuntu Bionic, if one calls:

  $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
  tcp  00   
127.0.0.1:58910 127.0.0.1:22   
users:(("ssh",pid=11672,fd=3)) timer:(keepalive,119min,0)

  it works. Just like when in Groovy:

  $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
  tcp   00  
127.0.0.1:58908 127.0.0.1:22   
users:(("ssh",pid=1488591,fd=3)) timer:(keepalive,119min,0)

  but.. if there is nothing to show, in Bionic we get a segfault:

  $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
  Segmentation fault

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1913187/+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 1913187] Re: iproute2 segfaults when filtering sockets

[Rafael David Tinoco]

$ git-ubuntu tag --upload

$ git describe
upload/4.15.0-2ubuntu1.3

$ git push pkg upload/4.15.0-2ubuntu1.3
Counting objects: 11, done.
Delta compression using up to 24 threads.
Compressing objects: 100% (11/11), done.
Writing objects: 100% (11/11), 2.07 KiB | 176.00 KiB/s, done.
Total 11 (delta 7), reused 0 (delta 0)
To ssh://git.launchpad.net/ubuntu/+source/iproute2
 * [new tag] upload/4.15.0-2ubuntu1.3 -> upload/4.15.0-2ubuntu1.3

$ debdiff *.dsc | diffstat
 changelog | 7 +++
 patches/lp1913187-ss-fix-NULL-dereference-when-rendering.patch | 40 

 patches/series | 1 +
 3 files changed, 48 insertions(+)

[rafaeldtinoco@iproute2issue ubuntu]$ dput ubuntu 
./iproute2_4.15.0-2ubuntu1.3_source.changes
Checking signature on .changes
gpg: ./iproute2_4.15.0-2ubuntu1.3_source.changes: Valid signature from 
A93E0E0AD83C0D0F
Checking signature on .dsc
gpg: ./iproute2_4.15.0-2ubuntu1.3.dsc: Valid signature from A93E0E0AD83C0D0F
Uploading to ubuntu (via ftp to upload.ubuntu.com):
  Uploading iproute2_4.15.0-2ubuntu1.3.dsc: done.
  Uploading iproute2_4.15.0-2ubuntu1.3.debian.tar.xz: done.
  Uploading iproute2_4.15.0-2ubuntu1.3_source.buildinfo: done.
  Uploading iproute2_4.15.0-2ubuntu1.3_source.changes: done.
Successfully uploaded packages.

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

Title:
  iproute2 segfaults when filtering sockets

Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Bionic:
  Confirmed

Bug description:
  [Impact]

   * The ss tool crashes when a query returns no results (seg fault)

  [Test Case]

   * $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 
127.0.0.1
  Segmentation fault

   * PPA with the fix:
  https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1913187

  [Where problems could occur]

   * The ss tool is impacted and it has its code changed for the fix.

   * The fix is a clean cherry-pick and straightforward (moving
  declaration after a NULL check).

  [Other Info]

  When in Ubuntu Bionic, if one calls:

  $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
  tcp  00   
127.0.0.1:58910 127.0.0.1:22   
users:(("ssh",pid=11672,fd=3)) timer:(keepalive,119min,0)

  it works. Just like when in Groovy:

  $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
  tcp   00  
127.0.0.1:58908 127.0.0.1:22   
users:(("ssh",pid=1488591,fd=3)) timer:(keepalive,119min,0)

  but.. if there is nothing to show, in Bionic we get a segfault:

  $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
  Segmentation fault

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1913187/+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 1913187] Re: iproute2 segfaults when filtering sockets

[Rafael David Tinoco]

MP: 
https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/iproute2/+git/iproute2/+merge/396921
PPA: https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1913187

** Description changed:

+ [Impact]
+ 
+  * The ss tool crashes when a query returns no results (seg fault)
+ 
+ [Test Case]
+ 
+  * $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 
127.0.0.1
+ Segmentation fault
+ 
+ [Where problems could occur]
+ 
+  * The ss tool is impacted and it has its code changed for the fix.
+ 
+  * The fix is a clean cherry-pick and straightforward (moving
+ declaration after a NULL check).
+ 
+ [Other Info]
+  
  When in Ubuntu Bionic, if one calls:
  
  $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
  tcp  00   
127.0.0.1:58910 127.0.0.1:22   
users:(("ssh",pid=11672,fd=3)) timer:(keepalive,119min,0)
  
  it works. Just like when in Groovy:
  
  $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
  tcp   00  
127.0.0.1:58908 127.0.0.1:22   
users:(("ssh",pid=1488591,fd=3)) timer:(keepalive,119min,0)
  
  but.. if there is nothing to show, in Bionic we get a segfault:
  
  $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
  Segmentation fault

** Description changed:

  [Impact]
  
-  * The ss tool crashes when a query returns no results (seg fault)
+  * The ss tool crashes when a query returns no results (seg fault)
  
  [Test Case]
  
-  * $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 
127.0.0.1
- Segmentation fault
+  * $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 
127.0.0.1
+ Segmentation fault
+ 
+  * PPA with the fix:
+ https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1913187
  
  [Where problems could occur]
  
-  * The ss tool is impacted and it has its code changed for the fix.
+  * The ss tool is impacted and it has its code changed for the fix.
  
-  * The fix is a clean cherry-pick and straightforward (moving
+  * The fix is a clean cherry-pick and straightforward (moving
  declaration after a NULL check).
  
  [Other Info]
-  
+ 
  When in Ubuntu Bionic, if one calls:
  
  $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
  tcp  00   
127.0.0.1:58910 127.0.0.1:22   
users:(("ssh",pid=11672,fd=3)) timer:(keepalive,119min,0)
  
  it works. Just like when in Groovy:
  
  $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
  tcp   00  
127.0.0.1:58908 127.0.0.1:22   
users:(("ssh",pid=1488591,fd=3)) timer:(keepalive,119min,0)
  
  but.. if there is nothing to show, in Bionic we get a segfault:
  
  $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
  Segmentation fault

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

Title:
  iproute2 segfaults when filtering sockets

Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Bionic:
  Confirmed

Bug description:
  [Impact]

   * The ss tool crashes when a query returns no results (seg fault)

  [Test Case]

   * $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 
127.0.0.1
  Segmentation fault

   * PPA with the fix:
  https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1913187

  [Where problems could occur]

   * The ss tool is impacted and it has its code changed for the fix.

   * The fix is a clean cherry-pick and straightforward (moving
  declaration after a NULL check).

  [Other Info]

  When in Ubuntu Bionic, if one calls:

  $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
  tcp  00   
127.0.0.1:58910 127.0.0.1:22   
users:(("ssh",pid=11672,fd=3)) timer:(keepalive,119min,0)

  it works. Just like when in Groovy:

  $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
  tcp   00  
127.0.0.1:58908 127.0.0.1:22   
users:(("ssh",pid=1488591,fd=3)) timer:(keepalive,119min,0)

  but.. if there is nothing to show, in Bionic we get a segfault:

  $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
  Segmentation fault

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

[Touch-packages] [Bug 1913187] Re: iproute2 segfaults when filtering sockets

[Rafael David Tinoco]

It only affects Bionic:

[rafaeldtinoco@iproute2issue iproute2]$ git describe 
eb8559eff124221bfbafe934c4dbfe30f20604c0
v4.15.0-103-geb8559ef

[rafaeldtinoco@iproute2issue ~]$ rmadison iproute2
 iproute2 | 3.12.0-2  | trusty   | source
 iproute2 | 3.12.0-2ubuntu1.2 | trusty-updates   | source
 iproute2 | 4.3.0-1ubuntu3| xenial   | source
 iproute2 | 4.3.0-1ubuntu3.16.04.5| xenial-updates   | source
 iproute2 | 4.15.0-2ubuntu1   | bionic   | source
 iproute2 | 4.15.0-2ubuntu1.1 | bionic-security  | source
 iproute2 | 4.15.0-2ubuntu1.2 | bionic-updates   | source
 iproute2 | 4.18.0-1ubuntu2~ubuntu18.04.1 | bionic-backports | source
 iproute2 | 5.5.0-1ubuntu1| focal| source
 iproute2 | 5.7.0-1ubuntu1| groovy   | source
 iproute2 | 5.9.0-1ubuntu1| hirsute  | source
 iproute2 | 5.10.0-2ubuntu1   | hirsute-proposed | source

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

Title:
  iproute2 segfaults when filtering sockets

Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Bionic:
  Confirmed

Bug description:
  When in Ubuntu Bionic, if one calls:

  $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
  tcp  00   
127.0.0.1:58910 127.0.0.1:22   
users:(("ssh",pid=11672,fd=3)) timer:(keepalive,119min,0)

  it works. Just like when in Groovy:

  $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
  tcp   00  
127.0.0.1:58908 127.0.0.1:22   
users:(("ssh",pid=1488591,fd=3)) timer:(keepalive,119min,0)

  but.. if there is nothing to show, in Bionic we get a segfault:

  $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
  Segmentation fault

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1913187/+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 1913187] Re: iproute2 segfaults when filtering sockets

[Rafael David Tinoco]

[rafaeldtinoco@iproute2issue iproute2]$ git unfixed
eb8559eff124221bfbafe934c4dbfe30f20604c0 is the first bad commit
commit eb8559eff124221bfbafe934c4dbfe30f20604c0
Author: Jean-Philippe Brucker 
Date:   Sat Mar 3 16:59:44 2018 +

ss: fix NULL dereference when rendering without header

When ss is invoked with the no-header flag, if the query doesn't return
any result, render() is called with 'buffer' uninitialized. This
currently leads to a segfault. Ensure that buffer is initialized before
rendering.

The bug can be triggered with: ss -H sport = 10

Signed-off-by: Jean-Philippe Brucker 
Acked-by: Stefano Brivio 
Signed-off-by: Stephen Hemminger 

:04 04 bf8f626f1c0b85bd690dab60d4f74db292ac8e65
6174ebf0728edab46c62b713f6aee495eef81cb5 M  misc

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

Title:
  iproute2 segfaults when filtering sockets

Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Bionic:
  Confirmed

Bug description:
  When in Ubuntu Bionic, if one calls:

  $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
  tcp  00   
127.0.0.1:58910 127.0.0.1:22   
users:(("ssh",pid=11672,fd=3)) timer:(keepalive,119min,0)

  it works. Just like when in Groovy:

  $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
  tcp   00  
127.0.0.1:58908 127.0.0.1:22   
users:(("ssh",pid=1488591,fd=3)) timer:(keepalive,119min,0)

  but.. if there is nothing to show, in Bionic we get a segfault:

  $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
  Segmentation fault

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1913187/+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 1913187] Re: iproute2 segfaults when filtering sockets

[Rafael David Tinoco]

workaround:

sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst
127.0.0.1 | cat -

by not trying to control terminal WIDTH, segfault does not occur.

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

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

Title:
  iproute2 segfaults when filtering sockets

Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Bionic:
  Confirmed

Bug description:
  When in Ubuntu Bionic, if one calls:

  $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
  tcp  00   
127.0.0.1:58910 127.0.0.1:22   
users:(("ssh",pid=11672,fd=3)) timer:(keepalive,119min,0)

  it works. Just like when in Groovy:

  $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
  tcp   00  
127.0.0.1:58908 127.0.0.1:22   
users:(("ssh",pid=1488591,fd=3)) timer:(keepalive,119min,0)

  but.. if there is nothing to show, in Bionic we get a segfault:

  $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
  Segmentation fault

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1913187/+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 1913187] Re: iproute2 segfaults when filtering sockets

[Rafael David Tinoco]

Issues comes from:

(gdb) bt
#0  render (screen_width=144) at ss.c:1204
#1  main (argc=, argv=) at ss.c:4974

render (screen_width=144) at ss.c:1204

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

Title:
  iproute2 segfaults when filtering sockets

Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Bionic:
  Confirmed

Bug description:
  When in Ubuntu Bionic, if one calls:

  $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
  tcp  00   
127.0.0.1:58910 127.0.0.1:22   
users:(("ssh",pid=11672,fd=3)) timer:(keepalive,119min,0)

  it works. Just like when in Groovy:

  $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
  tcp   00  
127.0.0.1:58908 127.0.0.1:22   
users:(("ssh",pid=1488591,fd=3)) timer:(keepalive,119min,0)

  but.. if there is nothing to show, in Bionic we get a segfault:

  $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
  Segmentation fault

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1913187/+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 1913187] [NEW] iproute2 segfaults when filtering sockets

[Rafael David Tinoco]

Public bug reported:

When in Ubuntu Bionic, if one calls:

$ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
tcp  00   
127.0.0.1:58910 127.0.0.1:22   
users:(("ssh",pid=11672,fd=3)) timer:(keepalive,119min,0)

it works. Just like when in Groovy:

$ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
tcp   00  
127.0.0.1:58908 127.0.0.1:22   
users:(("ssh",pid=1488591,fd=3)) timer:(keepalive,119min,0)

but.. if there is nothing to show, in Bionic we get a segfault:

$ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
Segmentation fault

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

** Affects: iproute2 (Ubuntu Bionic)
 Importance: Undecided
 Assignee: Rafael David Tinoco (rafaeldtinoco)
 Status: Confirmed

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

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

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

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

** Changed in: iproute2 (Ubuntu Bionic)
     Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco)

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

Title:
  iproute2 segfaults when filtering sockets

Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Bionic:
  Confirmed

Bug description:
  When in Ubuntu Bionic, if one calls:

  $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
  tcp  00   
127.0.0.1:58910 127.0.0.1:22   
users:(("ssh",pid=11672,fd=3)) timer:(keepalive,119min,0)

  it works. Just like when in Groovy:

  $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
  tcp   00  
127.0.0.1:58908 127.0.0.1:22   
users:(("ssh",pid=1488591,fd=3)) timer:(keepalive,119min,0)

  but.. if there is nothing to show, in Bionic we get a segfault:

  $ sudo ss -Hnp -o state established 'dport = 22' src 127.0.0.1 dst 127.0.0.1
  Segmentation fault

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1913187/+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 520546] Re: [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right

[Rafael David Tinoco]

I have just faced this and kbd_mode -s also fixed the issue for me. The
behavior started out of nothing (something I did without perceiving most
likely). I'm using:

[rafaeldtinoco@fujitsu ~]$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 20.10
Release:20.10
Codename:   groovy

apt-history shows last apt command was yesterday (for my host) and it
was working fine yesterday. Unfortunately I have no time to dig into
this now, but wanted to state that this still happens in 20.10 (and
possibly 20.04 according to @ribalkin report).

** Also affects: kbd (Ubuntu Lucid)
   Importance: Undecided
   Status: New

** Also affects: xorg-server (Ubuntu Lucid)
   Importance: Undecided
   Status: New

** Also affects: console-setup (Ubuntu Lucid)
   Importance: Undecided
   Status: New

** Also affects: kbd (Ubuntu Maverick)
   Importance: Undecided
   Status: New

** Also affects: xorg-server (Ubuntu Maverick)
   Importance: Undecided
   Status: New

** Also affects: console-setup (Ubuntu Maverick)
   Importance: Undecided
   Status: New

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

Title:
  [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT
  switch from Alt+Left/Right

Status in console-setup package in Ubuntu:
  Fix Released
Status in kbd package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Invalid
Status in console-setup source package in Lucid:
  New
Status in kbd source package in Lucid:
  New
Status in xorg-server source package in Lucid:
  New
Status in console-setup source package in Maverick:
  New
Status in kbd source package in Maverick:
  New
Status in xorg-server source package in Maverick:
  New
Status in console-setup source package in Xenial:
  Confirmed
Status in kbd source package in Xenial:
  Won't Fix
Status in xorg-server source package in Xenial:
  Confirmed
Status in console-setup source package in Bionic:
  Fix Released
Status in kbd source package in Bionic:
  Won't Fix
Status in linux source package in Bionic:
  Confirmed
Status in xorg-server source package in Bionic:
  Invalid
Status in console-setup source package in Cosmic:
  Fix Released
Status in kbd source package in Cosmic:
  Won't Fix
Status in linux source package in Cosmic:
  Won't Fix
Status in xorg-server source package in Cosmic:
  Invalid
Status in console-setup source package in Disco:
  Fix Released
Status in kbd source package in Disco:
  Won't Fix
Status in linux source package in Disco:
  Won't Fix
Status in xorg-server source package in Disco:
  Invalid
Status in console-setup source package in Eoan:
  Fix Released
Status in kbd source package in Eoan:
  Fix Released
Status in linux source package in Eoan:
  Confirmed
Status in xorg-server source package in Eoan:
  Invalid

Bug description:
  (kbd)
  [Impact]

   * kbd_mode -u is documented to break keyboards in modes other than xlate and 
unicode, while it is still called by some scripts. Those scripts are called 
transitively by maintainer scripts such as the one already fixed in 
console-setup. 
   * To avoid accidentally breaking keyboards a -f option is added to force 
such breaking mode changes. Without -f only the safe mode changes are performed 
and an error is printed when the requested mode change is not safe. Next 
upstream version will also exit with error, but the cherry-picked fix makes 
kbd_mode return success even when the mode switch is not performed to avoid 
regressions of scripts.

  [Test case]

   * Verify that safe mode switches work and dangerous ones are skipped
  without -f. Please note that the test will temporarily break the
  system's keyboard and it is recommended to run the test in a VM.

  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4; echo $?
  The keyboard is in Unicode (UTF-8) mode
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in xlate (8-bit) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in some unknown mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -f -u -C /dev/tty0; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -s -C /dev/tty0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in raw (scancode) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C 

[Touch-packages] [Bug 520546] Re: [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right

[Rafael David Tinoco]

[rafaeldtinoco@fujitsu ~]$ sudo kbd_mode 
The keyboard is in Unicode (UTF-8) mode

[rafaeldtinoco@fujitsu ~]$ sudo kbd_mode -C /dev/tty1
The keyboard is in Unicode (UTF-8) mode

[rafaeldtinoco@fujitsu ~]$ sudo kbd_mode -s

[rafaeldtinoco@fujitsu ~]$ sudo kbd_mode -C /dev/tty1
The keyboard is in raw (scancode) mode

and it was "fixed".

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

Title:
  [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT
  switch from Alt+Left/Right

Status in console-setup package in Ubuntu:
  Fix Released
Status in kbd package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Invalid
Status in console-setup source package in Lucid:
  New
Status in kbd source package in Lucid:
  New
Status in xorg-server source package in Lucid:
  New
Status in console-setup source package in Maverick:
  New
Status in kbd source package in Maverick:
  New
Status in xorg-server source package in Maverick:
  New
Status in console-setup source package in Xenial:
  Confirmed
Status in kbd source package in Xenial:
  Won't Fix
Status in xorg-server source package in Xenial:
  Confirmed
Status in console-setup source package in Bionic:
  Fix Released
Status in kbd source package in Bionic:
  Won't Fix
Status in linux source package in Bionic:
  Confirmed
Status in xorg-server source package in Bionic:
  Invalid
Status in console-setup source package in Cosmic:
  Fix Released
Status in kbd source package in Cosmic:
  Won't Fix
Status in linux source package in Cosmic:
  Won't Fix
Status in xorg-server source package in Cosmic:
  Invalid
Status in console-setup source package in Disco:
  Fix Released
Status in kbd source package in Disco:
  Won't Fix
Status in linux source package in Disco:
  Won't Fix
Status in xorg-server source package in Disco:
  Invalid
Status in console-setup source package in Eoan:
  Fix Released
Status in kbd source package in Eoan:
  Fix Released
Status in linux source package in Eoan:
  Confirmed
Status in xorg-server source package in Eoan:
  Invalid

Bug description:
  (kbd)
  [Impact]

   * kbd_mode -u is documented to break keyboards in modes other than xlate and 
unicode, while it is still called by some scripts. Those scripts are called 
transitively by maintainer scripts such as the one already fixed in 
console-setup. 
   * To avoid accidentally breaking keyboards a -f option is added to force 
such breaking mode changes. Without -f only the safe mode changes are performed 
and an error is printed when the requested mode change is not safe. Next 
upstream version will also exit with error, but the cherry-picked fix makes 
kbd_mode return success even when the mode switch is not performed to avoid 
regressions of scripts.

  [Test case]

   * Verify that safe mode switches work and dangerous ones are skipped
  without -f. Please note that the test will temporarily break the
  system's keyboard and it is recommended to run the test in a VM.

  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4; echo $?
  The keyboard is in Unicode (UTF-8) mode
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in xlate (8-bit) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in some unknown mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -f -u -C /dev/tty0; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -s -C /dev/tty0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in raw (scancode) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in raw (scancode) mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0

  [Regression Potential]

   * kbd_mode stops performing breaking mode switches and this may make
  scripts ineffective when trying to perform a breaking change. This is
  the intention of the change and the emitter error helps in finding the
  offending script.

  The following packages found to call kbd_mode directly:
  console-setup
  xinit
  console-cyrillic
  initramfs-tools
  dracut
  console-tools
  xview
  ubiquity's embedded console-setup copy
  console-data
  vnc4

  The console related packages are expected to execute only safe mode
  changes because they should operate on consoles only and the rest seem
  to 

[Touch-packages] [Bug 50093] Re: Some sysctls are ignored on boot

[Rafael David Tinoco]

** Changed in: procps (Ubuntu)
 Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)

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

Title:
  Some sysctls are ignored on boot

Status in procps package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: procps

  /etc/init.d/procps.sh comes too early in the boot process to apply a
  lot of sysctl's. As it runs before networking modules are loaded and
  filesystems are mounted, there are quite a lot of commonly-used
  sysctl's which are simply ignored on boot and produce errors to the
  console.

  Simply renaming the symlink from S17 to > S40 probably isn't a great
  solution, as there are probably folk who want and expect some sysctl's
  to be applied before filesystems are mounted and so on. However,
  simply ugnoring something as important as sysctl settings isn't really
  on. Administrators expect the settings in /etc/sysctl.conf to take
  effect.

  One sto-gap solution would be to run sysctl -p twice; once at S17 and once at 
S41. There may still be some warnings and errors, but everything would be 
applied. A different, more complex approach might be to re-architect the sysctl 
configuration into something like;
   
  /etc/sysctl.d/$modulename

  and have the userland module-loading binaries take care of applying
  them after modules are loaded. Though this may take care of explicitly
  loaded modules only, I'm not sure.

  Incidentally, /etc/sysctl.conf still refers to
  /etc/networking/options, but hasn't that been deprecated?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/50093/+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 1815101] Re: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted)

[Rafael David Tinoco]

Ubuntu HA wise:

I'm recommending all HA clusters to have the cluster interfaces
configured with systemd-networkd DIRECTLY instead of wrapping it through
netplan.io. At least until we're sure that HA has no issues with
netplan.io, having it configured directly will allow us to isolate
possible issues.

I see that this has been assigned to @slashd. Eric, Important thing here
is to have netplan fix in focal (as it is the latest LTS) in order for
HA to be supported with it. KeepConfiguration= is good enough, for now,
if using systemd-networkd only.

Thank you!

** Tags removed: server-next

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

Title:
  [master] Restarting systemd-networkd breaks keepalived, heartbeat,
  corosync, pacemaker (interface aliases are restarted)

Status in netplan:
  Confirmed
Status in heartbeat package in Ubuntu:
  Won't Fix
Status in keepalived package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  In Progress
Status in keepalived source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Confirmed
Status in keepalived source package in Bionic:
  Confirmed
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Disco:
  Won't Fix
Status in systemd source package in Eoan:
  Fix Released
Status in keepalived source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Fix Released

Bug description:
  [impact]

  - ALL related HA software has a small problem if interfaces are being
  managed by systemd-networkd: nic restarts/reconfigs are always going
  to wipe all interfaces aliases when HA software is not expecting it to
  (no coordination between them.

  - keepalived, smb ctdb, pacemaker, all suffer from this. Pacemaker is
  smarter in this case because it has a service monitor that will
  restart the virtual IP resource, in affected node & nic, before
  considering a real failure, but other HA service might consider a real
  failure when it is not.

  [test case]

  - comment #14 is a full test case: to have 3 node pacemaker, in that
  example, and cause a networkd service restart: it will trigger a
  failure for the virtual IP resource monitor.

  - other example is given in the original description for keepalived.
  both suffer from the same issue (and other HA softwares as well).

  [regression potential]

  - this backports KeepConfiguration parameter, which adds some
  significant complexity to networkd's configuration and behavior, which
  could lead to regressions in correctly configuring the network at
  networkd start, or incorrectly maintaining configuration at networkd
  restart, or losing network state at networkd stop.

  - Any regressions are most likely to occur during networkd start,
  restart, or stop, and most likely to involve missing or incorrect ip
  address(es).

  - the change is based in upstream patches adding the exact feature we
  needed to fix this issue & it will be integrated with a netplan change
  to add the needed stanza to systemd nic configuration file
  (KeepConfiguration=)

  [other info]

  original description:
  ---

  Configure netplan for interfaces, for example (a working config with
  IP addresses obfuscated)

  network:
  ethernets:
  eth0:
  addresses: [192.168.0.5/24]
  dhcp4: false
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  eth2:
  addresses:
    - 12.13.14.18/29
    - 12.13.14.19/29
  gateway4: 12.13.14.17
  dhcp4: false
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  eth3:
  addresses: [10.22.11.6/24]
  dhcp4: false
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  eth4:
  addresses: [10.22.14.6/24]
  dhcp4: false
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  eth7:
  addresses: [9.5.17.34/29]
  dhcp4: false
  optional: true
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  version: 2

  Configure keepalived (again, a working config with IP addresses
  obfuscated)

  global_defs   # Block id
  {
  notification_email {
  sysadm...@blah.com
  }
  notification_email_from 

[Touch-packages] [Bug 1880193] Re: autofs: Assertion 'set_remove(iterator->links, link) == link' failed at src/shared/userdb.c:314, function userdb_on_query_reply(). Aborting.

[Rafael David Tinoco]

I'll continue to reply here as you continue to provide me feedback about
this issue...

Thank you.

-rafaeldtinoco

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

Title:
  autofs: Assertion 'set_remove(iterator->links, link) == link' failed
  at src/shared/userdb.c:314, function userdb_on_query_reply().
  Aborting.

Status in autofs package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Triaged
Status in autofs source package in Focal:
  Triaged
Status in systemd source package in Focal:
  Triaged

Bug description:
  autofs has a periodic error on mounting shares in Ubuntu 20.04 (it happens 
about 1 time out of 5):
  "Assertion 'set_remove(iterator->links, link) == link' failed at 
src/shared/userdb.c:314, function userdb_on_query_reply(). Aborting.
  Aborted (core dumped)"


  `autofs.service` restart (or `automount` app restart) fixes this
  issue. However if some of home dirs (like `Desktop` or `Documents`)
  are mounted by `autofs`, user can't login into Ubuntu Desktop
  Environment (PC freezes on login with black screen). Since this error
  can prevent user log in, it might be considered as critical bug.


  It happens both in `autofs` systemd service and by direct execution of
  `automount` app (`automount -f -d` command).


  May be it's an underlying error in `systemd` library (I found the
  line, mentioned in error, in its source codes).


  This issue has place in Ubuntu 20.04 (it works correctly in Ubuntu
  18.04):

  > lsb_release -rd
  Description: Ubuntu 20.04 LTS
  Release: 20.04


  Packages versions:

  > apt-cache policy autofs systemd
  autofs:
Installed: 5.1.6-2
Candidate: 5.1.6-2
Version table:
   *** 5.1.6-2 500
  500 http://ru.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  systemd:
Installed: 245.4-4ubuntu3
Candidate: 245.4-4ubuntu3
Version table:
   *** 245.4-4ubuntu3 500
  500 http://ru.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status


  Steps to reproduce:
  1. Ubuntu 20.04 clean install
  2. `apt install realmd sssd sssd-tools libnss-sss libpam-sss adcli 
samba-common-bin`
  3. `realm join DOMAIN.NAME`
  4. Enable makehomedir by command: `pam-auth-update`
  5. `apt install cifs-utils`
  6. `apt install autofs`
  7. Add next line inside [domain/DOMAIN.EXT] section into /etc/sssd/sssd.conf: 
`krb5_ccname_template = FILE:%d/krb5cc_%U`
  8. Reboot
  9. Login as domain user and try to open directory, mounted by `autofs` (in my 
configuration shares are provided by AD).
  10. `autofs.service` stops with the error above about 1 time out of 5 (not 
always).

  Found workaround:
  Add `Restart=always` into `[Service]` section in 
`/lib/systemd/system/autofs.service` file (in other words configure 
auto-restart on failures for autofs service).


  Attachments:
  1. Full log of `automount -f -d` command.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1880193/+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 1880193] Re: autofs: Assertion 'set_remove(iterator->links, link) == link' failed at src/shared/userdb.c:314, function userdb_on_query_reply(). Aborting.

[Rafael David Tinoco]

With that said... perhaps if you can reproduce this easily you could
reproduce with:

systemd.log_level=debug systemd.log_target=syslog systemd.dump_core=true

added to your kernel cmdline, and provide me related debug text.

And also, updating your systemd to latest in Focal:

245.4-4ubuntu3.2

and providing me the core dump from the user session abort() generated
by:

"Assertion 'set_remove(iterator->links, link) == link' failed at
src/shared/userdb.c:314, function userdb_on_query_reply(). Aborting.

Aborted (core dumped)"

That would help me out trying to identify the issue.

** Changed in: autofs (Ubuntu Focal)
     Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)

** Changed in: autofs (Ubuntu)
 Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)

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

** Changed in: autofs (Ubuntu Focal)
   Status: New => Triaged

** Changed in: systemd (Ubuntu)
   Status: New => Triaged

** Changed in: systemd (Ubuntu Focal)
   Status: New => Triaged

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

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

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

Title:
  autofs: Assertion 'set_remove(iterator->links, link) == link' failed
  at src/shared/userdb.c:314, function userdb_on_query_reply().
  Aborting.

Status in autofs package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Triaged
Status in autofs source package in Focal:
  Triaged
Status in systemd source package in Focal:
  Triaged

Bug description:
  autofs has a periodic error on mounting shares in Ubuntu 20.04 (it happens 
about 1 time out of 5):
  "Assertion 'set_remove(iterator->links, link) == link' failed at 
src/shared/userdb.c:314, function userdb_on_query_reply(). Aborting.
  Aborted (core dumped)"


  `autofs.service` restart (or `automount` app restart) fixes this
  issue. However if some of home dirs (like `Desktop` or `Documents`)
  are mounted by `autofs`, user can't login into Ubuntu Desktop
  Environment (PC freezes on login with black screen). Since this error
  can prevent user log in, it might be considered as critical bug.


  It happens both in `autofs` systemd service and by direct execution of
  `automount` app (`automount -f -d` command).


  May be it's an underlying error in `systemd` library (I found the
  line, mentioned in error, in its source codes).


  This issue has place in Ubuntu 20.04 (it works correctly in Ubuntu
  18.04):

  > lsb_release -rd
  Description: Ubuntu 20.04 LTS
  Release: 20.04


  Packages versions:

  > apt-cache policy autofs systemd
  autofs:
Installed: 5.1.6-2
Candidate: 5.1.6-2
Version table:
   *** 5.1.6-2 500
  500 http://ru.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  systemd:
Installed: 245.4-4ubuntu3
Candidate: 245.4-4ubuntu3
Version table:
   *** 245.4-4ubuntu3 500
  500 http://ru.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status


  Steps to reproduce:
  1. Ubuntu 20.04 clean install
  2. `apt install realmd sssd sssd-tools libnss-sss libpam-sss adcli 
samba-common-bin`
  3. `realm join DOMAIN.NAME`
  4. Enable makehomedir by command: `pam-auth-update`
  5. `apt install cifs-utils`
  6. `apt install autofs`
  7. Add next line inside [domain/DOMAIN.EXT] section into /etc/sssd/sssd.conf: 
`krb5_ccname_template = FILE:%d/krb5cc_%U`
  8. Reboot
  9. Login as domain user and try to open directory, mounted by `autofs` (in my 
configuration shares are provided by AD).
  10. `autofs.service` stops with the error above about 1 time out of 5 (not 
always).

  Found workaround:
  Add `Restart=always` into `[Service]` section in 
`/lib/systemd/system/autofs.service` file (in other words configure 
auto-restart on failures for autofs service).


  Attachments:
  1. Full log of `automount -f -d` command.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1880193/+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 1894172] [NEW] isc-dhcp-server using wrong env variable for INTERFACES

[Rafael David Tinoco]

Public bug reported:

When checking isc-dhcp-server unit file I saw isc-dhcp-server is being
started by:

ConditionPathExists=/etc/default/isc-dhcp-server
ConditionPathExists=|/etc/ltsp/dhcpd.conf
ConditionPathExists=|/etc/dhcp/dhcpd.conf

[Service]
EnvironmentFile=/etc/default/isc-dhcp-server
RuntimeDirectory=dhcp-server
# The leases files need to be root:dhcpd even when dropping privileges
ExecStart=/bin/sh -ec '\
CONFIG_FILE=/etc/dhcp/dhcpd.conf; \
if [ -f /etc/ltsp/dhcpd.conf ]; then CONFIG_FILE=/etc/ltsp/dhcpd.conf; fi; \
[ -e /var/lib/dhcp/dhcpd.leases ] || touch /var/lib/dhcp/dhcpd.leases; \
chown root:dhcpd /var/lib/dhcp /var/lib/dhcp/dhcpd.leases; \
chmod 775 /var/lib/dhcp ; chmod 664 /var/lib/dhcp/dhcpd.leases; \
exec dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid 
-cf $CONFIG_FILE $INTERFACES'

But the /etc/default/isc-dhcp-server file sets $INTERFACESv4 and
$INTERFACESv6.

This has only been working because cmdline sets -4 and subnet
declaration in dhcpd.conf file makes dhcp-server to bind to the correct
interfaces, as it looks like.

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

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

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


** Tags: bitesize server-next

** Changed in: isc-dhcp (Ubuntu)
   Status: New => Triaged

** Also affects: isc-dhcp (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: isc-dhcp (Ubuntu Groovy)
   Importance: Undecided
   Status: Triaged

** Also affects: isc-dhcp (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: isc-dhcp (Ubuntu Focal)
   Status: New => Confirmed

** Changed in: isc-dhcp (Ubuntu Bionic)
   Status: New => Triaged

** No longer affects: isc-dhcp (Ubuntu Groovy)

** Tags added: server-next

** Tags added: bitesize

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

Title:
  isc-dhcp-server using wrong env variable for INTERFACES

Status in isc-dhcp package in Ubuntu:
  Triaged
Status in isc-dhcp source package in Bionic:
  Triaged
Status in isc-dhcp source package in Focal:
  Confirmed

Bug description:
  When checking isc-dhcp-server unit file I saw isc-dhcp-server is being
  started by:

  ConditionPathExists=/etc/default/isc-dhcp-server
  ConditionPathExists=|/etc/ltsp/dhcpd.conf
  ConditionPathExists=|/etc/dhcp/dhcpd.conf

  [Service]
  EnvironmentFile=/etc/default/isc-dhcp-server
  RuntimeDirectory=dhcp-server
  # The leases files need to be root:dhcpd even when dropping privileges
  ExecStart=/bin/sh -ec '\
  CONFIG_FILE=/etc/dhcp/dhcpd.conf; \
  if [ -f /etc/ltsp/dhcpd.conf ]; then CONFIG_FILE=/etc/ltsp/dhcpd.conf; 
fi; \
  [ -e /var/lib/dhcp/dhcpd.leases ] || touch /var/lib/dhcp/dhcpd.leases; \
  chown root:dhcpd /var/lib/dhcp /var/lib/dhcp/dhcpd.leases; \
  chmod 775 /var/lib/dhcp ; chmod 664 /var/lib/dhcp/dhcpd.leases; \
  exec dhcpd -user dhcpd -group dhcpd -f -4 -pf /run/dhcp-server/dhcpd.pid 
-cf $CONFIG_FILE $INTERFACES'

  But the /etc/default/isc-dhcp-server file sets $INTERFACESv4 and
  $INTERFACESv6.

  This has only been working because cmdline sets -4 and subnet
  declaration in dhcpd.conf file makes dhcp-server to bind to the
  correct interfaces, as it looks like.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1894172/+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 1893728] Re: Ubuntu CVE Tracker krb5 1.17-6ubuntu4 CVE-2018-20217 false positive

[Rafael David Tinoco]

** Also affects: krb5 (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

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

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

Title:
  Ubuntu CVE Tracker krb5 1.17-6ubuntu4 CVE-2018-20217 false positive

Status in krb5 package in Ubuntu:
  Fix Released
Status in krb5 source package in Bionic:
  New
Status in krb5 source package in Focal:
  New

Bug description:
  Information in shows that krb5 versions before 1.17 are vulnerable to 
CVE-2018-20217.
  https://people.canonical.com/~ubuntu-security/cve/2018/CVE-2018-20217.html

  Based on Debian bug report, this is already fixed in 1.16.2 version:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917387

  Ubuntu 20.04 LTS (Focal Fossa) includes version krb5 1.17.6:
  https://launchpad.net/ubuntu/focal/+source/krb5

  Ubuntu CVE Tracker page shows that Ubuntu 20.04 LTS (Focal Fossa) doesn't 
have a package where CVE-2018-20217 is fixed.
  https://people.canonical.com/~ubuntu-security/cve/2018/CVE-2018-20217.html

  Steps to reproduce:
  This was found when examining AWS Elastic Container Registry Vulnerability 
scanning results for a Docker image based on latest Ubuntu 20.04: Here is the 
complete line from the report:
  krb5:1.17-6ubuntu4 MEDIUM A Reachable Assertion issue was discovered in the 
KDC in MIT Kerberos 5 (aka krb5) before 1.17. If an attacker can obtain a 
krbtgt ticket using an older encryption type (single-DES, triple-DES, or RC4), 
the attacker can crash the KDC by making an S4U2Self request.

  It can be seen from the scan that the Docker image included krb5
  bversion 1.17-6.

  Expected:
  No vulnerability finding.

  Actual:
  krb5 bversion 1.17-6ubuntu4 is reported as vulnerable to CVE-2018-20217.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1893728/+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 1893716] Re: scripts in /etc/update-motd.d/ run even on login via non-interactive scp and sftp sessions

[Rafael David Tinoco]

Hello Thomas,

Thanks for reporting this and making Ubuntu better.

about your statement on lsb-release, in 00-header:


[ -r /etc/lsb-release ] && . /etc/lsb-release

if [ -z "$DISTRIB_DESCRIPTION" ] && [ -x /usr/bin/lsb_release ]; then
# Fall back to using the very slow lsb_release utility
DISTRIB_DESCRIPTION=$(lsb_release -s -d)
fi

# cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=16.04
DISTRIB_CODENAME=xenial
DISTRIB_DESCRIPTION="Ubuntu 16.04.7 LTS"


the slowpath is only executed if the DISTRIB_DESCRIPTION variable is not
set, at least in my tests.

In regards to your statement:

"""
The content of /etc/update-motd.d/* really, really, really shouldn't be 
executed if the session in question is not interactive, as it provides no value 
at all. Unfortunately, to disable it for these non-interactive sessions, we 
also have to disable it for the interactive ones as well where it has some 
value (though not enough to make spiking the load on this server through the 
roof an acceptable tradeoff).
"""

Considering there IS a way of disabling the dynamic motd contents
currently by commenting only the line containing the /run/motd.dynamic
wording:

# Print the message of the day upon successful login.
# This includes a dynamically generated part from /run/motd.dynamic
# and a static (admin-editable) part from /etc/motd.
# sessionoptional pam_motd.so  motd=/run/motd.dynamic
sessionoptional pam_motd.so noupdate

I'm flagging this bug as a whishlist priority.


** Also affects: update-motd (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: openssh (Ubuntu)

** No longer affects: base-files (Ubuntu)

** Changed in: update-motd (Ubuntu)
   Status: New => Triaged

** Changed in: update-motd (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  scripts in /etc/update-motd.d/ run even on login via non-interactive
  scp and sftp sessions

Status in update-motd package in Ubuntu:
  Triaged

Bug description:
  My client has 200+ devices automatically uploading information via
  sftp and scp to a server every few minutes. After a recent update, I
  noticed the load on their server spiking through the roof. Upon
  investigation, I discovered a horde of landscape-sysinfo and
  /usr/bin/lsb_release processes running that correlated with login
  session notifications in /var/log/syslog and the load spikes.

  It appears that even in non-interactive sessions where this
  information will never be seen, the configuration options below in
  /etc/pam.d/sshd cause these items to be launched (in fact, probably
  everything in /etc/update-motd.d). This only started on the system in
  question after a recent set of system updates were installed.

  The content of /etc/update-motd.d/* really, really, really shouldn't
  be executed if the session in question is not interactive, as it
  provides no value at all. Unfortunately, to disable it for these non-
  interactive sessions, we also have to disable it for the interactive
  ones as well where it has some value (though not enough to make
  spiking the load on this server through the roof an acceptable
  tradeoff).

  # Print the message of the day upon successful login.
  # This includes a dynamically generated part from /run/motd.dynamic
  # and a static (admin-editable) part from /etc/motd.
  #sessionoptional pam_motd.so  motd=/run/motd.dynamic
  #sessionoptional pam_motd.so noupdate

  Also, looking at the script 00-header in /etc/update-motd.d/,
  /usr/bin/lsb_release is being improperly launched, as /etc/lsb_release
  does include the necessary information:

  [ -r /etc/lsb-release ] && . /etc/lsb-release

  if [ -z "$DISTRIB_DESCRIPTION" ] && [ -x /usr/bin/lsb_release ]; then
  # Fall back to using the very slow lsb_release utility
  DISTRIB_DESCRIPTION=$(lsb_release -s -d)
  fi

  # cat /etc/lsb-release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=16.04
  DISTRIB_CODENAME=xenial
  DISTRIB_DESCRIPTION="Ubuntu 16.04.7 LTS"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-motd/+bug/1893716/+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 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa

[Rafael Motta]

*** This bug is a duplicate of bug 1871794 ***
https://bugs.launchpad.net/bugs/1871794

experiencing this as well
Lenovo ideapad 330
jbl live400bt
mic over bluetooth not working :(
but fully works over cable plugged in

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

Title:
  [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting
  HSP/HFP audio profile in Focal Fossa

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After updating the release from Ubuntu 19.10 to 20.04, the bluetooth
  headset doesn't work anymore when HSP/HFP profile is selected.

  With Ubuntu 19.10 the headset was working, there was audio and the mic
  was perfect for video conferencing.

  [Steps to reproduce]
  1. Connect headset (used blueman to setup and connect)
  1.1. When connected the system automatically selects A2DP profile
  2. Start playing audio (browser or other)
  3. Change profile to HSP/HFP with pavucontrol (or blueman)
  4. The audio disappears and microphone is not working (no input)
  5. Optionally switch back to A2DP and the audio comes back

  [Expected]
  When switching to HSP/HFP the audio should keep playing and the microphone 
should start working

  [Notes]
  I tried with pavucontrol to switch between profiles while playing audio from 
a browser.
  As side note there's a led in the headset that still blinks when switching 
profile.

  I tried deleting the pulse folder under user's profile .config without
  success, also reinstalled packages and did a `sudo alsa force-reload`
  and rebooting several times.

  Note: not sure this is a duplicate of [Bug #1576559], it looks quite
  different since the profile changes but the headset stops working.

  [System info]
  Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64
  pulseaudio: 1:13.99.1-1ubuntu3
  bluez: 5.53-0ubuntu3

  Headset: Sennheiser HD 4.50 BTNC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+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 1861941] Re: bcache by-uuid links disappear after mounting bcache0

[Rafael David Tinoco]

Bionic verification:

$ apt changelog bcache-tools | head -10

bcache-tools (1.0.8-2ubuntu0.18.04.1) bionic; urgency=medium

  [ Ryan Harper ]
  * Add helper script to read bcache devs superblock (LP: #1861941)

 -- Rafael David Tinoco   Wed, 05 Aug 2020
17:44:05 -0300

bcache-tools (1.0.8-2build1) artful; urgency=medium



$ dpkg-query -f '${Package}###${Version}\n' -W 'bcache-tools'
bcache-tools###1.0.8-2ubuntu0.18.04.1


$ sudo ./test-bcache.sh 
/mnt is a mountpoint
/dev/bcache0: 2 bytes were erased at offset 0x0438 (ext4): 53 ef
writing 1 to /sys/class/block/bcache0/bcache/stop
writing 1 to /sys/fs/bcache/60412675-9103-47b0-9794-91fcfb12d50d/stop
/dev/vdc: 16 bytes were erased at offset 0x1018 (bcache): c6 85 73 f6 4e 1a 
45 ca 82 65 f5 7f 48 ba 6d 81
10+0 records in
10+0 records out
10485760 bytes (10 MB, 10 MiB) copied, 0.0173157 s, 606 MB/s
/dev/vdb: 16 bytes were erased at offset 0x1018 (bcache): c6 85 73 f6 4e 1a 
45 ca 82 65 f5 7f 48 ba 6d 81
10+0 records in
10+0 records out
10485760 bytes (10 MB, 10 MiB) copied, 0.00634546 s, 1.7 GB/s
UUID:   c3758ea3-0e2c-42e3-bb77-da27292d2476
Set UUID:   b2b21f55-3599-461a-b162-8377d85fbc34
version:0
nbuckets:   2048
block_size: 1
bucket_size:1024
nr_in_set:  1
nr_this_dev:0
first_bucket:   1
UUID:   f4001b7e-386e-4ca3-a5e0-d53f100d156f
Set UUID:   b2b21f55-3599-461a-b162-8377d85fbc34
version:1
block_size: 1
data_offset:16
/dev/vdc
tee: /sys/fs/bcache/register: Invalid argument
/dev/vdb
tee: /sys/fs/bcache/register: Invalid argument
total 0
drwxr-xr-x 2 root root 60 Aug 21 14:03 .
drwxr-xr-x 3 root root 60 Aug 21 14:03 ..
lrwxrwxrwx 1 root root 13 Aug 21 14:03 f4001b7e-386e-4ca3-a5e0-d53f100d156f -> 
../../bcache0
Creating filesystems on bcache0
mke2fs 1.44.1 (24-Mar-2018)
Discarding device blocks: done
Creating filesystem with 262142 4k blocks and 65536 inodes
Filesystem UUID: 4ade91a9-6176-4a93-a34f-158fa08d0091
Superblock backups stored on blocks: 
32768, 98304, 163840, 229376

Allocating group tables: done
Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done

mounting bcache0 to /mnt
total 0
drwxr-xr-x 2 root root 60 Aug 21 14:03 .
drwxr-xr-x 3 root root 60 Aug 21 14:03 ..
lrwxrwxrwx 1 root root 13 Aug 21 14:03 f4001b7e-386e-4ca3-a5e0-d53f100d156f -> 
../../bcache0
Everything OK


** 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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1861941

Title:
  bcache by-uuid links disappear after mounting bcache0

Status in bcache-tools package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Committed
Status in systemd package in Ubuntu:
  Fix Released
Status in bcache-tools source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  Won't Fix
Status in bcache-tools source package in Focal:
  Fix Released
Status in systemd source package in Focal:
  In Progress

Bug description:
  SRU TEAM: The last 2 commits show a summary for the merges/changes
  I added some specific (to Bionic) notes in the template.
  Thanks!

  [Impact]

   * bcache-tools udev created symlinks might disappear when other udev
  events are processed for the same devices.

   * after mkfs.XXX in /dev/bcacheY you might face a condition where
  /dev/bcache/by-{uuid,label}/zzz symlinks are gone.

   * /dev/bcache/by-{uuid,label}/ symlinks are important so bcache
  devices can be addressed by their UUIDs and not the ordering they were
  assembled (MAAS depends on this feature, for example).

   * it was also discussed in this bug that systemd-udev should *not*
  populate /dev/disk/by-uuid/ with symlinks of disks that were bcache
  backing devices. this was turned into a discussion whether blkid
  should report those or not, and this discussion "died" after sometime.
  This last item is what the systemd update is all about: to disallow
  /dev/disk/by-XXX/ creation for bcache backing devices (a simple
  change that will reduce end users confusion).

  [Test Case]

   * The reproducer script is here:

     https://paste.ubuntu.com/p/37KGy2Smnp/

   * Bionic can't reproduce the issue with the 18.04 kernel, nor with
  the HWE kernel. Nevertheless, it is preferable that Bionic also do the
  same thing: to read bcache superblock and feed environment for
  /dev/bcache/by-{uuid,label} symlinks creation.

  [Regression Potential]

   * We are not depending on bcache device udev events any more when
  creating the /dev/bcache/by-{uuid,

[Touch-packages] [Bug 1576559] Re: Refused to switch profile to headset_head_unit: Not connected

[Rafael César Neves]

Same issue here with Sony WH-CH710N on a fresh install of Ubuntu 20.04.1
LTS kernel 5.4.0-42-generic

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

Title:
  Refused to switch profile to headset_head_unit: Not connected

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to connect a bluetooth-speaker-with-microphone (Mi
  Bluetooth Speaker) to Ubuntu. It works well as an A2DP sync, but can't
  use it as a headset with microphone.

  The device doesn't list in the "Input Devices" by default, and using
  the sound settings to change the profile of the device to HSP/HFP
  results in this log message:

  W: [pulseaudio] module-bluez5-device.c: Refused to switch profile to
  headset_head_unit: Not connected

  
  I'm running Ubuntu 16.04 LTS. I did an upgrade from Ubuntu 15.10.

  pulseaudio:
Installed: 1:8.0-0ubuntu3

  bluez:
Installed: 5.37-0ubuntu5

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1576559/+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 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa

[Rafael César Neves]

*** This bug is a duplicate of bug 1871794 ***
https://bugs.launchpad.net/bugs/1871794

Same issue here with Sony WH-CH710N on a fresh install of Ubuntu 20.04.1
LTS kernel 5.4.0-42-generic

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

Title:
  [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting
  HSP/HFP audio profile in Focal Fossa

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After updating the release from Ubuntu 19.10 to 20.04, the bluetooth
  headset doesn't work anymore when HSP/HFP profile is selected.

  With Ubuntu 19.10 the headset was working, there was audio and the mic
  was perfect for video conferencing.

  [Steps to reproduce]
  1. Connect headset (used blueman to setup and connect)
  1.1. When connected the system automatically selects A2DP profile
  2. Start playing audio (browser or other)
  3. Change profile to HSP/HFP with pavucontrol (or blueman)
  4. The audio disappears and microphone is not working (no input)
  5. Optionally switch back to A2DP and the audio comes back

  [Expected]
  When switching to HSP/HFP the audio should keep playing and the microphone 
should start working

  [Notes]
  I tried with pavucontrol to switch between profiles while playing audio from 
a browser.
  As side note there's a led in the headset that still blinks when switching 
profile.

  I tried deleting the pulse folder under user's profile .config without
  success, also reinstalled packages and did a `sudo alsa force-reload`
  and rebooting several times.

  Note: not sure this is a duplicate of [Bug #1576559], it looks quite
  different since the profile changes but the headset stops working.

  [System info]
  Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64
  pulseaudio: 1:13.99.1-1ubuntu3
  bluez: 5.53-0ubuntu3

  Headset: Sennheiser HD 4.50 BTNC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+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 1890892] Re: WSL openssh-server incorrect permissions .ssh

[Rafael David Tinoco]

Hello Brian,

Thank you for taking the time to file a bug report.

Are you complaining about permissions of ~/.ssh directory ?

I have subscribed Patrick Wu, in charge for WSL1/2 releases but, to be
honest, I'm not entirely sure what is the issue you're considering a bug
here... could you better describe it ?

Since there is not enough information in your report to begin triage or
to differentiate between a local configuration problem and a bug in
Ubuntu, I am marking this bug as "Incomplete". We would be grateful if
you would: provide a more complete description of the problem, explain
why you believe this is a bug in Ubuntu rather than a problem specific
to your system, and then change the bug status back to "New".

For local configuration issues, you can find assistance here:
http://www.ubuntu.com/support/community


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

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

Title:
  WSL openssh-server incorrect permissions .ssh

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  Using Ubuntu Windows Subsystem for Linux (WSL) 
  $ uname -srvmpio
  Linux 4.4.0-19041-Microsoft #1-Microsoft Fri Dec 06 14:06:00 PST 2019 x86_64 
x86_64 x86_64 GNU/Linux

  (Prestep required to add port for access to windows firewall)
  .ssh directory was set as 777 when 755 (minimum) is required for operation of 
authentication keys when trying to ssh -i /path-to-key/key user@domain.

  Generally poor housekeeping. <3

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: openssh-server 1:7.6p1-4ubuntu0.3
  ProcVersionSignature: Microsoft 4.4.0-19041.1-Microsoft 4.4.35
  Uname: Linux 4.4.0-19041-Microsoft x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  Date: Sat Aug  8 08:44:02 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SSHDConfig: Error: command ['pkexec', '/usr/sbin/sshd', '-T'] failed with 
exit code 127: Error getting authority: Error initializing authority: Could not 
connect: No such file or directory
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1890892/+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 1890892] Re: WSL openssh-server incorrect permissions .ssh

[Rafael David Tinoco]

** Changed in: openssh (Ubuntu)
   Status: Triaged => Incomplete

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

Title:
  WSL openssh-server incorrect permissions .ssh

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  Using Ubuntu Windows Subsystem for Linux (WSL) 
  $ uname -srvmpio
  Linux 4.4.0-19041-Microsoft #1-Microsoft Fri Dec 06 14:06:00 PST 2019 x86_64 
x86_64 x86_64 GNU/Linux

  (Prestep required to add port for access to windows firewall)
  .ssh directory was set as 777 when 755 (minimum) is required for operation of 
authentication keys when trying to ssh -i /path-to-key/key user@domain.

  Generally poor housekeeping. <3

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: openssh-server 1:7.6p1-4ubuntu0.3
  ProcVersionSignature: Microsoft 4.4.0-19041.1-Microsoft 4.4.35
  Uname: Linux 4.4.0-19041-Microsoft x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  Date: Sat Aug  8 08:44:02 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SSHDConfig: Error: command ['pkexec', '/usr/sbin/sshd', '-T'] failed with 
exit code 127: Error getting authority: Error initializing authority: Could not 
connect: No such file or directory
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1890892/+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 1861941] Re: bcache by-uuid links disappear after mounting bcache0

[Rafael David Tinoco]

** Changed in: systemd (Ubuntu Bionic)
   Status: In Progress => Won't Fix

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

Title:
  bcache by-uuid links disappear after mounting bcache0

Status in bcache-tools package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in bcache-tools source package in Bionic:
  In Progress
Status in systemd source package in Bionic:
  Won't Fix
Status in bcache-tools source package in Focal:
  Fix Committed
Status in systemd source package in Focal:
  In Progress

Bug description:
  SRU TEAM: The last 2 commits show a summary for the merges/changes
  I added some specific (to Bionic) notes in the template.
  Thanks!

  [Impact]

   * bcache-tools udev created symlinks might disappear when other udev
  events are processed for the same devices.

   * after mkfs.XXX in /dev/bcacheY you might face a condition where
  /dev/bcache/by-{uuid,label}/zzz symlinks are gone.

   * /dev/bcache/by-{uuid,label}/ symlinks are important so bcache
  devices can be addressed by their UUIDs and not the ordering they were
  assembled (MAAS depends on this feature, for example).

   * it was also discussed in this bug that systemd-udev should *not*
  populate /dev/disk/by-uuid/ with symlinks of disks that were bcache
  backing devices. this was turned into a discussion whether blkid
  should report those or not, and this discussion "died" after sometime.
  This last item is what the systemd update is all about: to disallow
  /dev/disk/by-XXX/ creation for bcache backing devices (a simple
  change that will reduce end users confusion).

  [Test Case]

   * The reproducer script is here:

     https://paste.ubuntu.com/p/37KGy2Smnp/

   * Bionic can't reproduce the issue with the 18.04 kernel, nor with
  the HWE kernel. Nevertheless, it is preferable that Bionic also do the
  same thing: to read bcache superblock and feed environment for
  /dev/bcache/by-{uuid,label} symlinks creation.

  [Regression Potential]

   * We are not depending on bcache device udev events any more when
  creating the /dev/bcache/by-{uuid,label}/ symlinks. Instead, we are
  depending on a wrapper script that heads bcache device superblock. If
  there is a bug in this wrapper the symlinks wouldn't work.

   * Previously we were thinking in asking the kernel team to remove the
  bcache udev event delta script they've done for previous case (LP:
  #1729145). It creates the udev events that were being read and filling
  the symlinks. We decided not to remove those (just from Groovy and on)
  so we don't need to worry on Breaks/Conflicts in between the kernel
  package and bcache-tools (and udev)).

   * Long story short: kernel will continue to emit bcache udev events
  as it did previously but now those events won't be used by anything -
  after installing this SRU - because udev wrapper script is doing this
  job (and doing it properly)

  [Other Info]

  - Original Description:

  1.
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  2.
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  root@ubuntu:~# apt-cache policy linux-image-virtual
  linux-image-virtual:
    Installed: 5.4.0.12.15
    Candidate: 5.4.0.12.15
    Version table:
   *** 5.4.0.12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic
  linux-image-5.4.0-12-generic:
    Installed: 5.4.0-12.15
    Candidate: 5.4.0-12.15
    Version table:
   *** 5.4.0-12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/
  + ls -al /dev/bcache/by-uuid/
  total 0
  drwxr-xr-x 2 root root 60 Feb  4 23:31 .
  drwxr-xr-x 3 root root 60 Feb  4 23:31 ..
  lrwxrwxrwx 1 root root 13 Feb  4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a 
-> ../../bcache0

  4.
  root@ubuntu:~# ls -al /dev/bcache/by-uuid
  ls: cannot access '/dev/bcache/by-uuid': No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Tue Feb  4 23:31:52 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+subscriptions

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

[Touch-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0

[Rafael David Tinoco]

SRU TEAM:

Summary is the one above. The reason why Bionic SRU makes sense was
discussed with @paelzer during merge review:

https://code.launchpad.net/~rafaeldtinoco/ubuntu/+source/bcache-
tools/+git/bcache-tools/+merge/388774/comments/1022492

Thanks for reviewing the SRU.

@rafaeldtinoco

** Description changed:

+ SRU TEAM: The last 2 commits show a summary for the merges/changes
+ I added some specific (to Bionic) notes in the template.
+ Thanks!
+ 
  [Impact]
  
   * bcache-tools udev created symlinks might disappear when other udev
  events are processed for the same devices.
  
   * after mkfs.XXX in /dev/bcacheY you might face a condition where
  /dev/bcache/by-{uuid,label}/zzz symlinks are gone.
  
   * /dev/bcache/by-{uuid,label}/ symlinks are important so bcache devices
  can be addressed by their UUIDs and not the ordering they were assembled
  (MAAS depends on this feature, for example).
  
   * it was also discussed in this bug that systemd-udev should *not*
  populate /dev/disk/by-uuid/ with symlinks of disks that were bcache
  backing devices. this was turned into a discussion whether blkid should
  report those or not, and this discussion "died" after sometime. This
  last item is what the systemd update is all about: to disallow /dev/disk
  /by-XXX/ creation for bcache backing devices (a simple change that
  will reduce end users confusion).
  
  [Test Case]
  
   * The reproducer script is here:
  
     https://paste.ubuntu.com/p/37KGy2Smnp/
  
   * Bionic can't reproduce the issue with the 18.04 kernel, nor with the
  HWE kernel. Nevertheless, it is preferable that Bionic also do the same
  thing: to read bcache superblock and feed environment for
  /dev/bcache/by-{uuid,label} symlinks creation.
  
  [Regression Potential]
  
   * We are not depending on bcache device udev events any more when
  creating the /dev/bcache/by-{uuid,label}/ symlinks. Instead, we are
  depending on a wrapper script that heads bcache device superblock. If
  there is a bug in this wrapper the symlinks wouldn't work.
  
   * Previously we were thinking in asking the kernel team to remove the
  bcache udev event delta script they've done for previous case (LP:
  #1729145). It creates the udev events that were being read and filling
  the symlinks. We decided not to remove those (just from Groovy and on)
  so we don't need to worry on Breaks/Conflicts in between the kernel
  package and bcache-tools (and udev)).
  
   * Long story short: kernel will continue to emit bcache udev events as
  it did previously but now those events won't be used by anything - after
  installing this SRU - because udev wrapper script is doing this job (and
  doing it properly)
  
  [Other Info]
  
  - Original Description:
  
  1.
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  
  2.
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  root@ubuntu:~# apt-cache policy linux-image-virtual
  linux-image-virtual:
    Installed: 5.4.0.12.15
    Candidate: 5.4.0.12.15
    Version table:
   *** 5.4.0.12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic
  linux-image-5.4.0-12-generic:
    Installed: 5.4.0-12.15
    Candidate: 5.4.0-12.15
    Version table:
   *** 5.4.0-12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  
  3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/
  + ls -al /dev/bcache/by-uuid/
  total 0
  drwxr-xr-x 2 root root 60 Feb  4 23:31 .
  drwxr-xr-x 3 root root 60 Feb  4 23:31 ..
  lrwxrwxrwx 1 root root 13 Feb  4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a 
-> ../../bcache0
  
  4.
  root@ubuntu:~# ls -al /dev/bcache/by-uuid
  ls: cannot access '/dev/bcache/by-uuid': No such file or directory
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Tue Feb  4 23:31:52 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  bcache by-uuid links disappear after mounting bcache0

Status in bcache-tools package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in bcache-tools source package in Bionic:
  In Progress
Status in systemd source package in Bionic:
  In Progress
Status in bcache-tools source package in Focal:
  Fix Committed

[Touch-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0

[Rafael David Tinoco]

CURRENT STATUS:

SUMMARY:

BUG: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1861941
TESTCASE: https://paste.ubuntu.com/p/37KGy2Smnp/
PPA: https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1861941

BCACHE-TOOLS:

GROOVY: https://tinyurl.com/yxonp5hz (merged)
FOCAL: https://tinyurl.com/y3tbd3un (committed + verified)
BIONIC: https://tinyurl.com/y58fm4l5 (being reviewed)

SYSTEMD-UDEV:

GROOVY: https://tinyurl.com/y4w22s57 (merged patch rewording, will wait next 
upload)
FOCAL: https://tinyurl.com/y2uqbyll (merged patch, will ask for an upload - SRU)
BIONIC: BEING WORKED

KERNEL:

Decided that won't be changed as the udev bcache changes won't cause any
harm. Will ask for the patch to be dropped from groovy's kernel since
there isn't any need to keep it.

** Description changed:

+ [Impact]
+ 
+  * bcache-tools udev created symlinks might disappear when other udev
+ events are processed for the same devices.
+ 
+  * after mkfs.XXX in /dev/bcacheY you might face a condition where
+ /dev/bcache/by-{uuid,label}/zzz symlinks are gone.
+ 
+  * /dev/bcache/by-{uuid,label}/ symlinks are important so bcache devices
+ can be addressed by their UUIDs and not the ordering they were assembled
+ (MAAS depends on this feature, for example).
+ 
+  * it was also discussed in this bug that systemd-udev should *not*
+ populate /dev/disk/by-uuid/ with symlinks of disks that were bcache
+ backing devices. this was turned into a discussion whether blkid should
+ report those or not, and this discussion "died" after sometime.
+ 
+ [Test Case]
+ 
+  * The reproducer script is here:
+ 
+https://paste.ubuntu.com/p/37KGy2Smnp/
+ 
+ [Regression Potential]
+ 
+  * We are not depending on bcache device udev events any more when
+ creating the /dev/bcache/by-{uuid,label}/ symlinks. Instead, we are
+ depending on a wrapper script that heads bcache device superblock. If
+ there is a bug in this wrapper the symlinks wouldn't work.
+ 
+  * Previously we were thinking in asking the kernel team to remove the
+ bcache udev event delta script they've done for previous case (LP:
+ #1729145). It creates the udev events that were being read and filling
+ the symlinks. We decided not to remove those (just from Groovy and on)
+ so we don't need to worry on Breaks/Conflicts in between the kernel
+ package and bcache-tools (and udev)).
+ 
+  * Long story short: kernel will continue to emit bcache udev events as
+ it did previously but now those events won't be used by anything - after
+ installing this SRU - because udev wrapper script is doing this job (and
+ doing it properly)
+ 
+ [Other Info]
+ 
+ - Original Description:
+ 
+ 
  1.
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  
- 2. 
+ 2.
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
- root@ubuntu:~# apt-cache policy linux-image-virtual 
+ root@ubuntu:~# apt-cache policy linux-image-virtual
  linux-image-virtual:
-   Installed: 5.4.0.12.15
-   Candidate: 5.4.0.12.15
-   Version table:
-  *** 5.4.0.12.15 500
- 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
- 100 /var/lib/dpkg/status
- root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic 
+   Installed: 5.4.0.12.15
+   Candidate: 5.4.0.12.15
+   Version table:
+  *** 5.4.0.12.15 500
+ 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
+ 100 /var/lib/dpkg/status
+ root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic
  linux-image-5.4.0-12-generic:
-   Installed: 5.4.0-12.15
-   Candidate: 5.4.0-12.15
-   Version table:
-  *** 5.4.0-12.15 500
- 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
- 100 /var/lib/dpkg/status
+   Installed: 5.4.0-12.15
+   Candidate: 5.4.0-12.15
+   Version table:
+  *** 5.4.0-12.15 500
+ 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
+ 100 /var/lib/dpkg/status
  
  3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/
  + ls -al /dev/bcache/by-uuid/
  total 0
  drwxr-xr-x 2 root root 60 Feb  4 23:31 .
  drwxr-xr-x 3 root root 60 Feb  4 23:31 ..
  lrwxrwxrwx 1 root root 13 Feb  4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a 
-> ../../bcache0
  
  4.
  root@ubuntu:~# ls -al /dev/bcache/by-uuid
  ls: cannot access '/dev/bcache/by-uuid': No such file or directory
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Tue Feb  4 23:31:52 2020
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  LANG=C.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  LANG=C.UTF-8
+  SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

[Touch-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0

[Rafael David Tinoco]

VERIFICATION FOR FOCAL:

(k)rafaeldtinoco@bcachefocal:~$ apt-cache policy bcache-tools
bcache-tools:
  Installed: (none)
  Candidate: 1.0.8-3ubuntu0.1
  Version table:
 1.0.8-3ubuntu0.1 500
500 http://br.archive.ubuntu.com/ubuntu focal-proposed/main amd64 
Packages
 1.0.8-3 500
500 http://br.archive.ubuntu.com/ubuntu focal/main amd64 Packages

(k)rafaeldtinoco@bcachefocal:~$ apt-get install bcache-tools

(k)rafaeldtinoco@bcachefocal:~/scripts$ sudo ./test-bcache.sh 
/mnt is not a mountpoint
/dev/bcache0: 2 bytes were erased at offset 0x0438 (ext4): 53 ef
writing 1 to /sys/class/block/bcache0/bcache/stop
writing 1 to /sys/fs/bcache/6fcbc055-be04-4527-9c73-788c2419b292/stop
/dev/vdc: 16 bytes were erased at offset 0x1018 (bcache): c6 85 73 f6 4e 1a 
45 ca 82 65 f5 7f 48 ba 6d 81
10+0 records in
10+0 records out
10485760 bytes (10 MB, 10 MiB) copied, 0.0204717 s, 512 MB/s
/dev/vdb: 16 bytes were erased at offset 0x1018 (bcache): c6 85 73 f6 4e 1a 
45 ca 82 65 f5 7f 48 ba 6d 81
10+0 records in
10+0 records out
10485760 bytes (10 MB, 10 MiB) copied, 0.0092515 s, 1.1 GB/s
UUID:   73cc1c6f-ded6-4874-b76a-465408cfbd19
Set UUID:   a2400c1f-e83b-4086-a58d-0b2ebba97a9c
version:0
nbuckets:   2048
block_size: 1
bucket_size:1024
nr_in_set:  1
nr_this_dev:0
first_bucket:   1
UUID:   5f51a399-d65d-49ec-af3b-6b2b28c39605
Set UUID:   a2400c1f-e83b-4086-a58d-0b2ebba97a9c
version:1
block_size: 1
data_offset:16
/dev/vdc
tee: /sys/fs/bcache/register: Invalid argument
/dev/vdb
tee: /sys/fs/bcache/register: Invalid argument
total 0
drwxr-xr-x 2 root root 60 Aug  5 21:12 .
drwxr-xr-x 3 root root 60 Aug  5 21:12 ..
lrwxrwxrwx 1 root root 13 Aug  5 21:12 5f51a399-d65d-49ec-af3b-6b2b28c39605 -> 
../../bcache0
Creating filesystems on bcache0
mke2fs 1.45.5 (07-Jan-2020)
Discarding device blocks: done
Creating filesystem with 2621438 4k blocks and 655360 inodes
Filesystem UUID: 1b609131-52ca-43f7-96b2-4dc931f2553f
Superblock backups stored on blocks: 
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632

Allocating group tables: done
Writing inode tables: done
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information: done 

mounting bcache0 to /mnt
total 0
drwxr-xr-x 2 root root 60 Aug  5 21:12 .
drwxr-xr-x 3 root root 60 Aug  5 21:12 ..
lrwxrwxrwx 1 root root 13 Aug  5 21:12 5f51a399-d65d-49ec-af3b-6b2b28c39605 -> 
../../bcache0
Everything OK

All good!


** 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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1861941

Title:
  bcache by-uuid links disappear after mounting bcache0

Status in bcache-tools package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in bcache-tools source package in Bionic:
  In Progress
Status in systemd source package in Bionic:
  In Progress
Status in bcache-tools source package in Focal:
  Fix Committed
Status in systemd source package in Focal:
  In Progress

Bug description:
  1.
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  2. 
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  root@ubuntu:~# apt-cache policy linux-image-virtual 
  linux-image-virtual:
Installed: 5.4.0.12.15
Candidate: 5.4.0.12.15
Version table:
   *** 5.4.0.12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic 
  linux-image-5.4.0-12-generic:
Installed: 5.4.0-12.15
Candidate: 5.4.0-12.15
Version table:
   *** 5.4.0-12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/
  + ls -al /dev/bcache/by-uuid/
  total 0
  drwxr-xr-x 2 root root 60 Feb  4 23:31 .
  drwxr-xr-x 3 root root 60 Feb  4 23:31 ..
  lrwxrwxrwx 1 root root 13 Feb  4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a 
-> ../../bcache0

  4.
  root@ubuntu:~# ls -al /dev/bcache/by-uuid
  ls: cannot access '/dev/bcache/by-uuid': No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Tue Feb  4 23:31:52 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   

[Touch-packages] [Bug 1889297] Re: Bionic: debian-installer FTBFS because udev-udeb depends on libkmod2 not libkmod2-udeb

[Rafael David Tinoco]

Very nice catch @mfo,

I'm sorry to have introduced this issue and I'm glad you found it.

Thanks for sharing. I'm +1 on both uploads to fix the issue.

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

Title:
  Bionic: debian-installer FTBFS because udev-udeb depends on libkmod2
  not libkmod2-udeb

Status in kmod package in Ubuntu:
  Invalid
Status in kmod source package in Bionic:
  In Progress

Bug description:
  [Impact]

   * debian-installer currently FTBFS on Bionic because
 udev-udeb depends on libkmod2 not on libkmod2-udeb.
 
   * This regression has been introduced in kmod 24-1ubuntu3.3,
 and it propagated into udev-udeb in systemd 237-3ubuntu10.40.

   * See the '[Details]' section for the details. :)

  [Fix]

   * That kmod change fixes a FTBFS with newer debhelper on Eoan and later,
 but it is not required with older debhelper on Bionic. Just revert it.

   * There is no need to "fix" this in Eoan and later (debhelper >= 12.3)
   
   * No-change rebuild of systemd (for udev-udeb to pick up libkmod2-udeb.)

  [Test Case]

   * Try to build debian-installer on Bionic; it FTBFS:
 
The following packages have unmet dependencies:
 udev-udeb : Depends: libkmod2 but it is not installable
E: Unable to correct problems, you have held broken packages.

   * Check if libkmod2's shlibs file contains an udeb line:
   
 $ dpkg-deb --control libkmod2__.deb dir
 $ cat dir/shlibs
 libkmod 2 libkmod2
 udeb: libkmod 2 libkmod2-udeb  # this is good.

  [Regression Potential]

   * The fix only changes the libkmod2's shlibs file to include
 an udeb line (so udebs that depend on that library package
 should depend on the -udeb package.)

 Thus the regression potential is limited to the installer,
 and the udeb packages which depend on libkmod2 (udev-udeb
 only, probably.)

 Regressions could be seen as failures to load libkmod2.so
 and/or not finding its dynamic symbols.

   * There is a no-change rebuild of systemd involved/required,
 so some dependency updates may potentially impact systemd.
 
  [Details]

  debian-installer currently FTBFS on Bionic because
  udev-udeb depends on libkmod2 not on libkmod2-udeb:

The following packages have unmet dependencies:
 udev-udeb : Depends: libkmod2 but it is not installable
E: Unable to correct problems, you have held broken packages.

  This regression has been introduced in kmod 24-1ubuntu3.3,
  and it propagated into udev-udeb in systemd 237-3ubuntu10.40.

kmod (24-1ubuntu3.3) bionic; urgency=medium
<...>
  * Removed --add-udeb from dh_makeshlibs, since libkmod2-udeb does not
actually contain a library. (Closes: #939779)
<...>

  From dh_makeshlibs(1):

--add-udeb=udeb
   Create an additional line for udebs in the shlibs file
   and use udeb as the package name for udebs to depend on
   instead of the regular library package.

  Before:

  $ dpkg-deb --control libkmod2_24-1ubuntu3.2_amd64.deb
  libkmod2-u32-control

$ cat libkmod2-u32-control/shlibs 
libkmod 2 libkmod2
udeb: libkmod 2 libkmod2-udeb

$ dpkg-deb --info udev-udeb_237-3ubuntu10.39_amd64.udeb | grep Depends:
 Depends: ..., libkmod2-udeb, ...

  After:

  $ dpkg-deb --control libkmod2_24-1ubuntu3.3_amd64.deb
  libkmod2-u33-control

$ cat libkmod2-u33-control/shlibs 
libkmod 2 libkmod2

$ dpkg-deb --info udev-udeb_237-3ubuntu10.40_amd64.udeb | grep Depends:
 Depends: ..., libkmod2, ...

  
  That kmod change fixes a FTBFS with newer debhelper on Eoan and later,
  but it is not required with older debhelper on Bionic:

  Eoan:

$ dpkg -s debhelper | grep Version:
Version: 12.6.1ubuntu2

$ dpkg-buildpackpage
<...>
dh_makeshlibs --add-udeb=libkmod2-udeb -- -c4
dh_makeshlibs: The udeb libkmod2-udeb does not contain any shared 
libraries but --add-udeb=libkmod2-udeb was passed!?
make: *** [debian/rules:120: .stamp-binary] Error 255
dpkg-buildpackage: error: debian/rules binary subprocess returned exit 
status 2

  Bionic:

$ dpkg -s debhelper | grep Version:
Version: 11.1.6ubuntu2

$ dpkg-buildpackpage
<...>
dh_makeshlibs --add-udeb=libkmod2-udeb -- -c4
dh_shlibdeps -- --warnings=7
<...>
dpkg-buildpackage: info: binary and diff upload (original source NOT 
included)

  
  There is no need to "fix" this in Eoan and later, as debhelper >= 12.3
  has support for udeb auto-detection in dh_makeshlibs(1) -- and the udeb
  line is added to shlibs by default (without --add-udeb):

  From dh_makeshlibs(1):

Since debhelper 12.3, dh_makeshlibs will by default 

[Touch-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0

[Rafael David Tinoco]

SUMMARY:

BUG: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1861941
TESTCASE: https://paste.ubuntu.com/p/37KGy2Smnp/
PPA: https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1861941

BCACHE-TOOLS:

GROOVY: https://tinyurl.com/yxonp5hz (needs-review for an upload)
FOCAL: https://tinyurl.com/y3tbd3un (needs-review for SRU)
BIONIC: Will be done after Groovy and Focal are reviewed.

SYSTEMD-UDEV:

GROOVY: https://tinyurl.com/y4w22s57 (merged patch rewording, will wait next 
upload)
FOCAL: https://tinyurl.com/y2uqbyll (merged patch, will ask for an upload - SRU)
BIONIC: Will be done after Groovy and Focal are reviewed.

KERNEL:

After Groovy, Focal and Bionic are fixed (bcache-tools and systemd-
udev), I'll send a SRU request for 3 kernels to remove bcache patches
created for old bcache/udev rules bug (not needed after this bcache-
tools fix).

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

Title:
  bcache by-uuid links disappear after mounting bcache0

Status in bcache-tools package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  Fix Released
Status in bcache-tools source package in Bionic:
  In Progress
Status in systemd source package in Bionic:
  In Progress
Status in bcache-tools source package in Focal:
  In Progress
Status in systemd source package in Focal:
  In Progress

Bug description:
  1.
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  2. 
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  root@ubuntu:~# apt-cache policy linux-image-virtual 
  linux-image-virtual:
Installed: 5.4.0.12.15
Candidate: 5.4.0.12.15
Version table:
   *** 5.4.0.12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic 
  linux-image-5.4.0-12-generic:
Installed: 5.4.0-12.15
Candidate: 5.4.0-12.15
Version table:
   *** 5.4.0-12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/
  + ls -al /dev/bcache/by-uuid/
  total 0
  drwxr-xr-x 2 root root 60 Feb  4 23:31 .
  drwxr-xr-x 3 root root 60 Feb  4 23:31 ..
  lrwxrwxrwx 1 root root 13 Feb  4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a 
-> ../../bcache0

  4.
  root@ubuntu:~# ls -al /dev/bcache/by-uuid
  ls: cannot access '/dev/bcache/by-uuid': No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Tue Feb  4 23:31:52 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+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 1861941] Re: bcache by-uuid links disappear after mounting bcache0

[Rafael David Tinoco]

** Merge proposal unlinked:
   
https://code.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/+git/systemd/+merge/387991

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

Title:
  bcache by-uuid links disappear after mounting bcache0

Status in bcache-tools package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  Fix Released
Status in bcache-tools source package in Bionic:
  In Progress
Status in systemd source package in Bionic:
  In Progress
Status in bcache-tools source package in Focal:
  In Progress
Status in systemd source package in Focal:
  In Progress

Bug description:
  1.
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  2. 
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  root@ubuntu:~# apt-cache policy linux-image-virtual 
  linux-image-virtual:
Installed: 5.4.0.12.15
Candidate: 5.4.0.12.15
Version table:
   *** 5.4.0.12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic 
  linux-image-5.4.0-12-generic:
Installed: 5.4.0-12.15
Candidate: 5.4.0-12.15
Version table:
   *** 5.4.0-12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/
  + ls -al /dev/bcache/by-uuid/
  total 0
  drwxr-xr-x 2 root root 60 Feb  4 23:31 .
  drwxr-xr-x 3 root root 60 Feb  4 23:31 ..
  lrwxrwxrwx 1 root root 13 Feb  4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a 
-> ../../bcache0

  4.
  root@ubuntu:~# ls -al /dev/bcache/by-uuid
  ls: cannot access '/dev/bcache/by-uuid': No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Tue Feb  4 23:31:52 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+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 1861941] Re: bcache by-uuid links disappear after mounting bcache0

[Rafael David Tinoco]

Just spoke to @ddstreet about the SYSTEMD-UDEV merges. We are discussing
if we should keep the udev delta (from upstream) or not, considering
that the issue will be already fixed by bcache-tools and udev change
would only serve not to have backing devices at /dev/disk/by-uuid and
/dev/disk/by-label (good for end user, but to add burden to ubuntu-
devel).

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

Title:
  bcache by-uuid links disappear after mounting bcache0

Status in bcache-tools package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  Fix Released
Status in bcache-tools source package in Bionic:
  In Progress
Status in systemd source package in Bionic:
  In Progress
Status in bcache-tools source package in Focal:
  In Progress
Status in systemd source package in Focal:
  In Progress

Bug description:
  1.
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  2. 
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  root@ubuntu:~# apt-cache policy linux-image-virtual 
  linux-image-virtual:
Installed: 5.4.0.12.15
Candidate: 5.4.0.12.15
Version table:
   *** 5.4.0.12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic 
  linux-image-5.4.0-12-generic:
Installed: 5.4.0-12.15
Candidate: 5.4.0-12.15
Version table:
   *** 5.4.0-12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/
  + ls -al /dev/bcache/by-uuid/
  total 0
  drwxr-xr-x 2 root root 60 Feb  4 23:31 .
  drwxr-xr-x 3 root root 60 Feb  4 23:31 ..
  lrwxrwxrwx 1 root root 13 Feb  4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a 
-> ../../bcache0

  4.
  root@ubuntu:~# ls -al /dev/bcache/by-uuid
  ls: cannot access '/dev/bcache/by-uuid': No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Tue Feb  4 23:31:52 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+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 1861941] Re: bcache by-uuid links disappear after mounting bcache0

[Rafael David Tinoco]

BUG: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1861941
TESTCASE: https://paste.ubuntu.com/p/37KGy2Smnp/
PPA: https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1861941

BCACHE-TOOLS:

GROOVY: https://tinyurl.com/yxonp5hz
FOCAL: https://tinyurl.com/y3tbd3un

SYSTEMD-UDEV:

GROOVY: patch rewording only (https://tinyurl.com/y3ln9ttu)
FOCAL: https://tinyurl.com/yxkz6tzl

** Merge proposal linked:
   
https://code.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/+git/systemd/+merge/387998

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

Title:
  bcache by-uuid links disappear after mounting bcache0

Status in bcache-tools package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  Fix Released
Status in bcache-tools source package in Bionic:
  In Progress
Status in systemd source package in Bionic:
  In Progress
Status in bcache-tools source package in Focal:
  In Progress
Status in systemd source package in Focal:
  In Progress

Bug description:
  1.
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  2. 
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  root@ubuntu:~# apt-cache policy linux-image-virtual 
  linux-image-virtual:
Installed: 5.4.0.12.15
Candidate: 5.4.0.12.15
Version table:
   *** 5.4.0.12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic 
  linux-image-5.4.0-12-generic:
Installed: 5.4.0-12.15
Candidate: 5.4.0-12.15
Version table:
   *** 5.4.0-12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/
  + ls -al /dev/bcache/by-uuid/
  total 0
  drwxr-xr-x 2 root root 60 Feb  4 23:31 .
  drwxr-xr-x 3 root root 60 Feb  4 23:31 ..
  lrwxrwxrwx 1 root root 13 Feb  4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a 
-> ../../bcache0

  4.
  root@ubuntu:~# ls -al /dev/bcache/by-uuid
  ls: cannot access '/dev/bcache/by-uuid': No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Tue Feb  4 23:31:52 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+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 1885755] Re: test-cap-list fails with Linux 5.8 due to new capabilities

[Rafael David Tinoco]

** Merge proposal unlinked:
   
https://code.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/+git/systemd/+merge/387991

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

Title:
  test-cap-list fails with Linux 5.8 due to new capabilities

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  == test-cap-list ===
  Assertion 'capability_set_to_string_alloc(c, ) == 0' failed at 
src/test/test-cap-list.c:60, function test_capability_set_one(). Aborting.
  FAIL: test-cap-list (code: 134)

  This seems to be a result of new capabilities added in 5.8. systemd
  builds an array to convert capability numbers to strings, and these
  new capabilities are not in its array, so the test bombs out when
  trying to look up the string for a capability it doesn't know about.
  Rebuilding systemd using headers from Linux 5.8 should fix this issue.

  
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/amd64/s/systemd/20200630_154532_b7979@/log.gz
  arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/arm64/s/systemd/20200630_155538_0c63d@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/ppc64el/s/systemd/20200630_162720_b3e1b@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/s390x/s/systemd/20200630_140417_c5bdb@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1885755/+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 1861941] Re: bcache by-uuid links disappear after mounting bcache0

[Rafael David Tinoco]

systemd (udev) is fixed for Groovy:

systemd (245.6-1ubuntu1) groovy; urgency=medium

[ Ryan Harper ]
* Skip over by-uuid/by-label symlinks for bcache backing and cache devices (LP: 
#1861941)
  File: debian/patches/lp1861941-dont-generate-disk-byuuid-for-bcache-uuid.patch
  
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=4b9a0e888ca40eae


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

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

Title:
  bcache by-uuid links disappear after mounting bcache0

Status in bcache-tools package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  Fix Released
Status in bcache-tools source package in Bionic:
  In Progress
Status in systemd source package in Bionic:
  In Progress
Status in bcache-tools source package in Focal:
  In Progress
Status in systemd source package in Focal:
  In Progress

Bug description:
  1.
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  2. 
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  root@ubuntu:~# apt-cache policy linux-image-virtual 
  linux-image-virtual:
Installed: 5.4.0.12.15
Candidate: 5.4.0.12.15
Version table:
   *** 5.4.0.12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic 
  linux-image-5.4.0-12-generic:
Installed: 5.4.0-12.15
Candidate: 5.4.0-12.15
Version table:
   *** 5.4.0-12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/
  + ls -al /dev/bcache/by-uuid/
  total 0
  drwxr-xr-x 2 root root 60 Feb  4 23:31 .
  drwxr-xr-x 3 root root 60 Feb  4 23:31 ..
  lrwxrwxrwx 1 root root 13 Feb  4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a 
-> ../../bcache0

  4.
  root@ubuntu:~# ls -al /dev/bcache/by-uuid
  ls: cannot access '/dev/bcache/by-uuid': No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Tue Feb  4 23:31:52 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+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 1861941] Re: bcache by-uuid links disappear after mounting bcache0

[Rafael David Tinoco]

About blkid fix: Ryan has explained carefully how to obtain FS UUID from
the backing device at:

https://github.com/systemd/systemd/pull/16317#issuecomment-655574875

and about bcache-export-cached wrapper he created for simulating
CACHED_UUID and CACHED_LABEL (at 69-bcache.rules) and to create
/dev/bcache/{by-uuid,by-label}/{CACHED_UUID,CACHED_LABEL} symlinks.

He explained that having /dev/bcache/{by-uuid,by-label} is mandatory to
maintain same names for multiple bcache'd environments over reboots.

Currently, with the bcache-export-cached fix applied, it is *not*
mandatory to have systemd-udev fix to correctly create bcache symlinks
(or not) at /dev/disk/{by-uuid,by-label}: libblkid could have more
information regarding bcache backing devices, but judging by upstream
developers disposition they don't seem too worried about having that
feature since ID_FS_TYPE=bcache is already provided. (So, having
/dev/disk/by-uuid/XXX pointing to bcache backing devices would continue
happening...)

Summary:

Having the bcache-tools fix is enough for this bug (LP: #1861941) and
there could be changes to systemd-udev (I doubt judging by discussions
at https://github.com/systemd/systemd/pull/16317), or libblkid, that
could provide more information regarding bcache device types. If those
changes happen, we would need to revisit this bug.

IMHO,

I like the "skip_bcache_fs_type" approach done by Ryan to systemd-udev.
I'll maintain that as a delta to udev until
https://github.com/systemd/systemd/pull/16317 is fixed (if ever).

So, for now, PPA contains fix for bcache-tools for Groovy and Focal (and
will for Bionic) and that is enough to make /dev/bcache/XXX to work and
be stable after reboots. I'll keep the udev fix for Groovy and SRU that
fix for Focal and Bionic and upload to the PPA as well.

After all that is done, I'll tell kernel team to revert the bcache patch
on Bionic, Focal and Groovy kernels since it is not needed and will
reduce their delta and reduce chances of regressions over time.

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

Title:
  bcache by-uuid links disappear after mounting bcache0

Status in bcache-tools package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  In Progress
Status in bcache-tools source package in Bionic:
  In Progress
Status in systemd source package in Bionic:
  In Progress
Status in bcache-tools source package in Focal:
  In Progress
Status in systemd source package in Focal:
  In Progress

Bug description:
  1.
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  2. 
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  root@ubuntu:~# apt-cache policy linux-image-virtual 
  linux-image-virtual:
Installed: 5.4.0.12.15
Candidate: 5.4.0.12.15
Version table:
   *** 5.4.0.12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic 
  linux-image-5.4.0-12-generic:
Installed: 5.4.0-12.15
Candidate: 5.4.0-12.15
Version table:
   *** 5.4.0-12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/
  + ls -al /dev/bcache/by-uuid/
  total 0
  drwxr-xr-x 2 root root 60 Feb  4 23:31 .
  drwxr-xr-x 3 root root 60 Feb  4 23:31 ..
  lrwxrwxrwx 1 root root 13 Feb  4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a 
-> ../../bcache0

  4.
  root@ubuntu:~# ls -al /dev/bcache/by-uuid
  ls: cannot access '/dev/bcache/by-uuid': No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Tue Feb  4 23:31:52 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+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 1861941] Re: bcache by-uuid links disappear after mounting bcache0

[Rafael David Tinoco]

PPA containing (for now) fixes for Groovy and Focal:

https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1861941

will contain fix for Bionic as well.

Testcase: https://paste.ubuntu.com/p/37KGy2Smnp/

Testcase passes for both versions when having PPA pkgs installed.

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

Title:
  bcache by-uuid links disappear after mounting bcache0

Status in bcache-tools package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  In Progress
Status in bcache-tools source package in Bionic:
  In Progress
Status in systemd source package in Bionic:
  In Progress
Status in bcache-tools source package in Focal:
  In Progress
Status in systemd source package in Focal:
  In Progress

Bug description:
  1.
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  2. 
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  root@ubuntu:~# apt-cache policy linux-image-virtual 
  linux-image-virtual:
Installed: 5.4.0.12.15
Candidate: 5.4.0.12.15
Version table:
   *** 5.4.0.12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic 
  linux-image-5.4.0-12-generic:
Installed: 5.4.0-12.15
Candidate: 5.4.0-12.15
Version table:
   *** 5.4.0-12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/
  + ls -al /dev/bcache/by-uuid/
  total 0
  drwxr-xr-x 2 root root 60 Feb  4 23:31 .
  drwxr-xr-x 3 root root 60 Feb  4 23:31 ..
  lrwxrwxrwx 1 root root 13 Feb  4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a 
-> ../../bcache0

  4.
  root@ubuntu:~# ls -al /dev/bcache/by-uuid
  ls: cannot access '/dev/bcache/by-uuid': No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Tue Feb  4 23:31:52 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+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 1861941] Re: bcache by-uuid links disappear after mounting bcache0

[Rafael David Tinoco]

Focal Merge Request:

FOCAL: https://tinyurl.com/y3tbd3un

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

Title:
  bcache by-uuid links disappear after mounting bcache0

Status in bcache-tools package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  In Progress
Status in bcache-tools source package in Bionic:
  In Progress
Status in systemd source package in Bionic:
  In Progress
Status in bcache-tools source package in Focal:
  In Progress
Status in systemd source package in Focal:
  In Progress

Bug description:
  1.
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  2. 
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  root@ubuntu:~# apt-cache policy linux-image-virtual 
  linux-image-virtual:
Installed: 5.4.0.12.15
Candidate: 5.4.0.12.15
Version table:
   *** 5.4.0.12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic 
  linux-image-5.4.0-12-generic:
Installed: 5.4.0-12.15
Candidate: 5.4.0-12.15
Version table:
   *** 5.4.0-12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/
  + ls -al /dev/bcache/by-uuid/
  total 0
  drwxr-xr-x 2 root root 60 Feb  4 23:31 .
  drwxr-xr-x 3 root root 60 Feb  4 23:31 ..
  lrwxrwxrwx 1 root root 13 Feb  4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a 
-> ../../bcache0

  4.
  root@ubuntu:~# ls -al /dev/bcache/by-uuid
  ls: cannot access '/dev/bcache/by-uuid': No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Tue Feb  4 23:31:52 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+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 1861941] Re: bcache by-uuid links disappear after mounting bcache0

[Rafael David Tinoco]

Groovy Merge Request:

BUG: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1861941
PPA: https://launchpad.net/~rafaeldtinoco/+archive/ubuntu/lp1861941
GROOVY: https://tinyurl.com/yxonp5hz

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

Title:
  bcache by-uuid links disappear after mounting bcache0

Status in bcache-tools package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  In Progress
Status in bcache-tools source package in Bionic:
  In Progress
Status in systemd source package in Bionic:
  In Progress
Status in bcache-tools source package in Focal:
  In Progress
Status in systemd source package in Focal:
  In Progress

Bug description:
  1.
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  2. 
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  root@ubuntu:~# apt-cache policy linux-image-virtual 
  linux-image-virtual:
Installed: 5.4.0.12.15
Candidate: 5.4.0.12.15
Version table:
   *** 5.4.0.12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic 
  linux-image-5.4.0-12-generic:
Installed: 5.4.0-12.15
Candidate: 5.4.0-12.15
Version table:
   *** 5.4.0-12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/
  + ls -al /dev/bcache/by-uuid/
  total 0
  drwxr-xr-x 2 root root 60 Feb  4 23:31 .
  drwxr-xr-x 3 root root 60 Feb  4 23:31 ..
  lrwxrwxrwx 1 root root 13 Feb  4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a 
-> ../../bcache0

  4.
  root@ubuntu:~# ls -al /dev/bcache/by-uuid
  ls: cannot access '/dev/bcache/by-uuid': No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Tue Feb  4 23:31:52 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+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 1861941] Re: bcache by-uuid links disappear after mounting bcache0

[Rafael David Tinoco]

Debian patch submitted (removed previous patch and proposed new one
based on what was proposed to upstream):

https://salsa.debian.org/debian/bcache-tools/-/merge_requests/2

Tests are good, I could run testcase multiple times and wasn't able to
reproduce the original issue.

** Changed in: bcache-tools (Ubuntu)
   Status: Fix Released => In Progress

** Changed in: bcache-tools (Ubuntu Bionic)
   Status: Triaged => In Progress

** Changed in: bcache-tools (Ubuntu Focal)
   Status: Confirmed => In Progress

** Changed in: systemd (Ubuntu Focal)
   Status: Triaged => In Progress

** Changed in: systemd (Ubuntu Bionic)
   Status: Triaged => In Progress

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

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

Title:
  bcache by-uuid links disappear after mounting bcache0

Status in bcache-tools package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  In Progress
Status in bcache-tools source package in Bionic:
  In Progress
Status in systemd source package in Bionic:
  In Progress
Status in bcache-tools source package in Focal:
  In Progress
Status in systemd source package in Focal:
  In Progress

Bug description:
  1.
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  2. 
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  root@ubuntu:~# apt-cache policy linux-image-virtual 
  linux-image-virtual:
Installed: 5.4.0.12.15
Candidate: 5.4.0.12.15
Version table:
   *** 5.4.0.12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic 
  linux-image-5.4.0-12-generic:
Installed: 5.4.0-12.15
Candidate: 5.4.0-12.15
Version table:
   *** 5.4.0-12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/
  + ls -al /dev/bcache/by-uuid/
  total 0
  drwxr-xr-x 2 root root 60 Feb  4 23:31 .
  drwxr-xr-x 3 root root 60 Feb  4 23:31 ..
  lrwxrwxrwx 1 root root 13 Feb  4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a 
-> ../../bcache0

  4.
  root@ubuntu:~# ls -al /dev/bcache/by-uuid
  ls: cannot access '/dev/bcache/by-uuid': No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Tue Feb  4 23:31:52 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+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 1861941] Re: bcache by-uuid links disappear after mounting bcache0

[Rafael David Tinoco]

I'm setting this bug to In Progress so I can better track reverted fix
and the new one in both packages for all Ubuntu versions.

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

Title:
  bcache by-uuid links disappear after mounting bcache0

Status in bcache-tools package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  In Progress
Status in bcache-tools source package in Bionic:
  In Progress
Status in systemd source package in Bionic:
  In Progress
Status in bcache-tools source package in Focal:
  In Progress
Status in systemd source package in Focal:
  In Progress

Bug description:
  1.
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  2. 
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  root@ubuntu:~# apt-cache policy linux-image-virtual 
  linux-image-virtual:
Installed: 5.4.0.12.15
Candidate: 5.4.0.12.15
Version table:
   *** 5.4.0.12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic 
  linux-image-5.4.0-12-generic:
Installed: 5.4.0-12.15
Candidate: 5.4.0-12.15
Version table:
   *** 5.4.0-12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/
  + ls -al /dev/bcache/by-uuid/
  total 0
  drwxr-xr-x 2 root root 60 Feb  4 23:31 .
  drwxr-xr-x 3 root root 60 Feb  4 23:31 ..
  lrwxrwxrwx 1 root root 13 Feb  4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a 
-> ../../bcache0

  4.
  root@ubuntu:~# ls -al /dev/bcache/by-uuid
  ls: cannot access '/dev/bcache/by-uuid': No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Tue Feb  4 23:31:52 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+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 1861941] Re: bcache by-uuid links disappear after mounting bcache0

[Rafael David Tinoco]

Upstream patch submitted (amended from Ryan's previous patch) with a
minor PATH fix:

- https://github.com/koverstreet/bcache-tools/pull/6/

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

Title:
  bcache by-uuid links disappear after mounting bcache0

Status in bcache-tools package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  In Progress
Status in bcache-tools source package in Bionic:
  In Progress
Status in systemd source package in Bionic:
  In Progress
Status in bcache-tools source package in Focal:
  In Progress
Status in systemd source package in Focal:
  In Progress

Bug description:
  1.
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  2. 
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  root@ubuntu:~# apt-cache policy linux-image-virtual 
  linux-image-virtual:
Installed: 5.4.0.12.15
Candidate: 5.4.0.12.15
Version table:
   *** 5.4.0.12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic 
  linux-image-5.4.0-12-generic:
Installed: 5.4.0-12.15
Candidate: 5.4.0-12.15
Version table:
   *** 5.4.0-12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/
  + ls -al /dev/bcache/by-uuid/
  total 0
  drwxr-xr-x 2 root root 60 Feb  4 23:31 .
  drwxr-xr-x 3 root root 60 Feb  4 23:31 ..
  lrwxrwxrwx 1 root root 13 Feb  4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a 
-> ../../bcache0

  4.
  root@ubuntu:~# ls -al /dev/bcache/by-uuid
  ls: cannot access '/dev/bcache/by-uuid': No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Tue Feb  4 23:31:52 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+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 1861941] Re: bcache by-uuid links disappear after mounting bcache0

[Rafael David Tinoco]

TODOs (currently being started):

1 - adjust/add bcache-tools patch to use bcache-super-show (full path)
(bcache-tools - bionic | focal | groovy)

1.1 - Ubuntu kernel patches for CACHED UUID resubmission could be removed
  (linux - bionic | focal | groovy) IF (1) is done and SRU'ed

1.2 - Work with upstream so they merge @raharper's patch

2 - drop systemd patch for /dev/disk/by-uuid | /dev/bcache/by-uuid ??
(systemd - bionic | focal | groovy)
- I prefer to keep this patch and open upstream discussion for (3)

3 - blkid should not report FS_UUID for bcache backing devices (not a filesytem)
   (blkid - bionic | focal | groovy)
   - would avoid useless dev/disk/by-uuid, just like the systemd patch
   - blkid would have to be SRUed to all or systemd patch kept
   - will drive upstream discussion

4 - provide a temporary PPA with all fixes before SRU happens (MAAS
tests)

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

Title:
  bcache by-uuid links disappear after mounting bcache0

Status in bcache-tools package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in bcache-tools source package in Bionic:
  Triaged
Status in systemd source package in Bionic:
  Triaged
Status in bcache-tools source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Triaged

Bug description:
  1.
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  2. 
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  root@ubuntu:~# apt-cache policy linux-image-virtual 
  linux-image-virtual:
Installed: 5.4.0.12.15
Candidate: 5.4.0.12.15
Version table:
   *** 5.4.0.12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic 
  linux-image-5.4.0-12-generic:
Installed: 5.4.0-12.15
Candidate: 5.4.0-12.15
Version table:
   *** 5.4.0-12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/
  + ls -al /dev/bcache/by-uuid/
  total 0
  drwxr-xr-x 2 root root 60 Feb  4 23:31 .
  drwxr-xr-x 3 root root 60 Feb  4 23:31 ..
  lrwxrwxrwx 1 root root 13 Feb  4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a 
-> ../../bcache0

  4.
  root@ubuntu:~# ls -al /dev/bcache/by-uuid
  ls: cannot access '/dev/bcache/by-uuid': No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Tue Feb  4 23:31:52 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+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 1861941] Re: bcache by-uuid links disappear after mounting bcache0

[Rafael David Tinoco]

Alright. +1 on you last comment. Thanks for the feedback! I'll work on
that!

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

Title:
  bcache by-uuid links disappear after mounting bcache0

Status in bcache-tools package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in bcache-tools source package in Bionic:
  Triaged
Status in systemd source package in Bionic:
  Triaged
Status in bcache-tools source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Triaged

Bug description:
  1.
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  2. 
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  root@ubuntu:~# apt-cache policy linux-image-virtual 
  linux-image-virtual:
Installed: 5.4.0.12.15
Candidate: 5.4.0.12.15
Version table:
   *** 5.4.0.12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic 
  linux-image-5.4.0-12-generic:
Installed: 5.4.0-12.15
Candidate: 5.4.0-12.15
Version table:
   *** 5.4.0-12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/
  + ls -al /dev/bcache/by-uuid/
  total 0
  drwxr-xr-x 2 root root 60 Feb  4 23:31 .
  drwxr-xr-x 3 root root 60 Feb  4 23:31 ..
  lrwxrwxrwx 1 root root 13 Feb  4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a 
-> ../../bcache0

  4.
  root@ubuntu:~# ls -al /dev/bcache/by-uuid
  ls: cannot access '/dev/bcache/by-uuid': No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Tue Feb  4 23:31:52 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+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 1861941] Re: bcache by-uuid links disappear after mounting bcache0

[Rafael David Tinoco]

And now, after reading it all, I do follow your comment:

https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1861941/comments/47

with the proposed changed. As you're probably not fully dedicated to
this, and I can be, I'll give your suggestions a try, possibly among
with other things, and post findings here with how I think we should
move (considering upstream hasn't been very eager to fix this
situation).

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

Title:
  bcache by-uuid links disappear after mounting bcache0

Status in bcache-tools package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in bcache-tools source package in Bionic:
  Triaged
Status in systemd source package in Bionic:
  Triaged
Status in bcache-tools source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Triaged

Bug description:
  1.
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  2. 
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  root@ubuntu:~# apt-cache policy linux-image-virtual 
  linux-image-virtual:
Installed: 5.4.0.12.15
Candidate: 5.4.0.12.15
Version table:
   *** 5.4.0.12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic 
  linux-image-5.4.0-12-generic:
Installed: 5.4.0-12.15
Candidate: 5.4.0-12.15
Version table:
   *** 5.4.0-12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/
  + ls -al /dev/bcache/by-uuid/
  total 0
  drwxr-xr-x 2 root root 60 Feb  4 23:31 .
  drwxr-xr-x 3 root root 60 Feb  4 23:31 ..
  lrwxrwxrwx 1 root root 13 Feb  4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a 
-> ../../bcache0

  4.
  root@ubuntu:~# ls -al /dev/bcache/by-uuid
  ls: cannot access '/dev/bcache/by-uuid': No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Tue Feb  4 23:31:52 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+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 1861941] Re: bcache by-uuid links disappear after mounting bcache0

[Rafael David Tinoco]

@raharper,

quick question... I see that you are trying to come up with something
nor relying in the kernel fix (to throw the variables again after pivot
root, etc..)

https://github.com/g2p/bcache-tools/pull/29/#issue-169277283

why are you merging in

"github.com/g2p" ? and not in "github.com/koverstreet" ?

which one is the "current official ?"

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

Title:
  bcache by-uuid links disappear after mounting bcache0

Status in bcache-tools package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in bcache-tools source package in Bionic:
  Triaged
Status in systemd source package in Bionic:
  Triaged
Status in bcache-tools source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Triaged

Bug description:
  1.
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  2. 
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  root@ubuntu:~# apt-cache policy linux-image-virtual 
  linux-image-virtual:
Installed: 5.4.0.12.15
Candidate: 5.4.0.12.15
Version table:
   *** 5.4.0.12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic 
  linux-image-5.4.0-12-generic:
Installed: 5.4.0-12.15
Candidate: 5.4.0-12.15
Version table:
   *** 5.4.0-12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/
  + ls -al /dev/bcache/by-uuid/
  total 0
  drwxr-xr-x 2 root root 60 Feb  4 23:31 .
  drwxr-xr-x 3 root root 60 Feb  4 23:31 ..
  lrwxrwxrwx 1 root root 13 Feb  4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a 
-> ../../bcache0

  4.
  root@ubuntu:~# ls -al /dev/bcache/by-uuid
  ls: cannot access '/dev/bcache/by-uuid': No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Tue Feb  4 23:31:52 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+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 1861941] Re: bcache by-uuid links disappear after mounting bcache0

[Rafael David Tinoco]

@raharper,

Great to know.. thanks! I'm in the "reading phase".. I think I managed
to read all the history until now.. now I'm reading your analysis for
this bug more carefully, knowing the history...

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

Title:
  bcache by-uuid links disappear after mounting bcache0

Status in bcache-tools package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in bcache-tools source package in Bionic:
  Triaged
Status in systemd source package in Bionic:
  Triaged
Status in bcache-tools source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Triaged

Bug description:
  1.
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  2. 
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  root@ubuntu:~# apt-cache policy linux-image-virtual 
  linux-image-virtual:
Installed: 5.4.0.12.15
Candidate: 5.4.0.12.15
Version table:
   *** 5.4.0.12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic 
  linux-image-5.4.0-12-generic:
Installed: 5.4.0-12.15
Candidate: 5.4.0-12.15
Version table:
   *** 5.4.0-12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/
  + ls -al /dev/bcache/by-uuid/
  total 0
  drwxr-xr-x 2 root root 60 Feb  4 23:31 .
  drwxr-xr-x 3 root root 60 Feb  4 23:31 ..
  lrwxrwxrwx 1 root root 13 Feb  4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a 
-> ../../bcache0

  4.
  root@ubuntu:~# ls -al /dev/bcache/by-uuid
  ls: cannot access '/dev/bcache/by-uuid': No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Tue Feb  4 23:31:52 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+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 1861941] Re: bcache by-uuid links disappear after mounting bcache0

[Rafael David Tinoco]

Status from old attempts to solve same nature issues:



Older (2018) merge request from @raharper:

https://github.com/koverstreet/bcache-tools/pull/1

addressing the fact that kernel uevents would not always emit 
CACHED_UUID parameters, making udev to delete (whenever that happens) 
/dev/bcache/{by-uuid,by-label} symlinks.

This last MR pointed to previous related bugs:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=890446
https://bugs.launchpad.net/curtin/+bug/1728742

And to an upstream kernel patch:

https://lore.kernel.org/patchwork/patch/921298/

to

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729145

that wasn't accepted upstream.

Even not being accepted upstream, the SRU was attempted:

LP: #1729145

https://lists.ubuntu.com/archives/kernel-team/2017-December/088680.html
https://lists.ubuntu.com/archives/kernel-team/2017-December/088679.html

Both were NACKED.

Attempted again:

https://lists.ubuntu.com/archives/kernel-team/2017-December/088682.html
https://lists.ubuntu.com/archives/kernel-team/2017-December/088683.html

NACKED again.

And a v2 was sent:

https://lists.ubuntu.com/archives/kernel-team/2017-December/088751.html
https://lists.ubuntu.com/archives/kernel-team/2017-December/088750.html
https://lists.ubuntu.com/archives/kernel-team/2017-December/088749.html

and acked in January 2018 by Coling:

https://lists.ubuntu.com/archives/kernel-team/2018-January/089492.html

but not upstreamed.

BIONIC contains the fix:

commit ed9333e1b583
Author: Ryan Harper 
Date:   Mon Dec 11 12:12:01 2017

UBUNTU: SAUCE: (no-up) bcache: decouple emitting a cached_dev CHANGE uevent

BugLink: http://bugs.launchpad.net/bugs/1729145

- decouple emitting a cached_dev CHANGE uevent which includes dev.uuid
  and dev.label from bch_cached_dev_run() which only happens when a
  bcacheX device is bound to the actual backing block device (bcache0 -> 
vdb)

- update bch_cached_dev_run() to invoke bch_cached_dev_emit_change() as
  needed; no functional code path changes here

- Modify register_bcache to detect a re-registering of a bcache
  cached_dev, and in that case call bcache_cached_dev_emit_change() to

Signed-off-by: Ryan Harper 
Signed-off-by: Joseph Salisbury 
Acked-by: Colin Ian King 
Acked-by: Stefan Bader 
Signed-off-by: Khalid Elmously 
[ saf: fix incorrect indentation ]
Signed-off-by: Seth Forshee 

FOCAL contains the fix:

commit 67553dcd7905
Author: Ryan Harper 
Date:   Mon Dec 11 12:12:01 2017

UBUNTU: SAUCE: (no-up) bcache: decouple emitting a cached_dev CHANGE
uevent

GROOVY contains the fix:

commit 67553dcd7905
Author: Ryan Harper 
Date:   Mon Dec 11 12:12:01 2017

UBUNTU: SAUCE: (no-up) bcache: decouple emitting a cached_dev CHANGE
uevent



So, the kernel patch wasn't accepted, nor bcache-tools patch by 
@raharper, the bcache-export-cached.



New Upstream summary from @raharper:

https://github.com/systemd/systemd/pull/16317#issuecomment-655647313

in the upstream merge request made by @rbalint.


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

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

Title:
  bcache by-uuid links disappear after mounting bcache0

Status in bcache-tools package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in bcache-tools source package in Bionic:
  Triaged
Status in systemd source package in Bionic:
  Triaged
Status in bcache-tools source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Triaged

Bug description:
  1.
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  2. 
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  root@ubuntu:~# apt-cache policy linux-image-virtual 
  linux-image-virtual:
Installed: 5.4.0.12.15
Candidate: 5.4.0.12.15
Version table:
   *** 5.4.0.12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic 
  linux-image-5.4.0-12-generic:
Installed: 5.4.0-12.15
Candidate: 5.4.0-12.15
Version table:
   *** 5.4.0-12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/
  + ls -al /dev/bcache/by-uuid/
  total 0
  drwxr-xr-x 2 root root 60 Feb  4 23:31 .
  drwxr-xr-x 3 root root 60 Feb  4 23:31 ..
  lrwxrwxrwx 1 root root 13 Feb  4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a 
-> ../../bcache0

  4.
  root@ubuntu:~# ls -al /dev/bcache/by-uuid
  ls: cannot access '/dev/bcache/by-uuid': No such file or 

[Touch-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0

[Rafael David Tinoco]

Alright, summarizing this so far, we have the following fixes landed in
Groovy:

udev (systemd pkg):

- 60-persistent-storage.rules: skip_bcache_fs_type:
  - /dev/disk/by-uuid/_ and /dev/disk/by-label/_ not created for bcache devs

Since it does not make sense to have the caching device symlink like if
it was a regular filesystem disk to be used:

(k)rafaeldtinoco@bcache:~$ ls -lah /dev/disk/by-uuid
total 0
drwxr-xr-x 2 root root 100 Jul 21 18:49 .
drwxr-xr-x 7 root root 140 Jul 21 17:39 ..
lrwxrwxrwx 1 root root  10 Jul 21 17:39 022E-07E1 -> ../../vda1
lrwxrwxrwx 1 root root  13 Jul 21 18:49 50b98f0d-c0e0-49d2-9856-8ac6bc91e232 -> 
../../bcache0
lrwxrwxrwx 1 root root  10 Jul 21 17:39 67993d4f-fa55-49b1-886e-c692f88393ba -> 
../../vda2

- 69-bcache.rules:
  - if any other driver - than bcache - touches /dev/bcache[0-9]*
bcache/by-uuid/_ (BCACHE_CACHED_UUID and LABEL) symlinks are
recreated.

To address the udev event responsible for wiping /dev/bcache/by-uuid,
like:

KERNEL[4175.725930] change   /devices/virtual/block/bcache0 (block)
ACTION=change
DEVPATH=/devices/virtual/block/bcache0
SUBSYSTEM=block
SYNTH_UUID=0
DEVNAME=/dev/bcache0
DEVTYPE=disk
SEQNUM=6746
MAJOR=251
MINOR=0
 
UDEV  [4175.758078] change   /devices/virtual/block/bcache0 (block)
ACTION=change
DEVPATH=/devices/virtual/block/bcache0
SUBSYSTEM=block
SYNTH_UUID=0
DEVNAME=/dev/bcache0
DEVTYPE=disk
SEQNUM=6746
USEC_INITIALIZED=4151438558
ID_FS_UUID=50b98f0d-c0e0-49d2-9856-8ac6bc91e232
ID_FS_UUID_ENC=50b98f0d-c0e0-49d2-9856-8ac6bc91e232
ID_FS_VERSION=1.0
ID_FS_TYPE=ext4
ID_FS_USAGE=filesystem
MAJOR=251
MINOR=0
DEVLINKS=/dev/disk/by-uuid/50b98f0d-c0e0-49d2-9856-8ac6bc91e232
TAGS=:systemd:

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

Title:
  bcache by-uuid links disappear after mounting bcache0

Status in bcache-tools package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in bcache-tools source package in Bionic:
  Triaged
Status in systemd source package in Bionic:
  Triaged
Status in bcache-tools source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Triaged

Bug description:
  1.
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  2. 
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  root@ubuntu:~# apt-cache policy linux-image-virtual 
  linux-image-virtual:
Installed: 5.4.0.12.15
Candidate: 5.4.0.12.15
Version table:
   *** 5.4.0.12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic 
  linux-image-5.4.0-12-generic:
Installed: 5.4.0-12.15
Candidate: 5.4.0-12.15
Version table:
   *** 5.4.0-12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/
  + ls -al /dev/bcache/by-uuid/
  total 0
  drwxr-xr-x 2 root root 60 Feb  4 23:31 .
  drwxr-xr-x 3 root root 60 Feb  4 23:31 ..
  lrwxrwxrwx 1 root root 13 Feb  4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a 
-> ../../bcache0

  4.
  root@ubuntu:~# ls -al /dev/bcache/by-uuid
  ls: cannot access '/dev/bcache/by-uuid': No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Tue Feb  4 23:31:52 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+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 1861941] Re: bcache by-uuid links disappear after mounting bcache0

[Rafael David Tinoco]

** No longer affects: util-linux (Ubuntu)

** No longer affects: bcache-tools (Ubuntu Groovy)

** Changed in: bcache-tools (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: bcache-tools (Ubuntu)
   Importance: High => Medium

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

** Changed in: systemd (Ubuntu Bionic)
   Status: New => Triaged

** Changed in: systemd (Ubuntu Focal)
   Status: Confirmed => Triaged

** Changed in: bcache-tools (Ubuntu Bionic)
   Status: New => Triaged

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

Title:
  bcache by-uuid links disappear after mounting bcache0

Status in bcache-tools package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in bcache-tools source package in Bionic:
  Triaged
Status in systemd source package in Bionic:
  Triaged
Status in bcache-tools source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Triaged

Bug description:
  1.
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  2. 
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  root@ubuntu:~# apt-cache policy linux-image-virtual 
  linux-image-virtual:
Installed: 5.4.0.12.15
Candidate: 5.4.0.12.15
Version table:
   *** 5.4.0.12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic 
  linux-image-5.4.0-12-generic:
Installed: 5.4.0-12.15
Candidate: 5.4.0-12.15
Version table:
   *** 5.4.0-12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/
  + ls -al /dev/bcache/by-uuid/
  total 0
  drwxr-xr-x 2 root root 60 Feb  4 23:31 .
  drwxr-xr-x 3 root root 60 Feb  4 23:31 ..
  lrwxrwxrwx 1 root root 13 Feb  4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a 
-> ../../bcache0

  4.
  root@ubuntu:~# ls -al /dev/bcache/by-uuid
  ls: cannot access '/dev/bcache/by-uuid': No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Tue Feb  4 23:31:52 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+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 1861941] Re: bcache by-uuid links disappear after mounting bcache0

[Rafael David Tinoco]

** No longer affects: linux-signed (Ubuntu Bionic)

** No longer affects: linux-signed (Ubuntu Groovy)

** No longer affects: linux-signed (Ubuntu Focal)

** No longer affects: linux (Ubuntu Groovy)

** Changed in: systemd (Ubuntu Groovy)
 Assignee: Balint Reczey (rbalint) => (unassigned)

** No longer affects: linux (Ubuntu Focal)

** No longer affects: linux (Ubuntu Bionic)

** Also affects: util-linux (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: bcache-tools (Ubuntu Groovy)
   Status: Triaged => Confirmed

** No longer affects: systemd (Ubuntu Groovy)

** Changed in: bcache-tools (Ubuntu Focal)
   Importance: Undecided => Medium

** Changed in: bcache-tools (Ubuntu Bionic)
   Importance: Undecided => Medium

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

** Changed in: systemd (Ubuntu Bionic)
   Importance: Undecided => Medium

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

Title:
  bcache by-uuid links disappear after mounting bcache0

Status in bcache-tools package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in bcache-tools source package in Bionic:
  Triaged
Status in systemd source package in Bionic:
  Triaged
Status in bcache-tools source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Triaged

Bug description:
  1.
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  2. 
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  root@ubuntu:~# apt-cache policy linux-image-virtual 
  linux-image-virtual:
Installed: 5.4.0.12.15
Candidate: 5.4.0.12.15
Version table:
   *** 5.4.0.12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic 
  linux-image-5.4.0-12-generic:
Installed: 5.4.0-12.15
Candidate: 5.4.0-12.15
Version table:
   *** 5.4.0-12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/
  + ls -al /dev/bcache/by-uuid/
  total 0
  drwxr-xr-x 2 root root 60 Feb  4 23:31 .
  drwxr-xr-x 3 root root 60 Feb  4 23:31 ..
  lrwxrwxrwx 1 root root 13 Feb  4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a 
-> ../../bcache0

  4.
  root@ubuntu:~# ls -al /dev/bcache/by-uuid
  ls: cannot access '/dev/bcache/by-uuid': No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Tue Feb  4 23:31:52 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+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 1861941] Re: bcache by-uuid links disappear after mounting bcache0

[Rafael David Tinoco]

Thanks Marian... I'm now currently working on this issue and will
provide feedback soon here...

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

Title:
  bcache by-uuid links disappear after mounting bcache0

Status in bcache-tools package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Fix Released
Status in bcache-tools source package in Bionic:
  New
Status in linux source package in Bionic:
  New
Status in linux-signed source package in Bionic:
  New
Status in systemd source package in Bionic:
  New
Status in bcache-tools source package in Focal:
  Confirmed
Status in linux source package in Focal:
  Invalid
Status in linux-signed source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Confirmed
Status in bcache-tools source package in Groovy:
  Triaged
Status in linux source package in Groovy:
  Incomplete
Status in linux-signed source package in Groovy:
  Confirmed
Status in systemd source package in Groovy:
  Fix Released

Bug description:
  1.
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

  2. 
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu Focal Fossa (development branch)
  Release:  20.04
  root@ubuntu:~# apt-cache policy linux-image-virtual 
  linux-image-virtual:
Installed: 5.4.0.12.15
Candidate: 5.4.0.12.15
Version table:
   *** 5.4.0.12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status
  root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic 
  linux-image-5.4.0-12-generic:
Installed: 5.4.0-12.15
Candidate: 5.4.0-12.15
Version table:
   *** 5.4.0-12.15 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/
  + ls -al /dev/bcache/by-uuid/
  total 0
  drwxr-xr-x 2 root root 60 Feb  4 23:31 .
  drwxr-xr-x 3 root root 60 Feb  4 23:31 ..
  lrwxrwxrwx 1 root root 13 Feb  4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a 
-> ../../bcache0

  4.
  root@ubuntu:~# ls -al /dev/bcache/by-uuid
  ls: cannot access '/dev/bcache/by-uuid': No such file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-12-generic 5.4.0-12.15
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  Date: Tue Feb  4 23:31:52 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: linux-signed-5.4
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+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 1817955] Re: Getting new "DN is out of the realm subtree" error on adding principal

[Rafael David Tinoco]

** Also affects: krb5 (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: krb5 (Ubuntu Trusty)
   Status: New => Triaged

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

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

Title:
  Getting new "DN is out of the realm subtree" error on adding principal

Status in krb5 package in Ubuntu:
  Fix Released
Status in krb5 source package in Trusty:
  Triaged

Bug description:
  Recently applied security update to 14.04.5 LTS kerberos (1.12+dfsg-
  2ubuntu5.4), and started getting errors when adding new principals to
  LDAP.

  Obfuscated example:

  kadmin.local -q "ank -x
  dn=\"uid=testuser,ou=People,dc=example,dc=com\" -pw \"dummypass\"
  testuser"

  now gives:
  Authenticating as principal root/ad...@test.example.com with password.
  NOTICE: no policy specified for testu...@test.example.com; assigning "default"
  add_principal: DN is out of the realm subtree while creating 
"testu...@test.example.com".

  
  This worked up through 1.12+dfsg-2ubuntu5.3, and I think it now fails due to 
changes in src/plugins/kdb/ldap/libkdb_ldap/ldap_principal2.c in response to 
CVE-2018-5729 or CVE-2018-5730.

  I'm going to attempt a downgrade to 1.12+dfsg-2ubuntu5.3 to check.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1817955/+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 1557157] Re: apparmor profile denied for saslauthd: /run/saslauthd/mux

[Rafael David Tinoco]

** Also affects: openldap (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: openldap (Ubuntu Trusty)
   Status: New => Triaged

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

Title:
  apparmor profile denied for saslauthd: /run/saslauthd/mux

Status in openldap package in Ubuntu:
  Incomplete
Status in openldap source package in Trusty:
  Triaged

Bug description:
  When using slapd with saslauthd the processes communicate via the
  {,/var}/run/saslauthd/mux socket (this is the default location for the
  saslauthd server from the sasl2-bin package in the
  /etc/default/saslauthd config), but the apparmor profile for
  usr.sbin.slapd does not allow access to this socket/file.

  Syslog message:
  apparmor="DENIED" operation="connect" profile="/usr/sbin/slapd" 
name="/run/saslauthd/mux" pid=1880
  4 comm="slapd" requested_mask="r" denied_mask="r" fsuid=108 ouid=0

  
  Please add the following line to  /etc/apparmor.d/usr.sbin.slapd:
  /{,var/}run/saslauthd/mux rw,

  
  Ubuntu version: Ubuntu 14.04.4 LTS
  slapd version: 2.4.31-1+nmu2ubu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1557157/+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 1878945] Re: crash slapd after update

[Rafael David Tinoco]

Okay, so next step here is to understand if there is any margin for the
upgrade execution path to have removed slapd database, just to make sure
it is good (that is why I'm not marking this as incomplete).

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

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

Title:
  crash slapd after update

Status in openldap package in Ubuntu:
  Triaged

Bug description:
  hi,
  after update slapd to version 2.4.42+dfsg-2ubuntu3.8 I get not working ldap 
auth service;

  perform: slaptest -f /etc/ldap/slapd.conf -F /etc/ldap/slapd.d/ and
  get:

  5ebeb45f hdb_db_open: database "dc=myBase": 
db_open(/var/lib/ldap/id2entry.bdb) failed: No such file or directory (2).
  5ebeb45f backend_startup_one (type=hdb, suffix="dc=myBase"): bi_db_open 
failed! (2)
  slap_startup failed (test would succeed using the -u switch)

  journalctl -xe

  -- Unit slapd.service has finished starting up.
  --
  -- The start-up result is done.
  May 15 18:25:33 srv sshd[3917]: Connection closed by IP port PORT1 [preauth]
  May 15 18:26:32 srv sshd[3919]: Connection closed by IP port PORT2 [preauth]
  May 15 18:27:21 srv systemd[1]: Starting Daily apt download activities...
  -- Subject: Unit apt-daily.service has begun start-up
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  --
  -- Unit apt-daily.service has begun starting up.
  May 15 18:27:23 srv systemd[1]: Started Daily apt download activities.
  -- Subject: Unit apt-daily.service has finished start-up
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  --
  -- Unit apt-daily.service has finished starting up.
  --
  -- The start-up result is done.
  May 15 18:27:32 srv sshd[3987]: Connection closed by IP port PORT3 [preauth]
  May 15 18:28:04 srv systemd[1]: Stopping LSB: OpenLDAP standalone server 
(Lightweight Directory Access Protocol)...
  -- Subject: Unit slapd.service has begun shutting down
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  --
  -- Unit slapd.service has begun shutting down.
  May 15 18:28:04 srv slapd[4020]:  * Stopping OpenLDAP slapd
  May 15 18:28:14 srv slapd[4020]:...fail!
  May 15 18:28:14 svr systemd[1]: slapd.service: Control process exited, 
code=exited status=1
  May 15 18:28:14 srv systemd[1]: Stopped LSB: OpenLDAP standalone server 
(Lightweight Directory Access Protocol).
  -- Subject: Unit slapd.service has finished shutting down
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  --
  -- Unit slapd.service has finished shutting down.
  May 15 18:28:14 srv systemd[1]: slapd.service: Unit entered failed state.
  May 15 18:28:14 srv systemd[1]: slapd.service: Failed with result 'exit-code'.
  May 15 18:28:14 srv systemd[1]: Starting LSB: OpenLDAP standalone server 
(Lightweight Directory Access Protocol)...
  -- Subject: Unit slapd.service has begun start-up
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  --
  -- Unit slapd.service has begun starting up.
  May 15 18:28:15 srv slapd[4029]:  * Starting OpenLDAP slapd
  May 15 18:28:15 srv slapd[4029]:...done.
  May 15 18:28:15 srv systemd[1]: Started LSB: OpenLDAP standalone server 
(Lightweight Directory Access Protocol).
  -- Subject: Unit slapd.service has finished start-up
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  --
  -- Unit slapd.service has finished starting up.
  --
  -- The start-up result is done.

  OS: Ubuntu 16.04.6 LTS

  help, please!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1878945/+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 1878945] Re: crash slapd after update

[Rafael David Tinoco]

It says that your ldap database cannot be opened... There is a debconf
option that says:

"Do you want the database to be removed when slapd is purged?"

I wonder if you had that enabled before the upgrade.

During slapd upgrade, it asks to create a backup of /var/lib/slapd:

(c)rafaeldtinoco@focal:/var/lib/ldap$ sudo dpkg-reconfigure -p low slapd 
  Backing up /etc/ldap/slapd.d in /var/backups/slapd-2.4.49+dfsg-2ubuntu1.2... 
done.
  Moving old database directory to /var/backups:
  - directory unknown... done.
  Creating initial configuration... done.
  Creating LDAP directory... done.

Do you have anything under /var/backups/* named '*slapd*' ?

** Changed in: openldap (Ubuntu)
   Status: New => Triaged

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

Title:
  crash slapd after update

Status in openldap package in Ubuntu:
  Triaged

Bug description:
  hi,
  after update slapd to version 2.4.42+dfsg-2ubuntu3.8 I get not working ldap 
auth service;

  perform: slaptest -f /etc/ldap/slapd.conf -F /etc/ldap/slapd.d/ and
  get:

  5ebeb45f hdb_db_open: database "dc=myBase": 
db_open(/var/lib/ldap/id2entry.bdb) failed: No such file or directory (2).
  5ebeb45f backend_startup_one (type=hdb, suffix="dc=myBase"): bi_db_open 
failed! (2)
  slap_startup failed (test would succeed using the -u switch)

  journalctl -xe

  -- Unit slapd.service has finished starting up.
  --
  -- The start-up result is done.
  May 15 18:25:33 srv sshd[3917]: Connection closed by IP port PORT1 [preauth]
  May 15 18:26:32 srv sshd[3919]: Connection closed by IP port PORT2 [preauth]
  May 15 18:27:21 srv systemd[1]: Starting Daily apt download activities...
  -- Subject: Unit apt-daily.service has begun start-up
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  --
  -- Unit apt-daily.service has begun starting up.
  May 15 18:27:23 srv systemd[1]: Started Daily apt download activities.
  -- Subject: Unit apt-daily.service has finished start-up
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  --
  -- Unit apt-daily.service has finished starting up.
  --
  -- The start-up result is done.
  May 15 18:27:32 srv sshd[3987]: Connection closed by IP port PORT3 [preauth]
  May 15 18:28:04 srv systemd[1]: Stopping LSB: OpenLDAP standalone server 
(Lightweight Directory Access Protocol)...
  -- Subject: Unit slapd.service has begun shutting down
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  --
  -- Unit slapd.service has begun shutting down.
  May 15 18:28:04 srv slapd[4020]:  * Stopping OpenLDAP slapd
  May 15 18:28:14 srv slapd[4020]:...fail!
  May 15 18:28:14 svr systemd[1]: slapd.service: Control process exited, 
code=exited status=1
  May 15 18:28:14 srv systemd[1]: Stopped LSB: OpenLDAP standalone server 
(Lightweight Directory Access Protocol).
  -- Subject: Unit slapd.service has finished shutting down
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  --
  -- Unit slapd.service has finished shutting down.
  May 15 18:28:14 srv systemd[1]: slapd.service: Unit entered failed state.
  May 15 18:28:14 srv systemd[1]: slapd.service: Failed with result 'exit-code'.
  May 15 18:28:14 srv systemd[1]: Starting LSB: OpenLDAP standalone server 
(Lightweight Directory Access Protocol)...
  -- Subject: Unit slapd.service has begun start-up
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  --
  -- Unit slapd.service has begun starting up.
  May 15 18:28:15 srv slapd[4029]:  * Starting OpenLDAP slapd
  May 15 18:28:15 srv slapd[4029]:...done.
  May 15 18:28:15 srv systemd[1]: Started LSB: OpenLDAP standalone server 
(Lightweight Directory Access Protocol).
  -- Subject: Unit slapd.service has finished start-up
  -- Defined-By: systemd
  -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
  --
  -- Unit slapd.service has finished starting up.
  --
  -- The start-up result is done.

  OS: Ubuntu 16.04.6 LTS

  help, please!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1878945/+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 1764044] Re: ssh-add asks about passphrases for keys already unlocked in the keychain

[Rafael David Tinoco]

Rolf,

Thank you for taking the time to file a bug report.

I have just used the following in my .bashrc (like keychain man page
says so):

"""
keychain id_rsa id_dsa id_ecdsa

[ -z "$HOSTNAME" ] && HOSTNAME=`uname -n`
[ -f $HOME/.keychain/$HOSTNAME-sh ] && . $HOME/.keychain/$HOSTNAME-sh
[ -f $HOME/.keychain/$HOSTNAME-sh-gpg ] && . $HOME/.keychain/$HOSTNAME-sh-gpg
"""

and I have all my keys already set:

"""
 * keychain 2.8.5 ~ http://www.funtoo.org
 * Found existing ssh-agent: 3684816
 * Known ssh key: /home/rafaeldtinoco/.ssh/id_rsa
 * Known ssh key: /home/rafaeldtinoco/.ssh/id_dsa
 * Known ssh key: /home/rafaeldtinoco/.ssh/id_ecdsa

rafaeldtinoco@workstation:~$ 
"""

for every new shell. Just needed to put my password once.

Since it seems likely to me that this is a local configuration problem,
rather than a bug in Ubuntu, I am marking this bug as 'Incomplete'.

However, if you believe that this is really a bug in Ubuntu, then we would
be grateful if you would provide a more complete description of the problem
with steps to reproduce, explain why you believe this is a bug in Ubuntu
rather than a problem specific to your system, and then change the bug
status back to "New".

For local configuration issues, you can find assistance here:
http://www.ubuntu.com/support/community


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

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

Title:
  ssh-add asks about passphrases for keys already unlocked in the
  keychain

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  In the below example, on the second invocation of ssh-add I should not
  be prompted to enter the passphrase again after I successfully entered
  it on the first instance.  This used to work fine in trusty i386
  setup.

  $ keychain && ssh-add

   * keychain 2.8.2 ~ http://www.funtoo.org
   * Starting ssh-agent...

  Enter passphrase for /home/rolf/.ssh/id_rsa:
  Identity added: /home/rolf/.ssh/id_rsa (/home/rolf/.ssh/id_rsa)
  Enter passphrase for /home/rolf/.ssh/id_dsa:
  Identity added: /home/rolf/.ssh/id_dsa (/home/rolf/.ssh/id_dsa)

  $ keychain && ssh-add

   * keychain 2.8.2 ~ http://www.funtoo.org
   * Found existing ssh-agent: 25744

  Enter passphrase for /home/rolf/.ssh/id_rsa:
  Identity added: /home/rolf/.ssh/id_rsa (/home/rolf/.ssh/id_rsa)
  Enter passphrase for /home/rolf/.ssh/id_dsa:
  Identity added: /home/rolf/.ssh/id_dsa (/home/rolf/.ssh/id_dsa)

  gnome-keyring is running:
  $ ps -ax|grep key
   2067 ?SLl0:05 /usr/bin/gnome-keyring-daemon --start --components 
ssh
   2078 ?Ssl0:01 
/usr/lib/x86_64-linux-gnu/indicator-keyboard/indicator-keyboard-service 
--use-gtk
   6987 ?S  0:00 /usr/bin/ssh-agent -D -a 
/run/user/1000/keyring/.ssh
  17832 pts/2S+ 0:00 grep --color=auto key

  ssh-agent is running:
  $ ps aux | grep ssh-agent
  leggewie  1928  0.0  0.0  15548   340 ?Ss   02:38   0:00 
/usr/bin/ssh-agent /usr/bin/im-launch env LD_PRELOAD=libgtk3-nocsd.so.0 
/usr/lib/gnome-session/run-systemd-session unity-session.target
  leggewie  6987  0.0  0.0  11304  1484 ?S02:50   0:00 
/usr/bin/ssh-agent -D -a /run/user/1000/keyring/.ssh
  leggewie  9952  0.0  0.0  11304   320 ?Ss   04:11   0:00 ssh-agent 
bash
  leggewie 17850  0.0  0.0  14492  1160 pts/2S+   06:06   0:00 grep 
--color=auto ssh-agent

  $ env|grep SSH
  SSH_AUTH_SOCK=/tmp/ssh-W6fuGBztRRds/agent.6992
  SSH_AGENT_PID=9952
  SSH_AGENT_LAUNCHER=gnome-keyring

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1764044/+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 1879450] Re: clvm package and it executables are missed in the Ubuntu 20.04 LTS

[Rafael David Tinoco]

@nrbbrtx:

LVM2 has deprecated clvm in favor of lvmlockd (lvm2-lockd in Focal) only
for VG access coordination AND it can use either DLM (dlm-controld) or
sanlock (sanlock) as lock managers.

http://manpages.ubuntu.com/manpages/focal/man8/lvmlockd.8.html

>From an upstream discussion thread, the lvmlockd benefits over clvm are:

"""
- lvmlockd supports two cluster locking plugins: dlm and sanlock. sanlock 
plugin can supports up to ~2000 nodes that benefits LVM usage in big 
virtualization / storage cluster, while dlm plugin fits HA cluster.

- lvmlockd has better design than clvmd. clvmd is command-line level based 
locking system, which means the  whole LVM software will get hang if any LVM 
command gets dead-locking issue. However, lvmlockd is *resources* based cluster 
locking. The resources to protect is VG and LV so that the deadlock issue will 
be isolated inside the resource and
operations on other VG/LV can still proceed.

- lvmlockd can work with lvmetad.
"""

Now, instead of using the clvm pacemaker resource agent, you should use:

lvmlockdagent manages the lvmlockd daemon.

from the available resource agents list:

https://discourse.ubuntu.com/t/ubuntu-ha-pacemaker-resource-agents-
supportability/15729


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

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

Title:
  clvm package and it executables are missed in the Ubuntu 20.04 LTS

Status in lvm2 package in Ubuntu:
  Invalid

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 18.04 LTS with `lvm2` and `clvm` installed
  2. Plan the upgrade to 20.04 LTS

  Expected results:
  * the binaries from `clvm` package (/usr/sbin/clvmd and /usr/sbin/cmirrord) 
exist in 20.04 LTS system

  Actual results:
  * the `clvm` package is not built for 20.04 LTS, the /usr/sbin/clvmd and 
/usr/sbin/cmirrord are missed in the Ubuntu 20.04 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1879450/+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 1876486] Re: Kernel panic booting after 18.04 to 20.04 upgrade

[Rafael David Tinoco]

Moving back to incomplete as stated by @paelzer.

** Changed in: libseccomp (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Kernel panic booting after 18.04 to 20.04 upgrade

Status in libseccomp package in Ubuntu:
  Incomplete

Bug description:
  Upgraded Ubuntu 18.04 to 20.04.  Following the upgrade, booting was not 
possible.  The error messages is:
  /sbin/init: symbol lookup error: /lib/systemd/libsystemd-shared-245.so: 
undefined symbol: seccomp_api_get
  [4.608900] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x7f00
  See also attached photograph of screen during boot.

  Upgrade followed steps from here: 
https://help.ubuntu.com/community/FocalUpgrades/Kubuntu
  With the excpetion that The -d flag was used for the do-release-upgrade:
  sudo do-release-upgrade -d -m desktop

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Prior to upgrade: Ubuntu 18.04.4
  After upgrade (but never booted): Ubuntu (Kubuntu) 20.04
  Note that Ubuntu had originally be installed, but kubuntu-desktop was 
recently installed to change to Kubuntu, but no booting problems were 
experienced before updating to 20.04.

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in 
  Unknown -- Package version may have changed when upgrading to 20.04.

  3) What you expected to happen
  Boot without kernel panic.

  4) What happened instead
  Could not boot.  Even selecting safe mode from grub could not boot.  Had to 
restore system from backups.  Will not attempt upgrade again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1876486/+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 1876230] Re: liburcu: Enable MEMBARRIER_CMD_PRIVATE_EXPEDITED to address performance problems with MEMBARRIER_CMD_SHARED

[Rafael David Tinoco]

@sil2100,

thanks for the trust. My TL;DR version for you is:

>From one of liburcu maintainers (https://github.com/compudj):

"""
Posted Nov 24, 2013 23:55 UTC (Sun) by compudj (subscriber, #43335) [Link]

Tracking threads running in multiple processes using a common shared memory is 
not possible with the currently implemented URCU flavors, but we look forward 
to adding a new URCU flavor to support this kind of use case.
"""

So that satisfies the corner case I have thought of.

By that, I'm +1 on the SRU.



continuing the longer version...

> I agree with @ddstreet, I don't think liburcu gives that sort of
guarantee when it comes to cross process synchronisation. It was my
belief that liburcu targets synchronisation across a set of threads
within the current process only.

It does not (like stated above) but I had to check, specially cause I
was just checking by the membarrier() syscall point of view (not too
much into liburcu implementation).

NOW with all that I got curious =)...

>From liburcu documentation:

"""
There are multiple flavors of liburcu available:

memb, qsbr, mb, signal, bp.

The API members start with the prefix "urcu__", where is the chosen
flavor name.

Usage of liburcu-memb

#include 

Link the application with -lurcu-memb

This is the preferred version of the library, in terms of grace-period
detection speed, read-side speed and flexibility. Dynamically detects
kernel support for sys_membarrier().

Falls back on urcu-mb scheme if support is not present, which has slower
read-side. Use the --disable-sys-membarrier-fallback configure option to
disable the fall back, thus requiring sys_membarrier() to be available.
This gives a small speedup when sys_membarrier() is supported by the
kernel, and aborts in the library constructor if not supported.

Usage of liburcu-qsbr

#include 

Link with -lurcu-qsbr

The QSBR flavor of RCU needs to have each reader thread executing
rcu_quiescent_state() periodically to progress. rcu_thread_online() and
rcu_thread_offline() can be used to mark long periods for which the
threads are not active. It provides the fastest read-side at the expense
of more intrusiveness in the application code.

Usage of liburcu-mb

#include 

Link with -lurcu-mb

This version of the urcu library uses memory barriers on the writer and
reader sides. This results in faster grace-period detection, but results
in slower reads.

Usage of liburcu-signal

#include 

Link the application with -lurcu-signal

Version of the library that requires a signal, typically SIGUSR1. Can be
overridden with -DSIGRCU by modifying Makefile.build.inc.

Usage of liburcu-bp

#include 

Link with -lurcu-bp

The BP library flavor stands for "bulletproof". It is specifically
designed to help tracing library to hook on applications without
requiring to modify these applications.

urcu_bp_init(), and urcu_bp_unregister_thread() all become nops, whereas 
calling urcu_bp_register_thread() becomes optional. The state is dealt with by 
the library internally at the expense of read-side and write-side performance.
"""

> If the program links against liburcu 0.9 or lower, the sys_membarrier
syscall did not exist yet, and liburcu will use the default compiler
based membarrier, which is only good within the current process.
Synchronisation across shared memory pages fails. This is the case on
Xenial, Trusty and the like.

> If the program links against liburcu 0.11 or newer, the sys_membarrier
syscall does exist, but MEMBARRIER_CMD_SHARED is only used if the
current running kernel does not support
MEMBARRIER_CMD_PRIVATE_EXPEDITED.

Yep. Showed here => https://tinyurl.com/y96692o8

> There is no toggle option in the API at all, so for users with a
kernel 4.14 or higher, MEMBARRIER_CMD_PRIVATE_EXPEDITED will be used,
and synchronisation across shared memory pages will fail. This is the
case on Eoan, Focal, Groovy.

Understood and agreed. The SRU line of thinking is always "not
introducing regressions" so I was more interested in the "change of
behavior" (even if "it is all broken").

> If the program links against liburcu 0.10, and uses the -qsbr, -md and 
> -signal variants, sys_membarrier is not used at all, and it falls back to the 
> compiler based membarrier, which is only good within the current process. 
> Synchronisation across shared memory pages 
will fail.

Agreed per documentation.

> If the program links against liburcu 0.10, and is used within a
container, with a kernel version less than 4.3 that does not support
sys_membarrier, such as a Bionic container on a Trusty 3.13 host, or on
a 3.10 RHEL host, the sys_membarrier syscall fails, and it falls back to
the compiler based membarrier. Synchronisation across shared memory
pages will fail.

Agreed, per "urcu_bp_sys_membarrier_status()".

> Now, the upstream developers added MEMBARRIER_CMD_PRIVATE_EXPEDITED as
the default in liburcu 0.11. They did not change the API to accommodate
both MEMBARRIER_CMD_SHARED and MEMBARRIER_CMD_PRIVATE_EXPEDITED, 

[Touch-packages] [Bug 1815101] Re: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted)

[Rafael David Tinoco]

@napsty: the "workaround" (from your blog) is actually to use:

- ifupdown/bridge-utils/vlan/resolvconf for network setup   OR
- use systemd-networkd DIRECTLY with the KeepConfiguration= option in .network 
file

Just highlighting it here.

@ddstreet, you said you would try to come up with the netplan change for
KeepConfiguration. Did you have time to check on this ? (just checking).

Cheers o/

** Changed in: keepalived (Ubuntu)
 Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)

** Changed in: keepalived (Ubuntu Xenial)
     Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)

** Changed in: keepalived (Ubuntu Bionic)
 Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)

** Changed in: keepalived (Ubuntu Disco)
     Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)

** Changed in: keepalived (Ubuntu Eoan)
 Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)

** Changed in: systemd (Ubuntu)
 Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)

** Changed in: systemd (Ubuntu Xenial)
 Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)

** Changed in: systemd (Ubuntu Bionic)
 Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)

** Changed in: systemd (Ubuntu Disco)
 Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)

** Changed in: systemd (Ubuntu Eoan)
 Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)

** Changed in: netplan
 Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)

** No longer affects: keepalived (Ubuntu Eoan)

** No longer affects: keepalived (Ubuntu Disco)

** Also affects: heartbeat (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: keepalived (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: systemd (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

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

** No longer affects: heartbeat (Ubuntu Focal)

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

Title:
  [master] Restarting systemd-networkd breaks keepalived, heartbeat,
  corosync, pacemaker (interface aliases are restarted)

Status in netplan:
  Confirmed
Status in heartbeat package in Ubuntu:
  Won't Fix
Status in keepalived package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  In Progress
Status in keepalived source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Confirmed
Status in keepalived source package in Bionic:
  Confirmed
Status in systemd source package in Bionic:
  Confirmed
Status in systemd source package in Disco:
  Won't Fix
Status in systemd source package in Eoan:
  Fix Released
Status in keepalived source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Fix Released

Bug description:
  [impact]

  - ALL related HA software has a small problem if interfaces are being
  managed by systemd-networkd: nic restarts/reconfigs are always going
  to wipe all interfaces aliases when HA software is not expecting it to
  (no coordination between them.

  - keepalived, smb ctdb, pacemaker, all suffer from this. Pacemaker is
  smarter in this case because it has a service monitor that will
  restart the virtual IP resource, in affected node & nic, before
  considering a real failure, but other HA service might consider a real
  failure when it is not.

  [test case]

  - comment #14 is a full test case: to have 3 node pacemaker, in that
  example, and cause a networkd service restart: it will trigger a
  failure for the virtual IP resource monitor.

  - other example is given in the original description for keepalived.
  both suffer from the same issue (and other HA softwares as well).

  [regression potential]

  - this backports KeepConfiguration parameter, which adds some
  significant complexity to networkd's configuration and behavior, which
  could lead to regressions in correctly configuring the network at
  networkd start, or incorrectly maintaining configuration at networkd
  restart, or losing network state at networkd stop.

  - Any regressions are most likely to occur during networkd start,
  restart, or stop, and most likely to involve missing or incorrect ip
  address(es).

  - the change is based in upstream patches adding the exact feature we
  needed to fix this issue & it will be integrated with a netplan change
  to add the needed stanza to systemd nic configuration file
  (KeepConfiguration=)

  [other info]

  original description:
  ---

  Configure netplan for interfaces, for example (a working config with
  IP addresses obfuscated)

  network:
  ethernets:
  eth0:
   

[Touch-packages] [Bug 1815101] Re: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted)

[Rafael David Tinoco]

TL;DR TODO SUMMARY:

- netplan change to support KeepConfiguration= for systemd-networkd backend 
(Groovy)
- backport this change: netplan for Ubuntu Focal  (SRU)
- backport this change: netplan for Ubuntu Eoan   (SRU, WontFix due to EOL ?)
- backport this change: netplan for Ubuntu Bionic (SRU)
- backport this change: netplan for Ubuntu Xenial (SRU, WontFix ?)

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

Title:
  [master] Restarting systemd-networkd breaks keepalived, heartbeat,
  corosync, pacemaker (interface aliases are restarted)

Status in netplan:
  Confirmed
Status in heartbeat package in Ubuntu:
  Won't Fix
Status in keepalived package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  In Progress
Status in keepalived source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Confirmed
Status in keepalived source package in Bionic:
  Confirmed
Status in systemd source package in Bionic:
  Confirmed
Status in systemd source package in Disco:
  Won't Fix
Status in systemd source package in Eoan:
  Fix Released
Status in keepalived source package in Focal:
  Confirmed
Status in systemd source package in Focal:
  Fix Released

Bug description:
  [impact]

  - ALL related HA software has a small problem if interfaces are being
  managed by systemd-networkd: nic restarts/reconfigs are always going
  to wipe all interfaces aliases when HA software is not expecting it to
  (no coordination between them.

  - keepalived, smb ctdb, pacemaker, all suffer from this. Pacemaker is
  smarter in this case because it has a service monitor that will
  restart the virtual IP resource, in affected node & nic, before
  considering a real failure, but other HA service might consider a real
  failure when it is not.

  [test case]

  - comment #14 is a full test case: to have 3 node pacemaker, in that
  example, and cause a networkd service restart: it will trigger a
  failure for the virtual IP resource monitor.

  - other example is given in the original description for keepalived.
  both suffer from the same issue (and other HA softwares as well).

  [regression potential]

  - this backports KeepConfiguration parameter, which adds some
  significant complexity to networkd's configuration and behavior, which
  could lead to regressions in correctly configuring the network at
  networkd start, or incorrectly maintaining configuration at networkd
  restart, or losing network state at networkd stop.

  - Any regressions are most likely to occur during networkd start,
  restart, or stop, and most likely to involve missing or incorrect ip
  address(es).

  - the change is based in upstream patches adding the exact feature we
  needed to fix this issue & it will be integrated with a netplan change
  to add the needed stanza to systemd nic configuration file
  (KeepConfiguration=)

  [other info]

  original description:
  ---

  Configure netplan for interfaces, for example (a working config with
  IP addresses obfuscated)

  network:
  ethernets:
  eth0:
  addresses: [192.168.0.5/24]
  dhcp4: false
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  eth2:
  addresses:
    - 12.13.14.18/29
    - 12.13.14.19/29
  gateway4: 12.13.14.17
  dhcp4: false
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  eth3:
  addresses: [10.22.11.6/24]
  dhcp4: false
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  eth4:
  addresses: [10.22.14.6/24]
  dhcp4: false
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  eth7:
  addresses: [9.5.17.34/29]
  dhcp4: false
  optional: true
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  version: 2

  Configure keepalived (again, a working config with IP addresses
  obfuscated)

  global_defs   # Block id
  {
  notification_email {
  sysadm...@blah.com
  }
  notification_email_from keepali...@system3.hq.blah.com
  smtp_server 10.22.11.7 # IP
  smtp_connect_timeout 30  # integer, seconds
  router_id system3  # string identifying the machine,
   # (doesn't have 

[Touch-packages] [Bug 1582899] Re: in-target: mkinitramfs: failed to determine device for /

[Rafael David Tinoco]

I'm marking this as incomplete for 18.04.2 and wont fix for xenial based
on @ahasenack's last input.

** Also affects: base-installer (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: initramfs-tools (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: live-installer (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: base-installer (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: initramfs-tools (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: live-installer (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: live-installer (Ubuntu)
   Status: Confirmed => Incomplete

** Changed in: live-installer (Ubuntu Bionic)
   Status: New => Incomplete

** Changed in: live-installer (Ubuntu Xenial)
   Status: New => Won't Fix

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

Title:
  in-target: mkinitramfs: failed to determine device for /

Status in base-installer package in Ubuntu:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Invalid
Status in live-installer package in Ubuntu:
  Incomplete
Status in base-installer source package in Xenial:
  New
Status in initramfs-tools source package in Xenial:
  New
Status in live-installer source package in Xenial:
  Won't Fix
Status in base-installer source package in Bionic:
  New
Status in initramfs-tools source package in Bionic:
  New
Status in live-installer source package in Bionic:
  Incomplete

Bug description:
  Sysadmin reported in #ubuntu (later #ubuntu-kernel) the 16.04 ubuntu-
  server ISO installer failed due to being unable to configure linux-
  image-4.4.0-21-generic.

  Lots of diagnostics and one SSH remote session later we seem to have
  narrowed it down to the installer.

  At the installer's boot menu the F6 option "Expert mode" is chosen.

  During initial ram file-system creation (after the kernel image is installed) 
the /dev/ file-system is not mounted in /target/ and therefore
  the initramfs-tools/hook-functions::dep_add_modules_mount() cannot match
  the mount device of "/" (in this case /dev/sda3) with any node under /dev/ 
which only contains static entries.

  Cause appears to be that live-installer.postinst has the crucial step
  calling library.sh:setup_dev() commented out:

  #waypoint 1 setup_dev

  OS=linux
  setup_dev() calls setup_dev_${OS}
  setup_dev_linux() mounts procfs and devtmpfs into /target/

  

  Originally the cause of the error message appeared to be that the
  symlink names in /dev/disk/by-uuid/  haven't been updated after the
  partitioning stage if there were pre-existing partitions and file-
  systems on the install device, *and* the sysadmin chose to format the
  existing partitions when selecting mountpoints.

  In this case a hardware RAID device presents:

  /dev/sda1 (/boot/)
  /dev/sda2 (swap)
  /dev/sda3 (/)

  From the shell I noticed:

  root@tmpstorage:/# ll /dev/disk/by-uuid/
  total 0
  lrwxrwxrwx 1 root root  10 May 17 19:39 130e4419-4bfd-46d2-87f9-62e5379bf591 
-> ../../sda1
  lrwxrwxrwx 1 root root  10 May 17 19:39 127d3fa1-c07c-48e4-9e26-1b926d37625c 
-> ../../sda3
  lrwxrwxrwx 1 root root  10 May 17 19:39 78b88456-2b0b-4265-9ed2-5db61522d887 
-> ../../sda2
  lrwxrwxrwx 1 root root   9 May 17 19:39 2016-04-20-22-45-29-00 -> ../../sr1
  drwxr-xr-x 6 root root 120 May 17 19:39 ..
  drwxr-xr-x 2 root root 120 May 17 19:39 .

  root@tmpstorage:/# blkid /dev/sda*
  /dev/sda: PTUUID="a84e60fd" PTTYPE="dos"
  /dev/sda1: UUID="61365714-8ff7-47a2-8035-8aed9e3191a6" TYPE="ext4" 
PARTUUID="a84e60fd-01"
  /dev/sda2: UUID="78b88456-2b0b-4265-9ed2-5db61522d887" TYPE="swap" 
PARTUUID="a84e60fd-02"
  /dev/sda3: UUID="75f68451-9472-47c7-9efc-ed032bfa9987" TYPE="ext4" 
PARTUUID="a84e60fd-03"

  More details to follow.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-installer/+bug/1582899/+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 1582899] Re: in-target: mkinitramfs: failed to determine device for /

[Rafael David Tinoco]

Thank you for taking the time to file a bug report.

Since there is not enough information in your report to begin triage or to
differentiate between a local configuration problem and a bug in Ubuntu, I
am marking this bug as "Incomplete". We would be grateful if you would:
provide a more complete description of the problem, explain why you
believe this is a bug in Ubuntu rather than a problem specific to your
system, and then change the bug status back to "New".

For local configuration issues, you can find assistance here:
http://www.ubuntu.com/support/community

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

Title:
  in-target: mkinitramfs: failed to determine device for /

Status in base-installer package in Ubuntu:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Invalid
Status in live-installer package in Ubuntu:
  Incomplete
Status in base-installer source package in Xenial:
  New
Status in initramfs-tools source package in Xenial:
  New
Status in live-installer source package in Xenial:
  Won't Fix
Status in base-installer source package in Bionic:
  New
Status in initramfs-tools source package in Bionic:
  New
Status in live-installer source package in Bionic:
  Incomplete

Bug description:
  Sysadmin reported in #ubuntu (later #ubuntu-kernel) the 16.04 ubuntu-
  server ISO installer failed due to being unable to configure linux-
  image-4.4.0-21-generic.

  Lots of diagnostics and one SSH remote session later we seem to have
  narrowed it down to the installer.

  At the installer's boot menu the F6 option "Expert mode" is chosen.

  During initial ram file-system creation (after the kernel image is installed) 
the /dev/ file-system is not mounted in /target/ and therefore
  the initramfs-tools/hook-functions::dep_add_modules_mount() cannot match
  the mount device of "/" (in this case /dev/sda3) with any node under /dev/ 
which only contains static entries.

  Cause appears to be that live-installer.postinst has the crucial step
  calling library.sh:setup_dev() commented out:

  #waypoint 1 setup_dev

  OS=linux
  setup_dev() calls setup_dev_${OS}
  setup_dev_linux() mounts procfs and devtmpfs into /target/

  

  Originally the cause of the error message appeared to be that the
  symlink names in /dev/disk/by-uuid/  haven't been updated after the
  partitioning stage if there were pre-existing partitions and file-
  systems on the install device, *and* the sysadmin chose to format the
  existing partitions when selecting mountpoints.

  In this case a hardware RAID device presents:

  /dev/sda1 (/boot/)
  /dev/sda2 (swap)
  /dev/sda3 (/)

  From the shell I noticed:

  root@tmpstorage:/# ll /dev/disk/by-uuid/
  total 0
  lrwxrwxrwx 1 root root  10 May 17 19:39 130e4419-4bfd-46d2-87f9-62e5379bf591 
-> ../../sda1
  lrwxrwxrwx 1 root root  10 May 17 19:39 127d3fa1-c07c-48e4-9e26-1b926d37625c 
-> ../../sda3
  lrwxrwxrwx 1 root root  10 May 17 19:39 78b88456-2b0b-4265-9ed2-5db61522d887 
-> ../../sda2
  lrwxrwxrwx 1 root root   9 May 17 19:39 2016-04-20-22-45-29-00 -> ../../sr1
  drwxr-xr-x 6 root root 120 May 17 19:39 ..
  drwxr-xr-x 2 root root 120 May 17 19:39 .

  root@tmpstorage:/# blkid /dev/sda*
  /dev/sda: PTUUID="a84e60fd" PTTYPE="dos"
  /dev/sda1: UUID="61365714-8ff7-47a2-8035-8aed9e3191a6" TYPE="ext4" 
PARTUUID="a84e60fd-01"
  /dev/sda2: UUID="78b88456-2b0b-4265-9ed2-5db61522d887" TYPE="swap" 
PARTUUID="a84e60fd-02"
  /dev/sda3: UUID="75f68451-9472-47c7-9efc-ed032bfa9987" TYPE="ext4" 
PARTUUID="a84e60fd-03"

  More details to follow.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-installer/+bug/1582899/+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 1876230] Re: liburcu: Enable MEMBARRIER_CMD_PRIVATE_EXPEDITED to address performance problems with MEMBARRIER_CMD_SHARED

[Rafael David Tinoco]

Sorry to jump in, I wrote the membarrier syscall LTP interface test
(https://github.com/linux-test-
project/ltp/blob/master/testcases/kernel/syscalls/membarrier/membarrier01.c)
when I was at Linaro and felt attracted to reading all this during my
bug triage day =).

So, for MEMBARRIER_CMD_PRIVATE_EXPEDITED, you said at the description:

" It only targets threads which share the same mm as the thread calling
the membarrier syscall "

And it occurred to me right away:

"Are there any dependencies using liburcu and Shared Mem IPC" ?

Mainly because the private expedited only guarantees the barrier - for
the RCU graceful period - among sibling tasks sharing the same address
space and thread id (which share the same mm) -> of course this explains
why it is much faster, specially in an OS containing tons of running
tasks.. or even worse: in a VM with tons of running tasks PLUS vcpus
coming in and out the real ones.

So, I think my message here, specially for the SRU team, as this is
changing the behavior of librcu library for a LTS version, is:

- apart from feedback given by @mruffell, to also check if any of librcu
consumers are depending on a full membarrier - driven by kernel - for **
shared pages among different processes **

before accepting this as a SRU. Or else we're changing synchronization
primitives of all dependencies and this would not be good =o).

I think this criteria may also help in the SRU acceptance ^

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

Title:
  liburcu: Enable MEMBARRIER_CMD_PRIVATE_EXPEDITED to address
  performance problems with MEMBARRIER_CMD_SHARED

Status in liburcu package in Ubuntu:
  Fix Released
Status in liburcu source package in Bionic:
  In Progress

Bug description:
  [Impact]

  In Linux 4.3, a new syscall was defined, called "membarrier". This
  systemcall was defined specifically for use in userspace-rcu (liburcu)
  to speed up the fast path / reader side of the library. The original
  implementation in Linux 4.3 only supported the MEMBARRIER_CMD_SHARED
  subcommand of the membarrier syscall.

  MEMBARRIER_CMD_SHARED executes a memory barrier on all threads from
  all processes running on the system. When it exits, the userspace
  thread which called it is guaranteed that all running threads share
  the same world view in regards to userspace addresses which are
  consumed by readers and writers.

  The problem with MEMBARRIER_CMD_SHARED is system calls made in this
  fashion can block, since it deploys a barrier across all threads in a
  system, and some other threads can be waiting on blocking operations,
  and take time to reach the barrier.

  In Linux 4.14, this was addressed by adding the
  MEMBARRIER_CMD_PRIVATE_EXPEDITED command to the membarrier syscall. It
  only targets threads which share the same mm as the thread calling the
  membarrier syscall, aka, threads in the current process, and not all
  threads / processes in the system.

  Calls to membarrier with the MEMBARRIER_CMD_PRIVATE_EXPEDITED command
  are guaranteed non-blocking, due to using inter-processor interrupts
  to implement memory barriers.

  Because of this, membarrier calls that use
  MEMBARRIER_CMD_PRIVATE_EXPEDITED are much faster than those that use
  MEMBARRIER_CMD_SHARED.

  Since Bionic uses a 4.15 kernel, all kernel requirements are met, and
  this SRU is to enable support for MEMBARRIER_CMD_PRIVATE_EXPEDITED in
  the liburcu package.

  This brings the performance of the liburcu library back in line to
  where it was in Trusty, as this particular user has performance
  problems upon upgrading from Trusty to Bionic.

  [Test]

  Testing performance is heavily dependant on the application which
  links against liburcu, and the workload which it executes.

  A test package is available in the following ppa:
  https://launchpad.net/~mruffell/+archive/ubuntu/sf276198-test

  For the sake of testing, we can use the benchmarks provided in the
  liburcu source code. Download a copy of the source code for liburcu
  either from the repos or from github:

  $ pull-lp-source liburcu bionic
  # OR
  $ git clone https://github.com/urcu/userspace-rcu.git
  $ git checkout v0.10.1 # version in bionic

  Build the code:

  $ ./bootstrap
  $ ./configure
  $ make

  Go into the tests/benchmark directory

  $ cd tests/benchmark

  From there, you can run benchmarks for the four main usages of
  liburcu: urcu, urcu-bp, urcu-signal and urcu-mb.

  On a 8 core machine, 6 threads for readers and 2 threads for writers,
  with a 10 second runtime, execute:

  $ ./test_urcu 6 2 10
  $ ./test_urcu_bp 6 2 10
  $ ./test_urcu_signal 6 2 10
  $ ./test_urcu_mb 6 2 10

  Results:

  ./test_urcu 6 2 10
  0.10.1-1: 17612527667 reads, 268 writes, 17612527935 ops
  0.10.1-1ubuntu1: 14988437247 reads, 810069 writes, 14989247316 ops

  $ ./test_urcu_bp 6 2 10
  0.10.1-1: 1177891079 

[Touch-packages] [Bug 1876787] [NEW] Keyboard Shortcuts didn't working.

[Rafael Gimenes]

Public bug reported:

Addded the "Super + 2", "Super + 3" and "Super + 4" commands to switch
to the 2,3,and 4 Workspaces and it's not working.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
Uname: Linux 5.4.0-28-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon May  4 15:17:49 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Sony Corporation 2nd Generation Core Processor Family Integrated 
Graphics Controller [104d:908a]
InstallationDate: Installed on 2020-04-24 (9 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: Sony Corporation VPCEG15FB
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic 
root=UUID=f4a823e2-8306-4dcc-a6bc-c34ec67ae110 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/06/2012
dmi.bios.vendor: INSYDE
dmi.bios.version: R0240Z8
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnINSYDE:bvrR0240Z8:bd01/06/2012:svnSonyCorporation:pnVPCEG15FB:pvrC902GW09:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.family: VAIO
dmi.product.name: VPCEG15FB
dmi.product.sku: N/A
dmi.product.version: C902GW09
dmi.sys.vendor: Sony Corporation
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu

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

Title:
  Keyboard Shortcuts didn't working.

Status in xorg package in Ubuntu:
  New

Bug description:
  Addded the "Super + 2", "Super + 3" and "Super + 4" commands to switch
  to the 2,3,and 4 Workspaces and it's not working.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May  4 15:17:49 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Sony Corporation 2nd Generation Core Processor Family 
Integrated Graphics Controller [104d:908a]
  InstallationDate: Installed on 2020-04-24 (9 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: Sony Corporation VPCEG15FB
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic 
root=UUID=f4a823e2-8306-4dcc-a6bc-c34ec67ae110 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/06/2012
  dmi.bios.vendor: INSYDE
  dmi.bios.version: R0240Z8
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnINSYDE:bvrR0240Z8:bd01/06/2012:svnSonyCorporation:pnVPCEG15FB:pvrC902GW09:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: VAIO
  dmi.product.name: VPCEG15FB
  dmi.product.sku: N/A
  dmi.product.version: C902GW09
  dmi.sys.vendor: Sony Corporation
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2
  

[Touch-packages] [Bug 1875697] Re: drop fix-ldap-distribution.patch?

[Rafael David Tinoco]

(c)rafaeldtinoco@devel:~$ rmadison openldap
 openldap | 2.4.28-1.1ubuntu4  | precise  | source
 openldap | 2.4.28-1.1ubuntu4.6| precise-security | source
 openldap | 2.4.28-1.1ubuntu4.6| precise-updates  | source
 openldap | 2.4.31-1+nmu2ubuntu8   | trusty   | source
 openldap | 2.4.31-1+nmu2ubuntu8.4 | trusty-security  | source
 openldap | 2.4.31-1+nmu2ubuntu8.5 | trusty-updates   | source
 openldap | 2.4.42+dfsg-2ubuntu3   | xenial   | source
 openldap | 2.4.42+dfsg-2ubuntu3.6 | xenial-security  | source
 openldap | 2.4.42+dfsg-2ubuntu3.7 | xenial-updates   | source
 openldap | 2.4.45+dfsg-1ubuntu1   | bionic   | source
 openldap | 2.4.45+dfsg-1ubuntu1.3 | bionic-security  | source
 openldap | 2.4.45+dfsg-1ubuntu1.4 | bionic-updates   | source
 openldap | 2.4.47+dfsg-3ubuntu2   | disco| source
 openldap | 2.4.47+dfsg-3ubuntu2.1 | disco-security   | source
 openldap | 2.4.47+dfsg-3ubuntu2.2 | disco-updates| source
 openldap | 2.4.48+dfsg-1ubuntu1   | eoan | source
 openldap | 2.4.49+dfsg-2ubuntu1   | focal| source
 openldap | 2.4.49+dfsg-2ubuntu1   | groovy   | source

Since we haven't synced with dfsg-3 for focal, I'm marking this as
server-next for groovy. For next merge, I would suggest this to be SRUed
for Focal as well, and leave for the SRU team to decide. Since its a
very small change, I'm flagging as blocking next SRU to focal, perhaps
one can add it to the next SRU.

** Tags added: server-next

** Tags added: block-proposed-focal

** Also affects: openldap (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: openldap (Ubuntu)
   Status: New => Triaged

** Changed in: openldap (Ubuntu Focal)
   Status: New => Triaged

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

Title:
  drop fix-ldap-distribution.patch?

Status in openldap package in Ubuntu:
  Triaged
Status in openldap source package in Focal:
  Triaged

Bug description:
  Hi,

  In version 2.4.49+dfsg-3 I fixed a bug where the version was missing
  from the -V output in OpenLDAP programs:
  .

  At the same time, I've patched it to display the package version
  there, instead of the upstream version:

  # slapd -VV
  @(#) $OpenLDAP: slapd 2.4.49+dfsg-4 (Apr 15 2020 04:33:16) $
Debian OpenLDAP Maintainers 

  If showing the distro version here fulfills the same requirements as
  the fix-ldap-distribution.patch, then maybe that patch can be dropped?

  Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1875697/+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 1875036] Re: bridge stops working on focal update

[Rafael David Tinoco]

Hello Javier,

Actually the release notes for the version you were at:

https://wiki.ubuntu.com/BionicBeaver/ReleaseNotes#netplan.io

already deprecated ifupdown in favor of netplan.io.

Upgrade path to 20.04 has likely uninstalled bridge-utils because of
that. You can keep using ifupdown + vlan + bridge-utils + net-tools but
do have in mind that those tools are being deprecated in favor of:
systemd-networkd, netplan.io, iproute2, etc.

Good examples on how to obtain the same result using netplan.io can be
found at:

https://netplan.io/examples

For now I'm marking this as a Invalid bug. If think there is anything
else on this topic I would suggest writing to Ubuntu Users mailing list,
a correct place for community-based technical support.

Best regards,

Rafael D. Tinoco



** Changed in: bridge-utils (Ubuntu)
   Status: New => Invalid

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

Title:
  bridge stops working on focal update

Status in bridge-utils package in Ubuntu:
  Invalid

Bug description:
  Hi,

  I don't know if this is the right package to report but: I have
  upgraded to 20.04 from 18.04 and my network stopped working. Problem
  was that bridge-utils package was uninstalled, so network was unable
  to start. Reinstalling the package solved the problem. But I don't
  understand why it was uninstalled. I have reviewed the release note
  for 20.04 and I haven't seen the problem, so I'm reporting in case in
  can help anyone.

  Regards

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/1875036/+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 1827253] Re: [apparmor] missing 'mr' on binary for usage on containers

[Rafael David Tinoco]

Simon,

Could you please help identifying the current status of this bug ? Your
original merge requests were postponed to the next SRU for rsyslog in
Bionic, Disco and Eoan, correct ?

During verification time you discovered the difference between "bin" and
"sbin" for the apparmor rule, is that it ? Than the verifications have
been marked as failed.

>From @paelzers comments I see that Focal is good. Should we re-try a SRU
for *at least* Bionic here in this bug ? Or just let it hang for
documentation purposes if others face this (since SRU is too small to be
accepted directly) ?

Any thoughts ?

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

Title:
  [apparmor] missing 'mr' on binary for usage on containers

Status in rsyslog package in Ubuntu:
  Fix Released
Status in rsyslog source package in Bionic:
  In Progress
Status in rsyslog source package in Disco:
  In Progress
Status in rsyslog source package in Eoan:
  In Progress

Bug description:
  [Impact]

   * rsyslog ships with a (Default disable) apparmor profile.
   * Security sensitive users are in general encouraged to enable such
     profiles but unfortunately due to slightly new behavior of the program
     the profile prevents its usage.
   * Allow the program to map/read its binary to get this working again

  [Test Case]

  1) Create a 'eoan' container called rs1 here:
    lxc launch ubuntu-daily:e rs1
  2) Enter the container
    lxc shell rs1
  3) Enable apparmor profile
    rm /etc/apparmor.d/disable/usr.sbin.rsyslogd
    apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd
    systemctl restart rsyslog
  4) notice rsyslog failed to start
    systemctl status rsyslog

  [Regression Potential]

   * This is just opening up the apparmor profile a bit. Therefore the only
     regression it could cause IMHO is a security issue. But then what it
     actually allows is reading (not writing!) its own binary which should
     be very safe.
   * Thinking further it came to my mind that package updates (independent 
 to the change) might restart services and that means if there is any 
 issue e.g. in a local config that worked but now fails (not by this 
 change but in general) then the upgrade will not cause, but trigger 
 this. This is a general regression risk for any upload, but in this 
 case worth to mention as it is about log handling - which if broken - 
 makes large scale systems hard to debug.

  [Other Info]

   * n/a

  ---

  Issue description:

  Enabling the rsyslog (disabled by default) Apparmor profile causes
  rsyslog to fail to start when running *inside a container*.

  Steps to reproduce:

  1) Create a 'eoan' container called rs1 here:
    lxc launch ubuntu-daily:e rs1
  2) Enter the container
    lxc shell rs1
  3) Enable apparmor profile
    rm /etc/apparmor.d/disable/usr.sbin.rsyslogd
    apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd
    systemctl restart rsyslog
  4) notice rsyslog failed to start
    systemctl status rsyslog

  Workaround:

    echo '  /usr/sbin/rsyslogd mr,' >> /etc/apparmor.d/local/usr.sbin.rsyslogd
    apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd
    systemctl restart rsyslog

  Additional information:

  root@rs1:~# uname -a
  Linux rs1 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 
x86_64 x86_64 GNU/Linux
  root@rs1:~# lsb_release -rd
  Description:  Ubuntu Eoan EANIMAL (development branch)
  Release:  19.10
  root@rs1:~# dpkg -l| grep -wE 'apparmor|rsyslog'
  ii  apparmor 2.13.2-9ubuntu6  amd64user-space parser utility for 
AppArmor
  ii  rsyslog  8.32.0-1ubuntu7  amd64reliable system and kernel logging 
daemon

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: rsyslog 8.32.0-1ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Wed May  1 17:36:29 2019
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: rsyslog
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1827253/+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 1827253] Re: [apparmor] missing 'mr' on binary for usage on containers

[Rafael David Tinoco]

Marking as Fix Released for Disco:

+rsyslog (8.32.0-1ubuntu7.1) disco; urgency=medium
+
+  [ Simon Deziel ]
+  * d/usr.sbin.rsyslogd: allow reading/mmap'ing rsyslog binary
+This is required for usage inside containers (LP: #1827253)
+
+ -- Christian Ehrhardt   Mon, 14 Oct 2019 
08:53:03 +0200

Marking as Fix Released for Bionic:

+rsyslog (8.32.0-1ubuntu4.1) bionic; urgency=medium
+
+  [ Simon Deziel ]
+  * d/usr.sbin.rsyslogd: allow reading/mmap'ing rsyslog binary
+This is required for usage inside containers (LP: #1827253)
+
+ -- Christian Ehrhardt   Mon, 14 Oct 2019 
08:54:45 +0200
+


** Changed in: rsyslog (Ubuntu Bionic)
   Status: Triaged => Fix Released

** Changed in: rsyslog (Ubuntu Disco)
   Status: Triaged => Fix Released

** Changed in: rsyslog (Ubuntu Eoan)
   Status: Triaged => In Progress

** Changed in: rsyslog (Ubuntu Disco)
   Status: Fix Released => In Progress

** Changed in: rsyslog (Ubuntu Bionic)
   Status: Fix Released => In Progress

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

Title:
  [apparmor] missing 'mr' on binary for usage on containers

Status in rsyslog package in Ubuntu:
  Fix Released
Status in rsyslog source package in Bionic:
  In Progress
Status in rsyslog source package in Disco:
  In Progress
Status in rsyslog source package in Eoan:
  In Progress

Bug description:
  [Impact]

   * rsyslog ships with a (Default disable) apparmor profile.
   * Security sensitive users are in general encouraged to enable such
     profiles but unfortunately due to slightly new behavior of the program
     the profile prevents its usage.
   * Allow the program to map/read its binary to get this working again

  [Test Case]

  1) Create a 'eoan' container called rs1 here:
    lxc launch ubuntu-daily:e rs1
  2) Enter the container
    lxc shell rs1
  3) Enable apparmor profile
    rm /etc/apparmor.d/disable/usr.sbin.rsyslogd
    apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd
    systemctl restart rsyslog
  4) notice rsyslog failed to start
    systemctl status rsyslog

  [Regression Potential]

   * This is just opening up the apparmor profile a bit. Therefore the only
     regression it could cause IMHO is a security issue. But then what it
     actually allows is reading (not writing!) its own binary which should
     be very safe.
   * Thinking further it came to my mind that package updates (independent 
 to the change) might restart services and that means if there is any 
 issue e.g. in a local config that worked but now fails (not by this 
 change but in general) then the upgrade will not cause, but trigger 
 this. This is a general regression risk for any upload, but in this 
 case worth to mention as it is about log handling - which if broken - 
 makes large scale systems hard to debug.

  [Other Info]

   * n/a

  ---

  Issue description:

  Enabling the rsyslog (disabled by default) Apparmor profile causes
  rsyslog to fail to start when running *inside a container*.

  Steps to reproduce:

  1) Create a 'eoan' container called rs1 here:
    lxc launch ubuntu-daily:e rs1
  2) Enter the container
    lxc shell rs1
  3) Enable apparmor profile
    rm /etc/apparmor.d/disable/usr.sbin.rsyslogd
    apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd
    systemctl restart rsyslog
  4) notice rsyslog failed to start
    systemctl status rsyslog

  Workaround:

    echo '  /usr/sbin/rsyslogd mr,' >> /etc/apparmor.d/local/usr.sbin.rsyslogd
    apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd
    systemctl restart rsyslog

  Additional information:

  root@rs1:~# uname -a
  Linux rs1 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 
x86_64 x86_64 GNU/Linux
  root@rs1:~# lsb_release -rd
  Description:  Ubuntu Eoan EANIMAL (development branch)
  Release:  19.10
  root@rs1:~# dpkg -l| grep -wE 'apparmor|rsyslog'
  ii  apparmor 2.13.2-9ubuntu6  amd64user-space parser utility for 
AppArmor
  ii  rsyslog  8.32.0-1ubuntu7  amd64reliable system and kernel logging 
daemon

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: rsyslog 8.32.0-1ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  Date: Wed May  1 17:36:29 2019
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: rsyslog
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1872589] Re: systemd-networkd is not honoring UseRoutes=false

[Rafael David Tinoco]

*** This bug is a duplicate of bug 1867375 ***
https://bugs.launchpad.net/bugs/1867375

I'm marking this as a duplicate of your bug then...

** This bug has been marked a duplicate of bug 1867375
   systemd-networkd: Setting UseRoutes to False results in DHCP default gateway 
not being installed

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

Title:
  systemd-networkd is not honoring UseRoutes=false

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  When netplan configures dhcp4-overrides and set "use-routes" to false,
  systemd-networkd should be configured with UseRoutes=false. It is.
  Unfortunately looks like systemd-networkd is not honoring it and
  configuring the default gateways for the interfaces no matter what.

  Ubuntu Focal: systemd: 245.4-2ubuntu1

  

  $ sudo cat /etc/netplan/50-cloud-init.yaml
  network:
  ethernets:
  enp5s0:
  match:
  macaddress: 00:16:3e:af:c4:d6
  set-name: eth0
  dhcp4: true
  dhcp-identifier: mac
  enp6s0:
  match:
  macaddress: 00:16:3e:50:11:9c
  set-name: iscsi01
  dhcp4: true
  dhcp-identifier: mac
  dhcp4-overrides:
    use-routes: false
  enp7s0:
  match:
  macaddress: 00:16:3e:b3:cc:50
  set-name: iscsi02
  dhcp4: true
  dhcp-identifier: mac
  dhcp4-overrides:
    use-routes: false
  version: 2
  renderer: networkd

  

  $ cat /var/run/systemd/network/10-netplan-enp6s0.network

  [Match]
  MACAddress=00:16:3e:50:11:9c
  Name=iscsi01

  [Network]
  DHCP=ipv4
  LinkLocalAddressing=ipv6

  [DHCP]
  ClientIdentifier=mac
  RouteMetric=100
  UseMTU=true
  UseRoutes=false

  --

  $ ip route show | grep default
  default via 10.250.93.1 dev iscsi02 proto dhcp src 10.250.93.101 metric 100
  default via 10.250.94.1 dev iscsi01 proto dhcp src 10.250.94.167 metric 100
  default via 10.250.97.1 dev eth0 proto dhcp src 10.250.97.123 metric 100

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1872589/+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 1872589] Re: systemd-networkd is not honoring UseRoutes=false

[Rafael David Tinoco]

*** This bug is a duplicate of bug 1867375 ***
https://bugs.launchpad.net/bugs/1867375

Ahhh good to know, documentation in netplan.io doesn't reflect that
also, that is why I opened the bug. Funny because because of the
attribute name "UseRoutes" I was in doubt if it would get the default
gateway or just the published routes.. then the documentation said it
would get the default GW.

Thanks for letting me know Dan!

-> https://netplan.io/reference

Documenting it if anyone is confused by this as well:

"""
use-routes (bool)
Default: true. When true, the routes received from the DHCP server will be 
installed in the routing table normally. When set to false, routes from the 
DHCP server will be ignored: in this case, the user is responsible for adding 
static routes if necessary for correct network operation. This allows users to 
avoid installing a default gateway for interfaces configured via DHCP. 
Available for both the networkd and NetworkManager backends.
"""

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

Title:
  systemd-networkd is not honoring UseRoutes=false

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  When netplan configures dhcp4-overrides and set "use-routes" to false,
  systemd-networkd should be configured with UseRoutes=false. It is.
  Unfortunately looks like systemd-networkd is not honoring it and
  configuring the default gateways for the interfaces no matter what.

  Ubuntu Focal: systemd: 245.4-2ubuntu1

  

  $ sudo cat /etc/netplan/50-cloud-init.yaml
  network:
  ethernets:
  enp5s0:
  match:
  macaddress: 00:16:3e:af:c4:d6
  set-name: eth0
  dhcp4: true
  dhcp-identifier: mac
  enp6s0:
  match:
  macaddress: 00:16:3e:50:11:9c
  set-name: iscsi01
  dhcp4: true
  dhcp-identifier: mac
  dhcp4-overrides:
    use-routes: false
  enp7s0:
  match:
  macaddress: 00:16:3e:b3:cc:50
  set-name: iscsi02
  dhcp4: true
  dhcp-identifier: mac
  dhcp4-overrides:
    use-routes: false
  version: 2
  renderer: networkd

  

  $ cat /var/run/systemd/network/10-netplan-enp6s0.network

  [Match]
  MACAddress=00:16:3e:50:11:9c
  Name=iscsi01

  [Network]
  DHCP=ipv4
  LinkLocalAddressing=ipv6

  [DHCP]
  ClientIdentifier=mac
  RouteMetric=100
  UseMTU=true
  UseRoutes=false

  --

  $ ip route show | grep default
  default via 10.250.93.1 dev iscsi02 proto dhcp src 10.250.93.101 metric 100
  default via 10.250.94.1 dev iscsi01 proto dhcp src 10.250.94.167 metric 100
  default via 10.250.97.1 dev eth0 proto dhcp src 10.250.97.123 metric 100

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1872589/+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 1872589] [NEW] systemd-networkd is not honoring UseRoutes=false

[Rafael David Tinoco]

Public bug reported:

When netplan configures dhcp4-overrides and set "use-routes" to false,
systemd-networkd should be configured with UseRoutes=false. It is.
Unfortunately looks like systemd-networkd is not honoring it and
configuring the default gateways for the interfaces no matter what.

Ubuntu Focal: systemd: 245.4-2ubuntu1



$ sudo cat /etc/netplan/50-cloud-init.yaml
network:
ethernets:
enp5s0:
match:
macaddress: 00:16:3e:af:c4:d6
set-name: eth0
dhcp4: true
dhcp-identifier: mac
enp6s0:
match:
macaddress: 00:16:3e:50:11:9c
set-name: iscsi01
dhcp4: true
dhcp-identifier: mac
dhcp4-overrides:
  use-routes: false
enp7s0:
match:
macaddress: 00:16:3e:b3:cc:50
set-name: iscsi02
dhcp4: true
dhcp-identifier: mac
dhcp4-overrides:
  use-routes: false
version: 2
renderer: networkd



$ cat /var/run/systemd/network/10-netplan-enp6s0.network

[Match]
MACAddress=00:16:3e:50:11:9c
Name=iscsi01

[Network]
DHCP=ipv4
LinkLocalAddressing=ipv6

[DHCP]
ClientIdentifier=mac
RouteMetric=100
UseMTU=true
UseRoutes=false

--

$ ip route show | grep default
default via 10.250.93.1 dev iscsi02 proto dhcp src 10.250.93.101 metric 100
default via 10.250.94.1 dev iscsi01 proto dhcp src 10.250.94.167 metric 100
default via 10.250.97.1 dev eth0 proto dhcp src 10.250.97.123 metric 100

** Affects: systemd (Ubuntu)
 Importance: Undecided
 Status: Triaged

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

** Changed in: systemd (Ubuntu)
   Status: Confirmed => Triaged

** Description changed:

+ When netplan configures dhcp4-overrides and set "use-routes" to false,
+ systemd-networkd should be configured with UseRoutes=false. It is.
+ Unfortunately looks like systemd-networkd is not honoring it and
+ configuring the default gateways for the interfaces no matter what.
  
- When netplan configures dhcp4-overrides and set "use-routes" to false, 
systemd-networkd should be configured with UseRoutes=false. It is. 
Unfortunately looks like systemd-networkd is not honoring it and configuring 
the default gateways for the interfaces no matter what.
+ Ubuntu Focal: systemd: 245.4-2ubuntu1
  
  
  
  $ sudo cat /etc/netplan/50-cloud-init.yaml
  network:
- ethernets:
- enp5s0:
- match:
- macaddress: 00:16:3e:af:c4:d6
- set-name: eth0
- dhcp4: true
- dhcp-identifier: mac
- enp6s0:
- match:
- macaddress: 00:16:3e:50:11:9c
- set-name: iscsi01
- dhcp4: true
- dhcp-identifier: mac
- dhcp4-overrides:
-   use-routes: false
- enp7s0:
- match:
- macaddress: 00:16:3e:b3:cc:50
- set-name: iscsi02
- dhcp4: true
- dhcp-identifier: mac
- dhcp4-overrides:
-   use-routes: false
- version: 2
- renderer: networkd
+ ethernets:
+ enp5s0:
+ match:
+ macaddress: 00:16:3e:af:c4:d6
+ set-name: eth0
+ dhcp4: true
+ dhcp-identifier: mac
+ enp6s0:
+ match:
+ macaddress: 00:16:3e:50:11:9c
+ set-name: iscsi01
+ dhcp4: true
+ dhcp-identifier: mac
+ dhcp4-overrides:
+   use-routes: false
+ enp7s0:
+ match:
+ macaddress: 00:16:3e:b3:cc:50
+ set-name: iscsi02
+ dhcp4: true
+ dhcp-identifier: mac
+ dhcp4-overrides:
+   use-routes: false
+ version: 2
+ renderer: networkd
  
  
  
  $ cat /var/run/systemd/network/10-netplan-enp6s0.network
  
  [Match]
  MACAddress=00:16:3e:50:11:9c
  Name=iscsi01
  
  [Network]
  DHCP=ipv4
  LinkLocalAddressing=ipv6
  
  [DHCP]
  ClientIdentifier=mac
  RouteMetric=100
  UseMTU=true
  UseRoutes=false
  
  --
  
  $ ip route show | grep default
  default via 10.250.93.1 dev iscsi02 proto dhcp src 10.250.93.101 metric 100
  default via 10.250.94.1 dev iscsi01 proto dhcp src 10.250.94.167 metric 100
  default via 10.250.97.1 dev eth0 proto dhcp src 10.250.97.123 metric 100

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

Title:
  systemd-networkd is not honoring UseRoutes=false

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  When netplan configures dhcp4-overrides and set "use-routes" to false,
  systemd-networkd should be configured with UseRoutes=false. It is.
  Unfortunately looks like systemd-networkd is not honoring it and
  configuring 

[Touch-packages] [Bug 1871465] Re: ssh_config(5) contains outdated information

[Rafael David Tinoco]

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

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

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

Title:
  ssh_config(5) contains outdated information

Status in openssh package in Ubuntu:
  Triaged

Bug description:
  The release of OpenSSH 8.2 has removed `ssh-rsa` from the default list
  of CACertificateAlgorithms. However the latest `openssh-client` still
  ships the man page for ssh_config(5) that contains the following
  description:

   CASignatureAlgorithms
   Specifies which algorithms are allowed for signing of 
certificates 
   by certificate authorities (CAs).  The default is:

     
ecdsa-sha2-nistp256,ecdsa-sha2-nistp384,ecdsa-sha2-nistp521,
     ssh-ed25519,rsa-sha2-512,rsa-sha2-256,ssh-rsa

   ssh(1) will not accept host certificates signed using algorithms 
   other than those specified.

  As far as I am concerned, `ssh-rsa` should be dropped from the list so
  as to match the behavior of ssh(1).

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

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

Re: [Touch-packages] [Bug 1864992] Please test proposed package

[Rafael David Tinoco]

> Hello Paride, or anyone else affected,
> 
> Accepted kmod into bionic-proposed. The package will build now and be
> available at https://launchpad.net/ubuntu/+source/kmod/24-1ubuntu3.3 in
> a few hours, and then in the -proposed repository.

kmod (24-1ubuntu3.3) bionic; urgency=medium

  * d/p/verbose_missing_bin: drop this patch to avoid spurious missing
file messages when running depmod -a for the first time in recent
kernels (>= 5.3.x) (LP: #1864992)
  * Removed --add-udeb from dh_makeshlibs, since libkmod2-udeb does not
actually contain a library. (Closes: #939779)

 -- Rafael David Tinoco   Wed, 11 Mar 2020
19:37:06 +

(k)rafaeldtinoco@bkmodissue:~$ apt-cache policy kmod
kmod:
  Installed: 24-1ubuntu3.3
  Candidate: 24-1ubuntu3.3
  Version table:
 *** 24-1ubuntu3.3 500
500 http://us.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 
Packages
100 /var/lib/dpkg/status
 24-1ubuntu3.2 500
500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
 24-1ubuntu3 500
500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

(k)rafaeldtinoco@bkmodissue:~$ uname -a
Linux bkmodissue 5.3.0-42-generic #34~18.04.1-Ubuntu SMP Fri Feb 28 13:42:26 
UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
(k)rafaeldtinoco@bkmodissue:~$ sudo rm /lib/modules/$(uname 
-r)/modules.builtin.bin
(k)rafaeldtinoco@bkmodissue:~$ sudo depmod -a -F /boot/System.map-$(uname -r)
(k)rafaeldtinoco@bkmodissue:~$

(k)rafaeldtinoco@bkmodissue:~$ uname -a
Linux bkmodissue 5.0.0-43-generic #47~18.04.1-Ubuntu SMP Mon Mar 2 04:28:21 UTC 
2020 x86_64 x86_64 x86_64 GNU/Linux
(k)rafaeldtinoco@bkmodissue:~$ sudo rm /lib/modules/$(uname 
-r)/modules.builtin.bin
(k)rafaeldtinoco@bkmodissue:~$ sudo depmod -a -F /boot/System.map-$(uname -r)
(k)rafaeldtinoco@bkmodissue:~$


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

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

Title:
  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

Status in kmod package in Ubuntu:
  Fix Released
Status in kmod source package in Bionic:
  Fix Committed
Status in kmod source package in Disco:
  Won't Fix
Status in kmod source package in Eoan:
  Fix Committed
Status in kmod source package in Focal:
  Fix Released

Bug description:
  [Impact]

  * There is no impact to the end user but spurious error messages (tons
  of them) causing the perception that something really bad happened:

  Example of one of those tons of messages:

  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

  [Test Case]

  * sudo rm /lib/modules/$(uname -r)/modules.builtin.bin

  * sudo depmod -a -F /boot/System.map-$(uname -r)

  This will cause the spurious error messages because depmod -a -F won't
  have the "modules.builtin.bin" file created. This is a simulation of
  what the linux-modules postinst package does and an example of why the
  messages happen.

  [Regression Potential]

  * We are reverting a debian patch so we will be closer to upstream
  code base.

  * the change is about 2 different priority changes on verbosity, so
  biggest problem would be extra (or fewer) stdout/stderr messages (for
  scripts relying on them, for example).

  * I have tested with kernels 4.15, 5.0 and 5.3 and all of them seemed
  to work fine.

  [Other Info]

  * Original Description:

  During a Focal install from the ISO image several errors like:

  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

  are logged in curtin's install logs. The installed system boots and
  works fine, but the error is clearly something we want to get rid of.

  At first glance this seems related to:

  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1863261

  but the version of initramfs-tools in both the installer and installed
  system (checked with `chroot /target dpkg -l initramfs-tools` during
  the installation) is 0.136ubuntu1, which should contain Rafael's fix
  for that bug. I wonder if the update-initramfs diversion has a role
  here.

  I verified this happens at least on amd64 and arm64. I'm attaching the full 
install logs for a amd64 installation.
  ---
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-14-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesI

Re: [Touch-packages] [Bug 1864992] Re: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

[Rafael David Tinoco]

> Hello Paride, or anyone else affected,
> 
> Accepted kmod into eoan-proposed. The package will build now and be
> available at https://launchpad.net/ubuntu/+source/kmod/26-1ubuntu1.1 in
> a few hours, and then in the -proposed repository.

Verification for eoan-proposed:

(k)rafaeldtinoco@ekmodissue:~$ apt changelog kmod
Get:1 https://changelogs.ubuntu.com kmod 26-1ubuntu1.1 Changelog [21.1 kB]
Fetched 21.1 kB in 2s (10.4 kB/s)

kmod (26-1ubuntu1.1) eoan; urgency=medium

  * d/p/verbose_missing_bin: drop this patch to avoid spurious missing
file messages when running depmod -a for the first time in recent
kernels (>= 5.3.x) (LP: #1864992)
  * Removed --add-udeb from dh_makeshlibs, since libkmod2-udeb does not
actually contain a library. (Closes: #939779)

 -- Rafael David Tinoco   Wed, 11 Mar 2020
19:32:52 +

(k)rafaeldtinoco@ekmodissue:~$ apt-cache policy kmod
kmod:
  Installed: 26-1ubuntu1.1
  Candidate: 26-1ubuntu1.1
  Version table:
 *** 26-1ubuntu1.1 500
500 http://us.archive.ubuntu.com/ubuntu eoan-proposed/main amd64 
Packages
100 /var/lib/dpkg/status
 26-1ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages

(k)rafaeldtinoco@ekmodissue:~$ uname -a
Linux ekmodissue 5.3.0-43-generic #36-Ubuntu SMP Mon Mar 16 13:29:01 UTC 2020 
x86_64 x86_64 x86_64 GNU/Linux
(k)rafaeldtinoco@ekmodissue:~$ sudo rm /lib/modules/$(uname 
-r)/modules.builtin.bin
(k)rafaeldtinoco@ekmodissue:~$ sudo depmod -a -F /boot/System.map-$(uname -r)
(k)rafaeldtinoco@ekmodissue:~$

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

Title:
  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

Status in kmod package in Ubuntu:
  Fix Released
Status in kmod source package in Bionic:
  Fix Committed
Status in kmod source package in Disco:
  Won't Fix
Status in kmod source package in Eoan:
  Fix Committed
Status in kmod source package in Focal:
  Fix Released

Bug description:
  [Impact]

  * There is no impact to the end user but spurious error messages (tons
  of them) causing the perception that something really bad happened:

  Example of one of those tons of messages:

  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

  [Test Case]

  * sudo rm /lib/modules/$(uname -r)/modules.builtin.bin

  * sudo depmod -a -F /boot/System.map-$(uname -r)

  This will cause the spurious error messages because depmod -a -F won't
  have the "modules.builtin.bin" file created. This is a simulation of
  what the linux-modules postinst package does and an example of why the
  messages happen.

  [Regression Potential]

  * We are reverting a debian patch so we will be closer to upstream
  code base.

  * the change is about 2 different priority changes on verbosity, so
  biggest problem would be extra (or fewer) stdout/stderr messages (for
  scripts relying on them, for example).

  * I have tested with kernels 4.15, 5.0 and 5.3 and all of them seemed
  to work fine.

  [Other Info]

  * Original Description:

  During a Focal install from the ISO image several errors like:

  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

  are logged in curtin's install logs. The installed system boots and
  works fine, but the error is clearly something we want to get rid of.

  At first glance this seems related to:

  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1863261

  but the version of initramfs-tools in both the installer and installed
  system (checked with `chroot /target dpkg -l initramfs-tools` during
  the installation) is 0.136ubuntu1, which should contain Rafael's fix
  for that bug. I wonder if the update-initramfs diversion has a role
  here.

  I verified this happens at least on amd64 and arm64. I'm attaching the full 
install logs for a amd64 installation.
  ---
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-14-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperVersion: 1.439
  DistroRelease: Ubuntu 20.04
  IwConfig: Error: [Errno 2] No such 

[Touch-packages] [Bug 1868720] Re: backport time64 syscalls whitelist

[Rafael David Tinoco]

I believe the patch you're mentioning is worth backporting to Bionic and
Eoan is this:

$ git log -1 -p be65b26b67099be2b2b4890d736dbd1ad15adf36 | diffstat
 include/seccomp-syscalls.h|  208 +-
 src/arch-aarch64-syscalls.c   |   35 ++-
 src/arch-arm-syscalls.c   |   35 ++-
 src/arch-mips-syscalls.c  |   51 --
 src/arch-mips64-syscalls.c|   31 ++
 src/arch-mips64n32-syscalls.c |   31 ++
 src/arch-parisc-syscalls.c|   33 ++
 src/arch-ppc-syscalls.c   |   51 --
 src/arch-ppc64-syscalls.c |   53 --
 src/arch-s390-syscalls.c  |   57 ---
 src/arch-s390.c   |  160 
 src/arch-s390x-syscalls.c |   59 ---
 src/arch-s390x.c  |  160 
 src/arch-x32-syscalls.c   |   31 ++
 src/arch-x86-syscalls.c   |  105 ++---
 src/arch-x86.c|  161 
 src/arch-x86_64-syscalls.c|   31 ++
 17 files changed, 1150 insertions(+), 142 deletions(-)

and to be honest that seems appropriate as it only updates the tables
and allows supporting newer system calls for all arches.

** Changed in: libseccomp (Ubuntu)
   Status: New => Triaged

** Also affects: libseccomp (Ubuntu Focal)
   Importance: Undecided
   Status: Triaged

** Also affects: libseccomp (Ubuntu Eoan)
   Importance: Undecided
   Status: New

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

** Also affects: libseccomp (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Changed in: libseccomp (Ubuntu Focal)
   Status: Triaged => Fix Released

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

** Changed in: libseccomp (Ubuntu Disco)
   Status: New => Won't Fix

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

** Tags added: server-next

** Changed in: libseccomp (Ubuntu Bionic)
   Status: Confirmed => Triaged

** Changed in: libseccomp (Ubuntu Eoan)
   Status: Confirmed => Triaged

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

Title:
  backport time64 syscalls whitelist

Status in libseccomp package in Ubuntu:
  Fix Released
Status in libseccomp source package in Bionic:
  Triaged
Status in libseccomp source package in Disco:
  Won't Fix
Status in libseccomp source package in Eoan:
  Triaged
Status in libseccomp source package in Focal:
  Fix Released

Bug description:
  A number of new *time64 syscalls are introduced in newer kernel series
  (>=5.1.x):

  403: clock_gettime64
  404: clock_settime64
  405: clock_adjtime64
  406: clock_getres_time64
  407: clock_nanosleep_time64
  408: timer_gettime64
  409: timer_settime64
  410: timerfd_gettime64
  411: timerfd_settime64
  412: utimensat_time64
  413: pselect6_time64
  414: ppoll_time64

  In particular utimensat_time64 is now used inside glibc>=2.31

  In turn ubuntu with has trouble running docker images of newer distros.
  This problem affects libseccomp<2.4.2, ie bionic (lts), and eoan, but not 
focal.

  See a similar report at Fedora:
  https://bugzilla.redhat.com/show_bug.cgi?id=1770154

  A solution could be to backport the related changes from 2.4.2
  similarly to what happened for the statx whitelisting
  (https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1755250).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1868720/+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 1868720] Re: backport time64 syscalls whitelist

[Rafael David Tinoco]

Could you provide a failing test case so we can base the SRU (stable
release update) on that use it as a non-regression test ?

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

Title:
  backport time64 syscalls whitelist

Status in libseccomp package in Ubuntu:
  Fix Released
Status in libseccomp source package in Bionic:
  Triaged
Status in libseccomp source package in Disco:
  Won't Fix
Status in libseccomp source package in Eoan:
  Triaged
Status in libseccomp source package in Focal:
  Fix Released

Bug description:
  A number of new *time64 syscalls are introduced in newer kernel series
  (>=5.1.x):

  403: clock_gettime64
  404: clock_settime64
  405: clock_adjtime64
  406: clock_getres_time64
  407: clock_nanosleep_time64
  408: timer_gettime64
  409: timer_settime64
  410: timerfd_gettime64
  411: timerfd_settime64
  412: utimensat_time64
  413: pselect6_time64
  414: ppoll_time64

  In particular utimensat_time64 is now used inside glibc>=2.31

  In turn ubuntu with has trouble running docker images of newer distros.
  This problem affects libseccomp<2.4.2, ie bionic (lts), and eoan, but not 
focal.

  See a similar report at Fedora:
  https://bugzilla.redhat.com/show_bug.cgi?id=1770154

  A solution could be to backport the related changes from 2.4.2
  similarly to what happened for the statx whitelisting
  (https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1755250).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1868720/+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 1864992] Re: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

[Rafael David Tinoco]

Actually, I missed my previous fix:

---
This bug was fixed in the package kmod - 27-1ubuntu2

---
kmod (27-1ubuntu2) focal; urgency=medium

  * d/p/verbose_missing_bin: drop this patch to avoid spurious missing
file messages when running depmod -a for the first time in recent
kernels (>= 5.3.x) (LP: #1864992)

 -- Rafael David Tinoco  Thu, 12 Mar 2020 13:15:28 
+
---

and it should have taken care of this issue.. checking the given
example:

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-focal/focal/amd64/d/doit/20200323_182614_c1613@/log.gz

It turns out the kernel gets updated *before* kmod fix.. and that
triggers the buggy logic. For that not to happen we would have to have
an updated cloud-image (with kmod 27-1ubuntu2) or update kmod before the
kernel.

Marking it back to Fix Released, feel free to re-open it if you think
this is wrong.

** Changed in: kmod (Ubuntu Focal)
   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/1864992

Title:
  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

Status in kmod package in Ubuntu:
  Fix Released
Status in kmod source package in Bionic:
  Fix Committed
Status in kmod source package in Disco:
  Won't Fix
Status in kmod source package in Eoan:
  Fix Committed
Status in kmod source package in Focal:
  Fix Released

Bug description:
  [Impact]

  * There is no impact to the end user but spurious error messages (tons
  of them) causing the perception that something really bad happened:

  Example of one of those tons of messages:

  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

  [Test Case]

  * sudo rm /lib/modules/$(uname -r)/modules.builtin.bin

  * sudo depmod -a -F /boot/System.map-$(uname -r)

  This will cause the spurious error messages because depmod -a -F won't
  have the "modules.builtin.bin" file created. This is a simulation of
  what the linux-modules postinst package does and an example of why the
  messages happen.

  [Regression Potential]

  * We are reverting a debian patch so we will be closer to upstream
  code base.

  * the change is about 2 different priority changes on verbosity, so
  biggest problem would be extra (or fewer) stdout/stderr messages (for
  scripts relying on them, for example).

  * I have tested with kernels 4.15, 5.0 and 5.3 and all of them seemed
  to work fine.

  [Other Info]

  * Original Description:

  During a Focal install from the ISO image several errors like:

  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

  are logged in curtin's install logs. The installed system boots and
  works fine, but the error is clearly something we want to get rid of.

  At first glance this seems related to:

  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1863261

  but the version of initramfs-tools in both the installer and installed
  system (checked with `chroot /target dpkg -l initramfs-tools` during
  the installation) is 0.136ubuntu1, which should contain Rafael's fix
  for that bug. I wonder if the update-initramfs diversion has a role
  here.

  I verified this happens at least on amd64 and arm64. I'm attaching the full 
install logs for a amd64 installation.
  ---
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-14-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperVersion: 1.439
  DistroRelease: Ubuntu 20.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  LiveMediaBuild: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha amd64 (20200225)
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
 

[Touch-packages] [Bug 1864992] Re: depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could not open builtin file '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

[Rafael David Tinoco]

Thanks doko, focal was Fix Released for the original initramfs-tools,
iirc. That made me miss the fix for Focal. I'm applying the same fix
(Eoan/Bionic SRUs) to Focal.

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

Title:
  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

Status in kmod package in Ubuntu:
  New
Status in kmod source package in Bionic:
  Fix Committed
Status in kmod source package in Disco:
  Won't Fix
Status in kmod source package in Eoan:
  Fix Committed
Status in kmod source package in Focal:
  New

Bug description:
  [Impact]

  * There is no impact to the end user but spurious error messages (tons
  of them) causing the perception that something really bad happened:

  Example of one of those tons of messages:

  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

  [Test Case]

  * sudo rm /lib/modules/$(uname -r)/modules.builtin.bin

  * sudo depmod -a -F /boot/System.map-$(uname -r)

  This will cause the spurious error messages because depmod -a -F won't
  have the "modules.builtin.bin" file created. This is a simulation of
  what the linux-modules postinst package does and an example of why the
  messages happen.

  [Regression Potential]

  * We are reverting a debian patch so we will be closer to upstream
  code base.

  * the change is about 2 different priority changes on verbosity, so
  biggest problem would be extra (or fewer) stdout/stderr messages (for
  scripts relying on them, for example).

  * I have tested with kernels 4.15, 5.0 and 5.3 and all of them seemed
  to work fine.

  [Other Info]

  * Original Description:

  During a Focal install from the ISO image several errors like:

  depmod: ERROR: ../libkmod/libkmod.c:515 lookup_builtin_file() could
  not open builtin file
  '/lib/modules/5.4.0-14-generic/modules.builtin.bin'

  are logged in curtin's install logs. The installed system boots and
  works fine, but the error is clearly something we want to get rid of.

  At first glance this seems related to:

  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1863261

  but the version of initramfs-tools in both the installer and installed
  system (checked with `chroot /target dpkg -l initramfs-tools` during
  the installation) is 0.136ubuntu1, which should contain Rafael's fix
  for that bug. I wonder if the update-initramfs diversion has a role
  here.

  I verified this happens at least on amd64 and arm64. I'm attaching the full 
install logs for a amd64 installation.
  ---
  ProblemType: Bug
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k5.4.0-14-generic.
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu18
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CRDA: N/A
  Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer'
  Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer'
  CasperVersion: 1.439
  DistroRelease: Ubuntu 20.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  LiveMediaBuild: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha amd64 (20200225)
  Lsusb:
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  Package: linux (not installed)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
  ProcFB: 0 qxldrmfb
  ProcKernelCmdLine: initrd=/casper/initrd quiet  --- maybe-ubiquity
  ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18
  RelatedPackageVersions:
   linux-restricted-modules-5.4.0-14-generic N/A
   linux-backports-modules-5.4.0-14-generic  N/A
   linux-firmware1.186
  RfKill: Error: [Errno 2] No such