[Touch-packages] [Bug 2050040] Re: Ubuntu 22.04.3 LTS top bar sound icon flickers

[kodi]

on fresh install of Ubuntu 22.04.3 lts this is the problem from the
motherboard audio controller and some how windows got this working after
the right driver install or something stop it form doing that same
thing, but i wish i knew how to do it on Ubuntu with the driver install.


i removed all audio drivers and still the beeping and noise on that sound port 
out/controller. something is turning it off and on or mute and unmute not sure 
why it is cycling. if the line out audio would stop cycling then it would be 
fine

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

Title:
  Ubuntu 22.04.3 LTS top bar sound icon flickers

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 22.04.3 LTS top bar right corner flicker icons All the icons flicker 
to the right about 2 squares to the right, they keep doing that like something 
is download or something is going on. This is just a new install fresh download 
from Ubuntu website and install on SSD drive from USB iso.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2024-01-21 (2 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  RelatedPackageVersions: mutter-common 42.9-0ubuntu5
  Tags:  jammy
  Uname: Linux 6.5.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2050040/+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 2050040] Re: Ubuntu 22.04.3 LTS top bar sound icon flickers

[kodi]

GIGABYTE GA-Z87N-WIFI LGA 1150 Intel Z87 HDMI SATA 6Gb/s USB 3.0 Mini ITX Intel 
Motherboard
Audio Chipset   Realtek ALC892
Audio Channels  7.1 Channels
Back I/O Ports  1 x Optical S/PDIF Out / 1 x PS/2 Keyboard/Mouse Combo / 2 x 
HDMI / 2 x USB 2.0/1.1 / 4 x USB 3.0
PS/21 x PS/2 keyboard/mouse port
Video Ports 1 x DVI-I
HDMI2 x HDMI
USB 3.0 4 x USB 3.0
USB 1.1/2.0 2 x USB 2.0
S/PDIF Out  1 x Optical
Audio Ports 5 x audio jacks (Center/Subwoofer Speaker Out, Rear Speaker 
Out, Line In, Line Out, Mic In)
Onboard USB 1 x USB 3.0/2.0 header
1 x USB 2.0/1.1 header
Other Connectors1 x 24-pin ATX main power connector
1 x 4-pin ATX 12V power connector
4 x SATA 6Gb/s connectors
1 x CPU fan header
1 x system fan header
1 x front panel header
1 x front panel audio header
1 x serial port header
1 x S/PDIF Out header
1 x Clear CMOS jumper
Additional InformationDate First Available  June 17, 2013
https://www.newegg.com/p/N82E16813128615

https://www.gigabyte.com/Motherboard/GA-Z87N-WIFI-
rev-1x/support#support-dl-driver

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

Title:
  Ubuntu 22.04.3 LTS top bar sound icon flickers

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 22.04.3 LTS top bar right corner flicker icons All the icons flicker 
to the right about 2 squares to the right, they keep doing that like something 
is download or something is going on. This is just a new install fresh download 
from Ubuntu website and install on SSD drive from USB iso.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2024-01-21 (2 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  RelatedPackageVersions: mutter-common 42.9-0ubuntu5
  Tags:  jammy
  Uname: Linux 6.5.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2050040/+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 2050040] Re: Ubuntu 22.04.3 LTS top bar sound icon flickers

[Daniel van Vugt]

Please try this command to see if it stops the problem:

  gnome-extensions disable mediacontr...@cliffniff.github.com

You should also avoid using 'sudo apt remove --purge' because it will
break the system even more.

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

Title:
  Ubuntu 22.04.3 LTS top bar sound icon flickers

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 22.04.3 LTS top bar right corner flicker icons All the icons flicker 
to the right about 2 squares to the right, they keep doing that like something 
is download or something is going on. This is just a new install fresh download 
from Ubuntu website and install on SSD drive from USB iso.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2024-01-21 (2 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  RelatedPackageVersions: mutter-common 42.9-0ubuntu5
  Tags:  jammy
  Uname: Linux 6.5.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2050040/+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 2051068] Re: GUI crashed after installed proposed package libegl-mesa0

[Kevin Yeh]

** Tags added: cert-sru

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

Title:
  GUI crashed after installed proposed package libegl-mesa0

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  [Summary]
  After installed proposed package libegl-mesa0, reboot system.

  GUI crashed but still able to access system by ssh.

  [Steps to reproduce]
  1. Boot into OS
  2. sudo apt update
  3. sudo apt upgrade
  4. After upgrade process finished, reboot system.
  5. GUI crashed.

  [Expected result]
  GUI displayed normally

  [Actual result]
  GUI crashed

  [Failure rate]
  100%

  Tester comments
  ---
  if we don't upgrade libegl-mesa0, GUI will be fine.

  [Additional information]
  CID: 202303-31429
  SKU: MYBY-DVT2-C5
  Image: dell-bto-jammy-jellyfish-muk-X105-20231026-26_A02.iso
  system-manufacturer: Dell Inc.
  system-product-name: Precision 5680
  CPU: Intel(R) Core(TM) i7-13700H
  kernel-version: 6.1.0-1028-oem

  [Stage]
  Issue reported and root cause of crash found.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2051068/+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 2051068] Re: GUI crashed after installed proposed package libegl-mesa0

[Launchpad Bug Tracker]

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

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

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

Title:
  GUI crashed after installed proposed package libegl-mesa0

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  [Summary]
  After installed proposed package libegl-mesa0, reboot system.

  GUI crashed but still able to access system by ssh.

  [Steps to reproduce]
  1. Boot into OS
  2. sudo apt update
  3. sudo apt upgrade
  4. After upgrade process finished, reboot system.
  5. GUI crashed.

  [Expected result]
  GUI displayed normally

  [Actual result]
  GUI crashed

  [Failure rate]
  100%

  Tester comments
  ---
  if we don't upgrade libegl-mesa0, GUI will be fine.

  [Additional information]
  CID: 202303-31429
  SKU: MYBY-DVT2-C5
  Image: dell-bto-jammy-jellyfish-muk-X105-20231026-26_A02.iso
  system-manufacturer: Dell Inc.
  system-product-name: Precision 5680
  CPU: Intel(R) Core(TM) i7-13700H
  kernel-version: 6.1.0-1028-oem

  [Stage]
  Issue reported and root cause of crash found.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2051068/+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 2050040] Re: Ubuntu 22.04.3 LTS top bar sound icon flickers

[kodi]

GIGABYTE GA-Z87N-WIFI LGA 1150 Intel Z87 HDMI SATA 6Gb/s USB 3.0 Mini ITX Intel 
Motherboard
Audio Chipset   Realtek ALC892
Audio Channels  7.1 Channels
Back I/O Ports  1 x Optical S/PDIF Out / 1 x PS/2 Keyboard/Mouse Combo / 2 x 
HDMI / 2 x USB 2.0/1.1 / 4 x USB 3.0
PS/21 x PS/2 keyboard/mouse port
Video Ports 1 x DVI-I
HDMI2 x HDMI
USB 3.0 4 x USB 3.0
USB 1.1/2.0 2 x USB 2.0
S/PDIF Out  1 x Optical
Audio Ports 5 x audio jacks (Center/Subwoofer Speaker Out, Rear Speaker 
Out, Line In, Line Out, Mic In)
Onboard USB 1 x USB 3.0/2.0 header
1 x USB 2.0/1.1 header
Other Connectors1 x 24-pin ATX main power connector
1 x 4-pin ATX 12V power connector
4 x SATA 6Gb/s connectors
1 x CPU fan header
1 x system fan header
1 x front panel header
1 x front panel audio header
1 x serial port header
1 x S/PDIF Out header
1 x Clear CMOS jumper
Additional InformationDate First Available  June 17, 2013
https://www.newegg.com/p/N82E16813128615

https://www.gigabyte.com/Motherboard/GA-Z87N-WIFI-
rev-1x/support#support-dl-driver

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

Title:
  Ubuntu 22.04.3 LTS top bar sound icon flickers

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 22.04.3 LTS top bar right corner flicker icons All the icons flicker 
to the right about 2 squares to the right, they keep doing that like something 
is download or something is going on. This is just a new install fresh download 
from Ubuntu website and install on SSD drive from USB iso.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2024-01-21 (2 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  RelatedPackageVersions: mutter-common 42.9-0ubuntu5
  Tags:  jammy
  Uname: Linux 6.5.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2050040/+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 2049885] Re: Merge console-setup (1.223) from Debian

[Launchpad Bug Tracker]

This bug was fixed in the package console-setup - 1.223ubuntu1

---
console-setup (1.223ubuntu1) noble; urgency=medium

  * Merge with Debian unstable (LP: #2049885). Remaining changes:
- debian/clean: Delete Keyboard/tree-keymaps/ on clean
- Add an apport hook
- If the locale is C during configuration, only set CHARMAP to
  ISO-8859-15 on kFreeBSD; otherwise restore the previous behaviour
  from before the kFreeBSD port of using UTF-8 in that case.
- Do not set default FONTFACE or FONTSIZE for Lat15, kernel has built-in
  Terminus font, at multitiple sizes, and it correctly selects low/high
  dpi font size, based on screen resolution.
- Set keymap and font in the initramfs if possible and sensible
  debian/vtrgb, debian/vtrgb.vga,
  debian/console-setup-linux.setvtrgb.service, debian/rules,
  debian/console-setup-linux.{postinst, prerm}: use Ubuntu's virtual
  terminal color scheme by default, with a VGA color scheme available
  as an alternative.
- Handle unattended upgrades without breaking plymouth when updating
  console fonts.
- Tolerate absence of setupcon in postinst scripts. Should be fixed by
  refactoring to not have a keyboard-configuration package that needs
  to call setupcon without depending on it.
- Don't copy keyboard-configuration questions to /target in OEM mode.
  oem-config will ask them later, and copying these confuses it.
- Added templates for keyboard detection
- debian/control: drop freebsd-specific packages
- If the detect-keyboard debconf plugin is available
  (cdebconf-newt-detect-keys in the installer), then offer to use it to
  detect the keyboard layout.
- keyboard-configuration.config: While sourcing config files to re-seed
  debconf, treat missing XKBOPTIONS as empty.
- Fix default keyboard selection for language/country combinations
  lacking a proper combined locale.
- debian/keyboard-configuration.config: lower the priority for the layout
  question.
- Map ppc64el/* to XKBMODEL=pc105
- Set default for Dutch to us(intl), not just us.
- Set default layout for Kurdish to tr(ku)
- Set default layout for Vietnam to 'us'
- debian/keyboard-configuration.config: change back the french default
  layout to be fr+oss and not fr+latin9
- debian/keyboard-configuration.config: Drop the xkb-keymap bits once
  again as we're not ready for those yet, as it's currently causing an
  invalid default layout in the installer.
- keyboard-configuration.{config,templates}: There is no good default
  for layout toggling, stop pretending there is.  Console users can set
  one with dpkg-reconfigure or editing /etc/defaults/keyboard
- keyboard_present.sh: Quiet config/postinst when we have no USB devices
- debian/preprocessor: revert the removal of keyboard names (for size) of
  console-setup-udeb: we do need those, since we don't use the simplified
  xkb-keymap template from Debian just yet: this way we can still show
  country/language names when selecting a keyboard, layout or variant
- Make COPYRIGHT a symlink to debian/copyright
- Don't cat over the keymaps; they're already moved to the right place.
- Include pc105.tree for ubiquity
- Keyboard/keymaptree tool to analyze key maps
- Add Keyboard/Makefile rule to build pc105.tree
- debian/control: Build depend on keymapper
- Make sure we give a meaningful name to ch layouts: "Switzerland"
  instead of "German (Switzerland), since it includes French too.
- Keyboard/Makefile: make sure KeyboardNames.pl is built with
  accurate data from xkb-data.
- xmlreader, KeyboardNames.pl: Added model entry to skip model selection
- Fix command injection in ckbcomp
- Generate a locale locally for translating keyboard names in
  kbdnames-maker.
- setupcon:
  - use only /run for tempfiles with /tmp as a non-root fallback.
  - handle compressed console maps and font files.
  - Map XKBMODEL=SKIP to '' for compatibility with existing
configs.
  - the variables are taken from a config file which, if changed,
invalidates the cache.
  - there is only ever one keyboard map per system.
  - the system should not have to resolve filenames to find the keymap
cache on boot.
  - Explicitly exit 0, so that postinsts don't fail in the event that
loadkeys can't find a console.
- Add noudeb build profile
- generated file Keyboard/KeyboardNames.pl

console-setup (1.223) unstable; urgency=medium

  * Team upload

  [ Updated translations ]
  * Gujarati (gu.po) by Kartik Mistry
  * Malayalam (ml.po) by Anish Sheela
  * Romanian (ro.po) by NicolaeFericitu
  * Turkish (tr.po) by Fatih Altun

 -- Heinrich Schuchardt   Fri, 19 Jan
2024 21:37:06 +0100

** Changed in: console-setup (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this 

[Touch-packages] [Bug 2050040] Re: Ubuntu 22.04.3 LTS top bar sound icon flickers

[kodi]

When i go into the onboard motherboard settings and disable audio
controller, it stop the audio beeping and the flicker and sound problem
is gone for the main onboard motherboard audio. When i enable it back
all the beeping and flicker in settings audio and dock bark come back,
only for the onboard audio controller

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

Title:
  Ubuntu 22.04.3 LTS top bar sound icon flickers

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 22.04.3 LTS top bar right corner flicker icons All the icons flicker 
to the right about 2 squares to the right, they keep doing that like something 
is download or something is going on. This is just a new install fresh download 
from Ubuntu website and install on SSD drive from USB iso.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2024-01-21 (2 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  RelatedPackageVersions: mutter-common 42.9-0ubuntu5
  Tags:  jammy
  Uname: Linux 6.5.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2050040/+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 2039235] Re: gnome-online-accounts -> when signing into google account, infinite loading after entering password

[Nathan Reed]

Another confirmation that the infinite load is related to having a
YubiKey as the primary 2FA on the account. Reloading the page as
suggested and then authenticating via mobile device is a successful
workaround.

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

Title:
  gnome-online-accounts -> when signing into google account, infinite
  loading after entering password

Status in gnome-online-accounts package in Ubuntu:
  Confirmed

Bug description:
  1) What you expected to happen
  - sign in is successful, which will allow google services to populate the 
appropriate applications (calendar, mail, google drive)

  2) What actually happened
  - sign in hangs infinitely after entering the password
  - the process is able to detect that the password is correct or incorrect. 
When entering an incorrect password, it will correctly and quickly complain 
that the password is incorrect. When entering the correct password, the bug 
will occur.

  3) Steps to reproduce
    a) start the program
    b) select online accounts
    c) select google
    d) enter email
    e) enter password
    f) loads forever

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: gnome-online-accounts 3.48.0-2
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 12 22:27:59 2023
  InstallationDate: Installed on 2023-10-12 (0 days ago)
  InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-online-accounts
  UpgradeStatus: No upgrade log present (probably fresh install)

  Hardware info (not sure if relevant):
  cpu: intel
  gpu: nvidia (driver version: "Using NVIDIA driver metapackage from 
nvidia-driver-535(proprietary, tested)")

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/2039235/+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 2050040] Re: Ubuntu 22.04.3 LTS top bar sound icon flickers

[kodi]

even when removing sudo apt remove --purge alsa-base pulseaudio and
sudo apt-get --purge remove linux-sound-base alsa-base alsa-utils

and rebooting and not sound settings now in settings sound nothing. The
sound is still beeping off and on no flickering on the dock anymore and
in settings sound, but the sound is still beeping off and on. I hope
that helps with some info on this.

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

Title:
  Ubuntu 22.04.3 LTS top bar sound icon flickers

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 22.04.3 LTS top bar right corner flicker icons All the icons flicker 
to the right about 2 squares to the right, they keep doing that like something 
is download or something is going on. This is just a new install fresh download 
from Ubuntu website and install on SSD drive from USB iso.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2024-01-21 (2 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  RelatedPackageVersions: mutter-common 42.9-0ubuntu5
  Tags:  jammy
  Uname: Linux 6.5.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2050040/+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 2050040] Re: Ubuntu 22.04.3 LTS top bar sound icon flickers

[kodi]

apport-collect 2050040 that command sent me to browser to authorize
application and then open up a windows ubuntu send problem report to the
developers? and it has a list of things but i can't copy and put here.

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

Title:
  Ubuntu 22.04.3 LTS top bar sound icon flickers

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 22.04.3 LTS top bar right corner flicker icons All the icons flicker 
to the right about 2 squares to the right, they keep doing that like something 
is download or something is going on. This is just a new install fresh download 
from Ubuntu website and install on SSD drive from USB iso.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2024-01-21 (2 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  RelatedPackageVersions: mutter-common 42.9-0ubuntu5
  Tags:  jammy
  Uname: Linux 6.5.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2050040/+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 2050040] Re: Ubuntu 22.04.3 LTS top bar sound icon flickers

[kodi]

it got send to the developers

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

Title:
  Ubuntu 22.04.3 LTS top bar sound icon flickers

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 22.04.3 LTS top bar right corner flicker icons All the icons flicker 
to the right about 2 squares to the right, they keep doing that like something 
is download or something is going on. This is just a new install fresh download 
from Ubuntu website and install on SSD drive from USB iso.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2024-01-21 (2 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  RelatedPackageVersions: mutter-common 42.9-0ubuntu5
  Tags:  jammy
  Uname: Linux 6.5.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2050040/+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 2051068] [NEW] GUI crashed after installed proposed package libegl-mesa0

[Lee Sheng Hung]

Public bug reported:

[Summary]
After installed proposed package libegl-mesa0, reboot system.

GUI crashed but still able to access system by ssh.

[Steps to reproduce]
1. Boot into OS
2. sudo apt update
3. sudo apt upgrade
4. After upgrade process finished, reboot system.
5. GUI crashed.

[Expected result]
GUI displayed normally

[Actual result]
GUI crashed

[Failure rate]
100%

Tester comments
---
if we don't upgrade libegl-mesa0, GUI will be fine.

[Additional information]
CID: 202303-31429
SKU: MYBY-DVT2-C5
Image: dell-bto-jammy-jellyfish-muk-X105-20231026-26_A02.iso
system-manufacturer: Dell Inc.
system-product-name: Precision 5680
CPU: Intel(R) Core(TM) i7-13700H
kernel-version: 6.1.0-1028-oem

[Stage]
Issue reported and root cause of crash found.

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


** Tags: 202303-31429 jellyfish-muk

** Description changed:

  [Summary]
  After installed proposed package libegl-mesa0, reboot system.
  
  GUI crashed but still able to access system by ssh.
  
  [Steps to reproduce]
  1. Boot into OS
  2. sudo apt update
  3. sudo apt upgrade
- 4. After upgrad process finished, reboot system.
+ 4. After upgrade process finished, reboot system.
  5. GUI crashed.
  
  [Expected result]
  GUI displayed normally
  
  [Actual result]
  GUI crashed
  
  [Failure rate]
  100%
  
  Tester comments
  ---
  if we don't upgrade libegl-mesa0, GUI will be fine.
  
- 
  [Additional information]
  CID: 202303-31429
  SKU: MYBY-DVT2-C5
  Image: dell-bto-jammy-jellyfish-muk-X105-20231026-26_A02.iso
  system-manufacturer: Dell Inc.
  system-product-name: Precision 5680
  CPU: Intel(R) Core(TM) i7-13700H
  kernel-version: 6.1.0-1028-oem
  
  [Stage]
  Issue reported and root cause of crash found.

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

Title:
  GUI crashed after installed proposed package libegl-mesa0

Status in mesa package in Ubuntu:
  New

Bug description:
  [Summary]
  After installed proposed package libegl-mesa0, reboot system.

  GUI crashed but still able to access system by ssh.

  [Steps to reproduce]
  1. Boot into OS
  2. sudo apt update
  3. sudo apt upgrade
  4. After upgrade process finished, reboot system.
  5. GUI crashed.

  [Expected result]
  GUI displayed normally

  [Actual result]
  GUI crashed

  [Failure rate]
  100%

  Tester comments
  ---
  if we don't upgrade libegl-mesa0, GUI will be fine.

  [Additional information]
  CID: 202303-31429
  SKU: MYBY-DVT2-C5
  Image: dell-bto-jammy-jellyfish-muk-X105-20231026-26_A02.iso
  system-manufacturer: Dell Inc.
  system-product-name: Precision 5680
  CPU: Intel(R) Core(TM) i7-13700H
  kernel-version: 6.1.0-1028-oem

  [Stage]
  Issue reported and root cause of crash found.

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

Re: [Touch-packages] [Bug 2045586] Re: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable

[dann frazier]

On Tue, Jan 23, 2024 at 8:55 PM Michael Hudson-Doyle
<2045...@bugs.launchpad.net> wrote:
>
> Amazing debugging Dann. Until we can get a kernel fix, what's the way
> forward here? Run losetup without -P, run udevadm settle, run partprobe
> on the device (then maybe run udevadm settle again??)

That seems logical. I don't see the need for the 2nd udevadm settle -
but I also don't see the harm.

I've a test fix kernel building in a PPA. I think Łukasz mentioned
that there's a way to have an autopkgtest run on a specific kernel?
Can someone give me those steps?

  -dann

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

Title:
  livecd-rootfs uses losetup -P for theoretically reliable/synchronous
  partition setup but it's not reliable

Status in linux package in Ubuntu:
  New
Status in livecd-rootfs package in Ubuntu:
  New
Status in util-linux package in Ubuntu:
  New

Bug description:
  In mantic, we migrated livecd-rootfs to use losetup -P instead of
  kpartx, with the expectation that this would give us a reliable, race-
  free way of loop-mounting partitions from a disk image during image
  build.

  In noble, we are finding that it is no longer reliable, and in fact
  fails rather often.

  It is most noticeable with riscv64 builds, which is the architecture
  where we most frequently ran into problems before with kpartx.  The
  first riscv64+generic build in noble where the expected loop partition
  device is not available is

https://launchpad.net/~ubuntu-
  cdimage/+livefs/ubuntu/noble/cpc/+build/531790

  The failure is however not unique to riscv64, and the autopkgtest for
  the latest version of livecd-rootfs (24.04.7) - an update that
  specifically tries to add more debugging code for this scenario - has
  also failed on ppc64el.

https://autopkgtest.ubuntu.com/packages/l/livecd-
  rootfs/noble/ppc64el

  The first failure happened on November 16.  While there has been an
  update to the util-linux package in noble, this did not land until
  November 23.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045586/+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 2050040] Re: Ubuntu 22.04.3 LTS top bar sound icon flickers

[Daniel van Vugt]

Thanks. Please try this command to see if it stops the problem:

  gnome-extensions disable mediacontr...@cliffniff.github.com

** Changed in: gnome-shell (Ubuntu)
   Status: New => Incomplete

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

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

Title:
  Ubuntu 22.04.3 LTS top bar sound icon flickers

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 22.04.3 LTS top bar right corner flicker icons All the icons flicker 
to the right about 2 squares to the right, they keep doing that like something 
is download or something is going on. This is just a new install fresh download 
from Ubuntu website and install on SSD drive from USB iso.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2024-01-21 (2 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  RelatedPackageVersions: mutter-common 42.9-0ubuntu5
  Tags:  jammy
  Uname: Linux 6.5.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2050040/+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 2050040] monitors.xml.txt

[kodi]

apport information

** Attachment added: "monitors.xml.txt"
   
https://bugs.launchpad.net/bugs/2050040/+attachment/5741873/+files/monitors.xml.txt

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

Title:
  Ubuntu 22.04.3 LTS top bar sound icon flickers

Status in gnome-shell package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Ubuntu 22.04.3 LTS top bar right corner flicker icons All the icons flicker 
to the right about 2 squares to the right, they keep doing that like something 
is download or something is going on. This is just a new install fresh download 
from Ubuntu website and install on SSD drive from USB iso.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2024-01-21 (2 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  RelatedPackageVersions: mutter-common 42.9-0ubuntu5
  Tags:  jammy
  Uname: Linux 6.5.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2050040/+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 2050040] ShellJournal.txt

[kodi]

apport information

** Attachment added: "ShellJournal.txt"
   
https://bugs.launchpad.net/bugs/2050040/+attachment/5741872/+files/ShellJournal.txt

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

Title:
  Ubuntu 22.04.3 LTS top bar sound icon flickers

Status in gnome-shell package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Ubuntu 22.04.3 LTS top bar right corner flicker icons All the icons flicker 
to the right about 2 squares to the right, they keep doing that like something 
is download or something is going on. This is just a new install fresh download 
from Ubuntu website and install on SSD drive from USB iso.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2024-01-21 (2 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  RelatedPackageVersions: mutter-common 42.9-0ubuntu5
  Tags:  jammy
  Uname: Linux 6.5.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2050040/+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 2050040] ProcCpuinfoMinimal.txt

[kodi]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/2050040/+attachment/5741871/+files/ProcCpuinfoMinimal.txt

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

Title:
  Ubuntu 22.04.3 LTS top bar sound icon flickers

Status in gnome-shell package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Ubuntu 22.04.3 LTS top bar right corner flicker icons All the icons flicker 
to the right about 2 squares to the right, they keep doing that like something 
is download or something is going on. This is just a new install fresh download 
from Ubuntu website and install on SSD drive from USB iso.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2024-01-21 (2 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  RelatedPackageVersions: mutter-common 42.9-0ubuntu5
  Tags:  jammy
  Uname: Linux 6.5.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2050040/+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 2050040] GsettingsChanges.txt

[kodi]

apport information

** Attachment added: "GsettingsChanges.txt"
   
https://bugs.launchpad.net/bugs/2050040/+attachment/5741870/+files/GsettingsChanges.txt

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

Title:
  Ubuntu 22.04.3 LTS top bar sound icon flickers

Status in gnome-shell package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Ubuntu 22.04.3 LTS top bar right corner flicker icons All the icons flicker 
to the right about 2 squares to the right, they keep doing that like something 
is download or something is going on. This is just a new install fresh download 
from Ubuntu website and install on SSD drive from USB iso.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2024-01-21 (2 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  RelatedPackageVersions: mutter-common 42.9-0ubuntu5
  Tags:  jammy
  Uname: Linux 6.5.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2050040/+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 2050040] Dependencies.txt

[kodi]

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/2050040/+attachment/5741869/+files/Dependencies.txt

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

Title:
  Ubuntu 22.04.3 LTS top bar sound icon flickers

Status in gnome-shell package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Ubuntu 22.04.3 LTS top bar right corner flicker icons All the icons flicker 
to the right about 2 squares to the right, they keep doing that like something 
is download or something is going on. This is just a new install fresh download 
from Ubuntu website and install on SSD drive from USB iso.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2024-01-21 (2 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  RelatedPackageVersions: mutter-common 42.9-0ubuntu5
  Tags:  jammy
  Uname: Linux 6.5.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2050040/+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 2050040] Re: Ubuntu 22.04.3 LTS top bar sound icon flickers

[kodi]

apport-collect 2050040 that command sent me to browser to authorize
application and then open up a windows ubuntu send problem report to the
developers? and it has a list of things but i can't copy and put here.

** Tags added: apport-collected

** Description changed:

- Ubuntu 22.04.3 LTS top bar right corner flicker icons All the icons
- flicker to the right about 2 squares to the right, they keep doing that
- like something is download or something is going on. This is just a new
- install fresh download from Ubuntu website and install on SSD drive from
- USB iso.
+ Ubuntu 22.04.3 LTS top bar right corner flicker icons All the icons flicker 
to the right about 2 squares to the right, they keep doing that like something 
is download or something is going on. This is just a new install fresh download 
from Ubuntu website and install on SSD drive from USB iso.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu82.5
+ Architecture: amd64
+ CasperMD5CheckResult: pass
+ CurrentDesktop: ubuntu:GNOME
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 22.04
+ InstallationDate: Installed on 2024-01-21 (2 days ago)
+ InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
+ NonfreeKernelModules: nvidia_modeset nvidia
+ Package: pulseaudio
+ PackageArchitecture: amd64
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
+ ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
+ RelatedPackageVersions: mutter-common 42.9-0ubuntu5
+ Tags:  jammy
+ Uname: Linux 6.5.0-14-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
+ _MarkForUpload: True

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

Title:
  Ubuntu 22.04.3 LTS top bar sound icon flickers

Status in gnome-shell package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Ubuntu 22.04.3 LTS top bar right corner flicker icons All the icons flicker 
to the right about 2 squares to the right, they keep doing that like something 
is download or something is going on. This is just a new install fresh download 
from Ubuntu website and install on SSD drive from USB iso.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2024-01-21 (2 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  RelatedPackageVersions: mutter-common 42.9-0ubuntu5
  Tags:  jammy
  Uname: Linux 6.5.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2050040/+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 2050040] Re: Ubuntu 22.04.3 LTS top bar sound icon flickers

[kodi]

* index: 1017
name: 
driver: 
flags: HARDWARE HW_MUTE_CTRL DECIBEL_VOLUME LATENCY DYNAMIC_LATENCY
state: RUNNING
suspend cause: (none)
priority: 9037
volume: front-left: 65536 / 100% / 0.00 dB,   front-right: 65536 / 100% 
/ 0.00 dB
balance 0.00
base volume: 65536 / 100% / 0.00 dB
volume steps: 65537
muted: no
current latency: 2.86 ms
max request: 0 KiB
max rewind: 0 KiB
monitor source: 1017
sample spec: s16le 2ch 44100Hz
channel map: front-left,front-right
 Stereo
used by: 1
linked by: 1
configured latency: 2.51 ms; range is 0.50 .. 2000.00 ms
card: 2 
module: 24
properties:
alsa.resolution_bits = "16"
device.api = "alsa"
device.class = "sound"
alsa.class = "generic"
alsa.subclass = "generic-mix"
alsa.name = "ALC892 Digital"
alsa.id = "ALC892 Digital"
alsa.subdevice = "0"
alsa.subdevice_name = "subdevice #0"
alsa.device = "1"
alsa.card = "1"
alsa.card_name = "HDA Intel PCH"
alsa.long_card_name = "HDA Intel PCH at 0xf7a3 irq 34"
alsa.driver_name = "snd_hda_intel"
device.bus_path = "pci-:00:1b.0"
sysfs.path = "/devices/pci:00/:00:1b.0/sound/card1"
device.bus = "pci"
device.vendor.id = "8086"
device.vendor.name = "Intel Corporation"
device.product.id = "8c20"
device.product.name = "8 Series/C220 Series Chipset High 
Definition Audio Controller"
device.form_factor = "internal"
device.string = "iec958:1"
device.buffering.buffer_size = "352800"
device.buffering.fragment_size = "176400"
device.access_mode = "mmap+timer"
device.profile.name = "iec958-stereo"
device.profile.description = "Digital Stereo (IEC958)"
device.description = "Built-in Audio Digital Stereo (IEC958)"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-pci"
ports:
iec958-stereo-output: Digital Output (S/PDIF) (priority 0, 
latency offset 0 usec, available: unknown)
properties:

active port: 

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

Title:
  Ubuntu 22.04.3 LTS top bar sound icon flickers

Status in gnome-shell package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Ubuntu 22.04.3 LTS top bar right corner flicker icons All the icons flicker 
to the right about 2 squares to the right, they keep doing that like something 
is download or something is going on. This is just a new install fresh download 
from Ubuntu website and install on SSD drive from USB iso.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2024-01-21 (2 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: pulseaudio
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  RelatedPackageVersions: mutter-common 42.9-0ubuntu5
  Tags:  jammy
  Uname: Linux 6.5.0-14-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2050040/+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 2040011] Re: [SRU] Ensure supported codenames are accurate

[Chris Halse Rogers]

It's a little weird that you're folding two patches into a single patch,
but looks ok. Please do update the bug description!

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

Title:
  [SRU] Ensure supported codenames are accurate

Status in vim package in Ubuntu:
  Fix Released
Status in vim source package in Focal:
  Incomplete
Status in vim source package in Jammy:
  Incomplete
Status in vim source package in Lunar:
  Won't Fix
Status in vim source package in Mantic:
  Incomplete

Bug description:
  In several stable releases of Ubuntu, Vim has information regarding
  releases that are outdated. It would be optimal for Vim to grab this
  data from distro-info-data (or similar), but unfortunately that is not
  the case. Therefore, the list needs to be updated.

  There is a minimal regression potential here; Vim simply reads a
  statically-set Perl array to determine if the release in the changelog
  and sources.list is supported or not. Any regression would present
  itself in external tooling that detects text highlighting, which is
  not a case I think we support in Ubuntu.

  A simple way to test this update is to download a package from the
  Lunar archive, and open the changelog with Vim. Instead of the
  changelog release (e.g. "noble") showing as red, it should show as
  blue. I would also suggest editing sources.list, to ensure e.g. Eoan
  shows as EOL.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/2040011/+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 2050040] Re: Ubuntu 22.04.3 LTS top bar sound icon flickers

[kodi]

about page

** Attachment added: "Screenshot from 2024-01-23 20-05-19.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2050040/+attachment/5741861/+files/Screenshot%20from%202024-01-23%2020-05-19.png

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

Title:
  Ubuntu 22.04.3 LTS top bar sound icon flickers

Status in gnome-shell package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Ubuntu 22.04.3 LTS top bar right corner flicker icons All the icons
  flicker to the right about 2 squares to the right, they keep doing
  that like something is download or something is going on. This is just
  a new install fresh download from Ubuntu website and install on SSD
  drive from USB iso.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2050040/+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 2050040] Re: Ubuntu 22.04.3 LTS top bar sound icon flickers

[Daniel van Vugt]

Please run:

  apport-collect 2050040

so we can see more details about the software versions in use.

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

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

Title:
  Ubuntu 22.04.3 LTS top bar sound icon flickers

Status in gnome-shell package in Ubuntu:
  New
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Ubuntu 22.04.3 LTS top bar right corner flicker icons All the icons
  flicker to the right about 2 squares to the right, they keep doing
  that like something is download or something is going on. This is just
  a new install fresh download from Ubuntu website and install on SSD
  drive from USB iso.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2050040/+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 2045586] Re: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable

[Michael Hudson-Doyle]

Amazing debugging Dann. Until we can get a kernel fix, what's the way
forward here? Run losetup without -P, run udevadm settle, run partprobe
on the device (then maybe run udevadm settle again??)

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

Title:
  livecd-rootfs uses losetup -P for theoretically reliable/synchronous
  partition setup but it's not reliable

Status in linux package in Ubuntu:
  New
Status in livecd-rootfs package in Ubuntu:
  New
Status in util-linux package in Ubuntu:
  New

Bug description:
  In mantic, we migrated livecd-rootfs to use losetup -P instead of
  kpartx, with the expectation that this would give us a reliable, race-
  free way of loop-mounting partitions from a disk image during image
  build.

  In noble, we are finding that it is no longer reliable, and in fact
  fails rather often.

  It is most noticeable with riscv64 builds, which is the architecture
  where we most frequently ran into problems before with kpartx.  The
  first riscv64+generic build in noble where the expected loop partition
  device is not available is

https://launchpad.net/~ubuntu-
  cdimage/+livefs/ubuntu/noble/cpc/+build/531790

  The failure is however not unique to riscv64, and the autopkgtest for
  the latest version of livecd-rootfs (24.04.7) - an update that
  specifically tries to add more debugging code for this scenario - has
  also failed on ppc64el.

https://autopkgtest.ubuntu.com/packages/l/livecd-
  rootfs/noble/ppc64el

  The first failure happened on November 16.  While there has been an
  update to the util-linux package in noble, this did not land until
  November 23.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045586/+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 2051045] Re: Xorg freeze

[Daniel van Vugt]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Run these commands:
journalctl -b0 > journal.txt
journalctl -b-1 > prevjournal.txt
and attach the resulting text files here.

2. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

3. If step 2 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.


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

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

** Summary changed:

- Xorg freeze
+ Freeze

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

Title:
  Freeze

Status in Ubuntu:
  Incomplete

Bug description:
  Freeze began after a system update

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-39-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.157  Wed Oct 12 09:19:07 
UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 21:45:39 2024
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 730] [10de:0f02] (rev a1) 
(prog-if 00 [VGA controller])
  InstallationDate: Installed on 2022-02-09 (713 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic 
root=UUID=299c5e76-ba77-4da8-8008-91c34568104b ro recovery nomodeset 
dis_ucode_ldr
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/30/2018
  dmi.bios.release: 8.15
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080015
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: INTEL H55
  dmi.board.vendor: INTEL
  dmi.board.version: INTEL
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd09/30/2018:br8.15:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnINTEL:rnINTELH55:rvrINTEL:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  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/2051045/+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 2050955] Re: consistently fails to resume from suspend

[Daniel van Vugt]

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

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 2050954, 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) => linux-hwe-6.5 (Ubuntu)

** This bug has been marked a duplicate of bug 2050954
   consistently fails to resume 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/2050955

Title:
  consistently fails to resume from suspend

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

Bug description:
  using integrated intel gpu no nvidia

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-17.17~22.04.1-generic 6.5.8
  Uname: Linux 6.5.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  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: ubuntu:GNOME
  Date: Tue Jan 23 08:39:14 2024
  DistUpgraded: 2022-08-02 07:50:46,100 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 RocketLake-S GT1 [UHD Graphics 750] [8086:4c8a] (rev 04) 
(prog-if 00 [VGA controller])
 Subsystem: Dell RocketLake-S GT1 [UHD Graphics 750] [1028:09c5]
  InstallationDate: Installed on 2022-04-28 (634 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  MachineType: Dell Inc. XPS 8940
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-17-generic 
root=UUID=cce872cb-0478-4e9a-b49b-c63cabcbe4f6 ro
  SourcePackage: xorg
  UpgradeStatus: Upgraded to jammy on 2022-08-02 (539 days ago)
  dmi.bios.date: 09/14/2022
  dmi.bios.release: 2.10
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.10.0
  dmi.board.name: 0427JK
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.10.0:bd09/14/2022:br2.10:svnDellInc.:pnXPS8940:pvr:rvnDellInc.:rn0427JK:rvrA00:cvnDellInc.:ct3:cvr:sku09C5:
  dmi.product.family: XPS
  dmi.product.name: XPS 8940
  dmi.product.sku: 09C5
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.14.1+22.04.20220820-0ubuntu1
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  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/linux-hwe-6.5/+bug/2050955/+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 2050954] Re: Xorg freeze

[Daniel van Vugt]

Thanks for the bug report. Next time the problem happens please:

1. Reboot.

2. Run:

   journalctl -b-1 > prevboot.txt

3. Attach the resulting text file here.


** Summary changed:

- Xorg freeze
+ consistently fails to resume from suspend

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

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

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

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

Title:
  consistently fails to resume from suspend

Status in linux-hwe-6.5 package in Ubuntu:
  Incomplete

Bug description:
  consistently fails to resume from suspend

  using integrated intel gpu no nvidia

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-17.17~22.04.1-generic 6.5.8
  Uname: Linux 6.5.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  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: ubuntu:GNOME
  Date: Tue Jan 23 08:34:38 2024
  DistUpgraded: 2022-08-02 07:50:46,100 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Since before I upgraded
  GraphicsCard:
   Intel Corporation RocketLake-S GT1 [UHD Graphics 750] [8086:4c8a] (rev 04) 
(prog-if 00 [VGA controller])
 Subsystem: Dell RocketLake-S GT1 [UHD Graphics 750] [1028:09c5]
  InstallationDate: Installed on 2022-04-28 (634 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  MachineType: Dell Inc. XPS 8940
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-17-generic 
root=UUID=cce872cb-0478-4e9a-b49b-c63cabcbe4f6 ro
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to jammy on 2022-08-02 (539 days ago)
  dmi.bios.date: 09/14/2022
  dmi.bios.release: 2.10
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.10.0
  dmi.board.name: 0427JK
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.10.0:bd09/14/2022:br2.10:svnDellInc.:pnXPS8940:pvr:rvnDellInc.:rn0427JK:rvrA00:cvnDellInc.:ct3:cvr:sku09C5:
  dmi.product.family: XPS
  dmi.product.name: XPS 8940
  dmi.product.sku: 09C5
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.14.1+22.04.20220820-0ubuntu1
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  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/linux-hwe-6.5/+bug/2050954/+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 2009145] Re: Xubuntu defaults in /etc/xdg/xdg-xubuntu are ignored

[Sean Davis]

There's this linked bug in Debian:
https://salsa.debian.org/xorg-team/xorg/-/merge_requests/17

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

Title:
  Xubuntu defaults in /etc/xdg/xdg-xubuntu are ignored

Status in xorg package in Ubuntu:
  New
Status in xubuntu-meta package in Ubuntu:
  Fix Released

Bug description:
  Related to https://salsa.debian.org/xorg-team/xorg/-/merge_requests/17

  The dbus-x11 package is being deprecated. As a result, the Xfce
  packages from upstream Debian no longer pull it in. Until the xorg
  packages have been updated accordingly in Ubuntu, the Xubuntu settings
  found in /etc/xdg/xdg-xubuntu are ignored.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2009145/+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 2015129] Re: gstreamer 1.22.1 bugfix release

[Launchpad Bug Tracker]

This bug was fixed in the package gstreamer-editing-services1.0 -
1.22.8-1

---
gstreamer-editing-services1.0 (1.22.8-1) unstable; urgency=medium

  [ Jeremy Bícha ]
  * Team upload
  * New upstream release
  * Revert pygi-overrides-dir workaround: no longer needed

  [ Graham Inggs ]
  * Add patch to ignore tests that have failed since glib 2.76
and are blocking the ongoing Python 3.12 transition
Mitigates: #1042341

 -- Jeremy Bícha   Tue, 23 Jan 2024 14:03:16 -0500

** Changed in: gstreamer-editing-services1.0 (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  gstreamer 1.22.1 bugfix release

Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-base1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-editing-services1.0 package in Ubuntu:
  Fix Released
Status in gstreamer1.0 package in Ubuntu:
  Fix Released

Bug description:
  Impact
  --
  This is a stable bugfix release

  See https://gstreamer.freedesktop.org/releases/1.22/#1.22.1 for more
  details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/2015129/+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 2051045] [NEW] Xorg freeze

[Jonathan Higdon]

Public bug reported:

Freeze began after a system update

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-39-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.157  Wed Oct 12 09:19:07 
UTC 2022
 GCC version:
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Jan 23 21:45:39 2024
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 730] [10de:0f02] (rev a1) 
(prog-if 00 [VGA controller])
InstallationDate: Installed on 2022-02-09 (713 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic 
root=UUID=299c5e76-ba77-4da8-8008-91c34568104b ro recovery nomodeset 
dis_ucode_ldr
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/30/2018
dmi.bios.release: 8.15
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080015
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: INTEL H55
dmi.board.vendor: INTEL
dmi.board.version: INTEL
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd09/30/2018:br8.15:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnINTEL:rnINTELH55:rvrINTEL:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug false-gpu-hang freeze jammy ubuntu

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Freeze began after a system update

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-39-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.157  Wed Oct 12 09:19:07 
UTC 2022
   GCC version:
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permissão negada: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 21:45:39 2024
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard: NVIDIA Corporation GF108 [GeForce GT 730] [10de:0f02] (rev a1) 
(prog-if 00 [VGA controller])
  InstallationDate: Installed on 2022-02-09 (713 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic 
root=UUID=299c5e76-ba77-4da8-8008-91c34568104b ro recovery nomodeset 
dis_ucode_ldr
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 

[Touch-packages] [Bug 2050033] Re: gettext: msgfmt --java2 does not support Java 21

[Vladimir Petko]

** Description changed:

  When building 'ssl-utils-clojure' package with Java 21 as default, the build
  fails with the following trace:
  --
  Applying task i18n to [make]
  Running 'make i18n'
  make[1]: *** [debian/rules:19: override_dh_auto_build] Error 1
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:12: binary] Error 2
  dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
2
  --
  
  Running make in the build chroot produces the following error:
  ---
  msgfmt --java2 -d resources -r puppetlabs.ssl_utils.Messages -l eo
  locales/eo.po
  msgfmt: Java compiler not found, try installing gcj or set $JAVAC
  msgfmt: compilation of Java class failed, please try --verbose or set $JAVAC
  make: *** [dev-resources/Makefile.i18n:94:
  resources/puppetlabs/ssl_utils/Messages_eo.class] Error 1
  ---
  
  It appears that gettext package does not support Java 21.
+ 
+ Note: gettext 0.22.4 refactors Java support. This delta can be safely
+ dropped after a new upstream release.

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

Title:
  gettext: msgfmt --java2 does not support Java 21

Status in gettext package in Ubuntu:
  New
Status in gettext package in Debian:
  New

Bug description:
  When building 'ssl-utils-clojure' package with Java 21 as default, the build
  fails with the following trace:
  --
  Applying task i18n to [make]
  Running 'make i18n'
  make[1]: *** [debian/rules:19: override_dh_auto_build] Error 1
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:12: binary] Error 2
  dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
2
  --

  Running make in the build chroot produces the following error:
  ---
  msgfmt --java2 -d resources -r puppetlabs.ssl_utils.Messages -l eo
  locales/eo.po
  msgfmt: Java compiler not found, try installing gcj or set $JAVAC
  msgfmt: compilation of Java class failed, please try --verbose or set $JAVAC
  make: *** [dev-resources/Makefile.i18n:94:
  resources/puppetlabs/ssl_utils/Messages_eo.class] Error 1
  ---

  It appears that gettext package does not support Java 21.

  Note: gettext 0.22.4 refactors Java support. This delta can be safely
  dropped after a new upstream release.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gettext/+bug/2050033/+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 2051031] [NEW] Occasionally system alert will play as loud scary static noise.

[Nicholas Romero]

Public bug reported:

EG when I made this issue I was trying to autocomplete a scp command in
my terminal. The autocomplete noise was a scary static noise.. litterlly
like something out of a horror movie and it's very jarring.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 6.1.0-1027.27-oem 6.1.61
Uname: Linux 6.1.0-1027-oem x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Jan 23 14:37:35 2024
InstallationDate: Installed on 2023-12-05 (49 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Blackjack successful
Symptom_Card: BRIO Ultra HD Webcam - Logitech BRIO
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: None of the above
Title: [USB-Audio - Onyx Blackjack, playback] Playback problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/17/2023
dmi.bios.release: 3.3
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 03.03
dmi.board.asset.tag: *
dmi.board.name: FRANMDCP07
dmi.board.vendor: Framework
dmi.board.version: A7
dmi.chassis.asset.tag: FRANDGCPA73433005D
dmi.chassis.type: 10
dmi.chassis.vendor: Framework
dmi.chassis.version: A7
dmi.modalias: 
dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA7:rvnFramework:rnFRANMDCP07:rvrA7:cvnFramework:ct10:cvrA7:skuFRANDGCP07:
dmi.product.family: Laptop
dmi.product.name: Laptop 13 (AMD Ryzen 7040Series)
dmi.product.sku: FRANDGCP07
dmi.product.version: A7
dmi.sys.vendor: Framework

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

Title:
  Occasionally system alert will play as loud scary static noise.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  EG when I made this issue I was trying to autocomplete a scp command
  in my terminal. The autocomplete noise was a scary static noise..
  litterlly like something out of a horror movie and it's very jarring.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.1.0-1027.27-oem 6.1.61
  Uname: Linux 6.1.0-1027-oem x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 14:37:35 2024
  InstallationDate: Installed on 2023-12-05 (49 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Blackjack 
successful
  Symptom_Card: BRIO Ultra HD Webcam - Logitech BRIO
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [USB-Audio - Onyx Blackjack, playback] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/17/2023
  dmi.bios.release: 3.3
  dmi.bios.vendor: INSYDE Corp.
  dmi.bios.version: 03.03
  dmi.board.asset.tag: *
  dmi.board.name: FRANMDCP07
  dmi.board.vendor: Framework
  dmi.board.version: A7
  dmi.chassis.asset.tag: FRANDGCPA73433005D
  dmi.chassis.type: 10
  dmi.chassis.vendor: Framework
  dmi.chassis.version: A7
  dmi.modalias: 
dmi:bvnINSYDECorp.:bvr03.03:bd10/17/2023:br3.3:svnFramework:pnLaptop13(AMDRyzen7040Series):pvrA7:rvnFramework:rnFRANMDCP07:rvrA7:cvnFramework:ct10:cvrA7:skuFRANDGCP07:
  dmi.product.family: Laptop
  dmi.product.name: Laptop 13 (AMD Ryzen 7040Series)
  dmi.product.sku: FRANDGCP07
  dmi.product.version: A7
  dmi.sys.vendor: Framework

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2051031/+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 2050033] Re: gettext: msgfmt --java2 does not support Java 21

[Vladimir Petko]

Piuparts gettext install/purge tests

** Attachment added: "noble-gettext.tar.gz"
   
https://bugs.launchpad.net/ubuntu/+source/gettext/+bug/2050033/+attachment/5741749/+files/noble-gettext.tar.gz

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

Title:
  gettext: msgfmt --java2 does not support Java 21

Status in gettext package in Ubuntu:
  New
Status in gettext package in Debian:
  New

Bug description:
  When building 'ssl-utils-clojure' package with Java 21 as default, the build
  fails with the following trace:
  --
  Applying task i18n to [make]
  Running 'make i18n'
  make[1]: *** [debian/rules:19: override_dh_auto_build] Error 1
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:12: binary] Error 2
  dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
2
  --

  Running make in the build chroot produces the following error:
  ---
  msgfmt --java2 -d resources -r puppetlabs.ssl_utils.Messages -l eo
  locales/eo.po
  msgfmt: Java compiler not found, try installing gcj or set $JAVAC
  msgfmt: compilation of Java class failed, please try --verbose or set $JAVAC
  make: *** [dev-resources/Makefile.i18n:94:
  resources/puppetlabs/ssl_utils/Messages_eo.class] Error 1
  ---

  It appears that gettext package does not support Java 21.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gettext/+bug/2050033/+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 2042587] Re: jammy's version breaks existing dhcp scripts with relay

[Andreas Hasenack]

Reproducing the bug

root@j-dnsmasq-2042587:~# apt-cache policy dnsmasq
dnsmasq:
  Installed: 2.86-1.1ubuntu0.4
  Candidate: 2.86-1.1ubuntu0.4
  Version table:
 *** 2.86-1.1ubuntu0.4 500
500 http://br.archive.ubuntu.com/ubuntu jammy-updates/universe amd64 
Packages
100 /var/lib/dpkg/status
 2.86-1.1ubuntu0.3 500
500 http://br.archive.ubuntu.com/ubuntu jammy-security/universe amd64 
Packages
 2.86-1.1 500
500 http://br.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages


Running the setup script:
# ./setup-and-server.sh

Cleaning up
Setting things up...

Commands to run in another terminal:

No DHCP relay:

  ip netns exec client dhclient -d -v p2

With DHCP relay set to 192.168.47.9, IP should NOT be that address:

  ip netns exec client dhclient -d -v p2 -g 192.168.47.9


Starting server, observe output and run the test commands above.
Press ctrl-c when done.

dnsmasq: started, version 2.86 cachesize 150
dnsmasq: compile time options: IPv6 GNU-getopt DBus no-UBus i18n IDN2 DHCP 
DHCPv6 no-Lua TFTP conntrack ipset auth cryptohash DNSSEC loop-detect inotify 
dumpfile
dnsmasq-dhcp: DHCP, IP range 192.168.47.10 -- 192.168.47.250, lease time 12h
dnsmasq-dhcp: DHCP, sockets bound exclusively to interface p1
dnsmasq: reading /etc/resolv.conf
dnsmasq: using nameserver 127.0.0.53#53
dnsmasq: read /etc/hosts - 7 addresses


For the "no DHCP relay" case:
# ip netns exec client dhclient -d -v p2
(...)
bound to 192.168.47.209 -- renewal in 21350 seconds.


And the server logs:
dnsmasq-dhcp: DHCPDISCOVER(p1) ee:a3:dd:58:d8:35 
dnsmasq-dhcp: DHCPOFFER(p1) 192.168.47.209 ee:a3:dd:58:d8:35
dnsmasq-dhcp: DHCPREQUEST(p1) 192.168.47.209 ee:a3:dd:58:d8:35
dnsmasq-dhcp: DHCPACK(p1) 192.168.47.209 ee:a3:dd:58:d8:35 j-dnsmasq-2042587
###
IP = 192.168.47.209
###


That's the correct IP we want to see. Now, on to the bug, which is WITH a DHCP 
relay.

We run this on the client:
# ip netns exec client dhclient -d -v p2 -g 192.168.47.9
(...)
DHCPREQUEST for 192.168.47.209 on p2 to 255.255.255.255 port 67 (xid=0x7f70085a)


And the server logs the incorrect iP:
dnsmasq-dhcp: DHCPREQUEST(p1) 192.168.47.209 ee:a3:dd:58:d8:35
dnsmasq-dhcp: DHCPACK(p1) 192.168.47.209 ee:a3:dd:58:d8:35 j-dnsmasq-2042587
###
IP = 192.168.47.9
TEST FAILED
###


Now let's use the package from proposed:

root@j-dnsmasq-2042587:~# apt-cache policy dnsmasq
dnsmasq:
  Installed: 2.86-1.1ubuntu0.5
  Candidate: 2.86-1.1ubuntu0.5
  Version table:
 *** 2.86-1.1ubuntu0.5 500
500 http://br.archive.ubuntu.com/ubuntu jammy-proposed/universe amd64 
Packages
100 /var/lib/dpkg/status
 2.86-1.1ubuntu0.4 500
500 http://br.archive.ubuntu.com/ubuntu jammy-updates/universe amd64 
Packages
 2.86-1.1ubuntu0.3 500
500 http://br.archive.ubuntu.com/ubuntu jammy-security/universe amd64 
Packages
 2.86-1.1 500
500 http://br.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages


We run the server script again:

The no-relay case:
# ip netns exec client dhclient -d -v p2
(...)
bound to 192.168.47.155 -- renewal in 19424 seconds.

Where the server logs:
(...)
dnsmasq-dhcp: DHCPACK(p1) 192.168.47.155 e2:c1:8c:88:0d:94 j-dnsmasq-2042587
###
IP = 192.168.47.155
###

Which was already working before, but now let's try the relay case, which was 
broken before:
# ip netns exec client dhclient -d -v p2 -g 192.168.47.9
(...)
DHCPREQUEST for 192.168.47.155 on p2 to 255.255.255.255 port 67 (xid=0x292ace5c)

Now the server logs the correct IP:
dnsmasq-dhcp: DHCPREQUEST(p1) 192.168.47.155 e2:c1:8c:88:0d:94
dnsmasq-dhcp: DHCPACK(p1) 192.168.47.155 e2:c1:8c:88:0d:94 j-dnsmasq-2042587
###
IP = 192.168.47.155
###


Jammy verification succeeded.

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

Title:
  jammy's version breaks existing dhcp scripts with relay

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in dnsmasq source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

  When upgrading from focal to jammy, existing dnsmasq dhcp-scripts
  stopped working in an environment where a DHCP relay is in use.
  Instead of the expected client IP address, the script gets the _relay_
  IP address as an argument.

  This was fixed in 2.87, therefore making only jammy carry an affected
  package.

  [ Test Plan ]

  To easily test this on a single machine, a test script is being
  provided to setup networking and dnsmasq configuration.

  # Launch a jammy VM

  lxc launch ubuntu-daily:jammy j-dnsmasq-2042587 --vm

  # open a root shell in that VM. All subsequent commands must be
  executed as root in that VM

  lxc shell j-dnsmasq-2042587

  # download test script

  wget

[Touch-packages] [Bug 1958019]

[lukas]

Hey, I have a Lenovo Yoga 7 16IAP7 with Fedora Workstation 39 installed.

Kernel Verion: Linux 6.6.11-200.fc39.x86_64
alsa-lib version: alsa-lib-1.2.10-3.fc39.x86_64

I installed alsa-tools and went into hdajackretask to see what is going
on. Then I noticed that my System is telling me that I have an ALC287
installed but actually it is a ALC3306. Sound is horrible and several
fixes with ALC 287 for Legion Models did nit work. In the Settings I can
see as well, that only 2 of the 4 integrated speakers are getting
noticed.

I have had this Problem for a while now.

Comment #806 said that this should have worked till 6.6 and then it
broke again. I had a fresh install of Fedora 38 back then with the
Kernel 6.4.6-200.fc38.x86_64. It did not work form me with this Kernel
either.

Are there any news or is there hope of fixes?

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

Title:
  [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No
  sound at all

Status in sound-2.6 (alsa-kernel):
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by
  internal speakers, but it work by headphones connected to standard
  jack aux.

  uname -r
  5.11.0-44-generic

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22
  Uname: Linux 5.11.0-44-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 15 15:10:53 2022
  InstallationDate: Installed on 2021-10-11 (96 days ago)
  InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  i3draven   1266 F pulseaudio
   /dev/snd/controlC0:  i3draven   1266 F pulseaudio
   /dev/snd/controlC1:  i3draven   1266 F pulseaudio
   /dev/snd/pcmC1D0p:   i3draven   1266 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/08/2021
  dmi.bios.release: 1.49
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GKCN49WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0R32862 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Legion 7 16ACHg6
  dmi.ec.firmware.release: 1.49
  dmi.modalias: 
dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6:
  dmi.product.family: Legion 7 16ACHg6
  dmi.product.name: 82N6
  dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6
  dmi.product.version: Legion 7 16ACHg6
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 2045570] Re: dnsmasq crash when no servers in resolv.conf

[Andreas Hasenack]

Reproducing the bug


root@j-dnsmasq-2045570:~# apt-cache policy dnsmasq
dnsmasq:
  Installed: 2.86-1.1ubuntu0.4
  Candidate: 2.86-1.1ubuntu0.4
  Version table:
 *** 2.86-1.1ubuntu0.4 500
500 http://br.archive.ubuntu.com/ubuntu jammy-updates/universe amd64 
Packages
100 /var/lib/dpkg/status
 2.86-1.1ubuntu0.3 500
500 http://br.archive.ubuntu.com/ubuntu jammy-security/universe amd64 
Packages
 2.86-1.1 500
500 http://br.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages


# dig @127.0.0.1 +short linux.com
23.185.0.3

# echo "#nameserver 1.1.1.1" > /etc/resolv.conf
#

Log:
Jan 23 16:57:40 j-dnsmasq-2045570 dnsmasq[]: no servers found in 
/etc/resolv.conf, will retry


root@j-dnsmasq-2045570:~# dig @127.0.0.1 +short ubuntu.com
;; communications error to 127.0.0.1#53: timed out
;; communications error to 127.0.0.1#53: connection refused
;; communications error to 127.0.0.1#53: connection refused
;; no servers could be reached

And the log show a crash:
Jan 23 17:03:12 j-dnsmasq-2045570 dnsmasq[253]: no servers found in 
/etc/resolv.conf, will retry
Jan 23 17:03:16 j-dnsmasq-2045570 systemd[1]: dnsmasq.service: Main process 
exited, code=dumped, status=11/SEGV
Jan 23 17:03:16 j-dnsmasq-2045570 systemd[1]: dnsmasq.service: Failed with 
result 'core-dump'.

(it took about 3 attempts, but it crashed)


With the new package from jammy-proposed:
root@j-dnsmasq-2045570:~# apt-cache policy dnsmasq
dnsmasq:
  Installed: 2.86-1.1ubuntu0.5
  Candidate: 2.86-1.1ubuntu0.5
  Version table:
 *** 2.86-1.1ubuntu0.5 500
500 http://br.archive.ubuntu.com/ubuntu jammy-proposed/universe amd64 
Packages
100 /var/lib/dpkg/status
 2.86-1.1ubuntu0.4 500
500 http://br.archive.ubuntu.com/ubuntu jammy-updates/universe amd64 
Packages
 2.86-1.1ubuntu0.3 500
500 http://br.archive.ubuntu.com/ubuntu jammy-security/universe amd64 
Packages
 2.86-1.1 500
500 http://br.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages

When I perform the same test as before, I get an immediate empty result, and no 
crash, when resolv.conf contains no server:
root@j-dnsmasq-2045570:~# dig @127.0.0.1 +short ubuntu.com
root@j-dnsmasq-2045570:~#

And the previous result, which was cached, is still there:
root@j-dnsmasq-2045570:~# dig @127.0.0.1 +short linux.com
23.185.0.3

Logs remain silent:
Jan 23 17:08:14 j-dnsmasq-2045570 dnsmasq[1350]: no servers found in 
/etc/resolv.conf, will retry

If I revert resolv.conf to a working content:
root@j-dnsmasq-2045570:~# echo "nameserver 1.1.1.1" > /etc/resolv.conf

The log notices that:
Jan 23 17:57:47 j-dnsmasq-2045570 dnsmasq[7370]: reading /etc/resolv.conf
Jan 23 17:57:47 j-dnsmasq-2045570 dnsmasq[7370]: using nameserver 1.1.1.1#53

And the server resumes working:
root@j-dnsmasq-2045570:~# dig @127.0.0.1 +short ubuntu.com
185.125.190.21
185.125.190.29
185.125.190.20
root@j-dnsmasq-2045570:~# dig @127.0.0.1 +short linux.com
23.185.0.3
root@j-dnsmasq-2045570:~#


Jammy verification succeeded.


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

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

Title:
  dnsmasq crash when no servers in resolv.conf

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in dnsmasq source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

  dnsmasq "keeps an eye" on /etc/resolv.conf, and reloads it whenever
  the file is updated. When that happens and for some reason there were
  no "nameserver" declarations in the updated file, dnsmasq can crash.

  Here is a log of a reproducer:
  $ dig +short @127.0.0.1 ubuntu.com
  ;; communications error to 127.0.0.1#53: timed out
  ;; communications error to 127.0.0.1#53: connection refused
  ;; communications error to 127.0.0.1#53: connection refused
  ;; no servers could be reached

  We can see the startup, then when resolv.conf is read again and no 
nameservers were found, and the crash:
  Jan 03 13:57:13 j-dnsmasq-2045570 dnsmasq[1507]: started, version 2.86 
cachesize 150
  Jan 03 13:57:13 j-dnsmasq-2045570 dnsmasq[1507]: DNS service limited to local 
subnets
  Jan 03 13:57:13 j-dnsmasq-2045570 dnsmasq[1507]: compile time options: IPv6 
GNU-getopt DBus no-UBus i18n IDN2 DHCP DHCPv6 no-Lua TFTP conntrack ipset auth 
cryptohash DNSSEC loop-detect inotify dumpfile
  Jan 03 13:57:13 j-dnsmasq-2045570 dnsmasq[1507]: reading /etc/resolv.conf
  Jan 03 13:57:13 j-dnsmasq-2045570 dnsmasq[1507]: using nameserver 
10.0.100.1#53
  Jan 03 13:57:13 j-dnsmasq-2045570 dnsmasq[1507]: read /etc/hosts - 7 addresses
  Jan 03 13:57:13 j-dnsmasq-2045570 systemd[1]: Started dnsmasq - A lightweight 
DHCP and caching DNS server.
  Jan 03 13:58:01 j-dnsmasq-2045570 dnsmasq[1507]: no servers found in 
/etc/resolv.conf, will retry
  Jan 03 13:58:22 j-dnsmasq-2045570 systemd[1]: 

[Touch-packages] [Bug 2045570] Re: dnsmasq crash when no servers in resolv.conf

[Andreas Hasenack]

Ah, I now understand what happened in the comment above. I only upgraded
the bin:dnsmasq package, and not bin:dnsmasq-base. Both need to be
upgraded, i.e., like a normal "apt ugprade" or "apt dist-upgrade" would
do.

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

Title:
  dnsmasq crash when no servers in resolv.conf

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in dnsmasq source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

  dnsmasq "keeps an eye" on /etc/resolv.conf, and reloads it whenever
  the file is updated. When that happens and for some reason there were
  no "nameserver" declarations in the updated file, dnsmasq can crash.

  Here is a log of a reproducer:
  $ dig +short @127.0.0.1 ubuntu.com
  ;; communications error to 127.0.0.1#53: timed out
  ;; communications error to 127.0.0.1#53: connection refused
  ;; communications error to 127.0.0.1#53: connection refused
  ;; no servers could be reached

  We can see the startup, then when resolv.conf is read again and no 
nameservers were found, and the crash:
  Jan 03 13:57:13 j-dnsmasq-2045570 dnsmasq[1507]: started, version 2.86 
cachesize 150
  Jan 03 13:57:13 j-dnsmasq-2045570 dnsmasq[1507]: DNS service limited to local 
subnets
  Jan 03 13:57:13 j-dnsmasq-2045570 dnsmasq[1507]: compile time options: IPv6 
GNU-getopt DBus no-UBus i18n IDN2 DHCP DHCPv6 no-Lua TFTP conntrack ipset auth 
cryptohash DNSSEC loop-detect inotify dumpfile
  Jan 03 13:57:13 j-dnsmasq-2045570 dnsmasq[1507]: reading /etc/resolv.conf
  Jan 03 13:57:13 j-dnsmasq-2045570 dnsmasq[1507]: using nameserver 
10.0.100.1#53
  Jan 03 13:57:13 j-dnsmasq-2045570 dnsmasq[1507]: read /etc/hosts - 7 addresses
  Jan 03 13:57:13 j-dnsmasq-2045570 systemd[1]: Started dnsmasq - A lightweight 
DHCP and caching DNS server.
  Jan 03 13:58:01 j-dnsmasq-2045570 dnsmasq[1507]: no servers found in 
/etc/resolv.conf, will retry
  Jan 03 13:58:22 j-dnsmasq-2045570 systemd[1]: dnsmasq.service: Main process 
exited, code=dumped, status=11/SEGV
  Jan 03 13:58:22 j-dnsmasq-2045570 systemd[1]: dnsmasq.service: Failed with 
result 'core-dump'.

  dnsmasq has provisions for this situation, we can see that in the
  13:58:01 message where it says it will retry, but due to this bug, it
  crashes instead.

  The problem was introduced[1] in version 2.86, and fixed in 2.87, so
  only jammy is affected.

  1. 
https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=patch;h=d290630d31f4517ab26392d00753d1397f9a4114;hp=d2ad5dc073aaacaf22b117f16106282a73586803
  The commit message says:
  """
  This problem was introduced in 2.86.
  """

  And indeed, I wasn't able to crash 2.80 shipped in focal.

  [ Test Plan ]
  It might take a few tries to reproduce the bug, but here is the general 
outline. Also keep in mind that it's important to use a DNS name that isn't 
cached already by a previous query.

  # Create a jammy lxd container

  lxc launch ubuntu-daily:jammy j-dnsmasq-2045570

  # Enter the container

  lxc shell j-dnsmasq-2045570

  # From now on, all commands should be executed in the container.
  # Install dnsmasq, and disable systemd-resolved

  apt update && apt install -y dnsmasq

  # Disable systemd-resolved, and start dnsmasq

  systemctl disable --now systemd-resolved
  systemctl enable --now dnsmasq

  # In one terminal inside the container, watch the dnsmasq logs:

  journalctl -u dnsmasq.service -f

  # In another terminal, remove /etc/resolv.conf and create a new one, empty
  rm /etc/resolv.conf
  echo "nameserver 1.1.1.1" > /etc/resolv.conf

  # restart dnsmasq
  systemctl restart dnsmasq.service

  # Perform a dns query

  dig @127.0.0.1 +short linux.com

  # Comment the namserver directive in resolv.conf
  echo "#nameserver 1.1.1.1" > /etc/resolv.conf

  # Observe in the dnsmasq logs that it notices the change with a
  message like:

  Jan 03 14:14:51 j-dnsmasq-2045570 dnsmasq[2274]: no servers found in
  /etc/resolv.conf, will retry

  # Perform a *different* DNS query

  dig @127.0.0.1 +short ubuntu.com

  # Observe in the dnsmasq logs that it crashes.
  Jan 03 13:58:22 j-dnsmasq-2045570 systemd[1]: dnsmasq.service: Main process 
exited, code=dumped, status=11/SEGV
  Jan 03 13:58:22 j-dnsmasq-2045570 systemd[1]: dnsmasq.service: Failed with 
result 'core-dump'.

  If it doesn't crash right away, repeat these steps a few times, but using a 
different domain name each time:
  - add "nameserver 127.0.0.1" to /etc/resolv.conf
  - observe that dnsmasq notices the change to the file
  - perform a query for some random domain using "dig @127.0.0.1 +short 
"
  - remove "nameserver" from /etc/resolv.conf, observe that dnsmasq noticed the 
change
  - perform a query for another random domain

  The fixed version from proposed will not crash. That last query with
  no "nameserver" lines in resolv.conf won't work, but it won't crash
  the server.

 

[Touch-packages] [Bug 2045570] Re: dnsmasq crash when no servers in resolv.conf

[Andreas Hasenack]

While performing the jammy verification, it happened once again what I
first saw in
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2045570/comments/4:
dnsmasq doesn't crash, but starts spinning 100% CPU and becomes
unresponsive.

I double checked that the source package contains the patch applied
correctly.

I'm repeating the test multiple times now, and not observing the 100%
cpu usage anymore...

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

Title:
  dnsmasq crash when no servers in resolv.conf

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in dnsmasq source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

  dnsmasq "keeps an eye" on /etc/resolv.conf, and reloads it whenever
  the file is updated. When that happens and for some reason there were
  no "nameserver" declarations in the updated file, dnsmasq can crash.

  Here is a log of a reproducer:
  $ dig +short @127.0.0.1 ubuntu.com
  ;; communications error to 127.0.0.1#53: timed out
  ;; communications error to 127.0.0.1#53: connection refused
  ;; communications error to 127.0.0.1#53: connection refused
  ;; no servers could be reached

  We can see the startup, then when resolv.conf is read again and no 
nameservers were found, and the crash:
  Jan 03 13:57:13 j-dnsmasq-2045570 dnsmasq[1507]: started, version 2.86 
cachesize 150
  Jan 03 13:57:13 j-dnsmasq-2045570 dnsmasq[1507]: DNS service limited to local 
subnets
  Jan 03 13:57:13 j-dnsmasq-2045570 dnsmasq[1507]: compile time options: IPv6 
GNU-getopt DBus no-UBus i18n IDN2 DHCP DHCPv6 no-Lua TFTP conntrack ipset auth 
cryptohash DNSSEC loop-detect inotify dumpfile
  Jan 03 13:57:13 j-dnsmasq-2045570 dnsmasq[1507]: reading /etc/resolv.conf
  Jan 03 13:57:13 j-dnsmasq-2045570 dnsmasq[1507]: using nameserver 
10.0.100.1#53
  Jan 03 13:57:13 j-dnsmasq-2045570 dnsmasq[1507]: read /etc/hosts - 7 addresses
  Jan 03 13:57:13 j-dnsmasq-2045570 systemd[1]: Started dnsmasq - A lightweight 
DHCP and caching DNS server.
  Jan 03 13:58:01 j-dnsmasq-2045570 dnsmasq[1507]: no servers found in 
/etc/resolv.conf, will retry
  Jan 03 13:58:22 j-dnsmasq-2045570 systemd[1]: dnsmasq.service: Main process 
exited, code=dumped, status=11/SEGV
  Jan 03 13:58:22 j-dnsmasq-2045570 systemd[1]: dnsmasq.service: Failed with 
result 'core-dump'.

  dnsmasq has provisions for this situation, we can see that in the
  13:58:01 message where it says it will retry, but due to this bug, it
  crashes instead.

  The problem was introduced[1] in version 2.86, and fixed in 2.87, so
  only jammy is affected.

  1. 
https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=patch;h=d290630d31f4517ab26392d00753d1397f9a4114;hp=d2ad5dc073aaacaf22b117f16106282a73586803
  The commit message says:
  """
  This problem was introduced in 2.86.
  """

  And indeed, I wasn't able to crash 2.80 shipped in focal.

  [ Test Plan ]
  It might take a few tries to reproduce the bug, but here is the general 
outline. Also keep in mind that it's important to use a DNS name that isn't 
cached already by a previous query.

  # Create a jammy lxd container

  lxc launch ubuntu-daily:jammy j-dnsmasq-2045570

  # Enter the container

  lxc shell j-dnsmasq-2045570

  # From now on, all commands should be executed in the container.
  # Install dnsmasq, and disable systemd-resolved

  apt update && apt install -y dnsmasq

  # Disable systemd-resolved, and start dnsmasq

  systemctl disable --now systemd-resolved
  systemctl enable --now dnsmasq

  # In one terminal inside the container, watch the dnsmasq logs:

  journalctl -u dnsmasq.service -f

  # In another terminal, remove /etc/resolv.conf and create a new one, empty
  rm /etc/resolv.conf
  echo "nameserver 1.1.1.1" > /etc/resolv.conf

  # restart dnsmasq
  systemctl restart dnsmasq.service

  # Perform a dns query

  dig @127.0.0.1 +short linux.com

  # Comment the namserver directive in resolv.conf
  echo "#nameserver 1.1.1.1" > /etc/resolv.conf

  # Observe in the dnsmasq logs that it notices the change with a
  message like:

  Jan 03 14:14:51 j-dnsmasq-2045570 dnsmasq[2274]: no servers found in
  /etc/resolv.conf, will retry

  # Perform a *different* DNS query

  dig @127.0.0.1 +short ubuntu.com

  # Observe in the dnsmasq logs that it crashes.
  Jan 03 13:58:22 j-dnsmasq-2045570 systemd[1]: dnsmasq.service: Main process 
exited, code=dumped, status=11/SEGV
  Jan 03 13:58:22 j-dnsmasq-2045570 systemd[1]: dnsmasq.service: Failed with 
result 'core-dump'.

  If it doesn't crash right away, repeat these steps a few times, but using a 
different domain name each time:
  - add "nameserver 127.0.0.1" to /etc/resolv.conf
  - observe that dnsmasq notices the change to the file
  - perform a query for some random domain using "dig @127.0.0.1 +short 
"
  - remove "nameserver" from /etc/resolv.conf, observe that dnsmasq noticed the 
change
  - 

[Touch-packages] [Bug 2051015] [NEW] Unable to install : dependencies missing

[Yves Roggeman]

Public bug reported:

Version 8.3.0-2
Package depends on gir1.2-freetype2-2.0-dev and gir1.2-gobject-2.0-dev that do 
not exist.
So this version cannot be installed.

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

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

Title:
  Unable to install : dependencies missing

Status in harfbuzz package in Ubuntu:
  New

Bug description:
  Version 8.3.0-2
  Package depends on gir1.2-freetype2-2.0-dev and gir1.2-gobject-2.0-dev that 
do not exist.
  So this version cannot be installed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/harfbuzz/+bug/2051015/+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 2045586] Re: livecd-rootfs uses losetup -P for theoretically reliable/synchronous partition setup but it's not reliable

[dann frazier]

** Summary changed:

- livecd-rootfs uses losetup -P for theoretically reliable/synchronous 
partition setup but it's not reliable in noble
+ livecd-rootfs uses losetup -P for theoretically reliable/synchronous 
partition setup but it's not reliable

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

Title:
  livecd-rootfs uses losetup -P for theoretically reliable/synchronous
  partition setup but it's not reliable

Status in linux package in Ubuntu:
  New
Status in livecd-rootfs package in Ubuntu:
  New
Status in util-linux package in Ubuntu:
  New

Bug description:
  In mantic, we migrated livecd-rootfs to use losetup -P instead of
  kpartx, with the expectation that this would give us a reliable, race-
  free way of loop-mounting partitions from a disk image during image
  build.

  In noble, we are finding that it is no longer reliable, and in fact
  fails rather often.

  It is most noticeable with riscv64 builds, which is the architecture
  where we most frequently ran into problems before with kpartx.  The
  first riscv64+generic build in noble where the expected loop partition
  device is not available is

https://launchpad.net/~ubuntu-
  cdimage/+livefs/ubuntu/noble/cpc/+build/531790

  The failure is however not unique to riscv64, and the autopkgtest for
  the latest version of livecd-rootfs (24.04.7) - an update that
  specifically tries to add more debugging code for this scenario - has
  also failed on ppc64el.

https://autopkgtest.ubuntu.com/packages/l/livecd-
  rootfs/noble/ppc64el

  The first failure happened on November 16.  While there has been an
  update to the util-linux package in noble, this did not land until
  November 23.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045586/+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 2049369] Re: autopkg tests ignored for migration of python3-defaults adding 3.12

[Bug Watch Updater]

** Changed in: jupyter-client (Debian)
   Status: New => Confirmed

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

Title:
  autopkg tests ignored for migration of python3-defaults adding 3.12

Status in cython package in Ubuntu:
  New
Status in cython-legacy package in Ubuntu:
  New
Status in ipykernel package in Ubuntu:
  New
Status in ironic-python-agent package in Ubuntu:
  New
Status in jupyter-client package in Ubuntu:
  New
Status in numpy package in Ubuntu:
  New
Status in python-memory-profiler package in Ubuntu:
  New
Status in python-oslo.versionedobjects package in Ubuntu:
  Fix Released
Status in python-urllib3 package in Ubuntu:
  New
Status in python3-defaults package in Ubuntu:
  New
Status in rich package in Ubuntu:
  New
Status in sphinx-autoapi package in Ubuntu:
  New
Status in vcr.py package in Ubuntu:
  New
Status in cython package in Debian:
  Confirmed
Status in cython-legacy package in Debian:
  New
Status in ipykernel package in Debian:
  New
Status in jupyter-client package in Debian:
  Confirmed
Status in numpy package in Debian:
  New
Status in python-memory-profiler package in Debian:
  New
Status in python-urllib3 package in Debian:
  Fix Released
Status in rich package in Debian:
  Confirmed
Status in sphinx-autoapi package in Debian:
  Fix Released
Status in vcr.py package in Debian:
  Fix Released

Bug description:
  autopkg tests ignored for migration of python3-defaults adding 3.12:

  These are the autopkg tests for packages, which we'll ignore for the
  initial migration of python3-defaults adding 3.12.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cython/+bug/2049369/+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 2042587] Re: jammy's version breaks existing dhcp scripts with relay

[Andreas Hasenack]

The autopkgtests are green now.

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

Title:
  jammy's version breaks existing dhcp scripts with relay

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in dnsmasq source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

  When upgrading from focal to jammy, existing dnsmasq dhcp-scripts
  stopped working in an environment where a DHCP relay is in use.
  Instead of the expected client IP address, the script gets the _relay_
  IP address as an argument.

  This was fixed in 2.87, therefore making only jammy carry an affected
  package.

  [ Test Plan ]

  To easily test this on a single machine, a test script is being
  provided to setup networking and dnsmasq configuration.

  # Launch a jammy VM

  lxc launch ubuntu-daily:jammy j-dnsmasq-2042587 --vm

  # open a root shell in that VM. All subsequent commands must be
  executed as root in that VM

  lxc shell j-dnsmasq-2042587

  # download test script

  wget
  
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2042587/+attachment/5738174/+files/setup-
  and-server.sh

  # make it executable

  chmod +x setup-and-server.sh

  # install dnsmasq. Ignore the postinst error (because systemd-resolved
  is also running and there is a port conflict)

  apt update && apt install dnsmasq -y

  # run the setup script. It will configure things and start dnsmasq
  ready to be tested

  ./setup-and-server.sh

  # in another root session inside the vm (so run "lxc shell
  j-dnsmasq-2042587" in another terminal), run the proposed commands
  from the setup script (and press ctrl-c after the result is shown):

  No DHCP relay:

    ip netns exec client dhclient -d -v p2

  The setup script should log an IP that is not a relay. For example:
  dnsmasq-dhcp: DHCPDISCOVER(p1) aa:a0:9d:00:5b:d6
  dnsmasq-dhcp: DHCPOFFER(p1) 192.168.47.150 aa:a0:9d:00:5b:d6
  dnsmasq-dhcp: DHCPREQUEST(p1) 192.168.47.150 aa:a0:9d:00:5b:d6
  dnsmasq-dhcp: DHCPACK(p1) 192.168.47.150 aa:a0:9d:00:5b:d6 j-dnsmasq-2042587
  ###
  IP = 192.168.47.150
  ###

  With DHCP relay set to 192.168.47.9, IP should NOT be that address:

    ip netns exec client dhclient -d -v p2 -g 192.168.47.9

  With the affected dnsmasq package, we will see an error:
  dnsmasq-dhcp: DHCPREQUEST(p1) 192.168.47.150 aa:a0:9d:00:5b:d6
  dnsmasq-dhcp: DHCPACK(p1) 192.168.47.150 aa:a0:9d:00:5b:d6 j-dnsmasq-2042587
  ###
  IP = 192.168.47.9
  TEST FAILED
  ###

  The error is that the obtained IP is that of the dhcp relay (provided
  via the -g option).

  With the fixed dnsmasq package, "TEST FAILED" must not appear, and the
  IP should not be that of the provided dhcp relay.

  [ Where problems could occur ]

  If the fix is incorrect, it would mean the dhcp-script would get an incorrect 
IP again, or perhaps we could have crashes in dnsmasq when dealing with buffers 
and pointers if the dhcp-script option is in use.
  This fix was committed upstream a few months after the bug was introduced, so 
it took a while to be noticed.

  [ Other Info ]
  Not at this time.

  [ Original description ]

  When upgrading from focal to jammy, existing dnsmasq dhcp-scripts
  stopped working in an environment where a DHCP relay is in use.
  Instead of the expected client IP address, the script gets the _relay_
  IP address as an argument. From dnsmasq documentation for --dhcp-
  script:

  > The arguments to the process are "add", "old" or "del", the MAC
  address of the host (or DUID for IPv6) , the IP address, and the
  hostname, if known.

  I believe the change has been inadverently made in upstream commit
  527c3c7d0d3bb4bf5fad699f10cf0d1a45a54692
  
(https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=blobdiff;f=src/helper.c;h=02340a01c00031db0cc682c8a4a279cfc1db574e;hp=d81de9622e6d484a264496b2cd3638b4e15e9677;hb=527c3c7d0d3bb4bf5fad699f10cf0d1a45a54692;hpb=fcb4dcaf7cc8a86ac2533b933161b6455f75bf8f)
  as the commit message only speaks about inet_ntoa replacement and not
  the behavioral change it also introduces (previously the relay address
  was only set to the environment variable, now it effectively overrides
  the prevoiusly set client's IP address).

  dnsmasq 2.86-1.1ubuntu0.3 / Ubuntu 22.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2042587/+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 2037604] Re: Backport packages for 22.04.4 HWE stack

[Timo Aaltonen]

** Description changed:

  [Impact]
  The graphics HWE stack from mantic needs to be backported for 22.04.4
  
  directx-headers
  - build-dep of the new Mesa
  
  mesa
  - new major release (23.2.x)
  - new HW support, Meteor Lake..
  
  [Test case]
  We want to cover at least 2-3 different, widely used and already previously 
supported GPU generations from both AMD and Intel which are supported by this 
release, as those are the ones that cover most bases; nouveau users tend to 
switch to the NVIDIA blob after installation. No need to test ancient GPU's 
supported by mesa-amber. And best to focus on the newer generations (~5y and 
newer) as the older ones are less likely to break at this point.
  - AMD: Vega, Navi1x (RX5000*), Navi2x (RX6000*), Navi3x (RX7000*)
- - Intel: gen9 (SKL/APL/KBL/CFL/WHL/CML), gen11 (ICL), gen12 (TGL/RKL/RPL/DG2)
+ - Intel: gen9 (SKL/APL/KBL/CFL/WHL/CML), gen11 (ICL), gen12 
(TGL/ADL/RKL/RPL/DG2)
  
  Install the new packages and run some tests:
  - check that the desktop is still using hw acceleration and hasn't fallen 
back to swrast/llvmpipe
  - run freely available benchmarks that torture the GPU (Unigine 
Heaven/Valley/Superposition)
  - run some games from Steam if possible
  
  and in each case check that there is no gfx corruption happening or
  worse.
  
  Note that upstream releases have already been tested for OpenGL and
  Vulkan conformance by their CI.
  
  [Where things could go wrong]
  This is a major update of Mesa, there could be regressions but we'll try to 
catch any with testing. And since it shares bugs with mantic, we'd already know 
if there are serious issues. We will backport the final 23.2.x at a later 
stage, the first backport is needed for enabling Intel Meteor Lake.

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

Title:
  Backport packages for 22.04.4 HWE stack

Status in directx-headers package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in rust-bindgen package in Ubuntu:
  Invalid
Status in rust-clang-sys package in Ubuntu:
  Invalid
Status in directx-headers source package in Jammy:
  Fix Committed
Status in mesa source package in Jammy:
  Fix Committed
Status in rust-bindgen source package in Jammy:
  Invalid
Status in rust-clang-sys source package in Jammy:
  Invalid

Bug description:
  [Impact]
  The graphics HWE stack from mantic needs to be backported for 22.04.4

  directx-headers
  - build-dep of the new Mesa

  mesa
  - new major release (23.2.x)
  - new HW support, Meteor Lake..

  [Test case]
  We want to cover at least 2-3 different, widely used and already previously 
supported GPU generations from both AMD and Intel which are supported by this 
release, as those are the ones that cover most bases; nouveau users tend to 
switch to the NVIDIA blob after installation. No need to test ancient GPU's 
supported by mesa-amber. And best to focus on the newer generations (~5y and 
newer) as the older ones are less likely to break at this point.
  - AMD: Vega, Navi1x (RX5000*), Navi2x (RX6000*), Navi3x (RX7000*)
  - Intel: gen9 (SKL/APL/KBL/CFL/WHL/CML), gen11 (ICL), gen12 
(TGL/ADL/RKL/RPL/DG2)

  Install the new packages and run some tests:
  - check that the desktop is still using hw acceleration and hasn't fallen 
back to swrast/llvmpipe
  - run freely available benchmarks that torture the GPU (Unigine 
Heaven/Valley/Superposition)
  - run some games from Steam if possible

  and in each case check that there is no gfx corruption happening or
  worse.

  Note that upstream releases have already been tested for OpenGL and
  Vulkan conformance by their CI.

  [Where things could go wrong]
  This is a major update of Mesa, there could be regressions but we'll try to 
catch any with testing. And since it shares bugs with mantic, we'd already know 
if there are serious issues. We will backport the final 23.2.x at a later 
stage, the first backport is needed for enabling Intel Meteor Lake.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/2037604/+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 2037667] Re: Regression on Jammy's kernel 5.15 when creating ip6gre and vti6 tunnels

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  Regression on Jammy's kernel 5.15 when creating ip6gre and vti6
  tunnels

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  Triaged
Status in systemd source package in Jammy:
  New

Bug description:
  We noticed that some of Netplan's integration tests started to fail on
  Jammy. These tests will try to create ip6gre and vti6 virtual
  interfaces and systemd-networkd is failing to create them starting on
  kernel 5.15.0-83.92. As far as I can tell, kernel 5.15.0-82.91 is the
  last revision where it works. So, some change between 5.15.0-82.91 and
  5.15.0-83.92 is causing this regression.

  How to reproduce the issue:

  # Launch a jammy cloud VM:

  lxc launch images:ubuntu/jammy/cloud jammy --vm
  lxc shell jammy

  # Create a netplan file that creates 2 tunnels:
   
  cat > /etc/netplan/10-tun.yaml 2' && reboot

  # Check with "ip link" again that both tun0 and tun1 were created

  # Reboot again to go back to the most recent kernel and check with "ip link" 
that both tun0 and tun1 were not created.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 29 12:52 seq
   crw-rw 1 root audio 116, 33 Sep 29 12:52 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: lxd
  CloudName: lxd
  CloudPlatform: lxd
  CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock)
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci: Error: [Errno 2] No such file or directory: 'lspci'
  Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci'
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb'
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 virtio_gpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-84-generic root=/dev/sda2 
ro quiet splash console=tty1 console=ttyS0 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-84.93-generic 5.15.116
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-84-generic N/A
   linux-backports-modules-5.15.0-84-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-84-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 2/2/2022
  dmi.bios.release: 0.0
  dmi.bios.vendor: EDK II
  dmi.bios.version: unknown
  dmi.board.name: LXD
  dmi.board.vendor: Canonical Ltd.
  dmi.board.version: pc-q35-8.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-8.0
  dmi.modalias: 
dmi:bvnEDKII:bvrunknown:bd2/2/2022:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-8.0:rvnCanonicalLtd.:rnLXD:rvrpc-q35-8.0:cvnQEMU:ct1:cvrpc-q35-8.0:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-8.0
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037667/+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 2029173] Re: fatal error: cannot open file '/usr/lib/clc/gfx1031-amdgcn-mesa-mesa3d.bc': No such file or directory

[Oibaf]

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

Let's mark this as a duplicate of bug 1909805.

** This bug has been marked a duplicate of bug 1909805
   libclc-amdgcn missing files for current AMD APUs

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

Title:
  fatal error: cannot open file '/usr/lib/clc/gfx1031-amdgcn-mesa-
  mesa3d.bc': No such file or directory

Status in mesa package in Ubuntu:
  New

Bug description:
  Programs using OpenCL report the following bug:
  fatal error: cannot open file '/usr/lib/clc/gfx1031-amdgcn-mesa-mesa3d.bc': 
No such file or directory

  This bug is encountered when trying to run
  github.com/ggerganov/llama.cpp build with CLBlast or just using
  clinfo.

  The hardware is an AMD Radeon RX 6700 XT

  lsb_release -rd:
  No LSB modules are available.
  Description:Ubuntu 23.04
  Release:23.04

  
  apt-cache policy mesa-opencl-icd  #although I am not sure that this is the 
offending package
  mesa-opencl-icd:
Installed: 23.0.4-0ubuntu1~23.04.1
Candidate: 23.0.4-0ubuntu1~23.04.1
Version table:
   *** 23.0.4-0ubuntu1~23.04.1 500
  500 http://de.archive.ubuntu.com/ubuntu lunar-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   23.0.2-1ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu lunar/universe amd64 Packages
  pc@pc-MS-7C02:~/ML/llama.cpp$ 

  
  clinfo output:
  Number of platforms   2
Platform Name   Clover
Platform Vendor Mesa
Platform VersionOpenCL 1.1 Mesa 
23.0.4-0ubuntu1~23.04.1
Platform ProfileFULL_PROFILE
Platform Extensions cl_khr_icd
Platform Extensions function suffix MESA

Platform Name   rusticl
Platform Vendor Mesa/X.org
Platform VersionOpenCL 3.0 
Platform ProfileFULL_PROFILE
Platform Extensions cl_khr_icd
Platform Extensions with Versioncl_khr_icd  
 0x40 (1.0.0)
Platform Numeric Version0xc0 (3.0.0)
Platform Extensions function suffix MESA
Platform Host timer resolution  0ns

Platform Name   Clover
  Number of devices 1
Device Name AMD Radeon RX 6700 XT 
(navi22, LLVM 15.0.7, DRM 3.49, 6.2.0-26-generic)
Device Vendor   AMD
Device Vendor ID0x1002
Device Version  OpenCL 1.1 Mesa 
23.0.4-0ubuntu1~23.04.1
Device Numeric Version  0x401000 (1.1.0)
Driver Version  23.0.4-0ubuntu1~23.04.1
Device OpenCL C Version OpenCL C 1.1 
Device OpenCL C Numeric Version 0x401000 (1.1.0)
Device Type GPU
Device Profile  FULL_PROFILE
Device AvailableYes
Compiler Available  Yes
Max compute units   40
Max clock frequency 2855MHz
Max work item dimensions3
Max work item sizes 256x256x256
Max work group size 256
  === CL_PROGRAM_BUILD_LOG ===
  fatal error: cannot open file '/usr/lib/clc/gfx1031-amdgcn-mesa-mesa3d.bc': 
No such file or directory
Preferred work group size multiple (kernel) 
Preferred / native vector sizes 
  char16 / 16  
  short8 / 8   
  int  4 / 4   
  long 2 / 2   
  half 0 / 0(n/a)
  float4 / 4   
  double   2 / 2
(cl_khr_fp64)
Half-precision Floating-point support   (n/a)
Single-precision Floating-point support (core)
  Denormals No
  Infinity and NANs Yes
  Round to nearest  Yes
  Round to zero No
 

[Touch-packages] [Bug 2029173] Re: fatal error: cannot open file '/usr/lib/clc/gfx1031-amdgcn-mesa-mesa3d.bc': No such file or directory

[lorn10]

Yeah, this is (or was) not a problem of Ubuntu nor it was a problem of
Mesa.

In the end it was a problem of libclc (which is part of LLVM) not
supporting newer Radeon hardware (I think anything newer than GCN4).

Whatever, - this problem was resolved when the libclc was updated:
https://github.com/llvm/llvm-project/pull/78884

Ergo, as of the end of January 2024 libclc includes support for Radeon
hardware up to the RDNA2 generation.

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

Title:
  fatal error: cannot open file '/usr/lib/clc/gfx1031-amdgcn-mesa-
  mesa3d.bc': No such file or directory

Status in mesa package in Ubuntu:
  New

Bug description:
  Programs using OpenCL report the following bug:
  fatal error: cannot open file '/usr/lib/clc/gfx1031-amdgcn-mesa-mesa3d.bc': 
No such file or directory

  This bug is encountered when trying to run
  github.com/ggerganov/llama.cpp build with CLBlast or just using
  clinfo.

  The hardware is an AMD Radeon RX 6700 XT

  lsb_release -rd:
  No LSB modules are available.
  Description:Ubuntu 23.04
  Release:23.04

  
  apt-cache policy mesa-opencl-icd  #although I am not sure that this is the 
offending package
  mesa-opencl-icd:
Installed: 23.0.4-0ubuntu1~23.04.1
Candidate: 23.0.4-0ubuntu1~23.04.1
Version table:
   *** 23.0.4-0ubuntu1~23.04.1 500
  500 http://de.archive.ubuntu.com/ubuntu lunar-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   23.0.2-1ubuntu1 500
  500 http://de.archive.ubuntu.com/ubuntu lunar/universe amd64 Packages
  pc@pc-MS-7C02:~/ML/llama.cpp$ 

  
  clinfo output:
  Number of platforms   2
Platform Name   Clover
Platform Vendor Mesa
Platform VersionOpenCL 1.1 Mesa 
23.0.4-0ubuntu1~23.04.1
Platform ProfileFULL_PROFILE
Platform Extensions cl_khr_icd
Platform Extensions function suffix MESA

Platform Name   rusticl
Platform Vendor Mesa/X.org
Platform VersionOpenCL 3.0 
Platform ProfileFULL_PROFILE
Platform Extensions cl_khr_icd
Platform Extensions with Versioncl_khr_icd  
 0x40 (1.0.0)
Platform Numeric Version0xc0 (3.0.0)
Platform Extensions function suffix MESA
Platform Host timer resolution  0ns

Platform Name   Clover
  Number of devices 1
Device Name AMD Radeon RX 6700 XT 
(navi22, LLVM 15.0.7, DRM 3.49, 6.2.0-26-generic)
Device Vendor   AMD
Device Vendor ID0x1002
Device Version  OpenCL 1.1 Mesa 
23.0.4-0ubuntu1~23.04.1
Device Numeric Version  0x401000 (1.1.0)
Driver Version  23.0.4-0ubuntu1~23.04.1
Device OpenCL C Version OpenCL C 1.1 
Device OpenCL C Numeric Version 0x401000 (1.1.0)
Device Type GPU
Device Profile  FULL_PROFILE
Device AvailableYes
Compiler Available  Yes
Max compute units   40
Max clock frequency 2855MHz
Max work item dimensions3
Max work item sizes 256x256x256
Max work group size 256
  === CL_PROGRAM_BUILD_LOG ===
  fatal error: cannot open file '/usr/lib/clc/gfx1031-amdgcn-mesa-mesa3d.bc': 
No such file or directory
Preferred work group size multiple (kernel) 
Preferred / native vector sizes 
  char16 / 16  
  short8 / 8   
  int  4 / 4   
  long 2 / 2   
  half 0 / 0(n/a)
  float4 / 4   
  double   2 / 2
(cl_khr_fp64)
Half-precision Floating-point support   (n/a)
Single-precision Floating-point support (core)
  Denormals 

[Touch-packages] [Bug 2037667] Re: Regression on Jammy's kernel 5.15 when creating ip6gre and vti6 tunnels

[Nick Rosbrook]

** Tags added: systemd-sru-next

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

Title:
  Regression on Jammy's kernel 5.15 when creating ip6gre and vti6
  tunnels

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  Triaged
Status in systemd source package in Jammy:
  New

Bug description:
  We noticed that some of Netplan's integration tests started to fail on
  Jammy. These tests will try to create ip6gre and vti6 virtual
  interfaces and systemd-networkd is failing to create them starting on
  kernel 5.15.0-83.92. As far as I can tell, kernel 5.15.0-82.91 is the
  last revision where it works. So, some change between 5.15.0-82.91 and
  5.15.0-83.92 is causing this regression.

  How to reproduce the issue:

  # Launch a jammy cloud VM:

  lxc launch images:ubuntu/jammy/cloud jammy --vm
  lxc shell jammy

  # Create a netplan file that creates 2 tunnels:
   
  cat > /etc/netplan/10-tun.yaml 2' && reboot

  # Check with "ip link" again that both tun0 and tun1 were created

  # Reboot again to go back to the most recent kernel and check with "ip link" 
that both tun0 and tun1 were not created.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 29 12:52 seq
   crw-rw 1 root audio 116, 33 Sep 29 12:52 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: lxd
  CloudName: lxd
  CloudPlatform: lxd
  CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock)
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci: Error: [Errno 2] No such file or directory: 'lspci'
  Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci'
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb'
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 virtio_gpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-84-generic root=/dev/sda2 
ro quiet splash console=tty1 console=ttyS0 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-84.93-generic 5.15.116
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-84-generic N/A
   linux-backports-modules-5.15.0-84-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-84-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 2/2/2022
  dmi.bios.release: 0.0
  dmi.bios.vendor: EDK II
  dmi.bios.version: unknown
  dmi.board.name: LXD
  dmi.board.vendor: Canonical Ltd.
  dmi.board.version: pc-q35-8.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-8.0
  dmi.modalias: 
dmi:bvnEDKII:bvrunknown:bd2/2/2022:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-8.0:rvnCanonicalLtd.:rnLXD:rvrpc-q35-8.0:cvnQEMU:ct1:cvrpc-q35-8.0:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-8.0
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037667/+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 2040406] Re: Merge openssh from Debian unstable for noble

[Miriam España Acebal]

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

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

Title:
  Merge openssh from Debian unstable for noble

Status in openssh package in Ubuntu:
  In Progress

Bug description:
  Scheduled-For: Backlog
  Upstream: tbd
  Debian:   1:9.4p1-1
  Ubuntu:   1:9.3p1-1ubuntu3

  
  The NOT SERVER TEAM team has maintained this package in the past and may be 
handling this merge.

  If it turns out this needs a sync rather than a merge, please change
  the tag 'needs-merge' to 'needs-sync', and (optionally) update the
  title as desired.

  
  ### New Debian Changes ###

  openssh (1:9.4p1-1) unstable; urgency=medium

* New upstream release (https://www.openssh.com/releasenotes.html#9.4p1):
  - ssh-agent(1): PKCS#11 modules must now be specified by their full
paths. Previously dlopen(3) could search for them in system library
directories.
  - ssh(1): allow forwarding Unix Domain sockets via ssh -W.
  - ssh(1): add support for configuration tags to ssh(1). This adds a
ssh_config(5) 'Tag' directive and corresponding 'Match tag' predicate
that may be used to select blocks of configuration similar to the
pf.conf(5) keywords of the same name.
  - ssh(1): add a 'match localnetwork' predicate. This allows matching on
the addresses of available network interfaces and may be used to vary
the effective client configuration based on network location.
  - ssh(1), sshd(8), ssh-keygen(1): infrastructure support for KRL
extensions. This defines wire formats for optional KRL extensions and
implements parsing of the new submessages. No actual extensions are
supported at this point.
  - sshd(8): AuthorizedPrincipalsCommand and AuthorizedKeysCommand now
accept two additional %-expansion sequences: %D which expands to the
routing domain of the connected session and %C which expands to the
addresses and port numbers for the source and destination of the
connection.
  - ssh-keygen(1): increase the default work factor (rounds) for the
bcrypt KDF used to derive symmetric encryption keys for passphrase
protected key files by 50%.
  - ssh-agent(1): improve isolation between loaded PKCS#11 modules by
running separate ssh-pkcs11-helpers for each loaded provider.
  - ssh(1): make -f (fork after authentication) work correctly with
multiplexed connections, including ControlPersist (closes: #348741).
  - ssh(1): make ConnectTimeout apply to multiplexing sockets and not just
to network connections.
  - ssh-agent(1), ssh(1): improve defences against invalid PKCS#11 modules
being loaded by checking that the requested module contains the
required symbol before loading it.
  - sshd(8): fix AuthorizedPrincipalsCommand when AuthorizedKeysCommand
appears before it in sshd_config. Since OpenSSH 8.7 the
AuthorizedPrincipalsCommand directive was incorrectly ignored in this
situation.
  - sshd(8), ssh(1), ssh-keygen(1): remove vestigial support for KRL
signatures. When the KRL format was originally defined, it included
support for signing of KRL objects. However, the code to sign KRLs and
verify KRL signatues was never completed in OpenSSH. This release
removes the partially-implemented code to verify KRLs. All OpenSSH
tools now ignore KRL_SECTION_SIGNATURE sections in KRL files.
  - All: fix a number of memory leaks and unreachable/harmless integer
overflows.
  - ssh-agent(1), ssh(1): don't truncate strings logged from PKCS#11
modules.
  - sshd(8), ssh(1): better validate CASignatureAlgorithms in ssh_config
and sshd_config. Previously this directive would accept certificate
algorithm names, but these were unusable in practice as OpenSSH does
not support CA chains.
  - ssh(1): make `ssh -Q CASignatureAlgorithms` only list signature
algorithms that are valid for CA signing. Previous behaviour was to
list all signing algorithms, including certificate algorithms.
  - ssh-keyscan(1): gracefully handle systems where rlimits or the maximum
number of open files is larger than INT_MAX.
  - ssh-keygen(1): fix 'no comment' not showing on when running
`ssh-keygen -l` on multiple keys where one has a comment and other
following keys do not. bz3580
  - scp(1), sftp(1): adjust ftruncate() logic to handle servers that
reorder requests. Previously, if the server reordered requests then
the resultant file would be erroneously truncated.
  - ssh(1): don't incorrectly disable hostname canonicalization when
CanonicalizeHostname=yes and ProxyJump was explicitly set to 

[Touch-packages] [Bug 2037667] Re: Regression on Jammy's kernel 5.15 when creating ip6gre and vti6 tunnels

[Lukas Märdian]

Actually, we can further reduce the patch to the removal of
`.generate_mac = true`. This already fixes the issue we observe here.

** Patch added: "lp2037667.patch"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037667/+attachment/5741632/+files/lp2037667.patch

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

Title:
  Regression on Jammy's kernel 5.15 when creating ip6gre and vti6
  tunnels

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  Triaged
Status in systemd source package in Jammy:
  New

Bug description:
  We noticed that some of Netplan's integration tests started to fail on
  Jammy. These tests will try to create ip6gre and vti6 virtual
  interfaces and systemd-networkd is failing to create them starting on
  kernel 5.15.0-83.92. As far as I can tell, kernel 5.15.0-82.91 is the
  last revision where it works. So, some change between 5.15.0-82.91 and
  5.15.0-83.92 is causing this regression.

  How to reproduce the issue:

  # Launch a jammy cloud VM:

  lxc launch images:ubuntu/jammy/cloud jammy --vm
  lxc shell jammy

  # Create a netplan file that creates 2 tunnels:
   
  cat > /etc/netplan/10-tun.yaml 2' && reboot

  # Check with "ip link" again that both tun0 and tun1 were created

  # Reboot again to go back to the most recent kernel and check with "ip link" 
that both tun0 and tun1 were not created.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 29 12:52 seq
   crw-rw 1 root audio 116, 33 Sep 29 12:52 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: lxd
  CloudName: lxd
  CloudPlatform: lxd
  CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock)
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci: Error: [Errno 2] No such file or directory: 'lspci'
  Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci'
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb'
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 virtio_gpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-84-generic root=/dev/sda2 
ro quiet splash console=tty1 console=ttyS0 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-84.93-generic 5.15.116
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-84-generic N/A
   linux-backports-modules-5.15.0-84-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-84-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 2/2/2022
  dmi.bios.release: 0.0
  dmi.bios.vendor: EDK II
  dmi.bios.version: unknown
  dmi.board.name: LXD
  dmi.board.vendor: Canonical Ltd.
  dmi.board.version: pc-q35-8.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-8.0
  dmi.modalias: 
dmi:bvnEDKII:bvrunknown:bd2/2/2022:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-8.0:rvnCanonicalLtd.:rnLXD:rvrpc-q35-8.0:cvnQEMU:ct1:cvrpc-q35-8.0:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-8.0
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037667/+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 2037667] Re: Regression on Jammy's kernel 5.15 when creating ip6gre and vti6 tunnels

[Lukas Märdian]

This seems to do the trick using the following Netplan config as a
testcase.

All 3 interfaces (tun[0-2]) are correctly created with their local &
remote properties set:

root@jj-abi:~/systemd# ip link show dev tun0
19: tun0@NONE:  mtu 1448 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
link/gre6 fe80::1 brd 2001:dead:beef::2 permaddr e262:75ae:2aa0::
root@jj-abi:~/systemd# ip link show dev tun1
20: tun1@NONE:  mtu 1332 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
link/tunnel6 fe80::2 brd 2001:dead:beef::3 permaddr c2aa:7446:cc29::
root@jj-abi:~/systemd# ip link show dev tun2
21: tun2@NONE:  mtu 1444 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
link/gre6 fe80::3 brd 2001:dead:beef::4 permaddr 3ef2:274c:a921::


Netplan test config:
```
network:
  version: 2
  tunnels:
tun0:
  mode: ip6gre
  local: fe80::1
  remote: 2001:dead:beef::2
tun1:
  mode: vti6
  local: fe80::2
  remote: 2001:dead:beef::3
tun2:
  mode: ip6gre
  key: 1234
  local: fe80::3
  remote: 2001:dead:beef::4
```

** Patch added: "network-netdev-introduce-.iftype-to-netdev-vtable.patch"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037667/+attachment/5741625/+files/network-netdev-introduce-.iftype-to-netdev-vtable.patch

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

Title:
  Regression on Jammy's kernel 5.15 when creating ip6gre and vti6
  tunnels

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  Triaged
Status in systemd source package in Jammy:
  New

Bug description:
  We noticed that some of Netplan's integration tests started to fail on
  Jammy. These tests will try to create ip6gre and vti6 virtual
  interfaces and systemd-networkd is failing to create them starting on
  kernel 5.15.0-83.92. As far as I can tell, kernel 5.15.0-82.91 is the
  last revision where it works. So, some change between 5.15.0-82.91 and
  5.15.0-83.92 is causing this regression.

  How to reproduce the issue:

  # Launch a jammy cloud VM:

  lxc launch images:ubuntu/jammy/cloud jammy --vm
  lxc shell jammy

  # Create a netplan file that creates 2 tunnels:
   
  cat > /etc/netplan/10-tun.yaml 2' && reboot

  # Check with "ip link" again that both tun0 and tun1 were created

  # Reboot again to go back to the most recent kernel and check with "ip link" 
that both tun0 and tun1 were not created.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 29 12:52 seq
   crw-rw 1 root audio 116, 33 Sep 29 12:52 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: lxd
  CloudName: lxd
  CloudPlatform: lxd
  CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock)
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci: Error: [Errno 2] No such file or directory: 'lspci'
  Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci'
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb'
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 virtio_gpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-84-generic root=/dev/sda2 
ro quiet splash console=tty1 console=ttyS0 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-84.93-generic 5.15.116
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-84-generic N/A
   linux-backports-modules-5.15.0-84-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-84-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 2/2/2022
  dmi.bios.release: 0.0
  dmi.bios.vendor: EDK II
  dmi.bios.version: unknown
  dmi.board.name: LXD
  dmi.board.vendor: Canonical Ltd.
  dmi.board.version: pc-q35-8.0
  

[Touch-packages] [Bug 2050955] [NEW] consistently fails to resume from suspend

[Scott Stensland]

Public bug reported:

using integrated intel gpu no nvidia

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-17.17~22.04.1-generic 6.5.8
Uname: Linux 6.5.0-17-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
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: ubuntu:GNOME
Date: Tue Jan 23 08:39:14 2024
DistUpgraded: 2022-08-02 07:50:46,100 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 RocketLake-S GT1 [UHD Graphics 750] [8086:4c8a] (rev 04) 
(prog-if 00 [VGA controller])
   Subsystem: Dell RocketLake-S GT1 [UHD Graphics 750] [1028:09c5]
InstallationDate: Installed on 2022-04-28 (634 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
MachineType: Dell Inc. XPS 8940
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-17-generic 
root=UUID=cce872cb-0478-4e9a-b49b-c63cabcbe4f6 ro
SourcePackage: xorg
UpgradeStatus: Upgraded to jammy on 2022-08-02 (539 days ago)
dmi.bios.date: 09/14/2022
dmi.bios.release: 2.10
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.10.0
dmi.board.name: 0427JK
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr2.10.0:bd09/14/2022:br2.10:svnDellInc.:pnXPS8940:pvr:rvnDellInc.:rn0427JK:rvrA00:cvnDellInc.:ct3:cvr:sku09C5:
dmi.product.family: XPS
dmi.product.name: XPS 8940
dmi.product.sku: 09C5
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.14.1+22.04.20220820-0ubuntu1
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug jammy third-party-packages ubuntu uec-images

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

Title:
  consistently fails to resume from suspend

Status in xorg package in Ubuntu:
  New

Bug description:
  using integrated intel gpu no nvidia

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-17.17~22.04.1-generic 6.5.8
  Uname: Linux 6.5.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  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: ubuntu:GNOME
  Date: Tue Jan 23 08:39:14 2024
  DistUpgraded: 2022-08-02 07:50:46,100 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 RocketLake-S GT1 [UHD Graphics 750] [8086:4c8a] (rev 04) 
(prog-if 00 [VGA controller])
 Subsystem: Dell RocketLake-S GT1 [UHD Graphics 750] [1028:09c5]
  InstallationDate: Installed on 2022-04-28 (634 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  MachineType: Dell Inc. XPS 8940
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-17-generic 
root=UUID=cce872cb-0478-4e9a-b49b-c63cabcbe4f6 ro
  SourcePackage: xorg
  UpgradeStatus: Upgraded to jammy on 2022-08-02 (539 days ago)
  dmi.bios.date: 09/14/2022
  dmi.bios.release: 2.10
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.10.0
  dmi.board.name: 0427JK
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.10.0:bd09/14/2022:br2.10:svnDellInc.:pnXPS8940:pvr:rvnDellInc.:rn0427JK:rvrA00:cvnDellInc.:ct3:cvr:sku09C5:
  dmi.product.family: XPS
  dmi.product.name: XPS 8940
  dmi.product.sku: 09C5
  dmi.sys.vendor: Dell Inc.
  version.compiz: 

[Touch-packages] [Bug 2050954] [NEW] Xorg freeze

[Scott Stensland]

Public bug reported:

consistently fails to resume from suspend

using integrated intel gpu no nvidia

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-17.17~22.04.1-generic 6.5.8
Uname: Linux 6.5.0-17-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
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: ubuntu:GNOME
Date: Tue Jan 23 08:34:38 2024
DistUpgraded: 2022-08-02 07:50:46,100 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GpuHangFrequency: Several times a week
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Since before I upgraded
GraphicsCard:
 Intel Corporation RocketLake-S GT1 [UHD Graphics 750] [8086:4c8a] (rev 04) 
(prog-if 00 [VGA controller])
   Subsystem: Dell RocketLake-S GT1 [UHD Graphics 750] [1028:09c5]
InstallationDate: Installed on 2022-04-28 (634 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
MachineType: Dell Inc. XPS 8940
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-17-generic 
root=UUID=cce872cb-0478-4e9a-b49b-c63cabcbe4f6 ro
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to jammy on 2022-08-02 (539 days ago)
dmi.bios.date: 09/14/2022
dmi.bios.release: 2.10
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.10.0
dmi.board.name: 0427JK
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr2.10.0:bd09/14/2022:br2.10:svnDellInc.:pnXPS8940:pvr:rvnDellInc.:rn0427JK:rvrA00:cvnDellInc.:ct3:cvr:sku09C5:
dmi.product.family: XPS
dmi.product.name: XPS 8940
dmi.product.sku: 09C5
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.14.1+22.04.20220820-0ubuntu1
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3.1~22.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~22.04.1
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug freeze jammy third-party-packages ubuntu uec-images

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  consistently fails to resume from suspend

  using integrated intel gpu no nvidia

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-17.17~22.04.1-generic 6.5.8
  Uname: Linux 6.5.0-17-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  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: ubuntu:GNOME
  Date: Tue Jan 23 08:34:38 2024
  DistUpgraded: 2022-08-02 07:50:46,100 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Since before I upgraded
  GraphicsCard:
   Intel Corporation RocketLake-S GT1 [UHD Graphics 750] [8086:4c8a] (rev 04) 
(prog-if 00 [VGA controller])
 Subsystem: Dell RocketLake-S GT1 [UHD Graphics 750] [1028:09c5]
  InstallationDate: Installed on 2022-04-28 (634 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  MachineType: Dell Inc. XPS 8940
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-17-generic 
root=UUID=cce872cb-0478-4e9a-b49b-c63cabcbe4f6 ro
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to jammy on 2022-08-02 (539 days ago)
  dmi.bios.date: 09/14/2022
  dmi.bios.release: 2.10
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.10.0
  

[Touch-packages] [Bug 2037667] Re: Regression on Jammy's kernel 5.15 when creating ip6gre and vti6 tunnels

[Lukas Märdian]

So after bisecting systemd (v249..v251) on Jammy, this seems to be the
commit that changed behavior for the better:

https://github.com/systemd/systemd/commit/9f0cf80dd007491698978dbfe38158d74c1c9526

It probably needs some backporting for v249.11.

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

Title:
  Regression on Jammy's kernel 5.15 when creating ip6gre and vti6
  tunnels

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in linux source package in Jammy:
  Triaged
Status in systemd source package in Jammy:
  New

Bug description:
  We noticed that some of Netplan's integration tests started to fail on
  Jammy. These tests will try to create ip6gre and vti6 virtual
  interfaces and systemd-networkd is failing to create them starting on
  kernel 5.15.0-83.92. As far as I can tell, kernel 5.15.0-82.91 is the
  last revision where it works. So, some change between 5.15.0-82.91 and
  5.15.0-83.92 is causing this regression.

  How to reproduce the issue:

  # Launch a jammy cloud VM:

  lxc launch images:ubuntu/jammy/cloud jammy --vm
  lxc shell jammy

  # Create a netplan file that creates 2 tunnels:
   
  cat > /etc/netplan/10-tun.yaml 2' && reboot

  # Check with "ip link" again that both tun0 and tun1 were created

  # Reboot again to go back to the most recent kernel and check with "ip link" 
that both tun0 and tun1 were not created.
  --- 
  ProblemType: Bug
  AlsaDevices:
   total 0
   crw-rw 1 root audio 116,  1 Sep 29 12:52 seq
   crw-rw 1 root audio 116, 33 Sep 29 12:52 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: [Errno 2] No such file or directory: 'fuser'
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CloudArchitecture: x86_64
  CloudID: lxd
  CloudName: lxd
  CloudPlatform: lxd
  CloudSubPlatform: LXD socket API v. 1.0 (/dev/lxd/sock)
  DistroRelease: Ubuntu 22.04
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci: Error: [Errno 2] No such file or directory: 'lspci'
  Lspci-vt: Error: [Errno 2] No such file or directory: 'lspci'
  Lsusb: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-t: Error: [Errno 2] No such file or directory: 'lsusb'
  Lsusb-v: Error: [Errno 2] No such file or directory: 'lsusb'
  MachineType: QEMU Standard PC (Q35 + ICH9, 2009)
  Package: linux (not installed)
  PciMultimedia:
   
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 virtio_gpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-84-generic root=/dev/sda2 
ro quiet splash console=tty1 console=ttyS0 vt.handoff=7
  ProcVersionSignature: Ubuntu 5.15.0-84.93-generic 5.15.116
  RelatedPackageVersions:
   linux-restricted-modules-5.15.0-84-generic N/A
   linux-backports-modules-5.15.0-84-generic  N/A
   linux-firmware N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  jammy uec-images
  Uname: Linux 5.15.0-84-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: True
  dmi.bios.date: 2/2/2022
  dmi.bios.release: 0.0
  dmi.bios.vendor: EDK II
  dmi.bios.version: unknown
  dmi.board.name: LXD
  dmi.board.vendor: Canonical Ltd.
  dmi.board.version: pc-q35-8.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-q35-8.0
  dmi.modalias: 
dmi:bvnEDKII:bvrunknown:bd2/2/2022:br0.0:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-8.0:rvnCanonicalLtd.:rnLXD:rvrpc-q35-8.0:cvnQEMU:ct1:cvrpc-q35-8.0:sku:
  dmi.product.name: Standard PC (Q35 + ICH9, 2009)
  dmi.product.version: pc-q35-8.0
  dmi.sys.vendor: QEMU

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037667/+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 2045033] Re: Merge rsyslog 8.2312.0-2 from Debian

[Launchpad Bug Tracker]

This bug was fixed in the package rsyslog - 8.2312.0-3ubuntu1

---
rsyslog (8.2312.0-3ubuntu1) noble; urgency=medium

  Merge with Debian unstable (LP: #2045033). Remaining changes:
- d/00rsyslog.conf, d/rsyslog.postinst, d/rsyslog.install: Install
  tmpfiles.d snippet to ensure that the syslog group can write into
  /var/log/.
- debian/50-default.conf: set of default rules for syslog
  + debian/50-default.conf: separated default rules
  + d/rsyslog.install: install default rules
  + d/rsyslog.postrm: clear default rules on purge
  + d/rsyslog.postrm: remove conf file in postrm on purge. manage with ucf
  + d/rsyslog.postinst: Adapt script to use ucf for Ubuntu's config files
  + debian/control: Add Depends for ucf
- debian/rsyslog.conf:
  + enable $RepeatedMsgReduction to avoid bloating the syslog file.
  + enable $KLogPermitNonKernelFacility for non-kernel klog messages
  + Run as syslog:syslog, set $FileOwner to syslog
  + Remove rules moved to 50-default.conf
- Add AppArmor profile, enabled by default, with support for
  AppArmor configuration snippets:
  + d/rsyslog.install: install apparmor rule
  + d/rsyslog.postinst: remove disabling of apparmor on upgrades if
we are upgrading from a version older than $now.
  + d/rules: use dh_apparmor to install profile before rsyslog is started
  + d/control: suggests apparmor (>= 2.3), Build-Depends on
dh-apparmor
  + d/rsyslog.dirs: install /etc/apparmor.d/rsyslog.d
  + d/usr.sbin.rsyslogd apparmor profile for rsyslogd
  + d/{apparmor/rsyslog-mysql,rsyslog-mysql.install}: add apparmor
profile for mysql plugin
  + d/{apparmor/rsyslog-pgsql,rsyslog-pgsql.install}: add apparmor
profile for postgresql plugin
  + d/{apparmor/rsyslog-gnutls.apparmor,rsyslog-gnutls.install}: add
apparmor profile for the gnutls plugin
  + d/{apparmor/rsyslog-openssl.apparmor,rsyslog-gnutls.install}: add
apparmor profile for the openssl plugin
  + New script to reload apparmor profile:
- d/rsyslog.service: reload apparmor profile in ExecStartPre and
  set StandardError to journal so we can see errors from the
  script
- d/rsyslog.install: install reload-apparmor-profile
- d/reload-apparmor-profile: script to reload the
  rsyslogd apparmor profile
  + d/NEWS: add info about apparmor changes in the Ubuntu packaging
  + d/rsyslog.docs, d/README.apparmor: explains how the dynamic
component of the rsyslog apparmor profile is applied
  + d/README.apparmor.rsyslog.d, d/rsyslog.install: install a specific
README file in the apparmor include directory for rsyslog
- d/rules: Fix LDFLAGS to avoid segfault on receipt of first message
- Drop [mm|pm]normalize modules, depending on liblognorm from universe.
  + d/rules: drop --enable-mmnormalize & --enable-pmnormalize
  + d/rsyslog.install: remove mmnormalize
- run as user syslog
  + d/rsyslog.postinst: fix ownership of /var/spool/rsyslog.
  + d/rsyslog.postinst: Create syslog user and add it to adm group
  + d/rsyslog.postinst: Adapt privileges for /var/log
  + debian/control: Add Depends for adduser
- d/dmesg.service, d/rsyslog.install: provide /var/log/dmesg.log as
  non log-rotated log for boot-time kernel messages.
- debian/clean: Delete some files left over by the test suite
- Add DEP8 tests (LP #1906333): + d/t/control, d/t/simple-logger:
  simple logger test
+ d/t/utils: common function(s)
+ d/t/control, d/t/simple-mysql: DEP8 test using rsyslog with a MySQL server
+ d/t/control, d/t/simple-pgsql: DEP8 test using rsyslog with a PostgreSQL 
server
+ d/t/apparmor-include-mechanism: DEP8 test for the rsyslog.d include 
mechanism used by the rsyslog apparmor profile
+ ubuntu: update debian/rsyslog.logcheck.ignore.server
+ Amend list of expected messages d/rsyslog.logcheck.ignore.server
  to fix6 armhf autopkgtest (LP #2028935)
+ ubuntu: add CAP_MAC_ADMIN, CAP_SETUID, CAP_SETGID
+ ubuntu: adjust sandboxing
+ d/p/omusrmsg-bugfix-potential-double-free-which-can-caus.patch

  * New changes
+ d/p/plugins-FromHost-must-be-63-characters-long.patch

rsyslog (8.2312.0-3) unstable; urgency=medium

  * Drop unused systemd Build-Depends.
Unfortunately, we can't run the journal related tests during build as
there typically is no journald available in the build environment. So
the systemd Build-Depends is not actually needed.

 -- Heinrich Schuchardt   Fri, 12 Jan
2024 13:27:29 +0100

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

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

Title:
  Merge rsyslog 8.2312.0-2 from Debian

Status in Rsyslog:
  

[Touch-packages] [Bug 2049369] Re: autopkg tests ignored for migration of python3-defaults adding 3.12

[Launchpad Bug Tracker]

This bug was fixed in the package python-oslo.versionedobjects -
3.2.0-3ubuntu1

---
python-oslo.versionedobjects (3.2.0-3ubuntu1) noble; urgency=low

  [ Ubuntu Merge-o-Matic ]
  * Merge from Debian unstable. Remaining changes:
- d/control: Update minimum version requirements to ensure smooth
  upgrades between and from Ubuntu Cloud Archive pockets.
- d/control: Bump debhelper-compat to 13.
- d/control: Update Vcs-Git to Ubuntu Openstack URL on LP.
- d/tests/*: Use autopkgtests from previous Ubuntu upload that cover
  basic import and unit testing (LP: #2049369).
- d/watch: Use version from previous Ubuntu upload that checks for
  release tarballs from upstream project.

python-oslo.versionedobjects (3.2.0-3) unstable; urgency=medium

  * Add remove-test_get_hashes-LP-2046220.patch.
  * Display /tmp/sphinx-err-*.log if there's a sphinx build error.
  * Add fix-sphinx-build-by-deleting-some-doc.patch.

python-oslo.versionedobjects (3.2.0-2) unstable; urgency=medium

  * Uploading to unstable.

python-oslo.versionedobjects (3.2.0-1) experimental; urgency=medium

  * New upstream release.

 -- James Page   Fri, 19 Jan 2024 09:35:30 +

** Changed in: python-oslo.versionedobjects (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  autopkg tests ignored for migration of python3-defaults adding 3.12

Status in cython package in Ubuntu:
  New
Status in cython-legacy package in Ubuntu:
  New
Status in ipykernel package in Ubuntu:
  New
Status in ironic-python-agent package in Ubuntu:
  New
Status in jupyter-client package in Ubuntu:
  New
Status in numpy package in Ubuntu:
  New
Status in python-memory-profiler package in Ubuntu:
  New
Status in python-oslo.versionedobjects package in Ubuntu:
  Fix Released
Status in python-urllib3 package in Ubuntu:
  New
Status in python3-defaults package in Ubuntu:
  New
Status in rich package in Ubuntu:
  New
Status in sphinx-autoapi package in Ubuntu:
  New
Status in vcr.py package in Ubuntu:
  New
Status in cython package in Debian:
  Confirmed
Status in cython-legacy package in Debian:
  New
Status in ipykernel package in Debian:
  New
Status in jupyter-client package in Debian:
  New
Status in numpy package in Debian:
  New
Status in python-memory-profiler package in Debian:
  New
Status in python-urllib3 package in Debian:
  Fix Released
Status in rich package in Debian:
  Confirmed
Status in sphinx-autoapi package in Debian:
  Fix Released
Status in vcr.py package in Debian:
  Fix Released

Bug description:
  autopkg tests ignored for migration of python3-defaults adding 3.12:

  These are the autopkg tests for packages, which we'll ignore for the
  initial migration of python3-defaults adding 3.12.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cython/+bug/2049369/+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 2023545] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From grgo.mari...@ibm.com 2024-01-23 05:09 EDT---
# apt-cache policy libssl3 openssl
libssl3:
Installed: 3.0.2-0ubuntu1.13
Candidate: 3.0.2-0ubuntu1.13
Version table:
*** 3.0.2-0ubuntu1.13 400
400 http://ports.ubuntu.com/ubuntu-ports jammy-proposed/main s390x Packages
100 /var/lib/dpkg/status
3.0.2-0ubuntu1.12 500
500 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main s390x Packages
500 http://ports.ubuntu.com/ubuntu-ports jammy-security/main s390x Packages
3.0.2-0ubuntu1 500
500 http://ports.ubuntu.com/ubuntu-ports jammy/main s390x Packages
openssl:
Installed: 3.0.2-0ubuntu1.13
Candidate: 3.0.2-0ubuntu1.13
Version table:
*** 3.0.2-0ubuntu1.13 400
400 http://ports.ubuntu.com/ubuntu-ports jammy-proposed/main s390x Packages
100 /var/lib/dpkg/status
3.0.2-0ubuntu1.12 500
500 http://ports.ubuntu.com/ubuntu-ports jammy-updates/main s390x Packages
500 http://ports.ubuntu.com/ubuntu-ports jammy-security/main s390x Packages
3.0.2-0ubuntu1 500
500 http://ports.ubuntu.com/ubuntu-ports jammy/main s390x Packages

Successfully verified. The problem is not visible any more. Thank you!

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

Title:
  [UBUNTU 22.04] openssl with ibmca engine configured dumps core when
  creating a new certificate

Status in Ubuntu on IBM z Systems:
  In Progress
Status in openssl package in Ubuntu:
  In Progress
Status in openssl source package in Jammy:
  Fix Committed
Status in openssl source package in Lunar:
  Fix Released

Bug description:
  === SRU information ===

  [Meta]
  This bug is part of a series of three bugs for a single SRU.
  The "central" bug with the global information and debdiff is 
http://pad.lv/2033422

  [Impact]
  Openssl using an engine dumps core upon certificate creation; other 
operations are probably affected too. Overall, engines are likely mostly 
unusable.

  [Test plan]
  - An openssl engine is req. to test the fix.
  - A z13 / LinuxONE LPAR or z/VM guest is needed, with attached APQN.
  - Check with 'lszcrypt -V' the availability (online) of the hw crypto 
resources.
  - Install the needed package that allows to exploit the hw crypto resources:
    sudo apt-get install libica-utils libica? openssl-ibmca
  - And copy a working sample openssf.cnf file:
    sudo cp /usr/share/doc/openssl-ibmca/examples/openssl.cnf.sample 
/etc/ssl/openssl.cnf
  - Verify if the 'openssl engine' lists an ibmca engine,
in addition to the dynamic engine:
openssl engine
      (dynamic) Dynamic engine loading support
      (ibmca) Ibmca hardware engine support  <===
  - try to create a new certificate, using this cmd-line:
    openssl req -new -newkey rsa:2048 -x509 -sha256 -nodes -out __cert.pem 
-keyout __key.pem --subj '/CN=US'
  - The above command must not lead to a 'Segmentation fault (core dumped)',
    rather than create a proper certificate file.
    Also watch /var/log/syslog / journalctl for more details.
  - Upgrade not only the openssl package itself,
but also libssl3, before verification.
  - The issue is fixed in openssl 3.0.8 which landed in lunar.

  [Where problems could occur]
  I don't pretend to understand the lifecycle of providers in openssl3 but the 
patch is simple and has been widely tested by now, including on ubuntu. Thus, I 
see little chance an unexpected problem would occur with it.

  [Patches]
  The patches come directly from upstream and apply cleanly.

  https://github.com/openssl/openssl/issues/18578

  *
  
https://git.launchpad.net/~adrien-n/ubuntu/+source/openssl/tree/debian/patches/jammy-
  sru-0001-Release-the-drbg-in-the-global-default-context-
  befor.patch?h=jammy-sru=04ef023920ab08fba214817523fba897527dfff0

  === Original description ===

  openssl req -new -newkey rsa:2048 -x509 -sha256 -nodes -out __cert.pem
  -keyout __key.pem --subj '/CN=US'

  ---Problem Description---
  OpenSSL with ibmca engine configured dumps core when creating a new 
certificate.

  # openssl engine
  (dynamic) Dynamic engine loading support
  (ibmca) Ibmca hardware engine support
  # openssl req  -new -newkey rsa:2048 -x509 -sha256 -nodes -out __cert.pem 
-keyout __key.pem --subj '/CN=US'
  Segmentation fault (core dumped)

  # journalctl
  Jun 07 13:06:08 SYSTEM kernel: User process fault: interruption code 003b 
ilc:2 in libc.so.6[3ffae08+1ca000]
  Jun 07 13:06:08 SYSTEM kernel: Failing address:  TEID: 
0800
  Jun 07 13:06:08 SYSTEM kernel: Fault in primary space mode while using user 
ASCE.
  Jun 07 13:06:08 SYSTEM kernel: AS:9c2941c7 R3:0024
  Jun 07 13:06:08 SYSTEM kernel: CPU: 2 PID: 2344 Comm: openssl Kdump: loaded 
Not tainted 5.15.0-73-generic #80-Ubuntu
  Jun 07 13:06:08 SYSTEM kernel: Hardware name: IBM 3931 A01 703 (z/VM 7.3.0)
  Jun 07 13:06:08 SYSTEM kernel: User PSW : 070500018000 03ffae11c708
  Jun 07 13:06:08 SYSTEM 

[Touch-packages] [Bug 1930914] Re: ubuntu-minimal depends on ubuntu-advantage-tools

[Michel-Ekimia]

Hi,

Very interesting bug on how Canonical destroy the Ubuntu community just
"because the don't care"

I guess we should stop wasting our customers and time to fix ubuntu pro
and move to something else.

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

Title:
  ubuntu-minimal depends on ubuntu-advantage-tools

Status in ubuntu-meta package in Ubuntu:
  Won't Fix

Bug description:
  This is counter to #1566183 There is no reason to enforce desktop
  users who manage machine on their own to install ubuntu-advantage-
  tools, especially when this is 'minimal' version.  This should include
  only essential packages to make the OS functional

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: ubuntu-minimal 1.450.2
  ProcVersionSignature: Ubuntu 5.4.0-73.82-lowlatency 5.4.106
  Uname: Linux 5.4.0-73-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.18
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Jun  4 18:54:56 2021
  InstallationDate: Installed on 2020-01-29 (491 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: ubuntu-meta
  UpgradeStatus: Upgraded to focal on 2020-06-27 (342 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1930914/+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 1949089] Re: systemd randomly fails to activate mount units in Ubuntu Core 18

[Lukas Märdian]

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

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

Title:
  systemd randomly fails to activate mount units in Ubuntu Core 18

Status in systemd package in Ubuntu:
  New
Status in systemd source package in Bionic:
  New

Bug description:
  Since a month or so, we've been seeing random failures in our snapd
  spread tests where systemd could not start the mount unit associated
  with a snap because of a failed dependency.

  The issue is described in the comments to PR
  https://github.com/snapcore/snapd/pull/10935, but I'll summarize it
  here.

  When starting a snap, snapd creates a mount unit to mount the snap's
  squashfs (the template is
  
https://github.com/snapcore/snapd/blob/release/2.53/systemd/systemd.go#L1186-L1205).
  The snapd asks systemd to reload the configuration, and starts the
  mount unit.

  The failure we've observed is that sometimes systemd decides to stop
  our mount unit (search for "Unmounting Mount unit for test-snapd-svc-
  flip-flop" in the attached log), and then tries to reactivate it
  again, and at that point it fails.

  When I asked for help, Lukas pointed out that the latest update
  contains a patch that is related to reload handling and mount units:
  
http://launchpadlibrarian.net/555420796/systemd_237-3ubuntu10.51_237-3ubuntu10.52.diff.gz
  (the patch itself is better visible at
  
https://github.com/systemd/systemd/commit/f0831ed2a03fcef582660be1c3b1a9f3e267e656).
  When looking at the systemd git log, though, I noticed another patch
  that was applied shortly after this one, which also seems related but
  was not backported:
  
https://github.com/systemd/systemd/commit/04eb582acc203eab0bc5c2cc5e13986f16e09df0

  Since the stopping of our mount unit happens immediately after a
  systemd reload, it actually seems very likely that the inclusion of
  f0831ed2a03fcef582660be1c3b1a9f3e267e656 in the systemd update is what
  causes our woes (though, indeed, the issue is not reliably
  reproducible, so we cannot be sure).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1949089/+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 2023545] Re: [UBUNTU 22.04] openssl with ibmca engine configured dumps core when creating a new certificate

[Frank Heimes]

Hi Grgo, did you also updated libssl3?
see test plan in Description:
"
- Upgrade not only the openssl package itself,
  but also libssl3, before verification.
"
With that I could successfully verify.

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

Title:
  [UBUNTU 22.04] openssl with ibmca engine configured dumps core when
  creating a new certificate

Status in Ubuntu on IBM z Systems:
  In Progress
Status in openssl package in Ubuntu:
  In Progress
Status in openssl source package in Jammy:
  Fix Committed
Status in openssl source package in Lunar:
  Fix Released

Bug description:
  === SRU information ===

  [Meta]
  This bug is part of a series of three bugs for a single SRU.
  The "central" bug with the global information and debdiff is 
http://pad.lv/2033422

  [Impact]
  Openssl using an engine dumps core upon certificate creation; other 
operations are probably affected too. Overall, engines are likely mostly 
unusable.

  [Test plan]
  - An openssl engine is req. to test the fix.
  - A z13 / LinuxONE LPAR or z/VM guest is needed, with attached APQN.
  - Check with 'lszcrypt -V' the availability (online) of the hw crypto 
resources.
  - Install the needed package that allows to exploit the hw crypto resources:
    sudo apt-get install libica-utils libica? openssl-ibmca
  - And copy a working sample openssf.cnf file:
    sudo cp /usr/share/doc/openssl-ibmca/examples/openssl.cnf.sample 
/etc/ssl/openssl.cnf
  - Verify if the 'openssl engine' lists an ibmca engine,
in addition to the dynamic engine:
openssl engine
      (dynamic) Dynamic engine loading support
      (ibmca) Ibmca hardware engine support  <===
  - try to create a new certificate, using this cmd-line:
    openssl req -new -newkey rsa:2048 -x509 -sha256 -nodes -out __cert.pem 
-keyout __key.pem --subj '/CN=US'
  - The above command must not lead to a 'Segmentation fault (core dumped)',
    rather than create a proper certificate file.
    Also watch /var/log/syslog / journalctl for more details.
  - Upgrade not only the openssl package itself,
but also libssl3, before verification.
  - The issue is fixed in openssl 3.0.8 which landed in lunar.

  [Where problems could occur]
  I don't pretend to understand the lifecycle of providers in openssl3 but the 
patch is simple and has been widely tested by now, including on ubuntu. Thus, I 
see little chance an unexpected problem would occur with it.

  [Patches]
  The patches come directly from upstream and apply cleanly.

  https://github.com/openssl/openssl/issues/18578

  *
  
https://git.launchpad.net/~adrien-n/ubuntu/+source/openssl/tree/debian/patches/jammy-
  sru-0001-Release-the-drbg-in-the-global-default-context-
  befor.patch?h=jammy-sru=04ef023920ab08fba214817523fba897527dfff0

  === Original description ===

  openssl req -new -newkey rsa:2048 -x509 -sha256 -nodes -out __cert.pem
  -keyout __key.pem --subj '/CN=US'

  ---Problem Description---
  OpenSSL with ibmca engine configured dumps core when creating a new 
certificate.

  # openssl engine
  (dynamic) Dynamic engine loading support
  (ibmca) Ibmca hardware engine support
  # openssl req  -new -newkey rsa:2048 -x509 -sha256 -nodes -out __cert.pem 
-keyout __key.pem --subj '/CN=US'
  Segmentation fault (core dumped)

  # journalctl
  Jun 07 13:06:08 SYSTEM kernel: User process fault: interruption code 003b 
ilc:2 in libc.so.6[3ffae08+1ca000]
  Jun 07 13:06:08 SYSTEM kernel: Failing address:  TEID: 
0800
  Jun 07 13:06:08 SYSTEM kernel: Fault in primary space mode while using user 
ASCE.
  Jun 07 13:06:08 SYSTEM kernel: AS:9c2941c7 R3:0024
  Jun 07 13:06:08 SYSTEM kernel: CPU: 2 PID: 2344 Comm: openssl Kdump: loaded 
Not tainted 5.15.0-73-generic #80-Ubuntu
  Jun 07 13:06:08 SYSTEM kernel: Hardware name: IBM 3931 A01 703 (z/VM 7.3.0)
  Jun 07 13:06:08 SYSTEM kernel: User PSW : 070500018000 03ffae11c708
  Jun 07 13:06:08 SYSTEM kernel:R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 
AS:0 CC:0 PM:0 RI:0 EA:3
  Jun 07 13:06:08 SYSTEM kernel: User GPRS: 0007 03ffae11c6f0 
 02aa3289f9d0
  Jun 07 13:06:08 SYSTEM kernel:02aa1825980f 02aa3289f9d0 
 02aa328a4300
  Jun 07 13:06:08 SYSTEM kernel:03ffae870720 03ffae657128 
02aa03ff 
  Jun 07 13:06:08 SYSTEM kernel:03ffae24dd10 03ffae657120 
03ffae437c22 03ffec2fe000
  Jun 07 13:06:08 SYSTEM kernel: User Code: 03ffae11c6fc: b90400b2  
  lgr%r11,%r2
    03ffae11c700: 
4700bc0,0
   #03ffae11c704: 
b24f00a0ear%r10,%a0
   

[Touch-packages] [Bug 2050874] [NEW] "Illegal characters in username" breaks sftp upload

[Jakob Lund]

Public bug reported:

A new error message appeared in 1:8.2p1-4ubuntu0.11, "remote username
contains invalid characters".

The underlying commit seems to be this:
https://github.com/openbsd/src/commit/ba05a7aae989020b8d05cc93cc6200109bba5a7b


I need to work with an sftp connection where the username includes "|". The 
lftp client uses ssh to connect, triggering the error.

It's possible to whitelist the username by adding it to a config file
(e.g. ~/.ssh/config), but in that case, there's no obvious way to set
the password.


I suppose this is in fact a feature more than it is a bug, but it is really 
inconvenient. Any hints on how to handle it would be welcome.


Regards,
Jakob Lund


Ubuntu 20.04.3 LTS

openssh-client:
  Installed: 1:8.2p1-4ubuntu0.11

lftp:
  Installed: 4.8.4-2build3

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

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

Title:
  "Illegal characters in username" breaks sftp upload

Status in openssh package in Ubuntu:
  New

Bug description:
  A new error message appeared in 1:8.2p1-4ubuntu0.11, "remote username
  contains invalid characters".

  The underlying commit seems to be this:
  https://github.com/openbsd/src/commit/ba05a7aae989020b8d05cc93cc6200109bba5a7b

  
  I need to work with an sftp connection where the username includes "|". The 
lftp client uses ssh to connect, triggering the error.

  It's possible to whitelist the username by adding it to a config file
  (e.g. ~/.ssh/config), but in that case, there's no obvious way to set
  the password.

  
  I suppose this is in fact a feature more than it is a bug, but it is really 
inconvenient. Any hints on how to handle it would be welcome.


  Regards,
  Jakob Lund


  Ubuntu 20.04.3 LTS

  openssh-client:
Installed: 1:8.2p1-4ubuntu0.11

  lftp:
Installed: 4.8.4-2build3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2050874/+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 2023545] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From grgo.mari...@ibm.com 2024-01-23 03:53 EDT---
After upgrading to Ubuntu 22.04.3 the solution is working and the problem is 
not visible anymore.

Explicit update of the fix is not valid on the older version (22.04.1).

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

Title:
  [UBUNTU 22.04] openssl with ibmca engine configured dumps core when
  creating a new certificate

Status in Ubuntu on IBM z Systems:
  In Progress
Status in openssl package in Ubuntu:
  In Progress
Status in openssl source package in Jammy:
  Fix Committed
Status in openssl source package in Lunar:
  Fix Released

Bug description:
  === SRU information ===

  [Meta]
  This bug is part of a series of three bugs for a single SRU.
  The "central" bug with the global information and debdiff is 
http://pad.lv/2033422

  [Impact]
  Openssl using an engine dumps core upon certificate creation; other 
operations are probably affected too. Overall, engines are likely mostly 
unusable.

  [Test plan]
  - An openssl engine is req. to test the fix.
  - A z13 / LinuxONE LPAR or z/VM guest is needed, with attached APQN.
  - Check with 'lszcrypt -V' the availability (online) of the hw crypto 
resources.
  - Install the needed package that allows to exploit the hw crypto resources:
    sudo apt-get install libica-utils libica? openssl-ibmca
  - And copy a working sample openssf.cnf file:
    sudo cp /usr/share/doc/openssl-ibmca/examples/openssl.cnf.sample 
/etc/ssl/openssl.cnf
  - Verify if the 'openssl engine' lists an ibmca engine,
in addition to the dynamic engine:
openssl engine
      (dynamic) Dynamic engine loading support
      (ibmca) Ibmca hardware engine support  <===
  - try to create a new certificate, using this cmd-line:
    openssl req -new -newkey rsa:2048 -x509 -sha256 -nodes -out __cert.pem 
-keyout __key.pem --subj '/CN=US'
  - The above command must not lead to a 'Segmentation fault (core dumped)',
    rather than create a proper certificate file.
    Also watch /var/log/syslog / journalctl for more details.
  - Upgrade not only the openssl package itself,
but also libssl3, before verification.
  - The issue is fixed in openssl 3.0.8 which landed in lunar.

  [Where problems could occur]
  I don't pretend to understand the lifecycle of providers in openssl3 but the 
patch is simple and has been widely tested by now, including on ubuntu. Thus, I 
see little chance an unexpected problem would occur with it.

  [Patches]
  The patches come directly from upstream and apply cleanly.

  https://github.com/openssl/openssl/issues/18578

  *
  
https://git.launchpad.net/~adrien-n/ubuntu/+source/openssl/tree/debian/patches/jammy-
  sru-0001-Release-the-drbg-in-the-global-default-context-
  befor.patch?h=jammy-sru=04ef023920ab08fba214817523fba897527dfff0

  === Original description ===

  openssl req -new -newkey rsa:2048 -x509 -sha256 -nodes -out __cert.pem
  -keyout __key.pem --subj '/CN=US'

  ---Problem Description---
  OpenSSL with ibmca engine configured dumps core when creating a new 
certificate.

  # openssl engine
  (dynamic) Dynamic engine loading support
  (ibmca) Ibmca hardware engine support
  # openssl req  -new -newkey rsa:2048 -x509 -sha256 -nodes -out __cert.pem 
-keyout __key.pem --subj '/CN=US'
  Segmentation fault (core dumped)

  # journalctl
  Jun 07 13:06:08 SYSTEM kernel: User process fault: interruption code 003b 
ilc:2 in libc.so.6[3ffae08+1ca000]
  Jun 07 13:06:08 SYSTEM kernel: Failing address:  TEID: 
0800
  Jun 07 13:06:08 SYSTEM kernel: Fault in primary space mode while using user 
ASCE.
  Jun 07 13:06:08 SYSTEM kernel: AS:9c2941c7 R3:0024
  Jun 07 13:06:08 SYSTEM kernel: CPU: 2 PID: 2344 Comm: openssl Kdump: loaded 
Not tainted 5.15.0-73-generic #80-Ubuntu
  Jun 07 13:06:08 SYSTEM kernel: Hardware name: IBM 3931 A01 703 (z/VM 7.3.0)
  Jun 07 13:06:08 SYSTEM kernel: User PSW : 070500018000 03ffae11c708
  Jun 07 13:06:08 SYSTEM kernel:R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 
AS:0 CC:0 PM:0 RI:0 EA:3
  Jun 07 13:06:08 SYSTEM kernel: User GPRS: 0007 03ffae11c6f0 
 02aa3289f9d0
  Jun 07 13:06:08 SYSTEM kernel:02aa1825980f 02aa3289f9d0 
 02aa328a4300
  Jun 07 13:06:08 SYSTEM kernel:03ffae870720 03ffae657128 
02aa03ff 
  Jun 07 13:06:08 SYSTEM kernel:03ffae24dd10 03ffae657120 
03ffae437c22 03ffec2fe000
  Jun 07 13:06:08 SYSTEM kernel: User Code: 03ffae11c6fc: b90400b2  
  lgr%r11,%r2
    03ffae11c700: 
4700bc0,0
   #03ffae11c704: 
b24f00a0ear%r10,%a0
     

[Touch-packages] [Bug 2023545] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From grgo.mari...@ibm.com 2024-01-23 03:44 EDT---
The problem is still visible after installing the -proposed package:

root:~# dpkg -l | grep openssl
ii  openssl   3.0.2-0ubuntu1.13 
  s390xSecure Sockets Layer toolkit - cryptographic utility
ii  openssl-ibmca 2.2.3-0ubuntu1.1  
  s390xlibica based hardware acceleration engine for OpenSSL
ii  python3-openssl   21.0.0-1  
  all  Python 3 wrapper around the OpenSSL library
root:~# openssl engine
(dynamic) Dynamic engine loading support
(ibmca) Ibmca hardware engine support

By running with gdb the following BT can be observed:
(gdb) r
Starting program: /usr/bin/openssl req -new -newkey rsa:2048 -x509 -sha256 
-nodes -out __cert.pem -keyout __key.pem --subj /CN=US
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/s390x-linux-gnu/libthread_db.so.1".
.+*..+.+.+..++...+...+.+*.+.+.+.+..+...+.+..+.+...+.+.+.+..+..+...++.+...+..+...+...+..+.+...+
...+.+++*...+.+.+..+*++...+
-

Program received signal SIGSEGV, Segmentation fault.
0x03fffd89c738 in __pthread_rwlock_wrlock_full64 (abstime=0x0, clockid=0, 
rwlock=0x0) at pthread_rwlock_common.c:603
603 pthread_rwlock_common.c: No such file or directory.
(gdb) bt
#0  0x03fffd89c738 in __pthread_rwlock_wrlock_full64 (abstime=0x0, 
clockid=0, rwlock=0x0) at pthread_rwlock_common.c:603
#1  ___pthread_rwlock_wrlock (rwlock=0x0) at pthread_rwlock_wrlock.c:26
#2  0x03fffdbb7812 in CRYPTO_THREAD_write_lock () from 
/lib/s390x-linux-gnu/libcrypto.so.3
#3  0x03fffdb634f2 in ENGINE_finish () from 
/lib/s390x-linux-gnu/libcrypto.so.3
#4  0x03fffdb86314 in EVP_CIPHER_CTX_reset () from 
/lib/s390x-linux-gnu/libcrypto.so.3
#5  0x03fffdb8635c in EVP_CIPHER_CTX_free () from 
/lib/s390x-linux-gnu/libcrypto.so.3
#6  0x03fffdc791ac in ?? () from /lib/s390x-linux-gnu/libcrypto.so.3
#7  0x03fffdb8ca88 in EVP_RAND_CTX_free () from 
/lib/s390x-linux-gnu/libcrypto.so.3
#8  0x03fffdbe4bc2 in ?? () from /lib/s390x-linux-gnu/libcrypto.so.3
#9  0x03fffdbb0c6c in CRYPTO_free_ex_data () from 
/lib/s390x-linux-gnu/libcrypto.so.3
#10 0x03fffdba8dfa in ?? () from /lib/s390x-linux-gnu/libcrypto.so.3
#11 0x03fffdbb36b8 in OPENSSL_cleanup () from 
/lib/s390x-linux-gnu/libcrypto.so.3
#12 0x03fffd84b6ec in __run_exit_handlers (status=, 
listp=0x3fffd9ce618 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true,
run_dtors=run_dtors@entry=true) at exit.c:113
#13 0x03fffd84b7b0 in __GI_exit (status=) at exit.c:143
#14 0x02aa00047c06 in main ()

syslog shows the following:

Jan 22 15:14:03 a8314006.lnxne.boe kernel:  [<03ff89d3242c>] 0x3ff89d3242c
Jan 22 15:14:03 a8314006.lnxne.boe kernel: Last Breaking-Event-Address:
Jan 22 15:14:03 a8314006.lnxne.boe kernel: User Code: 03ff89b1c72c: 
b90400b2lgr%r11,%r2
03ff89b1c730: 4700bc0,0
#03ff89b1c734: b24f00a0ear%r10,%a0
>03ff89b1c738: 58102018l%r1,24(%r2)
03ff89b1c73c: ebaa002dsllg%r10,%r10,32
03ff89b1c742: b24f00a1ear%r10,%a1
03ff89b1c746: 5910a0d0c%r1,208(%r10)
03ff89b1c74a: a7840033brc8,03ff89b1c7b0
Jan 22 15:14:03 SYSTEM kernel:03ff89c4dd10 03ff8a057120 
03ff89e37812 03ffc93fe170
Jan 22 15:14:03 SYSTEM kernel:03ff8a270720 03ff8a057128 
02aa03ff 
Jan 22 15:14:03 SYSTEM kernel:02aa272ac835 02aa0d8d5a40 
 02aa0d8da370
Jan 22 15:14:03 SYSTEM kernel: User GPRS: 0007 03ff89b1c720 
 02aa0d8d5a40
Jan 22 15:14:03 SYSTEM kernel:R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 
AS:0 CC:0 PM:0 RI:0 EA:3
Jan 22 15:14:03 SYSTEM kernel: User PSW : 070500018000 03ff89b1c738
Jan 22 15:14:03 SYSTEM kernel: Hardware name: IBM 3931 A01 703 (z/VM 7.3.0)
Jan 22 15:14:03 SYSTEM kernel: CPU: 0 PID: 98944 Comm: openssl Not tainted 
5.15.0-91-generic #101-Ubuntu
Jan 22 15:14:03 SYSTEM kernel: AS:9b00c1c7 R3:0024
Jan 22 15:14:03 SYSTEM kernel: Fault in primary space mode while 

[Touch-packages] [Bug 2037907] Re: No package 'nss' found

[Robert]

I tested version 23.12.0: same problem.
Thanks in advance for analyzing the problem.

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

Title:
  No package 'nss' found

Status in poppler package in Ubuntu:
  Invalid

Bug description:
  Have installed poppler on several systems, but experience issues in
  some cases.

  All the dependencies should be installed!

  Distro: Debian Bullseye 11

  
  # apt-get install libopenjp2-7-dev libfreetype6-dev libfontconfig1-dev 
libjpeg-dev libtiff5-dev
  # cd /var/bin && wget https://poppler.freedesktop.org/poppler-23.09.0.tar.xz 
&& tar -xvf poppler-23.09.0.tar.xz
  # cd poppler-23.09.0 && mkdir build && cd build
  # cmake ..

  
  CMake Warning at CMakeLists.txt:95 (message):

  
 No test data found in $testdatadir.
 You will not be able to run 'make test' successfully.


 The test data is not included in the source packages
 and is also not part of the main git repository. Instead,
 you can checkout the test data from its own git
 repository with:


   git clone git://git.freedesktop.org/git/poppler/test


 You should checkout the test data as a sibling of your
 poppler source folder or specify the location of your
 checkout with -DTESTDATADIR=/path/to/checkoutdir/test.


  -- Checking for module 'nss>=3.49'
  --   No package 'nss' found
  -- Could NOT find NSS3 (missing: NSS3_LIBRARIES NSS3_CFLAGS)
  CMake Warning at cmake/modules/MacroOptionalFindPackage.cmake:32 
(find_package):
By not providing "FindGpgmepp.cmake" in CMAKE_MODULE_PATH this project has
asked CMake to find a package configuration file provided by "Gpgmepp", but
CMake did not find one.

Could not find a package configuration file provided by "Gpgmepp"
(requested version 1.19) with any of the following names:

  GpgmeppConfig.cmake
  gpgmepp-config.cmake

Add the installation prefix of "Gpgmepp" to CMAKE_PREFIX_PATH or set
"Gpgmepp_DIR" to a directory containing one of the above files.  If
"Gpgmepp" provides a separate development package or SDK, be sure it has
been installed.
  Call Stack (most recent call first):
CMakeLists.txt:158 (macro_optional_find_package)

  
  CMake Warning at CMakeLists.txt:198 (find_package):
By not providing "FindQt5Core.cmake" in CMAKE_MODULE_PATH this project has
asked CMake to find a package configuration file provided by "Qt5Core", but
CMake did not find one.

Could not find a package configuration file provided by "Qt5Core"
(requested version 5.12) with any of the following names:

  Qt5CoreConfig.cmake
  qt5core-config.cmake

Add the installation prefix of "Qt5Core" to CMAKE_PREFIX_PATH or set
"Qt5Core_DIR" to a directory containing one of the above files.  If
"Qt5Core" provides a separate development package or SDK, be sure it has
been installed.

  
  CMake Warning at CMakeLists.txt:199 (find_package):
By not providing "FindQt5Gui.cmake" in CMAKE_MODULE_PATH this project has
asked CMake to find a package configuration file provided by "Qt5Gui", but
CMake did not find one.

Could not find a package configuration file provided by "Qt5Gui" with any
of the following names:

  Qt5GuiConfig.cmake
  qt5gui-config.cmake

Add the installation prefix of "Qt5Gui" to CMAKE_PREFIX_PATH or set
"Qt5Gui_DIR" to a directory containing one of the above files.  If "Qt5Gui"
provides a separate development package or SDK, be sure it has been
installed.

  
  CMake Warning at CMakeLists.txt:200 (find_package):
By not providing "FindQt5Xml.cmake" in CMAKE_MODULE_PATH this project has
asked CMake to find a package configuration file provided by "Qt5Xml", but
CMake did not find one.

Could not find a package configuration file provided by "Qt5Xml" with any
of the following names:

  Qt5XmlConfig.cmake
  qt5xml-config.cmake

Add the installation prefix of "Qt5Xml" to CMAKE_PREFIX_PATH or set
"Qt5Xml_DIR" to a directory containing one of the above files.  If "Qt5Xml"
provides a separate development package or SDK, be sure it has been
installed.

  
  CMake Warning at CMakeLists.txt:201 (find_package):
By not providing "FindQt5Widgets.cmake" in CMAKE_MODULE_PATH this project
has asked CMake to find a package configuration file provided by
"Qt5Widgets", but CMake did not find one.

Could not find a package configuration file provided by "Qt5Widgets" with
any of the following names:

  Qt5WidgetsConfig.cmake
  qt5widgets-config.cmake

Add the installation prefix of "Qt5Widgets" to CMAKE_PREFIX_PATH or set
"Qt5Widgets_DIR" to a directory containing one of the above files.  If
"Qt5Widgets" provides a separate development package or SDK, be sure it has
been installed.

  
  CMake Warning at 

[Touch-packages] [Bug 2036333]

[jeffclay]

(In reply to dabiswas112 from comment #6)
> Hi, I've fixed this on my copr at hazel-bunny/ports. I have also ported the
> signon-ui spec from webkit to webengine, because qt5-qtwebkit is a big
> security hole according to a GNOME guy.
> 
> @rdieter could you check if the updates in
> https://github.com/hazel-bunny/rpm-packaging/tree/master/lib/signon are
> acceptable?

Thoughts on becoming maintainer or co-maintainer of this package
@dabiswas112?

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

Title:
  signon-ui no longer works for Google authentication

Status in kio-gdrive package in Ubuntu:
  Confirmed
Status in signon-ui package in Ubuntu:
  Confirmed
Status in signon-ui package in Fedora:
  Confirmed

Bug description:
  The version of signon-ui from Launchpad no longer works for adding
  Google services in Kubuntu. The login hangs indefinitely after
  entering an email address.

  Apparently, a slightly newer version from its current home on git
  reportedly works, and is what others have been using:

  https://gitlab.com/accounts-sso/signon-ui

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kio-gdrive/+bug/2036333/+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 2047457] Re: GLib-GIO-CRITICAL **: GFileInfo created without standard::symlink-target sort-order

[Yangfl]

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

Title:
  GLib-GIO-CRITICAL **: GFileInfo created without standard::symlink-
  target sort-order

Status in glib-networking package in Ubuntu:
  New

Bug description:
  Just noticed ```.xsession-errors``` somewhat big with a timestamp from
  today.

  After checking the log out I mostly see:

  ```
  (caja:2681): GLib-GIO-CRITICAL **: 17:16:08.920: GFileInfo created without 
standard::sort-order

  (caja:2681): GLib-GIO-CRITICAL **: 17:16:08.920: file
  ../../../gio/gfileinfo.c: line 2108 (g_file_info_get_sort_order):
  should not be reached

  (caja:2681): GLib-GIO-CRITICAL **: 17:16:08.920: GFileInfo created
  without standard::symlink-target

  (caja:2681): GLib-GIO-CRITICAL **: 17:16:08.920: file
  ../../../gio/gfileinfo.c: line 2062 (g_file_info_get_symlink_target):
  should not be reached

  (caja:2681): GLib-GIO-CRITICAL **: 17:16:11.722: GFileInfo created
  without standard::sort-order

  (caja:2681): GLib-GIO-CRITICAL **: 17:16:11.723: file
  ../../../gio/gfileinfo.c: line 2108 (g_file_info_get_sort_order):
  should not be reached

  (caja:2681): GLib-GIO-CRITICAL **: 17:16:11.723: GFileInfo created
  without standard::symlink-target

  (caja:2681): GLib-GIO-CRITICAL **: 17:16:11.723: file
  ../../../gio/gfileinfo.c: line 2062 (g_file_info_get_symlink_target):
  should not be reached

  (caja:2681): GLib-GIO-CRITICAL **: 17:16:14.527: GFileInfo created
  without standard::sort-order

  (caja:2681): GLib-GIO-CRITICAL **: 17:16:14.527: file
  ../../../gio/gfileinfo.c: line 2108 (g_file_info_get_sort_order):
  should not be reached

  (caja:2681): GLib-GIO-CRITICAL **: 17:16:14.527: GFileInfo created
  without standard::symlink-target

  (caja:2681): GLib-GIO-CRITICAL **: 17:16:14.527: file 
../../../gio/gfileinfo.c: line 2062 (g_file_info_get_symlink_target): should 
not be reached
  ```

  Going through that log it is not always "caja" showing up.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: glib-networking 2.78.0-1
  ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: MATE
  Date: Tue Dec 26 17:16:53 2023
  InstallationDate: Installed on 2023-04-14 (256 days ago)
  InstallationMedia: Ubuntu-MATE 22.10 "Kinetic Kudu" - Release amd64 (20221018)
  SourcePackage: glib-networking
  UpgradeStatus: Upgraded to mantic on 2023-10-13 (74 days ago)

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