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

[Stephen Pflanze]

I too have a very similar error. Only when I attempt to launch firefox
remotely by SSH I get this:

/system.slice/ssh.service is not a snap cgroup

And this when I attempt launch firefox directly on my target computer:

WARNING: cannot start document portal: Expected portal at "/run/user/1000/doc", 
got "/home/stephen/.cache/doc"
/system.slice/sddm.service is not a snap cgroup

So I edited the three files as recommended by Michael Woods (woodsy) in
c44. The result is the target computer boots a dark, blank, monitor
screen. Fortunately the OS was nevertheless accessible by SSH, and so I
was able to restore the three files, and after doing so, I rebooted and
got the expected screen displays.

I am not sure I edited those three files correctly, so I attached those
edited files to this posting for your review. I also included in the
attachment the output from the command:

SNAPD_DEBUG=1 snap run firefox

I would deeply appreciate any help with this. It is a new computer, and
a new Ubuntu installation of mine.

** Attachment added: "Jira 1951491 Attachment 2022-07-13.zip"
   
https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1951491/+attachment/5603023/+files/Jira%201951491%20Attachment%202022-07-13.zip

-- 
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 X2Go:
  New
Status in snapd package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Confirmed
Status in x2goserver 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/x2go/+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 1981623] Re: Save As Dialog Box does not allow filename change

[Daniel van Vugt]

Sounds like it might be related to bug 1878076.

** Package changed: gnome-shell (Ubuntu) => gtk+3.0 (Ubuntu)

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

Title:
  Save As Dialog Box does not allow filename change

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  Ubuntu Mate 22.04 - Save-as dialog boxes (chrome, firefox, etc.) open
  as expected, but do not permit changing the filename. Text entry
  triggers the find function as opposed to file rename.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-shell 42.2-0ubuntu0.2
  ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
  Uname: Linux 5.15.0-40-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Wed Jul 13 14:33:18 2022
  DisplayManager: lightdm
  GsettingsChanges:
   b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.0'"
   b'org.gnome.desktop.app-folders' b'folder-children' b"['Utilities', 'YaST']"
   b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
   b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
   b'org.gnome.mutter' b'draggable-border-width' b'20'
  InstallationDate: Installed on 2022-05-21 (52 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions: mutter-common 42.2-0ubuntu1
  ShellJournal: -- No entries --
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1981623/+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 1981623] [NEW] Save As Dialog Box does not allow filename change

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Ubuntu Mate 22.04 - Save-as dialog boxes (chrome, firefox, etc.) open as
expected, but do not permit changing the filename. Text entry triggers
the find function as opposed to file rename.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-shell 42.2-0ubuntu0.2
ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
Uname: Linux 5.15.0-40-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: MATE
Date: Wed Jul 13 14:33:18 2022
DisplayManager: lightdm
GsettingsChanges:
 b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.0'"
 b'org.gnome.desktop.app-folders' b'folder-children' b"['Utilities', 'YaST']"
 b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
 b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
 b'org.gnome.mutter' b'draggable-border-width' b'20'
InstallationDate: Installed on 2022-05-21 (52 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: mutter-common 42.2-0ubuntu1
ShellJournal: -- No entries --
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy third-party-packages
-- 
Save As Dialog Box does not allow filename change
https://bugs.launchpad.net/bugs/1981623
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to gtk+3.0 in Ubuntu.

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

[Touch-packages] [Bug 1922715] Re: [Inspiron 5400 AIO, Realtek ALC274, Speaker, Internal] No sound at all (dummy output)

[Launchpad Bug Tracker]

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

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

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

Title:
  [Inspiron 5400 AIO, Realtek ALC274, Speaker, Internal] No sound at all
  (dummy output)

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Brand new PC (it is a descktop All-In-One with integrated speakers), no 
change to the bios, fresh install with no additional package.
  In the "sound" section of the parameters, the output menu has a single entry 
"dummy output" and the vu-meter below this menu tracks the input microphone, 
which works.
  (the UI is in Russian, it's a friend's PC, sorry if the English terms are not 
exactly right).
  Same with pavucontrol.
  Same on ubuntu 20.04 and 20.10.

  I first searched the internets and randomly tried the following additions to 
/etc/modprobe.d/alsa-base.conf (one by one), none of them worked
  options snd-hda-intel model=generic
  options snd-hda-intel model=alc274-dell-aio
  options snd-hda-intel model=auto
  options snd-hda-intel dmic_detect=0
  options snd-hda-intel index=2 # tested 0, 1, 2 and 8 -- wish I new what it 
means
  options snd-intel-dspcfg.dsp_drivers=1

  I was delighted to hear that Apport could play noise on this machine
  because before that I didn't get a click,  I was wondering if the HW
  was working.

  That's all. Bug reports are love letters.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: pulseaudio 1:14.2-1ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
  Uname: Linux 5.11.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  anton   908 F pulseaudio
   /dev/snd/pcmC0D0c:   anton   908 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  6 12:55:41 2021
  InstallationDate: Installed on 2021-04-02 (3 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Beta amd64 (20210402)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Встроенное аудио - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  anton   908 F pulseaudio
   /dev/snd/pcmC0D0c:   anton   908 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [Inspiron 5400 AIO, Realtek ALC274, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/04/2020
  dmi.bios.release: 1.1
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.0
  dmi.board.name: 0H1TR9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 13
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.0:bd09/04/2020:br1.1:svnDellInc.:pnInspiron5400AIO:pvr:rvnDellInc.:rn0H1TR9:rvrA00:cvnDellInc.:ct13:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5400 AIO
  dmi.product.sku: 0A06
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1922715/+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 1981645] [NEW] package initramfs-tools 0.140ubuntu13 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1

[Olin Russell]

Public bug reported:

Simply running sudo apt upgrade

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: initramfs-tools 0.140ubuntu13
ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
Uname: Linux 5.15.0-40-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5CheckResult: pass
Date: Wed Jul 13 16:01:05 2022
ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2022-02-27 (136 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226)
PackageArchitecture: all
Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.1
 apt  2.4.5
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.140ubuntu13 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package jammy

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

Title:
  package initramfs-tools 0.140ubuntu13 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Simply running sudo apt upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: initramfs-tools 0.140ubuntu13
  ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
  Uname: Linux 5.15.0-40-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl icp
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Wed Jul 13 16:01:05 2022
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2022-02-27 (136 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220226)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.10, Python 3.10.4, python3-minimal, 
3.10.4-0ubuntu2
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.5
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.140ubuntu13 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1981645/+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 1981431] Re: systemd-resolved: DNSSEC validation failed: incompatible-server

[Nick Rosbrook]

** Tags added: rls-jj-incoming

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

Title:
  systemd-resolved: DNSSEC validation failed: incompatible-server

Status in systemd package in Ubuntu:
  New

Bug description:
  Hi,

  I'm running Ubuntu 22.04 using systemd 249.11-0ubuntu3.4.

  2 days ago, I enabled DNSSEC=true through:

  # grep DNSSEC /etc/systemd/resolved.conf.d/dnssec.conf
  DNSSEC=yes

  After running some hours, systemd-resolved stop working. Log lines
  like incompatible-server starts to spam.

  Jul 09 13:51:41 htdocs systemd[1]: Starting Network Name Resolution...
  Jul 09 13:51:41 htdocs systemd-resolved[77507]: Positive Trust Anchors:
  Jul 09 13:51:41 htdocs systemd-resolved[77507]: . IN DS 20326 8 2 
e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
  Jul 09 13:51:41 htdocs systemd-resolved[77507]: Negative trust anchors: 
int.creativesandbox.de
  Jul 09 13:51:41 htdocs systemd-resolved[77507]: Using system hostname 
'htdocs'.
  Jul 09 13:51:41 htdocs systemd[1]: Started Network Name Resolution.
  Jul 09 15:40:20 htdocs systemd-resolved[77507]: DNSSEC validation failed for 
question 214.162.in-addr.arpa IN SOA: no-signature
  Jul 09 15:40:20 htdocs systemd-resolved[77507]: DNSSEC validation failed for 
question 76.214.162.in-addr.arpa IN DS: no-signature
  Jul 09 15:40:20 htdocs systemd-resolved[77507]: DNSSEC validation failed for 
question 126.76.214.162.in-addr.arpa IN DS: no-signature
  Jul 09 15:40:20 htdocs systemd-resolved[77507]: DNSSEC validation failed for 
question 126.76.214.162.in-addr.arpa IN SOA: no-signature
  Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for 
question . IN SOA: incompatible-server
  Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for 
question de IN DS: incompatible-server
  Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for 
question de IN SOA: incompatible-server
  Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for 
question your-server.de IN DS: incompatible-server
  Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for 
question your-server.de IN SOA: incompatible-server
  Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for 
question clients.your-server.de IN DS: incompatible-server
  Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for 
question 201.138.clients.your-server.de IN DS: incompatible-server
  Jul 10 03:16:18 htdocs systemd-resolved[77507]: DNSSEC validation failed for 
question static.237.11.201.138.clients.your-server.de IN : 
incompatible-server

  Mention here, I'm running multiple machines with the same config
  against the same upstream DNS server. From time to time, only one
  instance is stop working here.

  Running a manual query also fails here, for example:

  # resolvectl query noc3.wordfence.com
  noc3.wordfence.com: resolve call failed: DNSSEC validation failed: 
incompatible-server

  Running 'resolvectl reset-server-features' helps here and can be
  considered as workaround.

  # resolvectl query noc3.wordfence.com
  noc3.wordfence.com: resolve call failed: DNSSEC validation failed: 
incompatible-server
  # resolvectl reset-server-features
  # resolvectl query noc3.wordfence.com
  noc3.wordfence.com: 35.155.126.231 -- link: eth0

  -- Information acquired via protocol DNS in 26.5ms.
  -- Data is authenticated: no; Data was acquired via local or encrypted 
transport: no
  -- Data from: network

  By reading issues upstream looks like
  https://github.com/systemd/systemd/issues/6490.

  A fix is implemented (https://github.com/systemd/systemd/pull/18624)
  and released in 248 which is included in Ubuntu 22.04.

  But there is another fix around this issue
  (https://github.com/systemd/systemd/pull/20214) which is released in
  systemd 250.

  I would like to know if it's possible to backport this fix into Ubuntu
  22.04.

  Thanks.

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


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

[Touch-packages] [Bug 1948882] Re: PulseEffects does not properly initialize on startup

[Anon]

Version 4.8.7-1 from kinetic fixes this.

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

Title:
  PulseEffects does not properly initialize on startup

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

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

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

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

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


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

[Touch-packages] [Bug 1981622] Re: mtd device must be supplied (device name is empty)

[pelm]

** Description changed:

  After updating my 22.04 system (possibly caused by Systemd update). And
- now booting, dmesg have two error (red text):
+ now booting, dmesg has two errors (red text):
  
  'mtd device must be supplied (device name is empty)'.
  
  See line 8 and 134 in the included logfile.
  
  The system are booting as it should though, and the system are working
  like it should no errors at all.
  
  Is this maybe caused by 'efi-pstore-not-cleared-on-boot.patch' in
  systemd?
  
  I have an EFI mounted at boot but it isn't used because I have installed
  my system in legacy BIOS mode.
  
  Is this maybe the culprit?
  
  I could ignore the message but it isn't nice though.
  
  Regards

** Description changed:

  After updating my 22.04 system (possibly caused by Systemd update). And
- now booting, dmesg has two errors (red text):
+ now booting, dmesg has two errors:
  
  'mtd device must be supplied (device name is empty)'.
  
  See line 8 and 134 in the included logfile.
  
  The system are booting as it should though, and the system are working
  like it should no errors at all.
  
  Is this maybe caused by 'efi-pstore-not-cleared-on-boot.patch' in
  systemd?
  
  I have an EFI mounted at boot but it isn't used because I have installed
  my system in legacy BIOS mode.
  
  Is this maybe the culprit?
  
  I could ignore the message but it isn't nice though.
  
  Regards

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

Title:
  mtd device must be supplied (device name is empty)

Status in systemd package in Ubuntu:
  New

Bug description:
  After updating my 22.04 system (possibly caused by Systemd update).
  And now booting, dmesg has two errors:

  'mtd device must be supplied (device name is empty)'.

  See line 8 and 134 in the included logfile.

  The system are booting as it should though, and the system are working
  like it should no errors at all.

  Is this maybe caused by 'efi-pstore-not-cleared-on-boot.patch' in
  systemd?

  I have an EFI mounted at boot but it isn't used because I have
  installed my system in legacy BIOS mode.

  Is this maybe the culprit?

  I could ignore the message but it isn't nice though.

  Regards

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1981622/+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 1981622] [NEW] mtd device must be supplied (device name is empty)

[pelm]

Public bug reported:

After updating my 22.04 system (possibly caused by Systemd update). And
now booting, dmesg has two errors (red text):

'mtd device must be supplied (device name is empty)'.

See line 8 and 134 in the included logfile.

The system are booting as it should though, and the system are working
like it should no errors at all.

Is this maybe caused by 'efi-pstore-not-cleared-on-boot.patch' in
systemd?

I have an EFI mounted at boot but it isn't used because I have installed
my system in legacy BIOS mode.

Is this maybe the culprit?

I could ignore the message but it isn't nice though.

Regards

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

** Attachment added: "log.txt"
   https://bugs.launchpad.net/bugs/1981622/+attachment/5602928/+files/log.txt

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

Title:
  mtd device must be supplied (device name is empty)

Status in systemd package in Ubuntu:
  New

Bug description:
  After updating my 22.04 system (possibly caused by Systemd update).
  And now booting, dmesg has two errors (red text):

  'mtd device must be supplied (device name is empty)'.

  See line 8 and 134 in the included logfile.

  The system are booting as it should though, and the system are working
  like it should no errors at all.

  Is this maybe caused by 'efi-pstore-not-cleared-on-boot.patch' in
  systemd?

  I have an EFI mounted at boot but it isn't used because I have
  installed my system in legacy BIOS mode.

  Is this maybe the culprit?

  I could ignore the message but it isn't nice though.

  Regards

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1981622/+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 1969709] Re: libreoffice font selection unusably slow

[Harry W. Haines, III]

There is something else going on with fontconfig.  When you go to the
fonts viewer "Fonts", some of the DejaVu font families are not shown
correctly.  Some are duplicated and others are not shown.  The issue is
solid repeatable.  Install fonts-dejavu-extra and then launch "Fonts".
I'm not sure this is a libreoffice issue.  What patches did Ubuntu make
to it?

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

Title:
  libreoffice font selection unusably slow

Status in fontconfig package in Ubuntu:
  New
Status in libreoffice package in Ubuntu:
  Confirmed

Bug description:
  Trying to scroll through the font list in the menu bar, I experience
  an unacceptable degree of lagging. Just popping up the dropdown list
  takes 7-10 seconds and the system takes the same amount of time to
  respond to perform individidual scrolling gestures. The CPU jumps to
  100% and the whole system becomes unresponsive.

  I have tried deb, snap and even the packages offered on the site of
  the LibreOffice project. They all manifest the same behaviour. The
  only thing that works is disabling font previews. I have downgraded to
  7.2 for now, which appears to be unaffected.

  I have contacted the LibreOffice team and they tell me that this
  should be solved by fontconfig 2.14. Unfortunately, Ubuntu 22.04 is
  shipping 2.13...

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: libreoffice-core 1:7.3.2-0ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 21 05:01:24 2022
  ExecutablePath: /usr/lib/libreoffice/program/soffice.bin
  InstallationDate: Installed on 2022-03-27 (24 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
  SourcePackage: libreoffice
  UpgradeStatus: No upgrade log present (probably fresh install)

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

[Michał Małoszewski]

** Changed in: libmnl (Ubuntu Jammy)
 Assignee: (unassigned) => Michał Małoszewski (michal-maloszewski99)

-- 
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 Jammy:
  Triaged
Status in libmnl package in Debian:
  Fix Committed

Bug description:
  [Test Case]
  $ cat > /tmp/hello.c <

  int main() {
  printf("Hello world! (and LP: #1971523)\n");
  }
  EOF
  $ 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

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

[Christian Ehrhardt ]

** No longer affects: libmnl (Ubuntu Impish)

-- 
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 Jammy:
  Triaged
Status in libmnl package in Debian:
  Fix Committed

Bug description:
  [Test Case]
  $ cat > /tmp/hello.c <

  int main() {
  printf("Hello world! (and LP: #1971523)\n");
  }
  EOF
  $ 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

  [Original Report]
  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 1903516] Re: aborted (core dumped) when using ConnectTimeout > 2147483

[Athos Ribeiro]

** Changed in: openssh (Ubuntu Impish)
 Assignee: Athos Ribeiro (athos-ribeiro) => (unassigned)

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

Title:
  aborted (core dumped) when using ConnectTimeout > 2147483

Status in portable OpenSSH:
  Unknown
Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Bionic:
  Fix Released
Status in openssh source package in Focal:
  Fix Released
Status in openssh source package in Impish:
  Fix Committed
Status in openssh source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  Setting ConnectTimeout to a value higher than INT_MAX/1000 causes the
  ssh client to crash. This happens due to an integer overflow which was
  fixed upstream with the patch being proposed for this SRU, which caps
  the effective value for that option at INT_MAX/1000.

  While use cases triggering the bug may be uncommon, the patch is
  straightforward and the fix could be staged for the next time an
  upload is needed.

  
  [Test Plan]

  Running

  ssh -o "ConnectTimeout=$(perl -e 'use POSIX; my $max =
  int(POSIX::INT_MAX/1000)+1; print "$max\n";')" localhost

  triggers the error. In this case, the ssh client will crash and

  Aborted

  will be printed to stderr.

  By applying the proposed fix, running the same command should allow
  the ssh connection to proceed to the authentication steps.

  [Where problems could occur]

  Most problems would manifest due to rebuilding the package (e.g.,
  dependency changes). Since this proposal is to stage these SRUs, such
  risk is being deferred to be shared with the next, more critical,
  upload.

  [Other Info]
   
  All the SRUs proposed here should be staged due to the low priority nature of 
the bug.

  [Original bug report]

  The ssh client fails with the message "Aborted (core dumped)" when
  setting the ConnectTimeout to 2147484 or higher.

  lsb_release: Linux Mint 20 (but also tested this on latest ubuntu:20.04 
docker container)
  openssh-client version: 1:8.2p1-4ubuntu0.1

  I expected that either the connect timeout would be used correctly, or
  that it would fail with a proper error message saying the connect
  timeout can't be higher than 2147483.

  What happened:

  $ ssh -o "ConnectTimeout=2147484" localhost
  Aborted (core dumped)

To manage notifications about this bug go to:
https://bugs.launchpad.net/openssh/+bug/1903516/+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 1922414] Re: ssh-agent fails to start (has_option: command not found)

[Chris Wilson]

I'm affected by this on jammy with lightdm and wmaker.

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

Title:
  ssh-agent fails to start (has_option: command not found)

Status in gdm3 package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  I have been using ssh-agent for years and since I upgraded my system
  to Ubuntu 21.04/groovy, ssh-agent fails to start.

  Here is the error message:

  # journalctl | grep ssh-agent
  [...]
  Apr 02 20:16:32 vougeot /usr/libexec/gdm-x-session[3752]: 
/etc/X11/Xsession.d/90x11-common_ssh-agent: line 9: has_option: command not 
found

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: x11-common 1:7.7+22ubuntu1
  Uname: Linux 5.11.11-05-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu61
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Sat Apr  3 09:02:46 2021
  Dependencies: lsb-base 11.1.0ubuntu2
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  DkmsStatus:
   tuxedo-keyboard, 3.0.4, 5.11.0-13-generic, x86_64: installed
   tuxedo-keyboard, 3.0.4, 5.11.0-13-lowlatency, x86_64: installed
   tuxedo-keyboard, 3.0.4, 5.11.11-05-lowlatency, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation TigerLake GT2 [Iris Xe Graphics] [8086:9a49] (rev 01) 
(prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer Iris Xe Graphics [1558:51a1]
  MachineType: TUXEDO TUXEDO InfinityBook S 15 Gen6
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.11-05-lowlatency 
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor 
quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/07/2020
  dmi.bios.release: 7.3
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 1.07.03RTR
  dmi.board.name: NS50MU
  dmi.board.vendor: TUXEDO
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.ec.firmware.release: 7.2
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr1.07.03RTR:bd09/07/2020:br7.3:efr7.2:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50MU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: TUXEDO InfinityBook S 15 Gen6
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: TUXEDO
  version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu4
  version.libdrm2: libdrm2 2.4.104-1build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-1
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.1-1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.10-3ubuntu5
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2build1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1922414/+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 1979639] Re: Apps expecting an OpenSSL 1.1 -formatted openssl.cnf fail

[Robie Basak]

Thank you for working on this!

The proposed SRU carries quite a bit of regression risk I think, since
there are many packages both in and out of the archive that may parse
this file under various different circumstances. A regression that leads
to a TLS failure, possibly across multiple packages at once, would be
severe.

I wonder if it's acceptable to just fix nodejs in the archive to be able
to handle this situation, on the basis that software (whether in the
archive or not) needs to be able to be compatible with libssl3 if it
expects to both examine the *system* openssl configuration and be
functional on Ubuntu 22.04? This alternate approach would carry far less
risk, and would avoid the conffile prompt (in cases where users have
changed it). Why wouldn't this be acceptable?

If not, how long must we keep compatibility against libssl1.1 in our
shipped openssl.cnf? What's the deprecation plan?

> either separately packaged (e.g. as an upgrade leftover)

These packages would be broken and not expected to work. Presumably they
depended on libssl1.1 anyway. What would be the consequence of openssl
declaring a Breaks against libssl1.1?

If we do end up proceeding with the approach you've put in the upload
queue, then I think your Test Plan additionally needs:

* to verify that the default provider is indeed still being used by
libssl3 (ie. the wrong configuration doesn't get used by accident)

* a basic smoke test of libssl3 to ensure that we aren't about to break
the normal use of libssl3 for the entire archive


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

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

Title:
  Apps expecting an OpenSSL 1.1 -formatted openssl.cnf fail

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

Bug description:
  [Impact] 
  While the default configuration works fine for every package that uses the 
system libssl3, any software that uses libssl1.1, either separately packaged 
(e.g. as an upgrade leftover) or vendored in (as in nodejs in our own archive) 
will fail to load the configuration as they don't have any notion of providers.

  If the provider section isn't present in the configuration, libssl3
  will load the default provider, which means that commenting out the
  section won't impact the behavior of standard libssl3 users.

  [Test Plan]

  On a system with a pristine openssl configuration:

  $ sudo apt install nodejs
  $ nodejs -  const { privateKey, publicKey } = crypto.generateKeyPairSync('rsa', { 
modulusLength: 2048 });
  …
  > var sign = crypto.createSign('RSA-SHA256')
  …
  > sign.update(Buffer.from("hello"))
  …
  > sign.sign(privateKey.export({type: 'pkcs1', format: 'pem'}))
  Uncaught:
  Error: error:25066067:DSO support routines:dlfcn_load:could not load the 
shared library
  at Sign.sign (node:internal/crypto/sig:131:29) {
    opensslErrorStack: [
  'error:0E076071:configuration file routines:module_run:unknown module 
name',
  'error:0E07506E:configuration file routines:module_load_dso:error loading 
dso',
  'error:25070067:DSO support routines:DSO_load:could not load the shared 
library'
    ],
    library: 'DSO support routines',
    function: 'dlfcn_load',
    reason: 'could not load the shared library',
    code: 'ERR_OSSL_DSO_COULD_NOT_LOAD_THE_SHARED_LIBRARY'
  }

  Removing the relevant provider section lines (the Debian patch doesn't
  apply cleanly, hence the use of sed) fixes it:

  ~ $ sed -i '/_sect\b/s/^/# /' /etc/ssl/openssl.cnf
  ~ $ node
  Welcome to Node.js v16.15.0.
  Type ".help" for more information.
  > const { privateKey, publicKey } = crypto.generateKeyPairSync('rsa', { 

[Touch-packages] [Bug 1979639] Re: openssl 3.0.3-7 needs port from sid to jammy

[Robie Basak]

> openssl 3.0.3-7 needs port from sid to jammy

This is presuming the solution, rather than describing the problem, so
I'll amend this.

** Summary changed:

- openssl 3.0.3-7 needs port from sid to jammy
+ Apps expecting an OpenSSL 1.1 -formatted openssl.cnf fail

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

Title:
  Apps expecting an OpenSSL 1.1 -formatted openssl.cnf fail

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

Bug description:
  [Impact] 
  While the default configuration works fine for every package that uses the 
system libssl3, any software that uses libssl1.1, either separately packaged 
(e.g. as an upgrade leftover) or vendored in (as in nodejs in our own archive) 
will fail to load the configuration as they don't have any notion of providers.

  If the provider section isn't present in the configuration, libssl3
  will load the default provider, which means that commenting out the
  section won't impact the behavior of standard libssl3 users.

  [Test Plan]

  On a system with a pristine openssl configuration:

  $ sudo apt install nodejs
  $ nodejs -  const { privateKey, publicKey } = crypto.generateKeyPairSync('rsa', { 
modulusLength: 2048 });
  …
  > var sign = crypto.createSign('RSA-SHA256')
  …
  > sign.update(Buffer.from("hello"))
  …
  > sign.sign(privateKey.export({type: 'pkcs1', format: 'pem'}))
  Uncaught:
  Error: error:25066067:DSO support routines:dlfcn_load:could not load the 
shared library
  at Sign.sign (node:internal/crypto/sig:131:29) {
    opensslErrorStack: [
  'error:0E076071:configuration file routines:module_run:unknown module 
name',
  'error:0E07506E:configuration file routines:module_load_dso:error loading 
dso',
  'error:25070067:DSO support routines:DSO_load:could not load the shared 
library'
    ],
    library: 'DSO support routines',
    function: 'dlfcn_load',
    reason: 'could not load the shared library',
    code: 'ERR_OSSL_DSO_COULD_NOT_LOAD_THE_SHARED_LIBRARY'
  }

  Removing the relevant provider section lines (the Debian patch doesn't
  apply cleanly, hence the use of sed) fixes it:

  ~ $ sed -i '/_sect\b/s/^/# /' /etc/ssl/openssl.cnf
  ~ $ node
  Welcome to Node.js v16.15.0.
  Type ".help" for more information.
  > const { privateKey, publicKey } = crypto.generateKeyPairSync('rsa', { 
modulusLength: 2048 });
  …
  > var sign = crypto.createSign('RSA-SHA256')
  …
  > sign.update(Buffer.from("hello"))
  …
  > sign.sign(privateKey.export({type: 'pkcs1', format: 'pem'}))
  

  I realize there is no libssl1.1 on jammy, but a statically linked
  OpenSSL is not uncommon (Node.js being a very prominent example).

  Would it be possible to get this Debian sid change ported to jammy?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nodejs/+bug/1979639/+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 1980239] Re: Update gstreamer to 1.20.3

[Jeremy Bicha]

I installed gst-plugins-good1.0, gst-plugins-bad1.0, gst-libav1.0, and
gstreamer1.0 from jammy-proposed. I verified that I was able to play a
variety of audio files with Rhythmbox and video files from Totem. The
build tests also passed.

** Tags removed: verification-needed verification-needed-jammy
** Tags added: jammy upgrade-software-version verification-done 
verification-done-jammy

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

Title:
  Update gstreamer to 1.20.3

Status in gst-libav1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-ugly1.0 package in Ubuntu:
  Fix Released
Status in gst-python1.0 package in Ubuntu:
  Fix Released
Status in gst-rtsp-server1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-editing-services1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-vaapi package in Ubuntu:
  Fix Released
Status in gstreamer1.0 package in Ubuntu:
  Fix Released
Status in gst-libav1.0 source package in Jammy:
  Fix Committed
Status in gst-plugins-bad1.0 source package in Jammy:
  Fix Committed
Status in gst-plugins-good1.0 source package in Jammy:
  Fix Committed
Status in gst-plugins-ugly1.0 source package in Jammy:
  In Progress
Status in gst-python1.0 source package in Jammy:
  Won't Fix
Status in gst-rtsp-server1.0 source package in Jammy:
  In Progress
Status in gstreamer-editing-services1.0 source package in Jammy:
  Incomplete
Status in gstreamer-vaapi source package in Jammy:
  Triaged
Status in gstreamer1.0 source package in Jammy:
  Fix Committed

Bug description:
  Impact
  --
  Since Ubuntu 22.04 LTS's release with gstreamer 1.20.1, there have been two 
bugfix stable releases. 

  https://gstreamer.freedesktop.org/releases/1.20/#1.20.2
  https://gstreamer.freedesktop.org/releases/1.20/#1.20.3

  Test Case 1
  ---
  We now run upstream's test suite for most gstreamer components at build time 
and fail the build for errors on our key desktop architectures, amd64 & arm64.

  Ensure the builds succeeed.

  Test Case 2
  ---
  Play a variety of videos in Totem. Play a variety of audio tracks in 
Rhythmbox. Try to stream audio and/or video. Try to install a missing codec.

  In all cases, make sure that everything which worked before still
  works.

  What Could Go Wrong
  ---
  If one of the fixes is bad then it might break video or audio playback, or 
could crash any application that tries to use gstreamer.

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