[Bug 1967629] Re: gnome-sound-recorder 42 is not wanted for jammy

[Iain Lane]

laney@sherwood (main|…)> ./remove-package -s jammy-proposed -m "Not wanted in 
jammy: 
https://bugs.launchpad.net/ubuntu/+source/gnome-sound-recorder/+bug/1967629; 
gnome-sound-recorder
Removing packages from jammy-proposed:
gnome-sound-recorder 42.0-1 in jammy
gnome-sound-recorder 42.0-1 in jammy amd64
gnome-sound-recorder 42.0-1 in jammy arm64
gnome-sound-recorder 42.0-1 in jammy armhf
gnome-sound-recorder 42.0-1 in jammy i386
gnome-sound-recorder 42.0-1 in jammy ppc64el
gnome-sound-recorder 42.0-1 in jammy riscv64
gnome-sound-recorder 42.0-1 in jammy s390x
Comment: Not wanted in jammy: 
https://bugs.launchpad.net/ubuntu/+source/gnome-sound-recorder/+bug/1967629
Remove [y|N]? y
1 package successfully removed.


** Changed in: gnome-sound-recorder (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/1967629

Title:
  gnome-sound-recorder 42 is not wanted for jammy

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


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

[Bug 1957186] Re: librsvg fails to build on arm64

[Iain Lane]

** Changed in: rustc (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/1957186

Title:
  librsvg fails to build on arm64

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


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

[Bug 1957186] Re: librsvg fails to build on arm64

[Iain Lane]

Thanks, I looked for bugs against librsvg but didn't check rustc!
Michael said that an upload including it was planned for next week
anyway so I jumped the gun :-).

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

Title:
  librsvg fails to build on arm64

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


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

[Bug 1942437] Re: [UIFe] Impish wallpapers

[Iain Lane]

go for it!

** Changed in: ubuntu-wallpapers (Ubuntu)
   Status: New => Triaged

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

Title:
  [UIFe] Impish wallpapers

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


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

Re: [Bug 1925314] Re: no eject media message after install xubuntu

[Iain Lane]

On Thu, Sep 09, 2021 at 04:40:38PM -, Brian Murray wrote:
> Has anybody tested this with an Ubuntu impish image?

Yeah, I just installed a laptop with today's ISO and I didn't get the 
message.

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]

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

Title:
  no eject media message after install xubuntu

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


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

[Bug 1942911] Re: [FFe] Support wayland user sessions for Nvidia machines

[Iain Lane]

Yeah, please go ahead. We should get this in with as much time as
possible.

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

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

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

Title:
  [FFe] Support wayland user sessions for Nvidia machines

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


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

[Bug 1843049] Re: boxer-data: please keep it out from eoan

[Iain Lane]

I've applied that diff from #3

** Changed in: boxer-data (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/1843049

Title:
  boxer-data: please keep it out from eoan

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


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

[Bug 1890540] Re: [MIR] oem-somerville-squirtle-meta

[Iain Lane]

Hello Kai-Chuan, or anyone else affected,

Accepted oem-somerville-squirtle-meta into focal-proposed. The package
will build now and be available at
https://launchpad.net/ubuntu/+source/oem-somerville-squirtle-
meta/20.04~ubuntu1 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.

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

** Package changed: ubuntu => oem-somerville-squirtle-meta (Ubuntu)

** Also affects: oem-somerville-squirtle-meta (Ubuntu Focal)
   Importance: Undecided
   Status: New

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

** Changed in: oem-somerville-squirtle-meta (Ubuntu Focal)
   Status: New => In Progress

** Changed in: oem-somerville-squirtle-meta (Ubuntu Focal)
 Assignee: (unassigned) => Shih-Yuan Lee (fourdollars)

** Changed in: oem-somerville-squirtle-meta (Ubuntu Focal)
 Assignee: Shih-Yuan Lee (fourdollars) => Yuan-Chen Cheng (ycheng-twn)

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

Title:
  [MIR] oem-somerville-squirtle-meta

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


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

[Bug 1924726] Re: [MIR] oem-sutton.newell-aelfwine-meta

[Iain Lane]

Hello OEM, or anyone else affected,

Accepted oem-sutton.newell-aelfwine-meta into focal-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/oem-sutton.newell-aelfwine-
meta/20.04~ubuntu1 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.

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

** Package changed: ubuntu => oem-sutton.newell-aelfwine-meta (Ubuntu)

** Also affects: oem-sutton.newell-aelfwine-meta (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: oem-sutton.newell-aelfwine-meta (Ubuntu)
   Status: Confirmed => Won't Fix

** Changed in: oem-sutton.newell-aelfwine-meta (Ubuntu Focal)
   Status: New => In Progress

** Changed in: oem-sutton.newell-aelfwine-meta (Ubuntu Focal)
 Assignee: (unassigned) => Shih-Yuan Lee (fourdollars)

** Changed in: oem-sutton.newell-aelfwine-meta (Ubuntu Focal)
 Assignee: Shih-Yuan Lee (fourdollars) => Bin Li (binli)

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

Title:
  [MIR] oem-sutton.newell-aelfwine-meta

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


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

[Bug 1924725] Re: [MIR] oem-sutton.newell-aekerley-meta

[Iain Lane]

Hello OEM, or anyone else affected,

Accepted oem-sutton.newell-aekerley-meta into focal-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/oem-sutton.newell-aekerley-
meta/20.04~ubuntu1 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.

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

** Package changed: ubuntu => oem-sutton.newell-aekerley-meta (Ubuntu)

** Also affects: oem-sutton.newell-aekerley-meta (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: oem-sutton.newell-aekerley-meta (Ubuntu)
   Status: Confirmed => Won't Fix

** Changed in: oem-sutton.newell-aekerley-meta (Ubuntu Focal)
 Assignee: (unassigned) => Shengyao Xue (xueshengyao)

** Changed in: oem-sutton.newell-aekerley-meta (Ubuntu Focal)
   Status: New => In Progress

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

Title:
  [MIR] oem-sutton.newell-aekerley-meta

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


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

[Bug 1894946] Re: [MIR] oem-somerville-octillery-meta

[Iain Lane]

Hello Cyrus, or anyone else affected,

Accepted oem-somerville-octillery-meta into focal-proposed. The package
will build now and be available at
https://launchpad.net/ubuntu/+source/oem-somerville-octillery-
meta/20.04~ubuntu1 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.

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

** Package changed: ubuntu => oem-somerville-octillery-meta (Ubuntu)

** Also affects: oem-somerville-octillery-meta (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: oem-somerville-octillery-meta (Ubuntu Focal)
 Assignee: (unassigned) => Kai-Chuan Hsieh (kchsieh)

** Changed in: oem-somerville-octillery-meta (Ubuntu Focal)
   Status: New => In Progress

** Changed in: oem-somerville-octillery-meta (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/1894946

Title:
  [MIR] oem-somerville-octillery-meta

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


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

[Bug 1920204] Re: [MIR] oem-somerville-warcraft-intel-meta

[Iain Lane]

Hello Shih-Yuan, or anyone else affected,

Accepted oem-somerville-warcraft-intel-meta into focal-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/oem-somerville-warcraft-intel-
meta/20.04~ubuntu1 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.

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

** Package changed: ubuntu => oem-somerville-warcraft-intel-meta
(Ubuntu)

** Also affects: oem-somerville-warcraft-intel-meta (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: oem-somerville-warcraft-intel-meta (Ubuntu Focal)
 Assignee: (unassigned) => Cyrus Lien (cyruslien)

** Changed in: oem-somerville-warcraft-intel-meta (Ubuntu)
   Status: Confirmed => Won't Fix

** Changed in: oem-somerville-warcraft-intel-meta (Ubuntu Focal)
   Status: New => In Progress

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

Title:
  [MIR] oem-somerville-warcraft-intel-meta

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


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

[Bug 1937243] Re: [MIR] oem-somerville-varys-meta

[Iain Lane]

Hello OEM, or anyone else affected,

Accepted oem-somerville-varys-meta into focal-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source/oem-
somerville-varys-meta/20.04~ubuntu1 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.

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

** Package changed: ubuntu => oem-somerville-varys-meta (Ubuntu)

** Also affects: oem-somerville-varys-meta (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: oem-somerville-varys-meta (Ubuntu Focal)
 Assignee: (unassigned) => Shih-Yuan Lee (fourdollars)

** Changed in: oem-somerville-varys-meta (Ubuntu Focal)
   Status: New => In Progress

** Changed in: oem-somerville-varys-meta (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/1937243

Title:
  [MIR] oem-somerville-varys-meta

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


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

[Bug 1934936] Re: package libwind0-heimdal 7.7.0+dfsg-2build1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is different from other

[Iain Lane]

It's probably a bug in pkgstripfiles, will confirm

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

Title:
  package libwind0-heimdal 7.7.0+dfsg-2build1 failed to install/upgrade:
  trying to overwrite shared
  '/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is
  different from other instances of package libwind0-heimdal:i386

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


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

[Bug 1934936] Re: package libwind0-heimdal 7.7.0+dfsg-2build1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is different from other

[Iain Lane]

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

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

Title:
  package libwind0-heimdal 7.7.0+dfsg-2build1 failed to install/upgrade:
  trying to overwrite shared
  '/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is
  different from other instances of package libwind0-heimdal:i386

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


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

[Bug 1934936] Re: package libwind0-heimdal 7.7.0+dfsg-2build1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is different from other

[Iain Lane]

welp, this is more sensible as a thing to look at:

laney@raleigh> diff -u <(zcat changelog.Debian.gz-amd64) <(zcat 
changelog.Debian.gz-i386)
--- /proc/self/fd/112021-07-16 11:22:45.935902600 +0100
+++ /proc/self/fd/202021-07-16 11:22:45.939902539 +0100
@@ -95,4 +95,4 @@
 
  -- Brian May   Wed, 26 Apr 2017 19:38:20 +1000
 
-# For older changelog entries, run 'apt-get changelog libwind0-heimdal'
+# For older changelog entries, run 'apt-get changelog libheimbase1-heimdal'

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

Title:
  package libwind0-heimdal 7.7.0+dfsg-2build1 failed to install/upgrade:
  trying to overwrite shared
  '/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is
  different from other instances of package libwind0-heimdal:i386

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


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

[Bug 1934936] Re: package libwind0-heimdal 7.7.0+dfsg-2build1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is different from other

[Iain Lane]

Yeah I'm getting this too on dist-upgrade, now that heimdal migrated to
impish.

laney@raleigh> diff -u <(xxd changelog.Debian.gz-amd64) <(xxd 
changelog.Debian.gz-i386)
--- /proc/self/fd/112021-07-16 11:20:29.165989264 +0100
+++ /proc/self/fd/202021-07-16 11:20:29.169989204 +0100
@@ -97,5 +97,5 @@
 0600: 8a9e 51d4 4f3c 479b 631a d7fa aea8 3049  ..Q.Ohttps://bugs.launchpad.net/bugs/1934936

Title:
  package libwind0-heimdal 7.7.0+dfsg-2build1 failed to install/upgrade:
  trying to overwrite shared
  '/usr/share/doc/libwind0-heimdal/changelog.Debian.gz', which is
  different from other instances of package libwind0-heimdal:i386

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


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

[Bug 1932559] Re: [MIR] oem-somerville-gendry-meta

[Iain Lane]

Hello OEM, or anyone else affected,

Accepted oem-somerville-gendry-meta into focal-proposed. The package
will build now and be available at
https://launchpad.net/ubuntu/+source/oem-somerville-gendry-
meta/20.04~ubuntu1 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.

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

** Also affects: Ubuntu Focal
   Importance: Undecided
   Status: New

** Changed in: ubuntu
   Status: Confirmed => Won't Fix

** Also affects: oem-somerville-gendry-meta (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: Ubuntu Focal
   Status: New => Fix Released

** Changed in: oem-somerville-gendry-meta (Ubuntu)
   Status: New => Won't Fix

** Changed in: oem-somerville-gendry-meta (Ubuntu Focal)
   Status: New => Confirmed

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

Title:
  [MIR] oem-somerville-gendry-meta

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


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

[Bug 1930359] Re: glib2.0: Uninitialised memory is written to gschema.compiled, failure to parse this file leads to gdm, gnome-shell failing to start

[Iain Lane]

> Looks like both of us sponsored it for the queue. I'd appreciate
rejecting either one of them.

I pushed to the VCS[0] at the same time as sponsoring, so I'll reject
the other one which doesn't quite match up with it.

[0] https://salsa.debian.org/gnome-
team/glib/-/commits/ubuntu/2.64.6-1_ubuntu20.04.4/

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

Title:
  glib2.0: Uninitialised memory is written to gschema.compiled, failure
  to parse this file leads to gdm, gnome-shell failing to start

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

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

[Bug 1930359] Re: glib2.0: Uninitialised memory is written to gschema.compiled, failure to parse this file leads to gdm, gnome-shell failing to start

[Iain Lane]

Thanks, sponsored to the queue

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

Title:
  glib2.0: Uninitialised memory is written to gschema.compiled, failure
  to parse this file leads to gdm, gnome-shell failing to start

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

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

Re: [Bug 1934505] Re: gdb 11 doesn't work on impish/s390x: internal-error: displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, thread_info*, CORE_ADDR&): Assertion `gdbarch_data->num_

[Iain Lane]

On Wed, Jul 07, 2021 at 08:30:32AM -, Matthias Klose wrote:
> fixed in 11.0.90.20210705-0ubuntu2

yep, thanks for reproducing and forwarding!

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]

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

Title:
  gdb 11 doesn't work on impish/s390x: internal-error:
  displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*,
  thread_info*, CORE_ADDR&): Assertion
  `gdbarch_data->num_disp_step_buffers > 0' failed.

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

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

[Bug 1934505] Re: gdb 11 doesn't work on impish/s390x: internal-error: displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, thread_info*, CORE_ADDR&): Assertion `gdbarch_data->num_disp

[Iain Lane]

** Summary changed:

- gdb 11 doesn't work on impish: internal-error: displaced_step_prepare_status 
linux_displaced_step_prepare(gdbarch*, thread_info*, CORE_ADDR&): Assertion 
`gdbarch_data->num_disp_step_buffers > 0' failed.
+ gdb 11 doesn't work on impish/s390x: internal-error: 
displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, 
thread_info*, CORE_ADDR&): Assertion `gdbarch_data->num_disp_step_buffers > 0' 
failed.

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

Title:
  gdb 11 doesn't work on impish/s390x: internal-error:
  displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*,
  thread_info*, CORE_ADDR&): Assertion
  `gdbarch_data->num_disp_step_buffers > 0' failed.

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

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

[Bug 1934505] [NEW] gdb 11 doesn't work on impish: internal-error: displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, thread_info*, CORE_ADDR&): Assertion `gdbarch_data->num_disp_ste

[Iain Lane]

Public bug reported:

gdb doesn't work on impish/s390x at the minute. Even if you say 'no' to
both questions you still can't debug:

ubuntu@laney-bos01-s390x-2:~/glib-networking-2.66.0/build$ gdb ls
GNU gdb (Ubuntu 11.0.50.20210630-0ubuntu1) 11.0.50.20210630-git
Copyright (C) 2021 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "s390x-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ls...
(No debugging symbols found in ls)
(gdb) run
Starting program: /usr/bin/ls
/build/gdb-Ti35un/gdb-11.0.50.20210630/gdb/linux-tdep.c:2550: internal-error: 
displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, 
thread_info*, CORE_ADDR&): Assertion `gdbarch_data->num_disp_step_buffers > 0' 
failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) n

This is a bug, please report it.  For instructions, see:
.

/build/gdb-Ti35un/gdb-11.0.50.20210630/gdb/linux-tdep.c:2550: internal-error: 
displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*, 
thread_info*, CORE_ADDR&): Assertion `gdbarch_data->num_disp_step_buffers > 0' 
failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Create a core file of GDB? (y or n) n
Command aborted.
(gdb)

** Affects: gdb (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/1934505

Title:
  gdb 11 doesn't work on impish: internal-error:
  displaced_step_prepare_status linux_displaced_step_prepare(gdbarch*,
  thread_info*, CORE_ADDR&): Assertion
  `gdbarch_data->num_disp_step_buffers > 0' failed.

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

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

[Bug 1929471] Re: Shim apparently fails to run fwupd64 (hirsute regression?)

[Iain Lane]

> Chris Coulson's patch

https://github.com/rhboot/shim/pull/379

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

Title:
  Shim apparently fails to run fwupd64 (hirsute regression?)

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

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

[Bug 1928931] Re: German strings in deja-dup.mo for en_GB

[Iain Lane]

Hmm no, it needs removing first, my upload got rejected.

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

Title:
  German strings in deja-dup.mo for en_GB

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-pack-gnome-en/+bug/1928931/+subscriptions

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

[Bug 1928931] Re: German strings in deja-dup.mo for en_GB

[Iain Lane]

Okay, done. I think: remove this, let the removal publish, accept the
new one.

Hopefully the ageing period can be waived on that.

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

Title:
  German strings in deja-dup.mo for en_GB

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-pack-gnome-en/+bug/1928931/+subscriptions

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

[Bug 1928931] Re: German strings in deja-dup.mo for en_GB

[Iain Lane]

Wait, isn't the version wrong? 1:21.10+20210415ubuntu1.

I'm going to re-upload to the queue with 1:21.04.

Also, can we just run a langpack export for impish to fix this there
please? The version is greater than hirsute's now so I can't just copy
up.

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

Title:
  German strings in deja-dup.mo for en_GB

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-pack-gnome-en/+bug/1928931/+subscriptions

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

[Bug 1918044] Re: (Update libgweather to 3.36.2) Weather forecast and info is not available anymore

[Iain Lane]

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

** Also affects: gnome-weather (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Changed in: gnome-weather (Ubuntu)
   Status: Confirmed => Fix Released

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

** Changed in: gnome-weather (Ubuntu Focal)
 Assignee: (unassigned) => Iain Lane (laney)

** Changed in: libgweather (Ubuntu Focal)
 Assignee: (unassigned) => Iain Lane (laney)

** Tags removed: rls-ff-incoming

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

Title:
  (Update libgweather to 3.36.2) Weather forecast and info is not
  available anymore

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

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

[Bug 1918855] Re: Xorg xserver got signal 6 to abort

[Iain Lane]

** Changed in: mesa (Ubuntu Focal)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in: mesa (Ubuntu Hirsute)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  Xorg xserver got signal 6 to abort

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

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

[Bug 1925742] Re: Recent iCloud versions trigger an issue in IMAP x

[Iain Lane]

** Changed in: evolution-data-server (Ubuntu Hirsute)
 Assignee: (unassigned) => Sebastien Bacher (seb128)

** Tags removed: rls-hh-incoming

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

Title:
  Recent iCloud versions trigger an issue in IMAP x

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1925742/+subscriptions

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

[Bug 1926771] Re: [SRU] Hard dependency on desktop-file-utils not declared

[Iain Lane]

** Changed in: wslu (Ubuntu Hirsute)
 Assignee: (unassigned) => Patrick Wu (callmepk)

** Changed in: wslu (Ubuntu Focal)
 Assignee: (unassigned) => Patrick Wu (callmepk)

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

Title:
  [SRU] Hard dependency on desktop-file-utils not declared

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

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

[Bug 1931547] Re: DisplayLink displays are black after Mesa update

[Iain Lane]

Timo, please can you take care of this one, sounds like a regression?

** Changed in: xorg-server (Ubuntu)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in: xorg-server (Ubuntu Focal)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in: xorg-server (Ubuntu Hirsute)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  DisplayLink displays are black after Mesa update

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1931547/+subscriptions

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

[Bug 1931602] Re: [apparmor] Segfault in logs with apparmor enabled

[Iain Lane]

(Just assigning to clean the report)

** Changed in: firefox (Ubuntu)
 Assignee: (unassigned) => Dariusz Gadomski (dgadomski)

** Changed in: firefox (Ubuntu Focal)
 Assignee: (unassigned) => Dariusz Gadomski (dgadomski)

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

Title:
  [apparmor] Segfault in logs with apparmor enabled

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

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

[Bug 1931603] Re: [apparmor] Unable to show Downloads with apparmor enabled

[Iain Lane]

(Just assigning to clean the report)

** Changed in: firefox (Ubuntu)
 Assignee: (unassigned) => Dariusz Gadomski (dgadomski)

** Changed in: firefox (Ubuntu Focal)
 Assignee: (unassigned) => Dariusz Gadomski (dgadomski)

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

Title:
  [apparmor] Unable to show Downloads with apparmor enabled

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

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

[Bug 1932311] Re: migrate to llvm 12

[Iain Lane]

** Changed in: mesa (Ubuntu Focal)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

** Changed in: mesa (Ubuntu Hirsute)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  migrate to llvm 12

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

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

[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm

[Iain Lane]

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

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

** Changed in: gnome-shell (Ubuntu Groovy)
   Status: New => Invalid

** Changed in: gnome-shell (Ubuntu Hirsute)
   Status: New => Invalid

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

** Changed in: dbus (Ubuntu Hirsute)
   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/1871538

Title:
  dbus timeout-ed during an upgrade, taking services down including gdm

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

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

[Bug 1925837] Re: [Wayland] Sharing indicator window is not frameless

[Iain Lane]

Just assigning for tracking - Olivier, please close when you do the
upload!

** Also affects: firefox (Ubuntu Impish)
   Importance: Medium
   Status: Confirmed

** Changed in: firefox (Ubuntu Impish)
 Assignee: (unassigned) => Olivier Tilloy (osomon)

** Tags removed: rls-hh-incoming

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

Title:
  [Wayland] Sharing indicator window is not frameless

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

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

[Bug 1856032] Re: Removable media icon stays on the dock after eject.

[Iain Lane]

** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu Impish)
   Importance: Low
   Status: Confirmed

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Impish)
 Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0)

** Tags removed: rls-ii-incoming

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

Title:
  Removable media icon stays on the dock after eject.

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

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

[Bug 1931701] Re: autopkgtests failures on armhf of 7.1.4

[Iain Lane]

** Changed in: libreoffice (Ubuntu Hirsute)
 Assignee: (unassigned) => Rico Tzschichholz (ricotz)

** Changed in: libreoffice (Ubuntu Impish)
 Assignee: (unassigned) => Rico Tzschichholz (ricotz)

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

Title:
  autopkgtests failures on armhf of 7.1.4

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

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

[Bug 1927264] Re: Php8.0 Transition - Please remove and blacklist php7.4

[Iain Lane]

I added hints to force the migration, and removed a php7.4 rebuild from
impish-proposed. The release pocket removal is to come once the
migration happens.

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

Title:
  Php8.0 Transition - Please remove and blacklist php7.4

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

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

[Bug 1928931] Re: German strings in deja-dup.mo for en_GB

[Iain Lane]

> hm, do we actually know *why* this happened?

Yes, someone mis-translated the strings on Launchpad. I reverted them
all now, but I don't think we have any way of dealing with that
happening again, do we?

I've just verified the SRU. I installed language-pack-gnome-en
1:21.10+20210415ubuntu1 and ran deja-dup --prompt. With the SRU the
buttons are in English again!

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

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

Title:
  German strings in deja-dup.mo for en_GB

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-pack-gnome-en/+bug/1928931/+subscriptions

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

Re: [Bug 1894619] Re: [2.82 regression] router announcements have 'forever' lifetime by default

[Iain Lane]

On Mon, Jun 21, 2021 at 05:53:41AM -, Christian Ehrhardt  wrote:
> We finally got an answer to our questions/pings (thanks Simon)
> => 
> https://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/2021q2/015134.html
> 
> TL;DR: this might be wanted new behavior :/ ?!
> 
> @Laney - You initially started this when we have faced this bug
> I wonder now if we should indeed drop our delta and resolve the fallout in 
> other places like the formerly breaking tests.
> You have back then thought deeper into this, while I only carried this delta 
> a few times.
> Therefore I'd appreciate if you could let me know what you think of that 
> reply.
> 
> P.S. Because if we drop it then I guess we better do that now than e.g.
> late in 22.04 :-)

I don't know to be honest. What do you think, does that argument make 
sense? I don't really understand why it should be different whether 
you're using DHCPv6 or SLAAC, but maybe it's just me not getting 
something right now.

If it's fine, then feel free to drop the patch and upload a NM with 
adjusted regexes (preferrably committing to the VCS too).

Cheers,

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]

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

Title:
  [2.82 regression] router announcements have 'forever' lifetime by
  default

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

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

[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm

[Iain Lane]

I filed an upstream bug with D-Bus:
https://gitlab.freedesktop.org/dbus/dbus/-/issues/337

Hopefully a maintainer there will be able to give a better opinion as to
what's going on here

** Bug watch added: gitlab.freedesktop.org/dbus/dbus/-/issues #337
   https://gitlab.freedesktop.org/dbus/dbus/-/issues/337

** Also affects: dbus via
   https://gitlab.freedesktop.org/dbus/dbus/-/issues/337
   Importance: Unknown
   Status: Unknown

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

Title:
  dbus timeout-ed during an upgrade, taking services down including gdm

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

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

[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm

[Iain Lane]

Thanks! Here's where I think the problem starts:

Ok, let's authenticate to dbus:

Jun 16 08:54:54 alan-hirsute-base-aiamcicscciaelhaktpo systemd[1]: Bus 
bus-api-system: changing state AUTHENTICATING → HELLO
...
Jun 16 08:54:54 alan-hirsute-base-aiamcicscciaelhaktpo systemd[1]: Bus 
bus-api-system: changing state HELLO → RUNNING

Right, systemd thinks it's done it at least. You can see a whole bunch
of messages being returned, the connection is working.

After a while (note this first timestamp jump; is that significant?
looks to be waiting for udev to settle I think so maybe not; could be
snapd related) we decide to do something with a Type=dbus unit:

Jun 16 08:55:25 alan-hirsute-base-aiamcicscciaelhaktpo systemd[1]: Sent message 
type=method_call sender=n/a destination=org.freedesktop.DBus 
path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=AddMatch 
cookie=1511 reply_cookie=0 signature=s error-name=n/a error-message=n/a
Jun 16 08:55:25 alan-hirsute-base-aiamcicscciaelhaktpo systemd[1]: Sent message 
type=method_call sender=n/a destination=org.freedesktop.DBus 
path=/org/freedesktop/DBus interface=org.freedesktop.DBus member=GetNameOwner 
cookie=1512 reply_cookie=0 signature=s error-name=n/a error-message=n/a

And another timestamp jump, waiting for this timeout:

Jun 16 08:55:45 alan-hirsute-base-aiamcicscciaelhaktpo dbus-daemon[711]: 
[system] Connection has not authenticated soon enough, closing it 
(auth_timeout=3ms, elapsed: 45129ms)
Jun 16 08:55:45 alan-hirsute-base-aiamcicscciaelhaktpo systemd[1]: Got message 
type=method_return sender=org.freedesktop.DBus destination=:1.4 path=n/a 
interface=n/a member=n/a cookie=42 reply_cookie=1512 signature=s error-name=n/a 
error-message=n/a

The dbus-daemon didn't think that the connection was authenticated.

The last message AFAICS received on the bus connection was:

Jun 16 08:55:00 alan-hirsute-base-aiamcicscciaelhaktpo systemd[1]: Got message 
type=method_call sender=n/a destination=org.freedesktop.systemd1 
path=/org/freedesktop/systemd1 interface=org.freedesktop.systemd1.Manager 
member=Reload cookie=1 reply_cookie=0 signature=n/a error-name=n/a 
error-message=n/a
Jun 16 08:55:00 alan-hirsute-base-aiamcicscciaelhaktpo systemd[1]: Reloading.

No smoking gun yet, at least not to me. But interesting that the last
thing which happened successfully was reloading. Can we have another go
please, with these changes vs. an upstream clean image?

  - LogLevel=debug in /etc/systemd/system.conf
  - Using the dbus 1.12.20-2ubuntu1+ppa1 from ppa:ci-train-ppa-service/4587. 
This dbus is just the one from impish backported to hirsute with verbose 
debugging turned on.
  
And then attach the full `journalctl -b ` which will 
probably be quite large. :-)

Maybe we'll get some information out of the dbus side to say what it
thinks goes wrong with the connection.

** Please note ** The "connection has not authenticated" string does not
appear in the earlier logs from Christian or Steve. It could be that
there are two bugs here, with similar symptoms that systemd loses its
connection to the system bus.

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

Title:
  dbus timeout-ed during an upgrade, taking services down including gdm

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

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

[Bug 1931088] Re: boot-and-services tests fails in impish on armhf (248.3)

[Iain Lane]

I have added a badtest hint for this version, so that the many packages
blocked by this can become unblocked. But could somebody please take a
look? The hint is only for this version so the issue will come back with
the next systemd upload unless fixed.

(I'll reset systemd to  "New" so that it appears on the rls-incoming
page)

** Tags added: rls-ii-incoming

** Changed in: auto-package-testing
   Status: New => Incomplete

** Changed in: systemd (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/1931088

Title:
  boot-and-services tests fails in impish on armhf (248.3)

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/1931088/+subscriptions

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

[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm

[Iain Lane]

That's interesting actually. I thought this was an interaction between
reloading dbus-daemon and daemon-reloading systems at the same time. But
in this cloud case, I don't think dbus is being reloaded, is it?

It's going to be next to impossible for me to look into this in detail
without being able to reproduce it or getting a bit more debug
information.

Maybe you could crank up the system log level and try to reproduce this?

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

Title:
  dbus timeout-ed during an upgrade, taking services down including gdm

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

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

Re: [Bug 1931728] Re: [scalingstack bos01] bionic (arm64) instances always fail to boot on eMAGs in this cloud

[Iain Lane]

On Mon, Jun 14, 2021 at 11:23:06PM -, dann frazier wrote:
> btw, this bug says bionic guests fails to boot - do we know if other
> Ubuntu guests versions are OK?

Thanks for your efforts looking into this so far.

Yeah, I've only seen it in bionic. I tried spawning instances for all 
current supported releases, and only bionic failed:

ubuntu@juju-806ee7-stg-proposed-migration-43:~$ for ip in $(openstack server 
list | awk -F'[= |]+' '/bos01-arm64/ { print $6 }'); do timeout 60s ssh 
-oUserKnownHostsFile=/dev/null -oStrictHostKeyChecking=no ubuntu@${ip} 
'lsb_release -a; uptime'; done
Warning: Permanently added '10.43.128.5' (ECDSA) to the list of known hosts.
Distributor ID: Ubuntu
Description:Ubuntu 16.04.7 LTS
Release:16.04
Codename:   xenial
No LSB modules are available.
 08:21:32 up 3 days, 21:33,  0 users,  load average: 0.00, 0.00, 0.00
Warning: Permanently added '10.43.128.22' (ECDSA) to the list of known hosts.
Distributor ID: Ubuntu
Description:Ubuntu Impish Indri (development branch)
Release:21.10
Codename:   impish
No LSB modules are available.
 08:21:34 up 3 days, 21:33,  0 users,  load average: 0.00, 0.00, 0.00
Warning: Permanently added '10.43.128.8' (ECDSA) to the list of known hosts.
Distributor ID: Ubuntu
Description:Ubuntu 21.04
Release:21.04
Codename:   hirsute
No LSB modules are available.
 08:21:36 up 3 days, 21:33,  0 users,  load average: 0.00, 0.00, 0.00
Warning: Permanently added '10.43.128.4' (ECDSA) to the list of known hosts.
Distributor ID: Ubuntu
Description:Ubuntu 20.10
Release:20.10
Codename:   groovy
No LSB modules are available.
 08:21:38 up 3 days, 21:33,  0 users,  load average: 0.00, 0.00, 0.00
Warning: Permanently added '10.43.128.15' (ECDSA) to the list of known hosts.
Distributor ID: Ubuntu
Description:Ubuntu 20.04.2 LTS
Release:20.04
Codename:   focal
No LSB modules are available.
 08:21:40 up 3 days, 21:33,  0 users,  load average: 0.03, 0.01, 0.00
ssh: connect to host 10.43.128.20 port 22: No route to host  # that's the 
bionic instance

and I double checked they all eneded up on an eMAG.

(I was trying all releases with a reboot loop to try to reproduce the 
other issue Julian mentioned on ubuntu-devel, but failed to cause it to 
happen ...)

What do you think about the "MDS mitigation" BIOS setting idea as a 
difference between the working/broken installations, is it worth trying 
to get IS to flip that?  Seems like it's probably sane to have it on, 
but it'd maybe be useful info.

Cheers,

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]

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

Title:
  [scalingstack bos01] bionic (arm64) instances always fail to boot on
  eMAGs in this cloud

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

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

[Bug 1931728] Re: [scalingstack bos01] bionic instances always fail to boot on eMAGs in this cloud

[Iain Lane]

** Description changed:

  This is something to do with the configuration or software versions
  running here, since we have identical hardware running in an adjacent
  cloud region but with different versions of the cloud/virt stack.
  
- When we boot bionic Ubuntu cloud images in "bos01", they always fail
- like this:
+ When we boot bionic arm64 Ubuntu cloud images in "bos01" and they land
+ on the eMAG systems, they always fail like this:
  
  ...
  [1.585611] Key type dns_resolver registered
  [1.587408] registered taskstats version 1
  [1.588913] Loading compiled-in X.509 certificates
  [1.592668] Loaded X.509 cert 'Build time autogenerated kernel key: 
4a4a555bc5fd0178c9ab722f3ae7b392f7714ac4'
  [1.598866] Loaded X.509 cert 'Canonical Ltd. Live Patch Signing: 
14df34d1a87cf37625abec039ef2bf521249b969'
  [1.605389] Loaded X.509 cert 'Canonical Ltd. Kernel Module Signing: 
88f752e560a1e0737e31163a466ad7b70a850c19'
  [1.610861] Couldn't get size: 0x800e
  [1.613413] MODSIGN: Couldn't get UEFI db list
  [1.615920] Couldn't get size: 0x800e
  [1.618256] MODSIGN: Couldn't get UEFI MokListRT
  [1.620315] Couldn't get size: 0x800e
  [1.622317] MODSIGN: Couldn't get UEFI dbx list
  [1.624446] zswap: loaded using pool lzo/zbud
  [1.628185] Key type big_key registered
  [1.629937] Key type trusted registered
  [1.632012] Key type encrypted registered
  [1.633668] AppArmor: AppArmor sha1 policy hashing enabled
  [1.635625] ima: No TPM chip found, activating TPM-bypass! (rc=-19)
  [1.638009] ima: Allocated hash algorithm: sha1
  [1.639272] evm: HMAC attrs: 0x1
  [1.640875] rtc-efi rtc-efi: setting system clock to 2021-05-11 09:28:43 
UTC (1620725323)
  [1.646247] Freeing unused kernel memory: 5824K
  [1.657870] Checked W+X mappings: passed, no W+X pages found
  [1.660250] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0005
  [1.660250]
  [1.663294] CPU: 1 PID: 1 Comm: init Not tainted 4.15.0-142-generic 
#146-Ubuntu
  [1.665939] Hardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015
  [1.668204] Call trace:
  [1.668981]  dump_backtrace+0x0/0x198
  [1.670212]  show_stack+0x24/0x30
  [1.671282]  dump_stack+0x98/0xc8
  [1.672433]  panic+0x128/0x2b0
  [1.673502]  do_exit+0x75c/0xa80
  [1.674749]  do_group_exit+0x40/0xb0
  [1.676191]  get_signal+0x114/0x6e8
  [1.677867]  do_signal+0x18c/0x240
  [1.679498]  do_notify_resume+0xd0/0x328
  [1.681302]  work_pending+0x8/0x10
  [1.682771] SMP: stopping secondary CPUs
  [1.684624] Kernel Offset: disabled
  [1.686119] CPU features: 0x04802008
  [1.687353] Memory Limit: none
  [1.688453] ---[ end Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0005
  [1.688453]
  
  Full example log: https://autopkgtest.ubuntu.com/results/autopkgtest-
  bionic/bionic/arm64/c/chromium-browser/20210511_093739_ea3f2@/log.gz
  
  We tried to get IS to roll things back to match the working bos02, but
  they said it's too different and not possible.
  
  The working cloud is running Mitaka from the cloud archive on Xenial (qemu 
2.5)
  The broken cloud is running Queens from the cloud archive on Xenial (qemu 
2.11)
  
  The other thing someone suggested we try is that MDS mitigation is
  enabled in the broken cloud, so we could disable it. No idea if that
  makes sense tbh.
  
  That's about all we have right now.

** Summary changed:

- [scalingstack bos01] bionic instances always fail to boot on eMAGs in this 
cloud
+ [scalingstack bos01] bionic (arm64) instances always fail to boot on eMAGs in 
this cloud

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

Title:
  [scalingstack bos01] bionic (arm64) instances always fail to boot on
  eMAGs in this cloud

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

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

[Bug 1931728] [NEW] [scalingstack bos01] bionic (arm64) instances always fail to boot on eMAGs in this cloud

[Iain Lane]

Public bug reported:

This is something to do with the configuration or software versions
running here, since we have identical hardware running in an adjacent
cloud region but with different versions of the cloud/virt stack.

When we boot bionic arm64 Ubuntu cloud images in "bos01" and they land
on the eMAG systems, they always fail like this:

...
[1.585611] Key type dns_resolver registered
[1.587408] registered taskstats version 1
[1.588913] Loading compiled-in X.509 certificates
[1.592668] Loaded X.509 cert 'Build time autogenerated kernel key: 
4a4a555bc5fd0178c9ab722f3ae7b392f7714ac4'
[1.598866] Loaded X.509 cert 'Canonical Ltd. Live Patch Signing: 
14df34d1a87cf37625abec039ef2bf521249b969'
[1.605389] Loaded X.509 cert 'Canonical Ltd. Kernel Module Signing: 
88f752e560a1e0737e31163a466ad7b70a850c19'
[1.610861] Couldn't get size: 0x800e
[1.613413] MODSIGN: Couldn't get UEFI db list
[1.615920] Couldn't get size: 0x800e
[1.618256] MODSIGN: Couldn't get UEFI MokListRT
[1.620315] Couldn't get size: 0x800e
[1.622317] MODSIGN: Couldn't get UEFI dbx list
[1.624446] zswap: loaded using pool lzo/zbud
[1.628185] Key type big_key registered
[1.629937] Key type trusted registered
[1.632012] Key type encrypted registered
[1.633668] AppArmor: AppArmor sha1 policy hashing enabled
[1.635625] ima: No TPM chip found, activating TPM-bypass! (rc=-19)
[1.638009] ima: Allocated hash algorithm: sha1
[1.639272] evm: HMAC attrs: 0x1
[1.640875] rtc-efi rtc-efi: setting system clock to 2021-05-11 09:28:43 UTC 
(1620725323)
[1.646247] Freeing unused kernel memory: 5824K
[1.657870] Checked W+X mappings: passed, no W+X pages found
[1.660250] Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0005
[1.660250]
[1.663294] CPU: 1 PID: 1 Comm: init Not tainted 4.15.0-142-generic 
#146-Ubuntu
[1.665939] Hardware name: QEMU KVM Virtual Machine, BIOS 0.0.0 02/06/2015
[1.668204] Call trace:
[1.668981]  dump_backtrace+0x0/0x198
[1.670212]  show_stack+0x24/0x30
[1.671282]  dump_stack+0x98/0xc8
[1.672433]  panic+0x128/0x2b0
[1.673502]  do_exit+0x75c/0xa80
[1.674749]  do_group_exit+0x40/0xb0
[1.676191]  get_signal+0x114/0x6e8
[1.677867]  do_signal+0x18c/0x240
[1.679498]  do_notify_resume+0xd0/0x328
[1.681302]  work_pending+0x8/0x10
[1.682771] SMP: stopping secondary CPUs
[1.684624] Kernel Offset: disabled
[1.686119] CPU features: 0x04802008
[1.687353] Memory Limit: none
[1.688453] ---[ end Kernel panic - not syncing: Attempted to kill init! 
exitcode=0x0005
[1.688453]

Full example log: https://autopkgtest.ubuntu.com/results/autopkgtest-
bionic/bionic/arm64/c/chromium-browser/20210511_093739_ea3f2@/log.gz

We tried to get IS to roll things back to match the working bos02, but
they said it's too different and not possible.

The working cloud is running Mitaka from the cloud archive on Xenial (qemu 2.5)
The broken cloud is running Queens from the cloud archive on Xenial (qemu 2.11)

The other thing someone suggested we try is that MDS mitigation is
enabled in the broken cloud, so we could disable it. No idea if that
makes sense tbh.

That's about all we have right now.

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

** Description changed:

  This is something to do with the configuration or software versions
  running here, since we have identical hardware running in an adjacent
  cloud region but with different versions of the cloud/virt stack.
  
  When we boot bionic Ubuntu cloud images in "bos01", they always fail
  like this:
  
  ...
  [1.585611] Key type dns_resolver registered
  [1.587408] registered taskstats version 1
  [1.588913] Loading compiled-in X.509 certificates
  [1.592668] Loaded X.509 cert 'Build time autogenerated kernel key: 
4a4a555bc5fd0178c9ab722f3ae7b392f7714ac4'
  [1.598866] Loaded X.509 cert 'Canonical Ltd. Live Patch Signing: 
14df34d1a87cf37625abec039ef2bf521249b969'
  [1.605389] Loaded X.509 cert 'Canonical Ltd. Kernel Module Signing: 
88f752e560a1e0737e31163a466ad7b70a850c19'
  [1.610861] Couldn't get size: 0x800e
  [1.613413] MODSIGN: Couldn't get UEFI db list
  [1.615920] Couldn't get size: 0x800e
  [1.618256] MODSIGN: Couldn't get UEFI MokListRT
  [1.620315] Couldn't get size: 0x800e
  [1.622317] MODSIGN: Couldn't get UEFI dbx list
  [1.624446] zswap: loaded using pool lzo/zbud
  [1.628185] Key type big_key registered
  [1.629937] Key type trusted registered
  [1.632012] Key type encrypted registered
  [1.633668] AppArmor: AppArmor sha1 policy hashing enabled
  [1.635625] ima: No TPM chip found, activating TPM-bypass! (rc=-19)
  [1.638009] ima: Allocated hash algorithm: sha1
  [1.639272] evm: HMAC attrs: 0x1
  [1.640875] rtc-efi 

[Bug 1931088] Re: boot-and-services tests fails in impish on armhf (248.3)

[Iain Lane]

Just to put the information on the bug, I reproduced this failure on a
Raspberry Pi, not a piece of the Scalingstack infrastructure in sight
;-)

As far as I can tell it looked as if it's timing out waiting for
network-online.target to become active. It seems as if installing
network-manager makes the target take way longer to activate, so long
that it is over autopkgtest's timeout. I suppose this isn't expected, so
maybe the next step is to look into why that happens?

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

Title:
  boot-and-services tests fails in impish on armhf (248.3)

To manage notifications about this bug go to:
https://bugs.launchpad.net/auto-package-testing/+bug/1931088/+subscriptions

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

[Bug 1931257] Re: Please remove ruby-gitlab-pg-query from Impish (-proposed)

[Iain Lane]

laney@dev> ./remove-package -s impish-proposed -m "Accesses the internet during 
build, therefore FTBFS, to be removed in Debian (Debian bug #981878)" 
ruby-gitlab-pg-query
Removing packages from impish-proposed:
ruby-gitlab-pg-query 1.3.1-2 in impish
Comment: Accesses the internet during build, therefore FTBFS, to be removed in 
Debian (Debian bug #981878)
Remove [y|N]? y
1 package successfully removed.


** Changed in: ruby-gitlab-pg-query (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/1931257

Title:
  Please remove ruby-gitlab-pg-query from Impish (-proposed)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ruby-gitlab-pg-query/+bug/1931257/+subscriptions

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

[Bug 1925238] Re: [nvidia-prime] switches between xorg and wayland session

[Iain Lane]

Ok, let's keep this bug report about the udev rule. We will need to make
sure 470 works properly with prime, I'll follow up with that separately.

So would you be able to prepare a merge proposal please? 

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

Title:
  [nvidia-prime] switches between xorg and wayland session

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

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

Re: [Bug 1925238] Re: [nvidia-prime] switches between xorg and wayland session

[Iain Lane]

Yeah, I read the man page too, but it wasn't understandable to me. If 
you understand it more, could you prepare a change for upstream? I can't 
just paste those two entries there to them, that's not enough 
information.

Any hints on the second question about when wayland does start working, 
what prime support is supposed to do then?

On Fri, Jun 04, 2021 at 05:42:53AM -, Alberto Milone wrote:
> Here is the difference:
> 
> DRIVER
> Match the driver name of the event device. Only set this key for devices 
> which are bound to a driver at the time the event is generated.
> 
> DRIVERS
> Search the devpath upwards for a matching device driver name.
> 
> https://www.freedesktop.org/software/systemd/man/udev.html
> 
> 
> I assume the device is not always bound to the driver when the event is 
> generated.
> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1925238
> 
> Title:
>   [nvidia-prime] switches between xorg and wayland session
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1925238/+subscriptions

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]

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

Title:
  [nvidia-prime] switches between xorg and wayland session

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

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

Re: [Bug 1925238] Re: [nvidia-prime] switches between xorg and wayland session

[Iain Lane]

hmm, yeah, that seems to work!

Why is that, can you explain why the other one doesn't work so we can 
forward it upstream (the udev rule is upstream)?

Follow up question - we'll want to be dropping this file won't we, once 
nvidia actually supports wayland. What happens with prime then?

On Thu, Jun 03, 2021 at 09:07:50AM -, Alberto Milone wrote:
> yes, it is the ubuntu session (I wasn't given a choice on login).
> 
> Can you try replacing "DRIVER" with "DRIVERS" in
> /lib/udev/rules.d/61-gdm.rules , please?
> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1925238
> 
> Title:
>   [nvidia-prime] switches between xorg and wayland session
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1925238/+subscriptions

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]

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

Title:
  [nvidia-prime] switches between xorg and wayland session

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

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

Re: [Bug 1925238] Re: [nvidia-prime] switches between xorg and wayland session

[Iain Lane]

ack. Is yours the "ubuntu" session? i.e. auto-detection, the default, 
not "ubuntu-xorg" which is manually selecting "Ubuntu on Xorg" from gdm.  
Check $DESKTOP_SESSION. I can confirm that if I pick ubuntu-xorg then 
nvidia-smi looks like yours.

I see from `lsmod` that nvidia is loaded - apparently that's not enough 
to get it to be used though. I would have expected the udev rule 
(61-gdm.rules) to have fired here and caused gdm-disable-wayland to run, 
so that I got Xorg and things running on the nvidia GPU; is that a valid 
expectation?

On Tue, Jun 01, 2021 at 02:22:34PM -, Alberto Milone wrote:
> I don't get that at all (see the attached screenshot).
> 
> Detection seems to work well here:
> 
> giu 01 16:05:52 dell-g7 systemd[1725]: Starting GNOME Shell on Wayland...
> giu 01 16:05:52 dell-g7 systemd[1725]: Starting GNOME Shell on X11...
> giu 01 16:05:52 dell-g7 systemd[1725]: 
> app-gnome-gnome\x2dkeyring\x2dpkcs11-2001.scope: Succeeded.
> giu 01 16:05:52 dell-g7 systemd[1725]: org.gnome.Shell@wayland.service: 
> Control process exited, code=exited, status=2/INVALIDARGUMENT
> giu 01 16:05:52 dell-g7 systemd[1725]: org.gnome.Shell@wayland.service: 
> Skipped due to 'exec-condition'.
> giu 01 16:05:52 dell-g7 systemd[1725]: Condition check resulted in GNOME 
> Shell on Wayland being skipped.
> 
> ** Attachment added: "Screenshot from 2021-06-01 16-08-04.png"
>
> https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1925238/+attachment/5501675/+files/Screenshot%20from%202021-06-01%2016-08-04.png
> 
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1925238
> 
> Title:
>   [nvidia-prime] switches between xorg and wayland session
> 
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1925238/+subscriptions

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]

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

Title:
  [nvidia-prime] switches between xorg and wayland session

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

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

[Bug 1925238] Re: [nvidia-prime] switches between xorg and wayland session

[Iain Lane]

No, they should be on "ubuntu" and that is Wayland if wayland works and
Xorg if it doesn't.

The problem is that changing the setting doesn't appear to have any
effect at least from what I can see. For example look at the screenshot
attached here.

Do you see this kind of thing on a hybrid machine with hirsute or is it
all OK for you?

** Attachment added: "Screenshot from 2021-06-01 13-01-36.png"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1925238/+attachment/5501666/+files/Screenshot%20from%202021-06-01%2013-01-36.png

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

Title:
  [nvidia-prime] switches between xorg and wayland session

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

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

[Bug 1928001] Re: [SRU] New stable release 2.68.1

[Iain Lane]

I ran the applications listed in the description against
2.68.1-1~ubuntu21.04.1. I also generally exercised the desktop for a
while and didn't notice anything odd.

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

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

Title:
  [SRU] New stable release 2.68.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1928001/+subscriptions

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

[Bug 1928931] [NEW] German strings in deja-dup.mo for en_GB

[Iain Lane]

Public bug reported:

[ Description ]

Some German strings were accidentally translated under en_GB. They
affect the default Ubuntu install - some of them are strings which are
displayed as a notification some time after first logging in, so it's
quite visible. See the attached screenshot.

[ Fix ]

Revert the German and go back to the proper English text. The way to fix
langpacks is to upload the language-pack-gnome-XX package which replaces
files in language-pack-gnome-XX-base.

[ Devel release ]

I'd like to propose to binary copy forward, and let the normal langpack
release schedule take care of eventually dominating these away in
impish.

[ QA ]

To verify the diff, compare deja-dup.po from language-pack-gnome-en-base
to the one in this upload. You'll have to do that manually.

  0. Be in en_GB.
  1. Install the SRU
  2. In an Ubuntu Desktop session, open a terminal and run `deja-dup --prompt`.
  3. Note the buttons in the notification that shows up. They should be in 
English.

[ What could go wrong ]

1. There could be other instances of this in different packages we haven't 
noticed yet
2. If I break the .po file, it could either break the build or the translations 
at runtime (but this is English, so if we fall back to C it's not too bad)
3. If my diff is wrong then I might have dropped some en_GB translations or 
made them wrong

** Affects: language-pack-gnome-en (Ubuntu)
 Importance: Undecided
 Status: In Progress

** Affects: language-pack-gnome-en (Ubuntu Hirsute)
 Importance: Undecided
 Assignee: Iain Lane (laney)
 Status: In Progress

** Attachment added: "Screenshot from 2021-05-19 09-51-59.png"
   
https://bugs.launchpad.net/bugs/1928931/+attachment/5498717/+files/Screenshot%20from%202021-05-19%2009-51-59.png

** Also affects: language-pack-gnome-en-base (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

** Changed in: language-pack-gnome-en-base (Ubuntu Hirsute)
   Status: New => In Progress

** Changed in: language-pack-gnome-en-base (Ubuntu Hirsute)
 Assignee: (unassigned) => Iain Lane (laney)

** Changed in: language-pack-gnome-en-base (Ubuntu)
 Assignee: (unassigned) => Iain Lane (laney)

** Changed in: language-pack-gnome-en-base (Ubuntu)
   Status: New => In Progress

** Description changed:

  [ Description ]
  
  Some German strings were accidentally translated under en_GB. They
  affect the default Ubuntu install - some of them are strings which are
  displayed as a notification some time after first logging in, so it's
  quite visible. See the attached screenshot.
  
  [ Fix ]
  
  Revert the German and go back to the proper English text. The way to fix
  langpacks is to upload the language-pack-gnome-XX package which replaces
  files in language-pack-gnome-XX-base.
  
  [ Devel release ]
  
  I'd like to propose to binary copy forward, and let the normal langpack
  release schedule take care of eventually dominating these away in
  impish.
  
  [ QA ]
  
  To verify the diff, compare deja-dup.po from language-pack-gnome-en-base
  to the one in this upload. You'll have to do that manually.
  
-   0. Be in en_GB.
-   1. Install the SRU
-   2. In an Ubuntu Desktop session, open a terminal and run `deja-dup 
--prompt`.
-   3. Note the buttons in the notification that shows up. They should be in 
English.
+   0. Be in en_GB.
+   1. Install the SRU
+   2. In an Ubuntu Desktop session, open a terminal and run `deja-dup 
--prompt`.
+   3. Note the buttons in the notification that shows up. They should be in 
English.
  
  [ What could go wrong ]
  
- 1. I could have missed some strings, and so there might still be some Deutsch 
around
- 2. There could be other instances of this in different packages we haven't 
noticed yet
- 3. If I break the .po file, it could either break the build or the 
translations at runtime (but this is English, so if we fall back to C it's not 
too bad)
+ 1. There could be other instances of this in different packages we haven't 
noticed yet
+ 2. If I break the .po file, it could either break the build or the 
translations at runtime (but this is English, so if we fall back to C it's not 
too bad)

** Description changed:

  [ Description ]
  
  Some German strings were accidentally translated under en_GB. They
  affect the default Ubuntu install - some of them are strings which are
  displayed as a notification some time after first logging in, so it's
  quite visible. See the attached screenshot.
  
  [ Fix ]
  
  Revert the German and go back to the proper English text. The way to fix
  langpacks is to upload the language-pack-gnome-XX package which replaces
  files in language-pack-gnome-XX-base.
  
  [ Devel release ]
  
  I'd like to propose to binary copy forward, and let the normal langpack
  release schedule take care of eventually dominating these away in
  impish.
  
  [ QA ]
  
  To verify the diff, compare deja-dup.po from language-pack-gnome-en-base
  to the one in th

[Bug 1873895] Re: Regression: block staircase display with side-by-side monitors of different pixel widths

[Iain Lane]

Sean, can you provide a debdiff for amdgpu please? I'm happy to sponsor
it if you do that, ping me on IRC or something.

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

Title:
  Regression: block staircase display with side-by-side monitors of
  different pixel widths

To manage notifications about this bug go to:
https://bugs.launchpad.net/xf86-video-amd/+bug/1873895/+subscriptions

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

[Bug 1925238] Re: [nvidia-prime] switches between xorg and wayland session

[Iain Lane]

** Tags removed: rls-hh-incoming

** Also affects: ubuntu-drivers-common (Ubuntu Impish)
   Importance: Undecided
 Assignee: Alberto Milone (albertomilone)
   Status: New

** Also affects: ubuntu-drivers-common (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-drivers-common (Ubuntu Hirsute)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

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

Title:
  [nvidia-prime] switches between xorg and wayland session

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

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

[Bug 1922353] Re: Overview sometimes fails to appear or disappear in 21.04

[Iain Lane]

Accepting the rls nomination. Daniel, can you maybe get Marco to review
the MR upstream and then prepare backports for ubuntu/debian?

** Also affects: gnome-shell (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

** Also affects: gnome-shell-extension-ubuntu-dock (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

** Changed in: gnome-shell (Ubuntu Hirsute)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu Hirsute)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

** Changed in: gnome-shell (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

** Tags removed: rls-hh-incoming rls-ii-incoming

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

Title:
  Overview sometimes fails to appear or disappear in 21.04

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

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

[Bug 1928001] Re: [SRU] New stable release 2.68.1

[Iain Lane]

automake-1.16> same started happening in impish too - you could cherry-
pick 2b8b44ffc37047231757780952f6290398fb73e2 to the hints maybe?

netplan.io> slyon told me this is known bad and is skipped in other
releases already (upstream) and will be included in the next SRU to
hirsute, if any. could be hinted too?

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

Title:
  [SRU] New stable release 2.68.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1928001/+subscriptions

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

[Bug 1921862] Re: Call germinate with -updates

[Iain Lane]

Please see https://code.launchpad.net/~laney/ubuntu-archive-
publishing/updates/+merge/402698

I believe this is the kind of thing we need to fix this problem
properly, generating Task fields in the archive for -updates - currently
that does not happen. See add_task() in livecd-rootfs for how they are
used. There might be consequences to doing it that I've not thought of,
so maybe this will take a while to land in the archive.

Some workarounds / alternatives which could be done instead, to solve
the immediate problem

  - Directly install the needed packages in livecd-rootfs (hardcoding)
  - Make ubiquity or something else in the live task depend on them
  - Add a new package ubuntu-live-meta (example name) generated from the live 
task and install this, make it work with the normal seed ./update script and 
then SRUs will pick it up. That's a more general variant on the previous item.

** Branch linked: lp:~laney/ubuntu-archive-publishing/updates

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

Title:
  Call germinate with -updates

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

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

[Bug 1926843] Re: online accounts integration with fb isn't working

[Iain Lane]

I retried libgdata and it works now

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

Title:
  online accounts integration with fb isn't working

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

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

[Bug 1925238] Re: [nvidia-prime] switches between xorg and wayland session

[Iain Lane]

Hey Alberto, would you mind taking a look at this please? Feels to me
like there might be some updates needed for wayland-by-default here..?

** Changed in: ubuntu-drivers-common (Ubuntu)
 Assignee: (unassigned) => Alberto Milone (albertomilone)

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

Title:
  [nvidia-prime] switches between xorg and wayland session

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

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

[Bug 1925238] Re: [nvidia-prime] switches between xorg and wayland session

[Iain Lane]

>From looking at the code it seems like we're writing Xorg config files -
at least this probably needs updating to know about Wayland

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

Title:
  [nvidia-prime] switches between xorg and wayland session

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

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

[Bug 1928001] [NEW] [SRU] New stable release 2.68.1

[Iain Lane]

Public bug reported:

[ Description ]

Take this new upstream stable release.

* Fix a crash in `GKeyFile` when parsing a file which contains translations
  using a `GKeyFile` instance which has loaded another file previously (#2361)

* Pin GIO DLL in memory on Windows (!2016)

* Bugs fixed:
 - #2361 g_key_file_load_from_file segfaults on "Key[*]="like lines
 - !1997 Backport !1996 “Include glibconfig.h to get the G_OS_UNIX token” to 
glib-2-68
 - !2016 GIO W32: Pin gio DLL
 - !2021 Backport MR !2016 (GIO W32: Pin gio DLL) into glib-2-68
 - !2022 Few fixes and notes for building on Visual Studio 2012 and earlier
 - !2034 Backport MR !2032 (gkeyfile: Drop a redundant check) into glib-2-68
 - !2035 Backport !2026 “Split g_test_log() messages that contain multiple 
lines” to glib-2-68

[ QA ]

Upstream release, so QA already performed by maintainers

https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

This upload will trigger many autopkgtests that we expect to not be
regressed by this upload.

[ What could go wrong ]

This update contains fixes in multiple places so multiple apps could be
affected. The consequences of a broken GLib can range from some
functions returning bad results sometimes, which have minimal runtime
implications, up to the system simply crashing all the time.

Pretty much all parts of GNOME use GLib, so test anything in the desktop
that you can. If you reboot the machine and can get to the desktop,
that's already tested GLib extensively. But also run applications like
GNOME terminal, Files and Epiphany.

** Affects: glib2.0 (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: glib2.0 (Ubuntu Hirsute)
 Importance: Undecided
 Assignee: Iain Lane (laney)
 Status: In Progress

** Also affects: glib2.0 (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

** Changed in: glib2.0 (Ubuntu)
   Status: New => Fix Released

** Changed in: glib2.0 (Ubuntu Hirsute)
   Status: New => In Progress

** Changed in: glib2.0 (Ubuntu Hirsute)
 Assignee: (unassigned) => Iain Lane (laney)

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

Title:
  [SRU] New stable release 2.68.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1928001/+subscriptions

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

[Bug 1926660] Re: autopkgtests fail due to new update-motd snippet

[Iain Lane]

> IMO Ubuntu CI not upgrading all packages (-U) by default is a bug
because it tests a partially upgraded system

What do you mean please? I can see in the linked log "--apt-upgrade" in
the commandline right at the top. Can you please check this assertion?

The mentioned ubuntu-advantage-tools is currently only in impish-
proposed. What's happening here is the `apt-file search` which update-
motd does as part of its test finds update-motd snippets in any enabled
pocket, and that includes proposed even for packages we aren't taking
from there.

The new snippets in ubuntu-advantage-tools in proposed are found, not
tested (because they are not in the test-depends [would need a >=
version to get the right one, as the package is not in release atm, and
maybe a manual trigger on ubuntu-advantage-tools, not sure if proposed-
migration would be smart enough to figure that out]), and this is making
the error happen.

So, a buggy test in update-motd. I think the idea of this `update-motd`
test is a bit questionable - it's not really update-motd's job to test
everything which integrates with it works all of the time. It should
probably look more like an `autodep8` test in which the integrations
test themselves .

** Changed in: auto-package-testing
   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/1926660

Title:
  autopkgtests fail due to new update-motd snippet

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

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

[Bug 1926955] Re: [VMs on] arm64 eMAG system often failing to reboot with "IRQ Exception at 0x000000009BC11F38"

[Iain Lane]

> I'll file a ticket with IS for their input...

Canonical staff can see this at rt #130839

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

Title:
  [VMs on] arm64 eMAG system often failing to reboot with "IRQ Exception
  at 0x9BC11F38"

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

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

Re: [Bug 1926955] Re: [VMs on] arm64 eMAG system often failing to reboot with "IRQ Exception at 0x000000009BC11F38"

[Iain Lane]

On Wed, May 05, 2021 at 03:12:43PM -, dann frazier wrote:
> On ARM, accelerated guests have the host interrupt controller somewhat
> "passed through". I say that while vigorously waving my hands because I
> don't recall the details well - but I do know that we needed to teach
> the entire stack (host kernel -> QEMU -> edk2) about GICv3 and that was
> new in the xenial release. AIUI, the existing hosts in ScalingStack
> would've been X-Gene w/ older GICv2m controllers. I suspect the root
> cause of these issues lie somewhere in the GICv3 support in QEMU and/or
> edk2 - see bug 1675522 for a similar report. I'd definitely suggest
> upgrading to >= bionic if possible. Or, if not, maybe consider enabling
> the cloud archive to get a newer virt stack. If neither is possible, we
> could also of course try and bisect down the fixes for the xenial stack
> and try and SRU them back - but that will certainly take some time.
> 

Thanks for the analysis and for helping to look at this, it's really 
appreciated.

I suspect getting Scalingstack dist-upgraded to a newer release will be 
a difficult task... upgrading the virt stack alone *may* be possible, we 
can check that (the cloud archive doesn't contain edk2 though). It's 
also running Launchpad buildds though. I would expect reluctance to do 
this from their side due to the risks and, annoying as it is, think we 
should plan on identifying & doing the backports. Sorry :(

I'll file a ticket with IS for their input...

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]

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

Title:
  [VMs on] arm64 eMAG system often failing to reboot with "IRQ Exception
  at 0x9BC11F38"

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

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

[Bug 1926955] Re: [VMs on] arm64 eMAG system often failing to reboot with "IRQ Exception at 0x000000009BC11F38"

[Iain Lane]

I've just noticed a few failing with "Synchronous Exception at
0x984FA4A8" instead of the IRQ Exception seen earlier.

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

Title:
  [VMs on] arm64 eMAG system often failing to reboot with "IRQ Exception
  at 0x9BC11F38"

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

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

[Bug 1926955] Re: [VMs on] arm64 eMAG system often failing to reboot with "IRQ Exception at 0x000000009BC11F38"

[Iain Lane]

FTR, I just checked with Canonical IS and the affected host systems are
running Xenial.

(We also have some different hardware which is running the same versions
too and doesn't suffer from this bug, so I do suspect it is somehow hw
specific.)

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

Title:
  [VMs on] arm64 eMAG system often failing to reboot with "IRQ Exception
  at 0x9BC11F38"

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

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

[Bug 1926955] Re: [VMs on] arm64 eMAG system often failing to reboot with "IRQ Exception at 0x000000009BC11F38"

[Iain Lane]

** Summary changed:

- arm64 eMAG system often failng to reboot with "IRQ Exception at 
0x9BC11F38"
+ [VMs on] arm64 eMAG system often failing to reboot with "IRQ Exception at 
0x9BC11F38"

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

Title:
  [VMs on] arm64 eMAG system often failing to reboot with "IRQ Exception
  at 0x9BC11F38"

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

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

[Bug 1926955] Re: arm64 eMAG system often failng to reboot with "IRQ Exception at 0x000000009BC11F38"

[Iain Lane]

I captured the console log when the bug happens, was hoping there would
be something interesting just before the exception starts spamming the
console, but sadly not.

[  OK  ] Finished Reboot.
[  OK  ] Reached target Reboot.
[   17.856242] reboot: Restarting system


IRQ Exception at 0xBBC11F38


IRQ Exception at 0xBBC11F38


IRQ Exception at 0xBBC11F38


IRQ Exception at 0xBBC11F38


(keeps spamming this message)

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

Title:
  arm64 eMAG system often failng to reboot with "IRQ Exception at
  0x9BC11F38"

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

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

[Bug 1926955] Re: arm64 eMAG system often failng to reboot with "IRQ Exception at 0x000000009BC11F38"

[Iain Lane]

** Description changed:

  We recently installed some new arm64 Ampere eMAG hardware in the
  ScalingStack region which we use to run autopkgtests.
  
  Guests (currently impish VMs on OpenStack) which we spawn often fail to
  reboot, repeating this over and over:
  
-   IRQ Exception at 0x9BC11F38
+   IRQ Exception at 0x9BC11F38
+ 
+ Steps to reproduce:
+ 
+ 1. Boot a current impish daily cloud image (have not confirmed other 
releases) in a VM on an Ampere eMAG (have not verified bare metal).
+ 2. Wait for it to come up, and then issue `sudo reboot`
+ 3. If the machine comes back up again, repeat #2 a few times. This is 
intermittent.
+ 3a. If it fails, take a look at "openstack console log " for the 
IRQ exception which repeats indefinitely.
  
  (stand by, I will get something to attach shortly)
- --- 
+ ---
  ProblemType: Bug
  AlsaDevices:
-  total 0
-  crw-rw 1 root audio 116,  1 May  3 12:45 seq
-  crw-rw 1 root audio 116, 33 May  3 12:45 timer
+  total 0
+  crw-rw 1 root audio 116,  1 May  3 12:45 seq
+  crw-rw 1 root audio 116, 33 May  3 12:45 timer
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
  ApportVersion: 2.20.11-0ubuntu65
  Architecture: arm64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CasperMD5CheckResult: unknown
  DistroRelease: Ubuntu 21.10
  Ec2AMI: ami-fd9f
  Ec2AMIManifest: FIXME
  Ec2AvailabilityZone: nova
  Ec2InstanceType: m1.small
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
  Lspci-vt:
-  -[:00]-+-00.0  Red Hat, Inc. QEMU PCIe Host bridge
- \-01.0-[01-02]01.0-[02]--
+  -[:00]-+-00.0  Red Hat, Inc. QEMU PCIe Host bridge
+ \-01.0-[01-02]01.0-[02]--
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  Lsusb-t:
-  
+ 
  Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
  MachineType: QEMU KVM Virtual Machine
  Package: linux (not installed)
  PciMultimedia:
-  
+ 
  ProcFB:
-  
+ 
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=6bd452c7-16ff-4771-b2e8-36045e00cc68 ro nohz=off
  ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
  RelatedPackageVersions:
-  linux-restricted-modules-5.11.0-16-generic N/A
-  linux-backports-modules-5.11.0-16-generic  N/A
-  linux-firmware 1.197
+  linux-restricted-modules-5.11.0-16-generic N/A
+  linux-backports-modules-5.11.0-16-generic  N/A
+  linux-firmware 1.197
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
  Tags:  impish ec2-images
  Uname: Linux 5.11.0-16-generic aarch64
  UnreportableReason: This report is about a package that is not installed.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: N/A
  _MarkForUpload: False
  acpidump:
-  
+ 
  dmi.bios.date: 02/06/2015
  dmi.bios.release: 0.0
  dmi.bios.vendor: EFI Development Kit II / OVMF
  dmi.bios.version: 0.0.0
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnQEMU:pnKVMVirtualMachine:pvr1.0:cvnQEMU:ct1:cvr1.0:
  dmi.product.name: KVM Virtual Machine
  dmi.product.version: 1.0
  dmi.sys.vendor: QEMU

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

Title:
  arm64 eMAG system often failng to reboot with "IRQ Exception at
  0x9BC11F38"

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

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

[Bug 1926955] WifiSyslog.txt

[Iain Lane]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1926955/+attachment/5494400/+files/WifiSyslog.txt

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

Title:
  arm64 eMAG system often failng to reboot with "IRQ Exception at
  0x9BC11F38"

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

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

[Bug 1926955] UdevDb.txt

[Iain Lane]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1926955/+attachment/5494399/+files/UdevDb.txt

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

Title:
  arm64 eMAG system often failng to reboot with "IRQ Exception at
  0x9BC11F38"

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

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

[Bug 1926955] ProcInterrupts.txt

[Iain Lane]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1926955/+attachment/5494397/+files/ProcInterrupts.txt

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

Title:
  arm64 eMAG system often failng to reboot with "IRQ Exception at
  0x9BC11F38"

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

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

[Bug 1926955] ProcModules.txt

[Iain Lane]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1926955/+attachment/5494398/+files/ProcModules.txt

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

Title:
  arm64 eMAG system often failng to reboot with "IRQ Exception at
  0x9BC11F38"

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

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

[Bug 1926955] ProcEnviron.txt

[Iain Lane]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1926955/+attachment/5494396/+files/ProcEnviron.txt

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

Title:
  arm64 eMAG system often failng to reboot with "IRQ Exception at
  0x9BC11F38"

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

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

[Bug 1926955] ProcCpuinfoMinimal.txt

[Iain Lane]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1926955/+attachment/5494395/+files/ProcCpuinfoMinimal.txt

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

Title:
  arm64 eMAG system often failng to reboot with "IRQ Exception at
  0x9BC11F38"

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

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

[Bug 1926955] Lspci.txt

[Iain Lane]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1926955/+attachment/5494394/+files/Lspci.txt

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

Title:
  arm64 eMAG system often failng to reboot with "IRQ Exception at
  0x9BC11F38"

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

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

[Bug 1926955] CurrentDmesg.txt

[Iain Lane]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1926955/+attachment/5494393/+files/CurrentDmesg.txt

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

Title:
  arm64 eMAG system often failng to reboot with "IRQ Exception at
  0x9BC11F38"

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

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

[Bug 1926955] Re: arm64 eMAG system often failng to reboot with "IRQ Exception at 0x000000009BC11F38"

[Iain Lane]

apport information

** Tags added: apport-collected ec2-images impish

** Description changed:

  We recently installed some new arm64 Ampere eMAG hardware in the
  ScalingStack region which we use to run autopkgtests.
  
  Guests (currently impish VMs on OpenStack) which we spawn often fail to
  reboot, repeating this over and over:
  
IRQ Exception at 0x9BC11F38
  
  (stand by, I will get something to attach shortly)
+ --- 
+ ProblemType: Bug
+ AlsaDevices:
+  total 0
+  crw-rw 1 root audio 116,  1 May  3 12:45 seq
+  crw-rw 1 root audio 116, 33 May  3 12:45 timer
+ AplayDevices: Error: [Errno 2] No such file or directory: 'aplay'
+ ApportVersion: 2.20.11-0ubuntu65
+ Architecture: arm64
+ ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord'
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
+ CasperMD5CheckResult: unknown
+ DistroRelease: Ubuntu 21.10
+ Ec2AMI: ami-fd9f
+ Ec2AMIManifest: FIXME
+ Ec2AvailabilityZone: nova
+ Ec2InstanceType: m1.small
+ Ec2Kernel: unavailable
+ Ec2Ramdisk: unavailable
+ IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig'
+ Lspci-vt:
+  -[:00]-+-00.0  Red Hat, Inc. QEMU PCIe Host bridge
+ \-01.0-[01-02]01.0-[02]--
+ Lsusb: Error: command ['lsusb'] failed with exit code 1:
+ Lsusb-t:
+  
+ Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1:
+ MachineType: QEMU KVM Virtual Machine
+ Package: linux (not installed)
+ PciMultimedia:
+  
+ ProcFB:
+  
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic 
root=UUID=6bd452c7-16ff-4771-b2e8-36045e00cc68 ro nohz=off
+ ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12
+ RelatedPackageVersions:
+  linux-restricted-modules-5.11.0-16-generic N/A
+  linux-backports-modules-5.11.0-16-generic  N/A
+  linux-firmware 1.197
+ RfKill: Error: [Errno 2] No such file or directory: 'rfkill'
+ Tags:  impish ec2-images
+ Uname: Linux 5.11.0-16-generic aarch64
+ UnreportableReason: This report is about a package that is not installed.
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: N/A
+ _MarkForUpload: False
+ acpidump:
+  
+ dmi.bios.date: 02/06/2015
+ dmi.bios.release: 0.0
+ dmi.bios.vendor: EFI Development Kit II / OVMF
+ dmi.bios.version: 0.0.0
+ dmi.chassis.type: 1
+ dmi.chassis.vendor: QEMU
+ dmi.chassis.version: 1.0
+ dmi.modalias: 
dmi:bvnEFIDevelopmentKitII/OVMF:bvr0.0.0:bd02/06/2015:br0.0:svnQEMU:pnKVMVirtualMachine:pvr1.0:cvnQEMU:ct1:cvr1.0:
+ dmi.product.name: KVM Virtual Machine
+ dmi.product.version: 1.0
+ dmi.sys.vendor: QEMU

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1926955/+attachment/5494392/+files/CRDA.txt

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

Title:
  arm64 eMAG system often failng to reboot with "IRQ Exception at
  0x9BC11F38"

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

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

[Bug 1926955] [NEW] arm64 eMAG system often failng to reboot with "IRQ Exception at 0x000000009BC11F38"

[Iain Lane]

Public bug reported:

We recently installed some new arm64 Ampere eMAG hardware in the
ScalingStack region which we use to run autopkgtests.

Guests (currently impish VMs on OpenStack) which we spawn often fail to
reboot, repeating this over and over:

  IRQ Exception at 0x9BC11F38

(stand by, I will get something to attach shortly)

** Affects: linux (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/1926955

Title:
  arm64 eMAG system often failng to reboot with "IRQ Exception at
  0x9BC11F38"

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

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

[Bug 1890313] Re: GFileMonitor deadlocks

[Iain Lane]

The second version should be 0.1.15-2ubuntu1~20.10.1 (but
0.1.15-2ubuntu1 is in hirsute too with a good track record)

** Tags removed: block-proposed-focal block-proposed-groovy removal-candidate 
verification-needed verification-needed-focal verification-needed-groovy
** Tags added: verification-done verification-done-focal 
verification-done-groovy

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

Title:
  GFileMonitor deadlocks

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

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

[Bug 1890313] Re: GFileMonitor deadlocks

[Iain Lane]

Ah, thanks for the reminder.

I've checked the autopkgtest runs for 0.1.15-2ubuntu1~20.04.1 and
0.1.15-2ubuntu1 and didn't find any failures. It's as good as we can
get, I think, as outlined in the description.

I'll do the tags.

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

Title:
  GFileMonitor deadlocks

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

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

[Bug 1918985] Re: Xorg crashed with SIGABRT (caught SIGSEGV) in libinput_device_config_send_events_get_modes(device=NULL) from LibinputApplyConfig() from LibinputSetProperty() from XIChangeDevicePrope

[Iain Lane]

Hello Mahmoud, or anyone else affected,

Accepted xserver-xorg-input-libinput into hirsute-proposed. The package
will build now and be available at https://launchpad.net/ubuntu/+source
/xserver-xorg-input-libinput/0.30.0-1ubuntu1 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-
hirsute to verification-done-hirsute. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-hirsute. 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: xserver-xorg-input-libinput (Ubuntu Hirsute)
   Status: Triaged => Fix Committed

** Tags added: verification-needed verification-needed-hirsute

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

Title:
  Xorg crashed with SIGABRT (caught SIGSEGV) in
  libinput_device_config_send_events_get_modes(device=NULL) from
  LibinputApplyConfig() from LibinputSetProperty() from
  XIChangeDeviceProperty()

To manage notifications about this bug go to:
https://bugs.launchpad.net/xserver-xorg-input-libinput/+bug/1918985/+subscriptions

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

[Bug 1820859] Re: nautilus --version segfaults in g_application_impl_get_dbus_object_path

[Iain Lane]

Hello errors.ubuntu.com, or anyone else affected,

Accepted nautilus into hirsute-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/nautilus/1:3.38.2-1ubuntu2 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-
hirsute to verification-done-hirsute. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-hirsute. 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.

** Tags added: verification-needed verification-needed-hirsute

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

Title:
  nautilus --version segfaults in
  g_application_impl_get_dbus_object_path

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

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

[Bug 1925484] [NEW] Add Impish Indri

[Iain Lane]

Public bug reported:

[ Description ]

This is the codename for the release that will be 21.10

See the exception on https://wiki.ubuntu.com/StableReleaseUpdates
#distro-info-data

[ Test Case ]
  
Verify that the following subcommands of `distro-info` print information about 
the new devel and current stable releases:
  
 * `--devel`
 * `--supported`
 * `--stable`

and try the same commands with these modifiers:

 * `--date=<1 day after release>` along with the above
 * `--fullname`
 * `--release`

** Affects: distro-info-data (Ubuntu)
 Importance: High
 Assignee: Iain Lane (laney)
 Status: Triaged

** Affects: distro-info-data (Ubuntu Bionic)
 Importance: High
 Assignee: Iain Lane (laney)
 Status: Triaged

** Affects: distro-info-data (Ubuntu Focal)
 Importance: High
 Assignee: Iain Lane (laney)
 Status: Triaged

** Affects: distro-info-data (Ubuntu Groovy)
 Importance: High
 Assignee: Iain Lane (laney)
 Status: Triaged

** Affects: distro-info-data (Ubuntu Hirsute)
 Importance: High
 Assignee: Iain Lane (laney)
 Status: Triaged

** Also affects: distro-info-data (Ubuntu Groovy)
   Importance: Undecided
   Status: New

** Also affects: distro-info-data (Ubuntu Focal)
   Importance: Undecided
   Status: New

** Also affects: distro-info-data (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: distro-info-data (Ubuntu Hirsute)
   Importance: Undecided
   Status: New

** Changed in: distro-info-data (Ubuntu Bionic)
 Assignee: (unassigned) => Iain Lane (laney)

** Changed in: distro-info-data (Ubuntu Focal)
 Assignee: (unassigned) => Iain Lane (laney)

** Changed in: distro-info-data (Ubuntu Groovy)
 Assignee: (unassigned) => Iain Lane (laney)

** Changed in: distro-info-data (Ubuntu Hirsute)
 Assignee: (unassigned) => Iain Lane (laney)

** Changed in: distro-info-data (Ubuntu Bionic)
   Status: New => Triaged

** Changed in: distro-info-data (Ubuntu Focal)
   Status: New => Triaged

** Changed in: distro-info-data (Ubuntu Groovy)
   Status: New => Triaged

** Changed in: distro-info-data (Ubuntu Hirsute)
   Status: New => Triaged

** Changed in: distro-info-data (Ubuntu Bionic)
   Importance: Undecided => Critical

** Changed in: distro-info-data (Ubuntu Bionic)
   Importance: Critical => High

** Changed in: distro-info-data (Ubuntu Focal)
   Importance: Undecided => High

** Changed in: distro-info-data (Ubuntu Groovy)
   Importance: Undecided => High

** Changed in: distro-info-data (Ubuntu Hirsute)
   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/1925484

Title:
  Add Impish Indri

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

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

[Bug 1923162] Re: riscv64 images fail to boot in qemu

[Iain Lane]

** Tags removed: block-proposed block-proposed-hirsute

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

Title:
  riscv64 images fail to boot in qemu

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

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

[Bug 1925267] Re: u-boot unmatched dtb does not match kernel dtb

[Iain Lane]

** Tags removed: block-proposed block-proposed-hirsute

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

Title:
  u-boot unmatched dtb does not match kernel dtb

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

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

[Bug 1925238] Re: [nvidia-prime] switches between xorg and wayland session

[Iain Lane]

** Description changed:

  I have noticed this on a hirsute install from today's RC media
  (20210420) with ubuntu-drivers-common 1:0.8.9.1.
  
  The first boot is always xorg, and nvidia mode is selected.
  
  After that reboots are *usually* wayland, but sometimes they are xorg
- too. When it's wayland then ondemand mode is selected.
+ too.
+ 
+ Performance mode is selected in nvidia-settings, which is supposed to
+ mean nvidia & therefore xorg but it's not working. Selecting it
+ explicitly doesn't help either.
  
  What is the default meant to be - probably ondemand?
  
  Seems like it's somehow nondeterministic. Attaching some logs.

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

Title:
  [nvidia-prime] switches between xorg and wayland session

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

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

[Bug 1925238] Re: [nvidia-prime] switches between xorg and wayland session

[Iain Lane]

>From the second boot

** Attachment added: "gpu-manager-wayland.log"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1925238/+attachment/5490359/+files/gpu-manager-wayland.log

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

Title:
  [nvidia-prime] switches between xorg and wayland session

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

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

[Bug 1925238] Re: [nvidia-prime] switches between xorg and wayland session

[Iain Lane]

>From the first boot

** Attachment added: "gpu-manager-xorg.log"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1925238/+attachment/5490357/+files/gpu-manager-xorg.log

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

Title:
  [nvidia-prime] switches between xorg and wayland session

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

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

[Bug 1925238] Re: [nvidia-prime] switches between xorg and wayland session

[Iain Lane]

>From the second boot

** Attachment added: "lsmod-wayland.log"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1925238/+attachment/5490358/+files/lsmod-wayland.log

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

Title:
  [nvidia-prime] switches between xorg and wayland session

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

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

[Bug 1925238] [NEW] [nvidia-prime] switches between xorg and wayland session

[Iain Lane]

Public bug reported:

I have noticed this on a hirsute install from today's RC media
(20210420) with ubuntu-drivers-common 1:0.8.9.1.

The first boot is always xorg, and nvidia mode is selected.

After that reboots are *usually* wayland, but sometimes they are xorg
too. When it's wayland then ondemand mode is selected.

What is the default meant to be - probably ondemand?

Seems like it's somehow nondeterministic. Attaching some logs.

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

** Attachment added: "modinfo-nvidia-drm.log"
   
https://bugs.launchpad.net/bugs/1925238/+attachment/5490355/+files/modinfo-nvidia-drm.log

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

Title:
  [nvidia-prime] switches between xorg and wayland session

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

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

[Bug 1925238] Re: [nvidia-prime] switches between xorg and wayland session

[Iain Lane]

>From the first boot

** Attachment added: "lsmod-xorg.log"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1925238/+attachment/5490356/+files/lsmod-xorg.log

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

Title:
  [nvidia-prime] switches between xorg and wayland session

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

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

[Bug 1917362] Re: PAM: smartcard owner isn't associated to user by default

[Iain Lane]

This bug will need to be SRUified if we want to fix it in hirsute.
Otherwise, I could reject the pending upload and we leave hirsute as is
and fix for II onwards?

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

Title:
  PAM: smartcard owner isn't associated to user by default

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

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

[Bug 1910871] Re: Release notes hyperlink opens to wrong page

[Iain Lane]

This seems to be fixed, yay!

** Changed in: ubiquity (Ubuntu)
   Status: Triaged => 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/1910871

Title:
  Release notes hyperlink opens to wrong page

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

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