[Bug 1808567] [NEW] modules do not have retpoline modinfo

2018-12-14 Thread Thadeu Lima de Souza Cascardo
Public bug reported:

Even though they are built with CONFIG_RETPOLINE, modpost won't
correctly insert the MODULE_INFO after CONFIG_RETPOLINE was made
dependent on compiler support.

** Affects: linux (Ubuntu)
 Importance: Undecided
 Assignee: Thadeu Lima de Souza Cascardo (cascardo)
 Status: In Progress

** Affects: linux (Ubuntu Disco)
 Importance: Undecided
 Assignee: Thadeu Lima de Souza Cascardo (cascardo)
 Status: In Progress

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

Title:
  modules do not have retpoline modinfo

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

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

[Bug 1297790] Re: "Unknown audio device" dialog pops up every time I plug in headphones

2018-12-14 Thread tom
Praise jesus. They finally fixed this bug.

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

Title:
  "Unknown audio device" dialog pops up every time I plug in headphones

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

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

[Bug 1641928] Re: "Unknown audio device" dialog pops up every time I plug in headphones

2018-12-14 Thread tom
Finally fixed.

** Changed in: alsa-driver (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/1641928

Title:
  "Unknown audio device" dialog pops up every time I plug in headphones

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

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

[Bug 1602834] Re: obsolete conffiles not cleaned up on upgrade

2018-12-14 Thread Jamie Strandboge
** Changed in: ufw (Ubuntu Disco)
   Status: Triaged => In Progress

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

Title:
  obsolete conffiles not cleaned up on upgrade

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

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

[Bug 1778844] Re: nvme multipath does not report path relationships

2018-12-14 Thread Thadeu Lima de Souza Cascardo
https://lore.kernel.org/linux-block/20181213113549.GA7543@calabresa/T/#t

Upstream discussion in progress.

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

Title:
  nvme multipath does not report path relationships

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

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

[Bug 1808168] Please test proposed package

2018-12-14 Thread Łukasz Zemczak
Hello Lorenzo, or anyone else affected,

Accepted neutron-fwaas-dashboard into bionic-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/neutron-fwaas-dashboard/1.3.0-0ubuntu1 in a few hours, and then in the
-proposed repository.

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

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

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

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

** Also affects: neutron-fwaas-dashboard (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: neutron-fwaas-dashboard (Ubuntu Cosmic)
   Status: New => Invalid

** Changed in: neutron-fwaas-dashboard (Ubuntu Disco)
   Status: New => Invalid

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

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

Title:
  Neutron FWaaS panel missing from dashboard on Queens

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-openstack-dashboard/+bug/1808168/+subscriptions

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

[Bug 1808168] Re: Neutron FWaaS panel missing from dashboard on Queens

2018-12-14 Thread Łukasz Zemczak
Ok, looks good I think, let me approve it. A note to other archive-
admins/SRU members: there are some differences in packaging from the
cosmic 1.3.0 upload, but most of them are either related to py3->py2 or
are actually present in the cosmic+ 1.5.0 versions.

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

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

Title:
  Neutron FWaaS panel missing from dashboard on Queens

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-openstack-dashboard/+bug/1808168/+subscriptions

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

[Bug 1807982] Re: linux-oracle: 4.15.0-1007.9~16.04.1 -proposed tracker

2018-12-14 Thread Brad Figg
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => Fix Committed

** Description changed:

  This bug is for tracking the 4.15.0-1007.7~16.04.1 upload package. This
  bug will contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Uploaded
  phase-changed: Wednesday, 12. December 2018 20:11 UTC
  reason:
-   promote-to-proposed: Ready for review
+   promote-to-proposed: Packages copied but not yet published to -proposed

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

Title:
  linux-oracle: 4.15.0-1007.9~16.04.1 -proposed tracker

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

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

[Bug 1804287] Re: vgauth needs to start before vmtoolsd

2018-12-14 Thread Launchpad Bug Tracker
This bug was fixed in the package open-vm-tools - 2:10.3.5-3

---
open-vm-tools (2:10.3.5-3) unstable; urgency=medium

  [ Christian Ehrhardt ]
  * [d3d4703] Start vgauth before vmtoolsd.
VGAuthService needs to be ready when vmtoolsd runs. Certain cases - e.g.
Site Recovery Manager failover - will need vgauth to be up.
Therefore add an After=vgauth.service dependency to open-vm-tools.service
To have vgauth be able start early - and not pull cloud-init back late - it
is also required to drop default dependencies which according to VMware is
fine to do so.
(LP: #1804287)

 -- Bernd Zeimetz   Fri, 14 Dec 2018 09:55:04 +0100

** Changed in: open-vm-tools (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  vgauth needs to start before vmtoolsd

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

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

[Bug 211098] Re: Gateway EV910 "gwy232a" generates bad EDID

2018-12-14 Thread Bug Watch Updater
** Changed in: xorg-server
   Status: Confirmed => Unknown

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

Title:
  Gateway EV910 "gwy232a" generates bad EDID

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

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

[Bug 211098]

2018-12-14 Thread Gitlab-migration
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.

You can subscribe and participate further through the new bug through
this link to our GitLab instance:
https://gitlab.freedesktop.org/xorg/xserver/issues/365.

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

Title:
  Gateway EV910 "gwy232a" generates bad EDID

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

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

[Bug 1795342] Re: High Power Consumption

2018-12-14 Thread Irfan
Disabled snapd service and left the laptop idle, almost same power
usage.

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

Title:
  High Power Consumption

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

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

[Bug 1782984] Re: PCManFM crashes frequently on Lubuntu 18.04

2018-12-14 Thread Janos Verebes
Dear MarkF,

I used GIMP 2.10 from kesselgulasch's PPA since I experienced continuous crash 
of 2.8 installed normally from lubuntu packages. Absolutely no crash since 
then, but I could not find any connection between PcManFM 1.2.5 crash and GIMP 
crash. There are no shared packages between the two softwares. PcManFM 1.2.5 
was doing its crash as usual. Only then I upgraded PcManFm to 1.3.0 with LibFM 
1.2.5 and crashes became quite rare. BUT! The freezing is there!
The problem seemingly does not come from PcManFm, but I have not tried it under 
MATE or GNOME desktops. This could give the correct answer to the source of the 
problem. But since I tried Thunar file manager with Lubuntu and it also did the 
freezing emerged the question of not blaming PcManFM but Lubuntu.

Regards,
Janos

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

Title:
  PCManFM crashes frequently  on Lubuntu 18.04

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

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

[Bug 1807702] Re: linux-oracle: 4.15.0-1007.9 -proposed tracker

2018-12-14 Thread Brad Figg
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: In Progress => Fix Committed

** Description changed:

  This bug is for tracking the 4.15.0-1007.7 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Uploaded
  phase-changed: Wednesday, 12. December 2018 19:38 UTC
  reason:
-   promote-to-proposed: Review in progress
+   promote-to-proposed: Packages copied but not yet published to -proposed

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

Title:
  linux-oracle: 4.15.0-1007.9 -proposed tracker

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

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

[Bug 1808383] Re: Java 9+ multi-release jars are not supported in ant tasks

2018-12-14 Thread Tiago Stürmer Daitx
** Also affects: ant (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: ant (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: ant (Ubuntu Disco)
   Importance: Undecided
   Status: Confirmed

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

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

Title:
  Java 9+ multi-release jars are not supported in ant tasks

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

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

[Bug 1409872] Re: avahi-0.6.31 doesn't pass Apple conformance test

2018-12-14 Thread Stefano Cappa
The same for avahi 0.7 also with bonjour conformance test 1.4.0

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

Title:
  avahi-0.6.31 doesn't pass Apple conformance test

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

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

[Bug 1778362] Re: thymiovpl and asebastudio are missing from aseba package

2018-12-14 Thread piscvau via ubuntu-bugs
Hello
We tried to install the building script on a Xubuntu Bionics system. It does 
not work. bleow is the error code :
-- Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE)
Using dashel from 
/home/christian/Documents/thymio/build_Aseba_Debian/aseba-master/dashel
CMake Warning at enki/CMakeLists.txt:10 (find_package):
  By not providing "FindQt5.cmake" in CMAKE_MODULE_PATH this project has
  asked CMake to find a package configuration file provided by "Qt5", but
  CMake did not find one.

  Could not find a package configuration file provided by "Qt5" with any of
  the following names:

Qt5Config.cmake
qt5-config.cmake

  Add the installation prefix of "Qt5" to CMAKE_PREFIX_PATH or set "Qt5_DIR"
  to a directory containing one of the above files.  If "Qt5" provides a
  separate development package or SDK, be sure it has been installed.


CMake Error at 
/usr/share/cmake-3.10/Modules/FindPackageHandleStandardArgs.cmake:137 (message):
  Could NOT find OpenGL (missing: OPENGL_opengl_LIBRARY OPENGL_glx_LIBRARY
  OPENGL_INCLUDE_DIR)
Call Stack (most recent call first):
/usr/share/cmake-3.10/Modules/FindPackageHandleStandardArgs.cmake:378 
(_FPHSA_FAILURE_MESSAGE)
  /usr/share/cmake-3.10/Modules/FindOpenGL.cmake:369 
(FIND_PACKAGE_HANDLE_STANDARD_ARGS)
  enki/CMakeLists.txt:11 (find_package)


-- Configuring incomplete, errors occurred!
See also 
"/home/christian/Documents/thymio/build_Aseba_Debian/aseba-master/build/CMakeFiles/CMakeOutput.log".
make: *** Pas de cible spécifiée et aucun makefile n'a été trouvé. Arrêt.

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

Title:
  thymiovpl and asebastudio are missing from aseba package

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

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

[Bug 1808562] Re: package libc6-i386 2.27-3ubuntu1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2

2018-12-14 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package libc6-i386 2.27-3ubuntu1 failed to install/upgrade: dpkg-deb
  --fsys-tarfile subprocess returned error exit status 2

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

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

[Bug 1808193] ProcCpuinfoMinimal.txt

2018-12-14 Thread Irfan
apport information

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

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

Title:
  Battery percentage changes suddenly depending on whether AC is plugged
  in

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

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

[Bug 1808193] Re: Battery percentage changes suddenly depending on whether AC is plugged in

2018-12-14 Thread Irfan
apport information

** Description changed:

  The battery indicator in my Ubuntu 18.10 installed on Thinkpad shows 100% 
(Fully charged when plugged in) but when plugged out the battery shows 94%. 
Batteries are fine, no issues whatsoever with batteries.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-12-10 (3 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Package: gnome-shell 3.30.1-2ubuntu1.18.10.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
  Tags:  cosmic
  Uname: Linux 4.18.0-12-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.10-0ubuntu13.1
+ Architecture: amd64
+ CurrentDesktop: ubuntu:GNOME
+ DisplayManager: gdm3
+ DistroRelease: Ubuntu 18.10
+ InstallationDate: Installed on 2018-12-10 (4 days ago)
+ InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
+ Package: upower
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17
+ Tags:  cosmic
+ Uname: Linux 4.18.0-12-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

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

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

Title:
  Battery percentage changes suddenly depending on whether AC is plugged
  in

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

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

[Bug 1808193] GsettingsChanges.txt

2018-12-14 Thread Irfan
apport information

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

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

Title:
  Battery percentage changes suddenly depending on whether AC is plugged
  in

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

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

[Bug 1788549] Re: powerpc/powernv/pci: Work around races in PCI bridge enabling

2018-12-14 Thread Joseph Salisbury
@Mike, do you feel comfortable with the testing you've done to submit an
SRU request?  Or would you like to perform some additional testing?

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

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

Title:
  powerpc/powernv/pci: Work around races in PCI bridge enabling

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

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

[Bug 1808193] ProcEnviron.txt

2018-12-14 Thread Irfan
apport information

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

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

Title:
  Battery percentage changes suddenly depending on whether AC is plugged
  in

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

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

[Bug 1808562] [NEW] package libc6-i386 2.27-3ubuntu1 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2

2018-12-14 Thread Petar Mandic
Public bug reported:

it happened after unsuccessful uograde from 18.04 to 18.10 and restart

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libc6-i386 2.27-3ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
Uname: Linux 4.15.0-42-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
Date: Fri Dec 14 18:00:13 2018
Dependencies:
 gcc-8-base 8.2.0-1ubuntu2~18.04
 libc6 2.28-0ubuntu1
 libgcc1 1:8.2.0-1ubuntu2~18.04
 libidn2-0 2.0.4-1.1build2
 libunistring2 0.9.9-0ubuntu1
DuplicateSignature:
 package:libc6-i386:2.27-3ubuntu1
 Replaced by files in installed package libc6:i386 (2.28-0ubuntu1) ...
 dpkg: error processing archive 
/var/cache/apt/archives/libc6-i386_2.28-0ubuntu1_amd64.deb (--unpack):
  dpkg-deb --fsys-tarfile subprocess returned error exit status 2
ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
InstallationDate: Installed on 2018-08-10 (125 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
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: glibc
Title: package libc6-i386 2.27-3ubuntu1 failed to install/upgrade: dpkg-deb 
--fsys-tarfile subprocess returned error exit status 2
UpgradeStatus: Upgraded to bionic on 2018-12-14 (0 days ago)

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


** Tags: amd64 apport-package bionic

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

Title:
  package libc6-i386 2.27-3ubuntu1 failed to install/upgrade: dpkg-deb
  --fsys-tarfile subprocess returned error exit status 2

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

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

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

2018-12-14 Thread Anisur Rahman
Can you send me a video tutorial for this bug

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

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

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

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

[Bug 1805079] Re: click/pop noise in the headphone on several lenovo laptops

2018-12-14 Thread Vadim Vygonets
Hi Hui Wang,

While waiting for your patch to reach the mainline, I just insert these
two lines myself.

However, I still have issues with the sound.

Scenario: laptop is off, headphones are inserted, sound (both mic and
output) is muted; I turn it on, log in etc., unmute the output and play
something.

The sound is often too quiet (maybe 10 to 15 dB weaker than expected).
If I unplug the headphones and plug them back in, the sound level rises
to expected levels, but I start hearing noise reminiscent of cheap
soundcards (with grounding problems?), where the noise characteristics
change with the activity of other devices (e.g., mouse movements).  The
noise is stronger if I touch the touchpad.  If I mute the sound, the
noise disappears.

This does not happen if I remove the "0x12" line, whether or not I add
the .chained/.chain_id lines.  Interestingly, init_pin_configs in sysfs
shows the same value for 0x12:

$ cat /sys/class/sound/hwC0D0/init_pin_configs 
0x12 0x90a60130
0x13 0x4000
0x14 0x90170110
0x16 0x41f0
0x17 0x41f0
0x18 0x41f0
0x19 0x04a11040
0x1a 0x41f0
0x1b 0x41f0
0x1d 0x4061
0x1e 0x41f0
0x21 0x04211020

(driver_pin_configs and user_pin_configs are empty.)

Thank you,
Vadim.

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

Title:
  click/pop noise in the headphone on several lenovo laptops

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

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

[Bug 1808561] [NEW] dual boot installation, win10 not recognized, partition manually created, install failed during GRUB installation

2018-12-14 Thread Isaias Ullmann Thoen
Public bug reported:

Isa_thoen

system fail during grub installation on a computer with win10.
linux didn't found win10 as an OS previously installed.
I created manually two partitions to install lubuntu (/ and /home as ext4)

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.14
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
Architecture: amd64
CasperVersion: 1.394
Date: Fri Dec 14 14:54:40 2018
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/lubuntu.seed 
boot=casper only-ubiquity 
iso-scan/filename=/WinUSB/CFD7F09C-BFAE-4272-9515-89C5DB2B344F/lubuntu_18.04_desktop_amd64.iso
 quiet splash ---
LiveMediaBuild: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
 LANGUAGE=pt_BR.UTF-8
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=pt_BR.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 lubuntu ubiquity-18.04.14

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

Title:
  dual boot installation, win10 not recognized, partition manually
  created, install failed during GRUB installation

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

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

[Bug 1805802] Re: [UBUNTU] qeth: fix length check in SNMP processing

2018-12-14 Thread Joseph Salisbury
SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-December/097304.html

** Description changed:

- Description:  qeth: fix length check in SNMP processing
- Symptom:  Undefined behaviour.
- Problem:  The response for a SNMP request can consist of multiple parts,
+ == SRU Justification ==
+ The response for a SNMP request can consist of multiple parts,
which the cmd callback stages into a kernel buffer until all
parts have been received. If the callback detects that the
staging buffer provides insufficient space, it bails out with
error.
This processing is buggy for the first part of the response -
while it initially checks for a length of 'data_len', it later
copies an additional amount of
'offsetof(struct qeth_snmp_cmd, data)' bytes.
+ 
+ 
+ == Fix ==
+ 9a764c1e5968 ("s390/qeth: fix length check in SNMP processing")
+ 
+ == Regression Potential ==
+ Low.  Changes limited to s390.
+ 
+ == Test Case ==
+ A test kernel was built with this patch and tested by the original bug 
reporter.
+ The bug reporter states the test kernel resolved the bug.
+ 
+ 
+ 
+ == Original bug description ==
+ 
+ Description:  qeth: fix length check in SNMP processing
+ Symptom:  Undefined behaviour.
+ Problem:  The response for a SNMP request can consist of multiple parts,
+   which the cmd callback stages into a kernel buffer until all
+   parts have been received. If the callback detects that the
+   staging buffer provides insufficient space, it bails out with
+   error.
+   This processing is buggy for the first part of the response -
+   while it initially checks for a length of 'data_len', it later
+   copies an additional amount of
+   'offsetof(struct qeth_snmp_cmd, data)' bytes.
  Solution: Fix the calculation of 'data_len' for the first part of the
-   response.
+   response.
  Upstream-ID:  9a764c1e59684c0358e16ccaafd870629f2cfe67
  
  Should be applied to all Ubuntu Releases in Service

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

Title:
  [UBUNTU] qeth: fix length check in SNMP processing

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

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

[Bug 1804018] Re: Autogenerated interface name prevents creating a bridge over a VLAN

2018-12-14 Thread Dan Streetman
** Changed in: vlan (Ubuntu Cosmic)
   Status: New => In Progress

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

** Changed in: vlan (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: vlan (Ubuntu Trusty)
   Status: New => In Progress

** Changed in: vlan (Ubuntu Cosmic)
   Importance: Undecided => Medium

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

** Changed in: vlan (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: vlan (Ubuntu Trusty)
   Importance: Undecided => Medium

** Changed in: vlan (Ubuntu Cosmic)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: vlan (Ubuntu Bionic)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: vlan (Ubuntu Xenial)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: vlan (Ubuntu Trusty)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

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

Title:
  Autogenerated interface name prevents creating a bridge over a VLAN

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

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

[Bug 1805414] Re: [Ubuntu] kernel: zcrypt: reinit ap queue state machine

2018-12-14 Thread Joseph Salisbury
SRU request submitted:
https://lists.ubuntu.com/archives/kernel-team/2018-December/097301.html

** Description changed:

- Description:  kernel: zcrypt: reinit ap queue state machine
- 
- Symptom:  Zcrypt ap queue device not operational at host level after a
-   kvm guest used it.
- 
- Problem:  The vfio device driver when receiving an ap queue device does
+ == SRU Justification ==
+ The vfio device driver when receiving an ap queue device does
additional resets thereby removing the registration for
-   interrupts for  the ap device done by the ap bus core
+   interrupts for the ap device done by the ap bus core
code. So when later the vfio driver releases the device and
one of the default zcrypt drivers takes care of the device
the interrupt registration needs to get renewed. The current
code does no renew and result is that requests send into such
a queue will never see a reply processed - the application
hangs.
  
+ This commit has also been cc'd to upstream stable.
+ 
+ == Fix ==
+ 104f708fd ("s390/zcrypt: reinit ap queue state machine during device probe")
+ 
+ == Regression Potential ==
+ Low.  Limited to s390.
+ 
+ 
+ == Original Bug Description ==
+ Description:  kernel: zcrypt: reinit ap queue state machine
+ 
+ Symptom:  Zcrypt ap queue device not operational at host level after a
+   kvm guest used it.
+ 
+ Problem:  The vfio device driver when receiving an ap queue device does
+   additional resets thereby removing the registration for
+   interrupts for  the ap device done by the ap bus core
+   code. So when later the vfio driver releases the device and
+   one of the default zcrypt drivers takes care of the device
+   the interrupt registration needs to get renewed. The current
+   code does no renew and result is that requests send into such
+   a queue will never see a reply processed - the application
+   hangs.
+ 
  Solution: This patch adds a function which resets the aq queue state
-   machine for the ap queue device and triggers the walk through
-   the initial states (which are reset and registration for
-   interrupts). This function is now called before the driver's
-   probe function is invoked.
-   When the association between driver and device is released,
-   the driver's remove function is called. The current
-   implementation calls a ap queue function
-   ap_queue_remove(). This invokation has been moved to the ap
-   bus function to make the probe / remove pair for ap bus and
-   drivers more symmetric.
+   machine for the ap queue device and triggers the walk through
+   the initial states (which are reset and registration for
+   interrupts). This function is now called before the driver's
+   probe function is invoked.
+   When the association between driver and device is released,
+   the driver's remove function is called. The current
+   implementation calls a ap queue function
+   ap_queue_remove(). This invokation has been moved to the ap
+   bus function to make the probe / remove pair for ap bus and
+   drivers more symmetric.
  
  Reproduction: Set up an kvm guest to use one or more ap queues in
-   pass-through mode. Start the guest. Stop the guest. Reassign
-   the ap resources back to the host system. Run an application
-   which uses exactly this ap resources. Without the fix, the
-   application hangs; with the fix the application should run
-   fine.
+   pass-through mode. Start the guest. Stop the guest. Reassign
+   the ap resources back to the host system. Run an application
+   which uses exactly this ap resources. Without the fix, the
+   application hangs; with the fix the application should run
+   fine.
  
- Upstream commit(s): 
+ Upstream commit(s):
  104f708fd1241b22f808bdf066ab67dc5a051de5
  Available on kernel.org

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

Title:
  [Ubuntu] kernel: zcrypt: reinit ap queue state machine

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

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

[Bug 1808558] [NEW] Unable to upgrade from Ubuntu 16.04LTS to 18.04LTS

2018-12-14 Thread fieryhydra
Public bug reported:

After an update of some packages by the package manager (GUI mode), an
available upgrade to 18.04LTS was displayed in a new window. I clicked
"OK" for the upgrade, but ultimately the upgrade didn't happen.

I wasn't really planning on upgrading, but since the dialog window
showed that I could upgrade, I went along with it. Of course, in the
end, the upgrade failed.

Thanks.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-release-upgrader-core 1:16.04.26
ProcVersionSignature: Ubuntu 4.15.0-42.45~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-42-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CrashDB: ubuntu
CurrentDesktop: Unity
Date: Fri Dec 14 09:42:09 2018
InstallationDate: Installed on 2018-01-01 (347 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to xenial on 2018-12-14 (0 days ago)
VarLogDistupgradeTermlog:
 
mtime.conffile..etc.update-manager.release-upgrades: 2018-09-09T06:31:53.089990

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


** Tags: amd64 apport-bug dist-upgrade third-party-packages xenial

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

Title:
  Unable to upgrade from Ubuntu 16.04LTS to 18.04LTS

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

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

[Bug 1808557] Re: package libnm-glib-vpn1:i386 1.2.6-0ubuntu0.16.04.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

2018-12-14 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package libnm-glib-vpn1:i386 1.2.6-0ubuntu0.16.04.3 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/network-manager/+bug/1808557/+subscriptions

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

[Bug 1808557] [NEW] package libnm-glib-vpn1:i386 1.2.6-0ubuntu0.16.04.3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

2018-12-14 Thread Leo Germeys
Public bug reported:

the installing gui 'Ubuntu Software' is repeatedly outphased in X revealing 
instability somewhere. Ubuntu 16.04.5 LTS is the output from lsb_release -rd. 
As a result I had to restart installation for updates several times.
Such disfunctioning occured a number of times before with the gui, so I was 
using apt instead, but as it was stated that the gui would be improved, I gave 
it a try.
It showed a large number of errors. Moreover it does not show any progress of 
what is going on during install of updates.  
In the small window it was stated that libnm-glib-vpn1:i386 would be in total 
bad shape so it should be removed and reinstalled. This is now done. But that 
seems only the result of  an instability occuring lately quite often with 
Ubuntu, starting with some larger uodate a couple of months ago. 
I know this is not a very precise description. I will now clean up the system 
starting with verifying all packages. The instability will probably remain 
though. 
In the process the gui was also updated and seems now to be functioning, so the 
version is now 
ubuntu-software 3.20.5-0ubuntu0 i386 . 
There are similar issues of being outphased  with libreoffice, evince and 
probably some more which we seldom use.
The common link between these errors is that contact with X is temporarily lost 
while free memory is low.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libnm-glib-vpn1:i386 1.2.6-0ubuntu0.16.04.3
ProcVersionSignature: Ubuntu 4.4.0-140.166-generic 4.4.162
Uname: Linux 4.4.0-140-generic i686
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: i386
Date: Fri Dec 14 15:49:36 2018
DuplicateSignature:
 package:libnm-glib-vpn1:i386:1.2.6-0ubuntu0.16.04.3
 Processing triggers for hicolor-icon-theme (0.15-0ubuntu1.1) ...
 dpkg: error processing package libnm-glib-vpn1:i386 (--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
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2017-08-25 (476 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2)
IpRoute:
 default via 192.168.0.1 dev wlan0  proto static  metric 600 
 169.254.0.0/16 dev wlan0  scope link  metric 1000 
 192.168.0.0/24 dev wlan0  proto kernel  scope link  src 192.168.0.103  metric 
600
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
 WimaxEnabled=true
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.5
 apt  1.2.29
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
SourcePackage: network-manager
Title: package libnm-glib-vpn1:i386 1.2.6-0ubuntu0.16.04.3 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
UpgradeStatus: Upgraded to xenial on 2017-08-25 (476 days ago)
nmcli-dev:
 DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
 wlan0   wifi  connected/org/freedesktop/NetworkManager/Devices/2  
dlink-5C98  af76c1cc-4c5d-4991-af25-a2fdfd7a5b5c  
/org/freedesktop/NetworkManager/ActiveConnection/0 
 eth0ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  --   
   ---- 

 lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/0  --   
   ----
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.2.6connected  started  full  enabled enabled  
enabled  enabled  enabled

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 xenial

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

Title:
  package libnm-glib-vpn1:i386 1.2.6-0ubuntu0.16.04.3 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/network-manager/+bug/1808557/+subscriptions

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

[Bug 996552] Re: file roller does not open files with odt ending

2018-12-14 Thread Tim Wahrendorff
Still present in 18.04.

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

Title:
  file roller does not open files with odt ending

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

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

[Bug 1787729] Re: [FAILED] Failed to start Process error reports when automatic reporting is enabled.

2018-12-14 Thread Cristian Aravena Romero
Hello Brian Murray (brian-murray),

Will this change come in the next version?

Best regards,
--
Cristian Aravena Romero (caravena)

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

Title:
  [FAILED] Failed to start Process error reports when automatic
  reporting is enabled.

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

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

[Bug 1804018] Re: Autogenerated interface name prevents creating a bridge over a VLAN

2018-12-14 Thread Dan Streetman
hi, here are some clarifications on this bug:

> https://salsa.debian.org/debian/vlan/blob/debian/debian/network/if-pre-up.d/vlan#L21
> https://salsa.debian.org/debian/vlan/commit/7517228145310a29b7cb7f4bddccb1b70df347eb

these have nothing to do with this bug.  those changes are in case
sections that don't match the naming of your interface - yours starts
with "br-*" while those changes are in sections that only match actual
interface naming (i.e., not starting with "br-").

Additionally, I'm pretty sure that check was incorrectly written and has
never worked the way they thought it was working - i.e. it should check
for -n "$IF_BRIDGE_PORTS", but it doesn't, it checks for -z, so it
*won't* exit when called for a device that includes a 'bridge_ports'
param - it will exit for a normally-named interface with vlan extension
*without* vlan-raw-device or bridge_ports defined, which may be why it
was removed from ubuntu long ago (looks like it was re-introduced to
ubuntu in cosmic, so i should probably go and fix that too).

>
https://git.launchpad.net/ubuntu/+source/vlan/commit/?id=4c88eab61549ec4c6c8ed65e9610fca712ed98f4

getting closer with this one, but not quite there yet :)

this is the change that introduces this regression:

https://git.launchpad.net/ubuntu/+source/vlan/commit/?h=applied/ubuntu
/bionic-devel=117d183fa16e2d5e43da4cfe03e7e8685d27c6d1

yep it was me, sorry.

I want to say that I absolutely *HATE* the debian ifupdown api that
allows this kind of 'automagic' vlan creation just by appending ".NNN"
to an interface's name.  Is it *really* so hard to add a simple "vlan-
raw-device" param to the config?  The 'automagic'-ness of it makes
things *much* harder - especially when there are special cases like
this, a bridge on top of a vlan.

In any case, we can fix this regression by special-casing any configured
interface that includes a "bridge_ports" param, which (basically) should
get us back to how things worked before.

However, I personally think it's super, super confusing for juju to name
a bridge device with vlan suffix, and I highly support the juju patch
from comment 3 that changes the '.' to '-' (in addition to fixing this
regression in vlan).


** Changed in: vlan (Ubuntu)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

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

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

** Also affects: vlan (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

** Also affects: vlan (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: vlan (Ubuntu Disco)
   Importance: Medium
 Assignee: Dan Streetman (ddstreet)
   Status: In Progress

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

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

Title:
  Autogenerated interface name prevents creating a bridge over a VLAN

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

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

[Bug 1808553] [NEW] do-release-upgrade failed 17.10 to Last (x86 / 32bit)

2018-12-14 Thread dave
Public bug reported:


Vérification du gestionnaire de paquets
Lecture des listes de paquets… Terminé
Construction de l'arbre des dépendances
Lecture des informations d'état… Terminé

Calcul des modifications en cours

Calcul des modifications en cours

Impossible d'évaluer la mise à niveau

Un problème insoluble est survenu lors de la préparation de la mise à 
niveau. 

Ceci peut-être dû à : 
* la mise à niveau vers une version de développement d'Ubuntu ; 
* la version de développement d'Ubuntu est actuellement utilisée ; 
* des paquets logiciels non officiels, non fournis par Ubuntu. 

Si rien de tout cela ne s'applique, veuillez signaler ce bogue en 
utilisant la commande « ubuntu-bug ubuntu-release-upgrader-core » 
dans un terminal. 

---

That all i don't know why (3 month i try to upgrade)

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: ubuntu-release-upgrader-core 1:17.10.11
Uname: Linux 4.15.10-041510-generic i686
ApportVersion: 2.20.7-0ubuntu3.9
Architecture: i386
CrashDB: ubuntu
CurrentDesktop: XFCE
Date: Fri Dec 14 16:43:49 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-05-11 (1313 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
PackageArchitecture: all
SourcePackage: ubuntu-release-upgrader
UpgradeStatus: Upgraded to artful on 2018-12-14 (0 days ago)
VarLogDistupgradeAptclonesystemstate.tar.gz:

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


** Tags: apport-bug artful dist-upgrade i386 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/1808553

Title:
  do-release-upgrade failed 17.10 to Last (x86 / 32bit)

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

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

[Bug 1807056] Re: Occasional Keyboard freeze

2018-12-14 Thread Dilip
I am sorry. This is my primary laptop. I plan to keep the Ubuntu as
default as possible.

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

Title:
  Occasional Keyboard freeze

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

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

[Bug 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th

2018-12-14 Thread Thorsten
oky, i now also experienced the issue a couple of times but it only
occurs in 1 out of 10 times and i resolved by an additional
suspend/resume.

In dmesg i see:
psmouse serio1: Failed to disable mouse on isa0060/serio1

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

Title:
  Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1
  Carbon 6th

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

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

[Bug 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th

2018-12-14 Thread Thorsten
*more info: i am using ubuntu 18.04.1, 4.19.9 from mainline, libinput 1.12.1, 
attached is my dmesg, the last but one suspend/resume deactivated the touchpad 
and the last one restored it.
i had psmouse.synaptics_intertouch=1, i am now testing 
psmouse.synaptics_intertouch=0 

** Attachment added: "dmesg"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1791427/+attachment/5222301/+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/1791427

Title:
  Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1
  Carbon 6th

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

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

[Bug 1808366] Re: Led trigger not working on rpi3b+

2018-12-14 Thread Paolo Pisati
** Description changed:

  Impact:
  
  People are reporting that the green led (the one next to the red power
  led) is not working on the RaspberryPi 3B+ board.
  
  After debugging the issue, this is what i found:
  
  1) in reality, it's not the green led that is not working, but is the
- power led that "fails":
+ power led that fails to initialize:
  
  ...
  [2.299216] leds-gpio: probe of soc:leds failed with error -2
  ...
  
  what happens is that, since all leds are initialized in a loop, if one
  of them fail to init properly, the loop tears down all the initialized
  leds in that loop - one can easily proof that by adding debug to
  drivers/leds/leds-gpio.c::gpio_leds_create() and drivers/leds/leds-
  gpio.c::gpio_led_probe(), or simply commenting out the pwr_led block in
  arch/arm/boot/dts/bcm2710-rpi-3-b-plus.dts - the board will boot up, the
  above leds-gpio error will disappear and act_led will work properly.
  
- 2) the pwr_led in all rpi3 boards (rpi3 a/b classic or b+) are not
+ 2) the pwr_led in all rpi3 boards (rpi3 a/b classic or b+) is not
  available direcly by the OS, instead only the Bradcom firmware can
  manipulate its gpio, thus a new mechanism that used the bcm firmware as
  a middleman was developed - the exgpio driver: using a mailbox
  mechanism, messages are sent from the Linux kernel to the Broadcom
- firmware to query the status of the led GPIO or set it, this was it's
- possible for the linux led trigger to make it work.
+ firmware to query or set the status of the led GPIO, this way it's
+ possible to hook the Linux led trigger to it
  
  Fix:
  
  The fix is composed of 7 patches:
  
  9194ee1 UBUNTU: [Config] GPIO_BCM_EXP=y
  24bfd3c UBUNTU: SAUCE: dts: rpi3: remove hpd-gpios overwrite
  b9d10bb4 UBUNTU: SAUCE: dts: cm3: revert hpd-gpios to gpio
  b75dca4 UBUNTU: SAUCE: make it build on bcm2709
  9989bb3 Revert "UBUNTU: SAUCE: dts: use the virtgpio driver"
  20a6601 bcm2835-gpio-exp: Copy/paste error adding base twice
  85f3449 bcm2835-gpio-exp: Driver for GPIO expander via mailbox service
  
- Starting from the bottom, patch 0001 and 002 contain the "gpio via firmware" 
driver (and a fix for it) - those are the original patches tha are present in 
the Github's RaspberryPi repository, and they were cherry-picked cleanly from 
it (minus same changes in Kconfig and Makefile for the surrounding context).
+ Starting from the bottom, patch 0001 and 002 contain the "gpio via firmware" 
driver (and a fix for it) - those are the original patches that are present in 
the Github's RaspberryPi repository[*] rpi-4.9.y branch, and they were 
cherry-picked cleanly from it (minus same changes in Kconfig and Makefile 
surrounding context to make it apply).
  Patch 0003 reverts a change that tried to pilot pwr led gpio using the 
default virtgpio driver.
  Patch 004 fixes the arch name: in 4.9 the Raspberry arch was called 
"ARCH_BCM2835", while in Xenial 4.4 is "ARCH_BCM2709".
- Patch 005 and 006 reduce the "regression surface": when patch 001 was 
introduced, the hdmi phy in the rpi3 and cm3 was moved to use this new code, 
but since our hdmi driver is significantly different from the one in the 
rpy-4.9 tree, and noe one has reported any problem with it, to reduce the 
regression potential, i reverted this change, and moved back these gpios to use 
the in-tree gpio driver (as it is now in Xenial), using two SAUCE patches.
+ Patch 005 and 006 reduce the "regression surface": when patch 001 was 
introduced, the hdmi phy in the rpi3 and cm3 was moved to use this new code, 
but since our hdmi driver is significantly different from the one in the 
rpy-4.9 tree, and no one has reported any problem with it, to reduce the 
regression potential, i reverted this change, and moved back these gpios to use 
the in-tree gpio driver (as it is now in Xenial), using two SAUCE patches.
  Finally, patch 007 enable the driver in our Ubuntu raspi2 config.
  
  By apply these patches, the pwr led correctly initialize during boot,
  and as a consequence the act led too.
  
  How to test:
  
  Add this to config.txt:
  
  dtparam=act_led_trigger=heartbeat
  dtparam=pwr_led_trigger=heartbeat
  
  and reboot - on a non-patched kernel, the power led (red) will be always-on, 
while the green led will be off.
  On a patched kernel, both leds will blink continuosly.
  
- 
  Regression:
  
  It's new code, so there's always regression potential in it, but by
  reducing the scope of the original patch, the impact is limited to the
  led code.
+ 
+ XXX TBD: testing with older / newer firmware, testing on an unsupported
+ platform (rpi2), why the dafualt-on led trigger is not working?
+ 
+ *: https://github.com/raspberrypi/linux

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

Title:
  Led trigger not working on rpi3b+

To manage notifications about this bug go to:

[Bug 1726856] Re: ufw does not start automatically at boot

2018-12-14 Thread Jamie Strandboge
@Matt, there aren't any errors in your journalctl output that I can see.

Without removing the change to /lib/ufw/ufw-init yet, can you reboot
until you see the problem, and then before you correct the issue, can
you attach the output of all of the following:

1. journalctl --no-pager > /tmp/journal.full
2. dpkg -l > /tmp/dpkg.list
3. sudo tar -zcf /tmp/ufw.tar.gz /lib/ufw/ /etc/default/ufw /etc/ufw/ 
/usr/share/ufw/
4. sudo ufw show raw > /tmp/ufw.raw


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

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

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

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

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

Title:
  ufw does not start automatically at boot

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

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

[Bug 1017274] Re: package ttf-sil-scheherazade (not installed) failed to install/upgrade: package ttf-sil-scheherazade is not ready for configuration cannot configure (current status `config-files')

2018-12-14 Thread Bobby de Vos
The defoma configuration file is no longer in the package, so this issue
should not occur in newer packages.

** Changed in: fonts-sil-scheherazade (Ubuntu)
   Status: New => Fix Released

** Changed in: fonts-sil-scheherazade (Ubuntu)
 Assignee: (unassigned) => Bobby de Vos (bobby-devos)

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

Title:
  package ttf-sil-scheherazade (not installed) failed to
  install/upgrade: package ttf-sil-scheherazade is not ready for
  configuration  cannot configure (current status `config-files')

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fonts-sil-scheherazade/+bug/1017274/+subscriptions

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

[Bug 1808538] Re: Please remove src:lua-torch-cutorch

2018-12-14 Thread Bug Watch Updater
** Changed in: lua-torch-cutorch (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/1808538

Title:
  Please remove src:lua-torch-cutorch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lua-torch-cutorch/+bug/1808538/+subscriptions

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

[Bug 1808418] Re: Thinkpad T430u won't boot without noapic workaround

2018-12-14 Thread bmaupin
** Description changed:

  I've used Ubuntu on this specific machine for years without problems,
  but starting with the 4.13 kernel that came with the 17.10 HWE and
  continuing into 18.04 kernels my computer would no longer boot, hanging
  at various screens:
  
  - A blank screen with a flashing cursor
  - A screen with this message:
  Loading Linux 4.13.0.36-generic ...
  Loading initial ramdisk ...
  - A screen with kernel messages, ending in:
  APCI: EC: interrupt blocked
  
  I've encountered the bug in a number of kernels, including:
  - 4.13.0-32
  - 4.13.0-36
  - 4.13.0-37
  - 4.15.0-24
  - 4.15.0-34
  - 4.15.0-36
  - 4.15.0-38
- 
- I'm running the latest BIOS.
+ - 4.15.0-42
  
  I was able to work around the issue by adding noapic to
  GRUB_CMDLINE_LINUX_DEFAULT in /etc/default grub, e.g.:
  
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noapic"
  
  I'm not entirely sure of the consequences of this workaround, but one
  thing I've noticed is significantly reduced battery life.
  
- This bug seems very similar to what's described here for the Thinkpad
- E485/E585:
- https://web.archive.org/web/20180919160303/https://evilazrael.de/content
- /getting-linux-boot-lenovo-thinkpad-e485e585
- 
  I'll attach screenshots of various times I've encountered this bug over
  the last year.
- 
- $ lsb_release -rd
- Description:  Ubuntu 18.04.1 LTS
- Release:  18.04
- 
- $ apt-cache policy linux-image-4.15.0-42-generic
- linux-image-4.15.0-42-generic:
-   Installed: 4.15.0-42.45
-   Candidate: 4.15.0-42.45
-   Version table:
-  *** 4.15.0-42.45 500
- 500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
- 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
- 100 /var/lib/dpkg/status
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-42-generic 4.15.0-42.45
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bryan  2349 F pulseaudio
  CurrentDesktop: XFCE
  Date: Thu Dec 13 15:31:15 2018
  HibernationDevice: RESUME=UUID=4afa8032-cfe5-45f4-a626-738ab33904ac
  InstallationDate: Installed on 2014-05-08 (1680 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: LENOVO 3351CTO
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic 
root=UUID=cffbc87d-956b-4986-94df-b3b64ae5237f ro quiet splash noapic 
vt.handoff=1
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-42-generic N/A
   linux-backports-modules-4.15.0-42-generic  N/A
   linux-firmware 1.173.2
  SourcePackage: linux
  UpgradeStatus: Upgraded to bionic on 2018-07-12 (154 days ago)
  dmi.bios.date: 06/01/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: H6ETA0WW (2.18 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 3351CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 STD DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrH6ETA0WW(2.18):bd06/01/2018:svnLENOVO:pn3351CTO:pvrThinkPadT430u:rvnLENOVO:rn3351CTO:rvrWin8STDDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430u
  dmi.product.name: 3351CTO
  dmi.product.version: ThinkPad T430u
  dmi.sys.vendor: LENOVO

** Description changed:

  I've used Ubuntu on this specific machine for years without problems,
  but starting with the 4.13 kernel that came with the 17.10 HWE and
  continuing into 18.04 kernels my computer would no longer boot, hanging
  at various screens:
  
  - A blank screen with a flashing cursor
  - A screen with this message:
  Loading Linux 4.13.0.36-generic ...
  Loading initial ramdisk ...
  - A screen with kernel messages, ending in:
  APCI: EC: interrupt blocked
  
  I've encountered the bug in a number of kernels, including:
  - 4.13.0-32
  - 4.13.0-36
  - 4.13.0-37
  - 4.15.0-24
  - 4.15.0-34
  - 4.15.0-36
  - 4.15.0-38
  - 4.15.0-42
  
  I was able to work around the issue by adding noapic to
  GRUB_CMDLINE_LINUX_DEFAULT in /etc/default grub, e.g.:
  
  GRUB_CMDLINE_LINUX_DEFAULT="quiet splash noapic"
  
  I'm not entirely sure of the consequences of this workaround, but one
  thing I've noticed is significantly reduced battery life.
  
+ This bug seems very similar to what's described here for the Thinkpad
+ E485/E585:
+ https://web.archive.org/web/20180919160303/https://evilazrael.de/content
+ /getting-linux-boot-lenovo-thinkpad-e485e585
+ 
  I'll attach screenshots of various times I've encountered this bug over
  the last year.
+ 
+ $ lsb_release -rd
+ Description:Ubuntu 18.04.1 LTS
+ Release:18.04
+ 
+ $ apt-cache policy linux-image-4.15.0-42-generic
+ 

[Bug 1808201] Re: Big ram memory use

2018-12-14 Thread Theo Linkspfeifer
Related upstream bug report:

https://gitlab.com/vala-panel-project/vala-panel-appmenu/issues/118

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

Title:
  Big ram memory use

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

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

[Bug 1749985] Re: dpkg: error processing package libc-bin (--configure): triggers looping, abandoned

2018-12-14 Thread Jamie Strandboge
** Changed in: ufw (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/1749985

Title:
  dpkg: error processing package libc-bin (--configure):  triggers
  looping, abandoned

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

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

[Bug 1724793] Re: Error localization

2018-12-14 Thread Jamie Strandboge
** Package changed: ufw (Ubuntu) => language-selector (Ubuntu)

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

Title:
  Error localization

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1724793/+subscriptions

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

[Bug 1660040] Re: old-fashioned ufw structure reduces usability

2018-12-14 Thread Jamie Strandboge
*** This bug is a duplicate of bug 910324 ***
https://bugs.launchpad.net/bugs/910324

** This bug has been marked a duplicate of bug 910324
   Add directory support for before.rules and after.rules

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

Title:
  old-fashioned ufw structure reduces usability

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

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

[Bug 1775043] Re: bash completion not working: uses deprecated have()

2018-12-14 Thread Jamie Strandboge
** Also affects: ufw (Ubuntu Disco)
   Importance: Undecided
 Assignee: Jamie Strandboge (jdstrand)
   Status: Triaged

** Changed in: ufw (Ubuntu Disco)
   Status: Triaged => In Progress

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

** Changed in: ufw (Ubuntu Cosmic)
   Importance: Undecided => Medium

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

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

Title:
  bash completion not working: uses deprecated have()

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

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

[Bug 1792835] Re: Bash completion for Inkscape does not work

2018-12-14 Thread Jamie Strandboge
The ufw bug is being tracking in bug 1775043. Removing that task.

** No longer affects: ufw (Ubuntu)

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

Title:
  Bash completion for Inkscape does not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt-xapian-index/+bug/1792835/+subscriptions

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

[Bug 1204579] Re: ufw doesn't support concurrent updates

2018-12-14 Thread Jamie Strandboge
** Also affects: ufw (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

** Also affects: ufw (Ubuntu Disco)
   Importance: Medium
 Assignee: Jamie Strandboge (jdstrand)
   Status: In Progress

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

** Changed in: ufw (Ubuntu Cosmic)
   Status: New => Triaged

** Changed in: ufw (Ubuntu Bionic)
   Status: New => Triaged

** Changed in: ufw (Ubuntu Cosmic)
   Importance: Undecided => Medium

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

** Changed in: ufw (Ubuntu Cosmic)
 Assignee: (unassigned) => Jamie Strandboge (jdstrand)

** Changed in: ufw (Ubuntu Bionic)
 Assignee: (unassigned) => Jamie Strandboge (jdstrand)

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

Title:
  ufw doesn't support concurrent updates

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

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

[Bug 1155250] Re: ufw should error if arguments given to "ufw enable"

2018-12-14 Thread Jamie Strandboge
This was fixed in 0.35.

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

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

Title:
  ufw should error if arguments given to "ufw enable"

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

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

[Bug 1602834] Re: obsolete conffiles not cleaned up on upgrade

2018-12-14 Thread Jamie Strandboge
** Changed in: ufw (Ubuntu)
   Status: New => Triaged

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

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

** Also affects: ufw (Ubuntu Disco)
   Importance: Medium
   Status: Triaged

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

** Changed in: ufw (Ubuntu Cosmic)
   Status: New => Triaged

** Changed in: ufw (Ubuntu Bionic)
   Status: New => Triaged

** Changed in: ufw (Ubuntu Cosmic)
   Importance: Undecided => Medium

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

** Changed in: ufw (Ubuntu Disco)
 Assignee: (unassigned) => Jamie Strandboge (jdstrand)

** Changed in: ufw (Ubuntu Cosmic)
 Assignee: (unassigned) => Jamie Strandboge (jdstrand)

** Changed in: ufw (Ubuntu Bionic)
 Assignee: (unassigned) => Jamie Strandboge (jdstrand)

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

Title:
  obsolete conffiles not cleaned up on upgrade

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

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

[Bug 1509725] Re: Some ICMPv6 packets rejected due to rule ordering

2018-12-14 Thread Jamie Strandboge
*** This bug is a duplicate of bug 1664133 ***
https://bugs.launchpad.net/bugs/1664133

** This bug has been marked a duplicate of bug 1664133
   ipv6 multicast pings don't return

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

Title:
  Some ICMPv6 packets rejected due to rule ordering

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

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

[Bug 1719211] Re: Bad interface name

2018-12-14 Thread Jamie Strandboge
** Also affects: ufw (Ubuntu Disco)
   Importance: Medium
 Assignee: Jamie Strandboge (jdstrand)
   Status: In Progress

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

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

** Changed in: ufw (Ubuntu Cosmic)
   Status: New => Triaged

** Changed in: ufw (Ubuntu Bionic)
   Status: New => Triaged

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

** Changed in: ufw (Ubuntu Cosmic)
   Importance: Undecided => Medium

** Changed in: ufw (Ubuntu Bionic)
 Assignee: (unassigned) => Jamie Strandboge (jdstrand)

** Changed in: ufw (Ubuntu Cosmic)
 Assignee: (unassigned) => Jamie Strandboge (jdstrand)

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

Title:
  Bad interface name

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

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

[Bug 1661809] Re: package ufw (not installed) failed to install/upgrade: subprocess installed post-removal script returned error exit status 1

2018-12-14 Thread Jamie Strandboge
** Package changed: ufw (Ubuntu) => rpcbind (Ubuntu)

** Summary changed:

- package ufw (not installed) failed to install/upgrade: subprocess installed 
post-removal script returned error exit status 1
+ failed to install/upgrade: subprocess installed post-removal script returned 
error exit status 1

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

Title:
  failed to install/upgrade: subprocess installed post-removal script
  returned error exit status 1

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

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

[Bug 1664133] Re: ipv6 multicast pings don't return

2018-12-14 Thread Jamie Strandboge
** Also affects: ufw (Ubuntu)
   Importance: Undecided
   Status: New

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

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

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

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

** Changed in: ufw (Ubuntu Cosmic)
   Status: New => Triaged

** Changed in: ufw (Ubuntu Bionic)
   Status: New => Triaged

** Changed in: ufw (Ubuntu Bionic)
   Importance: Undecided => Low

** Changed in: ufw (Ubuntu Cosmic)
   Importance: Undecided => Low

** Changed in: ufw (Ubuntu Disco)
   Importance: Undecided => Low

** Changed in: ufw (Ubuntu Disco)
 Assignee: (unassigned) => Jamie Strandboge (jdstrand)

** Changed in: ufw (Ubuntu Cosmic)
 Assignee: (unassigned) => Jamie Strandboge (jdstrand)

** Changed in: ufw (Ubuntu Bionic)
 Assignee: (unassigned) => Jamie Strandboge (jdstrand)

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

Title:
  ipv6 multicast pings don't return

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

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

[Bug 1766503] Re: ibus-* randomly use high CPU

2018-12-14 Thread Michal
OK. I got it. In my case processes starts in similar way /tmp/XXX-XXX...
that's was suspicious after search info about similar cases I found
this:

https://ubuntuforums.org/showthread.php?t=2389313
https://www.reddit.com/r/Addons4Kodi/comments/8eto78/people_using_unofficial_kodi_addon_on_linux/

Please check if ~/.config/autostart/dbus-daemon.desktop exists.

After cleaning ~/.config/autostart/ folder situation is better also i
found suspicious inictl file in ~/.cache/fontconfig

I will check files with ClamAV but this will take some time.

For now CPU usage looks good for me.

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

Title:
  ibus-* randomly use high CPU

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

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

[Bug 1772921] Re: freeipa web ui -- incorrect configuration for awesome fonts

2018-12-14 Thread Andreas Ntaflos
Is this fix going to make it into bionic?

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

Title:
  freeipa web ui -- incorrect configuration for awesome fonts

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

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

[Bug 1204579] Re: ufw doesn't support concurrent updates

2018-12-14 Thread Jamie Strandboge
** Changed in: ufw (Ubuntu)
   Status: Triaged => In Progress

** Changed in: ufw (Ubuntu)
 Assignee: (unassigned) => Jamie Strandboge (jdstrand)

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

Title:
  ufw doesn't support concurrent updates

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

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

[Bug 1431322] Re: UnicodeEncodeError: 'ascii' codec can't encode character u'\ufeff'

2018-12-14 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: duplicity (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/1431322

Title:
  UnicodeEncodeError: 'ascii' codec can't encode character u'\ufeff'

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

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

[Bug 1377600] Re: ufw errors after ctr+c interupt

2018-12-14 Thread Jamie Strandboge
This will be fixed with the new feature for concurrent updates, which is
scheduled for ufw 0.36.

** Changed in: ufw (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: ufw (Ubuntu)
 Assignee: (unassigned) => Jamie Strandboge (jdstrand)

** Also affects: ufw (Ubuntu Disco)
   Importance: Medium
 Assignee: Jamie Strandboge (jdstrand)
   Status: In Progress

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

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

** Changed in: ufw (Ubuntu Bionic)
   Status: New => Triaged

** Changed in: ufw (Ubuntu Cosmic)
   Status: New => Triaged

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

** Changed in: ufw (Ubuntu Cosmic)
   Importance: Undecided => Medium

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

Title:
  ufw errors after ctr+c interupt

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

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

[Bug 1368411] Re: Cannot insert IPV6 rule before IPV4 rules

2018-12-14 Thread Jamie Strandboge
** Changed in: ufw
   Importance: Undecided => Low

** Changed in: ufw
   Importance: Low => Medium

** Changed in: ufw (Ubuntu Disco)
   Status: Triaged => In Progress

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

Title:
  Cannot insert IPV6 rule before IPV4 rules

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

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

[Bug 1431322] Re: UnicodeEncodeError: 'ascii' codec can't encode character u'\ufeff'

2018-12-14 Thread Wolf
Mine looks similar - ubuntu 10.04:

saving data fails with unknown error:

Traceback (innermost last):
  File "/usr/bin/duplicity", line 1555, in 
with_tempdir(main)
  File "/usr/bin/duplicity", line 1541, in with_tempdir
fn()
  File "/usr/bin/duplicity", line 1393, in main
do_backup(action)
  File "/usr/bin/duplicity", line 1511, in do_backup
full_backup(col_stats)
  File "/usr/bin/duplicity", line 572, in full_backup
globals.backend)
  File "/usr/bin/duplicity", line 454, in write_multivol
(tdp, dest_filename, vol_num)))
  File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line 
146, in schedule_task
return self.__run_synchronously(fn, params)
  File "/usr/lib/python2.7/dist-packages/duplicity/asyncscheduler.py", line 
172, in __run_synchronously
ret = fn(*params)
  File "/usr/bin/duplicity", line 453, in 
vol_num: put(tdp, dest_filename, vol_num),
  File "/usr/bin/duplicity", line 342, in put
backend.put(tdp, dest_filename)
  File "/usr/lib/python2.7/dist-packages/duplicity/backend.py", line 395, in 
inner_retry
% (n, e.__class__.__name__, util.uexc(e)))
  File "/usr/lib/python2.7/dist-packages/duplicity/util.py", line 79, in uexc
return ufn(unicode(e).encode('utf-8'))
 UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 33: 
ordinal not in range(128)

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

Title:
  UnicodeEncodeError: 'ascii' codec can't encode character u'\ufeff'

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

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

[Bug 1808366] Re: Led trigger not working on rpi3b+

2018-12-14 Thread Paolo Pisati
** Description changed:

  Impact:
  
  People are reporting that the green led (the one next to the red power
  led) is not working on the RaspberryPi 3B+ board.
  
  After debugging the issue, this is what i found:
  
  1) in reality, it's not the green led that is not working, but is the
  power led that "fails":
  
  ...
  [2.299216] leds-gpio: probe of soc:leds failed with error -2
  ...
  
  what happens is that, since all leds are initialized in a loop, if one
  of them fail to init properly, the loop tears down all the initialized
  leds in that loop - one can easily proof that by adding debug to
  drivers/leds/leds-gpio.c::gpio_leds_create() and drivers/leds/leds-
  gpio.c::gpio_led_probe(), or simply commenting out the pwr_led block in
  arch/arm/boot/dts/bcm2710-rpi-3-b-plus.dts - the board will boot up, the
  above leds-gpio error will disappear and act_led will work properly.
  
  2) the pwr_led in all rpi3 boards (rpi3 a/b classic or b+) are not
  available direcly by the OS, instead only the Bradcom firmware can
  manipulate its gpio, thus a new mechanism that used the bcm firmware as
  a middleman was developed - the exgpio driver: using a mailbox
  mechanism, messages are sent from the Linux kernel to the Broadcom
  firmware to query the status of the led GPIO or set it, this was it's
  possible for the linux led trigger to make it work.
  
  Fix:
  
- The original
+ The fix is composed of 7 patches:
+ 
+ 9194ee1 UBUNTU: [Config] GPIO_BCM_EXP=y
+ 24bfd3c UBUNTU: SAUCE: dts: rpi3: remove hpd-gpios overwrite
+ b9d10bb4 UBUNTU: SAUCE: dts: cm3: revert hpd-gpios to gpio
+ b75dca4 UBUNTU: SAUCE: make it build on bcm2709
+ 9989bb3 Revert "UBUNTU: SAUCE: dts: use the virtgpio driver"
+ 20a6601 bcm2835-gpio-exp: Copy/paste error adding base twice
+ 85f3449 bcm2835-gpio-exp: Driver for GPIO expander via mailbox service
+ 
+ Starting from the bottom, patch 0001 and 002 contain the "gpio via firmware" 
driver (and a fix for it) - those are the original patches tha are present in 
the Github's RaspberryPi repository, and they were cherry-picked cleanly from 
it (minus same changes in Kconfig and Makefile for the surrounding context).
+ Patch 0003 reverts a change that tried to pilot pwr led gpio using the 
default virtgpio driver.
+ Patch 004 fixes the arch name: in 4.9 the Raspberry arch was called 
"ARCH_BCM2835", while in Xenial 4.4 is "ARCH_BCM2709".
+ Patch 005 and 006 reduce the "regression surface": when patch 001 was 
introduced, the hdmi phy in the rpi3 and cm3 was moved to use this new code, 
but since our hdmi driver is significantly different from the one in the 
rpy-4.9 tree, and noe one has reported any problem with it, to reduce the 
regression potential, i reverted this change, and moved back these gpios to use 
the in-tree gpio driver (as it is now in Xenial), using two SAUCE patches.
+ Finally, patch 007 enable the driver in our Ubuntu raspi2 config.
+ 
+ By apply these patches, the pwr led correctly initialize during boot,
+ and as a consequence the act led too.
+ 
+ How to test:
+ 
+ Add this to config.txt:
+ 
+ dtparam=act_led_trigger=heartbeat
+ dtparam=pwr_led_trigger=heartbeat
+ 
+ and reboot - on a non-patched kernel, the power led (red) will be always-on, 
while the green led will be off.
+ On a patched kernel, both leds will blink continuosly.
+ 
  
  Regression:
+ 
+ It's new code, so there's always regression potential in it, but by
+ reducing the scope of the original patch, the impact is limited to the
+ led code.

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

Title:
  Led trigger not working on rpi3b+

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

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

[Bug 1808526] Re: package samba 2:4.8.4+dfsg-2ubuntu2.1 failed to install/upgrade: installed samba package post-installation script subprocess returned error exit status 1

2018-12-14 Thread Andreas Hasenack
Thanks for filing this bug in Ubuntu.

This is the error that was reported:
  get_guest_info3 failed with NT_STATUS_NO_SUCH_USER
  ERROR: failed to setup guest info.
  get_guest_info3 failed with NT_STATUS_NO_SUCH_USER
  ERROR: failed to setup guest info.
  get_guest_info3 failed with NT_STATUS_NO_SUCH_USER
  ERROR: failed to setup guest info.

You have a guest account setting like this in your smb.conf:
guest account = Servidor


Please make sure that the linux user "Servidor" exists. Or remove that line and 
let the sane default of "nobody" be used. Either way, after you fix it, run 
this:

sudo apt -f install

and it should be fine.

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

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

Title:
  package samba 2:4.8.4+dfsg-2ubuntu2.1 failed to install/upgrade:
  installed samba package post-installation script subprocess returned
  error exit status 1

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

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs


[Bug 1808526] Re: package samba 2:4.8.4+dfsg-2ubuntu2.1 failed to install/upgrade: installed samba package post-installation script subprocess returned error exit status 1

2018-12-14 Thread Andreas Hasenack
Thanks for filing this bug in Ubuntu.

This is the error that was reported:
  get_guest_info3 failed with NT_STATUS_NO_SUCH_USER
  ERROR: failed to setup guest info.
  get_guest_info3 failed with NT_STATUS_NO_SUCH_USER
  ERROR: failed to setup guest info.
  get_guest_info3 failed with NT_STATUS_NO_SUCH_USER
  ERROR: failed to setup guest info.

You have a guest account setting like this in your smb.conf:
guest account = Servidor


Please make sure that the linux user "Servidor" exists. Or remove that line and 
let the sane default of "nobody" be used. Either way, after you fix it, run 
this:

sudo apt -f install

and it should be fine.

** Changed in: samba (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/1808526

Title:
  package samba 2:4.8.4+dfsg-2ubuntu2.1 failed to install/upgrade:
  installed samba package post-installation script subprocess returned
  error exit status 1

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

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

[Bug 1775043] Re: bash completion not working: uses deprecated have()

2018-12-14 Thread Jamie Strandboge
** Changed in: ufw
   Importance: Undecided => Medium

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

Title:
  bash completion not working: uses deprecated have()

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

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

[Bug 1808538] [NEW] Please remove src:lua-torch-cutorch

2018-12-14 Thread Graham Inggs
Public bug reported:

Deprecated upstream, FTBFS

** Affects: lua-torch-cutorch (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: lua-torch-cutorch (Debian)
 Importance: Unknown
 Status: Unknown

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

** Also affects: lua-torch-cutorch (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916281
   Importance: Unknown
   Status: Unknown

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

Title:
  Please remove src:lua-torch-cutorch

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lua-torch-cutorch/+bug/1808538/+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)

2018-12-14 Thread Tony Partridge
Confirmed fixed with live ubuntu, working with gnome-shell
3.28.3-0ubuntu0.18.04.4 from bionic-proposed. Thanks guys, was a pesky
bug.

-- 
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 1771905] Re: Package does not depend on dbus-launch

2018-12-14 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: terminator (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/1771905

Title:
  Package does not depend on dbus-launch

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

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

[Bug 1798597] Please test proposed package

2018-12-14 Thread Adam Conrad
Hello Timo, or anyone else affected,

Accepted xorg-hwe-18.04 into bionic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/xorg-
hwe-18.04/1:7.7+19ubuntu8~18.04.1 in a few hours, and then in the
-proposed repository.

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

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

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

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

** Package changed: xorg (Ubuntu Bionic) => xorg-hwe-18.04 (Ubuntu
Bionic)

** Changed in: xorg-hwe-18.04 (Ubuntu Bionic)
   Status: New => Fix Committed

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

Title:
  Backport packages for 18.04.2 HWE stack

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

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

[Bug 887331] Re: file-roller cannot open filetypes with derived mimetypes (e.g. epub and ods files)

2018-12-14 Thread Tim Wahrendorff
Bug still exists in 18.04

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

Title:
  file-roller cannot open filetypes with derived mimetypes (e.g. epub
  and ods files)

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

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

[Bug 1808535] [NEW] package nvidia-opencl-icd-340 (not installed) failed to install/upgrade: conflicting packages - not installing nvidia-opencl-icd-340

2018-12-14 Thread dezi
Public bug reported:

Ubuntu 18.10

ProblemType: Package
DistroRelease: Ubuntu 18.10
Package: nvidia-opencl-icd-340 (not installed)
ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
Uname: Linux 4.18.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.1
AptOrdering:
 libcuda1-340:amd64: Install
 nvidia-340:amd64: Install
 nvidia-opencl-icd-340:amd64: Install
 nvidia-settings:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Fri Dec 14 15:11:58 2018
ErrorMessage: conflicting packages - not installing nvidia-opencl-icd-340
InstallationDate: Installed on 2018-12-03 (11 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.10
PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu5
 apt  1.7.0
SourcePackage: nvidia-graphics-drivers-340
Title: package nvidia-opencl-icd-340 (not installed) failed to install/upgrade: 
conflicting packages - not installing nvidia-opencl-icd-340
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package cosmic

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

Title:
  package nvidia-opencl-icd-340 (not installed) failed to
  install/upgrade: conflicting packages - not installing nvidia-opencl-
  icd-340

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

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

[Bug 1808526] Re: package samba 2:4.8.4+dfsg-2ubuntu2.1 failed to install/upgrade: installed samba package post-installation script subprocess returned error exit status 1

2018-12-14 Thread Leonidas S. Barbosa
** Information type changed from Private Security to Public

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

Title:
  package samba 2:4.8.4+dfsg-2ubuntu2.1 failed to install/upgrade:
  installed samba package post-installation script subprocess returned
  error exit status 1

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

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

[Bug 1807702] Re: linux-oracle: 4.15.0-1007.9 -proposed tracker

2018-12-14 Thread Brad Figg
** Description changed:

  This bug is for tracking the 4.15.0-1007.7 upload package. This bug will
  contain status and testing results related to that upload.
  
  For an explanation of the tasks and the associated workflow see: 
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
  -- swm properties --
  boot-testing-requested: true
  kernel-stable-master-bug: 1806659
  phase: Uploaded
  phase-changed: Wednesday, 12. December 2018 19:38 UTC
  reason:
-   promote-to-proposed: Ready for review
+   promote-to-proposed: Review in progress

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

Title:
  linux-oracle: 4.15.0-1007.9 -proposed tracker

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

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

[Bug 1808168] Re: Neutron FWaaS panel missing from dashboard on Queens

2018-12-14 Thread James Page
Thanks for the review @sil2100

1) TBH I don't know - that's how it arrived in the first sync from
Debian, but as we tidied the packaging last cycle we put things back in
'normal' places as much as possible.

2) That was not actually needed - the call to 'python manage.py
collectstatic' in the postinst script will shuffle things around into
the correct locations.

3) OpenStack publish release versions
(https://releases.openstack.org/queens/#neutron-fwaas-dashboard) - 1.3.0
is the most recent fwaas-dashboard version that's know compatible with
the rest of OpenStack queens.  1.5.0 is a Rocky version, so although it
might just work, it would put Ubuntu out of alignment with upstream
testing activities which generally is not super awesome.

Hope that explain things.

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

Title:
  Neutron FWaaS panel missing from dashboard on Queens

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-openstack-dashboard/+bug/1808168/+subscriptions

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

[Bug 1808168] Re: Neutron FWaaS panel missing from dashboard on Queens

2018-12-14 Thread Łukasz Zemczak
s/xenial/bionic/ of course.

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

Title:
  Neutron FWaaS panel missing from dashboard on Queens

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-openstack-dashboard/+bug/1808168/+subscriptions

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

[Bug 1775043] Re: bash completion not working: uses deprecated have()

2018-12-14 Thread Jamie Strandboge
This was committed to ufw a while ago and will be in the upcoming 0.36,
which I plan to SRU back to bionic.

** Changed in: ufw
   Status: In Progress => Fix Committed

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

Title:
  bash completion not working: uses deprecated have()

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

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

[Bug 1807702] Re: linux-oracle: 4.15.0-1007.9 -proposed tracker

2018-12-14 Thread Łukasz Zemczak
** Changed in: kernel-sru-workflow/promote-to-proposed
   Status: Confirmed => In Progress

** Changed in: kernel-sru-workflow/promote-to-proposed
 Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Łukasz 
Zemczak (sil2100)

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

Title:
  linux-oracle: 4.15.0-1007.9 -proposed tracker

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

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

[Bug 1808168] Re: Neutron FWaaS panel missing from dashboard on Queens

2018-12-14 Thread Łukasz Zemczak
I looked at the neutron-fwaas-dashboard package in the xenial NEW queue
and I have some question. There are obviously some differences between
1.3.0 in cosmic and the one backported to bionic. This makes the review
a bit less straightforward as our regular SRU NEW package-backport
policies do not apply.

The most obvious changes are the ones from py3 -> py2 which has been
explained in this bug, so I'll skip that part. There are some others
that I'd first want to know some about .

1) I noticed that in the cosmic package the tests were ran during
override_dh_install (which did seem a bit strange to me) but now have
moved to the proper place in override_dh_auto_test. What was the reason
that it was previously done at a different step?

2) In the original cosmic package, in override_dh_install I see that
some static files were being copied over to /usr/share/openstack-
dashboard/openstack_dashboard/static etc. which is not happening anymore
in the bionic backport. Everything else moved to
override_dh_auto_install. Are those now installed as part of pkgos-
dh_auto_install ? Why did the installation stages move so much?

3) This is a minor question (out of curiosity), just wanted to get some
context on this: why is 1.3.0 backported instead of 1.5.0? Not a problem
of course.

Thanks!

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

Title:
  Neutron FWaaS panel missing from dashboard on Queens

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-openstack-dashboard/+bug/1808168/+subscriptions

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

[Bug 1808528] Re: Update linux-firmware in bionic for 18.10 hwe kernel

2018-12-14 Thread Seth Forshee
** Changed in: linux-firmware (Ubuntu Bionic)
   Status: In Progress => Fix Committed

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

Title:
  Update linux-firmware in bionic for 18.10 hwe kernel

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

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

[Bug 1808412] Re: 4.15.0 memory allocation issue

2018-12-14 Thread Marc Gariépy
When the memory allocation was stalled, here is what perf top was giving me:
Samples: 483K of event 'cycles:ppp', Event count (approx.): 52114089074
Overhead  Shared Object Symbol
  28.53%  [kernel]  [k] total_mapcount
  25.34%  [kernel]  [k] kvm_age_rmapp
  13.54%  [kernel]  [k] slot_rmap_walk_next
  11.24%  [kernel]  [k] kvm_handle_hva_range
   6.35%  [kernel]  [k] rmap_get_first
   3.69%  [kernel]  [k] __x86_indirect_thunk_r13
   1.33%  [kernel]  [k] __isolate_lru_page
   0.63%  [kernel]  [k] 
isolate_lru_pages.isra.58
   0.48%  [kernel]  [k] page_vma_mapped_walk
   0.40%  [kernel]  [k] __mod_node_page_state
   0.35%  [kernel]  [k] clear_page_erms
   0.31%  [kernel]  [k] shrink_page_list
   0.28%  [kernel]  [k] _find_next_bit
   0.27%  [kernel]  [k] putback_inactive_pages
   0.27%  [kernel]  [k] move_active_pages_to_lru
   0.27%  [kernel]  [k] inactive_list_is_low
   0.22%  [kernel]  [k] __mod_zone_page_state


numactl -H when the memorry allocation stalled:
root@gpu-compute028:~# numactl -H
available: 2 nodes (0-1)
node 0 cpus: 0 2 4 6 8 10 12 14
node 0 size: 64288 MB
node 0 free: 55983 MB
node 1 cpus: 1 3 5 7 9 11 13 15
node 1 size: 64489 MB
node 1 free: 63810 MB
node distances:
node   0   1 
  0:  10  21 
  1:  21  10 
root@gpu-compute028:~# numactl -H
available: 2 nodes (0-1)
node 0 cpus: 0 2 4 6 8 10 12 14
node 0 size: 64288 MB
node 0 free: 366 MB
node 1 cpus: 1 3 5 7 9 11 13 15
node 1 size: 64489 MB
node 1 free: 63782 MB
node distances:
node   0   1 
  0:  10  21 
  1:  21  10 
root@gpu-compute028:~# numactl -H
available: 2 nodes (0-1)
node 0 cpus: 0 2 4 6 8 10 12 14
node 0 size: 64288 MB
node 0 free: 368 MB
node 1 cpus: 1 3 5 7 9 11 13 15
node 1 size: 64489 MB
node 1 free: 63757 MB
node distances:
node   0   1 
  0:  10  21 
  1:  21  10 
root@gpu-compute028:~# numactl -H
available: 2 nodes (0-1)
node 0 cpus: 0 2 4 6 8 10 12 14
node 0 size: 64288 MB
node 0 free: 368 MB
node 1 cpus: 1 3 5 7 9 11 13 15
node 1 size: 64489 MB
node 1 free: 63744 MB
node distances:
node   0   1 
  0:  10  21 
  1:  21  10 
root@gpu-compute028:~# numactl -H
available: 2 nodes (0-1)
node 0 cpus: 0 2 4 6 8 10 12 14
node 0 size: 64288 MB
node 0 free: 366 MB
node 1 cpus: 1 3 5 7 9 11 13 15
node 1 size: 64489 MB
node 1 free: 63504 MB
node distances:
node   0   1 
  0:  10  21 
  1:  21  10 

then i killed the process.

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

Title:
  4.15.0 memory allocation issue

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

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

[Bug 1780628] Re: linux-4.15.0-23-generic RAID 5 kernel BUG

2018-12-14 Thread Jaroslav Dytrych
I have a same problem with the current version of Ubuntu 18.04.1 LTS
(Bionic Beaver) with kernel 4.15.0-42-generic.

I have a new RAID 5 array with 4 12TB drives. As the array is being
initialized, it takes 3 to 10 minutes to reach a kernel bug (under the
additional system load less than 1 minute).

** Attachment added: "Call Trace"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1780628/+attachment/575/+files/trace.txt

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

Title:
  linux-4.15.0-23-generic RAID 5 kernel BUG

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

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

[Bug 1759836] Florian is dope

2018-12-14 Thread ach619
i started this thread the day ubuntu 18 was released, I've tried the work
around. It solved my problem, so I want to thank the original solution
contributor (...forgot which email it was. Read it and implemented it a
while ago). but I also thank you Florian for the clear, concise, well
articulated, up to date description of the work around. Specifically the
line numbers and code diff. much appreciated.

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

Title:
  systemd-udevd consumes 100% of CPU

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

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

[Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic

2018-12-14 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: qemu (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/1797581

Title:
  Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to
  kernel panic

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

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

[Bug 1808528] [NEW] Update linux-firmware in bionic for 18.10 hwe kernel

2018-12-14 Thread Seth Forshee
Public bug reported:

SRU Justification

Impact: A 4.18-based hwe kernel has been introduced into bionic. However
some of the firmware files it requires are missing from bionic's linux-
firmware, rendering the relevant hardware inoperable.

Fix: Add the missing firmware files.

Regression Potential: Most of these files will not be used by the
existing kernels in xenial. A few may be, and while regressions are not
expected it's possible that new firmware versions might introduce
regressions.

** Affects: linux-firmware (Ubuntu)
 Importance: High
 Assignee: Seth Forshee (sforshee)
 Status: Invalid

** Affects: linux-firmware (Ubuntu Bionic)
 Importance: High
 Assignee: Seth Forshee (sforshee)
 Status: In Progress

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

** Changed in: linux-firmware (Ubuntu Bionic)
   Importance: Undecided => High

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

** Changed in: linux-firmware (Ubuntu Bionic)
 Assignee: (unassigned) => Seth Forshee (sforshee)

** Changed in: linux-firmware (Ubuntu)
   Status: In Progress => Invalid

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

Title:
  Update linux-firmware in bionic for 18.10 hwe kernel

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

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

[Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic

2018-12-14 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to
  kernel panic

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

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

[Bug 1763387] Re: Bionic HWE kernel (4.15) does not contain the bnx2 (Broadcom NetXtreme II network card) firmware

2018-12-14 Thread Seth Forshee
*** This bug is a duplicate of bug 1763823 ***
https://bugs.launchpad.net/bugs/1763823

I believe that this bug should have been fixed by the updates for bug
1763823. Marking as a duplicate, but please let me know if this is still
an issue.

** This bug has been marked a duplicate of bug 1763823
   Update firmware for 18.04 hwe kernel

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

Title:
  Bionic HWE kernel (4.15) does not contain the bnx2 (Broadcom NetXtreme
  II network card) firmware

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

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

[Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic

2018-12-14 Thread Andres Rodriguez
Setting this back to incomplete for MAAS because there is not enough
information to determine this is a MAAS Bug. That said, given that this
work with any VM other than one with 2048 of RAM, the issue may appear
to be the kernel or libvirt.

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

Title:
  Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to
  kernel panic

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

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

[Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic

2018-12-14 Thread Andres Rodriguez
** Changed in: maas
   Status: Confirmed => Incomplete

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

Title:
  Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to
  kernel panic

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

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

[Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic

2018-12-14 Thread Vladimir Grevtsev
Subscribing field-medium as workaround (e.g not to use 2048mb ram VMs)
exists, but solution still need to be found.

Also, before yesterday (e.g on libvirt 1:2.11+dfsg-1ubuntu7.8 + maas
2.5rc2) worked fine.

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

Title:
  Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to
  kernel panic

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

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

[Bug 1797581] Re: Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to kernel panic

2018-12-14 Thread Vladimir Grevtsev
Reproduced today on MAAS 2.5 / latest Bionic.

qemu/maas versions: https://paste.ubuntu.com/p/kDk3c9tVFX/

good vm dump: http://paste.ubuntu.com/p/zTW2p6JGQJ/
good vm log: http://paste.ubuntu.com/p/V7GP9KgP8S/
good vm serial output: http://paste.ubuntu.com/p/FDymQcH8qD/

bad vm dump: http://paste.ubuntu.com/p/ZCv5dv3DTS/
bad vm log: http://paste.ubuntu.com/p/4Zk5qq9TfB/
bad vm serial output: http://paste.ubuntu.com/p/QgbmZsjPPP/

** Changed in: maas
   Status: Incomplete => Confirmed

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

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

** Tags added: cpe-onsite

** Tags added: field-medium

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

Title:
  Composing a VM in MAAS with exactly 2048 MB RAM causes the VM to
  kernel panic

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

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

[Bug 1388169] Re: Keyboard Input Methods crashes on every startup

2018-12-14 Thread Ákos Gavallér
Now, I also found this bug for vscode when minimizing, so it's not a
chrome related bug I guess.

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

Title:
  Keyboard Input Methods crashes on every startup

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1388169/+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

2018-12-14 Thread VanVan
Thanks to craig-jackson if you want to check before compiling your
kernel if you have the same problem that I had, you can check if the
sound can work for a few seconds with the command below :


sudo apt install git
git clone https://github.com/VanVan/check_sound.git
sudo ./check_sound/check_sound

If you can hear a sound from your internal speaker it's good, if not,
compiling a new kernel can still give you sound, depends on your laptop.


When you compile a new kernel, do not forget do to a git pull inside the linux 
folder or you can remove and clone again the repository to have the latest 
commit (hda_codec.h correction):
git clone https://github.com/VanVan/linux.git

-- 
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 1388169] Re: Keyboard Input Methods crashes on every startup

2018-12-14 Thread Ákos Gavallér
I've just installed chrome on ubuntu, but I faced this issue. I can
change url for first time, but after the first site is loaded it
freezes, if a change the language back and forth, it starts working tho.

Ubuntu version: Ubuntu 18.04.1 LTS
Chrome version: Version 70.0.3538.110 (Official Build) (64-bit)

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

Title:
  Keyboard Input Methods crashes on every startup

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

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

[Bug 1798597] Please test proposed package

2018-12-14 Thread Adam Conrad
Hello Timo, or anyone else affected,

Accepted xserver-xorg-video-dummy-hwe-18.04 into bionic-proposed. The
package will build now and be available at
https://launchpad.net/ubuntu/+source/xserver-xorg-video-dummy-
hwe-18.04/1:0.3.8-1build3~18.04.1 in a few hours, and then in the
-proposed repository.

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

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

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

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

** Also affects: xserver-xorg-video-dummy-hwe-18.04 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: xserver-xorg-video-dummy-hwe-18.04 (Ubuntu)
   Status: New => Invalid

** Changed in: xserver-xorg-video-dummy-hwe-18.04 (Ubuntu Bionic)
   Status: New => Fix Committed

** Changed in: xserver-xorg-video-dummy-hwe-18.04 (Ubuntu Bionic)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  Backport packages for 18.04.2 HWE stack

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

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

[Bug 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

2018-12-14 Thread Richard Baka
siyia (siyia), e-mail has been sent.

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

Title:
  Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't
  load, kernel freeze  (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash

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

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

[Bug 1808168] Re: Neutron FWaaS panel missing from dashboard on Queens

2018-12-14 Thread James Page
** Summary changed:

- Neutron FwaaS GUI panel missing from dashboard on Queens
+ Neutron FWaaS panel missing from dashboard on Queens

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

Title:
  Neutron FWaaS panel missing from dashboard on Queens

To manage notifications about this bug go to:
https://bugs.launchpad.net/charm-openstack-dashboard/+bug/1808168/+subscriptions

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

<    1   2   3   4   5   >