from:"and"

You have been subscribed to a public bug:

When specifying vers=4.0 or nfsvers=4.0 in NFSv4 mount options, the
client ends up using version 4.2 instead. This option seems to be
ignored.

This happens with pam_mount and manual mount. We have been using
pam_mount for years with the option vers=4.0, but now it appears to be
broken. Just recently noticed this is happening while troubleshooting
root causes of some other issues on our servers.

Test: mounting manually with option: minorversion=0, the client does not mount, 
no errors are seen with -vvv, no errors in logs either, it just fails silently. 
With pam_mount this option fails as well but is logged as mount failed into 
auth.log 
ex: Apr 24 17:15:22 servername sshd[666278]: (pam_mount.c:522): mount of 
/mnt/nfs/home/admin_username failed

I see that something similar was fixed in autofs, but this is not autofs
related. https://bugs.launchpad.net/bugs/1818121

Found a similar [oracle] issue but cannot read it=
https://support.oracle.com/knowledge/Oracle%20Linux%20and%20Virtualization/2528012_1.html

---

Description:Ubuntu 20.04.6 LTS
Release:20.04

---
util-linux:
  Installed: 2.34-0.1ubuntu9.6
  Candidate: 2.34-0.1ubuntu9.6
  Version table:
 *** 2.34-0.1ubuntu9.6 500
500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
500 http://us.archive.ubuntu.com/ubuntu focal-security/main amd64 
Packages
100 /var/lib/dpkg/status
 2.34-0.1ubuntu9 500
500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages


mount:
  Installed: 2.34-0.1ubuntu9.6
  Candidate: 2.34-0.1ubuntu9.6
  Version table:
 *** 2.34-0.1ubuntu9.6 500
500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
500 http://us.archive.ubuntu.com/ubuntu focal-security/main amd64 
Packages
100 /var/lib/dpkg/status
 2.34-0.1ubuntu9 500
500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages


nfs-common:
  Installed: 1:1.3.4-2.5ubuntu3.6
  Candidate: 1:1.3.4-2.5ubuntu3.6
  Version table:
 *** 1:1.3.4-2.5ubuntu3.6 500
500 http://us.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 1:1.3.4-2.5ubuntu3.3 500
500 http://us.archive.ubuntu.com/ubuntu focal-security/main amd64 
Packages
 1:1.3.4-2.5ubuntu3 500
500 http://us.archive.ubuntu.com/ubuntu focal/main amd64 Packages

** Affects: util-linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: mount nfs
-- 
NFS Client can't mount via NFS version 4.0 
https://bugs.launchpad.net/bugs/2063381
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to util-linux 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 2063328] Re: FTBFS in eglibc

2024-04-24 Thread Leonidas S. Barbosa

** Changed in: eglibc (Ubuntu)
   Importance: Undecided => High

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

Title:
  FTBFS in eglibc

Status in eglibc package in Ubuntu:
  In Progress

Bug description:
  == Summary ==

  A FTBFS occurs in eglibc that affects trusty-esm to be build.

  == What happens ==
  # Format: , Error  [(ignored)]
  #
  annexc.out, Error 1 (ignored)
  bug22.out, Error 1
  run-conformtest.out, Error 1 (ignored)
  tst-mutex7.out, Error 1
  tst-mutex7a.out, Error 1
  tst-mutexpi7.out, Error 1
  tst-mutexpi7a.out, Error 1
  tst-once2.out, Error 1
  tst-setlocale3.out, Error 1
  ***
  Encountered regressions that don't match expected failures 
(debian/testsuite-checking/expected-results-x86_64-linux-gnu-libc):
  bug22.out, Error 1
  tst-mutex7.out, Error 1
  tst-mutex7a.out, Error 1
  tst-mutexpi7.out, Error 1
  tst-mutexpi7a.out, Error 1
  tst-once2.out, Error 1
  tst-setlocale3.out, Error 1
  TEST bug22.out:
  ret = -1
  ret = -1
  ret = -1
  ret = -1
  TEST tst-mutex7.out:
  creating thread 63 failed
  TEST tst-mutex7a.out:
  creating thread 63 failed
  TEST tst-mutexpi7.out:
  creating thread 63 failed
  TEST tst-mutexpi7a.out:
  creating thread 63 failed
  TEST tst-once2.out:
  creation of thread 63 failed
  TEST tst-setlocale3.out:
  malloc failure
  Encountered progressions that don't match expected failures:
  tst-backtrace6.out, Error 1
  tst-cpuclock2.out, Error 1
  tst-cputimer1.out, Error 1
  tst-mqueue5.out, Error 1
  tst-timer.out, Error 139
  tst-waitid.out, Error 1
  tst-writev.out, Error 1
  make: *** [/<>/stamp-dir/check_libc] Error 1

  == Fix commit/related ==
  https://sourceware.org/bugzilla/show_bug.cgi?id=19648
  
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=36234ceda21820d2f874067553e7faae763a40cf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/2063328/+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 2062667] Re: Fails on (and should be removed from) raspi desktop

2024-04-24 Thread Ubuntu QA Website

This bug has been reported on the Ubuntu ISO testing tracker.

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

** Tags added: iso-testing

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

Title:
  Fails on (and should be removed from) raspi desktop

Status in protection-domain-mapper package in Ubuntu:
  Confirmed
Status in qrtr package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  The protection-domain-mapper package (and qrtr-tools) are both
  installed by default on the Ubuntu Desktop for Raspberry Pi images,
  thanks to their inclusion in the desktop-minimal seed for arm64.
  However, there's no hardware that they target on these platforms, and
  the result is a permanently failed service (pd-mapper.service).

  It appears these were added to support the X13s laptop [1]. I've
  attempted to work around the issue by excluding these packages in the
  desktop-raspi seed (experimentally in my no-pd-mapper branch [2]) but
  this does not work (the packages still appear in the built images).
  Ideally, these packages should be moved into a hardware-specific seed
  for the X13s (and/or whatever other laptops need these things).
  Alternatively, at a bare minimum, the package should have some
  conditional that causes the service not to attempt to start when it's
  not on Qualcomm hardware.

  [1]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu-
  seeds/+git/ubuntu/commit/desktop-
  minimal?id=afe820cd49514896e96d02303298ed873d8d7f8a

  [2]: https://git.launchpad.net/~waveform/ubuntu-
  seeds/+git/ubuntu/commit/?id=875bddac19675f7e971f56d9c5d39a9912dc6e38

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2062667/+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 2062667] Re: Fails on (and should be removed from) raspi desktop

2024-04-24 Thread Dave Jones

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

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

Title:
  Fails on (and should be removed from) raspi desktop

Status in protection-domain-mapper package in Ubuntu:
  Confirmed
Status in qrtr package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  The protection-domain-mapper package (and qrtr-tools) are both
  installed by default on the Ubuntu Desktop for Raspberry Pi images,
  thanks to their inclusion in the desktop-minimal seed for arm64.
  However, there's no hardware that they target on these platforms, and
  the result is a permanently failed service (pd-mapper.service).

  It appears these were added to support the X13s laptop [1]. I've
  attempted to work around the issue by excluding these packages in the
  desktop-raspi seed (experimentally in my no-pd-mapper branch [2]) but
  this does not work (the packages still appear in the built images).
  Ideally, these packages should be moved into a hardware-specific seed
  for the X13s (and/or whatever other laptops need these things).
  Alternatively, at a bare minimum, the package should have some
  conditional that causes the service not to attempt to start when it's
  not on Qualcomm hardware.

  [1]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu-
  seeds/+git/ubuntu/commit/desktop-
  minimal?id=afe820cd49514896e96d02303298ed873d8d7f8a

  [2]: https://git.launchpad.net/~waveform/ubuntu-
  seeds/+git/ubuntu/commit/?id=875bddac19675f7e971f56d9c5d39a9912dc6e38

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2062667/+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 2062667] Re: Fails on (and should be removed from) raspi desktop

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

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

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

Title:
  Fails on (and should be removed from) raspi desktop

Status in protection-domain-mapper package in Ubuntu:
  Confirmed
Status in qrtr package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  The protection-domain-mapper package (and qrtr-tools) are both
  installed by default on the Ubuntu Desktop for Raspberry Pi images,
  thanks to their inclusion in the desktop-minimal seed for arm64.
  However, there's no hardware that they target on these platforms, and
  the result is a permanently failed service (pd-mapper.service).

  It appears these were added to support the X13s laptop [1]. I've
  attempted to work around the issue by excluding these packages in the
  desktop-raspi seed (experimentally in my no-pd-mapper branch [2]) but
  this does not work (the packages still appear in the built images).
  Ideally, these packages should be moved into a hardware-specific seed
  for the X13s (and/or whatever other laptops need these things).
  Alternatively, at a bare minimum, the package should have some
  conditional that causes the service not to attempt to start when it's
  not on Qualcomm hardware.

  [1]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu-
  seeds/+git/ubuntu/commit/desktop-
  minimal?id=afe820cd49514896e96d02303298ed873d8d7f8a

  [2]: https://git.launchpad.net/~waveform/ubuntu-
  seeds/+git/ubuntu/commit/?id=875bddac19675f7e971f56d9c5d39a9912dc6e38

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2062667/+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 2062667] Re: Fails on (and should be removed from) raspi desktop

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

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

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

Title:
  Fails on (and should be removed from) raspi desktop

Status in protection-domain-mapper package in Ubuntu:
  Confirmed
Status in qrtr package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  The protection-domain-mapper package (and qrtr-tools) are both
  installed by default on the Ubuntu Desktop for Raspberry Pi images,
  thanks to their inclusion in the desktop-minimal seed for arm64.
  However, there's no hardware that they target on these platforms, and
  the result is a permanently failed service (pd-mapper.service).

  It appears these were added to support the X13s laptop [1]. I've
  attempted to work around the issue by excluding these packages in the
  desktop-raspi seed (experimentally in my no-pd-mapper branch [2]) but
  this does not work (the packages still appear in the built images).
  Ideally, these packages should be moved into a hardware-specific seed
  for the X13s (and/or whatever other laptops need these things).
  Alternatively, at a bare minimum, the package should have some
  conditional that causes the service not to attempt to start when it's
  not on Qualcomm hardware.

  [1]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu-
  seeds/+git/ubuntu/commit/desktop-
  minimal?id=afe820cd49514896e96d02303298ed873d8d7f8a

  [2]: https://git.launchpad.net/~waveform/ubuntu-
  seeds/+git/ubuntu/commit/?id=875bddac19675f7e971f56d9c5d39a9912dc6e38

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2062667/+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 2062667] Re: Fails on (and should be removed from) raspi desktop

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

** Changed in: protection-domain-mapper (Ubuntu)
   Status: New => Confirmed

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

Title:
  Fails on (and should be removed from) raspi desktop

Status in protection-domain-mapper package in Ubuntu:
  Confirmed
Status in qrtr package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  The protection-domain-mapper package (and qrtr-tools) are both
  installed by default on the Ubuntu Desktop for Raspberry Pi images,
  thanks to their inclusion in the desktop-minimal seed for arm64.
  However, there's no hardware that they target on these platforms, and
  the result is a permanently failed service (pd-mapper.service).

  It appears these were added to support the X13s laptop [1]. I've
  attempted to work around the issue by excluding these packages in the
  desktop-raspi seed (experimentally in my no-pd-mapper branch [2]) but
  this does not work (the packages still appear in the built images).
  Ideally, these packages should be moved into a hardware-specific seed
  for the X13s (and/or whatever other laptops need these things).
  Alternatively, at a bare minimum, the package should have some
  conditional that causes the service not to attempt to start when it's
  not on Qualcomm hardware.

  [1]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu-
  seeds/+git/ubuntu/commit/desktop-
  minimal?id=afe820cd49514896e96d02303298ed873d8d7f8a

  [2]: https://git.launchpad.net/~waveform/ubuntu-
  seeds/+git/ubuntu/commit/?id=875bddac19675f7e971f56d9c5d39a9912dc6e38

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/protection-domain-mapper/+bug/2062667/+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 2063371] Re: protection-domain-mapper and qrtr-tools should not be in ubuntu-desktop-raspi

2024-04-24 Thread Paul Larson

*** This bug is a duplicate of bug 2062667 ***
https://bugs.launchpad.net/bugs/2062667

** This bug has been marked a duplicate of bug 2062667
   Fails on (and should be removed from) raspi desktop

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

Title:
  protection-domain-mapper and qrtr-tools should not be in  ubuntu-
  desktop-raspi

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  I noticed from our automated certification tests on raspberry pi Noble
  desktop images that the pd-mapper service was failing on boot. It
  looks like this is a package only intended for qualcomm desktop
  system, and not something that is needed by raspberry pi.

  It looks like this got added with
  https://code.launchpad.net/~xnox/ubuntu-
  seeds/+git/ubuntu/+merge/453233

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2063371/+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 2063332] Re: Multiple problems Ubuntu 24.04 with Qt5

2024-04-24 Thread Dmitry Shachnev

What you describe sounds like an effect of switching from X11 to
Wayland, not a regression in Qt.

In X11, the window decorations can be drawn either by the window manager
or by the application itself. Qt relied on window manager, so the
decorations looked uniform.

In Wayland, there is no choice, and Qt draws its own window decorations,
which may be different from GNOME ones. If you signed into a Wayland
session in Ubuntu 22.04, you would likely get the same effect.

There is a third-party package which may make things better for Qt
applications in GNOME: qgnomeplatform-qt5. After installing it, try
running your application with QT_QPA_PLATFORMTHEME=gnome environment
variable.

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

Title:
Multiple problems Ubuntu 24.04 with Qt5

Status in qtbase-opensource-src package in Ubuntu:
New

Bug description:
After the upgrade to the 24.04 beta Qt5 UI is not at its best. Please,
notice that all this functionality is working on 22.04.

1. Windows controls settings from Gnome are not applied
When you set the Windows Title bar buttons to Placement Left, then Qt apps
ignore this setting. The default gt4 apps behave properly and place the buttons
to the left.

2. Windows actions like double click to maximize from settings also do
not with in the Qt5 apps unlike in gt4 apps.

3. Several keyboard shortcuts are passed differently to Qt5 apps.
The key "Ctrl+Period" is not passed to the qt app at all
The key "Ctrl+~" is passed as "Ctrl+0"
The key "Shift+Alt+F7" is also not working
This means some different handling is applied in Qt5 apps

4. If you use the env var "export QT_QPA_PLATFORM=xcb" and start the
Qt5 app, then it all works properly. The windows controls are on the
right side, you can use double click the title bar to maximize and
also the shortcuts are working fine. However, in such scenario no app
starts fullscreen. It starts in a positioned window (the position is
remembered) instead even if you maximized the window before you exited
it.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: libqt5core5t64 5.15.13+dfsg-1ubuntu1
ProcVersionSignature: Ubuntu 6.8.0-28.28-generic 6.8.1
Uname: Linux 6.8.0-28-generic x86_64
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 24 14:20:24 2024
InstallationDate: Installed on 2020-05-12 (1443 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: qtbase-opensource-src
UpgradeStatus: Upgraded to noble on 2024-04-20 (4 days ago)
modified.conffile..etc.init.d.apport: [modified]
mtime.conffile..etc.init.d.apport: 2024-04-19T01:50:32

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/2063332/+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 2060311] Re: Setting "optional: true" to overcome he timeout "Job systemd-networkd-wait-online" does no longer work with latest noble image

2024-04-24 Thread Lukas Märdian

** Changed in: netplan
   Status: In Progress => Fix Committed

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

Title:
  Setting "optional: true" to overcome he timeout "Job systemd-networkd-
  wait-online" does no longer work with latest noble image

Status in Netplan:
  Fix Committed
Status in Ubuntu on IBM z Systems:
  Fix Released
Status in netplan.io package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Invalid
Status in netplan.io source package in Noble:
  Fix Released
Status in systemd source package in Noble:
  Invalid

Bug description:
  Especially on s390x (but not limited to s390x) it's often the case that a 
system has network devices that are not necessarily connected during boot-up 
and one gets such a 2 min timeout:
  "Job systemd-networkd-wait-online. Start running (1min 59s / no limit)"

  In the past I could avoid that by setting "optional: true" post-install (no 
perfect, but worked),
  but this does no longer seem to work using the latest noble ISO image (Apr 
5th).

  Setting 'optional: true' in /etc/netplan/50-cloud-init.yaml looks like
  this for me:

  # This file is generated from information provided by the datasource.  Changes
  # to it will not persist across an instance reboot.  To disable cloud-init's
  # network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  ethernets:
  enP1p0s0:
  optional: true
  dhcp4: true
  enP1p0s0d1:
  optional: true
  dhcp4: true
  enP2p0s0:
  optional: true
  dhcp4: true
  enP2p0s0d1:
  optional: true
  dhcp4: true
  encc000: {}
  version: 2
  vlans:
  encc000.2653:
  addresses:
  - 10.11.12.15/24
  gateway4: 10.11.12.1
  id: 2653
  link: encc000
  nameservers:
  addresses:
  - 10.11.12.1

  ... can be set fine (also --dry-run does not moan, except about
  dhcp4).

  This worked in the past on noble, but also on older Ubuntu releases
  like jammy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/2060311/+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 2063371] [NEW] protection-domain-mapper and qrtr-tools should not be in ubuntu-desktop-raspi

2024-04-24 Thread Paul Larson

Public bug reported:

I noticed from our automated certification tests on raspberry pi Noble
desktop images that the pd-mapper service was failing on boot. It looks
like this is a package only intended for qualcomm desktop system, and
not something that is needed by raspberry pi.

It looks like this got added with
https://code.launchpad.net/~xnox/ubuntu-seeds/+git/ubuntu/+merge/453233

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

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

Title:
  protection-domain-mapper and qrtr-tools should not be in  ubuntu-
  desktop-raspi

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  I noticed from our automated certification tests on raspberry pi Noble
  desktop images that the pd-mapper service was failing on boot. It
  looks like this is a package only intended for qualcomm desktop
  system, and not something that is needed by raspberry pi.

  It looks like this got added with
  https://code.launchpad.net/~xnox/ubuntu-
  seeds/+git/ubuntu/+merge/453233

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2063371/+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 2063161] Re: PHP LDAP extension is missing a dependency

2024-04-24 Thread Athos Ribeiro

noble:

php8.3-ldap depends on libldap2;
libldap2 RECOMMENDS libldap-common;

focal:

php7.4-ldap depends on libldap-2.4-2;
libldap-2.4-2 DEPENDS on libldap-common;

in both cases, libldap-common only ships the /etc/ldap/ldap.conf
configuration file, which sets TLS_CACERT.

The openldap chagelog has the following entry:

openldap (2.4.25-1) unstable; urgency=low
...
  * Add debian specific patch for ldap.conf. Add TLS_CACERT option and set it
by default to /etc/ssl/certs/ca-certificates.crt (Closes: #555409, #616703)
...
 -- Matthijs Möhlmann   Mon, 11 Apr 2011 22:10:14 +0200

Which explains why we have the TLS_CACERT entry in the configuration file and 
why things work out of the box for php-ldap. The following bugs should give 
full context on the matter:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=555409
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=616703

Then, there is the following entry in the openldap package changelog;

openldap (2.4.51+dfsg-1) unstable; urgency=medium
...
  * Relax libldap's dependency on libldap-common to Recommends.
This is intended to mitigate the impact of bug #915948 in the case where
the arch:all build is delayed for so long that the old libldap-common
disappears. Previously, a delayed arch:all build could become
BD-Uninstallable if new amd64 binaries were published before the arch:all
build starts, due to the transitive build-dependency on libldap.
Although libldap works fine without libldap-common, in normal
installations it is still recommended to install libldap-common.
...
 -- Ryan Tandy   Sun, 23 Aug 2020 11:09:57 -0700

Which was implemented to fix http://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=915948.

The consequence here is that when the package is installed with --no-
install-recommends, TLS_CACERT is not set and you see the described
error (which is known to be a not ideal error message as described in
the debian bug linked above (#555409).

Still, in https://www.debian.org/doc/debian-policy/ch-
relationships.html, the Debian policy states that:

"Recommends declares a strong, but not absolute, dependency. The
Recommends field should list packages that would be found together with
this one in all but unusual installations."

Which is reasonable given the statement in the changelog bit mentioned
above ("libldap works fine without libldap-common").

However, this is a workaround for a bug in dak. Since we use launchpad,
we could verify if we also suffer of similar issues and then, in case
launchpad is not affected, consider reverting this change in a Ubuntu.

Once could also argue considering fixing this in php-ldap by also
depending on libldap-common. IMHO, that would be overstretching AND
undoing the openldap patch indirectly and would need to be done in other
packages as well for consistency. i.e., this is a bad option.

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

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

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

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

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

** Changed in: php-defaults (Ubuntu)
   Status: New => Opinion

** Tags added: server-todo

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

Title:
  PHP LDAP extension is missing a dependency

Status in openldap package in Ubuntu:
  Triaged
Status in php-defaults package in Ubuntu:
  Opinion

Bug description:
  When php-ldap package is installed with --no-install-recommends, the
  libldap-common package is not installed, which results in TLS
  certificate validation failure with useless message: "PHP Warning:
  ldap_bind(): Unable to bind to server: Can't contact LDAP server".

  Only with the debugging enabled I could see a bit more relevant
  information "TLS: peer cert untrusted or revoked (0x42)", but that
  information is also misleading as the server certificate is valid.

  Full log of actions to reproduce the issue (valid for Ubuntu 22.04 and
  24.04) is in the attached "Ubuntu PHP LDAP bug.txt". It also includes
  the happy path.

  I believe that when php-ldap package is installed with --no-install-
  recommends option, the libldap-common package should be installed as
  well.

  N.B. That this was working as expected in Ubuntu 20.04 .

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/2063161/+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 2063369] [NEW] e2image reports invalid argument when used with big partitions

2024-04-24 Thread Jaromír Cápík

Public bug reported:

It seems e2image is unable to work correctly with large filesystems. I
get the following error with etx4 on top of 48TB RAID5 array.

# e2image -pr /dev/md3 md3.e2i
e2image 1.46.5 (30-Dec-2021)
Scanning inodes...
Copying 802818 / 1547571 blocks (52%) 00:02:21 remaining at 20.50 
MB/sseek_relative: Invalid argument

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

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

Title:
  e2image reports invalid argument when used with big partitions

Status in e2fsprogs package in Ubuntu:
  New

Bug description:
  It seems e2image is unable to work correctly with large filesystems. I
  get the following error with etx4 on top of 48TB RAID5 array.

  # e2image -pr /dev/md3 md3.e2i
  e2image 1.46.5 (30-Dec-2021)
  Scanning inodes...
  Copying 802818 / 1547571 blocks (52%) 00:02:21 remaining at 20.50 
MB/sseek_relative: Invalid argument

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/2063369/+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 1957024] Re: pam-mkhomedir does not honor private home directories

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

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

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

Title:
  pam-mkhomedir does not honor private home directories

Status in pam package in Ubuntu:
  Confirmed

Bug description:
  As reported in https://discourse.ubuntu.com/t/private-home-
  directories-for-ubuntu-21-04-onwards/19533/13:

  A common situation is to have a central set of users (e.g. in LDAP)
  and use pam_mkhomedir.so to create the home directory when the user
  first logs in.

  These changes do not cover this situation. The default configuration
  of pam_mkhomedir.so will result in a home directory created with 0755
  permissions.

  To make pam_mkhomedir.so create a home directory by default with
  permissions consistent with the other tools then a umask argument can
  be added to the pam_mkhomedir.so module in the file /usr/share/pam-
  configs/mkhomedir. I believe this would have to be done before
  enabling the module. The file is part of the libpam-modules package.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pam/+bug/1957024/+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 2061726] Re: rsyslog apparmor denial on reading /proc/sys/net/ipv6/conf/all/disable_ipv6

** Tags added: rls-nn-incoming

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

Title:
  rsyslog apparmor denial on reading
  /proc/sys/net/ipv6/conf/all/disable_ipv6

Status in rsyslog package in Ubuntu:
  New

Bug description:
  One of our Cockpit integration tests [1] spotted an AppArmor
  regression in rsyslogd. This is coincidental, the test passes and it
  doesn't do anything with rsyslogd -- just something happens to happen
  in the background to trigger this (and I can actually reproduce it
  locally quite reliably).

  
  Mar 08 10:48:20 m1.cockpit.lan systemd[1]: dpkg-db-backup.service: 
Deactivated successfully.
  Mar 08 10:48:20 m1.cockpit.lan systemd[1]: Finished dpkg-db-backup.service - 
Daily dpkg database backup service.
  Mar 08 10:48:20 m1.cockpit.lan systemd[1]: rsyslog.service: Sent signal 
SIGHUP to main process 752 (rsyslogd) on client request.
  Mar 08 10:48:20 m1.cockpit.lan kernel: audit: type=1400 
audit(1615200500.418:125): apparmor="DENIED" operation="open" class="file" 
profile="rsyslogd" name="/proc/sys/net/ipv6/conf/all/disable_ipv6" pid=752 
comm="rsyslogd" requested_mask="r" denied_mask="r" fsuid=102 ouid=0
  Mar 08 10:48:20 m1.cockpit.lan kernel: audit: type=1400 
audit(1615200500.418:126): apparmor="DENIED" operation="open" class="file" 
profile="rsyslogd" name="/proc/sys/net/ipv6/conf/all/disable_ipv6" pid=752 
comm="rsyslogd" requested_mask="r" denied_mask="r" fsuid=102 ouid=0

  
  This happens on current Ubuntu 24.04 LTS noble devel, rsyslog 
8.2312.0-3ubuntu8 and apparmor 4.0.0-beta3-0ubuntu3.

  [1] 
https://cockpit-logs.us-east-1.linodeobjects.com/pull-20317-ce39e07e-20240415-204952-ubuntu-stable-other/log.html#152
  [2] 
https://cockpit-logs.us-east-1.linodeobjects.com/pull-20317-ce39e07e-20240415-204952-ubuntu-stable-other/TestHistoryMetrics-testEvents-ubuntu-stable-127.0.0.2-2901-FAIL.log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/2061726/+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 2063349] Re: systemd-coredump handler does not forward the crash to the container

2024-04-24 Thread Nick Rosbrook

Okay. The title should be changed then -- systemd-coredump on the host
attempts to forward the crash to the container, but finds that systemd-
coredump is not present in the container, so it falls back to keeping it
on the host.

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

Title:
  systemd-coredump handler does not forward the crash to the container

Status in apport package in Ubuntu:
  Triaged

Bug description:
  Steps to reproduce:
  1. install systemd-coredump on the host
  2. open a shell on a noble container
  2.1 machinectl pull-raw 
"http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img; 
noble
  2.2 machinectl start noble
  2.3 machinectl shell noble
  3. install chaos-marmosets inside the container (# apt install 
chaos-marmosets)
  4. generate a crash inside the container (# divide-by-zero)

  Observed behaviour: The .crash file is present on the host /var/crash
  Expected behaviour: The .crash file should be present inside the container 
/var/crash

  Note: Here is how you can enable Host Network on the container
  https://wiki.archlinux.org/title/systemd-nspawn#Use_host_networking

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: apport 2.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  NonfreeKernelModules: zfs
  ApportLog:
   INFO: apport (pid 126611) 2024-04-24 16:34:39,226: executable: 
/usr/bin/divide-by-zero (command line "divide-by-zero")
   INFO: apport (pid 126611) 2024-04-24 16:34:39,664: wrote report 
/var/crash/_usr_bin_divide-by-zero.1000.crash
   INFO: apport (pid 127435) 2024-04-24 16:41:16,322: executable: 
/usr/bin/divide-by-zero (command line "divide-by-zero")
   INFO: apport (pid 127435) 2024-04-24 16:41:16,758: wrote report 
/var/crash/_usr_bin_divide-by-zero.297664512.crash
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 24 17:03:02 2024
  InstallationDate: Installed on 2024-04-18 (6 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240418)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2063349/+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 2060326] Re: unnattended upgrades stuck burning 100% cpu

possible duplicate https://bugs.launchpad.net/ubuntu/+source/unattended-
upgrades/+bug/2063094

** Tags added: rls-nn-incoming

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

Title:
  unnattended upgrades stuck burning 100% cpu

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  For the last hour or so, unattended upgrades has been stuck burning
  100% of a cpu.

  series: noble
  version: 2.9.1+nmu4ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/2060326/+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 2061825] Re: [SRU] ucf fails to work for local diversions on Jammy

2024-04-24 Thread Ponnuvel Palaniyappan

Thanks, Heitor. I'll remember to run `update-maintainer` going forward!

Re. Focal: The syntax error and relevant code was introduced in 3.0040
whereas Focal is using older ucf. Thus Focal is unaffected. Likewise
Lunar/Mantic/Noble have the fixed version already. So this is a Jammy-
only backport.

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

Title:
  [SRU] ucf fails to work for local diversions on Jammy

Status in ucf package in Ubuntu:
  Fix Released
Status in ucf source package in Jammy:
  In Progress

Bug description:
  [ Impact ]

  When a dpkg-diversion is used to setup a package diversion and ucf for 
managing
  the configuration files for chrony package, the postinst script of ucf fails
  when installing chrony.

  This issue isn't specific to chrony but can happen for any package whose
  config files are managed by ucf.

  This affects users on Jammy who use ucf. Newer versions of ucf have this bug
  fixed already.

  [ Test Plan ]

  1. Create a Jammy container or VM
  2. Setup a diversion for chrony.conf: dpkg-divert --package chrony --add 
--rename --divert /etc/chrony/chrony.conf.custom /etc/chrony/chrony.conf
  3. Install chrony: apt install chrony -y
  4. Notice the postinst script fail with syntax errors such as:
  ```
  Preparing to unpack .../chrony_4.2-2ubuntu2_amd64.deb ...
  Unpacking chrony (4.2-2ubuntu2) ...
  Setting up chrony (4.2-2ubuntu2) ...
  /usr/bin/ucf: 444: [: missing ]
  grep: ]: No such file or directory
  /usr/bin/ucf: 444: [: missing ]
  grep: ]: No such file or directory
  ```
  5. Install the package with the fix from the PPA: 
https://launchpad.net/~pponnuvel/+archive/ubuntu/ucf-jammy (to be replaced with 
the package from the -proposed pocket)
  6. Repeat the same from steps 1 to 4 and notice no failures at step4.

  [ Where problems could occur ]

  Can further introduce similar bugs if the patch contains similar syntax
  errors. Consequently local diversion may not take effect for packages
  using ucf to manage configuration files.

  [ Other Info ]
   
  Upstream bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979354

  It's been fixed in version ucf/3.0043+nmu1. Lunar/Mantic/Noble all have the
  ucf version with this patch.

  Affects Jammy only and thus backported to only Jammy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ucf/+bug/2061825/+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 2063349] Re: systemd-coredump handler does not forward the crash to the container

>Did you verify that systemd-coredump is installed in the container?

It works when systemd-coredump is installed inside the container. This
report is for the default noble container. My understanding is that in
no case should the .crash file be on the host when a crash occurs inside
a container. I guess apport should forward the crash to the container in
this case.

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

Title:
  systemd-coredump handler does not forward the crash to the container

Status in apport package in Ubuntu:
  Triaged

Bug description:
  Steps to reproduce:
  1. install systemd-coredump on the host
  2. open a shell on a noble container
  2.1 machinectl pull-raw 
"http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img; 
noble
  2.2 machinectl start noble
  2.3 machinectl shell noble
  3. install chaos-marmosets inside the container (# apt install 
chaos-marmosets)
  4. generate a crash inside the container (# divide-by-zero)

  Observed behaviour: The .crash file is present on the host /var/crash
  Expected behaviour: The .crash file should be present inside the container 
/var/crash

  Note: Here is how you can enable Host Network on the container
  https://wiki.archlinux.org/title/systemd-nspawn#Use_host_networking

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: apport 2.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  NonfreeKernelModules: zfs
  ApportLog:
   INFO: apport (pid 126611) 2024-04-24 16:34:39,226: executable: 
/usr/bin/divide-by-zero (command line "divide-by-zero")
   INFO: apport (pid 126611) 2024-04-24 16:34:39,664: wrote report 
/var/crash/_usr_bin_divide-by-zero.1000.crash
   INFO: apport (pid 127435) 2024-04-24 16:41:16,322: executable: 
/usr/bin/divide-by-zero (command line "divide-by-zero")
   INFO: apport (pid 127435) 2024-04-24 16:41:16,758: wrote report 
/var/crash/_usr_bin_divide-by-zero.297664512.crash
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 24 17:03:02 2024
  InstallationDate: Installed on 2024-04-18 (6 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240418)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2063349/+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 2063349] Re: systemd-coredump handler does not forward the crash to the container

2024-04-24 Thread Benjamin Drung

Nick, it works if you have systemd-coredump installed in the container.

If you do not have systemd-coredump installed in the container, apport
on the host should do the forwarding.

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

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

Title:
  systemd-coredump handler does not forward the crash to the container

Status in apport package in Ubuntu:
  Triaged

Bug description:
  Steps to reproduce:
  1. install systemd-coredump on the host
  2. open a shell on a noble container
  2.1 machinectl pull-raw 
"http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img; 
noble
  2.2 machinectl start noble
  2.3 machinectl shell noble
  3. install chaos-marmosets inside the container (# apt install 
chaos-marmosets)
  4. generate a crash inside the container (# divide-by-zero)

  Observed behaviour: The .crash file is present on the host /var/crash
  Expected behaviour: The .crash file should be present inside the container 
/var/crash

  Note: Here is how you can enable Host Network on the container
  https://wiki.archlinux.org/title/systemd-nspawn#Use_host_networking

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: apport 2.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  NonfreeKernelModules: zfs
  ApportLog:
   INFO: apport (pid 126611) 2024-04-24 16:34:39,226: executable: 
/usr/bin/divide-by-zero (command line "divide-by-zero")
   INFO: apport (pid 126611) 2024-04-24 16:34:39,664: wrote report 
/var/crash/_usr_bin_divide-by-zero.1000.crash
   INFO: apport (pid 127435) 2024-04-24 16:41:16,322: executable: 
/usr/bin/divide-by-zero (command line "divide-by-zero")
   INFO: apport (pid 127435) 2024-04-24 16:41:16,758: wrote report 
/var/crash/_usr_bin_divide-by-zero.297664512.crash
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 24 17:03:02 2024
  InstallationDate: Installed on 2024-04-18 (6 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240418)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2063349/+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 2063349] Re: systemd-coredump handler does not forward the crash to the container

2024-04-24 Thread Nick Rosbrook

root@selected-slug:~# machinectl pull-raw 
"http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img; 
noble
Enqueued transfer job 1. Press C-c to continue download in background.
Pulling 
'http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img', 
saving as 'noble'.
Downloading 453.0M for 
http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img.
HTTP request to 
http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.roothash.p7s
 failed with code 404.
Root hash signature file could not be retrieved, proceeding without.
HTTP request to 
http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.verity 
failed with code 404.
Verity integrity file could not be retrieved, proceeding without.
HTTP request to 
http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.nspawn 
failed with code 404.
Settings file could not be retrieved, proceeding without.
Downloading 833B for 
http://cloud-images.ubuntu.com/noble/current/SHA256SUMS.gpg.
Acquired 833B.
Download of http://cloud-images.ubuntu.com/noble/current/SHA256SUMS.gpg 
complete.
HTTP request to 
http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.roothash
 failed with code 404.
Root hash file could not be retrieved, proceeding without.
Downloading 6.9K for http://cloud-images.ubuntu.com/noble/current/SHA256SUMS.
Got 37% of http://cloud-images.ubuntu.com/noble/current/SHA256SUMS.
Acquired 6.9K.
Download of http://cloud-images.ubuntu.com/noble/current/SHA256SUMS complete.
Got 1% of 
http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img. 
2min 13s left at 3.3M/s.
Got 5% of 
http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img. 
41s left at 10.4M/s.
Got 11% of 
http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img. 
26s left at 14.9M/s.
Got 16% of 
http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img. 
21s left at 17.5M/s.
Got 22% of 
http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img. 
18s left at 19.0M/s.
Got 28% of 
http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img. 
16s left at 20.1M/s.
Got 33% of 
http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img. 
14s left at 20.6M/s.
Got 39% of 
http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img. 
13s left at 21.1M/s.
Got 44% of 
http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img. 
11s left at 21.3M/s.
Got 50% of 
http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img. 
10s left at 21.8M/s.
Got 53% of 
http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img. 
9s left at 21.3M/s.
Got 58% of 
http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img. 
8s left at 21.4M/s.
Got 64% of 
http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img. 
7s left at 21.7M/s.
Got 69% of 
http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img. 
6s left at 21.9M/s.
Got 75% of 
http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img. 
4s left at 22.2M/s.
Got 81% of 
http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img. 
3s left at 22.4M/s.
Got 87% of 
http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img. 
2s left at 22.6M/s.
Got 93% of 
http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img. 
1s left at 22.7M/s.
Got 98% of 
http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img. 
306ms left at 22.8M/s.
Acquired 453.0M.
Download of 
http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img 
complete.
SHA256 checksum of 
http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img is 
valid.
gpg: Signature made Wed Apr 24 00:22:50 2024 UTC
gpg:using RSA key D2EB44626FDDC30B513D5BB71A5D6C4C7DB87C81
gpg: Good signature from "UEC Image Automatic Signing Key " 
[unknown]
gpg: WARNING: Using untrusted key!
Signature verification succeeded.
Unpacking QCOW2 file.
Created new local image 'noble'.
Operation completed successfully.
Exiting.
root@selected-slug:~# machinectl start noble
root@selected-slug:~# machinectl shell noble
Connected to machine noble. Press ^] three times within 1s to exit session.

### In the container now ###

root@ubuntu:~# apt update && apt install systemd-coredump chaos-marmosets -y
Get:1 http://archive.ubuntu.com/ubuntu noble InRelease [256 kB]
Get:2 http://archive.ubuntu.com/ubuntu noble-updates InRelease [89.7 kB]
  
Get:3 http://archive.ubuntu.com/ubuntu noble-backports InRelease [90.8 kB]
Hit:4 http://security.ubuntu.com/ubuntu noble-security InRelease
Get:5 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages [1403 kB]
Get:6 http://archive.ubuntu.com/ubuntu noble/universe amd64 Packages [15.5

[Touch-packages] [Bug 1869655] Re: Boot animations start too late to be useful

2024-04-24 Thread Mario Limonciello

> No longer in progress. You can get to 100% fixed by adding kernel
parameter 'plymouth.use-simpledrm' but I'm not totally sure that's
something everyone will want.

The main reasons that can be problematic are rotation right?  I wonder
if the right way to go about it is a heuristic within plymouth to decide
whether it can/should output.  For example if there are no rotation
sensors on the machine, or by looking at the orientation on them?

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

Title:
  Boot animations start too late to be useful

Status in Plymouth:
  New
Status in grub2 package in Ubuntu:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in plymouth package in Ubuntu:
  Triaged

Bug description:
  Boot animations start too late to be useful

  Modern systems spend all their boot time (a couple of seconds)
  decompressing the kernel. During that time the user only sees the
  static BIOS logo (ACPI BGRT). Then when Plymouth can finally start
  animating, the startup process is already finished and there's
  virtually no time left to show any useful animations.

  This could be fixed in:

    grub: By adding a splash under the BIOS logo to show some progress
  _before_ a Linux kernel is even started

  and/or

    plymouth: By preferencing legacy framebuffer devices (like EFI) over
  DRM, if we find those are available a few seconds sooner. That would
  also fix bug 1868240 completely, and bug 1836858 mostly as the flicker
  moves to when the login screen starts.

To manage notifications about this bug go to:
https://bugs.launchpad.net/plymouth/+bug/1869655/+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 2063349] Re: systemd-coredump handler does not forward the crash to the container

2024-04-24 Thread Nick Rosbrook

Did you verify that systemd-coredump is installed in the container?

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

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

Title:
  systemd-coredump handler does not forward the crash to the container

Status in apport package in Ubuntu:
  Incomplete

Bug description:
  Steps to reproduce:
  1. install systemd-coredump on the host
  2. open a shell on a noble container
  2.1 machinectl pull-raw 
"http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img; 
noble
  2.2 machinectl start noble
  2.3 machinectl shell noble
  3. install chaos-marmosets inside the container (# apt install 
chaos-marmosets)
  4. generate a crash inside the container (# divide-by-zero)

  Observed behaviour: The .crash file is present on the host /var/crash
  Expected behaviour: The .crash file should be present inside the container 
/var/crash

  Note: Here is how you can enable Host Network on the container
  https://wiki.archlinux.org/title/systemd-nspawn#Use_host_networking

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: apport 2.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  NonfreeKernelModules: zfs
  ApportLog:
   INFO: apport (pid 126611) 2024-04-24 16:34:39,226: executable: 
/usr/bin/divide-by-zero (command line "divide-by-zero")
   INFO: apport (pid 126611) 2024-04-24 16:34:39,664: wrote report 
/var/crash/_usr_bin_divide-by-zero.1000.crash
   INFO: apport (pid 127435) 2024-04-24 16:41:16,322: executable: 
/usr/bin/divide-by-zero (command line "divide-by-zero")
   INFO: apport (pid 127435) 2024-04-24 16:41:16,758: wrote report 
/var/crash/_usr_bin_divide-by-zero.297664512.crash
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 24 17:03:02 2024
  InstallationDate: Installed on 2024-04-18 (6 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240418)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2063349/+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 2061825] Re: [SRU] ucf fails to work for local diversions on Jammy

2024-04-24 Thread Heitor Alves de Siqueira

Hi Pon,

thanks for the revised debdiff! This seems to be a non-quilt package, so
your approach of directly patching the ucf/ucfr scripts is correct. The
only thing missing is running the update-maintainer script, as the
ubuntu1 version requires having an ubuntu.com address on the maintainers
field. This is something a sponsor can run easily, so don't worry about
fixing it for now (but feel free to do it for future debdiffs!).

Before uploading this, I'd like to check about Focal; is that release
affected at all? If it is, any reason why we shouldn't patch it?

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

Title:
  [SRU] ucf fails to work for local diversions on Jammy

Status in ucf package in Ubuntu:
  Fix Released
Status in ucf source package in Jammy:
  In Progress

Bug description:
  [ Impact ]

  When a dpkg-diversion is used to setup a package diversion and ucf for 
managing
  the configuration files for chrony package, the postinst script of ucf fails
  when installing chrony.

  This issue isn't specific to chrony but can happen for any package whose
  config files are managed by ucf.

  This affects users on Jammy who use ucf. Newer versions of ucf have this bug
  fixed already.

  [ Test Plan ]

  1. Create a Jammy container or VM
  2. Setup a diversion for chrony.conf: dpkg-divert --package chrony --add 
--rename --divert /etc/chrony/chrony.conf.custom /etc/chrony/chrony.conf
  3. Install chrony: apt install chrony -y
  4. Notice the postinst script fail with syntax errors such as:
  ```
  Preparing to unpack .../chrony_4.2-2ubuntu2_amd64.deb ...
  Unpacking chrony (4.2-2ubuntu2) ...
  Setting up chrony (4.2-2ubuntu2) ...
  /usr/bin/ucf: 444: [: missing ]
  grep: ]: No such file or directory
  /usr/bin/ucf: 444: [: missing ]
  grep: ]: No such file or directory
  ```
  5. Install the package with the fix from the PPA: 
https://launchpad.net/~pponnuvel/+archive/ubuntu/ucf-jammy (to be replaced with 
the package from the -proposed pocket)
  6. Repeat the same from steps 1 to 4 and notice no failures at step4.

  [ Where problems could occur ]

  Can further introduce similar bugs if the patch contains similar syntax
  errors. Consequently local diversion may not take effect for packages
  using ucf to manage configuration files.

  [ Other Info ]
   
  Upstream bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979354

  It's been fixed in version ucf/3.0043+nmu1. Lunar/Mantic/Noble all have the
  ucf version with this patch.

  Affects Jammy only and thus backported to only Jammy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ucf/+bug/2061825/+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 2063349] [NEW] systemd-coredump handler does not forward the crash to the container

Public bug reported:

Steps to reproduce:
1. install systemd-coredump on the host
2. open a shell on a noble container
2.1 machinectl pull-raw 
"http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img; 
noble
2.2 machinectl start noble
2.3 machinectl shell noble
3. install chaos-marmosets inside the container (# apt install chaos-marmosets)
4. generate a crash inside the container (# divide-by-zero)

Observed behaviour: The .crash file is present on the host /var/crash
Expected behaviour: The .crash file should be present inside the container 
/var/crash

Note: Here is how you can enable Host Network on the container
https://wiki.archlinux.org/title/systemd-nspawn#Use_host_networking

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: apport 2.28.1-0ubuntu2
ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
Uname: Linux 6.8.0-22-generic x86_64
NonfreeKernelModules: zfs
ApportLog:
 INFO: apport (pid 126611) 2024-04-24 16:34:39,226: executable: 
/usr/bin/divide-by-zero (command line "divide-by-zero")
 INFO: apport (pid 126611) 2024-04-24 16:34:39,664: wrote report 
/var/crash/_usr_bin_divide-by-zero.1000.crash
 INFO: apport (pid 127435) 2024-04-24 16:41:16,322: executable: 
/usr/bin/divide-by-zero (command line "divide-by-zero")
 INFO: apport (pid 127435) 2024-04-24 16:41:16,758: wrote report 
/var/crash/_usr_bin_divide-by-zero.297664512.crash
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 24 17:03:02 2024
InstallationDate: Installed on 2024-04-18 (6 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240418)
PackageArchitecture: all
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  systemd-coredump handler does not forward the crash to the container

Status in apport package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. install systemd-coredump on the host
  2. open a shell on a noble container
  2.1 machinectl pull-raw 
"http://cloud-images.ubuntu.com/noble/current/noble-server-cloudimg-amd64.img; 
noble
  2.2 machinectl start noble
  2.3 machinectl shell noble
  3. install chaos-marmosets inside the container (# apt install 
chaos-marmosets)
  4. generate a crash inside the container (# divide-by-zero)

  Observed behaviour: The .crash file is present on the host /var/crash
  Expected behaviour: The .crash file should be present inside the container 
/var/crash

  Note: Here is how you can enable Host Network on the container
  https://wiki.archlinux.org/title/systemd-nspawn#Use_host_networking

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: apport 2.28.1-0ubuntu2
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  NonfreeKernelModules: zfs
  ApportLog:
   INFO: apport (pid 126611) 2024-04-24 16:34:39,226: executable: 
/usr/bin/divide-by-zero (command line "divide-by-zero")
   INFO: apport (pid 126611) 2024-04-24 16:34:39,664: wrote report 
/var/crash/_usr_bin_divide-by-zero.1000.crash
   INFO: apport (pid 127435) 2024-04-24 16:41:16,322: executable: 
/usr/bin/divide-by-zero (command line "divide-by-zero")
   INFO: apport (pid 127435) 2024-04-24 16:41:16,758: wrote report 
/var/crash/_usr_bin_divide-by-zero.297664512.crash
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 24 17:03:02 2024
  InstallationDate: Installed on 2024-04-18 (6 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240418)
  PackageArchitecture: all
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2063349/+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 2061214] Re: [SRU] Software Sources is not compatible with deb822

2024-04-24 Thread Julian Andres Klode

Yeah sorry folks this was a bit awkward, to avoid respinning other
images we temporarily spun out software-properties-qt into its own
package (0.99.48.1) and fixed it there, and hence there was no bug
closure or anything. This will fold back into the main package in a
zero-day SRU in 0.99.49.

** Also affects: software-properties-qt (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: software-properties-qt (Ubuntu Noble)
   Status: New => Fix Released

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

Title:
  [SRU] Software Sources is not compatible with deb822

Status in software-properties package in Ubuntu:
  Confirmed
Status in software-properties-qt package in Ubuntu:
  Fix Released
Status in software-properties source package in Noble:
  Confirmed
Status in software-properties-qt source package in Noble:
  Fix Released

Bug description:
  [ Impact ]

  Ubuntu 24.04 now uses deb822 to represent software sources for deb
  packages, instead of /etc/apt/sources.list. The complete rationale for
  this change can be found here: https://discourse.ubuntu.com/t/spec-
  apt-deb822-sources-by-default/29333

  software-properties has two graphical frontends for editing these
  software sources, one is GTK-based and the other is Qt-based. When the
  underlying change to deb822 sources was made, the GTK-based frontend
  and the DBus backend interface gained support.

  The original bug report shown below informed us of the lack of deb822
  support in the Qt frontend, which results in a broken, non-functional
  interface when attempting to view or edit most values on the first two
  tabs. The fix for this is to implement a Qt dialog for deb822 sources
  that somewhat matches the existing GTK interface.

  [ Test Plan ]

  Install software-properties-qt 0.99.48 or earlier.

  Reproducing the bug:
   1. From the menu, open Software Sources. Alternatively, run `sudo -E 
software-properties-qt` in a terminal.
   2. Observe that all four checkboxes on the Ubuntu Software tab (main, 
universe, restricted, and multiverse) are unchecked.
   3. Move to the Other Software tab and observe that there are no items in the 
list.

  Upgrade to software-properties-qt 0.99.49.

  Intended functionality:
   1. From the menu, open Software Sources. Alternatively, run `sudo -E 
software-properties-qt` in a terminal.
   2. Observe that one or more checkboxes on the Ubuntu Software tab 
(representing main, universe, restricted, or multiverse) are checked. Toggle 
one or more of the checkboxes.
   3. Using a text editor of some kind (perhaps Vim), confirm that 
/etc/apt/sources.list.d/ubuntu.sources reflects your changes.
   4. Switch to the Other Software tab, there should be one item in the list.
   5. Select that item, then click Edit at the bottom of the dialog. Make a 
modification to every field on the screen, or a combination of fields you would 
like to test. All fields should work.
   6. Click the OK button at the bottom of the dialog to confirm the changes, 
then click Edit for that item again. The changes you made should be reflected 
(meaning, the changes were saved.)
   7. Using a text editor of some kind (perhaps Vim), confirm that 
/etc/apt/sources.list.d/ubuntu.sources reflects your changes.

  [ Where problems could occur ]

  This is well-tested code. That being said, the following small edge cases 
exist:
   - If you create a very large amount of rows, it infinitely expands the 
dialog without a scroll wheel. This is the same functionality as the GTK 
frontend.
   - Error validation is not performed on the deb822 lines, they are simply 
written to the ubuntu.sources file. This is good as a starting point, but also 
relies on the appropriate update notifier handling these errors. This is the 
same functionality as the GTK frontend.

  In a future update, this functionality could be broken by one or more of the 
following underlying changes:
   - Changes to the software-properties backend which are only implemented for 
the GTK frontend.
   - Changes to the location or formatting of the ubuntu.sources file.
   - Regressions in the Python bindings for Qt 5, which are rare but possible.
   - Regressions in Python itself.

  [ Other Info ]
   
  Ubuntu Studio's live ISO and installed system are affected by this. Only 
Lubuntu's installed system is affected by this.

  [ Original Report ]

  Upgrading Lubuntu Jammy to Lubuntu Noble using TUI results in
  "Software sources" not correctly updated after upgrade. Prompt= shows
  normal and not LTS

  Used command sudo do-release-upgrade -d

  Otherwise the upgrade is good

  see attached screenshot

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: software-properties-common 0.99.46
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  ApportVersion:

[Touch-packages] [Bug 1980836] Re: Regression in Ubuntu 22.04: Content of form field stored invisibly

2024-04-24 Thread Timo Jyrinki

SRU information added.

** Description changed:

- Evince on Ubuntu 22.04 is not able to handle some PDF forms correctly
- anymore that it was able to handle on Ubuntu 21.10 and on Ubuntu 20.04.
+ [ Impact ]
+ 
+ The bug causes text entered in certain PDF form fields to be stored but
+ both displayed and printed white (on white background).
+ 
+ [ Test Plan ]
+ 
+ 1. Download the attached 230-muster-01.pdf.
+ 2. Try to input to any of the main content fields starting with 06-09 
("Anrede des Zahlungspflichtigen etc").
+ 3. Observe that it does not work.
+ 4. Install the updated poppler package versions
+ 5. Try the same fields and see they're functoning properly now with visibla 
text.
+ 6. Test also that the fields like "Aktenzeichen", "TL-Nr." or 
"Buchungsstelle" that weren't broken continue to work.
+ 
+ [ Where problems could occur ]
+ 
+ It is a merged upstream fix to Annot.cc file that fixed two upstream
+ bugs https://gitlab.freedesktop.org/poppler/poppler/-/issues/1189 and
+ https://gitlab.freedesktop.org/poppler/poppler/-/issues/1267.
+ 
+ There are no indications of upstream regressions caused by this fix, and
+ it was released in upstream stable release 22.08.0 (Ubuntu 22.04 LTS has
+ version based on 22.02.0).
+ 
+ However, since it's an individual cherry-pick there could always be a
+ PDF somewhere having issues with this, so it's useful to let it be
+ tested with various files in addition to the problematic ones.
+ 
+ 
+ 
+ --- original report ---
+ 
+ 
+ Evince on Ubuntu 22.04 is not able to handle some PDF forms correctly anymore 
that it was able to handle on Ubuntu 21.10 and on Ubuntu 20.04.
  
  The symptom is that one can edit the form content and also save it, but
  that the entered text is only visible when the form field is focused and
  in edit mode. Otherwise the text it is invisible, also on printouts.
  
  Such bugs have been reported against Evince for a long time (e.g.,
  https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/265033) but I am
  reporting this as a new bug because for the current form with which I am
  experiencing this it is a regression.
  
  I have attached the problematic form with two form fields filled out, one in 
the upper left corner and the big one in the lower half.
  I have produced this by taking the original, empty form (produced by somebody 
else) and first opened it in Evince 41.4, which I have installed from the snap 
package (revision 1017) on Ubuntu 22.04. I entered text in the upper left field 
and saved the form.
  Then I opened the PDF in Evince 42.3 from the apt package of Ubuntu 22.04 and 
entered text in the big field and saved the form.
  
  Evince 3.36 on Ubuntu 20.04 has the same (correct) behavior as Evince
  41.4.
  
  When I open the PDF again, only the text in the first field is visible.
  The text in the second field is visible only if I click into the field.
  The visibility of the field contents is the same for Evince 41.4 (snap),
  Evince 42.3 (apt), and Okular 20.12.3 (snap). So it seems that the
  problem is with Evince 42.3 incorrectly saving the field content, not
  with displaying it.
  
  Firefox shows and prints the content of both fields, though.
  
  Note that I cannot switch back to Evince 41 because for some other forms
  that I have the exact same problem happens only with the old version and
  the new version fixes it. So it seems that something changed that fixed
  it for some forms and broke it for others.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: evince 42.3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35
  Uname: Linux 5.15.0-40-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul  6 14:32:27 2022
  InstallationDate: Installed on 2021-11-26 (222 days ago)
  InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
  RebootRequiredPkgs: Error: path contained symlinks.
  Snap.Changes:
-  ID   Status  Spawn  Bereit 
Zusammenfassung
-  137  Done2022-07-06T12:48:33+02:00  2022-07-06T12:48:41+02:00  
Installiere "evince" Snap
+  ID   Status  Spawn  Bereit 
Zusammenfassung
+  137  Done2022-07-06T12:48:33+02:00  2022-07-06T12:48:41+02:00  
Installiere "evince" Snap
  SourcePackage: evince
  UpgradeStatus: Upgraded to jammy on 2022-06-22 (13 days ago)

** Also affects: evince (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: poppler (Ubuntu Jammy)
   Importance: Undecided
   Status: New

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

** Changed in: poppler (Ubuntu Jammy)
 Assignee: (unassigned) => Timo Jyrinki (timo-jyrinki)

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

** Description changed:

  [ Impact ]
  
  The bug causes text entered in certain PDF form fields to be stored but
  both displayed

[Touch-packages] [Bug 2061825] Re: [SRU] ucf fails to work for local diversions on Jammy

2024-04-24 Thread Ponnuvel Palaniyappan

Thanks, Dariusz!

I've attached a new debdiff.

** Attachment added: "debdiff_2061825_new.txt"
   
https://bugs.launchpad.net/ubuntu/+source/ucf/+bug/2061825/+attachment/5770060/+files/debdiff_2061825_new.txt

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

Title:
  [SRU] ucf fails to work for local diversions on Jammy

Status in ucf package in Ubuntu:
  Fix Released
Status in ucf source package in Jammy:
  In Progress

Bug description:
  [ Impact ]

  When a dpkg-diversion is used to setup a package diversion and ucf for 
managing
  the configuration files for chrony package, the postinst script of ucf fails
  when installing chrony.

  This issue isn't specific to chrony but can happen for any package whose
  config files are managed by ucf.

  This affects users on Jammy who use ucf. Newer versions of ucf have this bug
  fixed already.

  [ Test Plan ]

  1. Create a Jammy container or VM
  2. Setup a diversion for chrony.conf: dpkg-divert --package chrony --add 
--rename --divert /etc/chrony/chrony.conf.custom /etc/chrony/chrony.conf
  3. Install chrony: apt install chrony -y
  4. Notice the postinst script fail with syntax errors such as:
  ```
  Preparing to unpack .../chrony_4.2-2ubuntu2_amd64.deb ...
  Unpacking chrony (4.2-2ubuntu2) ...
  Setting up chrony (4.2-2ubuntu2) ...
  /usr/bin/ucf: 444: [: missing ]
  grep: ]: No such file or directory
  /usr/bin/ucf: 444: [: missing ]
  grep: ]: No such file or directory
  ```
  5. Install the package with the fix from the PPA: 
https://launchpad.net/~pponnuvel/+archive/ubuntu/ucf-jammy (to be replaced with 
the package from the -proposed pocket)
  6. Repeat the same from steps 1 to 4 and notice no failures at step4.

  [ Where problems could occur ]

  Can further introduce similar bugs if the patch contains similar syntax
  errors. Consequently local diversion may not take effect for packages
  using ucf to manage configuration files.

  [ Other Info ]
   
  Upstream bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979354

  It's been fixed in version ucf/3.0043+nmu1. Lunar/Mantic/Noble all have the
  ucf version with this patch.

  Affects Jammy only and thus backported to only Jammy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ucf/+bug/2061825/+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 1980805] Re: Backport packages for 20.04.5 HWE stack

2024-04-24 Thread Timo Aaltonen

** Changed in: mesa-amber (Ubuntu Focal)
   Status: Fix Committed => Won't Fix

** Changed in: llvm-toolchain-13 (Ubuntu Focal)
   Status: Fix Committed => Won't Fix

** Changed in: libdrm (Ubuntu Focal)
   Status: Fix Committed => Won't Fix

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

Title:
  Backport packages for 20.04.5 HWE stack

Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-13 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in mesa-amber package in Ubuntu:
  Invalid
Status in libdrm source package in Focal:
  Won't Fix
Status in llvm-toolchain-13 source package in Focal:
  Won't Fix
Status in mesa source package in Focal:
  Won't Fix
Status in mesa-amber source package in Focal:
  Won't Fix

Bug description:
  [Impact]

  These are needed for 20.04.5 images.

  [Test case]

  Boot a daily image, see that it still has the necessary stack
  installed and working.

  [What could go wrong]

  libdrm: pci-id updates, some minor api updates

  mesa: a new major release, but we'll pull the final stable release of
  22.0.x series, so there shouldn't be any regressions left at that
  point

  mesa-amber: forked from mesa 21.3.x, this LTS branch keeps old DRI
  drivers that were removed from main mesa

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1980805/+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 2049529] Re: Extra ZFS-related log line with `useradd -m -R /path`

2024-04-24 Thread Paride Legovini

This also affects src:adduser, which has this delta:

+if ($action eq "adduser") {
+# Mute the command
+system('sh' => ( '-c' => '"$@" >/dev/null 2>&1', '--', 
'/usr/sbin/zsysctl', 'userdata', 'create', $new_name, $home_dir,));
+}

causing it to fail in minimal environments where /dev is non populated.

In practice we are hitting this with autopkgtest-virt-unshare(1), which
tries to create a user in the chroot, but fails because of that.

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

** Summary changed:

- Extra ZFS-related log line with `useradd -m -R /path`
+ Ubuntu delta causes `can't open /dev/null: No such file or directory` errors 
in minimal environments (chroot/unshare)

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

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

Title:
  Ubuntu delta causes `can't open /dev/null: No such file or directory`
  errors in minimal environments (chroot/unshare)

Status in adduser package in Ubuntu:
  Confirmed
Status in shadow package in Ubuntu:
  Confirmed
Status in adduser source package in Noble:
  Confirmed
Status in shadow source package in Noble:
  Confirmed

Bug description:
  Hi,

  I was digging into fixing `autopkgtest`'s `unshare` testsuite, and the
  rabbit hole led me here.

  Here is a very quick reproducer, first:

  Start a fresh Ubuntu VM. Here is a quick path, but other ways should do fine:
  ```
  $ cd /tmp
  $ autopkgtest-buildvm-ubuntu-cloud -a amd64 -r noble
  $ kvm -m 1G -snapshot -hda autopkgtest-noble-amd64.img
  ```

  Now in the VM:
  ```
  $ sudo apt install -y mmdebstrap
  $ mmdebstrap noble /tmp/rootfs
  [...]
  $ sudo useradd --create-home --root /tmp/rootfs user1
  can't open /dev/null: No such file or directory
  ```

  The line `can't open /dev/null: No such file or directory` is printed
  on `stderr`, and that's unexpected by the part of the code I was
  debugging in the first place.

  Digging a bit led me to that line that does the printing:
  
https://git.launchpad.net/ubuntu/+source/shadow/tree/debian/patches/1015_add_zsys_support.patch#n69

  There seem to me that there are multiple issues with that patch:
  * Why try to call `zsysctl` in every case without first checking that it 
would be relevant: ZFS is not even installed on the VM we just created, less 
alone it has any ZFS volume/pool/whatever.
  * Obviously, when creating a user in a `chroot`, `/dev/null` won't exist 
unless mapped, and `useradd` is perfectly aware of that, because it even does 
the `chroot` call itself! But why even try to mess with ZFS in the `chroot` 
case in the first place?

  From what history @brian-murray told me, this patch was part of some
  ZFS experimentation in the past. Maybe that experimentation is now
  finished, and that patch could be dropped? At the very least it needs
  improvements, imho.

  EDIT: Just for context on why this issue appears only now: I was
  trying to fix the `unshare` testsuite in `autopkgtest`, which is
  pretty recent (2022) (https://salsa.debian.org/ci-
  team/autopkgtest/-/commit/d1671f94f68bce9a0c6793310a9f8b79b4e919a5)
  even upstream on Debian, and has never worked yet on Ubuntu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adduser/+bug/2049529/+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 2063332] [NEW] Multiple problems Ubuntu 24.04 with Qt5

2024-04-24 Thread Jakub Klos

Public bug reported:

After the upgrade to the 24.04 beta Qt5 UI is not at its best. Please,
notice that all this functionality is working on 22.04.

1. Windows controls settings from Gnome are not applied
When you set the Windows Title bar buttons to Placement Left, then Qt apps 
ignore this setting. The default gt4 apps behave properly and place the buttons 
to the left.

2. Windows actions like double click to maximize from settings also do
not with in the Qt5 apps unlike in gt4 apps.

3. Several keyboard shortcuts are passed differently to Qt5 apps.
The key "Ctrl+Period" is not passed to the qt app at all
The key "Ctrl+~" is passed as "Ctrl+0"
The key "Shift+Alt+F7" is also not working
This means some different handling is applied in Qt5 apps

4. If you use the env var "export QT_QPA_PLATFORM=xcb" and start the Qt5
app, then it all works properly. The windows controls are on the right
side, you can use double click the title bar to maximize and also the
shortcuts are working fine. However, in such scenario no app starts
fullscreen. It starts in a positioned window (the position is
remembered) instead even if you maximized the window before you exited
it.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: libqt5core5t64 5.15.13+dfsg-1ubuntu1
ProcVersionSignature: Ubuntu 6.8.0-28.28-generic 6.8.1
Uname: Linux 6.8.0-28-generic x86_64
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 24 14:20:24 2024
InstallationDate: Installed on 2020-05-12 (1443 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: qtbase-opensource-src
UpgradeStatus: Upgraded to noble on 2024-04-20 (4 days ago)
modified.conffile..etc.init.d.apport: [modified]
mtime.conffile..etc.init.d.apport: 2024-04-19T01:50:32

** Affects: qtbase-opensource-src (Ubuntu)
 Importance: Undecided
 Status: New


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

** Attachment added: "Displays how gtk4 apps are displayed"
   
https://bugs.launchpad.net/bugs/2063332/+attachment/5770029/+files/Screenshot%20from%202024-04-24%2014-11-30.png

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

Title:
  Multiple problems Ubuntu 24.04 with Qt5

Status in qtbase-opensource-src package in Ubuntu:
  New

Bug description:
  After the upgrade to the 24.04 beta Qt5 UI is not at its best. Please,
  notice that all this functionality is working on 22.04.

  1. Windows controls settings from Gnome are not applied
  When you set the Windows Title bar buttons to Placement Left, then Qt apps 
ignore this setting. The default gt4 apps behave properly and place the buttons 
to the left.

  2. Windows actions like double click to maximize from settings also do
  not with in the Qt5 apps unlike in gt4 apps.

  3. Several keyboard shortcuts are passed differently to Qt5 apps.
  The key "Ctrl+Period" is not passed to the qt app at all
  The key "Ctrl+~" is passed as "Ctrl+0"
  The key "Shift+Alt+F7" is also not working
  This means some different handling is applied in Qt5 apps

  4. If you use the env var "export QT_QPA_PLATFORM=xcb" and start the
  Qt5 app, then it all works properly. The windows controls are on the
  right side, you can use double click the title bar to maximize and
  also the shortcuts are working fine. However, in such scenario no app
  starts fullscreen. It starts in a positioned window (the position is
  remembered) instead even if you maximized the window before you exited
  it.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: libqt5core5t64 5.15.13+dfsg-1ubuntu1
  ProcVersionSignature: Ubuntu 6.8.0-28.28-generic 6.8.1
  Uname: Linux 6.8.0-28-generic x86_64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 24 14:20:24 2024
  InstallationDate: Installed on 2020-05-12 (1443 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  SourcePackage: qtbase-opensource-src
  UpgradeStatus: Upgraded to noble on 2024-04-20 (4 days ago)
  modified.conffile..etc.init.d.apport: [modified]
  mtime.conffile..etc.init.d.apport: 2024-04-19T01:50:32

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/2063332/+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 2063332] Re: Multiple problems Ubuntu 24.04 with Qt5

2024-04-24 Thread Jakub Klos

** Attachment added: "Displays how Qt5 apps are displayed instead"

https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/2063332/+attachment/5770034/+files/Screenshot%20from%202024-04-24%2014-11-47.png

** Description changed:

After the upgrade to the 24.04 beta Qt5 UI is not at its best. Please,
- notice that all this functionality used to be working on 22.04.
+ notice that all this functionality is working on 22.04.

2. Windows actions like double click to maximize from settings also do
not with in the Qt5 apps unlike in gt4 apps.

- 3. Several keyboard shortcuts are passed differently to Qt5 apps.
+ 3. Several keyboard shortcuts are passed differently to Qt5 apps.
The key "Ctrl+Period" is not passed to the qt app at all
The key "Ctrl+~" is passed as "Ctrl+0"
The key "Shift+Alt+F7" is also not working
This means some different handling is applied in Qt5 apps

4. If you use the env var "export QT_QPA_PLATFORM=xcb" and start the Qt5
app, then it all works properly. The windows controls are on the right
side, you can use double click the title bar to maximize and also the
shortcuts are working fine. However, in such scenario no app starts
fullscreen. It starts in a positioned window (the position is
remembered) instead even if you maximized the window before you exited
it.

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

Title:
Multiple problems Ubuntu 24.04 with Qt5

Status in qtbase-opensource-src package in Ubuntu:
New

Bug description:
After the upgrade to the 24.04 beta Qt5 UI is not at its best. Please,
notice that all this functionality is working on 22.04.

2. Windows actions like double click to maximize from settings also do
not with in the Qt5 apps unlike in gt4 apps.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/2063332/+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 2061214] Re: [SRU] Software Sources is not compatible with deb822

2024-04-24 Thread Chris Guiver

Booted an install made earlier today on hp_compaq_dc7700 of lubuntu
noble (20240424) ;
https://iso.qa.ubuntu.com/qatracker/milestones/453/builds/300235/testcases/1701/results/

sudo apt update; sudo apt full-upgrade & no updates are available.
(software-properties-qt 0.99.48.1)

Following the "Intended Functionality" listed in the Bug.Description at
the top of this bug report and behavior is what I'd expect.

The `/etc/apt/sources.list` file contained comments only ; with all
subsequent changes being reflected in
`/etc/apt/sources.list.d/ubuntu.sources` and looked appropriate to me.

However I'm tired, and fear I've missed something (that I can't 'put my
finger on'), but I've repeated steps 1..7 twice & didn't locate what
'irks' me sorry.

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

Title:
  [SRU] Software Sources is not compatible with deb822

Status in software-properties package in Ubuntu:
  Confirmed
Status in software-properties source package in Noble:
  Confirmed

Bug description:
  [ Impact ]

  Ubuntu 24.04 now uses deb822 to represent software sources for deb
  packages, instead of /etc/apt/sources.list. The complete rationale for
  this change can be found here: https://discourse.ubuntu.com/t/spec-
  apt-deb822-sources-by-default/29333

  software-properties has two graphical frontends for editing these
  software sources, one is GTK-based and the other is Qt-based. When the
  underlying change to deb822 sources was made, the GTK-based frontend
  and the DBus backend interface gained support.

  The original bug report shown below informed us of the lack of deb822
  support in the Qt frontend, which results in a broken, non-functional
  interface when attempting to view or edit most values on the first two
  tabs. The fix for this is to implement a Qt dialog for deb822 sources
  that somewhat matches the existing GTK interface.

  [ Test Plan ]

  Install software-properties-qt 0.99.48 or earlier.

  Reproducing the bug:
   1. From the menu, open Software Sources. Alternatively, run `sudo -E 
software-properties-qt` in a terminal.
   2. Observe that all four checkboxes on the Ubuntu Software tab (main, 
universe, restricted, and multiverse) are unchecked.
   3. Move to the Other Software tab and observe that there are no items in the 
list.

  Upgrade to software-properties-qt 0.99.49.

  Intended functionality:
   1. From the menu, open Software Sources. Alternatively, run `sudo -E 
software-properties-qt` in a terminal.
   2. Observe that one or more checkboxes on the Ubuntu Software tab 
(representing main, universe, restricted, or multiverse) are checked. Toggle 
one or more of the checkboxes.
   3. Using a text editor of some kind (perhaps Vim), confirm that 
/etc/apt/sources.list.d/ubuntu.sources reflects your changes.
   4. Switch to the Other Software tab, there should be one item in the list.
   5. Select that item, then click Edit at the bottom of the dialog. Make a 
modification to every field on the screen, or a combination of fields you would 
like to test. All fields should work.
   6. Click the OK button at the bottom of the dialog to confirm the changes, 
then click Edit for that item again. The changes you made should be reflected 
(meaning, the changes were saved.)
   7. Using a text editor of some kind (perhaps Vim), confirm that 
/etc/apt/sources.list.d/ubuntu.sources reflects your changes.

  [ Where problems could occur ]

  This is well-tested code. That being said, the following small edge cases 
exist:
   - If you create a very large amount of rows, it infinitely expands the 
dialog without a scroll wheel. This is the same functionality as the GTK 
frontend.
   - Error validation is not performed on the deb822 lines, they are simply 
written to the ubuntu.sources file. This is good as a starting point, but also 
relies on the appropriate update notifier handling these errors. This is the 
same functionality as the GTK frontend.

  In a future update, this functionality could be broken by one or more of the 
following underlying changes:
   - Changes to the software-properties backend which are only implemented for 
the GTK frontend.
   - Changes to the location or formatting of the ubuntu.sources file.
   - Regressions in the Python bindings for Qt 5, which are rare but possible.
   - Regressions in Python itself.

  [ Other Info ]
   
  Ubuntu Studio's live ISO and installed system are affected by this. Only 
Lubuntu's installed system is affected by this.

  [ Original Report ]

  Upgrading Lubuntu Jammy to Lubuntu Noble using TUI results in
  "Software sources" not correctly updated after upgrade. Prompt= shows
  normal and not LTS

  Used command sudo do-release-upgrade -d

  Otherwise the upgrade is good

  see attached screenshot

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: software-properties-common

[Touch-packages] [Bug 2061214] Re: [SRU] Software Sources is not compatible with deb822

2024-04-24 Thread Leó Kolbeinsson

Tested Lubuntu Noble ISO dated 24-04-2024 and the bug no longer present.

Also tested upgrades from Lubuntu Jammy and Lubuntu Mantic to Lubuntu
Noble using GUI and also TUI and bug not present.

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

Title:
  [SRU] Software Sources is not compatible with deb822

Status in software-properties package in Ubuntu:
  Confirmed
Status in software-properties source package in Noble:
  Confirmed

Bug description:
  [ Impact ]

  Ubuntu 24.04 now uses deb822 to represent software sources for deb
  packages, instead of /etc/apt/sources.list. The complete rationale for
  this change can be found here: https://discourse.ubuntu.com/t/spec-
  apt-deb822-sources-by-default/29333

  software-properties has two graphical frontends for editing these
  software sources, one is GTK-based and the other is Qt-based. When the
  underlying change to deb822 sources was made, the GTK-based frontend
  and the DBus backend interface gained support.

  The original bug report shown below informed us of the lack of deb822
  support in the Qt frontend, which results in a broken, non-functional
  interface when attempting to view or edit most values on the first two
  tabs. The fix for this is to implement a Qt dialog for deb822 sources
  that somewhat matches the existing GTK interface.

  [ Test Plan ]

  Install software-properties-qt 0.99.48 or earlier.

  Reproducing the bug:
   1. From the menu, open Software Sources. Alternatively, run `sudo -E 
software-properties-qt` in a terminal.
   2. Observe that all four checkboxes on the Ubuntu Software tab (main, 
universe, restricted, and multiverse) are unchecked.
   3. Move to the Other Software tab and observe that there are no items in the 
list.

  Upgrade to software-properties-qt 0.99.49.

  Intended functionality:
   1. From the menu, open Software Sources. Alternatively, run `sudo -E 
software-properties-qt` in a terminal.
   2. Observe that one or more checkboxes on the Ubuntu Software tab 
(representing main, universe, restricted, or multiverse) are checked. Toggle 
one or more of the checkboxes.
   3. Using a text editor of some kind (perhaps Vim), confirm that 
/etc/apt/sources.list.d/ubuntu.sources reflects your changes.
   4. Switch to the Other Software tab, there should be one item in the list.
   5. Select that item, then click Edit at the bottom of the dialog. Make a 
modification to every field on the screen, or a combination of fields you would 
like to test. All fields should work.
   6. Click the OK button at the bottom of the dialog to confirm the changes, 
then click Edit for that item again. The changes you made should be reflected 
(meaning, the changes were saved.)
   7. Using a text editor of some kind (perhaps Vim), confirm that 
/etc/apt/sources.list.d/ubuntu.sources reflects your changes.

  [ Where problems could occur ]

  This is well-tested code. That being said, the following small edge cases 
exist:
   - If you create a very large amount of rows, it infinitely expands the 
dialog without a scroll wheel. This is the same functionality as the GTK 
frontend.
   - Error validation is not performed on the deb822 lines, they are simply 
written to the ubuntu.sources file. This is good as a starting point, but also 
relies on the appropriate update notifier handling these errors. This is the 
same functionality as the GTK frontend.

  In a future update, this functionality could be broken by one or more of the 
following underlying changes:
   - Changes to the software-properties backend which are only implemented for 
the GTK frontend.
   - Changes to the location or formatting of the ubuntu.sources file.
   - Regressions in the Python bindings for Qt 5, which are rare but possible.
   - Regressions in Python itself.

  [ Other Info ]
   
  Ubuntu Studio's live ISO and installed system are affected by this. Only 
Lubuntu's installed system is affected by this.

  [ Original Report ]

  Upgrading Lubuntu Jammy to Lubuntu Noble using TUI results in
  "Software sources" not correctly updated after upgrade. Prompt= shows
  normal and not LTS

  Used command sudo do-release-upgrade -d

  Otherwise the upgrade is good

  see attached screenshot

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: software-properties-common 0.99.46
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: LXQt
  Date: Sat Apr 13 11:44:28 2024
  InstallationDate: Installed on 2024-04-13 (0 days ago)
  InstallationMedia: Lubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240331)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to noble on 2024-04-13 (0 days ago)
  mtime.conffile..etc.init.d.apport:

[Touch-packages] [Bug 2063328] [NEW] FTBFS in eglibc

2024-04-24 Thread Leonidas S. Barbosa

Public bug reported:

== Summary ==

A FTBFS occurs in eglibc that affects trusty-esm to be build.

== What happens ==
# Format: , Error  [(ignored)]
#
annexc.out, Error 1 (ignored)
bug22.out, Error 1
run-conformtest.out, Error 1 (ignored)
tst-mutex7.out, Error 1
tst-mutex7a.out, Error 1
tst-mutexpi7.out, Error 1
tst-mutexpi7a.out, Error 1
tst-once2.out, Error 1
tst-setlocale3.out, Error 1
***
Encountered regressions that don't match expected failures 
(debian/testsuite-checking/expected-results-x86_64-linux-gnu-libc):
bug22.out, Error 1
tst-mutex7.out, Error 1
tst-mutex7a.out, Error 1
tst-mutexpi7.out, Error 1
tst-mutexpi7a.out, Error 1
tst-once2.out, Error 1
tst-setlocale3.out, Error 1
TEST bug22.out:
ret = -1
ret = -1
ret = -1
ret = -1
TEST tst-mutex7.out:
creating thread 63 failed
TEST tst-mutex7a.out:
creating thread 63 failed
TEST tst-mutexpi7.out:
creating thread 63 failed
TEST tst-mutexpi7a.out:
creating thread 63 failed
TEST tst-once2.out:
creation of thread 63 failed
TEST tst-setlocale3.out:
malloc failure
Encountered progressions that don't match expected failures:
tst-backtrace6.out, Error 1
tst-cpuclock2.out, Error 1
tst-cputimer1.out, Error 1
tst-mqueue5.out, Error 1
tst-timer.out, Error 139
tst-waitid.out, Error 1
tst-writev.out, Error 1
make: *** [/<>/stamp-dir/check_libc] Error 1

== Fix commit/related ==
https://sourceware.org/bugzilla/show_bug.cgi?id=19648
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=36234ceda21820d2f874067553e7faae763a40cf

** Affects: eglibc (Ubuntu)
 Importance: Undecided
 Assignee: Leonidas S. Barbosa (leosilvab)
 Status: In Progress

** Package changed: google-osconfig-agent (Ubuntu) => eglibc (Ubuntu)

** Changed in: eglibc (Ubuntu)
   Status: New => In Progress

** Changed in: eglibc (Ubuntu)
 Assignee: (unassigned) => Leonidas S. Barbosa (leosilvab)

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

Title:
  FTBFS in eglibc

Status in eglibc package in Ubuntu:
  In Progress

Bug description:
  == Summary ==

  A FTBFS occurs in eglibc that affects trusty-esm to be build.

  == What happens ==
  # Format: , Error  [(ignored)]
  #
  annexc.out, Error 1 (ignored)
  bug22.out, Error 1
  run-conformtest.out, Error 1 (ignored)
  tst-mutex7.out, Error 1
  tst-mutex7a.out, Error 1
  tst-mutexpi7.out, Error 1
  tst-mutexpi7a.out, Error 1
  tst-once2.out, Error 1
  tst-setlocale3.out, Error 1
  ***
  Encountered regressions that don't match expected failures 
(debian/testsuite-checking/expected-results-x86_64-linux-gnu-libc):
  bug22.out, Error 1
  tst-mutex7.out, Error 1
  tst-mutex7a.out, Error 1
  tst-mutexpi7.out, Error 1
  tst-mutexpi7a.out, Error 1
  tst-once2.out, Error 1
  tst-setlocale3.out, Error 1
  TEST bug22.out:
  ret = -1
  ret = -1
  ret = -1
  ret = -1
  TEST tst-mutex7.out:
  creating thread 63 failed
  TEST tst-mutex7a.out:
  creating thread 63 failed
  TEST tst-mutexpi7.out:
  creating thread 63 failed
  TEST tst-mutexpi7a.out:
  creating thread 63 failed
  TEST tst-once2.out:
  creation of thread 63 failed
  TEST tst-setlocale3.out:
  malloc failure
  Encountered progressions that don't match expected failures:
  tst-backtrace6.out, Error 1
  tst-cpuclock2.out, Error 1
  tst-cputimer1.out, Error 1
  tst-mqueue5.out, Error 1
  tst-timer.out, Error 139
  tst-waitid.out, Error 1
  tst-writev.out, Error 1
  make: *** [/<>/stamp-dir/check_libc] Error 1

  == Fix commit/related ==
  https://sourceware.org/bugzilla/show_bug.cgi?id=19648
  
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=36234ceda21820d2f874067553e7faae763a40cf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/2063328/+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 2063328] [NEW] FTBFS in eglibc

You have been subscribed to a public bug:

== Summary ==

A FTBFS occurs in eglibc that affects trusty-esm to be build.

== What happens ==
# Format: , Error  [(ignored)]
#
annexc.out, Error 1 (ignored)
bug22.out, Error 1
run-conformtest.out, Error 1 (ignored)
tst-mutex7.out, Error 1
tst-mutex7a.out, Error 1
tst-mutexpi7.out, Error 1
tst-mutexpi7a.out, Error 1
tst-once2.out, Error 1
tst-setlocale3.out, Error 1
***
Encountered regressions that don't match expected failures 
(debian/testsuite-checking/expected-results-x86_64-linux-gnu-libc):
bug22.out, Error 1
tst-mutex7.out, Error 1
tst-mutex7a.out, Error 1
tst-mutexpi7.out, Error 1
tst-mutexpi7a.out, Error 1
tst-once2.out, Error 1
tst-setlocale3.out, Error 1
TEST bug22.out:
ret = -1
ret = -1
ret = -1
ret = -1
TEST tst-mutex7.out:
creating thread 63 failed
TEST tst-mutex7a.out:
creating thread 63 failed
TEST tst-mutexpi7.out:
creating thread 63 failed
TEST tst-mutexpi7a.out:
creating thread 63 failed
TEST tst-once2.out:
creation of thread 63 failed
TEST tst-setlocale3.out:
malloc failure
Encountered progressions that don't match expected failures:
tst-backtrace6.out, Error 1
tst-cpuclock2.out, Error 1
tst-cputimer1.out, Error 1
tst-mqueue5.out, Error 1
tst-timer.out, Error 139
tst-waitid.out, Error 1
tst-writev.out, Error 1
make: *** [/<>/stamp-dir/check_libc] Error 1

== Fix commit/related ==
https://sourceware.org/bugzilla/show_bug.cgi?id=19648
https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=36234ceda21820d2f874067553e7faae763a40cf

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

-- 
FTBFS in eglibc 
https://bugs.launchpad.net/bugs/2063328
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to eglibc 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 2053289] Re: Internal microphone realtek ALC257 is not working in 24.04 Noble (Fujitsu WU4/H1)

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

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

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

Title:
  Internal microphone realtek ALC257 is not working in 24.04 Noble
  (Fujitsu WU4/H1)

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I tried to record sound with my internal Mic. Nothing is working. I
  use arecord.

  ```
  bagus:~$ arecord test.wav
  arecord: main:834: audio open error: Operation not supported
  bagus:~$ arecord -d 10 -f cd -t wav -D copy foobar.wav
  ALSA lib pcm.c:2675:(snd_pcm_open_noupdate) Unknown PCM copy
  arecord: main:834: audio open error: No such file or directory

  bagus:~$ arecord -l
   List of CAPTURE Hardware Devices 
  card 0: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) []
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 6: DMIC (*) []
Subdevices: 1/1
Subdevice #0: subdevice #0
  card 0: sofhdadsp [sof-hda-dsp], device 7: DMIC16kHz (*) []
Subdevices: 1/1
Subdevice #0: subdevice #0

  bagus:~$ lsb_release -rd
  No LSB modules are available.
  Description:  Ubuntu Noble Numbat (development branch)
  Release:  24.04

  bagus:~$ apt-cache policy alsa-base
  alsa-base:
Installed: (none)
Candidate: 1.0.25+dfsg-0ubuntu7
Version table:
   1.0.25+dfsg-0ubuntu7 500
  500 http://archive.ubuntu.com/ubuntu noble/main amd64 Packages

  
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/2053289/+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 2063324] [NEW] Ubuntu-bug -w notification can be made to hang if closing terminal ctrl+z

2024-04-24 Thread Jānis Kangarooo

Public bug reported:

Ubuntu-bug -w and fast switch windows alt+tab lost notification in back, then 
switch back to terminal and i dont see notification
I cancel terminall ubuntu-bug -w with ctrl+z
Notifications stays up
Closing it shows its frozen.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: apport-kde 2.20.11-0ubuntu82.5
ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13
Uname: Linux 6.5.0-28-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Wed Apr 24 11:15:44 2024
ExecutablePath: /usr/share/apport/apport-kde
InstallationDate: Installed on 2024-01-05 (110 days ago)
InstallationMedia: Kubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.1)
InterpreterPath: /usr/bin/python3.10
PackageArchitecture: all
Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
PythonDetails: N/A
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy

** Attachment added: "ubuntubugw.gif"
   
https://bugs.launchpad.net/bugs/2063324/+attachment/5769987/+files/ubuntubugw.gif

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

Title:
  Ubuntu-bug -w notification can be made to hang if closing terminal
  ctrl+z

Status in apport package in Ubuntu:
  New

Bug description:
  Ubuntu-bug -w and fast switch windows alt+tab lost notification in back, then 
switch back to terminal and i dont see notification
  I cancel terminall ubuntu-bug -w with ctrl+z
  Notifications stays up
  Closing it shows its frozen.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apport-kde 2.20.11-0ubuntu82.5
  ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13
  Uname: Linux 6.5.0-28-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Wed Apr 24 11:15:44 2024
  ExecutablePath: /usr/share/apport/apport-kde
  InstallationDate: Installed on 2024-01-05 (110 days ago)
  InstallationMedia: Kubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.1)
  InterpreterPath: /usr/bin/python3.10
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.10, Python 3.10.12, python3-minimal, 
3.10.6-1~22.04
  PythonDetails: N/A
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2063324/+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 2063200] Re: useradd --extrausers --groups tries to lock /etc/group

2024-04-24 Thread Simon Chopin

The issue was introduced with https://github.com/shadow-
maint/shadow/pull/237

Basically, the previous group validation was done using glibc's getgrid
directly, which was presumably coping well with the RO status of
/etc/group, but that poses consistency problems because you could add a
local user to a network group. That PR changed this to only check the
local /etc/group file contents manually instead.

Sadly, it doesn't cope well with our extrausers feature on multiple levels:
* The manual code fails hard if it can't lock the files
* We presumably have local groups defined in multiple places, which the code 
doesn't allow for.

A quickfix would be:
* Move the validation to until *after* parsing all of the options
* Revert back to the previous approach to validate groups if in extrausers mode

A more involved fix would be to replace that with an approach that would
check both /etc/group and the extrausers equivalent when validating
groups, while silently ignoring locking failures.

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

Title:
  useradd --extrausers --groups tries to lock /etc/group

Status in shadow package in Ubuntu:
  New

Bug description:
  On Ubuntu Core 24 calling the command line

  useradd --extrausers --groups somegroup somenewuser

  ... fails with:

  useradd: cannot lock /etc/group; try again later.

  It worked on 22.04. /etc is not writable. It also fails if somegroup
  is a group in extrausers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/2063200/+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 2060900] Re: gst-plugin-scanner crashed with SIGABRT in __assert_fail_base()

** Tags removed: need-amd64-retrace

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

Title:
  gst-plugin-scanner crashed with SIGABRT in __assert_fail_base()

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  this give me error from some files

  ProblemType: Crash
  DistroRelease: Ubuntu 24.04
  Package: libgstreamer1.0-0 1.24.1-1build1
  ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
  Uname: Linux 6.8.0-11-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Thu Apr 11 11:07:09 2024
  ExecutablePath: 
/usr/lib/x86_64-linux-gnu/gstreamer1.0/gstreamer-1.0/gst-plugin-scanner
  InstallationDate: Installed on 2024-04-04 (7 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240323)
  ProcCmdline: 
/usr/lib/x86_64-linux-gnu/../../lib/x86_64-linux-gnu/gstreamer1.0/gstreamer-1.0/gst-plugin-scanner
 -l /usr/bin/rhythmbox
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RebootRequiredPkgs: Error: path contained symlinks.
  Signal: 6
  SignalName: SIGABRT
  SourcePackage: gstreamer1.0
  StacktraceTop:
   __assert_fail_base (fmt=0x702a92dd01e8 "%s%s%s:%u: %s%sAssertion `%s' 
failed.\n%n", assertion=assertion@entry=0x702a7b4e1c90 "subsampling == 
SUBSAMPLE_YUV420 || subsampling == SUBSAMPLE_YUV422H || subsampling == 
SUBSAMPLE_YUV422V || subsampling == SUBSAMPLE_RGBX", 
file=file@entry=0x702a7b4e44b6 "i965_drv_video.c", line=line@entry=4653, 
function=function@entry=0x702a7b511600 "i965_check_alloc_surface_bo") at 
./assert/assert.c:94
   __assert_fail (assertion=0x702a7b4e1c90 "subsampling == SUBSAMPLE_YUV420 || 
subsampling == SUBSAMPLE_YUV422H || subsampling == SUBSAMPLE_YUV422V || 
subsampling == SUBSAMPLE_RGBX", file=0x702a7b4e44b6 "i965_drv_video.c", 
line=4653, function=0x702a7b511600 "i965_check_alloc_surface_bo") at 
./assert/assert.c:103
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
   ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
   vaCreateSurfaces () from /lib/x86_64-linux-gnu/libva.so.2
  Title: gst-plugin-scanner crashed with SIGABRT in __assert_fail_base()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sudo users
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/2060900/+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 2060693] Re: No welcome/login sound on Ubuntu desktop

2024-04-24 Thread Sebastien Bacher

If it's specific to raspi is it maybe the same problem than bug
#2063255?

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

Title:
  No welcome/login sound on Ubuntu desktop

Status in libcanberra package in Ubuntu:
  New

Bug description:
  Under the Ubuntu desktop for Raspberry Pi, for several recent
  releases, the startup sound from the Yaru sound theme has failed to
  play both at the initial setup (from oem-config, where it used to play
  just before language selection), and at the greeter.

  This worked in Jammy (22.04), but on at least mantic (23.10) and the
  forthcoming noble (24.04) (and possibly earlier), this has failed.
  It's not due to a crash in canberra-gtk-play (used to play the sound).
  The only hint that something has failed appears in the oem-config.log:

Failed to play sound: Not available

  Unfortunately there's nothing else in the log that hints at why
  canberra-gtk-play is failing.

  There are several similar bug report, but I doubt they are related
  given their age (e.g. LP: #1002114 relates to ubuntu 12.04 which had a
  very different sound stack and predates the preinstalled desktop
  images).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libcanberra/+bug/2060693/+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 2061825] Re: [SRU] ucf fails to work for local diversions on Jammy

2024-04-24 Thread Dariusz Gadomski

Hey Pon, the debdiff contains changes to a bunch of files inside .pc
which should not be included.

Can you try generating the debdiff again wtihout these changes?

Once of the ways would be to drop in a patch to d/patches and add it
with quilt or apply it with the "patch" command and then run "dpkg-
source --commit" to generate the patch for you.

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

Title:
  [SRU] ucf fails to work for local diversions on Jammy

Status in ucf package in Ubuntu:
  Fix Released
Status in ucf source package in Jammy:
  In Progress

Bug description:
  [ Impact ]

  When a dpkg-diversion is used to setup a package diversion and ucf for 
managing
  the configuration files for chrony package, the postinst script of ucf fails
  when installing chrony.

  This issue isn't specific to chrony but can happen for any package whose
  config files are managed by ucf.

  This affects users on Jammy who use ucf. Newer versions of ucf have this bug
  fixed already.

  [ Test Plan ]

  1. Create a Jammy container or VM
  2. Setup a diversion for chrony.conf: dpkg-divert --package chrony --add 
--rename --divert /etc/chrony/chrony.conf.custom /etc/chrony/chrony.conf
  3. Install chrony: apt install chrony -y
  4. Notice the postinst script fail with syntax errors such as:
  ```
  Preparing to unpack .../chrony_4.2-2ubuntu2_amd64.deb ...
  Unpacking chrony (4.2-2ubuntu2) ...
  Setting up chrony (4.2-2ubuntu2) ...
  /usr/bin/ucf: 444: [: missing ]
  grep: ]: No such file or directory
  /usr/bin/ucf: 444: [: missing ]
  grep: ]: No such file or directory
  ```
  5. Install the package with the fix from the PPA: 
https://launchpad.net/~pponnuvel/+archive/ubuntu/ucf-jammy (to be replaced with 
the package from the -proposed pocket)
  6. Repeat the same from steps 1 to 4 and notice no failures at step4.

  [ Where problems could occur ]

  Can further introduce similar bugs if the patch contains similar syntax
  errors. Consequently local diversion may not take effect for packages
  using ucf to manage configuration files.

  [ Other Info ]
   
  Upstream bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=979354

  It's been fixed in version ucf/3.0043+nmu1. Lunar/Mantic/Noble all have the
  ucf version with this patch.

  Affects Jammy only and thus backported to only Jammy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ucf/+bug/2061825/+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 2063154] Re: Wireguard imported with Network manager does not work after latest upgrade, wg-quick using the same config file works

2024-04-24 Thread Sebastien Bacher

thanks for the update, closing the report then but feel free to reopen
if you get it again

** Changed in: network-manager (Ubuntu)
   Status: New => Invalid

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

Title:
  Wireguard imported with Network manager does not work after latest
  upgrade, wg-quick using the same config file works

Status in network-manager package in Ubuntu:
  Invalid

Bug description:
  Until a few days ago, after some upgrade, wireguard config imported
  with Network manager worked ootb. Now, it does not, there is no
  handshake. Activating the same config file with wg-quick does work.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: network-manager 1.46.0-1ubuntu2
  ProcVersionSignature: Ubuntu 6.8.0-1005.5-oem 6.8.1
  Uname: Linux 6.8.0-1005-oem x86_64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 22 22:41:06 2024
  InstallationDate: Installed on 2024-04-08 (14 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240408)
  IpRoute:
   default via 192.168.173.139 dev wlp1s0 proto dhcp src 192.168.173.61 metric 
600 
   192.168.173.0/24 dev wlp1s0 proto kernel scope link src 192.168.173.61 
metric 600
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE   STATE   IP4-CONNECTIVITY  
IP6-CONNECTIVITY  DBUS-PATH  CONNECTION  
CON-UUID  CON-PATH  
  
   wlp1s0   wifi   connected   full  limited
   /org/freedesktop/NetworkManager/Devices/2  MR Net 1
f92fae58-e84a-487e-9bdd-8d1ffbf8ca17  
/org/freedesktop/NetworkManager/ActiveConnection/2  
   lo   loopback   connected (externally)  unknown   unknown
   /org/freedesktop/NetworkManager/Devices/1  lo  
6fc7aa03-b696-4081-a275-4dc81c74c13e  
/org/freedesktop/NetworkManager/ActiveConnection/1  
   P14s_wg  wireguard  connected (externally)  limited   limited
   /org/freedesktop/NetworkManager/Devices/4  P14s_wg 
40fadfce-b931-472f-b4cd-9922f77068ee  
/org/freedesktop/NetworkManager/ActiveConnection/14
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.46.0   connected  started  full  enabled enabled  
enabled  missing  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2063154/+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 2061337] Re: systemd-localed crashed with SIGABRT in __waitid()

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed as the report has a core dump which is invalid. The
corruption may have happened on the system which the crash occurred or during
transit.

Thank you for your understanding, and sorry for the inconvenience!


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

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/2061337/+attachment/5765423/+files/CoreDump.gz

** Tags removed: need-amd64-retrace

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

Title:
  systemd-localed crashed with SIGABRT in __waitid()

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  send report is displaed on install

  ProblemType: Crash
  DistroRelease: Ubuntu 24.04
  Package: systemd 255.4-1ubuntu7
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.496
  CloudArchitecture: x86_64
  CloudID: nocloud
  CloudName: unknown
  CloudPlatform: nocloud
  CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
  Date: Mon Apr 15 09:23:26 2024
  ExecutablePath: /usr/lib/systemd/systemd-localed
  LiveMediaBuild: Ubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240410.2)
  Lspci:
   
  Lspci-vt:
   
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
   
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: Microsoft Corporation Virtual Machine
  ProcCmdline: /usr/lib/systemd/systemd-localed
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz --- quiet splash
  RebootRequiredPkgs: Error: path contained symlinks.
  Signal: 6
  SignalName: SIGABRT
  SourcePackage: systemd
  StacktraceTop:
   __waitid (idtype=P_PID, id=3636, infop=0x7ffeb9206940, options=4) at 
../sysdeps/unix/sysv/linux/waitid.c:29
   wait_for_terminate () from 
/usr/lib/x86_64-linux-gnu/systemd/libsystemd-shared-255.so
   wait_for_terminate_and_check () from 
/usr/lib/x86_64-linux-gnu/systemd/libsystemd-shared-255.so
   safe_fork_full () from 
/usr/lib/x86_64-linux-gnu/systemd/libsystemd-shared-255.so
   ?? ()
  SystemdFailedUnits:
   Error: command ['systemctl', 'status', '--full', '●'] failed with exit code 
4: Invalid unit name "●" escaped as "\xe2\x97\x8f" (maybe you should use 
systemd-escape?).
   Unit \xe2\x97\x8f.service could not be found.
  Title: systemd-localed crashed with SIGABRT in __waitid()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  dmi.bios.date: 11/01/2019
  dmi.bios.release: 4.0
  dmi.bios.vendor: Microsoft Corporation
  dmi.bios.version: Hyper-V UEFI Release v4.0
  dmi.board.asset.tag: None
  dmi.board.name: Virtual Machine
  dmi.board.vendor: Microsoft Corporation
  dmi.board.version: Hyper-V UEFI Release v4.0
  dmi.chassis.asset.tag: 1040-4220-4322-0021-6896-6557-30
  dmi.chassis.type: 3
  dmi.chassis.vendor: Microsoft Corporation
  dmi.chassis.version: Hyper-V UEFI Release v4.0
  dmi.modalias: 
dmi:bvnMicrosoftCorporation:bvrHyper-VUEFIReleasev4.0:bd11/01/2019:br4.0:svnMicrosoftCorporation:pnVirtualMachine:pvrHyper-VUEFIReleasev4.0:rvnMicrosoftCorporation:rnVirtualMachine:rvrHyper-VUEFIReleasev4.0:cvnMicrosoftCorporation:ct3:cvrHyper-VUEFIReleasev4.0:skuNone:
  dmi.product.family: Virtual Machine
  dmi.product.name: Virtual Machine
  dmi.product.sku: None
  dmi.product.version: Hyper-V UEFI Release v4.0
  dmi.sys.vendor: Microsoft Corporation
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2061337/+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 2037015] Re: Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as during install

** Description changed:

+ [ Impact ]
+ 
+ Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as
+ during install.
+ 
+ [ Test Plan ]
+ 
+ 1. Open the default Help app by clicking the question mark icon in the
+ dock or by running 'yelp'.
+ 
+ 2. Verify it didn't crash and the window contents are not corrupt.
+ 
+ [ Where problems could occur ]
+ 
+ The fix is limited to webkit2gtk so can only affect apps such as yelp or
+ the Raspberry Pi installer.
+ 
+ [ Other Info ]
+ 
  During the initial configuration of the Ubuntu Desktop for Raspberry Pi
  (the oem-config process, derived from ubiquity), on the Mantic beta
  images, after the various pages of information have been filled out and
  the process moves onto configuration, the "slide deck" that is usually
  displayed during the process appeared corrupted as if a horizontal
  stride were incorrectly set somewhere.
  
  I'm attached a photo of the screen (as, while I could take a screenshot
  during the process, it evidently wasn't saved somewhere persistent).
  
  I originally thought this might be a regression of LP: #1924251 as the
  corruption in the window looks very similar (incorrect horizontal stride
  causing "banding"), but I tested the embedded browser (via the help
  system) after completing setup and it worked perfectly so that's
  *probably* unrelated.

** Description changed:

  [ Impact ]
  
  Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as
  during install.
  
  [ Test Plan ]
  
- 1. Open the default Help app by clicking the question mark icon in the
+ 1. Log into a Xorg session on a Raspberry Pi 4/400.
+ 
+ 2. Open the default Help app by clicking the question mark icon in the
  dock or by running 'yelp'.
  
- 2. Verify it didn't crash and the window contents are not corrupt.
+ 3. Verify it didn't crash and the window contents are not corrupt.
  
  [ Where problems could occur ]
  
  The fix is limited to webkit2gtk so can only affect apps such as yelp or
  the Raspberry Pi installer.
  
  [ Other Info ]
  
  During the initial configuration of the Ubuntu Desktop for Raspberry Pi
  (the oem-config process, derived from ubiquity), on the Mantic beta
  images, after the various pages of information have been filled out and
  the process moves onto configuration, the "slide deck" that is usually
  displayed during the process appeared corrupted as if a horizontal
  stride were incorrectly set somewhere.
  
  I'm attached a photo of the screen (as, while I could take a screenshot
  during the process, it evidently wasn't saved somewhere persistent).
  
  I originally thought this might be a regression of LP: #1924251 as the
  corruption in the window looks very similar (incorrect horizontal stride
  causing "banding"), but I tested the embedded browser (via the help
  system) after completing setup and it worked perfectly so that's
  *probably* unrelated.

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

Title:
  Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as
  during install

Status in Webkit:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  In Progress

Bug description:
  [ Impact ]

  Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as
  during install.

  [ Test Plan ]

  1. Log into a Xorg session on a Raspberry Pi 4/400.

  2. Open the default Help app by clicking the question mark icon in the
  dock or by running 'yelp'.

  3. Verify it didn't crash and the window contents are not corrupt.

  [ Where problems could occur ]

  The fix is limited to webkit2gtk so can only affect apps such as yelp
  or the Raspberry Pi installer.

  [ Other Info ]

  During the initial configuration of the Ubuntu Desktop for Raspberry
  Pi (the oem-config process, derived from ubiquity), on the Mantic beta
  images, after the various pages of information have been filled out
  and the process moves onto configuration, the "slide deck" that is
  usually displayed during the process appeared corrupted as if a
  horizontal stride were incorrectly set somewhere.

  I'm attached a photo of the screen (as, while I could take a
  screenshot during the process, it evidently wasn't saved somewhere
  persistent).

  I originally thought this might be a regression of LP: #1924251 as the
  corruption in the window looks very similar (incorrect horizontal
  stride causing "banding"), but I tested the embedded browser (via the
  help system) after completing setup and it worked perfectly so that's
  *probably* unrelated.

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


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

[Touch-packages] [Bug 2037015] Re: Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as during install

Confirmed this fix is now working:
https://salsa.debian.org/webkit-team/webkit/-/merge_requests/20

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

Title:
  Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as
  during install

Status in Webkit:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed
Status in webkit2gtk package in Ubuntu:
  In Progress

Bug description:
  [ Impact ]

  Screen corruption of webkit2gtk apps in X11 on Raspberry Pi, such as
  during install.

  [ Test Plan ]

  1. Log into a Xorg session on a Raspberry Pi 4/400.

  2. Open the default Help app by clicking the question mark icon in the
  dock or by running 'yelp'.

  3. Verify it didn't crash and the window contents are not corrupt.

  [ Where problems could occur ]

  The fix is limited to webkit2gtk so can only affect apps such as yelp
  or the Raspberry Pi installer.

  [ Other Info ]

  During the initial configuration of the Ubuntu Desktop for Raspberry
  Pi (the oem-config process, derived from ubiquity), on the Mantic beta
  images, after the various pages of information have been filled out
  and the process moves onto configuration, the "slide deck" that is
  usually displayed during the process appeared corrupted as if a
  horizontal stride were incorrectly set somewhere.

  I'm attached a photo of the screen (as, while I could take a
  screenshot during the process, it evidently wasn't saved somewhere
  persistent).

  I originally thought this might be a regression of LP: #1924251 as the
  corruption in the window looks very similar (incorrect horizontal
  stride causing "banding"), but I tested the embedded browser (via the
  help system) after completing setup and it worked perfectly so that's
  *probably* unrelated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/webkit/+bug/2037015/+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 2062146] Re: Raspberry Pi: webkit2gtk apps crash with SIGSEGV in v3d_load_utile

** Changed in: mesa (Ubuntu)
   Status: Invalid => Triaged

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

Title:
  Raspberry Pi: webkit2gtk apps crash with SIGSEGV in v3d_load_utile

Status in Mesa:
  New
Status in mesa package in Ubuntu:
  Triaged
Status in webkit2gtk package in Ubuntu:
  In Progress
Status in yelp package in Ubuntu:
  New

Bug description:
  MiniBrowser crashed immediately on Raspberry Pi 400.

  ProblemType: Crash
  DistroRelease: Ubuntu 24.04
  Package: libwebkit2gtk-4.1-0 2.44.0-2
  ProcVersionSignature: Ubuntu 6.8.0-1002.2-raspi 6.8.1
  Uname: Linux 6.8.0-1002-raspi aarch64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CloudArchitecture: aarch64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 18 17:32:12 2024
  ExecutablePath: /usr/lib/aarch64-linux-gnu/webkit2gtk-4.1/MiniBrowser
  JournalErrors: -- No entries --
  ProcCmdline: ./MiniBrowser
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  Signal: 11
  SignalName: SIGSEGV
  SourcePackage: webkit2gtk
  StacktraceTop:
   ?? () from /usr/lib/aarch64-linux-gnu/dri/vc4_dri.so
   ?? () from /usr/lib/aarch64-linux-gnu/dri/vc4_dri.so
   ?? () from /usr/lib/aarch64-linux-gnu/dri/vc4_dri.so
   ?? () from /lib/aarch64-linux-gnu/libgbm.so.1
   ?? () from /lib/aarch64-linux-gnu/libwebkit2gtk-4.1.so.0
  Title: MiniBrowser crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/2062146/+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 2062146] Re: Raspberry Pi: webkit2gtk apps crash with SIGSEGV in v3d_load_utile

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed as the report has a core dump which is invalid. The
corruption may have happened on the system which the crash occurred or during
transit.

Thank you for your understanding, and sorry for the inconvenience!


** Changed in: mesa (Ubuntu)
   Status: Triaged => Invalid

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/2062146/+attachment/5767410/+files/CoreDump.gz

** Tags removed: need-arm64-retrace

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

Title:
  Raspberry Pi: webkit2gtk apps crash with SIGSEGV in v3d_load_utile

Status in Mesa:
  New
Status in mesa package in Ubuntu:
  Invalid
Status in webkit2gtk package in Ubuntu:
  In Progress
Status in yelp package in Ubuntu:
  New

Bug description:
  MiniBrowser crashed immediately on Raspberry Pi 400.

  ProblemType: Crash
  DistroRelease: Ubuntu 24.04
  Package: libwebkit2gtk-4.1-0 2.44.0-2
  ProcVersionSignature: Ubuntu 6.8.0-1002.2-raspi 6.8.1
  Uname: Linux 6.8.0-1002-raspi aarch64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: arm64
  CasperMD5CheckResult: unknown
  CloudArchitecture: aarch64
  CloudID: none
  CloudName: none
  CloudPlatform: none
  CloudSubPlatform: config
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 18 17:32:12 2024
  ExecutablePath: /usr/lib/aarch64-linux-gnu/webkit2gtk-4.1/MiniBrowser
  JournalErrors: -- No entries --
  ProcCmdline: ./MiniBrowser
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  Signal: 11
  SignalName: SIGSEGV
  SourcePackage: webkit2gtk
  StacktraceTop:
   ?? () from /usr/lib/aarch64-linux-gnu/dri/vc4_dri.so
   ?? () from /usr/lib/aarch64-linux-gnu/dri/vc4_dri.so
   ?? () from /usr/lib/aarch64-linux-gnu/dri/vc4_dri.so
   ?? () from /lib/aarch64-linux-gnu/libgbm.so.1
   ?? () from /lib/aarch64-linux-gnu/libwebkit2gtk-4.1.so.0
  Title: MiniBrowser crashed with SIGSEGV
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo users
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/2062146/+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 2062550] Re: package systemd-resolved 253.5-1ubuntu6.1 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit statu

** Tags removed: need-duplicate-check

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

Title:
  package systemd-resolved 253.5-1ubuntu6.1 failed to install/upgrade:
  installed systemd-resolved package post-installation script subprocess
  returned error exit status 1

Status in systemd package in Ubuntu:
  New

Bug description:
  Upgrade from 22.04 LTS to 23.10

  ProblemType: Package
  DistroRelease: Ubuntu 23.10
  Package: systemd-resolved 253.5-1ubuntu6.1
  ProcVersionSignature: Ubuntu 6.5.0-1020.21-oem 6.5.13
  Uname: Linux 6.5.0-1020-oem x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu5
  Architecture: amd64
  CasperMD5CheckResult: pass
  Date: Fri Apr 19 16:01:52 2024
  ErrorMessage: installed systemd-resolved package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2023-10-24 (178 days ago)
  InstallationMedia: Ubuntu-Server 22.04.3 LTS "Jammy Jellyfish" - Release 
amd64 (20230810)
  Python3Details: /usr/bin/python3.11, Python 3.11.6, python3-minimal, 3.11.4-5
  PythonDetails: N/A
  RebootRequiredPkgs: Error: path contained symlinks.
  RelatedPackageVersions:
   dpkg 1.22.0ubuntu1.1
   apt  2.7.3ubuntu0.1
  SourcePackage: systemd
  Title: package systemd-resolved 253.5-1ubuntu6.1 failed to install/upgrade: 
installed systemd-resolved package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: Upgraded to mantic on 2024-04-19 (0 days ago)
  mtime.conffile..etc.systemd.resolved.conf: 2023-10-30T21:36:27.073262

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2062550/+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 2061856] Re: Apps are closing immediately instead of launching

** Package changed: xorg (Ubuntu) => 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/2061856

Title:
  Apps are closing immediately instead of launching

Status in Ubuntu:
  Incomplete

Bug description:
  Ola Bomdia Eu estou com um problema no terminal shell do ubuntu ele
  esta fechando assim que clico para abrir elefecha automaticamente ja
  tentetei usar outro terminal e tambem faz a mesma coisa eu tenho  o
  fish instalado tambem mas esta fazendo a mesma coisa fechando
  automaticamente, o unico que funciona e o terminal do vscode.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-213.224-generic 4.15.18
  Uname: Linux 4.15.0-213-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.29
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue Apr 16 12:04:00 2024
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0042] 
(rev 12) (prog-if 00 [VGA controller])
 Subsystem: Elitegroup Computer Systems Core Processor Integrated Graphics 
Controller [1019:1324]
  InstallationDate: Installed on 2023-07-23 (267 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release i386 
(20170215.2)
  Lsusb:
   Bus 002 Device 006: ID 04f3:0210 Elan Microelectronics Corp. Optical Mouse
   Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: MEGAWARE H55H-CM
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-213-generic 
root=UUID=3cfdb2f5-e8ec-4728-844a-29c984321037 ro quiet splash vt.handoff=1
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080015
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: MW-H55H-CM
  dmi.board.vendor: MEGAWARE
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: M0418501001
  dmi.chassis.type: 3
  dmi.chassis.vendor: MEGAWARE
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr080015:bd05/18/2010:svnMEGAWARE:pnH55H-CM:pvrMEGAWARE:rvnMEGAWARE:rnMW-H55H-CM:rvr1.0:cvnMEGAWARE:ct3:cvr1.0:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: H55H-CM
  dmi.product.version: MEGAWARE
  dmi.sys.vendor: MEGAWARE
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.15
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Thu Apr  4 13:22:01 2024
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputPS/2+USB Mouse   MOUSE, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4.15

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/2061856/+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 2063228] Re: screen sometimes blinking

Please try adding a kernel parameter:

  i915.enable_psr=0

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

** Changed in: linux (Ubuntu)
   Status: Confirmed => 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/2063228

Title:
  screen sometimes blinking

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  My screen sometimes starts flashing strongly. I move the mouse cursor, it 
stops. I put the cursor back in its place, it starts again.
  I notice this with Firefox because I use it a lot, I don't know if this 
happens with other software.
  I'm under wayland (xwayland?)

  Description:  Ubuntu 24.04 LTS
  Release:  24.04

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 23 18:57:50 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company WhiskeyLake-U GT2 [UHD Graphics 620] 
[103c:84bb]
  InstallationDate: Installed on 2024-04-07 (16 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240407.2)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 003: ID 04ca:707f Lite-On Technology Corp. HP Wide Vision HD 
Camera
   Bus 001 Device 004: ID 0bda:b00a Realtek Semiconductor Corp. Realtek 
Bluetooth 4.2 Adapter
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  MachineType: HP HP Pavilion Laptop 14-ce2xxx
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic 
root=UUID=51f857d1-b81e-42fb-b485-6d1bf22759e4 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/23/2022
  dmi.bios.release: 15.27
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.27
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 84BB
  dmi.board.vendor: HP
  dmi.board.version: 15.32
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 15.32
  dmi.modalias: 
dmi:bvnInsyde:bvrF.27:bd11/23/2022:br15.27:efr15.32:svnHP:pnHPPavilionLaptop14-ce2xxx:pvrType1ProductConfigId:rvnHP:rn84BB:rvr15.32:cvnHP:ct10:cvrChassisVersion:sku8KZ34EA#ABF:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Laptop 14-ce2xxx
  dmi.product.sku: 8KZ34EA#ABF
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  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/+bug/2063228/+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 2063298] [NEW] deprecate ubuntu-fan in Noble

2024-04-23 Thread Andrea Righi

Public bug reported:

[Impact]

In order to provide ubuntu-fan we need to maintain additional kernel
SAUCE patches that are currently conflicting with upstream code,
potentially breaking networking eBPF APIs.

To prevent such incompatibility the whole patch set requires a major
redesign.

However, after investigations and a detailed assessment we have not
found any relevant real-world use-case that still requuires ubuntu-fan,
as most of its features are now available in the upstream kernel and
user-space tools, using alternative solutions.

Moreover, maintaining ubuntu-fan is also slowing down / preventing the
development of other packages (see for example LP: #2051672).

Therefore, we are proposing to deprecate ubuntu-fan starting with noble.

[Test case]

We have ubuntu-fan test cases in our regression testing suite. Such
tests are expected to fail with the noble kernel, so we can hint/disable
them in Noble.

[Fix]

Drop (do not apply) the ubuntu-fan SAUCE patch set from the Ubuntu
kernel.

[Regression potential]

There are still some existing tools/systems that may still rely on
ubuntu-fan, so we may experience regressions when such systems are
moving to noble. However, the potential of breaking eBPF networking has
a much higher impact, so we can probably workaround any potential
ubuntu-fan regression using alternative upstream solutions.

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

** Affects: iproute2 (Ubuntu Noble)
 Importance: Undecided
 Status: New

** Also affects: iproute2 (Ubuntu Noble)
   Importance: Undecided
   Status: New

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

Title:
  deprecate ubuntu-fan in Noble

Status in iproute2 package in Ubuntu:
  New
Status in iproute2 source package in Noble:
  New

Bug description:
  [Impact]

  In order to provide ubuntu-fan we need to maintain additional kernel
  SAUCE patches that are currently conflicting with upstream code,
  potentially breaking networking eBPF APIs.

  To prevent such incompatibility the whole patch set requires a major
  redesign.

  However, after investigations and a detailed assessment we have not
  found any relevant real-world use-case that still requuires ubuntu-
  fan, as most of its features are now available in the upstream kernel
  and user-space tools, using alternative solutions.

  Moreover, maintaining ubuntu-fan is also slowing down / preventing the
  development of other packages (see for example LP: #2051672).

  Therefore, we are proposing to deprecate ubuntu-fan starting with
  noble.

  [Test case]

  We have ubuntu-fan test cases in our regression testing suite. Such
  tests are expected to fail with the noble kernel, so we can
  hint/disable them in Noble.

  [Fix]

  Drop (do not apply) the ubuntu-fan SAUCE patch set from the Ubuntu
  kernel.

  [Regression potential]

  There are still some existing tools/systems that may still rely on
  ubuntu-fan, so we may experience regressions when such systems are
  moving to noble. However, the potential of breaking eBPF networking
  has a much higher impact, so we can probably workaround any potential
  ubuntu-fan regression using alternative upstream solutions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/2063298/+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 1811295] Re: systemctl daemon-reexec does not update group membership

2024-04-23 Thread Launchpad Bug Tracker

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

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

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

Title:
  systemctl daemon-reexec does not update group membership

Status in systemd package in Ubuntu:
  Expired

Bug description:
  On  Ubuntu 16.04.4 LTS  
  using 
  Package: systemd
  Architecture: amd64
  Version: 229-4ubuntu21.10

  Changes the group membership are not picked up by the systemd process
  for a logged-in user or for a user with enable-linger set regardless
  of login status.  Evidently the

systemctl --user daemon-reexec

  command preserves group membership across the daemon restart. This is
  bad. It means that only a reboot or

sudo loginctl terminate-user 

  will update the group membership to the proper set. Both of those
  things are extreme disruptions for a system/user that runs servers.

  Can systemctl daemon-reexec be made to update group membership for the
  user in the systemd process?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1811295/+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 2063222] Re: Ghost "unknown display" since upgrading to 24.04 beta

2024-04-23 Thread Daniel van Vugt

*** This bug is a duplicate of bug 2060268 ***
https://bugs.launchpad.net/bugs/2060268

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 2060268, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-535
(Ubuntu)

** This bug has been marked a duplicate of bug 2060268
   Phantom monitor (simpledrm) shown in Settings after installing the Nvidia 
driver

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

Title:
  Ghost "unknown display" since upgrading to 24.04 beta

Status in nvidia-graphics-drivers-535 package in Ubuntu:
  New

Bug description:
  X11
  GNOME
  NVIDIA 4080 with their driver

  ->

  GNOME settings has a "ghost" display called "Unknown Display", its
  resolution is 1024 x 768

  I only have one display attached - a 4K 27" DELL plugged into the
  NVIDIA

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.171.04  Tue Mar 19 
20:30:00 UTC 2024
   GCC version:  gcc version 13.2.0 (Ubuntu 13.2.0-23ubuntu4)
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 23 08:55:55 2024
  DistUpgraded: 2024-04-14 17:14:28,561 DEBUG migrateToDeb822Sources()
  DistroCodename: noble
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia/535.171.04, 6.8.0-28-generic, x86_64: installed
   nvidia/535.171.04, 6.8.0-31-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Subsystem: Micro-Star International Co., Ltd. [MSI] AlderLake-S GT1 
[1462:7d25]
   NVIDIA Corporation AD103 [GeForce RTX 4080] [10de:2704] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] AD103 [GeForce RTX 
4080] [1462:5111]
  InstallationDate: Installed on 2022-04-30 (724 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Micro-Star International Co., Ltd. MS-7D25
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: root=UUID=43e064ac-5857-4c85-b15d-1dd96cdad27b ro quiet 
splash vt.handoff=7 initrd=boot\initrd.img-6.8.0-31-generic
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to noble on 2024-04-15 (9 days ago)
  dmi.bios.date: 11/13/2023
  dmi.bios.release: 5.27
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: A.F0
  dmi.board.asset.tag: Default string
  dmi.board.name: PRO Z690-A WIFI (MS-7D25)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrA.F0:bd11/13/2023:br5.27:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D25:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnPROZ690-AWIFI(MS-7D25):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: MS-7D25
  dmi.product.sku: Default string
  dmi.product.version: 2.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1

[Touch-packages] [Bug 2063271] Re: Illegal opcode in libssl

2024-04-23 Thread Seth Arnold

** Package changed: openssh (Ubuntu) => openssl (Ubuntu)

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

Title:
  Illegal opcode in libssl

Status in openssl package in Ubuntu:
  New

Bug description:
  Many programs using openssl now fail, typically with messages such as

Illegal instruction (core dumped)

  This seems to be a serious error, since it affects, for example,
  update-manager. Since this makes it harder to get security updates, I
  would also consider it a security vulnerability.

  The issue seems to be that openssl seems to be an attempt to use an
  illegal opcode. A few sample entries in /var/log/syslog are:

  Apr 21 19:16:39 einstein kernel: [495465.431588] traps: 
update-manager[396881] trap invalid opcode ip:740964b8ac6b sp:7409552125b0 
error:0 in libssl.so.3[740964b7a000+5b000]
  Apr 21 19:16:55 einstein kernel: [495482.104658] traps: python3[396949] trap 
invalid opcode ip:73607be8ac6b sp:736074d8d5b0 error:0 in 
libssl.so.3[73607be7a000+5b000]
  Apr 21 19:40:05 einstein kernel: [496871.653271] traps: 
chrome-gnome-sh[397293] trap invalid opcode ip:79432ffa7c6b sp:7ffd6bc03e70 
error:0 in libssl.so.3[79432ff97000+5b000]
  Apr 22 16:23:08 einstein kernel: [501744.765118] traps: 
check-new-relea[400397] trap invalid opcode ip:797c7cc8ac6b sp:797c6cace5b0 
error:0 in libssl.so.3[797c7cc7a000+5b000]
  Apr 23 15:08:03 einstein kernel: [518701.050526] traps: wget[443588] trap 
invalid opcode ip:73a8b2eb4c6b sp:7ffc04918740 error:0 in 
libssl.so.3[73a8b2ea4000+5b000]
  Apr 23 15:12:55 einstein kernel: [518992.493020] traps: curl[443851] trap 
invalid opcode ip:7e4e3951dc6b sp:7ffc804d2ed0 error:0 in 
libssl.so.3[7e4e3950d000+5b000]
  Apr 23 15:13:32 einstein kernel: [519029.181422] traps: apport-gtk[04] 
trap invalid opcode ip:7039180f5c6b sp:703902bfaad0 error:0 in 
libssl.so.3[7039180e5000+5b000]

  This bug report itself had to be submitted manually since ubuntu-bug
  now itself fails.

  lsb_release -rd reports:

Description:Ubuntu 22.04.4 LTS
Release:22.04

  apt-cache policy openssl reports:

openssl:
  Installed: 3.0.2-0ubuntu1.15
  Candidate: 3.0.2-0ubuntu1.15
  Version table:
 *** 3.0.2-0ubuntu1.15 500
500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
100 /var/lib/dpkg/status
 3.0.2-0ubuntu1 500
 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  /proc/version for my computer gives

Linux version 6.5.0-28-generic (buildd@lcy02-amd64-098) 
(x86_64-linux-gnu-gcc-12 (Ubuntu 12.3.0-1ubuntu1~22.04) 12.3.0, GNU ld (GNU 
Binutils for Ubuntu) 2.38) #29~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu 
Apr  4 14:39:20 UTC 2

  /proc/cpuinfo for my computer starts

  processor : 0
  vendor_id : GenuineIntel
  cpu family: 6
  model : 78
  model name: Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz
  stepping  : 3
  microcode : 0xf0
  cpu MHz   : 500.018
  cache size: 4096 KB
  physical id   : 0
  siblings  : 4
  core id   : 0
  cpu cores : 2
  apicid: 0
  initial apicid: 0
  fpu   : yes
  fpu_exception : yes
  cpuid level   : 22
  wp: yes
  flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb 
rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology 
nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl est tm2 ssse3 
sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt 
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch 
cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp fsgsbase tsc_adjust 
bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt intel_pt 
xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify 
hwp_act_window hwp_epp md_clear flush_l1d arch_capabilities
  bugs  : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds 
swapgs itlb_multihit srbds mmio_stale_data retbleed gds
  bogomips  : 5199.98
  clflush size  : 64
  cache_alignment   : 64
  address sizes : 39 bits physical, 48 bits virtual
  power management:
  ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/2063271/+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 2061869] Re: Snaps unable to connect to network under linux-lowlatency 6.8.0-25.25.3

2024-04-23 Thread Seth Arnold

*** This bug is a duplicate of bug 2061851 ***
https://bugs.launchpad.net/bugs/2061851

** This bug has been marked a duplicate of bug 2061851
   linux-gcp 6.8.0-1005.5 (+ others) Noble kernel regression with new apparmor 
profiles/features

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

Title:
  Snaps unable to connect to network under linux-lowlatency
  6.8.0-25.25.3

Status in apparmor package in Ubuntu:
  Confirmed
Status in linux-lowlatency package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to linux-lowlatency 6.8.0-25, suddenly snaps can no
  longer connect to network. I tried downgrading snapd from edge, still
  no connectivity. Only solution was to downgrade back to 6.8.0-7. I'll
  also add apparmor in case this is an apparmor issue as well.

  Marking as "critical" priority as this affects all installs of Ubuntu
  Studio and affects Firefox and Thunderbird.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2061869/+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 2063271] Re: Illegal opcode in libssl

2024-04-23 Thread John Todd Palumbo

Thank you for your quick and helpful reply. A few quick checks make it
appear that reinstalling libssl as you suggested has completely resolved
the problem.

Thanks also for your suggestion about checking failing hardware. There
seems to be no sign of any errors in my drive, but I'll continue to test
the drive and my RAM. Perhaps it was just a stray cosmic ray.

Thanks again and best wishes to successful bug smashing!

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

Title:
  Illegal opcode in libssl

Status in openssh package in Ubuntu:
  New

Bug description:
  Many programs using openssl now fail, typically with messages such as

Illegal instruction (core dumped)

  This seems to be a serious error, since it affects, for example,
  update-manager. Since this makes it harder to get security updates, I
  would also consider it a security vulnerability.

  The issue seems to be that openssl seems to be an attempt to use an
  illegal opcode. A few sample entries in /var/log/syslog are:

  Apr 21 19:16:39 einstein kernel: [495465.431588] traps: 
update-manager[396881] trap invalid opcode ip:740964b8ac6b sp:7409552125b0 
error:0 in libssl.so.3[740964b7a000+5b000]
  Apr 21 19:16:55 einstein kernel: [495482.104658] traps: python3[396949] trap 
invalid opcode ip:73607be8ac6b sp:736074d8d5b0 error:0 in 
libssl.so.3[73607be7a000+5b000]
  Apr 21 19:40:05 einstein kernel: [496871.653271] traps: 
chrome-gnome-sh[397293] trap invalid opcode ip:79432ffa7c6b sp:7ffd6bc03e70 
error:0 in libssl.so.3[79432ff97000+5b000]
  Apr 22 16:23:08 einstein kernel: [501744.765118] traps: 
check-new-relea[400397] trap invalid opcode ip:797c7cc8ac6b sp:797c6cace5b0 
error:0 in libssl.so.3[797c7cc7a000+5b000]
  Apr 23 15:08:03 einstein kernel: [518701.050526] traps: wget[443588] trap 
invalid opcode ip:73a8b2eb4c6b sp:7ffc04918740 error:0 in 
libssl.so.3[73a8b2ea4000+5b000]
  Apr 23 15:12:55 einstein kernel: [518992.493020] traps: curl[443851] trap 
invalid opcode ip:7e4e3951dc6b sp:7ffc804d2ed0 error:0 in 
libssl.so.3[7e4e3950d000+5b000]
  Apr 23 15:13:32 einstein kernel: [519029.181422] traps: apport-gtk[04] 
trap invalid opcode ip:7039180f5c6b sp:703902bfaad0 error:0 in 
libssl.so.3[7039180e5000+5b000]

  This bug report itself had to be submitted manually since ubuntu-bug
  now itself fails.

  lsb_release -rd reports:

Description:Ubuntu 22.04.4 LTS
Release:22.04

  apt-cache policy openssl reports:

openssl:
  Installed: 3.0.2-0ubuntu1.15
  Candidate: 3.0.2-0ubuntu1.15
  Version table:
 *** 3.0.2-0ubuntu1.15 500
500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
100 /var/lib/dpkg/status
 3.0.2-0ubuntu1 500
 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  /proc/version for my computer gives

Linux version 6.5.0-28-generic (buildd@lcy02-amd64-098) 
(x86_64-linux-gnu-gcc-12 (Ubuntu 12.3.0-1ubuntu1~22.04) 12.3.0, GNU ld (GNU 
Binutils for Ubuntu) 2.38) #29~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu 
Apr  4 14:39:20 UTC 2

  /proc/cpuinfo for my computer starts

  processor : 0
  vendor_id : GenuineIntel
  cpu family: 6
  model : 78
  model name: Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz
  stepping  : 3
  microcode : 0xf0
  cpu MHz   : 500.018
  cache size: 4096 KB
  physical id   : 0
  siblings  : 4
  core id   : 0
  cpu cores : 2
  apicid: 0
  initial apicid: 0
  fpu   : yes
  fpu_exception : yes
  cpuid level   : 22
  wp: yes
  flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb 
rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology 
nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl est tm2 ssse3 
sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt 
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch 
cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp fsgsbase tsc_adjust 
bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt intel_pt 
xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify 
hwp_act_window hwp_epp md_clear flush_l1d arch_capabilities
  bugs  : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds 
swapgs itlb_multihit srbds mmio_stale_data retbleed gds
  bogomips  : 5199.98
  clflush size  : 64
  cache_alignment   : 64
  address sizes : 39 bits physical, 48 bits virtual
  power management:
  ...

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


-- 
Mailing list:

[Touch-packages] [Bug 2063228] Re: screen sometimes blinking

2024-04-23 Thread Launchpad Bug Tracker

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

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

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

Title:
  screen sometimes blinking

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  My screen sometimes starts flashing strongly. I move the mouse cursor, it 
stops. I put the cursor back in its place, it starts again.
  I notice this with Firefox because I use it a lot, I don't know if this 
happens with other software.
  I'm under wayland (xwayland?)

  Description:  Ubuntu 24.04 LTS
  Release:  24.04

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 23 18:57:50 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company WhiskeyLake-U GT2 [UHD Graphics 620] 
[103c:84bb]
  InstallationDate: Installed on 2024-04-07 (16 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240407.2)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 003: ID 04ca:707f Lite-On Technology Corp. HP Wide Vision HD 
Camera
   Bus 001 Device 004: ID 0bda:b00a Realtek Semiconductor Corp. Realtek 
Bluetooth 4.2 Adapter
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  MachineType: HP HP Pavilion Laptop 14-ce2xxx
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic 
root=UUID=51f857d1-b81e-42fb-b485-6d1bf22759e4 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/23/2022
  dmi.bios.release: 15.27
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.27
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 84BB
  dmi.board.vendor: HP
  dmi.board.version: 15.32
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 15.32
  dmi.modalias: 
dmi:bvnInsyde:bvrF.27:bd11/23/2022:br15.27:efr15.32:svnHP:pnHPPavilionLaptop14-ce2xxx:pvrType1ProductConfigId:rvnHP:rn84BB:rvr15.32:cvnHP:ct10:cvrChassisVersion:sku8KZ34EA#ABF:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Laptop 14-ce2xxx
  dmi.product.sku: 8KZ34EA#ABF
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  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/2063228/+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 2063271] Re: Illegal opcode in libssl

2024-04-23 Thread Alex Murray

Thanks for reporting this issue - but it is strange since this update
has been published since 2024-02-27 and this is the first such report of
any issues.

Also given this update has been available for nearly 2 months it is
surprising you are seeing errors from it so much later - I wonder if
instead whether the on-disk binary has been corrupted? Can you please
try reinstalling libssl3 and see if that resolves the issue:

sudo apt install --reinstall libssl3

If this does resolve the issue, it might be worth checking whether you
have any failing hardware / disks etc that may have led to this problem.

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

Title:
  Illegal opcode in libssl

Status in openssh package in Ubuntu:
  New

Bug description:
  Many programs using openssl now fail, typically with messages such as

Illegal instruction (core dumped)

  This seems to be a serious error, since it affects, for example,
  update-manager. Since this makes it harder to get security updates, I
  would also consider it a security vulnerability.

  The issue seems to be that openssl seems to be an attempt to use an
  illegal opcode. A few sample entries in /var/log/syslog are:

  Apr 21 19:16:39 einstein kernel: [495465.431588] traps: 
update-manager[396881] trap invalid opcode ip:740964b8ac6b sp:7409552125b0 
error:0 in libssl.so.3[740964b7a000+5b000]
  Apr 21 19:16:55 einstein kernel: [495482.104658] traps: python3[396949] trap 
invalid opcode ip:73607be8ac6b sp:736074d8d5b0 error:0 in 
libssl.so.3[73607be7a000+5b000]
  Apr 21 19:40:05 einstein kernel: [496871.653271] traps: 
chrome-gnome-sh[397293] trap invalid opcode ip:79432ffa7c6b sp:7ffd6bc03e70 
error:0 in libssl.so.3[79432ff97000+5b000]
  Apr 22 16:23:08 einstein kernel: [501744.765118] traps: 
check-new-relea[400397] trap invalid opcode ip:797c7cc8ac6b sp:797c6cace5b0 
error:0 in libssl.so.3[797c7cc7a000+5b000]
  Apr 23 15:08:03 einstein kernel: [518701.050526] traps: wget[443588] trap 
invalid opcode ip:73a8b2eb4c6b sp:7ffc04918740 error:0 in 
libssl.so.3[73a8b2ea4000+5b000]
  Apr 23 15:12:55 einstein kernel: [518992.493020] traps: curl[443851] trap 
invalid opcode ip:7e4e3951dc6b sp:7ffc804d2ed0 error:0 in 
libssl.so.3[7e4e3950d000+5b000]
  Apr 23 15:13:32 einstein kernel: [519029.181422] traps: apport-gtk[04] 
trap invalid opcode ip:7039180f5c6b sp:703902bfaad0 error:0 in 
libssl.so.3[7039180e5000+5b000]

  This bug report itself had to be submitted manually since ubuntu-bug
  now itself fails.

  lsb_release -rd reports:

Description:Ubuntu 22.04.4 LTS
Release:22.04

  apt-cache policy openssl reports:

openssl:
  Installed: 3.0.2-0ubuntu1.15
  Candidate: 3.0.2-0ubuntu1.15
  Version table:
 *** 3.0.2-0ubuntu1.15 500
500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
100 /var/lib/dpkg/status
 3.0.2-0ubuntu1 500
 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  /proc/version for my computer gives

Linux version 6.5.0-28-generic (buildd@lcy02-amd64-098) 
(x86_64-linux-gnu-gcc-12 (Ubuntu 12.3.0-1ubuntu1~22.04) 12.3.0, GNU ld (GNU 
Binutils for Ubuntu) 2.38) #29~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu 
Apr  4 14:39:20 UTC 2

  /proc/cpuinfo for my computer starts

  processor : 0
  vendor_id : GenuineIntel
  cpu family: 6
  model : 78
  model name: Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz
  stepping  : 3
  microcode : 0xf0
  cpu MHz   : 500.018
  cache size: 4096 KB
  physical id   : 0
  siblings  : 4
  core id   : 0
  cpu cores : 2
  apicid: 0
  initial apicid: 0
  fpu   : yes
  fpu_exception : yes
  cpuid level   : 22
  wp: yes
  flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb 
rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology 
nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl est tm2 ssse3 
sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt 
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch 
cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp fsgsbase tsc_adjust 
bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt intel_pt 
xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify 
hwp_act_window hwp_epp md_clear flush_l1d arch_capabilities
  bugs  : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds 
swapgs itlb_multihit srbds mmio_stale_data retbleed gds
  bogomips  : 5199.98
  clflush size  : 64
  cache_alignment   : 64
  address sizes : 39 bits physical, 48

[Touch-packages] [Bug 2063271] Re: Illegal opcode in libssl

2024-04-23 Thread John Todd Palumbo

** Information type changed from Private Security to Public

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

Title:
  Illegal opcode in libssl

Status in openssh package in Ubuntu:
  New

Bug description:
  Many programs using openssl now fail, typically with messages such as

Illegal instruction (core dumped)

  This seems to be a serious error, since it affects, for example,
  update-manager. Since this makes it harder to get security updates, I
  would also consider it a security vulnerability.

  The issue seems to be that openssl seems to be an attempt to use an
  illegal opcode. A few sample entries in /var/log/syslog are:

  Apr 21 19:16:39 einstein kernel: [495465.431588] traps: 
update-manager[396881] trap invalid opcode ip:740964b8ac6b sp:7409552125b0 
error:0 in libssl.so.3[740964b7a000+5b000]
  Apr 21 19:16:55 einstein kernel: [495482.104658] traps: python3[396949] trap 
invalid opcode ip:73607be8ac6b sp:736074d8d5b0 error:0 in 
libssl.so.3[73607be7a000+5b000]
  Apr 21 19:40:05 einstein kernel: [496871.653271] traps: 
chrome-gnome-sh[397293] trap invalid opcode ip:79432ffa7c6b sp:7ffd6bc03e70 
error:0 in libssl.so.3[79432ff97000+5b000]
  Apr 22 16:23:08 einstein kernel: [501744.765118] traps: 
check-new-relea[400397] trap invalid opcode ip:797c7cc8ac6b sp:797c6cace5b0 
error:0 in libssl.so.3[797c7cc7a000+5b000]
  Apr 23 15:08:03 einstein kernel: [518701.050526] traps: wget[443588] trap 
invalid opcode ip:73a8b2eb4c6b sp:7ffc04918740 error:0 in 
libssl.so.3[73a8b2ea4000+5b000]
  Apr 23 15:12:55 einstein kernel: [518992.493020] traps: curl[443851] trap 
invalid opcode ip:7e4e3951dc6b sp:7ffc804d2ed0 error:0 in 
libssl.so.3[7e4e3950d000+5b000]
  Apr 23 15:13:32 einstein kernel: [519029.181422] traps: apport-gtk[04] 
trap invalid opcode ip:7039180f5c6b sp:703902bfaad0 error:0 in 
libssl.so.3[7039180e5000+5b000]

  This bug report itself had to be submitted manually since ubuntu-bug
  now itself fails.

  lsb_release -rd reports:

Description:Ubuntu 22.04.4 LTS
Release:22.04

  apt-cache policy openssl reports:

openssl:
  Installed: 3.0.2-0ubuntu1.15
  Candidate: 3.0.2-0ubuntu1.15
  Version table:
 *** 3.0.2-0ubuntu1.15 500
500 http://us.archive.ubuntu.com/ubuntu jammy-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 
Packages
100 /var/lib/dpkg/status
 3.0.2-0ubuntu1 500
 500 http://us.archive.ubuntu.com/ubuntu jammy/main amd64 Packages

  /proc/version for my computer gives

Linux version 6.5.0-28-generic (buildd@lcy02-amd64-098) 
(x86_64-linux-gnu-gcc-12 (Ubuntu 12.3.0-1ubuntu1~22.04) 12.3.0, GNU ld (GNU 
Binutils for Ubuntu) 2.38) #29~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu 
Apr  4 14:39:20 UTC 2

  /proc/cpuinfo for my computer starts

  processor : 0
  vendor_id : GenuineIntel
  cpu family: 6
  model : 78
  model name: Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz
  stepping  : 3
  microcode : 0xf0
  cpu MHz   : 500.018
  cache size: 4096 KB
  physical id   : 0
  siblings  : 4
  core id   : 0
  cpu cores : 2
  apicid: 0
  initial apicid: 0
  fpu   : yes
  fpu_exception : yes
  cpuid level   : 22
  wp: yes
  flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb 
rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology 
nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl est tm2 ssse3 
sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt 
tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch 
cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp fsgsbase tsc_adjust 
bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt intel_pt 
xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify 
hwp_act_window hwp_epp md_clear flush_l1d arch_capabilities
  bugs  : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds 
swapgs itlb_multihit srbds mmio_stale_data retbleed gds
  bogomips  : 5199.98
  clflush size  : 64
  cache_alignment   : 64
  address sizes : 39 bits physical, 48 bits virtual
  power management:
  ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2063271/+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 2039294] Re: apparmor docker

2024-04-23 Thread Tomáš Virtus

As a temporary workaround, put the file I have attached to
/etc/apparmor.d/docker-default and load it with "apparmor_parser -Kr
/etc/apparmor.d/docker-default". This will make dockerd skip loading its
builtin profile and use this one instead. The only difference between
the builtin one and this one is the following rule:

  # runc may send signals to container processes
  signal (receive) peer=runc,

I've opened PRs upstream:
- https://github.com/containerd/containerd/pull/10123
- https://github.com/moby/moby/pull/47749

I think I'll need to work a little bit more on them to add rules only
for profiles that exist. (It works even if they don't exist though.)

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

Title:
  apparmor docker

Status in docker:
  New
Status in apparmor package in Ubuntu:
  Incomplete

Bug description:
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 23.10
  Release:23.10
  Codename:   mantic

  
  Docker version 24.0.5, build 24.0.5-0ubuntu1

  
  Graceful shutdown doesn't work anymore due to SIGTERM and SIGKILL (maybe all 
signals?) doesn't reach the target process. Works when apparmor is uninstalled.

  
  [17990.085295] audit: type=1400 audit(1697213244.019:981): apparmor="DENIED" 
operation="signal" class="signal" profile="docker-default" pid=172626 
comm="runc" requested_mask="receive" denied_mask="receive" signal=term 
peer="/usr/sbin/runc"
  [17992.112517] audit: type=1400 audit(1697213246.043:982): apparmor="DENIED" 
operation="signal" class="signal" profile="docker-default" pid=172633 
comm="runc" requested_mask="receive" denied_mask="receive" signal=kill 
peer="/usr/sbin/runc"

To manage notifications about this bug go to:
https://bugs.launchpad.net/docker/+bug/2039294/+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 2039294] Re: apparmor docker

2024-04-23 Thread Tomáš Virtus

Forgot to attach the profile. Attached here.

** Attachment added: "docker-default"
   
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2039294/+attachment/5769855/+files/docker-default

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

Title:
  apparmor docker

Status in docker:
  New
Status in apparmor package in Ubuntu:
  Incomplete

Bug description:
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 23.10
  Release:23.10
  Codename:   mantic

  
  Docker version 24.0.5, build 24.0.5-0ubuntu1

  
  Graceful shutdown doesn't work anymore due to SIGTERM and SIGKILL (maybe all 
signals?) doesn't reach the target process. Works when apparmor is uninstalled.

  
  [17990.085295] audit: type=1400 audit(1697213244.019:981): apparmor="DENIED" 
operation="signal" class="signal" profile="docker-default" pid=172626 
comm="runc" requested_mask="receive" denied_mask="receive" signal=term 
peer="/usr/sbin/runc"
  [17992.112517] audit: type=1400 audit(1697213246.043:982): apparmor="DENIED" 
operation="signal" class="signal" profile="docker-default" pid=172633 
comm="runc" requested_mask="receive" denied_mask="receive" signal=kill 
peer="/usr/sbin/runc"

To manage notifications about this bug go to:
https://bugs.launchpad.net/docker/+bug/2039294/+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 2063257] Re: Noble: default pam config for login tries do load non-existent pam_lastlog.so

2024-04-23 Thread Bug Watch Updater

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

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

Title:
  Noble: default pam config for login tries do load non-existent
  pam_lastlog.so

Status in shadow package in Ubuntu:
  New
Status in shadow source package in Noble:
  New
Status in shadow package in Debian:
  New

Bug description:
  pam_lastlog.so was dropped by upstream in 1.5.3[1][4]. It's still
  there in the code, but not built by default.

  And indeed, in noble (1.5.3) we don't have it, while mantic (1.5.2)
  does.

  This does not prevent console logins, but generates an error in the logs:
  Apr 23 20:02:09 n1 login[835]: PAM unable to dlopen(pam_lastlog.so): 
/usr/lib/security/pam_lastlog.so: cannot open shared object file: No such file 
or directory
  Apr 23 20:02:09 n1 login[835]: PAM adding faulty module: pam_lastlog.so

  Debian's shadow package is also still shipping this config[2].

  If you think we should re-enable pam_lastlog, then this becomes a bug
  in the src:pam package, but keep in mind upstream is keen on removing
  it, and we might be better off switching to an alternative, perhaps
  pam_lastlog2[3].

  1. 
https://github.com/linux-pam/linux-pam/blob/cec36a8cd2c69cc87eacc21da471334fbef128ee/NEWS#L65
  2. 
https://salsa.debian.org/debian/shadow/-/blob/master/debian/login.pam?ref_type=heads#L82
  3. https://wiki.debian.org/PamLastlog2
  4. 
https://github.com/linux-pam/linux-pam/commit/357a4ddbe9b4b10ebd805d2af3e32f3ead5b8816

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/2063257/+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 2063257] [NEW] Noble: default pam config for login tries do load non-existent pam_lastlog.so

2024-04-23 Thread Andreas Hasenack

Public bug reported:

pam_lastlog.so was dropped by upstream in 1.5.3[1][4]. It's still there
in the code, but not built by default.

And indeed, in noble (1.5.3) we don't have it, while mantic (1.5.2)
does.

This does not prevent console logins, but generates an error in the logs:
Apr 23 20:02:09 n1 login[835]: PAM unable to dlopen(pam_lastlog.so): 
/usr/lib/security/pam_lastlog.so: cannot open shared object file: No such file 
or directory
Apr 23 20:02:09 n1 login[835]: PAM adding faulty module: pam_lastlog.so

Debian's shadow package is also still shipping this config[2].

If you think we should re-enable pam_lastlog, then this becomes a bug in
the src:pam package, but keep in mind upstream is keen on removing it,
and we might be better off switching to an alternative, perhaps
pam_lastlog2[3].

1. 
https://github.com/linux-pam/linux-pam/blob/cec36a8cd2c69cc87eacc21da471334fbef128ee/NEWS#L65
2. 
https://salsa.debian.org/debian/shadow/-/blob/master/debian/login.pam?ref_type=heads#L82
3. https://wiki.debian.org/PamLastlog2
4. 
https://github.com/linux-pam/linux-pam/commit/357a4ddbe9b4b10ebd805d2af3e32f3ead5b8816

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

** Affects: shadow (Ubuntu Noble)
 Importance: Undecided
 Status: New

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

** Summary changed:

- Default pam config for login tries do load non-existent pam module 
pam_lastlog.so
+ Noble: default pam config for login tries do load non-existent pam module 
pam_lastlog.so

** Also affects: shadow (Ubuntu Noble)
   Importance: Undecided
   Status: New

** Summary changed:

- Noble: default pam config for login tries do load non-existent pam module 
pam_lastlog.so
+ Noble: default pam config for login tries do load non-existent pam_lastlog.so

** Description changed:

  pam_lastlog.so was dropped by upstream in 1.5.3[1]. It's still there in
  the code, but not built by default.
  
  And indeed, in noble (1.5.3) we don't have it, while mantic (1.5.2)
  does.
  
- 
  This does not prevent console logins, but generates an error in the logs:
  Apr 23 20:02:09 n1 login[835]: PAM unable to dlopen(pam_lastlog.so): 
/usr/lib/security/pam_lastlog.so: cannot open shared object file: No such file 
or directory
  Apr 23 20:02:09 n1 login[835]: PAM adding faulty module: pam_lastlog.so
  
+ Debian's shadow package is also still shipping this config[2].
  
- Debian's shadow package is also still shipping this config[2].
+ If you think we should re-enable pam_lastlog, then this becomes a bug in
+ the src:pam package, but keep in mind upstream is keen on removing it,
+ and we might be better off switching to an alternative, perhaps
+ pam_lastlog2[3].
  
  
  1. 
https://github.com/linux-pam/linux-pam/blob/cec36a8cd2c69cc87eacc21da471334fbef128ee/NEWS#L65
  2. 
https://salsa.debian.org/debian/shadow/-/blob/master/debian/login.pam?ref_type=heads#L82
+ 3. https://wiki.debian.org/PamLastlog2

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

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

** Description changed:

- pam_lastlog.so was dropped by upstream in 1.5.3[1]. It's still there in
- the code, but not built by default.
+ pam_lastlog.so was dropped by upstream in 1.5.3[1][4]. It's still there
+ in the code, but not built by default.
  
  And indeed, in noble (1.5.3) we don't have it, while mantic (1.5.2)
  does.
  
  This does not prevent console logins, but generates an error in the logs:
  Apr 23 20:02:09 n1 login[835]: PAM unable to dlopen(pam_lastlog.so): 
/usr/lib/security/pam_lastlog.so: cannot open shared object file: No such file 
or directory
  Apr 23 20:02:09 n1 login[835]: PAM adding faulty module: pam_lastlog.so
  
  Debian's shadow package is also still shipping this config[2].
  
  If you think we should re-enable pam_lastlog, then this becomes a bug in
  the src:pam package, but keep in mind upstream is keen on removing it,
  and we might be better off switching to an alternative, perhaps
  pam_lastlog2[3].
  
- 
  1. 
https://github.com/linux-pam/linux-pam/blob/cec36a8cd2c69cc87eacc21da471334fbef128ee/NEWS#L65
  2. 
https://salsa.debian.org/debian/shadow/-/blob/master/debian/login.pam?ref_type=heads#L82
  3. https://wiki.debian.org/PamLastlog2
+ 4. 
https://github.com/linux-pam/linux-pam/commit/357a4ddbe9b4b10ebd805d2af3e32f3ead5b8816

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

Title:
  Noble: default pam config for login tries do load non-existent
  pam_lastlog.so

Status in shadow package in Ubuntu:
  New
Status in shadow source package in Noble:
  New
Status in shadow package in Debian:
  Unknown

Bug description:
  pam_lastlog.so was dropped by

[Touch-packages] [Bug 1958019]

2024-04-23 Thread shenghao-ding

# . tas2781-2dev-on.sh 2

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

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

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

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

  uname -r
  5.11.0-44-generic

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

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


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

[Touch-packages] [Bug 1958019]

2024-04-23 Thread cam

(In reply to Tintin from comment #869)
> kindly run 
> #i2cdetect -r 2
> and run following command during no sound issue 
> dmesg -c > kernel-mute.log

Forgot to get the dmesg even though I did look at the dmesg output
(*facepalm*). There are no messages related to this in dmesg when this
occurs. But next time it happens, I'll get this to you to be thorough
and Just In Case.

i2cdetect -r 2
# When it's working:
i2cdetect -y -r 2
 0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00: -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- UU -- -- -- -- -- -- 3f
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --

# When it's not working:
i2cdetect -y -r 2
 0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
00: -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- UU -- -- -- -- -- -- 3f
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --

I tried on i2cbus 0 and 1, no changes there either.

This time I finally remembered to try hibernating (suspend to disk).
Resuming didn't fix the issue.

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

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

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

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

  uname -r
  5.11.0-44-generic

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

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


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

[Touch-packages] [Bug 1958019]

2024-04-23 Thread shenghao-ding

Save following as tas2781-2dev-on.sh
run ". tas2781-2dev-on.sh" in root mode during no sound, and check whether to 
work?
Start###
#!/bin/sh
# echo Turn on log!
# set -x
clear
function clear_stdin()
(
old_tty_settings=`stty -g`
stty -icanon min 0 time 0

while read none; do :; done

stty "$old_tty_settings"
)

if [ $# -ne 1 ];
then
echo Kindly specify the i2c bus number. The default i2c bus number is 3.
echo Command as following:
echo $0 i2c-bus-number
i2c_bus=3
else
i2c_bus=$1
fi

echo i2c bus is $i2c_bus
i2c_addr=(0x3f 0x38)

count=0
for value in ${i2c_addr[@]};
do
val=$((${count} % 2))
i2cset -f -y $i2c_bus $value 0x00 0x00
i2cset -f -y $i2c_bus $value 0x7f 0x00
i2cset -f -y $i2c_bus $value 0x01 0x01
i2cset -f -y $i2c_bus $value 0x0e 0xc4
i2cset -f -y $i2c_bus $value 0x0f 0x40
i2cset -f -y $i2c_bus $value 0x5c 0xd9
i2cset -f -y $i2c_bus $value 0x60 0x10
if [ $val -eq 0 ];
then
i2cset -f -y $i2c_bus $value 0x0a 0x1e
else
i2cset -f -y $i2c_bus $value 0x0a 0x2e
fi
i2cset -f -y $i2c_bus $value 0x0d 0x01
i2cset -f -y $i2c_bus $value 0x16 0x40
i2cset -f -y $i2c_bus $value 0x00 0x01
i2cset -f -y $i2c_bus $value 0x17 0xc8
i2cset -f -y $i2c_bus $value 0x00 0x04
i2cset -f -y $i2c_bus $value 0x30 0x00
i2cset -f -y $i2c_bus $value 0x31 0x00
i2cset -f -y $i2c_bus $value 0x32 0x00
i2cset -f -y $i2c_bus $value 0x33 0x01

i2cset -f -y $i2c_bus $value 0x00 0x08
i2cset -f -y $i2c_bus $value 0x18 0x00
i2cset -f -y $i2c_bus $value 0x19 0x00
i2cset -f -y $i2c_bus $value 0x1a 0x00
i2cset -f -y $i2c_bus $value 0x1b 0x00
i2cset -f -y $i2c_bus $value 0x28 0x40
i2cset -f -y $i2c_bus $value 0x29 0x00
i2cset -f -y $i2c_bus $value 0x2a 0x00
i2cset -f -y $i2c_bus $value 0x2b 0x00

i2cset -f -y $i2c_bus $value 0x00 0x0a
i2cset -f -y $i2c_bus $value 0x48 0x00
i2cset -f -y $i2c_bus $value 0x49 0x00
i2cset -f -y $i2c_bus $value 0x4a 0x00
i2cset -f -y $i2c_bus $value 0x4b 0x00
i2cset -f -y $i2c_bus $value 0x58 0x40
i2cset -f -y $i2c_bus $value 0x59 0x00
i2cset -f -y $i2c_bus $value 0x5a 0x00
i2cset -f -y $i2c_bus $value 0x5b 0x00

i2cset -f -y $i2c_bus $value 0x00 0x00
i2cset -f -y $i2c_bus $value 0x02 0x00
count=$((${count} + 1))
done;
clear_stdin
End###

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

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

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

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

  uname -r
  5.11.0-44-generic

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

[Touch-packages] [Bug 1958019]

2024-04-23 Thread shenghao-ding

(In reply to dreamsyntax from comment #867)
> While audio working, and content is playing (actively outputting to device)
> Output is different:
> i2cset -y 2 0x38 0x00 0x00
> i2cset -y 2 0x38 0x7f 0x00
> i2cdump -y 2 0x38
> No size specified (using byte-data access)
>  0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f0123456789abcdef
> 00: 00 00 00 28 21 41 00 20 09 02 2a 28 10 93 02 00...(!A. ??*(???.
> 10: 84 00 00 08 0a 00 44 80 00 8d 00 62 36 40 00 01?..??.D?.?.b6@.?
> 20: 2e 14 00 00 00 00 00 00 00 00 00 00 00 00 00 00.?..
> 30: 00 00 00 00 06 bd ad a8 00 00 00 fc bb dd ff ff...???..
> 40: f6 14 00 02 19 00 00 00 00 04 02 19 80 00 5c 00??.??.\.
> 50: 00 06 a3 3c 85 08 81 da 87 84 00 97 d9 81 01 00.?? 60: 21 08 3c 48 84 88 b2 00 04 09 12 63 00 1a 03 00!? 70: 96 02 00 08 00 e0 00 00 0f 00 20 00 a0 00 25 00??.?.?..?. .?.%.
> 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

Kindly follow Comment 872 to force tas2781 to work

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

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

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

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

  uname -r
  5.11.0-44-generic

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

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


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

[Touch-packages] [Bug 2062979] Re: unable to create ubuntu-noble image due to dictionaries-common config failure

2024-04-23 Thread Julian Andres Klode

I'm unsubscribing as I only did a no-change rebuild. I'd generally
advise against using LC_ALL=C in any setting however, it's generally a
bad idea and you should use LC_ALL=C.UTF-8 instead.

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

Title:
  unable to create ubuntu-noble image due to dictionaries-common config
  failure

Status in aspell package in Ubuntu:
  New
Status in dictionaries-common package in Ubuntu:
  New

Bug description:
  this is running with LC_ALL=C

  the following are output in terminal when configuring dictionaries-
  common

  Setting up dictionaries-common (1.29.7) ...
  Processing triggers for dictionaries-common (1.29.7) ...
  aspell-autobuildhash: processing: en [en-common].
  Error: /dev/null:1: The key "/usr/bin/aspell" is unknown.
  Undefined subroutine ::subst called at /usr/sbin/aspell-autobuildhash 
line 54.
  dpkg: error processing package dictionaries-common (--configure):
   installed dictionaries-common package post-installation script subprocess 
returned error exit status 2
  Errors were encountered while processing:
   dictionaries-common

  this worked without issues when I last built images of ubuntu-noble in
  late February 2024

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aspell/+bug/2062979/+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 1809174] Re: apt doesn't detect file corruption in /var/lib/apt/lists

2024-04-23 Thread Charles Brian Quinn

Just saw this on some field units that are iOT type devices and
sometimes get shutdown non-cleanly.  We run apt-update on startup and we
noticed one machine would not update and had no knowledge of any
packages in one of the repos in the sources.list.

We noticed the Packages file has 0 size, and no amount of apt update or
apt-cache clean could fix it besides deleting/removing the corrupt file.

Deleting it resolved the issue:

```
$ ls -lat /var/lib/apt/lists/
total 71252
drwx-- 2 _apt root 4096 Apr 23 16:18 partial
drwxr-xr-x 5 root root 4096 Apr 23 15:40 ..
drwxr-xr-x 4 root root 4096 Apr 22 21:13 .
-rw-r--r-- 1 root root 4342 Apr 22 20:12 
[redacted-package-server]-experimental_dists_focal_InRelease
-rw-r--r-- 1 root root0 Apr 22 20:12 
[redacted-package-server]-experimental_dists_focal_main_binary-amd64_Packages
-rw-r--r-- 1 root root 4362 Jan 27  2023 
[redacted-package-server]-ubuntu-experimental_dists_focal_InRelease
```

Note the 0 file size on the `[redacted-package-
server]-experimental_dists_focal_main_binary-amd64_Packages` file.

During this time, it would not Get any new information from the package
server.  Even with updates pushed to the package server.

After removing the file, it does a `Get` and now can see all the
packages again:

$ sudo mv 
/var/lib/apt/lists/[redacted-package-server]-experimental_dists_focal_main_binary-amd64_Packages
$ sudo apt update
Hit:1 [redacted-server]-experimental focal InRelease
Hit:2 [redacted-server]-ubuntu-experimental focal InRelease
Get:3 [redacted-server]-experimental focal/main amd64 Packages [3524 kB]
Fetched 3524 kB in 6s (571 kB/s)
 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
27 packages can be upgraded. Run 'apt list --upgradable' to see them.
```

Server software is aptly.  apt version is `apt 2.0.6 (amd64)`

Happy to track this down and submit a patch for checking the file size
of 0, or the algorithm as suggested above.

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

Title:
  apt doesn't detect file corruption in /var/lib/apt/lists

Status in apt package in Ubuntu:
  Triaged

Bug description:
  The Problem
  ==

  /var/lib/apt/lists contains the repository index caches or similar;
  I'm not sure what the correct  apt-terminology is.

  I've installed Chrome on my laptop, so I have:

  smacdonald@L247:/var/lib/apt/lists$ dir *goog*
  -rw-r--r-- 1 root root  943 Dec 19 14:02 
dl.google.com_linux_chrome_deb_dists_stable_Release
  -rw-r--r-- 1 root root  819 Dec 19 14:02 
dl.google.com_linux_chrome_deb_dists_stable_Release.gpg
  -rw-r--r-- 1 root root 4457 Dec 19 14:02 
dl.google.com_linux_chrome_deb_dists_stable_main_binary-amd64_Packages

  for example.

  
  dl.google.com_linux_chrome_deb_dists_stable_Release contains checksums for 
the dl.google.com_linux_chrome_deb_dists_stable_main_binary-amd64_Packages file:

  smacdonald@L247:/var/lib/apt/lists$ cat 
dl.google.com_linux_chrome_deb_dists_stable_Release
  Origin: Google LLC
  Label: Google
  Suite: stable
  Codename: stable
  Version: 1.0
  Date: Wed, 19 Dec 2018 18:51:54 UTC
  Architectures: amd64
  Components: main
  Description: Google chrome-linux software repository
  MD5Sum:
   9e0d0ad6a4f5ccf8e3971c32e9bb22d3 4457 main/binary-amd64/Packages
   a17f6de0ef487b82af58ccd91df52d04 1109 main/binary-amd64/Packages.gz
   156e5ea7a0c6bed5973a68a45e546dc9 151 main/binary-amd64/Release
  SHA1:
   4c2cde4f71476d7881262d9a07e33cf4506232a7 4457 main/binary-amd64/Packages
   e002924c9ddfe41ee2033594ec768ed9e4545909 1109 main/binary-amd64/Packages.gz
   0f4348c2d4d7cc1f8e59b5934d87f1ca872f6e34 151 main/binary-amd64/Release
  SHA256:
   fb0e586c2b5ec5afa17965d0bbc6bd46c2071336f75e2b0f0c7f3e7b090a7844 4457 
main/binary-amd64/Packages
   2462cff732765679a56373a7ca9a5b8b029fdb445e707b1aba10d01fbdb853b3 1109 
main/binary-amd64/Packages.gz
   c1e3c9318381862306adcdc4fd4fe2d85be8aa4c4f3dcbb40fce80413f588286 151 
main/binary-amd64/Release

  
  If the dl.google.com_linux_chrome_deb_dists_stable_main_binary-amd64_Packages 
file has become corrupt in the specific manner of being 0 bytes in length, apt 
does not detect this, and the repository is effectively unreachable until one 
of two things occurs: a) the repository has an update causing apt to re-fetch 
the repository information and accidentally fix-by-over-writing the corrupt 0 
byte file, or, b) the user removes the corrupt 0-byte file and does an apt 
update to refetch the repository information.

  
  The Context
  ==

  Our IoT devices run Ubuntu 16.04, and their main storage is eMMC.
  Sometimes there are

[Touch-packages] [Bug 2062979] Re: unable to create ubuntu-noble image due to dictionaries-common config failure

2024-04-23 Thread theofficialgman

Adding Julian Andres Klode as a subscriber as seemingly this could only
be due to the recent package update from aspell
https://changelogs.ubuntu.com/changelogs/pool/main/a/aspell/aspell_0.60.8.1-1build1/changelog

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

Title:
  unable to create ubuntu-noble image due to dictionaries-common config
  failure

Status in aspell package in Ubuntu:
  New
Status in dictionaries-common package in Ubuntu:
  New

Bug description:
  this is running with LC_ALL=C

  the following are output in terminal when configuring dictionaries-
  common

  Setting up dictionaries-common (1.29.7) ...
  Processing triggers for dictionaries-common (1.29.7) ...
  aspell-autobuildhash: processing: en [en-common].
  Error: /dev/null:1: The key "/usr/bin/aspell" is unknown.
  Undefined subroutine ::subst called at /usr/sbin/aspell-autobuildhash 
line 54.
  dpkg: error processing package dictionaries-common (--configure):
   installed dictionaries-common package post-installation script subprocess 
returned error exit status 2
  Errors were encountered while processing:
   dictionaries-common

  this worked without issues when I last built images of ubuntu-noble in
  late February 2024

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aspell/+bug/2062979/+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 2063221] Re: Drop libglib2.0-0 transitional package

2024-04-23 Thread Jeremy Bícha

** Tags added: block-proposed

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

Title:
  Drop libglib2.0-0 transitional package

Status in glib2.0 package in Ubuntu:
  In Progress
Status in glib2.0 source package in Noble:
  In Progress

Bug description:
  Impact
  --
  apt can struggle with ordering when handling the massive Y2028 time_t 
transition when upgrading to Ubuntu 24.04 LTS.

  It was identified that dropping the libglib2.0-0 transitional package
  can help apt do things in the correct order.

  Test Case
  -
  Is libglib2.0-0 built?

  Other Info
  --
  This is related to LP: #2061918 for the thunderbird deb to snap upgrade

  There are likely several other Launchpad bugs that can be resolved by
  this update and some other workarounds in other packages, like in the
  transitional thunderbird package.

  https://salsa.debian.org/gnome-team/glib/-/merge_requests/34

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2063221/+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 1451978] Re: ubuntu-app-launch fails to install trying to access cache folder of another user

2024-04-23 Thread Launchpad Bug Tracker

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

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

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

Title:
  ubuntu-app-launch fails to install trying to access cache folder of
  another user

Status in click package in Ubuntu:
  Confirmed

Bug description:
  I'm experiencing problems updating my system. The exact issue can be
  narrowed down to the ubuntu-app-launch package failing to configure
  because it tries to access the cache folder of another user.

  > whoami
  rumo
  > sudo dpkg --configure ubuntu-app-launch
  ubuntu-app-launch (0.4+15.04.20150410-0ubuntu1) wird eingerichtet ...
  Traceback (most recent call last):
File "/usr/bin/click", line 86, in 
  sys.exit(main())
File "/usr/bin/click", line 82, in main
  return mod.run(args)
File "/usr/lib/python3/dist-packages/click/commands/hook.py", line 63, in 
run
  getattr(hook, per_hook_subcommands[subcommand])(user_name=None)
  GLib.Error: g-file-error-quark: ensuredir 
/home/kalikiana/.cache/ubuntu-app-launch/desktop failed: Permission denied (2)
  dpkg: Fehler beim Bearbeiten des Paketes ubuntu-app-launch (--configure):
   Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 
zurück
  Fehler traten auf beim Bearbeiten von:
   ubuntu-app-launch

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: ubuntu-app-launch 0.4+15.04.20150410-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3
  Uname: Linux 3.19.0-15-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue May  5 20:38:20 2015
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2013-07-03 (671 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  JournalErrors: Error: command ['journalctl', '-b', '--priority', 'warning'] 
failed with exit code 1: No journal files were found.
  SourcePackage: ubuntu-app-launch
  SystemImageInfo:
   current build number: 0
   device name: 
   channel: daily
   last update: Unknown
  UpgradeStatus: Upgraded to vivid on 2014-11-21 (165 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/click/+bug/1451978/+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 2061214] Re: [SRU] Software Sources is not compatible with deb822

2024-04-23 Thread Brian Murray

** Changed in: software-properties (Ubuntu Noble)
Milestone: None => noble-updates

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

Title:
  [SRU] Software Sources is not compatible with deb822

Status in software-properties package in Ubuntu:
  Confirmed
Status in software-properties source package in Noble:
  Confirmed

Bug description:
  [ Impact ]

  Ubuntu 24.04 now uses deb822 to represent software sources for deb
  packages, instead of /etc/apt/sources.list. The complete rationale for
  this change can be found here: https://discourse.ubuntu.com/t/spec-
  apt-deb822-sources-by-default/29333

  software-properties has two graphical frontends for editing these
  software sources, one is GTK-based and the other is Qt-based. When the
  underlying change to deb822 sources was made, the GTK-based frontend
  and the DBus backend interface gained support.

  The original bug report shown below informed us of the lack of deb822
  support in the Qt frontend, which results in a broken, non-functional
  interface when attempting to view or edit most values on the first two
  tabs. The fix for this is to implement a Qt dialog for deb822 sources
  that somewhat matches the existing GTK interface.

  [ Test Plan ]

  Install software-properties-qt 0.99.48 or earlier.

  Reproducing the bug:
   1. From the menu, open Software Sources. Alternatively, run `sudo -E 
software-properties-qt` in a terminal.
   2. Observe that all four checkboxes on the Ubuntu Software tab (main, 
universe, restricted, and multiverse) are unchecked.
   3. Move to the Other Software tab and observe that there are no items in the 
list.

  Upgrade to software-properties-qt 0.99.49.

  Intended functionality:
   1. From the menu, open Software Sources. Alternatively, run `sudo -E 
software-properties-qt` in a terminal.
   2. Observe that one or more checkboxes on the Ubuntu Software tab 
(representing main, universe, restricted, or multiverse) are checked. Toggle 
one or more of the checkboxes.
   3. Using a text editor of some kind (perhaps Vim), confirm that 
/etc/apt/sources.list.d/ubuntu.sources reflects your changes.
   4. Switch to the Other Software tab, there should be one item in the list.
   5. Select that item, then click Edit at the bottom of the dialog. Make a 
modification to every field on the screen, or a combination of fields you would 
like to test. All fields should work.
   6. Click the OK button at the bottom of the dialog to confirm the changes, 
then click Edit for that item again. The changes you made should be reflected 
(meaning, the changes were saved.)
   7. Using a text editor of some kind (perhaps Vim), confirm that 
/etc/apt/sources.list.d/ubuntu.sources reflects your changes.

  [ Where problems could occur ]

  This is well-tested code. That being said, the following small edge cases 
exist:
   - If you create a very large amount of rows, it infinitely expands the 
dialog without a scroll wheel. This is the same functionality as the GTK 
frontend.
   - Error validation is not performed on the deb822 lines, they are simply 
written to the ubuntu.sources file. This is good as a starting point, but also 
relies on the appropriate update notifier handling these errors. This is the 
same functionality as the GTK frontend.

  In a future update, this functionality could be broken by one or more of the 
following underlying changes:
   - Changes to the software-properties backend which are only implemented for 
the GTK frontend.
   - Changes to the location or formatting of the ubuntu.sources file.
   - Regressions in the Python bindings for Qt 5, which are rare but possible.
   - Regressions in Python itself.

  [ Other Info ]
   
  Ubuntu Studio's live ISO and installed system are affected by this. Only 
Lubuntu's installed system is affected by this.

  [ Original Report ]

  Upgrading Lubuntu Jammy to Lubuntu Noble using TUI results in
  "Software sources" not correctly updated after upgrade. Prompt= shows
  normal and not LTS

  Used command sudo do-release-upgrade -d

  Otherwise the upgrade is good

  see attached screenshot

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: software-properties-common 0.99.46
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: LXQt
  Date: Sat Apr 13 11:44:28 2024
  InstallationDate: Installed on 2024-04-13 (0 days ago)
  InstallationMedia: Lubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240331)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to noble on 2024-04-13 (0 days ago)
  mtime.conffile..etc.init.d.apport: 2024-02-22T14:20:00

To manage notifications about this bug go to:

[Touch-packages] [Bug 2063228] Re: screen sometimes blinking

2024-04-23 Thread dom21121

A video.

** Attachment added: "VID_20240423_185405.mp4"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2063228/+attachment/5769792/+files/VID_20240423_185405.mp4

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

Title:
  screen sometimes blinking

Status in xorg package in Ubuntu:
  New

Bug description:
  My screen sometimes starts flashing strongly. I move the mouse cursor, it 
stops. I put the cursor back in its place, it starts again.
  I notice this with Firefox because I use it a lot, I don't know if this 
happens with other software.
  I'm under wayland (xwayland?)

  Description:  Ubuntu 24.04 LTS
  Release:  24.04

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 23 18:57:50 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company WhiskeyLake-U GT2 [UHD Graphics 620] 
[103c:84bb]
  InstallationDate: Installed on 2024-04-07 (16 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240407.2)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 003: ID 04ca:707f Lite-On Technology Corp. HP Wide Vision HD 
Camera
   Bus 001 Device 004: ID 0bda:b00a Realtek Semiconductor Corp. Realtek 
Bluetooth 4.2 Adapter
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  MachineType: HP HP Pavilion Laptop 14-ce2xxx
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic 
root=UUID=51f857d1-b81e-42fb-b485-6d1bf22759e4 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/23/2022
  dmi.bios.release: 15.27
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.27
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 84BB
  dmi.board.vendor: HP
  dmi.board.version: 15.32
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.ec.firmware.release: 15.32
  dmi.modalias: 
dmi:bvnInsyde:bvrF.27:bd11/23/2022:br15.27:efr15.32:svnHP:pnHPPavilionLaptop14-ce2xxx:pvrType1ProductConfigId:rvnHP:rn84BB:rvr15.32:cvnHP:ct10:cvrChassisVersion:sku8KZ34EA#ABF:
  dmi.product.family: 103C_5335KV HP Pavilion
  dmi.product.name: HP Pavilion Laptop 14-ce2xxx
  dmi.product.sku: 8KZ34EA#ABF
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  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/2063228/+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 2063228] [NEW] screen sometimes blinking

2024-04-23 Thread dom21121

Public bug reported:

My screen sometimes starts flashing strongly. I move the mouse cursor, it 
stops. I put the cursor back in its place, it starts again.
I notice this with Firefox because I use it a lot, I don't know if this happens 
with other software.
I'm under wayland (xwayland?)

Description:Ubuntu 24.04 LTS
Release:24.04

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: xorg 1:7.7+23ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 23 18:57:50 2024
DistUpgraded: Fresh install
DistroCodename: noble
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company WhiskeyLake-U GT2 [UHD Graphics 620] 
[103c:84bb]
InstallationDate: Installed on 2024-04-07 (16 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240407.2)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
 Bus 001 Device 003: ID 04ca:707f Lite-On Technology Corp. HP Wide Vision HD 
Camera
 Bus 001 Device 004: ID 0bda:b00a Realtek Semiconductor Corp. Realtek Bluetooth 
4.2 Adapter
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
MachineType: HP HP Pavilion Laptop 14-ce2xxx
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-31-generic 
root=UUID=51f857d1-b81e-42fb-b485-6d1bf22759e4 ro quiet splash
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/23/2022
dmi.bios.release: 15.27
dmi.bios.vendor: Insyde
dmi.bios.version: F.27
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 84BB
dmi.board.vendor: HP
dmi.board.version: 15.32
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.ec.firmware.release: 15.32
dmi.modalias: 
dmi:bvnInsyde:bvrF.27:bd11/23/2022:br15.27:efr15.32:svnHP:pnHPPavilionLaptop14-ce2xxx:pvrType1ProductConfigId:rvnHP:rn84BB:rvr15.32:cvnHP:ct10:cvrChassisVersion:sku8KZ34EA#ABF:
dmi.product.family: 103C_5335KV HP Pavilion
dmi.product.name: HP Pavilion Laptop 14-ce2xxx
dmi.product.sku: 8KZ34EA#ABF
dmi.product.version: Type1ProductConfigId
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.120-2build1
version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
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 noble ubuntu wayland-session

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

Title:
  screen sometimes blinking

Status in xorg package in Ubuntu:
  New

Bug description:
  My screen sometimes starts flashing strongly. I move the mouse cursor, it 
stops. I put the cursor back in its place, it starts again.
  I notice this with Firefox because I use it a lot, I don't know if this 
happens with other software.
  I'm under wayland (xwayland?)

  Description:  Ubuntu 24.04 LTS
  Release:  24.04

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 23 18:57:50 2024
  DistUpgraded: Fresh install
  DistroCodename: noble
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] [8086:3ea0] (rev 02) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company WhiskeyLake-U GT2 [UHD Graphics 620] 
[103c:84bb]
  InstallationDate: Installed on 2024-04-07 (16 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240407.2)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 003: ID 04ca:707f Lite-On Technology Corp. HP Wide

[Touch-packages] [Bug 2055088] Re: debian/control incorrectly installs gnome-session dependencies in ubuntu-budgie

2024-04-23 Thread Brian Murray

** Also affects: software-properties (Ubuntu Noble)
   Importance: Undecided
   Status: New

** Changed in: software-properties (Ubuntu Noble)
Milestone: None => noble-updates

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

Title:
  debian/control incorrectly installs gnome-session dependencies in
  ubuntu-budgie

Status in software-properties package in Ubuntu:
  New
Status in software-properties source package in Noble:
  New

Bug description:
  software-properties-gtk is used on the official gtk desktops such as
  budgie.

  Currently in the debian control file it has a recommendation to
  install the session manager for that desktop - so gnome-session-bin
  for GNOME based desktops, mate-session for mate desktop and so on.

  budgie-desktop for noble now uses budgie-session as its session
  manager instead of gnome-session.

  Because of the current recommendation, gnome-session-bin is installed
  on budgie-desktop.  It no longer needs to be installed.

  software-properties needs an update to its alternate recommendations
  so that budgie-desktop doesnt pull in gnome-session-bin incorrectly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2055088/+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 2061214] Re: [SRU] Software Sources is not compatible with deb822

2024-04-23 Thread Simon Quigley

** Description changed:

+ [ Impact ]
+ 
+ Ubuntu 24.04 now uses deb822 to represent software sources for deb
+ packages, instead of /etc/apt/sources.list. The complete rationale for
+ this change can be found here: https://discourse.ubuntu.com/t/spec-apt-
+ deb822-sources-by-default/29333
+ 
+ software-properties has two graphical frontends for editing these
+ software sources, one is GTK-based and the other is Qt-based. When the
+ underlying change to deb822 sources was made, the GTK-based frontend and
+ the DBus backend interface gained support.
+ 
+ The original bug report shown below informed us of the lack of deb822
+ support in the Qt frontend, which results in a broken, non-functional
+ interface when attempting to view or edit most values on the first two
+ tabs. The fix for this is to implement a Qt dialog for deb822 sources
+ that somewhat matches the existing GTK interface.
+ 
+ [ Test Plan ]
+ 
+ Install software-properties-qt 0.99.48 or earlier.
+ 
+ Reproducing the bug:
+  1. From the menu, open Software Sources. Alternatively, run `sudo -E 
software-properties-qt` in a terminal.
+  2. Observe that all four checkboxes on the Ubuntu Software tab (main, 
universe, restricted, and multiverse) are unchecked.
+  3. Move to the Other Software tab and observe that there are no items in the 
list.
+ 
+ Upgrade to software-properties-qt 0.99.49.
+ 
+ Intended functionality:
+  1. From the menu, open Software Sources. Alternatively, run `sudo -E 
software-properties-qt` in a terminal.
+  2. Observe that one or more checkboxes on the Ubuntu Software tab 
(representing main, universe, restricted, or multiverse) are checked. Toggle 
one or more of the checkboxes.
+  3. Using a text editor of some kind (perhaps Vim), confirm that 
/etc/apt/sources.list.d/ubuntu.sources reflects your changes.
+  4. Switch to the Other Software tab, there should be one item in the list.
+  5. Select that item, then click Edit at the bottom of the dialog. Make a 
modification to every field on the screen, or a combination of fields you would 
like to test. All fields should work.
+  6. Click the OK button at the bottom of the dialog to confirm the changes, 
then click Edit for that item again. The changes you made should be reflected 
(meaning, the changes were saved.)
+  7. Using a text editor of some kind (perhaps Vim), confirm that 
/etc/apt/sources.list.d/ubuntu.sources reflects your changes.
+ 
+ [ Where problems could occur ]
+ 
+ This is well-tested code. That being said, the following small edge cases 
exist:
+  - If you create a very large amount of rows, it infinitely expands the 
dialog without a scroll wheel. This is the same functionality as the GTK 
frontend.
+  - Error validation is not performed on the deb822 lines, they are simply 
written to the ubuntu.sources file. This is good as a starting point, but also 
relies on the appropriate update notifier handling these errors. This is the 
same functionality as the GTK frontend.
+ 
+ In a future update, this functionality could be broken by one or more of the 
following underlying changes:
+  - Changes to the software-properties backend which are only implemented for 
the GTK frontend.
+  - Changes to the location or formatting of the ubuntu.sources file.
+  - Regressions in the Python bindings for Qt 5, which are rare but possible.
+  - Regressions in Python itself.
+ 
+ [ Other Info ]
+  
+ Ubuntu Studio's live ISO and installed system are affected by this. Only 
Lubuntu's installed system is affected by this.
+ 
+ [ Original Report ]
+ 
  Upgrading Lubuntu Jammy to Lubuntu Noble using TUI results in "Software
  sources" not correctly updated after upgrade. Prompt= shows normal and
  not LTS
  
  Used command sudo do-release-upgrade -d
  
  Otherwise the upgrade is good
  
  see attached screenshot
  
  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: software-properties-common 0.99.46
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: LXQt
  Date: Sat Apr 13 11:44:28 2024
  InstallationDate: Installed on 2024-04-13 (0 days ago)
  InstallationMedia: Lubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240331)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to noble on 2024-04-13 (0 days ago)
  mtime.conffile..etc.init.d.apport: 2024-02-22T14:20:00

** Also affects: software-properties (Ubuntu Noble)
   Importance: Critical
 Assignee: Simon Quigley (tsimonq2)
   Status: 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/2061214

Title:
  [SRU] Software Sources is not compatible with deb822

Status in software-properties package in Ubuntu:
  Confirmed
Status in software-properties source package in Noble:

[Touch-packages] [Bug 2063221] Re: Drop libglib2.0-0 transitional package

2024-04-23 Thread Brian Murray

** Also affects: glib2.0 (Ubuntu Noble)
   Importance: High
   Status: In Progress

** Changed in: glib2.0 (Ubuntu Noble)
Milestone: None => noble-updates

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

Title:
  Drop libglib2.0-0 transitional package

Status in glib2.0 package in Ubuntu:
  In Progress
Status in glib2.0 source package in Noble:
  In Progress

Bug description:
  Impact
  --
  apt can struggle with ordering when handling the massive Y2028 time_t 
transition when upgrading to Ubuntu 24.04 LTS.

  It was identified that dropping the libglib2.0-0 transitional package
  can help apt do things in the correct order.

  Test Case
  -
  Is libglib2.0-0 built?

  Other Info
  --
  This is related to LP: #2061918 for the thunderbird deb to snap upgrade

  There are likely several other Launchpad bugs that can be resolved by
  this update and some other workarounds in other packages, like in the
  transitional thunderbird package.

  https://salsa.debian.org/gnome-team/glib/-/merge_requests/34

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2063221/+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 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.

*** This bug is a duplicate of bug 2054761 ***
https://bugs.launchpad.net/bugs/2054761

The problem is that gnome-shell crashes during the upgrade, so packages
including systemd-resolved never finish getting installed. Marking as a
duplicate of bug 2054761.

** This bug has been marked a duplicate of bug 2054761
   gnome-shell crashed with signal 5:  Settings schema 
'org.gnome.mutter.wayland' does not contain a key named 
'xwayland-allow-byte-swapped-clients'

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

Title:
  When I upgraded from 22.04 to 24.04, DNS resolution went wrong.

Status in network-manager package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  New

Bug description:
  I was an unpatient idiot, and I upgraded from 22.04 to 24.04. Near to
  the end of the upgrade, I got an „Oh, no! Something has gone wrong and
  the system cannot recover. Call the system administrator” message
  after a red FAILED in the terminal. The system administrator is
  myself, because my computer is a personal one. Hard reset, same error,
  Ctrl+Alt+F3, sudo apt reinstall gdm3. Obviously. I needed to finish
  the update with dpkg. While dpkg was upgrading, it printed an error
  message for every WiFi connection:

  „[Failed] Failed to migrate [I do not remember, something with
  /etc/netplan]”

  It took at least one and a half hour to find the solution on Ask
  Ubuntu. The problem was: /etc/resolv.conf became a broken link, along
  with systemd-resolve.service. I needed to remove both of them and
  write a new resolv.conf to fix the error.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: network-manager 1.45.90-1ubuntu1
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 26 08:21:02 2024
  InstallationDate: Installed on 2023-07-05 (236 days ago)
  InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316)
  IpRoute:
   default via 192.168.0.1 dev wlp3s0 proto dhcp src 192.168.0.100 metric 600
   192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.100 metric 
600
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to noble on 2024-02-24 (2 days ago)
  modified.conffile..etc.init.d.apport: [modified]
  mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.45.90  connected  started  full  enabled enabled  
enabled  missing  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+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 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.

*** This bug is a duplicate of bug 2054761 ***
https://bugs.launchpad.net/bugs/2054761

Adding my journal from the crash.

** Attachment added: "journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2055012/+attachment/5769751/+files/journal.txt

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

Title:
  When I upgraded from 22.04 to 24.04, DNS resolution went wrong.

Status in network-manager package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  New

Bug description:
  I was an unpatient idiot, and I upgraded from 22.04 to 24.04. Near to
  the end of the upgrade, I got an „Oh, no! Something has gone wrong and
  the system cannot recover. Call the system administrator” message
  after a red FAILED in the terminal. The system administrator is
  myself, because my computer is a personal one. Hard reset, same error,
  Ctrl+Alt+F3, sudo apt reinstall gdm3. Obviously. I needed to finish
  the update with dpkg. While dpkg was upgrading, it printed an error
  message for every WiFi connection:

  „[Failed] Failed to migrate [I do not remember, something with
  /etc/netplan]”

  It took at least one and a half hour to find the solution on Ask
  Ubuntu. The problem was: /etc/resolv.conf became a broken link, along
  with systemd-resolve.service. I needed to remove both of them and
  write a new resolv.conf to fix the error.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: network-manager 1.45.90-1ubuntu1
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 26 08:21:02 2024
  InstallationDate: Installed on 2023-07-05 (236 days ago)
  InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316)
  IpRoute:
   default via 192.168.0.1 dev wlp3s0 proto dhcp src 192.168.0.100 metric 600
   192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.100 metric 
600
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to noble on 2024-02-24 (2 days ago)
  modified.conffile..etc.init.d.apport: [modified]
  mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.45.90  connected  started  full  enabled enabled  
enabled  missing  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+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 2061214] Re: [SRU] Software Sources is not compatible with deb822

2024-04-23 Thread Simon Quigley

** Summary changed:

- Software sources not correctly updated after upgrade and/or new installs
+ [SRU] Software Sources is not compatible with deb822

** Summary changed:

- [SRU] Software Sources is not compatible with deb822
+ Software Sources is not compatible with deb822

** Summary changed:

- Software Sources is not compatible with deb822
+ [SRU] Software Sources is not compatible with deb822

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

Title:
  [SRU] Software Sources is not compatible with deb822

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Upgrading Lubuntu Jammy to Lubuntu Noble using TUI results in
  "Software sources" not correctly updated after upgrade. Prompt= shows
  normal and not LTS

  Used command sudo do-release-upgrade -d

  Otherwise the upgrade is good

  see attached screenshot

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: software-properties-common 0.99.46
  ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1
  Uname: Linux 6.8.0-22-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: LXQt
  Date: Sat Apr 13 11:44:28 2024
  InstallationDate: Installed on 2024-04-13 (0 days ago)
  InstallationMedia: Lubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 
(20240331)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to noble on 2024-04-13 (0 days ago)
  mtime.conffile..etc.init.d.apport: 2024-02-22T14:20:00

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/2061214/+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 2063221] Re: Drop libglib2.0-0 transitional package

2024-04-23 Thread Jeremy Bícha

** Changed in: glib2.0 (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  Drop libglib2.0-0 transitional package

Status in glib2.0 package in Ubuntu:
  In Progress

Bug description:
  Impact
  --
  apt can struggle with ordering when handling the massive Y2028 time_t 
transition when upgrading to Ubuntu 24.04 LTS.

  It was identified that dropping the libglib2.0-0 transitional package
  can help apt do things in the correct order.

  Test Case
  -
  Is libglib2.0-0 built?

  Other Info
  --
  This is related to LP: #2061918 for the thunderbird deb to snap upgrade

  There are likely several other Launchpad bugs that can be resolved by
  this update and some other workarounds in other packages, like in the
  transitional thunderbird package.

  https://salsa.debian.org/gnome-team/glib/-/merge_requests/34

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2063221/+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 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.

** Changed in: ubuntu-release-upgrader (Ubuntu)
   Importance: Undecided => Critical

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

Title:
  When I upgraded from 22.04 to 24.04, DNS resolution went wrong.

Status in network-manager package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Confirmed
Status in ubuntu-release-upgrader package in Ubuntu:
  New

Bug description:
  I was an unpatient idiot, and I upgraded from 22.04 to 24.04. Near to
  the end of the upgrade, I got an „Oh, no! Something has gone wrong and
  the system cannot recover. Call the system administrator” message
  after a red FAILED in the terminal. The system administrator is
  myself, because my computer is a personal one. Hard reset, same error,
  Ctrl+Alt+F3, sudo apt reinstall gdm3. Obviously. I needed to finish
  the update with dpkg. While dpkg was upgrading, it printed an error
  message for every WiFi connection:

  „[Failed] Failed to migrate [I do not remember, something with
  /etc/netplan]”

  It took at least one and a half hour to find the solution on Ask
  Ubuntu. The problem was: /etc/resolv.conf became a broken link, along
  with systemd-resolve.service. I needed to remove both of them and
  write a new resolv.conf to fix the error.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: network-manager 1.45.90-1ubuntu1
  ProcVersionSignature: Ubuntu 6.6.0-14.14-generic 6.6.3
  Uname: Linux 6.6.0-14-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 26 08:21:02 2024
  InstallationDate: Installed on 2023-07-05 (236 days ago)
  InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316)
  IpRoute:
   default via 192.168.0.1 dev wlp3s0 proto dhcp src 192.168.0.100 metric 600
   192.168.0.0/24 dev wlp3s0 proto kernel scope link src 192.168.0.100 metric 
600
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  RfKill:
   0: phy0: Wireless LAN
    Soft blocked: no
    Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to noble on 2024-02-24 (2 days ago)
  modified.conffile..etc.init.d.apport: [modified]
  mtime.conffile..etc.init.d.apport: 2024-02-22T15:20:00
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.45.90  connected  started  full  enabled enabled  
enabled  missing  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2055012/+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 2063222] Re: Ghost "unknown display" since upgrading to 24.04 beta

2024-04-23 Thread Kostya Vasilyev

FWIW - I'm also using GNOME 46 in another distro - Manjaro - and this
issue does not exist there

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

Title:
  Ghost "unknown display" since upgrading to 24.04 beta

Status in xorg package in Ubuntu:
  New

Bug description:
  X11
  GNOME
  NVIDIA 4080 with their driver

  ->

  GNOME settings has a "ghost" display called "Unknown Display", its
  resolution is 1024 x 768

  I only have one display attached - a 4K 27" DELL plugged into the
  NVIDIA

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.171.04  Tue Mar 19 
20:30:00 UTC 2024
   GCC version:  gcc version 13.2.0 (Ubuntu 13.2.0-23ubuntu4)
  ApportVersion: 2.28.1-0ubuntu2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 23 08:55:55 2024
  DistUpgraded: 2024-04-14 17:14:28,561 DEBUG migrateToDeb822Sources()
  DistroCodename: noble
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia/535.171.04, 6.8.0-28-generic, x86_64: installed
   nvidia/535.171.04, 6.8.0-31-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   Subsystem: Micro-Star International Co., Ltd. [MSI] AlderLake-S GT1 
[1462:7d25]
   NVIDIA Corporation AD103 [GeForce RTX 4080] [10de:2704] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] AD103 [GeForce RTX 
4080] [1462:5111]
  InstallationDate: Installed on 2022-04-30 (724 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 
(20220419)
  MachineType: Micro-Star International Co., Ltd. MS-7D25
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   TERM=xterm-256color
   XDG_RUNTIME_DIR=
  ProcKernelCmdLine: root=UUID=43e064ac-5857-4c85-b15d-1dd96cdad27b ro quiet 
splash vt.handoff=7 initrd=boot\initrd.img-6.8.0-31-generic
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to noble on 2024-04-15 (9 days ago)
  dmi.bios.date: 11/13/2023
  dmi.bios.release: 5.27
  dmi.bios.vendor: American Megatrends International, LLC.
  dmi.bios.version: A.F0
  dmi.board.asset.tag: Default string
  dmi.board.name: PRO Z690-A WIFI (MS-7D25)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrA.F0:bd11/13/2023:br5.27:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D25:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnPROZ690-AWIFI(MS-7D25):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:skuDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: MS-7D25
  dmi.product.sku: Default string
  dmi.product.version: 2.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.120-2build1
  version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
  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/2063222/+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 2063222] [NEW] Ghost "unknown display" since upgrading to 24.04 beta

2024-04-23 Thread Kostya Vasilyev

Public bug reported:

X11
GNOME
NVIDIA 4080 with their driver

->

GNOME settings has a "ghost" display called "Unknown Display", its
resolution is 1024 x 768

I only have one display attached - a 4K 27" DELL plugged into the NVIDIA

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: xorg 1:7.7+23ubuntu3
ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
Uname: Linux 6.8.0-31-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  535.171.04  Tue Mar 19 
20:30:00 UTC 2024
 GCC version:  gcc version 13.2.0 (Ubuntu 13.2.0-23ubuntu4)
ApportVersion: 2.28.1-0ubuntu2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 23 08:55:55 2024
DistUpgraded: 2024-04-14 17:14:28,561 DEBUG migrateToDeb822Sources()
DistroCodename: noble
DistroVariant: ubuntu
DkmsStatus:
 nvidia/535.171.04, 6.8.0-28-generic, x86_64: installed
 nvidia/535.171.04, 6.8.0-31-generic, x86_64: installed
ExtraDebuggingInterest: No
GraphicsCard:
 Subsystem: Micro-Star International Co., Ltd. [MSI] AlderLake-S GT1 [1462:7d25]
 NVIDIA Corporation AD103 [GeForce RTX 4080] [10de:2704] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Micro-Star International Co., Ltd. [MSI] AD103 [GeForce RTX 4080] 
[1462:5111]
InstallationDate: Installed on 2022-04-30 (724 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
MachineType: Micro-Star International Co., Ltd. MS-7D25
ProcEnviron:
 LANG=en_US.UTF-8
 PATH=(custom, no user)
 SHELL=/bin/bash
 TERM=xterm-256color
 XDG_RUNTIME_DIR=
ProcKernelCmdLine: root=UUID=43e064ac-5857-4c85-b15d-1dd96cdad27b ro quiet 
splash vt.handoff=7 initrd=boot\initrd.img-6.8.0-31-generic
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to noble on 2024-04-15 (9 days ago)
dmi.bios.date: 11/13/2023
dmi.bios.release: 5.27
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: A.F0
dmi.board.asset.tag: Default string
dmi.board.name: PRO Z690-A WIFI (MS-7D25)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 2.0
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 2.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrA.F0:bd11/13/2023:br5.27:svnMicro-StarInternationalCo.,Ltd.:pnMS-7D25:pvr2.0:rvnMicro-StarInternationalCo.,Ltd.:rnPROZ690-AWIFI(MS-7D25):rvr2.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr2.0:skuDefaultstring:
dmi.product.family: Default string
dmi.product.name: MS-7D25
dmi.product.sku: Default string
dmi.product.version: 2.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.120-2build1
version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.12-1ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1build1
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 noble ubuntu

** Attachment added: "Screenshot from 2024-04-23 08-25-39.png"
   
https://bugs.launchpad.net/bugs/2063222/+attachment/5769727/+files/Screenshot%20from%202024-04-23%2008-25-39.png

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

Title:
  Ghost "unknown display" since upgrading to 24.04 beta

Status in xorg package in Ubuntu:
  New

Bug description:
  X11
  GNOME
  NVIDIA 4080 with their driver

  ->

  GNOME settings has a "ghost" display called "Unknown Display", its
  resolution is 1024 x 768

  I only have one display attached - a 4K 27" DELL plugged into the
  NVIDIA

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: xorg 1:7.7+23ubuntu3
  ProcVersionSignature: Ubuntu 6.8.0-31.31-generic 6.8.1
  Uname: Linux 6.8.0-31-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.

[Touch-packages] [Bug 2055012] Re: When I upgraded from 22.04 to 24.04, DNS resolution went wrong.