[Touch-packages] [Bug 1396828] Re: package libgl1-mesa-glx:amd64 10.3.0-0ubuntu3 failed to install/upgrade in distribution upgrade

2023-10-16 Thread Launchpad Bug Tracker
[Expired for mesa (Ubuntu) because there has been no activity for 60
days.]

** Changed in: mesa (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  package libgl1-mesa-glx:amd64 10.3.0-0ubuntu3 failed to
  install/upgrade in distribution upgrade

Status in mesa package in Ubuntu:
  Expired

Bug description:
  
  It crashed during the distribution upgrade to 14.10

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: libgl1-mesa-glx:amd64 10.3.0-0ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
  Uname: Linux 3.13.0-39-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Nov 26 18:55:11 2014
  DistUpgraded: 2014-11-26 18:58:05,340 ERROR SystemError from cache.commit(): 
installArchives() failed
  DistroCodename: utopic
  DistroVariant: ubuntu
  DkmsStatus:
   fglrx-updates-core, 14.201, 3.13.0-39-generic, x86_64: installed
   fglrx-updates-core, 14.201, 3.16.0-25-generic, x86_64: installed
  DuplicateSignature: package:libgl1-mesa-glx:amd64:10.3.0-0ubuntu3:subprocess 
installed post-installation script returned error exit status 2
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:195e]
   Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8670A/8670M/8750M] 
[1002:6600] (rev ff) (prog-if ff)
  InstallationDate: Installed on 2014-06-12 (167 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Hewlett-Packard HP ENVY Sleekbook 6
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-39-generic.efi.signed 
root=UUID=27b97477-54ab-4447-a6ae-1beeef50d0b7 ro splash quiet
  SourcePackage: mesa
  Title: package libgl1-mesa-glx:amd64 10.3.0-0ubuntu3 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 2
  UpgradeStatus: Upgraded to utopic on 2014-11-26 (0 days ago)
  dmi.bios.date: 01/15/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.23
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 195E
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 72.66
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.23:bd01/15/2013:svnHewlett-Packard:pnHPENVYSleekbook6:pvr088612305A0320100:rvnHewlett-Packard:rn195E:rvr72.66:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY Sleekbook 6
  dmi.product.version: 088612305A0320100
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12+14.10.20140918-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.56-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.3.0-0ubuntu3
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.3.0-0ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.16.0-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.0-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.4.0-2ubuntu2
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.914-1~exp1ubuntu4.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu2
  xserver.bootTime: Tue Nov 25 23:37:05 2014
  xserver.configfile: default
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5558 
   vendor CMN
  xserver.version: 2:1.15.1-0ubuntu2.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1396828/+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 1439994] Re: package libegl1-mesa-dev (not installed) failed to install/upgrade: Versuch, »/usr/include/EGL/eglext.h« zu überschreiben, welches auch in Paket libraspberrypi-dev 1

2023-10-16 Thread Launchpad Bug Tracker
[Expired for mesa (Ubuntu) because there has been no activity for 60
days.]

** Changed in: mesa (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  package libegl1-mesa-dev (not installed) failed to install/upgrade:
  Versuch, »/usr/include/EGL/eglext.h« zu überschreiben, welches auch in
  Paket libraspberrypi-dev 1.20150323.7650bcb-1 ist

Status in mesa package in Ubuntu:
  Expired

Bug description:
  appeared after installation of package qtcreator on a raspberry pi 2
  via apt-get

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libegl1-mesa-dev (not installed)
  ProcVersionSignature: Ubuntu 3.18.0-20.20-rpi2 3.18.10
  Uname: Linux 3.18.0-20-rpi2 armv7l
  ApportVersion: 2.14.1-0ubuntu3.8
  Architecture: armhf
  Date: Fri Apr  3 10:20:45 2015
  DuplicateSignature: package:libegl1-mesa-dev:(not installed):Versuch, 
»/usr/include/EGL/eglext.h« zu überschreiben, welches auch in Paket 
libraspberrypi-dev 1.20150323.7650bcb-1 ist
  ErrorMessage: Versuch, »/usr/include/EGL/eglext.h« zu überschreiben, welches 
auch in Paket libraspberrypi-dev 1.20150323.7650bcb-1 ist
  SourcePackage: mesa
  Title: package libegl1-mesa-dev (not installed) failed to install/upgrade: 
Versuch, »/usr/include/EGL/eglext.h« zu überschreiben, welches auch in Paket 
libraspberrypi-dev 1.20150323.7650bcb-1 ist
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1439994/+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 1449246] Re: package libgl1-mesa-glx 8.0.4-0ubuntu0.7 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 135

2023-10-16 Thread Launchpad Bug Tracker
[Expired for mesa (Ubuntu) because there has been no activity for 60
days.]

** Changed in: mesa (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  package libgl1-mesa-glx 8.0.4-0ubuntu0.7 failed to install/upgrade:
  ErrorMessage: subprocess installed post-installation script returned
  error exit status 135

Status in mesa package in Ubuntu:
  Expired

Bug description:
  sistem not working

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: libgl1-mesa-glx 8.0.4-0ubuntu0.7
  ProcVersionSignature: Ubuntu 3.2.0-80.116-generic 3.2.68
  Uname: Linux 3.2.0-80-generic i686
  ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: i386
  Date: Mon Apr 27 14:53:27 2015
  ErrorMessage: ErrorMessage: subprocess installed post-installation script 
returned error exit status 135
  InstallationMedia: Zorin OS 6 Lite - Release i386
  MarkForUpload: True
  SourcePackage: mesa
  Title: package libgl1-mesa-glx 8.0.4-0ubuntu0.7 failed to install/upgrade: 
ErrorMessage: subprocess installed post-installation script returned error exit 
status 135
  UpgradeStatus: Upgraded to precise on 2015-04-27 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1449246/+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 1584425] Re: package libgl1-mesa-glx:armhf 10.1.3-0ubuntu0.6 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139

2023-10-16 Thread Launchpad Bug Tracker
[Expired for mesa (Ubuntu) because there has been no activity for 60
days.]

** Changed in: mesa (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  package libgl1-mesa-glx:armhf 10.1.3-0ubuntu0.6 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 139

Status in mesa package in Ubuntu:
  Expired

Bug description:
  libgl1-mesa-glx:armhf gave segmentation fault during install on nvidia
  tx1 with

   Linux tegra-ubuntu 3.10.96-tegra #1 SMP PREEMPT Tue May 17 16:29:05
  PDT 2016 aarch64

  kernel from new 24.1 install 14.04 ubuntu 64bit kernel/userspace

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libgl1-mesa-glx:armhf 10.1.3-0ubuntu0.6
  Uname: Linux 3.10.96-tegra aarch64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.20
  Architecture: arm64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat May 21 21:32:53 2016
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DuplicateSignature: 
package:libgl1-mesa-glx:armhf:10.1.3-0ubuntu0.6:subprocess installed 
post-installation script returned error exit status 139
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 139
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   
  Lspci:
   
  PackageArchitecture: armhf
  ProcKernelCmdLine: fbcon=map:0 console=tty0 console=ttyS0,115200n8 
androidboot.modem=none androidboot.serialno=P2180A00P00940c003fd 
androidboot.security=non-secure tegraid=21.1.2.0.0 ddr_die=2048M@2048M 
ddr_die=2048M@4096M section=256M memtype=0 vpr_resize usb_port_owner_info=0 
lane_owner_info=0 emc_max_dvfs=0 touch_id=0@63 video=tegrafb 
no_console_suspend=1 debug_uartport=lsport,0 
earlyprintk=uart8250-32bit,0x70006000 maxcpus=4 usbcore.old_scheme_first=1 
lp0_vec=0x1000@0xff2bf000 nvdumper_reserved=0xff23f000 core_edp_mv=1125 
core_edp_ma=4000 gpt android.kerneltype=normal androidboot.touch_vendor_id=0 
androidboot.touch_panel_id=63 androidboot.touch_feature=0 
androidboot.bootreason=pmc:software_reset,pmic:0x0 root=/dev/mmcblk0p1 rw 
rootwait
  ProcModules:
   bcmdhd 7453607 0 - Live 0xffbffc879000
   bluedroid_pm 11452 0 - Live 0xffbffc00
   bnep 14864 2 - Live 0xffbffc007000
   cfg80211 452766 1 bcmdhd, Live 0xffbffc01
   rfcomm 66118 0 - Live 0xffbffc142000
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.6
   apt  1.0.1ubuntu2.13
  SourcePackage: mesa
  Title: package libgl1-mesa-glx:armhf 10.1.3-0ubuntu0.6 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 139
  UpgradeStatus: No upgrade log present (probably fresh install)
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.libdrm2: libdrm2 2.4.64-1~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sat May 21 20:28:11 2016
  xserver.configfile: /etc/X11/xorg.conf
  xserver.devices:
   inputgpio-keysKEYBOARD, id 6
   inputtegra-snd-t210ref-mobile-rt565x Headphone Jack KEYBOARD, id 7
   inputPixArt Microsoft USB Optical Mouse MOUSE, id 8
   inputMicrosoft Wired Keyboard 600 KEYBOARD, id 9
   inputMicrosoft Wired Keyboard 600 KEYBOARD, id 10
  xserver.errors:
   NVIDIA(0): Failed to allocate NVIDIA Error Handler
   NVIDIA(0): Failed to allocate NVIDIA Damage Manager
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.15.1-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1584425/+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 1706887] Re: package libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 [modified: usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz usr/share/doc/libgl1-mesa-dri/copyright] failed to insta

2023-10-16 Thread Launchpad Bug Tracker
[Expired for mesa (Ubuntu) because there has been no activity for 60
days.]

** Changed in: mesa (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  package libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 [modified:
  usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz
  usr/share/doc/libgl1-mesa-dri/copyright] failed to install/upgrade: no
  se pudieron copiar los datos extraídos de './usr/lib/x86_64-linux-
  gnu/dri/virtio_gpu_dri.so' a '/usr/lib/x86_64-linux-
  gnu/dri/virtio_gpu_dri.so.dpkg-new': fin de fichero o de flujo
  inesperado

Status in mesa package in Ubuntu:
  Expired

Bug description:
  ...

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 [modified: 
usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz 
usr/share/doc/libgl1-mesa-dri/copyright]
  ProcVersionSignature: Ubuntu 4.10.0-27.30~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-27-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Es un directorio: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.66  Mon May  1 15:29:16 
PDT 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Jul 27 10:43:44 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ErrorMessage: no se pudieron copiar los datos extraídos de 
'./usr/lib/x86_64-linux-gnu/dri/virtio_gpu_dri.so' a 
'/usr/lib/x86_64-linux-gnu/dri/virtio_gpu_dri.so.dpkg-new': fin de fichero o de 
flujo inesperado
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics 
Controller [1043:1477]
 Subsystem: ASUSTeK Computer Inc. GK107M [GeForce GT 740M] [1043:1477]
  InstallationDate: Installed on 2017-07-05 (21 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  MachineType: ASUSTeK COMPUTER INC. N46VB
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-27-generic 
root=UUID=cc5fe0fa-835e-47f5-8433-3071c5503421 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: mesa
  Title: package libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1 [modified: 
usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz 
usr/share/doc/libgl1-mesa-dri/copyright] failed to install/upgrade: no se 
pudieron copiar los datos extraídos de 
'./usr/lib/x86_64-linux-gnu/dri/virtio_gpu_dri.so' a 
'/usr/lib/x86_64-linux-gnu/dri/virtio_gpu_dri.so.dpkg-new': fin de fichero o de 
flujo inesperado
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/31/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N46VB.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N46VB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN46VB.204:bd01/31/2013:svnASUSTeKCOMPUTERINC.:pnN46VB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN46VB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N46VB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Thu Jul 27 10:40:36 2017
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6.1~16.04.2

To manage 

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

2023-10-16 Thread Tim Richardson
Janus, your kernel is old and does not match a desktop (HWE) kernel for
22.04.3, so I guess this is a server install of Ubuntu. How are you
connecting to it?

On Tue, 17 Oct 2023 at 13:21, Janus Kobain <1951...@bugs.launchpad.net>
wrote:

> In GNOME Terminal:
> $ chromium
> /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-404feab7-2748-4d47-ad69-3cceb67db014.scope
> is not a snap cgroup
>
> In xterm:
> $ chromium
> /user.slice/user-1000.slice/session-2.scope is not a snap cgroup
>
>
> $ lsb_release -a; uname -a
> No LSB modules are available.
> Distributor ID: Ubuntu
> Description:Ubuntu 22.04.3 LTS
> Release:22.04
> Codename:   jammy
> Linux panama 5.15.0-85-generic #95-Ubuntu SMP Fri Sep 1 15:02:17 UTC 2023
> x86_64 x86_64 x86_64 GNU/Linux
>
> Started happening out of nowhere several hours ago, now I'm afraid to
> restart Firefox.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1951491
>
> Title:
>   Can't run snaps: .slice/session-1.scope is not a snap cgroup
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/x2go/+bug/1951491/+subscriptions
>
>

-- 
Tim Richardson

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

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

Status in X2Go:
  New
Status in Xpra Terminal Server:
  New
Status in snapd package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Incomplete
Status in x2goserver package in Ubuntu:
  Confirmed
Status in snapd package in Debian:
  New
Status in snapd package in Fedora:
  New

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

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

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

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

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

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

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/x2go/+bug/1951491/+subscriptions


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


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

2023-10-16 Thread Janus Kobain
In GNOME Terminal:
$ chromium
/user.slice/user-1000.slice/user@1000.service/app.slice/app-org.gnome.Terminal.slice/vte-spawn-404feab7-2748-4d47-ad69-3cceb67db014.scope
 is not a snap cgroup

In xterm:
$ chromium
/user.slice/user-1000.slice/session-2.scope is not a snap cgroup


$ lsb_release -a; uname -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 22.04.3 LTS
Release:22.04
Codename:   jammy
Linux panama 5.15.0-85-generic #95-Ubuntu SMP Fri Sep 1 15:02:17 UTC 2023 
x86_64 x86_64 x86_64 GNU/Linux

Started happening out of nowhere several hours ago, now I'm afraid to
restart Firefox.

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

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

Status in X2Go:
  New
Status in Xpra Terminal Server:
  New
Status in snapd package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Incomplete
Status in x2goserver package in Ubuntu:
  Confirmed
Status in snapd package in Debian:
  New
Status in snapd package in Fedora:
  New

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

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

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

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

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

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

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

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/x2go/+bug/1951491/+subscriptions


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


[Touch-packages] [Bug 1957816] Re: Wayland dual monitor switch from 30Hz to 60Hz: High pitch audio double playback speed

2023-10-16 Thread Sam Wise
Same issue here.  AMD gpu, two 4k monitors, one on Display Port @ 60Hz
and The other on HDMI @ 60Hz with audio playback high pitched and
increased speed. Lowering the HDMI refresh rate to 30Hz fixes the audio.

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

Title:
  Wayland dual monitor switch from 30Hz to 60Hz: High pitch audio double
  playback speed

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I have a desktop computer with a 60Hz 4K display connected through Display 
Port. The display is a ThinkVision X1 with built in audio. With the Display 
Port cable I am then able to output sound from the monitor and this works 
without any issues.
  I have now added a 4K Samsung television through HDMI to the same GPU, which 
also allows me to do 4K at 60Hz, albeit only with Wayland. In Xorg I can only 
do 30Hz on the television while doing 60Hz on the ThinkVision X1. It is clear 
however, that when it is set to 60Hz in Wayland, the animation on the 
television is much more smooth. 

  The problem is that whenever I set the television to 60Hz, the playback of 
any sound is both high pitched and faster than normal. If I play a video in 
YouTube, the video appears to playback about twice as fast as normal and and 
very high pitched sound (everyone sounds like chipmunks). This is the case on 
the entire system (also when playing the video or any other sounds on the X1 
display at 60Hz). Only if I set the refresh rate, on the television, to 30Hz 
again does everything play and sound normal again. 
  It is only the playback of media that is doubled in speed. Everything else 
(animations, mouse, etc.) is still behaving as normal.

  If I change audio output to the ThinkVision X1 (or something else) at
  60Hz while also being connected to the television at 60Hz, the audio
  stays high pitched and sped up.

  If I unplug the main display, ThinkVision X1, then the playback of
  media on the television becomes normal.

  I have tried with different +100 USD HDMI cables, that are all rated
  as HDMI 2.0 and the behavior stays the same.

  My system is Ubuntu 20.04 LTS. I tried in a LiveUSB 21.10, but the
  behavior was the same.

  I have an AMD Radeon VII GPU (Has 3x Display Port and 1x HDMI).

  As mentioned I cannot test it in Xorg, but that is only because it
  does not allow me to set the refresh rate to 60Hz.

  I am uncertain whether this is related to MESA, Pulseaudio or maybe
  Mutter/Wayland?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1957816/+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 2039508] Re: Enable HISTTIMEFORMAT in /etc/skel/.bashrc by default

2023-10-16 Thread Haw Loeung
** Tags added: canonical-is

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

Title:
  Enable HISTTIMEFORMAT in /etc/skel/.bashrc by default

Status in bash package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  /etc/skel/.bashrc has the following:

  | # don't put duplicate lines or lines starting with space in the history.
  | # See bash(1) for more options
  | HISTCONTROL=ignoreboth
  |
  | # append to the history file, don't overwrite it
  | shopt -s histappend
  |
  | # for setting history length see HISTSIZE and HISTFILESIZE in bash(1)
  | HISTSIZE=1000
  | HISTFILESIZE=2000

  It would be nice to also include HISTTIMEFORMAT. Something like
  `HISTTIMEFORMAT='%F %T '`. It helps to serve as a little audit trail.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/2039508/+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 2039508] Re: Enable HISTTIMEFORMAT in /etc/skel/.bashrc by default

2023-10-16 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Enable HISTTIMEFORMAT in /etc/skel/.bashrc by default

Status in bash package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  /etc/skel/.bashrc has the following:

  | # don't put duplicate lines or lines starting with space in the history.
  | # See bash(1) for more options
  | HISTCONTROL=ignoreboth
  |
  | # append to the history file, don't overwrite it
  | shopt -s histappend
  |
  | # for setting history length see HISTSIZE and HISTFILESIZE in bash(1)
  | HISTSIZE=1000
  | HISTFILESIZE=2000

  It would be nice to also include HISTTIMEFORMAT. Something like
  `HISTTIMEFORMAT='%F %T '`. It helps to serve as a little audit trail.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/2039508/+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 2039508] [NEW] Enable HISTTIMEFORMAT in /etc/skel/.bashrc by default

2023-10-16 Thread Haw Loeung
Public bug reported:

Hi,

/etc/skel/.bashrc has the following:

| # don't put duplicate lines or lines starting with space in the history.
| # See bash(1) for more options
| HISTCONTROL=ignoreboth
|
| # append to the history file, don't overwrite it
| shopt -s histappend
|
| # for setting history length see HISTSIZE and HISTFILESIZE in bash(1)
| HISTSIZE=1000
| HISTFILESIZE=2000

It would be nice to also include HISTTIMEFORMAT. Something like
`HISTTIMEFORMAT='%F %T '`. It helps to serve as a little audit trail.

** Affects: bash (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: canonical-is

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

Title:
  Enable HISTTIMEFORMAT in /etc/skel/.bashrc by default

Status in bash package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  /etc/skel/.bashrc has the following:

  | # don't put duplicate lines or lines starting with space in the history.
  | # See bash(1) for more options
  | HISTCONTROL=ignoreboth
  |
  | # append to the history file, don't overwrite it
  | shopt -s histappend
  |
  | # for setting history length see HISTSIZE and HISTFILESIZE in bash(1)
  | HISTSIZE=1000
  | HISTFILESIZE=2000

  It would be nice to also include HISTTIMEFORMAT. Something like
  `HISTTIMEFORMAT='%F %T '`. It helps to serve as a little audit trail.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/2039508/+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 2039411] Re: Addition of ppa repository failing intermittently

2023-10-16 Thread Oleg Grenrus
I facing this issue while doing just

apt-add-repository -y 'ppa:hvr/ghc'

i.e. no `/ubungu` nor tilde. This is on Ubuntu 18.06, so maybe it's old
apt-add-repository which does some rewriting?

E.g. in fresh buildpack-deps:bionic Docker container this fails 100% of
the time

apt-get update
apt-get install -y --no-install-recommends gnupg ca-certificates dirmngr 
curl git software-properties-common libtinfo5
apt-add-repository -y 'ppa:hvr/ghc'

Either with JSONDecodeError or with "Cannot add PPA:
'ppa:~hvr/ubuntu/ghc'."

EDIT: seems to work on focal.

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

Title:
  Addition of ppa repository failing intermittently

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  I get following error intermittently when trying to add ppa repository:
  $ sudo add-apt-repository ppa:~longsleep/ubuntu/golang-backports
  Cannot add PPA: 'ppa:~longsleep/ubuntu/golang-backports'.
  The user named '~longsleep' has no PPA named 'ubuntu/golang-backports'
  Please choose from the following available PPAs:
   * 'bcmwl':  bcmwl
   * 'couchdb':  Apache CouchDB
   * 'couchdb-precise-backport':  Apache CouchDB with Erlang 18 for precise
   * 'createrepo-backports':  Createrepo Backports
   * 'firehol-backports':  Firehol Backports
   * 'golang-backports':  Golang Backports
   * 'golang-backports-dev':  Golang Backports Dev
   * 'iridium-browser-dev':  Iridium Browser Dev dependencies
   * 'pixel-extras':  Pixel extras
   * 'python2.7-backports':  Python 2.7 Backports
   * 'python3-m2crypto-backports':  Python 3 M2Crypto backports
   * 'stuff':  Stuff
   * 'ubuntu-pine64-flavour-makers':  Ubuntu Pine64 Makers PPA

  After multiple attempts, it may succeed, but the same above command sometimes 
may return following error as well (intermittently):
  $ sudo add-apt-repository ppa:~longsleep/ubuntu/golang-backports
  Traceback (most recent call last):
File "/usr/bin/add-apt-repository", line 137, in 
  shortcut = shortcut_handler(line)
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
885, in shortcut_handler
  ret = factory(shortcut)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 469, 
in shortcut_handler
  return PPAShortcutHandler(shortcut)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 426, 
in __init__
  info = get_ppa_info(self.shortcut)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 392, 
in get_ppa_info
  _get_suggested_ppa_message(user, ppa))
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 349, 
in _get_suggested_ppa_message
  lp_user = get_info_from_lp(LAUNCHPAD_USER_API % user)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 104, 
in get_info_from_lp
  return get_info_from_https(lp_url, True)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 98, 
in get_info_from_https
  return json.loads(data)
File "/usr/lib/python3.8/json/__init__.py", line 357, in loads
  return _default_decoder.decode(s)
File "/usr/lib/python3.8/json/decoder.py", line 337, in decode
  obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/usr/lib/python3.8/json/decoder.py", line 355, in raw_decode
  raise JSONDecodeError("Expecting value", s, err.value) from None
  json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2039411/+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 2039503] Re: package network-manager 1.44.2-1ubuntu1 failed to install/upgrade: installed network-manager package post-installation script subprocess returned error exit status 1

2023-10-16 Thread Steve Langasek
other connections also had . in the name and had no problem migrating.

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

** Tags added: foundations-todo

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

Title:
  package network-manager 1.44.2-1ubuntu1 failed to install/upgrade:
  installed network-manager package post-installation script subprocess
  returned error exit status 10

Status in network-manager package in Ubuntu:
  New
Status in network-manager source package in Mantic:
  New

Bug description:
  lunar to mantic upgrade, exciting to see output from network-manager
  postinst migrating connections to /etc/netplan one by one.  But then:

  Error: 491fa5c8-68ef-4140-8679-dca422f5c262 - no such connection profile.
  dpkg: error processing package network-manager (--configure):
   installed network-manager package post-installation script subprocess 
returned error exit status 10

  That UUID appears in a file /etc/NetworkManager/system-
  connections/UPTOWN.guests that hasn't been touched since 2015.

  Contents of the file were:

  [connection]
  id=UPTOWN.guests
  uuid=491fa5c8-68ef-4140-8679-dca422f5c262
  type=wifi

  [wifi]
  ssid=UPTOWN.guests
  mode=infrastructure
  mac-address=E0:9D:31:09:84:54

  [ipv6]
  method=auto

  [ipv4]
  method=auto

  
  I've removed it from disk and the migration continued to completion.

  Then I got another failure on:

  [connection]
  id=belkin.1e4.guests
  uuid=2c77e512-f3e3-4238-b401-c94559cc6db0
  type=802-11-wireless

  [802-11-wireless]
  ssid=belkin.1e4.guests
  mode=infrastructure
  mac-address=00:24:D7:1F:EA:20

  [ipv6]
  method=auto

  [ipv4]
  method=auto

  Is it unhappy because of the . in the names?

  ProblemType: Package
  DistroRelease: Ubuntu 23.10
  Package: network-manager 1.44.2-1ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-34.34-generic 6.2.16
  Uname: Linux 6.2.0-34-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Mon Oct 16 16:12:43 2023
  ErrorMessage: installed network-manager package post-installation script 
subprocess returned error exit status 10
  InstallationDate: Installed on 2019-12-23 (1393 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.22.0ubuntu1
   apt  2.7.3
  SourcePackage: network-manager
  Title: package network-manager 1.44.2-1ubuntu1 failed to install/upgrade: 
installed network-manager package post-installation script subprocess returned 
error exit status 10
  UpgradeStatus: Upgraded to mantic on 2023-10-16 (0 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.44.2   connected  started  full  enabled enabled  
enabled  missing  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2039503/+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 2039503] [NEW] package network-manager 1.44.2-1ubuntu1 failed to install/upgrade: installed network-manager package post-installation script subprocess returned error exit status

2023-10-16 Thread Steve Langasek
Public bug reported:

lunar to mantic upgrade, exciting to see output from network-manager
postinst migrating connections to /etc/netplan one by one.  But then:

Error: 491fa5c8-68ef-4140-8679-dca422f5c262 - no such connection profile.
dpkg: error processing package network-manager (--configure):
 installed network-manager package post-installation script subprocess returned 
error exit status 10

That UUID appears in a file /etc/NetworkManager/system-
connections/UPTOWN.guests that hasn't been touched since 2015.

Contents of the file were:

[connection]
id=UPTOWN.guests
uuid=491fa5c8-68ef-4140-8679-dca422f5c262
type=wifi

[wifi]
ssid=UPTOWN.guests
mode=infrastructure
mac-address=E0:9D:31:09:84:54

[ipv6]
method=auto

[ipv4]
method=auto


I've removed it from disk and the migration continued to completion.

Then I got another failure on:

[connection]
id=belkin.1e4.guests
uuid=2c77e512-f3e3-4238-b401-c94559cc6db0
type=802-11-wireless

[802-11-wireless]
ssid=belkin.1e4.guests
mode=infrastructure
mac-address=00:24:D7:1F:EA:20

[ipv6]
method=auto

[ipv4]
method=auto

Is it unhappy because of the . in the names?

ProblemType: Package
DistroRelease: Ubuntu 23.10
Package: network-manager 1.44.2-1ubuntu1
ProcVersionSignature: Ubuntu 6.2.0-34.34-generic 6.2.16
Uname: Linux 6.2.0-34-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
CasperMD5CheckResult: unknown
Date: Mon Oct 16 16:12:43 2023
ErrorMessage: installed network-manager package post-installation script 
subprocess returned error exit status 10
InstallationDate: Installed on 2019-12-23 (1393 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
PythonDetails: N/A
RebootRequiredPkgs: Error: path contained symlinks.
RelatedPackageVersions:
 dpkg 1.22.0ubuntu1
 apt  2.7.3
SourcePackage: network-manager
Title: package network-manager 1.44.2-1ubuntu1 failed to install/upgrade: 
installed network-manager package post-installation script subprocess returned 
error exit status 10
UpgradeStatus: Upgraded to mantic on 2023-10-16 (0 days ago)
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.44.2   connected  started  full  enabled enabled  
enabled  missing  enabled

** Affects: network-manager (Ubuntu)
 Importance: Critical
 Status: New

** Affects: network-manager (Ubuntu Mantic)
 Importance: Critical
 Status: New


** Tags: amd64 apport-package foundations-todo mantic need-duplicate-check

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => Critical

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

Title:
  package network-manager 1.44.2-1ubuntu1 failed to install/upgrade:
  installed network-manager package post-installation script subprocess
  returned error exit status 10

Status in network-manager package in Ubuntu:
  New
Status in network-manager source package in Mantic:
  New

Bug description:
  lunar to mantic upgrade, exciting to see output from network-manager
  postinst migrating connections to /etc/netplan one by one.  But then:

  Error: 491fa5c8-68ef-4140-8679-dca422f5c262 - no such connection profile.
  dpkg: error processing package network-manager (--configure):
   installed network-manager package post-installation script subprocess 
returned error exit status 10

  That UUID appears in a file /etc/NetworkManager/system-
  connections/UPTOWN.guests that hasn't been touched since 2015.

  Contents of the file were:

  [connection]
  id=UPTOWN.guests
  uuid=491fa5c8-68ef-4140-8679-dca422f5c262
  type=wifi

  [wifi]
  ssid=UPTOWN.guests
  mode=infrastructure
  mac-address=E0:9D:31:09:84:54

  [ipv6]
  method=auto

  [ipv4]
  method=auto

  
  I've removed it from disk and the migration continued to completion.

  Then I got another failure on:

  [connection]
  id=belkin.1e4.guests
  uuid=2c77e512-f3e3-4238-b401-c94559cc6db0
  type=802-11-wireless

  [802-11-wireless]
  ssid=belkin.1e4.guests
  mode=infrastructure
  mac-address=00:24:D7:1F:EA:20

  [ipv6]
  method=auto

  [ipv4]
  method=auto

  Is it unhappy because of the . in the names?

  ProblemType: Package
  DistroRelease: Ubuntu 23.10
  Package: network-manager 1.44.2-1ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-34.34-generic 6.2.16
  Uname: Linux 6.2.0-34-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: unknown
  Date: Mon Oct 16 16:12:43 2023
  ErrorMessage: installed network-manager package post-installation script 
subprocess returned error exit 

[Touch-packages] [Bug 1957819] Re: Wayland dual monitor switch from 30Hz to 60Hz: High pitch audio double playback speed

2023-10-16 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: alsa-driver (Ubuntu)
   Status: New => Confirmed

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

Title:
  Wayland dual monitor switch from 30Hz to 60Hz: High pitch audio double
  playback speed

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I described the issue here first:
  https://bugs.launchpad.net/ubuntu/+bug/1957816

  I am not sure it belongs here, but after the initial report i made an
  audio issue report with `ubuntu-bug -s audio`

  copy/paste:

  I have a desktop computer with a 60Hz 4K display connected through Display 
Port. The display is a ThinkVision X1 with built in audio. With the Display 
Port cable I am then able to output sound from the monitor and this works 
without any issues.
  I have now added a 4K Samsung television through HDMI to the same GPU, which 
also allows me to do 4K at 60Hz, albeit only with Wayland. In Xorg I can only 
do 30Hz on the television while doing 60Hz on the ThinkVision X1. It is clear 
however, that when it is set to 60Hz in Wayland, the animation on the 
television is much more smooth.

  The problem is that whenever I set the television to 60Hz, the playback of 
any sound is both high pitched and faster than normal. If I play a video in 
YouTube, the video appears to playback about twice as fast as normal and and 
very high pitched sound (everyone sounds like chipmunks). This is the case on 
the entire system (also when playing the video or any other sounds on the X1 
display at 60Hz). Only if I set the refresh rate, on the television, to 30Hz 
again does everything play and sound normal again.
  It is only the playback of media that is doubled in speed. Everything else 
(animations, mouse, etc.) is still behaving as normal.

  If I change audio output to the ThinkVision X1 (or something else) at
  60Hz while also being connected to the television at 60Hz, the audio
  stays high pitched and sped up.

  If I unplug the main display, ThinkVision X1, then the playback of
  media on the television becomes normal.

  I have tried with different +100 USD HDMI cables, that are all rated
  as HDMI 2.0 and the behavior stays the same.

  My system is Ubuntu 20.04 LTS. I tried in a LiveUSB 21.10, but the
  behavior was the same.

  I have an AMD Radeon VII GPU (Has 3x Display Port and 1x HDMI).

  As mentioned I cannot test it in Xorg, but that is only because it
  does not allow me to set the refresh rate to 60Hz.

  I am uncertain whether this is related to MESA, Pulseaudio or maybe
  Mutter/Wayland?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.13.0-25.26~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 13 17:24:02 2022
  InstallationDate: Installed on 2020-05-03 (620 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI successful
  Symptom_Card: Vega 20 HDMI Audio [Radeon VII] - HDA ATI HDMI
  Symptom_Jack: Digital Out, HDMI
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [System Product Name, ATI R6xx HDMI, Digital Out, HDMI] Playback 
problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 8101
  dmi.board.asset.tag: Default string
  dmi.board.name: CROSSHAIR VI HERO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr8101:bd07/15/2021:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnCROSSHAIRVIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1957819/+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 1957816] Re: Wayland dual monitor switch from 30Hz to 60Hz: High pitch audio double playback speed

2023-10-16 Thread tack22
Very similar issue over here. I can logon to X11 and run 4k at 60 Hz
without issue. However, when I logon to Wayland and run 4k at 60 Hz all
audio and video plays back at 2x-3x speed (YouTube, VLC, mp3, etc). I
have an AMD GPU and am running off the DisplayPort through a DisplayPort
to HDMI adapter, although the same issue occurs if I utilize the HDMI
directly.

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

Title:
  Wayland dual monitor switch from 30Hz to 60Hz: High pitch audio double
  playback speed

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I have a desktop computer with a 60Hz 4K display connected through Display 
Port. The display is a ThinkVision X1 with built in audio. With the Display 
Port cable I am then able to output sound from the monitor and this works 
without any issues.
  I have now added a 4K Samsung television through HDMI to the same GPU, which 
also allows me to do 4K at 60Hz, albeit only with Wayland. In Xorg I can only 
do 30Hz on the television while doing 60Hz on the ThinkVision X1. It is clear 
however, that when it is set to 60Hz in Wayland, the animation on the 
television is much more smooth. 

  The problem is that whenever I set the television to 60Hz, the playback of 
any sound is both high pitched and faster than normal. If I play a video in 
YouTube, the video appears to playback about twice as fast as normal and and 
very high pitched sound (everyone sounds like chipmunks). This is the case on 
the entire system (also when playing the video or any other sounds on the X1 
display at 60Hz). Only if I set the refresh rate, on the television, to 30Hz 
again does everything play and sound normal again. 
  It is only the playback of media that is doubled in speed. Everything else 
(animations, mouse, etc.) is still behaving as normal.

  If I change audio output to the ThinkVision X1 (or something else) at
  60Hz while also being connected to the television at 60Hz, the audio
  stays high pitched and sped up.

  If I unplug the main display, ThinkVision X1, then the playback of
  media on the television becomes normal.

  I have tried with different +100 USD HDMI cables, that are all rated
  as HDMI 2.0 and the behavior stays the same.

  My system is Ubuntu 20.04 LTS. I tried in a LiveUSB 21.10, but the
  behavior was the same.

  I have an AMD Radeon VII GPU (Has 3x Display Port and 1x HDMI).

  As mentioned I cannot test it in Xorg, but that is only because it
  does not allow me to set the refresh rate to 60Hz.

  I am uncertain whether this is related to MESA, Pulseaudio or maybe
  Mutter/Wayland?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1957816/+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 1957819] Re: Wayland dual monitor switch from 30Hz to 60Hz: High pitch audio double playback speed

2023-10-16 Thread tack22
Very similar issue over here. I can logon to X11 and run 4k at 60 Hz
without issue. However, when I logon to Wayland and run 4k at 60 Hz all
audio and video plays back at 2x-3x speed (YouTube, VLC, mp3, etc). I
have an AMD GPU and am running off the DisplayPort through a DisplayPort
to HDMI adapter, although the same issue occurs if I utilize the HDMI
directly.

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

Title:
  Wayland dual monitor switch from 30Hz to 60Hz: High pitch audio double
  playback speed

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I described the issue here first:
  https://bugs.launchpad.net/ubuntu/+bug/1957816

  I am not sure it belongs here, but after the initial report i made an
  audio issue report with `ubuntu-bug -s audio`

  copy/paste:

  I have a desktop computer with a 60Hz 4K display connected through Display 
Port. The display is a ThinkVision X1 with built in audio. With the Display 
Port cable I am then able to output sound from the monitor and this works 
without any issues.
  I have now added a 4K Samsung television through HDMI to the same GPU, which 
also allows me to do 4K at 60Hz, albeit only with Wayland. In Xorg I can only 
do 30Hz on the television while doing 60Hz on the ThinkVision X1. It is clear 
however, that when it is set to 60Hz in Wayland, the animation on the 
television is much more smooth.

  The problem is that whenever I set the television to 60Hz, the playback of 
any sound is both high pitched and faster than normal. If I play a video in 
YouTube, the video appears to playback about twice as fast as normal and and 
very high pitched sound (everyone sounds like chipmunks). This is the case on 
the entire system (also when playing the video or any other sounds on the X1 
display at 60Hz). Only if I set the refresh rate, on the television, to 30Hz 
again does everything play and sound normal again.
  It is only the playback of media that is doubled in speed. Everything else 
(animations, mouse, etc.) is still behaving as normal.

  If I change audio output to the ThinkVision X1 (or something else) at
  60Hz while also being connected to the television at 60Hz, the audio
  stays high pitched and sped up.

  If I unplug the main display, ThinkVision X1, then the playback of
  media on the television becomes normal.

  I have tried with different +100 USD HDMI cables, that are all rated
  as HDMI 2.0 and the behavior stays the same.

  My system is Ubuntu 20.04 LTS. I tried in a LiveUSB 21.10, but the
  behavior was the same.

  I have an AMD Radeon VII GPU (Has 3x Display Port and 1x HDMI).

  As mentioned I cannot test it in Xorg, but that is only because it
  does not allow me to set the refresh rate to 60Hz.

  I am uncertain whether this is related to MESA, Pulseaudio or maybe
  Mutter/Wayland?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.13.0-25.26~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 13 17:24:02 2022
  InstallationDate: Installed on 2020-05-03 (620 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI successful
  Symptom_Card: Vega 20 HDMI Audio [Radeon VII] - HDA ATI HDMI
  Symptom_Jack: Digital Out, HDMI
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [System Product Name, ATI R6xx HDMI, Digital Out, HDMI] Playback 
problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2021
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 8101
  dmi.board.asset.tag: Default string
  dmi.board.name: CROSSHAIR VI HERO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr8101:bd07/15/2021:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnCROSSHAIRVIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1957819/+subscriptions


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

[Touch-packages] [Bug 1957816] Re: Wayland dual monitor switch from 30Hz to 60Hz: High pitch audio double playback speed

2023-10-16 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Wayland dual monitor switch from 30Hz to 60Hz: High pitch audio double
  playback speed

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I have a desktop computer with a 60Hz 4K display connected through Display 
Port. The display is a ThinkVision X1 with built in audio. With the Display 
Port cable I am then able to output sound from the monitor and this works 
without any issues.
  I have now added a 4K Samsung television through HDMI to the same GPU, which 
also allows me to do 4K at 60Hz, albeit only with Wayland. In Xorg I can only 
do 30Hz on the television while doing 60Hz on the ThinkVision X1. It is clear 
however, that when it is set to 60Hz in Wayland, the animation on the 
television is much more smooth. 

  The problem is that whenever I set the television to 60Hz, the playback of 
any sound is both high pitched and faster than normal. If I play a video in 
YouTube, the video appears to playback about twice as fast as normal and and 
very high pitched sound (everyone sounds like chipmunks). This is the case on 
the entire system (also when playing the video or any other sounds on the X1 
display at 60Hz). Only if I set the refresh rate, on the television, to 30Hz 
again does everything play and sound normal again. 
  It is only the playback of media that is doubled in speed. Everything else 
(animations, mouse, etc.) is still behaving as normal.

  If I change audio output to the ThinkVision X1 (or something else) at
  60Hz while also being connected to the television at 60Hz, the audio
  stays high pitched and sped up.

  If I unplug the main display, ThinkVision X1, then the playback of
  media on the television becomes normal.

  I have tried with different +100 USD HDMI cables, that are all rated
  as HDMI 2.0 and the behavior stays the same.

  My system is Ubuntu 20.04 LTS. I tried in a LiveUSB 21.10, but the
  behavior was the same.

  I have an AMD Radeon VII GPU (Has 3x Display Port and 1x HDMI).

  As mentioned I cannot test it in Xorg, but that is only because it
  does not allow me to set the refresh rate to 60Hz.

  I am uncertain whether this is related to MESA, Pulseaudio or maybe
  Mutter/Wayland?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1957816/+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 2007828] Re: /usr/bin/software-properties-gtk:http.client.RemoteDisconnected:poll_for_magic_token:wait:_wait:get_magic_attach_token_info:request_url:readurl:urlopen:open:_open:_c

2023-10-16 Thread Sebastien Bacher
The error reports indeed stopped after that version

** Changed in: software-properties (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  /usr/bin/software-properties-
  
gtk:http.client.RemoteDisconnected:poll_for_magic_token:wait:_wait:get_magic_attach_token_info:request_url:readurl:urlopen:open:_open:_call_chain:https_open:do_open:getresponse:begin:_read_status

Status in software-properties package in Ubuntu:
  Fix Released

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2007828/+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 2038650] Re: crash reports not sent to the Error Tracker

2023-10-16 Thread Brian Murray
Hello Brian, or anyone else affected,

Accepted apport into lunar-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apport/2.26.1-0ubuntu2.1 in a few
hours, and then in the -proposed repository.

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

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

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

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

** Changed in: apport (Ubuntu Lunar)
   Status: Confirmed => Fix Committed

** Tags added: verification-needed verification-needed-lunar

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

Title:
  crash reports not sent to the Error Tracker

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Lunar:
  Fix Committed
Status in apport source package in Mantic:
  Fix Released

Bug description:
  [ Impact ]

  Crash reports aren't sent in when going through the UI, unless the
  user looks at the crash details.

  [ Test Plan ]

  0) Make sure that error reporting is set to manual in the system settings (in 
Privacy screen)
  1) Launch xeyes
  2) pkill -11 xeyes
  3) Click send in the apport dialog. DO NOT look at the details of the report.
  4) ls -lh /var/crash/*xeyes*

  There should be 3 files:

  -rw-r- 1 bdmurray whoopsie  3370567 Oct  6 11:53 _usr_bin_xeyes.1000.crash
  -rw-rw-r-- 1 bdmurray bdmurray0 Oct  6 11:53 
_usr_bin_xeyes.1000.upload
  -rw--- 1 whoopsie whoopsie   37 Oct  6 11:53 
_usr_bin_xeyes.1000.uploaded

  [ Where problems could occur ]

  If the patch is wrong, we actually see similar bugs for other UI
  paths, e.g. ticking the "Remember this" box, etc. I tried to cover
  them during manual testing but I might have missed some.

  [ Other Info ]
   
  If possible I'd like for us not to wait too long for this to mature in 
-proposed, as this would affect crashes during the upgrade.

  [ Original report ]
  From what I can tell when I click the send button to send a crash report to 
the Error Tracker the crash doesn't actually get sent. My testing process 
follows:

  1) Launch xeyes
  2) pkill -11 xeyes
  3) Click send in the apport dialog
  4) ls -lh /var/crash

  I would expect there to be three files in /var/crash:

  -rw-r- 1 bdmurray whoopsie  3370567 Oct  6 11:53 _usr_bin_xeyes.1000.crash
  -rw-rw-r-- 1 bdmurray bdmurray0 Oct  6 11:53 
_usr_bin_xeyes.1000.upload
  -rw--- 1 whoopsie whoopsie   37 Oct  6 11:53 
_usr_bin_xeyes.1000.uploaded

  However, after step #4 I'm only seeing the .crash file and not a
  .upload or .uploaded.  I was able to get the .upload and .uploaded
  files created if I chose to "View Report" and then click "Send".

  It's worth noting though that I did notice the size of the .crash file
  increase after clicking "Send" so some post-processing was done.

  ProblemType: BugDistroRelease: Ubuntu 23.10
  Package: apport 2.27.0-0ubuntu4
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashReports: 640:1000:123:20944237:2023-10-06 12:10:47.809248208 
+0100:2023-10-06 12:11:23.340030509 +0100:/var/crash/_usr_bin_mpv.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  6 12:12:46 2023
  InstallationDate: Installed on 2022-01-07 (637 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  PackageArchitecture: allSourcePackage: 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/2038650/+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 2038650] Re: crash reports not sent to the Error Tracker

2023-10-16 Thread Simon Chopin
We've agreed with Benjamin that the current fix is probably the way to
go for the SRU, while we work on the overall design to make this less
fragile (which would probably be way too much invasive for an SRU).

** Description changed:

- From what I can tell when I click the send button to send a crash report
- to the Error Tracker the crash doesn't actually get sent. My testing
- process follows:
+ [ Impact ]
+ 
+ Crash reports aren't sent in when going through the UI, unless the user
+ looks at the crash details.
+ 
+ [ Test Plan ]
+ 
+ 0) Make sure that error reporting is set to manual in the system settings (in 
Privacy screen)
+ 1) Launch xeyes
+ 2) pkill -11 xeyes
+ 3) Click send in the apport dialog. DO NOT look at the details of the report.
+ 4) ls -lh /var/crash/*xeyes*
+ 
+ There should be 3 files:
+ 
+ -rw-r- 1 bdmurray whoopsie  3370567 Oct  6 11:53 _usr_bin_xeyes.1000.crash
+ -rw-rw-r-- 1 bdmurray bdmurray0 Oct  6 11:53 
_usr_bin_xeyes.1000.upload
+ -rw--- 1 whoopsie whoopsie   37 Oct  6 11:53 
_usr_bin_xeyes.1000.uploaded
+ 
+ [ Where problems could occur ]
+ 
+ If the patch is wrong, we actually see similar bugs for other UI paths,
+ e.g. ticking the "Remember this" box, etc. I tried to cover them during
+ manual testing but I might have missed some.
+ 
+ [ Other Info ]
+  
+ If possible I'd like for us not to wait too long for this to mature in 
-proposed, as this would affect crashes during the upgrade.
+ 
+ [ Original report ]
+ From what I can tell when I click the send button to send a crash report to 
the Error Tracker the crash doesn't actually get sent. My testing process 
follows:
  
  1) Launch xeyes
  2) pkill -11 xeyes
  3) Click send in the apport dialog
  4) ls -lh /var/crash
  
  I would expect there to be three files in /var/crash:
  
  -rw-r- 1 bdmurray whoopsie  3370567 Oct  6 11:53 _usr_bin_xeyes.1000.crash
  -rw-rw-r-- 1 bdmurray bdmurray0 Oct  6 11:53 
_usr_bin_xeyes.1000.upload
  -rw--- 1 whoopsie whoopsie   37 Oct  6 11:53 
_usr_bin_xeyes.1000.uploaded
  
  However, after step #4 I'm only seeing the .crash file and not a .upload
  or .uploaded.  I was able to get the .upload and .uploaded files created
  if I chose to "View Report" and then click "Send".
  
  It's worth noting though that I did notice the size of the .crash file
  increase after clicking "Send" so some post-processing was done.
  
- ProblemType: Bug
- DistroRelease: Ubuntu 23.10
+ ProblemType: BugDistroRelease: Ubuntu 23.10
  Package: apport 2.27.0-0ubuntu4
  ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
  Uname: Linux 6.5.0-5-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu4
  Architecture: amd64
  CasperMD5CheckResult: pass
  CrashReports: 640:1000:123:20944237:2023-10-06 12:10:47.809248208 
+0100:2023-10-06 12:11:23.340030509 +0100:/var/crash/_usr_bin_mpv.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Oct  6 12:12:46 2023
  InstallationDate: Installed on 2022-01-07 (637 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
- PackageArchitecture: all
- SourcePackage: apport
+ PackageArchitecture: allSourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

** Changed in: apport (Ubuntu Lunar)
 Assignee: Benjamin Drung (bdrung) => Simon Chopin (schopin)

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

Title:
  crash reports not sent to the Error Tracker

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Lunar:
  Confirmed
Status in apport source package in Mantic:
  Fix Released

Bug description:
  [ Impact ]

  Crash reports aren't sent in when going through the UI, unless the
  user looks at the crash details.

  [ Test Plan ]

  0) Make sure that error reporting is set to manual in the system settings (in 
Privacy screen)
  1) Launch xeyes
  2) pkill -11 xeyes
  3) Click send in the apport dialog. DO NOT look at the details of the report.
  4) ls -lh /var/crash/*xeyes*

  There should be 3 files:

  -rw-r- 1 bdmurray whoopsie  3370567 Oct  6 11:53 _usr_bin_xeyes.1000.crash
  -rw-rw-r-- 1 bdmurray bdmurray0 Oct  6 11:53 
_usr_bin_xeyes.1000.upload
  -rw--- 1 whoopsie whoopsie   37 Oct  6 11:53 
_usr_bin_xeyes.1000.uploaded

  [ Where problems could occur ]

  If the patch is wrong, we actually see similar bugs for other UI
  paths, e.g. ticking the "Remember this" box, etc. I tried to cover
  them during manual testing but I might have missed some.

  [ Other Info ]
   
  If possible I'd like for us not to wait too long for this to mature in 
-proposed, as this would affect crashes during the upgrade.

  [ Original report ]
  From what I can tell when I click the send button to send a crash report to 
the Error Tracker the crash doesn't actually get sent. My testing 

[Touch-packages] [Bug 1837227] Re: systemd mount units fail during boot, while file system is correctly mounted

2023-10-16 Thread Nick Rosbrook
** Tags added: foundations-todo

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

Title:
  systemd mount units fail during boot, while file system is correctly
  mounted

Status in systemd:
  New
Status in Ubuntu Pro:
  In Progress
Status in Ubuntu Pro 18.04 series:
  In Progress
Status in linux package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Won't Fix
Status in systemd source package in Bionic:
  Won't Fix
Status in linux source package in Focal:
  Fix Released
Status in systemd source package in Focal:
  In Progress
Status in linux source package in Jammy:
  Fix Released
Status in systemd source package in Jammy:
  Fix Released

Bug description:
  [Impact]
  systemd mount units fail during boot, and the system boots into emergency mode

  [Test Plan]
  This issue seems to happen randomly, and doesn't seem related to a specific 
mount unit.

  We've used a test script with good results during investigation to
  reproduce similar mount failures in a running system, and have seen a
  strong correlation between the script failures and the boot time mount
  failures.

  The attached 'rep-tmpfs.sh' script should be used to validate that
  mount points are working correctly under stress. One can run through
  the different variants as below:

  # ./rep-tmpfs.sh --variant-0
  # ./rep-tmpfs.sh --variant-1
  # ./rep-tmpfs.sh --variant-2
  # ./rep-tmpfs.sh --variant-3
  # ./rep-tmpfs.sh --variant-4

  All of these should run successfully without any reported errors.

  [Where problems could occur]
  The patches change the way systemd tracks and handles mount points in 
general, so potential regressions could affect other mount units. We should 
keep an eye out for any issues with mounting file systems, as well as rapid 
mount/unmount operations. Successful test runs with the reproducer script 
should increase reliability in having no new regressions.

  [Other Info]
  This has been tackled upstream with several attempts, which have resulted in 
the final patch from 2022:
    01400460ae16 core/mount: adjust deserialized state based on 
/proc/self/mountinfo

  For Bionic, systemd requires several dependency patches as below:
    6a1d4d9fa6b9 core: properly reset all ExecStatus structures when entering a 
new unit cycle
    7eba1463dedc mount: flush out cycle state on DEAD→MOUNTED only, not the 
other way round
    350804867dbc mount: rescan /proc/self/mountinfo before processing waitid() 
results
    1d086a6e5972 mount: mark an existing "mounting" unit from 
/proc/self/mountinfo as "just_mounted"

  Additionally, the kernel also requires the following patches:
    28ca0d6d39ab list: introduce list_for_each_continue()
    9f6c61f96f2d proc/mounts: add cursor

  [Original Description]
  In Ubuntu 18.04 at least, we sometimes get a random server in emergency mode 
with a failed mount unit (ext4 file system), while the corresponding file 
system is in fact correctly mounted. It happens roughly once every 1000 reboots.

  It seems to be related with this bug :
  https://github.com/systemd/systemd/issues/10872

  Is it possible to apply the fix
  
(https://github.com/systemd/systemd/commit/350804867dbcc9b7ccabae1187d730d37e2d8a21)
  in Ubuntu 18.04 ?

  Thanks in advance.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1837227/+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 2025382] Re: 22.04 DHCPv6 IPv6 broken (at least on Oracle OCI)

2023-10-16 Thread Nick Rosbrook
** Tags removed: systemd-sru-next

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

Title:
  22.04 DHCPv6 IPv6 broken (at least on Oracle OCI)

Status in systemd package in Ubuntu:
  Triaged
Status in systemd source package in Jammy:
  Triaged
Status in systemd source package in Lunar:
  New

Bug description:
  Ubuntu 22.04.2 LTS
  kernel 5.15.0-1038-oracle
  systemd 249.11-0ubuntu3.9

  After an update a couple weeks ago, Ubuntu 22.04 can no longer get
  IPv6 via DHCPv6 systemd-networkd, at least on Oracle OCI, but there
  are also other similar reports, e.g.

  https://ubuntuforums.org/showthread.php?t=2487465=14146758

  Oracle seems to be aware of the issue but they claim it's a Ubuntu
  22.04 bug:

  https://community.oracle.com/customerconnect/discussion/687610/oci-
  ipv6-address-not-assigned-to-oci-ubuntu-instance-by-dhcp

  The workaround to assign a static IPv6 is not great when managing
  multiple cloud instances.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2025382/+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 2039358] Re: Audio via bluetooth gets intermitent when a browser is started

2023-10-16 Thread Juerg Haefliger
*** This bug is a duplicate of bug 2038539 ***
https://bugs.launchpad.net/bugs/2038539

** This bug has been marked a duplicate of bug 2038539
   bluetooth connections are unstable with linux-image-6.5.0-7-generic (MANTIC)

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

Title:
  Audio via bluetooth gets intermitent when a browser is started

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  listening to a fresh boot of mantic install .. sound works properly
  and bluetooh headphones/speaker connection is flawless.. starting a
  browser .. audio becomes choppy via bluetooth .. laptop speaker suffer
  no degradation.. occurs with kernels above 6.5.0-5  see bug 2038539
  also.. (reported from a 6.5.0-5 kernel instance

  This report was added so a report from a 6.5.0-9 kernel instance is
  made

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  derk   1707 F wireplumber
   /dev/snd/controlC1:  derk   1707 F wireplumber
   /dev/snd/seq:derk   1704 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: XFCE
  Date: Sat Oct 14 10:39:35 2023
  InstallationDate: Installed on 2023-10-04 (10 days ago)
  InstallationMedia: Xubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20231004)
  PackageArchitecture: all
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: alsa-driver
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/13/2023
  dmi.bios.release: 1.21
  dmi.bios.vendor: LENOVO
  dmi.bios.version: L9CN21WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0T76463 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: IdeaPad Slim 5 16ABR8
  dmi.ec.firmware.release: 1.21
  dmi.modalias: 
dmi:bvnLENOVO:bvrL9CN21WW:bd06/13/2023:br1.21:efr1.21:svnLENOVO:pn82XG:pvrIdeaPadSlim516ABR8:rvnLENOVO:rnLNVNB161216:rvrSDK0T76463WIN:cvnLENOVO:ct10:cvrIdeaPadSlim516ABR8:skuLENOVO_MT_82XG_BU_idea_FM_IdeaPadSlim516ABR8:
  dmi.product.family: IdeaPad Slim 5 16ABR8
  dmi.product.name: 82XG
  dmi.product.sku: LENOVO_MT_82XG_BU_idea_FM_IdeaPad Slim 5 16ABR8
  dmi.product.version: IdeaPad Slim 5 16ABR8
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2039358/+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 2039083] Re: "optional: true" flag introduces problem it's meant to fix in certain circumstances

2023-10-16 Thread Lukas Märdian
I think this is related to a recent change in behavior in systemd.

It is supposed to be fixed, by implementing the "network-online.target"
specification. Which defines what should be waited for:
https://discourse.ubuntu.com/t/spec-definition-of-an-online-system/27838

But we first need to get some of the groundwork landed in upstream
systemd-networkd.

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

** Changed in: netplan
   Status: New => Triaged

** Changed in: netplan
   Importance: Undecided => High

** Tags added: network-online-ordering

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

Title:
  "optional: true" flag introduces problem it's meant to fix in certain
  circumstances

Status in netplan:
  Triaged
Status in systemd package in Ubuntu:
  New

Bug description:
  Hello!

  This bug is in relation to the situation where the "systemd-networkd-
  wait-online.service" hangs for several minutes on boot before
  eventually failing. I guess I don't know if this flag was introduced
  specifically for this situation, but I do know that one of the fixes
  for this issue is to add "optional: true" to any non-critical
  interfaces (as per the docs[1]). While this may be the case, it just
  so happens that adding this flag to an interface when it's the only
  configured interface in netplan can actually INTRODUCE the issue as
  well. Example:

  ---
  :~# grep -Ev "^#" /etc/netplan/50-cloud-init.yaml
  network:
  version: 2
  ethernets:
  enp5s0:
  dhcp4: true
  optional: true
  ---

  The above config will cause the service hang/failure, and the removal
  of the flag will resolve the issue. I primarily opened this bug report
  with the idea that we might update aforementioned documentation to
  include a caveat that you want to avoid adding this flag to the only
  configured interface. However, it was also discussed that we might
  consider having the netplan config parser complain about such a setup
  and consider it invalid, which it kinda is. I believe in a situation
  where you may have a server that should have NO network connectivity,
  you would simply leave netplan unconfigured and/or stop any relevant
  services, rather than try to configure all interfaces as optional.

  My original test was on Jammy, though I tested this also on Focal and
  Bionic, and neither of those appear to be affected by this - setting
  the only interface as optional in either of those does not cause the
  "systemd-networkd-wait-online" service to hang and the system boots
  normally.

  Let me know if you'd like/need any more info from me! Thank you!

  [1] https://netplan.io/faq#prevent-waiting-for-interface

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/2039083/+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 2039449] [NEW] Screen flickers sometimes and all applications closed on return from lock screen/sleep more

2023-10-16 Thread Alexander Dietrich
Public bug reported:

Recent Upgrade to 23.10. 
New hardware, Lenovo T14 G4 AMD Ryzen 7 PRO 7840U w/ Radeon 780M Graphics

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Oct 16 15:36:51 2023
DistUpgraded: 2023-10-15 14:21:56,603 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
DistroCodename: mantic
DistroVariant: ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Phoenix1 [1002:15bf] (rev dd) (prog-if 
00 [VGA controller])
   Subsystem: Lenovo Phoenix [17aa:50d9]
InstallationDate: Installed on 2023-10-04 (12 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to mantic on 2023-10-15 (1 days ago)
dmi.bios.date: 08/03/2023
dmi.bios.release: 1.11
dmi.bios.vendor: LENOVO
dmi.bios.version: R2FET31W (1.11 )
dmi.board.asset.tag: Not Available
dmi.board.name: 21K4S02000
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.9
dmi.modalias: 
dmi:bvnLENOVO:bvrR2FET31W(1.11):bd08/03/2023:br1.11:efr1.9:svnLENOVO:pn21K4S02000:pvrThinkPadT14Gen4:rvnLENOVO:rn21K4S02000:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21K4_BU_Think_FM_ThinkPadT14Gen4:
dmi.product.family: ThinkPad T14 Gen 4
dmi.product.name: 21K4S02000
dmi.product.sku: LENOVO_MT_21K4_BU_Think_FM_ThinkPad T14 Gen 4
dmi.product.version: ThinkPad T14 Gen 4
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2
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

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


** Tags: amd64 apport-bug mantic ubuntu wayland-session

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

Title:
  Screen flickers sometimes and all applications closed on return from
  lock screen/sleep more

Status in xorg package in Ubuntu:
  New

Bug description:
  Recent Upgrade to 23.10. 
  New hardware, Lenovo T14 G4 AMD Ryzen 7 PRO 7840U w/ Radeon 780M Graphics

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 16 15:36:51 2023
  DistUpgraded: 2023-10-15 14:21:56,603 DEBUG Running PostInstallScript: 
'/usr/lib/ubuntu-advantage/upgrade_lts_contract.py'
  DistroCodename: mantic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Phoenix1 [1002:15bf] (rev dd) 
(prog-if 00 [VGA controller])
 Subsystem: Lenovo Phoenix [17aa:50d9]
  InstallationDate: Installed on 2023-10-04 (12 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-9-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to mantic on 2023-10-15 (1 days ago)
  dmi.bios.date: 08/03/2023
  dmi.bios.release: 1.11
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R2FET31W (1.11 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 21K4S02000
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.9
  dmi.modalias: 
dmi:bvnLENOVO:bvrR2FET31W(1.11):bd08/03/2023:br1.11:efr1.9:svnLENOVO:pn21K4S02000:pvrThinkPadT14Gen4:rvnLENOVO:rn21K4S02000:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21K4_BU_Think_FM_ThinkPadT14Gen4:
  dmi.product.family: ThinkPad T14 Gen 4
  

[Touch-packages] [Bug 2029410] Re: File dialog: using mouse buttons 4/5 to go back/forward?

2023-10-16 Thread Bug Watch Updater
** Changed in: gtk
   Status: Unknown => New

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

Title:
  File dialog: using mouse buttons 4/5 to go back/forward?

Status in GTK+:
  New
Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  Hello.

  I just realised that I have tried subconsciously several times now to
  use the same mechanism that's available in browsers, to move back and
  forward through page history, when I have been using the GTK file
  dialog, in an attempt to move back to the previous directory I was in.

  I am wondering if this there is any potential this mechanism could be
  included in the GTK file dialog at some point in the future? I'm
  guessing many folk are now familiar with this from their browser use
  that it would benefit.

  Thanks for your time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/2029410/+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 2029410] Re: File dialog: using mouse buttons 4/5 to go back/forward?

2023-10-16 Thread Sebastien Bacher
** Changed in: gtk+3.0 (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: gtk+3.0 (Ubuntu)
   Status: New => Triaged

** Bug watch added: gitlab.gnome.org/GNOME/gtk/-/issues #4637
   https://gitlab.gnome.org/GNOME/gtk/-/issues/4637

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

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

Title:
  File dialog: using mouse buttons 4/5 to go back/forward?

Status in GTK+:
  Unknown
Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  Hello.

  I just realised that I have tried subconsciously several times now to
  use the same mechanism that's available in browsers, to move back and
  forward through page history, when I have been using the GTK file
  dialog, in an attempt to move back to the previous directory I was in.

  I am wondering if this there is any potential this mechanism could be
  included in the GTK file dialog at some point in the future? I'm
  guessing many folk are now familiar with this from their browser use
  that it would benefit.

  Thanks for your time.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/2029410/+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 2039429] Re: Please merge wget 1.21.4 (main) from Debian unstable

2023-10-16 Thread Ubuntu Foundations Team Bug Bot
The attachment "wget.diff" 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 wget in Ubuntu.
https://bugs.launchpad.net/bugs/2039429

Title:
   Please merge wget 1.21.4 (main) from Debian unstable

Status in wget package in Ubuntu:
  Confirmed

Bug description:
  Please merge wget 1.21.4 (main) from Debian unstable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wget/+bug/2039429/+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 2038512] Re: [Mediatek] mt8195-demo: please help to include these MediaTek drivers in initrd.img in CD/DVD release image

2023-10-16 Thread Ubuntu Foundations Team Bug Bot
** Tags added: patch

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

Title:
  [Mediatek] mt8195-demo: please help to include these MediaTek drivers
  in initrd.img in CD/DVD release image

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  [Impact]
  Peripheral probe failure for MediaTek boards 'mt8195-demo' and 
'genio-1200-evk'.

  [Ubuntu Version]
  Jammy

  [initramfs-tools]
  0.140ubuntu13.4

  [Kernel version]
  5.15 -> 6.2
  (Generate initrd.img-6.2.0 on 5.15 kernel.)

  [Fix]
  I've used 'dracut' to examing the driver dependencies for boards 
'mt8195-demo' and 'genio-1200-evk'.
  It is able to buot into console and use USB port3.
  Hope these drivers could help to run installer with USB disk in next daily 
build.

  Note: It won't work with 'update-initramfs -u -k 6.2.0-34-generic' if
  just simply add driver lists in '/etc/modules',
  '/etc/modprobe.d/mediatek.conf' or '/etc/modules-
  load.d/mediatek.conf'. I fixed this issue with 'dracut' and it seems
  this tool will include more common framework drivers into initrd.img.

  [MediaTek relate drivers]
  file: mediatek-drivers-for-mt8195-demo-bringup.txt
  (Not listed in probing sequence)

  i2c-mt65xx
  spi-mt65xx
  reset-ti-syscon
  mt6397
  rtc-mt6397
  mtk-pmic-wrap
  mt6315-regulator
  spmi-mtk-pmif
  mtk_scp_ipi
  mediatek-drm
  mtk-vcodec-dec
  mtk-vcodec-enc
  mtk_jpeg
  mtk-vcodec-common
  mtk-jpeg-enc-hw
  mtk-vpu
  mtk-jpeg-dec-hw
  mtk-cmdq-helper
  mtk-cmdq-helper
  mtk-cmdq-mailbox
  mtk-mdp3
  phy-mtk-mipi-dsi-drv
  btmtk
  leds-mt6360
  tcpci_mt6360
  mt6360_charger
  mt6360-regulator
  mt6360-core
  mt6359-regulator
  mt6360-adc
  snd-soc-mt8195-afe
  snd-soc-mtk-common
  snd-soc-dmic
  dwmac-mediatek
  stmmac-platform
  stmmac
  mtk-rng
  mtk_scp
  mtk_rpmsg
  pwm-mediatek
  pwm-mtk-disp
  nvmem_mtk-efuse
  mtk-sd
  cqhci
  phy-mtk-tphy
  mtu3
  xhci-mtk-hcd
  phy-mtk-pcie
  pcie-mediatek-gen3

  [lsmod log]
  file: lsmod-i1200-demo-kernel-6.2-dracut-initrd.txt

  [Other info]
  effected kernel (6.2-latest)
  ubuntu kernel for lunar, and Mantic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2038512/+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 2039278] Re: Consistent naming of onboard NIC on all Pi on all Ubuntu

2023-10-16 Thread Juerg Haefliger
** Tags added: kern-8255

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

Title:
  Consistent naming of onboard NIC on all Pi on all Ubuntu

Status in linux-raspi package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New
Status in systemd-hwe package in Ubuntu:
  New
Status in ubuntu-raspi-settings package in Ubuntu:
  New

Bug description:
  Consistent naming of onboard NIC on all Pi on all Ubuntu

  
  We should have the one distro config, to force consistent oboard NIC naming 
on all Pi on all Ubuntu in the one place.

  Let's find all the puzzle pieces and do it onces, and for all

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2039278/+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 2038512] Re: [Mediatek] mt8195-demo: please help to include these MediaTek drivers in initrd.img in CD/DVD release image

2023-10-16 Thread Benjamin Drung
The initramfs-tools code can be found on
https://code.launchpad.net/~ubuntu-core-dev/ubuntu/+source/initramfs-
tools/+git/initramfs-tools

Can you test the proposed changes from
https://code.launchpad.net/~bdrung/ubuntu/+source/initramfs-
tools/+git/initramfs-tools/+ref/mediatek (patch with the changes from
the three commits is attached)? Apply the changes to
/usr/share/initramfs-tools/hook-functions and test if the boards boot
correctly then.

** Patch added: "proposed-changes.diff"
   
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2038512/+attachment/5709818/+files/proposed-changes.diff

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

Title:
  [Mediatek] mt8195-demo: please help to include these MediaTek drivers
  in initrd.img in CD/DVD release image

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  [Impact]
  Peripheral probe failure for MediaTek boards 'mt8195-demo' and 
'genio-1200-evk'.

  [Ubuntu Version]
  Jammy

  [initramfs-tools]
  0.140ubuntu13.4

  [Kernel version]
  5.15 -> 6.2
  (Generate initrd.img-6.2.0 on 5.15 kernel.)

  [Fix]
  I've used 'dracut' to examing the driver dependencies for boards 
'mt8195-demo' and 'genio-1200-evk'.
  It is able to buot into console and use USB port3.
  Hope these drivers could help to run installer with USB disk in next daily 
build.

  Note: It won't work with 'update-initramfs -u -k 6.2.0-34-generic' if
  just simply add driver lists in '/etc/modules',
  '/etc/modprobe.d/mediatek.conf' or '/etc/modules-
  load.d/mediatek.conf'. I fixed this issue with 'dracut' and it seems
  this tool will include more common framework drivers into initrd.img.

  [MediaTek relate drivers]
  file: mediatek-drivers-for-mt8195-demo-bringup.txt
  (Not listed in probing sequence)

  i2c-mt65xx
  spi-mt65xx
  reset-ti-syscon
  mt6397
  rtc-mt6397
  mtk-pmic-wrap
  mt6315-regulator
  spmi-mtk-pmif
  mtk_scp_ipi
  mediatek-drm
  mtk-vcodec-dec
  mtk-vcodec-enc
  mtk_jpeg
  mtk-vcodec-common
  mtk-jpeg-enc-hw
  mtk-vpu
  mtk-jpeg-dec-hw
  mtk-cmdq-helper
  mtk-cmdq-helper
  mtk-cmdq-mailbox
  mtk-mdp3
  phy-mtk-mipi-dsi-drv
  btmtk
  leds-mt6360
  tcpci_mt6360
  mt6360_charger
  mt6360-regulator
  mt6360-core
  mt6359-regulator
  mt6360-adc
  snd-soc-mt8195-afe
  snd-soc-mtk-common
  snd-soc-dmic
  dwmac-mediatek
  stmmac-platform
  stmmac
  mtk-rng
  mtk_scp
  mtk_rpmsg
  pwm-mediatek
  pwm-mtk-disp
  nvmem_mtk-efuse
  mtk-sd
  cqhci
  phy-mtk-tphy
  mtu3
  xhci-mtk-hcd
  phy-mtk-pcie
  pcie-mediatek-gen3

  [lsmod log]
  file: lsmod-i1200-demo-kernel-6.2-dracut-initrd.txt

  [Other info]
  effected kernel (6.2-latest)
  ubuntu kernel for lunar, and Mantic.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2038512/+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 2039242] Re: package apparmor 2.12-4ubuntu5.3 failed to install/upgrade: new apparmor package pre-installation script subprocess returned error exit status 1

2023-10-16 Thread Georgia Garcia
*** This bug is a duplicate of bug 2032851 ***
https://bugs.launchpad.net/bugs/2032851

** This bug has been marked a duplicate of bug 2032851
   package apparmor 2.12-4ubuntu5.3 failed to install/upgrade: new apparmor 
package pre-installation script subprocess returned error exit status 1

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

Title:
  package apparmor 2.12-4ubuntu5.3 failed to install/upgrade: new
  apparmor package pre-installation script subprocess returned error
  exit status 1

Status in apparmor package in Ubuntu:
  New

Bug description:
  I do not know. I am rookie.

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: apparmor 2.13.3-7ubuntu5.2
  ProcVersionSignature: Ubuntu 5.4.0-150.167~18.04.1-generic 5.4.233
  Uname: Linux 5.4.0-150-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Oct 13 08:25:02 2023
  DuplicateSignature:
   package:apparmor:2.12-4ubuntu5.3
   Preparing to unpack .../09-apparmor_2.13.3-7ubuntu5.2_amd64.deb ...
   rm: cannot remove '/etc/apparmor.d/cache/e10c1cf9.0': Is a directory
   dpkg: error processing archive 
/tmp/apt-dpkg-install-indEZB/09-apparmor_2.13.3-7ubuntu5.2_amd64.deb (--unpack):
new apparmor package pre-installation script subprocess returned error exit 
status 1
  ErrorMessage: new apparmor package pre-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2021-10-31 (711 days ago)
  InstallationMedia: Ubuntu 18.04.6 LTS "Bionic Beaver" - Release amd64 
(20210915)
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-150-generic 
root=UUID=e0b6f6e2-1185-4897-92c0-3bbde798fa08 ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.9
  SourcePackage: apparmor
  Title: package apparmor 2.12-4ubuntu5.3 failed to install/upgrade: new 
apparmor package pre-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to focal on 2023-10-13 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2039242/+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 2039342] Re: package linux-image-6.5.0-1005-raspi 6.5.0-1005.7 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2023-10-16 Thread Benjamin Drung
Thanks for debugging. So closing this bug as invalid, because dhcpcd-
base was not installed properly.

** Changed in: initramfs-tools (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  package linux-image-6.5.0-1005-raspi 6.5.0-1005.7 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  This happened during the upgrade.

  ProblemType: Package
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-1005-raspi 6.5.0-1005.7
  ProcVersionSignature: Ubuntu 6.2.0-1014.16-raspi 6.2.16
  Uname: Linux 6.2.0-1014-raspi aarch64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CloudArchitecture: aarch64
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial:
   
  CloudSubPlatform: config-disk (/dev/sdb1)
  Date: Sat Oct 14 09:07:02 2023
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  ImageMediaBuild: 20210201.1
  Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.22.0ubuntu1
   apt  2.7.3
  SourcePackage: initramfs-tools
  Title: package linux-image-6.5.0-1005-raspi 6.5.0-1005.7 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to mantic on 2023-10-14 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2039342/+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 2039342] Re: package linux-image-6.5.0-1005-raspi 6.5.0-1005.7 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2023-10-16 Thread KcrPL
kcrpl@raspberrypi-4-kcrpl:~$ ls /usr/lib/dhcpcd/dhcpcd-run-hooks
ls: cannot access '/usr/lib/dhcpcd/dhcpcd-run-hooks': No such file or 
directory

kcrpl@raspberrypi-4-kcrpl:~$ sudo apt install --reinstall dhcpcd-base
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not 
upgraded.
Need to get 208 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://ports.ubuntu.com/ubuntu-ports mantic/main arm64 
dhcpcd-base arm64 1:10.0.2-3ubuntu3 [208 kB]
Fetched 208 kB in 0s (580 kB/s)
(Reading database ... 214263 files and directories currently installed.)
Preparing to unpack .../dhcpcd-base_1%3a10.0.2-3ubuntu3_arm64.deb ...
Unpacking dhcpcd-base (1:10.0.2-3ubuntu3) over (1:10.0.2-3ubuntu3) ...
Setting up dhcpcd-base (1:10.0.2-3ubuntu3) ...
Processing triggers for man-db (2.11.2-3) ...
Scanning processes...
Scanning processor microcode...
Scanning linux images...

Running kernel seems to be up-to-date.

Failed to check for processor microcode upgrades.

No services need to be restarted.

No containers need to be restarted.

No user sessions are running outdated binaries.

No VM guests are running outdated hypervisor (qemu) binaries on
this host.

kcrpl@raspberrypi-4-kcrpl:~$ ls /usr/lib/dhcpcd/dhcpcd-run-hooks
/usr/lib/dhcpcd/dhcpcd-run-hooks

kcrpl@raspberrypi-4-kcrpl:~$ sudo update-initramfs -u
(skipping log)

...it worked! This happened during the upgrade because before that
everything worked correctly.

Thank you very much and have a great day!

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

Title:
  package linux-image-6.5.0-1005-raspi 6.5.0-1005.7 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  Incomplete

Bug description:
  This happened during the upgrade.

  ProblemType: Package
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-1005-raspi 6.5.0-1005.7
  ProcVersionSignature: Ubuntu 6.2.0-1014.16-raspi 6.2.16
  Uname: Linux 6.2.0-1014-raspi aarch64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CloudArchitecture: aarch64
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial:
   
  CloudSubPlatform: config-disk (/dev/sdb1)
  Date: Sat Oct 14 09:07:02 2023
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  ImageMediaBuild: 20210201.1
  Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.22.0ubuntu1
   apt  2.7.3
  SourcePackage: initramfs-tools
  Title: package linux-image-6.5.0-1005-raspi 6.5.0-1005.7 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to mantic on 2023-10-14 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2039342/+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 2007621] Re: gio open exits with success even though the underlying exec failed

2023-10-16 Thread Sebastien Bacher
Thank you for your bug report. Indeed that seems incorrect and should be
reported to https://gitlab.gnome.org/GNOME/glib/-/issues

** Changed in: glib2.0 (Ubuntu)
   Importance: Undecided => Low

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

Title:
  gio open exits with success even though the underlying exec failed

Status in glib2.0 package in Ubuntu:
  Confirmed

Bug description:
  This is a sort of annoyingly complex interaction, so bear with me. The
  observed problem is that xdg-open does not exit with a non-zero exit
  code when it fails to open.

  ```
  $ unset DISPLAY 
  $ xdg-open http://example.com
  exo-open: Cannot open display: .
  $ echo $?
  0
  ```

  It turns out to not exactly be xdg-open's fault, though:
  ```
  $ sh -x $(which xdg-open) http://example.com 2>&1 | tail -n10
  + return 0
  + open_xfce http://example.com
  + exo-open --help
  + gio help open
  + gio open http://example.com
  exo-open: Cannot open display: .
  + [ 0 -eq 0 ]
  + exit_success
  + [ 0 -gt 0 ]
  + exit 0
  ```

  So, from this we see that xdg-open uses `exo-open --help` to see if
  exo-open works, but it fails due to the DISPLAY, so it falls back to
  gio open. gio open ends up turning around and calling exo-open again,
  but gio swallows the exit code, so xdg-open thinks it worked.

  ```
  $ exo-open http://example.com
  exo-open: Cannot open display: .
  $ echo $?
  1
  $ gio open http://example.com
  exo-open: Cannot open display: .
  $ echo $?
  0
  ```

  Versions:
  $ lsb_release -rd  
  Description:Ubuntu 22.04.1 LTS
  Release:22.04
  $ xdg-open --version   
  xdg-open 1.1.3
  $ exo-open --version | head -n1
  exo-open 4.16.3
  $ gio --version   
  2.72.4

  Specifically:
  exo-utils:
Installed: 4.16.3-1
Candidate: 4.16.3-1
Version table:
   *** 4.16.3-1 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/universe amd64 Packages
  100 /var/lib/dpkg/status
  libglib2.0-bin:
Installed: 2.72.4-0ubuntu1
Candidate: 2.72.4-0ubuntu1
Version table:
   *** 2.72.4-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.72.1-1 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  xdg-utils:
Installed: 1.1.3-4.1ubuntu3~22.04.1
Candidate: 1.1.3-4.1ubuntu3~22.04.1
Version table:
   *** 1.1.3-4.1ubuntu3~22.04.1 500
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
  500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   1.1.3-4.1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
  500 http://us.archive.ubuntu.com/ubuntu jammy/main i386 Packages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2007621/+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 2039342] Re: package linux-image-6.5.0-1005-raspi 6.5.0-1005.7 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2023-10-16 Thread Benjamin Drung
initramfs-tools only uses the dhcpcd binary from dhcpcd-base (not the
dhcpcd service).

The relevant log lines from the output are:

+ copy_exec /usr/lib/dhcpcd/dhcpcd-run-hooks
+ local src target x nonoptlib ret
+ src=/usr/lib/dhcpcd/dhcpcd-run-hooks
+ target=/usr/lib/dhcpcd/dhcpcd-run-hooks
+ copy_file binary /usr/lib/dhcpcd/dhcpcd-run-hooks 
/usr/lib/dhcpcd/dhcpcd-run-hooks
+ local type src target link_target
+ type=binary
+ src=/usr/lib/dhcpcd/dhcpcd-run-hooks
+ target=/usr/lib/dhcpcd/dhcpcd-run-hooks
+ [ -f /usr/lib/dhcpcd/dhcpcd-run-hooks ]
+ return 2
+ return 1
E: /usr/share/initramfs-tools/hooks/dhcpcd failed with return 1.
update-initramfs: failed for /boot/initrd.img-6.5.0-1005-raspi with 1.

The test if /usr/lib/dhcpcd/dhcpcd-run-hooks exist fails. Is dhcpcd-base
fully installed and /usr/lib/dhcpcd/dhcpcd-run-hooks present?

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

Title:
  package linux-image-6.5.0-1005-raspi 6.5.0-1005.7 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  Incomplete

Bug description:
  This happened during the upgrade.

  ProblemType: Package
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-1005-raspi 6.5.0-1005.7
  ProcVersionSignature: Ubuntu 6.2.0-1014.16-raspi 6.2.16
  Uname: Linux 6.2.0-1014-raspi aarch64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CloudArchitecture: aarch64
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial:
   
  CloudSubPlatform: config-disk (/dev/sdb1)
  Date: Sat Oct 14 09:07:02 2023
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  ImageMediaBuild: 20210201.1
  Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.22.0ubuntu1
   apt  2.7.3
  SourcePackage: initramfs-tools
  Title: package linux-image-6.5.0-1005-raspi 6.5.0-1005.7 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to mantic on 2023-10-14 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2039342/+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 2038610] Re: package linux-image-6.2.0-34-generic 6.2.0-34.34~22.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2023-10-16 Thread Benjamin Drung
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The relevant dpkg terminal log says:

sync: error syncing '/boot/initrd.img-6.2.0-34-generic': Input/output
error

This indicates a problem with your hardware. I recommend performing a
back up and then investigating the situation.  Measures you might take
include checking cable connections and using software tools to
investigate the health of your hardware.  In the event that is is not in
fact an error with your hardware please set the bug's status back to
New.  Thanks and good luck!

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Invalid

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

Title:
  package linux-image-6.2.0-34-generic 6.2.0-34.34~22.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:
  Invalid

Bug description:
  System crashed when installing update

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.2.0-34-generic 6.2.0-34.34~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Fri Oct  6 06:44:43 2023
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2023-09-22 (13 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.10
  SourcePackage: initramfs-tools
  Title: package linux-image-6.2.0-34-generic 6.2.0-34.34~22.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/2038610/+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 2039340] Re: On upgrade from 23.04 to 23.10, cannot login using Gnome or Ubuntu WM entries

2023-10-16 Thread Sebastien Bacher
The journal shows a gnome-shell error

Bail out! Gjs:ERROR:../gi/wrapperutils.h:847:static Prototype*
GIWrapperPrototype::create_prototype(Info*, GType) [with Base = InterfaceBase;
Prototype = InterfacePrototype; Instance = InterfaceInstance; Info =
_GIBaseInfoStub; GType = long unsigned int]: assertion failed: (gtype !=
G_TYPE_INVALID)


Do you have local extensions installed? Could you try if a new user has the 
same issue?

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

** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => High

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

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

Title:
  On upgrade from 23.04 to 23.10, cannot login using Gnome or Ubuntu WM
  entries

Status in Ubuntu:
  New
Status in apparmor package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Last time I hacked around a bug like this, it had portions in PAM,
  apparmor, Seahorse, and Gnome so this time I'd like someone more
  focused on broad stability to look at things.

  The problem is simple.  Before the upgrade to 23.10, I could log in
  using the "Ubuntu", "Ubuntu on X.org". "Gnome", and "Gnome on X.org"
  WMs.  Now I can't.  I can still login using XFCE and TTY.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2039340/+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 2039429] [NEW] Please merge wget 1.21.4 (main) from Debian unstable

2023-10-16 Thread Nathan Teodosio
Public bug reported:

Please merge wget 1.21.4 (main) from Debian unstable.

** Affects: wget (Ubuntu)
 Importance: Wishlist
 Status: Confirmed

** Patch added: "wget.diff"
   https://bugs.launchpad.net/bugs/2039429/+attachment/5709802/+files/wget.diff

** Patch removed: "wget.diff"
   
https://bugs.launchpad.net/ubuntu/+source/wget/+bug/2039429/+attachment/5709802/+files/wget.diff

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

Title:
   Please merge wget 1.21.4 (main) from Debian unstable

Status in wget package in Ubuntu:
  Confirmed

Bug description:
  Please merge wget 1.21.4 (main) from Debian unstable.

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

2023-10-16 Thread Nathan Teodosio
** Patch added: "wget.diff"
   
https://bugs.launchpad.net/ubuntu/+source/wget/+bug/2039429/+attachment/5709803/+files/wget.diff

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

Title:
   Please merge wget 1.21.4 (main) from Debian unstable

Status in wget package in Ubuntu:
  Confirmed

Bug description:
  Please merge wget 1.21.4 (main) from Debian unstable.

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

2023-10-16 Thread Benjamin Drung
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The relevant dpkg terminal log says:

update-initramfs: deferring update (trigger activated)
dpkg-maintscript-helper: error: dpkg: error: unknown option --validate-version
[...]
dpkg: error processing package initramfs-tools (--configure):
 subprocess installed post-installation script returned error exit status 1

This should not happen. Which dpkg version do you have installed?

dpkg -l | grep dpkg

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Incomplete

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

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

Status in initramfs-tools package in Ubuntu:
  Incomplete

Bug description:
  i got this bug, when iam trying install apps through terminal

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: initramfs-tools 0.140ubuntu13.4
  ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-33-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82.5
  AptOrdering:
   fuse:amd64: Remove
   fuse3:amd64: Install
   gnome-remote-desktop:amd64: Install
   gnome-control-center:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5json:
   {
 "result": "skip"
   }
  Date: Sun Oct  1 14:42:33 2023
  DpkgHistoryLog:
   Start-Date: 2023-10-01  14:42:29
   Commandline: apt install gnome-control-center
   Requested-By: avinash (1000)
   Install: gnome-remote-desktop:amd64 (42.9-0ubuntu0.22.04.1, automatic), 
fuse3:amd64 (3.10.5-1build1, automatic), gnome-control-center:amd64 
(1:41.7-0ubuntu0.22.04.7)
   Remove: fuse:amd64 (2.9.9-5ubuntu3)
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2023-09-17 (13 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.140ubuntu13.4 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2037879/+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 2039391] Re: pakage broken

2023-10-16 Thread Sebastien Bacher
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:

1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected.
3. The behavior you actually encountered (in as much detail as possible).

Please also ensure that you include the release and flavour of Ubuntu
that you are using.

Thank you!

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

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

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

Title:
  pakage broken

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  instaler pakage broken

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-164.181-generic 5.4.248
  Uname: Linux 5.4.0-164-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sun Oct 15 22:20:43 2023
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   intel-hid, 3.1, 4.4.0-210-generic, x86_64: installed
   oem-audio-hda-daily, 0.201708030416~ubuntu16.04.1, 4.4.0-210-generic, 
x86_64: installed
   oem-wifi-qualcomm-ath10k-lp1734600-4.4, 4.1, 4.4.0-210-generic, x86_64: 
installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:0793]
  InstallationDate: Installed on 2023-07-12 (95 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0cf3:e009 Qualcomm Atheros Communications 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 0bda:5769 Realtek Semiconductor Corp. 
Integrated_Webcam_HD
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Vostro 15-3568
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-164-generic 
root=UUID=ecd93531-cc0b-4642-b530-68a5e7081e61 ro acpi_rev_override 
locale=en_IN alx.enable_wol=1 mem_sleep_default=deep quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/19/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.5.0
  dmi.board.name: 05HRPP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.5.0:bd04/19/2018:svnDellInc.:pnVostro15-3568:pvr:rvnDellInc.:rn05HRPP:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 15-3568
  dmi.product.sku: 0793
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.14.1+20.04.20220820-0ubuntu1
  version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.2.6-0ubuntu0.1~20.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
  xserver.bootTime: Sun Oct 15 21:52:15 2023
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.20.13-1ubuntu1~20.04.8

To manage notifications about this bug go to:

[Touch-packages] [Bug 2039342] Re: package linux-image-6.5.0-1005-raspi 6.5.0-1005.7 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2023-10-16 Thread KcrPL
I have added "set -x" just under "set -e" in the script. Here are the
following results:

kcrpl@raspberrypi-4-kcrpl:/usr/share/initramfs-tools/hooks$ sudo 
update-initramfs -u
+ sudo update-initramfs -u
update-initramfs: Generating /boot/initrd.img-6.5.0-1005-raspi
+ PREREQ=
+ prereqs
+ echo
+ exit 0
+ PREREQ=
+ . /usr/share/initramfs-tools/hook-functions
+ [ -x /usr/sbin/dhcpcd ]
+ copy_exec /usr/sbin/dhcpcd
+ local src target x nonoptlib ret
+ src=/usr/sbin/dhcpcd
+ target=/usr/sbin/dhcpcd
+ copy_file binary /usr/sbin/dhcpcd /usr/sbin/dhcpcd
+ local type src target link_target
+ type=binary
+ src=/usr/sbin/dhcpcd
+ target=/usr/sbin/dhcpcd
+ [ -f /usr/sbin/dhcpcd ]
+ [ -d /var/tmp/mkinitramfs_FoHhvu//usr/sbin/dhcpcd ]
+ [ -e /var/tmp/mkinitramfs_FoHhvu//usr/sbin/dhcpcd ]
+ mkdir -p /var/tmp/mkinitramfs_FoHhvu//usr/sbin
+ [ -h /usr/sbin/dhcpcd ]
+ [ n = y ]
+ cp -pP /usr/sbin/dhcpcd /var/tmp/mkinitramfs_FoHhvu//usr/sbin/dhcpcd
+ env --unset=LD_PRELOAD ldd /usr/sbin/dhcpcd
+ sed -e
/\//!d;
/linux-gate/d;
/=>/ {s/.*=>[[:blank:]]*\([^[:blank:]]*\).*/\1/};
s/[[:blank:]]*\([^[:blank:]]*\) (.*)/\1/
+ echo /lib/aarch64-linux-gnu/libcrypto.so.3
+ sed -e 
s#/lib/\([^/]*/\)\?\(tls\|i686\|sse2\|neon\|vfp\).*/\(lib.*\)#/lib/\1\3#
+ nonoptlib=/lib/aarch64-linux-gnu/libcrypto.so.3
+ echo /lib/aarch64-linux-gnu/libcrypto.so.3
+ sed -e s#-linux-gnu/\(tls\|i686\|sse2\|neon\|vfp\).*/\(lib.*\)#-linux-gnu/\2#
+ nonoptlib=/lib/aarch64-linux-gnu/libcrypto.so.3
+ [ -e /lib/aarch64-linux-gnu/libcrypto.so.3 ]
+ x=/lib/aarch64-linux-gnu/libcrypto.so.3
+ copy_file binary /lib/aarch64-linux-gnu/libcrypto.so.3
+ local type src target link_target
+ type=binary
+ src=/lib/aarch64-linux-gnu/libcrypto.so.3
+ target=/lib/aarch64-linux-gnu/libcrypto.so.3
+ [ -f /lib/aarch64-linux-gnu/libcrypto.so.3 ]
+ [ -d /var/tmp/mkinitramfs_FoHhvu//lib/aarch64-linux-gnu/libcrypto.so.3 ]
+ target=/usr/lib/aarch64-linux-gnu/libcrypto.so.3
+ [ -e /var/tmp/mkinitramfs_FoHhvu//usr/lib/aarch64-linux-gnu/libcrypto.so.3 ]
+ return 1
+ ret=1
+ [ 1 = 1 ]
+ echo /lib/aarch64-linux-gnu/libc.so.6
+ sed -e 
s#/lib/\([^/]*/\)\?\(tls\|i686\|sse2\|neon\|vfp\).*/\(lib.*\)#/lib/\1\3#
+ nonoptlib=/lib/aarch64-linux-gnu/libc.so.6
+ echo /lib/aarch64-linux-gnu/libc.so.6
+ sed -e s#-linux-gnu/\(tls\|i686\|sse2\|neon\|vfp\).*/\(lib.*\)#-linux-gnu/\2#
+ nonoptlib=/lib/aarch64-linux-gnu/libc.so.6
+ [ -e /lib/aarch64-linux-gnu/libc.so.6 ]
+ x=/lib/aarch64-linux-gnu/libc.so.6
+ copy_file binary /lib/aarch64-linux-gnu/libc.so.6
+ local type src target link_target
+ type=binary
+ src=/lib/aarch64-linux-gnu/libc.so.6
+ target=/lib/aarch64-linux-gnu/libc.so.6
+ [ -f /lib/aarch64-linux-gnu/libc.so.6 ]
+ [ -d /var/tmp/mkinitramfs_FoHhvu//lib/aarch64-linux-gnu/libc.so.6 ]
+ target=/usr/lib/aarch64-linux-gnu/libc.so.6
+ [ -e /var/tmp/mkinitramfs_FoHhvu//usr/lib/aarch64-linux-gnu/libc.so.6 ]
+ return 1
+ ret=1
+ [ 1 = 1 ]
+ echo /lib/ld-linux-aarch64.so.1
+ sed -e 
s#/lib/\([^/]*/\)\?\(tls\|i686\|sse2\|neon\|vfp\).*/\(lib.*\)#/lib/\1\3#
+ nonoptlib=/lib/ld-linux-aarch64.so.1
+ echo /lib/ld-linux-aarch64.so.1
+ sed -e s#-linux-gnu/\(tls\|i686\|sse2\|neon\|vfp\).*/\(lib.*\)#-linux-gnu/\2#
+ nonoptlib=/lib/ld-linux-aarch64.so.1
+ [ -e /lib/ld-linux-aarch64.so.1 ]
+ x=/lib/ld-linux-aarch64.so.1
+ copy_file binary /lib/ld-linux-aarch64.so.1
+ local type src target link_target
+ type=binary
+ src=/lib/ld-linux-aarch64.so.1
+ target=/lib/ld-linux-aarch64.so.1
+ [ -f /lib/ld-linux-aarch64.so.1 ]
+ [ -d /var/tmp/mkinitramfs_FoHhvu//lib/ld-linux-aarch64.so.1 ]
+ target=/usr/lib/ld-linux-aarch64.so.1
+ [ -e /var/tmp/mkinitramfs_FoHhvu//usr/lib/ld-linux-aarch64.so.1 ]
+ return 1
+ ret=1
+ [ 1 = 1 ]
+ copy_exec /usr/lib/dhcpcd/dhcpcd-run-hooks
+ local src target x nonoptlib ret
+ src=/usr/lib/dhcpcd/dhcpcd-run-hooks
+ target=/usr/lib/dhcpcd/dhcpcd-run-hooks
+ copy_file binary /usr/lib/dhcpcd/dhcpcd-run-hooks 
/usr/lib/dhcpcd/dhcpcd-run-hooks
+ local type src target link_target
+ type=binary
+ src=/usr/lib/dhcpcd/dhcpcd-run-hooks
+ target=/usr/lib/dhcpcd/dhcpcd-run-hooks
+ [ -f /usr/lib/dhcpcd/dhcpcd-run-hooks ]
+ return 2
+ return 1
E: /usr/share/initramfs-tools/hooks/dhcpcd failed with return 1.
update-initramfs: failed for /boot/initrd.img-6.5.0-1005-raspi with 1.
kcrpl@raspberrypi-4-kcrpl:/usr/share/initramfs-tools/hooks$


Just some additional info. For some reason after upgrading to 22.10 dhcpcd 
cannot start however DHCP still seems to work. Attaching output from systemctl 
status below:

kcrpl@raspberrypi-4-kcrpl:~$ sudo systemctl status dhcpcd
[sudo] password for kcrpl:
× dhcpcd.service - DHCP Client Daemon on all interfaces
 Loaded: loaded (/lib/systemd/system/dhcpcd.service; enabled; preset: 
enabled)
 Active: failed (Result: exit-code) since Sat 2023-10-14 18:30:37 CEST; 1 
day 17h ago
   Docs: man:dhcpcd(8)
CPU: 166ms

Oct 14 18:30:36 raspberrypi-4-kcrpl systemd[1]: Starting dhcpcd.service - DHCP 
Client 

[Touch-packages] [Bug 2038918] Re: package initramfs-tools 0.142ubuntu2.2 failed to install/upgrade: subproces van pakket initramfs-tools werd script post-installation geïnstalleerd gaf de foutwaarde

2023-10-16 Thread Benjamin Drung
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The relevant dpkg terminal log says:

update-initramfs: Generating /boot/initrd.img-4.9.337-138
grep: /boot/config-4.9.337-138: Bestand of map bestaat niet
W: zstd compression (CONFIG_RD_ZSTD) not supported by kernel, using gzip
grep: /boot/config-4.9.337-138: Bestand of map bestaat niet
E: gzip compression (CONFIG_RD_GZIP) not supported by kernel
update-initramfs: failed for /boot/initrd.img-4.9.337-138 with 1.

Translated:

update-initramfs: Generating /boot/initrd.img-4.9.337-138
grep: /boot/config-4.9.337-138: File or directory does not exist
W: zstd compression (CONFIG_RD_ZSTD) not supported by kernel, using gzip
grep: /boot/config-4.9.337-138: File or directory does not exist
E: gzip compression (CONFIG_RD_GZIP) not supported by kernel
update-initramfs: failed for /boot/initrd.img-4.9.337-138 with 1.

It looks like you did not have kernel 4.9.337-138 installed. You can
check the installed kernel versions with:

dpkg -l | grep linux-image

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Incomplete

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

Title:
  package initramfs-tools 0.142ubuntu2.2 failed to install/upgrade:
  subproces van pakket initramfs-tools werd script post-installation
  geïnstalleerd gaf de foutwaarde 1 terug

Status in initramfs-tools package in Ubuntu:
  Incomplete

Bug description:
  I get this while with an Odroid.

  ProblemType: Package
  DistroRelease: Ubuntu 23.04
  Package: initramfs-tools 0.142ubuntu2.2
  Uname: Linux 4.9.337-138 aarch64
  NonfreeKernelModules: spidev spi_meson_spicc
  ApportVersion: 2.26.1-0ubuntu2
  Architecture: arm64
  CasperMD5CheckResult: unknown
  Date: Tue Oct 10 13:43:00 2023
  ErrorMessage: subproces van pakket initramfs-tools werd script 
post-installation geïnstalleerd gaf de foutwaarde 1 terug
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.11, Python 3.11.4, python3-minimal, 3.11.2-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.21.21ubuntu1
   apt  2.6.0ubuntu0.1
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.142ubuntu2.2 failed to install/upgrade: 
subproces van pakket initramfs-tools werd script post-installation 
geïnstalleerd gaf de foutwaarde 1 terug
  UpgradeStatus: Upgraded to lunar on 2023-10-10 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2038918/+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 2039422] Re: Feature request: allow user to check 'Show password' by default in the WiFi password dialogue

2023-10-16 Thread Sebastien Bacher
Thank you for your bug report, that would be a request for upstream and
probably in the frontend side. Which destop environment are you using?
If GNOME then it's probably a request to have the option in gnome-shell
there

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Feature request: allow user to check 'Show password' by default in the
  WiFi password dialogue

Status in network-manager package in Ubuntu:
  New

Bug description:
  Whenever I connect to a new WiFi network, the password dialogue pops
  up. Every time (and I do mean literally every time), I end up clicking
  on the 'Show password' checkbox to make sure that I got it right. I
  understand the reasoning behind obscuring password fields, but for the
  vast majority of users, a WiFi password is not a personal secret. It's
  known to everyone in the same physical location, and obscuring the
  password is primarily a protection against shoulder surfing. It's
  usually also long and not easily memorable. I would like to request a
  user option to always check the 'Show password' box by default, which
  would initially be set to off (in other words, keeping the current
  behaviour by default, but allowing opt-in).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2039422/+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 1547589] Re: rtkit-daemon flooding syslog

2023-10-16 Thread Sebastien Bacher
We might want to distro patch https://github.com/heftig/rtkit/pull/33
there

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

Title:
  rtkit-daemon flooding syslog

Status in Rtkit:
  New
Status in rtkit package in Ubuntu:
  Confirmed
Status in rtkit package in Debian:
  Confirmed

Bug description:
  rtkit is flooding syslog with the following:

  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.

  This may be related to but #1547585

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: rtkit 0.11-4
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 19 11:42:58 2016
  InstallationDate: Installed on 2016-02-11 (7 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  SourcePackage: rtkit
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/rtkit/+bug/1547589/+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 1547589] Re: rtkit-daemon flooding syslog

2023-10-16 Thread Ubuntu QA Website
This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
https://iso.qa.ubuntu.com/qatracker/reports/bugs/1547589

** Tags added: iso-testing

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

Title:
  rtkit-daemon flooding syslog

Status in Rtkit:
  New
Status in rtkit package in Ubuntu:
  Confirmed
Status in rtkit package in Debian:
  Confirmed

Bug description:
  rtkit is flooding syslog with the following:

  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.

  This may be related to but #1547585

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: rtkit 0.11-4
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 19 11:42:58 2016
  InstallationDate: Installed on 2016-02-11 (7 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  SourcePackage: rtkit
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/rtkit/+bug/1547589/+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 2039342] Re: package linux-image-6.5.0-1005-raspi 6.5.0-1005.7 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2023-10-16 Thread Benjamin Drung
Thank you for taking the time to report this bug and helping to make
Ubuntu better. The relevant dpkg terminal log says:

E: /usr/share/initramfs-tools/hooks/dhcpcd failed with return 1.

Sadly there is no error message explaining the exit code 1. Can you move
/usr/share/initramfs-tools/hooks/dhcpcd back and add "set -x" (without
the quotes) to the script and then run update-initramfs to get more log
output?

sudo nano /usr/share/initramfs-tools/hooks/dhcpcd
sudo update-initramfs -u

Please attach the output to the bug report then.

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Incomplete

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

Title:
  package linux-image-6.5.0-1005-raspi 6.5.0-1005.7 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  Incomplete

Bug description:
  This happened during the upgrade.

  ProblemType: Package
  DistroRelease: Ubuntu 23.10
  Package: linux-image-6.5.0-1005-raspi 6.5.0-1005.7
  ProcVersionSignature: Ubuntu 6.2.0-1014.16-raspi 6.2.16
  Uname: Linux 6.2.0-1014-raspi aarch64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CloudArchitecture: aarch64
  CloudBuildName: server
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSerial:
   
  CloudSubPlatform: config-disk (/dev/sdb1)
  Date: Sat Oct 14 09:07:02 2023
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  ImageMediaBuild: 20210201.1
  Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.22.0ubuntu1
   apt  2.7.3
  SourcePackage: initramfs-tools
  Title: package linux-image-6.5.0-1005-raspi 6.5.0-1005.7 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to mantic on 2023-10-14 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2039342/+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 2039411] Re: Addition of ppa repository failing intermittently

2023-10-16 Thread Manfred Hampl
The correct PPA naming is ppa:longsleep/golang-backports and
ppa:criu/ppa without tilde character and without "/ubuntu" in the
middle.

Eventually the code of the script should be modified to cater for usage
with wrong-named PPAs.

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

Title:
  Addition of ppa repository failing intermittently

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  I get following error intermittently when trying to add ppa repository:
  $ sudo add-apt-repository ppa:~longsleep/ubuntu/golang-backports
  Cannot add PPA: 'ppa:~longsleep/ubuntu/golang-backports'.
  The user named '~longsleep' has no PPA named 'ubuntu/golang-backports'
  Please choose from the following available PPAs:
   * 'bcmwl':  bcmwl
   * 'couchdb':  Apache CouchDB
   * 'couchdb-precise-backport':  Apache CouchDB with Erlang 18 for precise
   * 'createrepo-backports':  Createrepo Backports
   * 'firehol-backports':  Firehol Backports
   * 'golang-backports':  Golang Backports
   * 'golang-backports-dev':  Golang Backports Dev
   * 'iridium-browser-dev':  Iridium Browser Dev dependencies
   * 'pixel-extras':  Pixel extras
   * 'python2.7-backports':  Python 2.7 Backports
   * 'python3-m2crypto-backports':  Python 3 M2Crypto backports
   * 'stuff':  Stuff
   * 'ubuntu-pine64-flavour-makers':  Ubuntu Pine64 Makers PPA

  After multiple attempts, it may succeed, but the same above command sometimes 
may return following error as well (intermittently):
  $ sudo add-apt-repository ppa:~longsleep/ubuntu/golang-backports
  Traceback (most recent call last):
File "/usr/bin/add-apt-repository", line 137, in 
  shortcut = shortcut_handler(line)
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
885, in shortcut_handler
  ret = factory(shortcut)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 469, 
in shortcut_handler
  return PPAShortcutHandler(shortcut)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 426, 
in __init__
  info = get_ppa_info(self.shortcut)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 392, 
in get_ppa_info
  _get_suggested_ppa_message(user, ppa))
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 349, 
in _get_suggested_ppa_message
  lp_user = get_info_from_lp(LAUNCHPAD_USER_API % user)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 104, 
in get_info_from_lp
  return get_info_from_https(lp_url, True)
File "/usr/lib/python3/dist-packages/softwareproperties/ppa.py", line 98, 
in get_info_from_https
  return json.loads(data)
File "/usr/lib/python3.8/json/__init__.py", line 357, in loads
  return _default_decoder.decode(s)
File "/usr/lib/python3.8/json/decoder.py", line 337, in decode
  obj, end = self.raw_decode(s, idx=_w(s, 0).end())
File "/usr/lib/python3.8/json/decoder.py", line 355, in raw_decode
  raise JSONDecodeError("Expecting value", s, err.value) from None
  json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2039411/+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 2039422] [NEW] Feature request: allow user to check 'Show password' by default in the WiFi password dialogue

2023-10-16 Thread Kitserve
Public bug reported:

Whenever I connect to a new WiFi network, the password dialogue pops up.
Every time (and I do mean literally every time), I end up clicking on
the 'Show password' checkbox to make sure that I got it right. I
understand the reasoning behind obscuring password fields, but for the
vast majority of users, a WiFi password is not a personal secret. It's
known to everyone in the same physical location, and obscuring the
password is primarily a protection against shoulder surfing. It's
usually also long and not easily memorable. I would like to request a
user option to always check the 'Show password' box by default, which
would initially be set to off (in other words, keeping the current
behaviour by default, but allowing opt-in).

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

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

Title:
  Feature request: allow user to check 'Show password' by default in the
  WiFi password dialogue

Status in network-manager package in Ubuntu:
  New

Bug description:
  Whenever I connect to a new WiFi network, the password dialogue pops
  up. Every time (and I do mean literally every time), I end up clicking
  on the 'Show password' checkbox to make sure that I got it right. I
  understand the reasoning behind obscuring password fields, but for the
  vast majority of users, a WiFi password is not a personal secret. It's
  known to everyone in the same physical location, and obscuring the
  password is primarily a protection against shoulder surfing. It's
  usually also long and not easily memorable. I would like to request a
  user option to always check the 'Show password' box by default, which
  would initially be set to off (in other words, keeping the current
  behaviour by default, but allowing opt-in).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2039422/+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 2035385] Re: update-initramfs fails: /usr/share/initramfs-tools/hooks/fuse failed with return 1.

2023-10-16 Thread Benjamin Drung
There might be multiple reasons for the bash script to exit with code 1.

The package fuse3 ships both files: /usr/share/initramfs-
tools/hooks/fuse and /sbin/mount.fuse3. So /sbin/mount.fuse3 should be
present.

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

Title:
  update-initramfs fails: /usr/share/initramfs-tools/hooks/fuse failed
  with return 1.

Status in fuse3 package in Ubuntu:
  Incomplete

Bug description:
  The system is not fully updated and gives the following error
  Setting up initramfs-tools (0.136ubuntu6.7) ...   
   
  update-initramfs: deferring update (trigger activated)
   
  Processing triggers for initramfs-tools (0.136ubuntu6.7) ...  
   
  update-initramfs: Generating /boot/initrd.img-5.4.0-162-generic   
   

   
  E: /usr/share/initramfs-tools/hooks/fuse failed with return 1.
   
  update-initramfs: failed for /boot/initrd.img-5.4.0-162-generic with 1.   
   
  dpkg: error processing package initramfs-tools (--configure): 
   
   installed initramfs-tools package post-installation script subprocess 
returned error exit status 1  
  Errors were encountered while processing: 
   
   initramfs-tools

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6.7
  ProcVersionSignature: Ubuntu 5.4.0-162.179-generic 5.4.246
  Uname: Linux 5.4.0-162-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Sep 13 19:39:18 2023
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python3.8, Python 3.8.10, python-is-python3, 3.8.2-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.9
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to focal on 2023-09-13 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fuse3/+bug/2035385/+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 2035385] Re: update-initramfs fails: /usr/share/initramfs-tools/hooks/fuse failed with return 1.

2023-10-16 Thread Benjamin Drung
Re-assigning from initramfs-tools to fuse3.

** Package changed: initramfs-tools (Ubuntu) => fuse3 (Ubuntu)

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

Title:
  update-initramfs fails: /usr/share/initramfs-tools/hooks/fuse failed
  with return 1.

Status in fuse3 package in Ubuntu:
  Incomplete

Bug description:
  The system is not fully updated and gives the following error
  Setting up initramfs-tools (0.136ubuntu6.7) ...   
   
  update-initramfs: deferring update (trigger activated)
   
  Processing triggers for initramfs-tools (0.136ubuntu6.7) ...  
   
  update-initramfs: Generating /boot/initrd.img-5.4.0-162-generic   
   

   
  E: /usr/share/initramfs-tools/hooks/fuse failed with return 1.
   
  update-initramfs: failed for /boot/initrd.img-5.4.0-162-generic with 1.   
   
  dpkg: error processing package initramfs-tools (--configure): 
   
   installed initramfs-tools package post-installation script subprocess 
returned error exit status 1  
  Errors were encountered while processing: 
   
   initramfs-tools

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6.7
  ProcVersionSignature: Ubuntu 5.4.0-162.179-generic 5.4.246
  Uname: Linux 5.4.0-162-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.27
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Sep 13 19:39:18 2023
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: /usr/bin/python3.8, Python 3.8.10, python-is-python3, 3.8.2-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3.2
   apt  2.0.9
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to focal on 2023-09-13 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fuse3/+bug/2035385/+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 2039371] Re: package network-manager 1.44.2-1ubuntu1 failed to install/upgrade: installed network-manager package post-installation script subprocess was killed by signal (Termin

2023-10-16 Thread Danilo Egea Gondolfo
Hello, thank you for reporting that.

May I ask you to attach the full NetworkManager journal so we can
understand better what is happening?

You can collect it with the command below:

journalctl -u NetworkManager > network-manager.log

It would be very helpful. Thanks!

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

Title:
  package network-manager 1.44.2-1ubuntu1 failed to install/upgrade:
  installed network-manager package post-installation script subprocess
  was killed by signal (Terminated)

Status in network-manager package in Ubuntu:
  New

Bug description:
  With do-release-upgrade -d, Setting up network-manager hanged
  indefinitely with

  [...]
  Setting up network-manager (1.44.2-1ubuntu1) ...
  SKIP: NetworkManager is not ready ...
  SKIP: NetworkManager is not ready ...
  SKIP: NetworkManager is not ready ...
  SKIP: NetworkManager is not ready ...
  SKIP: NetworkManager is not ready ...
  ^[[CSKIP: NetworkManager is not ready ...
  SKIP: NetworkManager is not ready ...
  SKIP: NetworkManager is not ready ...
  SKIP: NetworkManager is not ready ...
  SKIP: NetworkManager is not ready ...
  SKIP: NetworkManager is not ready ...
  SKIP: NetworkManager is not ready ...
  [...]

  Killing it resulted in

  Terminated
  SKIP: NetworkManager is not ready ...
  dpkg: error processing package network-manager (--configure):
   installed network-manager package post-installation script subprocess was 
killed by signal (Terminated)

  ProblemType: Package
  DistroRelease: Ubuntu 23.10
  Package: network-manager 1.44.2-1ubuntu1
  ProcVersionSignature: Ubuntu 6.2.0-34.34-generic 6.2.16
  Uname: Linux 6.2.0-34-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Sun Oct 15 00:40:40 2023
  ErrorMessage: installed network-manager package post-installation script 
subprocess was killed by signal (Terminated)
  InstallationDate: Installed on 2023-01-13 (274 days ago)
  InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020)
  IpRoute:
   default via 192.168.0.254 dev wlp2s0 proto dhcp src 192.168.0.29 metric 600 
   169.254.0.0/16 dev docker0 scope link metric 1000 linkdown 
   172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 linkdown 
   192.168.0.0/24 dev wlp2s0 proto kernel scope link src 192.168.0.29 metric 
600 
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
  PythonDetails: /usr/bin/python3.11, Python 3.11.6, python-is-python3, 3.11.4-1
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.22.0ubuntu1
   apt  2.7.3
  SourcePackage: network-manager
  Title: package network-manager 1.44.2-1ubuntu1 failed to install/upgrade: 
installed network-manager package post-installation script subprocess was 
killed by signal (Terminated)
  UpgradeStatus: Upgraded to mantic on 2023-10-14 (0 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP   CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.44.2   connected  starting  full  enabled enabled  
enabled  missing  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2039371/+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 1547589] Re: rtkit-daemon flooding syslog

2023-10-16 Thread corrado venturini
Still same problem on Ubuntu Mantic 23.10

Oct 14 21:10:32 corrado-n2-mantic rtkit-daemon[1212]: Supervising 9 threads of 
6 processes of 1 users.
Oct 14 21:10:32 corrado-n2-mantic rtkit-daemon[1212]: Supervising 9 threads of 
6 processes of 1 users.
Oct 14 21:10:36 corrado-n2-mantic rtkit-daemon[1212]: Supervising 9 threads of 
6 processes of 1 users.
Oct 14 21:10:36 corrado-n2-mantic rtkit-daemon[1212]: Supervising 9 threads of 
6 processes of 1 users.

corrado@corrado-n2-mantic:~$ journalctl -b -1 > journal.txt
corrado@corrado-n2-mantic:~$ wc -l journal.txt
12231 journal.txt
corrado@corrado-n2-mantic:~$ grep -o 'Supervising 9 threads' journal.txt | wc -l
1032

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

Title:
  rtkit-daemon flooding syslog

Status in Rtkit:
  New
Status in rtkit package in Ubuntu:
  Confirmed
Status in rtkit package in Debian:
  Confirmed

Bug description:
  rtkit is flooding syslog with the following:

  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Supervising 0 threads of 0 
processes of 1 users.
  Feb 19 11:42:07 galactica rtkit-daemon[20798]: Warning: Reached burst limit 
for user '1000', denying request.

  This may be related to but #1547585

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: rtkit 0.11-4
  ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
  Uname: Linux 4.4.0-6-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 19 11:42:58 2016
  InstallationDate: Installed on 2016-02-11 (7 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160210)
  SourcePackage: rtkit
  UpgradeStatus: No upgrade log present (probably fresh install)

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