So in short yes we are talking blocking this however its not as bad as
that makes it sound. There is the immediate technical side, and the
reason we must do that, and then there is longer term practical use
side.
So the technical short answer is yes that will be blocked at least
without additional
It's interesting.
I would like to reproduce your scenario on my side.
Would you please share:
1. "ionice -c3 nice cp -a SRC DST" is mandatory? Does it reproducible through a
normal "cp -a"?
2. What's the fail rate?
3. Would you please share the data type from "SRC"? a single large 29,613MB
file?
[Expired for rsyslog (Ubuntu) because there has been no activity for 60
days.]
** Changed in: rsyslog (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to rsyslog in Ubuntu.
https://bu
[Expired for apport (Ubuntu) because there has been no activity for 60
days.]
** Changed in: apport (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.
It seems to work now so I guess you can close this bug report.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1990902
Title:
Ubuntu-bug not submitting bug to website
Statu
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1990902
Title:
Ubuntu-bug not submitting bug to website
Status in apport package in Ubuntu:
New
Bug description:
Steps t
Can you still recreate this issue? I ask as there was some unexpected
downtime with Launchpad a few hours ago.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1990902
Title:
This bug is a bit of a placeholder at the moment - we'll get this landed
into kinetic first and then update this to SRU the change back to the
older releases.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: network-manager (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://
Today's update installed iwd to replace wpa_supplicant but that is still
installed and conflicting.
Run the following and restart
systemctl disable wpa_supplicant
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manag
No problem! I don't still have the D620 (or run 16.04 on anything...).
Side note, Intel GPU drivers sure have come along way since then! Back
in the day, the Intel driver OpenGL was somewhat questionable, it worked
or it didn't with various games and 3D-using stuff see this very bug
report.
Thanks I have updated the status of this CVE in the Ubuntu CVE tracker.
** Changed in: tar (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tar in Ubuntu.
https://bugs.launchpad.
Please explain what kind of problem you are experiencing.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
htt
*** This bug is a duplicate of bug 1990646 ***
https://bugs.launchpad.net/bugs/1990646
Please explain what kind of problem you are experiencing.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
** This bug has been marked a duplicate of bug
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
This issue has sat with a status of 'Incomplete' for over three years
now. There has been no response to comment #47 and the bug report only
references Ubuntu releases that are now EOL so it is being closed with a
status of 'Invalid'.
Please feel free to re-open this bug report if this is still an
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
I'm setting the status of this bug to 'Incomplete' as it's not seen any
activity for some time. If this bug repor
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
Further to comment #3 I'm closing this at the request of the reporter.
Henry, I'm sorry that it took us nearly six years to see your comment :o)
** Changed in: xorg (Ubuntu)
Status: New => Invalid
--
You received th
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
Ubuntu 17.04 (zesty) reached end-of-life
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 16.04 (xenial) reached end-of-standard-support on April 29, 2021.
I'm setting the status of this bug to '
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
review all reported bugs in a timely manner.
Ubuntu 14.04 (trusty) reached end-of-standard-support on April 25, 2019.
I'm setting the status of this bug to '
This Thunderbird issue has sat with a status of 'Incomplete' for over
two years now without any response from the reporter who seems to have
deactivated his account. As no-one else has confirmed or commented on
this issue I'll close this as being an invalid bug report.
** Changed in: network-manag
Public bug reported:
Steps to reproduce:
$ ubuntu-bug apport
Gtk-Message: 10:30:47.890: Failed to load module "xapp-gtk3-module"
Gtk-Message: 10:30:47.920: Failed to load module "canberra-gtk-module"
Gtk-Message: 10:30:47.921: Failed to load module "canberra-gtk-module"
A web browser opens with
Public bug reported:
The authentication dialog of openconnect crashes.
Steps to reproduce:
Add net vpn connection in Gui:
* Settings -> Network -> VPN -> +
* Selecct "Multi-protocol vpn client (openconnect)"
* Select "Cisco AnyConnect or openconnect"
* Enter as gateway "vpn.sydney.edu.au"
* Cli
Freshly released bash-5.2 allows to disable the highlighting of pasted
text (while keeping the "bracketed paste mode" functionality enabled),
or even to define custom highlighting.
You need to place something like this in your .inputrc:
set enable-active-region off
or
set active-region-star
Could you try the gdb from proposed? I think it should help.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1990729
Title:
gdb crashes when run from VSCode
Status in gdb pack
Public bug reported:
ThinkPad X1 Carbon 6th Gen
WiFi was working fine.
Installed today's batch of Kinetic updates.
Laptop can no longer see any WiFi networks (had to dig out my old ThinkPad USB
dongle and plug into my router to be able to submit this bug report).
ProblemType: Bug
DistroRelease:
In my case, if I introduce the boot parameter fsck.mode=skip, then the
message "Press Ctrl+C to cancel all filesystem checks in process" does
not appear and the boot is faster, hence I deduce that the checks are
indeed performed when the boot parameter is not present.
--
You received this bug not
Thank you for taking the time to file a bug report.
>From DpkgTerminalLog.txt, I see the following errors:
Configurando python3 (3.10.6-1~22.04) ...
running python rtupdate hooks for python3.10...
E: py3compile:212: cannot create directory /usr/share/hplip/base/__pycache__:
FileNotFoundError(2,
Public bug reported:
When I connect from my laptop an external monitor with different
refresh, instantly crash the session and get me back to the gdm. After
connect the monitor from the restart the session, I can use it without
any issues, but if I disconnect it and I connect it again, the session
I've had two more instances, one on the 18th and one (multiple,
actually) today. Both were triggered by copying a file as I'd described
(from CLI, "ionice -c3 nice cp -a SRC DST"). Today's OOM events also
killed a Firefox window for some reason. I captured an sosreport on
both days, but last wee
Public bug reported:
Whenever I try to generate a report in GnuCash it fails with a
segmentation fault. It doesn't matter which report I generate or which
accounts / files I am using.
About two weeks ago, everything was working fine. GnuCash package
version: 1:4.8-1build2
** Affects: gnucash (Ub
This bug was fixed in the package mesa - 22.2.0-1ubuntu1
---
mesa (22.2.0-1ubuntu1) kinetic; urgency=medium
* Merge from Debian. (LP: #1990387)
* patches: Drop DG2 patches that won't be getting applied upstream.
* control, rules: Migrate to llvm-15.
mesa (22.2.0-1) unstable; ur
This bug was fixed in the package mesa - 22.2.0-1ubuntu1
---
mesa (22.2.0-1ubuntu1) kinetic; urgency=medium
* Merge from Debian. (LP: #1990387)
* patches: Drop DG2 patches that won't be getting applied upstream.
* control, rules: Migrate to llvm-15.
mesa (22.2.0-1) unstable; ur
It seems that it runs after all at every boot. For example, I started my
system and checked afterwards:
> journalctl | grep fsck | grep 'sep 26'
sep 26 19:20:41 L-5591 systemd[1]: Created slice system-systemd\x2dfsck.slice.
sep 26 19:20:41 L-5591 systemd[1]: Listening on fsck to fsckd communicatio
** Tags removed: foundations-todo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1961427
Title:
zlib: compressBound() returns an incorrect result on z15
Status in Ubuntu on
** Tags removed: foundations-todo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1990187
Title:
systemd-resolved recommends libnss-resolve in kinetic, pulls it into
mini
This patch:
https://bugzilla.kernel.org/show_bug.cgi?id=216299#c3
fixes the problem. The volume is low, but better than not working at all
:)
** Bug watch added: Linux Kernel Bug Tracker #216299
https://bugzilla.kernel.org/show_bug.cgi?id=216299
--
You received this bug notification bec
Public bug reported:
During upgrade from Jammy to Kinetic, I get asked what to do because my
sshd_config has been modified. I say to do a 3-way merge. It says 3-way
merge fails. I shrug, figure I'll just restore my customizations with
Ansible after the upgrade like I always do, and tell it to use
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bug
On Monday, September 26 2022, Hadrien Mary wrote:
> I confirm the fix on Ubuntu 22.10 recently updated.
Thanks, Hadrien.
--
Sergio
GPG key ID: E92F D0B3 6B14 F1F4 D8E0 EB2F 106D A1C8 C3CB BF14
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, whi
This does not look like a systemd bug, so I am re-assigning to linux.
But, this sounds similar to your issue:
https://forums.developer.nvidia.com/t/nvidia-probe-of-00-0-failed-
with-error-1/199301, based on looking at your attached CurrentDmesg.txt.
** Package changed: systemd (Ubuntu) => li
Since most reporters say that the message "Press Ctrl+C to cancel all
filesystem checks in process" appears only for a short period of time,
the question is: Are there filesystem checks on every boot or is this
message shown despite no check were running?
--
You received this bug notification bec
we do not need or want libnss-resolve anymore, because we created stub-
resolv.conf which exports 1) local nameserver resolver 2) with correct
options 3) and search domains. We only needed libnss-resolve back when
we dind't have /run/systemd/resolve/stub-resolv.conf
--
You received this bug notif
** Tags added: foundation-triage-discuss
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to zlib in Ubuntu.
https://bugs.launchpad.net/bugs/1990379
Title:
[UBUNTU 20.04] zlib: inflate() does not update strm.adler if DFLTCC is
*** This bug is a duplicate of bug 1967576 ***
https://bugs.launchpad.net/bugs/1967576
This was fixed in bug 1967576, so I am marking this a duplicate of that.
** This bug has been marked a duplicate of bug 1967576
systemd: autopkgtest: tests-in-lxd fails because of remaining snap .mount
Update to my comment, issue is applicable to versions prior to 1.32 of
TAR. Be that as it may, Jammy is not affected.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to tar in Ubuntu.
https://bugs.launchpad.net/bugs/1810241
Tit
This issue is shown as Open on Jammy. The CVE is applicable to 1.32 and
prior versions of TAR. Jammy uses 1.34, so this status should be not
affected or closed. This was fixed in Focal in
1.30+dfsg-7ubuntu0.20.04.1. Please update the CVE status on Jammy.
--
You received this bug notification
have the same issue with hp envy 16 Alder Lake-P and Realtek ALC245.
With latest packages at the moment (kernel 5.15.0-48-generic)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.n
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1990824
Title:
initramfs-tools: out-of-memory failures during autopkgtest
Status in initramfs-
The empty blacklist.conf seems to have caused all this.
- CLOSE -
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1988658
Title:
boot stops at black screen (blinking cu
** Summary changed:
- package initramfs-tools 0.136ubuntu6 failed to install/upgrade: installed
initramfs-tools package post-installation script subprocess returned error exit
status 1
+ package initramfs-tools 0.136ubuntu6 failed to install/upgrade:
update-initramfs: Generating /boot/initrd.im
This issue seems to have been a funny bug in the solver, actually, and
not a bug in the phased update code itself.
So what happened is that we kept back grub-efi-amd64-signed, and it was
broken. So now the solver iterates over its dependencies and tries to
keep them back too. Except well, when loo
I confirm the fix on Ubuntu 22.10 recently updated.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to elfutils in Ubuntu.
https://bugs.launchpad.net/bugs/1990638
Title:
package libdebuginfod-common 0.187-3 failed to install/u
** Changed in: apt (Ubuntu)
Status: Confirmed => In Progress
** Changed in: apt (Ubuntu)
Assignee: (unassigned) => Julian Andres Klode (juliank)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https
** Changed in: systemd (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1946192
Title:
"Press Ctrl+C to cancel all filesystem checks
From looking at the available logs, the first guess why lz4 failed to
write is that the partition is full. Can you check how much space you
have left on /boot?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to initramfs-tools in
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 more debugging information, in a terminal:
apport-collect -p ubuntu-release-upgrader 1876376
--
You received this bug notification b
** Description changed:
package failed to install during 18.04 to 20.04 upgrade
+
+ DpkgTerminalLog.txt says:
+
+ update-initramfs: Generating /boot/initrd.img-5.4.0-28-generic
+ Error 24 : Write error : cannot write compressed block
+ E: mkinitramfs failure cpio 141 lz4 -9 -l 24
+ update-ini
** Tags added: foundtations-todo
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1990586
Title:
22.04: python3* mismatched phasing breaks dist-upgrades
Status in apt package i
** Description changed:
Hi , when i delete a file where is in another partition than " / " or
mounted in /media/ , i obtain the message in title.
how can i use trash again please ?
iznobe@iznobe-PC:~$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blk
All the initramfs-tools autopkgtest tests seem to run fine on a recent
kernel (5.19) with the debdiff in attach applied.
** Patch added: "initramfs-tools-increase-ram-2GB.debdiff"
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1990824/+attachment/5619021/+files/initramfs-tools-
Public bug reported:
[Impact]
Some autopkgtest tests are failing due to out-of-memory conditions,
especially amd64-ata-only and net.
It seems that we are creating a VM with 1GB only to run the amd64-ata-
only test and even just 512MB for the net test.
It probably makes sense to create larger VM
Considering this adds hardware support and Kinetic is an interim
release, and the (accidental) testing it's already had in Debian, FFe
granted, please go ahead.
** Changed in: mesa (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubun
1 - 100 of 102 matches
Mail list logo
