[Bug 1484990] Re: fsfreeze-hook script should also ignored dpkg generated files

2019-04-17 Thread Thomas Huth
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.
https://bugs.launchpad.net/bugs/1484990

Title:
  fsfreeze-hook script should also ignored dpkg generated files

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1484990/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1823755] Re: linux-gke-4.15: 4.15.0-1030.32 -proposed tracker

2019-04-17 Thread Ubuntu Kernel Bot
** 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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
  phase: Promote to Proposed
  phase-changed: Wednesday, 17. April 2019 16:06 UTC
  reason:
-   promote-to-proposed: Ongoing -- packages copied but not yet published to 
-proposed
+   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823755

Title:
  linux-gke-4.15: 4.15.0-1030.32 -proposed tracker

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1823755/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1823386] Re: [MRE] Please update to latest upstream release 7.2.17 & 7.3.4

2019-04-17 Thread Simon Déziel
** 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):
  
- * https://bugs.php.net/bug.php?id=77753 / CVE-pending
- * https://bugs.php.net/bug.php?id=77831 / CVE-pending
- 
+ * https://bugs.php.net/bug.php?id=77753 / 
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11034
+ * https://bugs.php.net/bug.php?id=77831 / 
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11035
  Changelog: https://secure.php.net/ChangeLog-7.php

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823386

Title:
  [MRE] Please update to latest upstream release 7.2.17 & 7.3.4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php7.2/+bug/1823386/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1822830] Re: linux-fips: 4.4.0-1008.10 -proposed tracker

2019-04-17 Thread Ubuntu Kernel Bot
** 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 workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822834
  phase: Promote to Proposed
  phase-changed: Wednesday, 17. April 2019 08:31 UTC
  reason:
-   promote-to-proposed: Ongoing -- review in progress
+   promote-signing-to-proposed: Holding -- builds not complete
+   promote-to-proposed: Ongoing -- packages copied but not yet published to 
-proposed

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1822830

Title:
  linux-fips: 4.4.0-1008.10 -proposed tracker

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1822830/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1793496] Re: scaling changes when closing/re-opening the lid

2019-04-17 Thread Treviño
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 set scaling to catch errors
- Update screen size only after monitors modes have been derived
  (LP: #1822616)
- Trigger a monitors rebuild only if scale has changed (LP: #1823485)
- Only update UI scaling when output scaling is enabled (LP: #1822478)

 -- Marco Trevisan (Treviño)  Wed, 03 Apr 2019 19:19:59 -0400


I expect this is fixed by 
https://gitlab.gnome.org/GNOME/mutter/merge_requests/336 (issue 
https://gitlab.gnome.org/GNOME/mutter/issues/407)

** Changed in: mutter (Ubuntu)
   Status: Triaged => Fix Released

** Bug watch added: gitlab.gnome.org/GNOME/mutter/issues #407
   https://gitlab.gnome.org/GNOME/mutter/issues/407

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1793496

Title:
  scaling changes when closing/re-opening the lid

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1793496/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1612713] Re: Please remove golang-juju-loggo

2019-04-17 Thread Steve Langasek
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 0.0~git20150318-0ubuntu1 in disco armhf
golang-juju-loggo-dev 0.0~git20150318-0ubuntu1 in disco i386
golang-juju-loggo-dev 0.0~git20150318-0ubuntu1 in disco ppc64el
golang-juju-loggo-dev 0.0~git20150318-0ubuntu1 in disco s390x
Comment: Ubuntu-specific, unmaintained, superseded by golang-github-juju-loggo; 
LP: #1612713
1 package successfully removed.


** Changed in: golang-juju-loggo (Ubuntu)
   Status: Triaged => 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/1612713

Title:
  Please remove golang-juju-loggo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/golang-juju-loggo/+bug/1612713/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1825227] [NEW] gnome-calendar overcompensates time zone difference in web ics calendar

2019-04-17 Thread Erich Eickmeyer
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 past,
likely attempting to compensate for my time zone (GMT -7).

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-calendar 3.32.0-1
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 17 11:47:17 2019
InstallationDate: Installed on 2019-04-15 (2 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190413.2)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-calendar
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-calendar (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug disco

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825227

Title:
  gnome-calendar overcompensates time zone difference in web ics
  calendar

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1825227/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1758287] Re: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent()

2019-04-17 Thread El jinete sin cabeza
** 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 notifications about this bug go to:
https://bugs.launchpad.net/gstreamer/+bug/1758287/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1825224] Re: gnome-calendar cannot add credentialed web ics calendars

2019-04-17 Thread Erich Eickmeyer
** 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, but the calendar
  would not be added.
  
  The only workaround was to add the calendar using Evolution, which
  properly accepted the username/app-password and added the calendar.
- Unfortunately, at that point, I discovered another bug which I will link
- here as soon as I get it filed.
+ Unfortunately, at that point, I discovered another bug (#185227).
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-calendar 3.32.0-1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 17 11:39:29 2019
  InstallationDate: Installed on 2019-04-15 (2 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190413.2)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: gnome-calendar
  UpgradeStatus: No upgrade log present (probably fresh install)

** 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, but the calendar
  would not be added.
  
  The only workaround was to add the calendar using Evolution, which
  properly accepted the username/app-password and added the calendar.
- Unfortunately, at that point, I discovered another bug (#185227).
+ Unfortunately, at that point, I discovered bug #185227.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-calendar 3.32.0-1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 17 11:39:29 2019
  InstallationDate: Installed on 2019-04-15 (2 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190413.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-calendar
  UpgradeStatus: No upgrade log present (probably fresh install)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825224

Title:
  gnome-calendar cannot add credentialed web ics calendars

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1825224/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1811900] Re: SRU 3.28 latest git to bionic

2019-04-17 Thread Treviño
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1811900

Title:
  SRU 3.28 latest git to bionic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1811900/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1811718] Re: Remove fbxkb from sync blacklist

2019-04-17 Thread Steve Langasek
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 fbxkb from sync blacklist

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fbxkb/+bug/1811718/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1816530] Re: DNS servers are not being set in the system correctly when you upgrade from 16.04 to 18.04

2019-04-17 Thread Zoltán Süle
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 notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1816530

Title:
  DNS servers are not being set in the system correctly when you upgrade
  from 16.04 to 18.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1816530/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1756972] Re: RM: gcc-4.8: no longer used

2019-04-17 Thread Steve Langasek
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.
https://bugs.launchpad.net/bugs/1756972

Title:
  RM: gcc-4.8: no longer used

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1756972/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1734568] Re: Please remove obsolete Android packages from Ubuntu

2019-04-17 Thread Steve Langasek
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
libwaudio1 1.8+13.10.20130807-0ubuntu1 in disco armhf
libwaudio1 1.8+13.10.20130807-0ubuntu1 in disco i386
libwaudio1-dev 1.8+13.10.20130807-0ubuntu1 in disco armhf
libwaudio1-dev 1.8+13.10.20130807-0ubuntu1 in disco i386
Comment: Ubuntu-specific, no uploads since 2013, unmaintained; LP: #1734568
1 package successfully removed.


** Changed in: android-audiosystem (Ubuntu)
   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/1734568

Title:
  Please remove obsolete Android packages from Ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/android-audiosystem/+bug/1734568/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1734568] Re: Please remove obsolete Android packages from Ubuntu

2019-04-17 Thread Steve Langasek
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 7-0ubuntu1 in disco i386
android-src-vendor 7-0ubuntu1 in disco ppc64el
android-src-vendor 7-0ubuntu1 in disco s390x
Comment: Ubuntu-specific, no uploads since 2014, unmaintained; LP: #1734568
1 package successfully removed.


** Changed in: android-src-vendor (Ubuntu)
   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/1734568

Title:
  Please remove obsolete Android packages from Ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/android-audiosystem/+bug/1734568/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1732733] Re: skytools3 demote to proposed for postgresql 10 transition

2019-04-17 Thread Steve Langasek
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.
https://bugs.launchpad.net/bugs/1732733

Title:
  skytools3 demote to proposed for postgresql 10 transition

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/skytools3/+bug/1732733/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1734568] Re: Please remove obsolete Android packages from Ubuntu

2019-04-17 Thread Steve Langasek
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 obsolete Android packages from Ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/android-audiosystem/+bug/1734568/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1754914] Re: Please remove gnome-themes-standard source, superseded by gnome-themes-extra

2019-04-17 Thread Steve Langasek
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 subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1754914

Title:
  Please remove gnome-themes-standard source, superseded by gnome-
  themes-extra

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-themes-standard/+bug/1754914/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1825229] Missing required logs.

2019-04-17 Thread Ubuntu Kernel Bot
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 nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

** Changed in: linux (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/1825229

Title:
  request to supercede the interim changes for 1815268  with upstream
  commit 8065a779

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825229/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1770680] Re: Please remove dune-grid [s390x]

2019-04-17 Thread Steve Langasek
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 => Won't Fix

** Changed in: dune-pdelab (Ubuntu)
   Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770680

Title:
  Please remove dune-grid [s390x]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dune-grid/+bug/1770680/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1768982] Re: Please move mess-desktop-entries to universe/games

2019-04-17 Thread Steve Langasek
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 in disco armhf: multiverse/gnome/optional/100% -> 
universe
mess-desktop-entries 0.2-4 in disco i386: multiverse/gnome/optional/100% -> 
universe
mess-desktop-entries 0.2-4 in disco ppc64el: multiverse/gnome/optional/100% -> 
universe
mess-desktop-entries 0.2-4 in disco s390x: multiverse/gnome/optional/100% -> 
universe
7 publications overridden.


** Changed in: mess-desktop-entries (Ubuntu)
   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/1768982

Title:
  Please move mess-desktop-entries to universe/games

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mess-desktop-entries/+bug/1768982/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1823836] Comment bridged from LTC Bugzilla

2019-04-17 Thread bugproxy
--- 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 4bb3583c228566958e2c6f34392c9e39e799bacf)

Correction:

When building libibverbs from the rdma-core from the master branch I do
NOT see the problem.

When using the libibverbs supplied with ubuntu 19.04
(libibverbs1/disco,now 22.1-1 ppc64el) the problem occurs.

Using libibverbs built from the debian/master branch of rdma-core, the
problem occurs.

(the results are the same with both the 5.0.7 kernel and 5.0.0-8-generic
kernel)

--- Comment From wil...@us.ibm.com 2019-04-17 18:25 EDT---
Mellanox case 601585.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823836

Title:
  dpdk app is reporting: net_mlx5: probe of PCI device  aborted
  after encountering an error: Unknown error -95

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1823836/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY

2019-04-17 Thread Tim Richardson
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://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1758287] Re: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent()

2019-04-17 Thread El jinete sin cabeza
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:

- https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153
+ https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153 
(DUPLICATE OF 
https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/143 )
  https://bugs.freedesktop.org/show_bug.cgi?id=110452 (RESOLVED NOTOURBUG)
  https://errors.ubuntu.com/problem/c7d8b2eb8ea371781ada6f2182d6926557d2fa91
  
  ---
  
  Backtrace goes through:
  
  totem -> clutter-gst (frame update) -> cogl (pipeline free) -> gstreamer
  (buffer free) -> gstreamer-vaapi (destroy objects) -> Nvidia libglvd
  (CommonMakeCurrent / InternalMakeCurrentVendor) -> Mesa GLX
  (MakeContextCurrent) -> Xlib (XError)
  
  Ubuntu bug doesn't say anything about what's the use-case / when this
  happens and whether it's reproducible (is it e.g. timing related), it
  seems just some random crash that Apport collects.
  
  In the backtrace Mesa MakeContextCurrent() calls __glXSendError() to tell 
that it was given invalid/bad context.  Corresponding Mesa code:
  ---
     if (gc) {
    /* Attempt to bind the context.  We do this before mucking with
     * gc and __glXSetCurrentContext to properly handle our state in
     * case of an error.
     *
     * If an error occurs, set the Null context since we've already
     * blown away our old context.  The caller is responsible for
     * figuring out how to handle setting a valid context.
     */
    if (gc->vtable->bind(gc, oldGC, draw, read) != Success) {
   __glXSetCurrentContextNull();
   __glXUnlock();
   __glXSendError(dpy, GLXBadContext, None, X_GLXMakeContextCurrent,
  False);
   return GL_FALSE;
    }
  ---
  
  I.e. bug is in what is given to Mesa, not what Mesa does.
  
  -> NOTOURBUG
  
  To me it looks something that could happen when Totem is exiting, gst-
  vaapi is trying to use resources that have already been freed, and X
  catching that when Gstreamer gstvaapitexture_glx.c::destroy_objects()
  ask libglvnd to do CommonMakeCurrent().
  
  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: totem 3.26.0-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Mar 23 11:26:51 2018
  ExecutablePath: /usr/bin/totem
  InstallationDate: Installed on 2017-05-04 (323 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170503)
  ProcCmdline: /usr/bin/totem --gapplication-service
  Signal: 5
  SourcePackage: totem
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libGLX_mesa.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libGLX.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstvaapi.so
  Title: totem crashed with signal 5
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

** No longer affects: gstreamer

** Also affects: totem via
   https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/143
   Importance: Unknown
   Status: Unknown

** Description changed:

- https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153 
(DUPLICATE OF 
https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/143 )
+ https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/153 DUPLICATE 
OF:
+ https://gitlab.freedesktop.org/gstreamer/gstreamer-vaapi/issues/143
+ 
  https://bugs.freedesktop.org/show_bug.cgi?id=110452 (RESOLVED NOTOURBUG)
  https://errors.ubuntu.com/problem/c7d8b2eb8ea371781ada6f2182d6926557d2fa91
  
  ---
  
  Backtrace goes through:
  
  totem -> clutter-gst (frame update) -> cogl (pipeline free) -> gstreamer
  (buffer free) -> gstreamer-vaapi (destroy objects) -> Nvidia libglvd
  (CommonMakeCurrent / InternalMakeCurrentVendor) -> Mesa GLX
  (MakeContextCurrent) -> Xlib (XError)
  
  Ubuntu bug doesn't say anything about what's the use-case / when this
  happens and whether it's reproducible (is it e.g. timing related), it
  seems just some random crash that Apport collects.
  
  In the backtrace Mesa MakeContextCurrent() calls __glXSendError() to tell 
that it was given invalid/bad context.  Corresponding Mesa code:
  ---
     if (gc) {
    /* Attempt to bind the context.  We do this before mucking with
     * gc and __glXSetCurrentContext to properly handle our state in
     * case of an error.
     *
     * If an error occurs, set the Null context since we've already
    

[Bug 1770792] Re: Clean up sync blacklist

2019-04-17 Thread Steve Langasek
> 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 of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1770792

Title:
  Clean up sync blacklist

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1770792/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1825224] [NEW] gnome-calendar cannot add credentialed web ics calendars

2019-04-17 Thread Erich Eickmeyer
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 calendar
would not be added.

The only workaround was to add the calendar using Evolution, which
properly accepted the username/app-password and added the calendar.
Unfortunately, at that point, I discovered bug #185227.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-calendar 3.32.0-1
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 17 11:39:29 2019
InstallationDate: Installed on 2019-04-15 (2 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190413.2)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-calendar
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-calendar (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug disco

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825224

Title:
  gnome-calendar cannot add credentialed web ics calendars

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-calendar/+bug/1825224/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1673258] Re: Remove aptdaemon and drop or port its reverse-dependencies

2019-04-17 Thread Steve Langasek
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 bug.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1673258

Title:
  Remove aptdaemon and drop or port its reverse-dependencies

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aptdaemon/+bug/1673258/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1823410] Re: utils.py's url_downloadable doesn't support https

2019-04-17 Thread Launchpad Bug Tracker
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 once per
uri thereby preventing situations where entries for the same server are
enabled and disabled. (LP: #1822886)
  * debian/control: build depend on the new version of update-manager which
supports checking to see if an https url is downloadable. (LP: #1823410)
  * tests/test_sources.list.py: add a test for https support.

 -- Brian Murray   Tue, 09 Apr 2019 18:05:01 -0700

** Changed in: ubuntu-release-upgrader (Ubuntu Bionic)
   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/1823410

Title:
  utils.py's url_downloadable doesn't support https

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1823410/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1823386] Re: [MRE] Please update to latest upstream release 7.2.17 & 7.3.4

2019-04-17 Thread Marc Deslauriers
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 in: php7.2 (Ubuntu Bionic)
 Assignee: (unassigned) => Marc Deslauriers (mdeslaur)

** Changed in: php7.2 (Ubuntu Cosmic)
 Assignee: (unassigned) => Marc Deslauriers (mdeslaur)

** Changed in: php7.2 (Ubuntu Disco)
 Assignee: (unassigned) => Marc Deslauriers (mdeslaur)

** Changed in: php7.2 (Ubuntu Bionic)
   Status: New => Confirmed

** Changed in: php7.2 (Ubuntu Cosmic)
   Status: New => Confirmed

** Changed in: php7.2 (Ubuntu Disco)
   Status: New => Confirmed

** Changed in: php7.2 (Ubuntu Bionic)
   Importance: Undecided => Medium

** Changed in: php7.2 (Ubuntu Cosmic)
   Importance: Undecided => Medium

** Changed in: php7.2 (Ubuntu Disco)
   Importance: Undecided => Medium

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-11034

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-11035

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823386

Title:
  [MRE] Please update to latest upstream release 7.2.17 & 7.3.4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php7.2/+bug/1823386/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1822886] Re: universe missing after bionic->cosmic do-release-upgrade

2019-04-17 Thread Launchpad Bug Tracker
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 once per
uri thereby preventing situations where entries for the same server are
enabled and disabled. (LP: #1822886)
  * debian/control: build depend on the new version of update-manager which
supports checking to see if an https url is downloadable. (LP: #1823410)
  * tests/test_sources.list.py: add a test for https support.

 -- Brian Murray   Tue, 09 Apr 2019 18:05:01 -0700

** Changed in: ubuntu-release-upgrader (Ubuntu Bionic)
   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/1822886

Title:
  universe missing after bionic->cosmic do-release-upgrade

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1822886/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1825228] [NEW] kpatch-dkms does not build with 5.0 kernels

2019-04-17 Thread Thadeu Lima de Souza Cascardo
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.

** Affects: kpatch (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: kpatch (Ubuntu Bionic)
 Importance: High
 Assignee: Thadeu Lima de Souza Cascardo (cascardo)
 Status: In Progress

** Also affects: kpatch (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: kpatch (Ubuntu Bionic)
 Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo)

** Changed in: kpatch (Ubuntu Bionic)
   Importance: Undecided => High

** Changed in: kpatch (Ubuntu Bionic)
   Status: New => In Progress

** Description changed:

- kpatch-dkms 0.5.0-0ubuntu1 from bionic does not build for linux-hwe-edge
- 5.0 kernels.
+ [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.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825228

Title:
  kpatch-dkms does not build with 5.0 kernels

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kpatch/+bug/1825228/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1813159] Re: remove from the archive, obsoleted by new split packaging

2019-04-17 Thread Steve Langasek
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.
https://bugs.launchpad.net/bugs/1813159

Title:
  remove from the archive, obsoleted by new split packaging

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vulkan/+bug/1813159/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1457400] Re: reduce 90s session kill timeout if the session does not shutdown cleanly

2019-04-17 Thread Rich Fiekowsky
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 #DefaultTimeoutStopSec=90 , one must also remove the # at the
beginning of the line, to uncomment it. Also, before I changed the conf
file, I had fast restarts sometimes by logging out before I restarted.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1457400

Title:
  reduce 90s session kill timeout if the session does not shutdown
  cleanly

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1457400/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1825163] Re: install fail

2019-04-17 Thread El jinete sin cabeza
@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.
https://bugs.launchpad.net/bugs/1825163

Title:
  install fail

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1825163/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1768688] Re: Please remove unmaintained gtk2 themes

2019-04-17 Thread Steve Langasek
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
gtk-clearlooks-gperfection2-theme 1.1-0ubuntu3 in disco armhf
gtk-clearlooks-gperfection2-theme 1.1-0ubuntu3 in disco i386
gtk-clearlooks-gperfection2-theme 1.1-0ubuntu3 in disco ppc64el
gtk-clearlooks-gperfection2-theme 1.1-0ubuntu3 in disco s390x
Comment: Obsolete, Ubuntu-specific, gtk2-only theme unmaintained since 2007; 
LP: #1768688
1 package successfully removed.


** Changed in: gtk-clearlooks-gperfection2-theme (Ubuntu)
   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/1768688

Title:
  Please remove unmaintained gtk2 themes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/blubuntu-look/+bug/1768688/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1823755] Re: linux-gke-4.15: 4.15.0-1030.32 -proposed tracker

2019-04-17 Thread Ubuntu Kernel Bot
** 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: kernel-sru-workflow/verification-testing
   Status: New => Confirmed

** 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 --
  boot-testing-requested: true
  kernel-stable-master-bug: 1822820
  phase: Promote to Proposed
  phase-changed: Wednesday, 17. April 2019 16:06 UTC
  reason:
-   promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror 
sync
+   automated-testing: Stalled -- testing FAILED
+   promote-to-proposed: Stalled -- packages are in the wrong component
+   regression-testing: Ongoing -- testing in progress
+   security-signoff: Pending -- waiting for signoff
+   verification-testing: Ongoing -- testing in progress

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1823755

Title:
  linux-gke-4.15: 4.15.0-1030.32 -proposed tracker

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1823755/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1772588] Re: Remove obsolete X11 drivers from the archive

2019-04-17 Thread Steve Langasek
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 Ubuntu.
https://bugs.launchpad.net/bugs/1772588

Title:
  Remove obsolete X11 drivers from the archive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xf86-input-mtrack/+bug/1772588/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1768688] Re: Please remove unmaintained gtk2 themes

2019-04-17 Thread Steve Langasek
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
gtk2-engines-equinox 1.50-0ubuntu4 in disco i386
gtk2-engines-equinox 1.50-0ubuntu4 in disco ppc64el
gtk2-engines-equinox 1.50-0ubuntu4 in disco s390x
Comment: Obsolete, Ubuntu-specific, gtk2-only theme unmaintained since 2011; 
LP: #1768688
1 package successfully removed.


** Changed in: gtk2-engines-equinox (Ubuntu)
   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/1768688

Title:
  Please remove unmaintained gtk2 themes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/blubuntu-look/+bug/1768688/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1805490] Re: Grub2 Failed to install "efibootmgr failed to register the boot entry: Block device required."

2019-04-17 Thread Mathieu Trudel-Lapierre
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 much at the point
where things are trying to delete the variable. It's either at deleting
the variable itself, or updating BootOrder.

Could you please run the following command, so as to give us more
information to address this issue?

sudo strace -ff efibootmgr -b  -B

Could you also run:

ls -l /sys/firmware/efi/efivars/

This will give us more information to hopefully fix this issue.

It seems like you're also seeing this on a Dell XPS 13 (9343), seemingly
with BIOS revision A15. Judging from
https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1753518/comments/32;
there's a BIOS A18 available from Dell that might address the issue.
Now, I'm not absolutely certain that the new *revision* fixes the issue,
but updating the firmware might clear things that would fix this. That's
partly why we need the extra information (so please run the commands
above before updating BIOS).

** Package changed: grub2-signed (Ubuntu Disco) => efibootmgr (Ubuntu
Disco)

** Changed in: efibootmgr (Ubuntu Disco)
   Status: Triaged => Incomplete

** Summary changed:

- Grub2 Failed to install "efibootmgr failed to register the boot entry: Block 
device required."
+ [master] Grub2 Failed to install "efibootmgr failed to register the boot 
entry: Block device required."

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1805490

Title:
  [master] Grub2 Failed to install "efibootmgr failed to register the
  boot entry: Block device required."

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/efibootmgr/+bug/1805490/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1729947] Re: /usr/bin/budgie-polkit-dialog:11:g_data_set_internal:g_datalist_id_set_data_full:g_object_unref:_vala_main:__libc_start_main

2019-04-17 Thread fossfreedom
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: verification-done verification-done-bionic 
verification-done-cosmic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1729947

Title:
  /usr/bin/budgie-polkit-
  
dialog:11:g_data_set_internal:g_datalist_id_set_data_full:g_object_unref:_vala_main:__libc_start_main

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1729947/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1784391] Re: Please remove python-mmkeys from archive

2019-04-17 Thread Steve Langasek
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.
https://bugs.launchpad.net/bugs/1784391

Title:
  Please remove python-mmkeys from archive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sonata/+bug/1784391/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1768688] Re: Please remove unmaintained gtk2 themes

2019-04-17 Thread Steve Langasek
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 disco i386
silicon-theme 0.1-0ubuntu2 in disco ppc64el
silicon-theme 0.1-0ubuntu2 in disco s390x
Comment: Obsolete, Ubuntu-specific, gtk2-only theme unmaintained since 2007; 
LP: #1768688
1 package successfully removed.


** Changed in: silicon-theme (Ubuntu)
   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/1768688

Title:
  Please remove unmaintained gtk2 themes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/blubuntu-look/+bug/1768688/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1811914] Re: Please remove rsbac-admin from Ubuntu

2019-04-17 Thread Steve Langasek
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
libnss-rsbac2 1.4.0-repack-0ubuntu8 in disco s390x
libpam-rsbac 1.4.0-repack-0ubuntu8 in disco amd64
libpam-rsbac 1.4.0-repack-0ubuntu8 in disco armhf
libpam-rsbac 1.4.0-repack-0ubuntu8 in disco i386
libpam-rsbac 1.4.0-repack-0ubuntu8 in disco s390x
librsbac-dev 1.4.0-repack-0ubuntu8 in disco amd64
librsbac-dev 1.4.0-repack-0ubuntu8 in disco armhf
librsbac-dev 1.4.0-repack-0ubuntu8 in disco i386
librsbac-dev 1.4.0-repack-0ubuntu8 in disco s390x
librsbac1 1.4.0-repack-0ubuntu8 in disco amd64
librsbac1 1.4.0-repack-0ubuntu8 in disco armhf
librsbac1 1.4.0-repack-0ubuntu8 in disco i386
librsbac1 1.4.0-repack-0ubuntu8 in disco s390x
rsbac-admin 1.4.0-repack-0ubuntu8 in disco amd64
rsbac-admin 1.4.0-repack-0ubuntu8 in disco armhf
rsbac-admin 1.4.0-repack-0ubuntu8 in disco i386
rsbac-admin 1.4.0-repack-0ubuntu8 in disco s390x
rsbac-doc 1.4.0-repack-0ubuntu8 in disco amd64
rsbac-doc 1.4.0-repack-0ubuntu8 in disco arm64
rsbac-doc 1.4.0-repack-0ubuntu8 in disco armhf
rsbac-doc 1.4.0-repack-0ubuntu8 in disco i386
rsbac-doc 1.4.0-repack-0ubuntu8 in disco ppc64el
rsbac-doc 1.4.0-repack-0ubuntu8 in disco s390x
rsbac-klogd 1.4.0-repack-0ubuntu8 in disco amd64
rsbac-klogd 1.4.0-repack-0ubuntu8 in disco armhf
rsbac-klogd 1.4.0-repack-0ubuntu8 in disco i386
rsbac-klogd 1.4.0-repack-0ubuntu8 in disco s390x
Comment: Ubuntu-specific (removed from Debian in 2006), unmaintained, not 
synced with upstream since 2009, depends on a patched kernel; LP: #1811914
1 package successfully removed.


** Changed in: rsbac-admin (Ubuntu)
   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/1811914

Title:
  Please remove rsbac-admin from Ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsbac-admin/+bug/1811914/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1824443] Re: [RM] watershed: Ubuntu-specific, no reverse-dependencies

2019-04-17 Thread Steve Langasek
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
watershed 9 in disco s390x
watershed-udeb 9 in disco amd64
watershed-udeb 9 in disco arm64
watershed-udeb 9 in disco armhf
watershed-udeb 9 in disco i386
watershed-udeb 9 in disco ppc64el
watershed-udeb 9 in disco s390x
Comment: Ubuntu-specific, unmaintained, and no longer used; LP: #1824443
1 package successfully removed.


** Changed in: watershed (Ubuntu)
   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/1824443

Title:
  [RM] watershed: Ubuntu-specific, no reverse-dependencies

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/watershed/+bug/1824443/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1825246] Re: Mysql 5.7 mysql.pid Apparmor Denial

2019-04-17 Thread Gold Star
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,
  /var/run/mysqld/mysqld.sock rw,
  /var/run/mysqld/mysqld.sock.lock rw,
  /run/mysqld/mysqld.pid rw,
  /run/mysqld/mysqld.sock rw,
  /run/mysqld/mysqld.sock.lock rw,

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825246

Title:
  Mysql 5.7 mysql.pid Apparmor Denial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1825246/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1790657] Re: amqp-tools server parameter unusable

2019-04-17 Thread timeless
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 because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1790657

Title:
  amqp-tools server parameter unusable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/librabbitmq/+bug/1790657/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1798184] Re: [SRU] PY3: python3-ldap does not allow bytes for DN/RDN/field names

2019-04-17 Thread Shashinandan Kolar Srinivasa
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.
https://bugs.launchpad.net/bugs/1798184

Title:
  [SRU] PY3: python3-ldap does not allow bytes for DN/RDN/field names

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1798184/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1824434] Re: [0-day SRU] MAAS 2.6.0beta1

2019-04-17 Thread Andres Rodriguez
** 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
   - ESXi storage support
   - ESXi vCenter registration
   - DB performance improvements
   - UI performance improvements
   - TFTP performance improvements
   - Performance profiling and tracking.
+  - OpenBMC power driver
+  - Better boot process output.
  
  Upcoming releases are targeted to only include bug fixes.
  
  Testing
  ==
  
  Testing performed:
  
   - CI testing
   - Manual UI testing
   - Fresh install testing
   - Upgrade testing
  
  Releases
  ===
  Current beta release contains all features targeted for 2.6. Currently sits 
in beta due to continues UI work.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824434

Title:
  [0-day SRU] MAAS 2.6.0beta1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1824434/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1825246] [NEW] Mysql 5.7 mysql.pid Apparmor Denial

2019-04-17 Thread Gold Star
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 not in the profile based
on the following output:

Profile:  /usr/sbin/mysqld
Path: /run/mysqld/mysql.pid
Mode: rw
Severity: unknown

 [1 - /run/mysqld/mysql.pid]
[(A)llow] / (D)eny / (I)gnore / (G)lob / Glob with (E)xtension / (N)ew / 
Abo(r)t / (F)inish / (M)ore
Adding /run/mysqld/mysql.pid rw to profile


Debugging info:


cat /etc/issue

Ubuntu 16.04.6 LTS \n \l


---

apt-cache policy mysql-server*

mysql-server-5.0:
  Installed: (none)
  Candidate: (none)
  Version table:
mysql-server-5.1:
  Installed: (none)
  Candidate: (none)
  Version table:
mysql-server-5.5:
  Installed: (none)
  Candidate: (none)
  Version table:
mysql-server-5.6:
  Installed: (none)
  Candidate: (none)
  Version table:
mysql-server-5.7:
  Installed: 5.7.25-0ubuntu0.16.04.2
  Candidate: 5.7.25-0ubuntu0.16.04.2
  Version table:
 *** 5.7.25-0ubuntu0.16.04.2 500
500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
100 /var/lib/dpkg/status
 5.7.11-0ubuntu6 500
500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
mysql-server:
  Installed: 5.7.25-0ubuntu0.16.04.2
  Candidate: 5.7.25-0ubuntu0.16.04.2
  Version table:
 *** 5.7.25-0ubuntu0.16.04.2 500
500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main i386 
Packages
500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu xenial-security/main i386 Packages
100 /var/lib/dpkg/status
 5.7.11-0ubuntu6 500
500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages
mysql-server-core-5.1:
  Installed: (none)
  Candidate: (none)
  Version table:
mysql-server-core-5.5:
  Installed: (none)
  Candidate: (none)
  Version table:
mysql-server-core-5.6:
  Installed: (none)
  Candidate: (none)
  Version table:
mysql-server-core-5.7:
  Installed: 5.7.25-0ubuntu0.16.04.2
  Candidate: 5.7.25-0ubuntu0.16.04.2
  Version table:
 *** 5.7.25-0ubuntu0.16.04.2 500
500 http://us.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
100 /var/lib/dpkg/status
 5.7.11-0ubuntu6 500
500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

** This system was upgraded from 14.04 using do-upgrade-release **

** Affects: mysql-5.7 (Ubuntu)
 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/1825246

Title:
  Mysql 5.7 mysql.pid Apparmor Denial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1825246/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1790657] Re: amqp-tools server parameter unusable

2019-04-17 Thread Launchpad Bug Tracker
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:
  amqp-tools server parameter unusable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/librabbitmq/+bug/1790657/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1823753] Re: arm64: cma_alloc errors at boot

2019-04-17 Thread dann frazier
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 manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823753/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 486154] Re: System beep broken in Karmic despite heroic efforts to fix it

2019-04-17 Thread Launchpad Bug Tracker
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

Title:
  System beep broken in Karmic despite heroic efforts to fix it

To manage notifications about this bug go to:
https://bugs.launchpad.net/metacity/+bug/486154/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 1570617] Re: [MIR] edk2

2019-04-17 Thread dann frazier
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
> accidentally mis-filed eight of them.

Can you point me to them?

> This package provides a boot environment; I must admit that I don't
> understand it well.

Happy to answer questions or demo it for you - just let me know.

> - Build-Depends: debhelper, uuid-dev, iasl, gcc-multilib [i386], nasm,
>   python, gcc-aarch64-linux-gnu, gcc-arm-linux-gnueabihf, genisoimage,
>   qemu-utils, qemu-system-x86, python3
>
> - Embeds OpenSSL cryptographic library
> - Probably doesn't daemonize

Correct

> - Probably doesn't listen on the network
>   - However, it includes many network client services, likely to use
> during PXE booting or similar
> - No pre/post inst/rm
> - No init scripts
> - No systemd unit files
> - No dbus services
> - No binaries in PATH
> - No sudo fragments
> - No udev rules
> - Probably no test suite

No built-in one, but see below...

> - No cron jobs
> - Build logs use -Werror -- the logs give misleading impression.
>
> - It's difficult to tell if subprocesses are spawned

You can certainly run EFI apps in it, so in a sense

> - Memory management varies; cppcheck finds many faults, but they may not
>   be in code that matters
> - Extensive file IO, it's difficult to tell how much would happen in the
>   context of a host vs a guest

While I consider it more of a QEMU vector than edk2 itself, it is
possible for this firmware, or EFI apps it runs, to access devices on
the host if QEMU allows it. For example, we have seen bugs[1][2] where
shim in a guest corrupts the guest's firmware image on the host. But
that's only possible because QEMU was given write access to that
image.

[1] https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1811901
[2] https://bugs.launchpad.net/ubuntu/+source/shim-signed/+bug/1811722

> - Extensive logging, spot checks showed no unsafe logging
> - Extensive cryptography, entirely unchecked
> - I didn't discover privileged vs unprivileged portions of code
> - Some privileged operations in the code but many appear to be available
>   as platform services
> - One instance of an unsafe write to /tmp/col in Oniguruma regular
>   expression engine. It is probably ifdef'd out.
> - No WebKit
> - No PolicyKit
> - Many cppcheck results reporting real bugs.
>
> This codebase is huge. I'm still not clear on what most of it is used for,
> or what threat model is assumed.

One security-relevant thing to note is that edk2 will be responsible
for the firmware-aspect of SecureBoot for QEMU guests booted in
SecureBoot mode.

> Code quality looked mixed: cppcheck reported a lot more results than I'd
> like to see, but the code I studied via the uaudit greps was high quality.
>
> In order to properly support edk2, the security team will need help from
> other teams. So, the security team is providing a provisional ACK for
> promoting edk2 to main once the following conditions are met:
>
> First, Dann has volunteered to strip out the Pythons, Lua, pccts, and
> perhaps other smaller pieces as testing indicates that they can be
> removed. We'd like these stripped before moving the package to main.

Yep - on my todo list for 19.10 devel.

> Second, someone needs to commit to working with the security team to
> properly triage edk2 issues as they arise.

I volunteer for this, but of course, I alone would be a SPOF.

> Third, someone needs to commit to testing packages that the security team
> prepares for our stable releases, for whatever lifetime is appropriate.
> (If, in six years, edk2 is included in 20.04 LTS's ESM offering due to
> customer interest, this team will need to commit to helping test 20.04's
> EDK2 until 2030, or whenever 20.04 LTS's ESM support offering comes to
> a close, as well as all future LTS releases that include edk2 in main.)

I can't personally commit to, well, anything for 10 years :) I wonder
if the server or foundations teams would be willing to "host" this
responsibility, with me owning it on their behalf for now?

Also, could the testing issue be solved w/ an automated test suite?
I've been wanting to find the time to implement one anyway. I'm not
sure yet if this could be done well w/ autopkgtest - ideally we'd be
able to test e.g. Windows guests, and I haven't looked into how
feasible that would be in the autopkgtest framework.

  -dann


> Please comment in this bug to sign up for these obligations.
>
> Thanks
>
>
> ** Changed in: edk2 (Ubuntu)
>  Assignee: Ubuntu Security Team (ubuntu-security) => (unassigned)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1570617
>
> Title:
>   [MIR] edk2
>
> To manage notifications about this bug go to:
> 

[Bug 1758287] Re: totem crashed with SIGTRAP in __glXSendError() from MakeContextCurrent()

2019-04-17 Thread Bug Watch Updater
** 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
  MakeContextCurrent()

To manage notifications about this bug go to:
https://bugs.launchpad.net/gstreamer/+bug/1758287/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1825209] Re: Automatic suspend delay is at least 15 mins

2019-04-17 Thread Mate Varga
*** 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 Ubuntu.
https://bugs.launchpad.net/bugs/1825209

Title:
  Automatic suspend delay is at least 15 mins

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1825209/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1825099] Re: Unable to deploy Xenial on a s390x KVM

2019-04-17 Thread Frank Heimes
+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 about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1825099/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1756979] Re: RM: gcc-5: no longer used

2019-04-17 Thread Steve Langasek
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.
https://bugs.launchpad.net/bugs/1756979

Title:
  RM: gcc-5: no longer used

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-5/+bug/1756979/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1748702] Re: Please upgrade that old version

2019-04-17 Thread Steve Langasek
** 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 this bug go to:
https://bugs.launchpad.net/ubuntu/+source/acpi-support/+bug/1748702/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1756979] Re: RM: gcc-5: no longer used

2019-04-17 Thread Steve Langasek
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.
https://bugs.launchpad.net/bugs/1756979

Title:
  RM: gcc-5: no longer used

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-5/+bug/1756979/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1825239] [NEW] Enable support for trusty ESM

2019-04-17 Thread Andreas Hasenack
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, which is subscribed to ubuntu-advantage-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1825239

Title:
  Enable support for trusty ESM

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1825239/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1825239] [NEW] Enable support for trusty ESM

2019-04-17 Thread Andreas Hasenack
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 is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825239

Title:
  Enable support for trusty ESM

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-advantage-tools/+bug/1825239/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1768688] Re: Please remove unmaintained gtk2 themes

2019-04-17 Thread Steve Langasek
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 in disco armhf
gtk2-engines-blueheart 0.20070123-0ubuntu2 in disco i386
gtk2-engines-blueheart 0.20070123-0ubuntu2 in disco ppc64el
gtk2-engines-blueheart 0.20070123-0ubuntu2 in disco s390x
Comment: Obsolete, Ubuntu-specific, gtk2-only theme unmaintained since 2007; 
LP: #1768688
1 package successfully removed.


** Changed in: gtk2-engines-blueheart (Ubuntu)
   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/1768688

Title:
  Please remove unmaintained gtk2 themes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/blubuntu-look/+bug/1768688/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1787254] Re: Possibly demote fwupdate to universe?

2019-04-17 Thread Steve Langasek
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.

Override component to universe
fwupdate 12-3ubuntu2 in disco: main/misc -> universe
fwupdate 12-3ubuntu2 in disco amd64: main/admin/optional/100% -> universe
fwupdate 12-3ubuntu2 in disco arm64: main/admin/optional/100% -> universe
fwupdate 12-3ubuntu2 in disco armhf: main/admin/optional/100% -> universe
fwupdate 12-3ubuntu2 in disco i386: main/admin/optional/100% -> universe
fwupdate-amd64-signed-template 12-3ubuntu2 in disco amd64: 
universe/libs/optional/100% -> universe
fwupdate-arm64-signed-template 12-3ubuntu2 in disco arm64: 
universe/libs/optional/100% -> universe
fwupdate-armhf-signed-template 12-3ubuntu2 in disco armhf: 
universe/libs/optional/100% -> universe
fwupdate-i386-signed-template 12-3ubuntu2 in disco i386: 
universe/libs/optional/100% -> universe
libfwup-dev 12-3ubuntu2 in disco amd64: universe/libdevel/optional/100% -> 
universe
libfwup-dev 12-3ubuntu2 in disco arm64: universe/libdevel/optional/100% -> 
universe
libfwup-dev 12-3ubuntu2 in disco armhf: universe/libdevel/optional/100% -> 
universe
libfwup-dev 12-3ubuntu2 in disco i386: universe/libdevel/optional/100% -> 
universe
libfwup1 12-3ubuntu2 in disco amd64: main/libs/optional/100% -> universe
libfwup1 12-3ubuntu2 in disco arm64: main/libs/optional/100% -> universe
libfwup1 12-3ubuntu2 in disco armhf: main/libs/optional/100% -> universe
libfwup1 12-3ubuntu2 in disco i386: main/libs/optional/100% -> universe
fwupdate-amd64-signed-template 12-3ubuntu2 in disco amd64 remained the same
fwupdate-arm64-signed-template 12-3ubuntu2 in disco arm64 remained the same
fwupdate-armhf-signed-template 12-3ubuntu2 in disco armhf remained the same
fwupdate-i386-signed-template 12-3ubuntu2 in disco i386 remained the same
libfwup-dev 12-3ubuntu2 in disco amd64 remained the same
libfwup-dev 12-3ubuntu2 in disco arm64 remained the same
libfwup-dev 12-3ubuntu2 in disco armhf remained the same
libfwup-dev 12-3ubuntu2 in disco i386 remained the same
9 publications overridden; 8 publications remained the same.

And unsubscribing ubuntu-archive.

** Changed in: fwupdate (Ubuntu)
   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/1787254

Title:
  Possibly demote fwupdate to universe?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fwupdate/+bug/1787254/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1753518] Re: package grub-efi-amd64-signed 1.93+2.02-2ubuntu8 failed to install/upgrade: installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 1

2019-04-17 Thread Mathieu Trudel-Lapierre
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 check with Dell if firmware updates exist. This is 
especially true for Dell XPS 13 (9343)). We will be tracking this (Invalid 
argument, followed by "Block device required" error messages) on bug 1805490.

If you are getting an "Input/output error"; please file your own NEW bug
report, and make sure to include the output of  "sudo efibootmgr -v". We
will ask you for more information on your own bug.

If you are getting "No space left on device"; please file your own NEW
bug report, and make sure to include the output of "ls -l
/sys/firmware/efi/efivars". We will ask you for more information on your
own bug.

If you are getting "grub-install: error: cannot find EFI directory.",
you have likely modified your installation in some way. Please file your
own NEW bug report, we can walk you through fixing this.

If you are getting any other kind of error not listed above; as for
everything else, please file a your own NEW bug report, so we can figure
out exactly what your problem is, not "guessing" based on what others
may have commented.

And above all, please do not follow random comments by people on bug
reports claiming they have workarounds. These may further complicate
things, it makes it very hard for developers to understand what is going
on and be able to fix bugs.

** Changed in: grub2-signed (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1753518

Title:
  package grub-efi-amd64-signed 1.93+2.02-2ubuntu8 failed to
  install/upgrade: installed grub-efi-amd64-signed package post-
  installation script subprocess returned error exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2-signed/+bug/1753518/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1824102] Re: Animations leave window artifacts when enabled

2019-04-17 Thread fossfreedom
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)
packages also displayed animations correctly.

** Tags removed: verification-needed verification-needed-bionic 
verification-needed-cosmic
** Tags added: verification-done verification-done-bionic 
verification-done-cosmic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824102

Title:
  Animations leave window artifacts when enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1824102/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1824229] Re: [SRU] Custom keyboard shortcuts occasionally stop working

2019-04-17 Thread fossfreedom
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 that a fully uptodate bionic + budgie upgrade works. Then
repeated testing with the new mutter (libmutter-2-0 mutter-common)
packages to doubly check all was well.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824229

Title:
  [SRU] Custom keyboard shortcuts occasionally stop working

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1824229/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1805490] Re: [master] Grub2 Failed to install "efibootmgr failed to register the boot entry: Block device required."

2019-04-17 Thread Mathieu Trudel-Lapierre
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 because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1805490

Title:
  [master] Grub2 Failed to install "efibootmgr failed to register the
  boot entry: Block device required."

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/efibootmgr/+bug/1805490/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1825050] Re: Raven remains open when switching workspaces

2019-04-17 Thread fossfreedom
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 also dismissed raven correctly when moving to a new workspace.


** Tags removed: verification-needed verification-needed-bionic 
verification-needed-cosmic
** Tags added: verification-done verification-done-bionic 
verification-done-cosmic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825050

Title:
  Raven remains open when switching workspaces

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/budgie-desktop/+bug/1825050/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1811900] Re: SRU 3.28 latest git to bionic

2019-04-17 Thread fossfreedom
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

Title:
  SRU 3.28 latest git to bionic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1811900/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1797436] Re: Please move comic-neue to universe

2019-04-17 Thread Steve Langasek
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: multiverse/fonts/optional/100% -> 
universe
fonts-comic-neue 2.4-2 in disco i386: multiverse/fonts/optional/100% -> universe
fonts-comic-neue 2.4-2 in disco ppc64el: multiverse/fonts/optional/100% -> 
universe
fonts-comic-neue 2.4-2 in disco s390x: multiverse/fonts/optional/100% -> 
universe
7 publications overridden.


** Changed in: comic-neue (Ubuntu)
   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/1797436

Title:
  Please move comic-neue to universe

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/comic-neue/+bug/1797436/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1789100] Re: Please remove src:node-tar-pack from cosmic

2019-04-17 Thread Steve Langasek
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.
https://bugs.launchpad.net/bugs/1789100

Title:
  Please remove src:node-tar-pack from cosmic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/node-tar-pack/+bug/1789100/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1793971] Re: RM: qca-qt5, binaries overtaken by qca2

2019-04-17 Thread Steve Langasek
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 are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1793971

Title:
  RM: qca-qt5, binaries overtaken by qca2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qca-qt5/+bug/1793971/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1808538] Re: Please remove src:lua-torch-cutorch

2019-04-17 Thread Steve Langasek
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.
https://bugs.launchpad.net/bugs/1808538

Title:
  Please remove src:lua-torch-cutorch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lua-torch-cutorch/+bug/1808538/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1825163] Re: install fail

2019-04-17 Thread DiQ
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:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1825163/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1821610] Re: is openbve-data useful without openbve?

2019-04-17 Thread Paul Sladen
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 engines; eg. the freeware-no-
source BVE Trainsim running under Wine).

** Bug watch added: github.com/leezer3/OpenBVE/issues #330
   https://github.com/leezer3/OpenBVE/issues/330

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821610

Title:
  is openbve-data useful without openbve?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openbve-data/+bug/1821610/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1770792] Re: Clean up sync blacklist

2019-04-17 Thread Steve Langasek
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 merged from
Debian but I don't see any reason in principle that it couldn't be.

Why are you dropping the blacklist of fbxkb, which was identified in the
blacklist file as "obsolete GNOME panel applet"?

I am satisfied that the rest of the changes here are correct, however I
would want the rationales to be better documented in the commit history.
I would ask you to please:

 - rebase on the current sync-blacklist branch (there is a conflict)
 - divide the commits up according to rationale (e.g., dropped because package 
removed from unstable; vs dropped because package is now in Ubuntu again; vs. 
reshuffling of file contents)
 - resubmit

Or, you can punt this to me to do and I'll apply these changes when I
have a chance.

** Changed in: ubuntu-meta (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/1770792

Title:
  Clean up sync blacklist

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1770792/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1825222] [NEW] Is it possible to enable CONFIG_ARCH_ROCKCHIP in ubuntu 18.04 (armhf and aarch64) kernel config?

2019-04-17 Thread Paweł Jarosz
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
CONFIG_SPI_ROCKCHIP
CONFIG_PINCTRL_ROCKCHIP
CONFIG_ROCKCHIP_IODOMAIN
CONFIG_ROCKCHIP_THERMAL
CONFIG_VIDEO_ROCKCHIP_RGA
CONFIG_DRM_ROCKCHIP
CONFIG_ROCKCHIP_ANALOGIX_DP
CONFIG_ROCKCHIP_CDN_DP
CONFIG_ROCKCHIP_DW_HDMI
CONFIG_ROCKCHIP_DW_MIPI_DSI
CONFIG_ROCKCHIP_INNO_HDMI
CONFIG_ROCKCHIP_LVDS
CONFIG_ROCKCHIP_RGB
CONFIG_SND_SOC_ROCKCHIP
CONFIG_SND_SOC_ROCKCHIP_I2S
CONFIG_SND_SOC_ROCKCHIP_PDM
CONFIG_SND_SOC_ROCKCHIP_SPDIF
CONFIG_SND_SOC_ROCKCHIP_MAX98090
CONFIG_SND_SOC_ROCKCHIP_RT5645
CONFIG_MMC_DW_ROCKCHIP
CONFIG_ROCKCHIP_TIMER
CONFIG_ROCKCHIP_MBOX
CONFIG_ROCKCHIP_IOMMU
CONFIG_ROCKCHIP_GRF
CONFIG_ROCKCHIP_PM_DOMAINS
CONFIG_DEVFREQ_EVENT_ROCKCHIP_DFI
CONFIG_ROCKCHIP_SARADC
CONFIG_PWM_ROCKCHIP
CONFIG_PHY_ROCKCHIP_DP
CONFIG_PHY_ROCKCHIP_EMMC
CONFIG_PHY_ROCKCHIP_INNO_HDMI
CONFIG_PHY_ROCKCHIP_INNO_USB2
CONFIG_PHY_ROCKCHIP_PCIE
CONFIG_PHY_ROCKCHIP_TYPEC
CONFIG_PHY_ROCKCHIP_USB
CONFIG_ROCKCHIP_EFUSE
CONFIG_CRYPTO_DEV_ROCKCHIP

Cheers,
Paweł Jarosz

** Affects: linux-hwe (Ubuntu)
 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/1825222

Title:
  Is it possible to enable CONFIG_ARCH_ROCKCHIP in ubuntu 18.04 (armhf
  and aarch64) kernel config?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1825222/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1699530] Re: Remove gogglesmm package

2019-04-17 Thread Steve Langasek
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
gogglesmm 0.12.7-3build2 in disco ppc64el
gogglesmm 0.12.7-3build2 in disco s390x
Comment: Upstream requests not to release stale upstream version; LP: #1699530
1 package successfully removed.


** Changed in: gogglesmm (Ubuntu)
   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/1699530

Title:
  Remove gogglesmm package

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gogglesmm/+bug/1699530/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1721909] Re: Goodix GF3208 (fingerprint reader) not being recognised by kernel/system

2019-04-17 Thread Simone Pernice
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
Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 002: ID 058f:3841 Alcor Micro Corp. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1721909

Title:
  Goodix GF3208 (fingerprint reader) not being recognised  by
  kernel/system

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1721909/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1821491] Re: DNS lookup fails for local hosts

2019-04-17 Thread Dan Streetman
> 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 defined:
> phspi05 192.168.2.35
> phspi05.phs 192.168.2.35

you don't need the router configured to resolve the "single label"
(without .phs) hostname (unless your router doesn't have 'phs' in its
resolv.conf search list, and you need to look up the hostname from the
router itself).

> on laptop
> dig phspi05 = fails

stop using dig to debug your system.  the behavior above is correct (dig
*should* fail when querying the local systemd-resolved resolver without
using .phs domain suffix).  Instead try using a program that uses
getaddrinfo(), like nslookup, ping, or even host.  e.g.:

$ host phspi05

> I guess I have a workaround to manually edit resolv.conf, and as I don't
> reboot that often it is not a big issue, but it doesn't feel right somehow.

it isn't right, and you don't need to.  Just make sure your router
delivers your domain as part of its dhcp reply, and you will be fine.
Your resolv.conf will contain your local domain in its 'search' and all
programs on your system using getaddrinfo() and friends will correctly
look up any address with your domain appended.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821491

Title:
  DNS lookup fails for local hosts

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1821491/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1732475] Re: node-mapnik doesn't work, link errors

2019-04-17 Thread Steve Langasek
** 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 => 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/1732475

Title:
  node-mapnik doesn't work, link errors

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/node-mapnik/+bug/1732475/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1728241] Re: stjerm project is abandoned(unmaintained) upstream -- please remove from archives

2019-04-17 Thread Steve Langasek
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 (it builds from source; it has no obsolete library
dependencies).

It doesn't seem necessary to remove this package from the archive.

** Changed in: stjerm (Ubuntu)
   Status: Confirmed => Incomplete

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1728241

Title:
  stjerm project is abandoned(unmaintained) upstream -- please remove
  from archives

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/stjerm/+bug/1728241/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1716338] Re: please kick out from artful, move to proposed

2019-04-17 Thread Steve Langasek
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.
https://bugs.launchpad.net/bugs/1716338

Title:
  please kick out from artful, move to proposed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ruby-kramdown-rfc2629/+bug/1716338/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1816530] Re: DNS servers are not being set in the system correctly when you upgrade from 16.04 to 18.04

2019-04-17 Thread Dan Streetman
> 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 feel free to update this bug.

** Changed in: resolvconf (Ubuntu)
   Status: Incomplete => Invalid

** Changed in: resolvconf (Ubuntu)
 Assignee: Dan Streetman (ddstreet) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1816530

Title:
  DNS servers are not being set in the system correctly when you upgrade
  from 16.04 to 18.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1816530/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1729876] Re: please remove libvideo-frequencies-perl from disco

2019-04-17 Thread Steve Langasek
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 armhf
libvideo-frequencies-perl 0.03-1ubuntu1 in disco i386
libvideo-frequencies-perl 0.03-1ubuntu1 in disco ppc64el
libvideo-frequencies-perl 0.03-1ubuntu1 in disco s390x
Comment: Ubuntu-specific, superseded by libvideo-capture-v4l-perl; LP: #1729876
1 package successfully removed.


** Changed in: libvideo-frequencies-perl (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/1729876

Title:
  please remove libvideo-frequencies-perl from disco

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvideo-frequencies-perl/+bug/1729876/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1768688] Re: Please remove unmaintained gtk2 themes

2019-04-17 Thread Steve Langasek
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
blubuntu-look 0.3.1 in disco ppc64el
blubuntu-look 0.3.1 in disco s390x
blubuntu-session-splashes 0.3.1 in disco amd64
blubuntu-session-splashes 0.3.1 in disco arm64
blubuntu-session-splashes 0.3.1 in disco armhf
blubuntu-session-splashes 0.3.1 in disco i386
blubuntu-session-splashes 0.3.1 in disco ppc64el
blubuntu-session-splashes 0.3.1 in disco s390x
blubuntu-theme 0.3.1 in disco amd64
blubuntu-theme 0.3.1 in disco arm64
blubuntu-theme 0.3.1 in disco armhf
blubuntu-theme 0.3.1 in disco i386
blubuntu-theme 0.3.1 in disco ppc64el
blubuntu-theme 0.3.1 in disco s390x
blubuntu-wallpapers 0.3.1 in disco amd64
blubuntu-wallpapers 0.3.1 in disco arm64
blubuntu-wallpapers 0.3.1 in disco armhf
blubuntu-wallpapers 0.3.1 in disco i386
blubuntu-wallpapers 0.3.1 in disco ppc64el
blubuntu-wallpapers 0.3.1 in disco s390x
Comment: Obsolete, Ubuntu-specific, gtk2-only theme unmaintained since 2010; 
LP: #1768688
1 package successfully removed.


** Changed in: blubuntu-look (Ubuntu)
   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/1768688

Title:
  Please remove unmaintained gtk2 themes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/blubuntu-look/+bug/1768688/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1825237] [NEW] installation crashed

2019-04-17 Thread Ale
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: 1.402
Date: Wed Apr 17 17:10:43 2019
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
boot=casper quiet splash ---
LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubiquity (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug disco ubiquity-19.04.7 ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825237

Title:
  installation crashed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1825237/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1825054] Re: My JavaFx project stopped compiling

2019-04-17 Thread Kristof Szilagyi
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 11 (I did try that before and some of my
tools stopped working but hopefully by now they are fixed)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825054

Title:
  My JavaFx project stopped compiling

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openjfx/+bug/1825054/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1825234] Re: Python3: After do-release-upgrade, all apt-installed modules need to be reinstalled, or they fail

2019-04-17 Thread Ubuntu Foundations Team Bug Bot
** 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
  be reinstalled, or they fail

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1825234/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1824434] Re: [0-day SRU] MAAS 2.6.0beta1

2019-04-17 Thread Andres Rodriguez
** 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 the following features:
  
-  - HTTP boot for amd64/arm64
-  - ESXi storage support
-  - ESXi vCenter registration
-  - DB performance improvements
-  - UI performance improvements
-  - TFTP performance improvements
-  - Performance profiling and tracking.
+  - HTTP boot for amd64/arm64
+  - ESXi storage support
+  - ESXi vCenter registration
+  - DB performance improvements
+  - UI performance improvements
+  - TFTP performance improvements
+  - Performance profiling and tracking.
  
  Upcoming releases are targeted to only include bug fixes.
  
  Testing
  ==
  
  Testing performed:
  
-  - CI testing
-  - Manual UI testing
-  - Fresh install testing
-  - Upgrade testing
+  - CI testing
+  - Manual UI testing
+  - Fresh install testing
+  - Upgrade testing
  
  Releases
  ===
- We are targeting a beta or RC as a 0-day SRU.
+ Current beta release contains all features targeted for 2.6. Currently sits 
in beta due to continues UI work.

** Description changed:

  Ubuntu Disco currently has MAAS 2.5.0. This is a Standing Feature Freeze
- Exception request for MAAS 2.6 release.
+ 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
   - ESXi storage support
   - ESXi vCenter registration
   - DB performance improvements
   - UI performance improvements
   - TFTP performance improvements
   - Performance profiling and tracking.
  
  Upcoming releases are targeted to only include bug fixes.
  
  Testing
  ==
  
  Testing performed:
  
   - CI testing
   - Manual UI testing
   - Fresh install testing
   - Upgrade testing
  
  Releases
  ===
  Current beta release contains all features targeted for 2.6. Currently sits 
in beta due to continues UI work.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1824434

Title:
  [0-day SRU] MAAS 2.6.0beta1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1824434/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1772588] Re: Remove obsolete X11 drivers from the archive

2019-04-17 Thread Timo Aaltonen
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.
https://bugs.launchpad.net/bugs/1772588

Title:
  Remove obsolete X11 drivers from the archive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xf86-input-mtrack/+bug/1772588/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1812582] Re: Unable to install hplip 3.18.12 on linux mint 19.1

2019-04-17 Thread FN via ubuntu-bugs
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.
Apr 17 20:33:22 xps13 systemd[1]: Started CUPS Scheduler.
Apr 17 22:48:38 xps13 hpcups[24442]: prnt/hpcups/HPCupsFilter.cpp 647: DEBUG: 
imageProcessorStartPage failed result = 2
Apr 17 22:49:23 xps13 hpcups[24471]: prnt/hpcups/HPCupsFilter.cpp 647: DEBUG: 
imageProcessorStartPage failed result = 2
Apr 17 22:51:08 xps13 hpcups[24526]: prnt/hpcups/HPCupsFilter.cpp 647: DEBUG: 
imageProcessorStartPage failed result = 2

When I print a test page


** Attachment added: "hp-check.log"
   
https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1812582/+attachment/5256606/+files/hp-check.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1812582

Title:
  Unable to install hplip 3.18.12 on linux mint 19.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/hplip/+bug/1812582/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1824154] Re: bionic/stein: python-ceph missing dependencies

2019-04-17 Thread David Ames
** 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.
https://bugs.launchpad.net/bugs/1824154

Title:
  bionic/stein: python-ceph missing dependencies

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-ceph-fs/+bug/1824154/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1825250] Re: ethmonitor does not list interfaces without assigned IP address

2019-04-17 Thread Heitor Alves de Siqueira
** 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 notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825250

Title:
  ethmonitor does not list interfaces without assigned IP address

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resource-agents/+bug/1825250/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1825054] Re: My JavaFx project stopped compiling

2019-04-17 Thread Kristof Szilagyi
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 member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1825054

Title:
  My JavaFx project stopped compiling

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openjfx/+bug/1825054/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1812925] Re: No OSDs has been initialized in random unit with "No block devices detected using current configuration"

2019-04-17 Thread David Ames
** 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 devices
  detected using current configuration"

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-ceph-osd/+bug/1812925/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1821491] Re: DNS lookup fails for local hosts

2019-04-17 Thread Steve Roberts
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 
in my glasshouse)
and confusingly to me they give different results, ping often works when 
nslookup fails (as is currently the case on the desktop)

> you don't need the router configured to resolve the "single label" (without 
> .phs) hostname ...
I have managed to telnet into the router:
# cat /etc/resolv.conf
domain phs
nameserver 208.67.222.222
nameserver 212.159.6.10

so clearly the domain is set, but if I remove the single label entry
from the router even ping fails from the desktop (but still works on the
laptop) and it seems that when providing an address via dhcp (e.g.
to the laptop) the router puts both phs09 and phs09.phs in /etc/hosts,
so I guess the router needs it...

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821491

Title:
  DNS lookup fails for local hosts

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1821491/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1822254] Re: Can't drag and drop files to Desktop on Disco 19.04 beta

2019-04-17 Thread Launchpad Bug Tracker
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.
https://bugs.launchpad.net/bugs/1822254

Title:
  Can't drag and drop files to Desktop on Disco 19.04 beta

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1822254/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1825219] Re: Acer Aspire Travelmate 535 after opening lid black screen and freeze occurs

2019-04-17 Thread Launchpad Bug Tracker
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:
  Acer Aspire Travelmate 535 after opening lid black screen and freeze
  occurs

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825219/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1825112] Re: Screen reader isn't actived on gdm if installed with a11y enabled

2019-04-17 Thread Brian Murray
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 bug go to:
https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1825112/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

  1   2   3   4   5   6   7   >