This bug was fixed in the package linux - 4.15.0-33.36
---
linux (4.15.0-33.36) bionic; urgency=medium
* linux: 4.15.0-33.36 -proposed tracker (LP: #1787149)
* RTNL assertion failure on ipvlan (LP: #1776927)
- ipvlan: drop ipv6 dependency
- ipvlan: use per device spinlock
This bug was fixed in the package linux - 4.15.0-33.36
---
linux (4.15.0-33.36) bionic; urgency=medium
* linux: 4.15.0-33.36 -proposed tracker (LP: #1787149)
* RTNL assertion failure on ipvlan (LP: #1776927)
- ipvlan: drop ipv6 dependency
- ipvlan: use per device spinlock
This bug was fixed in the package linux - 4.15.0-33.36
---
linux (4.15.0-33.36) bionic; urgency=medium
* linux: 4.15.0-33.36 -proposed tracker (LP: #1787149)
* RTNL assertion failure on ipvlan (LP: #1776927)
- ipvlan: drop ipv6 dependency
- ipvlan: use per device spinlock
This bug was fixed in the package linux - 4.15.0-33.36
---
linux (4.15.0-33.36) bionic; urgency=medium
* linux: 4.15.0-33.36 -proposed tracker (LP: #1787149)
* RTNL assertion failure on ipvlan (LP: #1776927)
- ipvlan: drop ipv6 dependency
- ipvlan: use per device spinlock
This bug was fixed in the package linux - 4.15.0-33.36
---
linux (4.15.0-33.36) bionic; urgency=medium
* linux: 4.15.0-33.36 -proposed tracker (LP: #1787149)
* RTNL assertion failure on ipvlan (LP: #1776927)
- ipvlan: drop ipv6 dependency
- ipvlan: use per device spinlock
This bug was fixed in the package linux - 4.15.0-33.36
---
linux (4.15.0-33.36) bionic; urgency=medium
* linux: 4.15.0-33.36 -proposed tracker (LP: #1787149)
* RTNL assertion failure on ipvlan (LP: #1776927)
- ipvlan: drop ipv6 dependency
- ipvlan: use per device spinlock
This bug was fixed in the package linux - 4.15.0-33.36
---
linux (4.15.0-33.36) bionic; urgency=medium
* linux: 4.15.0-33.36 -proposed tracker (LP: #1787149)
* RTNL assertion failure on ipvlan (LP: #1776927)
- ipvlan: drop ipv6 dependency
- ipvlan: use per device spinlock
This bug was fixed in the package linux - 4.15.0-33.36
---
linux (4.15.0-33.36) bionic; urgency=medium
* linux: 4.15.0-33.36 -proposed tracker (LP: #1787149)
* RTNL assertion failure on ipvlan (LP: #1776927)
- ipvlan: drop ipv6 dependency
- ipvlan: use per device spinlock
This bug was fixed in the package linux - 4.15.0-33.36
---
linux (4.15.0-33.36) bionic; urgency=medium
* linux: 4.15.0-33.36 -proposed tracker (LP: #1787149)
* RTNL assertion failure on ipvlan (LP: #1776927)
- ipvlan: drop ipv6 dependency
- ipvlan: use per device spinlock
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed => Fix Committed
** Changed in: kernel-sru-workflow/promote-to-updates
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz
Zemczak (sil2100)
** Changed in: kernel-sru-workflow/promote-to-security
** Changed in: kernel-sru-workflow/snap-release-to-candidate
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/1787184
Title:
linux-snapdragon: 4.4.0-1099.104 -p
** Changed in: kernel-sru-workflow/snap-release-to-candidate
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/1787183
Title:
linux-raspi2: 4.4.0-1095.103 -propo
I built a test kernel with commit db2173198b95. The test kernel can be
downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1788549
Can you test this kernel and see if it resolves this bug?
Note about installing test kernels:
• If the test kernel is prior to 4.15(Bionic) you need to install
In the attempt to workaround that behaviour at least for Landscape USN.
Would it be doable to force the package upgrade in Landscape by pocket
instead of package version ?
Fetching the package list from the USN file, then instead of ordering a
specific version, just mentioning where to go to find
# apt-get install --dry-run -t xenial-security systemd
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following additional packages will be installed:
libpam-systemd libsystemd0
Suggested packages:
systemd-ui systemd-container
The following p
This bug was fixed in the package linux-kvm - 4.15.0-1020.20
---
linux-kvm (4.15.0-1020.20) bionic; urgency=medium
* linux-kvm: 4.15.0-1020.20 -proposed tracker (LP: #1787158)
* DEBUG_WX is not set in Bionic KVM kernel (LP: #1782721)
- kvm: [Config] enable CONFIG_DEBUG_WX
This bug was fixed in the package linux - 4.15.0-33.36
---
linux (4.15.0-33.36) bionic; urgency=medium
* linux: 4.15.0-33.36 -proposed tracker (LP: #1787149)
* RTNL assertion failure on ipvlan (LP: #1776927)
- ipvlan: drop ipv6 dependency
- ipvlan: use per device spinlock
This bug was fixed in the package linux - 4.15.0-33.36
---
linux (4.15.0-33.36) bionic; urgency=medium
* linux: 4.15.0-33.36 -proposed tracker (LP: #1787149)
* RTNL assertion failure on ipvlan (LP: #1776927)
- ipvlan: drop ipv6 dependency
- ipvlan: use per device spinlock
This bug was fixed in the package linux - 4.15.0-33.36
---
linux (4.15.0-33.36) bionic; urgency=medium
* linux: 4.15.0-33.36 -proposed tracker (LP: #1787149)
* RTNL assertion failure on ipvlan (LP: #1776927)
- ipvlan: drop ipv6 dependency
- ipvlan: use per device spinlock
This bug was fixed in the package linux-aws - 4.15.0-1020.20
---
linux-aws (4.15.0-1020.20) bionic; urgency=medium
* linux-aws: 4.15.0-1020.20 -proposed tracker (LP: #1787154)
[ Ubuntu: 4.15.0-33.36 ]
* linux: 4.15.0-33.36 -proposed tracker (LP: #1787149)
* RTNL assertion f
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed => Fix Committed
** Changed in: kernel-sru-workflow/promote-to-updates
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz
Zemczak (sil2100)
** Changed in: kernel-sru-workflow/promote-to-security
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed => Fix Committed
** Changed in: kernel-sru-workflow/promote-to-updates
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz
Zemczak (sil2100)
** Changed in: kernel-sru-workflow/promote-to-security
This bug was fixed in the package linux-gcp - 4.15.0-1018.19
---
linux-gcp (4.15.0-1018.19) bionic; urgency=medium
* linux-gcp: 4.15.0-1018.19 -proposed tracker (LP: #1787156)
* linux-gcp: add a signed kernel (LP: #1782557)
- [Configuration] enable EFI signing support
[ Ub
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Confirmed => Fix Committed
** Changed in: kernel-sru-workflow/promote-to-updates
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz
Zemczak (sil2100)
** Changed in: kernel-sru-workflow/promote-to-security
This bug was fixed in the package linux-aws - 4.15.0-1020.20
---
linux-aws (4.15.0-1020.20) bionic; urgency=medium
* linux-aws: 4.15.0-1020.20 -proposed tracker (LP: #1787154)
[ Ubuntu: 4.15.0-33.36 ]
* linux: 4.15.0-33.36 -proposed tracker (LP: #1787149)
* RTNL assertion f
As we have experienced a regression in bionic-updates due to gnome-shell
building against newer mutter, I will be conditionally releasing this
package without this bug verified as it seems it is not easily
verifiable by unaffected users. The change is enough self-contained that
it appears to be saf
This bug was fixed in the package linux-raspi2 - 4.15.0-1021.23
---
linux-raspi2 (4.15.0-1021.23) bionic; urgency=medium
* linux-raspi2: 4.15.0-1021.23 -proposed tracker (LP: #1787151)
* Bionic update: upstream stable patchset 2018-06-26 (LP: #1778759)
- [Config] raspi2: CONF
This bug was fixed in the package mutter - 3.28.3-2~ubuntu18.04.1
---
mutter (3.28.3-2~ubuntu18.04.1) bionic; urgency=medium
* No-change backport from unstable to bionic
mutter (3.28.3-2) unstable; urgency=medium
* Team upload
[ Iain Lane ]
* debian/gbp.conf: Set the upstre
This bug was fixed in the package mutter - 3.28.3-2~ubuntu18.04.1
---
mutter (3.28.3-2~ubuntu18.04.1) bionic; urgency=medium
* No-change backport from unstable to bionic
mutter (3.28.3-2) unstable; urgency=medium
* Team upload
[ Iain Lane ]
* debian/gbp.conf: Set the upstre
The verification of the Stable Release Update for mutter has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a r
This bug was fixed in the package linux-kvm - 4.15.0-1020.20
---
linux-kvm (4.15.0-1020.20) bionic; urgency=medium
* linux-kvm: 4.15.0-1020.20 -proposed tracker (LP: #1787158)
* DEBUG_WX is not set in Bionic KVM kernel (LP: #1782721)
- kvm: [Config] enable CONFIG_DEBUG_WX
This bug was fixed in the package linux-gcp - 4.15.0-1018.19
---
linux-gcp (4.15.0-1018.19) bionic; urgency=medium
* linux-gcp: 4.15.0-1018.19 -proposed tracker (LP: #1787156)
* linux-gcp: add a signed kernel (LP: #1782557)
- [Configuration] enable EFI signing support
[ Ub
This bug was fixed in the package linux-gcp - 4.15.0-1018.19
---
linux-gcp (4.15.0-1018.19) bionic; urgency=medium
* linux-gcp: 4.15.0-1018.19 -proposed tracker (LP: #1787156)
* linux-gcp: add a signed kernel (LP: #1782557)
- [Configuration] enable EFI signing support
[ Ub
This bug was fixed in the package mutter - 3.28.3-2~ubuntu18.04.1
---
mutter (3.28.3-2~ubuntu18.04.1) bionic; urgency=medium
* No-change backport from unstable to bionic
mutter (3.28.3-2) unstable; urgency=medium
* Team upload
[ Iain Lane ]
* debian/gbp.conf: Set the upstre
This bug was fixed in the package linux-raspi2 - 4.15.0-1021.23
---
linux-raspi2 (4.15.0-1021.23) bionic; urgency=medium
* linux-raspi2: 4.15.0-1021.23 -proposed tracker (LP: #1787151)
* Bionic update: upstream stable patchset 2018-06-26 (LP: #1778759)
- [Config] raspi2: CONF
The verification of the Stable Release Update for mutter has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a r
This bug was fixed in the package mutter - 3.28.3-2~ubuntu18.04.1
---
mutter (3.28.3-2~ubuntu18.04.1) bionic; urgency=medium
* No-change backport from unstable to bionic
mutter (3.28.3-2) unstable; urgency=medium
* Team upload
[ Iain Lane ]
* debian/gbp.conf: Set the upstre
This bug was fixed in the package mutter - 3.28.3-2~ubuntu18.04.1
---
mutter (3.28.3-2~ubuntu18.04.1) bionic; urgency=medium
* No-change backport from unstable to bionic
mutter (3.28.3-2) unstable; urgency=medium
* Team upload
[ Iain Lane ]
* debian/gbp.conf: Set the upstre
This bug was fixed in the package linux-kvm - 4.15.0-1020.20
---
linux-kvm (4.15.0-1020.20) bionic; urgency=medium
* linux-kvm: 4.15.0-1020.20 -proposed tracker (LP: #1787158)
* DEBUG_WX is not set in Bionic KVM kernel (LP: #1782721)
- kvm: [Config] enable CONFIG_DEBUG_WX
This bug was fixed in the package mutter - 3.28.3-2~ubuntu18.04.1
---
mutter (3.28.3-2~ubuntu18.04.1) bionic; urgency=medium
* No-change backport from unstable to bionic
mutter (3.28.3-2) unstable; urgency=medium
* Team upload
[ Iain Lane ]
* debian/gbp.conf: Set the upstre
This bug was fixed in the package linux-kvm - 4.15.0-1020.20
---
linux-kvm (4.15.0-1020.20) bionic; urgency=medium
* linux-kvm: 4.15.0-1020.20 -proposed tracker (LP: #1787158)
* DEBUG_WX is not set in Bionic KVM kernel (LP: #1782721)
- kvm: [Config] enable CONFIG_DEBUG_WX
The verification of the Stable Release Update for mutter has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a r
The verification of the Stable Release Update for mutter has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a r
On Raspberry-Pi and Ubuntu 18.04 LTS no simple work around for me here.
Only work around on Pi is to use the Rasbian interface. So this should
be a critical bug for 18.04 LTS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
Hello Nick,
Thank you for submitting this bug and reporting a problem with cups. You made
this bug report some time ago and Ubuntu has been updated since then.
Could you confirm that this is no longer a problem and that we can close the
Hello Fernando,
Thank you for submitting this bug and reporting a problem with cups. You made
this bug report some time ago and Ubuntu has been updated since then.
Could you confirm that this is no longer a problem and that we can close t
Hello again John!
On this totally different bug report, we begin the conversation again. :)
Thank you for submitting this bug and reporting a problem with cups. You made
this bug report some time ago and Ubuntu has been updated since then.
Hello James,
Thank you for submitting this bug and reporting a problem with cups. You made
this bug report some time ago and Ubuntu has been updated since then.
Could you confirm that this is no longer a problem and that we can close the
Hello Reinach,
Thank you for submitting this bug and reporting a problem with cups. You made
this bug report some time ago and Ubuntu has been updated since then.
Could you confirm that this is no longer a problem and that we can close th
Just upgraded Ubuntu 16.04 LTS to 18.04.1 LTS. PPA that i added in
previous version, can't add it in newer and result is same as mentioned
by others "user or team does not exist."
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
This bug was fixed in the package mutter - 3.28.3-2~ubuntu18.04.1
---
mutter (3.28.3-2~ubuntu18.04.1) bionic; urgency=medium
* No-change backport from unstable to bionic
mutter (3.28.3-2) unstable; urgency=medium
* Team upload
[ Iain Lane ]
* debian/gbp.conf: Set the upstre
** Changed in: sssd (Ubuntu)
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/1430143
Title:
sss_obfuscate breaks /etc/sssd/sssd.conf
To manage notifications about th
*** This bug is a duplicate of bug 1755779 ***
https://bugs.launchpad.net/bugs/1755779
Thank you for taking the time to report this crash and helping to make
this software better. This particular crash has already been reported
and is a duplicate of bug #1755779, so is being marked as such.
** Also affects: shutter (Ubuntu)
Importance: Undecided
Status: New
** Changed in: shutter
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788611
Title:
Can't
Something strange just happened. I clicked on the Gnome "Show
Applications" button (which I never do -- was fidgeting while discussing
something) all but the pointer froze.
Here is the kern.log for the event:
Aug 23 15:32:13 winters kernel: [278586.296029] pool[604]: segfault at 28 ip
7f8cc
@Daniele, go to the Ubuntu or Linuxmint forums or documentation and look up the
command:
sudo dpkg -i *.deb
And you might have to update Grub as well.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/172
** Changed in: maas
Milestone: 2.5.0alpha2 => 2.5.0beta1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1607345
Title:
Collect all logs needed to debug curtin/cloud-init for each deployment
To m
** 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/1788620
Title:
package keyboard-configuration 1.178ubuntu2.6 failed to
install/upgrade: installed keyboard-confi
Had this too, for the first time, on Ubuntu 18.04 LTS.
[287327.941338] [drm] Reducing the compressed framebuffer size. This may lead
to less power savings than a non-reduced-size. Try to increase stolen memory
size if available in BIOS.
[287336.517202] [drm] Reducing the compressed framebuffer s
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 1788616
and then change the status of the bug to 'Confirmed'.
If, due to the nature
** Patch added: "fix to .config file"
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1788597/+attachment/5179744/+files/console-setup_1.178ubuntu2.6.dsc.diff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bug
Public bug reported:
Ubuntu 18.4.1 Upgrade Fail
sudo do-release-upgrade
Termanal:
Could not calculate the upgrade
An unresolvable problem occurred while calculating the upgrade.
This can be caused by:
* Upgrading to a pre-release version of Ubuntu
* Running the current pre-release version o
** 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/1788618
Title:
package python3-lazr.uri 1.0.3-2build1 failed to install/upgrade:
installed python3-lazr.uri pack
Public bug reported:
Using the Ubuntu 18.04.1 LTS default kernel 4.15.0-32-generic system
hangs/stalls during boot displaying the error shown below, kernels 4.13
and 4.17 don't show this bug. This seem to be an extended APIC issue in
the kernel on certain xeon skylake models and was already patche
Public bug reported:
installing updates
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: python3-lazr.uri 1.0.3-2build1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Thu Aug 23 10
Public bug reported:
My latest update for Ubuntu failed. I did not really focus on the error
reported though, Apologies for the same.
ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: keyboard-configuration 1.178ubuntu2.6
ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
Uname: Li
The nature of the bug prevents to boot the system with that kernel, as
such, apport-collect can't be executed.
** 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:
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-security
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Fix Committed => Fix Released
** Changed in: kernel-sr
setting
export QUOTING_STYLE=literal
in .profile or /etc/profile helps
It happened on moving from UBUNTU LTS 16.04 to UBUNTU LTS 18.04 (migration from
one server to the other, not an upgrade of one server)
It is related to the "ls" command only, and not a generic UNIX kernel.
Seems to be a ch
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-security
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Fix Committed => Fix Released
** Changed in: kernel-sr
** Changed in: kernel-sru-workflow/promote-to-security
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Fix Committed => Fix Released
** Description changed:
This bug is for tracking the upload package. This
bug will contain s
The package has been published and the bug is being set to Fix Released
** Changed in: kernel-sru-workflow/promote-to-security
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Fix Committed => Fix Released
** Changed in: kernel-sr
** Changed in: kernel-sru-workflow/promote-to-security
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Fix Committed => Fix Released
** Description changed:
This bug is for tracking the upload package. This
bug will contain s
** Changed in: kernel-sru-workflow/promote-to-security
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Fix Committed => Fix Released
** Description changed:
This bug is for tracking the upload package. This
bug will contain s
** Changed in: kernel-sru-workflow/promote-to-security
Status: Fix Committed => Fix Released
** Changed in: kernel-sru-workflow/promote-to-updates
Status: Fix Committed => Fix Released
** Description changed:
This bug is for tracking the upload package. This
bug will contain s
Updated system to 18.04.1 @ 23/8/2018 but problem still persist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1758974
Title:
Indicator-multiload does not work properly 18.04
To manage notifications
Hello Daniel van Vugt,
I added the variable 'GDK_SYNCHRONIZE=1' in my work environment,
however, the report was marked in the same way as replica ... As if it
were an identical report to LP: #1755779
See LP: #1788613 This report has the variable 'GDK_SYNCHRONIZE=1'
Please tell me what to do ...
Sorry, typo error
You should discuss to default to QUOTING_STYLE=literal on UBUNTU 18.04 LTS
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788455
Title:
Issue Creating Files with Equal sign =
To m
Public bug reported:
Unbound 1.6.7-1ubuntu2.1 on 18.04 (bionic):
$ sudo systemctl reload unbound
Job for unbound.service failed because a timeout was exceeded.
See "systemctl status unbound.service" and "journalctl -xe" for details.
Looks like https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=89
** Changed in: wget (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/1788608
Title:
wget doesn't support compression, it needs zlib1g-dev
To manage notifications
@redsandro that's not the bug described here. I'm on a completely new
laptop now (T470p) and I still have those messages.
I believe it's safe to close the bug as hardware issue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://
I just install 18.04.1.
With Gnome 3, no problem of keyboard shortcuts.
With Unity, some shortcuts don't work (Ctrl+Alt+T, Print screen , Media keys).
I try 2 solutions :
1. Post #11 (with delay 5sec) => in some sessions, they don't work, forced to
restart.
2. Keyboard input method system to no
** Changed in: xfce4-xkb-plugin (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/1510280
Title:
Text layout font size doesn't change
To manage notification
** Description changed:
IPv6 PMTU discovery fails when using source-specific routing on Ubuntu
18.04.
I have attached a test case called pmtu-sads.sh which is based on
tools/testing/selftests/net/pmtu.sh in the linux source.
- I have verified that the test succeeds on:
- Ubuntu 16.04
Public bug reported:
IPv6 PMTU discovery fails when using source-specific routing on Ubuntu
18.04.
I have attached a test case called pmtu-sads.sh which is based on
tools/testing/selftests/net/pmtu.sh in the linux source.
I have verified that the test fails on:
Ubuntu 18.04 with 4.15.0-30.32
Ubu
Patch which fixes the bug for me.
** Patch added: "net/ipv6/route: Fix PMTU for source-specific routes"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788623/+attachment/5179773/+files/0001-net-ipv6-route-Fix-PMTU-for-source-specific-routes.patch
--
You received this bug notification
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 1788623
and then change the status of the bug to 'Confirmed'.
If, due to the nature
** Changed in: apt (Ubuntu)
Status: Confirmed => Won't Fix
** Changed in: apt (Ubuntu Xenial)
Status: Confirmed => Won't Fix
** Changed in: apt (Ubuntu Bionic)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: nvidia-graphics-drivers-304 (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/
That workaround wouldn't work in Landscape for many configurations; we
can't assume pocket names as many use custom mirrors or repository
snapshots in which the pocket may not match.
It seems to me there is no simple way to resolve this automatically in
Landscape, but as that upgrade situation is
Probably related:
https://bugs.launchpad.net/ubuntu/+source/easystroke/+bug/1769397
Disabled Easystroke and so far not seeing crashes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778233
Title:
X
*** This bug is a duplicate of bug 1775226 ***
https://bugs.launchpad.net/bugs/1775226
** This bug has been marked a duplicate of bug 1775226
[SRU] Gnome Software offers installation of updates on shutdown
independently from update-manager and unattended-upgrades
--
You received this bug
This bug should be fixed in the Ubuntu-4.15.0-33 Bionic kernel by the following
commit:
f4b09557ddcf x86/apic/x2apic: Initialize cluster ID properly
Can you confirm this bug is fixed by testing the latest kernel?
Thanks in advance!
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: console-setup (Ubuntu)
Importance: Undecided => Critical
** Tags added: rls-cc-incoming
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1788597
Title:
ubiquity broken with console-s
Public bug reported:
Ubuntu Release
Description:Ubuntu 18.04.1 LTS
Release:18.04
Package installed
shim-signed:
Installed: 1.34.9.2+13-0ubuntu2
Candidate: 1.34.9.2+13-0ubuntu2
Version table:
*** 1.34.9.2+13-0ubuntu2 500
500 http://ca.archive.ubuntu.com/ubuntu bionic-upd
I just hope that this fix makes it into an official release this time,
and that other problems in 4.15.0-33.36 don't prevent me from using it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1764645
Tit
Launchpad has imported 14 comments from the remote bug at
https://bugzilla.kernel.org/show_bug.cgi?id=198699.
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
https://hel
FWIW, the real approach would be to follow unattended-upgrades and write
a GPLed script that uses python-apt and adjusts the candidates. Then
(copy and? - no real idea how landscape works) invoke that on the
system.
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
** Also affects: landscape-client (Ubuntu)
Importance: Undecided
Status: New
** Changed in: landscape-client (Ubuntu)
Status: New => Won't Fix
** Changed in: landscape-client (Ubuntu Xenial)
Status: New => Won't Fix
** Changed in: landscape-client (Ubuntu Bionic)
S
Public bug reported:
On the update of grub-efi-amd64, it's now warning about unsigned
kernels, which it was not doing before, and failing. However, before
this update, the unsigned kernels were booting properly with Secure Boot
enabled. I don't know what would make them unbootable now. The followi
1 - 100 of 863 matches
Mail list logo
