Also all autopkgtests are now good!
** Tags removed: verification-needed verification-needed-focal
verification-needed-impish
** Tags added: verification-done verification-done-focal
verification-done-impish
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
If you are able to wipe the machine and test 22.04 early then it can be
downloaded here:
http://cdimage.ubuntu.com/daily-live/current/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960747
Title:
It looks like there were a few rotation fixes upstream in mutter in the
past year or so, so maybe this has been fixed already.
Unfortunately you can't test it in a live session because live sessions
use Xorg still. We'll need to wait until you are able and willing to try
Ubuntu 22.04, which will
Thank you for reporting this bug to Ubuntu.
Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016.
See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases
We appreciate that this bug may be old and you might not be interested
in discussing it any more.
The verification of the Stable Release Update for linux-firmware has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
The verification of the Stable Release Update for linux-firmware has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
The verification of the Stable Release Update for linux-firmware has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
The verification of the Stable Release Update for linux-firmware has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
This bug was fixed in the package linux-firmware - 1.201.4
---
linux-firmware (1.201.4) impish; urgency=medium
* mt7921e: Failed to start WM firmware (LP: #1954300)
- linux-firmware: update frimware for mediatek bluetooth chip (MT7921)
* mt7921e :02:00.0: PM: failed to
This bug was fixed in the package linux-firmware - 1.187.26
---
linux-firmware (1.187.26) focal; urgency=medium
* [SRU][F] Add firmware of MT7922 (LP: #1958153)
- linux-firmware: add firmware for MT7922
- linux-firmware: add frimware for mediatek bluetooth chip (MT7922)
*
This bug was fixed in the package linux-firmware - 1.187.26
---
linux-firmware (1.187.26) focal; urgency=medium
* [SRU][F] Add firmware of MT7922 (LP: #1958153)
- linux-firmware: add firmware for MT7922
- linux-firmware: add frimware for mediatek bluetooth chip (MT7922)
*
This bug was fixed in the package linux-firmware - 1.187.26
---
linux-firmware (1.187.26) focal; urgency=medium
* [SRU][F] Add firmware of MT7922 (LP: #1958153)
- linux-firmware: add firmware for MT7922
- linux-firmware: add frimware for mediatek bluetooth chip (MT7922)
*
This bug was fixed in the package linux-firmware - 1.187.26
---
linux-firmware (1.187.26) focal; urgency=medium
* [SRU][F] Add firmware of MT7922 (LP: #1958153)
- linux-firmware: add firmware for MT7922
- linux-firmware: add frimware for mediatek bluetooth chip (MT7922)
*
This bug was fixed in the package linux-firmware - 1.201.4
---
linux-firmware (1.201.4) impish; urgency=medium
* mt7921e: Failed to start WM firmware (LP: #1954300)
- linux-firmware: update frimware for mediatek bluetooth chip (MT7921)
* mt7921e :02:00.0: PM: failed to
The verification of the Stable Release Update for linux-firmware has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you
This bug was fixed in the package linux-firmware - 1.187.26
---
linux-firmware (1.187.26) focal; urgency=medium
* [SRU][F] Add firmware of MT7922 (LP: #1958153)
- linux-firmware: add firmware for MT7922
- linux-firmware: add frimware for mediatek bluetooth chip (MT7922)
*
Please also check for crashes using these steps:
https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960742
Thanks for the bug report.
Next time the freeze happens please:
1. Wait 10 seconds.
2. Reboot.
3. Run:
journalctl -b-1 > prevboot.txt
4. Attach the resulting text file here.
** Summary changed:
- Xorg freeze
+ System freeze
** Package changed: xorg (Ubuntu) => linux-hwe-5.13 (Ubuntu)
** Package changed: xorg (Ubuntu) => mutter (Ubuntu)
** Summary changed:
- Autorotation of screen does not work on wayland, but on X
+ [Lenovo Yoga 7] Autorotation of screen does not work on wayland, but on X
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
BTW, "ConditionPathIsDirectory" is not new. It's been there for two
years already in Ubuntu 20.04.
If you have experienced a regression then more often that would come
from a kernel update so please try some different kernel versions.
** Also affects: linux (Ubuntu)
Importance: Undecided
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:
apport-collect 1960709
When reporting bugs in the future please use apport by using 'ubuntu-
At first this seems to work fine in 22.04 (much newer version of
desktop-icons-ng), but then I could get it to fail if I dragged a group
by a folder in the top left of the group.
Please try the latest version by booting this from USB:
http://cdimage.ubuntu.com/daily-live/current/
If the
Attach oem-somerville-weedle-meta_20.04~ubuntu1.debdiff by oem-scripts
1.29.
** Summary changed:
- [DRAFT][MIR] oem-somerville-weedle-meta
+ [MIR] oem-somerville-weedle-meta
** Description changed:
- [DRAFT][Availability]
+ [Background]
+
+ Please see
** Tags added: impish
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960679
Title:
Dekstop icon extension can't handle moving icons to a to-be-empty spot
To manage notifications about this bug go
** Changed in: linux (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/1960448
Title:
Sony WF-XB700 Bluetooth headset not detected
To manage
Tested virtualbox-ext-pack (as well as the latest virtualbox-guest-dkms)
on focal with linux-hwe-5.15. Everything is working fine.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960171
Title:
[SRU]
Public bug reported:
[Impact]
USB port stops working after unplug an USB device.
[Fix]
Commit c89686118c786a523eee3ef68ed38330319626d8 ("usb: core: Bail out when port
is stuck in reset loop")
[Test]
Affected vendor confirmed the patch can fix the issue after numerous round of
tests.
[Where
Thanks for the bug report.
I can see two problems here, though am not sure if either is the main
issue:
* Timeout, server 21.0.0.52 not responding. Whatever that is, if it's a
server the machine depends on then it might cause a startup failure.
* CurrentDmesg.txt seems to suggest file system
Public bug reported:
This was an issue which occurred during setup and brought me to this bug
report page. I need an older Ubuntu install for the GMA500 driver which
has not been updated for newer distros sadly.
(Should I open another bug for no 3D acceleration with GMA500 on 20.04
or 22.04?)
Thanks for the bug report. The final entry in your kernel log shows that
the Intel GPU tried and failed to update the screen:
[ 1216.206745] i915 :00:02.0: [drm] *ERROR* Atomic update failure on
pipe A (start=73567 end=73568) time 940 us, min 1073, max 1079, scanline
start 1033, end 1097
So
This bug causes severe problems for multiple of our users. The fix is
really small. Can someone please apply the patch.
** Changed in: cjson (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Test on Troy-MTE-DVT, BIOS 1.0.0
steps:
1. Install ubuntu impish
2. Enable proposed channel
3. Wi-Fi/BT works well after installation
** Attachment added: "dmesg.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1954300/+attachment/5560719/+files/dmesg.txt
** Tags removed:
Ubuntu 20.04 LTS ships with 5.5, 22.04 LTS will ship with 5.16. There
are no plans to backport these to 16.04 LTS
** Changed in: strace (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: grpc (Ubuntu)
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/1935709
Title:
Not having this is super inconvenient. Please include the cmake config
files.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1935709
Title:
grpc++-dev doesn't install gRPCConfig.cmake
To manage
We also need below commit to fix the issue introduced by this patch
https://patchwork.kernel.org/project/linux-mediatek/patch/70e27cbc652cbdb78277b9c691a3a5ba02653afb.1641540175.git.obj...@gmail.com/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Description changed:
[Steps to reproduce]
1. Install 20.04.3 with "Third-party packages" on a system which containing a
RTD3 supported nvidia card.
2. After the installation, press enter to reboot system
3. prime-select query
[Expected result]
on-demand
[Actual result]
** Description changed:
[Steps to reproduce]
1. Install 20.04.3 with "Third-party packages" on a system which containing a
RTD3 supported nvidia card.
2. After the installation, press enter to reboot system
3. prime-select query
[Expected result]
on-demand
[Actual result]
** Description changed:
[Steps to reproduce]
1. Install 20.04.3 with "Third-party packages" on a system which containing a
RTD3 supported nvidia card.
2. After the installation, press enter to reboot system
3. prime-select query
[Expected result]
on-demand
[Actual result]
per test, if fwupd-unsigned is not installed, then re-install bios will
be failed if secure boot is not turned on.
We need a patch around
https://github.com/fwupd/fwupd/blob/main/plugins/uefi-capsule/fu-uefi-
common.c#L89
--
You received this bug notification because you are a member of Ubuntu
** Also affects: libusb (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/1960768
Title:
fwupd crash on stop
To manage notifications about this bug
** Changed in: oem-priority
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/1894796
Title:
[MIR] oem-somerville-charmander-14-meta
To manage
** Changed in: oem-priority
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/1894795
Title:
[MIR] oem-somerville-charmander-meta
To manage notifications
** Changed in: oem-priority
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/1920195
Title:
[MIR] oem-somerville-pidgeot-14-meta
To manage notifications
** Changed in: oem-priority
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/1920196
Title:
[MIR] oem-somerville-pidgeot-meta
To manage notifications
** Changed in: oem-priority
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/1937223
Title:
[MIR] oem-somerville-kakuna-meta
To manage notifications about
Just a quick note to mention that Samba in Jammy is a lesser version
than in focal-updates and impish-updates, which should probably be
addressed before Jammy is released.
samba | 2:4.13.14+dfsg-0ubuntu2 | jammy | source, amd64,
arm64, armhf, ppc64el, riscv64, s390x
samba |
** Tags added: oem-priority originate-from-1958974 stella
** Tags added: originate-from-1959354
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960771
Title:
Use EC GPE for s2idle wakeup on AMD
Public bug reported:
[Impact]
Opening lid doesn't wakeup some AMD platforms from s2idle.
[Fix]
Use EC GPE for lid events to wakeup the laptops.
[Test]
Close and only the lid. The affected laptop now can be woken up by lid.
[Where problems could occur]
The original issue was later fixed by
jeremyszu: the pkg was withdrawn and needs rework.
** Changed in: fwupd (Ubuntu Focal)
Status: Fix Committed => Confirmed
** Changed in: fwupd (Ubuntu Impish)
Status: Fix Committed => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
[Expired for qemu (Ubuntu) because there has been no activity for 60
days.]
** Changed in: qemu (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1953628
I happened to install an impish iso with the previous libusb.
It seems to me that: after upgrading libusb, then this can be
reproduced.
more information will be provided.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
fixed in the 5.13 packaging
** Changed in: strace (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/1754945
Title:
update homepage metadata to
Hi Łukasz,
I didn't see the targeted fwupd in focal-proposed and impish-proposed.
$ apt policy fwupd
fwupd:
Installed: 1.7.4-1ubuntu1
Candidate: 1.7.4-1ubuntu1
Version table:
*** 1.7.4-1ubuntu1 500
500 http://tw.archive.ubuntu.com/ubuntu jammy/main amd64 Packages
100
Public bug reported:
I can reproduce crash with a similar stack as below as I stop fwupd
service.
https://errors.ubuntu.com/problem/4bfcf571c017010afe4775687ff2a9ca7ff79661
also test fwupd 1.7.5
(https://launchpad.net/~ycheng-twn/+archive/ubuntu/fwupd175)
still can reproduce this issue.
**
Hi Frode,
I went through the captures I have and effectively, if we filter out the
packets where the srcport != 53 or dstport != 6081 , we end up only with
valid dns traffic.
I believe this explains what we are seeing, and the other findings you
did regards the missing flows, we can say with
I wrote a script for making a core20 with glibc from proposed in it:
#!/bin/sh
set -eux
snap download --basename core20_prehax core20
unsquashfs -d core20 core20_prehax.snap
a=$(dpkg --print-architecture)
v=2.31-0ubuntu9.5
** Description changed:
After my Thinkpad T14 gen2 AMD spontaneously rebooted I found this in
the kernel log:
[6.211553]
===
[6.211556] UBSAN: invalid-load in
Public bug reported:
The nvidia-settings packages is needed for the new Nvidia 510 series
driver from 20.04 for OEM customer.
** Affects: nvidia-settings (Ubuntu)
Importance: Undecided
Status: New
** Summary changed:
- Introduce Nvidia the 510 series
+ Introduce 510 NVIDIA driver
Nothing in regular Ubuntu calls 'xrandr --brightness' that I know of.
Hence I recommend uninstalling 'brightness-controller' because it's the
most suspicious package right now.
Also I would expect 'GNOME' to avoid the problem more than 'GNOME on
Xorg' because 'GNOME' has no Xorg server and no
This change was made by a bot.
** Changed in: linux (Ubuntu)
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/1949075
Title:
[Sony WI-C310] [Intel Wireless 8260]
Jonas,
In comment #5 do you mean the fix was released to Ubuntu, or the fix is
only in the Mesa PPA from comment #3?
** No longer affects: xserver-xorg-video-intel (Ubuntu)
** No longer affects: linux (Ubuntu)
** No longer affects: kubuntu-meta (Ubuntu)
** No longer affects: xorg (Ubuntu)
**
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1960448
and then change the status of the bug to 'Confirmed'.
If, due to the
** Tags added: 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/1958591
Title:
[amdgpu] Random noise 'static' display after internal display turned
off/on
To manage notifications
Same issue in home desktop computer. Wifi not turn on. I have to restart
wifi-dongle and computer.
Ubuntu 18.04 LTS. I dont find any options in turned to off. Settings are same.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I think most likely the problem is a side effect of the customizations
this machine has experienced over the years. Like switching display
managers multiple times, or using a non-standard kernel.
I would suggest the fastest way to a fix might be to just reinstall
fresh:
Given the message in your kernel log:
Bluetooth: hci0: Ignoring error of Inquiry Cancel command
A similar problem with the same message was a kernel regression:
https://bbs.archlinux.org/viewtopic.php?id=259954
Maybe not related to this bug, but still a reminder that it might be a
kernel
** Changed in: bluez (Ubuntu)
Status: Incomplete => New
** Changed in: gnome-bluetooth (Ubuntu)
Status: Incomplete => New
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs,
This is still on my TODO list but low priority. The reason being this
kind of bug has been observed with every release on a variety of
hardware. I think it fails in more cases than it succeeds, and has
always done so.
If by chance a developer has access to the same specific headset then
the
** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1942
https://gitlab.gnome.org/GNOME/mutter/-/issues/1942
** Also affects: mutter via
https://gitlab.gnome.org/GNOME/mutter/-/issues/1942
Importance: Unknown
Status: Unknown
--
You received this bug notification because
*** This bug is a duplicate of bug 1876632 ***
https://bugs.launchpad.net/bugs/1876632
This is an ongoing problem with the Nvidia drivers. Now tracking in bug
1876632.
** This bug has been marked a duplicate of bug 1876632
[nvidia] Corrupted/missing shell textures when switching users or
Seem that this bug has been solved in 20210415-1 version for Jammy, so
should be closed.
Thanks and best regards.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1563083
Title:
Desktop file broken
Sorry, this bug is very old and this version of Ubuntu isn't supported
any more. If you think you have a similar issue, please file a new bug.
** Package changed: fedora => libgweather4 (Ubuntu)
** No longer affects: libgweather4 (Ubuntu)
--
You received this bug notification because you are a
** Changed in: gnome-desktop (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: gnome-desktop (Ubuntu)
Status: Fix Released => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: libgweather4 (Ubuntu)
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/980519
Title:
** Changed in: gnome-desktop (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/72172
Title:
wishlist: support for recently used applications
To manage
gnome-about doesn't exist any more.
** Changed in: gnome-desktop (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/465764
Title:
gnome-about crashed with
The Ubuntu kernel mailing list is a better place to discuss adding a new
package:
https://lists.ubuntu.com/archives/kernel-team/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960633
Title:
Create
Is it possible to bisect the kernel to find the offending commit?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960703
Title:
USB TASCAM US-122L audio interface crashes when system load increases
The Ubuntu Archive team will remove gnome-user-guide soon since it's in green at
https://people.canonical.com/~ubuntu-archive/nbs.html
** Changed in: gnome-user-docs (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Hey You-Sheng Yang @vicamo,
Friendly poke :) Could you please verify linux-firmware in impish-
proposed?
This verification seems to block the linux-firmware SRU on impish, and
that blocks a larger SRU on focal.
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Which version have you tested? backportpackge in u-d-t 0.187+ should
already be using the ~bp suffix.
Notably, note that 0.187 is available in focal-bpo.
On Sun, 13 Feb 2022, 8:35 pm Ross Gammon, <1959...@bugs.launchpad.net>
wrote:
> Regarding the requestbackport package, it is really only the
Debhelper 13 is available in focal-backports already.
Please make sure your build environment enables the backports pocket (and
that your dependency solver handles it appropriately).
If you are building in a PPA, there is an extra flag to check in the PPA
settings.
On Sun, 13 Feb 2022, 9:45 pm
Public bug reported:
i am completely new with the linux os so i am not sure how else to
describe the error.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: ubiquity 20.04.15.17
ProcVersionSignature: Ubuntu 5.11.0-27.29~20.04.1-generic 5.11.22
Uname: Linux 5.11.0-27-generic x86_64
Uploaded 5.1.4~bpo21.04.1 to impish-backports
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960752
Title:
[BPO] gramps/5.1.4-1 from Jammy
To manage notifications about this bug go to:
Public bug reported:
Connecting to a modern installation of Ubuntu 21.10 Impish Indri using
the Wayland display server (and PipeWire / gnome-remote-desktop) does
not work from the current LTS release 20.04 Focal Fossa. It aborts
immediately after authentication.
The bug appears directly related
And if you want to keep this behaviour, at least make sure `dpkg -V`
reports that files are missing due to a policy, not cause it's a bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960749
Title:
This was discovered during the run of a CI, and interactive steps are
provided for the ease of reproduction, not because it's the way it was
found. If you don't know how to use Docker images interactively, it
doesn't mean they are not used this way.
Also, even if I'd agree that Docker containers
Julian - correct I was using apt-cacher-ng as per sbuild instructions
here https://wiki.ubuntu.com/SimpleSbuild
Sorry - I've no idea how to configure squid-deb-proxy with sbuild. So
I've deleted my sbuild chroots & disabled using the .mk-sbuildrc proxy.
Installing from a ppa no longer shows 503
** Summary changed:
- install crashed with CalledProcessError - subiquity 290
+ install successful but crashed with CalledProcessError - subiquity 290
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
For over a decade now, at least, users have continually been puzzled by
this silent refusal. Again, in most contexts, that indicates a failure
of the interface.
Viewed 1.1M times
https://askubuntu.com/questions/601/the-following-packages-have-been-kept-back-why-and-how-do-i-solve-it
Viewed 62k
It should be fixed as of the AppArmor 3.0 release. With 3.0 the handling
of jobs doesn't stop with an error unless --abort-on-error is specified.
Instead the parser will keep track of the last error and return that
there was an error, but it will keep processing the rest of the jobs.
We did not
Regarding the requestbackport package, it is really only the template
for the bug report that needs to change from memory. I don't think it
had any other workflow related information. Once that is fixed, it just
needs a reference from the backports process wiki again (like it used to
have).
Public bug reported:
Getting the following error
gencache_init: Failed to create directory: /var/www/.cache/samba -
Permission denied
I seen this was also an issue in redhat
https://bugzilla.redhat.com/show_bug.cgi?id=1908506
Description:Ubuntu 20.04.3 LTS
Release:20.04
**
Nearly anything would be better than the current state of silent
failure. At present, probably many thousands of Ubuntu systems are
reporting the following:
root@system:/home# apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
It seems you use apt-cacher-ng, please try if the issue reproduces
without it, and if so, if it happens with a known good proxy like squid
(e.g. using deb-squid-proxy).
** Changed in: apt (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of
Gramps 5.1.4 from my ppa upgrades fine, and runs as normal on Impish.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1960752
Title:
[BPO] gramps/5.1.4-1 from Jammy
To manage notifications about
Marking as Opinion as David explained why that is not a thing we can
reasonably determine.
** Changed in: apt (Ubuntu)
Status: New => Opinion
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Gramps 5.1.4 builds fine in Impish.
Unfortunately, it fails to build in Focal
The following packages have unmet dependencies:
sbuild-build-depends-gramps-dummy : Depends: debhelper-compat (= 13)
It would be great if the latest debhelper was backported to Focal.
Otherwise I will have to drop the
Public bug reported:
Not sure if this needs to be dealt with manually, but to be safe:
The gnome-user-guide binary is a transitional dummy package which has
been built by the gnome-user-docs source package and which is not longer
needed. It was not built by the latest gnome-user-docs upload
1 - 100 of 172 matches
Mail list logo
