date:20230704

[Touch-packages] [Bug 1852911] Re: CriticalPowerAction=Suspend should be supported

2023-07-04 Thread Bug Watch Updater

** Changed in: upower
   Status: New => Fix Released

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

Title:
  CriticalPowerAction=Suspend should be supported

Status in Upower:
  Fix Released
Status in upower package in Ubuntu:
  Triaged

Bug description:
  The action to take when the battery is critical can only be one of the
  following:

  # Possible values are:
  # PowerOff
  # Hibernate
  # HybridSleep

  Adding Suspend to that list makes perfect sense. My laptop is
  currently powering off on low power which is useless as I'll be losing
  my work anyway. Might as well suspend and allow me to notice that and
  connect a charger. If the thinking is that suspend uses power I can
  set a high enough threshold to give me some margin.

  The failovers are:

  # If HybridSleep isn't available, Hibernate will be used
  # If Hibernate isn't available, PowerOff will be used

  I'd argue Suspend should actually come before PowerOff in that list.
  For most laptop users having their computer suspend because they
  didn't notice the battery was running out is very easy to fix and
  takes no time. They'll just connect the charger. If however the
  computer needs to be completely rebooted, not only does that take a
  lot more time it will very likely cause lost work.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: upower 0.99.10-1
  ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Nov 17 14:32:13 2019
  InstallationDate: Installed on 2019-05-09 (191 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: upower
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/upower/+bug/1852911/+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 1623173] Re: [Asus ZenBook UX501VW] Function key to toggle the screen doesn't work

2023-07-04 Thread Launchpad Bug Tracker

[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  [Asus ZenBook UX501VW] Function key to toggle the screen doesn't work

Status in xorg package in Ubuntu:
  Expired

Bug description:
  On Ubuntu Ubuntu 16.04.1 LTS with all the latest kernels installed
  from http://kernel.ubuntu.com/~kernel-ppa/mainline/ : 4.4.19, 4.5.7,
  4.6.7, 4.7.3 nor 4.8-rc6.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.8.0-040800rc6-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] est un dossier: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  367.44  Wed Aug 17 22:24:07 
PDT 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.2)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  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: Tue Sep 13 21:49:46 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Skylake Integrated Graphics [1043:1080]
 Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1080]
  InstallationDate: Installed on 2016-06-01 (104 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 046d:c069 Logitech, Inc. M-U0007 [Corded Mouse M500]
   Bus 001 Device 002: ID 04f2:b3fd Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. N501VW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-040800rc6-generic 
root=UUID=ad612961-a4ae-4950-9d5a-20dcf8e56681 ro quiet splash acpi_osi= 
acpi_backlight=native nouveau.modeset=0 nvidia.nomodeset=0 i915.nomodeset=0 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/09/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N501VW.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N501VW
  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.:bvrN501VW.300:bd05/09/2016:svnASUSTeKCOMPUTERINC.:pnN501VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN501VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N501VW
  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.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Sep 13 21:14:29 2016
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   [drm] Failed to open DRM device for (null): -22
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   12876 
   vendor SDC
  xserver.version: 2:1.18.3-1ubuntu2.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1623173/+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 1666088] Re: In my notebook Samsung Q330 excess VGA-1 display

2023-07-04 Thread Launchpad Bug Tracker

[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  In my notebook Samsung Q330 excess VGA-1 display

Status in xorg package in Ubuntu:
  Expired

Bug description:
  After install excess VGA-1 display.
  I may disable VGA-1 in screen. I use Laptop Screen, 1366x768.
  If i conncect external monitor through vga cable, In displays appears 
VGA-1-2, it is work.
  My video:
  00:02.0 VGA compatible controller: Intel Corporation Core Processor 
Integrated Graphics Controller (rev 02)
  02:00.0 VGA compatible controller: NVIDIA Corporation GT218M [GeForce 310M] 
(rev a2)

  lsmod:
  nouveau  1404928  1
  i915 1245184  21

  it is in 4.8 kernel and in 4.4 kernel KUBUNTU 16.04.2 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg (not installed)
  ProcVersionSignature: Ubuntu 4.8.0-36.36~16.04.1-generic 4.8.11
  Uname: Linux 4.8.0-36-generic i686
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: i386
  Date: Mon Feb 20 05:40:12 2017
  InstallationDate: Installed on 2016-05-03 (292 days ago)
  InstallationMedia: Kubuntu 16.04 LTS "Xenial Xerus" - Release i386 
(20160420.1)
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1666088/+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 1685772] Re: Too high CPU frequency

2023-07-04 Thread Launchpad Bug Tracker

[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  Too high CPU frequency

Status in xorg package in Ubuntu:
  Expired

Bug description:
  Hallo, the cpu  running is always  to high (35%-45%).
  The compiz Prozess need always power.
  I need help to configure Ubuntu right.
  Ähmm, i can German.

  Hear u scudelin

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  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: Mon Apr 24 12:58:04 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   3Dfx Interactive, Inc. Voodoo 4 / Voodoo 5 [121a:0009] (rev 01) (prog-if 00 
[VGA controller])
 Subsystem: 3Dfx Interactive, Inc. Voodoo5 PCI 5500 [121a:0003]
  InstallationDate: Installed on 2017-03-22 (32 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 001 Device 002: ID 058f:6387 Alcor Micro Corp. Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth 
Dongle (HCI mode)
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: MSI MS-7250
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic 
root=UUID=d9822317-7575-424c-9308-78678355dc5c ro quiet splash vt.handoff=7
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/31/2007
  dmi.bios.vendor: MS-7250
  dmi.bios.version: V1.8
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MS-7250
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnMS-7250:bvrV1.8:bd07/31/2007:svnMSI:pnMS-7250:pvr1.0:rvnMSI:rnMS-7250:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: MS-7250
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-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 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Apr 24 12:39:03 2017
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputAT Translated Set 2 keyboard KEYBOARD, id 8
   inputImExPS/2 Generic Explorer Mouse MOUSE, id 9
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.18.4-0ubuntu0.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1685772/+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 2025666] Re: Please merge 1.225-1 into mantic

2023-07-04 Thread Lucas Kanashiro

Thanks Danilo, I just added a comment to your MP.

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

Title:
  Please merge 1.225-1 into mantic

Status in netcat-openbsd package in Ubuntu:
  New

Bug description:
  PPA https://launchpad.net/~danilogondolfo/+archive/ubuntu/netcat-
  openbsd

  Autopkgtest https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-
  danilogondolfo-netcat-openbsd/mantic/amd64/n/netcat-
  openbsd/20230703_202110_fccf3@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netcat-openbsd/+bug/2025666/+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 2025525] Re: package libperl5.34:amd64 5.34.0-3ubuntu1.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting config

2023-07-04 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package libperl5.34:amd64 5.34.0-3ubuntu1.2 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in perl package in Ubuntu:
  New

Bug description:
  i don't knwo what happened..it started giving bugs automatically..i
  just now installed it

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: libperl5.34:amd64 5.34.0-3ubuntu1.2
  ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Sat Jul  1 13:22:02 2023
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2023-07-01 (0 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.8
  SourcePackage: perl
  Title: package libperl5.34:amd64 5.34.0-3ubuntu1.2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

2023-07-04 Thread Paulo Flabiano Smorigo

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

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

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  what i have done  is not journal boot file

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-image-5.15.0-76-generic 5.15.0-76.83
  ProcVersionSignature: Ubuntu 5.19.0-45.46~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-45-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  richard2167 F pulseaudio
   /dev/snd/controlC2:  richard2167 F pulseaudio
   /dev/snd/controlC1:  richard2167 F pulseaudio
  CasperMD5CheckResult: unknown
  Date: Thu Jun 29 13:36:04 2023
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2023-02-14 (134 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-45-generic 
root=UUID=c4093c70-14d4-4d70-a42a-0b8baa53982c ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.06-2ubuntu7.2
  SourcePackage: initramfs-tools
  StagingDrivers: atomisp_gmin_platform atomisp_lm3554
  Title: package linux-image-5.15.0-76-generic 5.15.0-76.83 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to jammy on 2023-02-14 (134 days ago)
  dmi.bios.date: 10/31/2014
  dmi.bios.release: 5.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.40
  dmi.board.name: Q1900-ITX
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.40:bd10/31/2014:br5.6:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnQ1900-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:skuToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2025315/+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 2025525] Re: package libperl5.34:amd64 5.34.0-3ubuntu1.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting config

2023-07-04 Thread Paulo Flabiano Smorigo

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  package libperl5.34:amd64 5.34.0-3ubuntu1.2 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in perl package in Ubuntu:
  New

Bug description:
  i don't knwo what happened..it started giving bugs automatically..i
  just now installed it

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: libperl5.34:amd64 5.34.0-3ubuntu1.2
  ProcVersionSignature: Ubuntu 5.19.0-46.47~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-46-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Sat Jul  1 13:22:02 2023
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2023-07-01 (0 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.21.1ubuntu2.2
   apt  2.4.8
  SourcePackage: perl
  Title: package libperl5.34:amd64 5.34.0-3ubuntu1.2 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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


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

[Touch-packages] [Bug 1991606] Autopkgtest regression report (dput/1.1.2ubuntu2.1)

2023-07-04 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted dput (1.1.2ubuntu2.1) for kinetic have 
finished running.
The following regressions have been reported in tests triggered by the package:

dgit/blacklisted (s390x)


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

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

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

Thank you!

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

Title:
  Invalid PEP440 package version breaking setuptools >= 66

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

Bug description:
  [ Impact ]

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

    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 844, in _resolve_dist
  env = Environment(self.entries)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1044, in __init__
  self.scan(search_path)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1077, in scan
  self.add(dist)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1096, in add
  dists.sort(key=operator.attrgetter('hashcmp'), reverse=True)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2631, in hashcmp
  self.parsed_version,
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2678, in parsed_version
  self._parsed_version = parse_version(self.version)
    File

[Touch-packages] [Bug 1991606] Autopkgtest regression report (dput/1.1.3ubuntu2.1)

2023-07-04 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted dput (1.1.3ubuntu2.1) for lunar have 
finished running.
The following regressions have been reported in tests triggered by the package:

dgit/blacklisted (s390x)


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

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

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

Thank you!

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

Title:
  Invalid PEP440 package version breaking setuptools >= 66

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

Bug description:
  [ Impact ]

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

    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 844, in _resolve_dist
  env = Environment(self.entries)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1044, in __init__
  self.scan(search_path)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1077, in scan
  self.add(dist)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1096, in add
  dists.sort(key=operator.attrgetter('hashcmp'), reverse=True)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2631, in hashcmp
  self.parsed_version,
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2678, in parsed_version
  self._parsed_version = parse_version(self.version)
    File

[Touch-packages] [Bug 1991606] Autopkgtest regression report (dput/1.1.0ubuntu2.1)

2023-07-04 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted dput (1.1.0ubuntu2.1) for jammy have 
finished running.
The following regressions have been reported in tests triggered by the package:

dgit/blacklisted (s390x)


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

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

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

Thank you!

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

Title:
  Invalid PEP440 package version breaking setuptools >= 66

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

Bug description:
  [ Impact ]

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

    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 844, in _resolve_dist
  env = Environment(self.entries)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1044, in __init__
  self.scan(search_path)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1077, in scan
  self.add(dist)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 1096, in add
  dists.sort(key=operator.attrgetter('hashcmp'), reverse=True)
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2631, in hashcmp
  self.parsed_version,
    File 
"/builds/databiosphere/toil/venv/lib/python3.9/site-packages/pkg_resources/__init__.py",
 line 2678, in parsed_version
  self._parsed_version = parse_version(self.version)
    File

[Touch-packages] [Bug 2025526] Re: Printer is not available in chromium snap

2023-07-04 Thread Heiko Gimbel

Here is the output as it is now after switching from driverless printing
to a cups driver for my printer.

lpstat -v
Gerät für HP_Officejet_Pro_8610_2414BB: 
implicitclass://HP_Officejet_Pro_8610_2414BB/
Gerät für HP_Officejet_Pro_8610_2414BB@HPFC3FDB2414BB.local: 
implicitclass://HP_Officejet_Pro_8610_2414BB%40HPFC3FDB2414BB.local/

lpstat -p
Drucker HP_Officejet_Pro_8610_2414BB ist im Leerlauf.  Aktiviert seit Mo 03 Jul 
2023 15:10:43 CEST
Drucker HP_Officejet_Pro_8610_2414BB@HPFC3FDB2414BB.local ist im Leerlauf.  
Aktiviert seit Di 04 Jul 2023 16:40:45 CEST

cups.lpstat -v
device for HP_Officejet_Pro_8610_2414BB: 
proxy://%2Frun%2Fcups%2Fcups.sock/HP_Officejet_Pro_8610_2414BB
device for HP_Officejet_Pro_8610_2414BB@HPFC3FDB2414BB.local: 
proxy://%2Frun%2Fcups%2Fcups.sock/HP_Officejet_Pro_8610_2414BB@HPFC3FDB2414BB.local

cups.lpstat -p
printer HP_Officejet_Pro_8610_2414BB is idle.  enabled since Mon Jul  3 
15:15:20 2023
printer HP_Officejet_Pro_8610_2414BB@HPFC3FDB2414BB.local is idle.  enabled 
since Tue Jul  4 16:40:45 2023

snap list | grep cups
cups2.4.6-1 962   
latest/stable  openprinting**  -

snap connections cups
SchnittstellePlug  Slot 
 Notizen
avahi-controlcups:avahi-control:avahi-control   
 -
cups chromium:cups cups:cups
 -
cups-control - cups:cups-server 
 -
cups-control cups:cups-control :cups-control
 -
home cups:home :home
 -
network  cups:network  :network 
 -
network-bind cups:network-bind :network-bind
 -
network-manager-observe  cups:network-manager-observe  :network-manager-observe 
 -
raw-usb  cups:raw-usb  :raw-usb 
 -
system-files cups:etc-cups :system-files
 -

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

Title:
  Printer is not available in chromium snap

Status in chromium-browser package in Ubuntu:
  Incomplete
Status in cups package in Ubuntu:
  Incomplete

Bug description:
  My printer is not available in chromium. I had the same problem in firefox 
but fixed it with the following command:

sudo snap connect firefox:cups-control

  However this did not work with the chromium snap. I got the following
  error:

snap "chromium" has no plug named "cups-control"

  My printer is a network printer and is automatically detected by my
  Kubuntu install. It works out of the box with all native apps and
  flatpaks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2025526/+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 2024164] Re: Replace dhclient with dhcpcd

2023-07-04 Thread Benjamin Drung

Pushed change to ubuntu/devel-dhcpcd branch:
https://code.launchpad.net/~ubuntu-core-dev/ubuntu/+source/initramfs-tools/+git/initramfs-tools/+ref/ubuntu/devel-dhcpcd

The upload needs to wait for the dhcpcd MIR in bug #2019191

** Changed in: initramfs-tools (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  Replace dhclient with dhcpcd

Status in initramfs-tools package in Ubuntu:
  In Progress

Bug description:
  ISC has announced the end of life for ISC DHCP as of the end of 2022.
  Kea is the recommended successor of the DHCP server (isc-dhcp-server).
  This bug report is about replacing the DHCP client (isc-dhcp-client).

  Ubuntu uses NetworkManager on the desktop and systemd-networkd on the
  server as default DHCP client. However isc-dhcp-client is still
  installed as part of all Ubuntu systems, because it is the only client
  implementation that integrates with initramfs-tools. isc-dhcp-client
  is also used by cloud-init and as a command line tool to configure
  transient DHCP on an interface.

  There are following requirements for the replacement DHCP client:
  1. The DHCP client must support DHCPv6.
  2. The DHCP client in the initramfs should be small enough to not increase 
the size noticeable.
  3. The DHCP client needs to be callable from the shell (for initramfs and 
cloud-init)

  The Ubuntu desktop uses network-manager and the server/cloud images
  uses systemd-networkd. So there is no need for changing the DHCP
  client on booted systems, but the initramfs uses dhclient from isc-
  dhcp-client.

  ipconfig (from klibc-utils) does not support DHCPv6 (but there is work
  in progress in
  https://git.kernel.org/pub/scm/linux/kernel/git/bwh/klibc.git/?h=ipv6).
  systemd-networkd, network-manager, and dhcpcanon pull in too many
  packages/libraries for the initramfs use case (unless using a systemd-
  based boot). For example, /lib/systemd/systemd-networkd is 1.6 MB big
  and directly depends on 24 libraries.

  systemd-networkd is designed to run as a service. It takes no
  arguments when called. So it must run as daemon.

  Therefore only dhcpcd and udhcpc remain as replacement (for the initramfs). 
From those two, I propose to use dhcpcd as replacement, because:
  * It has many features (like classless static routes or DHCP over InfiniBand)
  * It is actively developed (normally a few release per year)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2024164/+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 2011385] Re: [950XED, Realtek ALC298, Speaker, Internal] No sound at all

2023-07-04 Thread Tom Mason

Same issue on a Razer Blade 16 - other reports across the linux eco
system:

https://bbs.archlinux.org/viewtopic.php?id=285121
https://www.linuxquestions.org/questions/showthread.php?s=5778bfa3e63dcd856bc4b35c608837e9=6419132#post6419132
https://www.reddit.com/r/pop_os/comments/110vjt3/pop_on_razer_blade_18/
https://github.com/pop-os/linux/issues/246

** Bug watch added: github.com/pop-os/linux/issues #246
   https://github.com/pop-os/linux/issues/246

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

Title:
  [950XED, Realtek ALC298, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  only bluetooth can work,im sungsang book2 pro

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.19.0-35.36~22.04.1-generic 5.19.17
  Uname: Linux 5.19.0-35-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.3
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wang   1658 F pulseaudio
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 13 15:41:47 2023
  InstallationDate: Installed on 2023-03-08 (4 days ago)
  InstallationMedia: Ubuntu 22.04.2 LTS "Jammy Jellyfish" - Release amd64 
(20230223)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:sofhdadsp failed
  Symptom_Card: sof-hda-dsp - sof-hda-dsp
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  wang   1658 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [950XED, Realtek ALC298, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/17/2022
  dmi.bios.release: 5.25
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: P08RGF.054.220817.ZQ
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NT950XEW-A51AS
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGLFREEDOS-C00-R000-S+1.0.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrP08RGF.054.220817.ZQ:bd08/17/2022:br5.25:svnSAMSUNGELECTRONICSCO.,LTD.:pn950XED:pvrP08RGF:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNT950XEW-A51AS:rvrSGLFREEDOS-C00-R000-S+1.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:skuSCAI-ICPS-A5A5-ADLP-PRGF:
  dmi.product.family: Galaxy Book2 Pro
  dmi.product.name: 950XED
  dmi.product.sku: SCAI-ICPS-A5A5-ADLP-PRGF
  dmi.product.version: P08RGF
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2011385/+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 2025363] Re: Merge console-setup 1.222 into mantic

2023-07-04 Thread Heinrich Schuchardt

Thanks Lukas for reviewing.

The changes in Keyboard/KeyboardNames.pl were introduced by running
dpkg-buildpackage -S -sa -d.

I will look into it again.

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

Title:
  Merge console-setup 1.222 into mantic

Status in console-setup package in Ubuntu:
  Incomplete

Bug description:
  The Debian package has been upgraded to release 1.222. According to
  the changelog this is just a rebuild.

  Rebuilding will update the keyboard names.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/2025363/+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 2025363] Re: Merge console-setup 1.222 into mantic

2023-07-04 Thread Lukas Märdian

Hi Heinrich, thank you for working on the console-setup merge.

I see you provided a debdiff patch, which tries to patch the ./CHANGES
file. This file is a symlink to debian/changelog and cannot be patched.
The patch applies cleanly when this hunk is removed.

Also, I see that this package is being maintained in git-ubuntu and
@liushuyu-011 apparently put lots of effort into separating all the
delta into logical commits:
https://git.launchpad.net/ubuntu/+source/console-
setup/log/?h=ubuntu/devel So I would feel bad about throwing away all of
this work (git history), by uploading a plain debdiff.

Furthermore, When I was trying to re-create the git-history I spotted
some differences between your debdiff and the rebased branch (see diff
below), which I'd like to ask you to investigate and explain if those
are relevant.

May I ask you to rebase your work using the git-ubuntu branches and
creating a merge-proposal attached to this bug report instead? This
should also automatically avoid the CHANGES symlink issue.


```diff
diff --git a/Keyboard/KeyboardNames.pl b/Keyboard/KeyboardNames.pl
index 8c80646..ab1beb3 100644
--- a/Keyboard/KeyboardNames.pl
+++ b/Keyboard/KeyboardNames.pl
@@ -157,7 +157,6 @@ package KeyboardNames;
 'OLPC' => 'olpc',
 'Ortek Multimedia/Internet MCK-800' => 'oretec',
 'PC-98' => 'pc98',
-'PinePhone Keyboard' => 'ppkb',
 'Propeller Voyager KTEZ-1000' => 'propeller',
 'QTronix Scorpius 98N+' => 'qtronix',
 'SVEN Ergonomic 2500' => 'sven',
@@ -249,6 +248,7 @@ package KeyboardNames;
 'Hungarian' => 'hu',
 'Icelandic' => 'is',
 'Indian' => 'in',
+'Indonesian (Javanese)' => 'jv',
 'Indonesian (Latin)' => 'id',
 'Iraqi' => 'iq',
 'Irish' => 'ie',
@@ -375,11 +375,12 @@ package KeyboardNames;
'Belarusian (Latin)' => 'latin',
'Belarusian (intl.)' => 'intl',
'Belarusian (legacy)' => 'legacy',
-   'Belarusian (phonetic)' => 'phonetic',
'Russian (Belarus)' => 'ru',
 },
 'ca' => {
-   'Canadian (CSA)' => 'multix',
+   'Canadian (intl.)' => 'multix',
+   'Canadian (intl., 1st part)' => 'multi',
+   'Canadian (intl., 2nd part)' => 'multi-2gr',
'English (Canada)' => 'eng',
'French (Canada, Dvorak)' => 'fr-dvorak',
'French (Canada, legacy)' => 'fr-legacy',
@@ -485,12 +486,12 @@ package KeyboardNames;
'Faroese (no dead keys)' => 'nodeadkeys',
 },
 'fr' => {
-   'Breton (France)' => 'bre',
'French (AZERTY)' => 'azerty',
'French (AZERTY, AFNOR)' => 'afnor',
'French (BEPO)' => 'bepo',
'French (BEPO, AFNOR)' => 'bepo_afnor',
'French (BEPO, Latin-9 only)' => 'bepo_latin9',
+   'French (Breton)' => 'bre',
'French (Dvorak)' => 'dvorak',
'French (Macintosh)' => 'mac',
'French (US)' => 'us',
@@ -565,10 +566,8 @@ package KeyboardNames;
'Hungarian (standard)' => 'standard',
 },
 'id' => {
-   'Indonesian (Arab Melayu, extended phonetic)' => 'melayu-phoneticx',
-   'Indonesian (Arab Melayu, phonetic)' => 'melayu-phonetic',
-   'Indonesian (Arab Pegon, phonetic)' => 'pegon-phonetic',
-   'Javanese' => 'javanese',
+   'Indonesian (Arab Pegon, extended phonetic)' => 'phoneticx',
+   'Indonesian (Arab Pegon, phonetic)' => 'phonetic',
 },
 'ie' => {
'CloGaelach' => 'CloGaelach',
@@ -590,7 +589,6 @@ package KeyboardNames;
'Bangla (India, Probhat)' => 'ben_probhat',
'English (India, with rupee)' => 'eng',
'Gujarati' => 'guj',
-   'Gujarati (KaGaPa, phonetic)' => 'guj-kagapa',
'Hindi (Bolnagri)' => 'bolnagri',
'Hindi (KaGaPa, phonetic)' => 'hin-kagapa',
'Hindi (Wx)' => 'hin-wx',
@@ -610,12 +608,11 @@ package KeyboardNames;
'Punjabi (Gurmukhi Jhelum)' => 'jhelum',
'Punjabi (Gurmukhi)' => 'guru',
'Sanskrit (KaGaPa, phonetic)' => 'san-kagapa',
-   'Tamil (InScript, with Arabic numerals)' => 'tam',
-   'Tamil (InScript, with Tamil numerals)' => 'tam_tamilnumbers',
-   'Tamil (TamilNet 99 with Tamil numerals)' => 'tamilnet_tamilnumbers',
-   'Tamil (TamilNet 99)' => 'tamilnet',
-   'Tamil (TamilNet 99, TAB encoding)' => 'tamilnet_TAB',
-   'Tamil (TamilNet 99, TSCII encoding)' => 'tamilnet_TSCII',
+   'Tamil (InScript)' => 'tam',
+   'Tamil (TamilNet 99 with Tamil numerals)' => 'tam_tamilnet_with_tam_nums',
+   'Tamil (TamilNet 99)' => 'tam_tamilnet',
+   'Tamil (TamilNet 99, TAB encoding)' => 'tam_tamilnet_TAB',
+   'Tamil (TamilNet 99, TSCII encoding)' => 'tam_tamilnet_TSCII',
'Telugu' => 'tel',
'Telugu (KaGaPa, phonetic)' => 'tel-kagapa',
'Telugu (Sarala)' => 'tel-sarala',
@@ -630,7 +627,6 @@ package KeyboardNames;
'Kurdish (Iraq, Latin Q)' => 'ku',
 },
 'ir' => {
-   'Azerbaijani (Iran)' => 'azb',
'Kurdish (Iran, Arabic-Latin)' => 'ku_ara',
'Kurdish (Iran, F)' => 'ku_f',
'Kurdish (Iran, Latin Alt-Q)' => 'ku_alt',
@@ -679,6 +675,7 @@ package KeyboardNames;
'Lao (STEA)' => 'stea',
 },
 'latam' => {
+   'Spanish (Latin American, Colemak for gaming)' => 'colemak-gaming',
'Spanish

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

2023-07-04 Thread bugproxy

--- Comment From wint...@de.ibm.com 2023-07-04 07:59 EDT---
Is this issue reproducable on your side?
Or can we close this?

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

Title:
  iptables-1.8.7/iptables/tests/shell/testcases/nft-only/0009-needless-
  bitwise_0 fails on s390x

Status in iptables:
  Unknown
Status in Ubuntu on IBM z Systems:
  In Progress
Status in iptables package in Ubuntu:
  New

Bug description:
  In Ubuntu, we execute the full iptables shell testcases across all
  architectures.

  They seem to all pass everywhere, however

  iptables-1.8.7/iptables/tests/shell/testcases/nft-only/0009-needless-
  bitwise_0

  is currently failing on s390x like so:

  command17FAIL stderr: W: [FAILED]  ././testcases/nft-
  only/0009-needless-bitwise_0: expected 0 but got 1

  i wonder if there is some endian bug, as this is currently Ubuntu's
  only big-endian architecture.

  this can be reproduced with:

  pull-lp-source iptables
  cd iptables-1.8.7/
  chmod +x ./iptables/tests/shell/testcases/iptables/0007-zero-counters_0
  cd iptables/tests/shell
  sudo ./run-tests.sh --host

To manage notifications about this bug go to:
https://bugs.launchpad.net/iptables/+bug/1974056/+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 2009743] Re: networkd: classless routes served by DHCP are created incorrectly

2023-07-04 Thread Pedro Lopes

Yes I can confirm the classless routes we are trying to serve are under
the main subnet:

10.0.0.0/8 dev enp24s0
10.88.88.0/24 via 10.10.1.2 dev enp24s0
10.96.0.0/11 via 10.10.1.2 dev enp24s0

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

Title:
  networkd: classless routes served by DHCP are created incorrectly

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  After upgrading 20.04 systems to 22.04, the classless routes served
  via DHCP are not being registered correctly - they are missing the
  gateway address.

  Expected routes - these are taken from a 20.04 system on the same
  network:

  $ ip route
  default via 10.10.1.1 dev enp24s0 proto dhcp src 10.10.64.12 metric 100
  10.0.0.0/8 dev enp24s0 proto kernel scope link src 10.10.64.12
  10.88.88.0/24 via 10.10.1.2 dev enp24s0 proto dhcp src 10.10.64.12 metric 100
  10.96.0.0/11 via 10.10.1.2 dev enp24s0 proto dhcp src 10.10.64.12 metric 100

  Actual routes - these are the routes created in one of the affected
  22.04 systems:

  $ ip route
  default via 10.10.1.1 dev bond0 proto dhcp src 10.10.48.20 metric 100
  8.8.8.8 via 10.10.1.1 dev bond0 proto dhcp src 10.10.48.20 metric 100
  10.0.0.0/8 dev bond0 proto kernel scope link src 10.10.48.20 metric 100
  10.10.1.1 dev bond0 proto dhcp scope link src 10.10.48.20 metric 100
  10.10.1.2 dev bond0 proto dhcp scope link src 10.10.48.20 metric 100
  10.88.88.0/24 dev bond0 proto dhcp scope link src 10.10.48.20 metric 100
  10.96.0.0/11 dev bond0 proto dhcp scope link src 10.10.48.20 metric 100

  Note the routes for 10.88.88.0/24 and 10.96.0.0/11 are missing the "via" 
gateway address, and therefore don't work.
  (For some reason there are also static routes created for DNS server 
(8.8.8.8) and known gateways (10.10.1.1 and 10.10.1.2). These are redundant but 
harmless.)

  Both the working and non-working systems are being managed by netplan.
  The non-working system has a bonded interface but I have checked that
  is not the cause of the problem - using a physical interface directly
  has the same result.

  I have attached the files /etc/netplan/00-installer-config.yaml and
  /run/systemd/network/10-netplan-bond0.network of the affected system.

  Affected system:
  Ubuntu version: Ubuntu 22.04.2 LTS
  systemd version: 249.11-0ubuntu3.6

  Older system not affected:
  Ubuntu version: Ubuntu 20.04.5 LTS
  systemd version: 245.4-4ubuntu3.19

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2009743/+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 1949615] Re: Notify method not working correctly in 21.10 (impish)

2023-07-04 Thread Gordon Lack

This is still an issue in 23.04 (lunar)

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

Title:
  Notify method not working correctly in 21.10 (impish)

Status in dbus package in Ubuntu:
  New

Bug description:
  The replaces_id parameter to org.freedesktop.Notifications.Notify no longer 
works correctly at 21.10.
  It is OK on 21.04.

  At 21.10 if a message with replaces_id == x ever times out then any
  further message sent with that replaces_id never gets shown.  The
  timeout-over seems to become permanent for that replaces_id.

  Example program to follow

  ProblemType: Bug
  DistroRelease: Ubuntu 21.10
  Package: dbus 1.12.20-2ubuntu2
  ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
  Uname: Linux 5.13.0-20-generic x86_64
  ApportVersion: 2.20.11-0ubuntu71
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: KDE
  Date: Wed Nov  3 16:49:18 2021
  InstallationDate: Installed on 2020-08-13 (447 days ago)
  InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  SourcePackage: dbus
  UpgradeStatus: Upgraded to impish on 2021-10-17 (17 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1949615/+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 2009743] Re: networkd: classless routes served by DHCP are created incorrectly

2023-07-04 Thread Sylvain Guglielmi

I have the same issue.

I may be wrong, but it seem to me that it's related to the following DHCP 
options : 
DHCP option 1 : [SubnetMask]
DHCP option 121 : classless static route [DestCIDR] [Gateway]
When DestCIDR is within the subnet, the gateway is dropped by systemd-networkd 
: the route is added, without gateway.

@Pedro Lopes : does this match your occurrence of the issue.

Note that dhclient does not have this bug : running dhclient adds the
correct routes.

Unfortunately for me, the concerned machines are in production. So
further testing is not easy.

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

Title:
  networkd: classless routes served by DHCP are created incorrectly

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  After upgrading 20.04 systems to 22.04, the classless routes served
  via DHCP are not being registered correctly - they are missing the
  gateway address.

  Expected routes - these are taken from a 20.04 system on the same
  network:

  $ ip route
  default via 10.10.1.1 dev enp24s0 proto dhcp src 10.10.64.12 metric 100
  10.0.0.0/8 dev enp24s0 proto kernel scope link src 10.10.64.12
  10.88.88.0/24 via 10.10.1.2 dev enp24s0 proto dhcp src 10.10.64.12 metric 100
  10.96.0.0/11 via 10.10.1.2 dev enp24s0 proto dhcp src 10.10.64.12 metric 100

  Actual routes - these are the routes created in one of the affected
  22.04 systems:

  $ ip route
  default via 10.10.1.1 dev bond0 proto dhcp src 10.10.48.20 metric 100
  8.8.8.8 via 10.10.1.1 dev bond0 proto dhcp src 10.10.48.20 metric 100
  10.0.0.0/8 dev bond0 proto kernel scope link src 10.10.48.20 metric 100
  10.10.1.1 dev bond0 proto dhcp scope link src 10.10.48.20 metric 100
  10.10.1.2 dev bond0 proto dhcp scope link src 10.10.48.20 metric 100
  10.88.88.0/24 dev bond0 proto dhcp scope link src 10.10.48.20 metric 100
  10.96.0.0/11 dev bond0 proto dhcp scope link src 10.10.48.20 metric 100

  Note the routes for 10.88.88.0/24 and 10.96.0.0/11 are missing the "via" 
gateway address, and therefore don't work.
  (For some reason there are also static routes created for DNS server 
(8.8.8.8) and known gateways (10.10.1.1 and 10.10.1.2). These are redundant but 
harmless.)

  Both the working and non-working systems are being managed by netplan.
  The non-working system has a bonded interface but I have checked that
  is not the cause of the problem - using a physical interface directly
  has the same result.

  I have attached the files /etc/netplan/00-installer-config.yaml and
  /run/systemd/network/10-netplan-bond0.network of the affected system.

  Affected system:
  Ubuntu version: Ubuntu 22.04.2 LTS
  systemd version: 249.11-0ubuntu3.6

  Older system not affected:
  Ubuntu version: Ubuntu 20.04.5 LTS
  systemd version: 245.4-4ubuntu3.19

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2009743/+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 2009743] Re: networkd: classless routes served by DHCP are created incorrectly

2023-07-04 Thread Launchpad Bug Tracker

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

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

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

Title:
  networkd: classless routes served by DHCP are created incorrectly

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  After upgrading 20.04 systems to 22.04, the classless routes served
  via DHCP are not being registered correctly - they are missing the
  gateway address.

  Expected routes - these are taken from a 20.04 system on the same
  network:

  $ ip route
  default via 10.10.1.1 dev enp24s0 proto dhcp src 10.10.64.12 metric 100
  10.0.0.0/8 dev enp24s0 proto kernel scope link src 10.10.64.12
  10.88.88.0/24 via 10.10.1.2 dev enp24s0 proto dhcp src 10.10.64.12 metric 100
  10.96.0.0/11 via 10.10.1.2 dev enp24s0 proto dhcp src 10.10.64.12 metric 100

  Actual routes - these are the routes created in one of the affected
  22.04 systems:

  $ ip route
  default via 10.10.1.1 dev bond0 proto dhcp src 10.10.48.20 metric 100
  8.8.8.8 via 10.10.1.1 dev bond0 proto dhcp src 10.10.48.20 metric 100
  10.0.0.0/8 dev bond0 proto kernel scope link src 10.10.48.20 metric 100
  10.10.1.1 dev bond0 proto dhcp scope link src 10.10.48.20 metric 100
  10.10.1.2 dev bond0 proto dhcp scope link src 10.10.48.20 metric 100
  10.88.88.0/24 dev bond0 proto dhcp scope link src 10.10.48.20 metric 100
  10.96.0.0/11 dev bond0 proto dhcp scope link src 10.10.48.20 metric 100

  Note the routes for 10.88.88.0/24 and 10.96.0.0/11 are missing the "via" 
gateway address, and therefore don't work.
  (For some reason there are also static routes created for DNS server 
(8.8.8.8) and known gateways (10.10.1.1 and 10.10.1.2). These are redundant but 
harmless.)

  Both the working and non-working systems are being managed by netplan.
  The non-working system has a bonded interface but I have checked that
  is not the cause of the problem - using a physical interface directly
  has the same result.

  I have attached the files /etc/netplan/00-installer-config.yaml and
  /run/systemd/network/10-netplan-bond0.network of the affected system.

  Affected system:
  Ubuntu version: Ubuntu 22.04.2 LTS
  systemd version: 249.11-0ubuntu3.6

  Older system not affected:
  Ubuntu version: Ubuntu 20.04.5 LTS
  systemd version: 245.4-4ubuntu3.19

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2009743/+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 2025743] [NEW] "X11 connection broke with certain web browsers + window managers"

2023-07-04 Thread Tyler Johnson

Public bug reported:

I have two browsers that I normally love: Pale Moon and Basilisk.
Unfortunately, both trigger a bug in Xorg, where the server just
crashes, and returns me to the login screen. The problem does not affect
the XFCE4 desktop environment, but it does affect Cinnamon. I have a
first-gen Intel Core i5 mobile processor, and while I'm running Linux
Mint 21, I believe the problem affects Ubuntu 22.04.

For more info, please see the bug reports I filed for Mint, from the
following URLs:

https://github.com/linuxmint/mint21-beta/issues/148
https://github.com/linuxmint/cinnamon/issues/10972

Please note, I just recently tested a daily build of Ubuntu 23.10 with
Gnome, and had the same issue. Debian 12 also has the same problem,
although I have not filed a bug report there.

How to reproduce: use either of the previously-mentioned web browsers,
and open literally any webpage, except those build in to the browser.
(Eg, this very page will crash X, but "about:" pages won't.) X will
crash within seconds.

I will attach the output of "inxi -Fxxxrz" below (as "info.txt").

PS: IDK if "mesa" is the right package for this bug report. Perhaps it
should be an Xorg package?

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

** Attachment added: "output of "inxi -Fxxxrz""
   https://bugs.launchpad.net/bugs/2025743/+attachment/5683808/+files/info.txt

** Description changed:

  I have two browsers that I normally love: Pale Moon and Basilisk.
  Unfortunately, both trigger a bug in Xorg, where the server just
  crashes, and returns me to the login screen. The problem does not affect
  the XFCE4 desktop environment, but it does affect Cinnamon. I have a
  first-gen Intel Core i5 mobile processor, and while I'm running Linux
  Mint 21, I believe the problem affects Ubuntu 22.04.
  
  For more info, please see the bug reports I filed for Mint, from the
  following URLs:
  
  https://github.com/linuxmint/mint21-beta/issues/148
  https://github.com/linuxmint/cinnamon/issues/10972
  
  Please note, I just recently tested a daily build of Ubuntu 23.10 with
  Gnome, and had the same issue. Debian 12 also has the same problem,
  although I have not filed a bug report there.
  
  How to reproduce: use either of the previously-mentioned web browsers,
  and open literally any webpage, except those build in to the browser.
  (Eg, this very page will crash X, but "about:" pages won't.) X will
  crash within seconds.
  
  I will attach the output of "inxi -Fxxxrz", as "info.txt"
+ 
+ PS: IDK if "mesa" is the right package for this bug report. Perhaps it
+ should be an Xorg package?

** Description changed:

  I have two browsers that I normally love: Pale Moon and Basilisk.
  Unfortunately, both trigger a bug in Xorg, where the server just
  crashes, and returns me to the login screen. The problem does not affect
  the XFCE4 desktop environment, but it does affect Cinnamon. I have a
  first-gen Intel Core i5 mobile processor, and while I'm running Linux
  Mint 21, I believe the problem affects Ubuntu 22.04.
  
  For more info, please see the bug reports I filed for Mint, from the
  following URLs:
  
  https://github.com/linuxmint/mint21-beta/issues/148
  https://github.com/linuxmint/cinnamon/issues/10972
  
  Please note, I just recently tested a daily build of Ubuntu 23.10 with
  Gnome, and had the same issue. Debian 12 also has the same problem,
  although I have not filed a bug report there.
  
  How to reproduce: use either of the previously-mentioned web browsers,
  and open literally any webpage, except those build in to the browser.
  (Eg, this very page will crash X, but "about:" pages won't.) X will
  crash within seconds.
  
- I will attach the output of "inxi -Fxxxrz", as "info.txt"
+ I will attach the output of "inxi -Fxxxrz" below.
  
  PS: IDK if "mesa" is the right package for this bug report. Perhaps it
  should be an Xorg package?

** Description changed:

  I have two browsers that I normally love: Pale Moon and Basilisk.
  Unfortunately, both trigger a bug in Xorg, where the server just
  crashes, and returns me to the login screen. The problem does not affect
  the XFCE4 desktop environment, but it does affect Cinnamon. I have a
  first-gen Intel Core i5 mobile processor, and while I'm running Linux
  Mint 21, I believe the problem affects Ubuntu 22.04.
  
  For more info, please see the bug reports I filed for Mint, from the
  following URLs:
  
  https://github.com/linuxmint/mint21-beta/issues/148
  https://github.com/linuxmint/cinnamon/issues/10972
  
  Please note, I just recently tested a daily build of Ubuntu 23.10 with
  Gnome, and had the same issue. Debian 12 also has the same problem,
  although I have not filed a bug report there.
  
  How to reproduce: use either of the previously-mentioned web browsers,
  and open literally any webpage, except those build in to the browser.
  (Eg, this very page will crash X, but "about:" pages won't.) X will
  crash within seconds.

[Touch-packages] [Bug 2025599] Re: BlueZ release 5.68

2023-07-04 Thread Daniel van Vugt

** Changed in: bluez (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  BlueZ release 5.68

Status in bluez package in Ubuntu:
  In Progress

Bug description:
  BlueZ release 5.68 is now available:

  https://mirrors.edge.kernel.org/pub/linux/bluetooth/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2025599/+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 2025666] Re: Please merge 1.225-1 into mantic

2023-07-04 Thread Danilo Egea Gondolfo

** Merge proposal linked:
   
https://code.launchpad.net/~danilogondolfo/ubuntu/+source/netcat-openbsd/+git/netcat-openbsd/+merge/445940

** Description changed:

- [placeholder]
+ PPA https://launchpad.net/~danilogondolfo/+archive/ubuntu/netcat-openbsd
+ 
+ Autopkgtest https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-
+ danilogondolfo-netcat-openbsd/mantic/amd64/n/netcat-
+ openbsd/20230703_202110_fccf3@/log.gz

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

Title:
  Please merge 1.225-1 into mantic

Status in netcat-openbsd package in Ubuntu:
  New

Bug description:
  PPA https://launchpad.net/~danilogondolfo/+archive/ubuntu/netcat-
  openbsd

  Autopkgtest https://autopkgtest.ubuntu.com/results/autopkgtest-mantic-
  danilogondolfo-netcat-openbsd/mantic/amd64/n/netcat-
  openbsd/20230703_202110_fccf3@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netcat-openbsd/+bug/2025666/+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 1985057] Re: Camera output freeze when using pipewiresrc

2023-07-04 Thread Kai-Chuan Hsieh

@seb128

Do we have other alternative camera app for ubuntu desktop if we'd like
to deprecate cheese?

Thanks,

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

Title:
  Camera output freeze when using pipewiresrc

Status in OEM Priority Project:
  New
Status in gst-plugins-base1.0 package in Ubuntu:
  New
Status in gstreamer1.0 package in Ubuntu:
  New
Status in pipewire package in Ubuntu:
  Fix Released
Status in gst-plugins-base1.0 source package in Jammy:
  Incomplete
Status in gstreamer1.0 source package in Jammy:
  Incomplete
Status in pipewire source package in Jammy:
  Incomplete

Bug description:
  [Impact]
  On Dell platform with Microdia Integrated webcam, the Cheese preview is stuck 
on jammy. The gst-launch-1.0 command suggested by gst-device-monitor-1.0 can 
reproduce it too.

  [Test Plan]
  1. Install Jammy on the hardware issue reported, and hardware didn't report 
the issue to avoid the regression
     hardware list:
     a. 0bda:58ff Realtek Semiconductor Corp. Integrated_Webcam_HD
     b. 0c45:6747 Microdia Integrated_Webcam_HD
     c. 0c45:6a14 Microdia Integrated_Webcam_HD
     d. 1bcf:28d0 Sunplus Innovation Technology Inc. Integrated_Webcam_5M
     e. 04f2:b76b Chicony Electronics Co., Ltd HP HD Camera
     f. 0408:545a Quanta Computer, Inc. HP 5MP Camera
     g. 0408:5483 Quanta Computer, Inc. HP HD Camera
     h. 174f:2459 Syntek Integrated Camera (ThinkBook 14 Gen 4)
     i. 5986:116d Acer, Inc Integrated Camera (ThinkCentre Neo 50a)
     j. 0bda:5556 Realtek Semiconductor Corp. Integrated_Webcam_FHD
  2. try to install the updated pipewire packages (= 0.3.48-1ubuntu2)
  3. $ sudo reboot
  4. Check if gst-launch-1.0 work
     a. $ gst-device-monitor-1.0 Video/Source to get caps and suggest 
gst-launch-1.0 command
     b. $ gst-launch-1.0 pipewiresrc path= !  ! decodebin ! 
videoconvert ! glimagesink
     c. Check if the result ok
  5. Check the screencast function by pressing 'prt sc'
     a. the screenshot of all screen/selected region should work good
     b. the screenrecord of all screen/selected region should work good
  6. Check that video recording in gnome-shell works
     - use Ctrl+Shift+Alt+R to start a recording, stop it from the indicator, 
verify that there is a new entry in ~/Video
  7. Check that screen sharing is working
     - go to settings, screen sharing and enable the feature
     - try to connect using rdp/vnc from another client

  do those steps under wayland and unset X

  [Where problems could occur]
  The patches try to dequeue the shared buffer, instead of pool buffer to 
prevent the pool buffer being corrupted. it might cause some camera preview 
failed if shared buffer is corrupted.
  It is in upstream from 0.3.52 to 0.3.56, and there is no regression found,
  so the risk is low.

  [Other Info]
  Upstream commits:
  
https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/7cc509b117a6db66c395fb56ac4f17fb8cbd0c92
  
https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/a1f33a99df5756c3dedd68f5ba2690819098d14f

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1985057/+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 1996652] Re: Nautilus search is slow and jumbles keyboard input on 22.10

2023-07-04 Thread Gunnar Hjalmarsson

My first upload to the PPA proved to not be complete. Corrected now.
(Wait for the builds to finish and the packages to be published before
updating).

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

Title:
  Nautilus search is slow and jumbles keyboard input on 22.10

Status in ibus:
  New
Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  Since my upgrade to 22.10, I've found the search box in Nautilus
  (files) essentially unusable.  It is notably sluggish to launch and
  browse in general.  But most detrimental to the usability is this:

  The characters do not appear in real time as I type. When they do
  appear, they are sometimes jumbled or in reverse (consistently
  reproducible).  As I type in the file search box, the circular cursor
  spins intermittently, then the UI catches up and it's not what I
  typed.

  For example, I just typed "umbrella" into the search box, and Nautilus 
searched for:
  "umballer"

  Off-the-cuff test #2, searched for "Ubuntu" and I ended up with
  "Ubunut" ... you can't make this up. :-)

  Test #3, typed Launchpad, ended up with a search for "Laudaphcn".

  Keyboard input everywhere else on the system is otherwise normal and
  snappy.  No pun intended, really.

  FWIW Nautilus files preferences are as default (Search in subfolders,
  Show thumbnails, File count == This computer only).

  

  $ apt-cache policy nautilus
  nautilus:
Installed: 1:43.0-1ubuntu1
Candidate: 1:43.0-1ubuntu1
Version table:
   *** 1:43.0-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu kinetic/main amd64 Packages
  100 /var/lib/dpkg/status

  $ uname -r
  5.19.0-23-generic

  $ lsb_release -rd
  Description:Ubuntu 22.10
  Release:22.10

  $ snap list
  Name   Version   RevTracking 
Publisher  Notes
  bare   1.0   5  latest/stable
canonical✓ base
  core   16-2.57.2 13886  latest/stable
canonical✓ core
  core18 20221027  2620   latest/stable
canonical✓ base
  core20 20221027  1695   latest/stable
canonical✓ base
  gnome-3-34-18040+git.3556cb3 77 latest/stable/…  
canonical✓ -
  gnome-3-38-20040+git.6f39565 119latest/stable
canonical✓ -
  google-cloud-sdk   409.0.0   298latest/stable
google-cloud-sdk✓  classic
  gtk-common-themes  0.1-81-g442e511   1535   latest/stable/…  
canonical✓ -
  snap-store 41.3-64-g512c0ff  599latest/stable/…  
canonical✓ -
  snapd  2.57.417336  latest/stable
canonical✓ snapd
  snapd-desktop-integration  0.1   14 latest/stable/…  
canonical✓ -

  
  Side question:  Since this system has transitioned across several upgrades 
from 20.04 to 22.10, do I really need all of these core* and gnome* snaps?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ibus/+bug/1996652/+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 1852911] Re: CriticalPowerAction=Suspend should be supported

[Touch-packages] [Bug 1623173] Re: [Asus ZenBook UX501VW] Function key to toggle the screen doesn't work

[Touch-packages] [Bug 1666088] Re: In my notebook Samsung Q330 excess VGA-1 display

[Touch-packages] [Bug 1685772] Re: Too high CPU frequency

[Touch-packages] [Bug 2025666] Re: Please merge 1.225-1 into mantic

[Touch-packages] [Bug 2025525] Re: package libperl5.34:amd64 5.34.0-3ubuntu1.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting config

[Touch-packages] [Bug 2025315] Re: package linux-image-5.15.0-76-generic 5.15.0-76.83 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Touch-packages] [Bug 2025525] Re: package libperl5.34:amd64 5.34.0-3ubuntu1.2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting config

[Touch-packages] [Bug 1991606] Autopkgtest regression report (dput/1.1.2ubuntu2.1)

[Touch-packages] [Bug 1991606] Autopkgtest regression report (dput/1.1.3ubuntu2.1)

[Touch-packages] [Bug 1991606] Autopkgtest regression report (dput/1.1.0ubuntu2.1)

[Touch-packages] [Bug 2025526] Re: Printer is not available in chromium snap

[Touch-packages] [Bug 2024164] Re: Replace dhclient with dhcpcd

[Touch-packages] [Bug 2011385] Re: [950XED, Realtek ALC298, Speaker, Internal] No sound at all

[Touch-packages] [Bug 2025363] Re: Merge console-setup 1.222 into mantic

[Touch-packages] [Bug 2025363] Re: Merge console-setup 1.222 into mantic

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

[Touch-packages] [Bug 2009743] Re: networkd: classless routes served by DHCP are created incorrectly

[Touch-packages] [Bug 1949615] Re: Notify method not working correctly in 21.10 (impish)

[Touch-packages] [Bug 2009743] Re: networkd: classless routes served by DHCP are created incorrectly

[Touch-packages] [Bug 2009743] Re: networkd: classless routes served by DHCP are created incorrectly

[Touch-packages] [Bug 2025743] [NEW] "X11 connection broke with certain web browsers + window managers"

[Touch-packages] [Bug 2025599] Re: BlueZ release 5.68

[Touch-packages] [Bug 2025666] Re: Please merge 1.225-1 into mantic

[Touch-packages] [Bug 1985057] Re: Camera output freeze when using pipewiresrc

[Touch-packages] [Bug 1996652] Re: Nautilus search is slow and jumbles keyboard input on 22.10

26 matches

Site Navigation

Mail list logo

Footer information