[Touch-packages] [Bug 1965518] Re: [USB-Audio - USB Audio, recording] Recording problem

2022-06-20 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: alsa-driver (Ubuntu)
   Status: New => Confirmed

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

Title:
  [USB-Audio - USB Audio, recording] Recording problem

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Microphone when using built in mbo MSI Z690 Edge WiFi DDR4 audio
  Realtek ALC4080 is not recording audio. What I did found out, that the
  bar which indicates that something is recording is going up, when I
  play some sound on ubuntu, so input "thinks" it is output I think.

  If raport is somehow saying I was not using that mic at the moment,
  that is because I was using other card which I need to buy, for mic to
  temporarly work. I rechecked it before sending report, and yes, that
  original from MBO audio input is still not working.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19
  Uname: Linux 5.13.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: Unity
  Date: Fri Mar 18 10:39:26 2022
  InstallationDate: Installed on 2022-03-12 (5 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:Audio failed
  Symptom_Card: USB Audio - USB Audio
  Symptom_Type: None of the above
  Title: [USB-Audio - USB Audio, recording] Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/13/2021
  dmi.bios.release: 5.24
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: 1.10
  dmi.board.asset.tag: Default string
  dmi.board.name: MPG Z690 EDGE WIFI DDR4 (MS-7D31)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvr1.10:bd12/13/2021:br5.24:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D31:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMPGZ690EDGEWIFIDDR4(MS-7D31):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: MS-7D31
  dmi.product.sku: Default string
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1965518/+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 1969477] Re: apport-collect needs to be able to save logs to a file instead of requiring a launchpad connection

2022-06-18 Thread Launchpad Bug Tracker
[Expired for apport (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  apport-collect needs to be able to save logs to a file instead of
  requiring a launchpad connection

Status in apport package in Ubuntu:
  Expired

Bug description:
  We very often tell our hardware partners to "file a bug" when they
  encounter issues.  This requires them to run apport-collect to gather
  and submit logs for the bug.

  However, very often, the hardware that has the problem is in a lab
  that has tight security restrictions and direct access to launchpad is
  blocked.  This makes it nearly impossible for them to gather any
  requested logs, since apport-collect requires a direct line to
  Launchpad.

  apport-collect needs to adopt the --save feature of apport-bug/ubuntu-
  bug to save the prescribed logs and system data in a tarball that can
  then be attached to a bug after the fact.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apport 2.20.11-0ubuntu27.23
  ProcVersionSignature: Ubuntu 5.4.0-100.113-generic 5.4.166
  Uname: Linux 5.4.0-100-generic x86_64
  NonfreeKernelModules: lkp_Ubuntu_5_4_0_100_113_generic_85 zfs zunicode zavl 
icp nvidia_modeset zcommon znvpair nvidia
  ApportLog:
   
  ApportVersion: 2.20.11-0ubuntu27.23
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 19 10:25:54 2022
  InstallationDate: Installed on 2016-02-11 (2258 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1969477/+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 1948882] Re: PulseEffects does not properly initialize on startup

2022-06-18 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  PulseEffects does not properly initialize on startup

Status in d-conf package in Ubuntu:
  Confirmed
Status in pulseeffects package in Ubuntu:
  Confirmed

Bug description:
  In KUbuntu 21.10, PulseEffects no longer initializes its effects chain
  on startup. I usually use only Equalizer, so when I log into KDE, this
  equalizer does not get activated. To ativate it I need (i) start
  PulseEffects GUI, (ii) untic and tic again the "Equalizer" box. This
  is rarher annoying sequence that I have to repeat each time I login.

  Previousy, in ubuntu 21.04, all this was unnecessary. PluseEffets just
  worked immediately after logging in, without any additional actions. I
  would expect the same behaviour in 21.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: pulseeffects 4.8.4-1
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Oct 27 02:56:47 2021
  InstallationDate: Installed on 2017-04-03 (1667 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   LANGUAGE=ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseeffects
  UpgradeStatus: Upgraded to impish on 2021-09-24 (32 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/d-conf/+bug/1948882/+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 1979096] [NEW] X.org or Gnome-shell

2022-06-17 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

The problem happens, when I enable the dock to hide automatically. With
this enabled, it is not possible to run the programs through the search.
But when disabled, it is possible to search and run the programs. Here's
the video of the problem.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
Uname: Linux 5.15.0-39-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Jun 17 18:21:45 2022
DistUpgraded: 2022-04-21 13:52:59,951 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: jammy
DistroVariant: ubuntu
DkmsStatus:
 v4l2loopback/0.12.5, 5.15.0-37-generic, x86_64: installed
 v4l2loopback/0.12.5, 5.15.0-39-generic, x86_64: installed
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] RS780L [Radeon 3000] [1002:9616] 
(prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. RS780L [Radeon 3000] [1043:8388]
InstallationDate: Installed on 2021-04-15 (428 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-39-generic 
root=UUID=7e3c483e-6d02-4fc2-be0e-48207eb147eb ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to jammy on 2022-04-21 (57 days ago)
dmi.bios.date: 03/04/2017
dmi.bios.release: 8.15
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1201
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M5A78L-M LX/BR
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.:bvr1201:bd03/04/2017:br8.15:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-MLX/BR:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:skuToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2.1
version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2.1
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug jammy ubuntu
-- 
X.org or Gnome-shell
https://bugs.launchpad.net/bugs/1979096
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg 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 1117222] Re: autopkgtest test cases for libestr

2022-06-17 Thread Launchpad Bug Tracker
This bug was fixed in the package libestr - 0.1.11-1

---
libestr (0.1.11-1) unstable; urgency=medium

  * New maintainer (Closes: #1010434)
- redo packaging from scratch, following current best practices
- reintroduce autopkgtest from #700293 which was silently dropped in
  0.1.10-1, but adjust it for cross-compilation (LP: #1117222)
  * New upstream release (Closes: #912419)

 -- Florian Ernst   Sun, 05 Jun 2022 08:15:55 +0200

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

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

Title:
  autopkgtest test cases for libestr

Status in libestr package in Ubuntu:
  Fix Released
Status in libestr package in Debian:
  Fix Released

Bug description:
  The DEP 8 specification defines how automatic testing can very easily be 
integrated into packages. 
  I have created test cases for libestr and attached them as a debdiff.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libestr/+bug/1117222/+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 1970634] Re: FTBFS: mariadb fails to start due to low MEMLOCK limit

2022-06-17 Thread Launchpad Bug Tracker
** Merge proposal linked:
   
https://code.launchpad.net/~ahasenack/ubuntu/+source/mariadb-10.6/+git/mariadb-10.6/+merge/424986

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

Title:
  FTBFS: mariadb fails to start due to low MEMLOCK limit

Status in mariadb-10.6 package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in mariadb-10.6 source package in Jammy:
  Triaged
Status in systemd source package in Jammy:
  In Progress

Bug description:
  [Impact]

  Jammy's MariaDB will fail to build, and also fail to start, if the
  underlying kernel is 5.4.x (focal's) and if it's running in an
  unprivileged container (lxd, docker). It will also fail to build in
  launchpad builders.

  Common scenarios where this combination exists is a focal host,
  running an unprivileged jammy container (lxd or docker), or even a
  chroot (the launchpad builders).

  Jammy's MariaDB was built with io_uring support, and it tries to
  enable it at runtime if it deems it's running on a supported kernel.
  There is a range of kernel versions it checks, but of interest for
  this SRU, the Focal (5.4.x) kernel is inside this range and io_uring
  will be enabled. The jammy kernel (5.15) is not, so io_uring will not
  be enabled there, and thus the bug is not manifested in that case.

  If io_uring is enabled, a higher MEMLOCK limit is required than what
  is set by default in focal or jammy (64Mb is what we get, 256Mb or
  more is required).

  The systemd unit file for mariadb tries to raise this limit, but in an
  unprivileged container this won't work.

  MariaDB has checks in place to catch when MEMLOCK is too low, in which
  case it will not use io_uring, but these checks are failing because of
  the LTO build flags that were used in the jammy build of mariadb. It's
  unclear if it's a bug in gcc or something else. There is more
  information in comment #1, comment #5 and later.

  The suggested fix here is to disable LTO for the jammy build. This has
  been done for kinetic already, and is also applied to the debian
  packaging (inside a distro-specific conditional).

  [Test Plan]
  The test plan is to launch mariadb in a jammy lxd container running on a 
focal host.

  lxc launch ubuntu:focal f --vm
  lxc shell
  lxd init # just hit enter for all questions
  lxc launch ubuntu:jammy j
  lxc shell j
  ulimit -l # confirm it's less than 256
  apt update && apt install mariadb-server -y

  After the installation, mariadb will not be running, and this can be
  checked with:

  systemctl status mariadb-server

  or

  journalctl -u mariadb.server

  You will see something like this:
  Jun 17 18:32:01 jammy-mariadb systemd[1]: Starting MariaDB 10.6.7 database 
server...
  Jun 17 18:32:01 jammy-mariadb mariadbd[1864]: 2022-06-17 18:32:01 0 [Note] 
/usr/sbin/mariadbd (server 10.6.7-MariaDB-2ubuntu1) starting as process 1864 ...
  Jun 17 18:32:01 jammy-mariadb mariadbd[1864]: 2022-06-17 18:32:01 0 [Note] 
InnoDB: The first data file './ibdata1' did not exist. A new tablespace will be 
created!
  Jun 17 18:32:01 jammy-mariadb mariadbd[1864]: 2022-06-17 18:32:01 0 [Note] 
InnoDB: Compressed tables use zlib 1.2.11
  Jun 17 18:32:01 jammy-mariadb mariadbd[1864]: 2022-06-17 18:32:01 0 [Note] 
InnoDB: Using transactional memory
  Jun 17 18:32:01 jammy-mariadb mariadbd[1864]: 2022-06-17 18:32:01 0 [Note] 
InnoDB: Number of pools: 1
  Jun 17 18:32:01 jammy-mariadb mariadbd[1864]: 2022-06-17 18:32:01 0 [Note] 
InnoDB: Using crc32 + pclmulqdq instructions
  Jun 17 18:32:01 jammy-mariadb mariadbd[1864]: 2022-06-17 18:32:01 0 [Warning] 
mariadbd: io_uring_queue_init() failed with ENOMEM: try larger memory locked 
limit, ulimit -l, or 
https://mariadb.com/kb/en/systemd/#configuring-limitmemlock under systemd 
(262144 bytes required)
  Jun 17 18:32:01 jammy-mariadb mariadbd[1864]: 220617 18:32:01 [ERROR] mysqld 
got signal 6 ;

  And a crash dump.

  With the fixed version, the service will be running normally after
  installation.

  [Where problems could occur]
  The proposed fix is not a surgical strike. It's unfortunate that we didn't 
get to the bottom of why LTO is causing this behavior. Reverting it is still 
the quickest and less risky change at the moment, though. This gets us on par 
with upstream binary builds, and debian builds, and these also have wide test 
coverage and ample user base.

  The other regression possibility is that this is a rebuild of mariadb
  in the current jammy environment, and the package that is currently in
  jammy was built on March 10th, 2022. Most likely the reverse
  dependencies were updated in jammy since then.

  It's unclear how 10.6.7-2ubuntu1 migrated in jammy. I checked build
  logs and dep8 logs, and can't tell why the tests passed. At least the
  build log in jammy shows the host kernel was 5.4.x, so it should have
  been affected. My 

[Touch-packages] [Bug 1969896] Re: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched

2022-06-17 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Evince Document Viewer(42.0) does not remember last page in 22.04 and
  opens in a tiny window when launched

Status in apparmor package in Ubuntu:
  In Progress
Status in evince package in Ubuntu:
  In Progress
Status in apparmor source package in Jammy:
  In Progress
Status in evince source package in Jammy:
  Confirmed
Status in apparmor source package in Kinetic:
  In Progress
Status in evince source package in Kinetic:
  In Progress

Bug description:
  Just switched from Ubuntu 20.04 to 22.04 and realized that Document
  Viewer no longer open on the last viewed page and doesn't remember the
  side pane preference even after using the "Save Current Settings as
  Default" option. Kindly advise

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: evince 42.1-3
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 22 15:58:50 2022
  InstallationDate: Installed on 2022-03-19 (34 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: Upgraded to jammy on 2022-04-21 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1969896/+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 1979066] [NEW] BUG: kernel NULL pointer dereference, address: 0000000000000300

2022-06-17 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Recently I experienced the issue that after dis- and reconnecting my monitor 
(Philips 346B1C) with USB-Hub, my laptop (Lenovo E480) did not accept any 
inputs (mouse or keyboard, neither), while the display looked OK.
I was able to access the laptop using SSH and found following backtrace in 
dmesg:


[18890.250253] pcieport :00:1d.2: AER: Corrected error received: 
:00:1d.2
[18890.250286] pcieport :00:1d.2: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, (Receiver ID)
[18890.250293] pcieport :00:1d.2:   device [8086:9d1a] error 
status/mask=0001/2000
[18890.250300] pcieport :00:1d.2:[ 0] RxErr
[18923.193928] pcieport :00:1d.2: AER: Corrected error received: 
:00:1d.2
[18923.193941] pcieport :00:1d.2: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, (Receiver ID)
[18923.193944] pcieport :00:1d.2:   device [8086:9d1a] error 
status/mask=0001/2000
[18923.193948] pcieport :00:1d.2:[ 0] RxErr
[18929.192524] pcieport :00:1d.2: AER: Corrected error received: 
:00:1d.2
[18929.192547] pcieport :00:1d.2: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, (Receiver ID)
[18929.192554] pcieport :00:1d.2:   device [8086:9d1a] error 
status/mask=0001/2000
[18929.192561] pcieport :00:1d.2:[ 0] RxErr
[18941.195429] pcieport :00:1d.2: AER: Corrected error received: 
:00:1d.2
[18941.195440] pcieport :00:1d.2: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, (Receiver ID)
[18941.195446] pcieport :00:1d.2:   device [8086:9d1a] error 
status/mask=0001/2000
[18941.195450] pcieport :00:1d.2:[ 0] RxErr
[18965.194123] pcieport :00:1d.2: AER: Corrected error received: 
:00:1d.2
[18965.194132] pcieport :00:1d.2: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, (Receiver ID)
[18965.194134] pcieport :00:1d.2:   device [8086:9d1a] error 
status/mask=0001/2000
[18965.194136] pcieport :00:1d.2:[ 0] RxErr
[18983.192431] pcieport :00:1d.2: AER: Multiple Corrected error received: 
:00:1d.2
[18983.192471] pcieport :00:1d.2: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, (Transmitter ID)
[18983.192478] pcieport :00:1d.2:   device [8086:9d1a] error 
status/mask=1001/2000
[18983.192487] pcieport :00:1d.2:[ 0] RxErr
[18983.192494] pcieport :00:1d.2:[12] Timeout
[18989.194543] pcieport :00:1d.2: AER: Corrected error received: 
:00:1d.2
[18989.194574] pcieport :00:1d.2: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, (Receiver ID)
[18989.194581] pcieport :00:1d.2:   device [8086:9d1a] error 
status/mask=0001/2000
[18989.194588] pcieport :00:1d.2:[ 0] RxErr
[19001.195887] pcieport :00:1d.2: AER: Corrected error received: 
:00:1d.2
[19001.195914] pcieport :00:1d.2: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, (Receiver ID)
[19001.195919] pcieport :00:1d.2:   device [8086:9d1a] error 
status/mask=0001/2000
[19001.195926] pcieport :00:1d.2:[ 0] RxErr
[19005.947848] pcieport :00:1d.2: AER: Corrected error received: 
:00:1d.2
[19005.947872] pcieport :00:1d.2: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, (Receiver ID)
[19005.947878] pcieport :00:1d.2:   device [8086:9d1a] error 
status/mask=0001/2000
[19005.947886] pcieport :00:1d.2:[ 0] RxErr
[19007.194477] pcieport :00:1d.2: AER: Corrected error received: 
:00:1d.2
[19007.194505] pcieport :00:1d.2: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, (Receiver ID)
[19007.194509] pcieport :00:1d.2:   device [8086:9d1a] error 
status/mask=0001/2000
[19007.194514] pcieport :00:1d.2:[ 0] RxErr
[19024.985336] usb 1-2: USB disconnect, device number 38
[19024.985359] usb 1-2.1: USB disconnect, device number 39
[19024.985370] usb 1-2.1.1: USB disconnect, device number 40
[19025.030357] r8152 2-2.2:1.0 enx186571e521da: Stop submitting intr, status -71
[19025.049481] usb 1-2.1.2: USB disconnect, device number 41
[19025.151593] usb 1-2.1.4: USB disconnect, device number 42
[19025.276446] usb 2-2.1: Port disable: can't disable remote wake
[19025.555856] r8152 2-2.2:1.0 enx186571e521da: Tx status -71
[19025.735918] usb 1-2: new high-speed USB device number 43 using xhci_hcd
[19025.770499] usb 2-2: USB disconnect, device number 5
[19025.770513] usb 2-2.1: USB disconnect, device number 6
[19025.771766] usb 2-2.2: USB disconnect, device number 7
[19025.778710] pcieport :00:1d.2: AER: Corrected error received: 
:00:1d.2
[19025.778739] pcieport :00:1d.2: PCIe Bus Error: severity=Corrected, 
type=Physical Layer, (Receiver ID)
[19025.778748] pcieport :00:1d.2:   device [8086:9d1a] error 
status/mask=0001/2000
[19025.778760] pcieport :00:1d.2:[ 0] RxErr
[19025.884801] usb 1-2: New USB device found, idVendor=05e3, idProduct=0610, 

[Touch-packages] [Bug 1978079] Re: EFI pstore not cleared on boot

2022-06-17 Thread Launchpad Bug Tracker
** Merge proposal linked:
   
https://code.launchpad.net/~mustafakemalgilor/ubuntu/+source/systemd/+git/systemd/+merge/424958

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

Title:
  EFI pstore not cleared on boot

Status in systemd package in Ubuntu:
  In Progress

Bug description:
  Systemd has a systemd-pstore component that scans the pstore on boot
  and if non-empty, takes all previously created dumps, transfers them
  into its journal and removes the pstore elements. This is very
  important on UEFI systems, which only have a limited amount of space
  for variables.

  In Ubuntu, the kernel is configured with CONFIG_EFI_VARS_PSTORE=m
  which means the EFI pstore support gets loaded dynamically. In all of
  my boots, this dynamic module loading happened *after* systemd tried
  to check for pstore variables. So systemd-pstore never starts and
  never clears the UEFI variable store. I see this happening in AWS on
  Graviton instances, which eventually run out of space to store the
  dumps. On real hardware, this behavior may lead to unbootable systems.

  ```
  $ systemctl status systemd-pstore
  ○ systemd-pstore.service - Platform Persistent Storage Archival
   Loaded: loaded (/lib/systemd/system/systemd-pstore.service; enabled; 
vendor preset: enabled)
   Active: inactive (dead)
Condition: start condition failed at Thu 2022-06-09 09:11:41 UTC; 29min ago
   └─ ConditionDirectoryNotEmpty=/sys/fs/pstore was not met
 Docs: man:systemd-pstore(8)

  Jun 09 09:11:41 ip-172-31-0-61 systemd[1]: Condition check resulted in
  Platform Persistent Storage Archival being skipped.

  $ ls -la /sys/fs/pstore
  total 0
  drwxr-x--- 2 root root0 Jun  9 09:11 .
  drwxr-xr-x 8 root root0 Jun  9 09:11 ..
  -r--r--r-- 1 root root 1803 Jun  9 09:07 dmesg-efi-165476562001001
  -r--r--r-- 1 root root 1777 Jun  9 09:07 dmesg-efi-165476562002001
  -r--r--r-- 1 root root 1773 Jun  9 09:07 dmesg-efi-165476562003001
  -r--r--r-- 1 root root 1815 Jun  9 09:07 dmesg-efi-165476562004001
  -r--r--r-- 1 root root 1826 Jun  9 09:07 dmesg-efi-165476562005001
  -r--r--r-- 1 root root 1754 Jun  9 09:07 dmesg-efi-165476562006001
  -r--r--r-- 1 root root 1821 Jun  9 09:07 dmesg-efi-165476562007001
  -r--r--r-- 1 root root 1767 Jun  9 09:07 dmesg-efi-165476562008001
  -r--r--r-- 1 root root 1729 Jun  9 09:07 dmesg-efi-165476562009001
  -r--r--r-- 1 root root 1819 Jun  9 09:07 dmesg-efi-165476562010001
  -r--r--r-- 1 root root 1767 Jun  9 09:07 dmesg-efi-165476562011001
  -r--r--r-- 1 root root 1775 Jun  9 09:07 dmesg-efi-165476562012001
  -r--r--r-- 1 root root 1802 Jun  9 09:07 dmesg-efi-165476562013001
  -r--r--r-- 1 root root 1812 Jun  9 09:07 dmesg-efi-165476562014001
  -r--r--r-- 1 root root 1764 Jun  9 09:07 dmesg-efi-165476562015001
  -r--r--r-- 1 root root 1795 Jun  9 09:11 dmesg-efi-165476589801001
  -r--r--r-- 1 root root 1785 Jun  9 09:11 dmesg-efi-165476589802001
  -r--r--r-- 1 root root 1683 Jun  9 09:11 dmesg-efi-165476589803001
  -r--r--r-- 1 root root 1785 Jun  9 09:11 dmesg-efi-165476589804001
  -r--r--r-- 1 root root 1771 Jun  9 09:11 dmesg-efi-165476589805001
  -r--r--r-- 1 root root 1797 Jun  9 09:11 dmesg-efi-165476589806001
  -r--r--r-- 1 root root 1805 Jun  9 09:11 dmesg-efi-165476589807001
  -r--r--r-- 1 root root 1781 Jun  9 09:11 dmesg-efi-165476589808001
  -r--r--r-- 1 root root 1806 Jun  9 09:11 dmesg-efi-165476589809001
  -r--r--r-- 1 root root 1821 Jun  9 09:11 dmesg-efi-165476589810001
  -r--r--r-- 1 root root 1763 Jun  9 09:11 dmesg-efi-165476589811001
  -r--r--r-- 1 root root 1783 Jun  9 09:11 dmesg-efi-165476589812001
  -r--r--r-- 1 root root 1788 Jun  9 09:11 dmesg-efi-165476589813001
  -r--r--r-- 1 root root 1788 Jun  9 09:11 dmesg-efi-165476589814001
  -r--r--r-- 1 root root 1786 Jun  9 09:11 dmesg-efi-165476589815001
  ```

  This problem affects (at least) Ubuntu 20.04 and 22.04. A quick fix
  would be to configure CONFIG_EFI_VARS_PSTORE=y so that it's always
  available. A long term fix would make systemd rescan the directory
  after all module probing settled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1978079/+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 1979053] [NEW] UI glitches in GTK application with AMDGPU

2022-06-17 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

After updating to (K)ubuntu 22.04, I see user interface glitches in GTK
application.

Most obviously affected is Gimp, but Evolution and Eclipse IDE are
affected, too.

The glitches don't appear on a notebook with Intel graphics, so maybe
the problem is caused by a weird interaction between the AMDGPU X.Org
driver (I use a Radeon RX5600XT) and GTK.

But as the KDE desktop itself isn't affected and only GTK application
show these glitches, I think it's not a general problem with AMDGPU.

I also booted both Kubunutu and Ubuntu live images and installed Gimp:
The effect show up there, too. So it's than a problem of my actual
installation.

I will upload some Gimp screenshots, so you can see what I mean...

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: libcairo2 1.16.0-5ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-39.42-generic 5.15.35
Uname: Linux 5.15.0-39-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Fri Jun 17 12:36:26 2022
InstallationDate: Installed on 2022-04-27 (50 days ago)
InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
SourcePackage: cairo
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy
-- 
UI glitches in GTK application with AMDGPU
https://bugs.launchpad.net/bugs/1979053
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to cairo 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 1978079] Re: EFI pstore not cleared on boot

2022-06-17 Thread Launchpad Bug Tracker
** Merge proposal linked:
   
https://code.launchpad.net/~mustafakemalgilor/ubuntu/+source/systemd/+git/systemd/+merge/424938

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

Title:
  EFI pstore not cleared on boot

Status in systemd package in Ubuntu:
  In Progress

Bug description:
  Systemd has a systemd-pstore component that scans the pstore on boot
  and if non-empty, takes all previously created dumps, transfers them
  into its journal and removes the pstore elements. This is very
  important on UEFI systems, which only have a limited amount of space
  for variables.

  In Ubuntu, the kernel is configured with CONFIG_EFI_VARS_PSTORE=m
  which means the EFI pstore support gets loaded dynamically. In all of
  my boots, this dynamic module loading happened *after* systemd tried
  to check for pstore variables. So systemd-pstore never starts and
  never clears the UEFI variable store. I see this happening in AWS on
  Graviton instances, which eventually run out of space to store the
  dumps. On real hardware, this behavior may lead to unbootable systems.

  ```
  $ systemctl status systemd-pstore
  ○ systemd-pstore.service - Platform Persistent Storage Archival
   Loaded: loaded (/lib/systemd/system/systemd-pstore.service; enabled; 
vendor preset: enabled)
   Active: inactive (dead)
Condition: start condition failed at Thu 2022-06-09 09:11:41 UTC; 29min ago
   └─ ConditionDirectoryNotEmpty=/sys/fs/pstore was not met
 Docs: man:systemd-pstore(8)

  Jun 09 09:11:41 ip-172-31-0-61 systemd[1]: Condition check resulted in
  Platform Persistent Storage Archival being skipped.

  $ ls -la /sys/fs/pstore
  total 0
  drwxr-x--- 2 root root0 Jun  9 09:11 .
  drwxr-xr-x 8 root root0 Jun  9 09:11 ..
  -r--r--r-- 1 root root 1803 Jun  9 09:07 dmesg-efi-165476562001001
  -r--r--r-- 1 root root 1777 Jun  9 09:07 dmesg-efi-165476562002001
  -r--r--r-- 1 root root 1773 Jun  9 09:07 dmesg-efi-165476562003001
  -r--r--r-- 1 root root 1815 Jun  9 09:07 dmesg-efi-165476562004001
  -r--r--r-- 1 root root 1826 Jun  9 09:07 dmesg-efi-165476562005001
  -r--r--r-- 1 root root 1754 Jun  9 09:07 dmesg-efi-165476562006001
  -r--r--r-- 1 root root 1821 Jun  9 09:07 dmesg-efi-165476562007001
  -r--r--r-- 1 root root 1767 Jun  9 09:07 dmesg-efi-165476562008001
  -r--r--r-- 1 root root 1729 Jun  9 09:07 dmesg-efi-165476562009001
  -r--r--r-- 1 root root 1819 Jun  9 09:07 dmesg-efi-165476562010001
  -r--r--r-- 1 root root 1767 Jun  9 09:07 dmesg-efi-165476562011001
  -r--r--r-- 1 root root 1775 Jun  9 09:07 dmesg-efi-165476562012001
  -r--r--r-- 1 root root 1802 Jun  9 09:07 dmesg-efi-165476562013001
  -r--r--r-- 1 root root 1812 Jun  9 09:07 dmesg-efi-165476562014001
  -r--r--r-- 1 root root 1764 Jun  9 09:07 dmesg-efi-165476562015001
  -r--r--r-- 1 root root 1795 Jun  9 09:11 dmesg-efi-165476589801001
  -r--r--r-- 1 root root 1785 Jun  9 09:11 dmesg-efi-165476589802001
  -r--r--r-- 1 root root 1683 Jun  9 09:11 dmesg-efi-165476589803001
  -r--r--r-- 1 root root 1785 Jun  9 09:11 dmesg-efi-165476589804001
  -r--r--r-- 1 root root 1771 Jun  9 09:11 dmesg-efi-165476589805001
  -r--r--r-- 1 root root 1797 Jun  9 09:11 dmesg-efi-165476589806001
  -r--r--r-- 1 root root 1805 Jun  9 09:11 dmesg-efi-165476589807001
  -r--r--r-- 1 root root 1781 Jun  9 09:11 dmesg-efi-165476589808001
  -r--r--r-- 1 root root 1806 Jun  9 09:11 dmesg-efi-165476589809001
  -r--r--r-- 1 root root 1821 Jun  9 09:11 dmesg-efi-165476589810001
  -r--r--r-- 1 root root 1763 Jun  9 09:11 dmesg-efi-165476589811001
  -r--r--r-- 1 root root 1783 Jun  9 09:11 dmesg-efi-165476589812001
  -r--r--r-- 1 root root 1788 Jun  9 09:11 dmesg-efi-165476589813001
  -r--r--r-- 1 root root 1788 Jun  9 09:11 dmesg-efi-165476589814001
  -r--r--r-- 1 root root 1786 Jun  9 09:11 dmesg-efi-165476589815001
  ```

  This problem affects (at least) Ubuntu 20.04 and 22.04. A quick fix
  would be to configure CONFIG_EFI_VARS_PSTORE=y so that it's always
  available. A long term fix would make systemd rescan the directory
  after all module probing settled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1978079/+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 1973441] Re: Printing does not work on Ubuntu 22.04 - cups-pki-invalid

2022-06-17 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Printing does not work on Ubuntu 22.04 - cups-pki-invalid

Status in cups package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 22.04 printing did not work. There is cups-pki-
  invalid error and printer goes to paused state.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: cups 2.4.1op1-1ubuntu4
  Uname: Linux 5.17.7-051707-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CupsErrorLog: Error: [Errno 13] Permission denied: '/var/log/cups/error_log'
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 15 15:34:47 2022
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2021-10-12 (214 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211010)
  Lpstat: device for HP_Color_LaserJet_M552_5F80BF: 
implicitclass://HP_Color_LaserJet_M552_5F80BF/
  MachineType: ASUSTeK COMPUTER INC. ROG Strix G513QY_G513QY
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/HP_Color_LaserJet_M552_5F80BF.ppd'] failed with exit code 2: 
grep: /etc/cups/ppd/HP_Color_LaserJet_M552_5F80BF.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.17.7-051707-generic 
root=UUID=ff964c9b-ce92-4334-8759-9d785a262c60 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: Upgraded to jammy on 2022-04-24 (21 days ago)
  dmi.bios.date: 03/29/2022
  dmi.bios.release: 5.19
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: G513QY.318
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: G513QY
  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.ec.firmware.release: 0.81
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG513QY.318:bd03/29/2022:br5.19:efr0.81:svnASUSTeKCOMPUTERINC.:pnROGStrixG513QY_G513QY:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnG513QY:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
  dmi.product.family: ROG Strix
  dmi.product.name: ROG Strix G513QY_G513QY
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1973441/+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 1978980] [NEW] Wrong external screen resolution after wake up from sleep

2022-06-16 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

After the Ubuntu distro upgrade (upgrade from LTS 20.04 to LTS 22.04,
running KDE) I started experiencing a problem with external screen
resolution after the wake up from sleep. The monitor resolution is small
(1280x768) and doesn't respect the setting prior the sleep (1920x1200).

After the wake up from sleep:

```
> xrandr
HDMI-A-0 disconnected (normal left inverted right x axis y axis)
DisplayPort-0 disconnected (normal left inverted right x axis y axis)
DisplayPort-1 connected primary 1280x768+0+0 (normal left inverted right x axis 
y axis) 535mm x 339mm
   1280x768  59.94* 
   # a list of lower resolutions
```

There is an error when trying to change the setting to the highest
resolution supported by the monitor (which is not included in the above
list).

```
> xrandr --output DisplayPort-1 --mode 1920x1200
xrandr: cannot find mode 1920x1200
```

After the turn off and turn on of the external monitor, the resolution
is somehow added to the xrandr list:

```
> xrandr
HDMI-A-0 disconnected (normal left inverted right x axis y axis)
DisplayPort-0 disconnected (normal left inverted right x axis y axis)
DisplayPort-1 connected primary 1280x768+0+0 (normal left inverted right x axis 
y axis) 535mm x 339mm
   1920x1200 59.95 +
   # a list of resolutions
   1280x768  59.94* 
   # a list of lower resolutions
```

Now it is possible to change the resolution:

```
> xrandr --output DisplayPort-1 --mode 1920x1200
# no output, the resolution was successfully changed
```   

After the change, the resolution is successfully changed and xrandr
gives proper output:

```
> xrandr
HDMI-A-0 disconnected (normal left inverted right x axis y axis)
DisplayPort-0 disconnected (normal left inverted right x axis y axis)
DisplayPort-1 connected primary 1920x1200+0+0 (normal left inverted right x 
axis y axis) 535mm x 339mm
   1920x1200 59.95*+
   # a list of lower resolutions
```

The problem is not present on fresh start. However, it is consistently
present after the wake up from sleep.

What can cause the problem and how may I fix it?

Running AMD based laptop (Ryzen 7 3700U with integrated graphics), the
external monitor is connected via USB-C. There are no problems with
laptop screen resolution, only external monitor is affected.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35
Uname: Linux 5.15.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: unknown
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: KDE
Date: Thu Jun 16 18:12:05 2022
DistUpgraded: 2022-05-08 07:52:25,560 DEBUG icon theme changed, re-reading
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Picasso/Raven 2 [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15d8] (rev c1) (prog-if 00 [VGA controller])
   Subsystem: Lenovo ThinkPad E595 [17aa:5124]
InstallationDate: Installed on 2019-08-21 (1030 days ago)
InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: LENOVO 20NE000BMC
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-37-generic 
root=UUID=0fff4104-4909-4124-b8b0-8430281f24be ro open splash iommu=soft 
vt.handoff=7
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to jammy on 2022-05-08 (39 days ago)
dmi.bios.date: 01/26/2022
dmi.bios.release: 1.24
dmi.bios.vendor: LENOVO
dmi.bios.version: R11ET44W (1.24 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20NE000BMC
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.24
dmi.modalias: 
dmi:bvnLENOVO:bvrR11ET44W(1.24):bd01/26/2022:br1.24:efr1.24:svnLENOVO:pn20NE000BMC:pvrThinkPadE495:rvnLENOVO:rn20NE000BMC:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20NE_BU_Think_FM_ThinkPadE495:
dmi.product.family: ThinkPad E495
dmi.product.name: 20NE000BMC
dmi.product.sku: LENOVO_MT_20NE_BU_Think_FM_ThinkPad E495
dmi.product.version: ThinkPad E495
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2.1
version.libgl1-mesa-glx: libgl1-mesa-glx 22.0.1-1ubuntu2.1
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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

[Touch-packages] [Bug 1978476] Re: Incorrect UNTIL recurrence with midnight start

2022-06-16 Thread Launchpad Bug Tracker
This bug was fixed in the package evolution-data-server - 3.44.2-2

---
evolution-data-server (3.44.2-2) unstable; urgency=medium

  * Cherry-pick patch to fix recurring calendar events starting at midnight
(LP: #1978476)

 -- Jeremy Bicha   Tue, 14 Jun 2022 13:16:57 -0400

** Changed in: evolution-data-server (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Incorrect UNTIL recurrence with midnight start

Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in evolution-data-server source package in Focal:
  Triaged
Status in evolution-data-server source package in Jammy:
  Triaged

Bug description:
  Impact
  --

  EDS generates instances for recurring events starting at midnight with
  an UNTIL date  incorrectly. Specifically, using
  e_cal_client_generate_instances() or
  e_cal_recur_generate_instances_sync() generates an instance one day
  after the UNTIL date. This bug was introduced with the migration to
  libical-glib and libecal-2.0, so this affects bot focal and jammy. It
  was fixed with commit 3969303e (master) and 7fb64814 (gnome-42) which
  will be part of the 3.45.1+ and 3.44.3+ releases respectively.

  Upstream bug report: https://gitlab.gnome.org/GNOME/evolution-data-
  server/-/issues/393

  Test Case
  -

  
  What Could Go Wrong
  ---

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1978476/+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 1978942] [NEW] Sound problem. The sound is a few minutes away. A buzzer signal then appears. The image is also bad.

2022-06-16 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Sound problem. The sound is a few minutes away. A buzzer signal then
appears. The image is also bad.

ProblemType: Bug
DistroRelease: Ubuntu 22.10
Package: gstreamer1.0-plugins-good 1.20.2-1ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35
Uname: Linux 5.15.0-37-generic x86_64
ApportVersion: 2.21.0-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Thu Jun 16 15:17:35 2022
InstallationDate: Installed on 2022-05-19 (27 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
SourcePackage: gst-plugins-good1.0
UpgradeStatus: Upgraded to kinetic on 2022-06-13 (2 days ago)

** Affects: gst-plugins-good1.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug kinetic wayland-session
-- 
Sound problem. The sound is a few minutes away. A buzzer signal then appears. 
The image is also bad.
https://bugs.launchpad.net/bugs/1978942
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to gst-plugins-good1.0 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 1977968] Re: Security update tracking bug

2022-06-15 Thread Launchpad Bug Tracker
This bug was fixed in the package bluez - 5.48-0ubuntu3.9

---
bluez (5.48-0ubuntu3.9) bionic-security; urgency=medium

  * SECURITY UPDATE: various security improvements (LP: #1977968)
- debian/patches/avdtp-security.patch: check if capabilities are valid
  before attempting to copy them in profiles/audio/avdtp.c.
- debian/patches/avdtp-security-2.patch: fix size comparison and
  variable misassignment in profiles/audio/avdtp.c.
- debian/patches/avrcp-security.patch: make sure the number of bytes in
  the params_len matches the remaining bytes received so the code don't
  end up accessing invalid memory in profiles/audio/avrcp.c.
- No CVE numbers

 -- Marc Deslauriers   Wed, 08 Jun 2022
07:19:20 -0400

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

Title:
  Security update tracking bug

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  This bug is to track the security update that will contain these
  possibly security-relevant commits:

  
https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?id=e2b0f0d8d63e1223bb714a9efb37e2257818268b

  
https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?id=7a80d2096f1b7125085e21448112aa02f49f5e9a

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1977968/+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 1977968] Re: Security update tracking bug

2022-06-15 Thread Launchpad Bug Tracker
This bug was fixed in the package bluez - 5.53-0ubuntu3.6

---
bluez (5.53-0ubuntu3.6) focal-security; urgency=medium

  * SECURITY UPDATE: various security improvements (LP: #1977968)
- debian/patches/avdtp-security.patch: check if capabilities are valid
  before attempting to copy them in profiles/audio/avdtp.c.
- debian/patches/avdtp-security-2.patch: fix size comparison and
  variable misassignment in profiles/audio/avdtp.c.
- debian/patches/avrcp-security.patch: make sure the number of bytes in
  the params_len matches the remaining bytes received so the code don't
  end up accessing invalid memory in profiles/audio/avrcp.c.
- No CVE numbers

 -- Marc Deslauriers   Wed, 08 Jun 2022
07:09:00 -0400

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

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

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

Title:
  Security update tracking bug

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  This bug is to track the security update that will contain these
  possibly security-relevant commits:

  
https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?id=e2b0f0d8d63e1223bb714a9efb37e2257818268b

  
https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/?id=7a80d2096f1b7125085e21448112aa02f49f5e9a

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1977968/+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 1977982] Re: Please merge keyutils 1.6.1-3 (main) from Debian unstable (main)

2022-06-15 Thread Launchpad Bug Tracker
This bug was fixed in the package keyutils - 1.6.1-3ubuntu1

---
keyutils (1.6.1-3ubuntu1) kinetic; urgency=medium

  * Merge from Debian unstable (LP: #1977982).
Remaining changes:
- d/p/apply-ttl-records.patch: Add patch to apply default TTL to records
  obtained from getaddrinfo(). (LP: #1962453)
Dropped patches:
- d/p/private-priv.patch: This patch was fixing a FTBFS issue for nuxwdog
  which is no longer present in the archive. Other packages that
  build-depend on libkeyutils-dev do not FTBFS in Debian currently ; where
  the patch is not applied.

keyutils (1.6.1-3) unstable; urgency=medium

  * Bump Standards-Version to 4.6.0 (no changes needed)
  * Bump debhelper compatibility to 13
  * Drop cifs.patch (obsolete)

keyutils (1.6.1-2ubuntu3) jammy; urgency=medium

  * d/p/apply-default-ttl-to-records.patch: Add patch
to apply default TTL to records obtained from
getaddrinfo(). (LP: #1962453)

keyutils (1.6.1-2ubuntu2) impish; urgency=medium

  * No-change rebuild to build packages with zstd compression.

 -- Olivier Gayot   Wed, 08 Jun 2022
17:25:33 +0200

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

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

Title:
  Please merge keyutils 1.6.1-3 (main) from Debian unstable (main)

Status in keyutils package in Ubuntu:
  Fix Released

Bug description:
  The Ubuntu delta contains two patches:

  * d/p/private-priv.patch:
  This patch was applied in Ubuntu to fix a FTBFS issue on nuxwdog. nuxwdog was 
a C++ project and would include the header file from libkeyutils-dev. 
Unfortunately, the header file contains variables named "private" - which is a 
keyword in C++ but not in C.
  The last version of nuxwdog from the archive is in Bionic so I am tempted to 
drop this patch. The bug report on Debian was closed/not-fixed when nuxwdog was 
removed from the archive: 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923011
  If we drop this, there is a chance, however, that other packages would FTBFS 
if they build-depends on libkeyutils-dev and include the C header in C++ code. 
Here is the list of packages that build-depends on libkeyutils-dev:
    * bcachefs-tools
    * ceph
    * cifs-utils
    * ecryptfs-utils
    * gdm3
    * gssproxy
    * ima-evm-utils
    * kafs-client
    * krb5
    * kstart
    * ndctl
    * nfs-utils
    * python-keyutils
    * sssd
    * stress-ng
  All these packages are in Debian unstable today and are not FTBFS, so I'd 
assume it's fine to drop the patch.

  * d/p/apply-ttl-to-records.patch:
  This patch was applied recently (from upstream) to fix #1962453. I think we 
need to keep this patch and I'm considering forwarding it to Debian.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/keyutils/+bug/1977982/+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 1969896] Re: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched

2022-06-15 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Evince Document Viewer(42.0) does not remember last page in 22.04 and
  opens in a tiny window when launched

Status in apparmor package in Ubuntu:
  Confirmed
Status in evince package in Ubuntu:
  In Progress

Bug description:
  Just switched from Ubuntu 20.04 to 22.04 and realized that Document
  Viewer no longer open on the last viewed page and doesn't remember the
  side pane preference even after using the "Save Current Settings as
  Default" option. Kindly advise

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: evince 42.1-3
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 22 15:58:50 2022
  InstallationDate: Installed on 2022-03-19 (34 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: Upgraded to jammy on 2022-04-21 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1969896/+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 1969460] Re: software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings

2022-06-14 Thread Launchpad Bug Tracker
This bug was fixed in the package software-properties - 0.99.22.2

---
software-properties (0.99.22.2) jammy; urgency=medium

  * softwareproperties/gtk/SoftwarePropertiesGtk.py:
Don't crash if the driver package does not have a matching modules package
Fixes LP: #1969460

 -- Alberto Milone   Tue, 31 May 2022
11:39:13 +0200

** Changed in: software-properties (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

Title:
  software-properties-gtk crashed with TypeError in
  on_driver_selection_changed(): Expected a string or a pair of strings

Status in OEM Priority Project:
  Fix Committed
Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Jammy:
  Fix Released

Bug description:
  - Impact

  software-properties-gtk hit an exception when dealing some drivers

  - Test Case

  On a Dell XPS 13 9320 enable ppa:oem-solutions-group/intel-ipu6 and
  try to install libcamhal-ipu6ep0 using software-properties-gtk

  https://errors.ubuntu.com/problem/d3c26abd1d80970615ad06cff24972cee3001e57
  should not include reports on the new version

  - Regression potential

  The change make the driver code ignore one extra type of error, it
  shouldn't impact on any of the already working cases. Ensure that
  drivers that were hitting the error correctly install now

  [racb] It's possible that we accidentally catch and hide a real error
  due to an unrelated TypeError exception being raised inside the try
  block.

  

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Ubuntu 22.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
   software-properties-gtk 0.99.22

  3) What you expected to happen
  No crash when using Additional Drivers with 
ppa:oem-solutions-group/intel-ipu6 on Dell XPS 13 9320
  It can install libcamhal-ipu6ep0 from Additional Drivers without any problem.

  4) What happened instead
  It crashed when selecting libcamhal-ipu6ep0 in Additional Drivers

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1969460/+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 1974456] Re: regression: apt.postint fails if never previously configured

2022-06-14 Thread Launchpad Bug Tracker
This bug was fixed in the package apt - 2.0.9

---
apt (2.0.9) focal; urgency=medium

  * postinst: Do not run removed kernel postinst.d script (LP: #1974456)

 -- Julian Andres Klode   Tue, 24 May 2022 15:08:25
+0200

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

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

Title:
  regression: apt.postint fails if never previously configured

Status in apt package in Ubuntu:
  Confirmed
Status in apt source package in Bionic:
  Confirmed
Status in apt source package in Focal:
  Fix Released

Bug description:
  [Impact]
  bootstrapping a system with apt that fixes #1968154 fails in focal and 
bionic, as they try to execute the config file that is being removed.

  This is not a problem on updates, only on new installs, so impact is
  limited to bootstrapping tools that enable -updates, such as
  mmdebstrap.

  [Test case]

  bootstrapping with -updates enabled can easily be tested with
  mmdebstrap:

  mmdebstrap -v focal ~/Projects/Ubuntu/Scratch/focal

  for example, on focal:

  Setting up apt (2.0.8) ...
  /var/lib/dpkg/info/apt.postinst: 65: /etc/kernel/postinst.d/apt-auto-removal: 
not found
  dpkg: error processing package apt (--configure):
   installed apt package post-installation script subprocess returned error 
exit status 127

  [Regression potential]
  We remove 5 lines from the shell postinst script, there could be syntax 
errors? But then we'd see those during upgrades, so practically none.

  [Original bug report]
  #1968154 removed `/etc/kernel/postinst.d/apt-auto-removal` in this patch:
  
https://git.launchpad.net/ubuntu/+source/apt/commit/?id=f9d2d993687c0d5223c241956ef6a0aabcf15bf0

  ...but `apt.postinst` still tries to run it:

  # create kernel autoremoval blacklist on update
  if dpkg --compare-versions "$2" lt 0.9.9.3; then
  /etc/kernel/postinst.d/apt-auto-removal
  fi

  If I understand correctly, "$2" is the most-recently-configured-
  version, and if it's empty `dpkg --compare-versions lt` will evaluate
  to true.

  This fails when I'm building a focal (20.04) userspace from scratch:

  $ dpkg --configure -a
  [...]
  Setting up apt (2.0.8) ...
  /var/lib/dpkg/info/apt.postinst: 65: 
/etc/kernel/postinst.d/apt-auto-removal: not found
  dpkg: error processing package apt (--configure):
   installed apt package post-installation script subprocess returned error 
exit status 127

  It works with apt 2.0.6.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1974456/+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 1814302] Re: Quasselcore apparmor profile issue in lxd container.

2022-06-14 Thread Launchpad Bug Tracker
This bug was fixed in the package quassel - 1:0.14.0-1ubuntu1

---
quassel (1:0.14.0-1ubuntu1) kinetic; urgency=medium

  * d/usr.bin.quasselcore:
- Update apparmor profile to allow running in lxd (LP: #1814302)

 -- Dave Jones   Sun, 12 Jun 2022 20:52:19
+0100

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

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

Title:
  Quasselcore apparmor profile issue in lxd container.

Status in AppArmor:
  Invalid
Status in apparmor package in Ubuntu:
  Invalid
Status in quassel package in Ubuntu:
  Fix Released
Status in apparmor source package in Bionic:
  Invalid
Status in quassel source package in Bionic:
  Fix Released
Status in apparmor source package in Focal:
  Invalid
Status in quassel source package in Focal:
  Fix Released
Status in apparmor source package in Groovy:
  Invalid
Status in quassel source package in Groovy:
  Fix Released
Status in apparmor source package in Jammy:
  Invalid
Status in quassel source package in Jammy:
  Confirmed
Status in apparmor source package in Kinetic:
  Invalid
Status in quassel source package in Kinetic:
  Fix Released

Bug description:
  [impact]

  quasselcore cannot start inside lxd container

  [test case]

  create lxd container, install quassel-core, check quasselcore service:

  $ systemctl status quasselcore
  ● quasselcore.service - distributed IRC client using a central core component
   Loaded: loaded (/lib/systemd/system/quasselcore.service; enabled; vendor 
preset: enabled)
   Active: failed (Result: signal) since Tue 2020-06-30 18:32:40 UTC; 4s ago
 Docs: man:quasselcore(1)
  Process: 3853 ExecStart=/usr/bin/quasselcore --configdir=${DATADIR} 
--logfile=${LOGFILE} --loglevel=${LOGLEVEL} --port=${PORT} --listen=${LISTEN} 
(code=killed, signal=SEGV)
 Main PID: 3853 (code=killed, signal=SEGV)

  Jun 30 18:32:40 lp1814302-f systemd[1]: quasselcore.service: Scheduled 
restart job, restart counter is at 7.
  Jun 30 18:32:40 lp1814302-f systemd[1]: Stopped distributed IRC client using 
a central core component.
  Jun 30 18:32:40 lp1814302-f systemd[1]: quasselcore.service: Start request 
repeated too quickly.
  Jun 30 18:32:40 lp1814302-f systemd[1]: quasselcore.service: Failed with 
result 'signal'.
  Jun 30 18:32:40 lp1814302-f systemd[1]: Failed to start distributed IRC 
client using a central core component.

  
  Also, the binary will segfault when run directly due to apparmor denials:

  $ /usr/bin/quasselcore 
  Segmentation fault

  [760149.590802] audit: type=1400 audit(1593542073.962:1058):
  apparmor="DENIED" operation="file_mmap" namespace="root//lxd-
  lp1814302-f_" profile="/usr/bin/quasselcore"
  name="/usr/bin/quasselcore" pid=2006430 comm="quasselcore"
  requested_mask="r" denied_mask="r" fsuid=1000110 ouid=100

  [regression potential]

  this expands the apparmor profile, so any regression would likely
  involve problems while starting due to apparmor.

  [scope]

  this is needed for b/f/g.

  this is also needed for e, but that is EOL in weeks and this is not
  important enough to bother there.

  [original description]

  
  Fresh install of Ubuntu 18.04. lxd installed from snap. Fresh 18.04 
container. Everything up todate via apt.

  Install quassel-core. Service will not start.

  Set "aa-complain /usr/bin/quasselcore" allows quasselcore to start.

  I then added "/usr/bin/quasselcore rm," to
  "/etc/apparmor.d/usr.bin.quasselcore".

  Set "aa-enforce /usr/bin/quasselcore". Restarted main host.

  Quasselcore service now starts and I can connect to it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1814302/+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 1975785] Re: package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1

2022-06-14 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

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

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  failed to install initramfs-tools

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6.7
  Uname: Linux 5.16.19-76051619-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed May 25 22:33:13 2022
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2022-02-26 (88 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  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.8
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1975785/+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 1977645] Re: python3-gpg "1.16.0-unknown" version is incomparable -> dependencies always fail

2022-06-14 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gpgme1.0 (Ubuntu)
   Status: New => Confirmed

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

Title:
  python3-gpg "1.16.0-unknown" version is incomparable -> dependencies
  always fail

Status in gpgme1.0 package in Ubuntu:
  Confirmed

Bug description:
  The python version of the gpgme version contains "unknown" and is
  therefore not PEP440 order compatible.

  See this example:

# pip3 freeze | grep gpg
gpg===1.16.0-unknown

# pip3 install pstore
...
Successfully installed gpg-1.10.0
Successfully installed pstore-2.0.0

# pip3 freeze | grep gpg
gpg==1.10.0

  
  Key takeways from that example:

  - pstore depends on gpg>=1.10

  - 1.16 SHOULD be higher than 1.10

  - pip installs 1.10 even though 1.16 exists

  - the triple-= (gpg===1.16.0-unknown) means that the version exists,
  but cannot be version compared:
  https://peps.python.org/pep-0440/#arbitrary-equality


  Suggested fix:

  - replace the '-' from `gpgme-config --version` "1.16.0-unknown" with
  a '+'; that will compare as expected;

  - fix so "-unknown" isn't appended.

  
  Apparently, this is caused by insufficient fixes in 
0001-avoid-identifying-as-beta.patch

  I've attached a FIXED version, which should fix things.

  Before:

$ autoreconf -ivf

$ grep Generated.*gpgme configure
# Generated by GNU Autoconf 2.71 for gpgme 1.16.0-unknown.

  After:

$ quilt push 
Applying patch 0001-avoid-identifying-as-beta-FIXED.patch

$ autoreconf -ivf

$ grep Generated.*gpgme configure
# Generated by GNU Autoconf 2.71 for gpgme 1.16.0.

  
  Versions:

  $ lsb_release -a 2>/dev/null| grep Codename
  Codename: jammy

  $ apt-cache policy python3-gpg  | grep Installed
Installed: 1.16.0-1.2ubuntu4

  
  Cheers,
  Walter Doekes
  OSSO B.V.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gpgme1.0/+bug/1977645/+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 1905493] Re: cloud-init status --wait hangs indefinitely in a nested lxd container

2022-06-13 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  cloud-init status --wait hangs indefinitely in a nested lxd container

Status in AppArmor:
  New
Status in cloud-init:
  Invalid
Status in snapd:
  Confirmed
Status in dbus package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  When booting a nested lxd container inside another lxd container (just
  a normal container, not a VM) (i.e. just L2), using cloud-init -status
  --wait, the "." is just printed off infinitely and never returns.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1905493/+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 1971089] Re: Network Manager bug constant reconnecting and CPU usage

2022-06-11 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: network-manager (Ubuntu)
   Status: New => Confirmed

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

Title:
  Network Manager bug constant reconnecting and CPU usage

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Anyconnectin result cpu heavy usage. constant reconnections
  wifi/ethernet..no matter

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: network-manager 1.36.4-2ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Sun May  1 17:00:00 2022
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-06-03 (1793 days ago)
  InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  IpRoute:
   default via 192.168.1.1 dev enp5s0 proto dhcp metric 100 
   169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 
   172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
   192.168.1.0/24 dev enp5s0 proto kernel scope link src 192.168.1.148 metric 
100
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to jammy on 2022-04-25 (6 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN 
   running  1.36.4   connected  started  full  enabled enabled  
enabled  enabled  disabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1971089/+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 1433787] Re: rsync corrupts systematically jpg files when copying from jmtpfs

2022-06-10 Thread Launchpad Bug Tracker
[Expired for rsync (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  rsync corrupts systematically jpg files when copying from jmtpfs

Status in rsync package in Ubuntu:
  Expired

Bug description:
  rsync corrupts systematically jpg files when copying from jmtpfs
  I am filing the bug with rsync because neither cp nor scp show the problem. 
They copy the images just fine. Therefore I assume it is not a problem of 
jmtpfs.
  When I want to view the jpg files after a copy with rsync I get the following 
error: "Error interpreting JPEG image file (Application transferred too few 
scanlines)".
  Rsync runs through though and does not output any error nor warning.

  root@kimera:~# lsb_release -rd
  Description:  Ubuntu 14.10
  Release:  14.10

  root@kimera:~# apt-cache policy rsync
  rsync:
Installed: 3.1.1-2
Candidate: 3.1.1-2
Version table:
   *** 3.1.1-2 0
  500 http://ch.archive.ubuntu.com/ubuntu/ utopic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: rsync 3.1.1-2
  ProcVersionSignature: Ubuntu 3.16.0-31.43-generic 3.16.7-ckt5
  Uname: Linux 3.16.0-31-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Mar 18 21:47:32 2015
  InstallationDate: Installed on 2015-01-14 (63 days ago)
  InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: rsync
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1433787/+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 1964100] Re: Cannot connect to open WLAN with 1.36.0-1ubuntu2 on Jammy

2022-06-10 Thread Launchpad Bug Tracker
[Expired for network-manager (Ubuntu) because there has been no activity
for 60 days.]

** Changed in: network-manager (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Cannot connect to open WLAN with 1.36.0-1ubuntu2 on Jammy

Status in network-manager package in Ubuntu:
  Expired

Bug description:
  I'm trying to connect to an open (i.e. no ecryption) WLAN with
  network-manager 1.36.0-1ubuntu2 on 22.04 but it's failing with the
  following error message (after selecting the network from the network-
  manager applet prompt):

  Mär 08 10:50:04 Isaac-Laptop NetworkManager[31754]: 
  [1646733004.4425] audit: op="connection-add-activate" pid=12122
  uid=1000 result="fail" reason="802-11-wireless-security.key-mgmt:
  Access point does not support PSK but setting requires it"

  I haven't changed any of the default settings for network-manager and
  this network worked on 20.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1964100/+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 1978349] [NEW] Monitors sometimes permanently blanked after resume

2022-06-10 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Sometimes monitors don't wake up after resume. Happened couple times with 
Ubuntu 22.04 so far.
Journalctl lists only one instance of this, might have failed to save the logs 
on other times.

kernel BUG at
drivers/gpu/drm/amd/amdgpu/../display/amdgpu_dm/amdgpu_dm.c:10039!

1. (assumedly) occurs when resuming from ram
2. suspend chosen from ui
3. resume by clicking key on keyboard
4.-11. not tested yet with mainline builds, since uncertain about how to 
reproduce reliably.
12. openssh-server only installed after today's instance, so don't have much 
debug data beyond what was saved in logs before sysrq-sub.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35
Uname: Linux 5.15.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Jun 10 23:02:04 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GpuHangFrequency: Very infrequently
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Navi 14 [Radeon RX 5500/5500M / Pro 
5500M] [1002:7340] (rev c5) (prog-if 00 [VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 14 [Radeon RX 
5500/5500M / Pro 5500M] [1462:3822]
InstallationDate: Installed on 2022-04-27 (44 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-37-generic 
root=UUID=69fa5235-bbc4-4603-9895-5e7017992b3c ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/16/2012
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2106
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8B WS
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2106:bd07/16/2012:br4.6:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8BWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:skuSKU:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1
--- 
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  iheino 4966 F pulseaudio
 /dev/snd/controlC1:  iheino 4966 F pulseaudio
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2022-04-27 (44 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
MachineType: System manufacturer System Product Name
Package: linux (not installed)
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-37-generic 
root=UUID=69fa5235-bbc4-4603-9895-5e7017992b3c ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-37-generic N/A
 linux-backports-modules-5.15.0-37-generic  N/A
 linux-firmware 20220329.git681281e4-0ubuntu3
RfKill:
 
Tags:  jammy wayland-session
Uname: Linux 5.15.0-37-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 07/16/2012
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2106
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8B WS
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 

[Touch-packages] [Bug 1962454] Re: Oops pages show wrong time window in JournalErrors

2022-06-10 Thread Launchpad Bug Tracker
This bug was fixed in the package apport - 2.21.0-0ubuntu2

---
apport (2.21.0-0ubuntu2) kinetic; urgency=medium

  * tests: Use unlimited core ulimit for SIGQUIT test
  * data/apport: Fix log file writing if chown/chmod fails

 -- Benjamin Drung   Fri, 10 Jun 2022 15:39:32 +0200

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

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

Title:
  Oops pages show wrong time window in JournalErrors

Status in Apport:
  Fix Released
Status in Errors:
  Invalid
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Jammy:
  Triaged

Bug description:
  For example, I just experienced a crash at:

Feb 28 17:31:12

  And the JournalErrors entries are:

Feb 28 17:31:30 - Feb 28 17:31:41

  So don't relate to the crash.

  But it should be possible to tell journalctl to collect entries
  starting *before* the crash and cover the full crash timeframe.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1962454/+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 1978093] Re: openssl: FTBFS due to expired certificates

2022-06-10 Thread Launchpad Bug Tracker
This bug was fixed in the package openssl - 3.0.3-5ubuntu3

---
openssl (3.0.3-5ubuntu3) kinetic; urgency=medium

  * d/p/lp1978093/*: renew some expiring test certificates (LP:
#1978093)

 -- Simon Chopin   Thu, 09 Jun 2022 13:20:55 +0200

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

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

Title:
  openssl: FTBFS due to expired certificates

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Bionic:
  New
Status in openssl source package in Focal:
  New
Status in openssl source package in Impish:
  New
Status in openssl source package in Jammy:
  Fix Committed
Status in openssl source package in Kinetic:
  Fix Released

Bug description:
  [Impact]

  Some certificates in the openssl package expired on 2022-06-01, making
  the test suite fail. This needs to be fixed to facilitate future
  security updates.

  [Test Plan]

  Build the package. It currently fails with the following test summary:

  80-test_ssl_new.t(Wstat: 256 Tests: 30 Failed: 1)
Failed test:  12
Non-zero exit status: 1

  [Where problems could occur]

  I supposed this could break the build even worse.

  [Other Info]
   
  This currently prevents 3.0.2-0ubuntu1.3 in Jammy from publication.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1978093/+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 1968478] Re: ibus-x11 crashed with SIGSEGV in g_closure_invoke()

2022-06-09 Thread Launchpad Bug Tracker
[Expired for ibus (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  ibus-x11 crashed with SIGSEGV in g_closure_invoke()

Status in ibus package in Ubuntu:
  Expired

Bug description:
  Description:  Ubuntu Jammy Jellyfish (development branch)
  Release:  22.04

  ibus:
Installed: 1.5.26-3
Candidate: 1.5.26-3
Version table:
   *** 1.5.26-3 500
  500 http://pl.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  4) What happened instead
  closed

  ProblemType: Crash
  DistroRelease: Ubuntu 22.04
  Package: ibus 1.5.26-3
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 10 16:44:38 2022
  Disassembly: => 0x7fba2e2504f0:   Cannot access memory at address 
0x7fba2e2504f0
  ExecutablePath: /usr/libexec/ibus-x11
  InstallationDate: Installed on 2022-04-10 (0 days ago)
  InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 
(20220409)
  ProcCmdline: /usr/libexec/ibus-x11
  SegvAnalysis:
   Segfault happened at: 0x7fba2e2504f0:Cannot access memory at address 
0x7fba2e2504f0
   PC (0x7fba2e2504f0) not located in a known VMA region (needed executable 
region)!
  SegvReason: executing unknown VMA
  Signal: 11
  SourcePackage: ibus
  StacktraceTop:
   ?? ()
   g_closure_invoke () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   ?? () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit_valist () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
   g_signal_emit () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: ibus-x11 crashed with SIGSEGV in g_closure_invoke()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1968478/+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 1964494] Re: Setting DuplicateAddressDetection=none doesn't disable DAD for link-local IPs

2022-06-09 Thread Launchpad Bug Tracker
This bug was fixed in the package systemd - 249.11-0ubuntu4

---
systemd (249.11-0ubuntu4) kinetic; urgency=medium

  * d/p/lp1964494-network-do-not-enable-IPv4-ACD-for-IPv4-link-local-a.patch:
do not enable IPv4 ACD for IPv4 link-local address if ACD is
disabled explicitly (LP: #1964494)

 -- Dan Streetman   Tue, 31 May 2022 08:25:36 -0400

** Changed in: systemd (Ubuntu Kinetic)
   Status: Fix Committed => 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/1964494

Title:
  Setting DuplicateAddressDetection=none doesn't disable DAD for link-
  local IPs

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Jammy:
  In Progress
Status in systemd source package in Kinetic:
  Fix Released

Bug description:
  [impact]

  manual disabling of ipv4 DAD (IACD) for static link-local address does
  not work in jammy

  [test case]

  see 'Reproducer' in original description below

  [regression potential]

  failure to disable DAD, or incorrect disabling of DAD, or networkd
  issues around parsing of DAD config parsing

  [scope]

  this is needed for j and k

  introduced upstream by commit
  1cf4ed142d6c1e2b9dc6a0bc74b6a83ae30b0f8e, first included in v249, so
  this bug does not affect impish or earlier

  fixed upstream by commit 2859932bd64d61a89f85fa027762bc16961fcf53

  [original description]

  A customer reported network disconnections on their storage
  servers when running 'netplan apply'. The culprit was that
  they have link-local addresses configured and the Duplicate
  Address Detection (DAD) mechanism was delaying the interfaces
  from coming back up.

  As a workaround we tried to disable DAD for the interfaces
  but that's not working in Ubuntu 22.04:

  I've noticed that setting DuplicateAddressDetection=none for an
  interface with a link-local address (e.g., 169.254.*) via a
  .network file added to /etc/systemd/network/ doesn't really
  disable Duplicate Address Detection.

  OS and package versions:
  
   - Description:   Ubuntu Jammy Jellyfish (development branch). Release: 
22.04
   - systemd 249.5-2ubuntu4

  Reproducer:
  ---
  1- Set up Ubuntu 22.04 VM
  2- Increase systemlog level:

    mkdir -p /etc/systemd/system/systemd-networkd.service.d/
    cat > /etc/systemd/system/systemd-networkd.service.d/10-debug.conf 

[Touch-packages] [Bug 1978129] [NEW] Incomplete support for DT_RELR relocations on Ubuntu 22.04

2022-06-09 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

== Comment: #0 - Matheus Salgueiro Castanho  - 2022-06-09 
09:32:29 ==
---Problem Description---
Latest glibc uses DT_RELR relocations, but linker support is incomplete as of 
binutils-2.38-3ubuntu1 on Ubuntu 22.04. It lacks the following fix integrated 
into the upstream 2.38 branch:
 
PowerPC64 DT_RELR relative reloc addresses
https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=e4a35c7319628045302d4c597cb27f1b0a08c858

As mentioned in the binutils mailing list when this patch was discussed, this 
fixes several glibc regressions:
https://sourceware.org/pipermail/binutils/2022-March/119921.html
 
Contact Information = Matheus Castanho/mscasta...@ibm.com 
 
---uname output---
N/A
 
Machine Type = N/A 
 
---Debugger---
A debugger is not configured
 
---Steps to Reproduce---
 git clone git://sourceware.org/git/glibc.git
mkdir build && cd build
../glibc/configure --prefix=/usr && make -j8 && make check
 
Userspace tool common name: binutils 
 
The userspace tool has the following bit modes: 64-bit 

Userspace rpm: binutils

Userspace tool obtained from project website:  na 
 
*Additional Instructions for Matheus Castanho/mscasta...@ibm.com:
-Attach ltrace and strace of userspace application.

** Affects: ubuntu-power-systems
 Importance: Medium
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
 Status: New

** Affects: binutils (Ubuntu)
 Importance: Medium
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
 Status: New


** Tags: architecture-ppc64le bugnameltc-198498 severity-medium 
targetmilestone-inin20041
-- 
Incomplete support for DT_RELR relocations on Ubuntu 22.04
https://bugs.launchpad.net/bugs/1978129
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to binutils 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 1947099] Re: ipconfig does not honour user-requested timeouts in some cases

2022-06-09 Thread Launchpad Bug Tracker
This bug was fixed in the package klibc - 2.0.4-9ubuntu2.2

---
klibc (2.0.4-9ubuntu2.2) bionic; urgency=medium

  [ Khaled Elmously ]
  * d/p/lp1947099-honour-user-requested-timeouts-in-all-cases.patch:
Honour user-specified timeouts even in error cases. (LP: #1947099)

  [ Mauricio Faria de Oliveira ]
  * d/p/lp1947099-fix-for-no-timeout-specified.patch: Check for an
user-specified timeout before checking/adjusting timeout values.

 -- Mauricio Faria de Oliveira   Mon, 25 Apr 2022
11:39:01 -0300

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

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

Title:
  ipconfig does not honour user-requested timeouts in some cases

Status in klibc package in Ubuntu:
  Won't Fix
Status in klibc source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  In some cases, ipconfig can take a longer time than the user-specified 
timeouts, causing unexpected delays.

  [Test Plan]

  - Check that the ipconfig utility is able to obtain an IP through
  dhcp:

  # ip l set dev ens9 down
  # date; /usr/lib/klibc/bin/ipconfig ens9; date

  - Check if it respects the timeout (i.e. 2 seconds in the example
  below):

  # ip l set dev ens9 down
  # date; /usr/lib/klibc/bin/ipconfig -t 2 ens9; date

  - The original issue is that timeout is being ignored when not
  receiving any reply from a DHCP Server, so for this test you have to
  stop your DHCP Server (i.e. dnsmasq) and then test the timeouts:

  # ip l set dev ens9 down
  # date; /usr/lib/klibc/bin/ipconfig -t 2 ens9; date

  # ip l set dev ens9 down
  # date; /usr/lib/klibc/bin/ipconfig -t 5 ens9; date

  Make sure it times out respectivelly in 2 and 5 seconds.

  [racb: pending agreement with the SRU team; please see comment 37]

  Any situation where ipconfig encounters an error sending the DHCP
  packet, it will automatically set a delay of 10 seconds, which could
  be longer than the user-specified timeout. It can be reproduced by
  creating a dummy interface and attempting to run ipconfig on it with a
  timeout value of less than 10:

  # ip link add eth1 type dummy
  # date; /usr/lib/klibc/bin/ipconfig -t 2 eth1; date
  Thu Nov 18 04:46:13 EST 2021
  IP-Config: eth1 hardware address ae:e0:f5:9d:7e:00 mtu 1500 DHCP RARP
  IP-Config: no response after 2 secs - giving up
  Thu Nov 18 04:46:23 EST 2021

  ^ Notice above, ipconfig thinks that it waited 2 seconds, but the
  timestamps show an actual delay of 10 seconds.

  [Where problems could occur]
  Please see reproduction steps above. We are seeing this in production too 
(see comment #2).

  [Other Info]
  A patch to fix the issue is being proposed here. It is a safe fix - it only 
checks before going into sleep that the timeout never exceeds the 
user-requested value.

  [Original Description]

  In some cases, ipconfig can take longer than the user-specified
  timeouts, causing unexpected delays.

  in main.c, in function loop(), the process can go into
  process_timeout_event() (or process_receive_event() ) and if it
  encounters an error situation, will set an attempt to "try again
  later" at time equal now + 10 seconds by setting

  s->expire = now + 10;

  This can happen at any time during the main event loop, which can end
  up extending the user-specified timeout if "now + 10" is greater than
  "start_time + user-specified-timeout".

  I believe a patch like the following is needed to avoid this problem:

  --- a/usr/kinit/ipconfig/main.c
  +++ b/usr/kinit/ipconfig/main.c
  @@ -437,6 +437,13 @@ static int loop(void)

  if (timeout > s->expire - now.tv_sec)
  timeout = s->expire - now.tv_sec;
  +
  +   /* Compensate for already-lost time */
  +   gettimeofday(, NULL);
  +   if (now.tv_sec + timeout > start + loop_timeout) {
  +   timeout = loop_timeout - (now.tv_sec - start);
  +   printf("Lowered timeout to match user request 
= (%d s) \n", timeout);
  +   }
  }

  I believe the current behaviour is buggy. This is confirmed when the
  following line is executed:

  if (loop_timeout >= 0 &&
  now.tv_sec - start >= loop_timeout) {
  printf("IP-Config: no response after %d "
     "secs - giving up\n", loop_timeout);
  rc = -1;
  goto bail;
  }

  'loop_timeout' is the user-specified time-out. With a value of 2, in
  case of error, this line prints:

  IP-Config: no response after 2 secs - giving up

  So it thinks that it waited 2 seconds - however, in reality it had
 

[Touch-packages] [Bug 1977748] [NEW] No cairo GL support for wayland, 22.04

2022-06-08 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Instructed by "ask a question" I tried to file a wayland-targeted bug,
but apport-bug thinks I'm running Xorg.  See
https://answers.launchpad.net/ubuntu/+question/702075

PRETTY_NAME="Ubuntu 22.04 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy

$ ps -ef | grep Xwayland
xx  24931685  0 Jun04 ?00:05:36 /usr/bin/Xwayland :0 
-rootless -noreset -accessx -core -auth 
/run/user/1001/.mutter-Xwaylandauth.5ZZYM1 -listen 4 -listen 5 -displayfd 6 
-initfd 7

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35
Uname: Linux 5.15.0-35-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Jun  6 06:40:48 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
   Subsystem: Dell TigerLake-LP GT2 [Iris Xe Graphics] [1028:0991]
InstallationDate: Installed on 2021-10-02 (246 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
MachineType: Dell Inc. XPS 13 9310
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-35-generic 
root=UUID=c737013a-1cc7-494f-a1b7-a6efce6f09f7 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/17/2022
dmi.bios.release: 3.6
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 3.6.0
dmi.board.name: 0MK6WC
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr3.6.0:bd03/17/2022:br3.6:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0MK6WC:rvrA00:cvnDellInc.:ct10:cvr:sku0991:
dmi.product.family: XPS
dmi.product.name: XPS 13 9310
dmi.product.sku: 0991
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug jammy ubuntu wayland-session
-- 
No cairo GL support for wayland, 22.04
https://bugs.launchpad.net/bugs/1977748
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to cairo 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 1971305] Re: Merge openldap from Debian unstable for kinetic

2022-06-08 Thread Launchpad Bug Tracker
This bug was fixed in the package openldap - 2.5.12+dfsg-2ubuntu1

---
openldap (2.5.12+dfsg-2ubuntu1) kinetic; urgency=medium

  * Merge with Debian unstable (LP: #1971305). Remaining changes:
- Enable AppArmor support:
  + d/apparmor-profile: add AppArmor profile
  + d/rules: use dh_apparmor
  + d/control: Build-Depends on dh-apparmor
  + d/slapd.README.Debian: add note about AppArmor
- Enable ufw support:
  + d/control: suggest ufw.
  + d/rules: install ufw profile.
  + d/slapd.ufw.profile: add ufw profile.
- d/{rules,slapd.py}: Add apport hook.
- d/rules: better regexp to match the Maintainer tag in d/control,
  needed in the Ubuntu case because of XSBC-Original-Maintainer
  (Closes #960448, LP #1875697)

 -- Sergio Durigan Junior   Mon, 06 Jun
2022 15:34:48 -0400

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

Title:
  Merge openldap from Debian unstable for kinetic

Status in openldap package in Ubuntu:
  Fix Released

Bug description:
  Upstream: tbd
  Debian:   2.5.11+dfsg-1
  Ubuntu:   2.5.11+dfsg-1~exp1ubuntu3


  Debian does new releases regularly, so it's likely there will be newer
  versions available before FF that we can pick up if this merge is done
  later in the cycle.

  
  ### New Debian Changes ###

  openldap (2.5.11+dfsg-1) unstable; urgency=medium

* Upload to unstable.

   -- Ryan Tandy   Fri, 11 Mar 2022 19:38:02 -0800

  openldap (2.5.11+dfsg-1~exp1) experimental; urgency=medium

* New upstream release.
* Add openssl to Build-Depends to enable more checks in test067-tls.
* Update slapd-contrib's custom-library-search-path override to work with
  current Lintian.

   -- Ryan Tandy   Sun, 23 Jan 2022 17:16:05 -0800

  openldap (2.5.8+dfsg-1~exp1) experimental; urgency=medium

* New upstream release.
* Update slapd-contrib's custom-library-search-path override to work with
  Lintian 2.108.0.

   -- Ryan Tandy   Wed, 13 Oct 2021 18:42:55 -0700

  openldap (2.5.7+dfsg-1~exp1) experimental; urgency=medium

* New upstream release.
* Don't run autoreconf in contrib/ldapc++. We don't build it, and it is not
  yet compatible with autoconf 2.71. (Closes: #993032)
* Stop disabling automake in debian/rules now that upstream removed the
  AM_INIT_AUTOMAKE invocation.
* Drop custom config.{guess,sub} handling. dh_update_autotools_config does
  the right thing for us.
* Update Standards-Version to 4.6.0; no changes required.
* debian/not-installed: Add the ldapvc.1 man page.

   -- Ryan Tandy   Mon, 30 Aug 2021 18:54:25 -0700

  openldap (2.5.6+dfsg-1~exp1) experimental; urgency=medium

[ Ryan Tandy ]
* New upstream release.
* Export the cn=config database to LDIF format before upgrading from 2.4.
* slapd.README.Debian:
  - Remove text about the dropped evolution-ntlm patch.
  - Add guidance for recovering from upgrade failures.
* Remove the debconf warning and README text about the unsafe ACL configured
  by default in versions before jessie.
* Remove upgrade code for adding the pwdMaxRecordedFailure attribute to the
  ppolicy schema. It's obsolete since the schema has been internalized.

[ Sergio Durigan Junior ]
* Implement the 'escape hatch' mechanism.
  - d/po/*.po: Update PO files given the new template note.
  - d/po/templates.pot: Update file.
  - d/slapd.templates: Add note warning user about a postinst failure,
its possible cause and what to do.
  - d/slapd.postinst: Make certain upgrade functions return failure
instead of exiting, which allows the postinst script to gracefully
fail when applicable.  Also, when the general configuration upgrade
fails, display a critical warning to the user.  Implement
ignore_init_failure function.
  - d/slapd.prerm: Implement ignore_init_failure function.
  - d/slapd.scripts-common: Make certain functions return failure
instead of exiting.
  - d/rules: Use dh_installinit's --error-handler to instruct it on how
to handle possible errors with the init script.
  - d/slapd.NEWS: Add excerpt mentioning that the postinst script might
error out if it can't migrate the existing (old) database backend.

   -- Ryan Tandy   Mon, 16 Aug 2021 18:32:29 -0700

  openldap (2.5.5+dfsg-1~exp1) experimental; urgency=medium

* New upstream release.
  - Drop patches applied upstream: ITS#9544, ITS#9548.
* Mark slapd-contrib as breaking the old version of slapd to reduce the
  chance of upgrade failure due to slapd-contrib being unpacked first.

   -- Ryan Tandy   Fri, 11 Jun 2021 11:43:15 -0700

  openldap (2.5.4+dfsg-1~exp1) experimental; urgency=medium

* New upstream 

[Touch-packages] [Bug 1976313] Re: GPG Key Expired

2022-06-08 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: ubuntu-keyring (Ubuntu)
   Status: New => Confirmed

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

Title:
  GPG Key Expired

Status in ubuntu-keyring package in Ubuntu:
  Confirmed

Bug description:
  I get the following error when trying to run `sudo apt update`:

  W: An error occurred during the signature verification. The repository is not 
updated and the previous index files will be used. GPG error: 
http://ddebs.ubuntu.com focal-updates Release: The following signatures were 
invalid: BADSIG C8CAB6595FDFF622 Ubuntu Debug Symbol Archive Automatic Signing 
Key (2016) 
  W: Failed to fetch http://ddebs.ubuntu.com/dists/focal-updates/Release.gpg  
The following signatures were invalid: BADSIG C8CAB6595FDFF622 Ubuntu Debug 
Symbol Archive Automatic Signing Key (2016) 
  W: Some index files failed to download. They have been ignored, or old ones 
used instead.

  I'm using Ubuntu 20.04.4 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-dbgsym-keyring 2020.02.11.4
  ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.24
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: LXQt
  Date: Tue May 31 00:32:43 2022
  Dependencies:
   
  InstallationDate: Installed on 2020-05-11 (749 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: ubuntu-keyring
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-keyring/+bug/1976313/+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 1565498] Re: package libcurl4-gnutls-dev (not installed) failed to install/upgrade: trying to overwrite shared '/usr/bin/curl-config', which is different from other instances of

2022-06-08 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  package libcurl4-gnutls-dev (not installed) failed to install/upgrade:
  trying to overwrite shared '/usr/bin/curl-config', which is different
  from other instances of package libcurl4-gnutls-dev:amd64

Status in curl package in Ubuntu:
  Confirmed

Bug description:
  Just updated and installed a dependency yesterday

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libcurl4-gnutls-dev (not installed)
  Uname: Linux 4.5.0-040500-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu1
  AptOrdering:
   libcurl4-gnutls-dev: Install
   libcurl4-gnutls-dev: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat Apr  2 03:08:53 2016
  DpkgTerminalLog:
   Preparing to unpack .../libcurl4-gnutls-dev_7.47.0-1ubuntu2_amd64.deb ...
   Unpacking libcurl4-gnutls-dev:amd64 (7.47.0-1ubuntu2) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libcurl4-gnutls-dev_7.47.0-1ubuntu2_amd64.deb 
(--unpack):
trying to overwrite shared '/usr/bin/curl-config', which is different from 
other instances of package libcurl4-gnutls-dev:amd64
  DuplicateSignature:
   Unpacking libcurl4-gnutls-dev:amd64 (7.47.0-1ubuntu2) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libcurl4-gnutls-dev_7.47.0-1ubuntu2_amd64.deb 
(--unpack):
trying to overwrite shared '/usr/bin/curl-config', which is different from 
other instances of package libcurl4-gnutls-dev:amd64
  ErrorMessage: trying to overwrite shared '/usr/bin/curl-config', which is 
different from other instances of package libcurl4-gnutls-dev:amd64
  InstallationDate: Installed on 2016-03-12 (21 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.9
  SourcePackage: curl
  Title: package libcurl4-gnutls-dev (not installed) failed to install/upgrade: 
trying to overwrite shared '/usr/bin/curl-config', which is different from 
other instances of package libcurl4-gnutls-dev:amd64
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1565498/+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 1736986] Re: package libcurl4-openssl-dev 7.47.0-1ubuntu2.5 failed to install/upgrade: trying to overwrite shared '/usr/bin/curl-config', which is different from other instances

2022-06-08 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  package libcurl4-openssl-dev 7.47.0-1ubuntu2.5 failed to
  install/upgrade: trying to overwrite shared '/usr/bin/curl-config',
  which is different from other instances of package libcurl4-openssl-
  dev:armhf

Status in curl package in Ubuntu:
  Confirmed

Bug description:
  This came up while trying to install libcurl for armhf. System (amd64)
  is configured for cross-compiling on armhf; other packages were
  installed correctly.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libcurl4-openssl-dev 7.47.0-1ubuntu2.5
  ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95
  Uname: Linux 4.4.0-101-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  Date: Thu Dec  7 17:10:49 2017
  DuplicateSignature:
   package:libcurl4-openssl-dev:7.47.0-1ubuntu2.5
   Unpacking libcurl4-openssl-dev:armhf (7.47.0-1ubuntu2.5) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libcurl4-openssl-dev_7.47.0-1ubuntu2.5_armhf.deb 
(--unpack):
trying to overwrite shared '/usr/bin/curl-config', which is different from 
other instances of package libcurl4-openssl-dev:armhf
  ErrorMessage: trying to overwrite shared '/usr/bin/curl-config', which is 
different from other instances of package libcurl4-openssl-dev:armhf
  InstallationDate: Installed on 2015-04-23 (959 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: curl
  Title: package libcurl4-openssl-dev 7.47.0-1ubuntu2.5 failed to 
install/upgrade: trying to overwrite shared '/usr/bin/curl-config', which is 
different from other instances of package libcurl4-openssl-dev:armhf
  UpgradeStatus: Upgraded to xenial on 2017-11-29 (8 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1736986/+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 1976631] Re: Update to 20211016 bundle

2022-06-08 Thread Launchpad Bug Tracker
This bug was fixed in the package ca-certificates - 20211016~21.10.1

---
ca-certificates (20211016~21.10.1) impish-security; urgency=medium

  * Update ca-certificates database to 20211016 (LP: #1976631):
- mozilla/{certdata.txt,nssckbi.h}: Update Mozilla certificate
  authority bundle to version 2.50.
- backport certain changes from the Ubuntu 22.04 LTS 20211016 package.

 -- Marc Deslauriers   Thu, 02 Jun 2022
10:19:50 -0400

** Changed in: ca-certificates (Ubuntu Impish)
   Status: In Progress => Fix Released

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

Title:
  Update to 20211016 bundle

Status in ca-certificates package in Ubuntu:
  Fix Released
Status in ca-certificates source package in Bionic:
  Fix Released
Status in ca-certificates source package in Focal:
  Fix Released
Status in ca-certificates source package in Impish:
  Fix Released
Status in ca-certificates source package in Jammy:
  Fix Released
Status in ca-certificates source package in Kinetic:
  Fix Released

Bug description:
  This is a tracking bug to update the ca-certificates database to 2.50

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1976631/+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 1976631] Re: Update to 20211016 bundle

2022-06-08 Thread Launchpad Bug Tracker
This bug was fixed in the package ca-certificates - 20211016~18.04.1

---
ca-certificates (20211016~18.04.1) bionic-security; urgency=medium

  * Update ca-certificates database to 20211016 (LP: #1976631):
- mozilla/{certdata.txt,nssckbi.h}: Update Mozilla certificate
  authority bundle to version 2.50.
- backport certain changes from the Ubuntu 22.04 LTS 20211016 package.

 -- Marc Deslauriers   Thu, 02 Jun 2022
10:19:50 -0400

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

Title:
  Update to 20211016 bundle

Status in ca-certificates package in Ubuntu:
  Fix Released
Status in ca-certificates source package in Bionic:
  Fix Released
Status in ca-certificates source package in Focal:
  Fix Released
Status in ca-certificates source package in Impish:
  Fix Released
Status in ca-certificates source package in Jammy:
  Fix Released
Status in ca-certificates source package in Kinetic:
  Fix Released

Bug description:
  This is a tracking bug to update the ca-certificates database to 2.50

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1976631/+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 1976631] Re: Update to 20211016 bundle

2022-06-08 Thread Launchpad Bug Tracker
This bug was fixed in the package ca-certificates - 20211016~20.04.1

---
ca-certificates (20211016~20.04.1) focal-security; urgency=medium

  * Update ca-certificates database to 20211016 (LP: #1976631):
- mozilla/{certdata.txt,nssckbi.h}: Update Mozilla certificate
  authority bundle to version 2.50.
- backport certain changes from the Ubuntu 22.04 LTS 20211016 package.

 -- Marc Deslauriers   Thu, 02 Jun 2022
10:19:50 -0400

** Changed in: ca-certificates (Ubuntu Focal)
   Status: In Progress => Fix Released

** Changed in: ca-certificates (Ubuntu Bionic)
   Status: In Progress => Fix Released

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

Title:
  Update to 20211016 bundle

Status in ca-certificates package in Ubuntu:
  Fix Released
Status in ca-certificates source package in Bionic:
  Fix Released
Status in ca-certificates source package in Focal:
  Fix Released
Status in ca-certificates source package in Impish:
  Fix Released
Status in ca-certificates source package in Jammy:
  Fix Released
Status in ca-certificates source package in Kinetic:
  Fix Released

Bug description:
  This is a tracking bug to update the ca-certificates database to 2.50

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1976631/+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 1977652] Re: systemd loops trying to start systemd-ask-password-plymouth

2022-06-07 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  systemd loops trying to start systemd-ask-password-plymouth

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Short story:
  - after boot
  - when a systemd service wants a password
  - systemd-ask-password is invoked
  - systemd-ask-password-plymouth.path is reached
  - systemd-ask-password-plymouth.service is started

  Except:
  - the conditions for the latter are (apparently) not met

  End result:
  - 40.000x "Condition check resulted in Forward Password Requests to Plymouth 
being skipped."
  - 1.5 minutes of 100% cpu usage

  
  AFFECTED VERSION
  

  systemd 249.11-0ubuntu3.1 on Ubuntu/Jammy 22.04

  
  HOW TO REPRODUCE
  

  If I leave the `systemd-ask-password-plymouth.path` unmasked/enabled
  and reboot. OpenVPN (calling systemd-ask-password) will trigger the
  condition.

  This causes high CPU usage for 1.5 minutes.

  It looks like /run/plymouth/pid exists (for the .path file) at first,
  when that is invoked, but then the resultant target (the .service
  file) checks again, and finds that it is gone.

  Manually reproducing:

  # ls /run/systemd/ask-password
  ask.5hW6rb  sck.79cfe1203518610

  # mkdir /run/plymouth/pid
  # systemctl start systemd-ask-password-plymouth.service 
systemd-ask-password-plymouth.path

  # systemctl show --value --property=MainPID 
systemd-ask-password-plymouth.service
  24777

  # rmdir /run/plymouth/pid ; kill 24777

  Result: systemd going into a loop.

  Stop the loop with:

  # systemctl stop systemd-ask-password-plymouth.path

  
  
  ANALYSIS
  

  It looks like this:
  https://github.com/systemd/systemd/issues/21025

  which is fixed by:
  https://github.com/systemd/systemd/pull/21030

  Alternative bug reports:
  https://bugzilla.redhat.com/show_bug.cgi?id=1919538

  Systemd's own analysis of the situation:

  # systemd-analyze critical-chain systemd-ask-password-plymouth.service
  ...
  systemd-ask-password-plymouth.service @1min 35.823s
  └─systemd-ask-password-plymouth.path @593ms
└─plymouth-start.service @571ms +21ms
  └─systemd-udevd.service @450ms +119ms
└─systemd-tmpfiles-setup-dev.service @429ms +18ms
  └─systemd-sysusers.service @382ms +46ms
└─systemd-remount-fs.service @353ms +22ms
  └─systemd-journald.socket @318ms
└─system.slice @264ms
  └─-.slice @264ms

  ---
  WORKAROUNDS
  ---

  This works as long as you don't need the plymouth-ask-password:

  # systemctl disable systemd-ask-password-plymouth.path
  # systemctl mask systemd-ask-password-plymouth.path


  Could you get the relevant patches from upstream sorted in Jammy?

  Thanks!

  Walter Doekes
  OSSO B.V.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1977652/+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 1977748] [NEW] apport-bug thinks it's running on Xorg

2022-06-06 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Instructed by "ask a question" I tried to file a wayland-targeted bug,
but apport-bug thinks I'm running Xorg.  See
https://answers.launchpad.net/ubuntu/+question/702075

PRETTY_NAME="Ubuntu 22.04 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy

$ ps -ef | grep Xwayland
xx  24931685  0 Jun04 ?00:05:36 /usr/bin/Xwayland :0 
-rootless -noreset -accessx -core -auth 
/run/user/1001/.mutter-Xwaylandauth.5ZZYM1 -listen 4 -listen 5 -displayfd 6 
-initfd 7

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35
Uname: Linux 5.15.0-35-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Jun  6 06:40:48 2022
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation TigerLake-LP GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
   Subsystem: Dell TigerLake-LP GT2 [Iris Xe Graphics] [1028:0991]
InstallationDate: Installed on 2021-10-02 (246 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
MachineType: Dell Inc. XPS 13 9310
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-35-generic 
root=UUID=c737013a-1cc7-494f-a1b7-a6efce6f09f7 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/17/2022
dmi.bios.release: 3.6
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 3.6.0
dmi.board.name: 0MK6WC
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr3.6.0:bd03/17/2022:br3.6:svnDellInc.:pnXPS139310:pvr:rvnDellInc.:rn0MK6WC:rvrA00:cvnDellInc.:ct10:cvr:sku0991:
dmi.product.family: XPS
dmi.product.name: XPS 13 9310
dmi.product.sku: 0991
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.110-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug jammy ubuntu wayland-session
-- 
apport-bug thinks it's running on Xorg
https://bugs.launchpad.net/bugs/1977748
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg 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 1959993] Re: SRU of LXC 4.0.12 to focal (upstream bugfix release)

2022-06-06 Thread Launchpad Bug Tracker
This bug was fixed in the package lxc - 1:4.0.12-0ubuntu1~20.04.1

---
lxc (1:4.0.12-0ubuntu1~20.04.1) focal; urgency=medium

  * Cherry-pick upstream bugfixes (stable-4.0):
- 0002-lxc-checkconfig-Fix-bashism.patch
- 0003-doc-Fix-reverse-allowlist-denylist.patch

  * New upstream bugfix release (4.0.12) (LP: #1959993):
(https://discuss.linuxcontainers.org/t/lxc-4-0-12-has-been-released/13288)
- Fixed CRIU restoration of containers with pre-created veth interfaces
- Fixed issue with kernels lacking SMT support
- Extended cgroup2 config options in lxc.mount.auto (cgroup2)
- lxc-download now relies on HTTPS for validation (avoids GPG issues)

  * New upstream bugfix release (4.0.11):
(https://discuss.linuxcontainers.org/t/lxc-4-0-11-has-been-released/12427)
- Core scheduling support (lxc.sched.core)
- riscv64 support in lxc.arch
- Significantly improved bash completion profile
- Greater use of the new VFS mount API (when supported by the kernel)
- Fix containers with empty network namespaces
- Handle kernels that lack TIOCGPTPEER
- Improve CPU bitmask/id handling (handle skipped CPU numbers)
- Reworked the tests to run offline

  * New upstream bugfix release (4.0.10):
(https://discuss.linuxcontainers.org/t/lxc-4-0-10-has-been-released/11618)
- Fix issues with less common architectures
- Support for additional idmap mounts
- nft support in lxc-net
- Cleaner mount entries for sys:mixed
- Switched GPG server to keyserver.ubuntu.com

  * New upstream bugfix release (4.0.9):
(https://discuss.linuxcontainers.org/t/lxc-4-0-9-has-been-released/10999)
- Fix incorrect personality setting when running 32bit containers on 64bit

  * New upstream bugfix release (4.0.8):
- Fix CGroup attach against older running containers

  * New upstream bugfix release (4.0.7):
- Testing improvements including fixes from oss-fuzz
- Rework of the attach codepath
- Cgroup handling rework

  * Bump to debhelper 12 (allows focal SRUs)
  * Bump standards to 4.6.0.1
  * Add lintian overrides for incorrect bashism detection
  * Remove bash completion install logic (now done upstream)

 -- Stéphane Graber   Thu, 03 Feb 2022 23:50:20
-0500

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

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

Title:
  SRU of LXC 4.0.12 to focal (upstream bugfix release)

Status in lxc package in Ubuntu:
  In Progress
Status in lxc source package in Focal:
  Fix Released
Status in lxc source package in Impish:
  Fix Released

Bug description:
  LXC released 4.0.12 as a bugfix release and is now in jammy. We'd like
  to line things up in focal.

  [Impact]
  The proposed SRU will bump from 4.0.6 all the way to 4.0.12, lining it up 
with what's currently in jammy. We've been skipping a few of the bugfix 
releases in focal so far, mostly catching up when we're starting to see 
problems with the older version.

  In this case, we've seen a number of issues when running with the HWE
  kernels as well as autopkgtest issues on foreign architectures (arm64
  and s390x), all those will go away with this bump as we've confirmed
  everything is clean in jammy.

  Changelog:

    * Cherry-pick upstream bugfixes (stable-4.0):
  - 0002-lxc-checkconfig-Fix-bashism.patch
  - 0003-doc-Fix-reverse-allowlist-denylist.patch

    * New upstream bugfix release (4.0.12):
  (https://discuss.linuxcontainers.org/t/lxc-4-0-12-has-been-released/13288)
  - Fixed CRIU restoration of containers with pre-created veth interfaces
  - Fixed issue with kernels lacking SMT support
  - Extended cgroup2 config options in lxc.mount.auto (cgroup2)
  - lxc-download now relies on HTTPS for validation (avoids GPG issues)

    * New upstream bugfix release (4.0.11):
  (https://discuss.linuxcontainers.org/t/lxc-4-0-11-has-been-released/12427)
  - Core scheduling support (lxc.sched.core)
  - riscv64 support in lxc.arch
  - Significantly improved bash completion profile
  - Greater use of the new VFS mount API (when supported by the kernel)
  - Fix containers with empty network namespaces
  - Handle kernels that lack TIOCGPTPEER
  - Improve CPU bitmask/id handling (handle skipped CPU numbers)
  - Reworked the tests to run offline

    * New upstream bugfix release (4.0.10):
  (https://discuss.linuxcontainers.org/t/lxc-4-0-10-has-been-released/11618)
  - Fix issues with less common architectures
  - Support for additional idmap mounts
  - nft support in lxc-net
  - Cleaner mount entries for sys:mixed
  - Switched GPG server to keyserver.ubuntu.com

    * New upstream bugfix release (4.0.9):
  (https://discuss.linuxcontainers.org/t/lxc-4-0-9-has-been-released/10999)
  - Fix incorrect personality 

[Touch-packages] [Bug 1962453] Re: Apply default TTL to records obtained from getaddrinfo()

2022-06-06 Thread Launchpad Bug Tracker
This bug was fixed in the package keyutils - 1.6-6ubuntu1.1

---
keyutils (1.6-6ubuntu1.1) focal; urgency=medium

  * d/p/apply-default-ttl-to-records.patch: Add patch
to apply default TTL to records obtained from
getaddrinfo(). (LP: #1962453)

 -- Utkarsh Gupta   Fri, 27 May 2022 14:33:22 +0530

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

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

Title:
  Apply default TTL to records obtained from getaddrinfo()

Status in keyutils package in Ubuntu:
  Fix Released
Status in keyutils source package in Bionic:
  Fix Released
Status in keyutils source package in Focal:
  Fix Released
Status in keyutils source package in Impish:
  Fix Released
Status in keyutils source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  

  There's a strong dependency for cifs.ko (and nfs.ko) on keyutils for
  DNS resolution. The keyutils package contains the userspace utility to
  update the kernel keyring with the DNS mapping to IP address. Prior to
  1.6.2, this utility may erroneously set unlimited lifetime for this
  keyring in the kernel.

  [Test plan]
  ===

  1. Create a file share on an SMB server (can be a samba server) with
  two IP addresses. Make sure that FQDN of the server resolves to one of
  these addresses.

  2. mount the created share on the cifs client using the FQDN for the
  server. Make sure that the mount point is accessible.

  3. Using the ss command on the client, to kill the sockets that
  connect to the server: sudo ss -K dport :445

  4. Now update the DNS entry to make sure that the server FQDN now
  resolves to the second IP address of the server. Make sure that
  nslookup on the client now resolves to the new IP address.

  5. Repeat step 3 to kill the sockets that connect to server to force
  re-connection again.

  Without the fix, after step 5, with the "ss -t" command, you'll see
  that the client has reconnected to the old IP address, even when DNS
  lookups return the new IP.

  With the fix (after a reboot of the client machine to make sure that
  kernel keys are refreshed), you'll see that the client reconnects to
  the new IP address.

  The bug is due to unlimited lifetime set by key.dns_resolver (which is
  part of keyutils package). As a result, even if IP address for the DNS
  entries change, the kernel filesystems would continue to use old IP
  address, due to the cached keys. This issue causes clients to
  misbehave when Azure Files service endpoints move to a different
  cluster.

  [Where problems could occur]
  

  Address records obtained from getaddrinfo() don't come with any TTL
  information, even if they're obtained from the DNS, so if someone is
  relying on this particularly, might face some problem/regression but I
  don't think they would face that as it would still be highly
  configurable.

  [Other information]
  ===

  This request is essentially from one of our cloud partners and they're
  highly affected by this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/keyutils/+bug/1962453/+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 1959993] Re: SRU of LXC 4.0.12 to focal (upstream bugfix release)

2022-06-06 Thread Launchpad Bug Tracker
This bug was fixed in the package lxc - 1:4.0.12-0ubuntu1~21.10.1

---
lxc (1:4.0.12-0ubuntu1~21.10.1) impish; urgency=medium

  * Cherry-pick upstream bugfixes (stable-4.0):
- 0002-lxc-checkconfig-Fix-bashism.patch
- 0003-doc-Fix-reverse-allowlist-denylist.patch

  * New upstream bugfix release (4.0.12) (LP: #1959993):
(https://discuss.linuxcontainers.org/t/lxc-4-0-12-has-been-released/13288)
- Fixed CRIU restoration of containers with pre-created veth interfaces
- Fixed issue with kernels lacking SMT support
- Extended cgroup2 config options in lxc.mount.auto (cgroup2)
- lxc-download now relies on HTTPS for validation (avoids GPG issues)

  * New upstream bugfix release (4.0.11):
(https://discuss.linuxcontainers.org/t/lxc-4-0-11-has-been-released/12427)
- Core scheduling support (lxc.sched.core)
- riscv64 support in lxc.arch
- Significantly improved bash completion profile
- Greater use of the new VFS mount API (when supported by the kernel)
- Fix containers with empty network namespaces
- Handle kernels that lack TIOCGPTPEER
- Improve CPU bitmask/id handling (handle skipped CPU numbers)
- Reworked the tests to run offline

  * New upstream bugfix release (4.0.10):
(https://discuss.linuxcontainers.org/t/lxc-4-0-10-has-been-released/11618)
- Fix issues with less common architectures
- Support for additional idmap mounts
- nft support in lxc-net
- Cleaner mount entries for sys:mixed
- Switched GPG server to keyserver.ubuntu.com

  * New upstream bugfix release (4.0.9):
(https://discuss.linuxcontainers.org/t/lxc-4-0-9-has-been-released/10999)
- Fix incorrect personality setting when running 32bit containers on 64bit

  * New upstream bugfix release (4.0.8):
- Fix CGroup attach against older running containers

  * New upstream bugfix release (4.0.7):
- Testing improvements including fixes from oss-fuzz
- Rework of the attach codepath
- Cgroup handling rework

  * Bump to debhelper 12 (allows focal SRUs)
  * Bump standards to 4.6.0.1
  * Add lintian overrides for incorrect bashism detection
  * Remove bash completion install logic (now done upstream)

 -- Stéphane Graber   Thu, 03 Feb 2022 23:50:20
-0500

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

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

Title:
  SRU of LXC 4.0.12 to focal (upstream bugfix release)

Status in lxc package in Ubuntu:
  In Progress
Status in lxc source package in Focal:
  Fix Committed
Status in lxc source package in Impish:
  Fix Released

Bug description:
  LXC released 4.0.12 as a bugfix release and is now in jammy. We'd like
  to line things up in focal.

  [Impact]
  The proposed SRU will bump from 4.0.6 all the way to 4.0.12, lining it up 
with what's currently in jammy. We've been skipping a few of the bugfix 
releases in focal so far, mostly catching up when we're starting to see 
problems with the older version.

  In this case, we've seen a number of issues when running with the HWE
  kernels as well as autopkgtest issues on foreign architectures (arm64
  and s390x), all those will go away with this bump as we've confirmed
  everything is clean in jammy.

  Changelog:

    * Cherry-pick upstream bugfixes (stable-4.0):
  - 0002-lxc-checkconfig-Fix-bashism.patch
  - 0003-doc-Fix-reverse-allowlist-denylist.patch

    * New upstream bugfix release (4.0.12):
  (https://discuss.linuxcontainers.org/t/lxc-4-0-12-has-been-released/13288)
  - Fixed CRIU restoration of containers with pre-created veth interfaces
  - Fixed issue with kernels lacking SMT support
  - Extended cgroup2 config options in lxc.mount.auto (cgroup2)
  - lxc-download now relies on HTTPS for validation (avoids GPG issues)

    * New upstream bugfix release (4.0.11):
  (https://discuss.linuxcontainers.org/t/lxc-4-0-11-has-been-released/12427)
  - Core scheduling support (lxc.sched.core)
  - riscv64 support in lxc.arch
  - Significantly improved bash completion profile
  - Greater use of the new VFS mount API (when supported by the kernel)
  - Fix containers with empty network namespaces
  - Handle kernels that lack TIOCGPTPEER
  - Improve CPU bitmask/id handling (handle skipped CPU numbers)
  - Reworked the tests to run offline

    * New upstream bugfix release (4.0.10):
  (https://discuss.linuxcontainers.org/t/lxc-4-0-10-has-been-released/11618)
  - Fix issues with less common architectures
  - Support for additional idmap mounts
  - nft support in lxc-net
  - Cleaner mount entries for sys:mixed
  - Switched GPG server to keyserver.ubuntu.com

    * New upstream bugfix release (4.0.9):
  (https://discuss.linuxcontainers.org/t/lxc-4-0-9-has-been-released/10999)
  - Fix incorrect 

[Touch-packages] [Bug 1962453] Re: Apply default TTL to records obtained from getaddrinfo()

2022-06-06 Thread Launchpad Bug Tracker
This bug was fixed in the package keyutils - 1.6.1-2ubuntu2.1

---
keyutils (1.6.1-2ubuntu2.1) impish; urgency=medium

  * d/p/apply-default-ttl-to-records.patch: Add patch
to apply default TTL to records obtained from
getaddrinfo(). (LP: #1962453)

 -- Utkarsh Gupta   Fri, 27 May 2022 14:54:36 +0530

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

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

Title:
  Apply default TTL to records obtained from getaddrinfo()

Status in keyutils package in Ubuntu:
  Fix Released
Status in keyutils source package in Bionic:
  Fix Released
Status in keyutils source package in Focal:
  Fix Committed
Status in keyutils source package in Impish:
  Fix Released
Status in keyutils source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  

  There's a strong dependency for cifs.ko (and nfs.ko) on keyutils for
  DNS resolution. The keyutils package contains the userspace utility to
  update the kernel keyring with the DNS mapping to IP address. Prior to
  1.6.2, this utility may erroneously set unlimited lifetime for this
  keyring in the kernel.

  [Test plan]
  ===

  1. Create a file share on an SMB server (can be a samba server) with
  two IP addresses. Make sure that FQDN of the server resolves to one of
  these addresses.

  2. mount the created share on the cifs client using the FQDN for the
  server. Make sure that the mount point is accessible.

  3. Using the ss command on the client, to kill the sockets that
  connect to the server: sudo ss -K dport :445

  4. Now update the DNS entry to make sure that the server FQDN now
  resolves to the second IP address of the server. Make sure that
  nslookup on the client now resolves to the new IP address.

  5. Repeat step 3 to kill the sockets that connect to server to force
  re-connection again.

  Without the fix, after step 5, with the "ss -t" command, you'll see
  that the client has reconnected to the old IP address, even when DNS
  lookups return the new IP.

  With the fix (after a reboot of the client machine to make sure that
  kernel keys are refreshed), you'll see that the client reconnects to
  the new IP address.

  The bug is due to unlimited lifetime set by key.dns_resolver (which is
  part of keyutils package). As a result, even if IP address for the DNS
  entries change, the kernel filesystems would continue to use old IP
  address, due to the cached keys. This issue causes clients to
  misbehave when Azure Files service endpoints move to a different
  cluster.

  [Where problems could occur]
  

  Address records obtained from getaddrinfo() don't come with any TTL
  information, even if they're obtained from the DNS, so if someone is
  relying on this particularly, might face some problem/regression but I
  don't think they would face that as it would still be highly
  configurable.

  [Other information]
  ===

  This request is essentially from one of our cloud partners and they're
  highly affected by this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/keyutils/+bug/1962453/+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 1971712] Re: Add support for Intel DG2

2022-06-06 Thread Launchpad Bug Tracker
This bug was fixed in the package mesa - 22.0.1-1ubuntu2.1

---
mesa (22.0.1-1ubuntu2.1) jammy; urgency=medium

  * Add patches to support Intel DG2. (LP: #1971712)

 -- Timo Aaltonen   Mon, 09 May 2022 13:44:31 +0300

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

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

Title:
  Add support for Intel DG2

Status in linux-oem-5.17 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Fix Released
Status in linux-oem-5.17 source package in Jammy:
  Fix Committed
Status in mesa source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  Ubuntu 22.04 does not support Intel DG2-based hw which is released
  later this year.

  [Fix]

  Mesa: needs a bunch of patches backported to 22.0.x, will be upstream in 22.1 
or 22.2
  kernel: use a dkms provided by Intel and integrated in the OEM kernel source, 
the module will be shipped in a separate modules package

  [Test case]

  Boot a system with a DG2-based GPU, check that native graphics drivers
  are used.

  Test mesa also on gen9-gen12 GPU's to verify that there are no
  regressions even though the backports are for DG2.

  [What could go wrong]

  The Mesa patches are only for DG2 support, should not affect other
  hardware at all. The kernel driver is in a separate package which
  isn't installed by default except preinstall machines with this
  hardware. So other users are not affected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-oem-5.17/+bug/1971712/+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 1810499] Re: Provide a function to undo all upgrades of proposed packages

2022-06-05 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: software-properties (Ubuntu)
   Status: New => Confirmed

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

Title:
  Provide a function to undo all upgrades of proposed packages

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  While packages which are upgraded by versions delivered by a PPA are
  easy to downgrade with `ppa-purge` an equivalent function is missing
  for packages installed from `proposed` after it has been activated.
  Afaik the overview provided at
  https://askubuntu.com/questions/59443/how-can-i-revert-back-from-an-
  upgrade-to-the-proposed-repository is still the current state.

  The switch to `proposed` can be an easy way to fix issues, however
  once the fix makes it into an `-updates` repository it is a legitimate
  use case to stop using `proposed` packages since they can be
  troublesome.

  It'd be nice to automate the function provided by the scripts listed
  in the askubuntu.com post in a maintained official Ubuntu software.
  Most of the functionality is probably provided in `ppa-purge` already.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: software-properties-common 0.96.27
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan  4 10:56:18 2019
  InstallationDate: Installed on 2018-10-29 (66 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  ProcEnviron:
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1810499/+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 1958267] Re: wpa can't connect to servers using TLS 1.1 or older

2022-06-05 Thread Launchpad Bug Tracker
This bug was fixed in the package wpa - 2:2.10-9ubuntu1

---
wpa (2:2.10-9ubuntu1) kinetic; urgency=medium

  * debian/patches/lower_security_level_for_tls_1.patch:
- set the OpenSSL security level to 0 if that is the only option to
  continue the TLS negotiation, i.e., when TLS 1.0/1.1 are still allowed
  in wpa_supplicant default configuration and OpenSSL 3.0 with the
  constraint on MD5-SHA1 use. Patch proposed by Jouni Malinen on
  the upstream mailinglist (lp: #1958267)

 -- Sebastien Bacher   Tue, 31 May 2022 16:03:29
+0200

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

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

Title:
  wpa can't connect to servers using TLS 1.1 or older

Status in wpa package in Ubuntu:
  Fix Released
Status in wpa source package in Jammy:
  Confirmed
Status in wpa package in Debian:
  New

Bug description:
  wpa built with in openssl3 fails to connect to TLS 1.1 or lower server

  those uses MD5-SHA1 as digest in its signature algorithm which no
  longer meets OpenSSL default level of security of 80 bits

  http://lists.infradead.org/pipermail/hostap/2022-May/040563.html

  Workaround are described in #22 and #36 by basically using 
  CipherString = DEFAULT@SECLEVEL=0

  which lowers the security level

  ---

  With the current jammy version of wpasupplicant (2:2.10-1), I cannot
  connect to the WPA Enterprise network eduroam, which is used by
  Universities worldwide. I get a "Connection failed" message or a
  request to re-enter the password.

  - I've re-tried the credentials: no fix ;-)

  - Tried a 21.10 live session on the same machine: works fine!

  - Manually downgraded wpasupplicant to the impish version
  (2:2.9.0-21build1): connected normally.

  - Upgraded wpasupplicant to the latest version: fails to connect
  again.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: wpasupplicant 2:2.10-1
  ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12
  Uname: Linux 5.15.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu75
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 18 09:56:23 2022
  InstallationDate: Installed on 2021-11-30 (48 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211130)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: wpa
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1958267/+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 1976619] Re: Version 7.81 breaks support for multi-line header

2022-06-05 Thread Launchpad Bug Tracker
This bug was fixed in the package curl - 7.83.1-1ubuntu1

---
curl (7.83.1-1ubuntu1) kinetic; urgency=medium

  * Apply upstream patch to fix multi-line header support (LP: #1976619)

 -- Olivier Gayot   Thu, 02 Jun 2022
13:44:50 +0200

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

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

Title:
  Version 7.81 breaks support for multi-line header

Status in curl package in Ubuntu:
  Fix Released
Status in python-tornado package in Ubuntu:
  New
Status in curl package in Debian:
  New

Bug description:
  In curl 7.81, the support of multi-line headers is broken.

  
  This causes regressions in python-tornado:

  ```
  self.stop()
  
  timeout_handle = self.add_timeout(self.time() + timeout, 
timeout_callback)
  self.start()
  if timeout is not None:
  self.remove_timeout(timeout_handle)
  assert future_cell[0] is not None
  if future_cell[0].cancelled() or not future_cell[0].done():
  raise TimeoutError("Operation timed out after %s seconds" % 
timeout)
  >   return future_cell[0].result()
  E   tornado.curl_httpclient.CurlError: HTTP 599: Header without colon
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1976619/+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 1977619] Re: NetworkManager 1.36.6 orders IPv6 addresses incorrectly

2022-06-04 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: network-manager (Ubuntu)
   Status: New => Confirmed

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

Title:
  NetworkManager 1.36.6 orders IPv6 addresses incorrectly

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  My network has both DHCPv6 and SLAAC for IPv6. From both a privacy
  perspective and readability reasons, DHCPv6 should *always* be
  preferred over SLAAC addresses when available.

  NetworkManager has always been able to adhere to that by simply
  setting ip6.privacy=0 for the connection.

  So if you would - for instance - run `curl ifconfig.co`, the DHCPv6
  address would be used to connect to the outside world.

  Since the update to 1.36.6, this is no longer the case. NetworkManager
  now routes outgoing traffic through the SLAAC address, even if
  ip6.privacy=0 is set for the connection. Setting
  net.ipv6.conf.all.use_tempaddr=0 and
  net.ipv6.conf..use_tempaddr=0 with sysctl also no longer
  has any effect.

  Removing the SLAAC addresses with `ip addr del` or disabling SLAAC
  RA's altogether is the only way to stop NetworkManager from preferring
  SLAAC over DHCPv6 now.

  Looking at the changelog of NetworkManager 1.36.6, things regarding IP
  address order and temporary addresses have been changed in that
  release:
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-36/NEWS

  When running `ip -6 a`, the list now sorts SLAAC addresses above
  DHCPv6 addresses. With NetworkManager 1.36.4 this was not the case.
  (The Linux kernel uses the address highest in the list as preferred.)

  This can break many real-life use cases. For instance, my router gives
  out static leases to my machines. Those addresses are whitelisted in
  all kinds of firewalls to allow me to access servers for my work. Now
  that the "wrong" address is being preferred for outgoing traffic (a
  SLAAC address that I have no influence on), I am being locked out of
  the servers in question unless I forcefully remove the addresses or
  disable SLAAC on my router, so my outgoing traffic is being routed
  through the DHCPv6 address again.

  So this update introduces a very breaking change in IPv6 source
  address selection to an LTS release, while LTS releases should be
  stable.

  I should note that the bug is not present in NetworkManager 1.38.0 on
  Debian sid. That just prefers DHCPv6 addresses when available, like it
  should.

  /etc/os-release:

  PRETTY_NAME="Ubuntu 22.04 LTS"
  NAME="Ubuntu"
  VERSION_ID="22.04"
  VERSION="22.04 LTS (Jammy Jellyfish)"
  VERSION_CODENAME=jammy
  ID=ubuntu
  ID_LIKE=debian
  HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  UBUNTU_CODENAME=jammy

  nmcli -v:

  nmcli tool, version 1.36.6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1977619/+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 1977649] [NEW] my system is not showing me 1080p resolution

2022-06-04 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

After ubuntu 20 install I am not able to increase my screen resolution.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.13.0-44.49~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-44-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Jun  4 19:16:39 2022
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 4th Generation Core Processor Family Integrated Graphics 
Controller [8086:041e] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd 4th Generation Core Processor Family 
Integrated Graphics Controller [1458:d000]
InstallationDate: Installed on 2022-06-04 (0 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
MachineType: Gigabyte Technology Co., Ltd. H81M-S1
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-44-generic 
root=UUID=fc58eb01-ce48-4d0e-ac05-443d37948ed0 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/17/2014
dmi.bios.release: 4.6
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: FC
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H81M-S1
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.:bvrFC:bd01/17/2014:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnH81M-S1:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-S1:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: H81M-S1
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-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: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal third-party-packages ubuntu
-- 
my system is not showing me 1080p resolution
https://bugs.launchpad.net/bugs/1977649
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg 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 1947588] Re: Infinite Loop in OpenSSL s_server

2022-06-04 Thread Launchpad Bug Tracker
This bug was fixed in the package openssl - 3.0.3-5ubuntu2

---
openssl (3.0.3-5ubuntu2) kinetic; urgency=medium

  * d/p/Set-systemwide-default-settings-for-libssl-users: don't comment out
the CipherString string to avoid an empty section.

 -- Simon Chopin   Tue, 31 May 2022 13:02:15 +0200

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

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

Title:
  Infinite Loop in OpenSSL s_server

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Focal:
  Confirmed
Status in openssl source package in Impish:
  Confirmed
Status in openssl source package in Jammy:
  Confirmed

Bug description:
  [Impact]

  The TLS test server `openssl s_server` can very easily be led into an
  infinite loop if configured with incompatible settings and used via
  DTLS. This makes it harder to test one's TLS configuration.

  [Test plan]

  In one session:
  $ openssl s_server -nocert -psk 01020304 -dtls1
  In parallel:
  $ openssl s_client -dtls1 -psk 01020304

  The server session will enter an infinite loop:
  Using default temp DH parameters
  ACCEPT
  ERROR
  140247926990208:error:141FC044:SSL routines:tls_setup_handshake:internal 
error:../ssl/statem/statem_lib.c:109:
  ERROR
  140247926990208:error:141FC044:SSL routines:tls_setup_handshake:internal 
error:../ssl/statem/statem_lib.c:109:
  ERROR
  ... etc...

  [Where problems could occur]

  The patch is fairly self-contained, so regressions should only occur in
  the `openssl s_server` application, and not in the libssl or libcrypto
  libraries.
  However, the patch could break said server, which might be used in e.g.
  autopkgtests.

  [Original report]
  Launching openssl s_server as follows:

  $ openssl s_server -nocert -psk 01020304 -dtls1

  And using openssl s_client to connect to it like this:

  $ openssl s_client -dtls1 -psk 01020304

  Results in s_server entering an infinite loop:

  Using default temp DH parameters
  ACCEPT
  ERROR
  140247926990208:error:141FC044:SSL routines:tls_setup_handshake:internal 
error:../ssl/statem/statem_lib.c:109:
  ERROR
  140247926990208:error:141FC044:SSL routines:tls_setup_handshake:internal 
error:../ssl/statem/statem_lib.c:109:
  ERROR

  ...and so on...

  I have confirmed that upstream OpenSSL does not have this issue in a
  default build of 1.1.1j or 1.1.1k. Upstream 1.1.1l has a different bug
  with these commands (https://github.com/openssl/openssl/issues/16707)
  and it was while working on the fix for that issue
  (https://github.com/openssl/openssl/pull/16838) that I noticed this
  problem in the Ubuntu packages.

  $ lsb_release -rd
  Description: Ubuntu 21.04
  Release: 21.04

  $ apt-cache policy openssl
  openssl:
Installed: 1.1.1j-1ubuntu3.5
Candidate: 1.1.1j-1ubuntu3.5
Version table:
   *** 1.1.1j-1ubuntu3.5 500
  500 http://gb.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu hirsute-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.1.1j-1ubuntu3 500
  500 http://gb.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages

  $ openssl version -a
  OpenSSL 1.1.1j 16 Feb 2021
  built on: Mon Aug 23 17:02:39 2021 UTC
  platform: debian-amd64
  options: bn(64,64) rc4(16x,int) des(int) blowfish(ptr)
  compiler: gcc -fPIC -pthread -m64 -Wa,--noexecstack -Wall -Wa,--noexecstack 
-g -O2 -ffile-prefix-map=/build/openssl-5U8yxE/openssl-1.1.1j=. -flto=auto 
-ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security 
-DOPENSSL_TLS_SECURITY_LEVEL=2 -DOPENSSL_USE_NODELETE -DL_ENDIAN -DOPENSSL_PIC 
-DOPENSSL_CPUID_OBJ -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT 
-DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM 
-DSHA512_ASM -DKECCAK1600_ASM -DRC4_ASM -DMD5_ASM -DAESNI_ASM -DVPAES_ASM 
-DGHASH_ASM -DECP_NISTZ256_ASM -DX25519_ASM -DPOLY1305_ASM -DNDEBUG -Wdate-time 
-D_FORTIFY_SOURCE=2
  OPENSSLDIR: "/usr/lib/ssl"
  ENGINESDIR: "/usr/lib/x86_64-linux-gnu/engines-1.1"
  Seeding source: os-specific

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1947588/+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 1974035] Re: openssl: Merge 3.0.3-4 from Debian unstable

2022-06-04 Thread Launchpad Bug Tracker
This bug was fixed in the package openssl - 3.0.3-5ubuntu2

---
openssl (3.0.3-5ubuntu2) kinetic; urgency=medium

  * d/p/Set-systemwide-default-settings-for-libssl-users: don't comment out
the CipherString string to avoid an empty section.

 -- Simon Chopin   Tue, 31 May 2022 13:02:15 +0200

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

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

Title:
  openssl: Merge 3.0.3-4 from Debian unstable

Status in openssl package in Ubuntu:
  Fix Released

Bug description:
  The version 3.0.3-4 from Debian unstable should be merged in Kinetic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1974035/+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 1972056] Re: [openssl3] please sync openssl.cnf to ease changing security level

2022-06-04 Thread Launchpad Bug Tracker
This bug was fixed in the package openssl - 3.0.3-5ubuntu2

---
openssl (3.0.3-5ubuntu2) kinetic; urgency=medium

  * d/p/Set-systemwide-default-settings-for-libssl-users: don't comment out
the CipherString string to avoid an empty section.

 -- Simon Chopin   Tue, 31 May 2022 13:02:15 +0200

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

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

Title:
  [openssl3] please sync openssl.cnf to ease changing security level

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Jammy:
  Confirmed
Status in openssl source package in Kinetic:
  Fix Released
Status in openssl package in Debian:
  Fix Released

Bug description:
  [Impact]

  The OpenSSL 3.0 lead to a lot of broken setups. Some of them are
  regressions, but others are simply broken due to the use of outdated
  algorithms, such as SHA-1 signature on certificates. Changing the
  security level is a common action to identify and work around such
  cases, and as such the user should be able to change it easily  in the
  default config file.

  The fix is to partially revert our delta that ignored a Debian patch:
  instead of ignoring the patch entirely, we modify it to only affect
  the default configuration file, and in a way that matches our
  patchset. Using this approach will allow us to pick up on Debian's
  changes more easily during subsequent merges.

  [Test Plan]

  To easily check that the setting is taken into account, one can use
  'openssl ciphers -s'

  $ openssl ciphers -v -s | wc -l # Uses the default value
  30
  $ openssl ciphers -v -s 'DEFAULT:@SECLEVEL=2' | wc -l
  30
  $ openssl ciphers -v -s 'DEFAULT:@SECLEVEL=3' | wc -l
  24
  $ vim /etc/ssl/openssl.cf # edit the config file to bump the seclevel to 3
  $ openssl ciphers -v -s | wc -l # Uses the new value from the config file
  24

  [Where problems could occur]

  The changes could break the overall configuration of OpenSSL!

  [Origin report]
  openssl.cnf as provided misses some directive, which make it a bit difficult 
to change security level, which since openssl 3 disables SHA1 signatures.

  See also this Debian bug https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=1010360 and the committed fix:
  
https://salsa.debian.org/debian/openssl/-/commit/b507914c40270e32cde6afcc8af93707c225e7f4

  Can you please sync this change in Ubuntu openssl?

  This way one should just add a single directive to change the security
  level.

  Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1972056/+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 1974037] Re: openssl: EVP_EC_gen() segfault without init

2022-06-04 Thread Launchpad Bug Tracker
This bug was fixed in the package openssl - 3.0.3-5ubuntu2

---
openssl (3.0.3-5ubuntu2) kinetic; urgency=medium

  * d/p/Set-systemwide-default-settings-for-libssl-users: don't comment out
the CipherString string to avoid an empty section.

 -- Simon Chopin   Tue, 31 May 2022 13:02:15 +0200

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

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

Title:
  openssl: EVP_EC_gen() segfault without init

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Jammy:
  Confirmed
Status in openssl source package in Kinetic:
  Fix Released
Status in openssl package in Debian:
  Fix Released

Bug description:
  [Impact]

  The fix for
  https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1968997 has
  broken some code paths as the new string comparison functions now need
  initialization, triggering segafults.

  The provided debdiff fixes the immediate issue and also settles on a
  new implementation not requiring the initialization in the first
  place.

  [Test Plan]

  Since this is a regression fix, we first need to check that the
  original bug hasn't cropped up again:

  sudo locale-gen tr_TR.UTF-8
  LANG=C curl https://ubuntu.com/ > /dev/null # This work
  LANG=tr_TF.UTF-8 curl https://ubuntu.com/ > /dev/null # This should work as 
well

  For the regression itself:

  sudo apt install libssl-dev
  cat < openssl_test.c
  #include 
  int main()
  {
  EVP_PKEY_Q_keygen(NULL, NULL, "EC", "P-256");
  }
  EOF
  gcc openssl_test.c -lcrypto -lssl -o openssl_test
  ./openssl_test

  
  [Where problems could occur]

  This new patch set is relatively massive, on top of another massive one.
  Some new regressions could crop up of a similar kind. Furthermore, the
  homegrown string comparison function could be buggy, leading to algorithm 
name mismatches.

  [Other info]

  The patches all come from upstream and have been merged on their 3.0
  maintenance branch.

  [Original report]

  Source: sscg
  Version: 3.0.2-1
  Severity: serious
  Tags: ftbfs

  https://buildd.debian.org/status/logs.php?pkg=sscg=3.0.2-1%2Bb1

  ...
   1/10 generate_rsa_key_test FAIL  0.01s   killed by signal 11 
SIGSEGV
  04:32:21 MALLOC_PERTURB_=87 
/<>/obj-x86_64-linux-gnu/generate_rsa_key_test
  ...

  Summary of Failures:

   1/10 generate_rsa_key_test FAIL  0.01s   killed by signal
  11 SIGSEGV

  Ok: 9
  Expected Fail:  0
  Fail:   1
  Unexpected Pass:0
  Skipped:0
  Timeout:0
  dh_auto_test: error: cd obj-x86_64-linux-gnu && LC_ALL=C.UTF-8 
MESON_TESTTHREADS=4 ninja test returned exit code 1
  make: *** [debian/rules:6: binary-arch] Error 25

  This has also been reported on the openssl-users mailing list:

  https://www.mail-archive.com/openssl-users@openssl.org/msg90830.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1974037/+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 1968912] Re: vim.tiny reports 'E1187: Failed to source defaults.vim' on execution in default install

2022-06-03 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  vim.tiny reports 'E1187: Failed to source defaults.vim' on execution
  in default install

Status in vim package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 22.04

  When running vim.tiny it says:

  $ vim.tiny
  E1187: Failed to source defaults.vim
  Press ENTER or type command to continue

  This is due to the defaults.vim file not being available.  If you just
  run it as vi

  $ vi

  this message does not appear as vim.tiny runs in compatibility mode.  I found 
mention of this issue in:
  https://github.com/grml/grml-etc-core/issues/99

  The defaults.vim file is provided by the package vim-runtime.

  I'm unsure what the issue is, if something needs to be in
  /etc/vim/vimrc.tiny or a /etc/vim/vimrc needs to be provided dpkg
  claims vimrc is in vim-common, but no file is installed for me from
  that package, or if vim-runtime needs to be a required package for
  vim-tiny

  $ dpkg -S /etc/vim/vimrc
  vim-common: /etc/vim/vimrc
  $ ls -al /etc/vim/vimrc
  ls: cannot access '/etc/vim/vimrc': No such file or directory

  I discovered this because my .selected-editor was vim.tiny after
  running crontab -e

  $ crontab -e

  Select an editor.  To change later, run 'select-editor'.
    1. /bin/nano< easiest
    2. /usr/bin/vim.tiny
    3. /bin/ed

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: vim-tiny 2:8.2.3995-1ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-1005.5-raspi 5.15.30
  Uname: Linux 5.15.0-1005-raspi aarch64
  ApportVersion: 2.20.11-0ubuntu81
  Architecture: arm64
  CasperMD5CheckResult: unknown
  Date: Wed Apr 13 11:56:35 2022
  ImageMediaBuild: 20201022
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: vim
  UpgradeStatus: Upgraded to jammy on 2022-04-09 (4 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1968912/+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 1972115] Re: ubuntu-bug exits after dialog instead of sending data

2022-06-03 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  ubuntu-bug  exits after dialog instead of sending data

Status in apport package in Ubuntu:
  Confirmed
Status in apport source package in Jammy:
  Confirmed
Status in apport source package in Kinetic:
  Confirmed

Bug description:
  After a gnome-shell crash, I am trying to manually submit it by
  running 'ubuntu-bug /var/crash/_usr_bin_gnome-shell.1000.crash'.  This
  results in an apport-gtk prompt asking me "Send problem report to the
  developers?"  When I click 'send', the dialog disappears and ubuntu-
  bug exits, without uploading data to launchpad or interfacing with the
  browser.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1972115/+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 1972115] Re: ubuntu-bug exits after dialog instead of sending data

2022-06-03 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  ubuntu-bug  exits after dialog instead of sending data

Status in apport package in Ubuntu:
  Confirmed
Status in apport source package in Jammy:
  Confirmed
Status in apport source package in Kinetic:
  Confirmed

Bug description:
  After a gnome-shell crash, I am trying to manually submit it by
  running 'ubuntu-bug /var/crash/_usr_bin_gnome-shell.1000.crash'.  This
  results in an apport-gtk prompt asking me "Send problem report to the
  developers?"  When I click 'send', the dialog disappears and ubuntu-
  bug exits, without uploading data to launchpad or interfacing with the
  browser.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1972115/+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 1977493] [NEW] Upgrade from Ubuntu 21.10 to 22.04 fails - unmet dependencies: libpam-modules

2022-06-03 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

---Problem Description---
Upgrade from Ubuntu 21.10 to 22.4 fails

I run do-release-upgrade and I got a message upgrade completed with
errors. I rebooted the server and it is now in an undefined state
between 21.10 and 22.04. Not all packages have been installed. I attach
apt log and output of some commands:

root@tuxmaker:~# cat /etc/os-release 
PRETTY_NAME="Ubuntu 21.10"
NAME="Ubuntu"
VERSION_ID="21.10"
VERSION="21.10 (Impish Indri)"
VERSION_CODENAME=impish
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/;
SUPPORT_URL="https://help.ubuntu.com/;
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
UBUNTU_CODENAME=impish

root@tuxmaker:~# do-release-upgrade 
Checking for a new Ubuntu release
Please install all available updates for your release before upgrading.

root@tuxmaker:~# apt dist-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
 libpam-modules : PreDepends: libpam-modules-bin (= 1.3.1-5ubuntu11) but 
1.4.0-11ubuntu2 is installed
  Recommends: update-motd but it is not installed
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or 
specify a solution).

root@tuxmaker:~# apt --fix-broken install
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Correcting dependencies... Done
The following additional packages will be installed:
  libpam-modules
The following packages will be upgraded:
  libpam-modules
1 upgraded, 0 newly installed, 0 to remove and 1208 not upgraded.
4 not fully installed or removed.
Need to get 0 B/279 kB of archives.
After this operation, 1,024 B disk space will be freed.
Do you want to continue? [Y/n] y
Preconfiguring packages ...
(Reading database ... 401827 files and directories currently installed.)
Preparing to unpack .../libpam-modules_1.4.0-11ubuntu2_s390x.deb ...
dpkg: error processing archive 
/var/cache/apt/archives/libpam-modules_1.4.0-11ubuntu2_s390x.deb (--unpack):
 new libpam-modules:s390x package pre-installation script subprocess returned 
error exit status 2
Errors were encountered while processing:
 /var/cache/apt/archives/libpam-modules_1.4.0-11ubuntu2_s390x.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


Contact Information = pp...@de.ibm.com 
 
---uname output---
Linux tuxmaker 5.13.0-44-generic #49-Ubuntu SMP Wed May 18 13:30:03 UTC 2022 
s390x s390x s390x GNU/Linux
 
Machine Type = z15, 8561-701 
 
---boot type---
upgade
 
---Kernel cmdline used to launch install---
do-release-upgrade
 
---Install repository type---
Internet repository
 
---Install repository Location---
http://ports.ubuntu.com:80/
 
---Point of failure---
Other failure during installation (stage 1)

** Affects: pam (Ubuntu)
 Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
 Status: New


** Tags: architecture-s39064 bugnameltc-198429 severity-high 
targetmilestone-inin2110
-- 
Upgrade from Ubuntu 21.10 to 22.04 fails - unmet dependencies: libpam-modules
https://bugs.launchpad.net/bugs/1977493
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to pam 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 1971418] Re: network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29

2022-06-03 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 5.15.0-35.36

---
linux (5.15.0-35.36) jammy; urgency=medium

  * CVE-2022-21499
- SAUCE: debug: Lock down kgdb

linux (5.15.0-34.35) jammy; urgency=medium

  * jammy/linux: 5.15.0-34.35 -proposed tracker (LP: #1974322)

  * AMD APU s2idle is broken after the ASIC reset fix (LP: #1972134)
- drm/amdgpu: unify BO evicting method in amdgpu_ttm
- drm/amdgpu: explicitly check for s0ix when evicting resources

  * amd_gpio AMDI0030:00: Failed to translate GPIO pin 0x to IRQ, err -517
(LP: #1971597)
- gpio: Request interrupts after IRQ is initialized

  * config CONFIG_HISI_PMU for  kunpeng920 (LP: #1956086)
- [Config] CONFIG_HISI_PMU=m

  * Mute/mic LEDs no function on EliteBook G9 platfroms (LP: #1970552)
- ALSA: hda/realtek: Enable mute/micmute LEDs support for HP Laptops

  * network-manager/1.36.4-2ubuntu1 ADT test failure with linux/5.15.0-28.29
(LP: #1971418)
- Revert "rfkill: make new event layout opt-in"

  * PCIE LnkCtl ASPM not enabled under VMD mode for Alder Lake platforms
(LP: #1942160)
- SAUCE: vmd: fixup bridge ASPM by driver name instead

  * Mute/mic LEDs no function on HP EliteBook 845/865 G9 (LP: #1970178)
- ALSA: hda/realtek: Enable mute/micmute LEDs and limit mic boost on 
EliteBook
  845/865 G9

  * Enable headset mic on Lenovo P360 (LP: #1967069)
- ALSA: hda/realtek: Enable headset mic on Lenovo P360

  * WCN6856 BT keep in OFF state after coldboot system (LP: #1967067)
- Bluetooth: btusb: Improve stability for QCA devices

  * Screen sometimes can't update [Failed to post KMS update: CRTC property
(GAMMA_LUT) not found] (LP: #1967274)
- drm/i915/xelpd: Enable Pipe color support for D13 platform
- drm/i915: Use unlocked register accesses for LUT loads
- drm/i915/xelpd: Enable Pipe Degamma
- drm/i915/xelpd: Add Pipe Color Lut caps to platform config

  * Jammy update: v5.15.35 upstream stable release (LP: #1969857)
- drm/amd/display: Add pstate verification and recovery for DCN31
- drm/amd/display: Fix p-state allow debug index on dcn31
- hamradio: defer 6pack kfree after unregister_netdev
- hamradio: remove needs_free_netdev to avoid UAF
- cpuidle: PSCI: Move the `has_lpi` check to the beginning of the function
- ACPI: processor idle: Check for architectural support for LPI
- ACPI: processor: idle: fix lockup regression on 32-bit ThinkPad T40
- btrfs: remove unused parameter nr_pages in add_ra_bio_pages()
- btrfs: remove no longer used counter when reading data page
- btrfs: remove unused variable in btrfs_{start,write}_dirty_block_groups()
- soc: qcom: aoss: Expose send for generic usecase
- dt-bindings: net: qcom,ipa: add optional qcom,qmp property
- net: ipa: request IPA register values be retained
- btrfs: release correct delalloc amount in direct IO write path
- ALSA: core: Add snd_card_free_on_error() helper
- ALSA: sis7019: Fix the missing error handling
- ALSA: ali5451: Fix the missing snd_card_free() call at probe error
- ALSA: als300: Fix the missing snd_card_free() call at probe error
- ALSA: als4000: Fix the missing snd_card_free() call at probe error
- ALSA: atiixp: Fix the missing snd_card_free() call at probe error
- ALSA: au88x0: Fix the missing snd_card_free() call at probe error
- ALSA: aw2: Fix the missing snd_card_free() call at probe error
- ALSA: azt3328: Fix the missing snd_card_free() call at probe error
- ALSA: bt87x: Fix the missing snd_card_free() call at probe error
- ALSA: ca0106: Fix the missing snd_card_free() call at probe error
- ALSA: cmipci: Fix the missing snd_card_free() call at probe error
- ALSA: cs4281: Fix the missing snd_card_free() call at probe error
- ALSA: cs5535audio: Fix the missing snd_card_free() call at probe error
- ALSA: echoaudio: Fix the missing snd_card_free() call at probe error
- ALSA: emu10k1x: Fix the missing snd_card_free() call at probe error
- ALSA: ens137x: Fix the missing snd_card_free() call at probe error
- ALSA: es1938: Fix the missing snd_card_free() call at probe error
- ALSA: es1968: Fix the missing snd_card_free() call at probe error
- ALSA: fm801: Fix the missing snd_card_free() call at probe error
- ALSA: galaxy: Fix the missing snd_card_free() call at probe error
- ALSA: hdsp: Fix the missing snd_card_free() call at probe error
- ALSA: hdspm: Fix the missing snd_card_free() call at probe error
- ALSA: ice1724: Fix the missing snd_card_free() call at probe error
- ALSA: intel8x0: Fix the missing snd_card_free() call at probe error
- ALSA: intel_hdmi: Fix the missing snd_card_free() call at probe error
- ALSA: korg1212: Fix the missing snd_card_free() call at probe error
- ALSA: lola: Fix the missing snd_card_free() call at probe error
- ALSA: lx6464es: Fix the missing snd_card_free() call at probe error
- 

[Touch-packages] [Bug 1976371] Re: SRU for evolution-data-server 3.44.2

2022-06-02 Thread Launchpad Bug Tracker
This bug was fixed in the package evolution-data-server - 3.44.2-1

---
evolution-data-server (3.44.2-1) unstable; urgency=medium

  * New upstream release (LP: #1976371)

 -- Nathan Pratta Teodosio   Fri, 31 May
2022 09:30:00 -0300

** Changed in: evolution-data-server (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  SRU for evolution-data-server 3.44.2

Status in evolution-data-server package in Ubuntu:
  Fix Released
Status in evolution-data-server source package in Jammy:
  In Progress

Bug description:
  Impact
  --
  This is a new stable release in the 3.44 series.

  https://gitlab.gnome.org/GNOME/evolution-data-
  server/-/blob/3.44.2/NEWS

  Test Case
  -
  Install the update
  Log out and log back in (or restart)
  Ensure that GNOME Calendar and Evolution still work fine.

  What Could Go Wrong
  ---
  As a component of GNOME core, there is a micro-release exception for 
evolution-data-server

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1976371/+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 1912256] Re: Missing channel binding prevents authentication to ActiveDirectory

2022-06-02 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Missing channel binding prevents authentication to ActiveDirectory

Status in cyrus-sasl2 package in Ubuntu:
  Confirmed
Status in openldap package in Ubuntu:
  Confirmed

Bug description:
  > Are you uncertain if your issue is really a bug?
  Effect is an authentication error. Root case is a "missing feature" (see 
below) and requires updating dependencies, downporting.

  > If you are certain this is a bug please include the source package the bug 
is in.
  It's in the interaction between three libraries: openldap, cyrus-sasl, krb5

  > 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Broken in 18.04 and also in 20.10 (I guess it's also broken in anything 
inbetween)

  > 2) The version of the package you are using, via 'apt-cache policy
  pkgname' or by checking in Software Center

  libsasl2-modules-gssapi-mit: 2.1.27+dfsg-2ubuntu1
  ldap-utils: 2.4.53+dfsg-1ubuntu1.2
  libgssapi-krb5-2: 1.17-10ubuntu0.1

  > 3) What you expected to happen
  # kinit
  $ export LDAPSASL_CBINDING=tls-endpoint
  $ ldapwhoami -O minssf=0,maxssf=0 -N -Y GSSAPI -H ldaps://
  SASL/GSSAPI authentication started
  SASL username: 
  SASL SSF: 0
  u:

  > 4) What happened instead
  SASL/GSSAPI authentication started
  ldap_sasl_interactive_bind_s: Invalid credentials (49)
  additional info: 80090346: LdapErr: DSID-0C090597, comment: 
AcceptSecurityContext error, data 80090346, v4563

  
  ---

  
  Microsoft ActiveDirectory has "LDAP Channel Binding" and recommends 
activating this as a required feature. See 
https://access.redhat.com/articles/4661861
  Authentication to any AD DC which has mandatory channel binding fails.

  Channel binding requires at least an update to cyrus-sasl, which is
  not in any release as far as I can see:

  https://github.com/cyrusimap/cyrus-
  sasl/commit/975edbb69070eba6b035f08776de771a129cfb57

  
  It also needs this commit in openldap:

  
https://git.openldap.org/openldap/openldap/-/commit/3cd50fa8b32a21040a9892e2a8a7a9dfc7541ce6

  Which as far as I can tell is v2.5 (branch OPENLDAP_REL_ENG_2_5).

  
  RH also mentions it needs up-to-date krb5 libraries, but I can't tell what 
minimum version this needs.

  
  I can build all libraries from source, current master (except for krb5 where 
I've used 1.18.3) and can confirm that channel binding works when using those 
libraries.

  
  I'm not sure if Samba is affected, but at least adcli, ldap-utils, and I 
would guess by extension also SSSD and realmd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1912256/+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 1912256] Re: Missing channel binding prevents authentication to ActiveDirectory

2022-06-02 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: cyrus-sasl2 (Ubuntu)
   Status: New => Confirmed

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

Title:
  Missing channel binding prevents authentication to ActiveDirectory

Status in cyrus-sasl2 package in Ubuntu:
  Confirmed
Status in openldap package in Ubuntu:
  Confirmed

Bug description:
  > Are you uncertain if your issue is really a bug?
  Effect is an authentication error. Root case is a "missing feature" (see 
below) and requires updating dependencies, downporting.

  > If you are certain this is a bug please include the source package the bug 
is in.
  It's in the interaction between three libraries: openldap, cyrus-sasl, krb5

  > 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Broken in 18.04 and also in 20.10 (I guess it's also broken in anything 
inbetween)

  > 2) The version of the package you are using, via 'apt-cache policy
  pkgname' or by checking in Software Center

  libsasl2-modules-gssapi-mit: 2.1.27+dfsg-2ubuntu1
  ldap-utils: 2.4.53+dfsg-1ubuntu1.2
  libgssapi-krb5-2: 1.17-10ubuntu0.1

  > 3) What you expected to happen
  # kinit
  $ export LDAPSASL_CBINDING=tls-endpoint
  $ ldapwhoami -O minssf=0,maxssf=0 -N -Y GSSAPI -H ldaps://
  SASL/GSSAPI authentication started
  SASL username: 
  SASL SSF: 0
  u:

  > 4) What happened instead
  SASL/GSSAPI authentication started
  ldap_sasl_interactive_bind_s: Invalid credentials (49)
  additional info: 80090346: LdapErr: DSID-0C090597, comment: 
AcceptSecurityContext error, data 80090346, v4563

  
  ---

  
  Microsoft ActiveDirectory has "LDAP Channel Binding" and recommends 
activating this as a required feature. See 
https://access.redhat.com/articles/4661861
  Authentication to any AD DC which has mandatory channel binding fails.

  Channel binding requires at least an update to cyrus-sasl, which is
  not in any release as far as I can see:

  https://github.com/cyrusimap/cyrus-
  sasl/commit/975edbb69070eba6b035f08776de771a129cfb57

  
  It also needs this commit in openldap:

  
https://git.openldap.org/openldap/openldap/-/commit/3cd50fa8b32a21040a9892e2a8a7a9dfc7541ce6

  Which as far as I can tell is v2.5 (branch OPENLDAP_REL_ENG_2_5).

  
  RH also mentions it needs up-to-date krb5 libraries, but I can't tell what 
minimum version this needs.

  
  I can build all libraries from source, current master (except for krb5 where 
I've used 1.18.3) and can confirm that channel binding works when using those 
libraries.

  
  I'm not sure if Samba is affected, but at least adcli, ldap-utils, and I 
would guess by extension also SSSD and realmd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1912256/+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 1970978] [NEW] On Save As dialog, any navigation operation (e.g. change to sub-folder) takes focus away from file name entry and instead switches to search

2022-06-01 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Within "Save As" dialogs from any desktop application, all navigation
operations, specifically the most common one of changing folders,
switches focus away from the file name input, resulting in the search
input box accepting keyboard input instead of the filename input box.
This is extremely frustrating for a several reasons:

1. After navigating to the desired folder, typing the name for the file
is instead captured by the search input box instead of the expected
filename input box

2. The search input box does not even appear until key presses are
received, making it even more surprising that the filename is not being
altered and is instead the beginning of a search

3. Using the mouse to re-focus on the filename input box deselects the
originally selected default file name text, causing the user to have to
re-select everything

4. Re-selecting everything (see previous item) causes the default file
name extension (which is excluded in the initial selection) to also be
selected, requiring the user to think about what it was and to re-enter
that extension as well

5. "Tab" key navigation takes an inordinate number of tab key presses to
return to the filename input box

Sorry to complain about this, but I almost ALWAYS choose to change
folders, and then when I type in the name, I have to re-do all the steps
described above because the search input has invariably captured my key
presses instead of the changing the filename. It is very annoying.

I would like to suggest that the search input box either not be
automatically switched to in the  "Save As" mode of the dialog, or to
have a separate and explicit search input box that does not
automatically receive input after folder navigation operations.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: nautilus 1:3.36.3-0ubuntu1.20.04.1
ProcVersionSignature: Ubuntu 5.13.0-40.45~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.23
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 29 11:06:32 2022
ExecutablePath: /usr/bin/nautilus
InstallationDate: Installed on 2021-09-13 (227 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
ProcEnviron:
 XDG_RUNTIME_DIR=
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:

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


** Tags: amd64 apport-bug focal save-as
-- 
On Save As dialog, any navigation operation (e.g. change to sub-folder) takes 
focus away from file name entry and instead switches to search
https://bugs.launchpad.net/bugs/1970978
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to gtk+3.0 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 1960583] Re: dpkg error while processing - can't install nor upgrade

2022-06-01 Thread Launchpad Bug Tracker
*** This bug is a duplicate of bug 1960582 ***
https://bugs.launchpad.net/bugs/1960582

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

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

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

Title:
  dpkg error while processing - can't install nor upgrade

Status in apt package in Ubuntu:
  Confirmed
Status in dpkg package in Ubuntu:
  Confirmed

Bug description:
  My current ubuntu version :
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description: Ubuntu Jammy Jellyfish (development branch)
  Release: 22.04
  Codename: jammy

  Issue :
  when `sudo apt update` is ok, all newest package is downloaded
  but `sudo apt ugprade` show current error : ]

  sudo apt upgrade
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Calculating upgrade... Done
  The following packages have been kept back:
librygel-renderer-2.6-2 librygel-server-2.6-2 rygel
  The following packages will be upgraded:
bolt code deja-dup enchant-2 fwupd gdm3 gir1.2-gdm-1.0 
gir1.2-gst-plugins-base-1.0 gir1.2-nm-1.0 gir1.2-nma-1.0
gir1.2-upowerglib-1.0 gjs gstreamer1.0-alsa gstreamer1.0-gl 
gstreamer1.0-gtk3 gstreamer1.0-plugins-base
gstreamer1.0-plugins-base-apps gstreamer1.0-plugins-good 
gstreamer1.0-pulseaudio gstreamer1.0-x initramfs-tools
initramfs-tools-bin initramfs-tools-core iputils-ping iputils-tracepath 
language-pack-en language-pack-gnome-en
libenchant-2-2 libfwupd2 libfwupdplugin5 libgdm1 libgjs0g 
libgstreamer-gl1.0-0 libgstreamer-plugins-base1.0-0
libgstreamer-plugins-good1.0-0 libnl-3-200 libnl-genl-3-200 
libnl-route-3-200 libnm0 libnma-common libnma0
libpkcs11-helper1 libseccomp2 libunistring2 libunistring2:i386 
libupower-glib3 media-types nano network-manager
network-manager-config-connectivity-ubuntu python3-paramiko 
python3-software-properties simple-scan
software-properties-common software-properties-gtk upower
  56 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
  10 not fully installed or removed.
  Need to get 0 B/94,6 MB of archives.
  After this operation, 1.928 kB of additional disk space will be used.
  Do you want to continue? [Y/n] Y
  Extracting templates from packages: 100%
  Preconfiguring packages ...
  Setting up dpkg (1.21.1ubuntu1) ...
  head: error reading 'dpkg': Is a directory
  dpkg: error processing package dpkg (--configure):
   installed dpkg package post-installation script subprocess returned error 
exit status 1
  Errors were encountered while processing:
   dpkg
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  i have to resintall all of the package in cache with `sudo dpkg -i 
/var/cache/apt/archives/*.deb
  `, but the cache sometimes is not the newest packages
  and when i rerun `sudo apt upgrade`, there is still not the newest package

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1960583/+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 1960583] Re: dpkg error while processing - can't install nor upgrade

2022-06-01 Thread Launchpad Bug Tracker
*** This bug is a duplicate of bug 1960582 ***
https://bugs.launchpad.net/bugs/1960582

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

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

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

Title:
  dpkg error while processing - can't install nor upgrade

Status in apt package in Ubuntu:
  Confirmed
Status in dpkg package in Ubuntu:
  Confirmed

Bug description:
  My current ubuntu version :
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description: Ubuntu Jammy Jellyfish (development branch)
  Release: 22.04
  Codename: jammy

  Issue :
  when `sudo apt update` is ok, all newest package is downloaded
  but `sudo apt ugprade` show current error : ]

  sudo apt upgrade
  Reading package lists... Done
  Building dependency tree... Done
  Reading state information... Done
  Calculating upgrade... Done
  The following packages have been kept back:
librygel-renderer-2.6-2 librygel-server-2.6-2 rygel
  The following packages will be upgraded:
bolt code deja-dup enchant-2 fwupd gdm3 gir1.2-gdm-1.0 
gir1.2-gst-plugins-base-1.0 gir1.2-nm-1.0 gir1.2-nma-1.0
gir1.2-upowerglib-1.0 gjs gstreamer1.0-alsa gstreamer1.0-gl 
gstreamer1.0-gtk3 gstreamer1.0-plugins-base
gstreamer1.0-plugins-base-apps gstreamer1.0-plugins-good 
gstreamer1.0-pulseaudio gstreamer1.0-x initramfs-tools
initramfs-tools-bin initramfs-tools-core iputils-ping iputils-tracepath 
language-pack-en language-pack-gnome-en
libenchant-2-2 libfwupd2 libfwupdplugin5 libgdm1 libgjs0g 
libgstreamer-gl1.0-0 libgstreamer-plugins-base1.0-0
libgstreamer-plugins-good1.0-0 libnl-3-200 libnl-genl-3-200 
libnl-route-3-200 libnm0 libnma-common libnma0
libpkcs11-helper1 libseccomp2 libunistring2 libunistring2:i386 
libupower-glib3 media-types nano network-manager
network-manager-config-connectivity-ubuntu python3-paramiko 
python3-software-properties simple-scan
software-properties-common software-properties-gtk upower
  56 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
  10 not fully installed or removed.
  Need to get 0 B/94,6 MB of archives.
  After this operation, 1.928 kB of additional disk space will be used.
  Do you want to continue? [Y/n] Y
  Extracting templates from packages: 100%
  Preconfiguring packages ...
  Setting up dpkg (1.21.1ubuntu1) ...
  head: error reading 'dpkg': Is a directory
  dpkg: error processing package dpkg (--configure):
   installed dpkg package post-installation script subprocess returned error 
exit status 1
  Errors were encountered while processing:
   dpkg
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  i have to resintall all of the package in cache with `sudo dpkg -i 
/var/cache/apt/archives/*.deb
  `, but the cache sometimes is not the newest packages
  and when i rerun `sudo apt upgrade`, there is still not the newest package

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1960583/+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 1974428] Re: Update to the current 1.36 stable version

2022-05-31 Thread Launchpad Bug Tracker
This bug was fixed in the package network-manager - 1.36.6-0ubuntu1

---
network-manager (1.36.6-0ubuntu1) jammy; urgency=medium

  * New stable version (lp: #1974428)
  * debian/gbp.conf:
- updated the packaging vcs serie
  * d/p/supplicant-add-BIP-interface-capability.patch,
d/p/supplicant-enable-WPA3-transition-mode-only-when-interfac.patch:
- remove, included in the new version

 -- Sebastien Bacher   Fri, 20 May 2022 13:08:51
+0200

** Changed in: network-manager (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

Title:
  Update to the current 1.36 stable version

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Jammy:
  Fix Released

Bug description:
  * Impact

  It's a stable update from upstream, the changes are listed in the NEWS
  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-36/NEWS

  * Test Case

  Since it's an update with several fixes the testing should focus on a
  specific point but rather by validating that the testplan is green,
  https://wiki.ubuntu.com/NetworkManager/DistroTesting

  * Regression potential

  There are fixes around IPv6 handling, VPN connections and the hotspot
  feature, verify that those configurations are still working as
  expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1974428/+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 1969460] Re: software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings

2022-05-31 Thread Launchpad Bug Tracker
This bug was fixed in the package software-properties - 0.99.24

---
software-properties (0.99.24) kinetic; urgency=medium

  * softwareproperties/gtk/SoftwarePropertiesGtk.py:
Don't crash if the driver package does not have a matching modules package
Fixes LP: #1969460

 -- Alberto Milone   Mon, 30 May 2022
16:50:03 +0200

** Changed in: software-properties (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  software-properties-gtk crashed with TypeError in
  on_driver_selection_changed(): Expected a string or a pair of strings

Status in OEM Priority Project:
  New
Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Jammy:
  Fix Committed

Bug description:
  - Impact

  software-properties-gtk hit an exception when dealing some drivers

  - Test Case

  On a Dell XPS 13 9320 enable ppa:oem-solutions-group/intel-ipu6 and
  try to install libcamhal-ipu6ep0 using software-properties-gtk

  https://errors.ubuntu.com/problem/d3c26abd1d80970615ad06cff24972cee3001e57
  should not include reports on the new version

  - Regression potential

  The change make the driver code ignore one extra type of error, it
  shouldn't impact on any of the already working cases. Ensure that
  drivers that were hitting the error correctly install now

  

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Ubuntu 22.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
   software-properties-gtk 0.99.22

  3) What you expected to happen
  No crash when using Additional Drivers with 
ppa:oem-solutions-group/intel-ipu6 on Dell XPS 13 9320
  It can install libcamhal-ipu6ep0 from Additional Drivers without any problem.

  4) What happened instead
  It crashed when selecting libcamhal-ipu6ep0 in Additional Drivers

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1969460/+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 1971621] Re: package libnih-dbus1 1.0.3-6ubuntu2 failed to install/upgrade: package libnih-dbus1:amd64 (1.0.3-12) with field 'Multi-Arch: no' is not co-installable with libnih-db

2022-05-31 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  package libnih-dbus1 1.0.3-6ubuntu2 failed to install/upgrade: package
  libnih-dbus1:amd64 (1.0.3-12) with field 'Multi-Arch: no' is not co-
  installable with libnih-dbus1 which has multiple installed instances

Status in libnih package in Ubuntu:
  Confirmed

Bug description:
  This is a desktop system that has been upgraded from 14.04 -> 16.04 ->
  18.04 -> 20.04.  The error happened during the upgrade process to
  22.04 (command line).  It seems similar to, but not the same as
  #1948346

  ProblemType: Package
  DistroRelease: Ubuntu 21.10
  Package: libnih-dbus1 1.0.3-6ubuntu2
  ProcVersionSignature: Ubuntu 5.4.0-109.123-generic 5.4.178
  Uname: Linux 5.4.0-109-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu71.1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Wed May  4 13:59:53 2022
  DuplicateSignature:
   package:libnih-dbus1:1.0.3-6ubuntu2
   Unpacking libnfsidmap2:amd64 (0.25-6build1) over (0.25-5.1ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-FIA5UV/559-libnih-dbus1_1.0.3-12_amd64.deb (--unpack):
package libnih-dbus1:amd64 (1.0.3-12) with field 'Multi-Arch: no' is not 
co-installable with libnih-dbus1 which has multiple installed instances
  ErrorMessage: package libnih-dbus1:amd64 (1.0.3-12) with field 'Multi-Arch: 
no' is not co-installable with libnih-dbus1 which has multiple installed 
instances
  InstallationDate: Installed on 2014-10-10 (2763 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  Python3Details: /usr/bin/python3.9, Python 3.9.7, python3-minimal, 
3.9.4-1build1
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.18-9
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.20.9ubuntu2
   apt  2.3.9
  SourcePackage: libnih
  Title: package libnih-dbus1 1.0.3-6ubuntu2 failed to install/upgrade: package 
libnih-dbus1:amd64 (1.0.3-12) with field 'Multi-Arch: no' is not co-installable 
with libnih-dbus1 which has multiple installed instances
  UpgradeStatus: Upgraded to impish on 2022-05-04 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnih/+bug/1971621/+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 1973629] [NEW] Wifi hotspot not configured correctly on restart

2022-05-30 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I have configured the hotspot to automatically start at startup. The
hotspot correctly starts on startup, but it appears to be configured
incorrectly. No device connected to it can reach the internet. When
opening the settings, Wifi is indicated to be disabled, even though the
hotspot is running (see screenshot).

The expectation is that the hotpot to be fully functional on startup
meaning every device connected to it can reach the internet.

Currently the issue can be fixed by activating Wifi and then starting a
hotspot, even though the hotspot is already running. The hotspot started
at startup does not have to be shut down before starting a hotspot in
the settings.

All this leads me to believe that somewhere the configuration of Wifi
goes wrong on startup.


Running Ubuntu 22.04

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: dconf-service 0.40.0-3
ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30
Uname: Linux 5.15.0-30-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon May 16 19:59:02 2022
InstallationDate: Installed on 2021-12-08 (159 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
SourcePackage: dconf
UpgradeStatus: Upgraded to jammy on 2022-04-24 (22 days ago)

** Affects: network-manager (Ubuntu)
 Importance: Low
 Status: Incomplete


** Tags: amd64 apport-bug jammy
-- 
Wifi hotspot not configured correctly on restart
https://bugs.launchpad.net/bugs/1973629
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to network-manager 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 1933491] Re: kmod add zstd support

2022-05-30 Thread Launchpad Bug Tracker
This bug was fixed in the package kmod - 27-1ubuntu2.1

---
kmod (27-1ubuntu2.1) focal; urgency=medium

  * Build with zstd compression and testsuite enabled. LP: #1933491

 -- Dimitri John Ledkov   Fri, 28 Jan 2022
14:49:50 +

** Changed in: kmod (Ubuntu Focal)
   Status: Fix Committed => 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:
  Fix Released
Status in kmod source package in Impish:
  Fix Released
Status in kmod source package in Jammy:
  Fix Released
Status in kmod package in Debian:
  New

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 1240336] Re: After release upgrade, the user loses permissions for several basic actions in the system

2022-05-28 Thread Launchpad Bug Tracker
[Expired for policykit-desktop-privileges (Ubuntu) because there has
been no activity for 60 days.]

** Changed in: policykit-desktop-privileges (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  After release upgrade, the user loses permissions for several basic
  actions in the system

Status in gdm3 package in Ubuntu:
  Won't Fix
Status in lightdm package in Ubuntu:
  Expired
Status in lxdm package in Ubuntu:
  Expired
Status in policykit-desktop-privileges package in Ubuntu:
  Expired

Bug description:
  HOW TO REPRODUCE:
  - Upgrade Ubuntu to the next release.

  RESULT:
  - The user looses permissions for several basic actions in the system.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: policykit-desktop-privileges 0.16
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Tue Oct 15 20:20:55 2013
  InstallationDate: Installed on 2013-10-09 (7 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131008)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: policykit-desktop-privileges
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1240336/+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 1240336] Re: After release upgrade, the user loses permissions for several basic actions in the system

2022-05-28 Thread Launchpad Bug Tracker
[Expired for lightdm (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  After release upgrade, the user loses permissions for several basic
  actions in the system

Status in gdm3 package in Ubuntu:
  Won't Fix
Status in lightdm package in Ubuntu:
  Expired
Status in lxdm package in Ubuntu:
  Expired
Status in policykit-desktop-privileges package in Ubuntu:
  Expired

Bug description:
  HOW TO REPRODUCE:
  - Upgrade Ubuntu to the next release.

  RESULT:
  - The user looses permissions for several basic actions in the system.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: policykit-desktop-privileges 0.16
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Tue Oct 15 20:20:55 2013
  InstallationDate: Installed on 2013-10-09 (7 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131008)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: policykit-desktop-privileges
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1240336/+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 1240336] Re: After release upgrade, the user loses permissions for several basic actions in the system

2022-05-28 Thread Launchpad Bug Tracker
[Expired for lxdm (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  After release upgrade, the user loses permissions for several basic
  actions in the system

Status in gdm3 package in Ubuntu:
  Won't Fix
Status in lightdm package in Ubuntu:
  Expired
Status in lxdm package in Ubuntu:
  Expired
Status in policykit-desktop-privileges package in Ubuntu:
  Expired

Bug description:
  HOW TO REPRODUCE:
  - Upgrade Ubuntu to the next release.

  RESULT:
  - The user looses permissions for several basic actions in the system.

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: policykit-desktop-privileges 0.16
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Tue Oct 15 20:20:55 2013
  InstallationDate: Installed on 2013-10-09 (7 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta amd64 (20131008)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: policykit-desktop-privileges
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1240336/+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 827151] Re: Annoying log message "DIGEST-MD5 common mech free"

2022-05-28 Thread Launchpad Bug Tracker
This bug was fixed in the package cyrus-sasl2 - 2.1.28+dfsg-6ubuntu1

---
cyrus-sasl2 (2.1.28+dfsg-6ubuntu1) kinetic; urgency=medium

  * d/p/0033-honor-log_level-option-on-clients-too.patch: honor log
level option on clients (LP: #827151)

 -- Andreas Hasenack   Wed, 25 May 2022 16:41:43
-0300

** Changed in: cyrus-sasl2 (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Annoying log message "DIGEST-MD5 common mech free"

Status in Cyrus-sasl2:
  Fix Released
Status in cyrus-sasl2 package in Ubuntu:
  Fix Released
Status in cyrus-sasl2 source package in Trusty:
  Won't Fix
Status in cyrus-sasl2 source package in Xenial:
  Incomplete
Status in cyrus-sasl2 source package in Yakkety:
  Fix Released
Status in cyrus-sasl2 source package in Focal:
  Triaged
Status in cyrus-sasl2 source package in Impish:
  Triaged
Status in cyrus-sasl2 source package in Jammy:
  Triaged
Status in cyrus-sasl2 package in Debian:
  Fix Released

Bug description:
  I recently updated the libsasl2-modules to 
2.1.24~rc1.dfsg1+cvs2011-05-23-4ubuntu1 in oneiric.
  That triggered the bug also described in Debian here: 
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631932

  The annoying message is logged in auth.log. In my case, it is associated with 
svnserve:
  svnserve: DIGEST-MD5 common mech free

  I'm not exactly sure what action triggers the message, but I can
  investigate more if required.

  $ lsb_release -rd
  Description:Ubuntu oneiric (development branch)
  Release:11.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/cyrus-sasl2/+bug/827151/+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 1971242] [NEW] printing PDF appears always grey, no color

2022-05-28 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF
document. The print appears always b/w regardless color printing was
enabled or not. Printing from LibreOffice produces a color print. This
behavior (bug) is reproducible on three upgraded machines. It would be
nice to have color print back again.

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

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

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


** Tags: bot-comment
-- 
printing PDF appears always grey, no color
https://bugs.launchpad.net/bugs/1971242
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to cups 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 1895762] [NEW] PH-B-500 Headphone makes bluetooth loop

2022-05-28 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Hi there, I am using Ubuntu 18.04.4 LTS(Brazilian Portuguese, so, sorry
if I translated wrong some label) in a Dell Inspiron 15 series 3000 and
I am having some Bluetooth problems.

I always suffer to synchronize my Cadenza PH-B Bluetooth Headphone.
It Shows as PH-B-500 at the bluetooth devices list
What happens is:
1. I turn on the headphone
2. I go to Settings → Bluetooth
3. The Notebook entire bluetooth enters a shutdown reinitialize loop
4. It only stops when I turn off the headphone

But if I:
1. Keep the headphone off
2. go to Settings → Bluetooth
3. Click on the PH-B-500 on the list
4. Turn the headphone on and at the same time click on Conection at the 
PH-B-500 Bluetooth window
it usually starts working fine.
The headphone works perfectly on my Android cell phone so I don’t believe it is 
broken.

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


** Tags: bluetooth bot-comment headphone ph-b-500
-- 
PH-B-500 Headphone makes bluetooth loop
https://bugs.launchpad.net/bugs/1895762
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to bluez 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 1975883] Re: package linux-image-5.15.0-33-generic 5.15.0-33.34 failed to install/upgrade: run-parts: /etc/kernel/postint/d/initramfs-tools exited with return code 1

2022-05-27 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  package linux-image-5.15.0-33-generic 5.15.0-33.34 failed to
  install/upgrade: run-parts: /etc/kernel/postint/d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  During upgrade to ubuntu 22

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-33-generic 5.15.0-33.34
  ProcVersionSignature: Ubuntu 5.4.0-113.127-generic 5.4.181
  Uname: Linux 5.4.0-113-generic x86_64
  AlsaDevices:
   total 0
   crw-rw+ 1 root audio 116,  1 May 26 23:42 seq
   crw-rw+ 1 root audio 116, 33 May 26 23:42 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: pass
  Date: Thu May 26 23:45:41 2022
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2022-03-16 (71 days ago)
  InstallationMedia: Ubuntu-Server 20.04.4 LTS "Focal Fossa" - Release amd64 
(20220223.1)
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 480M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
480M
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  PciMultimedia:
   
  ProcFB: 0 EFI VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-113-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions: grub-pc N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  SourcePackage: initramfs-tools
  Title: package linux-image-5.15.0-33-generic 5.15.0-33.34 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to jammy on 2022-05-26 (0 days ago)
  dmi.board.name: Standard PC (i440FX + PIIX, 1996)
  dmi.board.vendor: QEMU
  dmi.board.version: pc-i440fx-4.1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-4.1
  dmi.modalias: 
dmi:bvn:bvr:bd:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-4.1:rvnQEMU:rnStandardPC(i440FX+PIIX,1996):rvrpc-i440fx-4.1:cvnQEMU:ct1:cvrpc-i440fx-4.1:
  dmi.product.name: Standard PC (i440FX + PIIX, 1996)
  dmi.product.version: pc-i440fx-4.1
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1975883/+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 1965439] Re: applications can no longer launch when called by kdesu

2022-05-27 Thread Launchpad Bug Tracker
This bug was fixed in the package ubuntustudio-default-settings -
22.10.1

---
ubuntustudio-default-settings (22.10.1) kinetic; urgency=medium

  * Revert changes for Jammy for driver manager (LP: #1965439)

 -- Erich Eickmeyer   Fri, 27 May 2022 09:01:47
-0700

** Changed in: ubuntustudio-default-settings (Ubuntu Kinetic)
   Status: Fix Committed => Fix Released

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

Title:
  applications can no longer launch when called by kdesu

Status in kdesu package in Ubuntu:
  Fix Released
Status in kubuntu-settings package in Ubuntu:
  Fix Released
Status in sudo package in Ubuntu:
  Confirmed
Status in ubuntustudio-default-settings package in Ubuntu:
  Fix Released
Status in kdesu source package in Jammy:
  Confirmed
Status in kubuntu-settings source package in Jammy:
  In Progress
Status in sudo source package in Jammy:
  Confirmed
Status in ubuntustudio-default-settings source package in Jammy:
  In Progress
Status in kdesu source package in Kinetic:
  Fix Released
Status in kubuntu-settings source package in Kinetic:
  Fix Released
Status in sudo source package in Kinetic:
  Confirmed
Status in ubuntustudio-default-settings source package in Kinetic:
  Fix Released
Status in kdesu package in Debian:
  New

Bug description:
  See description below. As the driver manager is done inside software-
  properties-qt, it's basically the same bug, but now it's affected by
  something we can't exactly get into the mechanism of: plasma-
  discover's "Software Sources" link.

  Steps to recrate:

  1) Open Plasma-discover
  2) Go to Settings
  3) Under click on "Software Sources"
  4) Attempt to enter password

  Expected: Software properties opens

  Actual: Pkexec keeps asking for password.

  --

  Earlier description:

  The driver manager for both Ubuntu Studio and Kubuntu can no longer
  launch due to some updated security measures in PolicyKit.

  The original behavior was that systemsettings would open
  /usr/bin/ubuntustudio-driver-manager (or /usr/bin/kubuntu-driver-
  manger) via pkexec, which would then open software-settings-qt.
  Unfortunately, the new behavior does not act correctly to pkexec and
  pkexec does not see the user as available in the sudoers file.

  The only way around this was to pass "export DISPLAY=:0" inside the
  appropriate driver manager executable with the command "sudo software-
  properties-qt". The KCM itself needs to execute the driver-manager via
  xterm, which then prompts for a password. It's ugly, but it works.

  I will attach a debdiff for the kubuntu-settings package.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntustudio-default-settings 22.04.19 [modified: 
usr/share/sddm/themes/ubuntustudio/theme.conf]
  ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19
  Uname: Linux 5.15.0-22-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Thu Mar 17 12:19:44 2022
  InstallationDate: Installed on 2021-03-20 (361 days ago)
  InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 
(20210320)
  PackageArchitecture: all
  SourcePackage: ubuntustudio-default-settings
  UpgradeStatus: Upgraded to jammy on 2021-11-07 (130 days ago)
  modified.conffile..etc.skel..local.share.konsole.Profile: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kdesu/+bug/1965439/+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 1975875] [NEW] libgail-3-0 install blocked by "=" dependency

2022-05-27 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

The libgtk dependency in libgail-3-0 is set to = *not* >= 3.24.18.

Since libgtk has moved on to 3.24.20 the install of libgail is now
blocked, which of course blocks everything that depends on it, Nemo in
my case but I'm sure there are many others as well.

Using Ubuntu 20.04 LTS with all current updates.

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


** Tags: bot-comment
-- 
libgail-3-0 install blocked by "=" dependency
https://bugs.launchpad.net/bugs/1975875
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to gtk+3.0 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 1972055] Re: [20XXS62S00, Realtek ALC287, Speaker, Internal] Underruns, dropouts or crackling sound

2022-05-27 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: alsa-driver (Ubuntu)
   Status: New => Confirmed

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

Title:
  [20XXS62S00, Realtek ALC287, Speaker, Internal] Underruns, dropouts or
  crackling sound

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  After upgrading Carbon X1 gen 9 to Ubuntu 22.04 (from 20.04), there
  appeared strange problem with speaker sound in video conferences
  (Zoom) and also with Chrome (for example YouTube & Preply).

  The problem is as following: the speaker sound level is reduced when
  somebody speaks after a gap of silence, then the sound level is
  quickly increased to normal level. This creates the very strange
  fluctuating up/down sound level which when sound level is low at the
  start of each sentence.

  This problem was not there with Ubuntu 20.04 on the same laptop. This
  problem is also not presented when using Zoom with Windows 11 on the
  same machine.

  Thank you for your consideration.

  Best regards, Rustem

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rustem 1576 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  7 11:24:53 2022
  InstallationDate: Installed on 2022-04-23 (13 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp 
successful
  Symptom_Card: Tiger Lake-LP Smart Sound Technology Audio Controller - 
sof-hda-dsp
  Symptom_Jack: Speaker, Internal
  Symptom_PulseAudioLog: May 07 11:15:06 rox1 pulseaudio[1002]: After module 
unload, module 'module-null-sink' was still loaded!
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [20XXS62S00, Realtek ALC287, Speaker, Internal] Underruns, dropouts or 
crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2021
  dmi.bios.release: 1.51
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N32ET75W (1.51 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20XXS62S00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.32
  dmi.modalias: 
dmi:bvnLENOVO:bvrN32ET75W(1.51):bd12/02/2021:br1.51:efr1.32:svnLENOVO:pn20XXS62S00:pvrThinkPadX1CarbonGen9:rvnLENOVO:rn20XXS62S00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20XX_BU_Think_FM_ThinkPadX1CarbonGen9:
  dmi.product.family: ThinkPad X1 Carbon Gen 9
  dmi.product.name: 20XXS62S00
  dmi.product.sku: LENOVO_MT_20XX_BU_Think_FM_ThinkPad X1 Carbon Gen 9
  dmi.product.version: ThinkPad X1 Carbon Gen 9
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1972055/+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 1965439] Re: applications can no longer launch when called by kdesu

2022-05-26 Thread Launchpad Bug Tracker
This bug was fixed in the package kdesu - 5.94.0-0ubuntu2

---
kdesu (5.94.0-0ubuntu2) kinetic; urgency=medium

  * Disable use of sudo 'Defaults use_pty' for kdesu. (LP: #1965439)

 -- Rik Mills   Thu, 26 May 2022 15:13:22 +0100

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

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

Title:
  applications can no longer launch when called by kdesu

Status in kdesu package in Ubuntu:
  Fix Released
Status in kubuntu-settings package in Ubuntu:
  In Progress
Status in sudo package in Ubuntu:
  Confirmed
Status in ubuntustudio-default-settings package in Ubuntu:
  In Progress
Status in kdesu source package in Jammy:
  Confirmed
Status in kubuntu-settings source package in Jammy:
  In Progress
Status in sudo source package in Jammy:
  Confirmed
Status in ubuntustudio-default-settings source package in Jammy:
  In Progress
Status in kdesu source package in Kinetic:
  Fix Released
Status in kubuntu-settings source package in Kinetic:
  In Progress
Status in sudo source package in Kinetic:
  Confirmed
Status in ubuntustudio-default-settings source package in Kinetic:
  In Progress
Status in kdesu package in Debian:
  Unknown

Bug description:
  See description below. As the driver manager is done inside software-
  properties-qt, it's basically the same bug, but now it's affected by
  something we can't exactly get into the mechanism of: plasma-
  discover's "Software Sources" link.

  Steps to recrate:

  1) Open Plasma-discover
  2) Go to Settings
  3) Under click on "Software Sources"
  4) Attempt to enter password

  Expected: Software properties opens

  Actual: Pkexec keeps asking for password.

  --

  Earlier description:

  The driver manager for both Ubuntu Studio and Kubuntu can no longer
  launch due to some updated security measures in PolicyKit.

  The original behavior was that systemsettings would open
  /usr/bin/ubuntustudio-driver-manager (or /usr/bin/kubuntu-driver-
  manger) via pkexec, which would then open software-settings-qt.
  Unfortunately, the new behavior does not act correctly to pkexec and
  pkexec does not see the user as available in the sudoers file.

  The only way around this was to pass "export DISPLAY=:0" inside the
  appropriate driver manager executable with the command "sudo software-
  properties-qt". The KCM itself needs to execute the driver-manager via
  xterm, which then prompts for a password. It's ugly, but it works.

  I will attach a debdiff for the kubuntu-settings package.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubuntustudio-default-settings 22.04.19 [modified: 
usr/share/sddm/themes/ubuntustudio/theme.conf]
  ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19
  Uname: Linux 5.15.0-22-lowlatency x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Thu Mar 17 12:19:44 2022
  InstallationDate: Installed on 2021-03-20 (361 days ago)
  InstallationMedia: Ubuntu-Studio 21.04 "Hirsute Hippo" - Alpha amd64 
(20210320)
  PackageArchitecture: all
  SourcePackage: ubuntustudio-default-settings
  UpgradeStatus: Upgraded to jammy on 2021-11-07 (130 days ago)
  modified.conffile..etc.skel..local.share.konsole.Profile: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kdesu/+bug/1965439/+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 827151] Re: Annoying log message "DIGEST-MD5 common mech free"

2022-05-26 Thread Launchpad Bug Tracker
** Merge proposal linked:
   
https://code.launchpad.net/~ahasenack/ubuntu/+source/cyrus-sasl2/+git/cyrus-sasl2/+merge/423455

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

Title:
  Annoying log message "DIGEST-MD5 common mech free"

Status in Cyrus-sasl2:
  Fix Released
Status in cyrus-sasl2 package in Ubuntu:
  Triaged
Status in cyrus-sasl2 source package in Trusty:
  Won't Fix
Status in cyrus-sasl2 source package in Xenial:
  Incomplete
Status in cyrus-sasl2 source package in Yakkety:
  Fix Released
Status in cyrus-sasl2 source package in Focal:
  Triaged
Status in cyrus-sasl2 source package in Impish:
  Triaged
Status in cyrus-sasl2 source package in Jammy:
  Triaged
Status in cyrus-sasl2 package in Debian:
  Fix Released

Bug description:
  I recently updated the libsasl2-modules to 
2.1.24~rc1.dfsg1+cvs2011-05-23-4ubuntu1 in oneiric.
  That triggered the bug also described in Debian here: 
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631932

  The annoying message is logged in auth.log. In my case, it is associated with 
svnserve:
  svnserve: DIGEST-MD5 common mech free

  I'm not exactly sure what action triggers the message, but I can
  investigate more if required.

  $ lsb_release -rd
  Description:Ubuntu oneiric (development branch)
  Release:11.10

To manage notifications about this bug go to:
https://bugs.launchpad.net/cyrus-sasl2/+bug/827151/+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 1947588] Re: Infinite Loop in OpenSSL s_server

2022-05-25 Thread Launchpad Bug Tracker
** Merge proposal linked:
   
https://code.launchpad.net/~schopin/ubuntu/+source/openssl/+git/openssl/+merge/423153

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

Title:
  Infinite Loop in OpenSSL s_server

Status in openssl package in Ubuntu:
  Confirmed
Status in openssl source package in Focal:
  Confirmed
Status in openssl source package in Impish:
  Confirmed
Status in openssl source package in Jammy:
  Confirmed

Bug description:
  Launching openssl s_server as follows:

  $ openssl s_server -nocert -psk 01020304 -dtls1

  And using openssl s_client to connect to it like this:

  $ openssl s_client -dtls1 -psk 01020304

  Results in s_server entering an infinite loop:

  
  Using default temp DH parameters
  ACCEPT
  ERROR
  140247926990208:error:141FC044:SSL routines:tls_setup_handshake:internal 
error:../ssl/statem/statem_lib.c:109:
  ERROR
  140247926990208:error:141FC044:SSL routines:tls_setup_handshake:internal 
error:../ssl/statem/statem_lib.c:109:
  ERROR

  ...and so on...

  I have confirmed that upstream OpenSSL does not have this issue in a
  default build of 1.1.1j or 1.1.1k. Upstream 1.1.1l has a different bug
  with these commands (https://github.com/openssl/openssl/issues/16707)
  and it was while working on the fix for that issue
  (https://github.com/openssl/openssl/pull/16838) that I noticed this
  problem in the Ubuntu packages.

  $ lsb_release -rd
  Description:  Ubuntu 21.04
  Release:  21.04

  $ apt-cache policy openssl
  openssl:
Installed: 1.1.1j-1ubuntu3.5
Candidate: 1.1.1j-1ubuntu3.5
Version table:
   *** 1.1.1j-1ubuntu3.5 500
  500 http://gb.archive.ubuntu.com/ubuntu hirsute-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu hirsute-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.1.1j-1ubuntu3 500
  500 http://gb.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages

  $ openssl version -a
  OpenSSL 1.1.1j  16 Feb 2021
  built on: Mon Aug 23 17:02:39 2021 UTC
  platform: debian-amd64
  options:  bn(64,64) rc4(16x,int) des(int) blowfish(ptr) 
  compiler: gcc -fPIC -pthread -m64 -Wa,--noexecstack -Wall -Wa,--noexecstack 
-g -O2 -ffile-prefix-map=/build/openssl-5U8yxE/openssl-1.1.1j=. -flto=auto 
-ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security 
-DOPENSSL_TLS_SECURITY_LEVEL=2 -DOPENSSL_USE_NODELETE -DL_ENDIAN -DOPENSSL_PIC 
-DOPENSSL_CPUID_OBJ -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT 
-DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM 
-DSHA512_ASM -DKECCAK1600_ASM -DRC4_ASM -DMD5_ASM -DAESNI_ASM -DVPAES_ASM 
-DGHASH_ASM -DECP_NISTZ256_ASM -DX25519_ASM -DPOLY1305_ASM -DNDEBUG -Wdate-time 
-D_FORTIFY_SOURCE=2
  OPENSSLDIR: "/usr/lib/ssl"
  ENGINESDIR: "/usr/lib/x86_64-linux-gnu/engines-1.1"
  Seeding source: os-specific

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1947588/+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 1972056] Re: [openssl3] please sync openssl.cnf to ease changing security level

2022-05-25 Thread Launchpad Bug Tracker
** Merge proposal linked:
   
https://code.launchpad.net/~schopin/ubuntu/+source/openssl/+git/openssl/+merge/423153

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

Title:
  [openssl3] please sync openssl.cnf to ease changing security level

Status in openssl package in Ubuntu:
  Confirmed
Status in openssl source package in Jammy:
  Confirmed
Status in openssl source package in Kinetic:
  Confirmed
Status in openssl package in Debian:
  Fix Released

Bug description:
  openssl.cnf as provided misses some directive, which make it a bit
  difficult to change security level, which since openssl 3 disables
  SHA1 signatures.

  See also this Debian bug https://bugs.debian.org/cgi-
  bin/bugreport.cgi?bug=1010360 and the committed fix:
  
https://salsa.debian.org/debian/openssl/-/commit/b507914c40270e32cde6afcc8af93707c225e7f4

  Can you please sync this change in Ubuntu openssl?

  This way one should just add a single directive to change the security
  level.

  Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1972056/+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 1975675] [NEW] GUI problem from {Online Accounts} Google Microsoft and {Ubuntu Desktop Guide}

2022-05-25 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

raspberry pi 4 (8GB memory, USB SSD boot) ubuntu 64 with 2 monitors


Description:Ubuntu 22.04 LTS
Release:22.04


Seems like the GUI for {Online Accounts} Google Microsoft and {Ubuntu Desktop 
Guide} can't render themselves correctly. Meanwhile, the Firefox can play 
YouTube on 2 monitors without any problem.
Please refer to the attached snapshot.

apt-cache policy 
Package files:
 100 /var/lib/dpkg/status
 release a=now
 500 http://ports.ubuntu.com/ubuntu-ports jammy-security/universe arm64 Packages
 release 
v=22.04,o=Ubuntu,a=jammy-security,n=jammy,l=Ubuntu,c=universe,b=arm64
 origin ports.ubuntu.com
 500 http://ports.ubuntu.com/ubuntu-ports jammy-security/restricted arm64 
Packages
 release 
v=22.04,o=Ubuntu,a=jammy-security,n=jammy,l=Ubuntu,c=restricted,b=arm64
 origin ports.ubuntu.com
 500 http://ports.ubuntu.com/ubuntu-ports jammy-security/main arm64 Packages
 release v=22.04,o=Ubuntu,a=jammy-security,n=jammy,l=Ubuntu,c=main,b=arm64
 origin ports.ubuntu.com
 100 http://ports.ubuntu.com/ubuntu-ports jammy-backports/universe arm64 
Packages
 release 
v=22.04,o=Ubuntu,a=jammy-backports,n=jammy,l=Ubuntu,c=universe,b=arm64
 origin ports.ubuntu.com
 500 http://ports.ubuntu.com/ubuntu-ports jammy-updates/universe arm64 Packages
 release 
v=22.04,o=Ubuntu,a=jammy-updates,n=jammy,l=Ubuntu,c=universe,b=arm64
 origin ports.ubuntu.com
 500 http://ports.ubuntu.com/ubuntu-ports jammy-updates/restricted arm64 
Packages
 release 
v=22.04,o=Ubuntu,a=jammy-updates,n=jammy,l=Ubuntu,c=restricted,b=arm64
 origin ports.ubuntu.com
 500 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main arm64 Packages
 release v=22.04,o=Ubuntu,a=jammy-updates,n=jammy,l=Ubuntu,c=main,b=arm64
 origin ports.ubuntu.com
 500 http://ports.ubuntu.com/ubuntu-ports jammy/multiverse arm64 Packages
 release v=22.04,o=Ubuntu,a=jammy,n=jammy,l=Ubuntu,c=multiverse,b=arm64
 origin ports.ubuntu.com
 500 http://ports.ubuntu.com/ubuntu-ports jammy/universe arm64 Packages
 release v=22.04,o=Ubuntu,a=jammy,n=jammy,l=Ubuntu,c=universe,b=arm64
 origin ports.ubuntu.com
 500 http://ports.ubuntu.com/ubuntu-ports jammy/restricted arm64 Packages
 release v=22.04,o=Ubuntu,a=jammy,n=jammy,l=Ubuntu,c=restricted,b=arm64
 origin ports.ubuntu.com
 500 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages
 release v=22.04,o=Ubuntu,a=jammy,n=jammy,l=Ubuntu,c=main,b=arm64
 origin ports.ubuntu.com
Pinned packages:
 librados2 -> 17.2.0-0ubuntu0.22.04.1 with priority 1
 crimson-osd -> 17.2.0-0ubuntu0.22.04.1 with priority 1
 ec2-instance-connect -> 1.1.14-0ubuntu1.1 with priority 1
 python3-etcd3gw -> 0.2.5-1ubuntu1.22.04.1 with priority 1
 budgie-control-center-data -> 1.0.1-2ubuntu2 with priority 1
 xdg-desktop-portal-tests -> 1.14.3-0ubuntu2.22.04.1 with priority 1
 budgie-desktop -> 10.6.1-1ubuntu1~22.04 with priority 1
 python-etcd3gw-doc -> 0.2.5-1ubuntu1.22.04.1 with priority 1
 ceph-volume -> 17.2.0-0ubuntu0.22.04.1 with priority 1
 evolution-dev -> 3.44.1-0ubuntu1 with priority 1
 libbudgietheme0 -> 10.6.1-1ubuntu1~22.04 with priority 1
 rbd-fuse -> 17.2.0-0ubuntu0.22.04.1 with priority 1
 ceph-mgr-modules-core -> 17.2.0-0ubuntu0.22.04.1 with priority 1
 libgtk-4-common -> 4.6.3+ds1-0ubuntu1 with priority 1
 ceph-grafana-dashboards -> 17.2.0-0ubuntu0.22.04.1 with priority 1
 gir1.2-clutter-gst-3.0 -> 3.0.27-2ubuntu1 with priority 1
 libgail-3-dev -> 3.24.33-1ubuntu2 with priority 1
 libgail-3-doc -> 3.24.33-1ubuntu2 with priority 1
 ceph-resource-agents -> 17.2.0-0ubuntu0.22.04.1 with priority 1
 ceph-base -> 17.2.0-0ubuntu0.22.04.1 with priority 1
 libsqlite3-mod-ceph-dev -> 17.2.0-0ubuntu0.22.04.1 with priority 1
 libjson-c-dev -> 0.15-3~ubuntu1.22.04.1 with priority 1
 libjson-c-doc -> 0.15-3~ubuntu1.22.04.1 with priority 1
 xdg-desktop-portal-dev -> 1.14.3-0ubuntu2.22.04.1 with priority 1
 gstreamer1.0-clutter-3.0 -> 3.0.27-2ubuntu1 with priority 1
 python3-ceph-common -> 17.2.0-0ubuntu0.22.04.1 with priority 1
 librbd1 -> 17.2.0-0ubuntu0.22.04.1 with priority 1
 gir1.2-budgie-1.0 -> 10.6.1-1ubuntu1~22.04 with priority 1
 libraven0 -> 10.6.1-1ubuntu1~22.04 with priority 1
 librgw2 -> 17.2.0-0ubuntu0.22.04.1 with priority 1
 libusb-1.0-0-dev -> 2:1.0.25-1ubuntu2 with priority 1
 libclutter-gst-3.0-dev -> 3.0.27-2ubuntu1 with priority 1
 libclutter-gst-3.0-doc -> 3.0.27-2ubuntu1 with priority 1
 ceph-mgr-cephadm -> 17.2.0-0ubuntu0.22.04.1 with priority 1
 libcephfs-dev -> 17.2.0-0ubuntu0.22.04.1 with priority 1
 budgie-control-center -> 1.0.1-2ubuntu2 with priority 1
 ceph-common -> 17.2.0-0ubuntu0.22.04.1 with priority 1
 libusb-1.0-doc -> 2:1.0.25-1ubuntu2 with priority 1
 libcephfs-jni -> 17.2.0-0ubuntu0.22.04.1 with priority 1
 evolution-plugins 

[Touch-packages] [Bug 1961859] Re: When we install ModemManager1.16.6 and others, this will lead to ubuntu can not enter into GNOME UI.

2022-05-24 Thread Launchpad Bug Tracker
[Expired for modemmanager (Ubuntu) because there has been no activity
for 60 days.]

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

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

Title:
  When we install ModemManager1.16.6 and others, this will lead to
  ubuntu can not enter into GNOME UI.

Status in modemmanager package in Ubuntu:
  Expired

Bug description:
  1. We use sourcecode to install ModemManger1.16.6
  2. Ubuntu can not enter UI.
  3. We capture log and picture and add these on the attachment.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1961859/+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 1892825] Re: update-locale not perform correctly sanity checks

2022-05-24 Thread Launchpad Bug Tracker
This bug was fixed in the package glibc - 2.27-3ubuntu1.6

---
glibc (2.27-3ubuntu1.6) bionic; urgency=medium

  [ Gunnar Hjalmarsson ]
  * d/local/usr_sbin/update-locale: improve sanity checks. (LP: #1892825)

  [ Aurelien Jarno ]
  * debian/debhelper.in/libc.preinst: drop the check for kernel release
> 255 now that glibc and preinstall script are fixed. (LP: #1962225)

 -- Michael Hudson-Doyle   Tue, 03 May 2022
22:19:39 +1200

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

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

Title:
  update-locale not perform correctly sanity checks

Status in glibc package in Ubuntu:
  Fix Released
Status in pam package in Ubuntu:
  New
Status in glibc source package in Bionic:
  Fix Released
Status in pam source package in Bionic:
  New
Status in glibc source package in Focal:
  Fix Released
Status in pam source package in Focal:
  New
Status in glibc source package in Hirsute:
  Won't Fix
Status in pam source package in Hirsute:
  New
Status in glibc source package in Impish:
  New
Status in pam source package in Impish:
  New

Bug description:
  [impact]
  A simple typo using the update-locale script can render a system inoperable 
without booting into single user mode or similar:

  $ sudo update-locale LANGUAGE = en_US.UTF-8
  $ sudo -s
  sudo: pam_open_session: Bad item passed to pam_*_item()
  sudo: policy plugin failed session initialization

  [test case]
  $ cp /etc/default/locale /tmp/locale
  $ update-locale --locale-file /tmp/locale LANGUAGE = en_US.UTF-8

  "diff -u /etc/default/locale /tmp/locale" should be empty.

  $ update-locale --locale-file /tmp/locale LANGUAGE=en_US.UTF-8

  The LANGUAGE=en_US.UTF-8 line should have been replaced by
  LANGUAGE=en_GB.UTF-8.

  $ update-locale --locale-file /tmp/locale LANGUAGE

  The LANGUAGE setting is now commented out.

  [regression potential]
  Apart from the general concerns about a glibc rebuild, this is a simple 
change to a simple script. Performing the test as in the test case section is 
enough to ensure it still works.

  [original description]
  By passing wrong input as following:
   sudo update-locale LANGUAGE = en_US.UTF-8
  result is:
  ...
  #LANGUAGE=en
  =

  This "equal" sign that was added makes system completely
  unusable(can't run sudo anymore):

  bentzy@bentzy-nb:~$ sudo vim /etc/default/locale
  sudo: pam_open_session: Bad item passed to pam_*_item()
  sudo: policy plugin failed session initialization

  Fixed it booting from installation disk and fixing corrupted
  /etc/default/locale

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: locales 2.31-0ubuntu9
  Uname: Linux 5.5.4-050504-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.6
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: KDE
  Date: Tue Aug 25 09:36:03 2020
  InstallationDate: Installed on 2020-08-17 (7 days ago)
  InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  SourcePackage: glibc
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1892825/+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 1974250] Re: ~/.pam_environment gets created as owned by root

2022-05-24 Thread Launchpad Bug Tracker
This bug was fixed in the package accountsservice - 22.07.5-2ubuntu2

---
accountsservice (22.07.5-2ubuntu2) kinetic; urgency=medium

  [ Marc Deslauriers ]
  * SECURITY UPDATE: accountsservice incorrect privilege dropping
(LP: #1974250)
- debian/patches/0009-language-tools.patch: updated to not reset
  effective uid, and migrate root-owned .pam_environment file.
- This change was originally known as CVE-2020-16126 and got reverted
  by mistake in 0.6.55-3ubuntu1.
- CVE-2022-1804
  * Fix FTBFS with a newer python-dbusmock package:
- debian/patches/adduser_invocation.patch: fix invocation of AddUser in
  tests/dbusmock/accounts_service.py.
- debian/patches/setlocked_signature.patch: fix the signature for the
  SetLocked call in tests/dbusmock/accounts_service.py.

 -- Gunnar Hjalmarsson   Tue, 24 May 2022 19:53:07
+0200

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

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

Title:
  ~/.pam_environment gets created as owned by root

Status in accountsservice package in Ubuntu:
  Fix Released
Status in accountsservice source package in Jammy:
  Fix Released
Status in accountsservice source package in Kinetic:
  Fix Released

Bug description:
  Something has happened lately with accountsservice, which makes it act
  as root instead of the current user when creating ~/.pam_environment.
  The very old bug #904395 comes to mind, and this smells a security
  issue.

  The function which is supposed to prevent this behavior is here:

  https://salsa.debian.org/freedesktop-
  team/accountsservice/-/blob/ubuntu/debian/patches/0010-set-
  language.patch#L75

  Haven't investigated further yet.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1974250/+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 1974230] Re: Negative cache results from dnsmasq do not include SOA as required in RFC2308

2022-05-24 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Negative cache results from dnsmasq do not include SOA as required in
  RFC2308

Status in dnsmasq package in Ubuntu:
  Confirmed

Bug description:
  RFC2308 states:
  6 - Negative answers from the cache

 When a server, in answering a query, encounters a cached negative
 response it MUST add the cached SOA record to the authority section
 of the response with the TTL decremented by the amount of time it was
 stored in the cache.  This allows the NXDOMAIN / NODATA response to
 time out correctly.

  The effect is that the negative cache results returned by dnsmasq
  cannot be cached by other resolvers such as systemd-resolved.

  A good example of why this is a problem:
  Two clients with systemd-resolved send DNS queries to dnsmasq for the same 
record
  The first one makes a query and gets NXDOMAIN with SOA. 
  This results in systemd-resolved caching the negative result.

  The second client makes a query and gets NODATA without the SOA. 
  This results in systemd-resolved not caching the negative result.

  Consider a domain name that only has an A record published.
  When connecting to that domain a lookup happens for the  and A record.
  One can end up in a situation where systemd-resolved has the A record cached 
locally, but it still goes out to the network to perform the  lookup only 
to get the same negative cache result that is missing the SOA

  I see this behavior in 18.04 and 22.04

  
  First query to dnsmasq can be cached:
  dig @10.0.1.21 a.google.com

  ; <<>> DiG 9.16.1-Ubuntu <<>> @10.0.1.21 a.google.com
  ; (1 server found)
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 3107
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 512
  ;; QUESTION SECTION:
  ;a.google.com.  IN  A

  ;; AUTHORITY SECTION:
  google.com. 60  IN  SOA ns1.google.com. 
dns-admin.google.com. 449437361 900 900 1800 60

  ;; Query time: 15 msec
  ;; SERVER: 10.0.1.21#53(10.0.1.21)
  ;; WHEN: Thu May 19 15:00:12 EDT 2022
  ;; MSG SIZE  rcvd: 91

  
  Cached response from dnsmasq cannot be cached:
  dig @10.0.1.21 a.google.com

  ; <<>> DiG 9.16.1-Ubuntu <<>> @10.0.1.21 a.google.com
  ; (1 server found)
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 61408
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 4096
  ;; QUESTION SECTION:
  ;a.google.com.  IN  A

  ;; Query time: 0 msec
  ;; SERVER: 10.0.1.21#53(10.0.1.21)
  ;; WHEN: Thu May 19 15:00:13 EDT 2022
  ;; MSG SIZE  rcvd: 41

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1974230/+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 1972721] Re: Include gtk3 changes needed for mutter 42.1

2022-05-24 Thread Launchpad Bug Tracker
This bug was fixed in the package gtk+3.0 - 3.24.33-1ubuntu2

---
gtk+3.0 (3.24.33-1ubuntu2) jammy; urgency=medium

  * Cherry-pick gtk-3-24 commits needed for mutter 42.1 (LP: #1972721)

 -- Jeremy Bicha   Mon, 09 May 2022 16:15:04 -0400

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

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

Title:
  Include gtk3 changes needed for mutter 42.1

Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Jammy:
  Fix Released

Bug description:
  Impact
  --
  We need to update gtk3 before updating mutter to 42.1. Otherwise, in gtk3 
apps like gedit, it's not possible to scroll past the cursor position.

  The mutter issue with more details is
  https://gitlab.gnome.org/GNOME/mutter/-/issues/2261

  We need to update mutter 42.1 since it includes a lot of bug fixes.

  GNOME Shell 42.1 (with the corresponding changes to mutter, gtk3 and
  gtk4) will better comply with the Wayland specifications.

  The gtk4 bug is LP: #1972722

  Test Case
  -
  Install the updated gtk3 packages.
  Use gedit to open a long text file.
  Scroll down past the page break.
  The document should scroll normally.

  What Could Go Wrong
  ---
  Ideally, GNOME would have done a new GTK3 release for this issue. They will 
eventually, but it seems better for Ubuntu to be proactive and not further 
delay the mutter/gnome-shell 42.1 releases.

  These commits are cherry-picks from the stable branch
  https://gitlab.gnome.org/GNOME/gtk/-/commits/gtk-3-24/

  NOTE
  
  To avoid a temporary mismatch related to phased updates, we want this update 
to be 100% phased before releasing mutter 42.1 to jammy-updates.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1972721/+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 1973270] Re: json-c please mark package as multiarch

2022-05-24 Thread Launchpad Bug Tracker
This bug was fixed in the package json-c - 0.15-3~ubuntu1.22.04.1

---
json-c (0.15-3~ubuntu1.22.04.1) jammy; urgency=medium

  * SRU to Ubuntu 22.04.1 (LP: #1973270)

json-c (0.15-3) unstable; urgency=medium

  * Mark dev package as M-A: same (Closes: #1009805)
- thanks Tomeu Vizoso for the hint.

 -- Gianfranco Costamagna   Fri, 13 May 2022
09:27:59 +0200

** Changed in: json-c (Ubuntu Jammy)
   Status: Fix Committed => Fix Released

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

Title:
  json-c please mark package as multiarch

Status in json-c package in Ubuntu:
  Fix Released
Status in json-c source package in Jammy:
  Fix Released
Status in json-c source package in Kinetic:
  Fix Released

Bug description:

  [Impact]

  People using multi-arch to build for different architectures

  [Test Plan]

   * Install json-c on M-A environment

  [Where problems could occur]

  * Specially now that we don't have anymore real i386 env

  [Other Info]
   
   json-c (0.15-3) unstable; urgency=medium
 * Mark dev package as M-A: same (Closes: #1009805)
   - thanks Tomeu Vizoso for the hint.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/json-c/+bug/1973270/+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 1975557] [NEW] blank screen does not turn off display backlight

2022-05-24 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I updated a system from 21.10 to 22.04 and noticed that when the screen
is blanked by no keyboard or mouse activity that the backlight in the
VGA monitor is still on.  The "settings->Displays" has "Unknown Display"
which I assume means the system does not know what commands to send to
the monitor to shut it off.  I booted a live DVD of 21.10 and the
settings has the VGA display as 'AOC 22" ' which is correct and the
screen blanking works correctly.  So it seems that the definition for
the AOC displays have been removed from 22.04.

This behavior is different on Ubuntu 21.10, the VGA display is blank and the 
backlight is off.  A minor nit is on 21.10 the "settings->Displays" shows the 
VGA display manufacture name, on 22.04 the
VGA display manufacture name is "Unknown Display".

I have discovered that the settings have the following options

"settings->Power->Screen Blank" with a time value to be selected and the
following text on the next line "Turns the screen off after a period of
inactivity"

"settings->Privacy->Screen->Blank Screen Display" with a time value to be
selected and the following text on the next line "Period of inactivity after
which the screen will go blank"

The two options have different actions but seem to be connected because
changing the time on one changes the time on the other.

My guess is that the update changed the action for Ubuntu 22.04.  I
would like the 21.10 behavior, that is to turn off the VGA display not
just blank the display when selecting the "settings->Power->Screen
Blank" for 22.04.

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


** Tags: bot-comment
-- 
blank screen does not turn off display backlight
https://bugs.launchpad.net/bugs/1975557
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg 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 1974046] Re: Please merge wget 1.21.3 (main) from Debian unstable (main)

2022-05-24 Thread Launchpad Bug Tracker
This bug was fixed in the package wget - 1.21.3-1ubuntu1

---
wget (1.21.3-1ubuntu1) kinetic; urgency=low

  * Merge from Debian unstable. Remaining changes: (LP: #1974046)
- d/control: Don't Build-Depend on libgnutls28-dev, only on libssl-dev.
- d/rules: Pass --with-ssl=openssl

wget (1.21.3-1) unstable; urgency=medium

  * new upstream from 2022-02-26
* remove now included patch from 1.21.2-2
  ssl_Removesupriousprintstatements_wget61125.patch

 -- Nathan Pratta Teodosio   Wed, 18 May
2022 14:23:07 -0300

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

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

Title:
  Please merge wget 1.21.3 (main) from Debian unstable (main)

Status in wget package in Ubuntu:
  Fix Released

Bug description:
  Please merge wget 1.21.3 from Debian stable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wget/+bug/1974046/+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 1974456] Re: regression: apt.postint fails if never previously configured

2022-05-23 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  regression: apt.postint fails if never previously configured

Status in apt package in Ubuntu:
  Confirmed
Status in apt source package in Bionic:
  Confirmed
Status in apt source package in Focal:
  Confirmed

Bug description:
  #1968154 removed `/etc/kernel/postinst.d/apt-auto-removal` in this patch:
  
https://git.launchpad.net/ubuntu/+source/apt/commit/?id=f9d2d993687c0d5223c241956ef6a0aabcf15bf0

  ...but `apt.postinst` still tries to run it:

  # create kernel autoremoval blacklist on update
  if dpkg --compare-versions "$2" lt 0.9.9.3; then
  /etc/kernel/postinst.d/apt-auto-removal
  fi

  If I understand correctly, "$2" is the most-recently-configured-
  version, and if it's empty `dpkg --compare-versions lt` will evaluate
  to true.

  This fails when I'm building a focal (20.04) userspace from scratch:

  $ dpkg --configure -a
  [...]
  Setting up apt (2.0.8) ...
  /var/lib/dpkg/info/apt.postinst: 65: 
/etc/kernel/postinst.d/apt-auto-removal: not found
  dpkg: error processing package apt (--configure):
   installed apt package post-installation script subprocess returned error 
exit status 127

  It works with apt 2.0.6.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1974456/+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 1974456] Re: regression: apt.postint fails if never previously configured

2022-05-23 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  regression: apt.postint fails if never previously configured

Status in apt package in Ubuntu:
  Confirmed
Status in apt source package in Bionic:
  Confirmed
Status in apt source package in Focal:
  Confirmed

Bug description:
  #1968154 removed `/etc/kernel/postinst.d/apt-auto-removal` in this patch:
  
https://git.launchpad.net/ubuntu/+source/apt/commit/?id=f9d2d993687c0d5223c241956ef6a0aabcf15bf0

  ...but `apt.postinst` still tries to run it:

  # create kernel autoremoval blacklist on update
  if dpkg --compare-versions "$2" lt 0.9.9.3; then
  /etc/kernel/postinst.d/apt-auto-removal
  fi

  If I understand correctly, "$2" is the most-recently-configured-
  version, and if it's empty `dpkg --compare-versions lt` will evaluate
  to true.

  This fails when I'm building a focal (20.04) userspace from scratch:

  $ dpkg --configure -a
  [...]
  Setting up apt (2.0.8) ...
  /var/lib/dpkg/info/apt.postinst: 65: 
/etc/kernel/postinst.d/apt-auto-removal: not found
  dpkg: error processing package apt (--configure):
   installed apt package post-installation script subprocess returned error 
exit status 127

  It works with apt 2.0.6.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1974456/+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


  1   2   3   4   5   6   7   8   9   10   >