[Bug 1836929] Re: chrony has migration regressions from autopkgtests (disco/eoan)

2019-07-17 Thread Christian Ehrhardt 
** Changed in: chrony (Ubuntu Eoan)
 Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned)

** Changed in: chrony (Ubuntu Disco)
   Status: Won't Fix => Triaged

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

Title:
  chrony has migration regressions from autopkgtests (disco/eoan)

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

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

[Bug 1834213] Re: After kernel upgrade, nf_conntrack_ipv4 module unloaded, no IP traffic to instances

2019-07-17 Thread James Page
Raising a kernel bug task.

Note my testing was on Bionic not Xenial.

Drew - can you confirm which kernel version and packages you are using.

** Changed in: charm-neutron-openvswitch
   Importance: Undecided => Low

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

Title:
  After kernel upgrade, nf_conntrack_ipv4 module unloaded, no IP traffic
  to instances

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-neutron-openvswitch/+bug/1834213/+subscriptions

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

[Bug 1836809] Re: segfault when CCD are present in two different HOG services

2019-07-17 Thread Mathieu Stephan
Noted! Anyway we already had installed the latest bluez version - 5.50.

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

Title:
  segfault when CCD are present in two different HOG services

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

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

[Bug 1834213] Re: After kernel upgrade, nf_conntrack_ipv4 module unloaded, no IP traffic to instances

2019-07-17 Thread James Page
Ignore prior comment:

$ lsmod | grep conntrack
nf_conntrack_ipv6  20480  1
nf_conntrack_ipv4  16384  1
nf_defrag_ipv4 16384  1 nf_conntrack_ipv4
nf_defrag_ipv6 36864  2 nf_conntrack_ipv6,openvswitch
nf_conntrack  131072  6 
nf_conntrack_ipv6,nf_conntrack_ipv4,nf_nat,nf_nat_ipv6,nf_nat_ipv4,openvswitch
libcrc32c  16384  5 nf_conntrack,nf_nat,openvswitch,xfs,raid456

as soon as a loaded the openvswitch kernel module the nf_conntrack_*
modules where loaded as well.


** Changed in: charm-neutron-openvswitch
   Status: New => Incomplete

** Also affects: linux (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/1834213

Title:
  After kernel upgrade, nf_conntrack_ipv4 module unloaded, no IP traffic
  to instances

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-neutron-openvswitch/+bug/1834213/+subscriptions

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

[Bug 1836805] modified.conffile..etc.gdm3.custom.conf.txt

2019-07-17 Thread Pascal Gicquel
apport information

** Attachment added: "modified.conffile..etc.gdm3.custom.conf.txt"
   
https://bugs.launchpad.net/bugs/1836805/+attachment/529/+files/modified.conffile..etc.gdm3.custom.conf.txt

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

Title:
  screen frozen after reboot

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

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

[Bug 1836805] ProcCpuinfoMinimal.txt

2019-07-17 Thread Pascal Gicquel
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1836805/+attachment/528/+files/ProcCpuinfoMinimal.txt

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

Title:
  screen frozen after reboot

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

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

[Bug 1836805] Re: screen frozen after reboot

2019-07-17 Thread Pascal Gicquel
A boot with 5.0.0-13 (available in boot menu after install) rather than default 
5.0.0-20 provided the same symptoms.
I changed /etc/gdm3/custom.conf to boot with xorg and ... it did work.

I was able to run apport-collect.

I guess I will stay in this configuration. Don't hesitate to tell me if
you need me to run more tests to help solving this issue

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

Title:
  screen frozen after reboot

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

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

[Bug 1836805] Re: screen frozen after reboot

2019-07-17 Thread Pascal Gicquel
apport information

** Tags added: apport-collected

** Description changed:

  After I installed Ubuntu 19.04 (fresh install with hard drive erasing),
  I was able to login once just after install. But then after reboot, the
  screen freezes in the middle of the boot process and I never get the
  login banner.
  
  I was able to launch the recovery mode and get some information through
  journalctl command and it seems that the problem is related to a Wayland
  server crash. I don't really know if the problem comes from Wayland or
  Gnome. The first worrying error message is : "gnome_shell[1165]: Failed
  to apply DRM plane transform 0: Permission non accordée" (ie, Permission
  denied in french)
  
  Thanks to the recovery mode I was able to upgrade via "apt-get update"
  and "apt-get upgrade", but the symptoms were the same after a reboot
  
  I uncommented the "Enable=true" flag of the [debug] section of
  /etc/gdm3/custom.conf and I provide and extract of the journalctl output
  related to the error as an attachment to this report
  (journalctl_extract.txt part). I also provide some system information
  (system.txt pat).
  
  I hope this may help to solve the issue.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.10-0ubuntu27.1
+ Architecture: amd64
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 19.04
+ InstallationDate: Installed on 2019-07-15 (2 days ago)
+ InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
+ Package: gdm3 3.32.0-1ubuntu1
+ PackageArchitecture: amd64
+ ProcEnviron:
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=fr_FR.UTF-8
+  SHELL=/bin/bash
+ ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
+ Tags:  disco
+ Uname: Linux 5.0.0-20-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ mtime.conffile..etc.gdm3.custom.conf: 2019-07-18T07:25:10.575513

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1836805/+attachment/527/+files/Dependencies.txt

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

Title:
  screen frozen after reboot

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

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

[Bug 1836929] Re: chrony has migration regressions from autopkgtests (disco/eoan)

2019-07-17 Thread Christian Ehrhardt 
I have reviewed and Nacked the MP for the force-badtest.
Lets continue here, summary:

Summarizing:
- actually two issues seem to break chrony tests
  1. some yet unknown change in a package added stderr which needs [1] for bug 
1836882
 The new thing is that this now also affects Disco
  2. (this bug) due to upstream clksim changes things don't properly match 
anymore.
 We need [2] and maybe [3]
- We will not need to add a badtest, we just fix the tests and iproute will 
then pass testing 
  against the new version.

I was able to reproduce that locally and will create a branch/ppa/test
for it that you later on (if I can make it in time) can take a look at.

[1]: 
https://git.launchpad.net/ubuntu/+source/chrony/commit/?id=ebdec551cbb6a0986bfd489e4ca90ef103e37a07
[2]: 
https://salsa.debian.org/debian/chrony/commit/bb79b3247c1938b40f7532a4aa445da16148f822
[3]: 
https://salsa.debian.org/debian/chrony/commit/bc402d6270fef5b6ed1b166abe198efeb78e0b16

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

Title:
  chrony has migration regressions from autopkgtests (disco/eoan)

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

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

[Bug 1799319] Re: Upgrade to 18.10 fails: Please install all available updates

2019-07-17 Thread Guy Rouillier
Brian, thanks for the reply.  I didn't get notified so I missed your
reply.  I used my workaround to eventually update the VM, so I can no
longer test the failed upgrade.  I'll try to remember if this happens
again. Here is the output of the command you requested:

guyr@ubuntu64:~$ apt-cache policy ubuntu-release-upgrader-core
ubuntu-release-upgrader-core:
  Installed: 1:19.04.16.6
  Candidate: 1:19.04.16.6
  Version table:
 *** 1:19.04.16.6 500
500 http://us.archive.ubuntu.com/ubuntu disco-updates/main amd64 
Packages
500 http://us.archive.ubuntu.com/ubuntu disco-updates/main i386 Packages
100 /var/lib/dpkg/status
 1:19.04.16 500
500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
500 http://us.archive.ubuntu.com/ubuntu disco/main i386 Packages

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

Title:
  Upgrade to 18.10 fails: Please install all available updates

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

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

[Bug 1823718] Re: Installation fails with Python3.7 SyntaxError on Ubuntu Disco

2019-07-17 Thread James Page
** Changed in: charm-hacluster
   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/1823718

Title:
  Installation fails with Python3.7 SyntaxError on Ubuntu Disco

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-hacluster/+bug/1823718/+subscriptions

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

[Bug 1824986] Re: twinkle doesn't start (stack smashing detected) (Lubuntu 18.04)

2019-07-17 Thread Dima
Yes, this does help. Thank you.

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

Title:
  twinkle doesn't start (stack smashing detected) (Lubuntu 18.04)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1824986/+subscriptions

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

[Bug 1836882] Re: autopkgtest due to other packages chaning

2019-07-17 Thread Christian Ehrhardt 
It seems this now also affects Disco, some other change (that was not
triggering chrony tests) got in that now makes it break.

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

** Changed in: chrony (Ubuntu Disco)
   Status: New => Triaged

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

Title:
  autopkgtest due to other packages chaning

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

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

[Bug 1835091] Re: subiquity crashes upon reusing failed to assemble raid member partition

2019-07-17 Thread Michael Hudson-Doyle
** Attachment added: "test failures (warning contains sparse disk images)"
   
https://bugs.launchpad.net/curtin/+bug/1835091/+attachment/525/+files/test-failures.tar.gz

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

Title:
  subiquity crashes upon reusing failed to assemble raid member
  partition

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

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

[Bug 1835091] Re: subiquity crashes upon reusing failed to assemble raid member partition

2019-07-17 Thread Michael Hudson-Doyle
** Attachment added: "logs from testing in KVM"
   
https://bugs.launchpad.net/curtin/+bug/1835091/+attachment/526/+files/logs.tgz

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

Title:
  subiquity crashes upon reusing failed to assemble raid member
  partition

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

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

[Bug 1835091] Re: subiquity crashes upon reusing failed to assemble raid member partition

2019-07-17 Thread Michael Hudson-Doyle
So https://code.launchpad.net/~mwhudson/curtin/+git/curtin/+merge/369918
now has matching test cases. Will attach failures from the tests
(warning, contains sparse disk images) and from my testing in KVM.

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

Title:
  subiquity crashes upon reusing failed to assemble raid member
  partition

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

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

[Bug 1836986] Re: Kernel 5.2.0-8: iwlwifi Microcode SW error detected Wireless-AC 9260

2019-07-17 Thread Brandon Darbro
Moving the 46 firmware out of /lib/firmware and copying the 43 firmware
to the 46 firmware's filename and rebooting has allowed me to have
successful wifi.  modinfo shows it wants 46, but lshw show's it actually
is running version 43.

Please either revert to version 43, or fix 46.

Thank you. :)

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

Title:
  Kernel 5.2.0-8: iwlwifi Microcode SW error detected Wireless-AC 9260

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

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

[Bug 1828948] Re: OBSOLETE_BY in DKMS.CONF does not work

2019-07-17 Thread Alex Tu
for #10, also followed the testing environment of #12 and tested passed
on bionic as well.

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

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

Title:
  OBSOLETE_BY in DKMS.CONF does not work

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

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

[Bug 1836630] Re: System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend

2019-07-17 Thread Kai-Heng Feng
PCI core saves device's config space during suspend so I think it won't
cause any issue.

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

Title:
  System76 Oryx Pro (oryp5) with 5.0.0-21: Fail to resume from suspend

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

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

[Bug 1836456] Re: [ThinkPad S1 Yoga] Machine Immediately Wakes Up From Suspend

2019-07-17 Thread Kai-Heng Feng
Ok, please compare "/sys/kernel/debug/wakeup_sources" before and after
suspend to see which device wakes the system up.

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

Title:
  [ThinkPad S1 Yoga] Machine Immediately Wakes Up From Suspend

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

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

[Bug 1447763] Re: HP Proliant Servers suffer from cpufreq initialization failure for some cpu cores

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

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

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

Title:
  HP Proliant Servers suffer from cpufreq initialization failure for
  some cpu cores

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

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

[Bug 1398497] Re: HP Proliant Serverrs - DL360 and DL380 Gen8 - Precise Kernel Panic - General Protection Fault and X2APIC/XAPIC boot parameters

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

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

Title:
  HP Proliant Serverrs - DL360 and DL380 Gen8 - Precise Kernel Panic -
  General Protection Fault and X2APIC/XAPIC boot parameters

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

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

[Bug 1398497] Re: HP Proliant Serverrs - DL360 and DL380 Gen8 - Precise Kernel Panic - General Protection Fault and X2APIC/XAPIC boot parameters

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

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

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

Title:
  HP Proliant Serverrs - DL360 and DL380 Gen8 - Precise Kernel Panic -
  General Protection Fault and X2APIC/XAPIC boot parameters

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

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

[Bug 1439872] Re: kernel panic involving drbd

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

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

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

Title:
  kernel panic involving drbd

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

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

[Bug 1626758] Re: tightvncserver doesn't work no s390x platform

2019-07-17 Thread Launchpad Bug Tracker
[Expired for tightvnc (Ubuntu) because there has been no activity for 60
days.]

** Changed in: tightvnc (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/1626758

Title:
  tightvncserver doesn't work no s390x platform

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

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

[Bug 1819761] Re: [MIR] containerd

2019-07-17 Thread Seth Arnold
There's roughly half-million lines of code in vendor/ -- we have asked
for Go packages to have their vendored code split out into their own
packages to simplify triage, fixing, and minimize rebuilding:

https://wiki.ubuntu.com/MIRTeam#Embedded_sources_and_static_linking

$ tokei vendor
---
 LanguageFilesLines Code Comments   Blanks
---
 Assembly   53 4127 38080  319
 C  18 2337 1481  502  354
 C Header3   61   42   109
 Go   1773   625922   4959227480155199
 Markdown   86 9461 946100
 Protocol Buffers   3411593 3103 6908 1582
 Plain Text  4  673  67300
---
 Total1971   654174   5144908222157463
---


Thanks

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

Title:
  [MIR] containerd

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

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

[Bug 1834549] Re: Wifi won't load

2019-07-17 Thread Brandon Darbro
Yes sorry, I was pretty sure I didn't mark it as a security bug.  Sorry
if I flubbed that part up.

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

Title:
  Wifi won't load

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

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

[Bug 1836169] Re: cpuhotplug04 in cpuhotplug from ubuntu_ltp failed on C ARM64

2019-07-17 Thread Po-Hsu Lin
On amd64 node naumann with Disco kernel, this test failed with:
 Name: cpuhotplug04
 Date: Mon Jul 8 17:22:01 UTC 2019
 Desc: Does it prevent us from offlining the last CPU?

 /opt/ltp/testcases/bin/cpuhotplug04.sh: 99: echo: echo: I/O error
 cpuhotplug04 1 TFAIL: Could not offline cpu95
 tag=cpuhotplug04 stime=1562606521 dur=59 exit=exited stat=1 core=no cu=44 
cs=105


** Tags added: 5.0 amd64 disco

** Also affects: linux (Ubuntu Disco)
   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/1836169

Title:
  cpuhotplug04 in cpuhotplug from ubuntu_ltp failed on C ARM64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1836169/+subscriptions

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

[Bug 1836167] Re: cpuhotplug03 in cpuhotplug from ubuntu_ltp failed on C Moonshot ARM64

2019-07-17 Thread Po-Hsu Lin
Same failure:
TFAIL: No cpuhotplug_do_spin_loop processes found on CPU1

Found on amd64 node naumann with Disco kernel.

** Also affects: linux (Ubuntu Disco)
   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/1836167

Title:
  cpuhotplug03 in cpuhotplug from ubuntu_ltp failed on C Moonshot ARM64

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1836167/+subscriptions

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

[Bug 1796260] Re: UEFI install onto an MBR disk, with a pre-existing os/partition, results in a non-bootable ESP on a logical partition

2019-07-17 Thread Michael Hudson-Doyle
So subiquity/curtin sort of tiptoe around this bug currently. Curtin's
data model uses the same field ("flag") to indicate that a partition is
an ESP (set flag to "boot") and that a partition is a logical partition
(set flag to "logical").

As it happens in the code in curtin that converts probert data to curtin
actions, "logicalness" wins over "ESPness", so the user will never be
given the chance to reuse a logical ESP (and subiquity only ever creates
GPT partitions).

To enable reuse of a logical ESP we'd need to change curtin somehow,
maybe just to allow "boot+logical" as a flag value, or maybe something
less crass. And then fix this bug. It seems somehow rather low priority
though.

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

Title:
  UEFI install onto an MBR disk, with a pre-existing os/partition,
  results in a non-bootable ESP on a logical partition

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

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

[Bug 1836938] Re: falkon failed to load some pages

2019-07-17 Thread Walter Lapchynski
Just to go on record, I did have this experience the other day, but have
not been able to reproduce.

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

Title:
  falkon failed to load some pages

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

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

[Bug 1834006] Re: cpuset_hotplug from controllers in ubuntu_ltp failed on C/D

2019-07-17 Thread Po-Hsu Lin
** Summary changed:

- cpuset_hotplug from controllers in ubuntu_ltp failed on Cosmic
+ cpuset_hotplug from controllers in ubuntu_ltp failed on C/D

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

Title:
  cpuset_hotplug from controllers in ubuntu_ltp failed on C/D

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1834006/+subscriptions

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

[Bug 1836971] Re: sched: Prevent CPU lockups when task groups take longer than the period

2019-07-17 Thread Matthew Ruffell
** Description changed:

  BugLink: https://bugs.launchpad.net/bugs/1836971
  
  [Impact]
  
  On machines with extremely high CPU usage, parent task groups which have
  a large number of children can make the for loop in
  sched_cfs_period_timer() run until the watchdog fires when the
  cfs_period_us setting is too short.
  
  In this particular case, it is unlikely that the call to
  hrtimer_forward_now() will return 0, meaning the for loop is never left,
  and tasks are never rescheduled.
  
  The large number of children makes do_sched_cfs_period_timer() take
  longer than the period, which impacts calls to hrtimer_forward_now().
  
  The kernel will produce this call trace:
  
  CPU: 51 PID: 0 Comm: swapper/51 Tainted: P OELK 4.15.0-50-generic
  #54-Ubuntu
  
  Call Trace:
  
  ? sched_clock+0x9/0x10
  walk_tg_tree_from+0x61/0xd0
  ? task_rq_unlock+0x30/0x30
  unthrottle_cfs_rq+0xcb/0x1a0
  distribute_cfs_runtime+0xd7/0x100
  sched_cfs_period_timer+0xd9/0x1a0
  ? sched_cfs_slack_timer+0xe0/0xe0
  __hrtimer_run_queues+0xdf/0x230
  hrtimer_interrupt+0xa0/0x1d0
  smp_apic_timer_interrupt+0x6f/0x130
  apic_timer_interrupt+0x84/0x90
  
  
  This has been hit in production in a particularly highly utilised hadoop
  cluster which is powering an analytics platform. About 30% of the
  cluster experiences this issue every week, and the machines need a
  manual reboot to get back online.
  
  [Fix]
  
  This was fixed in 5.1 upstream with the below commit:
  
  commit 2e8e19226398db8265a8e675fcc0118b9e80c9e8
  Author: Phil Auld 
  Date: Tue Mar 19 09:00:05 2019 -0400
  subject: sched/fair: Limit sched_cfs_period_timer() loop to avoid hard lockup
  
  This commit adds a check to see if the loop has run too many times, and if it
  has, scales up the period and quota, so the timer can complete before the
  next period expires, which enables the task to be rescheduled normally.
  
  Note, 2e8e19226398db8265a8e675fcc0118b9e80c9e8 was included in upstream
  stable versions 4.4.179, 4.9.171, 4.14.114, 4.19.37, 5.0.10.
  
- Please cherry pick 2e8e19226398db8265a8e675fcc0118b9e80c9e8 to all bionic
- kernels.
+ This patch requires minor backporting for 4.15, so please cherry pick 
+ d069fe4844f8d799d771659a745fe91870c93fda from upstream stable 4.14.y, where 
the backport has been done by the original author, to all bionic kernels.
  
  [Testcase]
  
  Kind of hard to reproduce, so this was tested on a production hadoop cluster
  with extremely high CPU load.
  
  I built a test kernel, which is available here:
  
  https://launchpad.net/~mruffell/+archive/ubuntu/sf232784-test
  
  For unpatched kernels, expect the machine to lockup and print the call
  trace in the impact section.
  
  For patched kernels, if the machine hits the condition, it will print a
  warning to the kernel log with the new period and quota which has been
  used:
  
  Example from the same hadoop cluster with a machine running the test
  kernel:
  
  % uname -a
  4.15.0-50-generic #54+hf232784v20190626b1-Ubuntu
  % sudo grep cfs /var/log/kern.log.*
  cfs_period_timer[cpu40]: period too short, scaling up (new cfs_period_us 
67872, cfs_quota_us = 3475091)
  cfs_period_timer[cpu48]: period too short, scaling up (new cfs_period_us 
22430, cfs_quota_us = 1148437)
  cfs_period_timer[cpu48]: period too short, scaling up (new cfs_period_us 
25759, cfs_quota_us = 1318908)
  cfs_period_timer[cpu68]: period too short, scaling up (new cfs_period_us 
29583, cfs_quota_us = 1514684)
  cfs_period_timer[cpu49]: period too short, scaling up (new cfs_period_us 
33974, cfs_quota_us = 1739519)
  cfs_period_timer[cpu3]: period too short, scaling up (new cfs_period_us 
39017, cfs_quota_us = 1997729)
  cfs_period_timer[cpu10]: period too short, scaling up (new cfs_period_us 
44809, cfs_quota_us = 2294267)
  cfs_period_timer[cpu3]: period too short, scaling up (new cfs_period_us 
51460, cfs_quota_us = 2634823)
  cfs_period_timer[cpu3]: period too short, scaling up (new cfs_period_us 
59099, cfs_quota_us = 3025929)
  cfs_period_timer[cpu3]: period too short, scaling up (new cfs_period_us 
67872, cfs_quota_us = 3475091)
  
  [Regression Potential]
  This patch was accepted into upstream stable versions 4.4.179, 4.9.171,
  4.14.114, 4.19.37, 5.0.10, and is thus treated as stable and trusted by the
  community.
  
  Xenial received this patch in 4.4.0-150.176, as per LP #1828420
  Disco will receive this patch in the next version, as per LP #1830922
  Eoan already has the patch, being based on 5.2.
  
  While this does effect a core part of the kernel, the scheduler, the
  patch has been extensively tested, and it has been proven in production
  environments, so the overall risk is low.

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

Title:
  sched: Prevent CPU lockups when task groups take longer than the
  period

To manage notifications about this bug go to:

[Bug 1834006] Re: cpuset_hotplug from controllers in ubuntu_ltp failed on Cosmic

2019-07-17 Thread Po-Hsu Lin
Found on node "amaura" with Disco kernel.

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

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

** Tags added: sru-20190701

** Tags added: 4.18 5.0 disco

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

Title:
  cpuset_hotplug from controllers in ubuntu_ltp failed on Cosmic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1834006/+subscriptions

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

[Bug 1771158] Re: Synaptic doesn't open with administrative privileges on wayland

2019-07-17 Thread HRJ
The solution described in #2 works for me. Thank you! I can finally
switch to Wayland now.

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

Title:
  Synaptic doesn't open with administrative privileges on wayland

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

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

[Bug 1836809] Re: segfault when CCD are present in two different HOG services

2019-07-17 Thread Daniel van Vugt
Thanks.

Please note Ubuntu 18.10 reaches end-of-life this month, so please
upgrade to 19.04.

** Tags added: cosmic

** Bug watch added: Linux Kernel Bug Tracker #204201
   https://bugzilla.kernel.org/show_bug.cgi?id=204201

** Also affects: bluez via
   https://bugzilla.kernel.org/show_bug.cgi?id=204201
   Importance: Unknown
   Status: Unknown

** Changed in: bluez (Ubuntu)
   Status: Incomplete => New

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

Title:
  segfault when CCD are present in two different HOG services

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

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

[Bug 1836960] Re: Gnome on Ubuntu 18.04.2 LTS text copying triggers apparently useless file writes

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

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

Title:
  Gnome on Ubuntu 18.04.2 LTS text copying triggers apparently useless
  file writes

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

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

[Bug 1836881] Re: gnome-shell freeze

2019-07-17 Thread Daniel van Vugt
Next time the problem happens, log into a tty and find the PID of the
frozen gnome-shell process. Then run:

  apport-cli --hanging -P PID

where PID is the process ID of the frozen gnome-shell process (which is
the one running as your own user ID, not gdm).

That should create a new bug/crash report. Please send us a link to
that.


** Changed in: gnome-shell (Ubuntu)
   Status: New => Incomplete

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

Title:
  gnome-shell freeze

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

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

[Bug 1836881] Re: Xorg freeze

2019-07-17 Thread Daniel van Vugt
If your "mouse works fine" then Xorg is still working and it's only
gnome-shell that's frozen, so reassigning...

** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)

** Summary changed:

- Xorg freeze
+ gnome-shell freeze

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

Title:
  gnome-shell freeze

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

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

[Bug 1836960] Re: Gnome on Ubuntu 18.04.2 LTS text copying triggers apparently useless file writes

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

** Changed in: gnome-shell (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/1836960

Title:
  Gnome on Ubuntu 18.04.2 LTS text copying triggers apparently useless
  file writes

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

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

[Bug 1836960] Re: Gnome on Ubuntu 18.04.2 LTS text copying triggers apparently useless file writes

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

** Changed in: nautilus (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/1836960

Title:
  Gnome on Ubuntu 18.04.2 LTS text copying triggers apparently useless
  file writes

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

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

[Bug 1836960] Re: Gnome on Ubuntu 18.04.2 LTS text copying triggers apparently useless file writes

2019-07-17 Thread Daniel van Vugt
** No longer affects: ubuntu

** Tags added: performance

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

Title:
  Gnome on Ubuntu 18.04.2 LTS text copying triggers apparently useless
  file writes

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

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

[Bug 1819761] Re: [MIR] containerd

2019-07-17 Thread Seth Arnold
The lintian errors appear to have been drastically reduced in the
interim:

E: containerd source: missing-build-dependency-for-dh-addon systemd => 
debhelper (>= 9.20160709~) | debhelper-compat | dh-sequence-systemd || 
dh-systemd
W: containerd source: vcs-obsolete-in-debian-infrastructure vcs-git 
https://anonscm.debian.org/git/pkg-go/packages/containerd.git
W: containerd source: vcs-obsolete-in-debian-infrastructure vcs-browser 
https://anonscm.debian.org/cgit/pkg-go/packages/containerd.git
E: containerd: init.d-script-not-included-in-package etc/init.d/containerd
W: containerd: manpage-has-bad-whatis-entry 
usr/share/man/man1/containerd-config.1.gz
W: containerd: manpage-has-bad-whatis-entry usr/share/man/man1/containerd.1.gz
W: containerd: manpage-has-bad-whatis-entry usr/share/man/man1/ctr.1.gz
W: containerd: manpage-has-bad-whatis-entry 
usr/share/man/man5/containerd-config.toml.5.gz
W: containerd: binary-without-manpage usr/bin/containerd-shim
W: containerd: binary-without-manpage usr/bin/containerd-shim-runc-v1
W: containerd: binary-without-manpage usr/bin/containerd-stress
W: golang-github-docker-containerd-dev: package-contains-vcs-control-file 
usr/share/gocode/src/github.com/containerd/containerd/.gitignore
W: golang-github-docker-containerd-dev: package-contains-vcs-control-file 
usr/share/gocode/src/github.com/containerd/containerd/docs/.gitignore
W: golang-github-docker-containerd-dev: executable-not-elf-or-script 
usr/share/gocode/src/github.com/containerd/containerd/runtime/linux/runctypes/1.0.pb.txt
W: golang-github-docker-containerd-dev: executable-not-elf-or-script 
usr/share/gocode/src/github.com/containerd/containerd/runtime/linux/runctypes/next.pb.txt
W: golang-github-docker-containerd-dev: executable-not-elf-or-script 
usr/share/gocode/src/github.com/containerd/containerd/windows/hcsshimtypes/next.pb.txt
W: golang-github-docker-containerd-dev: executable-not-elf-or-script 
usr/share/gocode/src/github.com/containerd/containerd/windows/hcsshimtypes/1.0.pb.txt
W: golang-github-docker-containerd-dev: executable-not-elf-or-script 
usr/share/gocode/src/github.com/containerd/containerd/api/1.1.pb.txt
W: golang-github-docker-containerd-dev: executable-not-elf-or-script 
usr/share/gocode/src/github.com/containerd/containerd/api/1.2.pb.txt
W: golang-github-docker-containerd-dev: executable-not-elf-or-script 
usr/share/gocode/src/github.com/containerd/containerd/api/1.0.pb.txt
W: golang-github-docker-containerd-dev: executable-not-elf-or-script 
usr/share/gocode/src/github.com/containerd/containerd/runtime/v2/runc/options/next.pb.txt
W: golang-github-docker-containerd-dev: executable-not-elf-or-script 
usr/share/gocode/src/github.com/containerd/containerd/api/next.pb.txt


Thanks

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

Title:
  [MIR] containerd

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

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

[Bug 1836805] Re: screen frozen after reboot

2019-07-17 Thread Daniel van Vugt
Please try the workaround in comment #3, and assuming that works please
then run this command to send us more information about the system:

  apport-collect 1836805


** Changed in: gdm3 (Ubuntu)
   Status: New => Incomplete

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

Title:
  screen frozen after reboot

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

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

[Bug 1836987] [NEW] update to 18.09.8

2019-07-17 Thread Michael Hudson-Doyle
Public bug reported:

[impact]
It includes the fix for CVE-2019-13509

[test case]
autopkgtests per https://wiki.ubuntu.com/DockerUpdates

[regression potential]
As per usual, we don't mind if the updated packages regress in some sense, 
that's all part of the "upstream experience" we provide for docker et al.

** Affects: docker.io (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: docker.io (Ubuntu Xenial)
 Importance: Undecided
 Status: New

** Affects: docker.io (Ubuntu Bionic)
 Importance: Undecided
 Status: New

** Affects: docker.io (Ubuntu Cosmic)
 Importance: Undecided
 Status: New

** Affects: docker.io (Ubuntu Disco)
 Importance: Undecided
 Status: New

** Also affects: docker.io (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: docker.io (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Also affects: docker.io (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: docker.io (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

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

Title:
  update to 18.09.8

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1836987/+subscriptions

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

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

2019-07-17 Thread Daniel van Vugt
** Tags added: xrandr-scaling

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

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

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

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

[Bug 1836986] [NEW] Kernel 5.2.0-8: iwlwifi Microcode SW error detected Wireless-AC 9260

2019-07-17 Thread Brandon Darbro
Public bug reported:

Ubuntu version:
Description:Ubuntu Eoan Ermine (development branch)
Release:19.10


System type:
description: Notebook
product: Precision 5530 (087D)
vendor: Dell Inc.


Hardware having issue:
(wireless card info from previous working kernel)
   *-network
description: Wireless interface
product: Wireless-AC 9260
vendor: Intel Corporation
physical id: 0
bus info: pci@:3b:00.0
logical name: wlp59s0
version: 29
serial: 48:89:e7:d5:ab:b5
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress msix bus_master cap_list 
ethernet physical wireless
configuration: broadcast=yes driver=iwlwifi 
driverversion=5.0.0-20-generic firmware=43.95eb4e97.0 ip=10.80.13.232 latency=0 
link=yes multicast=yes wireless=IEEE 802.11
resources: irq:16 memory:ed40-ed403fff


Grub config with settings for Dell laptop hardware set:
/etc/default/grub
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
#   info -f grub -n 'Simple configuration'

GRUB_DEFAULT=0
GRUB_TIMEOUT=0
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
#GRUB_CMDLINE_LINUX_DEFAULT="nosplash"
GRUB_CMDLINE_LINUX="nouveau.blacklist=1 acpi_rev_override=1 acpi_osi=Linux 
nouveau.modeset=0 pcie_aspm=force drm.vblankoffdelay=1 scsi_mod.use_blk_mq=1 
nouveau.runpm=0 mem_sleep_default=deep"

# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"

# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"


Iwlwifi config with 11n disabled, 11n wasn't ever stable before, so left it 
disabled.
/etc/modprobe.d/iwlwifi.conf 
# /etc/modprobe.d/iwlwifi.conf
# iwlwifi will dyamically load either iwldvm or iwlmvm depending on the
# microcode file installed on the system.  When removing iwlwifi, first
# remove the iwl?vm module and then iwlwifi.
remove iwlwifi \
(/sbin/lsmod | grep -o -e ^iwlmvm -e ^iwldvm -e ^iwlwifi | xargs /sbin/rmmod) \
&& /sbin/modprobe -r mac80211
options iwlwifi 11n_disable=1


Linux-Firmware package = 1.180
Nvidia Driver version = 430.34-0ubuntu2

Issue:
Problem with kernel 5.2.0-8-generic - Wifi firmware fails to load.  Works with 
5.0.0.-20-generic kernel.

Syslog:
Jul 17 15:13:31 Lappy kernel: [   85.319088] iwlwifi :3b:00.0: Microcode SW 
error detected. Restarting 0x0.
Jul 17 15:13:31 Lappy kernel: [   85.320158] iwlwifi :3b:00.0: Start IWL 
Error Log Dump:
Jul 17 15:13:31 Lappy kernel: [   85.320161] iwlwifi :3b:00.0: Status: 
0x0080, count: 6
Jul 17 15:13:31 Lappy kernel: [   85.320162] iwlwifi :3b:00.0: Loaded 
firmware version: 46.a41adfe7.0
Jul 17 15:13:31 Lappy kernel: [   85.320164] iwlwifi :3b:00.0: 0x0071 | 
NMI_INTERRUPT_UMAC_FATAL
Jul 17 15:13:31 Lappy kernel: [   85.320166] iwlwifi :3b:00.0: 0x00A022F0 | 
trm_hw_status0
Jul 17 15:13:31 Lappy kernel: [   85.320167] iwlwifi :3b:00.0: 0x | 
trm_hw_status1
Jul 17 15:13:31 Lappy kernel: [   85.320168] iwlwifi :3b:00.0: 0x004882F2 | 
branchlink2
Jul 17 15:13:31 Lappy kernel: [   85.320169] iwlwifi :3b:00.0: 0x004793A2 | 
interruptlink1
Jul 17 15:13:31 Lappy kernel: [   85.320171] iwlwifi :3b:00.0: 0x00480EA2 | 
interruptlink2
Jul 17 15:13:31 Lappy kernel: [   85.320172] iwlwifi :3b:00.0: 0x0001A7D2 | 
data1
Jul 17 15:13:31 Lappy kernel: [   85.320173] iwlwifi :3b:00.0: 0x1000 | 
data2
Jul 17 15:13:31 Lappy kernel: [   85.320174] iwlwifi :3b:00.0: 0xE008 | 
data3
Jul 17 15:13:31 Lappy kernel: [   85.320176] iwlwifi :3b:00.0: 0x | 
beacon time
Jul 17 15:13:31 Lappy kernel: [   85.320177] iwlwifi :3b:00.0: 0x0003ED44 | 
tsf low
Jul 17 15:13:31 Lappy kernel: [   85.320178] iwlwifi :3b:00.0: 0x | 
tsf hi
Jul 17 15:13:31 Lappy kernel: [   85.320180] iwlwifi :3b:00.0: 0x | 
time gp1
Jul 17 15:13:31 Lappy kernel: [   85.320181] iwlwifi :3b:00.0: 0x0003ED44 | 
time gp2
Jul 17 15:13:31 Lappy kernel: [   85.320182] iwlwifi :3b:00.0: 0x0001 | 
uCode revision 

[Bug 1836858] Re: i915: Display flickers during "flickerfree" boot

2019-07-17 Thread Daniel van Vugt
I've now found this occurs on an HP laptop, as well as a Lenovo desktop.

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

Title:
  i915: Display flickers during "flickerfree" boot

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

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

[Bug 1836983] Re: [Intel CyclonePeak] Pairing new BT mouse fails sometimes

2019-07-17 Thread AceLan Kao
commit dbcc2fb9a18de0116bd5d92a9435417b6a842cb8
Author: Amit K Bag 
Date:   Wed Jul 10 16:53:17 2019 +0530

linux-firmware: Update firmware file for Intel Bluetooth 22161

This patch updates new firmware file for Intel Bluetooth 22161
Also it is known as Intel CyclonePeak (CcP).

FW Build: REL0310

Release Version: 21.30.0.4

Signed-off-by: Amit K Bag 
Signed-off-by: Josh Boyer 

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

Title:
  [Intel CyclonePeak] Pairing new BT mouse fails sometimes

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

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

[Bug 1836949] Re: mtu gets lost in translation from netplan (v2) yaml

2019-07-17 Thread Server Team CI bot
This bug is fixed with commit 5498107d to cloud-init on branch master.
To view that commit see the following URL:
https://git.launchpad.net/cloud-init/commit/?id=5498107d


** Changed in: cloud-init
   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/1836949

Title:
  mtu gets lost in translation from netplan (v2) yaml

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

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

[Bug 1836828] Re: Kodi crashes when trying to play any video

2019-07-17 Thread Tom Lake
Kodi can't load radeonsi_dri.so

There used to occur this same issue with Steam, 
maybe we have here conflicting libraries?

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

Title:
  Kodi crashes when trying to play any video

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

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

[Bug 1836983] [NEW] [Intel CyclonePeak] Pairing new BT mouse fails sometimes

2019-07-17 Thread AceLan Kao
Public bug reported:

[Impact]
After update the BT firmware, it requires to pair twice to pair a new device.
There should be a "SMP: Pairing Request" send from hci0, but it doesn't be 
submitted in the first time.

[Fix]
The new firmware fix this issue.

[Test]
Verified on Dell platforms with BT Designer Mouse(DF:29:ED:BD:82:95)

[Regression Potential]
Low, the firmware is newly added for new Cyclone Peak wifi/bt, and it won't 
affect the devices on the market currently.

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

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

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

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

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

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

Title:
  [Intel CyclonePeak] Pairing new BT mouse fails sometimes

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

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

[Bug 1641290] Re: [04f3:0903] Elan Microelectronics Corp fingerprint reader not recognised

2019-07-17 Thread Diogo Falcomer
Here i have the same issue, and plus the right touchpad button doesn`t
work too.

I`m using  ubuntu 19.04 in a Notebook xiaomi air 13 (2017).


Bus 001 Device 004: ID 04f3:0c1a Elan Microelectronics Corp

:~$ fprintd-enroll 
list_devices failed: No devices available

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

Title:
  [04f3:0903] Elan Microelectronics Corp fingerprint reader not
  recognised

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

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

[Bug 1836938] Re: falkon failed to load some pages

2019-07-17 Thread Chris Guiver
I've been using falkon for launchpad quite a lot recently, so opened
term &

guiverc@d960-ubu2:~$   falkon duckduckgo.com
Attribute Qt::AA_ShareOpenGLContexts must be set before QCoreApplication is 
created.
guiverc@d960-ubu2:~$ 

>From duckduckgo I searched & went to spigel.de & looked at some photos without 
>issue.
Currently I'm still running older 5.0.0-20 kernel (haven't rebooted yet) but 
identical falkon package

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

Title:
  falkon failed to load some pages

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

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

[Bug 1836961] Re: ansible 2.0.0.2-2ubuntu1.2 uninstallable on Ubuntu 16.04

2019-07-17 Thread Steve Langasek
** Changed in: ansible (Ubuntu Xenial)
 Assignee: (unassigned) => Paulo Flabiano Smorigo (pfsmorigo)

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

Title:
  ansible 2.0.0.2-2ubuntu1.2 uninstallable on Ubuntu 16.04

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

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

[Bug 1836960] Re: Gnome on Ubuntu 18.04.2 LTS text copying triggers apparently useless file writes

2019-07-17 Thread Thinking Torus
** Also affects: gnome-shell (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: nautilus (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/1836960

Title:
  Gnome on Ubuntu 18.04.2 LTS text copying triggers apparently useless
  file writes

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

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

[Bug 1836979] Re: Kodi crashes with “nouveau_vp3_video_buffer_create: Assertion `templat->interlaced' failed”

2019-07-17 Thread Tina Russell
In that same update, I also upgraded the Mesa package:

2019-07-07 06:50:41 upgrade libegl-mesa0:amd64 18.2.8-0ubuntu0~18.04.2 
19.0.2-1ubuntu1.1~18.04.1
2019-07-07 06:50:41 status half-configured libegl-mesa0:amd64 
18.2.8-0ubuntu0~18.04.2
2019-07-07 06:50:41 status unpacked libegl-mesa0:amd64 18.2.8-0ubuntu0~18.04.2
2019-07-07 06:50:41 status half-installed libegl-mesa0:amd64 
18.2.8-0ubuntu0~18.04.2
2019-07-07 06:50:42 status half-installed libegl-mesa0:amd64 
18.2.8-0ubuntu0~18.04.2
2019-07-07 06:50:42 status unpacked libegl-mesa0:amd64 19.0.2-1ubuntu1.1~18.04.1
2019-07-07 06:50:42 status unpacked libegl-mesa0:amd64 19.0.2-1ubuntu1.1~18.04.1
2019-07-07 06:50:42 upgrade libgbm1:amd64 18.2.8-0ubuntu0~18.04.2 
19.0.2-1ubuntu1.1~18.04.1
2019-07-07 06:50:42 status half-configured libgbm1:amd64 18.2.8-0ubuntu0~18.04.2
2019-07-07 06:50:43 status unpacked libgbm1:amd64 18.2.8-0ubuntu0~18.04.2
2019-07-07 06:50:43 status half-installed libgbm1:amd64 18.2.8-0ubuntu0~18.04.2
2019-07-07 06:50:43 status half-installed libgbm1:amd64 18.2.8-0ubuntu0~18.04.2
2019-07-07 06:50:43 status unpacked libgbm1:amd64 19.0.2-1ubuntu1.1~18.04.1
2019-07-07 06:50:43 status unpacked libgbm1:amd64 19.0.2-1ubuntu1.1~18.04.1
2019-07-07 06:50:43 install libllvm8:i386  1:8-3~ubuntu18.04.1
2019-07-07 06:50:43 status half-installed libllvm8:i386 1:8-3~ubuntu18.04.1
2019-07-07 06:50:48 status unpacked libllvm8:i386 1:8-3~ubuntu18.04.1
2019-07-07 06:50:48 status unpacked libllvm8:i386 1:8-3~ubuntu18.04.1
2019-07-07 06:50:49 upgrade libgl1-mesa-dri:amd64 18.2.8-0ubuntu0~18.04.2 
19.0.2-1ubuntu1.1~18.04.1
2019-07-07 06:50:49 status half-configured libgl1-mesa-dri:amd64 
18.2.8-0ubuntu0~18.04.2
2019-07-07 06:50:49 status unpacked libgl1-mesa-dri:amd64 
18.2.8-0ubuntu0~18.04.2
2019-07-07 06:50:49 status half-configured libgl1-mesa-dri:i386 
18.2.8-0ubuntu0~18.04.2
2019-07-07 06:50:49 status half-installed libgl1-mesa-dri:amd64 
18.2.8-0ubuntu0~18.04.2
2019-07-07 06:50:51 status half-installed libgl1-mesa-dri:amd64 
18.2.8-0ubuntu0~18.04.2
2019-07-07 06:50:51 status unpacked libgl1-mesa-dri:amd64 
19.0.2-1ubuntu1.1~18.04.1
2019-07-07 06:50:51 status unpacked libgl1-mesa-dri:amd64 
19.0.2-1ubuntu1.1~18.04.1
2019-07-07 06:50:51 upgrade libgl1-mesa-dri:i386 18.2.8-0ubuntu0~18.04.2 
19.0.2-1ubuntu1.1~18.04.1
2019-07-07 06:50:51 status half-configured libgl1-mesa-dri:i386 
18.2.8-0ubuntu0~18.04.2
2019-07-07 06:50:51 status unpacked libgl1-mesa-dri:i386 18.2.8-0ubuntu0~18.04.2
2019-07-07 06:50:52 status half-installed libgl1-mesa-dri:i386 
18.2.8-0ubuntu0~18.04.2
2019-07-07 06:50:53 status half-installed libgl1-mesa-dri:i386 
18.2.8-0ubuntu0~18.04.2
2019-07-07 06:50:54 status unpacked libgl1-mesa-dri:i386 
19.0.2-1ubuntu1.1~18.04.1
2019-07-07 06:50:54 status unpacked libgl1-mesa-dri:i386 
19.0.2-1ubuntu1.1~18.04.1
2019-07-07 06:50:54 install libllvm8:amd64  1:8-3~ubuntu18.04.1
2019-07-07 06:50:54 status half-installed libllvm8:amd64 1:8-3~ubuntu18.04.1
2019-07-07 06:50:58 status unpacked libllvm8:amd64 1:8-3~ubuntu18.04.1
2019-07-07 06:50:58 status unpacked libllvm8:amd64 1:8-3~ubuntu18.04.1
2019-07-07 06:50:59 upgrade libglx-mesa0:i386 18.2.8-0ubuntu0~18.04.2 
19.0.2-1ubuntu1.1~18.04.1
2019-07-07 06:50:59 status half-configured libglx-mesa0:i386 
18.2.8-0ubuntu0~18.04.2
2019-07-07 06:50:59 status unpacked libglx-mesa0:i386 18.2.8-0ubuntu0~18.04.2
2019-07-07 06:50:59 status half-configured libglx-mesa0:amd64 
18.2.8-0ubuntu0~18.04.2
2019-07-07 06:50:59 status half-installed libglx-mesa0:i386 
18.2.8-0ubuntu0~18.04.2
2019-07-07 06:50:59 status half-installed libglx-mesa0:i386 
18.2.8-0ubuntu0~18.04.2
2019-07-07 06:51:00 status unpacked libglx-mesa0:i386 19.0.2-1ubuntu1.1~18.04.1
2019-07-07 06:51:00 status unpacked libglx-mesa0:i386 19.0.2-1ubuntu1.1~18.04.1
2019-07-07 06:51:00 upgrade libglx-mesa0:amd64 18.2.8-0ubuntu0~18.04.2 
19.0.2-1ubuntu1.1~18.04.1
2019-07-07 06:51:00 status half-configured libglx-mesa0:amd64 
18.2.8-0ubuntu0~18.04.2
2019-07-07 06:51:00 status unpacked libglx-mesa0:amd64 18.2.8-0ubuntu0~18.04.2
2019-07-07 06:51:00 status half-installed libglx-mesa0:amd64 
18.2.8-0ubuntu0~18.04.2
2019-07-07 06:51:01 status half-installed libglx-mesa0:amd64 
18.2.8-0ubuntu0~18.04.2
2019-07-07 06:51:01 status unpacked libglx-mesa0:amd64 19.0.2-1ubuntu1.1~18.04.1
2019-07-07 06:51:01 status unpacked libglx-mesa0:amd64 19.0.2-1ubuntu1.1~18.04.1
2019-07-07 06:51:01 upgrade libglapi-mesa:amd64 18.2.8-0ubuntu0~18.04.2 
19.0.2-1ubuntu1.1~18.04.1
2019-07-07 06:51:01 status half-configured libglapi-mesa:amd64 
18.2.8-0ubuntu0~18.04.2
2019-07-07 06:51:01 status unpacked libglapi-mesa:amd64 18.2.8-0ubuntu0~18.04.2
2019-07-07 06:51:01 status half-configured libglapi-mesa:i386 
18.2.8-0ubuntu0~18.04.2
2019-07-07 06:51:02 status half-installed libglapi-mesa:amd64 
18.2.8-0ubuntu0~18.04.2
2019-07-07 06:51:02 status half-installed libglapi-mesa:amd64 
18.2.8-0ubuntu0~18.04.2
2019-07-07 06:51:02 status unpacked libglapi-mesa:amd64 
19.0.2-1ubuntu1.1~18.04.1
2019-07-07 

[Bug 1836960] Re: Gnome on Ubuntu 18.04.2 LTS text copying triggers apparently useless file writes

2019-07-17 Thread Ubuntu Foundations Team Bug Bot
Thank you for taking the time to report this bug and helping to make
Ubuntu better.  It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general.  It is important that bug reports be filed about source
packages so that people interested in the package can find the bugs
about it.  You can find some hints about determining what package your
bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage.
You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit
https://bugs.launchpad.net/ubuntu/+bug/1836960/+editstatus and add the
package name in the text box next to the word Package.

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: bot-comment

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

Title:
  Gnome on Ubuntu 18.04.2 LTS text copying triggers apparently useless
  file writes

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

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

[Bug 1836975] Re: bluebird-gtk-theme 1.3-1 window borders incompatible with Cinnamon >= 3.8 and don't appear in the theme application menu

2019-07-17 Thread Ubuntu Foundations Team Bug Bot
The attachment "bluebird-gtk-theme_1.3-1ubuntu1-disco.debdiff" seems to
be a debdiff.  The ubuntu-sponsors team has been subscribed to the bug
report so that they can review and hopefully sponsor the debdiff.  If
the attachment isn't a patch, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are member of the
~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

Title:
  bluebird-gtk-theme 1.3-1 window borders incompatible with Cinnamon >=
  3.8 and don't appear in the theme application menu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluebird-gtk-theme/+bug/1836975/+subscriptions

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

[Bug 1836979] [NEW] Kodi crashes with “nouveau_vp3_video_buffer_create: Assertion `templat->interlaced' failed”

2019-07-17 Thread Tina Russell
Public bug reported:

I’m not exactly sure if this belongs here, libva, mesa, or upstream
somewhere. But, it doesn’t seem to be a Kodi bug, buggy is that program
is.

Kodi has worked just fine on my system, as recently as July 7th of this
year, but yesterday (July 16) I tried Kodi again: I got a blank screen
and a pause for a few moments, followed by an unceremonious crash-to-
desktop. This happens every time I start Kodi, now.

If I run it through the command-line, I get this:

libva info: VA-API version 1.1.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/nouveau_drv_video.so
libva info: Found init function __vaDriverInit_1_1
libva info: va_openDriver() returns 0
kodi-x11: ../src/gallium/drivers/nouveau/nouveau_vp3_video.c:91: 
nouveau_vp3_video_buffer_create: Assertion `templat->interlaced' failed.
Aborted (core dumped)

I’ve been using the same version of Kodi (“18.3 Git:20190621-89472b7”,
package version 2:18.3+git20190621.1610-final-0bionic, from the Team-
XBMC PPA) since its release in June, but in between July 7th and 16th, I
did upgrade Nouveau:

2019-07-07 06:51:44 configure libdrm-nouveau2:amd64 2.4.97-ubuntu1~18.04.1 

2019-07-07 06:51:44 status unpacked libdrm-nouveau2:amd64 
2.4.97-1ubuntu1~18.04.1
2019-07-07 06:51:44 status half-configured libdrm-nouveau2:amd64 
2.4.97-1ubuntu1~18.04.1
2019-07-07 06:51:44 status installed libdrm-nouveau2:amd64 
2.4.97-1ubuntu1~18.04.1
2019-07-07 06:51:44 configure libdrm-nouveau2:i386 2.4.97-1ubuntu1~18.04.1 

2019-07-07 06:51:44 status unpacked libdrm-nouveau2:i386 2.4.97-1ubuntu1~18.04.1
2019-07-07 06:51:44 status half-configured libdrm-nouveau2:i386 
2.4.97-1ubuntu1~18.04.1
2019-07-07 06:51:44 status installed libdrm-nouveau2:i386 
2.4.97-1ubuntu1~18.04.1

(Another reason I’m guessing this is a Nouveau problem is because I
later tried switching to the official NVidia drivers, didn’t get this
bug, and then later encountered a distinct yet worse bug that locks up
the whole system. So, now I’m back to using Nouveau.)

I tried looking in Xorg.0.log:

[ 17185.557] (II) NOUVEAU(0): EDID vendor "SEC", prod id 12620
[ 17185.557] (II) NOUVEAU(0): Printing DDC gathered Modelines:
[ 17185.558] (II) NOUVEAU(0): Modeline "1366x768"x0.0   72.33  1366 1414 1446 
1526  768 770 775 790 -hsync -vsync (47.4 kHz eP)

…that’s all that appears in the log when I try to load Kodi and a crash
happens.

I’m using Ubuntu MATE 18.04.2 LTS 64-bit on a Compaq Presario CQ60; if
you need more information, I’ve attached a hardinfo report, too. I hope
this bug can get fixed, soon. Thanks!

** Affects: xserver-xorg-video-nouveau (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "Information on Tina’s hardware"
   
https://bugs.launchpad.net/bugs/1836979/+attachment/5277708/+files/hardinfo_report_2019-07-17.html

** Description changed:

  I’m not exactly sure if this belongs here, libva, mesa, or upstream
  somewhere. But, it doesn’t seem to be a Kodi bug, buggy is that program
  is.
  
  Kodi has worked just fine on my system, as recently as July 7th of this
  year, but yesterday (July 16) I tried Kodi again: I got a blank screen
  and a pause for a few moments, followed by an unceremonious crash-to-
  desktop. This happens every time I start Kodi, now.
  
  If I run it through the command-line, I get this:
  
  libva info: VA-API version 1.1.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/nouveau_drv_video.so
  libva info: Found init function __vaDriverInit_1_1
  libva info: va_openDriver() returns 0
  kodi-x11: ../src/gallium/drivers/nouveau/nouveau_vp3_video.c:91: 
nouveau_vp3_video_buffer_create: Assertion `templat->interlaced' failed.
  Aborted (core dumped)
  
  I’ve been using the same version of Kodi (“18.3 Git:20190621-89472b7”,
  package version 2:18.3+git20190621.1610-final-0bionic, from the Team-
- XBMC PPA) for months, but in between July 7th and 16th, I did upgrade
- Nouveau:
+ XBMC PPA) since its release in June, but in between July 7th and 16th, I
+ did upgrade Nouveau:
  
  2019-07-16 17:33:05 upgrade libdrm-nouveau2:amd64 2.4.97-1ubuntu1~18.04.1 
2.4.97-1ubuntu1~18.04.1
  2019-07-16 17:33:05 status half-configured libdrm-nouveau2:amd64 
2.4.97-1ubuntu1~18.04.1
  2019-07-16 17:33:05 status unpacked libdrm-nouveau2:amd64 
2.4.97-1ubuntu1~18.04.1
  2019-07-16 17:33:05 status half-installed libdrm-nouveau2:amd64 
2.4.97-1ubuntu1~18.04.1
  2019-07-16 17:33:05 status half-installed libdrm-nouveau2:amd64 
2.4.97-1ubuntu1~18.04.1
  2019-07-16 17:33:05 status unpacked libdrm-nouveau2:amd64 
2.4.97-1ubuntu1~18.04.1
  2019-07-16 17:33:05 status unpacked libdrm-nouveau2:amd64 
2.4.97-1ubuntu1~18.04.1
  2019-07-16 17:33:06 upgrade libdrm-nouveau2:i386 2.4.97-1ubuntu1~18.04.1 
2.4.97-1ubuntu1~18.04.1
  2019-07-16 17:33:06 status half-configured libdrm-nouveau2:i386 
2.4.97-1ubuntu1~18.04.1
  2019-07-16 17:33:06 status unpacked libdrm-nouveau2:i386 

[Bug 1836960] Re: Gnome on Ubuntu 18.04.2 LTS text copying triggers apparently useless file writes

2019-07-17 Thread Thinking Torus
** Also affects: ubuntu-meta (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/1836960

Title:
  Gnome on Ubuntu 18.04.2 LTS text copying triggers apparently useless
  file writes

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

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

[Bug 1836828] Re: Kodi crashes when trying to play any video

2019-07-17 Thread Tom Lake
If I disable VDPAU from Settings/Player and leave enabled just VAAPI,
Kodi works.

So it must be a specific misconfiguration with VDPAU.

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

Title:
  Kodi crashes when trying to play any video

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

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

[Bug 1836975] Re: bluebird-gtk-theme 1.3-1 window borders incompatible with Cinnamon >= 3.8 and don't appear in the theme application menu

2019-07-17 Thread Connor Kuehl
** Description changed:

+ [Impact]
+ 
  The Cinnamon package shipped in the Ubuntu 19.04 repositories is >=
  Cinnamon 3.8. This version of Cinnamon only supports window border
  themes which are metacity-3 compliant [1].
  
  The Bluebird theme's upstream git repository has already been updated
  with metacity-3 compliance [2] but this change has not made its way into
  the Ubuntu package.
  
+ This means that while the package is installable, the theme will not be
+ selectable in Cinnamon's Theme application for selecting window borders
+ (it won't even appear as an option).
+ 
+ [Test Case]
+ 
+ Install `bluebird-gtk-theme`, open the "Themes" application and click on
+ "Window Borders"
+ 
+ Expected result: Bluebird window borders appear as an option, maybe
+ selected, and the window borders activate.
+ 
+ Actual result: Bluebird window borders are absent from the window
+ borders selection menu.
+ 
+ [Regression Potential]
+ 
+ This doesn't modify any of the rest of the theme, but only installs
+ metacity-3 support. In using the theme I haven't experienced any
+ oddities.
+ 
  [1] https://blog.linuxmint.com/?p=3557 Change log entry: "Titlebar
  themes are now restricted to metacity-3"
  
  [2]
  
https://github.com/shimmerproject/Bluebird/commit/12af472e008100153429c88eff8cd3d546b017e9

** Description changed:

  [Impact]
  
  The Cinnamon package shipped in the Ubuntu 19.04 repositories is >=
  Cinnamon 3.8. This version of Cinnamon only supports window border
  themes which are metacity-3 compliant [1].
  
  The Bluebird theme's upstream git repository has already been updated
  with metacity-3 compliance [2] but this change has not made its way into
  the Ubuntu package.
  
  This means that while the package is installable, the theme will not be
  selectable in Cinnamon's Theme application for selecting window borders
  (it won't even appear as an option).
  
  [Test Case]
  
  Install `bluebird-gtk-theme`, open the "Themes" application and click on
  "Window Borders"
  
- Expected result: Bluebird window borders appear as an option, maybe
+ Expected result: Bluebird window borders appear as an option, may be
  selected, and the window borders activate.
  
  Actual result: Bluebird window borders are absent from the window
  borders selection menu.
  
  [Regression Potential]
  
  This doesn't modify any of the rest of the theme, but only installs
  metacity-3 support. In using the theme I haven't experienced any
  oddities.
  
  [1] https://blog.linuxmint.com/?p=3557 Change log entry: "Titlebar
  themes are now restricted to metacity-3"
  
  [2]
  
https://github.com/shimmerproject/Bluebird/commit/12af472e008100153429c88eff8cd3d546b017e9

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

Title:
  bluebird-gtk-theme 1.3-1 window borders incompatible with Cinnamon >=
  3.8 and don't appear in the theme application menu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluebird-gtk-theme/+bug/1836975/+subscriptions

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

[Bug 1835091] Re: subiquity crashes upon reusing failed to assemble raid member partition

2019-07-17 Thread Michael Hudson-Doyle
So, no, neither case here is fixed in the latest subiquity :/ I'll try
to make vmtest testcases for curtin.

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

Title:
  subiquity crashes upon reusing failed to assemble raid member
  partition

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

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

[Bug 1836975] Re: bluebird-gtk-theme 1.3-1 window borders incompatible with Cinnamon >= 3.8 and don't appear in the theme application menu

2019-07-17 Thread Connor Kuehl
Attaching .debdiff for Disco to this comment.

** Patch added: "bluebird-gtk-theme_1.3-1ubuntu1-disco.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/bluebird-gtk-theme/+bug/1836975/+attachment/5277706/+files/bluebird-gtk-theme_1.3-1ubuntu1-disco.debdiff

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

Title:
  bluebird-gtk-theme 1.3-1 window borders incompatible with Cinnamon >=
  3.8 and don't appear in the theme application menu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluebird-gtk-theme/+bug/1836975/+subscriptions

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

[Bug 1836975] Re: bluebird-gtk-theme 1.3-1 window borders incompatible with Cinnamon >= 3.8 and don't appear in the theme application menu

2019-07-17 Thread Connor Kuehl
Sorry, comment #2 should read "Attaching .debdiff for Eoan to this
comment"

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

Title:
  bluebird-gtk-theme 1.3-1 window borders incompatible with Cinnamon >=
  3.8 and don't appear in the theme application menu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluebird-gtk-theme/+bug/1836975/+subscriptions

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

[Bug 1836975] [NEW] bluebird-gtk-theme 1.3-1 window borders incompatible with Cinnamon >= 3.8 and don't appear in the theme application menu

2019-07-17 Thread Connor Kuehl
Public bug reported:

The Cinnamon package shipped in the Ubuntu 19.04 repositories is >=
Cinnamon 3.8. This version of Cinnamon only supports window border
themes which are metacity-3 compliant [1].

The Bluebird theme's upstream git repository has already been updated
with metacity-3 compliance [2] but this change has not made its way into
the Ubuntu package.

[1] https://blog.linuxmint.com/?p=3557 Change log entry: "Titlebar
themes are now restricted to metacity-3"

[2]
https://github.com/shimmerproject/Bluebird/commit/12af472e008100153429c88eff8cd3d546b017e9

** Affects: bluebird-gtk-theme (Ubuntu)
 Importance: Medium
 Assignee: Connor Kuehl (connork)
 Status: In Progress

** Affects: bluebird-gtk-theme (Ubuntu Disco)
 Importance: Medium
 Assignee: Connor Kuehl (connork)
 Status: In Progress

** Affects: bluebird-gtk-theme (Ubuntu Eoan)
 Importance: Medium
 Assignee: Connor Kuehl (connork)
 Status: In Progress

** Also affects: bluebird-gtk-theme (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** Also affects: bluebird-gtk-theme (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Changed in: bluebird-gtk-theme (Ubuntu Disco)
   Status: New => In Progress

** Changed in: bluebird-gtk-theme (Ubuntu Eoan)
   Status: New => In Progress

** Changed in: bluebird-gtk-theme (Ubuntu Disco)
 Assignee: (unassigned) => Connor Kuehl (connork)

** Changed in: bluebird-gtk-theme (Ubuntu Eoan)
 Assignee: (unassigned) => Connor Kuehl (connork)

** Changed in: bluebird-gtk-theme (Ubuntu Eoan)
   Importance: Undecided => Medium

** Changed in: bluebird-gtk-theme (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/1836975

Title:
  bluebird-gtk-theme 1.3-1 window borders incompatible with Cinnamon >=
  3.8 and don't appear in the theme application menu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluebird-gtk-theme/+bug/1836975/+subscriptions

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

[Bug 1836975] Re: bluebird-gtk-theme 1.3-1 window borders incompatible with Cinnamon >= 3.8 and don't appear in the theme application menu

2019-07-17 Thread Connor Kuehl
Attaching .debdiff for Disco to this comment (it's identical, the
changelog release is different though).

** Patch added: "bluebird-gtk-theme_1.3-1ubuntu1-eoan.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/bluebird-gtk-theme/+bug/1836975/+attachment/5277707/+files/bluebird-gtk-theme_1.3-1ubuntu1-eoan.debdiff

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

Title:
  bluebird-gtk-theme 1.3-1 window borders incompatible with Cinnamon >=
  3.8 and don't appear in the theme application menu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluebird-gtk-theme/+bug/1836975/+subscriptions

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

[Bug 1836971] Missing required logs.

2019-07-17 Thread Ubuntu Kernel Bot
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1836971

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

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

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

** Tags added: bionic

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

Title:
  sched: Prevent CPU lockups when task groups take longer than the
  period

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

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

[Bug 1768169] Re: touchscreen doesn't work properly after stylus detection

2019-07-17 Thread Ian D. Scott
The problem should be fixed in git, and available in the 1.14.0.


I don't think there's a workaround other than building from source; but it 
should be possible to address it that way.

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

Title:
  touchscreen doesn't work properly after stylus detection

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

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

[Bug 1836971] [NEW] sched: Prevent CPU lockups when task groups take longer than the period

2019-07-17 Thread Matthew Ruffell
Public bug reported:

BugLink: https://bugs.launchpad.net/bugs/1836971

[Impact]

On machines with extremely high CPU usage, parent task groups which have
a large number of children can make the for loop in
sched_cfs_period_timer() run until the watchdog fires when the
cfs_period_us setting is too short.

In this particular case, it is unlikely that the call to
hrtimer_forward_now() will return 0, meaning the for loop is never left,
and tasks are never rescheduled.

The large number of children makes do_sched_cfs_period_timer() take
longer than the period, which impacts calls to hrtimer_forward_now().

The kernel will produce this call trace:

CPU: 51 PID: 0 Comm: swapper/51 Tainted: P OELK 4.15.0-50-generic
#54-Ubuntu

Call Trace:

? sched_clock+0x9/0x10
walk_tg_tree_from+0x61/0xd0
? task_rq_unlock+0x30/0x30
unthrottle_cfs_rq+0xcb/0x1a0
distribute_cfs_runtime+0xd7/0x100
sched_cfs_period_timer+0xd9/0x1a0
? sched_cfs_slack_timer+0xe0/0xe0
__hrtimer_run_queues+0xdf/0x230
hrtimer_interrupt+0xa0/0x1d0
smp_apic_timer_interrupt+0x6f/0x130
apic_timer_interrupt+0x84/0x90


This has been hit in production in a particularly highly utilised hadoop
cluster which is powering an analytics platform. About 30% of the
cluster experiences this issue every week, and the machines need a
manual reboot to get back online.

[Fix]

This was fixed in 5.1 upstream with the below commit:

commit 2e8e19226398db8265a8e675fcc0118b9e80c9e8
Author: Phil Auld 
Date: Tue Mar 19 09:00:05 2019 -0400
subject: sched/fair: Limit sched_cfs_period_timer() loop to avoid hard lockup

This commit adds a check to see if the loop has run too many times, and if it
has, scales up the period and quota, so the timer can complete before the
next period expires, which enables the task to be rescheduled normally.

Note, 2e8e19226398db8265a8e675fcc0118b9e80c9e8 was included in upstream
stable versions 4.4.179, 4.9.171, 4.14.114, 4.19.37, 5.0.10.

Please cherry pick 2e8e19226398db8265a8e675fcc0118b9e80c9e8 to all bionic
kernels.

[Testcase]

Kind of hard to reproduce, so this was tested on a production hadoop cluster
with extremely high CPU load.

I built a test kernel, which is available here:

https://launchpad.net/~mruffell/+archive/ubuntu/sf232784-test

For unpatched kernels, expect the machine to lockup and print the call
trace in the impact section.

For patched kernels, if the machine hits the condition, it will print a
warning to the kernel log with the new period and quota which has been
used:

Example from the same hadoop cluster with a machine running the test
kernel:

% uname -a
4.15.0-50-generic #54+hf232784v20190626b1-Ubuntu
% sudo grep cfs /var/log/kern.log.*
cfs_period_timer[cpu40]: period too short, scaling up (new cfs_period_us 67872, 
cfs_quota_us = 3475091)
cfs_period_timer[cpu48]: period too short, scaling up (new cfs_period_us 22430, 
cfs_quota_us = 1148437)
cfs_period_timer[cpu48]: period too short, scaling up (new cfs_period_us 25759, 
cfs_quota_us = 1318908)
cfs_period_timer[cpu68]: period too short, scaling up (new cfs_period_us 29583, 
cfs_quota_us = 1514684)
cfs_period_timer[cpu49]: period too short, scaling up (new cfs_period_us 33974, 
cfs_quota_us = 1739519)
cfs_period_timer[cpu3]: period too short, scaling up (new cfs_period_us 39017, 
cfs_quota_us = 1997729)
cfs_period_timer[cpu10]: period too short, scaling up (new cfs_period_us 44809, 
cfs_quota_us = 2294267)
cfs_period_timer[cpu3]: period too short, scaling up (new cfs_period_us 51460, 
cfs_quota_us = 2634823)
cfs_period_timer[cpu3]: period too short, scaling up (new cfs_period_us 59099, 
cfs_quota_us = 3025929)
cfs_period_timer[cpu3]: period too short, scaling up (new cfs_period_us 67872, 
cfs_quota_us = 3475091)

[Regression Potential]
This patch was accepted into upstream stable versions 4.4.179, 4.9.171,
4.14.114, 4.19.37, 5.0.10, and is thus treated as stable and trusted by the
community.

Xenial received this patch in 4.4.0-150.176, as per LP #1828420
Disco will receive this patch in the next version, as per LP #1830922
Eoan already has the patch, being based on 5.2.

While this does effect a core part of the kernel, the scheduler, the
patch has been extensively tested, and it has been proven in production
environments, so the overall risk is low.

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

** Affects: linux (Ubuntu Bionic)
 Importance: Medium
 Assignee: Matthew Ruffell (mruffell)
 Status: In Progress


** Tags: sts

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

** Tags added: sts

** Description changed:

- BugLink: https://bugs.launchpad.net/bugs/
+ BugLink: https://bugs.launchpad.net/bugs/1836971
  
  [Impact]
  
- On machines with extremely high CPU usage, parent task groups which have a 
large
- number of children can make the for loop in sched_cfs_period_timer() run 
until 
- the watchdog fires when the cfs_period_us setting is too short.
+ On machines with extremely high CPU 

[Bug 1836970] [NEW] I cannot get permission to move any files or access drives

2019-07-17 Thread lew1950
Public bug reported:

I have tried everything to recover from an upgrade to bionic beaver. It has 
changed my permissions to root and I cannot change that back I have all my work 
and music saved on here. I have tried chmod but it ignores it I also in the 
past used Krusader  in the sudo it would change files easily none of these work 
anymore and I have a book on here that I need to save.
desperate!!

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14.12
ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-15-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CasperVersion: 1.394
Date: Wed Jul 17 22:56:23 2019
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
boot=casper only-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic ubiquity-18.04.14.12 ubuntu

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

Title:
  I cannot get permission to move any files or access drives

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

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

[Bug 1836961] Re: ansible 2.0.0.2-2ubuntu1.2 uninstallable on Ubuntu 16.04

2019-07-17 Thread William Grant
** Also affects: ansible (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: ansible (Ubuntu)
   Status: Confirmed => Invalid

** Tags added: regression-update

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

Title:
  ansible 2.0.0.2-2ubuntu1.2 uninstallable on Ubuntu 16.04

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

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

[Bug 1836961] Re: ansible 2.0.0.2-2ubuntu1.2 uninstallable on Ubuntu 16.04

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

** Changed in: ansible (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/1836961

Title:
  ansible 2.0.0.2-2ubuntu1.2 uninstallable on Ubuntu 16.04

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

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

[Bug 1836961] Re: ansible 2.0.0.2-2ubuntu1.2 uninstallable on Ubuntu 16.04

2019-07-17 Thread William Grant
I've rolled xenial-updates and xenial-security back to ansible
2.0.0.2-2ubuntu1.1 to mitigate the breakage for now.

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

Title:
  ansible 2.0.0.2-2ubuntu1.2 uninstallable on Ubuntu 16.04

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

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

[Bug 1516451] Re: check_disk plugin broken after upgrade to 15.10

2019-07-17 Thread Bryce Harrington
Meanwhile, I've verified the issue seems relevant for newer ubuntu's
too:

### Bionic
# /usr/lib/nagios/plugins/check_disk -w '20%' -c '10%' -e
DISK CRITICAL - /sys/kernel/debug/tracing is not accessible: Permission denied

### Eoan
# /usr/lib/nagios/plugins/check_disk -w '20%' -c '10%' -e
DISK CRITICAL - /sys/kernel/debug/tracing is not accessible: Permission denied

The issue was reported to Debian but don't think an action was taken on it:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910267

Upstream also has recommendation to exclude tracefs for this issue:
http://www.dailyithelp.com/nagios-disk-critical-syskerneldebugtracing-is-not-accessible-permission/


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

** Changed in: nagios-plugins (Ubuntu)
   Status: Incomplete => Triaged

** Changed in: nagios-plugins (Ubuntu)
   Importance: Medium => High

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

Title:
  check_disk plugin broken after upgrade to 15.10

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

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

[Bug 1836456] Re: [ThinkPad S1 Yoga] Machine Immediately Wakes Up From Suspend

2019-07-17 Thread Stefano Coronado
@kaihengfeng

This did not solve the issue.

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

Title:
  [ThinkPad S1 Yoga] Machine Immediately Wakes Up From Suspend

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

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

[Bug 1836968] Re: Bionic update: upstream stable patchset 2019-07-17

2019-07-17 Thread Kamal Mostafa
** Description changed:

+ SRU Justification
  
- SRU Justification
+ Impact:
+    The upstream process for stable tree updates is quite similar
+    in scope to the Ubuntu SRU process, e.g., each patch has to
+    demonstrably fix a bug, and each patch is vetted by upstream
+    by originating either directly from a mainline/stable Linux tree or
+    a minimally backported form of that patch. The following upstream
+    stable patches should be included in the Ubuntu kernel:
  
- Impact:
-The upstream process for stable tree updates is quite similar
-in scope to the Ubuntu SRU process, e.g., each patch has to
-demonstrably fix a bug, and each patch is vetted by upstream
-by originating either directly from a mainline/stable Linux tree or
-a minimally backported form of that patch. The following upstream
-stable patches should be included in the Ubuntu kernel:
+    upstream stable patchset 2019-07-17
  
-upstream stable patchset 2019-07-17
-from git://git.kernel.org/
+ Ported from the following upstream stable releases:
+ v4.14.83, v4.19.4,
+ v4.14.84, v4.19.5,
+ v4.14.85, v4.19.6,
+ v4.14.86, v4.19.7
+ 
+    from git://git.kernel.org/

** Description changed:

  SRU Justification
  
  Impact:
     The upstream process for stable tree updates is quite similar
     in scope to the Ubuntu SRU process, e.g., each patch has to
     demonstrably fix a bug, and each patch is vetted by upstream
     by originating either directly from a mainline/stable Linux tree or
     a minimally backported form of that patch. The following upstream
     stable patches should be included in the Ubuntu kernel:
  
     upstream stable patchset 2019-07-17
  
- Ported from the following upstream stable releases:
- v4.14.83, v4.19.4,
- v4.14.84, v4.19.5,
- v4.14.85, v4.19.6,
- v4.14.86, v4.19.7
+ Ported from the following upstream stable releases:
+ v4.14.83, v4.19.4,
+ v4.14.84, v4.19.5,
+ v4.14.85, v4.19.6,
+ v4.14.86, v4.19.7
  
     from git://git.kernel.org/
+ 
+ flow_dissector: do not dissect l4 ports for fragments
+ ibmvnic: fix accelerated VLAN handling
+ ip_tunnel: don't force DF when MTU is locked
+ ipv6: Fix PMTU updates for UDP/raw sockets in presence of VRF
+ net-gro: reset skb->pkt_type in napi_reuse_skb()
+ sctp: not allow to set asoc prsctp_enable by sockopt
+ tg3: Add PHY reset for 5717/5719/5720 in change ring and flow control paths
+ tuntap: fix multiqueue rx
+ net: systemport: Protect stop from timeout
+ net: qualcomm: rmnet: Fix incorrect assignment of real_dev
+ net: dsa: microchip: initialize mutex before use
+ sctp: fix strchange_flags name for Stream Change Event
+ net: phy: mdio-gpio: Fix working over slow can_sleep GPIOs
+ sctp: not increase stream's incnt before sending addstrm_in request
+ mlxsw: spectrum: Fix IP2ME CPU policer configuration
+ net: smsc95xx: Fix MTU range
+ usbnet: smsc95xx: disable carrier check while suspending
+ inet: frags: better deal with smp races
+ ARM: dts: r8a7791: Correct critical CPU temperature
+ ARM: dts: r8a7793: Correct critical CPU temperature
+ net: bcmgenet: protect stop from timeout
+ tcp: Fix SOF_TIMESTAMPING_RX_HARDWARE to use the latest timestamp during TCP 
coalescing
+ tipc: don't assume linear buffer when reading ancillary data
+ tipc: fix link re-establish failure
+ net/mlx5e: Claim TC hw offloads support only under a proper build config
+ net/mlx5e: Adjust to max number of channles when re-attaching
+ net/mlx5e: Fix selftest for small MTUs
+ l2tp: fix a sock refcnt leak in l2tp_tunnel_register
+ net/mlx5e: IPoIB, Reset QP after channels are closed
+ net: dsa: mv88e6xxx: Fix clearing of stats counters
+ net: phy: realtek: fix RTL8201F sysfs name
+ sctp: define SCTP_SS_DEFAULT for Stream schedulers
+ rxrpc: Fix lockup due to no error backoff after ack transmit error
+ cifs: don't dereference smb_file_target before null check
+ cifs: fix return value for cifs_listxattr
+ arm64: kprobe: make page to RO mode when allocate it
+ ixgbe: fix MAC anti-spoofing filter after VFLR
+ reiserfs: propagate errors from fill_with_dentries() properly
+ hfs: prevent btree data loss on root split
+ hfsplus: prevent btree data loss on root split
+ um: Give start_idle_thread() a return code
+ drm/edid: Add 6 bpc quirk for BOE panel.
+ platform/x86: intel_telemetry: report debugfs failure
+ clk: fixed-rate: fix of_node_get-put imbalance
+ perf symbols: Set PLT entry/header sizes properly on Sparc
+ fs/exofs: fix potential memory leak in mount option parsing
+ clk: samsung: exynos5420: Enable PERIS clocks for suspend
+ apparmor: Fix uninitialized value in aa_split_fqname
+ x86/earlyprintk: Add a force option for 

[Bug 1668771] Re: systemd-resolved negative caching for extended period of time

2019-07-17 Thread Jorge Niedbalski
The proposal to extend the 'cache' option with 'no-negative' has been
merged upstream. I will proceed with the backports to Ubuntu on the
affected LTS releases.

[0] https://github.com/systemd/systemd/pull/13047

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

Title:
  systemd-resolved negative caching for extended period of time

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

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

[Bug 1836211] Re: bcmwl fails to install with recent Eoan (Bad return status for module build on kernel: 5.0.0-20-generic)

2019-07-17 Thread Alexander Browne
** Changed in: bcmwl (Ubuntu)
   Status: Incomplete => 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/1836211

Title:
  bcmwl fails to install with recent Eoan (Bad return status for module
  build on kernel: 5.0.0-20-generic)

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

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

[Bug 1516451] Re: check_disk plugin broken after upgrade to 15.10

2019-07-17 Thread Bryce Harrington
Ramon, thank you for the detailed test case, I was able to run through
it exactly as you described, both as root user (see attached) and as
nagios (with sudo setup).  I suspect I'm unable to reproduce the issue
you're seeing since under lxc the /sys/kernel/debug directory belongs to
the host and thus is owned by nobody:nogroup, (although I should think
that it would produce a permission denied error.)

>From the host:
# mount | grep tracing
tracefs on /sys/kernel/debug/tracing type tracefs (rw,relatime)

In any case, regarding the bug itself, I am able to detect the
permissions error:

# /usr/lib/nagios/plugins/check_disk -e
DISK CRITICAL - /sys/kernel/debug/tracing is not accessible: Permission denied

# ls -la /sys/kernel/debug/tracing
ls: cannot access '/sys/kernel/debug/tracing': Permission denied

# /usr/lib/nagios/plugins/check_disk -e -X tracefs
DISK OK| /=44420MB;;;0;3754403 /dev=0MB;;;0;0 /dev/full=0MB;;;0;16018 
/dev/null=0MB;;;0;16018 /dev/random=0MB;;;0;16018 /dev/tty=0MB;;;0;16018 
/dev/urandom=0MB;;;0;16018 /dev/zero=0MB;;;0;16018 /dev/fuse=0MB;;;0;16018 
/dev/net/tun=0MB;;;0;16018 /dev/lxd=0MB;;;0;0 /dev/.lxd-mounts=0MB;;;0;0 
/dev/shm=0MB;;;0;16041 /run=16MB;;;0;16041 /run/lock=0MB;;;0;5 
/sys/fs/cgroup=0MB;;;0;16041 /var/lib/lxd/shmounts=0MB;;;0;0 
/var/lib/lxd/devlxd=0MB;;;0;0 /run/user/1001=0MB;;;0;3208

The suggestion in comment #16 looks like the best approach for
addressing the issue so far.  Alternatively, I posted a patch to LP
#1827159 for altering check_disk itself, however as mentioned in comment
#9 on this bug, excluding all tmpfs would be too broad.

Ramon, if you can test out the approach outlined in comment #16 and let
me know if it seems suitable for your use case, perhaps we should
proceed with implementing an SRU for that.


** Attachment added: "Screenshot from 2019-07-17 14-19-10.png"
   
https://bugs.launchpad.net/ubuntu/+source/nagios-plugins/+bug/1516451/+attachment/5277690/+files/Screenshot%20from%202019-07-17%2014-19-10.png

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

Title:
  check_disk plugin broken after upgrade to 15.10

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

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

[Bug 1836968] [NEW] Bionic update: upstream stable patchset 2019-07-17

2019-07-17 Thread Kamal Mostafa
Public bug reported:


SRU Justification

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

   upstream stable patchset 2019-07-17
   from git://git.kernel.org/

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

** Affects: linux (Ubuntu Bionic)
 Importance: Undecided
 Status: New


** Tags: kernel-stable-tracking-bug

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

** Tags added: kernel-stable-tracking-bug

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

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

Title:
  Bionic update: upstream stable patchset 2019-07-17

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

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

[Bug 1836961] Re: ansible 2.0.0.2-2ubuntu1.2 uninstallable on Ubuntu 16.04

2019-07-17 Thread Robert Hill
We are seeing the same behavior on 16.04.

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

Title:
  ansible 2.0.0.2-2ubuntu1.2 uninstallable on Ubuntu 16.04

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

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

Re: [Bug 1835623] Re: Google Chrome Linux version 75 freezes and then crashes when trying to play any video

2019-07-17 Thread BavarianPH
Bug solved!

In my case, the Laine gnome-shell extension was causing all the problems.
when I turned the Laine extension off both google-chrome and chromium
versions 75 (newest updates) worked again. Both video and audio playback
ran normally again.

On Tue, Jul 16, 2019 at 2:51 PM BavarianPH  wrote:

> ** Attachment added: "Security_log"
>
> https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1835623/+attachment/5277514/+files/log_messages_Security.log
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1835623
>
> Title:
>   Google Chrome Linux version 75 freezes and then crashes when trying to
>   play any video
>
> Status in chromium-browser package in Ubuntu:
>   New
>
> Bug description:
>   (upstream bug report:
>   https://bugs.chromium.org/p/chromium/issues/detail?id=983203)
>
>   Ubuntu 18.04
>   I expect Chrome to play videos.
>   When I try to play any video on Google Chrome for Linux, any version of
> 75 or higher, Google Chrome freezes.
>   Chrome 75 will allow sound but no video.
>   All mouse clicks become unresponsive.
>   Attempting to close Chrome after many mouse clicks causes Chrome to
> crash.
>   Even worse it often also crashes Ubuntu 18.04.
>   Google Chrome 74 or lower work without any problems playing videos.
>   It is a Google Chrome Linux version 75 or higher problem.
>   I cannot believe that neither Google or Ubuntu or any other Linux OS
> seem to completely ignore this extremely serious problem.
>   I am forced to install Google Chrome 71 to fix video playback problem.
>   I posted on Ubuntu ask, and show over 90 views but no comments.
>   One answer confirms that he has the exact same problem.
>   ---
>   ProblemType: Bug
>   ApportVersion: 2.20.9-0ubuntu7.6
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Desktop-Session:
>'ubuntu'
>'/etc/xdg/xdg-ubuntu:/etc/xdg'
>'/usr/share/ubuntu:/usr/local/share:/usr/share:/var/lib/snapd/desktop'
>   DetectedPlugins:
>
>   DistroRelease: Ubuntu 18.04
>   Env:
>'None'
>'None'
>   InstallationDate: Installed on 2019-05-02 (66 days ago)
>   InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
> (20181019)
>   Load-Avg-1min: 1.47
>   Load-Processes-Running-Percent:   0.1%
>   MachineType: MSI MS-7641
>   NonfreeKernelModules: nvidia_modeset nvidia
>   Package: chromium-browser 75.0.3770.90-0ubuntu0.18.04.1
>   PackageArchitecture: amd64
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_US.UTF-8
>SHELL=/bin/bash
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-55-generic
> root=UUID=7181ee96-0bd0-4b3c-9100-fa205ef6bd1d ro quiet splash vt.handoff=1
>   ProcVersionSignature: Ubuntu 4.15.0-55.60-generic 4.15.18
>   Tags:  bionic
>   Uname: Linux 4.15.0-55-generic x86_64
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm adm cdrom cdrom dip dip lpadmin lpadmin plugdev plugdev
> sambashare sambashare sudo sudo
>   _MarkForUpload: True
>   dmi.bios.date: 04/20/2015
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: V25.1
>   dmi.board.asset.tag: To Be Filled By O.E.M.
>   dmi.board.name: 760GMA-P34(FX) (MS-7641)
>   dmi.board.vendor: MSI
>   dmi.board.version: 5.0
>   dmi.chassis.asset.tag: To Be Filled By O.E.M.
>   dmi.chassis.type: 3
>   dmi.chassis.vendor: MSI
>   dmi.chassis.version: 5.0
>   dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvrV25.1:bd04/20/2015:svnMSI:pnMS-7641:pvr5.0:rvnMSI:rn760GMA-P34(FX)(MS-7641):rvr5.0:cvnMSI:ct3:cvr5.0:
>   dmi.product.family: To Be Filled By O.E.M.
>   dmi.product.name: MS-7641
>   dmi.product.version: 5.0
>   dmi.sys.vendor: MSI
>   etcconfigcpepperflashpluginnonfree:
>flashso="/usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so"
>flashversion=`strings $flashso 2> /dev/null | grep LNX | cut -d ' ' -f
> 2 | sed -e "s/,/./g"`
>CHROMIUM_FLAGS="$CHROMIUM_FLAGS --ppapi-flash-path=$flashso
> --ppapi-flash-version=$flashversion"
>   modified.conffile..etc.default.chromium-browser: [deleted]
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1835623/+subscriptions
>

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

Title:
  Google Chrome Linux version 75 freezes and then crashes when trying to
  play any video

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

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

[Bug 1835623] Re: Google Chrome Linux version 75 freezes and then crashes when trying to play any video

2019-07-17 Thread BavarianPH
Bug solved!

In my case, the Laine gnome-shell extension was causing all the problems. when 
I turned the Laine extension off both google-chrome and chromium versions 75 
(newest updates) worked again. 
Both video and audio playback ran normally again.

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

Title:
  Google Chrome Linux version 75 freezes and then crashes when trying to
  play any video

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

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

[Bug 1710278] Re: [2.3a1] named stuck on reload, DNS broken

2019-07-17 Thread Dan Streetman
> Test build in ppa:

eh, there is still a view->attributes field that needs lock protection,
this isn't ready yet.

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

Title:
  [2.3a1] named stuck on reload, DNS broken

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

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

[Bug 1836965] [NEW] O gimp de crash ao terminar o resize de fotos em lote

2019-07-17 Thread José Osvaldo Henrique
Public bug reported:

```
GNU Image Manipulation Program version 2.10.8
git-describe: GIMP_2_10_6-294-ga967e8d2c2
C compiler:
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/8/lto-wrapper
OFFLOAD_TARGET_NAMES=nvptx-none
OFFLOAD_TARGET_DEFAULT=1
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 
8.2.0-13ubuntu1' --with-bugurl=file:///usr/share/doc/gcc-8/README.Bugs 
--enable-languages=c,ada,c++,go,brig,d,fortran,objc,obj-c++ --prefix=/usr 
--with-gcc-major-version-only --program-suffix=-8 
--program-prefix=x86_64-linux-gnu- --enable-shared --enable-linker-build-id 
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix 
--libdir=/usr/lib --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug 
--enable-libstdcxx-time=yes --with-default-libstdcxx-abi=new 
--enable-gnu-unique-object --disable-vtable-verify --enable-libmpx 
--enable-plugin --enable-default-pie --with-system-zlib 
--with-target-system-zlib --enable-objc-gc=auto --enable-multiarch 
--disable-werror --with-arch-32=i686 --with-abi=m64 
--with-multilib-list=m32,m64,mx32 --enable-multilib --with-tune=generic 
--enable-offload-targets=nvptx-none --without-cuda-driver 
--enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu 
--target=x86_64-linux-gnu
Thread model: posix
gcc version 8.2.0 (Ubuntu 8.2.0-13ubuntu1) 

using GEGL version 0.4.14 (compiled against version 0.4.12)
using GLib version 2.60.4 (compiled against version 2.58.1)
using GdkPixbuf version 2.38.1 (compiled against version 2.38.0)
using GTK+ version 2.24.32 (compiled against version 2.24.32)
using Pango version 1.42.3 (compiled against version 1.42.3)
using Fontconfig version 2.13.1 (compiled against version 2.13.0)
using Cairo version 1.16.0 (compiled against version 1.16.0)

```
> fatal error: Falha de segmentação

Stack trace:
```

# Stack traces obtained from PID 2245 - Thread 2245 #

[New LWP 2254]
[New LWP 2303]
[New LWP 2304]
[New LWP 2314]
[New LWP 2315]
[New LWP 2706]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
__libc_read (nbytes=256, buf=0x7ffc22a0f790, fd=28) at 
../sysdeps/unix/sysv/linux/read.c:26
  Id   Target Id  Frame 
* 1Thread 0x7fdd0b4a0e00 (LWP 2245) "gimp-2.10"   __libc_read (nbytes=256, 
buf=0x7ffc22a0f790, fd=28) at ../sysdeps/unix/sysv/linux/read.c:26
  2Thread 0x7fdd078d4700 (LWP 2254) "worker"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  3Thread 0x7fdd058b4700 (LWP 2303) "gmain"   0x7fdd0a8de729 in 
__GI___poll (fds=0x7fdcf40018d0, nfds=2, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  4Thread 0x7fdd050b3700 (LWP 2304) "gdbus"   0x7fdd0a8de729 in 
__GI___poll (fds=0x5624648a9290, nfds=2, timeout=-1) at 
../sysdeps/unix/sysv/linux/poll.c:29
  5Thread 0x7fdcf18e4700 (LWP 2314) "async"   syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  6Thread 0x7fdcf10e3700 (LWP 2315) "worker"  syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
  7Thread 0x7fdcf08e2700 (LWP 2706) "swap writer" syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38

Thread 7 (Thread 0x7fdcf08e2700 (LWP 2706)):
#0  0x7fdd0a8e42e9 in syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1  0x7fdd0abd693f in g_cond_wait () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x7fdd0b0a9799 in  () at /lib/x86_64-linux-gnu/libgegl-0.4.so.0
#3  0x7fdd0abb487d in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fdd0a9c6182 in start_thread (arg=) at 
pthread_create.c:486
ret = 
pd = 
now = 
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140586905380608, 
5657068594012658585, 140720889457358, 140720889457359, 140720889457504, 
140586905377024, -5676768682615465063, -5675691318224315495}, mask_was_saved = 
0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, 
canceltype = 0}}}
not_first_call = 
#5  0x7fdd0a8eab1f in clone () at 
../sysdeps/unix/sysv/linux/x86_64/clone.S:95

Thread 6 (Thread 0x7fdcf10e3700 (LWP 2315)):
#0  0x7fdd0a8e42e9 in syscall () at 
../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1  0x7fdd0abd693f in g_cond_wait () at 
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x5624637fd423 in  ()
#3  0x7fdd0abb487d in  () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x7fdd0a9c6182 in start_thread (arg=) at 
pthread_create.c:486
ret = 
pd = 
now = 
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {140586913773312, 
5657068594012658585, 140720889463006, 140720889463007, 140720889463152, 
140586913769728, -5676765384617452647, -5675691318224315495}, mask_was_saved = 
0}}, priv = {pad = {0x0, 0x0, 0x0, 0x0}, data = {prev = 0x0, cleanup = 0x0, 

[Bug 1710278] Re: [2.3a1] named stuck on reload, DNS broken

2019-07-17 Thread Dan Streetman
Test build in ppa:

https://launchpad.net/~ddstreet/+archive/ubuntu/lp1710278

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

Title:
  [2.3a1] named stuck on reload, DNS broken

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

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

[Bug 1836960] Re: Gnome on Ubuntu 18.04.2 LTS text copying triggers apparently useless file writes

2019-07-17 Thread Thinking Torus
** Description changed:

+ Description:
+ 
  I recently noticed a strange behavior on my (pretty vanilla) Ubuntu
  18.04.2 LTS. Every time I copy some text from GNOME Terminal, using
  keyboard or mouse, it triggers a little hard drive activity.
  
  Intrigued, I decided to see what was going on (persistent clipboard
  data?). After some investigation, I found out that the activity is due
  to a file being written to whenever I do a copy in GNOME Terminal (or in
  other apps):
  
- ~/.config/nautilus/desktop-metadata
+ ~/.config/nautilus/desktop-metadata
  
  The small file seems to record the nautilus view settings and the trash
  icon state, has no apparent relation to functions of the clipboard, and
  does not mutate following each write (the content stays unchanged).
  
- My questions are:
- 
- Does this happen on your system?
- Why?
- How can I stop this?
- 
- I just tested to see if the same happens on a different computer running
+ I also tested to see if the same happens on a different computer running
  18.04.2 desktop live usb, and the answer is yes. So this shouldn't be
  something particular to my system.
  
+ 
  Steps to reproduce:
  
- * Boot your computer using live CD or usb created with 
ubuntu-18.04.2-desktop-amd64.iso
+ * Boot your computer using live CD or usb created with: 
+ ubuntu-18.04.2-desktop-amd64.iso
  You can obtain it from:
- http://releases.ubuntu.com/18.04/ 
+ http://releases.ubuntu.com/18.04/
  last modified: 2019-02-10 00:27
  sha256: 22580b9f3b186cc66818e60f44c46f795d708a1ad86b9225c458413b638459c4)
- * Start Gnome Terminal, copy some text from there, and note the current time 
when you perform the copying
- * Check the timestamp of ~/.config/nautilus/desktop-metadata and observe it's 
been modified at the same time you did the copying
- * repeat as many times as you like
+ 
+ * Start Gnome Terminal, copy some text from there, and note the current
+ time when you perform the copying
+ 
+ * Check the timestamp of ~/.config/nautilus/desktop-metadata and observe
+ it's been modified at the same time you did the copying
+ 
+ * Repeat as many times as you like
+ 
+ 
+ Expected behavior:
+ 
+ Copying text in Gnome should not trigger writes to some arbitrary file
+ (and should not trigger any disk IO at all).

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

Title:
  Gnome on Ubuntu 18.04.2 LTS text copying triggers apparently useless
  file writes

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

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

[Bug 1827859] Re: Cura 3.3.1 not working correctly

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

** Changed in: cura (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/1827859

Title:
  Cura 3.3.1 not working correctly

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

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

[Bug 1835091] Re: subiquity crashes upon reusing failed to assemble raid member partition

2019-07-17 Thread Michael Hudson-Doyle
I fixed subiquity to wipe disks harder, which might well have fixed
this. Will check today.

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

Title:
  subiquity crashes upon reusing failed to assemble raid member
  partition

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

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

[Bug 1836964] [NEW] 18.04.2: cannot see Macbook Air 7, 1 NVMe partitions

2019-07-17 Thread Kevin Williams
Public bug reported:

The kernel that comes with Kubuntu 18.04.1 is able to see the partitions
on my Macbook Air 7,1 (mid-2015, 11.6")'s NVMe SSD.  However, the kernel
included in 18.04.2 cannot.

If I check dmesg for the string "nvme" I get
nvme nvme0: IO queues not created

lspci can see the drive just fine.

This seems to be an upstream issue because it also affects Debian Buster
and Arch Linux.

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

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

Title:
  18.04.2: cannot see Macbook Air 7,1 NVMe partitions

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

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

[Bug 1836960] Re: Gnome on Ubuntu 18.04.2 LTS text copying triggers apparently useless file writes

2019-07-17 Thread Thinking Torus
** Tags added: bionic

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

Title:
  Gnome on Ubuntu 18.04.2 LTS text copying triggers apparently useless
  file writes

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

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

[Bug 1836961] ProcCpuinfoMinimal.txt

2019-07-17 Thread Daniel Manrique
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1836961/+attachment/5277687/+files/ProcCpuinfoMinimal.txt

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

Title:
  ansible 2.0.0.2-2ubuntu1.2 uninstallable on Ubuntu 16.04

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

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

[Bug 1836961] [NEW] ansible 2.0.0.2-2ubuntu1.2 uninstallable on Ubuntu 16.04

2019-07-17 Thread Daniel Manrique
Public bug reported:

Ansible 2.0.0.2-2ubuntu1.2 was updated on July 12th and apparently just
recently hit xenial updates and security:

$ apt-cache policy ansible
ansible:
  Installed: 2.0.0.2-2ubuntu1.2
  Candidate: 2.0.0.2-2ubuntu1.2
  Version table:
 2.1.1.0-1~ubuntu16.04.1 100
100 http://archive.ubuntu.com/ubuntu xenial-backports/universe amd64 
Packages
 *** 2.0.0.2-2ubuntu1.2 500
500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
500 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
100 /var/lib/dpkg/status
 2.0.0.2-2 500
500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

However, 2.0.0.2-2ubuntu1.2 has an error which prevents it from being
installed properly:

Setting up ansible (2.0.0.2-2ubuntu1.2) ...
Sorry: IndentationError: unindent does not match any outer indentation level 
(constants.py, line 106)
dpkg: error processing package ansible (--configure):
 subprocess installed post-installation script returned error exit status 101
Setting up python-selinux (2.4-3build2) ...
Errors were encountered while processing:
 ansible
E: Sub-process /usr/bin/dpkg returned an error code (1)


A more complete traceback:

E: Sub-process /usr/bin/dpkg returned an error code (1)
Traceback (most recent call last):
  File "/usr/bin/ansible-playbook", line 40, in 
from ansible.utils.display import Display
  File "/usr/lib/python2.7/dist-packages/ansible/utils/display.py", line 35, in 

from ansible import constants as C
  File "/usr/lib/python2.7/dist-packages/ansible/constants.py", line 106
except OSError:
  ^
IndentationError: unindent does not match any outer indentation level
--- 
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2018-06-01 (411 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Package: ansible 2.5.1+dfsg-1
PackageArchitecture: all
ProcEnviron:
 LANG=en_CA.UTF-8
 TERM=xterm-256color
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
 PATH=(custom, user)
ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
Tags:  bionic
Uname: Linux 4.15.0-50-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip kvm lpadmin lxd plugdev sambashare sudo vboxusers
_MarkForUpload: True

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


** Tags: apport-collected bionic

** Tags added: apport-collected bionic

** Description changed:

  Ansible 2.0.0.2-2ubuntu1.2 was updated on July 12th and apparently just
  recently hit xenial updates and security:
  
  $ apt-cache policy ansible
  ansible:
Installed: 2.0.0.2-2ubuntu1.2
Candidate: 2.0.0.2-2ubuntu1.2
Version table:
   2.1.1.0-1~ubuntu16.04.1 100
  100 http://archive.ubuntu.com/ubuntu xenial-backports/universe amd64 
Packages
   *** 2.0.0.2-2ubuntu1.2 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/universe amd64 
Packages
  100 /var/lib/dpkg/status
   2.0.0.2-2 500
  500 http://archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
  
  However, 2.0.0.2-2ubuntu1.2 has an error which prevents it from being
  installed properly:
  
  Setting up ansible (2.0.0.2-2ubuntu1.2) ...
  Sorry: IndentationError: unindent does not match any outer indentation level 
(constants.py, line 106)
  dpkg: error processing package ansible (--configure):
   subprocess installed post-installation script returned error exit status 101
  Setting up python-selinux (2.4-3build2) ...
  Errors were encountered while processing:
   ansible
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  
  
  A more complete traceback:
  
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  Traceback (most recent call last):
File "/usr/bin/ansible-playbook", line 40, in 
  from ansible.utils.display import Display
File "/usr/lib/python2.7/dist-packages/ansible/utils/display.py", line 35, 
in 
  from ansible import constants as C
File "/usr/lib/python2.7/dist-packages/ansible/constants.py", line 106
  except OSError:
^
  IndentationError: unindent does not match any outer indentation level
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.7
+ Architecture: amd64
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2018-06-01 (411 days ago)
+ InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
+ Package: ansible 2.5.1+dfsg-1
+ PackageArchitecture: all
+ ProcEnviron:
+  LANG=en_CA.UTF-8
+  TERM=xterm-256color
+  SHELL=/bin/bash
+  XDG_RUNTIME_DIR=
+  PATH=(custom, user)
+ ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
+ Tags:  bionic
+ Uname: Linux 

[Bug 1836961] Dependencies.txt

2019-07-17 Thread Daniel Manrique
apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1836961/+attachment/5277686/+files/Dependencies.txt

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

Title:
  ansible 2.0.0.2-2ubuntu1.2 uninstallable on Ubuntu 16.04

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

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

[Bug 1836879] Re: linux-lts-xenial: 4.4.0-156.183~14.04.1 -proposed tracker

2019-07-17 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: New => Confirmed

** Tags added: block-proposed-trusty

** Tags added: block-proposed

** 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: 1836880
- phase: Holding before Promote to Proposed
- phase-changed: Wednesday, 17. July 2019 14:10 UTC
+ phase: Ready for Promote to Proposed
+ phase-changed: Wednesday, 17. July 2019 21:12 UTC
  reason:
-   promote-to-proposed: Pending -- builds not complete in ppa 
main:building,signed:queued
+   promote-to-proposed: Pending -- ready for review
  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/1836879

Title:
  linux-lts-xenial: 4.4.0-156.183~14.04.1 -proposed tracker

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

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

[Bug 1516451] Re: check_disk plugin broken after upgrade to 15.10

2019-07-17 Thread Bryce Harrington
** Tags added: server-next

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

Title:
  check_disk plugin broken after upgrade to 15.10

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

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

[Bug 1786046] Re: Bypass Login Screen by replugging in external monitors

2019-07-17 Thread Ihor Menshykov
Well, it was v1.1.0e which is the latest one per Apt. The stuff that's
in conflict seems to also be stock, not custom.

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

Title:
  Bypass Login Screen by replugging in external monitors

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

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

[Bug 1827159] Re: check_all_disks includes squashfs /snap/* which are 100%

2019-07-17 Thread Bryce Harrington
Ramon, I'm not certain yet if LP #1516451 and LP #1516451 are precisely
the same issue, although it's likely they can be solved in similar
fashion.  Your customer issue looks like a better match to 1516451 since
it involves the /sys/kernel/debug/tracing file which I see you've
already commented on with a better test case than I had found, so I'll
follow up with you there.

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

Title:
  check_all_disks includes squashfs /snap/* which are 100%

To manage notifications about this bug go to:
https://bugs.launchpad.net/nagios-charm/+bug/1827159/+subscriptions

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

  1   2   3   4   5   6   >