Got stuck on this today after upgrading from 19.04 -> 19.10. I do dual-
boot Windows. Also Ubuntu is on a 2-disk mdadm RAID array.
- I couldn't get boot-repair-disk to work: It wouldn't recognize the
internet connection. The LXTerminal it comes with was broken too and
didn't respond to keyboard
Hello Douglas, thanks for the report. AppArmor is one of several tools
the snap packaging system uses to enforce confinement on packages. The
AppArmor project doesn't supply the policy though, just the enforcement
mechanism. I believe you'll need to talk to whoever wrote the snap
package, as they
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: grub2 (Ubuntu Eoan)
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/1848797
Title:
** Information type changed from Private Security to Public Security
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851139
Title:
Firefox crashing about every 10-20 minutes
To manage notifications
Hello archive admins, I believe this is compelling case to remove
prelink from Ubuntu before 20.04 LTS is released:
- prelink defeats ASLR runtime exploit mitigations
- prelink breaks debsums(1)-style accidental modification detection tools
- prelink also appears to break everything else in eoan
On Thu, 7 Nov 2019 at 20:05, Scott Moser wrote:
>
> > > So that means we have this sequence of events:
> > > a.) growpart change partition table
> > > b.) growpart call partx
> > > c.) udev created and events being processed
>
> > That is not true. whilst sfdisk is deleting, creating,
On Thu, 7 Nov 2019 at 17:50, Ryan Harper <1834...@bugs.launchpad.net> wrote:
>
> @ddstreet
>
> Yes, settle does not help.
>
> Re-triggering udevadm trigger --action=add /sys/class/block/sda
>
> Would re-run all of them after the partition change has occurred, which
> is what I'm currently
Hi Frank,
Just giving you an update on the status of these bugs. The kernel team
has reviewed the patches I submitted, and each set of patches have
received two acks each, meaning they will be built into the next kernel
update.
Bug 1842037:
As an experiment, I retried this test with focal host/guest (on the off-
chance that e.g. we were missing something from QEMU or some topology
logic in virtinst), but the results were the same.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Public bug reported:
MAAS uses twisted and we have ran into an issue where it seems to be
that the MAAS's networking monitoring services has a lock file to ensure
that only one processes updates the networking information. If the
processes gets killed, the lock file stays, pointing to the PID the
Different code path but a similar error with kill throwing a
PermissionError in
https://bugs.launchpad.net/ubuntu/+source/twisted/+bug/512708
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851737
I can confirm that Booting ISO files from BIOS in Ubuntu 19.10 works fine.
UEFI seems to have the issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851311
Title:
Grub 2.04 Out of memory error,
The GNOME key expired this week, that's bug #1851564. The issue there is
older so it can't be the same issue
** Changed in: gnome-online-accounts
Importance: Unknown => Undecided
** Changed in: gnome-online-accounts
Remote watch: gitlab.gnome.org/GNOME/gnome-online-accounts/issues #42 =>
Thanks for the fix. I tested it on my end and I confirmed this bug as
being fixed. I can now restart and shutdown via gdm.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847896
Title:
Unable to
Thank you for your bug report, could you a 'journalctl -b 0' log from a
session where you noticed the issue?
** Changed in: gnome-software (Ubuntu)
Importance: Undecided => Low
** Changed in: gnome-software (Ubuntu)
Status: New => Incomplete
--
You received this bug notification
** Tags added: desktop-lts-wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1791981
Title:
X Server session crash for "No space left on device"
To manage notifications about this bug go to:
*** This bug is a duplicate of bug 1851564 ***
https://bugs.launchpad.net/bugs/1851564
** This bug has been marked a duplicate of bug 1851564
Daily Limit Exceeded messages for google calendars
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
All autopkgtests for the newly accepted python3.6 (3.6.9-1~18.04) for bionic
have finished running.
The following regressions have been reported in tests triggered by the package:
pybigwig/0.3.2-1ubuntu5 (armhf)
Please visit the excuses page listed below and investigate the failures,
Public bug reported:
I stopped the formatting 19.04 stage because of a bad security choice,
then restarted on the usb live key but there is now a SSD formating
problem
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: ubiquity 19.04.9
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
nothing more
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851735
Title:
after installing 19.10 but with the scan problem I reinstalled 19.04
To manage notifications about this bug go to:
"Illegal instruction" is unlikely to be a bug in the actual software.
Is this problem reproducible if you try to install again on the same
hardware? (Did the installation of Ubuntu 16.04 succeed after this
error?)
Any particular reason you're installing Ubuntu 16.04 rather than the
current LTS,
Public bug reported:
BUG
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14.6
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CasperVersion: 1.394
@jjohansen, I see that you've included the fix in most of the kernels
currently in -proposed, thanks for that! Although, I'm not seeing those
for 4.4 and 4.15 and I'd like to make sure they don't fall through the
cracks ;)
--
You received this bug notification because you are a member of Ubuntu
> We can't know how many devices are in the system. It maybe nearly zero,
> it could be minutes.
I'm not suggesting you trigger uevents for all devices, just the one
you're repartitioning...
> The cold plug is required (initramfs may or maynot
> have ran
> scripts/udevd etc but kernel events
** Changed in: pure-ftpd (Debian)
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/1832998
Title:
Pure-FTPd Breaks with OpenSSL v1.1.1
To manage notifications about
Peter, Pedro, thanks for the extra detail. After reading
https://github.com/kubernetes/kubernetes/issues/58927, I agree that we
won't be able to fix this in Charmed Kubernetes directly.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: gnome-online-accounts (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/1847597
Title:
gnome-control-center cannot access google account
All autopkgtests for the newly accepted systemd (242-7ubuntu3.2) for eoan have
finished running.
The following regressions have been reported in tests triggered by the package:
gvfs/1.42.1-1ubuntu1 (amd64)
systemd/242-7ubuntu3.2 (ppc64el)
ndctl/unknown (armhf)
casper/1.427 (amd64)
All autopkgtests for the newly accepted systemd (242-7ubuntu3.2) for eoan have
finished running.
The following regressions have been reported in tests triggered by the package:
gvfs/1.42.1-1ubuntu1 (amd64)
systemd/242-7ubuntu3.2 (ppc64el)
ndctl/unknown (armhf)
casper/1.427 (amd64)
All autopkgtests for the newly accepted systemd (242-7ubuntu3.2) for eoan have
finished running.
The following regressions have been reported in tests triggered by the package:
gvfs/1.42.1-1ubuntu1 (amd64)
systemd/242-7ubuntu3.2 (ppc64el)
ndctl/unknown (armhf)
casper/1.427 (amd64)
For reference, I'm attaching screenshots of a file save dialog in:
- chromium-browser as a deb package in bionic (kdialog as expected)
- chromium as a snap in eoan (gtk dialog, not correct)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
All autopkgtests for the newly accepted systemd (242-7ubuntu3.2) for eoan have
finished running.
The following regressions have been reported in tests triggered by the package:
gvfs/1.42.1-1ubuntu1 (amd64)
systemd/242-7ubuntu3.2 (ppc64el)
ndctl/unknown (armhf)
casper/1.427 (amd64)
All autopkgtests for the newly accepted systemd (242-7ubuntu3.2) for eoan have
finished running.
The following regressions have been reported in tests triggered by the package:
gvfs/1.42.1-1ubuntu1 (amd64)
systemd/242-7ubuntu3.2 (ppc64el)
ndctl/unknown (armhf)
casper/1.427 (amd64)
** Attachment added: "eoan-snap-gtkdialog.png"
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1851621/+attachment/5303612/+files/eoan-snap-gtkdialog.png
** Changed in: chromium-browser (Ubuntu)
Status: New => Confirmed
** Changed in: chromium-browser (Ubuntu)
All autopkgtests for the newly accepted systemd (242-7ubuntu3.2) for eoan have
finished running.
The following regressions have been reported in tests triggered by the package:
gvfs/1.42.1-1ubuntu1 (amd64)
systemd/242-7ubuntu3.2 (ppc64el)
ndctl/unknown (armhf)
casper/1.427 (amd64)
** Attachment added: "bionic-deb-kdialog.png"
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1851621/+attachment/5303611/+files/bionic-deb-kdialog.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
All autopkgtests for the newly accepted systemd (242-7ubuntu3.2) for eoan have
finished running.
The following regressions have been reported in tests triggered by the package:
gvfs/1.42.1-1ubuntu1 (amd64)
systemd/242-7ubuntu3.2 (ppc64el)
ndctl/unknown (armhf)
casper/1.427 (amd64)
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851723
Title:
package cryptsetup 2:1.6.6-5ubuntu2.1 failed to install/upgrade:
subprocess installed
Public bug reported:
Hi,
Since recently, I can't import a VPN connection in NetworkManager and store my
credentials.
NetworkManager will systematically forget the password, despite a log entry
confirming that the operation was a success:
nov. 07 22:26:52 NetworkManager[1518]:
Public bug reported:
I was install Ubuntu from a bootable USB stick. It gave me this error.
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: cryptsetup 2:1.6.6-5ubuntu2.1
ProcVersionSignature: Ubuntu 4.13.0-1024.27-oem 4.13.16
Uname: Linux 4.13.0-1024-oem x86_64
ApportVersion:
** Changed in: gnome-online-accounts
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1847597
Title:
gnome-control-center cannot access google account
To manage
issue#40080 has been addressed upstream and the fix will be delivered in
the next point release of luminous (12.2.13).
The bitmap allocator is an experimental feature, that has been reported
unstable by upstream [0]. There isn't an urgent need to drive this fix
ahead of upstream.
Marking this
*** This bug is a duplicate of bug 1846557 ***
https://bugs.launchpad.net/bugs/1846557
Thanks Miroslav for opening this bug, two weeks after me opening bug #1846557.
Unfortunately, it took proving that gdb couldn't debug properly _any_ 32-bit
program, not just kernels running on QEMU, in
On Thu, Nov 7, 2019 at 2:41 PM Dan Streetman
wrote:
> > Issuing a second
> > trigger will repeat this.
> > IMO, that's a non-zero amount of time that slows the boot down, so I'd
> like
> > to avoid that.
>
> systemd-udev-trigger.serivce retriggers *everything* at boot (except in
>
an
Public bug reported:
Every time I adjust my laptop's screen brightness using the dedicated
brightness keys, there is a substantial delay between when I press the
button and the screen adjusts. Sometimes it even "twitches" and
decreasing the brightness by tapping the button two times will quickly
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: debootstrap (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/1851459
Title:
** Changed in: kernel-sru-workflow/automated-testing
Status: In Progress => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851349
Title:
Xorg
A fix was released after bug #1848200, reporting the same problem, was
opened.
** Changed in: gdb (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On Thu, Nov 7, 2019 at 11:30 AM Dimitri John Ledkov
wrote:
> > So that means we have this sequence of events:
> > a.) growpart change partition table
> > b.) growpart call partx
> > c.) udev created and events being processed
>
> That is not true. whilst sfdisk is deleting, creating,
> Issuing a second
> trigger will repeat this.
> IMO, that's a non-zero amount of time that slows the boot down, so I'd like
> to avoid that.
systemd-udev-trigger.serivce retriggers *everything* at boot (except in
an unprivileged container where it can't), so I'm not sure how much
added time
** Changed in: kernel-sru-workflow/verification-testing
Status: In Progress => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated
*** This bug is a duplicate of bug 1846557 ***
https://bugs.launchpad.net/bugs/1846557
** This bug has been marked a duplicate of bug 1846557
Unable to debug any kernel on i386 qemu machine
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Changed in: kernel-sru-workflow/verification-testing
Status: In Progress => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated
I could resolve this issue by upgrading the printer firmware to latest
version 1.40. No idea, why Ubuntu 19.04 printed happily with older
printer firmware, but as of Ubuntu 19.10 new printer firmware (can be
installed through printer web interface) is needed.
--
You received this bug
** Changed in: kernel-sru-workflow/verification-testing
Status: In Progress => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated
** Changed in: kernel-sru-workflow/verification-testing
Status: In Progress => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated
** Changed in: kernel-sru-workflow/verification-testing
Status: In Progress => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated
I have tested with a second google account (my canonical one, as opposed
to my personal one) and get the exact same error.
** Bug watch added: gitlab.gnome.org/GNOME/gnome-online-accounts/issues #42
https://gitlab.gnome.org/GNOME/gnome-online-accounts/issues/42
** Also affects:
I've been reminded that set -o pipefail is not perfect. I'm going to
quote from the excellent bash faq:
http://mywiki.wooledge.org/BashFAQ/105
> though with pipefail in effect, code like this will sometimes cause an
> error, depending on whether the output of somecmd exceeds the size of the
>
** Changed in: kernel-sru-workflow/verification-testing
Status: In Progress => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated
** Changed in: kernel-sru-workflow/verification-testing
Status: In Progress => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated
I'm seeing the same error.
Steps to reproduce:
Open System Settings
Go to Online Accounts
Add a google account
Enter username / password
I then get the same dialog as the reporter of this bug.
I'm on Ubuntu 19.10.
This smacks of our online accounts api key being revoked / rate-limited
or
** Changed in: ubuntu
Assignee: Andres Rodriguez (andreserl) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1765476
Title:
[needs-packaging] candid
To manage notifications
** Changed in: kernel-sru-workflow/verification-testing
Status: In Progress => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated
** Changed in: kernel-sru-workflow/verification-testing
Status: In Progress => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated
** Tags removed: need-duplicate-check
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851714
Title:
package libssl1.1:i386 1.1.1-1ubuntu2.1~18.04.4 failed to
install/upgrade: installed
Hi Tim, I don't think patching kubernetes-master will resolve this
issue. Mainly because the issue happens on kubernetes-workers.
We were seeing PVCs failing with: "No VM found". When we look into the
logs, actually kubernetes was trying to learn about its kubernetes-
workers through SystemUUID.
** Changed in: kernel-sru-workflow/verification-testing
Status: In Progress => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated
Public bug reported:
on login to laptop.
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libssl1.1:i386 1.1.1-1ubuntu2.1~18.04.4
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic i686
ApportVersion: 2.20.9-0ubuntu7
Architecture: i386
Date: Thu Nov
That's not enough information. At this point you should report a new
bug, please.
Notice the linked bug #1760450 includes a crash trace. (Not saying for
sure you'd be able to do the same). The fatal signal is SIGBUS, as
opposed to the usual SIGSEGV or abort. If you've got a SIGSEGV or an
What we're seeing is a failed provisioning error when adding volumes, we
hit this closed issue:
https://github.com/kubernetes/kubernetes/issues/58927 Kubernetes
behaviour changed to fix this issue by switching to the */product_serial
file as the source of truth.
But for our case the
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: pgcli (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/1846351
Title:
> > So that means we have this sequence of events:
> > a.) growpart change partition table
> > b.) growpart call partx
> > c.) udev created and events being processed
> That is not true. whilst sfdisk is deleting, creating, finishing
> partition table (a) and partx is called (b), udev events
I've run the command
sudo chown -R myuser.myuser /home/myuser/.kde/
let's see after some days if the error returns.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851573
Title:
configuration file
If this is going to be addressed via code changes rather than a rewrite,
I'd like to suggest the following order:
- remove all evals
- add set -o pipefail to help catch errors in pipelines
- add set -u to help catch unset variables
- replace /tmp/sigline with mktemp -d
Thanks
--
You received
Wrong - not "any" password auto filler is fooled, I use Lastpass and it
works just fine.
Dale, are you by chance using Chrome/Chromium with the browser's built-
in password auto-filler? Let me know.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Thanks Mr. Kernel Bot but I really do not think that this bug misses
logs :)
** 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/1851709
Yes, freeze from time to time and the all system freezing with it.
alt+f+prinscreen (oom killer) or hard reboot are the only options to go back
from it.
My suspect is multi processes by default but I'm just guessing.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Attaching all-in-one test case for testing patched kernels.
** Attachment added: "lp1850994.sh"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850994/+attachment/5303560/+files/lp1850994.sh
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
On Thu, Nov 7, 2019 at 1:30 PM Dan Streetman
wrote:
> > Yes, settle does not help.
>
> Well, I didn't suggest just to settle ;-)
>
Sorry; long bug thread.
> > I'm currently suggesting as a heavy-handed workaround.
>
> I don't really see why you think this is heavy-handed, but I must be
>
> Yes, settle does not help.
Well, I didn't suggest just to settle ;-)
> I'm currently suggesting as a heavy-handed workaround.
I don't really see why you think this is heavy-handed, but I must be
missing something.
> I would like to understand *why* the udevd/kernel pair exhibits this racy
>
I see and understand now that mounting casper-rw in live-only mode is by
intention and not a bug.
I think the important thing is that it is possible to unmount all
partitions on the drive when running live-only with 'toram'.
It is also valuable to learn about the boot option 'nopersistent.'
So
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 1851709
and then change the status of the bug to 'Confirmed'.
If, due to the
oops! Forgot to specify the exact release. But I think all releases are
affected.
me@comp:/more/Documents$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.3 LTS
Release:18.04
Codename: bionic
me@comp:/more/Documents$ uname -a
Linux
Public bug reported:
Mostly the same info as on a related kernel.org bugzilla entr[0].
[0]: https://bugzilla.kernel.org/show_bug.cgi?id=205441
We got issues reported with old Intel CPUs and Linux guest run with
QEMU/KVM after a recent kernel update which is based on
Ubuntu-5.0.0-33.35.
I
Reviewed: https://review.opendev.org/686974
Committed:
https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=e349bfb14aeaa884e3d26dce7e09ffb96cc0ae73
Submitter: Zuul
Branch:master
commit e349bfb14aeaa884e3d26dce7e09ffb96cc0ae73
Author: Frode Nordahl
Date: Mon Oct 7 10:10:34
We could potentially patch Charmed Kubernetes against this by not
reading /sys/class/dmi/id/product_uuid (https://github.com/charmed-
kubernetes/charm-kubernetes-
master/blob/master/reactive/kubernetes_master.py#L2244), but instead
using the workaround published by vmware at
Public bug reported:
I encountered this problem when I was backing up my data to an ext4 drive.
As I understand, the problem will happen with any editor and likely with any
other program.
When disk is full, files are erased when you try to save them.
Scenario 1 (exactly as it happens in real
Hi Peter, can you elaborate on this part please: "manifests itself by
breaking provisioning in Kubernetes."
Can you describe the behavior you're seeing?
--
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: gdm3 (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/1848534
Title:
Just a clarification, the description says "hpre patchset have merged
into mainline 5.4rc3 kernel", however it has not:
$ git log --pretty=oneline --abbrev-commit v5.3..v5.4-rc6 --grep
"crypto: hisilicon - add HiSilicon HPRE accelerator"
But it is in linux-next:
$ git log --pretty=oneline
Public bug reported:
i was using "mailspring", and confirming a subscription to tfir by clicking the
confirm link in the email they sent. upon clicking the confirm link, firefox
opened. then after clicking the "verify humanity" button and hitting confirm
(on the page now open in firefox), that
Public bug reported:
The rtags-rc -w command is racy, see more details at:
https://github.com/Andersbakken/rtags/pull/1348
** Affects: rtags (Ubuntu)
Importance: Undecided
Status: New
** Tags: update-excuse
--
You received this bug notification because you are a member of
It seems any password auto filler gets fooled by the honeypot on the
page and results in the error.
The irony is that in order to comment or mark "it affects me", you have
to get past the very form that's causing the problem. I suspect this
affects a lot more people than is indicated.
--
You
As the Debian maintainer I filed a removal ticket
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921401 but there's one
package using it (sl-modem, I think that's fixable by throwing
-Wl,-execstack or something at it) that I haven't gotten around to
chasing. If someone wants to apply
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => In Progress
** Description changed:
This bug will contain status and test results related to a kernel source
Public bug reported:
There are DEP8 failures with the new lz4 package on focal-proposed,
1.9.2-1
[ 78%] main.mysqlpump_basic_lz4 [ fail ]
Test ended at 2019-11-04 20:04:36
CURRENT_TEST: main.mysqlpump_basic_lz4
Dump progress: 1/2 tables, 0/9 rows
mysqlpump: [NOTE]
** Description changed:
Hi,
- On VMWare when decoding /sys/class/dmi/id/product_serial dmidecode
- produces an output whereby the first 16 characters have been reversed in
- comparison to /sys/class/dmi/id/product_uuid.
+ On VMWare 6.5 and higher (HW version 13 and higher) when decoding
+
Digging a little deeper, specifically in /usr/lib/ubiquity/plugins/ubi-
prepare.py, in the method setup_sufficient_space() there is a call to a
subprocess, that subprocess being parted_devices. Running parted_devices
on your own in terminal with this device will report the above "HBG4a"
and
101 - 200 of 538 matches
Mail list logo
