[Touch-packages] [Bug 1990089] Re: Screen freeze when performing memory stress in Wayland mode

[Andy Chi]

** Changed in: oem-priority
   Status: Incomplete => Fix Released

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

Title:
  Screen freeze when performing memory stress in Wayland mode

Status in Linux:
  New
Status in Mutter:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Jammy:
  Fix Committed
Status in mesa source package in Kinetic:
  Won't Fix
Status in mesa source package in Lunar:
  Fix Released

Bug description:
  [Impact]

  Running stress-ng freezes the screen under wayland on intel iris.
  Upstream has fixed it in

  5aae8a05264c354aa93017d323ce238858f68227 iris: Retry 
DRM_IOCTL_I915_GEM_EXECBUFFER2 on ENOMEM
  646cff13bca8a92b846984d782ef00e57d34d7a1 Revert "iris: Avoid abort() if 
kernel can't allocate memory"

  which need to be backported for 22.2.5

  [Test case]

  Install the update, then

  1. stress-ng --stack 0 --timeout 300
  2. check the screen

  and note that it shouldn't freeze anymore.

  [Where things could go wrong]

  This moves checking ENOMEM to the right place, so it's hard to see how
  it might cause issues.

  --

  [Steps to reproduce]
  (disable systemd-oomd or executing over ssh)
  (below command allocates a lot of memory to stress kernel page fault)

  1. stress-ng --stack 0 --timeout 300
  2. check the screen

  [Expected result]
  Screen will update slowly when performing the stress-test.
  but screen needs back to work after stress.

  [Actual result]
  Screen freeze after stress test.

  [Additional information]
  kernel version: vmlinuz-5.17.0-1017-oem
  kernel version: vmlinuz-6.0.0-06rc4drmtip20220910-generic
  Mesa version: 22.0.5-0ubuntu0.1
  Mutter version: 42.2-0ubuntu1
  Gnome-shell version: 42.2-0ubuntu0.2

  * Issue happens in Wayland only

  * gnome-shell keeps issuing ioctl()
  ```
  (gdb) bt
  #0  __GI___ioctl (fd=fd@entry=14, request=request@entry=3223348419) at 
../sysdeps/unix/sysv/linux/ioctl.c:36
  #1  0x7fcacab0eb4f in intel_ioctl (arg=0x7fffc5404d80, 
request=3223348419, fd=14) at ../src/intel/common/intel_gem.h:75
  #2  iris_wait_syncobj (timeout_nsec=140736502713808, syncobj=, 
bufmgr=) at ../src/gallium/drivers/iris/iris_fence.c:229
  #3  iris_wait_syncobj (bufmgr=, syncobj=, 
timeout_nsec=timeout_nsec@entry=9223372036854775807) at 
../src/gallium/drivers/iris/iris_fence.c:215
  #4  0x7fcacab8beab in iris_get_query_result (result=0x7fffc5404e50, 
wait=, query=0x55774159b800, ctx=) at 
../src/gallium/drivers/iris/iris_query.c:635
  #5  iris_get_query_result (ctx=, query=0x55774159b800, 
wait=, result=0x7fffc5404e50) at 
../src/gallium/drivers/iris/iris_query.c:601
  #6  0x7fcaca405e89 in tc_get_query_result (_pipe=, 
query=0x55774159b800, wait=, result=0x7fffc5404e50) at 
../src/gallium/auxiliary/util/u_threaded_context.c:881
  #7  0x7fcaca0f0e64 in get_query_result (pipe=pipe@entry=0x55773f87bad0, 
q=q@entry=0x557741a0c790, wait=wait@entry=1 '\001') at 
../src/mesa/main/queryobj.c:266
  #8  0x7fcaca0f1b12 in _mesa_wait_query (q=0x557741a0c790, 
ctx=0x55773f8af980) at ../src/mesa/main/queryobj.c:344
  #9  get_query_object (ctx=0x55773f8af980, func=func@entry=0x7fcacaf28283 
"glGetQueryObjecti64v", id=, pname=34918, 
ptype=ptype@entry=5134, buf=0x0, offset=140736502714192)
  at ../src/mesa/main/queryobj.c:1174
  #10 0x7fcaca0f2d65 in _mesa_GetQueryObjecti64v (id=, 
pname=, params=) at 
../src/mesa/main/queryobj.c:1257
  #11 0x7fcadfa39b90 in ?? () from 
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
  #12 0x7fcadfa751b9 in cogl_frame_info_get_rendering_duration_ns () from 
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
  #13 0x7fcadf8819c4 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
  #14 0x7fcadfa6e7a2 in _cogl_onscreen_notify_complete () from 
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
  #15 0x7fcadf969cdd in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
  #16 0x7fcadf96ec7b in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
  #17 0x7fcadf969601 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
  #18 0x7fcadf98395e in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
  #19 0x7fcadf96962d in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
  #20 0x7fcae0743c24 in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #21 0x7fcae07986f8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  #22 0x7fcae0743293 in g_main_loop_run () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #23 0x7fcadf8d0849 in meta_context_run_main_loop () from 
/lib/x86_64-linux-gnu/libmutter-10.so.0
  #24 0x55773f1a4f12 in ?? ()
  #25 0x7fcadf429d90 in __libc_start_call_main 
(main=main@entry=0x55773f1a4a70, argc=argc@entry=1, 
argv=argv@entry=0x7fffc54053e8) at 

[Touch-packages] [Bug 1990089] Re: Screen freeze when performing memory stress in Wayland mode

[Kai-Heng Feng]

I can verify the issue is fixed following the steps:
1) Enable -proposed pocket, and upgrade mesa
2) Run `stress-ng --stack 0 --mmap 0 --aggressive --timeout 300`
3) See if GNOME is frozen
4) Use top to observe CPU usage

With the new mesa, GNOME is no longer hung and there's no high CPU usage
anymore.

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

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

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

Title:
  Screen freeze when performing memory stress in Wayland mode

Status in Linux:
  New
Status in Mutter:
  Fix Released
Status in OEM Priority Project:
  Incomplete
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Jammy:
  Fix Committed
Status in mesa source package in Kinetic:
  Won't Fix
Status in mesa source package in Lunar:
  Fix Released

Bug description:
  [Impact]

  Running stress-ng freezes the screen under wayland on intel iris.
  Upstream has fixed it in

  5aae8a05264c354aa93017d323ce238858f68227 iris: Retry 
DRM_IOCTL_I915_GEM_EXECBUFFER2 on ENOMEM
  646cff13bca8a92b846984d782ef00e57d34d7a1 Revert "iris: Avoid abort() if 
kernel can't allocate memory"

  which need to be backported for 22.2.5

  [Test case]

  Install the update, then

  1. stress-ng --stack 0 --timeout 300
  2. check the screen

  and note that it shouldn't freeze anymore.

  [Where things could go wrong]

  This moves checking ENOMEM to the right place, so it's hard to see how
  it might cause issues.

  --

  [Steps to reproduce]
  (disable systemd-oomd or executing over ssh)
  (below command allocates a lot of memory to stress kernel page fault)

  1. stress-ng --stack 0 --timeout 300
  2. check the screen

  [Expected result]
  Screen will update slowly when performing the stress-test.
  but screen needs back to work after stress.

  [Actual result]
  Screen freeze after stress test.

  [Additional information]
  kernel version: vmlinuz-5.17.0-1017-oem
  kernel version: vmlinuz-6.0.0-06rc4drmtip20220910-generic
  Mesa version: 22.0.5-0ubuntu0.1
  Mutter version: 42.2-0ubuntu1
  Gnome-shell version: 42.2-0ubuntu0.2

  * Issue happens in Wayland only

  * gnome-shell keeps issuing ioctl()
  ```
  (gdb) bt
  #0  __GI___ioctl (fd=fd@entry=14, request=request@entry=3223348419) at 
../sysdeps/unix/sysv/linux/ioctl.c:36
  #1  0x7fcacab0eb4f in intel_ioctl (arg=0x7fffc5404d80, 
request=3223348419, fd=14) at ../src/intel/common/intel_gem.h:75
  #2  iris_wait_syncobj (timeout_nsec=140736502713808, syncobj=, 
bufmgr=) at ../src/gallium/drivers/iris/iris_fence.c:229
  #3  iris_wait_syncobj (bufmgr=, syncobj=, 
timeout_nsec=timeout_nsec@entry=9223372036854775807) at 
../src/gallium/drivers/iris/iris_fence.c:215
  #4  0x7fcacab8beab in iris_get_query_result (result=0x7fffc5404e50, 
wait=, query=0x55774159b800, ctx=) at 
../src/gallium/drivers/iris/iris_query.c:635
  #5  iris_get_query_result (ctx=, query=0x55774159b800, 
wait=, result=0x7fffc5404e50) at 
../src/gallium/drivers/iris/iris_query.c:601
  #6  0x7fcaca405e89 in tc_get_query_result (_pipe=, 
query=0x55774159b800, wait=, result=0x7fffc5404e50) at 
../src/gallium/auxiliary/util/u_threaded_context.c:881
  #7  0x7fcaca0f0e64 in get_query_result (pipe=pipe@entry=0x55773f87bad0, 
q=q@entry=0x557741a0c790, wait=wait@entry=1 '\001') at 
../src/mesa/main/queryobj.c:266
  #8  0x7fcaca0f1b12 in _mesa_wait_query (q=0x557741a0c790, 
ctx=0x55773f8af980) at ../src/mesa/main/queryobj.c:344
  #9  get_query_object (ctx=0x55773f8af980, func=func@entry=0x7fcacaf28283 
"glGetQueryObjecti64v", id=, pname=34918, 
ptype=ptype@entry=5134, buf=0x0, offset=140736502714192)
  at ../src/mesa/main/queryobj.c:1174
  #10 0x7fcaca0f2d65 in _mesa_GetQueryObjecti64v (id=, 
pname=, params=) at 
../src/mesa/main/queryobj.c:1257
  #11 0x7fcadfa39b90 in ?? () from 
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
  #12 0x7fcadfa751b9 in cogl_frame_info_get_rendering_duration_ns () from 
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
  #13 0x7fcadf8819c4 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
  #14 0x7fcadfa6e7a2 in _cogl_onscreen_notify_complete () from 
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
  #15 0x7fcadf969cdd in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
  #16 0x7fcadf96ec7b in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
  #17 0x7fcadf969601 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
  #18 0x7fcadf98395e in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
  #19 0x7fcadf96962d in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
  #20 0x7fcae0743c24 in g_main_context_dispatch () from 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
  #21 0x7fcae07986f8 in ?? () from 

[Touch-packages] [Bug 1958019]

[thomas.gfeller+kernel]

(In reply to Thomas Gfeller from comment #761)
> Created attachment 304265 [details]
> journalctl on a 83BU Yoga Pro 9 14IRP8

I have the same issue on a 83BU Yoga Pro 9 14IRP8. I can see some lines
that look suspicious in the logs:

skl_hda_dsp_generic skl_hda_dsp_generic: ASoC: Parent card not yet
available, widget card binding deferred

I'm running Fedora 38 with 6.2.15-300.fc38.x86_64.

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

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

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

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

  uname -r
  5.11.0-44-generic

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions


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

[Touch-packages] [Bug 1991606] Re: Invalid PEP440 package version breaking setuptools >= 66

[Martin Pecka]

There is downstream software depending on python3-packaging to work
correctly. That library is affected, too, because it checks for strict
compliance to PEP 440. And, obviously, it can't be fixed by fixing the
packaging library, as it does its work correctly.

Example downstream usage: https://github.com/ros-
infrastructure/rosdep/pull/909 .

Would this be enough to support an SRU for all projects with wrong
version strings in bionic and the other releases?

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

Title:
  Invalid PEP440 package version breaking setuptools >= 66

Status in devscripts package in Ubuntu:
  Fix Released
Status in distro-info package in Ubuntu:
  Fix Released
Status in drslib package in Ubuntu:
  New
Status in duecredit package in Ubuntu:
  Fix Released
Status in gpgme1.0 package in Ubuntu:
  New
Status in python-debian package in Ubuntu:
  Fix Released
Status in reportbug package in Ubuntu:
  Fix Released
Status in ubuntu-dev-tools package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in devscripts source package in Bionic:
  New
Status in distro-info source package in Bionic:
  New
Status in drslib source package in Bionic:
  Invalid
Status in duecredit source package in Bionic:
  New
Status in gpgme1.0 source package in Bionic:
  New
Status in python-debian source package in Bionic:
  Invalid
Status in reportbug source package in Bionic:
  New
Status in ubuntu-dev-tools source package in Bionic:
  New
Status in update-manager source package in Bionic:
  New
Status in devscripts source package in Focal:
  New
Status in distro-info source package in Focal:
  New
Status in drslib source package in Focal:
  New
Status in duecredit source package in Focal:
  New
Status in gpgme1.0 source package in Focal:
  New
Status in python-debian source package in Focal:
  New
Status in reportbug source package in Focal:
  New
Status in ubuntu-dev-tools source package in Focal:
  New
Status in update-manager source package in Focal:
  New
Status in devscripts source package in Jammy:
  New
Status in distro-info source package in Jammy:
  New
Status in drslib source package in Jammy:
  New
Status in duecredit source package in Jammy:
  New
Status in gpgme1.0 source package in Jammy:
  New
Status in python-debian source package in Jammy:
  New
Status in reportbug source package in Jammy:
  New
Status in ubuntu-dev-tools source package in Jammy:
  Invalid
Status in update-manager source package in Jammy:
  New
Status in devscripts source package in Kinetic:
  New
Status in distro-info source package in Kinetic:
  Fix Released
Status in drslib source package in Kinetic:
  New
Status in duecredit source package in Kinetic:
  New
Status in gpgme1.0 source package in Kinetic:
  New
Status in python-debian source package in Kinetic:
  Invalid
Status in reportbug source package in Kinetic:
  New
Status in ubuntu-dev-tools source package in Kinetic:
  Invalid
Status in update-manager source package in Kinetic:
  New

Bug description:
  [ Impact ]

  With setuptools 66, the versions of all packages visible in the Python
  environment *must* obey PEP440 .
  Otherwise, attempts to use pip to install a package with a setup.py-
  based build system, or other attempts to use the `pkg-resources`
  module, can produce errors like this:

    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 844, in _resolve_dist
  env = Environment(self.entries)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1044, in __init__
  self.scan(search_path)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1077, in scan
  self.add(dist)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1096, in add
  dists.sort(key=operator.attrgetter('hashcmp'), reverse=True)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2631, in hashcmp
  self.parsed_version,
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2678, in parsed_version
  self._parsed_version = parse_version(self.version)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/_vendor/packaging/version.py",
 line 266, in __init__
  raise InvalidVersion(f"Invalid version: '{version}'")
  pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: 
'0.23ubuntu1'

  The official opinion of the setuptools maintainers seems to be that
  version strings of this form haven't *really* been allowed since about
  2014, and distributions need to change their package version naming
  scheme for Python 

[Touch-packages] [Bug 1958019]

[thomas.gfeller+kernel]

Created attachment 304265
journalctl on a 83BU Yoga Pro 9 14IRP8

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

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

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

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

  uname -r
  5.11.0-44-generic

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1958019/+subscriptions


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

[Touch-packages] [Bug 1991606] Re: Invalid PEP440 package version breaking setuptools >= 66

[Steve Langasek]

You're right, python3-setuptools is in bionic, I was looking at the
setuptools source package which is not in bionic. python3-setuptools in
bionic comes from the 'python-setuptools' source package instead.

In any event, this issue should not affect the python3-setuptools 39.0.1
shipped as part of the bionic release; it is only reported to affect
setuptools 66.

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

Title:
  Invalid PEP440 package version breaking setuptools >= 66

Status in devscripts package in Ubuntu:
  Fix Released
Status in distro-info package in Ubuntu:
  Fix Released
Status in drslib package in Ubuntu:
  New
Status in duecredit package in Ubuntu:
  Fix Released
Status in gpgme1.0 package in Ubuntu:
  New
Status in python-debian package in Ubuntu:
  Fix Released
Status in reportbug package in Ubuntu:
  Fix Released
Status in ubuntu-dev-tools package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in devscripts source package in Bionic:
  New
Status in distro-info source package in Bionic:
  New
Status in drslib source package in Bionic:
  Invalid
Status in duecredit source package in Bionic:
  New
Status in gpgme1.0 source package in Bionic:
  New
Status in python-debian source package in Bionic:
  Invalid
Status in reportbug source package in Bionic:
  New
Status in ubuntu-dev-tools source package in Bionic:
  New
Status in update-manager source package in Bionic:
  New
Status in devscripts source package in Focal:
  New
Status in distro-info source package in Focal:
  New
Status in drslib source package in Focal:
  New
Status in duecredit source package in Focal:
  New
Status in gpgme1.0 source package in Focal:
  New
Status in python-debian source package in Focal:
  New
Status in reportbug source package in Focal:
  New
Status in ubuntu-dev-tools source package in Focal:
  New
Status in update-manager source package in Focal:
  New
Status in devscripts source package in Jammy:
  New
Status in distro-info source package in Jammy:
  New
Status in drslib source package in Jammy:
  New
Status in duecredit source package in Jammy:
  New
Status in gpgme1.0 source package in Jammy:
  New
Status in python-debian source package in Jammy:
  New
Status in reportbug source package in Jammy:
  New
Status in ubuntu-dev-tools source package in Jammy:
  Invalid
Status in update-manager source package in Jammy:
  New
Status in devscripts source package in Kinetic:
  New
Status in distro-info source package in Kinetic:
  Fix Released
Status in drslib source package in Kinetic:
  New
Status in duecredit source package in Kinetic:
  New
Status in gpgme1.0 source package in Kinetic:
  New
Status in python-debian source package in Kinetic:
  Invalid
Status in reportbug source package in Kinetic:
  New
Status in ubuntu-dev-tools source package in Kinetic:
  Invalid
Status in update-manager source package in Kinetic:
  New

Bug description:
  [ Impact ]

  With setuptools 66, the versions of all packages visible in the Python
  environment *must* obey PEP440 .
  Otherwise, attempts to use pip to install a package with a setup.py-
  based build system, or other attempts to use the `pkg-resources`
  module, can produce errors like this:

    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 844, in _resolve_dist
  env = Environment(self.entries)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1044, in __init__
  self.scan(search_path)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1077, in scan
  self.add(dist)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1096, in add
  dists.sort(key=operator.attrgetter('hashcmp'), reverse=True)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2631, in hashcmp
  self.parsed_version,
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2678, in parsed_version
  self._parsed_version = parse_version(self.version)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/_vendor/packaging/version.py",
 line 266, in __init__
  raise InvalidVersion(f"Invalid version: '{version}'")
  pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: 
'0.23ubuntu1'

  The official opinion of the setuptools maintainers seems to be that
  version strings of this form haven't *really* been allowed since about
  2014, and distributions need to change their package version naming
  scheme for Python packages they install, so that the resulting version
  strings obey PEP440. See for example
  

[Touch-packages] [Bug 1991606] Re: Invalid PEP440 package version breaking setuptools >= 66

[Martin Pecka]

> Setuptools is not in bionic

I don't understand. I clearly see it there:
https://webcache.googleusercontent.com/search?q=cache:fZGhFT_sSb8J:https://packages.ubuntu.com/bionic/python-
setuptools . Or am I missing something?

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

Title:
  Invalid PEP440 package version breaking setuptools >= 66

Status in devscripts package in Ubuntu:
  Fix Released
Status in distro-info package in Ubuntu:
  Fix Released
Status in drslib package in Ubuntu:
  New
Status in duecredit package in Ubuntu:
  Fix Released
Status in gpgme1.0 package in Ubuntu:
  New
Status in python-debian package in Ubuntu:
  Fix Released
Status in reportbug package in Ubuntu:
  Fix Released
Status in ubuntu-dev-tools package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in devscripts source package in Bionic:
  New
Status in distro-info source package in Bionic:
  New
Status in drslib source package in Bionic:
  Invalid
Status in duecredit source package in Bionic:
  New
Status in gpgme1.0 source package in Bionic:
  New
Status in python-debian source package in Bionic:
  Invalid
Status in reportbug source package in Bionic:
  New
Status in ubuntu-dev-tools source package in Bionic:
  New
Status in update-manager source package in Bionic:
  New
Status in devscripts source package in Focal:
  New
Status in distro-info source package in Focal:
  New
Status in drslib source package in Focal:
  New
Status in duecredit source package in Focal:
  New
Status in gpgme1.0 source package in Focal:
  New
Status in python-debian source package in Focal:
  New
Status in reportbug source package in Focal:
  New
Status in ubuntu-dev-tools source package in Focal:
  New
Status in update-manager source package in Focal:
  New
Status in devscripts source package in Jammy:
  New
Status in distro-info source package in Jammy:
  New
Status in drslib source package in Jammy:
  New
Status in duecredit source package in Jammy:
  New
Status in gpgme1.0 source package in Jammy:
  New
Status in python-debian source package in Jammy:
  New
Status in reportbug source package in Jammy:
  New
Status in ubuntu-dev-tools source package in Jammy:
  Invalid
Status in update-manager source package in Jammy:
  New
Status in devscripts source package in Kinetic:
  New
Status in distro-info source package in Kinetic:
  Fix Released
Status in drslib source package in Kinetic:
  New
Status in duecredit source package in Kinetic:
  New
Status in gpgme1.0 source package in Kinetic:
  New
Status in python-debian source package in Kinetic:
  Invalid
Status in reportbug source package in Kinetic:
  New
Status in ubuntu-dev-tools source package in Kinetic:
  Invalid
Status in update-manager source package in Kinetic:
  New

Bug description:
  [ Impact ]

  With setuptools 66, the versions of all packages visible in the Python
  environment *must* obey PEP440 .
  Otherwise, attempts to use pip to install a package with a setup.py-
  based build system, or other attempts to use the `pkg-resources`
  module, can produce errors like this:

    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 844, in _resolve_dist
  env = Environment(self.entries)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1044, in __init__
  self.scan(search_path)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1077, in scan
  self.add(dist)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1096, in add
  dists.sort(key=operator.attrgetter('hashcmp'), reverse=True)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2631, in hashcmp
  self.parsed_version,
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2678, in parsed_version
  self._parsed_version = parse_version(self.version)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/_vendor/packaging/version.py",
 line 266, in __init__
  raise InvalidVersion(f"Invalid version: '{version}'")
  pkg_resources.extern.packaging.version.InvalidVersion: Invalid version: 
'0.23ubuntu1'

  The official opinion of the setuptools maintainers seems to be that
  version strings of this form haven't *really* been allowed since about
  2014, and distributions need to change their package version naming
  scheme for Python packages they install, so that the resulting version
  strings obey PEP440. See for example
  .

  suffix 1build1 is invalid.

  Some python building tools, that 

[Touch-packages] [Bug 1349945] Re: Dialog doesn't fit Page

[carlostipton1319]

if a dialog doesn't fit the page, meaning it extends beyond the visible
area, you can try the following steps:

Resize the dialog: If possible, try manually resizing the dialog window by 
dragging its edges or corners. This can help make the content fit within the 
visible area of the page.
https://theweddingguides.com/
Maximize or fullscreen the window: If the dialog has a maximize or fullscreen 
option, click on it to expand the window to its maximum size. This can provide 
more space for the dialog's content and ensure it fits within the page.

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

Title:
  Dialog doesn't fit Page

Status in ubuntu-ui-toolkit package in Ubuntu:
  Incomplete
Status in ubuntu-ui-toolkit package in Ubuntu RTM:
  New

Bug description:
  Sometimes Dialog doesn't fit Page, see screenshot
  https://yadi.sk/i/7wUC4aCAYMXvp
  In that Page there are 2 views - ListView and GridView. When ListView is 
used, Page's "flickable" is set to that ListView. When GridView is used, Page's 
"flickable" is set to null. At that moment bug appears. 

  Toolkit v14.10-dev2
  Doesn't appear on Desktop 14.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-ui-toolkit/+bug/1349945/+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 1003842] Re: dnsmasq sometimes fails to resolve private names in networks with non-equivalent nameservers

[carlostipton1319]

when using dnsmasq, you may encounter situations where it fails to
resolve private names in networks with non-equivalent nameservers. This
can happen when the nameservers configured for your network do not have
the necessary information to resolve the private names.

To troubleshoot this issue, you can try the following steps:

Verify DNS configuration: Double-check your network's DNS configuration
settings. Ensure that the nameservers specified in the configuration
have the ability to resolve private names. If needed, update the DNS
configuration to include appropriate nameservers.

Check firewall settings: If you have a firewall in place, ensure that it is not 
blocking the necessary DNS traffic. Adjust the firewall rules to allow DNS 
queries and responses to flow smoothly between your network and the nameservers.
https://home-decoration-ideas.com/what-forms-do-i-need-to-become-a-licensed-garage-door-repair-in-highland-springs/
Configure dnsmasq options: Review the configuration options for dnsmasq. Ensure 
that it is properly configured to use the correct nameservers for resolving 
private names. Check for any specific settings related to resolving private 
names and adjust them if necessary.

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

Title:
  dnsmasq sometimes fails to resolve private names in networks with non-
  equivalent nameservers

Status in dnsmasq package in Ubuntu:
  Triaged
Status in network-manager package in Ubuntu:
  Invalid
Status in dnsmasq source package in Precise:
  Won't Fix
Status in network-manager source package in Precise:
  Won't Fix
Status in dnsmasq package in Debian:
  New

Bug description:
  A number of reports already filed against network-manager seem to
  reflect this problem, but to make things very clear I am opening a new
  report.  Where appropriate I will mark other reports as duplicates of
  this one.

  Consider a pre-Precise system with the following /etc/resolv.conf:

  nameserver 192.168.0.1
  nameserver 8.8.8.8

  The first address is the address of a nameserver on the LAN that can
  resolve both private and public domain names.  The second address is
  the address of a nameserver on the Internet that can resolve only
  public names.

  This setup works fine because the GNU resolver always tries the first-
  listed address first.

  Now the administrator upgrades to Precise and instead of writing the
  above to resolv.conf, NetworkManager writes

  server=192.168.0.1
  server=8.8.8.8

  to /var/run/nm-dns-dnsmasq.conf and "nameserver 127.0.0.1" to
  resolv.conf.  Resolution of private domain names is now broken because
  dnsmasq treats the two upstream nameservers as equals and uses the
  faster one, which could be 8.8.8.8.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1003842/+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 1300722] Re: hud-service is eating up 100% of one of my CPUs in a poll loop

[carlostipton1319]

if the hud-service is consuming 100% of one of your CPUs in a poll
loop, it could indicate an issue with the service or its configuration.
Here are a few steps you can try to address the problem:

Restart the hud-service: Restarting the hud-service can help resolve
temporary issues. You can do this by finding the appropriate command for
your operating system and executing it. For example, on Linux, you can
try "sudo systemctl restart hud-service".

Check for updates: Ensure that your system is running the latest version
of the hud-service. Updates often include bug fixes and performance
improvements. Update the service if a newer version is available.

Investigate system logs: Check the system logs for any error messages or 
warnings related to the hud-service. Logs can provide insights into the 
underlying cause of the high CPU usage. Review the logs to identify any 
specific errors or issues and take appropriate actions.
https://beautyhomedesigns.com/diy-garage-door-repair-how-to-safely-fix-common-problems/
Disable or reconfigure hud-service: If the high CPU usage persists, you can try 
disabling or reconfiguring the hud-service. Refer to the documentation or 
community resources for your specific operating system to learn how to disable 
or adjust the service's settings.

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

Title:
  hud-service is eating up 100% of one of my CPUs in a poll loop

Status in Unity HUD:
  New
Status in unbuntu-fr Scripts - apt:
  Fix Committed
Status in hud package in Ubuntu:
  Incomplete

Bug description:
  hud-service is polling like crazy:

  Context Switches:
PID  ProcessVoluntary   Involuntary Total
   Ctxt Sw/Sec  Ctxt Sw/Sec  Ctxt Sw/Sec
2295 hud-service  46084.6342.94 46127.58 (very high)
2325 hud-service  0.09 0.00 0.09 (very low)
2329 hud-service  0.07 0.00 0.07 (very low)
2340 hud-service  0.05 0.00 0.05 (very low)
   Total  46084.8442.94 46127.78

  File I/O operations:
   No file I/O operations detected.

  System calls traced:
PID  Process  Syscall   CountRate/Sec
2295 hud-service  poll 83   23124.8503
2295 hud-service  write10   0.2313
2295 hud-service  sendmsg   4   0.0925
2325 hud-service  restart_syscall   1   0.0231
2329 hud-service  restart_syscall   1   0.0231
2340 hud-service  restart_syscall   1   0.0231
   Total  100   23125.2435

  (gdb) where
  #0  0x7fda8121cfbd in poll () at ../sysdeps/unix/syscall-template.S:81
  #1  0x7fda7f1bb4b8 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
  #2  0x7fda7f1ba3ff in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
  #3  0x7fda7f1a49dc in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
  #4  0x7fda7f1a5464 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
  #5  0x7fda82ce9e65 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
  #6  0x7fda82d2fc64 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
  #7  0x7fda82d30582 in QDBusPendingCallWatcher::waitForFinished() () from 
/usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
  #8  0x7fda83eb940b in DBusMenuImporter::slotMenuAboutToShow() () from 
/usr/lib/x86_64-linux-gnu/libdbusmenu-qt5.so.2
  #9  0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) 
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #10 0x0045ab3f in hud::service::DBusMenuCollector::openMenu(QMenu*, 
unsigned int&) ()
  #11 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, 
unsigned int&) ()
  #12 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, 
unsigned int&) ()
  #13 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, 
unsigned int&) ()
  #14 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, 
unsigned int&) ()
  #15 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, 
unsigned int&) ()
  #16 0x0045ae8d in hud::service::DBusMenuCollector::activate() ()
  #17 0x00441e43 in hud::service::WindowImpl::activate() ()
  #18 0x00439f6a in 
hud::service::QueryImpl::updateToken(QSharedPointer) ()
  #19 0x0043a672 in hud::service::QueryImpl::refresh() ()
  #20 0x0044b115 in ?? ()
  #21 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) 
() from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
  #22 0x0045662a in 
hud::service::ApplicationListImpl::FocusedWindowChanged(unsigned int, 

[Touch-packages] [Bug 1083565] Re: avahi malfunctions on a machine connected to the network via multiple interfaces

[carlostipton1319]

if Avahi malfunctions on a machine connected to the network via multiple
interfaces, it can cause issues with service discovery and hostname
resolution. Here are a few steps you can try to troubleshoot the
problem:

Check network connectivity: Ensure that all network interfaces are properly 
connected and have a valid IP configuration. Verify that you can access other 
devices on the network and that there are no general connectivity issues.
https://homecleaningblog.com/preparing-your-home-for-garage-door-repairs/
Restart Avahi service: Restart the Avahi service on the machine. This can help 
refresh its configuration and resolve any temporary issues. You can do this by 
running the appropriate command for your operating system, such as "sudo 
systemctl restart avahi-daemon" on Linux.

Verify Avahi configuration: Review the Avahi configuration file
(/etc/avahi/avahi-daemon.conf) and check for any misconfigurations or
conflicts. Pay attention to settings related to interfaces and network
discovery. Make sure that all relevant interfaces are enabled for Avahi
service.

Check firewall settings: Ensure that the firewall on the machine is not
blocking Avahi traffic. Avahi uses specific ports and protocols for
service discovery. Adjust the firewall rules to allow Avahi traffic to
pass through.

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

Title:
  avahi malfunctions on a machine connected to the network via multiple
  interfaces

Status in avahi package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I have a router making up one local NAT network connected to the
  internet. The router allows to connect both wired and wireless. My
  laptops are configured to use both wired and wireless. So I can walk
  around with them and also connect to the quicker wired network if they
  are on the desk.

  Problem is that when the laptops are on my desk and I plug in the
  network cables they stay connected on wireless and so they get
  connected twice, wired and wireless, with two IP addresses, appearing
  as two computers for the router and all other computers in the
  network. Most things still simply work, like accessing the internet
  from the laptops, SSHing to another computer, ... what causes problems
  is Bonjour/mDNS. Avahi broadcasts available services (I have shared
  CUPS printers on the laptops) into the network, using the host name of
  the machine assigned on installation, for example "till-lenovo". As
  the broadcasts go through two interfaces there is a service name
  conflict and it seems that Avahi tries to overcome it by using host
  names like "till-lenovo-1", "till-lenovo-2", ... When the laptop keeps
  running one sees in the "avahi-discover" output on another machine the
  entries from the laptop, but with host names (and so the service
  names) changing from time to time. This leads to a client with a print
  queue pointing to a printer shared by the laptop via the printer's
  Bonjour service name cannot print any more.

  I have done a short test and Avahi stops adding numbers to the
  original host name when turning off wireless on the laptop so that it
  connects only through the wired network.

  One way of fixing (or working around?) the problem would be a change
  in network-manager to automatically turn off wireless if the computer
  is connected to a wired network and switching wireless back on when
  the network cable gets disconnected. This would probably also solve
  problems with other server functionality. --->> http://somapills.net

  Another solution would be a change in Avahi, somehow recognizing that
  the broadcasts through the two interfaces come from the same computer
  and so they can (and should) have the same service names, or
  recognizing that the two interfaces go into the same network and
  therefore broadcast only through one of them, stopping the
  broadcasting through the weaker one (the wireless in our case).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1083565/+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 1992454] Autopkgtest regression report (iptables/1.8.7-1ubuntu6.1)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted iptables (1.8.7-1ubuntu6.1) for kinetic 
have finished running.
The following regressions have been reported in tests triggered by the package:

nova/3:26.1.0-0ubuntu2.1 (armhf)
west-chamber/20100405+svn2007.r124-14 (i386)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/kinetic/update_excuses.html#iptables

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  iptables: segfault when renaming a chain

Status in iptables package in Ubuntu:
  Fix Released
Status in iptables source package in Bionic:
  Fix Committed
Status in iptables source package in Focal:
  Fix Committed
Status in iptables source package in Jammy:
  Fix Committed
Status in iptables source package in Kinetic:
  Fix Committed

Bug description:
  [ Impact ]
   * An explanation of the effects of the bug on users

  This is the description for the upstream fix of this bug[1] :

  This is an odd bug: If the number of chains is right and one renames the
  last one in the list, libiptc dereferences a NULL pointer.

   * justification for backporting the fix to the stable release.
  Without this patch, users may experience segmentation fault when using
  the following versions of iptables :

    - Bionic : iptables
    - Focal  : iptables
    - Jammy  : iptables-legacy
    - Kinetic: iptables-legacy

   * In addition, it is helpful, but not required, to include an
     explanation of how the upload fixes this bug.

  The upstream fix adjust the size of the chain_index if the element is the
  last chain in the list.

  [1]
  
http://git.netfilter.org/iptables/commit/?id=97bf4e68fc0794adba3243fd96f40f4568e7216f

  [ Test Plan ]

   * detailed instructions how to reproduce the bug

   The following code (adapted from the upstream commit to work on Kinetic) may 
be used to reproduce the issue :
  8<
  #!/bin/bash
  #
  # Cover for a bug in libiptc:
  # - the chain 'node-98-tmp' is the last in the list sorted by name
  # - there are 81 chains in total, so three chain index buckets
  # - the last index bucket contains only the 'node-98-tmp' chain
  # => rename temporarily removes it from the bucket, leaving a NULL bucket
  # behind which is dereferenced later when inserting the chain again with new
  # name again

  (
   echo "*filter"
   for chain in node-1 node-10 node-101 node-102 node-104 node-107 node-11 
node-12 node-13 node-14 node-15 node-16 node-17 node-18 node-19 node-2 node-20 
node-21 node-22 node-23 node-25 node-26 node-27 node-28 node-29 node-3 node-30 
node-31 node-32 node-33 node-34 node-36 node-37 node-39 node-4 node-40 node-41 
node-42 node-43 node-44 node-45 node-46 node-47 node-48 node-49 node-5 node-50 
node-51 node-53 node-54 node-55 node-56 node-57 node-58 node-59 node-6 node-60 
node-61 node-62 node-63 node-64 node-65 node-66 node-68 node-69 node-7 node-70 
node-71 node-74 node-75 node-76 node-8 node-80 node-81 node-86 node-89 node-9 
node-92 node-93 node-95 node-98-tmp; do
    echo ":$chain - [0:0]"
   done
   echo "COMMIT"
  ) | $XT_MULTI iptables-legacy-restore
  $XT_MULTI iptables-legacy -E node-98-tmp node-98
  exit $?
  >8

  Alternatively, this test has been added to the DEP8 list of tests, and
  will be executed automatically once the package is accepted into
  proposed. The DEP8 logs can be inspected for its run. Look for a test
  named "0006rename-segfault".

  [ Where problems could occur ]

  For Jammy and onward, only users of the -legacy commands may be affected.
  Since Jammy, iptables uses the new nft libraries which are not affected
  by the bug.

  For Bionic and Focal users, the regular iptables command is affected by
  the change.

  As stated in the manpage :
  E, --rename-chain old-chain new-chain
    Rename the user specified chain to the user supplied name.  
This is cosmetic, and has no effect on the structure of the table.

  In case of a problem, only the modification of the name would be affected
  as this is clearly outlined as a cosmetic only change.

  [ Other Info ]
  The patch is also applied to lunar and mantic, but is fixed in upstream's 
1.8.9 release which so far is only in debian testing/unstable.

  This is being uploaded together with test fixes from bug #1992454
  (bionic-specific) and bug #2019023 (focal-specific), which were found
  and fixed while trying out the DEP8 runs for this package.

To manage notifications about this bug go to:

[Touch-packages] [Bug 2019745] Re: problem closing a window on the desktop

[Ubuntu Foundations Team Bug Bot]

** Package changed: ubuntu => xorg (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/2019745

Title:
  problem closing a window on the desktop

Status in xorg package in Ubuntu:
  New

Bug description:
  If I fully open my Firefox or any program and then I want to close it
  nothing happens.You have to drag the window from the title bar
  downwards and move it away from the top of the screen. Any app that's
  fully open has the same problem. Only happens since I upgraded. I am
  using dual screen and this happens on the screen on the first line.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: unknown
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 15 19:05:39 2023
  DistUpgraded: Fresh install
  DistroCodename: lunar
  DistroVariant: ubuntu
  DkmsStatus: nvidia/390.157, 6.2.0-20-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [Radeon Vega Series / Radeon 
Vega Mobile Series] [1002:1638] (rev c9) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Cezanne [Radeon Vega Series / 
Radeon Vega Mobile Series] [1458:d000]
  InstallationDate: Installed on 2020-05-19 (1091 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Gigabyte Technology Co., Ltd. B550 AORUS ELITE V2
  ProcEnviron:
   LANG=en_ZA.UTF-8
   LANGUAGE=en_ZA:en
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-20-generic 
root=UUID=7ccfa3c6-7f5e-43fc-8097-6169b339d161 ro ...security=apparmor 
apparmor=1...
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/04/2022
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: F14
  dmi.board.asset.tag: Default string
  dmi.board.name: B550 AORUS ELITE V2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF14:bd01/04/2022:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnB550AORUSELITEV2:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB550AORUSELITEV2:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
  dmi.product.family: B550 MB
  dmi.product.name: B550 AORUS ELITE V2
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.14.2+22.10.20220822-0ubuntu3
  version.libdrm2: libdrm2 2.4.114-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.2-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2019745/+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 2018457] Re: [SRU] Enable support for Bobcat Cloud Archive

[Corey Bryant]

Verified successfully:

root@j1:~# sudo add-apt-repository cloud-archive:bobcat
root@j1:~# sudo add-apt-repository cloud-archive:bobcat-proposed
root@j1:~# apt policy python3-openstackclient
python3-openstackclient:
  Installed: (none)
  Candidate: 6.2.0-0ubuntu1~cloud0
  Version table:
 6.2.0-0ubuntu1~cloud0 500
500 http://ubuntu-cloud.archive.canonical.com/ubuntu 
jammy-updates/bobcat/main amd64 Packages
500 http://ubuntu-cloud.archive.canonical.com/ubuntu 
jammy-proposed/bobcat/main amd64 Packages
 5.8.0-0ubuntu1 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages

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

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

Title:
   [SRU] Enable support for Bobcat Cloud Archive

Status in software-properties package in Ubuntu:
  Fix Released
Status in software-properties source package in Jammy:
  Fix Committed
Status in software-properties source package in Mantic:
  Fix Released

Bug description:
  Please add support for:

 cloud-archive:bobcat
 cloud-archive:bobcat-proposed

  This will also need to be SRU'd back to jammy.

  [Impact]
  End users have to manually enable the antelope cloud archive pockets.

  [Test case]
  sudo add-apt-repository cloud-archive:bobcat
  sudo add-apt-repository cloud-archive:bobcat-proposed

  [Regression potential]
  Limited - just a data item addition

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2018457/+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 2017999] Re: tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency

[Benjamin Drung]

tzdata 2023c-0ubuntu0.20.04.2 debdiff for focal.

** Patch added: "tzdata_2023c-0ubuntu0.20.04.2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2017999/+attachment/5673240/+files/tzdata_2023c-0ubuntu0.20.04.2.debdiff

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

Title:
  tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency

Status in python-tz package in Ubuntu:
  Fix Released
Status in tzdata package in Ubuntu:
  Fix Released
Status in python-tz source package in Focal:
  New
Status in tzdata source package in Focal:
  New
Status in python-tz source package in Jammy:
  New
Status in tzdata source package in Jammy:
  New
Status in python-tz source package in Kinetic:
  New
Status in tzdata source package in Kinetic:
  New
Status in python-tz source package in Lunar:
  Fix Committed
Status in tzdata source package in Lunar:
  New

Bug description:
  [ Impact ]

  Recent updates have been using `PACKRATDATA=backzone` in order to add
  all out-of-scope lower-quality pre-1970 data back that existed in
  earlier tzadata releases (see bug #2003797). However it also leads to
  time zones like America/Ensenada, Atlantic/Jan_Mayen, Europe/Tiraspol,
  and Pacific/Enderbury to change:

  compared to 2023c-0ubuntu0.22.04.0
  - America/Ensenada->only dst changes until 2022 are shown
  - Atlantic/Jan_Mayen->now valid data is shown
  - Europe/Tiraspol->only dst changes until 2010 are shown

  [ Test Plan ]

  Add an autopkgtest test case for post-1970 symlink consistency: Check
  that the timezones for today and in half a year (= to cover DST
  changes) do not change compared to building them without
  `PACKRATDATA=backzone`.

  The mentioned timezones that differed can also be tested manually.
  Running following commands should have the same output (the output
  mentioned here is from tzdata 2023c-0ubuntu0.22.04.1):

  ```
  $ TZ=America/Ensenada date -d "2023-04-28 13:49 Z"
  Fri Apr 28 05:49:00 PST 2023
  $ TZ=Atlantic/Jan_Mayen date -d "2023-04-28 13:49 Z"
  Fri Apr 28 12:49:00 -01 2023
  $ TZ=Europe/Tiraspol date -d "2023-04-28 13:49 Z"
  Fri Apr 28 16:49:00 MSK 2023
  ```

  [ Where problems could occur ]

  Timezone data could be wrong. Systems with incorrect timezone set may
  observe unexpected time shift when updating the package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-tz/+bug/2017999/+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 2017999] Re: tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency

[Benjamin Drung]

tzdata 2023c-0ubuntu0.22.04.2 debdiff for jammy.

** Patch added: "tzdata_2023c-0ubuntu0.22.04.2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2017999/+attachment/5673216/+files/tzdata_2023c-0ubuntu0.22.04.2.debdiff

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

Title:
  tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency

Status in python-tz package in Ubuntu:
  Fix Released
Status in tzdata package in Ubuntu:
  Fix Released
Status in python-tz source package in Focal:
  New
Status in tzdata source package in Focal:
  New
Status in python-tz source package in Jammy:
  New
Status in tzdata source package in Jammy:
  New
Status in python-tz source package in Kinetic:
  New
Status in tzdata source package in Kinetic:
  New
Status in python-tz source package in Lunar:
  Fix Committed
Status in tzdata source package in Lunar:
  New

Bug description:
  [ Impact ]

  Recent updates have been using `PACKRATDATA=backzone` in order to add
  all out-of-scope lower-quality pre-1970 data back that existed in
  earlier tzadata releases (see bug #2003797). However it also leads to
  time zones like America/Ensenada, Atlantic/Jan_Mayen, Europe/Tiraspol,
  and Pacific/Enderbury to change:

  compared to 2023c-0ubuntu0.22.04.0
  - America/Ensenada->only dst changes until 2022 are shown
  - Atlantic/Jan_Mayen->now valid data is shown
  - Europe/Tiraspol->only dst changes until 2010 are shown

  [ Test Plan ]

  Add an autopkgtest test case for post-1970 symlink consistency: Check
  that the timezones for today and in half a year (= to cover DST
  changes) do not change compared to building them without
  `PACKRATDATA=backzone`.

  The mentioned timezones that differed can also be tested manually.
  Running following commands should have the same output (the output
  mentioned here is from tzdata 2023c-0ubuntu0.22.04.1):

  ```
  $ TZ=America/Ensenada date -d "2023-04-28 13:49 Z"
  Fri Apr 28 05:49:00 PST 2023
  $ TZ=Atlantic/Jan_Mayen date -d "2023-04-28 13:49 Z"
  Fri Apr 28 12:49:00 -01 2023
  $ TZ=Europe/Tiraspol date -d "2023-04-28 13:49 Z"
  Fri Apr 28 16:49:00 MSK 2023
  ```

  [ Where problems could occur ]

  Timezone data could be wrong. Systems with incorrect timezone set may
  observe unexpected time shift when updating the package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-tz/+bug/2017999/+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 2019722] Re: ubuntu-minimal: please change Depends on isc-dhcp-client to | dhcp-client

[Jeremy Bícha]

Thank you for following up.

It looks like Ubuntu plans to switch ubuntu-minimal from isc-dhcp-client
to dhcpcd-base for Ubuntu 23.10 already. There is no need to allow
people to choose to install isc-dhcp-client instead at that point.

** Summary changed:

- ubuntu-minimal: please change Depends on isc-dhcp-client to | dhcp-client
+ ubuntu-minimal: please change Depends on isc-dhcp-client to dhcpcd-base

** Changed in: ubuntu-meta (Ubuntu)
   Status: New => Triaged

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

Title:
  ubuntu-minimal: please change Depends on isc-dhcp-client to dhcpcd-
  base

Status in ubuntu-meta package in Ubuntu:
  Triaged

Bug description:
  ubuntu-minimal currently has a hard Depends on isc-dhcp-client. Unless
  there is a compelling reason to depend on a specific DHCP
  implementation, this should be changed to "isc-dhcp-client | dhcp-
  client" instead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2019722/+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 2017999] Re: tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency

[Benjamin Drung]

tzdata 2023c-0ubuntu0.22.10.2 debdiff for kinetic.

** Patch added: "tzdata_2023c-0ubuntu0.22.10.2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2017999/+attachment/5673215/+files/tzdata_2023c-0ubuntu0.22.10.2.debdiff

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

Title:
  tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency

Status in python-tz package in Ubuntu:
  Fix Released
Status in tzdata package in Ubuntu:
  Fix Released
Status in python-tz source package in Focal:
  New
Status in tzdata source package in Focal:
  New
Status in python-tz source package in Jammy:
  New
Status in tzdata source package in Jammy:
  New
Status in python-tz source package in Kinetic:
  New
Status in tzdata source package in Kinetic:
  New
Status in python-tz source package in Lunar:
  Fix Committed
Status in tzdata source package in Lunar:
  New

Bug description:
  [ Impact ]

  Recent updates have been using `PACKRATDATA=backzone` in order to add
  all out-of-scope lower-quality pre-1970 data back that existed in
  earlier tzadata releases (see bug #2003797). However it also leads to
  time zones like America/Ensenada, Atlantic/Jan_Mayen, Europe/Tiraspol,
  and Pacific/Enderbury to change:

  compared to 2023c-0ubuntu0.22.04.0
  - America/Ensenada->only dst changes until 2022 are shown
  - Atlantic/Jan_Mayen->now valid data is shown
  - Europe/Tiraspol->only dst changes until 2010 are shown

  [ Test Plan ]

  Add an autopkgtest test case for post-1970 symlink consistency: Check
  that the timezones for today and in half a year (= to cover DST
  changes) do not change compared to building them without
  `PACKRATDATA=backzone`.

  The mentioned timezones that differed can also be tested manually.
  Running following commands should have the same output (the output
  mentioned here is from tzdata 2023c-0ubuntu0.22.04.1):

  ```
  $ TZ=America/Ensenada date -d "2023-04-28 13:49 Z"
  Fri Apr 28 05:49:00 PST 2023
  $ TZ=Atlantic/Jan_Mayen date -d "2023-04-28 13:49 Z"
  Fri Apr 28 12:49:00 -01 2023
  $ TZ=Europe/Tiraspol date -d "2023-04-28 13:49 Z"
  Fri Apr 28 16:49:00 MSK 2023
  ```

  [ Where problems could occur ]

  Timezone data could be wrong. Systems with incorrect timezone set may
  observe unexpected time shift when updating the package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-tz/+bug/2017999/+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 2019746] [NEW] package bluez 5.64-0ubuntu1 failed to install/upgrade: installed bluez package pre-removal script subprocess returned error exit status 1

[Wayne Hughes]

Public bug reported:

adding import of OBD with these packages as requirements, but are in
constrast to each other.

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: bluez 5.64-0ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-41-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.4
AptOrdering:
 pulseaudio-module-bluetooth:amd64: Remove
 gnome-bluetooth:amd64: Remove
 bluez:amd64: Remove
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: pass
Date: Mon May 15 13:30:12 2023
DpkgTerminalLog:
 Removing pulseaudio-module-bluetooth (1:15.99.1+dfsg1-1ubuntu2.1) ...
 Removing gnome-bluetooth (3.34.5-8) ...
 Removing bluez (5.64-0ubuntu1) ...
 Failed to stop bluetooth.service: Unit bluetooth.service not loaded.
 invoke-rc.d: initscript bluetooth, action "stop" failed.
ErrorMessage: installed bluez package pre-removal script subprocess returned 
error exit status 1
InstallationDate: Installed on 2023-01-23 (112 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
InterestingModules: bluetooth
MachineType: Gateway NE56R
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-41-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.1
 apt  2.4.9
Snap.Changes:
 ID   Status  Spawn  Ready  Summary
 27   Done2023-05-14T20:11:56-04:00  2023-05-14T20:13:10-04:00  Install 
"bluez" snap
SourcePackage: bluez
Title: package bluez 5.64-0ubuntu1 failed to install/upgrade: installed bluez 
package pre-removal script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/15/2012
dmi.bios.release: 2.7
dmi.bios.vendor: Gateway
dmi.bios.version: V2.07
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: EG50_HC_HR
dmi.board.vendor: Gateway
dmi.board.version: Type2 - Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Gateway
dmi.chassis.version: V2.07
dmi.ec.firmware.release: 0.0
dmi.modalias: 
dmi:bvnGateway:bvrV2.07:bd10/15/2012:br2.7:efr0.0:svnGateway:pnNE56R:pvrV2.07:rvnGateway:rnEG50_HC_HR:rvrType2-BoardVersion:cvnGateway:ct10:cvrV2.07:skuNE56R_0649_V2.07:
dmi.product.family: Type1Family
dmi.product.name: NE56R
dmi.product.sku: NE56R_0649_V2.07
dmi.product.version: V2.07
dmi.sys.vendor: Gateway
hciconfig:

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


** Tags: amd64 apport-package jammy

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

Title:
  package bluez 5.64-0ubuntu1 failed to install/upgrade: installed bluez
  package pre-removal script subprocess returned error exit status 1

Status in bluez package in Ubuntu:
  New

Bug description:
  adding import of OBD with these packages as requirements, but are in
  constrast to each other.

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: bluez 5.64-0ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.4
  AptOrdering:
   pulseaudio-module-bluetooth:amd64: Remove
   gnome-bluetooth:amd64: Remove
   bluez:amd64: Remove
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Mon May 15 13:30:12 2023
  DpkgTerminalLog:
   Removing pulseaudio-module-bluetooth (1:15.99.1+dfsg1-1ubuntu2.1) ...
   Removing gnome-bluetooth (3.34.5-8) ...
   Removing bluez (5.64-0ubuntu1) ...
   Failed to stop bluetooth.service: Unit bluetooth.service not loaded.
   invoke-rc.d: initscript bluetooth, action "stop" failed.
  ErrorMessage: installed bluez package pre-removal script subprocess returned 
error exit status 1
  InstallationDate: Installed on 2023-01-23 (112 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  InterestingModules: bluetooth
  MachineType: Gateway NE56R
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-41-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.1
   apt  2.4.9
  Snap.Changes:
   ID   Status  Spawn  Ready  Summary
   27   Done2023-05-14T20:11:56-04:00  2023-05-14T20:13:10-04:00  Install 
"bluez" snap
  SourcePackage: bluez
  Title: package bluez 5.64-0ubuntu1 failed to install/upgrade: installed bluez 
package pre-removal script subprocess returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/15/2012
  dmi.bios.release: 2.7
  dmi.bios.vendor: Gateway
  dmi.bios.version: 

[Touch-packages] [Bug 2017999] Re: tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency

[Benjamin Drung]

tzdata 2023c-2exp1ubuntu1.1 debdiff for lunar.

** Patch added: "tzdata_2023c-2exp1ubuntu1.1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/2017999/+attachment/5673192/+files/tzdata_2023c-2exp1ubuntu1.1.debdiff

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

Title:
  tzdata 2023c-0ubuntu0.22.04.1 might have some inconsistency

Status in python-tz package in Ubuntu:
  Fix Released
Status in tzdata package in Ubuntu:
  Fix Released
Status in python-tz source package in Focal:
  New
Status in tzdata source package in Focal:
  New
Status in python-tz source package in Jammy:
  New
Status in tzdata source package in Jammy:
  New
Status in python-tz source package in Kinetic:
  New
Status in tzdata source package in Kinetic:
  New
Status in python-tz source package in Lunar:
  Fix Committed
Status in tzdata source package in Lunar:
  New

Bug description:
  [ Impact ]

  Recent updates have been using `PACKRATDATA=backzone` in order to add
  all out-of-scope lower-quality pre-1970 data back that existed in
  earlier tzadata releases (see bug #2003797). However it also leads to
  time zones like America/Ensenada, Atlantic/Jan_Mayen, Europe/Tiraspol,
  and Pacific/Enderbury to change:

  compared to 2023c-0ubuntu0.22.04.0
  - America/Ensenada->only dst changes until 2022 are shown
  - Atlantic/Jan_Mayen->now valid data is shown
  - Europe/Tiraspol->only dst changes until 2010 are shown

  [ Test Plan ]

  Add an autopkgtest test case for post-1970 symlink consistency: Check
  that the timezones for today and in half a year (= to cover DST
  changes) do not change compared to building them without
  `PACKRATDATA=backzone`.

  The mentioned timezones that differed can also be tested manually.
  Running following commands should have the same output (the output
  mentioned here is from tzdata 2023c-0ubuntu0.22.04.1):

  ```
  $ TZ=America/Ensenada date -d "2023-04-28 13:49 Z"
  Fri Apr 28 05:49:00 PST 2023
  $ TZ=Atlantic/Jan_Mayen date -d "2023-04-28 13:49 Z"
  Fri Apr 28 12:49:00 -01 2023
  $ TZ=Europe/Tiraspol date -d "2023-04-28 13:49 Z"
  Fri Apr 28 16:49:00 MSK 2023
  ```

  [ Where problems could occur ]

  Timezone data could be wrong. Systems with incorrect timezone set may
  observe unexpected time shift when updating the package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-tz/+bug/2017999/+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 2018530] Re: Updating error, apt and apt-utils on Kubuntu 22.04 kernel version 5.19.0-41

[feveal]

I finally decided to try to fix it.
I have deleted the file 'trusted.gpg.d' which could not be overwritten and have 
already updated both packages. It seems to work.

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

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

Title:
  Updating error, apt and apt-utils on Kubuntu 22.04 kernel version
  5.19.0-41

Status in apt package in Ubuntu:
  Fix Released

Bug description:
  Doing regular update fails apt and apt-utils packages:

  ¿Desea continuar? [S/n] s
  (Leyendo la base de datos ... 759723 ficheros o directorios instalados 
actualmente.)
  Preparando para desempaquetar .../archives/apt_2.4.9_amd64.deb ...
  Desempaquetando apt (2.4.9) sobre (2.4.8) ...
  dpkg: error al procesar el archivo 
/var/cache/apt/archives/apt_2.4.9_amd64.deb (--unpack):
   intentando sobreescribir `/etc/apt/trusted.gpg.d', que está también en el 
paquete ubuntu-oem-keyring 2021.03.26
  dpkg-deb: error: el subproceso copiado fue terminado por la señal (Tubería 
rota)
  Se encontraron errores al procesar:
   /var/cache/apt/archives/apt_2.4.9_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  __

  Operating System: Kubuntu 22.04
  KDE Plasma Version: 5.24.7
  KDE Frameworks Version: 5.92.0
  Qt Version: 5.15.3
  Kernel Version: 5.19.0-41-generic (64-bit)
  Graphics Platform: X11
  Processors: 8 × Intel® Core™ i5-8265U CPU @ 1.60GHz
  Memory: 31.0 GiB of RAM
  Graphics Processor: Mesa Intel® UHD Graphics 620

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2018530/+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 2018530] Re: Updating error, apt and apt-utils on Kubuntu 22.04 kernel version 5.19.0-41

[feveal]

does anyone know how to solve this?
i have done several package updates but these two apt and apt-utils keep giving 
the same error:


** Attachment added: "1.png"
   
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2018530/+attachment/5673170/+files/1.png

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

Title:
  Updating error, apt and apt-utils on Kubuntu 22.04 kernel version
  5.19.0-41

Status in apt package in Ubuntu:
  New

Bug description:
  Doing regular update fails apt and apt-utils packages:

  ¿Desea continuar? [S/n] s
  (Leyendo la base de datos ... 759723 ficheros o directorios instalados 
actualmente.)
  Preparando para desempaquetar .../archives/apt_2.4.9_amd64.deb ...
  Desempaquetando apt (2.4.9) sobre (2.4.8) ...
  dpkg: error al procesar el archivo 
/var/cache/apt/archives/apt_2.4.9_amd64.deb (--unpack):
   intentando sobreescribir `/etc/apt/trusted.gpg.d', que está también en el 
paquete ubuntu-oem-keyring 2021.03.26
  dpkg-deb: error: el subproceso copiado fue terminado por la señal (Tubería 
rota)
  Se encontraron errores al procesar:
   /var/cache/apt/archives/apt_2.4.9_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  __

  Operating System: Kubuntu 22.04
  KDE Plasma Version: 5.24.7
  KDE Frameworks Version: 5.92.0
  Qt Version: 5.15.3
  Kernel Version: 5.19.0-41-generic (64-bit)
  Graphics Platform: X11
  Processors: 8 × Intel® Core™ i5-8265U CPU @ 1.60GHz
  Memory: 31.0 GiB of RAM
  Graphics Processor: Mesa Intel® UHD Graphics 620

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/2018530/+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 2019722] Re: ubuntu-minimal: please change Depends on isc-dhcp-client to | dhcp-client

[Martin-Éric Racine]

1) isc-dhcp-client doesn't do IPv6 well and cannot handle a dual-stack
case at all.

2) isc-dhcp-client is EOL upstream.

3) https://bugs.launchpad.net/ubuntu/+source/dhcpcd5/+bug/2019191

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

Title:
  ubuntu-minimal: please change Depends on isc-dhcp-client to | dhcp-
  client

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  ubuntu-minimal currently has a hard Depends on isc-dhcp-client. Unless
  there is a compelling reason to depend on a specific DHCP
  implementation, this should be changed to "isc-dhcp-client | dhcp-
  client" instead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2019722/+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 1939537] Re: Tests in ubuntu_lxc failed with "ERROR: Couldn't find a matching image." on X-hwe and older releases

[Ubuntu Foundations Team Bug Bot]

The attachment "lxc_3.0.3-0ubuntu1~18.04.3.debdiff" seems to be a
debdiff.  The ubuntu-sponsors team has been subscribed to the bug report
so that they can review and hopefully sponsor the debdiff.  If the
attachment isn't a patch, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are member of the
~ubuntu-sponsors, unsubscribe the team.

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

** Tags added: patch

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

Title:
  Tests in ubuntu_lxc failed with "ERROR: Couldn't find a matching
  image." on X-hwe and older releases

Status in ubuntu-kernel-tests:
  New
Status in lxc package in Ubuntu:
  New
Status in lxc source package in Bionic:
  New

Bug description:
  Issue found on node onibi 4.15.0-142-generic #146~16.04.1

  With bug 1916087 resolved, the following tests:
* lxc-test-apparmor-mount
* lxc-test-autostart
* lxc-test-unpriv
* lxc-test-usernic

  Are now failing with:
ERROR: Couldn't find a matching image.
   
  This is because with lxc version 2.0.11-0ubuntu1~16.04.3 the default target 
release is "trusty" or the system release if supported. It will be checked with:
ubuntu-distro-info --supported

  However Xenial is an ESM series now, it won't use xenial as the target
  release but use trusty instead.

  The attempt to download trusty image will fail with this error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1939537/+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 2019722] Re: ubuntu-minimal: please change Depends on isc-dhcp-client to | dhcp-client

[Jeremy Bícha]

Only isc-dhcp-client is in Ubuntu Main and therefore is supported by
Canonical.

Do you have a specific reason why people would need to use the alternate
implementation?

** Changed in: ubuntu-meta (Ubuntu)
   Status: Invalid => New

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

Title:
  ubuntu-minimal: please change Depends on isc-dhcp-client to | dhcp-
  client

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  ubuntu-minimal currently has a hard Depends on isc-dhcp-client. Unless
  there is a compelling reason to depend on a specific DHCP
  implementation, this should be changed to "isc-dhcp-client | dhcp-
  client" instead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2019722/+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 2019739] Re: Cannot reauthorize Google account

[mastier1]

Ok, worse. Cannot add at all. It crashes

** Summary changed:

- Cannot reauthorize Google account
+ Cannot reauthorize Google account or authorize again. The app crashes

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

Title:
  Cannot reauthorize Google account or authorize again. The app crashes

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

Bug description:
  As in title

  I tried to relogin, The window prompt appears and quickly exits and
  nothing happens. Still cannot not logged in. Have to remove account
  and sign in again.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-online-accounts 3.44.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-41-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon 
znvpair
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 15 17:45:34 2023
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-online-accounts
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/2019739/+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 2019739] Re: Cannot reauthorize Google account or authorize again. The app crashes

[mastier1]

/var/log/syslog:May 15 16:59:16 drakkar dbus-daemon[6292]: [session uid=127 
pid=6292] Activating via systemd: service name='org.gtk.vfs.GoaVolumeMonitor' 
unit='gvfs-goa-volume-monitor.service' requested by ':1.7' (uid=127 pid=6491 
comm="/usr/libexec/tracker-miner-fs-3 " label="unconfined")
/var/log/syslog:May 15 16:59:16 drakkar dbus-daemon[6292]: [session uid=127 
pid=6292] Activating service name='org.gnome.OnlineAccounts' requested by 
':1.9' (uid=127 pid=6563 comm="/usr/libexec/gvfs-goa-volume-monitor " 
label="unconfined")
/var/log/syslog:May 15 16:59:16 drakkar goa-daemon[6576]: goa-daemon version 
3.44.0 starting
/var/log/syslog:May 15 16:59:16 drakkar dbus-daemon[6292]: [session uid=127 
pid=6292] Activating service name='org.gnome.Identity' requested by ':1.10' 
(uid=127 pid=6576 comm="/usr/libexec/goa-daemon " label="unconfined")
/var/log/syslog:May 15 16:59:16 drakkar dbus-daemon[6292]: [session uid=127 
pid=6292] Successfully activated service 'org.gtk.vfs.GoaVolumeMonitor'
/var/log/syslog:May 15 16:59:28 drakkar dbus-daemon[21263]: [session uid=1000 
pid=21263] Activating via systemd: service name='org.gtk.vfs.GoaVolumeMonitor' 
unit='gvfs-goa-volume-monitor.service' requested by ':1.6' (uid=1000 pid=21292 
comm="/usr/libexec/tracker-miner-fs-3 " label="unconfined")
/var/log/syslog:May 15 16:59:28 drakkar dbus-daemon[21263]: [session uid=1000 
pid=21263] Activating service name='org.gnome.OnlineAccounts' requested by 
':1.9' (uid=1000 pid=21338 comm="/usr/libexec/gvfs-goa-volume-monitor " 
label="unconfined")
/var/log/syslog:May 15 16:59:28 drakkar goa-daemon[21342]: goa-daemon version 
3.44.0 starting
/var/log/syslog:May 15 16:59:28 drakkar dbus-daemon[21263]: [session uid=1000 
pid=21263] Activating service name='org.gnome.Identity' requested by ':1.10' 
(uid=1000 pid=21342 comm="/usr/libexec/goa-daemon " label="unconfined")
/var/log/syslog:May 15 16:59:28 drakkar dbus-daemon[21263]: [session uid=1000 
pid=21263] Successfully activated service 'org.gtk.vfs.GoaVolumeMonitor'
/var/log/syslog:May 15 16:59:29 drakkar goa-daemon[21342]: 
/org/gnome/OnlineAccounts/Accounts/account_1673287540_0: Setting 
AttentionNeeded to TRUE because EnsureCredentials() failed with: Failed to 
refresh access token (rest-proxy-error-quark, 400): Bad Request 
(goa-error-quark, 4)

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

Title:
  Cannot reauthorize Google account or authorize again. The app crashes

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

Bug description:
  As in title

  I tried to relogin, The window prompt appears and quickly exits and
  nothing happens. Still cannot not logged in. Have to remove account
  and sign in again.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-online-accounts 3.44.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-41-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon 
znvpair
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 15 17:45:34 2023
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-online-accounts
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/2019739/+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 2019739] [NEW] Cannot reauthorize Google account or authorize again. The app crashes

[mastier1]

Public bug reported:

As in title

I tried to relogin, The window prompt appears and quickly exits and
nothing happens. Still cannot not logged in. Have to remove account and
sign in again.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gnome-online-accounts 3.44.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-41-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon 
znvpair
ApportVersion: 2.20.11-0ubuntu82.4
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Mon May 15 17:45:34 2023
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-online-accounts
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-online-accounts (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  Cannot reauthorize Google account or authorize again. The app crashes

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

Bug description:
  As in title

  I tried to relogin, The window prompt appears and quickly exits and
  nothing happens. Still cannot not logged in. Have to remove account
  and sign in again.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: gnome-online-accounts 3.44.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-41-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon 
znvpair
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 15 17:45:34 2023
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-online-accounts
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/2019739/+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 2019722] Re: ubuntu-minimal: please change Depends on isc-dhcp-client to | dhcp-client

[Martin-Éric Racine]

Could it Depends on dhcp-client and let APT decide which package
providing this has the highest priority?

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

Title:
  ubuntu-minimal: please change Depends on isc-dhcp-client to | dhcp-
  client

Status in ubuntu-meta package in Ubuntu:
  Invalid

Bug description:
  ubuntu-minimal currently has a hard Depends on isc-dhcp-client. Unless
  there is a compelling reason to depend on a specific DHCP
  implementation, this should be changed to "isc-dhcp-client | dhcp-
  client" instead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2019722/+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 2019722] Re: ubuntu-minimal: please change Depends on isc-dhcp-client to | dhcp-client

[Jeremy Bícha]

It is not possible for ubuntu-meta to use alternate dependencies,
because ubuntu-meta relies on germinate.

** Changed in: ubuntu-meta (Ubuntu)
   Status: New => Invalid

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

Title:
  ubuntu-minimal: please change Depends on isc-dhcp-client to | dhcp-
  client

Status in ubuntu-meta package in Ubuntu:
  Invalid

Bug description:
  ubuntu-minimal currently has a hard Depends on isc-dhcp-client. Unless
  there is a compelling reason to depend on a specific DHCP
  implementation, this should be changed to "isc-dhcp-client | dhcp-
  client" instead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2019722/+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 2011458] Re: ssh fails to rebind when it is killed with -HUP

[Nick Rosbrook]

I verified the fix using openssh-server 1:9.0p1-1ubuntu7.2 from kinetic-
proposed:

Test 1:

root@kinetic:~# apt-cache policy openssh-server
openssh-server:
  Installed: 1:9.0p1-1ubuntu7.2
  Candidate: 1:9.0p1-1ubuntu7.2
  Version table:
 *** 1:9.0p1-1ubuntu7.2 500
500 http://archive.ubuntu.com/ubuntu kinetic-proposed/main amd64 
Packages
100 /var/lib/dpkg/status
 1:9.0p1-1ubuntu7.1 500
500 http://archive.ubuntu.com/ubuntu kinetic-updates/main amd64 Packages
 1:9.0p1-1ubuntu7 500
500 http://archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
root@kinetic:~# ssh localhost
The authenticity of host 'localhost (::1)' can't be established.
ED25519 key fingerprint is SHA256:DduZSXZNbtS3h9D91h0NQfRK7wnuxpWrj3f8/0J4ajc.
This key is not known by any other names
Are you sure you want to continue connecting (yes/no/[fingerprint])? no
Host key verification failed.
root@kinetic:~# systemctl status ssh.service
● ssh.service - OpenBSD Secure Shell server
 Loaded: loaded (/lib/systemd/system/ssh.service; disabled; preset: enabled)
Drop-In: /etc/systemd/system/ssh.service.d
 └─00-socket.conf
 /run/systemd/system/service.d
 └─zzz-lxc-service.conf
 Active: active (running) since Mon 2023-05-15 14:00:03 UTC; 11s ago
TriggeredBy: ● ssh.socket
   Docs: man:sshd(8)
 man:sshd_config(5)
Process: 1013 ExecStartPre=/usr/sbin/sshd -t (code=exited, status=0/SUCCESS)
   Main PID: 1014 (sshd)
  Tasks: 1 (limit: 18854)
 Memory: 1.3M
CPU: 40ms
 CGroup: /system.slice/ssh.service
 └─1014 "sshd: /usr/sbin/sshd -D [listener] 0 of 10-100 startups"

May 15 14:00:03 kinetic systemd[1]: Starting OpenBSD Secure Shell server...
May 15 14:00:03 kinetic sshd[1014]: Server listening on :: port 22.
May 15 14:00:03 kinetic systemd[1]: Started OpenBSD Secure Shell server.
May 15 14:00:04 kinetic sshd[1015]: Connection closed by ::1 port 43046 
[preauth]
root@kinetic:~# systemctl reload ssh.service
root@kinetic:~# systemctl status ssh.service
● ssh.service - OpenBSD Secure Shell server
 Loaded: loaded (/lib/systemd/system/ssh.service; disabled; preset: enabled)
Drop-In: /etc/systemd/system/ssh.service.d
 └─00-socket.conf
 /run/systemd/system/service.d
 └─zzz-lxc-service.conf
 Active: active (running) since Mon 2023-05-15 14:00:03 UTC; 22s ago
TriggeredBy: ● ssh.socket
   Docs: man:sshd(8)
 man:sshd_config(5)
Process: 1013 ExecStartPre=/usr/sbin/sshd -t (code=exited, status=0/SUCCESS)
Process: 1021 ExecReload=/usr/sbin/sshd -t (code=exited, status=0/SUCCESS)
Process: 1022 ExecReload=/bin/kill -HUP $MAINPID (code=exited, 
status=0/SUCCESS)
   Main PID: 1014 (sshd)
  Tasks: 1 (limit: 18854)
 Memory: 1.4M
CPU: 97ms
 CGroup: /system.slice/ssh.service
 └─1014 "sshd: /usr/sbin/sshd -D [listener] 0 of 10-100 startups"

May 15 14:00:03 kinetic systemd[1]: Starting OpenBSD Secure Shell server...
May 15 14:00:03 kinetic sshd[1014]: Server listening on :: port 22.
May 15 14:00:03 kinetic systemd[1]: Started OpenBSD Secure Shell server.
May 15 14:00:04 kinetic sshd[1015]: Connection closed by ::1 port 43046 
[preauth]
May 15 14:00:23 kinetic systemd[1]: Reloading OpenBSD Secure Shell server...
May 15 14:00:23 kinetic sshd[1014]: Received SIGHUP; restarting.
May 15 14:00:23 kinetic systemd[1]: Reloaded OpenBSD Secure Shell server.
May 15 14:00:23 kinetic sshd[1014]: Server listening on :: port 22.

Test 2:

root@kinetic:~# apt-cache policy openssh-server
openssh-server:
  Installed: 1:9.0p1-1ubuntu7.2
  Candidate: 1:9.0p1-1ubuntu7.2
  Version table:
 *** 1:9.0p1-1ubuntu7.2 500
500 http://archive.ubuntu.com/ubuntu kinetic-proposed/main amd64 
Packages
100 /var/lib/dpkg/status
 1:9.0p1-1ubuntu7.1 500
500 http://archive.ubuntu.com/ubuntu kinetic-updates/main amd64 Packages
 1:9.0p1-1ubuntu7 500
500 http://archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
root@kinetic:~# vi /etc/default/ssh 
root@kinetic:~# cat /etc/default/ssh 
# Default settings for openssh-server. This file is sourced by /bin/sh from
# /etc/init.d/ssh.

# Options to pass to sshd
SSHD_OPTS=-ddd
root@kinetic:~# ssh localhost
The authenticity of host 'localhost (::1)' can't be established.
ED25519 key fingerprint is SHA256:DduZSXZNbtS3h9D91h0NQfRK7wnuxpWrj3f8/0J4ajc.
This key is not known by any other names
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
Warning: Permanently added 'localhost' (ED25519) to the list of known hosts.
Welcome to Ubuntu 22.10 (GNU/Linux 6.2.0-20-generic x86_64)

 * Documentation:  https://help.ubuntu.com
 * Management: https://landscape.canonical.com
 * Support:https://ubuntu.com/advantage

The programs included with the Ubuntu system are free software;
the exact distribution terms for each program are described in the
individual files in 

[Touch-packages] [Bug 2011458] Re: ssh fails to rebind when it is killed with -HUP

[Nick Rosbrook]

I verified the fix using openssh-server 1:9.0p1-1ubuntu8.1 from lunar-
proposed:

Test 1:

root@lunar:~# apt-cache policy openssh-server
openssh-server:
  Installed: 1:9.0p1-1ubuntu8.1
  Candidate: 1:9.0p1-1ubuntu8.1
  Version table:
 *** 1:9.0p1-1ubuntu8.1 100
100 http://archive.ubuntu.com/ubuntu lunar-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 1:9.0p1-1ubuntu8 500
500 http://archive.ubuntu.com/ubuntu lunar/main amd64 Packages
root@lunar:~# ssh localhost
The authenticity of host 'localhost (::1)' can't be established.
ED25519 key fingerprint is SHA256:AbCnblNKQGNc02dY90hZSSobjAiPKfXOOs0YFUhVe9c.
This key is not known by any other names
Are you sure you want to continue connecting (yes/no/[fingerprint])? no
Host key verification failed.
root@lunar:~# systemctl status ssh.service
● ssh.service - OpenBSD Secure Shell server
 Loaded: loaded (/lib/systemd/system/ssh.service; disabled; preset: enabled)
Drop-In: /etc/systemd/system/ssh.service.d
 └─00-socket.conf
 /run/systemd/system/service.d
 └─zzz-lxc-service.conf
 Active: active (running) since Mon 2023-05-15 13:51:10 UTC; 16s ago
TriggeredBy: ● ssh.socket
   Docs: man:sshd(8)
 man:sshd_config(5)
Process: 148 ExecStartPre=/usr/sbin/sshd -t (code=exited, status=0/SUCCESS)
   Main PID: 149 (sshd)
  Tasks: 1 (limit: 18854)
 Memory: 1.3M
CPU: 71ms
 CGroup: /system.slice/ssh.service
 └─149 "sshd: /usr/sbin/sshd -D [listener] 0 of 10-100 startups"

May 15 13:51:10 lunar systemd[1]: Starting ssh.service - OpenBSD Secure Shell 
server...
May 15 13:51:10 lunar sshd[149]: Server listening on :: port 22.
May 15 13:51:10 lunar systemd[1]: Started ssh.service - OpenBSD Secure Shell 
server.
May 15 13:51:12 lunar sshd[150]: Connection closed by ::1 port 37598 [preauth]
root@lunar:~# systemctl reload ssh
root@lunar:~# systemctl status ssh.service
● ssh.service - OpenBSD Secure Shell server
 Loaded: loaded (/lib/systemd/system/ssh.service; disabled; preset: enabled)
Drop-In: /etc/systemd/system/ssh.service.d
 └─00-socket.conf
 /run/systemd/system/service.d
 └─zzz-lxc-service.conf
 Active: active (running) since Mon 2023-05-15 13:51:10 UTC; 23s ago
TriggeredBy: ● ssh.socket
   Docs: man:sshd(8)
 man:sshd_config(5)
Process: 148 ExecStartPre=/usr/sbin/sshd -t (code=exited, status=0/SUCCESS)
Process: 158 ExecReload=/usr/sbin/sshd -t (code=exited, status=0/SUCCESS)
Process: 159 ExecReload=/bin/kill -HUP $MAINPID (code=exited, 
status=0/SUCCESS)
   Main PID: 149 (sshd)
  Tasks: 1 (limit: 18854)
 Memory: 1.3M
CPU: 127ms
 CGroup: /system.slice/ssh.service
 └─149 "sshd: /usr/sbin/sshd -D [listener] 0 of 10-100 startups"

May 15 13:51:10 lunar systemd[1]: Starting ssh.service - OpenBSD Secure Shell 
server...
May 15 13:51:10 lunar sshd[149]: Server listening on :: port 22.
May 15 13:51:10 lunar systemd[1]: Started ssh.service - OpenBSD Secure Shell 
server.
May 15 13:51:12 lunar sshd[150]: Connection closed by ::1 port 37598 [preauth]
May 15 13:51:33 lunar systemd[1]: Reloading ssh.service - OpenBSD Secure Shell 
server...
May 15 13:51:33 lunar sshd[149]: Received SIGHUP; restarting.
May 15 13:51:33 lunar systemd[1]: Reloaded ssh.service - OpenBSD Secure Shell 
server.
May 15 13:51:33 lunar sshd[149]: Server listening on :: port 22.

Test 2:

root@lunar:~# apt-cache policy openssh-server
openssh-server:
  Installed: 1:9.0p1-1ubuntu8.1
  Candidate: 1:9.0p1-1ubuntu8.1
  Version table:
 *** 1:9.0p1-1ubuntu8.1 100
100 http://archive.ubuntu.com/ubuntu lunar-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 1:9.0p1-1ubuntu8 500
500 http://archive.ubuntu.com/ubuntu lunar/main amd64 Packages
root@lunar:~# vi /etc/default/ssh 
root@lunar:~# cat /etc/default/ssh 
# Default settings for openssh-server. This file is sourced by /bin/sh from
# /etc/init.d/ssh.

# Options to pass to sshd
SSHD_OPTS=-ddd
root@lunar:~# ssh localhost
The authenticity of host 'localhost (::1)' can't be established.
ED25519 key fingerprint is SHA256:AbCnblNKQGNc02dY90hZSSobjAiPKfXOOs0YFUhVe9c.
This key is not known by any other names
Are you sure you want to continue connecting (yes/no/[fingerprint])? yes
Warning: Permanently added 'localhost' (ED25519) to the list of known hosts.
Welcome to Ubuntu 23.04 (GNU/Linux 6.2.0-20-generic x86_64)

 * Documentation:  https://help.ubuntu.com
 * Management: https://landscape.canonical.com
 * Support:https://ubuntu.com/advantage

The programs included with the Ubuntu system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Ubuntu comes with ABSOLUTELY NO WARRANTY, to the extent permitted by
applicable law.

debug1: PAM: reinitializing credentials
debug1: permanently_set_uid: 0/0
debug3: Copy environment: 

[Touch-packages] [Bug 1939537] Re: Tests in ubuntu_lxc failed with "ERROR: Couldn't find a matching image." on X-hwe and older releases

[Andrei Gherzan]

I am attaching a fix for Bionic. Note that this pulls in another
unapproved change from @xnox to ease merging in time for the SRU cycle.

This was checked with Stéphane Graber, who agreed to an exception of
pushing a test-specific change given the SRU cycle is ending very soon,
and most of the users would have switched anyway.

** Patch added: "lxc_3.0.3-0ubuntu1~18.04.3.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1939537/+attachment/5673160/+files/lxc_3.0.3-0ubuntu1~18.04.3.debdiff

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

Title:
  Tests in ubuntu_lxc failed with "ERROR: Couldn't find a matching
  image." on X-hwe and older releases

Status in ubuntu-kernel-tests:
  New
Status in lxc package in Ubuntu:
  New
Status in lxc source package in Bionic:
  New

Bug description:
  Issue found on node onibi 4.15.0-142-generic #146~16.04.1

  With bug 1916087 resolved, the following tests:
* lxc-test-apparmor-mount
* lxc-test-autostart
* lxc-test-unpriv
* lxc-test-usernic

  Are now failing with:
ERROR: Couldn't find a matching image.
   
  This is because with lxc version 2.0.11-0ubuntu1~16.04.3 the default target 
release is "trusty" or the system release if supported. It will be checked with:
ubuntu-distro-info --supported

  However Xenial is an ESM series now, it won't use xenial as the target
  release but use trusty instead.

  The attempt to download trusty image will fail with this error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1939537/+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 2018128] Re: Apport does not collect all logs when the package is HWE kernel

[Benjamin Drung]

The kernel package has an exception. The apport package ships the
source_linux.py hooks and several symlinks:

```
$ ls -l /usr/share/apport/package-hooks/source_linux* 
lrwxrwxrwx 1 root root   15 Apr 14 00:17 
/usr/share/apport/package-hooks/source_linux-firmware.py -> source_linux.py
lrwxrwxrwx 1 root root   15 Apr 14 00:17 
/usr/share/apport/package-hooks/source_linux-meta-oem-osp1.py -> source_linux.py
lrwxrwxrwx 1 root root   15 Apr 14 00:17 
/usr/share/apport/package-hooks/source_linux-meta-oem.py -> source_linux.py
lrwxrwxrwx 1 root root   15 Apr 14 00:17 
/usr/share/apport/package-hooks/source_linux-meta.py -> source_linux.py
lrwxrwxrwx 1 root root   15 Apr 14 00:17 
/usr/share/apport/package-hooks/source_linux-meta-raspi.py -> source_linux.py
lrwxrwxrwx 1 root root   15 Apr 14 00:17 
/usr/share/apport/package-hooks/source_linux-oem-osp1.py -> source_linux.py
lrwxrwxrwx 1 root root   15 Apr 14 00:17 
/usr/share/apport/package-hooks/source_linux-oem.py -> source_linux.py
-rw-r--r-- 1 root root 6523 Apr 14 00:17 
/usr/share/apport/package-hooks/source_linux.py
lrwxrwxrwx 1 root root   15 Apr 14 00:17 
/usr/share/apport/package-hooks/source_linux-signed-oem-osp1.py -> 
source_linux.py
lrwxrwxrwx 1 root root   15 Apr 14 00:17 
/usr/share/apport/package-hooks/source_linux-signed-oem.py -> source_linux.py
lrwxrwxrwx 1 root root   15 Apr 14 00:17 
/usr/share/apport/package-hooks/source_linux-signed.py -> source_linux.py
```

How is the HWE kernel package named? Can you try to add a symlink for
the source package name to see if that solves your issue?

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

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

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

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

Title:
  Apport does not collect all logs when the package is HWE kernel

Status in apport package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 22.04 LTS with kernel 5.19.0-41-generic

  When filing bugs against the package 'linux' apport collects all the logs 
needed
  to the kernel

  But in case the user is not on stock kernel anymore and has the HWE kernel
  apport only imports 2 logs Dependencies.txt + ProcCpuInfoMinimal.txt

  and forwards the package 'linux' towards linux-signed-hwe-5.19 (in my
  case)

  would it be possible to make apport collect all the logs needed in all
  kernel cases?

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apport 2.20.11-0ubuntu82.4
  ProcVersionSignature: Ubuntu 5.19.0-41.42~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-41-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.11-0ubuntu82.4
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 29 05:25:30 2023
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2018128/+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 1858202] Re: apport dialog with "text" text or without a description

[Benjamin Drung]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

The attached logs do not indicate which part of the apport code (or one
of the package hooks) shows this faulty dialog. Can you reproduce
getting this faulty dialog presented? Can you provide step by step
instruction how to reproduce it? Is there anything special in your setup
that could have an influence (language, etc)?

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

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

Title:
  apport dialog with "text" text or without a description

Status in apport package in Ubuntu:
  Incomplete

Bug description:
  When using ubuntu-bug, the dialog box is shown twice asking for using 
confirmation.
  However, the text in the dialog is garbage.  It is "text" instead of a real 
description.
  If I have to bet, "text" was a placeholder not replaced by the real content.
  See the screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: apport 2.20.11-0ubuntu8.2
  Uname: Linux 5.4.5-050405-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportLog:
   
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Fri Jan  3 09:44:29 2020
  InstallationDate: Installed on 2014-05-12 (2062 days ago)
  InstallationMedia: Error: [Errno 13] Permission denied: 
'/var/log/installer/media-info'
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to eoan on 2019-11-17 (46 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1858202/+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 2019295] Re: ubuntu 20.04 can not collect app dump

[Benjamin Drung]

Investigation so far


The crashing Python code line:

```
exe_mtime = os.stat('exe', dir_fd=proc_pid_fd).st_mtime
```

I search my system for processes where /proc//exe could not be read
by running `sudo ls /proc/[0-9]*/exe` and looking for error messages. I
found one process:

```
$ sudo LANG=C stat /proc/6157/exe
  File: /proc/6157/exe -> /snap/snapd/19122/usr/lib/snapd/snapd
  Size: 0   Blocks: 0  IO Block: 1024   symbolic link
Device: 0,22Inode: 68395   Links: 1
Access: (0777/lrwxrwxrwx)  Uid: (100/ UNKNOWN)   Gid: (100/ UNKNOWN)
Access: 2023-05-15 10:35:02.60873 +0200
Modify: 2023-05-15 10:35:02.584000872 +0200
Change: 2023-05-15 10:35:02.584000872 +0200
 Birth: -
$ sudo LANG=C stat /snap/snapd/19122/usr/lib/snapd/snapd
stat: cannot statx '/snap/snapd/19122/usr/lib/snapd/snapd': No such file or 
directory
```

** Summary changed:

- ubuntu 20.04 can not collect app dump
+ Apport failed to collect crash dump: PermissionError: [Errno 13] Permission 
denied: 'exe'

** Description changed:

  ubuntu 20.04 can not collect app dump
+ 
+ ApportLog.txt shows:
+ 
+ ```
+ ERROR: apport (pid 15077) Fri May 12 15:26:09 2023: Unhandled exception:
+ Traceback (most recent call last):
+   File "/usr/share/apport/apport", line 666, in 
+ exe_mtime = os.stat('exe', dir_fd=proc_pid_fd).st_mtime
+ PermissionError: [Errno 13] Permission denied: 'exe'
+ ERROR: apport (pid 15077) Fri May 12 15:26:09 2023: pid: 15077, uid: 0, gid: 
0, euid: 0, egid: 0
+ ERROR: apport (pid 15077) Fri May 12 15:26:09 2023: environment: 
environ({'LC_CTYPE': 'C.UTF-8'})
+ ```
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apport 2.20.11-0ubuntu27.25
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri May 12 15:37:13 2023
  InstallationDate: Installed on 2022-08-17 (268 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Apport failed to collect crash dump: PermissionError: [Errno 13]
  Permission denied: 'exe'

Status in apport package in Ubuntu:
  New

Bug description:
  ubuntu 20.04 can not collect app dump

  ApportLog.txt shows:

  ```
  ERROR: apport (pid 15077) Fri May 12 15:26:09 2023: Unhandled exception:
  Traceback (most recent call last):
File "/usr/share/apport/apport", line 666, in 
  exe_mtime = os.stat('exe', dir_fd=proc_pid_fd).st_mtime
  PermissionError: [Errno 13] Permission denied: 'exe'
  ERROR: apport (pid 15077) Fri May 12 15:26:09 2023: pid: 15077, uid: 0, gid: 
0, euid: 0, egid: 0
  ERROR: apport (pid 15077) Fri May 12 15:26:09 2023: environment: 
environ({'LC_CTYPE': 'C.UTF-8'})
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apport 2.20.11-0ubuntu27.25
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri May 12 15:37:13 2023
  InstallationDate: Installed on 2022-08-17 (268 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2019295/+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 2019721] [NEW] package python3-software-properties 0.99.22.7 failed to install/upgrade: new python3-software-properties package pre-removal script subprocess returned error exit

[John Friesen]

Public bug reported:

Trying to fix broken install

ProblemType: Package
DistroRelease: Ubuntu 22.04
Package: python3-software-properties 0.99.22.7
ProcVersionSignature: Ubuntu 5.19.0-40.41~22.04.1-generic 5.19.17
Uname: Linux 5.19.0-40-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Mon May 15 07:24:20 2023
ErrorMessage: new python3-software-properties package pre-removal script 
subprocess returned error exit status 139
InstallationDate: Installed on 2020-11-11 (914 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
PackageArchitecture: all
Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.21.1ubuntu2.2
 apt  2.4.9
SourcePackage: software-properties
Title: package python3-software-properties 0.99.22.7 failed to install/upgrade: 
new python3-software-properties package pre-removal script subprocess returned 
error exit status 139
UpgradeStatus: Upgraded to jammy on 2022-04-07 (403 days ago)

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package jammy package-from-proposed third-party-packages

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

Title:
  package python3-software-properties 0.99.22.7 failed to
  install/upgrade: new python3-software-properties package pre-removal
  script subprocess returned error exit status 139

Status in software-properties package in Ubuntu:
  New

Bug description:
  Trying to fix broken install

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: python3-software-properties 0.99.22.7
  ProcVersionSignature: Ubuntu 5.19.0-40.41~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-40-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Mon May 15 07:24:20 2023
  ErrorMessage: new python3-software-properties package pre-removal script 
subprocess returned error exit status 139
  InstallationDate: Installed on 2020-11-11 (914 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.9
  SourcePackage: software-properties
  Title: package python3-software-properties 0.99.22.7 failed to 
install/upgrade: new python3-software-properties package pre-removal script 
subprocess returned error exit status 139
  UpgradeStatus: Upgraded to jammy on 2022-04-07 (403 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2019721/+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 2019722] [NEW] ubuntu-minimal: please change Depends on isc-dhcp-client to | dhcp-client

[Martin-Éric Racine]

Public bug reported:

ubuntu-minimal currently has a hard Depends on isc-dhcp-client. Unless
there is a compelling reason to depend on a specific DHCP
implementation, this should be changed to "isc-dhcp-client | dhcp-
client" instead.

** Affects: ubuntu-meta (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  ubuntu-minimal: please change Depends on isc-dhcp-client to | dhcp-
  client

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  ubuntu-minimal currently has a hard Depends on isc-dhcp-client. Unless
  there is a compelling reason to depend on a specific DHCP
  implementation, this should be changed to "isc-dhcp-client | dhcp-
  client" instead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2019722/+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 2003339] Re: kwin_x11: The X11 connection broke: I/O error (code 1)

[Gunter Ohrner]

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

Title:
  kwin_x11: The X11 connection broke: I/O error (code 1)

Status in KDE Base Workspace:
  Fix Released
Status in Mesa:
  Fix Released
Status in kwin package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Fix Released
Status in kwin source package in Jammy:
  Invalid
Status in mesa source package in Jammy:
  Fix Committed
Status in kwin package in Debian:
  New

Bug description:
  [Impact]

  kwin might crash after running some time

  Two commits have been reverted upstream since 22.2.x branch was
  closed, needs those backported to fix this.

  [Test case]

  Run kwin for a day or so, which is usually enough time to hit this.

  Crash happens mostly on a notification popups, so system must be
  actively receiving notifications to test the crash. Without that crash
  may not happen even in a week of runtime.

  [Where things could go wrong]

  This just reverts two commits, and they have been upstream for a few
  months now, so these causing a regression is unlikely.

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdebase-workspace/+bug/2003339/+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 2003339] Re: kwin_x11: The X11 connection broke: I/O error (code 1)

[Gunter Ohrner]

I can confirm the fix for jammy - I'm now running the fixed version
since it hit jammy-proposed on Friday.

I wanted to wait a few days to be sure, but so far it looks very
promising - no kwin crash / termination since then! :)

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

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

Title:
  kwin_x11: The X11 connection broke: I/O error (code 1)

Status in KDE Base Workspace:
  Fix Released
Status in Mesa:
  Fix Released
Status in kwin package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Fix Released
Status in kwin source package in Jammy:
  Invalid
Status in mesa source package in Jammy:
  Fix Committed
Status in kwin package in Debian:
  New

Bug description:
  [Impact]

  kwin might crash after running some time

  Two commits have been reverted upstream since 22.2.x branch was
  closed, needs those backported to fix this.

  [Test case]

  Run kwin for a day or so, which is usually enough time to hit this.

  Crash happens mostly on a notification popups, so system must be
  actively receiving notifications to test the crash. Without that crash
  may not happen even in a week of runtime.

  [Where things could go wrong]

  This just reverts two commits, and they have been upstream for a few
  months now, so these causing a regression is unlikely.

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdebase-workspace/+bug/2003339/+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 2019295] Re: ubuntu 20.04 can not collect app dump

[Benjamin Drung]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.

ApportLog.txt shows:

```
ERROR: apport (pid 15077) Fri May 12 15:26:09 2023: Unhandled exception:
Traceback (most recent call last):
  File "/usr/share/apport/apport", line 666, in 
exe_mtime = os.stat('exe', dir_fd=proc_pid_fd).st_mtime
PermissionError: [Errno 13] Permission denied: 'exe'
ERROR: apport (pid 15077) Fri May 12 15:26:09 2023: pid: 15077, uid: 0, gid: 0, 
euid: 0, egid: 0
ERROR: apport (pid 15077) Fri May 12 15:26:09 2023: environment: 
environ({'LC_CTYPE': 'C.UTF-8'})
```

Do you know which application crashed?

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

Title:
  ubuntu 20.04 can not collect app dump

Status in apport package in Ubuntu:
  New

Bug description:
  ubuntu 20.04 can not collect app dump

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apport 2.20.11-0ubuntu27.25
  ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-30-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.25
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri May 12 15:37:13 2023
  InstallationDate: Installed on 2022-08-17 (268 days ago)
  InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2019295/+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 1780767] Re: Some GTK UI tests are flaky due to timeout

[Benjamin Drung]

The autopkgtests for apport 2.20.11-0ubuntu82.5 succeeded:

* amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/a/apport/20230513_011620_4e4be@/log.gz
* arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/arm64/a/apport/20230513_004013_dc931@/log.gz
* armhf: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/armhf/a/apport/20230513_004303_6da9e@/log.gz
* ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/ppc64el/a/apport/20230513_003849_f2533@/log.gz
* s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/s390x/a/apport/20230513_004752_eb29f@/log.gz

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

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

Title:
  Some GTK UI tests are flaky due to timeout

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Bionic:
  Fix Released
Status in apport source package in Focal:
  New
Status in apport source package in Jammy:
  Fix Committed

Bug description:
  [Impact]

  The autopkgtests are sometimes passing, sometimes stuck for more than 2h:
  http://autopkgtest.ubuntu.com/packages/apport/cosmic/amd64.
  It's blocking randomly on different tests.

  All tests that are stucked, implements closing a request via a timeout
  (and then, executing "run"). The bet is that the timeout is short
  enough (1s) so that, when autopkgtests infra is busy, time to execute
  the bash subcommand is taking more than a second, and so "dismissing"
  is ran before execution happens and the whole testsuite hangs.

  There are few instances of setting this timeout function:
  $ grep eout_add_sec test/*
  test/test_ui_gtk.py:GLib.timeout_add_seconds(1, cont)
  test/test_ui_gtk.py:GLib.timeout_add_seconds(1, cont)
  test/test_ui_gtk.py:GLib.timeout_add_seconds(1, cont)
  test/test_ui_gtk.py:GLib.timeout_add_seconds(1, c)
  test/test_ui_gtk.py:GLib.timeout_add_seconds(1, c)

  Short term solution could be to increase the timeout. Long term would
  be to eliminate this potential race implementing cancelling
  differently. The short term workaround to increase the timeout
  increases the test execution time by five minutes.

  [Test Plan]

  Check that the autopkgtest succeed on all architectures (except for
  i386).

  [Where problems could occur]

  The test cases are only part of the apport source package and are not
  copied in any binary packages. Changes to the test will only affect
  the package build and test execution.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1780767/+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 1973470] Re: Ubuntu-bug command can't find Firefox on Lubuntu Kinetic

[Benjamin Drung]

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

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

Title:
  Ubuntu-bug command can't find Firefox on Lubuntu Kinetic

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in xdg-utils package in Ubuntu:
  Invalid
Status in apport source package in Jammy:
  Fix Committed
Status in xdg-utils source package in Jammy:
  New

Bug description:
  Test hardware is an Elitebook 8570p, 16 GB RAM, 120 GB SSD.

  While reporting Bug #1973469, I discovered that ubuntu-bug was unable
  to open Firefox at the very end of the process. Sadly, I closed the
  terminal window that contained the initial error, but I was able to
  easily reproduce it reporting this bug. The full console output of
  "ubuntu-bug apport" on Lubuntu Kinetic is:

  
  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  ..

  *** Send problem report to the developers?

  After the problem report has been sent, please fill out the form in the
  automatically opened web browser.

  What would you like to do? Your options are:
S: Send report (5.1 KB)
V: View report
K: Keep report file for sending later or copying to somewhere else
I: Cancel and ignore future crashes of this program version
C: Cancel
  Please choose (S/V/K/I/C): s

  *** Uploading problem information

  The collected information is being sent to the bug tracking system.
  This might take a few minutes.
  94%

  *** To continue, you must visit the following URL:

  
https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/d7ffa3e0-d46d-11ec-a167-40a8f03099c8?

  You can launch a browser now, or copy this URL into a browser on
  another computer.

  
  Choices:
1: Launch a browser now
C: Cancel
  Please choose (1/C): 1
  /usr/bin/xdg-open: 882: firefox: not found
  /usr/bin/xdg-open: 882: firefox: not found
  xdg-open: no method available for opening 
'https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/d7ffa3e0-d46d-11ec-a167-40a8f03099c8?'

  I am unsure if this problem is in Apport or Lubuntu. ubuntu-bug works
  just fine for me on Ubuntu Kinetic, but not on Lubuntu. I suspect this
  is due to the Snap version of Firefox, but I don't know for sure.
  Since ubuntu-bug is what gave me the error, I'm filing this against
  Apport.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.10
  Package: apport 2.20.11-0ubuntu82
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.470
  CurrentDesktop: LXQt
  Date: Sun May 15 11:41:07 2022
  LiveMediaBuild: Lubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220514)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1973470/+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 1978301] Re: Broken contact URL in German translation

[Benjamin Drung]

Verified apport 2.20.11-0ubuntu82.5 in a jammy VM as good as possible.
The German translation removed the dot at the end in the meantime. The
links displayed in the presented window is correct.

Sadly there seems to be a regression somewhere else: Clicking on the
link did not open the browser window, but causes these error messages
(identical behavior to apport 2.20.11-0ubuntu82.4):

```
$ LANGUAGE=de ubuntu-bug firefox
grep: /proc/sys/fs/binfmt_misc/WSLInterop: No such file or directory
WSL Interopability is disabled. Please enable it before using WSL.
grep: /proc/sys/fs/binfmt_misc/WSLInterop: No such file or directory
[error] WSL Interoperability is disabled. Please enable it before using WSL.
/usr/bin/wslview: line 216: /mnt/c/Windows/System32/reg.exe: No such file or 
directory
/usr/bin/wslview: line 149: /mnt/c/Windows/System32/chcp.com: No such file or 
directory
/usr/bin/wslview: line 156: 
/mnt/c/Windows/System32/WindowsPowerShell/v1.0/powershell.exe: No such file or 
directory
/usr/bin/wslview: line 149: /mnt/c/Windows/System32/chcp.com: No such file or 
directory
```

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

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

Title:
  Broken contact URL in German translation

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Jammy:
  Fix Committed

Bug description:
  Impact
  --

  All German users (and all translations that use "%s." in their
  translation template) will get a broken URL link for bug reports
  against snaps (e.g. Firefox).

  Test Case
  -

  1. Execute following command: LANGUAGE=de ubuntu-bug firefox
  2. Click on the URL
  3. A browser window should open and not display a 404 page

  Regression Potential
  

  Since there was no test case for converting text to HTML before this
  fix, there might be some URLs that will become broken by this fix.

  Original Description
  

  "LANGUAGE=de ubuntu-bug firefox" end up in a dialog saying:

  firefox wird durch einen von mozilla veröffentlichten Snap
  bereitgestellt. Für Hilfe gehen Sie über
  https://support.mozilla.org/kb/file-bug-report-or-feature-request-
  mozilla.

  The dot at the end is included in the URL link. The dot makes the URL
  link broken. The regular expression in gtk/apport-gtk for http URLs
  should become smarter.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1978301/+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 1531404] Re: nonexistent partition in /dev, & lsblk/disk util misbehaving with randomized disks

[DiagonalArg]

Seven years and two weeks later!

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

Title:
  nonexistent partition in /dev, & lsblk/disk util misbehaving with
  randomized disks

Status in util-linux package in Ubuntu:
  Expired

Bug description:
  I have two 2T disks with no partition table and which have been filled
  with random data.  GNU parted shows nothing on this disk:

  GNU Parted 3.2
  Using /dev/sda
  Welcome to GNU Parted! Type 'help' to view a list of commands.
  (parted) print
  Error: /dev/sda: unrecognised disk label
  Model: ATA WDC WD2002FAEX-0 (scsi)
  Disk /dev/sda: 2000GB
  Sector size (logical/physical): 512B/512B
  Partition Table: unknown
  Disk Flags:

  but when I check with `lsblk`, I see one disk with partitions and the
  other without:

  Code:
  NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
  sda 8:0 0 1.8T 0 disk
  └─sda2 8:2 0 1.6T 0 part

  NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
  sdb 8:16 0 1.8T 0 disk

  and the Disks utility agrees (see: http://ibin.co/2SQv4KbH06Mz).

  Also, /dev/disk/by-id contains an entry pointing to sda and one
  pointing to sda2. So it really does think there's a second partition
  there.

  Thinking there was something wrong, I re-filled the disks with random
  data.  Now sda is properly (in the Disks utility as just an "unknown
  disk"), but sdb shows a second partition, and identically to how sda
  was showing it before (ie the Disks utility output is the same with
  181GB at the beginning and 128GB at the end).

  I am running all this from the Ubuntu Gnome 15.10 installer disk.
  --- 
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 15.10
  InstallationDate: Installed on 2015-08-31 (130 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  Package: util-linux 2.26.2-6ubuntu3
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.2.0-23.28-generic 4.2.6
  Tags:  wily
  Uname: Linux 4.2.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1531404/+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 1967965] Re: apport-kde: "Other problem" and "Display" options are swapped

[Benjamin Drung]

Verified for apport-kde 2.20.11-0ubuntu27.27 in a focal VM.

** 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 apport in Ubuntu.
https://bugs.launchpad.net/bugs/1967965

Title:
  apport-kde: "Other problem" and "Display" options are swapped

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Focal:
  Fix Committed
Status in apport source package in Jammy:
  Fix Released

Bug description:
  [ Impact ]

  Due to this bug, users on KDE have hard times to report generic
  problems against Ubuntu.

  [ Testcase ]

  1. Run: /usr/share/apport/apport-kde -f
  2. Select "Display (X.org)" and click OK
  3. Then a window asking "What display problem do you observe?" should be 
presented.

  [ Where problems could occur ]

  Since this fix enables users to properly report generic problems, it
  can reveal bugs in the later stage.

  [ Other Info ]

  Since this fix touched the KDE part, the SRU will also enable the KDE
  UI tests again and repair them to make them run.

  [ Original report ]

  When attempting to report
  https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1967963 I was
  unable to use `ubuntu-bug firefox`, so I just ran `ubuntu-bug`.
  However doing so gave me a menu with unrelated option (as expected)
  and an "Other problem..." option. I assumed this was for generic other
  bugs, as I think is reasonable; however, it brings me to a menu that
  only makes sense for display-related bugs. I think this text should be
  changed to note that; perhaps "Other display problem...".

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apport 2.20.11-0ubuntu80
  ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
  Uname: Linux 5.15.0-23-generic x86_64
  ApportVersion: 2.20.11-0ubuntu80
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashReports:
   640:1000:124:13488049:2022-03-30 13:20:08.905176436 -0500:2022-03-30 
13:20:07.977480154 -0500:/var/crash/_usr_bin_telegram-desktop.1000.crash
   640:0:124:755694:2022-03-30 13:17:26.598466630 -0500:2022-03-30 
13:17:26.258453989 -0500:/var/crash/_usr_libexec_udisks2_udisksd.0.crash
  CurrentDesktop: KDE
  Date: Tue Apr  5 19:58:56 2022
  InstallationDate: Installed on 2022-03-30 (6 days ago)
  InstallationMedia: Kubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/usr/bin/zsh
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1967965/+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 1947800] Re: /usr/share/apport/whoopsie-upload-all:zlib.error:/usr/share/apport/whoopsie-upload-all@196:collect_info:process_report:add_gdb_info:gdb_command:write:read:readinto:r

[Benjamin Drung]

2.20.11-0ubuntu27.27 has not appeared on
https://errors.ubuntu.com/problem/fff3109d511a7db05ec5526679b8d8608a143932
so far.

** 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 apport in Ubuntu.
https://bugs.launchpad.net/bugs/1947800

Title:
  /usr/share/apport/whoopsie-upload-
  all:zlib.error:/usr/share/apport/whoopsie-upload-
  
all@196:collect_info:process_report:add_gdb_info:gdb_command:write:read:readinto:read

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Focal:
  Fix Committed
Status in apport source package in Impish:
  Won't Fix
Status in apport source package in Jammy:
  Fix Released

Bug description:
  [ Impact ]

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.11-0ubuntu70, the problem page at 
https://errors.ubuntu.com/problem/7120f8aebdf09e9dca39196d035eec234071e800 
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/.

  Traceback (most recent call last):
    File "/usr/share/apport/whoopsie-upload-all", line 196, in 
  stamps = collect_info()
    File "/usr/share/apport/whoopsie-upload-all", line 146, in collect_info
  res = process_report(r)
    File "/usr/share/apport/whoopsie-upload-all", line 103, in process_report
  r.add_gdb_info()
    File "/usr/lib/python3/dist-packages/apport/report.py", line 786, in 
add_gdb_info
  gdb_cmd, environ = self.gdb_command(rootdir, gdb_sandbox)
    File "/usr/lib/python3/dist-packages/apport/report.py", line 1706, in 
gdb_command
  self['CoreDump'].write(f)
    File "/usr/lib/python3/dist-packages/problem_report.py", line 75, in write
  block = gz.read(1048576)
    File "/usr/lib/python3.9/gzip.py", line 300, in read
  return self._buffer.read(size)
    File "/usr/lib/python3.9/_compression.py", line 68, in readinto
  data = self.read(len(byte_view))
    File "/usr/lib/python3.9/gzip.py", line 495, in read
  uncompress = self._decompressor.decompress(buf, size)
  zlib.error: Error -3 while decompressing data: invalid code lengths set

  Report for 20.04 (focal):
  https://errors.ubuntu.com/problem/fff3109d511a7db05ec5526679b8d8608a143932

  [ Test plan ]

  Check that the fixed version does not appear on
  https://errors.ubuntu.com/problem/fff3109d511a7db05ec5526679b8d8608a143932

  [Where problems could occur]

  Worst case - in any part of the bug reporting/collection procedure,
  since that is what's changing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1947800/+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 1964828] Re: /usr/share/apport/general-hooks/ubuntu.py crashed: KeyError: 'CasperMD5json'

[Benjamin Drung]

Verified that apport 2.20.11-0ubuntu27.27 does not throw a KeyError on
CasperMD5json any more:

```
$ ubuntu-bug -f
Error executing command as another user: Request dismissed
ERROR: hook /usr/share/apport/package-hooks/source_ubiquity.py crashed:
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/apport/report.py", line 228, in _run_hook
symb['add_info'](report, ui)
  File "/usr/share/apport/package-hooks/source_ubiquity.py", line 65, in 
add_info
add_installation_log(report, 'UbiquitySyslog', 'syslog')
  File "/usr/share/apport/package-hooks/source_ubiquity.py", line 29, in 
add_installation_log
if isinstance(report[ident], bytes):
  File "/usr/lib/python3.8/collections/__init__.py", line 1010, in __getitem__
raise KeyError(key)
KeyError: 'UbiquitySyslog'
```

This KeyError on UbiquitySyslog is a separate issue.

** 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 apport in Ubuntu.
https://bugs.launchpad.net/bugs/1964828

Title:
  /usr/share/apport/general-hooks/ubuntu.py crashed: KeyError:
  'CasperMD5json'

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Focal:
  Fix Committed
Status in apport source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  If the user reports a bug and rejects to enter the root password for
  collecting information (like the CasperMD5json), the Ubuntu add_info
  hook will fail with a stack trace. The remaining code for collecting
  more information is not executed. So the resulting bug reports will be
  less helpful. The check_for_disk_error call is not reached and
  therefore skipped.

  [Test Plan]

  1. Install Ubuntu (e.g. from ubuntu-22.04-desktop-amd64.iso)
  2. Open a terminal
  3. Run: ubuntu-bug -f
  4. Select "installer" and click on OK
  5. Click on "abort" when ask for the password
  6. The terminal should not show a stacktrace

  [Where problems could occur]

  The changed code is the Ubuntu add_info hook. So this hook could fail
  due to a regression or reveal bugs in the later code path. The later
  code path could cause more more load on the users machine (but only
  when the user wants to report the issue). Apport will catch failing
  add_info hooks and store the failure in the report.

  [Orinial report]

  ERROR: hook /usr/share/apport/general-hooks/ubuntu.py crashed:
  Traceback (most recent call last):
    File "/usr/lib/python3/dist-packages/apport/report.py", line 228, in 
_run_hook
  symb['add_info'](report, ui)
    File "/usr/share/apport/general-hooks/ubuntu.py", line 81, in add_info
  apport.hookutils.attach_casper_md5check(report,
    File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 1016, in 
attach_casper_md5check
  check = json.loads(report['CasperMD5json'])
    File "/usr/lib/python3.10/collections/__init__.py", line 1102, in 
__getitem__
  raise KeyError(key)
  KeyError: 'CasperMD5json'
  kubuntu@kubuntu:~$ Gtk-Message: 21:22:43.923: Failed to load module 
"colorreload-gtk-module"
  ATTENTION: default value of option mesa_glthread overridden by environment.
  ATTENTION: default value of option mesa_glthread overridden by environment.
  ATTENTION: default value of option mesa_glthread overridden by environment.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: ubiquity 22.04.7
  ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19
  Uname: Linux 5.15.0-22-generic x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperVersion: 1.467
  CurrentDesktop: KDE
  Date: Mon Mar 14 21:22:23 2022
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/kubuntu.seed 
maybe-ubiquity quiet splash ---
  LiveMediaBuild: Kubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220314)
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1964828/+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 1889443] Re: "ValueError: ['separator'] has no binary content" when running `apport-unpack /var/crash/...`

[Benjamin Drung]

Verified in a focal VM (using sleep since focal does not have chaos-
marmosets):

```
$ sleep 3600 &
$ sudo rm /var/crash/_usr_bin_*
$ killall -11 sleep
$ tmpdir=$(mktemp -d)
$ apport-unpack /var/crash/_usr_bin_sleep.1000.crash "$tmpdir"
$ 
```

** 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 apport in Ubuntu.
https://bugs.launchpad.net/bugs/1889443

Title:
  "ValueError: ['separator'] has no binary content" when running
  `apport-unpack /var/crash/...`

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Bionic:
  Triaged
Status in apport source package in Focal:
  Fix Committed
Status in apport source package in Jammy:
  Fix Released

Bug description:
  [ Impact ]

  Extracting a crash file will always fail in case the crash report was
  processed.

  [ Test plan ]

  1. Create crash (e.g. with divide-by-zero):
  ```
  sudo apt install chaos-marmosets
  divide-by-zero
  ```
  2. Click on "show details" in Apport crash UI, then close it
  3. exract crash report:
  ```
  tmpdir=$(mktemp -d)
  apport-unpack /var/crash/_usr_bin_divide-by-zero.1000.crash "$tmpdir"
  rm -rf "$tmpdir"
  ```

  The extraction should work and not print a stack trace.

  [ Where problems could occur ]

  The change touches the problem report reading code which is used in
  several places. This could cause regressions in reading the problem
  report.

  [ Original report ]

  The crash file I'm using is as-produced by the system (on groovy), and
  appears to have an empty value for separator:

  $ grep separator /var/crash/_usr_bin_neomutt.1000.crash
  separator:

  Traceback (most recent call last):
    File "/usr/bin/apport-unpack", line 77, in 
  pr.extract_keys(f, bin_keys, dir)
    File "/usr/lib/python3/dist-packages/problem_report.py", line 269, in 
extract_keys
  raise ValueError('%s has no binary content' %
  ValueError: ['separator'] has no binary content

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: apport 2.20.11-0ubuntu42
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  ApportVersion: 2.20.11-0ubuntu42
  Architecture: amd64
  CasperMD5CheckResult: skip
  CrashReports:
   640:1000:117:1620030:2020-07-29 12:16:57.045274496 -0400:2020-07-29 
12:19:15.559243636 -0400:/var/crash/_usr_bin_neomutt.1000.crash
   640:1000:117:4399480:2020-07-23 10:30:21.433552906 -0400:2020-07-23 
10:30:18.921508067 -0400:/var/crash/_usr_bin_pavucontrol.1000.crash
   640:1000:117:29909:2020-07-29 12:19:15.603244279 -0400:2020-07-29 
12:19:15.603244279 -0400:/var/crash/_usr_bin_apport-unpack.1000.crash
  CurrentDesktop: i3
  Date: Wed Jul 29 12:22:54 2020
  InstallationDate: Installed on 2019-05-07 (448 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to groovy on 2020-06-22 (37 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1889443/+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 1992172] Re: test_run_crash_kernel fails on ppc64el

[Benjamin Drung]

The autopkgtests for apport 2.20.11-0ubuntu27.27 succeeded:

* amd64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/amd64/a/apport/20230513_042506_dce23@/log.gz
* arm64: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/arm64/a/apport/20230513_011707_2c784@/log.gz
* armhf: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/a/apport/20230513_010336_13a04@/log.gz
* ppc64el: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/ppc64el/a/apport/20230513_011208_bca87@/log.gz
* s390x: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/s390x/a/apport/20230513_005211_9652b@/log.gz


** 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 apport in Ubuntu.
https://bugs.launchpad.net/bugs/1992172

Title:
  test_run_crash_kernel fails on ppc64el

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Bionic:
  New
Status in apport source package in Focal:
  Fix Committed
Status in apport source package in Jammy:
  Fix Released

Bug description:
  [Impact]

  The autopkgtest for apport 2.23.1-0ubuntu1 fails on ppc64el:

  ```
  ==
  FAIL: test_run_crash_kernel (tests.integration.test_ui.T)
  run_crash() for a kernel error
  --
  Traceback (most recent call last):
    File "/usr/lib/python3.10/unittest/mock.py", line 1369, in patched
  return func(*newargs, **newkeywargs)
    File 
"/tmp/autopkgtest.W5WLIN/autopkgtest_tmp/tests/integration/test_ui.py", line 
1617, in test_run_crash_kernel
  self.assertEqual(
  AssertionError: 'http://linux.bugs.example.com/5' != 
'http://linux-signed.bugs.example.com/5'
  - http://linux.bugs.example.com/5
  + http://linux-signed.bugs.example.com/5
  ? +++

  --
  ```

  Full log: https://autopkgtest.ubuntu.com/results/autopkgtest-
  kinetic/kinetic/ppc64el/a/apport/20221007_113450_023d9@/log.gz

  [Test Plan]

  Check that the autopkgtest succeed all architectures (except for
  i386).

  [Where problems could occur]

  The test cases are only part of the apport source package and are not
  copied in any binary packages. Changes to the test will only affect
  the package build and test execution.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1992172/+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 1771041] Re: Remove gconf from Ubuntu

[David D Lowe]

ooo-thumbnailer is an abandoned project and is being removed from
Debian. Project link: https://launchpad.net/ooo-thumbnailer

** Changed in: ooo-thumbnailer (Ubuntu)
   Status: New => Invalid

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

Title:
  Remove gconf from Ubuntu

Status in desktopnova package in Ubuntu:
  New
Status in evolution-indicator package in Ubuntu:
  Fix Released
Status in gconf package in Ubuntu:
  New
Status in gconf-editor package in Ubuntu:
  New
Status in gkdebconf package in Ubuntu:
  New
Status in gnome-mastermind package in Ubuntu:
  New
Status in gnome-phone-manager package in Ubuntu:
  New
Status in gnome-xcf-thumbnailer package in Ubuntu:
  New
Status in gnomint package in Ubuntu:
  New
Status in gtkwave package in Ubuntu:
  Fix Released
Status in guake-indicator package in Ubuntu:
  New
Status in gyrus package in Ubuntu:
  Fix Released
Status in jack-mixer package in Ubuntu:
  Fix Released
Status in jana package in Ubuntu:
  New
Status in mssh package in Ubuntu:
  New
Status in ogmrip package in Ubuntu:
  New
Status in ooo-thumbnailer package in Ubuntu:
  Invalid
Status in planner package in Ubuntu:
  New
Status in ogmrip package in Debian:
  Fix Released

Bug description:
  gconf is being removed from Debian Testing. We should remove it from
  Ubuntu also.

  eclipse is troublesome. At a minimum, we can remove everything but
  eclipse and gconf.

  libgnome is sort of a blocker so do it first LP: #1771031
  And remove libqt-gconf LP: #1740538

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/desktopnova/+bug/1771041/+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 2018425] Re: apt install ubuntu-desktop takes forever

[Olivier Gayot]

Hello and thank you for your bug report,

Marking invalid for subiquity since there is nothing we can do from the
installer's standpoint. Adding ubuntu-meta (which is the source package
for ubuntu-desktop).

Thanks,
Olivier

** Also affects: ubuntu-meta (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: subiquity
   Status: New => Invalid

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

Title:
  apt install ubuntu-desktop takes forever

Status in subiquity:
  Invalid
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Install server 23.04 to take advantage of flexible disk
  partitioning/raid. While installing desktop over the installed server
  (apt install ubuntu-desktop) it proceeds normally about 40% of the way
  but after that it slows down tremendously, hanging for minutes in
  between packages. It eventually (after several hours) completes
  without error.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.04
  Package: subiquity (unknown)
  ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6
  Uname: Linux 6.2.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  3 11:41:00 2023
  InstallationDate: Installed on 2023-04-29 (3 days ago)
  InstallationMedia: Ubuntu-Server 23.04 "Lunar Lobster" - Release amd64 
(20230415)
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  SourcePackage: subiquity
  Symptom: installer
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/2018425/+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 50333] Re: Default configuration file prevents the creation of a valid Certificate Authority

[Adrien Nader]

I'm leaning towards marking this bug as Won't Fix. As stated above, this
is needed by a minority of users and the current configuration (which is
still the same regarding this) is therefore sound for the vast majority
of users. Moreover this would have consequences for this majority of
users as stated in the configuration:

# This goes against PKIX guidelines but some CAs do it and some software
# requires this to avoid interpreting an end user certificate as a CA.

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

Title:
  Default configuration file prevents the creation of a valid
  Certificate Authority

Status in openssl package in Ubuntu:
  Confirmed

Bug description:
  When using the default configuration file and the script
  /usr/lib/ssl/misc/CA.[sh|pl] -newca is run, the certificate authority
  created by the script is not authorized to issue certificates.

  An error is issued by Windows' clients after the certificate is
  imported:

  "This Certificate is not valid because one of the certification
  authorities in the certification path does not appear to be allowed to
  issue certificates or this certificate cannot be used as an end-entity
  certificate."

  To correct the problem, one line needs to be modified in the [
  CA_default ] section of /etc/ssl/openssl.cnf:

  Change this:

  x509_extensions = usr_crt

  To this:

  x509_extensions = v3_ca

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/50333/+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 1832822] Re: functionality stopped working (extra new_oids policy)

[Adrien Nader]

I've tried to reproduce on Lunar and got a CSR. I'm going to mark this
as Fix Released.

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

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

Title:
  functionality stopped working (extra new_oids policy)

Status in openssl package in Ubuntu:
  Fix Released

Bug description:
  Unable to generate certificate request targeting new_oids policy.

  It used to work on this machine, looks like openssl got updated just
  few days ago: 12-06-2019

  The command and exit result:
  gge@itstools-04:~/ssl_ownca/direct_1$ openssl req -new -key direct_1.key -out 
direct_1.csr -subj '/2.5.4.97=direct_1/O=Sample Direct 
1/C=NL/ST=NorthHolland/L=Amsterdam/CN=direct_1.sample.net'problem creating 
object psd2=2.5.4.97
  140648544747968:error:08064066:object identifier routines:OBJ_create:oid 
exists:../crypto/objects/obj_dat.c:709:
  gge@itstools-04:~/ssl_ownca/direct_1$ echo $?
  1

  No CSR file is produced
  (openssl1.1.1-1ubuntu2.1~18.04.1)

  
  re-playing this on different machines provides correct results:
fresh unupdated ubuntu-18.04.1-live-server-amd64.iso install:  openssl   
1.1.0g-2ubuntu4.1
old unupdated CentOS release 6.10 (Final):  openssl-1.0.1e-57.el6.x86_64

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: openssl 1.1.1-1ubuntu2.1~18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  Date: Fri Jun 14 10:00:10 2019
  ProcEnviron:
   LANG=en_US.UTF-8
   SHELL=/bin/bash
   TERM=xterm
   PATH=(custom, no user)
  SourcePackage: openssl
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.ssl.openssl.cnf: 2019-06-14T09:29:39.313665

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1832822/+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 2017990] Re: package linux-image-5.15.0-71-generic 5.15.0-71.78~20.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Christian Neumann]

Warum /root 0 bit vorhanden? Festplatte zeigt über 90 G frei.
LG Christian

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

Title:
  package linux-image-5.15.0-71-generic 5.15.0-71.78~20.04.1 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  None

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.15.0-71-generic 5.15.0-71.78~20.04.1
  ProcVersionSignature: Ubuntu 5.15.0-69.76~20.04.1-generic 5.15.87
  Uname: Linux 5.15.0-69-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.26
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Apr 28 07:53:45 2023
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2021-12-16 (497 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.9
  SourcePackage: initramfs-tools
  Title: package linux-image-5.15.0-71-generic 5.15.0-71.78~20.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2017990/+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 1469834] Re: openssl 1.0.1f-1ubuntu2.15 prevents connection to WPA Enterprise networks

[Adrien Nader]

Thanks for the analysis and testing. I think we can mark this issue as
Won't Fix, especially after all this time.

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

Title:
  openssl 1.0.1f-1ubuntu2.15 prevents connection to WPA Enterprise
  networks

Status in openssl package in Ubuntu:
  Triaged

Bug description:
  The current version of openssl/libssl in Ubuntu 14.04
  (1.0.1f-1ubuntu2.15) breaks wireless connectivity to WPA Enterprise
  networks at my institution.  WPA 2 personal networks are unaffected
  (my home setup).  If I install the "-1ubuntu2.12" version of openssl,
  libssl (amd64 and i386) I can once again connect to the WPA Enterprise
  network (I need to manually restart networking via network-manager
  *and* make sure to kill wpa_supplicant from the command line to make
  sure that the broken library is no longer loaded).


  The WPA Enterprise network in question can be accessed a few different
  ways.  One way uses TLS and certs, the other uses Tunneled TLS, no
  cert, but a username/password combination.  Both methods break upon
  installing the new openssl & libssl.

  I'm marking this as a security vulnerability because the only way (for
  me) to currently access WPA Enterprise networks is to run an older
  version of openssl

  lsb_release -rd
  Description:  Ubuntu 14.04.2 LTS
  Release:  14.04

  *Working* version of package:
  apt-cache policy openssl
  openssl:
Installed: 1.0.1f-1ubuntu2.12
Candidate: 1.0.1f-1ubuntu2.15
Version table:
   1.0.1f-1ubuntu2.15 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu/ trusty-security/main amd64 
Packages
   *** 1.0.1f-1ubuntu2.12 0
  100 /var/lib/dpkg/status
   1.0.1f-1ubuntu2 0
  500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

  The "candidate" version listed above breaks WPA enterprise.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: openssl 1.0.1f-1ubuntu2.12
  ProcVersionSignature: Ubuntu 3.13.0-55.94-generic 3.13.11-ckt20
  Uname: Linux 3.13.0-55-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Jun 29 13:05:58 2015
  SourcePackage: openssl
  UpgradeStatus: Upgraded to trusty on 2014-06-03 (391 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1469834/+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 1820172] Re: [regression] Python async test fails with OpenSSL 1.1.1b

[Adrien Nader]

As far as I understand, this was an issue in python and it has been
fixed. I'm going to mark the openssl side as Invalid.

I guess the python side can be marked as Fix Released but I'll let you
do it.

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

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

Title:
  [regression] Python async test fails with OpenSSL 1.1.1b

Status in Python:
  Fix Released
Status in openssl package in Ubuntu:
  Invalid
Status in python3.7 package in Ubuntu:
  New

Bug description:
  Python async test fails with OpenSSL 1.1.1b, after upgrading from
  1.1.1. Reported also in the Python tracker.

To manage notifications about this bug go to:
https://bugs.launchpad.net/python/+bug/1820172/+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 1842383] Re: openssl 1.1.1 memory overuse/leak

[Adrien Nader]

I expect the fix for this to be shipped already and Ubuntu 18.04 is
reaching end-of-life in a few days. Considering both of these elements,
I'm going to mark this as Fix Released.

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

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

Title:
  openssl 1.1.1 memory overuse/leak

Status in openssl package in Ubuntu:
  Fix Released

Bug description:
  [Impact]

  At some point in the past do_ssl3_write() used to return the number of
  bytes written, or a value <= 0 on error.

  With libssl1.11 it now just returns a success/
  error code and writes the number of bytes written to |tmpwrit|.

  The SSL_MODE_RELEASE_BUFFERS code was still looking at the return code
  for the number of bytes written rather than |tmpwrit|. This has the effect
  that the buffers are not released when they are supposed to be.

  Thus such software as nginx currenty use significantly more memory
  compared to libssl1.0.

  [Test Case]

  Use 'top' to measure the memory usage by nginx with ssl configured.

  Example:

  No memory overuse:
  ii libssl1.1:amd64 1.1.0g-2ubuntu4 amd64 Secure Sockets Layer toolkit - 
shared libraries
  https://launchpadlibrarian.net/442818951/1.1.0g.png

  2,5x memory overuse:
  ii libssl1.1:amd64 1.1.1-1ubuntu2.1~18.04.4 amd64 Secure Sockets Layer 
toolkit - shared libraries
  https://launchpadlibrarian.net/442819146/1.1.1.png

  [Regression Potential]

  Low. This particular fix is tiny
  (https://git.openssl.org/?p=openssl.git;a=commitdiff;h=f2bb79a) and
  has been released and used in a couple of upstream openssl versions
  already without issue.

  [Other Info]
   
  The fix has been tested by nginx team and it solved the memory overuse issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1842383/+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 1802125] Re: openssl 1.1.0 incorrectly verifies certificates with permitted name constraints

[Adrien Nader]

Since the versions currently in Ubuntu contain this fix, I'm going to
mark this bug as Fix Released.

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

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

Title:
  openssl 1.1.0 incorrectly verifies certificates with permitted name
  constraints

Status in openssl package in Ubuntu:
  Fix Released

Bug description:
  Seen on 18.04.1 with openssl/libssl 1.1.0g-2ubuntu4.1

  As per the issue on the openssl github at
  https://github.com/openssl/openssl/issues/5521 - 1.1.0 is overzealous
  about parsing common names as hostnames and this can lead to
  incorrectly rejecting client certificates from CAs with DNS name
  constraints. This is reportedly fixed in 1.1.1.

  Specifically this is an issue in my case because I run an apache2
  server that verifies client certificates on https connections and have
  discovered that some certificates are being rejected because an
  intermediate CA has DNS name constraints which are being unexpectedly
  applied to the CN of client certificates.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1802125/+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 1720643] Re: relocation error: /usr/lib/x86_64-linux-gnu/libssl.so: symbol EVP_rc4, version OPENSSL_1.0.0 not defined in file libcrypto.so.1.0.0 with link time reference

[Adrien Nader]

We're going to mark this as Won't Fix because while the report is about
1.0.x, at the moment it's clear there won't be any more RC4.

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

Title:
  relocation error: /usr/lib/x86_64-linux-gnu/libssl.so: symbol EVP_rc4,
  version OPENSSL_1.0.0 not defined in file libcrypto.so.1.0.0 with link
  time reference

Status in openssl package in Ubuntu:
  New

Bug description:
  relocation error: /usr/lib/x86_64-linux-gnu/libssl.so: symbol EVP_rc4,
  version OPENSSL_1.0.0 not defined in file libcrypto.so.1.0.0 with link
  time reference

  $ dpkg -S /usr/lib/x86_64-linux-gnu/libssl.so
  libssl-dev:amd64: /usr/lib/x86_64-linux-gnu/libssl.so

  $ dpkg -S /usr/lib/x86_64-linux-gnu/libcrypto.so 
  libssl-dev:amd64: /usr/lib/x86_64-linux-gnu/libcrypto.so

  $ apt-cache policy libssl-dev 
  libssl-dev:
Installed: 1.0.2g-1ubuntu4.8
Candidate: 1.0.2g-1ubuntu4.8
Version table:
   *** 1.0.2g-1ubuntu4.8 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1.0.2g-1ubuntu4.6 500
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
   1.0.2g-1ubuntu4 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  I checked openssl changelog, RC4 is not disabled until 1.1.0. Nothing
  in Ubuntu change log for xenial mentioned RC4 removal.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1720643/+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 2003339] Re: kwin_x11: The X11 connection broke: I/O error (code 1)

[Timo Aaltonen]

yes, now that lunar is out, I'd skip kinetic

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

Title:
  kwin_x11: The X11 connection broke: I/O error (code 1)

Status in KDE Base Workspace:
  Fix Released
Status in Mesa:
  Fix Released
Status in kwin package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Fix Released
Status in kwin source package in Jammy:
  Invalid
Status in mesa source package in Jammy:
  Fix Committed
Status in kwin package in Debian:
  New

Bug description:
  [Impact]

  kwin might crash after running some time

  Two commits have been reverted upstream since 22.2.x branch was
  closed, needs those backported to fix this.

  [Test case]

  Run kwin for a day or so, which is usually enough time to hit this.

  Crash happens mostly on a notification popups, so system must be
  actively receiving notifications to test the crash. Without that crash
  may not happen even in a week of runtime.

  [Where things could go wrong]

  This just reverts two commits, and they have been upstream for a few
  months now, so these causing a regression is unlikely.

To manage notifications about this bug go to:
https://bugs.launchpad.net/kdebase-workspace/+bug/2003339/+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