date:20240110

https://github.com/vim/vim/pull/13825

I will test this first in Debian, upload it there, then do a merge.

** Changed in: vim (Ubuntu)
   Status: Confirmed => In Progress

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

Title:
  Highlighting of patches offers insufficient contrast

Status in vim package in Ubuntu:
  In Progress

Bug description:
  With vim 2:9.0.2189-1ubuntu1 the coloring of patches has been changed.

  The result is that in konsole patches have become illegible. See
  appendix.

  Deleted lines have foreground cyan #18b2b2 and background light blue
  #7f7fff. Kind of blue on blue.

  Please, provide sane color defaults. The previous release used bright
  white on black for deleted lines.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/2047982/+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 2047780] Re: BlueZ release 5.71

> Force pushing my local commits over, sorry not sorry. :)

Yeah it's fine this time. :)

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

Title:
  BlueZ release 5.71

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  Release BlueZ 5.71 to noble.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+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 2047780] Re: BlueZ release 5.71

> Please also remember to commit proposed changes to
https://git.launchpad.net/~bluetooth/bluez

Force pushing my local commits over, sorry not sorry. :)

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

Title:
  BlueZ release 5.71

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  Release BlueZ 5.71 to noble.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+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 2047780] Re: BlueZ release 5.71

> Simon, ell already has a recent approved MIR LP: #1971738

Er, the binary packages in question don't.

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

Title:
  BlueZ release 5.71

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  Release BlueZ 5.71 to noble.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+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 2047780] Re: BlueZ release 5.71

I'm pretty shocked, I ran a local sbuild with this and yet it still
FTBFS. Doing an ubuntu2 upload as a fixup.

I would think that because we use the published tarball and not the
upstream source like Debian does, that would affect our ability to ship
the -test package.

Something's up with my local setup. I'll figure it out, fix it, and
allow us to move forward here.

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

Title:
  BlueZ release 5.71

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  Release BlueZ 5.71 to noble.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+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 2046459] Re: systemd-gpt-auto-generator is omitted since 253.5-1ubuntu5 resulting in boot failure

2024-01-10 Thread Nils K

This says fix commited though it seems to be neither available in
mantic-updates nor in noble? This is annoying as we have to resort to
installing 253.5-1ubuntu4 manually from the old repository archives and
prevent updates of it

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

Title:
  systemd-gpt-auto-generator is omitted since 253.5-1ubuntu5 resulting
  in boot failure

Status in systemd package in Ubuntu:
  Fix Committed

Bug description:
  I have my system set up to rely on GPT auto generator together with
  Discoverable Partitions Specification (DPS). After upgrading my system
  the gpt generator is no longer included resulting in boot failure.

  I have been able to workaround this by setting up the mounts in fstab but 
that is unsatisfactory.
  Furthermore I work on an embedded device which uses Ubuntu as a base and 
relies on the GPT auto generator. In this case it is not possible for me to 
switch back to an old fstab file as we rely on some autodiscovery possible only 
with DPS.

  Even though it is not used by the default installation, I kindly
  request to revert a366279a84730e92ed734710560ea833709f359d. Even
  though the default does not require it does not mean that no one else
  does. Also the generator binary fairly small at a few dozen KB so not
  much is gained from omitting it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2046459/+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 2047780] Re: BlueZ release 5.71

BTW, having the previous Ubuntu version 5.71-0ubuntu3 on line 415 of the
changelog doesn't feel ideal for people wanting to read the Ubuntu
release history.

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

Title:
  BlueZ release 5.71

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  Release BlueZ 5.71 to noble.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+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 2047780] Re: BlueZ release 5.71 and merge from Debian

Ideally please open a new bug for the merge. This bug should remain Fix
Released because we're already past the point in time when it was
released to Noble.

Please also remember to commit proposed changes to
https://git.launchpad.net/~bluetooth/bluez

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

** Summary changed:

- BlueZ release 5.71 and merge from Debian
+ BlueZ release 5.71

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

Title:
  BlueZ release 5.71

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  Release BlueZ 5.71 to noble.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+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 2047780] Re: BlueZ release 5.71 and merge from Debian

2024-01-10 Thread Jeremy Bícha

Simon, ell already has a recent approved MIR LP: #1971738

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

Title:
  BlueZ release 5.71 and merge from Debian

Status in bluez package in Ubuntu:
  In Progress

Bug description:
  Release BlueZ 5.71 to noble.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+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 2047780] Re: BlueZ release 5.71 and merge from Debian

At first I was just going to say, ell-dev isn't built on i386 and it's
not arch:all, of course it will need an i386 allowlist entry! However,
this is the output I'm getting:

```
$ check-mir
Checking support status of build dependencies...
 * debhelper-compat does not exist (pure virtual?)
 * libell-dev binary and source package is in universe
 * check binary and source package is in universe

Checking support status of binary dependencies...
 * default-dbus-system-bus does not exist (pure virtual?)
  ... alternative dbus-system-bus does not exist (pure virtual?)

Please check https://wiki.ubuntu.com/MainInclusionProcess if this source 
package needs to get into in main/restricted, or reconsider if the package 
really needs above dependencies.
```

I'm going to fix check-mir itself so it ignores debhelper-compat (that
is certainly a false flag since debhelper is in main, and I don't want
to see anyone waste time on this red herring), `libell-dev` and `check`
are valid points. Both of those seem like reasonably small libraries
that could be MIRed, especially ell for embedded devices. That being
said, we did not have these dependencies before, so this is much lower
on my priority list. I would highly encourage someone to beat me to it.

That being said, I've been listening to music with no issue with the
updated bluez, which is what I would expect to be the baseline for a
"working" bluez. The only quirk I noticed is that despite my device
(Beats Flex) being set to autoconnect, I needed to manually connect (to
the already saved device). Connected promptly, no stuttering issues
(from YouTube Music/Firefox Nightly snap), audio is as good/loud as I
would expect it to be, and volume control works smoothly. I'm not
noticing anything particularly different on the blueman configuration
front.

tl;dr: Uploaded Gianfranco's diff to Noble with slight modifications.
This will need to go through binary NEW.

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

Title:
  BlueZ release 5.71 and merge from Debian

Status in bluez package in Ubuntu:
  In Progress

Bug description:
  Release BlueZ 5.71 to noble.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+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 798414] Re: update-initramfs should produce a more helpful error message when there isn't enough free space--or provide an automatic tool for removal of old files

2024-01-10 Thread lizehao

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

Title:
  update-initramfs should produce a more helpful error message when
  there isn't enough  free space--or provide an automatic tool for
  removal of old files

Status in initramfs-tools package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: initramfs-tools

  When installing a kernel, /boot may become full during execution of
  post-installation script typically when update-initramfs is creating
  or updating an initrd.img file. This is resulting in kernel
  installation error.  For example:

  Setting up initramfs-tools (0.98.8ubuntu3) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for initramfs-tools ...
  update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic

  gzip: stdout: No space left on device
  E: mkinitramfs failure cpio 141 gzip 1
  update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic
  dpkg: error processing initramfs-tools (--configure):
   subprocess installed post-installation script returned error exit status 1

  Ideal behavior:

  Give a more helpful error message when this unfortunate situation
  occurs so that user can fix the broken system and keep it going.

  Workaround:

  As the bug reporting system forwards user to this bug report, such 
instructions can be given here:
  https://help.ubuntu.com/community/RemoveOldKernels

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/798414/+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 798414] Re: update-initramfs should produce a more helpful error message when there isn't enough free space--or provide an automatic tool for removal of old files

2024-01-10 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/798414

** Tags added: iso-testing

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

Title:
  update-initramfs should produce a more helpful error message when
  there isn't enough  free space--or provide an automatic tool for
  removal of old files

Status in initramfs-tools package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: initramfs-tools

  When installing a kernel, /boot may become full during execution of
  post-installation script typically when update-initramfs is creating
  or updating an initrd.img file. This is resulting in kernel
  installation error.  For example:

  Setting up initramfs-tools (0.98.8ubuntu3) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for initramfs-tools ...
  update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic

  gzip: stdout: No space left on device
  E: mkinitramfs failure cpio 141 gzip 1
  update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic
  dpkg: error processing initramfs-tools (--configure):
   subprocess installed post-installation script returned error exit status 1

  Ideal behavior:

  Give a more helpful error message when this unfortunate situation
  occurs so that user can fix the broken system and keep it going.

  Workaround:

  As the bug reporting system forwards user to this bug report, such 
instructions can be given here:
  https://help.ubuntu.com/community/RemoveOldKernels

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/798414/+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 2003756] Re: Cannot configure krb5-kdc on Ubuntu Jammy 22.04.01, "Could not execute systemctl: at /usr/bin/deb-systemd-invoke line 142."

2024-01-10 Thread Sergio Durigan Junior

I'm changing my opinion here.

I feel like this is indeed a problem with how init-system-helpers (more
specifically, deb-systemd-invoke) warns users about errors.  Since it
uses "--quiet" when invoking systemctl, I believe it needs to be a bit
more verbose to explain what happened.

What's interesting that I can't reproduce the apt failure.  For example,
"apt install proftpd" will warn me about deb-systemd-invoke, but the
command will finish successfully.  ISTR having seen this behaviour
before, but I don't remember my conclusion at the time.

Anyway, this needs to be forwarded to Debian.  I don't believe Ubuntu
should diverge from Debian in this case.

** Changed in: init-system-helpers (Ubuntu)
   Status: Confirmed => Triaged

** Changed in: krb5 (Ubuntu)
   Status: Confirmed => Triaged

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

Title:
  Cannot configure krb5-kdc on Ubuntu Jammy 22.04.01, "Could not execute
  systemctl:  at /usr/bin/deb-systemd-invoke line 142."

Status in init-system-helpers package in Ubuntu:
  Triaged
Status in krb5 package in Ubuntu:
  Triaged

Bug description:
  I have a fresh install of Ubuntu Server 22.04.01 LTS.  After
  installing the server and running all updates, I run the following
  command:

  apt -y install slapd ldap-utils schema2ldif sasl2-bin
  libsasl2-modules-gssapi-mit krb5-kdc-ldap krb5-admin-server krb5-kdc

  This will be installing krb5-kdc 1.19.2-2.

  This is in preparation for setting up an OpenLDAP server, a Kerberos
  server with an LDAP backend, and saslauthd for pass-through
  authentication.  krb5-kdc was auto-selected when running the steps in
  the guide here in my development environment:
  https://ubuntu.com/server/docs/service-kerberos-with-openldap-backend
  When installing that, I get the following in the output:

  Setting up krb5-kdc (1.19.2-2) ...
  Created symlink /etc/systemd/system/multi-user.target.wants/krb5-kdc.service 
→ /lib/systemd/system/krb5-kdc.service.
  Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 142.

  I do get the prompts for the realm, kdc, and admin server hostnames,
  and they are reflected in /etc/krb5.conf.  If I then run the
  following:

  dpkg-reconfigure krb5-kdc

  I am prompted for whether I want the package to create the Kerberos
  KDC configuration automatically, and when I say yes, it then repeats
  the following error:

  Could not execute systemctl:  at /usr/bin/deb-systemd-invoke line 142.

  I cannot find any further debug in the syslog or anything to indicate
  what the root cause is; the list of packages here are all installed
  together on a separate development server where I experimented with
  the configuration I will be deploying here in production so I don't
  think it's incompatible packages in the install list, but I am open to
  feedback on that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/init-system-helpers/+bug/2003756/+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 2029352] Re: systemd/ 245.4-4ubuntu3.22 ADT test failure with linux/5.4.0-156.173

2024-01-10 Thread Nick Rosbrook

The autopkgtest for systemd 245.4-4ubuntu3.23 on armhf passed, which
verifies this fix: https://autopkgtest.ubuntu.com/results/autopkgtest-
focal/focal/armhf/s/systemd/20240110_171824_cbc46@/log.gz.

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

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

Title:
  systemd/ 245.4-4ubuntu3.22  ADT test failure with linux/5.4.0-156.173

Status in systemd package in Ubuntu:
  Invalid
Status in systemd source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  The armhf autopkgtest fails for focal and ultimately leads to less
  test coverage because other packages now won't block on these
  failures, and may not notice new regressions.

  [Test Plan]

  The test-execute test within root-unittests should pass.

  [Where problems could occur]

  The patch only changes a service file in the test tree of systemd, so
  this is not a change that will be seen on real Ubuntu systems. Hence
  any further problems would be seen only in the test-execute test.

  [Original Description]

  This is a scripted bug report about ADT failures while running systemd tests 
for linux/5.4.0-156.173 on focal. Whether this is caused by the dep8 tests of 
the tested source or the kernel has yet to be determined.
  root-unittests fails.

  Testing failed on:
  armhf: 
https://autopkgtest.ubuntu.com/results/autopkgtest-focal/focal/armhf/s/systemd/20230727_150132_9cd77@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2029352/+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 2024009] Re: [PATCH] systemd-resolved can't follow more than 8 CNAMEs

2024-01-10 Thread Nick Rosbrook

I have verified the fix using systemd 245.4-4ubuntu3.23 from focal-
proposed.

On the host, I have a Focal container, and killed the existing DNS
servers:

nr@clean-jammy-amd64:~$ lxc list
+---+-+--+--+---+---+
| NAME  |  STATE  | IPV4 | IPV6 |   
TYPE| SNAPSHOTS |
+---+-+--+--+---+---+
| focal | RUNNING |  | fd42:b04:cc58:1a82:216:3eff:fe28:d8d9 (eth0) | 
CONTAINER | 0 |
+---+-+--+--+---+---+
nr@clean-jammy-amd64:~$ systemctl stop systemd-resolved
nr@clean-jammy-amd64:~$ kill -9 $(pgrep dnsmasq)

Then, I start a new DNS server with a record which contains 10 CNAME
redirects:

nr@clean-jammy-amd64:~$ sudo dnsmasq --cname=test10.lan,test9.lan
--cname=test9.lan,test8.lan --cname=test8.lan,test7.lan
--cname=test7.lan,test6.lan --cname=test6.lan,test5.lan
--cname=test5.lan,test4.lan --cname=test4.lan,test3.lan
--cname=test3.lan,test2.lan --cname=test2.lan,test1.lan
--cname=test1.lan,test0.lan -k -i lxdbr0 -z -I lo --host-
record=test0.lan,192.168.122.143

...

In the container, I have systemd installed from focal-proposed, and I
was able to successfully make the query despite more than 8 CNAME
redirects:

root@focal:~# apt policy systemd
systemd:
  Installed: 245.4-4ubuntu3.23
  Candidate: 245.4-4ubuntu3.23
  Version table:
 *** 245.4-4ubuntu3.23 500
500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 245.4-4ubuntu3.22 500
500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages
 245.4-4ubuntu3.20 500
500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages
 245.4-4ubuntu3 500
500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
root@focal:~# resolvectl query test10.lan
test10.lan: 192.168.122.143-- link: eth0
(test0.lan)

-- Information acquired via protocol DNS in 70.3ms.
-- Data is authenticated: no


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

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

Title:
  [PATCH] systemd-resolved can't follow more than 8 CNAMEs

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Fix Committed

Bug description:
  [Impact]

  Using systemd-resolved to resolve a hostname which has more than 8
  CNAME redirects will fail because of the hard-coded limit. While this
  case is somewhat rare, the original reporter demonstrated a real-world
  scenario where this happened (although that particular hostname seems
  to be fixed now).

  [Test Plan]

  This test plan uses a LXC container to test systemd-resolved on Focal.
  If LXD has not been configured on your system, start with:

  $ lxd init --auto

  Then, create a Focal container with:

  $ lxc launch ubuntu-daily:focal focal

  Install dnsmasq-base if needed:

  $ apt install dnsmasq-base

  Stop other DNS servers:

  $ systemctl stop systemd-resolved
  $ kill -9 $(pgrep dnsmasq)

  Now, on the host start a new DNS server that listens on lxdbr0, and
  sets up an A record, and many CNAME records which ultimately redirect
  to the A record:

  $ dnsmasq \
  --cname=test10.lan,test9.lan \
  --cname=test9.lan,test8.lan \
  --cname=test8.lan,test7.lan \
  --cname=test7.lan,test6.lan \
  --cname=test6.lan,test5.lan \
  --cname=test5.lan,test4.lan \
  --cname=test4.lan,test3.lan \
  --cname=test3.lan,test2.lan \
  --cname=test2.lan,test1.lan \
  --cname=test1.lan,test0.lan \
  -k -i lxdbr0 -z -I lo --host-record=test0.lan,$IP

  where $IP is any host on your network.

  Now, obtain a shell in the Focal container:

  $ lxc exec focal bash

  Attempt to resolve test10.lan:

  $ resolvectl query test10.lan
  test10.lan: resolve call failed: CNAME loop detected, or CNAME resolving 
disabled on 'test2.lan'

  On an affected system, the above error will be seen. On a patched
  system, the hostname should be resolved.

  [Where problems could occur]

  The patch simply increases the maximum CNAME redirects that are
  allowed from 8 to 16, so a reasonable limit is still imposed. If an
  application specifically relied on systemd-resolved's limit being at
  8, then that application would potentially see new behavior.

  [Original Description]

  On Ubuntu 20.04 (systemd v245.4-4ubuntu3.21), hostname resolution only
  follows 8 CNAME redirections maximum.

  So when using a service like Azure Virtual Desktop that has between 9
  and 12 redirections, name resolution fails.

  $ host client.wvd.microsoft.com
  Host client.wvd.microsoft.com not found:

[Touch-packages] [Bug 2047780] Re: BlueZ release 5.71

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

** Summary changed:

- BlueZ release 5.71
+ BlueZ release 5.71 and merge from Debian

** Changed in: bluez (Ubuntu)
 Assignee: Daniel van Vugt (vanvugt) => Simon Quigley (tsimonq2)

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

Title:
  BlueZ release 5.71 and merge from Debian

Status in bluez package in Ubuntu:
  In Progress

Bug description:
  Release BlueZ 5.71 to noble.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+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 2042587] Re: jammy's version breaks existing dhcp scripts with relay

** Merge proposal linked:
   
https://code.launchpad.net/~ahasenack/ubuntu/+source/dnsmasq/+git/dnsmasq/+merge/458373

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

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

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

Bug description:
  [ Impact ]

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

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

  [ Test Plan ]

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

  # Launch a jammy VM

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

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

  lxc shell j-dnsmasq-2042587

  # download test script

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

  # make it executable

  chmod +x setup-and-server.sh

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

  apt update && apt install dnsmasq -y

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

  ./setup-and-server.sh

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

  No DHCP relay:

    ip netns exec client dhclient -d -v p2

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

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

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

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

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

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

  [ Where problems could occur ]

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

  [ Other Info ]
  Not at this time.

  [ Original description ]

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

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

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

  dnsmasq 2.86-1.1ubuntu0.3 / Ubuntu 22.04

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


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

[Touch-packages] [Bug 2042587] Re: jammy's version breaks existing dhcp scripts with relay

Test script

** Description changed:

  [ Impact ]
  
  When upgrading from focal to jammy, existing dnsmasq dhcp-scripts
  stopped working in an environment where a DHCP relay is in use. Instead
  of the expected client IP address, the script gets the _relay_ IP
  address as an argument.
  
- 
  [ Test Plan ]
  
-  * detailed instructions how to reproduce the bug
+ To easily test this on a single machine, a test script is being provided
+ to setup networking and dnsmasq configuration.
  
-  * these should allow someone who is not familiar with the affected
-    package to reproduce the bug and verify that the updated package fixes
-    the problem.
  
-  * if other testing is appropriate to perform before landing this update,
-    this should also be described here.
+ # Launch a jammy VM
+ 
+ lxc launch ubuntu-daily:jammy j-dnsmasq-2042587 --vm
+ 
+ # open a root shell in that VM. All subsequent commands must be executed
+ as root in that VM
+ 
+ lxc shell j-dnsmasq-2042587
+ 
+ # download test script
+ 
+ wget
+ 
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/2042587/+attachment/5738170/+files/setup-
+ and-server.sh
+ 
+ # make it executable
+ 
+ chmod +x setup-and-server.sh
+ 
+ # install dnsmasq. Ignore the postinst error (because systemd-resolved
+ is also running and there is a port conflict)
+ 
+ apt update && apt install dnsmasq -y
+ 
+ # run the setup script. It will configure things and start dnsmasq ready
+ to be tested
+ 
+ ./setup-and-server.sh
+ 
+ 
+ # in another root session inside the vm (so run "lxc shell j-dnsmasq-2042587" 
in another terminal), run the proposed commands from the setup script (and 
press ctrl-c after the result is shown):
+ 
+ 
+ No DHCP relay:
+ 
+   ip netns exec client dhclient -d -v p2
+ 
+ The setup script should log an IP that is not a relay. For example:
+ dnsmasq-dhcp: DHCPDISCOVER(p1) aa:a0:9d:00:5b:d6 
+ dnsmasq-dhcp: DHCPOFFER(p1) 192.168.47.150 aa:a0:9d:00:5b:d6 
+ dnsmasq-dhcp: DHCPREQUEST(p1) 192.168.47.150 aa:a0:9d:00:5b:d6 
+ dnsmasq-dhcp: DHCPACK(p1) 192.168.47.150 aa:a0:9d:00:5b:d6 j-dnsmasq-2042587
+ ###
+ IP = 192.168.47.150
+ ###
+ 
+ 
+ With DHCP relay set to 192.168.47.9, IP should NOT be that address:
+ 
+   ip netns exec client dhclient -d -v p2 -g 192.168.47.9
+ 
+ 
+ With the affected dnsmasq package, we will see an error:
+ dnsmasq-dhcp: DHCPREQUEST(p1) 192.168.47.150 aa:a0:9d:00:5b:d6 
+ dnsmasq-dhcp: DHCPACK(p1) 192.168.47.150 aa:a0:9d:00:5b:d6 j-dnsmasq-2042587
+ ###
+ IP = 192.168.47.9
+ TEST FAILED
+ ###
+ 
+ The error is that the obtained IP is that of the dhcp relay (provided
+ via the -g option).
+ 
+ With the fixed dnsmasq package, "TEST FAILED" must not appear, and the
+ IP should not be that of the provided dhcp relay.
+ 
  
  [ Where problems could occur ]
  
   * Think about what the upload changes in the software. Imagine the change is
     wrong or breaks something else: how would this show up?
  
   * It is assumed that any SRU candidate patch is well-tested before
     upload and has a low overall risk of regression, but it's important
     to make the effort to think about what ''could'' happen in the
     event of a regression.
  
   * This must '''never''' be "None" or "Low", or entirely an argument as to why
     your upload is low risk.
  
   * This both shows the SRU team that the risks have been considered,
     and provides guidance to testers in regression-testing the SRU.
  
  [ Other Info ]
  
   * Anything else you think is useful to include
   * Anticipate questions from users, SRU, +1 maintenance, security teams and 
the Technical Board
   * and address these questions in advance
  
  [ Original description ]
  
  When upgrading from focal to jammy, existing dnsmasq dhcp-scripts
  stopped working in an environment where a DHCP relay is in use. Instead
  of the expected client IP address, the script gets the _relay_ IP
  address as an argument. From dnsmasq documentation for --dhcp-script:
  
  > The arguments to the process are "add", "old" or "del", the MAC
  address of the host (or DUID for IPv6) , the IP address, and the
  hostname, if known.
  
  I believe the change has been inadverently made in upstream commit
  527c3c7d0d3bb4bf5fad699f10cf0d1a45a54692
  
(https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=blobdiff;f=src/helper.c;h=02340a01c00031db0cc682c8a4a279cfc1db574e;hp=d81de9622e6d484a264496b2cd3638b4e15e9677;hb=527c3c7d0d3bb4bf5fad699f10cf0d1a45a54692;hpb=fcb4dcaf7cc8a86ac2533b933161b6455f75bf8f)
  as the commit message only speaks about inet_ntoa replacement and not
  the behavioral change it also introduces (previously the relay address
  was only set to the environment variable, now it effectively overrides
  the prevoiusly set client's IP address).
  
  dnsmasq 2.86-1.1ubuntu0.3 / Ubuntu 22.04

** Attachment removed: "setup-and-server.sh"

[Touch-packages] [Bug 2042587] Re: jammy's version breaks existing dhcp scripts with relay

Test script

** Description changed:

+ [ Impact ]
+ 
+  * An explanation of the effects of the bug on users and
+ 
+  * justification for backporting the fix to the stable release.
+ 
+  * In addition, it is helpful, but not required, to include an
+explanation of how the upload fixes this bug.
+ 
+ [ Test Plan ]
+ 
+  * detailed instructions how to reproduce the bug
+ 
+  * these should allow someone who is not familiar with the affected
+package to reproduce the bug and verify that the updated package fixes
+the problem.
+ 
+  * if other testing is appropriate to perform before landing this update,
+this should also be described here.
+ 
+ [ Where problems could occur ]
+ 
+  * Think about what the upload changes in the software. Imagine the change is
+wrong or breaks something else: how would this show up?
+ 
+  * It is assumed that any SRU candidate patch is well-tested before
+upload and has a low overall risk of regression, but it's important
+to make the effort to think about what ''could'' happen in the
+event of a regression.
+ 
+  * This must '''never''' be "None" or "Low", or entirely an argument as to why
+your upload is low risk.
+ 
+  * This both shows the SRU team that the risks have been considered,
+and provides guidance to testers in regression-testing the SRU.
+ 
+ [ Other Info ]
+  
+  * Anything else you think is useful to include
+  * Anticipate questions from users, SRU, +1 maintenance, security teams and 
the Technical Board
+  * and address these questions in advance
+ 
+ 
+ [ Original description ]
+ 
  When upgrading from focal to jammy, existing dnsmasq dhcp-scripts
  stopped working in an environment where a DHCP relay is in use. Instead
  of the expected client IP address, the script gets the _relay_ IP
  address as an argument. From dnsmasq documentation for --dhcp-script:
  
  > The arguments to the process are "add", "old" or "del", the MAC
  address of the host (or DUID for IPv6) , the IP address, and the
  hostname, if known.
  
  I believe the change has been inadverently made in upstream commit
  527c3c7d0d3bb4bf5fad699f10cf0d1a45a54692
  
(https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=blobdiff;f=src/helper.c;h=02340a01c00031db0cc682c8a4a279cfc1db574e;hp=d81de9622e6d484a264496b2cd3638b4e15e9677;hb=527c3c7d0d3bb4bf5fad699f10cf0d1a45a54692;hpb=fcb4dcaf7cc8a86ac2533b933161b6455f75bf8f)
  as the commit message only speaks about inet_ntoa replacement and not
  the behavioral change it also introduces (previously the relay address
  was only set to the environment variable, now it effectively overrides
  the prevoiusly set client's IP address).
  
  dnsmasq 2.86-1.1ubuntu0.3 / Ubuntu 22.04

** Description changed:

  [ Impact ]
  
-  * An explanation of the effects of the bug on users and
+ When upgrading from focal to jammy, existing dnsmasq dhcp-scripts
+ stopped working in an environment where a DHCP relay is in use. Instead
+ of the expected client IP address, the script gets the _relay_ IP
+ address as an argument.
  
-  * justification for backporting the fix to the stable release.
- 
-  * In addition, it is helpful, but not required, to include an
-explanation of how the upload fixes this bug.
  
  [ Test Plan ]
  
-  * detailed instructions how to reproduce the bug
+  * detailed instructions how to reproduce the bug
  
-  * these should allow someone who is not familiar with the affected
-package to reproduce the bug and verify that the updated package fixes
-the problem.
+  * these should allow someone who is not familiar with the affected
+    package to reproduce the bug and verify that the updated package fixes
+    the problem.
  
-  * if other testing is appropriate to perform before landing this update,
-this should also be described here.
+  * if other testing is appropriate to perform before landing this update,
+    this should also be described here.
  
  [ Where problems could occur ]
  
-  * Think about what the upload changes in the software. Imagine the change is
-wrong or breaks something else: how would this show up?
+  * Think about what the upload changes in the software. Imagine the change is
+    wrong or breaks something else: how would this show up?
  
-  * It is assumed that any SRU candidate patch is well-tested before
-upload and has a low overall risk of regression, but it's important
-to make the effort to think about what ''could'' happen in the
-event of a regression.
+  * It is assumed that any SRU candidate patch is well-tested before
+    upload and has a low overall risk of regression, but it's important
+    to make the effort to think about what ''could'' happen in the
+    event of a regression.
  
-  * This must '''never''' be "None" or "Low", or entirely an argument as to why
-your upload is low risk.
+  * This must '''never''' be "None" or "Low", or entirely an argument as to why
+    your upload is low risk.
  
-  * This both shows the SRU team

[Touch-packages] [Bug 1833322] Re: Consider removing irqbalance from default install on desktop images

2024-01-10 Thread Doug Smythies

Hi Christian,

Thank you for your reply to my post.

> I do not know the ping pong test,

A simple token passing ring, that is useful for getting the system to utilize
shallow idles states. Otherwise it can be difficult to get to such shallow
states on my test system, without them being timer based.
While not relevant to this thread, the test presents a challenge for the TEO
(Timer Events Orientated) idle governor, and the menu governor should perform
better.

> but on iperf, I think that is in the noise
> range as far as I remember.

Agreed. I am just searching for good example type tests is all.

> If you'd just re-run that as-is what is the delta
> on your test box?

Oh. it's repeatable. I just haven't got to re-testing it yet with 24.04
as my host hardware.

> let me ask, what kind of system (cpu, size, nodes, ...)
> was that.

Intel(R) Core(TM) i5-10600K CPU @ 4.10GHz
6 cores, 2 threads per core, 12 CPUs.
HWP enabled (A.K.A. Intel Speed Shift)
intel_pstate CPU frequency driver
powersave governor
teo idle governor (but menu used below)
No throttling involved, ever.

> Your results show no change or minimal
> degradation while at the same time losing
> a bit of power. Have you also had a chance
> to try the powerthresh argument
> that Steve mentioned above?

I was just searching for a good test, and since that post I did find a really
good one (not reported here). However, that was with 20.04 which has an old
version of irqbalance. So I made my system dual boot adding 24.04. That same
test is now not good at all for showing any differences.
And yes, also tested with the powerthresh argument.
Just for completeness, the attached graph shows processor package power and the
only other graph that had some slight signal above the noise, the "idle state 1
was to deep" graph.
The test: 6 ping pong pairs, with almost no work done at each stop, 300 million
loops. About 27 minutes.
Legend:
irqb-menu-disable: irqbalance disabled, menu governor.
irqb-menu-enable-1: irqbalance enabled with powerthresh=1, menu governor.
irqb-menu-enable: irqbalance enabled, menu governor.

Power: see graph, same for all.
irqbalance disabled: 5.1854 uSec/loop
irqbalance enabled powerthresh=1: 5.1966 uSec/loop
irqbalance enabled: 5.1817 uSec/loop

** Attachment added: "power-and-1-above.png"

https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1833322/+attachment/5738151/+files/power-and-1-above.png

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

Title:
Consider removing irqbalance from default install on desktop images

Status in Ubuntu on IBM z Systems:
New
Status in irqbalance package in Ubuntu:
Confirmed
Status in ubuntu-meta package in Ubuntu:
Confirmed

Bug description:
as per https://github.com/pop-os/default-settings/issues/60

Distribution (run cat /etc/os-release):

$ cat /etc/os-release
NAME="Pop!_OS"
VERSION="19.04"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Pop!_OS 19.04"
VERSION_ID="19.04"
HOME_URL="https://system76.com/pop;
SUPPORT_URL="http://support.system76.com;
BUG_REPORT_URL="https://github.com/pop-os/pop/issues;
PRIVACY_POLICY_URL="https://system76.com/privacy;
VERSION_CODENAME=disco
UBUNTU_CODENAME=disco

Related Application and/or Package Version (run apt policy $PACKAGE
NAME):

$ apt policy irqbalance
irqbalance:
Installed: 1.5.0-3ubuntu1
Candidate: 1.5.0-3ubuntu1
Version table:
*** 1.5.0-3ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
100 /var/lib/dpkg/status

$ apt rdepends irqbalance
irqbalance
Reverse Depends:
Recommends: ubuntu-standard
gce-compute-image-packages

Issue/Bug Description:

as per konkor/cpufreq#48 and
http://konkor.github.io/cpufreq/faq/#irqbalance-detected

irqbalance is technically not needed on desktop systems (supposedly it
is mainly for servers), and may actually reduce performance and power
savings. It appears to provide benefits only to server environments
that have relatively-constant loading. If it is truly a server-
oriented package, then it shouldn't be installed by default on a
desktop/laptop system and shouldn't be included in desktop OS images.

Steps to reproduce (if you know):

This is potentially an issue with all default installs.

Expected behavior:

n/a

Other Notes:

I can safely remove it via "sudo apt purge irqbalance" without any
apparent adverse side-effects. If someone is running a situation where
they need it, then they always have the option of installing it from
the repositories.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1833322/+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 2048925] Re: Got crash notification, cant report crash since report tool crashed gathering data and got 2, then 3, then 4 crashes

** Attachment added: "Crash 4.png"
   
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2048925/+attachment/5738147/+files/Crash%204.png

** Description changed:

  Got crash notification, cant report crash since report tool crashed
- gathering data and got 2, then 3, then 4 crashes
+ gathering data and got 2, then i started making screenshots then 3, then
+ 4 crashes
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apport 2.20.11-0ubuntu82.5
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-39-generic x86_64
  ApportLog:
-  ERROR: apport (pid 157240) Wed Jan 10 14:48:06 2024: called for pid 156913, 
signal 11, core limit 0, dump mode 1
-  ERROR: apport (pid 157240) Wed Jan 10 14:48:06 2024: executable: 
/usr/bin/peek (command line "/usr/bin/peek --gapplication-service")
-  ERROR: apport (pid 157240) Wed Jan 10 14:48:06 2024: is_closing_session(): 
Could not determine DBUS socket.
-  ERROR: apport (pid 157240) Wed Jan 10 14:48:08 2024: wrote report 
/var/crash/_usr_bin_peek.1000.crash
+  ERROR: apport (pid 157240) Wed Jan 10 14:48:06 2024: called for pid 156913, 
signal 11, core limit 0, dump mode 1
+  ERROR: apport (pid 157240) Wed Jan 10 14:48:06 2024: executable: 
/usr/bin/peek (command line "/usr/bin/peek --gapplication-service")
+  ERROR: apport (pid 157240) Wed Jan 10 14:48:06 2024: is_closing_session(): 
Could not determine DBUS socket.
+  ERROR: apport (pid 157240) Wed Jan 10 14:48:08 2024: wrote report 
/var/crash/_usr_bin_peek.1000.crash
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Wed Jan 10 20:39:45 2024
  InstallationDate: Installed on 2024-01-05 (5 days ago)
  InstallationMedia: Kubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  Got crash notification, cant report crash since report tool crashed
- gathering data and got 2, then i started making screenshots then 3, then
- 4 crashes
+ gathering data and each time i clicked to continue sending or gathering
+ data then got new crashes got 2, then i started making screenshots then
+ 3, then 4 crashes then out of nowhere Doplin opened in Pictures folder.
+ No other folders didnt close so Dolphine didnt really crash. Dolphin was
+ swimming :)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apport 2.20.11-0ubuntu82.5
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-39-generic x86_64
  ApportLog:
   ERROR: apport (pid 157240) Wed Jan 10 14:48:06 2024: called for pid 156913, 
signal 11, core limit 0, dump mode 1
   ERROR: apport (pid 157240) Wed Jan 10 14:48:06 2024: executable: 
/usr/bin/peek (command line "/usr/bin/peek --gapplication-service")
   ERROR: apport (pid 157240) Wed Jan 10 14:48:06 2024: is_closing_session(): 
Could not determine DBUS socket.
   ERROR: apport (pid 157240) Wed Jan 10 14:48:08 2024: wrote report 
/var/crash/_usr_bin_peek.1000.crash
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Wed Jan 10 20:39:45 2024
  InstallationDate: Installed on 2024-01-05 (5 days ago)
  InstallationMedia: Kubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Got crash notification, cant report crash since report tool crashed
  gathering data and got 2, then 3, then 4 crashes

Status in apport package in Ubuntu:
  New

Bug description:
  Got crash notification, cant report crash since report tool crashed
  gathering data and each time i clicked to continue sending or
  gathering data then got new crashes got 2, then i started making
  screenshots then 3, then 4 crashes then out of nowhere Doplin opened
  in Pictures folder. No other folders didnt close so Dolphine didnt
  really crash. Dolphin was swimming :)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apport 2.20.11-0ubuntu82.5
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-39-generic x86_64
  ApportLog:
   ERROR: apport (pid 157240) Wed Jan 10 14:48:06 2024: called for pid 156913, 
signal 11, core limit 0, dump mode 1
   ERROR: apport (pid 157240) Wed Jan 10 14:48:06 2024: executable: 
/usr/bin/peek (command line "/usr/bin/peek --gapplication-service")
   ERROR: apport (pid 157240) Wed Jan 10 14:48:06 2024: is_closing_session(): 
Could not determine DBUS socket.
   ERROR: apport (pid 157240) Wed Jan 10 14:48:08 2024: wrote report 
/var/crash/_usr_bin_peek.1000.crash
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64

[Touch-packages] [Bug 2048925] Re: Got crash notification, cant report crash since report tool crashed gathering data and got 2, then 3, then 4 crashes

** Attachment added: "Crash 2.png"
   
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2048925/+attachment/5738144/+files/Crash%202.png

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

Title:
  Got crash notification, cant report crash since report tool crashed
  gathering data and got 2, then 3, then 4 crashes

Status in apport package in Ubuntu:
  New

Bug description:
  Got crash notification, cant report crash since report tool crashed
  gathering data and each time i clicked to continue sending or
  gathering data then got new crashes got 2, then i started making
  screenshots then 3, then 4 crashes then out of nowhere Doplin opened
  in Pictures folder. No other folders didnt close so Dolphine didnt
  really crash. Dolphin was swimming :)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apport 2.20.11-0ubuntu82.5
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-39-generic x86_64
  ApportLog:
   ERROR: apport (pid 157240) Wed Jan 10 14:48:06 2024: called for pid 156913, 
signal 11, core limit 0, dump mode 1
   ERROR: apport (pid 157240) Wed Jan 10 14:48:06 2024: executable: 
/usr/bin/peek (command line "/usr/bin/peek --gapplication-service")
   ERROR: apport (pid 157240) Wed Jan 10 14:48:06 2024: is_closing_session(): 
Could not determine DBUS socket.
   ERROR: apport (pid 157240) Wed Jan 10 14:48:08 2024: wrote report 
/var/crash/_usr_bin_peek.1000.crash
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Wed Jan 10 20:39:45 2024
  InstallationDate: Installed on 2024-01-05 (5 days ago)
  InstallationMedia: Kubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.1)
  PackageArchitecture: all
  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/2048925/+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 2048925] Re: Got crash notification, cant report crash since report tool crashed gathering data and got 2, then 3, then 4 crashes

** Attachment added: "Crash 3.png"
   
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2048925/+attachment/5738146/+files/Crash%203.png

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

Title:
  Got crash notification, cant report crash since report tool crashed
  gathering data and got 2, then 3, then 4 crashes

Status in apport package in Ubuntu:
  New

Bug description:
  Got crash notification, cant report crash since report tool crashed
  gathering data and each time i clicked to continue sending or
  gathering data then got new crashes got 2, then i started making
  screenshots then 3, then 4 crashes then out of nowhere Doplin opened
  in Pictures folder. No other folders didnt close so Dolphine didnt
  really crash. Dolphin was swimming :)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apport 2.20.11-0ubuntu82.5
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-39-generic x86_64
  ApportLog:
   ERROR: apport (pid 157240) Wed Jan 10 14:48:06 2024: called for pid 156913, 
signal 11, core limit 0, dump mode 1
   ERROR: apport (pid 157240) Wed Jan 10 14:48:06 2024: executable: 
/usr/bin/peek (command line "/usr/bin/peek --gapplication-service")
   ERROR: apport (pid 157240) Wed Jan 10 14:48:06 2024: is_closing_session(): 
Could not determine DBUS socket.
   ERROR: apport (pid 157240) Wed Jan 10 14:48:08 2024: wrote report 
/var/crash/_usr_bin_peek.1000.crash
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Wed Jan 10 20:39:45 2024
  InstallationDate: Installed on 2024-01-05 (5 days ago)
  InstallationMedia: Kubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.1)
  PackageArchitecture: all
  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/2048925/+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 2048925] Re: Got crash notification, cant report crash since report tool crashed gathering data and got 2, then 3, then 4 crashes

** Attachment added: "Crash 1.png"
   
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2048925/+attachment/5738143/+files/Crash%201.png

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

Title:
  Got crash notification, cant report crash since report tool crashed
  gathering data and got 2, then 3, then 4 crashes

Status in apport package in Ubuntu:
  New

Bug description:
  Got crash notification, cant report crash since report tool crashed
  gathering data and each time i clicked to continue sending or
  gathering data then got new crashes got 2, then i started making
  screenshots then 3, then 4 crashes then out of nowhere Doplin opened
  in Pictures folder. No other folders didnt close so Dolphine didnt
  really crash. Dolphin was swimming :)

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apport 2.20.11-0ubuntu82.5
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-39-generic x86_64
  ApportLog:
   ERROR: apport (pid 157240) Wed Jan 10 14:48:06 2024: called for pid 156913, 
signal 11, core limit 0, dump mode 1
   ERROR: apport (pid 157240) Wed Jan 10 14:48:06 2024: executable: 
/usr/bin/peek (command line "/usr/bin/peek --gapplication-service")
   ERROR: apport (pid 157240) Wed Jan 10 14:48:06 2024: is_closing_session(): 
Could not determine DBUS socket.
   ERROR: apport (pid 157240) Wed Jan 10 14:48:08 2024: wrote report 
/var/crash/_usr_bin_peek.1000.crash
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Wed Jan 10 20:39:45 2024
  InstallationDate: Installed on 2024-01-05 (5 days ago)
  InstallationMedia: Kubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.1)
  PackageArchitecture: all
  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/2048925/+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 2042587] Re: jammy's version breaks existing dhcp scripts with relay

Reproduced the problem and verified the fix.

@timotunk, if you would like to give the fix a try, it's available in
this PPA for jammy:

https://launchpad.net/~ahasenack/+archive/ubuntu/dnsmasq-
relay-2042587/+packages

I'll in the meantime prepare the SRU paperwork and merge proposal for
review.


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

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

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

Status in dnsmasq package in Ubuntu:
  New
Status in dnsmasq source package in Jammy:
  In Progress

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

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

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

  dnsmasq 2.86-1.1ubuntu0.3 / Ubuntu 22.04

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


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

[Touch-packages] [Bug 2048925] [NEW] Got crash notification, cant report crash since report tool crashed gathering data and got 2, then 3, then 4 crashes

Public bug reported:

Got crash notification, cant report crash since report tool crashed
gathering data and got 2, then 3, then 4 crashes

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: apport 2.20.11-0ubuntu82.5
ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-39-generic x86_64
ApportLog:
 ERROR: apport (pid 157240) Wed Jan 10 14:48:06 2024: called for pid 156913, 
signal 11, core limit 0, dump mode 1
 ERROR: apport (pid 157240) Wed Jan 10 14:48:06 2024: executable: /usr/bin/peek 
(command line "/usr/bin/peek --gapplication-service")
 ERROR: apport (pid 157240) Wed Jan 10 14:48:06 2024: is_closing_session(): 
Could not determine DBUS socket.
 ERROR: apport (pid 157240) Wed Jan 10 14:48:08 2024: wrote report 
/var/crash/_usr_bin_peek.1000.crash
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Wed Jan 10 20:39:45 2024
InstallationDate: Installed on 2024-01-05 (5 days ago)
InstallationMedia: Kubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.1)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug jammy

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

Title:
  Got crash notification, cant report crash since report tool crashed
  gathering data and got 2, then 3, then 4 crashes

Status in apport package in Ubuntu:
  New

Bug description:
  Got crash notification, cant report crash since report tool crashed
  gathering data and got 2, then 3, then 4 crashes

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apport 2.20.11-0ubuntu82.5
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-39-generic x86_64
  ApportLog:
   ERROR: apport (pid 157240) Wed Jan 10 14:48:06 2024: called for pid 156913, 
signal 11, core limit 0, dump mode 1
   ERROR: apport (pid 157240) Wed Jan 10 14:48:06 2024: executable: 
/usr/bin/peek (command line "/usr/bin/peek --gapplication-service")
   ERROR: apport (pid 157240) Wed Jan 10 14:48:06 2024: is_closing_session(): 
Could not determine DBUS socket.
   ERROR: apport (pid 157240) Wed Jan 10 14:48:08 2024: wrote report 
/var/crash/_usr_bin_peek.1000.crash
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Wed Jan 10 20:39:45 2024
  InstallationDate: Installed on 2024-01-05 (5 days ago)
  InstallationMedia: Kubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.1)
  PackageArchitecture: all
  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/2048925/+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 1731628] Re: Cannot add caldav calendar

2024-01-10 Thread Jeremy Bícha

This will be possible with Ubuntu 24.04 LTS by adding the account using
the Settings app > Online Accounts > WebDAV

** Package changed: gnome-calendar (Ubuntu) => gnome-online-accounts
(Ubuntu)

** Changed in: gnome-online-accounts (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  Cannot add caldav calendar

Status in gnome-online-accounts package in Ubuntu:
  Fix Committed

Bug description:
  Hi,

  I try to add a caldav calendar

  calendars -> Add -> From Web ->
  https://posteo.de:8443/calendars/max.mustermann/default/

  and I hit enter but the "add" button in the right upper corner remains
  grayed out.

  Kind regards

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-calendar 3.26.2-1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 11 14:47:03 2017
  InstallationDate: Installed on 2017-11-11 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171109)
  SourcePackage: gnome-calendar
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1731628/+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 2046356] Re: Update URL for Support information in MOTD message

2024-01-10 Thread Lucas Albuquerque Medeiros de Moura

The tests were re-triggered and they should not be an issue anymore

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

Title:
  Update URL for Support information in MOTD message

Status in base-files package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  Fix Committed
Status in base-files source package in Bionic:
  Fix Committed
Status in base-files source package in Focal:
  Fix Committed
Status in base-files source package in Jammy:
  Fix Committed
Status in base-files source package in Lunar:
  Fix Committed
Status in base-files source package in Mantic:
  Fix Committed
Status in base-files source package in Noble:
  Fix Released

Bug description:
  
  [Impact]
  When users see the MOTD message, they are currently seeing an outdated url 
under the support information.
  Even though the outdated url redirects to new Ubuntu Pro webpage, we believe 
the users should still see
  the correct url from the start

  [Test Case]

  - Launch a LXD container for any of the affected releases
  - Install the package with this fix applied
  - Install `update-motd` package
  - Run `update-motd` and confirm the Support url is now the correct one

  [Regression Potential]
  If users are parsing MOTD for some reason, the url change might break that 
logic now. However, parsing MOTD messages is not a supported flow, so we 
believe regression potential is low here.

  [Discussion]
  Since we want users to be aware of what Ubuntu Pro is, we should highlight 
the right product name on any place that is still using the old "advantage" 
name. Updating the support URL here is a step into this direction

  [Original Bug Description]
  On the file 10-help-text, we are printing the following line on MOTD:

  * Support: https://ubuntu.com/advantage

  We should update the url to https://ubuntu.com/pro instead, as this
  will the default url for support information now

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/2046356/+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 1851046] Re: Enable Last.fm provider

2024-01-10 Thread Jeremy Bícha

GNOME 46 Alpha has removed the Last.fm provider

** Changed in: gnome-online-accounts (Ubuntu)
   Status: New => Won't Fix

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

Title:
  Enable Last.fm provider

Status in gnome-online-accounts package in Ubuntu:
  Won't Fix

Bug description:
  Since a while now GOA supports Last.fm accounts but for some reason this 
provider is excluded in the Ubuntu build parameters of this package.
  Is there a specific reason why this is not enabled? Would it be possible to 
enable this provider as well?

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-online-accounts 3.34.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Nov  2 16:07:05 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-11-26 (1437 days ago)
  InstallationMedia: It
  SourcePackage: gnome-online-accounts
  UpgradeStatus: Upgraded to eoan on 2019-10-20 (13 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1851046/+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 1731628] [NEW] Cannot add caldav calendar

2024-01-10 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

Hi,

I try to add a caldav calendar

calendars -> Add -> From Web ->
https://posteo.de:8443/calendars/max.mustermann/default/

and I hit enter but the "add" button in the right upper corner remains
grayed out.

Kind regards

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-calendar 3.26.2-1
ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
Uname: Linux 4.13.0-16-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Nov 11 14:47:03 2017
InstallationDate: Installed on 2017-11-11 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171109)
SourcePackage: gnome-calendar
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-online-accounts (Ubuntu)
 Importance: Low
 Status: Fix Committed


** Tags: amd64 apport-bug bionic
-- 
Cannot add caldav calendar
https://bugs.launchpad.net/bugs/1731628
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to gnome-online-accounts 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 2047780] Re: BlueZ release 5.71

2024-01-10 Thread Gianfranco Costamagna

two patches are now with Debian bugs
 Opened #1060393 in bluez 5.67-1 by Gianfranco Costamagna (locutusofborg) 
«please update patch 
work-around-Logitech-diNovo-Edge-keyboard-firmware-i.patch». 
https://bugs.debian.org/1060393
 Opened #1060395 in bluez by Gianfranco Costamagna (locutusofborg) «please 
add simple testsuite from Ubuntu». https://bugs.debian.org/1060395

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

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

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

Title:
  BlueZ release 5.71

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  Release BlueZ 5.71 to noble.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+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 2047780] Re: BlueZ release 5.71

2024-01-10 Thread Gianfranco Costamagna

and ell-dev needs a i386 whitelist, not sure

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

Title:
  BlueZ release 5.71

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  Release BlueZ 5.71 to noble.

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


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

[Touch-packages] [Bug 2033422] Re: openssl: backport to jammy "clear method store / query cache confusion"

2024-01-10 Thread Simon Chopin

Reviewed and uploaded.

For the particular patch series attached to this very bug, I'm seeing
the patchset as two distincts parts. First are a few optimization
patches by being more selective in flushing some caches, whereas the
second part are behaviour changes that belong more in the realm of fixes
than optimization. Given the nature of those fixes (e.g. "Complete the
cleanup of an algorithm in OSSL_METHOD_STORE"), I'm *assuming* that they
were hidden by the previous aggressive flushing, especially since they
originate from the same PR
(https://github.com/openssl/openssl/pull/18151)

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

In http://pad.lv/2009544 , Rafael also shared his performance numbers
and they are relatable to these. He used slightly different versions
(upstreams rather than patched with cherry-picks) but at least one of
the version used does not include other performance change. He also
used different hardware and this performance issue seems to depend on
the number of CPUs available but also obtained a performance several
times better. Results on a given machine vary also very little across
runs (less than 2% variation on runs of size 10). They are also very
similar on a Raspberry Pi 4 (8GB).

The benchmark uses https://www.google.com/humans.txt which takes
around 130ms to download on my machine but I modified the script to
download something only 20ms away. Results are so close to the ones
using humans.txt that they are within the error margin. This is
consistent with the high-concurrency in the

[Touch-packages] [Bug 2047780] Re: BlueZ release 5.71

2024-01-10 Thread Gianfranco Costamagna

Hello, I did the merge from Debian, now the packaging is really simpler,
please have a look and upload if possible.

** Attachment added: "bluez_5.71-1ubuntu1.debian.tar.xz"
   
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+attachment/5738106/+files/bluez_5.71-1ubuntu1.debian.tar.xz

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

Title:
  BlueZ release 5.71

Status in bluez package in Ubuntu:
  Fix Released

Bug description:
  Release BlueZ 5.71 to noble.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2047780/+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 2035122] Re: Under ubuntu core/core-desktop, /etc/default/locale is not modifiable

2024-01-10 Thread Sergio Costas

Sorry for the delay, I had some trouble these days to build a Core
Desktop image mixing our PPA and the "proposed" repository. Finally I've
been able to do so and test this, and it seems to work as expected.
Thanks!

** Description changed:

  [Impact]
  
  When working with ubuntu core or ubuntu core desktop, neither
  */etc/default/locale* nor */etc/default/keyboard* are modifiable, so
  it's not possible to set the global keyboard or the global language.
  This is required to allow to set the GDM language, and the default one
  during installation.
  
  The first half of the solution is to create the folder
  */etc/writable/default*, and make soft-links from */etc/default/locale*
  to */etc/writable/default/locale* and from */etc/default/keyboard* to
  */etc/writable/default/keyboard*, just like it is already being done
  with */etc/hostname*, */etc/issue*, */etc/localtime*, */etc/motd* and ,
  */etc/timezone*.
  
  This solution, unfortunately, isn't complete. Although any application
  that just reads the files will work, not all of the applications that
  write to them will; specifically the systemd utilities that set the
  contents for those files, because they don't open the file directly;
  instead, they create first the new file in the same folder than the old
  one, fill its contents, and only then delete the old one and rename the
  new one. To solve this, systemd in Ubuntu already has several patches
  that detect if a file is a soft-link, in which case it replaces the old
  path with the destination one.
  
  Currently I have in place a patch for Ubuntu Core Desktop that
  implements both changes for both */etc/default/locale* and
  */etc/default/keyboard*.
  
  [Test plan]
  
- Using *sudo localectl set-lang LANG="xx_YY.UTF-8"* in an Ubuntu Core or
+ Using *sudo localectl set-locale xx_YY.UTF-8* in an Ubuntu Core or
  Ubuntu Core Desktop admin terminal must change the locale to the
  specified one, which can be checked by reading the */etc/default/locale*
  file. Also, *localectl* must return the new locale.
  
  Using *sudo dbus-send --system --print-reply
  --dest=org.freedesktop.locale1 /org/freedesktop/locale1
  org.freedesktop.locale1.SetX11Keyboard string:XX string:pc10Y string:
  string: boolean:true boolean:false" must change the
  */etc/default/keyboard* file to layout XX and model PC10Y (being Y
  either 1, 2, 4 or 5). Reading the file allows to check it. Also,
  *localectl status* must return the layout and model values in "X11
  Layout" and "X11 Model" entries.
  
  [Where problems could occur]
  
  In general, applications just read the content of the file and use the
  DBus interface to set the locale, so only those applications that modify
  by themselves the */etc/default/keyboard* and/or */etc/default/locale*
  would present a problem, in which case they would require specific
  patches. Anyway, those applications neither would work with the current
  state (with those files in a read-only filesystem).
  
  [Other info]
  
  For Noble, this will be addressed when we merge systemd v255 from
  Debian. This is only needed on core, so we don't need to fix for Mantic
  or Lunar.

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

Title:
  Under ubuntu core/core-desktop, /etc/default/locale is not modifiable

Status in systemd package in Ubuntu:
  New
Status in systemd source package in Jammy:
  Fix Committed
Status in systemd source package in Lunar:
  Won't Fix
Status in systemd source package in Mantic:
  Won't Fix

Bug description:
  [Impact]

  When working with ubuntu core or ubuntu core desktop, neither
  */etc/default/locale* nor */etc/default/keyboard* are modifiable, so
  it's not possible to set the global keyboard or the global language.
  This is required to allow to set the GDM language, and the default one
  during installation.

  The first half of the solution is to create the folder
  */etc/writable/default*, and make soft-links from
  */etc/default/locale* to */etc/writable/default/locale* and from
  */etc/default/keyboard* to */etc/writable/default/keyboard*, just like
  it is already being done with */etc/hostname*, */etc/issue*,
  */etc/localtime*, */etc/motd* and , */etc/timezone*.

  This solution, unfortunately, isn't complete. Although any application
  that just reads the files will work, not all of the applications that
  write to them will; specifically the systemd utilities that set the
  contents for those files, because they don't open the file directly;
  instead, they create first the new file in the same folder than the
  old one, fill its contents, and only then delete the old one and
  rename the new one. To solve this, systemd in Ubuntu already has
  several patches that detect if a file is a soft-link, in which case it
  replaces the old path with the destination one.

  Currently I have in place a patch for Ubuntu

[Touch-packages] [Bug 2046498] Re: test-execute fails in LXD with failure in exec-networknamespacepath-privatemounts-no.service

2024-01-10 Thread Nick Rosbrook

https://github.com/systemd/systemd/pull/30854

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

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

Title:
  test-execute fails in LXD with failure in exec-networknamespacepath-
  privatemounts-no.service

Status in systemd package in Ubuntu:
  Triaged

Bug description:
  This is in v255. This log snippet is taken from a local autopkgtest
  build:

  exec-networknamespacepath-privatemounts-no.service: Child 4580 belongs to 
exec-networknamespacepath-privatemounts-no.service.
  exec-networknamespacepath-privatemounts-no.service: Main process exited, 
code=exited, status=0/SUCCESS (success)
  exec-networknamespacepath-privatemounts-no.service: Running next main command 
for state start.
  exec-networknamespacepath-privatemounts-no.service: Will spawn child 
(service_run_next_main): /bin/sh
  exec-networknamespacepath-privatemounts-no.service: Passing 0 fds to service
  exec-networknamespacepath-privatemounts-no.service: About to execute: /bin/sh 
-x -c "ip link show dummy-test-ns"
  Serializing sd-executor-state to memfd.
  exec-networknamespacepath-privatemounts-no.service: Forked /bin/sh as 4581
  Closing set fd 19 (socket:[109908])
  Closing set fd 21 (socket:[51])
  Closing set fd 20 (socket:[50])
  Received SIGCHLD from PID 4581 (sh).
  Child 4581 (sh) died (code=exited, status=1/FAILURE)
  exec-networknamespacepath-privatemounts-no.service: Child 4581 belongs to 
exec-networknamespacepath-privatemounts-no.service.
  exec-networknamespacepath-privatemounts-no.service: Main process exited, 
code=exited, status=1/FAILURE
  exec-networknamespacepath-privatemounts-no.service: Failed with result 
'exit-code'.
  exec-networknamespacepath-privatemounts-no.service: Service will not restart 
(restart setting)
  exec-networknamespacepath-privatemounts-no.service: Changed start -> failed
  exec-networknamespacepath-privatemounts-no.service: Unit entered failed state.
  exec-networknamespacepath-privatemounts-no.service: Consumed 23ms CPU time.
  src/test/test-execute.c:1124:test_exec_networknamespacepath: 
exec-networknamespacepath-privatemounts-no.service: can_unshare=no: exit status 
1, expected 0
  (test-execute-without-unshare) terminated by signal ABRT.
  Assertion 'r >= 0' failed at src/test/test-execute.c:1330, function 
prepare_ns(). Aborting.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2046498/+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 1833322] Re: Consider removing irqbalance from default install on desktop images

2024-01-10 Thread Loïc Minier

Just saw a mention of this bug, and I wanted to provide another
datapoint: I recently sponsored a SRU for an irqbalance bugfix (LP
#2038300), it was for an edge server platform (NVIDIA IGX Orin). What I
noticed was that the code was inherently racy and hard to validate with
unit tests because it's trying to read from multiple kernel data
structures in virtual filesystems and then take action. I do believe its
function would better be provided in the kernel itself.

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

Title:
  Consider removing irqbalance from default install on desktop images

Status in Ubuntu on IBM z Systems:
  New
Status in irqbalance package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  as per https://github.com/pop-os/default-settings/issues/60

  Distribution (run cat /etc/os-release):

  $ cat /etc/os-release
  NAME="Pop!_OS"
  VERSION="19.04"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Pop!_OS 19.04"
  VERSION_ID="19.04"
  HOME_URL="https://system76.com/pop;
  SUPPORT_URL="http://support.system76.com;
  BUG_REPORT_URL="https://github.com/pop-os/pop/issues;
  PRIVACY_POLICY_URL="https://system76.com/privacy;
  VERSION_CODENAME=disco
  UBUNTU_CODENAME=disco

  Related Application and/or Package Version (run apt policy $PACKAGE
  NAME):

  $ apt policy irqbalance
  irqbalance:
  Installed: 1.5.0-3ubuntu1
  Candidate: 1.5.0-3ubuntu1
  Version table:
  *** 1.5.0-3ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

  $ apt rdepends irqbalance
  irqbalance
  Reverse Depends:
  Recommends: ubuntu-standard
  gce-compute-image-packages

  Issue/Bug Description:

  as per konkor/cpufreq#48 and
  http://konkor.github.io/cpufreq/faq/#irqbalance-detected

  irqbalance is technically not needed on desktop systems (supposedly it
  is mainly for servers), and may actually reduce performance and power
  savings. It appears to provide benefits only to server environments
  that have relatively-constant loading. If it is truly a server-
  oriented package, then it shouldn't be installed by default on a
  desktop/laptop system and shouldn't be included in desktop OS images.

  Steps to reproduce (if you know):

  This is potentially an issue with all default installs.

  Expected behavior:

  n/a

  Other Notes:

  I can safely remove it via "sudo apt purge irqbalance" without any
  apparent adverse side-effects. If someone is running a situation where
  they need it, then they always have the option of installing it from
  the repositories.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1833322/+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 1969365] Re: focal: backport kexec fallback patch

2024-01-10 Thread Dan Watkins

In the VM created in my above comment, I enabled proposed, installed the
new systemd and rebooted.  After that, I re-ran:

cd /boot
sudo kexec -l vmlinuz --initrd initrd.img --append 
'BOOT_IMAGE=/boot/vmlinuz-5.4.0-167-generic root=LABEL=cloudimg-rootfs ro 
console=tty1 console=ttyS0'
sudo reboot

And observed the following in the console:

[  OK  ] Reached target Final Step.
 Starting Reboot via kexec...
[  102.782246] systemd-udevd[369]: anon_vma(937:udisks2.service): Worker [960] 
did not accept message, killing the worker: Connection refused
[  102.784224] systemd-udevd[369]: anon_vma(937:udisks2.service): Worker [963] 
did not accept message, killing the worker: Connection refused
[  102.786398] systemd-udevd[369]: anon_vma(937:udisks2.service): Worker [966] 
did not accept message, killing the worker: Connection refused
[  102.788390] systemd-udevd[369]: anon_vma(937:udisks2.service): Worker [968] 
did not accept message, killing the worker: Connection refused
[  102.789954] systemd-udevd[369]: anon_vma(937:udisks2.service): Worker [962] 
did not accept message, killing the worker: Connection refused
[  102.791562] systemd-udevd[369]: anon_vma(937:udisks2.service): Worker [961] 
did not accept message, killing the worker: Connection refused
[  102.793198] systemd-udevd[369]: anon_vma(937:udisks2.service): Worker [964] 
did not accept message, killing the worker: Connection refused
[  102.794669] systemd-udevd[369]: anon_vma(937:udisks2.service): Worker [967] 
did not accept message, killing the worker: Connection refused
[  102.796841] systemd-udevd[369]: anon_vma(937:udisks2.service): Worker [965] 
did not accept message, killing the worker: Connection refused
[  102.904092] kexec_core: Starting new kernel
[0.00] Linux version 5.4.0-167-generic (buildd@lcy02-amd64-010) (gcc 
version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.2)) #184-Ubuntu SMP Tue Oct 31 
09:21:49 UTC 2023 (Ubuntu 5.4.0-167.184-generic 5.4.252)

So I can confirm that the new systemd addresses this bug.

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

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

Title:
  focal: backport kexec fallback patch

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Fix Committed

Bug description:
  It would be great if focal's systemd could have
  
https://github.com/systemd/systemd/commit/71180f8e57f8fbb55978b00a13990c79093ff7b3
  backported to it.

  [Impact]

  We have observed that kexec'ing to another kernel will fail as the
  drive containing the `kexec` binary has been unmounted by the time
  systemd attempts to do so, indicated in the console:

   Starting Reboot via kexec...
  [  163.960938] shutdown[1]: (sd-kexec) failed with exit status 1.
  [  163.963463] reboot: Restarting system

  [Test Plan]

  1) Launch a 20.04 instance
  2) `apt-get install kexec-tools`
  3) In `/boot`, filling in whatever  needed in your environment:

  kexec -l vmlinuz --initrd initrd.img --append ''

  4) `reboot`

  (I have reproduced this in a single-disk VM, so I assume it reproduces
  ~everywhere: if not, `apt-get remove kexec-tools` before the `reboot`
  could be used to emulate the unmounting.)

  [Where problems could occur]

  Users could inadvertently be relying on the current behaviour: if they
  have configured their systems to kexec, they currently will be
  rebooting normally, and this patch would cause them to start actually
  kexec'ing.

  [Other info]

  We're currently maintaining a systemd tree with only this patch added
  to focal's tree: this patch has received a bunch of testing from us in
  focal.

  This patch landed in v246, so it's already present in supported
  releases later than focal.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1969365/+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 1969365] Re: focal: backport kexec fallback patch

2024-01-10 Thread Dan Watkins

Apologies, I completely missed your comment, Nick!  I was just able to
reproduce this using uvtool.

To launch the VM (and monitor the console output):

uvt-simplestreams-libvirt sync release=focal arch=amd64
uvt-kvm create firsttest release=focal
virsh console firsttest

Then, within the instance via `uvt-kvm ssh firsttest`:

sudo apt update
sudo apt install kexec-tools
sudo reboot  # I wanted to check `virsh console` was getting output

After reboot and reconnecting:

cd /boot
sudo kexec -l vmlinuz --initrd initrd.img --append 
'BOOT_IMAGE=/boot/vmlinuz-5.4.0-167-generic root=LABEL=cloudimg-rootfs ro 
console=tty1 console=ttyS0'
sudo reboot

I then observed the following in `virsh console`'s output (note the
"Unmount All Filesystems", which is what I think is causing the
problem):

[  OK  ] Reached target Unmount All Filesystems.
 Stopping Monitoring of LVM…meventd or progress polling...
 Stopping Device-Mapper Multipath Device Controller...
[  OK  ] Stopped Create Static Device Nodes in /dev.
[  OK  ] Stopped Create System Users.
[  OK  ] Stopped Remount Root and Kernel File Systems.
[  OK  ] Stopped File System Check on Root Device.
[  OK  ] Stopped Device-Mapper Multipath Device Controller.
[  OK  ] Stopped Monitoring of LVM2… dmeventd or progress polling.
[  OK  ] Reached target Shutdown.
[  OK  ] Reached target Final Step.
 Starting Reboot via kexec...
[   53.030829] systemd-udevd[372]: proc_inode_cache(1258:kexec.service): Worker 
[960] did not accept message, killing the worker: Connection refused
[   53.032915] systemd-udevd[372]: proc_inode_cache(1258:kexec.service): Worker 
[954] did not accept message, killing the worker: Connection refused
[   53.034697] systemd-udevd[372]: proc_inode_cache(1258:kexec.service): Worker 
[953] did not accept message, killing the worker: Connection refused
[   53.036756] systemd-udevd[372]: proc_inode_cache(1258:kexec.service): Worker 
[955] did not accept message, killing the worker: Connection refused
[   53.039144] systemd-udevd[372]: proc_inode_cache(1258:kexec.service): Worker 
[956] did not accept message, killing the worker: Connection refused
[   53.041049] systemd-udevd[372]: proc_inode_cache(1258:kexec.service): Worker 
[958] did not accept message, killing the worker: Connection refused
[   53.042673] systemd-udevd[372]: proc_inode_cache(1258:kexec.service): Worker 
[961] did not accept message, killing the worker: Connection refused
[   53.123845] shutdown[1]: (sd-kexec) failed with exit status 1.
[   53.138542] reboot: Restarting system
[0.00] Linux version 5.4.0-167-generic (buildd@lcy02-amd64-010) (gcc 
version 9.4.0 (Ubuntu 9.4.0-1ubuntu1~20.04.2)) #184-Ubuntu SMP Tue Oct 31 
09:21:49 UTC 2023 (Ubuntu 5.4.0-167.184-generic 5.4.252)

(I initially tried to re-reproduce using an Incus VM (and so a community
image rather than a cloud-images one) and could not do so.  Executing
the above `kexec` command produced "ima: impossible to appraise a kernel
image without a file descriptor; try using kexec_file_load syscall." in
the console.  Adding `-s`/`--kexec-file-syscall` to the kexec command
caused it to exit zero, and the VM did then successfully kexec on
`reboot`.)

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

Title:
  focal: backport kexec fallback patch

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Focal:
  Fix Committed

Bug description:
  It would be great if focal's systemd could have
  
https://github.com/systemd/systemd/commit/71180f8e57f8fbb55978b00a13990c79093ff7b3
  backported to it.

  [Impact]

  We have observed that kexec'ing to another kernel will fail as the
  drive containing the `kexec` binary has been unmounted by the time
  systemd attempts to do so, indicated in the console:

   Starting Reboot via kexec...
  [  163.960938] shutdown[1]: (sd-kexec) failed with exit status 1.
  [  163.963463] reboot: Restarting system

  [Test Plan]

  1) Launch a 20.04 instance
  2) `apt-get install kexec-tools`
  3) In `/boot`, filling in whatever  needed in your environment:

  kexec -l vmlinuz --initrd initrd.img --append ''

  4) `reboot`

  (I have reproduced this in a single-disk VM, so I assume it reproduces
  ~everywhere: if not, `apt-get remove kexec-tools` before the `reboot`
  could be used to emulate the unmounting.)

  [Where problems could occur]

  Users could inadvertently be relying on the current behaviour: if they
  have configured their systems to kexec, they currently will be
  rebooting normally, and this patch would cause them to start actually
  kexec'ing.

  [Other info]

  We're currently maintaining a systemd tree with only this patch added
  to focal's tree: this patch has received a bunch of testing from us in
  focal.

  This patch landed in v246, so it's already present in supported
  releases later than

[Touch-packages] [Bug 1833322] Re: Consider removing irqbalance from default install on desktop images

2024-01-10 Thread bugproxy

** Tags added: architecture-s39064 bugnameltc-204586 severity-medium
targetmilestone-inin2404

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

Title:
  Consider removing irqbalance from default install on desktop images

Status in Ubuntu on IBM z Systems:
  New
Status in irqbalance package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  as per https://github.com/pop-os/default-settings/issues/60

  Distribution (run cat /etc/os-release):

  $ cat /etc/os-release
  NAME="Pop!_OS"
  VERSION="19.04"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Pop!_OS 19.04"
  VERSION_ID="19.04"
  HOME_URL="https://system76.com/pop;
  SUPPORT_URL="http://support.system76.com;
  BUG_REPORT_URL="https://github.com/pop-os/pop/issues;
  PRIVACY_POLICY_URL="https://system76.com/privacy;
  VERSION_CODENAME=disco
  UBUNTU_CODENAME=disco

  Related Application and/or Package Version (run apt policy $PACKAGE
  NAME):

  $ apt policy irqbalance
  irqbalance:
  Installed: 1.5.0-3ubuntu1
  Candidate: 1.5.0-3ubuntu1
  Version table:
  *** 1.5.0-3ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

  $ apt rdepends irqbalance
  irqbalance
  Reverse Depends:
  Recommends: ubuntu-standard
  gce-compute-image-packages

  Issue/Bug Description:

  as per konkor/cpufreq#48 and
  http://konkor.github.io/cpufreq/faq/#irqbalance-detected

  irqbalance is technically not needed on desktop systems (supposedly it
  is mainly for servers), and may actually reduce performance and power
  savings. It appears to provide benefits only to server environments
  that have relatively-constant loading. If it is truly a server-
  oriented package, then it shouldn't be installed by default on a
  desktop/laptop system and shouldn't be included in desktop OS images.

  Steps to reproduce (if you know):

  This is potentially an issue with all default installs.

  Expected behavior:

  n/a

  Other Notes:

  I can safely remove it via "sudo apt purge irqbalance" without any
  apparent adverse side-effects. If someone is running a situation where
  they need it, then they always have the option of installing it from
  the repositories.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1833322/+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 1833322] Re: Consider removing irqbalance from default install on desktop images

2024-01-10 Thread Frank Heimes

** Also affects: ubuntu-z-systems
   Importance: Undecided
   Status: New

** Changed in: ubuntu-z-systems
 Assignee: (unassigned) => bugproxy (bugproxy)

** Tags added: reverse-proxy-bugzilla

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

Title:
  Consider removing irqbalance from default install on desktop images

Status in Ubuntu on IBM z Systems:
  New
Status in irqbalance package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  as per https://github.com/pop-os/default-settings/issues/60

  Distribution (run cat /etc/os-release):

  $ cat /etc/os-release
  NAME="Pop!_OS"
  VERSION="19.04"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Pop!_OS 19.04"
  VERSION_ID="19.04"
  HOME_URL="https://system76.com/pop;
  SUPPORT_URL="http://support.system76.com;
  BUG_REPORT_URL="https://github.com/pop-os/pop/issues;
  PRIVACY_POLICY_URL="https://system76.com/privacy;
  VERSION_CODENAME=disco
  UBUNTU_CODENAME=disco

  Related Application and/or Package Version (run apt policy $PACKAGE
  NAME):

  $ apt policy irqbalance
  irqbalance:
  Installed: 1.5.0-3ubuntu1
  Candidate: 1.5.0-3ubuntu1
  Version table:
  *** 1.5.0-3ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

  $ apt rdepends irqbalance
  irqbalance
  Reverse Depends:
  Recommends: ubuntu-standard
  gce-compute-image-packages

  Issue/Bug Description:

  as per konkor/cpufreq#48 and
  http://konkor.github.io/cpufreq/faq/#irqbalance-detected

  irqbalance is technically not needed on desktop systems (supposedly it
  is mainly for servers), and may actually reduce performance and power
  savings. It appears to provide benefits only to server environments
  that have relatively-constant loading. If it is truly a server-
  oriented package, then it shouldn't be installed by default on a
  desktop/laptop system and shouldn't be included in desktop OS images.

  Steps to reproduce (if you know):

  This is potentially an issue with all default installs.

  Expected behavior:

  n/a

  Other Notes:

  I can safely remove it via "sudo apt purge irqbalance" without any
  apparent adverse side-effects. If someone is running a situation where
  they need it, then they always have the option of installing it from
  the repositories.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1833322/+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 2042587] Re: jammy's version breaks existing dhcp scripts with relay

I believe this to be the fix:
https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=patch;h=1c8855ed10d3923a9a4fd8a89f1c95439d4c8827

>From 1c8855ed10d3923a9a4fd8a89f1c95439d4c8827 Mon Sep 17 00:00:00 2001
From: Simon Kelley 
Date: Sun, 26 Dec 2021 16:35:54 +
Subject: [PATCH] Fix wrong client address for dhcp-script when DHCPv4 relay in
 use.

---
 src/helper.c | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/src/helper.c b/src/helper.c
index 02340a0..455a68c 100644
--- a/src/helper.c
+++ b/src/helper.c
@@ -432,8 +432,8 @@ int create_helper(int event_fd, int err_fd, uid_t uid, 
gid_t gid, long max_fd)
buf = grab_extradata_lua(buf, end, "relay_address");
  else if (data.giaddr.s_addr != 0)
{
- inet_ntop(AF_INET, , daemon->addrbuff, 
ADDRSTRLEN);
- lua_pushstring(lua, daemon->addrbuff);
+ inet_ntop(AF_INET, , daemon->dhcp_buff2, 
ADDRSTRLEN);
+ lua_pushstring(lua, daemon->dhcp_buff2);
  lua_setfield(lua, -2, "relay_address");
}
  
@@ -615,7 +615,7 @@ int create_helper(int event_fd, int err_fd, uid_t uid, 
gid_t gid, long max_fd)
{
  const char *giaddr = NULL;
  if (data.giaddr.s_addr != 0)
- giaddr = inet_ntop(AF_INET, , daemon->addrbuff, 
ADDRSTRLEN);
+ giaddr = inet_ntop(AF_INET, , daemon->dhcp_buff2, 
ADDRSTRLEN);
  my_setenv("DNSMASQ_RELAY_ADDRESS", giaddr, );
}
  
-- 
2.20.1


Committed a few months later in the same area. Will try to test it.

If that's really the fix, then only jammy is affected, because the patch is in 
v2.87 and later:
 dnsmasq | 2.80-1.1ubuntu1| focal   | source
 dnsmasq | 2.80-1.1ubuntu1.7  | focal-security  | source
 dnsmasq | 2.80-1.1ubuntu1.7  | focal-updates   | source
 dnsmasq | 2.86-1.1   | jammy   | source
 dnsmasq | 2.86-1.1ubuntu0.3  | jammy-security  | source
 dnsmasq | 2.86-1.1ubuntu0.4  | jammy-proposed  | source
 dnsmasq | 2.86-1.1ubuntu0.4  | jammy-updates   | source
 dnsmasq | 2.89-1 | lunar   | source
 dnsmasq | 2.89-1 | mantic  | source
 dnsmasq | 2.89-1 | noble   | source

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

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

Status in dnsmasq package in Ubuntu:
  New
Status in dnsmasq source package in Jammy:
  Triaged

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

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

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

  dnsmasq 2.86-1.1ubuntu0.3 / Ubuntu 22.04

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


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

[Touch-packages] [Bug 2048897] [NEW] [USB-Audio - Shokz Loop110, playback] Input and Duplex not listed, Output has underruns, dropouts for a few seconds then no sound

2024-01-10 Thread Marcel Brouillet

Public bug reported:

I purchased a USB dongle that presents to the system a sound device (and
hides a Bluetooth or proprietary RF connection to a headset).
https://fr.shokz.com/products/dongle

When connected, I only get to choose between two playback profiles in 
pavucontrol (see below). There is no input profile nor the Duplex that I'd 
expect.
Moreover, when I play some music, there are a few low cracks, music is barely 
recognizable for 2 seconds (if anything) and then fades out completely.
Sound is perfect with the same headset in Bluetooth mode A2DP or HFP, but I 
expected better latency with the proprietary USB dongle.

$ pactl list
Card #3
Name: alsa_card.usb-Qualcomm_Shokz_Loop110_F521F7FD67FC2D2D69C7-02
Driver: module-alsa-card.c
Owner Module: 26
Properties:
alsa.card = "2"
alsa.card_name = "Shokz Loop110"
alsa.long_card_name = "Qualcomm Shokz Loop110 at 
usb-:00:14.0-13.1, full speed"
alsa.driver_name = "snd_usb_audio"
device.bus_path = "pci-:00:14.0-usb-0:13.1:1.2"
sysfs.path = 
"/devices/pci:00/:00:14.0/usb1/1-13/1-13.1/1-13.1:1.2/sound/card2"
udev.id = "usb-Qualcomm_Shokz_Loop110_F521F7FD67FC2D2D69C7-02"
device.bus = "usb"
device.vendor.id = "0a12"
device.vendor.name = "Cambridge Silicon Radio, Ltd"
device.product.id = "4007"
device.product.name = "Shokz Loop110"
device.serial = "Qualcomm_Shokz_Loop110_F521F7FD67FC2D2D69C7"
device.string = "2"
device.description = "Shokz Loop110"
module-udev-detect.discovered = "1"
device.icon_name = "audio-card-usb"
Profiles:
output:analog-stereo: Analog Stereo Output (sinks: 1, sources: 
0, priority: 6500, available: yes)
output:iec958-stereo: Digital Stereo (IEC958) Output (sinks: 1, 
sources: 0, priority: 5500, available: yes)
off: Off (sinks: 0, sources: 0, priority: 0, available: yes)
Active Profile: output:analog-stereo
Ports:
analog-output: Analog Output (type: Analog, priority: 9900, 
latency offset: 0 usec, availability unknown)
Part of profile(s): output:analog-stereo
iec958-stereo-output: Digital Output (S/PDIF) (type: SPDIF, 
priority: 0, latency offset: 0 usec, availability unknown


$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 22.04.3 LTS
Release:22.04
Codename:   jammy


$ apt-cache policy alsa-base
alsa-base:
  Installed: 1.0.25+dfsg-0ubuntu7
  Candidate: 1.0.25+dfsg-0ubuntu7
  Version table:
 *** 1.0.25+dfsg-0ubuntu7 500
500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu jammy/main i386 Packages
100 /var/lib/dpkg/status


System is up to date (apt update ; apt upgrade)

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: alsa-base 1.0.25+dfsg-0ubuntu7
ProcVersionSignature: Ubuntu 5.15.0-91.101-lowlatency 5.15.131
Uname: Linux 5.15.0-91-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: XFCE
Date: Tue Jan  9 10:21:29 2024
InstallationDate: Installed on 2023-02-13 (329 days ago)
InstallationMedia: Ubuntu-Studio 22.04.1 LTS "Jammy Jellyfish" - Release amd64 
(20220809)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Loop110 failed
Symptom_Card: Shokz Loop110 - Shokz Loop110
Symptom_Type: Underruns, dropouts, or "crackling" sound
Title: [USB-Audio - Shokz Loop110, playback] Underruns, dropouts or crackling 
sound
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/18/2021
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX582LR.203
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX582LR
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX582LR.203:bd02/18/2021:br5.17:svnASUSTeKCOMPUTERINC.:pnZenBookProDuoUX582LR_UX582LR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX582LR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku:
dmi.product.family: ZenBook
dmi.product.name: ZenBook Pro Duo UX582LR_UX582LR
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2023-03-02T20:23:08.273376

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


** Tags: amd64 apport-bug jammy

** Attachment added: "Output of alsa-info"
   
https://bugs.launchpad.net/bugs/2048897/+attachment/5738059/+files/alsa-info.txt.1TlLlNkiPQ

--

[Touch-packages] [Bug 1833322] Re: Consider removing irqbalance from default install on desktop images

Pings done, in a perfect world (if all reply) that would cover more than
we ever need, but then there is 0% guarantee they even have time or care
about this at the moment :-)

If anyone has connections as well, please ask them to participate too.

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

Title:
  Consider removing irqbalance from default install on desktop images

Status in irqbalance package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  as per https://github.com/pop-os/default-settings/issues/60

  Distribution (run cat /etc/os-release):

  $ cat /etc/os-release
  NAME="Pop!_OS"
  VERSION="19.04"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Pop!_OS 19.04"
  VERSION_ID="19.04"
  HOME_URL="https://system76.com/pop;
  SUPPORT_URL="http://support.system76.com;
  BUG_REPORT_URL="https://github.com/pop-os/pop/issues;
  PRIVACY_POLICY_URL="https://system76.com/privacy;
  VERSION_CODENAME=disco
  UBUNTU_CODENAME=disco

  Related Application and/or Package Version (run apt policy $PACKAGE
  NAME):

  $ apt policy irqbalance
  irqbalance:
  Installed: 1.5.0-3ubuntu1
  Candidate: 1.5.0-3ubuntu1
  Version table:
  *** 1.5.0-3ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

  $ apt rdepends irqbalance
  irqbalance
  Reverse Depends:
  Recommends: ubuntu-standard
  gce-compute-image-packages

  Issue/Bug Description:

  as per konkor/cpufreq#48 and
  http://konkor.github.io/cpufreq/faq/#irqbalance-detected

  irqbalance is technically not needed on desktop systems (supposedly it
  is mainly for servers), and may actually reduce performance and power
  savings. It appears to provide benefits only to server environments
  that have relatively-constant loading. If it is truly a server-
  oriented package, then it shouldn't be installed by default on a
  desktop/laptop system and shouldn't be included in desktop OS images.

  Steps to reproduce (if you know):

  This is potentially an issue with all default installs.

  Expected behavior:

  n/a

  Other Notes:

  I can safely remove it via "sudo apt purge irqbalance" without any
  apparent adverse side-effects. If someone is running a situation where
  they need it, then they always have the option of installing it from
  the repositories.

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

2024-01-10 Thread Tim Holmes-Mitra

I've tested the proposed mesa + hwe kernel and as far as I can tell it's
working well. I believe my Z16 is navi 2nd generation and it has an iGPU
and dGPU both AMD (600M series and RX 6500 respectively). What I tested:

- firefox you tube videos (with both DRI_PRIME=0 and 1)
- steam deb running dota and quake2 (with both DRI_PRIME=0 and 1)
- desktop is hardware rendered with the iGPU and working well
- multi-monitor (2 external 4k monitors)

Let me know if there's anything else I should add or test.

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

Title:
  Backport packages for 22.04.4 HWE stack

Status in directx-headers package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in rust-bindgen package in Ubuntu:
  Invalid
Status in rust-clang-sys package in Ubuntu:
  Invalid
Status in directx-headers source package in Jammy:
  Fix Committed
Status in mesa source package in Jammy:
  Fix Committed
Status in rust-bindgen source package in Jammy:
  Invalid
Status in rust-clang-sys source package in Jammy:
  Invalid

Bug description:
  [Impact]
  The graphics HWE stack from mantic needs to be backported for 22.04.4

  directx-headers
  - build-dep of the new Mesa

  mesa
  - new major release (23.2.x)
  - new HW support, Meteor Lake..

  [Test case]
  We want to cover at least 2-3 different, widely used and already previously 
supported GPU generations from both AMD and Intel which are supported by this 
release, as those are the ones that cover most bases; nouveau users tend to 
switch to the NVIDIA blob after installation. No need to test ancient GPU's 
supported by mesa-amber. And best to focus on the newer generations (~5y and 
newer) as the older ones are less likely to break at this point.
  - AMD: Vega, Navi1x (RX5000*), Navi2x (RX6000*), Navi3x (RX7000*)
  - Intel: gen9 (SKL/APL/KBL/CFL/WHL/CML), gen11 (ICL), gen12 (TGL/RKL/RPL/DG2)

  Install the new packages and run some tests:
  - check that the desktop is still using hw acceleration and hasn't fallen 
back to swrast/llvmpipe
  - run freely available benchmarks that torture the GPU (Unigine 
Heaven/Valley/Superposition)
  - run some games from Steam if possible

  and in each case check that there is no gfx corruption happening or
  worse.

  Note that upstream releases have already been tested for OpenGL and
  Vulkan conformance by their CI.

  [Where things could go wrong]
  This is a major update of Mesa, there could be regressions but we'll try to 
catch any with testing. And since it shares bugs with mantic, we'd already know 
if there are serious issues. We will backport the final 23.2.x at a later 
stage, the first backport is needed for enabling Intel Meteor Lake.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/2037604/+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 1833322] Re: Consider removing irqbalance from default install on desktop images

I want to try to avoid that this becomes too stale, so I wondered
what we can do from here. Two things came to my mind.

On one hand I will try to use some indirect relations to pull in some
HW manufacturer experts. They often have large performance teams tracking
things like that against different workloads.

And on the other hand, due to the request seemingly to close in on
"please consider not making it the default on desktop" (server is more likely
to have these large scaling workloads that are more likely to benefit) we need
to pull in someone from Desktop a bit more.
I'll do a few direct pings for that as well to ensure to get their voice too.

Doing so now ...

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

Title:
  Consider removing irqbalance from default install on desktop images

Status in irqbalance package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  as per https://github.com/pop-os/default-settings/issues/60

  Distribution (run cat /etc/os-release):

  $ cat /etc/os-release
  NAME="Pop!_OS"
  VERSION="19.04"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Pop!_OS 19.04"
  VERSION_ID="19.04"
  HOME_URL="https://system76.com/pop;
  SUPPORT_URL="http://support.system76.com;
  BUG_REPORT_URL="https://github.com/pop-os/pop/issues;
  PRIVACY_POLICY_URL="https://system76.com/privacy;
  VERSION_CODENAME=disco
  UBUNTU_CODENAME=disco

  Related Application and/or Package Version (run apt policy $PACKAGE
  NAME):

  $ apt policy irqbalance
  irqbalance:
  Installed: 1.5.0-3ubuntu1
  Candidate: 1.5.0-3ubuntu1
  Version table:
  *** 1.5.0-3ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

  $ apt rdepends irqbalance
  irqbalance
  Reverse Depends:
  Recommends: ubuntu-standard
  gce-compute-image-packages

  Issue/Bug Description:

  as per konkor/cpufreq#48 and
  http://konkor.github.io/cpufreq/faq/#irqbalance-detected

  irqbalance is technically not needed on desktop systems (supposedly it
  is mainly for servers), and may actually reduce performance and power
  savings. It appears to provide benefits only to server environments
  that have relatively-constant loading. If it is truly a server-
  oriented package, then it shouldn't be installed by default on a
  desktop/laptop system and shouldn't be included in desktop OS images.

  Steps to reproduce (if you know):

  This is potentially an issue with all default installs.

  Expected behavior:

  n/a

  Other Notes:

  I can safely remove it via "sudo apt purge irqbalance" without any
  apparent adverse side-effects. If someone is running a situation where
  they need it, then they always have the option of installing it from
  the repositories.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1833322/+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 1833322] Re: Consider removing irqbalance from default install on desktop images

Hi Paride

> Back in the day I asked upstream their take on irqbalance usefulness with
> newer kernels, here is their reply:
> https://github.com/Irqbalance/irqbalance/issues/151

Thanks for this and the other extra pointers.
The Debian bug was referenced before, AFAIC it is mostly around
a) the kernel got smarter in many cases (true)
b) bad in virtual environments (we already removed it from those)

And in that discussion the upstream comments (it is good to see that
they are still convinced of their code) revolved around:
c) There should be no conflict with running irqbalance (with the new kernel)
d) The kernel policy is driver centric (irqbalance has a full picture)

Both - as I read them - are more arguments to keep it than to remove.
But as all other, not with enough data to make it a clear yes/no.

As I said much earlier in this case, I feel this is system and workload
dependent and hence there will never be a clear generic yes/no.
The best we can achieve is finding sets (like images used in virtual
environments - or as suggested desktop systems) and drop it being the
default there.

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

Title:
  Consider removing irqbalance from default install on desktop images

Status in irqbalance package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  as per https://github.com/pop-os/default-settings/issues/60

  Distribution (run cat /etc/os-release):

  $ cat /etc/os-release
  NAME="Pop!_OS"
  VERSION="19.04"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Pop!_OS 19.04"
  VERSION_ID="19.04"
  HOME_URL="https://system76.com/pop;
  SUPPORT_URL="http://support.system76.com;
  BUG_REPORT_URL="https://github.com/pop-os/pop/issues;
  PRIVACY_POLICY_URL="https://system76.com/privacy;
  VERSION_CODENAME=disco
  UBUNTU_CODENAME=disco

  Related Application and/or Package Version (run apt policy $PACKAGE
  NAME):

  $ apt policy irqbalance
  irqbalance:
  Installed: 1.5.0-3ubuntu1
  Candidate: 1.5.0-3ubuntu1
  Version table:
  *** 1.5.0-3ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

  $ apt rdepends irqbalance
  irqbalance
  Reverse Depends:
  Recommends: ubuntu-standard
  gce-compute-image-packages

  Issue/Bug Description:

  as per konkor/cpufreq#48 and
  http://konkor.github.io/cpufreq/faq/#irqbalance-detected

  irqbalance is technically not needed on desktop systems (supposedly it
  is mainly for servers), and may actually reduce performance and power
  savings. It appears to provide benefits only to server environments
  that have relatively-constant loading. If it is truly a server-
  oriented package, then it shouldn't be installed by default on a
  desktop/laptop system and shouldn't be included in desktop OS images.

  Steps to reproduce (if you know):

  This is potentially an issue with all default installs.

  Expected behavior:

  n/a

  Other Notes:

  I can safely remove it via "sudo apt purge irqbalance" without any
  apparent adverse side-effects. If someone is running a situation where
  they need it, then they always have the option of installing it from
  the repositories.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1833322/+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 1833322] Re: Consider removing irqbalance from default install on desktop images

Hi Dough

> If irqbalance is to be included by default, then there should be due
> diligence to demonstrate a clear benefit.

You are right that we should have that as well.
But this would be even more ture if this would be about "making it the default
when it was not before".
Right now (purely opinion) the lack of data can IMHO neither be used to keep
it nor to remove it - which sadly locks this up a bit.

> The results were:

I want to thank you a lot, this won't be enough but it is a masterpiece
demonstration of dedicating time to start providing such data.
Thank you.

I do not know the ping pong test, but on iperf, I think that is in the noise
range as far as I remember. If you'd just re-run that as-is what is the delta
on your test box?

Hoping that this will be extended by more contributing different workloads
on different systems let me ask, what kind of system (cpu, size, nodes, ...)
was that. I know you are good at writing up things, you might set the standard
how others might report to this :-)

Your results show no change or minimal degradation while at the same time losing
a bit of power. Have you also had a chance to try the powerthresh argument
that Steve mentioned above?

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

Title:
  Consider removing irqbalance from default install on desktop images

Status in irqbalance package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  as per https://github.com/pop-os/default-settings/issues/60

  Distribution (run cat /etc/os-release):

  $ cat /etc/os-release
  NAME="Pop!_OS"
  VERSION="19.04"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Pop!_OS 19.04"
  VERSION_ID="19.04"
  HOME_URL="https://system76.com/pop;
  SUPPORT_URL="http://support.system76.com;
  BUG_REPORT_URL="https://github.com/pop-os/pop/issues;
  PRIVACY_POLICY_URL="https://system76.com/privacy;
  VERSION_CODENAME=disco
  UBUNTU_CODENAME=disco

  Related Application and/or Package Version (run apt policy $PACKAGE
  NAME):

  $ apt policy irqbalance
  irqbalance:
  Installed: 1.5.0-3ubuntu1
  Candidate: 1.5.0-3ubuntu1
  Version table:
  *** 1.5.0-3ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

  $ apt rdepends irqbalance
  irqbalance
  Reverse Depends:
  Recommends: ubuntu-standard
  gce-compute-image-packages

  Issue/Bug Description:

  as per konkor/cpufreq#48 and
  http://konkor.github.io/cpufreq/faq/#irqbalance-detected

  irqbalance is technically not needed on desktop systems (supposedly it
  is mainly for servers), and may actually reduce performance and power
  savings. It appears to provide benefits only to server environments
  that have relatively-constant loading. If it is truly a server-
  oriented package, then it shouldn't be installed by default on a
  desktop/laptop system and shouldn't be included in desktop OS images.

  Steps to reproduce (if you know):

  This is potentially an issue with all default installs.

  Expected behavior:

  n/a

  Other Notes:

  I can safely remove it via "sudo apt purge irqbalance" without any
  apparent adverse side-effects. If someone is running a situation where
  they need it, then they always have the option of installing it from
  the repositories.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1833322/+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 1833322] Re: Consider removing irqbalance from default install on desktop images

Hi Mike

> SUSE ... says that the first step to get there is to disable
irqbalance

I've read the same, IMHO that is just "if you want to manually tune, disable
it" which does not imply that it is bad to have it. But this is how I read
it, I have not talked to the authors to get their underlaying reasoning.


> Applications vendors ... currently recommend removing irqbalance

The only one that does so AFAICS is cpufreq and everyone else just links
to their reasoning and follows. And even some statements there like
"If you are still running irqbalance, you are not getting the maximum
performance your system is capable of!" are hard to believe as a general
statement - especially without data across a wide variety of system types
and workload.
As we have seen as well in the references linked, irqbalance helps just as
much for "maximum performance" in many other cases.

> I found this blog (https://blogs.oracle.com/linux/post/irqbalance-
design-and-internals)

Thanks, every extra background we find will only help (except for those
joining later to read more).

> The question I have is, if Ubuntu is Debian Branch, and we long ago went
> from having different kernels for desktop & server in ubuntu-base, but do
> have ubuntu-server packages and ubuntu-desktop packages, where things could
> be different, why is this still a broad sweep as a default install "for all"?

Because there was no well-funded conclusion like "it really is bad for
environment X" to remove it. You are right that there are no technical blockers
to make it e.g. kept in servers but no more the default in Desktop.
After all it is already dropped in cloud-images used in virtual environemnts as
it had a more clear reasoning and argument there.

And there are also cases where irqbalance missing caused performance impact
and bug reports like the already mentioned [1] (clearly high scale server
though)


> I am happy that this is getting discussed properly now so that we can
> relook at this, and what it means to us today.

Ack, that is why I tried to compile all I've found into one place.


[1]: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/2038573

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

Title:
  Consider removing irqbalance from default install on desktop images

Status in irqbalance package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  as per https://github.com/pop-os/default-settings/issues/60

  Distribution (run cat /etc/os-release):

  $ cat /etc/os-release
  NAME="Pop!_OS"
  VERSION="19.04"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Pop!_OS 19.04"
  VERSION_ID="19.04"
  HOME_URL="https://system76.com/pop;
  SUPPORT_URL="http://support.system76.com;
  BUG_REPORT_URL="https://github.com/pop-os/pop/issues;
  PRIVACY_POLICY_URL="https://system76.com/privacy;
  VERSION_CODENAME=disco
  UBUNTU_CODENAME=disco

  Related Application and/or Package Version (run apt policy $PACKAGE
  NAME):

  $ apt policy irqbalance
  irqbalance:
  Installed: 1.5.0-3ubuntu1
  Candidate: 1.5.0-3ubuntu1
  Version table:
  *** 1.5.0-3ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

  $ apt rdepends irqbalance
  irqbalance
  Reverse Depends:
  Recommends: ubuntu-standard
  gce-compute-image-packages

  Issue/Bug Description:

  as per konkor/cpufreq#48 and
  http://konkor.github.io/cpufreq/faq/#irqbalance-detected

  irqbalance is technically not needed on desktop systems (supposedly it
  is mainly for servers), and may actually reduce performance and power
  savings. It appears to provide benefits only to server environments
  that have relatively-constant loading. If it is truly a server-
  oriented package, then it shouldn't be installed by default on a
  desktop/laptop system and shouldn't be included in desktop OS images.

  Steps to reproduce (if you know):

  This is potentially an issue with all default installs.

  Expected behavior:

  n/a

  Other Notes:

  I can safely remove it via "sudo apt purge irqbalance" without any
  apparent adverse side-effects. If someone is running a situation where
  they need it, then they always have the option of installing it from
  the repositories.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1833322/+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 1833322] Re: Consider removing irqbalance from default install on desktop images

Hi Ethanay
> All I can find is a recommendation not to use it on CPUs with 2 or fewer
> cores as the overhead is said to be too high

This isn't a real problem anyway, the service will stop immediately if only
running on one core - even if running on multiple cores with the same
cache (as the intended benefit is due to cache hotness by having all I/O
hitting the same cache).

> I can imagine it might still add undesirable or even critical latency in
> applications that are highly latency sensitive

I understand your line of thought, but it might even improve latency.
If there is no bottleneck on the cores assigned to handle an IRQ then
the improved cache hit rate will make even latency better.
And if there is a strong bottleneck, then some drivers without IRQbalance
would end up locked on one cpu - so again these might gain lower latency.
But I have no data on this either (just like no one seems to have on almost
any of this).

Just like others I'd personally more expect the drawback to be on a potential
lack of power saving.

> This website gave me some clarity on the theory and purpose:
> https://www.baeldung.com/linux/irqbalance-modern-hardware

Hah, didn't find this one yet - thank you!
But to me it only underlines the "it can help as much or even more often"
expectation.

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

Title:
  Consider removing irqbalance from default install on desktop images

Status in irqbalance package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  as per https://github.com/pop-os/default-settings/issues/60

  Distribution (run cat /etc/os-release):

  $ cat /etc/os-release
  NAME="Pop!_OS"
  VERSION="19.04"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Pop!_OS 19.04"
  VERSION_ID="19.04"
  HOME_URL="https://system76.com/pop;
  SUPPORT_URL="http://support.system76.com;
  BUG_REPORT_URL="https://github.com/pop-os/pop/issues;
  PRIVACY_POLICY_URL="https://system76.com/privacy;
  VERSION_CODENAME=disco
  UBUNTU_CODENAME=disco

  Related Application and/or Package Version (run apt policy $PACKAGE
  NAME):

  $ apt policy irqbalance
  irqbalance:
  Installed: 1.5.0-3ubuntu1
  Candidate: 1.5.0-3ubuntu1
  Version table:
  *** 1.5.0-3ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

  $ apt rdepends irqbalance
  irqbalance
  Reverse Depends:
  Recommends: ubuntu-standard
  gce-compute-image-packages

  Issue/Bug Description:

  as per konkor/cpufreq#48 and
  http://konkor.github.io/cpufreq/faq/#irqbalance-detected

  irqbalance is technically not needed on desktop systems (supposedly it
  is mainly for servers), and may actually reduce performance and power
  savings. It appears to provide benefits only to server environments
  that have relatively-constant loading. If it is truly a server-
  oriented package, then it shouldn't be installed by default on a
  desktop/laptop system and shouldn't be included in desktop OS images.

  Steps to reproduce (if you know):

  This is potentially an issue with all default installs.

  Expected behavior:

  n/a

  Other Notes:

  I can safely remove it via "sudo apt purge irqbalance" without any
  apparent adverse side-effects. If someone is running a situation where
  they need it, then they always have the option of installing it from
  the repositories.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1833322/+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 1833322] Re: Consider removing irqbalance from default install on desktop images

Hi Steve,

> I see a lot of strong opinions ... I would want any decision to remove
> irqbalance from the desktop to be based on evidence, not conjecture.

I agree that there is plenty of opinion (often backing up each other with cyclic
links) and not much data. Hence my compilation of the history to make it
somehwat consumable.

I wasn't entirely sure on my own but I agree that we'd need data to back
up changes, thanks for empowering that branch of the decision tree.

Yet on the other hand, that most likely means not much will move quickly.
Which is fine, but also makes it unlikely to conclude before Noble freezes.

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

Title:
  Consider removing irqbalance from default install on desktop images

Status in irqbalance package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  as per https://github.com/pop-os/default-settings/issues/60

  Distribution (run cat /etc/os-release):

  $ cat /etc/os-release
  NAME="Pop!_OS"
  VERSION="19.04"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Pop!_OS 19.04"
  VERSION_ID="19.04"
  HOME_URL="https://system76.com/pop;
  SUPPORT_URL="http://support.system76.com;
  BUG_REPORT_URL="https://github.com/pop-os/pop/issues;
  PRIVACY_POLICY_URL="https://system76.com/privacy;
  VERSION_CODENAME=disco
  UBUNTU_CODENAME=disco

  Related Application and/or Package Version (run apt policy $PACKAGE
  NAME):

  $ apt policy irqbalance
  irqbalance:
  Installed: 1.5.0-3ubuntu1
  Candidate: 1.5.0-3ubuntu1
  Version table:
  *** 1.5.0-3ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

  $ apt rdepends irqbalance
  irqbalance
  Reverse Depends:
  Recommends: ubuntu-standard
  gce-compute-image-packages

  Issue/Bug Description:

  as per konkor/cpufreq#48 and
  http://konkor.github.io/cpufreq/faq/#irqbalance-detected

  irqbalance is technically not needed on desktop systems (supposedly it
  is mainly for servers), and may actually reduce performance and power
  savings. It appears to provide benefits only to server environments
  that have relatively-constant loading. If it is truly a server-
  oriented package, then it shouldn't be installed by default on a
  desktop/laptop system and shouldn't be included in desktop OS images.

  Steps to reproduce (if you know):

  This is potentially an issue with all default installs.

  Expected behavior:

  n/a

  Other Notes:

  I can safely remove it via "sudo apt purge irqbalance" without any
  apparent adverse side-effects. If someone is running a situation where
  they need it, then they always have the option of installing it from
  the repositories.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1833322/+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 2045570] Re: dnsmasq crash when no servers in resolv.conf

Uploaded to jammy unapproved, waiting on SRU team now.

** Merge proposal linked:
   
https://code.launchpad.net/~ahasenack/ubuntu/+source/dnsmasq/+git/dnsmasq/+merge/457905

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

Title:
  dnsmasq crash when no servers in resolv.conf

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

Bug description:
  [ Impact ]

  dnsmasq "keeps an eye" on /etc/resolv.conf, and reloads it whenever
  the file is updated. When that happens and for some reason there were
  no "nameserver" declarations in the updated file, dnsmasq can crash.

  Here is a log of a reproducer:
  $ dig +short @127.0.0.1 ubuntu.com
  ;; communications error to 127.0.0.1#53: timed out
  ;; communications error to 127.0.0.1#53: connection refused
  ;; communications error to 127.0.0.1#53: connection refused
  ;; no servers could be reached

  We can see the startup, then when resolv.conf is read again and no 
nameservers were found, and the crash:
  Jan 03 13:57:13 j-dnsmasq-2045570 dnsmasq[1507]: started, version 2.86 
cachesize 150
  Jan 03 13:57:13 j-dnsmasq-2045570 dnsmasq[1507]: DNS service limited to local 
subnets
  Jan 03 13:57:13 j-dnsmasq-2045570 dnsmasq[1507]: compile time options: IPv6 
GNU-getopt DBus no-UBus i18n IDN2 DHCP DHCPv6 no-Lua TFTP conntrack ipset auth 
cryptohash DNSSEC loop-detect inotify dumpfile
  Jan 03 13:57:13 j-dnsmasq-2045570 dnsmasq[1507]: reading /etc/resolv.conf
  Jan 03 13:57:13 j-dnsmasq-2045570 dnsmasq[1507]: using nameserver 
10.0.100.1#53
  Jan 03 13:57:13 j-dnsmasq-2045570 dnsmasq[1507]: read /etc/hosts - 7 addresses
  Jan 03 13:57:13 j-dnsmasq-2045570 systemd[1]: Started dnsmasq - A lightweight 
DHCP and caching DNS server.
  Jan 03 13:58:01 j-dnsmasq-2045570 dnsmasq[1507]: no servers found in 
/etc/resolv.conf, will retry
  Jan 03 13:58:22 j-dnsmasq-2045570 systemd[1]: dnsmasq.service: Main process 
exited, code=dumped, status=11/SEGV
  Jan 03 13:58:22 j-dnsmasq-2045570 systemd[1]: dnsmasq.service: Failed with 
result 'core-dump'.

  dnsmasq has provisions for this situation, we can see that in the
  13:58:01 message where it says it will retry, but due to this bug, it
  crashes instead.

  The problem was introduced[1] in version 2.86, and fixed in 2.87, so
  only jammy is affected.

  1. 
https://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=patch;h=d290630d31f4517ab26392d00753d1397f9a4114;hp=d2ad5dc073aaacaf22b117f16106282a73586803
  The commit message says:
  """
  This problem was introduced in 2.86.
  """

  And indeed, I wasn't able to crash 2.80 shipped in focal.

  [ Test Plan ]
  It might take a few tries to reproduce the bug, but here is the general 
outline. Also keep in mind that it's important to use a DNS name that isn't 
cached already by a previous query.

  # Create a jammy lxd container

  lxc launch ubuntu-daily:jammy j-dnsmasq-2045570

  # Enter the container

  lxc shell j-dnsmasq-2045570

  # From now on, all commands should be executed in the container.
  # Install dnsmasq, and disable systemd-resolved

  apt update && apt install -y dnsmasq

  # Disable systemd-resolved, and start dnsmasq

  systemctl disable --now systemd-resolved
  systemctl enable --now dnsmasq

  # In one terminal inside the container, watch the dnsmasq logs:

  journalctl -u dnsmasq.service -f

  # In another terminal, remove /etc/resolv.conf and create a new one, empty
  rm /etc/resolv.conf
  echo "nameserver 1.1.1.1" > /etc/resolv.conf

  # restart dnsmasq
  systemctl restart dnsmasq.service

  # Perform a dns query

  dig @127.0.0.1 +short linux.com

  # Comment the namserver directive in resolv.conf
  echo "#nameserver 1.1.1.1" > /etc/resolv.conf

  # Observe in the dnsmasq logs that it notices the change with a
  message like:

  Jan 03 14:14:51 j-dnsmasq-2045570 dnsmasq[2274]: no servers found in
  /etc/resolv.conf, will retry

  # Perform a *different* DNS query

  dig @127.0.0.1 +short ubuntu.com

  # Observe in the dnsmasq logs that it crashes.
  Jan 03 13:58:22 j-dnsmasq-2045570 systemd[1]: dnsmasq.service: Main process 
exited, code=dumped, status=11/SEGV
  Jan 03 13:58:22 j-dnsmasq-2045570 systemd[1]: dnsmasq.service: Failed with 
result 'core-dump'.

  If it doesn't crash right away, repeat these steps a few times, but using a 
different domain name each time:
  - add "nameserver 127.0.0.1" to /etc/resolv.conf
  - observe that dnsmasq notices the change to the file
  - perform a query for some random domain using "dig @127.0.0.1 +short 
"
  - remove "nameserver" from /etc/resolv.conf, observe that dnsmasq noticed the 
change
  - perform a query for another random domain

  The fixed version from proposed will not crash. That last query with
  no "nameserver" lines in resolv.conf won't work, but it won't crash
  the server.

  [ Where problems could occur ]

  This is

[Touch-packages] [Bug 1833322] Re: Consider removing irqbalance from default install on desktop images

2024-01-10 Thread Paride Legovini

Hi, adding a couple of extra pointers here (I'm the Debian irqbalance
maintainer). This the Debian bug where the discussion on removing
irqbalance from the kernel Recommends happened:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926967

In Debian irqbalance is not installed anymore by default since mid-2019
(clearly reflected by popcon: https://qa.debian.org/popcon-
graph.php?packages=irqbalance), and no bug was reported related to it
being missing.

Back in the day I asked upstream their take on irqbalance usefulness
with newer kernels, here is their reply:

https://github.com/Irqbalance/irqbalance/issues/151

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

** Bug watch added: github.com/Irqbalance/irqbalance/issues #151
   https://github.com/Irqbalance/irqbalance/issues/151

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

Title:
  Consider removing irqbalance from default install on desktop images

Status in irqbalance package in Ubuntu:
  Confirmed
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  as per https://github.com/pop-os/default-settings/issues/60

  Distribution (run cat /etc/os-release):

  $ cat /etc/os-release
  NAME="Pop!_OS"
  VERSION="19.04"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Pop!_OS 19.04"
  VERSION_ID="19.04"
  HOME_URL="https://system76.com/pop;
  SUPPORT_URL="http://support.system76.com;
  BUG_REPORT_URL="https://github.com/pop-os/pop/issues;
  PRIVACY_POLICY_URL="https://system76.com/privacy;
  VERSION_CODENAME=disco
  UBUNTU_CODENAME=disco

  Related Application and/or Package Version (run apt policy $PACKAGE
  NAME):

  $ apt policy irqbalance
  irqbalance:
  Installed: 1.5.0-3ubuntu1
  Candidate: 1.5.0-3ubuntu1
  Version table:
  *** 1.5.0-3ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

  $ apt rdepends irqbalance
  irqbalance
  Reverse Depends:
  Recommends: ubuntu-standard
  gce-compute-image-packages

  Issue/Bug Description:

  as per konkor/cpufreq#48 and
  http://konkor.github.io/cpufreq/faq/#irqbalance-detected

  irqbalance is technically not needed on desktop systems (supposedly it
  is mainly for servers), and may actually reduce performance and power
  savings. It appears to provide benefits only to server environments
  that have relatively-constant loading. If it is truly a server-
  oriented package, then it shouldn't be installed by default on a
  desktop/laptop system and shouldn't be included in desktop OS images.

  Steps to reproduce (if you know):

  This is potentially an issue with all default installs.

  Expected behavior:

  n/a

  Other Notes:

  I can safely remove it via "sudo apt purge irqbalance" without any
  apparent adverse side-effects. If someone is running a situation where
  they need it, then they always have the option of installing it from
  the repositories.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1833322/+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 406397] Re: init: job stuck with expect fork/daemon when parent reaps child

2024-01-10 Thread Paride Legovini

** Changed in: pld-linux
   Status: New => Incomplete

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

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

Title:
  init: job stuck with expect fork/daemon when parent reaps child

Status in upstart :
  Triaged
Status in irqbalance package in Ubuntu:
  Invalid
Status in upstart package in Ubuntu:
  Invalid
Status in upstart package in Debian:
  Fix Released
Status in PLD Linux:
  Incomplete

Bug description:
  Hi

  Wrong use of the expect fork stanza can create job with status
job stop/killled, process nnn
  without any process nnn running on the system.

  As an example the following avahi.conf should have used
  "expect daemon", but will instead create a stuck job.

  stop on stopping dbus-system
  respawn
  expect fork
  exec avahi-daemon -D

  /Emil Renner Berthing

To manage notifications about this bug go to:
https://bugs.launchpad.net/upstart/+bug/406397/+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 2045931] Re: ps3 sixasis controller request pin to connect to bt

** Description changed:

+ [ Workaround ]
+ 
+ 1. Set ClassicBondedOnly=false in /etc/bluetooth/input.conf
+ 2. Run: systemctl restart bluetooth # or reboot
+ 
+ [ Original Description ]
+ 
  Once my Ubuntu updated bluez package to 5.64-0ubuntu1.1 I was not able
  to connect my PS3 Sixasis controller via bluetooth. It is aking to enter
  a PIN in the device (not possible to enter a pin in the gamepad).
  
  Source pacakge (from "apt list -a bluez"):
  
  bluez/jammy-updates,jammy-security 5.64-0ubuntu1.1 amd64
  
  Once downgraded to 5.64-0ubuntu1 version, gamepad connects OK again
  without asking for a connection PIN.
  
  Ubuntu release:
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04
  
  Package version:
  bluez:
-   Installed: 5.64-0ubuntu1.1
+   Installed: 5.64-0ubuntu1.1
  
  Expected to happen:
  Connect PS3 Controller by Bluetooth without asking for a PIN code
  
  Happened instead:
  PS3 Controller cannot connect because PIN code is requested

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

Title:
  ps3 sixasis controller request pin to connect to bt

Status in bluez package in Ubuntu:
  Won't Fix

Bug description:
  [ Workaround ]

  1. Set ClassicBondedOnly=false in /etc/bluetooth/input.conf
  2. Run: systemctl restart bluetooth # or reboot

  [ Original Description ]

  Once my Ubuntu updated bluez package to 5.64-0ubuntu1.1 I was not able
  to connect my PS3 Sixasis controller via bluetooth. It is aking to
  enter a PIN in the device (not possible to enter a pin in the
  gamepad).

  Source pacakge (from "apt list -a bluez"):

  bluez/jammy-updates,jammy-security 5.64-0ubuntu1.1 amd64

  Once downgraded to 5.64-0ubuntu1 version, gamepad connects OK again
  without asking for a connection PIN.

  Ubuntu release:
  Description:  Ubuntu 22.04.3 LTS
  Release:  22.04

  Package version:
  bluez:
    Installed: 5.64-0ubuntu1.1

  Expected to happen:
  Connect PS3 Controller by Bluetooth without asking for a PIN code

  Happened instead:
  PS3 Controller cannot connect because PIN code is requested

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/2045931/+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 1375640] Re: fsck should do some sanity checks to avoid damaging an ext3/ext4 file system

2024-01-10 Thread Michael Mess

Thank you for you recommendations. 
I was able to restore some of the data which has been lost.

The nvidia graphics card was causing all the trouble, after a replacement with 
intel graphics, I have never experienced any issues again.
It is likely that the closed source driver caused also other issues which 
didn't always lead to crashes, but to an unreliable system where things got 
corrupted silently.

But this is sure not an issue in tools (like fsck) which produce much
i/o load and thus have a greater probability to get hit by the buggy
nvidia driver, thus I can close the issue.

Since then I have always avoided buying equipment from firms which do
not provide open source drivers, and I have never experienced any issues
with data corruption any more.

So I call out to the world: If you are a hardware manufacturer and want
me to buy your product: Provide good open source drivers!

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

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

Title:
  fsck should do some sanity checks to avoid damaging an ext3/ext4 file
  system

Status in e2fsprogs package in Ubuntu:
  Invalid

Bug description:
  After some crashes due to a broken nvidia driver, the system didn't boot and 
presented me a shell to manually repair the file system.
  Then I didn't think and typed fsck without the -t ext4 parameter and the 
program asked me many questions, if I want to fix something which I answered 
with y.
  After some time I remembered, that I forgot to specify the -t ext4 parameter, 
but the filesystem was broken already, so it was already too late, when I do 
Ctrl-C.
  And I didn't think about that there could be already severe file system 
corruption, making the things even worse.

  Thus I would recommend that a warning message is displayed, when calling fsck 
manually with the wrong filesystem type.
  Also a big note that this is now the right time to make an image backup of 
the disk could be helpful for people like me that always tell other people how 
important backups are before working on something, but sometimes fail to make 
one, because they forget to turn their brain on before starting work. ;-)

  I would expect that when calling fsck on a filesystem, not just defaults are 
used, but the filesystem type is determined.
  Then a big scary warning message should say something like this:

  "
  You have called fsck on an ext4 filesystem. 
  For an ext4 file system you *must* specify the filesystem type with option 
"-t ext4", otherwise severe damage to the file system will occur.
  NOTE: It is highly recommended that you make a backup image of your disk 
device before you continue, so that you have something to recover from, if 
things go wrong. 
  This can be especially important, if the disk drive hardware you are trying 
to recover the filesystem on, is possibly dying.
  You can use dd_rescue or similar tools to try to get a disk image to recover 
as much as possible of your data from a damaged hard drive.

  Are you really sure, you want to continue (and probably damage the file 
system)? (yes/NO)
  "

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/e2fsprogs/+bug/1375640/+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 2045886] Re: Please merge 8.5.0-2 into noble

2024-01-10 Thread Launchpad Bug Tracker

This bug was fixed in the package curl - 8.5.0-2ubuntu1

---
curl (8.5.0-2ubuntu1) noble; urgency=medium

  * Merge with Debian unstable (LP: #2045886). Remaining changes:
- debian/control: Don't build-depend on python3-impacket on i386
  so we can drop it (and its dependencies) from the i386 partial port.
  It's only used for the tests, which do not block the build in any case.

curl (8.5.0-2) unstable; urgency=medium

  * d/p/openldap_fix_an_LDAP_crash.patch: New patch to fix ldap segfault
(closes: #1057855)

curl (8.5.0-1) unstable; urgency=medium

  [ Samuel Henrique ]
  * New upstream version 8.5.0
- Fix CVE-2023-46218: cookie mixed case PSL bypass (closes: #1057646)
- Fix CVE-2023-46219: HSTS long file name clears contents (closes: #1057645)
  * d/rules: Use pkg-info.mk instead of dpkg-parsechangelog for DEB_VERSION
  * d/p/90_gnutls.patch: Update patch
  * d/p/dist_add_tests_errorcodes_pl_to_the_tarball.patch: Upstream patch to
fix tests
  * d/p/add_errorcodes_upstream_file.patch: Include missing file from upstream
tarball

  [ Carlos Henrique Lima Melara ]
  * d/control: change Maintainer field to curl packaging team
  * d/README.Debian: add readme to explain curl's team creation
  * d/control: add myself to Uploaders

 -- Danilo Egea Gondolfo   Tue, 02
Jan 2024 09:32:27 +

** Changed in: curl (Ubuntu)
   Status: New => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-46218

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-46219

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

Title:
  Please merge 8.5.0-2 into noble

Status in curl package in Ubuntu:
  Fix Released

Bug description:
  tracking bug

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curl/+bug/2045886/+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 2034672] Re: gnome-shell crashed with GLXBadDrawable on startup in a Xorg session

** Changed in: mesa (Ubuntu)
   Status: Fix Committed => Fix Released

** Tags removed: fixed-in-mesa-23.3
** Tags added: fixed-in-mesa-23.3.0

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

Title:
  gnome-shell crashed with GLXBadDrawable on startup in a Xorg session

Status in Mutter:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  Mantic 20230907 on Latitude 3320

  Crash on boot of the live session

  ProblemType: Crash
  DistroRelease: Ubuntu 23.10
  Package: gnome-shell 45~rc-0ubuntu1
  ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5
  Uname: Linux 6.3.0-7-generic x86_64
  NonfreeKernelModules: zfs
  ApportVersion: 2.27.0-0ubuntu2
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CasperVersion: 1.482
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Sep  7 08:02:08 2023
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  ExecutableTimestamp: 1694028853
  LiveMediaBuild: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230907)
  ProcCmdline: /usr/bin/gnome-shell
  ProcCwd: /home/ubuntu
  ProcEnviron:
   LANG=C.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  RelatedPackageVersions: mutter-common 45~rc-0ubuntu1
  Signal: 5
  SourcePackage: gnome-shell
  StacktraceTop:
   g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log_default_handler () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_logv () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_log () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/mutter-13/libmutter-mtk-13.so.0
  Title: gnome-shell crashed with signal 5 in g_log_structured_array()
  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/mutter/+bug/2034672/+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 2048845] Re: Kubuntu Ubuntu-bug reporting snap apps doesnt show clickable bug reporting link

firefox bug before snap refresh
In lubuntu terminal even link is clickable if ctrl+click

** Attachment added: "snap bug lubuntu live cd firefox.png"
   
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2048845/+attachment/5737971/+files/snap%20bug%20lubuntu%20live%20cd%20firefox.png

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

Title:
  Kubuntu Ubuntu-bug reporting snap apps doesnt show clickable bug
  reporting link

Status in apport package in Ubuntu:
  New

Bug description:
  Kubuntu Ubuntu-bug reporting snap apps doesnt show clickable bug
  reporting link

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apport 2.20.11-0ubuntu82.5
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-39-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Wed Jan 10 09:59:21 2024
  InstallationDate: Installed on 2024-01-05 (5 days ago)
  InstallationMedia: Kubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.1)
  PackageArchitecture: all
  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/2048845/+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 2048845] Re: Kubuntu Ubuntu-bug reporting snap apps doesnt show clickable bug reporting link

snap ubuntu bug lubuntu

** Attachment added: "ubuntu bug lubuntu terminal.png"
   
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2048845/+attachment/5737970/+files/ubuntu%20bug%20lubuntu%20terminal.png

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

Title:
  Kubuntu Ubuntu-bug reporting snap apps doesnt show clickable bug
  reporting link

Status in apport package in Ubuntu:
  New

Bug description:
  Kubuntu Ubuntu-bug reporting snap apps doesnt show clickable bug
  reporting link

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apport 2.20.11-0ubuntu82.5
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-39-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Wed Jan 10 09:59:21 2024
  InstallationDate: Installed on 2024-01-05 (5 days ago)
  InstallationMedia: Kubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.1)
  PackageArchitecture: all
  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/2048845/+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 2048845] Re: Kubuntu Ubuntu-bug reporting snap apps doesnt show clickable bug reporting link

Kubuntu doesn show clickable link

** Attachment added: "snap bug kubuntu not clickable.png"
   
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2048845/+attachment/5737968/+files/snap%20bug%20kubuntu%20not%20clickable.png

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

Title:
  Kubuntu Ubuntu-bug reporting snap apps doesnt show clickable bug
  reporting link

Status in apport package in Ubuntu:
  New

Bug description:
  Kubuntu Ubuntu-bug reporting snap apps doesnt show clickable bug
  reporting link

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apport 2.20.11-0ubuntu82.5
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-39-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Wed Jan 10 09:59:21 2024
  InstallationDate: Installed on 2024-01-05 (5 days ago)
  InstallationMedia: Kubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.1)
  PackageArchitecture: all
  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/2048845/+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 2048845] Re: Kubuntu Ubuntu-bug reporting snap apps doesnt show clickable bug reporting link

Snap choose bug ubuntu

** Attachment added: "snap bug.png"
   
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2048845/+attachment/5737965/+files/snap%20bug.png

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

Title:
  Kubuntu Ubuntu-bug reporting snap apps doesnt show clickable bug
  reporting link

Status in apport package in Ubuntu:
  New

Bug description:
  Kubuntu Ubuntu-bug reporting snap apps doesnt show clickable bug
  reporting link

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apport 2.20.11-0ubuntu82.5
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-39-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Wed Jan 10 09:59:21 2024
  InstallationDate: Installed on 2024-01-05 (5 days ago)
  InstallationMedia: Kubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.1)
  PackageArchitecture: all
  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/2048845/+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 2048845] Re: Kubuntu Ubuntu-bug reporting snap apps doesnt show clickable bug reporting link

Ubuntu link clickable

** Attachment added: "snap bug-clickable.png"
   
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/2048845/+attachment/5737966/+files/snap%20bug-clickable.png

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

Title:
  Kubuntu Ubuntu-bug reporting snap apps doesnt show clickable bug
  reporting link

Status in apport package in Ubuntu:
  New

Bug description:
  Kubuntu Ubuntu-bug reporting snap apps doesnt show clickable bug
  reporting link

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: apport 2.20.11-0ubuntu82.5
  ProcVersionSignature: Ubuntu 6.2.0-39.40~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-39-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: KDE
  Date: Wed Jan 10 09:59:21 2024
  InstallationDate: Installed on 2024-01-05 (5 days ago)
  InstallationMedia: Kubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.1)
  PackageArchitecture: all
  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/2048845/+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 2048845] [NEW] Kubuntu Ubuntu-bug reporting snap apps doesnt show clickable bug reporting link