[Touch-packages] [Bug 1942694] Re: [21.04] Uncooperative WiFi manager on TTY7 for proper end user integration

[Norbert]

** Also affects: network-manager-applet (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: network-manager-applet (Ubuntu)

** Also affects: network-manager (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  [21.04] Uncooperative WiFi manager on TTY7 for proper end user
  integration

Status in Ubuntu MATE:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  Desc.:
  Using 21.04-latest on a Dell XPS 13" laptop and working on TTY7, the wifi 
manager becomes uncooperative after, it seems, it gets tied up to 2 wifi 
profiles.

  Recreation steps:
  1. Install 21.04-latest + full patch it using your home LAN WiFi AP;
  2. Login newly installed system + test Internet = it works fine;
  3. Take same laptop and go to a hotel(for example): manually create a new 
profile for the new WiFi network from TTY7, login "hotel" wifi network profile 
+ test Internet = it works fine;
  4. Physically move back to where your "home" LAN WiFi profile is and boot 
system:

  Problem now happens::
  1. Internet doesn't work off WiFi;
  2. Click on the "Wi-Fi Network" icon at the top hand right side of the screen 
-> "no network devices available";
  3. Select "Edit connections" -> there will be your 2 profiles there: "home" 
and "hotel", delete "hotel" -> OK;
  4. "no network devices available" still shows under "Wi-Fi Network" at the 
top.
  MY USER EXPECTATIONS: Get a new list of close by AP and/or automatically 
reconnect to "profile 1: home".
  NOTA: Both profiles are set to priority 0 and also all set to "all uses may 
connect to this network". Could this be the problem?

  Solution:
  Reboot system.
  After reboot. TTY7 will have defaulted back to the "home" WiFi profile and 
Internet will work at the first user attempt.

  xo

  PS: I have been having this problem from way before hirsute.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1942694/+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 1941962] Re: pulseaudio crashed with SIGSEGV in XFreeGC() from XCloseDisplay() from pa_x11_wrapper_unref()

[Igor V. Kovalenko]

I believe this crash is caused by this libx11 issue
https://gitlab.freedesktop.org/xorg/lib/libx11/-/issues/139


** Bug watch added: gitlab.freedesktop.org/xorg/lib/libx11/-/issues #139
   https://gitlab.freedesktop.org/xorg/lib/libx11/-/issues/139

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

Title:
  pulseaudio crashed with SIGSEGV in XFreeGC() from XCloseDisplay() from
  pa_x11_wrapper_unref()

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/52094416ad4b4132ebf639ec8530fed1fdbac584

  crash

  ProblemType: Crash
  DistroRelease: Ubuntu 21.10
  Package: pulseaudio 1:15.0+dfsg1-1ubuntu2
  Uname: Linux 5.13.13-xanmod1-cacule x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu68
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  anasc  1719 F pulseaudio
   /dev/snd/pcmC0D0p:   anasc  1719 F...m pulseaudio
  CasperMD5CheckResult: pass
  Date: Sat Aug 28 21:00:59 2021
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2021-08-26 (2 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210824)
  ProcCmdline: /usr/bin/pulseaudio --daemonize=no --log-target=journal
  SegvAnalysis:
   Segfault happened at: 0x7fbcc9d6a8a4 :  mov%edx,0x4(%rax)
   PC (0x7fbcc9d6a8a4) ok
   source "%edx" ok
   destination "0x4(%rax)" (0x0004) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: pulseaudio
  StacktraceTop:
   XFreeGC () from /lib/x86_64-linux-gnu/libX11.so.6
   XCloseDisplay () from /lib/x86_64-linux-gnu/libX11.so.6
   pa_x11_wrapper_unref () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-15.0.so
   module_x11_publish_LTX_pa__done () from 
/usr/lib/pulse-15.0+dfsg1/modules/module-x11-publish.so
   ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-15.0.so
  Title: pulseaudio crashed with SIGSEGV in XFreeGC()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  dmi.bios.date: 02/05/2021
  dmi.bios.release: 15.14
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.14
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 86E2
  dmi.board.vendor: HP
  dmi.board.version: 95.36
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 95.36
  dmi.modalias: 
dmi:bvnInsyde:bvrF.14:bd02/05/2021:br15.14:efr95.36:svnHP:pnHPPavilionLaptop15-cs3xxx:pvrType1ProductConfigId:sku5SU52EA#BH4:rvnHP:rn86E2:rvr95.36:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Laptop 15-cs3xxx
  dmi.product.sku: 5SU52EA#BH4
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1941962/+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 1921781] Re: Build-depends on qt5-default which is obsolete and dropped in hirsute

[Launchpad Bug Tracker]

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

** Changed in: indicator-sound (Ubuntu)
   Status: New => Confirmed

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

Title:
  Build-depends on qt5-default which is obsolete and dropped in hirsute

Status in indicator-sound package in Ubuntu:
  Confirmed
Status in libqofono package in Ubuntu:
  Fix Released
Status in poppler-qml-plugin package in Ubuntu:
  Fix Released
Status in qtpowerd package in Ubuntu:
  Fix Released
Status in qtubuntu-cameraplugin-fake package in Ubuntu:
  Fix Released
Status in signon-keyring-extension package in Ubuntu:
  Fix Released
Status in signon-plugin-sasl package in Ubuntu:
  Fix Released
Status in signon-ui package in Ubuntu:
  Fix Released
Status in unity-api package in Ubuntu:
  Fix Released
Status in unity-control-center package in Ubuntu:
  Confirmed

Bug description:
  These packages build-depend on the qt5-default package, which has been
  dropped upstream in Debian and will not be available in the hirsute
  release.

  These packages should either be updated to not require this build-
  dependency, or be removed from hirsute.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1921781/+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 1918044] Re: (Update libgweather to 3.36.2) Weather forecast and info is not available anymore

[Wazhai]

Will this be fixed for focal LTS too? Weather from libgweather has been
completely broken since the beginning of March 2021.

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

Title:
  (Update libgweather to 3.36.2) Weather forecast and info is not
  available anymore

Status in libgweather:
  Unknown
Status in gnome-weather package in Ubuntu:
  Fix Released
Status in libgweather package in Ubuntu:
  Fix Released
Status in gnome-weather source package in Focal:
  Confirmed
Status in libgweather source package in Focal:
  Confirmed
Status in gnome-weather package in Fedora:
  New

Bug description:
  [Impact]

  The weather forecast is not available since one week now. Also, the
  weather info is gone from gnome-shell.

  The weather service provider retired their old API.
  
https://developer.yr.no/news/important-changes-to-locationforecast-and-nowcast/

  https://gitlab.gnome.org/GNOME/libgweather/-/blob/gnome-3-36/NEWS

  ==
  Version 3.36.2
  ==

  This version switches the yr.no backend to use met.no instead. Please note
  that this backport is only meant as a compatibility layer. Where at all
  possible, the newer libgweather 40 should be used as applications cannot
  fully comply with the met.no ToS otherwise.

  
  [Test case]

  - gnome-weather shows the weather forecast
  - gnome-shell shows the weather forecast in the calendar menu

  
  [Regression potential]

  - Weather forecast is totally broken now and can't be more broken.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: libgweather-3-16 3.36.1-1~ubuntu20.04.1
  ProcVersionSignature: Ubuntu 5.8.0-44.50~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-44-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.16
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Mar  7 09:54:52 2021
  InstallationDate: Installed on 2020-04-26 (314 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: libgweather
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/libgweather/+bug/1918044/+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 1921781] Re: Build-depends on qt5-default which is obsolete and dropped in hirsute

[Launchpad Bug Tracker]

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

** Changed in: unity-control-center (Ubuntu)
   Status: New => Confirmed

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

Title:
  Build-depends on qt5-default which is obsolete and dropped in hirsute

Status in indicator-sound package in Ubuntu:
  Confirmed
Status in libqofono package in Ubuntu:
  Fix Released
Status in poppler-qml-plugin package in Ubuntu:
  Fix Released
Status in qtpowerd package in Ubuntu:
  Fix Released
Status in qtubuntu-cameraplugin-fake package in Ubuntu:
  Fix Released
Status in signon-keyring-extension package in Ubuntu:
  Fix Released
Status in signon-plugin-sasl package in Ubuntu:
  Fix Released
Status in signon-ui package in Ubuntu:
  Fix Released
Status in unity-api package in Ubuntu:
  Fix Released
Status in unity-control-center package in Ubuntu:
  Confirmed

Bug description:
  These packages build-depend on the qt5-default package, which has been
  dropped upstream in Debian and will not be available in the hirsute
  release.

  These packages should either be updated to not require this build-
  dependency, or be removed from hirsute.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/1921781/+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 1073669] Re: Bluetooth won't stay disabled after reboot due to early upstart job

[Wazhai]

Still affects 20.04+. My laptop has Bluetooth and it always turns itself
on after a restart.

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

Title:
  Bluetooth won't stay disabled after reboot due to early upstart job

Status in rfkill package in Ubuntu:
  Confirmed

Bug description:
  Using a Dell XPS 13 with Ubuntu 12.04.

  In order to restore RF interfaces to their previous state between
  boots, rfkill is run via two Upstart jobs in /etc/init/: rfkill-
  store.conf (run while shutting down) and rfkill-restore.conf (run when
  starting up). However, while rfkill-restore.conf starts on the Upstart
  local-filesystems signal, there is a high probability that the RF kill
  switches in /sys/class/rfkill/ still won't yet be populated (i.e.
  every time on the Dell XPS 13). This results in behavior like the
  following:

  1. Disable bluetooth via applet.
  2. Reboot.
  3. Login.
  4. Observe bluetooth is re-enabled!

  Bluetooth should have stayed disabled, but since the kill switches
  weren't present when rfkill-restore was run, the kill switch states
  were not restored.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rfkill/+bug/1073669/+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 1938065] Re: systemd 248.3-1ubuntu2 fails to install (when upgrading 21.04->21.10)

[Norbert]

** Tags added: hirsute impish

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

Title:
  systemd 248.3-1ubuntu2 fails to install (when upgrading 21.04->21.10)

Status in systemd package in Ubuntu:
  New

Bug description:
  This happened when trying to upgrade from 21.04 to 21.10.

  Setting up systemd (248.3-1ubuntu2) ...
  systemd-machine-id-setup: error while loading shared libraries: 
libsystemd-shared-247.so: cannot open shared object file: No such file or 
directory
  dpkg: error processing package systemd (--configure):
   installed systemd package post-installation script subprocess returned error 
exit status 127
  Processing triggers for initramfs-tools (0.140ubuntu6) ...
  update-initramfs: Generating /boot/initrd.img-5.11.0-25-generic
  Processing triggers for libc-bin (2.33-0ubuntu7) ...
  Processing triggers for man-db (2.9.4-2) ...
  Processing triggers for dbus (1.12.20-2ubuntu1) ...
  Errors were encountered while processing:
   systemd

  I reverted to old version by manualing installing the hirsute's debs
  (from 21.04: libsystemd0_247.3-3ubuntu3.4_i386.deb
  systemd_247.3-3ubuntu3.4_amd64.deb libnss-
  systemd_247.3-3ubuntu3.4_amd64.deb libsystemd-
  dev_247.3-3ubuntu3.4_amd64.deb systemd-sysv_247.3-3ubuntu3.4_amd64.deb
  libpam-systemd_247.3-3ubuntu3.4_amd64.deb
  libudev1_247.3-3ubuntu3.4_amd64.deb udev_247.3-3ubuntu3.4_amd64.deb
  libsystemd0_247.3-3ubuntu3.4_amd64.deb libudev-
  dev_247.3-3ubuntu3.4_amd64.deb)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1938065/+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 1942703] [NEW] Remove-Unused-Kernel-Packages leaves unused linux-hwe-.*-headers-.* packages around

[Jarno Suni]

Public bug reported:

If user has linux-generic-hwe-18.04 installed, versioned linux-headers
packages depend on versioned linux-hwe-5.4-headers packages that will
not get removed. Consequently in time there will be hundreds of
thousands of unused files under /usr/src. For example I have about
45 totalling 1.4 GB. The number of inodes may be bigger issue,
because file systems have some limitations.

I noted the issue when using my linux-purge tool. It is supposed to be
able to remove kernels, even if the file system runs out of inodes.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: unattended-upgrades 1.1ubuntu1.18.04.14
ProcVersionSignature: Ubuntu 5.4.0-81.91~18.04.1-generic 5.4.128
Uname: Linux 5.4.0-81-generic i686
ApportVersion: 2.20.9-0ubuntu7.24
Architecture: i386
Date: Sun Sep  5 14:38:49 2021
InstallationDate: Installed on 2016-09-05 (1826 days ago)
InstallationMedia: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160719)
PackageArchitecture: all
SourcePackage: unattended-upgrades
UpgradeStatus: Upgraded to bionic on 2019-04-06 (882 days ago)
modified.conffile..etc.apt.apt.conf.d.10periodic: [modified]
mtime.conffile..etc.apt.apt.conf.d.10periodic: 2018-03-26T11:42:30.041160

** Affects: unattended-upgrades
 Importance: Unknown
 Status: Unknown

** Affects: unattended-upgrades (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug bionic i386

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

Title:
  Remove-Unused-Kernel-Packages leaves unused linux-hwe-.*-headers-.*
  packages around

Status in unattended-upgrades:
  Unknown
Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  If user has linux-generic-hwe-18.04 installed, versioned linux-headers
  packages depend on versioned linux-hwe-5.4-headers packages that will
  not get removed. Consequently in time there will be hundreds of
  thousands of unused files under /usr/src. For example I have about
  45 totalling 1.4 GB. The number of inodes may be bigger issue,
  because file systems have some limitations.

  I noted the issue when using my linux-purge tool. It is supposed to be
  able to remove kernels, even if the file system runs out of inodes.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: unattended-upgrades 1.1ubuntu1.18.04.14
  ProcVersionSignature: Ubuntu 5.4.0-81.91~18.04.1-generic 5.4.128
  Uname: Linux 5.4.0-81-generic i686
  ApportVersion: 2.20.9-0ubuntu7.24
  Architecture: i386
  Date: Sun Sep  5 14:38:49 2021
  InstallationDate: Installed on 2016-09-05 (1826 days ago)
  InstallationMedia: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160719)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: Upgraded to bionic on 2019-04-06 (882 days ago)
  modified.conffile..etc.apt.apt.conf.d.10periodic: [modified]
  mtime.conffile..etc.apt.apt.conf.d.10periodic: 2018-03-26T11:42:30.041160

To manage notifications about this bug go to:
https://bugs.launchpad.net/unattended-upgrades/+bug/1942703/+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 1942703] Re: Remove-Unused-Kernel-Packages leaves unused linux-hwe-.*-headers-.* packages around

[Jarno Suni]

** Bug watch added: github.com/mvo5/unattended-upgrades/issues #302
   https://github.com/mvo5/unattended-upgrades/issues/302

** Also affects: unattended-upgrades via
   https://github.com/mvo5/unattended-upgrades/issues/302
   Importance: Unknown
   Status: Unknown

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

Title:
  Remove-Unused-Kernel-Packages leaves unused linux-hwe-.*-headers-.*
  packages around

Status in unattended-upgrades:
  Unknown
Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  If user has linux-generic-hwe-18.04 installed, versioned linux-headers
  packages depend on versioned linux-hwe-5.4-headers packages that will
  not get removed. Consequently in time there will be hundreds of
  thousands of unused files under /usr/src. For example I have about
  45 totalling 1.4 GB. The number of inodes may be bigger issue,
  because file systems have some limitations.

  I noted the issue when using my linux-purge tool. It is supposed to be
  able to remove kernels, even if the file system runs out of inodes.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: unattended-upgrades 1.1ubuntu1.18.04.14
  ProcVersionSignature: Ubuntu 5.4.0-81.91~18.04.1-generic 5.4.128
  Uname: Linux 5.4.0-81-generic i686
  ApportVersion: 2.20.9-0ubuntu7.24
  Architecture: i386
  Date: Sun Sep  5 14:38:49 2021
  InstallationDate: Installed on 2016-09-05 (1826 days ago)
  InstallationMedia: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160719)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: Upgraded to bionic on 2019-04-06 (882 days ago)
  modified.conffile..etc.apt.apt.conf.d.10periodic: [modified]
  mtime.conffile..etc.apt.apt.conf.d.10periodic: 2018-03-26T11:42:30.041160

To manage notifications about this bug go to:
https://bugs.launchpad.net/unattended-upgrades/+bug/1942703/+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 1922186] Re: ibus very difficult to restart

[Gunnar Hjalmarsson]

The behavior when starting ibus-daemon from IBus Preferences was fixed
in ibus 1.5.25-2.

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

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

Title:
  ibus very difficult to restart

Status in ibus:
  New
Status in ibus package in Ubuntu:
  Fix Released

Bug description:
  After closing ibus by task bar -> icon -> rightclick -> `Close` it
  seems to be impossible to restart it.

  Here some ways that should work and how they fail:

  1) Menu -> ibus
  -
  - opens iBus settings 
  - starts ibus service

  Problems:
- No keyboard input is actually processed; I.e. cannot use keyboard then.
- Service is not daemonized; I.e. as soon as the iBus settings window is 
closed, the services quits.

  Suggestion:
- No keyboard input possible seems to be a bug -> should be fixed.
- Service should be daemonized at this point

  2) terminal -> `ibus start`
  ---
  Problems:
- This command does not exist. One has to know, that `ibus-daemon` is the 
one they are searching for.

  Suggestions:
- Implement this command to start the daemon from here

  3) terminal -> `ibus-daemon &` / `ibus-daemon -d`
  -
   - brings up ibus with usable keyboard (good)

  Problems: 
- As soon as terminal gets closed, ibus-daemon quits

  4) terminal -> `nohup ibus-daemon &`
  -
   - brings up ibus with usable keyboard (good)

  Problem: 
- As soon as terminal gets closed, ibus-daemon quits (very strange. 
something I wouldn't expect from a `nohup` call, by the way).

  System
  ===

  - I use ibus in conjunction with ibus-anthy

  
  lsb_release -rd
  --
  Description:  Ubuntu 20.10
  Release:  20.10

  
  apt-cache policy ibus
  --
  ibus:
Installed: 1.5.23-0ubuntu1
Candidate: 1.5.23-0ubuntu1
Version table:
   *** 1.5.23-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu groovy/main amd64 Packages
  100 /var/lib/dpkg/status

  
  apt-cache policy ibus-anthy
  --
  ibus-anthy:
Installed: 1.5.11-1build1
Candidate: 1.5.11-1build1
Version table:
   *** 1.5.11-1build1 500
  500 http://archive.ubuntu.com/ubuntu groovy/universe amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: ibus 1.5.23-0ubuntu1
  ProcVersionSignature: Ubuntu 5.8.0-45.51-generic 5.8.18
  Uname: Linux 5.8.0-45-generic x86_64
  ApportVersion: 2.20.11-0ubuntu50.5
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Thu Apr  1 15:33:00 2021
  RebootRequiredPkgs:
   linux-image-5.8.0-48-generic
   linux-base
   linux-image-5.8.0-49-generic
   linux-base
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ibus/+bug/1922186/+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 1941752] Re: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable

[Launchpad Bug Tracker]

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

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

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

Title:
  Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening
  images exported by darktable

Status in Gwenview:
  Unknown
Status in exiv2 package in Ubuntu:
  Confirmed
Status in gwenview package in Ubuntu:
  Confirmed

Bug description:
  Since the recent security update of exiv2, Gwenview crashes when
  trying to open image files that got exported by darktable.

  Steps to reproduce:

  * Make a test installation of Kubuntu 21.04 in VirtualBox
  * Install all updates
  * Install darktable
  * Copy one of the images in /usr/share/wallpapers (or any other image) to 
your home directory and open it with darktable
  * Within darktable, export a copy of the image (no need to do any actual 
modifications)
  * Try to open that copy with Gwenview. Gwenview will crash.

  I'm attaching a crash report hinting that this is related to exiv2.

  Temporary workaround:
  If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so 
it seems the crash is related to changes in 0.27.3-3ubuntu1.5.

  I don't know if the underlying cause is actually some bug in exiv2,
  Gwenview or darktable.

  Kind regards, Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: libexiv2-27 0.27.3-3ubuntu1.5
  ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22
  Uname: Linux 5.11.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Thu Aug 26 15:16:47 2021
  InstallationDate: Installed on 2021-08-26 (0 days ago)
  InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  SourcePackage: exiv2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gwenview/+bug/1941752/+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 1941752] Re: Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening images exported by darktable

[Launchpad Bug Tracker]

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

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

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

Title:
  Regression: exiv2 0.27.3-3ubuntu1.5 makes Gwenview crash when opening
  images exported by darktable

Status in Gwenview:
  Unknown
Status in exiv2 package in Ubuntu:
  Confirmed
Status in gwenview package in Ubuntu:
  Confirmed

Bug description:
  Since the recent security update of exiv2, Gwenview crashes when
  trying to open image files that got exported by darktable.

  Steps to reproduce:

  * Make a test installation of Kubuntu 21.04 in VirtualBox
  * Install all updates
  * Install darktable
  * Copy one of the images in /usr/share/wallpapers (or any other image) to 
your home directory and open it with darktable
  * Within darktable, export a copy of the image (no need to do any actual 
modifications)
  * Try to open that copy with Gwenview. Gwenview will crash.

  I'm attaching a crash report hinting that this is related to exiv2.

  Temporary workaround:
  If I downgrade libexiv2-27 to 0.27.3-3ubuntu1.4, Gwenview doesn't crash, so 
it seems the crash is related to changes in 0.27.3-3ubuntu1.5.

  I don't know if the underlying cause is actually some bug in exiv2,
  Gwenview or darktable.

  Kind regards, Jan

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: libexiv2-27 0.27.3-3ubuntu1.5
  ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22
  Uname: Linux 5.11.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Thu Aug 26 15:16:47 2021
  InstallationDate: Installed on 2021-08-26 (0 days ago)
  InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  SourcePackage: exiv2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gwenview/+bug/1941752/+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 1448657] Re: isc-dhcp-server: Can't create PID file /run/dhcp-server/dhcpd.pid: Permission denied

[dienteperro]

This bug exists in Ubuntu 20.04 focal.

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

Title:
  isc-dhcp-server: Can't create PID file /run/dhcp-server/dhcpd.pid:
  Permission denied

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  Just upgraded from 14-10 to 15-04, and now see the following in
  syslog:

  Apr 26 10:50:08 server kernel: [70470.960718] audit: type=1400 
audit(1430045408.725:8): apparmor="DENIED" operation="capable" 
profile="/usr/sbin/dhcpd" pid=8619 comm="dhcpd" capability=1  capname="dac_ove
  rride"
  Apr 26 10:50:08 server sh[8619]: Can't create PID file 
/run/dhcp-server/dhcpd.pid: Permission denied.

  Description:Ubuntu 15.04
  Release:15.04

  isc-dhcp-server:
Installed: 4.3.1-5ubuntu2

  --- 8x -

  # cat /etc/default/isc-dhcp-server

  # Defaults for isc-dhcp-server initscript
  # sourced by /etc/init.d/isc-dhcp-server
  # installed at /etc/default/isc-dhcp-server by the maintainer scripts

  #
  # This is a POSIX shell fragment
  #

  # Path to dhcpd's config file (default: /etc/dhcp/dhcpd.conf).
  #DHCPD_CONF=/etc/dhcp/dhcpd.conf

  # Path to dhcpd's PID file (default: /var/run/dhcpd.pid).
  #DHCPD_PID=/var/run/dhcpd.pid

  # Additional options to start dhcpd with.
  #   Don't use options -cf or -pf here; use DHCPD_CONF/ DHCPD_PID instead
  #OPTIONS=""

  # On what interfaces should the DHCP server (dhcpd) serve DHCP requests?
  #   Separate multiple interfaces with spaces, e.g. "eth0 eth1".
  INTERFACES=""

  --- 8x -

  # ls -la /var/run
  lrwxrwxrwx 1 root root 4 Oct 24  2013 /var/run -> /run

  # ls -la /run/dhcp-server/
  total 0
  drwxr-xr-x  2 dhcpd dhcpd   40 Apr 26 10:59 .
  drwxr-xr-x 34 root  root  1060 Apr 26 11:33 ..

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1448657/+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 1900640] Re: Ubuntu 20.04 has no capability of surrounding-text feature

[Gunnar Hjalmarsson]

According to upstream this is an issue with Google Chrome and gnome-
terminal and not IBus.

A workaround when using ibus-libthai is to choose the "No Check" option
under the "Input sequence check mode" category.

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

** Changed in: ibus (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Ubuntu 20.04 has no capability of surrounding-text feature

Status in ibus:
  Unknown
Status in ibus package in Ubuntu:
  Invalid

Bug description:
  I recently upgrade my Ubuntu LTS from 18.04 to 20.04.
  After the upgrade, I failed to type Thai text with any combining character in 
some apps.
  The log contains this error message:
  `gnome-shell[2076]: (google-chrome-stable:2069): IBUS-WARNING **: 
09:07:10.843: google-chrome-stable has no capability of surrounding-text 
feature`
  `gnome-terminal-[2589]: gnome-terminal-server has no capability of 
surrounding-text feature`

  Expected behavior: Capable of typing any Thai character in any app.
  Actual behavior: Only few apps support typing Thai character, e.g. Firefox, 
Gnome Text Editor.

  Step to reproduce:
  1. Boot up the machine.
  2. Open Google Chrome.
  3. Switch keyboard layout to `Thai (LibThai)`
  4. Type Thai text "กิน" which is equals to following keystroke "dbo" but with 
Thai keyboard layout.

  
  Current workaround:
  Whenever you want to type Thai switch 
  1. Open `Gnome Text Editor`
  2. Switch keyboard layout to `Thai (LibThai)`
  3. Switch to Chrome
  4. Type Thai

To manage notifications about this bug go to:
https://bugs.launchpad.net/ibus/+bug/1900640/+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 1761382] Re: Unable to connect to ibus: Could not connect: Connection refused

[Gunnar Hjalmarsson]

I can't reproduce this on the 21.10 development version of Ubuntu. Would
anybody mind if we close this bug report?

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

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

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

Title:
  Unable to connect to ibus: Could not connect: Connection refused

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

Bug description:
  Get this logged:

  oem@ubuntu:~$ journalctl -b | grep ibus

  dbus-daemon[1074]: [session uid=120 pid=1074] Activating service
  name='org.freedesktop.portal.IBus' requested by ':1.18' (uid=120
  pid=1135 comm="ibus-daemon --xim --panel disable " label="unconfined")

  gnome-shell[1084]: Unable to connect to ibus: Could not connect:
  Connection refused

  /usr/lib/gdm3/gdm-x-session[1281]: dbus-update-activation-environment:
  setting QT_IM_MODULE=ibus

  /usr/lib/gdm3/gdm-x-session[1281]: dbus-update-activation-environment:
  setting XMODIFIERS=@im=ibus

  /usr/lib/gdm3/gdm-x-session[1281]: dbus-update-activation-environment:
  setting GTK_IM_MODULE=ibus

  dbus-daemon[1293]: [session uid=1000 pid=1293] Activating service
  name='org.freedesktop.portal.IBus' requested by ':1.27' (uid=1000
  pid=1458 comm="ibus-daemon --xim --panel disable " label="unconfined")

  gnome-shell[1435]: Unable to connect to ibus: Could not connect:
  Connection refused

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.28.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Apr  5 07:43:59 2018
  DisplayManager: gdm3
  EcryptfsInUse: Yes
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1761382/+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 1934981] Re: systemctl suspend-then-hibernate attempts hybrid-sleep instead

[Dan Streetman]

ubuntu@lp1934981-h:~$ dpkg -l systemd|grep systemd
ii  systemd247.3-3ubuntu3.4 amd64system and service manager
ubuntu@lp1934981-h:~$ grep -E 'AllowSuspendThenHibernate|AllowHybridSleep' 
/etc/systemd/sleep.conf
AllowSuspendThenHibernate=yes
AllowHybridSleep=no
ubuntu@lp1934981-h:~$ sudo systemctl suspend-then-hibernate
Failed to suspend system, hibernate later via logind: Sleep verb "hybrid-sleep" 
not supported


ubuntu@lp1934981-h:~$ dpkg -l systemd|grep systemd
ii  systemd247.3-3ubuntu3.5 amd64system and service manager
ubuntu@lp1934981-h:~$ grep -E 'AllowSuspendThenHibernate|AllowHybridSleep' 
/etc/systemd/sleep.conf
AllowSuspendThenHibernate=yes
AllowHybridSleep=no
ubuntu@lp1934981-h:~$ sudo systemctl suspend-then-hibernate
ubuntu@lp1934981-h:~$

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

Title:
  systemctl suspend-then-hibernate attempts hybrid-sleep instead

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Groovy:
  Won't Fix
Status in systemd source package in Hirsute:
  Fix Committed
Status in systemd source package in Impish:
  Fix Committed

Bug description:
  [impact]

  suspend-then-hibernate not possible using systemctl

  [test case]

  configure a system to allow suspend-then-hibernate but not hybrid-
  sleep, e.g. by editing /etc/systemd/sleep.conf to set
  AllowSuspendThenHibernate=yes and AllowHybridSleep=no, then try it:

  $ sudo systemctl suspend-then-hibernate
  Failed to suspend system, hibernate later via logind: Sleep verb 
"hybrid-sleep" not supported

  [regression potential]

  failure to correctly enter hybrid-sleep and/or suspend-then-hibernate,
  or other issues around suspending/hibernating

  [scope]

  This is needed in b and later.

  The bug appears to have been introduced by a typo in the original
  suspend-then-hibernate commit c58493c00af, and then fixed with larger
  changes in commit c8cd8ca3986.

  this is also present in b, by a backport of the functionality

  [other info]

  note that if hybrid-sleep is allowed/possible, then calling 'systemctl
  suspend-then-hibernate' does actually perform suspend-then-hibernate;
  this typo only controls what suspend action logind checks for support
  of, not what suspend action it actually performs.

  [original description]

  ```
  systemctl suspend-then-hibernate
  Failed to suspend system, hibernate later via logind: Sleep verb 
"hybrid-sleep" not supported
  ```

  Note the verb change!

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: systemd 247.3-3ubuntu3
  ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul  8 08:54:01 2021
  InstallationDate: Installed on 2021-07-06 (1 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Dell Inc. XPS 13 9300
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic 
root=/dev/mapper/username-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/systemd-localed.service → 
/usr/lib/systemd/system/systemd-localed.service.d/locale-gen.conf
   [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf

   3 overridden configuration files found.
  SystemdFailedUnits:
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/03/2021
  dmi.bios.release: 1.5
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0PP9G2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd02/03/2021:br1.5:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn0PP9G2:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9300
  dmi.product.sku: 096D
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.systemd.sleep.conf: 2021-07-08T08:51:57.213321

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

[Touch-packages] [Bug 1934981] Re: systemctl suspend-then-hibernate attempts hybrid-sleep instead

[Dan Streetman]

ubuntu@lp1934981-f:~$ dpkg -l systemd|grep systemd
ii  systemd245.4-4ubuntu3.11 amd64system and service manager
ubuntu@lp1934981-f:~$ grep -E 'AllowSuspendThenHibernate|AllowHybridSleep' 
/etc/systemd/sleep.conf
AllowSuspendThenHibernate=yes
AllowHybridSleep=no
ubuntu@lp1934981-f:~$ sudo systemctl suspend-then-hibernate
Failed to suspend system, hibernate later via logind: Sleep verb "hybrid-sleep" 
not supported
ubuntu@lp1934981-f:~$ 

ubuntu@lp1934981-f:~$ dpkg -l systemd|grep systemd
ii  systemd245.4-4ubuntu3.12 amd64system and service manager
ubuntu@lp1934981-f:~$ grep -E 'AllowSuspendThenHibernate|AllowHybridSleep' 
/etc/systemd/sleep.conf
AllowSuspendThenHibernate=yes
AllowHybridSleep=no
ubuntu@lp1934981-f:~$ sudo systemctl suspend-then-hibernate
ubuntu@lp1934981-f:~$

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

Title:
  systemctl suspend-then-hibernate attempts hybrid-sleep instead

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Groovy:
  Won't Fix
Status in systemd source package in Hirsute:
  Fix Committed
Status in systemd source package in Impish:
  Fix Committed

Bug description:
  [impact]

  suspend-then-hibernate not possible using systemctl

  [test case]

  configure a system to allow suspend-then-hibernate but not hybrid-
  sleep, e.g. by editing /etc/systemd/sleep.conf to set
  AllowSuspendThenHibernate=yes and AllowHybridSleep=no, then try it:

  $ sudo systemctl suspend-then-hibernate
  Failed to suspend system, hibernate later via logind: Sleep verb 
"hybrid-sleep" not supported

  [regression potential]

  failure to correctly enter hybrid-sleep and/or suspend-then-hibernate,
  or other issues around suspending/hibernating

  [scope]

  This is needed in b and later.

  The bug appears to have been introduced by a typo in the original
  suspend-then-hibernate commit c58493c00af, and then fixed with larger
  changes in commit c8cd8ca3986.

  this is also present in b, by a backport of the functionality

  [other info]

  note that if hybrid-sleep is allowed/possible, then calling 'systemctl
  suspend-then-hibernate' does actually perform suspend-then-hibernate;
  this typo only controls what suspend action logind checks for support
  of, not what suspend action it actually performs.

  [original description]

  ```
  systemctl suspend-then-hibernate
  Failed to suspend system, hibernate later via logind: Sleep verb 
"hybrid-sleep" not supported
  ```

  Note the verb change!

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: systemd 247.3-3ubuntu3
  ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul  8 08:54:01 2021
  InstallationDate: Installed on 2021-07-06 (1 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Dell Inc. XPS 13 9300
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic 
root=/dev/mapper/username-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/systemd-localed.service → 
/usr/lib/systemd/system/systemd-localed.service.d/locale-gen.conf
   [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf

   3 overridden configuration files found.
  SystemdFailedUnits:
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/03/2021
  dmi.bios.release: 1.5
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0PP9G2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd02/03/2021:br1.5:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn0PP9G2:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9300
  dmi.product.sku: 096D
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.systemd.sleep.conf: 2021-07-08T08:51:57.213321

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


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

[Touch-packages] [Bug 1934981] Re: systemctl suspend-then-hibernate attempts hybrid-sleep instead

[Dan Streetman]

** Description changed:

  [impact]
  
  suspend-then-hibernate not possible using systemctl
  
  [test case]
  
- configure a system to allow suspend-then-hibernate but not hybrid-sleep,
- e.g. by editing /etc/systemd/sleep.conf to set
- AllowSuspendThenHibernate=yes and AllowHybridSleep=no, then try it:
+ configure a system (that has enough swap to be able to hibernate) to
+ allow suspend-then-hibernate but not hybrid-sleep, e.g. by editing
+ /etc/systemd/sleep.conf to set AllowSuspendThenHibernate=yes and
+ AllowHybridSleep=no, then try it:
  
  $ sudo systemctl suspend-then-hibernate
  Failed to suspend system, hibernate later via logind: Sleep verb 
"hybrid-sleep" not supported
+ 
+ note that on bionic, the Allow...= params do not exist, so the repro
+ instead can be done on a system without any configured swap, which will
+ show the incorrect sleep verb before, and correct sleep verb after the
+ fix.
  
  [regression potential]
  
  failure to correctly enter hybrid-sleep and/or suspend-then-hibernate,
  or other issues around suspending/hibernating
  
  [scope]
  
  This is needed in b and later.
  
  The bug appears to have been introduced by a typo in the original
  suspend-then-hibernate commit c58493c00af, and then fixed with larger
  changes in commit c8cd8ca3986.
  
  this is also present in b, by a backport of the functionality
  
  [other info]
  
  note that if hybrid-sleep is allowed/possible, then calling 'systemctl
  suspend-then-hibernate' does actually perform suspend-then-hibernate;
  this typo only controls what suspend action logind checks for support
  of, not what suspend action it actually performs.
  
  [original description]
  
  ```
  systemctl suspend-then-hibernate
  Failed to suspend system, hibernate later via logind: Sleep verb 
"hybrid-sleep" not supported
  ```
  
  Note the verb change!
  
  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: systemd 247.3-3ubuntu3
  ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul  8 08:54:01 2021
  InstallationDate: Installed on 2021-07-06 (1 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Dell Inc. XPS 13 9300
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic 
root=/dev/mapper/username-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/systemd-localed.service → 
/usr/lib/systemd/system/systemd-localed.service.d/locale-gen.conf
   [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf
  
   3 overridden configuration files found.
  SystemdFailedUnits:
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/03/2021
  dmi.bios.release: 1.5
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0PP9G2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd02/03/2021:br1.5:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn0PP9G2:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9300
  dmi.product.sku: 096D
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.systemd.sleep.conf: 2021-07-08T08:51:57.213321

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

Title:
  systemctl suspend-then-hibernate attempts hybrid-sleep instead

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Groovy:
  Won't Fix
Status in systemd source package in Hirsute:
  Fix Committed
Status in systemd source package in Impish:
  Fix Committed

Bug description:
  [impact]

  suspend-then-hibernate not possible using systemctl

  [test case]

  configure a system (that has enough swap to be able to hibernate) to
  allow suspend-then-hibernate but not hybrid-sleep, e.g. by editing
  /etc/systemd/sleep.conf to set AllowSuspendThenHibernate=yes and
  AllowHybridSleep=no, then try it:

  $ sudo systemctl suspend-then-hibernate
  Failed to suspend system, hibernate later via logind: Sleep verb 
"hybrid-sleep" not supported

  note that on bionic, the Allow...= params do not exist, so the repro
  instead can be done on a system with

[Touch-packages] [Bug 1939409] Re: e2fsprogs 1.46.3-1 on architecture s390x fails in test f_baddotdir

[Launchpad Bug Tracker]

This bug was fixed in the package e2fsprogs - 1.46.3-1ubuntu3

---
e2fsprogs (1.46.3-1ubuntu3) impish; urgency=medium

  * Restore mke2fs capability to create files adding patch

- mke2fs: fix creating a file system image w/o a pre-existing file

 -- Heinrich Schuchardt   Mon, 30 Aug
2021 17:58:29 +0200

** Changed in: e2fsprogs (Ubuntu Impish)
   Status: In Progress => Fix Released

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

Title:
  e2fsprogs 1.46.3-1 on architecture s390x fails in test f_baddotdir

Status in e2fsprogs package in Ubuntu:
  Fix Released
Status in e2fsprogs source package in Impish:
  Fix Released

Bug description:
  e2fsprogs 1.46.3-1ubuntu1 is in proposed.

  Architecture s390x fail in test f_baddotdir. The test image was
  changed with the new release.

  Next step should be analyzing the error on a s390x virtual machine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1939409/+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 1934981] Re: systemctl suspend-then-hibernate attempts hybrid-sleep instead

[Dan Streetman]

ubuntu@lp1934981-b:~$ dpkg -l systemd|grep systemd
ii  systemd237-3ubuntu10.51 amd64system and service manager
ubuntu@lp1934981-b:~$ cat /etc/systemd/sleep.conf
[Sleep]
HybridSleepState=bugverification
ubuntu@lp1934981-b:~$ sudo systemctl suspend-then-hibernate 
Failed to put system into suspend followed by hibernate via logind: Sleep verb 
not supported

ubuntu@lp1934981-b:~$ dpkg -l systemd|grep systemd
ii  systemd237-3ubuntu10.52 amd64system and service manager
ubuntu@lp1934981-b:~$ cat /etc/systemd/sleep.conf
[Sleep]
HybridSleepState=bugverification
ubuntu@lp1934981-b:~$ sudo systemctl suspend-then-hibernate 
ubuntu@lp1934981-b:~$ 


** Description changed:

  [impact]
  
  suspend-then-hibernate not possible using systemctl
  
  [test case]
  
  configure a system (that has enough swap to be able to hibernate) to
  allow suspend-then-hibernate but not hybrid-sleep, e.g. by editing
  /etc/systemd/sleep.conf to set AllowSuspendThenHibernate=yes and
  AllowHybridSleep=no, then try it:
  
  $ sudo systemctl suspend-then-hibernate
  Failed to suspend system, hibernate later via logind: Sleep verb 
"hybrid-sleep" not supported
  
- note that on bionic, the Allow...= params do not exist, so the repro
- instead can be done on a system without any configured swap, which will
- show the incorrect sleep verb before, and correct sleep verb after the
- fix.
+ note that on bionic, the Allow...= params do not exist, instead we can
+ reproduce the error by setting one of the hybrid parameters to an
+ invalid value, e.g. HybridSleepState=bugverification
+ 
  
  [regression potential]
  
  failure to correctly enter hybrid-sleep and/or suspend-then-hibernate,
  or other issues around suspending/hibernating
  
  [scope]
  
  This is needed in b and later.
  
  The bug appears to have been introduced by a typo in the original
  suspend-then-hibernate commit c58493c00af, and then fixed with larger
  changes in commit c8cd8ca3986.
  
  this is also present in b, by a backport of the functionality
  
  [other info]
  
  note that if hybrid-sleep is allowed/possible, then calling 'systemctl
  suspend-then-hibernate' does actually perform suspend-then-hibernate;
  this typo only controls what suspend action logind checks for support
  of, not what suspend action it actually performs.
  
  [original description]
  
  ```
  systemctl suspend-then-hibernate
  Failed to suspend system, hibernate later via logind: Sleep verb 
"hybrid-sleep" not supported
  ```
  
  Note the verb change!
  
  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: systemd 247.3-3ubuntu3
  ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21
  Uname: Linux 5.11.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jul  8 08:54:01 2021
  InstallationDate: Installed on 2021-07-06 (1 days ago)
  InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  MachineType: Dell Inc. XPS 13 9300
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-22-generic 
root=/dev/mapper/username-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /usr/lib/systemd/system/rc-local.service → 
/usr/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /usr/lib/systemd/system/systemd-localed.service → 
/usr/lib/systemd/system/systemd-localed.service.d/locale-gen.conf
   [EXTENDED]   /usr/lib/systemd/system/user@.service → 
/usr/lib/systemd/system/user@.service.d/timeout.conf
  
   3 overridden configuration files found.
  SystemdFailedUnits:
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/03/2021
  dmi.bios.release: 1.5
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.5.0
  dmi.board.name: 0PP9G2
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.5.0:bd02/03/2021:br1.5:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn0PP9G2:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9300
  dmi.product.sku: 096D
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.systemd.sleep.conf: 2021-07-08T08:51:57.213321

** Tags removed: verification-needed verification-needed-bionic 
verification-needed-focal verification-needed-hirsute
** Tags added: verification-done verification-done-bionic 
verification-done-focal verification-done-hirsute

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

Title:
  systemctl suspend-then-hibernate attempts hybrid-sleep instead

Status in systemd package in U

[Touch-packages] [Bug 1934147] Re: systemd leaks abandoned session scopes

[Dan Streetman]

ubuntu@lp1934147-h:~$ dpkg -l systemd|grep systemd
ii  systemd247.3-3ubuntu3.4 amd64system and service manager
ubuntu@lp1934147-h:~$ for i in {1..100}; do sudo -b -i -u ubuntu ssh localhost 
-- sleep 1; done; for i in {1..20}; do echo 'Reloading...'; sudo systemctl 
daemon-reload; done
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
ubuntu@lp1934147-h:~$ loginctl list-sessions
SESSION  UID USER   SEAT TTY
  1 1000 ubuntu  ttyS0
 51 1000 ubuntu  
 55 1000 ubuntu  
 56 1000 ubuntu  
 58 1000 ubuntu  

5 sessions listed.

ubuntu@lp1934147-h:~$ dpkg -l systemd|grep systemd
ii  systemd247.3-3ubuntu3.5 amd64system and service manager
ubuntu@lp1934147-h:~$ loginctl list-sessions
SESSION  UID USER   SEAT TTY
  1 1000 ubuntu  ttyS0

1 sessions listed.
ubuntu@lp1934147-h:~$ for i in {1..100}; do sudo -b -i -u ubuntu ssh localhost 
-- sleep 1; done; for i in {1..20}; do echo 'Reloading...'; sudo systemctl 
daemon-reload; done
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
ubuntu@lp1934147-h:~$ loginctl list-sessions
SESSION  UID USER   SEAT TTY
  1 1000 ubuntu  ttyS0

1 sessions listed.

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

Title:
  systemd leaks abandoned session scopes

Status in snapd:
  New
Status in systemd:
  New
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Groovy:
  Won't Fix
Status in systemd source package in Hirsute:
  Fix Committed
Status in systemd source package in Impish:
  Fix Committed

Bug description:
  [impact]

  systemd may leak sessions, leaving empty cgroups around as well as
  abandoned session scopes.

  [test case]

  on a system where the user has a ssh key that allows noninteractive
  login to localhost, and also has noninteractive sudo, run:

  $ for i in {1..100}; do sudo -b -i -u ubuntu ssh localhost -- sleep 1;
  done; for i in {1..20}; do echo 'Reloading...'; sudo systemctl daemon-
  reload; done

  check the sessions to see there have been leaked sessions:

  $ loginctl list-sessions

  SESSION  UID USER   SEAT TTY
1 1000 ubuntu  ttyS0
  350 1000 ubuntu  
  351 1000 ubuntu  
  360 1000 ubuntu  
  ...

  to verify the sessions were leaked, clear them out with:

  $ echo '' | sudo tee
  
/sys/fs/cgroup/unified/user.slice/user-1000.slice/session-*.scope/cgroup.events

  that should result in all the leaked sessions being cleaned up.

  [regression potential]

  issues during systemd pid1 reexec/reload, or issues while cleaning up
  sessions, including leaking sessions/cgroups

  [scope]

  this is needed for all releases

  upstream bug linked above, and upstream PR:
  https://github.com/systemd/systemd/pull/20199

  [original description]

  On a system that is monitored via telegraf I found many abandoned
  systemd session which I believe are created by a potential race where
  systemd is reloading unit files and at the same time a user is
  connecting to the system via ssh or is executing the su command.

  The simple reproducer

  $ for i in {1..100}; do sleep 0.2; ssh localhost sudo systemctl
  daemon-reload & ssh localhost sleep 1 & done

  Wait > 1 second

  $ jobs -p | xargs --verbose --no-run-if-empty kill -KILL

  To clean out STOPPED jobs and

  $ systemctl status --all 2> /dev/null | grep --before-context 3
  abandoned

  will produce something similar to

     │ ├─  175 su - ubuntu
     │ ├─  178 -su
     │ ├─62375 systemctl status --all
     │ └─62376 grep --color=auto --before-context 3 abandoned
  --
  ● session-273.scope - Session 273 of user ubuntu
     Loaded: loaded (/run/systemd/transient/session-273.scope; transient)
  Transient: yes
     Active: active (abandoned) since Wed 2021-06-30 13:32:03 UTC; 4min 7s ago
  --
  ● session-274.scope - Session 274 of user ubuntu
     Loaded: loaded (/run/systemd/transient/session-274.scope; transient)
  Transient: yes
     Active: active (abandoned) since Wed 2021-06-30 13:32:03 UTC; 4min 7s ago
  --
  ● session-30.scope - Session 30 of user ubuntu
     Loaded: loaded (/run/systemd/transient/session-30.scope; transient)
  Transient: yes
     Active: active (abandoned) since Wed 2021-06-30 10:05:56 UTC; 3h 30min ago
  --
  ● session-302.scope - Session 302 of

[Touch-packages] [Bug 1934147] Re: systemd leaks abandoned session scopes

[Dan Streetman]

ubuntu@lp1934147-f:~$ dpkg -l systemd | grep systemd
ii  systemd245.4-4ubuntu3.11 amd64system and service manager
ubuntu@lp1934147-f:~$ loginctl list-sessions
SESSION  UID USER   SEAT TTY  
  1 1000 ubuntu  ttyS0

1 sessions listed.
ubuntu@lp1934147-f:~$ for i in {1..100}; do sudo -b -i -u ubuntu ssh localhost 
-- sleep 1; done; for i in {1..20}; do echo 'Reloading...'; sudo systemctl 
daemon-reload; done
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
ubuntu@lp1934147-f:~$ loginctl list-sessions
SESSION  UID USER   SEAT TTY  
  1 1000 ubuntu  ttyS0
103 1000 ubuntu   
 75 1000 ubuntu   
 82 1000 ubuntu   

4 sessions listed.

ubuntu@lp1934147-f:~$ dpkg -l systemd | grep systemd
ii  systemd245.4-4ubuntu3.12 amd64system and service manager
ubuntu@lp1934147-f:~$ loginctl list-sessions
SESSION  UID USER   SEAT TTY  
  1 1000 ubuntu  ttyS0

1 sessions listed.
ubuntu@lp1934147-f:~$ for i in {1..100}; do sudo -b -i -u ubuntu ssh localhost 
-- sleep 1; done; for i in {1..20}; do echo 'Reloading...'; sudo systemctl 
daemon-reload; done
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
ubuntu@lp1934147-f:~$ loginctl list-sessions
SESSION  UID USER   SEAT TTY  
  1 1000 ubuntu  ttyS0

1 sessions listed.

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

Title:
  systemd leaks abandoned session scopes

Status in snapd:
  New
Status in systemd:
  New
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Groovy:
  Won't Fix
Status in systemd source package in Hirsute:
  Fix Committed
Status in systemd source package in Impish:
  Fix Committed

Bug description:
  [impact]

  systemd may leak sessions, leaving empty cgroups around as well as
  abandoned session scopes.

  [test case]

  on a system where the user has a ssh key that allows noninteractive
  login to localhost, and also has noninteractive sudo, run:

  $ for i in {1..100}; do sudo -b -i -u ubuntu ssh localhost -- sleep 1;
  done; for i in {1..20}; do echo 'Reloading...'; sudo systemctl daemon-
  reload; done

  check the sessions to see there have been leaked sessions:

  $ loginctl list-sessions

  SESSION  UID USER   SEAT TTY
1 1000 ubuntu  ttyS0
  350 1000 ubuntu  
  351 1000 ubuntu  
  360 1000 ubuntu  
  ...

  to verify the sessions were leaked, clear them out with:

  $ echo '' | sudo tee
  
/sys/fs/cgroup/unified/user.slice/user-1000.slice/session-*.scope/cgroup.events

  that should result in all the leaked sessions being cleaned up.

  [regression potential]

  issues during systemd pid1 reexec/reload, or issues while cleaning up
  sessions, including leaking sessions/cgroups

  [scope]

  this is needed for all releases

  upstream bug linked above, and upstream PR:
  https://github.com/systemd/systemd/pull/20199

  [original description]

  On a system that is monitored via telegraf I found many abandoned
  systemd session which I believe are created by a potential race where
  systemd is reloading unit files and at the same time a user is
  connecting to the system via ssh or is executing the su command.

  The simple reproducer

  $ for i in {1..100}; do sleep 0.2; ssh localhost sudo systemctl
  daemon-reload & ssh localhost sleep 1 & done

  Wait > 1 second

  $ jobs -p | xargs --verbose --no-run-if-empty kill -KILL

  To clean out STOPPED jobs and

  $ systemctl status --all 2> /dev/null | grep --before-context 3
  abandoned

  will produce something similar to

     │ ├─  175 su - ubuntu
     │ ├─  178 -su
     │ ├─62375 systemctl status --all
     │ └─62376 grep --color=auto --before-context 3 abandoned
  --
  ● session-273.scope - Session 273 of user ubuntu
     Loaded: loaded (/run/systemd/transient/session-273.scope; transient)
  Transient: yes
     Active: active (abandoned) since Wed 2021-06-30 13:32:03 UTC; 4min 7s ago
  --
  ● session-274.scope - Session 274 of user ubuntu
     Loaded: loaded (/run/systemd/transient/session-274.scope; transient)
  Transient: yes
     Active: active (abandoned) since Wed 2021-06-30 13:32:03 UTC; 4min 7s ago
  --
  ● session-30.scope - Session 30 of user ubuntu
     Loaded: loaded (/run/systemd/transient/session-30.scope; transient)
  Transient:

[Touch-packages] [Bug 1678187] Re: Removing a linux-image-extra package fails, if /boot is about full

[Hayden Clark]

Sorry I was not clear enough.
When I said "Filled with" I meant that they were the files occupying space. I'm 
sorry if that gave the idea that the corresponding vmlinuz-* files weren't 
present - it was just that in terms of bytes occupied, the initrd files are the 
big ones.

As you can see from the directory listings, this has been a problem,
and, since I'm using a Lenovo Thinkbook 15, I used the OEM kernel
install. I probably followed https://wiki.ubuntu.com/Kernel/OEMKernel to
install it and it fixed my audio problems.

When removing kernels, I followed the instructions on the
RemoveOldKernels page once I found them.

What this bug is about is that when you somehow get a full /boot (from
whatever cause), the updates stop working. Since /boot is a finite
resource, it would be nice if the system could recover either
automatically, or in an easy-to-initiate way.

Thank you for my free operating system :-)

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

Title:
  Removing a linux-image-extra package fails, if /boot is about full

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  System calls /etc/kernel/postinst.d/initramfs-tools when
  purging/removing a linux-image-extra package. That calls "update-
  initramfs -c" which needs significant amount of additional disk space
  in /boot temporarily. But there is no space left, if /boot is full.

  Likewise /etc/kernel/postinst.d/dkms may call "update-initramfs -u".

  The fix could be to create the new initrg.img file in different partition 
before replacing the old one by it in update-initramfs. So the update-initramfs 
script should be fixed. But there may not be such a partition..
  Anyway the likely case when space runs out is when there is a separate /boot 
partition.

  Alternatively the init scripts should remove the respective 
/boot/initrd.img- file when removing/installing the linux-image-extra 
package. That could also be done by
  update-initramfs -d -k 
  That may be worse way, as then initrd.img file is missing for longer period 
of time and system integrity may suffer in case of e.g. power cut.

  Related question: http://askubuntu.com/q/898499/21005
  The output of 'dpkg --purge' presented there shows that corresponding 
linux-image package may get successfully removed while the linux-image-extra is 
left broken. If the linux-image-extra package will be removed later, the 
post-installation script will create an initrd.img file for a non-installed 
kernel! Same would happen, if removing would be done by apt-get purge.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: initramfs-tools 0.103ubuntu4.7
  ProcVersionSignature: Ubuntu 4.4.0-71.92~14.04.1-generic 4.4.49
  Uname: Linux 4.4.0-71-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 31 17:42:35 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-09-21 (922 days ago)
  InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.1)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1678187/+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 1934147] Re: systemd leaks abandoned session scopes

[Dan Streetman]

ubuntu@lp1934147-b:~$ dpkg -l systemd|grep systemd
ii  systemd237-3ubuntu10.51 amd64system and service manager
ubuntu@lp1934147-b:~$ loginctl list-sessions
   SESSIONUID USER SEAT TTY 
 2   1000 ubuntuttyS0   

1 sessions listed.
ubuntu@lp1934147-b:~$ for i in {1..100}; do sudo -b -i -u ubuntu ssh localhost 
-- sleep 1; done; for i in {1..20}; do echo 'Reloading...'; sudo systemctl 
daemon-reload; done
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
ubuntu@lp1934147-b:~$ loginctl list-sessions
   SESSIONUID USER SEAT TTY 
60   1000 ubuntu
   103   1000 ubuntu
   105   1000 ubuntu
80   1000 ubuntu
   104   1000 ubuntu
 2   1000 ubuntuttyS0   
   100   1000 ubuntu
63   1000 ubuntu
83   1000 ubuntu
74   1000 ubuntu
95   1000 ubuntu
64   1000 ubuntu
76   1000 ubuntu
59   1000 ubuntu

14 sessions listed.

ubuntu@lp1934147-b:~$ dpkg -l systemd|grep systemd
ii  systemd237-3ubuntu10.52 amd64system and service manager
ubuntu@lp1934147-b:~$ loginctl list-sessions
   SESSIONUID USER SEAT TTY 
 2   1000 ubuntuttyS0   

1 sessions listed.
ubuntu@lp1934147-b:~$ for i in {1..100}; do sudo -b -i -u ubuntu ssh localhost 
-- sleep 1; done; for i in {1..20}; do echo 'Reloading...'; sudo systemctl 
daemon-reload; done
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
Reloading...
ubuntu@lp1934147-b:~$ loginctl list-sessions
   SESSIONUID USER SEAT TTY 
 2   1000 ubuntuttyS0   

1 sessions listed.


** Tags removed: verification-needed verification-needed-bionic 
verification-needed-focal verification-needed-hirsute
** Tags added: verification-done verification-done-bionic 
verification-done-focal verification-done-hirsute

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

Title:
  systemd leaks abandoned session scopes

Status in snapd:
  New
Status in systemd:
  New
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Groovy:
  Won't Fix
Status in systemd source package in Hirsute:
  Fix Committed
Status in systemd source package in Impish:
  Fix Committed

Bug description:
  [impact]

  systemd may leak sessions, leaving empty cgroups around as well as
  abandoned session scopes.

  [test case]

  on a system where the user has a ssh key that allows noninteractive
  login to localhost, and also has noninteractive sudo, run:

  $ for i in {1..100}; do sudo -b -i -u ubuntu ssh localhost -- sleep 1;
  done; for i in {1..20}; do echo 'Reloading...'; sudo systemctl daemon-
  reload; done

  check the sessions to see there have been leaked sessions:

  $ loginctl list-sessions

  SESSION  UID USER   SEAT TTY
1 1000 ubuntu  ttyS0
  350 1000 ubuntu  
  351 1000 ubuntu  
  360 1000 ubuntu  
  ...

  to verify the sessions were leaked, clear them out with:

  $ echo '' | sudo tee
  
/sys/fs/cgroup/unified/user.slice/user-1000.slice/session-*.scope/cgroup.events

  that should result in all the leaked sessions being cleaned up.

  [regression potential]

  issues during systemd pid1 reexec/reload, or issues while cleaning up
  sessions, including leaking sessions/cgroups

  [scope]

  this is needed for all releases

  upstream bug linked above, and upstream PR:
  https://github.com/systemd/systemd/pull/20199

  [original descri

[Touch-packages] [Bug 1937238] Re: systemd-time-wait-sync.service stuck in "activating" state after boot, blocks timers from starting

[Dan Streetman]

marking verified per comment 18, thanks!

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

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

Title:
  systemd-time-wait-sync.service stuck in "activating" state after boot,
  blocks timers from starting

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Fix Committed

Bug description:
  [impact]

  systemd-time-wait-sync service sometimes misses sync completed event
  and remains in 'activating' state

  [test case]

  this isn't consistently reproducable, see original description for
  test case

  [regression potential]

  possible problems with the systemd-time-wait-sync service completing
  too early or not completing on time

  [scope]

  this is needed only for f

  this is fixed upstream with commit
  f6f4f5fe5395a57f10dd446c7266c53f0673eaac which is in v246, so this is
  fixed in h and later already

  the service does not exist in b so this does not apply there

  [original description]

  When I start my server running Ubuntu 20.04 the systemd-time-wait-
  sync.service is stuck in "activating" state. I noticed this because
  none of the systemd timer units triggered, because all the timers
  depend on systemd-time-wait-sync.service. Running "systemctl restart
  systemd-time-wait-sync.service" manually works around the problem.

  Some logs and command outputs:

  raek@mizar:~$ lsb_release -rd
  Description:Ubuntu 20.04.2 LTS
  Release:20.04

  raek@mizar:~$ systemctl | grep systemd-time-wait-sync.service
    systemd-time-wait-sync.service  
 loaded activating start start Wait Until Kernel Time 
Synchronized

  raek@mizar:~$ systemctl status systemd-time-wait-sync.service
  ● systemd-time-wait-sync.service - Wait Until Kernel Time Synchronized
   Loaded: loaded (/lib/systemd/system/systemd-time-wait-sync.service; 
enabled; vendor preset: enabled)
   Active: activating (start) since Thu 2021-07-22 11:06:52 CEST; 27min ago
     Docs: man:systemd-time-wait-sync.service(8)
     Main PID: 514 (systemd-time-wa)
    Tasks: 1 (limit: 9415)
   Memory: 972.0K
   CGroup: /system.slice/systemd-time-wait-sync.service
   └─514 /lib/systemd/systemd-time-wait-sync

  Jul 22 11:06:52 mizar systemd-time-wait-sync[514]: adjtime state 5 status 40 
time Thu 2021-07-22 09:06:52.216338 UTC
  Warning: journal has been rotated since unit was started, output may be 
incomplete.

  raek@mizar:~$ journalctl -b -u systemd-time-wait-sync.service
  -- Logs begin at Wed 2020-07-08 16:34:13 CEST, end at Thu 2021-07-22 11:36:44 
CEST. --
  Jul 22 11:06:52 mizar systemd-time-wait-sync[514]: adjtime state 5 status 40 
time Thu 2021-07-22 09:06:52.216338 UTC

  raek@mizar:~$ dpkg -S /lib/systemd/system/systemd-time-wait-sync.service
  systemd: /lib/systemd/system/systemd-time-wait-sync.service

  raek@mizar:~$ apt-cache policy systemd
  systemd:
    Installed: 245.4-4ubuntu3.11
    Candidate: 245.4-4ubuntu3.11
    Version table:
   *** 245.4-4ubuntu3.11 500
  500 http://se.archive.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   245.4-4ubuntu3.10 500
  500 http://se.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
   245.4-4ubuntu3.8 400
  400 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 
Packages
   245.4-4ubuntu3 500
  500 http://se.archive.ubuntu.com/ubuntu focal/main amd64 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1937238/+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 1939255] Re: dhclient triggers systemd-resolved start limit when processing more than 5 interfaces at once

[Dan Streetman]

ubuntu@lp1939255-f:~$ dpkg -l systemd|grep systemd
ii  systemd245.4-4ubuntu3.11 amd64system and service manager
ubuntu@lp1939255-f:~$ sudo dhclient ens8 ens9 ens10 ens11 ens12 ens13 ens14 
ens15
ubuntu@lp1939255-f:~$ journalctl --no-pager -b -u systemd-resolved
-- Logs begin at Sun 2021-09-05 21:35:56 UTC, end at Sun 2021-09-05 21:40:13 
UTC. --
...
Sep 05 21:40:13 lp1939255-f systemd[1]: systemd-resolved.service: Start request 
repeated too quickly.
Sep 05 21:40:13 lp1939255-f systemd[1]: systemd-resolved.service: Failed with 
result 'start-limit-hit'.
Sep 05 21:40:13 lp1939255-f systemd[1]: Failed to start Network Name Resolution.


ubuntu@lp1939255-f:~$ dpkg -l systemd|grep systemd
ii  systemd245.4-4ubuntu3.12 amd64system and service manager
ubuntu@lp1939255-f:~$ sudo dhclient ens8 ens9 ens10 ens11 ens12 ens13 ens14 
ens15
ubuntu@lp1939255-f:~$ journalctl --no-pager -b -u systemd-resolved
-- Logs begin at Sun 2021-09-05 21:35:56 UTC, end at Sun 2021-09-05 21:44:25 
UTC. --
...
Sep 05 21:44:23 lp1939255-f systemd[1]: Started Network Name Resolution.

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

Title:
  dhclient triggers systemd-resolved start limit when processing more
  than 5 interfaces at once

Status in systemd package in Ubuntu:
  Invalid
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Focal:
  Fix Committed

Bug description:
  [impact]

  on a system where systemd-resolved is running, if dhclient is used on
  more than 5 interfaces, it calls the '/etc/dhcp/dhclient-enter-
  hooks.d/resolved' script multiple times, which then restarts systemd-
  resolved multiple times, triggering the unit's start-limit throttle
  which results in the unit entering failed state

  [test case]

  on a system with more than 5 available interfaces to run dhclient on
  (where all the interfaces will get a dhcp response), run dhclient with
  the interfaces:

  $ dhclient ens8 ens9 ens10 ens11 ens12 ens13 ens14 ens15

  check if systemd-resolved failed:

  $ journalctl -b -1 -u systemd-resolved
  ...
  Aug 09 00:38:08 sf316232-b systemd[1]: systemd-resolved.service: Start 
request repeated too quickly.
  Aug 09 00:38:08 sf316232-b systemd[1]: systemd-resolved.service: Failed with 
result 'start-limit-hit'.
  Aug 09 00:38:08 sf316232-b systemd[1]: Failed to start Network Name 
Resolution.

  [regression potential]

  failure to start/stop/restart systemd-resolved, or problems adding
  dhclient-provided DNS nameservers to systemd-resolved

  [scope]

  this is needed only for b/f

  the dhclient 'hook' script is provided by the systemd package in focal
  and earlier, and needs fixing in those releases

  in h and later, the 'hook' script is included in the isc-dhcp-client
  package and notifies systemd-resolved in a more direct way without
  requiring restarting, and so doesn't trigger the restart limiting.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1939255/+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 1939255] Re: dhclient triggers systemd-resolved start limit when processing more than 5 interfaces at once

[Dan Streetman]

ubuntu@lp1939255-b:~$ dpkg -l systemd|grep systemd
ii  systemd237-3ubuntu10.51 amd64system and service manager
ubuntu@lp1939255-b:~$ sudo dhclient ens8 ens9 ens10 ens11 ens12 ens13 ens14 
ens15
ubuntu@lp1939255-b:~$ journalctl --no-pager -b -u systemd-resolved
-- Logs begin at Sun 2021-09-05 21:36:12 UTC, end at Sun 2021-09-05 21:41:06 
UTC. --
...
Sep 05 21:40:57 lp1939255-b systemd[1]: systemd-resolved.service: Start request 
repeated too quickly.
Sep 05 21:40:57 lp1939255-b systemd[1]: systemd-resolved.service: Failed with 
result 'start-limit-hit'.
Sep 05 21:40:57 lp1939255-b systemd[1]: Failed to start Network Name Resolution.

ubuntu@lp1939255-b:~$ dpkg -l systemd|grep systemd
ii  systemd237-3ubuntu10.52 amd64system and service manager
ubuntu@lp1939255-b:~$ sudo dhclient ens8 ens9 ens10 ens11 ens12 ens13 ens14 
ens15
ubuntu@lp1939255-b:~$ journalctl --no-pager -b -u systemd-resolved
-- Logs begin at Sun 2021-09-05 21:36:12 UTC, end at Sun 2021-09-05 21:50:57 
UTC. --
...
Sep 05 21:50:57 lp1939255-b systemd[1]: Started Network Name Resolution.


** Tags removed: verification-needed verification-needed-bionic 
verification-needed-focal
** Tags added: verification-done verification-done-bionic 
verification-done-focal

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

Title:
  dhclient triggers systemd-resolved start limit when processing more
  than 5 interfaces at once

Status in systemd package in Ubuntu:
  Invalid
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Focal:
  Fix Committed

Bug description:
  [impact]

  on a system where systemd-resolved is running, if dhclient is used on
  more than 5 interfaces, it calls the '/etc/dhcp/dhclient-enter-
  hooks.d/resolved' script multiple times, which then restarts systemd-
  resolved multiple times, triggering the unit's start-limit throttle
  which results in the unit entering failed state

  [test case]

  on a system with more than 5 available interfaces to run dhclient on
  (where all the interfaces will get a dhcp response), run dhclient with
  the interfaces:

  $ dhclient ens8 ens9 ens10 ens11 ens12 ens13 ens14 ens15

  check if systemd-resolved failed:

  $ journalctl -b -1 -u systemd-resolved
  ...
  Aug 09 00:38:08 sf316232-b systemd[1]: systemd-resolved.service: Start 
request repeated too quickly.
  Aug 09 00:38:08 sf316232-b systemd[1]: systemd-resolved.service: Failed with 
result 'start-limit-hit'.
  Aug 09 00:38:08 sf316232-b systemd[1]: Failed to start Network Name 
Resolution.

  [regression potential]

  failure to start/stop/restart systemd-resolved, or problems adding
  dhclient-provided DNS nameservers to systemd-resolved

  [scope]

  this is needed only for b/f

  the dhclient 'hook' script is provided by the systemd package in focal
  and earlier, and needs fixing in those releases

  in h and later, the 'hook' script is included in the isc-dhcp-client
  package and notifies systemd-resolved in a more direct way without
  requiring restarting, and so doesn't trigger the restart limiting.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1939255/+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 1935051] Re: systemd pid 1 memory leak

[Dan Streetman]

@bocmanpy, can you check with the version of systemd from -proposed
(instructions for how to install it are in comment 7) and verify it
still fixes the issue for you?

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

Title:
  systemd pid 1 memory leak

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Fix Committed

Bug description:
  [impact]

  pid1 leaks memory when rebuilding unit path cache

  [test case]

  see original description.

  also, the patch contains an example of how to reproduce:

  $ for i in {1..300}; do cp ~/.config/systemd/user/test0001.service
  ~/.config/systemd/user/test$(printf %04d $i).service; systemctl --user
  start test$(printf %04d $i).service;done

  [regression]

  any problems would occur when rebuilding the path cache, possibly
  resulting in memory leaks or pid1 crashes.

  [scope]

  this is needed only in f

  fixed upstream by 3fb2326f3ed87aa0b26078d307ebfb299e36286d which is
  included in v246, so fixed in h and later

  the code in b is very different and doesn't appear to have the leak,
  per original report

  [original description]

  Hi everybody.

  We've meet a memory leak of pid1 process on the focal release.
  When we launch chef-client, several systemd .service and .timers are checked 
for state.
  Every time of this run pid1 increase VSZ/RSS on ~ 232 Kb, this don't happen 
on xenial and bionic releases.
  I straced pid1 when that leak happen and found brk call.
  On pmap view of pid 1 it's anon memory grow on the same address and all 
marked as dirty.
  All that leak memory can be freed by calling systemctl daemon-reexec.

  Searching in systemd github repo i found this commit
  
https://github.com/systemd/systemd/commit/3fb2326f3ed87aa0b26078d307ebfb299e36286d
  - it may be related to this leak.

  

  Environment:
    Distributor ID: Ubuntu
    Description:Ubuntu 20.04.2 LTS
    Release:20.04
    Codename:   focal
    Uname:  5.4.0-77-generic #83-Ubuntu SMP Sat May 8 02:35:39 UTC 2021 
x86_64

  Package:
    systemd:
  Installed: 245.4-4ubuntu3.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1935051/+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 1678187] Re: Removing a linux-image-extra package fails, if /boot is about full

[Jarno Suni]

Actually this bug report is not about updates stopping working. This is
about not being able to remove a kernel with related packages completely
by usual ways due to a specific reason, if /boot becomes full enough.
There are other bug reports that call for bigger /boot partition or an
automatic way of removing unused kernels.

You are welcome. Feel free to donate at https://launchpad.net/linux-
purge

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

Title:
  Removing a linux-image-extra package fails, if /boot is about full

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  System calls /etc/kernel/postinst.d/initramfs-tools when
  purging/removing a linux-image-extra package. That calls "update-
  initramfs -c" which needs significant amount of additional disk space
  in /boot temporarily. But there is no space left, if /boot is full.

  Likewise /etc/kernel/postinst.d/dkms may call "update-initramfs -u".

  The fix could be to create the new initrg.img file in different partition 
before replacing the old one by it in update-initramfs. So the update-initramfs 
script should be fixed. But there may not be such a partition..
  Anyway the likely case when space runs out is when there is a separate /boot 
partition.

  Alternatively the init scripts should remove the respective 
/boot/initrd.img- file when removing/installing the linux-image-extra 
package. That could also be done by
  update-initramfs -d -k 
  That may be worse way, as then initrd.img file is missing for longer period 
of time and system integrity may suffer in case of e.g. power cut.

  Related question: http://askubuntu.com/q/898499/21005
  The output of 'dpkg --purge' presented there shows that corresponding 
linux-image package may get successfully removed while the linux-image-extra is 
left broken. If the linux-image-extra package will be removed later, the 
post-installation script will create an initrd.img file for a non-installed 
kernel! Same would happen, if removing would be done by apt-get purge.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: initramfs-tools 0.103ubuntu4.7
  ProcVersionSignature: Ubuntu 4.4.0-71.92~14.04.1-generic 4.4.49
  Uname: Linux 4.4.0-71-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 31 17:42:35 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2014-09-21 (922 days ago)
  InstallationMedia: Ubuntu-Studio 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.1)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1678187/+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 1938259] Re: Add ACCEL_LOCATION=base property for Dell clamshell models

[Yao Wei]

Is it possible to respin the SRU for now?  I need to correct the sku
number, that 0B0B isn't correct one.  The correct one is 0A36.

I will upstream the fix first.

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

Title:
  Add ACCEL_LOCATION=base property for Dell clamshell models

Status in OEM Priority Project:
  New
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Hirsute:
  Fix Committed
Status in systemd source package in Impish:
  Fix Committed

Bug description:
  We are planning to do SRU to systemd in focal, to avoid unwanted
  screen rotations on some Dell laptop models.

  [Impact]

   * This fixes unwanted rotations on certain Dell clamshell laptop
  models with accelerometer.

  [Test Plan]

   * On Dell laptops with model SKU 0A3E or 0E0E, install this package and 
kernel 5.13, or kernel with this patch backported:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e26f023e01ef26b4138bc1099af309bdc4523d23
   * Rotate the laptop and the display should not be rotated.

  [Where problems could occur]

   * This is to add parameters for certain models in hwdb, and does not
  affect any other part of systemd.

   * This fix would only take effect with kernel 5.13 or the above patch
  backported.

  [scope]

  this is needed for all releases

  this is being fixed upstream by
  https://github.com/systemd/systemd/pull/20314

  [Other info]

   * The patch mentioned above is going to have a separated SRU for
  linux-oem-5.10 and linux-hwe-5.11 (LP: #1938143)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1938259/+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 1941962] Re: pulseaudio crashed with SIGSEGV in XFreeGC() from XCloseDisplay() from pa_x11_wrapper_unref()

[Daniel van Vugt]

** Also affects: xorg-server via
   https://gitlab.freedesktop.org/xorg/lib/libx11/-/issues/139
   Importance: Unknown
   Status: Unknown

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

Title:
  pulseaudio crashed with SIGSEGV in XFreeGC() from XCloseDisplay() from
  pa_x11_wrapper_unref()

Status in X.Org X server:
  Unknown
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/52094416ad4b4132ebf639ec8530fed1fdbac584

  crash

  ProblemType: Crash
  DistroRelease: Ubuntu 21.10
  Package: pulseaudio 1:15.0+dfsg1-1ubuntu2
  Uname: Linux 5.13.13-xanmod1-cacule x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu68
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  anasc  1719 F pulseaudio
   /dev/snd/pcmC0D0p:   anasc  1719 F...m pulseaudio
  CasperMD5CheckResult: pass
  Date: Sat Aug 28 21:00:59 2021
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2021-08-26 (2 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Alpha amd64 (20210824)
  ProcCmdline: /usr/bin/pulseaudio --daemonize=no --log-target=journal
  SegvAnalysis:
   Segfault happened at: 0x7fbcc9d6a8a4 :  mov%edx,0x4(%rax)
   PC (0x7fbcc9d6a8a4) ok
   source "%edx" ok
   destination "0x4(%rax)" (0x0004) not located in a known VMA region 
(needed writable region)!
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: pulseaudio
  StacktraceTop:
   XFreeGC () from /lib/x86_64-linux-gnu/libX11.so.6
   XCloseDisplay () from /lib/x86_64-linux-gnu/libX11.so.6
   pa_x11_wrapper_unref () from 
/usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-15.0.so
   module_x11_publish_LTX_pa__done () from 
/usr/lib/pulse-15.0+dfsg1/modules/module-x11-publish.so
   ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-15.0.so
  Title: pulseaudio crashed with SIGSEGV in XFreeGC()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  dmi.bios.date: 02/05/2021
  dmi.bios.release: 15.14
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.14
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 86E2
  dmi.board.vendor: HP
  dmi.board.version: 95.36
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 95.36
  dmi.modalias: 
dmi:bvnInsyde:bvrF.14:bd02/05/2021:br15.14:efr95.36:svnHP:pnHPPavilionLaptop15-cs3xxx:pvrType1ProductConfigId:sku5SU52EA#BH4:rvnHP:rn86E2:rvr95.36:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Laptop 15-cs3xxx
  dmi.product.sku: 5SU52EA#BH4
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1941962/+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 1938259] Re: Add ACCEL_LOCATION=base property for Dell clamshell models

[Yao Wei]

** Tags added: verification-failed-focal

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

Title:
  Add ACCEL_LOCATION=base property for Dell clamshell models

Status in OEM Priority Project:
  New
Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Focal:
  Fix Committed
Status in systemd source package in Hirsute:
  Fix Committed
Status in systemd source package in Impish:
  Fix Committed

Bug description:
  We are planning to do SRU to systemd in focal, to avoid unwanted
  screen rotations on some Dell laptop models.

  [Impact]

   * This fixes unwanted rotations on certain Dell clamshell laptop
  models with accelerometer.

  [Test Plan]

   * On Dell laptops with model SKU 0A3E or 0E0E, install this package and 
kernel 5.13, or kernel with this patch backported:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e26f023e01ef26b4138bc1099af309bdc4523d23
   * Rotate the laptop and the display should not be rotated.

  [Where problems could occur]

   * This is to add parameters for certain models in hwdb, and does not
  affect any other part of systemd.

   * This fix would only take effect with kernel 5.13 or the above patch
  backported.

  [scope]

  this is needed for all releases

  this is being fixed upstream by
  https://github.com/systemd/systemd/pull/20314

  [Other info]

   * The patch mentioned above is going to have a separated SRU for
  linux-oem-5.10 and linux-hwe-5.11 (LP: #1938143)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1938259/+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 1942723] [NEW] Laptop wakes from sleep, no display

[Anonymous]

Public bug reported:

When I close the lid on my laptop to put Kubuntu to sleep, it wakes up
with a black screen - with the exception of a single blinking cursor (_)
in the upper left corner. Machine is clearly on. Turning off/back on
gets the machine back into a good state.

I had a prior installation of Kubuntu on this box and it did not have
this problem, though I do not remember if it had the nvidia drivers.

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: xorg 1:7.7+22ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22
Uname: Linux 5.11.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: KDE
Date: Sun Sep  5 20:05:22 2021
DistUpgraded: Fresh install
DistroCodename: hirsute
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
   Subsystem: Acer Incorporated [ALI] HD Graphics 630 [1025:118a]
 NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] [10de:1c8d] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Mobile] 
[1025:118b]
InstallationDate: Installed on 2021-09-05 (0 days ago)
InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 04f2:b5f7 Chicony Electronics Co., Ltd HD WebCam
 Bus 001 Device 002: ID 04ca:3016 Lite-On Technology Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer Nitro AN515-51
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-31-generic 
root=UUID=8ecb8601-20bb-4090-b7c3-bd63a2fee44e ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/15/2019
dmi.bios.release: 1.22
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.22
dmi.board.asset.tag: Type2 - Board Serial Number
dmi.board.name: Freed_KLS
dmi.board.vendor: KBL
dmi.board.version: V1.22
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.22
dmi.ec.firmware.release: 1.16
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.22:bd03/15/2019:br1.22:efr1.16:svnAcer:pnNitroAN515-51:pvrV1.22:rvnKBL:rnFreed_KLS:rvrV1.22:cvnAcer:ct10:cvrV1.22:
dmi.product.family: Acer Nitro 5
dmi.product.name: Nitro AN515-51
dmi.product.sku: 
dmi.product.version: V1.22
dmi.sys.vendor: Acer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.105-3~21.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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


** Tags: amd64 apport-bug fonts hirsute kubuntu 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/1942723

Title:
  Laptop wakes from sleep, no display

Status in xorg package in Ubuntu:
  New

Bug description:
  When I close the lid on my laptop to put Kubuntu to sleep, it wakes up
  with a black screen - with the exception of a single blinking cursor
  (_) in the upper left corner. Machine is clearly on. Turning off/back
  on gets the machine back into a good state.

  I had a prior installation of Kubuntu on this box and it did not have
  this problem, though I do not remember if it had the nvidia drivers.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22
  Uname: Linux 5.11.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Sun Sep  5 20:05:22 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Acer Incorporated [ALI] HD Graphics 630 [1025:118a]
   NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] [10de:1c8d] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Mobile] 
[1025:118b]
  InstallationDate: Installed on 2021-09-05 (0 days ago)
  InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Lsusb:
  

[Touch-packages] [Bug 1938259] Re: Add ACCEL_LOCATION=base property for Dell clamshell models

[Yao Wei]

We found that Dell Latitude 7420 is not actually fixed, and may cause
Impish to have regression due to the removal of the product name
modalias.

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

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

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

** Tags added: verification-failed-impish

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

Title:
  Add ACCEL_LOCATION=base property for Dell clamshell models

Status in OEM Priority Project:
  New
Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Focal:
  In Progress
Status in systemd source package in Hirsute:
  In Progress
Status in systemd source package in Impish:
  In Progress

Bug description:
  We are planning to do SRU to systemd in focal, to avoid unwanted
  screen rotations on some Dell laptop models.

  [Impact]

   * This fixes unwanted rotations on certain Dell clamshell laptop
  models with accelerometer.

  [Test Plan]

   * On Dell laptops with model SKU 0A3E or 0E0E, install this package and 
kernel 5.13, or kernel with this patch backported:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e26f023e01ef26b4138bc1099af309bdc4523d23
   * Rotate the laptop and the display should not be rotated.

  [Where problems could occur]

   * This is to add parameters for certain models in hwdb, and does not
  affect any other part of systemd.

   * This fix would only take effect with kernel 5.13 or the above patch
  backported.

  [scope]

  this is needed for all releases

  this is being fixed upstream by
  https://github.com/systemd/systemd/pull/20314

  [Other info]

   * The patch mentioned above is going to have a separated SRU for
  linux-oem-5.10 and linux-hwe-5.11 (LP: #1938143)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1938259/+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 1942599] Re: KDE Volume not matching alsa volume in ALC294 (Asus Zenbook UM431D)

[Daniel van Vugt]

** Tags added: hirsute

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

Title:
  KDE Volume not matching alsa volume in ALC294 (Asus Zenbook UM431D)

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Hello.

  I posted  some weeks ago in pulseaudio bugtracker
  https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/1249
  about an issue, but i was thinking it should be better have here the
  issue too because maybe is related with other components in (K)Ubuntu
  system.

  I will go to a copy paste, because it self explanatory:

  ---

  * Context:

  OS: KUbuntu 21.04 with kernel 5.14.0rc4 mainline.
  Laptop: Asus Zenbook UMD431D with ALC294
  pa-info: pa-info.txt (attached)

  Also recently was fixed an issue with alsa about the 4 speakers volume
  (two of them weren't affected by it
  https://bugzilla.kernel.org/show_bug.cgi?id=212547) however, this
  doesn't seems related to that. (That's why i use 5.14.0rc4, because
  5.14 are the first with the patch).

  * Issue behaviour and description

  The main issue can be seen in the next video:
  https://www.youtube.com/watch?v=eBrHi1f9bck

  Summarizing, when you go up and down the KDE volume, if you compared
  the desired volume in the slider with alsamixer doesn't match. But the
  issue is when you reach below 9%, with that the Master volume in
  alsamixer is 0%, so there isn't any sound, and between 1%~8% it's
  changing the "Speaker" slider, doing nothing. It's like the "Speaker"
  slider is stacked below the "Master", but that doesn't make any sense
  in practice.

  Changing the volume in the KDE volume slider is not "linear", between
  50%~100% it's more or less and the volume "feels" right, but below
  that, the volume goes down way faster. For example, having the volume
  at 25%, the sound is almost noticiable unless you put you ears near
  the speakers, something like this should be at 10%, but at the real
  10% you have a barely noticiable sound in the speakers when you have
  your ears directly in them.

  * Expected Results

  The general volume slider should match the Master Volume in alsa, and
  only change that slider.

  Thanks!

  ---

  Offtopic: Also i found doing testing for the kernel bug noted above,
  that changing to some alsa model in this laptop, then appears in the
  volume/audio configurator a selection of output and input what can
  overrides the headphone plug status, and i see it very useful,
  especially because if i plug a headphone without microphone i can't
  use the laptop built-in microphone and the only thing i can do is not
  use headphone. But using some models (dell-headset-multi, for example)
  i can do that, however, it brings the issue with the volume in the
  back speakers. How pulseaudio can be do this? it can be done for my
  laptop?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1942599/+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 1942723] Re: Laptop wakes from sleep, no display

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

2. If step 1 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.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

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

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

Title:
  Laptop wakes from sleep, no display

Status in Ubuntu:
  Incomplete

Bug description:
  When I close the lid on my laptop to put Kubuntu to sleep, it wakes up
  with a black screen - with the exception of a single blinking cursor
  (_) in the upper left corner. Machine is clearly on. Turning off/back
  on gets the machine back into a good state.

  I had a prior installation of Kubuntu on this box and it did not have
  this problem, though I do not remember if it had the nvidia drivers.

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22
  Uname: Linux 5.11.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Sun Sep  5 20:05:22 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: Acer Incorporated [ALI] HD Graphics 630 [1025:118a]
   NVIDIA Corporation GP107M [GeForce GTX 1050 Mobile] [10de:1c8d] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] GP107M [GeForce GTX 1050 Mobile] 
[1025:118b]
  InstallationDate: Installed on 2021-09-05 (0 days ago)
  InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b5f7 Chicony Electronics Co., Ltd HD WebCam
   Bus 001 Device 002: ID 04ca:3016 Lite-On Technology Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Nitro AN515-51
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-31-generic 
root=UUID=8ecb8601-20bb-4090-b7c3-bd63a2fee44e ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/15/2019
  dmi.bios.release: 1.22
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.22
  dmi.board.asset.tag: Type2 - Board Serial Number
  dmi.board.name: Freed_KLS
  dmi.board.vendor: KBL
  dmi.board.version: V1.22
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.22
  dmi.ec.firmware.release: 1.16
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.22:bd03/15/2019:br1.22:efr1.16:svnAcer:pnNitroAN515-51:pvrV1.22:rvnKBL:rnFreed_KLS:rvrV1.22:cvnAcer:ct10:cvrV1.22:
  dmi.product.family: Acer Nitro 5
  dmi.product.name: Nitro AN515-51
  dmi.product.sku: 
  dmi.product.version: V1.22
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~21.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1942723/+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 1942031] Re: gnome-shell crashed with SIGSEGV in _XSend() from XQueryExtension() from InitDisplayInfoEntry() from __glXLookupDisplay() from CommonMakeCurrent()

[Akbarkhon Variskhanov]

I believe this bug needs to be mentioned here:
https://discourse.ubuntu.com/t/impish-indri-release-notes/21951

in the "Ubuntu Desktop" category.

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

Title:
  gnome-shell crashed with SIGSEGV in _XSend() from XQueryExtension()
  from InitDisplayInfoEntry() from __glXLookupDisplay() from
  CommonMakeCurrent()

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

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
40.2-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/11d90a7db51d11df7d99a6ef6e5aa31eb678d273 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1942031/+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 1942031] Re: gnome-shell crashed with SIGSEGV in _XSend() from XQueryExtension() from InitDisplayInfoEntry() from __glXLookupDisplay() from CommonMakeCurrent()

[Daniel van Vugt]

** Tags added: regression-release

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

Title:
  gnome-shell crashed with SIGSEGV in _XSend() from XQueryExtension()
  from InitDisplayInfoEntry() from __glXLookupDisplay() from
  CommonMakeCurrent()

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

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
40.2-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/11d90a7db51d11df7d99a6ef6e5aa31eb678d273 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1942031/+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 1942031] Re: gnome-shell crashed with SIGSEGV in _XSend() from XQueryExtension() from InitDisplayInfoEntry() from __glXLookupDisplay() from CommonMakeCurrent()

[Daniel van Vugt]

Upstream bugs:

https://gitlab.gnome.org/GNOME/mutter/-/issues/1835
https://gitlab.gnome.org/GNOME/mutter/-/issues/1851

appear to be the same issue.

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

** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1835
   https://gitlab.gnome.org/GNOME/mutter/-/issues/1835

** Also affects: mutter via
   https://gitlab.gnome.org/GNOME/mutter/-/issues/1835
   Importance: Unknown
   Status: Unknown

** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1851
   https://gitlab.gnome.org/GNOME/mutter/-/issues/1851

** Also affects: gnome-shell (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  gnome-shell crashed with SIGSEGV in _XSend() from XQueryExtension()
  from InitDisplayInfoEntry() from __glXLookupDisplay() from
  CommonMakeCurrent()

Status in Mutter:
  Unknown
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in libx11 package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
40.2-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/11d90a7db51d11df7d99a6ef6e5aa31eb678d273 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1942031/+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 1942728] [NEW] /usr/bin/pulseaudio:11:_IceTransClose:_IceFreeConnection:IceCloseConnection:SmcCloseConnection:x11_kill_cb

[errors.ubuntu.com bug bridge]

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

Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:15.0+dfsg1-1ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/877172e07ed9f86b0674cd458a5aaf24b37fb01e 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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


** Tags: impish kylin-21.10

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

Title:
  
/usr/bin/pulseaudio:11:_IceTransClose:_IceFreeConnection:IceCloseConnection:SmcCloseConnection:x11_kill_cb

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:15.0+dfsg1-1ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/877172e07ed9f86b0674cd458a5aaf24b37fb01e 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1942728/+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 1942685] Re: pulseaudio crashed with SIGSEGV in _IceTransClose()

[Daniel van Vugt]

** Description changed:

+ https://errors.ubuntu.com/problem/877172e07ed9f86b0674cd458a5aaf24b37fb01e
+ 
+ ---
+ 
  Installing Xubuntu Impish daily ISO 04092021
  
  After install I rebooted - applied updates and then rebooted again-
  
  the errors (pulseaudio crashed with SIGSEGV in _IceTransClose() )
  occurred after logging in.
  
  ProblemType: Crash
  DistroRelease: Ubuntu 21.10
  Package: pulseaudio 1:15.0+dfsg1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1
  Uname: Linux 5.13.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu68
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  kx  847 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  kx  847 F pulseaudio
  CasperMD5CheckResult: pass
  Date: Sat Sep  4 16:43:45 2021
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2021-09-04 (0 days ago)
  InstallationMedia: Xubuntu 21.10 "Impish Indri" - Alpha amd64 (20210904)
  ProcCmdline: /usr/bin/pulseaudio --daemonize=no --log-target=journal
  Signal: 11
  SourcePackage: pulseaudio
  StacktraceTop:
-  _IceTransClose () from /lib/x86_64-linux-gnu/libICE.so.6
-  _IceFreeConnection () from /lib/x86_64-linux-gnu/libICE.so.6
-  IceCloseConnection () from /lib/x86_64-linux-gnu/libICE.so.6
-  SmcCloseConnection () from /lib/x86_64-linux-gnu/libSM.so.6
-  ?? () from /usr/lib/pulse-15.0+dfsg1/modules/module-x11-xsmp.so
+  _IceTransClose () from /lib/x86_64-linux-gnu/libICE.so.6
+  _IceFreeConnection () from /lib/x86_64-linux-gnu/libICE.so.6
+  IceCloseConnection () from /lib/x86_64-linux-gnu/libICE.so.6
+  SmcCloseConnection () from /lib/x86_64-linux-gnu/libSM.so.6
+  ?? () from /usr/lib/pulse-15.0+dfsg1/modules/module-x11-xsmp.so
  Title: pulseaudio crashed with SIGSEGV in _IceTransClose()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  dmi.bios.date: 12/23/2020
  dmi.bios.release: 1.51
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DKCN51WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo V14-IIL
  dmi.ec.firmware.release: 1.51
  dmi.modalias: 
dmi:bvnLENOVO:bvrDKCN51WW:bd12/23/2020:br1.51:efr1.51:svnLENOVO:pn82C4:pvrLenovoV14-IIL:skuLENOVO_MT_82C4_BU_idea_FM_V14-IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoV14-IIL:
  dmi.product.family: V14-IIL
  dmi.product.name: 82C4
  dmi.product.sku: LENOVO_MT_82C4_BU_idea_FM_V14-IIL
  dmi.product.version: Lenovo V14-IIL
  dmi.sys.vendor: LENOVO
  separator:

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

Title:
  pulseaudio crashed with SIGSEGV in _IceTransClose()

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/877172e07ed9f86b0674cd458a5aaf24b37fb01e

  ---

  Installing Xubuntu Impish daily ISO 04092021

  After install I rebooted - applied updates and then rebooted again-

  the errors (pulseaudio crashed with SIGSEGV in _IceTransClose() )
  occurred after logging in.

  ProblemType: Crash
  DistroRelease: Ubuntu 21.10
  Package: pulseaudio 1:15.0+dfsg1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1
  Uname: Linux 5.13.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu68
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kx  847 F pulseaudio
  CasperMD5CheckResult: pass
  Date: Sat Sep  4 16:43:45 2021
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2021-09-04 (0 days ago)
  InstallationMedia: Xubuntu 21.10 "Impish Indri" - Alpha amd64 (20210904)
  ProcCmdline: /usr/bin/pulseaudio --daemonize=no --log-target=journal
  Signal: 11
  SourcePackage: pulseaudio
  StacktraceTop:
   _IceTransClose () from /lib/x86_64-linux-gnu/libICE.so.6
   _IceFreeConnection () from /lib/x86_64-linux-gnu/libICE.so.6
   IceCloseConnection () from /lib/x86_64-linux-gnu/libICE.so.6
   SmcCloseConnection () from /lib/x86_64-linux-gnu/libSM.so.6
   ?? () from /usr/lib/pulse-15.0+dfsg1/modules/module-x11-xsmp.so
  Title: pulseaudio crashed with SIGSEGV in _IceTransClose()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  dmi.bios.date: 12/23/2020
  dmi.bios.release: 1.51
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DKCN51WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo V14-IIL
  dmi.ec.

[Touch-packages] [Bug 1942685] Re: pulseaudio crashed with SIGSEGV in _IceTransClose()

[Launchpad Bug Tracker]

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

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

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

Title:
  pulseaudio crashed with SIGSEGV in _IceTransClose()

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  https://errors.ubuntu.com/problem/877172e07ed9f86b0674cd458a5aaf24b37fb01e

  ---

  Installing Xubuntu Impish daily ISO 04092021

  After install I rebooted - applied updates and then rebooted again-

  the errors (pulseaudio crashed with SIGSEGV in _IceTransClose() )
  occurred after logging in.

  ProblemType: Crash
  DistroRelease: Ubuntu 21.10
  Package: pulseaudio 1:15.0+dfsg1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-14.14-generic 5.13.1
  Uname: Linux 5.13.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu68
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  kx  847 F pulseaudio
  CasperMD5CheckResult: pass
  Date: Sat Sep  4 16:43:45 2021
  ExecutablePath: /usr/bin/pulseaudio
  InstallationDate: Installed on 2021-09-04 (0 days ago)
  InstallationMedia: Xubuntu 21.10 "Impish Indri" - Alpha amd64 (20210904)
  ProcCmdline: /usr/bin/pulseaudio --daemonize=no --log-target=journal
  Signal: 11
  SourcePackage: pulseaudio
  StacktraceTop:
   _IceTransClose () from /lib/x86_64-linux-gnu/libICE.so.6
   _IceFreeConnection () from /lib/x86_64-linux-gnu/libICE.so.6
   IceCloseConnection () from /lib/x86_64-linux-gnu/libICE.so.6
   SmcCloseConnection () from /lib/x86_64-linux-gnu/libSM.so.6
   ?? () from /usr/lib/pulse-15.0+dfsg1/modules/module-x11-xsmp.so
  Title: pulseaudio crashed with SIGSEGV in _IceTransClose()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  dmi.bios.date: 12/23/2020
  dmi.bios.release: 1.51
  dmi.bios.vendor: LENOVO
  dmi.bios.version: DKCN51WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo V14-IIL
  dmi.ec.firmware.release: 1.51
  dmi.modalias: 
dmi:bvnLENOVO:bvrDKCN51WW:bd12/23/2020:br1.51:efr1.51:svnLENOVO:pn82C4:pvrLenovoV14-IIL:skuLENOVO_MT_82C4_BU_idea_FM_V14-IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoV14-IIL:
  dmi.product.family: V14-IIL
  dmi.product.name: 82C4
  dmi.product.sku: LENOVO_MT_82C4_BU_idea_FM_V14-IIL
  dmi.product.version: Lenovo V14-IIL
  dmi.sys.vendor: LENOVO
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1942685/+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 1942728] Re: /usr/bin/pulseaudio:11:_IceTransClose:_IceFreeConnection:IceCloseConnection:SmcCloseConnection:x11_kill_cb

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 1942685
   pulseaudio crashed with SIGSEGV in _IceTransClose()

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

Title:
  
/usr/bin/pulseaudio:11:_IceTransClose:_IceFreeConnection:IceCloseConnection:SmcCloseConnection:x11_kill_cb

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
pulseaudio.  This problem was most recently seen with package version 
1:15.0+dfsg1-1ubuntu2, the problem page at 
https://errors.ubuntu.com/problem/877172e07ed9f86b0674cd458a5aaf24b37fb01e 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1942728/+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 1940505] Re: monero FTBFS on riscv64

[Michael Hudson-Doyle]

** Tags added: update-excuse

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

Title:
  monero FTBFS on riscv64

Status in binutils:
  Fix Released
Status in binutils package in Ubuntu:
  New
Status in monero package in Ubuntu:
  New

Bug description:
  monero FTBFS on riscv64 due to toolchain issues:

  [ 64%] Linking CXX executable signature_fuzz_tests
  cd "/<>/obj-riscv64-linux-gnu/tests/fuzz" && /usr/bin/cmake -E 
cmake_link_script CMakeFiles/signature_fuzz_tests.dir/link.txt --verbose=1
  /usr/bin/c++ -g -O2 -ffile-prefix-map=/<>=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -pthread -DNO_AES  -fno-strict-aliasing -std=c++11 
-D_GNU_SOURCE   -Wall -Wextra -Wpointer-arith -Wundef -Wvla -Wwrite-strings 
-Wno-error=extra -Wno-error=deprecated-declarations -Wno-unused-parameter 
-Wno-unused-variable -Wno-error=unused-variable -Wno-error=undef 
-Wno-error=uninitialized -Wlogical-op -Wno-error=maybe-uninitialized 
-Wno-error=cpp -Wno-reorder -Wno-missing-field-initializers  -fPIC  -Wformat 
-Wformat-security -fstack-protector -fstack-protector-strong 
-fstack-clash-protection -fno-strict-aliasing -ftemplate-depth=900 
-Wl,-Bsymbolic-functions -Wl,-z,relro  -pie -Wl,-z,relro -Wl,-z,now 
-Wl,-z,noexecstack  -rdynamic 
CMakeFiles/signature_fuzz_tests.dir/signature.cpp.o 
CMakeFiles/signature_fuzz_tests.dir/fuzzer.cpp.o -o signature_fuzz_tests  
../../lib/libwallet.a ../../src/cryptonote_core/libcryptonote_core.a 
../../src/p2p/libp2p.a ../../contrib/epee/src/libepee.a 
../../src/device/libdevice.a -Wl,-Bstatic -lrt -Wl,-Bdynamic -ldl 
../../src/rpc/librpc_base.a ../../src/mnemonics/libmnemonics.a 
../../src/device_trezor/libdevice_trezor.a 
../../src/cryptonote_core/libcryptonote_core.a ../../src/multisig/libmultisig.a 
../../src/blockchain_db/libblockchain_db.a 
../../external/db_drivers/liblmdb/liblmdb.a ../../src/ringct/libringct.a 
../../src/cryptonote_basic/libcryptonote_basic.a ../../src/device/libdevice.a 
-lhidapi-libusb ../../src/ringct/libringct_basic.a ../../src/blocks/libblocks.a 
../../src/checkpoints/libcheckpoints.a ../../src/hardforks/libhardforks.a 
../../src/net/libnet.a ../../src/common/libcommon.a 
../../src/crypto/libcncrypto.a ../../contrib/epee/src/libepee.a 
../../external/easylogging++/libeasylogging.a -lrandomx -lunbound -lboost_regex 
-lboost_date_time -lssl -lcrypto -lzmq -lpgm -lnorm -lgssapi_krb5 -lsodium 
../../src/libversion.a -lminiupnpc -lboost_chrono -lboost_serialization 
-lboost_filesystem -lboost_system -lboost_thread -lboost_program_options 
-Wl,-Bstatic -lrt -Wl,-Bdynamic -ldl  -latomic 
  ../../external/db_drivers/liblmdb/liblmdb.a(mdb.c.o): in function 
`mdb_node_add':
  
./obj-riscv64-linux-gnu/external/db_drivers/liblmdb/./external/db_drivers/liblmdb/mdb.c:8245:(.text+0x44e6):
 relocation truncated to fit: R_RISCV_JAL against `mdb_assert_fail.constprop.0'
  collect2: error: ld returned 1 exit status
  make[3]: *** [tests/fuzz/CMakeFiles/signature_fuzz_tests.dir/build.make:166: 
tests/fuzz/signature_fuzz_tests] Error 1
  make[3]: Leaving directory '/<>/obj-riscv64-linux-gnu'
  make[2]: *** [CMakeFiles/Makefile2:4165: 
tests/fuzz/CMakeFiles/signature_fuzz_tests.dir/all] Error 2
  make[2]: Leaving directory '/<>/obj-riscv64-linux-gnu'
  make[1]: *** [Makefile:163: all] Error 2
  make[1]: Leaving directory '/<>/obj-riscv64-linux-gnu'
  dh_auto_build: error: cd obj-riscv64-linux-gnu && make -j1 "INSTALL=install 
--strip-program=true" VERBOSE=1 returned exit code 2
  make: *** [debian/rules:47: binary-arch] Error 25
  dpkg-buildpackage: error: debian/rules binary-arch subprocess returned exit 
status 2

To manage notifications about this bug go to:
https://bugs.launchpad.net/binutils/+bug/1940505/+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 1942738] [NEW] XOrg / nouveau - hard lockups and does not draw to screen

[JXT]

Public bug reported:

Changing display settings hard locks the machine (no reisub save).
Installing nouveau-firmware allows changes to be made without hard lock
ups but the screen using nouveau draws the mouse cursor and will launch
apps on it but does not draw anything on screen. Dmesg is flooded with
nouveau and XOrg failure messages.

Description:Ubuntu 21.04
Release:21.04

xorg:
  Installed: 1:7.7+22ubuntu1
  Candidate: 1:7.7+22ubuntu1
  Version table:
 *** 1:7.7+22ubuntu1 500
500 http://ca.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
100 /var/lib/dpkg/status

nouveau-firmware:
  Installed: 20091212-0ubuntu1
  Candidate: 20091212-0ubuntu1
  Version table:
 *** 20091212-0ubuntu1 500
500 http://ca.archive.ubuntu.com/ubuntu hirsute/multiverse amd64 
Packages
500 http://ca.archive.ubuntu.com/ubuntu hirsute/multiverse i386 Packages
100 /var/lib/dpkg/status


xserver-xorg-video-nouveau:
  Installed: 1:1.0.17-1
  Candidate: 1:1.0.17-1
  Version table:
 *** 1:1.0.17-1 500
500 http://ca.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: xorg 1:7.7+22ubuntu1
ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22
Uname: Linux 5.11.0-31-generic x86_64
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: XFCE
Date: Sun Sep  5 23:52:43 2021
DistUpgraded: Fresh install
DistroCodename: hirsute
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation C61 [GeForce 6100 nForce 405] [10de:03d1] (rev a2) (prog-if 
00 [VGA controller])
   Subsystem: Elitegroup Computer Systems C61 [GeForce 6100 nForce 405] 
[1019:2601]
 Advanced Micro Devices, Inc. [AMD/ATI] Oland XT [Radeon HD 8670 / R7 250/350] 
[1002:6610] (prog-if 00 [VGA controller])
   Subsystem: Diamond Multimedia Systems Oland XT [Radeon HD 8670 / R7 250/350] 
[1092:0250]
InstallationDate: Installed on 2021-04-07 (151 days ago)
InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 003: ID 04d9:a0cd Holtek Semiconductor, Inc. USB Keyboard
 Bus 002 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Acer ASE380/AST180/APM8
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-31-generic 
root=UUID=cf6234fa-9047-4e3a-8931-f8f36bce86cf ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/29/2006
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: R01-B1
dmi.board.name: EM61SM/EM61PM
dmi.board.vendor: Acer
dmi.chassis.asset.tag: Asset tag number: at least 22 digits
dmi.chassis.type: 3
dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrR01-B1:bd12/29/2006:svnAcer:pnASE380/AST180/APM8:pvrR01-B1:rvnAcer:rnEM61SM/EM61PM:rvr:cvn:ct3:cvr:
dmi.product.name: ASE380/AST180/APM8
dmi.product.version: R01-B1
dmi.sys.vendor: Acer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.105-3~21.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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


** Tags: amd64 apport-bug hirsute 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/1942738

Title:
  XOrg / nouveau - hard lockups and does not draw to screen

Status in xorg package in Ubuntu:
  New

Bug description:
  Changing display settings hard locks the machine (no reisub save).
  Installing nouveau-firmware allows changes to be made without hard
  lock ups but the screen using nouveau draws the mouse cursor and will
  launch apps on it but does not draw anything on screen. Dmesg is
  flooded with nouveau and XOrg failure messages.

  Description:  Ubuntu 21.04
  Release:  21.04

  xorg:
Installed: 1:7.7+22ubuntu1
Candidate: 1:7.7+22ubuntu1
Version table:
   *** 1:7.7+22ubuntu1 500
  500 http://ca.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
  100 /var/lib/dpkg/status

  nouveau-firmware:
Installed: 20091212-0ubuntu1
Candidate: 20091212-0ubuntu1
Version table:
   *** 20091212-0ubuntu1 500
  500 http://ca.archive.ubuntu.com/ubuntu hirsute/multiverse amd64 
Packag

[Touch-packages] [Bug 1942738] Re: XOrg / nouveau - hard lockups and does not draw to screen

[Daniel van Vugt]

** Tags added: nouveau radeon

** Package changed: xorg (Ubuntu) => xserver-xorg-video-nouveau (Ubuntu)

** Also affects: xserver-xorg-video-ati (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  XOrg / nouveau - hard lockups and does not draw to screen

Status in linux package in Ubuntu:
  Confirmed
Status in xserver-xorg-video-ati package in Ubuntu:
  New
Status in xserver-xorg-video-nouveau package in Ubuntu:
  New

Bug description:
  Changing display settings hard locks the machine (no reisub save).
  Installing nouveau-firmware allows changes to be made without hard
  lock ups but the screen using nouveau draws the mouse cursor and will
  launch apps on it but does not draw anything on screen. Dmesg is
  flooded with nouveau and XOrg failure messages.

  Description:  Ubuntu 21.04
  Release:  21.04

  xorg:
Installed: 1:7.7+22ubuntu1
Candidate: 1:7.7+22ubuntu1
Version table:
   *** 1:7.7+22ubuntu1 500
  500 http://ca.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
  100 /var/lib/dpkg/status

  nouveau-firmware:
Installed: 20091212-0ubuntu1
Candidate: 20091212-0ubuntu1
Version table:
   *** 20091212-0ubuntu1 500
  500 http://ca.archive.ubuntu.com/ubuntu hirsute/multiverse amd64 
Packages
  500 http://ca.archive.ubuntu.com/ubuntu hirsute/multiverse i386 
Packages
  100 /var/lib/dpkg/status

  
  xserver-xorg-video-nouveau:
Installed: 1:1.0.17-1
Candidate: 1:1.0.17-1
Version table:
   *** 1:1.0.17-1 500
  500 http://ca.archive.ubuntu.com/ubuntu hirsute/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 21.04
  Package: xorg 1:7.7+22ubuntu1
  ProcVersionSignature: Ubuntu 5.11.0-31.33-generic 5.11.22
  Uname: Linux 5.11.0-31-generic x86_64
  ApportVersion: 2.20.11-0ubuntu65.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sun Sep  5 23:52:43 2021
  DistUpgraded: Fresh install
  DistroCodename: hirsute
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 6100 nForce 405] [10de:03d1] (rev a2) 
(prog-if 00 [VGA controller])
 Subsystem: Elitegroup Computer Systems C61 [GeForce 6100 nForce 405] 
[1019:2601]
   Advanced Micro Devices, Inc. [AMD/ATI] Oland XT [Radeon HD 8670 / R7 
250/350] [1002:6610] (prog-if 00 [VGA controller])
 Subsystem: Diamond Multimedia Systems Oland XT [Radeon HD 8670 / R7 
250/350] [1092:0250]
  InstallationDate: Installed on 2021-04-07 (151 days ago)
  InstallationMedia: Xubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 04d9:a0cd Holtek Semiconductor, Inc. USB Keyboard
   Bus 002 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Acer ASE380/AST180/APM8
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-31-generic 
root=UUID=cf6234fa-9047-4e3a-8931-f8f36bce86cf ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/29/2006
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: R01-B1
  dmi.board.name: EM61SM/EM61PM
  dmi.board.vendor: Acer
  dmi.chassis.asset.tag: Asset tag number: at least 22 digits
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvrR01-B1:bd12/29/2006:svnAcer:pnASE380/AST180/APM8:pvrR01-B1:rvnAcer:rnEM61SM/EM61PM:rvr:cvn:ct3:cvr:
  dmi.product.name: ASE380/AST180/APM8
  dmi.product.version: R01-B1
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~21.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200714-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1

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