** Package changed: ubuntu => nova (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829828
Title:
instance failed to revert after a set-password failure
To manage notifications about this
** Tags removed: verification-done
** Tags added: verification-needed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778844
Title:
nvme multipath does not report path relationships
To manage
Edit /etc/default/grub and add them to the line
GRUB_CMDLINE_LINUX_DEFAULT...
Then run 'sudo update-grub' and reboot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821269
Title:
[Aspire ES1-131,
Ok, let me know what you find in your case
If you don't like dissecting debdiffs from the PPA, here the links to git:
https://git.launchpad.net/~ubuntu-virt/ubuntu/+source/qemu/log/?h=bug-1829868-wily-machine-type-diverged
** Changed in: linux-firmware (Ubuntu)
Importance: Undecided => Critical
** Changed in: linux-firmware (Ubuntu Bionic)
Importance: Undecided => Critical
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I only saw this because it expired now :-/
Anyone affected by this might want to take a look at bug 1776189 where
Ubuntu added a special machine type to more easily set "host-phys-bits"
which is the qemu flag to have more (usually the host has more)
available (at the cost of migratability). That
Sorry. I am not familiar with Linux. So I don't know how to modify bootargs.
Can you explain me little more kindly? I'm sorry to bother you.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821269
https://lists.ubuntu.com/archives/kernel-team/2019-May/100831.html
** Description changed:
- LTP: starting af_alg06
- BUG: unable to handle kernel paging request at 9cbe
- IP: sha256_transform+0x28/0x1b20
- PGD 4d341067 P4D 4d341067 PUD 4d345067 PMD 4d346067 PTE 0
- Oops:
It should be safe.
Let's see if it's already fixed upstream, before bisecting between two
older kernel versions.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826461
Title:
Suspend fails on
Yes I am aware of the stale bug problem and have been on both ends.
But as the number of open bugs decreases (at least in some components),
the problem should happen less:
https://docs.google.com/spreadsheets/d/e/2PACX-
1vRDHPxGBHqM6XkT_S8ggtYfD0xchKSUD_z9PopNVE3G1rU05fVSnxDGcDsEstl7gu7N-
Please confirm the issue doesn't happen on previous kernel versions.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829679
Title:
Resolution stuck at 1024x768
To manage notifications about this
** Also affects: network-manager (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/1828134
Title:
Wifi not working after suspend/resume cycle
To
Laptops are almost always wired with only the Intel GPU connected to the
LCD. If there is an Nvidia GPU then it is not connected to the screen;
it only shares rendered frames with the Intel GPU via system memory.
This allows the Nvidia GPU to be completely turned off without losing
the screen or
The reason I ask this is that launchpad has an unfortunate approach to
issue management (these two that you have been communicating in are a
welcome change - thanks) where bugs go stale for years or are dropped
due to lack of engagement from maintainers.
--
You received this bug notification
Does the actually network speed affected by this bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830090
Title:
Cannot reach 1300Mbps using DW1830 (BCM943602BAED) with linux-firmware
To manage
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818797
Title:
Xenial update: 4.4.172 upstream stable release
To manage
** Changed in: debconf (Debian)
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/1782577
Title:
docker: impossible to create image with python3 because tzdata
To manage
re:nomodeset: That's odd unless the drivers on the live usb media are
old; nomodeset is definitely needed to not lock up from the live usb on
this machine.
re:grubmenu: I'm not using UEFI, so AFAIU, shift should be the key
(though I tried both). Is it edge triggered? If not, I've had the key
held
This bug was fixed in the package livecd-rootfs - 2.586
---
livecd-rootfs (2.586) eoan; urgency=medium
[ Robert C Jennings ]
* magic-proxy: Send headers on error (LP: #1829944)
-- Michael Hudson-Doyle Thu, 23 May 2019
12:33:21 +1200
** Changed in: livecd-rootfs (Ubuntu)
Hello Robert, or anyone else affected,
Accepted livecd-rootfs into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/livecd-
rootfs/2.525.25 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Robert, or anyone else affected,
Accepted livecd-rootfs into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/livecd-
rootfs/2.408.47 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Robert, or anyone else affected,
Accepted livecd-rootfs into cosmic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/livecd-
rootfs/2.542.4 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
[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/1562653
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
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/1562653
Title:
Ubuntu
[Expired for thunar (Ubuntu) because there has been no activity for 60
days.]
** Changed in: thunar (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/1820765
** 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/1827822
Title:
kernel null pointer dereference
To manage notifications about this
Public bug reported:
ii ubuntu-advantage-tools 10ubuntu0.16.04.1
all management tools for Ubuntu Advantage
cloud-init 18.5-45-g3554ffe8-0ubuntu1~16.04.1
Trying to enable livepatch using ubuntu-advantage cloud-config fails on
Xenial only due to timing of snapd package
cloud-init failure on ubuntu-advantage xenial
** Attachment added: "cloud-init.tar.gz"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1830154/+attachment/5265860/+files/cloud-init.tar.gz
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I think it's appropriate to stay Incomplete because this is essentially
just a kernel bug, in the nouveau driver.
Option (b) above isn't directly relevant, but might be a workaround,
even permanently. Any proper solution to this bug requires testing of
option (a) in comment #4. So still
Passed with Cosmic i386 with proposed kernel.
** Tags removed: verification-needed-cosmic
** Tags added: verification-done-cosmic
** Changed in: ubuntu-kernel-tests
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Public bug reported:
This test has passed with Cosmic kernel on the same node ("baltar"), but
not with the 4.18 kernel on Bionic.
selftests: ebb: cycles_test
test: cycles
tags: git_version:unknown
EBB Handler is at 0x10004170
ebb_state:
ebb_count =
** Bug watch added: Debian Bug tracker #929417
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929417
** Also affects: debconf (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929417
Importance: Unknown
Status: Unknown
** Also affects: debconf (Ubuntu)
Just one update, if I change the perms of the symlink made (chown -h)
the OSD will actually start.
After rebooting, however, I found that the links I had made had gone
again and the whole process needed repeating in order to start the OSD.
--
You received this bug notification because you are a
Please undo the incomplete. The action that was asked for was performed
in the comment #2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830029
Title:
nouveau driver for nvidia is sluggish on
Your Intel GPU, which usually is the only GPU wired directly to the
laptop screen, requires modesetting to be enabled. I recall old versions
of the Nvidia driver did not like that, but current versions do. I think
"current" includes Ubuntu 18.04.
As for the grub menu, yes it might have become
I will give that a go. The nomodeset option was set during istall,
presumably because the live usb install media doesn't boot without it. I
vaguely recall altering that option at the grub menu, but it was a long
day yesterday, so I am not sure (as an aside, why does the grub menu not
come up with
Please do a test:
add "snd_hda_intel.model=lifebook-extmic" in the bootargs (kernel
bootargs). After booting up, please a headset, does the headset-mic
work?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Reviewed: https://review.opendev.org/656307
Committed:
https://git.openstack.org/cgit/openstack/nova/commit/?id=8241b47967adb792a4254eeb58fda1fc55edf314
Submitter: Zuul
Branch:stable/rocky
commit 8241b47967adb792a4254eeb58fda1fc55edf314
Author: Corey Bryant
Date: Thu Feb 7 10:12:54 2019
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779756
Title:
Intel XL710 - i40e driver does not work with kernel 4.15 (Ubuntu
18.04)
To manage notifications about this bug go
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1814095
Title:
bnxt_en_po: TX timed out triggering Netdev Watchdog Timer
To manage notifications about this bug go to:
** Tags added: sts
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic verification-done-cosmic
** Tags removed: verification-done-cosmic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794232
Title:
Geneve tunnels don't work when ipv6 is disabled
To manage notifications about this bug go to:
I had the same error as #5 installing Ubuntu 18.04
I ended up finding a solution from an SO post from 2015 (!)
https://askubuntu.com/questions/502307/the-attempt-to-mount-a-file-
system-with-type-vfat-in-ssi10-0-0-partition1sda
mkfs.vfat /dev/sdb1 worked for me to format the EFI partition and
I installed from a USB stick, by the way, not from DVD
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1423830
Title:
Ubiquity hangs if the ESP can not be mounted
To manage notifications about this
Please test this dkms under 5.0 kernel, if the sound changes better?
To install this deb:
sudo dpkg -i oem-audio-xxx.deb
reboot
check your sound
To remove this deb:
sudo dpkg -P oem-audio-hda-daily-dkms
reboot
** Attachment added: "oem-audio-hda-daily-dkms_0.1_all.deb"
Your kernel log in comment #2 is showing a lot of crashes in the nouveau
kernel driver. The best and only remedies for that are:
(a) Install a newer kernel or just install a newer version of Ubuntu.
Ubuntu 19.04: http://releases.ubuntu.com/19.04/ or kernel packages:
** Package changed: gdm3 (Ubuntu) => nvidia-graphics-drivers-390
(Ubuntu)
** Tags added: nvidia
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/183
Title:
NVIDIA driver (390) does not allow
You appear to be using a kernel parameter ('nomodeset') which will
definitely break the nouveau driver and prevent it from working. To fix
this, please:
1. Edit /etc/default/grub and remove 'nomodeset'.
2. Run: sudo update-grub
3. Reboot
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
**
The same on Lenovo desktop, had to downgrade to 4.4.0-146.
Kernel driver in use: i915
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829657
Title:
Ubuntu 16.04 with kernel 4.4.0-148 hangs on boot
It is likely this bug has already been fixed in a newer version of
Ubuntu.
Please try live booting these from USB to see if they have the same
problem (open the 'Cheese' app to test the camera):
* 18.04 LTS: http://releases.ubuntu.com/18.04.2/
* 19.04: http://releases.ubuntu.com/19.04/
--
Thanks. It appears the kernel doesn't detect/support your camera, so I
am reassigning this bug to the kernel.
** Summary changed:
- Getting raedon error when booting
+ Camera is not detected
** Summary changed:
- Camera is not detected
+ [HP ProBook 450 G0] Camera is not detected
** Package
Oh, actually your XorgLog files suggest the problem is just that the
Nvidia driver is not properly installed. And your kernel log seems to
show that you are using a kernel option ('nomodeset') which will prevent
the Intel GPU from driving the screen properly.
To fix these issues, please:
1. Edit
OK, the system log should contain a hint of the problem. Unfortunately
that's not yet attached to this bug.
Please reproduce the problem again and while it is happening, log in
remotely. Now run:
journalctl -b0 > curjournal.txt
and attach the file 'curjournal.txt' to this bug.
--
You
Ubuntu 18.10 (which does not have the bug) uses kernel version 4.18 so
please start testing versions around there. If you find 4.18 fixes the
bug then next please find a version roughly halfway between 4.18 and
5.0.0 ...
--
You received this bug notification because you are a member of Ubuntu
Launchpad has imported 6 comments from the remote bug at
https://bugzilla.mozilla.org/show_bug.cgi?id=1553554.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
Learned something new today. :)
No crash here starting Mozilla/5.0 (X11; Linux x86_64; rv:60.0)
Gecko/20100101 Thunderbird/60.6.1 from Ubuntu with GTK_USE_PORTAL=1
thunderbird -p on Ubuntu 18.04.2 LTS.
I did get this message in the terminal.
"JavaScript error:
Hi Wayne,
I tried recompiling Thunderbird but, despite adding the proper configuration
switches to add debug symbols, apparently the build process did not add them.
I can also confirm that the crash does not happen with Firefox (I tested
it with the Arch Linux provided package, version
Patch submitted upstream:
https://www.spinics.net/lists/netdev/msg571753.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829652
Title:
Kernel panic upon resetting ixgbe SR-IOV VFIO virtual
Public bug reported:
$ lsb_release -rd
Description:Pop!_OS 19.04
Release:19.04
apt-cache policy gimp
gimp:
Installed: 2.10.10+om-1ubu19.04.25~ppa
Candidate: 2.10.10+om-1ubu19.04.25~ppa
Version table:
*** 2.10.10+om-1ubu19.04.25~ppa 500
500
Thank you for the update and the explanation. I will post some feedback
on gitlab.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827751
Title:
Shield screen is displayed after blanking even when
** Changed in: gnome-control-center
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/1810660
Title:
vpn configuration requires to enter a gateway
To manage notifications
With chance of regression quite low, we will not remove this particular
fix prior to release
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824259
Title:
Headphone jack switch sense is inverted:
The attachment "lttng-modules_2.10.5-1ubuntu1.3.debdiff" seems to be a
debdiff. The ubuntu-sponsors team has been subscribed to the bug report
so that they can review and hopefully sponsor the debdiff. If the
attachment isn't a patch, please remove the "patch" flag from the
attachment, remove
** Also affects: livecd-rootfs (Ubuntu Disco)
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/1829944
Title:
magic-proxy does not send along headers for
Hello David, any new information on this problem?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828134
Title:
Wifi not working after suspend/resume cycle
To manage notifications about this bug go
When deploying from maas, using this proposed version of cloud-init, the
deployment fails. More detail is available in
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1830129
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Kai-Heng Feng, thanks for your time.
I would like to help but I have never installed mainline kernel before. Is it
safe? Is it necessary since we know that this bug appeared after upgrade from
Ubuntu 16.04 to 18.04 (so it didn't affect kernels before 4.15)? This is my
only laptop and it is
Do I have to downgrade my system from Dingo to Cosmic in order to test
this in Cosmic, to keep my bug from being closed?
May 20, 2019 7:02 AM, "Ubuntu Kernel Bot" wrote:
> This bug is awaiting verification that the kernel in -proposed solves
> the problem. Please test the kernel and update this
Public bug reported:
Deployment fails when maas curtin_userdata is set to install cloud-init
from proposed.
ubuntu@maas:~$ diff -u curtin_userdata-20190522.orig
/etc/maas/preseeds/curtin_userdata
--- curtin_userdata-20190522.orig 2019-05-22 16:54:35.745391284 +
+++ /etc/maas/preseeds
** Attachment added: "hoskins_console.proposed_cloud-init"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1830129/+attachment/5265831/+files/hoskins_console.proposed_cloud-init
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Added field-critical, there's a cloud deploy ongoing where I currently
can't reboot any hosts, nor get some of the OSDs back from a host I
rebooted, until we have a workaround.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
OK, in the interest of full disclosure, here is a bit more about the
root of my problems. I was trying to use this in a virtualized
environment. It turns out that the kernel compiled didn't include the
nfsd module which led to the above error of "unknown filesystem type
'nfsd'". A crafty colleague
@hui.wang
I did what you told me to do.
Please check attachment file. I extracted this from the /tmp/ path.
** Attachment added: "alsa-info.txt.jVPW6t7Y5W"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1821269/+attachment/5265827/+files/alsa-info.txt.jVPW6t7Y5W
--
You received
I'm seeing this in a slightly different manner, on Bionic/Queens.
We have LVMs encrypted (thanks Vault), and rebooting a host results in
at least one OSD not returning fairly consistently. The LVs appear in
the list, however the difference between a working and a non-working OSD
is the lack of
*** This bug is a security vulnerability ***
Public security bug reported:
Intel is still working on Sandy Bridge microcode (sigs 0x000206d7 and
0x000206d6) to address MDS. This bug report is for people to track their
status in Ubuntu.
** Affects: intel-microcode (Ubuntu)
Importance:
All releases of Ubuntu (except for Ubuntu 12.04 ESM, where the kernel
does not support early microcode loading, and the changes to add support
are significant and would likely introduce regressions) received
backported intel-microcode updates for Spectre/Meltdown.
Closing this bug. Thanks.
**
Chris, thanks for confirming which processor is in use.
To force downgrade the microcode package on bionic, do:
sudo apt install intel-microcode=3.20180312.0~ubuntu18.04.1
For other releases, you will need to replace the version with what
version(s) are available for your release; you can use
An alternative (preferable IMO, and probably simpler) is to make the
dock configurable to always hide.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1711377
Title:
Nautilus desktop mode should
^^^ sorry this cpuinfo was off a ux433fn booted on an affected kernel
with dis_ucode_ldr
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829620
Title:
intel-microcode on ASUS makes kernel stuck
** Changed in: ubiquity (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1829873
Title:
gpgv fails on install
To manage notifications about this bug go
** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/issues #138
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/138
** Also affects: gnome-control-center via
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/138
Importance: Unknown
Status: Unknown
*** This bug is a duplicate of bug 1810660 ***
https://bugs.launchpad.net/bugs/1810660
Thanks, it looks like bug #1810660 then
** This bug has been marked a duplicate of bug 1810660
vpn configuration requires to enter a gateway
--
You received this bug notification because you are a
Steve, Mark, I've had bios version 302 installed since the 5th of April
and was booting fine until the apt-get upgrade run on the 21st of May
note in my proc/cpuinfo the microcode version is listed as 0x98
also how do you force a downgrade of the microcode package?
** Attachment added:
*** This bug is a duplicate of bug 1711377 ***
https://bugs.launchpad.net/bugs/1711377
Thank you for your bug report, that has been already reported as bug
#1711377
** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
Importance: Undecided => Low
** This bug has been marked a
** Changed in: firefox (Ubuntu)
Status: New => Triaged
** Changed in: firefox (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1830096
Title:
Firefox
** Tags added: canonical-bootstack
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828617
Title:
Hosts randomly 'losing' disks, breaking ceph-osd service enumeration
To manage notifications about
Attach file nocloud-kvm-sru-19.1.1.txt.
** Attachment added: "nocloud-kvm-sru-19.1.1.txt"
https://bugs.launchpad.net/bugs/1828637/+attachment/5265820/+files/nocloud-kvm-sru-19.1.1.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Changed in: df-libreoffice
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/1826757
Title:
libreoffice in 19.04 not responding on ODT, working on ODS
To manage
Attach file nocloud-lxd-sru-19.1.1.txt.
** Attachment added: "nocloud-lxd-sru-19.1.1.txt"
https://bugs.launchpad.net/bugs/1828637/+attachment/5265821/+files/nocloud-lxd-sru-19.1.1.txt
** Attachment removed: "nocloud-kvm-sru-19.1.1.txt"
Works with 6.3.0.0.alpha1+
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826757
Title:
libreoffice in 19.04 not responding on ODT, working on ODS
To manage notifications about this bug go to:
Unconfirmed on windows 7 x64 with Version: 6.2.3.2 (x64)
Build ID: aecc05fe267cc68dde00352a451aa867b3b546ac
CPU threads: 3; OS: Windows 6.1; UI render: default; VCL: win
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Intel microcode update definitely created same issue for me on Asus
Zenbook 14 (UX433F) on 18.04.2 LTS.
Can also confirm the instructions above "add dis_ucode_ldr to the kernel
command line (from GRUB if you cannot boot)" worked perfectly for
temporary workaround.
This is my fourth Asus, and
it takes 1 second in
Version: 6.3.0.0.alpha1+
Build ID: 33cc1debf963c503636cf9219aa81d1a6cf2e943
CPU threads: 4; OS: Linux 4.15; UI render: default; VCL: gtk3;
Locale: ca-ES (ca_ES.UTF-8); UI-Language: en-US
Calc: threaded
and
Version: 6.2.5.0.0+
Build ID:
Public bug reported:
The pam_mount module does not mount the volumes that contain defined
control attributes (user, pgrp, sgrp, uid, and gid).
I believe that it simply ignores all volume tags that contain this
control, because even with debug enable ="1" nothing is registered in
syslog. Only
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 1830116
and then change the status of the bug to 'Confirmed'.
If, due to the
*** This bug is a duplicate of bug 1829620 ***
https://bugs.launchpad.net/bugs/1829620
Thanks Mark, it looks like it is a duplicate of
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829620
The temporary solution seems to resolve the problem for now. I added
dis_ucode_ldr parameter to
An extensive yet tactical take on your Career Episodes can help represent
everything that makes you an asset to the Engineers Australia. Career Episodes
can open those closed doors comfortably. They demonstrate the key skills, the
experience, and the expertise you bring along in your
An extensive yet tactical take on your Career Episodes can help represent
everything that makes you an asset to the Engineers Australia. Career Episodes
can open those closed doors comfortably. They demonstrate the key skills, the
experience, and the expertise you bring along in your
** Changed in: heimdal (Debian)
Status: Unknown => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823422
Title:
heimdal ftbfs in disco
To manage notifications about this bug go
.debdiff attached to this comment. Adding SRU paperwork to original bug
description.
** Patch added: "lttng-modules_2.10.5-1ubuntu1.3.debdiff"
https://bugs.launchpad.net/ubuntu/+source/linux-hwe-edge/+bug/1826846/+attachment/5265819/+files/lttng-modules_2.10.5-1ubuntu1.3.debdiff
**
1 - 100 of 568 matches
Mail list logo
