[Bug 1280300] Re: Desktop contents displayed on resume, before lock screen is shown

2019-09-24 Thread Chris Guiver
Lubuntu 19.10 QA-test (live) on lenovo thinkpad sl510 (c2d-t6570, 2gb
ram, i915)

suspended system, waited, it resumed (image was visible briefly before
xscreensaver covered screens; screensaver woke on touch of key - i'll
record as https://bugs.launchpad.net/ubuntu/+source/gnome-
screensaver/+bug/1280300

Issue is exactly as described, except the xscreensaver image appeared in
well under a second after laptop awoke.  I had external vga in use too,
and it wasn't hidden either briefly

** Tags added: eoan

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

Title:
  Desktop contents displayed on resume, before lock screen is shown

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

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

[Bug 1845285] Re: SRU request: Include xf86-input-wacom - 1:0.36.1-0ubuntu2 in Ubuntu 18.04

2019-09-24 Thread Cyrus Lien
** Changed in: oem-priority/bionic
   Status: New => Confirmed

** Changed in: oem-priority/bionic
   Importance: Undecided => High

** Changed in: oem-priority/bionic
 Assignee: (unassigned) => Cyrus Lien (cyruslien)

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

Title:
  SRU request: Include xf86-input-wacom - 1:0.36.1-0ubuntu2 in Ubuntu
  18.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1845285/+subscriptions

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

[Bug 1819207] Proposed package upload rejected

2019-09-24 Thread Chris Halse Rogers
An upload of ubuntu-drivers-common to bionic-proposed has been rejected
from the upload queue for the following reason: "Includes a bunch of
(hopefully!) non-functional whitespace changes. Changelog links to LP:#
1819207, marked as Won't Fix, and doesn't match the description in the
changelog.".

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

Title:
  [FFe] Add Modaliases to open-vm-tools-desktop to allow automatic
  installation by ubuntu-drivers

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

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

[Bug 1843796] Proposed package upload rejected

2019-09-24 Thread Chris Halse Rogers
An upload of ubuntu-drivers-common to bionic-proposed has been rejected
from the upload queue for the following reason: "Includes a bunch of
(hopefully!) non-functional whitespace changes. Changelog links to LP:#
1819207, marked as Won't Fix, and doesn't match the description in the
changelog.".

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

Title:
  ubuntu-drivers install --gpgpu should use a DKMS fallback when no
  linux-modules-nvidia package is available

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

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

[Bug 1842382] Re: /proc/self/maps paths missing on live session (was vlc won't start; eoan 19.10 & bionic 18.04 ubuntu/lubuntu/kubuntu/xubuntu/ubuntu-mate dailies)

2019-09-24 Thread Chris Guiver
please ignore my #47 - launchpad had a :( (crash) & my 'back' caused it
to return to a prior page & I didn't notice in time...  Sorry

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

Title:
  /proc/self/maps paths missing on live session (was vlc won't start;
  eoan 19.10 & bionic 18.04 ubuntu/lubuntu/kubuntu/xubuntu/ubuntu-mate
  dailies)

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

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

[Bug 1842382] Re: /proc/self/maps paths missing on live session (was vlc won't start; eoan 19.10 & bionic 18.04 ubuntu/lubuntu/kubuntu/xubuntu/ubuntu-mate dailies)

2019-09-24 Thread Chris Guiver
Lubuntu 19.10 QA-test (live) on lenovo thinkpad sl510 (c2d-t6570, 2gb
ram, i915)

suspended system, waited, it resumed (image was visible briefly before
xscreensaver covered screens; screensaver woke on touch of key - i'll
record as https://bugs.launchpad.net/ubuntu/+source/gnome-
screensaver/+bug/1280300

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

Title:
  /proc/self/maps paths missing on live session (was vlc won't start;
  eoan 19.10 & bionic 18.04 ubuntu/lubuntu/kubuntu/xubuntu/ubuntu-mate
  dailies)

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

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

[Bug 1845285] Re: SRU request: Include xf86-input-wacom - 1:0.36.1-0ubuntu2 in Ubuntu 18.04

2019-09-24 Thread Cyrus Lien
** Also affects: oem-priority/bionic
   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/1845285

Title:
  SRU request: Include xf86-input-wacom - 1:0.36.1-0ubuntu2 in Ubuntu
  18.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1845285/+subscriptions

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

[Bug 1845285] Re: SRU request: Include xf86-input-wacom - 1:0.36.1-0ubuntu2 in Ubuntu 18.04

2019-09-24 Thread Cyrus Lien
Please apply the patch comes from 1:0.36.1-0ubuntu2.

** Patch added: "skip-touchscreens.diff"
   
https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1845285/+attachment/5291036/+files/skip-touchscreens.diff

** Also affects: oem-priority
   Importance: Undecided
   Status: New

** Changed in: oem-priority
 Assignee: (unassigned) => Cyrus Lien (cyruslien)

** Changed in: oem-priority
   Status: New => Confirmed

** Changed in: oem-priority
   Importance: Undecided => High

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

Title:
  SRU request: Include xf86-input-wacom - 1:0.36.1-0ubuntu2 in Ubuntu
  18.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1845285/+subscriptions

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

[Bug 1845285] [NEW] SRU request: Include xf86-input-wacom - 1:0.36.1-0ubuntu2 in Ubuntu 18.04

2019-09-24 Thread Cyrus Lien
Public bug reported:

SRU Request:

[Impact]
xf86-input-wacom version 1:0.36.1-0ubuntu1 shipped 
/usr/share/X11/xorg.conf.d/70-wacom.conf has this:

Section "InputClass"
Identifier "Wacom touchscreen class"
MatchProduct "Wacom|WACOM|PTK-540WL|ISD-V4"
MatchDevicePath "/dev/input/event*"
MatchIsTouchscreen "true"
Driver "wacom"
EndSection

Which config let Wacom touchscreen using wacom input driver and makes
the touchscreen act incorrectly.

https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1774242
(comment #14)

[Test Case]
1) Enable the bionic-proposed repository, and install the xf86-input-wacom 
package

2) Restart and see if the Wacom touchscreen works correctly. Also check
/var/log/Xorg.0.log to see if Wacom touchscreen using libinput driver
instead wacom driver.

[Regression Potential]
Low, the package  xf86-input-wacom - 1:0.36.1-0ubuntu2  is already in Eoan and 
Disco.

** Affects: xf86-input-wacom (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: oem-priority

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

Title:
  SRU request: Include xf86-input-wacom - 1:0.36.1-0ubuntu2 in Ubuntu
  18.04

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

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

[Bug 1845285] [NEW] SRU request: Include xf86-input-wacom - 1:0.36.1-0ubuntu2 in Ubuntu 18.04

2019-09-24 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

SRU Request:

[Impact]
xf86-input-wacom version 1:0.36.1-0ubuntu1 shipped 
/usr/share/X11/xorg.conf.d/70-wacom.conf has this:

Section "InputClass"
Identifier "Wacom touchscreen class"
MatchProduct "Wacom|WACOM|PTK-540WL|ISD-V4"
MatchDevicePath "/dev/input/event*"
MatchIsTouchscreen "true"
Driver "wacom"
EndSection

Which config let Wacom touchscreen using wacom input driver and makes
the touchscreen act incorrectly.

https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/1774242
(comment #14)

[Test Case]
1) Enable the bionic-proposed repository, and install the xf86-input-wacom 
package

2) Restart and see if the Wacom touchscreen works correctly. Also check
/var/log/Xorg.0.log to see if Wacom touchscreen using libinput driver
instead wacom driver.

[Regression Potential]
Low, the package  xf86-input-wacom - 1:0.36.1-0ubuntu2  is already in Eoan and 
Disco.

** Affects: ubuntu
 Importance: Undecided
 Status: New


** Tags: oem-priority
-- 
SRU request: Include xf86-input-wacom - 1:0.36.1-0ubuntu2 in Ubuntu 18.04 
https://bugs.launchpad.net/bugs/1845285
You received this bug notification because you are a member of Ubuntu Bugs, 
which is subscribed to Ubuntu.

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

[Bug 1842532] Re: Touchpad stops working after resuming from s2idle

2019-09-24 Thread You-Sheng Yang
** Bug watch added: Linux Kernel Bug Tracker #204991
   https://bugzilla.kernel.org/show_bug.cgi?id=204991

** Also affects: linux via
   https://bugzilla.kernel.org/show_bug.cgi?id=204991
   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/1842532

Title:
  Touchpad stops working after resuming from s2idle

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1842532/+subscriptions

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

Re: [Bug 1845157] Re: runner/autopkgtest fails to setup env with binary packages moved to another packge, and different source/binary versions

2019-09-24 Thread Matthias Klose
On 25.09.19 02:39, Dan Streetman wrote:
> Since I assume that even if we *do* start building for mips arch, you
> don't want the binutils source package to build for it (you would want
> the binutils-mipsen package to build for it, right?),

No. src:binutils builds all the native packages, plus most of the cross 
packages. src:binutils-mipsen only builds some cross targets, some of them 
already built before. If src:binutils-mipsen is staying, then this should be 
the 
final packaging layout.

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

Title:
  runner/autopkgtest fails to setup env with binary packages moved to
  another packge, and different source/binary versions

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

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

[Bug 1766945] Re: (EFI on top of legacy install) choosing "replace" or "resize" options in partitioning may lead to an install failure

2019-09-24 Thread Rushikesh Deore
i getting problem for installing ubntu

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

Title:
  (EFI on top of legacy install) choosing "replace" or "resize" options
  in partitioning may lead to an install failure

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

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

[Bug 1819907] Re: 19.04 installer hangs on installation complete dialog

2019-09-24 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

** Changed in: linux (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  19.04 installer hangs on installation complete dialog

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

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

[Bug 1835957] Re: cupsd gobbles up resources

2019-09-24 Thread Launchpad Bug Tracker
[Expired for cups (Ubuntu) because there has been no activity for 60
days.]

** Changed in: cups (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  cupsd gobbles up resources

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

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

[Bug 1714387] Re: browser crashes

2019-09-24 Thread Launchpad Bug Tracker
[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]

** Changed in: firefox (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  browser crashes

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

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

[Bug 1838018] Re: Unable to locate package linux-lowlatency-lts-trusty for Precise ESM

2019-09-24 Thread Launchpad Bug Tracker
[Expired for linux (Ubuntu) because there has been no activity for 60
days.]

** Changed in: linux (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Unable to locate package linux-lowlatency-lts-trusty for Precise ESM

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

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

[Bug 1675202] Re: Error Code: F7363-1260 trying to use Netflix on Firefox

2019-09-24 Thread Launchpad Bug Tracker
[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]

** Changed in: firefox (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Error Code: F7363-1260 trying to use Netflix on Firefox

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

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

[Bug 1833065] Re: Intel WiFi (CNVi) module has no function on Comet Lake [8086:02f0]

2019-09-24 Thread You-Sheng Yang
For Bionic/Cosmic/Disco generic kernel users, this bug depends on
previous work in bug 1809224, which is too many/risky to backport to a
already released generic kernel. Please use oem-osp1 kernel instead.

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Bionic)
   Status: New => Won't Fix

** Changed in: linux (Ubuntu Cosmic)
   Status: New => Won't Fix

** Changed in: linux (Ubuntu Disco)
   Status: New => Won't Fix

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

Title:
  Intel WiFi (CNVi) module has no function on Comet Lake [8086:02f0]

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1833065/+subscriptions

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

[Bug 1835879] Re: Intel Wireless-AC 9462/9560 not supported on ICL

2019-09-24 Thread You-Sheng Yang
For Bionic/Cosmic/Disco generic kernel users, this bug depends on
previous work in bug 1809224, which is too many/risky to backport to a
already released generic kernel. Please use oem-osp1 kernel instead.

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Bionic)
   Status: New => Won't Fix

** Changed in: linux (Ubuntu Cosmic)
   Status: New => Won't Fix

** Changed in: linux (Ubuntu Disco)
   Status: New => Won't Fix

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

Title:
  Intel Wireless-AC 9462/9560 not supported on ICL

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1835879/+subscriptions

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

[Bug 1809224] Re: To support Intel Wireless-AX 22000 series

2019-09-24 Thread You-Sheng Yang
** Also affects: linux (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Also affects: linux-oem-osp1 (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Eoan)
   Importance: Undecided
   Status: In Progress

** Also affects: linux-oem-osp1 (Ubuntu Eoan)
   Importance: Undecided
   Status: Invalid

** Changed in: linux (Ubuntu Disco)
   Status: New => Won't Fix

** Changed in: linux (Ubuntu Eoan)
   Status: In Progress => Won't Fix

** Changed in: linux-oem-osp1 (Ubuntu Disco)
   Status: New => Fix Released

** Changed in: linux (Ubuntu Eoan)
   Status: Won't Fix => Invalid

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

Title:
  To support Intel Wireless-AX 22000 series

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

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

[Bug 1844787] Re: Killer Wi-Fi 6 AX1650 device not supported by kernel

2019-09-24 Thread You-Sheng Yang
Hi makitso,

We had some more discussion on backporting current iwlwifi support work.
Basically all the related work, bug 1809224/bug 1833065/bug 1834415/bug
1835879/bug 1845138, has been(or will be) landed to oem-osp1 kernel, and
bug 1809224 alone has around 150+ patches backported. While oem-osp1
kernel[1] is actually based on Disco generic kernel and it's also
available in Disco, we should recommend users to use oem-osp1 kernel in
this case instead of doing duplicated work. So, I'm closing this issue
and other similar ones as WONTFIX. Thank you.

For Eoan users, there should not be any problems as Eoan generic kernel
is following kernel v5.3.

[1]: https://packages.ubuntu.com/disco/linux-image-oem-osp1

** Changed in: linux (Ubuntu)
   Status: Confirmed => Won't Fix

** Summary changed:

- Killer Wi-Fi 6 AX1650 device not supported by kernel
+ Killer Wi-Fi 6 AX1650 device not supported by Disco generic kernel

** Also affects: linux (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu Disco)
   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/1844787

Title:
  Killer Wi-Fi 6 AX1650 device not supported by Disco generic kernel

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

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

[Bug 1801629] Re: direct dependencies of ubiquity should not be autoremovable

2019-09-24 Thread Launchpad Bug Tracker
This bug was fixed in the package ubuntu-mate-meta - 1.253

---
ubuntu-mate-meta (1.253) eoan; urgency=medium

  * Refreshed dependencies
  * Added cryptsetup to core, desktop (LP: #11841672, #1801629)
  * Added libnotify-bin to core-recommends, desktop-recommends

 -- Martin Wimpress   Wed, 25 Sep 2019 00:47:17
+0100

** Changed in: ubuntu-mate-meta (Ubuntu Eoan)
   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/1801629

Title:
  direct dependencies of ubiquity should not be autoremovable

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1801629/+subscriptions

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

[Bug 1845023] Re: Updated screenshots for Ubuntu slideshow in 19.10

2019-09-24 Thread Launchpad Bug Tracker
This bug was fixed in the package ubiquity-slideshow-ubuntu - 148

---
ubiquity-slideshow-ubuntu (148) eoan; urgency=medium

  [ Will Cooke ]
  * Adds new screenshots for the slideshow update for 19.10. No strings
changes. UIFe has been filed and approved. Fixes LP: #1845023

  [ handsome_feng ]
  * ubuntukylin: Update welcome and wps pages and the related po files

 -- Sebastien Bacher   Tue, 24 Sep 2019 16:18:05
+0200

** Changed in: ubiquity-slideshow-ubuntu (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/1845023

Title:
  Updated screenshots for Ubuntu slideshow in 19.10

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

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

[Bug 1790134] Re: “______ will be downloaded” icon is too large

2019-09-24 Thread Launchpad Bug Tracker
This bug was fixed in the package update-manager - 1:19.04.8

---
update-manager (1:19.04.8) eoan; urgency=medium

  * data/gtkbuilder/UpdateManager.ui: enforce icon size for download size icon
so it's consistent with the other status icons. (LP: #1790134)

 -- Mathieu Trudel-Lapierre   Tue, 24 Sep 2019
17:44:21 -0400

** Changed in: update-manager (Ubuntu Eoan)
   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/1790134

Title:
  “__ will be downloaded” icon is too large

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

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

[Bug 1844320] Re: efibootmgr -v UiAppCould not parse device path

2019-09-24 Thread Launchpad Bug Tracker
This bug was fixed in the package efivar - 37-2ubuntu2

---
efivar (37-2ubuntu2) eoan; urgency=medium

  * Backport more fixes from upstream that fix efibootmgr -v. (LP:
#1844320)

 -- Michael Hudson-Doyle   Wed, 25 Sep 2019
10:50:57 +1200

** Changed in: efivar (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/1844320

Title:
  efibootmgr -v UiAppCould not parse device path

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

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

[Bug 1797717] Re: fstrim -av tries to trim read only mounted ntfs-3g and fails

2019-09-24 Thread Ivan Larionov
** Tags added: disco

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

Title:
  fstrim -av tries to trim read only mounted ntfs-3g and fails

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

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

[Bug 1845190] Re: binutils nm wrong output format breaks i386 nm work

2019-09-24 Thread Bug Watch Updater
** Changed in: binutils
   Status: In Progress => 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/1845190

Title:
  binutils nm wrong output format breaks i386 nm work

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

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

[Bug 1845190]

2019-09-24 Thread Alan Modra
Fixed.

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

Title:
  binutils nm wrong output format breaks i386 nm work

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

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

[Bug 935681] Re: "Restart services during package upgrades without asking?" fails to honor --yes for apt-get

2019-09-24 Thread Taihsiang Ho
This issues show up again on Bionic now.

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

Title:
  "Restart services during package upgrades without asking?" fails to
  honor --yes for apt-get

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

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

[Bug 1840239] Re: tsc marked unstable after entered PC10 on Intel CoffeeLake

2019-09-24 Thread You-Sheng Yang
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=0f0b7e1cc7abf8e1a8b301f2868379d611d05ae2
introduced another parameter "tsc=nowatchdog", which should have the
same effect of the current work-around "tsc=reliable", but that's not
meant to be and will not be the ultimate solution for this issue.

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

Title:
  tsc marked unstable after entered PC10 on Intel CoffeeLake

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1840239/+subscriptions

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

[Bug 1845008] Re: The autopkgtests are failing with the newer gobject-introspection

2019-09-24 Thread Jeremy Bicha
You could try https://github.com/ruby-gnome/ruby-gnome/pull/1295

** Changed in: ruby-gnome (Ubuntu)
   Status: New => Triaged

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

Title:
  The autopkgtests are failing with the newer gobject-introspection

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

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

[Bug 1845190] Re: binutils nm wrong output format breaks i386 nm work

2019-09-24 Thread Bug Watch Updater
** Changed in: binutils
   Status: New => 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/1845190

Title:
  binutils nm wrong output format breaks i386 nm work

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

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

[Bug 913444]

2019-09-24 Thread Olivier Dierick
Created attachment 65286
v2 Patch 2/2 shell32: Create symbolic links rather than directories for 
specific user shell folders

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

Title:
  Every wine update re-enables desktop integration links

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

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

[Bug 913444]

2019-09-24 Thread Forest
Olivier, thank you. Getting rid of the remove() call looks like it would
fix the annoyance of having My Documents relocated every time I upgrade
wine or dxvk.

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

Title:
  Every wine update re-enables desktop integration links

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

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

[Bug 913444]

2019-09-24 Thread Olivier Dierick
Created attachment 65285
v2 Patch 1/2 shell32: Move and split _SHCreateSymbolicLinks()

Hello,

Here is a new patchset that I think is cleaner.
I changed my mind and don't touch anything but the issue.
I think it will help getting the patchset approved sooner.
Other features deserve their own enhancement bugs anyway.

Patch 1/2:
- Splits the _SHCreateSymbolicLinks() into folder type-specific functions, 
keeping the old logic intact. This way the different folders can be handled 
separately.
- It also fixes some trailing whitespace in the moved code but that's 
negligible.

Patch 2/2:
- Adds a helper function that creates a single symbolic link at a time, for the 
folders we are interested in.
- Calls the helper function where the old code did only create a directory.
- Disables the removal of existing symlinks/directories, in the symlink 
creation functions.
- Also says to not create the folder when looking up for its path for the 
symlink, to avoid an infinite loop.

Note that the winecfg code handles the folder symlink/directory
switching itself, removing the symlink/directory as appropriate. It even
makes a backup of the directory when switching to a symlink and restores
it when switching back. The removal of the remove() calls doesn't affect
the ability to manage the shell folders through the winecfg UI.

Please, test the patchset thoroughly on your system and give feedback if it 
breaks anything.
Meanwhile, I'll request for comments on the developer mailing list.

Regards.

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

Title:
  Every wine update re-enables desktop integration links

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

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

[Bug 1845190]

2019-09-24 Thread Cvs-commit
The master branch has been updated by Alan Modra
:

https://sourceware.org/git/gitweb.cgi?p=binutils-
gdb.git;h=352f6bc3e5b23e76d8e6f56fb7db4e57d8f5d5bd

commit 352f6bc3e5b23e76d8e6f56fb7db4e57d8f5d5bd
Author: Alan Modra 
Date:   Tue Sep 24 22:47:13 2019 +0930

PR25031, nm reports wrong address on 32bit

Using saved_format breaks when nm is presented with multiple object
files, some 32-bit and some 64-bit.

PR 25031
* nm.c (print_format_string): New.
(get_print_format): Delete saved_format.  Move earlier.
(set_print_width): Call get_print_format.
(print_value): Use print_format_string.

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

Title:
  binutils nm wrong output format breaks i386 nm work

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

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

[Bug 1845190]

2019-09-24 Thread Cvs-commit
The binutils-2_33-branch branch has been updated by Alan Modra
:

https://sourceware.org/git/gitweb.cgi?p=binutils-
gdb.git;h=895b6d98785ba89819820aa5f4abed17fbb28c37

commit 895b6d98785ba89819820aa5f4abed17fbb28c37
Author: Alan Modra 
Date:   Tue Sep 24 22:47:13 2019 +0930

PR25031, nm reports wrong address on 32bit

Using saved_format breaks when nm is presented with multiple object
files, some 32-bit and some 64-bit.

PR 25031
* nm.c (print_format_string): New.
(get_print_format): Delete saved_format.  Move earlier.
(set_print_width): Call get_print_format.
(print_value): Use print_format_string.

(cherry picked from commit 352f6bc3e5b23e76d8e6f56fb7db4e57d8f5d5bd)

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

Title:
  binutils nm wrong output format breaks i386 nm work

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

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

[Bug 1843767] Re: xe-guest-utilities ftbfs in eoan

2019-09-24 Thread Launchpad Bug Tracker
This bug was fixed in the package xe-guest-utilities - 7.10.0-0ubuntu2

---
xe-guest-utilities (7.10.0-0ubuntu2) eoan; urgency=medium

  * Set GOCACHE to a safely writeable directory, fixing ftbfs with Go 1.12+.
(LP: #1843767).
  * Fix typos in Vcs-* fields in d/control.

 -- Michael Hudson-Doyle   Wed, 25 Sep 2019
09:36:13 +1200

** Changed in: xe-guest-utilities (Ubuntu Eoan)
   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/1843767

Title:
  xe-guest-utilities ftbfs in eoan

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xe-guest-utilities/+bug/1843767/+subscriptions

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

[Bug 61002]

2019-09-24 Thread Bencriss64
(In reply to Joseph from comment #0)
> User-Agent:   Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
> rv:1.8.1b1) Gecko/20060803 BonEcho/2.0b1
> Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;
> rv:1.8.1b1) Gecko/20060803 BonEcho/2.0b1
> 
> Bug 337654 removed UI elements from the Quick Find bar under the assumption
> that Quick Find is an accessibility feature with different needs than Find. 
> While this may be true for users who choose to invoke it using / or '
> instead of Ctrl+F, one class of users was overlooked: those who use the
> typeaheadfind.autostart pref as a way to invoke Find behavior without any
> extra keystroke.
> 
> For these users, an appropriate behavior change would be to make the
> autostart pref bring up the Find bar rather than QuickFind bar, leaving
> QuickFind as a separate feature focused on accessibility needs.  Since
> autostart FAYT always searches text rather than just links as in QuickFind
> invoked with the apostrophe, there is little search functionality difference
> between auto FAYT and the Find bar except the now missing UI elements. 
> Without this change, the visual differentiation (from bug 337654) has
> reduced user confusion but also acts as a functional regression, since there
> is now no way to truly start FINDing when you begin typing.
> 
> Discussion of the loss of autostart FAYT functionality due to the QuickFind
> changes can be found in these three MozillaZine threads:
> https://pornogratisaqu.com/es/category/242/Facial/popular/1/
> http://forums.mozillazine.org/viewtopic.php?t=437010
> http://forums.mozillazine.org/viewtopic.php?t=436989
> http://forums.mozillazine.org/viewtopic.php?t=446362
> 
> Reproducible: Always

thx nice

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

Title:
  Mozilla Firefox: No buttons at Quick Find

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

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

[Bug 1843323] Re: Kernel 4.15.0-59 (and onwards) breaks scroll wheel of USB mouse (A4Tech X5-50D)

2019-09-24 Thread Christian Schrötter
> $ apt-cache policy linux-image-4.15.0-65-generic
> linux-image-4.15.0-65-generic:
>   Installed: 4.15.0-65.74
>   Candidate: 4.15.0-65.74
>   Version table:
>  *** 4.15.0-65.74 500
> 500 http://at.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 
> Packages
> 100 /var/lib/dpkg/status

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

Title:
  Kernel 4.15.0-59 (and onwards) breaks scroll wheel of USB mouse
  (A4Tech X5-50D)

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

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

[Bug 1843323] Re: Kernel 4.15.0-59 (and onwards) breaks scroll wheel of USB mouse (A4Tech X5-50D)

2019-09-24 Thread Christian Schrötter
@vladisslav: Your version is too old, that's not from bionic-proposed!
;-)

> $ apt-cache policy linux-image-generic
linux-image-generic:
>   Installed: 4.15.0.65.67
>   Candidate: 4.15.0.65.67
>   Version table:
>  *** 4.15.0.65.67 500
> 500 http://at.archive.ubuntu.com/ubuntu bionic-proposed/main amd64 
> Packages
> 100 /var/lib/dpkg/status
>  4.15.0.64.66 500
> 500 http://at.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
> Packages
> 500 http://at.archive.ubuntu.com/ubuntu bionic-security/main amd64 
> Packages
>  4.15.0.20.23 500
> 500 http://at.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

I'm running 4.15.0.65.67 (uname = 4.15.0-65-generic) and it's working
fine.

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

Title:
  Kernel 4.15.0-59 (and onwards) breaks scroll wheel of USB mouse
  (A4Tech X5-50D)

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

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

[Bug 1845157] Re: runner/autopkgtest fails to setup env with binary packages moved to another packge, and different source/binary versions

2019-09-24 Thread Bug Watch Updater
** Changed in: autopkgtest (Debian)
   Status: Unknown => New

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

Title:
  runner/autopkgtest fails to setup env with binary packages moved to
  another packge, and different source/binary versions

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

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

[Bug 1841381] Re: Aegisub crashes immediately after opening the context menu

2019-09-24 Thread Bug Watch Updater
** Changed in: aegisub (Debian)
   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/1841381

Title:
  Aegisub crashes immediately after opening the context menu

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

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

[Bug 1845190] Re: binutils nm wrong output format breaks i386 nm work

2019-09-24 Thread MarcH
> on amd64 it works correctly:
>
> nm elfmix1.not_a 
> return42_or_3_long_name.o:
>  T return42_or_3
> return42_or_3_long_name.obj:
>  T return42_or_3

No, on amd64 the bug is the same as on i386. The correct output on both
i386 and amd64 must be:

return42_or_3_long_name.o:
 T return42_or_3
return42_or_3_long_name.obj:
 T return42_or_3

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

Title:
  binutils nm wrong output format breaks i386 nm work

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

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

[Bug 1845000] Re: evince assert failure: double free or corruption (!prev)

2019-09-24 Thread Bug Watch Updater
** Changed in: evince
   Status: Unknown => New

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

Title:
  evince assert failure: double free or corruption (!prev)

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

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

[Bug 1844853] Re: IBus no longer works in Qt applications after upgrade

2019-09-24 Thread Bug Watch Updater
** Changed in: ibus
   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/1844853

Title:
  IBus no longer works in Qt applications after upgrade

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

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

[Bug 1844385] Re: bionic/linux-bluefield: 5.0.0-1001.10 -proposed tracker

2019-09-24 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: 1844403
  packages:
main: linux-bluefield
meta: linux-meta-bluefield
  phase: Ready for Promote to Proposed
  phase-changed: Tuesday, 24. September 2019 12:50 UTC
  reason:
-   promote-to-proposed: Pending -- ready for review
+   promote-to-proposed: Stalled -- ready for review
  replaces: bug 1842811
  variant: debs

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

Title:
  bionic/linux-bluefield: 5.0.0-1001.10 -proposed tracker

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

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

[Bug 1845037] Re: autopkgtest package "lxd" test has started failing

2019-09-24 Thread Dan Streetman
** Description changed:

  [impact]
  
  the failure is seen in (at least) the "lxd" autopkgtest from the autopkgtest 
package itself, e.g.:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-disco/disco/amd64/a/autopkgtest/20190923_160817_66dbe@/log.gz
  
  [test case]
  
  run the autopkgtests for the package 'autopkgtest', or check 
autopkgtest.ubuntu.com, e.g.:
  http://autopkgtest.ubuntu.com/packages/a/autopkgtest/disco/amd64
  http://autopkgtest.ubuntu.com/packages/a/autopkgtest/disco/i386
  http://autopkgtest.ubuntu.com/packages/a/autopkgtest/eoan/amd64
  http://autopkgtest.ubuntu.com/packages/a/autopkgtest/eoan/i386
  
  note that this is failing only for disco and eoan, and note that the 'lxd' 
test is skipped for non-intel archs.  this does not appear to be failing on 
bionic:
  http://autopkgtest.ubuntu.com/packages/a/autopkgtest/bionic/amd64
  
  [regression potential]
  
- TBD
+ this only redirects stdin from /dev/null, for the call to 'lxc launch'
+ inside autopkgtest-build-lxd; so the regression potential should be low.
+ Any regressions would almost certainly involve a failure during the call
+ to autopkgtest-build-lxd, during the creation of the lxd container.
  
  [other info]
  
  this is reproducable with the current packages from disco-updates using
- a local qemu vm for testing; it seems that some change in the lxd snap
- recently has caused this regression.
+ a local qemu vm for testing.
+ 
+ I put the 'importance' of this as low because this bug will only be
+ reproduced when calling autopkgtest-build-lxd from inside a here
+ document passed to a shell, or otherwise called with input queued on
+ stdin, which seems like an unusual way to call autopkgest-build-lxd.

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

Title:
  autopkgtest package "lxd" test has started failing

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

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

[Bug 1101636] Re: LICENSE.aic94xx-seq in linux-firmware - is this firmware distributable?

2019-09-24 Thread yamato
I found the Adaptec license in "copyright" file.
I suppose this issue occured again, right?

http://changelogs.ubuntu.com/changelogs/pool/main/l/linux-firmware
/linux-firmware_1.173.9/copyright

I have reported this.
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1844471

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

Title:
  LICENSE.aic94xx-seq in linux-firmware - is this firmware
  distributable?

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

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

[Bug 1845157] Re: runner/autopkgtest fails to setup env with binary packages moved to another packge, and different source/binary versions

2019-09-24 Thread Dan Streetman
This looks similar to bug 1831492.  @vorlon was insistent that was a bug
in autopkgtest, but personally it seemed like a real bug to me, for the
reasons i explained in that bug.

However for this bug, I think it actually is a bug in autopkgtest,
because the resulting binaries are in fact separated by arch, even
though autopkgtest doesn't realize that.


IIUC, autopkgtest is looking at the package list for binutils, and it sees the 
same packages provided by 'binutils' as well as 'binutils-mipsen'; for example:

in debian/control for binutils in eoan-proposed there is:
Package: binutils-mipsel-linux-gnu
Priority: optional
Architecture: mipsel

in debian/control for binutils-mipsen in eoan-proposed there is:
Package: binutils-mipsel-linux-gnu
Priority: optional
Architecture: amd64 i386 x32


autopkgtest seems not currently smart enough to notice that those source 
packages don't *actually* overlap with those binary packages, because they are 
limited to separate archs.  So autopkgtest thinks that both source packages 
provide the same binary package, which causes this confusing error, because it 
can't find the '4~c4ubuntu1' version of the binutils source package.

Since I assume that even if we *do* start building for mips arch, you
don't want the binutils source package to build for it (you would want
the binutils-mipsen package to build for it, right?), removing the
conflicting binary packages from the binutils package debian/control
would "fix" this autopkgtest error.

Alternately, the autopkgtest should be taught that it needs to parse the
arch fields for the binary package list, to account for situations like
this.

That's all assuming I haven't misunderstood everything, of course.

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

Title:
  runner/autopkgtest fails to setup env with binary packages moved to
  another packge, and different source/binary versions

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

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

[Bug 1842508] Re: motd messaging changes regarding apt updates

2019-09-24 Thread Chad Smith
Testing before and after -proposed upgrade to update-notifier-common v.
0.154.1ubuntu7 with ubuntu-advantage-tools v.19.5+


--- before ---
root@dev-t:~/ubuntu-advantage-client# /usr/lib/update-notifier/apt-check --human
-readable
Extended Security Maintenance (ESM) is not enabled.

3 updates can be installed immediately.
0 of these updates are security updates.

Enable ESM to receive 30 additional security updates.
See 'ua enable esm' or https://ubuntu.com/esm

--- after ---
root@dev-t:~/ubuntu-advantage-client# /usr/lib/update-notifier/apt-check --human
-readable
UA Infrastructure Extended Security Maintenance (ESM) is not enabled.

2 updates can be installed immediately.
0 of these updates are security updates.
To see these additional updates run: apt list --upgradable

Enable UA Infrastructure ESM to receive 30 additional security updates.
See https://ubuntu.com/esm or run: sudo ua status


It's a little busy with calls to action, I'll run this by Josh Powers today to 
see this is  significant enough to warrant any changes on our side.

I'll circle back on this with any feedback.

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

Title:
  motd messaging changes regarding apt updates

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

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

[Bug 1845127] Re: bionic/linux-gcp: 5.0.0-1019.19~18.04.1 -proposed tracker

2019-09-24 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: 1845128
  packages:
lrm: linux-restricted-modules-gcp
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Testing
  phase-changed: Tuesday, 24. September 2019 12:17 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
-   stakeholder-signoff: Pending -- waiting for signoff
+   stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  replaces: bug 1844346
  trackers:
bionic/linux-gcp-edge: bug 1844345
bionic/linux-gcp/gcp-kernel: bug 1845126
  variant: debs

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

Title:
  bionic/linux-gcp: 5.0.0-1019.19~18.04.1 -proposed tracker

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

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

[Bug 1845281] [NEW] /usr/bin/gnome-shell:6:__GI_raise:__GI_abort:g_assertion_message:g_assertion_message_expr:meta_window_get_workspaces

2019-09-24 Thread errors.ubuntu.com bug bridge
Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.34.0-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/85b6b0b07aafeed5ae109ce89a813b77d3721684 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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


** Tags: artful bionic cosmic disco eoan

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

Title:
  /usr/bin/gnome-
  
shell:6:__GI_raise:__GI_abort:g_assertion_message:g_assertion_message_expr:meta_window_get_workspaces

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

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

[Bug 1841672] Re: CryptSetup packages should not be removed by `apt-get autoremove` on system installed with encryption and LVM

2019-09-24 Thread Martin Wimpress
** Changed in: ubuntu-mate-meta (Ubuntu Eoan)
   Status: In Progress => Fix Committed

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

Title:
  CryptSetup packages should not be removed by `apt-get autoremove` on
  system installed with encryption and LVM

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

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

[Bug 1801629] Re: direct dependencies of ubiquity should not be autoremovable

2019-09-24 Thread Martin Wimpress
** Changed in: ubuntu-mate-meta (Ubuntu Eoan)
   Status: In Progress => Fix Committed

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

Title:
  direct dependencies of ubiquity should not be autoremovable

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1801629/+subscriptions

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

[Bug 1832651] Re: jackdbus fails to start: cannot allocate memory

2019-09-24 Thread Brian Murray
I was unable to recreate this on an installation of Eoan, which will
become Ubuntu 19.10, using systemd version 241-7ubuntu1 and jackd2
version 1.9.12~dfsg-2build1 subsequently I'm setting the Eoan task to
Fix Released.

** Changed in: systemd (Ubuntu Eoan)
   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/1832651

Title:
  jackdbus fails to start: cannot allocate memory

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

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

[Bug 1801629] Re: direct dependencies of ubiquity should not be autoremovable

2019-09-24 Thread Martin Wimpress
This issue is still affecting Ubuntu MATE 19.10 beta. See the following
for more detail:

  * https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1841672

** Also affects: xubuntu-meta (Ubuntu Eoan)
   Importance: Undecided
   Status: Invalid

** Also affects: ubiquity (Ubuntu Eoan)
   Importance: High
   Status: Invalid

** Also affects: livecd-rootfs (Ubuntu Eoan)
   Importance: Undecided
   Status: Fix Released

** Also affects: ubuntu-mate-meta (Ubuntu Eoan)
   Importance: Undecided
   Status: Invalid

** Changed in: ubuntu-mate-meta (Ubuntu Eoan)
   Importance: Undecided => Critical

** Changed in: ubuntu-mate-meta (Ubuntu Eoan)
   Status: Invalid => In Progress

** Changed in: ubuntu-mate-meta (Ubuntu Eoan)
 Assignee: (unassigned) => Martin Wimpress (flexiondotorg)

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

Title:
  direct dependencies of ubiquity should not be autoremovable

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1801629/+subscriptions

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

[Bug 1841957] Re: The system installed from Ubuntu-MATE 20190829.1 ISO has GNOME Shell and GDM3 as default

2019-09-24 Thread Martin Wimpress
** Changed in: ubuntu-mate-meta (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/1841957

Title:
  The system installed from Ubuntu-MATE 20190829.1 ISO has GNOME Shell
  and GDM3 as default

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

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

[Bug 1841672] Re: CryptSetup packages should not be removed by `apt-get autoremove` on system installed with encryption and LVM

2019-09-24 Thread Martin Wimpress
** Changed in: ubuntu-mate-meta (Ubuntu Eoan)
   Status: Confirmed => In Progress

** Changed in: ubuntu-mate-meta (Ubuntu Eoan)
 Assignee: (unassigned) => Martin Wimpress (flexiondotorg)

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

Title:
  CryptSetup packages should not be removed by `apt-get autoremove` on
  system installed with encryption and LVM

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

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

[Bug 1845128] Re: disco/linux-gcp: 5.0.0-1019.19 -proposed tracker

2019-09-24 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: 1844362
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Testing
  phase-changed: Tuesday, 24. September 2019 11:25 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
security-signoff: Pending -- waiting for signoff
-   stakeholder-signoff: Pending -- waiting for signoff
+   stakeholder-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-gcp: bug 1845127
bionic/linux-gke-5.0: bug 1845131
  variant: debs

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

Title:
  disco/linux-gcp: 5.0.0-1019.19 -proposed tracker

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

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

[Bug 1842682] Re: regression in test-growpart results in test fail device or resource busy

2019-09-24 Thread Rafael David Tinoco
I have verified code from my own git ubuntu tree, and missed it wasn't
in -proposed yet. I'll provide correct verification from pkgs in
-proposed next. Thanks for fixing it Brian.

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

Title:
  regression in test-growpart results in test fail device or resource
  busy

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

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

[Bug 1797417] Re: Background of system tray icons not drawn properly

2019-09-24 Thread Bug Watch Updater
** Changed in: xfce4-panel
   Status: In Progress => 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/1797417

Title:
  Background of system tray icons not drawn properly

To manage notifications about this bug go to:
https://bugs.launchpad.net/xfce4-panel/+bug/1797417/+subscriptions

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

[Bug 1790134] Re: “______ will be downloaded” icon is too large

2019-09-24 Thread Launchpad Bug Tracker
** Branch linked: lp:update-manager

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

Title:
  “__ will be downloaded” icon is too large

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

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

[Bug 1600622] Re: Screen doesn't lock or go to sleep when certain Chrome tabs are open

2019-09-24 Thread pepster
Still a problem for me (Kubuntu 19.04), even with uBlock installed.

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

Title:
  Screen doesn't lock or go to sleep when certain Chrome tabs are open

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

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

[Bug 1797417]

2019-09-24 Thread Iv-n
Simon, thank you for reviewing and merging.

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

Title:
  Background of system tray icons not drawn properly

To manage notifications about this bug go to:
https://bugs.launchpad.net/xfce4-panel/+bug/1797417/+subscriptions

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

[Bug 1844320] Re: efibootmgr -v UiAppCould not parse device path

2019-09-24 Thread Michael Hudson-Doyle
** Package changed: efibootmgr (Ubuntu) => efivar (Ubuntu)

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

Title:
  efibootmgr -v UiAppCould not parse device path

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

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

[Bug 452073]

2019-09-24 Thread Qa-admin-q
Dear Jérôme,

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open,
confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked
on this bug report. During that time, it's possible that the bug has
been fixed, or the details of the problem have changed. We'd really
appreciate your help in getting confirmation that the bug is still
present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of
LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information 
from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to 
RESOLVED-WORKSFORME and leave a comment that includes the information from Help 
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular 
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a 
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your 
bug pertains to a feature added after 3.3) from 
http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: 
https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

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

Title:
  [Upstream] Shouldn't detect configuration at each invocation

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/452073/+subscriptions

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

[Bug 1577925] Re: Can't locate Mail/SpamAssassin/CompiledRegexps/body_0.pm in @INC (you may need to install the Mail::SpamAssassin::CompiledRegexps::body_0 module)

2019-09-24 Thread Bryce Harrington
I ran into this same error message, but on bionic, when adding some body
rules to my local.cf.  I suspect this may relate to
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854404


** Bug watch added: Debian Bug tracker #854404
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=854404

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

Title:
  Can't locate Mail/SpamAssassin/CompiledRegexps/body_0.pm in @INC (you
  may need to install the Mail::SpamAssassin::CompiledRegexps::body_0
  module)

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

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

[Bug 1772445]

2019-09-24 Thread Qa-admin-q
Dear vaaydayaasra,

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open,
confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked
on this bug report. During that time, it's possible that the bug has
been fixed, or the details of the problem have changed. We'd really
appreciate your help in getting confirmation that the bug is still
present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of
LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information 
from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to 
RESOLVED-WORKSFORME and leave a comment that includes the information from Help 
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular 
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a 
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your 
bug pertains to a feature added after 3.3) from 
http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: 
https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

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

Title:
  Text cannot be rotated in a RTL table in LibreOffice Writer

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1772445/+subscriptions

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

[Bug 1772439]

2019-09-24 Thread Qa-admin-q
Dear vaaydayaasra,

To make sure we're focusing on the bugs that affect our users today,
LibreOffice QA is asking bug reporters and confirmers to retest open,
confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked
on this bug report. During that time, it's possible that the bug has
been fixed, or the details of the problem have changed. We'd really
appreciate your help in getting confirmation that the bug is still
present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of
LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information 
from Help - About LibreOffice.
 
If the bug is NOT present, please set the bug's Status field to 
RESOLVED-WORKSFORME and leave a comment that includes the information from Help 
- About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular 
meaning that is not 
appropriate in this case)


If you want to do more to help you can test to see if your issue is a 
REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your 
bug pertains to a feature added after 3.3) from 
http://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword


Feel free to come ask questions or to say hello in our QA chat: 
https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-UntouchedBug

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

Title:
  Arabic text gets deformed when creating a PDF in LibreOffice Writer

To manage notifications about this bug go to:
https://bugs.launchpad.net/df-libreoffice/+bug/1772439/+subscriptions

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

[Bug 1845154] Re: do not see what kind of report is being submitted - no details provided

2019-09-24 Thread Chris Guiver
** Changed in: update-notifier (Ubuntu)
   Status: Incomplete => New

** Summary changed:

- do not see what kind of report is being submitted - no details provided
+ feature request: "System problem detected" without details provided, request 
for more detail in message

** Description changed:

  Every (re)boot, I got this error popup window displayed. It is quite
  new, earlier Xubuntu versions had not been having this issue. The
  problem is: what is it about? There are no details whatsoever :/ I will
  attach a screenshot next reboot...
+ 
+ (from question discussion https://answers.launchpad.net/ubuntu/+source
+ /update-notifier/+question/684182)
+ 
+ "OK, I've removed all from /var/crash - and now I am OK - no dialogue
+ being opened any more. So thank you!
+ 
+ BUT...
+ 
+ I still want to make a feature request in order to: let the users know
+ where the crashes are located"
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: update-notifier 3.192.18
  ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Sep 24 09:33:27 2019
  ExecutablePath: /usr/bin/update-notifier
  InstallationDate: Installed on 2018-09-03 (385 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: update-notifier
  UpgradeStatus: Upgraded to disco on 2019-06-16 (99 days ago)

** Description changed:

  Every (re)boot, I got this error popup window displayed. It is quite
  new, earlier Xubuntu versions had not been having this issue. The
  problem is: what is it about? There are no details whatsoever :/ I will
  attach a screenshot next reboot...
  
  (from question discussion https://answers.launchpad.net/ubuntu/+source
  /update-notifier/+question/684182)
  
- "OK, I've removed all from /var/crash - and now I am OK - no dialogue
- being opened any more. So thank you!
- 
- BUT...
+ "OK, I've removed all from /var/crash - and now I am OK ..  BUT...
  
  I still want to make a feature request in order to: let the users know
  where the crashes are located"
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: update-notifier 3.192.18
  ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Sep 24 09:33:27 2019
  ExecutablePath: /usr/bin/update-notifier
  InstallationDate: Installed on 2018-09-03 (385 days ago)
  InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: update-notifier
  UpgradeStatus: Upgraded to disco on 2019-06-16 (99 days ago)

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

Title:
  feature request: "System problem detected" without details provided,
  request for more detail in message

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

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

[Bug 1845271] [NEW] bluetooth device connects, but never shows up as output device in audio devices

2019-09-24 Thread Thomas Schweikle
Public bug reported:

bluetooth audio device connects, pairs and is shown as trusted device.
But it is never shown as output device for audio output. It is not shown
at all.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: blueman 2.0.5-1ubuntu2
ProcVersionSignature: Ubuntu 5.0.0-30.32-generic 5.0.21
Uname: Linux 5.0.0-30-generic x86_64
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
CurrentDesktop: XFCE
Date: Wed Sep 25 00:11:31 2019
InstallationDate: Installed on 2011-10-19 (2897 days ago)
InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
SourcePackage: blueman
UpgradeStatus: Upgraded to disco on 2019-04-27 (150 days ago)

** Affects: blueman (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/1845271

Title:
  bluetooth device connects, but never shows up as output device in
  audio devices

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

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

[Bug 1840956] Autopkgtest regression report (qemu/1:3.1+dfsg-2ubuntu3.5)

2019-09-24 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted qemu (1:3.1+dfsg-2ubuntu3.5) for disco 
have finished running.
The following regressions have been reported in tests triggered by the package:

systemd/240-6ubuntu5.7 (armhf, ppc64el)
ubuntu-image/1.7+19.04ubuntu1 (i386)
cinder/2:14.0.0-0ubuntu1 (amd64, i386, armhf, arm64, ppc64el, s390x)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/disco/update_excuses.html#qemu

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  qemu-user-static fails to install in WSL

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

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

[Bug 1845269] Re: nvidia proprietary dkms module builds but doesn't load

2019-09-24 Thread Steve Conklin
purging all nvidia* and libnvidia* packages and rebooting restores
operation on Nouveau

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

Title:
  nvidia proprietary dkms module builds but doesn't load

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

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

[Bug 1845269] [NEW] nvidia proprietary dkms module builds but doesn't load

2019-09-24 Thread Steve Conklin
Public bug reported:

This is a freshly installed 18.04.3 system.

lspci -vv output for the video card:
02:00.0 VGA compatible controller: NVIDIA Corporation GF108 [GeForce GT 440] 
(rev a1) (prog-if 00 [VGA controller])
Subsystem: eVga.com. Corp. GF108 [GeForce GT 440]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- 
Kernel driver in use: nouveau
Kernel modules: nvidiafb, nouveau


I'll attach the driver install and build logs

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-5.0.0-29-generic 5.0.0-29.31~18.04.1
ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-29-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Sep 24 16:58:42 2019
InstallationDate: Installed on 2019-09-24 (0 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: linux-signed-hwe
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-signed-hwe (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

** Attachment added: "debug.txt"
   https://bugs.launchpad.net/bugs/1845269/+attachment/5291000/+files/debug.txt

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

Title:
  nvidia proprietary dkms module builds but doesn't load

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

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

[Bug 1808389] Re: iwlwifi Intel 8265 firmware crashing on lenovo x1 Gen 6

2019-09-24 Thread inkvizitor68sl
Sorry, forget to point, that it happens on 19.04 for me

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

Title:
  iwlwifi  Intel 8265 firmware crashing on lenovo x1 Gen 6

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

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

[Bug 1845036] Re: Xenial update: 4.4.191 upstream stable release

2019-09-24 Thread Connor Kuehl
** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The following upstream
+    stable patches should be included in the Ubuntu kernel:
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+ * HID: Add 044f:b320 ThrustMaster, Inc. 2 in 1 DT
+ * MIPS: kernel: only use i8253 clocksource with periodic clockevent
+ * netfilter: ebtables: fix a memory leak bug in compat
+ * bonding: Force slave speed check after link state recovery for 802.3ad
+ * can: dev: call netif_carrier_off() in register_candev()
+ * st21nfca_connectivity_event_received: null check the allocation
+ * st_nci_hci_connectivity_event_received: null check the allocation
+ * ASoC: ti: davinci-mcasp: Correct slot_width posed constraint
+ * net: usb: qmi_wwan: Add the BroadMobi BM818 card
+ * isdn: mISDN: hfcsusb: Fix possible null-pointer dereferences in 
start_isoc_chain()
+ * isdn: hfcsusb: Fix mISDN driver crash caused by transfer buffer on the stack
+ * perf bench numa: Fix cpu0 binding
+ * can: sja1000: force the string buffer NULL-terminated
+ * can: peak_usb: force the string buffer NULL-terminated
+ * NFSv4: Fix a potential sleep while atomic in nfs4_do_reclaim()
+ * net: cxgb3_main: Fix a resource leak in a error path in 'init_one()'
+ * net: hisilicon: make hip04_tx_reclaim non-reentrant
+ * net: hisilicon: fix hip04-xmit never return TX_BUSY
+ * net: hisilicon: Fix dma_map_single failed on arm64
+ * libata: add SG safety checks in SFF pio transfers
+ * selftests: kvm: Adding config fragments
+ * HID: wacom: correct misreported EKR ring values
+ * Revert "dm bufio: fix deadlock with loop device"
+ * userfaultfd_release: always remove uffd flags and clear vm_userfaultfd_ctx
+ * x86/retpoline: Don't clobber RFLAGS during CALL_NOSPEC on i386
+ * x86/apic: Handle missing global clockevent gracefully
+ * x86/boot: Save fields explicitly, zero out everything else
+ * x86/boot: Fix boot regression caused by bootparam sanitizing
+ * dm btree: fix order of block initialization in btree_split_beneath
+ * dm space map metadata: fix missing store of apply_bops() return value
+ * dm table: fix invalid memory accesses with too high sector number
+ * cgroup: Disable IRQs while holding css_set_lock
+ * net: arc_emac: fix koops caused by sk_buff free
+ * siphash: implement HalfSipHash1-3 for hash tables
+ * netfilter: ctnetlink: don't use conntrack/expect object addresses as id
+ * netfilter: conntrack: Use consistent ct id hash calculation
+ * Revert "perf test 6: Fix missing kvm module load for s390"
+ * x86/pm: Introduce quirk framework to save/restore extra MSR registers 
around suspend/resume
+ * x86/CPU/AMD: Clear RDRAND CPUID bit on AMD family 15h/16h
+ * scsi: ufs: Fix NULL pointer dereference in ufshcd_config_vreg_hpm()
+ * dmaengine: ste_dma40: fix unneeded variable warning
+ * usb: gadget: composite: Clear "suspended" on reset/disconnect
+ * usb: host: fotg2: restart hcd after port reset
+ * tools: hv: fix KVP and VSS daemons exit code
+ * watchdog: bcm2835_wdt: Fix module autoload
+ * tcp: fix tcp_rtx_queue_tail in case of empty retransmit queue
+ * ALSA: usb-audio: Fix a stack buffer overflow bug in check_input_term
+ * ALSA: usb-audio: Fix an OOB bug in parse_audio_mixer_unit
+ * tcp: make sure EPOLLOUT wont be missed
+ * ALSA: seq: Fix potential concurrent access to the deleted pool
+ * KVM: x86: Don't update RIP or do single-step on faulting emulation
+ * x86/apic: Do not initialize LDR and DFR for bigsmp
+ * x86/apic: Include the LDR when clearing out APIC registers
+ * usb-storage: Add new JMS567 revision to unusual_devs
+ * USB: cdc-wdm: fix race between write and disconnect due to flag abuse
+ * usb: host: ohci: fix a race condition between shutdown and irq
+ * USB: storage: ums-realtek: Update module parameter description for 
auto_delink_en
+ * USB: storage: ums-realtek: Whitelist auto-delink support
+ * ptrace,x86: Make user_64bit_mode() available to 32-bit builds
+ * uprobes/x86: Fix detection of 32-bit user mode
+ * mmc: sdhci-of-at91: add quirk for broken HS200
+ * mmc: core: Fix init of SD cards reporting an invalid VDD range
+ * stm class: Fix a double free of stm_source_device
+ * VMCI: Release resource if the work is already queued
+ * Revert "cfg80211: fix processing 

[Bug 1808389] Re: iwlwifi Intel 8265 firmware crashing on lenovo x1 Gen 6

2019-09-24 Thread inkvizitor68sl
Affects me too on X1g6
Both, 2.4 and 5 GHz essids. 
Easily reproduces, while i am trying to rsync whole / to local NAS. 

linux-firmware=1.178.3
5.2.6-050206-generic 


** Attachment added: "dmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+bug/1808389/+attachment/5290999/+files/dmesg.txt

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

Title:
  iwlwifi  Intel 8265 firmware crashing on lenovo x1 Gen 6

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

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

[Bug 1845266] [NEW] Bionic update: upstream stable patchset 2019-09-24

2019-09-24 Thread Kamal Mostafa
Public bug reported:

SRU Justification

Impact:
   The upstream process for stable tree updates is quite similar
   in scope to the Ubuntu SRU process, e.g., each patch has to
   demonstrably fix a bug, and each patch is vetted by upstream
   by originating either directly from a mainline/stable Linux tree or
   a minimally backported form of that patch. The following upstream
   stable patches should be included in the Ubuntu kernel:

   upstream stable patchset 2019-09-24

Ported from the following upstream stable releases:
v4.14.145, v4.19.74
v4.14.146, v4.19.75

   from git://git.kernel.org/

bridge/mdb: remove wrong use of NLM_F_MULTI
cdc_ether: fix rndis support for Mediatek based smartphones
ipv6: Fix the link time qualifier of 'ping_v6_proc_exit_net()'
isdn/capi: check message length in capi_write()
net: Fix null de-reference of device refcount
net: gso: Fix skb_segment splat when splitting gso_size mangled skb having 
linear-headed frag_list
net: phylink: Fix flow control resolution
sch_hhf: ensure quantum and hhf_non_hh_weight are non-zero
sctp: Fix the link time qualifier of 'sctp_ctrlsock_exit()'
sctp: use transport pf_retrans in sctp_do_8_2_transport_strike
tcp: fix tcp_ecn_withdraw_cwr() to clear TCP_ECN_QUEUE_CWR
tipc: add NULL pointer check before calling kfree_rcu
tun: fix use-after-free when register netdev failed
btrfs: compression: add helper for type to string conversion
btrfs: correctly validate compression type
Revert "MIPS: SiByte: Enable swiotlb for SWARM, LittleSur and BigSur"
gpiolib: acpi: Add gpiolib_acpi_run_edge_events_on_boot option and blacklist
gpio: fix line flag validation in linehandle_create
gpio: fix line flag validation in lineevent_create
Btrfs: fix assertion failure during fsync and use of stale transaction
genirq: Prevent NULL pointer dereference in resend_irqs()
KVM: s390: Do not leak kernel stack data in the KVM_S390_INTERRUPT ioctl
KVM: x86: work around leak of uninitialized stack contents
KVM: nVMX: handle page fault in vmread
MIPS: VDSO: Prevent use of smp_processor_id()
MIPS: VDSO: Use same -m%-float cflag as the kernel proper
powerpc: Add barrier_nospec to raw_copy_in_user()
drm/meson: Add support for XBGR & ABGR formats
clk: rockchip: Don't yell about bad mmc phases when getting
mtd: rawnand: mtk: Fix wrongly assigned OOB buffer pointer issue
PCI: Always allow probing with driver_override
ubifs: Correctly use tnc_next() in search_dh_cookie()
driver core: Fix use-after-free and double free on glue directory
crypto: talitos - check AES key size
crypto: talitos - fix CTR alg blocksize
crypto: talitos - check data blocksize in ablkcipher.
crypto: talitos - fix ECB algs ivsize
crypto: talitos - Do not modify req->cryptlen on decryption.
crypto: talitos - HMAC SNOOP NO AFEU mode requires SW icv checking.
firmware: ti_sci: Always request response from firmware
drm/mediatek: mtk_drm_drv.c: Add of_node_put() before goto
Revert "Bluetooth: btusb: driver to enable the usb-wakeup feature"
platform/x86: pmc_atom: Add CB4063 Beckhoff Automation board to critclk_systems 
DMI table
nvmem: Use the same permissions for eeprom as for nvmem
x86/build: Add -Wnoaddress-of-packed-member to REALMODE_CFLAGS, to silence GCC9 
build warning
ixgbe: Prevent u8 wrapping of ITR value to something less than 10us
x86/purgatory: Change compiler flags from -mcmodel=kernel to -mcmodel=large to 
fix kexec relocation errors
modules: fix BUG when load module with rodata=n
modules: fix compile error if don't have strict module rwx
UBUNTU: upstream stable to v4.14.145, v4.19.74
HID: wacom: generic: read HID_DG_CONTACTMAX from any feature report
Input: elan_i2c - remove Lenovo Legion Y7000 PnpID
powerpc/mm/radix: Use the right page size for vmemmap mapping
USB: usbcore: Fix slab-out-of-bounds bug during device reset
phy: renesas: rcar-gen3-usb2: Disable clearing VBUS in over-current
media: tm6000: double free if usb disconnect while streaming
xen-netfront: do not assume sk_buff_head list is empty in error handling
net_sched: let qdisc_put() accept NULL pointer
KVM: coalesced_mmio: add bounds checking
firmware: google: check if size is valid when decoding VPD data
serial: sprd: correct the wrong sequence of arguments
tty/serial: atmel: reschedule TX after RX was started
mwifiex: Fix three heap overflow at parsing element in cfg80211_ap_settings
nl80211: Fix possible Spectre-v1 for CQM RSSI thresholds
ARM: OMAP2+: Fix missing SYSC_HAS_RESET_STATUS for dra7 epwmss
s390/bpf: fix lcgr instruction encoding
ARM: OMAP2+: Fix omap4 errata warning on other SoCs
ARM: dts: dra74x: Fix iodelay configuration for mmc3
s390/bpf: use 32-bit index for tail calls
fpga: altera-ps-spi: Fix getting of optional confd gpio
netfilter: xt_nfacct: Fix alignment mismatch in xt_nfacct_match_info
NFSv4: Fix return values for nfs4_file_open()
NFSv4: Fix return value in nfs_finish_open()
NFS: Fix initialisation of I/O 

[Bug 1845264] [NEW] Calico plugin deployment fails with Atomic image.

2019-09-24 Thread Henro
Public bug reported:

Deployment details:
template: 
cluster_distro: fedora-atomic
network_driver: calico
image: 
Fedora-Atomic-27-2018041
labels:
{'kube_tag': 'v1.15.4', 'kube_allow_priv': 'true', 'ingress': 'nginx', 
'tiller_enabled': 'true', 'tiller_tag': 'v2.13.1'} |

Issue:

The calico deployment fails and I see the following in the system logs:

Unable to update cni config: No networks found in /etc/cni/net.d
Container runtime network not ready: NetworkReady=false 
reason:NetworkPluginNotReady message:docker: network plugin is not ready: cni 
config uninitialized

The directory /etc/cni/net.d is empty.

When I try to deploy calico manually with the following commands:
CALICO_DEPLOY=/srv/magnum/kubernetes/manifests/calico-deploy.yaml
/usr/local/bin/kubectl apply -f ${CALICO_DEPLOY} --namespace=kube-system

I get the following:
The DaemonSet "calico-node" is invalid: 
spec.template.spec.containers[0].securityContext.privileged: Forbidden: 
disallowed by cluster policy

I believe this is caused by missing --allow-privileged=true flag in kube
apiserver config.

This is a workaround that fixed it for me, along with label:
'kube_allow_priv': 'true':

--- 
/usr/lib/python3/dist-packages/magnum/drivers/common/templates/kubernetes/fragments/configure-kubernetes-master.sh.orig
 2019-09-24 21:13:02.947882594 +
+++ 
/usr/lib/python3/dist-packages/magnum/drivers/common/templates/kubernetes/fragments/configure-kubernetes-master.sh
  2019-09-24 21:13:16.291766370 +
@@ -60,7 +60,7 @@
 
-KUBE_API_ARGS="--runtime-config=api/all=true"
+KUBE_API_ARGS="--runtime-config=api/all=true 
--allow-privileged=$KUBE_ALLOW_PRIV"
 

Not sure if I missed any config options but I could not find if the flag
was added anywhere else.


Henro

** Affects: magnum (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/1845264

Title:
  Calico plugin deployment fails with Atomic image.

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

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

[Bug 1845265] [NEW] Calico plugin deployment fails with Atomic image.

2019-09-24 Thread Henro
Public bug reported:

Deployment details:
template: 
cluster_distro: fedora-atomic
network_driver: calico
image: 
Fedora-Atomic-27-2018041
labels:
{'kube_tag': 'v1.15.4', 'kube_allow_priv': 'true', 'ingress': 'nginx', 
'tiller_enabled': 'true', 'tiller_tag': 'v2.13.1'} |

Issue:

The calico deployment fails and I see the following in the system logs:

Unable to update cni config: No networks found in /etc/cni/net.d
Container runtime network not ready: NetworkReady=false 
reason:NetworkPluginNotReady message:docker: network plugin is not ready: cni 
config uninitialized

The directory /etc/cni/net.d is empty.

When I try to deploy calico manually with the following commands:
CALICO_DEPLOY=/srv/magnum/kubernetes/manifests/calico-deploy.yaml
/usr/local/bin/kubectl apply -f ${CALICO_DEPLOY} --namespace=kube-system

I get the following:
The DaemonSet "calico-node" is invalid: 
spec.template.spec.containers[0].securityContext.privileged: Forbidden: 
disallowed by cluster policy

I believe this is caused by missing --allow-privileged=true flag in kube
apiserver config.

This is a workaround that fixed it for me, along with label:
'kube_allow_priv': 'true':

--- 
/usr/lib/python3/dist-packages/magnum/drivers/common/templates/kubernetes/fragments/configure-kubernetes-master.sh.orig
 2019-09-24 21:13:02.947882594 +
+++ 
/usr/lib/python3/dist-packages/magnum/drivers/common/templates/kubernetes/fragments/configure-kubernetes-master.sh
  2019-09-24 21:13:16.291766370 +
@@ -60,7 +60,7 @@
 
-KUBE_API_ARGS="--runtime-config=api/all=true"
+KUBE_API_ARGS="--runtime-config=api/all=true 
--allow-privileged=$KUBE_ALLOW_PRIV"
 

Not sure if I missed any config options but I could not find if the flag
was added anywhere else.


Henro

** Affects: magnum (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/1845265

Title:
  Calico plugin deployment fails with Atomic image.

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

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

[Bug 1782922] Re: LDAP: changing user_id_attribute bricks group mapping

2019-09-24 Thread Corey Bryant
Ubuntu SRU Details:

[Impact]
When using the keystone LDAP backend, changing user_id_attribute breaks group 
mapping. This is because the _dn_to_id() method only calculated the uid to be 
the first RDN of the DN. _dn_to_id() is updated in the fix to also deal with 
the case where the uid is set to a different attribute.

[Test Case]
See details in comment #5: 
https://bugs.launchpad.net/keystone/+bug/1782922/comments/5

[Regression Potential]
The patch takes a minimal approach to the fix and includes unit tests to help 
ensure the patched code doesn't regress. The patches have landed in all 
upstream releases back to stable/queens which helps get even more exposure with 
upstream reviews, gate testing and real deployments.

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

Title:
  LDAP: changing user_id_attribute bricks group mapping

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

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

[Bug 1845262] [NEW] papirus-icon-theme does not show trash can full icon

2019-09-24 Thread FranksMCB
Public bug reported:

Ubuntu MATE 19.10 beta

Installed papirus-icon-theme and enabled Trashcan icon on desktop.


Expected:
When adding trash to Trashcan, icon changes to "red"

Actual:
When adding trash to Trashcan, icon does not change to "red"

This is working in 18.04 and 19.04 Ubuntu MATE

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: papirus-icon-theme 20190817-1
ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
Uname: Linux 5.3.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: MATE
Date: Tue Sep 24 15:08:37 2019
Dependencies: hicolor-icon-theme 0.17-2
InstallationDate: Installed on 2019-09-24 (0 days ago)
InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Alpha amd64 (20190924.1)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: papirus-icon-theme
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: papirus-icon-theme (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug eoan

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

Title:
  papirus-icon-theme does not show trash can full icon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/papirus-icon-theme/+bug/1845262/+subscriptions

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

[Bug 1845263] [NEW] [wishlist] Add TLSv1.3 support to apache2 on Bionic

2019-09-24 Thread Simon Déziel
Public bug reported:

Since LP: #1797386, openssl with TLS 1.3 support is available on Bionic.
This had the nice side effect of enabling TLS 1.3 for various services
(nginx, postfix, dovecot, etc) but not apache2.

TLS 1.3 support is required to use the "modern compatibility"
configuration recommended by Mozilla [1]. Since Bionic is an LTS release
and apache2 is popular and in main, it would be nice to have support for
TLS 1.3.

According to [2], support for TLS 1.3 was added in version 2.4.36 while
Bionic ships 2.4.29. Disco ships with 2.4.38 so should be OK.


1: https://wiki.mozilla.org/Security/Server_Side_TLS#Modern_compatibility
2: 
https://ssl-config.mozilla.org/#server=apache=2.4.39=modern=1.1.1

** Affects: apache2 (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: bionic wishlist

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

Title:
  [wishlist] Add TLSv1.3 support to apache2 on Bionic

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

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

[Bug 1845263] Re: [wishlist] Add TLSv1.3 support to apache2 on Bionic

2019-09-24 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: apache2 (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/1845263

Title:
  [wishlist] Add TLSv1.3 support to apache2 on Bionic

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

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

[Bug 1842382] Re: /proc/self/maps paths missing on live session (was vlc won't start; eoan 19.10 & bionic 18.04 ubuntu/lubuntu/kubuntu/xubuntu/ubuntu-mate dailies)

2019-09-24 Thread Seth Forshee
Revert submitted for SRU to disco:

https://lists.ubuntu.com/archives/kernel-team/2019-September/103893.html

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

Title:
  /proc/self/maps paths missing on live session (was vlc won't start;
  eoan 19.10 & bionic 18.04 ubuntu/lubuntu/kubuntu/xubuntu/ubuntu-mate
  dailies)

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

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

[Bug 1845037] Re: autopkgtest package "lxd" test has started failing

2019-09-24 Thread Dan Streetman
@stgraber, just to clarify, calls to lxd like this now fail:

root@autopkgtest:~# cat < lxc launch ubuntu:bionic
> echo ok done
> EOF
Error: yaml: unmarshal errors:
  line 1: cannot unmarshal !!str `echo ok...` into api.ContainerPut


is it really expected that lxd should fail when used with input queued on stdin 
like this?

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

Title:
  autopkgtest package "lxd" test has started failing

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

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

[Bug 1586528] Re: Avahi-daemon withdraws address record

2019-09-24 Thread hellscream
I found a workaround this problem.
Check my git
https://github.com/WillyWeiss/-Avahi-daemon-withdraws-address-record-/blob/master/README.md

I just a simple bash that check for a valid IP Address on a given card. 
If the IP is not found then 'dhclient' will be called on that given 
interface(card)
It is working by default on eth0 but you can add more cards in the script. Just 
read the readme in the git above. 

Hope it helps.

Prove of functionality:
Sep 24 16:47:40 MyHostName rngd[395]: stats: Entropy starvations: 0
Sep 24 16:47:40 MyHostName rngd[395]: stats: Time spent starving for entropy: 
(min=0; avg=0.000; max=0)us
Sep 24 16:47:46 MyHostName avahi-daemon[380]: Withdrawing address record for 
192.168.0.13 on eth0.
Sep 24 16:47:46 MyHostName avahi-daemon[380]: Leaving mDNS multicast group on 
interface eth0.IPv4 with address 192.168.0.13.
Sep 24 16:47:46 MyHostName avahi-daemon[380]: Interface eth0.IPv4 no longer 
relevant for mDNS.
Sep 24 16:47:47 MyHostName dhclient[4487]: DHCPREQUEST for 192.168.0.13 on eth0 
to 255.255.255.255 port 67
Sep 24 16:47:47 MyHostName dhclient[4487]: DHCPACK of 192.168.0.13 from 
192.168.0.1
Sep 24 16:47:47 MyHostName avahi-daemon[380]: Joining mDNS multicast group on 
interface eth0.IPv4 with address 192.168.0.13.
Sep 24 16:47:47 MyHostName avahi-daemon[380]: New relevant interface eth0.IPv4 
for mDNS.
Sep 24 16:47:47 MyHostName avahi-daemon[380]: Registering new address record 
for 192.168.0.13 on eth0.IPv4.
Sep 24 16:47:47 MyHostName dhclient[4487]: bound to 192.168.0.13 -- renewal in 
41664 seconds.

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

Title:
  Avahi-daemon withdraws address record

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

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

[Bug 1771914] Re: release-upgrade-motd can't update message via apt proxy

2019-09-24 Thread Brian Murray
Hello Kaneg, or anyone else affected,

Accepted update-manager into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/update-
manager/1:16.04.16 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: update-manager (Ubuntu Xenial)
   Status: New => Fix Committed

** Tags added: verification-needed-xenial

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

Title:
  release-upgrade-motd can't update message via apt proxy

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

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

[Bug 1744318] Re: changelogs.ubuntu.com should be using HTTPS

2019-09-24 Thread Brian Murray
Hello TJ, or anyone else affected,

Accepted update-manager into xenial-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/update-
manager/1:16.04.16 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: update-manager (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-xenial

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

Title:
  changelogs.ubuntu.com should be using HTTPS

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

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

[Bug 1833229] Re: `--extra-index-url` not working for PIP

2019-09-24 Thread Marc Mercer
@james-page I think the thing being overlooked is what it is doing, not
wether or not the exception is correct.  In our case, we have
repositories that have some artifacts, and repositories that may have
other artifacts... (and once in a rare while, overlap with different
versions)..   If we request a package that does *not* exist in the
custom urls, then it will fail completely, instead of passing with the
only failure being on that one repository.  By default, it should check
each of the repositories, see if they have it, etc..  It seems to be
checking them all, but if *any* of them fails to have an artifact being
requested, the entire pip operation implodes, even if the package *is*
available in a different repository successfully prior to the fetching
of the failed repo.

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

Title:
  `--extra-index-url` not working for PIP

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

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

[Bug 1787110] Re: False positives in reporting server unavailable

2019-09-24 Thread Brian Murray
Hello Robbert, or anyone else affected,

Accepted nagios-plugins-rabbitmq into xenial-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/nagios-plugins-rabbitmq/1:1.2.0-2.1ubuntu0.1 in a few hours, and then
in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: nagios-plugins-rabbitmq (Ubuntu Xenial)
   Status: Triaged => Fix Committed

** Tags added: verification-needed-xenial

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

Title:
  False positives in reporting server unavailable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nagios-plugins-rabbitmq/+bug/1787110/+subscriptions

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

[Bug 1844570] Re: xtables-addons fail to build with linux-hwe-edge 5.3

2019-09-24 Thread Brian Murray
Hello Thadeu, or anyone else affected,

Accepted xtables-addons into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/xtables-
addons/3.0-0.1ubuntu3 in a few hours, and then in the -proposed
repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: xtables-addons (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-bionic

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

Title:
  xtables-addons fail to build with linux-hwe-edge 5.3

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

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

[Bug 1845218] Re: --hash argument ignored when creating a luks2 volume

2019-09-24 Thread Jabb
In addition, I see a link to another bug report:
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1843181

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

Title:
  --hash argument ignored when creating a luks2 volume

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

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

[Bug 1845218] Re: --hash argument ignored when creating a luks2 volume

2019-09-24 Thread Jabb
That's right, but I am asking you to update the Ubuntu 18.04 package
because the current version of cryptsetup is too low (2.0.2 and the bug
removed in 2.2.0)

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

Title:
  --hash argument ignored when creating a luks2 volume

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

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

[Bug 1844591] Re: nat-rtsp fails to build with linux-hwe-edge 5.3

2019-09-24 Thread Brian Murray
Hello Thadeu, or anyone else affected,

Accepted nat-rtsp into bionic-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/nat-
rtsp/0.7+1.g2ea3cb6-1ubuntu1~18.04.2 in a few hours, and then in the
-proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: nat-rtsp (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-bionic

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

Title:
  nat-rtsp fails to build with linux-hwe-edge 5.3

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

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

[Bug 1844719] Re: v4l2loopback fails to build with linux-hwe-edge 5.3

2019-09-24 Thread Brian Murray
Hello Thadeu, or anyone else affected,

Accepted v4l2loopback into bionic-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/v4l2loopback/0.10.0-1ubuntu1.2 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: v4l2loopback (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-bionic

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

Title:
  v4l2loopback fails to build with linux-hwe-edge 5.3

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

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

[Bug 1839890] Re: openafs 1.8.0~pre5-1ubuntu1 fails to build on 5.0 kernels

2019-09-24 Thread Connor Kuehl
** Description changed:

  [Impact]
  
  * The openafs DKMS module fails to build on 5.0 kernels due to changes
  in the kernel API between 4.15 and 5.0. This affects the Bionic
  HWE{-edge} kernels which are based on 5.0.
  
  [Test Case]
  
  * Install the `openafs` dkms modules package (sudo apt install openafs-
  modules-dkms)
  
  Expected result: the package installs without any build-time errors, and
  the module is listed when `sudo dkms status` is ran.
  
  Actual result: the package installation fails because the openafs dkms
  module fails to build with compilation errors
  
  [Testing]
  
  These instructions were carried out in an amd64 Bionic virtual machine
  with the 4.15 Bionic kernel and the 5.0 Bionic HWE kernel.
  
  * Install the 5.0 kernel (sudo apt update; sudo apt install 
linux-image-generic-hwe-18.04)
- * Install the ubuntu-dev-tools package (sudo apt install ubuntu-dev-tools)
- * Download the openafs package (pull-lp-source openafs bionic)
- * In the openafs directory, run "quilt pop -a"
- * Apply the .debdiff in comment #3 (patch -p1 < ../path-to-file.debdiff)
- * Apply all patches (quilt push -a)
- * Build the package (debuild -b -uc -us)
- * Install the `openafs-modules-dkms_1.8.0~pre5-1ubuntu1.1_all.deb` produced 
from the previous step.
+ * Install `openafs-modules-dkms` from -proposed
  * Confirm the package installs correctly on 4.15 and 5.0 kernels (it should 
install for both). Run "sudo dkms status" and ensure it's listed there.
  
  If it doesn't install for both kernels, you can prompt it to install for
  a specific kernel like this: "sudo dkms install openafs/1.8.0pre5 -k
  4.15.0-55-generic/x86_64
  
  [Regression Potential]
  
  Low. These changes use preprocessor define macros that are deduced at
  configuration time to tell the package to act "normal" if a given
  feature exists or doesn't exist.

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

Title:
  openafs 1.8.0~pre5-1ubuntu1 fails to build on 5.0 kernels

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

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

[Bug 1839890] Re: openafs 1.8.0~pre5-1ubuntu1 fails to build on 5.0 kernels

2019-09-24 Thread Brian Murray
Hello Connor, or anyone else affected,

Accepted openafs into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/openafs/1.8.0~pre5-1ubuntu1.1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: openafs (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-bionic

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

Title:
  openafs 1.8.0~pre5-1ubuntu1 fails to build on 5.0 kernels

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

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

  1   2   3   4   5   >