[Touch-packages] [Bug 2047450] Autopkgtest regression report (coreutils/9.1-1ubuntu2.23.10.1)

2024-01-21 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted coreutils (9.1-1ubuntu2.23.10.1) for 
mantic have finished running.
The following regressions have been reported in tests triggered by the package:

initramfs-tools/0.142ubuntu15.1 (arm64, armhf, s390x)
linux-laptop/6.5.0-1009.12 (arm64)
linux-lowlatency/6.5.0-17.17.1 (arm64)
uqm/0.8.0+dfsg-2 (amd64, armhf, ppc64el, 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/mantic/update_excuses.html#coreutils

[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 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 2050033] Re: gettext: msgfmt --java2 does not support Java 21

2024-01-21 Thread Bug Watch Updater
** Changed in: gettext (Debian)
   Status: Unknown => New

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

Title:
  gettext: msgfmt --java2 does not support Java 21

Status in gettext package in Ubuntu:
  New
Status in gettext package in Debian:
  New

Bug description:
  When building 'ssl-utils-clojure' package with Java 21 as default, the build
  fails with the following trace:
  --
  Applying task i18n to [make]
  Running 'make i18n'
  make[1]: *** [debian/rules:19: override_dh_auto_build] Error 1
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:12: binary] Error 2
  dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
2
  --

  Running make in the build chroot produces the following error:
  ---
  msgfmt --java2 -d resources -r puppetlabs.ssl_utils.Messages -l eo
  locales/eo.po
  msgfmt: Java compiler not found, try installing gcj or set $JAVAC
  msgfmt: compilation of Java class failed, please try --verbose or set $JAVAC
  make: *** [dev-resources/Makefile.i18n:94:
  resources/puppetlabs/ssl_utils/Messages_eo.class] Error 1
  ---

  It appears that gettext package does not support Java 21.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gettext/+bug/2050033/+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] Autopkgtest regression report (coreutils/8.32-4.1ubuntu1.1)

2024-01-21 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted coreutils (8.32-4.1ubuntu1.1) for jammy 
have finished running.
The following regressions have been reported in tests triggered by the package:

dgit/9.15 (amd64)
linux-azure-5.19/5.19.0-1027.30~22.04.2 (arm64)
linux-gcp-5.19/5.19.0-1030.32~22.04.1 (arm64)
linux-gcp-6.2/6.2.0-1019.21~22.04.1 (arm64)
linux-hwe-5.19/5.19.0-50.50 (arm64)
linux-lowlatency/5.15.0-91.101 (arm64)
linux-lowlatency-hwe-5.19/5.19.0-1030.30 (arm64)
linux-lowlatency-hwe-6.5/6.5.0-14.14.1~22.04.1 (arm64)
linux-nvidia-6.5/6.5.0-1010.10 (arm64)
linux-nvidia-tegra/5.15.0-1020.20 (arm64)
linux-xilinx-zynqmp/5.15.0-1025.29 (arm64)


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#coreutils

[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 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 1307883] Re: ca-certificates-java misses runtime dependency on initscripts

2024-01-21 Thread Thorsten Glaser
openjdk-8 fixed this by introducing explicit dependencies on the package
carrying mountpoint:

ifneq (,$(filter $(distrel),wheezy jessie precise trusty))
  control_vars += '-Vmountpoint:Depends=initscripts'
else
  control_vars += '-Vmountpoint:Depends=util-linux (>= 2.26.2-4)'
endif


** Changed in: openjdk-8 (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  ca-certificates-java misses runtime dependency on initscripts

Status in ca-certificates-java package in Ubuntu:
  Confirmed
Status in openjdk-7 package in Ubuntu:
  Confirmed
Status in openjdk-8 package in Ubuntu:
  Fix Released
Status in util-linux package in Ubuntu:
  Triaged

Bug description:
  Jitsi build-depends on openjdk-7-jre but the package fails to install
  in pbuilder and thus I currently cannot build the package.  Here is
  the output I get while I am logged in to the trusty chroot.

  # aptitude install default-jdk
  [...]
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  A package failed to install.  Trying to recover:
  Setting up ca-certificates-java (20130815ubuntu1) ...
  /var/lib/dpkg/info/ca-certificates-java.postinst: line 90: mountpoint: 
command not found
  the keytool command requires a mounted proc fs (/proc).
  dpkg: error processing package ca-certificates-java (--configure):
   subprocess installed post-installation script returned error exit status 1
  Setting up openjdk-7-jre-headless:i386 (7u51-2.4.6-1ubuntu4) ...
  /var/lib/dpkg/info/openjdk-7-jre-headless:i386.postinst: 18: 
/var/lib/dpkg/info/openjdk-7-jre-headless:i386.postinst: mountpoint: not found
  the java command requires a mounted proc fs (/proc).
  dpkg: error processing package openjdk-7-jre-headless:i386 (--configure):
   subprocess installed post-installation script returned error exit status 1
  Setting up default-jre-headless (2:1.7-51) ...
  dpkg: dependency problems prevent configuration of openjdk-7-jre:i386:
   openjdk-7-jre:i386 depends on openjdk-7-jre-headless (= 
7u51-2.4.6-1ubuntu4); however:
    Package openjdk-7-jre-headless:i386 is not configured yet.

  dpkg: error processing package openjdk-7-jre:i386 (--configure):
   dependency problems - leaving unconfigured
  Setting up default-jre (2:1.7-51) ...
  dpkg: dependency problems prevent configuration of openjdk-7-jdk:i386:
   openjdk-7-jdk:i386 depends on openjdk-7-jre (= 7u51-2.4.6-1ubuntu4); however:
    Package openjdk-7-jre:i386 is not configured yet.

  dpkg: error processing package openjdk-7-jdk:i386 (--configure):
   dependency problems - leaving unconfigured
  dpkg: dependency problems prevent configuration of default-jdk:
   default-jdk depends on openjdk-7-jdk (>= 7~u3-2.1.1); however:
    Package openjdk-7-jdk:i386 is not configured yet.

  dpkg: error processing package default-jdk (--configure):
   dependency problems - leaving unconfigured
  Processing triggers for ca-certificates (20130906ubuntu2) ...
  Updating certificates in /etc/ssl/certs... 0 added, 0 removed; done.
  Running hooks in /etc/ca-certificates/update.d
  /etc/ca-certificates/update.d/jks-keystore: 33: 
/etc/ca-certificates/update.d/jks-keystore: mountpoint: not found
  the keytool command requires a mounted proc fs (/proc).
  E: /etc/ca-certificates/update.d/jks-keystore exited with code 1.
  done.
  Errors were encountered while processing:
   ca-certificates-java
   openjdk-7-jre-headless:i386
   openjdk-7-jre:i386
   openjdk-7-jdk:i386
   default-jdk

  # mount
  /proc on /proc type proc (rw,relatime)
  tmpfs on /run/shm type tmpfs (rw,relatime)
  /dev/pts on /dev/pts type devpts 
(rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates-java/+bug/1307883/+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] Re: multiscreen one display goes black on resume

2024-01-21 Thread Daniel van Vugt
If it's software at all then this would be a kernel bug. But I suspect
the issue is more likely hardware since 1920x1080 @60Hz is pushing the
limits of analog VGA. Anything less than a perfect cable with perfect
connections and I'd expect display glitches like this.

Personally I'd recommend adding a graphics card to the machine so you
can use HDMI on both monitors. But you might also want to try 30Hz to
see if it makes the display more stable. We can also keep this open as a
kernel bug just in case it is.


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

** Summary changed:

- multiscreen one display goes black on resume
+ Analog VGA goes black on resume

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

Title:
  Analog VGA goes black on resume

Status in linux package in Ubuntu:
  New

Bug description:
  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, 

[Touch-packages] [Bug 1673258] Re: Remove aptdaemon and drop or port its reverse-dependencies

2024-01-21 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: update-notifier (Ubuntu)
   Status: New => Confirmed

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

Title:
  Remove aptdaemon and drop or port its reverse-dependencies

Status in aptdaemon package in Ubuntu:
  Confirmed
Status in apturl package in Ubuntu:
  Confirmed
Status in dell-recovery package in Ubuntu:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in language-selector package in Ubuntu:
  Confirmed
Status in lubuntu-software-center package in Ubuntu:
  Fix Released
Status in lubuntu-update-notifier package in Ubuntu:
  Confirmed
Status in mythbuntu-control-centre package in Ubuntu:
  Fix Released
Status in oem-config package in Ubuntu:
  Confirmed
Status in sessioninstaller package in Ubuntu:
  Fix Released
Status in software-properties package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Confirmed
Status in ubuntu-mate-meta package in Ubuntu:
  Fix Released
Status in ubuntu-mate-welcome package in Ubuntu:
  Opinion
Status in update-manager package in Ubuntu:
  Confirmed
Status in update-notifier package in Ubuntu:
  Confirmed
Status in zeroinstall-injector package in Ubuntu:
  Fix Released

Bug description:
  aptdaemon is abandoned and unmaintained.  It has already been dropped
  from Debian, but there are several reverse dependencies keeping it in
  Ubuntu.  I will add bug tasks for each of those dependencies, which
  should be ported or dropped themselves.  Then we can get rid of
  aptdaemon too.

  See this mailing list thread for more details:
  https://lists.ubuntu.com/archives/ubuntu-devel/2017-March/039722.html

  https://github.com/ubuntu-mate/ubuntu-mate-welcome/issues/48

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1673258/+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 1673258] Re: Remove aptdaemon and drop or port its reverse-dependencies

2024-01-21 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: update-manager (Ubuntu)
   Status: New => Confirmed

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

Title:
  Remove aptdaemon and drop or port its reverse-dependencies

Status in aptdaemon package in Ubuntu:
  Confirmed
Status in apturl package in Ubuntu:
  Confirmed
Status in dell-recovery package in Ubuntu:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in language-selector package in Ubuntu:
  Confirmed
Status in lubuntu-software-center package in Ubuntu:
  Fix Released
Status in lubuntu-update-notifier package in Ubuntu:
  Confirmed
Status in mythbuntu-control-centre package in Ubuntu:
  Fix Released
Status in oem-config package in Ubuntu:
  Confirmed
Status in sessioninstaller package in Ubuntu:
  Fix Released
Status in software-properties package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Confirmed
Status in ubuntu-mate-meta package in Ubuntu:
  Fix Released
Status in ubuntu-mate-welcome package in Ubuntu:
  Opinion
Status in update-manager package in Ubuntu:
  Confirmed
Status in update-notifier package in Ubuntu:
  Confirmed
Status in zeroinstall-injector package in Ubuntu:
  Fix Released

Bug description:
  aptdaemon is abandoned and unmaintained.  It has already been dropped
  from Debian, but there are several reverse dependencies keeping it in
  Ubuntu.  I will add bug tasks for each of those dependencies, which
  should be ported or dropped themselves.  Then we can get rid of
  aptdaemon too.

  See this mailing list thread for more details:
  https://lists.ubuntu.com/archives/ubuntu-devel/2017-March/039722.html

  https://github.com/ubuntu-mate/ubuntu-mate-welcome/issues/48

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1673258/+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 1673258] Re: Remove aptdaemon and drop or port its reverse-dependencies

2024-01-21 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Remove aptdaemon and drop or port its reverse-dependencies

Status in aptdaemon package in Ubuntu:
  Confirmed
Status in apturl package in Ubuntu:
  Confirmed
Status in dell-recovery package in Ubuntu:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in language-selector package in Ubuntu:
  Confirmed
Status in lubuntu-software-center package in Ubuntu:
  Fix Released
Status in lubuntu-update-notifier package in Ubuntu:
  Confirmed
Status in mythbuntu-control-centre package in Ubuntu:
  Fix Released
Status in oem-config package in Ubuntu:
  Confirmed
Status in sessioninstaller package in Ubuntu:
  Fix Released
Status in software-properties package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Confirmed
Status in ubuntu-mate-meta package in Ubuntu:
  Fix Released
Status in ubuntu-mate-welcome package in Ubuntu:
  Opinion
Status in update-manager package in Ubuntu:
  Confirmed
Status in update-notifier package in Ubuntu:
  Confirmed
Status in zeroinstall-injector package in Ubuntu:
  Fix Released

Bug description:
  aptdaemon is abandoned and unmaintained.  It has already been dropped
  from Debian, but there are several reverse dependencies keeping it in
  Ubuntu.  I will add bug tasks for each of those dependencies, which
  should be ported or dropped themselves.  Then we can get rid of
  aptdaemon too.

  See this mailing list thread for more details:
  https://lists.ubuntu.com/archives/ubuntu-devel/2017-March/039722.html

  https://github.com/ubuntu-mate/ubuntu-mate-welcome/issues/48

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1673258/+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 1673258] Re: Remove aptdaemon and drop or port its reverse-dependencies

2024-01-21 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: oem-config (Ubuntu)
   Status: New => Confirmed

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

Title:
  Remove aptdaemon and drop or port its reverse-dependencies

Status in aptdaemon package in Ubuntu:
  Confirmed
Status in apturl package in Ubuntu:
  Confirmed
Status in dell-recovery package in Ubuntu:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in language-selector package in Ubuntu:
  Confirmed
Status in lubuntu-software-center package in Ubuntu:
  Fix Released
Status in lubuntu-update-notifier package in Ubuntu:
  Confirmed
Status in mythbuntu-control-centre package in Ubuntu:
  Fix Released
Status in oem-config package in Ubuntu:
  Confirmed
Status in sessioninstaller package in Ubuntu:
  Fix Released
Status in software-properties package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Confirmed
Status in ubuntu-mate-meta package in Ubuntu:
  Fix Released
Status in ubuntu-mate-welcome package in Ubuntu:
  Opinion
Status in update-manager package in Ubuntu:
  Confirmed
Status in update-notifier package in Ubuntu:
  Confirmed
Status in zeroinstall-injector package in Ubuntu:
  Fix Released

Bug description:
  aptdaemon is abandoned and unmaintained.  It has already been dropped
  from Debian, but there are several reverse dependencies keeping it in
  Ubuntu.  I will add bug tasks for each of those dependencies, which
  should be ported or dropped themselves.  Then we can get rid of
  aptdaemon too.

  See this mailing list thread for more details:
  https://lists.ubuntu.com/archives/ubuntu-devel/2017-March/039722.html

  https://github.com/ubuntu-mate/ubuntu-mate-welcome/issues/48

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1673258/+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 1673258] Re: Remove aptdaemon and drop or port its reverse-dependencies

2024-01-21 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Remove aptdaemon and drop or port its reverse-dependencies

Status in aptdaemon package in Ubuntu:
  Confirmed
Status in apturl package in Ubuntu:
  Confirmed
Status in dell-recovery package in Ubuntu:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in language-selector package in Ubuntu:
  Confirmed
Status in lubuntu-software-center package in Ubuntu:
  Fix Released
Status in lubuntu-update-notifier package in Ubuntu:
  Confirmed
Status in mythbuntu-control-centre package in Ubuntu:
  Fix Released
Status in oem-config package in Ubuntu:
  Confirmed
Status in sessioninstaller package in Ubuntu:
  Fix Released
Status in software-properties package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Confirmed
Status in ubuntu-mate-meta package in Ubuntu:
  Fix Released
Status in ubuntu-mate-welcome package in Ubuntu:
  Opinion
Status in update-manager package in Ubuntu:
  Confirmed
Status in update-notifier package in Ubuntu:
  Confirmed
Status in zeroinstall-injector package in Ubuntu:
  Fix Released

Bug description:
  aptdaemon is abandoned and unmaintained.  It has already been dropped
  from Debian, but there are several reverse dependencies keeping it in
  Ubuntu.  I will add bug tasks for each of those dependencies, which
  should be ported or dropped themselves.  Then we can get rid of
  aptdaemon too.

  See this mailing list thread for more details:
  https://lists.ubuntu.com/archives/ubuntu-devel/2017-March/039722.html

  https://github.com/ubuntu-mate/ubuntu-mate-welcome/issues/48

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1673258/+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 1673258] Re: Remove aptdaemon and drop or port its reverse-dependencies

2024-01-21 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: language-selector (Ubuntu)
   Status: New => Confirmed

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

Title:
  Remove aptdaemon and drop or port its reverse-dependencies

Status in aptdaemon package in Ubuntu:
  Confirmed
Status in apturl package in Ubuntu:
  Confirmed
Status in dell-recovery package in Ubuntu:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in language-selector package in Ubuntu:
  Confirmed
Status in lubuntu-software-center package in Ubuntu:
  Fix Released
Status in lubuntu-update-notifier package in Ubuntu:
  Confirmed
Status in mythbuntu-control-centre package in Ubuntu:
  Fix Released
Status in oem-config package in Ubuntu:
  Confirmed
Status in sessioninstaller package in Ubuntu:
  Fix Released
Status in software-properties package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Confirmed
Status in ubuntu-mate-meta package in Ubuntu:
  Fix Released
Status in ubuntu-mate-welcome package in Ubuntu:
  Opinion
Status in update-manager package in Ubuntu:
  Confirmed
Status in update-notifier package in Ubuntu:
  Confirmed
Status in zeroinstall-injector package in Ubuntu:
  Fix Released

Bug description:
  aptdaemon is abandoned and unmaintained.  It has already been dropped
  from Debian, but there are several reverse dependencies keeping it in
  Ubuntu.  I will add bug tasks for each of those dependencies, which
  should be ported or dropped themselves.  Then we can get rid of
  aptdaemon too.

  See this mailing list thread for more details:
  https://lists.ubuntu.com/archives/ubuntu-devel/2017-March/039722.html

  https://github.com/ubuntu-mate/ubuntu-mate-welcome/issues/48

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1673258/+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 1673258] Re: Remove aptdaemon and drop or port its reverse-dependencies

2024-01-21 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Remove aptdaemon and drop or port its reverse-dependencies

Status in aptdaemon package in Ubuntu:
  Confirmed
Status in apturl package in Ubuntu:
  Confirmed
Status in dell-recovery package in Ubuntu:
  Fix Released
Status in gnome-software package in Ubuntu:
  Fix Released
Status in language-selector package in Ubuntu:
  Confirmed
Status in lubuntu-software-center package in Ubuntu:
  Fix Released
Status in lubuntu-update-notifier package in Ubuntu:
  Confirmed
Status in mythbuntu-control-centre package in Ubuntu:
  Fix Released
Status in oem-config package in Ubuntu:
  Confirmed
Status in sessioninstaller package in Ubuntu:
  Fix Released
Status in software-properties package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Confirmed
Status in ubuntu-mate-meta package in Ubuntu:
  Fix Released
Status in ubuntu-mate-welcome package in Ubuntu:
  Opinion
Status in update-manager package in Ubuntu:
  Confirmed
Status in update-notifier package in Ubuntu:
  Confirmed
Status in zeroinstall-injector package in Ubuntu:
  Fix Released

Bug description:
  aptdaemon is abandoned and unmaintained.  It has already been dropped
  from Debian, but there are several reverse dependencies keeping it in
  Ubuntu.  I will add bug tasks for each of those dependencies, which
  should be ported or dropped themselves.  Then we can get rid of
  aptdaemon too.

  See this mailing list thread for more details:
  https://lists.ubuntu.com/archives/ubuntu-devel/2017-March/039722.html

  https://github.com/ubuntu-mate/ubuntu-mate-welcome/issues/48

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1673258/+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 2049318] Autopkgtest regression report (iptables/1.8.7-1ubuntu5.2)

2024-01-21 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted iptables (1.8.7-1ubuntu5.2) for jammy 
have finished running.
The following regressions have been reported in tests triggered by the package:

ganeti/3.0.2-1ubuntu1 (armhf)


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#iptables

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

Thank you!

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

Title:
  [SRU] free(): double free detected in tcache 2

Status in iptables package in Ubuntu:
  Fix Released
Status in iptables source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

  iptables is unable to list the iptables rules or save the iptables
  rules if a nftables ruleset is defined which iptables does not
  recognize.

  [ Test Plan ]

  1. Simple test plan based on upstream test case:

  sudo nft -f - < rules.txt

  * Convert the rule to nftables ruleset
    - sudo iptables-nft-restore < rules.txt

  * List the nftables ruleset
    - sudo nft list ruleset

  * Also confirm that iptables can list the old rule
    - sudo iptables -L

  * Now add another nftables rule (this rule is taken from upstream test
  case)

  sudo nft -f - 

[Touch-packages] [Bug 2050033] Re: gettext: msgfmt --java2 does not support Java 21

2024-01-21 Thread Launchpad Bug Tracker
** Merge proposal linked:
   
https://code.launchpad.net/~vpa1977/ubuntu/+source/gettext/+git/gettext/+merge/459117

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

Title:
  gettext: msgfmt --java2 does not support Java 21

Status in gettext package in Ubuntu:
  New
Status in gettext package in Debian:
  Unknown

Bug description:
  When building 'ssl-utils-clojure' package with Java 21 as default, the build
  fails with the following trace:
  --
  Applying task i18n to [make]
  Running 'make i18n'
  make[1]: *** [debian/rules:19: override_dh_auto_build] Error 1
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:12: binary] Error 2
  dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
2
  --

  Running make in the build chroot produces the following error:
  ---
  msgfmt --java2 -d resources -r puppetlabs.ssl_utils.Messages -l eo
  locales/eo.po
  msgfmt: Java compiler not found, try installing gcj or set $JAVAC
  msgfmt: compilation of Java class failed, please try --verbose or set $JAVAC
  make: *** [dev-resources/Makefile.i18n:94:
  resources/puppetlabs/ssl_utils/Messages_eo.class] Error 1
  ---

  It appears that gettext package does not support Java 21.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gettext/+bug/2050033/+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: [HP Victus 15-fb0xxx] Can't change screen brightness

2024-01-21 Thread Daniel van Vugt
** Summary changed:

- Can't change screen brightness
+ [HP Victus 15-fb0xxx] Can't change screen brightness

** Package changed: xorg (Ubuntu) => linux-hwe-6.5 (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:
  [HP Victus 15-fb0xxx] Can't change screen brightness

Status in linux-hwe-6.5 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/linux-hwe-6.5/+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 2049958] Re: package bluez-obexd 5.68-0ubuntu1 failed to install/upgrade: unable to make backup link of './usr/lib/bluetooth/obexd' before installing new version: Input/output er

2024-01-21 Thread Daniel van Vugt
"Input/output error" is probably a USB connection issue, or a flash
drive error. Please try a different drive and/or different USB port.

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

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  package bluez-obexd 5.68-0ubuntu1 failed to install/upgrade: unable to
  make backup link of './usr/lib/bluetooth/obexd' before installing new
  version: Input/output error

Status in Ubuntu:
  Incomplete

Bug description:
  bug found during software update launched from bootable usb

  ProblemType: Package
  DistroRelease: Ubuntu 23.10
  Package: bluez-obexd 5.68-0ubuntu1
  ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
  Uname: Linux 6.5.0-9-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckMismatches: ./casper/minimal.squashfs
  CasperMD5CheckResult: fail
  CasperVersion: 1.486
  CloudArchitecture: x86_64
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
  Date: Sat Jan 20 00:18:32 2024
  DuplicateSignature:
   package:bluez-obexd:5.68-0ubuntu1
   Unpacking bluez-obexd (5.68-0ubuntu1.1) over (5.68-0ubuntu1) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-MsVzUs/045-bluez-obexd_5.68-0ubuntu1.1_amd64.deb 
(--unpack):
unable to make backup link of './usr/lib/bluetooth/obexd' before installing 
new version: Input/output error
  ErrorMessage: unable to make backup link of './usr/lib/bluetooth/obexd' 
before installing new version: Input/output error
  InterestingModules: rfcomm bnep btusb bluetooth
  LiveMediaBuild: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz persistent 
layerfs-path=minimal.standard.live.squashfs --- quiet splash
  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: bluez
  Title: package bluez-obexd 5.68-0ubuntu1 failed to install/upgrade: unable to 
make backup link of './usr/lib/bluetooth/obexd' before installing new version: 
Input/output error
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/26/2018
  dmi.bios.release: 5.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 306
  dmi.board.asset.tag: Default string
  dmi.board.name: GL553VW
  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.:bvr306:bd09/26/2018:br5.6:svnASUSTeKCOMPUTERINC.:pnGL553VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL553VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU:
  dmi.product.family: GL
  dmi.product.name: GL553VW
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: D0:57:7B:12:13:2F  ACL MTU: 1021:5  SCO MTU: 96:6
UP RUNNING 
RX bytes:1345 acl:0 sco:0 events:90 errors:0
TX bytes:3835 acl:0 sco:0 commands:90 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2049958/+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] Re: [Acer eMachines D725] Display backlight

2024-01-21 Thread Daniel van Vugt
** Summary changed:

- display backlight
+ [Acer eMachines D725] Display backlight

** Package changed: xorg (Ubuntu) => linux-hwe-6.2 (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/2047727

Title:
  [Acer eMachines D725] Display backlight

Status in linux-hwe-6.2 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/linux-hwe-6.2/+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 80900] Re: Avahi daemon prevents resolution of FQDNs ending in ".local" due to false negatives in the detection of ".local" networks

2024-01-21 Thread Ken Sharp
** Changed in: avahi (Debian)
   Importance: Undecided => Unknown

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

** Changed in: avahi (Debian)
 Remote watch: None => Debian Bug tracker #393711

** Package changed: avahi (Debian) => nss-mdns (Debian)

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

Title:
  Avahi daemon prevents resolution of FQDNs ending in ".local" due to
  false negatives in the detection of ".local" networks

Status in avahi package in Ubuntu:
  Fix Released
Status in nss-mdns package in Ubuntu:
  Fix Released
Status in nss-mdns package in Debian:
  Unknown

Bug description:
  Install Kubuntu Feisty
  Set the ip address to dhcp for eth0 (ethernet port)
  make sure the host name and domain name are set
  Hostname computer1
  DomainName mydomain.local
  allow DHCP to assign the IP address

  Ensure the computer details are registered in DNS for
  mydomain.local...

  computer names registered in DNS (FQDN)
  computer1.mydomain.local
  computer2.mydomain.local
  computer3.mydomain.local

  computer2 and computer3 are both running Kubuntu Dapper and are both
  using DHCP.

  if I issue the following comands on computer2 or computer3, it works
  correctly:

  ping computer2  (response received - ping good)
  ping computer3  (response received - ping good)
  ping computer2.mydomain.local   (response received - ping good)
  ping computer3.mydomain.local   (response received - ping good)

  if i issue the same commands from the feisty box (computer1), these
  are the results..

  ping computer2   (response received - ping good)
  ping computer3   (response received - ping good)
  ping computer2.mydomain.local   (unknown host)
  ping computer3.mydomain.local  (unknown host)
  for some reason if you try to ping the fully qualified domain name on feisty, 
it cant resolve it, yet it can resolve it using both static IP Addressing and 
DHCP addressing on Dapper. (i set the IP to static as well for the test) Static 
and DHCP on Dapper works fine. Static and DHCP wont resolve fully qualified 
domain names on Feisty. (computer1, computer2 and computer 3 are all Kubuntu 
machines. DNS Server is a Windows 2003 Server (that will be changed a kubuntu 
server very soon though!)

  It can resolve the host name only though, and will return the fully
  qualified domain name in the response.

  cheers

  Rod.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/80900/+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 2050033] [NEW] gettext: msgfmt --java2 does not support Java 21

2024-01-21 Thread Vladimir Petko
Public bug reported:

When building 'ssl-utils-clojure' package with Java 21 as default, the build
fails with the following trace:
--
Applying task i18n to [make]
Running 'make i18n'
make[1]: *** [debian/rules:19: override_dh_auto_build] Error 1
make[1]: Leaving directory '/<>'
make: *** [debian/rules:12: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--

Running make in the build chroot produces the following error:
---
msgfmt --java2 -d resources -r puppetlabs.ssl_utils.Messages -l eo
locales/eo.po
msgfmt: Java compiler not found, try installing gcj or set $JAVAC
msgfmt: compilation of Java class failed, please try --verbose or set $JAVAC
make: *** [dev-resources/Makefile.i18n:94:
resources/puppetlabs/ssl_utils/Messages_eo.class] Error 1
---

It appears that gettext package does not support Java 21.

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

** Affects: gettext (Debian)
 Importance: Unknown
 Status: Unknown

** Bug watch added: Debian Bug tracker #1056293
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056293

** Also affects: gettext (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1056293
   Importance: Unknown
   Status: Unknown

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

Title:
  gettext: msgfmt --java2 does not support Java 21

Status in gettext package in Ubuntu:
  New
Status in gettext package in Debian:
  Unknown

Bug description:
  When building 'ssl-utils-clojure' package with Java 21 as default, the build
  fails with the following trace:
  --
  Applying task i18n to [make]
  Running 'make i18n'
  make[1]: *** [debian/rules:19: override_dh_auto_build] Error 1
  make[1]: Leaving directory '/<>'
  make: *** [debian/rules:12: binary] Error 2
  dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 
2
  --

  Running make in the build chroot produces the following error:
  ---
  msgfmt --java2 -d resources -r puppetlabs.ssl_utils.Messages -l eo
  locales/eo.po
  msgfmt: Java compiler not found, try installing gcj or set $JAVAC
  msgfmt: compilation of Java class failed, please try --verbose or set $JAVAC
  make: *** [dev-resources/Makefile.i18n:94:
  resources/puppetlabs/ssl_utils/Messages_eo.class] Error 1
  ---

  It appears that gettext package does not support Java 21.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gettext/+bug/2050033/+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 2043640] Re: amdgpu: GPU Recovery fails, frequent hangs

2024-01-21 Thread OEM Taipei Bot
linux-oem-22.04d 6.5.0.1014.16 in jammy-proposed contains the fix.
https://changelogs.ubuntu.com/changelogs/pool/main/l/linux-
oem-6.5/linux-oem-6.5_6.5.0-1014.15/changelog

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

Title:
  amdgpu: GPU Recovery fails, frequent hangs

Status in Mesa:
  Fix Released
Status in linux package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Fix Released
Status in linux source package in Jammy:
  Confirmed
Status in mesa source package in Jammy:
  New
Status in linux source package in Lunar:
  Confirmed
Status in mesa source package in Lunar:
  New

Bug description:
  I've been using 23.04 for a few months, and experienced a total system
  hang occasionally when sharing my screen over Zoom or Google Meet
  (running on Google Chrome).

  At first it hangs and then it periodically flashes like it's trying
  (unsuccessfully) to recover; I've got 3 screens (including the
  laptop's internal one) and each attempt shows something different (at
  first it tries to recover the contents of all 3 screens, then it shows
  only one of them, and then it shows the same content on all 3, but it
  never gets responsive).

  I've recently upgraded to 23.10, hoping a new kernel would help the
  situation. It's only gotten considerably worse now; it hangs sometimes
  just when opening Zoom; it's somehow easier to reproduce with Google
  Chrome. Interestingly, it fails quickly and reliably now when enabling
  my webcam (with special effects). It started hanging badly when using
  Google Maps as well.

  For all these behaviors, I suspect amdgpu is to blame (I'm running on
  Renoir, 4750U Pro); `dmesg` and `journalctl` didn't seem to show
  anything interesting.

  Any tips about debugging this further?

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: linux-generic 6.5.0.10.12
  ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
  Uname: Linux 6.5.0-10-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: GNOME
  Date: Thu Nov 16 02:27:45 2023
  InstallationDate: Installed on 2023-07-02 (137 days ago)
  InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418)
  MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcFB: 0 amdgpudrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic 
root=/dev/mapper/ubuntu--vg-ubuntu--lv 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.
  RelatedPackageVersions:
   linux-restricted-modules-6.5.0-10-generic N/A
   linux-backports-modules-6.5.0-10-generic  N/A
   linux-firmware20230919.git3672ccab-0ubuntu2.1
  SourcePackage: linux
  UpgradeStatus: Upgraded to mantic on 2023-11-14 (2 days ago)
  dmi.bios.date: 06/13/2023
  dmi.bios.release: 1.44
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R1BET75W(1.44 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20UD000GUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.44
  dmi.modalias: 
dmi:bvnLENOVO:bvrR1BET75W(1.44):bd06/13/2023:br1.44:efr1.44:svnLENOVO:pn20UD000GUS:pvrThinkPadT14Gen1:rvnLENOVO:rn20UD000GUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UD_BU_Think_FM_ThinkPadT14Gen1:
  dmi.product.family: ThinkPad T14 Gen 1
  dmi.product.name: 20UD000GUS
  dmi.product.sku: LENOVO_MT_20UD_BU_Think_FM_ThinkPad T14 Gen 1
  dmi.product.version: ThinkPad T14 Gen 1
  dmi.sys.vendor: LENOVO

  X-HWE-Bug: Bug #2047389

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/2043640/+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 1913977] Re: Bad sound quality (no bass) on Thinkpad T490s

2024-01-21 Thread Bavarian
I have the same issue with Thinkpad L14 Gen 2, Intel version. 
Running Ubuntu 22.04.3 LTS with kernel 6.5.0-14-generic

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

Title:
  Bad sound quality (no bass) on Thinkpad T490s

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Sound works on with 20.04 on the Thinkpad T490s, but sound quality is
  noticeably worse than on Windows. It looks like the same bug here:
  https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1872108

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18
  Uname: Linux 5.8.0-41-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.14
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  hmahmood   1360 F pulseaudio
   /dev/snd/pcmC0D0p:   hmahmood   1360 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 31 19:14:57 2021
  InstallationDate: Installed on 2021-01-30 (1 days ago)
  InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: None of the above
  Title: [20NYS83800, Realtek ALC257, Speaker, Internal] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/31/2020
  dmi.bios.release: 1.70
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N2JET92W (1.70 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20NYS83800
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.ec.firmware.release: 1.20
  dmi.modalias: 
dmi:bvnLENOVO:bvrN2JET92W(1.70):bd08/31/2020:br1.70:efr1.20:svnLENOVO:pn20NYS83800:pvrThinkPadT490s:rvnLENOVO:rn20NYS83800:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T490s
  dmi.product.name: 20NYS83800
  dmi.product.sku: LENOVO_MT_20NY_BU_Think_FM_ThinkPad T490s
  dmi.product.version: ThinkPad T490s
  dmi.sys.vendor: LENOVO

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


Re: [Touch-packages] [Bug 2049988] Re: Latest kernel kills wifi.

2024-01-21 Thread Patrick M
Thank you for the reply. I had to apply the command twice. It gave me an 
error the first time. Report was sent ( I think)

On 1/21/24 03:16, Chris Guiver wrote:
> apport-collect 2049988

** Package changed: linux (Ubuntu) => network-manager (Ubuntu)

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

Title:
  Latest kernel kills wifi.

Status in network-manager package in Ubuntu:
  New

Bug description:
  New kernel 6.0.5-14 boot up system does not recognize built in wifi
  adapter. When I drop to last kernel install wifi works fine.

  HP Pavillion With intel core I7 chip.

  Output of lshow --C network:

   *-network 
 description: Wireless interface
 product: MT7921 802.11ax PCI Express Wireless Network Adapter
 vendor: MEDIATEK Corp.
 physical id: 0
 bus info: pci@:02:00.0
 logical name: wlp2s0
 version: 00
 serial: b4:8c:9d:28:0e:cb
 width: 64 bits
 clock: 33MHz
 capabilities: pciexpress msi pm bus_master cap_list ethernet physical 
wireless
 configuration: broadcast=yes driver=mt7921e 
driverversion=6.2.0-39-generic firmware=01-20220209150915 
ip=192.168.1.81 latency=0 link=yes multicast=yes wireless=IEEE 802.11
 resources: iomemory:600-5ff iomemory:600-5ff iomemory:600-5ff irq:144 
memory:601210-60121f memory:601220-6012203fff 
memory:6012204000-6012204fff
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  patrick2379 F pulseaudio
  CRDA: N/A
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 22.04
  InstallationDate: Installed on 2022-11-15 (432 days ago)
  InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
  MachineType: HP HP Pavilion Laptop 15-eg2xxx
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic 
root=UUID=2a43dcba-8f84-43f8-a1d6-ad38002f17c0 ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  RelatedPackageVersions:
   linux-restricted-modules-6.2.0-39-generic N/A
   linux-backports-modules-6.2.0-39-generic  N/A
   linux-firmware20220329.git681281e4-0ubuntu3.24
  Tags:  jammy
  Uname: Linux 6.2.0-39-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 11/08/2023
  dmi.bios.release: 15.14
  dmi.bios.vendor: AMI
  dmi.bios.version: F.14
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 89F7
  dmi.board.vendor: HP
  dmi.board.version: 14.27
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 14.27
  dmi.modalias: 
dmi:bvnAMI:bvrF.14:bd11/08/2023:br15.14:efr14.27:svnHP:pnHPPavilionLaptop15-eg2xxx:pvr:rvnHP:rn89F7:rvr14.27:cvnHP:ct10:cvrChassisVersion:sku6W540UA#ABA:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Laptop 15-eg2xxx
  dmi.product.sku: 6W540UA#ABA
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2049988/+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 2049988] [NEW] Latest kernel kills wifi.

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

New kernel 6.0.5-14 boot up system does not recognize built in wifi
adapter. When I drop to last kernel install wifi works fine.

HP Pavillion With intel core I7 chip.

Output of lshow --C network:

 *-network 
   description: Wireless interface
   product: MT7921 802.11ax PCI Express Wireless Network Adapter
   vendor: MEDIATEK Corp.
   physical id: 0
   bus info: pci@:02:00.0
   logical name: wlp2s0
   version: 00
   serial: b4:8c:9d:28:0e:cb
   width: 64 bits
   clock: 33MHz
   capabilities: pciexpress msi pm bus_master cap_list ethernet physical 
wireless
   configuration: broadcast=yes driver=mt7921e 
driverversion=6.2.0-39-generic firmware=01-20220209150915 
ip=192.168.1.81 latency=0 link=yes multicast=yes wireless=IEEE 802.11
   resources: iomemory:600-5ff iomemory:600-5ff iomemory:600-5ff irq:144 
memory:601210-60121f memory:601220-6012203fff 
memory:6012204000-6012204fff
--- 
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  patrick2379 F pulseaudio
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2022-11-15 (432 days ago)
InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809.1)
MachineType: HP HP Pavilion Laptop 15-eg2xxx
Package: linux (not installed)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-39-generic 
root=UUID=2a43dcba-8f84-43f8-a1d6-ad38002f17c0 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
RelatedPackageVersions:
 linux-restricted-modules-6.2.0-39-generic N/A
 linux-backports-modules-6.2.0-39-generic  N/A
 linux-firmware20220329.git681281e4-0ubuntu3.24
Tags:  jammy
Uname: Linux 6.2.0-39-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 11/08/2023
dmi.bios.release: 15.14
dmi.bios.vendor: AMI
dmi.bios.version: F.14
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 89F7
dmi.board.vendor: HP
dmi.board.version: 14.27
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 14.27
dmi.modalias: 
dmi:bvnAMI:bvrF.14:bd11/08/2023:br15.14:efr14.27:svnHP:pnHPPavilionLaptop15-eg2xxx:pvr:rvnHP:rn89F7:rvr14.27:cvnHP:ct10:cvrChassisVersion:sku6W540UA#ABA:
dmi.product.family: 103C_5335KV HP Pavilion
dmi.product.name: HP Pavilion Laptop 15-eg2xxx
dmi.product.sku: 6W540UA#ABA
dmi.sys.vendor: HP

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


** Tags: 6.0.5-14 apport-collected bot-comment jammy kernel no wifi
-- 
Latest kernel kills wifi.
https://bugs.launchpad.net/bugs/2049988
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to network-manager 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 2042587] Re: jammy's version breaks existing dhcp scripts with relay

2024-01-21 Thread Timo M
Hello,

and thank you, seems to fix the issue. I updated my jammy's to dsnmasq
version 2.86-1.1ubuntu0.5, and tested with the same setup as I reported
the original bug. Can confirm that the DHCP hook script now works exatly
like it used to in focal, getting the correct IP address as an argument.


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

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

Title:
  jammy's version breaks existing dhcp scripts with relay

Status in dnsmasq package in Ubuntu:
  Fix Released
Status in dnsmasq source package in Jammy:
  Fix Committed

Bug description:
  [ Impact ]

  When upgrading from focal to jammy, existing dnsmasq dhcp-scripts
  stopped working in an environment where a DHCP relay is in use.
  Instead of the expected client IP address, the script gets the _relay_
  IP address as an argument.

  This was fixed in 2.87, therefore making only jammy carry an affected
  package.

  [ Test Plan ]

  To easily test this on a single machine, a test script is being
  provided to setup networking and dnsmasq configuration.

  # Launch a jammy VM

  lxc launch ubuntu-daily:jammy j-dnsmasq-2042587 --vm

  # open a root shell in that VM. All subsequent commands must be
  executed as root in that VM

  lxc shell j-dnsmasq-2042587

  # download test script

  wget
  
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2042587/+attachment/5738174/+files/setup-
  and-server.sh

  # make it executable

  chmod +x setup-and-server.sh

  # install dnsmasq. Ignore the postinst error (because systemd-resolved
  is also running and there is a port conflict)

  apt update && apt install dnsmasq -y

  # run the setup script. It will configure things and start dnsmasq
  ready to be tested

  ./setup-and-server.sh

  # in another root session inside the vm (so run "lxc shell
  j-dnsmasq-2042587" in another terminal), run the proposed commands
  from the setup script (and press ctrl-c after the result is shown):

  No DHCP relay:

    ip netns exec client dhclient -d -v p2

  The setup script should log an IP that is not a relay. For example:
  dnsmasq-dhcp: DHCPDISCOVER(p1) aa:a0:9d:00:5b:d6
  dnsmasq-dhcp: DHCPOFFER(p1) 192.168.47.150 aa:a0:9d:00:5b:d6
  dnsmasq-dhcp: DHCPREQUEST(p1) 192.168.47.150 aa:a0:9d:00:5b:d6
  dnsmasq-dhcp: DHCPACK(p1) 192.168.47.150 aa:a0:9d:00:5b:d6 j-dnsmasq-2042587
  ###
  IP = 192.168.47.150
  ###

  With DHCP relay set to 192.168.47.9, IP should NOT be that address:

    ip netns exec client dhclient -d -v p2 -g 192.168.47.9

  With the affected dnsmasq package, we will see an error:
  dnsmasq-dhcp: DHCPREQUEST(p1) 192.168.47.150 aa:a0:9d:00:5b:d6
  dnsmasq-dhcp: DHCPACK(p1) 192.168.47.150 aa:a0:9d:00:5b:d6 j-dnsmasq-2042587
  ###
  IP = 192.168.47.9
  TEST FAILED
  ###

  The error is that the obtained IP is that of the dhcp relay (provided
  via the -g option).

  With the fixed dnsmasq package, "TEST FAILED" must not appear, and the
  IP should not be that of the provided dhcp relay.

  [ Where problems could occur ]

  If the fix is incorrect, it would mean the dhcp-script would get an incorrect 
IP again, or perhaps we could have crashes in dnsmasq when dealing with buffers 
and pointers if the dhcp-script option is in use.
  This fix was committed upstream a few months after the bug was introduced, so 
it took a while to be noticed.

  [ Other Info ]
  Not at this time.

  [ Original description ]

  When upgrading from focal to jammy, existing dnsmasq dhcp-scripts
  stopped working in an environment where a DHCP relay is in use.
  Instead of the expected client IP address, the script gets the _relay_
  IP address as an argument. From dnsmasq documentation for --dhcp-
  script:

  > The arguments to the process are "add", "old" or "del", the MAC
  address of the host (or DUID for IPv6) , the IP address, and the
  hostname, if known.

  I believe the change has been inadverently made in upstream commit
  527c3c7d0d3bb4bf5fad699f10cf0d1a45a54692
  
(https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=blobdiff;f=src/helper.c;h=02340a01c00031db0cc682c8a4a279cfc1db574e;hp=d81de9622e6d484a264496b2cd3638b4e15e9677;hb=527c3c7d0d3bb4bf5fad699f10cf0d1a45a54692;hpb=fcb4dcaf7cc8a86ac2533b933161b6455f75bf8f)
  as the commit message only speaks about inet_ntoa replacement and not
  the behavioral change it also introduces (previously the relay address
  was only set to the environment variable, now it effectively overrides
  the prevoiusly set client's IP address).

  dnsmasq 2.86-1.1ubuntu0.3 / Ubuntu 22.04

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


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

[Touch-packages] [Bug 2049995] Re: System volume doesn't change volume

2024-01-21 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => alsa-driver (Ubuntu)

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

Title:
  System volume doesn't change volume

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Hi, as described here https://askubuntu.com/questions/1487030/system-
  volume-doesnt-change-app-volume, I also have this problem.

  I've already tried to boot with a Manjaro USB live with Gnome and
  there the volume works as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 23.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
  Uname: Linux 6.5.0-14-generic x86_64
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  japimentel   8590 F wireplumber
   /dev/snd/controlC0:  japimentel   8590 F wireplumber
   /dev/snd/seq:japimentel   8580 F pipewire
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jan 21 10:28:26 2024
  InstallationDate: Installed on 2023-11-21 (61 days ago)
  InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 
(20231016.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/12/2023
  dmi.bios.release: 1.21
  dmi.bios.vendor: LENOVO
  dmi.bios.version: MLCN21WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Yoga Pro 7 14APH8
  dmi.ec.firmware.release: 1.21
  dmi.modalias: 
dmi:bvnLENOVO:bvrMLCN21WW:bd07/12/2023:br1.21:efr1.21:svnLENOVO:pn82Y8:pvrYogaPro714APH8:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrYogaPro714APH8:skuLENOVO_MT_82Y8_BU_idea_FM_YogaPro714APH8:
  dmi.product.family: Yoga Pro 7 14APH8
  dmi.product.name: 82Y8
  dmi.product.sku: LENOVO_MT_82Y8_BU_idea_FM_Yoga Pro 7 14APH8
  dmi.product.version: Yoga Pro 7 14APH8
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2049995/+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 2049995] [NEW] System volume doesn't change volume

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

Hi, as described here https://askubuntu.com/questions/1487030/system-
volume-doesnt-change-app-volume, I also have this problem.

I've already tried to boot with a Manjaro USB live with Gnome and there
the volume works as expected.

ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 6.5.0-14.14-generic 6.5.3
Uname: Linux 6.5.0-14-generic x86_64
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  japimentel   8590 F wireplumber
 /dev/snd/controlC0:  japimentel   8590 F wireplumber
 /dev/snd/seq:japimentel   8580 F pipewire
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Sun Jan 21 10:28:26 2024
InstallationDate: Installed on 2023-11-21 (61 days ago)
InstallationMedia: Ubuntu 23.10.1 "Mantic Minotaur" - Release amd64 (20231016.1)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/12/2023
dmi.bios.release: 1.21
dmi.bios.vendor: LENOVO
dmi.bios.version: MLCN21WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: No DPK
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Yoga Pro 7 14APH8
dmi.ec.firmware.release: 1.21
dmi.modalias: 
dmi:bvnLENOVO:bvrMLCN21WW:bd07/12/2023:br1.21:efr1.21:svnLENOVO:pn82Y8:pvrYogaPro714APH8:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrYogaPro714APH8:skuLENOVO_MT_82Y8_BU_idea_FM_YogaPro714APH8:
dmi.product.family: Yoga Pro 7 14APH8
dmi.product.name: 82Y8
dmi.product.sku: LENOVO_MT_82Y8_BU_idea_FM_Yoga Pro 7 14APH8
dmi.product.version: Yoga Pro 7 14APH8
dmi.sys.vendor: LENOVO

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug mantic wayland-session
-- 
System volume doesn't change volume
https://bugs.launchpad.net/bugs/2049995
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to alsa-driver 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