Fix had been included here (in QEMU v3.1 already):
https://git.qemu.org/?p=qemu.git;a=commitdiff;h=7294e600eb814fd2
** Changed in: qemu
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** 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 --
** Description changed:
Upstream has released microversions addressing security issues (pending
CVE attribution) and other bug fixes.
PHP 7.2.16 / 7.3.3 (07 Mar 2019):
* The CVEs addressed were backported by the security team already
PHP 7.2.17 / 7.3.4 (04 Apr 2019):
- *
** Changed in: kernel-sru-workflow/promote-to-proposed
Status: In Progress => Fix Committed
** 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
This has been fixed by
mutter (3.32.0-1ubuntu2) disco; urgency=medium
* debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
- Don't invert the screen size when rotation is enabled (LP: #1822513)
- Remove unneeded cleanup changes
- Use xcb checked function to
Removing packages from disco:
golang-juju-loggo 0.0~git20150318-0ubuntu1 in disco
golang-juju-loggo-dev 0.0~git20150318-0ubuntu1 in disco amd64
golang-juju-loggo-dev 0.0~git20150318-0ubuntu1 in disco arm64
golang-juju-loggo-dev
Public bug reported:
Upon adding a web ics calendar (via Evolution due to Bug #1825224), the
events from this calendar were not properly time-compensated for my time
zone. While Evolution and Gnome Shell displayed the time of my events
properly, gnome-calendar displayed the events 7 hours in the
** Project changed: totem => gstreamer
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1758287
Title:
totem crashed with SIGTRAP in __glXSendError() from
MakeContextCurrent()
To manage
** Description changed:
Upon attempting to add a calendar from outlook.com, I was greeted with a
username/password dialog box. So, I entered my username (an email
address in this case) and an app password I generated since I have two-
factor authentication. The dialog box would go away,
Both budgie and gnome-shell are in proposed now and this is verified for
mutter and both shell.
** Tags removed: verification-needed verification-needed-bionic
** Tags added: verification-done verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
blacklist entry removed; this can be synced once the blacklist
propagates, or it will automatically sync when E archive opens.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811718
Title:
Remove
I don't know whether I find time to install a 16.04 then upgrade it to 18.04,
but as you can see, many people were affected. Check the number of the visitors
and the comments:
https://askubuntu.com/questions/1021884/no-internet-after-upgrade-from-16-04-to-18-04
--
You received this bug
Removed 2019-02-21:
(From Debian) ROM; obsolete GCC version; Debian bug #821336
** Changed in: gcc-4.8 (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Removing packages from disco:
android-audiosystem 1.8+13.10.20130807-0ubuntu1 in disco
libandroid-audiosystem-asound2 1.8+13.10.20130807-0ubuntu1 in
disco armhf
libandroid-audiosystem-asound2 1.8+13.10.20130807-0ubuntu1 in
disco i386
Removing packages from disco:
android-src-vendor 7-0ubuntu1 in disco
android-src-vendor 7-0ubuntu1 in disco amd64
android-src-vendor 7-0ubuntu1 in disco arm64
android-src-vendor 7-0ubuntu1 in disco armhf
android-src-vendor
Was removed from Ubuntu on 2017-11-16.
FTBFS with postgresql-10; Debian bug #878561
** Changed in: skytools3 (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
wpa still has a build-dependency on android-headers.
** Changed in: wpa (Ubuntu)
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1734568
Title:
Please remove
Removed 2018-10-09 via Debian:
(From Debian) RoQA; source package renamed to gnome-themes-extra; Debian
bug #892100
** Changed in: gnome-themes-standard (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
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 1825229
and then change the status of the bug to 'Confirmed'.
If, due to the
Newer versions of these packages (dune-grid 2.6.0) are built fine and
releasable on s390x.
** Changed in: dune-grid (Ubuntu)
Status: New => Fix Released
** Changed in: dune-grid (Ubuntu)
Status: Fix Released => Won't Fix
** Changed in: dune-grid-glue (Ubuntu)
Status: New =>
Override component to universe
mess-desktop-entries 0.2-4 in disco: multiverse/gnome -> universe
mess-desktop-entries 0.2-4 in disco amd64: multiverse/gnome/optional/100% ->
universe
mess-desktop-entries 0.2-4 in disco arm64: multiverse/gnome/optional/100% ->
universe
mess-desktop-entries 0.2-4
--- Comment From wil...@us.ibm.com 2019-04-17 18:20 EDT---
(In reply to comment #24)
> I upgraded a built the following packages, I am continuing to see the same
> error with the new versions.
>
> kernel 5.0.7-stable
> dpdk-19.02
> rdma-core (master branch, commit
kde neon: (ubuntu 18.04.2 with HWE stack)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/520546
Title:
Alt+KEY incorrectly behaves like Ctrl+Alt+KEY
To manage notifications about this bug go to:
https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/143
** Bug watch added: gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues #143
https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/143
** Description changed:
-
> Why are you dropping the blacklist of fbxkb, which was identified
> in the blacklist file as "obsolete GNOME panel applet"?
This is answered by LP: #1811718. But still, please make this rationale
apparent in the commit history.
--
You received this bug notification because you are a member
Public bug reported:
Upon attempting to add a calendar from outlook.com, I was greeted with a
username/password dialog box. So, I entered my username (an email
address in this case) and an app password I generated since I have two-
factor authentication. The dialog box would go away, but the
In the time it took to try to port from aptdaemon to packagekit,
packagekit has gone dead upstream, and we have been recommended not to
port further work to it.
Julian is now looking at providing an aptd as part of apt upstream that
is fit for purpose.
I am unsubscribing ubuntu-archive from this
This bug was fixed in the package ubuntu-release-upgrader - 1:18.04.31
---
ubuntu-release-upgrader (1:18.04.31) bionic; urgency=medium
* DistUpgradeController.py: Instead of checking every sources.list entry to
see if they are accessible keep track of the uris and only test
CVE-2019-11034
CVE-2019-11035
** Also affects: php7.2 (Ubuntu Disco)
Importance: Undecided
Status: New
** Also affects: php7.2 (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: php7.2 (Ubuntu Bionic)
Importance: Undecided
Status: New
** Changed
This bug was fixed in the package ubuntu-release-upgrader - 1:18.04.31
---
ubuntu-release-upgrader (1:18.04.31) bionic; urgency=medium
* DistUpgradeController.py: Instead of checking every sources.list entry to
see if they are accessible keep track of the uris and only test
Public bug reported:
[Impact]
kpatch-dkms 0.5.0-0ubuntu1 from bionic does not build for linux-hwe-edge 5.0
kernels.
[Test case]
Build kpatch-dkms with both 5.0 and 4.15 kernels.
[Regression potential]
The fix might cause the package to fail to build on older kernels. Test it with
4.15 kernel.
Removed 2019-02-02 via Debian:
(From Debian) [auto-cruft] obsolete source package
** Changed in: vulkan (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I also experienced "A stop job is running for Session c2 ... / 1min 30
s)". Newbies (like me) might need to know that in a fresh install of
Ubuntu 16.04, the file /etc/systemd/system.conf has (almost) all lines
commented out with a # . So, in addition to changing the number in the
line
@DiQ,
You have an old version of the installer. Please try downloading the
latest revision of the stable LTS version of Ubuntu.
http://releases.ubuntu.com/18.04.2/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Removing packages from disco:
gtk-clearlooks-gperfection2-theme 1.1-0ubuntu3 in disco
gtk-clearlooks-gperfection2-theme 1.1-0ubuntu3 in disco amd64
gtk-clearlooks-gperfection2-theme 1.1-0ubuntu3 in disco arm64
** Changed in: kernel-sru-workflow/automated-testing
Status: Confirmed => Incomplete
** Changed in: kernel-sru-workflow/regression-testing
Status: New => Confirmed
** Changed in: kernel-sru-workflow/security-signoff
Status: New => In Progress
** Changed in:
See Bryan's question. These are syncs from Debian, if they are
obsolete, why have they not been removed there first?
** Changed in: xf86-input-mtrack (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Removing packages from disco:
gtk2-engines-equinox 1.50-0ubuntu4 in disco
gtk2-engines-equinox 1.50-0ubuntu4 in disco amd64
gtk2-engines-equinox 1.50-0ubuntu4 in disco arm64
gtk2-engines-equinox 1.50-0ubuntu4 in disco armhf
Alright; I think I've finally made some progress on this.
Turns out "Block device required" is really a red herring. It's some
random value (15) used in efibootmgr code, for any number of causes for
failure. We can't read anything into it.
The real error in indeed "Invalid argument", and very
Followed the test case for 64bit Bionic and 64bit Cosmic.
Repeated the test case for 32bit Bionic.
In all cases, pkexec dialog was correctly cancelled after upgrading
budgie.
** Tags removed: verification-needed verification-needed-bionic
verification-needed-cosmic
** Tags added:
This appears to have eben done some time ago.
sonata | 1.7~b1-3 | disco/universe | source, all
** Changed in: sonata (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Removing packages from disco:
silicon-theme 0.1-0ubuntu2 in disco
silicon-theme 0.1-0ubuntu2 in disco amd64
silicon-theme 0.1-0ubuntu2 in disco arm64
silicon-theme 0.1-0ubuntu2 in disco armhf
silicon-theme 0.1-0ubuntu2 in
Removing packages from disco:
rsbac-admin 1.4.0-repack-0ubuntu8 in disco
libnss-rsbac2 1.4.0-repack-0ubuntu8 in disco amd64
libnss-rsbac2 1.4.0-repack-0ubuntu8 in disco armhf
libnss-rsbac2 1.4.0-repack-0ubuntu8 in disco i386
Removing packages from disco:
watershed 9 in disco
watershed 9 in disco amd64
watershed 9 in disco arm64
watershed 9 in disco armhf
watershed 9 in disco i386
watershed 9 in disco ppc64el
In the package of
http://archive.ubuntu.com/ubuntu/pool/main/m/mysql-5.7/mysql-5.7_5.7.25.orig.tar.gz
file
./packaging/deb-in/extra/apparmor-profile
The following pids are listed but not mysql.pid
# Allow pid, socket, socket lock file access
/var/run/mysqld/mysqld.pid rw,
According to github, it's fixed in 0.9.0:
https://github.com/alanxz/rabbitmq-c/commit/5dfe5d2f2680a4639090a9c239a2b0018d90c789#diff-0d2986f9db9bba422328c4379976b6d9
Would it be possible to upgrade the package?
Or would someone prefer to backport the fix?
--
You received this bug notification
Any pointers to upgrade my existing bionic-rocky deployment to 14.1.0 version
of keystone?
Asking cause, "juju upgrade-charm keystone" did not upgrade the application
version.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Description changed:
Ubuntu Disco currently has MAAS 2.5.0. This is a Standing Feature Freeze
Exception request for MAAS 2.6.0 beta 1 release.
Dependencies & Upgrade
==
MAAS 2.6 has introduced the following features:
- HTTP boot for amd64/arm64
-
Public bug reported:
On Ubuntu 16.04.6 LTS, after apt purge mysql-server* then apt install
mysql-server the intallation fails because the AppArmor profile is
incomplete. Booting with kernel command line parameter apparmor=0 allows
successful install.
Running aa-logprof shows that the pid file is
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: librabbitmq (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/1790657
Title:
Upstream thread:
http://lists.infradead.org/pipermail/linux-arm-kernel/2019-April/647345.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823753
Title:
arm64: cma_alloc errors at boot
To
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-lts-xenial (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/486154
On Fri, Apr 12, 2019 at 9:54 PM Seth Arnold <1570...@bugs.launchpad.net> wrote:
>
> I reviewed edk2 version 0~20181115.85588389-2ubuntu1 as checked into
> disco. This review barely scratches the surface of the package.
>
> It appears there's roughly 20 CVEs for sources in this package. We've
>
** Changed in: gstreamer
Status: Unknown => 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/1758287
Title:
totem crashed with SIGTRAP in __glXSendError() from
*** This bug is a duplicate of bug 1825208 ***
https://bugs.launchpad.net/bugs/1825208
** This bug has been marked a duplicate of bug 1825208
Automatic suspend delay is at least 15 mins
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
+1 for Xenial KVM guest support (not for xenial as base OS for MAAS)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825099
Title:
Unable to deploy Xenial on a s390x KVM
To manage notifications
gcc-5-cross-ports removed 2019-01-29:
(From Debian) RoQA; old gcc version; Debian bug #920162
** Changed in: gcc-5-cross-ports (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: acpi-support (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/1748702
Title:
Please upgrade that old version
To manage notifications about
gcc-5-cross removed 2019-01-07:
uninstallable following cruft removal of gcc-6-cross, and unused.
** Changed in: gcc-5-cross (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Public bug reported:
ubuntu-advantage-tools on trusty needs an update to support trusty ESM.
SRU template to follow.
** Affects: ubuntu-advantage-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server,
Public bug reported:
ubuntu-advantage-tools on trusty needs an update to support trusty ESM.
SRU template to follow.
** Affects: ubuntu-advantage-tools (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Removing packages from disco:
gtk2-engines-blueheart 0.20070123-0ubuntu2 in disco
gtk2-engines-blueheart 0.20070123-0ubuntu2 in disco amd64
gtk2-engines-blueheart 0.20070123-0ubuntu2 in disco arm64
gtk2-engines-blueheart 0.20070123-0ubuntu2
I have swapped fwupdate for fwupd in the system-image seeds so that
fwupdate can be demoted to universe for disco. Since it does not appear
that either fwupd or fwupdate are actually used as part of the core18
build today, we should at least be referring to the *right* unused
implementation.
Please read this until the end before commenting. I am closing this bug
as "Invalid", because we can't deal with the many different types of
problems seen by people all on this same bug report.
This is, for most users, a firmware issue (in which case, if you're running a
Dell laptop, please
Followed the test case for 64bit Bionic and 64bit Cosmic.
Repeated the test case for 32bit Bionic.
In all cases, animations were correctly displayed.
Note - checked that a fully uptodate bionic + budgie upgrade works.
Then repeated testing with the new mutter (libmutter-2-0 mutter-common)
Followed the test case for 64bit Bionic and 64bit Cosmic.
Repeated the test case for 32bit Bionic.
In all cases (including logging out and in/ repeated reboots) workspace
navigation (which is a custom shortcut key) as well as opening a
terminal (which is not) worked correctly.
Note - checked
In addition to the above; if anyone has previously had Ubuntu 17.10
installed on the affected system, it is possible this is due to bug
1734147. Please see if the bug's description matched with what you are
seeing. If you're unsure, ask here for help.
--
You received this bug notification
Followed the test case for 64bit Bionic and 64bit Cosmic.
Repeated the test case for 32bit Bionic.
In all cases, raven was dismissed correctly.
Note - checked that a fully uptodate bionic + budgie upgrade works. Then
repeated testing with the new mutter (libmutter-2-0 mutter-common)
packages
confirmed that the new mutter also tries to uplift the budgie-desktop
version.
Tested the new mutter with the 4 budgie SRU's and all is ok.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811900
Override component to universe
comic-neue 2.4-2 in disco: multiverse/misc -> universe
fonts-comic-neue 2.4-2 in disco amd64: multiverse/fonts/optional/100% ->
universe
fonts-comic-neue 2.4-2 in disco arm64: multiverse/fonts/optional/100% ->
universe
fonts-comic-neue 2.4-2 in disco armhf:
Removed via Debian, 2018-10-10:
(From Debian) RoM; obsolete; unmaintained upstream; Debian bug #907195
** Changed in: node-tar-pack (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Removing packages from disco:
qca-qt5 2.1.1-0ubuntu2 in disco
Comment: Obsolete, Ubuntu-specific, superseded by qca2; LP: #1793971
1 package successfully removed.
** Changed in: qca-qt5 (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you
Removed via Debian, 2019-01-07:
(From Debian) ROM; deprecated upstream; NBS; NPOASR;; Debian bug #916281
** Changed in: lua-torch-cutorch (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
18.04.2 works as expected, thanks Was 18.04.1 really broken? LTS??!!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825163
Title:
install fail
To manage notifications about this bug go to:
The new upstream maintainers are quite enthusiastically working to help
get Openbve back into Debian/Ubuntu. If the data files hang around, it
is likely to be less work later on:
* https://github.com/leezer3/OpenBVE/issues/330#issuecomment-484102817
(The data files can be used with other
You've dropped ccsm from the blacklist, but the sole binary package
built from ccsm in Debian comes from compiz source in Ubuntu; I think
this needs to be retained.
You've traded icedove for thunderbird, but why should thunderbird be
blacklisted? It's currently maintained in Ubuntu and not
Public bug reported:
Would it be possible to enable rockchip support in Ubuntu 18.04 kernel
for arch armhf and aarch64?
Related kernel config options:
CONFIG_ARCH_ROCKCHIP
CONFIG_PCIE_ROCKCHIP
CONFIG_PCIE_ROCKCHIP_HOST
CONFIG_EMAC_ROCKCHIP
CONFIG_DWMAC_ROCKCHIP
CONFIG_ROCKCHIP_PHY
Removing packages from disco:
gogglesmm 0.12.7-3build2 in disco
gogglesmm 0.12.7-3build2 in disco amd64
gogglesmm 0.12.7-3build2 in disco arm64
gogglesmm 0.12.7-3build2 in disco armhf
gogglesmm 0.12.7-3build2 in disco i386
I have the same bug on my new laptop, a Teclast F6:
lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 8087:0a2a Intel Corp.
Bus 001 Device 006: ID 27c6:5740
Bus 001 Device 005: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card
Reader Controller
> So it seems to me that lookups by systemd-resolved
> are failing to lookup the hostname on the local DNS
> (even if this is by design)
yes, this is by design. systemd-resolved never forwards "single label"
addresses to upstream nameservers.
> If the router has the hostname AND domainname
** Changed in: node-mapnik (Ubuntu)
Status: New => Fix Released
** Changed in: node-tilelive-bridge (Ubuntu)
Status: New => Fix Released
** Changed in: node-tilelive-vector (Ubuntu)
Status: New => Fix Released
** Changed in: node-tilelive-mapnik (Ubuntu)
Status: New
What bugs, specifically, do you believe justify this package's removal
from the archive?
There are only two other bug reports open against the package, neither
of which at a glance seems particularly severe.
The package does not appear to be causing maintenance problems for the
Ubuntu release
The Debian bug has since been fixed. A newer version of the package has
been synced.
** Changed in: ruby-kramdown-rfc2629 (Ubuntu)
Status: New => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
> it seems the problem is solved.
great!
> The question is whether the patch/fix/change is included into that ISO file
> which
> is used for upgrading the older ubuntu releases to the 18.04?
I'm not sure what, if any, the bug was in the first place. If you can
reproduce the failure, please
Removing packages from disco:
libvideo-frequencies-perl 0.03-1ubuntu1 in disco
libvideo-frequencies-perl 0.03-1ubuntu1 in disco amd64
libvideo-frequencies-perl 0.03-1ubuntu1 in disco arm64
libvideo-frequencies-perl 0.03-1ubuntu1 in disco
Removing packages from disco:
blubuntu-look 0.3.1 in disco
blubuntu-look 0.3.1 in disco amd64
blubuntu-look 0.3.1 in disco arm64
blubuntu-look 0.3.1 in disco armhf
blubuntu-look 0.3.1 in disco i386
Public bug reported:
crashed when attemping to install new packages
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: ubiquity 19.04.7
ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
Uname: Linux 5.0.0-7-generic x86_64
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
CasperVersion:
I am not sure how to reproduce this. My build was working one day and
stopped the other day. Given I don't know what happened and what the
status was before it's hard to tell. I suspect the JavaFX jar file has
vanished. And yes, I am using Java 8 so that might be it.
I will try to upgrade to Java
** Tags added: cosmic2disco
** Tags added: third-party-packages
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825234
Title:
Python3: After do-release-upgrade, all apt-installed modules need to
** Summary changed:
- [FFe] MAAS 2.6.0 a 2
+ [0-day SRU] MAAS 2.6.0beta1
** Description changed:
Ubuntu Disco currently has MAAS 2.5.0. This is a Standing Feature Freeze
Exception request for MAAS 2.6 release.
Dependencies & Upgrade
==
MAAS 2.6 has introduced
Yes, the plan was to get rid of these in Debian first, maybe after
Buster..
** Changed in: xf86-input-mtrack (Ubuntu)
Assignee: (unassigned) => Timo Aaltonen (tjaalton)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
1) Uninstalled hplip-3.17.1
2) Did a fresh install of hplip-3.19.3
3) Installed the plugin
Still getting
-- Reboot --
Apr 17 20:28:21 xps13 systemd[1]: Started CUPS Scheduler.
Apr 17 20:33:22 xps13 systemd[1]: Stopping CUPS Scheduler...
Apr 17 20:33:22 xps13 systemd[1]: Stopped CUPS Scheduler.
** Changed in: charm-ceph-fs
Status: Fix Committed => Fix Released
** Changed in: charm-ceph-proxy
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Bug watch added: Debian Bug tracker #927311
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927311
** Also affects: resource-agents (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=927311
Importance: Unknown
Status: Unknown
--
You received this bug
I managed to fix this for myself. I did upgrade to java 11 and then
followed https://github.com/scalafx/scalafx on how to fix my build.sbt.
Similar instructions for other build systems can be found here:
https://openjfx.io/openjfx-docs/
--
You received this bug notification because you are a
** Changed in: charm-ceph-osd
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1812925
Title:
No OSDs has been initialized in random unit with "No block
Thanks again Dan for taking the time to explain.
> stop using dig to debug your system.
Sorry thought I was using dig at your request...
I was originally using nslookup and ping to find out why I couldn't browse to
the server on phspi05 (phspi05 is actually controlling the heating and cooling
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: gnome-shell-extension-desktop-icons (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Status changed to 'Confirmed' because the bug affects multiple users.
** 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/1825219
Title:
Is this the same as bug 1796275?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825112
Title:
Screen reader isn't actived on gdm if installed with a11y enabled
To manage notifications about this
1 - 100 of 685 matches
Mail list logo
