[Touch-packages] [Bug 1921317] [NEW] [20VA, Realtek ALC287, Speaker, Internal] Playback problem

[Fikrul Arif]

Public bug reported:

Lenovo ThinkBook 14s G2
1. Boot to windows (ah yes, I'm still using windows for something that's not 
fully supported by Ubuntu).
2. Restart, boot to Ubuntu.
3. Got no sound, except just a cool "hreck" sound when it has to be a 
sound, only a short sound although I'm about to play a long audio. Probably 
each time playback is activated the short "hreck" sound is produced.
4. Restart, boot to Ubuntu again.
5. It is not fixed yet.

However the playback works if I fully turn the computer off and then
turn it on again, instead of restarting.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  fikr4n 1519 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Mar 25 11:34:59 2021
InstallationDate: Installed on 2021-03-17 (7 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed
Symptom_Card: sof-hda-dsp - sof-hda-dsp
Symptom_Jack: Speaker, Internal
Symptom_Type: None of the above
Title: [20VA, Realtek ALC287, Speaker, Internal] Playback problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/03/2021
dmi.bios.release: 1.38
dmi.bios.vendor: LENOVO
dmi.bios.version: F9CN38WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0Q55726 WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: ThinkBook 14s G2 ITL
dmi.ec.firmware.release: 1.37
dmi.modalias: 
dmi:bvnLENOVO:bvrF9CN38WW:bd03/03/2021:br1.38:efr1.37:svnLENOVO:pn20VA:pvrThinkBook14sG2ITL:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55726WIN:cvnLENOVO:ct10:cvrThinkBook14sG2ITL:
dmi.product.family: ThinkBook 14s G2 ITL
dmi.product.name: 20VA
dmi.product.sku: LENOVO_MT_20VA_BU_idea_FM_ThinkBook 14s G2 ITL
dmi.product.version: ThinkBook 14s G2 ITL
dmi.sys.vendor: LENOVO
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2021-03-19T21:35:47.990357

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

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

Title:
  [20VA, Realtek ALC287, Speaker, Internal] Playback problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Lenovo ThinkBook 14s G2
  1. Boot to windows (ah yes, I'm still using windows for something that's not 
fully supported by Ubuntu).
  2. Restart, boot to Ubuntu.
  3. Got no sound, except just a cool "hreck" sound when it has to be a 
sound, only a short sound although I'm about to play a long audio. Probably 
each time playback is activated the short "hreck" sound is produced.
  4. Restart, boot to Ubuntu again.
  5. It is not fixed yet.

  However the playback works if I fully turn the computer off and then
  turn it on again, instead of restarting.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.8.0-48.54~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  fikr4n 1519 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 25 11:34:59 2021
  InstallationDate: Installed on 2021-03-17 (7 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed
  Symptom_Card: sof-hda-dsp - sof-hda-dsp
  Symptom_Jack: Speaker, Internal
  Symptom_Type: None of the above
  Title: [20VA, Realtek ALC287, Speaker, Internal] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/03/2021
  dmi.bios.release: 1.38
  dmi.bios.vendor: LENOVO
  dmi.bios.version: F9CN38WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0Q55726 WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: ThinkBook 14s G2 ITL
  dmi.ec.firmware.release: 1.37
  dmi.modalias: 
dmi:bvnLENOVO:bvrF9CN38WW:bd03/03/2021:br1.38:efr1.37:svnLENOVO:pn20VA:pvrThinkBook14sG2ITL:rvnLENOVO:rnLNVNB161216:rvrSDK0Q55726WIN:cvnLENOVO:ct10:cvrThinkBook14sG2ITL:
  dmi.product.family: ThinkBook 

[Touch-packages] [Bug 1915159] Re: package linux-image-5.8.0-43-lowlatency 5.8.0-43.49 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Launchpad Bug Tracker]

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

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

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

Title:
  package linux-image-5.8.0-43-lowlatency 5.8.0-43.49 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  Regular apt-get upgrade…

  ProblemType: Package
  DistroRelease: Ubuntu 20.10
  Package: linux-image-5.8.0-43-lowlatency 5.8.0-43.49
  ProcVersionSignature: Ubuntu 5.8.0-41.46-lowlatency 5.8.18
  Uname: Linux 5.8.0-41-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  benjamin   2554 F pulseaudio
   /dev/snd/pcmC0D0p:   benjamin   2554 F...m pulseaudio
  CasperMD5CheckResult: skip
  Date: Tue Feb  9 16:26:12 2021
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2020-12-04 (67 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: Dell Inc. XPS 15 9500
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-41-lowlatency 
root=/dev/mapper/vgubuntu-root ro threadirqs quiet splash vt.handoff=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 
3.8.6-0ubuntu1
  PythonDetails: N/A
  RebootRequiredPkgs:
   linux-image-5.8.0-43-generic
   linux-base
  RelatedPackageVersions: grub-pc 2.04-1ubuntu35.2
  SourcePackage: initramfs-tools
  Title: package linux-image-5.8.0-43-lowlatency 5.8.0-43.49 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/24/2020
  dmi.bios.release: 1.6
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.1
  dmi.board.name: 05XYW7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.1:bd12/24/2020:br1.6:svnDellInc.:pnXPS159500:pvr:rvnDellInc.:rn05XYW7:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9500
  dmi.product.sku: 097D
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1911036] Re: GDK/GTK app crash in XFCE when performing drag operation (in gdk_window_cache_new <- gdk_window_cache_get <- drag_context_find_window_cache <- gdk_x11_drag_context_f

[Daniel van Vugt]

Proposed the fix to Ubuntu here: https://salsa.debian.org/gnome-
team/gtk3/-/merge_requests/5

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

Title:
  GDK/GTK app crash in XFCE when performing drag operation (in
  gdk_window_cache_new <- gdk_window_cache_get <-
  drag_context_find_window_cache <- gdk_x11_drag_context_find_window)

Status in GTK+:
  Unknown
Status in gtk+3.0 package in Ubuntu:
  Fix Committed
Status in gtk4 package in Ubuntu:
  Fix Committed

Bug description:
  For many months now, whenever any mouse drag is attempted in an
  application using the gtk tool kit, the application immediately
  crashes. I've noticed this at least in Firefox and thunar. It also
  occurs when displaying these applications from a Virtualbox machine or
  from another server running something other than Ubuntu.  The VM was
  running CentOS 8 and the remote server was running Mageia. Both
  Firefox and thunar run fine with Mageia's Xorg. It seems like the
  issue may be with the Xorg server on Ubuntu.

  I tried setting the GDK_SYNCHRONIZE variable to various settings but
  was unable to produce further debug output. The only other debug
  output I was able to gather is when running thunar with the --gtk-
  debug parameter (attached). I also tried running thunar with GDB but
  without recompiling it, it doesn't produce much information other than
  it's stopping in glib.

  Let me know what other information I can provide.

  (firefox:110380): Gdk-ERROR **: 13:47:04.663: The program 'firefox' received 
an X Window System error.
  This probably reflects a bug in the program.
  The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 8405 error_code 3 request_code 141 (Composite) minor_code 
8)
(Note to programmers: normally, X errors are reported asynchronously;
 that is, you will receive the error a while after causing it.
 To debug your program, run it with the GDK_SYNCHRONIZE environment
 variable to change this behavior. You can then get a meaningful
 backtrace from your debugger if you break on the gdk_x_error() function.)
  ExceptionHandler::GenerateDump cloned child 110611
  ExceptionHandler::SendContinueSignalToChild sent continue signal to child
  ExceptionHandler::WaitForContinueSignal waiting for continue signal...
  Exiting due to channel error.
  Exiting due to channel error.
  Exiting due to channel error.
  Exiting due to channel error.
  [1]+  Trace/breakpoint trap   (core dumped) firefox

  (Thunar:2961220): Gdk-ERROR **: 13:55:39.621: The program 'Thunar' received 
an X Window System error.
  This probably reflects a bug in the program.
  The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 64804 error_code 3 request_code 141 (Composite) minor_code 
8)
(Note to programmers: normally, X errors are reported asynchronously;
 that is, you will receive the error a while after causing it.
 To debug your program, run it with the GDK_SYNCHRONIZE environment
 variable to change this behavior. You can then get a meaningful
 backtrace from your debugger if you break on the gdk_x_error() function.)
  Trace/breakpoint trap (core dumped)

  $ ldd /bin/thunar
  linux-vdso.so.1 (0x7ffc0c8cc000)
  libthunarx-3.so.0 => /lib/x86_64-linux-gnu/libthunarx-3.so.0 
(0x7fdbb548c000)
  libexo-2.so.0 => /lib/x86_64-linux-gnu/libexo-2.so.0 
(0x7fdbb544f000)
  libgudev-1.0.so.0 => /lib/x86_64-linux-gnu/libgudev-1.0.so.0 
(0x7fdbb5442000)
  libnotify.so.4 => /lib/x86_64-linux-gnu/libnotify.so.4 
(0x7fdbb5437000)
  libSM.so.6 => /lib/x86_64-linux-gnu/libSM.so.6 (0x7fdbb542c000)
  libICE.so.6 => /lib/x86_64-linux-gnu/libICE.so.6 (0x7fdbb540e000)
  libxfce4ui-2.so.0 => /lib/x86_64-linux-gnu/libxfce4ui-2.so.0 
(0x7fdbb53f3000)
  libgtk-3.so.0 => /lib/x86_64-linux-gnu/libgtk-3.so.0 
(0x7fdbb4c42000)
  libgdk-3.so.0 => /lib/x86_64-linux-gnu/libgdk-3.so.0 
(0x7fdbb4b3d000)
  libatk-1.0.so.0 => /lib/x86_64-linux-gnu/libatk-1.0.so.0 
(0x7fdbb4b13000)
  libcairo.so.2 => /lib/x86_64-linux-gnu/libcairo.so.2 
(0x7fdbb49f)
  libgdk_pixbuf-2.0.so.0 => 
/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0 (0x7fdbb49c8000)
  libxfce4util.so.7 => /lib/x86_64-linux-gnu/libxfce4util.so.7 
(0x7fdbb49b4000)
  libxfconf-0.so.3 => /lib/x86_64-linux-gnu/libxfconf-0.so.3 
(0x7fdbb4996000)
  libpango-1.0.so.0 => /lib/x86_64-linux-gnu/libpango-1.0.so.0 
(0x7fdbb4947000)
  libgio-2.0.so.0 => /lib/x86_64-linux-gnu/libgio-2.0.so.0 
(0x7fdbb4766000)
  libgobject-2.0.so.0 => /lib/x86_64-linux-gnu/libgobject-2.0.so.0 
(0x7fdbb4706000)
  libglib-2.0.so.0 => /lib/x86_64-linux-gnu/libglib-2.0.so.0 
(0x7fdbb45dd000)
  libc.so.6 

[Touch-packages] [Bug 1919404] Re: Desktop icon shadows are broken at scale 200%

[Daniel van Vugt]

Also proposed the fix to Ubuntu here: https://salsa.debian.org/gnome-
team/gtk3/-/merge_requests/5

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

Title:
  Desktop icon shadows are broken at scale 200%

Status in Gnome Shell Extension Desktop Icons Ng:
  Unknown
Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Fix Committed

Bug description:
  Desktop icon shadows are broken at scale 200%.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-desktop-icons-ng/+bug/1919404/+subscriptions

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

[Touch-packages] [Bug 1787512] Re: gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from gtk_icon_info_load_icon_finish() [

[Daniel van Vugt]

** Changed in: gtk+3.0 (Ubuntu)
   Status: Triaged => Fix Released

** Tags added: fixed-in-3.24.14

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

Title:
  gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort()
  from g_assertion_message() from g_assertion_message_expr() from
  gtk_icon_info_load_icon_finish() ["assertion failed:
  (icon_info_get_pixbuf_ready (icon_info))"]

Status in GTK+:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 package in Fedora:
  Won't Fix

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

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

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

[Touch-packages] [Bug 1919404] Re: Desktop icon shadows are broken at scale 200%

[Daniel van Vugt]

** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu)
   Status: In Progress => Invalid

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

Title:
  Desktop icon shadows are broken at scale 200%

Status in Gnome Shell Extension Desktop Icons Ng:
  Unknown
Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  Fix Committed

Bug description:
  Desktop icon shadows are broken at scale 200%.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-desktop-icons-ng/+bug/1919404/+subscriptions

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

[Touch-packages] [Bug 1919404] Re: Desktop icon shadows are broken at scale 200%

[Daniel van Vugt]

** Changed in: gtk+3.0 (Ubuntu)
   Status: In Progress => Fix Committed

** Tags added: fixed-in-3.24.28 fixed-upstream

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

Title:
  Desktop icon shadows are broken at scale 200%

Status in Gnome Shell Extension Desktop Icons Ng:
  Unknown
Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu:
  In Progress
Status in gtk+3.0 package in Ubuntu:
  Fix Committed

Bug description:
  Desktop icon shadows are broken at scale 200%.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-desktop-icons-ng/+bug/1919404/+subscriptions

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

[Touch-packages] [Bug 1920640] Re: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing Key (2016)

[Who Cares]

You know that Canonical have huge problems if the guys responsible for
security are prompting you to trust keys downloaded through http
protocol

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

Title:
  EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic
  Signing Key (2016) 

Status in ubuntu-keyring package in Ubuntu:
  Fix Released
Status in ubuntu-keyring source package in Bionic:
  Confirmed
Status in ubuntu-keyring source package in Focal:
  Confirmed
Status in ubuntu-keyring source package in Groovy:
  Confirmed
Status in ubuntu-keyring source package in Hirsute:
  Fix Released

Bug description:
  The public key used by the debugging symbols repository
  /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg from the package ubuntu-
  dbgsym-keyring expired.

  $ apt policy ubuntu-dbgsym-keyring
  ubuntu-dbgsym-keyring:
    Installed: 2020.02.11.2
    Candidate: 2020.02.11.2
    Version table:
   *** 2020.02.11.2 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  500 http://archive.ubuntu.com/ubuntu focal/main i386 Packages
  100 /var/lib/dpkg/status
  $ gpg --no-default-keyring --keyring 
/usr/share/keyrings/ubuntu-dbgsym-keyring.gpg --list-keys
  /usr/share/keyrings/ubuntu-dbgsym-keyring.gpg
  -
  pub   rsa4096 2016-03-21 [SC] [expired: 2021-03-20]
    F2EDC64DC5AEE1F6B9C621F0C8CAB6595FDFF622
  uid   [ expired] Ubuntu Debug Symbol Archive Automatic Signing Key 
(2016) 

  
  Error message on "apt update":

  E: The repository 'http://ddebs.ubuntu.com bionic-updates Release' is not 
signed.
  N: Updating from such a repository can't be done securely, and is therefore 
disabled by default.
  N: See apt-secure(8) manpage for repository creation and user configuration 
details.
  W: GPG error: http://ddebs.ubuntu.com bionic Release: The following 
signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive 
Automatic Signing Key (2016) 
  E: The repository 'http://ddebs.ubuntu.com bionic Release' is not signed.
  N: Updating from such a repository can't be done securely, and is therefore 
disabled by default.
  N: See apt-secure(8) manpage for repository creation and user configuration 
details.
  W: GPG error: http://ddebs.ubuntu.com bionic-proposed Release: The following 
signatures were invalid: EXPKEYSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive 
Automatic Signing Key (2016) 
  E: The repository 'http://ddebs.ubuntu.com bionic-proposed Release' is not 
signed.
  N: Updating from such a repository can't be done securely, and is therefore 
disabled by default.
  N: See apt-secure(8) manpage for repository creation and user configuration 
details.

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

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

[Touch-packages] [Bug 1920836] Re: Show Extended Security Maintenence status

[Robert Ancell]

Merge request for master:
https://code.launchpad.net/~robert-ancell/software-properties/+git/software-properties/+merge/400153

Other branches for SRUing:
https://code.launchpad.net/~robert-ancell/software-properties/+git/software-properties/+ref/esm-focal
https://code.launchpad.net/~robert-ancell/software-properties/+git/software-properties/+ref/esm-bionic

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

Title:
  Show Extended Security Maintenence status

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

Bug description:
  [Impact]
  There is not currently a graphical method of determining if a system is 
subscribed to [Extended Security Maintenance](https://ubuntu.com/security/esm) 
updates. This is resolved by adding some [new 
UI](https://wiki.ubuntu.com/SoftwareUpdates#Extended_Security_Maintenance) to 
the software properties application.

  [Test Case]
  1. Install latest version of Ubuntu advantage:
  $ sudo add-apt-repository ppa:ua-client/stable
  $ sudo apt update
  $ sudo apt upgrade
  2. Open Software Properties
  3. Go to Updates tab.

  Expected result:
  Information is shown that indicates if this system is using Extended Security 
Maintenance updates, when updates will supported until, and a link to upgrade 
to ESM.

  Observed result:
  No ESM information currently shown.

  [Where problems could occur]
  - Software properties could hit a bug getting a response from the ua app. The 
current code carefully checks if and what is returned, falling back to a safe 
default behavior.
  - Launching software properties could trigger a bug in the ua app.
  - Software properties could show incorrect information, causing confusion for 
the user. The solution uses information from distro-info and the ua app which 
means software-properties contains no data about ESM, and instead relies on 
these apps that can be updated if things change.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1920836/+subscriptions

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

[Touch-packages] [Bug 1528422] Re: Additional drivers reports the wrong driver in use

[Si Dedman]

Edit: related to the above, I'm no longer able to use the 'Additional
Drivers' GUI since it's locked onto the wrong thing and greyed out. Any
help much appreciated.

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

Title:
  Additional drivers reports the wrong driver in use

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  See attached screenshot - it's reporting the AMD driver is in use,
  while in reality it is the Intel driver.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: software-properties-gtk 0.96.13.1
  ProcVersionSignature: Ubuntu 4.2.0-22.27-generic 4.2.6
  Uname: Linux 4.2.0-22-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Dec 22 12:45:42 2015
  InstallationDate: Installed on 2014-06-26 (543 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to wily on 2015-10-26 (56 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1528422/+subscriptions

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

[Touch-packages] [Bug 1920987] Re: IANA tzdata file format cannot represent different country code for a given timezone in different time periods [ i.e. Europe/Simferopol country code changes ]; iso 3

[Alexander]

And now the American does not agree with this, and considers it a
controversial issue. He does not even know what kind or tribe he is, or
how he came to be on the American continent in the first place... but he
does not agree with the age-old history of the peoples of the world.

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

Title:
  IANA tzdata file format cannot represent different country code for a
  given timezone in different time periods [ i.e. Europe/Simferopol
  country code changes ]; iso 3166-2 has no RU subdivisions for Crimea

Status in iso-codes package in Ubuntu:
  New
Status in tzdata package in Ubuntu:
  Opinion

Bug description:
  Europe/Simferopol,  Crimea is RUSSIA

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: tzdata 2021a-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0
  Uname: Linux 5.11.0-11-generic x86_64
  ApportVersion: 2.20.11-0ubuntu60
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Tue Mar 23 21:44:56 2021
  InstallationDate: Installed on 2021-03-21 (1 days ago)
  InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Alpha amd64 (20210321)
  PackageArchitecture: all
  SourcePackage: tzdata
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iso-codes/+bug/1920987/+subscriptions

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

[Touch-packages] [Bug 1920987] Re: IANA tzdata file format cannot represent different country code for a given timezone in different time periods [ i.e. Europe/Simferopol country code changes ]; iso 3

[Alexander]

As you can see, Simferopol, Sevastopol, Kerch, Feodosia... these are the
Greek names of cities. For which the Russians fought together with the
Greeks.

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

Title:
  IANA tzdata file format cannot represent different country code for a
  given timezone in different time periods [ i.e. Europe/Simferopol
  country code changes ]; iso 3166-2 has no RU subdivisions for Crimea

Status in iso-codes package in Ubuntu:
  New
Status in tzdata package in Ubuntu:
  Opinion

Bug description:
  Europe/Simferopol,  Crimea is RUSSIA

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: tzdata 2021a-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0
  Uname: Linux 5.11.0-11-generic x86_64
  ApportVersion: 2.20.11-0ubuntu60
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Tue Mar 23 21:44:56 2021
  InstallationDate: Installed on 2021-03-21 (1 days ago)
  InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Alpha amd64 (20210321)
  PackageArchitecture: all
  SourcePackage: tzdata
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iso-codes/+bug/1920987/+subscriptions

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

[Touch-packages] [Bug 1921295] [NEW] package linux-image-generic-hwe-20.04 5.8.0.45.51~20.04.31 failed to install/upgrade: problemas de dependencias - se deja sin configurar

[alarmasvillegas]

Public bug reported:



ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-image-generic-hwe-20.04 5.8.0.45.51~20.04.31
ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-44-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
AptOrdering:
 linux-headers-5.8.0-41-generic:amd64: Remove
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed Mar 24 20:09:16 2021
ErrorMessage: problemas de dependencias - se deja sin configurar
InstallationDate: Installed on 2020-05-10 (318 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.4
SourcePackage: initramfs-tools
Title: package linux-image-generic-hwe-20.04 5.8.0.45.51~20.04.31 failed to 
install/upgrade: problemas de dependencias - se deja sin configurar
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal

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

Title:
  package linux-image-generic-hwe-20.04 5.8.0.45.51~20.04.31 failed to
  install/upgrade: problemas de dependencias - se deja sin configurar

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-image-generic-hwe-20.04 5.8.0.45.51~20.04.31
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  AptOrdering:
   linux-headers-5.8.0-41-generic:amd64: Remove
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Mar 24 20:09:16 2021
  ErrorMessage: problemas de dependencias - se deja sin configurar
  InstallationDate: Installed on 2020-05-10 (318 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.4
  SourcePackage: initramfs-tools
  Title: package linux-image-generic-hwe-20.04 5.8.0.45.51~20.04.31 failed to 
install/upgrade: problemas de dependencias - se deja sin configurar
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1918920] Re: Harden test for no new acquires after transaction abort

[Brian Murray]

Hello Julian, or anyone else affected,

Accepted apt into groovy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/2.1.10ubuntu0.3 in
a few hours, and then in the -proposed repository.

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

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

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

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

** Changed in: apt (Ubuntu Groovy)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-groovy

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

Title:
  Harden test for no new acquires after transaction abort

Status in apt package in Ubuntu:
  Fix Committed
Status in apt source package in Bionic:
  New
Status in apt source package in Focal:
  New
Status in apt source package in Groovy:
  Fix Committed

Bug description:
  [Impact]
  test-pdiff-usage is somewhat flaky, especially on Debian, this makes it less 
flaky. No end user impact as it's a test-only change.

  [Test plan]
  Running autopkgtest, which runs our extensive integration test suite which 
includes the changed test.

  [Where problems could occur]
  No end user regression potential on its own, but might slightly change 
regression potential for future pdiff changes:

  Test approach is slightly different now. It still catches that updates
  fail correctly, but tests more concretely that a transaction was
  aborted rather than that no worker received work (which was not
  guaranteed, the work could be scheduled before it was aborted).

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

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

[Touch-packages] [Bug 1615381] Re: apt-get autoremove may remove current kernel

[Brian Murray]

Hello Jarno, or anyone else affected,

Accepted apt into groovy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/2.1.10ubuntu0.3 in
a few hours, and then in the -proposed repository.

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

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

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

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

** Changed in: apt (Ubuntu Groovy)
   Status: In Progress => Fix Committed

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

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

Title:
  apt-get autoremove may remove current kernel

Status in apt package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Trusty:
  Won't Fix
Status in unattended-upgrades source package in Xenial:
  Fix Released
Status in unattended-upgrades source package in Artful:
  Won't Fix
Status in apt source package in Bionic:
  Confirmed
Status in apt source package in Focal:
  Confirmed
Status in apt source package in Groovy:
  Fix Committed
Status in apt source package in Hirsute:
  Fix Released

Bug description:
  [Impact]
  APT will try and fail to remove the currently running kernel, when booted 
into an older kernel that is not protected. May wreak some havoc if mixed with 
other operations to the point that apt goes weird and needs manual fixing up.

  [Test case]
  For the SRUs we have included an automated test case that starts with an 
empty autoremove config file, and then checks that the running kernel is 
protected at runtime.

  You can also test manually, but it's not necessary:

  - Install new kernel
  - Reboot into kernel not listed as protected in 01autoremove-kernels
  - Run autoremove

  [Where problems could occur]
  We may more easily run out of space in /boot. hirsute has new autoremoval 
code that runs completely at runtime; but that seems a bit large to SRU after 
only a few weeks in hirsute. Hence, we should protect the current kernel _in 
addition_ to the other kernels, just like unattended-upgrades and 
update-manager do. This increases the risk of filling up /boot compared to 
older apt versions, but is at the same level as unattended-upgrades and 
update-manager.

  [Original bug report]

  This may happen, if you boot one of the older kernels, that is not
  protected by /etc/apt/apt.conf.d/01autoremove-kernels

  Workaround: run
  /etc/kernel/postinst.d/apt-auto-removal
  during each boot (e.g. by using cron).
  Note: The workaround breaks autoremoving feature of new unneeded kernels in  
unattended-upgrades i.e. the setting 
'Unattended-Upgrade::Remove-New-Unused-Dependencies "true"' (which is default 
in 16.04 unless 'Unattended-Upgrade::Remove-Unused-Dependencies "true"' is set 
in '/etc/apt/apt.conf.d/50unattended-upgrades'.

  In shell:

  $ uname -r
  4.4.0-22-generic
  $ apt-get -s autoremove
  NOTE: This is only a simulation!
    apt-get needs root privileges for real execution.
    Keep also in mind that locking is deactivated,
    so don't depend on the relevance to the real current situation!
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following packages will be REMOVED:
    linux-headers-4.4.0-21 linux-headers-4.4.0-21-generic linux-headers-4.4.0-22
    linux-headers-4.4.0-22-generic linux-headers-4.4.0-31-generic
    linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic
    linux-image-4.4.0-31-generic linux-image-extra-4.4.0-21-generic
    linux-image-extra-4.4.0-22-generic linux-image-extra-4.4.0-31-generic
  0 upgraded, 0 newly installed, 11 to remove and 13 not upgraded.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.12~ubuntu16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  

[Touch-packages] [Bug 1693900] Re: apt-get update should return exit code != 0 on error

[Brian Murray]

Hello Jens, or anyone else affected,

Accepted apt into groovy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/2.1.10ubuntu0.3 in
a few hours, and then in the -proposed repository.

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

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

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

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

** Changed in: apt (Ubuntu Groovy)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-groovy

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

Title:
  apt-get update should return exit code != 0 on error

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  New
Status in apt source package in Bionic:
  Triaged
Status in apt source package in Focal:
  Triaged
Status in apt source package in Groovy:
  Fix Committed

Bug description:
  [Impact]
  There is no way for scripts to run apt update and be sure that it was 
entirely successful.

  We introduce a new flag, --error-mode=any that makes apt update also
  error out on transient errors.

  [Test plan]
  We have included a test in the test-suite in 
test-apt-update-failure-propagation that ensures that warnings become errors.

  [Where problems could occur]
  If there's an issue some warnings for transient errors could become errors, 
or worse I suppose it's possible but unlikely for errors to be reported as 
warnings...

  Since the new behavior is behind a flag, regression potential for
  existing scripts is low if there is no bug.

  [Original bug report]

  When running 'apt-get update' (e.g. on a container install post-
  install script), apt-get return with exit code 0, even so it wasn't
  able to "update" properly. E.g.:

  + apt-get update
  Err:1 http://de.archive.ubuntu.com/ubuntu xenial InRelease
    Temporary failure resolving 'de.archive.ubuntu.com'
  Err:2 http://security.ubuntu.com/ubuntu xenial-security InRelease
    Temporary failure resolving 'security.ubuntu.com'
  Err:3 http://de.archive.ubuntu.com/ubuntu xenial-updates InRelease
    Temporary failure resolving 'de.archive.ubuntu.com'
  Reading package lists... Done
  W: Failed to fetch http://de.archive.ubuntu.com/ubuntu/dists/xenial/InRelease 
 Temporary failure resolving 'de.archive.ubuntu.com'
  W: Failed to fetch 
http://de.archive.ubuntu.com/ubuntu/dists/xenial-updates/InRelease  Temporary 
failure resolving 'de.archive.ubuntu.com'
  W: Failed to fetch 
http://security.ubuntu.com/ubuntu/dists/xenial-security/InRelease  Temporary 
failure resolving 'security.ubuntu.com'
  W: Some index files failed to download. They have been ignored, or old ones 
used instead.

  It should be corrected to return useful exit code, so that scripts can
  take the appropriate actions ...

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

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

[Touch-packages] [Bug 1916050] Re: Invalid base64 for high-bit characters

[Brian Murray]

Hello Julian, or anyone else affected,

Accepted apt into groovy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/2.1.10ubuntu0.3 in
a few hours, and then in the -proposed repository.

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

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

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

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

** Changed in: apt (Ubuntu Groovy)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-groovy

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

Title:
  Invalid base64 for high-bit characters

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Confirmed
Status in apt source package in Bionic:
  Confirmed
Status in apt source package in Focal:
  Confirmed
Status in apt source package in Groovy:
  Fix Committed
Status in apt source package in Hirsute:
  Fix Released

Bug description:
  [Impact]
  The Base64Encode function incorrectly encodes using char instead of uint8_t, 
leading to characters with the high bit set to be encoded wrongly. This 
function is used for base authentication, and high bits are set for UTF-8 
character sequences, so it's likely affecting people with utf-8 user names and 
passwords and might cause them to be denied access to their https resources 
(though arguably they'd work around that).

  [Test case]
  A unit test has been added that checks that the encoding is correct.

  [Where problems could occur]
  This only affects the base64 encoding function, which is only used for 
quoting user names and passwords in basic auth in http, but it's also exposed 
to library users and like in python-apt, so problems could occur wherever they 
use that base64 encoding function as well.

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

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

[Touch-packages] [Bug 1907850] Re: Cache not generated for all translations

[Brian Murray]

Hello Julian, or anyone else affected,

Accepted apt into groovy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/2.1.10ubuntu0.3 in
a few hours, and then in the -proposed repository.

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

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

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

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

** Changed in: apt (Ubuntu Groovy)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-groovy

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

Title:
  Cache not generated for all translations

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Confirmed
Status in apt source package in Bionic:
  Confirmed
Status in apt source package in Focal:
  Confirmed
Status in apt source package in Groovy:
  Fix Committed
Status in apt source package in Hirsute:
  Fix Released

Bug description:
  [Impact]
  In bug 1161743 we discovered that if a system is configured with multiple 
locales, only the locales of the user who generated the apt-cache will be 
available for translated descriptions.

  [Test case]
  An automated test case has been included as a snippet in  
test/integration/test-bug-49-search-in-all-translations which runs during 
autopkgtest. That's sufficient for validation.

  Manual test:

  # apt install locales-all # get the locale
  # export LANG=sv_SE.UTF-8
  # locale
  LANG=sv_SE.UTF-8
  LANGUAGE=
  LC_CTYPE="sv_SE.UTF-8"
  LC_NUMERIC="sv_SE.UTF-8"
  LC_TIME="sv_SE.UTF-8"
  LC_COLLATE="sv_SE.UTF-8"
  LC_MONETARY="sv_SE.UTF-8"
  LC_MESSAGES="sv_SE.UTF-8"
  LC_PAPER="sv_SE.UTF-8"
  LC_NAME="sv_SE.UTF-8"
  LC_ADDRESS="sv_SE.UTF-8"
  LC_TELEPHONE="sv_SE.UTF-8"
  LC_MEASUREMENT="sv_SE.UTF-8"
  LC_IDENTIFICATION="sv_SE.UTF-8"
  LC_ALL=
  # apt update
  # apt-cache show tasksel | grep Desc
  Description-sv: tool for selecting tasks for installation on Debian systems
  Description-md5: cbbb747708986d11ea77c80b9b038fec
  # apt-cache showpkg tasksel
  Package: tasksel
  Versions:
  3.34ubuntu16 
(/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_binary-amd64_Packages)
   Description Language:
   File: 
/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_binary-amd64_Packages
    MD5: cbbb747708986d11ea77c80b9b038fec
   Description Language: sv
   File: 
/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_i18n_Translation-sv
    MD5: cbbb747708986d11ea77c80b9b038fec
   Description Language: en
   File: 
/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_i18n_Translation-en
    MD5: cbbb747708986d11ea77c80b9b038fec
  [...]

  So far so good, but now assume the root user actually has C configured
  as locale, and e.g. runs apt-cache show (or apt-daily.service does an
  update):

  root@g:~# rm /var/cache/apt/*.bin
  root@g:~# LANG=C apt-cache  show tasksel
  [...]
  Description-en: tool for selecting tasks for installation on Debian systems
   This package provides 'tasksel', a simple interface for users who
   want to configure their system to perform a specific task.

  root@g:~# apt-cache  showpkg tasksel
  Package: tasksel
  Versions:
  3.34ubuntu16 
(/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_binary-amd64_Packages)
   Description Language:
   File: 
/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_binary-amd64_Packages
    MD5: cbbb747708986d11ea77c80b9b038fec
   Description Language: en
   File: 
/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_groovy_main_i18n_Translation-en
    MD5: cbbb747708986d11ea77c80b9b038fec

  This should show the sv locale as well given that it's still around
  (also we are still running with LANG=sv_SE.UTF-8), but it only
  generated the cache with the english language description in here.

  

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

[Brian Murray]

Hello udippel, or anyone else affected,

Accepted apt into groovy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/2.1.10ubuntu0.3 in
a few hours, and then in the -proposed repository.

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

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

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

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

** Changed in: apt (Ubuntu Groovy)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-groovy

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

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

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

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

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

  [Test plan]

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

  import apt
  import time

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

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

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-release-upgrader-core 1:20.04.25
  ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60
  Uname: Linux 5.4.0-48-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.9
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashDB: ubuntu
  CurrentDesktop: KDE
  Date: Thu Oct  1 11:48:39 2020
  InstallationDate: Installed on 2019-03-14 (566 days ago)
  InstallationMedia: Kubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  

[Touch-packages] [Bug 1916725] Re: Protected/Important packages are not deconfigured, require Force-LoopBreak

[Brian Murray]

Hello Julian, or anyone else affected,

Accepted apt into groovy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/apt/2.1.10ubuntu0.3 in
a few hours, and then in the -proposed repository.

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

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

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

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

** Changed in: apt (Ubuntu Groovy)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-groovy

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

Title:
  Protected/Important packages are not deconfigured, require Force-
  LoopBreak

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Bionic:
  Triaged
Status in apt source package in Focal:
  Triaged
Status in apt source package in Groovy:
  Fix Committed
Status in apt source package in Hirsute:
  Fix Released

Bug description:
  [Impact]
  If a package that is Protected: yes (or Important: yes), or one of it's 
dependencies, is involved in a dependency loop with Breaks, APT requires 
APT::Force-LoopBreak instead of resolving the situation directly.

  On focal, we also introduce the actual support for protected packages
  to enable upgrading to later releases more easily (in case a protected
  package needs to be removed during the upgrade), and to make the
  backport more similar to main.

  [Test plan]
  Run the integration test suite (the autopkgtest) :)

  Our test suite covers the tests for both Breaks and Conflicts.

  Breaks:

  protected-sysvinit (= 1) without dependencies is installed
  protected-sysvinit (= 2) Pre-Depends protected-systemd-sysv
  protected-systemd-sysv (= 2) Breaks: protected-sysvinit (<< 2)

  Test: Install protected-sysvinit (= 2)
  Expected result: Unpacking protected-sysvinit (= 2) deconfigures 
protected-sysvinit (= 1), and then we unpack and configure protected-sysvinit 
(= 2) and end up with a working system.

  Conflicts: As for Breaks, but the Conflicts will remove the package
  temporarily, requiring the use of APT::Force-LoopBreak option.

  For focal, we also do have a test to check that the Protected field is
  being used.

  [Where problems could occur]
  We now allow dpkg to automatically deconfigure protected packages. This 
should just make them behave like normal packages to APT's eye, but bugs I 
guess could occur somewhere in the APT/dpkg interaction (this only applies to 
releases with Protected support in dpkg, Important is not affected, it's always 
been "normal" for dpkg).

  During development, we accidentally simplified the patch so much that
  Conflicts did not require Force-LoopBreak for temporary removal. We
  fixed that, but it points out that there is a place where the loop
  break check happens that is a potential regression place.

  On focal, we pass additional flags to dpkg that focal's dpkg does not
  understand, however, we only do that if dpkg asserts it does that, so
  in practice, this should all work fine and the code path will only be
  taken with >=groovy dpkg.

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

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

[Touch-packages] [Bug 1917780] Re: initramfs-tools does not include fsck binaries in the initrd if all mount pass are 0

[Launchpad Bug Tracker]

This bug was fixed in the package initramfs-tools - 0.139ubuntu3

---
initramfs-tools (0.139ubuntu3) hirsute; urgency=medium

  * hooks/fsck: always include fsck binaries irrespective of PASSNO value,
otherwise initrds fail to mount rootfs and have no ability to fix the
rootfs. LP: #1917780

 -- Dimitri John Ledkov   Wed, 24 Mar 2021 15:21:50
+

** Changed in: initramfs-tools (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  initramfs-tools does not include fsck binaries in the initrd if all
  mount pass are 0

Status in initramfs-tools package in Ubuntu:
  Fix Released

Bug description:
  [Impact]

   * initramfs-tools does not include fsck in initrd if MNT_PASS equals
  zero in the fstab entries.

  This has lead to the following situation :
  when dropping to initramfs shell during boot due to fs errors, we are not 
able to run fsck manually
  because it is not included in initrd.

  fsck should be included regardless of the MNT_PASS value.

  [Test Plan]

   * change /etc/fstab with PASSNO set to 0 for all entries
   * update-initramfs -u
   * lsinitramfs that is just generated
   * observe that it includes fsck utilities for the filesystems in /etc/fstab. 
I.e. fsck.ext4 e2fsck must exist

  
  [Where problems could occur]

   * The initramfs size will increase slightly upon upgrade, for the
  same initramfs-tools default options & kernel. However, one can
  control and remove fsck binaries (or include more of them) by setting
  FSTYPE variable in the initramfs settings.

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

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

[Touch-packages] [Bug 1920837] Re: apport bugs from official raspi or riscv images are not identified

[Launchpad Bug Tracker]

This bug was fixed in the package apport - 2.20.11-0ubuntu61

---
apport (2.20.11-0ubuntu61) hirsute; urgency=medium

  * apport/hookutils.py: when creating KernLog with MAC information use
root_command_output with dmesg. Missed when fixing LP #1896095.
  * data/general-hooks/ubuntu.py: tag bugs from Raspberry Pi images and RISCV
images appropriately. (LP: #1920837)

 -- Brian Murray   Wed, 24 Mar 2021 08:07:43 -0700

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

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

Title:
  apport bugs from official raspi or riscv images are not identified

Status in apport package in Ubuntu:
  Fix Released

Bug description:
  It would be helpful if bugs reported from images for Raspberry Pi's or
  RISCV systems were tagged so that one could search for bugs from
  systems running those images e.g. 'raspi-image'.

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

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

[Touch-packages] [Bug 1542471] Re: Playing mp3 files causes: Problem occurred without error being set. This is a bug in Rhythmbox or GStreamer.

[crvi]

This is being addressed as part of upstream issue
https://gitlab.gnome.org/GNOME/rhythmbox/-/issues/1451.


** Bug watch added: gitlab.gnome.org/GNOME/rhythmbox/-/issues #1451
   https://gitlab.gnome.org/GNOME/rhythmbox/-/issues/1451

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

Title:
  Playing mp3 files causes: Problem occurred without error being set.
  This is a bug in Rhythmbox or GStreamer.

Status in gstreamer1.0 package in Ubuntu:
  Confirmed
Status in rhythmbox package in Ubuntu:
  Incomplete

Bug description:
  I get the following error in the console when trying to play a mp3
  file using Rhythmbox:

  (21:23:27) [0x832a60] [rb_shell_player_error] rb-shell-player.c:2443:
  playback error while playing: Problem occurred without error being
  set. This is a bug in Rhythmbox or GStreamer.

  I don't get the same error while trying to play the same file using
  'Video's. I installed the required codec using the 'Video's
  application as it told me to install a codec.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libgstreamer1.0-0 1.7.1-1
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.19.4-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb  5 21:24:05 2016
  ExecutablePath: /usr/bin/rhythmbox
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1542471/+subscriptions

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

[Touch-packages] [Bug 1920987] Re: IANA tzdata file format cannot represent different country code for a given timezone in different time periods [ i.e. Europe/Simferopol country code changes ]; iso 3

[Alexander]

First there was the Crimea (Cimmeria, pre-Scythian period), then Rome,
and already then the Vatican. At that time, Rome was not yet in the
project.

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

Title:
  IANA tzdata file format cannot represent different country code for a
  given timezone in different time periods [ i.e. Europe/Simferopol
  country code changes ]; iso 3166-2 has no RU subdivisions for Crimea

Status in iso-codes package in Ubuntu:
  New
Status in tzdata package in Ubuntu:
  Opinion

Bug description:
  Europe/Simferopol,  Crimea is RUSSIA

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: tzdata 2021a-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0
  Uname: Linux 5.11.0-11-generic x86_64
  ApportVersion: 2.20.11-0ubuntu60
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Tue Mar 23 21:44:56 2021
  InstallationDate: Installed on 2021-03-21 (1 days ago)
  InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Alpha amd64 (20210321)
  PackageArchitecture: all
  SourcePackage: tzdata
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iso-codes/+bug/1920987/+subscriptions

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

[Touch-packages] [Bug 1874824] Re: pgrep reports error "cannot allocate" when run without stack limit

[Ubuntu Foundations Team Bug Bot]

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

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

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

Title:
  pgrep reports error "cannot allocate" when run without stack limit

Status in procps package in Ubuntu:
  Fix Committed
Status in procps source package in Focal:
  In Progress
Status in procps source package in Groovy:
  In Progress
Status in procps source package in Hirsute:
  Fix Committed
Status in procps package in Debian:
  New

Bug description:
  [Impact]

- Users who have ulimit set high would see either slow
  or failed pgrep and pkill commands
- Users who have ulimit set to unlimited would see
  failed pgrep and pkill commands
- This bug occurs because the behavior of sysconf(_SC_ARG_MAX)
  changed with a newer version of the kernel.

  [Test Case]

- set the ulimit to unlimited by running `ulimit -S -s unlimited`
- run `pgrep bash` to see that the "cannot allocate" error is
   printed and the command has failed.

  [Where Problems Could Occur]

- We have set upper and lower limits on the size of the malloc, but
  if further kernel versions break the call to sysconf in
  unexpected ways we could still see problems.

  [Original Description]

  If you have no stack limit (ulimit -S -s unlimited), any pgrep call
  will fail with an error:

  > pgrep vim
  pgrep: cannot allocate 4611686018427387903 bytes

  If you have a high stack limit (e.g. ulimit -S -s 50), pgrep is
  very slow:

  > time pgrep vim
  2196
  real 8.48s user 8.40s syst 0.07s busy 99% rmem 253444

  The relevant upstream bug report could be: 
https://gitlab.com/procps-ng/procps/-/issues/152
  Archlinux bug report: https://bugs.archlinux.org/task/66093

  procps:
    Installed: 2:3.3.16-1ubuntu2
    500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

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

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

[Touch-packages] [Bug 1874824] Re: pgrep reports error "cannot allocate" when run without stack limit

[William Wilson]

** Description changed:

+ [Impact]
+ 
+   - Users who have ulimit set high would see either slow
+ or failed pgrep and pkill commands
+   - Users who have ulimit set to unlimited would see
+ failed pgrep and pkill commands
+   - This bug occurs because the behavior of sysconf(_SC_ARG_MAX)
+ changed with a newer version of the kernel.
+ 
+ [Test Case]
+ 
+   - set the ulimit to unlimited by running `ulimit -S -s unlimited`
+   - run `pgrep bash` to see that the "cannot allocate" error is
+  printed and the command has failed.
+ 
+ [Where Problems Could Occur]
+ 
+   - We have set upper and lower limits on the size of the malloc, but
+ if further kernel versions break the call to sysconf in
+ unexpected ways we could still see problems.
+ 
+ [Original Description]
+ 
  If you have no stack limit (ulimit -S -s unlimited), any pgrep call will
  fail with an error:
  
  > pgrep vim
  pgrep: cannot allocate 4611686018427387903 bytes
  
  If you have a high stack limit (e.g. ulimit -S -s 50), pgrep is very
  slow:
  
  > time pgrep vim
  2196
  real 8.48s user 8.40s syst 0.07s busy 99% rmem 253444
  
  The relevant upstream bug report could be: 
https://gitlab.com/procps-ng/procps/-/issues/152
  Archlinux bug report: https://bugs.archlinux.org/task/66093
  
  procps:
-   Installed: 2:3.3.16-1ubuntu2
-   500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
+   Installed: 2:3.3.16-1ubuntu2
+   500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

** Changed in: procps (Ubuntu Hirsute)
   Status: Triaged => In Progress

** Changed in: procps (Ubuntu Groovy)
   Status: Confirmed => In Progress

** Changed in: procps (Ubuntu Focal)
   Status: Confirmed => In Progress

** Changed in: procps (Ubuntu Hirsute)
   Status: In Progress => Fix Committed

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

Title:
  pgrep reports error "cannot allocate" when run without stack limit

Status in procps package in Ubuntu:
  Fix Committed
Status in procps source package in Focal:
  In Progress
Status in procps source package in Groovy:
  In Progress
Status in procps source package in Hirsute:
  Fix Committed
Status in procps package in Debian:
  New

Bug description:
  [Impact]

- Users who have ulimit set high would see either slow
  or failed pgrep and pkill commands
- Users who have ulimit set to unlimited would see
  failed pgrep and pkill commands
- This bug occurs because the behavior of sysconf(_SC_ARG_MAX)
  changed with a newer version of the kernel.

  [Test Case]

- set the ulimit to unlimited by running `ulimit -S -s unlimited`
- run `pgrep bash` to see that the "cannot allocate" error is
   printed and the command has failed.

  [Where Problems Could Occur]

- We have set upper and lower limits on the size of the malloc, but
  if further kernel versions break the call to sysconf in
  unexpected ways we could still see problems.

  [Original Description]

  If you have no stack limit (ulimit -S -s unlimited), any pgrep call
  will fail with an error:

  > pgrep vim
  pgrep: cannot allocate 4611686018427387903 bytes

  If you have a high stack limit (e.g. ulimit -S -s 50), pgrep is
  very slow:

  > time pgrep vim
  2196
  real 8.48s user 8.40s syst 0.07s busy 99% rmem 253444

  The relevant upstream bug report could be: 
https://gitlab.com/procps-ng/procps/-/issues/152
  Archlinux bug report: https://bugs.archlinux.org/task/66093

  procps:
    Installed: 2:3.3.16-1ubuntu2
    500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

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

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

[Touch-packages] [Bug 1874824] Re: pgrep reports error "cannot allocate" when run without stack limit

[William Wilson]

Attached is a patch to fix the issue in hirsute. Assuming this is
approved, I have also prepared the SRUs for focal and groovy.

** Patch added: "Hirsute debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1874824/+attachment/5480543/+files/lp1874824_hirsute.debdiff

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

Title:
  pgrep reports error "cannot allocate" when run without stack limit

Status in procps package in Ubuntu:
  In Progress
Status in procps source package in Focal:
  In Progress
Status in procps source package in Groovy:
  In Progress
Status in procps source package in Hirsute:
  In Progress
Status in procps package in Debian:
  New

Bug description:
  [Impact]

- Users who have ulimit set high would see either slow
  or failed pgrep and pkill commands
- Users who have ulimit set to unlimited would see
  failed pgrep and pkill commands
- This bug occurs because the behavior of sysconf(_SC_ARG_MAX)
  changed with a newer version of the kernel.

  [Test Case]

- set the ulimit to unlimited by running `ulimit -S -s unlimited`
- run `pgrep bash` to see that the "cannot allocate" error is
   printed and the command has failed.

  [Where Problems Could Occur]

- We have set upper and lower limits on the size of the malloc, but
  if further kernel versions break the call to sysconf in
  unexpected ways we could still see problems.

  [Original Description]

  If you have no stack limit (ulimit -S -s unlimited), any pgrep call
  will fail with an error:

  > pgrep vim
  pgrep: cannot allocate 4611686018427387903 bytes

  If you have a high stack limit (e.g. ulimit -S -s 50), pgrep is
  very slow:

  > time pgrep vim
  2196
  real 8.48s user 8.40s syst 0.07s busy 99% rmem 253444

  The relevant upstream bug report could be: 
https://gitlab.com/procps-ng/procps/-/issues/152
  Archlinux bug report: https://bugs.archlinux.org/task/66093

  procps:
    Installed: 2:3.3.16-1ubuntu2
    500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

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

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

[Touch-packages] [Bug 1841783] Re: Update to 1.2.0?

[Amr Ibrahim]

Upstream Speex moved to GitLab (links updated in the description). The
Debian maintainer probably abandoned this package. I suggest that the
package moves under the maintainership of the Debian Multimedia Team.

** Tags added: hirsute

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

Title:
  Update to 1.2.0?

Status in speex package in Ubuntu:
  Triaged
Status in speex package in Debian:
  New

Bug description:
  The source was split in rc2, Debian didn't follow the change, and we
  are in sync, do we want to update?

  Speex and SpeexDSP

  https://gitlab.xiph.org/xiph/speex

  https://gitlab.xiph.org/xiph/speexdsp

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

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

[Touch-packages] [Bug 1841783] Re: Update to 1.2.0?

[Amr Ibrahim]

** Description changed:

  The source was split in rc2, Debian didn't follow the change, and we are
  in sync, do we want to update?
  
  Speex and SpeexDSP
  
- https://git.xiph.org/?p=speex.git;a=summary
+ https://gitlab.xiph.org/xiph/speex
  
- https://git.xiph.org/?p=speexdsp.git;a=summary
+ https://gitlab.xiph.org/xiph/speexdsp

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

Title:
  Update to 1.2.0?

Status in speex package in Ubuntu:
  Triaged
Status in speex package in Debian:
  New

Bug description:
  The source was split in rc2, Debian didn't follow the change, and we
  are in sync, do we want to update?

  Speex and SpeexDSP

  https://gitlab.xiph.org/xiph/speex

  https://gitlab.xiph.org/xiph/speexdsp

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

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

[Touch-packages] [Bug 1920987] Re: IANA tzdata file format cannot represent different country code for a given timezone in different time periods [ i.e. Europe/Simferopol country code changes ]; iso 3

[Dimitri John Ledkov]

To be fair, Sevastopol has always had a special status of a federal city
- across all times. Closes analogy being Vatican City. It was federal
city separate from Crimea during whichever government defacto government
ruling be it USSR, Ukranian SSR, Ukrain or Russian Federation.

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

Title:
  IANA tzdata file format cannot represent different country code for a
  given timezone in different time periods [ i.e. Europe/Simferopol
  country code changes ]; iso 3166-2 has no RU subdivisions for Crimea

Status in iso-codes package in Ubuntu:
  New
Status in tzdata package in Ubuntu:
  Opinion

Bug description:
  Europe/Simferopol,  Crimea is RUSSIA

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: tzdata 2021a-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0
  Uname: Linux 5.11.0-11-generic x86_64
  ApportVersion: 2.20.11-0ubuntu60
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Tue Mar 23 21:44:56 2021
  InstallationDate: Installed on 2021-03-21 (1 days ago)
  InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Alpha amd64 (20210321)
  PackageArchitecture: all
  SourcePackage: tzdata
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iso-codes/+bug/1920987/+subscriptions

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

[Touch-packages] [Bug 1793763] Re: NetworkManager interaction with dhclient triggers IP conflict detection at dhcp server, causes ip address changing every day

[Brandon Applegate]

For what it's worth - I am seeing (I believe) this same issue on the
latest Kali linux:

https://bugs.kali.org/view.php?id=7116

What's very interesting is that after this race condition happens, the
machine still responds to the old IP yet it doesn't show with 'ip addr
show'.  Seems to be something down in the kernel that is still claiming
this old IP.

** Bug watch added: bugs.kali.org/ #7116
   https://bugs.kali.org/view.php?id=7116

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

Title:
  NetworkManager interaction with dhclient triggers IP conflict
  detection at dhcp server, causes ip address changing every day

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  After installing my laptop with Ubuntu and using the wired network
  cable with default NetworkManager service to handle the connection, I
  ran into the issue that my local ipv4 address changes every day, while
  this never happens for other devices in the network. This is
  undesirable to me, because it exhausts the local networks IP address
  pool and the change of IP is inconvenient when working with services
  like SSH, samba, etc. Added to this, I sometimes experience random
  network outages especially when waking up from suspend.

  After some investigation, I found the following to happen:

  - The exact time the DHCP server provides with a new IP address that 
different from previous one, is when I wake up my laptop after about 12 hours 
of being suspended, typicaly at the start of the new working day.
  - When I lookup the logs of the DHCP server at the time of the laptop getting 
its new IP address, I find the following:
  Sep 21 14:36 router dhcpd: DHCPDISCOVER from 68:f7:28:3f:a0:11 via eth2
  Sep 21 14:36 router dhcpd: Abandoning IP address 192.168.1.137: pinged before 
offer
  Sep 21 14:36 router dhcpd: DHCPDISCOVER from 68:f7:28:3f:a0:11 via eth2
  Sep 21 14:36 router dhcpd: DHCPOFFER on 192.168.1.139 to 68:f7:28:3f:a0:11 
(kubuntu1804) via eth2

  It looks like the DHCP server is detecting a possible IP conflict
  because it can ping .137 while a DHCPDISCOVER for the hardware address
  matches the lease with the same IP address it is about to offer. To
  prevent problems, the DHCP server finds a new free IP address .139 and
  offers this one instead.

  Why is this triggered by the ubuntu client? When I look at the client
  logs at the same time, I see following to happen:

  Sep 21 00:27 kubuntu1804 systemd-sleep[21703]: Suspending system...
  Sep 21 14:36 kubuntu1804 kernel: [14934.160293] Restarting tasks ... done.
  Sep 21 14:36 kubuntu1804 NetworkManager[1027]:   [1537533403.1923] 
device (enp0s25): carrier: link connected
  Sep 21 14:36 kubuntu1804 NetworkManager[1027]:   [1537533403.1925] 
device (enp0s25): DHCPv4 lease renewal requested
  Sep 21 14:36 kubuntu1804 NetworkManager[1027]:   [1537533403.2246] 
dhcp4 (enp0s25): canceled DHCP transaction, DHCP client pid 18900
  Sep 21 14:36 kubuntu1804 NetworkManager[1027]:   [1537533403.2247] 
dhcp4 (enp0s25): state changed bound -> done
  Sep 21 14:36 kubuntu1804 NetworkManager[1027]:   [1537533403.2257] 
dhcp4 (enp0s25): activation: beginning transaction (timeout in 45 seconds)
  Sep 21 14:36 kubuntu1804 NetworkManager[1027]:   [1537533403.2292] 
dhcp4 (enp0s25): dhclient started with pid 21860
  Sep 21 14:36 kubuntu1804 dhclient[21860]: DHCPDISCOVER on enp0s25 to 
255.255.255.255 port 67 interval 3 (xid=0x71ed8c51)
  Sep 21 14:36 kubuntu1804 dhclient[21860]: DHCPDISCOVER on enp0s25 to 
255.255.255.255 port 67 interval 5 (xid=0x71ed8c51)
  Sep 21 14:36 kubuntu1804 dhclient[21860]: DHCPREQUEST of 192.168.1.139 on 
enp0s25 to 255.255.255.255 port 67 (xid=0x518ced71)
  Sep 21 14:36 kubuntu1804 dhclient[21860]: DHCPOFFER of 192.168.1.139 from 
192.168.1.1
  Sep 21 14:36 kubuntu1804 dhclient[21860]: DHCPACK of 192.168.1.139 from 
192.168.1.1

  So if I understand it well, the summary of what happens here is:

  1) Client wakes up after being suspended for about 14h
  2) Existing running dhclient fired from NetworkManager discovers the lease 
has expired and requesting a renewal
  3) Shortly after that this dhclient is killed by NetworkManager, probably 
because NetworkManager has detected a "link connected" event, caused by the 
suspend (the cable has not been removed physicaly). The old dhclient is killed 
during the lease renewal and probably long before the renewal procedure could 
be proparly handled
  4) A new dhclient is fired by NetworkManager, performing a whole new DHCP 
request, getting a new IP address from the server

  I expect the events 2 and 3 happening simultaneously are causing
  trouble. Probably the old IP .137 is already set to the interface
  while handling the lease renewal and then a new dhclient is started
  performing again a new DHCPREQUEST, confusing the dhcp server.

  When I look 

[Touch-packages] [Bug 1920987] Re: IANA tzdata file format cannot represent different country code for a given timezone in different time periods [ i.e. Europe/Simferopol country code changes ]

[Dimitri John Ledkov]

In the iso-codes package there is a related issue, ISO 3166-2:RU
contains no codes for the Russian-administered Republic of Crimea and
Federal City of Sevastopol. Instead the UA codes are still specified,
i.e. UA-43 for Crimea.

** Also affects: iso-codes (Ubuntu)
   Importance: Undecided
   Status: New

** Summary changed:

- IANA tzdata file format cannot represent different country code for a given 
timezone in different time periods [ i.e. Europe/Simferopol country code 
changes ]
+ IANA tzdata file format cannot represent different country code for a given 
timezone in different time periods [ i.e. Europe/Simferopol country code 
changes ]; iso 3166-2 has no RU subdivisions for Crimea

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

Title:
  IANA tzdata file format cannot represent different country code for a
  given timezone in different time periods [ i.e. Europe/Simferopol
  country code changes ]; iso 3166-2 has no RU subdivisions for Crimea

Status in iso-codes package in Ubuntu:
  New
Status in tzdata package in Ubuntu:
  Opinion

Bug description:
  Europe/Simferopol,  Crimea is RUSSIA

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: tzdata 2021a-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0
  Uname: Linux 5.11.0-11-generic x86_64
  ApportVersion: 2.20.11-0ubuntu60
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Tue Mar 23 21:44:56 2021
  InstallationDate: Installed on 2021-03-21 (1 days ago)
  InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Alpha amd64 (20210321)
  PackageArchitecture: all
  SourcePackage: tzdata
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iso-codes/+bug/1920987/+subscriptions

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

[Touch-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"

[Gunnar Hjalmarsson]

On 2021-03-23 17:32, Gunnar Hjalmarsson wrote:
> Then I tried with the groovy ISO, and the issue was present with that
> as well.

That was false alarm at least. Sorry.

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

Title:
  Ubiquity KDE crash on try/install and from live session with
  "malloc(): unaligned tcache chunk detected"

Status in mesa package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Confirmed
Status in mesa source package in Hirsute:
  Confirmed
Status in ubiquity source package in Hirsute:
  Confirmed

Bug description:
  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubiquity 21.04.11
  ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0
  Uname: Linux 5.11.0-11-generic x86_64
  ApportVersion: 2.20.11-0ubuntu60
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.460
  CurrentDesktop: KDE
  Date: Sun Mar 21 11:53:44 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed 
maybe-ubiquity quiet splash ---
  LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321)
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

  Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try
  install screen) and from the live session is crashing on launch or
  shortly after.

  Try/Install crash:

   Screen fails to start, or starts then crashes on any user action. The
  user is presented with:

  "Installation failed - The installer encountered an unrecoverable error.
  A desktop session will now be run so that you may investigate the problem or 
try installing again"

  Live session crash:

  The installer does not start from the desktop icon. Starting ubiquity
  from the terminal results in an "Aborted (core dumped)" message and
  nothing else.

  An example /var/log/installer/debug log from a session where both
  crashes were triggered is below.

   /var/log/installer/debug 

  Ubiquity 21.04.11
  TEXT If more than one person will use this computer, you can set up 
multiple accounts after installation.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT The name it uses when it talks to other computers.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT If more than one person will use this computer, you can set up 
multiple accounts after installation.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT The name it uses when it talks to other computers.
  QSocketNotifier: Invalid socket 17 and type 'Read', disabling...
  QSocketNotifier: Invalid socket 17 and type 'Write', disabling...
  QSocketNotifier: Invalid socket 17 and type 'Exception', disabling...
  Your console font configuration will be updated the next time your system
  boots. If you want to update it now, run 'setupcon' from a virtual console.
  update-initramfs is disabled since running on read-only media
  debconf: DbDriver "passwords" warning: could not open 
/var/cache/debconf/passwords.dat: Permission denied
  munmap_chunk(): invalid pointer
  Ubiquity 21.04.11
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu'
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu'
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu'
  TEXT If more than one person will use this computer, you can set up 
multiple accounts after installation.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT The name it uses when it talks to other computers.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  malloc(): unaligned tcache chunk detected

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

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

[Touch-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"

[Rik Mills]

** Changed in: mesa (Ubuntu Hirsute)
   Importance: Undecided => Critical

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

Title:
  Ubiquity KDE crash on try/install and from live session with
  "malloc(): unaligned tcache chunk detected"

Status in mesa package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Confirmed
Status in mesa source package in Hirsute:
  Confirmed
Status in ubiquity source package in Hirsute:
  Confirmed

Bug description:
  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubiquity 21.04.11
  ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0
  Uname: Linux 5.11.0-11-generic x86_64
  ApportVersion: 2.20.11-0ubuntu60
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.460
  CurrentDesktop: KDE
  Date: Sun Mar 21 11:53:44 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed 
maybe-ubiquity quiet splash ---
  LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321)
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

  Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try
  install screen) and from the live session is crashing on launch or
  shortly after.

  Try/Install crash:

   Screen fails to start, or starts then crashes on any user action. The
  user is presented with:

  "Installation failed - The installer encountered an unrecoverable error.
  A desktop session will now be run so that you may investigate the problem or 
try installing again"

  Live session crash:

  The installer does not start from the desktop icon. Starting ubiquity
  from the terminal results in an "Aborted (core dumped)" message and
  nothing else.

  An example /var/log/installer/debug log from a session where both
  crashes were triggered is below.

   /var/log/installer/debug 

  Ubiquity 21.04.11
  TEXT If more than one person will use this computer, you can set up 
multiple accounts after installation.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT The name it uses when it talks to other computers.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT If more than one person will use this computer, you can set up 
multiple accounts after installation.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT The name it uses when it talks to other computers.
  QSocketNotifier: Invalid socket 17 and type 'Read', disabling...
  QSocketNotifier: Invalid socket 17 and type 'Write', disabling...
  QSocketNotifier: Invalid socket 17 and type 'Exception', disabling...
  Your console font configuration will be updated the next time your system
  boots. If you want to update it now, run 'setupcon' from a virtual console.
  update-initramfs is disabled since running on read-only media
  debconf: DbDriver "passwords" warning: could not open 
/var/cache/debconf/passwords.dat: Permission denied
  munmap_chunk(): invalid pointer
  Ubiquity 21.04.11
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu'
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu'
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu'
  TEXT If more than one person will use this computer, you can set up 
multiple accounts after installation.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT The name it uses when it talks to other computers.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  malloc(): unaligned tcache chunk detected

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

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

[Touch-packages] [Bug 1874824] Re: pgrep reports error "cannot allocate" when run without stack limit

[William Wilson]

** Changed in: procps (Ubuntu Focal)
 Assignee: (unassigned) => William Wilson (jawn-smith)

** Changed in: procps (Ubuntu Groovy)
 Assignee: (unassigned) => William Wilson (jawn-smith)

** Changed in: procps (Ubuntu Hirsute)
 Assignee: (unassigned) => William Wilson (jawn-smith)

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

Title:
  pgrep reports error "cannot allocate" when run without stack limit

Status in procps package in Ubuntu:
  Triaged
Status in procps source package in Focal:
  Confirmed
Status in procps source package in Groovy:
  Confirmed
Status in procps source package in Hirsute:
  Triaged
Status in procps package in Debian:
  New

Bug description:
  If you have no stack limit (ulimit -S -s unlimited), any pgrep call
  will fail with an error:

  > pgrep vim
  pgrep: cannot allocate 4611686018427387903 bytes

  If you have a high stack limit (e.g. ulimit -S -s 50), pgrep is
  very slow:

  > time pgrep vim
  2196
  real 8.48s user 8.40s syst 0.07s busy 99% rmem 253444

  The relevant upstream bug report could be: 
https://gitlab.com/procps-ng/procps/-/issues/152
  Archlinux bug report: https://bugs.archlinux.org/task/66093

  procps:
Installed: 2:3.3.16-1ubuntu2
500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

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

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

[Touch-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"

[Rik Mills]

In reverse of my previous installation bisect, I can confirm that force
downgrading mesa to the previous major release results in these crashes
going away.

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

Title:
  Ubiquity KDE crash on try/install and from live session with
  "malloc(): unaligned tcache chunk detected"

Status in mesa package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Confirmed
Status in mesa source package in Hirsute:
  Confirmed
Status in ubiquity source package in Hirsute:
  Confirmed

Bug description:
  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubiquity 21.04.11
  ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0
  Uname: Linux 5.11.0-11-generic x86_64
  ApportVersion: 2.20.11-0ubuntu60
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.460
  CurrentDesktop: KDE
  Date: Sun Mar 21 11:53:44 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed 
maybe-ubiquity quiet splash ---
  LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321)
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

  Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try
  install screen) and from the live session is crashing on launch or
  shortly after.

  Try/Install crash:

   Screen fails to start, or starts then crashes on any user action. The
  user is presented with:

  "Installation failed - The installer encountered an unrecoverable error.
  A desktop session will now be run so that you may investigate the problem or 
try installing again"

  Live session crash:

  The installer does not start from the desktop icon. Starting ubiquity
  from the terminal results in an "Aborted (core dumped)" message and
  nothing else.

  An example /var/log/installer/debug log from a session where both
  crashes were triggered is below.

   /var/log/installer/debug 

  Ubiquity 21.04.11
  TEXT If more than one person will use this computer, you can set up 
multiple accounts after installation.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT The name it uses when it talks to other computers.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT If more than one person will use this computer, you can set up 
multiple accounts after installation.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT The name it uses when it talks to other computers.
  QSocketNotifier: Invalid socket 17 and type 'Read', disabling...
  QSocketNotifier: Invalid socket 17 and type 'Write', disabling...
  QSocketNotifier: Invalid socket 17 and type 'Exception', disabling...
  Your console font configuration will be updated the next time your system
  boots. If you want to update it now, run 'setupcon' from a virtual console.
  update-initramfs is disabled since running on read-only media
  debconf: DbDriver "passwords" warning: could not open 
/var/cache/debconf/passwords.dat: Permission denied
  munmap_chunk(): invalid pointer
  Ubiquity 21.04.11
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu'
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu'
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu'
  TEXT If more than one person will use this computer, you can set up 
multiple accounts after installation.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT The name it uses when it talks to other computers.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  malloc(): unaligned tcache chunk detected

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

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

[Touch-packages] [Bug 1920601] Re: Frequent test failures caused by networking issues on armhf runners

[Iain Lane]

Neat, can someone prepare a merge proposal for that?

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

Title:
  Frequent test failures caused by networking issues on armhf runners

Status in Auto Package Testing:
  Triaged
Status in apt package in Ubuntu:
  New

Bug description:
  Armhf runners have been known to have networking issues for years.

  A test of Focal's glibc SRU in Bileto shows that those issues did not
  go away. The glibc package itself is not expected to cause regression,
  this was just a run to confirm that.

  The test resuts are shown here:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_39a8dbb93caf4ec889f8a1b7f69885db/bileto-4017-excuses/2021-03-20_09:25:01/4017_focal_excuses.html

  Out of the 114 failed tests 58 containst the 'Connection timed out'
  string and only test logs from armhf contain that string:

  $ zgrep -l 'Connection timed out' ~/.cache/ubuntu-archive-tools/focal_*.gz 
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_atk1.0_20210318_182825_daefa.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_axe-demultiplexer_20210318_183430_6b008.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_bacula_20210318_190411_e3ad7.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_dialign-t_20210318_204503_b4d94.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_elisa-player_20210318_211129_9537d.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_fyba_20210318_181755_7731e.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_gcc-7_20210318_02_4d95c.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_gcc-8_20210318_221659_0e69f.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_golang-github-mailru-easyjson_20210318_231917_67888.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_gphoto2_20210318_200015_eb767.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_gtk+3.0_20210318_235412_db3e5.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_ipmitool_20210319_003215_d03da.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_kbibtex_20210319_004639_0ac1a.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_kcptun_20210318_193309_6dcd9.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libcache-memcached-getparserxs-perl_20210319_024051_33029.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libclass-load-xs-perl_20210319_025846_01419.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libconvert-uulib-perl_20210319_034852_21cd1.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libhat-trie_20210319_060826_fd334.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libhtml-tidy5-perl_20210319_070723_05fa8.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libimager-perl_20210319_063314_b19a2.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libipc-sharelite-perl_20210319_072246_0217e.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_liblexical-var-perl_20210319_070235_4c450.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libmarpa-r2-perl_20210319_073731_f7554.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libmemcached-libmemcached-perl_20210319_011004_dbca1.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libnet-ldns-perl_20210319_081224_49912.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libnet-pcap-perl_20210319_081606_4d772.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libparams-util-perl_20210319_084831_74d13.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libperlio-eol-perl_20210319_085645_97c6c.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libperlio-layers-perl_20210319_085937_8bd70.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libsass_20210319_092518_4db37.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libsdl-perl_20210319_095502_00c8c.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libtext-bibtex-perl_20210319_105027_abf4a.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libtext-hunspell-perl_20210319_103326_4a603.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libunix-syslog-perl_20210319_111403_f4374.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libwx-scintilla-perl_20210319_114818_a6aab.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libzstd_20210319_114737_0c4d9.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_mod-gearman_20210319_132205_d41ca.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_mrbayes_20210319_133633_10adb.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_octave-interval_20210319_151509_8348f.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_open-isns_20210319_161741_dffad.gz
  

[Touch-packages] [Bug 1920601] Re: Frequent test failures caused by networking issues on armhf runners

[Julian Andres Klode]

We can set Acquire::Retries in apt.conf like Debian does for debci now

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

Title:
  Frequent test failures caused by networking issues on armhf runners

Status in Auto Package Testing:
  Triaged
Status in apt package in Ubuntu:
  New

Bug description:
  Armhf runners have been known to have networking issues for years.

  A test of Focal's glibc SRU in Bileto shows that those issues did not
  go away. The glibc package itself is not expected to cause regression,
  this was just a run to confirm that.

  The test resuts are shown here:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_39a8dbb93caf4ec889f8a1b7f69885db/bileto-4017-excuses/2021-03-20_09:25:01/4017_focal_excuses.html

  Out of the 114 failed tests 58 containst the 'Connection timed out'
  string and only test logs from armhf contain that string:

  $ zgrep -l 'Connection timed out' ~/.cache/ubuntu-archive-tools/focal_*.gz 
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_atk1.0_20210318_182825_daefa.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_axe-demultiplexer_20210318_183430_6b008.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_bacula_20210318_190411_e3ad7.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_dialign-t_20210318_204503_b4d94.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_elisa-player_20210318_211129_9537d.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_fyba_20210318_181755_7731e.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_gcc-7_20210318_02_4d95c.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_gcc-8_20210318_221659_0e69f.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_golang-github-mailru-easyjson_20210318_231917_67888.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_gphoto2_20210318_200015_eb767.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_gtk+3.0_20210318_235412_db3e5.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_ipmitool_20210319_003215_d03da.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_kbibtex_20210319_004639_0ac1a.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_kcptun_20210318_193309_6dcd9.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libcache-memcached-getparserxs-perl_20210319_024051_33029.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libclass-load-xs-perl_20210319_025846_01419.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libconvert-uulib-perl_20210319_034852_21cd1.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libhat-trie_20210319_060826_fd334.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libhtml-tidy5-perl_20210319_070723_05fa8.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libimager-perl_20210319_063314_b19a2.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libipc-sharelite-perl_20210319_072246_0217e.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_liblexical-var-perl_20210319_070235_4c450.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libmarpa-r2-perl_20210319_073731_f7554.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libmemcached-libmemcached-perl_20210319_011004_dbca1.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libnet-ldns-perl_20210319_081224_49912.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libnet-pcap-perl_20210319_081606_4d772.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libparams-util-perl_20210319_084831_74d13.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libperlio-eol-perl_20210319_085645_97c6c.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libperlio-layers-perl_20210319_085937_8bd70.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libsass_20210319_092518_4db37.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libsdl-perl_20210319_095502_00c8c.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libtext-bibtex-perl_20210319_105027_abf4a.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libtext-hunspell-perl_20210319_103326_4a603.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libunix-syslog-perl_20210319_111403_f4374.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libwx-scintilla-perl_20210319_114818_a6aab.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libzstd_20210319_114737_0c4d9.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_mod-gearman_20210319_132205_d41ca.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_mrbayes_20210319_133633_10adb.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_octave-interval_20210319_151509_8348f.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_open-isns_20210319_161741_dffad.gz
  

[Touch-packages] [Bug 1920837] Re: apport bugs from official raspi or riscv images are not identified

[Launchpad Bug Tracker]

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

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

Title:
  apport bugs from official raspi or riscv images are not identified

Status in apport package in Ubuntu:
  In Progress

Bug description:
  It would be helpful if bugs reported from images for Raspberry Pi's or
  RISCV systems were tagged so that one could search for bugs from
  systems running those images e.g. 'raspi-image'.

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

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

[Touch-packages] [Bug 1920601] Re: Frequent test failures caused by networking issues on armhf runners

[Iain Lane]

I think both things would be fine. It's better to not surface these
problems to end users if we can, which we have a mechanism to do.

If and when apt gets a fix which works, then these retries will
automatically stop happening and we can remove the workarounds.

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

Title:
  Frequent test failures caused by networking issues on armhf runners

Status in Auto Package Testing:
  Triaged
Status in apt package in Ubuntu:
  New

Bug description:
  Armhf runners have been known to have networking issues for years.

  A test of Focal's glibc SRU in Bileto shows that those issues did not
  go away. The glibc package itself is not expected to cause regression,
  this was just a run to confirm that.

  The test resuts are shown here:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_39a8dbb93caf4ec889f8a1b7f69885db/bileto-4017-excuses/2021-03-20_09:25:01/4017_focal_excuses.html

  Out of the 114 failed tests 58 containst the 'Connection timed out'
  string and only test logs from armhf contain that string:

  $ zgrep -l 'Connection timed out' ~/.cache/ubuntu-archive-tools/focal_*.gz 
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_atk1.0_20210318_182825_daefa.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_axe-demultiplexer_20210318_183430_6b008.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_bacula_20210318_190411_e3ad7.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_dialign-t_20210318_204503_b4d94.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_elisa-player_20210318_211129_9537d.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_fyba_20210318_181755_7731e.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_gcc-7_20210318_02_4d95c.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_gcc-8_20210318_221659_0e69f.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_golang-github-mailru-easyjson_20210318_231917_67888.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_gphoto2_20210318_200015_eb767.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_gtk+3.0_20210318_235412_db3e5.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_ipmitool_20210319_003215_d03da.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_kbibtex_20210319_004639_0ac1a.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_kcptun_20210318_193309_6dcd9.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libcache-memcached-getparserxs-perl_20210319_024051_33029.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libclass-load-xs-perl_20210319_025846_01419.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libconvert-uulib-perl_20210319_034852_21cd1.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libhat-trie_20210319_060826_fd334.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libhtml-tidy5-perl_20210319_070723_05fa8.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libimager-perl_20210319_063314_b19a2.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libipc-sharelite-perl_20210319_072246_0217e.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_liblexical-var-perl_20210319_070235_4c450.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libmarpa-r2-perl_20210319_073731_f7554.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libmemcached-libmemcached-perl_20210319_011004_dbca1.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libnet-ldns-perl_20210319_081224_49912.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libnet-pcap-perl_20210319_081606_4d772.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libparams-util-perl_20210319_084831_74d13.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libperlio-eol-perl_20210319_085645_97c6c.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libperlio-layers-perl_20210319_085937_8bd70.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libsass_20210319_092518_4db37.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libsdl-perl_20210319_095502_00c8c.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libtext-bibtex-perl_20210319_105027_abf4a.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libtext-hunspell-perl_20210319_103326_4a603.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libunix-syslog-perl_20210319_111403_f4374.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libwx-scintilla-perl_20210319_114818_a6aab.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libzstd_20210319_114737_0c4d9.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_mod-gearman_20210319_132205_d41ca.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_mrbayes_20210319_133633_10adb.gz
  

[Touch-packages] [Bug 1917780] Re: initramfs-tools does not include fsck binaries in the initrd if all mount pass are 0

[Dimitri John Ledkov]

** Description changed:

- initramfs-tools does not include fsck in initrd if MNT_PASS equals zero
- in the fstab entries.
+ [Impact]
+ 
+  * initramfs-tools does not include fsck in initrd if MNT_PASS equals
+ zero in the fstab entries.
  
  This has lead to the following situation :
  when dropping to initramfs shell during boot due to fs errors, we are not 
able to run fsck manually
  because it is not included in initrd.
  
  fsck should be included regardless of the MNT_PASS value.
+ 
+ [Test Plan]
+ 
+  * change /etc/fstab with PASSNO set to 0 for all entries
+  * update-initramfs -u
+  * lsinitramfs that is just generated
+  * observe that it includes fsck utilities for the filesystems in /etc/fstab. 
I.e. fsck.ext4 e2fsck must exist
+ 
+ 
+ [Where problems could occur]
+ 
+  * The initramfs size will increase slightly upon upgrade, for the same
+ initramfs-tools default options & kernel. However, one can control and
+ remove fsck binaries (or include more of them) by setting FSTYPE
+ variable in the initramfs settings.

** Changed in: initramfs-tools (Ubuntu)
   Status: In Progress => Fix Committed

** Changed in: initramfs-tools (Ubuntu)
 Assignee: Ioanna Alifieraki (joalif) => (unassigned)

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

Title:
  initramfs-tools does not include fsck binaries in the initrd if all
  mount pass are 0

Status in initramfs-tools package in Ubuntu:
  Fix Committed

Bug description:
  [Impact]

   * initramfs-tools does not include fsck in initrd if MNT_PASS equals
  zero in the fstab entries.

  This has lead to the following situation :
  when dropping to initramfs shell during boot due to fs errors, we are not 
able to run fsck manually
  because it is not included in initrd.

  fsck should be included regardless of the MNT_PASS value.

  [Test Plan]

   * change /etc/fstab with PASSNO set to 0 for all entries
   * update-initramfs -u
   * lsinitramfs that is just generated
   * observe that it includes fsck utilities for the filesystems in /etc/fstab. 
I.e. fsck.ext4 e2fsck must exist

  
  [Where problems could occur]

   * The initramfs size will increase slightly upon upgrade, for the
  same initramfs-tools default options & kernel. However, one can
  control and remove fsck binaries (or include more of them) by setting
  FSTYPE variable in the initramfs settings.

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

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

[Touch-packages] [Bug 1920987] Re: IANA tzdata file format cannot represent different country code for a given timezone in different time periods [ i.e. Europe/Simferopol country code changes ]

[Alexander]

That is, she says... "fuck you all, the United States has a different
opinion on this". And it does this not only for the residents of the
Crimean Peninsula, but also for the residents of the Russian Federation
as a whole. You are wrong to think that this does not affect Ubuntu. It
affects the whole world.

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

Title:
  IANA tzdata file format cannot represent different country code for a
  given timezone in different time periods [ i.e. Europe/Simferopol
  country code changes ]

Status in tzdata package in Ubuntu:
  Opinion

Bug description:
  Europe/Simferopol,  Crimea is RUSSIA

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: tzdata 2021a-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0
  Uname: Linux 5.11.0-11-generic x86_64
  ApportVersion: 2.20.11-0ubuntu60
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Tue Mar 23 21:44:56 2021
  InstallationDate: Installed on 2021-03-21 (1 days ago)
  InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Alpha amd64 (20210321)
  PackageArchitecture: all
  SourcePackage: tzdata
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 559548] Re: fontconfig-config breaks monospace and diacritics

[madbiologist]

On Ubuntu 18.04.5, the output of fc-match Monospace is

DejaVuSansMono.ttf: "DejaVu Sans Mono" "Book"

Can you confirm this bug no longer occurs?

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

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

Title:
  fontconfig-config breaks monospace and diacritics

Status in fontconfig package in Ubuntu:
  Incomplete

Bug description:
  Besides being redundant (see 
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/387848)
  45-latin.conf and 60-latin.conf have contradictory aliases settings. The 
superseding one, 45-latin.conf is breaking the 'monospace' alias font when 
combining diacritics are being used by prioritizing Bitstream Vera Sans Mono 
over DejaVu Sans Mono.
  DejaVu Sans Mono has characters and OpenType features Bitsteam Vera Sans Mono 
doesn't have. It doesn't make sense to prioritize Vera. This breaks things like 
"e" + U+0301, where 'e' comes from Vera and U+0301 comes from DejaVu.

  see https://bugzilla.mozilla.org/show_bug.cgi?id=556715 or
  https://bug556715.bugzilla.mozilla.org/attachment.cgi?id=436657 for
  example.

  45-latin.conf has
  
  Bitstream Vera Sans Mono
  DejaVu Sans Mono
  Liberation Mono
  Inconsolata
  Courier New
  Courier
  Andale Mono
  Luxi Mono
  Cumberland AMT
  Cumberland
  Nimbus Mono L
  monospace
  

  60-latin.conf has
  
  monospace
  
  DejaVu Sans Mono
  Bitstream Vera Sans Mono
  Inconsolata
  Andale Mono
  Courier New
  Cumberland AMT
  Luxi Mono
  Nimbus Mono L
  Courier
  
  

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

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

[Touch-packages] [Bug 1921135] Re: package linux-image-5.8.0-45-generic 5.8.0-45.51~20.04.1+1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Apport retracing service]

** Package changed: ubuntu => initramfs-tools (Ubuntu)

** Tags removed: need-duplicate-check

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

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

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  no further information

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.8.0-45-generic 5.8.0-45.51~20.04.1+1
  ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-45-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Thu Mar 18 10:34:46 2021
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2021-01-23 (60 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.4
  SourcePackage: initramfs-tools
  Title: package linux-image-5.8.0-45-generic 5.8.0-45.51~20.04.1+1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1921136] Re: package initramfs-tools 0.136ubuntu6.4 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1

[Apport retracing service]

** Package changed: ubuntu => initramfs-tools (Ubuntu)

** Tags removed: need-duplicate-check

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

Title:
  package initramfs-tools 0.136ubuntu6.4 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  no further information

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6.4
  ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-45-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Mar 24 15:49:31 2021
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2021-01-23 (60 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.4
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.136ubuntu6.4 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1920987] Re: IANA tzdata file format cannot represent different country code for a given timezone in different time periods [ i.e. Europe/Simferopol country code changes ]

[Alexander]

96 percent of the population of Crimea voted for joining the Russian
Federation in the conditions of the overthrow of the legitimate
president of the country, at that time Crimea had the status of the
Autonomous Republic of Crimea. Today it is the Republic of Crimea, which
no longer has the status of autonomy, because it is part of the Russian
Federation. When selecting the location of the city of Simferopol,
Ubuntu adds the UA domain.

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

Title:
  IANA tzdata file format cannot represent different country code for a
  given timezone in different time periods [ i.e. Europe/Simferopol
  country code changes ]

Status in tzdata package in Ubuntu:
  Opinion

Bug description:
  Europe/Simferopol,  Crimea is RUSSIA

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: tzdata 2021a-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0
  Uname: Linux 5.11.0-11-generic x86_64
  ApportVersion: 2.20.11-0ubuntu60
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Tue Mar 23 21:44:56 2021
  InstallationDate: Installed on 2021-03-21 (1 days ago)
  InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Alpha amd64 (20210321)
  PackageArchitecture: all
  SourcePackage: tzdata
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

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

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

no further information

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: linux-image-5.8.0-45-generic 5.8.0-45.51~20.04.1+1
ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-45-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
Date: Thu Mar 18 10:34:46 2021
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
InstallationDate: Installed on 2021-01-23 (60 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.4
SourcePackage: initramfs-tools
Title: package linux-image-5.8.0-45-generic 5.8.0-45.51~20.04.1+1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal need-duplicate-check
-- 
package linux-image-5.8.0-45-generic 5.8.0-45.51~20.04.1+1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
https://bugs.launchpad.net/bugs/1921135
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to initramfs-tools in Ubuntu.

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

[Touch-packages] [Bug 1921136] [NEW] package initramfs-tools 0.136ubuntu6.4 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

no further information

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: initramfs-tools 0.136ubuntu6.4
ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-45-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
Date: Wed Mar 24 15:49:31 2021
ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2021-01-23 (60 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
PackageArchitecture: all
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.4
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.136ubuntu6.4 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package focal need-duplicate-check
-- 
package initramfs-tools 0.136ubuntu6.4 failed to install/upgrade: installed 
initramfs-tools package post-installation script subprocess returned error exit 
status 1
https://bugs.launchpad.net/bugs/1921136
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to initramfs-tools in Ubuntu.

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

[Touch-packages] [Bug 1920601] Re: Frequent test failures caused by networking issues on armhf runners

[Balint Reczey]

@laney IMO 'Confirmed' would be the accurate state since the root cause
is not known. I used to be a proponent of adding more retry strings but
they also cause retry lool of test failures. I think APT should retry on
timeouts instead, thus adding APT as affected package.

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

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

Title:
  Frequent test failures caused by networking issues on armhf runners

Status in Auto Package Testing:
  Triaged
Status in apt package in Ubuntu:
  New

Bug description:
  Armhf runners have been known to have networking issues for years.

  A test of Focal's glibc SRU in Bileto shows that those issues did not
  go away. The glibc package itself is not expected to cause regression,
  this was just a run to confirm that.

  The test resuts are shown here:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_39a8dbb93caf4ec889f8a1b7f69885db/bileto-4017-excuses/2021-03-20_09:25:01/4017_focal_excuses.html

  Out of the 114 failed tests 58 containst the 'Connection timed out'
  string and only test logs from armhf contain that string:

  $ zgrep -l 'Connection timed out' ~/.cache/ubuntu-archive-tools/focal_*.gz 
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_atk1.0_20210318_182825_daefa.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_axe-demultiplexer_20210318_183430_6b008.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_bacula_20210318_190411_e3ad7.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_dialign-t_20210318_204503_b4d94.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_elisa-player_20210318_211129_9537d.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_fyba_20210318_181755_7731e.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_gcc-7_20210318_02_4d95c.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_gcc-8_20210318_221659_0e69f.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_golang-github-mailru-easyjson_20210318_231917_67888.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_gphoto2_20210318_200015_eb767.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_gtk+3.0_20210318_235412_db3e5.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_ipmitool_20210319_003215_d03da.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_kbibtex_20210319_004639_0ac1a.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_kcptun_20210318_193309_6dcd9.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libcache-memcached-getparserxs-perl_20210319_024051_33029.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libclass-load-xs-perl_20210319_025846_01419.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libconvert-uulib-perl_20210319_034852_21cd1.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libhat-trie_20210319_060826_fd334.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libhtml-tidy5-perl_20210319_070723_05fa8.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libimager-perl_20210319_063314_b19a2.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libipc-sharelite-perl_20210319_072246_0217e.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_liblexical-var-perl_20210319_070235_4c450.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libmarpa-r2-perl_20210319_073731_f7554.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libmemcached-libmemcached-perl_20210319_011004_dbca1.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libnet-ldns-perl_20210319_081224_49912.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libnet-pcap-perl_20210319_081606_4d772.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libparams-util-perl_20210319_084831_74d13.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libperlio-eol-perl_20210319_085645_97c6c.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libperlio-layers-perl_20210319_085937_8bd70.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libsass_20210319_092518_4db37.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libsdl-perl_20210319_095502_00c8c.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libtext-bibtex-perl_20210319_105027_abf4a.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libtext-hunspell-perl_20210319_103326_4a603.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libunix-syslog-perl_20210319_111403_f4374.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libwx-scintilla-perl_20210319_114818_a6aab.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_libzstd_20210319_114737_0c4d9.gz
  
/home/rbalint/.cache/ubuntu-archive-tools/focal_armhf_mod-gearman_20210319_132205_d41ca.gz
  

[Touch-packages] [Bug 1804719] Re: package lvm2 2.02.176-4.1ubuntu3 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1

[Launchpad Bug Tracker]

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

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

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

Title:
  package lvm2 2.02.176-4.1ubuntu3 failed to install/upgrade: installed
  lvm2 package post-installation script subprocess returned error exit
  status 1

Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  This is what do I do on my terminal:

  
  $ sudo apt-get install qemu-kvm libvirt-bin ubuntu-vm-builder bridge-utils
  [sudo] password for septian: 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  bridge-utils is already the newest version (1.5-15ubuntu1).
  ubuntu-vm-builder is already the newest version (0.12.4+bzr494-0ubuntu1).
  libvirt-bin is already the newest version (4.0.0-1ubuntu8.5).
  qemu-kvm is already the newest version (1:2.11+dfsg-1ubuntu7.7).
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
  1 not fully installed or removed.
  After this operation, 0 B of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Setting up lvm2 (2.02.176-4.1ubuntu3) ...
  update-initramfs: deferring update (trigger activated)
  Failed to restart lvm2-lvmetad.service: Unit lvm2-lvmetad.socket is masked.
  invoke-rc.d: initscript lvm2-lvmetad, action "restart" failed.
  ● lvm2-lvmetad.service - LVM2 metadata daemon
 Loaded: loaded (/lib/systemd/system/lvm2-lvmetad.service; static; vendor 
preset: enabled)
 Active: inactive (dead)
   Docs: man:lvmetad(8)
  dpkg: error processing package lvm2 (--configure):
   installed lvm2 package post-installation script subprocess returned error 
exit status 1
  Processing triggers for initramfs-tools (0.130ubuntu3.5) ...
  update-initramfs: Generating /boot/initrd.img-4.15.0-39-generic
  Errors were encountered while processing:
   lvm2
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: lvm2 2.02.176-4.1ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  Date: Fri Nov 23 06:47:21 2018
  ErrorMessage: installed lvm2 package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2018-11-19 (3 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: lvm2
  Title: package lvm2 2.02.176-4.1ubuntu3 failed to install/upgrade: installed 
lvm2 package post-installation script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1921108] [NEW] blkid reports disk as zfs_member if it has a zfs_member partition

[James Dingwall]

Public bug reported:

Upstream bug report: https://github.com/karelzak/util-linux/issues/918

In summary if a disk partition used for zfs is at the end of the disk
then libblkid identifies the _whole_ disk as a zfs member which causes
udev information returned for other partitions to be incorrect.  blkid
used directly reports the correct information.

# udevadm info /dev/sdb | grep ID_FS_TYPE
E: ID_FS_TYPE=zfs_member

# udevadm info /dev/sdb3 | grep ID_FS_TYPE
E: ID_FS_TYPE=zfs_member

# blkid /dev/sdb3
/dev/sdb3: UUID="4dcL2M-osmP-8MNF-kB3G-VobX-m1UX-aWGYk1" TYPE="LVM2_member" 
PARTLABEL="bootvg" PARTUUID="3abeebf9-9699-49c1-9e6e-039afb3b04a2"

# gdisk -l /dev/sdb
GPT fdisk (gdisk) version 1.0.3

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present

Found valid GPT with protective MBR; using GPT.
Disk /dev/sdb: 3907029168 sectors, 1.8 TiB
Model: HUS722T2TALA600 
Sector size (logical/physical): 512/512 bytes
Disk identifier (GUID): 45A8D0F8-D347-4D68-8DA1-72CDB2CCAC38
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 3907029134
Partitions will be aligned on 2048-sector boundaries
Total free space is 4205 sectors (2.1 MiB)

Number  Start (sector)End (sector)  Size   Code  Name
   120484095   1024.0 KiB  EF02  BIOSBOOT
   24096 2099199   1023.0 MiB  EF00  EFI_DATA
   3 2099200 3147775   512.0 MiB   8E00  vg1
   4 3147776 7342079   2.0 GiB 8E00  vg2
   5 734208011536383   2.0 GiB 0700  recovery
   611536384  3907029133   1.8 TiB BF01  ztank


This is fixed for me by rebuilding the util-linux patch and adding commit 
f6e182078a3f05af3ce3b5e5a2d1956d4b9677e2 from the upstream git tree.  Once that 
is applied:

# udevadm info /dev/sdb | grep ID_FS_TYPE
(no output)

# udevadm info /dev/sdb3 | grep ID_FS_TYPE
E: ID_FS_TYPE=LVM2_member

This has been observed on Ubuntu bionic.

$ apt-cache policy util-linux
util-linux:
  Installed: 2.31.1-0.4ubuntu3.7
  Candidate: 2.31.1-0.4ubuntu3.7
  Version table:
 *** 2.31.1-0.4ubuntu3.7 500
500 http://gb.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
 2.31.1-0.4ubuntu3 500
500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.5 LTS
Release:18.04
Codename:   bionic

On Ubuntu focal an ID_FS_TYPE is also incorrectly reported for the whole
disk but the information for individual partitions seems to be correct
although I don't have a system with same partition table from the
example.  I haven't yet tried with the util-linux patch in focal.

** Affects: util-linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: bionic focal

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

Title:
  blkid reports disk as zfs_member if it has a zfs_member partition

Status in util-linux package in Ubuntu:
  New

Bug description:
  Upstream bug report: https://github.com/karelzak/util-linux/issues/918

  In summary if a disk partition used for zfs is at the end of the disk
  then libblkid identifies the _whole_ disk as a zfs member which causes
  udev information returned for other partitions to be incorrect.  blkid
  used directly reports the correct information.

  # udevadm info /dev/sdb | grep ID_FS_TYPE
  E: ID_FS_TYPE=zfs_member

  # udevadm info /dev/sdb3 | grep ID_FS_TYPE
  E: ID_FS_TYPE=zfs_member

  # blkid /dev/sdb3
  /dev/sdb3: UUID="4dcL2M-osmP-8MNF-kB3G-VobX-m1UX-aWGYk1" TYPE="LVM2_member" 
PARTLABEL="bootvg" PARTUUID="3abeebf9-9699-49c1-9e6e-039afb3b04a2"

  # gdisk -l /dev/sdb
  GPT fdisk (gdisk) version 1.0.3

  Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present

  Found valid GPT with protective MBR; using GPT.
  Disk /dev/sdb: 3907029168 sectors, 1.8 TiB
  Model: HUS722T2TALA600 
  Sector size (logical/physical): 512/512 bytes
  Disk identifier (GUID): 45A8D0F8-D347-4D68-8DA1-72CDB2CCAC38
  Partition table holds up to 128 entries
  Main partition table begins at sector 2 and ends at sector 33
  First usable sector is 34, last usable sector is 3907029134
  Partitions will be aligned on 2048-sector boundaries
  Total free space is 4205 sectors (2.1 MiB)

  Number  Start (sector)End (sector)  Size   Code  Name
 120484095   1024.0 KiB  EF02  BIOSBOOT
 24096 2099199   1023.0 MiB  EF00  EFI_DATA
 3 2099200 3147775   512.0 MiB   8E00  vg1
 4 3147776 7342079   

[Touch-packages] [Bug 388605] Re: [MIR] rsyslog

[Christian Ehrhardt ]

Thanks for the pre-checks Andreas,
- with my MIR-Team-hat I agree that it does not need a new re-evaluation for 
this.
- with my Server-Team-hat I have prepared a seed change for Hirsute to 
implement it.
  => 
https://code.launchpad.net/~paelzer/ubuntu-seeds/+git/platform/+merge/400101

Once we have agreed and completed it there we can discuss if/how-far back (in 
terms of releases) we want to apply the change.
Maybe you could join standup today  to have a talk about the case with the Team?

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

Title:
  [MIR] rsyslog

Status in rsyslog package in Ubuntu:
  Fix Released
Status in rsyslog source package in Bionic:
  New
Status in rsyslog source package in Focal:
  New
Status in rsyslog source package in Groovy:
  New
Status in rsyslog source package in Hirsute:
  Fix Released

Bug description:
  Binary package hint: rsyslog

  We want to make rsyslog the new default syslogger.

  See https://wiki.ubuntu.com/MainInclusionReport/rsyslog

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

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

[Touch-packages] [Bug 388605] Re: [MIR] rsyslog

[Launchpad Bug Tracker]

** Merge proposal linked:
   https://code.launchpad.net/~paelzer/ubuntu-seeds/+git/platform/+merge/400101

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

Title:
  [MIR] rsyslog

Status in rsyslog package in Ubuntu:
  Fix Released
Status in rsyslog source package in Bionic:
  New
Status in rsyslog source package in Focal:
  New
Status in rsyslog source package in Groovy:
  New
Status in rsyslog source package in Hirsute:
  Fix Released

Bug description:
  Binary package hint: rsyslog

  We want to make rsyslog the new default syslogger.

  See https://wiki.ubuntu.com/MainInclusionReport/rsyslog

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

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

[Touch-packages] [Bug 1920987] Re: Europe/Simferopol, Crimea is RUSSIA

[Dimitri John Ledkov]

The upstream IANA tzdata file format is very restrictive and cannot
change and reflect country codes correctly, across correct historical
dates.

>From "europe" file:
Zone Europe/Simferopol   2:16:24 -  LMT 1880
 2:16   -   SMT 1924 May  2 # Simferopol Mean T
 2:00   -   EET 1930 Jun 21
 3:00   -   MSK 1941 Nov
 1:00   C-Eur   CE%sT   1944 Apr 13
 3:00   Russia  MSK/MSD 1990
 3:00   -   MSK 1990 Jul  1  2:00
 2:00   -   EET 1992
# Central Crimea used Moscow time 1994/1997.
#
# From Paul Eggert (2006-03-22):
# The _Economist_ (1994-05-28, p 45) reports that central Crimea switched
# from Kiev to Moscow time sometime after the January 1994 elections.
# Shanks (1999) says "date of change uncertain", but implies that it happened
# sometime between the 1994 DST switches.  Shanks & Pottenger simply say
# 1994-09-25 03:00, but that can't be right.  For now, guess it
# changed in May.
 2:00   E-Eur   EE%sT   1994 May
# From IATA SSIM (1994/1997), which also says that Kerch is still like Kiev.
 3:00   E-Eur   MSK/MSD 1996 Mar 31  0:00s
 3:00   1:00MSD 1996 Oct 27  3:00s
# IATA SSIM (1997-09) says Crimea switched to EET/EEST.
# Assume it happened in March by not changing the clocks.
 3:00   Russia  MSK/MSD 1997
 3:00   -   MSK 1997 Mar lastSun  1:00u
# From Alexander Krivenyshev (2014-03-17):
# time change at 2:00 (2am) on March 30, 2014
# https://vz.ru/news/2014/3/17/677464.html
# From Paul Eggert (2014-03-30):
# Simferopol and Sevastopol reportedly changed their central town clocks
# late the previous day, but this appears to have been ceremonial
# and the discrepancies are small enough to not worry about.
 2:00   EU  EE%sT   2014 Mar 30  2:00
 4:00   -   MSK 2014 Oct 26  2:00s
 3:00   -   MSK

The above defines which timezone was used when in Crimea.

But the mapping from Europe/Simferopol => country code [UA,RU] as appropriate 
for a given time period is not possible in the zone.tab file. Hence it 
currently stayed with:
./zone.tab:UA   +4457+03406 Europe/Simferopol   Crimea

There is a newer format in zone1970.tab file which says:
./zone1970.tab:RU,UA+4457+03406 Europe/Simferopol   Crimea

But that is not helpful, as it lists two countries. And it still doesn't
map country codes to the correct time periods.

It almost feels like we either need a new country code for Crimea to
explain that depending which year one is in, it should be one or the
other country code. Or we need to extend the zore1970.tab format similar
to the file format of europe format such that country codes can be
specified for every relevant time period.

So to get where you want to be, IANA needs to create a new tzdata format
and for everyone to switch to it. I guess that would need to be
requested via Discussions mailing list at IANA - see
https://www.iana.org/time-zones

There is nothing in particular that Ubuntu can do to fix tzdata. As
disagreement across other users of tzdata across the network can
introduce interoperability bugs.

My only recommendation is to use Europe/Kiev or Europe/Moscow zones,
which have the correct country code mappings for the most recent
decades.

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

Title:
  IANA tzdata file format cannot represent different country code for a
  given timezone in different time periods [ i.e. Europe/Simferopol
  country code changes ]

Status in tzdata package in Ubuntu:
  Opinion

Bug description:
  Europe/Simferopol,  Crimea is RUSSIA

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: tzdata 2021a-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0
  Uname: Linux 5.11.0-11-generic x86_64
  ApportVersion: 2.20.11-0ubuntu60
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Tue Mar 23 21:44:56 2021
  InstallationDate: Installed on 2021-03-21 (1 days ago)
  InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Alpha amd64 (20210321)
  PackageArchitecture: all
  SourcePackage: tzdata
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1920987] Re: IANA tzdata file format cannot represent different country code for a given timezone in different time periods [ i.e. Europe/Simferopol country code changes ]

[Dimitri John Ledkov]

Setting the status of the bug report to Opinion, as it doesn't fit the
scope of Ubuntu project. It has to be fixed by IANA in upstream releases
of tzdata. Once they come up with a better solution in the file format,
the bug can change to confirmed to be integrated in Ubuntu.

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

Title:
  IANA tzdata file format cannot represent different country code for a
  given timezone in different time periods [ i.e. Europe/Simferopol
  country code changes ]

Status in tzdata package in Ubuntu:
  Opinion

Bug description:
  Europe/Simferopol,  Crimea is RUSSIA

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: tzdata 2021a-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0
  Uname: Linux 5.11.0-11-generic x86_64
  ApportVersion: 2.20.11-0ubuntu60
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Tue Mar 23 21:44:56 2021
  InstallationDate: Installed on 2021-03-21 (1 days ago)
  InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Alpha amd64 (20210321)
  PackageArchitecture: all
  SourcePackage: tzdata
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1920987] Re: Europe/Simferopol, Crimea is RUSSIA

[Dimitri John Ledkov]

Is there anything in particular about all the other packages that you
marked them as affected? I suspect that they all use Ubuntu's provided
tzdata as the source of information, and hence they will all be
reflecting simply whatever tzdata tells them. Hence any changes will be
automatically reflected in them, if and when, tzdata is improved.

Would it be ok to close all the other tasks, whilst keeping tzdata one
open?

** Summary changed:

- Europe/Simferopol,Crimea is RUSSIA
+ IANA tzdata file format cannot represent different country code for a given 
timezone in different time periods [ i.e. Europe/Simferopol country code 
changes ]

** No longer affects: ayatana-indicator-datetime (Ubuntu)

** No longer affects: evolution-ews (Ubuntu)

** No longer affects: gnome-clocks (Ubuntu)

** No longer affects: gnome-control-center (Ubuntu)

** No longer affects: libgweather (Ubuntu)

** No longer affects: liblangtag (Ubuntu)

** No longer affects: mate-control-center (Ubuntu)

** No longer affects: mate-panel (Ubuntu)

** No longer affects: publicsuffix (Ubuntu)

** Changed in: tzdata (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: tzdata (Ubuntu)
   Status: Confirmed => Opinion

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

Title:
  IANA tzdata file format cannot represent different country code for a
  given timezone in different time periods [ i.e. Europe/Simferopol
  country code changes ]

Status in tzdata package in Ubuntu:
  Opinion

Bug description:
  Europe/Simferopol,  Crimea is RUSSIA

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: tzdata 2021a-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0
  Uname: Linux 5.11.0-11-generic x86_64
  ApportVersion: 2.20.11-0ubuntu60
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Tue Mar 23 21:44:56 2021
  InstallationDate: Installed on 2021-03-21 (1 days ago)
  InstallationMedia: Ubuntu-MATE 21.04 "Hirsute Hippo" - Alpha amd64 (20210321)
  PackageArchitecture: all
  SourcePackage: tzdata
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1919404] Re: Desktop icon shadows are broken at scale 200%

[Daniel van Vugt]

Fix proposed to GTK:
https://gitlab.gnome.org/GNOME/gtk/-/merge_requests/3343

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

** Changed in: gtk+3.0 (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

** Changed in: gtk+3.0 (Ubuntu)
   Importance: Undecided => Medium

** Changed in: gtk+3.0 (Ubuntu)
   Status: New => In Progress

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

Title:
  Desktop icon shadows are broken at scale 200%

Status in Gnome Shell Extension Desktop Icons Ng:
  Unknown
Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu:
  In Progress
Status in gtk+3.0 package in Ubuntu:
  In Progress

Bug description:
  Desktop icon shadows are broken at scale 200%.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell-extension-desktop-icons-ng/+bug/1919404/+subscriptions

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

[Touch-packages] [Bug 1921064] Re: wget 1.19.4 corrupts large downloaded files

[Tony Travis]

Please note: I ran "ubuntu-bug" on the system running "wget" 1.19.4
under Ubuntu-MATE 18.04 LTS, but I reported the bug using Firefox
running under Ubuntu-MATE 20.04 LTS

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

Title:
  wget 1.19.4 corrupts large downloaded files

Status in wget package in Ubuntu:
  New

Bug description:
  In normal use, downloading small files, "wget" 1.19.4 works correctly
  under Ubuntu-MATE 18.04 LTS. The length and md5sums of downloaded
  files are correct. However, when attempting to download a larger 16GB
  .tar.gz file the length of the original file on the server is
  16336802611 bytes, but the downloaded file is 16463139667 bytes and
  the computed md5sum of the file does not match the stored md5sum of
  the file on the server:

  ionice -c idle wget --no-check-certificate 
ftp://ftp.ncbi.nih.gov/snp/organisms/human_9606_b151_GRCh38p7/VCF/All_20180418.vcf.gz
  --2021-03-23 16:22:12--  
ftp://ftp.ncbi.nih.gov/snp/organisms/human_9606_b151_GRCh38p7/VCF/All_20180418.vcf.gz
 => ‘All_20180418.vcf.gz’
  Resolving ftp.ncbi.nih.gov (ftp.ncbi.nih.gov)... 130.14.250.11, 
130.14.250.13, 2607:f220:41e:250::11, ...
  Connecting to ftp.ncbi.nih.gov (ftp.ncbi.nih.gov)|130.14.250.11|:21... 
connected.
  Logging in as anonymous ... Logged in!
  ==> SYST ... done.==> PWD ... done.
  ==> TYPE I ... done.  ==> CWD (1) /snp/organisms/human_9606_b151_GRCh38p7/VCF 
... done.
  ==> SIZE All_20180418.vcf.gz ... 16336802611
  ==> PASV ... done.==> RETR All_20180418.vcf.gz ... done.
  Length: 16336802611 (15G) (unauthoritative)

  All_20180418.vcf.gz
  
100%[>]
  15.33G   939KB/sin 2h 7m

  2021-03-23 18:29:25 (2.06 MB/s) - ‘All_20180418.vcf.gz’ saved
  [16463139667]

  Repeating the same download using "wget" 1.20.3 under Ubuntu-MATE
  20.04 LTS, the file length and md5sum are correct.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: wget 1.19.4-1ubuntu2.2
  ProcVersionSignature: Ubuntu 5.4.0-66.74~18.04.2-generic 5.4.86
  Uname: Linux 5.4.0-66-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.9-0ubuntu7.23
  Architecture: amd64
  Date: Wed Mar 24 02:32:49 2021
  InstallationDate: Installed on 2020-08-03 (232 days ago)
  InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 
(20200423)
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: wget
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"

[Bob H]

I should repeat, I am performing the installation using 'Safe Graphics'
mode.

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

Title:
  Ubiquity KDE crash on try/install and from live session with
  "malloc(): unaligned tcache chunk detected"

Status in mesa package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Confirmed
Status in mesa source package in Hirsute:
  Confirmed
Status in ubiquity source package in Hirsute:
  Confirmed

Bug description:
  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubiquity 21.04.11
  ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0
  Uname: Linux 5.11.0-11-generic x86_64
  ApportVersion: 2.20.11-0ubuntu60
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.460
  CurrentDesktop: KDE
  Date: Sun Mar 21 11:53:44 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed 
maybe-ubiquity quiet splash ---
  LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321)
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

  Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try
  install screen) and from the live session is crashing on launch or
  shortly after.

  Try/Install crash:

   Screen fails to start, or starts then crashes on any user action. The
  user is presented with:

  "Installation failed - The installer encountered an unrecoverable error.
  A desktop session will now be run so that you may investigate the problem or 
try installing again"

  Live session crash:

  The installer does not start from the desktop icon. Starting ubiquity
  from the terminal results in an "Aborted (core dumped)" message and
  nothing else.

  An example /var/log/installer/debug log from a session where both
  crashes were triggered is below.

   /var/log/installer/debug 

  Ubiquity 21.04.11
  TEXT If more than one person will use this computer, you can set up 
multiple accounts after installation.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT The name it uses when it talks to other computers.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT If more than one person will use this computer, you can set up 
multiple accounts after installation.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT The name it uses when it talks to other computers.
  QSocketNotifier: Invalid socket 17 and type 'Read', disabling...
  QSocketNotifier: Invalid socket 17 and type 'Write', disabling...
  QSocketNotifier: Invalid socket 17 and type 'Exception', disabling...
  Your console font configuration will be updated the next time your system
  boots. If you want to update it now, run 'setupcon' from a virtual console.
  update-initramfs is disabled since running on read-only media
  debconf: DbDriver "passwords" warning: could not open 
/var/cache/debconf/passwords.dat: Permission denied
  munmap_chunk(): invalid pointer
  Ubiquity 21.04.11
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu'
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu'
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu'
  TEXT If more than one person will use this computer, you can set up 
multiple accounts after installation.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT The name it uses when it talks to other computers.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  malloc(): unaligned tcache chunk detected

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

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

[Touch-packages] [Bug 1920665] Re: Ubiquity KDE crash on try/install and from live session with "malloc(): unaligned tcache chunk detected"

[Bob H]

I have attempted to install from

kubuntu hirsute daily build 21-03-22
kubuntu hirsute daily build 21-03-23
kubuntu hirsute daily build 21-03-24

each version the insstallation fails.

Incidentally I noticed another change.

While the daily builds were installing correctly a procedure appeared on
screen, this no longer happens.

After booting the installation media, a self check ran with an on screen
display showing the stages the check was passing through.

The word Kubuntu appeared on screen and this display was beneath it.

Since the installation began to fail, the file check no longer shows and
although the word Kubuntu appears it disappears shortly after.

As it changed when installation began to fail, maybe there is a
connection?

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

Title:
  Ubiquity KDE crash on try/install and from live session with
  "malloc(): unaligned tcache chunk detected"

Status in mesa package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Confirmed
Status in mesa source package in Hirsute:
  Confirmed
Status in ubiquity source package in Hirsute:
  Confirmed

Bug description:
  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: ubiquity 21.04.11
  ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0
  Uname: Linux 5.11.0-11-generic x86_64
  ApportVersion: 2.20.11-0ubuntu60
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.460
  CurrentDesktop: KDE
  Date: Sun Mar 21 11:53:44 2021
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed 
maybe-ubiquity quiet splash ---
  LiveMediaBuild: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210321)
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

  Since approximately 16/03/2021 ubiquity from maybe-ubiquity (try
  install screen) and from the live session is crashing on launch or
  shortly after.

  Try/Install crash:

   Screen fails to start, or starts then crashes on any user action. The
  user is presented with:

  "Installation failed - The installer encountered an unrecoverable error.
  A desktop session will now be run so that you may investigate the problem or 
try installing again"

  Live session crash:

  The installer does not start from the desktop icon. Starting ubiquity
  from the terminal results in an "Aborted (core dumped)" message and
  nothing else.

  An example /var/log/installer/debug log from a session where both
  crashes were triggered is below.

   /var/log/installer/debug 

  Ubiquity 21.04.11
  TEXT If more than one person will use this computer, you can set up 
multiple accounts after installation.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT The name it uses when it talks to other computers.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT If more than one person will use this computer, you can set up 
multiple accounts after installation.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT The name it uses when it talks to other computers.
  QSocketNotifier: Invalid socket 17 and type 'Read', disabling...
  QSocketNotifier: Invalid socket 17 and type 'Write', disabling...
  QSocketNotifier: Invalid socket 17 and type 'Exception', disabling...
  Your console font configuration will be updated the next time your system
  boots. If you want to update it now, run 'setupcon' from a virtual console.
  update-initramfs is disabled since running on read-only media
  debconf: DbDriver "passwords" warning: could not open 
/var/cache/debconf/passwords.dat: Permission denied
  munmap_chunk(): invalid pointer
  Ubiquity 21.04.11
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu'
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu'
  QStandardPaths: XDG_RUNTIME_DIR not set, defaulting to '/tmp/runtime-kubuntu'
  TEXT If more than one person will use this computer, you can set up 
multiple accounts after installation.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  TEXT The name it uses when it talks to other computers.
  TEXT Enter the same password twice, so that it can be checked for 
typing errors.
  malloc(): unaligned tcache chunk detected

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

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

[Touch-packages] [Bug 1911036] Re: GDK/GTK app crash in XFCE when performing drag operation (in gdk_window_cache_new <- gdk_window_cache_get <- drag_context_find_window_cache <- gdk_x11_drag_context_f

[Daniel van Vugt]

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

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

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

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

Title:
  GDK/GTK app crash in XFCE when performing drag operation (in
  gdk_window_cache_new <- gdk_window_cache_get <-
  drag_context_find_window_cache <- gdk_x11_drag_context_find_window)

Status in GTK+:
  Unknown
Status in gtk+3.0 package in Ubuntu:
  Fix Committed
Status in gtk4 package in Ubuntu:
  Fix Committed

Bug description:
  For many months now, whenever any mouse drag is attempted in an
  application using the gtk tool kit, the application immediately
  crashes. I've noticed this at least in Firefox and thunar. It also
  occurs when displaying these applications from a Virtualbox machine or
  from another server running something other than Ubuntu.  The VM was
  running CentOS 8 and the remote server was running Mageia. Both
  Firefox and thunar run fine with Mageia's Xorg. It seems like the
  issue may be with the Xorg server on Ubuntu.

  I tried setting the GDK_SYNCHRONIZE variable to various settings but
  was unable to produce further debug output. The only other debug
  output I was able to gather is when running thunar with the --gtk-
  debug parameter (attached). I also tried running thunar with GDB but
  without recompiling it, it doesn't produce much information other than
  it's stopping in glib.

  Let me know what other information I can provide.

  (firefox:110380): Gdk-ERROR **: 13:47:04.663: The program 'firefox' received 
an X Window System error.
  This probably reflects a bug in the program.
  The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 8405 error_code 3 request_code 141 (Composite) minor_code 
8)
(Note to programmers: normally, X errors are reported asynchronously;
 that is, you will receive the error a while after causing it.
 To debug your program, run it with the GDK_SYNCHRONIZE environment
 variable to change this behavior. You can then get a meaningful
 backtrace from your debugger if you break on the gdk_x_error() function.)
  ExceptionHandler::GenerateDump cloned child 110611
  ExceptionHandler::SendContinueSignalToChild sent continue signal to child
  ExceptionHandler::WaitForContinueSignal waiting for continue signal...
  Exiting due to channel error.
  Exiting due to channel error.
  Exiting due to channel error.
  Exiting due to channel error.
  [1]+  Trace/breakpoint trap   (core dumped) firefox

  (Thunar:2961220): Gdk-ERROR **: 13:55:39.621: The program 'Thunar' received 
an X Window System error.
  This probably reflects a bug in the program.
  The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 64804 error_code 3 request_code 141 (Composite) minor_code 
8)
(Note to programmers: normally, X errors are reported asynchronously;
 that is, you will receive the error a while after causing it.
 To debug your program, run it with the GDK_SYNCHRONIZE environment
 variable to change this behavior. You can then get a meaningful
 backtrace from your debugger if you break on the gdk_x_error() function.)
  Trace/breakpoint trap (core dumped)

  $ ldd /bin/thunar
  linux-vdso.so.1 (0x7ffc0c8cc000)
  libthunarx-3.so.0 => /lib/x86_64-linux-gnu/libthunarx-3.so.0 
(0x7fdbb548c000)
  libexo-2.so.0 => /lib/x86_64-linux-gnu/libexo-2.so.0 
(0x7fdbb544f000)
  libgudev-1.0.so.0 => /lib/x86_64-linux-gnu/libgudev-1.0.so.0 
(0x7fdbb5442000)
  libnotify.so.4 => /lib/x86_64-linux-gnu/libnotify.so.4 
(0x7fdbb5437000)
  libSM.so.6 => /lib/x86_64-linux-gnu/libSM.so.6 (0x7fdbb542c000)
  libICE.so.6 => /lib/x86_64-linux-gnu/libICE.so.6 (0x7fdbb540e000)
  libxfce4ui-2.so.0 => /lib/x86_64-linux-gnu/libxfce4ui-2.so.0 
(0x7fdbb53f3000)
  libgtk-3.so.0 => /lib/x86_64-linux-gnu/libgtk-3.so.0 
(0x7fdbb4c42000)
  libgdk-3.so.0 => /lib/x86_64-linux-gnu/libgdk-3.so.0 
(0x7fdbb4b3d000)
  libatk-1.0.so.0 => /lib/x86_64-linux-gnu/libatk-1.0.so.0 
(0x7fdbb4b13000)
  libcairo.so.2 => /lib/x86_64-linux-gnu/libcairo.so.2 
(0x7fdbb49f)
  libgdk_pixbuf-2.0.so.0 => 
/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0 (0x7fdbb49c8000)
  libxfce4util.so.7 => /lib/x86_64-linux-gnu/libxfce4util.so.7 
(0x7fdbb49b4000)
  libxfconf-0.so.3 => /lib/x86_64-linux-gnu/libxfconf-0.so.3 
(0x7fdbb4996000)
  libpango-1.0.so.0 => /lib/x86_64-linux-gnu/libpango-1.0.so.0 
(0x7fdbb4947000)
  libgio-2.0.so.0 => /lib/x86_64-linux-gnu/libgio-2.0.so.0 
(0x7fdbb4766000)
  libgobject-2.0.so.0 => /lib/x86_64-linux-gnu/libgobject-2.0.so.0 
(0x7fdbb4706000)
 

[Touch-packages] [Bug 1921078] [NEW] libsoup2.4-dev provides an outdated version of libsoup-2.4.vapi

[gammell]

Public bug reported:

The packages libsoup2.4-dev and valac-0.40-vapi provide different
versions of the file libsoup-2.4.vapi, and the one provided by
libsoup2.4-dev appears to be out of date.

$ apt-file search libsoup-2.4.vapi
libsoup2.4-dev: /usr/share/vala/vapi/libsoup-2.4.vapi
valac-0.40-vapi: /usr/share/vala-0.40/vapi/libsoup-2.4.vapi

I have been informed that this problem also exists on Ubuntu 20.04, but
the differences are less problematic.

https://github.com/pdfpc/pdfpc/issues/589

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libsoup2.4-dev 2.62.1-1ubuntu0.4
ProcVersionSignature: Ubuntu 5.4.0-67.75~18.04.1-generic 5.4.94
Uname: Linux 5.4.0-67-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.23
Architecture: amd64
CurrentDesktop: XFCE
Date: Wed Mar 24 07:32:36 2021
SourcePackage: libsoup2.4
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: libsoup2.4 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

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

Title:
  libsoup2.4-dev provides an outdated version of libsoup-2.4.vapi

Status in libsoup2.4 package in Ubuntu:
  New

Bug description:
  The packages libsoup2.4-dev and valac-0.40-vapi provide different
  versions of the file libsoup-2.4.vapi, and the one provided by
  libsoup2.4-dev appears to be out of date.

  $ apt-file search libsoup-2.4.vapi
  libsoup2.4-dev: /usr/share/vala/vapi/libsoup-2.4.vapi
  valac-0.40-vapi: /usr/share/vala-0.40/vapi/libsoup-2.4.vapi

  I have been informed that this problem also exists on Ubuntu 20.04,
  but the differences are less problematic.

  https://github.com/pdfpc/pdfpc/issues/589

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libsoup2.4-dev 2.62.1-1ubuntu0.4
  ProcVersionSignature: Ubuntu 5.4.0-67.75~18.04.1-generic 5.4.94
  Uname: Linux 5.4.0-67-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.23
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Mar 24 07:32:36 2021
  SourcePackage: libsoup2.4
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libsoup2.4/+bug/1921078/+subscriptions

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

[Touch-packages] [Bug 1902674] Re: cso_set_viewport: Conditional jump or move depends on uninitialised value(s)

[Daniel van Vugt]

mesa (21.0.0-1) experimental; urgency=medium

  * New upstream release. (LP: #1917763)
  * control: Add directx-headers-dev to build-depends for amd64 and arm64
on Linux, which is what WSL2 currently supports.

 -- Timo Aaltonen   Mon, 15 Mar 2021 19:22:33 +0200

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

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

Title:
  cso_set_viewport: Conditional jump or move depends on uninitialised
  value(s)

Status in mesa package in Ubuntu:
  Fix Released

Bug description:
  ==12912== Conditional jump or move depends on uninitialised value(s)
  ==12912==at 0x12094269: cso_set_viewport (cso_context.c:739)
  ==12912==by 0x120942EB: cso_set_viewport_dims (cso_context.c:764)
  ==12912==by 0x11C2AD80: clear_with_quad (st_cb_clear.c:335)
  ==12912==by 0x11C2AD80: st_Clear (st_cb_clear.c:545)

  Because there are unused bits in:

  struct pipe_viewport_state
  {
     float scale[3];
     float translate[3];
     enum pipe_viewport_swizzle swizzle_x:3;
     enum pipe_viewport_swizzle swizzle_y:3;
     enum pipe_viewport_swizzle swizzle_z:3;
     enum pipe_viewport_swizzle swizzle_w:3;
  };

  Fortunately this seems to be fixed upstream already, in
  a3363c348dcd968f2d3e413099a4d28fcda047eb

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

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

[Touch-packages] [Bug 1915870] Re: gnome-shell/gnome-session-check-accelerated-gl-helper crashed with SIGSEGV in cso_destroy_context() [r300_dri.so]

[Daniel van Vugt]

mesa (21.0.0-1) experimental; urgency=medium

  * New upstream release. (LP: #1917763)
  * control: Add directx-headers-dev to build-depends for amd64 and arm64
on Linux, which is what WSL2 currently supports.

 -- Timo Aaltonen   Mon, 15 Mar 2021 19:22:33 +0200

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

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

Title:
  gnome-shell/gnome-session-check-accelerated-gl-helper crashed with
  SIGSEGV in cso_destroy_context() [r300_dri.so]

Status in Mesa:
  Unknown
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa package in Fedora:
  Confirmed

Bug description:
  Graphical user interface is not coming up upon start. Only SSH is
  possible.

  lsb_release -rd:

  Description:  Ubuntu 20.10
  Release:  20.10

  dmesg:

  [   11.985343] gnome-session-c[1013]: segfault at 0 ip  sp 
7fff7679ca48 error 14 in 
gnome-session-check-accelerated-gl-helper[56020e238000+2000]
  [   11.985352] Code: Unable to access opcode bytes at RIP 0xffd6.
  [   14.216117] gnome-shell[1094]: segfault at 0 ip  sp 
7ffeddff9f88 error 14
  [   14.216122] Code: Unable to access opcode bytes at RIP 0xffd6.
  [   15.316292] gnome-shell[1109]: segfault at 0 ip  sp 
7ffc70716198 error 14
  [   15.316297] Code: Unable to access opcode bytes at RIP 0xffd6.

  apt-cache policy:

  gnome-session:
Installed: (none)
Candidate: 3.38.0-1ubuntu1
Version table:
   3.38.0-1ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages
  gnome-session-bin:
Installed: 3.38.0-1ubuntu1
Candidate: 3.38.0-1ubuntu1
Version table:
   *** 3.38.0-1ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  100 /var/lib/dpkg/status
  gnome-session-common:
Installed: 3.38.0-1ubuntu1
Candidate: 3.38.0-1ubuntu1
Version table:
   *** 3.38.0-1ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  500 http://de.archive.ubuntu.com/ubuntu groovy/main i386 Packages
  100 /var/lib/dpkg/status

  /var/crash: see attachment

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

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

[Touch-packages] [Bug 1921076] Re: My screen crashed

[Daniel van Vugt]

The 'xserver-xorg-video-intel' driver is old and should not be used. But
also the attached logs say you're not using it...

Next time the problem happens, please:

1. Take a photo of the screen.

2. Take a fresh system log by running:

   journalctl -b0 > journal.txt

3. Attach both the photo and the text file here.


** Package changed: xorg (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  My screen crashed

Status in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I use the newest version of Ubuntu 20, and sometimes after boot i see a 
corrupted image.
  Then I turn it on recovery mode and I run 'sudo apt-get install 
xserver-xorg-video-intel'.
  After the operation and restart pc everything works correctly.
  I think the problem is related with integrated graphics driver.

  Hope you can fix the problem,
  greetings

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-45-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 24 07:55:00 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Device [8086:9bc5] (rev 05) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
  InstallationDate: Installed on 2021-03-20 (3 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Gigabyte Technology Co., Ltd. Z490 GAMING X AX
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-45-generic 
root=UUID=1ccca862-3ceb-4fcc-9a2d-1743e3f6ad23 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/17/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: Default string
  dmi.board.name: Z490 GAMING X AX
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/17/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnZ490GAMINGXAX:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnZ490GAMINGXAX:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Z490 MB
  dmi.product.name: Z490 GAMING X AX
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1921076] [NEW] My screen crashed

[Kamil]

Public bug reported:

Hi,

I use the newest version of Ubuntu 20, and sometimes after boot i see a 
corrupted image.
Then I turn it on recovery mode and I run 'sudo apt-get install 
xserver-xorg-video-intel'.
After the operation and restart pc everything works correctly.
I think the problem is related with integrated graphics driver.

Hope you can fix the problem,
greetings

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-45-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 24 07:55:00 2021
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Device [8086:9bc5] (rev 05) (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
InstallationDate: Installed on 2021-03-20 (3 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
MachineType: Gigabyte Technology Co., Ltd. Z490 GAMING X AX
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=pl_PL.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-45-generic 
root=UUID=1ccca862-3ceb-4fcc-9a2d-1743e3f6ad23 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/17/2020
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F3
dmi.board.asset.tag: Default string
dmi.board.name: Z490 GAMING X AX
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/17/2020:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnZ490GAMINGXAX:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnZ490GAMINGXAX:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Z490 MB
dmi.product.name: Z490 GAMING X AX
dmi.product.sku: Default string
dmi.product.version: -CF
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu

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

Title:
  My screen crashed

Status in xorg package in Ubuntu:
  New

Bug description:
  Hi,

  I use the newest version of Ubuntu 20, and sometimes after boot i see a 
corrupted image.
  Then I turn it on recovery mode and I run 'sudo apt-get install 
xserver-xorg-video-intel'.
  After the operation and restart pc everything works correctly.
  I think the problem is related with integrated graphics driver.

  Hope you can fix the problem,
  greetings

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.8.0-45.51~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-45-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar 24 07:55:00 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Device [8086:9bc5] (rev 05) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Device [1458:d000]
  InstallationDate: Installed on 2021-03-20 (3 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  MachineType: Gigabyte Technology Co., Ltd. Z490 GAMING X AX
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-45-generic 
root=UUID=1ccca862-3ceb-4fcc-9a2d-1743e3f6ad23 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/17/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F3
  dmi.board.asset.tag: Default string