[Ubuntu-translations-coordinators] [Bug 2017606] Re: Chinese translation error in gnome-tweaks

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-tweaks - 45.1-1

---
gnome-tweaks (45.1-1) unstable; urgency=medium

  * New upstream release (LP: #2017606)
  * Stop using debian/control.in and dh_gnome_clean
  * Use dh-user-session-migration to clean up lid switch inhibitor
autostart file. That feature is no longer included in the Tweaks app.
(Closes: #863245, LP: #1968528, LP: #1931785)
  * Drop patches applied in new release

 -- Jeremy Bícha   Thu, 29 Feb 2024 20:15:15 -0500

** Changed in: gnome-tweaks (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching subscriptions: Ubuntu Translations bug mail
https://bugs.launchpad.net/bugs/2017606

Title:
  Chinese translation error in gnome-tweaks

Status in GNOME Tweaks:
  Invalid
Status in Ubuntu Translations:
  Fix Committed
Status in gnome-tweaks package in Ubuntu:
  Fix Released

Bug description:
  The "top bar" settings page apparently translate "day of week" into
  "工作日", while that means "working day".  Correct translation should be
  "星期”。

  This is a tiny bug and easy to fix. I hope triagers can explain how
  users can help fix these translation errors, hopefully directly on
  launchpad.

  System Info:

  Ubuntu 23.04
  GNOME Tweaks 42.beta
  GNOME Shell 44.0 （ubuntu 模式）
  GTK 3.24.37

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


___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 2016318] Re: free command: in Italian header is misaligned and wrongly translated

[Launchpad Bug Tracker]

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching subscriptions: Ubuntu Translations bug mail
https://bugs.launchpad.net/bugs/2016318

Title:
  free command: in Italian header is misaligned and wrongly translated

Status in Ubuntu Translations:
  Confirmed
Status in procps package in Ubuntu:
  Confirmed

Bug description:
  free command: in Italian header is misaligned and wrongly translated
  gratuiti is 'for free' or 'gratis' or 'toll free' 
  'free' may be translated with 'liberi'  

  total  = totali ... ok
  used   = usati  ... ok
  free   = liberi ... to be changed 
  shared = condivisi  ... ok
  buff/cache  ... ok 
  available = disponibili  ... ok

  corrado@corrado-n4-ll-beta:~$ free
 totalusedfree  shared  buff/cache   
available
  Mem:16151400 223667211599888  517412 3171440
13914728
  Swap:8388604   0 8388604
  corrado@corrado-n4-ll-beta:~$ 

  corradi@corrado-n4-ll-beta:~$ free
 buff/cache condivisi gratuiti totali utilizzati disponibili
  Mem:16151400 175200411850636  333144 3227540
14399396
  Swap:8388604   0 8388604
  corradi@corrado-n4-ll-beta:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: procps 2:4.0.3-1ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 14 18:34:49 2023
  InstallationDate: Installed on 2023-03-31 (14 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Beta amd64 (20230329)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: procps
  UpgradeStatus: No upgrade log present (probably fresh install)

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


___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1943049] [NEW] Docker ubuntu:impish: Problem executing scripts DPkg::Post-Invoke 'rm -f /var/cache/apt/archives/*.deb /var/cache/apt/archives/partial/*.deb /var

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Sometime betweek August 28 and September 4 2021 the ubuntu:impish images
published on dockerhub began erroring when executing the commands
defined in /etc/apt/apt.conf.d/docker-clean.

I have this reproducer, which is probably not as minimal as it can be
but looks reliable:

1. docker run -it --rm ubuntu:impish bash
2. apt update
3. apt install git
4. apt -y remove git

This results in:

E: Problem executing scripts DPkg::Post-Invoke 'rm -f 
/var/cache/apt/archives/*.deb /var/cache/apt/archives/partial/*.deb 
/var/cache/apt/*.bin || true'
E: Sub-process returned an error code

*Removing* a package is not strictly needed to trigger the failure, but
it seems that *two* apt operations are needed to trigger it, so this
reproducer found by athos-ribeiro also works:

docker run -it --rm ubuntu:impish /bin/bash -c 'apt-get update; apt-get
full-upgrade -y; apt-get install -y jq'

This doesn't happen when using ubuntu:hirsute.

** Affects: ubuntu-translations
 Importance: Undecided
 Status: Confirmed

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

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

** Affects: docker.io (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: golang-github-containers-common (Ubuntu)
 Importance: High
 Assignee: Reinhard Tartler (siretart)
 Status: Fix Released

** Affects: golang-github-opencontainers-specs (Ubuntu)
 Importance: Undecided
 Status: Fix Released

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

** Affects: containerd (Ubuntu Bionic)
 Importance: Undecided
 Status: Fix Released

** Affects: docker.io (Ubuntu Bionic)
 Importance: Undecided
 Status: Fix Released

** Affects: containerd (Ubuntu Focal)
 Importance: Undecided
 Status: Fix Released

** Affects: docker.io (Ubuntu Focal)
 Importance: Undecided
 Status: Fix Released

** Affects: containerd (Ubuntu Hirsute)
 Importance: Undecided
 Status: Fix Released

** Affects: docker.io (Ubuntu Hirsute)
 Importance: Undecided
 Status: Fix Released

** Affects: containerd (Ubuntu Impish)
 Importance: Undecided
 Status: Fix Released

** Affects: crun (Ubuntu Impish)
 Importance: Undecided
 Status: Won't Fix

** Affects: docker.io (Ubuntu Impish)
 Importance: Undecided
 Status: Fix Released

** Affects: golang-github-containers-common (Ubuntu Impish)
 Importance: High
 Assignee: Reinhard Tartler (siretart)
 Status: Fix Released

** Affects: golang-github-opencontainers-specs (Ubuntu Impish)
 Importance: Undecided
 Status: Fix Released

** Affects: libpod (Ubuntu Impish)
 Importance: Undecided
 Status: Fix Released


** Tags: fr-1704 verification-done verification-done-bionic 
verification-done-focal verification-done-hirsute
-- 
Docker ubuntu:impish: Problem executing scripts DPkg::Post-Invoke 'rm -f 
/var/cache/apt/archives/*.deb /var/cache/apt/archives/partial/*.deb 
/var/cache/apt/*.bin || true'
https://bugs.launchpad.net/bugs/1943049
You received this bug notification because you are a member of Ubuntu 
Translations Coordinators, which is subscribed to Ubuntu Translations.

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 2000937] Re: DING settings values shown untranslated

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-control-center -
1:44~alpha-0ubuntu1

---
gnome-control-center (1:44~alpha-0ubuntu1) lunar; urgency=medium

  [ Jeremy Bicha ]
  * New upstream release
  * debian/control.in: Bump minimum GTK4 to 4.8 and libnma-gtk4 to 1.10.2
  * Stop disabling the Device Security panel
  * Revert commit that hides Device Security panel when chassis_type is empty
  * Refresh patches
  * Update patches to drop deprecated gtk_widget_show/hide

  [ Gunnar Hjalmarsson ]
  * Make "Color" in "Appearance" view translatable (LP: #2000937)
  * Use a context aware gettext function in the Ubuntu panel (LP: #2000937)

 -- Jeremy Bicha   Fri, 13 Jan 2023 11:48:57 -0500

** Changed in: gnome-control-center (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching subscriptions: Ubuntu Translations bug mail
https://bugs.launchpad.net/bugs/2000937

Title:
  DING settings values shown untranslated

Status in Ubuntu Translations:
  Fix Committed
Status in gnome-control-center package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu 22.10 ; Gnome 43.0

  Hello,
  There is a translation problem (missing?) in gnome-control-center.
  See image attached.
  Regards,
  Roxfr

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


___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 2002680] Re: "Sharing Options" not translated to local language

[Launchpad Bug Tracker]

This bug was fixed in the package nautilus-share - 0.7.5-0.3

---
nautilus-share (0.7.5-0.3) unstable; urgency=medium

  * Non-maintainer upload
  * Add support for language packs when building for Ubuntu
(LP: #2002680)
  * Update po/POTFILES.in due to new build system
- patch forwarded upstream
  * Bump Standards-Version to 4.6.2

 -- Gunnar Hjalmarsson   Fri, 13 Jan 2023 13:57:38
+0100

** Changed in: nautilus-share (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching subscriptions: Ubuntu Translations bug mail
https://bugs.launchpad.net/bugs/2002680

Title:
  "Sharing Options" not translated to local language

Status in Ubuntu Translations:
  Incomplete
Status in nautilus-share package in Ubuntu:
  Fix Released

Bug description:
  after installing nautilus-share the context entry for sharing is
  inconsistent with system language.

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


___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1966063] [NEW] no Polish name for browse button in file form

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Hi, after update to 98.0.1 (64 bity) canonical 1.0 browse button in file upload 
form is displayed as "Browse" and should be as "Przeglądaj"
I've got Polish language installed and set on top of list, menu bar is in 
Polish.

Description:Ubuntu 18.04.6 LTS
Release:18.04
firefox:
  Zainstalowana: 98.0.1+build2-0ubuntu0.18.04.1
  Kandydująca:   98.0.1+build2-0ubuntu0.18.04.1
  Tabela wersji:
 *** 98.0.1+build2-0ubuntu0.18.04.1 500
500 http://pl.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
100 /var/lib/dpkg/status
 59.0.2+build1-0ubuntu1 500
500 http://pl.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

** Affects: ubuntu-translations
 Importance: Undecided
 Status: New

-- 
no Polish name for browse button in file form
https://bugs.launchpad.net/bugs/1966063
You received this bug notification because you are a member of Ubuntu 
Translations Coordinators, which is subscribed to Ubuntu Translations.

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1989403] Re: g-c-c translation handling broken due to missing dh_translations override

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-control-center -
1:43~rc-1ubuntu2

---
gnome-control-center (1:43~rc-1ubuntu2) kinetic; urgency=medium

  * debian/rules:
- restore the dh_translations override which was forgotten during one
  of the recent merge, it's still needed (lp: #1989403)

 -- Sebastien Bacher   Tue, 13 Sep 2022 12:10:16
+0200

** Changed in: gnome-control-center (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching subscriptions: Ubuntu Translations bug mail
https://bugs.launchpad.net/bugs/1989403

Title:
  g-c-c translation handling broken due to missing dh_translations
  override

Status in Ubuntu Translations:
  New
Status in gnome-control-center package in Ubuntu:
  Fix Released

Bug description:
  From the latest kinetic buildlog:

 dh_translations
  dh_translations: warning: more than one meson translation domain found 
(gnome-control-center-2.0,gnome-control-center-2.0-timezones), don't know which 
one to use

  Previously d/rules included this override:

  override_dh_translations:
dh_translations --domain=gnome-control-center-2.0

  Somehow it seems to have been dropped, though. Maybe, to reduce the
  risk it gets unintentionally dropped again, it should be added to the
  debian/master branch instead of the ubuntu/master ditto?

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


___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1939855] [NEW] [SRU] Ice driver causes the kernel to crash with Ubuntu 20.04.2 with ethtool specific register commands

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

[Impact]

When we run the command, ethtool -d  with Intel cards (ice 
driver), the kernel crashes because of the ice driver.
The same works fine with HWE kernel (5.11). Here, we do not see any crash.

[FIXES]

ice: Fix bad register reads
The "ethtool -d" handler reads registers in the ice_regs_dump_list array
and returns read values back to the userspace.

commitID:  1fba4a8a92706c89716449b1aab1b6879f438d34

https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-
next.git/commit/drivers/net/ethernet/intel/ice?id=1fba4a8a92706c89716449b1aab1b6879f438d34

[TESTING]

Install Focal on a system with an E810 network device.
Ensure the network device has an IP address and has connectivity
Run ethtool -d 
Expected result: Prints a register dump for the specified network device

[REGRESSION RISK]

The regression risk is low

[OTHER INFO]

I have added the fix, built the kernel and tested the fix.

https://code.launchpad.net/~mreed8855/ubuntu/+source/linux/+git/focal/+ref/e810_ethtool_fix_next

** Affects: ubuntu-translations
 Importance: Undecided
 Status: Incomplete

** Affects: linux (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: linux (Ubuntu Focal)
 Importance: High
 Status: Fix Released


** Tags: focal verification-done-focal
-- 
[SRU] Ice driver causes the kernel to crash with Ubuntu 20.04.2 with ethtool 
specific register commands
https://bugs.launchpad.net/bugs/1939855
You received this bug notification because you are a member of Ubuntu 
Translations Coordinators, which is subscribed to Ubuntu Translations.

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1919177] [NEW] Azure: issues with accelerated networking on Hirsute

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

[General]

On Azure, when provisioning a Hirsute VM with Accelerated Networking
enabled, sometimes part of the cloud-init configuration is not applied.

Especially, in those cases, the public SSH key is not setup properly.

[how to reproduce]

Start a VM with AN enabled:

```
az vm create --name "$VM_NAME --resource-group "$GROUP" --location "UK South"  
--image 
'Canonical:0001-com-ubuntu-server-hirsute-daily:21_04-daily-gen2:latest' --size 
Standard_F8s_v2 --admin-username ubuntu --ssh-key-value "$SSH_KEY" 
--accelerated-networking
```

After a moment, try to SSH: if you succeed, delete and recreate a new
VM.

[troubleshooting]

To be able to connect into the VM, run:

az vm run-command invoke -g "$GROUP" -n "$VM_NAME" --command-id RunShellScript 
--scripts "sudo -u ubuntu ssh-import-id $LP_USERNAME"
```

In "/run/cloud-init/instance-data.json", I can see:
```
 "publicKeys": [
  {
   "keyData": "",
   "path": "/home/ubuntu/.ssh/authorized_keys"
  }
 ],
```

as expected.

[workaround]

As mentioned, Azure allows the user to run command into the VM without
SSH connection. To do so, one can use the Azure CLI:

az vm run-command invoke -g "$GROUP" -n "$VM_NAME" --command-id
RunShellScript --scripts "sudo -u ubuntu ssh-import-id $LP_USERNAME"

This example uses "ssh-import-id" but it's also possible to just echo a
given public key into /home/ubuntu/.ssh/authorized_keys

NOTE: this will only solves the SSH issue, I do not know if this bug
affects other things. If so the user would have to apply those things
manually.

** Affects: ubuntu-translations
 Importance: Undecided
 Status: Incomplete

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

** Affects: systemd (Ubuntu Hirsute)
 Importance: Undecided
 Status: New


** Tags: fr-1324
-- 
Azure: issues with accelerated networking on Hirsute
https://bugs.launchpad.net/bugs/1919177
You received this bug notification because you are a member of Ubuntu 
Translations Coordinators, which is subscribed to Ubuntu Translations.

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1240360] [NEW] Rename boot option from "recovery mode" to "safe mode" in GRUB menu

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

SRU justification:

[Impact] Customer request to allow renaming the "recovery mode" boot option.
[Test Case] Set GRUB_RECOVERY_TITLE to something other than "recovery mode" in 
an /etc/default/grub.d/*.cfg file, run update-grub, and make sure that it takes 
effect.
[Regression Potential] Not much; just make sure that the defaults remain the 
same without setting GRUB_RECOVERY_TITLE.

Original report follows:

This is a request from OEM.

OEM request to rename the boot option from "recovery mode" to "safe
mode" in GRUB menu.

It's more sensible for user.

** Affects: ubuntu-translations
 Importance: Undecided
 Status: New

** Affects: oem-priority
 Importance: High
 Assignee: Ara Pulido (ara)
 Status: Fix Released

** Affects: grub2 (Ubuntu)
 Importance: Medium
 Assignee: Colin Watson (cjwatson)
 Status: Fix Released

** Affects: grub2 (Ubuntu Precise)
 Importance: Medium
 Assignee: Colin Watson (cjwatson)
 Status: Fix Released


** Tags: patch verification-done
-- 
Rename boot option from "recovery mode" to "safe mode" in GRUB menu
https://bugs.launchpad.net/bugs/1240360
You received this bug notification because you are a member of Ubuntu 
Translations Coordinators, which is subscribed to Ubuntu Translations.

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1938442] [NEW] Wrong permissions on ~/.hplip/.gnupg

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

[Impact]
* The directory ~/.hplip/.gnupg is readable by non-root users
* This directory contains only public keys, but should still
  have the permissions changed to 700 for privacy reasons

[Test Case]
* Install hplip and run `hp-plugin -i` 
* ls -al ~/.hplip and observe that ~/.hplip/.gnupg has perms drwxr-xr-x
* rm -rf ~/.hplip and install hplip from -proposed
* run `hp-plugin -i` again
* ls -al ~/.hplip and observe that ~/.hplip/.gnupg has perms drwx--

[Regression Potential]
* Because of file permissions becoming more restrictive,
  it is possible that some other hplip binaries would
  fail to read the .gnupg directory
* To ensure this isn't the case, testing should be done
  on different hplip use-cases to ensure they still
  function properly

[Original Description]
Hi,

we have a report in Fedora -
https://bugzilla.redhat.com/show_bug.cgi?id=1985251 - where Sergey found
out that ~/.hplip/.gnupg directory has permissions 755 instead of 700.
Perms 700 prevent accessing the dir by other users, because the dir can
contain private keys.

However, .gnupg dir contains only a public key used in GPG verification
of HP plugin, so the matter isn't that critical, but it is good to have
it fixed.

The patch is attached.

** Affects: ubuntu-translations
 Importance: Undecided
 Status: New

** Affects: hplip (Ubuntu)
 Importance: Undecided
 Assignee: Till Kamppeter (till-kamppeter)
 Status: New

** Affects: hplip (Ubuntu Bionic)
 Importance: Undecided
 Status: New

** Affects: hplip (Ubuntu Focal)
 Importance: Undecided
 Status: New

** Affects: hplip (Ubuntu Hirsute)
 Importance: Undecided
 Status: New

** Affects: hplip (Ubuntu Impish)
 Importance: Undecided
 Status: New

** Affects: hplip (Ubuntu Jammy)
 Importance: Undecided
 Assignee: Till Kamppeter (till-kamppeter)
 Status: New


** Tags: patch
-- 
Wrong permissions on ~/.hplip/.gnupg
https://bugs.launchpad.net/bugs/1938442
You received this bug notification because you are a member of Ubuntu 
Translations Coordinators, which is subscribed to Ubuntu Translations.

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1938442] [NEW] Wrong permissions on ~/.hplip/.gnupg

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

[Impact]
* The directory ~/.hplip/.gnupg is readable by non-root users
* This directory contains only public keys, but should still
  have the permissions changed to 700 for privacy reasons

[Test Case]
* Install hplip and run `hp-plugin -i` 
* ls -al ~/.hplip and observe that ~/.hplip/.gnupg has perms drwxr-xr-x
* rm -rf ~/.hplip and install hplip from -proposed
* run `hp-plugin -i` again
* ls -al ~/.hplip and observe that ~/.hplip/.gnupg has perms drwx--

[Regression Potential]
* Because of file permissions becoming more restrictive,
  it is possible that some other hplip binaries would
  fail to read the .gnupg directory
* To ensure this isn't the case, testing should be done
  on different hplip use-cases to ensure they still
  function properly

[Original Description]
Hi,

we have a report in Fedora -
https://bugzilla.redhat.com/show_bug.cgi?id=1985251 - where Sergey found
out that ~/.hplip/.gnupg directory has permissions 755 instead of 700.
Perms 700 prevent accessing the dir by other users, because the dir can
contain private keys.

However, .gnupg dir contains only a public key used in GPG verification
of HP plugin, so the matter isn't that critical, but it is good to have
it fixed.

The patch is attached.

** Affects: hplip
 Importance: Undecided
 Status: New

** Affects: hplip (Ubuntu)
 Importance: Undecided
 Assignee: Till Kamppeter (till-kamppeter)
 Status: New

** Affects: hplip (Ubuntu Bionic)
 Importance: Undecided
 Status: New

** Affects: hplip (Ubuntu Focal)
 Importance: Undecided
 Status: New

** Affects: hplip (Ubuntu Hirsute)
 Importance: Undecided
 Status: New

** Affects: hplip (Ubuntu Impish)
 Importance: Undecided
 Status: New

** Affects: hplip (Ubuntu Jammy)
 Importance: Undecided
 Assignee: Till Kamppeter (till-kamppeter)
 Status: New

** Affects: ubuntu-translations
 Importance: Undecided
 Status: New


** Tags: patch
-- 
Wrong permissions on ~/.hplip/.gnupg
https://bugs.launchpad.net/bugs/1938442
You received this bug notification because you are a member of Ubuntu 
Translations Coordinators, which is subscribed to Ubuntu Translations.

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1943266] [NEW] Duplicated ARP responses from ovnmetadata namespaces

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

When OpenStack instances are connected to an external network, an 
ovn-etadata-namespace is created in each compute that has VMs attached to that
network. Because the ovn-metadata namespace has interfaces with the same mac 
address in all computers, external switches might ARP query for the IP
 and receive multiple responses in different ports triggering network error 
alerts.

[ubuntu@sombrafam-bastion(kvm):~/internal_git/stsstack-bundles/openstack]$ sudo 
arping -c 1 10.5.150.0
ARPING 10.5.150.0
42 bytes from fa:16:3e:d3:10:01 (10.5.150.0): index=0 time=1.678 msec
42 bytes from fa:16:3e:d3:10:01 (10.5.150.0): index=1 time=2.143 msec

--- 10.5.150.0 statistics ---
1 packets transmitted, 2 packets received,   0% unanswered (1 extra)
rtt min/avg/max/std-dev = 1.678/1.911/2.143/0.232 ms


Reproducer: https://paste.ubuntu.com/p/nbnhvTM9d4/

** Affects: ubuntu-translations
 Importance: Undecided
 Assignee: Erlon R. Cruz (sombrafam)
 Status: Invalid

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

** Affects: ovn (Ubuntu Focal)
 Importance: High
 Status: Fix Committed

** Affects: ovn (Ubuntu Hirsute)
 Importance: High
 Status: Fix Committed

** Affects: ovn (Ubuntu Impish)
 Importance: Undecided
 Status: Fix Released


** Tags: verification-done verification-done-focal verification-done-hirsute
-- 
Duplicated ARP responses from ovnmetadata namespaces
https://bugs.launchpad.net/bugs/1943266
You received this bug notification because you are a member of Ubuntu 
Translations Coordinators, which is subscribed to Ubuntu Translations.

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1914988] [NEW] IGMP Snooping does not work with RBAC enabled ovn-controllers

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

[Impact]
It is currently not possible to use Multicast IGMP snooping with OVN in Ubuntu 
Focal and Hirsute.

[Test Plan]
1. Execute the gate tests for the neutron-api-plugin-ovn charm, which performs 
a full cloud deployment and confirms two instances can spawn, get metadata and 
communicate with each other.

2. Enable IGMP snooping and have instances join a multicast group and
validate that packets forward and check for RBAC errors.

[Regression Potential]
This is a very small patch that adds a static RBAC rule that ovn-northd writes 
into the database.  The patch has already been available in the upstream 
branches since February 2021, we have also landed several similar patches 
upstream which have previously been made available to Focal through point 
release updates.

[Original Bug Description]
Hi,

I've tested this on both 20.03 and 20.06.

Looking into ovn-architecture.xml: 
https://github.com/ovn-org/ovn/blob/master/ovn-architecture.7.xml#L2530
It states that once RBAC is enabled, ovn-controllers will have access to some 
of the tables and that is hardcoded within OVN.

That means once RBAC is enabled, IGMP_Group table is out of reach for
ovn-controllers and will cause the following issue:

2021-02-06T17:17:40.916Z|00028|ovsdb_idl|WARN|transaction error:
{"details":"RBAC rules for client "REDACTED" role "ovn-controller"
prohibit row insertion into table "IGMP_Group".","error":"permission
error"}

Reported on upstream repo: https://github.com/ovn-org/ovn/issues/77

Proposed patch:
https://github.com/phvalguima/ovn/commit/3419d9946c51b413f816ceb82372677e4afdbe9d

** Affects: ubuntu-translations
 Importance: Undecided
 Status: Invalid

** Affects: cloud-archive
 Importance: Undecided
 Status: Fix Released

** Affects: cloud-archive/ussuri
 Importance: Undecided
 Status: Fix Committed

** Affects: cloud-archive/wallaby
 Importance: Undecided
 Status: Fix Committed

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

** Affects: ovn (Ubuntu Focal)
 Importance: Undecided
 Status: Fix Committed

** Affects: ovn (Ubuntu Hirsute)
 Importance: High
 Status: Fix Committed

** Affects: ovn (Ubuntu Impish)
 Importance: Undecided
 Status: Fix Released


** Tags: sts verification-done verification-done-focal 
verification-done-hirsute verification-ussuri-done verification-wallaby-done
-- 
IGMP Snooping does not work with RBAC enabled ovn-controllers
https://bugs.launchpad.net/bugs/1914988
You received this bug notification because you are a member of Ubuntu 
Translations Coordinators, which is subscribed to Ubuntu Translations.

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1946499] [NEW] SRU: GDebi - installation of deb-packages with gdebi-gtk not working at all

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Steps to reproduce:
1. Install Ubuntu MATE 21.10
2. Open Firefox, navigate to discord.com
3. Download deb-file. At time of writing from the 
https://dl.discordapp.net/apps/linux/0.0.16/discord-0.0.16.deb link
4. Open Caja in ~/Downloads folder and use GDebi to install the 
discord-0.0.16.deb file
5. In the GDebi window click Install button

Expected results:
* Gdebi quietly install discord package, there are no error messages in its 
terminal

Actual results:
* Gdebi terminal shows the error in the last line

```
Selecting previously unselected package gconf2-common.
(Reading database ... 457178 files and directories currently installed.)
Preparing to unpack .../0-gconf2-common_3.2.6-7ubuntu2_all.deb ...
Unpacking gconf2-common (3.2.6-7ubuntu2) ...
Selecting previously unselected package libgconf-2-4:amd64.
Preparing to unpack .../1-libgconf-2-4_3.2.6-7ubuntu2_amd64.deb ...
Unpacking libgconf-2-4:amd64 (3.2.6-7ubuntu2) ...
Selecting previously unselected package gconf-service-backend.
Preparing to unpack .../2-gconf-service-backend_3.2.6-7ubuntu2_amd64.deb ...
Unpacking gconf-service-backend (3.2.6-7ubuntu2) ...
Selecting previously unselected package gconf-service.
Preparing to unpack .../3-gconf-service_3.2.6-7ubuntu2_amd64.deb ...
Unpacking gconf-service (3.2.6-7ubuntu2) ...
Selecting previously unselected package libappindicator1.
Preparing to unpack 
.../4-libappindicator1_12.10.1+20.10.20200706.1-0ubuntu1_amd64.deb ...
Unpacking libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ...
Selecting previously unselected package libunwind-13:amd64.
Preparing to unpack .../5-libunwind-13_1%3a13.0.0-2_amd64.deb ...
Unpacking libunwind-13:amd64 (1:13.0.0-2) ...
Selecting previously unselected package libc++abi1-13:amd64.
Preparing to unpack .../6-libc++abi1-13_1%3a13.0.0-2_amd64.deb ...
Unpacking libc++abi1-13:amd64 (1:13.0.0-2) ...
Selecting previously unselected package libc++1-13:amd64.
Preparing to unpack .../7-libc++1-13_1%3a13.0.0-2_amd64.deb ...
Unpacking libc++1-13:amd64 (1:13.0.0-2) ...
Selecting previously unselected package libc++1:amd64.
Preparing to unpack .../8-libc++1_1%3a13.0-53~exp1_amd64.deb ...
Unpacking libc++1:amd64 (1:13.0-53~exp1) ...
Setting up libappindicator1 (12.10.1+20.10.20200706.1-0ubuntu1) ...
Setting up gconf2-common (3.2.6-7ubuntu2) ...

Creating config file /etc/gconf/2/path with new version
Setting up libunwind-13:amd64 (1:13.0.0-2) ...
Setting up libc++abi1-13:amd64 (1:13.0.0-2) ...
Setting up libc++1-13:amd64 (1:13.0.0-2) ...
Setting up libc++1:amd64 (1:13.0-53~exp1) ...
Setting up gconf-service (3.2.6-7ubuntu2) ...
Processing triggers for libc-bin (2.34-0ubuntu2) ...
Processing triggers for sgml-base (1.30) ...
Setting up libgconf-2-4:amd64 (3.2.6-7ubuntu2) ...
Setting up gconf-service-backend (3.2.6-7ubuntu2) ...
Processing triggers for libc-bin (2.34-0ubuntu2) ...
dpkg: error: unable to read filedescriptor flags for : Bad file descriptor
```

and as the result Discord package is not installed .

ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: gdebi 0.9.5.7+nmu5ubuntu1
ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
Uname: Linux 5.13.0-16-generic x86_64
ApportVersion: 2.20.11-0ubuntu70
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: MATE
Date: Fri Oct  8 18:17:36 2021
InstallationDate: Installed on 2021-10-08 (0 days ago)
InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Daily amd64 (20211008)
PackageArchitecture: all
SourcePackage: gdebi
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.default.apport:
 # set this to 0 to disable apport, or to 1 to enable it
 # you can temporarily override this with
 # sudo service apport start force_start=1
 enabled=0
mtime.conffile..etc.default.apport: 2021-10-08T15:41:41.001986

** Affects: ubuntu-translations
 Importance: Undecided
 Status: Invalid

** Affects: gdebi (Ubuntu)
 Importance: High
 Status: Fix Released

** Affects: vte2.91 (Ubuntu)
 Importance: Undecided
 Status: Confirmed

** Affects: gdebi (Ubuntu Impish)
 Importance: High
 Status: Fix Committed


** Tags: amd64 apport-bug impish patch verification-done-impish 
verification-needed
-- 
SRU: GDebi - installation of deb-packages with gdebi-gtk not working at all
https://bugs.launchpad.net/bugs/1946499
You received this bug notification because you are a member of Ubuntu 
Translations Coordinators, which is subscribed to Ubuntu Translations.

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1945894] [NEW] Translated strings not imported from damned lies

[Launchpad Bug Tracker]

You have been subscribed to a public bug by Akbarkhon Variskhanov (kbar):

The newly translated strings in GTK does not seem to be imported from
Damned Lies. GTK in Ubuntu has 50 untranslated strings in Danish but is
fully translated in Damned Lies.

** Affects: gtk+3.0 (Ubuntu)
 Importance: Undecided
 Status: New

-- 
Translated strings not imported from damned lies
https://bugs.launchpad.net/bugs/1945894
You received this bug notification because you are a member of Ubuntu 
Translations Coordinators, which is subscribed to the bug report.

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1916485] [NEW] test -x fails inside shell scripts in containers

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

(SRU template for systemd)

[impact]

bash (and some other shells) builtin test command -x operation fails

[test case]

on any affected host system, start nspawn container, e.g.:

$ sudo apt install systemd-container
$ wget 
https://cloud-images.ubuntu.com/hirsute/current/hirsute-server-cloudimg-amd64-root.tar.xz
$ mkdir h
$ cd h
$ sudo tar xvf ../hirsute-server-cloudimg-amd64-root.tar.xz
$ sudo systemd-nspawn

Then from a bash shell, verify if test -x works:

root@h:~# ls -l /usr/bin/gpg
-rwxr-xr-x 1 1000 1000 1083472 Jan 16 09:53 /usr/bin/gpg
root@h:~# test -x /usr/bin/gpg || echo "fail"
fail

[regression potential]

any regression would likely occur during a syscall, most likely
faccessat2(), or during other syscalls.

[scope]

this is needed for b/f

this is fixed upstream by commit
bcf08acbffdee0d6360d3c31d268e73d0623e5dc which is in 247 and later, so
this is fixed in h

this was pulled into Debian at version 246.2 in commit
e80c5e5371ab77792bae94e0f8c5e85a4237e6eb, so this is fixed in g

in x, the entire systemd seccomp code is completely different and the
patch doesn't apply, nor does it appear to be needed, as the problem
doesn't reproduce in a h container under x.

[other info]

this needs fixing in libseccomp as well

[original description]

glibc regression causes test -x to fail inside scripts inside
docker/podman, dash and bash are broken, mksh and zsh are fine:

root@0df2ce5d7a46:/# test -x /usr/bin/gpg || echo Fail
root@0df2ce5d7a46:/# dash -c "test -x /usr/bin/gpg || echo Fail"
Fail
root@0df2ce5d7a46:/# bash -c "test -x /usr/bin/gpg || echo Fail"
Fail
root@0df2ce5d7a46:/# mksh -c "test -x /usr/bin/gpg || echo Fail"
root@0df2ce5d7a46:/# zsh -c "test -x /usr/bin/gpg || echo Fail"
root@0df2ce5d7a46:/#

root@0df2ce5d7a46:/# zsh -c "[ -x /usr/bin/gpg ] || echo Fail"
root@0df2ce5d7a46:/# mksh -c "[ -x /usr/bin/gpg ] || echo Fail"
root@0df2ce5d7a46:/# dash -c "[ -x /usr/bin/gpg ] || echo Fail"
Fail
root@0df2ce5d7a46:/# bash -c "[ -x /usr/bin/gpg ] || echo Fail"
Fail

The -f flag works, as does /usr/bin/test:
# bash -c "test -f /usr/bin/gpg  || echo Fail"
# bash -c "/usr/bin/test -x /usr/bin/gpg  || echo Fail"
#

[Original bug report]
root@84b750e443f8:/# lsb_release -rd
Description:Ubuntu Hirsute Hippo (development branch)
Release:21.04
root@84b750e443f8:/# dpkg -l gnupg apt
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name   Version Architecture Description
+++-==-===--==
ii  apt2.1.20  amd64commandline package manager
ii  gnupg  2.2.20-1ubuntu2 all  GNU privacy guard - a free PGP 
replacement

Hi,
for 3 days our CI pipelines to recreate Docker images fails for the Hirsute 
images. From comparison this seems to be caused by apt 2.1.20.

The build fails with:

0E: gnupg, gnupg2 and unupg1 do not seem to be installed, but one of
them is required for this operation

The simple Dockerfile to reproduce the error - "docker build -t foo ."

FROM amd64/ubuntu:hirsute
MAINTAINER Florian Lohoff 

USER root

RUN apt-get update \
 && DEBIAN_FRONTEND=noninteractive apt-get -y install curl gnupg apt \
  && curl https://syncthing.net/release-key.txt | apt-key add -

Breaking it down it this seems to be an issue that there is new
functionality in apt/apt-key e.g. security hardening that docker
prohibits in its containers. Running this manually works only in an
--privileged container.

So adding keys in unpriviledged container or possibly kubernetes will
not work anymore.

Flo

** Affects: ubuntu-translations
 Importance: Undecided
 Status: Invalid

** Affects: glibc (Ubuntu)
 Importance: Undecided
 Status: Opinion

** Affects: libseccomp (Ubuntu)
 Importance: Critical
 Status: Fix Released

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

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

** Affects: libseccomp (Ubuntu Xenial)
 Importance: Undecided
 Status: Fix Released

** Affects: runc (Ubuntu Xenial)
 Importance: Undecided
 Status: Invalid

** Affects: systemd (Ubuntu Xenial)
 Importance: Undecided
 Status: Invalid

** Affects: libseccomp (Ubuntu Bionic)
 Importance: Undecided
 Status: Fix Released

** Affects: runc (Ubuntu Bionic)
 Importance: Undecided
 Status: Fix Released

** Affects: systemd (Ubuntu Bionic)
 Importance: Undecided
 Status: Fix Released

** Affects: libseccomp (Ubuntu Focal)
 Importance: Undecided
 Status: Fix Released

** Affects: runc (Ubuntu Focal)
 Importance: Undecided
 Status: Fix Released

** Affects: systemd (Ubuntu Focal)
 Importance: Undecided
   

[Ubuntu-translations-coordinators] [Bug 1756547] Re: LP refuses to import plural strings where e.g. msgstr[0] entries in PO file miss %d

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-shell - 40.2-1ubuntu6

---
gnome-shell (40.2-1ubuntu6) impish; urgency=medium

  * d/rules:
- Drop dh_translations workaround. gettext used by LP has been
  updated (LP: #1756547).
- Fix Lintian warning about DEB_HOST_ARCH assignment

gnome-shell (40.2-1ubuntu5) impish; urgency=medium

  * Fix translation issues (LP: #1941954):
- Really fix translation import problem as reported in LP: #1756547
- Add libgtk-3-bin to Build-Depends for dh_translations

gnome-shell (40.2-1ubuntu4) impish; urgency=medium

  * debian/rules:
- Skip tests when building for ppc64el to fix FTBFS (LP: #1941792)

gnome-shell (40.2-1ubuntu3) impish; urgency=medium

  [ Daniel van Vugt ]
  * Add layout-Make-starting-in-the-overview-optional.patch:
- So that extensions like Ubuntu Dock have the option of preventing
  the shell starting in the overview. (LP: #1940925)

gnome-shell (40.2-1ubuntu2) impish; urgency=medium

  [ Daniel van Vugt ]
  * Add workspace-Remove-skip-taskbar-windows-while-the-over.patch to stop the
desktop icons window appearing like an app window in the overview on
startup (LP: #1936643)

 -- Gunnar Hjalmarsson   Wed, 01 Sep 2021 15:44:38
+0200

** Changed in: gnome-shell (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching subscriptions: Ubuntu Translations bug mail
https://bugs.launchpad.net/bugs/1756547

Title:
  LP refuses to import plural strings where e.g. msgstr[0] entries in PO
  file miss %d

Status in Launchpad itself:
  Fix Released
Status in Ubuntu Translations:
  Fix Released
Status in gettext package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released

Bug description:
  Some strings of GNOME Shell are untranslated in the Czech translation
  on Ubuntu 18.04 although they are translated upstream and when I try
  to manually translate them on launchpad, I get this error: "number of
  format specifications in 'msgid_plural' and 'msgstr[0]' does not
  match".

  The bad strings are:
  %d minute ago
  %d minutes ago

  %d hour ago
  %d hours ago

  %d week ago
  %d weeks ago

  %d month ago
  %d months ago

  %d year ago
  %d years ago

  They seem to be correct, but they are not accepted for some reason.

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


___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1879798] [NEW] designate-manage pool update doesn't reflects targets master dns servers into zones.

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

[Environment]

Ubuntu + Ussuri

[Description]

If running designate-manage pool update with new targets, those targets
gets properly updated in the pool target masters list, but those aren't
reflected into the zones that belongs to this pool, therefore, the masters
associated to that zones aren't updated causing failures as the expressed
in the Further Information section.

designate-manager pool update should offer an option to update the zones
associated to the pools with the new target masters and be able to apply
these changes into existing zones.

For the case of the bind9 backend the current workaround is to manually
run the rndc modzone command with the new masters, but that's not suitable
for large installations with multiple zones and pools.


[Further information]

We have a designate/designate-bind setup. We migrated designate units to
different machines, replacing 3 designate units with 3 new units.
However, this caused issues with existing zones, including creating new
recordsets for these zones. The zone would result in having an ERROR
status and a CREATE action.

Looking at the designate bind units, we see that designate is attempting
to run:

'addzone $zone { type slave; masters {$new_designate_ips port 5354;};
file "slave.$zone.$hash"; };'

This addzone fails due to the zone already existing. However, we found
that the zone configuration (using 'rndc showzone $zone' from designate-
bind unit) still had the old designate ips for its masters. There are
also logs in /var/log/syslog like the following:

May 20 06:27:10 juju-c27f05-15-lxd-1 named[72648]: transfer of '$zone'
from $old_designate_ip#5354: failed to connect: host unreachable

We were able to resolve this issue by modifying the zone config on all
designate-bind units:

juju run -a designate-bind -- rndc modzone $zone '{ type slave; file
"slave.$zone.$hash"; masters { $new_designate_ip_1 port 5354;
$new_designate_ip_2 port 5354; $new_designate_ip_3 port 5354; }; };'

After modifying the zone, the recordset creations completed and resolved
almost immediately.

Would this be something the charm could do in an automated way when
masters are removed/replaced, or is there a better way of fixing the
zone configurations? For these designate migrations, we will have to
enumerate over every zone to fix their configurations.

** Affects: ubuntu-translations
 Importance: Undecided
 Assignee: Jorge Niedbalski (niedbalski)
 Status: Invalid

** Affects: cloud-archive
 Importance: Undecided
 Status: Fix Released

** Affects: cloud-archive/stein
 Importance: Undecided
 Status: New

** Affects: cloud-archive/train
 Importance: Undecided
 Status: New

** Affects: cloud-archive/ussuri
 Importance: Undecided
 Status: New

** Affects: cloud-archive/victoria
 Importance: Undecided
 Status: New

** Affects: cloud-archive/wallaby
 Importance: Undecided
 Status: Fix Released

** Affects: cloud-archive/xena
 Importance: Undecided
 Status: Fix Released

** Affects: designate
 Importance: Undecided
 Assignee: Jorge Niedbalski (niedbalski)
 Status: Fix Released

** Affects: designate (Ubuntu)
 Importance: Medium
 Assignee: Jorge Niedbalski (niedbalski)
 Status: Fix Committed

** Affects: designate (Ubuntu Focal)
 Importance: Medium
 Status: New


** Tags: patch scaleback
-- 
designate-manage pool update doesn't reflects targets master dns servers into 
zones.
https://bugs.launchpad.net/bugs/1879798
You received this bug notification because you are a member of Ubuntu 
Translations Coordinators, which is subscribed to Ubuntu Translations.

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1939224] Re: Remove the Edubuntu POT template

[Launchpad Bug Tracker]

This bug was fixed in the package ubiquity-slideshow-ubuntu - 169

---
ubiquity-slideshow-ubuntu (169) impish; urgency=medium

  [ Gunnar Hjalmarsson ]
  * Drop the Edubuntu slideshow (LP: #1939224)

 -- Gunnar Hjalmarsson   Tue, 10 Aug 2021 17:29:16
+0200

** Changed in: ubiquity-slideshow-ubuntu (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching subscriptions: Ubuntu Translations bug mail
https://bugs.launchpad.net/bugs/1939224

Title:
  Remove the Edubuntu POT template

Status in Ubuntu Translations:
  Fix Released
Status in ubiquity-slideshow-ubuntu package in Ubuntu:
  Fix Released

Bug description:
  It’s no longer relevant, and we shouldn’t be making translators waste
  time on strings that are never going to be used.

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


___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1939224] Re: Remove the Edubuntu POT template

[Launchpad Bug Tracker]

** Branch linked: lp:ubiquity-slideshow-ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching subscriptions: Ubuntu Translations bug mail
https://bugs.launchpad.net/bugs/1939224

Title:
  Remove the Edubuntu POT template

Status in Ubuntu Translations:
  Fix Released
Status in ubiquity-slideshow-ubuntu package in Ubuntu:
  In Progress

Bug description:
  It’s no longer relevant, and we shouldn’t be making translators waste
  time on strings that are never going to be used.

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


___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1922447] [NEW] Wellcome to Ubuntu Mate slideshow is not entirely in Spanish

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

There are 4-5 slides written in English despite the selected language
for instalation is Spanish

** Affects: ubuntu-translations
 Importance: Undecided
 Status: Confirmed

** Affects: ubiquity-slideshow-ubuntu (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: hirsute iso-testing ubuntu-mate
-- 
Wellcome to Ubuntu Mate slideshow is not entirely in Spanish
https://bugs.launchpad.net/bugs/1922447
You received this bug notification because you are a member of Ubuntu 
Translations Coordinators, which is subscribed to Ubuntu Translations.

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1879494] [NEW] RM ancient obsolete version of mongodb

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

RM ancient obsolete version of mongodb

$ reverse-depends src:mongodb
Reverse-Recommends
* nextepc   (for mongodb)
* nextepc-hss [amd64 arm64 ppc64el s390x]
* nextepc-pcrf [amd64 arm64 ppc64el s390x]
* rsyslog-mongodb [amd64 arm64 armhf ppc64el s390x]
* uwsgi-plugin-mongo [amd64 arm64 armhf ppc64el s390x]

Packages without architectures listed are reverse-dependencies in:
amd64, arm64, armhf, i386, ppc64el, s390x

$ reverse-depends -b src:mongodb
Reverse-Testsuite-Triggers
* python-motor  (for mongodb-server)
* ruby-mongo(for mongodb-server)

Reverse-Build-Depends-Indep
* aodh  (for mongodb)
* zaqar (for mongodb)

And juju

== Analysis for removal ==

Reverse recommends do not matter.

Testsuite-triggers => cannot really test anything without mongodb server
running, mark as regressed.

Build-Depends-Indep => must be fixed

juju => 2.8+ has switched to use juju-db snap (a variant of mongodb
tailored for juju)

** Affects: ubuntu-translations
 Importance: Undecided
 Status: New

** Affects: aodh (Ubuntu)
 Importance: High
 Status: Fix Released

** Affects: mongodb (Ubuntu)
 Importance: High
 Status: Fix Released

** Affects: zaqar (Ubuntu)
 Importance: High
 Status: Fix Released


** Tags: patch rls-gg-incoming
-- 
RM ancient obsolete version of mongodb
https://bugs.launchpad.net/bugs/1879494
You received this bug notification because you are a member of Ubuntu 
Translations Coordinators, which is subscribed to Ubuntu Translations.

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1918855] [NEW] Xorg xserver got signal 6 to abort

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

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

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

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

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


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

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

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

** Affects: oem-priority
 Importance: Critical
 Assignee: jeremyszu (os369510)
 Status: In Progress

** Affects: ubuntu-translations
 Importance: Undecided
 Status: New

** Affects: mesa (Ubuntu)
 Importance: Medium
 Assignee: Timo Aaltonen (tjaalton)
 Status: Fix Released

** Affects: mesa (Ubuntu Focal)
 Importance: Medium
 Assignee: Timo Aaltonen (tjaalton)
 Status: New

** Affects: mesa (Ubuntu Hirsute)
 Importance: Medium
 Assignee: Timo Aaltonen (tjaalton)
 Status: New


** Tags: oem-priority originate-from-1917692 originate-from-1929152 
originate-from-1932285 patch somerville stella
-- 
Xorg xserver got signal 6 to abort
https://bugs.launchpad.net/bugs/1918855
You received this bug notification because you are a member of Ubuntu 
Translations Coordinators, which is subscribed to Ubuntu Translations.

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1922929] Re: Remove/Merge filipino (fil) translation as its a duplicate of tagalog (tl)

[Launchpad Bug Tracker]

[Expired for Ubuntu Translations because there has been no activity for
60 days.]

** Changed in: ubuntu-translations
   Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching subscriptions: Ubuntu Translations bug mail
https://bugs.launchpad.net/bugs/1922929

Title:
  Remove/Merge filipino (fil) translation as its a duplicate of tagalog
  (tl)

Status in Ubuntu Translations:
  Expired

Bug description:
  Filipino (fil) is listed as one of the languages to translate the
  ubuntu installer, but you can't select it in the installer, while the
  Tagalog (tl) language is listed and unfortunately more people have
  added translations to Filipino rather than Tagalog. To eliminate this
  duplication, the work done in Filipino should be copied into Tagalog
  and Filipino should be removed.

  https://translations.launchpad.net/ubuntu/hirsute/+source/ubiquity/+pots
  /ubiquity-debconf/fil/+translate

  https://translations.launchpad.net/ubuntu/hirsute/+source/ubiquity/+pots
  /ubiquity-debconf/tl/+translate

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

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1905613] [NEW] Please backport v4l2loopback 0.12.5-1 (universe) from hirsute

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

[SRU Justification]

[Impact]

On a MIPI camera through Intel IPU6 platform that its raw V4L2 loopback
interface is preserved for Intel Camera HAL libraries, a relay daemon +
v4l2loopback is used to allow the usage of legacy V4L2 based apps.

By design, the relayd will open v4l2sink to v4l2loopback OUTPUT deivce,
and it will only open libcamhal based GStreamer source element, and
therefore underlying camera hardware, until received new client
notifications via V4L2 Event API that is introduced in this SRU.

Besides, frame sizes/intervals enumeration is also fixed to meet better
compliance with user apps.

[Test Plan]

v4l2loopback doesn't support V4L2 Event API until recently, so requests
for the usage will always fail:

  struct v4l2_event_subscription sub;
  int fd;

  memset (&sub, 0, sizeof (sub));
  sub.type = ...;
  if (ioctl (fd, VIDIOC_SUBSCRIBE_EVENT, &sub) == 0) // fail

With this fix, it shall support Event API operations, e.g.
VIDIOC_SUBSCRIBE_EVENT, VIDIOC_UNSUBSCRIBE_EVENT, VIDIOC_DQEVENT.

[Where problems could occur]

While a custom type of V4L2 event is now registered for OEM projects,
software expected same ID (numerically equivalent to
V4L2_EVENT_PRIVATE_START) may get confused. While this falls in the
private usage section, it's not supposed to be used in general, and when
it does, it should be under some presumptions, e.g. selected hardware,
so it's unlikely to happen on OEM projects.

For generic Ubuntu, programs may begin to take advantage of this new
capability to update its UI, or to take other actions after receiving
desired events. There might be behavior changes, but should be under the
original design if was done carefully.

[Other Info]

For Focal backports, 0.12.5-1 is equivalent to 0.12.3-1ubuntu0.3 plus
micro version updates, so there should be little risk backport a new
release, and we can drop additional patches carried. This implies bug
1905613.

= original bug report ==

Please backport v4l2loopback 0.12.5-1 (universe) from hirsute to focal,
groovy.

Reason for the backport:

Makes dkms module compatible with 5.8 kernels eg linux-generic-hwe-20.04-edge

Testing:

Mark off items in the checklist [X] as you test them, but please leave the 
checklist so that backporters can quickly evaluate the state of testing.

You can test-build the backport in your PPA with backportpackage:
$ backportpackage -u ppa:/ -s hirsute -d focal 
v4l2loopback
$ backportpackage -u ppa:/ -s hirsute -d groovy 
v4l2loopback

* focal:
[x] Package builds without modification
[x] v4l2loopback-source installs cleanly and runs
[x] v4l2loopback-dkms installs cleanly and runs
[x] v4l2loopback-utils installs cleanly and runs
* groovy:
[x] Package builds without modification
[x] v4l2loopback-source installs cleanly and runs
[x] v4l2loopback-dkms installs cleanly and runs
[x] v4l2loopback-utils installs cleanly and runs

Reverse dependencies:
=
The following reverse-dependencies need to be tested against the new version of 
v4l2loopback. For reverse-build-dependencies (-Indep), please test that the 
package still builds against the new v4l2loopback. For reverse-dependencies, 
please test that the version of the package currently in the release still 
works with the new v4l2loopback installed. Reverse- Recommends, Suggests, and 
Enhances don't need to be tested, and are listed for completeness-sake.

v4l2loopback-source
---

v4l2loopback-dkms
-
* gem-plugin-v4l2
  [ ] focal (Reverse-Suggests)
  [ ] groovy (Reverse-Suggests)
* xpra
  [ ] focal (Reverse-Suggests)
  [ ] groovy (Reverse-Suggests)

v4l2loopback-utils
--

** Affects: ubuntu-translations
 Importance: Undecided
 Status: New

** Affects: hwe-next
 Importance: High
 Status: New

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

** Affects: v4l2loopback (Ubuntu Focal)
 Importance: High
 Assignee: You-Sheng Yang (vicamo)
 Status: In Progress

** Affects: v4l2loopback (Ubuntu Groovy)
 Importance: Undecided
 Status: Won't Fix

-- 
Please backport v4l2loopback 0.12.5-1 (universe) from hirsute
https://bugs.launchpad.net/bugs/1905613
You received this bug notification because you are a member of Ubuntu 
Translations Coordinators, which is subscribed to Ubuntu Translations.

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1905613] [NEW] Please backport v4l2loopback 0.12.5-1 (universe) from hirsute

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

[SRU Justification]

[Impact]

On a MIPI camera through Intel IPU6 platform that its raw V4L2 loopback
interface is preserved for Intel Camera HAL libraries, a relay daemon +
v4l2loopback is used to allow the usage of legacy V4L2 based apps.

By design, the relayd will open v4l2sink to v4l2loopback OUTPUT deivce,
and it will only open libcamhal based GStreamer source element, and
therefore underlying camera hardware, until received new client
notifications via V4L2 Event API that is introduced in this SRU.

Besides, frame sizes/intervals enumeration is also fixed to meet better
compliance with user apps.

[Test Plan]

v4l2loopback doesn't support V4L2 Event API until recently, so requests
for the usage will always fail:

  struct v4l2_event_subscription sub;
  int fd;

  memset (&sub, 0, sizeof (sub));
  sub.type = ...;
  if (ioctl (fd, VIDIOC_SUBSCRIBE_EVENT, &sub) == 0) // fail

With this fix, it shall support Event API operations, e.g.
VIDIOC_SUBSCRIBE_EVENT, VIDIOC_UNSUBSCRIBE_EVENT, VIDIOC_DQEVENT.

[Where problems could occur]

While a custom type of V4L2 event is now registered for OEM projects,
software expected same ID (numerically equivalent to
V4L2_EVENT_PRIVATE_START) may get confused. While this falls in the
private usage section, it's not supposed to be used in general, and when
it does, it should be under some presumptions, e.g. selected hardware,
so it's unlikely to happen on OEM projects.

For generic Ubuntu, programs may begin to take advantage of this new
capability to update its UI, or to take other actions after receiving
desired events. There might be behavior changes, but should be under the
original design if was done carefully.

[Other Info]

For Focal backports, 0.12.5-1 is equivalent to 0.12.3-1ubuntu0.3 plus
micro version updates, so there should be little risk backport a new
release, and we can drop additional patches carried. This implies bug
1905613.

= original bug report ==

Please backport v4l2loopback 0.12.5-1 (universe) from hirsute to focal,
groovy.

Reason for the backport:

Makes dkms module compatible with 5.8 kernels eg linux-generic-hwe-20.04-edge

Testing:

Mark off items in the checklist [X] as you test them, but please leave the 
checklist so that backporters can quickly evaluate the state of testing.

You can test-build the backport in your PPA with backportpackage:
$ backportpackage -u ppa:/ -s hirsute -d focal 
v4l2loopback
$ backportpackage -u ppa:/ -s hirsute -d groovy 
v4l2loopback

* focal:
[x] Package builds without modification
[x] v4l2loopback-source installs cleanly and runs
[x] v4l2loopback-dkms installs cleanly and runs
[x] v4l2loopback-utils installs cleanly and runs
* groovy:
[x] Package builds without modification
[x] v4l2loopback-source installs cleanly and runs
[x] v4l2loopback-dkms installs cleanly and runs
[x] v4l2loopback-utils installs cleanly and runs

Reverse dependencies:
=
The following reverse-dependencies need to be tested against the new version of 
v4l2loopback. For reverse-build-dependencies (-Indep), please test that the 
package still builds against the new v4l2loopback. For reverse-dependencies, 
please test that the version of the package currently in the release still 
works with the new v4l2loopback installed. Reverse- Recommends, Suggests, and 
Enhances don't need to be tested, and are listed for completeness-sake.

v4l2loopback-source
---

v4l2loopback-dkms
-
* gem-plugin-v4l2
  [ ] focal (Reverse-Suggests)
  [ ] groovy (Reverse-Suggests)
* xpra
  [ ] focal (Reverse-Suggests)
  [ ] groovy (Reverse-Suggests)

v4l2loopback-utils
--

** Affects: focal-backports
 Importance: Undecided
 Status: New

** Affects: ubuntu-translations
 Importance: Undecided
 Status: New

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

** Affects: v4l2loopback (Ubuntu Focal)
 Importance: High
 Assignee: You-Sheng Yang (vicamo)
 Status: In Progress

** Affects: v4l2loopback (Ubuntu Groovy)
 Importance: Undecided
 Status: Won't Fix

-- 
Please backport v4l2loopback 0.12.5-1 (universe) from hirsute
https://bugs.launchpad.net/bugs/1905613
You received this bug notification because you are a member of Ubuntu 
Translations Coordinators, which is subscribed to Ubuntu Translations.

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1930857] [NEW] pages "Guide du bureau Ubuntu" only partially translated in french

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Not every page of the manual seems to be translated in French, or only 
partially. 
For example, the main page states :
"Premiers pas avec GNOME
Visual overwiew of GNOME
Déconnexion, extinction, ou changement d'utilisateur"

Both the "Visual overview" page and the "Déconnexion, extinction, ..."
page show some paragraphs in French and some in English, and so does
fast every page of the manual wich can be accessed directly from the
main page.

Ubuntu release : 20.04.2 LTS
Version of the package : 20.04.3

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubuntu-docs 20.04.3
ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106
Uname: Linux 5.4.0-73-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Jun  4 10:45:52 2021
InstallationDate: Installed on 2020-02-16 (473 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
PackageArchitecture: all
SourcePackage: ubuntu-docs
UpgradeStatus: Upgraded to focal on 2020-12-01 (184 days ago)

** Affects: ubuntu-translations
 Importance: Medium
 Assignee: Ubuntu French Translators (ubuntu-l10n-fr)
 Status: New


** Tags: amd64 apport-bug focal
-- 
pages "Guide du bureau Ubuntu"  only partially translated in french
https://bugs.launchpad.net/bugs/1930857
You received this bug notification because you are a member of Ubuntu 
Translations Coordinators, which is subscribed to Ubuntu Translations.

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1925131] [NEW] Nové návrhy na překlad v balíku gnome-shell-extension-desktop-icons-ng package

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Dobrý den,
doplnil jsem návrhy ke všem chybějícím překladům v daném balíku a žádám o 
kontrolu a potvrzení překladu.
https://translations.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons-ng

Hezký den.

** Affects: ubuntu-translations
 Importance: Undecided
 Status: New

-- 
Nové návrhy na překlad v balíku gnome-shell-extension-desktop-icons-ng package
https://bugs.launchpad.net/bugs/1925131
You received this bug notification because you are a member of Ubuntu 
Translations Coordinators, which is subscribed to Ubuntu Translations.

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 885086] Re: XDG "Desktop" item not translated on Live CD

[Launchpad Bug Tracker]

** Merge proposal linked:
   https://code.launchpad.net/~gunnarhj/casper/+git/casper/+merge/400294

-- 
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching subscriptions: Ubuntu Translations bug mail
https://bugs.launchpad.net/bugs/885086

Title:
  XDG "Desktop" item not translated on Live CD

Status in Ubuntu Translations:
  Triaged
Status in casper package in Ubuntu:
  In Progress
Status in xdg-user-dirs package in Ubuntu:
  Opinion

Bug description:
  When I switch the language on my Oneiric Live CD, other XDG
  directories are translated except the "Desktop" item. When I have a
  look inside ~/.config/user-dirs.dirs, the string is untranslated
  (other strings in the file are translated all right). If I run xdg-
  user-dirs-update, ~/.config/user-dirs.dirs is updated to the correct
  translation. So I suppose that the default Live CD user is created by
  some not-localized hackish solution.

  If this seems not so important, since installed systems have the
  "Desktop" directory translated all right (at least I hope so, because
  my system has), it certainly affects all Ubuntu localized Live-CDs and
  makes them fail the basic "translated or not surface check".

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

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1892367] [NEW] [UBUNTU 20.04] udev rule change did not get applied

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

SRU:


[Impact]

 * In case a ccw (special s390x hardware) device is configured
   in a special (non-default) way using chzdev
   (like for example increasing the qeth buffer_count to 128),
   the modifications are not persistent by default, since the
   generated udev rules are not automatically incuded/added to the initramfs.

 * One needs to either manually re-create the initramfs,
   e.g. with 'sudo update-initramfs -k all -u' (maybe triggered by zipl)

 * or pass the arguments '-p -r zdev:early' to chzdev.

 * This is not really intuitive and what people expect
   and partly leads to confusion.

 * The solution is to compile with the ZDEV_ALWAYS_UPDATE_INITRD=1 option set.
   This makes sure that executions of chzdev always trigger 'update-initramfs 
-u'.

[Test Plan]

 * Prepare an Ubuntu Server 20.04 or 20.04 on IBM Z with at least
   one ccw device, for example a qeth network device, here '0.0.1234'.
   (better to do that with a second spare qeth device,
other than the one that is in use by your remote connection).

 * Configure the device using:
   sudo chzdev qeth -e 1234

 * Check the (default) value of a certain attribute, like qeth buffer_count:
   cat /sys/devices/qeth/0.0.1234/buffer_count
   64

 * Disable the ccw device again:
   sudo chzdev qeth -d 1234
   
 * And enable (re-)enable it with an increased buffer_count:
   sudo chzdev -e 1234 buffer_count=128

 * Check the (increased) value of the qeth buffer_count:
   cat /sys/devices/qeth/0.0.1234/buffer_count
   128

 * Restart the system (without manually running update-initramfs or zipl):
   sudo shutdown -r now

 * Once the system is up again, re-check if the ccw device was enabled again
   and if it still has the increased buffer_count value:
   lszdev qeth 1234
   TYPE  ID  ON   PERS  NAMES
   qeth  0.0.1234:0.0.1235:0.0.1236  yes  yes   enc1234
   cat /sys/devices/qeth/0.0.1234/buffer_count
   128
   (alternatively check with: lsqeth enc1234 | grep buffer_count)

[Where problems could occur]

 * The logic of handling DZDEV_ALWAYS_UPDATE_INITRD could be wrong, e.g. 
inversed.
   Then the initramfs is re-build even if not desired
   and in case needed not done, hence similar result than before.

 * The setting of 'ZDEV_ALWAYS_UPDATE_INITRD=1' could have been missed,
   which would lead to the similar behaviour than w/o the patch.

 * 'add_pers_removed' could handle wrong device types or not all devices,
   in case of potential array index errors.

 * 'is_zdev_early_0' could identify wrong persistent devices as some to be
   included early in the boot process (means added to the initramfs).

 * Problems in 'if (all_pers)' could lead to a wrong set of persistent devices
   that are considered (or not all),
   which could lead to unexpected (de-)configurations.

 * Finally the handling of the confirmation
   or the 'build of the command line' could be errornous,
   since the encapsulated if condition(s) changed (sightly).

[Other Info]

 * This patch became upstream accepted with s390-tools 2.16.0 and is
   with that already included in hirsute, based on LP:1914574.

__

During the ubuntu installation in tessia, we do chzdev for both dasd and
qeth devices, as below.

2020-08-20 09:54:45 | INFO | START subiquity/Early/run/command_1 : chzdev -e 
dasd 385c
2020-08-20 09:54:45 | INFO | SUCCESS subiquity/Early/run/command_1 : chzdev -e 
dasd 385c
2020-08-20 09:54:45 | INFO | START subiquity/Early/run/command_2 : chzdev -e 
qeth 0.0.bdf0
2020-08-20 09:54:47 | INFO | SUCCESS subiquity/Early/run/command_2 : chzdev -e 
qeth 0.0.bdf0

and we can see the below files in the /etc/udev/rules.d/
oot@m8360024:~# ls -l /etc/udev/rules.d/
total 76
-rw-r--r-- 1 root root   154 Aug 20 09:08 41-cio-ignore.rules
-rw-r--r-- 1 root root   430 Aug 20 09:08 41-dasd-eckd-0.0.385c.rules
-rw-r--r-- 1 root root   357 Aug 20 09:08 41-generic-ccw-0.0.0009.rules
-rw-r--r-- 1 root root  1049 Aug 20 09:08 41-qeth-0.0.bdf0.rules
-rw-r--r-- 1 root root 58549 Aug 20 09:10 70-snap.snapd.rules

Now, lsinitramfs shows files as below,

root@m8360024:~# lsinitramfs /boot/initrd.img-5.4.0-42-generic | grep 41
etc/udev/rules.d/41-cio-ignore-root.rules
etc/udev/rules.d/41-dasd-eckd-0.0.385c.rules
usr/lib/udev/rules.d/41-cio-ignore.rules
usr/lib/udev/rules.d/41-dasd-eckd-0.0.385c.rules
usr/lib/udev/rules.d/41-generic-ccw-0.0.0009.rules
usr/lib/udev/rules.d/41-qeth-0.0.bdf0.rules

Even though lsinitramfs shows the below files, they are overruled by the
filesystem files.

Next thing we did was to modify the 41-qeth-0.0.bdf0.rules and modified
the buffer_count to 128 (As in the attached file). In ideal scenario,
the value should we modified as mentioned in the bug. But, in our case,
if we are not doing a zipl or update-initramfs -u, the value is not
getting modified.

** Affects: ubuntu-translations
 Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
 Status: Inva

[Ubuntu-translations-coordinators] [Bug 1685754] [NEW] 'systemd --user' unduly forces umask=0022

[Launchpad Bug Tracker]

*** This bug is a security vulnerability ***

You have been subscribed to a public security bug:

[impact]

pam_umask, from /etc/passwd, is not honored in systemd --user instances

[test case]

on a desktop system, edit /etc/passwd to change the test user entry
(e.g. the 'ubuntu' user) to include 'umask=007' in the GECOS field (5th
field). For example change:

ubuntu:x:1000:1000:Ubuntu:/home/ubuntu:/bin/bash

to:

ubuntu:x:1000:1000:Ubuntu,umask=007:/home/ubuntu:/bin/bash

You may need to reboot for your X session to pick up the change.

Then, from the graphical desktop, open a terminal and run:

$ gnome-terminal -e sh

in the opened terminal, run:

$ umask

the number shown should be 0007, as set in the passwd file

[regression potential]

any regression would likely result in an incorrect umask for the user
whose passwd entry is modified.

[scope]

this is needed only for b

this is fixed in systemd upstream by commit
5e37d1930b41b24c077ce37c6db0e36c745106c7 which was first included in
v246, so this is fixed in g and later. This commit was also picked up by
Debian and included in the v245 release for focal, so this is fixed in
focal already.

[original description]

In order to set the default umask of my users to 027 or 007, I followed
the instructions provided in 'man pam_umask' :

In the 'gecos' field of '/etc/passwd', I have inserted 'umask=027' or
'umask=007' (for myself).

Then, MOST graphical applications systematically run with the correct
umask.

In particular, when I press Alt-F2, run 'xterm sh' and type 'umask', it
systematically displays 0007.

But when I press Alt-F2, run 'gnome-terminal -e sh' and type 'umask', it
systematically displays 0022.

That is BAD, and is a security issue.

Workaround :  Inside the newly created '/etc/profile.d/umask.sh', and in each 
'~/.bashrc', add following content :
UMASK="$(grep  -o  "^$USER:.*,umask=0[0-7]*"  /etc/passwd)"
if  [ "$UMASK" ];  then
  umask  "${UMASK#$USER:*,umask=}"
fi

In fact, 'gnome-terminal' MUST NOT force umask=022, but keep umask
unchanged.

Thank you in advance for a quick correction.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: gnome-terminal 3.20.2-1ubuntu8
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CurrentDesktop: X-Cinnamon
Date: Mon Apr 24 08:36:58 2017
InstallationDate: Installed on 2017-03-28 (26 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu-translations
 Importance: Medium
 Status: Confirmed

** Affects: systemd
 Importance: Unknown
 Status: Unknown

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

** Affects: systemd (Ubuntu Bionic)
 Importance: Medium
 Assignee: Dan Streetman (ddstreet)
 Status: Fix Committed


** Tags: amd64 apport-bug artful bionic eoan verification-needed 
verification-needed-bionic zesty
-- 
'systemd --user' unduly forces umask=0022
https://bugs.launchpad.net/bugs/1685754
You received this bug notification because you are a member of Ubuntu 
Translations Coordinators, which is subscribed to Ubuntu Translations.

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1685754] [NEW] 'systemd --user' unduly forces umask=0022

[Launchpad Bug Tracker]

*** This bug is a security vulnerability ***

You have been subscribed to a public security bug:

[impact]

pam_umask, from /etc/passwd, is not honored in systemd --user instances

[test case]

on a desktop system, edit /etc/passwd to change the test user entry
(e.g. the 'ubuntu' user) to include 'umask=007' in the GECOS field (5th
field). For example change:

ubuntu:x:1000:1000:Ubuntu:/home/ubuntu:/bin/bash

to:

ubuntu:x:1000:1000:Ubuntu,umask=007:/home/ubuntu:/bin/bash

You may need to reboot for your X session to pick up the change.

Then, from the graphical desktop, open a terminal and run:

$ gnome-terminal -e sh

in the opened terminal, run:

$ umask

the number shown should be 0007, as set in the passwd file

[regression potential]

any regression would likely result in an incorrect umask for the user
whose passwd entry is modified.

[scope]

this is needed only for b

this is fixed in systemd upstream by commit
5e37d1930b41b24c077ce37c6db0e36c745106c7 which was first included in
v246, so this is fixed in g and later. This commit was also picked up by
Debian and included in the v245 release for focal, so this is fixed in
focal already.

[original description]

In order to set the default umask of my users to 027 or 007, I followed
the instructions provided in 'man pam_umask' :

In the 'gecos' field of '/etc/passwd', I have inserted 'umask=027' or
'umask=007' (for myself).

Then, MOST graphical applications systematically run with the correct
umask.

In particular, when I press Alt-F2, run 'xterm sh' and type 'umask', it
systematically displays 0007.

But when I press Alt-F2, run 'gnome-terminal -e sh' and type 'umask', it
systematically displays 0022.

That is BAD, and is a security issue.

Workaround :  Inside the newly created '/etc/profile.d/umask.sh', and in each 
'~/.bashrc', add following content :
UMASK="$(grep  -o  "^$USER:.*,umask=0[0-7]*"  /etc/passwd)"
if  [ "$UMASK" ];  then
  umask  "${UMASK#$USER:*,umask=}"
fi

In fact, 'gnome-terminal' MUST NOT force umask=022, but keep umask
unchanged.

Thank you in advance for a quick correction.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: gnome-terminal 3.20.2-1ubuntu8
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CurrentDesktop: X-Cinnamon
Date: Mon Apr 24 08:36:58 2017
InstallationDate: Installed on 2017-03-28 (26 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu-translations
 Importance: Undecided
 Status: Invalid

** Affects: gnome-terminal
 Importance: Medium
 Status: Confirmed

** Affects: systemd
 Importance: Unknown
 Status: Unknown

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

** Affects: systemd (Ubuntu Bionic)
 Importance: Medium
 Assignee: Dan Streetman (ddstreet)
 Status: Fix Committed


** Tags: amd64 apport-bug artful bionic eoan verification-needed 
verification-needed-bionic zesty
-- 
'systemd --user' unduly forces umask=0022
https://bugs.launchpad.net/bugs/1685754
You received this bug notification because you are a member of Ubuntu 
Translations Coordinators, which is subscribed to Ubuntu Translations.

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1685754] [NEW] 'systemd --user' unduly forces umask=0022

[Launchpad Bug Tracker]

*** This bug is a security vulnerability ***

You have been subscribed to a public security bug:

[impact]

pam_umask, from /etc/passwd, is not honored in systemd --user instances

[test case]

on a desktop system, edit /etc/passwd to change the test user entry
(e.g. the 'ubuntu' user) to include 'umask=007' in the GECOS field (5th
field). For example change:

ubuntu:x:1000:1000:Ubuntu:/home/ubuntu:/bin/bash

to:

ubuntu:x:1000:1000:Ubuntu,umask=007:/home/ubuntu:/bin/bash

You may need to reboot for your X session to pick up the change.

Then, from the graphical desktop, open a terminal and run:

$ gnome-terminal -e sh

in the opened terminal, run:

$ umask

the number shown should be 0007, as set in the passwd file

[regression potential]

any regression would likely result in an incorrect umask for the user
whose passwd entry is modified.

[scope]

this is needed only for b

this is fixed in systemd upstream by commit
5e37d1930b41b24c077ce37c6db0e36c745106c7 which was first included in
v246, so this is fixed in g and later. This commit was also picked up by
Debian and included in the v245 release for focal, so this is fixed in
focal already.

[original description]

In order to set the default umask of my users to 027 or 007, I followed
the instructions provided in 'man pam_umask' :

In the 'gecos' field of '/etc/passwd', I have inserted 'umask=027' or
'umask=007' (for myself).

Then, MOST graphical applications systematically run with the correct
umask.

In particular, when I press Alt-F2, run 'xterm sh' and type 'umask', it
systematically displays 0007.

But when I press Alt-F2, run 'gnome-terminal -e sh' and type 'umask', it
systematically displays 0022.

That is BAD, and is a security issue.

Workaround :  Inside the newly created '/etc/profile.d/umask.sh', and in each 
'~/.bashrc', add following content :
UMASK="$(grep  -o  "^$USER:.*,umask=0[0-7]*"  /etc/passwd)"
if  [ "$UMASK" ];  then
  umask  "${UMASK#$USER:*,umask=}"
fi

In fact, 'gnome-terminal' MUST NOT force umask=022, but keep umask
unchanged.

Thank you in advance for a quick correction.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: gnome-terminal 3.20.2-1ubuntu8
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CurrentDesktop: X-Cinnamon
Date: Mon Apr 24 08:36:58 2017
InstallationDate: Installed on 2017-03-28 (26 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu-translations
 Importance: Undecided
 Status: Invalid

** Affects: gnome-session
 Importance: Undecided
 Status: Invalid

** Affects: gnome-terminal
 Importance: Medium
 Status: Confirmed

** Affects: systemd
 Importance: Unknown
 Status: Unknown

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

** Affects: systemd (Ubuntu Bionic)
 Importance: Medium
 Assignee: Dan Streetman (ddstreet)
 Status: Fix Committed


** Tags: amd64 apport-bug artful bionic eoan verification-needed 
verification-needed-bionic zesty
-- 
'systemd --user' unduly forces umask=0022
https://bugs.launchpad.net/bugs/1685754
You received this bug notification because you are a member of Ubuntu 
Translations Coordinators, which is subscribed to Ubuntu Translations.

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1685754] [NEW] 'systemd --user' unduly forces umask=0022

[Launchpad Bug Tracker]

*** This bug is a security vulnerability ***

You have been subscribed to a public security bug:

[impact]

pam_umask, from /etc/passwd, is not honored in systemd --user instances

[test case]

on a desktop system, edit /etc/passwd to change the test user entry
(e.g. the 'ubuntu' user) to include 'umask=007' in the GECOS field (5th
field). For example change:

ubuntu:x:1000:1000:Ubuntu:/home/ubuntu:/bin/bash

to:

ubuntu:x:1000:1000:Ubuntu,umask=007:/home/ubuntu:/bin/bash

You may need to reboot for your X session to pick up the change.

Then, from the graphical desktop, open a terminal and run:

$ gnome-terminal -e sh

in the opened terminal, run:

$ umask

the number shown should be 0007, as set in the passwd file

[regression potential]

any regression would likely result in an incorrect umask for the user
whose passwd entry is modified.

[scope]

this is needed only for b

this is fixed in systemd upstream by commit
5e37d1930b41b24c077ce37c6db0e36c745106c7 which was first included in
v246, so this is fixed in g and later. This commit was also picked up by
Debian and included in the v245 release for focal, so this is fixed in
focal already.

[original description]

In order to set the default umask of my users to 027 or 007, I followed
the instructions provided in 'man pam_umask' :

In the 'gecos' field of '/etc/passwd', I have inserted 'umask=027' or
'umask=007' (for myself).

Then, MOST graphical applications systematically run with the correct
umask.

In particular, when I press Alt-F2, run 'xterm sh' and type 'umask', it
systematically displays 0007.

But when I press Alt-F2, run 'gnome-terminal -e sh' and type 'umask', it
systematically displays 0022.

That is BAD, and is a security issue.

Workaround :  Inside the newly created '/etc/profile.d/umask.sh', and in each 
'~/.bashrc', add following content :
UMASK="$(grep  -o  "^$USER:.*,umask=0[0-7]*"  /etc/passwd)"
if  [ "$UMASK" ];  then
  umask  "${UMASK#$USER:*,umask=}"
fi

In fact, 'gnome-terminal' MUST NOT force umask=022, but keep umask
unchanged.

Thank you in advance for a quick correction.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: gnome-terminal 3.20.2-1ubuntu8
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
CurrentDesktop: X-Cinnamon
Date: Mon Apr 24 08:36:58 2017
InstallationDate: Installed on 2017-03-28 (26 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
SourcePackage: gnome-terminal
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gedit
 Importance: Undecided
 Status: Invalid

** Affects: gnome-session
 Importance: Undecided
 Status: Invalid

** Affects: gnome-terminal
 Importance: Medium
 Status: Confirmed

** Affects: ubuntu-translations
 Importance: Undecided
 Status: Invalid

** Affects: systemd
 Importance: Unknown
 Status: Unknown

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

** Affects: systemd (Ubuntu Bionic)
 Importance: Medium
 Assignee: Dan Streetman (ddstreet)
 Status: Fix Committed


** Tags: amd64 apport-bug artful bionic eoan verification-needed 
verification-needed-bionic zesty
-- 
'systemd --user' unduly forces umask=0022
https://bugs.launchpad.net/bugs/1685754
You received this bug notification because you are a member of Ubuntu 
Translations Coordinators, which is subscribed to Ubuntu Translations.

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1865226] [NEW] gdm-smartcard pam config needs to be updated for Ubuntu and installed

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

the pam profile for gdm-smartcard is missing. gdm refuses to login with
a smartcard. Looking at ubuntu/+source/gdm3, other pam files are
pregenerated into debian/ and installed from there; gdm-smartcard is
left out.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gdm3 3.28.3-0ubuntu18.04.4
ProcVersionSignature: Ubuntu 5.3.0-24.26~18.04.2-generic 5.3.10
Uname: Linux 5.3.0-24-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
ApportVersion: 2.20.9-0ubuntu7.11
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Feb 28 14:30:30 2020
InstallationDate: Installed on 2016-05-23 (1376 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.gdm3.Xsession: 2018-04-27T11:41:04.766901

** Affects: ubuntu-translations
 Importance: Undecided
 Status: New

** Affects: gnome-settings-daemon
 Importance: Unknown
 Status: Unknown

** Affects: gdm3 (Ubuntu)
 Importance: High
 Assignee: Marco Trevisan (Treviño) (3v1n0)
 Status: Confirmed

** Affects: gnome-settings-daemon (Ubuntu)
 Importance: Medium
 Assignee: Marco Trevisan (Treviño) (3v1n0)
 Status: In Progress

** Affects: gdm3 (Ubuntu Bionic)
 Importance: High
 Assignee: Marco Trevisan (Treviño) (3v1n0)
 Status: Won't Fix

** Affects: gdm3 (Ubuntu Focal)
 Importance: High
 Assignee: Marco Trevisan (Treviño) (3v1n0)
 Status: Confirmed

** Affects: gnome-settings-daemon (Ubuntu Focal)
 Importance: Undecided
 Assignee: Marco Trevisan (Treviño) (3v1n0)
 Status: New

** Affects: gdm3 (Ubuntu Groovy)
 Importance: High
 Assignee: Marco Trevisan (Treviño) (3v1n0)
 Status: Confirmed

** Affects: gnome-settings-daemon (Ubuntu Groovy)
 Importance: Undecided
 Assignee: Marco Trevisan (Treviño) (3v1n0)
 Status: New

** Affects: gdm3 (Debian)
 Importance: Unknown
 Status: Unknown


** Tags: amd64 apport-bug bionic third-party-packages
-- 
gdm-smartcard pam config needs to be updated for Ubuntu and installed
https://bugs.launchpad.net/bugs/1865226
You received this bug notification because you are a member of Ubuntu 
Translations Coordinators, which is subscribed to Ubuntu Translations.

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1903864] [NEW] qemu-system-x86_64: -device tpm-tis, tpmdev=tpm-tpm0, id=tpm0: Property 'tpm-tis.tpmdev' can't find value 'tpm-tpm0'

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

[Impact]

 * TPM isn't always easy, but at least some rough edges can be improved.
   In this case some qemu commandlines will lead to odd error reporting
   which is a) a false-positive and b) blocking the use case.

 * This was fixed upstream and hereby the fix is backported

[Test Case]

Easiest - using passthrough:
You need a system that has a TPM:

$ sudo qemu-system-x86_64 -nodefaults -S -display none -monitor stdio
-tpmdev passthrough,id=tpm0,path=/dev/tpm0 -device tpm-tis,tpmdev=tpm0

If you enter the qemu monitor you are good, if qemu doesn't start
complaining about its command line arguments then the error is still
present.

One can (if you want to go the extra mile) also set up a swtpm based
emulator and try that. But swtpm isn't in the archive yet and trousers
(a dependency) has issues on install. Commands would then be like:

$ swtpm socket --tpmstate dir=/tmp/mytpm1 --ctrl 
type=unixio,path=/tmp/mytpm1/swtpm-sock --log level=20
$ qemu-system-x86_64 -nodefaults -S -display none -monitor stdio -chardev 
socket,id=chrtpm,path=/tmp/mytpm1/swtpm-sock -tpmdev 
emulator,id=tpm0,chardev=chrtpm -device tpm-tis,tpmdev=tpm0



[Where problems could occur]

 * The changes are local only to the tpm code in qemu. So we can assume
   that other areas will unlikely be affected, but at the same time errors
   would occur in exactly that place. So for the time after release our 
   bug triage can be extra careful if anyone mentioned qemu+tpm to spot 
   regressions.

[Other Info]
 
 * n/a




Hello. The TPM device in virt-manager never really worked in Ubuntu (I tried 
upgrades from 16.04 to 20.04 and each of them exhibited a different kind of 
issues).
The Ubuntu 20.04 versions of libvirt/qemu are throwing the following error:

qemu-system-x86_64: -device tpm-tis,tpmdev=tpm-tpm0,id=tpm0: Property
'tpm-tis.tpmdev' can't find value 'tpm-tpm0'

Our employer changed a security policy, requiring encrypted drives and
that endangers usage of Linux as the host system without making the tpm
passthrough working.

Versions:
libvirt0:amd64  6.0.0-0ubuntu8.5
qemu-kvm1:4.2-3ubuntu6.8
virt-manager1:2.2.1-3ubuntu2.1

** Affects: ubuntu-translations
 Importance: Undecided
 Status: Invalid

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

** Affects: qemu (Ubuntu Focal)
 Importance: Undecided
 Status: Fix Committed

** Affects: qemu (Ubuntu Groovy)
 Importance: Undecided
 Status: Fix Committed


** Tags: block-proposed block-proposed-focal block-proposed-groovy server-next 
verification-needed verification-needed-focal verification-needed-groovy
-- 
qemu-system-x86_64: -device tpm-tis,tpmdev=tpm-tpm0,id=tpm0: Property 
'tpm-tis.tpmdev' can't find value 'tpm-tpm0'
https://bugs.launchpad.net/bugs/1903864
You received this bug notification because you are a member of Ubuntu 
Translations Coordinators, which is subscribed to Ubuntu Translations.

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1868703] [NEW] Support "ad_use_ldaps" flag for new AD requirements (ADV190023)

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

***
[NOTE FOR SRU VERIFICATION TEAM]

>From security team :
"
Since this is more of a hardening measure and does not directly fix a
security vulnerability it is not really appropriate to go to just
-security - and so the SRU process should be followed as normal. Once
this is complete for the respective releases, please re-ping us and we
can sponsor it to -security then.
"
***

[Impact]

Microsoft has released a new security advisory for Active Directory (AD)
which outlines that man-in-the-middle attacks can be performed on a LDAP
server, such as AD DS, that works by an attacker forwarding an
authentication request to a Windows LDAP server that does not enforce
LDAP channel binding or LDAP signing for incoming connections.

To address this, Microsoft has announced new Active Directory
requirements in ADV190023 [1][2].

[1] https://msrc.microsoft.com/update-guide/en-us/vulnerability/ADV190023
[2] 
https://support.microsoft.com/en-us/help/4520412/2020-ldap-channel-binding-and-ldap-signing-requirements-for-windows

These new requirements strongly encourage system administrators to
require LDAP signing and authenticated channel binding in their AD
environments.

The effects of this is to stop unauthenticated and unencrypted traffic
from communicating over LDAP port 389, and to force authenticated and
encrypted traffic instead, over LDAPS port 636 and Global Catalog port
3629.

Microsoft will not be forcing this change via updates to their servers,
system administrators must opt in and change their own configuration.

To support these new requirements in Ubuntu, changes need to be made to
the sssd and adcli packages. Upstream have added a new flag
"ad_use_ldaps" to sssd, and "use-ldaps" has been added to adcli.

If "ad_use_ldaps = True", then sssd will send all communication over
port 636, authenticated and encrypted.

For adcli, if the server supports GSS-SPNEGO, it will be now be used by
default, with the normal LDAP port 389. If the LDAP port is blocked,
then "use-ldaps" can now be used, which will use the LDAPS port 636
instead.

This is currently reporting the following on Ubuntu 18.04/20.04LTS
machines with the following error:

"[sssd] [sss_ini_call_validators] (0x0020):
[rule/allowed_domain_options]: Attribute 'ad_use_ldaps' is not allowed
in section 'domain/test.com'. Check for typos."

These patches are needed to stay in line with Microsoft security
advisories, since security conscious system administrators would like to
firewall off the LDAP port 389 in their environments, and use LDAPS port
636 only.

[Testcase]

To test these changes, you will need to set up a Windows Server 2019
box, install and configure Active Directory, import the AD certificate
to the Ubuntu clients, and create some users in Active Directory.

>From there, you can try do a user search from the client to the AD
server, and check what ports are used for communication.

Currently, you should see port 389 in use:

$ sudo netstat -tanp |grep sssd
tcp 0 0 x.x.x.x:43954 x.x.x.x:389 ESTABLISHED 27614/sssd_be
tcp 0 0 x.x.x.x:54381 x.x.x.x:3268 ESTABLISHED 27614/sssd_be

Test packages are available in the following ppa:

https://launchpad.net/~mruffell/+archive/ubuntu/sf294530-test

Instructions to install (on a bionic or focal system):
1) sudo add-apt-repository ppa:mruffell/sf294530-test
2) sudo apt update
3) sudo apt install adcli sssd

Then, modify /etc/sssd/sssd.conf and add "ad_use_ldaps = True", restart
sssd.

Add a firewall rule to block traffic to LDAP port 389 and Global Catalog
3268.

$ sudo ufw deny 389
$ sudo ufw deny 3268

Then do another user lookup, and check ports in use:

$ sudo netstat -tanp |grep sssd
tcp 0 0 x.x.x.x:44586 x.x.x.x:636 ESTABLISHED 28474/sssd_be
tcp 0 0 x.x.x.x:56136 x.x.x.x:3269 ESTABLISHED 28474/sssd_be

We see LDAPS port 636, and Global Catalog port 3629 in use. The user
lookup will succeed even with ports 389 and 3268 blocked, since it uses
their authenticated and encrypted variants instead.

[Where problems could occur]

Firstly, the adcli and sssd packages will continue to work with AD
servers that haven't had LDAP signing or authenticated channel binding
enforced, due to the measures being optional.

For both sssd and adcli, the changes don't implement anything new, and
instead, the changes add configuration and logic to "select" what
protocol to use to talk to the AD server. LDAP and LDAPS are already
implemented in both sssd and adcli, the changes just add some logic to
select the use of LDAPS over LDAP.

For sssd, the changes are hidden behind configuration parameters, such
as "ldap_sasl_mech" and "ad_use_ldaps". If a regression were to occur,
it would be limited to systems where the system administrator had
enabled these configuration options to the /etc/sssd/sssd.conf file.

For adcli, the changes are more immediate. adcli will now use GSS-SPENGO
by default if the server supports it, which is a behaviour change. The
"use-ldaps" option is a flag on t

[Ubuntu-translations-coordinators] [Bug 1883497] [NEW] Only timing mode list in EDID supported on continuous freq monitors

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

[Impact]
Some new laptop display set EDID continuous freq bit 1.
Then Xorg only uses the timing modes defined in EDID, no other modes are shown 
on Xorg.

Upstream Bug:
https://gitlab.freedesktop.org/drm/intel/-/issues/313

Fix of Xorg in merge request:
https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/421

https://cgit.freedesktop.org/xorg/xserver/commit/?id=6a79a737e2c0bc730ee693b4ea4a1530c108be4e

this is required to support new laptop models which use such panels

[Test case]
Test that a proper list of modes is shown with a panel that uses the new EDID.

[Regression potential]
The patch retains the previous code path for setting modes on GTF-able 
monitors, and only adds support for non-GTF monitors. So in that sense there 
shouldn't be any regression potential, this has been reviewed by an upstream 
expert.

** Affects: hwe-next
 Importance: Undecided
 Status: New

** Affects: ubuntu-translations
 Importance: Undecided
 Status: New

** Affects: xserver-xorg-video-intel
 Importance: Unknown
 Status: Unknown

** Affects: xorg-server (Ubuntu)
 Importance: Critical
 Assignee: Timo Aaltonen (tjaalton)
 Status: Fix Released

** Affects: xorg-server (Ubuntu Bionic)
 Importance: Undecided
 Assignee: Timo Aaltonen (tjaalton)
 Status: Fix Released

** Affects: xorg-server-hwe-18.04 (Ubuntu Bionic)
 Importance: Undecided
 Status: Fix Released

** Affects: xorg-server (Ubuntu Focal)
 Importance: Undecided
 Assignee: Timo Aaltonen (tjaalton)
 Status: Fix Released

** Affects: xorg-server (Ubuntu Groovy)
 Importance: Undecided
 Assignee: Timo Aaltonen (tjaalton)
 Status: Fix Committed


** Tags: oem-priority originate-from-1881988 originate-from-1882188 
originate-from-1883198 sutton verification-done-bionic verification-done-focal 
verification-needed verification-needed-groovy
-- 
Only timing mode list in EDID supported on continuous freq monitors
https://bugs.launchpad.net/bugs/1883497
You received this bug notification because you are a member of Ubuntu 
Translations Coordinators, which is subscribed to Ubuntu Translations.

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1895358] [NEW] [Bug] A simple code including tgmath.h cannot be compiled with icc with Ubuntu 20.04 OS

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

[Impact]

 A simple code including tgmath.h cannot be compiled with icc with
Ubuntu 20.04 OS and later releases.

[Test Case]
icc:
 Compile the following code with Intel compiler (icc) by running “icc -c test.c”

$ cat test.c
#include 

There should not be any compilation error


[Where problems could occur]

The fix is dropping compile time check preventing using float128 with
icc. In case of a mistake using float128 becomes prevented in other
compilers as well, but this is highly unlikely, since the vanilla
upstream code is known to work.

Older icc compilers (for which the patch has been introduced) will stop
compiling code with the _fixed_ tgmath.h because of LP: #1717257.

Users can still install older icc compilers from 3rd party sources, but
there is no good way of avoiding that. They can still override the
packaged tgmath.h.

[Original Bug Text]

[Summary]: A simple code including tgmath.h cannot be compiled with icc
with Ubuntu 20.04 OS

[Ubuntu OS version]: 20.04

[Reproduce Steps]: Compile the following code with Intel compiler (icc)
by running “icc -c test.c”

$ cat test.c
#include 

[Results]
Expected: There should not be any compilation error

Actual: The following error is produced:

$ icc -c test.c
In file included from 
/localdisk2/mkl/aakkas/20200721_rls/lnx/compiler/latest/linux/bin/intel64/../../compiler/include/icc/tgmath.h(25),
 from test.c(1):
/usr/include/tgmath.h(54): error: #error directive: "Unsupported combination of 
types for ."
  #  error "Unsupported combination of types for ."
 ^

compilation aborted for test.c (code 2)

[Additional Information on Test setup]:

ICC compiler supports the __float128 type if the reference compiler is
more recent than GNU version 4.4. Therefore, __HAVE_FLOAT128 should be
set to 1 when ICC compiler is used with GNU version higher than 4.4.
Based on this, I believe that the red part below in floatn.h, which
comes with Ubuntu OS, should be updated/removed.

#if (defined __x86_64__ \
 ? __GNUC_PREREQ (4, 3) \
 : (defined __GNU__ ? __GNUC_PREREQ (4, 5) : __GNUC_PREREQ (4, 4))) \
 &&  !defined(__CUDACC__) && !defined(__ICC)
# define __HAVE_FLOAT128 1
#else
# define __HAVE_FLOAT128 0
#endif

Currently, when the tgmath.h system header file is included on Ubuntu
20.04 OS system,  __HAVE_FLOAT128 is set to zero and __HAVE_FLOAT64X set
to 1 for ICC. And this is not a supported combination as checked in the
new tgmath.h system header file:

# if ((__HAVE_FLOAT64X && !__HAVE_FLOAT128) \
  || (__HAVE_FLOAT128 && !__HAVE_FLOAT64X))
#  error "Unsupported combination of types for ."
# endif

Upstream bug: Not known
=

** Affects: ubuntu-translations
 Importance: Undecided
 Status: Invalid

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

** Affects: glibc (Ubuntu Focal)
 Importance: Undecided
 Assignee: Balint Reczey (rbalint)
 Status: Fix Released

** Affects: glibc (Ubuntu Groovy)
 Importance: Undecided
 Assignee: Balint Reczey (rbalint)
 Status: Fix Committed


** Tags: block-proposed-groovy fr-900 intel verification-done 
verification-done-focal verification-done-groovy
-- 
[Bug] A simple code including tgmath.h cannot be compiled with icc with Ubuntu 
20.04 OS
https://bugs.launchpad.net/bugs/1895358
You received this bug notification because you are a member of Ubuntu 
Translations Coordinators, which is subscribed to Ubuntu Translations.

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1903984] [NEW] [UBUNTU 20.04] Cannot run zcryptstats in the Hosting Appliance

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

SRU Justification:
==

[Impact]

 * If multiple s390x crypto domains are available,
   the output of all domains does no longer fit into the output buffer of one 
CHSC call.

 * Thus, the response contains a partial-response-snippet that indicates
that there is more data to be retrieved.

 * The remaining data is then retrieved in a subsequent CHSC call,
   but there is an error in zcryptstats in populating the request with the next 
domain number to obtain data for.

 * This results in the fact that it retrieves the data for domains 1 to n over 
and over again,
   and always gets the partial-response snippet, hence this loops indefinitely.

[Test Case]

 * An Ubuntu Server 20.04 system (or newer) is needed on z/VM or LPAR
with two or more crypto domains accessible.

 * Now call 'zcryptstats --all -V' and verify if the command completes
successfully (within seconds) or hangs (loops).

[Where problems could occur]

 * The patch fixes the code that passes the correct next-domain to the
subsequent CHSC call of a partial response.

 * In case done wrong even no data at all from any of the domains is
retrieved,

 * or the tool may even try to retrieve data from a domain that has an
invalid index, which will lead to an error (the rc is captured).

 * But the code changes are marginal and pretty straight forward, and
the cases where scdmd_area.request.first_drid is handled are now
enclosed by proper 'if/else' statement.

 * This patch was already upstream accepted and a patched s390-tools package 
was build and shared in a PPA for further testing.
__
---Problem Description---
I have had trouble collecting data via the zcryptstats 
(https://github.com/ibm-s390-tools/s390-tools/blob/master/zconf/zcrypt/zcryptstats.c)
 tool for our Hosting Appliance - VPC environment. Basically, the tool reports 
data for only the last two domain IDs. Further, it hangs if I collect data for 
a complete crypto card, and then I have to kill the ssh session to get back.

strace attached, ltrace not available and can't be installed due to no
Internet access.

===

Addl. Information:

This seems to be a problem with the handling of partial responses of the
SCDMD CHSC command.

When many domains are available, then the output of all domains does not
fit into the output buffer of one CHSC call. Thus, the response contains
a partial-response-bit that indicates that there is more data to be
retrieved. This is done in a subsequent CHSC call, but there is an error
in zcryptstats with populating the request with the next domain number
to obtain data for. This results in the fact that it retrieves the data
for domains 1 to n over and over again, and always gets the partial-
response bit set. So this loops forever.

===
The fix for this in now upstream:
https://github.com/ibm-s390-tools/s390-tools/commit/cf2311f1f1de17435b49ba8c8697be91705ba031

This need to be integrated in all Ubuntu distros, from 20.04 on. F/G/H

** Affects: ubuntu-translations
 Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
 Status: Invalid

** Affects: ubuntu-z-systems
 Importance: Medium
 Assignee: Skipper Bug Screeners (skipper-screen-team)
 Status: Triaged

** Affects: s390-tools (Ubuntu)
 Importance: Medium
 Status: Fix Committed

** Affects: s390-tools (Ubuntu Focal)
 Importance: Medium
 Assignee: Frank Heimes (fheimes)
 Status: Triaged

** Affects: s390-tools (Ubuntu Groovy)
 Importance: Medium
 Assignee: Frank Heimes (fheimes)
 Status: Triaged

** Affects: s390-tools (Ubuntu Hirsute)
 Importance: Medium
 Status: Fix Committed


** Tags: architecture-s39064 bugnameltc-189183 patch severity-medium 
targetmilestone-inin2004
-- 
[UBUNTU 20.04] Cannot run zcryptstats in the Hosting Appliance
https://bugs.launchpad.net/bugs/1903984
You received this bug notification because you are a member of Ubuntu 
Translations Coordinators, which is subscribed to Ubuntu Translations.

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1867996] [NEW] Segfault in app_indicator_set_icon_full [patch attached]

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

[ Impact ]

Discord and several other applications using libappindicator are widely
reported to have been crashing for several years. See:
https://github.com/flathub/com.discordapp.Discord/issues/30 (and others)

[ Test case ]

- Run discord application
- It must not crash in ubuntu (or when indicators are enabled)

[ Regression potential ]

Very low, icons might not appear in some cases, if any.

-

This is the backtrace:
(gdb) bt full
#0  0x7fe1d5d2e00e in  () at /app/lib/libappindicator.so
#1  0x7fe1f5a6f3c5 in g_closure_invoke () at /lib/libgobject-2.0.so.0
#2  0x7fe1f5a813d2 in  () at /lib/libgobject-2.0.so.0
#3  0x7fe1f5a8a02c in g_signal_emit_valist () at /lib/libgobject-2.0.so.0
#4  0x7fe1f5a8a40f in g_signal_emit () at /lib/libgobject-2.0.so.0
#5  0x7fe1d5d2ed4f in app_indicator_set_icon_full () at 
/app/lib/libappindicator.so
#6  0x0077851a in  ()
#7  0x01de7123 in  ()
#8  0x01e4bd4e in  ()
#9  0x01e6e34c in  ()
#10 0x01e6e668 in  ()
#11 0x01e6e9cb in  ()
#12 0x01df971a in  ()
#13 0x7fe1f354b1c7 in g_main_context_dispatch () at /lib/libglib-2.0.so.0
#14 0x7fe1f354b430 in  () at /lib/libglib-2.0.so.0
#15 0x7fe1f354b4dc in g_main_context_iteration () at /lib/libglib-2.0.so.0
#16 0x01df9606 in  ()
#17 0x01e6e0e7 in  ()
#18 0x01e29570 in  ()
#19 0x00c37ec8 in  ()
#20 0x00c37d15 in  ()
#21 0x00c1da7d in  ()
#22 0x00a9282e in  ()
#23 0x007892d4 in  ()
#24 0x007896e0 in  ()
#25 0x03b830a3 in main ()

Happens in all versions of libappindicator built from latest sources
available on launchpad.

I ran into the issue yesterday when installing Discord for the first
time. I have tracked the problem down to libappindicator passing in an
extra vararg item to g_signal_emit that the signal's definition in
libappindicator was not declaring, causing the crash you see above in
gobject's g_signal dispatch machinery.

Patch is attached.

I am presuming this is 'upstream' for libappindicator, whatever that may
mean for what appears to be an unmaintained project. If it is not, and
since it is an Ubuntu/Canonical-sourced project originally, I
respectfully request that you assist in upstreaming it since this bug is
causing severe breakage for users across all distros.

** Affects: libappindicator (Ubuntu)
 Importance: Undecided
 Assignee: Marco Trevisan (Treviño) (3v1n0)
 Status: Fix Released

** Affects: libappindicator (Ubuntu Bionic)
 Importance: Undecided
 Assignee: Marco Trevisan (Treviño) (3v1n0)
 Status: Fix Committed

** Affects: ubuntu-translations
 Importance: Undecided
 Status: New


** Tags: patch verification-done-bionic
-- 
Segfault in app_indicator_set_icon_full [patch attached]
https://bugs.launchpad.net/bugs/1867996
You received this bug notification because you are a member of Ubuntu 
Translations Coordinators, which is subscribed to Ubuntu Translations.

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1727470] Re: [RFE] Automatically update the Ubuntu version strings in python-apt

[Launchpad Bug Tracker]

This bug was fixed in the package python-apt - 2.1.7

---
python-apt (2.1.7) unstable; urgency=medium

  * SECURITY UPDATE: various memory and file descriptor leaks (LP: #1899193)
- python/arfile.cc, python/generic.h, python/tag.cc, python/tarfile.cc:
  fix file descriptor and memory leaks
- python/apt_instmodule.cc, python/apt_instmodule.h, python/arfile.h:
  Avoid reference cycle with control,data members in apt_inst.DebFile
  objects
- tests/test_cve_2020_27351.py: Test cases for DebFile (others not easily
  testable)
  * Regression fixes for the updates merged too:
- arfile.cc: Fix segmentation fault when opening fd, track lifetime 
correctly
  (Closes: #977000)
- arfile: Regression: Collect file<->deb/ar reference cycles

 -- Julian Andres Klode   Thu, 10 Dec 2020 15:35:32
+0100

** Changed in: python-apt (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1727470

Title:
  [RFE] Automatically update the Ubuntu version strings in python-apt

Status in Ubuntu Translations:
  Fix Released
Status in python-apt package in Ubuntu:
  Fix Released

Bug description:
  Every time there is a new Ubuntu release, some strings need to be
  manually translated although the only thing that is changing is the
  Ubuntu version and code name. Please, consider updating these strings
  automatically based on a translated template. It would help many
  translators.

  These strings are:
  Ubuntu xx.yy 'Code Name'
  Cdrom with Ubuntu xx.yy 'Code Name'

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

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 736005] Re: POFile:+translate timeouts

[Launchpad Bug Tracker]

** Merge proposal linked:
   https://code.launchpad.net/~cjwatson/launchpad/+git/launchpad/+merge/395934

-- 
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching subscriptions: Ubuntu Translations bug mail
https://bugs.launchpad.net/bugs/736005

Title:
  POFile:+translate timeouts

Status in JOSM:
  Unknown
Status in Launchpad itself:
  Triaged
Status in Odoo Addons (MOVED TO GITHUB):
  New
Status in Ubuntu Translations:
  Triaged

Bug description:
  
1 SELECT TranslationMessage.comment, TranslationMessage.date_created, 
TranslationMessage.date_revie ... gstr3, -$INT), COALESCE(msgstr4, -$INT), 
COALESCE(msgstr5, -$INT), date_created DESC ) LIMIT $INT:
 GET: 1 Robots: 0  Local: 1
1 
https://translations.launchpad.net/picapy/trunk/+pots/picapy/de/+translate 
(POFile:+translate)
 OOPS-1900K842

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

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1848286] [NEW] octavia is not reporting metrics like lbaasv2

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

[Environment]

Stein OpenStack
Ubuntu Bionic

[Description]

>From my understanding the current Octavia API should be backwards
compatible with LBaaS v2, therefore, the current LBaaS v2 pollster [1]
should suffice to gather the following meters:

meters:

- network.services.lb.outgoing.bytes
- network.services.lb.incoming.bytes
- network.services.lb.pool
- network.services.lb.listener
- network.services.lb.member
- network.services.lb.health_monitor
- network.services.lb.loadbalancer
- network.services.lb.total.connections
- network.services.lb.active.connections

However, the following warning is noticed when restarted the ceilometer
services.

2999:2019-11-07 15:05:41.665 22487 WARNING ceilometer.publisher.gnocchi [-] 
metric network.services.lb.loadbalancer is not handled by Gnocchi
3467:2019-11-07 15:06:21.830 3916 WARNING ceilometer.publisher.gnocchi [-] 
metric network.services.lb.loadbalancer is not handled by Gnocchi

In fact, by checking at the gnocchi metric list 
(https://pastebin.canonical.com/p/zyMTFv8vww/) the network.services.lb
metrics/resources haven't been created.

The reason is that for a gnocchi resource to exist, ceilometer has to create 
the resource type explicitly.
This action is commanded by the ceilometer gnocchi client [2] and it uses the 
file 
/usr/lib/python3/dist-packages/ceilometer/publisher/data/gnocchi_resources.yaml
for the resource definitions, which doesn't includes the lbaasv2 directives.

[Test case]

1) Deploy a gnocchi backed ceilometer unit with octavia deployed.
2) check that lb meters aren't being gathered

$ gnocchi metric list|grep loadbalancer | wc -l
0
3) install the patched version
4) configure all pollsters
$  juju config ceilometer enable-all-pollsters=true
5) sudo systemctl restart ceilometer*
6) sudo ceilometer-upgrade
7) Check that lb metrics are being gathered

ubuntu@niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi metric 
list|grep loadbalancer | wc -l
72

ubuntu@niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi metric 
list|grep network.services
| 3947b249-b1ed-489d-9f51-b7549b5b78ce | ceilometer-low | 
network.services.lb.loadbalancer | loadbalancer | 
f97838f1-215d-4fcb-bd78-61e1f9859507 |
| 5527c5b6-d17e-4218-868b-c8d5326575a6 | ceilometer-low | 
network.services.lb.active.connections | connection | 
f97838f1-215d-4fcb-bd78-61e1f9859507 |
| 57d63bcb-48e1-47fb-825c-1109ad7d966d | ceilometer-low | 
network.services.lb.loadbalancer | loadbalancer | 
82d129f3-64a5-40d6-a72b-7ae704046176 |
| 5d93c751-0645-4b7b-a315-26b0e96dda3d | ceilometer-low | 
network.services.lb.outgoing.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
| 71ace776-9216-40a4-848c-42e9cc6f93a0 | ceilometer-low | 
network.services.lb.listener | listener | e7a4dd96-73a1-4aca-946d-8e87ba8f7a37 |
| 738b1dd0-0930-4bfa-b358-1a27fb63121e | ceilometer-low | 
network.services.lb.total.connections | connection | 
f97838f1-215d-4fcb-bd78-61e1f9859507 |
| 7b4726f6-9490-4d6c-a586-7e12b738b001 | ceilometer-low | 
network.services.lb.health_monitor | health_monitor | 
3ebc3ac0-8e1c-47d9-8789-bb51e6d29eba |
| 8689e872-c6d0-450f-bb73-d19197c62418 | ceilometer-low | 
network.services.lb.incoming.bytes | B | 82d129f3-64a5-40d6-a72b-7ae704046176 |
| ae72c5f3-4d8b-400b-ba86-2aaf068c20fc | ceilometer-low | 
network.services.lb.incoming.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
| b59ef5ae-9d71-4884-bb7c-66e0d46f5ecb | ceilometer-low | 
network.services.lb.outgoing.bytes | B | f97838f1-215d-4fcb-bd78-61e1f9859507 |
| bdf259a1-7471-4c23-ab2b-cac11f522f45 | ceilometer-low | 
network.services.lb.active.connections | connection | 
82d129f3-64a5-40d6-a72b-7ae704046176 |
| e5d2e433-9482-4e2a-9485-e73d7a13271a | ceilometer-low | 
network.services.lb.listener | listener | c87e0f88-26bf-496f-a882-71b1c67956b4 |
| eb634e4e-8e94-4ee4-8fac-4f4db12d56aa | ceilometer-low | 
network.services.lb.total.connections | connection | 
82d129f3-64a5-40d6-a72b-7ae7040

[Regression Potential]

There is no regression potential identified on this patch as it uses
the new metrics upgrade path and it doesn't
enables any new metrics if the lbaasv2 pollster isn't configured.

[Proposed solution]

Enable the resources on /usr/lib/python3/dist 
packages/ceilometer/publisher/data/gnocchi_resources.yaml
and modify the gnocchi client provider. I am able to gather the metrics for the 
octavia load balancers.

ubuntu@niedbalski-bastion:~/stsstack-bundles/openstack$ gnocchi metric 
list|grep network.services
| 3947b249-b1ed-489d-9f51-b7549b5b78ce | ceilometer-low | 
network.services.lb.loadbalancer | loadbalancer | 
f97838f1-215d-4fcb-bd78-61e1f9859507 |
| 5527c5b6-d17e-4218-868b-c8d5326575a6 | ceilometer-low | 
network.services.lb.active.connections | connection | 
f97838f1-215d-4fcb-bd78-61e1f9859507 |
| 57d63bcb-48e1-47fb-825c-1109ad7d966d | ceilometer-low | 
network.services.lb.loadbalancer | loadbalancer | 
82d129f3-64a5-40d6-a72b-7ae704046176 |
| 5d93c751-0645-4b7b-a315

[Ubuntu-translations-coordinators] [Bug 1902944] [NEW] Cannot create a swift container, mandatory "Storage Policy" dropdown field is empty

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

[Impact]
focal-ussuri, charms revision 20.10

I can't create a container with GUI. When entering "Containers" tab, the
error "Error: Unable to fetch the policy details." appears.

If I proceed and try to create a container, I can't click "Submit"
button until I select a Storage Policy. But the mandatory "Storage
Policy" dropdown field is empty. See attached screenshot.

I can, however, create a container with a CLI. `openstack container
create c1` works fine.

[Test Case]
Deploy horizon with ceph radosgw instead of swift, navigate to 
http://horizon-ip/horizon/project/containers/ and attempt to create a 
container. With the package and charm fixes in this bug, it will be successful. 
Otherwise it will fail as described in this bug.

Note, we also want to test horizon with swift proper for this bug to
ensure it still works with the dashboard.

[Regression Potential]
It's possible this could regress horizon with swift proper as a backend so it 
should also be regression tested.

** Affects: ubuntu-translations
 Importance: Undecided
 Status: Invalid

** Affects: cloud-archive
 Importance: High
 Status: Fix Committed

** Affects: cloud-archive/ussuri
 Importance: High
 Status: Fix Committed

** Affects: cloud-archive/victoria
 Importance: High
 Status: Fix Committed

** Affects: horizon (Ubuntu)
 Importance: High
 Status: Fix Released

** Affects: python-swiftclient (Ubuntu)
 Importance: High
 Status: Fix Released

** Affects: horizon (Ubuntu Focal)
 Importance: High
 Status: Fix Committed

** Affects: python-swiftclient (Ubuntu Focal)
 Importance: High
 Status: Fix Committed

** Affects: horizon (Ubuntu Groovy)
 Importance: High
 Status: Fix Committed

** Affects: python-swiftclient (Ubuntu Groovy)
 Importance: High
 Status: Fix Released

** Affects: horizon (Ubuntu Hirsute)
 Importance: High
 Status: Fix Released

** Affects: python-swiftclient (Ubuntu Hirsute)
 Importance: High
 Status: Fix Released


** Tags: verification-focal-done verification-needed verification-needed-groovy 
verification-ussuri-needed verification-victoria-needed
-- 
Cannot create a swift container, mandatory "Storage Policy" dropdown field is 
empty
https://bugs.launchpad.net/bugs/1902944
You received this bug notification because you are a member of Ubuntu 
Translations Coordinators, which is subscribed to Ubuntu Translations.

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1580596] [NEW] Xenial & bionic vagrant box disk size is too small

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

[Impact]
Users could not use vagrant boxes as a full computer (or anything requiring 
more than 10G of memory). This was a regression from our behavior in 14.04

[Test Case]

vagrant init ubuntu/bionic64 (replace with ubuntu/eoan64 or ubuntu/xenial64 as 
needed)
vagrant up
vagrant ssh default
Run `df -H` inside the vagrant box
Observe Disk size of drive mounted at / (before the fix it will list ~10G, 
after the fix it will list ~40G)

[Regression Potential]

Making the disk size bigger for vagrant boxes does not increase the size
of the box when running (not until that extra size is used). Therefore,
the regression potential is low, as users with under 40G of disk space
are still able to launch the new Vagrant images without running out of
space.

The 40G was also present in 14.04, which should improve confidence that
our users can use 40G Vagrant images. This has also released with 20.04.

[Original Description]
The ubuntu/xenial64 box has only 10GB of disk whereas it was 40GB with the 
trusty box.

This makes the box not really usable as a desktop computer.

** Affects: cloud-images
 Importance: High
 Assignee: Pat Viafore (patviafore)
 Status: Fix Committed

** Affects: ubuntu-translations
 Importance: Undecided
 Assignee: Pat Viafore (patviafore)
 Status: New

** Affects: livecd-rootfs (Ubuntu)
 Importance: Medium
 Assignee: Pat Viafore (patviafore)
 Status: Fix Released

** Affects: livecd-rootfs (Ubuntu Xenial)
 Importance: Medium
 Status: Fix Committed

** Affects: livecd-rootfs (Ubuntu Bionic)
 Importance: Medium
 Status: Fix Committed


** Tags: verification-done-bionic verification-needed-xenial
-- 
Xenial & bionic vagrant box disk size is too small
https://bugs.launchpad.net/bugs/1580596
You received this bug notification because you are a member of Ubuntu 
Translations Coordinators, which is subscribed to Ubuntu Translations.

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1884580] [NEW] Nova novncproxy doesnt work - unexpected keyword

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

== Impact ==

SSL secured console access to instances in OpenStack clouds is broken.

== Test Case ==

Deploy OpenStack using TLS secured endpoints (juju + charms)
Boot instance, attempt to access console via dashboard - error in web page and
error seen in nova-novncproxy log file.


== Regression Potential ==

Medium - the fix is in eventlet's use of the SSL native library which was 
broken when wrapping sockets using the SSLContext class.  The fix has been
accepted upstream and is accompanied with a test case.


== Original Bug Report ==


Ubuntu Focal (20.04)
Openstack Ussuri (distro-proposed)
LXC
Nova Cloud Controller Charm Rev 68

When attempting to view the console in Horizon (Openstack Dashboard),
console frame returns "503 Service Unavailable", when checking the nova
cloud controller logs for nova-novncproxy, the following error appears:

2020-06-22 17:48:18.262 1463207 INFO nova.console.websocketproxy [-]
handler exception: wrap_socket() got an unexpected keyword argument
'_context'

Google seems to find related issues:
https://github.com/eventlet/eventlet/issues/526

as well as:

https://ask.openstack.org/en/question/127493/nova-novncproxy-fails-to-
connect-handler-exception-wrap_socket-got-an-unexpected-keyword-
argument-_context/

So it seems to be an issue with Python > 3.6, but I cannot downgrade
python version as it would break nova-novncproxy (already tried)

** Affects: ubuntu-translations
 Importance: Undecided
 Assignee: James Page (james-page)
 Status: Invalid

** Affects: python-eventlet (Ubuntu)
 Importance: High
 Assignee: James Page (james-page)
 Status: Fix Released

** Affects: python-eventlet (Ubuntu Focal)
 Importance: High
 Assignee: James Page (james-page)
 Status: Fix Released

** Affects: python-eventlet (Ubuntu Groovy)
 Importance: High
 Assignee: James Page (james-page)
 Status: Fix Released


** Tags: verification-done verification-done-focal
-- 
Nova novncproxy doesnt work - unexpected keyword 
https://bugs.launchpad.net/bugs/1884580
You received this bug notification because you are a member of Ubuntu 
Translations Coordinators, which is subscribed to Ubuntu Translations.

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1871268] [NEW] Installation fails due to useless immediate configuration error when "Install Third-Party Drivers" is selected

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

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

So what we do is change that to a warning.

[Test case]
Not available right now. Issues can flare up and then disappear again.

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

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

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

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

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

The following error message is displayed in /var/log/syslog
/plugininstall.py: Verifying downloads ...
/plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/gcc_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
/plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxcrypt/libcrypt-dev_4.4.10-10ubuntu4_amd64.deb: 
"Version: '4.4.10-10ubuntu4' not found."
/plugininstall.py: Failed to find package object for 
/cdrom//pool/main/g/gcc-defaults/g++_9.3.0-1ubuntu2_amd64.deb: "Version: 
'9.3.0-1ubuntu2' not found."
/plugininstall.py: Failed to find package object for 
/cdrom//pool/main/z/zlib/zlib1g_1.2.11.dfsg-2ubuntu1_i386.deb: "Version: 
'1.2.11.dfsg-2ubuntu1' not found."
/plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxau/libxau6_1.0.9-0ubuntu1_i386.deb: "Version: 
'1.0.9-0ubuntu1' not found."
/plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdmcp/libxdmcp6_1.1.3-0ubuntu1_i386.deb: "Version: 
'1.1.3-0ubuntu1' not found."
/plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-6_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
/plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxext/libxext6_1.3.4-0ubuntu1_i386.deb: "Version: 
'1.3.4-0ubuntu1' not found."
/plugininstall.py: Failed to find package object for 
/cdrom//pool/main/l/lm-sensors/libsensors5_3.6.0-2ubuntu1_i386.deb: "Version: 
'3.6.0-2ubuntu1' not found."
/plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libx11/libx11-xcb1_1.6.9-2ubuntu1_i386.deb: "Version: 
'1.6.9-2ubuntu1' not found."
/plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxdamage/libxdamage1_1.1.5-1_i386.deb: "Version: 
'1.1.5-1' not found."
/plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxfixes/libxfixes3_5.0.3-1_i386.deb: "Version: 
'5.0.3-1' not found."
/plugininstall.py: Failed to find package object for 
/cdrom//pool/main/libx/libxxf86vm/libxxf86vm1_1.1.4-1build1_i386.deb: "Version: 
'1.1.4-1build1' not found."
/plugininstall.py: Downloads verified successfully
ubiquity: Error in function: install
/plugininstall.py: Exception during installation:
/plugininstall.py: apt_pkg.Error: E:Could not configure 'libc6:i386'. , E:Could 
not perform immediate configuration on 'libgcc-s1:i386'. Please see man 5 
apt.conf under APT::Immediate-Configure for details. (2)
/plugininstall.py:

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.9
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu22
Architecture: amd64
CasperVersion: 1.442
Date: Mon Apr  6 20:17:07 2020
InstallCmdLine: file=/cdrom/preseed/xubuntu.seed only-ubiquity 
initrd=/casper/initrd quiet splash ---
LiveMediaBuild: Xubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
ProcEnviron:
 LANGUAGE=es_EC.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=es_EC.UTF-8
 LC_NUMERIC=C.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu-translations
 Importance: Undecided
 Status: New

** Affects: ubuntu-cdimage
 Importance: Undecided
 Status: Fix Released

** Affects: apt (Ubuntu)
 Importance: High
 Status: Fix Released

** Affects: apt (Ubuntu Bionic)
 Importance: Undecided
 Status: Triaged

** Affects: apt (Ubuntu Focal)
 Importa

[Ubuntu-translations-coordinators] [Bug 1897444] Re: Cannot find and translate the new Active Directory strings

[Launchpad Bug Tracker]

This bug was fixed in the package ubiquity - 20.10.12

---
ubiquity (20.10.12) groovy; urgency=medium

  [ Gunnar Hjalmarsson ]
  * d-i/patches/localechooser-post-base-installer.patch:
- Set sw (Swahili) as the default Kenya language (LP: #1763025)
  * Translation update (LP: #1897444)

  [ Sebastien Bacher ]
  * POTFILES.in entries were not updated after a directory rename

 -- Gunnar Hjalmarsson   Fri, 16 Oct 2020 11:41:38
+0100

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

-- 
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching subscriptions: Ubuntu Translations bug mail
https://bugs.launchpad.net/bugs/1897444

Title:
  Cannot find and translate the new Active Directory strings

Status in Ubuntu Translations:
  Triaged
Status in ubiquity package in Ubuntu:
  Fix Released

Bug description:
  I took the latest Ubuntu Groovy for test spin. When I came to the step
  for adding a user, I noticed the new Active Directory feature which
  was recently added (bug 1894055). These strings were untranslated, so
  I figured I could look them up and help complete the translations.

  However, I'm unable to find the strings in Launchpad
  https://translations.launchpad.net/ubuntu/groovy/+source/ubiquity/+pots
  /ubiquity-debconf/nb/+translate?batch=10&show=all&search=active

  (there's two other translation templates, but this is the one with the
  most strings)

  From what I could see from the merge proposal, the strings seem split
  out and translatable like all the others, so I'm not sure why they
  don't show up on Launchpad. Perhaps there's some syncing which hasn't
  been done when the latest version was uploaded?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: ubiquity 20.10.10
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.452
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 27 12:23:17 2020
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200923)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nb_NO.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1897444] Re: Cannot find and translate the new Active Directory strings

[Launchpad Bug Tracker]

** Merge proposal linked:
   https://code.launchpad.net/~gunnarhj/ubiquity/+git/ubiquity/+merge/392332

-- 
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching subscriptions: Ubuntu Translations bug mail
https://bugs.launchpad.net/bugs/1897444

Title:
  Cannot find and translate the new Active Directory strings

Status in Ubuntu Translations:
  Triaged
Status in ubiquity package in Ubuntu:
  Triaged

Bug description:
  I took the latest Ubuntu Groovy for test spin. When I came to the step
  for adding a user, I noticed the new Active Directory feature which
  was recently added (bug 1894055). These strings were untranslated, so
  I figured I could look them up and help complete the translations.

  However, I'm unable to find the strings in Launchpad
  https://translations.launchpad.net/ubuntu/groovy/+source/ubiquity/+pots
  /ubiquity-debconf/nb/+translate?batch=10&show=all&search=active

  (there's two other translation templates, but this is the one with the
  most strings)

  From what I could see from the merge proposal, the strings seem split
  out and translatable like all the others, so I'm not sure why they
  don't show up on Launchpad. Perhaps there's some syncing which hasn't
  been done when the latest version was uploaded?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: ubiquity 20.10.10
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.452
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 27 12:23:17 2020
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200923)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nb_NO.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1897444] Re: Cannot find and translate the new Active Directory strings

[Launchpad Bug Tracker]

This bug was fixed in the package ubiquity - 20.10.11

---
ubiquity (20.10.11) groovy; urgency=medium

  [ Jean-Baptiste Lallement ]
  * Remove popularity-contest.
  * Initialize text variables to fix crash in OEM mode (LP: #1898029)

  [ Sebastien Bacher ]
  * Updated translations (LP: #1897444)

  [ Dimitri John Ledkov ]
  * oem-config.target: Correct name of the NetworkManager.service unit
(LP: #1665384)
  * localechooser.patch: set my (Burmese) as the default Myanmar language.
(LP: #1872186)

 -- Dimitri John Ledkov   Wed, 14 Oct 2020 13:18:26
+0100

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

-- 
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching subscriptions: Ubuntu Translations bug mail
https://bugs.launchpad.net/bugs/1897444

Title:
  Cannot find and translate the new Active Directory strings

Status in Ubuntu Translations:
  Triaged
Status in ubiquity package in Ubuntu:
  Fix Released

Bug description:
  I took the latest Ubuntu Groovy for test spin. When I came to the step
  for adding a user, I noticed the new Active Directory feature which
  was recently added (bug 1894055). These strings were untranslated, so
  I figured I could look them up and help complete the translations.

  However, I'm unable to find the strings in Launchpad
  https://translations.launchpad.net/ubuntu/groovy/+source/ubiquity/+pots
  /ubiquity-debconf/nb/+translate?batch=10&show=all&search=active

  (there's two other translation templates, but this is the one with the
  most strings)

  From what I could see from the merge proposal, the strings seem split
  out and translatable like all the others, so I'm not sure why they
  don't show up on Launchpad. Perhaps there's some syncing which hasn't
  been done when the latest version was uploaded?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: ubiquity 20.10.10
  ProcVersionSignature: Ubuntu 5.8.0-18.19-generic 5.8.4
  Uname: Linux 5.8.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu45
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.452
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 27 12:23:17 2020
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
maybe-ubiquity quiet splash ---
  LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200923)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nb_NO.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1892162] Re: typo in po/fi.po

[Launchpad Bug Tracker]

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

** Changed in: ubuntu-release-upgrader (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching subscriptions: Ubuntu Translations bug mail
https://bugs.launchpad.net/bugs/1892162

Title:
  typo in po/fi.po

Status in Ubuntu Translations:
  Fix Committed
Status in ubuntu-release-upgrader package in Ubuntu:
  Confirmed

Bug description:
  There's a typo in the Finnish translation:

  :: > do-release-upgrade 
  Etsitään uutta Ubuntu-julkaisua
  LTS:n kehitysversiota ei ole saatavilla.
  Päivittääksesi viimeisimpään ei–LTS-kehitysversioon 
  aseta Prompt=normal /etc/upgrade-manager/release-upgrades –tiedostossa.

  there is no "/etc/upgrade-manager", should be "/etc/update-manager".

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.24
  ProcVersionSignature: Ubuntu 5.6.0-1020.20-oem 5.6.19
  Uname: Linux 5.6.0-1020-oem x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 19 12:10:11 2020
  InstallationDate: Installed on 2018-02-06 (924 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180206)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to focal on 2020-02-06 (194 days ago)
  VarLogDistupgradeXorgFixuplog:
   INFO:root:/usr/bin/do-release-upgrade running
   INFO:root:No xorg.conf, exiting

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

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1875339] [NEW] xorg does not use nvidia gpu on a I+N machine.

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

SRU Request:

[Test Case]
1) Enable the -proposed repository, and install the new ubuntu-drivers-common 
(1:0.8.1.1).

2) Check that the dpkg-dev package is also installed.

3) Restart your computer, and see if everything works correctly when
accessing the desktop.

[Regression Potential]
Low. No code was changed, only a missing dependency was added to solve the 
problem.


__
On a machine with I+N, I install with focal 20.04 image. I didn't turn on 
auto-login. I checked "install 3rd party driver" during installation. It does 
install Nvidia driver (440.82+really.440.64-0ubuntu6).

On first boot, I double check by run 'prime-select query'. It return
nvidia.

run nvidia-smi, no program is using NV GPU.

---
$ glxinfo -B
name of display: :1
display: :1  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
Vendor: Intel (0x8086)
Device: Mesa Intel(R) UHD Graphics 630 (CFL GT2) (0x3e9b)
Version: 20.0.4
Accelerated: yes
Video memory: 3072MB
Unified memory: yes
Preferred profile: core (0x1)
Max core profile version: 4.6
Max compat profile version: 4.6
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.2
OpenGL vendor string: Intel
OpenGL renderer string: Mesa Intel(R) UHD Graphics 630 (CFL GT2)
OpenGL core profile version string: 4.6 (Core Profile) Mesa 20.0.4
OpenGL core profile shading language version string: 4.60
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6 (Compatibility Profile) Mesa 20.0.4
OpenGL shading language version string: 4.60
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile

OpenGL ES profile version string: OpenGL ES 3.2 Mesa 20.0.4
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20
---

Run lsmod | grep nvidia, I got:

---
nvidia_uvm970752  0
nvidia_drm 49152  0
nvidia_modeset   1114112  1 nvidia_drm
nvidia  20430848  8 nvidia_uvm,nvidia_modeset
drm_kms_helper184320  2 nvidia_drm,i915
ipmi_msghandler   106496  2 ipmi_devintf,nvidia
drm   491520  11 drm_kms_helper,nvidia_drm,i915
---

I run

$ sudo prime-select intel
$ sudo prime-select nvidia
$ sudo reboot

After reboot, nothing changed.

However, previously, on the same machine, I once get it works. (nvidia-smi show 
some X related process use GPU, glxinfo -B show Nvidia). I remembered I create 
another admin account, and later on, I found it's fixed. I didn't remember what 
else exactly make it happened.
I re-installed again, and try to do more tests, can't fix it so far.

LP: #1875315 have all the log that it first fixed.
---

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
 GCC version:
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 27 18:58:04 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (rev 02) (prog-if 00 
[VGA controller])
   Subsystem: Dell UHD Graphics 630 (Mobile) [1028:091a]
   Subsystem: Dell GP107GLM [Quadro P620] [1028:091a]
InstallationDate: Installed on 2020-04-27 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: Dell Inc. Precision 3541
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic 
root=UUID=8c0e264c-f63c-4d5a-b85f-6faf4008b9e6 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/21/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.5.1
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.1:bd08/21/2019:svnDellInc.:pnPrecision3541:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:
dmi.product.family: Precision
dmi.product.name: Precision 3541
dmi.product.sku: 091A
dmi.sys.vendor: Dell Inc.
nvidia-settings:
 ERROR: Unable to load info from any available system

 ERROR: Unable to load info from any available system
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-

[Ubuntu-translations-coordinators] [Bug 1882531] Re: desktop context not localized

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-flashback - 3.36.4-0ubuntu1

---
gnome-flashback (3.36.4-0ubuntu1) focal; urgency=medium

  * New upstream bugfix release (LP: #1892628).
- Update lock screen window on monitor changes (LP: #1891855).
- Don't lock screen on suspend if automatic screen lock is disabled
  (LP: #1891681).
- Updated translations (LP: #1882531).

 -- Dmitry Shachnev   Sun, 23 Aug 2020 16:04:59
+0300

** Changed in: gnome-flashback (Ubuntu Focal)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching subscriptions: Ubuntu Translations bug mail
https://bugs.launchpad.net/bugs/1882531

Title:
  desktop context not localized

Status in Ubuntu Translations:
  Invalid
Status in gnome-flashback package in Ubuntu:
  Fix Released
Status in gnome-flashback source package in Focal:
  Fix Released

Bug description:
  [Impact]

  GNOME Flashback desktop is not localized into German.

  [Test Case]

  1. Enable German locale (de_DE.UTF-8).
  2. Log into the GNOME Flashback (Metacity) session.
  3. Right-click on the desktop to open the context menu.
  4. It should be in German, not in English.

  [Regression Potential]

  The regression can be that the translation is wrong. The German
  translation was done by me (Dmitry Shachnev), but it was reviewed and
  corrected by Tim Sabsch.

  [Original Description]

  Hi,

  at least in german environment the rightclick menu is not localized
  (and also the home-link).

  see screenshot attached

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

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1891733] [NEW] Support better Arabic font

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

As per the  discussion.

** Affects: ubuntu-translations
 Importance: Undecided
 Status: New

** Affects: language-selector (Ubuntu)
 Importance: Undecided
 Status: New

-- 
Support better Arabic font
https://bugs.launchpad.net/bugs/1891733
You received this bug notification because you are a member of Ubuntu 
Translations Coordinators, which is subscribed to Ubuntu Translations.

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1861177] [NEW] seccomp_rule_add is very slow

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

[IMPACT]
There is a known and patched issue with version 2.4 of libseccomp where certain 
operations have a large performance regression. This is causing some packages 
that use libseccomp such as container orchestration systems to occasionally 
time out or otherwise fail under certain workloads.

Please consider porting the patch into the various Ubuntu versions that
have version 2.4 of libseccomp and into the backports. The performance
patch from version 2.5 (yet to be released) applies cleanly on top of
the 2.4 branch of libseccomp.

For more information, and for a copy of the patch (which can also be
cherry picked from the upstream libseccomp repos) see the similar Debian
issue: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943913

Upstream issue : https://github.com/seccomp/libseccomp/issues/153
Upstream fix : https://github.com/seccomp/libseccomp/pull/180/

[Test Case]

For this test case we use Docker on Ubuntu Groovy (20.10) :

--> Current libseccomp version
#dpkg -l | grep libseccomp
ii  libseccomp2:amd64  2.4.3-1ubuntu3   
   amd64high level interface to Linux seccomp filter

## pull ubuntu image
# docker pull ubuntu
## create a container
# docker run --name test_seccomp -it 74435f89ab78 /bin/bash

## run test case
# for i in `seq 1 40`; do (time sudo docker exec test_seccomp true &); done
...
MAX TIME :
real0m10,319s
user0m0,018s
sys 0m0,033s


--> Patched libseccomp version

# dpkg -l | grep libseccomp
ii  libseccomp2:amd64  2.4.3-1ubuntu4   
   amd64high level interface to Linux seccomp filter

# docker start test_seccomp
## run test case
# for i in `seq 1 40`; do (time sudo docker exec test_seccomp true &); done
...
MAX TIME :
real0m3,650s
user0m0,025s
sys 0m0,028s

[Regression Potential]

The first of the 2 patches cleans up the code that adds rules to a
single filter without changing the logic of the code. The second patch
introduces the idea of shadow transactions. On a successful transaction
commit the old transaction checkpoint is preserved and is brought up to
date with the current filter. The next time a new transaction starts, it
checks is the a shadow transaction exist and if so the shadow is used
instead of creating a new checkpoint from scratch [1]. This is the patch
that mitigates the performance regression. Any potential regression will
involve the parts of the code that add rules to filters and/or the code
that creates and checks the shadow transactions.


[Other]

Affected releases : Groovy, Focal, Eoan, Bionic, Xenial.

[1]
https://github.com/seccomp/libseccomp/pull/180/commits/bc3a6c0453b0350ee43e4925482f705a2fbf5a4d

** Affects: ubuntu-translations
 Importance: Medium
 Status: Invalid

** Affects: libseccomp (Ubuntu)
 Importance: Medium
 Assignee: Ioanna Alifieraki (joalif)
 Status: Fix Released

** Affects: libseccomp (Ubuntu Xenial)
 Importance: Medium
 Assignee: Ioanna Alifieraki (joalif)
 Status: Fix Released

** Affects: libseccomp (Ubuntu Bionic)
 Importance: Medium
 Assignee: Ioanna Alifieraki (joalif)
 Status: Fix Released

** Affects: libseccomp (Ubuntu Eoan)
 Importance: Medium
 Assignee: Ioanna Alifieraki (joalif)
 Status: Won't Fix

** Affects: libseccomp (Ubuntu Focal)
 Importance: Medium
 Assignee: Ioanna Alifieraki (joalif)
 Status: Fix Released

** Affects: libseccomp (Ubuntu Groovy)
 Importance: Medium
 Assignee: Ioanna Alifieraki (joalif)
 Status: Fix Released


** Tags: patch verification-done-bionic verification-done-eoan 
verification-done-focal verification-done-xenial verification-needed
-- 
seccomp_rule_add is very slow
https://bugs.launchpad.net/bugs/1861177
You received this bug notification because you are a member of Ubuntu 
Translations Coordinators, which is subscribed to Ubuntu Translations.

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1877401] Re: The Italian translation is not complete

[Launchpad Bug Tracker]

This bug was fixed in the package evince - 3.36.5-0ubuntu1

---
evince (3.36.5-0ubuntu1) focal; urgency=medium

  * New upstream release (lp: #1879475)
  * debian/patches/git_armhf_build.patch:
- cherry pick an upstream fix 'backend: Fix -Werror=format=2 on
  dvi', fixes the build on armhf
  * debian/rules:
- override the dh_translations call to delete the outdated template
  which is provided by upstream (lp: #1877401)

 -- Sebastien Bacher   Tue, 19 May 2020 16:23:45
+0200

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

-- 
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching subscriptions: Ubuntu Translations bug mail
https://bugs.launchpad.net/bugs/1877401

Title:
  The Italian translation is not complete

Status in Ubuntu Translations:
  Fix Released
Status in evince package in Ubuntu:
  Fix Released
Status in evince source package in Focal:
  Fix Released

Bug description:
  The Italian translation in the version 3.36.0 in Ubuntu 20.04 LTS is
  not complete. Some items in the menu are shown in English, like "Right
  to Left Document" and "Properties".

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

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 691590] [NEW] libvirt restore exactly the old ownership of images

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Natty (and it was also the same on Maverick, IIRC).

When you assign an ISO to a VM, libvirt will take over onwership of the
ISO. This creates problems if the ISO is updated.

For example, I am daily updating the Natty server ISOs, and running
tests on them via KVM (all automated). The ISO updates will fail because
libvirt chowns them.

I see no reason for this: libvirt only needs the ISO as input.

WORKAROUND:
  edit /etc/libvirt/qemu.conf, change 'dynamic_ownership = 0', restart qemu/KVM.

** Affects: libvirt (Ubuntu)
 Importance: Medium
 Assignee: Christian Ehrhardt  (paelzer)
 Status: In Progress

** Affects: ubuntu-translations
 Importance: Medium
 Status: Fix Released


** Tags: iso-testing libvirt-20.10 natty qa
-- 
libvirt restore exactly the old ownership of images
https://bugs.launchpad.net/bugs/691590
You received this bug notification because you are a member of Ubuntu 
Translations Coordinators, which is subscribed to Ubuntu Translations.

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1873272] Re: Error in livepatch is not translated

[Launchpad Bug Tracker]

This bug was fixed in the package software-properties - 0.98.10

---
software-properties (0.98.10) groovy; urgency=medium

  [ Sebastien Bacher ]
  * softwareproperties/gtk/LivepatchPage.py:
- set error string in the init so it happens after the textdomain
  is set, also fix the string used with gettext (lp: #1873272)

  [ Corey Bryant ]
  * cloudarchive: Enable support for the Victoria Ubuntu Cloud Archive on
20.04 (LP: #1882583).

 -- Corey Bryant   Mon, 08 Jun 2020 14:18:42
-0400

** Changed in: software-properties (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching subscriptions: Ubuntu Translations bug mail
https://bugs.launchpad.net/bugs/1873272

Title:
  Error in livepatch is not translated

Status in Ubuntu Translations:
  New
Status in software-properties package in Ubuntu:
  Fix Released

Bug description:
  On focal, the string "Canonical Livepatch has experienced an internal
  error. Please refer to
  https://wiki.ubuntu.com/Kernel/Livepatch#CommonIssues for further
  information." is not translated in french whereas the string is
  translated in https://translations.launchpad.net/ubuntu/focal/+source
  /software-properties/+pots/software-properties/fr/129

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

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1877401] Re: The Italian translation is not complete

[Launchpad Bug Tracker]

This bug was fixed in the package evince - 3.36.1-1

---
evince (3.36.1-1) unstable; urgency=medium

  * New upstream release (lp: #1879475)
  * debian/rules:
- override the dh_translations call to delete the outdated template
  which is provided by upstream (lp: #1877401)

 -- Sebastien Bacher   Tue, 19 May 2020 16:23:45
+0200

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

-- 
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching subscriptions: Ubuntu Translations bug mail
https://bugs.launchpad.net/bugs/1877401

Title:
  The Italian translation is not complete

Status in Ubuntu Translations:
  New
Status in evince package in Ubuntu:
  Fix Released

Bug description:
  The Italian translation in the version 3.36.0 in Ubuntu 20.04 LTS is
  not complete. Some items in the menu are shown in English, like "Right
  to Left Document" and "Properties".

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

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1872667] [NEW] Upgrade gummi package to version 0.8.1

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Dear Maintainer,

I am the upstream developer for gummi. After a long hiatus I have in
recent months resumed development. Unfortunately the gummi package that
was imported from Debian sid for this Ubuntu release is a development
build that suffers from a critical bug.

I hereby request to:

1. Update the package to stable release 0.8.1 (see [2])
2. Remove the package from ubuntu universe/tex

Thanks in advance and with kind regards,

alexandervdm

[1] https://github.com/alexandervdm/gummi/issues/33
[2] https://github.com/alexandervdm/gummi/releases/tag/0.8.1

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gummi 0.7.999-1
ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
Uname: Linux 5.4.0-18-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu26
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: MATE
Date: Tue Apr 14 10:54:35 2020
InstallationDate: Installed on 2020-02-24 (49 days ago)
InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Alpha amd64 (20200211)
SourcePackage: gummi
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu-translations
 Importance: Undecided
 Status: New

** Affects: gummi (Ubuntu)
 Importance: Low
 Status: Fix Committed

** Affects: gummi (Ubuntu Focal)
 Importance: Low
 Status: New


** Tags: amd64 apport-bug focal upgrade-software-version
-- 
Upgrade gummi package to version 0.8.1
https://bugs.launchpad.net/bugs/1872667
You received this bug notification because you are a member of Ubuntu 
Translations Coordinators, which is subscribed to Ubuntu Translations.

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1877402] Re: The Italian translation is not complete

[Launchpad Bug Tracker]

This bug was fixed in the package simple-scan - 3.36.1-1build1

---
simple-scan (3.36.1-1build1) groovy; urgency=medium

  * No-change rebuild for translations (LP: #1877402)

 -- Gunnar Hjalmarsson   Thu, 07 May 2020 23:58:00
+0200

** Changed in: simple-scan (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching subscriptions: Ubuntu Translations bug mail
https://bugs.launchpad.net/bugs/1877402

Title:
  The Italian translation is not complete

Status in Ubuntu Translations:
  New
Status in simple-scan package in Ubuntu:
  Fix Released

Bug description:
  The Italian translation is not complete. Some items in the version
  3.36.0 in Ubuntu 20.04 LTS are shown in English, like "Scan", "Single
  Page", "Text", "Image", "Print" and others.

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

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 488431] Re: Userinformation screen hides some text fields due to long and split texts

[Launchpad Bug Tracker]

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching subscriptions: Ubuntu Translations bug mail
https://bugs.launchpad.net/bugs/488431

Title:
  Userinformation screen hides some text fields due to long and split
  texts

Status in Ubuntu Translations:
  Invalid
Status in ubiquity package in Ubuntu:
  Expired

Bug description:
  Binary package hint: ubiquity

  During a danish installation of Kubuntu Karmic Koala, The user
  information tab does not show all text on all text fields.

  There are several problems on the screenshot attached:
  1) The text on the tabs "Diskopsæt..." should be displayed in full like 
"Diskopsætning", the same holds for "Brugerinfo..." which should display 
"Brugerinformation"

  2) The sentence "Hvis der er flere end en person der skal bruge
  computeren kan du" (en: if there is more than one person that shall
  use the computer, you can) apparantly continues on a second line,
  which is not shown except from the top pixels of some of the letters.

  3) The sentence "Indtast den samme adgangskode to gange så den kan
  blive tjekket for" (en: enter the same password twice, so it can be
  checked for) apparantly continues on a second line, which is not shown
  except from the top pixels of some of the letters.

  4) The second bottom line says "Kræver min adgangskode fo...", which
  is a danish translation from  (I guess) "Require my password to ...",
  bu tthe rest of the sentence is not shown. Which makes the default
  chosen option an unknown choice.

  ProblemType: Bug
  Architecture: amd64
  Date: Wed Nov 25 21:27:21 2009
  DistroRelease: Ubuntu 9.10
  InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
  NonfreeKernelModules: wl fglrx
  Package: ubiquity (not installed)
  ProcEnviron:
   LANGUAGE=
   PATH=(custom, user)
   LANG=da_DK.UTF-8
   SHELL=/usr/bin/tcsh
  ProcVersionSignature: Ubuntu 2.6.31-15.50-generic
  SourcePackage: ubiquity
  Uname: Linux 2.6.31-15-generic x86_64
  XsessionErrors:
   (polkit-gnome-authentication-agent-1:2254): GLib-CRITICAL **: 
g_once_init_leave: assertion `initialization_value != 0' failed
   (npviewer.bin:3563): Gtk-WARNING **: 
/usr/lib/gtk-2.0/2.10.0/engines/libqtcurve.so: wrong ELF class: ELFCLASS64

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

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 892386] Re: No shortcut available for "forward" button for Chinese during installation / oem-config

[Launchpad Bug Tracker]

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching subscriptions: Ubuntu Translations bug mail
https://bugs.launchpad.net/bugs/892386

Title:
  No shortcut available for "forward" button for Chinese during
  installation / oem-config

Status in OEM Priority Project:
  Won't Fix
Status in OEM Priority Project oneiric series:
  Won't Fix
Status in OEM Priority Project precise series:
  Won't Fix
Status in OEM Priority Project quantal series:
  Won't Fix
Status in OEM Priority Project raring series:
  Won't Fix
Status in Ubuntu Translations:
  Invalid
Status in ubiquity package in Ubuntu:
  Expired

Bug description:
  For installations where Simplified Chinese is the default language,
  there is no shortcut available for the Forward Button in either the
  installer or during oem-config.  There are shortcuts for Back (B) and
  Quit (Q).  Chinese users can press Alt+B or Alt+Q to move backward or
  quit the installation, but, there's nothing that will allow them to
  press Alt+F to move forward.   I have attached a photo as an example
  of what the user sees.

  Steps to reproduce:

  1) Install Ubuntu 11.10 and select Simplified Chinese as the language.

  Actual Results:
  During installation (or oem-config) there is no shortcut available for the 
forward button.

  Expected Results:

  In addition to being able to quit, cancel, or go backward, the user
  should also have an (F) on the button and press Alt+F to move forward
  through the installation.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 3.0.0-13.22somerville1-generic 3.0.6
  Uname: Linux 3.0.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  Date: Sat Nov 19 06:31:10 2011
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-oneiric-amd64-2016-1
  InstallationMedia: Ubuntu 11.10 "Oneiric" - Build amd64 LIVE Binary 
2016-18:24
  ProcEnviron:
   LANGUAGE=zh_CN:zh
   PATH=(custom, no user)
   LANG=zh_CN.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1870154] Re: checksum verification messages not translated

[Launchpad Bug Tracker]

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching subscriptions: Ubuntu Translations bug mail
https://bugs.launchpad.net/bugs/1870154

Title:
  checksum verification messages not translated

Status in Ubuntu Translations:
  New
Status in casper package in Ubuntu:
  Confirmed

Bug description:
  The first check disk before focal installation is not translated 
  Please see attachment

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

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1559650] [NEW] gnome-shell crashed with SIGSEGV in ___vsnprintf_chk()

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

[Impact]

gnome-shell crashes a lot. Over 38000 times in bionic so far:
https://errors.ubuntu.com/problem/00455200cd9fb890dacfe09b92c7bda2f6ad3af7

[Test Case]

None known yet. Just keeping an eye on the above link for regressions.

[Regression Potential]

Low. The same fix has been released to newer distros for the past 2
years already.

[Other Info]

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: gnome-shell 3.18.4-0ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5
Uname: Linux 4.4.0-13-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME
Date: Wed Mar 16 17:15:11 2016
DisplayManager: gdm3
ExecutablePath: /usr/bin/gnome-shell
GsettingsChanges:

InstallationDate: Installed on 2016-03-13 (6 days ago)
InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160311)
ProcCmdline: gnome-shell --mode=gdm --wayland --display-server
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/false
SegvAnalysis:
 Segfault happened at: 0x7f1ff33f46ab <___vsnprintf_chk+107>:   movb   
$0x0,(%r12)
 PC (0x7f1ff33f46ab) ok
 source "$0x0" ok
 destination "(%r12)" (0x) not located in a known VMA region (needed 
writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: gnome-shell
StacktraceTop:
 ___vsnprintf_chk (s=0x0, maxlen=, flags=1, slen=, format=0x7f1fe54ccae5 "%s%s", args=args@entry=0x7f1fce502da8) at 
vsnprintf_chk.c:55
 ___snprintf_chk (s=, maxlen=, flags=, slen=, format=) at snprintf_chk.c:34
 XauFileName () from /usr/lib/x86_64-linux-gnu/libXau.so.6
 XauGetBestAuthByAddr () from /usr/lib/x86_64-linux-gnu/libXau.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
Title: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

** Affects: ubuntu-translations
 Importance: Unknown
 Status: Unknown

** Affects: libxau (Ubuntu)
 Importance: Medium
 Status: Fix Released

** Affects: libxau (Ubuntu Bionic)
 Importance: Medium
 Assignee: Daniel van Vugt (vanvugt)
 Status: Fix Committed

** Affects: libxau (Ubuntu Eoan)
 Importance: Medium
 Status: Fix Released

** Affects: libxau (Ubuntu Focal)
 Importance: Medium
 Status: Fix Released


** Tags: amd64 apport-crash bionic xenial
-- 
gnome-shell crashed with SIGSEGV in ___vsnprintf_chk()
https://bugs.launchpad.net/bugs/1559650
You received this bug notification because you are a member of Ubuntu 
Translations Coordinators, which is subscribed to Ubuntu Translations.

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1870156] Re: Ubiquity translations need to be updated

[Launchpad Bug Tracker]

This bug was fixed in the package ubiquity - 20.04.10

---
ubiquity (20.04.10) focal; urgency=medium

  [ Sebastien Bacher ]
  * Updated translations from launchpad. (LP: #1870156)

  [ Jean-Baptiste Lallement ]
  * zsys-setup: Make /boot/grub world-readable.

  [ Iain Lane ]
  * The following two changes are *not* exposed. They are mainly to extract
the strings for translators to work on. A followup upload will expose the
UI when necessary.
  * Add the UI for a "Turn off RST" page.
It's not hooked up yet - this is waiting for another change, but we can
get on with translating it.
  * Add the UI for a "you need to disable Bitlocker" page.
As in the previous commit, this is disabled unless a special environment
variable is set.

 -- Iain Lane   Wed, 08 Apr 2020 17:44:59 +0100

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

-- 
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching subscriptions: Ubuntu Translations bug mail
https://bugs.launchpad.net/bugs/1870156

Title:
  Ubiquity translations need to be updated

Status in Ubuntu Translations:
  New
Status in ubiquity package in Ubuntu:
  Fix Released
Status in ubiquity source package in Focal:
  Fix Released

Bug description:
  please see attachment

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

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1871087] Re: po/bootloader.pot outdated

[Launchpad Bug Tracker]

This bug was fixed in the package gfxboot-theme-ubuntu - 0.23.1

---
gfxboot-theme-ubuntu (0.23.1) focal; urgency=medium

  * po/bootloader.pot:
- updated to add the safe graphics strings (lp: #1871087)

 -- Sebastien Bacher   Tue, 07 Apr 2020 10:29:10
+0200

** Changed in: gfxboot-theme-ubuntu (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching subscriptions: Ubuntu Translations bug mail
https://bugs.launchpad.net/bugs/1871087

Title:
  po/bootloader.pot outdated

Status in Ubuntu Translations:
  New
Status in gfxboot-theme-ubuntu package in Ubuntu:
  Fix Released

Bug description:
  The current POT was created 2016-04-16. As reported in
  ,
  strings newer than that are not translatable in LP.

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

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1870152] Re: 'System Sounds' string showing not translated

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-control-center -
1:3.36.1-1ubuntu3

---
gnome-control-center (1:3.36.1-1ubuntu3) focal; urgency=medium

  * debian/patches/0001-sound-Fix-translation-of-System-Sounds.patch:
- Fix system sounds not being translated (LP: #1870152)

 -- Robert Ancell   Thu, 02 Apr 2020
13:47:54 +1300

** Changed in: gnome-control-center (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching subscriptions: Ubuntu Translations bug mail
https://bugs.launchpad.net/bugs/1870152

Title:
  'System Sounds' string showing not translated

Status in gnome-control-center:
  Unknown
Status in Ubuntu Translations:
  New
Status in gnome-control-center package in Ubuntu:
  Fix Released

Bug description:
  Please check attachment

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1870152/+subscriptions

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1824724] Re: aa-logprof: german translation: ERROR: PromptUser: Ungültiges Tastenkürzel für V: Änderungen ansehen

[Launchpad Bug Tracker]

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

** Changed in: language-pack-de (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching subscriptions: Ubuntu Translations bug mail
https://bugs.launchpad.net/bugs/1824724

Title:
  aa-logprof: german translation: ERROR: PromptUser: Ungültiges
  Tastenkürzel für V: Änderungen ansehen

Status in AppArmor:
  New
Status in Ubuntu Translations:
  New
Status in language-pack-de package in Ubuntu:
  Confirmed
Status in language-pack-de-base package in Ubuntu:
  Confirmed

Bug description:
  after the last Erl(a)uben [Allow] theres an errormessage:
  "ERROR: PromptUser: Ungültiges Tastenkürzel für V: Änderungen ansehen"
  see here:

  Profil:  /usr/bin/snap
  Pfad:/sys/kernel/security/apparmor/features/policy/versions/v5
  Neuer Modus: r
  Schweregrad: 4

   [1 - /sys/kernel/security/apparmor/features/policy/versions/v5 r,]
  Erl(a)uben / [A(b)lehnen] / (I)gnorieren / (G)lob / Glob with (E)xtension / 
(N)eu / Audi(t) / Abb(r)echen / En(d)e
  /sys/kernel/security/apparmor/features/policy/versions/v5 r, wird zum Profil 
hinzugefügt.

  ERROR: PromptUser: Ungültiges Tastenkürzel für V: Änderungen ansehen
  [view changes]

  imho it's a translation error.

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

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1824724] Re: aa-logprof: german translation: ERROR: PromptUser: Ungültiges Tastenkürzel für V: Änderungen ansehen

[Launchpad Bug Tracker]

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

** Changed in: language-pack-de-base (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching subscriptions: Ubuntu Translations bug mail
https://bugs.launchpad.net/bugs/1824724

Title:
  aa-logprof: german translation: ERROR: PromptUser: Ungültiges
  Tastenkürzel für V: Änderungen ansehen

Status in AppArmor:
  New
Status in Ubuntu Translations:
  New
Status in language-pack-de package in Ubuntu:
  Confirmed
Status in language-pack-de-base package in Ubuntu:
  Confirmed

Bug description:
  after the last Erl(a)uben [Allow] theres an errormessage:
  "ERROR: PromptUser: Ungültiges Tastenkürzel für V: Änderungen ansehen"
  see here:

  Profil:  /usr/bin/snap
  Pfad:/sys/kernel/security/apparmor/features/policy/versions/v5
  Neuer Modus: r
  Schweregrad: 4

   [1 - /sys/kernel/security/apparmor/features/policy/versions/v5 r,]
  Erl(a)uben / [A(b)lehnen] / (I)gnorieren / (G)lob / Glob with (E)xtension / 
(N)eu / Audi(t) / Abb(r)echen / En(d)e
  /sys/kernel/security/apparmor/features/policy/versions/v5 r, wird zum Profil 
hinzugefügt.

  ERROR: PromptUser: Ungültiges Tastenkürzel für V: Änderungen ansehen
  [view changes]

  imho it's a translation error.

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

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 736005] Re: POFile:+translate timeouts

[Launchpad Bug Tracker]

** Merge proposal linked:
   https://code.launchpad.net/~cjwatson/launchpad/+git/launchpad/+merge/381540

-- 
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching subscriptions: Ubuntu Translations bug mail
https://bugs.launchpad.net/bugs/736005

Title:
  POFile:+translate timeouts

Status in JOSM:
  Unknown
Status in Launchpad itself:
  Triaged
Status in Odoo Addons (MOVED TO GITHUB):
  New
Status in Ubuntu Translations:
  Triaged

Bug description:
  
1 SELECT TranslationMessage.comment, TranslationMessage.date_created, 
TranslationMessage.date_revie ... gstr3, -$INT), COALESCE(msgstr4, -$INT), 
COALESCE(msgstr5, -$INT), date_created DESC ) LIMIT $INT:
 GET: 1 Robots: 0  Local: 1
1 
https://translations.launchpad.net/picapy/trunk/+pots/picapy/de/+translate 
(POFile:+translate)
 OOPS-1900K842

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

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 736005] Re: POFile:+translate timeouts

[Launchpad Bug Tracker]

** Merge proposal linked:
   https://code.launchpad.net/~cjwatson/launchpad/+git/launchpad/+merge/381533

-- 
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching subscriptions: Ubuntu Translations bug mail
https://bugs.launchpad.net/bugs/736005

Title:
  POFile:+translate timeouts

Status in JOSM:
  Unknown
Status in Launchpad itself:
  Triaged
Status in Odoo Addons (MOVED TO GITHUB):
  New
Status in Ubuntu Translations:
  Triaged

Bug description:
  
1 SELECT TranslationMessage.comment, TranslationMessage.date_created, 
TranslationMessage.date_revie ... gstr3, -$INT), COALESCE(msgstr4, -$INT), 
COALESCE(msgstr5, -$INT), date_created DESC ) LIMIT $INT:
 GET: 1 Robots: 0  Local: 1
1 
https://translations.launchpad.net/picapy/trunk/+pots/picapy/de/+translate 
(POFile:+translate)
 OOPS-1900K842

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

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1870150] [NEW] not translated

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Please see attachment

** Affects: ubuntu-translations
 Importance: Undecided
 Status: New

-- 
not translated
https://bugs.launchpad.net/bugs/1870150
You received this bug notification because you are a member of Ubuntu 
Translations Coordinators, which is subscribed to Ubuntu Translations.

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1859960] Re: Livepatch polkit rules strings are not translatable

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-initial-setup - 3.36.0-1ubuntu3

---
gnome-initial-setup (3.36.0-1ubuntu3) focal; urgency=medium

  * Refresh the control...

 -- Sebastien Bacher   Tue, 17 Mar 2020 16:28:27
+0100

** Changed in: gnome-initial-setup (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching subscriptions: Ubuntu Translations bug mail
https://bugs.launchpad.net/bugs/1859960

Title:
  Livepatch polkit rules strings are not translatable

Status in Ubuntu Translations:
  New
Status in gnome-initial-setup package in Ubuntu:
  Fix Released

Bug description:
  The "Manage Livepatch" and "Authentication is required to enable
  Livepatch" translatable strings from
  /usr/share/polkit-1/actions/com.ubuntu.welcome.policy do not seem to
  be available to translate on Launchpad. They were translatable and
  their translation was correctly applied in Bionic, however since then
  (Cosmic, Disco, Eoan, Focal), they are untranslated and not available
  on Launchpad.

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

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1859960] Re: Livepatch polkit rules strings are not translatable

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-initial-setup - 3.36.0-1ubuntu1

---
gnome-initial-setup (3.36.0-1ubuntu1) focal; urgency=medium

  * Merge with Debian. Remaining changes:
+ debian/control.in:
  - Build-Depends on libsnapd-glib-dev, libsoup2.4-dev, libsysmetrics-dev
+ Add Ubuntu-specific patches:
  - 0001-Don-t-run-welcome-tour-at-end.patch
  - 0001-Make-summary-page-explicitly-request-navigation-butt.patch
  - 0001-Ensure-stamp-file-if-the-user-quit-the-wizard.patch
  - 0001-Add-Ubuntu-mode-with-special-pages.patch
  - 0001-Display-the-ubuntu-welcome-wizard-in-Unity.patch
  - 0006-goa-Add-Ubuntu-Single-Sign-On-to-the-list.patch
  - 0007-goa-adjust-description-to-not-mention-email-or-conta.patch
  - Don-t-show-Facebook-in-Ubuntu.patch
  - 0008-Ubuntu-location-default.patch
  * debian/patches/0001-Add-Ubuntu-mode-with-special-pages.patch:
- don't add non existant sources to the translation template,
  should fix the translations import (lp: #1859960)

 -- Sebastien Bacher   Thu, 12 Mar 2020 20:37:23
+0100

** Changed in: gnome-initial-setup (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching subscriptions: Ubuntu Translations bug mail
https://bugs.launchpad.net/bugs/1859960

Title:
  Livepatch polkit rules strings are not translatable

Status in Ubuntu Translations:
  New
Status in gnome-initial-setup package in Ubuntu:
  Fix Released

Bug description:
  The "Manage Livepatch" and "Authentication is required to enable
  Livepatch" translatable strings from
  /usr/share/polkit-1/actions/com.ubuntu.welcome.policy do not seem to
  be available to translate on Launchpad. They were translatable and
  their translation was correctly applied in Bionic, however since then
  (Cosmic, Disco, Eoan, Focal), they are untranslated and not available
  on Launchpad.

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

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1171844] Re: Ubiquity: Tajik Language Support

[Launchpad Bug Tracker]

This bug was fixed in the package gfxboot-theme-ubuntu - 0.22.0

---
gfxboot-theme-ubuntu (0.22.0) focal; urgency=medium

  * langnames.inc: add Tajik to the list of languages to be included in the
isolinux language selector.  Closes: #1171844.

 -- Steve Langasek   Sun, 08 Mar 2020
00:03:19 -0800

** Changed in: gfxboot-theme-ubuntu (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching subscriptions: Ubuntu Translations bug mail
https://bugs.launchpad.net/bugs/1171844

Title:
  Ubiquity: Tajik Language Support

Status in Ubuntu Translations:
  Fix Released
Status in debian-installer package in Ubuntu:
  New
Status in gfxboot-theme-ubuntu package in Ubuntu:
  Fix Released
Status in localechooser package in Ubuntu:
  Fix Released

Bug description:
  Hi,

  Currently we keep working on Tajik (tgk/tg) translations for Ubuntu
  and have good statistics for translated files. To test our recent
  translations and improve any found errors we have downloaded Ubuntu
  13.04 (Raring Ringtail) Daily Build on April 17, 2013 at
  http://cdimage.ubuntu.com/daily-live/current/ and Tajik language in
  not listed for the Installation process.

  Could you please, create an Ubuntu language pack for Tajik and list
  Tajik Language for the installation option.

  Thank you,
  Victor Ibragimov
  ---
  Tajik Ubuntu Localization Team

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

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1860037] [NEW] Typo in the Russian interface of the package

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

The Russian interface of the gnome-control-center package contains a typo. A 
typo is highlighted in the attached screenshot. Instead of "входе с систему" 
you must specify "входе в систему".
Ubuntu version is 18.04.3 LTS
gnome-control-center version is 1:3.28.2-0ubuntu0.18.04.5

** Affects: ubuntu-translations
 Importance: Medium
 Assignee: Russian Ubuntu Translators (ubuntu-l10n-ru)
 Status: Triaged


** Tags: typo
-- 
Typo in the Russian interface of the package
https://bugs.launchpad.net/bugs/1860037
You received this bug notification because you are a member of Ubuntu 
Translations Coordinators, which is subscribed to Ubuntu Translations.

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1856850] [NEW] Ukrainian translation problem for file copy dialog

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Ukrainian message translation issue. Current ukrainian to english
translation is "The file is too large."

Ukrainian https://i.imgur.com/BHuZgAm.png
English https://i.imgur.com/mKY5Y4r.png

Kernel: 4.15.0-72-generic x86_64 bits: 64 Desktop: Xfce 4.12.3 Distro:
Ubuntu 18.04.3 LTS

** Affects: ubuntu-translations
 Importance: Undecided
 Status: New

-- 
Ukrainian translation problem for file copy dialog
https://bugs.launchpad.net/bugs/1856850
You received this bug notification because you are a member of Ubuntu 
Translations Coordinators, which is subscribed to Ubuntu Translations.

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1852818] Re: Wrong Turkish translation in the firefox.desktop file

[Launchpad Bug Tracker]

This bug was fixed in the package firefox - 71.0+build2-0ubuntu2

---
firefox (71.0+build2-0ubuntu2) focal; urgency=medium

  * Increase the autopkgtests timeout to 10 minutes
- debian/tests/control
  * Update test expectation
- debian/tests/html5test

 -- Olivier Tilloy   Wed, 27 Nov 2019
15:50:37 +0100

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

-- 
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching subscriptions: Ubuntu Translations bug mail
https://bugs.launchpad.net/bugs/1852818

Title:
  Wrong Turkish translation in the firefox.desktop file

Status in Ubuntu Translations:
  New
Status in firefox package in Ubuntu:
  Fix Released

Bug description:
  Hi,

  Firstly, I opened this bug report on Mozilla Firefox's Bugzilla page
  (https://bugzilla.mozilla.org/show_bug.cgi?id=1595524)

  It turned out that bug didn't completely belong to them.

  This bug is just a simple wrong translation.

  This string, "Yeni bir pencere aç" needs to be translated as "Yeni
  gizli pencere aç". (In firefox.desktop file, at line 219)

  Secondly, there is another firefox.desktop file in /taskcluster/docker
  /firefox-snap/ folder, in firefox source code and both firefox.desktop
  files have the same translation error.

  I think my translation enough to fix this little translation error.
  Also, you might ask Selim Sumlu
  (https://bugzilla.mozilla.org/user_profile?user_id=380385) to decide
  which translation might be better for it.

  I hope, both teams can fix the bug soon.

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

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1852818] Re: Wrong Turkish translation in the firefox.desktop file

[Launchpad Bug Tracker]

** Branch linked: lp:~mozillateam/firefox/firefox.xenial

** Branch linked: lp:~mozillateam/firefox/firefox.bionic

** Branch linked: lp:~mozillateam/firefox/firefox.disco

** Branch linked: lp:~mozillateam/firefox/firefox.eoan

** Branch linked: lp:firefox

-- 
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching subscriptions: Ubuntu Translations bug mail
https://bugs.launchpad.net/bugs/1852818

Title:
  Wrong Turkish translation in the firefox.desktop file

Status in Ubuntu Translations:
  New
Status in firefox package in Ubuntu:
  Fix Committed

Bug description:
  Hi,

  Firstly, I opened this bug report on Mozilla Firefox's Bugzilla page
  (https://bugzilla.mozilla.org/show_bug.cgi?id=1595524)

  It turned out that bug didn't completely belong to them.

  This bug is just a simple wrong translation.

  This string, "Yeni bir pencere aç" needs to be translated as "Yeni
  gizli pencere aç". (In firefox.desktop file, at line 219)

  Secondly, there is another firefox.desktop file in /taskcluster/docker
  /firefox-snap/ folder, in firefox source code and both firefox.desktop
  files have the same translation error.

  I think my translation enough to fix this little translation error.
  Also, you might ask Selim Sumlu
  (https://bugzilla.mozilla.org/user_profile?user_id=380385) to decide
  which translation might be better for it.

  I hope, both teams can fix the bug soon.

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

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1851028] [NEW] Livepatch tip is not translated in update-manager

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Ubuntu 20.04 development branch with kernel 5.3.0-18-generic up to date
to latest @ 2/11/2019

After update-manager GUI has finished its updates
the finish window has not translated the livepatch tip and the settings & 
livepatch button
in the systems language, dutch in my case, i did not test other languages
(see screenshot)

The title however has been translated correctly (The software on this
computer has been updated)

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: update-manager 1:19.04.8
ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
Uname: Linux 5.3.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu9
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Nov  2 12:52:27 2019
InstallationDate: Installed on 2019-10-25 (8 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191021)
PackageArchitecture: all
SourcePackage: update-manager
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu-translations
 Importance: Medium
 Assignee: Ubuntu Dutch Translators (ubuntu-l10n-nl)
 Status: In Progress


** Tags: amd64 apport-bug focal
-- 
Livepatch tip is not translated in update-manager
https://bugs.launchpad.net/bugs/1851028
You received this bug notification because you are a member of Ubuntu 
Translations Coordinators, which is subscribed to Ubuntu Translations.

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1779574] Re: Missing static translations in .desktop files

[Launchpad Bug Tracker]

This bug was fixed in the package geary - 0.12.4-4~ubuntu18.04.3

---
geary (0.12.4-4~ubuntu18.04.3) bionic; urgency=medium

  [ Amr Ibrahim ]
  * Backport to bionic (LP: #1815626)

  [ Gunnar Hjalmarsson ]
  * Handle translations for bionic (LP: #1779574):
- debian/control.in, debian/control:
  - Don't enable language packs.
- debian/rules:
  - Prevent dh_translations from removing upstream translations
from the .desktop files.

 -- David Mohammed   Wed, 02 Oct 2019 22:49:05
+0100

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

-- 
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching subscriptions: Ubuntu Translations bug mail
https://bugs.launchpad.net/bugs/1779574

Title:
  Missing static translations in .desktop files

Status in Ubuntu Translations:
  Triaged
Status in geary package in Ubuntu:
  Fix Released
Status in geary source package in Bionic:
  Fix Released

Bug description:
  Rationale
  X-Ubuntu-Gettext-Domain should be added to .desktop files but static 
translations should be preferred.
  [1]

  Current state
  X-Ubuntu-Gettext-Domain is present in Geary .desktop files but static 
translations not.

  Expected state
  Both X-Ubuntu-Gettext-Domain and static translations are present in the 
.desktop files.

  More info:
  https://gitlab.gnome.org/GNOME/geary/issues/16

  Source:
  [1] 
https://wiki.ubuntu.com/UbuntuDevelopment/Internationalisation/Packaging#Other_translation_files

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: geary 0.12.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Jul  1 20:37:26 2018
  SourcePackage: geary
  UpgradeStatus: No upgrade log present (probably fresh install)

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

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1851221] [NEW] localized language (Icelandic) incomplete

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Localized language (Icelandic) incomplete - the system not fully localized. 
This occurred testing Kubuntu Focal Desktop daily build 20191104.

Many pages/texts are mixed with both English and Icelandic

The calendar settings show the regional settings correctly.

** Affects: ubuntu-translations
 Importance: Low
 Assignee: Íslenska UBUNTU þýðingarteymið - Icelandic Translators 
(ubuntu-l10n-is)
 Status: Confirmed


** Tags: iso-testing
-- 
localized language (Icelandic) incomplete
https://bugs.launchpad.net/bugs/1851221
You received this bug notification because you are a member of Ubuntu 
Translations Coordinators, which is subscribed to Ubuntu Translations.

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1834565] [NEW] python 3.7: wrap_socket() got an unexpected keyword argument '_context'

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

[Impact]
Unable to enable TLS termination of any endpoints for OpenStack with Python 3.7.

[Test Case]
sudo apt install python3-eventlet
python3 << EOF
import eventlet
eventlet.monkey_patch()

import socket
import ssl

sock = socket.socket(socket.AF_INET, socket.SOCK_STREAM)
wrappedSocket = ssl.wrap_socket(sock)
EOF

Traceback (most recent call last):
  File "", line 8, in 
  File "/usr/lib/python3/dist-packages/eventlet/green/ssl.py", line 403, in 
wrap_socket
return GreenSSLSocket(sock, *a, **kw)
  File "/usr/lib/python3/dist-packages/eventlet/green/ssl.py", line 80, in 
__init__
*args, **kw
  File "/usr/lib/python3.7/ssl.py", line 1222, in wrap_socket
suppress_ragged_eofs=suppress_ragged_eofs
  File "/usr/lib/python3/dist-packages/eventlet/green/ssl.py", line 426, in 
wrap_socket
return GreenSSLSocket(sock, *a, _context=self, **kw)
  File "/usr/lib/python3/dist-packages/eventlet/green/ssl.py", line 80, in 
__init__
*args, **kw
TypeError: wrap_socket() got an unexpected keyword argument '_context'

[Regression Potential]
Low; codepaths are all Python 3.7 specific due to internal changes in the SSL 
implementation.

[Original bug report]
In an SSL enabled OpenStack Stein deploy, deployed on Disco, the 
cinder-scheduler service is crashing with the below stacktrace:

2019-06-27 18:35:07.593 5427 WARNING cinder.scheduler.host_manager 
[req-9c5d17cd-1414-482a-bfc9-a6bef2369637 - - - - -] volume service is down. 
(host: juju-20eff5-mojo-0-7@LVM)
2019-06-27 18:35:07.594 5427 WARNING cinder.scheduler.host_manager 
[req-9c5d17cd-1414-482a-bfc9-a6bef2369637 - - - - -] volume service is down. 
(host: cinder@cinder-ceph)
2019-06-27 18:35:07.610 5427 INFO cinder.rpc 
[req-9c5d17cd-1414-482a-bfc9-a6bef2369637 - - - - -] Automatically selected 
cinder-volume objects version 1.37 as minimum service version.
2019-06-27 18:35:07.619 5427 INFO cinder.rpc 
[req-9c5d17cd-1414-482a-bfc9-a6bef2369637 - - - - -] Automatically selected 
cinder-volume RPC version 3.16 as minimum service version.
2019-06-27 18:35:07.638 5427 INFO cinder.rpc 
[req-9c5d17cd-1414-482a-bfc9-a6bef2369637 - - - - -] Automatically selected 
cinder-scheduler objects version 1.37 as minimum service version.
2019-06-27 18:35:07.647 5427 INFO cinder.rpc 
[req-9c5d17cd-1414-482a-bfc9-a6bef2369637 - - - - -] Automatically selected 
cinder-scheduler RPC version 3.11 as minimum service version.
2019-06-27 18:35:07.702 5427 WARNING oslo_config.cfg 
[req-9c5d17cd-1414-482a-bfc9-a6bef2369637 - - - - -] Deprecated: Option 
"auth_uri" from group "keystone_authtoken" is deprecated for removal (The 
auth_uri option is deprecated in favor of www_authenticate_uri and will be 
removed in the S  release.).  Its value may be silently ignored in the future.
2019-06-27 18:35:07.703 5427 WARNING oslo_config.cfg 
[req-9c5d17cd-1414-482a-bfc9-a6bef2369637 - - - - -] Deprecated: Option 
"signing_dir" from group "keystone_authtoken" is deprecated for removal (PKI 
token format is no longer supported.).  Its value may be silently ignored in 
the future.
2019-06-27 18:35:07.705 5427 WARNING oslo_config.cfg 
[req-9c5d17cd-1414-482a-bfc9-a6bef2369637 - - - - -] Deprecated: Option 
"auth_uri" from group "keystone_authtoken" is deprecated. Use option 
"www_authenticate_uri" from group "keystone_authtoken".
2019-06-27 18:35:07.726 5427 INFO cinder.service [-] Starting cinder-scheduler 
node (version 14.0.0)
2019-06-27 18:35:07.736 5427 INFO cinder.manager 
[req-e208c3e5-83e5-4c5b-85a3-1f5e09c86da9 - - - - -] Initiating service 4 
cleanup
2019-06-27 18:35:07.745 5427 INFO cinder.manager 
[req-e208c3e5-83e5-4c5b-85a3-1f5e09c86da9 - - - - -] Service 4 cleanup 
completed.
2019-06-27 18:35:07.776 5427 ERROR oslo_service.service 
[req-e208c3e5-83e5-4c5b-85a3-1f5e09c86da9 - - - - -] Error starting thread.: 
TypeError: wrap_socket() got an unexpected keyword argument '_context'
2019-06-27 18:35:07.776 5427 ERROR oslo_service.service Traceback (most recent 
call last):
2019-06-27 18:35:07.776 5427 ERROR oslo_service.service   File 
"/usr/lib/python3/dist-packages/oslo_service/service.py", line 796, in 
run_service
2019-06-27 18:35:07.776 5427 ERROR oslo_service.service service.start()
2019-06-27 18:35:07.776 5427 ERROR oslo_service.service   File 
"/usr/lib/python3/dist-packages/cinder/service.py", line 236, in start
2019-06-27 18:35:07.776 5427 ERROR oslo_service.service 
self.rpcserver.start()
2019-06-27 18:35:07.776 5427 ERROR oslo_service.service   File 
"/usr/lib/python3/dist-packages/oslo_messaging/server.py", line 270, in wrapper
2019-06-27 18:35:07.776 5427 ERROR oslo_service.service log_after, 
timeout_timer)
2019-06-27 18:35:07.776 5427 ERROR oslo_service.service   File 
"/usr/lib/python3/dist-packages/oslo_messaging/server.py", line 190, in run_once
2019-06-27 18:35:07.776 5427 ERROR oslo_service.service post_fn = fn()
2019-06-27 18:35:07.776 5427 ERROR oslo_service.service   File 
"/usr/lib/python3/dist-pa

[Ubuntu-translations-coordinators] [Bug 1833618] [NEW] MAAS can't deploy Ubuntu if ID_SERIAL of any block device is broken (USB pendrive in this case).

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

[Impact]

 * sg3-utils-udev package introduces 55-scsi-sg3_id.rules udev rule that
take places BEFORE rules either finding correct ID_SERIAL for the USB
block device, or calculating it from "usb_id" parameter:

- this rule changes USB ID_SERIAL parameter for the ones given by
the Vital Product Data from the block device.

- USB memory sticks might not provide VPD pages (0x80, 0x83) and,
because of that, the USB ID_SERIAL will be broken.

- because the failure in sg_inq command from the 55-XXX udev rules
file, to obtain the VPDs, the udev ACTION(add) takes long time and
consumers might not have considered a "settle" need.

 * Anything depending on ID_SERIAL udev attribute from USB block devices
might not find appropriate device.

 * Any type of udev consumer not calculating the need for a big time-consuming 
"udevadm settle" right after a pen drive is inserted
might not be able to see all USB block devices attributes from udev.

[Test Case]

 * Install package "sg3-utils-udev", monitor journalctl -f while
introducing a memory stick in your machine and watch sg_inq command
failing:

systemd-udevd[1021]: Process '/usr/bin/sg_inq --export
--inhex=/sys/block/sdb/device/vpd_pg83 --raw' failed with exit code 15.

 * Compare udevadm attributes with and without "sg3-utils-udev" package
is installed:

Without sg3-utils 55-scsi-sg3_id.rules:

$ udevadm info --query=all --name=/dev/sdb | grep -i serial
E: ID_SERIAL=Corsair_Voyager_Mini_3.0_070851D0E490C776-0:0
E: ID_SERIAL_SHORT=070851D0E490C776

With 55-scsi-sg3_id.rules:

$ udevadm info --query=all --name=/dev/sdb | grep -i serial
E: ID_SERIAL=3
E: ID_SERIAL_SHORT=2000acde48234567

[Regression Potential]

 * Minor: either I brake functionality for sg3-utils packages on USB
block devices. Since sg3-utils is used mostly for SCSI debugging,
management and investigations, its a very minor risk.

 * The change is a 1 line change in a udev rule file, very easy to test
following the test case.

[Other Info]


ORIGINAL DESCRIPTION:
 
* MAAS version: 2.4.2 (7034-g2f5deb8b8-0ubuntu1)

MAAS UI changes:

```
Node changed status - From 'Deploying' to 'Failed deployment'
Node installation failure - 'curtin' curtin command install
```

when console_log shows:

```

[  244.588201] cloud-init[3139]:   File 
"/curtin/curtin/commands/block_meta.py", line 1515, in get_path_if_present
[  244.588389] cloud-init[3139]: return 
get_path_to_storage_volume(disk, config)
[  244.588588] cloud-init[3139]:   File 
"/curtin/curtin/commands/block_meta.py", line 433, in get_path_to_storage_volume
[  244.588774] cloud-init[3139]: specified to identify disk")
[  244.588963] cloud-init[3139]: ValueError: serial, wwn or path to 
block dev must be specified to identify disk
[  244.589153] cloud-init[3139]: serial, wwn or path to block dev must 
be specified to identify disk
[  244.589338] cloud-init[3139]:
[  244.589523] cloud-init[3139]: Stderr: ''
[  244.589708] cloud-init[3139]: Unexpected error while running command.
[  244.589905] cloud-init[3139]: Command: ['curtin', 'block-meta', 'custom']
[  244.590088] cloud-init[3139]: Exit code: 3
[  244.590271] cloud-init[3139]: Reason: -
[  244.590459] cloud-init[3139]: Stdout: start: 
cmd-install/stage-partitioning/builtin/cmd-block-meta: curtin command block-meta
```

Reproducible: yes

aarch64, arm64 machine:
Manufacturer: CN8890-2000BG2601-CP-Y-G
Part Number: CN88xx

Cavium SOC
=
Cavium THUNDERX Boot Stub
=
BDK Version: 04.02.14, 2.38 Branch: gigabyte-2.38, Built: Fri Aug 18 01:16:58 
UTC 2017

Board Model:gbt-mt30
Board name: MT30-GS1-00
System name:R120-T33-00
Board Revision: 1.x
Board SKU:  04 SATA
SKU version:1.1

Node:  0 (Fixed)
Chip:  0xa1 Pass 2.1
SKU:   CN8890-2000BG2601-CP-Y-G

*MAAS get-curtin-config: https://paste.ubuntu.com/p/k54HHN55ZF/

** Affects: ubuntu-translations
 Importance: Undecided
 Status: Invalid

** Affects: sg3-utils (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: sg3-utils (Ubuntu Bionic)
 Importance: High
 Assignee: Rafael David Tinoco (rafaeldtinoco)
 Status: In Progress

** Affects: sg3-utils (Ubuntu Disco)
 Importance: High
 Assignee: Rafael David Tinoco (rafaeldtinoco)
 Status: Fix Committed

** Affects: sg3-utils (Ubuntu Eoan)
 Importance: Undecided
 Status: Fix Released

** Affects: sg3-utils (Ubuntu Focal)
 Importance: Undecided
 Status: Fix Released


** Tags: verification-needed verification-needed-disco
-- 
MAAS can't deploy Ubuntu if ID_SERIAL of any block device is broken (USB 
pendrive in this case).
https://bugs.launchpad.net/bugs/1833618
You received this bug notification because you are a member of Ubuntu 
Translations Coordinators, which is subscribed to Ubuntu Translations.

___

[Ubuntu-translations-coordinators] [Bug 1833618] [NEW] MAAS can't deploy Ubuntu if ID_SERIAL of any block device is broken (USB pendrive in this case).

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

[Impact]

 * sg3-utils-udev package introduces 55-scsi-sg3_id.rules udev rule that
take places BEFORE rules either finding correct ID_SERIAL for the USB
block device, or calculating it from "usb_id" parameter:

- this rule changes USB ID_SERIAL parameter for the ones given by
the Vital Product Data from the block device.

- USB memory sticks might not provide VPD pages (0x80, 0x83) and,
because of that, the USB ID_SERIAL will be broken.

- because the failure in sg_inq command from the 55-XXX udev rules
file, to obtain the VPDs, the udev ACTION(add) takes long time and
consumers might not have considered a "settle" need.

 * Anything depending on ID_SERIAL udev attribute from USB block devices
might not find appropriate device.

 * Any type of udev consumer not calculating the need for a big time-consuming 
"udevadm settle" right after a pen drive is inserted
might not be able to see all USB block devices attributes from udev.

[Test Case]

 * Install package "sg3-utils-udev", monitor journalctl -f while
introducing a memory stick in your machine and watch sg_inq command
failing:

systemd-udevd[1021]: Process '/usr/bin/sg_inq --export
--inhex=/sys/block/sdb/device/vpd_pg83 --raw' failed with exit code 15.

 * Compare udevadm attributes with and without "sg3-utils-udev" package
is installed:

Without sg3-utils 55-scsi-sg3_id.rules:

$ udevadm info --query=all --name=/dev/sdb | grep -i serial
E: ID_SERIAL=Corsair_Voyager_Mini_3.0_070851D0E490C776-0:0
E: ID_SERIAL_SHORT=070851D0E490C776

With 55-scsi-sg3_id.rules:

$ udevadm info --query=all --name=/dev/sdb | grep -i serial
E: ID_SERIAL=3
E: ID_SERIAL_SHORT=2000acde48234567

[Regression Potential]

 * Minor: either I brake functionality for sg3-utils packages on USB
block devices. Since sg3-utils is used mostly for SCSI debugging,
management and investigations, its a very minor risk.

 * The change is a 1 line change in a udev rule file, very easy to test
following the test case.

[Other Info]


ORIGINAL DESCRIPTION:
 
* MAAS version: 2.4.2 (7034-g2f5deb8b8-0ubuntu1)

MAAS UI changes:

```
Node changed status - From 'Deploying' to 'Failed deployment'
Node installation failure - 'curtin' curtin command install
```

when console_log shows:

```

[  244.588201] cloud-init[3139]:   File 
"/curtin/curtin/commands/block_meta.py", line 1515, in get_path_if_present
[  244.588389] cloud-init[3139]: return 
get_path_to_storage_volume(disk, config)
[  244.588588] cloud-init[3139]:   File 
"/curtin/curtin/commands/block_meta.py", line 433, in get_path_to_storage_volume
[  244.588774] cloud-init[3139]: specified to identify disk")
[  244.588963] cloud-init[3139]: ValueError: serial, wwn or path to 
block dev must be specified to identify disk
[  244.589153] cloud-init[3139]: serial, wwn or path to block dev must 
be specified to identify disk
[  244.589338] cloud-init[3139]:
[  244.589523] cloud-init[3139]: Stderr: ''
[  244.589708] cloud-init[3139]: Unexpected error while running command.
[  244.589905] cloud-init[3139]: Command: ['curtin', 'block-meta', 'custom']
[  244.590088] cloud-init[3139]: Exit code: 3
[  244.590271] cloud-init[3139]: Reason: -
[  244.590459] cloud-init[3139]: Stdout: start: 
cmd-install/stage-partitioning/builtin/cmd-block-meta: curtin command block-meta
```

Reproducible: yes

aarch64, arm64 machine:
Manufacturer: CN8890-2000BG2601-CP-Y-G
Part Number: CN88xx

Cavium SOC
=
Cavium THUNDERX Boot Stub
=
BDK Version: 04.02.14, 2.38 Branch: gigabyte-2.38, Built: Fri Aug 18 01:16:58 
UTC 2017

Board Model:gbt-mt30
Board name: MT30-GS1-00
System name:R120-T33-00
Board Revision: 1.x
Board SKU:  04 SATA
SKU version:1.1

Node:  0 (Fixed)
Chip:  0xa1 Pass 2.1
SKU:   CN8890-2000BG2601-CP-Y-G

*MAAS get-curtin-config: https://paste.ubuntu.com/p/k54HHN55ZF/

** Affects: ubuntu-translations
 Importance: Undecided
 Status: Invalid

** Affects: maas
 Importance: Undecided
 Status: Invalid

** Affects: sg3-utils (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: sg3-utils (Ubuntu Bionic)
 Importance: High
 Assignee: Rafael David Tinoco (rafaeldtinoco)
 Status: In Progress

** Affects: sg3-utils (Ubuntu Disco)
 Importance: High
 Assignee: Rafael David Tinoco (rafaeldtinoco)
 Status: Fix Committed

** Affects: sg3-utils (Ubuntu Eoan)
 Importance: Undecided
 Status: Fix Released

** Affects: sg3-utils (Ubuntu Focal)
 Importance: Undecided
 Status: Fix Released


** Tags: verification-needed verification-needed-disco
-- 
MAAS can't deploy Ubuntu if ID_SERIAL of any block device is broken (USB 
pendrive in this case).
https://bugs.launchpad.net/bugs/1833618
You received this bug notification because you are a member of Ubuntu 
Translations Coordinators, wh

[Ubuntu-translations-coordinators] [Bug 1751252] [NEW] [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

* Impact
The Ubuntu installer crashes on some machines (seems more often on hiDPI 
machines (QHD/UHD etc)).

* Test case
Try installing Ubuntu on an hidpi machine, it should complete installation 
instead of crashing.

* Regression potential
The fix in ubiquity touches the code handle uid drop/privilege, that can have 
unexpected side effects so we need proper/complete testing of the installer

--

Update: Actually the crash occurs on slow-ish systems due to a race
condition. It's not strictly only hi-DPI machines - that's just the most
common place it is experienced.

---

https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77
https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15
https://errors.ubuntu.com/problem/dcd4c9da5ee0cc6d36324446e0e49d39705c90b7
https://errors.ubuntu.com/problem/cb82f70f9ede07369e8104da9ddf87e28b42257d
https://errors.ubuntu.com/problem/84a5563af3d2b85f098da832ece4cb8450bfd524

---

WORKAROUND:

1. Boot into the live session.
2. Settings > Devices > Displays > Scale = 100%
3. Click Apply.
4. Proceed with installation: Click "Install Ubuntu 18.04 LTS".

---

Crashed in a VM in the middle of installation. The host is Bionic up to
date.

>From the journal
Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3 ip:7f5a76936961 
sp:7ffde5090c50 error:0 in libglib-2.0.so.0.5400.1[7f5a768e6000+111000]
Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation:
Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last):
Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 757, in 
Feb 23 12:52:41 ubuntu /install.py[6858]: install.run()
Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 135, in run
Feb 23 12:52:41 ubuntu /install.py[6858]: self.copy_all()
Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 505, in copy_all
Feb 23 12:52:41 ubuntu /install.py[6858]: self.db.progress('SET', 10 + 
copy_progress)
Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 83, in 
Feb 23 12:52:41 ubuntu /install.py[6858]: lambda *args, **kw: 
self.command(command, *args, **kw))
Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 104, in command
Feb 23 12:52:41 ubuntu /install.py[6858]: status = int(status)
Feb 23 12:52:41 ubuntu /install.py[6858]: ValueError: invalid literal for int() 
with base 10: ''

ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.1
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CasperVersion: 1.388
Date: Fri Feb 23 12:52:28 2018
ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr 
keyboard-configuration/variantcode=oss
InterpreterPath: /usr/bin/python3.6
LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity -d
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=C.UTF-8
 SHELL=/bin/bash
Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
Signal: 5
SourcePackage: ubiquity
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
Title: ubiquity crashed with signal 5 in _XEventsQueued()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

** Affects: ubuntu-translations
 Importance: Medium
 Status: Unknown

** Affects: oem-priority
 Importance: Critical
 Status: Fix Released

** Affects: ubiquity (Ubuntu)
 Importance: High
 Assignee: Andrea Azzarone (azzar1)
 Status: Fix Released

** Affects: ubiquity (Ubuntu Bionic)
 Importance: High
 Assignee: Andrea Azzarone (azzar1)
 Status: Fix Released


** Tags: amd64 apport-crash bionic id-5a9829e833b1e20a0cfd336c iso-testing 
ubiquity-18.04.1 ubuntu verification-done-bionic verification-needed
-- 
[regression] ubiquity crashed in debconf.py:104 with ValueError: invalid 
literal for int() with base 10: ''
https://bugs.launchpad.net/bugs/1751252
You received this bug notification because you are a member of Ubuntu 
Translations Coordinators, which is subscribed to Ubuntu Translations.

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.

[Ubuntu-translations-coordinators] [Bug 1731070] Re: "_Skip" button label not translatable

[Launchpad Bug Tracker]

This bug was fixed in the package ubiquity - 19.10.19

---
ubiquity (19.10.19) eoan; urgency=medium

  [ Sebastien Bacher ]
  * Update the 'Skip' string to '_Skip', matching  the change done to
ubiquity.ui some years ago. The template needs to be manual updated which
wasn't done at the time, should make it translatable again (LP: #1731070)

  [ Mathieu Trudel-Lapierre ]
  * Update translations from Launchpad.
  * debian/real-po/templates.pot: update template using debconf-updatepo.

  [ Jean-Baptiste Lallement ]
  * Switch zpool sync property back to standard after installation
  * zfsutils-linux and zfs-initramfs moved to the live task, don't remove them
at the end of installation (LP: #1847739)
  * Change partition types to Solaris Boot and Root types

  [ Didier Roche ]
  * As we are not going to own in the end org.zsys, move our identifier tags
to com.ubuntu.zsys (LP: #1847711)

 -- Jean-Baptiste Lallement 
Fri, 11 Oct 2019 12:05:23 +0200

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

-- 
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching subscriptions: Ubuntu Translations bug mail
https://bugs.launchpad.net/bugs/1731070

Title:
  "_Skip" button label not translatable

Status in Ubuntu Translations:
  Confirmed
Status in ubiquity package in Ubuntu:
  Fix Released

Bug description:
  The "Skip" string is showing as untranslated in non-English Ubuntu
  installation. This is because "Skip" is in the translation template,
  but "_Skip" is not. (See comment #7.)

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

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1731070] Re: "_Skip" button label not translatable

[Launchpad Bug Tracker]

** Merge proposal linked:
   https://code.launchpad.net/~seb128/ubiquity/+git/ubiquity/+merge/373977

-- 
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching subscriptions: Ubuntu Translations bug mail
https://bugs.launchpad.net/bugs/1731070

Title:
  "_Skip" button label not translatable

Status in Ubuntu Translations:
  Confirmed
Status in ubiquity package in Ubuntu:
  In Progress

Bug description:
  The "Skip" string is showing as untranslated in non-English Ubuntu
  installation. This is because "Skip" is in the translation template,
  but "_Skip" is not. (See comment #7.)

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

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 545778] Re: xul-ext-lightning is only available in English

[Launchpad Bug Tracker]

This bug was fixed in the package thunderbird -
1:60.9.0+build1-0ubuntu0.19.04.1

---
thunderbird (1:60.9.0+build1-0ubuntu0.19.04.1) disco; urgency=medium

  * New upstream stable release (60.9.0build1)

  * Do not attach Wi-Fi syslog to apport reports (LP: #1801383)
- update debian/apport/source_thunderbird.py.in
  * Install the WeTransfer FileLink provider by default (LP: #1823361)
- update debian/thunderbird.install.in
  * Do not exclude calendar translations from the source tarball, and repack
the lightning xpi with all available locales (LP: #545778)
- update debian/config/tarball.conf
- update debian/build/rules.mk
- update debian/rules

 -- Olivier Tilloy   Mon, 07 Oct 2019
10:32:00 +0200

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

-- 
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching subscriptions: Ubuntu Translations bug mail
https://bugs.launchpad.net/bugs/545778

Title:
  xul-ext-lightning is only available in English

Status in One Hundred Papercuts:
  Invalid
Status in Mozilla Thunderbird:
  Invalid
Status in Ubuntu Translations:
  Invalid
Status in lightning-sunbird package in Ubuntu:
  Invalid
Status in thunderbird package in Ubuntu:
  Fix Released
Status in thunderbird source package in Xenial:
  Fix Released
Status in thunderbird source package in Bionic:
  Fix Released
Status in thunderbird source package in Disco:
  Fix Released

Bug description:
  ***
   ISSUE
  ***

  HOW TO REPRODUCE

  1. Change the user session language to other different than English.
  2. In Thunderbird, open the calendar

  EXPECTED BEHAVIOUR

  - The calendar interface to be in the session language.

  REAL BEHAVIOUR

  - The calendar is in English.

  RELEVANT DETAILS

  - None.

  **
   SOLUTION
  **

  WORK-AROUND

  - None known.

  FIX

  - .

  REGRESSION POTENTIAL

  - Since no code needs to be modified, the regression potential is very
  low.

  
   TECHNICAL INFO
  

  Binary package hint: lightning-extension

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

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 545778] Re: xul-ext-lightning is only available in English

[Launchpad Bug Tracker]

This bug was fixed in the package thunderbird -
1:60.9.0+build1-0ubuntu0.16.04.2

---
thunderbird (1:60.9.0+build1-0ubuntu0.16.04.2) xenial; urgency=medium

  * Enclose the path to the lightning extension XPI in double quotes to ensure
dh_install finds it
- update debian/rules

 -- Olivier Tilloy   Mon, 07 Oct 2019
10:59:57 +0200

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

-- 
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching subscriptions: Ubuntu Translations bug mail
https://bugs.launchpad.net/bugs/545778

Title:
  xul-ext-lightning is only available in English

Status in One Hundred Papercuts:
  Invalid
Status in Mozilla Thunderbird:
  Invalid
Status in Ubuntu Translations:
  Invalid
Status in lightning-sunbird package in Ubuntu:
  Invalid
Status in thunderbird package in Ubuntu:
  Fix Released
Status in thunderbird source package in Xenial:
  Fix Released
Status in thunderbird source package in Bionic:
  Fix Released
Status in thunderbird source package in Disco:
  Fix Released

Bug description:
  ***
   ISSUE
  ***

  HOW TO REPRODUCE

  1. Change the user session language to other different than English.
  2. In Thunderbird, open the calendar

  EXPECTED BEHAVIOUR

  - The calendar interface to be in the session language.

  REAL BEHAVIOUR

  - The calendar is in English.

  RELEVANT DETAILS

  - None.

  **
   SOLUTION
  **

  WORK-AROUND

  - None known.

  FIX

  - .

  REGRESSION POTENTIAL

  - Since no code needs to be modified, the regression potential is very
  low.

  
   TECHNICAL INFO
  

  Binary package hint: lightning-extension

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

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 545778] Re: xul-ext-lightning is only available in English

[Launchpad Bug Tracker]

This bug was fixed in the package thunderbird -
1:60.9.0+build1-0ubuntu0.18.04.1

---
thunderbird (1:60.9.0+build1-0ubuntu0.18.04.1) bionic; urgency=medium

  * New upstream stable release (60.9.0+build1)

  * Do not attach Wi-Fi syslog to apport reports (LP: #1801383)
- update debian/apport/source_thunderbird.py.in
  * Install the WeTransfer FileLink provider by default (LP: #1823361)
- update debian/thunderbird.install.in
  * Do not exclude calendar translations from the source tarball, and repack
the lightning xpi with all available locales (LP: #545778)
- update debian/config/tarball.conf
- update debian/build/rules.mk
- update debian/rules

 -- Olivier Tilloy   Mon, 07 Oct 2019
10:03:16 +0200

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

-- 
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching subscriptions: Ubuntu Translations bug mail
https://bugs.launchpad.net/bugs/545778

Title:
  xul-ext-lightning is only available in English

Status in One Hundred Papercuts:
  Invalid
Status in Mozilla Thunderbird:
  Invalid
Status in Ubuntu Translations:
  Invalid
Status in lightning-sunbird package in Ubuntu:
  Invalid
Status in thunderbird package in Ubuntu:
  Fix Released
Status in thunderbird source package in Xenial:
  Fix Released
Status in thunderbird source package in Bionic:
  Fix Released
Status in thunderbird source package in Disco:
  Fix Committed

Bug description:
  ***
   ISSUE
  ***

  HOW TO REPRODUCE

  1. Change the user session language to other different than English.
  2. In Thunderbird, open the calendar

  EXPECTED BEHAVIOUR

  - The calendar interface to be in the session language.

  REAL BEHAVIOUR

  - The calendar is in English.

  RELEVANT DETAILS

  - None.

  **
   SOLUTION
  **

  WORK-AROUND

  - None known.

  FIX

  - .

  REGRESSION POTENTIAL

  - Since no code needs to be modified, the regression potential is very
  low.

  
   TECHNICAL INFO
  

  Binary package hint: lightning-extension

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

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 545778] Re: xul-ext-lightning is only available in English

[Launchpad Bug Tracker]

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

** Changed in: lightning-sunbird (Ubuntu Disco)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching subscriptions: Ubuntu Translations bug mail
https://bugs.launchpad.net/bugs/545778

Title:
  xul-ext-lightning is only available in English

Status in One Hundred Papercuts:
  Invalid
Status in Mozilla Thunderbird:
  Invalid
Status in Ubuntu Translations:
  Invalid
Status in lightning-sunbird package in Ubuntu:
  Invalid
Status in thunderbird package in Ubuntu:
  Fix Released
Status in lightning-sunbird source package in Xenial:
  Confirmed
Status in thunderbird source package in Xenial:
  Fix Committed
Status in lightning-sunbird source package in Bionic:
  Confirmed
Status in thunderbird source package in Bionic:
  Fix Committed
Status in lightning-sunbird source package in Disco:
  Confirmed
Status in thunderbird source package in Disco:
  Fix Committed

Bug description:
  ***
   ISSUE
  ***

  HOW TO REPRODUCE

  1. Change the user session language to other different than English.
  2. In Thunderbird, open the calendar

  EXPECTED BEHAVIOUR

  - The calendar interface to be in the session language.

  REAL BEHAVIOUR

  - The calendar is in English.

  RELEVANT DETAILS

  - None.

  **
   SOLUTION
  **

  WORK-AROUND

  - None known.

  FIX

  - .

  REGRESSION POTENTIAL

  - Since no code needs to be modified, the regression potential is very
  low.

  
   TECHNICAL INFO
  

  Binary package hint: lightning-extension

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

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 545778] Re: xul-ext-lightning is only available in English

[Launchpad Bug Tracker]

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

** Changed in: lightning-sunbird (Ubuntu Bionic)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching subscriptions: Ubuntu Translations bug mail
https://bugs.launchpad.net/bugs/545778

Title:
  xul-ext-lightning is only available in English

Status in One Hundred Papercuts:
  Invalid
Status in Mozilla Thunderbird:
  Invalid
Status in Ubuntu Translations:
  Invalid
Status in lightning-sunbird package in Ubuntu:
  Invalid
Status in thunderbird package in Ubuntu:
  Fix Released
Status in lightning-sunbird source package in Xenial:
  Confirmed
Status in thunderbird source package in Xenial:
  Fix Committed
Status in lightning-sunbird source package in Bionic:
  Confirmed
Status in thunderbird source package in Bionic:
  Fix Committed
Status in lightning-sunbird source package in Disco:
  Confirmed
Status in thunderbird source package in Disco:
  Fix Committed

Bug description:
  ***
   ISSUE
  ***

  HOW TO REPRODUCE

  1. Change the user session language to other different than English.
  2. In Thunderbird, open the calendar

  EXPECTED BEHAVIOUR

  - The calendar interface to be in the session language.

  REAL BEHAVIOUR

  - The calendar is in English.

  RELEVANT DETAILS

  - None.

  **
   SOLUTION
  **

  WORK-AROUND

  - None known.

  FIX

  - .

  REGRESSION POTENTIAL

  - Since no code needs to be modified, the regression potential is very
  low.

  
   TECHNICAL INFO
  

  Binary package hint: lightning-extension

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

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 545778] Re: xul-ext-lightning is only available in English

[Launchpad Bug Tracker]

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

** Changed in: lightning-sunbird (Ubuntu Xenial)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching subscriptions: Ubuntu Translations bug mail
https://bugs.launchpad.net/bugs/545778

Title:
  xul-ext-lightning is only available in English

Status in One Hundred Papercuts:
  Invalid
Status in Mozilla Thunderbird:
  Invalid
Status in Ubuntu Translations:
  Invalid
Status in lightning-sunbird package in Ubuntu:
  Invalid
Status in thunderbird package in Ubuntu:
  Fix Released
Status in lightning-sunbird source package in Xenial:
  Confirmed
Status in thunderbird source package in Xenial:
  Fix Committed
Status in lightning-sunbird source package in Bionic:
  Confirmed
Status in thunderbird source package in Bionic:
  Fix Committed
Status in lightning-sunbird source package in Disco:
  Confirmed
Status in thunderbird source package in Disco:
  Fix Committed

Bug description:
  ***
   ISSUE
  ***

  HOW TO REPRODUCE

  1. Change the user session language to other different than English.
  2. In Thunderbird, open the calendar

  EXPECTED BEHAVIOUR

  - The calendar interface to be in the session language.

  REAL BEHAVIOUR

  - The calendar is in English.

  RELEVANT DETAILS

  - None.

  **
   SOLUTION
  **

  WORK-AROUND

  - None known.

  FIX

  - .

  REGRESSION POTENTIAL

  - Since no code needs to be modified, the regression potential is very
  low.

  
   TECHNICAL INFO
  

  Binary package hint: lightning-extension

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

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 545778] Re: xul-ext-lightning is only available in English

[Launchpad Bug Tracker]

This bug was fixed in the package thunderbird - 1:68.1.1+build1-0ubuntu1

---
thunderbird (1:68.1.1+build1-0ubuntu1) eoan; urgency=medium

  * New upstream stable release (68.1.1build1)

  * Build thunderbird against the system-wide version of sqlite3 (LP: #1845929)
- update debian/config/mozconfig.in
- update debian/control{,.in}

 -- Olivier Tilloy   Tue, 01 Oct 2019
14:47:00 +0200

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

-- 
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching subscriptions: Ubuntu Translations bug mail
https://bugs.launchpad.net/bugs/545778

Title:
  xul-ext-lightning is only available in English

Status in One Hundred Papercuts:
  Invalid
Status in Mozilla Thunderbird:
  Invalid
Status in Ubuntu Translations:
  Invalid
Status in lightning-sunbird package in Ubuntu:
  Invalid
Status in thunderbird package in Ubuntu:
  Fix Released

Bug description:
  ***
   ISSUE
  ***

  HOW TO REPRODUCE

  1. Change the user session language to other different than English.
  2. In Thunderbird, open the calendar

  EXPECTED BEHAVIOUR

  - The calendar interface to be in the session language.

  REAL BEHAVIOUR

  - The calendar is in English.

  RELEVANT DETAILS

  - None.

  **
   SOLUTION
  **

  WORK-AROUND

  - None known.

  FIX

  - .

  REGRESSION POTENTIAL

  - Since no code needs to be modified, the regression potential is very
  low.

  
   TECHNICAL INFO
  

  Binary package hint: lightning-extension

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

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 1842865] [NEW] Xubuntu 18.04 sometimes freezes when turned on on logo

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

When I turn off the computer, it hangs on the logo. The light on the
system unit continues to light. Does not respond to the keyboard. Kernel
version 5.0.0-27. Here is the error:

info: task systemd shutdown:1 blocked for more than 120 seconds
Not tainted 5.0.0-20-generic #21-Ubuntu
«echo 0 /proc/sys kernel/hung_task_timeout_secs» disables this message

https://ibb.co/PcYvDLq

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gvfs 1.36.1-0ubuntu1.3.3
ProcVersionSignature: Ubuntu 5.0.0-27.28~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-27-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CurrentDesktop: XFCE
Date: Thu Sep  5 09:44:35 2019
InstallationDate: Installed on 2019-08-09 (26 days ago)
InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
ProcEnviron:
 LANGUAGE=ru_UA:ru
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_UA.UTF-8
 SHELL=/bin/bash
SourcePackage: gvfs
UpgradeStatus: No upgrade log present (probably fresh install)
--- 
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  max1055 F pulseaudio
CurrentDesktop: XFCE
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-08-09 (37 days ago)
InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
IwConfig:
 enp0s25   no wireless extensions.
 
 enp7s4no wireless extensions.
 
 lono wireless extensions.
MachineType: Hewlett-Packard HP Compaq dc5800 Microtower
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-62-generic 
root=UUID=8c77fe78-d1d9-4452-aca0-eb1f84404122 ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 4.15.0-62.69-generic 4.15.18
RelatedPackageVersions:
 linux-restricted-modules-4.15.0-62-generic N/A
 linux-backports-modules-4.15.0-62-generic  N/A
 linux-firmware 1.173.9
RfKill:
 
Tags:  bionic
Uname: Linux 4.15.0-62-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 10/26/2015
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 786F2 v01.60
dmi.board.asset.tag: CZC8107S1Y
dmi.board.name: 2820h
dmi.board.vendor: Hewlett-Packard
dmi.chassis.asset.tag: CZC8107S1Y
dmi.chassis.type: 6
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786F2v01.60:bd10/26/2015:svnHewlett-Packard:pnHPCompaqdc5800Microtower:pvr:rvnHewlett-Packard:rn2820h:rvr:cvnHewlett-Packard:ct6:cvr:
dmi.product.family: 103C_53307F
dmi.product.name: HP Compaq dc5800 Microtower
dmi.sys.vendor: Hewlett-Packard

** Affects: ubuntu-translations
 Importance: Undecided
 Status: New

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


** Tags: amd64 apport-bug apport-collected bionic disco
-- 
Xubuntu 18.04 sometimes freezes when turned on on logo
https://bugs.launchpad.net/bugs/1842865
You received this bug notification because you are a member of Ubuntu 
Translations Coordinators, which is subscribed to Ubuntu Translations.

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp

[Ubuntu-translations-coordinators] [Bug 545778] Re: xul-ext-lightning is only available in English

[Launchpad Bug Tracker]

** Branch linked: lp:~mozillateam/thunderbird/thunderbird.bionic

** Branch linked: lp:~mozillateam/thunderbird/thunderbird.xenial

-- 
You received this bug notification because you are a member of Ubuntu
Translations Coordinators, which is subscribed to Ubuntu Translations.
Matching subscriptions: Ubuntu Translations bug mail
https://bugs.launchpad.net/bugs/545778

Title:
  xul-ext-lightning is only available in English

Status in One Hundred Papercuts:
  Invalid
Status in Mozilla Thunderbird:
  Invalid
Status in Ubuntu Translations:
  Invalid
Status in lightning-sunbird package in Ubuntu:
  Invalid
Status in thunderbird package in Ubuntu:
  Fix Committed

Bug description:
  ***
   ISSUE
  ***

  HOW TO REPRODUCE

  1. Change the user session language to other different than English.
  2. In Thunderbird, open the calendar

  EXPECTED BEHAVIOUR

  - The calendar interface to be in the session language.

  REAL BEHAVIOUR

  - The calendar is in English.

  RELEVANT DETAILS

  - None.

  **
   SOLUTION
  **

  WORK-AROUND

  - None known.

  FIX

  - .

  REGRESSION POTENTIAL

  - Since no code needs to be modified, the regression potential is very
  low.

  
   TECHNICAL INFO
  

  Binary package hint: lightning-extension

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

___
Mailing list: https://launchpad.net/~ubuntu-translations-coordinators
Post to : ubuntu-translations-coordinators@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-translations-coordinators
More help   : https://help.launchpad.net/ListHelp