The only binary we care about is 'libgupnp-1.0-4'.We can promote the
documentation if that's standard practice but that's not needed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1799974
Title:
There other applications which are affected as well (like LibreOffice).
My screen has a resolution set to 2550*1440, scaling is set to 200%
(sadly it isn't possible to set scaling to 150% without activating
experimental features).
--
You received this bug notification because you are a member of
I have not tried Centos6 VMs.
The customer reported that he deployed Centos7 to the baremetal blades
and saw, in ping traffic that incoming packets were vlan 0 tagged.
Then he deployed Centos6 to two baremetal blades and, in a ping test,
did not see any vlan tags.
If this is true, it suggests
As the reporter of the duplicate bug 1799787, I thought that I would see
if I could reproduce this problem with the latest disco daily
(20181205). Unfortunately I can by taking the following steps:
1. Boot to live session
2. Make external monitor the primary display and the laptop's internal
Sure, the only binary we care about here is 'libgssdp-1.0-3'. We can
promote the documentation if that's standard practice but that's not
needed.
Let's talk about the nitpick tomorrow, I'm not familiar on the
difference between dh_missing and dh_install --fail-missing, so it's
basically about
** Description changed:
* Availability
Builds on all supported architectures in Ubuntu and on sync from Debian
* Rationale
We would like to enable dlna sharing of media files, which is a GNOME
- upstream feature and relying on rygel
+ upstream feature and relying on rygel.
+
+
That's probably it. My primary is 1920x1080 and my secondary is
1280x1024. I just took two windows and manually placed them and at their
smallest width they overlap. At least I know why this is happening now.
Thanks.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-cosmic
** Tags added: block-proposed
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that
Launchpad has imported 1 comments from the remote bug at
https://bugs.documentfoundation.org/show_bug.cgi?id=121927.
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
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-cosmic
** Tags added: block-proposed
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that
@vhart, can you clarify that last comment? Do you mean that the CentOS 6
VMs exhibit the issue caused by the VLAN 0 tags and the CentOS 7 tags do
not? Or are you saying the tags are filtered elsewhere in the stack on
CentOS 6 (such as the NIC driver, 8021q driver, or virtual bridge)?
--
You
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-cosmic
** Tags added: block-proposed
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-cosmic
** Tags added: block-proposed
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that
By starting gscan2pdf with the --log=log option, it creates a file
called "log" in the current directory.
gscan2pdf --log=gscan2pdf.log
would create a file called "gscan2pdf.log". Instead of copy-pasting the
output from the terminal, please attach the file.
If setting # pages to 1 works for
** Bug watch added: Debian Bug tracker #915669
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915669
** Also affects: cloud-init (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915669
Importance: Unknown
Status: Unknown
** Also affects: open-iscsi (Debian) via
What's the resolution of your second monitor? gnome-shell is going to
refuse to snap a window to half of the screen if the minimal width of
that one is higher than the target (similar to what is described in bug
#1804973)
--
You received this bug notification because you are a member of Ubuntu
** Changed in: cmake (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/1806276
Title:
regression: kio FTBFS on i386 and armhf with cmake >= 3.13
To manage
** Changed in: gnutls28 (Ubuntu)
Status: In Progress => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1804673
Title:
gnutls causes gnome-music segmentation fault
To manage
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: telegram-desktop (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/1765879
Testing on bionic with above ppa:
$ dpkg -l |grep open-iscsi
ii open-iscsi
2.0.874-5ubuntu2.4+test1806777v20181205b2 amd64iSCSI initiator tools
$ cat /etc/network/interfaces.d/50-cloud-init.cfg
# This file is generated from information provided by
# the
Could you provide your /var/log/dist-upgrade/main.log file from the
upgrade to Ubuntu 18.04? Thanks in advance.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1773637
Title:
Distribution upgrade to
Thank you for your bug report, could you add your journalctl log of a
boot getting the issue?
** Changed in: gdm3 (Ubuntu)
Importance: Undecided => High
** Changed in: gdm3 (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: bug 1806410
** Tags added: server-next
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1781991
Title:
libsss-sudo.postinst clobbers local change to /etc/nsswitch.conf
To manage notifications about this bug go
ppa with test open-iscsi pkgs
https://launchpad.net/~ddstreet/+archive/ubuntu/lp1806777
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1806777
Title:
cloud-init with iscsi ibft keeps interface at
On bionic iBFT system, I switched to ifupdown:
$ sudo apt install ifupdown
...
$ sudo apt install resolvconf
...
$ sudo apt remove netplan.io
...
$ sudo vi /etc/network/interfaces
...
$ cat /etc/network/interfaces
auto lo
iface lo inet loopback
source /etc/network/interfaces.d/*.cfg
$ sudo
** Changed in: strongswan (Ubuntu Cosmic)
Status: Incomplete => Confirmed
** Changed in: strongswan (Ubuntu Bionic)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
** Changed in: strongswan (Ubuntu Cosmic)
Status: Incomplete => Confirmed
** Changed in: strongswan (Ubuntu Bionic)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug was fixed in the package ceph - 0.80.11-0ubuntu1.14.04.4
---
ceph (0.80.11-0ubuntu1.14.04.4) trusty; urgency=medium
* Don't truncate message sequence to 32-bit (LP: #1798081).
- d/p/msg-don-t-truncate-message-sequence-to-32-bits.patch:
use uint64_t for message
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
Hello Corey, or anyone else affected,
Accepted nova into cosmic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/nova/2:18.0.3-0ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
The verification of the Stable Release Update for ceph 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
Hello Matthew, or anyone else affected,
Accepted nova into cosmic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/nova/2:18.0.3-0ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Sorry, I got that wrong. A deployment of a pair of Centos6 hosts to the
blades did not have vlan 0 tags. The Centos7 deployments did have vlan 0
tags.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The Centos7 deployments were to other blades in the UCS chassis and
pings between the two Centos7 machines did not have vlan 0 tags.
I'll add your ppa and update to your ipxe and test pod VM booting.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Merge proposal linked:
https://code.launchpad.net/~ddstreet/ubuntu/+source/open-iscsi/+git/open-iscsi/+merge/360146
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1806777
Title:
cloud-init
...would it make sense to link to this reason why(eg some maintainers in
other projects actually do use it) in the error message, rather than
just warning about it? Would a more descriptive warning message make
sense so the next guy doesn't submit the same patch?
** Changed in: debhelper
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-signed
Status: In Progress => Fix Released
** Description changed:
This bug is for tracking the upload package. This
bug will contain
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Released
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the
** Summary changed:
- linux-hwe: -proposed tracker
+ linux-hwe: 4.18.0-13.14~18.04.2 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: New => In Progress
** Changed in: kernel-sru-workflow/prepare-package-meta
Assignee: Canonical Kernel Team
Hello,
Source code:
https://github.com/tomaspinho/rtl8821ce
Best regards,
--
Cristian Aravena Romero (caravena)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1806649
Title:
Not work Network
** Changed in: debhelper (Ubuntu)
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/1806509
Title:
dh_auto_configure: --disable-maintainer-mode
To manage notifications
Public bug reported:
I've a problem when resuming from suspend mode and try to unlock my pc.
Expected Behavior:
Interface shows correctly after resuming from suspend mode.
Real Behavior:
Interface shows badly after resume PC from suspend.
unlock interface doesn't shows at all; instead of it,
Hi Vern,
Could you confirm something to us. WHen you say that the customer
deployed centos 7 and were able to see the issue there, did you mean
that they saw the issue in the packets themselves? In other words,
CentOS7 deployed successfully but the packets still had the VLAN tag?
The reason I
Hello Corey, or anyone else affected,
Accepted keystone into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/keystone/2:13.0.2-0ubuntu1 in a few
hours, and then in the -proposed repository.
Please help us by testing this new package. See
Thanks!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1806385
Title:
Creating a new slide by double click not working correctly
To manage notifications about this bug go to:
This hasn't been tested yet on cosmic-proposed and we have a stable
point release of nova to get out so we're going to have to combine this
fix with the stable point release. That means this is going to have to
live in cosmic-proposed (and rocky-proposed) for another 7 days minimum.
--
You
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
I would suggest to reconsider #7. For me this this error is happening when
closing the lid. See few entries before crash (reverse order):
pro 05 19:19:35 hermes org.gnome.Shell.desktop[1245]: #0 7ffead301600 b
resource:///org/gnome/gjs/modules/overrides/GObject.js:468 (7f08f96cc040 @
pro
Hello Corey, or anyone else affected,
Accepted ceilometer into cosmic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/ceilometer/1:11.0.1-0ubuntu1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello Corey, or anyone else affected,
Accepted ceilometer into cosmic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/ceilometer/1:11.0.1-0ubuntu1 in a
few hours, and then in the -proposed repository.
Please help us by testing this new package. See
This bug was fixed in the package libgpiod - 1.2-2
---
libgpiod (1.2-2) unstable; urgency=medium
* d/libgpiod2.symbols
- Fix symbols for s390x
- Fix symbols for armel
-- SZ Lin (林上智) Wed, 05 Dec 2018 13:46:32 +0800
** Changed in: libgpiod (Ubuntu)
Status: New =>
This bug was fixed in the package netplan.io - 0.40.1~18.04.3
---
netplan.io (0.40.1~18.04.3) bionic; urgency=medium
* Fix idempotency in renaming: bond members should be exempt from rename, as
they may all share a single MAC for the bond device. (LP: #1802322)
*
This bug was fixed in the package netplan.io - 0.40.1~18.04.3
---
netplan.io (0.40.1~18.04.3) bionic; urgency=medium
* Fix idempotency in renaming: bond members should be exempt from rename, as
they may all share a single MAC for the bond device. (LP: #1802322)
*
This bug was fixed in the package netplan.io - 0.40.1~18.04.3
---
netplan.io (0.40.1~18.04.3) bionic; urgency=medium
* Fix idempotency in renaming: bond members should be exempt from rename, as
they may all share a single MAC for the bond device. (LP: #1802322)
*
I'm having a similar issue where setting the MTU to 1500 and using a match on
mac address does not stick. This is on a EC2 T2.Medium instance. Actual
configuration from a dev server:
network:
version: 2
ethernets:
eth0:
match:
macaddress: 12:0f:ae:49:5d:06
mtu: 1500
I'm having a similar issue where setting the MTU to 1500 and using a match on
mac address does not stick. This is on a EC2 T2.Medium instance. Actual
configuration from a dev server:
network:
version: 2
ethernets:
eth0:
match:
macaddress: 12:0f:ae:49:5d:06
mtu: 1500
This bug was fixed in the package netplan.io - 0.40.1~18.04.3
---
netplan.io (0.40.1~18.04.3) bionic; urgency=medium
* Fix idempotency in renaming: bond members should be exempt from rename, as
they may all share a single MAC for the bond device. (LP: #1802322)
*
This bug was fixed in the package netplan.io - 0.40.1~18.04.3
---
netplan.io (0.40.1~18.04.3) bionic; urgency=medium
* Fix idempotency in renaming: bond members should be exempt from rename, as
they may all share a single MAC for the bond device. (LP: #1802322)
*
*** This bug is a duplicate of bug 1736965 ***
https://bugs.launchpad.net/bugs/1736965
This bug was fixed in the package netplan.io - 0.40.1~18.04.3
---
netplan.io (0.40.1~18.04.3) bionic; urgency=medium
* Fix idempotency in renaming: bond members should be exempt from rename,
This bug was fixed in the package netplan.io - 0.40.1~18.04.3
---
netplan.io (0.40.1~18.04.3) bionic; urgency=medium
* Fix idempotency in renaming: bond members should be exempt from rename, as
they may all share a single MAC for the bond device. (LP: #1802322)
*
This bug was fixed in the package netplan.io - 0.40.1~18.04.3
---
netplan.io (0.40.1~18.04.3) bionic; urgency=medium
* Fix idempotency in renaming: bond members should be exempt from rename, as
they may all share a single MAC for the bond device. (LP: #1802322)
*
This bug was fixed in the package netplan.io - 0.40.1~18.04.3
---
netplan.io (0.40.1~18.04.3) bionic; urgency=medium
* Fix idempotency in renaming: bond members should be exempt from rename, as
they may all share a single MAC for the bond device. (LP: #1802322)
*
This bug was fixed in the package netplan.io - 0.40.1~18.04.3
---
netplan.io (0.40.1~18.04.3) bionic; urgency=medium
* Fix idempotency in renaming: bond members should be exempt from rename, as
they may all share a single MAC for the bond device. (LP: #1802322)
*
This bug was fixed in the package netplan.io - 0.40.1~18.04.3
---
netplan.io (0.40.1~18.04.3) bionic; urgency=medium
* Fix idempotency in renaming: bond members should be exempt from rename, as
they may all share a single MAC for the bond device. (LP: #1802322)
*
This bug was fixed in the package netplan.io - 0.40.1~18.04.3
---
netplan.io (0.40.1~18.04.3) bionic; urgency=medium
* Fix idempotency in renaming: bond members should be exempt from rename, as
they may all share a single MAC for the bond device. (LP: #1802322)
*
This bug was fixed in the package netplan.io - 0.40.1~18.04.3
---
netplan.io (0.40.1~18.04.3) bionic; urgency=medium
* Fix idempotency in renaming: bond members should be exempt from rename, as
they may all share a single MAC for the bond device. (LP: #1802322)
*
This bug was fixed in the package netplan.io - 0.40.1~18.04.3
---
netplan.io (0.40.1~18.04.3) bionic; urgency=medium
* Fix idempotency in renaming: bond members should be exempt from rename, as
they may all share a single MAC for the bond device. (LP: #1802322)
*
*** This bug is a duplicate of bug 1736965 ***
https://bugs.launchpad.net/bugs/1736965
The verification of the Stable Release Update for netplan.io has
completed successfully and the package has now been released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
This bug was fixed in the package netplan.io - 0.40.1~18.04.3
---
netplan.io (0.40.1~18.04.3) bionic; urgency=medium
* Fix idempotency in renaming: bond members should be exempt from rename, as
they may all share a single MAC for the bond device. (LP: #1802322)
*
This bug was fixed in the package netplan.io - 0.40.1~18.04.3
---
netplan.io (0.40.1~18.04.3) bionic; urgency=medium
* Fix idempotency in renaming: bond members should be exempt from rename, as
they may all share a single MAC for the bond device. (LP: #1802322)
*
** Changed in: open-iscsi (Ubuntu Trusty)
Status: New => Invalid
** Description changed:
[impact]
in bug 1752391, cloud-init was updated to check if the initramfs has
specific iscsi root device config (e.g. static initramfs config, or
ibft), and if so then set up the interface
/etc/default/grub.d/50-curtin-settings.cfg have been overriding the
settings from /etc/default/grub. In my case this was expected as I
deployed via MAAS.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I can confirm that 16.04 and 18.04 are also affected:
# Ubuntu 16.04
root@xxx:~# lsb_release -d
Description:Ubuntu 16.04.5 LTS
root@xxx:~# apt list libsss-sudo
Listing... Done
libsss-sudo/xenial-updates,now 1.13.4-1ubuntu1.12 amd64 [installed,automatic]
N: There are 2 additional versions.
Yuup, latest version (1.09).
I was also shocked when worked.
Pic:-
https://drive.google.com/file/d/1BUuJCczocVGFClxiTNGOk1GcnpfKdSLH/view?usp=drivesdk
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sorry, can't give you more data now as I am having my end sem exams in
college, but as soon as they are ie on 12, I will give you more data
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1776563
Public bug reported:
I upgraded about a week ago. At login I get only cursor and background.
While gdm-panel is "running", killall only kills it.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gdm3 3.28.3-0ubuntu18.04.3
ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
Uname:
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: New => Confirmed
** Tags added: block-proposed-xenial
** Tags added: block-proposed
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that
I've marked the subiquity task as invalid given the updated information
and added the debian-installer task
** Changed in: subiquity (Ubuntu)
Status: Incomplete => Invalid
** Also affects: debian-installer (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug
** Changed in: cloud-archive
Status: Triaged => Fix Committed
** Changed in: cloud-archive/rocky
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802226
tests results here: https://paste.ubuntu.com/p/z4Vjz2jYYG/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1778936
Title:
please re-add Support-system-image-read-only-etc.patch
To manage
** Changed in: cloud-archive
Status: Invalid => Fix Committed
** Changed in: cloud-archive/rocky
Status: Triaged => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1806049
Na problem, here it is:
https://bugs.documentfoundation.org/show_bug.cgi?id=121927
** Bug watch added: Document Foundation Bugzilla #121927
https://bugs.documentfoundation.org/show_bug.cgi?id=121927
** Also affects: df-libreoffice via
Public bug reported:
Happened during an upgrade from Xubuntu 18.04 to Xubuntu 18.10. But ZFS
did work OK after upgrade.
ProblemType: Package
DistroRelease: Ubuntu 18.10
Package: zfs-dkms 0.7.9-3ubuntu6
ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
Uname: Linux 4.18.0-12-generic
Public bug reported:
Azure IMDS service doesn't seem to be available during initial instance
boot.
Cloud-init tries 4 times and gives up. This doesn't seem to be enough
and cloud-init fallsback to basic network configuration of 1 network
device, ignoring any additional devices the user had
** Description changed:
[impact]
in bug 1752391, cloud-init was updated to check if the initramfs has
specific iscsi root device config (e.g. static initramfs config, or
ibft), and if so then set up the interface in e/n/i but do not mark it
as 'auto'. This prevents ifupdown from
Hi! This also affects me on Ubuntu 18.04, using the same package (gnome-
screenshot/bionic,now 3.25.0-0ubuntu2 amd64).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1728764
Title:
gnome-screenshot
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Released
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the
Finally I could verify the fix works well and fixes the issue.
We are building core18 image using the snap which has systemd from
proposed.
Steps to validate:
1. build core18 snap using proposed
> git clone -b master https://git.launchpad.net/snap-core18
> cd snap-core18
> sed -i -e
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: bug 1806570
Microsoft's testing has turned up
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1806972 as
an issue in the latest version of walinuxagent, which will need
addressing before we can SRU it.
** Tags removed: verification-needed-bionic verification-needed-cosmic
** Changed in: cloud-init (Ubuntu Xenial)
Status: In Progress => Invalid
** Changed in: cloud-init (Ubuntu Xenial)
Assignee: Dan Streetman (ddstreet) => (unassigned)
** Also affects: open-iscsi (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: cloud-init
> How about fixing it without rewriting extfs?
So what's your plan? I've explained the cause of the problem, and why it
requires a rewrite above.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1232727
*without
--
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 5/Radeon/Raven) / AMDGPU
Juhani Numminen,
You say "So please disable that software source.". I am a Linux newbie. How do
I do that?
Robert Pearson
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1806479
Title:
Multiple
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Released
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated
--- Comment From cborn...@de.ibm.com 2018-12-05 12:34 EDT---
Confirmed. I installed bionic,
add bionic-proposed
used virt-install to install a guest
shut down guest
and added a hostdev to guest
started guest:
[root@localhost ~]# lszcrypt
CARD.DOMAIN TYPE MODESTATUS REQUEST_CNT
Public bug reported:
Hello,
caravena@romanescu:~$ systemctl status apport-autoreport.service
● apport-autoreport.service - Process error reports when automatic reporting is
enabled
Loaded: loaded (/lib/systemd/system/apport-autoreport.service; static;
vendor preset: enabled)
Active:
bios version of your laptop?i find it hard to believe that you can boot
with additional kernel parameters
--
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
201 - 300 of 723 matches
Mail list logo
