date:20191026

This problem is fixed by this commit, it is in the
https://github.com/raspberrypi/linux.git

(the data structure does not match the firmware definition)


commit 26f64fa81357f4b18192432eb8023f99c7eb5cf7 (HEAD -> 
26f64fa81357f4b18192432eb8023f99c7eb5cf7)
Author: Michael Brown 
Date:   Sun Sep 22 21:51:29 2019 +0100

bcm2708_fb: Fix layout of struct vc4_display_settings_t

The display parameters returned by the VC4 firmware in response to the
RPI_FIRMWARE_FRAMEBUFFER_GET_DISPLAY_SETTINGS tag do not match the
layout of struct vc4_display_settings_t: the colour depth and row
pitch are erroneously swapped in the kernel definition.  This can
trigger a kernel warning from pixel_to_pat(), such as:

  pixel_to_pat(): unsupported pixelformat 7296

Fix by adjusting the layout of struct vc4_display_settings_t to match
the layout as used by the VC4 firmware.

Signed-off-by: Michael Brown 

diff --git a/drivers/video/fbdev/bcm2708_fb.c b/drivers/video/fbdev/bcm2708_fb.c
index 4da577c8a0d8..59443f79f228 100644
--- a/drivers/video/fbdev/bcm2708_fb.c
+++ b/drivers/video/fbdev/bcm2708_fb.c
@@ -88,8 +88,8 @@ struct vc4_display_settings_t {
u32 display_num;
u32 width;
u32 height;
-   u32 pitch;
u32 depth;
+   u32 pitch;
u32 virtual_width;
u32 virtual_height;
u32 virtual_width_offset;

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

Title:
  rpi3b+: corrupted screen on hdmi

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

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

[Bug 1850023] Re: malformed gui in 1910

2019-10-26 Thread Paul Ortyl

*** This bug is a duplicate of bug 1827859 ***
https://bugs.launchpad.net/bugs/1827859

Duplicate of https://bugs.launchpad.net/ubuntu/+source/cura/+bug/1827859


** This bug has been marked a duplicate of bug 1827859
   Cura 3.3.1 not working correctly

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

Title:
  malformed gui in 1910

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

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

[Bug 1847596] Re: rpi3b+: corrupted screen on hdmi

And this bug will be fixed with
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1849623


And there is a testing kernel, we could install this testing kernel and remove 
the vc4-fkms-v3d from the config.txt.
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848790/comments/11

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

Title:
  rpi3b+: corrupted screen on hdmi

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

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

[Bug 1848075] Re: eoan server image does not boot on RPI3-A+

*** This bug is a duplicate of bug 1848247 ***
https://bugs.launchpad.net/bugs/1848247

About the root cause and fix for this bug, please refer to:

https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1847596/comments/9
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1847596/comments/10

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

Title:
  eoan server image does not boot on RPI3-A+

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

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

[Bug 1850023] [NEW] malformed gui in 1910

2019-10-26 Thread Paul Ortyl

*** This bug is a duplicate of bug 1827859 ***
https://bugs.launchpad.net/bugs/1827859

Public bug reported:

Cura starts with a lot warnings and error messages in the console.
Menus and control buttons are missing.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: cura 3.3.1-2
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Oct 27 07:39:20 2019
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-02-25 (1339 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160225)
PackageArchitecture: all
SourcePackage: cura
UpgradeStatus: Upgraded to eoan on 2019-09-30 (26 days ago)

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


** Tags: amd64 apport-bug eoan wayland-session

** Attachment added: "Console output of first run"
   
https://bugs.launchpad.net/bugs/1850023/+attachment/5300531/+files/cura_console_output.txt

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

Title:
  malformed gui in 1910

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

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

[Bug 1849682] Re: [REGRESSION] md/raid0: cannot assemble multi-zone RAID0 with default_layout setting

2019-10-26 Thread Khaled El Mously

** Changed in: linux (Ubuntu Bionic)
   Status: Confirmed => 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/1849682

Title:
  [REGRESSION]  md/raid0: cannot assemble multi-zone RAID0 with
  default_layout setting

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

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

[Bug 1848703] Re: Raspberry Pi 4 - USB Bus not detecting any devices

*** This bug is a duplicate of bug 1848790 ***
https://bugs.launchpad.net/bugs/1848790

And this bug will be fixed with
https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1849623

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

Title:
  Raspberry Pi 4 - USB Bus not detecting any devices

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

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

[Bug 1848790] Re: USB not working under arm64 on Pi4

And also Pi 3 Model A Plus is not in the all.db.

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

Title:
  USB not working under arm64 on Pi4

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

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

[Bug 1849669] Re: do-release-upgrade (19.04 -> 19.10) aborts

2019-10-26 Thread Arul

distro-info:
  Installed: 0.21ubuntu2
  Candidate: 0.21ubuntu2
  Version table:
 *** 0.21ubuntu2 500
500 http://in.archive.ubuntu.com/ubuntu disco/main amd64 Packages
100 /var/lib/dpkg/status


This is what i got

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

Title:
  do-release-upgrade (19.04 -> 19.10) aborts

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

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

[Bug 1841953] Re: Bionic ⋅ SuperTuxKart ⋅ Flickering shadows ⋅ Haswell i915

2019-10-26 Thread Timo Aaltonen

ok, thanks

then this needs to be filed upstream at gitlab.freedesktop.org/mesa

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

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

Title:
  Bionic ⋅ SuperTuxKart ⋅ Flickering shadows ⋅ Haswell i915

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

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

[Bug 1847980] Re: Lightdm is just a black screen when booting kernel 5.3 on an i5-6500, but kernels 5.0/5.2 work

2019-10-26 Thread Timo Aaltonen

great, then try 5.4-rc1 hoping that it's broken there, then a fix would
be fairly easy to spot

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

Title:
  Lightdm is just a black screen when booting kernel 5.3 on an i5-6500,
  but kernels 5.0/5.2 work

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

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

[Bug 1849052] Re: chsh.ldap in nslcd-utils crashes with segfault

2019-10-26 Thread Tatsunori Uchino

Line #33 in `/usr/share/nslcd-utils/shells.py` causes the problem.

ctypes.c_char_p(libc.getusershell()) -> OK
ctypes.c_char_p(libc.getusershell()).value -> SEGFAULT!

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

Title:
  chsh.ldap in nslcd-utils crashes with segfault

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nss-pam-ldapd/+bug/1849052/+subscriptions

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

[Bug 1846539]

2019-10-26 Thread kernelbugs

Removing SND_SOC_SOF_BROADWELL_SUPPORT fixes Pixel 2015 audio on Arch
default kernel config

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

Title:
  [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback no
  longer works on Dell Venue 11 Pro 7140

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

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

[Bug 1850019] [NEW] zfs-linux 0.7.5-1ubuntu16.6 ADT test failure with linux-hwe-edge 5.3.0-19.20~18.04.2

2019-10-26 Thread Khaled El Mously

Public bug reported:

Testing failed on:
s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/s390x/z/zfs-linux/20191025_102120_32b45@/log.gz

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


** Tags: kernel-adt-failure

** Tags added: kernel-adt-failure

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

Title:
  zfs-linux 0.7.5-1ubuntu16.6 ADT test failure with linux-hwe-edge
  5.3.0-19.20~18.04.2

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

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

[Bug 1705064] Re: lshw doesn't have logicalname, serial number, or size for nvme device

we need https://github.com/lyonel/lshw/pull/45

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

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

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

** Changed in: oem-priority
 Assignee: (unassigned) => Yuan-Chen Cheng (ycheng-twn)

** Tags added: 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/1705064

Title:
  lshw doesn't have logicalname,  serial number, or size for nvme device

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

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

[Bug 1826737] Re: lshw does not list NVMe storage devices as "disk" nodes ( RedHat Bug 1695343 )

hmm, per check
https://github.com/lyonel/lshw/pull/45https://github.com/lyonel/lshw/pull/45/commits/16e1d7b9e9a1aa69a59867de0aad6411c953fbfc/commits/16e1d7b9e9a1aa69a59867de0aad6411c953fbfc

it belongs to both storage and disk class.

** Tags removed: oem-priority

** No longer affects: 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/1826737

Title:
  lshw does not list NVMe storage devices as "disk" nodes ( RedHat Bug
  1695343 )

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

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

[Bug 1848703] Re: Raspberry Pi 4 - USB Bus not detecting any devices

*** This bug is a duplicate of bug 1848790 ***
https://bugs.launchpad.net/bugs/1848790

And for me, I run commands through serial console, and if you have the
uart->usb converter, you could use serial console too.

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

Title:
  Raspberry Pi 4 - USB Bus not detecting any devices

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

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

[Bug 1850016] [NEW] undocumented mouse button 9 response

2019-10-26 Thread My name

Public bug reported:

There is an undocumented mouse button 9 response that is redundant with
the documented  mouse binds & serves no purpose. But it does interfere
with my desire to use button 9 for my own purposes. I sure would like to
know how to fix this.

** Affects: viewnior (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/1850016

Title:
  undocumented mouse button 9 response

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

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

[Bug 1848703] Re: Raspberry Pi 4 - USB Bus not detecting any devices

*** This bug is a duplicate of bug 1848790 ***
https://bugs.launchpad.net/bugs/1848790

@reply #21,

The simplest workaround is to plug the sd card into a cardreader and
connect the cardreader to computer, then edit $mount_folder/system-
boot/config.txt

Add total_mem=3072 in the section [pi4], just like below:

[pi4]
kernel=uboot_rpi_4.bin
max_framebuffers=2
total_mem=3072

Then reboot, you could you the usb keyboard now, after installing the
testing kernel, you could remove total_mem=3072.



And another way to login is to use ssh.

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

Title:
  Raspberry Pi 4 - USB Bus not detecting any devices

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

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

[Bug 1848703] Re: Raspberry Pi 4 - USB Bus not detecting any devices

2019-10-26 Thread Ricardo

*** This bug is a duplicate of bug 1848790 ***
https://bugs.launchpad.net/bugs/1848790

@Hui Wang,
But if I can't use the keyborad by USB, how can I type in those cmd?

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

Title:
  Raspberry Pi 4 - USB Bus not detecting any devices

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

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

[Bug 1807569] Re: netplan accept-ra disables slaac

[Expired for netplan.io (Ubuntu) because there has been no activity for
60 days.]

** Changed in: netplan.io (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/1807569

Title:
  netplan accept-ra disables slaac

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

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

[Bug 1807569] Re: netplan accept-ra disables slaac

[Expired for netplan because there has been no activity for 60 days.]

** Changed in: netplan
   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/1807569

Title:
  netplan accept-ra disables slaac

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

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

[Bug 1831869] Re: [SRU] Backport boost_python3 fix for cmake

[Expired for cmake (Ubuntu) because there has been no activity for 60
days.]

** Changed in: cmake (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/1831869

Title:
  [SRU] Backport boost_python3 fix for cmake

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

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

[Bug 1687130] Re: NFS client input/output-error on kernel >=4.9

[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/1687130

Title:
  NFS client input/output-error on kernel >=4.9

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

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

[Bug 1840858] Re: installer crashed

[Expired for ubiquity (Ubuntu) because there has been no activity for 60
days.]

** Changed in: ubiquity (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/1840858

Title:
  installer crashed

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

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

[Bug 1687130] Re: NFS client input/output-error on kernel >=4.9

[Expired for linux (Ubuntu Zesty) because there has been no activity for
60 days.]

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

Title:
  NFS client input/output-error on kernel >=4.9

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

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

[Bug 1840650] Re: System crashes under nfs heavy load

[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/1840650

Title:
  System crashes under nfs heavy load

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

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

[Bug 1837688] Re: Ubuntu won't boot on Dell Inspiron 7375

2019-10-26 Thread Agustin-ferrario

Flickr free boot on Eoan! I'll need it to test it in Disco

** Tags removed: verification-needed-eoan
** Tags added: verification-done-eoan

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

Title:
  Ubuntu won't boot on Dell Inspiron 7375

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

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

[Bug 1848964] Re: ubuntu-18.04.3 iso boot up, but hung up few minutes leater

2019-10-26 Thread Seiichi Nakashima

I checked ubuntu-18.04.3 Japanese edition at UEFI PC(i3-7100 CPU),
but same situation not occur.
perhaps this problem is older pc only.

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

Title:
  ubuntu-18.04.3 iso boot up, but hung up few minutes leater

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

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

[Bug 1850015] Re: Rasbpery Pi upgrade from 18.04 to 19.10 - package linux-image-5.0.0-32-generic 5.0.0-32.34 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with re

** Tags removed: need-duplicate-check

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

Title:
  Rasbpery Pi upgrade from 18.04 to 19.10 - package linux-
  image-5.0.0-32-generic 5.0.0-32.34 failed to install/upgrade: run-
  parts: /etc/kernel/postinst.d/initramfs-tools exited with return code
  1

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

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

[Bug 1792085] Re: MTP not working/very slow on Bionic

2019-10-26 Thread Prahlad Yeri

For those experiencing the slowness problem:

I've observed that if you turn on USB Debugging (by enabling Developer
Mode) on your android phone, the mtp file transfer then becomes
considerably faster.

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

Title:
  MTP not working/very slow on Bionic

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

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

[Bug 1850015] [NEW] Rasbpery Pi upgrade from 18.04 to 19.10 - package linux-image-5.0.0-32-generic 5.0.0-32.34 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with

2019-10-26 Thread Adrian Belgun

Public bug reported:

Encountered when updating my Raspberry PI 3B from 18.04 to 19.10.

ProblemType: Package
DistroRelease: Ubuntu 19.04
Package: linux-image-5.0.0-32-generic 5.0.0-32.34
ProcVersionSignature: Ubuntu 4.15.0-1048.52-raspi2 4.15.18
Uname: Linux 4.15.0-1048-raspi2 aarch64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.15.0-1048-raspi2.
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: arm64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/by-id', '/dev/snd/pcmC1D0c', '/dev/snd/controlC1', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
Card1.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
Card1.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 
'amixer'
Date: Sun Oct 27 03:17:39 2019
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
Lsusb:
 Bus 001 Device 004: ID 045e:0810 Microsoft Corp. 
 Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 
Fast Ethernet Adapter
 Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
PciMultimedia:
 
ProcFB: 0 BCM2708 FB
ProcKernelCmdLine: 8250.nr_uarts=1 bcm2708_fb.fbwidth=656 
bcm2708_fb.fbheight=416 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec0 
vc_mem.mem_size=0x4000  net.ifnames=0 dwc_otg.lpm_enable=0 
console=ttyS0,115200 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 
elevator=deadline rootwait
Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1
PythonDetails: N/A
RelatedPackageVersions: grub-pc N/A
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: initramfs-tools
Title: package linux-image-5.0.0-32-generic 5.0.0-32.34 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: Upgraded to disco on 2019-10-27 (0 days ago)

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package arm64 disco uec-images

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

Title:
  Rasbpery Pi upgrade from 18.04 to 19.10 - package linux-
  image-5.0.0-32-generic 5.0.0-32.34 failed to install/upgrade: run-
  parts: /etc/kernel/postinst.d/initramfs-tools exited with return code
  1

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

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

[Bug 390001] Leo here

2019-10-26 Thread Leo Petroski

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

Title:
  Gnome visual effects not retained after reboot

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

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

[Bug 1847892] Re: large performance regression (~30-40%) in wifi with 19.10 / 5.3 kernel

2019-10-26 Thread arQon

I expect so. I don't usually have a machine available to run as a server
though, hence the preference for rsync.

If you're concerned that the NAS might be the bottleneck, don't be.
That's a sensible point to raise, but it's GbE and saturates it wired.
(To say nothing of the months during which the rsync consistenly hit
80+).

If you think iperf might narrow the scope of where to look though, let me know 
and I'll try it next time I can dedicate a machine to it: shouldn't be more 
than a week.
(hmm - I could run one up in a VM at will, which would still have more than 
enough network performance for this, but I'm not sure I'd fully trust the 
results from that until I've got a baseline to compare against. I'll try to 
remember it when I boot the client off an older kernel).

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

Title:
  large performance regression (~30-40%) in wifi with 19.10 / 5.3 kernel

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

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

[Bug 1850014] [NEW] package grub-efi-amd64 2.02-2ubuntu8.13 failed to install/upgrade: installed grub-efi-amd64 package post-installation script subprocess returned error exit status 1

2019-10-26 Thread Muhammad Jamshaid Iqbal

Public bug reported:

I got the problem while running sudo apt-get upgrade after installing
Ubuntu 18.04.3

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: grub-efi-amd64 2.02-2ubuntu8.13
ProcVersionSignature: Ubuntu 4.15.0-1024.29-oem 4.15.18
Uname: Linux 4.15.0-1024-oem x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
Date: Sun Oct 27 08:05:06 2019
DistributionChannelDescriptor:
 # This is the distribution channel descriptor for the OEM CDs
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-bionic-amd64-20180608-47+loki-n3-v3-whl+X32
ErrorMessage: installed grub-efi-amd64 package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2019-10-27 (0 days ago)
InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1024-oem.efi.signed 
root=UUID=507aecdc-c42f-421d-bdde-05dd567a439c ro mem_sleep_default=deep 
usbcore.quirks=2386:3119:k quiet splash vt.handoff=1
Python3Details: /usr/bin/python3.6, Python 3.6.8, python3-minimal, 3.6.7-1~18.04
PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.3
 apt  1.6.12
SourcePackage: grub2
Title: package grub-efi-amd64 2.02-2ubuntu8.13 failed to install/upgrade: 
installed grub-efi-amd64 package post-installation script subprocess returned 
error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: grub2 (Ubuntu)
 Importance: Undecided
 Status: Invalid


** Tags: amd64 apport-package bionic need-duplicate-check

** Changed in: grub2 (Ubuntu)
   Status: New => Invalid

** Converted to question:
   https://answers.launchpad.net/ubuntu/+source/grub2/+question/685446

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

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

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

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

[Bug 1842173] Re: ubuntu 18.04.3 install /dev/sda1 could not boot up

2019-10-26 Thread Seiichi Nakashima

I test to install ubuntu-18.04.2 and 18.04.2 at UEFI PC using CMS.
upload syslog file


ubuntu-18.04.3-UEFI-syslog : install /dev/sda1 boot from pbr, but could not 
start up
ubuntu-18.04.2-UEFI-syslog : install /dev/sda1 boot from pbr, could start up


I found to delete kernel parameter splash, then could start up

ubunut-18.04.3-UEFI-grub-syslog : update /etc/default/grub and update-grub, 
could start up
grub : update GRUB_CMDLINE_LINUX_DEFAULT="quiet"

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

Title:
  ubuntu 18.04.3 install /dev/sda1 could not boot up

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

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

[Bug 1850012] [NEW] After log in, sound out/inputs resort to wrong devices

2019-10-26 Thread Phillip Prado

Public bug reported:

I really hope I am submitting this bug to the right place, but every
time I log in (whether after logout, reboot, etc.) the sound output and
input devices resort to my HDMI cable (monitor) and the mic on my webcam
instead of the devices I last selected.

In previous versions of Ubuntu, if I were to select my speakers as the
output device, they would remain the default until I changed it again,
even after logout/log in. Now, whenever I log in, the sound still comes
out of my speakers, but adjusting the volume does not work properly
until I go into settings > sound > and then reselect my speakers as the
output device. The volume indicator pops up on screen and it shows the
sound going up or down, but it says it is adjusting the sound to my HDMI
cable instead and it has no effect on my desktop speakers.

I really hope that makes sense.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 26 21:20:59 2019
InstallationDate: Installed on 2018-12-22 (308 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: SPDIF Out, Internal
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: None of the above
Title: [System Product Name, Realtek ALC887-VD, SPDIF Out, Internal] Playback 
problem
UpgradeStatus: Upgraded to eoan on 2019-10-14 (12 days ago)
dmi.bios.date: 09/06/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0410
dmi.board.asset.tag: Default string
dmi.board.name: Z170M-PLUS
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0410:bd09/06/2015:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ170M-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

** Affects: alsa-driver (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/1850012

Title:
  After log in, sound out/inputs resort to wrong devices

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

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

[Bug 1798596] Re: nautilus-python: Please build against Python3

2019-10-26 Thread Bug Watch Updater

** Changed in: nautilus-python (Debian)
   Status: New => 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/1798596

Title:
  nautilus-python: Please build against Python3

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

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

[Bug 1850010] [NEW] package xserver-xorg-video-nvidia-430 (not installed) failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/nvidia/xorg/nvidia_drv.so', which is also in package

2019-10-26 Thread Zachary M

Public bug reported:

Nvidia laptop support is basically nonexistent for linux. I've had
nothing but problems with Ubuntu

ProblemType: Package
DistroRelease: Ubuntu 19.10
Package: xserver-xorg-video-nvidia-430 (not installed)
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
Date: Sat Oct 26 18:56:24 2019
DpkgTerminalLog:
 Preparing to unpack 
.../xserver-xorg-video-nvidia-430_430.50-0ubuntu2_amd64.deb ...
 Unpacking xserver-xorg-video-nvidia-430 (430.50-0ubuntu2) ...
 [1mdpkg:[0m error processing archive 
/var/cache/apt/archives/xserver-xorg-video-nvidia-430_430.50-0ubuntu2_amd64.deb 
(--unpack):
  trying to overwrite '/usr/lib/x86_64-linux-gnu/nvidia/xorg/nvidia_drv.so', 
which is also in package xserver-xorg-video-nvidia-440 
440.26-0ubuntu0~gpu19.10.2
ErrorMessage: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/nvidia/xorg/nvidia_drv.so', which is also in package 
xserver-xorg-video-nvidia-440 440.26-0ubuntu0~gpu19.10.2
InstallationDate: Installed on 2019-10-26 (0 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu2
 apt  1.9.4
SourcePackage: nvidia-graphics-drivers-430
Title: package xserver-xorg-video-nvidia-430 (not installed) failed to 
install/upgrade: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/nvidia/xorg/nvidia_drv.so', which is also in package 
xserver-xorg-video-nvidia-440 440.26-0ubuntu0~gpu19.10.2
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: nvidia-graphics-drivers-430 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package eoan

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

Title:
  package xserver-xorg-video-nvidia-430 (not installed) failed to
  install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-
  gnu/nvidia/xorg/nvidia_drv.so', which is also in package xserver-xorg-
  video-nvidia-440 440.26-0ubuntu0~gpu19.10.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-430/+bug/1850010/+subscriptions

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

[Bug 1849951] Re: add hints to lshw -json so that we have pci subvendor and subdevice

Sample for hints in json output.

  "hints" : {
"icon" : "display",
"pci.class" : "0x300",
"pci.device" : "0x591B",
"pci.subdevice" : "0x802",
"pci.subvendor" : "0x1028",
"pci.vendor" : "0x8086"
  }

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

Title:
  add hints to lshw -json so that we have pci subvendor and subdevice

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

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

[Bug 1826737] Re: lshw does not list NVMe storage devices as "disk" nodes ( RedHat Bug 1695343 )

2019-10-26 Thread Stephen Boston

@Yuan - Thank you.

For precedent in this issue can we look to the transition from tape to
disk? Both are devices for persistent storage but each is in its own
class. Now with NVM we have a third type of storage device so perhaps we
should consider a new class.

lshw is a hardware listing. Classifying NVM as 'disk' is a metaphor. So
the question is how far are we comfortable introducing or extending
metaphor into a hardware listing? Can we live with that loss of
precision?

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

Title:
  lshw does not list NVMe storage devices as "disk" nodes ( RedHat Bug
  1695343 )

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

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

[Bug 1850009] [NEW] Issue with detecting new state in dhclient-enter-hooks.d/resolved

2019-10-26 Thread Ivan Brawley

Public bug reported:

After upgrading to 19.10 I noticed that resolving hostnames stopped
working.

Quick release, which package and version info:

root@caret:~# lsb_release -r
Release:19.10
root@caret:~# dpkg -S /etc/dhcp/dhclient-enter-hooks.d/resolved
systemd: /etc/dhcp/dhclient-enter-hooks.d/resolved
root@caret:~# apt-cache policy systemd
systemd:
  Installed: 242-7ubuntu3
  Candidate: 242-7ubuntu3
  Version table:
 *** 242-7ubuntu3 500
500 http://au.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
100 /var/lib/dpkg/status


The file /etc/resolv.conf was pointing to the local instance of 
systemd-resolved however there was no search line, indicating something wasn't 
quite right.

Restarting the systemd-resolved service did recreate /etc/resolv.conf
with expected search line.

After much debugging, I've worked out what was going wrong.

The dhcp hook file /etc/dhcp/dhclient-enter-hooks.d/resolved has a bug
in the resolver state change logic.

This may also impact on tickets 1805183, 1832050, 1832053 and maybe
others.

When doing the md5sum of the old and new state, the command is wrong. It
isn't sending STDOUT (and optionally STDERR) to the temp file but rather
putting the md5sum command into the background and then creating an
empty file for both states. Which obviously isn't different, so systemd-
resolved doesn't restart.

Quick diff of a working version (I'm not capturing STDERR but one can
with "2>&1")

=== BEGIN PATCH ===
*** .brk-resolved-20191027  2019-10-27 11:19:56.210069032 +1030
--- resolved2019-10-27 11:30:17.156381734 +1030
***
*** 30,36 
mkdir -p $statedir

oldstate="$(mktemp)"
!   md5sum $statedir/isc-dhcp-v4-$interface.conf 
$statedir/isc-dhcp-v6-$interface.conf &> $oldstate
if [ -n "$new_domain_name_servers" ] ; then
cat <$statedir/isc-dhcp-v4-$interface.conf
  [Resolve]
--- 30,36 
mkdir -p $statedir

oldstate="$(mktemp)"
!   md5sum $statedir/isc-dhcp-v4-$interface.conf 
$statedir/isc-dhcp-v6-$interface.conf > $oldstate
if [ -n "$new_domain_name_servers" ] ; then
cat <$statedir/isc-dhcp-v4-$interface.conf
  [Resolve]
***
*** 55,61 
fi

newstate="$(mktemp)"
!   md5sum $statedir/isc-dhcp-v4-$interface.conf 
$statedir/isc-dhcp-v6-$interface.conf &> $newstate
if ! cmp $oldstate $newstate; then
systemctl try-reload-or-restart systemd-resolved.service
fi
--- 55,61 
fi

newstate="$(mktemp)"
!   md5sum $statedir/isc-dhcp-v4-$interface.conf 
$statedir/isc-dhcp-v6-$interface.conf > $newstate
if ! cmp $oldstate $newstate; then
systemctl try-reload-or-restart systemd-resolved.service
fi
===  END  PATCH ===

Also, the script removes the script removes the $oldstate file but
doesn't remove the $newstate file.

Not sure how this made it through QA testing... But breaking DHCP client
shouldn't happen like this.

ivan.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: network-manager 1.20.4-2ubuntu2
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
Date: Sun Oct 27 11:48:33 2019
InstallationDate: Installed on 2017-04-21 (918 days ago)
InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412)
IpRoute:
 default via 172.16.1.14 dev enp0s5 
 150.101.89.32/28 dev enp0s5 scope link 
 169.254.0.0/16 dev enp0s5 scope link metric 1000 
 172.16.1.0/24 dev enp0s5 proto kernel scope link src 172.16.1.120
IwConfig:
 lono wireless extensions.
 
 enp0s5no wireless extensions.
NetworkManager.state:
 [main]
 NetworkingEnabled=false
 WirelessEnabled=true
 WWANEnabled=true
ProcEnviron:
 LANGUAGE=en_AU:en
 TERM=vt100
 PATH=(custom, no user)
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
RfKill:
 
SourcePackage: network-manager
UpgradeStatus: Upgraded to eoan on 2019-10-26 (0 days ago)
nmcli-con:
 
nmcli-dev:
 DEVICE  TYPE  STATE  IP4-CONNECTIVITY  IP6-CONNECTIVITY  DBUS-PATH 
 CONNECTION  CON-UUID  CON-PATH 
 enp0s5  ethernet  unmanaged  unknown   unknown   
/org/freedesktop/NetworkManager/Devices/2  --  ----   
 lo  loopback  unmanaged  unknown   unknown   
/org/freedesktop/NetworkManager/Devices/1  --  ----
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.20.4   connected  started  unknown   disabledenabled  
enabled  enabled  enabled

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


** Tags: amd64 apport-bug eoan

** Package changed: network-man

[Bug 1849951] Re: add hints to lshw -json so that we have pci subvendor and subdevice

upstream pull request: https://github.com/lyonel/lshw/pull/49

** Tags added: 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/1849951

Title:
  add hints to lshw -json so that we have pci subvendor and subdevice

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

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

[Bug 1843063] Re: lshw -json output invalid in Eoan

per my test, this fix this bug: https://github.com/lyonel/lshw/pull/48

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

Title:
  lshw -json output invalid in Eoan

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

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

[Bug 1843063] Re: lshw -json output invalid in Eoan

command that can do testing: lshw -json 2>/dev/null | python -m
json.tool

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

Title:
  lshw -json output invalid in Eoan

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

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

[Bug 1724876] Re: libreoffice soffice.bin using 100% cpu

2019-10-26 Thread Gabriel Staples

Marcus, here's all the extensions I have installed.

Also, I just downgraded my LibreOffice installation from 6.3.2 to 6.3.1 then to 
6.2.8. 
6.3.2 and 6.3.1 both were buggy, but 6.2.8 seems to work perfectly now and 
actually makes my entire computer feel like I just bought a new computer! All 
of a sudden it feels totally usable again! 

Here's my bug report I just made on this. It may be related:
https://bugs.documentfoundation.org/show_bug.cgi?id=128406.

See also this (appears to be the *exact* same problem as my bug report
above): https://ask.libreoffice.org/en/question/208712/calc-6312-macro-
button-problem/

** Bug watch added: Document Foundation Bugzilla #128406
   https://bugs.documentfoundation.org/show_bug.cgi?id=128406

** Attachment added: "Selection_021.png"
   
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1724876/+attachment/5300482/+files/Selection_021.png

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

Title:
  libreoffice soffice.bin using 100% cpu

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

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

[Bug 1724876] Re: libreoffice soffice.bin using 100% cpu

2019-10-26 Thread Gabriel Staples

Also, here was my work-around to try to fix the 100% cpu soffice.bin
bug: https://serverfault.com/questions/953809/soffice-bin-high-cpu-
usage/986039#986039.

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

Title:
  libreoffice soffice.bin using 100% cpu

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

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

[Bug 1826737] Re: lshw does not list NVMe storage devices as "disk" nodes ( RedHat Bug 1695343 )

@Stephane, I am open to it.

Here are all class current supported:

system, bridge, memory, processor, address, storage, disk, tape,
bus, network, display, input, printer, multimedia, communication,
power, volume, generic

Per quick check, NVME / SATA controller are belongs to storage class.
Agree NVME is not a 'disk' becuase nothing spins, however it probably
the best place it goes given current on hwNode only have one class.

Maybe https://www.intel.com/content/www/us/en/products/memory-storage
/optane-dc-persistent-memory.html is something really harder to decide
whether we should put it in memory or storage.

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

Title:
  lshw does not list NVMe storage devices as "disk" nodes ( RedHat Bug
  1695343 )

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

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

[Bug 1849904] Re: lxd init assumes ipv6 is available

2019-10-26 Thread Stéphane Graber via ubuntu-bugs

This is a non-standard configuration (disabling IPv6) and actually not
recommended for any environment these days.

The tool does mention the availability of "none" so, someone in such an
environment should be able to make the connection and set to "none".

"lxd init" cannot actually check whether the machine will have IPv6 or
not as this is all done over the remote LXD API and IPv6 availability
isn't something that can be queried (and it's so niche that it doesn't
really make any sense to add).

The error comes from "lxd init" having told LXD to set "ipv6.address" to
"auto", "auto" here means select an IPv6 subnet automatically, which it
did and then failed to apply due to the disabled kernel support.

We can add a check for the presence of "/proc/sys/net/ipv6" and fail
with a nicer error, but this particular case will still fail and I don't
see us changing that.

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

Title:
  lxd init assumes ipv6 is available

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

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

[Bug 1849904] Re: lxd init assumes ipv6 is available

2019-10-26 Thread Stéphane Graber via ubuntu-bugs

https://github.com/lxc/lxd/pull/6354

Closing bug as we don't normally track issues on Launchpad and there
won't be any auto-closing on release.

** Changed in: lxd (Ubuntu)
   Status: New => Fix Released

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

Title:
  lxd init assumes ipv6 is available

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

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

[Bug 1793965] Re: Firmware update daemon resets displays connected to Dell TB16 dock soon after every first login

2019-10-26 Thread Mario Limonciello

Fixed in 1.3.2-5 in focal.

** Changed in: fwupd (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/1793965

Title:
  Firmware update daemon resets displays connected to Dell TB16 dock
  soon after every first login

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

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

[Bug 1849032] Re: xenial/linux-hwe-edge: 4.15.0-67.76~16.04.1 -proposed tracker

** 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: 1849854
  packages:
meta: linux-meta-hwe-edge
  phase: Testing
  phase-changed: Thursday, 24. October 2019 23:45 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
-   security-signoff: Pending -- waiting for signoff
+   security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  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/1849032

Title:
  xenial/linux-hwe-edge: 4.15.0-67.76~16.04.1 -proposed tracker

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

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

[Bug 1850005] [NEW] Global Application Menu applet English description issue

2019-10-26 Thread Lindsay

Public bug reported:

This is right up there with "All your base are belong to us"

Distribution: Ubuntu 18.04.3 LTS
Package: mate-applet-appmenu 0.6.94+repack1

--- org.vala-panel.appmenu.mate-panel-applet2018-03-29 15:00:01.0 
-0500
+++ /root/tmp/org.vala-panel.appmenu.mate-panel-applet  2019-10-26 
17:51:21.816968077 -0500
@@ -14,7 +14,7 @@
 Name[ru]=Глобальное меню
 Name[zh_CN]=全局菜单
 Name=Global Application Menu
-Description=All menus will hosts here
+Description=Application menus will appear on panel
 Icon[es]=aplicaciones-sistema
 Icon[ru]=applications-system
 Icon[zh_CN]=\s

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: mate-applet-appmenu 0.6.94+repack1-1
ProcVersionSignature: Ubuntu 4.15.0-66.75-generic 4.15.18
Uname: Linux 4.15.0-66-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CurrentDesktop: MATE
Date: Sat Oct 26 18:02:59 2019
InstallationDate: Installed on 2018-02-14 (619 days ago)
InstallationMedia: Ubuntu-MATE 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: vala-panel-appmenu
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: vala-panel-appmenu (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic third-party-packages

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

Title:
  Global Application Menu applet English description issue

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vala-panel-appmenu/+bug/1850005/+subscriptions

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

[Bug 1826737] Re: lshw does not list NVMe storage devices as "disk" nodes ( RedHat Bug 1695343 )

2019-10-26 Thread Stephen Boston

I don't recall posting this bug that I don't think is a bug. NVM is not
a disk so why should it be reported as a disk?

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

Title:
  lshw does not list NVMe storage devices as "disk" nodes ( RedHat Bug
  1695343 )

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

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

[Bug 1850003] [NEW] /etc/grub.d/10_linux_zfs doesn't skip non-linux zpools

2019-10-26 Thread Benjamin Gentil

Public bug reported:

# 1. Symptoms: `update-grub` fails when trying to access an os-release
file

root@x250:/home/benjamin# update-grub
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/init-select.cfg'
Generating grub configuration file ...
/etc/grub.d/10_linux_zfs: 338: .: Can't open 
/tmp/zfsmnt.Ejuktn/etc/os-release
done

# 2. Cause: 10_linux_zfs is trying to access /etc/os-release in all zpool, even 
when the system is not Linux based
+ machine_id=rpool/ROOT/openindiana
+ . /tmp/zfsmnt.AC9sAy/etc/os-release
/etc/grub.d/10_linux_zfs: 339: .: Can't open 
/tmp/zfsmnt.AC9sAy/etc/os-release
+ pretty_name=
+ boot_list=\n
+ boot_list=
+ on_exit
+ zpool export rpool
+ mountpoint -q /tmp/zfsmnt.AC9sAy
+ true
+ rmdir /tmp/zfsmnt.AC9sAy
+ rm -rf /tmp/zfstmp.lEMWy3
+ exit 0
done

# 3. Quick fix (for /etc/os-release)

in /etc/grub.d/10_linux_zfs:321, replace:
if [ -z  "${etc_dir}" ]; then
by:
if [ -z  "${etc_dir}" ] || [ ! -f "${etc_dir}/os-release" ]; then

then when the file is not found, the zpool is skipped
root@x250:/home/benjamin# update-grub
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/init-select.cfg'
Generating grub configuration file ...
Warning: Ignoring rpool/ROOT/openindiana
Warning: Ignoring rpool/ROOT/openindiana-1
Warning: Ignoring rpool/ROOT/openindiana-1@install
Warning: Ignoring rpool/ROOT/openindiana-1@2018-08-24-23:15:22
Found linux image: vmlinuz-5.0.0-32-generic in x250/ROOT/ubuntu
Found initrd image: initrd.img-5.0.0-32-generic in x250/ROOT/ubuntu
Found linux image: vmlinuz-5.3.0-19-generic in x250/ROOT/ubuntu
Found initrd image: initrd.img-5.3.0-19-generic in x250/ROOT/ubuntu
Found linux image: vmlinuz-5.0.0-32-generic in x250/ROOT/ubuntu@install
Found initrd image: initrd.img-5.0.0-32-generic in 
x250/ROOT/ubuntu@install
Found linux image: vmlinuz-5.3.0-19-generic in x250/ROOT/ubuntu@install
Found initrd image: initrd.img-5.3.0-19-generic in 
x250/ROOT/ubuntu@install
done

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: grub-common 2.04-1ubuntu12
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CurrentDesktop: XFCE
Date: Sun Oct 27 00:30:31 2019
SourcePackage: grub2
UpgradeStatus: Upgraded to eoan on 2019-10-26 (0 days ago)
modified.conffile..etc.grub.d.10_linux_zfs: [modified]
mtime.conffile..etc.grub.d.10_linux_zfs: 2019-10-27T00:09:53.228144

** Affects: grub2 (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/1850003

Title:
  /etc/grub.d/10_linux_zfs doesn't skip non-linux zpools

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

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

[Bug 1850002] [NEW] /etc/grub.d/10_linux_zfs fail when zpool import output to stdout

2019-10-26 Thread Benjamin Gentil

Public bug reported:

## 1. Symptoms, `update-grub` fails with "no such pool"

### output
benjamin@x250:~$ sudo update-grub
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/init-select.cfg'
Generating grub configuration file ...
cannot open 'This': no such pool

### debug output
benjamin@x250:~$ sudo update-grub
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/init-select.cfg'
Generating grub configuration file ...
+ set -u
+ which zfs
+ 
+ imported_pools=
+ mktemp -d /tmp/zfsmnt.XX
+ MNTDIR=/tmp/zfsmnt.bunqET
+ mktemp -d /tmp/zfstmp.XX
+ ZFSTMP=/tmp/zfstmp.X21h0R
+ RC=0
+ trap on_exit EXIT INT QUIT ABRT PIPE TERM
+ GRUB_LINUX_ZFS_TEST=
+ import_pools
+ zpool list
+ awk {if (NR>1) print $1}
+ local initial_pools=x250
+ local all_pools=
+ local imported_pools=
+ zpool import -f -a -o cachefile=none -N
+ imported_pools=This pool uses the following feature(s) not supported 
by this system:
com.delphix:spacemap_v2 (Space maps representing large segments 
are more efficient.)
org.zfsonlinux:project_quota (space/object accounting based on 
project ID.)
All unsupported features are only required for writing to the pool.
The pool can be imported using '-o readonly=on'.
This pool uses the following feature(s) not supported by this system:
com.delphix:spacemap_v2 (Space maps representing large segments 
are more efficient.)
All unsupported features are only required for writing to the pool.
The pool can be imported using '-o readonly=on'.
+ on_exit
+ zpool export This
cannot open 'This': no such pool

## 2. Cause
Only the stderr of `zpool import -f -a -o cachefile=none -N` is sent to 
/dev/null so when the 
command outputs on stdout everything ends up in the `imported_pools` 
variable

## 3. Quick fix
in /etc/grub.d/10_linux_zfs:67, replace:
zpool import -f -a -o cachefile=none -N 2>/dev/null
by
zpool import -f -a -o cachefile=none -N >/dev/null 2>&1

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: grub-common 2.04-1ubuntu12
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CurrentDesktop: XFCE
Date: Sat Oct 26 17:17:20 2019
SourcePackage: grub2
UpgradeStatus: Upgraded to eoan on 2019-10-26 (0 days ago)
modified.conffile..etc.grub.d.10_linux_zfs: [modified]
mtime.conffile..etc.grub.d.10_linux_zfs: 2019-10-26T17:14:38.665289

** Affects: grub2 (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/1850002

Title:
  /etc/grub.d/10_linux_zfs fail when zpool import output to stdout

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

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

[Bug 1849720] Re: Running VM with Virtual NIC Crashes Host OS

2019-10-26 Thread Robert Strube

Here's the main bug report I was thinking about:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1841040

The kernel module is 'r8169'.

Brian perhaps you could do an 'lsmod | grep r8169' to see if that module
is loaded for you as well?

If it is, perhaps you could try to blacklist the module by adding
'r8169' to the end of your '/etc/modprobe.d/blacklist.conf' file and
rebooting?

Of course if you're using a wired connection this would cause problems,
but if you're like me and are using a wireless connection, perhaps this
will solve the issue?

It seems like that ethernet card is notoriously buggy.

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

Title:
  Running VM with Virtual NIC Crashes Host OS

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

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

[Bug 1841953] Re: Bionic ⋅ SuperTuxKart ⋅ Flickering shadows ⋅ Haswell i915

2019-10-26 Thread Coeur Noir via ubuntu-bugs

As I feared from trying with Ubuntu 19.10, using
ppa:ubuntu-x-swat/updates on 18.04 did not fix the flickering-shadows
problem.

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

Title:
  Bionic ⋅ SuperTuxKart ⋅ Flickering shadows ⋅ Haswell i915

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

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

[Bug 1850001] [NEW] nautilus hangs on file delete

2019-10-26 Thread peterzay

Public bug reported:

Nautilus hangs when deleting a file.  The file does not get deleted.
This applies to the DELETE key, the SHIFT+DELETE keys, and the RIGHT-
CLICK attempt at deleting.

This is reproducible in this boot session.

This has never happened since the install of the OS.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: nautilus 1:3.34.1-1ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 26 18:12:36 2019
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
 
InstallationDate: Installed on 2019-10-20 (6 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191014)
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)
usr_lib_nautilus:

** Affects: nautilus (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/1850001

Title:
  nautilus hangs on file delete

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

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

[Bug 1849720] Re: Running VM with Virtual NIC Crashes Host OS

2019-10-26 Thread Robert Strube

One thing I thought of, is that both Brian and I have System76
computers, so perhaps there's a hardware issue specifically with our
computers? Brian, I have a Darter Pro 2019, what model do you have?

Just to clarify I've tried both Pop_OS 19.10 and Ubuntu 19.10 and the
issue is present on both installs.  Perhaps it's an issue with the
networking hardware on our systems in conjunction with the new 5.3
kernel?

I have a Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
Controller (rev 12) as my ethernet controller.  I had some really
strange issues with the ethernet with Ubuntu 19.04, in fact you can see
some posts about this hardware here:

https://ubuntu-mate.community/t/19-04-ethernet-wired-connection-refuses-
to-connect-when-plugged-in-before-boot/19333/2

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1752772

My issue was that if I had the ethernet cable plugged in at boot, the
connection wouldn't work.  I would have to start the system, and plug
the cable in afterwards.  Even then it wouldn't always work correctly.

My point is that perhaps there's something up very low level with this
particular hardware? I wonder if we blacklist the ethernet kernel module
we could run the VM without issue?

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

Title:
  Running VM with Virtual NIC Crashes Host OS

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

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

[Bug 1849025] Re: xenial/linux-azure-edge: 4.15.0-1062.67 -proposed tracker

** 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: 1849027
  packages:
meta: linux-meta-azure-edge
  phase: Testing
  phase-changed: Thursday, 24. October 2019 22:12 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
-   security-signoff: Pending -- waiting for signoff
+   security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  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/1849025

Title:
  xenial/linux-azure-edge: 4.15.0-1062.67 -proposed tracker

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

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

[Bug 1693342] Re: package out of date

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: highlight (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/1693342

Title:
  package out of date

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

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

[Bug 1843591] Re: Security issues related to php7.2.19

Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: nginx (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/1843591

Title:
  Security issues related to php7.2.19

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

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

[Bug 1843591] Re: Security issues related to php7.2.19

2019-10-26 Thread Thomas Ward

This has to do with the NGINX configs used by Nextcloud, without
evidence that this directly affects NGINX default configurations,
there's nothing for us to do here for NGINX.

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

Title:
  Security issues related to php7.2.19

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

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

[Bug 1843591] Re: Security issues related to php7.2.19

2019-10-26 Thread Thomas Ward

This bug has *nothing* to do with NGINX, and everything to do with PHP
specifically.  There is no embedded PHP in NGINX.  Marking as "Invalid"
against NGINX, this needs to be fixed in PHP *only* and not NGINX.

** Project changed: nginx => nginx (Ubuntu)

** Changed in: nginx (Ubuntu)
   Status: New => Invalid

** Also affects: nginx
   Importance: Undecided
   Status: New

** Changed in: nginx
   Status: New => Invalid

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

Title:
  Security issues related to php7.2.19

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

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

[Bug 1841953] Re: Bionic ⋅ SuperTuxKart ⋅ Flickering shadows ⋅ Haswell i915

2019-10-26 Thread Coeur Noir via ubuntu-bugs

I'll try that and report, thanks.

Meanwhile I have tried with Ubuntu ( default ) 19.10 and same problem…

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

Title:
  Bionic ⋅ SuperTuxKart ⋅ Flickering shadows ⋅ Haswell i915

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

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

[Bug 1849720] Re: Running VM with Virtual NIC Crashes Host OS

2019-10-26 Thread Robert Strube

Hi Christian,

I can tell you what was happening for me.

I run all my VMs through virt-manager, so I first open up virt-manager
and then start my Windows Server 2019 VM.  The VM boots fine and I get
to the login screen where I need to send a CTRL+ALT+DELETE to login.  A
couple extra seconds after reaching the login screen my entire hos
system hangs.  By this I mean I can no longer move the mouse in the
Gnome DE, the screen no longer updates (one time I had a browser window
open with some animated content), I can't switch to a virtual terminal
(e.g. using CTRL+ALT+FX), nothing.

It makes no difference if I quickly hit CTRL+ALT+DELETE and start to
type my name in, or if I just start the VM and wait, it always freezes
my entire system, everything is unresponsive, and the only way to
restart is to do a hard power off / power on.

The reason I determined it was the networking that caused the problem is
because after one of these hard power off / power on cycles, the VM
asked me if I wanted to boot into safe mode.  I chose this option and
the same thing happened.  The next time I chose safe mode without a
network connection and everything worked fine.  I could browse files on
the VM, start programs, etc.

After that I start messing with the configuration for my VM, and
specifically removed the network hardware, the VM started fine - it was
then that I realized the networking causes the problem.

I also tried with a clean ISO install to eliminate the possibility of
the qemu guest agent causing the issues.  I can run through the entire
Windows Server 2019 installation process, but once I reboot after I've
completed the installation, I get the same hard hang where the host
system is entirely unresponsive.

One thing I thought of is providing you access to the Windows Server
2019 ISO, this wouldn't violate any license agreements as you can
install it without needing to put a key in (trial mode).

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

Title:
  Running VM with Virtual NIC Crashes Host OS

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

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

[Bug 1849998] [NEW] Plasma-Wayland sometimes getting random black screen.

2019-10-26 Thread DR. VIMAL HURRY

Public bug reported:

Plasma-Wayland is working well on my 4K screen & I'm getting 60 FPS 😇
But I'm still sometimes getting random black screens when I try to
login. Any ideas why? I'm using Kubuntu 19.10 on an AMD Ryzen5 2400G
APU.

** Affects: plasma
 Importance: Undecided
 Status: New

** Affects: wayland
 Importance: Undecided
 Status: New

** Affects: ubuntu
 Importance: Undecided
 Status: New


** Tags: 2400g 4k 60fps kde kubuntu ryzen5 wayland

** Also affects: wayland
   Importance: Undecided
   Status: New

** Also affects: plasma
   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/1849998

Title:
  Plasma-Wayland  sometimes getting random black screen.

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

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

[Bug 1849930] Re: Additional VPN Breaks First VPN

This doesn't fix the underlying bug, but I was able to find a workaround that 
repairs the corruption caused by the bug. See here:
https://askubuntu.com/a/1184070/256054

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

Title:
  Additional VPN Breaks First VPN

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1849930/+subscriptions

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

[Bug 1849996] Re: package lirc 0.10.1-6 failed to install/upgrade: installed lirc package post-installati│······························································································

** Tags removed: need-duplicate-check

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

Title:
  package lirc 0.10.1-6 failed to install/upgrade: installed lirc
  package post-
  
installati│··

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

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

[Bug 1754671] Re: Full-tunnel VPN DNS leakage regression

2019-10-26 Thread Eric Desrochers

The netplan.io (arm64) autopkgtest failure (due to timeout) has been retried 
today, it passed:
http://autopkgtest.ubuntu.com/packages/n/netplan.io/bionic/arm64

No more failure reported in pending sru page.

- Eric

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

Title:
  Full-tunnel VPN DNS leakage regression

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1754671/+subscriptions

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

[Bug 1849996] [NEW] package lirc 0.10.1-6 failed to install/upgrade: installed lirc package post-installati│····························································································

2019-10-26 Thread Gustin Johnson via ubuntu-bugs

Public bug reported:

Standard do-release-upgrade

ProblemType: Package
DistroRelease: Ubuntu 19.10
Package: lirc 0.10.1-6
ProcVersionSignature: Ubuntu 5.0.0-32.34-generic 5.0.21
Uname: Linux 5.0.0-32-generic x86_64
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
Date: Sat Oct 26 15:12:22 2019
ErrorMessage: installed lirc package post-installation script subprocess 
returned error exit status 1
Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1
PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1
RelatedPackageVersions:
 dpkg 1.19.7ubuntu2
 apt  1.9.4
SourcePackage: lirc
Title: package lirc 0.10.1-6 failed to install/upgrade: installed lirc package 
post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to eoan on 2019-10-26 (0 days ago)

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


** Tags: amd64 apport-package eoan

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

Title:
  package lirc 0.10.1-6 failed to install/upgrade: installed lirc
  package post-
  
installati│··

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

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

[Bug 1843591] Re: Security issues related to php7.2.19

2019-10-26 Thread Thomas Kopp

With php7.2-fpm Module

** Also affects: nginx
   Importance: Undecided
   Status: New

** Bug watch added: bugs.php.net/ #78599
   http://bugs.php.net/bug.php?id=78599

** Also affects: php-fpm via
   http://bugs.php.net/bug.php?id=78599
   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/1843591

Title:
  Security issues related to php7.2.19

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

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

[Bug 1849993] Status changed to Confirmed

This change was made by a bot.

** Changed in: linux (Ubuntu)
   Status: New => Confirmed

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

Title:
  DualShock 4 over Bluetooth does not work

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

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

[Bug 1848852] Re: Counter-Strike Global Offensive freezes in gnome-shell

2019-10-26 Thread uriel

I hope someone can fix this, is very annoying.

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

Title:
  Counter-Strike Global Offensive freezes in gnome-shell

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

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

[Bug 1849374] Re: packages built for python3.8 with disabled tests, for a first binary

2019-10-26 Thread Matthias Klose

python-tornado has tests enabled again

** Changed in: python-tornado (Ubuntu)
   Status: New => Fix Released

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

Title:
  packages built for python3.8 with disabled tests, for a first binary

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

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

[Bug 1849930] Re: Additional VPN Breaks First VPN

** Description changed:

  When I add only one L2TP VPN profile to gnome-control-center's Network >
  VPN settings, it works fine.
  
  However, if I add a 2nd L2TP VPN, the 2nd L2TP VPN, not only doesn't
  work, but it corrupts the first L2TP VPN so that it too stops working.
  
  Furthermore, if I remove 2nd L2TP VPN profile (that corrupted the first
  L2TP VPN) this does NOT repair the corruption to the first L2TP VPN, it
  remains corrupted.
  
  Additionally, removing all VPN profiles and re-adding the first one
  back, doesn't repair the corruption. Rebooting and adding them back
  doesn't work either.
  
  The only thing that works, that I've found, is completely reinstalling
  Ubuntu 19.10. Please advise better workarounds than reinstalling.
+ 
+ In case it matters, these additional packages were also required for my
+ initial VPN setup:
+ 
+ sudo apt-get install -y network-manager-l2tp network-manager-l2tp-gnome
+ strongswan
  
  Here's what's in the syslog on a failed VPN Connection attempt:
  
  Oct 26 02:58:35 workstation5 NetworkManager[1241]:   [1572076715.5632] 
audit: op="connection-activate" uuid="1942cf95-93b1-4e74-a44a-947a46bffb5a" 
name="L2TP VPN1" pid=3531 uid=1000 result="success"
  Oct 26 02:58:35 workstation5 NetworkManager[1241]:   [1572076715.5702] 
vpn-connection[0x5642f421c750,1932cf95-91b1-4e85-a44a-498a56befb5a,"L2TP 
VPN1",0]: Started the VPN service, PID 7273
  Oct 26 02:58:35 workstation5 NetworkManager[1241]:   [1572076715.5747] 
vpn-connection[0x5642f421c750,1932cf95-91b1-4e85-a44a-498a56befb5a,"L2TP 
VPN1",0]: Saw the service appear; activating connection
  Oct 26 02:58:35 workstation5 NetworkManager[1241]:   [1572076715.6566] 
vpn-connection[0x5642f421c750,1932cf95-91b1-4e85-a44a-498a56befb5a,"L2TP 
VPN1",0]: VPN connection: (ConnectInteractive) reply received
  Oct 26 02:58:35 workstation5 NetworkManager[1241]: Stopping strongSwan IPsec 
failed: starter is not running
  Oct 26 02:58:37 workstation5 NetworkManager[1241]: Starting strongSwan 5.7.2 
IPsec [starter]...
  Oct 26 02:58:37 workstation5 NetworkManager[1241]: Loading config setup
  Oct 26 02:58:37 workstation5 NetworkManager[1241]: Loading conn 
'1942cf95-93b1-4e74-a44a-947a46bffb5a'
  Oct 26 02:58:37 workstation5 NetworkManager[1241]: found netkey IPsec stack
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: Stopping strongSwan 
IPsec...
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: initiating Main Mode 
IKE_SA 1942cf95-93b1-4e74-a44a-947a46bffb5a[1] to 49.230.24.121
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: generating ID_PROT request 
0 [ SA V V V V V ]
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending packet: from 
192.168.1.2[500] to 49.230.24.121[500] (236 bytes)
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: received packet: from 
49.230.24.121[500] to 192.168.1.2[500] (156 bytes)
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: parsed ID_PROT response 0 
[ SA V V V V ]
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: received XAuth vendor ID
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: received DPD vendor ID
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: received FRAGMENTATION 
vendor ID
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: received NAT-T (RFC 3947) 
vendor ID
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: selected proposal: 
IKE:3DES_CBC/HMAC_SHA1_96/PRF_HMAC_SHA1/MODP_1024
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: generating ID_PROT request 
0 [ KE No NAT-D NAT-D ]
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending packet: from 
192.168.1.2[500] to 49.230.24.121[500] (244 bytes)
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: received packet: from 
49.230.24.121[500] to 192.168.1.2[500] (244 bytes)
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: parsed ID_PROT response 0 
[ KE No NAT-D NAT-D ]
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: local host is behind NAT, 
sending keep alives
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: generating ID_PROT request 
0 [ ID HASH ]
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending packet: from 
192.168.1.2[4500] to 49.230.24.121[4500] (68 bytes)
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: received packet: from 
49.230.24.121[500] to 192.168.1.2[500] (68 bytes)
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: invalid HASH_V1 payload 
length, decryption failed?
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: could not decrypt payloads
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: message parsing failed
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: ignore malformed 
INFORMATIONAL request
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: INFORMATIONAL_V1 request 
with message ID 3016741680 processing failed
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending retransmit 1 of 
request message ID 0, seq 3
  Oct 26 02:58:48 workstation5 NetworkManager[1241]: sending packet: from 
192.168.1.2

[Bug 1849993] [NEW] DualShock 4 over Bluetooth does not work

2019-10-26 Thread Lastique

Public bug reported:

Connecting Sony DualShock 4 over Bluetooth does not work on kernel 5.3.
After pressing the PS button on the gamepad, the LED blinks for a few
seconds while connecting and then stays constantly lit when Bluetooth
connection is established. However, while "connected", lsusb doesn't
show the gamepad and it doesn't work in games.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: linux-image-lowlatency 5.3.0.19.22
ProcVersionSignature: Ubuntu 5.3.0-19.20-lowlatency 5.3.1
Uname: Linux 5.3.0-19-lowlatency x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC3:  lastique   2092 F pulseaudio
 /dev/snd/controlC0:  lastique   2092 F pulseaudio
 /dev/snd/controlC2:  lastique   2092 F pulseaudio
 /dev/snd/controlC1:  lastique   2092 F pulseaudio
CurrentDesktop: KDE
Date: Sat Oct 26 23:55:45 2019
HibernationDevice:
 # Prevents "gave up waiting for suspend/resume device" timeout on boot
 RESUME=none
InstallationDate: Installed on 2015-05-01 (1639 days ago)
InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
MachineType: System manufacturer System Product Name
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-19-lowlatency 
root=UUID=a03f1835-52f9-4409-9da7-fe45770637ae ro quiet splash nomdmonddf 
nomdmonisw vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-5.3.0-19-lowlatency N/A
 linux-backports-modules-5.3.0-19-lowlatency  N/A
 linux-firmware   1.183.1
RfKill:
 0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to eoan on 2019-10-26 (0 days ago)
dmi.bios.date: 11/09/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3603
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8Z68-V PRO
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3603:bd11/09/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

** Affects: linux (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/1849993

Title:
  DualShock 4 over Bluetooth does not work

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

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

[Bug 1849993] Re: DualShock 4 over Bluetooth does not work

2019-10-26 Thread Lastique

The problem exists in the mainline kernel 5.3.7 and does NOT exist with
5.2.21. I cannot test 5.4-rc4 because Nvidia driver doesn't compile for
this kernel.

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

Title:
  DualShock 4 over Bluetooth does not work

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

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

[Bug 1849992] Re: Autokey-GTK : Can't see typing cursor when using Gnome dark themes

** Also affects: gnome-tweaks
   Importance: Undecided
   Status: New

** Summary changed:

- Autokey-GTK : Can't see typing cursor when using Gnome dark themes
+ Autokey-GTK : Can't see typing cursor when using Gnome-Tweaks dark themes

** Description changed:

- Autokey-gtk's phrase editor does not show a typing cursor when you're
- running Ubuntu 19.10 with dark themes.
+ Autokey-gtk's phrase editor (and script editor) does not show a typing-
+ cursor when you're running Ubuntu 19.10 with dark themes.
  
  Steps to reproduce:
  1) Launch GNOME-TWEAKs:
  sudo apt install gnome-tweaks ; gnome-tweaks &
  
  2) Click "Appearance".
  
  3) Under Themes > Applications, change it to either Adwaita-dark or
  Yaru-dark
  
  4) Launch Autokey-gtk
  sudo apt install autokey-gtk ; autokey-gtk
  
  5) In the left pane of Autokey-gtk, select any phrase or script (or
  create a new phrase or script) and then left-click your mouse at any
  point within the text.
  
  Expect Result: You should see a typing cursor that allows you to use
  your arrow keys to navigate to any location within the text shown in the
  editor.
  
  Actual Result: The typing cursor is completely invisible.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: autokey-gtk 0.90.4-1.1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 26 15:28:37 2019
  InstallationDate: Installed on 2019-10-19 (7 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: autokey
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

- Autokey-gtk's phrase editor (and script editor) does not show a typing-
- cursor when you're running Ubuntu 19.10 with dark themes.
+ Autokey-gtk's phrase editor (and script editor too) does not show a
+ typing-cursor when you're running Ubuntu 19.10 with dark themes.
  
  Steps to reproduce:
  1) Launch GNOME-TWEAKs:
  sudo apt install gnome-tweaks ; gnome-tweaks &
  
  2) Click "Appearance".
  
  3) Under Themes > Applications, change it to either Adwaita-dark or
  Yaru-dark
  
  4) Launch Autokey-gtk
  sudo apt install autokey-gtk ; autokey-gtk
  
  5) In the left pane of Autokey-gtk, select any phrase or script (or
  create a new phrase or script) and then left-click your mouse at any
  point within the text.
  
  Expect Result: You should see a typing cursor that allows you to use
  your arrow keys to navigate to any location within the text shown in the
  editor.
  
  Actual Result: The typing cursor is completely invisible.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: autokey-gtk 0.90.4-1.1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 26 15:28:37 2019
  InstallationDate: Installed on 2019-10-19 (7 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: autokey
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  Autokey-gtk's phrase editor (and script editor too) does not show a
  typing-cursor when you're running Ubuntu 19.10 with dark themes.
  
  Steps to reproduce:
  1) Launch GNOME-TWEAKs:
  sudo apt install gnome-tweaks ; gnome-tweaks &
  
  2) Click "Appearance".
  
  3) Under Themes > Applications, change it to either Adwaita-dark or
- Yaru-dark
+ Yaru-dark.
  
  4) Launch Autokey-gtk
  sudo apt install autokey-gtk ; autokey-gtk
  
  5) In the left pane of Autokey-gtk, select any phrase or script (or
  create a new phrase or script) and then left-click your mouse at any
  point within the text.
  
  Expect Result: You should see a typing cursor that allows you to use
  your arrow keys to navigate to any location within the text shown in the
  editor.
  
  Actual Result: The typing cursor is completely invisible.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: autokey-gtk 0.90.4-1.1
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 26 15:28:37 2019
  InstallationDate: Installed on 2019-10

[Bug 1818547] Re: hid-sensor-hub spamming dmesg in 4.20

2019-10-26 Thread Mark Borgerding

This is blasting 3.45 million messages into my dmesg per day ( at least
no longer in syslog thanks to @incognito666 )


Dell XPS 13 7390 2-in-1 Ubuntu 19.10 kernel 5.3.0-19-generic

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

Title:
  hid-sensor-hub spamming dmesg in 4.20

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

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

[Bug 1849992] [NEW] Autokey-GTK : Can't see typing cursor when using Gnome-Tweaks dark themes

Public bug reported:

Autokey-gtk's phrase editor does not show a typing cursor when you're
running Ubuntu 19.10 with dark themes.

Steps to reproduce:
1) Launch GNOME-TWEAKs:
sudo apt install gnome-tweaks ; gnome-tweaks &

2) Click "Appearance".

3) Under Themes > Applications, change it to either Adwaita-dark or
Yaru-dark

4) Launch Autokey-gtk
sudo apt install autokey-gtk ; autokey-gtk

5) In the left pane of Autokey-gtk, select any phrase or script (or
create a new phrase or script) and then left-click your mouse at any
point within the text.

Expect Result: You should see a typing cursor that allows you to use
your arrow keys to navigate to any location within the text shown in the
editor.

Actual Result: The typing cursor is completely invisible.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: autokey-gtk 0.90.4-1.1
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat Oct 26 15:28:37 2019
InstallationDate: Installed on 2019-10-19 (7 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: autokey
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-tweaks
 Importance: Undecided
 Status: New

** Affects: autokey (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/1849992

Title:
  Autokey-GTK : Can't see typing cursor when using Gnome-Tweaks dark
  themes

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-tweaks/+bug/1849992/+subscriptions

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

[Bug 1849991] [NEW] Missing dependency : python-pkg-resources

2019-10-26 Thread Bernardo Bahia Monteiro

Public bug reported:

Traceback (most recent call last):
  File "/usr/bin/maybe", line 5, in 
from pkg_resources import load_entry_point
ImportError: No module named pkg_resources

System details
--

Description:Ubuntu 18.04.3 LTS
Release:18.04

maybe:
  Installed: 0.4.0-1
  Candidate: 0.4.0-1
  Version table:
 *** 0.4.0-1 500
500 http://us.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
100 /var/lib/dpkg/status

** Affects: maybe (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/1849991

Title:
  Missing dependency : python-pkg-resources

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

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

[Bug 1743592] Re: NGINX fails to start/install/upgrade if IPv6 is completely disabled.

2019-10-26 Thread Eric Desrochers

** Description changed:

  [IMPACT]
  
  With current default vhost listening on IPV6, nginx won't start on fully
  IPV6 disabled system, expecting to connect to a IPV6 socket on port 80.
  
  # nginx -t
  nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
  ==> nginx: [emerg] socket() [::]:80 failed (97: Address family not supported 
by protocol)
  nginx: configuration file /etc/nginx/nginx.conf test failed
  
  # cat /etc/nginx/sites-enabled/default
  ..
  server {
   listen 80 default_server;
  ==> listen [::]:80 default_server;
  ..
  
  [TEST CASE]
  * Disable ipv6
    # cat /proc/cmdline
     ipv6.disable=1
  
  * Reboot for the kernel parameter to be taken into account.
  
  * Fresh install of nginx:
    # apt-get install nginx -y
  
  Output:
  
  ..
  Setting up nginx-core (1.14.0-0ubuntu1.6) ...
  Job for nginx.service failed because the control process exited with error 
code.
  See "systemctl status nginx.service" and "journalctl -xe" for details.
  invoke-rc.d: initscript nginx, action "start" failed.
  ● nginx.service - A high performance web server and a reverse proxy server
     Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: 
enabled)
     Active: failed (Result: exit-code) since Wed 2019-10-23 14:01:26 UTC; 6ms 
ago
   Docs: man:nginx(8)
    Process: 1005 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; 
master_process on; (code=exited, status=1/FAILURE)
  
  Oct 23 14:01:26 nginxbionictest1 systemd[1]: Starting A high performance web 
server and a reverse proxy server...
  Oct 23 14:01:26 nginxbionictest1 nginx[1005]: nginx: [emerg] socket() [::]:80 
failed (97: Address family not supported by protocol)
  Oct 23 14:01:26 nginxbionictest1 nginx[1005]: nginx: configuration file 
/etc/nginx/nginx.conf test failed
  Oct 23 14:01:26 nginxbionictest1 systemd[1]: nginx.service: Control process 
exited, code=exited status=1
  Oct 23 14:01:26 nginxbionictest1 systemd[1]: nginx.service: Failed with 
result 'exit-code'.
  Oct 23 14:01:26 nginxbionictest1 systemd[1]: Failed to start A high 
performance web server and a reverse proxy server.
  dpkg: error processing package nginx-core (--configure):
   installed nginx-core package post-installation script subprocess returned 
error exit status 1
  dpkg: dependency problems prevent configuration of nginx:
   nginx depends on nginx-core (<< 1.14.0-0ubuntu1.6.1~) | nginx-full (<< 
1.14.0-0ubuntu1.6.1~) | nginx-light (<< 1.14.0-0ubuntu1.6.1~) | nginx-extras 
(<< 1.14.0-0ubuntu1.6.1~); however:
    Package nginx-core is not configured yet.
    Package nginx-full is not installed.
    Package nginx-light is not installed.
    Package nginx-extras is not installed.
   nginx depends on nginx-core (>= 1.14.0-0ubuntu1.6) | nginx-full (>= 
1.14.0-0ubuntu1.6) | nginx-light (>= 1.14.0-0ubuntu1.6) | nginx-extras (>= 
1.14.0-0ubuntu1.6); however:
    Package nginx-core is not configured yet.
    Package nginx-full is not installed.
    Package nginx-light is not installed.
    Package nginx-extras is not installed.
  
  dpkg: error processing package nginx (--configure):
   dependency problems - leaving unconfigured
  Processing triggers for systemd (237-3ubuntu10.31) ...
  No apport report written because the error message indicates its a followup 
error from a previous failure.
    
Processing triggers for man-db (2.8.3-2ubuntu0.1) 
...
  Processing triggers for ufw (0.36-0ubuntu0.18.04.1) ...
  Processing triggers for ureadahead (0.100.0-21) ...
  Processing triggers for libc-bin (2.27-3ubuntu1) ...
  Errors were encountered while processing:
   nginx-core
   nginx
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  
  
  [REGRESSION POTENTIAL]
  
  LOW.
  
  Other distributions does that (not including ipv6 listen by default)
  already (e.g. Centos and Upstream)
  
  * nginx.vh.default.conf -> "nginx-1.16.0-1.el8.ngx.src.rpm"
  server {
  listen 80;
  server_name localhost;
  
  * Upstream nginx:
  https://github.com/nginx/nginx/blob/master/conf/nginx.conf#L36
  
  This won't introduce behaviour change for those who upgrade nginx, but
  it will introduce a behaviour change for those used to have ipv6 listen
  in the default vhost at fresh package installation.
  
  But IMHO, the default vhost is a starting point/example, that the admin
  will anyway have to modify manually or via some automation tool
  (ansible, chef, puppet, ...)
  
  So this will only imply that the admin will need to update their recipe
  to add the ipv6 listen in their vhost config (ONLY if needed).
  
  I don't see any major blocker here.
  
+ Minus leaving the users to have to uncomment the ipv6 listen in the
+ vhost (if needed) manually, automation recipes, ... I don't see any
+ major blocker, it's a good compromise in order to prevent the actual
+ package to fails and be found in a erroneous s

[Bug 1849987] [NEW] empty space when on list view and when back to icon view

2019-10-26 Thread Miguel Belardinelli Prytoluk

Public bug reported:

Description: Ubuntu 19.10
Release: 19.10

nautilus:
Installed: 1:3.34.1-1ubuntu1
Candidate: 1:3.34.1-1ubuntu1

Expected behavior:

- (1) Open nautilus in list view OR (2) Open Nautilus in icon view and then
switch to list view
- List view occupies all the space between the top bar and the bottom.
- Switch to icon view
- Icon view occupies all the space between the top bar and the bottom.

Actual Behavior

- (1) Open nautilus in list view OR (2) Open Nautilus in icon view and then
switch to list view
- List view occupies approximately 55% of the space between the top bar and the
bottom. Approximately 45% of the space between the top bar and the bottom is
blank (the upmost part).
- Switch to icon view
- Icon view occupies approximately 55% of the space between the top bar and the
bottom. Approximately 45% of the space between the top bar and the bottom is
blank (the upmost part).

Observations:
- The side bar doesn't seem to affect the bug.
- By Starting nautilus in icon view the bug doesn't occur. In this case it's
only triggered when switching to list view.
- There are only 2 known ways to revert the bug: (1) when on icon view,
clicking on "Other Locations", and then back to any section. (2) by restarting
nautilus. There is no known way to revert the bug in list view.

I am on Ubuntu 19.10 64Bit Using Gnome and Gnome Shell 3.34.1-1ubuntu1.

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

** Attachment added: "Bug on Icon View screenshot"

https://bugs.launchpad.net/bugs/1849987/+attachment/5300440/+files/Screenshot%20from%202019-10-26%2017-23-21.png

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

Title:
empty space when on list view and when back to icon view

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

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

[Bug 1849985] [NEW] pidgin crashes on jabber login

2019-10-26 Thread Majestyx

Public bug reported:

Description:Ubuntu 19.10
Release:19.10
---
pidgin:
  Installiert:   1:2.13.0-2.2ubuntu1
  Installationskandidat: 1:2.13.0-2.2ubuntu1
  Versionstabelle:
 *** 1:2.13.0-2.2ubuntu1 500
500 http://de.archive.ubuntu.com/ubuntu eoan/universe amd64 Packages
100 /var/lib/dpkg/status
-

i set up a account on pidgin, connect...crash ...

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: pidgin 1:2.13.0-2.2ubuntu1
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CurrentDesktop: XFCE
Date: Sat Oct 26 22:06:51 2019
InstallationDate: Installed on 2019-10-07 (19 days ago)
InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
ProcEnviron:
 LANGUAGE=de_DE
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SourcePackage: pidgin
UpgradeStatus: Upgraded to eoan on 2019-10-22 (3 days ago)

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


** Tags: amd64 apport-bug eoan

** Attachment added: "crash log"
   
https://bugs.launchpad.net/bugs/1849985/+attachment/5300437/+files/_usr_bin_pidgin.1000.crash

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

Title:
  pidgin crashes on jabber login

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

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

[Bug 1849983] Re: package bind9 1:9.11.5.P4+dfsg-5.1ubuntu2 failed to install/upgrade: installed bind9 package post-installation script subprocess returned error exit status 1

** Tags removed: need-duplicate-check

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

Title:
  package bind9 1:9.11.5.P4+dfsg-5.1ubuntu2 failed to install/upgrade:
  installed bind9 package post-installation script subprocess returned
  error exit status 1

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

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

[Bug 1849930] Re: Additional VPN Breaks First VPN

How is it possible that adding an additional VPN profile can corrupted
an "already added and working" vpn? Which packages would be responsible
for that type of corruption?

Most importantly, short of reinstalling Ubuntu 19.10 what would be a
workaround that may remove this corruption?

For example, many times in the past, when I've had applications get
corrupted, I could usually delete some .hiddenFolder or configuration
file, and it would repair the corruption after rebooting.

Do any of you know which files would have to be deleted to get my VPN
situation back to "fresh install quality" (short of actually
reinstalling)?

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

Title:
  Additional VPN Breaks First VPN

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/1849930/+subscriptions

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

[Bug 1849982] Re: package zfs-dkms 0.8.1-1ubuntu14 failed to install/upgrade: installed zfs-dkms package post-installation script subprocess returned error exit status 10

** Tags removed: need-duplicate-check

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

Title:
  package zfs-dkms 0.8.1-1ubuntu14 failed to install/upgrade: installed
  zfs-dkms package post-installation script subprocess returned error
  exit status 10

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

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

[Bug 1849983] [NEW] package bind9 1:9.11.5.P4+dfsg-5.1ubuntu2 failed to install/upgrade: installed bind9 package post-installation script subprocess returned error exit status 1

2019-10-26 Thread Kensay

Public bug reported:

An error occurred while updating the system to version 19.10

ProblemType: Package
DistroRelease: Ubuntu 19.10
Package: bind9 1:9.11.5.P4+dfsg-5.1ubuntu2
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
Date: Sat Oct 26 13:07:46 2019
ErrorMessage: installed bind9 package post-installation script subprocess 
returned error exit status 1
InstallationDate: Installed on 2015-11-01 (1455 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1
PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1
RelatedPackageVersions:
 dpkg 1.19.7ubuntu2
 apt  1.9.4
SourcePackage: bind9
Title: package bind9 1:9.11.5.P4+dfsg-5.1ubuntu2 failed to install/upgrade: 
installed bind9 package post-installation script subprocess returned error exit 
status 1
UpgradeStatus: Upgraded to eoan on 2019-10-26 (0 days ago)

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


** Tags: amd64 apport-package eoan need-duplicate-check

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

Title:
  package bind9 1:9.11.5.P4+dfsg-5.1ubuntu2 failed to install/upgrade:
  installed bind9 package post-installation script subprocess returned
  error exit status 1

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

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

[Bug 1849982] [NEW] package zfs-dkms 0.8.1-1ubuntu14 failed to install/upgrade: installed zfs-dkms package post-installation script subprocess returned error exit status 10

2019-10-26 Thread Roy

Public bug reported:

Package is really zfs-dkms but bug tool no have

upgrading 19.04 - 19.10 mac Mini

   Processing triggers for initramfs-tools (0.133ubuntu10) ...
   This system doesn't support Secure Boot
   Secure Boot not enabled on this system.
   Errors were encountered while processing:
zfs-dkms

ProblemType: Package
DistroRelease: Ubuntu 19.10
Package: zfs-dkms 0.8.1-1ubuntu14
ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
Uname: Linux 5.0.0-29-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zlua zcommon znvpair
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
Date: Sat Oct 26 12:22:09 2019
ErrorMessage: installed zfs-dkms package post-installation script subprocess 
returned error exit status 10
InstallationDate: Installed on 2019-06-20 (128 days ago)
InstallationMedia: Ubuntu-Server 19.04 "Disco Dingo" - Release amd64 
(20190416.1)
PackageArchitecture: all
Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1
PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1
RelatedPackageVersions:
 dpkg 1.19.7ubuntu2
 apt  1.9.4
SourcePackage: zfs-linux
Title: package zfs-dkms 0.8.1-1ubuntu14 failed to install/upgrade: installed 
zfs-dkms package post-installation script subprocess returned error exit status 
10
UpgradeStatus: Upgraded to eoan on 2019-10-26 (0 days ago)

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


** Tags: amd64 apport-package eoan

** Description changed:

+ Package is really zfs-dkms but bug tool no have
+ 
  upgrading 19.04 - 19.10 mac Mini
  
-Processing triggers for initramfs-tools (0.133ubuntu10) ...
-This system doesn't support Secure Boot
-Secure Boot not enabled on this system.
-Errors were encountered while processing:
- zfs-dkms
+    Processing triggers for initramfs-tools (0.133ubuntu10) ...
+    This system doesn't support Secure Boot
+    Secure Boot not enabled on this system.
+    Errors were encountered while processing:
+ zfs-dkms
  
  ProblemType: Package
  DistroRelease: Ubuntu 19.10
  Package: zfs-dkms 0.8.1-1ubuntu14
  ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zlua zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  Date: Sat Oct 26 12:22:09 2019
  ErrorMessage: installed zfs-dkms package post-installation script subprocess 
returned error exit status 10
  InstallationDate: Installed on 2019-06-20 (128 days ago)
  InstallationMedia: Ubuntu-Server 19.04 "Disco Dingo" - Release amd64 
(20190416.1)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1
  RelatedPackageVersions:
-  dpkg 1.19.7ubuntu2
-  apt  1.9.4
+  dpkg 1.19.7ubuntu2
+  apt  1.9.4
  SourcePackage: zfs-linux
  Title: package zfs-dkms 0.8.1-1ubuntu14 failed to install/upgrade: installed 
zfs-dkms package post-installation script subprocess returned error exit status 
10
  UpgradeStatus: Upgraded to eoan on 2019-10-26 (0 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/1849982

Title:
  package zfs-dkms 0.8.1-1ubuntu14 failed to install/upgrade: installed
  zfs-dkms package post-installation script subprocess returned error
  exit status 10

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

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

[Bug 1849034] Re: xenial/linux-hwe: 4.15.0-67.76~16.04.1 -proposed tracker

** 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: 1849035
  packages:
main: linux-hwe
meta: linux-meta-hwe
signed: linux-signed-hwe
  phase: Testing
  phase-changed: Thursday, 24. October 2019 19:36 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
certification-testing: Ongoing -- testing in progress
regression-testing: Ongoing -- testing in progress
-   security-signoff: Pending -- waiting for signoff
+   security-signoff: Stalled -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
xenial/linux-deeplens: bug 1849033
xenial/linux-hwe-edge: bug 1849032
  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/1849034

Title:
  xenial/linux-hwe: 4.15.0-67.76~16.04.1 -proposed tracker

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

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

[Bug 1743592] Re: NGINX fails to start/install/upgrade if IPv6 is completely disabled.

2019-10-26 Thread Eric Desrochers

@teward, sound good I'll let you drive the focal upload since you were
already in the middle of it and include solution #1 in it.

For the SRU, I'll take care of the discussion internally, and will keep
the bug updated on the outcome.

Eric


** Changed in: nginx (Ubuntu)
 Assignee: Eric Desrochers (slashd) => Thomas Ward (teward)

** Changed in: nginx (Ubuntu Eoan)
   Status: New => In Progress

** Changed in: nginx (Ubuntu Eoan)
   Importance: Undecided => Medium

** Changed in: nginx (Ubuntu Disco)
   Status: New => In Progress

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

** Changed in: nginx (Ubuntu Bionic)
   Importance: Undecided => Medium

** Changed in: nginx (Ubuntu Disco)
   Importance: Undecided => Medium

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

Title:
  NGINX fails to start/install/upgrade if IPv6 is completely disabled.

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

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

[Bug 1743592] Re: NGINX fails to start/install/upgrade if IPv6 is completely disabled.

2019-10-26 Thread Thomas Ward

I am in favor of solution #1, and will drive this for Focal.  However, I
have no call in whether this is accepted by the SRU team for SRU.

More to come though, I have a priority on the nginx package in Focal and
determining which branch we track heading up to release first.

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

Title:
  NGINX fails to start/install/upgrade if IPv6 is completely disabled.

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

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

[Bug 1849981] Re: package zfs-dkms 0.8.1-1ubuntu14 failed to install/upgrade: installed zfs-dkms package post-installation script subprocess returned error exit status 10