[Touch-packages] [Bug 1954649] Re: autopkgtest regressions with python3.10 as supported

[Bug Watch Updater]

** Changed in: vorta (Debian)
   Status: Confirmed => Fix Released

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

Title:
  autopkgtest regressions with python3.10 as supported

Status in ipywidgets package in Ubuntu:
  New
Status in pygobject package in Ubuntu:
  Fix Released
Status in pytest-twisted package in Ubuntu:
  New
Status in python-b2sdk package in Ubuntu:
  New
Status in python-hypothesis package in Ubuntu:
  Fix Released
Status in python-taskflow package in Ubuntu:
  Fix Released
Status in python3-defaults package in Ubuntu:
  New
Status in skimage package in Ubuntu:
  Invalid
Status in supysonic package in Ubuntu:
  Fix Released
Status in vorta package in Ubuntu:
  Fix Released
Status in ipywidgets package in Debian:
  New
Status in pygobject package in Debian:
  Fix Released
Status in pytest-twisted package in Debian:
  New
Status in python-b2sdk package in Debian:
  Confirmed
Status in python-hypothesis package in Debian:
  Fix Released
Status in supysonic package in Debian:
  Fix Released
Status in vorta package in Debian:
  Fix Released

Bug description:
  This bug is for tracking the packages having autopkgtest regressions
  with python3.10 as a supported version, blocking migration of
  python3-defaults/3.9.7-4.

  All packages are in universe except pygobject and python-taskflow in
  main.

  All packages have RC bugs in Debian except python-taskflow which is
  based on a newer upstream version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ipywidgets/+bug/1954649/+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 1956350] Re: xdg-desktop-portal-gnome missing in Jammy ISO

[corrado venturini]

https://bugs.launchpad.net/bugs/1953197 fix has been released, so also
this bug can be closed.


** Changed in: ubuntu-meta (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  xdg-desktop-portal-gnome missing in Jammy ISO

Status in ubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  Ubuntu Jammy ISO contains xdg-desktop-portal-gtk but xdg-desktop-portal-gnome 
is missing.
  xdg-desktop-portal-gnome is needed for GIMP Color picker and Flameshot on 
Wayland.
  see https://gitlab.gnome.org/GNOME/gimp/-/issues/1074
  apt show xdg-desktop-portal-gnome says:
  Non-GNOME GTK-based desktop environments should normally use
   xdg-desktop-portal-gtk or their own portal implementation instead of
   this one.
  and Ubuntu 22.04 is a GNOME desktop, so xdg-desktop-portal-gnome should be 
included in the ISO image.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1956350/+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 1780296] Re: [SRU] Update to bugfix 2.0.5 in Bionic

[Erich Eickmeyer ]

Thank you for taking the time to file this bug report and make Ubuntu
better. We apologize that we're not always able to get to bug reports in
a timely manner as most bug triage is done by volunteers.

This appears to be an attempt at an SRU, however, it does not follow the
prescribed SRU procedure. If the reporter does not have upload rights, a
fix will need to be sponsored by a member of the Ubuntu Core Development
team.

Proper SRU procedure is outlined here:
https://wiki.ubuntu.com/StableReleaseUpdates#Procedure

As of this comment, this bug has yet to be fixed. Realistically, the
likelihood of this fix happening is lessening as 18.04 (Bionic) reaches
End of Regular Support in April 2023, meaning that nearly four of the
five-year regular support span has already lapsed.

The best method of resolving this is to upgrade to Ubuntu 20.04 LTS or,
when it releases April 2022, Ubuntu 22.04 LTS.

Additionally, the likelihood of an SRU happening is slim due to this:

>   * libtracker-direct: Majorly rewritten

Any major rewrites usually constitute a rejection of an SRU. However, I
am not on the SRU team, so YMMV.

** Changed in: tracker-miners (Ubuntu)
   Status: New => Invalid

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

** Changed in: tracker (Ubuntu Bionic)
   Status: New => Incomplete

** Changed in: tracker-miners (Ubuntu Bionic)
   Status: New => Incomplete

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

Title:
  [SRU] Update to bugfix 2.0.5 in Bionic

Status in tracker package in Ubuntu:
  Invalid
Status in tracker-miners package in Ubuntu:
  Invalid
Status in tracker source package in Bionic:
  Incomplete
Status in tracker-miners source package in Bionic:
  Incomplete

Bug description:
  Upstream released bugfix version 2.0.5. Please SRU to Bionic.

  https://gitlab.gnome.org/GNOME/tracker-miners/blob/2.0.5/NEWS

  NEW in 2.0.5 - 2018-06-25
  =

* tracker-extract: Made daemon able to shutdown on inactivity, lifetime
  will be managed by tracker-miner-fs
* tracker-stract: Fixes in generated SPARQL for geolocation data
* build: Multiple improvements and library detection fixes

  Translations: el, en_GB, hr, ro, ru
  --

  https://gitlab.gnome.org/GNOME/tracker/blob/2.0.5/NEWS

  NEW in 2.0.5 - 2018-07.22
  =

    * build: Make tarballs able to build with meson. Future releases will
  eventually phase out Autotools
    * build: Various meson build fixes
    * tests: Many fixes to functional tests
    * libtracker-miner: Fixed race conditions that may result in spurious
  "parent not indexed yet" warnings.
    * libtracker-direct: Majorly rewritten
    * tracker-store: Streamlined to use a libtracker-direct connection
  instead of reimplementing most of it.

  NEW in 2.0.4 - 2018-06-25
  =

    * libtracker-miner: Fix event emission order of the root folder when
  a recursive directory is found through monitor events.
    * libtracker-data: Perform VACUUM only past a database file size limit
    * libtracker-miner: Improvements to attribute-only update handling
    * build: Improvements in meson support
    * build: Fix build with --disable-fts
    * build: Drop automatic versioning of parser files, only showstopper
  for meson adoption
    * build: Fixes when building tracker-miners as subproject
    * build: Vala compiler warning fixes
    * build: Update sqlite dep to reflect practical reality

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1780296/+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 1780296] Re: [SRU] Update to bugfix 2.0.5 in Bionic

[Erich Eickmeyer ]

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

** Also affects: tracker-miners (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

Title:
  [SRU] Update to bugfix 2.0.5 in Bionic

Status in tracker package in Ubuntu:
  New
Status in tracker-miners package in Ubuntu:
  New
Status in tracker source package in Bionic:
  New
Status in tracker-miners source package in Bionic:
  New

Bug description:
  Upstream released bugfix version 2.0.5. Please SRU to Bionic.

  https://gitlab.gnome.org/GNOME/tracker-miners/blob/2.0.5/NEWS

  NEW in 2.0.5 - 2018-06-25
  =

* tracker-extract: Made daemon able to shutdown on inactivity, lifetime
  will be managed by tracker-miner-fs
* tracker-stract: Fixes in generated SPARQL for geolocation data
* build: Multiple improvements and library detection fixes

  Translations: el, en_GB, hr, ro, ru
  --

  https://gitlab.gnome.org/GNOME/tracker/blob/2.0.5/NEWS

  NEW in 2.0.5 - 2018-07.22
  =

    * build: Make tarballs able to build with meson. Future releases will
  eventually phase out Autotools
    * build: Various meson build fixes
    * tests: Many fixes to functional tests
    * libtracker-miner: Fixed race conditions that may result in spurious
  "parent not indexed yet" warnings.
    * libtracker-direct: Majorly rewritten
    * tracker-store: Streamlined to use a libtracker-direct connection
  instead of reimplementing most of it.

  NEW in 2.0.4 - 2018-06-25
  =

    * libtracker-miner: Fix event emission order of the root folder when
  a recursive directory is found through monitor events.
    * libtracker-data: Perform VACUUM only past a database file size limit
    * libtracker-miner: Improvements to attribute-only update handling
    * build: Improvements in meson support
    * build: Fix build with --disable-fts
    * build: Drop automatic versioning of parser files, only showstopper
  for meson adoption
    * build: Fixes when building tracker-miners as subproject
    * build: Vala compiler warning fixes
    * build: Update sqlite dep to reflect practical reality

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tracker/+bug/1780296/+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 1959343] Re: deprecation of the Canonical partner archive

[Steve Langasek]

Yes, looks like this can be removed.

** Also affects: app-install-data-partner (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  deprecation of the Canonical partner archive

Status in subiquity:
  Invalid
Status in app-install-data-partner package in Ubuntu:
  New
Status in cloud-init package in Ubuntu:
  In Progress
Status in curtin package in Ubuntu:
  Invalid
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in python-apt package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  In Progress
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released

Bug description:
  The Canonical partner archive is no longer being used for publishing
  new packages, and is empty from Ubuntu 20.10 on.  We should stop
  including it in the default sources.list, and clean up references to
  it in our codebase.

To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/1959343/+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 1959363] Re: [needs-packaging] Update to libXfixes 6.x

[Brian Murray]

*** This is an automated message ***

This bug is tagged needs-packaging which identifies it as a request for
a new package in Ubuntu.  As a part of the managing needs-packaging bug
reports specification,
https://wiki.ubuntu.com/QATeam/Specs/NeedsPackagingBugs, all needs-
packaging bug reports have Wishlist importance.  Subsequently, I'm
setting this bug's status to Wishlist.

** Summary changed:

- Update to libXfixes 6.x
+ [needs-packaging] Update to libXfixes 6.x

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

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

Title:
  [needs-packaging] Update to libXfixes 6.x

Status in libxfixes package in Ubuntu:
  New
Status in libxfixes package in Debian:
  New

Bug description:
  Update to libXfixes 6.x

  https://gitlab.freedesktop.org/xorg/lib/libxfixes/-/tags

  It is a prerequisite to build mutter 42.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxfixes/+bug/1959363/+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 1923845] Re: Please compress packages with zstd by default

[Stephan Lachnit]

FYI I added initial support for Lutris here 
(https://github.com/lutris/lutris/pull/4021).
However this is really only cosmetics, it won't work until an stdlib zstd 
module is available in Python (see 
https://mail.python.org/archives/list/python-id...@python.org/thread/VQIFA7WTNRAOYZGTVP4WZC2CD36KYIVY/#RMMZFYPKHDJHGSHCKHRKRDGKPZSCUHT2).

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

Title:
  Please compress packages with zstd by default

Status in appstream-glib package in Ubuntu:
  New
Status in apt package in Ubuntu:
  Fix Released
Status in aptly package in Ubuntu:
  New
Status in boinc package in Ubuntu:
  New
Status in busybox package in Ubuntu:
  New
Status in cdebootstrap package in Ubuntu:
  New
Status in cdist package in Ubuntu:
  New
Status in debdelta package in Ubuntu:
  New
Status in debian-el package in Ubuntu:
  New
Status in debootstrap package in Ubuntu:
  Fix Released
Status in debsig-verify package in Ubuntu:
  New
Status in debsigs package in Ubuntu:
  New
Status in diffoscope package in Ubuntu:
  Fix Released
Status in dpkg package in Ubuntu:
  Fix Released
Status in dpkg-sig package in Ubuntu:
  New
Status in file package in Ubuntu:
  New
Status in hello package in Ubuntu:
  Fix Released
Status in libsolv package in Ubuntu:
  New
Status in lintian package in Ubuntu:
  Fix Released
Status in lutris package in Ubuntu:
  In Progress
Status in obs-build package in Ubuntu:
  New
Status in osc package in Ubuntu:
  New
Status in python-debian package in Ubuntu:
  Fix Released
Status in radare2 package in Ubuntu:
  New
Status in reprepro package in Ubuntu:
  Fix Released
Status in vim-scripts package in Ubuntu:
  New
Status in zeroinstall-injector package in Ubuntu:
  New
Status in reprepro source package in Focal:
  Fix Released
Status in reprepro source package in Groovy:
  Fix Released
Status in reprepro source package in Hirsute:
  Fix Released
Status in debian-el package in Debian:
  New

Bug description:
  https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built
  on Hirsute having both data and control members of the .deb being
  compressed with zstd. It can be handy for testing various tools.

  [dpkg]
  Decompression support in dpkg landed first in Bionic and is being SRUd to 
Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the 
zstd-compressed binary packages.
  From dpkg's perspective the upgrade path is cleared.

  The original plan was compressing only the internal data.tar .deb
  member, but dpkg uses uniform compression by default since dpkg 1.19.0
  thus I'm collecting all the changes to support control.tar.zst, too,
  in this bug.

  Reviewed packages from:
  https://codesearch.debian.net/search?q=data.tar.xz&literal=1&perpkg=1
  https://codesearch.debian.net/search?q=control.tar.xz&literal=1&perpkg=1

  appstream-glib  - needs fix: libappstream-builder/asb-package-deb.c
  aptly   - needs fix: deb/deb.go
  boinc   - needs fix: debian/fetch_example_applications.sh
  busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c
  cdebootstrap- needs fix: src/package.c
  cdist   - may need fix, can use dpkg-deb: 
cdist/preos/debootstrap/files/devuan-debootstrap/functions
  debdelta- needs fix: debdelta debpatch.sh
  debian-el   - needs fix: deb-view.el
  debian-handbook - needs fix, maybe later, for Debian
  debootstrap - needs fix, 
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54
  debsigs - needs fix, debsigs
  debsig-verify   - needs fix, src/debsig-verify.c
  diffoscope  - needs fix, diffoscope/comparators/deb.py
  dpkg- needs fix, change default
  dpkg-sig- needs fix, dpkg-sig
  dpmb- needs fix, maybe later, for Debian
  elfutils- may need fix, uses dpkg-deb if it is available, does not 
handle .gz either
  file- needs fix, magic/Magdir/archive
  libsolv - needs fix, ext/repo_deb.c
  lintian - needs fix malformed-deb-archive
  lutris  - needs fix, lutris/util/extract.py
  obs-build   - needs fix Build/Deb.pm
  osc - needs fix osc/util/debquery.py control.tar.zst only
  python-apt  - needs fix 
apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall()
  radare2 - needs fix
  reprepro- needs fix, debfile.c
  vim-scripts - needs fix debPlugin/autoload/deb.vim
  winetricks  - needs fix when Debian switches src/winetricks
  zeroinstall-injector - needs fix src/zeroinstall/archive.ml

  acr - skip, does not _have to_ be fixed, just creates packages, 
see dist/deb_hand.mak
  alien   - skip, uses dpkg-deb to extract .deb
  ansible - not affected, just test data in dbdata.tar.xz
  anthy   - not affected, just changelog entry
  apt - seems fixe

[Touch-packages] [Bug 1959343] Re: deprecation of the Canonical partner archive

[Brian Murray]

Can we also remove app-install-data-partner from the archive?

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

Title:
  deprecation of the Canonical partner archive

Status in subiquity:
  Invalid
Status in cloud-init package in Ubuntu:
  In Progress
Status in curtin package in Ubuntu:
  Invalid
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in python-apt package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  In Progress
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released

Bug description:
  The Canonical partner archive is no longer being used for publishing
  new packages, and is empty from Ubuntu 20.10 on.  We should stop
  including it in the default sources.list, and clean up references to
  it in our codebase.

To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/1959343/+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 1923845] Re: Please compress packages with zstd by default

[Stephan Lachnit]

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

** Changed in: lutris (Ubuntu)
 Assignee: (unassigned) => Stephan Lachnit (stephanlachnit)

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

Title:
  Please compress packages with zstd by default

Status in appstream-glib package in Ubuntu:
  New
Status in apt package in Ubuntu:
  Fix Released
Status in aptly package in Ubuntu:
  New
Status in boinc package in Ubuntu:
  New
Status in busybox package in Ubuntu:
  New
Status in cdebootstrap package in Ubuntu:
  New
Status in cdist package in Ubuntu:
  New
Status in debdelta package in Ubuntu:
  New
Status in debian-el package in Ubuntu:
  New
Status in debootstrap package in Ubuntu:
  Fix Released
Status in debsig-verify package in Ubuntu:
  New
Status in debsigs package in Ubuntu:
  New
Status in diffoscope package in Ubuntu:
  Fix Released
Status in dpkg package in Ubuntu:
  Fix Released
Status in dpkg-sig package in Ubuntu:
  New
Status in file package in Ubuntu:
  New
Status in hello package in Ubuntu:
  Fix Released
Status in libsolv package in Ubuntu:
  New
Status in lintian package in Ubuntu:
  Fix Released
Status in lutris package in Ubuntu:
  In Progress
Status in obs-build package in Ubuntu:
  New
Status in osc package in Ubuntu:
  New
Status in python-debian package in Ubuntu:
  Fix Released
Status in radare2 package in Ubuntu:
  New
Status in reprepro package in Ubuntu:
  Fix Released
Status in vim-scripts package in Ubuntu:
  New
Status in zeroinstall-injector package in Ubuntu:
  New
Status in reprepro source package in Focal:
  Fix Released
Status in reprepro source package in Groovy:
  Fix Released
Status in reprepro source package in Hirsute:
  Fix Released
Status in debian-el package in Debian:
  New

Bug description:
  https://people.canonical.com/~rbalint/zstd-debs/ contains a .deb built
  on Hirsute having both data and control members of the .deb being
  compressed with zstd. It can be handy for testing various tools.

  [dpkg]
  Decompression support in dpkg landed first in Bionic and is being SRUd to 
Xenial in LP: #1764220 enable Launchpad's Xenial systems to process the 
zstd-compressed binary packages.
  From dpkg's perspective the upgrade path is cleared.

  The original plan was compressing only the internal data.tar .deb
  member, but dpkg uses uniform compression by default since dpkg 1.19.0
  thus I'm collecting all the changes to support control.tar.zst, too,
  in this bug.

  Reviewed packages from:
  https://codesearch.debian.net/search?q=data.tar.xz&literal=1&perpkg=1
  https://codesearch.debian.net/search?q=control.tar.xz&literal=1&perpkg=1

  appstream-glib  - needs fix: libappstream-builder/asb-package-deb.c
  aptly   - needs fix: deb/deb.go
  boinc   - needs fix: debian/fetch_example_applications.sh
  busybox - needs fix: archival/dpkg_deb.c archival/dpkg.c
  cdebootstrap- needs fix: src/package.c
  cdist   - may need fix, can use dpkg-deb: 
cdist/preos/debootstrap/files/devuan-debootstrap/functions
  debdelta- needs fix: debdelta debpatch.sh
  debian-el   - needs fix: deb-view.el
  debian-handbook - needs fix, maybe later, for Debian
  debootstrap - needs fix, 
https://salsa.debian.org/installer-team/debootstrap/-/merge_requests/54
  debsigs - needs fix, debsigs
  debsig-verify   - needs fix, src/debsig-verify.c
  diffoscope  - needs fix, diffoscope/comparators/deb.py
  dpkg- needs fix, change default
  dpkg-sig- needs fix, dpkg-sig
  dpmb- needs fix, maybe later, for Debian
  elfutils- may need fix, uses dpkg-deb if it is available, does not 
handle .gz either
  file- needs fix, magic/Magdir/archive
  libsolv - needs fix, ext/repo_deb.c
  lintian - needs fix malformed-deb-archive
  lutris  - needs fix, lutris/util/extract.py
  obs-build   - needs fix Build/Deb.pm
  osc - needs fix osc/util/debquery.py control.tar.zst only
  python-apt  - needs fix 
apt_inst.DebFile("glibc-doc-reference_2.33-0ubuntu2~zstd1_all.deb").control.extractall()
  radare2 - needs fix
  reprepro- needs fix, debfile.c
  vim-scripts - needs fix debPlugin/autoload/deb.vim
  winetricks  - needs fix when Debian switches src/winetricks
  zeroinstall-injector - needs fix src/zeroinstall/archive.ml

  acr - skip, does not _have to_ be fixed, just creates packages, 
see dist/deb_hand.mak
  alien   - skip, uses dpkg-deb to extract .deb
  ansible - not affected, just test data in dbdata.tar.xz
  anthy   - not affected, just changelog entry
  apt - seems fixed already
  ceph- not affected in Ubuntu's version
  circlator   - not affected, just test data
  cowdancer   - not affected, just documentation
  eccodes 

[Touch-packages] [Bug 1959343] Re: deprecation of the Canonical partner archive

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-release-upgrader - 1:22.04.4

---
ubuntu-release-upgrader (1:22.04.4) jammy; urgency=medium

  [ Steve Langasek ]
  * DistUpgrade/DistUpgradeController.py: remove references to
archive.canonical.com from sources.list on upgrade.  LP: #1959343.

  [ Brian Murray ]
  * tests/test_sources_list.py: update the tests which expected / utilized the
archive.canonical.com partner repository.

 -- Brian Murray   Fri, 28 Jan 2022 11:39:24 -0800

** Changed in: ubuntu-release-upgrader (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 python-apt in Ubuntu.
https://bugs.launchpad.net/bugs/1959343

Title:
  deprecation of the Canonical partner archive

Status in subiquity:
  Invalid
Status in cloud-init package in Ubuntu:
  In Progress
Status in curtin package in Ubuntu:
  Invalid
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in python-apt package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  In Progress
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released

Bug description:
  The Canonical partner archive is no longer being used for publishing
  new packages, and is empty from Ubuntu 20.10 on.  We should stop
  including it in the default sources.list, and clean up references to
  it in our codebase.

To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/1959343/+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 1959453] [NEW] package libdrm-intel1:amd64 2.4.105-3~20.04.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting co

[Christopher Paddon]

Public bug reported:

Could not perform a system update upon fresh install

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libdrm-intel1:amd64 2.4.105-3~20.04.2
ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
CompositorRunning: None
Date: Fri Jan 28 13:13:01 2022
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
DuplicateSignature:
 package:libdrm-intel1:amd64:2.4.105-3~20.04.2
 Setting up libsystemd0:amd64 (245.4-4ubuntu3.15) ...
 dpkg: error processing package libdrm-intel1:amd64 (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
GraphicsCard:
 Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:883c]
InstallationDate: Installed on 2022-01-28 (0 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 04f2:b710 Chicony Electronics Co., Ltd HP TrueVision HD 
Camera
 Bus 001 Device 004: ID 0bda:b00e Realtek Semiconductor Corp. Bluetooth Radio 
 Bus 001 Device 002: ID 1bcf:0005 Sunplus Innovation Technology Inc. Optical 
Mouse
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: HP HP Laptop 17-cn0xxx
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic 
root=UUID=445be58c-9730-41e0-9728-2ecc1fcc50d1 ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.6
SourcePackage: libdrm
Title: package libdrm-intel1:amd64 2.4.105-3~20.04.2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2021
dmi.bios.release: 15.4
dmi.bios.vendor: AMI
dmi.bios.version: F.04
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 883C
dmi.board.vendor: HP
dmi.board.version: 69.16
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 69.16
dmi.modalias: 
dmi:bvnAMI:bvrF.04:bd04/01/2021:br15.4:efr69.16:svnHP:pnHPLaptop17-cn0xxx:pvr:rvnHP:rn883C:rvr69.16:cvnHP:ct10:cvrChassisVersion:sku316H8UA#ABA:
dmi.product.family: 103C_5335KV HP Notebook
dmi.product.name: HP Laptop 17-cn0xxx
dmi.product.sku: 316H8UA#ABA
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.105-3~20.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2
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: libdrm (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package focal need-duplicate-check ubuntu

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

Title:
  package libdrm-intel1:amd64 2.4.105-3~20.04.2 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in libdrm package in Ubuntu:
  New

Bug description:
  Could not perform a system update upon fresh install

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libdrm-intel1:amd64 2.4.105-3~20.04.2
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Fri Jan 28 13:13:01 2022
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DuplicateSignature:
   package:libdrm-intel1:amd64:2.4.105-3~20.04.2
   Setting up libsystemd0:amd64 (245.4-4ubuntu3.15) ...
   dpkg: error processing package libdrm-intel1:amd64 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  GraphicsCard:
   Intel Corporation Device [8086:9a49] (rev 01) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:883c]
  InstallationDate: Installed on 2022-01-28 (0 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  

Re: [Touch-packages] [Bug 1737479] Re: Xorg appears to crash on login

[Chris Lee]

I can't say that I am still experiencing this problem because I upgraded a
long time ago to the latest. Thanks for checking in though!

On Fri, Jan 28, 2022 at 5:56 AM Paul White  <1737...@bugs.launchpad.net>
wrote:

> We are sorry that we do not always have the capacity to review all
> reported bugs in a timely manner. You reported this bug some time ago
> and there have been many changes in Ubuntu since that time.
>
> Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.
>
> Do you still see a problem related to the one that you reported when
> using a currently supported version of Ubuntu? Please let us know if you
> do otherwise this report can be left to expire in approximately 60 days
> time.
>
> Thank you for helping make Ubuntu better.
>
>
> ** Changed in: xorg (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1737479
>
> Title:
>   Xorg appears to crash on login
>
> Status in xorg package in Ubuntu:
>   Incomplete
>
> Bug description:
>   Upon logging in, a crash report appears detailing that xorg has
>   crashed and also that the problem report is damaged and cannot be
>   processed.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: xorg 1:7.7+13ubuntu3
>   ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
>   Uname: Linux 4.4.0-98-generic x86_64
>   .tmp.unity_support_test.0:
>
>   ApportVersion: 2.20.1-0ubuntu2.10
>   Architecture: amd64
>   BootLog:
>Scanning for Btrfs filesystems
>UBUNTU: clean, 38/28950528 files, 3863331/115784448 blocks
>   CompizPlugins: No value set for
> `/apps/compiz-1/general/screen0/options/active_plugins'
>   CompositorRunning: compiz
>   CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
>   CompositorUnredirectFSW: true
>   CurrentDesktop: Unity
>   Date: Sun Dec 10 22:21:06 2017
>   DistUpgraded: Fresh install
>   DistributionChannelDescriptor:
># This is a distribution channel descriptor
># For more information see
> http://wiki.ubuntu.com/DistributionChannelDescriptor
>canonical-oem-somerville-xenial-amd64-20160624-2
>   DistroCodename: xenial
>   DistroVariant: ubuntu
>   DpkgLog:
>
>   GraphicsCard:
>Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA
> controller])
>  Subsystem: Dell Device [1028:075b]
>   InstallationDate: Installed on 2016-12-01 (374 days ago)
>   InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary
> 20160624-10:47
>   Lsusb:
>Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>Bus 001 Device 004: ID 0bda:568b Realtek Semiconductor Corp.
>Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp.
>Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc.
>Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>   MachineType: Dell Inc. XPS 13 9360
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic.efi.signed
> root=UUID=d9ec0f69-d5f3-4e71-ac1c-6e3c5ec32195 ro quiet splash vt.handoff=7
>   SourcePackage: xorg
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 09/13/2016
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: 1.0.7
>   dmi.board.name: 0839Y6
>   dmi.board.vendor: Dell Inc.
>   dmi.board.version: A00
>   dmi.chassis.type: 9
>   dmi.chassis.vendor: Dell Inc.
>   dmi.modalias:
> dmi:bvnDellInc.:bvr1.0.7:bd09/13/2016:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0839Y6:rvrA00:cvnDellInc.:ct9:cvr:
>   dmi.product.name: XPS 13 9360
>   dmi.sys.vendor: Dell Inc.
>   version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
>   version.ia32-libs: ia32-libs N/A
>   version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
>   version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
>   version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
>   version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
>   version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev
> 1:2.10.1-1ubuntu2
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
> 1:1.0.12-1build2
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1737479/+subscriptions
>
>

-- 
Christopher Lee

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

Title:
  Xorg appears to crash on login

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Upon logging in, a crash report appears detailing that xorg has
  crashed and also that the problem report is damaged and cannot be
  processed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7

[Touch-packages] [Bug 1959445] [NEW] DHCPD gets confused about what IPs should be handed out on what interfaces

[Daniel C]

Public bug reported:

I had a device request an IP on one VLAN (one interface associated with
the server -- ens256), and then I moved the device to a different VLAN
(interface ens192 on the server), and was surprised when the DHCPD
process continued to hand out the same IP on the new VLAN.

Here are the associated syslog entries, and the IP interface settings:

Jan 28 12:06:35 backup dhcpd[1020678]: DHCPREQUEST for 10.2.195.100 from 
ec:02:73:b8:4d:01 via ens256
Jan 28 12:06:35 backup dhcpd[1020678]: DHCPACK on 10.2.195.100 to 
ec:02:73:b8:4d:01 via ens256
Jan 28 12:08:43 backup dhcpd[1020678]: DHCPREQUEST for 10.2.195.100 from 
ec:02:73:b8:4d:01 via ens256
Jan 28 12:08:43 backup dhcpd[1020678]: DHCPACK on 10.2.195.100 to 
ec:02:73:b8:4d:01 via ens256
Jan 28 12:11:08 backup dhcpd[1024746]: DHCPREQUEST for 10.2.195.100 from 
ec:02:73:b8:4d:01 via ens192
Jan 28 12:11:08 backup dhcpd[1024746]: DHCPACK on 10.2.195.100 to 
ec:02:73:b8:4d:01 via ens192
Jan 28 12:11:23 backup dhcpd[1024746]: DHCPREQUEST for 10.2.195.100 from 
ec:02:73:b8:4d:01 via ens192
Jan 28 12:11:23 backup dhcpd[1024746]: DHCPACK on 10.2.195.100 to 
ec:02:73:b8:4d:01 via ens192

(I've trimmed out the IPv6 information):
backup$ ip addr list
...
3: ens192:  mtu 1500 qdisc mq state UP group 
default qlen 1000
link/ether 00:50:56:9e:8b:d8 brd ff:ff:ff:ff:ff:ff
inet 10.7.32.2/21 brd 10.7.39.255 scope global ens192
   valid_lft forever preferred_lft forever
...
5: ens256:  mtu 1500 qdisc mq state UP group 
default qlen 1000
link/ether 00:50:56:9e:f2:e6 brd ff:ff:ff:ff:ff:ff
inet 10.2.195.2/24 brd 10.2.195.255 scope global ens256
   valid_lft forever preferred_lft forever
...

When I rebooted the client, it went back to DHCPDISCOVER mode and then
the DHCPD daemon correctly recognized that this client was on a new
interface/VLAN and handed it a valid IP address for that interface/VLAN.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: isc-dhcp-server 4.4.1-2.1ubuntu5.20.04.2 [modified: usr/bin/omshell]
ProcVersionSignature: Ubuntu 5.4.0-94.106-generic 5.4.157
Uname: Linux 5.4.0-94-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: pass
Date: Fri Jan 28 12:24:05 2022
InstallationDate: Installed on 2021-06-29 (212 days ago)
InstallationMedia: Ubuntu-Server 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
ProcEnviron:
 SHELL=/bin/bash
 TERM=xterm-color
 XDG_RUNTIME_DIR=
 PATH=(custom, user)
SourcePackage: isc-dhcp
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.dhcp.dhcpd6.conf: [modified]
mtime.conffile..etc.dhcp.dhcpd.conf: 2022-01-28T12:09:41.747865
mtime.conffile..etc.dhcp.dhcpd6.conf: 2019-01-03T15:05:49

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


** Tags: amd64 apport-bug focal uec-images

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

Title:
  DHCPD gets confused about what IPs should be handed out on what
  interfaces

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  I had a device request an IP on one VLAN (one interface associated
  with the server -- ens256), and then I moved the device to a different
  VLAN (interface ens192 on the server), and was surprised when the
  DHCPD process continued to hand out the same IP on the new VLAN.

  Here are the associated syslog entries, and the IP interface settings:

  Jan 28 12:06:35 backup dhcpd[1020678]: DHCPREQUEST for 10.2.195.100 from 
ec:02:73:b8:4d:01 via ens256
  Jan 28 12:06:35 backup dhcpd[1020678]: DHCPACK on 10.2.195.100 to 
ec:02:73:b8:4d:01 via ens256
  Jan 28 12:08:43 backup dhcpd[1020678]: DHCPREQUEST for 10.2.195.100 from 
ec:02:73:b8:4d:01 via ens256
  Jan 28 12:08:43 backup dhcpd[1020678]: DHCPACK on 10.2.195.100 to 
ec:02:73:b8:4d:01 via ens256
  Jan 28 12:11:08 backup dhcpd[1024746]: DHCPREQUEST for 10.2.195.100 from 
ec:02:73:b8:4d:01 via ens192
  Jan 28 12:11:08 backup dhcpd[1024746]: DHCPACK on 10.2.195.100 to 
ec:02:73:b8:4d:01 via ens192
  Jan 28 12:11:23 backup dhcpd[1024746]: DHCPREQUEST for 10.2.195.100 from 
ec:02:73:b8:4d:01 via ens192
  Jan 28 12:11:23 backup dhcpd[1024746]: DHCPACK on 10.2.195.100 to 
ec:02:73:b8:4d:01 via ens192

  (I've trimmed out the IPv6 information):
  backup$ ip addr list
  ...
  3: ens192:  mtu 1500 qdisc mq state UP group 
default qlen 1000
  link/ether 00:50:56:9e:8b:d8 brd ff:ff:ff:ff:ff:ff
  inet 10.7.32.2/21 brd 10.7.39.255 scope global ens192
 valid_lft forever preferred_lft forever
  ...
  5: ens256:  mtu 1500 qdisc mq state UP group 
default qlen 1000
  link/ether 00:50:56:9e:f2:e6 brd ff:ff:ff:ff:ff:ff
  inet 10.2.195.2/24 brd 10.2.195.255 scope global ens256
 valid_lft forever preferred_lft forever
  ...

  When I rebooted the client, it went back to DHCPDISCOVER mode and then
  the DHCPD daemon correctly rec

[Touch-packages] [Bug 1955997] Re: The airplane hotkey has no function on a HP platform

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 249.9-0ubuntu2

---
systemd (249.9-0ubuntu2) jammy; urgency=medium

  * Skip flaky 55-OOMD test on ppc64el
File: debian/patches/deny-list-TEST-55-OOMD-on-ppc64el.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=211f8962ce89d416c2866444e0e2da794ecd5dd1

 -- Lukas Märdian   Fri, 28 Jan 2022 10:46:41 +0100

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

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

Title:
  The airplane hotkey has no function on a HP platform

Status in OEM Priority Project:
  Triaged
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  New
Status in systemd source package in Impish:
  New
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  The airplane hokey doesn't work on HP new generation machines.

  [Test Plan]
  Press airplane hokey.

  Before the patch, nothing happens.
  After the patch, the rfkill works as expected.

  [Where problems could occur]
  In non-gnome ubuntu, if the specific dmi contains HPQ6001, then airplane will 
not work but HP confirmed the new HP generation won't contain the HPQ6001 and 
also each DM still need to deal with multi-rfkill events because upstream 
changes[2].

  ---

  In the last year, HP mentions HP machines need to use hp-wireless
  (HPQ6001) as the rfkill source[1].

  However, HP confirms the HPQ6001 has been retired in the platforms
  since 2022.

  In the platforms after 2022, there are two sources of rkfill events 
(intel-hid, atkbd) and HP only guarantee the intel-hid works.
  Therefore, the upstream already accept the patch[2] to unmask intel-hid and 
mention this big change in the NEWS.

  This change makes the pre-2022 HP platforms meet the regression since they 
have two rfkill events (HPQ6001 and intel-hid) be triggered if pressing 
function key.
  Thus, there is a patch[3] to make sure the GNOME could deal with this case 
smoothly.
  However, the systemd change will still cause other DEs meet the regression 
(xfce, KDE, lxde, etc..).
  Backport systemd change to make HP 2022 platforms work is not the best choice 
on stable version (focal in this case).

  We still need a solution to make airplane key works on 2022 HP platforms 
(intel-hid and atkbd only).
  The potential solution from my mind that is to maintain a whitelist to unmask 
intel-hid in ubuntu-patch in focal, something like:
  ```
  evdev:name:Intel HID events:dmi:bvn*:bvr*:bd*:svnHP*:pnHPZBookFury16inchG9*:*
   KEYBOARD_KEY_8=wlan # Use hp-wireless instead
  ```
  after "KEYBOARD_KEY_8=unkown".

  [1] https://bugs.launchpad.net/bugs/1883846
  [2] https://github.com/systemd/systemd/pull/20219
  [3] 
https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/commit/f4dbcf3d7b0f951fe44b29229206c97b625dbfda

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1955997/+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 1959013] Re: systemd test_exec_umask_namespace fails in privileged container

[Launchpad Bug Tracker]

This bug was fixed in the package systemd - 249.9-0ubuntu2

---
systemd (249.9-0ubuntu2) jammy; urgency=medium

  * Skip flaky 55-OOMD test on ppc64el
File: debian/patches/deny-list-TEST-55-OOMD-on-ppc64el.patch

https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=211f8962ce89d416c2866444e0e2da794ecd5dd1

 -- Lukas Märdian   Fri, 28 Jan 2022 10:46:41 +0100

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

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

Title:
  systemd test_exec_umask_namespace fails in privileged container

Status in lxd package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  systemd added a new test case to it's "test-execute", which is failing
  in privileged containers, while passing everywhere else.

  https://github.com/systemd/systemd-
  stable/commit/ae53f4b5e48860b473c4d05958486a77f84ecc6d

  exec-umask-namespace.service: Passing 0 fds to service
  exec-umask-namespace.service: About to execute /bin/ls -lahd /tmp/subdir
  exec-umask-namespace.service: Forked /bin/ls as 2485
  exec-umask-namespace.service: Changed dead -> start
  exec-umask-namespace.service: User lookup succeeded: uid=65534 gid=65534
  Received SIGCHLD from PID 2485 (ls).
  Child 2485 (ls) died (code=exited, status=2/INVALIDARGUMENT)
  exec-umask-namespace.service: Failed to read oom_kill field of memory.events 
cgroup attribute: No such file or directory
  exec-umask-namespace.service: Child 2485 belongs to 
exec-umask-namespace.service.
  exec-umask-namespace.service: Main process exited, code=exited, 
status=2/INVALIDARGUMENT
  exec-umask-namespace.service: Failed with result 'exit-code'.
  exec-umask-namespace.service: Service will not restart (restart setting)
  exec-umask-namespace.service: Changed start -> failed
  exec-umask-namespace.service: Unit entered failed state.
  src/test/test-execute.c:868:test_exec_umask_namespace: 
exec-umask-namespace.service: exit status 2, expected 0

  
  A full test-run / log is available at 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy-slyon-testing/jammy/amd64/s/systemd/20220125_143301_25947@/log.gz

  I'll be skipping this test case fow now, to be able to move forward
  with systemd 249.9

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1959013/+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 1959439] [NEW] On Ubuntu 22.04 logrotate does not rotate syslog

[corrado venturini]

Public bug reported:

On my Ubuntu 22.04 Jammy installed 2022-01-03 /var/log/syslog is very
big and was never rotated.

corrado@corrado-n3-jj-0103:~$ stat /var/log/syslog
  File: /var/log/syslog
  Size: 77434065Blocks: 151248 IO Block: 4096   regular file
Device: 10303h/66307d   Inode: 264672  Links: 1
Access: (0640/-rw-r-)  Uid: (  104/  syslog)   Gid: (4/ adm)
Access: 2022-01-28 16:35:50.408728666 +0100
Modify: 2022-01-28 16:35:47.705029318 +0100
Change: 2022-01-28 16:35:47.705029318 +0100
 Birth: 2022-01-03 14:31:29.195999321 +0100
corrado@corrado-n3-jj-0103:~$ 

looking to journalctl i see logrotate has been started on January 25 but
log file was not cut

corrado@corrado-n3-jj-0103:~$ journalctl -b-18 | grep logrotate
gen 25 07:58:01 corrado-n3-jj-0103 systemd[1]: logrotate.service: Deactivated 
successfully.
gen 25 09:35:09 corrado-n3-jj-0103 systemd[1]: logrotate.timer: Deactivated 
successfully.
corrado@corrado-n3-jj-0103:~$ 

corrado@corrado-n3-jj-0103:~$ systemctl status logrotate.service
○ logrotate.service - Rotate log files
 Loaded: loaded (/lib/systemd/system/logrotate.service; static)
 Active: inactive (dead)
TriggeredBy: ● logrotate.timer
   Docs: man:logrotate(8)
 man:logrotate.conf(5)
corrado@corrado-n3-jj-0103:~$ 

corrado@corrado-n3-jj-0103:~$ cat /etc/logrotate.conf
# see "man logrotate" for details

# global options do not affect preceding include directives

# rotate log files weekly
weekly

# use the adm group by default, since this is the owning group
# of /var/log/syslog.
su root adm

# keep 4 weeks worth of backlogs
rotate 4

# create new (empty) log files after rotating old ones
create

# use date as a suffix of the rotated file
#dateext

# uncomment this if you want your log files compressed
#compress

# packages drop log rotation information into this directory
include /etc/logrotate.d

# system-specific logs may also be configured here.
corrado@corrado-n3-jj-0103:~$ 

corrado@corrado-n3-jj-0103:~$ ls /var/log -lh
total 108M
-rw-r--r--  1 root  root  42K gen 27 21:20 
alternatives.log
-rw-r-  1 root  adm  5,5K gen 28 17:32 apport.log
drwxr-xr-x  2 root  root 4,0K gen 28 17:52 apt
-rw-r-  1 syslogadm  762K gen 28 19:08 auth.log
-rw---  1 root  root1019K gen 28 17:54 boot.log
-rw-r--r--  1 root  root 105K gen  3 08:43 bootstrap.log
-rw-rw  1 root  utmp0 gen  3 08:42 btmp
drwxr-xr-x  2 root  root 4,0K gen  3 14:31 cups
drwxr-xr-x  2 root  root 4,0K ott 29 18:59 dist-upgrade
-rw-r-  1 root  adm   81K gen 28 17:55 dmesg
-rw-r-  1 root  adm   80K gen 28 17:22 dmesg.0
-rw-r-  1 root  adm   22K gen 28 17:02 dmesg.1.gz
-rw-r-  1 root  adm   22K gen 28 16:01 dmesg.2.gz
-rw-r-  1 root  adm   22K gen 28 10:29 dmesg.3.gz
-rw-r-  1 root  adm   22K gen 28 08:54 dmesg.4.gz
-rw-r--r--  1 root  root 1,4M gen 28 17:52 dpkg.log
-rw-r--r--  1 root  root  32K gen  6 09:44 faillog
-rw-r--r--  1 root  root  12K gen 28 15:32 
fontconfig.log
drwx--x--x  2 root  gdm  4,0K gen  3 14:31 gdm3
-rw-r--r--  1 root  root 1,5K gen 28 17:54 
gpu-manager.log
drwxr-xr-x  3 root  root 4,0K gen  3 08:44 hp
drwxr-xr-x  2 root  root 4,0K gen  3 13:59 installer
-rw-r--r--  1 root  root 544K gen 11 08:33 installer.zip
-rw-r--r--  1 root  root 544K gen  3 21:25 inst.zip
drwxr-sr-x+ 3 root  systemd-journal  4,0K gen  3 14:31 journal
-rw-r-  1 syslogadm   27M gen 28 19:09 kern.log
-rw-rw-r--  1 root  utmp 286K gen  6 09:44 lastlog
drwxr-xr-x  2 root  root 4,0K nov 18 15:05 openvpn
drwx--  2 root  root 4,0K gen  3 08:42 private
drwx--  2 speech-dispatcher root 4,0K dic 11 23:07 
speech-dispatcher
-rw-r-  1 syslogadm   76M gen 28 19:10 syslog
-rw---  1 root  root  90K gen 27 18:40 
ubuntu-advantage.log
-rw---  1 root  root 6,1K gen 28 18:30 
ubuntu-advantage-timer.log
drwxr-x---  2 root  adm  4,0K gen  6 10:28 
unattended-upgrades
-rw-r--r--  1 root  root 392K gen 28 17:54 
uvcdynctrl-udev.log
-rw-rw-r--  1 root  utmp 179K gen 28 17:56 wtmp
corrado@corrado-n3-jj-0103:~

corrado@corrado-n3-jj-0103:~$ cat /etc/logrotate.d/rsyslog
/var/log/syslog
/var/log/mail.info
/var/log/mail.warn
/va

[Touch-packages] [Bug 1959325] Re: New binutils causes build failures for many RISC-V packages

[Heinrich Schuchardt]

U-Boot, OpenSBI, Linux kernel require patches to build with the new
binutils,e.g.
https://lists.denx.de/pipermail/u-boot/2022-January/473499.html

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

Title:
  New binutils causes build failures for many RISC-V packages

Status in binutils package in Ubuntu:
  Confirmed
Status in binutils source package in Jammy:
  Confirmed

Bug description:
  binutils 2.37.90.20220126-0ubuntu1 changes the -march flags.
  We see a lot of packages not building in proposed anymore: OpenSBI, 
ktexteditor, ...

  Best regards

  Heinrich

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1959325/+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 1959325] Re: New binutils causes build failures for many RISC-V packages

[Heinrich Schuchardt]

Package gcc-riscv64-linux-gnu depends on gcc-10-riscv64-linux-gnu which
is too old for the new binutils. GCC 10 gives an error:

cc1: error: ‘-march=rv64imac_zicsr_zifencei’: unsupported ISA subset ‘z

The cross compiler package needs a respin to match the new binutils.

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

Title:
  New binutils causes build failures for many RISC-V packages

Status in binutils package in Ubuntu:
  Confirmed
Status in binutils source package in Jammy:
  Confirmed

Bug description:
  binutils 2.37.90.20220126-0ubuntu1 changes the -march flags.
  We see a lot of packages not building in proposed anymore: OpenSBI, 
ktexteditor, ...

  Best regards

  Heinrich

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1959325/+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 1953052] Re: In Jammy sound level reset after reboot

[corrado venturini]

I did some tests by changing the volume and inserting and removing the
headphones but I don't see anything in the journalctl.

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

Title:
  In Jammy sound level reset after reboot

Status in alsa-utils package in Ubuntu:
  Confirmed

Bug description:
  After reboot sound level is reset ignoring the level set in previous
  session.

  I manually set the sound output level 
  at next boot the sound is set at a different level (about 70%)

  Expected: the sound level is persistent across power off/on

  What happens : sound level is set at a different level (about 70%)

  Note: this problem does not occur on different partitions of same PC
  running Ubuntu 20.04 or 21.10

  corrado@corrado-p3-jj-1130:~$ apt policy gnome-control-center
  gnome-control-center:
Installed: 1:41.1-1ubuntu1
Candidate: 1:41.1-1ubuntu1
Version table:
   *** 1:41.1-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-p3-jj-1130:~$ inxi -Fx
  System:Host: corrado-p3-jj-1130 Kernel: 5.13.0-19-generic x86_64 bits: 64 
compiler: gcc v: 11.2.0
 Desktop: GNOME 40.5 Distro: Ubuntu 22.04 (Jammy Jellyfish)
  Machine:   Type: Laptop System: Dell product: Inspiron 3793 v: N/A serial: 

 Mobo: Dell model: 0C1PF2 v: A00 serial:  UEFI: 
Dell v: 1.5.0 date: 12/17/2019
  Battery:   ID-1: BAT0 charge: 13.9 Wh (42.1%) condition: 33.0/42.0 Wh (78.7%) 
volts: 11.3 min: 11.4
 model: SWD-ATL3.618 DELL WJPC403 status: Discharging
  CPU:   Info: Quad Core model: Intel Core i5-1035G1 bits: 64 type: MT MCP 
arch: Ice Lake rev: 5 cache:
 L2: 6 MiB
 flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 19046
 Speed: 968 MHz min/max: 400/1000 MHz Core speeds (MHz): 1: 968 2: 
710 3: 706 4: 714 5: 966 6: 712
 7: 724 8: 821
  Graphics:  Device-1: Intel Iris Plus Graphics G1 vendor: Dell driver: i915 v: 
kernel bus-ID: 00:02.0
 Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo 
bus-ID: 1-6:3
 Display: wayland server: X.Org 1.21.1.2 compositor: gnome-shell 
driver: loaded: i915
 note: n/a (using device driver) resolution: 1920x1080~60Hz
 OpenGL: renderer: Mesa Intel UHD Graphics (ICL GT1) v: 4.6 Mesa 
21.2.2 direct render: Yes
  Audio: Device-1: Intel Ice Lake-LP Smart Sound Audio vendor: Dell driver: 
snd_hda_intel v: kernel
 bus-ID: 00:1f.3
 Sound Server-1: ALSA v: k5.13.0-19-generic running: yes
 Sound Server-2: PulseAudio v: 15.0 running: yes
 Sound Server-3: PipeWire v: 0.3.40 running: yes
  Network:   Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell 
driver: r8169 v: kernel port: 3000
 bus-ID: 01:00.0
 IF: enp1s0 state: down mac: 98:e7:43:59:19:19
 Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network 
Adapter vendor: Dell driver: ath10k_pci
 v: kernel bus-ID: 02:00.0
 IF: wlp2s0 state: up mac: d8:12:65:b8:21:b9
  Bluetooth: Device-1: Qualcomm Atheros type: USB driver: btusb v: 0.8 bus-ID: 
1-10:4
 Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: 
enabled,running rfk-block: hardware: no
 software: yes address: D8:12:65:B8:21:BA
  Drives:Local Storage: total: 942.7 GiB used: 11.77 GiB (1.2%)
 ID-1: /dev/nvme0n1 vendor: Toshiba model: KBG40ZNS512G NVMe KIOXIA 
512GB size: 476.94 GiB temp: 24.9 C
 ID-2: /dev/sda vendor: Crucial model: CT500MX500SSD1 size: 465.76 
GiB
  Partition: ID-1: / size: 46.95 GiB used: 11.73 GiB (25.0%) fs: ext4 dev: 
/dev/nvme0n1p3
 ID-2: /boot/efi size: 246 MiB used: 46.4 MiB (18.9%) fs: vfat dev: 
/dev/nvme0n1p1
  Swap:  Alert: No swap data was found.
  Sensors:   System Temperatures: cpu: 27.8 C mobo: N/A
 Fan Speeds (RPM): cpu: 0
  Info:  Processes: 263 Uptime: 31m Memory: 15.4 GiB used: 2.45 GiB (15.9%) 
Init: systemd runlevel: 5 Compilers:
 gcc: N/A Packages: 1785 Shell: Bash v: 5.1.12 inxi: 3.3.07
  corrado@corrado-p3-jj-1130:~$
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2021-11-30 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  Package: gnome-control-center 1:41.1-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Tags:  wayland-session jammy
  Uname: Linux 5.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev

[Touch-packages] [Bug 1957086] Re: Autopkgtest systemd fail against dnsmasq 2.86 (22.04)

[Lukas Märdian]

This should now be solved, as of 249.9-0ubuntu2

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

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

Title:
  Autopkgtest systemd fail against dnsmasq 2.86 (22.04)

Status in dnsmasq package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Fix Committed

Bug description:
  Full log (same on all architectures):
  
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/s/systemd/20220106_214401_24d29@/log.gz

  The test is from systemd:
  https://github.com/systemd/systemd/blob/main/test/networkd-test.py#L619

  Tail of the log:
  ```
  ERROR: test_resolved_domain_restricted_dns (__main__.DnsmasqClientTest)
  resolved: domain-restricted DNS servers
  --
  Traceback (most recent call last):
File "/tmp/autopkgtest.NdIvJq/build.fBQ/src/test/networkd-test.py", line 
678, in test_resolved_domain_restricted_dns
  out = subprocess.check_output(['resolvectl', 'query', 'math.lab'])
File "/usr/lib/python3.9/subprocess.py", line 424, in check_output
  return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
File "/usr/lib/python3.9/subprocess.py", line 528, in run
  raise CalledProcessError(retcode, process.args,
  subprocess.CalledProcessError: Command '['resolvectl', 'query', 'math.lab']' 
returned non-zero exit status 1.
  ```

  
  Tagging update-excuse to be shown in excuses

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1957086/+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 1959363] Re: Update to libXfixes 6.x

[Bug Watch Updater]

** Changed in: libxfixes (Debian)
   Status: Unknown => New

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

Title:
  Update to libXfixes 6.x

Status in libxfixes package in Ubuntu:
  New
Status in libxfixes package in Debian:
  New

Bug description:
  Update to libXfixes 6.x

  https://gitlab.freedesktop.org/xorg/lib/libxfixes/-/tags

  It is a prerequisite to build mutter 42.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxfixes/+bug/1959363/+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 1959425] [NEW] headphones, no sound from onboard card

[Mac]

Public bug reported:

I have a GA-Z77X-UD5H (rev. 1.0) that I recently installed Ubuntu 21.10

The Gigabyte website says that the motherboard sound controller supports
the Realtek ALC898 codec.

I created an Alsa report; see link below:

http://alsa-project.org/db/?f=43a1cb48648835a145be78f7bf474d1507d69124

Although I can't get the sound working through the headphone using the
jacks at the back of the computer, the sound does work via the GPU and
monitor. The headphones function as expected under Windows 10.

alsa-base is (1.0.25+dfsg-0ubuntu7).

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

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

Title:
  headphones, no sound from onboard card

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I have a GA-Z77X-UD5H (rev. 1.0) that I recently installed Ubuntu
  21.10

  The Gigabyte website says that the motherboard sound controller
  supports the Realtek ALC898 codec.

  I created an Alsa report; see link below:

  http://alsa-project.org/db/?f=43a1cb48648835a145be78f7bf474d1507d69124

  Although I can't get the sound working through the headphone using the
  jacks at the back of the computer, the sound does work via the GPU and
  monitor. The headphones function as expected under Windows 10.

  alsa-base is (1.0.25+dfsg-0ubuntu7).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1959425/+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 1932329] Re: Benchmark if we can compress kernel modules

[Dimitri John Ledkov]

** Description changed:

+ --- initramfs-tools
+ 
+ [Impact]
+ 
+  * Initramfs-tools already supports compressed kernel modules. However,
+ in focal it does so inefficiently. It is always better to have a
+ compressed initramfs of uncommpressed kernel modules, than a compressed
+ initrd of compressed kernel modules. Thus when kernel module compression
+ is turned on, it is prudent for initramfs-tools to pre-uncompress kernel
+ modules when building initramfs.
+ 
+ [Test Plan]
+ 
+  * Compress all kernel modules with xz for a current kernel, check that
+ all of them have .ko.xz extension and no .ko ones available
+ 
+  * Rerun depmod
+ 
+  * Update initramfs with update-initramfs -u
+ 
+  * lsinitramfs contents and check that all kernel modules are present,
+ and are uncompressed (.ko extension)
+ 
+ [Where problems could occur]
+ 
+  * This optimization for compressed kernel modules will make initramfs
+ build time longer (due to decompression) whilst improving bootspeed
+ (overall smaller size of the initrd).
+ 
+ [Other Info]
+  
+  * Original bug report re kernel feature
+ 
+ 
  Symbol: MODULE_COMPRESS_ZSTD [=n]
  Type  : bool
  
  = Impacts to measure and observe =
  
  == Disk space ==
  
  * Inspect linux-modules-* and linux-modules-extra* deb package
  Installed-Size and Download-Size changes, i.e.
  
  $ apt show linux-modules-5.8.0-53-generic linux-modules-
  extra-5.8.0-53-generic  | grep -e Package: -e Size:
  
  Package: linux-modules-5.8.0-53-generic
  Installed-Size: 81.5 MB
  Download-Size: 15.5 MB
  
  Package: linux-modules-extra-5.8.0-53-generic
  Installed-Size: 215 MB
  Download-Size: 41.5 MB
  
  In theory, there should not be a significant change in the Download-
  size. It is desired that there is a significant reduction in Installed-
  Size. Modules take up about 300MB and normally one has upto three kernel
  version installed, resulting in about of 1GB of disk space that one
  constantly pays for.
  
  == Boot Speed ==
  
  In theory, boot speed may either improve or regress. It depends if disk
  IO is slower than decompression speed, meaning loading compressed
  modules is faster.
  
  Also one has to observe the changes in the initrd size. zstd(zstd)
  compression may result in slight growth, which shouldn't impact boot
  speed too much.
  
  = Outcomes =
  
  If installed size savings can be achieved without regressing bootspeed
  we should enable CONFIG_MODULE_COMPRESS_ZSTD=y by default.

** Description changed:

  --- initramfs-tools
  
  [Impact]
  
-  * Initramfs-tools already supports compressed kernel modules. However,
+  * Initramfs-tools already supports compressed kernel modules. However,
  in focal it does so inefficiently. It is always better to have a
  compressed initramfs of uncommpressed kernel modules, than a compressed
  initrd of compressed kernel modules. Thus when kernel module compression
  is turned on, it is prudent for initramfs-tools to pre-uncompress kernel
  modules when building initramfs.
  
  [Test Plan]
  
-  * Compress all kernel modules with xz for a current kernel, check that
+  * Compress all kernel modules with xz for a current kernel, check that
  all of them have .ko.xz extension and no .ko ones available
  
-  * Rerun depmod
+  * Rerun depmod
  
-  * Update initramfs with update-initramfs -u
+  * Update initramfs with update-initramfs -u
  
-  * lsinitramfs contents and check that all kernel modules are present,
+  * lsinitramfs contents and check that all kernel modules are present,
  and are uncompressed (.ko extension)
  
  [Where problems could occur]
  
-  * This optimization for compressed kernel modules will make initramfs
+  * This optimization for compressed kernel modules will make initramfs
  build time longer (due to decompression) whilst improving bootspeed
  (overall smaller size of the initrd).
  
  [Other Info]
-  
-  * Original bug report re kernel feature
  
+  * Original bug report re kernel feature
+ 
+ --- linux
  
  Symbol: MODULE_COMPRESS_ZSTD [=n]
  Type  : bool
  
  = Impacts to measure and observe =
  
  == Disk space ==
  
  * Inspect linux-modules-* and linux-modules-extra* deb package
  Installed-Size and Download-Size changes, i.e.
  
  $ apt show linux-modules-5.8.0-53-generic linux-modules-
  extra-5.8.0-53-generic  | grep -e Package: -e Size:
  
  Package: linux-modules-5.8.0-53-generic
  Installed-Size: 81.5 MB
  Download-Size: 15.5 MB
  
  Package: linux-modules-extra-5.8.0-53-generic
  Installed-Size: 215 MB
  Download-Size: 41.5 MB
  
  In theory, there should not be a significant change in the Download-
  size. It is desired that there is a significant reduction in Installed-
  Size. Modules take up about 300MB and normally one has upto three kernel
  version installed, resulting in about of 1GB of disk space that one
  constantly pays for.
  
  == Boot Speed ==
  
  In theory, boot speed may either improve or regress. It depends if disk
  IO is slower than decompression speed, meaning loading compresse

Re: [Touch-packages] [Bug 1955347] Re: rsync works bad with encfs now

[Micouin Claude]

Hi Utkarsh Gupta,
I understand better what is a step-by-step reproducer :-)
I have tried to downgrade rsync with apt-get install rsync=3.1.3-8 and
there is no change. But the version who seemed to work on my PC was
older rsync_3.1.2-2.1
I've tried to install it but apt-get refused.
Is there a way to do this installation?
Thanks.

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

Title:
  rsync works bad with encfs now

Status in rsync package in Ubuntu:
  Incomplete

Bug description:
  Hello,
  I think rsync works bad with encfs now.

  When root uses it, rsync cannot read a directory encrypted with encfs
  by a user. More precisely, it cannot read the mounted directory, the
  virtual one where the user can read the datas.

  Until now there was only a warning like this
  "rsync: readlink_stat("/home/claude/Documents_chiffres") failed:
  Permission denied (13)"
  and the software went on working (only ignoring the content of the mounted 
directory and of course without saving this content)

  But recently there is this more:
  "IO error encountered -- skipping file deletion"
  and because of this "skipping file deletion", the software can't work 
normally. The destination gets bigger more and more because the deleted files 
in the source are not deleted in the destination.

  Thanks for reading me.
  rsync 3.1.3-8ubuntu0.1
  Description:Ubuntu 20.04.3 LTS
  Release:20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1955347/+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 1959363] Re: Update to libXfixes 6.x

[Hans Joachim Desserud]

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

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

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

Title:
  Update to libXfixes 6.x

Status in libxfixes package in Ubuntu:
  New
Status in libxfixes package in Debian:
  Unknown

Bug description:
  Update to libXfixes 6.x

  https://gitlab.freedesktop.org/xorg/lib/libxfixes/-/tags

  It is a prerequisite to build mutter 42.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxfixes/+bug/1959363/+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 1942260] Re: compress firmware in /lib/firmware

[Dimitri John Ledkov]

** Description changed:

+ -- initramfs-tools
+ 
+ [Impact]
+ 
+  * linux supports xz compressed linux-firmware which saves disk space.
+ In focal, initramfs-tools only knows how to included uncompressed
+ firmware files (even when kernel supports loading compressed ones).
+ Newer releases of linux-firmware may use compressed firmware files only,
+ in such cases it would be nice for focal's initramfs-tools to support
+ compressed firmware files in case of partial or incomplete upgrades
+ (i.e. linux-firmware force installed or upgraded, without newer
+ initramfs-tools). The proposed changes to initramfs-tools are backwards
+ and forwards compatible, they prefer to include uncompressed firmware
+ files; and if missing, include compressed firmware files in their
+ uncompressed form. Thus maintaining compatibility with any kernels,
+ irrespective of compressed/uncompressed firmware inputs.
+ 
+ [Test Plan]
+ 
+  * Compress all files shipped by linux-firmware with xz
+ 
+  * Rebuild initrd
+ 
+  * Check that all the same firmware files are still included in the
+ initramfs, in their uncompressed form as before
+ 
+ [Where problems could occur]
+ 
+  * This SRU is precautionary to prevent accidental installation of
+ compressed linux-firmware from generating incorrect initramfs. It should
+ be noted that whilst initramfs-tools would create a compatible initramfs
+ with any kernels, pre-v5.3 kernels do not support xz compressed firmware
+ files at runtime. Mixing this new initramfs with compressed firmwares
+ and pre 5.3 kernels may lead to expectations of supporting compressed
+ firmware files with them only working at initrd stage and not at
+ runtime.
+ 
+ [Other Info]
+ Original bug report
+ 
  Some facts:
-  - The linux kernel has supported loading xz compressed firmware since 5.3
-  - The size of /lib/firmware in impish is ~650Mb (and growing)
-  - The compressed size of firmware could be ~230Mb
+  - The linux kernel has supported loading xz compressed firmware since 5.3
+  - The size of /lib/firmware in impish is ~650Mb (and growing)
+  - The compressed size of firmware could be ~230Mb
  
  It would be nice to install compressed firmware to save space.
  
  Here are the plans from the Fedora project:
  https://fedoraproject.org/wiki/Changes/CompressKernelFirmware

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

Title:
  compress firmware in /lib/firmware

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in linux-firmware package in Ubuntu:
  New
Status in linux-firmware-raspi2 package in Ubuntu:
  New

Bug description:
  -- initramfs-tools

  [Impact]

   * linux supports xz compressed linux-firmware which saves disk space.
  In focal, initramfs-tools only knows how to included uncompressed
  firmware files (even when kernel supports loading compressed ones).
  Newer releases of linux-firmware may use compressed firmware files
  only, in such cases it would be nice for focal's initramfs-tools to
  support compressed firmware files in case of partial or incomplete
  upgrades (i.e. linux-firmware force installed or upgraded, without
  newer initramfs-tools). The proposed changes to initramfs-tools are
  backwards and forwards compatible, they prefer to include uncompressed
  firmware files; and if missing, include compressed firmware files in
  their uncompressed form. Thus maintaining compatibility with any
  kernels, irrespective of compressed/uncompressed firmware inputs.

  [Test Plan]

   * Compress all files shipped by linux-firmware with xz

   * Rebuild initrd

   * Check that all the same firmware files are still included in the
  initramfs, in their uncompressed form as before

  [Where problems could occur]

   * This SRU is precautionary to prevent accidental installation of
  compressed linux-firmware from generating incorrect initramfs. It
  should be noted that whilst initramfs-tools would create a compatible
  initramfs with any kernels, pre-v5.3 kernels do not support xz
  compressed firmware files at runtime. Mixing this new initramfs with
  compressed firmwares and pre 5.3 kernels may lead to expectations of
  supporting compressed firmware files with them only working at initrd
  stage and not at runtime.

  [Other Info]
  Original bug report

  Some facts:
   - The linux kernel has supported loading xz compressed firmware since 5.3
   - The size of /lib/firmware in impish is ~650Mb (and growing)
   - The compressed size of firmware could be ~230Mb

  It would be nice to install compressed firmware to save space.

  Here are the plans from the Fedora project:
  https://fedoraproject.org/wiki/Changes/CompressKernelFirmware

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


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

[Touch-packages] [Bug 1958887] Re: Please merge logrotate 3.19.0-1 (main) from Debian unstable (main)

[Launchpad Bug Tracker]

This bug was fixed in the package logrotate - 3.19.0-1ubuntu1

---
logrotate (3.19.0-1ubuntu1) jammy; urgency=low

  * Merge from Debian unstable (LP: #1958887). Remaining changes:
- debian/control: Drop mailx to Suggests for Ubuntu; it's only used
  on request, and we don't configure an MTA by default.
- debian/patches/ubuntu/logrotate.conf-use-group-adm.patch:
  Use group 'adm' by default when rotating logs.

logrotate (3.19.0-1) unstable; urgency=medium

  * New upstream version 3.19.0
- More strict configuration parser, e.g. invalid lines are no longer
  accepted (Closes: #1002022)
- Files with multiple hard links are no longer rotated by default

  * d/rules: enable LTO
  * d/copyright: update years and upstream names
  * d/control: bump to std version 4.6.0 (no further changes)
  * d/patches: add patch to drop ELF header from test case file

 -- Alexandre Ghiti   Mon, 24 Jan 2022
16:37:01 +0100

** Changed in: logrotate (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 logrotate in Ubuntu.
https://bugs.launchpad.net/bugs/1958887

Title:
  Please merge logrotate 3.19.0-1 (main) from Debian unstable (main)

Status in logrotate package in Ubuntu:
  Fix Released

Bug description:
  Please merge logrotate 3.19.0-1 (main) from Debian unstable (main)

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


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

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

[Dimitri John Ledkov]

** Description changed:

- kmod add zstd support
+ [Impact]
  
- * v27+ needs patches cherrypicked from v28
+  * To safe diskspace, upcoming devel series / hwe kernels may turn on
+ zstd kernel module compression. Kmod since impish support zstd support.
+ But in order to keep hwe kernels at parity, or allow inspecting jammy
+ modules from focal host, it would be beneficial for kmod in focal to
+ support zstd compressed modules.
  
- * v28+ needs new build-time deps adjusted
+ [Test Plan]
+ 
+  * Pick any kernel module
+ 
+  * Compress it with zstd: $ zstd *.ko
+ 
+  * Check that modinfo can read it: $ modinfo *.ko.zst
+ 
+ [Where problems could occur]
+ 
+  * kmod will gain a new dependecy on libzstd1, however it should already
+ be present, because dpkg in focal depends on libzstd1 already.
+ 
+  * initramfs-tools already supports compressed modules, but in focal at
+ the moment it does so in an inefficient manner (regresses bootspeed),
+ this has been improved in
+ https://launchpad.net/ubuntu/+source/initramfs-tools/0.140ubuntu8 and is
+ yet to be SRUed into Focal.

** Also affects: kmod (Ubuntu Impish)
   Importance: Undecided
   Status: New

** Also affects: kmod (Ubuntu Jammy)
   Importance: Undecided
   Status: Fix Released

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

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

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

Title:
  kmod add zstd support

Status in kmod package in Ubuntu:
  Fix Released
Status in kmod source package in Focal:
  New
Status in kmod source package in Impish:
  Fix Released
Status in kmod source package in Jammy:
  Fix Released

Bug description:
  [Impact]

   * To safe diskspace, upcoming devel series / hwe kernels may turn on
  zstd kernel module compression. Kmod since impish support zstd
  support. But in order to keep hwe kernels at parity, or allow
  inspecting jammy modules from focal host, it would be beneficial for
  kmod in focal to support zstd compressed modules.

  [Test Plan]

   * Pick any kernel module

   * Compress it with zstd: $ zstd *.ko

   * Check that modinfo can read it: $ modinfo *.ko.zst

  [Where problems could occur]

   * kmod will gain a new dependecy on libzstd1, however it should
  already be present, because dpkg in focal depends on libzstd1 already.

   * initramfs-tools already supports compressed modules, but in focal
  at the moment it does so in an inefficient manner (regresses
  bootspeed), this has been improved in
  https://launchpad.net/ubuntu/+source/initramfs-tools/0.140ubuntu8 and
  is yet to be SRUed into Focal.

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


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

[Touch-packages] [Bug 1958904] Re: autopkgtest is failing on jammy with "no space left on device"

[Dimitri John Ledkov]

I wonder if I should have included feature backports to support
compressed kernel modules & coompressed firmware files
https://launchpad.net/ubuntu/+source/initramfs-tools/0.140ubuntu8

This would be actually useful, and would allow us to enable compressed
kernel modules for jammy and hwe-5.15 when it lands in 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/1958904

Title:
  autopkgtest is failing on jammy with "no space left on device"

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Bionic:
  Invalid
Status in initramfs-tools source package in Focal:
  Fix Committed
Status in initramfs-tools source package in Impish:
  Fix Committed

Bug description:
  [Impact]
  In debian/tests/prep-image we create an image file of 1GB, but recent 
jammy/focal cloud images are (barely) bigger than that, for example the current 
one uncompressed is 1001MB...

  Example of a test failure:
  
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/i/initramfs-tools/20220126_160323_8bcd1@/log.gz

  Maybe we should consider to create image files of 2GB or even bigger,
  considering that we are only going to allocate the space that is
  actually needed, because we create the file using truncate.

  [Test Plan]
  Run autotestpkg tests from initramfs-tools package. The "net" test is the one 
that depends on the image created by 'prep-image'. The testcase should complete 
successfully without the temporary image running out of space.

  [Where problems could occur]
  The creation of a larger image for the tests could fail if the filesystem of 
the test system is low on disk space. However, as mentioned before, as the 
image file is created using 'truncate', only the necessary space needed to 
uncompress the cloudimg will be used on the filesystem. Apart from that, we 
assume that 2GB of free space should be available on every test system used for 
Ubuntu autopkgtest.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958904/+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 1664369] Re: Super key always applied for VNC session

[Paul White ]

** Package changed: xorg (Ubuntu) => metacity (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/1664369

Title:
  Super key always applied for VNC session

Status in metacity package in Ubuntu:
  New

Bug description:
  This a regression report for bug 1440570 with the latest package
  installed on 14.04 Trusty.

  Problem still reproduces exactly as specified.  Every time I press 'N'
  in terminal over VNC, a new window is opened.  I don't want to delete
  my super key mappings, they are quite useful when interacting with the
  machine locally but I also need remote access to things like a web
  browser and VNC is most useful for this.

  Unfortunately the super key is constantly on.  I saw that 1440570 was
  closed with a fix, I might have undone the fix because I used gnome-
  tweak-tool to swap my Alt-Win keys (Alt-Win behavior under typing).
  Even after switching this back however, the problem persists over VNC,
  making it unusable.

  Let me know what I can do to help debug.

  Output of apt list metacity:

  Listing... Done
  metacity/trusty-updates,now 1:2.34.13-0ubuntu4.1 amd64 [installed]

  Output of lsb_release -rd:

  Description:Ubuntu 14.04.5 LTS
  Release:14.04

  #regression-update

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-62.83~14.04.1-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Mon Feb 13 11:40:39 2017
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150720-0
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   oem-audio-hda-daily-lts-xenial, 0.201611160201~ubuntu14.04.1, 
4.4.0-62-generic, x86_64: installed
   synaptic-i2c-hid-3.13.0-32-backport, 1.6.4: added
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1912] (rev 06) (prog-if 
00 [VGA controller])
 Subsystem: Dell Device [1028:06b9]
  InstallationDate: Installed on 2016-12-16 (59 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150720-04:06
  MachineType: Dell Inc. OptiPlex 7040
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-62-generic.efi.signed 
root=UUID=e4b640d9-85ce-43f1-9369-2744897fd9f5 ro pcie_aspm=off quiet splash 
vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/12/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.9
  dmi.board.name: 0Y7WYT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.9:bd09/12/2016:svnDellInc.:pnOptiPlex7040:pvr:rvnDellInc.:rn0Y7WYT:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.name: OptiPlex 7040
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Feb  8 15:18:04 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   16485 
   vendor DEL
  xserver.version: 2:1.18.3-1ubuntu2.3~trusty1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1664369/+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 1357469] Re: Display-Helligkeit läßt sich nicht dauerhaft fest einstellen.

[Paul White ]

We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.

Ubuntu 14.04 (trusty) reached end-of-life on April 25,2019.

Do you still see a problem related to the one that you reported when
using a currently supported version of Ubuntu? Please let us know if you
do otherwise this report can be left to expire in approximately 60 days
time.

Thank you for helping make Ubuntu better.


** Description changed:

  Beim Hochfahren wird immer die höchste Helligkeit eingestellt.
  Die Einstellung einer geringeren Helligkeit geht beim Herunterfahren des 
Systems wieder verloren.
+ 
+ Google translates as:
+ When starting up, the highest brightness is always set.
+ A lower brightness setting is lost again when the system is shut down.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-33.58-generic 3.13.11.4
  Uname: Linux 3.13.0-33-generic i686
  .tmp.unity.support.test.0:
-  
+ 
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: i386
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Aug 15 18:12:46 2014
  DistUpgraded: 2014-08-12 11:46:20,854 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
-  Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
-Subsystem: ASUSTeK Computer Inc. Device [1043:145d]
+  Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
+    Subsystem: ASUSTeK Computer Inc. Device [1043:145d]
  InstallationDate: Installed on 2013-12-14 (243 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 
(20130213)
  MachineType: ASUSTeK COMPUTER INC. X551CA
  ProcEnviron:
-  LANGUAGE=de_DE
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=de_DE.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=de_DE
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=de_DE.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-33-generic 
root=UUID=0eed76a2-b2cc-45da-8c73-2c81a4b157c3 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to trusty on 2014-08-12 (3 days ago)
  dmi.bios.date: 10/23/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X551CA.207
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X551CA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX551CA.207:bd10/23/2013:svnASUSTeKCOMPUTERINC.:pnX551CA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX551CA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X551CA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.11.2+14.04.20140714-0ubuntu1
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Fri Aug 15 17:42:04 2014
  xserver.configfile: default
  xserver.errors:
-  
+ 
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
-  product id5543 
-  vendor CMO
+  product id5543
+  vendor CMO
  xserver.version: 2:1.15.1-0ubuntu2

** Summary changed:

- Display-Helligkeit läßt sich nicht dauerhaft fest einstellen.
+ Display-Helligkeit läßt sich nicht dauerhaft fest einstellen. (Display 
brightness cannot be set permanently)

** Changed in: xorg (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/1357469

Title:
  Display-Helligkeit läßt sich nicht dauerhaft fest einstellen. (Display
  brightness cannot be set permanently)

[Touch-packages] [Bug 1585150] Re: cannot open kubuntu desktop nor xubuntu desktop

[Paul White ]

We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.

Ubuntu 14.04 (trusty) reached end-of-life on April 25,2019.

Do you still see a problem related to the one that you reported when
using a currently supported version of Ubuntu? Please let us know if you
do otherwise this report can be left to expire in approximately 60 days
time.

Thank you for helping make Ubuntu better.


** 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/1585150

Title:
  cannot open kubuntu desktop nor xubuntu desktop

Status in Ubuntu:
  Incomplete

Bug description:
  i'm new in GPU computing and after i installed nvidia-361.28 and cuda-7.5 all 
the windows fell.
  wua...what a huge mess
  cannot even log in when i reboot my system.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.19.0-59.66~14.04.1-generic 3.19.8-ckt19
  Uname: Linux 3.19.0-59-generic x86_64
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.14.1-0ubuntu3.20
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue May 24 18:27:31 2016
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GM107 [GeForce GTX 750 Ti] [10de:1380] (rev a2) (prog-if 
00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Device [1458:362d]
  InstallationDate: Installed on 2015-12-08 (168 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  MachineType: Gigabyte Technology Co., Ltd. B85M-D3V
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-59-generic 
root=UUID=ab447542-e029-488c-92f4-58169f0b0af6 ro quiet splash vt.handoff=7
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/17/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FB
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B85M-D3V
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFB:bd01/17/2014:svnGigabyteTechnologyCo.,Ltd.:pnB85M-D3V:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85M-D3V:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: B85M-D3V
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.65+git20151026.c745e541-0ubuntu0ricotz~trusty
  version.libgl1-mesa-dri: libgl1-mesa-dri 
11.0.4~git20151026+11.0.ec14e6f8-0ubuntu0ricotz~trusty
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 
11.0.4~git20151026+11.0.ec14e6f8-0ubuntu0ricotz~trusty
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.4.99+git20140806.fbf575cb-0ubuntu0sarvatt~trusty
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20151202.da9ad388-0ubuntu0sarvatt~trusty
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11+git20141030.3fb97d78-0ubuntu0sarvatt~trusty2
  xserver.bootTime: Tue May 24 18:22:03 2016
  xserver.configfile: /etc/X11/xorg.conf
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputUSB Optical MouseMOUSE, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.15.1-0ubuntu2.7

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

[Timo Aaltonen]

Hello Andrea, or anyone else affected,

Accepted initramfs-tools into impish-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/initramfs-
tools/0.140ubuntu6.1 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-
impish to verification-done-impish. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-impish. In either case, without details of your testing we will
not be able to proceed.

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

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

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

Title:
  autopkgtest is failing on jammy with "no space left on device"

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Bionic:
  Invalid
Status in initramfs-tools source package in Focal:
  Fix Committed
Status in initramfs-tools source package in Impish:
  Fix Committed

Bug description:
  [Impact]
  In debian/tests/prep-image we create an image file of 1GB, but recent 
jammy/focal cloud images are (barely) bigger than that, for example the current 
one uncompressed is 1001MB...

  Example of a test failure:
  
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/i/initramfs-tools/20220126_160323_8bcd1@/log.gz

  Maybe we should consider to create image files of 2GB or even bigger,
  considering that we are only going to allocate the space that is
  actually needed, because we create the file using truncate.

  [Test Plan]
  Run autotestpkg tests from initramfs-tools package. The "net" test is the one 
that depends on the image created by 'prep-image'. The testcase should complete 
successfully without the temporary image running out of space.

  [Where problems could occur]
  The creation of a larger image for the tests could fail if the filesystem of 
the test system is low on disk space. However, as mentioned before, as the 
image file is created using 'truncate', only the necessary space needed to 
uncompress the cloudimg will be used on the filesystem. Apart from that, we 
assume that 2GB of free space should be available on every test system used for 
Ubuntu autopkgtest.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958904/+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 1958904] Re: autopkgtest is failing on jammy with "no space left on device"

[Timo Aaltonen]

Hello Andrea, or anyone else affected,

Accepted initramfs-tools into focal-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/initramfs-
tools/0.136ubuntu6.7 in a few hours, and then in the -proposed
repository.

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

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

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

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

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

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

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

** Tags added: verification-needed-impish

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

Title:
  autopkgtest is failing on jammy with "no space left on device"

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Bionic:
  Invalid
Status in initramfs-tools source package in Focal:
  Fix Committed
Status in initramfs-tools source package in Impish:
  Fix Committed

Bug description:
  [Impact]
  In debian/tests/prep-image we create an image file of 1GB, but recent 
jammy/focal cloud images are (barely) bigger than that, for example the current 
one uncompressed is 1001MB...

  Example of a test failure:
  
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/i/initramfs-tools/20220126_160323_8bcd1@/log.gz

  Maybe we should consider to create image files of 2GB or even bigger,
  considering that we are only going to allocate the space that is
  actually needed, because we create the file using truncate.

  [Test Plan]
  Run autotestpkg tests from initramfs-tools package. The "net" test is the one 
that depends on the image created by 'prep-image'. The testcase should complete 
successfully without the temporary image running out of space.

  [Where problems could occur]
  The creation of a larger image for the tests could fail if the filesystem of 
the test system is low on disk space. However, as mentioned before, as the 
image file is created using 'truncate', only the necessary space needed to 
uncompress the cloudimg will be used on the filesystem. Apart from that, we 
assume that 2GB of free space should be available on every test system used for 
Ubuntu autopkgtest.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1958904/+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 1690512] Re: shutdown/restart/suspend freezes laptop on intel graphics

[Paul White ]

We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.

Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.

Do you still see a problem related to the one that you reported when
using a currently supported version of Ubuntu? Please let us know if you
do otherwise this report can be left to expire in approximately 60 days
time.

Thank you for helping make Ubuntu better.


** Changed in: linux (Ubuntu)
   Status: Confirmed => Incomplete

** Changed in: xorg (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/1690512

Title:
  shutdown/restart/suspend freezes laptop on intel graphics

Status in intel-microcode package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Incomplete
Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I'm not sure where to report this under, so please bear with me.
  Reporting this bug using ubuntu-bug just crashes my system if im using
  intel graphics, I had to switch to nvidia graphics just to file this
  bug report so the automatically attached log files may not be a good
  representation of the problem.

  I've attached the syslog and kern.log files below.

  PROBLEM:

  When using intel graphics:

  Whenever I close the laptop lid or restart / shutdown using GUI or
  terminal commands, it goes into a black screen with a single "_" at
  the top left corner, and hangs. Only long-pressing (hard reset) the
  power button would shut down the computer.

  However, when I use sudo prime-select nvidia to switch over to nvidia,
  everything works fine.log

  I have tried many things, and all do not work. I have attached the
  logs for /var/log/syslog and /var/log/kern.log below.

  Attempts so far:

  1)Tried installing new intel drivers from Updated kernel to 4.8 now
  missing firmware warnings --> Did not work. Issue persists

  2) Tried upgrading kernel from 4.8 to 4.10.15 --> Did not work.
  Problem got worse. Instead of the normal login screen, it gives a
  terminal login screen and hangs.

  3) Tried the fix to nvidia-prime
  https://askubuntu.com/a/884506/547039, but both the poweron.sh and
  poweroff.sh script hangs my laptop instead.

  4) Tried sudo swapoff -a && systemctl poweroff as a workaround, no
  avail.

  5) Tried changing GRUB_CMDLINE_LINUX_DEFAULT="quiet splash" to
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash acpi=force" Does not work
  either.

  Additional note:
  'sudo lshw -C display' on intel graphics outputs PCI(sysfs) then laptop 
freezes.

  LOG FILES:
  /var/log/syslog
  https://codeshare.io/5XOPwM

  /var/log/kern.log
  https://codeshare.io/aJp6nq

  specs:

  Intel 7700HQ, NVIDIA 1060GTX, kernel 4.8, Ubuntu 16.04

  Would really appreciate your help. Thank you!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-51.54~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-51-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  381.22  Thu May  4 00:55:03 
PDT 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat May 13 17:06:20 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-77-generic, x86_64: installed
   bbswitch, 0.8, 4.8.0-49-generic, x86_64: installed
   bbswitch, 0.8, 4.8.0-51-generic, x86_64: installed
   nvidia-381, 381.22, 4.8.0-51-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
     Subsystem: CLEVO/KAPOK Computer Device [1558:65a1]
   NVIDIA Corporation Device [10de:1c20] (rev a1) (prog-if 00 [VGA controller])
     Subsystem: CLEVO/KAPOK Computer Device [1558:65a1]
  InstallationDate: Installed on 2017-03-30 (43 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f2:b5a7 Chicony Electronics Co., Ltd
   Bus 001 Device 003: ID 8087:0a2b Intel Corp.
   Bus 001 Device 002: ID 0483:374b STMicroelect

[Touch-packages] [Bug 1687870] Re: Can not detect external screen when docking laptop

[Paul White ]

We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.

Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.

Do you still see a problem related to the one that you reported when
using a currently supported version of Ubuntu? Please let us know if you
do otherwise this report can be left to expire in approximately 60 days
time.

Thank you for helping make Ubuntu better.


** 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/1687870

Title:
  Can not detect external screen when docking laptop

Status in Ubuntu:
  Incomplete

Bug description:
  My W540 can not detect my external screen when I arrive at work after
  my laptop have been used at home with no external screen and suspended
  on the way to work. Sometimes it does detect it. Sometimes I can un-
  dock and dock again and it works. Sometimes it never works when I am
  redocking.

  After reboot it works fine.

  It worked with Ubuntu 14.04 on the same HW.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-75.96-generic 4.4.59
  Uname: Linux 4.4.0-75-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,mousepoll,gnomecompat,imgpng,move,regex,place,resize,wall,animation,snap,grid,unitymtgrabhandles,vpswitch,workarounds,session,fade,expo,ezoom,scale,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed May  3 09:14:10 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.32, 4.4.0-70-generic, x86_64: installed
   virtualbox, 5.0.32, 4.4.0-71-generic, x86_64: installed
   virtualbox, 5.0.32, 4.4.0-72-generic, x86_64: installed
   virtualbox, 5.0.32, 4.4.0-75-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:221e]
   NVIDIA Corporation GK107GLM [Quadro K1100M] [10de:0ff6] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo GK107GLM [Quadro K1100M] [17aa:221e]
  InstallationDate: Installed on 2017-02-16 (75 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: LENOVO 20BHS0BM00
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-75-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/12/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GNET70WW (2.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BHS0BM00
  dmi.board.vendor: LENOVO
  dmi.board.version: 0B98401 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGNET70WW(2.18):bd01/12/2015:svnLENOVO:pn20BHS0BM00:pvrThinkPadW540:rvnLENOVO:rn20BHS0BM00:rvr0B98401WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 20BHS0BM00
  dmi.product.version: ThinkPad W540
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed May  3 09:11:54 2017
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   NOUVEAU(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   38562 
   vendor MEI
  xserver.version: 2:1.18.4-0ubuntu0.2

To manage notifications about this bu

[Touch-packages] [Bug 1591715] Re: Black background and image

[Paul White ]

We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.

Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.

Do you still see a problem related to the one that you reported when
using a currently supported version of Ubuntu? Please let us know if you
do otherwise this report can be left to expire in approximately 60 days
time.

Thank you for helping make Ubuntu better.


** 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/1591715

Title:
  Black background and image

Status in Ubuntu:
  Incomplete

Bug description:
  Qt Creator 3.5.1
  Based on Qt 5.5.1 (GCC 5.2.1 20151129, 64 bit)

  It happens always when I open ubuntu-sdk

  I think It is a graphics bug of QT library or I don't have a package
  installed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun Jun 12 18:16:35 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.18, 4.4.0-22-generic, x86_64: installed
   virtualbox, 5.0.18, 4.4.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M 
Series] [1002:6760] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Radeon HD 7470M [1043:2002]
  MachineType: ASUSTeK Computer Inc. K54HR
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=f5309739-ba9f-41fa-abaa-4b6bd1e6c9c1 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/13/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K54HR.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K54HR
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK54HR.206:bd08/13/2012:svnASUSTeKComputerInc.:pnK54HR:pvr1.0:rvnASUSTeKComputerInc.:rnK54HR:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.name: K54HR
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK Computer Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sun Jun 12 12:00:20 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs: Output  HDMI-0
LVDS   VGA-0
  xserver.version: 2:1.18.3-1ubuntu2.2
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1591715/+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 1667958] Re: Mouse becomes erratiic after a while

[Paul White ]

We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.

Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.

Do you still see a problem related to the one that you reported when
using a currently supported version of Ubuntu? Please let us know if you
do otherwise this report can be left to expire in approximately 60 days
time.

Thank you for helping make Ubuntu better.


** Changed in: xorg (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/1667958

Title:
  Mouse becomes erratiic after a while

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Standard external usb mouse, after the system has been up for a variable 
time, sometimes a few hours sometimes 2 days the mouse does not properly move 
around the screen and it also does not properly respond to right and left 
click, it will take many attempts before the button presses are recognised.
  A reboot does fix it, but it should not need rebooting so often.

  xorg was used because it seems to be the xorg mouse drivers that are
  in use.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  Uname: Linux 4.4.0-64-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Feb 25 18:15:16 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1912] (rev 06) (prog-if 
00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Skylake Integrated Graphics 
[1458:d000]
  InstallationDate: Installed on 2016-05-03 (297 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Gigabyte Technology Co., Ltd. Z170X-UD5
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed 
root=UUID=4db7fc40-87b9-494c-8c02-5b4c4ff8abc8 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/15/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F5j
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170X-UD5-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF5j:bd01/15/2016:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-UD5:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-UD5-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: Z170X-UD5
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Feb 23 07:57:52 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   30934 
   vendor BNQ
  xserver.version: 2:1.18.4-0ubuntu0.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1667958/+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 1668389] Re: Brightness doesnt change.

[Paul White ]

We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.

Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.

Do you still see a problem related to the one that you reported when
using a currently supported version of Ubuntu? Please let us know if you
do otherwise this report can be left to expire in approximately 60 days
time.

Thank you for helping make Ubuntu better.


** Changed in: xorg (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/1668389

Title:
  Brightness doesnt change.

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  It is decaying my battery life.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
  Uname: Linux 4.4.0-64-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Feb 28 01:51:12 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:397d]
  InstallationDate: Installed on 2017-02-06 (21 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO HuronRiver Platform
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-64-generic.efi.signed 
root=UUID=1c4be268-197c-40c3-9023-4660f1707bbd ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/21/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 45CN38WW
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Emerald Lake
  dmi.board.vendor: LENOVO
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnLENOVO:bvr45CN38WW:bd10/21/2011:svnLENOVO:pnHuronRiverPlatform:pvrIdeapadZ570:rvnLENOVO:rnEmeraldLake:rvrFAB1:cvnLENOVO:ct10:cvr0.1:
  dmi.product.name: HuronRiver Platform
  dmi.product.version: Ideapad Z570
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Feb 28 01:46:45 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1562 
   vendor IVO
  xserver.version: 2:1.18.4-0ubuntu0.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1668389/+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 1734424] Re: Mouse cursor jumps to top of screen when moved

[Paul White ]

Thanks for your feedback in comment #2. Sorry it took over four years
for someone to acknowledge. I'm closing this as "Invalid" as it doesn't
seem that a software update was needed in order to resolve the issue.

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

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

Title:
  Mouse cursor jumps to top of screen when moved

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Creating this bug report has been a challenge. Every time I move the
  cursor, it jumps back to the top of the screen, slightly to the right.
  So I repeat and repeat and repeat until I get a hit on what I need to
  do.

  I have tried to purge nvidia, use nouveau, different versions of
  nvidia, purged xorg, tried ubuntu instead of lubuntu, nothing improves
  the mouse issue.

  It all started after an update a few days ago. The mouse has been
  working perfectly until then. I have tried different mouse types,
  replaced batteries. Nothing works. So now I am stuck with a computer
  that does not work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-40-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Er en mappe: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.98  Thu Oct 26 15:16:01 
PDT 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Nov 25 08:37:36 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-384, 384.98, 4.10.0-40-generic, x86_64: installed
   virtualbox, 5.0.40, 4.10.0-38-generic, x86_64: installed
   virtualbox, 5.0.40, 4.10.0-40-generic, x86_64: installed
   virtualbox, 5.0.40, 4.4.0-101-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GconfCompiz:
   /apps/compiz-1/general:
 /apps/compiz-1/general/screen0:
  /apps/compiz-1/general/screen0/options:
   active_plugins = 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  GraphicsCard:
   NVIDIA Corporation Device [10de:1c02] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:85b1]
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-40-generic 
root=UUID=eb61181b-453b-4475-a698-f3bbb8282eff ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2101
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M5A78L-M/USB3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2101:bd12/02/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-M/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  v

[Touch-packages] [Bug 1737479] Re: Xorg appears to crash on login

[Paul White ]

We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.

Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.

Do you still see a problem related to the one that you reported when
using a currently supported version of Ubuntu? Please let us know if you
do otherwise this report can be left to expire in approximately 60 days
time.

Thank you for helping make Ubuntu better.


** Changed in: xorg (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/1737479

Title:
  Xorg appears to crash on login

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Upon logging in, a crash report appears detailing that xorg has
  crashed and also that the problem report is damaged and cannot be
  processed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  BootLog:
   Scanning for Btrfs filesystems
   UBUNTU: clean, 38/28950528 files, 3863331/115784448 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun Dec 10 22:21:06 2017
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: xenial
  DistroVariant: ubuntu
  DpkgLog:
   
  GraphicsCard:
   Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:075b]
  InstallationDate: Installed on 2016-12-01 (374 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:568b Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 04f3:20d0 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 0cf3:e301 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9360
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic.efi.signed 
root=UUID=d9ec0f69-d5f3-4e71-ac1c-6e3c5ec32195 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/13/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.7
  dmi.board.name: 0839Y6
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.7:bd09/13/2016:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn0839Y6:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1737479/+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 1750410] Re: display lock up if addition display not present

[Paul White ]

We are sorry that we do not always have the capacity to review all
reported bugs in a timely manner. You reported this bug some time ago
and there have been many changes in Ubuntu since that time.

Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021.

Do you still see a problem related to the one that you reported when
using a currently supported version of Ubuntu? Please let us know if you
do otherwise this report can be left to expire in approximately 60 days
time.

Thank you for helping make Ubuntu better.


** Changed in: xorg (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/1750410

Title:
  display lock up if addition display not present

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  display lock up if addition display not present

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Feb 19 12:07:50 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Apple Inc. 3rd Gen Core processor Graphics Controller 
[106b:00fb]
   NVIDIA Corporation GK107M [GeForce GT 650M Mac Edition] [10de:0fd5] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Apple Inc. GK107M [GeForce GT 650M Mac Edition] [106b:00fc]
  InstallationDate: Installed on 2018-02-16 (3 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Apple Inc. MacBookPro9,1
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic.efi.signed 
root=UUID=4e57a30a-5941-45af-b5d4-53ee5dd4a074 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/08/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP91.88Z.00D3.B0B.1506081214
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-4B7AC7E43945597E
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro9,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-4B7AC7E43945597E
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP91.88Z.00D3.B0B.1506081214:bd06/08/2015:svnAppleInc.:pnMacBookPro9,1:pvr1.0:rvnAppleInc.:rnMac-4B7AC7E43945597E:rvrMacBookPro9,1:cvnAppleInc.:ct10:cvrMac-4B7AC7E43945597E:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro9,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.
  version.compiz: compiz 1:0.9.12.3+16.04.20171116-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Mon Feb 19 12:01:37 2018
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: nouveau

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1750410/+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 1958594] Re: Boot error: libgcc_s.so.1 must be installed for pthread_exit to work

[Athos Ribeiro]

In case you are running Jammy and gets affected by this issue:

The workaround described consists of booting from a live usb, decrypting
the disk, getting a chroot, and only then installing thin-provisioning-
tools and running update-initramfs.

This is the script I was using to decrypt the disk and get the chroot
(you will need to adjust it for your disk) [1].

In special, the name used with luksOpen should match the one described
in /etc/crypttab


[1]:

#!/bin/bash
set -eux
sudo cryptsetup luksOpen /dev/nvme0n1p3 crypt_dev_nvme0n1p3
sudo vgscan --mknodes
sudo vgchange -ay
sudo mkdir /media/disk
sudo mount /dev/mapper/system-root /media/disk/
sudo mount /dev/nvme0n1p1 /media/disk/boot/
sudo cp -L /etc/resolv.conf /media/disk/etc/resolv.conf 
cd /
sudo mount -t proc proc /media/disk/proc
sudo mount -t sysfs sys /media/disk/sys
sudo mount -o bind /dev /media/disk/dev
sudo chroot /media/disk /bin/bash

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

Title:
  Boot error: libgcc_s.so.1 must be installed for pthread_exit to work

Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in initramfs-tools source package in Jammy:
  Confirmed

Bug description:
  [Bug description]

  On a jammy installation, which was upgraded from focal, after a full-
  upgrade and a reboot,

  I enter the LUKS password to decrypt the disk. Then I get the
  following error:

  libgcc_s.so.1 must be installed for pthread_exit to work

  After the error is shown, the system asks for the password again
  (which never works, always throwing the same error).

  [Root cause]

  I was able to decrypt the disk with the same password by booting from
  a live usb. Which allowed further investigation.

  The error shown in the LUKS password prompt menu comes from
  https://github.com/bminor/glibc/blob/glibc-2.34/nptl/pthread_exit.c#L31-L32, 
which indeed shows that pthread_exit fails when libgcc_s.so.1 is missing.

  From
  
https://git.launchpad.net/ubuntu/+source/initramfs-tools/tree/hook-functions?h=import/0.140ubuntu10#n260,
  we noticed that libgcc_s.so.1 is only copied if

  1) copy_exec is called for a binary directly linked to libgcc_s.so.1, or
  2) copy_exec is called for a binary linked to libpthread

  The cryptsetup initramfs hook, calls copy_exec for /sbin/cryptsetup,
  which is linked to libargon2.so.1, which is linked to libpthread.so.0.
  This covers case (2) above. As a consequence, libgcc_s.so.1 is copied
  to the initrd image and the error reported here is not seen.

  However, since glibc 2.34, libpthread is shipped within glibc, and the
  binaries are no longer linked to libpthread.so.0. As a consequence, an
  argon2 package built with glibc 2.32 will no longer be linked to
  libpthread.so.0 and libgcc_s.so.1 will no longer be copied to the
  initrd image. Triggering the reported error.

  This can be verified in these two argon2 builds, from the same
  sources, but with different glibc versions:

  
https://launchpad.net/ubuntu/+source/argon2/0~20171227-0.2build21.04.0/+build/21066610
  
https://launchpad.net/ubuntu/+source/argon2/0~20171227-0.2build22/+build/22255217

  Still lvm2 is a seeded package, which Recommends thin-provisioning-
  tools. thin-provisioning-tools ships a initramfs hook that calls
  copy_exec for /usr/sbin/pdata_tools, which is directly linked to
  libgcc_s.so.1. This covers the case (1) above and should suffice to
  ensure the boot process works properly.

  Since thin-provisioning-tools is just a recommends for lvm2, it could
  be removed from the system (and indeed, for some reason, was not
  present in my focal=>jammy installation). In this case, a new kernel
  installation should trigger the reported error.

  [Reproducer]

  - Install jammy with a LUKS encrypted disk
  - remove thin-provisioning-tools
  - perform a full-upgrade (make sure the kernel was upgraded or run 
update-initramfs manually)
  - reboot and verify you can no longer get past the decrypt password prompt 
screen

  [Workaround]

  A workaround for anyone affected would be to install thin-
  provisioning-tools and run update-initramfs.

  [Impact]

  Users upgrading from focal to jammy will eventually be locked out of
  their systems in case they are using LUKS encryption.

  [Additional information]

  While this issue is similar to
  https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1861757,
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950254, and
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950551,
  This is a different bug, with a different root cause.

  Thanks to sergiodj for the pairing session on the root cause analysis.

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


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

[Touch-packages] [Bug 1958887] Re: Please merge logrotate 3.19.0-1 (main) from Debian unstable (main)

[Lukas Märdian]

Thank you, LGTM!

$ dput ubuntu ../logrotate_3.19.0-1ubuntu1_source.changes
D: Setting host argument.
Checking signature on .changes
gpg: ../logrotate_3.19.0-1ubuntu1_source.changes: Valid signature from 
5889C17AB1C8D890
Checking signature on .dsc
gpg: ../logrotate_3.19.0-1ubuntu1.dsc: Valid signature from 5889C17AB1C8D890
Uploading to ubuntu (via sftp to upload.ubuntu.com):
  Uploading logrotate_3.19.0-1ubuntu1.dsc: done.
  Uploading logrotate_3.19.0.orig.tar.xz: done.
  Uploading logrotate_3.19.0.orig.tar.xz.asc: done.
  Uploading logrotate_3.19.0-1ubuntu1.debian.tar.xz: done.  
  Uploading logrotate_3.19.0-1ubuntu1_source.buildinfo: done.
  Uploading logrotate_3.19.0-1ubuntu1_source.changes: done.
Successfully uploaded packages.

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

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

Title:
  Please merge logrotate 3.19.0-1 (main) from Debian unstable (main)

Status in logrotate package in Ubuntu:
  In Progress

Bug description:
  Please merge logrotate 3.19.0-1 (main) from Debian unstable (main)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1958887/+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 1959375] Re: [SRU] Please support group manipulation with "extrausers"

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  [SRU] Please support group manipulation with "extrausers"

Status in shadow package in Ubuntu:
  New
Status in shadow source package in Bionic:
  New
Status in shadow source package in Focal:
  New
Status in shadow source package in Impish:
  New
Status in shadow source package in Jammy:
  New

Bug description:
  Currently doing something like:

  sudo usermod -a -G snap_microk8s dbeamonte

  on a Ubuntu Core system will fail with

  usermod: /etc/group.15965: Read-only file system

  This is because the existing usermod patches to detect
  the extrausers file do not cover this case. Attached
  a simple patch that enables it. I will give this patch
  a test run in our image PPA for jammy and if things look
  good I would like upload to 22.04 and SRU for 20.04 and
  18.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1959375/+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 1959325] Re: New binutils causes build failures for many RISC-V packages

[Matthias Klose]

adding exact references from IRC logs ... please provide these in the
first place.

https://launchpadlibrarian.net/582482377/buildlog_ubuntu-jammy-
riscv64.ktexteditor_5.90.0-0ubuntu2_BUILDING.txt.gz"

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

Title:
  New binutils causes build failures for many RISC-V packages

Status in binutils package in Ubuntu:
  Confirmed
Status in binutils source package in Jammy:
  Confirmed

Bug description:
  binutils 2.37.90.20220126-0ubuntu1 changes the -march flags.
  We see a lot of packages not building in proposed anymore: OpenSBI, 
ktexteditor, ...

  Best regards

  Heinrich

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1959325/+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 1959371] Re: Unable to access DVD player on Desktop

[Ubuntu Foundations Team Bug Bot]

** Package changed: ubuntu => util-linux (Ubuntu)

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

Title:
  Unable to access DVD player on Desktop

Status in util-linux package in Ubuntu:
  New

Bug description:
  I installed Ubuntu 20.04 LTS on two ThinkStation S30 machines today,
  and seeing the same problem on both. So, it's not a machine specific
  hardware issue. After booting up, I can't read any DVDs. I tried
  multiple DVDs on both machines, and on a third machine where I am able
  to read them. So, it's not a media issue either. Here are some
  additional details

  $ cat /etc/group | grep cdrom
  cdrom:x:24:vipin

  So, I am a member of the cdrom group

  $ pwd
  /dev
  $ ls -l cdrom dvd dvdrw sr0
  lrwxrwxrwx  1 root root  3 Jan 27 23:46 cdrom -> sr0
  lrwxrwxrwx  1 root root  3 Jan 27 23:46 dvd -> sr0
  lrwxrwxrwx  1 root root  3 Jan 27 23:46 dvdrw -> sr0
  brw-rw+ 1 root cdrom 11, 0 Jan 27 23:46 sr0

  $ lsblk
  NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
  loop07:0055M  1 loop /snap/core18/1705
  loop17:10 240.8M  1 loop /snap/gnome-3-34-1804/24
  loop27:20  49.8M  1 loop /snap/snap-store/433
  loop37:30  27.1M  1 loop /snap/snapd/7264
  loop47:40  62.1M  1 loop /snap/gtk-common-themes/1506
  sda  8:00 238.5G  0 disk 
  ├─sda1   8:10   512M  0 part 
  ├─sda2   8:20   514M  0 part /boot/efi
  ├─sda3   8:30 1K  0 part 
  └─sda5   8:50 237.5G  0 part /
  sr0 11:01  1024M  0 rom

  $ sudo mount -t iso9660 /dev/sr0 /mnt/dvdrw
  mount: /mnt/dvdrw: no medium found on /dev/sr0.

  As can be seen sr0 is recognized as a block device, but is not
  mounted. When I try to mount it (also tried without -t), I get an
  error that no medium was found.

  Saw some posts about potentially changing the SATA ports on the
  motherboard. That's not a domain I wish to enter if I can avoid.
  Appreciate any help.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mount 2.34-0.1ubuntu9.1
  ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 27 23:55:09 2022
  InstallationDate: Installed on 2022-01-28 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1959371/+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 1959371] [NEW] Unable to access DVD player on Desktop

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

I installed Ubuntu 20.04 LTS on two ThinkStation S30 machines today, and
seeing the same problem on both. So, it's not a machine specific
hardware issue. After booting up, I can't read any DVDs. I tried
multiple DVDs on both machines, and on a third machine where I am able
to read them. So, it's not a media issue either. Here are some
additional details

$ cat /etc/group | grep cdrom
cdrom:x:24:vipin

So, I am a member of the cdrom group

$ pwd
/dev
$ ls -l cdrom dvd dvdrw sr0
lrwxrwxrwx  1 root root  3 Jan 27 23:46 cdrom -> sr0
lrwxrwxrwx  1 root root  3 Jan 27 23:46 dvd -> sr0
lrwxrwxrwx  1 root root  3 Jan 27 23:46 dvdrw -> sr0
brw-rw+ 1 root cdrom 11, 0 Jan 27 23:46 sr0

$ lsblk
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
loop07:0055M  1 loop /snap/core18/1705
loop17:10 240.8M  1 loop /snap/gnome-3-34-1804/24
loop27:20  49.8M  1 loop /snap/snap-store/433
loop37:30  27.1M  1 loop /snap/snapd/7264
loop47:40  62.1M  1 loop /snap/gtk-common-themes/1506
sda  8:00 238.5G  0 disk 
├─sda1   8:10   512M  0 part 
├─sda2   8:20   514M  0 part /boot/efi
├─sda3   8:30 1K  0 part 
└─sda5   8:50 237.5G  0 part /
sr0 11:01  1024M  0 rom

$ sudo mount -t iso9660 /dev/sr0 /mnt/dvdrw
mount: /mnt/dvdrw: no medium found on /dev/sr0.

As can be seen sr0 is recognized as a block device, but is not mounted.
When I try to mount it (also tried without -t), I get an error that no
medium was found.

Saw some posts about potentially changing the SATA ports on the
motherboard. That's not a domain I wish to enter if I can avoid.
Appreciate any help.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: mount 2.34-0.1ubuntu9.1
ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-27-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 27 23:55:09 2022
InstallationDate: Installed on 2022-01-28 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: util-linux
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal
-- 
Unable to access DVD player on Desktop
https://bugs.launchpad.net/bugs/1959371
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to util-linux 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 1959325] Re: New binutils causes build failures for many RISC-V packages

[Rik Mills]

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

** Also affects: binutils (Ubuntu Jammy)
   Importance: Critical
   Status: Confirmed

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

Title:
  New binutils causes build failures for many RISC-V packages

Status in binutils package in Ubuntu:
  Confirmed
Status in binutils source package in Jammy:
  Confirmed

Bug description:
  binutils 2.37.90.20220126-0ubuntu1 changes the -march flags.
  We see a lot of packages not building in proposed anymore: OpenSBI, 
ktexteditor, ...

  Best regards

  Heinrich

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1959325/+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 1958389] Re: Jammy builds of xen segfault, but only on launchpad x86 builders

[Bug Watch Updater]

** Changed in: binutils
   Status: Confirmed => In Progress

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

Title:
  Jammy builds of xen segfault, but only on launchpad x86 builders

Status in binutils:
  In Progress
Status in launchpad-buildd:
  New
Status in binutils package in Ubuntu:
  New
Status in xen package in Ubuntu:
  Invalid
Status in binutils source package in Jammy:
  New
Status in xen source package in Jammy:
  Invalid
Status in binutils package in Debian:
  New

Bug description:
  FTBFS in Jammy on LP infra:
  
https://launchpadlibrarian.net/580924961/buildlog_ubuntu-jammy-amd64.xen_4.16.0-1~ubuntu1~jammyppa4_BUILDING.txt.gz
  
https://launchpadlibrarian.net/581060687/buildlog_ubuntu-jammy-amd64.xen_4.16.0-1~ubuntu1~jammyppa6_BUILDING.txt.gz
  Related PPA:
  https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4760/+packages

  Summary:
  - Build reliably fails on LP
  - Build in local sbuild works reliably on my Laptop
  - Build in local VM (sizing like LP builders) works (other crashes but works)
  - Build on AMD server (chip more similar to LP) works reliably

  Failing step:

  On Launchpad build infrastructure it breaks on ld:
  $ x86_64-linux-gnu-ld -mi386pep --subsystem=10 
--image-base=0x82d04000 --stack=0,0 --heap=0,0 
--section-alignment=0x20 --file-alignment=0x20 --major-image-version=4 
--minor-image-version=16 --major-os-version=2 --minor-os-version=0 
--major-subsystem-version=2 --minor-subsystem-version=0 --no-insert-timestamp 
--build-id=sha1 -T efi.lds -N prelink.o  
/<>/xen/common/symbols-dummy.o -b pe-x86-64 efi/buildid.o -o 
/<>/xen/.xen.efi.0x82d04000.0 && :
  Segmentation fault (core dumped

  ---

  Steps to recreate (result depends on platform)

  # you can grab the package from https://launchpad.net/~ci-train-ppa-
  service/+archive/ubuntu/4760/+packages

  sudo vim /etc/apt/sources.list
  sudo apt update
  sudo apt dist-upgrade -y
  sudo apt build-dep xen
  sudo apt install flex bison python3-dev libpython3-dev dpkg-dev devscripts 
apport-retrace
  sudo mkdir /mnt/build
  sudo chmod go+w /mnt/build
  cd  /mnt/build
  # copy in things from host
  scp xen_4.16.0-1~ubuntu1~jammyppa6.dsc 
xen_4.16.0-1~ubuntu1~jammyppa6.debian.tar.xz xen_4.16.0.orig.tar.bz2 
ubuntu@:/mnt/build
  dpkg-source -x xen_4.16.0-1~ubuntu1~jammyppa6.dsc xen_4.16.0
  cd xen_4.16.0
  dpkg-buildpackage -i -us -uc -b

  ---

  In a jammy VM 4cpu/8G I get some avx2 crashes but the build works:

  Jan 19 07:41:27 j kernel: x86_64-linux-gn[130016]: segfault at 0 ip 
7f189432ef3d sp 7ffc8e2361d8 error 4 in libc.so.6[7f18941bb000+194000]
  Jan 19 07:41:27 j kernel: Code: f8 77 c3 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 
1e fa 89 f8 48 89 fa c5 f9 ef c0 25 ff 0f 00 00 3d e0 0f 00 00 0f 87 33 01 00 
00  fd 74 0f c5 fd d7 c1 85 c0 74 57 f3 0f bc c0 c5 f8 77 c3 66 66

  #0  __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74
  74../sysdeps/x86_64/multiarch/strlen-avx2.S: No such file or directory.
  (gdb) bt
  #0  __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74
  #1  0x7fa98d63c2d0 in ?? () from 
/lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so
  #2  0x7fa98d6021e8 in ?? () from 
/lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so
  #3  0x7fa98d602509 in coff_write_alien_symbol () from 
/lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so
  #4  0x7fa98d6033bd in _bfd_coff_final_link () from 
/lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so
  #5  0x562bdaaae3bf in ?? ()
  #6  0x7fa98d2e8fd0 in __libc_start_call_main 
(main=main@entry=0x562bdaaad5e0, argc=argc@entry=8, 
argv=argv@entry=0x7ffc797f2968) at ../sysdeps/nptl/libc_start_call_main.h:58
  #7  0x7fa98d2e907d in __libc_start_main_impl (main=0x562bdaaad5e0, 
argc=8, argv=0x7ffc797f2968, init=, fini=, 
rtld_fini=, 
  stack_end=0x7ffc797f2958) at ../csu/libc-start.c:409
  #8  0x562bdaaad515 in ?? ()

  ^^ that is a different crash than on th LP builders
  ! And despite those crashes the build does appear to work oO?!

  The same crashes I see on my local sbuild runs, the full set of one build is
  Jan 19 07:39:02 Keschdeichel kernel: x86_64-linux-gn[4131180]: segfault at 0 
ip 7f566e8b3f3d sp 7ffde04b75a8 error 4 in 
libc.so.6[7f566e74+194000]
  Jan 19 07:39:03 Keschdeichel kernel: x86_64-linux-gn[4131332]: segfault at 0 
ip 7fbba26e4f3d sp 7fffab8a5b68 error 4 in 
libc.so.6[7fbba2571000+194000]
  Jan 19 07:39:03 Keschdeichel kernel: x86_64-linux-gn[4131382]: segfault at 0 
ip 7fe3681b7f3d sp 7ffcbbf16628 error 4 in 
libc.so.6[7fe368044000+194000]
  Jan 19 07:39:42 Keschdeichel kernel: x86_64-linux-gn[4134584]: segfault at 0 
ip 7f241f455f3d sp 7ffd05c2e7c8 error 4 in 
libc.so.6[7f241f2e2000+194000]
  Jan 19 07:44:57 Keschdeichel kernel: x86_64-linux-gn[4171794]: seg

[Touch-packages] [Bug 1958389]

[Alan Modra]

Created attachment 13937
Likely fix

>From the backtrace in https://bugs.debian.org/1004269 it is clear that
the problem is triggered by commit e86fc4a5bc37 in which a new extrap
field was added to coffcode.h combined_entry_type but is not used on
anything except rs6000 coff targets.

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

Title:
  Jammy builds of xen segfault, but only on launchpad x86 builders

Status in binutils:
  In Progress
Status in launchpad-buildd:
  New
Status in binutils package in Ubuntu:
  New
Status in xen package in Ubuntu:
  Invalid
Status in binutils source package in Jammy:
  New
Status in xen source package in Jammy:
  Invalid
Status in binutils package in Debian:
  New

Bug description:
  FTBFS in Jammy on LP infra:
  
https://launchpadlibrarian.net/580924961/buildlog_ubuntu-jammy-amd64.xen_4.16.0-1~ubuntu1~jammyppa4_BUILDING.txt.gz
  
https://launchpadlibrarian.net/581060687/buildlog_ubuntu-jammy-amd64.xen_4.16.0-1~ubuntu1~jammyppa6_BUILDING.txt.gz
  Related PPA:
  https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4760/+packages

  Summary:
  - Build reliably fails on LP
  - Build in local sbuild works reliably on my Laptop
  - Build in local VM (sizing like LP builders) works (other crashes but works)
  - Build on AMD server (chip more similar to LP) works reliably

  Failing step:

  On Launchpad build infrastructure it breaks on ld:
  $ x86_64-linux-gnu-ld -mi386pep --subsystem=10 
--image-base=0x82d04000 --stack=0,0 --heap=0,0 
--section-alignment=0x20 --file-alignment=0x20 --major-image-version=4 
--minor-image-version=16 --major-os-version=2 --minor-os-version=0 
--major-subsystem-version=2 --minor-subsystem-version=0 --no-insert-timestamp 
--build-id=sha1 -T efi.lds -N prelink.o  
/<>/xen/common/symbols-dummy.o -b pe-x86-64 efi/buildid.o -o 
/<>/xen/.xen.efi.0x82d04000.0 && :
  Segmentation fault (core dumped

  ---

  Steps to recreate (result depends on platform)

  # you can grab the package from https://launchpad.net/~ci-train-ppa-
  service/+archive/ubuntu/4760/+packages

  sudo vim /etc/apt/sources.list
  sudo apt update
  sudo apt dist-upgrade -y
  sudo apt build-dep xen
  sudo apt install flex bison python3-dev libpython3-dev dpkg-dev devscripts 
apport-retrace
  sudo mkdir /mnt/build
  sudo chmod go+w /mnt/build
  cd  /mnt/build
  # copy in things from host
  scp xen_4.16.0-1~ubuntu1~jammyppa6.dsc 
xen_4.16.0-1~ubuntu1~jammyppa6.debian.tar.xz xen_4.16.0.orig.tar.bz2 
ubuntu@:/mnt/build
  dpkg-source -x xen_4.16.0-1~ubuntu1~jammyppa6.dsc xen_4.16.0
  cd xen_4.16.0
  dpkg-buildpackage -i -us -uc -b

  ---

  In a jammy VM 4cpu/8G I get some avx2 crashes but the build works:

  Jan 19 07:41:27 j kernel: x86_64-linux-gn[130016]: segfault at 0 ip 
7f189432ef3d sp 7ffc8e2361d8 error 4 in libc.so.6[7f18941bb000+194000]
  Jan 19 07:41:27 j kernel: Code: f8 77 c3 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 
1e fa 89 f8 48 89 fa c5 f9 ef c0 25 ff 0f 00 00 3d e0 0f 00 00 0f 87 33 01 00 
00  fd 74 0f c5 fd d7 c1 85 c0 74 57 f3 0f bc c0 c5 f8 77 c3 66 66

  #0  __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74
  74../sysdeps/x86_64/multiarch/strlen-avx2.S: No such file or directory.
  (gdb) bt
  #0  __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74
  #1  0x7fa98d63c2d0 in ?? () from 
/lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so
  #2  0x7fa98d6021e8 in ?? () from 
/lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so
  #3  0x7fa98d602509 in coff_write_alien_symbol () from 
/lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so
  #4  0x7fa98d6033bd in _bfd_coff_final_link () from 
/lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so
  #5  0x562bdaaae3bf in ?? ()
  #6  0x7fa98d2e8fd0 in __libc_start_call_main 
(main=main@entry=0x562bdaaad5e0, argc=argc@entry=8, 
argv=argv@entry=0x7ffc797f2968) at ../sysdeps/nptl/libc_start_call_main.h:58
  #7  0x7fa98d2e907d in __libc_start_main_impl (main=0x562bdaaad5e0, 
argc=8, argv=0x7ffc797f2968, init=, fini=, 
rtld_fini=, 
  stack_end=0x7ffc797f2958) at ../csu/libc-start.c:409
  #8  0x562bdaaad515 in ?? ()

  ^^ that is a different crash than on th LP builders
  ! And despite those crashes the build does appear to work oO?!

  The same crashes I see on my local sbuild runs, the full set of one build is
  Jan 19 07:39:02 Keschdeichel kernel: x86_64-linux-gn[4131180]: segfault at 0 
ip 7f566e8b3f3d sp 7ffde04b75a8 error 4 in 
libc.so.6[7f566e74+194000]
  Jan 19 07:39:03 Keschdeichel kernel: x86_64-linux-gn[4131332]: segfault at 0 
ip 7fbba26e4f3d sp 7fffab8a5b68 error 4 in 
libc.so.6[7fbba2571000+194000]
  Jan 19 07:39:03 Keschdeichel kernel: x86_64-linux-gn[4131382]: segfault at 0 
ip 7fe3681b7f3d sp 7ffcbbf16628 error 4 in 
libc.so.6[7fe368044000+194000]
  Jan 19 0

[Touch-packages] [Bug 1958389]

[Cvs-commit]

The master branch has been updated by Alan Modra
:

https://sourceware.org/git/gitweb.cgi?p=binutils-
gdb.git;h=07c9f243b3a12cc6749bc02ee7b165859979348b

commit 07c9f243b3a12cc6749bc02ee7b165859979348b
Author: Alan Modra 
Date:   Fri Jan 28 14:29:34 2022 +1030

PR28826 x86_64 ld segfaults building xen

Fallout from commit e86fc4a5bc37

PR 28826
* coffgen.c (coff_write_alien_symbol): Init dummy to zeros.

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

Title:
  Jammy builds of xen segfault, but only on launchpad x86 builders

Status in binutils:
  In Progress
Status in launchpad-buildd:
  New
Status in binutils package in Ubuntu:
  New
Status in xen package in Ubuntu:
  Invalid
Status in binutils source package in Jammy:
  New
Status in xen source package in Jammy:
  Invalid
Status in binutils package in Debian:
  New

Bug description:
  FTBFS in Jammy on LP infra:
  
https://launchpadlibrarian.net/580924961/buildlog_ubuntu-jammy-amd64.xen_4.16.0-1~ubuntu1~jammyppa4_BUILDING.txt.gz
  
https://launchpadlibrarian.net/581060687/buildlog_ubuntu-jammy-amd64.xen_4.16.0-1~ubuntu1~jammyppa6_BUILDING.txt.gz
  Related PPA:
  https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4760/+packages

  Summary:
  - Build reliably fails on LP
  - Build in local sbuild works reliably on my Laptop
  - Build in local VM (sizing like LP builders) works (other crashes but works)
  - Build on AMD server (chip more similar to LP) works reliably

  Failing step:

  On Launchpad build infrastructure it breaks on ld:
  $ x86_64-linux-gnu-ld -mi386pep --subsystem=10 
--image-base=0x82d04000 --stack=0,0 --heap=0,0 
--section-alignment=0x20 --file-alignment=0x20 --major-image-version=4 
--minor-image-version=16 --major-os-version=2 --minor-os-version=0 
--major-subsystem-version=2 --minor-subsystem-version=0 --no-insert-timestamp 
--build-id=sha1 -T efi.lds -N prelink.o  
/<>/xen/common/symbols-dummy.o -b pe-x86-64 efi/buildid.o -o 
/<>/xen/.xen.efi.0x82d04000.0 && :
  Segmentation fault (core dumped

  ---

  Steps to recreate (result depends on platform)

  # you can grab the package from https://launchpad.net/~ci-train-ppa-
  service/+archive/ubuntu/4760/+packages

  sudo vim /etc/apt/sources.list
  sudo apt update
  sudo apt dist-upgrade -y
  sudo apt build-dep xen
  sudo apt install flex bison python3-dev libpython3-dev dpkg-dev devscripts 
apport-retrace
  sudo mkdir /mnt/build
  sudo chmod go+w /mnt/build
  cd  /mnt/build
  # copy in things from host
  scp xen_4.16.0-1~ubuntu1~jammyppa6.dsc 
xen_4.16.0-1~ubuntu1~jammyppa6.debian.tar.xz xen_4.16.0.orig.tar.bz2 
ubuntu@:/mnt/build
  dpkg-source -x xen_4.16.0-1~ubuntu1~jammyppa6.dsc xen_4.16.0
  cd xen_4.16.0
  dpkg-buildpackage -i -us -uc -b

  ---

  In a jammy VM 4cpu/8G I get some avx2 crashes but the build works:

  Jan 19 07:41:27 j kernel: x86_64-linux-gn[130016]: segfault at 0 ip 
7f189432ef3d sp 7ffc8e2361d8 error 4 in libc.so.6[7f18941bb000+194000]
  Jan 19 07:41:27 j kernel: Code: f8 77 c3 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 
1e fa 89 f8 48 89 fa c5 f9 ef c0 25 ff 0f 00 00 3d e0 0f 00 00 0f 87 33 01 00 
00  fd 74 0f c5 fd d7 c1 85 c0 74 57 f3 0f bc c0 c5 f8 77 c3 66 66

  #0  __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74
  74../sysdeps/x86_64/multiarch/strlen-avx2.S: No such file or directory.
  (gdb) bt
  #0  __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74
  #1  0x7fa98d63c2d0 in ?? () from 
/lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so
  #2  0x7fa98d6021e8 in ?? () from 
/lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so
  #3  0x7fa98d602509 in coff_write_alien_symbol () from 
/lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so
  #4  0x7fa98d6033bd in _bfd_coff_final_link () from 
/lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so
  #5  0x562bdaaae3bf in ?? ()
  #6  0x7fa98d2e8fd0 in __libc_start_call_main 
(main=main@entry=0x562bdaaad5e0, argc=argc@entry=8, 
argv=argv@entry=0x7ffc797f2968) at ../sysdeps/nptl/libc_start_call_main.h:58
  #7  0x7fa98d2e907d in __libc_start_main_impl (main=0x562bdaaad5e0, 
argc=8, argv=0x7ffc797f2968, init=, fini=, 
rtld_fini=, 
  stack_end=0x7ffc797f2958) at ../csu/libc-start.c:409
  #8  0x562bdaaad515 in ?? ()

  ^^ that is a different crash than on th LP builders
  ! And despite those crashes the build does appear to work oO?!

  The same crashes I see on my local sbuild runs, the full set of one build is
  Jan 19 07:39:02 Keschdeichel kernel: x86_64-linux-gn[4131180]: segfault at 0 
ip 7f566e8b3f3d sp 7ffde04b75a8 error 4 in 
libc.so.6[7f566e74+194000]
  Jan 19 07:39:03 Keschdeichel kernel: x86_64-linux-gn[4131332]: segfault at 0 
ip 7fbba26e4f3d sp 7fffab8a5b68 error 4 in 
libc.so.6[7fbba2571000+194000]
  Jan 19 07

[Touch-packages] [Bug 1958389]

[Alan Modra]

HJ, you likely can reproduce the failue with an asan build of binutils,
or using MALLOC_PERTURB_.  I haven't tested the patch yet.

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

Title:
  Jammy builds of xen segfault, but only on launchpad x86 builders

Status in binutils:
  In Progress
Status in launchpad-buildd:
  New
Status in binutils package in Ubuntu:
  New
Status in xen package in Ubuntu:
  Invalid
Status in binutils source package in Jammy:
  New
Status in xen source package in Jammy:
  Invalid
Status in binutils package in Debian:
  New

Bug description:
  FTBFS in Jammy on LP infra:
  
https://launchpadlibrarian.net/580924961/buildlog_ubuntu-jammy-amd64.xen_4.16.0-1~ubuntu1~jammyppa4_BUILDING.txt.gz
  
https://launchpadlibrarian.net/581060687/buildlog_ubuntu-jammy-amd64.xen_4.16.0-1~ubuntu1~jammyppa6_BUILDING.txt.gz
  Related PPA:
  https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4760/+packages

  Summary:
  - Build reliably fails on LP
  - Build in local sbuild works reliably on my Laptop
  - Build in local VM (sizing like LP builders) works (other crashes but works)
  - Build on AMD server (chip more similar to LP) works reliably

  Failing step:

  On Launchpad build infrastructure it breaks on ld:
  $ x86_64-linux-gnu-ld -mi386pep --subsystem=10 
--image-base=0x82d04000 --stack=0,0 --heap=0,0 
--section-alignment=0x20 --file-alignment=0x20 --major-image-version=4 
--minor-image-version=16 --major-os-version=2 --minor-os-version=0 
--major-subsystem-version=2 --minor-subsystem-version=0 --no-insert-timestamp 
--build-id=sha1 -T efi.lds -N prelink.o  
/<>/xen/common/symbols-dummy.o -b pe-x86-64 efi/buildid.o -o 
/<>/xen/.xen.efi.0x82d04000.0 && :
  Segmentation fault (core dumped

  ---

  Steps to recreate (result depends on platform)

  # you can grab the package from https://launchpad.net/~ci-train-ppa-
  service/+archive/ubuntu/4760/+packages

  sudo vim /etc/apt/sources.list
  sudo apt update
  sudo apt dist-upgrade -y
  sudo apt build-dep xen
  sudo apt install flex bison python3-dev libpython3-dev dpkg-dev devscripts 
apport-retrace
  sudo mkdir /mnt/build
  sudo chmod go+w /mnt/build
  cd  /mnt/build
  # copy in things from host
  scp xen_4.16.0-1~ubuntu1~jammyppa6.dsc 
xen_4.16.0-1~ubuntu1~jammyppa6.debian.tar.xz xen_4.16.0.orig.tar.bz2 
ubuntu@:/mnt/build
  dpkg-source -x xen_4.16.0-1~ubuntu1~jammyppa6.dsc xen_4.16.0
  cd xen_4.16.0
  dpkg-buildpackage -i -us -uc -b

  ---

  In a jammy VM 4cpu/8G I get some avx2 crashes but the build works:

  Jan 19 07:41:27 j kernel: x86_64-linux-gn[130016]: segfault at 0 ip 
7f189432ef3d sp 7ffc8e2361d8 error 4 in libc.so.6[7f18941bb000+194000]
  Jan 19 07:41:27 j kernel: Code: f8 77 c3 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 
1e fa 89 f8 48 89 fa c5 f9 ef c0 25 ff 0f 00 00 3d e0 0f 00 00 0f 87 33 01 00 
00  fd 74 0f c5 fd d7 c1 85 c0 74 57 f3 0f bc c0 c5 f8 77 c3 66 66

  #0  __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74
  74../sysdeps/x86_64/multiarch/strlen-avx2.S: No such file or directory.
  (gdb) bt
  #0  __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74
  #1  0x7fa98d63c2d0 in ?? () from 
/lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so
  #2  0x7fa98d6021e8 in ?? () from 
/lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so
  #3  0x7fa98d602509 in coff_write_alien_symbol () from 
/lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so
  #4  0x7fa98d6033bd in _bfd_coff_final_link () from 
/lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so
  #5  0x562bdaaae3bf in ?? ()
  #6  0x7fa98d2e8fd0 in __libc_start_call_main 
(main=main@entry=0x562bdaaad5e0, argc=argc@entry=8, 
argv=argv@entry=0x7ffc797f2968) at ../sysdeps/nptl/libc_start_call_main.h:58
  #7  0x7fa98d2e907d in __libc_start_main_impl (main=0x562bdaaad5e0, 
argc=8, argv=0x7ffc797f2968, init=, fini=, 
rtld_fini=, 
  stack_end=0x7ffc797f2958) at ../csu/libc-start.c:409
  #8  0x562bdaaad515 in ?? ()

  ^^ that is a different crash than on th LP builders
  ! And despite those crashes the build does appear to work oO?!

  The same crashes I see on my local sbuild runs, the full set of one build is
  Jan 19 07:39:02 Keschdeichel kernel: x86_64-linux-gn[4131180]: segfault at 0 
ip 7f566e8b3f3d sp 7ffde04b75a8 error 4 in 
libc.so.6[7f566e74+194000]
  Jan 19 07:39:03 Keschdeichel kernel: x86_64-linux-gn[4131332]: segfault at 0 
ip 7fbba26e4f3d sp 7fffab8a5b68 error 4 in 
libc.so.6[7fbba2571000+194000]
  Jan 19 07:39:03 Keschdeichel kernel: x86_64-linux-gn[4131382]: segfault at 0 
ip 7fe3681b7f3d sp 7ffcbbf16628 error 4 in 
libc.so.6[7fe368044000+194000]
  Jan 19 07:39:42 Keschdeichel kernel: x86_64-linux-gn[4134584]: segfault at 0 
ip 7f241f455f3d sp 7ffd05c2e7c8 error 4 in 
libc.so.6[7f241f2e2000+194000]
 

[Touch-packages] [Bug 1958389]

[Hjl-tools]

Works for me:

/export/build/gnu/tools-build/binutils-asan/build-x86_64-linux/ld/ld-new
-mi386pep --subsystem=10 --image-base=0x82d04000 --stack=0,0
--heap=0,0 --section-alignment=0x20 --file-alignment=0x20 --major-
image-version=4 --minor-image-version=16 --major-os-version=2 --minor-
os-version=0 --major-subsystem-version=2 --minor-subsystem-version=0
--build-id=sha1 -T efi.lds -N prelink.o
/export/gnu/import/git/gitlab/xen/xen/.xen.efi.1r.o
/export/gnu/import/git/gitlab/xen/xen/.xen.efi.1s.o -b pe-x86-64
efi/buildid.o -o /export/gnu/import/git/gitlab/xen/xen/xen.efi

=
==1616314==ERROR: LeakSanitizer: detected memory leaks

Direct leak of 862212 byte(s) in 133 object(s) allocated from:
#0 0x7f3fbb6e791f in __interceptor_malloc (/lib64/libasan.so.6+0xae91f)
#1 0xb4844b in xmalloc 
/export/gnu/import/git/gitlab/x86-binutils/libiberty/xmalloc.c:149

SUMMARY: AddressSanitizer: 862212 byte(s) leaked in 133 allocation(s).
[hjl@gnu-tgl-2 x86]$

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

Title:
  Jammy builds of xen segfault, but only on launchpad x86 builders

Status in binutils:
  In Progress
Status in launchpad-buildd:
  New
Status in binutils package in Ubuntu:
  New
Status in xen package in Ubuntu:
  Invalid
Status in binutils source package in Jammy:
  New
Status in xen source package in Jammy:
  Invalid
Status in binutils package in Debian:
  New

Bug description:
  FTBFS in Jammy on LP infra:
  
https://launchpadlibrarian.net/580924961/buildlog_ubuntu-jammy-amd64.xen_4.16.0-1~ubuntu1~jammyppa4_BUILDING.txt.gz
  
https://launchpadlibrarian.net/581060687/buildlog_ubuntu-jammy-amd64.xen_4.16.0-1~ubuntu1~jammyppa6_BUILDING.txt.gz
  Related PPA:
  https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4760/+packages

  Summary:
  - Build reliably fails on LP
  - Build in local sbuild works reliably on my Laptop
  - Build in local VM (sizing like LP builders) works (other crashes but works)
  - Build on AMD server (chip more similar to LP) works reliably

  Failing step:

  On Launchpad build infrastructure it breaks on ld:
  $ x86_64-linux-gnu-ld -mi386pep --subsystem=10 
--image-base=0x82d04000 --stack=0,0 --heap=0,0 
--section-alignment=0x20 --file-alignment=0x20 --major-image-version=4 
--minor-image-version=16 --major-os-version=2 --minor-os-version=0 
--major-subsystem-version=2 --minor-subsystem-version=0 --no-insert-timestamp 
--build-id=sha1 -T efi.lds -N prelink.o  
/<>/xen/common/symbols-dummy.o -b pe-x86-64 efi/buildid.o -o 
/<>/xen/.xen.efi.0x82d04000.0 && :
  Segmentation fault (core dumped

  ---

  Steps to recreate (result depends on platform)

  # you can grab the package from https://launchpad.net/~ci-train-ppa-
  service/+archive/ubuntu/4760/+packages

  sudo vim /etc/apt/sources.list
  sudo apt update
  sudo apt dist-upgrade -y
  sudo apt build-dep xen
  sudo apt install flex bison python3-dev libpython3-dev dpkg-dev devscripts 
apport-retrace
  sudo mkdir /mnt/build
  sudo chmod go+w /mnt/build
  cd  /mnt/build
  # copy in things from host
  scp xen_4.16.0-1~ubuntu1~jammyppa6.dsc 
xen_4.16.0-1~ubuntu1~jammyppa6.debian.tar.xz xen_4.16.0.orig.tar.bz2 
ubuntu@:/mnt/build
  dpkg-source -x xen_4.16.0-1~ubuntu1~jammyppa6.dsc xen_4.16.0
  cd xen_4.16.0
  dpkg-buildpackage -i -us -uc -b

  ---

  In a jammy VM 4cpu/8G I get some avx2 crashes but the build works:

  Jan 19 07:41:27 j kernel: x86_64-linux-gn[130016]: segfault at 0 ip 
7f189432ef3d sp 7ffc8e2361d8 error 4 in libc.so.6[7f18941bb000+194000]
  Jan 19 07:41:27 j kernel: Code: f8 77 c3 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 
1e fa 89 f8 48 89 fa c5 f9 ef c0 25 ff 0f 00 00 3d e0 0f 00 00 0f 87 33 01 00 
00  fd 74 0f c5 fd d7 c1 85 c0 74 57 f3 0f bc c0 c5 f8 77 c3 66 66

  #0  __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74
  74../sysdeps/x86_64/multiarch/strlen-avx2.S: No such file or directory.
  (gdb) bt
  #0  __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74
  #1  0x7fa98d63c2d0 in ?? () from 
/lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so
  #2  0x7fa98d6021e8 in ?? () from 
/lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so
  #3  0x7fa98d602509 in coff_write_alien_symbol () from 
/lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so
  #4  0x7fa98d6033bd in _bfd_coff_final_link () from 
/lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so
  #5  0x562bdaaae3bf in ?? ()
  #6  0x7fa98d2e8fd0 in __libc_start_call_main 
(main=main@entry=0x562bdaaad5e0, argc=argc@entry=8, 
argv=argv@entry=0x7ffc797f2968) at ../sysdeps/nptl/libc_start_call_main.h:58
  #7  0x7fa98d2e907d in __libc_start_main_impl (main=0x562bdaaad5e0, 
argc=8, argv=0x7ffc797f2968, init=, fini=, 
rtld_fini=, 
  stack_end=0x7ffc797f2958) at ../c

[Touch-packages] [Bug 1958389]

[Hjl-tools]

I can build xen-4.16.0 on Fedora 35.  Please provide ALL inputs so that
I can reproduce it.

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

Title:
  Jammy builds of xen segfault, but only on launchpad x86 builders

Status in binutils:
  In Progress
Status in launchpad-buildd:
  New
Status in binutils package in Ubuntu:
  New
Status in xen package in Ubuntu:
  Invalid
Status in binutils source package in Jammy:
  New
Status in xen source package in Jammy:
  Invalid
Status in binutils package in Debian:
  New

Bug description:
  FTBFS in Jammy on LP infra:
  
https://launchpadlibrarian.net/580924961/buildlog_ubuntu-jammy-amd64.xen_4.16.0-1~ubuntu1~jammyppa4_BUILDING.txt.gz
  
https://launchpadlibrarian.net/581060687/buildlog_ubuntu-jammy-amd64.xen_4.16.0-1~ubuntu1~jammyppa6_BUILDING.txt.gz
  Related PPA:
  https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4760/+packages

  Summary:
  - Build reliably fails on LP
  - Build in local sbuild works reliably on my Laptop
  - Build in local VM (sizing like LP builders) works (other crashes but works)
  - Build on AMD server (chip more similar to LP) works reliably

  Failing step:

  On Launchpad build infrastructure it breaks on ld:
  $ x86_64-linux-gnu-ld -mi386pep --subsystem=10 
--image-base=0x82d04000 --stack=0,0 --heap=0,0 
--section-alignment=0x20 --file-alignment=0x20 --major-image-version=4 
--minor-image-version=16 --major-os-version=2 --minor-os-version=0 
--major-subsystem-version=2 --minor-subsystem-version=0 --no-insert-timestamp 
--build-id=sha1 -T efi.lds -N prelink.o  
/<>/xen/common/symbols-dummy.o -b pe-x86-64 efi/buildid.o -o 
/<>/xen/.xen.efi.0x82d04000.0 && :
  Segmentation fault (core dumped

  ---

  Steps to recreate (result depends on platform)

  # you can grab the package from https://launchpad.net/~ci-train-ppa-
  service/+archive/ubuntu/4760/+packages

  sudo vim /etc/apt/sources.list
  sudo apt update
  sudo apt dist-upgrade -y
  sudo apt build-dep xen
  sudo apt install flex bison python3-dev libpython3-dev dpkg-dev devscripts 
apport-retrace
  sudo mkdir /mnt/build
  sudo chmod go+w /mnt/build
  cd  /mnt/build
  # copy in things from host
  scp xen_4.16.0-1~ubuntu1~jammyppa6.dsc 
xen_4.16.0-1~ubuntu1~jammyppa6.debian.tar.xz xen_4.16.0.orig.tar.bz2 
ubuntu@:/mnt/build
  dpkg-source -x xen_4.16.0-1~ubuntu1~jammyppa6.dsc xen_4.16.0
  cd xen_4.16.0
  dpkg-buildpackage -i -us -uc -b

  ---

  In a jammy VM 4cpu/8G I get some avx2 crashes but the build works:

  Jan 19 07:41:27 j kernel: x86_64-linux-gn[130016]: segfault at 0 ip 
7f189432ef3d sp 7ffc8e2361d8 error 4 in libc.so.6[7f18941bb000+194000]
  Jan 19 07:41:27 j kernel: Code: f8 77 c3 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 
1e fa 89 f8 48 89 fa c5 f9 ef c0 25 ff 0f 00 00 3d e0 0f 00 00 0f 87 33 01 00 
00  fd 74 0f c5 fd d7 c1 85 c0 74 57 f3 0f bc c0 c5 f8 77 c3 66 66

  #0  __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74
  74../sysdeps/x86_64/multiarch/strlen-avx2.S: No such file or directory.
  (gdb) bt
  #0  __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:74
  #1  0x7fa98d63c2d0 in ?? () from 
/lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so
  #2  0x7fa98d6021e8 in ?? () from 
/lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so
  #3  0x7fa98d602509 in coff_write_alien_symbol () from 
/lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so
  #4  0x7fa98d6033bd in _bfd_coff_final_link () from 
/lib/x86_64-linux-gnu/libbfd-2.37.50-system.20220106.so
  #5  0x562bdaaae3bf in ?? ()
  #6  0x7fa98d2e8fd0 in __libc_start_call_main 
(main=main@entry=0x562bdaaad5e0, argc=argc@entry=8, 
argv=argv@entry=0x7ffc797f2968) at ../sysdeps/nptl/libc_start_call_main.h:58
  #7  0x7fa98d2e907d in __libc_start_main_impl (main=0x562bdaaad5e0, 
argc=8, argv=0x7ffc797f2968, init=, fini=, 
rtld_fini=, 
  stack_end=0x7ffc797f2958) at ../csu/libc-start.c:409
  #8  0x562bdaaad515 in ?? ()

  ^^ that is a different crash than on th LP builders
  ! And despite those crashes the build does appear to work oO?!

  The same crashes I see on my local sbuild runs, the full set of one build is
  Jan 19 07:39:02 Keschdeichel kernel: x86_64-linux-gn[4131180]: segfault at 0 
ip 7f566e8b3f3d sp 7ffde04b75a8 error 4 in 
libc.so.6[7f566e74+194000]
  Jan 19 07:39:03 Keschdeichel kernel: x86_64-linux-gn[4131332]: segfault at 0 
ip 7fbba26e4f3d sp 7fffab8a5b68 error 4 in 
libc.so.6[7fbba2571000+194000]
  Jan 19 07:39:03 Keschdeichel kernel: x86_64-linux-gn[4131382]: segfault at 0 
ip 7fe3681b7f3d sp 7ffcbbf16628 error 4 in 
libc.so.6[7fe368044000+194000]
  Jan 19 07:39:42 Keschdeichel kernel: x86_64-linux-gn[4134584]: segfault at 0 
ip 7f241f455f3d sp 7ffd05c2e7c8 error 4 in 
libc.so.6[7f241f2e2000+194000]
  Jan 19 07:44:57 Keschdeichel kernel: x

[Touch-packages] [Bug 1958720] Re: python3-yaml and python3-six are not co-installable with python-is-python2 in jammy

[Utkarsh Gupta]

Thank you, Rolf. On a quick look, what you reported appears to be
correct and hopefully the debdiff you added should just resolve the
issue at hand. I'm adding the `server-todo` tag so that someone from the
Server team can take a look at this and sponsor the debdiff for you if
that's all what's need to be done.

Thank you very much!

** Tags added: server-todo

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

** Changed in: pyyaml (Ubuntu)
   Importance: Undecided => High

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

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

Title:
  python3-yaml and python3-six are not co-installable with python-is-
  python2 in jammy

Status in pyyaml package in Ubuntu:
  Confirmed
Status in six package in Ubuntu:
  Invalid

Bug description:
  The packages python3-yaml and python-is-python2 are not co-installable
  in jammy and I believe they should be.  This currently prevents me
  from upgrading one of my machines from focal to jammy.

  Further analysis with the help of Stefano Rivera revealed that what-
  is-python no longer produces a python-is-python2 package and the
  changelog hints at that being intentional.  Jammy still has a python2
  package, though.

  python3-yaml in jammy breaks on python (<2.7.18).  The python-is-
  python2 package in focal is version 2.7.17-4 and in impish it is
  2.7.18-9 and thus will be forcefully removed when going to jammy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pyyaml/+bug/1958720/+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 1726856] Re: ufw does not start automatically at boot

[Stefan Staeglich]

@jdstran The fix of Debian doesn't help. I use fail2ban too. But if
fail2ban.service is disabled and masked then the issue still happens.

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

Title:
  ufw does not start automatically at boot

Status in ufw:
  Invalid
Status in ufw package in Ubuntu:
  Fix Released
Status in ufw source package in Xenial:
  Invalid
Status in ufw source package in Bionic:
  Invalid
Status in ufw source package in Cosmic:
  Invalid
Status in ufw source package in Disco:
  Invalid

Bug description:
  Whenever I boot into 17.10 ufw is always inactive, even though
  /etc/ufw/ufw.conf has this:

  # Set to yes to start on boot. If setting this remotely, be sure to add a rule
  # to allow your remote connection before starting ufw. Eg: 'ufw allow 22/tcp'
  ENABLED=yes

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: ufw 0.35-5
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 24 13:56:40 2017
  InstallationDate: Installed on 2015-04-01 (936 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: ufw
  UpgradeStatus: Upgraded to artful on 2017-10-24 (0 days ago)
  mtime.conffile..etc.default.ufw: 2015-06-17T22:01:02.089170

To manage notifications about this bug go to:
https://bugs.launchpad.net/ufw/+bug/1726856/+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 1959375] Re: [SRU] Please support group manipulation with "extrausers"

[Michael Vogt]

** Patch added: "debdiff for the PPA jammy test upload"
   
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1959375/+attachment/5557912/+files/shadow_4.8.1-2ubuntu2~ppa1.debdiff

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

Title:
  [SRU] Please support group manipulation with "extrausers"

Status in shadow package in Ubuntu:
  New
Status in shadow source package in Bionic:
  New
Status in shadow source package in Focal:
  New
Status in shadow source package in Impish:
  New
Status in shadow source package in Jammy:
  New

Bug description:
  Currently doing something like:

  sudo usermod -a -G snap_microk8s dbeamonte

  on a Ubuntu Core system will fail with

  usermod: /etc/group.15965: Read-only file system

  This is because the existing usermod patches to detect
  the extrausers file do not cover this case. Attached
  a simple patch that enables it. I will give this patch
  a test run in our image PPA for jammy and if things look
  good I would like upload to 22.04 and SRU for 20.04 and
  18.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1959375/+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 1955347] Re: rsync works bad with encfs now

[Utkarsh Gupta]

Hi Claude,

You could provide step-by-step reproducer by mentioning the exact steps
that one could follow to reproduce the bug in a clean environment.

If you could provide steps/commands that I can copy-paste in a Docker or
an LXD container, then that'd really help us and we can take it from
there. \o/

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

Title:
  rsync works bad with encfs now

Status in rsync package in Ubuntu:
  Incomplete

Bug description:
  Hello,
  I think rsync works bad with encfs now.

  When root uses it, rsync cannot read a directory encrypted with encfs
  by a user. More precisely, it cannot read the mounted directory, the
  virtual one where the user can read the datas.

  Until now there was only a warning like this
  "rsync: readlink_stat("/home/claude/Documents_chiffres") failed:
  Permission denied (13)"
  and the software went on working (only ignoring the content of the mounted 
directory and of course without saving this content)

  But recently there is this more:
  "IO error encountered -- skipping file deletion"
  and because of this "skipping file deletion", the software can't work 
normally. The destination gets bigger more and more because the deleted files 
in the source are not deleted in the destination.

  Thanks for reading me.
  rsync 3.1.3-8ubuntu0.1
  Description:Ubuntu 20.04.3 LTS
  Release:20.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1955347/+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 1959375] Re: [SRU] Please support group manipulation with "extrausers"

[Michael Vogt]

** Patch added: "Proposed (untested) patch"
   
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1959375/+attachment/5557911/+files/shadow-lp1959375.diff

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

Title:
  [SRU] Please support group manipulation with "extrausers"

Status in shadow package in Ubuntu:
  New
Status in shadow source package in Bionic:
  New
Status in shadow source package in Focal:
  New
Status in shadow source package in Impish:
  New
Status in shadow source package in Jammy:
  New

Bug description:
  Currently doing something like:

  sudo usermod -a -G snap_microk8s dbeamonte

  on a Ubuntu Core system will fail with

  usermod: /etc/group.15965: Read-only file system

  This is because the existing usermod patches to detect
  the extrausers file do not cover this case. Attached
  a simple patch that enables it. I will give this patch
  a test run in our image PPA for jammy and if things look
  good I would like upload to 22.04 and SRU for 20.04 and
  18.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1959375/+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 1959375] [NEW] [SRU] Please support group manipulation with "extrausers"

[Michael Vogt]

Public bug reported:

Currently doing something like:

sudo usermod -a -G snap_microk8s dbeamonte

on a Ubuntu Core system will fail with

usermod: /etc/group.15965: Read-only file system

This is because the existing usermod patches to detect
the extrausers file do not cover this case. Attached
a simple patch that enables it. I will give this patch
a test run in our image PPA for jammy and if things look
good I would like upload to 22.04 and SRU for 20.04 and
18.04.

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

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

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

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

** Affects: shadow (Ubuntu Jammy)
 Importance: Undecided
 Status: New

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

** Also affects: shadow (Ubuntu Impish)
   Importance: Undecided
   Status: New

** Also affects: shadow (Ubuntu Jammy)
   Importance: Undecided
   Status: New

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

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

Title:
  [SRU] Please support group manipulation with "extrausers"

Status in shadow package in Ubuntu:
  New
Status in shadow source package in Bionic:
  New
Status in shadow source package in Focal:
  New
Status in shadow source package in Impish:
  New
Status in shadow source package in Jammy:
  New

Bug description:
  Currently doing something like:

  sudo usermod -a -G snap_microk8s dbeamonte

  on a Ubuntu Core system will fail with

  usermod: /etc/group.15965: Read-only file system

  This is because the existing usermod patches to detect
  the extrausers file do not cover this case. Attached
  a simple patch that enables it. I will give this patch
  a test run in our image PPA for jammy and if things look
  good I would like upload to 22.04 and SRU for 20.04 and
  18.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1959375/+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 1854383] Re: Extra window decorations are created on windows with client-side decorations.

[Norbert]

Yes, it is. Install gnome-calendar as deb-package and try to resize its
window by dragging its window border.

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

Title:
  Extra window decorations are created on windows with client-side
  decorations.

Status in Ubuntu MATE:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in marco package in Ubuntu:
  New

Bug description:
  Steps to reproduce after a minimal/full install of Ubuntu MATE:

  1. Start up a Gtk3 application with a header bar (tested with Gnome
  Software) or a browser (such as Firefox) without using a standard
  window title bar that saves the position and size of the window before
  it was closed.

  2. Maximize the application window, then close it without changing the
  window size

  3. Relaunch the application and resize/unmaximize it

  After this, dummy window decorations will be created around the
  window. This issue has been tested on a Dell XPS 9570 and using Gnome
  Boxes 3.34.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1854383/+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 1953052] Re: In Jammy sound level reset after reboot

[corrado venturini]

not 'journalctl -b 1 > log' but 'journalctl -b-1 > log' 
.. log attached 

** Attachment added: "log"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1953052/+attachment/5557907/+files/log

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

Title:
  In Jammy sound level reset after reboot

Status in alsa-utils package in Ubuntu:
  Confirmed

Bug description:
  After reboot sound level is reset ignoring the level set in previous
  session.

  I manually set the sound output level 
  at next boot the sound is set at a different level (about 70%)

  Expected: the sound level is persistent across power off/on

  What happens : sound level is set at a different level (about 70%)

  Note: this problem does not occur on different partitions of same PC
  running Ubuntu 20.04 or 21.10

  corrado@corrado-p3-jj-1130:~$ apt policy gnome-control-center
  gnome-control-center:
Installed: 1:41.1-1ubuntu1
Candidate: 1:41.1-1ubuntu1
Version table:
   *** 1:41.1-1ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-p3-jj-1130:~$ inxi -Fx
  System:Host: corrado-p3-jj-1130 Kernel: 5.13.0-19-generic x86_64 bits: 64 
compiler: gcc v: 11.2.0
 Desktop: GNOME 40.5 Distro: Ubuntu 22.04 (Jammy Jellyfish)
  Machine:   Type: Laptop System: Dell product: Inspiron 3793 v: N/A serial: 

 Mobo: Dell model: 0C1PF2 v: A00 serial:  UEFI: 
Dell v: 1.5.0 date: 12/17/2019
  Battery:   ID-1: BAT0 charge: 13.9 Wh (42.1%) condition: 33.0/42.0 Wh (78.7%) 
volts: 11.3 min: 11.4
 model: SWD-ATL3.618 DELL WJPC403 status: Discharging
  CPU:   Info: Quad Core model: Intel Core i5-1035G1 bits: 64 type: MT MCP 
arch: Ice Lake rev: 5 cache:
 L2: 6 MiB
 flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 19046
 Speed: 968 MHz min/max: 400/1000 MHz Core speeds (MHz): 1: 968 2: 
710 3: 706 4: 714 5: 966 6: 712
 7: 724 8: 821
  Graphics:  Device-1: Intel Iris Plus Graphics G1 vendor: Dell driver: i915 v: 
kernel bus-ID: 00:02.0
 Device-2: Realtek Integrated_Webcam_HD type: USB driver: uvcvideo 
bus-ID: 1-6:3
 Display: wayland server: X.Org 1.21.1.2 compositor: gnome-shell 
driver: loaded: i915
 note: n/a (using device driver) resolution: 1920x1080~60Hz
 OpenGL: renderer: Mesa Intel UHD Graphics (ICL GT1) v: 4.6 Mesa 
21.2.2 direct render: Yes
  Audio: Device-1: Intel Ice Lake-LP Smart Sound Audio vendor: Dell driver: 
snd_hda_intel v: kernel
 bus-ID: 00:1f.3
 Sound Server-1: ALSA v: k5.13.0-19-generic running: yes
 Sound Server-2: PulseAudio v: 15.0 running: yes
 Sound Server-3: PipeWire v: 0.3.40 running: yes
  Network:   Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Dell 
driver: r8169 v: kernel port: 3000
 bus-ID: 01:00.0
 IF: enp1s0 state: down mac: 98:e7:43:59:19:19
 Device-2: Qualcomm Atheros QCA9377 802.11ac Wireless Network 
Adapter vendor: Dell driver: ath10k_pci
 v: kernel bus-ID: 02:00.0
 IF: wlp2s0 state: up mac: d8:12:65:b8:21:b9
  Bluetooth: Device-1: Qualcomm Atheros type: USB driver: btusb v: 0.8 bus-ID: 
1-10:4
 Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: 
enabled,running rfk-block: hardware: no
 software: yes address: D8:12:65:B8:21:BA
  Drives:Local Storage: total: 942.7 GiB used: 11.77 GiB (1.2%)
 ID-1: /dev/nvme0n1 vendor: Toshiba model: KBG40ZNS512G NVMe KIOXIA 
512GB size: 476.94 GiB temp: 24.9 C
 ID-2: /dev/sda vendor: Crucial model: CT500MX500SSD1 size: 465.76 
GiB
  Partition: ID-1: / size: 46.95 GiB used: 11.73 GiB (25.0%) fs: ext4 dev: 
/dev/nvme0n1p3
 ID-2: /boot/efi size: 246 MiB used: 46.4 MiB (18.9%) fs: vfat dev: 
/dev/nvme0n1p1
  Swap:  Alert: No swap data was found.
  Sensors:   System Temperatures: cpu: 27.8 C mobo: N/A
 Fan Speeds (RPM): cpu: 0
  Info:  Processes: 263 Uptime: 31m Memory: 15.4 GiB used: 2.45 GiB (15.9%) 
Init: systemd runlevel: 5 Compilers:
 gcc: N/A Packages: 1785 Shell: Bash v: 5.1.12 inxi: 3.3.07
  corrado@corrado-p3-jj-1130:~$
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu74
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2021-11-30 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  Package: gnome-control-center 1:41.1-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14
  Tags:  wayland-session jammy
  Uname: Linux 5.13.0-19-generic x86_64
  UpgradeStatus: No upgrade log pre