*** This bug is a duplicate of bug 216847 ***
https://bugs.launchpad.net/bugs/216847
Le 15/05/2019 à 23:07, Andreas Hasenack a écrit :
> *** This bug is a duplicate of bug 216847 ***
> https://bugs.launchpad.net/bugs/216847
>
> Thanks for filing this bug. I believe this falls under the
** Changed in: kernel-sru-workflow/snap-release-to-stable
Status: New => Invalid
** 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:
No, my device doesn't work with 6Gbps. In kernel 4.14 if my drive was
offline, function sata_down_spd_limit() cut down link->sata_spd_limit to
1, so it corresponds to 1.5Gbps, and was working. But it wasn't even try
to set limit to 3Gbps.
In my device, unfortunately mask and link->sata_spd_limit
This bug was fixed in the package cups - 2.2.8-5ubuntu1.3
---
cups (2.2.8-5ubuntu1.3) cosmic; urgency=medium
* d/p/systemd-service-for-cupsd-after-sssd.patch: Start cupsd after sssd if
installed (LP: #1822062)
-- Victor Tapia Wed, 24 Apr 2019 17:21:13
+0200
** Changed in:
This bug was fixed in the package cups - 2.2.7-1ubuntu2.5
---
cups (2.2.7-1ubuntu2.5) bionic; urgency=medium
* d/p/systemd-service-for-cupsd-after-sssd.patch: Start cupsd after sssd if
installed (LP: #1822062)
-- Victor Tapia Wed, 24 Apr 2019 16:58:30
+0200
** Changed in:
This bug was fixed in the package cups - 2.1.3-4ubuntu0.8
---
cups (2.1.3-4ubuntu0.8) xenial; urgency=medium
* d/p/systemd-service-for-cupsd-after-sssd.patch: Start cupsd after sssd if
installed (LP: #1822062)
-- Victor Tapia Tue, 23 Apr 2019 17:44:19
+0200
--
You
This bug was fixed in the package netkit-tftp - 0.17-22ubuntu1
---
netkit-tftp (0.17-22ubuntu1) eoan; urgency=medium
* Merge from debian unstable. Remaining changes:
- debian/control: Change dependency from openbsd-inetd to xinetd
so correct size is reported
-
Public bug reported:
I believe this has occurred since the last update, but this did not
occur on a machine I use.
I've tried renaming the profile and tried reinstalling libreoffice via
synaptic.
1) $ lsb_release -rd
Description:Ubuntu 18.04.2 LTS
Release:18.04
2) $ apt-cache
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: bluez (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/1823076
Title:
The verification of the Stable Release Update for cups 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
This bug was fixed in the package cups - 2.2.10-4ubuntu1
---
cups (2.2.10-4ubuntu1) disco; urgency=medium
* d/p/systemd-service-for-cupsd-after-sssd.patch: Start cupsd after sssd if
installed (LP: #1822062)
-- Victor Tapia Wed, 24 Apr 2019 17:02:49
+0200
** Changed in:
** Also affects: cloud-archive
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/1825882
Title:
[SRU] Virsh disk attach errors silently ignored
To manage
Just passing by to see if anything has changed. Would be good to know if
the workaround is effective for those affected.
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/216847
Title:
sshd
Just passing by to see if anything has changed. Would be good to know if
the workaround is effective for those affected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/216847
Title:
sshd
This works. Thanks. What does gdm3 do that requires this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1716857
Title:
gdm3, hybrid nvidia with modeset=1, no external monitors detected
To manage
Managed to report a bug here https://bugs.kde.org/show_bug.cgi?id=407572
@Eric, it would probably be useful if you could also report the version
of xdg-desktop-portal and xdg-desktop-portal-kde you are running. Could
you paste the output of the following command ?
$ apt policy xdg-desktop-portal
Thanks for filing this bug in Ubuntu.
This is the error:
Setting up mysql-server-5.7 (5.7.26-0ubuntu0.18.04.1) ...
Installing new version of config file /etc/mysql/mysql.conf.d/mysqld.cnf ...
/var/lib/dpkg/info/mysql-server-5.7.postinst: line 191:
/usr/share/mysql-common/configure-symlinks: No
Thanks for filing this bug in Ubuntu.
This is the error:
Setting up mysql-server-5.7 (5.7.26-0ubuntu0.18.04.1) ...
Installing new version of config file /etc/mysql/mysql.conf.d/mysqld.cnf ...
/var/lib/dpkg/info/mysql-server-5.7.postinst: line 191:
/usr/share/mysql-common/configure-symlinks: No
> could you also add the patch which fixes bug 1754671
Can you create a debdiff? It's not clear to me which patch, exactly,
fixes that bug; the upload containing the fix contains a large amount of
changes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: systemd (Ubuntu Eoan)
Status: Triaged => In Progress
** Changed in: systemd (Ubuntu Eoan)
Assignee: (unassigned) => Dan Streetman (ddstreet)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 216847 ***
https://bugs.launchpad.net/bugs/216847
Thanks for filing this bug. I believe this falls under the umbrella of
bug #216847
** This bug has been marked a duplicate of bug 216847
sshd will not start at boot if ListenAddress is set, because
Public bug reported:
It seems like after upgrade to 19.04 that exim is not running the
local_scan function (in my case the sa-exim /usr/lib/exim4/local_scan
/sa-exim.so)
So I now don't have the spam-scan I am used to(I have enabled scanning
by the way of an RCPT_ACL for now)
Hope this can fixed
*** This bug is a duplicate of bug 216847 ***
https://bugs.launchpad.net/bugs/216847
Thanks for filing this bug. I believe this falls under the umbrella of
bug #216847
** This bug has been marked a duplicate of bug 216847
sshd will not start at boot if ListenAddress is set, because
** Summary changed:
- linux-aws: -proposed tracker
+ linux-aws: 4.15.0-1040.42 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team
OK speaking with upstream we think this is likely a xdg-desktop-portal-
kde bug, so I am marking this as affect that project and marking as
invalid for flatpak.
I'm also trying to work out how to report a bug against
https://phabricator.kde.org/source/xdg-desktop-portal-kde/ if I can
figure it
11.3 is in eoan, marking that task as fix released.
** Changed in: postgresql-11 (Ubuntu Eoan)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828012
Title:
New
** 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 1829185
11.3 is in eoan, marking that task as fix released.
** Changed in: postgresql-11 (Ubuntu Eoan)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to postgresql-11 in Ubuntu.
Sorry, what do you mean?
--
You received this bug notification because you are a member of Ubuntu
Server, which is subscribed to clamav in Ubuntu.
https://bugs.launchpad.net/bugs/1827782
Title:
This tool requires libclamav with functionality level 110 or higher
(current f-level: 102)
To
Sorry, what do you mean?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1827782
Title:
This tool requires libclamav with functionality level 110 or higher
(current f-level: 102)
To manage
Thoughts:
DistUpgradeViewKDE.py includes a line which replaces "Ubuntu" with
"Ubuntu xx.xx":
self.window_main.label_title.setText(self.window_main.label_title.text().replace("Ubuntu",
name))
So if the title would be changed to "Upgrading Ubuntu to version %s", I
suppose that "%s" could be
@causeless, @jdoefp, can either of you review my SRU template info,
especially the test case section, to make sure it is correct. I've
reproduced locally but would like to make sure the steps I mentioned are
correct.
** Description changed:
+ [impact]
+
+ systemd does not set endpoints for
Thanks ! To me this looks like flatpak is launching the app correctly
and the app is instead hanging inside Qt when trying to communicate
using xdg-desktop-portal-kde with the host for settings. I'll have a
chat with upstream, but this might be a xdg-desktop-portal-kde issue.
--
You received
Hello. Sure thing. See below.
Output of apt policy:
apt policy bubblewrap flatpak
bubblewrap:
Installed: 0.3.1-4
Candidate: 0.3.1-4
Version table:
*** 0.3.1-4 500
500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
100 /var/lib/dpkg/status
flatpak:
Hello bugproxy, or anyone else affected,
Accepted util-linux into xenial-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/util-
linux/2.27.1-6ubuntu3.7 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
** Description changed:
[IMPACT]
In xenial lscpu prints the wrong "Hypervisor vendor" and "Virtualization
type" on PowerVM or KVM systems. Incorrect hypervisor and virtualization
type reported in ubuntu 16.04.04 guest running in P8compat mode on P9
boston-LC.
[TEST]
Curent
I keep fully updating with `apt`; you can assume I'm running the latest
official stable releases
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828116
Title:
Password works uppercase and lowercase
Well, no, I'm not going to waste resources retrying all the archs, I
only retried ppc64el.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826870
Title:
cache.commit() doesn't release the archives
> Do you get the issue in the lock screen as well on only on the boot greeter?
Yes
> Could you try adding another user to the system and see if it has the
same bug?
Here are my steps:
1. Add a new user with a password made of lowercase, numbers and a % sign
1. Lock the screen
1. "Login as
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Released
** Changed in: kernel-sru-workflow/prepare-package-meta
Status: In Progress => Fix Released
** Description changed:
This bug will contain status and test results related to a kernel source
This bug was fixed in the package python3.8 - 3.8.0~a4-3
---
python3.8 (3.8.0~a4-3) experimental; urgency=medium
* Update symbols files.
-- Matthias Klose Wed, 15 May 2019 00:30:25 +0200
** Changed in: python3.8 (Ubuntu)
Status: Confirmed => Fix Released
--
You
** 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 1829214
I don't see apt-clone having been tried with itself as a trigger for
amd64.
http://autopkgtest.ubuntu.com/packages/a/apt-clone/bionic/amd64
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1826870
** Also affects: systemd (Ubuntu Eoan)
Importance: Undecided
Status: Confirmed
** Also affects: systemd (Ubuntu Disco)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Eoan)
Status: Confirmed => In Progress
** Changed in: systemd (Ubuntu Disco)
The attachment "lp1824236_bionic.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 the
"patch" tag,
The attachment "kmem_cache_create_usercopy.patch" seems to be a patch.
If it isn't, please remove the "patch" flag from the attachment, remove
the "patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.
[This is an automated message performed by a Launchpad user owned
** Tags removed: verification-needed verification-needed-bionic
verification-needed-cosmic verification-needed-disco verification-needed-xenial
** Tags added: verification-done verification-done-bionic
verification-done-cosmic verification-done-disco verification-done-xenial
--
You received
I'm also experiencing this bug after upgrading from 16.04 to 18.04.
Removing and reinstalling the package and .Slic3r dir does not fix it.
The Github developer comments suggest this problem was fixed as of slic3r
version 1.3.1.
The slic3r packaged with Ubuntu 18.04 is V1.2.9.
However 18.04
Hello, we have the very same problem after upgrading to ubuntu 18.04 .
Server is not booting anymore, hanging on:
aacraid: Host Adapter abort request.
aacraid: Outstanding commands on (1,1,241,0):
aacraid: Host Adapter abort request.
aacraid: Outstanding commands on (1,1,242,0):
aacraid: Host
This bug was fixed in the package linux-kvm - 4.4.0-1046.52
---
linux-kvm (4.4.0-1046.52) xenial; urgency=medium
[ Ubuntu: 4.4.0-148.174 ]
* CVE-2018-12126 // CVE-2018-12127 // CVE-2018-12130
- Documentation/l1tf: Fix small spelling typo
- perf/x86/intel: Add model
This bug was fixed in the package linux-gcp - 4.15.0-1032.34~16.04.1
---
linux-gcp (4.15.0-1032.34~16.04.1) xenial; urgency=medium
[ Ubuntu: 4.15.0-1032.34 ]
* CVE-2018-12126 // CVE-2018-12127 // CVE-2018-12130
- Documentation/l1tf: Fix small spelling typo
- x86/cpu:
This bug was fixed in the package linux-aws - 4.4.0-1083.93
---
linux-aws (4.4.0-1083.93) xenial; urgency=medium
[ Ubuntu: 4.4.0-148.174 ]
* CVE-2018-12126 // CVE-2018-12127 // CVE-2018-12130
- Documentation/l1tf: Fix small spelling typo
- perf/x86/intel: Add model
This bug was fixed in the package linux-raspi2 - 4.4.0-1109.117
---
linux-raspi2 (4.4.0-1109.117) xenial; urgency=medium
[ Ubuntu: 4.4.0-148.174 ]
* CVE-2018-12126 // CVE-2018-12127 // CVE-2018-12130
- Documentation/l1tf: Fix small spelling typo
- perf/x86/intel: Add
This bug was fixed in the package linux-snapdragon - 4.4.0-1113.118
---
linux-snapdragon (4.4.0-1113.118) xenial; urgency=medium
[ Ubuntu: 4.4.0-148.174 ]
* CVE-2018-12126 // CVE-2018-12127 // CVE-2018-12130
- Documentation/l1tf: Fix small spelling typo
- perf/x86/intel:
This bug was fixed in the package linux-aws-hwe - 4.15.0-1039.41~16.04.1
---
linux-aws-hwe (4.15.0-1039.41~16.04.1) xenial; urgency=medium
[ Ubuntu: 4.15.0-1039.41 ]
* CVE-2018-12126 // CVE-2018-12127 // CVE-2018-12130
- Documentation/l1tf: Fix small spelling typo
-
This bug was fixed in the package linux-gcp - 4.15.0-1032.34~16.04.1
---
linux-gcp (4.15.0-1032.34~16.04.1) xenial; urgency=medium
[ Ubuntu: 4.15.0-1032.34 ]
* CVE-2018-12126 // CVE-2018-12127 // CVE-2018-12130
- Documentation/l1tf: Fix small spelling typo
- x86/cpu:
This bug was fixed in the package linux-azure - 4.15.0-1045.49
---
linux-azure (4.15.0-1045.49) xenial; urgency=medium
* [linux-azure] Storage performance drop on RAID (LP: #1828248)
- Revert "blk-mq: remove the request_list usage"
[ Ubuntu: 4.15.0-50.54 ]
*
This bug was fixed in the package linux-oracle - 4.15.0-1013.15~16.04.1
---
linux-oracle (4.15.0-1013.15~16.04.1) xenial; urgency=medium
[ Ubuntu: 4.15.0-1013.15 ]
* CVE-2018-12126 // CVE-2018-12127 // CVE-2018-12130
- Documentation/l1tf: Fix small spelling typo
-
This bug was fixed in the package linux-oracle - 4.15.0-1013.15~16.04.1
---
linux-oracle (4.15.0-1013.15~16.04.1) xenial; urgency=medium
[ Ubuntu: 4.15.0-1013.15 ]
* CVE-2018-12126 // CVE-2018-12127 // CVE-2018-12130
- Documentation/l1tf: Fix small spelling typo
-
This bug was fixed in the package linux-hwe - 4.15.0-50.54~16.04.1
---
linux-hwe (4.15.0-50.54~16.04.1) xenial; urgency=medium
[ Ubuntu: 4.15.0-50.54 ]
* CVE-2018-12126 // CVE-2018-12127 // CVE-2018-12130
- Documentation/l1tf: Fix small spelling typo
- x86/cpu: Sanitize
Verified 1.15.5-1ubuntu5.16.04.0 on Xenial:
ubuntu@ubuntu-Standard-PC-i440FX-PIIX-1996:~$ dpkg -l kbd | cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name
This is the patch from debian for this issue. The driver seems to
compile fine with it.
** Patch added: "kmem_cache_create_usercopy.patch"
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1802622/+attachment/5264097/+files/kmem_cache_create_usercopy.patch
--
You
@Dan Streetman
That's right, this problem does not affect the reboot or shutdown of the
operating system.
My concern is the loss of data due to improper unmount.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Michael,
You will need the following for the 256 Cores:
https://bugs.launchpad.net/amd/+bug/1816669
--kim
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819485
Title:
AMD Rome : Additional
Hello Chad, or anyone else affected,
Accepted cloud-init into xenial-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/cloud-
init/19.1-1-gbaa47854-0ubuntu1~16.04.1 in a few hours, and then in the
-proposed repository.
Please help us by testing this
Hello Chad, or anyone else affected,
Accepted cloud-init into xenial-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/cloud-
init/19.1-1-gbaa47854-0ubuntu1~16.04.1 in a few hours, and then in the
-proposed repository.
Please help us by testing this
Hello Chad, or anyone else affected,
Accepted cloud-init into bionic-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/cloud-
init/19.1-1-gbaa47854-0ubuntu1~18.04.1 in a few hours, and then in the
-proposed repository.
Please help us by testing this
With Eoan we now always default to 4k, hence Fix Released in e2fsprogs
and the project.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1817097
Title:
pvmove causes file system corruption without
Vibhu, please see https://usn.ubuntu.com/3943-1/ for information on the
most recent wget security update we performed.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1828190
Title:
I also confirm that Paco Angulo (3rpako)'s suggestion (#42) worked for
my laptop too. It's Asus with I7 core running Debian-10. Thanks Paco
Angulo.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello Chad, or anyone else affected,
Accepted cloud-init into bionic-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/cloud-
init/19.1-1-gbaa47854-0ubuntu1~18.04.1 in a few hours, and then in the
-proposed repository.
Please help us by testing this
I not sure upstream will let us change the value of mask.
Will you get the same result of you set sata_spd_limit?
link->sata_spd_limit = 0x7
I believe that corresponds to 6Gbps but I don't see a #define
we can use.
Also, is the comment accurate? Before you started debugging
did you see a hard
** Also affects: systemd (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: systemd (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Changed in: systemd (Ubuntu Cosmic)
Assignee: (unassigned) => Dan Streetman (ddstreet)
** Changed in: systemd (Ubuntu
Verified 2.0.4-2ubuntu1.18.04.0 on Bionic:
test@test-Standard-PC-i440FX-PIIX-1996:~$ dpkg -l kbd | cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name
** 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 --
Public bug reported:
[impact]
with systemd and resolvconf installed, the /etc/resolv.conf file is
managed by resolvconf, and in bug 1817903 the 'options edns0' option is
stripped from the systemd stub resolv.conf so no 'options edns0' will be
present in /etc/resolv.conf (unless added through
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
This does seem odd, on my Ubuntu system Telegram launches immediately.
Could you paste (or pastebin) the output of the following commands?
$ apt policy bubblewrap flatpak
$ flatpak run -vv org.telegram.desktop
** Summary changed:
- linux-raspi2: -proposed tracker
+ linux-raspi2: 4.4.0-1110.118 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/prepare-package
Assignee: Canonical Kernel Team
There's actually a second patch that is recommended as per the libreelec
tree:
https://github.com/LibreELEC/LibreELEC.tv/blob/9012226b40baa26241069317fdce6174935ca71b/packages/x11/driver/xf86
-video-nvidia-legacy/patches/xf86-video-nvidia-legacy-02-fix-
linux-5.1.patch
I've combined both
Hi Kim,
I have tested this on a system, using Disco with 5.0 and I am currently
seeing only 255 cores, has support landed in Disco yet?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819485
Title:
** Changed in: systemd (Ubuntu)
Status: Confirmed => In Progress
** Changed in: systemd (Ubuntu Xenial)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hello Chad, or anyone else affected,
Accepted cloud-init into cosmic-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/cloud-
init/19.1-1-gbaa47854-0ubuntu1~18.10.1 in a few hours, and then in the
-proposed repository.
Please help us by testing this
The disco package worked for me to. Version info below:
# apt-cache policy python3-glance-store
python3-glance-store:
Installed: 0.28.0-0ubuntu1.1
Candidate: 0.28.0-0ubuntu1.1
Version table:
*** 0.28.0-0ubuntu1.1 500
500 http://archive.ubuntu.com/ubuntu disco-proposed/main amd64
Hello Chad, or anyone else affected,
Accepted cloud-init into cosmic-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/cloud-
init/19.1-1-gbaa47854-0ubuntu1~18.10.1 in a few hours, and then in the
-proposed repository.
Please help us by testing this
To reiterate and clarify: net-tools and ifupdown both exhibit the bug
in bionic, whereas neither exhibits the bug in xenial. The bug is
observed in the following package versions:
:; apt-cache policy net-tools
net-tools:
Installed: 1.60+git20161116.90da8a0-1ubuntu1
Candidate:
Message 2 of 2: This is easy to use and/or test ifup dummy0 and ifdown
dummy0
You don't need to know the complexities of the motivation for why this
is important; the test case is very simple.
In the context of the ifupdown package, this requires putting a stanza like
this in
The additional patch needed can be modeled off the one at
https://bugs.archlinux.org/task/62610 labeled as nvidia-340xx.patch
I've updated the patch to be additive on top of the
buildfix_kernel_5.0.patch
** Patch added: "buildfix_kernel_5.1.patch"
Msg 1 of 2: Here is a use-case for ifup dummy0 and ifdown dummy0:
I have multiple laptops. Sally has multiple laptops. Sometimes they
are wired (for speed) and sometimes wireless (for portability).
Sometimes we are at the same workplace, or at my abode, or her abode, or
the local library, or
These systems are using dnsmasq not systemd-resolver. This was done for
historical reasons; I'm not sure of the specific bug which caused that
choice.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: kernel-sru-workflow/prepare-package
Status: In Progress => Fix Released
** 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
Debdiff for Disco.
** Patch added: "lp1824236_disco.debdiff"
https://bugs.launchpad.net/ubuntu/+source/supermin/+bug/1824236/+attachment/5264092/+files/lp1824236_disco.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Debdiff for Disco.
** Patch added: "lp1824236_disco.debdiff"
https://bugs.launchpad.net/ubuntu/+source/supermin/+bug/1824236/+attachment/5264091/+files/lp1824236_disco.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Debdiff for Bionic.
** Patch added: "lp1824236_bionic.debdiff"
https://bugs.launchpad.net/ubuntu/+source/supermin/+bug/1824236/+attachment/5264089/+files/lp1824236_bionic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Debdiff for Cosmic.
** Patch added: "lp1824236_cosmic.debdiff"
https://bugs.launchpad.net/ubuntu/+source/supermin/+bug/1824236/+attachment/5264090/+files/lp1824236_cosmic.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Debdiff for Eoan.
** Patch added: "lp1824236_eoan.debdiff"
https://bugs.launchpad.net/ubuntu/+source/supermin/+bug/1824236/+attachment/5264093/+files/lp1824236_eoan.debdiff
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Changed in: linux-hwe-edge (Ubuntu)
Status: Fix Released => 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/1828553
Title:
Unable to boot Bionic 5.0 linux-hwe-edge kernel on
** Description changed:
+ [Impact]
+ Release upgrades on a system w/o python3-distro-info will crash.
+
+ [Test Case]
+ On a bionic-amd64 chroot:
+
(bionic-amd64)root@impulse:/home/bdmurray/Documents# do-release-upgrade
Checking for a new Ubuntu release
Get:1 Upgrade tool signature [819
Public bug reported:
The Ubuntu Error Tracker has been receiving reports about a problem regarding
wget. This problem was most recently seen with package version
1.19.4-1ubuntu2.2, the problem page at
https://errors.ubuntu.com/problem/43804a326c081388f17c668a4a2e7699bb2b44d8
contains more
*** This bug is a duplicate of bug 1599580 ***
https://bugs.launchpad.net/bugs/1599580
** This bug has been marked a duplicate of bug 1599580
package bamfdaemon 0.5.3~bzr0+16.04.20160523-0ubuntu1 failed to
install/upgrade: triggers looping, abandoned
--
You received this bug
Hello Chad, or anyone else affected,
Accepted cloud-init into disco-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/cloud-
init/19.1-1-gbaa47854-0ubuntu1~19.04.1 in a few hours, and then in the
-proposed repository.
Please help us by testing this new
101 - 200 of 739 matches
Mail list logo
