[Touch-packages] [Bug 2049552] Re: [noble] ftbfs with new zlib 1.3

2024-01-20 Thread Colin Watson 
You could probably just merge current Debian openssh rather than trying
to fix all these problems independently?

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

Title:
  [noble] ftbfs with new zlib 1.3

Status in openssh package in Ubuntu:
  In Progress

Bug description:
  The zlib detection code seems faulty:

  checking for possibly buggy zlib... yes
  configure: error: *** zlib too old - check config.log ***
  Your reported zlib version has known security problems.  It's possible your
  vendor has fixed these problems without changing the version number.  If you
  are sure this is the case, you can disable the check by running
  "./configure --without-zlib-version-check".
  If you are in doubt, upgrade zlib to version 1.2.3 or greater.
  See http://www.gzip.org/zlib/ for details.

  | #include 
  | #include 
  | #include 
  |
  | int
  | main (void)
  | {
  |
  |   int a=0, b=0, c=0, d=0, n, v;
  |   n = sscanf(ZLIB_VERSION, "%d.%d.%d.%d", , , , );
  |   if (n != 3 && n != 4)
  |   exit(1);
  |   v = a*100 + b*1 + c*100 + d;
  |   fprintf(stderr, "found zlib version %s (%d)\n", ZLIB_VERSION, v);
  |
  |   /* 1.1.4 is OK */
  |   if (a == 1 && b == 1 && c >= 4)
  |   exit(0);
  |
  |   /* 1.2.3 and up are OK */
  |   if (v >= 1020300)
  |   exit(0);
  |
  |   exit(2);
  |
  |   ;
  |   return 0;
  | }

  Upstream bug report: https://bugzilla.mindrot.org/show_bug.cgi?id=3604

  Upstream fix (untested): https://github.com/openssh/openssh-
  portable/commit/cb4ed12ffc332d1f72d054ed92655b5f1c38f621

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2049552/+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 2047450] Re: tail emits no output for sysfs files when using large page kernels

2024-01-20 Thread dann frazier 
= jammy verification =
ubuntu@hinyari:~$ getconf PAGESIZE
65536
ubuntu@hinyari:~$ tail /sys/kernel/profiling 
ubuntu@hinyari:~$ sudo apt install coreutils -t jammy-proposed
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be upgraded:
  coreutils
1 upgraded, 0 newly installed, 0 to remove and 42 not upgraded.
Need to get 1397 kB of archives.
After this operation, 8192 B of additional disk space will be used.
Get:1 http://ports.ubuntu.com/ubuntu-ports jammy-proposed/main arm64 coreutils 
arm64 8.32-4.1ubuntu1.1 [1397 kB]
Fetched 1397 kB in 1s (2153 kB/s)
(Reading database ... 83707 files and directories currently installed.)
Preparing to unpack .../coreutils_8.32-4.1ubuntu1.1_arm64.deb ...
Unpacking coreutils (8.32-4.1ubuntu1.1) over (8.32-4.1ubuntu1) ...
Setting up coreutils (8.32-4.1ubuntu1.1) ...
Processing triggers for install-info (6.8-4build1) ...
Processing triggers for man-db (2.10.2-1) ...
Scanning processes...   
   
Scanning candidates...  
   
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.
ubuntu@hinyari:~$ tail /sys/kernel/profiling 
0


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

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

Title:
  tail emits no output for sysfs files when using large page kernels

Status in coreutils package in Ubuntu:
  Fix Released
Status in coreutils source package in Jammy:
  Fix Committed
Status in coreutils source package in Lunar:
  Won't Fix
Status in coreutils source package in Mantic:
  Fix Committed
Status in coreutils source package in Noble:
  Fix Released

Bug description:
  [Impact]
  Ubuntu provides 64K page size kernels for ppc64el (always) and arm64 
(optional -64k flavors). When booted on 64K kernels, tail emits no output when 
tailing a sysfs file. The difference in behavior can be a source for bugs in 
scripts that use tail, and general user confusion.

  [Test Plan]
  The upstream fix includes a test case that tails the /sys/kernel/profiling 
file, if it exists. That case would fail with an unfixed coreutils package as 
shown below:

  = When booted on a 4K kernel =
  ubuntu@gunyolk:~$ tail /sys/kernel/profiling 
  0

  = When booted on a 64K kernel =
  ubuntu@gunyolk:~$ tail /sys/kernel/profiling 
  ubuntu@gunyolk:~$ 

  Since the upstream test cases are executed at build time, the existing
  tests and this new test will be used  to regression test behavior.
  This should cover both 4K (!ppc64el) and 64K (ppc64el) cases. We
  should also do a manual verification on arm64 w/ the 64K kernel since
  that case is not covered by our builders.

  [Where Problems Could Occur]
  The biggest risk for a regression I see is due to the side-effect of the fix 
now allocating a dynamic buffer instead of the stack. An error in logic there 
could cause a crash or a memory leak in scenarios undetected during testing. I 
used valgrind when developing the fix to derisk the memory leak scenario.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/2047450/+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 2033422] Re: openssl: backport to jammy "clear method store / query cache confusion"

2024-01-20 Thread Simon Déziel 
Using a fast HTTPS server (same LAN as client), the `main.py` tests goes
from ~8s to ~2.5s:

# time python3 /tmp/main.py 
Distro: Ubuntu 22.04.3 LTS
Python Version: 3.10.12 (main, Nov 20 2023, 15:14:05) [GCC 11.4.0]
OpenSSL Version: OpenSSL 3.0.2 15 Mar 2022
0 1 2 3 ... 99 
real0m8.163s
user0m16.041s
sys 0m3.474s


# apt-get install -t jammy-proposed libssl3
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be upgraded:
  libssl3
1 upgraded, 0 newly installed, 0 to remove and 38 not upgraded.
Need to get 1,902 kB of archives.
After this operation, 1,024 B of additional disk space will be used.

# time python3 /tmp/main.py 
Distro: Ubuntu 22.04.3 LTS
Python Version: 3.10.12 (main, Nov 20 2023, 15:14:05) [GCC 11.4.0]
OpenSSL Version: OpenSSL 3.0.2 15 Mar 2022
0 1 2 3 ... 99 
real0m2.533s
user0m9.188s
sys 0m0.096s

Upgrading the server side (NGINX) didn't make a measurable difference.

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

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

Title:
  openssl: backport to jammy "clear method store / query cache
  confusion"

Status in openssl package in Ubuntu:
  New
Status in openssl source package in Jammy:
  Fix Committed
Status in openssl source package in Lunar:
  Fix Released

Bug description:
  === SRU information ===
  [ATTENTION]
  This SRU contains THREE changes which are listed in the section below.

  [Meta]
  This bug is part of a series of three bugs for a single SRU.
  This ( #2033422 ) is the "central" bug with the global information and 
debdiff.

  This SRU addresses three issues with Jammy's openssl version:
  - http://pad.lv/1994165: ignored SMIME signature errors
  - http://pad.lv/2023545: imbca engine dumps core
  - http://pad.lv/2033422: very high CPU usage for concurrent TLS connections 
(this one)

  The SRU information has been added to the three bug reports and I am
  attaching the debdiff here only for all three.

  All the patches have been included in subsequent openssl 3.0.x
  releases which in turn have been included in subsequent Ubuntu
  releases. There has been no report of issues when updating to these
  Ubuntu releases.

  I have rebuilt the openssl versions and used abi-compliance-checker to
  compare the ABIs of the libraries in jammy and the one for the SRU.
  Both matched completely (FYI, mantic's matched completely too).

  I have also pushed the code to git (without any attempt to make it
  git-ubuntu friendly).

  
https://code.launchpad.net/~adrien-n/ubuntu/+source/openssl/+git/openssl/+ref/jammy-
  sru

  I asked Brian Murray about phasing speed and he concurs a slow roll-out is 
probably better for openssl. There is a small uncertainty because a security 
update could come before the phasing is over, effectively fast-forwarding the 
SRU. Still, unless there is already a current pre-advisory, this is probably 
better than a 10% phasing which is over after only a couple days anyway.
  NB: at the moment openssl doesn't phase slowly so this needs to be 
implemented.

  [Impact]
  Severely degraded performance for concurrent operations compared to openssl 
1.1. The performance is so degraded that some workloads fail due to timeouts or 
insufficient resources (noone magically has 5 times more machines). As a 
consequence, a number of people use openssl 1.1 instead and do not get security 
updates.

  [Test plan]
  Rafael Lopez has shared a simple benchmarks in http://pad.lv/2009544 with 
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2009544/+attachment/5690224/+files/main.py
 .

  To test, follow these steps:
  - run "time python3 main.py" # using the aforementioned main.py script
  - apt install -t jammy-proposed libssl3
  - run "time python3 main.py"
  - compare the runtimes for the two main.py runs

  You can run this on x86_64, Raspberry Pi 4 or any machine, and get a
  very large speed-up in all cases. The improvements are not
  architecture-dependant.

  Using this changeset, I get the following numbers for ten runs on my
  laptop:

  3.0.2:
  real  2m5.567s
  user  4m3.948s
  sys   2m0.233s

  this SRU:
  real  0m23.966s
  user  2m35.687s
  sys   0m1.920s

  As can be easily seen, the speed-up is massive: system time is divided
  by 60 and overall wall clock time is roughly five times lower.

  In http://pad.lv/2009544 , Rafael also shared his performance numbers
  and they are relatable to these. He used slightly different versions
  (upstreams rather than patched with cherry-picks) but at least one of
  the version used does not include other performance change. He also
  used different hardware and this performance issue seems to depend on
  the number of CPUs available but also obtained a

[Touch-packages] [Bug 2047450] Re: tail emits no output for sysfs files when using large page kernels

2024-01-20 Thread dann frazier 
= mantic verification =
ubuntu@hinyari:~$ getconf PAGESIZE
65536
ubuntu@hinyari:~$ tail /sys/kernel/profiling 
0
ubuntu@hinyari:~$ dpkg -l | grep coreutils
ii  coreutils9.1-1ubuntu2.23.10.1   
 arm64GNU core utilities


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

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

Title:
  tail emits no output for sysfs files when using large page kernels

Status in coreutils package in Ubuntu:
  Fix Released
Status in coreutils source package in Jammy:
  Fix Committed
Status in coreutils source package in Lunar:
  Won't Fix
Status in coreutils source package in Mantic:
  Fix Committed
Status in coreutils source package in Noble:
  Fix Released

Bug description:
  [Impact]
  Ubuntu provides 64K page size kernels for ppc64el (always) and arm64 
(optional -64k flavors). When booted on 64K kernels, tail emits no output when 
tailing a sysfs file. The difference in behavior can be a source for bugs in 
scripts that use tail, and general user confusion.

  [Test Plan]
  The upstream fix includes a test case that tails the /sys/kernel/profiling 
file, if it exists. That case would fail with an unfixed coreutils package as 
shown below:

  = When booted on a 4K kernel =
  ubuntu@gunyolk:~$ tail /sys/kernel/profiling 
  0

  = When booted on a 64K kernel =
  ubuntu@gunyolk:~$ tail /sys/kernel/profiling 
  ubuntu@gunyolk:~$ 

  Since the upstream test cases are executed at build time, the existing
  tests and this new test will be used  to regression test behavior.
  This should cover both 4K (!ppc64el) and 64K (ppc64el) cases. We
  should also do a manual verification on arm64 w/ the 64K kernel since
  that case is not covered by our builders.

  [Where Problems Could Occur]
  The biggest risk for a regression I see is due to the side-effect of the fix 
now allocating a dynamic buffer instead of the stack. An error in logic there 
could cause a crash or a memory leak in scenarios undetected during testing. I 
used valgrind when developing the fix to derisk the memory leak scenario.

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


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

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

2024-01-20 Thread Bug Watch Updater 
** Changed in: sphinx-autoapi (Debian)
   Status: Unknown => Fix Released

** Changed in: cython (Debian)
   Status: Unknown => New

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

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

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

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

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

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


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

[Touch-packages] [Bug 2040017] Re: package libasound2-plugins 1.2.7.1-1ubuntu2 failed to install/upgrade: trying to overwrite shared '/etc/alsa/conf.d/99-pulseaudio-default.conf.example', which is dif

2024-01-20 Thread bastubis 
I got the same error and the package had failed to install on doing a
dist-upgrade from 23.04 to 23.10. I installed it manually without
errors.

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

Title:
  package libasound2-plugins 1.2.7.1-1ubuntu2 failed to install/upgrade:
  trying to overwrite shared '/etc/alsa/conf.d/99-pulseaudio-
  default.conf.example', which is different from other instances of
  package libasound2-plugins:i386

Status in alsa-plugins package in Ubuntu:
  Confirmed

Bug description:
  I dont know much about

  ProblemType: Package
  DistroRelease: Ubuntu 23.10
  Package: libasound2-plugins 1.2.7.1-1ubuntu2
  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
  CasperMD5CheckResult: pass
  Date: Sat Oct 21 02:05:11 2023
  DuplicateSignature:
   package:libasound2-plugins:1.2.7.1-1ubuntu2
   Unpacking libasound2-plugins:i386 (1.2.7.1-1ubuntu2) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-KQ6wMx/50-libasound2-plugins_1.2.7.1-1ubuntu2_i386.deb 
(--unpack):
trying to overwrite shared 
'/etc/alsa/conf.d/99-pulseaudio-default.conf.example', which is different from 
other instances of package libasound2-plugins:i386
  ErrorMessage: trying to overwrite shared 
'/etc/alsa/conf.d/99-pulseaudio-default.conf.example', which is different from 
other instances of package libasound2-plugins:i386
  InstallationDate: Installed on 2022-12-23 (301 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.22.0ubuntu1
   apt  2.7.3
  SourcePackage: alsa-plugins
  Title: package libasound2-plugins 1.2.7.1-1ubuntu2 failed to install/upgrade: 
trying to overwrite shared 
'/etc/alsa/conf.d/99-pulseaudio-default.conf.example', which is different from 
other instances of package libasound2-plugins:i386
  UpgradeStatus: Upgraded to mantic on 2023-10-20 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-plugins/+bug/2040017/+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 2019856] Re: Add missing ARM-cores to support Grace-based systems

2024-01-20 Thread Jamie Nguyen 
Verified on 22.04 using util-linux=2.37.2-4ubuntu3.2

$ apt policy util-linux
util-linux:
  Installed: 2.37.2-4ubuntu3.2
  Candidate: 2.37.2-4ubuntu3.2
  Version table:
 *** 2.37.2-4ubuntu3.2 500
500 http://ports.ubuntu.com/ubuntu-ports jammy-proposed/main arm64 
Packages
100 /var/lib/dpkg/status
 2.37.2-4ubuntu3 500
500 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages
$ lscpu | head -n10
Architecture:   aarch64
CPU op-mode(s): 64-bit
Byte Order: Little Endian
CPU(s): 288
On-line CPU(s) list:0-287
Vendor ID:  ARM
Model name: Neoverse-V2
Model:  0
Thread(s) per core: 1
Core(s) per socket: 72

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

Title:
  Add missing ARM-cores to support Grace-based systems

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Jammy:
  Fix Committed
Status in util-linux source package in Kinetic:
  Won't Fix
Status in util-linux source package in Lunar:
  Won't Fix
Status in util-linux source package in Mantic:
  Fix Released

Bug description:
  [Impact]

  When running "lscpu" on a Grace-based system + Ubuntu 22.04, it
  doesn't report a model name:

  Vendor ID: ARM
  Model: 0

  [Fix]

  Adding the additional arm_part to sys-utils/lscpu-arm.c solves the
  problem. The commit below adds the specific codes missing from Jammy's
  version.

  https://github.com/util-linux/util-
  linux/commit/6857cccbb4157d5da34ca98f77a0ac9d68e1e740

  [Test Steps]

  * Verify whether output of lscpu is correct on new CPUs; eg:
  Vendor ID: ARM
  Model name: Neoverse-V2

  * Verify whether output of lscpu doesn't change on old CPUs; eg:
  Vendor ID: ARM
  Model name: Neoverse-N1

  [What Could Go Wrong]

  The fix only introduces additional model identifiers to match
  against and print a model name string, thus regression impact
  should be contained within lscpu and printing cpus model name
  on ARM systems. 

  Output doesn't change on systems with non-affected CPU models.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/2019856/+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 2049972] Re: Can't change screen brightness

2024-01-20 Thread Ubuntu Foundations Team Bug Bot 
** Package changed: ubuntu => xorg (Ubuntu)

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

Title:
  Can't change screen brightness

Status in xorg package in Ubuntu:
  New

Bug description:
  HP Victus with Radeon 6500 graphics, Ubuntu 22.04.3. When pressing
  functions key, a brightness popup appears, but the brightness is still
  maximum. I tried to update GRUB with adding "acpi_osi=Linux
  acpi_backlight=vendor" but after that even the popup doesn't show by
  pressing functions key, nothing really happens.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jan 20 13:35:33 2024
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Subsystem: Hewlett-Packard Company Device [103c:8a3f]
   Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c6) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Cezanne [103c:8a3f]
  InstallationDate: Installed on 2024-01-20 (0 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: HP Victus by HP Gaming Laptop 15-fb0xxx
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic 
root=UUID=82abbfb4-55a4-49f1-aaf8-f00a4d56e35f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/11/2023
  dmi.bios.release: 15.18
  dmi.bios.vendor: AMI
  dmi.bios.version: F.18
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 8A3F
  dmi.board.vendor: HP
  dmi.board.version: 35.44
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 35.44
  dmi.modalias: 
dmi:bvnAMI:bvrF.18:bd08/11/2023:br15.18:efr35.44:svnHP:pnVictusbyHPGamingLaptop15-fb0xxx:pvr:rvnHP:rn8A3F:rvr35.44:cvnHP:ct10:cvrChassisVersion:sku9Q377EA#AKD:
  dmi.product.family: 103C_5335M7 HP VICTUS
  dmi.product.name: Victus by HP Gaming Laptop 15-fb0xxx
  dmi.product.sku: 9Q377EA#AKD
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2049972/+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 2049972] [NEW] Can't change screen brightness

2024-01-20 Thread Launchpad Bug Tracker 
You have been subscribed to a public bug:

HP Victus with Radeon 6500 graphics, Ubuntu 22.04.3. When pressing
functions key, a brightness popup appears, but the brightness is still
maximum. I tried to update GRUB with adding "acpi_osi=Linux
acpi_backlight=vendor" but after that even the popup doesn't show by
pressing functions key, nothing really happens.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-14.14~22.04.1-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Jan 20 13:35:33 2024
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Subsystem: Hewlett-Packard Company Device [103c:8a3f]
 Advanced Micro Devices, Inc. [AMD/ATI] Cezanne [1002:1638] (rev c6) (prog-if 
00 [VGA controller])
   Subsystem: Hewlett-Packard Company Cezanne [103c:8a3f]
InstallationDate: Installed on 2024-01-20 (0 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
MachineType: HP Victus by HP Gaming Laptop 15-fb0xxx
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=pl_PL.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-14-generic 
root=UUID=82abbfb4-55a4-49f1-aaf8-f00a4d56e35f ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/11/2023
dmi.bios.release: 15.18
dmi.bios.vendor: AMI
dmi.bios.version: F.18
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 8A3F
dmi.board.vendor: HP
dmi.board.version: 35.44
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 35.44
dmi.modalias: 
dmi:bvnAMI:bvrF.18:bd08/11/2023:br15.18:efr35.44:svnHP:pnVictusbyHPGamingLaptop15-fb0xxx:pvr:rvnHP:rn8A3F:rvr35.44:cvnHP:ct10:cvrChassisVersion:sku9Q377EA#AKD:
dmi.product.family: 103C_5335M7 HP VICTUS
dmi.product.name: Victus by HP Gaming Laptop 15-fb0xxx
dmi.product.sku: 9Q377EA#AKD
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug jammy ubuntu wayland-session
-- 
Can't change screen brightness
https://bugs.launchpad.net/bugs/2049972
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg in Ubuntu.

-- 
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 2049977] [NEW] journalctl --follow --grep lists lines in wrong order

2024-01-20 Thread Dominic 
Public bug reported:

Version: systemd 253 (253.5-1ubuntu6.1) (23.10 mantic)

When executing:

journalctl --follow --grep="session closed"

the lines are printed from newest to oldest. This essentially makes
--follow useless since it is tail-ing in the wrong direction.

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

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

Title:
  journalctl --follow --grep lists lines in wrong order

Status in systemd package in Ubuntu:
  New

Bug description:
  Version: systemd 253 (253.5-1ubuntu6.1) (23.10 mantic)

  When executing:

  journalctl --follow --grep="session closed"

  the lines are printed from newest to oldest. This essentially makes
  --follow useless since it is tail-ing in the wrong direction.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2049977/+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 2049976] [NEW] multiscreen one display goes black on resume

2024-01-20 Thread James Cobban 
Public bug reported:

Starting a few weeks ago after applying regular maintenance to 22.04.3
LTS one of my two displays, an LG 22MP47HQ-P connected to my tower by a
D-Sub cable, blinked multiple times immediately on resume from suspend.
My second display which is connected using HDMI works normally. This, of
course, was merely a mild annoyance because after a few seconds it
stopped. However in the past week that same display flashes on, and then
goes black. I power the display off and back on and again it flashes on
for a fraction of a second and then goes black. After several power
cycles of the display it stays on, so again this is only a mild
annoyance. Is this a known issue with a recent update?

Specifically this is after a deep suspend, one where on unlock you need
to press a key to get the login prompt.

I tried updating to 23.10 but the problem is there as well.

This bug tool does not permit reporting a problem against Wayland.

lshw -C video
*-display
description: VGA compatible controller
product: Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller
vendor: Intel Corporation
physical id: 2
bus info: pci@:00:02.0
logical name: /dev/fb0
version: 06
width: 64 bits
clock: 33MHz
capabilities: msi pm vga_controller bus_master cap_list rom fb
configuration: depth=32 driver=i915 latency=0 resolution=1920,1080
resources: irq:31 memory:f780-f7bf memory:e000-efff 
ioport:f000(size=64) memory:c-d

/var/log/apt/history.log taken immediately after encountering the issue
on 22.04

Start-Date: 2024-01-02 16:01:30
Commandline: aptdaemon role='role-commit-packages' sender=':1.7295'
Upgrade: thunderbird:amd64 (1:115.5.0+build1-0ubuntu0.22.04.1, 
1:115.6.0+build2-0ubuntu0.22.04.1), thunderbird-locale-en:amd64 
(1:115.5.0+build1-0ubuntu0.22.04.1, 1:115.6.0+build2-0ubuntu0.22.04.1), 
thunderbird-locale-en-gb:amd64 (1:115.5.0+build1-0ubuntu0.22.04.1, 
1:115.6.0+build2-0ubuntu0.22.04.1), thunderbird-locale-en-us:amd64 
(1:115.5.0+build1-0ubuntu0.22.04.1, 1:115.6.0+build2-0ubuntu0.22.04.1), 
thunderbird-gnome-support:amd64 (1:115.5.0+build1-0ubuntu0.22.04.1, 
1:115.6.0+build2-0ubuntu0.22.04.1)
End-Date: 2024-01-02 16:01:33

Start-Date: 2024-01-03 16:57:04
Commandline: /usr/bin/unattended-upgrade
Upgrade: libsqlite3-dev:amd64 (3.37.2-2ubuntu0.1, 3.37.2-2ubuntu0.3), 
libsqlite3-0:amd64 (3.37.2-2ubuntu0.1, 3.37.2-2ubuntu0.3), sqlite3:amd64 
(3.37.2-2ubuntu0.1, 3.37.2-2ubuntu0.3)
End-Date: 2024-01-03 16:57:05

Start-Date: 2024-01-03 16:57:08
Commandline: /usr/bin/unattended-upgrade
Upgrade: openssh-client:amd64 (1:8.9p1-3ubuntu0.5, 1:8.9p1-3ubuntu0.6), 
openssh-server:amd64 (1:8.9p1-3ubuntu0.5, 1:8.9p1-3ubuntu0.6), 
openssh-sftp-server:amd64 (1:8.9p1-3ubuntu0.5, 1:8.9p1-3ubuntu0.6)
End-Date: 2024-01-03 16:57:10

Start-Date: 2024-01-03 16:57:13
Commandline: /usr/bin/unattended-upgrade
Upgrade: libnode72:amd64 (12.22.9~dfsg-1ubuntu3.2, 12.22.9~dfsg-1ubuntu3.3), 
nodejs:amd64 (12.22.9~dfsg-1ubuntu3.2, 12.22.9~dfsg-1ubuntu3.3), 
libnode-dev:amd64 (12.22.9~dfsg-1ubuntu3.2, 12.22.9~dfsg-1ubuntu3.3)
End-Date: 2024-01-03 16:57:14

Start-Date: 2024-01-03 16:57:16
Commandline: /usr/bin/unattended-upgrade
Upgrade: nodejs-doc:amd64 (12.22.9~dfsg-1ubuntu3.2, 12.22.9~dfsg-1ubuntu3.3)
End-Date: 2024-01-03 16:57:17

Start-Date: 2024-01-09 20:43:19
Commandline: aptdaemon role='role-commit-packages' sender=':1.9514'
Install: php8.3-xml:amd64 (8.3.1-1+ubuntu22.04.1+deb.sury.org+1, automatic), 
php8.3-mbstring:amd64 (8.3.1-1+ubuntu22.04.1+deb.sury.org+1, automatic), 
php8.3-common:amd64 (8.3.1-1+ubuntu22.04.1+deb.sury.org+1, automatic), 
php8.3-intl:amd64 (8.3.1-1+ubuntu22.04.1+deb.sury.org+1, automatic)
Upgrade: php-common:amd64 (2:93+ubuntu22.04.1+deb.sury.org+3, 
2:94+ubuntu22.04.1+deb.sury.org+1), software-properties-common:amd64 
(0.99.22.8, 0.99.22.9), python3-software-properties:amd64 (0.99.22.8, 
0.99.22.9), php-intl:amd64 (2:8.2+93+ubuntu22.04.1+deb.sury.org+3, 
2:8.3+94+ubuntu22.04.1+deb.sury.org+1), php-mbstring:amd64 
(2:8.2+93+ubuntu22.04.1+deb.sury.org+3, 2:8.3+94+ubuntu22.04.1+deb.sury.org+1), 
software-properties-gtk:amd64 (0.99.22.8, 0.99.22.9), python3-distro-info:amd64 
(1.1ubuntu0.1, 1.1ubuntu0.2), distro-info-data:amd64 (0.52ubuntu0.5, 
0.52ubuntu0.6), linux-firmware:amd64 (20220329.git681281e4-0ubuntu3.23, 
20220329.git681281e4-0ubuntu3.24), php-xml:amd64 
(2:8.2+93+ubuntu22.04.1+deb.sury.org+3, 2:8.3+94+ubuntu22.04.1+deb.sury.org+1), 
distro-info:amd64 (1.1ubuntu0.1, 1.1ubuntu0.2)
End-Date: 2024-01-09 20:45:50

Start-Date: 2024-01-10 21:58:10
Commandline: /usr/bin/unattended-upgrade
Upgrade: libc6:amd64 (2.35-0ubuntu3.5, 2.35-0ubuntu3.6), libc6:i386 
(2.35-0ubuntu3.5, 2.35-0ubuntu3.6), libc-dev-bin:amd64 (2.35-0ubuntu3.5, 
2.35-0ubuntu3.6), libc6-dbg:amd64 (2.35-0ubuntu3.5, 2.35-0ubuntu3.6), 
libc6-dev:amd64 (2.35-0ubuntu3.5, 2.35-0ubuntu3.6)
End-Date: 2024-01-10 21:58:28

Start-Date: 2024-01-10 21:58:35
Commandline: /usr/bin/unattended-upgrade
Upgrade: libc-bin:amd64

[Touch-packages] [Bug 2047727] Re: display backlight

2024-01-20 Thread Paul White 
Moving to 'xorg' so that this bug report reaches Ubuntu's Desktop Team
Please explain in further detail 'display backlight' and  'bridness backlight'
What exactly is the problem that you are seeing while using Ubuntu?

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

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

Title:
  display backlight

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  bridness backlight

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
  Uname: Linux 6.2.0-26-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec 30 20:15:41 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:0214]
 Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:0214]
  InstallationDate: Installed on 2023-12-30 (0 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: emachines emachines D725
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-26-generic root=/dev/sda2 ro 
quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/10/2009
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.12
  dmi.board.name: HM40
  dmi.board.vendor: emachines
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.12:bd08/10/2009:svnemachines:pnemachinesD725:pvr0100:rvnemachines:rnHM40:rvrRev:cvnAcer:ct10:cvrN/A:sku:
  dmi.product.name: emachines D725
  dmi.product.version: 0100
  dmi.sys.vendor: emachines
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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

2024-01-20 Thread Benjamin Drung 
*** This bug is a duplicate of bug 798414 ***
https://bugs.launchpad.net/bugs/798414

Thank you for taking the time to report this bug and helping to make
Ubuntu better. The relevant dpkg terminal log says:

zstd: error 25 : Write error : No space left on dev

So generating the initramfs fails because your / partition is full.
Please cleanup your root partition. Feel free to continue to report any
other bugs you may find.

** This bug has been marked a duplicate of bug 798414
   update-initramfs should produce a more helpful error message when there 
isn't enough  free space--or provide an automatic tool for removal of old files

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

Title:
  package linux-image-6.5.0-14-generic 6.5.0-14.14~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:
  New

Bug description:
  i occured this when i on terminal i can't provide more details because
  i don't know much

  ProblemType: Package
  DistroRelease: Ubuntu 22.04
  Package: linux-image-6.5.0-14-generic 6.5.0-14.14~22.04.1
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Fri Jan 12 19:20:00 2024
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2023-10-28 (76 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.11
  SourcePackage: initramfs-tools
  Title: package linux-image-6.5.0-14-generic 6.5.0-14.14~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/2049239/+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 2047727] [NEW] display backlight

2024-01-20 Thread Launchpad Bug Tracker 
You have been subscribed to a public bug:

bridness backlight

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-26.26~22.04.1-generic 6.2.13
Uname: Linux 6.2.0-26-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Dec 30 20:15:41 2023
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:0214]
   Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:0214]
InstallationDate: Installed on 2023-12-30 (0 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
MachineType: emachines emachines D725
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-26-generic root=/dev/sda2 ro quiet 
splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/10/2009
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: V1.12
dmi.board.name: HM40
dmi.board.vendor: emachines
dmi.board.version: Rev
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.12:bd08/10/2009:svnemachines:pnemachinesD725:pvr0100:rvnemachines:rnHM40:rvrRev:cvnAcer:ct10:cvrN/A:sku:
dmi.product.name: emachines D725
dmi.product.version: 0100
dmi.sys.vendor: emachines
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug jammy ubuntu wayland-session
-- 
display backlight
https://bugs.launchpad.net/bugs/2047727
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg in Ubuntu.

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

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

2024-01-20 Thread Bug Watch Updater 
** Changed in: vcr.py (Debian)
   Status: Unknown => Fix Released

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

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

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

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

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

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


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