It's not a kernel bug. The nvidia driver keeps the contents of the GRUB
screen and the first two lines of kernel log visible as a frozen static
picture.
Deinstall and reinstall of nvidia drivers fixed the issue.
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received
(In reply to Erik from comment #184)
> @Vladislav Kamenev i still need ivrs to boot 5.1-rc5 kernel.
> Since there was talks about problems with hibernation i even setup a swap
> file and tested hibernation (Suspend to Disk S4) and it works, i normally
> only use suspend (Suspend to RAM S3),
On 16/04/2019 11.31, Robie Basak wrote:
>> Can you explain how the new soname is a problem? I think it
>> clearly separates the new and old libraries.
>
> We can't delete the old library from Bionic, so the new and old must
> exist concurrently. Therefore you can't just upload a replacement
>
Have you updated bios to 1.13?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776563
Title:
Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't
load, kernel freeze (AMD Ryzen
@Vladislav Kamenev i still need ivrs to boot 5.1-rc5 kernel.
Since there was talks about problems with hibernation i even setup a swap file
and tested hibernation (Suspend to Disk S4) and it works, i normally only use
suspend (Suspend to RAM S3), suspend works with all my kernels 4.19+ and ivrs.
I have IOMMU and SVM enabled in bios/UEFI.
I toggled Secure boot setting and it doesn't change anything, hibernation works
anyway and i still need ivrs to boot.
I tried with secure boot enabled and hibernation works with all my kernels
(4.19.34, 5.0.7, 5.1-rc5).
Since i use a swap file for
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/1824815
Title:
With kernel 5.0.0-11-generic and nouveau,
** Changed in: ubuntu-mate-welcome (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1749578
Title:
Incorrect grammar in "Welcome wizard ->
Anyhow, none of this is a bug I nthe dispatcher, and I don't know what
else, so I'm going to reassign it to the kernel - if there are broken
ARP tables and whatnot, what else could it be.
** Package changed: networkd-dispatcher (Ubuntu) => linux (Ubuntu)
--
You received this bug notification
Your logs do not show network dispatcher restarting, but it is reloading
it's list of interfaces as it has to figure out which interface it got
notified about.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: ubuntu-mate-welcome (Ubuntu)
Assignee: (unassigned) => Martin Wimpress (flexiondotorg)
** Changed in: ubuntu-mate-welcome (Ubuntu)
Status: In Progress => Confirmed
** Changed in: ubuntu-mate-welcome (Ubuntu)
Status: Confirmed => Fix Committed
** Changed in:
With new kernel 5.0.0-13-generic, colors and brightness are working
normally.
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: ubuntu-mate
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Openstack patches are tracked in bug 1560965 (this LP is for the SRU
part)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822129
Title:
[SRU] leave device name empty so that nova can determine it
** Merge proposal linked:
https://code.launchpad.net/~slashd/ubuntu/+source/horizon/+git/horizon/+merge/366119
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822129
Title:
[SRU] leave device
** Tags added: regression-testing-passed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824819
Title:
linux: 5.0.0-13.14 -proposed tracker
To manage notifications about this bug go to:
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => 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
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-bionic
** Tags added: block-proposed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
just fyi, this also affects newer iso releases of 18.04 (e.g. 18.04.2)
i suspect the new xorg in the hwe version needs the bochs drm module
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1795857
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubiquity (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/1824195
Title:
** 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/1824980
Title:
package linux-modules-extra-4.4.0-144-generic (not installed) failed
to install/upgrade: cannot
** 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
Public bug reported:
O erro ocorreu durante a atualização de programas.
ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: linux-modules-extra-4.4.0-144-generic (not installed)
ProcVersionSignature: Ubuntu 4.4.0-31.50~14.04.1-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
After testing on the live image, the above mentioned fix solved the
problem. Regardless of when the nvidia driver is actually installed,
having udev (repeatedly) trying to modprobe modules and to start daemons
is a waste of resources on the live image.
Overriding the udev rule works really well,
Public bug reported:
Ubuntu 18.04.2 LTS
Linux SRV013 4.15.0-47-generic #50-Ubuntu SMP Wed Mar 13 10:44:52 UTC 2019
x86_64 x86_64 x86_64 GNU/Linux
DELL R740, 2 CPU (40 Cores, 80 Threads), 384 GiB RAM
top - 12:39:53 up 3:41, 4 users, load average: 66.19, 64.06, 76.90
Tasks: 1076 total, 1
Ubuntu:
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 18.04.1 LTS
Release:18.04
Codename: bionic
--
root@u18_svr_madsz:/icxmSim/dist# ifconfig
ens33: flags=4163 mtu 1500
inet 10.206.49.229 netmask
Failed Logs:
--
Apr 16 10:56:27 u18_svr_madsz systemd-udevd[30948]: link_config:
autonegotiation is unset or enabled, the speed and duplex are not writable.
Apr 16 10:56:27 u18_svr_madsz systemd-udevd[30948]: Could not generate
persistent MAC address for 2icx0: No such file or directory
Apr
** Changed in: kernel-sru-workflow/stakeholder-signoff
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824376
Title:
linux-azure: 5.0.0-1003.3 -proposed tracker
I checked case (B) that I added.
First I created a new setup as described (to make sure no old modifications
influence the verification)
That worked, I saw the wait line on boot:
[*** ] A start job is running for Wait for… to be Configured (29s / no limit)
After boot I had the wait time in the
** 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 see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
** Changed in: kernel-sru-workflow/stakeholder-signoff
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824834
Title:
linux-azure: 5.0.0-1004.4 -proposed tracker
Had another failure with similar symptoms (fan on, screen black once
laptop lid opened), but logs look different this time.
** Attachment added: "differentfailure.txt"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823029/+attachment/5256275/+files/differentfailure.txt
--
You
*** This bug is a duplicate of bug 1817924 ***
https://bugs.launchpad.net/bugs/1817924
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-shell (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of
> they have to do with python applications with apport hooks that are
confined with apparmor.
The hook is defined in site.py, so by definition all python applications
have the hook, and thus all python applications that are confined with
apparmor.
So either we want that apport for all of them,
This bug was fixed in the package linux-aws - 5.0.0-1004.4
---
linux-aws (5.0.0-1004.4) disco; urgency=medium
* linux-aws: 5.0.0-1004.4 -proposed tracker (LP: #1824833)
[ Ubuntu: 5.0.0-13.14 ]
* linux: 5.0.0-13.14 -proposed tracker (LP: #1824819)
* Display only has 640x480
This bug was fixed in the package casper - 1.405
---
casper (1.405) disco; urgency=medium
[ Dimitri John Ledkov ]
* scripts/casper-bottom/25adduser:
- Make boot non-degraded, by clearing the lock. As otherwise
systemd-sysusers fails and boots the system degraded on
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-cosmic
** Tags added: block-proposed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
The package unattended-upgrades=1.10ubuntu5 fixes the problem on Ubuntu
18.04 LTS bionic.
** Tags removed: verification-needed verification-needed-disco
** Tags added: verification-done verification-done-disco
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Gah, typo:
> so the linker finds the GCC 9 ones in libstdc++.so.6.0.25 and uses
them
That should have said libstdc++.so.6.0.26 - sorry for any confusion.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
>From the logs:
Setting up linux-firmware (1.175.1) ...
update-initramfs: Generating /boot/initrd.img-4.18.0-17-generic
/usr/sbin/mkinitramfs: 165: /usr/sbin/mkinitramfs: Cannot fork
/usr/sbin/mkinitramfs: 225: /usr/sbin/mkinitramfs: Cannot fork
/usr/sbin/mkinitramfs: 183: /usr/sbin/mkinitramfs:
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-bionic
** Tags added: block-proposed
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
** Changed in: kernel-sru-workflow/promote-to-proposed
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy
Whitcroft (apw)
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => In Progress
--
You received this bug notification because you are a member
Ok, well, no idea what happened, but I did a hard power cycle with that
kernel parameter, and it started working. I rebooted again without it,
and it still worked. Perhaps the hard power cycle did something
different this time with the new BIOS, but I thought I had done that
since. In any event,
Yes i got bios 1.13.
The bug with being forced to add my grub as trusted file was in earlier bios
and i don't know if it's still in the latest bios as i haven't tried it out.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I might also mention on IRC the exact type of thing why we've had these
rules in the profile that ship them:
[119698.000187] audit: type=1400 audit(1555405334.985:222):
apparmor="DENIED" operation="exec" profile="/usr/sbin/kopano-search"
name="/usr/bin/x86_64-linux-gnu-gcc-8" pid=15647
it's exactly the same procedure has describe in Debian bug.
In fact I configure a yubikey with a ssh key inside.
Whenever I try to connect somewhere, where I'm sure my pub key is I get:
sign_and_send_pubkey: signing failed: agent refused operation
--
You received this bug notification
Not fixable for X. Does not occur on Wayland.
See: https://bugs.kde.org/show_bug.cgi?id=383327
and https://bugs.kde.org/show_bug.cgi?id=70063
** Changed in: kde-baseapps (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Not fixable for X.
See: https://bugs.kde.org/show_bug.cgi?id=70063
and https://bugs.kde.org/show_bug.cgi?id=70063
** Bug watch added: KDE Bug Tracking System #70063
https://bugs.kde.org/show_bug.cgi?id=70063
** Bug watch added: KDE Bug Tracking System #383327
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => 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
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => 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
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: Confirmed => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Canonical Kernel Team (canonical-kernel-team) => Marcelo Cerri
(mhcerri)
** Description changed:
This bug will contain
Traditionally we have actually put these accesses in the packages that
ship the profile, like Marc said, because profilers may not want the
profile to automatically have everything apport requires. These accesses
should *not* be in the python abstraction because the accesses have
nothing to do
@Mike, arguing over the triaging details isn't really that useful, but
for the record see https://wiki.ubuntu.com/Bugs/Importance. The battery
estimate is indeed useful, but you are so far the only one reporting the
issues and one report isn't enough to consider it as High then (for what
we know
** Changed in: kernel-sru-workflow/regression-testing
Status: Confirmed => 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
** Changed in: kernel-sru-workflow/prepare-package-signed
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
** 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 see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: bug 1824839
** 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 see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
Thank you for your bug report. Could you get a debug log as described on
https://wiki.gnome.org/Projects/NetworkManager/Debugging
#Debugging_NetworkManager-openvpn ? (you need to reboot or 'sudo
systemctl restart NetworkManager' before starting the client in debug)
** Changed in:
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: In Progress => New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824592
Title:
linux-fips: 4.15.0-1005.6 -proposed tracker
To
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-bionic
** Tags added: block-proposed
** Description changed:
This bug will
@Steve, right, I just gave it a try and indeed n-m needs to be restarted
('sudo systemctl restart NetworkManager' is enough, no need of
rebooting)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1800542
Closing because I can no longer reproduce this and there has not been
any response for several years. If you have a similar issue, please file
a new bug at https://gitlab.com/inkscape/inbox. Thank you!
Closed by: https://gitlab.com/Qantas94Heavy
** Changed in: inkscape
Status: New =>
** Changed in: gnome-bluetooth (Ubuntu Cosmic)
Assignee: (unassigned) => Sebastien Bacher (seb128)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1777062
Title:
Logitech M535 mouse only pairs
Thank you for the report but Cosmic build issues are low priority at
this point, tagging as rls-cc-notfixing , that doesn't stop fixing those
problems but they are not going to be tracked as rls issues
** Tags removed: rls-cc-incoming
** Tags added: rls-cc-notfixing
--
You received this bug
** Tags added: rls-dd-notfixing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1734095
Title:
Software & Updates not showing authorization popup [gnome-shell[N]:
pushModal: invocation of
xnox, would you please elaborate what "in unapproved" means ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1764628
Title:
incorrect hypervisor and virtualization type reported in compat mode
(same in ubuntu)
** Changed in: inkscape (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1044064
Title:
inkscape freezes in 12.10 after clicking on fonts
Public bug reported:
chzdev export/prepare-for-import/import bombs out on import in python3.6
like so:
Apr 16 14:05:49 ubuntu-server curtin_log.1663[1766]: Running command ['chzdev',
'--quiet', '--persistent', '--no-root-update', '--base', '/etc=/target/etc',
'--import', '-'] with allowed
To restore the touchpad after a disconnect you want to try modprobe -r
hid-multitouch && modprobe hid-multitouch. You shouldn't need to reset
i2c-hid unless it's a last resort and resetting hid-multitouch didn't
work.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
If I unplug the charger and reboot, the command issues the following
(100% always):
upower -d
Device: /org/freedesktop/UPower/devices/line_power_AC0
native-path: AC0
power supply: yes
updated: Вт 16 апр 2019 18:06:47 (313 seconds ago)
has history: no
Here is a script I made for resetting the touchpad with the gnome
keyring (because it requires sudo priviledge).
#!/bin/bash
if [ -z $1 ]
then
echo 'rsmod unloads and reloads kernel modules with modprobe'
echo 'usage: rsmod '
echo 'Requires root privileges'
** Changed in: ubuntu-power-systems
Status: In Progress => Fix Released
** Changed in: ubuntu-power-systems
Status: Fix Released => Fix Committed
** Also affects: util-linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: util-linux (Ubuntu Xenial)
The verification of the Stable Release Update for nova has completed
successfully and the package has now been released to -updates. In the
event that you encounter a regression using the package from -updates
please report a new bug using ubuntu-bug and tag the bug report
regression-update so we
The verification of the Stable Release Update for nova has completed
successfully and the package has now been released to -updates. In the
event that you encounter a regression using the package from -updates
please report a new bug using ubuntu-bug and tag the bug report
regression-update so we
This bug was fixed in the package nova - 2:16.1.7-0ubuntu1~cloud2
---
nova (2:16.1.7-0ubuntu1~cloud2) xenial-pike; urgency=medium
.
* d/p/(re)fix-disk-size-during-live-migration-with-disk-over-commit.patch:
Cherry-picked from upstream stable/pike branch to ensure disk size
This bug was fixed in the package nova - 2:15.1.5-0ubuntu1~cloud3
---
nova (2:15.1.5-0ubuntu1~cloud3) xenial-ocata; urgency=medium
.
* d/p/(re)fix-disk-size-during-live-migration-with-disk-over-commit.patch:
Cherry-picked from upstream ocata gerrit reviews to ensure disk
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that there was an error on your system when
trying to install a particular package. Please execute the following
command, as it will clear your package cache, in a terminal:
sudo apt-get clean
Then try
*** This bug is a duplicate of bug 1292398 ***
https://bugs.launchpad.net/bugs/1292398
I can confirm that it's not fixed. Rebooting has become a major problem
for me because it loses my display settings, corrupts the displays, and
I spend 20 minutes fixing everything.
--
You received this
It's in the xenial-proposed queue.
Marking fixed for trunk.
** Changed in: util-linux (Ubuntu)
Status: In Progress => 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/1764628
** Attachment added: "Last 250 lines of journalctl log for shutdown"
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1824893/+attachment/5256268/+files/journalctl.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've added the last 250 lines of the log, if that's not enough let me
know. Once it says it's reached target reboot the next thing it does is
send a kill signal to all processes, including journalctl so there is not
much useful information beyond that point. Also I can not switch virtual
problem occurs when both interface created using multiprocessing module of
python
Process 1 execution ->
ip link add link ens34 2icx0 type macvlan
ifconfig 2icx0 up
ip addr add 192.168.49.230/16 dev 2icx0
Process 2 execution ->
ip link add link ens34 2icx1 type macvlan
ifconfig
** Changed in: kernel-sru-workflow/automated-testing
Status: Incomplete => 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
** Tags added: regression-testing-passed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824834
Title:
linux-azure: 5.0.0-1004.4 -proposed tracker
To manage notifications about this bug go to:
@infinity has found a fix for this in Debian and is looking at syncing
it now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824103
Title:
aplay record file failed always.
To manage notifications
SRU validated, no issues found. Logs:
xenial: https://paste.ubuntu.com/p/9jdjdQns7t/
bionic: https://paste.ubuntu.com/p/P6CZ5WnmmB/
** Tags removed: verification-needed verification-needed-bionic
verification-needed-xenial
** Tags added: verification-done verification-done-bionic
lp1822129-cosmic.debdiff
** Patch added: "lp1822129-cosmic.debdiff"
https://bugs.launchpad.net/ubuntu/bionic/+source/horizon/+bug/1822129/+attachment/5256277/+files/lp1822129-cosmic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
lp1822129-bionic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822129
Title:
[SRU] leave device name empty so that nova can determine it instead
To manage notifications about this bug go
All tasks have been completed and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/automated-testing
Status: Incomplete => Fix Released
** Changed in: kernel-sru-workflow
Status: In Progress => Fix Released
** Description changed:
This bug will contain
One reason why apparmor may need to be disabled:
Issue:
Apparmor prevents
docker container stop
from working - it blocks the signalling init process. From dmesg, we see
[156522.040461] audit: type=1400 audit(1555422697.325:338):
apparmor="DENIED" operation="signal"
** Changed in: ceph (Ubuntu Bionic)
Importance: Medium => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822872
Title:
Bionic: Luminous radosgw incompatible with libssl1.1
To manage
lp1822129-bionic.debdiff
** Patch added: "lp1822129-bionic.debdiff"
https://bugs.launchpad.net/ubuntu/bionic/+source/horizon/+bug/1822129/+attachment/5256278/+files/lp1822129-bionic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
The problem with suspend/hibernation was with usb3 port not secure boot,
just disable wake from usb devices at xchi0 and xchi1 controllers.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776563
This bug was fixed in the package neutron-dynamic-routing -
2:14.0.0-0ubuntu1~cloud0
---
neutron-dynamic-routing (2:14.0.0-0ubuntu1~cloud0) bionic-stein; urgency=medium
.
* New upstream release for the Ubuntu Cloud Archive.
.
neutron-dynamic-routing (2:14.0.0-0ubuntu1) disco;
This bug was fixed in the package neutron-dynamic-routing -
2:14.0.0-0ubuntu1~cloud0
---
neutron-dynamic-routing (2:14.0.0-0ubuntu1~cloud0) bionic-stein; urgency=medium
.
* New upstream release for the Ubuntu Cloud Archive.
.
neutron-dynamic-routing (2:14.0.0-0ubuntu1) disco;
The may seem to the same, but do the symptoms occur at different time?
The original issue happens at suspending, while #20 occurs at resuming?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823029
** Also affects: horizon (Ubuntu Xenial)
Importance: Undecided
Status: New
** Changed in: horizon (Ubuntu Xenial)
Importance: Undecided => Medium
** Changed in: horizon (Ubuntu Xenial)
Status: New => In Progress
** Changed in: horizon (Ubuntu Xenial)
Assignee:
** Merge proposal linked:
https://code.launchpad.net/~azzar1/ubuntu/+source/gnome-initial-setup/+git/gnome-initial-setup/+merge/366123
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824996
Title:
Public bug reported:
Hi
Today is actually impossible to keep NM translations in good shape since
Zanata (a tool used in Fedora and Red Hat) is messing up the
translations.
Example:
https://translations.launchpad.net/ubuntu/disco/+source/network-
manager/+pots/networkmanager/es/870/+translate
I have exactly the same issue. Started recently. All my gnome extensions
including the lock symbol disappear after returning from an unlock.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1796265
With the package 1.30.1-0ubuntu1.1 from rocky-proposed in place, I ran
through the test case for this and did not hit any failures. I can
verify this fixes the issue for rocky.
** Tags removed: verification-rocky-needed
** Tags added: verification-rocky-done
--
You received this bug
1 - 100 of 996 matches
Mail list logo