date:20180226

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

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

Title:
  PCI/internal sound card not detected and no sound

Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  root@issa-R610:/home/issa# lspci
  00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory 
Controller Hub (rev 07)
  00:01.0 PCI bridge: Intel Corporation Mobile 4 Series Chipset PCI Express 
Graphics Port (rev 07)
  00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #4 (rev 03)
  00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #5 (rev 03)
  00:1a.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #6 (rev 03)
  00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI 
Controller #2 (rev 03)
  00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio 
Controller (rev 03)
  00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 
(rev 03)
  00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 
(rev 03)
  00:1c.3 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 4 
(rev 03)
  00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #1 (rev 03)
  00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #2 (rev 03)
  00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #3 (rev 03)
  00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI 
Controller #1 (rev 03)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic i686
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Mon Jun 26 11:05:34 2017
  InstallationDate: Installed on 2017-06-16 (9 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.2)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/26/2008
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 02LK.MP00.20080926.SCY
  dmi.board.name: R610
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr02LK.MP00.20080926.SCY:bd09/26/2008:svnSAMSUNGELECTRONICSCO.,LTD.:pnR610:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR610:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.name: R610
  dmi.product.version: Not Applicable
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1700505/+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 1703724] Re: package systemd-sysv 231-9ubuntu5 failed to install/upgrade: subprocess installed post-removal script returned error exit status 2

This is an unsupported release now. Please think to install the next LTS
'Bionic 18.04'

http://cdimage.ubuntu.com/lubuntu-next/daily-live/current/
https://www.omgubuntu.co.uk/2018/02/ubuntu-18-04-minimal-install-option

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

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

Title:
  package systemd-sysv 231-9ubuntu5 failed to install/upgrade:
  subprocess installed post-removal script returned error exit status 2

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  Failed upgrade installation.

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: systemd-sysv 231-9ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17
  Uname: Linux 4.8.0-59-generic i686
  ApportVersion: 2.20.3-0ubuntu8.6
  Architecture: i386
  Date: Mon Jul 10 14:12:44 2017
  ErrorMessage: subprocess installed post-removal script returned error exit 
status 2
  InstallationDate: Installed on 2012-02-25 (1963 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1.1
   apt  1.3.5
  SourcePackage: systemd
  Title: package systemd-sysv 231-9ubuntu5 failed to install/upgrade: 
subprocess installed post-removal script returned error exit status 2
  UpgradeStatus: Upgraded to yakkety on 2017-07-10 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1703724/+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 1750780] Re: Race with local file systems can make open-vm-tools fail to start

2018-02-26 Thread ChristianEhrhardt

I'Ll likely revert the Binonic change tmrw morning as we have discussed.
local-fs.target is actually >> the implicit dependency.

But that does not solve the Xenial issue outlined in the former comment.

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

Title:
  Race with local file systems can make open-vm-tools fail to start

Status in cloud-init:
  Invalid
Status in open-vm-tools package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in open-vm-tools source package in Xenial:
  Triaged
Status in systemd source package in Xenial:
  New
Status in open-vm-tools package in Debian:
  Incomplete

Bug description:
  Since the change in [1] open-vm-tools-service starts very (very) early.
  Not so much due to the 
  Before=cloud-init-local.service
  But much more by
  DefaultDependencies=no

  That can trigger an issue that looks like
  root@ubuntuguest:~# systemctl status -l open-vm-tools.service
  ● open-vm-tools.service - Service for virtual machines hosted on VMware
 Loaded: loaded (/lib/systemd/system/open-vm-tools.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: resources)

  
  As it is right now open-vm-tools can race with the other early start and then 
fail.
  In detail one can find a message like:
open-vm-tools.service: Failed to run 'start' task: Read-only file system"

  This is due to privtaeTmp=yes which is also set needing a writable
  /var/tmp [2]

  To ensure this works PrivateTmp would have to be removed (not good) or some 
after dependencies added that make this work reliably.
  I added
  After=local-fs.target
  which made it work for me in 3/3 tests.

  I' like to have an ack by the cloud-init Team that this does not totally kill 
the originally intended Before=cloud-init-local.service
  I think it does not as local-fs can complete before cloud-init-local, then 
open-vm-tools can initialize and finally cloud-init-local can pick up the data.

  To summarize:
  # cloud-init-local #
  DefaultDependencies=no
  Wants=network-pre.target
  After=systemd-remount-fs.service
  Before=NetworkManager.service
  Before=network-pre.target
  Before=shutdown.target
  Before=sysinit.target
  Conflicts=shutdown.target
  RequiresMountsFor=/var/lib/cloud

  # open-vm-tools #
  DefaultDependencies=no
  Before=cloud-init-local.service

  Proposed is to add to the latter:
  After=local-fs.target

  [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859677
  [2]: https://github.com/systemd/systemd/issues/5610

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1750780/+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 1751484] Re: Captive portal browser/device misreported

2018-02-26 Thread Will Cooke

** Changed in: network-manager (Ubuntu)
   Status: New => Confirmed

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

Title:
  Captive portal browser/device misreported

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  
  The browser used in the captive portal system is reported as 'Desktop Safari 
Linux 64'. Could we change this to 'Ubuntu Desktop', please?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1751484/+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 1703048] Re: package click 0.4.45.1+16.10.20160916-0ubuntu1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 1

This is an unsupported release now. Please think to install the next LTS
'Bionic 18.04'

http://cdimage.ubuntu.com/lubuntu-next/daily-live/current/
https://www.omgubuntu.co.uk/2018/02/ubuntu-18-04-minimal-install-option

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

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

Title:
  package click 0.4.45.1+16.10.20160916-0ubuntu1 failed to
  install/upgrade: subprocess new pre-removal script returned error exit
  status 1

Status in click package in Ubuntu:
  Invalid

Bug description:
  Preparing to unpack .../click_0.4.46+16.10.20170607.3-0ubuntu1_amd64.deb ...
  Cannot start click due to a conflict with a different locally-installed 
Python 'click' package.  Remove it using Python packaging tools and try again.
  dpkg: warning: subprocess old pre-removal script returned error exit status 1
  dpkg: trying script from the new package instead ...
  Cannot start click due to a conflict with a different locally-installed 
Python 'click' package.  Remove it using Python packaging tools and try again.
  dpkg: error processing archive 
/var/cache/apt/archives/click_0.4.46+16.10.20170607.3-0ubuntu1_amd64.deb 
(--unpack):
   subprocess new pre-removal script returned error exit status 1
  Job for click-system-hooks.service failed because the control process exited 
with error code.
  See "systemctl status click-system-hooks.service" and "journalctl -xe" for 
details.
  click-system-hooks.service couldn't start.
  Errors were encountered while processing:
   /var/cache/apt/archives/click_0.4.46+16.10.20170607.3-0ubuntu1_amd64.deb
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  lsb_release -rd
  Description:  Ubuntu 16.10
  Release:  16.10

  
  apt-cache policy click
  click:
Installed: 0.4.45.1+16.10.20160916-0ubuntu1
Candidate: 0.4.46+16.10.20170607.3-0ubuntu1
Version table:
   0.4.46+16.10.20170607.3-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu yakkety-updates/main amd64 
Packages
   *** 0.4.45.1+16.10.20160916-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu yakkety/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: click 0.4.45.1+16.10.20160916-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-54.57-generic 4.8.17
  Uname: Linux 4.8.0-54-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.3-0ubuntu8.3
  AptOrdering:
   click:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Fri Jul  7 13:13:19 2017
  DpkgHistoryLog:
   Start-Date: 2017-07-07  13:13:18
   Commandline: apt-get -f install
   Requested-By: george (1000)
   Upgrade: click:amd64 (0.4.45.1+16.10.20160916-0ubuntu1, 
0.4.46+16.10.20170607.3-0ubuntu1)
  ErrorMessage: subprocess new pre-removal script returned error exit status 1
  InstallationDate: Installed on 2017-01-10 (178 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1.1
   apt  1.3.5
  SourcePackage: click
  Title: package click 0.4.45.1+16.10.20160916-0ubuntu1 failed to 
install/upgrade: subprocess new pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/click/+bug/1703048/+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 1702543] Re: package keyboard-configuration 1.142ubuntu5 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 127

This is an unsupported release now. Please think to install the next LTS
'Bionic 18.04'

http://cdimage.ubuntu.com/lubuntu-next/daily-live/current/
https://www.omgubuntu.co.uk/2018/02/ubuntu-18-04-minimal-install-option

** Changed in: console-setup (Ubuntu)
   Status: New => Invalid

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

Title:
  package keyboard-configuration 1.142ubuntu5 failed to install/upgrade:
  le sous-processus script post-installation installé a retourné une
  erreur de sortie d'état 127

Status in console-setup package in Ubuntu:
  Invalid

Bug description:
  When i press any key on the keyboard all it does is display the
  console for locking, suspending, restarting and shutting down the
  computer, how to fix this problem

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: keyboard-configuration 1.142ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-58.63-generic 4.8.17
  Uname: Linux 4.8.0-58-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.3
  Architecture: amd64
  Date: Wed Jul  5 20:58:26 2017
  ErrorMessage: le sous-processus script post-installation installé a retourné 
une erreur de sortie d'état 127
  InstallationDate: Installed on 2017-07-04 (1 days ago)
  InstallationMedia: Ubuntu-MATE 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1.1
   apt  1.3.5
  SourcePackage: console-setup
  Title: package keyboard-configuration 1.142ubuntu5 failed to install/upgrade: 
le sous-processus script post-installation installé a retourné une erreur de 
sortie d'état 127
  UpgradeStatus: Upgraded to yakkety on 2017-07-05 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1702543/+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 1702869] Re: package zlib1g:amd64 1:1.2.8.dfsg-2ubuntu5.1 failed to install/upgrade: package zlib1g:amd64 is already installed and configured

This is an unsupported release now. Please think to install the next LTS
'Bionic 18.04'

http://cdimage.ubuntu.com/lubuntu-next/daily-live/current/
https://www.omgubuntu.co.uk/2018/02/ubuntu-18-04-minimal-install-option

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

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

Title:
  package zlib1g:amd64 1:1.2.8.dfsg-2ubuntu5.1 failed to
  install/upgrade: package zlib1g:amd64 is already installed and
  configured

Status in zlib package in Ubuntu:
  Invalid

Bug description:
  Ubuntu won't fully upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: zlib1g:amd64 1:1.2.8.dfsg-2ubuntu5.1
  ProcVersionSignature: Ubuntu 4.4.0-83.106-generic 4.4.70
  Uname: Linux 4.4.0-83-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
  Architecture: amd64
  Date: Fri Jul  7 11:48:11 2017
  Dependencies:
   gcc-6-base 6.2.0-5ubuntu12
   libc6 2.24-3ubuntu2.2
   libgcc1 1:6.2.0-5ubuntu12
  ErrorMessage: package zlib1g:amd64 is already installed and configured
  InstallationDate: Installed on 2015-12-22 (563 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1.1
   apt  1.2.20
  SourcePackage: zlib
  Title: package zlib1g:amd64 1:1.2.8.dfsg-2ubuntu5.1 failed to 
install/upgrade: package zlib1g:amd64 is already installed and configured
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1702869/+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 1701967] Re: package linux-image-generic 4.8.0.58.71 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

This is an unsupported release now. Please think to install the next LTS
'Bionic 18.04'

http://cdimage.ubuntu.com/lubuntu-next/daily-live/current/
https://www.omgubuntu.co.uk/2018/02/ubuntu-18-04-minimal-install-option

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Invalid

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

Title:
  package linux-image-generic 4.8.0.58.71 failed to install/upgrade:
  run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return
  code 1

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  I don't know

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: linux-image-generic 4.8.0.58.71
  ProcVersionSignature: Ubuntu 4.8.0-56.61-generic 4.8.17
  Uname: Linux 4.8.0-56-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  tasos  2329 F pulseaudio
   /dev/snd/controlC0:  tasos  2329 F pulseaudio
   /dev/snd/controlC1:  tasos  2329 F pulseaudio
  Date: Wed Jun 28 00:45:58 2017
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=4e8cd5c6-9fd0-499f-b212-c9458002202a
  InstallationDate: Installed on 2016-12-19 (195 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  IwConfig:
   enp4s0no wireless extensions.
   
   lono wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-56-generic 
root=UUID=d4b21a16-2b70-456b-9374-3df0d5206c01 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu11
  RfKill:
   
  SourcePackage: initramfs-tools
  Title: package linux-image-generic 4.8.0.58.71 failed to install/upgrade: 
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
  UpgradeStatus: Upgraded to yakkety on 2017-06-30 (1 days ago)
  dmi.bios.date: 07/11/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 6508
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A85-M
  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.:bvr6508:bd07/11/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnF2A85-M:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1701967/+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 1700505] Re: PCI/internal sound card not detected and no sound

This is an unsupported release now. Please think to install the next LTS
'Bionic 18.04'

http://cdimage.ubuntu.com/lubuntu-next/daily-live/current/
https://www.omgubuntu.co.uk/2018/02/ubuntu-18-04-minimal-install-option

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

Title:
  PCI/internal sound card not detected and no sound

Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  root@issa-R610:/home/issa# lspci
  00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory 
Controller Hub (rev 07)
  00:01.0 PCI bridge: Intel Corporation Mobile 4 Series Chipset PCI Express 
Graphics Port (rev 07)
  00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #4 (rev 03)
  00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #5 (rev 03)
  00:1a.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #6 (rev 03)
  00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI 
Controller #2 (rev 03)
  00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio 
Controller (rev 03)
  00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 
(rev 03)
  00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 
(rev 03)
  00:1c.3 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 4 
(rev 03)
  00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #1 (rev 03)
  00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #2 (rev 03)
  00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI 
Controller #3 (rev 03)
  00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI 
Controller #1 (rev 03)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic i686
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Mon Jun 26 11:05:34 2017
  InstallationDate: Installed on 2017-06-16 (9 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.2)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/26/2008
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: 02LK.MP00.20080926.SCY
  dmi.board.name: R610
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvr02LK.MP00.20080926.SCY:bd09/26/2008:svnSAMSUNGELECTRONICSCO.,LTD.:pnR610:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR610:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.name: R610
  dmi.product.version: Not Applicable
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1700505/+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 1751762] Re: AppArmor prevents opening LibreOffice Writer documents from another HDD

2018-02-26 Thread Jamie Strandboge

*** This bug is a duplicate of bug 1751005 ***
https://bugs.launchpad.net/bugs/1751005

** Package changed: apparmor (Ubuntu) => libreoffice (Ubuntu)

** This bug has been marked a duplicate of bug 1751005
   libreoffice cannot open a document not within $HOME

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

Title:
  AppArmor prevents opening LibreOffice Writer documents from another
  HDD

Status in libreoffice package in Ubuntu:
  New

Bug description:
  When I try to open a LibreOffice Writer document from another HDD
  which is mounted on to my main HDD, AppArmor prevents LibreOffice from
  opening it.

  Steps to reproduce:

  1. Use Nautilus to go to your document (on the mounted HDD)
  2. Double-Click the document
  3. LibreOffice splash screen appears and closes a few seconds
  4. Nothing happens

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: apparmor 2.11.0-2ubuntu17.1
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 26 12:21:18 2018
  InstallationDate: Installed on 2018-01-20 (36 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdline: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: apparmor
  Syslog:
   
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1751762/+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 1705184] Re: Unable to send files via bluetooth since upgrade to 16.10

This is an unsupported release now. Please think to install the next LTS
'Bionic 18.04'

http://cdimage.ubuntu.com/lubuntu-next/daily-live/current/
https://www.omgubuntu.co.uk/2018/02/ubuntu-18-04-minimal-install-option

** Changed in: indicator-bluetooth (Ubuntu)
   Status: New => Invalid

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

Title:
  Unable to send files via bluetooth since upgrade to 16.10

Status in indicator-bluetooth package in Ubuntu:
  Invalid

Bug description:
  To replicate:
  Select "Send files" in either the bluetooth control panel or under the 
bluetooth indicator menu. Select a file in the dialog that appears, click the 
"select button"
  What happens:
  The dialog closes, and there is no evidence whatsoever that any attempt to 
send the file has been made.

  This feature was working correctly in 16.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: indicator-bluetooth 0.0.6+16.10.20161003-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-58.63-generic 4.8.17
  Uname: Linux 4.8.0-58-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jul 19 18:30:26 2017
  EcryptfsInUse: Yes
  ExecutablePath: 
/usr/lib/x86_64-linux-gnu/indicator-bluetooth/indicator-bluetooth-service
  InstallationDate: Installed on 2017-03-04 (136 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  SourcePackage: indicator-bluetooth
  UpgradeStatus: Upgraded to yakkety on 2017-07-16 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1705184/+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 1704051] Re: package bsdutils 1:2.28.2-1ubuntu1.2 failed to install/upgrade: le paquet est dans un état vraiment incohérent; vous devriez le réinstaller avant de tenter de le co

This is an unsupported release now. Please think to install the next LTS
'Bionic 18.04'

http://cdimage.ubuntu.com/lubuntu-next/daily-live/current/
https://www.omgubuntu.co.uk/2018/02/ubuntu-18-04-minimal-install-option

** Changed in: util-linux (Ubuntu)
   Status: New => Invalid

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

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

Title:
  package bsdutils 1:2.28.2-1ubuntu1.2 failed to install/upgrade: le
  paquet est dans un état vraiment incohérent; vous devriez  le
  réinstaller avant de tenter de le configurer.

Status in dpkg package in Ubuntu:
  Invalid
Status in util-linux package in Ubuntu:
  Invalid

Bug description:
  No comment, sorry

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: bsdutils 1:2.28.2-1ubuntu1.2
  ProcVersionSignature: Ubuntu 4.8.0-58.63-generic 4.8.17
  Uname: Linux 4.8.0-58-generic i686
  ApportVersion: 2.20.3-0ubuntu8.6
  AptOrdering:
   bsdutils:i386: Configure
   flashplugin-installer:i386: Install
   NULL: ConfigurePending
  Architecture: i386
  Date: Thu Jul 13 07:16:29 2017
  DpkgTerminalLog:
   dpkg: erreur de traitement du paquet bsdutils (--configure) :
le paquet est dans un état vraiment incohérent; vous devriez
le réinstaller avant de tenter de le configurer.
  ErrorMessage: le paquet est dans un état vraiment incohérent; vous devriez  
le réinstaller avant de tenter de le configurer.
  InstallationDate: Installed on 2017-02-21 (141 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release i386 
(20161012.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1.1
   apt  1.3.5
  SourcePackage: util-linux
  Title: package bsdutils 1:2.28.2-1ubuntu1.2 failed to install/upgrade: le 
paquet est dans un état vraiment incohérent; vous devriez  le réinstaller avant 
de tenter de le configurer.
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1704051/+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 1700089] Re: package python3-click-package 0.4.46+16.10.20170607.3-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

This is an unsupported release now. Please think to install the next LTS
'Bionic 18.04'

http://cdimage.ubuntu.com/ubuntu-next/daily-live/current/
https://www.omgubuntu.co.uk/2018/02/ubuntu-18-04-minimal-install-option

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

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

Title:
  package python3-click-package 0.4.46+16.10.20170607.3-0ubuntu1 failed
  to install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in click package in Ubuntu:
  Invalid

Bug description:
  Not sure what happened, just had this pop up.

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: python3-click-package 0.4.46+16.10.20170607.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-56.61-generic 4.8.17
  Uname: Linux 4.8.0-56-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.3
  AptOrdering:
   click:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Fri Jun 23 14:59:20 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-08-21 (305 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1.1
   apt  1.3.5
  SourcePackage: click
  Title: package python3-click-package 0.4.46+16.10.20170607.3-0ubuntu1 failed 
to install/upgrade: subprocess installed post-installation script returned 
error exit status 1
  UpgradeStatus: Upgraded to yakkety on 2016-10-19 (247 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/click/+bug/1700089/+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 1720482] Re: Demote xterm to universe

2018-02-26 Thread Jeremy Bicha

** Changed in: xterm (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Demote xterm to universe

Status in tk8.6 package in Ubuntu:
  Fix Released
Status in xinit package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Fix Released
Status in xterm package in Ubuntu:
  Fix Released

Bug description:
  Now that xterm is no longer included in the default Ubuntu install, we
  should be able to demote it to universe and let gnome-terminal fulfill
  the x-terminal-emulator virtual package dependency.

  $ reverse-depends -c main xterm
  Reverse-Recommends
  ==
  * tk8.6
  * xinit

  Reverse-Depends
  ===
  * xorg

  tk8.6
  Recommends: xterm | x-terminal-emulator

  xinit
  Recommends: xterm | x-session-manager | x-window-manager | x-terminal-emulator

  xorg
  Depends: xterm | x-terminal-emulator

  gnome-terminal
  Provides: x-terminal-emulator

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tk8.6/+bug/1720482/+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 1732002] Re: cloud images in lxc get ipv6 address

2018-02-26 Thread Ryan Harper

I've got a branch which would have cloud-init disable accept-ra unless
cloud-init has an explicit ipv6 configuration (static or dhcp6).  This
only affects the solicitation effort, ipv6 link-local is of course,
unaffected as is explicit ipv6 configuration.  I believe LXD is in a
position to know if it has an ipv6 enabled bridge; it could control the
template to use a dhcp6 config instead of dhcp (which is ipv4) and not
the unconfigured IPV6 RA, which on older releases like Xenial and Trusty
won't see without configuration anyhow.

https://code.launchpad.net/~raharper/cloud-init/+git/cloud-
init/+merge/339437

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

Title:
  cloud images in lxc get ipv6 address

Status in nplan package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  I noticed that lxd (lxc list) reports that an lxc container has an
  ipv6 address in artful or bionic.  It does not list this in xenial or
  zesty.  I suspect this change occurred in the switch over to
  netplan/networkd.

  This may at first seem harmless or even desired, but note that the
  user configuration did not request ipv6 config, so its presence is a
  bug.

  $ for rel in xenial zesty artful bionic; do
 lxc launch ubuntu-daily:$rel $rel-demo; done
  Creating xenial-demo
  Starting xenial-demo
  ..
  Creating bionic-demo
  Starting bionic-demo

  
  $ sleep 10
  $ lxc list
  $ lxc list
  
+-+-+--+++---+
  |NAME |  STATE  | IPV4 |  IPV6
  |TYPE| SNAPSHOTS |
  
+-+-+--+++---+
  | artful-demo | RUNNING | 10.75.205.208 (eth0) | 
fd42:eee5:7c43:3d62:3a42:611c:3f6f:1184 (eth0) | PERSISTENT | 0 |
  
+-+-+--+++---+
  | bionic-demo | RUNNING | 10.75.205.187 (eth0) | 
fd42:eee5:7c43:3d62:6f4:155b:39cc:fc3d (eth0)  | PERSISTENT | 0 |
  
+-+-+--+++---+
  | xenial-demo | RUNNING | 10.75.205.143 (eth0) |  
  | PERSISTENT | 0 |
  
+-+-+--+++---+
  | zesty-demo  | RUNNING | 10.75.205.123 (eth0) |  
  | PERSISTENT | 0 |
  
+-+-+--+++---+

  ## Here is the config that was provided by lxd
  $ lxc exec bionic-demo cat /var/lib/cloud/seed/nocloud-net/network-config
  version: 1
  config:
  - type: physical
name: eth0
subnets:
- type: dhcp
  control: auto

  ## Here is the config that cloud-init rendered.
  $ lxc exec bionic-demo -- grep -v '^#' /etc/netplan/50-cloud-init.yaml
  network:
  version: 2
  ethernets:
  eth0:
  dhcp4: true

  $ lxc exec bionic-demo cat /run/systemd/network/10-netplan-eth0.network
  [Match]
  Name=eth0

  [Network]
  DHCP=ipv4

  [DHCP]
  UseMTU=true
  RouteMetric=100

  $ lxc exec bionic-demo  -- systemctl status --no-pager --full systemd-networkd
  ● systemd-networkd.service - Network Service
 Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; 
vendor preset: enabled)
 Active: active (running) since Mon 2017-11-13 18:37:34 UTC; 8min ago
   Docs: man:systemd-networkd.service(8)
   Main PID: 118 (systemd-network)
 Status: "Processing requests..."
  Tasks: 1 (limit: 4915)
 Memory: 2.0M
CPU: 19ms
 CGroup: /system.slice/systemd-networkd.service
 └─118 /lib/systemd/systemd-networkd

  Nov 13 18:37:34 bionic-demo systemd[1]: Starting Network Service...
  Nov 13 18:37:34 bionic-demo systemd-networkd[118]: eth0: Gained IPv6LL
  Nov 13 18:37:34 bionic-demo systemd-networkd[118]: Enumeration completed
  Nov 13 18:37:34 bionic-demo systemd[1]: Started Network Service.
  Nov 13 18:37:37 bionic-demo systemd-networkd[118]: eth0: DHCPv6 address 
fd42:eee5:7c43:3d62:6f4:155b:39cc:fc3d/128 timeout preferred 3600 valid 3600
  Nov 13 18:37:37 bionic-demo systemd-networkd[118]: eth0: DHCPv4 address 
10.75.205.187/24 via 10.75.205.1
  Nov 13 18:37:37 bionic-demo systemd-networkd[118]: Not connected to system 
bus, ignoring transient hostname.
  Nov 13 18:37:39 bionic-demo systemd-networkd[118]: eth0: Configured
  Nov 13 18:38:09 bionic-demo systemd-networkd[118]: Could not set hostname: 
Method call timed out

[Touch-packages] [Bug 1751657] Re: man journalctl gives info about -g option not present in command

2018-02-26 Thread Hans Joachim Desserud

** Tags added: manpage

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

Title:
  man journalctl gives info about -g option not present in command

Status in systemd package in Ubuntu:
  New

Bug description:
  man journalctl documents a --grep option, however:

  $ journalctl -g a
  journalctl: invalid option -- 'g'

  $ journalctl --grep a
  Compiled without pattern matching support

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Sun Feb 25 21:53:29 2018
  InstallationDate: Installed on 2017-06-21 (248 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. 
   Bus 001 Device 003: ID 0c45:6713 Microdia 
   Bus 001 Device 004: ID 10d7:1102  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9560
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed 
root=UUID=18bdf6ee-e85b-4eb2-8fd1-68cf15fe1167 ro quiet splash 
acpi_rev_override=5 pci=noaer vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: Upgraded to bionic on 2018-02-17 (8 days ago)
  dmi.bios.date: 12/15/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.0
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd12/15/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1751657/+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 1700619] Re: package gtk-update-icon-cache (not installed) failed to install/upgrade: sub-processo novo script pre-installation retornou estado de saída de erro 2

This is an unsupported release now. Please think to install the next LTS
'Bionic 18.04'

http://cdimage.ubuntu.com/lubuntu-next/daily-live/current/
https://www.omgubuntu.co.uk/2018/02/ubuntu-18-04-minimal-install-option

** Changed in: gtk+3.0 (Ubuntu)
   Status: New => Invalid

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

Title:
  package gtk-update-icon-cache (not installed) failed to
  install/upgrade: sub-processo novo script pre-installation retornou
  estado de saída de erro 2

Status in gtk+3.0 package in Ubuntu:
  Invalid

Bug description:
  the problem start after a did a update of ubuntu core.

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gtk-update-icon-cache (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Mon Jun 26 14:00:33 2017
  ErrorMessage: sub-processo novo script pre-installation retornou estado de 
saída de erro 2
  InstallationDate: Installed on 2016-10-05 (264 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1.1
   apt  1.2.20
  SourcePackage: gtk+3.0
  Title: package gtk-update-icon-cache (not installed) failed to 
install/upgrade: sub-processo novo script pre-installation retornou estado de 
saída de erro 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1700619/+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 1750379] Re: Distortion Realtek ALC887

2018-02-26 Thread fleamour

I installed Win 10 & still had audio glitching. This is not a software
bug, got working in Mint 18.3 (will now test Ubuntu Beaver.) I have a
3.5mm audio splitter for double monitor set up. The upper one is toast
(soundwise). Whether this is due to running full amplification not
sure?!? What say you?

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

Title:
  Distortion Realtek ALC887

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Sounds can distort even when not amplified. Amplification worked well
  for years before recent PulseAudio update. The audio is Realtek ALC887
  under an IntelG41 Chipset with GA-G41M-Combo main board;

  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  I am seeking to engage upstream for April LTS release. Windows have
  abandoned this esoteric hardware! Please Ubuntu! Keep a C2D user
  going!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu6
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fleamour   1049 F pulseaudio
   /dev/snd/controlC2:  fleamour   1049 F pulseaudio
   /dev/snd/controlC0:  fleamour   1049 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 19 13:54:33 2018
  InstallationDate: Installed on 2018-02-19 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FB
  dmi.board.name: G41M-Combo
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFB:bd10/25/2012:svnGigabyteTechnologyCo.,Ltd.:pnG41M-Combo:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG41M-Combo:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: G41M-Combo
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750379/+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 1701157] Re: package libpam-systemd:amd64 231-9ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

This is an unsupported release now. Please think to install the next LTS
'Bionic 18.04'

http://cdimage.ubuntu.com/lubuntu-next/daily-live/current/
https://www.omgubuntu.co.uk/2018/02/ubuntu-18-04-minimal-install-option

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

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

Title:
  package libpam-systemd:amd64 231-9ubuntu5 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  unknown the system want to send the bug report

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: libpam-systemd:amd64 231-9ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-56.61-generic 4.8.17
  Uname: Linux 4.8.0-56-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.3
  Architecture: amd64
  Date: Wed Jun 28 15:23:07 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2016-05-02 (422 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1.1
   apt  1.3.5
  SourcePackage: systemd
  Title: package libpam-systemd:amd64 231-9ubuntu5 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1701157/+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 1750780] Re: Race with local file systems can make open-vm-tools fail to start

2018-02-26 Thread Scott Moser

I agree with reverting change in bionic, and that xenial still needs
some fix.

I recreated your failure in xenial and agree with your change there.
I used this job as it actually tries to write to the private tmp.

If I change 'ExecStart' below to be  just '/bin/true' like in your job,
it does not fail (status says 'code=exited, status=0/SUCCESS).  But the
command below seems to never get exited (it produces no output).

So it seems to me that the 'Read only filesystem' error is not even from
the service itself, but rather from systemd, and also dependent on the
content in ExecStart.

$ cat /lib/systemd/system/my-ptmp-test.service
[Unit]
Description=foo
DefaultDependencies=no
[Service]
Type=oneshot
PrivateTmp=yes
ExecStart=/bin/sh -ec 'f=/tmp/my.txt; uptime > $f; echo ==; cat $f; echo ==; 
cat /proc/mounts'
[Install]
WantedBy=multi-user.target


Then we can see the same failure:

$ journalctl -o short-monotonic --no-pager | grep --context=2 my-ptmp-test
[7.715220] xenial-20180223-142555 systemd[1]: Created slice System Slice.
[7.718923] xenial-20180223-142555 systemd[1]: Created slice 
system-systemd\x2dfsck.slice.
[7.740250] xenial-20180223-142555 systemd[1]: my-ptmp-test.service: Failed 
to run 'start' task: Read-only file system
[7.749135] xenial-20180223-142555 systemd[1]: Failed to start foo.
[7.754114] xenial-20180223-142555 systemd[1]: my-ptmp-test.service: Unit 
entered failed state.
[7.760217] xenial-20180223-142555 systemd[1]: my-ptmp-test.service: Failed 
with result 'resources'.
[7.764170] xenial-20180223-142555 systemd[1]: Starting Load Kernel 
Modules...
[7.775558] xenial-20180223-142555 systemd[1]: Starting Journal Service...

$ systemctl status my-ptmp-test.service --no-pager --full
● my-ptmp-test.service - foo
   Loaded: loaded (/lib/systemd/system/my-ptmp-test.service; enabled; vendor 
preset: enabled)
   Active: failed (Result: resources)

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

Title:
  Race with local file systems can make open-vm-tools fail to start

Status in cloud-init:
  Invalid
Status in open-vm-tools package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in open-vm-tools source package in Xenial:
  Triaged
Status in systemd source package in Xenial:
  New
Status in open-vm-tools package in Debian:
  Incomplete

Bug description:
  Since the change in [1] open-vm-tools-service starts very (very) early.
  Not so much due to the 
  Before=cloud-init-local.service
  But much more by
  DefaultDependencies=no

  That can trigger an issue that looks like
  root@ubuntuguest:~# systemctl status -l open-vm-tools.service
  ● open-vm-tools.service - Service for virtual machines hosted on VMware
 Loaded: loaded (/lib/systemd/system/open-vm-tools.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: resources)

  
  As it is right now open-vm-tools can race with the other early start and then 
fail.
  In detail one can find a message like:
open-vm-tools.service: Failed to run 'start' task: Read-only file system"

  This is due to privtaeTmp=yes which is also set needing a writable
  /var/tmp [2]

  To ensure this works PrivateTmp would have to be removed (not good) or some 
after dependencies added that make this work reliably.
  I added
  After=local-fs.target
  which made it work for me in 3/3 tests.

  I' like to have an ack by the cloud-init Team that this does not totally kill 
the originally intended Before=cloud-init-local.service
  I think it does not as local-fs can complete before cloud-init-local, then 
open-vm-tools can initialize and finally cloud-init-local can pick up the data.

  To summarize:
  # cloud-init-local #
  DefaultDependencies=no
  Wants=network-pre.target
  After=systemd-remount-fs.service
  Before=NetworkManager.service
  Before=network-pre.target
  Before=shutdown.target
  Before=sysinit.target
  Conflicts=shutdown.target
  RequiresMountsFor=/var/lib/cloud

  # open-vm-tools #
  DefaultDependencies=no
  Before=cloud-init-local.service

  Proposed is to add to the latter:
  After=local-fs.target

  [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859677
  [2]: https://github.com/systemd/systemd/issues/5610

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1750780/+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 1751871] [NEW] Installation of Audacity causes headphone output to no longer work

Public bug reported:

OS: Linux Mint 18.2
Audacity version: 2.2.2 from ubuntuhandbook repo
Alsa log: 
http://www.alsa-project.org/db/?f=46cdccac7c37f25f2acd6c567ae56cd58aba2f0b

I just installed Audacity to make a quick edit on a MP3 file. I
installed 2.1.2 from the default Linux Mint 18 repo, opened Audacity and
selected my file. It played over my headphones just fine. I closed
Audacity, then immediately opened it again to select a different file to
edit. As Audacity opened I heard an audible 'click' over my headphones.
I could no longer hear anything over my headphones whether in Audacity
or via browser/youtube or other media player.

I discovered an AskUbuntu question with the same problem. An answer
there said that we just needed to open Audacity and select Internal
Mic:0. Tried that, and presto had audio over my headphones again.

Another answer on the same AU question recommended upgrading from 2.1.2
to the current (then) version of 2.2.0 to get around the bug in the
future. So, I uninstalled 2.1.2, and installed 2.2.2 from the
ubuntuhandbook repo.

Opened Audacity 2.2.2, only to discover that I now have no headphone
volume again, and this time changing the output to Internal Mic:0 did
not work. In fact, I cannot get headphone output on any of the 10 output
options. Nothing plays over headphones now, not youtube/browser, not
files in VLC.

All of this occurred in less than 5 minutes, and I am left without an
ability to use my laptop's headphone jack.

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


** Tags: audacity headphones

** Summary changed:

- lost headphone output
+ Installation of Audacity causes headphone output to no longer work

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

Title:
  Installation of Audacity causes headphone output to no longer work

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  OS: Linux Mint 18.2
  Audacity version: 2.2.2 from ubuntuhandbook repo
  Alsa log: 
http://www.alsa-project.org/db/?f=46cdccac7c37f25f2acd6c567ae56cd58aba2f0b

  I just installed Audacity to make a quick edit on a MP3 file. I
  installed 2.1.2 from the default Linux Mint 18 repo, opened Audacity
  and selected my file. It played over my headphones just fine. I closed
  Audacity, then immediately opened it again to select a different file
  to edit. As Audacity opened I heard an audible 'click' over my
  headphones. I could no longer hear anything over my headphones whether
  in Audacity or via browser/youtube or other media player.

  I discovered an AskUbuntu question with the same problem. An answer
  there said that we just needed to open Audacity and select Internal
  Mic:0. Tried that, and presto had audio over my headphones again.

  Another answer on the same AU question recommended upgrading from
  2.1.2 to the current (then) version of 2.2.0 to get around the bug in
  the future. So, I uninstalled 2.1.2, and installed 2.2.2 from the
  ubuntuhandbook repo.

  Opened Audacity 2.2.2, only to discover that I now have no headphone
  volume again, and this time changing the output to Internal Mic:0 did
  not work. In fact, I cannot get headphone output on any of the 10
  output options. Nothing plays over headphones now, not
  youtube/browser, not files in VLC.

  All of this occurred in less than 5 minutes, and I am left without an
  ability to use my laptop's headphone jack.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1751871/+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 1751871] Re: Installation of Audacity causes headphone output to no longer work

Additionally, if I unplug my headphones I hear audio over my laptop's
speakers.   I cannot listen to audio over the speakers at work however,
so this is not a helpful workaround.

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

Title:
  Installation of Audacity causes headphone output to no longer work

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  OS: Linux Mint 18.2
  Audacity version: 2.2.2 from ubuntuhandbook repo
  Alsa log: 
http://www.alsa-project.org/db/?f=46cdccac7c37f25f2acd6c567ae56cd58aba2f0b

  I just installed Audacity to make a quick edit on a MP3 file. I
  installed 2.1.2 from the default Linux Mint 18 repo, opened Audacity
  and selected my file. It played over my headphones just fine. I closed
  Audacity, then immediately opened it again to select a different file
  to edit. As Audacity opened I heard an audible 'click' over my
  headphones. I could no longer hear anything over my headphones whether
  in Audacity or via browser/youtube or other media player.

  I discovered an AskUbuntu question with the same problem. An answer
  there said that we just needed to open Audacity and select Internal
  Mic:0. Tried that, and presto had audio over my headphones again.

  Another answer on the same AU question recommended upgrading from
  2.1.2 to the current (then) version of 2.2.0 to get around the bug in
  the future. So, I uninstalled 2.1.2, and installed 2.2.2 from the
  ubuntuhandbook repo.

  Opened Audacity 2.2.2, only to discover that I now have no headphone
  volume again, and this time changing the output to Internal Mic:0 did
  not work. In fact, I cannot get headphone output on any of the 10
  output options. Nothing plays over headphones now, not
  youtube/browser, not files in VLC.

  All of this occurred in less than 5 minutes, and I am left without an
  ability to use my laptop's headphone jack.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1751871/+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 1257956] Re: Headphones stopped working after use of Audacity. They are detected, but no sound is produced.

I just installed Audacity to make a quick edit on an a MP3 file.  I
installed 2.1.2 from the default Linux Mint repo, opened Audacity and
selected my file.  It played over my headphones just fine.   I closed
Audacity, then immediately opened it again to select a different file to
edit.  As Audacity opened I heard an audible 'click' over my headphones.
I could no longer hear anything over my headphones whether in Audacity
or via browser/youtube or other media player.

I discovered an AskUbuntu question with the same problem.  An answer
there said that we just needed to open Audacity and select Internal
Mic:0.   Tried that, and presto had audio over my headphones again.

Another answer on the same question recommended upgrading from 2.1.2 to
the current (then) version of 2.2.0 to get around the bug in the future.
I then uninstalled 2.1.2, and installed 2.2.2 from the ubuntuhandbook
repo.

Opened Audacity 2.2.2, only to discover that I now have no headphone
volume again, and this time changing the output to Internal Mic:0 did
not work.  In fact, I cannot get headphone output on any of the 10
output options.   Nothing plays over headphones now, not
youtube/browser, not files in VLC.

Installing Audacity has literally broken my laptops ability to listen to
music over headphones.

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

Title:
  Headphones stopped working after use of Audacity. They are detected,
  but no sound is produced.

Status in alsa-driver package in Ubuntu:
  Expired

Bug description:
  I'm running 13.10 and the latest GNOME. I've just fresh installed
  everything and the problem has occured again the same way. I would
  like to be able to use audacity, but I suppose in the mean time I will
  just reinstall everything.

  Steps to reproduce : 
  1) Install audacity 2.0.3 from official Ubuntu repositories
  2) Open Audacity and play something with it
  3) That's it : no more headphones sound.

  
  - alsa log created with 'alsa-info.sh' 
(https://wiki.ubuntu.com/Audio/AlsaInfo) : http://paste.ubuntu.com/7131709/

  - pulse log when I plug in my headphones, I run a MP3 file with VLC,
  close VLC then unplug headphones
  (https://wiki.ubuntu.com/PulseAudio/Log) :
  http://paste.ubuntu.com/7131713/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1257956/+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 1613184] Re: method mirror broken at 1.3

2018-02-26 Thread Bojan Markovic

I am still having this error if I select mirror method on Zesty with apt
1.4.6

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

Title:
  method mirror broken at 1.3

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Released
Status in apt source package in Zesty:
  Fix Committed

Bug description:
  [Impact]
  The mirror method always dies with a SEGV. It does not initialize _system but 
calls a function that sometimes uses it.

  [Test case]
  Use a mirror sources.list entry like

  deb mirror://mirrors.ubuntu.com/mirrors.txt zesty main restricted
  universe multiverse

  [Regression potential]
  The fix is small, and simply avoids using _system if _system is NULL in the 
called method. There should not be any regressions due to this.

  
https://anonscm.debian.org/cgit/apt/apt.git/commit/?id=cba5c5a26a9bf00724f8ea647ac61b30e32734ba

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1613184/+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 1751871] Re: Installation of Audacity causes headphone output to no longer work

Opened alsamixer and ensured that no channels are muted (all are showing
the green oo symbol), and that all of the channels have volumes as high
as they will go.   Still no luck in getting audio to pipe back through
my headphone jack.

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

Title:
  Installation of Audacity causes headphone output to no longer work

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  OS: Linux Mint 18.2
  Audacity version: 2.2.2 from ubuntuhandbook repo
  Alsa log: 
http://www.alsa-project.org/db/?f=46cdccac7c37f25f2acd6c567ae56cd58aba2f0b

  I just installed Audacity to make a quick edit on a MP3 file. I
  installed 2.1.2 from the default Linux Mint 18 repo, opened Audacity
  and selected my file. It played over my headphones just fine. I closed
  Audacity, then immediately opened it again to select a different file
  to edit. As Audacity opened I heard an audible 'click' over my
  headphones. I could no longer hear anything over my headphones whether
  in Audacity or via browser/youtube or other media player.

  I discovered an AskUbuntu question with the same problem. An answer
  there said that we just needed to open Audacity and select Internal
  Mic:0. Tried that, and presto had audio over my headphones again.

  Another answer on the same AU question recommended upgrading from
  2.1.2 to the current (then) version of 2.2.0 to get around the bug in
  the future. So, I uninstalled 2.1.2, and installed 2.2.2 from the
  ubuntuhandbook repo.

  Opened Audacity 2.2.2, only to discover that I now have no headphone
  volume again, and this time changing the output to Internal Mic:0 did
  not work. In fact, I cannot get headphone output on any of the 10
  output options. Nothing plays over headphones now, not
  youtube/browser, not files in VLC.

  All of this occurred in less than 5 minutes, and I am left without an
  ability to use my laptop's headphone jack.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1751871/+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 1705297] LightdmLog.txt

apport information

** Attachment added: "LightdmLog.txt"
   
https://bugs.launchpad.net/bugs/1705297/+attachment/5063890/+files/LightdmLog.txt

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

Title:
  login after booting hangs

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The following occurs occasionally (seemingly at random):

  After booting and logging in only the background image is shown, and no 
action is possbile.
  After switching to tty1, logging in and performing a shutdown/reboot
  everything is o.k.

  (Sometimes -- seldomly -- on tty1 an error message was shown.)

  peter@TP:~/bin$ uname --all
  Linux TP 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Skylake Integrated Graphics [17aa:2231]
  InstallationDate: Installed on 2016-11-12 (471 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 138a:0017 Validity Sensors, Inc. Fingerprint Reader
   Bus 001 Device 003: ID 04ca:7058 Lite-On Technology Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20FJS36700
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic 
root=UUID=929e493d-18e2-41ed-a0a1-b34fd11acd2e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-116-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/20/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1KET21W (1.08 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FJS36700
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1KET21W(1.08):bd04/20/2016:svnLENOVO:pn20FJS36700:pvrThinkPadT560:rvnLENOVO:rn20FJS36700:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20FJS36700
  dmi.product.version: ThinkPad T560
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.3+16.04.20171116-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1705297/+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 1705297] Lspci.txt

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1705297/+attachment/5063891/+files/Lspci.txt

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

Title:
  login after booting hangs

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The following occurs occasionally (seemingly at random):

  After booting and logging in only the background image is shown, and no 
action is possbile.
  After switching to tty1, logging in and performing a shutdown/reboot
  everything is o.k.

  (Sometimes -- seldomly -- on tty1 an error message was shown.)

  peter@TP:~/bin$ uname --all
  Linux TP 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Skylake Integrated Graphics [17aa:2231]
  InstallationDate: Installed on 2016-11-12 (471 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 138a:0017 Validity Sensors, Inc. Fingerprint Reader
   Bus 001 Device 003: ID 04ca:7058 Lite-On Technology Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20FJS36700
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic 
root=UUID=929e493d-18e2-41ed-a0a1-b34fd11acd2e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-116-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/20/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1KET21W (1.08 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FJS36700
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1KET21W(1.08):bd04/20/2016:svnLENOVO:pn20FJS36700:pvrThinkPadT560:rvnLENOVO:rn20FJS36700:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20FJS36700
  dmi.product.version: ThinkPad T560
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.3+16.04.20171116-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1705297/+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 1705297] DpkgLog.txt

apport information

** Attachment added: "DpkgLog.txt"
   
https://bugs.launchpad.net/bugs/1705297/+attachment/5063887/+files/DpkgLog.txt

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

Title:
  login after booting hangs

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The following occurs occasionally (seemingly at random):

  After booting and logging in only the background image is shown, and no 
action is possbile.
  After switching to tty1, logging in and performing a shutdown/reboot
  everything is o.k.

  (Sometimes -- seldomly -- on tty1 an error message was shown.)

  peter@TP:~/bin$ uname --all
  Linux TP 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Skylake Integrated Graphics [17aa:2231]
  InstallationDate: Installed on 2016-11-12 (471 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 138a:0017 Validity Sensors, Inc. Fingerprint Reader
   Bus 001 Device 003: ID 04ca:7058 Lite-On Technology Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20FJS36700
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic 
root=UUID=929e493d-18e2-41ed-a0a1-b34fd11acd2e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-116-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/20/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1KET21W (1.08 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FJS36700
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1KET21W(1.08):bd04/20/2016:svnLENOVO:pn20FJS36700:pvrThinkPadT560:rvnLENOVO:rn20FJS36700:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20FJS36700
  dmi.product.version: ThinkPad T560
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.3+16.04.20171116-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1705297/+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 1717224] Re: virsh start of virtual guest domain fails with internal error due to low default aio-max-nr sysctl value

2018-02-26 Thread Seth Forshee

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

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

Title:
  virsh start of virtual guest domain fails with internal error due to
  low default aio-max-nr sysctl value

Status in Ubuntu on IBM z Systems:
  In Progress
Status in kvm package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Fix Released
Status in procps package in Ubuntu:
  New
Status in linux source package in Xenial:
  In Progress
Status in procps source package in Xenial:
  New
Status in linux source package in Zesty:
  Won't Fix
Status in procps source package in Zesty:
  Won't Fix
Status in linux source package in Artful:
  In Progress
Status in procps source package in Artful:
  New

Bug description:
  Starting virtual guests via on Ubuntu 16.04.2 LTS installed with its
  KVM hypervisor on an IBM Z14 system LPAR fails on the 18th guest with
  the following error:

  root@zm93k8:/rawimages/ubu1604qcow2# virsh start zs93kag70038
  error: Failed to start domain zs93kag70038
  error: internal error: process exited while connecting to monitor: 
2017-07-26T01:48:26.352534Z qemu-kvm: -drive 
file=/guestimages/data1/zs93kag70038.qcow2,format=qcow2,if=none,id=drive-virtio-disk0,cache=none,aio=native:
 Could not open backing file: Could not set AIO state: Inappropriate ioctl for 
device

  The previous 17 guests started fine:

  root@zm93k8# virsh start zs93kag70020
  Domain zs93kag70020 started

  root@zm93k8# virsh start zs93kag70021
  Domain zs93kag70021 started

  .
  .

  root@zm93k8:/rawimages/ubu1604qcow2# virsh start zs93kag70036
  Domain zs93kag70036 started

  
  We ended up fixing the issue by adding the following line to /etc/sysctl.conf 
: 

  fs.aio-max-nr = 4194304

  ... then, reload the sysctl config file:

  root@zm93k8:/etc# sysctl -p /etc/sysctl.conf
  fs.aio-max-nr = 4194304

  
  Now, we're able to start more guests...

  root@zm93k8:/etc# virsh start zs93kag70036
  Domain zs93kag70036 started

  
  The default value was originally set to 65535: 

  root@zm93k8:/rawimages/ubu1604qcow2# cat /proc/sys/fs/aio-max-nr
  65536

  
  Note, we chose the 4194304 value, because this is what our KVM on System Z 
hypervisor ships as its default value.  Eg.  on our zKVM system: 

  [root@zs93ka ~]# cat /proc/sys/fs/aio-max-nr
  4194304

  ubuntu@zm93k8:/etc$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 16.04.2 LTS
  Release:16.04
  Codename:   xenial
  ubuntu@zm93k8:/etc$

  ubuntu@zm93k8:/etc$ dpkg -s qemu-kvm |grep Version
  Version: 1:2.5+dfsg-5ubuntu10.8

  Is something already documented for Ubuntu KVM users warning them about the 
low default value, and some guidance as to
  how to select an appropriate value?   Also, would you consider increasing the 
default aio-max-nr value to something much
  higher, to accommodate significantly more virtual guests?  

  Thanks!

  ---uname output---
  ubuntu@zm93k8:/etc$ uname -a Linux zm93k8 4.4.0-62-generic #83-Ubuntu SMP Wed 
Jan 18 14:12:54 UTC 2017 s390x s390x s390x GNU/Linux
   
  Machine Type = z14 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   See Problem Description.

  The problem was happening a week ago, so this may not reflect that
  activity.

  This file was collected on Aug 7, one week after we were hitting the
  problem.  If I need to reproduce the problem and get fresh data,
  please let me know.

  /var/log/messages doesn't exist on this system, so I provided syslog
  output instead.

  All data have been collected too late after the problem was observed
  over a week ago.  If you need me to reproduce the problem and get new
  data, please let me know.  That's not a problem.

  Also, we would have to make special arrangements for login access to
  these systems.  I'm happy to run traces and data collection for you as
  needed.  If that's not sufficient, then we'll explore log in access
  for you.

  Thanks...   - Scott G.

  
  I was able to successfully recreate the problem and captured / attached new 
debug docs. 

  Recreate procedure:

  #  Started out with no virtual guests running.

  ubuntu@zm93k8:/home/scottg$ virsh list
   IdName   State
  

  
  # Set fs.aio-max-nr back to original Ubuntu "out of the box" value in 
/etc/sysctl.conf

  ubuntu@zm93k8:~$ tail -1 /etc/sysctl.conf
  fs.aio-max-nr = 65536

  
  ## sysctl -a shows: 

  fs.aio-max-nr = 4194304

  
  ##  Reload sysctl.

  ubuntu@zm93k8:~$ sudo sysctl -p /etc/sysctl.conf
  fs.aio-max-nr = 65536
  ubuntu@zm93k8:~$

  ubuntu@zm93k8:~$ sudo sysctl -a |grep fs.aio-max-nr
  fs.aio-max-nr = 65536

  ubuntu@zm93k8:~$  cat /proc/sys/fs/aio-max-nr
  65536


  # Attempt to start more than 17 qcow2 virtual guests on the Ubuntu

[Touch-packages] [Bug 1705297] Re: login after booting hangs

2018-02-26 Thread Christopher M. Penalver

Peter Schmitt, to see if this is already resolved in your release, could
you please update your HWE stack as per
https://wiki.ubuntu.com/Kernel/LTSEnablementStack and advise to the
results?

** Tags added: bios-outdated-1.23

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

Title:
  login after booting hangs

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The following occurs occasionally (seemingly at random):

  After booting and logging in only the background image is shown, and no 
action is possbile.
  After switching to tty1, logging in and performing a shutdown/reboot
  everything is o.k.

  (Sometimes -- seldomly -- on tty1 an error message was shown.)

  peter@TP:~/bin$ uname --all
  Linux TP 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Skylake Integrated Graphics [17aa:2231]
  InstallationDate: Installed on 2016-11-12 (471 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 138a:0017 Validity Sensors, Inc. Fingerprint Reader
   Bus 001 Device 003: ID 04ca:7058 Lite-On Technology Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20FJS36700
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic 
root=UUID=929e493d-18e2-41ed-a0a1-b34fd11acd2e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-116-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/20/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1KET21W (1.08 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FJS36700
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1KET21W(1.08):bd04/20/2016:svnLENOVO:pn20FJS36700:pvrThinkPadT560:rvnLENOVO:rn20FJS36700:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20FJS36700
  dmi.product.version: ThinkPad T560
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.3+16.04.20171116-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1705297/+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 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04)

2018-02-26 Thread Mythological

Silvano (spaccabyte), if you never added that PPA (and the majority of
Ubuntu users will not have) then there is nothing to remove.  In that
case, you probably have the "standard" gcc and could just follow the
instructions at
https://ubuntuforums.org/showthread.php?t=2385621=f41dc2da85d14b7d5854118ae4594254=13742673#post13742673
in post #7.  You may need to exit and restart Synaptic during the
process, if it won't let you reinstall the kernel after removing it.

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

Title:
  4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and
  16.04)

Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Running fine with nvidia-384 until this kernel update came along.
  When booted into the new kernel, got super low resolution and nvidia-
  settings was missing most of its functionality - could not change
  resolution.

  Rebooted into 4.4.0-112 kernel and all was well.

  The root cause of the problem has been found to be installing the -116
  kernel without a sufficiently updated version of gcc.  In my case, my
  system received the gcc update AFTER the kernel update.

  Uninstalling the -116 kernel and reinstalling it with the updated
  version of gcc solved the problem for me.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Feb 21 19:23:39 2018
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed
   bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed
   nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller])
     Subsystem: eVga.com. Corp. Device [3842:6253]
  InstallationDate: Installed on 2015-03-03 (1086 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: ASUSTeK COMPUTER INC. M11AD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic 
root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/15/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0302
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M11AD
  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.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: M11AD
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK COMPUTER 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 N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed Feb 21 18:48:14 2018
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.18.3-1ubuntu2.3~trusty4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750937/+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 1705297] CurrentDmesg.txt

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1705297/+attachment/5063885/+files/CurrentDmesg.txt

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

Title:
  login after booting hangs

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The following occurs occasionally (seemingly at random):

  After booting and logging in only the background image is shown, and no 
action is possbile.
  After switching to tty1, logging in and performing a shutdown/reboot
  everything is o.k.

  (Sometimes -- seldomly -- on tty1 an error message was shown.)

  peter@TP:~/bin$ uname --all
  Linux TP 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Skylake Integrated Graphics [17aa:2231]
  InstallationDate: Installed on 2016-11-12 (471 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 138a:0017 Validity Sensors, Inc. Fingerprint Reader
   Bus 001 Device 003: ID 04ca:7058 Lite-On Technology Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20FJS36700
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic 
root=UUID=929e493d-18e2-41ed-a0a1-b34fd11acd2e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-116-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/20/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1KET21W (1.08 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FJS36700
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1KET21W(1.08):bd04/20/2016:svnLENOVO:pn20FJS36700:pvrThinkPadT560:rvnLENOVO:rn20FJS36700:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20FJS36700
  dmi.product.version: ThinkPad T560
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.3+16.04.20171116-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1705297/+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 1705297] Dependencies.txt

apport information

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

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

Title:
  login after booting hangs

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The following occurs occasionally (seemingly at random):

  After booting and logging in only the background image is shown, and no 
action is possbile.
  After switching to tty1, logging in and performing a shutdown/reboot
  everything is o.k.

  (Sometimes -- seldomly -- on tty1 an error message was shown.)

  peter@TP:~/bin$ uname --all
  Linux TP 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Skylake Integrated Graphics [17aa:2231]
  InstallationDate: Installed on 2016-11-12 (471 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 138a:0017 Validity Sensors, Inc. Fingerprint Reader
   Bus 001 Device 003: ID 04ca:7058 Lite-On Technology Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20FJS36700
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic 
root=UUID=929e493d-18e2-41ed-a0a1-b34fd11acd2e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-116-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/20/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1KET21W (1.08 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FJS36700
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1KET21W(1.08):bd04/20/2016:svnLENOVO:pn20FJS36700:pvrThinkPadT560:rvnLENOVO:rn20FJS36700:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20FJS36700
  dmi.product.version: ThinkPad T560
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.3+16.04.20171116-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1705297/+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 1705297] JournalErrors.txt

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1705297/+attachment/5063888/+files/JournalErrors.txt

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

Title:
  login after booting hangs

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The following occurs occasionally (seemingly at random):

  After booting and logging in only the background image is shown, and no 
action is possbile.
  After switching to tty1, logging in and performing a shutdown/reboot
  everything is o.k.

  (Sometimes -- seldomly -- on tty1 an error message was shown.)

  peter@TP:~/bin$ uname --all
  Linux TP 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Skylake Integrated Graphics [17aa:2231]
  InstallationDate: Installed on 2016-11-12 (471 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 138a:0017 Validity Sensors, Inc. Fingerprint Reader
   Bus 001 Device 003: ID 04ca:7058 Lite-On Technology Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20FJS36700
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic 
root=UUID=929e493d-18e2-41ed-a0a1-b34fd11acd2e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-116-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/20/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1KET21W (1.08 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FJS36700
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1KET21W(1.08):bd04/20/2016:svnLENOVO:pn20FJS36700:pvrThinkPadT560:rvnLENOVO:rn20FJS36700:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20FJS36700
  dmi.product.version: ThinkPad T560
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.3+16.04.20171116-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1705297/+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 1705297] Xrandr.txt

apport information

** Attachment added: "Xrandr.txt"
   https://bugs.launchpad.net/bugs/1705297/+attachment/5063902/+files/Xrandr.txt

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

Title:
  login after booting hangs

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The following occurs occasionally (seemingly at random):

  After booting and logging in only the background image is shown, and no 
action is possbile.
  After switching to tty1, logging in and performing a shutdown/reboot
  everything is o.k.

  (Sometimes -- seldomly -- on tty1 an error message was shown.)

  peter@TP:~/bin$ uname --all
  Linux TP 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Skylake Integrated Graphics [17aa:2231]
  InstallationDate: Installed on 2016-11-12 (471 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 138a:0017 Validity Sensors, Inc. Fingerprint Reader
   Bus 001 Device 003: ID 04ca:7058 Lite-On Technology Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20FJS36700
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic 
root=UUID=929e493d-18e2-41ed-a0a1-b34fd11acd2e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-116-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/20/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1KET21W (1.08 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FJS36700
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1KET21W(1.08):bd04/20/2016:svnLENOVO:pn20FJS36700:pvrThinkPadT560:rvnLENOVO:rn20FJS36700:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20FJS36700
  dmi.product.version: ThinkPad T560
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.3+16.04.20171116-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1705297/+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 1705297] LightdmDisplayLog.txt

apport information

** Attachment added: "LightdmDisplayLog.txt"
   
https://bugs.launchpad.net/bugs/1705297/+attachment/5063889/+files/LightdmDisplayLog.txt

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

Title:
  login after booting hangs

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The following occurs occasionally (seemingly at random):

  After booting and logging in only the background image is shown, and no 
action is possbile.
  After switching to tty1, logging in and performing a shutdown/reboot
  everything is o.k.

  (Sometimes -- seldomly -- on tty1 an error message was shown.)

  peter@TP:~/bin$ uname --all
  Linux TP 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Skylake Integrated Graphics [17aa:2231]
  InstallationDate: Installed on 2016-11-12 (471 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 138a:0017 Validity Sensors, Inc. Fingerprint Reader
   Bus 001 Device 003: ID 04ca:7058 Lite-On Technology Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20FJS36700
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic 
root=UUID=929e493d-18e2-41ed-a0a1-b34fd11acd2e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-116-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/20/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1KET21W (1.08 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FJS36700
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1KET21W(1.08):bd04/20/2016:svnLENOVO:pn20FJS36700:pvrThinkPadT560:rvnLENOVO:rn20FJS36700:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20FJS36700
  dmi.product.version: ThinkPad T560
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.3+16.04.20171116-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1705297/+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 1751797] Re: dns resolution only works for domains in 'search'.

2018-02-26 Thread Dan Watkins

Oops, removed the rest of my comment when pasting; I'm also seeing this
issue, but on a wireless interface.

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

Title:
  dns resolution only works for domains in 'search'.

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  After reboot, dns was broken.
  This is a very simple Network Manager managed interface that has dhcp.

  $ nmcli device show enp0s25  | pastebinit
  http://paste.ubuntu.com/p/sMVTdrMBxJ/

  
  I've attached systemd-resolve --status output.

  In order to file the bug I just modified /etc/resolv.conf to put the
  dns server in directly.

  Other information, it seems like it just will only look for dns under
  my search domains from the dhcp server:

  $ systemd-resolve home.mosers.us
  home.mosers.us: 23.28.108.176

  -- Information acquired via protocol DNS in 1.5ms.
  -- Data is authenticated: no

  $ systemd-resolve google.com
  google.com: resolve call failed: No appropriate name servers or networks for 
name found

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 26 09:35:32 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (949 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  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.13.0-32-generic 
root=UUID=f897b32a-eacf-4191-9717-844918947069 ro quiet splash vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.vendor: Intel Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1751797/+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 1751271] Re: sudo apt remove xclip sudo apt sudo E: Sub-process /usr/bin/dpkg returned an error code (1)

2018-02-26 Thread Seth Arnold

Hello Mitya, I think in your case you would be best served by running a
command like:

sudo apt-get install sudo apt ubuntu-minimal

If apt-get is now completely useless, try:

sudo aptitude install sudo apt ubuntu-minimal

If that does not work, then I suggest asking a question on
http://askubuntu.com/

I think askubuntu would also be a good place to look for a Dicter
replacement. I know of translate-shell but it is probably not as
convenient as Dicter.

Thanks

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

Title:
   sudo apt remove xclip sudo apt sudo E: Sub-process /usr/bin/dpkg
  returned an error code (1)

Status in sudo package in Ubuntu:
  New

Bug description:
  При удалении пакетов мною была допущена ошибка в тексте команды. Вот
  полное описание процесса:

  beginner@beginner-desktop:~$ sudo apt remove xclip sudo apt
  Чтение списков пакетов… Готово
  Построение дерева зависимостей   
  Чтение информации о состоянии… Готово
  Следующие пакеты устанавливались автоматически и больше не требуются:
extlinux gdebi-core gnome-icon-theme libgksu2-0 linux-headers-4.10.0-28
linux-headers-4.10.0-28-generic linux-image-4.10.0-28-generic
linux-image-extra-4.10.0-28-generic sudo-ldap unetbootin-translations
  Для их удаления используйте «sudo apt autoremove».
  Будут установлены следующие дополнительные пакеты:
sudo-ldap
  Пакеты, которые будут УДАЛЕНЫ:
apt apt-utils gdebi gksu sudo ubuntu-minimal unattended-upgrades unetbootin
xclip
  НОВЫЕ пакеты, которые будут установлены:
sudo-ldap
  ВНИМАНИЕ: Эти существенно важные пакеты будут удалены.
  НЕ ДЕЛАЙТЕ этого, если вы НЕ представляете себе все возможные последствия!
apt
  обновлено 0, установлено 1 новых пакетов, для удаления отмечено 9 пакетов, и 
0 пакетов не обновлено.
  Необходимо скачать 420 kБ архивов.
  После данной операции, объём занятого дискового пространства уменьшится на 6 
050 kB.
  То, что вы хотите сделать, может иметь нежелательные последствия.
  Чтобы продолжить, введите фразу: «Да, делать, как я скажу!»
   ?] Да, делать, как я скажу!
  Пол:1 http://ru.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
sudo-ldap amd64 1.8.16-0ubuntu1.5 [420 kB]
  Получено 420 kБ за 20с (20,8 kБ/c)
  (Чтение базы данных … на данный момент установлено 307670 файлов и каталогов.)
  Удаляется unattended-upgrades (0.90ubuntu0.9) …
  Удаляется ubuntu-minimal (1.361.1) …
  Удаляется apt-utils (1.2.25) …
  Удаляется apt (1.2.25) …
  Удаляется gdebi (0.9.5.7ubuntu1) …
  Удаляется unetbootin (608-1) …
  Удаляется gksu (2.0.2-9ubuntu1) …
  Удаляется sudo (1.8.16-0ubuntu1.5) …
  You have asked that the sudo package be removed,
  but no root password has been set.
  Without sudo, you may not be able to gain administrative privileges.

  If you would prefer to access the root account with su(1)
  or by logging in directly,
  you must set a root password with "sudo passwd".

  If you have arranged other means to access the root account,
  and you are sure this is what you want,
  you may bypass this check by setting an environment variable 
  (export SUDO_FORCE_REMOVE=yes).

  Refusing to remove sudo.
  dpkg: ошибка при обработке пакета sudo (--remove):
   подпроцесс установлен сценарий pre-removal возвратил код ошибки 1
  Удаляется xclip (0.12+svn84-4) …
  Обрабатываются триггеры для man-db (2.7.5-1) …
  Обрабатываются триггеры для libc-bin (2.23-0ubuntu10) …
  Обрабатываются триггеры для gnome-menus (3.13.3-6ubuntu3.1) …
  Обрабатываются триггеры для desktop-file-utils (0.22-1ubuntu5.1) …
  Обрабатываются триггеры для bamfdaemon (0.5.3~bzr0+16.04.20160824-0ubuntu1) …
  Rebuilding /usr/share/applications/bamf-2.index...
  Обрабатываются триггеры для mime-support (3.59ubuntu1) …
  При обработке следующих пакетов произошли ошибки:
   sudo
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: sudo 1.8.16-0ubuntu1.5
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  Architecture: amd64
  Date: Fri Feb 23 11:53:32 2018
  ErrorMessage: подпроцесс установлен сценарий pre-removal возвратил код ошибки 
1
  InstallationDate: Installed on 2018-01-29 (24 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: sudo
  Title: package sudo 1.8.16-0ubuntu1.5 failed to install/upgrade: подпроцесс 
установлен сценарий pre-removal возвратил код ошибки 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  VisudoCheck:
   /etc/sudoers: parsed OK
   /etc/sudoers.d/README: parsed OK

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to :

[Touch-packages] [Bug 1751797] Re: dns resolution only works for domains in 'search'.

2018-02-26 Thread Dan Watkins

$ nmcli device show wlp3s0 | pastebinit
http://paste.ubuntu.com/p/xJ6YjD8WQ9/

$ systemd-resolve --status | pastebinit
http://paste.ubuntu.com/p/bPDMzY3sYh/

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

Title:
  dns resolution only works for domains in 'search'.

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  After reboot, dns was broken.
  This is a very simple Network Manager managed interface that has dhcp.

  $ nmcli device show enp0s25  | pastebinit
  http://paste.ubuntu.com/p/sMVTdrMBxJ/

  
  I've attached systemd-resolve --status output.

  In order to file the bug I just modified /etc/resolv.conf to put the
  dns server in directly.

  Other information, it seems like it just will only look for dns under
  my search domains from the dhcp server:

  $ systemd-resolve home.mosers.us
  home.mosers.us: 23.28.108.176

  -- Information acquired via protocol DNS in 1.5ms.
  -- Data is authenticated: no

  $ systemd-resolve google.com
  google.com: resolve call failed: No appropriate name servers or networks for 
name found

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 26 09:35:32 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (949 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  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.13.0-32-generic 
root=UUID=f897b32a-eacf-4191-9717-844918947069 ro quiet splash vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.vendor: Intel Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1751797/+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 1745828] Re: [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices

2018-02-26 Thread George Hunter

** Description changed:

  It is ON and VISIBLE in the control panel.  My iPhone can see two other
  devices but it can't see the computer, and the computer  can't see
  anything, even if left searching for tens of minutes.
  
  The previous answers listed below suggest the following diagnostics
  
  Bluetooth not working after update
  How can I make my bluetooth works on Ubuntu 16.04?
  Ubuntu 16.04 bluetooth not working (Dell XPS13)
  Bluetooth (Atheros AR3012) not working on Ubuntu 16.04
  Bluetooth not working on Ubuntu 16.04 LTS
  Bluetooth cannot find any devices
  Stuck on a bluetooth problem
  
  The service seems to be running
  
  /home >sudo service bluetooth status
  ● bluetooth.service - Bluetooth service
-Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset
-Active: active (running) since Thu 2018-01-25 09:16:43 GMT; 1h 46min ago
-  Docs: man:bluetoothd(8)
-  Main PID: 790 (bluetoothd)
-Status: "Running"
-CGroup: /system.slice/bluetooth.service
-└─790 /usr/lib/bluetooth/bluetoothd
+    Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset
+    Active: active (running) since Thu 2018-01-25 09:16:43 GMT; 1h 46min ago
+  Docs: man:bluetoothd(8)
+  Main PID: 790 (bluetoothd)
+    Status: "Running"
+    CGroup: /system.slice/bluetooth.service
+    └─790 /usr/lib/bluetooth/bluetoothd
  
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
- Jan 25 09:18:31 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset 
+ Jan 25 09:18:31 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
- Jan 25 09:20:32 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset 
+ Jan 25 09:20:32 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  
  and not blocked
  
  /home >rfkill list
  0: hci0: Bluetooth
-   Soft blocked: no
-   Hard blocked: no
+  Soft blocked: no
+  Hard blocked: no
  1: phy0: Wireless LAN
-   Soft blocked: no
-   Hard blocked: no
+  Soft blocked: no
+  Hard blocked: no
  
  I have edited /etc/bluetooth/main.conf to include
  
  AutoEnable=true
  
  but I noted that the entire file was commented out.
  
  The kernel seems reasonably up to date
  
-  >uname -a
+  >uname -a
  Linux george-CM6330 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 
22:00:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
  
  I wonder if I need a device driver, but I have no idea how to find out.
  The following diagnostics may help some of you knowledgeable people find
  out.
  
-  >hcitool dev
+  >hcitool dev
  Devices:
-   hci024:0A:64:F5:EE:86
+  hci0 24:0A:64:F5:EE:86
  
  and the output of dmsg is
  
  >dmesg | grep Blue
- [2.030855] usb 1-1.4: Product: Bluetooth Radio 
+ [2.030855] usb 1-1.4: Product: Bluetooth Radio
  [   13.806355] Bluetooth: Core ver 2.22
  [   13.806369] Bluetooth: HCI device and connection manager initialized
  [   13.806372] Bluetooth: HCI socket layer initialized
  [   13.806373] Bluetooth: L2CAP socket layer initialized
  [   13.806377] Bluetooth: SCO socket layer initialized
  [   13.827384] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000a 
lmp_ver=06 lmp_subver=8821
  [   13.827386] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_config.bin
  [   13.865327] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_fw.bin
  [   13.877382] Bluetooth: hci0: rom_version status=0 version=1
  [   13.877387] Bluetooth: cfg_sz 0, total size 17428
  [   16.550280] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   16.550281] Bluetooth: BNEP filters: protocol multicast
  [   16.550284] Bluetooth: BNEP socket layer initialized
  [   27.868345] Bluetooth: RFCOMM TTY layer initialized
  [   27.868350] Bluetooth: RFCOMM socket layer initialized
  [   27.868354] Bluetooth: RFCOMM ver 1.11
  
  and of lsusb is
  
  >lsusb
  Bus 002 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver
  Bus 002 Device 006: ID 04b8:0849 Seiko Epson Corp. Stylus SX205
  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
- Bus 004 Device 002: ID 04e8:6123 Samsung Electronics Co., Ltd 
+ Bus 004 Device 002: ID 04e8:6123 Samsung Electronics Co., Ltd
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0

[Touch-packages] [Bug 1670291] Re: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot

2018-02-26 Thread Damiön la Bagh

Could we please use

$ systemctl reboot
$ systemctl -f reboot
$ systemctl -ff reboot 

instead of poweroff.
 
My machines are spread all around the country I live in. I don't want to have 
to drive hundreds of kilometers to go around to turn on all my machines by hand 
after the upgrade.

Thanks!

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

Title:
  Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot

Status in landscape-client package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Incomplete
Status in landscape-client source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Incomplete

Bug description:
  Used Landscape (Paid Canonical Subscription) to upgrade one of my
  machines.

  Landscape only shows "In Progress" for more than 8 hours now and asked
  for a reboot of the machine in a second alert.

  In the reboot attempt I get the message:
  =
  Failed to set wall message, ignoring: Method "SetWallMessage" with signature 
"sb" on interface "org.freedesktop.login1.Manager" doesn't exist
  Failed to call ScheduleShutdown in logind, proceeding with immediate 
shutdown: Method "ScheduleShutdown" with signature "st" on interface 
"org.freedesktop.login1.Manager" doesn't exist
  =

  Steps to reproduce:
  * Fully updated 14.04.5 machine
  * Open Landscape
  * Choose the machine
  * Choose Packages
  * This computer can be upgraded to a newer release
  * Apply
  * Wait 2 hours
  * Alert comes in a seperate Landscape message Machine is ready for reboot
  * Choose Info... Power
  * Deliver to selected computers as soon as possible
  * Error message

  I found this thread on reddit about this issue maybe the solution can be 
built into the upgrade script
  
https://www.reddit.com/r/linuxquestions/comments/4wy3go/trying_to_run_as_user_instance_but_the_system_has/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1670291/+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 1705297] Re: login after booting hangs

apport information

** Tags added: apport-collected compiz-0.9 ubuntu xenial

** Description changed:

  The following occurs occasionally (seemingly at random):
  
  After booting and logging in only the background image is shown, and no 
action is possbile.
  After switching to tty1, logging in and performing a shutdown/reboot
  everything is o.k.
  
  (Sometimes -- seldomly -- on tty1 an error message was shown.)
  
  peter@TP:~/bin$ uname --all
  Linux TP 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux
+ --- 
+ .tmp.unity_support_test.0:
+  
+ ApportVersion: 2.20.1-0ubuntu2.15
+ Architecture: amd64
+ CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
+ CompositorRunning: compiz
+ CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
+ CompositorUnredirectFSW: true
+ CurrentDesktop: Unity
+ DistUpgraded: Fresh install
+ DistroCodename: xenial
+ DistroRelease: Ubuntu 16.04
+ DistroVariant: ubuntu
+ ExtraDebuggingInterest: Yes
+ GraphicsCard:
+  Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
+Subsystem: Lenovo Skylake Integrated Graphics [17aa:2231]
+ InstallationDate: Installed on 2016-11-12 (471 days ago)
+ InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
+ Lsusb:
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 004: ID 138a:0017 Validity Sensors, Inc. Fingerprint Reader
+  Bus 001 Device 003: ID 04ca:7058 Lite-On Technology Corp. 
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ MachineType: LENOVO 20FJS36700
+ Package: xorg 1:7.7+13ubuntu3
+ PackageArchitecture: amd64
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic 
root=UUID=929e493d-18e2-41ed-a0a1-b34fd11acd2e ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
+ Tags:  xenial ubuntu compiz-0.9
+ Uname: Linux 4.4.0-116-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 04/20/2016
+ dmi.bios.vendor: LENOVO
+ dmi.bios.version: N1KET21W (1.08 )
+ dmi.board.asset.tag: Not Available
+ dmi.board.name: 20FJS36700
+ dmi.board.vendor: LENOVO
+ dmi.board.version: Not Defined
+ dmi.chassis.asset.tag: No Asset Information
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: LENOVO
+ dmi.chassis.version: None
+ dmi.modalias: 
dmi:bvnLENOVO:bvrN1KET21W(1.08):bd04/20/2016:svnLENOVO:pn20FJS36700:pvrThinkPadT560:rvnLENOVO:rn20FJS36700:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
+ dmi.product.name: 20FJS36700
+ dmi.product.version: ThinkPad T560
+ dmi.sys.vendor: LENOVO
+ version.compiz: compiz 1:0.9.12.3+16.04.20171116-0ubuntu1
+ version.ia32-libs: ia32-libs N/A
+ version.libdrm2: libdrm2 2.4.83-1~16.04.1
+ version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
+ version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
+ version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
+ version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
+ version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
+ version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
+ version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
+ version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

** Attachment added: "BootLog.txt"
   
https://bugs.launchpad.net/bugs/1705297/+attachment/5063884/+files/BootLog.txt

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

Title:
  login after booting hangs

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The following occurs occasionally (seemingly at random):

  After booting and logging in only the background image is shown, and no 
action is possbile.
  After switching to tty1, logging in and performing a shutdown/reboot
  everything is o.k.

  (Sometimes -- seldomly -- on tty1 an error message was shown.)

  peter@TP:~/bin$ uname --all
  Linux TP 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Skylake Integrated Graphics

[Touch-packages] [Bug 295832] Re: Alsa does not honor pcm.!default because of /usr/share/alsa/pulse.conf

2018-02-26 Thread Rafael Rubio

This bug isn't fixed already, in 17.10 version I must edit
/usr/share/alsa/alsa.conf.d/pulse.conf and add the asound.conf and
.asoundrc. I have a JAVA app that uses alsa to redirec its audio to a
fifo and I have to make this changes every time ALSA is updated. Please,
reopen the bug or give an alternate solution that doesn't imply editing
this file.

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

Title:
  Alsa does not honor pcm.!default because of /usr/share/alsa/pulse.conf

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Intrepid:
  Fix Released

Bug description:
  SRU information follows:

  Impact statement: Users of Ubuntu 8.10 find that their
  /etc/asound.conf and ~/.asoundrc are ignored due to missing entries in
  /usr/share/alsa/pulse.conf. This symptom affects all users with the
  pulseaudio package installed *and* the daemon (regardless of system-
  wide or per-user session instance) running.

  Bug resolution: The missing lines [referencing /etc/asound.conf and
  ~/.asoundrc] are added to /usr/share/alsa/pulse.conf. The change to
  the errors line mimics libasound2's /usr/share/alsa/alsa.conf [to not
  throw an error upon a missing ~/.asoundrc]. With these changes, users
  of default Ubuntu 8.10 will have their /etc/asound.conf and
  ~/.asoundrc, if extant, honoured with higher priority than the
  configuration shipped by pulseaudio, thereby restoring expected alsa-
  lib runtime conf behaviour (for native ALSA applications) prior to
  intrepid. If either /etc/asound.conf or ~/.asoundrc is missing, the
  current intrepid behaviour of pulseaudio overriding {pcm,ctl}.default
  is retained. This change is shown via Loggerhead here:
  
http://bazaar.launchpad.net/~crimsun/pulseaudio/ubuntu/revision/38?remember=36_revid=36.

  SRU patch:
  http://launchpadlibrarian.net/2123/pulseaudio_0.9.10-2ubuntu9.3.debdiff

  Instructions to reproduce the symptom: Create an ~/.asoundrc with the
  following contents only:

  # --- begin ---
  pcm.!default {
 type plug
 slave hw:5,0
  }

  ctl.!default {
 type hw
 card 5
  }
  # --- end ---

  After a fresh GNOME session login, open Applications> Accessories> Terminal, 
and use `speaker-test -Ddefault -c2' to verify that:
  1) the speaker-test output continues to play (until interrupt, ctrl+c) 
through the PulseAudio-configured default device;
  2) no errors are generated by alsa-lib.

  These two symptoms verify that ~/.asoundrc is ignored.

  Regression potential: Users who have a misconfigured /etc/asound.conf
  or ~/.asoundrc will notice that native ALSA apps refuse to start and
  throw alsa-lib error(s), which can be resolved by removing the
  offending conffile.

  Original description follows:

  Binary package hint: pulseaudio

  Even if I define a pcm.!default section in ~/.asoundrc, /usr/share
  /pulse-alsa.conf overrides this definition, so the default alsa output
  is always pulseaudio.

  If I comment the pcm.!default and ctl.!default in /usr/share/alsa
  /pulse-alsa.conf everything behaves as normal.

  Using Intrepid amd64.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/295832/+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 1751893] [NEW] package bluez 5.37-0ubuntu5.1 failed to install/upgrade: problèmes de dépendances - laissé non configuré

2018-02-26 Thread Claude Camy-Peyret

Public bug reported:

Dear Community manager,

I am not a system specialist and I cannot say more about this problem

Thanks for your help

Claude

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: bluez 5.37-0ubuntu5.1
ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
Uname: Linux 4.4.0-104-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Fri Jan  5 14:52:19 2018
ErrorMessage: problèmes de dépendances - laissé non configuré
InstallationDate: Installed on 2016-07-30 (576 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
InterestingModules: bluetooth
MachineType: Dell Inc. Precision M6500
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-104-generic 
root=UUID=80b71b49-579d-4c19-b1ed-b0f1cee9626e ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.24
SourcePackage: bluez
Title: package bluez 5.37-0ubuntu5.1 failed to install/upgrade: problèmes de 
dépendances - laissé non configuré
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/04/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A10
dmi.board.name: 0R1203
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd06/04/2013:svnDellInc.:pnPrecisionM6500:pvr:rvnDellInc.:rn0R1203:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Precision M6500
dmi.sys.vendor: Dell Inc.
hciconfig:
 
syslog: févr. 26 21:16:01 groix NetworkManager[888]:   [1519676161.1202] 
Loaded device plugin: NMBluezManager 
(/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so)

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


** Tags: amd64 apport-package xenial

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

Title:
  package bluez 5.37-0ubuntu5.1 failed to install/upgrade: problèmes de
  dépendances - laissé non configuré

Status in bluez package in Ubuntu:
  New

Bug description:
  Dear Community manager,

  I am not a system specialist and I cannot say more about this problem

  Thanks for your help

  Claude

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.37-0ubuntu5.1
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Fri Jan  5 14:52:19 2018
  ErrorMessage: problèmes de dépendances - laissé non configuré
  InstallationDate: Installed on 2016-07-30 (576 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  InterestingModules: bluetooth
  MachineType: Dell Inc. Precision M6500
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-104-generic 
root=UUID=80b71b49-579d-4c19-b1ed-b0f1cee9626e ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: bluez
  Title: package bluez 5.37-0ubuntu5.1 failed to install/upgrade: problèmes de 
dépendances - laissé non configuré
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/04/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0R1203
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd06/04/2013:svnDellInc.:pnPrecisionM6500:pvr:rvnDellInc.:rn0R1203:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Precision M6500
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   
  syslog: févr. 26 21:16:01 groix NetworkManager[888]:   
[1519676161.1202] Loaded device plugin: NMBluezManager 
(/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1751893/+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 1751892] [NEW] Unable to set different Scale on different Monitors

2018-02-26 Thread Stephen Ostrow

Public bug reported:

My laptop screen is 3840x2160 while my external monitor is only
1680x1050. In order for the laptop monitor to be usable I have the
scaling set at 200 (this works wonderful). However, when I plug in my
external monitor it is scaled up to 200% as well making it unusable.

Attempting to scale one to 100 and the other 200 looks to be possible;
however, the Apply button keeps appearing and disappearing randomly with
no actual effect.

It looks like practically you can only set one scale for both monitors
even though the UI looks to be letting you do it.

I have tried this on Wayland and Xorg with similar results.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
Uname: Linux 4.13.0-36-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Feb 26 15:12:53 2018
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:83b9]
InstallationDate: Installed on 2018-02-21 (5 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
MachineType: HP HP Spectre x360 Convertible 13-ae0xx
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-36-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/23/2018
dmi.bios.vendor: AMI
dmi.bios.version: F.14
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 83B9
dmi.board.vendor: HP
dmi.board.version: 56.37
dmi.chassis.type: 31
dmi.chassis.vendor: HP
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAMI:bvrF.14:bd01/23/2018:svnHP:pnHPSpectrex360Convertible13-ae0xx:pvr:rvnHP:rn83B9:rvr56.37:cvnHP:ct31:cvrChassisVersion:
dmi.product.family: 103C_5335KV HP Spectre
dmi.product.name: HP Spectre x360 Convertible 13-ae0xx
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
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 artful 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/1751892

Title:
  Unable to set different Scale on different Monitors

Status in xorg package in Ubuntu:
  New

Bug description:
  My laptop screen is 3840x2160 while my external monitor is only
  1680x1050. In order for the laptop monitor to be usable I have the
  scaling set at 200 (this works wonderful). However, when I plug in my
  external monitor it is scaled up to 200% as well making it unusable.

  Attempting to scale one to 100 and the other 200 looks to be possible;
  however, the Apply button keeps appearing and disappearing randomly
  with no actual effect.

  It looks like practically you can only set one scale for both monitors
  even though the UI looks to be letting you do it.

  I have tried this on Wayland and Xorg with similar results.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 26 15:12:53 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation Device [8086:5917] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:83b9]
  InstallationDate: Installed on 2018-02-21 (5 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: HP HP Spectre x360 Convertible 13-ae0xx
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine:

[Touch-packages] [Bug 1751904] [NEW] FILES

2018-02-26 Thread Steve

Public bug reported:

NEEDS BUG FIXED ASAP

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-35.39~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-35-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
Date: Mon Feb 26 15:44:52 2018
SourcePackage: xorg
UpgradeStatus: Upgraded to artful on 2018-02-17 (9 days ago)

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


** Tags: amd64 apport-bug artful

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

Title:
  FILES

Status in xorg package in Ubuntu:
  New

Bug description:
  NEEDS BUG FIXED ASAP

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-35.39~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-35-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Mon Feb 26 15:44:52 2018
  SourcePackage: xorg
  UpgradeStatus: Upgraded to artful on 2018-02-17 (9 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1751904/+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 1705297] xdpyinfo.txt

apport information

** Attachment added: "xdpyinfo.txt"
   
https://bugs.launchpad.net/bugs/1705297/+attachment/5063903/+files/xdpyinfo.txt

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

Title:
  login after booting hangs

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The following occurs occasionally (seemingly at random):

  After booting and logging in only the background image is shown, and no 
action is possbile.
  After switching to tty1, logging in and performing a shutdown/reboot
  everything is o.k.

  (Sometimes -- seldomly -- on tty1 an error message was shown.)

  peter@TP:~/bin$ uname --all
  Linux TP 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Skylake Integrated Graphics [17aa:2231]
  InstallationDate: Installed on 2016-11-12 (471 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 138a:0017 Validity Sensors, Inc. Fingerprint Reader
   Bus 001 Device 003: ID 04ca:7058 Lite-On Technology Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20FJS36700
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic 
root=UUID=929e493d-18e2-41ed-a0a1-b34fd11acd2e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-116-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/20/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1KET21W (1.08 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FJS36700
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1KET21W(1.08):bd04/20/2016:svnLENOVO:pn20FJS36700:pvrThinkPadT560:rvnLENOVO:rn20FJS36700:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20FJS36700
  dmi.product.version: ThinkPad T560
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.3+16.04.20171116-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1705297/+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 1705297] UdevDb.txt

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1705297/+attachment/5063898/+files/UdevDb.txt

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

Title:
  login after booting hangs

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The following occurs occasionally (seemingly at random):

  After booting and logging in only the background image is shown, and no 
action is possbile.
  After switching to tty1, logging in and performing a shutdown/reboot
  everything is o.k.

  (Sometimes -- seldomly -- on tty1 an error message was shown.)

  peter@TP:~/bin$ uname --all
  Linux TP 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Skylake Integrated Graphics [17aa:2231]
  InstallationDate: Installed on 2016-11-12 (471 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 138a:0017 Validity Sensors, Inc. Fingerprint Reader
   Bus 001 Device 003: ID 04ca:7058 Lite-On Technology Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20FJS36700
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic 
root=UUID=929e493d-18e2-41ed-a0a1-b34fd11acd2e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-116-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/20/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1KET21W (1.08 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FJS36700
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1KET21W(1.08):bd04/20/2016:svnLENOVO:pn20FJS36700:pvrThinkPadT560:rvnLENOVO:rn20FJS36700:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20FJS36700
  dmi.product.version: ThinkPad T560
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.3+16.04.20171116-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1705297/+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 1705297] XorgLogOld.txt

apport information

** Attachment added: "XorgLogOld.txt"
   
https://bugs.launchpad.net/bugs/1705297/+attachment/5063901/+files/XorgLogOld.txt

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

Title:
  login after booting hangs

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The following occurs occasionally (seemingly at random):

  After booting and logging in only the background image is shown, and no 
action is possbile.
  After switching to tty1, logging in and performing a shutdown/reboot
  everything is o.k.

  (Sometimes -- seldomly -- on tty1 an error message was shown.)

  peter@TP:~/bin$ uname --all
  Linux TP 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Skylake Integrated Graphics [17aa:2231]
  InstallationDate: Installed on 2016-11-12 (471 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 138a:0017 Validity Sensors, Inc. Fingerprint Reader
   Bus 001 Device 003: ID 04ca:7058 Lite-On Technology Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20FJS36700
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic 
root=UUID=929e493d-18e2-41ed-a0a1-b34fd11acd2e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-116-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/20/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1KET21W (1.08 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FJS36700
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1KET21W(1.08):bd04/20/2016:svnLENOVO:pn20FJS36700:pvrThinkPadT560:rvnLENOVO:rn20FJS36700:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20FJS36700
  dmi.product.version: ThinkPad T560
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.3+16.04.20171116-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1705297/+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 1705297] ProcModules.txt

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1705297/+attachment/5063897/+files/ProcModules.txt

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

Title:
  login after booting hangs

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The following occurs occasionally (seemingly at random):

  After booting and logging in only the background image is shown, and no 
action is possbile.
  After switching to tty1, logging in and performing a shutdown/reboot
  everything is o.k.

  (Sometimes -- seldomly -- on tty1 an error message was shown.)

  peter@TP:~/bin$ uname --all
  Linux TP 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Skylake Integrated Graphics [17aa:2231]
  InstallationDate: Installed on 2016-11-12 (471 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 138a:0017 Validity Sensors, Inc. Fingerprint Reader
   Bus 001 Device 003: ID 04ca:7058 Lite-On Technology Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20FJS36700
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic 
root=UUID=929e493d-18e2-41ed-a0a1-b34fd11acd2e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-116-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/20/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1KET21W (1.08 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FJS36700
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1KET21W(1.08):bd04/20/2016:svnLENOVO:pn20FJS36700:pvrThinkPadT560:rvnLENOVO:rn20FJS36700:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20FJS36700
  dmi.product.version: ThinkPad T560
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.3+16.04.20171116-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1705297/+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 1479559] Re: Headphones Not Working - HP Pavilion g7

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

Title:
  Headphones Not Working - HP Pavilion g7

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  installed a recent update and not long after my headphone jack no longer 
works.
  It would appear that computer is unable to sense that headphones are plugged
  into system and therefore sound continues to play from internal speakers even
  when headphones are plugged in. 

  I have used alsamixer to ensure that the headphone channels are not muted, 
  in addition when I check for the device in pulse audio control, headphones are
  listed as 'unplugged' even when they are plugged in.

  I have also tried reinstalling sound drivers, nothing works.

  This is a nightmare! Please help ASAP!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1479559/+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 1479559] Re: Headphones Not Working - HP Pavilion g7

I have a similar problem documented in
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1751871.
Have you found any solutions since posting this bug report?

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

Title:
  Headphones Not Working - HP Pavilion g7

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  installed a recent update and not long after my headphone jack no longer 
works.
  It would appear that computer is unable to sense that headphones are plugged
  into system and therefore sound continues to play from internal speakers even
  when headphones are plugged in. 

  I have used alsamixer to ensure that the headphone channels are not muted, 
  in addition when I check for the device in pulse audio control, headphones are
  listed as 'unplugged' even when they are plugged in.

  I have also tried reinstalling sound drivers, nothing works.

  This is a nightmare! Please help ASAP!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1479559/+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 1751484] Re: Captive portal browser/device misreported

2018-02-26 Thread Will Cooke

Added to Trello: https://trello.com/c/dxhWtGV6/241-bug1751484-captive-
portal-browser-device-misreported

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

Title:
  Captive portal browser/device misreported

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  
  The browser used in the captive portal system is reported as 'Desktop Safari 
Linux 64'. Could we change this to 'Ubuntu Desktop', please?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1751484/+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 1705297] ProcInterrupts.txt

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1705297/+attachment/5063896/+files/ProcInterrupts.txt

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

Title:
  login after booting hangs

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The following occurs occasionally (seemingly at random):

  After booting and logging in only the background image is shown, and no 
action is possbile.
  After switching to tty1, logging in and performing a shutdown/reboot
  everything is o.k.

  (Sometimes -- seldomly -- on tty1 an error message was shown.)

  peter@TP:~/bin$ uname --all
  Linux TP 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Skylake Integrated Graphics [17aa:2231]
  InstallationDate: Installed on 2016-11-12 (471 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 138a:0017 Validity Sensors, Inc. Fingerprint Reader
   Bus 001 Device 003: ID 04ca:7058 Lite-On Technology Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20FJS36700
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic 
root=UUID=929e493d-18e2-41ed-a0a1-b34fd11acd2e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-116-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/20/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1KET21W (1.08 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FJS36700
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1KET21W(1.08):bd04/20/2016:svnLENOVO:pn20FJS36700:pvrThinkPadT560:rvnLENOVO:rn20FJS36700:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20FJS36700
  dmi.product.version: ThinkPad T560
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.3+16.04.20171116-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1705297/+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 1705297] ProcEnviron.txt

apport information

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

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

Title:
  login after booting hangs

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The following occurs occasionally (seemingly at random):

  After booting and logging in only the background image is shown, and no 
action is possbile.
  After switching to tty1, logging in and performing a shutdown/reboot
  everything is o.k.

  (Sometimes -- seldomly -- on tty1 an error message was shown.)

  peter@TP:~/bin$ uname --all
  Linux TP 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Skylake Integrated Graphics [17aa:2231]
  InstallationDate: Installed on 2016-11-12 (471 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 138a:0017 Validity Sensors, Inc. Fingerprint Reader
   Bus 001 Device 003: ID 04ca:7058 Lite-On Technology Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20FJS36700
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic 
root=UUID=929e493d-18e2-41ed-a0a1-b34fd11acd2e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-116-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/20/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1KET21W (1.08 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FJS36700
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1KET21W(1.08):bd04/20/2016:svnLENOVO:pn20FJS36700:pvrThinkPadT560:rvnLENOVO:rn20FJS36700:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20FJS36700
  dmi.product.version: ThinkPad T560
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.3+16.04.20171116-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1705297/+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 1705297] ProcCpuinfo.txt

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1705297/+attachment/5063893/+files/ProcCpuinfo.txt

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

Title:
  login after booting hangs

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The following occurs occasionally (seemingly at random):

  After booting and logging in only the background image is shown, and no 
action is possbile.
  After switching to tty1, logging in and performing a shutdown/reboot
  everything is o.k.

  (Sometimes -- seldomly -- on tty1 an error message was shown.)

  peter@TP:~/bin$ uname --all
  Linux TP 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Skylake Integrated Graphics [17aa:2231]
  InstallationDate: Installed on 2016-11-12 (471 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 138a:0017 Validity Sensors, Inc. Fingerprint Reader
   Bus 001 Device 003: ID 04ca:7058 Lite-On Technology Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20FJS36700
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic 
root=UUID=929e493d-18e2-41ed-a0a1-b34fd11acd2e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-116-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/20/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1KET21W (1.08 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FJS36700
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1KET21W(1.08):bd04/20/2016:svnLENOVO:pn20FJS36700:pvrThinkPadT560:rvnLENOVO:rn20FJS36700:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20FJS36700
  dmi.product.version: ThinkPad T560
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.3+16.04.20171116-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1705297/+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 1705297] MonitorsUser.xml.txt

apport information

** Attachment added: "MonitorsUser.xml.txt"
   
https://bugs.launchpad.net/bugs/1705297/+attachment/5063892/+files/MonitorsUser.xml.txt

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

Title:
  login after booting hangs

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The following occurs occasionally (seemingly at random):

  After booting and logging in only the background image is shown, and no 
action is possbile.
  After switching to tty1, logging in and performing a shutdown/reboot
  everything is o.k.

  (Sometimes -- seldomly -- on tty1 an error message was shown.)

  peter@TP:~/bin$ uname --all
  Linux TP 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Skylake Integrated Graphics [17aa:2231]
  InstallationDate: Installed on 2016-11-12 (471 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 138a:0017 Validity Sensors, Inc. Fingerprint Reader
   Bus 001 Device 003: ID 04ca:7058 Lite-On Technology Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20FJS36700
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic 
root=UUID=929e493d-18e2-41ed-a0a1-b34fd11acd2e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-116-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/20/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1KET21W (1.08 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FJS36700
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1KET21W(1.08):bd04/20/2016:svnLENOVO:pn20FJS36700:pvrThinkPadT560:rvnLENOVO:rn20FJS36700:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20FJS36700
  dmi.product.version: ThinkPad T560
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.3+16.04.20171116-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1705297/+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 1705297] ProcCpuinfoMinimal.txt

apport information

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

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

Title:
  login after booting hangs

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The following occurs occasionally (seemingly at random):

  After booting and logging in only the background image is shown, and no 
action is possbile.
  After switching to tty1, logging in and performing a shutdown/reboot
  everything is o.k.

  (Sometimes -- seldomly -- on tty1 an error message was shown.)

  peter@TP:~/bin$ uname --all
  Linux TP 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Skylake Integrated Graphics [17aa:2231]
  InstallationDate: Installed on 2016-11-12 (471 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 138a:0017 Validity Sensors, Inc. Fingerprint Reader
   Bus 001 Device 003: ID 04ca:7058 Lite-On Technology Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20FJS36700
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic 
root=UUID=929e493d-18e2-41ed-a0a1-b34fd11acd2e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-116-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/20/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1KET21W (1.08 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FJS36700
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1KET21W(1.08):bd04/20/2016:svnLENOVO:pn20FJS36700:pvrThinkPadT560:rvnLENOVO:rn20FJS36700:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20FJS36700
  dmi.product.version: ThinkPad T560
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.3+16.04.20171116-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1705297/+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 1751797] Re: dns resolution only works for domains in 'search'.

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

** Changed in: systemd (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/1751797

Title:
  dns resolution only works for domains in 'search'.

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  After reboot, dns was broken.
  This is a very simple Network Manager managed interface that has dhcp.

  $ nmcli device show enp0s25  | pastebinit
  http://paste.ubuntu.com/p/sMVTdrMBxJ/

  
  I've attached systemd-resolve --status output.

  In order to file the bug I just modified /etc/resolv.conf to put the
  dns server in directly.

  Other information, it seems like it just will only look for dns under
  my search domains from the dhcp server:

  $ systemd-resolve home.mosers.us
  home.mosers.us: 23.28.108.176

  -- Information acquired via protocol DNS in 1.5ms.
  -- Data is authenticated: no

  $ systemd-resolve google.com
  google.com: resolve call failed: No appropriate name servers or networks for 
name found

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 26 09:35:32 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (949 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  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.13.0-32-generic 
root=UUID=f897b32a-eacf-4191-9717-844918947069 ro quiet splash vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.vendor: Intel Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1751797/+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 1749722] Re: NTP: take into account systemd-timesyncd where present

2018-02-26 Thread Ryan Harper

** Merge proposal linked:
   https://code.launchpad.net/~raharper/cloud-init/+git/cloud-init/+merge/339438

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

Title:
  NTP: take into account systemd-timesyncd where present

Status in cloud-init:
  In Progress
Status in systemd package in Ubuntu:
  New

Bug description:
  Currently, the NTP module configures ntpd during cloud-init install by
  installing and configuring ntpd.

  ntpd competes with systemd-timesyncd on systemd distros like Ubuntu
  Xenial.

  Ideally the NTP module should configure systemd-timesyncd where
  present, falling back to ntpd where not present.

  This stops two separate daemons (ntpd and systemd-timesyncd) competing
  with each other to set the time, where systemd-timesyncd (on Ubuntu at
  least) has an internal hardcoded compiled in timeserver to fall back
  on if no timeserver is configured (which is bad, but what can you do).

  The competing timeserver behaviour is invisible when the machine can
  see the net, but logs this error constantly when the machine cannot
  see the net:

  systemd-timesyncd[527]: Timed out waiting for reply from
  91.189.94.4:123 (ntp.ubuntu.com).

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1749722/+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 1705297] UnitySupportTest.txt

apport information

** Attachment added: "UnitySupportTest.txt"
   
https://bugs.launchpad.net/bugs/1705297/+attachment/5063899/+files/UnitySupportTest.txt

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

Title:
  login after booting hangs

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The following occurs occasionally (seemingly at random):

  After booting and logging in only the background image is shown, and no 
action is possbile.
  After switching to tty1, logging in and performing a shutdown/reboot
  everything is o.k.

  (Sometimes -- seldomly -- on tty1 an error message was shown.)

  peter@TP:~/bin$ uname --all
  Linux TP 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Skylake Integrated Graphics [17aa:2231]
  InstallationDate: Installed on 2016-11-12 (471 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 138a:0017 Validity Sensors, Inc. Fingerprint Reader
   Bus 001 Device 003: ID 04ca:7058 Lite-On Technology Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20FJS36700
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic 
root=UUID=929e493d-18e2-41ed-a0a1-b34fd11acd2e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-116-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/20/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1KET21W (1.08 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FJS36700
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1KET21W(1.08):bd04/20/2016:svnLENOVO:pn20FJS36700:pvrThinkPadT560:rvnLENOVO:rn20FJS36700:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20FJS36700
  dmi.product.version: ThinkPad T560
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.3+16.04.20171116-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1705297/+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 1705297] XorgLog.txt

apport information

** Attachment added: "XorgLog.txt"
   
https://bugs.launchpad.net/bugs/1705297/+attachment/5063900/+files/XorgLog.txt

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

Title:
  login after booting hangs

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The following occurs occasionally (seemingly at random):

  After booting and logging in only the background image is shown, and no 
action is possbile.
  After switching to tty1, logging in and performing a shutdown/reboot
  everything is o.k.

  (Sometimes -- seldomly -- on tty1 an error message was shown.)

  peter@TP:~/bin$ uname --all
  Linux TP 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Skylake Integrated Graphics [17aa:2231]
  InstallationDate: Installed on 2016-11-12 (471 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 138a:0017 Validity Sensors, Inc. Fingerprint Reader
   Bus 001 Device 003: ID 04ca:7058 Lite-On Technology Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20FJS36700
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic 
root=UUID=929e493d-18e2-41ed-a0a1-b34fd11acd2e ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Tags:  xenial ubuntu compiz-0.9
  Uname: Linux 4.4.0-116-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 04/20/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1KET21W (1.08 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FJS36700
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1KET21W(1.08):bd04/20/2016:svnLENOVO:pn20FJS36700:pvrThinkPadT560:rvnLENOVO:rn20FJS36700:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20FJS36700
  dmi.product.version: ThinkPad T560
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.3+16.04.20171116-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1705297/+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 1751916] Re: packagekitd crashed with SIGSEGV in gst_mini_object_unref()

2018-02-26 Thread Apport retracing service

*** This bug is a duplicate of bug 1720694 ***
https://bugs.launchpad.net/bugs/1720694

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

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1751916/+attachment/5063932/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1751916/+attachment/5063934/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1751916/+attachment/5063938/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1751916/+attachment/5063939/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1751916/+attachment/5063940/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1751916/+attachment/5063941/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1751916/+attachment/5063942/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1720694

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  packagekitd crashed with SIGSEGV in gst_mini_object_unref()

Status in packagekit package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  Was coming when I was doing an apt-get dist-upgrade

  It's working stable after that.

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: packagekit 1.1.7-1
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Mon Feb 26 22:43:45 2018
  ExecutablePath: /usr/lib/packagekit/packagekitd
  InstallationDate: Installed on 2018-02-23 (3 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180213)
  ProcCmdline: /usr/lib/packagekit/packagekitd
  SegvAnalysis:
   Segfault happened at: 0x7fcd0bd39880 : mov
0x8(%rbx),%edi
   PC (0x7fcd0bd39880) ok
   source "0x8(%rbx)" (0x0014) not located in a known VMA region (needed 
readable region)!
   destination "%edi" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: packagekit
  StacktraceTop:
   gst_mini_object_unref () from /usr/lib/x86_64-linux-gnu/libgstreamer-1.0.so.0
   GstMatcher::~GstMatcher() () from 
/usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so
   AptIntf::providesCodec(PkgList&, char**) () from 
/usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so
   ?? () from 
/usr/lib/x86_64-linux-gnu/packagekit-backend/libpk_backend_aptcc.so
   ?? ()
  Title: packagekitd crashed with SIGSEGV in gst_mini_object_unref()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/packagekit/+bug/1751916/+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 1750780] Re: Race with local file systems can make open-vm-tools fail to start

2018-02-26 Thread ChristianEhrhardt

Thanks Scott for your cross check.
I wonder why my former test failed on each of my tests without writing, but 
never the less your extended example is great for the systemd issue that 
remains.

Although all of this is still a race, for example with the job above on a 
Xenial container I could not trigger it in several retries (5/5 worked).
Doing the same in a Xenial KVM guest instead triggered it right away, but still 
not on every reboot (3/5 failed).

I hope that helps everybody trying to reproduce this.

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

Title:
  Race with local file systems can make open-vm-tools fail to start

Status in cloud-init:
  Invalid
Status in open-vm-tools package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in open-vm-tools source package in Xenial:
  Triaged
Status in systemd source package in Xenial:
  New
Status in open-vm-tools package in Debian:
  Incomplete

Bug description:
  Since the change in [1] open-vm-tools-service starts very (very) early.
  Not so much due to the 
  Before=cloud-init-local.service
  But much more by
  DefaultDependencies=no

  That can trigger an issue that looks like
  root@ubuntuguest:~# systemctl status -l open-vm-tools.service
  ● open-vm-tools.service - Service for virtual machines hosted on VMware
 Loaded: loaded (/lib/systemd/system/open-vm-tools.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: resources)

  
  As it is right now open-vm-tools can race with the other early start and then 
fail.
  In detail one can find a message like:
open-vm-tools.service: Failed to run 'start' task: Read-only file system"

  This is due to privtaeTmp=yes which is also set needing a writable
  /var/tmp [2]

  To ensure this works PrivateTmp would have to be removed (not good) or some 
after dependencies added that make this work reliably.
  I added
  After=local-fs.target
  which made it work for me in 3/3 tests.

  I' like to have an ack by the cloud-init Team that this does not totally kill 
the originally intended Before=cloud-init-local.service
  I think it does not as local-fs can complete before cloud-init-local, then 
open-vm-tools can initialize and finally cloud-init-local can pick up the data.

  To summarize:
  # cloud-init-local #
  DefaultDependencies=no
  Wants=network-pre.target
  After=systemd-remount-fs.service
  Before=NetworkManager.service
  Before=network-pre.target
  Before=shutdown.target
  Before=sysinit.target
  Conflicts=shutdown.target
  RequiresMountsFor=/var/lib/cloud

  # open-vm-tools #
  DefaultDependencies=no
  Before=cloud-init-local.service

  Proposed is to add to the latter:
  After=local-fs.target

  [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859677
  [2]: https://github.com/systemd/systemd/issues/5610

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1750780/+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 1613184] Re: method mirror broken at 1.3

2018-02-26 Thread Julian Andres Klode

@Bojan The fix would have been in 1.4.8, but zesty is not supported
anymore - please upgrade to artful.

** Changed in: apt (Ubuntu Zesty)
   Status: Fix Committed => Won't Fix

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

Title:
  method mirror broken at 1.3

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Released
Status in apt source package in Zesty:
  Won't Fix

Bug description:
  [Impact]
  The mirror method always dies with a SEGV. It does not initialize _system but 
calls a function that sometimes uses it.

  [Test case]
  Use a mirror sources.list entry like

  deb mirror://mirrors.ubuntu.com/mirrors.txt zesty main restricted
  universe multiverse

  [Regression potential]
  The fix is small, and simply avoids using _system if _system is NULL in the 
called method. There should not be any regressions due to this.

  
https://anonscm.debian.org/cgit/apt/apt.git/commit/?id=cba5c5a26a9bf00724f8ea647ac61b30e32734ba

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1613184/+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 1751871] Re: Installation of Audacity causes headphone output to no longer work

pavucontrol shows signal going to headphones when they are plugged in,
but nothing is playing. If I remove the headphones from the jack,
pavucontrol then shows signal going to speakers (which are working).

** Attachment added: "Screenshot at 2018-02-26 15-07-03.png"

https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1751871/+attachment/5063791/+files/Screenshot%20at%202018-02-26%2015-07-03.png

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

Title:
Installation of Audacity causes headphone output to no longer work

Status in alsa-driver package in Ubuntu:
New

Bug description:
OS: Linux Mint 18.2
Audacity version: 2.2.2 from ubuntuhandbook repo
Alsa log:
http://www.alsa-project.org/db/?f=46cdccac7c37f25f2acd6c567ae56cd58aba2f0b

I just installed Audacity to make a quick edit on a MP3 file. I
installed 2.1.2 from the default Linux Mint 18 repo, opened Audacity
and selected my file. It played over my headphones just fine. I closed
Audacity, then immediately opened it again to select a different file
to edit. As Audacity opened I heard an audible 'click' over my
headphones. I could no longer hear anything over my headphones whether
in Audacity or via browser/youtube or other media player.

I discovered an AskUbuntu question with the same problem. An answer
there said that we just needed to open Audacity and select Internal
Mic:0. Tried that, and presto had audio over my headphones again.

Another answer on the same AU question recommended upgrading from
2.1.2 to the current (then) version of 2.2.0 to get around the bug in
the future. So, I uninstalled 2.1.2, and installed 2.2.2 from the
ubuntuhandbook repo.

Opened Audacity 2.2.2, only to discover that I now have no headphone
volume again, and this time changing the output to Internal Mic:0 did
not work. In fact, I cannot get headphone output on any of the 10
output options. Nothing plays over headphones now, not
youtube/browser, not files in VLC.

All of this occurred in less than 5 minutes, and I am left without an
ability to use my laptop's headphone jack.

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

Re: [Touch-packages] [Bug 1751271] Re: sudo apt remove xclip sudo apt sudo E: Sub-process /usr/bin/dpkg returned an error code (1)

2018-02-26 Thread mitya

Thank you very much for your help. Linux Ubuntu - very not bad. :-)

On 27.02.2018 1:02, Seth Arnold wrote:
> Hello Mitya, I think in your case you would be best served by running a
> command like:
>
> sudo apt-get install sudo apt ubuntu-minimal
>
> If apt-get is now completely useless, try:
>
> sudo aptitude install sudo apt ubuntu-minimal
>
> If that does not work, then I suggest asking a question on
> http://askubuntu.com/
>
> I think askubuntu would also be a good place to look for a Dicter
> replacement. I know of translate-shell but it is probably not as
> convenient as Dicter.
>
> Thanks
>

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

Title:
   sudo apt remove xclip sudo apt sudo E: Sub-process /usr/bin/dpkg
  returned an error code (1)

Status in sudo package in Ubuntu:
  New

Bug description:
  При удалении пакетов мною была допущена ошибка в тексте команды. Вот
  полное описание процесса:

  beginner@beginner-desktop:~$ sudo apt remove xclip sudo apt
  Чтение списков пакетов… Готово
  Построение дерева зависимостей   
  Чтение информации о состоянии… Готово
  Следующие пакеты устанавливались автоматически и больше не требуются:
extlinux gdebi-core gnome-icon-theme libgksu2-0 linux-headers-4.10.0-28
linux-headers-4.10.0-28-generic linux-image-4.10.0-28-generic
linux-image-extra-4.10.0-28-generic sudo-ldap unetbootin-translations
  Для их удаления используйте «sudo apt autoremove».
  Будут установлены следующие дополнительные пакеты:
sudo-ldap
  Пакеты, которые будут УДАЛЕНЫ:
apt apt-utils gdebi gksu sudo ubuntu-minimal unattended-upgrades unetbootin
xclip
  НОВЫЕ пакеты, которые будут установлены:
sudo-ldap
  ВНИМАНИЕ: Эти существенно важные пакеты будут удалены.
  НЕ ДЕЛАЙТЕ этого, если вы НЕ представляете себе все возможные последствия!
apt
  обновлено 0, установлено 1 новых пакетов, для удаления отмечено 9 пакетов, и 
0 пакетов не обновлено.
  Необходимо скачать 420 kБ архивов.
  После данной операции, объём занятого дискового пространства уменьшится на 6 
050 kB.
  То, что вы хотите сделать, может иметь нежелательные последствия.
  Чтобы продолжить, введите фразу: «Да, делать, как я скажу!»
   ?] Да, делать, как я скажу!
  Пол:1 http://ru.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
sudo-ldap amd64 1.8.16-0ubuntu1.5 [420 kB]
  Получено 420 kБ за 20с (20,8 kБ/c)
  (Чтение базы данных … на данный момент установлено 307670 файлов и каталогов.)
  Удаляется unattended-upgrades (0.90ubuntu0.9) …
  Удаляется ubuntu-minimal (1.361.1) …
  Удаляется apt-utils (1.2.25) …
  Удаляется apt (1.2.25) …
  Удаляется gdebi (0.9.5.7ubuntu1) …
  Удаляется unetbootin (608-1) …
  Удаляется gksu (2.0.2-9ubuntu1) …
  Удаляется sudo (1.8.16-0ubuntu1.5) …
  You have asked that the sudo package be removed,
  but no root password has been set.
  Without sudo, you may not be able to gain administrative privileges.

  If you would prefer to access the root account with su(1)
  or by logging in directly,
  you must set a root password with "sudo passwd".

  If you have arranged other means to access the root account,
  and you are sure this is what you want,
  you may bypass this check by setting an environment variable 
  (export SUDO_FORCE_REMOVE=yes).

  Refusing to remove sudo.
  dpkg: ошибка при обработке пакета sudo (--remove):
   подпроцесс установлен сценарий pre-removal возвратил код ошибки 1
  Удаляется xclip (0.12+svn84-4) …
  Обрабатываются триггеры для man-db (2.7.5-1) …
  Обрабатываются триггеры для libc-bin (2.23-0ubuntu10) …
  Обрабатываются триггеры для gnome-menus (3.13.3-6ubuntu3.1) …
  Обрабатываются триггеры для desktop-file-utils (0.22-1ubuntu5.1) …
  Обрабатываются триггеры для bamfdaemon (0.5.3~bzr0+16.04.20160824-0ubuntu1) …
  Rebuilding /usr/share/applications/bamf-2.index...
  Обрабатываются триггеры для mime-support (3.59ubuntu1) …
  При обработке следующих пакетов произошли ошибки:
   sudo
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: sudo 1.8.16-0ubuntu1.5
  ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  Architecture: amd64
  Date: Fri Feb 23 11:53:32 2018
  ErrorMessage: подпроцесс установлен сценарий pre-removal возвратил код ошибки 
1
  InstallationDate: Installed on 2018-01-29 (24 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: sudo
  Title: package sudo 1.8.16-0ubuntu1.5 failed to install/upgrade: подпроцесс 
установлен сценарий pre-removal возвратил код ошибки 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  VisudoCheck:
   /etc/sudoers: parsed OK
   /etc/sudoers.d/README: parsed OK

To manage notifications about this bug go to:

[Touch-packages] [Bug 1750741] Re: Memory leak in g_dbus_proxy_new_for_bus_sync()

2018-02-26 Thread Seyeong Kim

@ddstreet

After analyzing code.

I don't think this fix is possible without any big changes for trusty.

and glib2.0 affects many pkgs it seems.

it is quite dangerous to fix this with large commits.

so lets focus on pacemaker instead of glib2.0

how about this ddstreet?

Thanks

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

Title:
  Memory leak in g_dbus_proxy_new_for_bus_sync()

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Trusty:
  Confirmed

Bug description:
  [Impact]

  This issue is found while debugging pacemaker lrmd memory leak

  glib2.0 gio function g_dbus_proxy_new_for_bus_sync has leak as [1]
  said

  this is affected to Trusty

  [Test Case]

  https://pastebin.ubuntu.com/p/fqK6Cx3SKK/
  you can check memory leak with this script

  [Regression]
  This patch is affected to library pkg. so related daemon should be restarted 
after patching. patch itself is very simple and old. it seems verified for few 
years.

  [Others]

  original commit

  
https://gitlab.gnome.org/GNOME/glib/commit/db641e32920ee8b553ab6f2d318aafa156e4390c

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1750741/+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 1693095] Re: package bsdutils 1:2.28.2-1ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

This is an unsupported release now. Please think to install the next LTS
'Bionic 18.04'

http://cdimage.ubuntu.com/ubuntu-next/daily-live/current/
https://www.omgubuntu.co.uk/2018/02/ubuntu-18-04-minimal-install-option

** Changed in: util-linux (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  package bsdutils 1:2.28.2-1ubuntu1.1 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in util-linux package in Ubuntu:
  Invalid

Bug description:
  i was install os updates from the gui installer.

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: bsdutils 1:2.28.2-1ubuntu1.1
  ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  Date: Tue May 23 20:42:55 2017
  DpkgTerminalLog:
   dpkg: error processing package bsdutils (--configure):
package is in a very bad inconsistent state; you should
reinstall it before attempting configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-05-21 (2 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3.3
  SourcePackage: util-linux
  Title: package bsdutils 1:2.28.2-1ubuntu1.1 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1693095/+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 1750780] Re: Race with local file systems can make open-vm-tools fail to start

2018-02-26 Thread ChristianEhrhardt

With the former update in mind I retried Xenial/Bionic again.
All of it is racy (as we knew), but it never triggered for Bionic.

Xenial (19/33 fails)
Bionic (0/37 fails)

So for now we continue to assume that it is fixed there (by systemd) and
revert our added dependency.

Note: as with the simple job in comment #12 and comment #14 this is Hipervisor 
agnostic.
You can even test the open-vm-tools service in KVM by removing the condition on 
vmware.

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

Title:
  Race with local file systems can make open-vm-tools fail to start

Status in cloud-init:
  Invalid
Status in open-vm-tools package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in open-vm-tools source package in Xenial:
  Triaged
Status in systemd source package in Xenial:
  New
Status in open-vm-tools package in Debian:
  Incomplete

Bug description:
  Since the change in [1] open-vm-tools-service starts very (very) early.
  Not so much due to the 
  Before=cloud-init-local.service
  But much more by
  DefaultDependencies=no

  That can trigger an issue that looks like
  root@ubuntuguest:~# systemctl status -l open-vm-tools.service
  ● open-vm-tools.service - Service for virtual machines hosted on VMware
 Loaded: loaded (/lib/systemd/system/open-vm-tools.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: resources)

  
  As it is right now open-vm-tools can race with the other early start and then 
fail.
  In detail one can find a message like:
open-vm-tools.service: Failed to run 'start' task: Read-only file system"

  This is due to privtaeTmp=yes which is also set needing a writable
  /var/tmp [2]

  To ensure this works PrivateTmp would have to be removed (not good) or some 
after dependencies added that make this work reliably.
  I added
  After=local-fs.target
  which made it work for me in 3/3 tests.

  I' like to have an ack by the cloud-init Team that this does not totally kill 
the originally intended Before=cloud-init-local.service
  I think it does not as local-fs can complete before cloud-init-local, then 
open-vm-tools can initialize and finally cloud-init-local can pick up the data.

  To summarize:
  # cloud-init-local #
  DefaultDependencies=no
  Wants=network-pre.target
  After=systemd-remount-fs.service
  Before=NetworkManager.service
  Before=network-pre.target
  Before=shutdown.target
  Before=sysinit.target
  Conflicts=shutdown.target
  RequiresMountsFor=/var/lib/cloud

  # open-vm-tools #
  DefaultDependencies=no
  Before=cloud-init-local.service

  Proposed is to add to the latter:
  After=local-fs.target

  [1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859677
  [2]: https://github.com/systemd/systemd/issues/5610

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1750780/+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 1698570] Re: package keyboard-configuration 1.70ubuntu8 failed to install/upgrade: subprocess new pre-installation script returned error exit status 1

This is an unsupported release now. Please think to install the next LTS
'Bionic 18.04'

http://cdimage.ubuntu.com/ubuntu-next/daily-live/current/
https://www.omgubuntu.co.uk/2018/02/ubuntu-18-04-minimal-install-option

** Changed in: console-setup (Ubuntu)
   Status: New => Invalid

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

Title:
  package keyboard-configuration 1.70ubuntu8 failed to install/upgrade:
  subprocess new pre-installation script returned error exit status 1

Status in console-setup package in Ubuntu:
  Invalid

Bug description:
  no idea what this is about.  I got it while upgrading to 16.10

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: keyboard-configuration 1.70ubuntu8
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic i686
  ApportVersion: 2.14.1-0ubuntu3.24
  Architecture: i386
  Date: Sat Jun 17 14:58:07 2017
  DuplicateSignature: package:keyboard-configuration:1.70ubuntu8:subprocess new 
pre-installation script returned error exit status 1
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 1
  InstallationDate: Installed on 2016-08-17 (304 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 
(20160217.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1.1
   apt  1.0.1ubuntu2.17
  SourcePackage: console-setup
  Title: package keyboard-configuration 1.70ubuntu8 failed to install/upgrade: 
subprocess new pre-installation script returned error exit status 1
  UpgradeStatus: Upgraded to yakkety on 2017-06-17 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1698570/+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 1751716] Re: [Aspire 6930G, Realtek ALC888, Speaker, Internal] Sound is distorted

2018-02-26 Thread Radosław M . Ścisło

New finding: the distortion seems to appear after reboot (without power
off).  IMO some variables in sound card (probably gain) are not reset to
initial values during reboot and/or switch between audio sources (maybe
even during switch between browser tabs) and this over-steers final
amplifiers.

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

Title:
  [Aspire 6930G, Realtek ALC888, Speaker, Internal] Sound is distorted

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After installing recent updates to sound libraries (see log below) sound is 
distorted, sounds like over-steered, especially right channel (I use build-in 
speakers with "stereo sound" option [BTW: I cannot get working sub-woofer]). 
  ==
  Upgrade log:

  Start-Date: 2018-02-26  07:52:58
  Commandline: apt upgrade
  Requested-By: x (1000)
  Upgrade: libpulsedsp:amd64 (1:8.0-0ubuntu3.7, 1:8.0-0ubuntu3.8), 
grub-common:amd64 (2.02~beta2-36ubuntu3.16, 2.02~beta2-36ubuntu3.17), 
pulseaudio:amd64 (1:8.0-0ubuntu3.7, 1:8.0-0ubuntu3.8), python-apt-common:amd64 
(1.1.0~beta1build1, 1.1.0~beta1ubuntu0.16.04.1), grub2-common:amd64 
(2.02~beta2-36ubuntu3.16, 2.02~beta2-36ubuntu3.17), grub-pc:amd64 
(2.02~beta2-36ubuntu3.16, 2.02~beta2-36ubuntu3.17), grub-pc-bin:amd64 
(2.02~beta2-36ubuntu3.16, 2.02~beta2-36ubuntu3.17), ubuntu-drivers-common:amd64 
(1:0.4.17.3, 1:0.4.17.6), python3-distupgrade:amd64 (1:16.04.23, 1:16.04.24), 
libpulse0:amd64 (1:8.0-0ubuntu3.7, 1:8.0-0ubuntu3.8), libpulse0:i386 
(1:8.0-0ubuntu3.7, 1:8.0-0ubuntu3.8), ubuntu-release-upgrader-core:amd64 
(1:16.04.23, 1:16.04.24), libpulse-mainloop-glib0:amd64 (1:8.0-0ubuntu3.7, 
1:8.0-0ubuntu3.8), pulseaudio-module-x11:amd64 (1:8.0-0ubuntu3.7, 
1:8.0-0ubuntu3.8), ubuntu-release-upgrader-gtk:amd64 (1:16.04.23, 1:16.04.24), 
pulseaudio-module-bluetooth:amd64 (1:8.0-0ubuntu3.7, 1:8.0-0ubuntu3.8), 
opera-stable:amd64 (51.0.2830.34, 51.0.2830.40), pulseaudio-utils:amd64 
(1:8.0-0ubuntu3.7, 1:8.0-0ubuntu3.8), python3-apt:amd64 (1.1.0~beta1build1, 
1.1.0~beta1ubuntu0.16.04.1), base-files:amd64 (9.4ubuntu4.5, 9.4ubuntu4.6)
  End-Date: 2018-02-26  07:58:28

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  radek  2730 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Feb 26 08:19:21 2018
  InstallationDate: Installed on 2017-11-10 (107 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_Jack: Speaker, Internal
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [Aspire 6930G, Realtek ALC888, Speaker, Internal] Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/14/2008
  dmi.bios.vendor: Acer
  dmi.bios.version: v0.3120
  dmi.board.name: Makalu
  dmi.board.vendor: Acer, Inc.
  dmi.board.version: Not Applicable
  dmi.chassis.type: 1
  dmi.chassis.vendor: Acer, Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAcer:bvrv0.3120:bd08/14/2008:svnAcer,inc.:pnAspire6930G:pvrNotApplicable:rvnAcer,Inc.:rnMakalu:rvrNotApplicable:cvnAcer,Inc.:ct1:cvrN/A:
  dmi.product.name: Aspire 6930G
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Acer, inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1751716/+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 1696589] Re: [USB-Audio - ThinkPad OneLink Plus Dock Audi, playback] fails after a while

This is an unsupported release now. Please think to install the next LTS
'Bionic 18.04'

http://cdimage.ubuntu.com/ubuntu-next/daily-live/current/
https://www.omgubuntu.co.uk/2018/02/ubuntu-18-04-minimal-install-option

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

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

Title:
  [USB-Audio - ThinkPad OneLink Plus Dock Audi, playback] fails after a
  while

Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  On Ubuntu 16.10

  The pulseaudio daemon dies occasionally.  It's probably caused by
  audio output activity, but I can't be sure it always stops during
  playback because I can't always hear it (headphones plugged in but not
  on my head).  It doesn't seem to die as much when I'm not playing
  audio, however.

  The included log collected by `ubuntu-bug audio` does not represent
  the bug.  It does not occur frequently enough to capture it while
  creating this report.  But I have capture logs of several crashes in
  the past.

  A month or so ago I added this to my /etc/pulse/client.conf:

  ; Added for debugging pulseaudio failures
  ; https://wiki.ubuntu.com/PulseAudio/Log
  ; Maybe related: 
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1574324
  extra-arguments = - --log-target=newfile:/tmp/pulseverbose.log 
--log-time=1

  I have attached some of the logs up the point of failure to this
  report.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-52.55-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   phord  9173 F...m pulseaudio
   /dev/snd/controlC1:  phord  9173 F pulseaudio
   /dev/snd/pcmC0D0c:   phord  9173 F...m pulseaudio
   /dev/snd/controlC0:  phord  9173 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jun  7 14:48:59 2017
  InstallationDate: Installed on 2017-02-17 (110 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: ThinkPad OneLink Plus Dock Audio - ThinkPad OneLink Plus Dock 
Audi
  Symptom_Type: Sound works for a while, then breaks
  Title: [USB-Audio - ThinkPad OneLink Plus Dock Audi, playback] fails after a 
while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/02/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1FET43W (1.17 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FB005LUS
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET43W(1.17):bd08/02/2016:svnLENOVO:pn20FB005LUS:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FB005LUS:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20FB005LUS
  dmi.product.version: ThinkPad X1 Carbon 4th
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1696589/+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 1698688] Re: DNS resolution stopped working suddenly

This is an unsupported release now. Please think to install the next LTS
'Bionic 18.04'

http://cdimage.ubuntu.com/ubuntu-next/daily-live/current/
https://www.omgubuntu.co.uk/2018/02/ubuntu-18-04-minimal-install-option

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

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

Title:
  DNS resolution stopped working suddenly

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  DNS resolution stopped working all of a sudden.

  This is the only clue I've got, not sure what it means.

  systemctl restart network-manager appears to fix the issue.

  
  Jun 18 21:53:07 nico-lenovo-ubuntu systemd[1]: Stopping User Manager for UID 
113...
  Jun 18 21:53:07 nico-lenovo-ubuntu systemd[19918]: Stopping D-Bus User 
Message Bus...
  Jun 18 21:53:07 nico-lenovo-ubuntu systemd[19918]: Stopped target Default.
  Jun 18 21:53:07 nico-lenovo-ubuntu systemd[19918]: Stopping Virtual 
filesystem service...
  Jun 18 21:53:07 nico-lenovo-ubuntu systemd[19918]: Stopped D-Bus User Message 
Bus.
  Jun 18 21:53:07 nico-lenovo-ubuntu systemd[19918]: Stopped Virtual filesystem 
service.
  Jun 18 21:53:07 nico-lenovo-ubuntu systemd[19918]: Stopped target Basic 
System.
  Jun 18 21:53:07 nico-lenovo-ubuntu systemd[19918]: Stopped target Sockets.
  Jun 18 21:53:07 nico-lenovo-ubuntu systemd[19918]: Stopped target Paths.
  Jun 18 21:53:07 nico-lenovo-ubuntu systemd[19918]: Stopped target Timers.
  Jun 18 21:53:07 nico-lenovo-ubuntu systemd[19918]: Closed D-Bus User Message 
Bus Socket.
  Jun 18 21:53:07 nico-lenovo-ubuntu systemd[19918]: Reached target Shutdown.
  Jun 18 21:53:07 nico-lenovo-ubuntu systemd[19918]: Starting Exit the 
Session...
  Jun 18 21:53:07 nico-lenovo-ubuntu systemd[19918]: Received SIGRTMIN+24 from 
PID 20775 (kill).
  Jun 18 21:53:07 nico-lenovo-ubuntu systemd[19919]: 
pam_unix(systemd-user:session): session closed for user lightdm
  Jun 18 21:53:07 nico-lenovo-ubuntu systemd[1]: user@113.service: Killing 
process 20775 (kill) with signal SIGKILL.
  Jun 18 21:53:07 nico-lenovo-ubuntu systemd[1]: Stopped User Manager for UID 
113.
  Jun 18 21:53:07 nico-lenovo-ubuntu systemd[1]: Removed slice User Slice of 
lightdm.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-9ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-52.55-lowlatency 4.8.17
  Uname: Linux 4.8.0-52-lowlatency x86_64
  ApportVersion: 2.20.3-0ubuntu8.3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sun Jun 18 22:03:40 2017
  InstallationDate: Installed on 2016-10-20 (241 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: LENOVO 20FBCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-52-lowlatency 
root=UUID=9c48fc00-9dd5-45e9-8cd1-edbb5d1b8818 ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/02/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1FET43W (1.17 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FBCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET43W(1.17):bd08/02/2016:svnLENOVO:pn20FBCTO1WW:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FBCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20FBCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 4th
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1698688/+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 1697329] Re: package libwrap0:i386 7.6.q-25 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

This is an unsupported release now. Please think to install the next LTS
'Bionic 18.04'

http://cdimage.ubuntu.com/ubuntu-next/daily-live/current/
https://www.omgubuntu.co.uk/2018/02/ubuntu-18-04-minimal-install-option

** Changed in: tcp-wrappers (Ubuntu)
   Status: New => Invalid

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

Title:
  package libwrap0:i386 7.6.q-25 failed to install/upgrade: package is
  in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in tcp-wrappers package in Ubuntu:
  Invalid

Bug description:
  I got this error while logged in

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: libwrap0:i386 7.6.q-25
  ProcVersionSignature: Ubuntu 4.8.0-54.57-generic 4.8.17
  Uname: Linux 4.8.0-54-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.3
  Architecture: amd64
  Date: Sun Jun 11 02:46:08 2017
  DuplicateSignature:
   package:libwrap0:i386:7.6.q-25
   Setting up libssl-doc (1.0.2g-1ubuntu9.3) ...
   dpkg: error processing package libwrap0:i386 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2016-06-10 (366 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1.1
   apt  1.3.5
  SourcePackage: tcp-wrappers
  Title: package libwrap0:i386 7.6.q-25 failed to install/upgrade: package is 
in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: Upgraded to yakkety on 2017-05-28 (15 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tcp-wrappers/+bug/1697329/+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 1745428] Re: package linux-firmware 1.157.15 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

I had a similar problem, also caused by a copy error.
Because of that problem I could not only not upgrade the kernel but couldn't 
install any software at all.

In my case the problem was caused by a missing udev rule in
/etc/udev/rules.d/. I created the rule when trying to run a windows
installation on a second hd with Virtual Box. Because that didn't come
to work, I deleted the rule again. I don't now why but the system was
trying to copy this rule during the process of upgrading the kernel.
Since I deleted the file, the process of upgrading failed. I tried to
find out, where this rule was still linked so that I could remove the
link and the system wouldn't want to copy this rule anymore, but I
couldn't find out where that was. But restoring the rule did it for me
and the system is upgrading fine again.

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

Title:
  package linux-firmware 1.157.15 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  package linux-firmware 1.157.15 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-firmware 1.157.15
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Thu Jan 25 16:24:40 2018
  Dependencies:
   
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-10-13 (469 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: initramfs-tools
  Title: package linux-firmware 1.157.15 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1745428/+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 1745113] Re: package linux-image-4.13.0-31-generic 4.13.0-31.34~16.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

Because of that problem I could not only not upgrade the kernel but
couldn't install any software at all.

In my case the problem was caused by a missing udev rule in
/etc/udev/rules.d/. I created the rule when trying to run a windows
installation on a second hd with Virtual Box. Because that didn't come
to work, I deleted the rule again. I don't now why but the system was
trying to copy this rule during the process of upgrading the kernel.
Since I deleted the file, the process of upgrading failed. I tried to
find out, where this rule was still linked so that I could remove the
link and the system wouldn't want to copy this rule anymore, but I
couldn't find out where that was. But restoring the rule did it for me
and the system is upgrading fine again.

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

Title:
  package linux-image-4.13.0-31-generic 4.13.0-31.34~16.04.1 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  new installation.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Wed Jan 24 06:52:15 2018
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2018-01-12 (12 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: initramfs-tools
  Title: package linux-image-4.13.0-31-generic 4.13.0-31.34~16.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1745113/+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 1749199] Re: purge conf files on removal of upstart (was session fails to start after an upgrade from xenial to bionic)

This bug was fixed in the package xorg - 1:7.7+19ubuntu5

---
xorg (1:7.7+19ubuntu5) bionic; urgency=medium

  * Cleanup upstart Xsession.d files, when upstart is removed, but not
purged, and thus breaking graphical login after upgrades. LP: #1749199

 -- Dimitri John Ledkov   Thu, 22 Feb 2018 16:43:18
+

** Changed in: xorg (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 xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1749199

Title:
  purge conf files on removal of upstart (was session fails to start
  after an upgrade from xenial to bionic)

Status in ubuntu-release-upgrader package in Ubuntu:
  Triaged
Status in xorg package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader source package in Bionic:
  Triaged
Status in xorg source package in Bionic:
  Fix Released

Bug description:
  [Testcase]

  1. Launch xenial lxd container
  2. install x11-common upstart
  3. do-release-upgrade to bionic
  4. Upgrade to bionic removes upstart
  5. upgrade to new x11-common, make sure the upstart snippets are gone from 
disk: /etc/X11/Xsession.d/00upstart
  /etc/X11/Xsession.d/99upstart
  6. for the new release-upgrader, check that upstart is purged, if user 
selects to remove packages at the end of the do-release-upgrade.

  
  After an upgrade from Xenial to Bionic the session fails to start and returns 
immediately to the login screen.

  There is this line in the journal
  [...] /usr/lib/gdm3/gdm-x-session[3584]: 
/etc/X11/Xsession.d/99x11-common_start: ligne 5: /sbin/upstart: Aucun fichier 
ou dossier de ce type

  (full journal from a failed attempt attached)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-session 3.26.1-0ubuntu9
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  Date: Tue Feb 13 15:11:12 2018
  InstallationDate: Installed on 2018-02-07 (6 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: Upgraded to bionic on 2018-02-13 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1749199/+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 295832] Re: Alsa does not honor pcm.!default because of /usr/share/alsa/pulse.conf

* Declared closed over 9 years ago.

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

Title:
  Alsa does not honor pcm.!default because of /usr/share/alsa/pulse.conf

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Intrepid:
  Fix Released

Bug description:
  SRU information follows:

  Impact statement: Users of Ubuntu 8.10 find that their
  /etc/asound.conf and ~/.asoundrc are ignored due to missing entries in
  /usr/share/alsa/pulse.conf. This symptom affects all users with the
  pulseaudio package installed *and* the daemon (regardless of system-
  wide or per-user session instance) running.

  Bug resolution: The missing lines [referencing /etc/asound.conf and
  ~/.asoundrc] are added to /usr/share/alsa/pulse.conf. The change to
  the errors line mimics libasound2's /usr/share/alsa/alsa.conf [to not
  throw an error upon a missing ~/.asoundrc]. With these changes, users
  of default Ubuntu 8.10 will have their /etc/asound.conf and
  ~/.asoundrc, if extant, honoured with higher priority than the
  configuration shipped by pulseaudio, thereby restoring expected alsa-
  lib runtime conf behaviour (for native ALSA applications) prior to
  intrepid. If either /etc/asound.conf or ~/.asoundrc is missing, the
  current intrepid behaviour of pulseaudio overriding {pcm,ctl}.default
  is retained. This change is shown via Loggerhead here:
  
http://bazaar.launchpad.net/~crimsun/pulseaudio/ubuntu/revision/38?remember=36_revid=36.

  SRU patch:
  http://launchpadlibrarian.net/2123/pulseaudio_0.9.10-2ubuntu9.3.debdiff

  Instructions to reproduce the symptom: Create an ~/.asoundrc with the
  following contents only:

  # --- begin ---
  pcm.!default {
 type plug
 slave hw:5,0
  }

  ctl.!default {
 type hw
 card 5
  }
  # --- end ---

  After a fresh GNOME session login, open Applications> Accessories> Terminal, 
and use `speaker-test -Ddefault -c2' to verify that:
  1) the speaker-test output continues to play (until interrupt, ctrl+c) 
through the PulseAudio-configured default device;
  2) no errors are generated by alsa-lib.

  These two symptoms verify that ~/.asoundrc is ignored.

  Regression potential: Users who have a misconfigured /etc/asound.conf
  or ~/.asoundrc will notice that native ALSA apps refuse to start and
  throw alsa-lib error(s), which can be resolved by removing the
  offending conffile.

  Original description follows:

  Binary package hint: pulseaudio

  Even if I define a pcm.!default section in ~/.asoundrc, /usr/share
  /pulse-alsa.conf overrides this definition, so the default alsa output
  is always pulseaudio.

  If I comment the pcm.!default and ctl.!default in /usr/share/alsa
  /pulse-alsa.conf everything behaves as normal.

  Using Intrepid amd64.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/295832/+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 295832] Re: Alsa does not honor pcm.!default because of /usr/share/alsa/pulse.conf

This bug is closed, rightly or wrongly. I'm not saying the fix mentioned
above was really sufficient, but since it was declared closed 8 years
ago it would be most helpful for anyone still experiencing problems to
open a new bug with fresh information using this command:

  ubuntu-bug pulseaudio

Thanks.

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

Title:
  Alsa does not honor pcm.!default because of /usr/share/alsa/pulse.conf

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Intrepid:
  Fix Released

Bug description:
  SRU information follows:

  Impact statement: Users of Ubuntu 8.10 find that their
  /etc/asound.conf and ~/.asoundrc are ignored due to missing entries in
  /usr/share/alsa/pulse.conf. This symptom affects all users with the
  pulseaudio package installed *and* the daemon (regardless of system-
  wide or per-user session instance) running.

  Bug resolution: The missing lines [referencing /etc/asound.conf and
  ~/.asoundrc] are added to /usr/share/alsa/pulse.conf. The change to
  the errors line mimics libasound2's /usr/share/alsa/alsa.conf [to not
  throw an error upon a missing ~/.asoundrc]. With these changes, users
  of default Ubuntu 8.10 will have their /etc/asound.conf and
  ~/.asoundrc, if extant, honoured with higher priority than the
  configuration shipped by pulseaudio, thereby restoring expected alsa-
  lib runtime conf behaviour (for native ALSA applications) prior to
  intrepid. If either /etc/asound.conf or ~/.asoundrc is missing, the
  current intrepid behaviour of pulseaudio overriding {pcm,ctl}.default
  is retained. This change is shown via Loggerhead here:
  
http://bazaar.launchpad.net/~crimsun/pulseaudio/ubuntu/revision/38?remember=36_revid=36.

  SRU patch:
  http://launchpadlibrarian.net/2123/pulseaudio_0.9.10-2ubuntu9.3.debdiff

  Instructions to reproduce the symptom: Create an ~/.asoundrc with the
  following contents only:

  # --- begin ---
  pcm.!default {
 type plug
 slave hw:5,0
  }

  ctl.!default {
 type hw
 card 5
  }
  # --- end ---

  After a fresh GNOME session login, open Applications> Accessories> Terminal, 
and use `speaker-test -Ddefault -c2' to verify that:
  1) the speaker-test output continues to play (until interrupt, ctrl+c) 
through the PulseAudio-configured default device;
  2) no errors are generated by alsa-lib.

  These two symptoms verify that ~/.asoundrc is ignored.

  Regression potential: Users who have a misconfigured /etc/asound.conf
  or ~/.asoundrc will notice that native ALSA apps refuse to start and
  throw alsa-lib error(s), which can be resolved by removing the
  offending conffile.

  Original description follows:

  Binary package hint: pulseaudio

  Even if I define a pcm.!default section in ~/.asoundrc, /usr/share
  /pulse-alsa.conf overrides this definition, so the default alsa output
  is always pulseaudio.

  If I comment the pcm.!default and ctl.!default in /usr/share/alsa
  /pulse-alsa.conf everything behaves as normal.

  Using Intrepid amd64.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/295832/+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 1751716] Re: [Aspire 6930G, Realtek ALC888, Speaker, Internal] Sound is distorted

** Package changed: alsa-driver (Ubuntu) => pulseaudio (Ubuntu)

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

Title:
  [Aspire 6930G, Realtek ALC888, Speaker, Internal] Sound is distorted

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  After installing recent updates to sound libraries (see log below) sound is 
distorted, sounds like over-steered, especially right channel (I use build-in 
speakers with "stereo sound" option [BTW: I cannot get working sub-woofer]). 
  ==
  Upgrade log:

  Start-Date: 2018-02-26  07:52:58
  Commandline: apt upgrade
  Requested-By: x (1000)
  Upgrade: libpulsedsp:amd64 (1:8.0-0ubuntu3.7, 1:8.0-0ubuntu3.8), 
grub-common:amd64 (2.02~beta2-36ubuntu3.16, 2.02~beta2-36ubuntu3.17), 
pulseaudio:amd64 (1:8.0-0ubuntu3.7, 1:8.0-0ubuntu3.8), python-apt-common:amd64 
(1.1.0~beta1build1, 1.1.0~beta1ubuntu0.16.04.1), grub2-common:amd64 
(2.02~beta2-36ubuntu3.16, 2.02~beta2-36ubuntu3.17), grub-pc:amd64 
(2.02~beta2-36ubuntu3.16, 2.02~beta2-36ubuntu3.17), grub-pc-bin:amd64 
(2.02~beta2-36ubuntu3.16, 2.02~beta2-36ubuntu3.17), ubuntu-drivers-common:amd64 
(1:0.4.17.3, 1:0.4.17.6), python3-distupgrade:amd64 (1:16.04.23, 1:16.04.24), 
libpulse0:amd64 (1:8.0-0ubuntu3.7, 1:8.0-0ubuntu3.8), libpulse0:i386 
(1:8.0-0ubuntu3.7, 1:8.0-0ubuntu3.8), ubuntu-release-upgrader-core:amd64 
(1:16.04.23, 1:16.04.24), libpulse-mainloop-glib0:amd64 (1:8.0-0ubuntu3.7, 
1:8.0-0ubuntu3.8), pulseaudio-module-x11:amd64 (1:8.0-0ubuntu3.7, 
1:8.0-0ubuntu3.8), ubuntu-release-upgrader-gtk:amd64 (1:16.04.23, 1:16.04.24), 
pulseaudio-module-bluetooth:amd64 (1:8.0-0ubuntu3.7, 1:8.0-0ubuntu3.8), 
opera-stable:amd64 (51.0.2830.34, 51.0.2830.40), pulseaudio-utils:amd64 
(1:8.0-0ubuntu3.7, 1:8.0-0ubuntu3.8), python3-apt:amd64 (1.1.0~beta1build1, 
1.1.0~beta1ubuntu0.16.04.1), base-files:amd64 (9.4ubuntu4.5, 9.4ubuntu4.6)
  End-Date: 2018-02-26  07:58:28

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  radek  2730 F pulseaudio
  CurrentDesktop: Unity
  Date: Mon Feb 26 08:19:21 2018
  InstallationDate: Installed on 2017-11-10 (107 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Intel failed
  Symptom_Card: Built-in Audio - HDA Intel
  Symptom_Jack: Speaker, Internal
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [Aspire 6930G, Realtek ALC888, Speaker, Internal] Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/14/2008
  dmi.bios.vendor: Acer
  dmi.bios.version: v0.3120
  dmi.board.name: Makalu
  dmi.board.vendor: Acer, Inc.
  dmi.board.version: Not Applicable
  dmi.chassis.type: 1
  dmi.chassis.vendor: Acer, Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAcer:bvrv0.3120:bd08/14/2008:svnAcer,inc.:pnAspire6930G:pvrNotApplicable:rvnAcer,Inc.:rnMakalu:rvrNotApplicable:cvnAcer,Inc.:ct1:cvrN/A:
  dmi.product.name: Aspire 6930G
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Acer, inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1751716/+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 1750884] Re: [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic, leads to no DNS resolution

2018-02-26 Thread Mathieu Trudel-Lapierre

Whether or not /e/n/i supports something correctly or just happens to
work by sheer luck has no bearing on what is technically correct and
sensical -- let's abstract this, what we need to concern ourselves with
here is netplan, cloud-init and maas.

In the network world, it is absolutely true that DNS nameservers only
make sense on a per-interface basis: nothing guarantees that a
"globally-set" nameserver of 8.8.8.8 is reachable through all
interfaces. It just happens to be that way on 99% of systems because
they only connect to one network, through one interface.

So, in light of the nameserver setting in MaaS under Settings being
unspecified, there's /no other way/ but to either set the nameserver
globally or try to guess the right interface (either by which is
connected to MaaS, or which gets the default gateway, or which matches
subnets). None of the detection options I could come up with strike me
as particularly solid and foolproof.

Next steps for netplan strike me as being to add support for global
nameservers even if it's silly; we shouldn't expect users to have to
have the level of knowledge of networking to know to set it up on a
particular interface when it will work correctly as "global" for 99% of
cases.

In MaaS, my opinion is that every effort should be taken to allow
network administrators to set things up correctly -- nothing guarantees
that the systems deployed will remain accessible to MaaS, or that it
will be their main interface to the network. Only allowing global DNS is
brittle at best, and breaks at least what *I* have been taught were best
practices, to have a separate "public" network from the authenticated
"private" side where monitoring and/or deployment happens. Maybe I'm
just the one who's particular in doing this.

I'm not sure what next steps are for cloud-init -- given a valid
configuration, I assumed it should just pass it through to netplan if
it's v2.

I'll take care of the "global DNS" implementation in netplan.

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

Title:
  [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic,
  leads to no DNS resolution

Status in cloud-init:
  New
Status in MAAS:
  Triaged
Status in nplan package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  When deploying Bionic, /etc/resolv.conf is not configured correctly,
  which leads to no DNS resolution. In the output below, you will see
  that netplan config is correctly to the 10.90.90.1 nameserver, but in
  resolv.conf that's a local address.

  Resolv.conf should really be configured to use the provided DNS
  server(s). That said, despite that fact, DNS resolution doesn't work
  with the local address.

  Bionic
  --

  ubuntu@node01:~$ cat /etc/netplan/50-cloud-init.yaml
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  enp0s25:
  match:
  macaddress: b8:ae:ed:7d:17:d2
  mtu: 1500
  nameservers:
  addresses:
  - 10.90.90.1
  search:
  - maaslab
  - maas
  set-name: enp0s25
  bridges:
  br0:
  addresses:
  - 10.90.90.3/24
  gateway4: 10.90.90.1
  interfaces:
  - enp0s25
  parameters:
  forward-delay: 15
  stp: false
  ubuntu@node01:~$ cat /etc/resolv.conf
  # This file is managed by man:systemd-resolved(8). Do not edit.
  #
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.
  nameserver 127.0.0.53

  search maaslab maas
  ubuntu@node01:~$ ping google.com
  ping: google.com: Temporary failure in name resolution

  [...]

  ubuntu@node01:~$ sudo vim /etc/resolv.conf
  ubuntu@node01:~$ cat /etc/resolv.conf
  # This file is managed by man:systemd-resolved(8). Do not edit.
  #
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.
  nameserver 10.90.90.1

  search maaslab maas
  ubuntu@node01:~$ ping google.com
  PING google.com (172.217.0.174) 56(84) bytes of data.
  64 bytes from mia09s16-in-f14.1e100.net (172.217.0.174): icmp_seq=1 ttl=52 
time=4.46 ms
  64 bytes from mia09s16-in-f14.1e100.net (172.217.0.174): icmp_seq=2 ttl=52 
time=4.38 ms

  =
  Xenial
  ==

  ubuntu@node05:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg
  #

[Touch-packages] [Bug 1700256] Re: package bluez 5.37-0ubuntu5 failed to install/upgrade: Abhängigkeitsprobleme - verbleibt unkonfiguriert

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

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

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

Title:
  package bluez 5.37-0ubuntu5 failed to install/upgrade [bluez depends
  on udev (> = 170-1); but: Package udev is not configured yet.]

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  
  This bug is already displayed when I start up. Updates are not possible, 
there are further error messages ...

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.37-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-81.104-generic 4.4.67
  Uname: Linux 4.4.0-81-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Tue Jun 20 21:06:57 2017
  ErrorMessage: Abhängigkeitsprobleme - verbleibt unkonfiguriert
  InstallationDate: Installed on 2016-06-20 (369 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  InterestingModules: bluetooth
  MachineType: LENOVO 2491.A3G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-81-generic 
root=UUID=5c7ae55f-369b-45ae-bb99-457d973001cb ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: bluez
  Title: package bluez 5.37-0ubuntu5 failed to install/upgrade: 
Abhängigkeitsprobleme - verbleibt unkonfiguriert
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/10/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9HKT58AUS
  dmi.board.vendor: LENOVO
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvr9HKT58AUS:bd06/10/2014:svnLENOVO:pn2491.A3G:pvrThinkCentreM91:rvnLENOVO:rn:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: 2491.A3G
  dmi.product.version: ThinkCentre M91
  dmi.sys.vendor: LENOVO
  hciconfig:
   
  rfkill:
   
  syslog: Jun 24 16:43:19 ted-M91 NetworkManager[1108]:   
[1498315399.6618] Loaded device plugin: NMBluezManager 
(/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1700256/+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 1717224] Re: virsh start of virtual guest domain fails with internal error due to low default aio-max-nr sysctl value

2018-02-26 Thread Joseph Salisbury

** No longer affects: linux (Ubuntu Zesty)

** No longer affects: procps (Ubuntu Zesty)

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

Title:
  virsh start of virtual guest domain fails with internal error due to
  low default aio-max-nr sysctl value

Status in Ubuntu on IBM z Systems:
  In Progress
Status in kvm package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Fix Released
Status in procps package in Ubuntu:
  New
Status in linux source package in Xenial:
  In Progress
Status in procps source package in Xenial:
  New
Status in linux source package in Artful:
  In Progress
Status in procps source package in Artful:
  New

Bug description:
  Starting virtual guests via on Ubuntu 16.04.2 LTS installed with its
  KVM hypervisor on an IBM Z14 system LPAR fails on the 18th guest with
  the following error:

  root@zm93k8:/rawimages/ubu1604qcow2# virsh start zs93kag70038
  error: Failed to start domain zs93kag70038
  error: internal error: process exited while connecting to monitor: 
2017-07-26T01:48:26.352534Z qemu-kvm: -drive 
file=/guestimages/data1/zs93kag70038.qcow2,format=qcow2,if=none,id=drive-virtio-disk0,cache=none,aio=native:
 Could not open backing file: Could not set AIO state: Inappropriate ioctl for 
device

  The previous 17 guests started fine:

  root@zm93k8# virsh start zs93kag70020
  Domain zs93kag70020 started

  root@zm93k8# virsh start zs93kag70021
  Domain zs93kag70021 started

  .
  .

  root@zm93k8:/rawimages/ubu1604qcow2# virsh start zs93kag70036
  Domain zs93kag70036 started

  
  We ended up fixing the issue by adding the following line to /etc/sysctl.conf 
: 

  fs.aio-max-nr = 4194304

  ... then, reload the sysctl config file:

  root@zm93k8:/etc# sysctl -p /etc/sysctl.conf
  fs.aio-max-nr = 4194304

  
  Now, we're able to start more guests...

  root@zm93k8:/etc# virsh start zs93kag70036
  Domain zs93kag70036 started

  
  The default value was originally set to 65535: 

  root@zm93k8:/rawimages/ubu1604qcow2# cat /proc/sys/fs/aio-max-nr
  65536

  
  Note, we chose the 4194304 value, because this is what our KVM on System Z 
hypervisor ships as its default value.  Eg.  on our zKVM system: 

  [root@zs93ka ~]# cat /proc/sys/fs/aio-max-nr
  4194304

  ubuntu@zm93k8:/etc$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 16.04.2 LTS
  Release:16.04
  Codename:   xenial
  ubuntu@zm93k8:/etc$

  ubuntu@zm93k8:/etc$ dpkg -s qemu-kvm |grep Version
  Version: 1:2.5+dfsg-5ubuntu10.8

  Is something already documented for Ubuntu KVM users warning them about the 
low default value, and some guidance as to
  how to select an appropriate value?   Also, would you consider increasing the 
default aio-max-nr value to something much
  higher, to accommodate significantly more virtual guests?  

  Thanks!

  ---uname output---
  ubuntu@zm93k8:/etc$ uname -a Linux zm93k8 4.4.0-62-generic #83-Ubuntu SMP Wed 
Jan 18 14:12:54 UTC 2017 s390x s390x s390x GNU/Linux
   
  Machine Type = z14 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   See Problem Description.

  The problem was happening a week ago, so this may not reflect that
  activity.

  This file was collected on Aug 7, one week after we were hitting the
  problem.  If I need to reproduce the problem and get fresh data,
  please let me know.

  /var/log/messages doesn't exist on this system, so I provided syslog
  output instead.

  All data have been collected too late after the problem was observed
  over a week ago.  If you need me to reproduce the problem and get new
  data, please let me know.  That's not a problem.

  Also, we would have to make special arrangements for login access to
  these systems.  I'm happy to run traces and data collection for you as
  needed.  If that's not sufficient, then we'll explore log in access
  for you.

  Thanks...   - Scott G.

  
  I was able to successfully recreate the problem and captured / attached new 
debug docs. 

  Recreate procedure:

  #  Started out with no virtual guests running.

  ubuntu@zm93k8:/home/scottg$ virsh list
   IdName   State
  

  
  # Set fs.aio-max-nr back to original Ubuntu "out of the box" value in 
/etc/sysctl.conf

  ubuntu@zm93k8:~$ tail -1 /etc/sysctl.conf
  fs.aio-max-nr = 65536

  
  ## sysctl -a shows: 

  fs.aio-max-nr = 4194304

  
  ##  Reload sysctl.

  ubuntu@zm93k8:~$ sudo sysctl -p /etc/sysctl.conf
  fs.aio-max-nr = 65536
  ubuntu@zm93k8:~$

  ubuntu@zm93k8:~$ sudo sysctl -a |grep fs.aio-max-nr
  fs.aio-max-nr = 65536

  ubuntu@zm93k8:~$  cat /proc/sys/fs/aio-max-nr
  65536


  # Attempt to start more than 17 qcow2 virtual guests on the Ubuntu
  host.  Fails on the 18th XML.

  Script used to start guests..

[Touch-packages] [Bug 1745713] Re: package linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

Because of that problem I could not only not upgrade the kernel but
couldn't install any software at all.

In my case the problem was caused by a missing udev rule in
/etc/udev/rules.d/. I created the rule when trying to run a windows
installation on a second hd with Virtual Box. Because that didn't come
to work, I deleted the rule again. I don't now why but the system was
trying to copy this rule during the process of upgrading the kernel.
Since I deleted the file, the process of upgrading failed. I tried to
find out, where this rule was still linked so that I could remove the
link and the system wouldn't want to copy this rule anymore, but I
couldn't find out where that was. But restoring the rule did it for me
and the system is upgrading fine again.

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

Title:
  package linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  new installation

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Sat Jan 27 15:50:58 2018
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2018-01-12 (15 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: initramfs-tools
  Title: package linux-image-4.13.0-32-generic 4.13.0-32.35~16.04.1 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1745713/+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 1751893] Re: package bluez 5.37-0ubuntu5.1 failed to install/upgrade: problèmes de dépendances - laissé non configuré

*** This bug is a duplicate of bug 1700256 ***
https://bugs.launchpad.net/bugs/1700256

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


** This bug has been marked a duplicate of bug 1718974
   package bluez 5.37-0ubuntu5.1 failed to install/upgrade: проблемы 
зависимостей — оставляем не настроенным

** This bug is no longer a duplicate of bug 1718974
   package bluez 5.37-0ubuntu5.1 failed to install/upgrade: проблемы 
зависимостей — оставляем не настроенным
** This bug has been marked a duplicate of bug 1700256
   package bluez 5.37-0ubuntu5 failed to install/upgrade: Abhängigkeitsprobleme 
- verbleibt unkonfiguriert

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

Title:
  package bluez 5.37-0ubuntu5.1 failed to install/upgrade: problèmes de
  dépendances - laissé non configuré

Status in bluez package in Ubuntu:
  New

Bug description:
  Dear Community manager,

  I am not a system specialist and I cannot say more about this problem

  Thanks for your help

  Claude

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.37-0ubuntu5.1
  ProcVersionSignature: Ubuntu 4.4.0-104.127-generic 4.4.98
  Uname: Linux 4.4.0-104-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Fri Jan  5 14:52:19 2018
  ErrorMessage: problèmes de dépendances - laissé non configuré
  InstallationDate: Installed on 2016-07-30 (576 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  InterestingModules: bluetooth
  MachineType: Dell Inc. Precision M6500
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-104-generic 
root=UUID=80b71b49-579d-4c19-b1ed-b0f1cee9626e ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: bluez
  Title: package bluez 5.37-0ubuntu5.1 failed to install/upgrade: problèmes de 
dépendances - laissé non configuré
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/04/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A10
  dmi.board.name: 0R1203
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA10:bd06/04/2013:svnDellInc.:pnPrecisionM6500:pvr:rvnDellInc.:rn0R1203:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Precision M6500
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   
  syslog: févr. 26 21:16:01 groix NetworkManager[888]:   
[1519676161.1202] Loaded device plugin: NMBluezManager 
(/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1751893/+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 1750379] Re: Distortion Realtek ALC887

If you experience the same sounding glitching in Win 10 then yes this
sounds like a hardware problem. But you also said that "Amplification
worked well for years before recent PulseAudio update", so I wonder if
you can find any older Ubuntu release where it works still? Try live
booting some of these:

  http://cdimages.ubuntu.com/releases/

Otherwise, try replacing your 3.5mm audio splitter and related cables. I
was stunned in the past to discover that cheap/broken audio cables can
severely distort sound, so it's probably worth trying other cables and
connectors.

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

Title:
  Distortion Realtek ALC887

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Sounds can distort even when not amplified. Amplification worked well
  for years before recent PulseAudio update. The audio is Realtek ALC887
  under an IntelG41 Chipset with GA-G41M-Combo main board;

  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  I am seeking to engage upstream for April LTS release. Windows have
  abandoned this esoteric hardware! Please Ubuntu! Keep a C2D user
  going!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu6
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  fleamour   1049 F pulseaudio
   /dev/snd/controlC2:  fleamour   1049 F pulseaudio
   /dev/snd/controlC0:  fleamour   1049 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 19 13:54:33 2018
  InstallationDate: Installed on 2018-02-19 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FB
  dmi.board.name: G41M-Combo
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFB:bd10/25/2012:svnGigabyteTechnologyCo.,Ltd.:pnG41M-Combo:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnG41M-Combo:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: G41M-Combo
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750379/+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 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04)

2018-02-26 Thread henczati

As mentioned in #47, same problem on trusty + xenial HWE stack
(14.04.5).

Additionally, had a gcc version mismatch, don't know where that came
from.

Meta package gcc was 4:4.8.2-1ubuntu6, but /usr/bin/gcc (and corresponding 
package gcc-4.8) was 4.8.5-1ubuntu1~14.04 .
I also had installed just gcc-4.9-base (without even gcc-4.9) due to some 
dependencies.

Went back to -112 kernel.

Tried #57 (@cjjefcoat) steps, but did not trigger a driver rebuild.

I had a lot of PPA-s and manual file-wrapped deb lines in 
/etc/apt/sources.list.d/.
I had ubuntu-toolchain-r/ppa, not ubuntu-toolchain-r/test, but IIRC purging 
failed somehow (cant remember, couple of days ago), probably due to same 
mismatch.

So just deleted all entries from /etc/apt/sources.list.d/, manually
cleaned /etc/apt/sources.list, updated repo cache.

Then tried to force-install (downgrade) gcc-4.8 and gcc-4.8-base to 
4.8.4-2ubuntu1~14.04.4, to make it in sync with the gcc package again.
After force-picking all the needed dependencies, I ended up with
sudo apt-get install gcc-4.8 gcc-4.8-base:i386=4.8.4-2ubuntu1~14.04.4 
gcc-4.8-base:amd64=4.8.4-2ubuntu1~14.04.4 g++-4.8=4.8.4-2ubuntu1~14.04.4 
libstdc++-4.8-dev=4.8.4-2ubuntu1~14.04.4 libgcc-4.8-dev=4.8.4-2ubuntu1~14.04.4 
cpp-4.8=4.8.4-2ubuntu1~14.04.4 libgl1-mesa-dri 
libgfortran3=4.8.4-2ubuntu1~14.04.4 libstdc++6=4.8.4-2ubuntu1~14.04.4 
libquadmath0=4.8.4-2ubuntu1~14.04.4 libgomp1=4.8.4-2ubuntu1~14.04.4 
libitm1=4.8.4-2ubuntu1~14.04.4 libatomic1=4.8.4-2ubuntu1~14.04.4 
libasan0=4.8.4-2ubuntu1~14.04.4 libtsan0=4.8.4-2ubuntu1~14.04.4

Somewhere in the process (do not remember when) the nvidia driver, dkms, the 
HWE stack (kernel + xorg) and some other stuff got uninstalled (due to missing 
dependencies).
Probably I could have avoided that and was just too strict on removing 
potentially screwed up stuff.
I think I totally removed gcc-4.8 or even all of gcc before reinstalling with 
the (assumed) correct version.

So after "aligning" gcc, I installed back the xenial kernel (a'la ubuntu wiki 
HWE page, for multiarch):
sudo apt-get install --install-recommends linux-generic-lts-xenial 
xserver-xorg-core-lts-xenial xserver-xorg-lts-xenial 
xserver-xorg-video-all-lts-xenial xserver-xorg-input-all-lts-xenial 
libwayland-egl1-mesa-lts-xenial libgl1-mesa-glx-lts-xenial 
libgl1-mesa-glx-lts-xenial:i386 libglapi-mesa-lts-xenial:i386

There the amd64 and i386 versions of libgl1-mesa-dri-lts-xenial had a 
/etc/drirc conflict.
Apt was useless, just returned a dpkg fail (with or without -f).
Overwriting /etc/drirc with /etc/drirc.dpkg-new was not enough, had to remove 
/etc/drirc alltogether.
THEN on `sudo apt-get install -f` apt asked me to resolve /etc/drirc conflict 
using apt-s command line query.
One said Unigine Heaven 3.0 this and that setting, the other said "Unigine 
Heaven 3.0 and older contain too many bugs and can't be supported [...]".
Went with the second, seemingly newer one.

Then came the nvidia driver (with forcing the dependencies previously removed 
by apt):
sudo apt-get -f install nvidia-340 dkms acpid lib32gcc1 libc6-i386 nvidia-prime 
nvidia-opencl-icd-340

This compiled the driver and
modinfo nvidia-340 -k 4.4.0-116-generic | grep vermagic
said retpoline.

Reboot, works.

Just like that. :)

I guess the system is ripe for reinstall. :)

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

Title:
  4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and
  16.04)

Status in linux package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-384 package in Ubuntu:
  Confirmed
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Running fine with nvidia-384 until this kernel update came along.
  When booted into the new kernel, got super low resolution and nvidia-
  settings was missing most of its functionality - could not change
  resolution.

  Rebooted into 4.4.0-112 kernel and all was well.

  The root cause of the problem has been found to be installing the -116
  kernel without a sufficiently updated version of gcc.  In my case, my
  system received the gcc update AFTER the kernel update.

  Uninstalling the -116 kernel and reinstalling it with the updated
  version of gcc solved the problem for me.

  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3)
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Feb 21 19:23:39 2018
  DistUpgraded: Fresh install

[Touch-packages] [Bug 1717224] Re: virsh start of virtual guest domain fails with internal error due to low default aio-max-nr sysctl value

2018-02-26 Thread Joseph Salisbury

Commit 2a8a98673c13 has been in Xenial and Artful for some time now.
Can you confirm this bug is now resolved with the latest updates.

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

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

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

Title:
  virsh start of virtual guest domain fails with internal error due to
  low default aio-max-nr sysctl value

Status in Ubuntu on IBM z Systems:
  In Progress
Status in kvm package in Ubuntu:
  Won't Fix
Status in linux package in Ubuntu:
  Fix Released
Status in procps package in Ubuntu:
  New
Status in linux source package in Xenial:
  Fix Released
Status in procps source package in Xenial:
  New
Status in linux source package in Artful:
  Fix Released
Status in procps source package in Artful:
  New

Bug description:
  Starting virtual guests via on Ubuntu 16.04.2 LTS installed with its
  KVM hypervisor on an IBM Z14 system LPAR fails on the 18th guest with
  the following error:

  root@zm93k8:/rawimages/ubu1604qcow2# virsh start zs93kag70038
  error: Failed to start domain zs93kag70038
  error: internal error: process exited while connecting to monitor: 
2017-07-26T01:48:26.352534Z qemu-kvm: -drive 
file=/guestimages/data1/zs93kag70038.qcow2,format=qcow2,if=none,id=drive-virtio-disk0,cache=none,aio=native:
 Could not open backing file: Could not set AIO state: Inappropriate ioctl for 
device

  The previous 17 guests started fine:

  root@zm93k8# virsh start zs93kag70020
  Domain zs93kag70020 started

  root@zm93k8# virsh start zs93kag70021
  Domain zs93kag70021 started

  .
  .

  root@zm93k8:/rawimages/ubu1604qcow2# virsh start zs93kag70036
  Domain zs93kag70036 started

  
  We ended up fixing the issue by adding the following line to /etc/sysctl.conf 
: 

  fs.aio-max-nr = 4194304

  ... then, reload the sysctl config file:

  root@zm93k8:/etc# sysctl -p /etc/sysctl.conf
  fs.aio-max-nr = 4194304

  
  Now, we're able to start more guests...

  root@zm93k8:/etc# virsh start zs93kag70036
  Domain zs93kag70036 started

  
  The default value was originally set to 65535: 

  root@zm93k8:/rawimages/ubu1604qcow2# cat /proc/sys/fs/aio-max-nr
  65536

  
  Note, we chose the 4194304 value, because this is what our KVM on System Z 
hypervisor ships as its default value.  Eg.  on our zKVM system: 

  [root@zs93ka ~]# cat /proc/sys/fs/aio-max-nr
  4194304

  ubuntu@zm93k8:/etc$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 16.04.2 LTS
  Release:16.04
  Codename:   xenial
  ubuntu@zm93k8:/etc$

  ubuntu@zm93k8:/etc$ dpkg -s qemu-kvm |grep Version
  Version: 1:2.5+dfsg-5ubuntu10.8

  Is something already documented for Ubuntu KVM users warning them about the 
low default value, and some guidance as to
  how to select an appropriate value?   Also, would you consider increasing the 
default aio-max-nr value to something much
  higher, to accommodate significantly more virtual guests?  

  Thanks!

  ---uname output---
  ubuntu@zm93k8:/etc$ uname -a Linux zm93k8 4.4.0-62-generic #83-Ubuntu SMP Wed 
Jan 18 14:12:54 UTC 2017 s390x s390x s390x GNU/Linux
   
  Machine Type = z14 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   See Problem Description.

  The problem was happening a week ago, so this may not reflect that
  activity.

  This file was collected on Aug 7, one week after we were hitting the
  problem.  If I need to reproduce the problem and get fresh data,
  please let me know.

  /var/log/messages doesn't exist on this system, so I provided syslog
  output instead.

  All data have been collected too late after the problem was observed
  over a week ago.  If you need me to reproduce the problem and get new
  data, please let me know.  That's not a problem.

  Also, we would have to make special arrangements for login access to
  these systems.  I'm happy to run traces and data collection for you as
  needed.  If that's not sufficient, then we'll explore log in access
  for you.

  Thanks...   - Scott G.

  
  I was able to successfully recreate the problem and captured / attached new 
debug docs. 

  Recreate procedure:

  #  Started out with no virtual guests running.

  ubuntu@zm93k8:/home/scottg$ virsh list
   IdName   State
  

  
  # Set fs.aio-max-nr back to original Ubuntu "out of the box" value in 
/etc/sysctl.conf

  ubuntu@zm93k8:~$ tail -1 /etc/sysctl.conf
  fs.aio-max-nr = 65536

  
  ## sysctl -a shows: 

  fs.aio-max-nr = 4194304

  
  ##  Reload sysctl.

  ubuntu@zm93k8:~$ sudo sysctl -p /etc/sysctl.conf
  fs.aio-max-nr = 65536
  ubuntu@zm93k8:~$

  ubuntu@zm93k8:~$ sudo sysctl -a |grep fs.aio-max-nr
  fs.aio-max-nr = 65536

Re: [Touch-packages] [Bug 1705297] Re: login after booting hangs

Hi,

thank you for dealing with this matter.
But before performing this I would like to know why this may be necessary
because I regularly do "dist-upgrade"s, and -- on the other hand --
I am not sure that I could report on results (what results?)
since this bug happens only rarely (only once during the last few weeks,
If I remember it correctly) and is not predictable.

Best regards, Peter

On Mon, 26 Feb 2018, Christopher M. Penalver wrote:

> Peter Schmitt, to see if this is already resolved in your release, 
could
> you please update your HWE stack as per
> https://wiki.ubuntu.com/Kernel/LTSEnablementStack and advise to the
> results?
>
> ** Tags added: bios-outdated-1.23
>
> -- 
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1705297
>
> Title:
>  login after booting hangs
>
> Status in xorg package in Ubuntu:
>  Incomplete
>
> Bug description:
>  The following occurs occasionally (seemingly at random):
>
>  After booting and logging in only the background image is shown, and no 
> action is possbile.
>  After switching to tty1, logging in and performing a shutdown/reboot
>  everything is o.k.
>
>  (Sometimes -- seldomly -- on tty1 an error message was shown.)
>
>  peter@TP:~/bin$ uname --all
>  Linux TP 4.4.0-83-generic #106-Ubuntu SMP Mon Jun 26 17:54:43 UTC 2017 
> x86_64 x86_64 x86_64 GNU/Linux
>  ---
>  .tmp.unity_support_test.0:
>
>  ApportVersion: 2.20.1-0ubuntu2.15
>  Architecture: amd64
>  CompizPlugins: No value set for 
> `/apps/compiz-1/general/screen0/options/active_plugins'
>  CompositorRunning: compiz
>  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
>  CompositorUnredirectFSW: true
>  CurrentDesktop: Unity
>  DistUpgraded: Fresh install
>  DistroCodename: xenial
>  DistroRelease: Ubuntu 16.04
>  DistroVariant: ubuntu
>  ExtraDebuggingInterest: Yes
>  GraphicsCard:
>   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) 
> (prog-if 00 [VGA controller])
> Subsystem: Lenovo Skylake Integrated Graphics [17aa:2231]
>  InstallationDate: Installed on 2016-11-12 (471 days ago)
>  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
> (20160719)
>  Lsusb:
>   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>   Bus 001 Device 004: ID 138a:0017 Validity Sensors, Inc. Fingerprint Reader
>   Bus 001 Device 003: ID 04ca:7058 Lite-On Technology Corp.
>   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>  MachineType: LENOVO 20FJS36700
>  Package: xorg 1:7.7+13ubuntu3
>  PackageArchitecture: amd64
>  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-116-generic 
> root=UUID=929e493d-18e2-41ed-a0a1-b34fd11acd2e ro quiet splash vt.handoff=7
>  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
>  Tags:  xenial ubuntu compiz-0.9
>  Uname: Linux 4.4.0-116-generic x86_64
>  UpgradeStatus: No upgrade log present (probably fresh install)
>  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>  _MarkForUpload: True
>  dmi.bios.date: 04/20/2016
>  dmi.bios.vendor: LENOVO
>  dmi.bios.version: N1KET21W (1.08 )
>  dmi.board.asset.tag: Not Available
>  dmi.board.name: 20FJS36700
>  dmi.board.vendor: LENOVO
>  dmi.board.version: Not Defined
>  dmi.chassis.asset.tag: No Asset Information
>  dmi.chassis.type: 10
>  dmi.chassis.vendor: LENOVO
>  dmi.chassis.version: None
>  dmi.modalias: 
> dmi:bvnLENOVO:bvrN1KET21W(1.08):bd04/20/2016:svnLENOVO:pn20FJS36700:pvrThinkPadT560:rvnLENOVO:rn20FJS36700:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
>  dmi.product.name: 20FJS36700
>  dmi.product.version: ThinkPad T560
>  dmi.sys.vendor: LENOVO
>  version.compiz: compiz 1:0.9.12.3+16.04.20171116-0ubuntu1
>  version.ia32-libs: ia32-libs N/A
>  version.libdrm2: libdrm2 2.4.83-1~16.04.1
>  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
>  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
>  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
>  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
>  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
>  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
>  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
> 2:2.99.917+git20160325-1ubuntu1.2
>  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
> 1:1.0.12-1build2
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1705297/+subscriptions
>

Peter Schmittpeter.schm...@univie.ac.at
   Adolf Gstöttner-Gasse 6/37, 1200 Wien

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

Title:
  login after booting hangs

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  The following occurs occasionally (seemingly at random):

  After

[Touch-packages] [Bug 1742573] Re: package linux-image-4.13.0-26-generic 4.13.0-26.29~16.04.2 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

Because of that problem I could not only not upgrade the kernel but
couldn't install any software at all.

In my case the problem was caused by a missing udev rule in
/etc/udev/rules.d/. I created the rule when trying to run a windows
installation on a second hd with Virtual Box. Because that didn't come
to work, I deleted the rule again. I don't now why but the system was
trying to copy this rule during the process of upgrading the kernel.
Since I deleted the file, the process of upgrading failed. I tried to
find out, where this rule was still linked so that I could remove the
link and the system wouldn't want to copy this rule anymore, but I
couldn't find out where that was. But restoring the rule did it for me
and the system is upgrading fine again.

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

Title:
  package linux-image-4.13.0-26-generic 4.13.0-26.29~16.04.2 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Fully encrypted system with separate encrypted /home partition.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.13.0-26-generic 4.13.0-26.29~16.04.2
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Thu Jan 11 06:08:19 2018
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.24
  SourcePackage: initramfs-tools
  Title: package linux-image-4.13.0-26-generic 4.13.0-26.29~16.04.2 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1742573/+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 1751689] Re: apparmor="DENIED" operation="open" profile="libreoffice-soffice" name="/etc/sane.d/dll.d/hplip"

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

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

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

Title:
  apparmor="DENIED" operation="open" profile="libreoffice-soffice"
  name="/etc/sane.d/dll.d/hplip"

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  currently able to scan with xsane utility. libreoffice is not able to
  scan because it cannot find the scanner.

  log shows

  
  Feb 25 21:44:34 know kernel: [ 2224.752585] audit: type=1400 
audit(1519613074.593:93): apparmor="DENIED" operation="open" 
profile="libreoffice-soffice" name="/etc/sane.d/dll.d/hplip" pid=23827 
comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1001 ouid=0
  Feb 25 21:44:34 know kernel: [ 2224.752589] audit: type=1400 
audit(1519613074.593:94): apparmor="DENIED" operation="open" 
profile="libreoffice-soffice" name="/etc/sane.d/dll.conf" pid=23827 
comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1001 ouid=0
  Feb 25 21:44:34 know kernel: [ 2224.752591] audit: type=1400 
audit(1519613074.593:95): apparmor="DENIED" operation="open" 
profile="libreoffice-soffice" name="/home/darla/.so_sane_state" pid=23827 
comm="soffice.bin" requested_mask="r" denied_mask="r" fsuid=1001 ouid=1001

  
  this stopped working after latest "do-release-upgrade"

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: apport 2.20.7-0ubuntu3.7
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CrashReports:
   664:1001:121:0:2018-02-25 21:41:06.022625011 -0500:2018-02-25 
21:41:06.022625011 -0500:/var/crash/_usr_bin_xsane.1001.upload
   600:112:121:0:2018-02-25 21:41:10.086691806 -0500:2018-02-25 
21:41:10.086691806 -0500:/var/crash/_usr_bin_xsane.1001.uploaded
   640:1001:121:1939286:2018-02-25 21:41:05.022624969 -0500:2018-02-25 
21:41:06.122626654 -0500:/var/crash/_usr_bin_xsane.1001.crash
   640:1001:121:14271279:2018-02-25 20:56:20.565849525 -0500:2018-02-25 
20:57:09.433475929 -0500:/var/crash/_usr_bin_ckb.1001.crash
  CurrentDesktop: XFCE
  Date: Sun Feb 25 22:00:01 2018
  InstallationDate: Installed on 2017-04-19 (312 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to artful on 2018-02-06 (20 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1751689/+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 1718974] Re: package bluez 5.37-0ubuntu5.1 failed to install/upgrade: проблемы зависимостей — оставляем не настроенным

*** This bug is a duplicate of bug 1700256 ***
https://bugs.launchpad.net/bugs/1700256

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


** This bug has been marked a duplicate of bug 1700256
   package bluez 5.37-0ubuntu5 failed to install/upgrade: Abhängigkeitsprobleme 
- verbleibt unkonfiguriert

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

Title:
  package bluez 5.37-0ubuntu5.1 failed to install/upgrade: проблемы
  зависимостей — оставляем не настроенным

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  When updating

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.37-0ubuntu5.1
  ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  Date: Fri Sep 22 22:25:17 2017
  ErrorMessage: проблемы зависимостей — оставляем не настроенным
  InstallationDate: Installed on 2017-07-29 (55 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  InterestingModules: bluetooth
  MachineType: Gigabyte Technology Co., Ltd. P35-S3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-35-generic 
root=UUID=68eb309e-4d7d-4735-b7ec-c972ec4839d6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: bluez
  Title: package bluez 5.37-0ubuntu5.1 failed to install/upgrade: проблемы 
зависимостей — оставляем не настроенным
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2009
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F8
  dmi.board.name: P35-S3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF8:bd06/19/2009:svnGigabyteTechnologyCo.,Ltd.:pnP35-S3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnP35-S3:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: P35-S3
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  hciconfig:
   
  rfkill:
   
  syslog:
   Сен 22 22:23:03 leonid-P35-S3 NetworkManager[776]:   [1506108183.9686] 
Loaded device plugin: NMBluezManager 
(/usr/lib/x86_64-linux-gnu/NetworkManager/libnm-device-plugin-bluetooth.so)
   Сен 22 22:23:57 leonid-P35-S3 ureadahead[249]: 
ureadahead:unity-control-center_bluetooth.png: Относительный путь пропущен

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1718974/+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 1700256] Re: package bluez 5.37-0ubuntu5 failed to install/upgrade [bluez depends on udev (> = 170-1); but: Package udev is not configured yet.]