[Bug 1838919] Re: Slow and lost keyboard and mouse events

2019-08-05 Thread Brian Burch
dpkg list next...

** Attachment added: "dpkg list"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1838919/+attachment/5281101/+files/schizo-2019-08-06-allpackages-txt

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

Title:
  Slow and lost keyboard and mouse events

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

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

Re: [Bug 1838876] Re: OBS Studio (snap) can't launch with GNOME on Wayland (there are no problems with X.org session)

2019-08-05 Thread Artyom Pozharov
Why? I don't have any problems with X.Org session. And with Wayland I can't
launch a half of programs.

вт, 6 авг. 2019 г., 1:10 Sebastian Ramacher
<1838...@bugs.launchpad.net>:

> Problems with the snap version don't belong here.
>
> ** Changed in: obs-studio (Ubuntu)
>Status: New => Invalid
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1838876
>
> Title:
>   OBS Studio (snap) can't launch with GNOME on Wayland (there are no
>   problems with X.org session)
>
> Status in obs-studio package in Ubuntu:
>   Invalid
>
> Bug description:
>   artem@hp-250-g6-notebook-pc:~$ obs-studio
>   libva info: VA-API version 1.1.0
>   libva info: va_getDriverName() returns -1
>   libva error: va_getDriverName() failed with unknown libva
> error,driver_name=(null)
>   vaInitialize failed with error code -1 (unknown libva error),exit
>
> /snap/obs-studio/525/usr/sbin:/snap/obs-studio/525/usr/bin:/snap/obs-studio/525/sbin:/snap/obs-studio/525/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games
>   This application failed to start because it could not find or load the
> Qt platform plugin "wayland-egl"
>   in "".
>
>   Available platform plugins are: eglfs, linuxfb, minimal, minimalegl,
>   offscreen, vnc, xcb.
>
>   Reinstalling the application may fix this problem.
>   Aborted (core dumped)
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 19.10
>   Package: gnome-shell 3.32.2-2ubuntu1
>   ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0
>   Uname: Linux 5.2.0-8-generic x86_64
>   ApportVersion: 2.20.11-0ubuntu7
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sun Aug  4 15:00:05 2019
>   DisplayManager: gdm3
>   GsettingsChanges:
>b'org.gnome.shell' b'app-picker-view' b'uint32 1'
>b'org.gnome.desktop.app-folders' b'folder-children' b"['Utilities',
> 'Sundry', 'YaST']"
>b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us'), ('xkb',
> 'ua')]"
>b'org.gnome.desktop.interface' b'gtk-im-module'
> b"'gtk-im-context-simple'"
>b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
>   InstallationDate: Installed on 2019-08-04 (0 days ago)
>   InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190802)
>   RelatedPackageVersions: mutter-common 3.32.2+git20190711-2ubuntu1
>   SourcePackage: gnome-shell
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/obs-studio/+bug/1838876/+subscriptions
>

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

Title:
  OBS Studio (snap) can't launch with GNOME on Wayland (there are no
  problems with X.org session)

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

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

[Bug 1837567] Re: disco/linux-azure: 5.0.0-1013.13 -proposed tracker

2019-08-05 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/automated-testing
   Status: Incomplete => Fix Released

** 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
  
  backports: bug 1838087 (bionic/linux-azure)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1838395
  packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
- phase: Testing
- phase-changed: Monday, 29. July 2019 12:21 UTC
+ phase: Ready for Testing
+ phase-changed: Tuesday, 06. August 2019 05:10 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
-   automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
stakeholder-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-azure: bug 1838087
  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/1837567

Title:
  disco/linux-azure: 5.0.0-1013.13 -proposed tracker

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

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

[Bug 1838919] Re: Slow and lost keyboard and mouse events

2019-08-05 Thread Brian Burch
Hi Daniel, thanks for not giving up! First, here is snap list:-

Name  Version Rev   Tracking  Publisher   
Notes
core  16-2.39.3   7270  stablecanonical✓  
core
core18201907231074  stablecanonical✓  
base
gnome-3-26-1604   3.26.0.20190705 90stable/…  canonical✓  -
gnome-3-28-1804   3.28.0-10-gaa70833.aa70833  67stablecanonical✓  -
gnome-calculator  3.32.1  406   stable/…  canonical✓  -
gnome-characters  v3.32.1+git2.3367201296   stable/…  canonical✓  -
gnome-logs3.32.0-4-ge8f3f37ca861stable/…  canonical✓  -
gnome-system-monitor  3.32.1-3-g0ea89b4922100   stable/…  canonical✓  -
gtk-common-themes 0.1-22-gab0a26b 1313  stable/…  canonical✓  -
pdftk-smoser  2.02-4  18stablesmoser  -

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

Title:
  Slow and lost keyboard and mouse events

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

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

[Bug 1838919] Re: Slow and lost keyboard and mouse events

2019-08-05 Thread Brian Burch
top on 4 second intervals rotates the same 5 or 6 threads, so I set the
interval to 20 seconds and copied the output to a file, which I have
attached. I have also attached the dpkg list.

** Attachment added: "top interval 20 seconds"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1838919/+attachment/5281100/+files/schizo-2019-08-06-top-d-20

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

Title:
  Slow and lost keyboard and mouse events

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

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

[Bug 1838982] Re: unable to handle kernel NULL pointer dereference at 000000000000002c (IP: iget5_locked+0x9e/0x1f0)

2019-08-05 Thread Khaled El Mously
** Changed in: linux (Ubuntu Bionic)
   Status: Confirmed => Fix Committed

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

Title:
  unable to handle kernel NULL pointer dereference at 002c
  (IP: iget5_locked+0x9e/0x1f0)

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1838982/+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-08-05 Thread Eric Desrochers
** important note ***

For eventual newer version of bind upgrade into later Ubuntu.

https://ftp.isc.org/isc/bind9/9.14.0/RELEASE-NOTES-bind-9.14.0.html


Previously, it was possible to build BIND without thread support for old 
architectures and systems without threads support. BIND now requires threading 
support (either POSIX or Windows) from the operating system, and it cannot be 
built without threads.


Seems like we can use single-thread up to 9.14, after that it's no
longer offer as an configuration option, so until the upstream deadlocks
are fix, and considering that --disable-threads is our current
workaround/best options, we should not go beyond 9.14 until we have a
better solution using multi threading and/or if upstream fix the
deadlocks issues that MAAS suffers.

-- 
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 1710278] Re: [2.3a1] named stuck on reload, DNS broken

2019-08-05 Thread Eric Desrochers
I just confirmed the above ^ :

$ git checkout v9_13_0
$ ./configure --help | grep -i "enable-thread"
  --enable-threadsenable multithreading

$ git checkout v9_14_0
$ ./configure --help | grep -i "enable-thread"
==> NO MORE OPTION.

-- 
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 1833716] Re: System crashes on hot adding a core with drmgr command (4.15.0-48-generic)

2019-08-05 Thread bugproxy
** Tags removed: targetmilestone-inin---
** Tags added: targetmilestone-inin18042

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

Title:
  System crashes on hot adding a core with drmgr command
  (4.15.0-48-generic)

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

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

[Bug 1838434] Re: linux-image-5.0.0-1013-raspi2 refuses to boot with a kernel panic on Raspberry Pi 3 B+

2019-08-05 Thread Khaled El Mously
Sorry to hear that @Georgi

It's a strange problem to have. That kernel worked fine in all our pre-
release testing. Certainly _booting_ shouldn't be a problem.

Could there be some other root-cause for this problem? (e.g. filesystem
corruption or bad install or changes in /etc/fstab or new hardware
added/removed, etc.)

Are you able to boot the prior kernel again without issues?

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

Title:
  linux-image-5.0.0-1013-raspi2 refuses to boot with a kernel panic on
  Raspberry Pi 3 B+

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

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

[Bug 1827228] Re: nVidia-340 driver install failed, black screen upon boot and hanging

2019-08-05 Thread Ubuntu QA Website
This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1827228

** Tags added: iso-testing

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

Title:
  nVidia-340 driver install failed, black screen upon boot and hanging

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

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

[Bug 1826181] Re: Add DMIC support to oem-kernel

2019-08-05 Thread M Willis Monroe
I found this through random googling... but I'm running a Lenovo X1
Carbon gen 7 with Disco and installing this oem kernel package doesn't
seem to enable the DMIC.  Not sure if this is the correct place for that
observation.

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

Title:
  Add DMIC support to oem-kernel

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

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

[Bug 1831629] Re: snapd hammers SSD for long periods

2019-08-05 Thread Launchpad Bug Tracker
[Expired for snapd (Ubuntu) because there has been no activity for 60
days.]

** Changed in: snapd (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/1831629

Title:
  snapd hammers SSD for long periods

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

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

[Bug 1839051] Re: can't install "grub-install/dev/sda"

2019-08-05 Thread Chris Guiver
Thank you for your report.

This installation looks like it was caused by a corrupted file system. I
notice in the logs

Aug  6 03:54:25 ubuntu ubiquity: find: ‘/target/boot/efi/EFI/Dell’
Aug  6 03:54:25 ubuntu ubiquity: : Input/output error
Aug  6 03:54:25 ubuntu kernel: [  356.783337] FAT-fs (sda2): error, corrupted 
directory (invalid entries)
Aug  6 03:54:25 ubuntu kernel: [  356.783350] FAT-fs (sda2): Filesystem has 
been set read-only
Aug  6 03:54:25 ubuntu kernel: [  356.783377] FAT-fs (sda2): error, corrupted 
directory (invalid entries)

Aug 5 10:01:00 ubuntu grub-installer: grub-install: error: cannot open
`/boot/efi/EFI/ubuntu/shimx64.efi': Read-only file system.

I've marked this bug as incomplete, if you believe I'm in error please
leave a comment as to why, and you can return the status to new.

I suggest you `fsck` your /dev/sda2 (EFI partition) the try again. If it
fails again please change the status of this bug report back to new and
report what you found. If I'm correct the install will succeed after
`fsck`.

If you are unfamiliar with `fsck` (or file system checks) please refer
to https://help.ubuntu.com/community/FilesystemTroubleshooting or for
actual help please refer to https://discourse.ubuntu.com/t/finding-
help/712

I would also suggest using a more modern build of Ubuntu 16.04 LTS
(16.04.6 came out 28-Feb-2019 this year using the then latest kernel
4.15 instead of your used 2017 build which uses a now EOL 4.10 kernel).

Thank you for taking the time to report this bug and helping to make
Ubuntu better

** Changed in: grub-installer (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/1839051

Title:
  can't install "grub-install/dev/sda"

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

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

[Bug 1831945] Re: HDMI/DP audio: ELD not updated on hotplug event

2019-08-05 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/1831945

Title:
  HDMI/DP audio: ELD not updated on hotplug event

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

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

[Bug 1825054] Re: My JavaFx project stopped compiling

2019-08-05 Thread Launchpad Bug Tracker
[Expired for openjfx (Ubuntu) because there has been no activity for 60
days.]

** Changed in: openjfx (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/1825054

Title:
  My JavaFx project stopped compiling

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

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

[Bug 1831903] Re: Microphone audio pitch changes sometimes

2019-08-05 Thread Launchpad Bug Tracker
[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

** Changed in: pulseaudio (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/1831903

Title:
  Microphone audio pitch changes sometimes

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

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

[Bug 1838919] Re: Slow and lost keyboard and mouse events

2019-08-05 Thread Daniel van Vugt
Please also run:

  dpkg -l > allpackages.txt

and attach the file 'allpackages.txt'.

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

Title:
  Slow and lost keyboard and mouse events

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

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

[Bug 1839051] [NEW] can't install "grub-install/dev/sda"

2019-08-05 Thread ANIRUDDHA KUMAR
Public bug reported:

can't install "grub-install/dev/sda"

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubiquity 2.21.63.4
ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
Uname: Linux 4.10.0-28-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
CasperVersion: 1.376.2
Date: Tue Aug  6 09:25:01 2019
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/ubuntu.seed 
boot=casper only-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
ProcEnviron:
 LANGUAGE=en_IN
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IN
SourcePackage: grub-installer
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: grub-installer (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug ubiquity-2.21.63.4 ubuntu xenial

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

Title:
  can't install "grub-install/dev/sda"

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

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

[Bug 1838919] Re: Slow and lost keyboard and mouse events

2019-08-05 Thread Daniel van Vugt
Just a couple of ideas:

* Please run 'top' and tell us if any process is using high CPU while
the problem occurs.

* Please run 'snap list' and paste the output here.

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

Title:
  Slow and lost keyboard and mouse events

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

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

[Bug 1838919] Re: Slow and lost keyboard and mouse events

2019-08-05 Thread Brian Burch
What can I do to help you diagnose the problem further, Daniel?

I think something changed recently, and that must have been an update. I
do not believe I have installed any new packages that might have called
for GTK2, so my guess is that it has been there since the clean 18.10
install and not been in conflict with GTK3 until recently.

Searching on the conflict has not revealed anything helpful to me
because this kind of error has popped up lots of times as far back as
ubuntu 12.04. The packages recommended to be installed to "fix" these
old problems all seem to be present on my system already.

Is there an easy way to discover what is calling for GTK2, or is that
being done by canberra on behalf of some applications, but not others?

Is there any point in me booting recovery mode to see whether the errors
(keyboard mapping too, don't forget) are logged from the simple tty
console login?

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

Title:
  Slow and lost keyboard and mouse events

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

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

[Bug 1808657] Re: Ubiquity fails to boot when selecting the Try Kubuntu (live session).

2019-08-05 Thread Ubuntu QA Website
This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1808657

** Tags added: iso-testing

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

Title:
  Ubiquity fails to boot when selecting the Try  Kubuntu (live session).

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

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

[Bug 1835968] Re: Regression in backported patch for openssl 1.1

2019-08-05 Thread Unit 193
Howdy,

Well I tested this before, but the current version in -proposed seems to
work just as expected after a few days.

** 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/1835968

Title:
  Regression in backported patch for openssl 1.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ruby2.5/+bug/1835968/+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-08-05 Thread Eric Desrochers
Ok I made some progress

bind9-single-thread is now "threads support is disabled" according to
"named -V"

and

bind9 is still "threads support is enabled" still according to "named
-V"

There is a few things to fix still here and there due to the recent
change, but at least I think I found what dh_install needed to separate
the binaries into their respective binary package.

It is a bit more difficult since it involves multiple recompilation of
the same software but with different configuration options for each of
them. Still need some time to refine the configuration and test again.

-- 
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 1825222] Re: CONFIG_ARCH_ROCKCHIP is not set in ubuntu 18.04 aarch64, arm64

2019-08-05 Thread Po-Hsu Lin
Hi,
4.18 will reach EOL soon, the HWE stack will move to 5.0 kernel. I will add 
support to this instead.

https://ubuntu.com/about/release-cycle

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

Title:
  CONFIG_ARCH_ROCKCHIP is not set in ubuntu 18.04 aarch64,arm64

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

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

[Bug 1838982] Re: unable to handle kernel NULL pointer dereference at 000000000000002c (IP: iget5_locked+0x9e/0x1f0)

2019-08-05 Thread AaronMa
With this regression, Ubuntu can not be installed in OEM image which is using 
current 4.15-56 kernel.
So set it as critical.

** Changed in: linux (Ubuntu Bionic)
   Importance: High => Critical

** Changed in: linux (Ubuntu)
   Importance: Undecided => Critical

** Changed in: hwe-next
   Importance: Undecided => Critical

** Changed in: hwe-next
   Status: New => In Progress

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

Title:
  unable to handle kernel NULL pointer dereference at 002c
  (IP: iget5_locked+0x9e/0x1f0)

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

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

[Bug 1811819] Re: please include the kernel module VXLAN

2019-08-05 Thread Po-Hsu Lin
Hello,
can you give the kernel in comment #1 a try?
Thanks

** Also affects: linux-kvm (Ubuntu Xenial)
   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/1811819

Title:
  please include the kernel module VXLAN

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

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

[Bug 1239578] Re: No wireless support for Realtek RTL8192EE [10ec:818b]

2019-08-05 Thread Gray
~ > sudo lspci -s 03:00 -
03:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8192EE PCIe 
Wireless Network Adapter (rev ff)
00: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff
...
ff0: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff

---
Just that, ff everywhere.

Kernel: 5.0.0-23

Also, I tried the alternative driver on Larry's github, it works, that
is I have connectivity at least but it has some weird issues with
bettercap and the monitor mode.

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

Title:
  No wireless support for Realtek RTL8192EE [10ec:818b]

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

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

[Bug 1839024] Status changed to Confirmed

2019-08-05 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

Title:
  [i915] display flickering in perpetual loop while starting ubuntu
  18.04.2

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

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

[Bug 1838982] Re: unable to handle kernel NULL pointer dereference at 000000000000002c (IP: iget5_locked+0x9e/0x1f0)

2019-08-05 Thread Bin Li
Cool, we also met 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/1838982

Title:
  unable to handle kernel NULL pointer dereference at 002c
  (IP: iget5_locked+0x9e/0x1f0)

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

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

[Bug 1839024] Re: display flickering in perpetual loop while starting ubuntu 18.04.2

2019-08-05 Thread Daniel van Vugt
If possible, please also take a video of the problem with a phone and
then attach the video here.

** Package changed: xorg (Ubuntu) => linux (Ubuntu)

** Summary changed:

- display flickering in perpetual loop while starting ubuntu 18.04.2
+ [i915] display flickering in perpetual loop while starting ubuntu 18.04.2

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

Title:
  [i915] display flickering in perpetual loop while starting ubuntu
  18.04.2

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

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

[Bug 1838879] Re: Nvidia MX130 Video

2019-08-05 Thread Daniel van Vugt
It appears you are using the unsupported 'oibaf' PPA on this machine:

version.libdrm2: libdrm2 2.4.99+git1908030630.98996f~oibaf~b
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2~git1908031930.2dd598~oibaf~b
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2~git1908031930.2dd598~oibaf~b

Please remove it using the 'ppa-purge' command, then reboot. If the
problem persists then please open a new bug by running:

  ubuntu-bug xorg-server


** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Changed in: xorg-server (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/1838879

Title:
  Nvidia MX130 Video

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

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

[Bug 1838979] Re: [i915] framebuffer console flickers on 5.0.0 kernel

2019-08-05 Thread lotuspsychje
Thank you for providing more info, do you have the bug only on tty
or also on the desktop after 3 sec?

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

Title:
  [i915] framebuffer console flickers on 5.0.0 kernel

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

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

[Bug 1838979] Re: [i915] framebuffer console flickers on 5.0.0 kernel

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

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

Title:
  [i915] framebuffer console flickers on 5.0.0 kernel

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

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

[Bug 1839016] Re: Suspend is iterrupted by ALT key

2019-08-05 Thread Daniel van Vugt
I'm not familiar with the code that does suspension so suggest:

1. Verify the bug is still in Ubuntu 19.04/19.10.

2. If so then please report it to the upstream developers at:

   https://gitlab.gnome.org/GNOME/gnome-shell/issues

   and then tell us the new bug ID.

** Tags added: bionic

** 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/1839016

Title:
  Suspend is iterrupted by ALT key

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

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

[Bug 1839042] Re: Updater failed

2019-08-05 Thread Chris Guiver
Thank you for reporting this bug to Ubuntu.

It relates to Zorin which is not Ubuntu, and the Ubuntu components
reached EOL (end-of-life) on 27 January 2014 so the door closed to
release-upgrade long ago for that release.  This is not a bug, as it
works until some time after EOL, after which you need to manually change
the script for Ubuntu releases to point to old-releases yourself.

Ubuntu 18.10 (cosmic) reached end-of-life on July 18, 2019.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.
Ubuntu 17.04 (zesty) reached end-of-life on January 13, 2018.
Ubuntu 16.10 (yakkety) reached end-of-life on July 20, 2017.
Ubuntu 15.10 (wily) reached end-of-life on July 28, 2016.
Ubuntu 15.04 (vivid) reached end-of-life on February 4, 2016.
Ubuntu 14.10 (utopic) reached end-of-life on July 23, 2015.
Ubuntu 14.04 (trusty) reached end-of-life on April 25, 2019.
Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014.
Ubuntu 13.04 (raring) reached end-of-life on January 27, 2014.
Ubuntu 12.10 (quantal) reached end-of-life on May 16, 2014.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.
Ubuntu 11.10 (oneiric) reached end-of-life on May 9, 2013.
Ubuntu 11.04 (natty) reached end-of-life on October 28, 2012.
Ubuntu 10.10 (maverick) reached end-of-life on April 10, 2012.
Ubuntu 10.04 (lucid) reached end-of-life on May 9, 2013.
Ubuntu 9.10 (karmic) reached end-of-life on April 30, 2011.
Ubuntu 9.04 (jaunty) reached end-of-life on October 23, 2010.
Ubuntu 8.10 (intrepid) reached end-of-life on April 30, 2010.
Ubuntu 8.04 (hardy) reached end-of-life on May 12, 2011.
Ubuntu 7.10 (gutsy) reached end-of-life on April 18th, 2009.
Ubuntu 7.04 (feisty) reached end-of-life on October 19, 2008.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

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

Title:
  Updater failed

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

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

[Bug 1839008] Re: Extra mouse cursor fixed on screen

2019-08-05 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1827428 ***
https://bugs.launchpad.net/bugs/1827428

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1827428, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** Package changed: xorg (Ubuntu) => mutter (Ubuntu)

** Also affects: nvidia-graphics-drivers-418 (Ubuntu)
   Importance: Undecided
   Status: New

** Summary changed:

- Extra mouse cursor fixed on screen
+ [nvidia] Extra mouse cursor fixed on screen

** Tags added: nvidia

** This bug has been marked a duplicate of bug 1827428
   Mouse cursor left frozen copy of itself

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

Title:
  [nvidia] Extra mouse cursor fixed on screen

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

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

[Bug 1838919] Re: Slow and lost keyboard and mouse events

2019-08-05 Thread Daniel van Vugt
Thanks again. Life is rarely simple enough to reveal the cause of a
shell bug in the log. If it was though, then the canberra errors are the
only ones I think could be relevant.

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

** Changed in: mutter (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/1838919

Title:
  Slow and lost keyboard and mouse events

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

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

[Bug 1827428] Re: Mouse cursor left frozen copy of itself

2019-08-05 Thread Daniel van Vugt
** Also affects: nvidia-graphics-drivers-418 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: nvidia-graphics-drivers-418 (Ubuntu)
   Status: New => Confirmed

** Summary changed:

- Mouse cursor left frozen copy of itself
+ [nvidia] Mouse cursor left frozen copy of itself

** Changed in: nvidia-graphics-drivers-418 (Ubuntu)
   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/1827428

Title:
  [nvidia] Mouse cursor left frozen copy of itself

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

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

[Bug 1838848] Status changed to Confirmed

2019-08-05 Thread Ubuntu Kernel Bot
This change was made by a bot.

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

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

Title:
  Bluetooth controller not detected after resume from suspend [Qualcomm
  Atheros AR9285 Malbec Bluetooth Adapter]

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

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

[Bug 1838848] Re: Bluetooth device not detected after resume from suspend [Qualcomm Atheros AR9485]

2019-08-05 Thread Daniel van Vugt
Thanks, apparently idProduct=311d means:

  Atheros AR9285 Malbec Bluetooth Adapter

So if it is on the same board as the AR9485, it's at least a different
chip.

** Summary changed:

- Bluetooth device not detected after resume from suspend [Qualcomm Atheros 
AR9485]
+ Bluetooth device not detected after resume from suspend [Qualcomm Atheros 
AR9285 Malbec Bluetooth Adapter]

** Summary changed:

- Bluetooth device not detected after resume from suspend [Qualcomm Atheros 
AR9285 Malbec Bluetooth Adapter]
+ Bluetooth controller not detected after resume from suspend [Qualcomm Atheros 
AR9285 Malbec Bluetooth Adapter]

** Package changed: bluez (Ubuntu) => linux (Ubuntu)

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

Title:
  Bluetooth controller not detected after resume from suspend [Qualcomm
  Atheros AR9285 Malbec Bluetooth Adapter]

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

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

[Bug 1837572] Re: disco/linux-kvm: 5.0.0-1012.13 -proposed tracker

2019-08-05 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1838395
  packages:
main: linux-kvm
meta: linux-meta-kvm
- phase: Signoff
- phase-changed: Thursday, 01. August 2019 19:52 UTC
+ phase: Ready for Testing
+ phase-changed: Tuesday, 06. August 2019 01:50 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
regression-testing: Ongoing -- testing in progress
-   security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  variant: debs

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

Title:
  disco/linux-kvm: 5.0.0-1012.13 -proposed tracker

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

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

[Bug 1837573] Re: disco/linux-snapdragon: 5.0.0-1018.19 -proposed tracker

2019-08-05 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1838395
  packages:
main: linux-snapdragon
meta: linux-meta-snapdragon
  phase: Testing
  phase-changed: Tuesday, 30. July 2019 22:01 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Ongoing -- testing in progress
certification-testing: Ongoing -- testing in progress
-   security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  variant: debs

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

Title:
  disco/linux-snapdragon: 5.0.0-1018.19 -proposed tracker

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

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

[Bug 1837572] Re: disco/linux-kvm: 5.0.0-1012.13 -proposed tracker

2019-08-05 Thread Steve Beattie
** Changed in: kernel-sru-workflow/security-signoff
   Status: In Progress => Fix Released

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

Title:
  disco/linux-kvm: 5.0.0-1012.13 -proposed tracker

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

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

[Bug 1837573] Re: disco/linux-snapdragon: 5.0.0-1018.19 -proposed tracker

2019-08-05 Thread Steve Beattie
** Changed in: kernel-sru-workflow/security-signoff
   Status: In Progress => Fix Released

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

Title:
  disco/linux-snapdragon: 5.0.0-1018.19 -proposed tracker

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

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

[Bug 1838725] Re: Plymouth fails to display graphical splash screens on some machines, shows text mode dots animation instead.

2019-08-05 Thread Daniel van Vugt
Thanks for the video in comment #3, but it's completely different to
what I'm trying to describe here. Here I do see a plymouth animation,
but the word Ubuntu and the dots are shown in the middle of the text
console.

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

Title:
  Plymouth fails to display graphical splash screens on some machines,
  shows text mode dots animation instead.

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

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

[Bug 1837519] Re: plymouth-theme-spinner should show an Ubuntu logo when BGRT is missing

2019-08-05 Thread Daniel van Vugt
I'm still curious to hear an answer to comment #7.

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

Title:
  plymouth-theme-spinner should show an Ubuntu logo when BGRT is missing

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

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

[Bug 1838959] Re: [drm:radeon_atom_pick_dig_encoder [radeon]] *ERROR* chosen encoder in use 0

2019-08-05 Thread Daniel van Vugt
Your system is still using the unsupported 'oidbaf' PPA:

version.libdrm2: libdrm2 2.4.99+git1908030630.98996f~oibaf~b
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2~git1908041930.486b33~oibaf~b
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2~git1908041930.486b33~oibaf~b

Please try using 'ppa-purge' to remove it from your machine and then
reboot.

** Package changed: xorg (Ubuntu) => linux (Ubuntu)

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

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

Title:
  [drm:radeon_atom_pick_dig_encoder [radeon]] *ERROR* chosen encoder in
  use 0

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

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

[Bug 1838959] Re: [drm:radeon_atom_pick_dig_encoder [radeon]] *ERROR* chosen encoder in use 0

2019-08-05 Thread Daniel van Vugt
Your system is still using the unsupported 'oibaf' PPA:

version.libdrm2: libdrm2 2.4.99+git1908030630.98996f~oibaf~b
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2~git1908041930.486b33~oibaf~b
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2~git1908041930.486b33~oibaf~b

Please try using 'ppa-purge' to remove it from your machine and then
reboot.

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

Title:
  [drm:radeon_atom_pick_dig_encoder [radeon]] *ERROR* chosen encoder in
  use 0

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

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

[Bug 1838443] Re: No flicker free boot since Ignoring BGRT: invalid version 0 (expected 1)

2019-08-05 Thread Daniel van Vugt
It's not up to me... You'll need to seek guidance and a code review from
kernel developers.

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

Title:
  No flicker free boot since Ignoring BGRT: invalid version 0 (expected
  1)

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

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

[Bug 1838945] Re: [drm:radeon_atom_pick_dig_encoder [radeon]] *ERROR* chosen encoder in use 0

2019-08-05 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1838959 ***
https://bugs.launchpad.net/bugs/1838959

** This bug has been marked a duplicate of bug 1838959
   [drm:radeon_atom_pick_dig_encoder [radeon]] *ERROR* chosen encoder in use 0

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

Title:
  [drm:radeon_atom_pick_dig_encoder [radeon]] *ERROR* chosen encoder in
  use 0

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

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

[Bug 1838358] Re: Ibus causes gnome-shell to freeze when password fields are selected in Firefox

2019-08-05 Thread Matthew Ruffell
Hi Lukasz,

We are in luck, after some very helpful debugging done by the customer, I have
been able to reliably reproduce this issue myself.

Firstly, this issue only affects users of Ubuntu inside a VMware Horizon VDI, 
and only occurs after you install the VMware Horizon Agent for Linux. 

The issue can be replicated reliably in the customer environment, and several 
hundred users have been affected.

I downloaded and installed the Horizon Agent 
VMware-horizonagent-linux-x86_64-7.9.0-13916467.tar.gz in my test 18.04 VM.

Download location [1] (Requires registration)
Installation Instructions [2]

I now see gnome-shell and firefox act strange, with a large delay in input to 
the password field and having the box clearing randomly.

The customer also sees this behaviour. If the customer enables NVIDIA GRID
graphics acceleration, then gnome-shell freezes instead of having the large 
input delay. Disabling graphics acceleration shows the behaviour I can 
reproduce, of seeing large input delay and intermittent gnome-shell lockups.

I did some digging, and it seems the Horizon agent replaces some gnome-shell
libraries with its own.

# openssl sha256 ./usr/lib/gnome-shell/libgnome-shell.so
bd86f21646db0be70139fa75879c6e56dd28b849bfc4a8ed4fae390c8bac
# openssl sha256 
./home/ubuntu/VMware-horizonagent-linux-x86_64-7.9.0-13916467/sso/ubuntu/1804/libgnome-shell.so
bd86f21646db0be70139fa75879c6e56dd28b849bfc4a8ed4fae390c8bac

# openssl sha256 ./usr/lib/vmware/viewagent/sso/backup/libgnome-shell.orig.so
381698f0554e53512c3627afd170dcd1567fa833d9a0e19fb36c0054296ead00
# openssl sha256 
./home/ubuntu/VMware-horizonagent-linux-x86_64-7.9.0-13916467/sso/ubuntu/1804/libgnome-shell.orig.so
381698f0554e53512c3627afd170dcd1567fa833d9a0e19fb36c0054296ead00

VMware Horizon has a feature called "True SSO" [3] which seems to enable users
to authenticate once to the VMware Identity Manager, and then use a SSO token
afterwards to log into supported websites.

>From what I can see, VMware have built their own custom gnome-shell libraries
and modified their library to implement the True SSO feature, which probably
uses interactions between gnome-shell and ibus to detect password input fields
and automate password entry.

When I revert the custom gnome-shell library to the one Canonical provides in
the Ubuntu 18.04 main archive, the issue is fixed, and I can enter text in
password fields normally.

>From our side, Canonical cannot support these custom gnome-shell libraries,
since we do not have source code for them and we don't know whats in them or
how they are built.

What we can do is work around them, and the proposed change to ibus does
exactly that. With those environment variables in place, input is "discarded"
by ibus and passed directly into the application, and likely skips the 
"True SSO" functionality which is breaking Firefox.

A case has now been opened with VMware so they can fix their custom gnome-shell
libraries, but for now, the ibus workaround is a agreeable solution for this
customer, mostly since they do not use the "True SSO" functionality.

I can now replicate the problem, and customer is also on board to test the
-proposed package in their environment.

I can now verify myself that the test package in my ppa works around the problem
successfully.

Lukasz, I hope that answers some of your questions.

Matthew

[1] https://my.vmware.com/group/vmware/evalcenter?p=horizon-7#tab_download
[2] 
https://docs.vmware.com/en/VMware-Horizon-7/7.1/com.vmware.horizon-view.linuxdesktops.doc/GUID-F06FF1A7-BDEF-4269-B2AB-C62819D4FCCD.html
[3] 
https://blogs.vmware.com/euc/2016/03/true-sso-single-sign-on-view-identity-manager-authenticate.html

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

Title:
  Ibus causes gnome-shell to freeze when password fields are selected in
  Firefox

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

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

[Bug 1839042] [NEW] Updater failed

2019-08-05 Thread David Batchelor
Public bug reported:

W: A error occurred during the signature verification. The repository is
not updated and the previous index files will be used. GPG error:
http://dl.google.com stable Release: The following signatures couldn't
be verified because the public key is not available: NO_PUBKEY
6494C6D6997C215E

W: A error occurred during the signature verification. The repository is
not updated and the previous index files will be used. GPG error:
http://deb.opera.com stable Release: The following signatures couldn't
be verified because the public key is not available: NO_PUBKEY
D615560BA5C7FF72

W: Failed to fetch
http://dl.google.com/linux/chrome/deb/dists/stable/Release

W: Failed to fetch http://deb.opera.com/opera/dists/stable/Release

W: Failed to fetch
http://extras.ubuntu.com/ubuntu/dists/raring/main/source/Sources  404
Not Found [IP: 2001:67c:1560:8001::29 80]

W: Failed to fetch
http://archive.ubuntu.com/ubuntu/dists/raring/main/source/Sources  404
Not Found [IP: 2001:67c:1360:8001::17 80]

W: Failed to fetch
http://extras.ubuntu.com/ubuntu/dists/raring/main/binary-i386/Packages
404  Not Found [IP: 2001:67c:1560:8001::29 80]

W: Failed to fetch
http://archive.ubuntu.com/ubuntu/dists/raring/universe/source/Sources
404  Not Found [IP: 2001:67c:1360:8001::17 80]

W: Failed to fetch
http://archive.ubuntu.com/ubuntu/dists/raring/main/binary-i386/Packages
404  Not Found [IP: 2001:67c:1360:8001::17 80]

W: Failed to fetch
http://archive.ubuntu.com/ubuntu/dists/raring/universe/binary-i386/Packages
404  Not Found [IP: 2001:67c:1360:8001::17 80]

W: Failed to fetch
http://archive.canonical.com/ubuntu/dists/raring/partner/source/Sources
404  Not Found [IP: 2001:67c:1562::1c 80]

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/raring-
updates/main/source/Sources  404  Not Found [IP: 2001:67c:1360:8001::17
80]

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/raring-
updates/universe/source/Sources  404  Not Found [IP:
2001:67c:1360:8001::17 80]

W: Failed to fetch
http://archive.canonical.com/ubuntu/dists/raring/partner/binary-i386/Packages
404  Not Found [IP: 2001:67c:1562::1c 80]

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/raring-
updates/main/binary-i386/Packages  404  Not Found [IP:
2001:67c:1360:8001::17 80]

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/raring-
updates/universe/binary-i386/Packages  404  Not Found [IP:
2001:67c:1360:8001::17 80]

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/raring-
backports/main/source/Sources  404  Not Found [IP:
2001:67c:1360:8001::17 80]

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/raring-
backports/universe/source/Sources  404  Not Found [IP:
2001:67c:1360:8001::17 80]

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/raring-
backports/main/binary-i386/Packages  404  Not Found [IP:
2001:67c:1360:8001::17 80]

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/raring-
backports/universe/binary-i386/Packages  404  Not Found [IP:
2001:67c:1360:8001::17 80]

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/raring-
security/main/source/Sources  404  Not Found [IP: 2001:67c:1360:8001::17
80]

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/raring-
security/universe/source/Sources  404  Not Found [IP:
2001:67c:1360:8001::17 80]

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/raring-
security/main/binary-i386/Packages  404  Not Found [IP:
2001:67c:1360:8001::17 80]

W: Failed to fetch http://archive.ubuntu.com/ubuntu/dists/raring-
security/universe/binary-i386/Packages  404  Not Found [IP:
2001:67c:1360:8001::17 80]

W: Some index files failed to download. They have been ignored, or old
ones used instead.

ProblemType: Bug
DistroRelease: Zorin 7
Package: ubuntu-release-upgrader-core 1:0.192.13 [origin: Ubuntu]
ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8
Uname: Linux 3.8.0-31-generic i686
ApportVersion: 2.9.2-0ubuntu8.3
Architecture: i386
CrashDB: ubuntu
Date: Tue Aug  6 02:00:56 2019
InstallationDate: Installed on 2014-09-26 (1774 days ago)
InstallationMedia: Zorin 7 - Release i386
MarkForUpload: True
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to raring on 2019-08-06 (0 days ago)
VarLogDistupgradeAptlog:
 Log time: 2019-08-06 02:00:09.739361
 Log time: 2019-08-06 02:00:13.886279
 Log time: 2019-08-06 02:00:35.788120
 Log time: 2019-08-06 02:01:04.457022
VarLogDistupgradeTermlog:

** Affects: ubuntu-release-upgrader (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-bug dist-upgrade i386 raring third-party-packages

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

Title:
  Updater failed

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

-- 
ubuntu-bugs mailing list

[Bug 1798921] Re: sky2 ethernet card don't work after returning from suspension

2019-08-05 Thread ricardovitor
I'm new to the community, I wanted some guidance on how to report this
bug. I have a Samsung RV510 Notebook, which uses this "sky 2" Driver to
manage the Notebook's Lan network interface. Upon returning from sleep,
the Lan interface stops working and only works when you completely
restart the Notebook. I've read some comments here in the topic,
including that the bugs were fixed in some kernel versions, but for me
the version: 4.15.0-55.57 and 4.18.0-25.26 still have the same bug. I
did some tests on other distros not based on Ubuntu and using newer
Kernel, the problem also happens, very strange this problem. An interim
solution I found in this topic was the "quiet splash pci = nomsi, noaer"
which I believe has temporarily solved the problem. I appreciate the
community response.

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

Title:
  sky2 ethernet card don't work after returning from suspension

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

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

[Bug 1810215] Re: Smart data works on kernel 4.13 but not on 4.15

2019-08-05 Thread Nathan Stratton Treadway
@Mike/Robie:

Actually the "uas: Always apply US_FL_NO_ATA_1X quirk to Seagate
devices" patch to the kernel is (part of) the cause of the current
smartmontool failure rather than a fix for it.

The underlying problem is that most Seagate drive enclosures do not
properly handle SAT (= "ATA pass-through") when in UAS mode, and so the
kernel now (after that patch) disables SAT for all Seagate enclosures
when UAS is in use.

That change allows those enclosures to work okay in UAS mode for normal
data access (with the associated increase in performance) ... but since
Smartmontools and other utilities (e.g. "hdparm") require SAT to work,
the change breaks their functionality for those devices.

The current workaround is to use the kernel quirks to disable UAS for a
particular device, so that the kernel falls back to the old usb-storage
mode instead; this lets SAT work again (and thus Smartmontools, etc.
function properly), but only at the expense of losing UAS performance
for normal data access.

So in the long run it would be ideal for the kernel to have some way to
more dynamically deal with these sorts of buggy devices (i.e. switching
modes temporarily to allow SAT to work for special operations such as
Smartmontools but use UAT most of the time)... but I haven't run across
any discussion about such a patch anywhere, so it seems like people with
these devices will be stuck with having to choose between SAT or UAS for
the time being.

Anyway, there's now a Smartmontools Wiki page devoted to this specific
topic:  https://www.smartmontools.org/wiki/SAT-with-UAS-Linux .

** Summary changed:

- Smart data works on kernel 4.13 but not on 4.15
+ for Seagate USB drive enclosures, SAT (e.g. smartmontools)  works on kernel 
4.13 but not on 4.15

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

Title:
  for Seagate USB drive enclosures, SAT (e.g. smartmontools)  works on
  kernel 4.13 but not on 4.15

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

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

[Bug 1747630] Re: Kernel security test test_022_aslr_hardy_vdso failed on Precise i386

2019-08-05 Thread Steve Beattie
Okay, the reason this test (and bug 1717856) fail sporadically is that
ASLR in precise for i386 has very low number of random values for vdso
and shared library offsets, when ulimits are set such that unlimited
stack sizes are allowed:

  ubuntu@sec-precise-i386:~/tests/qrt-test-kernel-security$ uname -a
  Linux sec-precise-i386 3.2.0-142-generic #189-Ubuntu SMP Fri Jul 5 18:40:43 
UTC 2019 i686 i686 i386 GNU/Linux
  ubuntu@sec-precise-i386:~/tests/qrt-test-kernel-security$ ulimit -s unlimited
  ubuntu@sec-precise-i386:~/tests/qrt-test-kernel-security$ ulimit -s
  unlimited
  ubuntu@sec-precise-i386:~/tests/qrt-test-kernel-security$ for ((i=0; i<1; 
i++)) ; do ./kernel-security/aslr/aslr --report vdso ; done | sort | uniq -c
 1273 0x4000
 8662 0x40022000
   65 0x40026000

Yes, all of 3 values, and 86% of the invocations result in one value.
The shared library base values are slightly better, but not much:

  ubuntu@sec-precise-i386:~/tests/qrt-test-kernel-security$ for ((i=0; i<1; 
i++)) ; do ./kernel-security/aslr/aslr --report libs ; done | sort | uniq -c
  499 0x40003d80
  285 0x40016d80
  566 0x40025d80
 7608 0x40038d80
  295 0x4003cd80
  250 0x4003dd80
  167 0x4003ed80
  153 0x4003fd80
  177 0x40040d80

Compare this with the 3.13 results:

  ubuntu@sec-trusty-i386:~/tests/qrt-test-kernel-security$ uname -a
  Linux sec-trusty-i386 3.13.0-170-generic #220-Ubuntu SMP Thu May 9 12:41:17 
UTC 2019 i686 i686 i686 GNU/Linux
  ubuntu@sec-trusty-i386:~/tests/qrt-test-kernel-security$ ulimit -s unlimited
  ubuntu@sec-trusty-i386:~/tests/qrt-test-kernel-security$ ulimit -s
  unlimited
  ubuntu@sec-trusty-i386:~/tests/qrt-test-kernel-security$ for ((i=0; i<1; 
i++)) ; do ./kernel-security/aslr/aslr --report vdso ; done | sort | uniq -c | 
wc -l
  256

(output is piped into wc -l, because there are 256 distinct results.) So
8 bits of randomisation, which is not great, but better than >2.

The tests were added in response to http://hmarco.org/bugs/CVE-2016-3672
-Unlimiting-the-stack-not-longer-disables-ASLR.html and fixes were
applied for the 3.2.0-104.145 kernel.

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

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

Title:
  Kernel security test test_022_aslr_hardy_vdso failed on Precise i386

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1747630/+subscriptions

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

[Bug 1747630] Re: Kernel security test test_022_aslr_hardy_vdso failed on Precise i386

2019-08-05 Thread Steve Beattie
That said, at this point, I don't believe we are likely to fix this for
3.2 kernels, so adjusting the QRT test may be in order.

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

Title:
  Kernel security test test_022_aslr_hardy_vdso failed on Precise i386

To manage notifications about this bug go to:
https://bugs.launchpad.net/qa-regression-testing/+bug/1747630/+subscriptions

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

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

2019-08-05 Thread Agustin-ferrario
Hi! Sorry for the delay. I installed the packages in ubuntu 19.04
(Disco):

$ ls
linux-headers-5.3.0-050300rc1_5.3.0-050300rc1.201907212232_all.deb
linux-image-unsigned-5.3.0-050300rc1-generic_5.3.0-050300rc1.201907212232_amd64.deb
linux-headers-5.3.0-050300rc1-generic_5.3.0-050300rc1.201907212232_amd64.deb
linux-modules-5.3.0-050300rc1-generic_5.3.0-050300rc1.201907212232_amd64.deb
crash@crash-Inspiron-7375:~/Downloads$ sudo dpkg -i linux-*

Then rebooted but with the same error. I will try to manually compile
and install the kernel with the sources listed there without the patches
and will confirm.

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

Title:
  Ubuntu won't boot on Dell Inspiron 7375

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

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

[Bug 1767536] Re: Accessing the WIFI section of the "Settings" window causes massive freezes

2019-08-05 Thread Brian
To copy a workaround from the thread linked above: `nm-connection-
editor` still works great.

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

Title:
  Accessing the WIFI section of the "Settings" window causes massive
  freezes

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

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

Re: [Bug 1796292] Re: Tight timeout for bcache removal causes spurious failures

2019-08-05 Thread Ryan Harper
On Mon, Aug 5, 2019 at 1:19 PM Ryan Harper 
wrote:

>
>
> On Mon, Aug 5, 2019 at 8:01 AM Andrea Righi 
> wrote:
>
>> Ryan, I've uploaded a new test kernel with the fix mentioned in the
>> comment before:
>>
>> https://kernel.ubuntu.com/~arighi/LP-1796292/4.15.0-56.62~lp1796292+4/
>>
>> I've performed over 100 installations using curtin-nvme.sh
>> (install_count = 100), no hung task timeout. I'll run other stress tests
>> to make sure we're not breaking anything else with this fix, but results
>> look promising so far.
>>
>> It'd be great if you could also do a test on your side. Thanks!
>>
>
> Thats excellent news.  I'm starting my tests on this kernel now.
>

I've got 233 consecutive installs successful.


>
>
>>
>> --
>> You received this bug notification because you are subscribed to the bug
>> report.
>> https://bugs.launchpad.net/bugs/1796292
>>
>> Title:
>>   Tight timeout for bcache removal causes spurious failures
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/curtin/+bug/1796292/+subscriptions
>>
>

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

Title:
  Tight timeout for bcache removal causes spurious failures

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

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

[Bug 1839041] [NEW] I was trying to install Ubuntu Mate along side Windows 10

2019-08-05 Thread jwsheff
Public bug reported:

Installing Ubuntu 18.04.2 Mate on a Lenovo ideapad 330 after resizing
the Windows 10 partition within the install processed. Grub failed to
install.

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: Mon Aug  5 17:07:52 2019
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu-mate.seed 
boot=casper quiet splash ---
LiveMediaBuild: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
SourcePackage: grub-installer
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: grub-installer (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  I was trying to install Ubuntu Mate along side Windows 10

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

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

[Bug 1837571] Re: disco/linux-gcp: 5.0.0-1012.12 -proposed tracker

2019-08-05 Thread Steve Beattie
** Changed in: kernel-sru-workflow/security-signoff
   Status: In Progress => Fix Released

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

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

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

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

[Bug 1837571] Re: disco/linux-gcp: 5.0.0-1012.12 -proposed tracker

2019-08-05 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  backports: bug 1837569 (bionic/linux-gke-5.0), bug 1837570 (bionic
  /linux-gcp-edge)
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1838395
  packages:
main: linux-gcp
meta: linux-meta-gcp
signed: linux-signed-gcp
  phase: Testing
  phase-changed: Monday, 29. July 2019 12:22 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
-   security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  trackers:
bionic/linux-gcp-edge: bug 1837570
bionic/linux-gke-5.0: bug 1837569
  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/1837571

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

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

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

[Bug 1828558] Re: installing ubuntu on a former md raid volume makes system unusable

2019-08-05 Thread Michael Hudson-Doyle
** Changed in: partman-base (Ubuntu)
   Status: Fix Released => In Progress

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

Title:
  installing ubuntu on a former md raid volume makes system unusable

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

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

[Bug 1837570] Re: bionic/linux-gcp-edge: 5.0.0-1012.12~18.04.1 -proposed tracker

2019-08-05 Thread Steve Beattie
** Changed in: kernel-sru-workflow/security-signoff
   Status: In Progress => Fix Released

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

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

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

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

[Bug 1837570] Re: bionic/linux-gcp-edge: 5.0.0-1012.12~18.04.1 -proposed tracker

2019-08-05 Thread Ubuntu Kernel Bot
** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1837571
  packages:
main: linux-gcp-edge
meta: linux-meta-gcp-edge
signed: linux-signed-gcp-edge
  phase: Testing
  phase-changed: Monday, 05. August 2019 12:31 UTC
  proposed-announcement-sent: true
  proposed-testing-requested: true
  reason:
automated-testing: Stalled -- testing FAILED
regression-testing: Ongoing -- testing in progress
-   security-signoff: Pending -- waiting for signoff
verification-testing: Ongoing -- testing in progress
  variant: debs

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

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

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

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

[Bug 1828558] Re: installing ubuntu on a former md raid volume makes system unusable

2019-08-05 Thread Michael Hudson-Doyle
Turns out my fix is wrong: it is clearing the superblocks in NEW_LABEL,
but really the disk should not be touched until COMMIT.

** Tags removed: verification-needed verification-needed-bionic 
verification-needed-disco
** Tags added: verification-failed verification-failed-bionic 
verification-failed-disco

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

Title:
  installing ubuntu on a former md raid volume makes system unusable

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

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

[Bug 1839037] Missing required logs.

2019-08-05 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 1839037

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

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

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

Title:
  Stacked onexec transitions fail when under NO NEW PRIVS restrictions

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

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

[Bug 1838698] Re: Cannot boot ISO unless using nomodeset

2019-08-05 Thread fossfreedom
** Attachment added: "image seen at boot after installing"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel-hwe-18.04/+bug/1838698/+attachment/5281070/+files/20190805_233922.jpg

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

Title:
  Cannot boot ISO unless using nomodeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel-hwe-18.04/+bug/1838698/+subscriptions

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

[Bug 1838698] Re: Cannot boot ISO unless using nomodeset

2019-08-05 Thread fossfreedom
** Attachment added: "wtmp"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel-hwe-18.04/+bug/1838698/+attachment/5281069/+files/wtmp

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

Title:
  Cannot boot ISO unless using nomodeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel-hwe-18.04/+bug/1838698/+subscriptions

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

[Bug 1838698] Re: Cannot boot ISO unless using nomodeset

2019-08-05 Thread fossfreedom
** Attachment added: "Xorg.0.log.old"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel-hwe-18.04/+bug/1838698/+attachment/5281068/+files/Xorg.0.log.old

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

Title:
  Cannot boot ISO unless using nomodeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel-hwe-18.04/+bug/1838698/+subscriptions

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

[Bug 1838698] Re: Cannot boot ISO unless using nomodeset

2019-08-05 Thread fossfreedom
** Attachment added: "apport.log"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel-hwe-18.04/+bug/1838698/+attachment/5281064/+files/apport.log

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

Title:
  Cannot boot ISO unless using nomodeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel-hwe-18.04/+bug/1838698/+subscriptions

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

[Bug 1838698] Re: Cannot boot ISO unless using nomodeset

2019-08-05 Thread fossfreedom
** Attachment added: "auth.log"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel-hwe-18.04/+bug/1838698/+attachment/5281067/+files/auth.log

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

Title:
  Cannot boot ISO unless using nomodeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel-hwe-18.04/+bug/1838698/+subscriptions

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

[Bug 1838698] Re: Cannot boot ISO unless using nomodeset

2019-08-05 Thread fossfreedom
** Attachment added: "syslog"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel-hwe-18.04/+bug/1838698/+attachment/5281066/+files/syslog

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

Title:
  Cannot boot ISO unless using nomodeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel-hwe-18.04/+bug/1838698/+subscriptions

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

[Bug 1838698] Re: Cannot boot ISO unless using nomodeset

2019-08-05 Thread fossfreedom
** Attachment added: "kern.log"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel-hwe-18.04/+bug/1838698/+attachment/5281065/+files/kern.log

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

Title:
  Cannot boot ISO unless using nomodeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel-hwe-18.04/+bug/1838698/+subscriptions

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

[Bug 1838698] Re: Cannot boot ISO unless using nomodeset

2019-08-05 Thread fossfreedom
After installing the 32bit ISO I could not boot into the OS.

With nomodeset I just saw the enclosed picture.

Without nomodeset I saw briefly the same picture and then just a black
screen no blinking cursor.

The best logs I could find is to launch back into the livesession (with
nomodeset) and navigate to the /var/log on the harddrive

I'll attach all the logs at the latest time in that folder

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

Title:
  Cannot boot ISO unless using nomodeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel-hwe-18.04/+bug/1838698/+subscriptions

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

[Bug 1839038] [NEW] adplug+libbinio+memory mapped = crash on some files

2019-08-05 Thread Stian Skjelstad
Public bug reported:

The build already includes this patch:

https://github.com/adplug/libbinio/commit/76b5346a6196c76a1e9ea1ae0593d695da1dbd37

but it will also need this to remove all crashes (".D00" files, that are
memory mapped for instance, when loaded via libadplug)

https://github.com/adplug/libbinio/pull/8/commits/41fddc3a8123ec5455dcc8979f34a8b705eee5e6


(The crashes that happens inside Adplug, is due to memory allocated buffer that 
only receives the first byte set from a read-call, and further parsing assumes 
that the full data has been fetched)

** Affects: libbinio (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/1839038

Title:
  adplug+libbinio+memory mapped = crash on some files

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

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

[Bug 1838836] Re: network-manager needs to be restarted frequently

2019-08-05 Thread Jeremy
Chelmite, change it to 2 and see if it works better

sudo sed -i 's/3/2/' /etc/NetworkManager/conf.d/*

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

Title:
  network-manager needs to be restarted frequently

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

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

[Bug 1597466] Re: dpkg giving warning about '/etc/lsb-release' version number not starting with a digit when there is no apparent problem in the file

2019-08-05 Thread Carl Nobile
This has shown up again in 18.04.

dpkg: warning: version '/etc/lsb-release' has bad syntax: version number
does not start with digit

$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04.3 LTS"

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

Title:
  dpkg giving warning about '/etc/lsb-release' version number not
  starting with a digit when there is no apparent problem in the file

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

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

[Bug 1839037] [NEW] Stacked onexec transitions fail when under NO NEW PRIVS restrictions

2019-08-05 Thread John Johansen
Public bug reported:

running the apparmor nnp regression tests results in the following
failure

Error: transition failed. Test 'NNP (stack onexec - NNP)' was expected
to 'pass'. Reason for failure 'FAIL - execv: Operation not permitted'

with a log message of

[ 1169.863302] audit: type=1400 audit(1565046042.144:280686):
apparmor="DENIED" operation="exec" info="no new privs" error=-1
profile="/home/jj/apparmor.git/tests/regression/apparmor/transition"
name="/home/jj/apparmor.git/tests/regression/apparmor/open" pid=1888
comm="transition" requested_mask="x" denied_mask="x" fsuid=0 ouid=1000
target="/home/jj/apparmor.git/tests/regression/apparmor/open"

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

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

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

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

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

Title:
  Stacked onexec transitions fail when under NO NEW PRIVS restrictions

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

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

[Bug 1839036] Re: Bionic update: upstream stable patchset 2019-08-05

2019-08-05 Thread Kamal Mostafa
** 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-08-05
  
-Ported from the following upstream stable releases:
-v4.19.59,
- v4.14.134, v4.19.60,
-v4.19.61,
-v4.19.62,
- v4.14.135,
+    Ported from the following upstream stable releases:
+    v4.19.59,
+ v4.14.134, v4.19.60,
+    v4.19.61,
+    v4.19.62,
+ v4.14.135,
  
     from git://git.kernel.org/
+ 
+ e1000e: start network tx queue only when link is up
+ Input: synaptics - enable SMBUS on T480 thinkpad trackpad
+ nilfs2: do not use unexported cpu_to_le32()/le32_to_cpu() in uapi header
+ drivers: base: cacheinfo: Ensure cpu hotplug work is done before Intel RDT
+ crypto: talitos - rename alternative AEAD algos.
+ samples, bpf: fix to change the buffer size for read()
+ bpf: sockmap, fix use after free from sleep in psock backlog workqueue
+ staging:iio:ad7150: fix threshold mode config bit
+ mac80211: mesh: fix RCU warning
+ mac80211: free peer keys before vif down in mesh
+ iwlwifi: Fix double-free problems in iwl_req_fw_callback()
+ dt-bindings: can: mcp251x: add mcp25625 support
+ can: mcp251x: add support for mcp25625
+ can: m_can: implement errata "Needless activation of MRAF irq"
+ can: af_can: Fix error path of can_init()
+ ibmvnic: Refresh device multicast list after reset
+ ARM: dts: am335x phytec boards: Fix cd-gpios active level
+ Input: imx_keypad - make sure keyboard can always wake up system
+ KVM: arm/arm64: vgic: Fix kvm_device leak in vgic_its_destroy
+ mlxsw: spectrum: Disallow prio-tagged packets when PVID is removed
+ ARM: davinci: da850-evm: call regulator_has_full_constraints()
+ ARM: davinci: da8xx: specify dma_coherent_mask for lcdc
+ mac80211: only warn once on chanctx_conf being NULL
+ qmi_wwan: add support for QMAP padding in the RX path
+ qmi_wwan: avoid RCU stalls on device disconnect when in QMAP mode
+ qmi_wwan: extend permitted QMAP mux_id value range
+ md: fix for divide error in status_resync
+ bnx2x: Check if transceiver implements DDM before access
+ drm: return -EFAULT if copy_to_user() fails
+ ip6_tunnel: allow not to count pkts on tstats by passing dev as NULL
+ net: lio_core: fix potential sign-extension overflow on large shift
+ quota: fix a problem about transfer quota
+ net: dsa: mv88e6xxx: fix shift of FID bits in mv88e6185_g1_vtu_loadpurge()
+ net :sunrpc :clnt :Fix xps refcount imbalance on the error path
+ fscrypt: don't set policy for a dead directory
+ udf: Fix incorrect final NOT_ALLOCATED (hole) extent length
+ ALSA: hda/realtek - Headphone Mic can't record after S3
+ block, bfq: NULL out the bic when it's no longer valid
+ x86/ptrace: Fix possible spectre-v1 in ptrace_get_debugreg()
+ x86/tls: Fix possible spectre-v1 in do_get_thread_area()
+ Documentation: Add section about CPU vulnerabilities for Spectre
+ mwifiex: Abort at too short BSS descriptor element
+ mwifiex: Don't abort on small, spec-compliant vendor IEs
+ USB: serial: ftdi_sio: add ID for isodebug v1
+ USB: serial: option: add support for GosunCn ME3630 RNDIS mode
+ Revert "serial: 8250: Don't service RX FIFO if interrupts are disabled"
+ p54usb: Fix race between disconnect and firmware loading
+ usb: gadget: ether: Fix race between gether_disconnect and rx_submit
+ usb: renesas_usbhs: add a workaround for a race condition of workqueue
+ staging: comedi: dt282x: fix a null pointer deref on interrupt
+ staging: comedi: amplc_pci230: fix null pointer deref on interrupt
+ binder: fix memory leak in error path
+ carl9170: fix misuse of device driver API
+ VMCI: Fix integer overflow in VMCI handle arrays
+ MIPS: Remove superfluous check for __linux__
+ clk: ti: clkctrl: Fix returning uninitialized data
+ efi/bgrt: Drop BGRT status field reserved bits check
+ perf/core: Fix perf_sample_regs_user() mm check
+ ARM: omap2: remove incorrect __init annotation
+ be2net: fix link failure after ethtool offline test
+ ppp: mppe: Add softdep to arc4
+ sis900: fix TX completion
+ ARM: dts: imx6ul: fix PWM[1-4] interrupts
+ dm verity: use message limit for data block corruption message
+ x86/boot/64: Fix crash if kernel image crosses page table boundary
+ cpu/hotplug: Fix out-of-bounds read when setting fail state
+ linux/kernel.h: fix overflow for DIV_ROUND_UP_ULL
+ ARC: hide unused function unw_hdr_alloc
+ s390: fix stfle zero padding
+ 

[Bug 1838919] Re: Slow and lost keyboard and mouse events

2019-08-05 Thread Brian Burch
Also, I will attach journalctl -xb log taken as soon as I booted the
system and logged on this morning. It seems to me that as soon as
systemd started the gnome terminal server unit, related error messages
began to be generated.

Chrome/chromium had not been started at the time - it was autostarted by
your apport command quite a while later.

** Attachment added: "cold boot journalctl"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1838919/+attachment/5281063/+files/schizo-2001908-06-xb

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

Title:
  Slow and lost keyboard and mouse events

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

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

[Bug 1838919] Re: Slow and lost keyboard and mouse events

2019-08-05 Thread Brian Burch
Thanks for explaining Daniel #5. You will see I ran the command again.

However... It is interesting to see that even the apport-collect command
from a new terminal session triggered the canberra error.

brian@schizo:~$ apport-collect 1838919

(apport-gtk:21631): Gtk-WARNING **: 08:30:48.771: GTK+ module 
/usr/lib/x86_64-linux-gnu/gtk-2.0/modules/libgail.so cannot be loaded.
GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not 
supported.
Gtk-Message: 08:30:48.771: Not loading module "atk-bridge": The functionality 
is provided by GTK natively. Please try to not load it.

(apport-gtk:21631): Gtk-WARNING **: 08:30:49.106: GTK+ module 
/usr/lib/x86_64-linux-gnu/gtk-2.0/modules/libcanberra-gtk-module.so cannot be 
loaded.
GTK+ 2.x symbols detected. Using GTK+ 2.x and GTK+ 3 in the same process is not 
supported.
Gtk-Message: 08:30:49.106: Failed to load module "canberra-gtk-module"
The authorization page:
 
(https://launchpad.net/+authorize-token?oauth_token=t0cRSdJcr5xGQ4MLSbPG_permission=DESKTOP_INTEGRATION)
should be opening in your browser. Use your browser to authorize
this program to access Launchpad on your behalf.
Waiting to hear from Launchpad about your decision...
brian@schizo:~$

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

Title:
  Slow and lost keyboard and mouse events

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

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

[Bug 1838919] GsettingsChanges.txt

2019-08-05 Thread Brian Burch
apport information

** Attachment added: "GsettingsChanges.txt"
   
https://bugs.launchpad.net/bugs/1838919/+attachment/5281059/+files/GsettingsChanges.txt

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

Title:
  Slow and lost keyboard and mouse events

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

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

[Bug 1838919] ProcEnviron.txt

2019-08-05 Thread Brian Burch
apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1838919/+attachment/5281061/+files/ProcEnviron.txt

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

Title:
  Slow and lost keyboard and mouse events

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

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

[Bug 1838919] ShellJournal.txt

2019-08-05 Thread Brian Burch
apport information

** Attachment added: "ShellJournal.txt"
   
https://bugs.launchpad.net/bugs/1838919/+attachment/5281062/+files/ShellJournal.txt

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

Title:
  Slow and lost keyboard and mouse events

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

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

[Bug 1838919] Re: Slow and lost keyboard and mouse events

2019-08-05 Thread Brian Burch
apport information

** Tags added: apport-collected

** Description changed:

  This was a fresh amd64 installation with 18.10 desktop, upgraded to
  19.04 as soon as available. It has been getting worse over the last few
  weeks and is now so bad I can hardly type an email (or this bug report!)
  without having to fix many typos.
  
  journalctl shows many different gnome errors, so it is difficult to
  figure out which is the underlying cause and which are simply collateral
  damage.
  
  There are two sequences that appear first after a reboot, and the first
  of these has been reported many times on ubuntu releases going back for
  years:-
  
  Aug 05 08:16:08 schizo org.gnome.Shell.desktop[3529]: # GTK+ module 
/usr/lib/x86_64-linux-gnu/gtk-2.0/modules/libcanberra-gtk-module.so cannot be 
loaded.
  Aug 05 08:16:08 schizo org.gnome.Shell.desktop[3529]: # GTK+ 2.x symbols 
detected. Using GTK+ 2.x and GTK+ 3 in the same process is not supported.
  Aug 05 08:16:08 schizo org.gnome.Shell.desktop[3529]: # Failed to load module 
"canberra-gtk-module"
  
    and 
  
  Aug 05 09:11:04 schizo gnome-shell[3529]: [AppIndicatorSupport-DEBUG] 
Registering StatusNotifierItem 
:1.89/org/ayatana/NotificationItem/software_update_available
  Aug 05 09:11:04 schizo gnome-shell[3529]: [AppIndicatorSupport-FATAL] unable 
to update overlay icon
  Aug 05 09:11:04 schizo gnome-shell[3529]: [AppIndicatorSupport-FATAL] unable 
to update overlay icon
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 33 with keysym 33 (keycode c).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 31 with keysym 31 (keycode a).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 32 with keysym 32 (keycode b).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 34 with keysym 34 (keycode d).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 35 with keysym 35 (keycode e).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 39 with keysym 39 (keycode 12).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 36 with keysym 36 (keycode f).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 37 with keysym 37 (keycode 10).
  Aug 05 09:11:05 schizo org.gnome.Shell.desktop[3529]: Window manager warning: 
Overwriting existing binding of keysym 38 with keysym 38 (keycode 11).
  Aug 05 09:12:19 schizo org.gnome.Shell.desktop[3529]: 
[4042:4042:0805/091219.948098:ERROR:buffer_manager.cc(488)] 
[.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error 
from previous GL command
  Aug 05 09:12:21 schizo org.gnome.Shell.desktop[3529]: 
[4042:4042:0805/091221.376983:ERROR:buffer_manager.cc(488)] 
[.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error 
from previous GL command
  Aug 05 09:12:22 schizo org.gnome.Shell.desktop[3529]: 
[4042:4042:0805/091222.542169:ERROR:buffer_manager.cc(488)] 
[.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <-
  
  Is this a recent regression? I know for sure the system wasn't this
  unresponsive 3 weeks ago, but I cannot be sure when it started to go
  wrong. My mouse/keyboard combo has a USB-wireless dongle and I've
  fiddled around with distance and battery state until I was sure the
  problem was somewhere else and started to check the system log.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-software 3.30.6-2ubuntu4.19.04.1
  ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15
  Uname: Linux 5.0.0-23-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug  5 11:53:37 2019
  InstalledPlugins:
   gnome-software-plugin-flatpak 3.30.6-2ubuntu4.19.04.1
   gnome-software-plugin-snap3.30.6-2ubuntu4.19.04.1
  SourcePackage: gnome-software
  UpgradeStatus: Upgraded to disco on 2019-04-28 (98 days ago)
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.10-0ubuntu27.1
+ Architecture: amd64
+ CurrentDesktop: ubuntu:GNOME
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 19.04
+ Package: mutter
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.0.0-23.24-generic 5.0.15
+ RelatedPackageVersions: mutter-common 3.32.2+git20190711-2ubuntu1~19.04.1
+ Tags:  disco
+ Uname: Linux 5.0.0-23-generic x86_64
+ UpgradeStatus: Upgraded to disco on 2019-04-28 (99 days ago)
+ UserGroups: adm audio cdrom dip disk floppy lp lpadmin plugdev sambashare 
scans sudo video wireshark
+ _MarkForUpload: True

** Attachment added: "Dependencies.txt"
   

[Bug 1838919] ProcCpuinfoMinimal.txt

2019-08-05 Thread Brian Burch
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1838919/+attachment/5281060/+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/1838919

Title:
  Slow and lost keyboard and mouse events

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

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

[Bug 1830748] Re: Pressing scrollbar makes it sticky

2019-08-05 Thread klfyt
** Also affects: webkit-open-source
   Importance: Undecided
   Status: New

** No longer affects: webkit-open-source

** Also affects: chromium-browser (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: webkit (Ubuntu)

** No longer affects: webkit (Fedora)

** Also affects: fedora via
   https://bugzilla.redhat.com/show_bug.cgi?id=1714149
   Importance: Unknown
   Status: Unknown

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

Title:
  Pressing scrollbar makes it sticky

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

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

[Bug 1795808] Re: Xorg freeze when using nvidia driver 390

2019-08-05 Thread mohammad
thank you. uncommenting "WaylandEnable=false " worked for me as well.
now I can use android studio emulator with hardware accelerator.

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

Title:
  Xorg freeze when using nvidia driver 390

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

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

[Bug 1831181] Re: [aodh.notifier] Not setting user_domain_id raises keystone error: The resource could not be found.

2019-08-05 Thread Jorge Niedbalski
With the patch applied, the problem isn't longer reproduced:
https://pastebin.canonical.com/p/sPT82rwBCh/ , marking verification as
completed.

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

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

Title:
  [aodh.notifier] Not setting user_domain_id raises keystone error: The
  resource could not be found.

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

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

[Bug 1839036] [NEW] Bionic update: upstream stable patchset 2019-08-05

2019-08-05 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-08-05

   Ported from the following upstream stable releases:
   v4.19.59,
v4.14.134, v4.19.60,
   v4.19.61,
   v4.19.62,
v4.14.135,

   from git://git.kernel.org/

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

** Affects: linux (Ubuntu Bionic)
 Importance: Undecided
 Assignee: Kamal Mostafa (kamalmostafa)
 Status: In Progress


** 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

** 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-08-05
  
-upstream stable patchset 2019-08-05
-from git://git.kernel.org/
+Ported from the following upstream stable releases:
+v4.19.59,
+ v4.14.134, v4.19.60,
+v4.19.61,
+v4.19.62,
+ v4.14.135,
+ 
+    from git://git.kernel.org/

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

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)

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

Title:
  Bionic update: upstream stable patchset 2019-08-05

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

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

[Bug 1831181] Re: [aodh.notifier] Not setting user_domain_id raises keystone error: The resource could not be found.

2019-08-05 Thread Jorge Niedbalski
Please @SRU, check the bionic debdiff that's also attached into this
case.

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/1831181

Title:
  [aodh.notifier] Not setting user_domain_id raises keystone error: The
  resource could not be found.

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

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

[Bug 1828495] Re: [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM.

2019-08-05 Thread Rafael David Tinoco
I'll wait for the next SRU for bionic to be in -proposed to provide
Bionic full verification just like I did to Disco. It shall not take too
long and the version currently in -proposed will be superseded by the
one we have in the merge request right now.

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

Title:
  [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM.

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

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

[Bug 1828495] Re: [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM.

2019-08-05 Thread Rafael David Tinoco
# Disco verification:

ubuntu@disco:~$ sudo /usr/bin/qemu-system-x86_64 -name guest="guest"
-machine accel=kvm -cpu host,+arch-capabilities,+ssbd,+md-clear,+rdctl-
no,+ibrs-all,+skip-l1dfl-vmentry,+mds-no -m 2048 -realtime mlock=off
-smp 1,sockets=1,cores=1,threads=1 -uuid 7e55c71a-558f-
412c-8445-db0e95fc549f -display none -no-user-config -nodefaults -rtc
base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=delay -no-
shutdown -global PIIX4_PM.disable_s3=1 -global PIIX4_PM.disable_s4=1
-boot strict=on -kernel /var/lib/libvirt/images/guest/vmlinuz -initrd
/var/lib/libvirt/images/guest/initrd.img -append "root=/dev/vda noresume
console=tty0 console=ttyS0,38400n8 apparmor=0 net.ifnames=0
crashkernel=256M" -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2
-drive
file=/var/lib/libvirt/images/guest/disk01.ext4.qcow2,format=qcow2,if=none,id
=drive-virtio-disk0 -device virtio-blk-
pci,scsi=off,bus=pci.0,addr=0x3,drive=drive-virtio-disk0,id=virtio-
disk0,bootindex=1 -device virtio-balloon-
pci,id=balloon0,bus=pci.0,addr=0x4 -msg timestamp=on -serial stdio

-> changing "host" to CascadeLake-Server also works the same way.

Provided me:

inaddy@guest:~$ cat /proc/cpuinfo
processor   : 0
vendor_id   : GenuineIntel
cpu family  : 6
model   : 85
model name  : Intel(R) Xeon(R) Gold 6252 CPU @ 2.10GHz
stepping: 6
microcode   : 0x1
cpu MHz : 2095.076
cache size  : 16384 KB
physical id : 0
siblings: 1
core id : 0
cpu cores   : 1
apicid  : 0
initial apicid  : 0
fpu : yes
fpu_exception   : yes
cpuid level : 13
wp  : yes
flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush mmx fxsr sse sse2 ss syscall nx pdpe1gb rdtscp lm 
constant_tsc arch_perfmon rep_good nopl xtopology cpuid tsc_known_freq pni 
pclmulqdq vmx ssse3 fma cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt 
tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm abm 
3dnowprefetch cpuid_fault invpcid_single ssbd ibrs ibpb ibrs_enhanced 
tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep 
bmi2 erms invpcid rtm mpx avx512f avx512dq rdseed adx smap clflushopt clwb 
avx512cd avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves arat umip pku ospke 
avx512_vnni md_clear arch_capabilities
bugs: spectre_v1 spectre_v2 spec_store_bypass
bogomips: 4190.15
clflush size: 64
cache_alignment : 64
address sizes   : 40 bits physical, 48 bits virtual
power management:

AND reading the MSR directly:

inaddy@guest:~$ sudo rdmsr 0x10a
2b

We have bits: 0 1 3 and 5 like it should be.

-

Running same QEMU cmd line, enabling +arch-capabilities in CascadeLake-
Server but without specifying any other CPU flags:

flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov 
pat pse36 clflush mmx fxsr sse sse2 syscall nx pdpe1gb rdtscp lm constant_tsc 
rep_good nopl xtopology cpuid tsc_known_freq pni pclmulqdq ssse3 fma cx16 pcid 
sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand 
hypervisor lahf_lm abm 3dnowprefetch cpuid_fault invpcid_single pti ssbd ibrs 
ibpb fsgsbase bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx avx512f avx512dq 
rdseed adx smap clflushopt clwb avx512cd avx512bw avx512vl xsaveopt xsavec 
xgetbv1 arat pku ospke avx512_vnni arch_capabilities
bugs: cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds

inaddy@guest:~$ sudo rdmsr 0x10a
0

We are not enabling any mitigation flag in arch-capabilities MSR by
default, like we planned so. All CPU capabilities are going to be
enabled by hand and/or through libvirt XML definitions as soon as
libvirt gets the capabilities (this same bug).

-

Marking Disco as verified.

Thank you!


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

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

Title:
  [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM.

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

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

[Bug 1837600] Re: xenial/linux-fips: 4.4.0-1016.21 -proposed tracker

2019-08-05 Thread Ubuntu Kernel Bot
** Changed in: kernel-sru-workflow/automated-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/promote-signing-to-proposed
   Status: Fix Committed => Fix Released

** Changed in: kernel-sru-workflow/regression-testing
   Status: New => Confirmed

** Changed in: kernel-sru-workflow/verification-testing
   Status: New => Confirmed

** Description changed:

  This bug will contain status and test results related to a kernel source
  (or snap) as stated in the title.
  
  For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1837609
  packages:
main: linux-fips
meta: linux-meta-fips
signed: linux-signed-fips
- phase: Promote to Proposed
- phase-changed: Monday, 05. August 2019 20:31 UTC
+ phase: Ready for Testing
+ phase-changed: Monday, 05. August 2019 22:16 UTC
+ proposed-announcement-sent: true
+ proposed-testing-requested: true
  reason:
-   promote-signing-to-proposed: Ongoing -- packages waiting in -proposed for 
mirror
- sync
+   automated-testing: Ongoing -- testing in progress
+   regression-testing: Ongoing -- testing in progress
+   verification-testing: Ongoing -- testing in progress
  variant: debs

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

Title:
  xenial/linux-fips: 4.4.0-1016.21 -proposed tracker

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

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

[Bug 1838876] Re: OBS Studio (snap) can't launch with GNOME on Wayland (there are no problems with X.org session)

2019-08-05 Thread Sebastian Ramacher
Problems with the snap version don't belong here.

** Changed in: obs-studio (Ubuntu)
   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/1838876

Title:
  OBS Studio (snap) can't launch with GNOME on Wayland (there are no
  problems with X.org session)

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

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

[Bug 1838979] Re: [i915] framebuffer console flickers on 5.0.0 kernel

2019-08-05 Thread Mathias Leyendecker
apport-collect did not create anything meaningful (exited with "Package 
linux-hwe not installed and no hook available, ignoring"), but I ran a few 
commands (including dmesg) to try to include a more complete report.
Please let me know if you need anything else.

My computer is the Clevo N750WU (laptop).

** Attachment added: "i915_bug.tar.gz"
   
https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1838979/+attachment/5281057/+files/i915_bug.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/1838979

Title:
  [i915] framebuffer console flickers on 5.0.0 kernel

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

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

[Bug 1815172] Re: [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa

2019-08-05 Thread Timo Aaltonen
Reopening mesa for bionic, because the revert needs to be dropped once
the kernel is fixed, otherwise Ice Lake is broken because it needs
softpin for the DRI driver to work.

** Changed in: mesa (Ubuntu Bionic)
   Status: Fix Released => In Progress

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

Title:
  [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa

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

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

[Bug 1810728] Re: cups error - internal server error when adding a printer

2019-08-05 Thread dick via ubuntu-bugs
I am not sure that the update fixed the problem. I am running 19.04 that
is up to date and I am still having the problem with installing a
network printer.

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

Title:
  cups error - internal server error when adding a printer

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

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

  1   2   3   4   5   >