[Bug 1809083] [NEW] [Ubuntu 18.04] Backward migration of Ubuntu 16.04.4 P8 guest from Ubuntu 18.04 P9 Host -> Ubuntu 16.04.4 P8 host is broken

[bugproxy]

Public bug reported:

== Comment: #0 - Balamuruhan S  - 2018-05-02 08:09:21 ==
---Problem Description---
Backward migration of Ubuntu 16.04.4 P8 guest from Ubuntu 18.04 P9 Host -> 
Ubuntu 16.04.4 P8 host fails

# virsh -c qemu+ssh://9.40.194.204/system migrate avocado-vt-vm1-migration 
qemu+ssh://9.47.70.201/system --live --verbose
root@9.47.70.201's password: 
Migration: [ 99 %]error: internal error: early end of file from monitor, 
possible problem: 2018-05-02T12:49:07.324377Z qemu-system-ppc64: error while 
loading state for instance 0x0 of device 'cpu'
2018-05-02T12:49:07.332143Z qemu-system-ppc64: load of migration failed: 
Invalid argument
 
This is broken because cpu model QEMU 2.5 (-cpu host,compat=power8) and QEMU 
2.11 (-machine max-cpu-compat=power8) known for latest qemu (Ubuntu 18.04) is 
not compatible with older qemu in (Ubuntu 16.04.4).

Machine Type = Boston 
 
---Steps to Reproduce---
1. Boot healthy P8 16.04.4 Ubuntu guest with explicit compat mode setting on P8 
host due to the reason mentioned on 
https://bugzilla.linux.ibm.com/show_bug.cgi?id=17#c22,


 power8


2. Have P9 Host with 18.04 Ubuntu build and allow iptables to permit
migration

3. Perform migration from Ubuntu 16.04.4 -> Ubuntu 18.04 and it works as
expected,

# virsh migrate avocado-vt-vm1-migration qemu+ssh://9.40.194.204/system --live 
--verbose
Migration: [100 %]

4. Perform backward migration of the same guest from Ubuntu 18.04 P9
host -> Ubuntu 16.04.4 P8 host and it is broken,

# virsh -c qemu+ssh://9.40.194.204/system migrate avocado-vt-vm1-migration 
qemu+ssh://9.47.70.201/system --live --verbose
root@9.47.70.201's password: 
Migration: [ 99 %]error: internal error: early end of file from monitor, 
possible problem: 2018-05-02T12:49:07.324377Z qemu-system-ppc64: error while 
loading state for instance 0x0 of device 'cpu'
2018-05-02T12:49:07.332143Z qemu-system-ppc64: load of migration failed: 
Invalid argument

---uname output---

Ubuntu 18.04 P9 Host:

Kernel
# uname -a
Linux ltc-boston114 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:14:44 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux

Qemu:
# dpkg -l | grep qemu
ii  ipxe-qemu  1.0.0+git-20180124.fbe8c52d-0ubuntu2 
all  PXE boot firmware - ROM images for qemu
ii  ipxe-qemu-256k-compat-efi-roms 1.0.0+git-20150424.a25a16d-0ubuntu2  
all  PXE boot firmware - Compat EFI ROM images for qemu
ii  qemu   1:2.11+dfsg-1ubuntu7 
ppc64el  fast processor emulator
ii  qemu-block-extra:ppc64el   1:2.11+dfsg-1ubuntu7 
ppc64el  extra block backend modules for qemu-system and qemu-utils
ii  qemu-kvm   1:2.11+dfsg-1ubuntu7 
ppc64el  QEMU Full virtualization on x86 hardware
ii  qemu-slof  20170724+dfsg-1ubuntu1   
all  Slimline Open Firmware -- QEMU PowerPC version
ii  qemu-utils 1:2.11+dfsg-1ubuntu7 
ppc64el  QEMU utilities
ii  qemu-utils 1:2.11+dfsg-1ubuntu7 
ppc64el  QEMU utilities

Libvirt:
# dpkg -l | grep libvirt
ii  libvirt-bin4.0.0-1ubuntu8   
ppc64el  programs for the libvirt library
ii  libvirt-clients4.0.0-1ubuntu8   
ppc64el  Programs for the libvirt library
ii  libvirt-daemon 4.0.0-1ubuntu8   
ppc64el  Virtualization daemon
ii  libvirt-daemon-system  4.0.0-1ubuntu8   
ppc64el  Libvirt daemon configuration files
ii  libvirt-dev:ppc64el4.0.0-1ubuntu8   
ppc64el  development files for the libvirt library
ii  libvirt-doc4.0.0-1ubuntu8   
all  documentation for the libvirt library

Ubuntu 16.04.4 P8 Host:

Kernel:
# uname -a
Linux pkvmhab006 4.13.0-39-generic #44~16.04.1-Ubuntu SMP Thu Apr 5 16:41:53 
UTC 2018 ppc64le ppc64le ppc64le GNU/Linux

Qemu:
# dpkg -l | grep qemu
ii  ipxe-qemu   1.0.0+git-20150424.a25a16d-1ubuntu1.2   
   all  PXE boot firmware - ROM images for qemu
ii  qemu-block-extra:ppc64el1:2.5+dfsg-5ubuntu10.25 
   ppc64el  extra block backend modules for qemu-system and qemu-utils
ii  qemu-kvm1:2.5+dfsg-5ubuntu10.25 
   ppc64el  QEMU Full virtualization
ii  qemu-slof   20151103+dfsg-1ubuntu1.1
   all  Slimline Open Firmware -- QEMU PowerPC version
ii  qemu-system-common  1:2.5+dfsg-5ubuntu10.25 
   ppc64el  QEMU full system emulation binaries (common files)
ii  qemu-system-ppc 1:2.5+dfsg-5ubuntu10.25 
   ppc64el  QEMU 

[Bug 1800101] Re: gnome-shell uses 100% CPU

[Daniel van Vugt]

René,

You need to have logged in from another machine (via ssh) and run gdb
from there. That way gdb won't hang when you stop the shell with Ctrl+C.

Please also remember to try uninstalling the nvidia driver (briefly) so
as to compare with nouveau.

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

Title:
  gnome-shell uses 100% CPU

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

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

[Bug 1800101] Re: gnome-shell uses 100% CPU

[René Schultz Madsen]

Daniel,

Now I have experienced the 100% CPU to more times and both times I tried
to follow the guide here
https://wiki.ubuntu.com/Backtrace#Already_running_programs but it's not
possible to go to do "If the program hangs but doesn't crash you can
press ctrl+c in gdb while the program is frozen and then continue with
the next step."

Then gdb hangs :-P so no luck there. See attatched gdb log file. Any
suggestions what to do next?

The thing I have noticed now with the 100% CPU usage is that it's always
after restarting a VM several times in VirtualBox.

** Attachment added: "gdb-gnome-shell.txt"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1800101/+attachment/5223458/+files/gdb-gnome-shell.txt

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

Title:
  gnome-shell uses 100% CPU

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

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

[Bug 1795668] Re: Enable bubblewrap in gnome-desktop3 for Ubuntu 18.04 LTS

[Nicolas Bernaerts]

I've also encountered the same trouble with some of my external
thumbnailers (lo-thumbnailer, msoffice-thumbnailer, ...).

I realised that bwarp calls fail under Ubuntu and Debian because of
--symlink options used on /bin and /sbin. --ro-bind should be used
instead of --symlink.

Till problem is solved on the Nautilus side, I've written a small
article to explain how to get back external thumbnailers under 18.04 and
18.10 with the help of a bwrap wrapper under /usr/local/bin.

http://bernaerts.dyndns.org/linux/360-ubuntu-nautilus-external-
thumbnailer-failure

Hope it helps

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

Title:
  Enable bubblewrap in gnome-desktop3 for Ubuntu 18.04 LTS

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

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

[Bug 1799070] Re: Netboot initrd is not updated with signed modules

[Roland Kaufmann]

It used to be that the kernel in main/installer-amd64 was unsigned,
which is why my scripts had to go look in main/signed instead.
Apparently this changed at some point, which announcement I missed, and
as you say the kernel that is stored together with the netboot image is
now signed. I am happy, as a fair bunch of bespoke logic to figure out
the correct kernel can now be shown the door, and the script becomes
significantly simpler. But, I should have checked this beforehand with
sbverify. Mea culpa indeed. Sorry for the hassle.

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

Title:
  Netboot initrd is not updated with signed modules

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

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

[Bug 1799693] Re: Stable libopus-1.3 released

[Bug Watch Updater]

** Changed in: opus (Debian)
   Status: New => Fix Released

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

Title:
  Stable libopus-1.3 released

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

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

[Bug 1731940] Re: [P7xxDM2(-G), Realtek ALC898, Headphone Jack, External] No sound at all

[Dennis Mungai Lin.Jr.]

A possible work-around: Update the jack's description to PulseAudio, as
shown:

Create the file `/usr/share/pulseaudio/alsa-mixer/paths/iec958-stereo-
output.conf` and populate it with:

```
# This file is part of PulseAudio.
#
# PulseAudio is free software; you can redistribute it and/or modify
# it under the terms of the GNU Lesser General Public License as
# published by the Free Software Foundation; either version 2.1 of the
# License, or (at your option) any later version.
#
# PulseAudio is distributed in the hope that it will be useful, but
# WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
# General Public License for more details.
#
# You should have received a copy of the GNU Lesser General Public License
# along with PulseAudio; if not, see .


[General]
description = Headphones + Digital Output (S/PDIF)

[Element IEC958]
switch = mute
```

Then set the model definition at `/etc/modprobe.d/sound.conf` with the
following entries:

`options snd-hda-intel model=no-primary-hp enable=1 index=0`

When done, issue a reboot.

For current HDA model lists, see http://git.alsa-project.org/?p=alsa-
kernel.git;a=blob;f=Documentation/sound/alsa/HD-Audio-
Models.txt;hb=HEAD.

Will test and report back.

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

Title:
  [P7xxDM2(-G), Realtek ALC898, Headphone Jack, External] No sound at
  all

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

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

[Bug 1542491] Re: Scheduler update_aggregates race causes incorrect aggregate information

[jingtao]

Is there anybody else concerned about this question?

Maybe we can try to synchronize add_host_to_aggregate and
remove_host_from_aggregate.

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

Title:
  Scheduler update_aggregates race causes incorrect aggregate
  information

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

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

[Bug 1808783] Re: GHC removals

[Steve Langasek]

Removing packages from disco:
haskell-cabal-helper 0.8.0.2-1build1 in disco
cabal-helper 0.8.0.2-1build1 in disco amd64
cabal-helper 0.8.0.2-1build1 in disco arm64
cabal-helper 0.8.0.2-1build1 in disco armhf
cabal-helper 0.8.0.2-1build1 in disco i386
cabal-helper 0.8.0.2-1build1 in disco ppc64el
cabal-helper 0.8.0.2-1build1 in disco s390x
libghc-cabal-helper-dev 0.8.0.2-1build1 in disco amd64
libghc-cabal-helper-dev 0.8.0.2-1build1 in disco arm64
libghc-cabal-helper-dev 0.8.0.2-1build1 in disco armhf
libghc-cabal-helper-dev 0.8.0.2-1build1 in disco i386
libghc-cabal-helper-dev 0.8.0.2-1build1 in disco ppc64el
libghc-cabal-helper-dev 0.8.0.2-1build1 in disco s390x
libghc-cabal-helper-doc 0.8.0.2-1build1 in disco amd64
libghc-cabal-helper-doc 0.8.0.2-1build1 in disco arm64
libghc-cabal-helper-doc 0.8.0.2-1build1 in disco armhf
libghc-cabal-helper-doc 0.8.0.2-1build1 in disco i386
libghc-cabal-helper-doc 0.8.0.2-1build1 in disco ppc64el
libghc-cabal-helper-doc 0.8.0.2-1build1 in disco s390x
libghc-cabal-helper-prof 0.8.0.2-1build1 in disco amd64
libghc-cabal-helper-prof 0.8.0.2-1build1 in disco arm64
libghc-cabal-helper-prof 0.8.0.2-1build1 in disco armhf
libghc-cabal-helper-prof 0.8.0.2-1build1 in disco i386
libghc-cabal-helper-prof 0.8.0.2-1build1 in disco ppc64el
libghc-cabal-helper-prof 0.8.0.2-1build1 in disco s390x
Comment: FTBFS with ghc 8.4; Debian bug #913053, LP: #1808783
1 package successfully removed.


** Changed in: haskell-cabal-helper (Ubuntu)
   Status: New => Fix Released

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

Title:
  GHC removals

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

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

[Bug 1809077] [NEW] upgrade 18.10 from lubuntu 18.04

[charlyeds]

Public bug reported:

can't install "lubuntu-core"

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-release-upgrader-core 1:18.04.29
ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
Uname: Linux 4.15.0-42-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: LXDE
Date: Wed Dec 19 07:33:41 2018
InstallationDate: Installed on 2018-06-03 (198 days ago)
InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: No upgrade log present (probably fresh install)
VarLogDistupgradeTermlog:
 
mtime.conffile..etc.update-manager.release-upgrades: 2018-12-13T08:08:33.865470

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


** Tags: amd64 apport-bug bionic dist-upgrade

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

Title:
  upgrade 18.10 from lubuntu 18.04

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

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

[Bug 1808783] Re: GHC removals

[Steve Langasek]

Removing packages from disco:
haskell-cabal-file-th 0.2.4-3 in disco
libghc-cabal-file-th-dev 0.2.4-3 in disco amd64
libghc-cabal-file-th-dev 0.2.4-3 in disco arm64
libghc-cabal-file-th-dev 0.2.4-3 in disco armhf
libghc-cabal-file-th-dev 0.2.4-3 in disco i386
libghc-cabal-file-th-dev 0.2.4-3 in disco ppc64el
libghc-cabal-file-th-dev 0.2.4-3 in disco s390x
libghc-cabal-file-th-doc 0.2.4-3 in disco amd64
libghc-cabal-file-th-doc 0.2.4-3 in disco arm64
libghc-cabal-file-th-doc 0.2.4-3 in disco armhf
libghc-cabal-file-th-doc 0.2.4-3 in disco i386
libghc-cabal-file-th-doc 0.2.4-3 in disco ppc64el
libghc-cabal-file-th-doc 0.2.4-3 in disco s390x
libghc-cabal-file-th-prof 0.2.4-3 in disco amd64
libghc-cabal-file-th-prof 0.2.4-3 in disco arm64
libghc-cabal-file-th-prof 0.2.4-3 in disco armhf
libghc-cabal-file-th-prof 0.2.4-3 in disco i386
libghc-cabal-file-th-prof 0.2.4-3 in disco ppc64el
libghc-cabal-file-th-prof 0.2.4-3 in disco s390x
Comment: FTBFS with ghc 8.4; Debian bug #911570, LP: #1808783
1 package successfully removed.


** Changed in: haskell-cabal-file-th (Ubuntu)
   Status: New => Fix Released

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

Title:
  GHC removals

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

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

[Bug 1808783] Re: GHC removals

[Steve Langasek]

Removing packages from disco:
haskell-blogliterately 0.8.6.2-1build3 in disco
blogliterately 0.8.6.2-1build3 in disco amd64
blogliterately 0.8.6.2-1build3 in disco arm64
blogliterately 0.8.6.2-1build3 in disco armhf
blogliterately 0.8.6.2-1build3 in disco i386
blogliterately 0.8.6.2-1build3 in disco ppc64el
blogliterately 0.8.6.2-1build3 in disco s390x
libghc-blogliterately-dev 0.8.6.2-1build3 in disco amd64
libghc-blogliterately-dev 0.8.6.2-1build3 in disco arm64
libghc-blogliterately-dev 0.8.6.2-1build3 in disco armhf
libghc-blogliterately-dev 0.8.6.2-1build3 in disco i386
libghc-blogliterately-dev 0.8.6.2-1build3 in disco ppc64el
libghc-blogliterately-dev 0.8.6.2-1build3 in disco s390x
libghc-blogliterately-doc 0.8.6.2-1build3 in disco amd64
libghc-blogliterately-doc 0.8.6.2-1build3 in disco arm64
libghc-blogliterately-doc 0.8.6.2-1build3 in disco armhf
libghc-blogliterately-doc 0.8.6.2-1build3 in disco i386
libghc-blogliterately-doc 0.8.6.2-1build3 in disco ppc64el
libghc-blogliterately-doc 0.8.6.2-1build3 in disco s390x
libghc-blogliterately-prof 0.8.6.2-1build3 in disco amd64
libghc-blogliterately-prof 0.8.6.2-1build3 in disco arm64
libghc-blogliterately-prof 0.8.6.2-1build3 in disco armhf
libghc-blogliterately-prof 0.8.6.2-1build3 in disco i386
libghc-blogliterately-prof 0.8.6.2-1build3 in disco ppc64el
libghc-blogliterately-prof 0.8.6.2-1build3 in disco s390x
Comment: FTBFS with ghc 8.4; Debian bug #914449, LP: #1808783
Remove [y|N]? y
1 package successfully removed.


** Changed in: haskell-blogliterately (Ubuntu)
   Status: New => Fix Released

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

Title:
  GHC removals

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

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

[Bug 1808783] Re: GHC removals

[Steve Langasek]

git-annex build-depends on haskell-cabal; what should be done with this?

** Changed in: haskell-cabal (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/1808783

Title:
  GHC removals

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

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

[Bug 1799497] Re: 4.15 kernel hard lockup about once a week

[Luis Rodriguez]

OK.. it is been quite a while with no locks I had it once after the zram
config pacakge was removed,, but no other locks since then.

kernel version is  4.15.0-33 to 38 in different servers.. I am going to
update the servers to latest version reboot, and wait for a little
longer.

then I am going to install back zram-config on certain servers to see if
it shows up again.

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

Title:
  4.15 kernel hard lockup about once a week

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

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

[Bug 1808783] Re: GHC removals

[Steve Langasek]

Removing packages from disco:
elpa-agda2-mode 2.5.3-5build3 in disco armhf
libghc-agda-dev 2.5.3-5build3 in disco armhf
libghc-agda-doc 2.5.3-5build3 in disco armhf
Comment: ANAIS
3 packages successfully removed.


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

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

Title:
  GHC removals

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

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

[Bug 1805097] Re: A bunch of ACPI Errors

[Yoshiba]

** Description changed:

  [   12.867697] ACPI Error: No handler for Region [ECRM] (5c67776a) 
[EmbeddedControl] (20180531/evregion-132)
  [   12.867709] ACPI Error: Region EmbeddedControl (ID=3) has no handler 
(20180531/exfldio-265)
  [   12.867724] No Local Variables are initialized for Method [OBTS]
  [   12.867727] Initialized Arguments for Method [OBTS]:  (1 arguments defined 
for method invocation)
  [   12.867728]   Arg0:   fa7e36ecInteger 

  [   12.867739] ACPI Error: Method parse/execution failed \OBTS, AE_NOT_EXIST 
(20180531/psparse-516)
  [   12.867752] ACPI Error: Method parse/execution failed \AMW0.DEVS, 
AE_NOT_EXIST (20180531/psparse-516)
  [   12.867767] ACPI Error: Method parse/execution failed \AMW0.WMBC, 
AE_NOT_EXIST (20180531/psparse-516)
  [   12.920848] ACPI Error: No handler for Region [ECRM] (5c67776a) 
[EmbeddedControl] (20180531/evregion-132)
  [   12.920861] ACPI Error: Region EmbeddedControl (ID=3) has no handler 
(20180531/exfldio-265)
  [   12.920875] No Local Variables are initialized for Method [OBTS]
  [   12.920878] Initialized Arguments for Method [OBTS]:  (1 arguments defined 
for method invocation)
  [   12.920879]   Arg0:   ae4b9fc7Integer 

  [   12.920890] ACPI Error: Method parse/execution failed \OBTS, AE_NOT_EXIST 
(20180531/psparse-516)
  [   12.920903] ACPI Error: Method parse/execution failed \AMW0.DEVS, 
AE_NOT_EXIST (20180531/psparse-516)
  [   12.920918] ACPI Error: Method parse/execution failed \AMW0.WMBC, 
AE_NOT_EXIST (20180531/psparse-516)
- [   12.960632] rtl8192cu 1-2.4:1.0 wlx0013ef75041d: renamed from wlan0
+ [   12.960632] rtl8192cu 1-2.4:1.0 wlx: renamed from wlan0
  
  cpuinfo
  processor   : 0
  vendor_id   : GenuineIntel
  cpu family  : 6
  model   : 55
  model name  : Intel(R) Pentium(R) CPU  J2900  @ 2.41GHz
  stepping: 8
  microcode   : 0x837
  cpu MHz : 1332.996
  cache size  : 1024 KB
  physical id : 0
  siblings: 4
  core id : 0
  cpu cores   : 4
  apicid  : 0
  initial apicid  : 0
  fpu : yes
  fpu_exception   : yes
  cpuid level : 11
  wp  : yes
  flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx 
rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology 
tsc_reliable nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 
monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt 
tsc_deadline_timer rdrand lahf_lm 3dnowprefetch epb pti ibrs ibpb stibp 
tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms dtherm ida arat
  bugs: cpu_meltdown spectre_v1 spectre_v2
  bogomips: 4831.40
  clflush size: 64
  cache_alignment : 64
  address sizes   : 36 bits physical, 48 bits virtual
  power management:
  
  processor   : 1
  vendor_id   : GenuineIntel
  cpu family  : 6
  model   : 55
  model name  : Intel(R) Pentium(R) CPU  J2900  @ 2.41GHz
  stepping: 8
  microcode   : 0x837
  cpu MHz : 1332.896
  cache size  : 1024 KB
  physical id : 0
  siblings: 4
  core id : 1
  cpu cores   : 4
  apicid  : 2
  initial apicid  : 2
  fpu : yes
  fpu_exception   : yes
  cpuid level : 11
  wp  : yes
  flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx 
rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology 
tsc_reliable nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 
monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm sse4_1 sse4_2 movbe popcnt 
tsc_deadline_timer rdrand lahf_lm 3dnowprefetch epb pti ibrs ibpb stibp 
tpr_shadow vnmi flexpriority ept vpid tsc_adjust smep erms dtherm ida arat
  bugs: cpu_meltdown spectre_v1 spectre_v2
  bogomips: 4831.40
  clflush size: 64
  cache_alignment : 64
  address sizes   : 36 bits physical, 48 bits virtual
  power management:
  
  processor   : 2
  vendor_id   : GenuineIntel
  cpu family  : 6
  model   : 55
  model name  : Intel(R) Pentium(R) CPU  J2900  @ 2.41GHz
  stepping: 8
  microcode   : 0x837
  cpu MHz : 1332.828
  cache size  : 1024 KB
  physical id : 0
  siblings: 4
  core id : 2
  cpu cores   : 4
  apicid  : 4
  initial apicid  : 4
  fpu : yes
  fpu_exception   : yes
  cpuid level : 11
  wp  : yes
  flags   : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx 
rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology 
tsc_reliable nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dte

[Bug 1805098] Re: failed to assign [mem size 0x00200000 64bit pref]

[Yoshiba]

More system info check this post below.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805097

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

** Tags added: kernel-bug-exists-upstream

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

Title:
  failed to assign [mem size 0x0020 64bit pref]

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

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

[Bug 1805097] Re: A bunch of ACPI Errors

[Yoshiba]

wifisyslog

** Attachment added: "wifisyslog"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805097/+attachment/5223447/+files/wifisyslog

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

Title:
  A bunch of ACPI Errors

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

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

[Bug 1808968] Re: MSA 2050 is not registered

[Jonghan]

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

** No longer affects: xmms (Ubuntu)

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

Title:
  MSA 2050 is not registered

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

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

[Bug 1805099] Re: nvidia: module verification failed: signature and/or required key missing - tainting kernel

[Yoshiba]

More system info check this post below.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805097

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

** Tags added: kernel-bug-exists-upstream

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

Title:
  nvidia: module verification failed: signature and/or required key
  missing - tainting kernel

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

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

[Bug 1805097] Re: A bunch of ACPI Errors

[Yoshiba]

UdevDb

** Attachment removed: "UdevDb.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805097/+attachment/5223191/+files/UdevDb.txt

** Attachment added: "UdevDb"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805097/+attachment/5223446/+files/UdevDb

** Tags added: kernel-bug-exists-upstream

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

Title:
  A bunch of ACPI Errors

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

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

[Bug 1807974] Re: Wireless regularly breaking (ath10k firmware crashed!) after upgrade to Cosmic

[Kai-Heng Feng]

The firmware for this device got updated recently [1].
Please copy binary blobs in [2] to the same relative path under /lib/firmwares/.

[1] https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/commit/?id=a87eb5f7bac0f70ade57da57d9126d14eee12336

[2] https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-
firmware.git/tree/ath10k/QCA6174/hw3.0

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

Title:
  Wireless regularly breaking (ath10k firmware crashed!) after upgrade
  to Cosmic

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

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

[Bug 1809073] [NEW] package xbrlapi 5.5-4ubuntu2.0.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

[Vikramjit Roy]

Public bug reported:

I am not able to back up

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: xbrlapi 5.5-4ubuntu2.0.1
ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
Uname: Linux 4.15.0-39-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
Date: Wed Dec 19 11:16:56 2018
DuplicateSignature:
 package:xbrlapi:5.5-4ubuntu2.0.1
 Unpacking python-gi (3.26.1-2) ...
 dpkg: error processing package xbrlapi (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2018-11-16 (32 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.1
 apt  1.6.6
SourcePackage: brltty
Title: package xbrlapi 5.5-4ubuntu2.0.1 failed to install/upgrade: package is 
in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  package xbrlapi 5.5-4ubuntu2.0.1 failed to install/upgrade: package is
  in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

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

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

[Bug 1805097] Re: A bunch of ACPI Errors

[Yoshiba]

dmesg

** Attachment added: "dmesg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1805097/+attachment/5223438/+files/dmesg

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

Title:
  A bunch of ACPI Errors

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

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

[Bug 1542491] Re: Scheduler update_aggregates race causes incorrect aggregate information

[jingtao]

** Changed in: nova
 Assignee: (unassigned) => jingtao (liang888)

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

Title:
  Scheduler update_aggregates race causes incorrect aggregate
  information

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

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

[Bug 1752437]

[obelisk]

I can confirm 4.19 from Ubuntu works well with Ubuntu 8.10, I've been
using it for a couple of days now, it's fast and stable as long as you
don't try to suspend (which freezes the machine).

I suspect that there is a long way to go for proper ACPI states support,
but that's a whole different ticket :-)

Thanks all!

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

Title:
  [HP ENVY x360 - 15-bq102ng] Touchscreen does not work

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

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

[Bug 1774569] Re: gsmartcontrol, hdparm, and ZFS all refuse to talk to an apparently working Seagate Backup+ Hub drive after upgrade to 18.04

[axion]

HDParm/SDParm bug afects me as well with 2 different Seagate usb drives,
I think this one should have a high priority, since it also affects
power management. Further more since the aforementioned drive is also a
sub-hub it would be good to be able to turn on/off the drive portion
without needing to re-plug the usb-cable or the power-cable.

However I cannot confirm or deny if this behaviour was not observed in
17.04.

Seagate Backup+ Hub;

[733263.671304] usb 1-2: new full-speed USB device number 82 using xhci_hcd
[733263.927640] usb 2-2: new SuperSpeed USB device number 49 using xhci_hcd
[733263.953201] usb 2-2: New USB device found, idVendor=0bc2, idProduct=ab45
[733263.953206] usb 2-2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
[733263.953209] usb 2-2: Product: Backup+ Hub
[733263.953211] usb 2-2: Manufacturer: Seagate
[733263.953214] usb 2-2: SerialNumber: 01CB7447B2D2
[733263.955412] hub 2-2:1.0: USB hub found
[733263.955699] hub 2-2:1.0: 3 ports detected
[733264.075319] usb 1-2: new high-speed USB device number 83 using xhci_hcd
[733264.226923] usb 1-2: New USB device found, idVendor=0bc2, idProduct=ab44
[733264.226928] usb 1-2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
[733264.226931] usb 1-2: Product: Backup+ Hub
[733264.226934] usb 1-2: Manufacturer: Seagate
[733264.226936] usb 1-2: SerialNumber: 01CB7447B2D2
[733264.228162] hub 1-2:1.0: USB hub found
[733264.228426] hub 1-2:1.0: 3 ports detected
[733264.303425] usb 2-2.1: new SuperSpeed USB device number 50 using xhci_hcd
[733264.324224] usb 2-2.1: New USB device found, idVendor=0bc2, idProduct=ab38
[733264.324228] usb 2-2.1: New USB device strings: Mfr=2, Product=3, 
SerialNumber=1
[733264.324232] usb 2-2.1: Product: Backup+ Hub BK
[733264.324234] usb 2-2.1: Manufacturer: Seagate
[733264.324236] usb 2-2.1: SerialNumber: NA8TS9K5
[733264.328836] scsi host6: uas
[733264.329274] scsi 6:0:0:0: Direct-Access Seagate  Backup+ Hub BK   D781 
PQ: 0 ANSI: 6
[733264.329760] sd 6:0:0:0: Attached scsi generic sg0 type 0
[733264.329875] sd 6:0:0:0: [sda] Spinning up disk...
[733265.291754] usb 1-2-port2: Cannot enable. Maybe the USB cable is bad?
[733265.363336] .
[733266.387390] .
[733267.411383] .
[733268.435283] .
[733269.459369] .
[733270.483306] .
[733271.507316] .
[733272.531296] .
[733273.559245] .
[733274.579343] .
[733275.603273] .
[733276.627270] .
[733276.628098] ready
[733276.628416] sd 6:0:0:0: [sda] 11721045167 512-byte logical blocks: (6.00 
TB/5.46 TiB)
[733276.641757] sd 6:0:0:0: [sda] Write Protect is off
[733276.641759] sd 6:0:0:0: [sda] Mode Sense: 4f 00 00 00
[733276.641909] sd 6:0:0:0: [sda] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
[733276.774212]  sda: sda1
[733276.775169] sd 6:0:0:0: [sda] Attached SCSI disk

Seagate Expansion Desk;

[733476.458208] usb 2-2: new SuperSpeed USB device number 52 using xhci_hcd
[733476.483130] usb 2-2: New USB device found, idVendor=0bc2, idProduct=3320
[733476.483137] usb 2-2: New USB device strings: Mfr=2, Product=3, 
SerialNumber=1
[733476.483141] usb 2-2: Product: Expansion Desk
[733476.483145] usb 2-2: Manufacturer: Seagate
[733476.483149] usb 2-2: SerialNumber: NA4MBV5C
[733476.487448] scsi host6: uas
[733476.489027] scsi 6:0:0:0: Direct-Access Seagate  Expansion Desk   0711 
PQ: 0 ANSI: 6
[733476.489568] sd 6:0:0:0: Attached scsi generic sg0 type 0
[733476.489702] sd 6:0:0:0: [sda] Spinning up disk...
[733477.522122] .
[733478.546133] .
[733479.570122] .
[733480.594118] .
[733481.618115] .
[733482.642179] .
[733483.666088] .
[733484.690112] .
[733485.714083] .
[733486.738101] .
[733487.762049] .
[733488.786066] .
[733488.787214] ready
[733488.787477] sd 6:0:0:0: [sda] 976754645 4096-byte logical blocks: (4.00 
TB/3.64 TiB)
[733488.803316] sd 6:0:0:0: [sda] Write Protect is off
[733488.803318] sd 6:0:0:0: [sda] Mode Sense: 4f 00 00 00
[733488.803468] sd 6:0:0:0: [sda] Write cache: enabled, read cache: enabled, 
doesn't support DPO or FUA
[733488.869597]  sda: sda1
[733488.870488] sd 6:0:0:0: [sda] Attached SCSI disk

OnMemory USB-Core.
Th following drive gives a different "sparm/hdparm -i" and can be set to 
spindown and use power management and is smart capable.

[733625.017283] usb 2-2: new SuperSpeed USB device number 53 using xhci_hcd
[733625.037984] usb 2-2: New USB device found, idVendor=174c, idProduct=55aa
[733625.037988] usb 2-2: New USB device strings: Mfr=2, Product=3, 
SerialNumber=1
[733625.037990] usb 2-2: Product: External HDD
[733625.037992] usb 2-2: Manufacturer: 
01234567890123456789012345678901234567890123
[733625.037994] usb 2-2: SerialNumber: 201202152114
[733625.039122] usb-storage 2-2:1.0: USB Mass Storage device detected
[733625.039243] usb-storage 2-2:1.0: Quirks match for vid 174c pid 55aa: 40
[733625.039267] scsi host6: usb-storage 2-2:1.0
[733635.521181] scsi 6:0:0:0: Direct-Access TOSHIBA  DT01ACA300   MX6O 
PQ: 0 ANSI: 5
[733635.521835] sd 6:0:0:0: Attached scsi generic sg0 type 0
[733635

[Bug 1806532] Re: The line-out on the Dell Dock station can't work

[Hui Wang]

This is the debdiff for bionic, it is not an incremental debdiff (since
the debdiff of #3 is not merged to bionic-proposed branch yet), this
debdiff will replace the one in the #3. It fixed the problem of
forgetting to add dir in the configure.ac.



** Patch added: "alsa-lib_1.1.3-5ubuntu0.2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806532/+attachment/5223434/+files/alsa-lib_1.1.3-5ubuntu0.2.debdiff

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

Title:
  The line-out on the Dell Dock station can't work

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

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

[Bug 1335492]

[Andreldm-2]

@alexxcons the patch proposed in Bug 14979 might help or worsen this
one.

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

Title:
  [4.11.8] Desktop icons rearrange on each login

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

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

[Bug 1781879] Re: Latest ASUS trackpad doesn't work in Ubuntu

[Kai-Heng Feng]

Oops, I forgot what commits I backported.

So please test the following kernels,
Bionic: https://people.canonical.com/~khfeng/lp1781879-bionic/
Cosmic: https://people.canonical.com/~khfeng/lp1781879-cosmic/

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

Title:
  Latest ASUS trackpad doesn't work in Ubuntu

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

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

[Bug 1657409] Re: [MIR] virglrenderer

[Seth Arnold]

I reviewed virglrenderer version 0.7.0-1 as checked into disco; this
shouldn't be considered a full security audit but rather a quick gauge of
maintainability.

virgl is an attempt to provide GPUs to guests that leverage the host GPUs
but may not be direct passthroughs of devices.

There's 14 CVEs in our database; most were the result of one fairly active
researcher who appeared to be doing a fairly thorough job. I had the
impression the fixes were handled well.

- Build-Depends: autoconf-archive, debhelper, libdrm-dev,
  libegl1-mesa-dev, libepoxy-dev, libgbm-dev, pkg-config, python

Is the python build dependency cause for concern?

- Does not daemonize
- Does not appear to listen to network
- No pre/post inst/rm scripts
- No init scripts
- No systemd services
- No dbus services
- No setuid files
- No binaries in PATH
- No sudo fragments
- No udev rules
- There's 6KLOC in tests/ but nothing appears to run during the build
- No cron jobs
- Build logs are extremely messy. Addressing the issues would be an
  immense undertaking. (To the point that switching to C++ to use
  std::string or Rust to use String would be easier than trying to
  address these issues in C.)

- No subprocesses spawned
- Memory management is pretty rough. C string operations without bounds
  checking, snprintfs without error return validations, etc. Fixed length
  stack-allocated buffers are used extensively and it's far from clear
  that all inputs will properly fit into the buffers.

  The generated GLGL inputs are fed into other tools and errors would
  likely cause cascading failures.

  Addressing this in C could be a disaster. I suspect trying to "fix" the
  existing code would introduce more errors than it would solve. A rewrite
  into a better language would be a lot more plausible to me.

- Opens /dev/dri/renderD* files
- Logging looked fine
- Uses many of its own environment variables:
  GALLIUM_LOG_FILE, GALLIUM_PRINT_OPTIONS, TGSI_PRINT_SANITY,
  GALLIUM_DUMP_CPU, VIRGL_DISABLE_MT, VTEST_SAVE, VTEST_USE_GLX,
  VTEST_USE_EGL_SURFACELESS, VTEST_USE_GLES, LIBGL_ALWAYS_SOFTWARE,
- No privileged operations
- No cryptography
- I'm unsure about networking -- the test infrastructure uses unix domain
  sockets, but I don't obviously spot how virglrenderer interacts outside
  its process.
- No privileged portions of code
- No temp files
- No webkit
- No JavaScript
- Some cppcheck errors have been fixed upstream since our package

I don't love the GLGL code generation. Running this code may bring the
guest operating system video drivers into the trusted codebase.

I discussed some of the issues I found with upstream authors and found
them very responsive and understanding. (To be clear I found nothing of
importance.)

Security team ACK for promoting virglrenderer to main.

Thanks


** Changed in: virglrenderer (Ubuntu)
 Assignee: Ubuntu Security Team (ubuntu-security) => (unassigned)

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

Title:
  [MIR] virglrenderer

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

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

[Bug 1798462] Re: package linux-image-4.15.0-36-generic 4.15.0-36.39 failed to install/upgrade: installed linux-image-4.15.0-36-generic package post-installation script subprocess returned error exit

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

Title:
  package linux-image-4.15.0-36-generic 4.15.0-36.39 failed to
  install/upgrade: installed linux-image-4.15.0-36-generic package post-
  installation script subprocess returned error exit status 1

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

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

[Bug 1797898] Re: evebody

[Launchpad Bug Tracker]

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

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

Title:
  evebody

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

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

[Bug 1787739] Re: postfix name lookup failed after dist-upgrade (Aug-2018)

[Launchpad Bug Tracker]

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

** Changed in: bind9 (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/1787739

Title:
  postfix name lookup failed after dist-upgrade (Aug-2018)

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

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

[Bug 1798810] Re: installer crashes after failing to install bootloader

[Launchpad Bug Tracker]

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

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

Title:
  installer crashes after failing to install bootloader

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

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

[Bug 1798672] Re: Not possible to upgrade from 16.04 LTS to 18.04 LTS

[Launchpad Bug Tracker]

[Expired for ubuntu-release-upgrader (Ubuntu) because there has been no
activity for 60 days.]

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

Title:
  Not possible to upgrade from 16.04 LTS to 18.04 LTS

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

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

[Bug 1798802] Re: package linux-headers-4.4.0-128-generic 4.4.0-128.154 failed to install/upgrade: package linux-headers-4.4.0-128-generic is not ready for configuration cannot configure (current stat

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

Title:
  package linux-headers-4.4.0-128-generic 4.4.0-128.154 failed to
  install/upgrade: package linux-headers-4.4.0-128-generic is not ready
  for configuration  cannot configure (current status 'half-installed')

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

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

[Bug 1798800] Re: Ubuntu 18.04->18.10 upgrade, blank screen on/before login

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

Title:
  Ubuntu 18.04->18.10 upgrade, blank screen on/before login

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

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

[Bug 1798614] Re: It doesn't regonize my touchpad after automaticly closing screen (or maybe suspend)

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

Title:
  It doesn't regonize my touchpad after automaticly closing screen (or
  maybe suspend)

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

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

[Bug 903651] Re: When opening files from network share, applications try to cache entire file locally

[Launchpad Bug Tracker]

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

** Changed in: file-roller (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/903651

Title:
  When opening files from network share, applications try to cache
  entire file locally

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

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

[Bug 1806532] Re: The line-out on the Dell Dock station can't work

[Hui Wang]

The build failure for cosmic and bionic (after applying the debdiff of
#2 and #3) is because I forgot to add one more patch to add this ucm to
configure.ac.

here I fixed it, and generate an incremental debdiff for cosmic (since
the debdiff of #2 is already merged to cosmic-proposed branch). If need
me put this debdiff and the debdiff of #2 into one debdiff, let me know.

thanks.

This is the incremental debdiff based on #2 for Cosmic.


** Patch added: "alsa-lib_1.1.6-1ubuntu1.2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806532/+attachment/5223433/+files/alsa-lib_1.1.6-1ubuntu1.2.debdiff

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

Title:
  The line-out on the Dell Dock station can't work

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

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

[Bug 1806488] Re: Support non-strict iommu mode on arm64

[dann frazier]

** Description changed:

  [Impact]
- There's a significant performance gain to be had by removing the need to 
flush the IOMMU TLB on every unmap. I'm seeing a 25% performance gain w/ fio 
reads on a single NVMe device. This mode of operation is available for x86 via 
the "intel_iommu=strict" parameter. This support is now available upstream for 
ARM platforms via the "iommu.strict=[0|1]" parameter, while keeping the default 
in strict mode.
+ The Intel IOMMU driver provides an option for strict mode. When disabled, 
batching of IOTLB flush operations is permitted, allowing the user to trade-off 
isolation for improved performance. Ubuntu's kernel currently lacks a parity 
for this feature for ARM.
+ 
+ There's a significant performance gain to be had by removing the need to
+ flush the IOMMU TLB on every unmap on arm64. I'm seeing a 25%
+ performance gain w/ fio reads on a single NVMe device.
+ 
+ This mode of operation is available for x86 via the "intel_iommu=strict"
+ parameter. Upstream now exposes an equivalent feature for ARM platforms
+ via the "iommu.strict=[0|1]" parameter, while retaining the default
+ strict-enabled mode.
  
  [Test Case]
  $ cat fio.rc
  [global]
  rw=read
  direct=1
  ioengine=libaio
  iodepth=2048
  numjobs=10
  bs=4k
  group_reporting=1
  group_reporting=1
  cpumask=0xff
  runtime=100
  loops = 1
  
  [job1]
  filename=/dev/nvme0n1
  
  [Fix]
  44f6876a00e83 iommu/arm-smmu: Support non-strict mode
  b2dfeba654cb0 iommu/io-pgtable-arm-v7s: Add support for non-strict mode
  9662b99a19abc iommu/arm-smmu-v3: Add support for non-strict mode
  b6b65ca20bc93 iommu/io-pgtable-arm: Add support for non-strict mode
  68a6efe86f6a1 iommu: Add "iommu.strict" command line option
  2da274cdf998a iommu/dma: Add support for non-strict mode
  07fdef34d2be6 iommu/arm-smmu-v3: Implement flush_iotlb_all hook
  85c7a0f1ef624 iommu/io-pgtable-arm: Fix race handling in split_blk_unmap()
  
  [Regression Risk]
+ Most of these patches are specific to ARM, and have been regression tested on 
both arm64 (HiSilicon D06) and armhf (QEMU virt) using "stress-ng --vm $(nproc)"
+ 
+ 2 patches do touch arch-indep code however:
+ 
+ > 68a6efe86f6a1 iommu: Add "iommu.strict" command line option
+ Adds a new command line option and sets an attribute that iommu drivers can 
optionally react to. Doesn't change default behavior.
+ 
+ > 2da274cdf998a iommu/dma: Add support for non-strict mode
+ This driver is only built for arm64 and ppc64el (determined by looking at the 
build logs). Most of this patch only changes behavior in the non-default (and 
new) iommu.strict=0 case. The exception, which is called out in the commit 
message, is this hunk:
+ 
+ -   WARN_ON(iommu_unmap(domain, dma_addr, size) != size);
+ +   WARN_ON(iommu_unmap_fast(domain, dma_addr, size) != size);
+ +   if (!cookie->fq_domain)
+ +   iommu_tlb_sync(domain);
+ 
+ 
+ In the default case, where fq_domain will be NULl, we are now factoring 
iommu_unmap() into:
+   iommu_unmap_fast()
+   iommu_tlb_sync()
+ 
+ Looking at the source to iommu_unmap() confirms that this is
+ functionally equivalent.

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

Title:
  Support non-strict iommu mode on arm64

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

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

[Bug 1808588] Re: Upgrade from 18.04 to 18.10 lost trackpad/trackpoint

[Kai-Heng Feng]

Please attach output of `cat /sys/bus/serio/devices/serio1/firmware_id`,
thanks!

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

Title:
  Upgrade from 18.04 to 18.10 lost trackpad/trackpoint

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

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

[Bug 1808588] Re: Upgrade from 18.04 to 18.10 lost trackpad/trackpoint

[Alexis Dinno]

@kaihengfeng Your suggestion did the trick! I had tried a similar
parameter I found elsewhere on the web (I *think* it was something like
'psmouse.elantech=0') to no avail.

Thank you Kai-Heng Feng!

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

Title:
  Upgrade from 18.04 to 18.10 lost trackpad/trackpoint

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

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

[Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

[VanVan]

It's already commited, check here :
http://mailman.alsa-project.org/pipermail/alsa-devel/2018-December/143282.html

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

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

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

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

[Bug 1809053] Re: package openssh-server 1:7.6p1-4ubuntu0.1 failed to install/upgrade: installed openssh-server package post-installation script subprocess was killed by signal (Aborted)

[David Langolf]

Unfortunately I don't. I let it run, came back a couple hours later and
it wasn't accepting my password. I just let it continue. Was able to
login in the morning and it finished installing while I was at work.
When I got home it worked except for the installation errors posted
here.

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

Title:
  package openssh-server 1:7.6p1-4ubuntu0.1 failed to install/upgrade:
  installed openssh-server package post-installation script subprocess
  was killed by signal (Aborted)

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

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

[Bug 1808944] Re: ndiswrapper-dkms 1.59-2: ndiswrapper kernel module failed to build [error: implicit declaration of function ‘vmalloc’]

[Daniel van Vugt]

Sounds almost like bug 1514243, but the function name has changed.

I personally recommend upgrading to at least Ubuntu 16.04 or later since
14.04 will reach end of life in a few months from now
(https://wiki.ubuntu.com/Releases).

If you can, try Ubuntu 18.04. Although it looks like you might encounter
bug 1727356 in the official release of 18.04 so you might want to use
this instead: http://cdimages.ubuntu.com/bionic/daily-live/current/

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

Title:
  ndiswrapper-dkms 1.59-2: ndiswrapper kernel module failed to build
  [error: implicit declaration of function ‘vmalloc’]

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

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

[Bug 1808944] Re: ndiswrapper-dkms 1.59-2: ndiswrapper kernel module failed to build [error: implicit declaration of function ‘vmalloc’]

[Daniel van Vugt]

** Summary changed:

- ndiswrapper-dkms 1.59-2: ndiswrapper kernel module failed to build
+ ndiswrapper-dkms 1.59-2: ndiswrapper kernel module failed to build [error: 
implicit declaration of function ‘vmalloc’]

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

Title:
  ndiswrapper-dkms 1.59-2: ndiswrapper kernel module failed to build
  [error: implicit declaration of function ‘vmalloc’]

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

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

[Bug 1807743] Re: QEMU timerfd_create support on PowerPC

[Wes Tarro]

I have tested this package and it fixes the bug without causing any
regressions in my tests. To test the update I re-performed the test case
procedure to verify the updated package fixed the bug and then used the
updated package to run the unit tests for an internal application
compiled for ppc64.

Is that enough to move this from verification-needed to verification-
done?

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

Title:
  QEMU timerfd_create support on PowerPC

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

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

[Bug 374079] Re: Internal microphone doesn't work at all

[Daniel van Vugt]

David,

Please log your own new bug from an affected machine by running:

  ubuntu-bug pulseaudio


** Changed in: alsa-driver (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  Internal microphone doesn't work at all

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

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

[Bug 1808990] Re: Xorg freeze

[Daniel van Vugt]

If you can't log in remotely any more then that sounds like a kernel
issue. But regardless, please:

 1. Reproduce the freeze again.

 2. Reboot

 3. Run this command to collect the system log from the previous
(frozen) boot:

journalctl -b-1 > prevboot.txt

 4. Attach the file 'prevboot.txt' to the bug here.


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

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

** Tags added: nouveau

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

Title:
  Xorg freeze

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

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

[Bug 1808990] Re: Xorg freeze

[Daniel van Vugt]

Alternatively, log in remotely before the freeze happens and start
collecting the system log this way:

  dmesg -w > kernellogprefreeze.txt

Then reproduce the freeze, reboot and send us the above file.

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

Title:
  Xorg freeze

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

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

[Bug 1808881] Re: Unwanted touchpad movements on tap with Synaptics touchpad on DELL Inspiron-3521

[Daniel van Vugt]

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

** Description changed:

+ https://gitlab.freedesktop.org/libinput/libinput/issues/199
+ 
+ ---
+ 
  When using the touchpad, the mouse cursor moves even when keeping the
  finger still on one point.
  
  Triggering the behaviour: this happens when the contact surface is very
  small, so it gets triggered for example when tapping on a button, right
  before the finger leaves the touchpad. This makes clicking buttons using
  the touchpad (for example, the "x" button in the browser tabs) very
  difficult.
  
  In attachment, an evemu-record done keeping the finger on one point,
  barely touching the touchpad.
  
  The recording was done with the command:
  
  sudo evemu-record > touchpad.evemu
  Available devices:
  /dev/input/event0:Power Button
  /dev/input/event1:Lid Switch
  /dev/input/event2:Power Button
  /dev/input/event3:AT Translated Set 2 keyboard
  /dev/input/event4:Video Bus
  /dev/input/event8:SynPS/2 Synaptics TouchPad
  /dev/input/event9:Dell WMI hotkeys
  /dev/input/event10:   HDA Intel PCH Mic
  /dev/input/event11:   HDA Intel PCH Front Headphone
  /dev/input/event12:   HDA Intel PCH HDMI/DP,pcm=3
  /dev/input/event13:   Laptop_Integrated_Webcam_HD: In
  Select the device event number [0-13]: 8
  
  To replay the recording (the strange behaviour is particularly visible
  in the final part):
  
  sudo evemu-play  /dev/input/event8 < touchpad.evemu
  
  (replace event8 with your input device)
  
  System info:
  
  lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  Codename: bionic
  
  apt-cache policy libinput10
  libinput10:
    Installato: 1.10.4-1
    Candidato:  1.10.4-1
    Tabella versione:
   *** 1.10.4-1 500
  500 http://it.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  
  apt-cache policy libinput-bin
  libinput-bin:
    Installato: 1.10.4-1
    Candidato:  1.10.4-1
    Tabella versione:
   *** 1.10.4-1 500
  500 http://it.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

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

Title:
  Unwanted touchpad movements on tap with Synaptics touchpad on DELL
  Inspiron-3521

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

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

[Bug 1808908] Re: Screen not locked when coming out of suspend/hibernate

[Eben Cowley]

In case it's relevant, I'm on a Lenovo Y700 laptop. When I set my password
from the Settings GUI it sets both the root password and the password that
I use to unlock the laptop. At least with the version of gnome that I'm
using, Ubuntu has a lock screen where it shows a wallpaper and the time,
and a login screen which has the user logged in and a field where you type
your password.

Yesterday my password was a string, X. I opened my laptop, entered the
first character of X, expecting the lock screen to transition to the login
screen. The lock screen did not transition into the login screen. I typed
the first character again, and nothing happened. I pressed the spacebar to
try to get the laptop to respond, and it unlocked (without me ever typing
in the password). This was really unnerving because it meant that the
laptop was completely vulnerable, so I rebooted.

After rebooting, I tried entering a random string to log in and it didn't
work. I entered X and it unlocked. I promptly changed both my root password
and my login to the string Y via the Settings GUI. I ran a sudo command and
the terminal would only accept Y as the password. Just a few minutes ago, I
tried unlocking the laptop with X and it worked.

This is really upsetting because it means there's a chance that any random
person could walk up to my laptop and unlock it, regardless of what the
password is. I'm going to upgrade to 18.10 soon, but I think it's pretty
necessary to report this problem. By the way, the bug report says that the
faulty package is gnome-screensaver, but that it's not installed. I don't
know which package is responsible, so I changed that in the bug report.


** Description changed:

  Ubuntu 18.04.1
  
  Just a few minutes ago, I typed the first character of my password, and
  the lock screen didn't change to the login screen. I typed the character
  again and nothing happened, so I pressed the spacebar to try to get the
  thing's attention.
  
- 
  Then it unlocked.
  
- 
- This is spooked me, so I restarted my laptop and tried logging in with a 
random string, and nothing happened. I logged in with my regular password and 
then promptly changed it.
+ This is spooked me, so I restarted my laptop and tried logging in with a
+ random string, and nothing happened. I logged in with my regular
+ password and then promptly changed it.
  
  I tried unlocking my system with my old password, and it worked.
  However, the terminal only recognizes my new root password.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
- Package: gnome-screensaver (not installed)
+ Package: unknown
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Dec 17 23:10:46 2018
  InstallationDate: Installed on 2018-09-15 (94 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: gnome-screensaver
  Symptom: security
  Title: Screen not locked when coming out of suspend/hibernate
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Screen not locked when coming out of suspend/hibernate

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

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

[Bug 1804031] Re: gnome-shell crashed with SIGSEGV in clutter_x11_handle_event()

[Daniel van Vugt]

This bug needs to stay closed (Invalid) per comment #2 because we were
unable to debug the crash report. It would help if you are able to
reproduce the problem and then log a new bug for it. Some handy
instructions for logging a new crash report are here:

https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

I suspect it might turn out to be a duplicate of bug 1783673 or bug
1809058.

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

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

Title:
  gnome-shell crashed with SIGSEGV in clutter_x11_handle_event()

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

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

[Bug 1783673] Re: gnome-shell crashed with SIGSEGV in clutter_input_device_xi2_get_current_tool → clutter_device_manager_xi2_translate_event → clutter_backend_real_translate_event → clutter_x11_handle

[Daniel van Vugt]

** Summary changed:

- gnome-shell crashed with SIGSEGV in 
clutter_input_device_xi2_get_current_tool()
+ gnome-shell crashed with SIGSEGV in clutter_input_device_xi2_get_current_tool 
→ clutter_device_manager_xi2_translate_event → 
clutter_backend_real_translate_event → clutter_x11_handle_event → 
handle_host_xevent

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

Title:
  gnome-shell crashed with SIGSEGV in
  clutter_input_device_xi2_get_current_tool →
  clutter_device_manager_xi2_translate_event →
  clutter_backend_real_translate_event → clutter_x11_handle_event →
  handle_host_xevent

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

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

[Bug 1809058] Re: gnome-shell crashed with SIGSEGV in _clutter_input_device_reset_scroll_info() from clutter_device_manager_xi2_translate_event() from clutter_backend_real_translate_event() from clutt

[Daniel van Vugt]

** Summary changed:

- 
/usr/bin/gnome-shell:11:_clutter_input_device_reset_scroll_info:clutter_device_manager_xi2_translate_event:clutter_backend_real_translate_event:clutter_x11_handle_event:handle_host_xevent
+ gnome-shell crashed with SIGSEGV in _clutter_input_device_reset_scroll_info() 
from clutter_device_manager_xi2_translate_event() from 
clutter_backend_real_translate_event() from clutter_x11_handle_event() from 
handle_host_xevent()

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

Title:
  gnome-shell crashed with SIGSEGV in
  _clutter_input_device_reset_scroll_info() from
  clutter_device_manager_xi2_translate_event() from
  clutter_backend_real_translate_event() from clutter_x11_handle_event()
  from handle_host_xevent()

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

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

[Bug 1809058] [NEW] gnome-shell crashed with SIGSEGV in _clutter_input_device_reset_scroll_info() from clutter_device_manager_xi2_translate_event() from clutter_backend_real_translate_event() from clu

[errors.ubuntu.com bug bridge]

Public bug reported:

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

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


** Tags: artful bionic cosmic vivid wily xenial yakkety zesty

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

Title:
  gnome-shell crashed with SIGSEGV in
  _clutter_input_device_reset_scroll_info() from
  clutter_device_manager_xi2_translate_event() from
  clutter_backend_real_translate_event() from clutter_x11_handle_event()
  from handle_host_xevent()

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

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

[Bug 1784485] Re: [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

[VanVan]

** Changed in: alsa-driver (Ubuntu)
   Status: Confirmed => Fix Committed

** Changed in: linux (Ubuntu)
   Status: Incomplete => 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/1784485

Title:
  [ZenBook S UX391UA, Realtek ALC294, Mic, Internal] No sound at all

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

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

[Bug 1797882] Re: At dual monitor intel_do_flush_locked failed: Resource deadlock avoided

[Daniel van Vugt]

Gert,

Please report the problem to the Mesa developers who will best be able
to help:

  https://bugs.freedesktop.org/enter_bug.cgi?product=Mesa

and then let us know the new bug ID.

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

Title:
  At dual monitor intel_do_flush_locked failed: Resource deadlock
  avoided

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

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

[Bug 1807250] Re: At some point in the 18.04 cycle, /sys/bus/iio has disappeared from my system

[Your full name]

https://news.ycombinator.com/item?id=18711970

The sad state of being able to use Ubuntu on touch devices (hint: you
can't)

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

So, apparently support for an entire bus class has been missing since
ubuntu bionic (18.04 LTS) was released in april. Using kernels from
other distros or ubuntus old xenial 4.4.0-134 all provide access to
sensor data, suggesting the issue is with current (and shipped) kernels.
Three weeks into this not much is happening even though the issue also
affect canonical-specific 4,18 kernels.

This all suggests that pretty much no one has been using ubuntu on touch
devices otherwise i wouldn't be the first one to notice this. Now that
the devs know this they have no time for it...


** Also affects: gdm3 (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/1807250

Title:
  At some point in the 18.04 cycle, /sys/bus/iio has disappeared from my
  system

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

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

[Bug 1809056] [NEW] bind9 package needs install libdns1100 - incomplete dependency

[Ondra]

Public bug reported:

Linux ubuntu 4.15.0-1010-raspi2 #11-Ubuntu SMP PREEMPT Tue Apr 24
06:27:17 UTC 2018 armv7l armv7l armv7l GNU/Linux

bind9 1:9.11.3+dfsg-1ubuntu1.3


apt install bind9
...
Setting up bind9 (1:9.11.3+dfsg-1ubuntu1.3) ...
rndc-confgen: error while loading shared libraries: libdns.so.1100: cannot open 
shared object file: No such file or directory
dpkg: error processing package bind9 (--configure):
...

after
apt install libdns1100

installing bind9 went just fine.

** Affects: bind9 (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/1809056

Title:
  bind9 package needs install libdns1100 - incomplete dependency

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

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

[Bug 1809052] Re: package friendly-recovery 0.2.38ubuntu1 failed to install/upgrade: installed friendly-recovery package post-installation script subprocess returned error exit status 1

[Dimitri John Ledkov]

tail: impossible d'ouvrir '/etc/grub.d/39_custom' en lecture: Aucun fichier ou 
dossier de ce type
tail: impossible d'ouvrir '(copie)' en lecture: Aucun fichier ou dossier de ce 
type


Something is wrong with that file. What is it?!

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

Title:
  package friendly-recovery 0.2.38ubuntu1 failed to install/upgrade:
  installed friendly-recovery package post-installation script
  subprocess returned error exit status 1

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

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

[Bug 1809053] Re: package openssh-server 1:7.6p1-4ubuntu0.1 failed to install/upgrade: installed openssh-server package post-installation script subprocess was killed by signal (Aborted)

[Seth Arnold]

This is sure surprising:

(frontend:26097): Pango-WARNING **: 01:57:45.798: font_face 
status is: out of memory
...
Gtk:ERROR:../../../../gtk/gtkiconhelper.c:494:ensure_surface_for_gicon: 
assertion failed (error == NULL): Failed to load 
/usr/share/icons/Humanity/status/48/image-missing.svg: Error opening file 
/usr/share/icons/Humanity/status/48/image-missing.svg: Too many open files 
(g-io-error-quark, 31)
dpkg: error processing package openssh-server (--configure):
 installed openssh-server package post-installation script subprocess was 
killed by signal (Aborted)

Do you know how the system got "too many open files" as an error
message? that's normally pretty hard to hit.

Thanks

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

Title:
  package openssh-server 1:7.6p1-4ubuntu0.1 failed to install/upgrade:
  installed openssh-server package post-installation script subprocess
  was killed by signal (Aborted)

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

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

[Bug 1778817] Re: release upgrade from xenial to bionic desktop: screen locks itself, password to unlock fails

[Steve Langasek]

It is not invalid; it is a regression vs all previous screen lock
implementations that compiz does pam handling in process instead of in a
helper process, making it vulnerable to this kind of library skew.

** Changed in: compiz (Ubuntu)
   Status: Invalid => Triaged

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

Title:
  release upgrade from xenial to bionic desktop: screen locks itself,
  password to unlock fails

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

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

[Bug 1809054] Re: package libsane1 1.0.27-1~experimental3ubuntu2 [modified: lib/udev/rules.d/60-libsane1.rules] failed to install/upgrade: trying to overwrite shared '/lib/udev/rules.d/60-libsane1.rul

[Ubuntu Foundations Team Bug Bot]

Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware.  I recommend
performing a back up and then investigating the situation.  Measures you
might take include checking cable connections and using software tools
to investigate the health of your hardware.  In the event that is is not
in fact an error with your hardware please set the bug's status back to
New.  Thanks and good luck!

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

** Tags added: hardware-error

** Changed in: sane-backends (Ubuntu)
   Importance: Undecided => Low

** Changed in: sane-backends (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/1809054

Title:
  package libsane1 1.0.27-1~experimental3ubuntu2 [modified:
  lib/udev/rules.d/60-libsane1.rules] failed to install/upgrade: trying
  to overwrite shared '/lib/udev/rules.d/60-libsane1.rules', which is
  different from other instances of package libsane1:i386

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

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

[Bug 1767223] Re: multilib selects wrong start files

[Launchpad Bug Tracker]

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

** Changed in: newlib (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/1767223

Title:
  multilib selects wrong start files

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

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

[Bug 1767223] Re: multilib selects wrong start files

[Launchpad Bug Tracker]

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

** Changed in: newlib (Ubuntu Cosmic)
   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/1767223

Title:
  multilib selects wrong start files

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

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

[Bug 1808493] Re: Let's Encrypt CA Root Certificates missing

[Seth Arnold]

Thanks, I'll mark it "invalid" to take it off our radar again.

** Changed in: ca-certificates (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  Let's Encrypt CA Root Certificates missing

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

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

[Bug 1808908] Re: Screen not locked when coming out of suspend/hibernate

[Seth Arnold]

Hmm, I don't follow the chain of events here.

Ubuntu by default doesn't have a root password; if you've set one,
that's fine, but it's probably a distraction here.

Can you describe what specifically happened?

Thanks

** Information type changed from Private Security to Public Security

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

Title:
  Screen not locked when coming out of suspend/hibernate

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

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

[Bug 1808908] [NEW] Screen not locked when coming out of suspend/hibernate

[Launchpad Bug Tracker]

*** This bug is a security vulnerability ***

You have been subscribed to a public security bug by Seth Arnold (seth-arnold):

Ubuntu 18.04.1

Just a few minutes ago, I typed the first character of my password, and
the lock screen didn't change to the login screen. I typed the character
again and nothing happened, so I pressed the spacebar to try to get the
thing's attention.


Then it unlocked.


This is spooked me, so I restarted my laptop and tried logging in with a random 
string, and nothing happened. I logged in with my regular password and then 
promptly changed it.

I tried unlocking my system with my old password, and it worked.
However, the terminal only recognizes my new root password.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-screensaver (not installed)
ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
Uname: Linux 4.15.0-42-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Dec 17 23:10:46 2018
InstallationDate: Installed on 2018-09-15 (94 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-screensaver
Symptom: security
Title: Screen not locked when coming out of suspend/hibernate
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic
-- 
Screen not locked when coming out of suspend/hibernate
https://bugs.launchpad.net/bugs/1808908
You received this bug notification because you are a member of Ubuntu Bugs, 
which is subscribed to the bug report.

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

[Bug 1804715] Re: package desktop-file-utils 0.22-1ubuntu5.1 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[Launchpad Bug Tracker]

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

** Changed in: desktop-file-utils (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/1804715

Title:
  package desktop-file-utils 0.22-1ubuntu5.1 failed to install/upgrade:
  dependency problems - leaving triggers unprocessed

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

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

[Bug 1767314] Re: Ubuntu Bionic vi/vim not working correctly

[flashydave]

Setting regexpengine=1 drops this back down to 1.4 seconds. So either
this is the root cause of this particular slowdown (i.e. when syntax
highlighting gitolite format files) or at least compensates for whatever
is the root cause.  According to
https://stackoverflow.com/posts/38521226 the default regexp engine
changed with Vim 7.4. This was the version shipped with Trusty onwards
so in theory was already in use on 14.04 and 16.04 ubuntu so something
doesnt quite tie up

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

Title:
  Ubuntu Bionic vi/vim not working correctly

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

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

[Bug 1809054] [NEW] package libsane1 1.0.27-1~experimental3ubuntu2 [modified: lib/udev/rules.d/60-libsane1.rules] failed to install/upgrade: trying to overwrite shared '/lib/udev/rules.d/60-libsane1.r

[Tom Huber]

Public bug reported:

I tried to install wine and this happened.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libsane1 1.0.27-1~experimental3ubuntu2 [modified: 
lib/udev/rules.d/60-libsane1.rules]
ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
Uname: Linux 4.15.0-42-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Tue Dec 18 17:12:18 2018
DuplicateSignature:
 package:libsane1:1.0.27-1~experimental3ubuntu2 [modified: 
lib/udev/rules.d/60-libsane1.rules]
 Unpacking libsane1:i386 (1.0.27-1~experimental3ubuntu2) ...
 dpkg: error processing archive 
/var/cache/apt/archives/libsane1_1.0.27-1~experimental3ubuntu2_i386.deb 
(--unpack):
  trying to overwrite shared '/lib/udev/rules.d/60-libsane1.rules', which is 
different from other instances of package libsane1:i386
ErrorMessage: trying to overwrite shared '/lib/udev/rules.d/60-libsane1.rules', 
which is different from other instances of package libsane1:i386
InstallationDate: Installed on 2018-07-17 (154 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.3ubuntu0.1
SourcePackage: sane-backends
Title: package libsane1 1.0.27-1~experimental3ubuntu2 [modified: 
lib/udev/rules.d/60-libsane1.rules] failed to install/upgrade: trying to 
overwrite shared '/lib/udev/rules.d/60-libsane1.rules', which is different from 
other instances of package libsane1:i386
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: sane-backends (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic need-duplicate-check package-conflict 
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/1809054

Title:
  package libsane1 1.0.27-1~experimental3ubuntu2 [modified:
  lib/udev/rules.d/60-libsane1.rules] failed to install/upgrade: trying
  to overwrite shared '/lib/udev/rules.d/60-libsane1.rules', which is
  different from other instances of package libsane1:i386

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

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

[Bug 1809052] [NEW] package friendly-recovery 0.2.38ubuntu1 failed to install/upgrade: installed friendly-recovery package post-installation script subprocess returned error exit status 1

[yves GUILLON]

Public bug reported:

Maybe double with half an hour ago report

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: friendly-recovery 0.2.38ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
Date: Tue Dec 18 23:23:08 2018
ErrorMessage: installed friendly-recovery package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2018-12-18 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.1
 apt  1.6.6
SourcePackage: friendly-recovery
Title: package friendly-recovery 0.2.38ubuntu1 failed to install/upgrade: 
installed friendly-recovery package post-installation script subprocess 
returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: friendly-recovery (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  package friendly-recovery 0.2.38ubuntu1 failed to install/upgrade:
  installed friendly-recovery package post-installation script
  subprocess returned error exit status 1

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

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

[Bug 1809053] [NEW] package openssh-server 1:7.6p1-4ubuntu0.1 failed to install/upgrade: installed openssh-server package post-installation script subprocess was killed by signal (Aborted)

[David Langolf]

Public bug reported:

doesn't seem to be a major issue.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: openssh-server 1:7.6p1-4ubuntu0.1
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic i686
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: i386
Date: Tue Dec 18 08:31:24 2018
ErrorMessage: installed openssh-server package post-installation script 
subprocess was killed by signal (Aborted)
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.1
 apt  1.6.6
SourcePackage: openssh
Title: package openssh-server 1:7.6p1-4ubuntu0.1 failed to install/upgrade: 
installed openssh-server package post-installation script subprocess was killed 
by signal (Aborted)
UpgradeStatus: Upgraded to bionic on 2018-12-18 (0 days ago)

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


** Tags: apport-package bionic i386

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

Title:
  package openssh-server 1:7.6p1-4ubuntu0.1 failed to install/upgrade:
  installed openssh-server package post-installation script subprocess
  was killed by signal (Aborted)

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

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

[Bug 1809051] [NEW] It don't installed on Dell Inspiron 1545

[Gopal Raha]

Public bug reported:

Ubuntu 18.04 installation won't works on Dell Inspiron 1545

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14.6
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CasperVersion: 1.394
CurrentDesktop: ubuntu:GNOME
Date: Wed Dec 19 04:21:15 2018
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper only-ubiquity 
initrd=/casper/initrd.lz quiet splash ---
LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
ProcEnviron:
 LANGUAGE=en_IN
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IN
 LC_NUMERIC=C.UTF-8
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  It don't installed on Dell Inspiron 1545

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

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

[Bug 1726380] Re: Option “-e” is deprecated and might be removed in a later version of gnome-terminal

[Bug Watch Updater]

** Changed in: gnome-terminal
   Status: Unknown => Confirmed

** Changed in: gnome-terminal
   Importance: Unknown => Medium

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

Title:
  Option “-e” is deprecated and might be removed in a later version of
  gnome-terminal

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

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

[Bug 1809050] [NEW] package grub-pc 2.02-2ubuntu8.9 failed to install/upgrade: installed grub-pc package post-installation script subprocess returned error exit status 1

[yves GUILLON]

Public bug reported:

Original =installation not clean, under emergency activation with
external disks.

Possible initiation of difficulties 6 month ago when passing from ubuntu
14.04 to 16.04 (either overflow of partition, or bad transition from
graphic server  (mixed things between Lubuntu; Xubuntu and Ubuntu.

Initial emergency solution from september , maybe with a 32bits systeme
on secondary hard-drive, but activation of previous /home directory
(probably 64bits).

Manual adjustment of grub.cfg in ordre to get access to xubuntu18.04
(from external amovible backup disk.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: grub-pc 2.02-2ubuntu8.9
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
Date: Tue Dec 18 23:28:35 2018
ErrorMessage: installed grub-pc package post-installation script subprocess 
returned error exit status 1
InstallationDate: Installed on 2018-12-18 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
InvalidGrubScript: /etc/grub.d/39_custom (copie) /etc/grub.d/40_custom
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=0beca069-d781-439a-8538-c4fc07172aaa ro quiet splash
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.1
 apt  1.6.6
SourcePackage: grub2
Title: package grub-pc 2.02-2ubuntu8.9 failed to install/upgrade: installed 
grub-pc package post-installation script subprocess returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

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

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

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

[Bug 1779640] Re: [Hyper-V] KVP daemon crashes at startup

[Dan Watkins]

Yep, I have now done so:

$ ls -la /dev/vmbus/hv_kvp
crw--- 1 root root 10, 55 Dec 18 22:31 /dev/vmbus/hv_kvp

Joe, I've also imported your SSH keys in to ubuntu@test-
slgyvlgaldgcyzqkzuoz.cloudapp.net if there's any other poking around you
want to do.

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

Title:
  [Hyper-V] KVP daemon crashes at startup

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

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

[Bug 1808997] Re: Update to 2.x

[Bug Watch Updater]

** Changed in: wsjtx (Debian)
   Status: Unknown => New

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

Title:
  Update to 2.x

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

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

[Bug 1809048] [NEW] Time

[solomon zerihun]

Public bug reported:

i don't know what happen to it

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libcups2:i386 2.1.3-4ubuntu0.7
ProcVersionSignature: Ubuntu 4.4.0-141.167-generic 4.4.162
Uname: Linux 4.4.0-141-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
Architecture: amd64
CrashReports:
 640:0:116:870147:2018-12-19 00:30:48.274436950 +0200:2018-12-19 
00:30:50.698492338 +0200:/var/crash/udev.0.crash
 644:0:116:0:2018-12-19 00:30:50.698492338 +0200:2018-12-19 00:30:50.698492338 
+0200:/var/crash/udev.0.upload
 640:0:116:957771:2018-12-19 00:31:04.306784391 +0200:2018-12-19 
00:31:05.306784391 +0200:/var/crash/libcups2:amd64.0.crash
 644:0:116:0:2018-12-19 00:31:06.454808614 +0200:2018-12-19 00:31:06.454808614 
+0200:/var/crash/libcups2:amd64.0.upload
 600:0:116:249269:2018-12-19 00:29:57.896657466 +0200:2018-12-19 
00:29:58.896657466 +0200:/var/crash/libcups2:i386.0.crash
CupsErrorLog: W [17/Dec/2018:13:07:11 +0200] Notifier for subscription 2490 
(dbus://) went away, retrying!
Date: Wed Dec 19 00:29:58 2018
ErrorMessage: package libcups2:i386 is already installed and configured
InstallationDate: Installed on 2017-09-17 (457 days ago)
InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
MachineType: LENOVO 80UD
PackageArchitecture: i386
Papersize: a4
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-141-generic.efi.signed 
root=UUID=9831f001-2138-47f7-a22b-f0540653a805 ro quiet splash vt.handoff=7
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-141-generic.efi.signed 
root=UUID=9831f001-2138-47f7-a22b-f0540653a805 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.5
 apt  1.2.29
SourcePackage: dpkg
Title: package libcups2:i386 2.1.3-4ubuntu0.7 failed to install/upgrade: 
package libcups2:i386 is already installed and configured
UpgradeStatus: Upgraded to xenial on 2017-09-26 (448 days ago)
dmi.bios.date: 12/27/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: 1TCN22WW(V2.03)
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: Lenovo ideapad 1
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40679 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 110-15ISK
dmi.modalias: 
dmi:bvnLENOVO:bvr1TCN22WW(V2.03):bd12/27/2016:svnLENOVO:pn80UD:pvrLenovoideapad110-15ISK:rvnLENOVO:rnLenovoideapad1:rvrSDK0J40679WIN:cvnLENOVO:ct10:cvrLenovoideapad110-15ISK:
dmi.product.name: 80UD
dmi.product.version: Lenovo ideapad 110-15ISK
dmi.sys.vendor: LENOVO

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


** Tags: already-installed apport-package i386 need-duplicate-check 
package-from-proposed xenial

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

Title:
  Time

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

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

[Bug 374079] Re: Internal microphone doesn't work at all

[David VANTYGHEM]

As explained in https://elubuntero.wordpress.com/tag/realtek-alc268/ , I
tried to add linux-backports-modules-*** but this package isn't anymore
in Ubuntu and Mint repositories.

I tried all options as explained in https://doc.ubuntu-
fr.org/audio_intel_hda , no result. Please heelp.

** Changed in: alsa-driver (Ubuntu)
   Status: Invalid => Confirmed

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

Title:
  Internal microphone doesn't work at all

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

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

[Bug 374079] Re: Internal microphone doesn't work at all

[David VANTYGHEM]

I have this problem with Ubuntu 18.04, 18.10 and Linux Mint 19, on 2 computers :
HP Pavilion dv6700 and Acer Extensa 5620Z, both with a Realtek ALC268 chipset.
Audio is working but not internal microphone (and on HP Pavilion, external 
microphone doesn't work too).

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

Title:
  Internal microphone doesn't work at all

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

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

[Bug 1767314] Re: Ubuntu Bionic vi/vim not working correctly

[flashydave]

Just by way of more info I was editing a gitolite conf file of 4096 lines with 
the following stats to render the syntax with the cursor at the end of the file
The total time taken was 5 seconds. By default redrawtime is set to 2 seconds 
so the 5 srconds taken represents a considetable drop off in performance.  It 
is true that 18.04 feels sluggish. Maybe Spectre malware fix slowdowns?


TOTAL  COUNT  MATCH   SLOWEST AVERAGE   NAME   PATTERN
  1.580522   4214   96  0.0028750.000375  gitoliteRefex  
\(^\s*\(-\|R\|RW+\?C\?D\?\)\s\+\)\@<=\S.\{-}\(\s*=
  1.542289   4068   27120.0060480.000379  gitoliteConfigKey  
\(\(config\|option\)\s\+\)\@<=[^ =]*
  0.986339   1426   0   0.0327780.000692  gitoliteCreateRule 
\(^\s*C\s.*=\s*\)\@<=\S[^#]*[^# ]
  0.777079   4068   40680.0008700.000191  gitoliteConfigVal  
\(=\s*\)\@<=\S.*
  0.652198   1502   95  0.040.000434  gitoliteDenyRule   
\(^\s*-\s.*=\s*\)\@<=\S[^#]*[^# ]
  0.059132   2852   14260.0001000.21  gitoliteRule   
\(^\s*\)\@<=\(-\|C\|R\|RW+\?C\?D\?\)\s\@=
  0.033258   4118   13560.490.08  gitoliteConfigLine 
^\s*\(config\|option\|include\|subconf\)\s[^#]*
  0.024610   4142   14260.350.06  gitoliteRuleLine   
^\s*\(-\|C\|R\|RW+\?C\?D\?\)\s[^#]*
  0.016784   6026   32580.130.03  gitoliteGroup  @\S\+
  0.014909   4142   13950.130.04  gitoliteRepoError  
^\s*\S\+\s*=
  0.014868   4118   657 0.450.04  gitoliteRepoLine   
^\s*repo\s\+[^=]*$
  0.013410   4118   0   0.440.03  gitoliteRepoError  ^\s*repo.*=
  0.010654   4400   574 0.450.02  gitoliteComment#.*
  0.004946   4118   1   0.140.01  gitoliteGroupLine  
^\s*@\S\+\s*=\s*\S.*$
  0.003386   4118   0   0.090.01  gitoliteTemplateLine ^=begin 
template-data$
  0.001547   4118   0   0.020.00  gitoliteSpecialRefex /USER/
  0.001208   4118   0   0.010.00  gitoliteSpecialRefex NAME/

  5.737139   65666

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

Title:
  Ubuntu Bionic vi/vim not working correctly

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

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

[Bug 1809047] [NEW] Grub-install/dev/sda failed

[Obaid Ur Rehman]

Public bug reported:

At the end of installation grub installation failed

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14.6
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CasperVersion: 1.394
CurrentDesktop: ubuntu:GNOME
Date: Wed Dec 19 03:09:17 2018
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed 
boot=casper only-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
ProcEnviron:
 LANGUAGE=en_US.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 LC_NUMERIC=C.UTF-8
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.6 ubuntu

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

Title:
  Grub-install/dev/sda failed

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

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

[Bug 1765304] Re: Ubuntu 18.04's ibus package breaks password fields in Firefox (by lowering & raising window whenever they're focused)

[Brian Murray]

Hello Daniel, or anyone else affected,

Accepted gnome-shell into cosmic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/gnome-
shell/3.30.1-2ubuntu1.18.10.2 in a few hours, and then in the -proposed
repository.

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

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

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

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

** Changed in: gnome-shell (Ubuntu Cosmic)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-cosmic

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

Title:
  Ubuntu 18.04's ibus package breaks password fields in Firefox (by
  lowering & raising window whenever they're focused)

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

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

[Bug 1779640] Re: [Hyper-V] KVP daemon crashes at startup

[Joseph Salisbury]

Do you have a way to pause a test, so you can access the instance?  It
would be good to know if the file actually exists:

ls -l /dev/vmbus/hv_kvp

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

Title:
  [Hyper-V] KVP daemon crashes at startup

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

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

[Bug 1809046] [NEW] Cannot initialize ATA disk if IDENTIFY command fails

[dann frazier]

Public bug reported:

[Impact]
ATA disks attached to a SAS controller may not initialize if the initial 
IDENTIFY command fails.

[Test Case]
The positive test case would require a disk that fails to respond correctly to 
an IDENTIFY command. I don't have one of those, so can only regression test on 
a system w/ SAS connected disks.

[Fix]
437207d3697f5 scsi: libsas: check the ata device status by ata_dev_enabled()

[Regression Risk]
Clean cherry pick from upstream - any regressions will have upstream support.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: dann frazier (dannf)
 Status: In Progress

** Affects: linux (Ubuntu Bionic)
 Importance: Undecided
 Assignee: dann frazier (dannf)
 Status: In Progress

** Affects: linux (Ubuntu Cosmic)
 Importance: Undecided
 Assignee: dann frazier (dannf)
 Status: In Progress

** Affects: linux (Ubuntu Disco)
 Importance: Undecided
 Assignee: dann frazier (dannf)
 Status: In Progress

** Also affects: linux (Ubuntu Disco)
   Importance: Undecided
 Assignee: dann frazier (dannf)
   Status: In Progress

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

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

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

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

** Changed in: linux (Ubuntu Bionic)
 Assignee: (unassigned) => dann frazier (dannf)

** Changed in: linux (Ubuntu Cosmic)
 Assignee: (unassigned) => dann frazier (dannf)

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

Title:
  Cannot initialize ATA disk if IDENTIFY command fails

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

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

[Bug 1809045] [NEW] Dash - "See more results" shortcut doesn't lead to more results

[Eduardo Santos]

Public bug reported:

Ubuntu 18.04.1

Description / How to reproduce:

- Open the dash, search for any word you know that should bring multiple
file results. Now imagine that you wanted to check the full results and
not only the few that the dash shows, so you click in "Files" icon, in
the left side, which is a kind of shortcut to the full list of the
results for your search.

3) What you expected to happen
This should open a new window with all the results of your search. 

4) What happened instead
It does open a window but no results are shown, and no matter what you search, 
it will bring no results in that window.
However, if you close that window and open any folder to search, it will work 
just fine. It just doesn't work if you use the "shortcut" from the dash.

** Affects: unity (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/1809045

Title:
  Dash - "See more results" shortcut doesn't lead to more results

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

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

[Bug 1767314] Re: Ubuntu Bionic vi/vim not working correctly

[flashydave]

Further investigation with a recompiled version more recent than that
shipped with 18.04 yields that syntax highlighting failure is caused by
redrawtime being exceeded  - often triggered after using G to move to
the end of the file. It is not possible to set "syntax on" manually at
that point as it immediatetly gets disabled again unless you move to the
start of the file with g.

This explains the "persistence" due to the "jump to the previously
edited line in the file" setting being set - but forgetting it upon
deletion of .viminfo as this is where this Info is stored.  Without it
vi opens with the cursor at line 1.

In my case this problem has occurred following an upgrade and has never
happened before on the same hardware running the same applications for
many years with lots of files being edited multiple times every day -
day in day out.  Ie something in the timing dynamics when running vi has
changed wirh 18.04

See https://github.com/vim/vim/issues/2790 for further discussion and
possible workarounds.

** Bug watch added: github.com/vim/vim/issues #2790
   https://github.com/vim/vim/issues/2790

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

Title:
  Ubuntu Bionic vi/vim not working correctly

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

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

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

[Launchpad Bug Tracker]

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

** Changed in: grub2 (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/1795818

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

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

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

[Bug 1571403] Re: lz4 fails to run the tests on s390x (glibc-2.23 related?)

[Adam Conrad]

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

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

Title:
  lz4 fails to run the tests on s390x (glibc-2.23 related?)

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

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

[Bug 1700239] Re: Fritzing executable should be named in lowercase (i.e. fritzing)

[Juhani Numminen]

Lower-case fritzing command seems to be available since bionic at least.

https://packages.ubuntu.com/bionic/amd64/fritzing/filelist
https://packages.ubuntu.com/cosmic/amd64/fritzing/filelist
https://packages.ubuntu.com/disco/amd64/fritzing/filelist

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

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

Title:
  Fritzing executable should be named in lowercase (i.e. fritzing)

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

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

[Bug 1809004] Re: update disco to latest smartmontools

[Jeff Lane]

After further chat with the person who was reporting this, I think
there's something else going on, the tester did validate that 6.6 works.
And I'm on holiday after today and won't get back to this unitl January.
I'll follow up then once I have more concrete info.

** Changed in: smartmontools (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/1809004

Title:
  update disco to latest smartmontools

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

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

[Bug 1744079] Re: [SRU] disk over-commit still not correctly calculated during live migration

[Launchpad Bug Tracker]

This bug was fixed in the package nova - 2:17.0.7-0ubuntu1

---
nova (2:17.0.7-0ubuntu1) bionic; urgency=medium

  * d/p/disk-size-live-migration-overcommit.patch: Cherry-picked from
https://review.openstack.org/#/c/602478 to ensure proper disk calculation
during live migration with over-commit (LP: #1744079).
  * New stable point release for OpenStack Queens (LP: #1806043).

 -- Corey Bryant   Fri, 07 Dec 2018 08:27:02
-0500

** Changed in: nova (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  [SRU] disk over-commit still not correctly calculated during live
  migration

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

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

[Bug 1806043] Re: [SRU] queens stable releases

[Launchpad Bug Tracker]

This bug was fixed in the package nova - 2:17.0.7-0ubuntu1

---
nova (2:17.0.7-0ubuntu1) bionic; urgency=medium

  * d/p/disk-size-live-migration-overcommit.patch: Cherry-picked from
https://review.openstack.org/#/c/602478 to ensure proper disk calculation
during live migration with over-commit (LP: #1744079).
  * New stable point release for OpenStack Queens (LP: #1806043).

 -- Corey Bryant   Fri, 07 Dec 2018 08:27:02
-0500

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

Title:
  [SRU] queens stable releases

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

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

[Bug 1809014] Re: mpeg-2 detected as tga (Targa image)

[Juhani Numminen]

** Tags added: cosmic

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

Title:
  mpeg-2 detected as tga (Targa image)

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

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

[Bug 1806043] Re: [SRU] queens stable releases

[Launchpad Bug Tracker]

This bug was fixed in the package neutron-fwaas - 1:12.0.1-0ubuntu1

---
neutron-fwaas (1:12.0.1-0ubuntu1) bionic; urgency=medium

  * d/gbp.conf: Create stable/queens branch.
  * New stable point release for OpenStack Queens (LP: #1806043).

 -- Corey Bryant   Mon, 03 Dec 2018 09:15:45
-0500

** Changed in: keystone (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  [SRU] queens stable releases

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

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

[Bug 1806043] Re: [SRU] queens stable releases

[Launchpad Bug Tracker]

This bug was fixed in the package gnocchi - 4.2.5-0ubuntu1

---
gnocchi (4.2.5-0ubuntu1) bionic; urgency=medium

  * New stable point release for OpenStack Queens (LP: #1806043).

 -- Corey Bryant   Mon, 03 Dec 2018 09:15:05
-0500

** Changed in: gnocchi (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

** Changed in: neutron-fwaas (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  [SRU] queens stable releases

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

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