date:20220608

If the OBS issue is related to this then it will be in some common
component like a library or the shell. We don't need to add a task for
each app. This problem is too low level for apps to have any control
over it.

** No longer affects: obs-studio (Ubuntu)

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

Title:
  gnome-extensions-app fails to start [Error reading events from
  display: Protocol error]

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  $ dpkg-query -W gnome-shell-extension-prefs
  gnome-shell-extension-prefs   42~beta-1ubuntu3
  $ gnome-extensions-app
  Gdk-Message: 17:54:19.697: Error reading events from display: Protocol error

  Caveat: I currently have a mix of packages from jammy-release and
  jammy-proposed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965563/+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 1978057] Re: [SRU] Support WWAN "type" attribute for 5.15 or 5.14-oem kernel

And I knew there is a plan to upgrade MM to 1.18.6[1], and it's proposed
channel, but it has been hold more than one month because of some risks.

Is it possible that we merge this fix[2] into 1.16.6 first.

[1] https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1965901
[2]
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/1a5e0609dce59c0a49a8698f0e8cb198483124c8

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

Title:
[SRU] Support WWAN "type" attribute for 5.15 or 5.14-oem kernel

Status in modemmanager package in Ubuntu:
New

Bug description:
[Impact]
On 20.04.4, with modemmanager 1.16.6-2, the WWAN could be recognized
correctly.
With the new rules, the modem devices could be recognized correctly. And also
could avoid wrong command for other protocols, like set 'AT' to wwan0mbim.

[Where problems could occur]
It's just a udev rules, no harm to the system.

[Fix]

https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/1a5e0609dce59c0a49a8698f0e8cb198483124c8

udev: Match WWAN "type" attribute instead of device name
Recent changes in the WWAN framework in the kernel changed the WWAN
port names from e.g. "wwan0p1AT" and "wwan0p2QMI" to "wwan0at0" and
"wwan0qmi0" [1, 2]. This means that the udev rules no longer match
since AT/QMI are now lower-case and no longer at the end of the name.

However, recently additionally a "type" sysfs attribute was added
for all WWAN ports [3], which makes it much more reliable to match
the WWAN port names without relying on their exact device name.

Add some additional udev rules to apply the port hints based on the
"type" sysfs attributes. This fixes the port enumeration on newer
Linux kernels that include the aforementioned commits.

Note that we still need to keep the old udev rules for now since
Linux 5.13 does not have the "type" attribute yet.

[1]:
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=392c26f7f133b9f09e5f58db1ce6ef4b3b4df49f
[2]:
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=f458709ff40b0d992fec496952f79c7820dd3fde
[3]:
https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/?id=b3e22e10fdda8e7be3830289a4a63ae8b88d450c

(cherry picked from commit 4282c8d8)

[Test]
With new rule, like Fibcomm L860 (8086:7560) could be recognized and show
'Mobile Broadband' item in the top-right menu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1978057/+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] No cairo GL support for wayland, 22.04

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 1978057] [NEW] [SRU] Support WWAN "type" attribute for 5.15 or 5.14-oem kernel

Public bug reported:

[Impact]
On 20.04.4, with modemmanager 1.16.6-2, the WWAN could be recognized correctly.
With the new rules, the modem devices could be recognized correctly. And also
could avoid wrong command for other protocols, like set 'AT' to wwan0mbim.

[Where problems could occur]
It's just a udev rules, no harm to the system.

[Fix]
https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/1a5e0609dce59c0a49a8698f0e8cb198483124c8

However, recently additionally a "type" sysfs attribute was added
for all WWAN ports [3], which makes it much more reliable to match
the WWAN port names without relying on their exact device name.

Add some additional udev rules to apply the port hints based on the
"type" sysfs attributes. This fixes the port enumeration on newer
Linux kernels that include the aforementioned commits.

Note that we still need to keep the old udev rules for now since
Linux 5.13 does not have the "type" attribute yet.

(cherry picked from commit 4282c8d8)

[Test]
With new rule, like Fibcomm L860 (8086:7560) could be recognized and show
'Mobile Broadband' item in the top-right menu.

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

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

Title:
[SRU] Support WWAN "type" attribute for 5.15 or 5.14-oem kernel

Status in modemmanager package in Ubuntu:
New

[Where problems could occur]
It's just a udev rules, no harm to the system.

[Fix]

https://gitlab.freedesktop.org/mobile-broadband/ModemManager/-/commit/1a5e0609dce59c0a49a8698f0e8cb198483124c8

However, recently additionally a "type" sysfs attribute was added
for all WWAN ports [3], which makes it much more reliable to match
the WWAN port names without relying on their exact device name.

Add some additional udev rules to apply the port hints based on the
"type" sysfs attributes. This fixes the port enumeration on newer
Linux kernels that include the aforementioned commits.

Note that we still need to keep the old udev rules for now since
Linux 5.13 does not have the "type" attribute yet.

(cherry picked from commit 4282c8d8)

[Test]
With new rule, like Fibcomm L860 (8086:7560) could be recognized and show
'Mobile Broadband' item in the top-right menu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1978057/+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 1965563] Re: gnome-extensions-app fails to start [Error reading events from display: Protocol error]

2022-06-08 Thread DuckDuckWhale

** Also affects: obs-studio (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  gnome-extensions-app fails to start [Error reading events from
  display: Protocol error]

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in obs-studio package in Ubuntu:
  New

Bug description:
  $ dpkg-query -W gnome-shell-extension-prefs
  gnome-shell-extension-prefs   42~beta-1ubuntu3
  $ gnome-extensions-app
  Gdk-Message: 17:54:19.697: Error reading events from display: Protocol error

  Caveat: I currently have a mix of packages from jammy-release and
  jammy-proposed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965563/+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 1978042] Re: adduser doesn't support extrausers for group management

** Description changed:

  [Impact]
  
  When using adduser --extrausers on Ubuntu Core the command attempts to
  use the /etc/group file instead of /var/lib/extrausers/group. e.g. the
  following commands will fail:
  
  $ adduser --extrausers user group
  $ adduser --extrausers --ingroup group user
  
  [Test Plan]
  
  1. Install libnss-extrausers
- 2. Add a new group:
+ 2. Edit /etc/nsswitch.conf to use extrausers as shown in 
/usr/share/doc/libnss-extrausers/README
+ 3. Add a new group:
  $ sudo adduser --extrausers --group test-group
- 3. Create a new user with this group:
+ 4. Create a new user with this group:
  $ sudo adduser --extrausers --ingroup test-group test-user1
- 4. Create a new user and add them to this group:
+ 5. Create a new user and add them to this group:
  $ sudo adduser --extrausers test-user2
  $ sudo adduser --extrausers test-user2 test-group
  
  Expected result:
  Two new users (test-user1 and test-user2) are successfully added to the 
system and are entered in /var/lib/extrausers/{passwd,shadow}.
  A new group (test-group) is successfully added to /var/lib/extrausers/group 
and contains the new users.
  
  [Where problems could occur]
  Existing users of adduser and gpasswd that don't use --extrausers are 
unlikely to hit any issues, as their codepath is unchanged.
  Existing users that use --extrausers will have a behavior change, but the 
existing behavior was to fail so this is unlikely to introduce any new issues.
  There is the risk of introducing new bugs by this change, but it has used 
since impish without any issues being detected.

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

Title:
  adduser doesn't support extrausers for group management

Status in adduser package in Ubuntu:
  Fix Released
Status in shadow package in Ubuntu:
  Fix Released
Status in adduser source package in Focal:
  In Progress
Status in shadow source package in Focal:
  In Progress
Status in adduser source package in Impish:
  Fix Released
Status in shadow source package in Impish:
  Fix Released
Status in adduser source package in Jammy:
  Fix Released
Status in shadow source package in Jammy:
  Fix Released
Status in adduser source package in Kinetic:
  Fix Released
Status in shadow source package in Kinetic:
  Fix Released

Bug description:
  [Impact]

  When using adduser --extrausers on Ubuntu Core the command attempts to
  use the /etc/group file instead of /var/lib/extrausers/group. e.g. the
  following commands will fail:

  $ adduser --extrausers user group
  $ adduser --extrausers --ingroup group user

  [Test Plan]

  1. Install libnss-extrausers
  2. Edit /etc/nsswitch.conf to use extrausers as shown in 
/usr/share/doc/libnss-extrausers/README
  3. Add a new group:
  $ sudo adduser --extrausers --group test-group
  4. Create a new user with this group:
  $ sudo adduser --extrausers --ingroup test-group test-user1
  5. Create a new user and add them to this group:
  $ sudo adduser --extrausers test-user2
  $ sudo adduser --extrausers test-user2 test-group

  Expected result:
  Two new users (test-user1 and test-user2) are successfully added to the 
system and are entered in /var/lib/extrausers/{passwd,shadow}.
  A new group (test-group) is successfully added to /var/lib/extrausers/group 
and contains the new users.

  [Where problems could occur]
  Existing users of adduser and gpasswd that don't use --extrausers are 
unlikely to hit any issues, as their codepath is unchanged.
  Existing users that use --extrausers will have a behavior change, but the 
existing behavior was to fail so this is unlikely to introduce any new issues.
  There is the risk of introducing new bugs by this change, but it has used 
since impish without any issues being detected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/1978042/+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 1965563] Re: gnome-extensions-app fails to start [Error reading events from display: Protocol error]

2022-06-08 Thread DuckDuckWhale

OBS is also affected.  Log:

$ obs
...
qt.qpa.wayland: Wayland does not support QWindow::requestActivate()
...
info: [pipewire] screencast session created
The Wayland connection experienced a fatal error: Protocol error
Aborted (core dumped)
$

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

Title:
  gnome-extensions-app fails to start [Error reading events from
  display: Protocol error]

Status in gnome-shell package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  $ dpkg-query -W gnome-shell-extension-prefs
  gnome-shell-extension-prefs   42~beta-1ubuntu3
  $ gnome-extensions-app
  Gdk-Message: 17:54:19.697: Error reading events from display: Protocol error

  Caveat: I currently have a mix of packages from jammy-release and
  jammy-proposed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1965563/+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 1978042] Re: adduser doesn't support extrausers for group management

I realized after generating the debdiffs that I didn't have the bug
number in the changelog - this is fixed in the version uploaded to
focal.

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

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

** Description changed:

  [Impact]
  
  When using adduser --extrausers on Ubuntu Core the command attempts to
  use the /etc/group file instead of /var/lib/extrausers/group. e.g. the
  following commands will fail:
  
  $ adduser --extrausers user group
  $ adduser --extrausers --ingroup group user
  
  [Test Plan]
  
  1. Install libnss-extrausers
  2. Add a new group:
  $ sudo adduser --extrausers --group test-group
  3. Create a new user with this group:
- $ adduser --extrausers --ingroup test-group test-user1
+ $ sudo adduser --extrausers --ingroup test-group test-user1
  4. Create a new user and add them to this group:
- $ adduser --extrausers test-user2
- $ adduser --extrausers test-user2 test-group
+ $ sudo adduser --extrausers test-user2
+ $ sudo adduser --extrausers test-user2 test-group
  
  Expected result:
  Two new users (test-user1 and test-user2) are successfully added to the 
system and are entered in /var/lib/extrausers/{passwd,shadow}.
  A new group (test-group) is successfully added to /var/lib/extrausers/group 
and contains the new users.
  
  [Where problems could occur]
  Existing users of adduser and gpasswd that don't use --extrausers are 
unlikely to hit any issues, as their codepath is unchanged.
- Existing users that use --extrausers will have a behavior change, but the 
existing behavior was to fail so this is unlikely to introduce any new issues. 
+ Existing users that use --extrausers will have a behavior change, but the 
existing behavior was to fail so this is unlikely to introduce any new issues.
  There is the risk of introducing new bugs by this change, but it has used 
since impish without any issues being detected.

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

Title:
  adduser doesn't support extrausers for group management

Status in adduser package in Ubuntu:
  Fix Released
Status in shadow package in Ubuntu:
  Fix Released
Status in adduser source package in Focal:
  In Progress
Status in shadow source package in Focal:
  In Progress
Status in adduser source package in Impish:
  Fix Released
Status in shadow source package in Impish:
  Fix Released
Status in adduser source package in Jammy:
  Fix Released
Status in shadow source package in Jammy:
  Fix Released
Status in adduser source package in Kinetic:
  Fix Released
Status in shadow source package in Kinetic:
  Fix Released

Bug description:
  [Impact]

  When using adduser --extrausers on Ubuntu Core the command attempts to
  use the /etc/group file instead of /var/lib/extrausers/group. e.g. the
  following commands will fail:

  $ adduser --extrausers user group
  $ adduser --extrausers --ingroup group user

  [Test Plan]

  1. Install libnss-extrausers
  2. Add a new group:
  $ sudo adduser --extrausers --group test-group
  3. Create a new user with this group:
  $ sudo adduser --extrausers --ingroup test-group test-user1
  4. Create a new user and add them to this group:
  $ sudo adduser --extrausers test-user2
  $ sudo adduser --extrausers test-user2 test-group

  Expected result:
  Two new users (test-user1 and test-user2) are successfully added to the 
system and are entered in /var/lib/extrausers/{passwd,shadow}.
  A new group (test-group) is successfully added to /var/lib/extrausers/group 
and contains the new users.

  [Where problems could occur]
  Existing users of adduser and gpasswd that don't use --extrausers are 
unlikely to hit any issues, as their codepath is unchanged.
  Existing users that use --extrausers will have a behavior change, but the 
existing behavior was to fail so this is unlikely to introduce any new issues.
  There is the risk of introducing new bugs by this change, but it has used 
since impish without any issues being detected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/1978042/+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 1978042] Re: adduser doesn't support extrausers for group management

** Patch added: "adduser.debdiff"
   
https://bugs.launchpad.net/ubuntu/focal/+source/adduser/+bug/1978042/+attachment/5595790/+files/adduser.debdiff

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

Title:
  adduser doesn't support extrausers for group management

Status in adduser package in Ubuntu:
  Fix Released
Status in shadow package in Ubuntu:
  Fix Released
Status in adduser source package in Focal:
  New
Status in shadow source package in Focal:
  New
Status in adduser source package in Impish:
  Fix Released
Status in shadow source package in Impish:
  Fix Released
Status in adduser source package in Jammy:
  Fix Released
Status in shadow source package in Jammy:
  Fix Released
Status in adduser source package in Kinetic:
  Fix Released
Status in shadow source package in Kinetic:
  Fix Released

Bug description:
  [Impact]

  When using adduser --extrausers on Ubuntu Core the command attempts to
  use the /etc/group file instead of /var/lib/extrausers/group. e.g. the
  following commands will fail:

  $ adduser --extrausers user group
  $ adduser --extrausers --ingroup group user

  [Test Plan]

  1. Install libnss-extrausers
  2. Add a new group:
  $ sudo adduser --extrausers --group test-group
  3. Create a new user with this group:
  $ adduser --extrausers --ingroup test-group test-user1
  4. Create a new user and add them to this group:
  $ adduser --extrausers test-user2
  $ adduser --extrausers test-user2 test-group

  Expected result:
  Two new users (test-user1 and test-user2) are successfully added to the 
system and are entered in /var/lib/extrausers/{passwd,shadow}.
  A new group (test-group) is successfully added to /var/lib/extrausers/group 
and contains the new users.

  [Where problems could occur]
  Existing users of adduser and gpasswd that don't use --extrausers are 
unlikely to hit any issues, as their codepath is unchanged.
  Existing users that use --extrausers will have a behavior change, but the 
existing behavior was to fail so this is unlikely to introduce any new issues. 
  There is the risk of introducing new bugs by this change, but it has used 
since impish without any issues being detected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/1978042/+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 1971305] Re: Merge openldap from Debian unstable for kinetic

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 1978042] Re: adduser doesn't support extrausers for group management

** Patch added: "shadow.debdiff"
   
https://bugs.launchpad.net/ubuntu/focal/+source/adduser/+bug/1978042/+attachment/5595787/+files/shadow.debdiff

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

Title:
  adduser doesn't support extrausers for group management

Status in adduser package in Ubuntu:
  Fix Released
Status in shadow package in Ubuntu:
  Fix Released
Status in adduser source package in Focal:
  New
Status in shadow source package in Focal:
  New
Status in adduser source package in Impish:
  Fix Released
Status in shadow source package in Impish:
  Fix Released
Status in adduser source package in Jammy:
  Fix Released
Status in shadow source package in Jammy:
  Fix Released
Status in adduser source package in Kinetic:
  Fix Released
Status in shadow source package in Kinetic:
  Fix Released

Bug description:
  [Impact]

  When using adduser --extrausers on Ubuntu Core the command attempts to
  use the /etc/group file instead of /var/lib/extrausers/group. e.g. the
  following commands will fail:

  $ adduser --extrausers user group
  $ adduser --extrausers --ingroup group user

  [Test Plan]

  1. Install libnss-extrausers
  2. Add a new group:
  $ sudo adduser --extrausers --group test-group
  3. Create a new user with this group:
  $ adduser --extrausers --ingroup test-group test-user1
  4. Create a new user and add them to this group:
  $ adduser --extrausers test-user2
  $ adduser --extrausers test-user2 test-group

  Expected result:
  Two new users (test-user1 and test-user2) are successfully added to the 
system and are entered in /var/lib/extrausers/{passwd,shadow}.
  A new group (test-group) is successfully added to /var/lib/extrausers/group 
and contains the new users.

  [Where problems could occur]
  Existing users of adduser and gpasswd that don't use --extrausers are 
unlikely to hit any issues, as their codepath is unchanged.
  Existing users that use --extrausers will have a behavior change, but the 
existing behavior was to fail so this is unlikely to introduce any new issues. 
  There is the risk of introducing new bugs by this change, but it has used 
since impish without any issues being detected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/1978042/+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 1978042] Re: adduser doesn't support extrausers for group management

LP: #195375 adds extrausers groups support to the usermod command, this
SRU adds support to gpasswd (which is used by useradd).

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

Title:
  adduser doesn't support extrausers for group management

Status in adduser package in Ubuntu:
  Fix Released
Status in shadow package in Ubuntu:
  Fix Released
Status in adduser source package in Focal:
  New
Status in shadow source package in Focal:
  New
Status in adduser source package in Impish:
  Fix Released
Status in shadow source package in Impish:
  Fix Released
Status in adduser source package in Jammy:
  Fix Released
Status in shadow source package in Jammy:
  Fix Released
Status in adduser source package in Kinetic:
  Fix Released
Status in shadow source package in Kinetic:
  Fix Released

Bug description:
  [Impact]

  When using adduser --extrausers on Ubuntu Core the command attempts to
  use the /etc/group file instead of /var/lib/extrausers/group. e.g. the
  following commands will fail:

  $ adduser --extrausers user group
  $ adduser --extrausers --ingroup group user

  [Test Plan]

  1. Install libnss-extrausers
  2. Add a new group:
  $ sudo adduser --extrausers --group test-group
  3. Create a new user with this group:
  $ adduser --extrausers --ingroup test-group test-user1
  4. Create a new user and add them to this group:
  $ adduser --extrausers test-user2
  $ adduser --extrausers test-user2 test-group

  Expected result:
  Two new users (test-user1 and test-user2) are successfully added to the 
system and are entered in /var/lib/extrausers/{passwd,shadow}.
  A new group (test-group) is successfully added to /var/lib/extrausers/group 
and contains the new users.

  [Where problems could occur]
  Existing users of adduser and gpasswd that don't use --extrausers are 
unlikely to hit any issues, as their codepath is unchanged.
  Existing users that use --extrausers will have a behavior change, but the 
existing behavior was to fail so this is unlikely to introduce any new issues. 
  There is the risk of introducing new bugs by this change, but it has used 
since impish without any issues being detected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/1978042/+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 1978042] Re: adduser doesn't support extrausers for group management

2022-06-08 Thread Alex Murray

This looks like a duplicate of LP: #1959375

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

Title:
  adduser doesn't support extrausers for group management

Status in adduser package in Ubuntu:
  Fix Released
Status in shadow package in Ubuntu:
  Fix Released
Status in adduser source package in Focal:
  New
Status in shadow source package in Focal:
  New
Status in adduser source package in Impish:
  Fix Released
Status in shadow source package in Impish:
  Fix Released
Status in adduser source package in Jammy:
  Fix Released
Status in shadow source package in Jammy:
  Fix Released
Status in adduser source package in Kinetic:
  Fix Released
Status in shadow source package in Kinetic:
  Fix Released

Bug description:
  [Impact]

  When using adduser --extrausers on Ubuntu Core the command attempts to
  use the /etc/group file instead of /var/lib/extrausers/group. e.g. the
  following commands will fail:

  $ adduser --extrausers user group
  $ adduser --extrausers --ingroup group user

  [Test Plan]

  1. Install libnss-extrausers
  2. Add a new group:
  $ sudo adduser --extrausers --group test-group
  3. Create a new user with this group:
  $ adduser --extrausers --ingroup test-group test-user1
  4. Create a new user and add them to this group:
  $ adduser --extrausers test-user2
  $ adduser --extrausers test-user2 test-group

  Expected result:
  Two new users (test-user1 and test-user2) are successfully added to the 
system and are entered in /var/lib/extrausers/{passwd,shadow}.
  A new group (test-group) is successfully added to /var/lib/extrausers/group 
and contains the new users.

  [Where problems could occur]
  Existing users of adduser and gpasswd that don't use --extrausers are 
unlikely to hit any issues, as their codepath is unchanged.
  Existing users that use --extrausers will have a behavior change, but the 
existing behavior was to fail so this is unlikely to introduce any new issues. 
  There is the risk of introducing new bugs by this change, but it has used 
since impish without any issues being detected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/1978042/+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 1978042] [NEW] adduser doesn't support extrausers for group management

Public bug reported:

[Impact]

When using adduser --extrausers on Ubuntu Core the command attempts to
use the /etc/group file instead of /var/lib/extrausers/group. e.g. the
following commands will fail:

$ adduser --extrausers user group
$ adduser --extrausers --ingroup group user

[Test Plan]

1. Install libnss-extrausers
2. Add a new group:
$ sudo adduser --extrausers --group test-group
3. Create a new user with this group:
$ adduser --extrausers --ingroup test-group test-user1
4. Create a new user and add them to this group:
$ adduser --extrausers test-user2
$ adduser --extrausers test-user2 test-group

Expected result:
Two new users (test-user1 and test-user2) are successfully added to the system 
and are entered in /var/lib/extrausers/{passwd,shadow}.
A new group (test-group) is successfully added to /var/lib/extrausers/group and 
contains the new users.

[Where problems could occur]
Existing users of adduser and gpasswd that don't use --extrausers are unlikely 
to hit any issues, as their codepath is unchanged.
Existing users that use --extrausers will have a behavior change, but the 
existing behavior was to fail so this is unlikely to introduce any new issues. 
There is the risk of introducing new bugs by this change, but it has used since 
impish without any issues being detected.

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

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

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

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

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

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

** Affects: adduser (Ubuntu Jammy)
 Importance: Undecided
 Status: Fix Released

** Affects: shadow (Ubuntu Jammy)
 Importance: Undecided
 Status: Fix Released

** Affects: adduser (Ubuntu Kinetic)
 Importance: Undecided
 Status: Fix Released

** Affects: shadow (Ubuntu Kinetic)
 Importance: Undecided
 Status: Fix Released

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

** Also affects: adduser (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Title:
  adduser doesn't support extrausers for group management

Status in adduser package in Ubuntu:
  Fix Released
Status in shadow package in Ubuntu:
  Fix Released
Status in adduser source package in Focal:
  New
Status in shadow source package in Focal:
  New
Status in adduser source package in Impish:
  Fix Released
Status in shadow source package in Impish:
  Fix Released
Status in adduser source package in Jammy:
  Fix Released
Status in shadow source package in Jammy:
  Fix Released
Status in adduser source package in Kinetic:
  Fix Released
Status in shadow source package in Kinetic:
  Fix Released

Bug description:
  [Impact]

  When using adduser --extrausers on Ubuntu Core the command attempts to
  use the /etc/group file instead of /var/lib/extrausers/group. e.g. the
  following commands will fail:

  $ adduser --extrausers user group
  $ adduser --extrausers --ingroup group user

  [Test Plan]

  1. Install libnss-extrausers
  2. Add a new group:
  $ sudo adduser --extrausers --group test-group
  3. Create a new user with this group:
  $ adduser --extrausers --ingroup test-group test-user1
  4. Create a new user and add them to this group:
  $ adduser --extrausers test-user2
  $ adduser --extrausers test-user2 test-group

[Touch-packages] [Bug 1977986] Re: UPower and battery indicator show update in 2 minutes when connecting power cable ThinkPad

** Tags added: oem-priority originate-from-1975803 sutton

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

Title:
  UPower and battery indicator show update in 2 minutes  when connecting
  power cable ThinkPad

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

Bug description:
  We found this issue on several ThinkPad. The upower will change
  'pending-charge' to 'charging' after 2 minutes later, but the
  /sys/class/power_supply/BAT0/status changes to 'Charging' immediately
  when connecting the power cable.

  $ upower -i /org/freedesktop/UPower/devices/battery_BAT0
native-path:  BAT0
vendor:   Sunwoda
model:5B10W13975
serial:   34226
power supply: yes
updated:  Wed 08 Jun 2022 11:42:02 PM CST (1 seconds ago)
has history:  yes
has statistics:   yes
battery
  present: yes
  rechargeable:yes
  state:   pending-charge
  warning-level:   none
  energy:  55.94 Wh
  energy-empty:0 Wh
  energy-full: 57 Wh
  energy-full-design:  57 Wh
  energy-rate: 5.79 W
  voltage: 16.688 V
  percentage:  98%
  capacity:100%
  technology:  lithium-polymer
  icon-name:  'battery-full-charging-symbolic'
History (charge):
  1654702882  98.000  pending-charge
  1654702863  97.000  pending-charge
History (rate):
  1654702863  5.790   pending-charge
  1654702863  6.171   pending-charge

  $ cat /sys/class/power_supply/BAT0/status 
  Charging

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1977986/+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 1977564] Re: wireplumber conflicts with pipewire-media-session & needs fixing

2022-06-08 Thread Ubuntu Foundations Team Bug Bot

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

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

** Tags added: patch

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

Title:
  wireplumber conflicts with pipewire-media-session & needs fixing

Status in pipewire-media-session package in Ubuntu:
  Triaged
Status in ubuntu-meta package in Ubuntu:
  Triaged
Status in wireplumber package in Ubuntu:
  Triaged
Status in pipewire-media-session package in Debian:
  Confirmed

Bug description:
  This issue was reported on IRC and we should probably fix it before
  installing wireplumber by default so I'm setting the block-proposed
  tag.

  https://i.imgur.com/L5VFZO8.png

  wireplumber is apparently too forceful in how it enables PipeWire.
  Both Arch Linux and Debian had to

  https://archlinux.org/news/undone-replacement-of-pipewire-media-
  session-with-wireplumber/

  Is it necessary for wireplumber to conflict with pipewire-media-
  session?

  Should we add Replaces?

  What files does pipewire-media-session need to clean up when it is
  removed?

  See https://salsa.debian.org/gnome-team/gnome-remote-
  desktop/-/commit/52799cfd for an example of how files that aren't
  technically conffiles can be removed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pipewire-media-session/+bug/1977564/+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 1969375] Re: systemd-cryptenroll does not support TPM2 devices

2022-06-08 Thread Steve Langasek

Please include as part of the test plan a check that:
- there are no new binary dependencies introduced in the package
- systemd-cryptenroll doesn't have any undefined symbols that prevent it from 
running (a simple 'systemd-cryptenroll --help' suffices for this)
- non-TPM use cases of systemd-cryptenroll have not regressed.

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

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

Title:
  systemd-cryptenroll does not support TPM2 devices

Status in systemd package in Ubuntu:
  Triaged
Status in systemd source package in Jammy:
  Incomplete
Status in systemd source package in Kinetic:
  Triaged

Bug description:
  [Impact]

   * TPM2/FIDO cannot be used to unlock luks encrpyted block devices
   * due to missing build-time support in systemd
   * Error message: "TPM2 not supported on this build."

  [Test Plan]

  # prepare test
  $ sudo apt install libtss2-rc0 # runtime dependency for TPM usage
  $ dd if=/dev/zero of=encrypted.img bs=1 count=0 seek=100M
  $ echo -n "s0s3cur3" | cryptsetup luksFormat encrypted.img -
  $ sudo /usr/lib/systemd/systemd-cryptsetup attach volume encrypted.img
   Please enter passphrase for disk volume: s0s3cure
  Set cipher aes, mode xts-plain64, key size 512 bits for device encrypted.img.
  $ sudo mkfs.ext4 /dev/mapper/volume
  $ sudo mount /dev/mapper/volume /mnt
  $ sudo touch /mnt/TPM_TEST
  $ ls -la /mnt
  drwxr-xr-x  3 root root  4096 Jun  7 15:06 .
  drwxr-xr-x 20 root root  4096 Apr 20 11:45 ..
  drwx--  2 root root 16384 Jun  7 15:06 lost+found
  -rw-r--r--  1 root root 0 Jun  7 15:06 TPM_TEST
  $ sudo umount /dev/mapper/volume
  $ sudo cryptsetup luksClose volume
  $ ls -la /mnt # empty

  # use TPM
  $ systemd-cryptenroll --tpm2-device=list
  PATHDEVICE  DRIVER
  /dev/tpmrm0 MSFT0101:00 tpm_tis
  $ sudo systemd-cryptenroll --tpm2-device=auto --tpm2-pcrs=7 encrypted.img
   Please enter current passphrase for disk 
/home/lukas/canonical/systemd-dbg/encrypted.img: s0s3cur3
  New TPM2 token enrolled as key slot 1.
  $ sudo /usr/lib/systemd/systemd-cryptsetup attach volume encrypted.img - 
tpm2-device=auto
  Set cipher aes, mode xts-plain64, key size 512 bits for device encrypted.img.
  Automatically discovered security TPM2 token unlocks volume.
  # no password needed above!
  $ sudo mount /dev/mapper/volume /mnt
  $ ls -la /mnt
  drwxr-xr-x  3 root root  4096 Jun  7 15:06 .
  drwxr-xr-x 20 root root  4096 Apr 20 11:45 ..
  drwx--  2 root root 16384 Jun  7 15:06 lost+found
  -rw-r--r--  1 root root 0 Jun  7 15:06 TPM_TEST

  #cleanup
  $ sudo umount /dev/mapper/volume
  $ sudo cryptsetup luksClose volume
  $ ls -la /mnt # empty
  $ sudo rm encrypted.img

  [Where problems could occur]

   * we're enabling a build-flag to allow usage of TPM/FIDO hardware
   * running new code paths in systemd due to enablement of a new feature, 
could trigger hidden bugs in systemd-cryptsetup, e.g. (un-)locking for 
encrypted devices
   * new functionality is only active/used if enabled explicitly and suggested 
runtime dependencies are manually installed

  [Other Info]

   * This is not necessarily fall under the HWE SRU policy, as the TPM is 
already there, but just can't be used via systemd-cryptencroll
   * In a discussion with the SRU team (@vorlon) we agreed that this should be 
an exception to the rule, due to low regression risk. As long as it would not 
pull in extra dependencies into the default installation, which it doesn't (new 
dependencies are only "Suggests:")
   * This will be enabled in Kinetic+ as soon as we merge systemd v251 from 
Debian: 
https://salsa.debian.org/systemd-team/systemd/-/commit/6b5e99f1d7f63c0c83007de9f98f7745f4a564f8

  === original description ===

  systemd-cryptenroll can make use of tpm2 modules to bind against
  secure boot pcrs and enable auto unlocking of luks devices.

  Following the instructions here:
  https://wiki.archlinux.org/title/Trusted_Platform_Module#systemd-cryptenroll

  the following commands fail on ubuntu jammy (5.15.0-25-generic)

  root@testbox:~# systemd-cryptenroll --tpm2-device=list
  TPM2 not supported on this build.
  root@testbox:~# systemd-cryptenroll --tpm2-device=auto --tpm2-pcrs=7 /dev/sda3
   Please enter current passphrase for disk /dev/sda3: ***
  root@testbox:~# echo $?
  1

  It appears that this issue has been resolved in the debian build for
  systemd here:  https://salsa.debian.org/systemd-
  team/systemd/-/commit/6b5e99f1d7f63c0c83007de9f98f7745f4a564f8

  Can we get the same modifications to the Jammy systemd build?

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


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

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

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 1977564] Re: wireplumber conflicts with pipewire-media-session & needs fixing

2022-06-08 Thread Dylan Aïssi

Basically, pipewire-pulse.service wants pipewire-session-manager.service.
pipewire-session-manager.service is an alias from both wireplumber.service and 
pipewire-media-session.service.
To avoid this conflict, we need to remove pipewire-media-session.service during 
the remove step of the package, not only at the purge step.

I am thinking about applying this fix. And a similar patch for
wireplumber, just in case a user wants to move from wireplumber to
pipewire-media-session for whatever reason.

** Patch added: 
"0001-Remove-pipewire-media-session.service-when-the-packa.patch"
   
https://bugs.launchpad.net/ubuntu/+source/wireplumber/+bug/1977564/+attachment/5595684/+files/0001-Remove-pipewire-media-session.service-when-the-packa.patch

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

Title:
  wireplumber conflicts with pipewire-media-session & needs fixing

Status in pipewire-media-session package in Ubuntu:
  Triaged
Status in ubuntu-meta package in Ubuntu:
  Triaged
Status in wireplumber package in Ubuntu:
  Triaged
Status in pipewire-media-session package in Debian:
  Confirmed

Bug description:
  This issue was reported on IRC and we should probably fix it before
  installing wireplumber by default so I'm setting the block-proposed
  tag.

  https://i.imgur.com/L5VFZO8.png

  wireplumber is apparently too forceful in how it enables PipeWire.
  Both Arch Linux and Debian had to

  https://archlinux.org/news/undone-replacement-of-pipewire-media-
  session-with-wireplumber/

  Is it necessary for wireplumber to conflict with pipewire-media-
  session?

  Should we add Replaces?

  What files does pipewire-media-session need to clean up when it is
  removed?

  See https://salsa.debian.org/gnome-team/gnome-remote-
  desktop/-/commit/52799cfd for an example of how files that aren't
  technically conffiles can be removed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pipewire-media-session/+bug/1977564/+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 1976258] Re: icu ftbfs in the jammy release pocket

2022-06-08 Thread William Wilson

** Description changed:

- as seen in a test rebuild, this package fails to build in the jammy
- release pocket (note the log behind the link might go away):
+ [Impact]
+ * icu is currently FTBFS in the jammy release pocket
+ 
+ [Test Plan]
+ * Build the package from -proposed against the jammy -proposed pocket
+ * I have built it in a ppa: 
https://launchpad.net/~jawn-smith/+archive/ubuntu/ppa/+packages
+ 
+ [Regression Potential]
+ * The Canonical IDs for timezones change periodically. If a change
+   made to them here is reverted in new uploads of tzdata, they
+   will have to be updated again.
+ 
+ [Original Description]
+ as seen in a test rebuild, this package fails to build in the jammy release 
pocket (note the log behind the link might go away):
  
  https://launchpadlibrarian.net/604216394/buildlog_ubuntu-jammy-
  amd64.icu_70.1-2_BUILDING.txt.gz
  
  [...]
  make[4]: Leaving directory '/<>/source/test/cintltst'
  -
- | *** FAILING TEST SUMMARY FOR:  intltest  
-  TestCanonicalID
-   TimeZoneTest
-format
+ | *** FAILING TEST SUMMARY FOR:  intltest
+  TestCanonicalID
+   TimeZoneTest
+    format
  | *** END FAILING TEST SUMMARY FOR:  intltest
  ---
  ALL TESTS SUMMARY:
  ok:  testdata iotest cintltst
  = ERRS:  intltest
  make[3]: *** [Makefile:91: check-recursive] Error 1

** Description changed:

  [Impact]
  * icu is currently FTBFS in the jammy release pocket
  
  [Test Plan]
  * Build the package from -proposed against the jammy -proposed pocket
  * I have built it in a ppa: 
https://launchpad.net/~jawn-smith/+archive/ubuntu/ppa/+packages
  
  [Regression Potential]
  * The Canonical IDs for timezones change periodically. If a change
-   made to them here is reverted in new uploads of tzdata, they
-   will have to be updated again.
+   made to them here is reverted in new uploads of tzdata, they
+   will have to be updated again.
+ * The change is in a build-time test only, and therefore will not
+   affect users.
  
  [Original Description]
  as seen in a test rebuild, this package fails to build in the jammy release 
pocket (note the log behind the link might go away):
  
  https://launchpadlibrarian.net/604216394/buildlog_ubuntu-jammy-
  amd64.icu_70.1-2_BUILDING.txt.gz
  
  [...]
  make[4]: Leaving directory '/<>/source/test/cintltst'
  -
  | *** FAILING TEST SUMMARY FOR:  intltest
   TestCanonicalID
    TimeZoneTest
     format
  | *** END FAILING TEST SUMMARY FOR:  intltest
  ---
  ALL TESTS SUMMARY:
  ok:  testdata iotest cintltst
  = ERRS:  intltest
  make[3]: *** [Makefile:91: check-recursive] Error 1

** Tags added: verification-needed verification-needed-jammy

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

Title:
  icu ftbfs in the jammy release pocket

Status in icu package in Ubuntu:
  New

Bug description:
  [Impact]
  * icu is currently FTBFS in the jammy release pocket

  [Test Plan]
  * Build the package from -proposed against the jammy -proposed pocket
  * I have built it in a ppa: 
https://launchpad.net/~jawn-smith/+archive/ubuntu/ppa/+packages

  [Regression Potential]
  * The Canonical IDs for timezones change periodically. If a change
    made to them here is reverted in new uploads of tzdata, they
    will have to be updated again.
  * The change is in a build-time test only, and therefore will not
affect users.

  [Original Description]
  as seen in a test rebuild, this package fails to build in the jammy release 
pocket (note the log behind the link might go away):

  https://launchpadlibrarian.net/604216394/buildlog_ubuntu-jammy-
  amd64.icu_70.1-2_BUILDING.txt.gz

  [...]
  make[4]: Leaving directory '/<>/source/test/cintltst'
  -
  | *** FAILING TEST SUMMARY FOR:  intltest
   TestCanonicalID
    TimeZoneTest
     format
  | *** END FAILING TEST SUMMARY FOR:  intltest
  ---
  ALL TESTS SUMMARY:
  ok:  testdata iotest cintltst
  = ERRS:  intltest
  make[3]: *** [Makefile:91: check-recursive] Error 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/icu/+bug/1976258/+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 no longer prefers DHCPv6 addresses over SLAAC

2022-06-08 Thread Justin

@seb128 I am also affected by this bug and privacy-wise every other
Ubuntu 22.04 user as well, but I didn´t respond, trusting the process
that this bug would be fixed. So I am supporting your efforts getting an
upstream fix shortly or alternatively reverting the change that created
the regression.

-- 
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 no longer prefers DHCPv6 addresses over SLAAC

Status in NetworkManager:
  New
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Situation:

  My network has both DHCPv6 and SLAAC (autoconf) for IPv6. From a
  privacy perspective, for readability reasons and for network
  management policies, DHCPv6 should *always* be preferred over SLAAC
  addresses when available. And according to RFC 6724, the smaller /128
  scope of the DHCPv6 address should be chosen over the larger /64 scope
  of the SLAAC address.

  NetworkManager has always been able to adhere to that by simply
  setting ip6.privacy=0 for the connection (in nm-connection-editor
  *not* selecting "Prefer temporary address" for IPv6 privacy
  extensions). Then it would use the DHCPv6 address as the source for
  all outgoing traffic.

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

  Regression:

  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.

  Constantly removing the SLAAC addresses with `ip addr del` or
  disabling SLAAC RA's on the router are now the only ways to stop
  NetworkManager from preferring SLAAC over DHCPv6. None of the local
  options in NetworkManager 1.36.6 are able to restore the previous,
  desired and correct way of working: the SLAAC address should never be
  used as the preferred address if a DHCPv6 lease is given.

  Looking at the changelog of NetworkManager 1.36.6, multiple things
  regarding IP address order and temporary addresses have been changed
  in that release, any of them (or a combination) introducing this bug:

  * Fix a bug in synchronization of IP addresses with kernel that could lead to 
a wrong address order.
  * Ignore addresses from DHCPv6 when the Otherconf router advertisement flag 
is set.
  * Ensure temporary IPv6 addresses are removed on disconnect and reapply.

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-36/NEWS

  Steps to reproduce:

  1. Connect to a network where the router sends "A" and "M" bits in the
  RA's and has a DHCPv6 server running (e.g. any OpenWrt router).

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

  3. When running something like `curl ifconfig.co`, the SLAAC address
  is being returned, which makes sense as that is now preferred by the
  kernel. (But it shouldn't be.)

  Desired behaviour:

  NetworkManager should always sort DHCPv6 addresses above SLAAC
  addresses, as is the case for all versions prior to 1.36.6 and also
  corrected again in 1.38.0. In case static addresses are manually set,
  those should take first priority, with DHCPv6 second and
  SLAAC/autoconf last.

  Implications:

  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 and cannot centrally
  configure), 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.

  Note that "just disabling SLAAC RA's on the router" is not something
  everybody can do, as it requires root access to the device. Moreover,
  it would break IPv6 connectivity entirely for devices that don't
  support DHCPv6 (read: Android).

  Conclusion:

  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. As that version is also used in Ubuntu kinetic, most likely
  this bug is not present there.

  Looking at the changelog of 1.38.0:

  * Fix bug setting priority for IP addresses.
  * Static IPv6 addresses from "ipv6.addresses" are now preferred over 
addresses from DHCPv6, which are preferred over addresses from

[Touch-packages] [Bug 1977619] Re: NetworkManager 1.36.6 no longer prefers DHCPv6 addresses over SLAAC

2022-06-08 Thread Kevin Keijzer

Unfortunately I was not tracking jammy-proposed, so I only found out
about this bug when it entered jammy-updates.

I don't think my configuration is that exotic to be honest. Many
companies use DHCPv6 servers giving out static leases, and many
companies use firewalls to restrict incoming (SSH) connections to their
servers. And not many network administrators disable SLAAC as that would
break IPv6 for all Android users. So corporate and home networks with
DHCPv6 and SLAAC enabled are quite common.

How viable would it be to create something like 1.36.7~really1.36.4 or
something like that, which would be the previous version with only
commit 6a82dd18 cherry picked to fix the hotspot issue and not introduce
the source address selection bug?

I suppose upstream would at some point release 1.36.9, which will
hopefully have this bug fixed, and also have commit 6a82dd18 included,
so Ubuntu can go back to the upstream version then.

-- 
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 no longer prefers DHCPv6 addresses over SLAAC

Status in NetworkManager:
  New
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Situation:

  My network has both DHCPv6 and SLAAC (autoconf) for IPv6. From a
  privacy perspective, for readability reasons and for network
  management policies, DHCPv6 should *always* be preferred over SLAAC
  addresses when available. And according to RFC 6724, the smaller /128
  scope of the DHCPv6 address should be chosen over the larger /64 scope
  of the SLAAC address.

  NetworkManager has always been able to adhere to that by simply
  setting ip6.privacy=0 for the connection (in nm-connection-editor
  *not* selecting "Prefer temporary address" for IPv6 privacy
  extensions). Then it would use the DHCPv6 address as the source for
  all outgoing traffic.

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

  Regression:

  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.

  Constantly removing the SLAAC addresses with `ip addr del` or
  disabling SLAAC RA's on the router are now the only ways to stop
  NetworkManager from preferring SLAAC over DHCPv6. None of the local
  options in NetworkManager 1.36.6 are able to restore the previous,
  desired and correct way of working: the SLAAC address should never be
  used as the preferred address if a DHCPv6 lease is given.

  Looking at the changelog of NetworkManager 1.36.6, multiple things
  regarding IP address order and temporary addresses have been changed
  in that release, any of them (or a combination) introducing this bug:

  * Fix a bug in synchronization of IP addresses with kernel that could lead to 
a wrong address order.
  * Ignore addresses from DHCPv6 when the Otherconf router advertisement flag 
is set.
  * Ensure temporary IPv6 addresses are removed on disconnect and reapply.

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-36/NEWS

  Steps to reproduce:

  1. Connect to a network where the router sends "A" and "M" bits in the
  RA's and has a DHCPv6 server running (e.g. any OpenWrt router).

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

  3. When running something like `curl ifconfig.co`, the SLAAC address
  is being returned, which makes sense as that is now preferred by the
  kernel. (But it shouldn't be.)

  Desired behaviour:

  NetworkManager should always sort DHCPv6 addresses above SLAAC
  addresses, as is the case for all versions prior to 1.36.6 and also
  corrected again in 1.38.0. In case static addresses are manually set,
  those should take first priority, with DHCPv6 second and
  SLAAC/autoconf last.

  Implications:

  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 and cannot centrally
  configure), 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.

  Note that "just disabling SLAAC RA's on the router" is not something
  everybody can do, as it requires root access to the device. Moreover,
  it would break IPv6 connectivity entirely for devices that don't
  support DHCPv6 (read:

[Touch-packages] [Bug 1977619] Re: NetworkManager 1.36.6 no longer prefers DHCPv6 addresses over SLAAC

2022-06-08 Thread Sebastien Bacher

@Kevin. Thanks, it's a bit of an annoying situation. The current update
is not only in proposed but was moving to updates before you reported
the regression, which means we can't simply delete it from proposed, we
need a fix or revert. I was hoping upstream would figure out a fix
quickly enough that we could do another bugfix upload. If that doesn't
play out this way we need to figure out what to do.

The initial reason for SRUing the update, out of keeping up with
upstream fixes, was that it fixes some hotspot issues which is a topic
we are getting complain about
(https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/6a82dd18)

We could revert back the version, including other fixes. Or revert the
change that created the regression you reported. Note that while it
seems an annoying issue to you that's the only report we got so far
which suggest it's not a common configuration for our users, which is
also a reason why I decided to wait a bit to see if upstream was
reacting before reverting.

-- 
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 no longer prefers DHCPv6 addresses over SLAAC

Status in NetworkManager:
  New
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Situation:

  My network has both DHCPv6 and SLAAC (autoconf) for IPv6. From a
  privacy perspective, for readability reasons and for network
  management policies, DHCPv6 should *always* be preferred over SLAAC
  addresses when available. And according to RFC 6724, the smaller /128
  scope of the DHCPv6 address should be chosen over the larger /64 scope
  of the SLAAC address.

  NetworkManager has always been able to adhere to that by simply
  setting ip6.privacy=0 for the connection (in nm-connection-editor
  *not* selecting "Prefer temporary address" for IPv6 privacy
  extensions). Then it would use the DHCPv6 address as the source for
  all outgoing traffic.

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

  Regression:

  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.

  Constantly removing the SLAAC addresses with `ip addr del` or
  disabling SLAAC RA's on the router are now the only ways to stop
  NetworkManager from preferring SLAAC over DHCPv6. None of the local
  options in NetworkManager 1.36.6 are able to restore the previous,
  desired and correct way of working: the SLAAC address should never be
  used as the preferred address if a DHCPv6 lease is given.

  Looking at the changelog of NetworkManager 1.36.6, multiple things
  regarding IP address order and temporary addresses have been changed
  in that release, any of them (or a combination) introducing this bug:

  * Fix a bug in synchronization of IP addresses with kernel that could lead to 
a wrong address order.
  * Ignore addresses from DHCPv6 when the Otherconf router advertisement flag 
is set.
  * Ensure temporary IPv6 addresses are removed on disconnect and reapply.

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-36/NEWS

  Steps to reproduce:

  1. Connect to a network where the router sends "A" and "M" bits in the
  RA's and has a DHCPv6 server running (e.g. any OpenWrt router).

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

  3. When running something like `curl ifconfig.co`, the SLAAC address
  is being returned, which makes sense as that is now preferred by the
  kernel. (But it shouldn't be.)

  Desired behaviour:

  NetworkManager should always sort DHCPv6 addresses above SLAAC
  addresses, as is the case for all versions prior to 1.36.6 and also
  corrected again in 1.38.0. In case static addresses are manually set,
  those should take first priority, with DHCPv6 second and
  SLAAC/autoconf last.

  Implications:

  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 and cannot centrally
  configure), 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.

  Note that "just disabling SLAAC RA's on the router" is not something
  everybody can do, as it requires root access to the device. Moreover,
  it would

[Touch-packages] [Bug 1972056] Re: [openssl3] please sync openssl.cnf to ease changing security level

2022-06-08 Thread Oibaf

It looks like it failed to build...
Any reason not to backport 3.0.3-5ubuntu2 from kinetic?

-- 
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:
  Fix Committed
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 1977619] Re: NetworkManager 1.36.6 no longer prefers DHCPv6 addresses over SLAAC

2022-06-08 Thread Kevin Keijzer

@seb128 What is the plan for the network-manager package in Ubuntu
jammy-updates? Is it to be left broken until upstream fixes this bug?

Because I think that the problem this last version introduces is a lot
bigger than the problem(s) it solves. Therefore I would say that it can
be defended to upload a new version that restores 1.36.4-2ubuntu1 for
the time being, and then re-sync with upstream when (or if) this bug is
fixed.

As far as I'm aware, the update from 1.36.4 to 1.36.6 did not close any
outstanding Launchpad bugs, so it didn't fix anything from Ubuntu's
perspective. It just introduced this regression.

-- 
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 no longer prefers DHCPv6 addresses over SLAAC

Status in NetworkManager:
  New
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Situation:

  My network has both DHCPv6 and SLAAC (autoconf) for IPv6. From a
  privacy perspective, for readability reasons and for network
  management policies, DHCPv6 should *always* be preferred over SLAAC
  addresses when available. And according to RFC 6724, the smaller /128
  scope of the DHCPv6 address should be chosen over the larger /64 scope
  of the SLAAC address.

  NetworkManager has always been able to adhere to that by simply
  setting ip6.privacy=0 for the connection (in nm-connection-editor
  *not* selecting "Prefer temporary address" for IPv6 privacy
  extensions). Then it would use the DHCPv6 address as the source for
  all outgoing traffic.

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

  Regression:

  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.

  Constantly removing the SLAAC addresses with `ip addr del` or
  disabling SLAAC RA's on the router are now the only ways to stop
  NetworkManager from preferring SLAAC over DHCPv6. None of the local
  options in NetworkManager 1.36.6 are able to restore the previous,
  desired and correct way of working: the SLAAC address should never be
  used as the preferred address if a DHCPv6 lease is given.

  Looking at the changelog of NetworkManager 1.36.6, multiple things
  regarding IP address order and temporary addresses have been changed
  in that release, any of them (or a combination) introducing this bug:

  * Fix a bug in synchronization of IP addresses with kernel that could lead to 
a wrong address order.
  * Ignore addresses from DHCPv6 when the Otherconf router advertisement flag 
is set.
  * Ensure temporary IPv6 addresses are removed on disconnect and reapply.

  
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-36/NEWS

  Steps to reproduce:

  1. Connect to a network where the router sends "A" and "M" bits in the
  RA's and has a DHCPv6 server running (e.g. any OpenWrt router).

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

  3. When running something like `curl ifconfig.co`, the SLAAC address
  is being returned, which makes sense as that is now preferred by the
  kernel. (But it shouldn't be.)

  Desired behaviour:

  NetworkManager should always sort DHCPv6 addresses above SLAAC
  addresses, as is the case for all versions prior to 1.36.6 and also
  corrected again in 1.38.0. In case static addresses are manually set,
  those should take first priority, with DHCPv6 second and
  SLAAC/autoconf last.

  Implications:

  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 and cannot centrally
  configure), 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.

  Note that "just disabling SLAAC RA's on the router" is not something
  everybody can do, as it requires root access to the device. Moreover,
  it would break IPv6 connectivity entirely for devices that don't
  support DHCPv6 (read: Android).

  Conclusion:

  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

[Touch-packages] [Bug 1974196] Re: Installing libudev1 on a new Jammy installation uninstalls many packages.

2022-06-08 Thread Tully

I completely understand that moving the apt-get update && apt upgrade to
the beginning of the manual would be better. The problem is that this
can completely destroy an ubuntu system installation if done without
following that best practice. We had user reports which is why we have
made sure with the conflicts to not cause this.

The above reproduction is focused on isolating the minimum set. You can
reproduce it with a larger system using one of the older tags
https://hub.docker.com/layers/udevdebug/tfoote/udevdebug/1/images/sha256-de4ca1bfb4aef4ab5b5909ea60814d33101aa3b855eb2a41dddb54dda146817c?context=explore

docker run -ti --rm tfoote/udevdebug:1 bash -c 'apt-get update && apt-
get install libudev1'


And you'll get it removing a large fraction of essential ubuntu and make your 
system unusable.


docker run -ti --rm tfoote/udevdebug:1 bash -c 'apt-get update && apt-get 
install libudev1'
Get:1 http://security.ubuntu.com/ubuntu jammy-security InRelease [110 kB]
Hit:2 http://archive.ubuntu.com/ubuntu jammy InRelease 
Get:3 http://archive.ubuntu.com/ubuntu jammy-updates InRelease [109 kB]
Get:4 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages [198 
kB]
Get:5 http://security.ubuntu.com/ubuntu jammy-security/main amd64 DEP-11 
Metadata [12.7 kB]
Get:6 http://security.ubuntu.com/ubuntu jammy-security/main DEP-11 48x48 Icons 
[5952 B]
Get:7 http://security.ubuntu.com/ubuntu jammy-security/main DEP-11 64x64 Icons 
[8219 B]  
Get:8 http://security.ubuntu.com/ubuntu jammy-security/main amd64 c-n-f 
Metadata [2600 B]
Get:9 http://security.ubuntu.com/ubuntu jammy-security/restricted amd64 
Packages [188 kB]
Get:10 http://security.ubuntu.com/ubuntu jammy-security/restricted amd64 c-n-f 
Metadata [464 B]
Get:11 http://security.ubuntu.com/ubuntu jammy-security/universe amd64 Packages 
[81.0 kB]
Get:12 http://security.ubuntu.com/ubuntu jammy-security/universe amd64 c-n-f 
Metadata [1076 B]
Get:13 http://security.ubuntu.com/ubuntu jammy-security/multiverse amd64 c-n-f 
Metadata [228 B]
Get:14 http://archive.ubuntu.com/ubuntu jammy-backports InRelease [99.8 kB] 
 
Get:15 http://archive.ubuntu.com/ubuntu jammy/main amd64 c-n-f Metadata [30.3 
kB]
Get:16 http://archive.ubuntu.com/ubuntu jammy/restricted amd64 c-n-f Metadata 
[488 B]
Get:17 http://archive.ubuntu.com/ubuntu jammy/universe amd64 c-n-f Metadata 
[286 kB]
Get:18 http://archive.ubuntu.com/ubuntu jammy/multiverse amd64 c-n-f Metadata 
[8372 B]
Get:19 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages [348 
kB]
Get:20 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 DEP-11 
Metadata [91.0 kB]
Get:21 http://archive.ubuntu.com/ubuntu jammy-updates/main DEP-11 48x48 Icons 
[25.0 kB]
Get:22 http://archive.ubuntu.com/ubuntu jammy-updates/main DEP-11 64x64 Icons 
[37.1 kB]
Get:23 http://archive.ubuntu.com/ubuntu jammy-updates/main DEP-11 64x64@2 Icons 
[29 B]
Get:24 http://archive.ubuntu.com/ubuntu jammy-updates/main amd64 c-n-f Metadata 
[4840 B]
Get:25 http://archive.ubuntu.com/ubuntu jammy-updates/restricted amd64 Packages 
[209 kB]
Get:26 http://archive.ubuntu.com/ubuntu jammy-updates/restricted amd64 c-n-f 
Metadata [460 B]
Get:27 http://archive.ubuntu.com/ubuntu jammy-updates/universe amd64 Packages 
[142 kB]
Get:28 http://archive.ubuntu.com/ubuntu jammy-updates/universe amd64 DEP-11 
Metadata [115 kB]
Get:29 http://archive.ubuntu.com/ubuntu jammy-updates/universe DEP-11 48x48 
Icons [35.1 kB]
Get:30 http://archive.ubuntu.com/ubuntu jammy-updates/universe DEP-11 64x64 
Icons [46.5 kB]
Get:31 http://archive.ubuntu.com/ubuntu jammy-updates/universe DEP-11 64x64@2 
Icons [29 B]
Get:32 http://archive.ubuntu.com/ubuntu jammy-updates/universe amd64 c-n-f 
Metadata [2292 B]
Get:33 http://archive.ubuntu.com/ubuntu jammy-updates/multiverse amd64 Packages 
[4653 B]
Get:34 http://archive.ubuntu.com/ubuntu jammy-updates/multiverse amd64 c-n-f 
Metadata [232 B]
Get:35 http://archive.ubuntu.com/ubuntu jammy-backports/main amd64 c-n-f 
Metadata [112 B]
Get:36 http://archive.ubuntu.com/ubuntu jammy-backports/restricted amd64 c-n-f 
Metadata [116 B]
Get:37 http://archive.ubuntu.com/ubuntu jammy-backports/universe amd64 Packages 
[2016 B]
Get:38 http://archive.ubuntu.com/ubuntu jammy-backports/universe amd64 DEP-11 
Metadata [1122 B]
Get:39 http://archive.ubuntu.com/ubuntu jammy-backports/universe DEP-11 48x48 
Icons [2686 B]
Get:40 http://archive.ubuntu.com/ubuntu jammy-backports/universe DEP-11 64x64 
Icons [4938 B]
Get:41 http://archive.ubuntu.com/ubuntu jammy-backports/universe DEP-11 64x64@2 
Icons [29 B]
Get:42 http://archive.ubuntu.com/ubuntu jammy-backports/universe amd64 c-n-f 
Metadata [216 B]
Get:43 http://archive.ubuntu.com/ubuntu jammy-backports/multiverse amd64 c-n-f 
Metadata [116 B]
Fetched 2216 kB in 2s (1031 kB/s) 
Reading package lists... Done
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer

[Touch-packages] [Bug 1977982] Re: Please merge keyutils 1.6.1-3 (main) from Debian unstable (main)

2022-06-08 Thread Olivier Gayot

Debdiff from Ubuntu

** Patch added: "Debdiff from ubuntu"
   
https://bugs.launchpad.net/ubuntu/+source/keyutils/+bug/1977982/+attachment/5595637/+files/1-keyutils_1.6.1-2ubuntu3__1.6.1-3ubuntu1.debdiff

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

-- 
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:
  Confirmed

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 use 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 1977982] Re: Please merge keyutils 1.6.1-3 (main) from Debian unstable (main)

2022-06-08 Thread Olivier Gayot

Adding debdiff from Debian

** Patch added: "Debdiff from debian 1.6.1-3"
   
https://bugs.launchpad.net/ubuntu/+source/keyutils/+bug/1977982/+attachment/5595636/+files/1-keyutils_1.6.1-3__1.6.1-3ubuntu1.debdiff

-- 
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:
  Confirmed

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 use 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 1951586] Re: Need option to specify wifi regulatory domain

** Changed in: netplan
   Status: New => In Progress

** Changed in: netplan
 Assignee: (unassigned) => Lukas Märdian (slyon)

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

Title:
  Need option to specify wifi regulatory domain

Status in cloud-init:
  Invalid
Status in netplan:
  In Progress
Status in NetworkManager:
  New
Status in netplan.io package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  Incomplete
Status in netplan.io source package in Jammy:
  Triaged
Status in network-manager source package in Jammy:
  Incomplete
Status in netplan.io source package in Kinetic:
  Triaged
Status in network-manager source package in Kinetic:
  Incomplete

Bug description:
  It would be nice if netplan offered an option to specify the wifi
  regulatory domain (country code).

  
  For devices such as the Raspberry Pi you are currently advertising that users 
can simply setup Ubuntu Server headless by putting the wifi configuration 
details in cloudinit/netplan's "network-config" on the FAT partition of the SD 
card: 
https://ubuntu.com/tutorials/how-to-install-ubuntu-on-your-raspberry-pi#3-wifi-or-ethernet
  But an option to set the wifi country code there does not seem to exist, so 
may not work.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1951586/+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 1977986] [NEW] UPower and battery indicator show update in 2 minutes when connecting power cable ThinkPad

Public bug reported:

We found this issue on several ThinkPad. The upower will change
'pending-charge' to 'charging' after 2 minutes later, but the
/sys/class/power_supply/BAT0/status changes to 'Charging' immediately
when connecting the power cable.

$ upower -i /org/freedesktop/UPower/devices/battery_BAT0
  native-path:  BAT0
  vendor:   Sunwoda
  model:5B10W13975
  serial:   34226
  power supply: yes
  updated:  Wed 08 Jun 2022 11:42:02 PM CST (1 seconds ago)
  has history:  yes
  has statistics:   yes
  battery
present: yes
rechargeable:yes
state:   pending-charge
warning-level:   none
energy:  55.94 Wh
energy-empty:0 Wh
energy-full: 57 Wh
energy-full-design:  57 Wh
energy-rate: 5.79 W
voltage: 16.688 V
percentage:  98%
capacity:100%
technology:  lithium-polymer
icon-name:  'battery-full-charging-symbolic'
  History (charge):
1654702882  98.000  pending-charge
1654702863  97.000  pending-charge
  History (rate):
1654702863  5.790   pending-charge
1654702863  6.171   pending-charge

$ cat /sys/class/power_supply/BAT0/status 
Charging

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

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

Title:
  UPower and battery indicator show update in 2 minutes  when connecting
  power cable ThinkPad

Status in upower package in Ubuntu:
  New

Bug description:
  We found this issue on several ThinkPad. The upower will change
  'pending-charge' to 'charging' after 2 minutes later, but the
  /sys/class/power_supply/BAT0/status changes to 'Charging' immediately
  when connecting the power cable.

  $ upower -i /org/freedesktop/UPower/devices/battery_BAT0
native-path:  BAT0
vendor:   Sunwoda
model:5B10W13975
serial:   34226
power supply: yes
updated:  Wed 08 Jun 2022 11:42:02 PM CST (1 seconds ago)
has history:  yes
has statistics:   yes
battery
  present: yes
  rechargeable:yes
  state:   pending-charge
  warning-level:   none
  energy:  55.94 Wh
  energy-empty:0 Wh
  energy-full: 57 Wh
  energy-full-design:  57 Wh
  energy-rate: 5.79 W
  voltage: 16.688 V
  percentage:  98%
  capacity:100%
  technology:  lithium-polymer
  icon-name:  'battery-full-charging-symbolic'
History (charge):
  1654702882  98.000  pending-charge
  1654702863  97.000  pending-charge
History (rate):
  1654702863  5.790   pending-charge
  1654702863  6.171   pending-charge

  $ cat /sys/class/power_supply/BAT0/status 
  Charging

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/upower/+bug/1977986/+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-06-08 Thread Łukasz Zemczak

Hello Matt, or anyone else affected,

Accepted openssl into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/openssl/3.0.2-0ubuntu1.3 in a few
hours, and then in the -proposed repository.

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

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

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

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

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

** Tags added: verification-needed verification-needed-jammy

-- 
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:
  Fix Committed

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

[Touch-packages] [Bug 1972056] Re: [openssl3] please sync openssl.cnf to ease changing security level

2022-06-08 Thread Łukasz Zemczak

Hello Oibaf, or anyone else affected,

Accepted openssl into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/openssl/3.0.2-0ubuntu1.3 in a few
hours, and then in the -proposed repository.

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

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

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

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

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

** Tags added: verification-needed verification-needed-jammy

-- 
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:
  Fix Committed
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-08 Thread Łukasz Zemczak

Hello Simon, or anyone else affected,

Accepted openssl into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/openssl/3.0.2-0ubuntu1.3 in a few
hours, and then in the -proposed repository.

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

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

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

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

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

** Tags added: verification-needed verification-needed-jammy

-- 
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:
  Fix Committed
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 1805115] Re: problem with (ubuntu/cosmic)mawk /^[[:space:]]*

2022-06-08 Thread Christian Ehrhardt 

** Tags removed: server-todo

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

Title:
   problem with (ubuntu/cosmic)mawk /^[[:space:]]*http://archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status
  ###

  more background @ 
  https://github.com/whiteinge/ok.sh/issues/66# problem with 
(ubuntu/cosmic)mawk /^[[:space:]]*https://api.github.com/repositories/3386088/issues?page=2>; 
rel="next", ; 
rel="last"' | awk '
  BEGIN { RS=", "; FS="; "; OFS=": " }
  {
  sub(/^rel="/, "", $2); sub(/"$/, "", $2)
  sub(/^ *$/, "", $1)
  print "Link_" $2, $1
  }'
  Link_next: https://api.github.com/repositories/3386088/issues?page=2
  Link_last: https://api.github.com/repositories/3386088/issues?page=33
  -

  fails using [[:space:]]
  eg
  -
  printf %s '; 
rel="next", ; 
rel="last"' | awk '
  BEGIN { RS=", "; FS="; "; OFS=": " }
  {
  sub(/^rel="/, "", $2); sub(/"$/, "", $2)
  sub(/^[[:space:]]*$/, "", $1)
  print "Link_" $2, $1
  }'
  Link_next:

[Touch-packages] [Bug 1977982] [NEW] Please merge keyutils 1.6.1-3 (main) from Debian unstable (main)

2022-06-08 Thread Olivier Gayot

Public bug reported:

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 use 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.

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

-- 
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:
  New

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 use 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 1971523] Re: Static build does not work for libmnl (-lmnl)

2022-06-08 Thread Christian Ehrhardt 

Thank you Lars,
Debian maintainer confirmed the issue and agreed on making the necessary 
changes which is great as we do not have to deviate. They didn't land yet, but 
once they do (which will update the now linked Debian bug).

>From there we can then consider SRUs - I added bug tasks for these.

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

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

** Changed in: libmnl (Ubuntu Impish)
   Status: New => Triaged

** Changed in: libmnl (Ubuntu Jammy)
   Status: New => Triaged

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

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

Title:
  Static build does not work for libmnl (-lmnl)

Status in libmnl package in Ubuntu:
  Triaged
Status in libmnl source package in Impish:
  Triaged
Status in libmnl source package in Jammy:
  Triaged
Status in libmnl package in Debian:
  Unknown

Bug description:
  Example;
  # gcc -o /tmp/hello /tmp/hello.c -lmnl
  (dynamic libs work)
  # gcc -static -o /tmp/hello /tmp/hello.c -lmnl
  /usr/bin/ld: cannot find -lmnl: No such file or directory

  
  My program uses both -lmnl and -lnetfilter_queue and in Ubuntu 20.04 the 
-lnetfilter_queue did not work and -lmnl worked for static builds. In Ubuntu 
22.04 the problem is reversed, -lnetfilter_queue works but -lmnl doesn't for 
static builds. This is very awkward during the transition 20.04->22.04 when 
both should be supported.

  I compensated in Ubuntu 20.04 by building netfilter_queue locally;
  https://github.com/Nordix/nfqueue-loadbalancer#build

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libmnl0:amd64 1.0.4-3build2
  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
  CasperMD5CheckResult: unknown
  CurrentDesktop: XFCE
  Date: Wed May  4 07:33:26 2022
  InstallationDate: Installed on 2018-09-07 (1334 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: libmnl
  UpgradeStatus: Upgraded to jammy on 2022-05-01 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libmnl/+bug/1971523/+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 1973607] Re: Please merge logrotate 3.19.0-2 (main) from Debian unstable (main)

2022-06-08 Thread Alexandre Ghiti

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

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

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

Status in logrotate package in Ubuntu:
  Invalid

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1973607/+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

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

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 1969375] Re: systemd-cryptenroll does not support TPM2 devices

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

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

Title:
  systemd-cryptenroll does not support TPM2 devices

Status in systemd package in Ubuntu:
  Triaged
Status in systemd source package in Jammy:
  In Progress
Status in systemd source package in Kinetic:
  Triaged

Bug description:
  [Impact]

   * TPM2/FIDO cannot be used to unlock luks encrpyted block devices
   * due to missing build-time support in systemd
   * Error message: "TPM2 not supported on this build."

  [Test Plan]

  # prepare test
  $ sudo apt install libtss2-rc0 # runtime dependency for TPM usage
  $ dd if=/dev/zero of=encrypted.img bs=1 count=0 seek=100M
  $ echo -n "s0s3cur3" | cryptsetup luksFormat encrypted.img -
  $ sudo /usr/lib/systemd/systemd-cryptsetup attach volume encrypted.img
   Please enter passphrase for disk volume: s0s3cure
  Set cipher aes, mode xts-plain64, key size 512 bits for device encrypted.img.
  $ sudo mkfs.ext4 /dev/mapper/volume
  $ sudo mount /dev/mapper/volume /mnt
  $ sudo touch /mnt/TPM_TEST
  $ ls -la /mnt
  drwxr-xr-x  3 root root  4096 Jun  7 15:06 .
  drwxr-xr-x 20 root root  4096 Apr 20 11:45 ..
  drwx--  2 root root 16384 Jun  7 15:06 lost+found
  -rw-r--r--  1 root root 0 Jun  7 15:06 TPM_TEST
  $ sudo umount /dev/mapper/volume
  $ sudo cryptsetup luksClose volume
  $ ls -la /mnt # empty

  # use TPM
  $ systemd-cryptenroll --tpm2-device=list
  PATHDEVICE  DRIVER
  /dev/tpmrm0 MSFT0101:00 tpm_tis
  $ sudo systemd-cryptenroll --tpm2-device=auto --tpm2-pcrs=7 encrypted.img
   Please enter current passphrase for disk 
/home/lukas/canonical/systemd-dbg/encrypted.img: s0s3cur3
  New TPM2 token enrolled as key slot 1.
  $ sudo /usr/lib/systemd/systemd-cryptsetup attach volume encrypted.img - 
tpm2-device=auto
  Set cipher aes, mode xts-plain64, key size 512 bits for device encrypted.img.
  Automatically discovered security TPM2 token unlocks volume.
  # no password needed above!
  $ sudo mount /dev/mapper/volume /mnt
  $ ls -la /mnt
  drwxr-xr-x  3 root root  4096 Jun  7 15:06 .
  drwxr-xr-x 20 root root  4096 Apr 20 11:45 ..
  drwx--  2 root root 16384 Jun  7 15:06 lost+found
  -rw-r--r--  1 root root 0 Jun  7 15:06 TPM_TEST

  #cleanup
  $ sudo umount /dev/mapper/volume
  $ sudo cryptsetup luksClose volume
  $ ls -la /mnt # empty
  $ sudo rm encrypted.img

  [Where problems could occur]

   * we're enabling a build-flag to allow usage of TPM/FIDO hardware
   * running new code paths in systemd due to enablement of a new feature, 
could trigger hidden bugs in systemd-cryptsetup, e.g. (un-)locking for 
encrypted devices
   * new functionality is only active/used if enabled explicitly and suggested 
runtime dependencies are manually installed

  [Other Info]

   * This is not necessarily fall under the HWE SRU policy, as the TPM is 
already there, but just can't be used via systemd-cryptencroll
   * In a discussion with the SRU team (@vorlon) we agreed that this should be 
an exception to the rule, due to low regression risk. As long as it would not 
pull in extra dependencies into the default installation, which it doesn't (new 
dependencies are only "Suggests:")
   * This will be enabled in Kinetic+ as soon as we merge systemd v251 from 
Debian: 
https://salsa.debian.org/systemd-team/systemd/-/commit/6b5e99f1d7f63c0c83007de9f98f7745f4a564f8

  === original description ===

  systemd-cryptenroll can make use of tpm2 modules to bind against
  secure boot pcrs and enable auto unlocking of luks devices.

  Following the instructions here:
  https://wiki.archlinux.org/title/Trusted_Platform_Module#systemd-cryptenroll

  the following commands fail on ubuntu jammy (5.15.0-25-generic)

  root@testbox:~# systemd-cryptenroll --tpm2-device=list
  TPM2 not supported on this build.
  root@testbox:~# systemd-cryptenroll --tpm2-device=auto --tpm2-pcrs=7 /dev/sda3
   Please enter current passphrase for disk /dev/sda3: ***
  root@testbox:~# echo $?
  1

  It appears that this issue has been resolved in the debian build for
  systemd here:  https://salsa.debian.org/systemd-
  team/systemd/-/commit/6b5e99f1d7f63c0c83007de9f98f7745f4a564f8

  Can we get the same modifications to the Jammy systemd build?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1969375/+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

** Changed in: systemd (Ubuntu Kinetic)
   Status: Triaged => Fix Committed

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/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 Committed
Status in systemd source package in Jammy:
  In Progress
Status in systemd source package in Kinetic:
  Fix Committed

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 1977710] Re: /etc/adduser.conf.dpkg-save created by postinst since 3.121ubuntu1

2022-06-08 Thread Sebastien Bacher

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

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

** Changed in: adduser (Ubuntu)
   Importance: Undecided => Low

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

Title:
  /etc/adduser.conf.dpkg-save created by postinst since 3.121ubuntu1

Status in adduser package in Ubuntu:
  Triaged
Status in adduser package in Debian:
  Unknown

Bug description:
  Since version 3.121ubuntu1 adduser's postinst script creates
  /etc/adduser.conf.dpkg-save file on debootstrap's root filesystem,
  that is, even when /etc/adduser.conf doesn't exist prior to package
  installation.

  Because of the change below the postinst script changes packaged
  /etc/adduser.conf and creates /etc/adduser.conf.dpkg-save as a backup:

- Enable private home directories by default (LP: #48734)
  + Set DIR_MODE=0750 in the default adduser.conf
  + Change the description and default value to select private home
directories by default in debconf template
  + Change the DIR_MODE when private home directories is configured via
debconf from 0751 to 0750 to ensure files are truly private

  The .dpkg-save file shouldn't be present on debootstrapped system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/1977710/+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 1973607] Re: Please merge logrotate 3.19.0-2 (main) from Debian unstable (main)

Looks like this was obsoleted by
https://launchpad.net/ubuntu/+source/logrotate/3.20.1-1ubuntu1

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

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

Status in logrotate package in Ubuntu:
  New

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1973607/+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 1973607] Re: Please merge logrotate 3.19.0-2 (main) from Debian unstable (main)

Looks like this was obsoleted by
https://launchpad.net/ubuntu/+source/logrotate/3.20.1-1ubuntu1

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

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

Status in logrotate package in Ubuntu:
  New

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1973607/+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 1967576] Re: systemd: autopkgtest: tests-in-lxd fails because of remaining snap .mount units

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

** Changed in: systemd (Ubuntu Jammy)
 Assignee: (unassigned) => Lukas Märdian (slyon)

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

Title:
  systemd: autopkgtest: tests-in-lxd fails because of remaining snap
  .mount units

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

Bug description:
  [Impact]

   * The "tests-in-lxd/boot-and-services/test_no_failed" autopkgtest fails
   * it did not stand out due to LP: #1976607
   * we want to have proper autopkgtest coverage for systemd in Jammy LTS

  [Test Plan]

   * check autopkgtest logs on autopkgtest.ubuntu.com and make sure all
  instances of "boot-and-services" PASS (especially the "test_no_failed"
  test case. This includes running the test natively in autopkgtest and
  inside the "tests-in-lxd" container.

  [Where problems could occur]

   * other/new snapd-*.mount regressions could be hidden.
   * but snapd is being removed during systemd's tests anyway (introducing this 
failure)

  [Other Info]
   
   * The issue was not visible up to now, as the whole tests-in-lxd 
autopkgtests has been skipped: LP: #1976607

  
  === original description ===
  This build log provides an example of the problem: 
https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/s/systemd/20220331_190433_fdbbe@/log.gz.

  During setup for tests-in-lxd, an attempt is made to purge snapd, but
  this fails:

  [ ... ]
  Purging configuration files for snapd (2.54.3+21.10.1ubuntu0.2) ...
  Stopping snap.lxd.activate.service
  Stopping unit snap.lxd.activate.service
  Waiting until unit snap.lxd.activate.service is stopped [attempt 1]
  snap.lxd.activate.service is stopped.
  Removing snap.lxd.activate.service
  Stopping snap.lxd.daemon.service
  Stopping unit snap.lxd.daemon.service
  Waiting until unit snap.lxd.daemon.service is stopped [attempt 1]
  snap.lxd.daemon.service is stopped.
  Removing snap.lxd.daemon.service
  Stopping snap.lxd.user-daemon.service
  Stopping unit snap.lxd.user-daemon.service
  Waiting until unit snap.lxd.user-daemon.service is stopped [attempt 1]
  snap.lxd.user-daemon.service is stopped.
  Removing snap.lxd.user-daemon.service
  Stopping snap-core20-1378.mount
  Stopping unit snap-core20-1378.mount
  Waiting until unit snap-core20-1378.mount is stopped [attempt 1]
  snap-core20-1378.mount is stopped.
  Removing snap core20 and revision 1378
  Removing snap-core20-1378.mount
  Stopping snap-lxd-22672.mount
  Stopping unit snap-lxd-22672.mount
  Waiting until unit snap-lxd-22672.mount is stopped [attempt 1]
  snap-lxd-22672.mount is stopped.
  Removing snap lxd and revision 22672
  rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/cpuinfo': Function 
not implemented
  rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/meminfo': Function 
not implemented
  rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/stat': Function 
not implemented
  rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/uptime': Function 
not implemented
  rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/diskstats': 
Function not implemented
  rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/swaps': Function 
not implemented
  rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/loadavg': Function 
not implemented
  rm: cannot remove '/var/snap/lxd/common/var/lib/lxcfs/proc/slabinfo': 
Function not implemented
  rm: cannot remove 
'/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/cpu0': Operation not 
permitted
  rm: cannot remove 
'/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/cpuidle': Operation 
not permitted
  rm: cannot remove 
'/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/uevent': Function 
not implemented
  rm: cannot remove 
'/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/svm': Function not 
implemented
  rm: cannot remove 
'/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/hotplug': Operation 
not permitted
  rm: cannot remove 
'/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/offline': Function 
not implemented
  rm: cannot remove 
'/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/present': Function 
not implemented
  rm: cannot remove 
'/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/power': Operation 
not permitted
  rm: cannot remove 
'/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/dscr_default': 
Function not implemented
  rm: cannot remove 
'/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/probe': Function not 
implemented
  rm: cannot remove 
'/var/snap/lxd/common/var/lib/lxcfs/sys/devices/system/cpu/smt': Operation not 
permitted
  rm: cannot remove

[Touch-packages] [Bug 1951491] Re: Can't run snaps: .slice/session-1.scope is not a snap cgroup

2022-06-08 Thread Michael Joyner

Confirm issue is in latest LTS Xubuntu setup running x2go desktop
environment.

lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 22.04 LTS
Release:22.04
Codename:   jammy

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

Title:
  Can't run snaps: .slice/session-1.scope is not a snap cgroup

Status in snapd package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Confirmed
Status in snapd package in Debian:
  New

Bug description:
  I just upgraded from hirsute to impish using do-release-upgrade. On
  the upgraded system, I can't run either firefox or chromium (both of
  which worked fine under hirsute). Both fail with:

  /user.slice/user-NNN.slice/session-1.scope is not a snap cgroup where
  NNN is my uid

  With firefox, I was able to fix the problem with:

  snap remove --purge firefox
  apt purge firefox
  apt install firefox

  Now firefox works. But I tried the same thing substituting chromium-
  browser for firefox, and it didn't help: chromium fails with the same
  error message.

  I guess there must be something left over from the hirsute version of
  snapd that isn't getting noticed or cleared by the impish version?

  Someone suggested this might be related to bug 1850667, but that bug
  is marked fixed as of a couple months ago, and I just did this upgrade
  today. Also, it doesn't mention the error message I'm seeing.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: snapd 2.53+21.10ubuntu1
  ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18
  Uname: Linux 5.13.0-21-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Thu Nov 18 18:12:45 2021
  InstallationDate: Installed on 2020-04-29 (568 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: snapd
  UpgradeStatus: Upgraded to impish on 2021-11-18 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1951491/+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

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

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

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 1977968] Re: Security update tracking bug

2022-06-08 Thread Marc Deslauriers

This is also required:

https://git.kernel.org/pub/scm/bluetooth/bluez.git/commit/profiles/audio/avdtp.c?id=0388794dc5fdb73a4ea88bcf148de0a12b4364d4

-- 
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:
  New

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] [NEW] Security update tracking bug

2022-06-08 Thread Marc Deslauriers

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

Public security bug reported:

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

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

-- 
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:
  New

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 1977966] [NEW] Huawei MateStation S [AMD HD-Audio + Realtek ALC256] Rear analog output not detected

2022-06-08 Thread Riccardo Boninsegna

Public bug reported:

Hello, unfortunately I am not familiar with Ubuntu anymore since a
decade so hopefully I'm filing this bug correctly (I am using ubuntu-bug
which reportbug recommended to me); that said, my problem is...

The name-brand computer in the topic is almost perfectly Linux*
compatible, except for the fact the conventional green audio socket on
the back is not detected; however, the rear inputs (mic & line) as well
as the front jack (combo headphone+mic, only tested the former) do in
fact work fine!

* The problem also manifests in Devuan Chimaera (5.10 and 5.18) and
Fedora

I am willing to cooperate in testing if you need to!

Thanks in advance

lspci (relevant device only):
08:00.6 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h 
(Models 10h-1fh) HD Audio Controller [1022:15e3]

/proc/asound/cards (alsamixer):
0 [Generic]: HDA-Intel - HD-Audio Generic
 HD-Audio Generic at 0xd05c8000 irq 92
1 [Generic_1  ]: HDA-Intel - HD-Audio Generic
 HD-Audio Generic at 0xd05c irq 93

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
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
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  riki   1576 F pulseaudio
 /dev/snd/controlC0:  riki   1576 F pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Jun  8 12:07:54 2022
InstallationDate: Installed on 2022-04-26 (43 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:Generic_1 failed
Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic
Symptom_Type: Only some of outputs are working
Title: [HDA-Intel - HD-Audio Generic, playback] Playback problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/30/2021
dmi.bios.release: 1.13
dmi.bios.vendor: HUAWEI
dmi.bios.version: 1.13
dmi.board.asset.tag: N/A
dmi.board.name: PUM-WDX9-PCB-B1
dmi.board.vendor: HUAWEI
dmi.board.version: M1020
dmi.chassis.asset.tag: 3430210522028242
dmi.chassis.type: 3
dmi.chassis.vendor: HUAWEI
dmi.chassis.version: M1020
dmi.ec.firmware.release: 1.13
dmi.modalias: 
dmi:bvnHUAWEI:bvr1.13:bd04/30/2021:br1.13:efr1.13:svnHUAWEI:pnPUM-WDX9:pvrM1020:rvnHUAWEI:rnPUM-WDX9-PCB-B1:rvrM1020:cvnHUAWEI:ct3:cvrM1020:skuC100:
dmi.product.family: MateStation S
dmi.product.name: PUM-WDX9
dmi.product.sku: C100
dmi.product.version: M1020
dmi.sys.vendor: HUAWEI

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


** Tags: amd64 apport-bug jammy wayland-session

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

Title:
  Huawei MateStation S [AMD HD-Audio + Realtek ALC256] Rear analog
  output not detected

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hello, unfortunately I am not familiar with Ubuntu anymore since a
  decade so hopefully I'm filing this bug correctly (I am using ubuntu-
  bug which reportbug recommended to me); that said, my problem is...

  The name-brand computer in the topic is almost perfectly Linux*
  compatible, except for the fact the conventional green audio socket on
  the back is not detected; however, the rear inputs (mic & line) as
  well as the front jack (combo headphone+mic, only tested the former)
  do in fact work fine!

  * The problem also manifests in Devuan Chimaera (5.10 and 5.18) and
  Fedora

  I am willing to cooperate in testing if you need to!

  Thanks in advance

  lspci (relevant device only):
  08:00.6 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Family 17h 
(Models 10h-1fh) HD Audio Controller [1022:15e3]

  /proc/asound/cards (alsamixer):
  0 [Generic]: HDA-Intel - HD-Audio Generic
   HD-Audio Generic at 0xd05c8000 irq 92
  1 [Generic_1  ]: HDA-Intel - HD-Audio Generic
   HD-Audio Generic at 0xd05c irq 93

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  riki   1576 F pulseaudio
   /dev/snd/controlC0:  riki   1576 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jun  8 12:07:54 2022
  InstallationDate: Installed on 2022-04-26 (43 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  PackageArchitecture: all

[Touch-packages] [Bug 1972654] Re: [security review] Sync policykit-1 0.120-6 (main) from Debian experimental

2022-06-08 Thread Simon McVittie

More discussion here: https://salsa.debian.org/utopia-
team/polkit/-/merge_requests/6

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

Title:
  [security review] Sync policykit-1 0.120-6 (main) from Debian
  experimental

Status in policykit-1 package in Ubuntu:
  Confirmed

Bug description:
  Please sync policykit-1 0.120-6 (main) from Debian experimental

  Changelog entries since current kinetic version 0.105-33:
  https://tracker.debian.org/media/packages/p/policykit-1/changelog-0.120-6

  In particular, see the 0.120-4 changelog entry.

  I am filing a bug for Security Team review.
  Previously, Debian and Ubuntu developers agreed to keep using
  the last version of policykit before it switched to using JavaScript rules.

  But that was years ago. I believe Debian & Ubuntu are the only distros
  to have opted out of the new policykit. It is harder to maintain
  the old style rules when upstream rules use the new format. And it is
  a challenge to backport security and other bugfixes from the new
  series, without making mistakes or missing important details.

  There was a proposal to use duktape instead of mozjs for the JavaScript
  interpreter but I don't think that's been merged yet.

  It appears the Debian maintainer is considering switching Debian to the
  updated version in time for the next Debian Stable release (so uploading
  to unstable later this year).

  My requested deadline is August 25, Ubuntu 22.10 Feature Freeze.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1972654/+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 1965490] Re: Create multiple profiles per verb for conflicting devices

2022-06-08 Thread Sebastien Bacher

** Changed in: pulseaudio (Ubuntu)
 Assignee: Kai-Heng Feng (kaihengfeng) => (unassigned)

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

Title:
  Create multiple profiles per verb for conflicting devices

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

Bug description:
  Please include the following MR to make UCM's ConflictingDevice work
  properly under PulseAudio. Systems like Lenovo P520c requires the
  change to make audio port selection logic really work.

  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/merge_requests/596

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1965490/+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 1972654] Re: [security review] Sync policykit-1 0.120-6 (main) from Debian experimental

2022-06-08 Thread Simon McVittie

> There was a proposal to use duktape instead of mozjs for the JavaScript
> interpreter but I don't think that's been merged yet.

This was merged upstream, but unfortunately there has not yet been a
release that contains this change.

I don't really want to use an arbitrary git snapshot for security-
sensitive software; but then again, all releases of polkit have security
vulnerabilities (CVE-2021-4115 and CVE-2021-4034 were both fixed since
0.120) so in some ways an arbitrary git snapshot would be safer.

I was surprised to see that Fedora is currently patching polkit to use
mozjs91 (also merged upstream but not released), rather than patching it
to use duktape.

> My understanding is the Debian experimental version doesn't support both at 
> the same
> time, it's one or the other depending on which binary package you install.

That is correct. You can have the old PKLA policies with no runtime
dependency on mozjs by installing polkitd-pkla, or you can have the JS
policies with a runtime dependency on mozjs (which will switch to
duktape in future) by installing polkitd-javascript, but you can't have
both simultaneously.

There is a separate package in e.g. Fedora that extends the JS backend
to also read PKLA policies, but that's not currently in Debian or
Ubuntu, and it isn't clear to me that it should be.

I have also been very tempted to modify 0.120 so it only builds polkitd-
pkla (dropping the JS dependency) and upload that to unstable, versioned
0.105+really0.120 or something, as a way to get a PKLA backend that
isn't in a codebase from the distant past (look at the debian/patches of
0.105 and despair).

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-4034

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2021-4115

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

Title:
  [security review] Sync policykit-1 0.120-6 (main) from Debian
  experimental

Status in policykit-1 package in Ubuntu:
  Confirmed

Bug description:
  Please sync policykit-1 0.120-6 (main) from Debian experimental

  Changelog entries since current kinetic version 0.105-33:
  https://tracker.debian.org/media/packages/p/policykit-1/changelog-0.120-6

  In particular, see the 0.120-4 changelog entry.

  I am filing a bug for Security Team review.
  Previously, Debian and Ubuntu developers agreed to keep using
  the last version of policykit before it switched to using JavaScript rules.

  But that was years ago. I believe Debian & Ubuntu are the only distros
  to have opted out of the new policykit. It is harder to maintain
  the old style rules when upstream rules use the new format. And it is
  a challenge to backport security and other bugfixes from the new
  series, without making mistakes or missing important details.

  There was a proposal to use duktape instead of mozjs for the JavaScript
  interpreter but I don't think that's been merged yet.

  It appears the Debian maintainer is considering switching Debian to the
  updated version in time for the next Debian Stable release (so uploading
  to unstable later this year).

  My requested deadline is August 25, Ubuntu 22.10 Feature Freeze.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1972654/+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 1977710] Re: /etc/adduser.conf.dpkg-save created by postinst since 3.121ubuntu1

2022-06-08 Thread Tomáš Virtus

You are right, this happens even when deboostrapping Debian. Reported
against adduser' in Debian: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=1012492

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

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

Title:
  /etc/adduser.conf.dpkg-save created by postinst since 3.121ubuntu1

Status in adduser package in Ubuntu:
  Incomplete

Bug description:
  Since version 3.121ubuntu1 adduser's postinst script creates
  /etc/adduser.conf.dpkg-save file on debootstrap's root filesystem,
  that is, even when /etc/adduser.conf doesn't exist prior to package
  installation.

  Because of the change below the postinst script changes packaged
  /etc/adduser.conf and creates /etc/adduser.conf.dpkg-save as a backup:

- Enable private home directories by default (LP: #48734)
  + Set DIR_MODE=0750 in the default adduser.conf
  + Change the description and default value to select private home
directories by default in debconf template
  + Change the DIR_MODE when private home directories is configured via
debconf from 0751 to 0750 to ensure files are truly private

  The .dpkg-save file shouldn't be present on debootstrapped system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/1977710/+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 1977695] Re: Black Screen on Boot with X11

Thanks for the bug report.

Please:

1. Reproduce the black screen problem again.

2. Reboot in a mode that avoids the problem.

3. Run:

   journalctl -b-1 > prevboot.txt

4. Attach the resulting text file here.


** Tags added: hybrid i915 nvidia

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

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

Title:
  Black Screen on Boot with X11

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Description:  Ubuntu 22.04 LTS
  Release:  22.04

  xorg:
Installed: 1:7.7+23ubuntu2
Candidate: 1:7.7+23ubuntu2
Version table:
   *** 1:7.7+23ubuntu2 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  100 /var/lib/dpkg/status

  1. Uncomment WaylandEnable=false in /etc/gdm3/custom.conf
  2. Reboot.
  3. See black screen after selecting Ubuntu at GRUB prompt. Login screen never 
loads.

  Unplugging any external monitors appears to have no effect on the bug.
  I am aware that most users of Ubuntu 22.04 see an option at the login
  screen to change the display manager. I have never seen such an
  option. My machine always uses Wayland unless I modify
  /etc/gdm3/custom.conf directly. Using Wayland is detrimental to my
  health, because the Night Light feature does nothing. I have nvidia-
  driver-510 installed. I am happy to provide further debugging
  information upon request.

  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
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  510.73.05  Sat May  7 
05:30:26 UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun  5 15:47:31 2022
  DistUpgraded: 2022-05-07 18:27:00,043 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company HD Graphics 630 [103c:8259]
 Subsystem: Hewlett-Packard Company GP107M [GeForce GTX 1050 Mobile] 
[103c:8259]
  InstallationDate: Installed on 2020-12-09 (543 days ago)
  InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
  MachineType: HP OMEN by HP Laptop
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.15.0-35-generic 
root=UUID=13d7b775-7783-44fc-8e24-164127457fd4 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to jammy on 2022-05-08 (28 days ago)
  dmi.bios.date: 12/22/2020
  dmi.bios.release: 15.56
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.56
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8259
  dmi.board.vendor: HP
  dmi.board.version: 83.72
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 83.72
  dmi.modalias: 
dmi:bvnInsyde:bvrF.56:bd12/22/2020:br15.56:efr83.72:svnHP:pnOMENbyHPLaptop:pvrType1ProductConfigId:rvnHP:rn8259:rvr83.72:cvnHP:ct10:cvrChassisVersion:skuW2N35UAR#ABA:
  dmi.product.family: 103C_5335KV HP Omen
  dmi.product.name: OMEN by HP Laptop
  dmi.product.sku: W2N35UAR#ABA
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  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 22.0.1-1ubuntu2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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

[Touch-packages] [Bug 1977958] [NEW] binutils: addr2line: getting error "DWARF error: section .debug_str is larger than its filesize" when building Android 8.1 on Ubuntu 20.04

2022-06-08 Thread Jasper Vicenti

Public bug reported:

Getting the error "DWARF error: section .debug_str is larger than its
filesize" when building an Android app. This is traced back to a
security fix introduced in version 2.34-6ubuntu1.3 of binutils.
Reverting to 2.34-6ubuntu1 resolves the issue temporarily, but the fix
is to allow for .debug_str sizes up to 10x larger than the file size
(because of compression).

It looks like this fix was made already for Ubuntu 22.04 (binutils
2.38), but has not been backported to 20.04.

More detail on the issue and fix is available here:
https://sourceware.org/bugzilla/show_bug.cgi?id=28834

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

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

Title:
  binutils: addr2line: getting error "DWARF error: section .debug_str is
  larger than its filesize" when building Android 8.1 on Ubuntu 20.04

Status in binutils package in Ubuntu:
  New

Bug description:
  Getting the error "DWARF error: section .debug_str is larger than its
  filesize" when building an Android app. This is traced back to a
  security fix introduced in version 2.34-6ubuntu1.3 of binutils.
  Reverting to 2.34-6ubuntu1 resolves the issue temporarily, but the fix
  is to allow for .debug_str sizes up to 10x larger than the file size
  (because of compression).

  It looks like this fix was made already for Ubuntu 22.04 (binutils
  2.38), but has not been backported to 20.04.

  More detail on the issue and fix is available here:
  https://sourceware.org/bugzilla/show_bug.cgi?id=28834

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

The statement "apport-bug thinks it's running on Xorg" appears to be
false. Apport created this bug and correctly identified that you are
using Wayland (see the Tags section).

While all graphics bugs do get assigned to the 'xorg' source package by
default, that's a minor annoyance and I suspect isn't the main problem
you want to solve...

So what's the real issue we should discuss here? Is it the Cairo problem
from https://answers.launchpad.net/ubuntu/+question/702075 ?

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

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

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

Title:
  apport-bug thinks it's running on Xorg

Status in Ubuntu:
  Incomplete

Bug description:
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1977748/+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] Re: [i915] Analog VGA defaults to 1024x768 instead of 1080p

Please try booting the newer Ubuntu 22.04 release from USB:
https://ubuntu.com/download/desktop

If that fixes the problem then I would recommend installing 22.04
instead.


** Summary changed:

- my system is not showing me 1080p resolution
+ [i915] Analog VGA defaults to 1024x768 instead of 1080p

** Package changed: xorg (Ubuntu) => linux-hwe-5.13 (Ubuntu)

** Tags added: i915

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

Title:
  [i915] Analog VGA defaults to 1024x768 instead of 1080p

Status in linux-hwe-5.13 package in Ubuntu:
  New

Bug description:
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.13/+bug/1977649/+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 1977648] Re: GLX is rendered by Intel GPU only in Wayland

*** This bug is a duplicate of bug 1969130 ***
https://bugs.launchpad.net/bugs/1969130

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1969130, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** Package changed: gnome-shell (Ubuntu) => mutter (Ubuntu)

** Package changed: wayland (Ubuntu) => xwayland (Ubuntu)

** Summary changed:

- GLX is rendered by Intel GPU only in Wayland
+ [nvidia] GLX is rendered by Intel GPU only in Wayland

** Tags added: nvidia nvidia-wayland

** This bug has been marked a duplicate of bug 1969130
   [Feature requrest] nvidia offloading doesn't work on Wayland

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

Title:
  [nvidia] GLX is rendered by Intel GPU only in Wayland

Status in mutter package in Ubuntu:
  New
Status in xwayland package in Ubuntu:
  New

Bug description:
  I'm using Nvidia driver and PRIME profile is set to performance, however in 
Wayland only, GLX is rendered by Intel GPU and can't have Nvidia as default 
renderer.
  This is a problem because not all OpenGL applications can work with XWayland 
or by setting the ENV variables to use Nvidia.

  In Xorg Nvidia can be the default renderer with the same
  configuration.

  $ prime-select query
  nvidia

  $ glxinfo -B
  name of display: :1
  display: :1  screen: 0
  direct rendering: Yes
  Extended renderer info (GLX_MESA_query_renderer):
  Vendor: Intel (0x8086)
  Device: Mesa Intel(R) Xe Graphics (TGL GT2) (0x9a49)
  Version: 22.0.1
  Accelerated: yes
  Video memory: 3072MB
  Unified memory: yes
  Preferred profile: core (0x1)
  Max core profile version: 4.6
  Max compat profile version: 4.6
  Max GLES1 profile version: 1.1
  Max GLES[23] profile version: 3.2
  OpenGL vendor string: Intel
  OpenGL renderer string: Mesa Intel(R) Xe Graphics (TGL GT2)
  OpenGL core profile version string: 4.6 (Core Profile) Mesa 22.0.1
  OpenGL core profile shading language version string: 4.60
  OpenGL core profile context flags: (none)
  OpenGL core profile profile mask: core profile

  OpenGL version string: 4.6 (Compatibility Profile) Mesa 22.0.1
  OpenGL shading language version string: 4.60
  OpenGL context flags: (none)
  OpenGL profile mask: compatibility profile

  OpenGL ES profile version string: OpenGL ES 3.2 Mesa 22.0.1
  OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.1-0ubuntu0.1
  ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35
  Uname: Linux 5.15.0-35-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Sat Jun  4 15:15:50 2022
  DisplayManager: gdm3
  GsettingsChanges:
   
  InstallationDate: Installed on 2022-02-03 (120 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  RelatedPackageVersions: mutter-common 42.1-0ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to jammy on 2022-04-21 (43 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1977648/+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 1977545] Re: xrandr: Failed to get size of gamma for output default

Ubuntu 14.04 (trusty) reached end of standard support in April 2019:

  https://wiki.ubuntu.com/Releases

If you would like to continue with free support then please update to a
newer Ubuntu version and tell us if the problem still occurs.

If you would like to continue with Ubuntu 14.04 then there is a paid
support option detailed at https://www.ubuntu.com/esm


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

** Changed in: ubuntu
   Status: New => Won't Fix

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

Title:
  xrandr: Failed to get size of gamma for output default

Status in Ubuntu:
  Won't Fix

Bug description:
  spectrum@04397701017:/opt/swSpectrum/bin$ xrandr
  xrandr: Failed to get size of gamma for output default
  Screen 0: minimum 1920 x 1080, current 1920 x 1080, maximum 1920 x 1080
  default connected 1920x1080+0+0 0mm x 0mm
 1920x1080  77.0*

  Display setup

  GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name
  org.gnome.SettingsDaemon was not provided by any .service files

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-148.174~14.04.1-generic 4.4.177
  Uname: Linux 4.4.0-148-generic x86_64
  .tmp.unity.support.test.1:
   
  ApportVersion: 2.14.1-0ubuntu3.29
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Jun  3 17:50:08 2022
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:9bc8] (rev 03) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:09b4]
  InstallationDate: Installed on 2022-05-27 (7 days ago)
  InstallationMedia: VMI 14.04 - Release amd64
  MachineType: Dell Inc. Vostro 3681
  PlymouthDebug: Error: [Errno 13] Permission denied: 
'/var/log/plymouth-debug.log'
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-148-generic.efi.signed 
root=UUID=27e11871-0570-4fe3-91a8-53cd0df8d538 ro splash quiet 
i915.alpha_support=1
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/13/2022
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.8.2
  dmi.board.name: 0X9X1W
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.8.2:bd01/13/2022:svnDellInc.:pnVostro3681:pvr:rvnDellInc.:rn0X9X1W:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.name: Vostro 3681
  dmi.sys.vendor: Dell Inc.
  drirc:
   
   
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.11
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.7
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Fri Jun  3 17:29:43 2022
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.15.1-0ubuntu2.11

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1977545/+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 1976567] Re: Desktop resolution was set incorrectly until I booted up the PC AFTER turning on the monitor

I suspect when this bug is occurring you are seeing a Xorg session,
despite the fact this bug was created from a Wayland session. The reason
being bug 1919400...

Please reproduce the problem again and log in with the problem still
happening. While the problem is happening, please run:

  journalctl -b0 > journal.txt
  xrandr --verbose > xrandrv.txt

and attach the resulting text files here.


** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

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

Title:
  Desktop resolution was set incorrectly until I booted up the PC AFTER
  turning on the monitor

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Whenever I boot up my PC, I turn on the monitor as well. When this
  happens, the Intel Mesa graphics loads, and my screen ends up being
  small with large pixelated icons. The resolution was capped at
  1024x768. Only after I reboot my PC multiple times without changing
  the display settings did the resolution increase to 1680x1050, the
  correct resolution.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30
  Uname: Linux 5.15.0-33-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: Wed Jun  1 21:07:53 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family 
Integrated Graphics Controller [1025:0589]
  InstallationDate: Installed on 2022-05-22 (10 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Gateway DX4860
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic 
root=UUID=804dde02-f626-4837-9802-fcd2a3da1eeb ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/01/2011
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02-A1
  dmi.board.name: IPISB-VR
  dmi.board.vendor: Gateway
  dmi.board.version: 1.01
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gateway
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02-A1:bd08/01/2011:br4.6:svnGateway:pnDX4860:pvr:rvnGateway:rnIPISB-VR:rvr1.01:cvnGateway:ct3:cvr:sku:
  dmi.product.family: Gateway Desktop
  dmi.product.name: DX4860
  dmi.sys.vendor: Gateway
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1976567/+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 1976563] Re: All text and images in Gnome Shell are corrupted

*** This bug is a duplicate of bug 1876632 ***
https://bugs.launchpad.net/bugs/1876632

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1876632, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-510
(Ubuntu)

** This bug has been marked a duplicate of bug 1876632
   [nvidia] Corrupted/missing shell textures when switching users or resuming 
from suspend

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

Title:
  All text and images in Gnome Shell are corrupted

Status in nvidia-graphics-drivers-510 package in Ubuntu:
  New

Bug description:
  See attached screenshot.

  The corrupted text and images are only appearing in the Ubuntu desktop
  environment (like the login screen, dock, and the bar at top of the
  screen). Applications like Nautilus, the Terminal app, and Chrome are
  not affected.

  Maybe an Nvidia issue?

  I'm going to restart my PC which will probably fix the issue. I'll
  edit this if the issue persists after the restart.

  Edit: To anyone investigating this issue, I recommend looking at some
  of the other issues I've reported recently. It seems like they could
  all be connected somehow, with Nvidia as the common thread.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30
  Uname: Linux 5.15.0-33-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..06.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  510.73.05  Sat May  7 
05:30:26 UTC 2022
   GCC version:
  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: Wed Jun  1 18:58:22 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  DkmsStatus: nvidia/510.73.05, 5.15.0-33-generic, x86_64: installed (WARNING! 
Diff between built and installed module!) (WARNING! Diff between built and 
installed module!) (WARNING! Diff between built and installed module!) 
(WARNING! Diff between built and installed module!)
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GP106 [GeForce GTX 1060 3GB] [10de:1c02] (rev a1) 
(prog-if 00 [VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] GP106 [GeForce GTX 
1060 3GB] [1462:3287]
  InstallationDate: Installed on 2022-04-23 (39 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Gigabyte Technology Co., Ltd. B450M DS3H
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic 
root=UUID=c4ac1391-7d4e-4282-94ba-fbae3c4c044c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2019
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: Default string
  dmi.board.name: B450M DS3H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd01/25/2019:br5.13:svnGigabyteTechnologyCo.,Ltd.:pnB450MDS3H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB450MDS3H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: B450M DS3H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A

[Touch-packages] [Bug 1976567] Re: Desktop resolution was set incorrectly until I booted up the PC AFTER turning on the monitor

** Summary changed:

- Desktop scaling was set incorrectly until I booted up the PC AFTER turning on 
the monitor
+ Desktop resolution was set incorrectly until I booted up the PC AFTER turning 
on the monitor

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

Title:
  Desktop resolution was set incorrectly until I booted up the PC AFTER
  turning on the monitor

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Whenever I boot up my PC, I turn on the monitor as well. When this
  happens, the Intel Mesa graphics loads, and my screen ends up being
  small with large pixelated icons. The resolution was capped at
  1024x768. Only after I reboot my PC multiple times without changing
  the display settings did the resolution increase to 1680x1050, the
  correct resolution.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30
  Uname: Linux 5.15.0-33-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: Wed Jun  1 21:07:53 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family 
Integrated Graphics Controller [1025:0589]
  InstallationDate: Installed on 2022-05-22 (10 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Gateway DX4860
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-33-generic 
root=UUID=804dde02-f626-4837-9802-fcd2a3da1eeb ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/01/2011
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02-A1
  dmi.board.name: IPISB-VR
  dmi.board.vendor: Gateway
  dmi.board.version: 1.01
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gateway
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02-A1:bd08/01/2011:br4.6:svnGateway:pnDX4860:pvr:rvnGateway:rnIPISB-VR:rvr1.01:cvnGateway:ct3:cvr:sku:
  dmi.product.family: Gateway Desktop
  dmi.product.name: DX4860
  dmi.sys.vendor: Gateway
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1976567/+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 1977939] Re: logind does not recognize ID 17ef:3060 Lenovo ThinkPad Dock

2022-06-08 Thread Heinrich Schuchardt

systemd-249.11/hwdb.d/20-usb-vendor-model.hwdb has this entry:

usb:v17EFp3060*
 ID_MODEL_FROM_DATABASE=ThinkPad Dock

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

Title:
  logind does not recognize ID 17ef:3060 Lenovo ThinkPad Dock

Status in systemd package in Ubuntu:
  New

Bug description:
  lsusb identifies my docking station as: ID 17ef:3060 Lenovo ThinkPad
  Dock

  But when booting with the lid closed the laptop suspends before
  showing the login prompt with these settings;

  /etc/systemd/logind.conf
  [Login]
  #HandleLidSwitch=suspend
  #HandleLidSwitchExternalPower=suspend
  #HandleLidSwitchDocked=ignore

  The following is a workaround:

  /etc/systemd/logind.conf.d/10-lid.conf
  [Login]
  HandleLidSwitchExternalPower=ignore

  But I think discovering the USB device ID should be enough to stop
  suspending the laptop.

  Best regards

  Heinrich

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1977939/+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 1977939] [NEW] logind does not recognize ID 17ef:3060 Lenovo ThinkPad Dock

2022-06-08 Thread Heinrich Schuchardt

Public bug reported:

lsusb identifies my docking station as: ID 17ef:3060 Lenovo ThinkPad
Dock

But when booting with the lid closed the laptop suspends before showing
the login prompt with these settings;

/etc/systemd/logind.conf
[Login]
#HandleLidSwitch=suspend
#HandleLidSwitchExternalPower=suspend
#HandleLidSwitchDocked=ignore

The following is a workaround:

/etc/systemd/logind.conf.d/10-lid.conf
[Login]
HandleLidSwitchExternalPower=ignore

But I think discovering the USB device ID should be enough to stop
suspending the laptop.

Best regards

Heinrich

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

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

Title:
  logind does not recognize ID 17ef:3060 Lenovo ThinkPad Dock

Status in systemd package in Ubuntu:
  New

Bug description:
  lsusb identifies my docking station as: ID 17ef:3060 Lenovo ThinkPad
  Dock

  But when booting with the lid closed the laptop suspends before
  showing the login prompt with these settings;

  /etc/systemd/logind.conf
  [Login]
  #HandleLidSwitch=suspend
  #HandleLidSwitchExternalPower=suspend
  #HandleLidSwitchDocked=ignore

  The following is a workaround:

  /etc/systemd/logind.conf.d/10-lid.conf
  [Login]
  HandleLidSwitchExternalPower=ignore

  But I think discovering the USB device ID should be enough to stop
  suspending the laptop.

  Best regards

  Heinrich

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1977939/+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 1975909] Re: le bluetooth ne suit pas le rythme (perte de connexion au smartphone, reste connecté, garde l'adresse IP assigné alors que inutilisable), le bluetooth c'est Titanic