The verification of the Stable Release Update for libvirt 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
The verification of the Stable Release Update for gnome-shell-extension-
desktop-icons 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 verification of the Stable Release Update for ubuntu-report 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
This bug was fixed in the package libvirt - 5.0.0-1ubuntu2.2
---
libvirt (5.0.0-1ubuntu2.2) disco; urgency=medium
* d/p/ubuntu/lp-1825195-*.patch: fix issues with old guests that defined
the never functional osxsave and ospke features (LP: #1825195).
-- Christian Ehrhardt
This bug was fixed in the package libvirt - 5.0.0-1ubuntu2.2
---
libvirt (5.0.0-1ubuntu2.2) disco; urgency=medium
* d/p/ubuntu/lp-1825195-*.patch: fix issues with old guests that defined
the never functional osxsave and ospke features (LP: #1825195).
-- Christian Ehrhardt
This bug was fixed in the package gnome-shell-extension-desktop-icons -
19.01.3-1~ubuntu19.04.1
---
gnome-shell-extension-desktop-icons (19.01.3-1~ubuntu19.04.1) disco;
urgency=medium
* Backport new upstream release from eoan to disco (LP: #1829244)
- Fixes insecure
The verification of the Stable Release Update for gnome-shell-extension-
desktop-icons 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
** 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/1831026
Title:
package cups-browsed 1.8.3-2ubuntu3.5 failed to install/upgrade:
subprocess installed
Public bug reported:
steam crashed
ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: cups-browsed 1.8.3-2ubuntu3.5
ProcVersionSignature: Ubuntu 4.15.0-50.54~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-50-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Tue May
Today I got same issue and @pujanm's suggestion is solved the problem.
# apt-get update
Get:1 http://archive.ubuntu.com/ubuntu bionic InRelease [242 kB]
Get:2 http://security.ubuntu.com/ubuntu bionic-security InRelease [88,7 kB]
The verification of the Stable Release Update for deepin-qt5dxcb-plugin
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
This bug was fixed in the package deepin-qt5dxcb-plugin -
1.1.22-1ubuntu1.1
---
deepin-qt5dxcb-plugin (1.1.22-1ubuntu1.1) disco; urgency=medium
* Rebuild against qtbase ≥ 5.12.2+dfsg-4 (LP: #1826629).
* Build-depend on libxcb-xinput-dev to fix build failure.
-- Dmitry Shachnev
Dear Adam,
the log you provided does not seem to indicate an issue with acquiring
data from http://ppa.launchpad.net/jtaylor/keepass/ubuntu but from
http://ppa.launchpad.net/daniel.pavel/solaar/ubuntu - a PPA which does
not support your Ubuntu release (18.04 / bionic).
So this appears to not be
That's the wrong source, please read the error message carefully - the
solaar ppa for which the error occurs does not provide any bionic
packages.
** Changed in: apt (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: Confirmed => In Progress
** Changed in: kernel-sru-workflow/promote-to-proposed
Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz
Zemczak (sil2100)
--
You received this bug notification because you are
Hi Nathan, thanks for the bug report. This is currently a known issue
with non-integer scaling factors in KDE [1]. There's unfortunately no
big fix for everyone yet, just small fixes that work for some and not
for others. Keep up-to-date with KDE updates and it's likely the issue
will eventually
I see now 5.0.0-1007.7 is also available for 19.04, but I'll wait and
see what you advise @Dexuan after looking at my serial log.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822133
Title:
Azure
Public bug reported:
The following file siteated in /etc/apt/sources.d/jtaylor-ubuntu-
keepass-bionic.list:
deb http://ppa.launchpad.net/jtaylor/keepass/ubuntu bionic main
causes sudo apt update to fail for this entry with the error:
404 Not Found [IP: 91.189.95.83 80]
Full transcript:
** Description changed:
+ [Impact]
+
+ The documentation allows the following types of arguments for the
PreserveJobHistory parameter:
+ PreserveJobHistory Yes
+ PreserveJobHistory No
+ PreserveJobHistory seconds
+
+ The value in seconds is treated in the same as 'No' resulting in
Thanks for reporting this issue - this would appear to have potential
security implications, however as it is already public I see no reason
to keep this private - if a CVE were to be assigned then this could be
fixed via a security update by the security team, otherwise this would
be fixed via
I got the VM back by force stopping, then starting. It looks like
5.0.0-1007.7 only comes with 19.10, which is not available yet on Azure?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822133
Title:
This has been fixed in 19.10 for cups 2.2.10-6 (backport from upstream).
** Changed in: cups (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1747765
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: cups (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/1747765
Title:
On Wed, May 29, 2019 at 7:15 PM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:
> We tell build failure bugs apart according to their error messages. So
> the error message should go in the title.
>
> In this case it suggests you have an unusual C compiler installed as the
> default
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/1831020
Title:
BTRS Raid boot failure
To manage
** Description changed:
+ When an interface is added to a bond interface, if it is the first
+ interface added, the MAC address of the bond interface is changed
+ to the MAC address of the added interface. When subsequent interfaces
+ are added, their MAC addresses are changed to that of the bond
After some analysis I believe the very high default value of
LogDebugHistory (9) is to blame for this (attaching massif report
from the test case).
With a high number of jobs it's very easy to get hunderds-thousands of messages
in LogDebugHistory which in turn will lead to enormous memory
Public bug reported:
Under heavy workload conditions cups can reach irrationally high memory
consumption very quickly (tens of GBs).
Test case:
1. Set MaxJobs to 4 in cupsd.conf.
2. sudo apt install cups-pdf
3. Fill the queue with jobs:
while [ 1 ]; lp -d PDF
Public bug reported:
After upgrading from Ubuntu 18.10 to 19.04 my BTRFS Raid0 based system
doesn't boot anymore.
It drops to busybox because of an error mounting the root file system.
Manually trying to mount root reveals an error message saying that the
second raid volume could not be found
Thank you for your report. The mysql log
(Logs.var.log.mysql.error.log.txt) shows that mysqld was failing to
start even before the upgrade, e.g.:
190529 15:55:01 [Note] Server hostname (bind-address): '192.168.4.153'; port:
3306
190529 15:55:01 [Note] - '192.168.4.153' resolves to
** Also affects: oem-priority
Importance: Undecided
Status: New
** Changed in: oem-priority
Importance: Undecided => Critical
** Changed in: oem-priority
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
How do I upgrade the kernel to 5.0.0-1007.7 if that is what is
recommended to avoid this issue? apt-get dist-upgrade on another vm with
4.18.0-1018-azure did not upgrade the kernel. Thank God it restarted! Or
is 5.0.0-1007.7 not an Azure kernel so I would need to switch to stock
Ubuntu kernel?
@Dexuan I emailed you my serial log. I restarted via portal a number of
times without success. I tried to redeploy twice and it failed. Trying
to restart via cli now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I have found that if I set the reboot once at 15 min, the server works
for 5-6 days. If the reboots are done once at 10 min, the server get
stuck in 24-48h max. Now I'm testing the reboots once at 20min, it
should take 10 days or more until is stuck.
Also, I have tried all "reboot=" grub options,
@Kirk: I suppose you can get your VM back by Restarting the VM by force
via Azure Portal (or Azure cmd line)?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822133
Title:
Azure Instance never
** Changed in: linux (Ubuntu Cosmic)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Disco)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Kirk: Can you please share the VM's serial log, which can be obtained
from Azure portal's Boot Diagnostics -> Serial log?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822133
Title:
Azure
kernel is 4.18.0-1018-azure
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822133
Title:
Azure Instance never recovered during series of instance reboots.
To manage notifications about this bug go
401 - 438 of 438 matches
Mail list logo
