[Bug 1950692] Re: Ubuntu advantage tools should be removable without breakage of the core system functionality

2022-06-03 Thread Steve Langasek
This bug was already closed 'opinion' once by the developers but has
been reopened by the submitter.  The developers asked that discussion
about this decision be taken to the mailing list.

A release cycle and change later, this continues to come up in
discussions, but the submitter of this bug has not participated on the
mailing list thread to offer any arguments; so the Server Team has asked
me to comment.

I have also posted my comment to the mailing list at
https://lists.ubuntu.com/archives/ubuntu-devel/2022-June/042115.html but
am copying it here for the record.

The ubuntu-minimal metapackage defines the minimal experience that we
consider to be "Ubuntu".  It is possible to remove this metapackage from
the system, from a packaging system / policy perspective this is
permitted. However, by doing so, you are making the system "not Ubuntu"
and you will not receive support for such a system from the Ubuntu
community.

We have always taken an opinionated view on what defines the minimal "Ubuntu".  
For instance: at one point in the past, upstart was our supported init system, 
but there were other init system packages in the archive.  It was possible to 
install these - but only by removing the ubuntu-minimal package.  Requests to 
relax the dependency in order to allow other init
systems as an alternative were rejected, because that was not the defined 
Ubuntu experience.

We should always be willing to reconsider the contents of our minimal install 
based on technical considerations.  To date, however, the objections I've seen 
to ubuntu-advantage-tools being a required minimal package have not been 
technical, but rather questions of taste: specifically, some people appear to 
find it distasteful that a paid service from Canonical is being
advertised without the ability to opt out.

Firstly, users are always entitled to their opinion when it comes to
questions of taste; but the Ubuntu developers are not obligated to
accomodate differences of taste when it comes to the Ubuntu experience.

But secondly, as I've commented before, the purpose of ubuntu-advantage-tools 
inclusion in ubuntu-minimal isn't to advertise
commercial services; it's to ensure users are informed regarding the security 
status of their systems, and to provide a clean user experience for enabling 
the ESM service - which in some contexts is a paid service, in some contexts 
not - to provide the best possible security for those systems.

There are two other issues that have come up in discussion around
ubuntu-advantage-tools.  Neither requires making the package removable
in order to address, and ensuring they are addressed in the package
itself improves the Ubuntu experience for all users, not just those that
choose to remove this package.

 - https://bugs.launchpad.net/bugs/1956115 objects about not being able
to opt out of the MOTD messages.  This bug report however is marked
incomplete, as the behavior described does not appear to correspond to
the default behavior in Ubuntu Desktop or Server.  If there are problems
being unable to opt out, we certainly want to address those.

 - ubuntu-advantage-tools is now a bit larger than it was originally,
weighing in at around 2.8MB.  We should always be mindful of managing
the size of a minimal Ubuntu install; however I have not actually seen
anyone say that they were trying to remove ubuntu-advantage-tools from
their system because of the disk space used.  In any case, the team is
looking at bringing the size of this package back down to under 1MB.

In conclusion, in the absence of any other arguments being advanced,
ubuntu-advantage-tools will remain a dependency of ubuntu-minimal at
this time.  This is always subject to revision in light of new technical
arguments that might be put forward, but explains the current state of
affairs for the released Ubuntu 22.04 LTS.


** Changed in: ubuntu-advantage-tools (Ubuntu)
   Status: Confirmed => Opinion

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1950692

Title:
  Ubuntu advantage tools should be removable without breakage of the
  core system functionality

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1950692/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1971767] Re: [MIR] libfreeaptx

2022-06-03 Thread Steve Langasek
Override component to main
libfreeaptx 0.1.1-2 in kinetic: universe/misc -> main
freeaptx-utils 0.1.1-2 in kinetic amd64: universe/utils/optional/100% -> main
freeaptx-utils 0.1.1-2 in kinetic arm64: universe/utils/optional/100% -> main
freeaptx-utils 0.1.1-2 in kinetic armhf: universe/utils/optional/100% -> main
freeaptx-utils 0.1.1-2 in kinetic i386: universe/utils/optional/100% -> main
freeaptx-utils 0.1.1-2 in kinetic ppc64el: universe/utils/optional/100% -> main
freeaptx-utils 0.1.1-2 in kinetic riscv64: universe/utils/optional/100% -> main
freeaptx-utils 0.1.1-2 in kinetic s390x: universe/utils/optional/100% -> main
libfreeaptx-dev 0.1.1-2 in kinetic amd64: universe/libdevel/optional/100% -> 
main
libfreeaptx-dev 0.1.1-2 in kinetic arm64: universe/libdevel/optional/100% -> 
main
libfreeaptx-dev 0.1.1-2 in kinetic armhf: universe/libdevel/optional/100% -> 
main
libfreeaptx-dev 0.1.1-2 in kinetic i386: universe/libdevel/optional/100% -> main
libfreeaptx-dev 0.1.1-2 in kinetic ppc64el: universe/libdevel/optional/100% -> 
main
libfreeaptx-dev 0.1.1-2 in kinetic riscv64: universe/libdevel/optional/100% -> 
main
libfreeaptx-dev 0.1.1-2 in kinetic s390x: universe/libdevel/optional/100% -> 
main
libfreeaptx0 0.1.1-2 in kinetic amd64: universe/libs/optional/100% -> main
libfreeaptx0 0.1.1-2 in kinetic arm64: universe/libs/optional/100% -> main
libfreeaptx0 0.1.1-2 in kinetic armhf: universe/libs/optional/100% -> main
libfreeaptx0 0.1.1-2 in kinetic i386: universe/libs/optional/100% -> main
libfreeaptx0 0.1.1-2 in kinetic ppc64el: universe/libs/optional/100% -> main
libfreeaptx0 0.1.1-2 in kinetic riscv64: universe/libs/optional/100% -> main
libfreeaptx0 0.1.1-2 in kinetic s390x: universe/libs/optional/100% -> main
22 publications overridden.


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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971767

Title:
  [MIR] libfreeaptx

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1977493] Re: Upgrade from Ubuntu 21.10 to 22.04 fails - unmet dependencies: libpam-modules

2022-06-03 Thread Steve Langasek
I'm going to mark this triaged for ubuntu-release-upgrader.  It's
important to have guards in preinst scripts against breaking a system as
part of an upgrade, but we also want to avoid actually hitting these
failures in the middle of a release upgrade precisely because it's so
difficult to get the system back into a coherent state afterwards.
Where we know such preinst checks exist (especially for such critical
packages as pam), it's best to have do-release-upgrader detect early and
block the upgrade.

** Changed in: ubuntu-release-upgrader (Ubuntu)
   Importance: Undecided => High

** Changed in: ubuntu-release-upgrader (Ubuntu)
   Status: Incomplete => Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1977493

Title:
  Upgrade from Ubuntu 21.10 to 22.04 fails - unmet dependencies: libpam-
  modules

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1977493/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1977493] Re: Upgrade from Ubuntu 21.10 to 22.04 fails - unmet dependencies: libpam-modules

2022-06-03 Thread Steve Langasek
On Fri, Jun 03, 2022 at 03:58:24PM -, Frank Heimes wrote:

> Fwiw - I just took the system that I used for the description above and
> did a 'do-release-upgrade' and it work fine

Yes, this problem only occurs because the submitter has references to the
obsolete pam_tally module in their config and PAM blocks the upgrade to
prevent the user from having a broken config after upgrade (and potentially
be locked out of administering the system to fix it).  It will not happen on
a system with a stock config.

It is unfortunately not safe for us to automatically edit the configs to
remove references to pam_tally on upgrade, as this may also result in an
admin lock-out.


** Tags added: rls-jj-incoming

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1977493

Title:
  Upgrade from Ubuntu 21.10 to 22.04 fails - unmet dependencies: libpam-
  modules

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1977493/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1977493] Re: Upgrade from Ubuntu 21.10 to 22.04 fails - unmet dependencies: libpam-modules

2022-06-03 Thread Steve Langasek
If there's any bug in Ubuntu here, it's that the release upgrader didn't
try harder to get the system into a consistent state before offering a
reboot.  No bug in pam, which is simply one of the packages to be
upgraded.

libpam-modules refused to be upgraded because there were references to
obsolete modules in the system config and one or more services would be
broken after upgrade.  At the per package level there really isn't a
better way to handle this.

** Package changed: pam (Ubuntu) => ubuntu-release-upgrader (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1977493

Title:
  Upgrade from Ubuntu 21.10 to 22.04 fails - unmet dependencies: libpam-
  modules

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1977493/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1971128] Re: z3 is incorrectly marked as a MIR candidate

2022-05-31 Thread Steve Langasek
I see no references to llvm-13-dev from rustc in jammy, and this has
been resolved in kinetic by relaxing the package relationship, so
closing this task.

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971128

Title:
  z3 is incorrectly marked as a MIR candidate

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1827442] Re: [MIR] libheif

2022-05-23 Thread Steve Langasek
imagemagick is no longer in main, so this is wontfix.

** Changed in: libde265 (Ubuntu)
   Status: Incomplete => Won't Fix

** Changed in: libheif (Ubuntu)
   Status: In Progress => Won't Fix

** Changed in: x265 (Ubuntu)
   Status: Incomplete => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827442

Title:
  [MIR] libheif

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1971650] Re: wrong check for "server" in libssl3.postinst

2022-05-23 Thread Steve Langasek
Certainly if Debian is dropping the per-package code in favor of
needrestart we should head in the same direction, but we need to sort
out getting needrestart included in the desktop-common seed first.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971650

Title:
  wrong check for "server" in libssl3.postinst

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1915878] Re: RM sl-modem hardware not available

2022-05-20 Thread Steve Langasek
I think the rationale here is insufficient to justify a removal.

> However, it appears that to the best of my knowledge all hardware
> vendors of SmartLink chips, modems, or whitelabel ODMs are all
> out of business at least as far back as 2005.

Lack of currently-produced hardware is not an argument for ceasing to
support existing hardware which may still be in use.  (This would not,
for example, be a rationale for disabling any of the many drivers in the
linux package for hardware that is no longer produced.)

> sl-modem also does not pass the cat-video test - it is unlikely that even
> if one has sl-modem working one can open Ubuntu and watch a cat
> video online.

I don't know what evidence you have to support this conclusion.

> sl-modem-daemon only builds on i386, and has no amd64 userspace
support.

Yes, but the i386 package is still installable on amd64, so this doesn't
seem to matter for users.

> the kernel driver is not upstream and thus requires constant patching
> by our kernel team to keep building.

"constant patching": there has been exactly one round of patching by the
kernel team to fix a build failure, in 2019.

Note that this package was removed once before, but came back via Debian
(bug #1650379).

If there were pointers to concrete evidence that this is a maintenance
burden for the kernel team, I would accept that as a removal rationale.

** Changed in: sl-modem (Ubuntu)
   Status: Triaged => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1915878

Title:
  RM sl-modem hardware not available

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sl-modem/+bug/1915878/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1973885] Re: kernel panic with latest daily iso 20.04

2022-05-19 Thread Steve Langasek
At minimum we need to see the console output from this kernel panic.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973885

Title:
  kernel panic with latest daily iso 20.04

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1972115] Re: ubuntu-bug exits after dialog instead of sending data

2022-05-19 Thread Steve Langasek
On Thu, May 19, 2022 at 12:25:22PM -, Ralf Sternberg wrote:
> This bug seems to prevent me from providing a crash log in
> https://bugs.launchpad.net/bugs/1973802.

> Is there any alternative way of attaching a crash log to a bug report?
> Attachment doesn't work, apparently because of the file size. Thanks.

Are you running the 'apport-collect' command?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1972115

Title:
  ubuntu-bug  exits after dialog instead of sending data

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1958224] Proposed package upload rejected

2022-05-18 Thread Steve Langasek
An upload of brltty to jammy-proposed has been rejected from the upload
queue for the following reason: "Would introduce a critical regression
for blind users of this hardware".

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958224

Title:
  brltty claiming cp210x devices on 22.04

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1958224] Re: brltty claiming cp210x devices on 22.04

2022-05-18 Thread Steve Langasek
I understand the importance of fixing this conflict, and I agree it's
bad behavior on the part of the hardware manufacturer that retail
devices were shipped using these generic USB IDs, but the consequence of
the proposed SRU - disabling the use of brltty on the USB ids in
question - is that a blind user who uses one of these devices, who has
successfully installed Ubuntu and has a working system, will on the
installation of this SRU have their only accessible tty device rendered
inoperable.

That represents a CRITICAL regression for the users in question.  It
effectively bricks their machine and requires the user to rely on a
sighted person (who is also Ubuntu-knowledgeable) to get it working
again.

So I am rejecting this SRU.  It's unfortunate that this wasn't caught
before release, but now that support for this hardware is present in the
release, we can't be bricking blind users' systems to enable other
cp210x devices.  We'll need to find some other path forward.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1958224

Title:
  brltty claiming cp210x devices on 22.04

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1970789] Re: Microsoft Code PlatformIO extension conflicts with brltty Ubuntu 22.04 LTS (USB ID 1a86:7523)

2022-05-18 Thread Steve Langasek
*** This bug is a duplicate of bug 1958224 ***
https://bugs.launchpad.net/bugs/1958224

** This bug has been marked a duplicate of bug 1958224
   brltty claiming cp210x devices on 22.04

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970789

Title:
  Microsoft Code PlatformIO extension conflicts with brltty Ubuntu 22.04
  LTS (USB ID 1a86:7523)

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1974091] Re: no-longer-needed build-dep on execstack

2022-05-18 Thread Steve Langasek
** Description changed:

  The nvidia packages in Ubuntu have a build-dep on execstack, as
  requested in bug #409456.
  
  That bug was filed 13 years ago, about the fact that the upstream
  binaries were built with executable stack.  They've been rebuilt a few
  times since then, and there are no longer any upstream binaries with an
  executable stack:
  
- $ find NVIDIA-Linux/ -name *.so* | xargs -n1 readelf -lW | grep GNU_STACK.*E  
- $ readelf -SW NVIDIA-Linux/nvidia-{smi,xconfig,persistenced} | grep 
GNU_STACK.*E
+ $ find NVIDIA-Linux/ -name *.so* | xargs -n1 readelf -lW | grep GNU_STACK.*E
+ $ readelf -lW NVIDIA-Linux/nvidia-{smi,xconfig,persistenced} | grep 
GNU_STACK.*E
  $
  
  So the current use of execstack is a no-op.
  
  The execstack binary is built from prelink, which was dropped from
  Debian over a year ago.
  
  Please drop this build-dependency from all the nvidia packages so that
  we can drop prelink from the archive.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1974091

Title:
  no-longer-needed build-dep on execstack

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1974091/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1974091] Re: no-longer-needed build-dep on execstack

2022-05-18 Thread Steve Langasek
NB the readelf commands used above come from
https://wiki.ubuntu.com/SecurityTeam/Roadmap/ExecutableStacks

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1974091

Title:
  no-longer-needed build-dep on execstack

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1974091/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1974091] [NEW] no-longer-needed build-dep on execstack

2022-05-18 Thread Steve Langasek
Public bug reported:

The nvidia packages in Ubuntu have a build-dep on execstack, as
requested in bug #409456.

That bug was filed 13 years ago, about the fact that the upstream
binaries were built with executable stack.  They've been rebuilt a few
times since then, and there are no longer any upstream binaries with an
executable stack:

$ find NVIDIA-Linux/ -name *.so* | xargs -n1 readelf -lW | grep GNU_STACK.*E  
$ readelf -SW NVIDIA-Linux/nvidia-{smi,xconfig,persistenced} | grep GNU_STACK.*E
$

So the current use of execstack is a no-op.

The execstack binary is built from prelink, which was dropped from
Debian over a year ago.

Please drop this build-dependency from all the nvidia packages so that
we can drop prelink from the archive.

** Affects: nvidia-graphics-drivers-470 (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1974091

Title:
  no-longer-needed build-dep on execstack

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-470/+bug/1974091/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1974069] [NEW] warning: ‘__builtin_memset’ specified size between 18446744071562067968 and 184467440737095516 15 exceeds maximum object size 9223372036854775807

2022-05-18 Thread Steve Langasek
Public bug reported:

The scotch autopkgtest is failing on ppc64el in kinetic because the
compiler is outputting a warning to stderr:

[...]
mpicc -O3 -fPIC -I. -I/usr/include/metis -Drestrict=__restrict 
-DCOMMON_FILE_COMPRESS_GZ -DCOMMON_FILE_COMPRESS_BZ2 
-DCOMMON_FILE_COMPRESS_LZMA -DSCOTCH_PTHREAD -DCOMMON_PTHREAD 
-DSCOTCH_PTHREAD_NUMBER=2 -DCOMMON_PTHREAD_FILE 
-DCOMMON_RANDOM_FIXED_SEED -DSCOTCH_RENAME -DSCOTCH_RENAME_PARSER 
-I/usr/include/scotch -L/usr/lib/powerpc64le-linux-gnu 
test_scotch_graph_induce.c -o test_scotch_graph_induce -lscotch -lscotcherr -lm
In file included from /usr/include/string.h:535,
 from test_scotch_graph_induce.c:59:
In function 'memset',
inlined from 'main' at test_scotch_graph_induce.c:134:3:
/usr/include/powerpc64le-linux-gnu/bits/string_fortified.h:59:10: warning: 
'__builtin_memset' specified size between 18446744071562067968 and 
18446744073709551615 exceeds maximum object size 9223372036854775807 
[-Wstringop-overflow=]
   59 |   return __builtin___memset_chk (__dest, __ch, __len,
  |  ^~~~
   60 |  __glibc_objsize0 (__dest));
  |  ~~
[...]

  (https://autopkgtest.ubuntu.com/results/autopkgtest-
kinetic/kinetic/ppc64el/s/scotch/20220509_164658_7d31d@/log.gz)

Reproducible when invoking gcc directly instead of via the mpicc
wrapper; also reproducible with gcc -O2 instead of gcc -O3.

This warning is patently nonsense.  The size ranges listed is, in hex,
0x8000-0x.  We are not trying to memset an
object of that size, and at runtime there is no problem with the actual
behavior.

So something is wrong with gcc's calculation here, resulting in a
spurious warning.

This issue was not reproduced when the autopkgtest ran on ppc64el in
Debian.  I don't know why, as the compiler should be essentially the
same between Debian and Ubuntu - and I've ruled out this being a problem
of the -O3 default that exists in Ubuntu packaging but not in Debian.

** Affects: gcc-11 (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1974069

Title:
  warning: ‘__builtin_memset’ specified size between
  18446744071562067968 and 184467440737095516 15 exceeds maximum object
  size 9223372036854775807

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-11/+bug/1974069/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1973885] Re: kernel panic with latest daily iso 20.04

2022-05-18 Thread Steve Langasek
** Project changed: ubuntu-cdimage => linux (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973885

Title:
  kernel panic with latest daily iso 20.04

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1973796] Re: autopkgtests fail on s390x with new libzstd

2022-05-18 Thread Steve Langasek
Thanks, I retriggered the test and it passed.

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

** Changed in: golang-github-valyala-gozstd (Ubuntu)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973796

Title:
  autopkgtests fail on s390x with new libzstd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-github-valyala-gozstd/+bug/1973796/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1877194] Re: switch-on-connect mistakes startup for USB hotplug, so seemingly ignores the old default device on reboot

2022-05-17 Thread Steve Langasek
This behavior particularly affects Raspberry Pis, where USB is the only
bus available for a lot of devices and treating this as "hotplug" gives
wrong results.

That doesn't mean the default should change for pulseaudio on the
desktop in general, but should somehow be treated in a hardware-specific
manner.

I would suggest making /etc/pulse/default.pa key its loading of module-
switch-on-connect on the absence of a flag file, which could then be
provided by raspberry pi images.

I'm going to open a task on ubuntu-settings for the moment, since it
provides ubuntu-raspi-settings that seems the most likely existing
package to attach the raspi side of this to.

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

** Changed in: ubuntu-settings (Ubuntu)
 Assignee: (unassigned) => Dave Jones (waveform)

** Also affects: pulseaudio (Ubuntu Kinetic)
   Importance: Low
   Status: Triaged

** Also affects: ubuntu-settings (Ubuntu Kinetic)
   Importance: Undecided
 Assignee: Dave Jones (waveform)
   Status: New

** Tags added: rls-jj-incoming

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1877194

Title:
  switch-on-connect mistakes startup for USB hotplug, so seemingly
  ignores the old default device on reboot

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1973796] [NEW] autopkgtests fail on s390x with new libzstd

2022-05-17 Thread Steve Langasek
Public bug reported:

libzstd is currently blocked in -proposed by a regression in the
autopkgtests of golang-github-valyala-gozstd on s390x.

[...]
== RUN   TestNewWriterLevel
FAILgithub.com/valyala/gozstd   3.458s
FAIL
dh_auto_test: error: cd _build && go test -vet=off -v -p 1 
github.com/valyala/gozstd returned exit code 1
[...]

  (https://autopkgtest.ubuntu.com/results/autopkgtest-
kinetic/kinetic/s390x/g/golang-github-valyala-
gozstd/20220517_120214_b707c@/log.gz)

** Affects: golang-github-valyala-gozstd (Ubuntu)
 Importance: Undecided
 Status: New

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


** Tags: update-excuse

** Tags added: update-excuse

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973796

Title:
  autopkgtests fail on s390x with new libzstd

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-github-valyala-gozstd/+bug/1973796/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1973630] Re: Deprecate /etc/default/nfs-*

2022-05-16 Thread Steve Langasek
more than just removing them, it's important to migrate any
configuration on upgrade.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973630

Title:
  Deprecate /etc/default/nfs-*

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1973630/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1972115] Re: ubuntu-bug exits after dialog instead of sending data

2022-05-09 Thread Steve Langasek
I don't think it's by design that if you explicitly run 'ubuntu-bug', it
exits without giving you the opportunity to file a bug report or
explaining why.  Yes, it's intentional that we don't by default open bug
reports on crashes, but the above seems like an accidental outcome.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1972115

Title:
  ubuntu-bug  exits after dialog instead of sending data

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1972035] Re: installed grub-efi on bios install on upgrade from 21.10 to 22.04

2022-05-09 Thread Steve Langasek
In Ubuntu 21.10, we always install both the EFI and BIOS bootloaders to
disk, so that future changes to the system's firmware don't break
compatibility with the OS.

The upgrade failure indicates that, at some point after installation,
the partition that was used as the EFI System Partition has been
reformatted and is no longer recognized as one; but you did not remove
the EFI grub package from your system so it's still expected to be
there.

My recommendation would be to NOT remove the ESP that Ubuntu configured.
But if you don't want to restore it, then you need to remove the grub-
efi-amd64-signed package from your system instead.

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1972035

Title:
  installed grub-efi on bios install on upgrade from 21.10 to 22.04

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1972133] [NEW] +/- geometry offsets don't work under Wayland

2022-05-08 Thread Steve Langasek
Public bug reported:

When using the default wayland-based session in Ubuntu 22.04, trying to
use +/- to control window placement doesn't work.  E.g. the following
should give me a gnome-terminal window in the lower-right corner of the
screen:

  gnome-terminal --geometry -0-0

It does not; instead it stacks it with a window position just slightly
down from and to the left of the previous window.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xwayland 2:22.1.1-1
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Sun May  8 18:14:34 2022
InstallationDate: Installed on 2019-12-23 (867 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
SourcePackage: xwayland
UpgradeStatus: Upgraded to jammy on 2022-04-15 (23 days ago)

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


** Tags: amd64 apport-bug jammy

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1972133

Title:
  +/- geometry offsets don't work under Wayland

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1972115] [NEW] ubuntu-bug exits after dialog instead of sending data

2022-05-08 Thread Steve Langasek
Public bug reported:

After a gnome-shell crash, I am trying to manually submit it by running
'ubuntu-bug /var/crash/_usr_bin_gnome-shell.1000.crash'.  This results
in an apport-gtk prompt asking me "Send problem report to the
developers?"  When I click 'send', the dialog disappears and ubuntu-bug
exits, without uploading data to launchpad or interfacing with the
browser.

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


** Tags: rls-jj-incoming

** Tags added: rls-jj-incoming

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1972115

Title:
  ubuntu-bug  exits after dialog instead of sending data

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1968260] Re: [UBUNTU 20.04] genprotimg fails to process z15 host key documents after April 2022 (s390-tools)

2022-05-06 Thread Steve Langasek
Hello bugproxy, or anyone else affected,

Accepted s390-tools into focal-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/s390-tools/2.12.0-0ubuntu3.5 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: s390-tools (Ubuntu Focal)
   Status: In Progress => Fix Committed

** Changed in: s390-tools-signed (Ubuntu Impish)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-focal

** Changed in: s390-tools-signed (Ubuntu Focal)
   Status: In Progress => Fix Committed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968260

Title:
  [UBUNTU 20.04] genprotimg fails to process z15 host key documents
  after April 2022 (s390-tools)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1968260/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1968259] Re: [UBUNTU 21.10 / 22.04] check_hostkeydoc is checking the certificate issuer too strictly (s390-tools)

2022-05-06 Thread Steve Langasek
Hello bugproxy, or anyone else affected,

Accepted s390-tools into impish-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/s390-tools/2.17.0-0ubuntu2.1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
impish to verification-done-impish. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-impish. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: s390-tools (Ubuntu Impish)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-impish

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968259

Title:
  [UBUNTU 21.10 / 22.04] check_hostkeydoc is checking the certificate
  issuer too strictly (s390-tools)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1968259/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1968260] Re: [UBUNTU 20.04] genprotimg fails to process z15 host key documents after April 2022 (s390-tools)

2022-05-06 Thread Steve Langasek
Hello bugproxy, or anyone else affected,

Accepted s390-tools into impish-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/s390-tools/2.17.0-0ubuntu2.1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
impish to verification-done-impish. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-impish. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: s390-tools (Ubuntu Impish)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-impish

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968260

Title:
  [UBUNTU 20.04] genprotimg fails to process z15 host key documents
  after April 2022 (s390-tools)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1968260/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1962704] Re: iwlwifi: Unknown symbol iwl_mei_is_connected

2022-05-06 Thread Steve Langasek
Hello You-Sheng, or anyone else affected,

Accepted backport-iwlwifi-dkms into impish-proposed. The package will
build now and be available at
https://launchpad.net/ubuntu/+source/backport-iwlwifi-
dkms/9580-0ubuntu1~21.10.1.1 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
impish to verification-done-impish. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-impish. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: backport-iwlwifi-dkms (Ubuntu Impish)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-impish

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962704

Title:
  iwlwifi: Unknown symbol iwl_mei_is_connected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1962704/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1962704] Re: iwlwifi: Unknown symbol iwl_mei_is_connected

2022-05-06 Thread Steve Langasek
The rationale for SRU to impish is clear-cut, as you explain that the
package currently in impish is unusable due to symbol resolution errors
and cannot work for any users.

But for focal you say that the iwlwifi module *may* fail to load
firmware; this implies that the package currently in focal can work for
some users, which means that there is the possibility of this new
version regressing the package for those users.  The SRU policy says:

   For Long Term Support releases we regularly want to enable new
hardware. Such changes are appropriate provided that we can ensure not
to affect upgrades on existing hardware.

This bug report lacks information about how you have ensured this will
not regress existing hardware and does not have a standing SRU
exception, therefore as written does not fit our SRU policy.

** Changed in: backport-iwlwifi-dkms (Ubuntu Focal)
   Status: In Progress => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1962704

Title:
  iwlwifi: Unknown symbol iwl_mei_is_connected

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/backport-iwlwifi-dkms/+bug/1962704/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1971960] Re: [FTBFS] python-xmlsec fails to build on s390x

2022-05-06 Thread Steve Langasek
Hello Chris, or anyone else affected,

Accepted python-xmlsec into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/python-
xmlsec/1.3.12-1ubuntu0.22.04.1 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Description changed:

  [Impact]
  
- python3-xmlsec isn't available to installce on s390x on Jammy.
+ python3-xmlsec isn't available to install on s390x on Jammy.
  
  As can be seen in this build log
  (https://launchpadlibrarian.net/599963344/buildlog_ubuntu-
  focal-s390x.python-xmlsec_1.3.12-1build1~cloud0_BUILDING.txt.gz), the
  s390x build fails testing with a lot of errors matching:
  
  ___ ERROR at teardown of
  TestSignContext.test_set_enabled_key_data_bad_args 
  
  self = 
  
- def test_set_enabled_key_data_bad_args(self):
- ctx = xmlsec.SignatureContext()
+ def test_set_enabled_key_data_bad_args(self):
+ ctx = xmlsec.SignatureContext()
  >   ctx.key = xmlsec.Key.from_file(self.path('rsakey.pem'), 
format=consts.KeyDataFormatPem)
  E   xmlsec.Error: (1, 'cannot read key')
  
  tests/test_ds.py:326: Error
  - Captured stderr call 
-
  
func=xmlSecOpenSSLAppKeyLoadBIO:file=app.c:line=330:obj=unknown:subj=unknown:error=17:invalid
 format:format=131072
  
func=xmlSecOpenSSLAppKeyLoad:file=app.c:line=175:obj=unknown:subj=xmlSecOpenSSLAppKeyLoadBIO:error=1:xmlsec
 library function 
failed:filename=/<>/.pybuild/cpython3_3.8/build/tests/data/rsakey.pem
  
func=xmlSecOpenSSLAppKeyLoadBIO:file=app.c:line=330:obj=unknown:subj=unknown:error=17:invalid
 format:format=131072
  
func=xmlSecOpenSSLAppKeyLoad:file=app.c:line=175:obj=unknown:subj=xmlSecOpenSSLAppKeyLoadBIO:error=1:xmlsec
 library function 
failed:filename=/<>/.pybuild/cpython3_3.8/build/tests/data/rsakey.pem
  
func=xmlSecOpenSSLAppKeyLoadBIO:file=app.c:line=330:obj=unknown:subj=unknown:error=17:invalid
 format:format=131072
  
func=xmlSecOpenSSLAppKeyLoad:file=app.c:line=175:obj=unknown:subj=xmlSecOpenSSLAppKeyLoadBIO:error=1:xmlsec
 library function 
failed:filename=/<>/.pybuild/cpython3_3.8/build/tests/data/rsakey.pem
  
func=xmlSecOpenSSLAppKeyLoadBIO:file=app.c:line=330:obj=unknown:subj=unknown:error=17:invalid
 format:format=131072
  
func=xmlSecOpenSSLAppKeyLoad:file=app.c:line=175:obj=unknown:subj=xmlSecOpenSSLAppKeyLoadBIO:error=1:xmlsec
 library function 
failed:filename=/<>/.pybuild/cpython3_3.8/build/tests/data/rsakey.pem
  
func=xmlSecOpenSSLAppKeyLoadBIO:file=app.c:line=330:obj=unknown:subj=unknown:error=17:invalid
 format:format=131072
  
func=xmlSecOpenSSLAppKeyLoad:file=app.c:line=175:obj=unknown:subj=xmlSecOpenSSLAppKeyLoadBIO:error=1:xmlsec
 library function 
failed:filename=/<>/.pybuild/cpython3_3.8/build/tests/data/rsakey.pem
  
func=xmlSecOpenSSLAppKeyLoadBIO:file=app.c:line=330:obj=unknown:subj=unknown:error=17:invalid
 format:format=131072
  
func=xmlSecOpenSSLAppKeyLoad:file=app.c:line=175:obj=unknown:subj=xmlSecOpenSSLAppKeyLoadBIO:error=1:xmlsec
 library function 
failed:filename=/<>/.pybuild/cpython3_3.8/build/tests/data/rsakey.pem
  
func=xmlSecOpenSSLAppKeyLoadBIO:file=app.c:line=330:obj=unknown:subj=unknown:error=17:invalid
 format:format=131072
  
func=xmlSecOpenSSLAppKeyLoad:file=app.c:line=175:obj=unknown:subj=xmlSecOpenSSLAppKeyLoadBIO:error=1:xmlsec
 library function 
failed:filename=/<>/.pybuild/cpython3_3.8/build/tests/data/rsakey.pem
  
func=xmlSecOpenSSLAppKeyLoadBIO:file=app.c:line=330:obj=unknown:subj=unknown:error=17:invalid
 format:format=131072
  
func=xmlSecOpenSSLAppKeyLoad:file=app.c:line=175:obj=unknown:subj=xmlSecOpenSSLAppKeyLoadBIO:error=1:xmlsec
 library function 
failed:filename=/<>/.pybuild/cpython3_3.8/build/tests/data/rsakey.pem
  
func=xmlSecOpenSSLAppKeyLoadBIO:file=app.c:line=330:obj=unknown:subj=unknown:error=17:invalid
 format:format=131072
  

[Bug 1968318] Please test proposed package

2022-05-06 Thread Steve Langasek
Hello James, or anyone else affected,

Accepted ceph into jammy-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/ceph/17.2.0-0ubuntu0.22.04.1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968318

Title:
  [sru] ceph 17.2.0 (Quincy) release

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1968318] Re: [sru] ceph 17.2.0 (Quincy) release

2022-05-06 Thread Steve Langasek
diff -Nru ceph-17.1.0/debian/rules ceph-17.2.0/debian/rules
--- ceph-17.1.0/debian/rules2022-03-21 09:47:22.0 +
+++ ceph-17.2.0/debian/rules2022-04-29 14:12:46.0 +
@@ -73,6 +73,7 @@
 extraopts += -DWITH_RADOSGW_KAFKA_ENDPOINT=OFF
 extraopts += -DCMAKE_BUILD_TYPE=RelWithDebInfo
 extraopts += -DWITH_GRAFANA=ON
+extraopts += -DWITH_RADOSGW_SELECT_PARQUET=OFF
 
 ifneq (,$(findstring $(DEB_HOST_ARCH),amd64 arm64 ppc64el))
 extraopts += -DWITH_RBD_RWL=ON

This is a packaging change, but it's ok for SRU without a separate SRU
process because it is preserving behavior of the existing package (the
upstream default switched from ON to OFF between 17.1.0 and 17.2.0).

** Changed in: ceph (Ubuntu Jammy)
   Status: Triaged => Fix Committed

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968318

Title:
  [sru] ceph 17.2.0 (Quincy) release

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1970248] Re: .deb files open with Archive Manager by default

2022-05-06 Thread Steve Langasek
Missing 'where problems could occur' per
https://wiki.ubuntu.com/StableReleaseUpdates#SRU_Bug_Template

And I do see significant risk of problems; while the mime handler for
.deb files is incorrect, a diff of /etc/gnome/defaults.list vs
/usr/share/applications/gnome-mimeapps.list shows a number of
differences, including some types that are only handled in
/usr/share/applications/gnome-mimeapps.list.  Given that shipping
/usr/share/applications/gnome-mimeapps.list was unintentional and it's
so soon after release we might accept wholesale dropping of the file,
however I would still want to see analysis of the impact.

** Changed in: gnome-session (Ubuntu Jammy)
   Status: Fix Committed => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970248

Title:
  .deb files open with Archive Manager by default

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1970248/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969752] Re: oss4-dkms '-mfloat-abi=hard' build failure

2022-05-06 Thread Steve Langasek
Andrea, the -mfloat-abi=hard is only relevant on armhf; what about
dropping support for it only on armhf?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969752

Title:
  oss4-dkms '-mfloat-abi=hard' build failure

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969752] Re: oss4-dkms '-mfloat-abi=hard' build failure

2022-05-06 Thread Steve Langasek
And I'm more than happy for us to drop this as obsolete in kinetic and
later; please file a separate bug report for that and subscribe ubuntu-
archive.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969752

Title:
  oss4-dkms '-mfloat-abi=hard' build failure

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1951706] Re: Failed to unmount /oldroot/dev/pts: Device or resource busy

2022-05-06 Thread Steve Langasek
Please show the output of 'sudo lsblk' on this system.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1951706

Title:
  Failed to unmount /oldroot/dev/pts: Device or resource busy

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1971965] [NEW] fwupd has dbx plugin enabled but shouldn't

2022-05-06 Thread Steve Langasek
Public bug reported:

In discussion with the Security Team, I've learned that the dbx plugin
in fwupd is enabled by default.  Prior to 22.04 release I had
conversations about the fact that we should not be using fwupd to
deliver dbx updates by default, but these don't seem to have resulted in
changes to the packaging.  We may in the future want to use fwupd to
deliver dbx updates, but in the meantime there is a concern that
delivery of dbx updates needs to be coordinated with the OS (we have the
secureboot-db package seeded across all products in support of this),
and there is not coordination between fwupd and the OS package manager.

We need to update fwupd to disable the dbx plugin by default
(DisabledPlugins= in /etc/fwupd/daemon.conf).

This affects both jammy and focal, where fwupd has been SRUed.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: fwupd 1.7.5-3
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri May  6 11:04:01 2022
InstallationDate: Installed on 2019-12-23 (864 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: fwupd
UpgradeStatus: Upgraded to jammy on 2022-04-15 (20 days ago)

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

** Affects: fwupd (Ubuntu Focal)
 Importance: Undecided
 Status: New

** Affects: fwupd (Ubuntu Impish)
 Importance: Undecided
 Status: New

** Affects: fwupd (Ubuntu Jammy)
 Importance: Undecided
 Status: New

** Affects: fwupd (Ubuntu Kinetic)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug fr-2358 jammy wayland-session

** Description changed:

  In discussion with the Security Team, I've learned that the dbx plugin
  in fwupd is enabled by default.  Prior to 22.04 release I had
  conversations about the fact that we should not be using fwupd to
  deliver dbx updates by default, but these don't seem to have resulted in
  changes to the packaging.  We may in the future want to use fwupd to
  deliver dbx updates, but in the meantime there is a concern that
  delivery of dbx updates needs to be coordinated with the OS (we have the
  secureboot-db package seeded across all products in support of this),
  and there is not coordination between fwupd and the OS package manager.
  
  We need to update fwupd to disable the dbx plugin by default
  (DisabledPlugins= in /etc/fwupd/daemon.conf).
+ 
+ This affects both jammy and focal, where fwupd has been SRUed.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: fwupd 1.7.5-3
  ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
  Uname: Linux 5.15.0-27-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May  6 11:04:01 2022
  InstallationDate: Installed on 2019-12-23 (864 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  RebootRequiredPkgs: Error: path contained symlinks.
  SourcePackage: fwupd
  UpgradeStatus: Upgraded to jammy on 2022-04-15 (20 days ago)

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

** Also affects: fwupd (Ubuntu Impish)
   Importance: Undecided
   Status: New

** Also affects: fwupd (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

** Also affects: fwupd (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Tags added: fr-2358

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971965

Title:
  fwupd has dbx plugin enabled but shouldn't

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1971669] Re: Can't even launch `ubuntu-bug` console application to report any other bug!

2022-05-05 Thread Steve Langasek
Your log shows:

May 05 14:44:00 khteh-p17-2i update-notifier.desktop[15164]: File 
"/home/khteh/.local/lib/python3.10/site-packages/httplib2/__init__.py", line 
52, in 
May 05 14:44:00 khteh-p17-2i update-notifier.desktop[15164]: from . import auth
May 05 14:44:00 khteh-p17-2i update-notifier.desktop[15164]: File 
"/home/khteh/.local/lib/python3.10/site-packages/httplib2/auth.py", line 20, in 

May 05 14:44:00 khteh-p17-2i update-notifier.desktop[15164]: auth_param_name = 
token.copy().setName("auth-param-name").addParseAction(pp.downcaseTokens)
May 05 14:44:00 khteh-p17-2i update-notifier.desktop[15164]: AttributeError: 
module 'pyparsing' has no attribute 'downcaseTokens'

So, you have a locally-installed httplib2 in your home directory which
is not compatible with the pyparsing from the system.  You will need to
remove this.

** Package changed: update-notifier (Ubuntu) => apport (Ubuntu)

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971669

Title:
  Can't even launch `ubuntu-bug` console application to report any other
  bug!

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1965636] Re: libfuse2 no longer included in jammy, required for AppImages

2022-05-05 Thread Steve Langasek
fuse has been demoted from Ubuntu main in favor of fuse3; it would not
be appropriate to re-promote it to main and expand the security surface
of a default Ubuntu install (fuse is a very security-relevant facility),
and Ubuntu images build only from main.  So this is a wontfix for the
Ubuntu desktop, libfuse2 is not going to be brought back into the
default install and users who want to use libfuse2-dependent AppImages
will need to install this library themselves beforehand.

Our community flavors are free to make their own decisions about whether
to bundle libfuse2 by default, as several of them did before the
release.

** Changed in: ubuntu-meta (Ubuntu)
   Status: Confirmed => Won't Fix

** Changed in: ubuntu-meta (Ubuntu Jammy)
   Status: Confirmed => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965636

Title:
  libfuse2 no longer included in jammy, required for AppImages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1965636/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969689] Re: USB devices not detected on CM4

2022-05-05 Thread Steve Langasek
** Also affects: linux-raspi (Ubuntu Kinetic)
   Importance: Undecided
   Status: Confirmed

** Also affects: linux-raspi (Ubuntu Jammy)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969689

Title:
  USB devices not detected on CM4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1969689/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1925265] Re: Fresh install of hirsute-preinstalled-desktop-arm64+raspi has packages to autoremove

2022-05-04 Thread Steve Langasek
ok, figured this out a bit more.  oem-config is installed (because you need a 
first-boot configurator), which is built from ubiquity source.  
oem-config-firstboot runs:
apt-get -y purge ubiquity >>/var/log/oem-config.log 2>&1

But does not do an apt autoremove --purge afterwards.  So the code needs
changed to do this.

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925265

Title:
  Fresh install of hirsute-preinstalled-desktop-arm64+raspi has packages
  to autoremove

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1925265] Re: Fresh install of hirsute-preinstalled-desktop-arm64+raspi has packages to autoremove

2022-05-04 Thread Steve Langasek
This bug has been open now and listed in the release notes for 3
releases, including the latest LTS, which is far from ideal.  Has anyone
reproduced it with a current release?  If this is a preinstalled image,
why is this reported against ubiquity, which is the desktop installer?

I don't have a raspi to test on, but if I mount the jammy image and
chroot into it (without booting) I see:

# apt autoremove --purge
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
#

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925265

Title:
  Fresh install of hirsute-preinstalled-desktop-arm64+raspi has packages
  to autoremove

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1925265] Re: Fresh install of hirsute-preinstalled-desktop-arm64+raspi has packages to autoremove

2022-05-04 Thread Steve Langasek
** Also affects: ubiquity (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: ubiquity (Ubuntu Kinetic)
   Importance: Undecided
   Status: New

** Changed in: ubiquity (Ubuntu Impish)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1925265

Title:
  Fresh install of hirsute-preinstalled-desktop-arm64+raspi has packages
  to autoremove

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969529] Re: snapd slow to seed firefox on Pi 400

2022-05-04 Thread Steve Langasek
** Also affects: snapd (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: snapd (Ubuntu Kinetic)
   Importance: High
   Status: Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969529

Title:
  snapd slow to seed firefox on Pi 400

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969664] Re: 22.04 Vagrant Images Do Not Finish Initial Boot Due to SSH Timeout

2022-05-04 Thread Steve Langasek
** Summary changed:

- 22.04 Vagrant Images Do Not Finish Initial Boot Due to SSH Timout
+ 22.04 Vagrant Images Do Not Finish Initial Boot Due to SSH Timeout

** Also affects: livecd-rootfs (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: livecd-rootfs (Ubuntu Kinetic)
   Importance: Undecided
   Status: Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969664

Title:
  22.04 Vagrant Images Do Not Finish Initial Boot Due to SSH Timeout

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1969664/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1964025] Re: Do not support OpenSSL 3

2022-05-04 Thread Steve Langasek
** Also affects: ruby-net-ssh (Ubuntu Jammy)
   Importance: Undecided
   Status: New

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

** Also affects: ruby-bcrypt-pbkdf (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: ruby-net-ssh (Ubuntu Kinetic)
   Importance: Critical
   Status: In Progress

** Also affects: vagrant (Ubuntu Kinetic)
   Importance: Undecided
   Status: Triaged

** Also affects: ruby-bcrypt-pbkdf (Ubuntu Kinetic)
   Importance: Undecided
   Status: Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964025

Title:
  Do not support OpenSSL 3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ruby-bcrypt-pbkdf/+bug/1964025/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1922342] Re: Impish live session takes ages to boot on BIOS systems

2022-05-04 Thread Steve Langasek
** Also affects: casper (Ubuntu Kinetic)
   Importance: High
   Status: Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922342

Title:
  Impish live session takes ages to boot on BIOS systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1922342/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1930880] Re: Booting Ubuntu 21.04 from DVD takes more than 30 minutes and its environment are corrupted

2022-05-04 Thread Steve Langasek
** Also affects: casper (Ubuntu Kinetic)
   Importance: Medium
   Status: Triaged

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1930880

Title:
  Booting Ubuntu 21.04 from DVD takes more than 30 minutes and its
  environment are corrupted

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1930880/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1946828] Re: ntfsresize hang and call traces in syslog

2022-05-04 Thread Steve Langasek
** Also affects: ubiquity (Ubuntu Kinetic)
   Importance: Undecided
   Status: Confirmed

** Also affects: ntfs-3g (Ubuntu Kinetic)
   Importance: Undecided
   Status: Confirmed

** Also affects: linux (Ubuntu Kinetic)
   Importance: Undecided
   Status: Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1946828

Title:
  ntfsresize hang and call traces in syslog

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969353] Re: Apt/Grub issue with 22.04 Upgrade (Missing libcrypto.so.1.1)

2022-05-04 Thread Steve Langasek
** Changed in: grub-customizer (Ubuntu)
   Status: Confirmed => Won't Fix

** Changed in: ubuntu-release-upgrader (Ubuntu)
   Status: Confirmed => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969353

Title:
  Apt/Grub issue with 22.04 Upgrade (Missing libcrypto.so.1.1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub-customizer/+bug/1969353/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1971650] [NEW] wrong check for "server" in libssl3.postinst

2022-05-04 Thread Steve Langasek
Public bug reported:

A security update has just been applied to my system for openssl, and
the 'reboot required' message just popped on my desktop.  I looked to
see why this was, and found the following code in the libssl3 postinst:

# Here we issue the reboot notification for upgrades and
# security updates. We do want services to be restarted when we
# update for a security issue, but planned by the sysadmin, not
# automatically.

# Only issue the reboot notification for servers; we proxy this by
# testing that the X server is not running (LP: #244250)
if ! pidof /usr/lib/xorg/Xorg > /dev/null && [ -x 
/usr/share/update-notifier/notify-reboot-required ]; then
/usr/share/update-notifier/notify-reboot-required
fi

Now, AFAIK this is the only package that interfaces with notify-reboot-
required but omits the notification on desktops, so that seems to be an
inconsistent policy; but even if we thought that was the correct policy
to apply, the above check for a desktop is not because it doesn't match
in the case the user is running Xwayland, which most users not using the
nvidia driver will be doing now by default.

Also, this is now inside a block that checks for the presence of
needrestart, which is part of the server seed; so in effect this
notification now *never* fires on servers, it *only* fires on desktops.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: openssl 3.0.2-0ubuntu1.1
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Thu May  5 05:39:06 2022
InstallationDate: Installed on 2019-12-23 (863 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: openssl
UpgradeStatus: Upgraded to jammy on 2022-04-15 (19 days ago)

** Affects: openssl (Ubuntu)
 Importance: Medium
 Status: New


** Tags: amd64 apport-bug jammy rls-jj-incoming rls-kk-incoming wayland-session

** Changed in: openssl (Ubuntu)
   Importance: Undecided => Medium

** Tags added: rls-jj-incoming rls-kk-incoming

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971650

Title:
  wrong check for "server" in libssl3.postinst

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1965568] Re: missing dependency on python3-dbus

2022-05-04 Thread Steve Langasek
** Changed in: ubuntu-release-upgrader (Ubuntu)
 Assignee: (unassigned) => Nick Rosbrook (enr0n)

** Also affects: ubuntu-release-upgrader (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Also affects: ubuntu-release-upgrader (Ubuntu Kinetic)
   Importance: High
 Assignee: Nick Rosbrook (enr0n)
   Status: Confirmed

** Changed in: ubuntu-release-upgrader (Ubuntu Kinetic)
   Status: Confirmed => Triaged

** Changed in: ubuntu-release-upgrader (Ubuntu Jammy)
   Status: New => Triaged

** Changed in: ubuntu-release-upgrader (Ubuntu Jammy)
   Importance: Undecided => High

** Tags added: fr-2342

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965568

Title:
  missing dependency on python3-dbus

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1965568/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1965568] Re: missing dependency on python3-dbus

2022-05-04 Thread Steve Langasek
** Changed in: ubuntu-release-upgrader (Ubuntu)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1965568

Title:
  missing dependency on python3-dbus

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1965568/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1971427] Re: gdm in jammy defaults to wrong keymap option with no UI for fixing it

2022-05-03 Thread Steve Langasek
On Tue, May 03, 2022 at 03:13:06PM -, Sebastien Bacher wrote:
> Thank you for your bug report. Was dvorak the default only for your
> graphical session or for the system?

It's the default when I'm at a non-GUI tty.

> What configuration do you have in /etc/default/keyboard and
> /var/lib/AccountsService/users/$USER ?

$ cat /etc/default/keyboard 
XKBLAYOUT="us,gr,cn,ru,us"
XKBVARIANT="dvorak-alt-intl,polytonic,,,"
BACKSPACE="guess"
XKBMODEL="pc105"
XKBOPTIONS="grp_led:scroll"
$

$ sudo cat /var/lib/AccountsService/users/vorlon
[User]
Language=en_US
Session=
XSession=
Icon=/home/vorlon/.face
SystemAccount=false

[InputSource0]
xkb=us+dvorak-alt-intl

[InputSource1]
xkb=gr+polytonic

[InputSource2]
xkb=cn

[InputSource3]
xkb=ru
$

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971427

Title:
  gdm in jammy defaults to wrong keymap option with no UI for fixing it

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1971427] [NEW] gdm in jammy defaults to wrong keymap option with no UI for fixing it

2022-05-03 Thread Steve Langasek
Public bug reported:

After upgrade to jammy, gdm somehow has defaulted to the English US
keymap.  This is not my keymap of choice, and this is not the keymap
that was used on impish before upgrade.  It is a keymap that I had
configured as an option for my login session, but it was not the default
and after removing it from my user config, it persists as the keymap
used for gdm.

The keymap that *should* be used is English (Dvorak, alt. intl.) en.

There is a selector for the keymap in the top bar, but after every
logout, the keymap setting reverts to the wrong one.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: gdm3 42.0-1ubuntu7
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Tue May  3 14:36:21 2022
InstallationDate: Installed on 2019-12-23 (861 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
SourcePackage: gdm3
UpgradeStatus: Upgraded to jammy on 2022-04-15 (17 days ago)

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


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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1971427

Title:
  gdm in jammy defaults to wrong keymap option with no UI for fixing it

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1964510] Re: [SRU] enable signing riscv64 binaries in bionic

2022-05-03 Thread Steve Langasek
Hello Heinrich, or anyone else affected,

Accepted sbsigntool into focal-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/sbsigntool/0.9.2-2ubuntu1.1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: sbsigntool (Ubuntu Bionic)
   Status: Incomplete => In Progress

** Changed in: sbsigntool (Ubuntu Focal)
   Status: Confirmed => Fix Committed

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

** Changed in: sbsigntool (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-bionic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964510

Title:
  [SRU] enable signing riscv64 binaries in bionic

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1964510] Please test proposed package

2022-05-03 Thread Steve Langasek
Hello Heinrich, or anyone else affected,

Accepted sbsigntool into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/sbsigntool/0.9.2-2ubuntu1~18.04.2
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
bionic to verification-done-bionic. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-bionic. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964510

Title:
  [SRU] enable signing riscv64 binaries in bionic

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1964510] Re: [SRU] enable signing riscv64 binaries in bionic

2022-05-02 Thread Steve Langasek
Note that the version number in the focal diff is wrong; focal already
has 0.9.2-2ubuntu1, so needs to have a version number that sorts later
than this such as 0.9.2-2ubuntu1.1.
https://wiki.ubuntu.com/SecurityTeam/UpdatePreparation#Update_the_packaging
provides recommendations for the version schema to use for SRUs.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964510

Title:
  [SRU] enable signing riscv64 binaries in bionic

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1964510] Re: [SRU] enable signing riscv64 binaries in bionic

2022-05-02 Thread Steve Langasek
Please include in the test case a pointer to a specific riscv64 EFI
binary that should be used for testing.

** Changed in: sbsigntool (Ubuntu Bionic)
   Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1964510

Title:
  [SRU] enable signing riscv64 binaries in bionic

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1970232] Re: Remove package khmer

2022-05-02 Thread Steve Langasek
Removing packages from kinetic:
khmer 2.1.2+dfsg-10 in kinetic
khmer 2.1.2+dfsg-10 in kinetic amd64
khmer 2.1.2+dfsg-10 in kinetic arm64
khmer-common 2.1.2+dfsg-10 in kinetic amd64
khmer-common 2.1.2+dfsg-10 in kinetic arm64
khmer-common 2.1.2+dfsg-10 in kinetic armhf
khmer-common 2.1.2+dfsg-10 in kinetic i386
khmer-common 2.1.2+dfsg-10 in kinetic ppc64el
khmer-common 2.1.2+dfsg-10 in kinetic riscv64
khmer-common 2.1.2+dfsg-10 in kinetic s390x
liboxli-dev 2.1.2+dfsg-10 in kinetic amd64
liboxli-dev 2.1.2+dfsg-10 in kinetic arm64
liboxli1 2.1.2+dfsg-10 in kinetic amd64
liboxli1 2.1.2+dfsg-10 in kinetic arm64
Comment: FTBFS with python3.10; Debian bug #1008402, LP: #1970232
1 package successfully removed.
Removing packages from kinetic-proposed:
khmer 2.1.2+dfsg-10build1 in kinetic
Comment: FTBFS with python3.10; Debian bug #1008402, LP: #1970232
1 package successfully removed.


** Changed in: khmer (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970232

Title:
  Remove package khmer

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1970232] Re: Remove package khmer

2022-05-02 Thread Steve Langasek
$ reverse-depends src:khmer
Reverse-Recommends
* med-bio   (for khmer)

Packages without architectures listed are reverse-dependencies in: amd64, 
arm64, armhf, i386, ppc64el, s390x
$ reverse-depends src:khmer -a source
No reverse dependencies found
$

Ok to remove.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970232

Title:
  Remove package khmer

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1970480] Re: please remove elog

2022-05-02 Thread Steve Langasek
It is already gone from kinetic.  Are you asking that it be removed from
stable releases?

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970480

Title:
  please remove elog

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1939349] Re: frequent hangs with latest hirsute kernel (nvidia graphics)

2022-05-02 Thread Steve Langasek
The tradeoff of disabling hybrid graphics is that, with discrete nvidia
graphics only running, I lose all power management, screen power off,
and suspend/resume support (because suspend works, but after resume
video does not come back).

Since I'm now at a sprint, these are bigger practical issues that have
caused me to revisit this bug.  I've confirmed that re-enabling hybrid
graphics still makes the system hang early after boot.

I've now removed the nvidia drivers from my system, and so far have an
uptime of 55 minutes, which is a substantial improvement.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1939349

Title:
  frequent hangs with latest hirsute kernel (nvidia graphics)

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1970959] Re: [MIR] libgweather4

2022-05-01 Thread Steve Langasek
Override component to main
libgweather4 4.0.0-2 in kinetic: universe/misc -> main
gir1.2-gweather-4.0 4.0.0-2 in kinetic amd64: 
universe/introspection/optional/100% -> main
gir1.2-gweather-4.0 4.0.0-2 in kinetic arm64: 
universe/introspection/optional/100% -> main
gir1.2-gweather-4.0 4.0.0-2 in kinetic armhf: 
universe/introspection/optional/100% -> main
gir1.2-gweather-4.0 4.0.0-2 in kinetic i386: 
universe/introspection/optional/100% -> main
gir1.2-gweather-4.0 4.0.0-2 in kinetic ppc64el: 
universe/introspection/optional/100% -> main
gir1.2-gweather-4.0 4.0.0-2 in kinetic riscv64: 
universe/introspection/optional/100% -> main
gir1.2-gweather-4.0 4.0.0-2 in kinetic s390x: 
universe/introspection/optional/100% -> main
libgweather-4-0 4.0.0-2 in kinetic amd64: universe/libs/optional/100% -> main
libgweather-4-0 4.0.0-2 in kinetic arm64: universe/libs/optional/100% -> main
libgweather-4-0 4.0.0-2 in kinetic armhf: universe/libs/optional/100% -> main
libgweather-4-0 4.0.0-2 in kinetic i386: universe/libs/optional/100% -> main
libgweather-4-0 4.0.0-2 in kinetic ppc64el: universe/libs/optional/100% -> main
libgweather-4-0 4.0.0-2 in kinetic riscv64: universe/libs/optional/100% -> main
libgweather-4-0 4.0.0-2 in kinetic s390x: universe/libs/optional/100% -> main
libgweather-4-common 4.0.0-2 in kinetic amd64: universe/libs/optional/100% -> 
main
libgweather-4-common 4.0.0-2 in kinetic arm64: universe/libs/optional/100% -> 
main
libgweather-4-common 4.0.0-2 in kinetic armhf: universe/libs/optional/100% -> 
main
libgweather-4-common 4.0.0-2 in kinetic i386: universe/libs/optional/100% -> 
main
libgweather-4-common 4.0.0-2 in kinetic ppc64el: universe/libs/optional/100% -> 
main
libgweather-4-common 4.0.0-2 in kinetic riscv64: universe/libs/optional/100% -> 
main
libgweather-4-common 4.0.0-2 in kinetic s390x: universe/libs/optional/100% -> 
main
libgweather-4-dev 4.0.0-2 in kinetic amd64: universe/libdevel/optional/100% -> 
main
libgweather-4-dev 4.0.0-2 in kinetic arm64: universe/libdevel/optional/100% -> 
main
libgweather-4-dev 4.0.0-2 in kinetic armhf: universe/libdevel/optional/100% -> 
main
libgweather-4-dev 4.0.0-2 in kinetic i386: universe/libdevel/optional/100% -> 
main
libgweather-4-dev 4.0.0-2 in kinetic ppc64el: universe/libdevel/optional/100% 
-> main
libgweather-4-dev 4.0.0-2 in kinetic riscv64: universe/libdevel/optional/100% 
-> main
libgweather-4-dev 4.0.0-2 in kinetic s390x: universe/libdevel/optional/100% -> 
main
29 publications overridden.


** Changed in: libgweather4 (Ubuntu)
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970959

Title:
  [MIR] libgweather4

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1970959] Re: [MIR] libgweather4

2022-04-29 Thread Steve Langasek
(The only package still needing fixed for this is gnome-shell; the other
4 are all waiting in -proposed together.)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970959

Title:
  [MIR] libgweather4

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1970959] Re: [MIR] libgweather4

2022-04-29 Thread Steve Langasek
We shouldn't need an MIR process here as it is a replacement for the
existing source.  However, this requires that you get all reverse-
depends switched to use the new one so we can do a drop-in replacement.

$ reverse-depends -r jammy -c main src:libgweather
Reverse-Depends
* evolution-data-server (for libgweather-3-16)
* gnome-calendar(for libgweather-3-16)
* gnome-initial-setup   (for libgweather-3-16)
* gnome-settings-daemon (for libgweather-3-16)
* gnome-shell   (for gir1.2-gweather-3.0)

$

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970959

Title:
  [MIR] libgweather4

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1970464] Re: Please remove acpi-support from the archive

2022-04-29 Thread Steve Langasek
Removing packages from kinetic:
acpi-support 0.144 in kinetic
acpi-support 0.144 in kinetic amd64
Comment: Obsoleted by systemd; LP: #1970464
1 package successfully removed.


** Changed in: acpi-support (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970464

Title:
  Please remove acpi-support from the archive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/acpi-support/+bug/1970464/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1970464] Re: Please remove acpi-support from the archive

2022-04-29 Thread Steve Langasek
reverse-depends doesn't yet work for kinetic, but:

$ apt rdepends acpi-support
acpi-support
Reverse Depends:
$

So this can be removed now.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970464

Title:
  Please remove acpi-support from the archive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/acpi-support/+bug/1970464/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1970789] Re: Microsoft Code PlatformIO extension conflicts with brltty Ubuntu 22.04 LTS

2022-04-28 Thread Steve Langasek
Your log shows:

Apr 28 19:03:14 HIDDEN kernel: [ 1063.197438] usb 3-2.1: new full-speed USB 
device number 7 using xhci_hcd
Apr 28 19:03:14 HIDDEN kernel: [ 1063.321857] usb 3-2.1: New USB device found, 
idVendor=1a86, idProduct=7523, bcdDevice= 2.64
Apr 28 19:03:14 HIDDEN kernel: [ 1063.321866] usb 3-2.1: New USB device 
strings: Mfr=0, Product=2, SerialNumber=0
Apr 28 19:03:14 HIDDEN kernel: [ 1063.321869] usb 3-2.1: Product: USB Serial

And /lib/udev/rules.d/85-brltty.rules says:

# Device: 1A86:7523
# Baum [NLS eReader Zoomax (20 cells)]
ENV{PRODUCT}=="1a86/7523/*", ENV{BRLTTY_BRAILLE_DRIVER}="bm", 
GOTO="brltty_usb_run"

What is the device in question? /usr/share/misc/usb.ids says it is
QinHeng Electronics, "CH340 serial converter" which does sound too
generic for brltty.


** Summary changed:

- Microsoft Code PlatformIO extension conflicts with brltty Ubuntu 22.04 LTS
+ Microsoft Code PlatformIO extension conflicts with brltty Ubuntu 22.04 LTS 
(USB ID 1a86:7523)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970789

Title:
  Microsoft Code PlatformIO extension conflicts with brltty Ubuntu 22.04
  LTS (USB ID 1a86:7523)

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969464] Re: Ubuntu 22.04 fails update Unpacking casper (1.470) over (1.468)

2022-04-28 Thread Steve Langasek
** Changed in: casper (Ubuntu)
   Status: New => Incomplete

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969464

Title:
  Ubuntu 22.04 fails update Unpacking casper (1.470) over (1.468)

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1970464] Re: Please remove acpi-support from the archive

2022-04-26 Thread Steve Langasek
Removing packages from kinetic:
powermanagement-interface 0.3.21 in kinetic
powermanagement-interface 0.3.21 in kinetic amd64
powermanagement-interface 0.3.21 in kinetic arm64
powermanagement-interface 0.3.21 in kinetic armhf
powermanagement-interface 0.3.21 in kinetic ppc64el
powermanagement-interface 0.3.21 in kinetic riscv64
powermanagement-interface 0.3.21 in kinetic s390x
Comment: Ubuntu-specific, unmaintained, obsolete and unused (and probably 
broken); LP: #1970464
1 package successfully removed.


** Changed in: powermanagement-interface (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970464

Title:
  Please remove acpi-support from the archive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/acpi-support/+bug/1970464/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1970464] Re: Please remove acpi-support from the archive

2022-04-26 Thread Steve Langasek
Also, for powermanagement-interface:

$ reverse-depends src:powermanagement-interface -r jammy -a source
No reverse dependencies found
$ reverse-depends src:powermanagement-interface -r jammy 
No reverse dependencies found
$

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970464

Title:
  Please remove acpi-support from the archive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/acpi-support/+bug/1970464/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1970464] Re: Please remove acpi-support from the archive

2022-04-26 Thread Steve Langasek
All of the metapackages have been uploaded to the queue.  Will review
this again once they've migrated to the kinetic release pocket.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970464

Title:
  Please remove acpi-support from the archive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/acpi-support/+bug/1970464/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1970227] Update Released

2022-04-26 Thread Steve Langasek
The verification of the Stable Release Update for distro-info-data has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970227

Title:
  Add Kinetic to distro-info-data

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/distro-info-data/+bug/1970227/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1970042] Re: livepatch

2022-04-26 Thread Steve Langasek
*** This bug is a duplicate of bug 1969386 ***
https://bugs.launchpad.net/bugs/1969386

** This bug has been marked a duplicate of bug 1969394
   'Settings & Livepatch' button opens 'settings' tab, not livepatch

** This bug is no longer a duplicate of bug 1969394
   'Settings & Livepatch' button opens 'settings' tab, not livepatch
** This bug has been marked a duplicate of bug 1969386
   Hints about enabling livepatch even if the service isn't available

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970042

Title:
  livepatch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1970042/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969396] Re: Can't use Right Alt as compose key with English (Dvorak, alt. intl.) layout

2022-04-25 Thread Steve Langasek
On Wed, Apr 20, 2022 at 03:58:40AM -, Gunnar Hjalmarsson wrote:
> Alternate Charters Key to None + Compose key to Right Alt
> -
> $ gsettings get org.gnome.desktop.input-sources xkb-options
> ['lv3:ralt_alt', 'compose:ralt']

> Right Alt according to xev: Multi_key

xev also returns Multi_key for me here, but it doesn't actually *work* as a
compose key with the above values.  The lv3:ralt_alt conflicts in some
fashion and only when I remove it from the settings do I get Compose key
functionality.

So if your assertion is that the gsettings values are correct and it's a bug
in how xkeyboard-config interprets/applies those settings, then it's not a
bug in gnome-control-center.  However if this is a wrong setting to be set
in gsettings, it's a gnome-control-center bug.


** Changed in: gnome-control-center (Ubuntu)
   Status: Incomplete => New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969396

Title:
  Can't use Right Alt as compose key with English (Dvorak, alt. intl.)
  layout

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1969396/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1968929] Update Released

2022-04-25 Thread Steve Langasek
The verification of the Stable Release Update for gdm3 has completed
successfully and the package is now being released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968929

Title:
  Missing Wayland login option on NVIDIA systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1968929/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1970066] Re: using snap after fresh 22.04 install with (encrypted) ZFS breaks APT, snapd

2022-04-24 Thread Steve Langasek
As root, what does ls -la /var/lib/dpkg show?

** Changed in: snapd (Ubuntu Jammy)
   Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970066

Title:
  using snap after fresh 22.04 install with (encrypted) ZFS breaks APT,
  snapd

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1970066] Re: using snap after fresh 22.04 install with (encrypted) ZFS breaks APT, snapd

2022-04-24 Thread Steve Langasek
** Changed in: snapd (Ubuntu Jammy)
   Importance: Undecided => Critical

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970066

Title:
  using snap after fresh 22.04 install with (encrypted) ZFS breaks APT,
  snapd

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1970069] Re: Annoying boot messages interfering with splash screen, since upgrading to Jammy

2022-04-23 Thread Steve Langasek
This is a bug.  The 'splash' option is configured, but text messages
from the kernel are being shown.

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970069

Title:
  Annoying boot messages interfering with splash screen, since upgrading
  to Jammy

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969979] Re: UC22 armhf Raspi images are failing to build

2022-04-22 Thread Steve Langasek
Hello William, or anyone else affected,

Accepted ubuntu-image into jammy-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/ubuntu-
image/2.2+22.04ubuntu3 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: ubuntu-image (Ubuntu Jammy)
   Status: New => Fix Committed

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969979

Title:
  UC22 armhf Raspi images are failing to build

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-image/+bug/1969979/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969623] Re: Creation of SNMPv3 user broken (Jammy/22.04)

2022-04-22 Thread Steve Langasek
Hello Sascha, or anyone else affected,

Accepted net-snmp into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/net-
snmp/5.9.1+dfsg-1ubuntu2.1 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: net-snmp (Ubuntu Jammy)
   Status: In Progress => Fix Committed

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969623

Title:
  Creation of SNMPv3 user broken (Jammy/22.04)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/net-snmp/+bug/1969623/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969752] Re: oss4-dkms '-mfloat-abi=hard' build failure

2022-04-22 Thread Steve Langasek
> We may experience performance regressions in oss4, but
> getting rid of '-mfloat-abi=hard’ provides a better
> compatibility across all the supported architectures and toolchains.

Where, according to the newly-uploaded package, "supported
architectures" are being reduced to amd64-only.  That is not normally a
change we allow in SRU.  Please elaborate why it is appropriate to
reduce the architecture support in this package.

** Changed in: oss4 (Ubuntu Jammy)
   Status: In Progress => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969752

Title:
  oss4-dkms '-mfloat-abi=hard' build failure

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969960] Re: Jammy's /etc/os-release missing LTS string in VERSION

2022-04-22 Thread Steve Langasek
Hello Paride, or anyone else affected,

Accepted base-files into jammy-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/base-
files/12ubuntu4.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: base-files (Ubuntu Jammy)
   Status: Triaged => Fix Committed

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969960

Title:
  Jammy's /etc/os-release missing LTS string in VERSION

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1969960/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1491205] Re: mathematica-fonts returns 404 when attempting to download fonts

2022-04-22 Thread Steve Langasek
** Changed in: mathematica-fonts (Ubuntu)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1491205

Title:
  mathematica-fonts returns 404 when attempting to download fonts

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mathematica-fonts/+bug/1491205/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1968757] Re: New icon still not present on Ubuntu Desktop Guide

2022-04-22 Thread Steve Langasek
Hello Marcos, or anyone else affected,

Accepted ubuntu-docs into jammy-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/ubuntu-docs/22.04.5
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: ubuntu-docs (Ubuntu Jammy)
   Status: In Progress => Fix Committed

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968757

Title:
  New icon still not present on Ubuntu Desktop Guide

To manage notifications about this bug go to:
https://bugs.launchpad.net/help.ubuntu.com/+bug/1968757/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969848] Re: Update gtksourceview5 to 5.4.1

2022-04-22 Thread Steve Langasek
Hello Jeremy, or anyone else affected,

Accepted gtksourceview5 into jammy-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/gtksourceview5/5.4.1-0ubuntu1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: gtksourceview5 (Ubuntu Jammy)
   Status: In Progress => Fix Committed

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969848

Title:
  Update gtksourceview5 to 5.4.1

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969970] Re: ubuntu jammy 22.04 iso: unable to find a live file system on the network

2022-04-22 Thread Steve Langasek
This is going to be a casper and/or livecd-rootfs issue, so reassigning.

What I don't understand is that neither the blkid output nor the contents of 
/cdrom/.disk/casper-uuid-generic appear to match what I have here:
$ blkid ~/devel/iso/ubuntu-22.04-live-server-amd64.iso 
/home/vorlon/devel/iso/ubuntu-22.04-live-server-amd64.iso: BLOCK_SIZE="2048" 
UUID="2022-04-21-06-14-25-00" LABEL="Ubuntu-Server 22.04 LTS amd64" 
TYPE="iso9660" PTUUID="c84e0225-4be7-447a-9fa1-ebf040bdc01f" PTTYPE="gpt"
$ cat /mnt/.disk/casper-uuid-generic 
ba2335f2-81b6-46b2-a037-549fe52a8261
$ 

I don't know how blkid is figuring a UUID for an iso9660 filesystem, but
here it is the timestamp of the image on the server, which is preserved
by wget.  It's surprising that yours has a timestamp months in the
past...

** Project changed: ubuntu-cdimage => casper (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969970

Title:
  ubuntu jammy 22.04 iso: unable to find a live file system on the
  network

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1968929] Re: Missing Wayland login option on NVIDIA systems

2022-04-22 Thread Steve Langasek
Hello Marcos, or anyone else affected,

Accepted gdm3 into jammy-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/gdm3/42.0-1ubuntu7 in
a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
jammy to verification-done-jammy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-jammy. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: gdm3 (Ubuntu Jammy)
   Status: In Progress => Fix Committed

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968929

Title:
  Missing Wayland login option on NVIDIA systems

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1968929/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1968067] Re: upgrade_lts_contract.py exception on impish and later

2022-04-21 Thread Steve Langasek
** Description changed:

  [Impact]
- When users are upgrading their machines, we run the upgrade_lts_contract 
script to ensure that the services that were unable will keep being enable in 
the new ubuntu release the users are upgraded too.
+ When users are upgrading their machines, we run the upgrade_lts_contract 
script to ensure that the services that were enabled will keep being enabled in 
the new ubuntu release the users are upgraded to.
  
  Currently, if the user upgrades directly from Focal to Jammy, the script
  will error out because we are missing the entries for Focal and Impish
  on that script.
  
  Therefore, even though we might not have full support for some services
  in Jammy yet, we should not error out on that script and allow it to
  complete;
- 
  
  [Test Case]
  To reproduce the bug: follow these steps:
  
  1. Launch a jammy machine
  2. Attach to a valid UA token
  3. run `sudo python3 /usr/lib/ubuntu-advantage/upgrade_lts_contract.py`
  
  And to verify that the fix works:
  
  1. Upgrade UA to version 27.8
  2. re-run `sudo python3 /usr/lib/ubuntu-advantage/upgrade_lts_contract.py` 
and confirm no errors are raised
- 
  
  [Regression Potential]
  We are just adding the new releases into our support dict and providing 
better error messages if that problem happens again in the future. Therefore, 
we don't believe we have a big regression issue here.
  
  [Original Description]
  
  See this error
  https://errors.ubuntu.com/problem/864d1a4d38167a7b009ce993125030b58eb012d5
  
  When upgrading from focal -> impish or from impish -> jammy, a KeyError
  will occur in the upgrade_lts_contract.py script from ubuntu-advantage-
  tools. This happens because that script has not been kept up-to-date
  with new ubuntu series names since groovy.
  
  We plan to fix this bug in our next release of ubuntu-advantage-tools,
  which will be version 27.8 and should occur within the next month.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1968067

Title:
  upgrade_lts_contract.py exception on impish and later

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1968067/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969439] Re: Plugins not available

2022-04-20 Thread Steve Langasek
** Description changed:

  * Impact
  
  Shotwell doesn't list any plugin as available
  
  = Test Case
  
  - Start shotwell
- - Go to preference
+ - Go to Edit->Preferences
  - Select the plugins tab
  
  The list should lists plugins in the categories with checkboxes to
  enable/disable them on the left column
- 
  
  * Regression Potential
  
  The patch is changing the LIB definition so it could lead to issue
  finding other assets though in practice the value was null before the
  fix and the plugin seems to be the only code relying on that resource
  definition so the risk is limited
- 
  
  -
  
  Just installed 22.04 and Shotwell but I cannot enable any plugin, no one
  available.
  
  May be a lib path error?
  
  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: shotwell 0.30.14-1ubuntu5 [modified: 
usr/share/applications/shotwell.desktop]
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: pass
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 19 11:04:59 2022
  InstallationDate: Installed on 2022-04-16 (2 days ago)
  InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Daily amd64 (20220416)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: shotwell
  UpgradeStatus: No upgrade log present (probably fresh install)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969439

Title:
  Plugins not available

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969464] Re: Ubuntu 22.04 fails update Unpacking casper (1.470) over (1.468)

2022-04-20 Thread Steve Langasek
If casper was left installed on the target system by the installer,
that's an installer bug.

Can you please run 'apport-collect -p ubiquity 1969464' from the
affected system so we can see the installer logs?

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

** Tags added: rls-jj-incoming

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969464

Title:
  Ubuntu 22.04 fails update Unpacking casper (1.470) over (1.468)

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969396] Re: Can't use Right Alt as compose key with English (Dvorak, alt. intl.) layout

2022-04-19 Thread Steve Langasek
> And AFAICT gnome-control-center sets the expected XKB options,
> so it's not a g-c-c bug. Maybe an xkeyboard-config bug.

From my initial bug report:

Setting Alternate Characters Key to None, and moving the Compose Key
setting around between different options (and then back to Right Alt),
the behavior of the Right Alt key is still AltGr and not Compose.

So no, gnome-control-center was not setting the expected XKB options
either.

** Also affects: gnome-control-center (Ubuntu)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969396

Title:
  Can't use Right Alt as compose key with English (Dvorak, alt. intl.)
  layout

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1969396/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1891238] Re: [RM] neutron-fwaas, vmware-nsx

2022-04-19 Thread Steve Langasek
Removing packages from jammy:
neutron-fwaas 1:16.0.0+git2022033113.de8a4d4cf-0ubuntu1 in jammy
neutron-fwaas-common 1:16.0.0+git2022033113.de8a4d4cf-0ubuntu1 
in jammy amd64
neutron-fwaas-common 1:16.0.0+git2022033113.de8a4d4cf-0ubuntu1 
in jammy arm64
neutron-fwaas-common 1:16.0.0+git2022033113.de8a4d4cf-0ubuntu1 
in jammy armhf
neutron-fwaas-common 1:16.0.0+git2022033113.de8a4d4cf-0ubuntu1 
in jammy i386
neutron-fwaas-common 1:16.0.0+git2022033113.de8a4d4cf-0ubuntu1 
in jammy ppc64el
neutron-fwaas-common 1:16.0.0+git2022033113.de8a4d4cf-0ubuntu1 
in jammy riscv64
neutron-fwaas-common 1:16.0.0+git2022033113.de8a4d4cf-0ubuntu1 
in jammy s390x
python3-neutron-fwaas 1:16.0.0+git2022033113.de8a4d4cf-0ubuntu1 
in jammy amd64
python3-neutron-fwaas 1:16.0.0+git2022033113.de8a4d4cf-0ubuntu1 
in jammy arm64
python3-neutron-fwaas 1:16.0.0+git2022033113.de8a4d4cf-0ubuntu1 
in jammy armhf
python3-neutron-fwaas 1:16.0.0+git2022033113.de8a4d4cf-0ubuntu1 
in jammy i386
python3-neutron-fwaas 1:16.0.0+git2022033113.de8a4d4cf-0ubuntu1 
in jammy ppc64el
python3-neutron-fwaas 1:16.0.0+git2022033113.de8a4d4cf-0ubuntu1 
in jammy riscv64
python3-neutron-fwaas 1:16.0.0+git2022033113.de8a4d4cf-0ubuntu1 
in jammy s390x
Comment: Ubuntu-specific, obsolete, unsupported; LP: #1891238
1 package successfully removed.


** Changed in: neutron-fwaas (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891238

Title:
  [RM] neutron-fwaas, vmware-nsx

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/networking-odl/+bug/1891238/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1891238] Re: [RM] neutron-fwaas, vmware-nsx

2022-04-19 Thread Steve Langasek
Removing packages from jammy:
vmware-nsx 17.0.0+git2021120910.0253265f7-0ubuntu1 in jammy
python3-vmware-nsx 17.0.0+git2021120910.0253265f7-0ubuntu1 in 
jammy amd64
python3-vmware-nsx 17.0.0+git2021120910.0253265f7-0ubuntu1 in 
jammy arm64
python3-vmware-nsx 17.0.0+git2021120910.0253265f7-0ubuntu1 in 
jammy armhf
python3-vmware-nsx 17.0.0+git2021120910.0253265f7-0ubuntu1 in 
jammy i386
python3-vmware-nsx 17.0.0+git2021120910.0253265f7-0ubuntu1 in 
jammy ppc64el
python3-vmware-nsx 17.0.0+git2021120910.0253265f7-0ubuntu1 in 
jammy riscv64
python3-vmware-nsx 17.0.0+git2021120910.0253265f7-0ubuntu1 in 
jammy s390x
vmware-nsx-common 17.0.0+git2021120910.0253265f7-0ubuntu1 in 
jammy amd64
vmware-nsx-common 17.0.0+git2021120910.0253265f7-0ubuntu1 in 
jammy arm64
vmware-nsx-common 17.0.0+git2021120910.0253265f7-0ubuntu1 in 
jammy armhf
vmware-nsx-common 17.0.0+git2021120910.0253265f7-0ubuntu1 in 
jammy i386
vmware-nsx-common 17.0.0+git2021120910.0253265f7-0ubuntu1 in 
jammy ppc64el
vmware-nsx-common 17.0.0+git2021120910.0253265f7-0ubuntu1 in 
jammy riscv64
vmware-nsx-common 17.0.0+git2021120910.0253265f7-0ubuntu1 in 
jammy s390x
Comment: Ubuntu-specific, depends on obsolete neutron-fwaas; LP: #1891238
1 package successfully removed.


** Changed in: vmware-nsx (Ubuntu)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1891238

Title:
  [RM] neutron-fwaas, vmware-nsx

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/networking-odl/+bug/1891238/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1969396] Re: gnome-control-center compose key setting does not set compose key

2022-04-19 Thread Steve Langasek
On Tue, Apr 19, 2022 at 06:42:15AM -, Gunnar Hjalmarsson wrote:
> Is 'lv3:none' a valid XKB option?

I have no idea.  But until I set it, I was seeing conflicting lv3
options.

> I can't reproduce your problem on my jammy. Even if I set "Alternate
> Characters Key" to "Right Alt" in Settings, the 'compose:ralt' option
> overrides it and RightAlt/AltGr works as a compose key. That's true also
> if I use the Swedish layout, which — unlike the basic us layout — sets
> 'lv3:ralt_switch' by default in the background.

> More questions:

> 1. Which keyboard layout are you using?

English (Dvorak, alt. intl.)

> 2. What happens if you drop the 'lv3:none' option, so you only have:
> ['altwin:menu', 'compose:ralt']

This works.

> ? While you need to set 'altwin:menu' elsewhere (Tweaks?), setting
> 'compose:ralt' can be accomplished from Settings:

> * Disable "Alternate Characters Key" by switching to "Use layout
> default"

> * Select "Right Alt" for "Compose Key"

That was not the behavior here.  *Now*, toggling Alternate Characters Key is
not having any effect; but previously, choosing 'Use layout default' was
giving me lv3:ralt_alt, lv3:switch.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969396

Title:
  gnome-control-center compose key setting does not set compose key

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1969396/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1969396] Re: gnome-control-center compose key setting does not set compose key

2022-04-18 Thread Steve Langasek
Was able to force the Compose key to work by running the following
command:

gsettings set org.gnome.desktop.input-sources xkb-options
"['altwin:menu', 'compose:ralt', 'lv3:none']"

seems impossible to get to this configuration via the UI.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1969396

Title:
  gnome-control-center compose key setting does not set compose key

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1969396/+subscriptions


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

  1   2   3   4   5   6   7   8   9   10   >