date:20180531

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

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

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

Title:
  Ubuntu Bionic vi/vim not working correctly

Status in vim package in Ubuntu:
  Confirmed

Bug description:
  The vim default configuration in Bionic does not match Ubuntu 17.10
  nor Centos 7 and is hard to use. It auto-inserts tabs or spaces, and
  the '/' search mode command works differently (pressing enter is
  required before you can use cursors left/right).

  For some discussion, please see
  https://askubuntu.com/questions/1026820/vi-vim-usage-in-ubuntu-bionic-
  not-normal/1028684#1028684

  Setting :set nocompatbile in ~/.vimrc fixes it, but this should not be
  required.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

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

2018-05-31 Thread Thiago Martins

Thanks! vim on Ubuntu 18.04 is so annoying!  lol

The workaround is good!

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

Title:
  Ubuntu Bionic vi/vim not working correctly

Status in vim package in Ubuntu:
  Confirmed

Bug description:
  The vim default configuration in Bionic does not match Ubuntu 17.10
  nor Centos 7 and is hard to use. It auto-inserts tabs or spaces, and
  the '/' search mode command works differently (pressing enter is
  required before you can use cursors left/right).

  For some discussion, please see
  https://askubuntu.com/questions/1026820/vi-vim-usage-in-ubuntu-bionic-
  not-normal/1028684#1028684

  Setting :set nocompatbile in ~/.vimrc fixes it, but this should not be
  required.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1706939] Re: A live session can't be shut down due to "[ *** ] (2 of 2) A start job is running for ... (22s / no limit)"

2018-05-31 Thread Daniel van Vugt

Using cosmic image 20180530, I can still see the error briefly. But in
less than a second it's now replaced with a black terminal screen saying
just:

  "Please remove the installation medium, then reboot."

So no, pressing Enter does not cause the system to reboot. I have to use
the power button.

No, I do not see any purple screen.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1706939

Title:
  A live session can't be shut down due to "[ ***  ] (2 of 2) A start
  job is running for ... (22s / no limit)"

Status in Release Notes for Ubuntu:
  Fix Released
Status in casper package in Ubuntu:
  New
Status in gdm3 package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in casper source package in Bionic:
  New
Status in gdm3 source package in Bionic:
  Confirmed

Bug description:
  Test case:
  Boot to live session using current or recent image
  Attempt to restart, shutdown or even log out.
  Hangs basically forever with:

  [ ***  ] (2 of 2) A start job is running for Hold until boot process
  finishes up (21s / no limit)

  or

  [ *** ] (2 of 2) A start job is running for Wait for Network to be
  Configured (21s / no limit)

  ---
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gdm3 3.24.2-1ubuntu9
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: GNOME
  Date: Thu Jul 27 10:15:57 2017
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170723)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2017-07-27T10:13:04.127685

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1774542] [NEW] [HDA-Intel - HDA ATI SB, playback] fails after a while

2018-05-31 Thread David LaPointe

Public bug reported:

Audio output of last item in the Sound->Applications list is turned off
by (possibly) any new process that enables sound. I observed this
behaviour by playing a Video while using Chrome or Firefox. A Teamspeak
notification also seemed to mute sound in the Video.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu May 31 20:37:29 2018
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: USB headset BSF - USB headset BSF
Symptom_PulseAudioLog:
 May 30 20:17:36 ftl dbus-daemon[789]: [system] Activating via systemd: service 
name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by 
':1.47' (uid=120 pid=1376 comm="/usr/bin/pulseaudio --daemonize=no " 
label="unconfined")
 May 30 20:17:37 ftl pulseaudio[1376]: W: [pulseaudio] sink.c: Default and 
alternate sample rates are the same.
 May 30 20:17:37 ftl pulseaudio[1376]: W: [pulseaudio] source.c: Default and 
alternate sample rates are the same.
 May 30 20:17:38 ftl dbus-daemon[789]: [system] Activating via systemd: service 
name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.79' (uid=120 
pid=1376 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined")
Symptom_Type: Sound works for a while, then breaks
Title: [HDA-Intel - HDA ATI SB, playback] fails after a while
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/23/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0603
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M4A88T-M/USB3
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0603:bd08/23/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A88T-M/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1774542

Title:
  [HDA-Intel - HDA ATI SB, playback] fails after a while

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Audio output of last item in the Sound->Applications list is turned
  off by (possibly) any new process that enables sound. I observed this
  behaviour by playing a Video while using Chrome or Firefox. A
  Teamspeak notification also seemed to mute sound in the Video.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 31 20:37:29 2018
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: USB headset BSF - USB headset BSF
  Symptom_PulseAudioLog:
   May 30 20:17:36 ftl dbus-daemon[789]: [system] Activating via systemd: 
service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' 
requested by ':1.47' (uid=120 pid=1376 comm="/usr/bin/pulseaudio --daemonize=no 
" label="unconfined")
   May 30 20:17:37 ftl pulseaudio[1376]: W: [pulseaudio] sink.c: Default and 
alternate sample rates are the same.
   May 30 20:17:37 ftl pulseaudio[1376]: W: [pulseaudio] source.c: Default and 
alternate sample rates are the same.
   May 30 20:17:38 ftl dbus-daemon[789]: [system] Activating via systemd: 
service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.79' 
(uid=120 pid=1376 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined")
  Symptom_Type: Sound works for a while, then breaks
  Title: [HDA-Intel - HDA ATI SB, playback] fails after a while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/23/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0603
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M4A88T-M/USB3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag:

[Touch-packages] [Bug 1656100] Re: Unable to remove signing keys using gnome-software-properties

2018-05-31 Thread Paul White

** Tags added: bionic cosmic

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1656100

Title:
  Unable to remove signing keys using gnome-software-properties

Status in Ubuntu GNOME:
  Invalid
Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  I have found that on Ubuntu GNOME 16.10 with GNOME 3.22 that I am
  unable to remove signing keys in the Authentication tab. If I select a
  key I wish to remove and click the Remove button, either nothing will
  happen, or it will ask me for authentication, upon giving it the
  correct password all that will happen is it will deselect the key I
  select, but at no point will it actually remove it, which is rather
  annoying.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: software-properties-gtk 0.96.24.7
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Jan 12 21:35:55 2017
  InstallationDate: Installed on 2017-01-09 (3 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1756238] Re: gdebi-gtk broken in 18.04 error: unable to read filedescriptor flags

2018-05-31 Thread Iain Lane

This bug is Fix Released in bionic. The reference is only included in
LP-Bugs-Fixed because I copied the previous merge entry and then built
the source package with -v. Sorry that that's confusing.

(bug #1765389 is actually missing SRU information and I pinged Rico to
add it.)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdebi in Ubuntu.
https://bugs.launchpad.net/bugs/1756238

Title:
  gdebi-gtk broken in 18.04 error: unable to read filedescriptor flags

Status in gdebi package in Ubuntu:
  Triaged
Status in vte2.91 package in Ubuntu:
  Fix Released

Bug description:
  When using gdebi-gtk to install a .deb the install fails with the
  message:-

  dpkg: error: unable to read filedescriptor flags for : Bad file descriptor

  This only occurs via the gdebi-gtk GUI front end, packages install perfectly 
if done via the CLI with:
  sudo gdebi /path/to/packagename.deb

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1615381] Re: apt-get autoremove may remove current kernel

2018-05-31 Thread Eric Desrochers

** Tags added: sts

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1615381

Title:
  apt-get autoremove may remove current kernel

Status in apt package in Ubuntu:
  Won't Fix
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in apt source package in Trusty:
  Won't Fix
Status in unattended-upgrades source package in Trusty:
  New
Status in apt source package in Xenial:
  Won't Fix
Status in unattended-upgrades source package in Xenial:
  Confirmed
Status in apt source package in Artful:
  Won't Fix
Status in unattended-upgrades source package in Artful:
  New

Bug description:
  This may happen, if you boot one of the older kernels, that is not
  protected by /etc/apt/apt.conf.d/01autoremove-kernels

  Workaround: run
  /etc/kernel/postinst.d/apt-auto-removal
  during each boot (e.g. by using cron).
  Note: The workaround breaks autoremoving feature of new unneeded kernels in  
unattended-upgrades i.e. the setting 
'Unattended-Upgrade::Remove-New-Unused-Dependencies "true"' (which is default 
in 16.04 unless 'Unattended-Upgrade::Remove-Unused-Dependencies "true"' is set 
in '/etc/apt/apt.conf.d/50unattended-upgrades'.

  
  In shell:

  $ uname -r
  4.4.0-22-generic
  $ apt-get -s autoremove
  NOTE: This is only a simulation!
    apt-get needs root privileges for real execution.
    Keep also in mind that locking is deactivated,
    so don't depend on the relevance to the real current situation!
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  The following packages will be REMOVED:
    linux-headers-4.4.0-21 linux-headers-4.4.0-21-generic linux-headers-4.4.0-22
    linux-headers-4.4.0-22-generic linux-headers-4.4.0-31-generic
    linux-image-4.4.0-21-generic linux-image-4.4.0-22-generic
    linux-image-4.4.0-31-generic linux-image-extra-4.4.0-21-generic
    linux-image-extra-4.4.0-22-generic linux-image-extra-4.4.0-31-generic
  0 upgraded, 0 newly installed, 11 to remove and 13 not upgraded.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.12~ubuntu16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Aug 21 16:11:27 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-28 (114 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.kernel.postinst.d.apt-auto-removal: [modified]
  mtime.conffile..etc.kernel.postinst.d.apt-auto-removal: 
2016-07-30T12:15:32.706300

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1702793] Re: Full backport SRU for unattended-upgrades

2018-05-31 Thread Eric Desrochers

** Tags added: sts

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1702793

Title:
  Full backport SRU for unattended-upgrades

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

  * I would like to propose a one-off full backport of unattended-upgrades
  1.2ubuntu1 to Bionic, Artful, Xenial and possibly Trusty releases because 
selectively backporting fixes for crashes and for issues that made u-u 
unreliable would be more risky thanks to the huge number of fixes and the
  inter-dependencies between them.

  [Test Case]

  * Since this backport involves fixing several bugs and this bug itself covers 
the full backport I suggest that this bug should be considered verified when 
the following list of bugs are verified:
   - TODO add most important bugs
  and the following tests are passing:
   - TODO add tests not covered by bugs above

  [Regression Potential]

  * Due to this update covering the full backport unattended-upgrades can 
regress in any imaginable way including failing to install, upgrade, run, or 
removing essential packages from the system. Those are unlikely.
  * There are open bugs about u-u being slower than in the past, thus this may 
be a likely regression but IMO the pending speed optimizations should not be 
blocking the backport because the reliability issues are more important to fix 
and speed optimizations can be cherry-picked later.
  * LP: #1773033 is a regression causing u-u to not install upgrades on 
shutdown when the system was started on battery. I have a WIP fix and can add 
the fix to the SRU if needed.

  [Other Info]

  I asked for an exception for the package in following the SRU process:
  https://lists.ubuntu.com/archives/ubuntu-release/2018-May/004479.html

  I'm preparing the backport in ppa:rbalint/scratch and also run
  autopkgtests on it in addition to testing it manually in VMs.

  [Original Bug Text]

  Changes to support day-of-week patching and logging to syslog were
  added to upstream (https://github.com/mvo5/unattended-upgrades) over a
  year ago. These changes are not present in the latest Xenial nor
  Trusty packages (0.90 and 0.82.1) - requesting that these changes be
  pulled from upstream.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1702793/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1774499] [NEW] /usr/bin/software-properties-gtk:IndexError:check_line:init:parse

2018-05-31 Thread errors.ubuntu.com bug bridge

Public bug reported:

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

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: artful bionic precise quantal raring saucy trusty vivid wily xenial 
yakkety zesty

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1774499

Title:
  /usr/bin/software-properties-gtk:IndexError:check_line:__init__:parse

Status in software-properties package in Ubuntu:
  New

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1774499/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1774491] Re: pkcon install fails -- proxy?

2018-05-31 Thread Matthias Klumpp

This very much looks like a bug int Aptdaemon's PK compatibility layer
to me. At this point, it likely makes no sense to fix this issue, since
that code has been dropped after the Xenial release.

@tlc: This will likely be a won't fix bug, please upgrade to Bionic if you can. 
If you can't upgrade, you can try to switch from the compat layer to the real 
PK daemon, if the system allows you to do that:
sudo apt purge python3-aptdaemon.pkcompat  ; sudo apt install packagekit


** Package changed: packagekit (Ubuntu) => aptdaemon (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1774491

Title:
  pkcon install fails -- proxy?

Status in aptdaemon package in Ubuntu:
  New

Bug description:
  Xenial Desktop.  I am behind a proxy but have no idea how to configure a 
proxy for pkcon.
  Proxies are set and working in /etc/environment and /etc/apt

  
   $ sudo apt-get install packagekit-tools 

   $ pkcon install pianobar
  Command failed: The proxy could not be set: 
GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Traceback (most recent 
call last):
File "/usr/lib/python3/dist-packages/dbus/service.py", line 654, in 
_message_cb
  (candidate_method, parent_method) = _method_lookup(self, method_name, 
interface_name)
File "/usr/lib/python3/dist-packages/dbus/service.py", line 246, in 
_method_lookup
  raise UnknownMethodException('%s is not a valid method of interface %s' % 
(method_name, dbus_interface))
  dbus.exceptions.UnknownMethodException: 
org.freedesktop.DBus.Error.UnknownMethod: Unknown method: SetProxy is not a 
valid method of interface org.freedesktop.PackageKit

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: packagekit-tools 0.8.17-4ubuntu6~gcc5.4ubuntu1.2
  ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117
  Uname: Linux 4.4.0-124-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu May 31 15:39:40 2018
  InstallationDate: Installed on 2015-01-08 (1239 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: packagekit
  UpgradeStatus: Upgraded to xenial on 2016-09-23 (615 days ago)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1755456] Re: [ffe] Optional recording/sending of installer details to help improving Ubuntu

Hello Sebastien, or anyone else affected,

Accepted ubuntu-release-upgrader into bionic-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/ubuntu-release-upgrader/1:18.04.19 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!

** Changed in: ubuntu-release-upgrader (Ubuntu Bionic)
   Status: Triaged => Fix Committed

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1755456

Title:
  [ffe] Optional recording/sending of installer details to help
  improving Ubuntu

Status in gnome-initial-setup package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader source package in Bionic:
  Fix Committed

Bug description:
  [Rationale]
  We added telemetry data for people installing ubuntu from ubiquity. We didn't 
get the time to do the same on upgrade despite the FFe acking it. It was 
decided it was better to first polish the installation and report experience, 
and then, tackling the upgrade for .1, where most LTS users will migrate from.

  ubuntu-release-upgrade just drop a telemetry file (like ubiquity is
  dropping one) which is then picked up by ubuntu-report for user's
  review and approval before sending.

  Note that ubuntu-report is already aware of the upgrade telemetry and
  just ignores it when it's missing it (case of install of ugprade
  without this ubuntu-release-upgrade versinon)

  [Impact]
   * ubuntu-release-upgrade just drop a telemetry file (like ubiquity is 
dropping one) which is then picked up by ubuntu-report for user's review and 
approval before sending.
   * Note that ubuntu-report is already aware of the upgrade telemetry and just 
ignores it when it's missing it (case of install of ugprade without this 
ubuntu-release-upgrade versinon)
   * The ubuntu-release-upgrade only drops a file thus. The logic is really 
similar to the one included in ubiquity for 18.04. The telemetry class is 
similar.
   * The telemetry is reported by all existing UI.
   * What we send is:
 - From (distro we ugprade from)
 - Type of installer (GTK, KDE, non interactive, text…)
 - If third party ressources were used (but not the list of those external 
repos)
 - Original installation media
 - Stages of installation indexed by their relative time duration

  
  [Test Case]
   * Install ubuntu-release-upgrade on an artful machine
   * Run an upgrade from artful to bionic
   * Check that once the upgrade finished, there is a 
/var/log/ugprade/telemetry file present on disk.

  [Regression Potential]

   * The code is similar to ubiquity ones, and the impact is only dropping a 
file on disk.
   * Preliminary testing has been done on 17.04 -> 18.04 upgrade, in text mode, 
GTK3 and KDE frontends.

  ---

  The topic has been discussed on the ubuntu-devel@ list, see
  https://lists.ubuntu.com/archives/ubuntu-
  devel/2018-February/040139.html

  The feature has different parts
  - the installer is going to record some informations about the installation 
details & options selected
  - the session is going to have a command line/GUI part that let user 
review those informations
  - the desktop settings should have a control to change the option later on

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1774491] [NEW] pkcon install fails -- proxy?

2018-05-31 Thread tlc

Public bug reported:

Xenial Desktop.  I am behind a proxy but have no idea how to configure a proxy 
for pkcon.
Proxies are set and working in /etc/environment and /etc/apt


 $ sudo apt-get install packagekit-tools 

 $ pkcon install pianobar
Command failed: The proxy could not be set: 
GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Traceback (most recent 
call last):
  File "/usr/lib/python3/dist-packages/dbus/service.py", line 654, in 
_message_cb
(candidate_method, parent_method) = _method_lookup(self, method_name, 
interface_name)
  File "/usr/lib/python3/dist-packages/dbus/service.py", line 246, in 
_method_lookup
raise UnknownMethodException('%s is not a valid method of interface %s' % 
(method_name, dbus_interface))
dbus.exceptions.UnknownMethodException: 
org.freedesktop.DBus.Error.UnknownMethod: Unknown method: SetProxy is not a 
valid method of interface org.freedesktop.PackageKit

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: packagekit-tools 0.8.17-4ubuntu6~gcc5.4ubuntu1.2
ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117
Uname: Linux 4.4.0-124-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CurrentDesktop: Unity
Date: Thu May 31 15:39:40 2018
InstallationDate: Installed on 2015-01-08 (1239 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
SourcePackage: packagekit
UpgradeStatus: Upgraded to xenial on 2016-09-23 (615 days ago)

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


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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to packagekit in Ubuntu.
https://bugs.launchpad.net/bugs/1774491

Title:
  pkcon install fails -- proxy?

Status in packagekit package in Ubuntu:
  New

Bug description:
  Xenial Desktop.  I am behind a proxy but have no idea how to configure a 
proxy for pkcon.
  Proxies are set and working in /etc/environment and /etc/apt

  
   $ sudo apt-get install packagekit-tools 

   $ pkcon install pianobar
  Command failed: The proxy could not be set: 
GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Traceback (most recent 
call last):
File "/usr/lib/python3/dist-packages/dbus/service.py", line 654, in 
_message_cb
  (candidate_method, parent_method) = _method_lookup(self, method_name, 
interface_name)
File "/usr/lib/python3/dist-packages/dbus/service.py", line 246, in 
_method_lookup
  raise UnknownMethodException('%s is not a valid method of interface %s' % 
(method_name, dbus_interface))
  dbus.exceptions.UnknownMethodException: 
org.freedesktop.DBus.Error.UnknownMethod: Unknown method: SetProxy is not a 
valid method of interface org.freedesktop.PackageKit

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: packagekit-tools 0.8.17-4ubuntu6~gcc5.4ubuntu1.2
  ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117
  Uname: Linux 4.4.0-124-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu May 31 15:39:40 2018
  InstallationDate: Installed on 2015-01-08 (1239 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: packagekit
  UpgradeStatus: Upgraded to xenial on 2016-09-23 (615 days ago)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1756238] Missing SRU information

Thanks for uploading the fix for this bug report to -proposed.  However,
when reviewing the package in -proposed and the details of this bug
report I noticed that the bug description is missing information
required for the SRU process.  You can find full details at
http://wiki.ubuntu.com/StableReleaseUpdates#Procedure but essentially
this bug is missing some of the following: a statement of impact, a test
case and details regarding the regression potential.  Thanks in advance!

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdebi in Ubuntu.
https://bugs.launchpad.net/bugs/1756238

Title:
  gdebi-gtk broken in 18.04 error: unable to read filedescriptor flags

Status in gdebi package in Ubuntu:
  Triaged
Status in vte2.91 package in Ubuntu:
  Fix Released

Bug description:
  When using gdebi-gtk to install a .deb the install fails with the
  message:-

  dpkg: error: unable to read filedescriptor flags for : Bad file descriptor

  This only occurs via the gdebi-gtk GUI front end, packages install perfectly 
if done via the CLI with:
  sudo gdebi /path/to/packagename.deb

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1476769]

2018-05-31 Thread Jan

This bug has been reported against a Fedora version which is already unsuported.
In compliance with FESCo decision how to handle EOL of Security issues [1],
I am changing the version to '27', the latest supported release.

Please check whether this bug is still an issue on the '27' release.
If you find this bug not being applicable on this release, please close it.

[1] https://pagure.io/fesco/issue/1736

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1476769

Title:
  When activating OpenVPN without DHCP6, random traffic will be routed
  without VPN

Status in network-manager package in Ubuntu:
  Confirmed
Status in openvpn package in Ubuntu:
  Confirmed
Status in Fedora:
  Confirmed

Bug description:
  When activating an OpenVPN without DHCP6 through NetworkManager,
  random traffic will be routed without VPN if the basic physical
  network device has IPv6 connectivity but the VPN hasn't. This is a
  security issue, since a user activating the VPN would expect all go
  through it.

  network-manager package version: 0.9.10.0-4ubuntu15.1

  Steps to reproduce:
  1. Find some VPN without IPv6 routing or DHCP6. Get the according openvpn 
configuration file and import into NetworkManager
  2. Make sure your physical networking device has native IPv6 access
  3. Activate the VPN in the network settings

  Expected result:

   * IPv4 default route through VPN
   * IPv6 default route absent (as VPN doesn't provide any)

  Actual result (as I understand the bug report):

   * IPv4 default route through VPN (good)
   * IPv6 default route via local gateway (bad)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: openvpn 2.3.2-9ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
  Uname: Linux 3.19.0-21-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jul 21 19:21:50 2015
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: openvpn
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1476769]

2018-05-31 Thread Didier

Still present in Fedora 27

If VPN server does not provide IPv6 support, IPv6 traffic is not blocked
but routed outside of the VPN.

This is definitely a VPN leak.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1476769

Title:
  When activating OpenVPN without DHCP6, random traffic will be routed
  without VPN

Status in network-manager package in Ubuntu:
  Confirmed
Status in openvpn package in Ubuntu:
  Confirmed
Status in Fedora:
  Confirmed

Bug description:
  When activating an OpenVPN without DHCP6 through NetworkManager,
  random traffic will be routed without VPN if the basic physical
  network device has IPv6 connectivity but the VPN hasn't. This is a
  security issue, since a user activating the VPN would expect all go
  through it.

  network-manager package version: 0.9.10.0-4ubuntu15.1

  Steps to reproduce:
  1. Find some VPN without IPv6 routing or DHCP6. Get the according openvpn 
configuration file and import into NetworkManager
  2. Make sure your physical networking device has native IPv6 access
  3. Activate the VPN in the network settings

  Expected result:

   * IPv4 default route through VPN
   * IPv6 default route absent (as VPN doesn't provide any)

  Actual result (as I understand the bug report):

   * IPv4 default route through VPN (good)
   * IPv6 default route via local gateway (bad)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: openvpn 2.3.2-9ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
  Uname: Linux 3.19.0-21-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jul 21 19:21:50 2015
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: openvpn
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1476769]

2018-05-31 Thread Jonas

Was this ever fixed? I currently don't have a VPN configured, but this
is quite a dangerous issue (for people who rely on VPN privacy with
their life which isn't unheard of) so it shouldn't just get lost.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1476769

Title:
  When activating OpenVPN without DHCP6, random traffic will be routed
  without VPN

Status in network-manager package in Ubuntu:
  Confirmed
Status in openvpn package in Ubuntu:
  Confirmed
Status in Fedora:
  Confirmed

Bug description:
  When activating an OpenVPN without DHCP6 through NetworkManager,
  random traffic will be routed without VPN if the basic physical
  network device has IPv6 connectivity but the VPN hasn't. This is a
  security issue, since a user activating the VPN would expect all go
  through it.

  network-manager package version: 0.9.10.0-4ubuntu15.1

  Steps to reproduce:
  1. Find some VPN without IPv6 routing or DHCP6. Get the according openvpn 
configuration file and import into NetworkManager
  2. Make sure your physical networking device has native IPv6 access
  3. Activate the VPN in the network settings

  Expected result:

   * IPv4 default route through VPN
   * IPv6 default route absent (as VPN doesn't provide any)

  Actual result (as I understand the bug report):

   * IPv4 default route through VPN (good)
   * IPv6 default route via local gateway (bad)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: openvpn 2.3.2-9ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
  Uname: Linux 3.19.0-21-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jul 21 19:21:50 2015
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: openvpn
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1476769]

2018-05-31 Thread Fedora

This message is a reminder that Fedora 25 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 25. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '25'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 25 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1476769

Title:
  When activating OpenVPN without DHCP6, random traffic will be routed
  without VPN

Status in network-manager package in Ubuntu:
  Confirmed
Status in openvpn package in Ubuntu:
  Confirmed
Status in Fedora:
  Confirmed

Bug description:
  When activating an OpenVPN without DHCP6 through NetworkManager,
  random traffic will be routed without VPN if the basic physical
  network device has IPv6 connectivity but the VPN hasn't. This is a
  security issue, since a user activating the VPN would expect all go
  through it.

  network-manager package version: 0.9.10.0-4ubuntu15.1

  Steps to reproduce:
  1. Find some VPN without IPv6 routing or DHCP6. Get the according openvpn 
configuration file and import into NetworkManager
  2. Make sure your physical networking device has native IPv6 access
  3. Activate the VPN in the network settings

  Expected result:

   * IPv4 default route through VPN
   * IPv6 default route absent (as VPN doesn't provide any)

  Actual result (as I understand the bug report):

   * IPv4 default route through VPN (good)
   * IPv6 default route via local gateway (bad)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: openvpn 2.3.2-9ubuntu4
  ProcVersionSignature: Ubuntu 3.19.0-21.21-generic 3.19.8
  Uname: Linux 3.19.0-21-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Jul 21 19:21:50 2015
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: openvpn
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1774486] [NEW] graphic chip

2018-05-31 Thread SherifALi

Public bug reported:

i didnt know how to install my intel chip 3000 hd

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu May 31 21:05:34 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0402] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core 
Processor Integrated Graphics Controller [1458:d000]
InstallationDate: Installed on 2018-05-24 (7 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: Gigabyte Technology Co., Ltd. H81M-S2PH
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=91ec5cbc-f46b-4c99-9d84-78001db6db6b ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/10/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: FC
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: H81M-S2PH
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFC:bd11/10/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-S2PH:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-S2PH:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: H81M-S2PH
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1774486

Title:
  graphic chip

Status in xorg package in Ubuntu:
  New

Bug description:
  i didnt know how to install my intel chip 3000 hd

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 31 21:05:34 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0402] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core 
Processor Integrated Graphics Controller [1458:d000]
  InstallationDate: Installed on 2018-05-24 (7 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Gigabyte Technology Co., Ltd. H81M-S2PH
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=91ec5cbc-f46b-4c99-9d84-78001db6db6b ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/10/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FC
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-S2PH
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias:

[Touch-packages] [Bug 1759468] Re: gnome-control-center (11) gtk_style_context_clear_property_cache → gtk_css_widget_node_update_style → gtk_css_node_ensure_style → gtk_css_node_ensure_style → gtk_css

Hello errors.ubuntu.com, or anyone else affected,

Accepted gnome-control-center into bionic-proposed. The package will
build now and be available at https://launchpad.net/ubuntu/+source
/gnome-control-center/1:3.28.1-0ubuntu1.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!

** Changed in: gnome-control-center (Ubuntu Bionic)
   Status: New => Fix Committed

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1759468

Title:
  gnome-control-center (11) gtk_style_context_clear_property_cache →
  gtk_css_widget_node_update_style → gtk_css_node_ensure_style →
  gtk_css_node_ensure_style → gtk_css_node_validate_internal

Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Bionic:
  Fix Committed

Bug description:
  * Impact
  gnome-control-center sometimes hits a segfault

  * Test case
  - Check if the e.u.c reports stop with the new version

  or

  - Open GNOME Control Center
  - Go to Devices->Display panel
  - Close the window
  - Open GNOME Control Center again (in overview mode) 

  the settings should open without error

  * Regression potential
  check the panels can be opened without error and that switching between them 
works as well

  --

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

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1755863] Re: netbooting the bionic live CD over NFS goes straight to maintenance mode :

2018-05-31 Thread Martin Bogomolni

The "toram" workaround does not work for me attempting to boot on a
SuperMicro X10DRW motherboard with 128GB of ram installed + SATA SSD.  I
have also added Woodrow Shen's workaround in the command line.

The difference is that I am attempting to install 18.04 server.

Environment is:

Debian "Wheezy" server runnig dnsmasq to provide DHCP and tftp service
Synced/mirrored Ubuntu 18.04 repository being served via nginx

-

May 29 18:08:13 ubuntu systemd[1]: dev-mqueue.mount: Mount process finished, 
but there is no mount.
May 29 18:08:13 ubuntu systemd[1]: dev-mqueue.mount: Failed with result 
'protocol'.
May 29 18:08:13 ubuntu systemd[1]: Failed to mount POSIX Message Queue File 
System.
-- Subject: Unit dev-mqueue.mount has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit dev-mqueue.mount has failed.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1755863

Title:
  netbooting the bionic live CD over NFS goes straight to maintenance
  mode :

Status in casper package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  netbooting the bionic live CD[1] over NFS goes straight to maintenance
  mode :

  [1] http://cdimage.ubuntu.com/daily-live/current/

  # casper.log
  Begin: Adding live session user... ... dbus-daemon[568]: [session uid=999 
pid=568] Activating service name='org.gtk.vfs.Daemon' requested by ':1.0' 
(uid=999 pid=569 comm="" label="unconfined")
  dbus-daemon[568]: [session uid=999 pid=568] Successfully activated service 
'org.gtk.vfs.Daemon'
  dbus-daemon[568]: [session uid=999 pid=568] Activating service 
name='org.gtk.vfs.Metadata' requested by ':1.0' (uid=999 pid=569 comm="" 
label="unconfined")
  fuse: device not found, try 'modprobe fuse' first
  dbus-daemon[568]: [session uid=999 pid=568] Successfully activated service 
'org.gtk.vfs.Metadata'

  (gvfsd-metadata:580): GUdev-CRITICAL **: 16:28:56.270:
  g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)'
  failed

  (gvfsd-metadata:580): GUdev-CRITICAL **: 16:28:56.270: 
g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed
  A connection to the bus can't be made
  done.
  Begin: Setting up init... ... done.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1774462] [NEW] nividi drivers

2018-05-31 Thread Krzysztof Wierzbicki

Public bug reported:

nvidia drivers fuck up total bullshit noting woks in laptop that was
purchestwit ubunt 14.04 simple sudo apt full-upgrade distrosit

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.13.0-149.199-generic 3.13.11-ckt39
Uname: Linux 3.13.0-149-generic x86_64
NonfreeKernelModules: bbswitch nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  396.24  Thu Apr 26 00:10:09 
PDT 2018
 GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.4)
ApportVersion: 2.14.1-0ubuntu3.28
Architecture: amd64
Date: Thu May 31 19:04:47 2018
DistUpgraded: Fresh install
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-trusty-amd64-20140620-0
DistroCodename: trusty
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:06ae]
   Subsystem: Dell Device [1028:06ae]
InstallationDate: Installed on 2015-07-22 (1044 days ago)
InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
MachineType: Dell Inc. Inspiron 5558
ProcEnviron:
 PATH=(custom, no user)
 LANG=pl_PL.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-149-generic 
root=UUID=704f2fc5-97f6-46db-8498-c4dc3400a4e2 ro drm.debug=0xe plymouth:debug 
quiet splash radeon.modeset=0 nouveau.modeset=0
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/14/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A03
dmi.board.name: 086DKN
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd07/14/2015:svnDellInc.:pnInspiron5558:pvr01:rvnDellInc.:rn086DKN:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Inspiron 5558
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6
version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.11
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.7
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2
xserver.bootTime: Thu May 31 18:58:57 2018
xserver.configfile: /etc/X11/xorg.conf
xserver.devices:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.15.1-0ubuntu2.11

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


** Tags: amd64 apport-bug trusty ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1774462

Title:
  nividi drivers

Status in xorg package in Ubuntu:
  New

Bug description:
  nvidia drivers fuck up total bullshit noting woks in laptop that was
  purchestwit ubunt 14.04 simple sudo apt full-upgrade distrosit

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-149.199-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-149-generic x86_64
  NonfreeKernelModules: bbswitch nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  396.24  Thu Apr 26 00:10:09 
PDT 2018
   GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.4)
  ApportVersion: 2.14.1-0ubuntu3.28
  Architecture: amd64
  Date: Thu May 31 19:04:47 2018
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:06ae]
 Subsystem: Dell Device [1028:06ae]
  InstallationDate: Installed on 2015-07-22 (1044 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  MachineType: Dell Inc. Inspiron 5558
  ProcEnviron:
   PATH=(custom, no user)
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine:

[Touch-packages] [Bug 1774458] Re: ubuntu-bug produces links that do not work

2018-05-31 Thread Scott Moser

I think this was user-error... I think the serial console was just messing with
me.
I'll re-open if I see it again.

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

--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1774458

Title:
ubuntu-bug produces links that do not work

Status in apport package in Ubuntu:
Invalid

Bug description:
ubuntu-bug is now producing links that do not work.
using 'ubuntu-bug' in xenial produces links that look like:

https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/0f274d36-64f2-11e8-b34a-002481e7f48a?
but the cosmic version produces links like:

https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/d4561bae-64ee-11e8-?

And the cosmic version links don't work. I suspect if I could just
guess the final 16 chars of that uuid i could make it work.

$ dpkg -S `which ubuntu-bug`
apport: /usr/bin/ubuntu-bug
$ dpkg-query --show apport
apport2.20.10-0ubuntu2

$ ubuntu-bug `which ubuntu-bug`
*** Collecting problem information

The collected information can be sent to the developers to improve the
application. This might take a few minutes.
...

*** Send problem report to the developers?

After the problem report has been sent, please fill out the form in the
automatically opened web browser.

What would you like to do? Your options are:
S: Send report (4.7 KB)
V: View report
K: Keep report file for sending later or copying to somewhere else
I: Cancel and ignore future crashes of this program version
C: Cancel
Please choose (S/V/K/I/C): S

*** Uploading problem information

The collected information is being sent to the bug tracking system.
This might take a few minutes.
92%

*** To continue, you must visit the following URL:

https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/d4561bae-
64ee-11e8-?

You can launch a browser now, or copy this URL into a browser on
another comput.

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

--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1752737] Re: [2.3.0-6434] mDNS observer problems

2018-05-31 Thread Andres Rodriguez

** Also affects: maas/2.4
   Importance: Undecided
   Status: New

** Changed in: maas
Milestone: 2.4.x => 2.5.0

** Changed in: maas/2.4
Milestone: None => 2.4.1

** Changed in: maas/2.4
   Status: New => Triaged

** Changed in: maas/2.4
   Importance: Undecided => High

** Changed in: maas
   Importance: Medium => High

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to avahi in Ubuntu.
https://bugs.launchpad.net/bugs/1752737

Title:
  [2.3.0-6434] mDNS observer problems

Status in Avahi:
  Unknown
Status in MAAS:
  Triaged
Status in MAAS 2.4 series:
  Triaged
Status in avahi package in Ubuntu:
  Confirmed

Bug description:
  I see avahi-browser choking on non-utf8 characters in my rackd.log:

  ==> rackd.log <==
  2018-02-28 16:54:33 provisioningserver.utils.services: [info] mDNS 
observation process started.
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
Traceback (most recent call last):
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
File "/usr/lib/maas/maas-common", line 87, in 
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
main()
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
File "/usr/lib/maas/maas-common", line 83, in main
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
run()
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
File "/usr/lib/maas/maas-common", line 52, in run
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
from provisioningserver.__main__ import main
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
File "/usr/lib/python3/dist-packages/provisioningserver/__main__.py", line 55, 
in 
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
main()
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
File "/usr/lib/python3/dist-packages/provisioningserver/utils/script.py", line 
91, in __call__
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
self.execute(argv)
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
File "/usr/lib/python3/dist-packages/provisioningserver/utils/script.py", line 
86, in execute
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
args.handler.run(args)
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
File "/usr/lib/python3/dist-packages/provisioningserver/utils/avahi.py", line 
221, in run
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
_observe_mdns(reader, output, args.verbose)
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
File "/usr/lib/python3/dist-packages/provisioningserver/utils/avahi.py", line 
145, in _observe_mdns
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
for event in observer(events):
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
File "/usr/lib/python3/dist-packages/provisioningserver/utils/avahi.py", line 
161, in _observe_resolver_found
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
for event in filter(_p_resolver_found, events):
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
File "/usr/lib/python3/dist-packages/provisioningserver/utils/avahi.py", line 
125, in _extract_mdns_events
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
for event in map(parse_avahi_event, lines):
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
File "/usr/lib/python3.5/codecs.py", line 321, in decode
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
(result, consumed) = self._buffer_decode(data, self.errors, final)
  2018-02-28 16:54:36 provisioningserver.utils.services: [info] observe-mdns: 
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xc8 in position 240: 
invalid continuation byte
  2018-02-28 16:54:36 provisioningserver.utils.services: [critical] mDNS 
observation process failed.

  Traceback (most recent call last):
  Failure: twisted.internet.error.ProcessTerminated: A process has ended with a 
probable error condition: process ended with exit code 1.

  ==> regiond.log <==
  2018-02-28 16:54:50 regiond: [info] ::1 GET /MAAS/rpc/ HTTP/1.0 --> 200 OK 
(referrer: -; agent: provisioningserver.rpc.clusterservice.ClusterClientService)
  2018-02-28 16:55:20 regiond: [info] ::1 GET /MAAS/rpc/ HTTP/1.0 --> 200 OK 
(referrer: -; agent: provisioningserver.rpc.clusterservice.ClusterClientService)

  ==> maas.log <==
  Feb 28 16:53:52 MAAS-RC01 maas.interface: [info] ens33 (physical) on 
MAAS-RC01: New MAC, IP binding observed: 08:eb:74:ca:d3:6f, 192.168.1.82

  Similar traceback when running from

[Touch-packages] [Bug 1774458] [NEW] ubuntu-bug produces links that do not work

2018-05-31 Thread Scott Moser

Public bug reported:

ubuntu-bug is now producing links that do not work.
using 'ubuntu-bug' in xenial produces links that look like:

https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/0f274d36-64f2-11e8-b34a-002481e7f48a?
but the cosmic version produces links like:
https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/d4561bae-64ee-11e8-?

And the cosmic version links don't work. I suspect if I could just guess
the final 16 chars of that uuid i could make it work.

$ dpkg -S `which ubuntu-bug`
apport: /usr/bin/ubuntu-bug
$ dpkg-query --show apport
apport 2.20.10-0ubuntu2

$ ubuntu-bug `which ubuntu-bug`
*** Collecting problem information

The collected information can be sent to the developers to improve the
application. This might take a few minutes.
...

*** Send problem report to the developers?

After the problem report has been sent, please fill out the form in the
automatically opened web browser.

*** Uploading problem information

The collected information is being sent to the bug tracking system.
This might take a few minutes.
92%

*** To continue, you must visit the following URL:

https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/d4561bae-
64ee-11e8-?

You can launch a browser now, or copy this URL into a browser on another
comput.

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

--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1774458

Title:
ubuntu-bug produces links that do not work

Status in apport package in Ubuntu:
New

Bug description:
ubuntu-bug is now producing links that do not work.
using 'ubuntu-bug' in xenial produces links that look like:

https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/0f274d36-64f2-11e8-b34a-002481e7f48a?
but the cosmic version produces links like:

https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/d4561bae-64ee-11e8-?

And the cosmic version links don't work. I suspect if I could just
guess the final 16 chars of that uuid i could make it work.

$ dpkg -S `which ubuntu-bug`
apport: /usr/bin/ubuntu-bug
$ dpkg-query --show apport
apport2.20.10-0ubuntu2

$ ubuntu-bug `which ubuntu-bug`
*** Collecting problem information

The collected information can be sent to the developers to improve the
application. This might take a few minutes.
...

*** Send problem report to the developers?

After the problem report has been sent, please fill out the form in the
automatically opened web browser.

*** Uploading problem information

The collected information is being sent to the bug tracking system.
This might take a few minutes.
92%

*** To continue, you must visit the following URL:

https://bugs.launchpad.net/ubuntu/+source/apport/+filebug/d4561bae-
64ee-11e8-?

You can launch a browser now, or copy this URL into a browser on
another comput.

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

--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1767283] Update Released

The verification of the Stable Release Update for netcat-openbsd has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to netcat-openbsd in Ubuntu.
https://bugs.launchpad.net/bugs/1767283

Title:
  nc doesn't support "-s IP" option

Status in netcat-openbsd package in Ubuntu:
  Fix Released
Status in netcat-openbsd source package in Bionic:
  Fix Released
Status in netcat-openbsd package in Debian:
  Fix Released

Bug description:
  [Impact]

   * This worked in former relases, so from a LTS->LTS upgraders POV it is 
 an upgrade regression
   * The impact is that local source (-s) can no more be used as before
   * The fix is backporting the fix that we made in Debian (but without all 
 the noise of the arg parsing rewrite for SRU simplicity)

  [Test Case]

   * Run with local source port, like your local SSH for example:
   $ netcat -s 127.0.0.1 127.0.0.1 22 < /dev/null

  [Regression Potential]

   * the Minimized change (compared to the big change that versions going 
 forward got) should be safe as it just allows a case that was formerly 
 forbidden in arg-parsing. Never the less there could be a regression if 
 one of those combinations causes an issue when ran where it formerly 
 just was denied on arg parse. Think a script that since Bionic fails 
 (due to this bug) but once enabled will "work" and DUE TO THAT might 
 then trigger actions that are an issue.
 Never the less, since currently in Bionic this just fails, I'd assume 
 the this is a rather theoretical risk - and being a regression to 
 former releases we should fix it to make LTS->LTS upgraders suffer 
 less.

  [Other Info]
   
   * n/a


  Hey,

  netcat shows a usage error if i try to use the "-s" option:

  Example in Bionic:

  $ netcat -s 127.0.0.1 127.0.0.1 22 < /dev/null
  usage: nc [-46CDdFhklNnrStUuvZz] [-I length] [-i interval] [-M ttl]
     [-m minttl] [-O length] [-P proxy_username] [-p source_port]
     [-q seconds] [-s source] [-T keyword] [-V rtable] [-W recvlimit] [-w 
timeout]
     [-X proxy_protocol] [-x proxy_address[:port]][destination] [port]

  Example in Xenial:

  netcat -s 127.0.0.1 127.0.0.1 22 < /dev/null
  SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.4

  Manpage shows that the option is still availible and should work. Both
  systems use openbsd netcat.

  $ type netcat
  netcat is hashed (/bin/netcat)
  $ ls -lah /bin/netcat
  lrwxrwxrwx 1 root root 24 Apr 25 21:56 /bin/netcat -> /etc/alternatives/netcat
  $ ls -lah /etc/alternatives/netcat
  lrwxrwxrwx 1 root root 15 Apr 25 21:56 /etc/alternatives/netcat -> 
/bin/nc.openbsd

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: netcat-openbsd 1.187-1
  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
  Date: Fri Apr 27 13:41:20 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libbsd0 0.8.7-1
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: netcat-openbsd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netcat-openbsd/+bug/1767283/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1767283] Re: nc doesn't support "-s IP" option

This bug was fixed in the package netcat-openbsd - 1.187-1ubuntu0.1

---
netcat-openbsd (1.187-1ubuntu0.1) bionic; urgency=medium

  * Re-enable usage of '-s' (local source address) and '-p' (local source
port) in client mode (when '-l' is unset).  Regression introduced in
a Debian-specific patch added in 1.187-1. (LP: #1767283).
Backport of https://salsa.debian.org/debian/netcat-openbsd/commit/338b1fa7

 -- Christian Ehrhardt   Mon, 14 May
2018 14:24:33 +0200

** Changed in: netcat-openbsd (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to netcat-openbsd in Ubuntu.
https://bugs.launchpad.net/bugs/1767283

Title:
  nc doesn't support "-s IP" option

Status in netcat-openbsd package in Ubuntu:
  Fix Released
Status in netcat-openbsd source package in Bionic:
  Fix Released
Status in netcat-openbsd package in Debian:
  Fix Released

Bug description:
  [Impact]

   * This worked in former relases, so from a LTS->LTS upgraders POV it is 
 an upgrade regression
   * The impact is that local source (-s) can no more be used as before
   * The fix is backporting the fix that we made in Debian (but without all 
 the noise of the arg parsing rewrite for SRU simplicity)

  [Test Case]

   * Run with local source port, like your local SSH for example:
   $ netcat -s 127.0.0.1 127.0.0.1 22 < /dev/null

  [Regression Potential]

   * the Minimized change (compared to the big change that versions going 
 forward got) should be safe as it just allows a case that was formerly 
 forbidden in arg-parsing. Never the less there could be a regression if 
 one of those combinations causes an issue when ran where it formerly 
 just was denied on arg parse. Think a script that since Bionic fails 
 (due to this bug) but once enabled will "work" and DUE TO THAT might 
 then trigger actions that are an issue.
 Never the less, since currently in Bionic this just fails, I'd assume 
 the this is a rather theoretical risk - and being a regression to 
 former releases we should fix it to make LTS->LTS upgraders suffer 
 less.

  [Other Info]
   
   * n/a


  Hey,

  netcat shows a usage error if i try to use the "-s" option:

  Example in Bionic:

  $ netcat -s 127.0.0.1 127.0.0.1 22 < /dev/null
  usage: nc [-46CDdFhklNnrStUuvZz] [-I length] [-i interval] [-M ttl]
     [-m minttl] [-O length] [-P proxy_username] [-p source_port]
     [-q seconds] [-s source] [-T keyword] [-V rtable] [-W recvlimit] [-w 
timeout]
     [-X proxy_protocol] [-x proxy_address[:port]][destination] [port]

  Example in Xenial:

  netcat -s 127.0.0.1 127.0.0.1 22 < /dev/null
  SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.4

  Manpage shows that the option is still availible and should work. Both
  systems use openbsd netcat.

  $ type netcat
  netcat is hashed (/bin/netcat)
  $ ls -lah /bin/netcat
  lrwxrwxrwx 1 root root 24 Apr 25 21:56 /bin/netcat -> /etc/alternatives/netcat
  $ ls -lah /etc/alternatives/netcat
  lrwxrwxrwx 1 root root 15 Apr 25 21:56 /etc/alternatives/netcat -> 
/bin/nc.openbsd

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: netcat-openbsd 1.187-1
  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
  Date: Fri Apr 27 13:41:20 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libbsd0 0.8.7-1
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: netcat-openbsd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netcat-openbsd/+bug/1767283/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1766740] Re: apport autopkgtest regression due to kernel packaging changes

Hello Steve, or anyone else affected,

Accepted apport into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apport/2.20.9-0ubuntu7.2 in a few
hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-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!

** Changed in: apport (Ubuntu Bionic)
   Status: In Progress => Fix Committed

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1766740

Title:
  apport autopkgtest regression due to kernel packaging changes

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Bionic:
  Fix Committed

Bug description:
  [SRU Justification]
  In bionic, linux-image-$kvers-$flavor is now built from the linux-signed 
source package on amd64, not from the linux source package.  This now causes a 
test to fail in the apport test suite:

  [...]
  ==
  FAIL: test_run_crash_kernel (__main__.T)
  run_crash() for a kernel error
  --
  Traceback (most recent call last):
    File "./test_ui.py", line 1305, in test_run_crash_kernel
  self.assertEqual(self.ui.opened_url, 'http://linux.bugs.example.com/%i' % 
se
  lf.ui.crashdb.latest_id())
  AssertionError: 'http://linux-signed.bugs.example.com/5' != 
'http://linux.bugs.e
  xample.com/5'
  - http://linux-signed.bugs.example.com/5
  ? ---
  + http://linux.bugs.example.com/5

  --
  Ran 70 tests in 79.815s

  FAILED (failures=1)
  [...]

  
(https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-
  bionic/bionic/amd64/a/apport/20180424_19_45dc8@/log.gz)

  This test needs to be fixed to know about the packaging change.

  Note that this packaging change is expected to soon be SRUed back to
  all Ubuntu releases, so apport's testsuite change should also be
  SRUed.

  [Test case]
  This passes if the autopkgtests pass.

  [Regression potential]
  The test could be changed to pass while leaving underlying issues in the 
code.  This has probably not happened here.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1766794] Re: apport-collect doesn't create a ProblemType in the report

Hello John, or anyone else affected,

Accepted apport into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apport/2.20.9-0ubuntu7.2 in a few
hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-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!

** Changed in: apport (Ubuntu Bionic)
   Status: In Progress => Fix Committed

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1766794

Title:
  apport-collect doesn't create a ProblemType in the report

Status in Apport:
  Fix Released
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Bionic:
  Fix Committed

Bug description:
  Running 'sudo apport-collect BUGID' on 18.04 and then selecting 'V:
  View report' results in Tracebacks.

  [Test Case]
  1) ssh to a system running bionic
  2) run apport-collect 1766787
  3) say yes that you want to update a bug report that isn't yours
  4) Choose to view the report
  5) Observe the following Traceback

  ERROR: hook /usr/share/apport/general-hooks/generic.py crashed:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 198, in 
_run_hook
  symb['add_info'](report, ui)
File "/usr/share/apport/general-hooks/generic.py", line 90, in add_info
  if report['ProblemType'] == 'Crash':
File "/usr/lib/python3.6/collections/__init__.py", line 991, in __getitem__
  raise KeyError(key)
  KeyError: 'ProblemType'

  With the version of the package from -proposed you will not see the
  Traceback.

  [Regression Potential]
  The change is just to stop removing the ProblemType from the created report 
so there really isn't a chance of a regression.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1769262] Re: PythonDetails contains an error message if python not installed

Hello Brian, or anyone else affected,

Accepted apport into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apport/2.20.9-0ubuntu7.2 in a few
hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-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!

** Changed in: apport (Ubuntu Bionic)
   Status: In Progress => Fix Committed

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1769262

Title:
  PythonDetails contains an error message if python not installed

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Bionic:
  Fix Committed

Bug description:
  [Test Case]
  0) ensure python is not installed on the system
  1) launch update-manager
  2) kill update-manager
  3) view the crash report

  With the version of apport in the archive you will see messy
  PythonDetails like below. With the version of apport from -proposed
  you will instead see:

  PythonDetails: N/A

  [Regression Potential]
  The fix for this also modified the code which creates Python3Details so we 
should ensure that Python3Details is not broken.

  Original Description
  
  In an Ubuntu 18.04 apport-package report, bug 1768866, we can see the 
following which looks super messy:

  PythonDetails: /root/Error: command ['which', 'python'] failed with
  exit code 1:, Error: [Errno 2] Aucun fichier ou dossier de ce type:
  "/root/Error: command ['which', 'python'] failed with exit code 1:":
  "/root/Error: command ['which', 'python'] failed with exit code 1:",
  unpackaged

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1773012] Re: kernel bugs in bionic are reported about linux-signed and package hook doesn't run

Hello Brian, or anyone else affected,

Accepted apport into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/apport/2.20.9-0ubuntu7.2 in a few
hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-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!

** Changed in: apport (Ubuntu Bionic)
   Status: In Progress => Fix Committed

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1773012

Title:
  kernel bugs in bionic are reported about linux-signed and package hook
  doesn't run

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Bionic:
  Fix Committed

Bug description:
  During the development of bionic the linux-image-$kvers-$flavor
  package was changed from being built from the linux package to the
  linux-signed package, however apport was not updated in bionic for
  this change. Subsequently, the apport package hook for linux doesn't
  run for linux-signed bug reports. Additionally, the kernel team would
  like reports about linux-signed redirected to the linux package.

  Test Case
  -
  1) In a terminal run 'ubuntu-bug linux-image-4.15.0-20-generic'
  2) In the crash report dialog observe the following:
    a) The source package is linux-signed
    b) ProcFB is not included

  With the version of the package from -proposed the source package will
  be linux and ProcFB will be included. Also test 'ubuntu-bug linux-
  image-generic' to and check to see that the crash report contains the
  same information as above.

  Regression Potential
  
  The code that redirects bugs from linux-signed to linux was written and that 
change, if it were bad, could negatively affect bugs reported about the 
linux-meta package. So it'd be good to test that process by running 'ubuntu-bug 
linux-image-generic' with the -proposed version of the package.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1774450] [NEW] bug

2018-05-31 Thread bjoern

Public bug reported:

look at summary

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..22.00.0: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/gpus/:22:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.48  Thu Mar 22 00:42:57 
PDT 2018
 GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Thu May 31 17:55:44 2018
DistUpgraded: 2018-05-11 18:46:23,230 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Kindprozess 
»./xorg_fix_proprietary.py« konnte nicht ausgeführt werden (Datei oder 
Verzeichnis nicht gefunden) (8))
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 390.48, 4.15.0-22-generic, x86_64: installed
 nvidia, 390.48, 4.15.0-23-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: ASUSTeK Computer Inc. GK106 [GeForce GTX 660] [1043:8422]
InstallationDate: Installed on 2018-02-22 (97 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: System manufacturer System Product Name
ProcEnviron:
 PATH=(custom, no user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=3487a6bb-a3c6-47ed-93c6-4c469f004ca6 ro drm.debug=0xe plymouth:debug
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2018-05-11 (19 days ago)
dmi.bios.date: 03/20/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0513
dmi.board.asset.tag: Default string
dmi.board.name: PRIME B350-PLUS
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0513:bd03/20/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Thu May 31 17:52:56 2018
xserver.configfile: default
xserver.errors: open /dev/fb0: No such file or directory
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.6-1ubuntu4

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


** Tags: amd64 apport-bug bionic ubuntu

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1774450

Title:
  bug

Status in xorg package in Ubuntu:
  New

Bug description:
  look at summary

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..22.00.0: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/gpus/:22:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.48  Thu Mar 22 00:42:57 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu May 31 17:55:44 2018
  DistUpgraded: 2018-05-11 18:46:23,230 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Kindprozess 
»./xorg_fix_proprietary.py« konnte nicht ausgeführt werden (Datei oder 
Verzeichnis nicht gefunden) (8))
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.48, 4.15.0-22-generic, x86_64: installed
   nvidia, 390.48,

[Touch-packages] [Bug 1766740] Re: apport autopkgtest regression due to kernel packaging changes

** Description changed:

- In bionic, linux-image-$kvers-$flavor is now built from the linux-signed
- source package on amd64, not from the linux source package.  This now
- causes a test to fail in the apport test suite:
+ [SRU Justification]
+ In bionic, linux-image-$kvers-$flavor is now built from the linux-signed 
source package on amd64, not from the linux source package.  This now causes a 
test to fail in the apport test suite:
  
  [...]
  ==
  FAIL: test_run_crash_kernel (__main__.T)
  run_crash() for a kernel error
  --
  Traceback (most recent call last):
    File "./test_ui.py", line 1305, in test_run_crash_kernel
  self.assertEqual(self.ui.opened_url, 'http://linux.bugs.example.com/%i' % 
se
  lf.ui.crashdb.latest_id())
  AssertionError: 'http://linux-signed.bugs.example.com/5' != 
'http://linux.bugs.e
  xample.com/5'
  - http://linux-signed.bugs.example.com/5
  ? ---
  + http://linux.bugs.example.com/5
  
  --
  Ran 70 tests in 79.815s
  
  FAILED (failures=1)
  [...]
  
  
(https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-bionic/bionic/amd64/a/apport/20180424_19_45dc8@/log.gz)
  
  This test needs to be fixed to know about the packaging change.
  
  Note that this packaging change is expected to soon be SRUed back to all
  Ubuntu releases, so apport's testsuite change should also be SRUed.
+ 
+ [Test case]
+ This passes if the autopkgtests pass.
+ 
+ [Regression potential]
+ The test could be changed to pass while leaving underlying issues in the 
code.  This has probably not happened here.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1766740

Title:
  apport autopkgtest regression due to kernel packaging changes

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Bionic:
  In Progress

Bug description:
  [SRU Justification]
  In bionic, linux-image-$kvers-$flavor is now built from the linux-signed 
source package on amd64, not from the linux source package.  This now causes a 
test to fail in the apport test suite:

  [...]
  ==
  FAIL: test_run_crash_kernel (__main__.T)
  run_crash() for a kernel error
  --
  Traceback (most recent call last):
    File "./test_ui.py", line 1305, in test_run_crash_kernel
  self.assertEqual(self.ui.opened_url, 'http://linux.bugs.example.com/%i' % 
se
  lf.ui.crashdb.latest_id())
  AssertionError: 'http://linux-signed.bugs.example.com/5' != 
'http://linux.bugs.e
  xample.com/5'
  - http://linux-signed.bugs.example.com/5
  ? ---
  + http://linux.bugs.example.com/5

  --
  Ran 70 tests in 79.815s

  FAILED (failures=1)
  [...]

  
(https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-
  bionic/bionic/amd64/a/apport/20180424_19_45dc8@/log.gz)

  This test needs to be fixed to know about the packaging change.

  Note that this packaging change is expected to soon be SRUed back to
  all Ubuntu releases, so apport's testsuite change should also be
  SRUed.

  [Test case]
  This passes if the autopkgtests pass.

  [Regression potential]
  The test could be changed to pass while leaving underlying issues in the 
code.  This has probably not happened here.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1774443] [NEW] wireless hardblocked and wireless enable button not functional

2018-05-31 Thread Nicholas Wright

Public bug reported:

Laptop is an HP Pavilion dm4-3170se. Dual booting Windows 7 and ubuntu.
In Windows, system boots with wireless disabled and then pressing the
wireless enable button twice enables WiFi.

In ubuntu, system boots with wireless disabled and wireless enable
button has no functionality either directly or in combination with the
fn-key.

Module hp_wmi may be the culprit? But disabling this has no effect on
hardblock.

reference forum post for more detailed info:
https://ubuntuforums.org/showthread.php?t=2392934=13772159#post13772159

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager 1.2.6-0ubuntu0.16.04.2
ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-43-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.17
Architecture: amd64
CurrentDesktop: Unity
Date: Thu May 31 10:32:38 2018
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2018-05-19 (11 days ago)
InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
IpRoute:
 default via 172.16.96.1 dev eno1  proto static  metric 100 
 169.254.0.0/16 dev eno1  scope link  metric 1000 
 172.16.96.0/19 dev eno1  proto kernel  scope link  src 172.16.119.109  metric 
100 
 192.17.90.180 via 172.16.96.1 dev eno1  proto dhcp  metric 100
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con:
 NAMEUUID  TYPE
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH
 Wired connection 1  0357c159-f43c-38f9-8b6f-91bb641d1712  802-3-ethernet  
1527780471  Thu 31 May 2018 10:27:51 AM CDT  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/0  yes eno1activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1
nmcli-dev:
 DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
 eno1ethernet  connected/org/freedesktop/NetworkManager/Devices/2  
Wired connection 1  0357c159-f43c-38f9-8b6f-91bb641d1712  
/org/freedesktop/NetworkManager/ActiveConnection/1 
 wlp8s0  wifi  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  
disabled  enabled  enabled

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


** Tags: amd64 apport-bug xenial

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1774443

Title:
  wireless hardblocked and wireless enable button not functional

Status in network-manager package in Ubuntu:
  New

Bug description:
  Laptop is an HP Pavilion dm4-3170se. Dual booting Windows 7 and
  ubuntu. In Windows, system boots with wireless disabled and then
  pressing the wireless enable button twice enables WiFi.

  In ubuntu, system boots with wireless disabled and wireless enable
  button has no functionality either directly or in combination with the
  fn-key.

  Module hp_wmi may be the culprit? But disabling this has no effect on
  hardblock.

  reference forum post for more detailed info:
  https://ubuntuforums.org/showthread.php?t=2392934=13772159#post13772159

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-43-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu May 31 10:32:38 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-05-19 (11 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  IpRoute:
   default via 172.16.96.1 dev eno1  proto static  metric 100 
   169.254.0.0/16 dev eno1  scope link  metric 1000 
   172.16.96.0/19 dev eno1  proto

[Touch-packages] [Bug 1774417] Re: systemd-logind: do_ypcall: clnt_call: RPC: Unable to send; errno = Operation not permitted

2018-05-31 Thread Bug Watch Updater

** Changed in: nis (Debian)
   Status: Unknown => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1774417

Title:
  systemd-logind: do_ypcall: clnt_call: RPC: Unable to send; errno =
  Operation not permitted

Status in nis package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Won't Fix
Status in nis package in Debian:
  Confirmed

Bug description:
  See upstream bug report 7074 (systemd-logind's IP sandbox breaks nss-
  nis and suchlike) [1]. Logging in takes a long time.

  May 30 13:26:25 ubuntu1804 systemd-logind[2993]: do_ypcall: clnt_call: 
RPC: Unable to send; errno = Operation not permitted
  May 30 13:26:50 ubuntu1804 sshd[3446]: pam_systemd(sshd:session): Failed 
to create session: Connection timed out

  Conclusion:

  > Please ask your downstream distribution to either:
  > 
  > 1.  include a systemd-logind.service.d/ snippet in your nss-nis package 
that turns off the IP firewalling logic for logind
  > 2.  or patching systemd-logind.service for everybody to disable it 
distro-wide (which I'd really not recommend though, compromising the security 
for everybody just because for compat of a nowadays pretty niche nss module 
that does some very questionnable things doesn't sound like the best way out to 
me)

  
  [1] https://github.com/systemd/systemd/issues/7074

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1774433] [NEW] Display on Toshiba S75-A7334 stays black

2018-05-31 Thread Al Marcenkus

Public bug reported:

When I open my notebook computer, Toshiba S75-A7334 (on Windows 10), the
screen remains black, unless I repeatedly open and close the lid. This
is terribly frustrating. I have been dealing with this for years.
Nothing I have tried has worked. I am new to this website, so I'm not
sure I am following your proper procedures. I am an average computer
user that does not write code. Any help is greatly appreciated.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1774433

Title:
  Display on Toshiba S75-A7334 stays black

Status in xorg package in Ubuntu:
  New

Bug description:
  When I open my notebook computer, Toshiba S75-A7334 (on Windows 10),
  the screen remains black, unless I repeatedly open and close the lid.
  This is terribly frustrating. I have been dealing with this for years.
  Nothing I have tried has worked. I am new to this website, so I'm not
  sure I am following your proper procedures. I am an average computer
  user that does not write code. Any help is greatly appreciated.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1774419] Re: easy_install command is missing

2018-05-31 Thread Nick Jones

The changelog for this package states that it the easy_install scripts
were removed, as of:

https://launchpad.net/ubuntu/+source/python-setuptools/39.0.1-2

No rationale is given for the removal, or any suggestion of what users
should be expected to do instead.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-setuptools in
Ubuntu.
https://bugs.launchpad.net/bugs/1774419

Title:
  easy_install command is missing

Status in python-setuptools package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  Package: python-setuptools
  Version:  39.0.1-2

  This package installs the easy_install module, but the command is
  missing:

  deploy@controller0:~$ which easy_install
  deploy@controller0:~$ echo $?
  1

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1772183] Re: [Microsoft Sculpt Ergonomic Mouse] Booting from Windows to Ubuntu causes mouse to scroll multiple lines at a time

2018-05-31 Thread Christopher M. Penalver

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1772183

Title:
  [Microsoft Sculpt Ergonomic Mouse] Booting from Windows to Ubuntu
  causes mouse to scroll multiple lines at a time

Status in xorg package in Ubuntu:
  New

Bug description:
  What happens when booting immediately from Windows to Ubuntu is that
  the mouse scrolls multiple lines at time. This problem doesn't happen
  when booting to and using Windows 10.

  WORKAROUND: https://sourceforge.net/projects/resetmsmice/

  WORKAROUND: Once the problem has stopped in Ubuntu, avoid booting into
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:04:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  396.24  Thu Apr 26 00:10:09 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 19 13:02:28 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 396.24, 4.15.0-20-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
     Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:80de]
     Subsystem: Hewlett-Packard Company GM108M [GeForce 940M] [103c:80de]
  InstallationDate: Installed on 2018-04-27 (22 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180425.1)
  MachineType: HP HP ENVY m7 Notebook
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=f280ba9f-7dfc-4687-84f5-36a316b08404 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/02/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.49
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80DE
  dmi.board.vendor: HP
  dmi.board.version: 64.43
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.49:bd03/02/2018:svnHP:pnHPENVYm7Notebook:pvrType1ProductConfigId:rvnHP:rn80DE:rvr64.43:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV
  dmi.product.name: HP ENVY m7 Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1774423] [NEW] package gstreamer1.0-plugins-bad 1.14.0-1ubuntu1 failed to install/upgrade: Extrahierte Daten für »./usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstfrei0r.so« können

2018-05-31 Thread Julia Sabine Enko

Public bug reported:

apt clean and retry to install the package solved the problem

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: gstreamer1.0-plugins-bad 1.14.0-1ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.1
Architecture: amd64
Date: Thu May 31 15:52:11 2018
ErrorMessage: Extrahierte Daten für 
»./usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstfrei0r.so« können nicht nach 
»/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstfrei0r.so.dpkg-new« kopiert 
werden: Unerwartetes Ende der Datei oder des Datenstroms
InstallationDate: Installed on 2018-05-21 (9 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: gst-plugins-bad1.0
Title: package gstreamer1.0-plugins-bad 1.14.0-1ubuntu1 failed to 
install/upgrade: Extrahierte Daten für 
»./usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstfrei0r.so« können nicht nach 
»/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstfrei0r.so.dpkg-new« kopiert 
werden: Unerwartetes Ende der Datei oder des Datenstroms
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gst-plugins-bad1.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package bionic

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gst-plugins-bad1.0 in
Ubuntu.
https://bugs.launchpad.net/bugs/1774423

Title:
  package gstreamer1.0-plugins-bad 1.14.0-1ubuntu1 failed to
  install/upgrade: Extrahierte Daten für »./usr/lib/x86_64-linux-
  gnu/gstreamer-1.0/libgstfrei0r.so« können nicht nach »/usr/lib/x86_64
  -linux-gnu/gstreamer-1.0/libgstfrei0r.so.dpkg-new« kopiert werden:
  Unerwartetes Ende der Datei oder des Datenstroms

Status in gst-plugins-bad1.0 package in Ubuntu:
  New

Bug description:
  apt clean and retry to install the package solved the problem

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: gstreamer1.0-plugins-bad 1.14.0-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  Date: Thu May 31 15:52:11 2018
  ErrorMessage: Extrahierte Daten für 
»./usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstfrei0r.so« können nicht nach 
»/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstfrei0r.so.dpkg-new« kopiert 
werden: Unerwartetes Ende der Datei oder des Datenstroms
  InstallationDate: Installed on 2018-05-21 (9 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: gst-plugins-bad1.0
  Title: package gstreamer1.0-plugins-bad 1.14.0-1ubuntu1 failed to 
install/upgrade: Extrahierte Daten für 
»./usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstfrei0r.so« können nicht nach 
»/usr/lib/x86_64-linux-gnu/gstreamer-1.0/libgstfrei0r.so.dpkg-new« kopiert 
werden: Unerwartetes Ende der Datei oder des Datenstroms
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-bad1.0/+bug/1774423/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1774417] Re: systemd-logind: do_ypcall: clnt_call: RPC: Unable to send; errno = Operation not permitted

2018-05-31 Thread Dimitri John Ledkov

Well, on Ubuntu we do not have nss-nis package.

As libnss_nis is shipped in libc6, and thus available everywhere. Thus
adding a depends or a drop-in is a non-starter as well it would be
installed by default everywhere.

I'm not sure if we can somehow detect that it was enabled, and require
nscd installation at that point.

I'd rather not unsandbox logind.

** Also affects: glibc (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: nis (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: glibc (Ubuntu)

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

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

** Changed in: systemd (Ubuntu)
   Status: New => Won't Fix

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1774417

Title:
  systemd-logind: do_ypcall: clnt_call: RPC: Unable to send; errno =
  Operation not permitted

Status in nis package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Won't Fix
Status in nis package in Debian:
  Unknown

Bug description:
  See upstream bug report 7074 (systemd-logind's IP sandbox breaks nss-
  nis and suchlike) [1]. Logging in takes a long time.

  May 30 13:26:25 ubuntu1804 systemd-logind[2993]: do_ypcall: clnt_call: 
RPC: Unable to send; errno = Operation not permitted
  May 30 13:26:50 ubuntu1804 sshd[3446]: pam_systemd(sshd:session): Failed 
to create session: Connection timed out

  Conclusion:

  > Please ask your downstream distribution to either:
  > 
  > 1.  include a systemd-logind.service.d/ snippet in your nss-nis package 
that turns off the IP firewalling logic for logind
  > 2.  or patching systemd-logind.service for everybody to disable it 
distro-wide (which I'd really not recommend though, compromising the security 
for everybody just because for compat of a nowadays pretty niche nss module 
that does some very questionnable things doesn't sound like the best way out to 
me)

  
  [1] https://github.com/systemd/systemd/issues/7074

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1774417] [NEW] systemd-logind: do_ypcall: clnt_call: RPC: Unable to send; errno = Operation not permitted

2018-05-31 Thread Paul Menzel

Public bug reported:

See upstream bug report 7074 (systemd-logind's IP sandbox breaks nss-nis
and suchlike) [1]. Logging in takes a long time.

May 30 13:26:25 ubuntu1804 systemd-logind[2993]: do_ypcall: clnt_call: RPC: 
Unable to send; errno = Operation not permitted
May 30 13:26:50 ubuntu1804 sshd[3446]: pam_systemd(sshd:session): Failed to 
create session: Connection timed out

Conclusion:

> Please ask your downstream distribution to either:
> 
> 1.  include a systemd-logind.service.d/ snippet in your nss-nis package that 
> turns off the IP firewalling logic for logind
> 2.  or patching systemd-logind.service for everybody to disable it 
> distro-wide (which I'd really not recommend though, compromising the security 
> for everybody just because for compat of a nowadays pretty niche nss module 
> that does some very questionnable things doesn't sound like the best way out 
> to me)


[1] https://github.com/systemd/systemd/issues/7074

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1774417

Title:
  systemd-logind: do_ypcall: clnt_call: RPC: Unable to send; errno =
  Operation not permitted

Status in systemd package in Ubuntu:
  New

Bug description:
  See upstream bug report 7074 (systemd-logind's IP sandbox breaks nss-
  nis and suchlike) [1]. Logging in takes a long time.

  May 30 13:26:25 ubuntu1804 systemd-logind[2993]: do_ypcall: clnt_call: 
RPC: Unable to send; errno = Operation not permitted
  May 30 13:26:50 ubuntu1804 sshd[3446]: pam_systemd(sshd:session): Failed 
to create session: Connection timed out

  Conclusion:

  > Please ask your downstream distribution to either:
  > 
  > 1.  include a systemd-logind.service.d/ snippet in your nss-nis package 
that turns off the IP firewalling logic for logind
  > 2.  or patching systemd-logind.service for everybody to disable it 
distro-wide (which I'd really not recommend though, compromising the security 
for everybody just because for compat of a nowadays pretty niche nss module 
that does some very questionnable things doesn't sound like the best way out to 
me)

  
  [1] https://github.com/systemd/systemd/issues/7074

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1767096] Re: Random Xorg crashes

2018-05-31 Thread spodin

As workaround for this issue:

1. switched from Nouveau to NVIDIA-340
2. in "NVIDIA X Server Settings" changed PRIME profile from 'Nvidia' to 'Intel'

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1767096

Title:
  Random Xorg crashes

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Xorg crashes randomly: environment just freezes for a second and I'm
  getting login screen.

  ProblemType: Bug
  DistroRelease: elementary 0.4.1
  Package: xorg 1:7.7+13ubuntu3 [origin: Ubuntu]
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  CurrentDesktop: Pantheon
  Date: Thu Apr 26 12:57:22 2018
  InstallationDate: Installed on 2018-03-01 (55 days ago)
  InstallationMedia: elementary OS 0.4.1 "Loki" - Stable amd64 (20180214)
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1774419] [NEW] easy_install command is missing

2018-05-31 Thread Nick Jones

Public bug reported:

Description:Ubuntu 18.04 LTS
Release:18.04

Package: python-setuptools
Version:  39.0.1-2

This package installs the easy_install module, but the command is
missing:

deploy@controller0:~$ which easy_install
deploy@controller0:~$ echo $?
1

** Affects: python-setuptools (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to python-setuptools in
Ubuntu.
https://bugs.launchpad.net/bugs/1774419

Title:
  easy_install command is missing

Status in python-setuptools package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  Package: python-setuptools
  Version:  39.0.1-2

  This package installs the easy_install module, but the command is
  missing:

  deploy@controller0:~$ which easy_install
  deploy@controller0:~$ echo $?
  1

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1774421] [NEW] [X555LA, Realtek ALC3236, Speaker, Internal] No sound when switching from HDMI to internal audio

2018-05-31 Thread Laoise

Public bug reported:

When switching from HDMI audio to internal speakers, the sound stops
working altogether. The only way to prevent this is to enter the
settings while still connected to HDMI and select "Speakers - Built in
audio" as the output. Disconnecting from HDMI without doing this stops
any audio playing through internal speakers or headphones (including the
speaker test in settings). It was expected that disconnecting a HDMI
output would automatically change the sound output to internal speakers.
Attempting to click "Speakers - Built in audio" when disconnected from
HDMI has no effect, the only way to remedy this is to reconnect the
device to HDMI and select the  above output. This means if the device is
removed from HDMI and taken to another location, no sound can be used
until a HDMI output can be found and connected. Rebooting has mixed
effects, on one occasion a reboot restored the sound, however on all
others it does not. The test tones DID play during the debug process
however this is the only sounds I can get to play. The version of Ubuntu
is 18.04 LTS.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC1D0c:   laoise 1485 F...m pulseaudio
 /dev/snd/controlC1:  laoise 1485 F pulseaudio
 /dev/snd/pcmC0D7p:   laoise 1485 F...m pulseaudio
 /dev/snd/controlC0:  laoise 1485 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Thu May 31 14:35:41 2018
InstallationDate: Installed on 2017-04-13 (412 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Speaker, Internal
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: No sound at all
Title: [X555LA, Realtek ALC3236, Speaker, Internal] No sound at all
UpgradeStatus: Upgraded to bionic on 2018-05-12 (19 days ago)
dmi.bios.date: 08/14/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X555LA.308
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X555LA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555LA.308:bd08/14/2014:svnASUSTeKCOMPUTERINC.:pnX555LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: X
dmi.product.name: X555LA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1774421

Title:
  [X555LA, Realtek ALC3236, Speaker, Internal] No sound when switching
  from HDMI to internal audio

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  When switching from HDMI audio to internal speakers, the sound stops
  working altogether. The only way to prevent this is to enter the
  settings while still connected to HDMI and select "Speakers - Built in
  audio" as the output. Disconnecting from HDMI without doing this stops
  any audio playing through internal speakers or headphones (including
  the speaker test in settings). It was expected that disconnecting a
  HDMI output would automatically change the sound output to internal
  speakers. Attempting to click "Speakers - Built in audio" when
  disconnected from HDMI has no effect, the only way to remedy this is
  to reconnect the device to HDMI and select the  above output. This
  means if the device is removed from HDMI and taken to another
  location, no sound can be used until a HDMI output can be found and
  connected. Rebooting has mixed effects, on one occasion a reboot
  restored the sound, however on all others it does not. The test tones
  DID play during the debug process however this is the only sounds I
  can get to play. The version of Ubuntu is 18.04 LTS.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0c:   laoise 1485 F...m pulseaudio
   /dev/snd/controlC1:  laoise 1485 F pulseaudio
   /dev/snd/pcmC0D7p:   laoise 1485 F...m pulseaudio
   /dev/snd/controlC0:  laoise 1485 F pulseaudio
  CurrentDesktop:

[Touch-packages] [Bug 1702793] Re: Full backport SRU for unattended-upgrades

2018-05-31 Thread Balint Reczey

** Description changed:

  [Impact]
  
  * I would like to propose a one-off full backport of unattended-upgrades
  1.2ubuntu1 to Bionic, Artful, Xenial and possibly Trusty releases because 
selectively backporting fixes for crashes and for issues that made u-u 
unreliable would be more risky thanks to the huge number of fixes and the
  inter-dependencies between them.
  
  [Test Case]
  
  * Since this backport involves fixing several bugs and this bug itself covers 
the full backport I suggest that this bug should be considered verified when 
the following list of bugs are verified:
-  - TODO add most important bugs
+  - TODO add most important bugs
  and the following tests are passing:
-  - TODO add tests not covered by bugs above
+  - TODO add tests not covered by bugs above
  
  [Regression Potential]
  
  * Due to this update covering the full backport unattended-upgrades can 
regress in any imaginable way including failing to install, upgrade, run, or 
removing essential packages from the system. Those are unlikely.
  * There are open bugs about u-u being slower than in the past, thus this may 
be a likely regression but IMO the pending speed optimizations should not be 
blocking the backport because the reliability issues are more important to fix 
and speed optimizations can be cherry-picked later.
+ * LP: #1773033 is a regression causing u-u to not install upgrades on 
shutdown when the system was started on battery. I have a WIP fix and can add 
the fix to the SRU if needed.
  
  [Other Info]
  
  I asked for an exception for the package in following the SRU process:
  https://lists.ubuntu.com/archives/ubuntu-release/2018-May/004479.html
  
  I'm preparing the backport in ppa:rbalint/scratch and also run
  autopkgtests on it in addition to testing it manually in VMs.
  
  [Original Bug Text]
  
  Changes to support day-of-week patching and logging to syslog were added
  to upstream (https://github.com/mvo5/unattended-upgrades) over a year
  ago. These changes are not present in the latest Xenial nor Trusty
  packages (0.90 and 0.82.1) - requesting that these changes be pulled
  from upstream.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1702793

Title:
  Full backport SRU for unattended-upgrades

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

  * I would like to propose a one-off full backport of unattended-upgrades
  1.2ubuntu1 to Bionic, Artful, Xenial and possibly Trusty releases because 
selectively backporting fixes for crashes and for issues that made u-u 
unreliable would be more risky thanks to the huge number of fixes and the
  inter-dependencies between them.

  [Test Case]

  * Since this backport involves fixing several bugs and this bug itself covers 
the full backport I suggest that this bug should be considered verified when 
the following list of bugs are verified:
   - TODO add most important bugs
  and the following tests are passing:
   - TODO add tests not covered by bugs above

  [Regression Potential]

  * Due to this update covering the full backport unattended-upgrades can 
regress in any imaginable way including failing to install, upgrade, run, or 
removing essential packages from the system. Those are unlikely.
  * There are open bugs about u-u being slower than in the past, thus this may 
be a likely regression but IMO the pending speed optimizations should not be 
blocking the backport because the reliability issues are more important to fix 
and speed optimizations can be cherry-picked later.
  * LP: #1773033 is a regression causing u-u to not install upgrades on 
shutdown when the system was started on battery. I have a WIP fix and can add 
the fix to the SRU if needed.

  [Other Info]

  I asked for an exception for the package in following the SRU process:
  https://lists.ubuntu.com/archives/ubuntu-release/2018-May/004479.html

  I'm preparing the backport in ppa:rbalint/scratch and also run
  autopkgtests on it in addition to testing it manually in VMs.

  [Original Bug Text]

  Changes to support day-of-week patching and logging to syslog were
  added to upstream (https://github.com/mvo5/unattended-upgrades) over a
  year ago. These changes are not present in the latest Xenial nor
  Trusty packages (0.90 and 0.82.1) - requesting that these changes be
  pulled from upstream.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1702793/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1766872] Re: 'Enable Network' in recovery mode not working in Bionic

2018-05-31 Thread Francis Ginther

** Tags added: id-5afda46ded21519fcf26f22b

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1766872

Title:
  'Enable Network' in recovery mode not working in Bionic

Status in friendly-recovery package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  This bug has been noticed after the introduction of the fix of (LP:
  #1682637) in Bionic.

  I have notice a block in Bionic when choosing 'Enable Network' option
  in recovery mode on different bionic vanilla system and I can
  reproduce all the time.

  I also asked colleagues to give it a try (for a second pair of eye on
  this) and they have the same result as me.

  Basically, when choosing 'Enable Network' it get block or lock.
  If we hit 'ctrl-c', then a shell arrive and the system has network 
connectivity.

  Here's what I find while enabling "systemd.debug-shell=1" from vtty9 :

  # pstree
  systemd-+-bash---pstree
  |-recovery-menu---network---systemctl---systemd-tty-ask
  |-systemd-journal
  

  # ps
  root 486 473 0 08:29 tty1 00:00:00 /bin/systemd-tty-ask-password-agent

  root 473 486 0 08:29 tty1 00:00:00 systemctl start dbus.socket

  root 486 283 0 08:29 tty1 00:00:00 /bin/sh /lib/recovery-
  mode/options/network

  Additionally,

  systemd-analyze blame:
  "Bootup is not yet finished. Please try again later"

  "systemctl list-jobs" is showing a 100 jobs in 'waiting' state

  The only 'running' unit is friendly-recovery.service :
  52 friendly-recovery.service start running

  The rest are all "waiting". My understanding is that "waiting" units
  will be executed only after those which are "running" are completed.
  Which explain why the "ctlr-c" allow the boot to continue.

  All the systemd special unit important at boot-up are waiting.
  7 sysinit.target start waiting
  3 basic.target   start waiting
  .

  Seems like systemd is not fully initialise in 'Recovery Mode' and
  doesn't allow any 'systemctl start' operation without
  password/passphrase request, which I suspect is hidden by the
  recovery-mode menu.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1773157] Re: procps outdated network options, old syncookies, new ecn update please.

2018-05-31 Thread Simon Iremonger

Right -- systemd have just-now agreed to set the change in their upstream
systemd sysctl files :-
https://github.com/systemd/systemd/commit/6f130e85c76cfc2c58ba31f90d2ac3800866c1dd

I notice, however, that ubuntu's systemd pkg 'strips most those settings
out', in 18.04 currently only carrying the 18.04 fq_codel switch-on in
their sysctl.d

I think, given what has been said, I would like to propose that I :-

* Make a suggested text for a 10-network-bufferbloat.conf here in
procps in 18.10 (hopefully-onwards, including suitable
references/comments about BBR (which should be there but commented/not-
enabled yet unless we are sure its' been fixed to respond to ECN
notifications.). This text shall explain clearly these are deliberately
being tested into 18.10 and where to report bugs.

* Look at what ubuntu's systemd package towards 18.10 is importing in
sysctl.d -- and likely suggest ubuntu 'taken out' entirely so procps
is the 'one' location for these settings (i.e. no duplicate setting of
qdisc=fq_codel in 2 different places). Some will want to boot ubuntu
with OpenRC or upstart for whatever reasons and consistent-behaviour
would be helpful...

* Ask in the BBR community about tcp_congestion_control goings-on there,
when they are ready for ECN-compatible BBR wider-deployment.

* Then, as/when seems appropriate, suggest changes into upstream-debian
and upstream-kernel on the defaults.

@rbalint -- what do you think on this plan for the interim?

--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to procps in Ubuntu.
https://bugs.launchpad.net/bugs/1773157

Title:
procps outdated network options, old syncookies, new ecn update
please.

Status in procps package in Ubuntu:
Confirmed

Bug description:
The ubuntu version of procps carries it's own /etc/sysctl.d/10
-network-security.conf file explicitly that appears not to be part of
debian procps version.

Firstly, the section about "# Turn on SYN-flood protections." (came from LP
#57091 ) is now entirely outdated, upstream kernel has long since turned on
syncookies by default, so setting this flag explicitly in
10-network-security.conf is entirely redundant likely since before ubuntu-14.04
.
I would like the ubuntu-maintainer to remove that section entirely in cosmic
onwards.

[I am going to report debian the similarly outdated syncookies
comments in sysctl.conf itself].

Secondly, I propose a new 10-network-tuning.conf with:-
==
# Allow ECN for outgoing connections. Starting with 4.2, there is an adaptive
# fallback [enabled by default tcp_ecn_fallback option] preventing connection
# loss even with ecn enabled, also ecn-intolerance is increasingly very rare.
net.ipv4.tcp_ecn=1
==

I know there is a (small) chance of issues/regressions with ECN
enabled by default on outgoing but I'm quite sure the issue is very
rare, like others notice [ref: 1 and 2 below]. Apple's selective
enablements etc. show this works just as much as my own use for years
and many similar reports.

ECN actually being used for outgoing connections really helps with
latency-reduction with modern routers (both core and edge) using
queuing disciplines fq_codel or otherwise, able to mark rather than
drop packets on ECN-enabled flows [helps latency and realtime
applications]. Now we are just past LTS release is in my view the
'right time' to finally enable ECN [and obviously easy to revert!].
If this is disputed, in ANY case I strongly suggest at the very least
a commented-out ECN section should be included, but 'defaults
matter'!.

I was going to suggest a non-default section about
net.core.default_qdisc [ LP #1436945 ] but this appears to have been
fixed upstream similarly.

[1]
https://www.ietf.org/proceedings/98/slides/slides-98-maprg-tcp-ecn-experience-with-enabling-ecn-on-the-internet-padma-bhooma-00.pdf
[2] http://seclists.org/nanog/2015/Jun/675

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

--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1774399] [NEW] No sound at all (internal speaker - LG AIO)

2018-05-31 Thread LedStyle

Public bug reported:

My internal speaker is not working [ALC282].

When I plug in headphones or external speakers into headphone slot
there's no problem.

But when I try to play sounds with my internal speaker, it stay mute.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  antonio1188 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Thu May 31 08:12:41 2018
InstallationDate: Installed on 2018-04-29 (31 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=pt_BR:pt:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Áudio interno - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  antonio1188 F pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [24V360-L.BJ57P1, Realtek ALC282, Speaker, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/25/2016
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 24VA1440 X64
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 24V360
dmi.board.vendor: LG Electronics
dmi.board.version: FAB2
dmi.chassis.asset.tag: Asset Tag
dmi.chassis.type: 13
dmi.chassis.vendor: LG Electronics
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr24VA1440X64:bd03/25/2016:svnLGElectronics:pn24V360-L.BJ57P1:pvr0.1:rvnLGElectronics:rn24V360:rvrFAB2:cvnLGElectronics:ct13:cvr0.1:
dmi.product.family: Braswell System
dmi.product.name: 24V360-L.BJ57P1
dmi.product.version: 0.1
dmi.sys.vendor: LG Electronics

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

** Description changed:

- My internal speaker is not working.
+ My internal speaker is not working [ALC282].
  
  When I plug in headphones or external speakers into headphone slot
  there's no problem.
  
  But when I try to play sounds with my internal speaker, it stay mute.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  antonio1188 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  antonio1188 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 31 08:12:41 2018
  InstallationDate: Installed on 2018-04-29 (31 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
-  LANGUAGE=pt_BR:pt:en
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=pt_BR.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=pt_BR:pt:en
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=pt_BR.UTF-8
+  SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Áudio interno - HDA Intel PCH
  Symptom_DevicesInUse:
-  USERPID ACCESS COMMAND
-  /dev/snd/controlC0:  antonio1188 F pulseaudio
+  USERPID ACCESS COMMAND
+  /dev/snd/controlC0:  antonio1188 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [24V360-L.BJ57P1, Realtek ALC282, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/25/2016
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 24VA1440 X64
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 24V360
  dmi.board.vendor: LG Electronics
  dmi.board.version: FAB2
  dmi.chassis.asset.tag: Asset Tag
  dmi.chassis.type: 13
  dmi.chassis.vendor: LG Electronics
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr24VA1440X64:bd03/25/2016:svnLGElectronics:pn24V360-L.BJ57P1:pvr0.1:rvnLGElectronics:rn24V360:rvrFAB2:cvnLGElectronics:ct13:cvr0.1:
  dmi.product.family: Braswell System
  dmi.product.name: 24V360-L.BJ57P1
  dmi.product.version: 0.1
  dmi.sys.vendor: LG Electronics

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1774399

Title:
  No sound at all (internal speaker - LG AIO)

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  My internal speaker is not working [ALC282].

  When I plug in headphones or external speakers into headphone slot

[Touch-packages] [Bug 1243866] Re: [Inspiron 3521, Realtek ALC282, Speaker, Internal] No sound at all

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1243866

Title:
  [Inspiron 3521, Realtek ALC282, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  fds

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu1.1
  ProcVersionSignature: Ubuntu 3.8.0-32.47~precise1-generic 3.8.13.10
  Uname: Linux 3.8.0-32-generic x86_64
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k3.8.0-32-generic.
  ApportVersion: 2.0.1-0ubuntu17.5
  Architecture: amd64
  ArecordDevices:
    List of CAPTURE Hardware Devices 
   card 0: PCH [HDA Intel PCH], device 0: ALC282 Analog [ALC282 Analog]
 Subdevices: 1/1
 Subdevice #0: subdevice #0
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  e_mamut2304 F pulseaudio
e_mamut3924 F TeamViewer.exe
   /dev/snd/pcmC0D0p:   e_mamut2304 F...m pulseaudio
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xc061 irq 44'
 Mixer name : 'Intel PantherPoint HDMI'
 Components : 'HDA:10ec0282,10280597,0013 
HDA:80862806,80860101,0010'
 Controls  : 27
 Simple ctrls  : 10
  Date: Wed Oct 23 13:24:36 2013
  InstallationMedia: Ubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 
(20130820.1)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=es_EC:es
   PATH=(custom, no user)
   LANG=es_EC.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Audio Interno - HDA Intel PCH
  Symptom_DevicesInUse: 2304  3924  2304
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [Inspiron 3521, Realtek ALC282, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/03/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0CPH8W
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A05
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd01/03/2013:svnDellInc.:pnInspiron3521:pvrA05:rvnDellInc.:rn0CPH8W:rvrA02:cvnDellInc.:ct8:cvrA05:
  dmi.product.name: Inspiron 3521
  dmi.product.version: A05
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1772183] Re: [Microsoft Sculpt Ergonomic Mouse] Booting from Windows to Ubuntu causes mouse to scroll multiple lines at a time

2018-05-31 Thread Mike L

Unfortunately I do not own a wired USB mouse to test it with.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1772183

Title:
  [Microsoft Sculpt Ergonomic Mouse] Booting from Windows to Ubuntu
  causes mouse to scroll multiple lines at a time

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  What happens when booting immediately from Windows to Ubuntu is that
  the mouse scrolls multiple lines at time. This problem doesn't happen
  when booting to and using Windows 10.

  WORKAROUND: https://sourceforge.net/projects/resetmsmice/

  WORKAROUND: Once the problem has stopped in Ubuntu, avoid booting into
  Windows.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..04.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:04:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  396.24  Thu Apr 26 00:10:09 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May 19 13:02:28 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 396.24, 4.15.0-20-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 5500 [8086:1616] (rev 09) (prog-if 00 [VGA 
controller])
     Subsystem: Hewlett-Packard Company HD Graphics 5500 [103c:80de]
     Subsystem: Hewlett-Packard Company GM108M [GeForce 940M] [103c:80de]
  InstallationDate: Installed on 2018-04-27 (22 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180425.1)
  MachineType: HP HP ENVY m7 Notebook
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=f280ba9f-7dfc-4687-84f5-36a316b08404 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/02/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.49
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 80DE
  dmi.board.vendor: HP
  dmi.board.version: 64.43
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.49:bd03/02/2018:svnHP:pnHPENVYm7Notebook:pvrType1ProductConfigId:rvnHP:rn80DE:rvr64.43:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV
  dmi.product.name: HP ENVY m7 Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1772975] Re: /lib/udev/ifupdown-hotplug is not executable