[Touch-packages] [Bug 1733046] Re: package tzdata 2017c-0ubuntu0.14.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package tzdata 2017c-0ubuntu0.14.04 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in tzdata package in Ubuntu:
  New

Bug description:
  Normal update. Nothing to add.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: tzdata 2017c-0ubuntu0.14.04
  ProcVersionSignature: Ubuntu 4.4.0-93.116~14.04.1-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: amd64
  Date: Sat Nov 18 07:38:14 2017
  DuplicateSignature: package:tzdata:2017c-0ubuntu0.14.04:subprocess installed 
post-installation script returned error exit status 128
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-01-25 (296 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: tzdata
  Title: package tzdata 2017c-0ubuntu0.14.04 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/tzdata/+bug/1733046/+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 1733046] [NEW] package tzdata 2017c-0ubuntu0.14.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128

[Jo-Erlend Schinstad]

Public bug reported:

Normal update. Nothing to add.

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: tzdata 2017c-0ubuntu0.14.04
ProcVersionSignature: Ubuntu 4.4.0-93.116~14.04.1-generic 4.4.79
Uname: Linux 4.4.0-93-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.25
Architecture: amd64
Date: Sat Nov 18 07:38:14 2017
DuplicateSignature: package:tzdata:2017c-0ubuntu0.14.04:subprocess installed 
post-installation script returned error exit status 128
ErrorMessage: subprocess installed post-installation script returned error exit 
status 128
InstallationDate: Installed on 2017-01-25 (296 days ago)
InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.17.5ubuntu5.7
 apt  1.0.1ubuntu2.17
SourcePackage: tzdata
Title: package tzdata 2017c-0ubuntu0.14.04 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package trusty

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

Title:
  package tzdata 2017c-0ubuntu0.14.04 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 128

Status in tzdata package in Ubuntu:
  New

Bug description:
  Normal update. Nothing to add.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: tzdata 2017c-0ubuntu0.14.04
  ProcVersionSignature: Ubuntu 4.4.0-93.116~14.04.1-generic 4.4.79
  Uname: Linux 4.4.0-93-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: amd64
  Date: Sat Nov 18 07:38:14 2017
  DuplicateSignature: package:tzdata:2017c-0ubuntu0.14.04:subprocess installed 
post-installation script returned error exit status 128
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2017-01-25 (296 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.7
   apt  1.0.1ubuntu2.17
  SourcePackage: tzdata
  Title: package tzdata 2017c-0ubuntu0.14.04 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/tzdata/+bug/1733046/+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 1732559] Re: package apport 2.20.1-0ubuntu2.12 failed to install/upgrade: end of file on stdin at conffile prompt

[Launchpad Bug Tracker]

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

Title:
  package apport 2.20.1-0ubuntu2.12 failed to install/upgrade: end of
  file on stdin at conffile prompt

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  weather applet crashes on logou

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.12
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.1-0ubuntu2.12
  Architecture: amd64
  CrashReports: 600:0:116:2842973:2017-11-15 19:14:12.331785678 
-0400:2017-11-15 19:14:13.331785678 -0400:/var/crash/apport.0.crash
  Date: Wed Nov 15 19:14:13 2017
  ErrorMessage: end of file on stdin at conffile prompt
  InstallationDate: Installed on 2016-08-04 (468 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: apport
  Title: package apport 2.20.1-0ubuntu2.12 failed to install/upgrade: end of 
file on stdin at conffile prompt
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.init.apport.conf: 2016-04-13T22:46:42
  mtime.conffile..etc.init.d.apport: 2016-03-31T09:43:38
  mtime.conffile..etc.logrotate.d.apport: 2016-04-13T22:46:42

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1732559/+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 1725840] Re: resolvconf not correctly configured after update from 17.04 to 17.10

[MuppaneniBharath]

I do have the same issue after upgrade from 17.4-17.10.   So do we have
a FIX !!!

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

Title:
  resolvconf not correctly configured after update from 17.04 to 17.10

Status in resolvconf package in Ubuntu:
  Confirmed

Bug description:
  After having updated my laptop from Ubuntu 17.04 to 17.10, the DNS
  lookup on my wireless network connection did not work any more.

  As it seems, the file /etc/resolv.conf was static and contained wrong
  data assigned by the NetworkManager. When I changed the file content
  manually to

nameserver 127.0.0.53

  DNS lookup worked fine. After reboot, however, I had to repeat this
  operation since NetworkManager seems to have replaced the file
  content.

  Finally, I found a solution. Running

  sudo dpkg-reconfigure resolvconf

  the file /etc/resolv.conf was replaced by the link

  /etc/resolv.conf -> ../run/resolvconf/resolv.conf

  Now, the wireless network seems to work properly.

  Hence, there must be some kind of bug during the update process from
  Ubuntu 17.04 to 17.10 that impedes resolvconf to be configured
  properly.

  Best regards,

  Artur

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: resolvconf 1.79ubuntu8
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 21 23:17:38 2017
  InstallationDate: Installed on 2013-10-18 (1463 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  PackageArchitecture: all
  SourcePackage: resolvconf
  UpgradeStatus: Upgraded to artful on 2017-10-19 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1725840/+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 1603715] Re: bluetooth unavailable after rfkill hard (or soft) unblocking and after suspend/resume

[Bug Watch Updater]

** Changed in: bluez
   Status: New => Incomplete

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

Title:
  bluetooth unavailable after rfkill hard (or soft) unblocking and after
  suspend/resume

Status in Bluez Utilities:
  Incomplete
Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  DELL Latitude E5510 has a hardware switch to disable and enable
  bluetooth and wifi devices ("hard blocking" in terms of rfkill). In
  terms of wifi, this works great: After hard unblocking, the device
  resumes back to normal operation without any manual intervention. That
  was also working with bluetooth as of ubuntu 14.04, kernel 4.2.

  In ubuntu 16.04, kernel 4.4.0-31-generic, together with systemd, this
  is not working any more:

  After hard blocking and unblocking

  - bluetooth is not working at all
  - the applet-indicator remains gray
  - bluetooth cannot be enabled with the applet-indicator (see 
https://storage6.static.itmages.com/i/16/0717/h_1468721829_7715160_83cd33bfba.png).
 Applet-indicator remains gray
  - rfkill list tells me that the kernel knows about the hard unblocking (turns 
from "yes" to "no"):
  rfkill list bluetooth
  2: dell-bluetooth: Bluetooth
   Soft blocked: no
   Hard blocked: no
  8: hci0: Bluetooth
   Soft blocked: no
   Hard blocked: no

  The device is a
  sudo lsusb
  Bus 002 Device 010: ID 413c:8187 Dell Computer Corp. DW375 Bluetooth Module

  Workaround: After a

  sudo service bluetooth restart

  the bluetooth device turns back to normal operation and the applet-
  indicator turns from gray to black (available).

  Suggested fix: Make the workaround obsolete.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sun Jul 17 04:00:58 2016
  InstallationDate: Installed on 2014-11-29 (595 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Dell Inc. Latitude E5510
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-31-generic 
root=UUID=6408c2d9-1b60-43d7-9a7f-2dceeb40de28 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to xenial on 2016-06-15 (31 days ago)
  dmi.bios.date: 12/06/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A16
  dmi.board.name: 023HKR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA16:bd12/06/2013:svnDellInc.:pnLatitudeE5510:pvr0001:rvnDellInc.:rn023HKR:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Latitude E5510
  dmi.product.version: 0001
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/1603715/+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 1733029] [NEW] Asus N55JM in 2.1 mode alsa SonicMaster subwoofer doesn't work

[Dmitriy]

Public bug reported:

I expect my subwoofer working when choosing ALSA 2.1 in VLC audio settings, but 
in fact it doesn't sound at all
AlsaMixer shows BassSpeaker, but changing it's volume has no effect
Also I tried the trick described in similar bug I 
found(https://bugs.launchpad.net/ubuntu/+source/alsa-tools/+bug/1405691, 
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/871808) with 
hdajackretask with pin 0x1a as LFE and hda_analyzer - no effect though

System Kubuntu
Description:Ubuntu 17.10
Release:17.10

alsaplayer-alsa:
  Установлен: (отсутствует)
  Кандидат:   0.99.81-2
  Таблица версий:
 0.99.81-2 500
500 http://ru.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
alsa-base:
  Установлен: 1.0.25+dfsg-0ubuntu5
  Кандидат:   1.0.25+dfsg-0ubuntu5
  Таблица версий:
 *** 1.0.25+dfsg-0ubuntu5 500
500 http://ru.archive.ubuntu.com/ubuntu artful/main amd64 Packages
500 http://ru.archive.ubuntu.com/ubuntu artful/main i386 Packages
100 /var/lib/dpkg/status
alsa-source:
  Установлен: (отсутствует)
  Кандидат:   1.0.25+dfsg-0ubuntu5
  Таблица версий:
 1.0.25+dfsg-0ubuntu5 500
500 http://ru.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
500 http://ru.archive.ubuntu.com/ubuntu artful/universe i386 Packages
alsamixergui:
  Установлен: 0.9.0rc2-1-10
  Кандидат:   0.9.0rc2-1-10
  Таблица версий:
 *** 0.9.0rc2-1-10 500
500 http://ru.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
100 /var/lib/dpkg/status
alsaplayer-output:
  Установлен: (отсутствует)
  Кандидат:   (отсутствует)
  Таблица версий:
alsaplayer:
  Установлен: (отсутствует)
  Кандидат:   (отсутствует)
  Таблица версий:
alsaplayer-jack:
  Установлен: (отсутствует)
  Кандидат:   0.99.81-2
  Таблица версий:
 0.99.81-2 500
500 http://ru.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
alsaplayer-common:
  Установлен: (отсутствует)
  Кандидат:   0.99.81-2
  Таблица версий:
 0.99.81-2 500
500 http://ru.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
alsa:
  Установлен: (отсутствует)
  Кандидат:   (отсутствует)
  Таблица версий:
alsaplayer-esd:
  Установлен: (отсутствует)
  Кандидат:   (отсутствует)
  Таблица версий:
alsaplayer-gtk:
  Установлен: (отсутствует)
  Кандидат:   0.99.81-2
  Таблица версий:
 0.99.81-2 500
500 http://ru.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
alsa-utils:
  Установлен: 1.1.3-1ubuntu1
  Кандидат:   1.1.3-1ubuntu1
  Таблица версий:
 *** 1.1.3-1ubuntu1 500
500 http://ru.archive.ubuntu.com/ubuntu artful/main amd64 Packages
100 /var/lib/dpkg/status
alsaplayer-text:
  Установлен: (отсутствует)
  Кандидат:   0.99.81-2
  Таблица версий:
 0.99.81-2 500
500 http://ru.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
alsa-firmware-loaders:
  Установлен: (отсутствует)
  Кандидат:   1.1.3-1
  Таблица версий:
 1.1.3-1 500
500 http://ru.archive.ubuntu.com/ubuntu artful/multiverse amd64 Packages
alsaplayer-xosd:
  Установлен: (отсутствует)
  Кандидат:   0.99.81-2
  Таблица версий:
 0.99.81-2 500
500 http://ru.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
alsa-tools:
  Установлен: 1.1.3-1
  Кандидат:   1.1.3-1
  Таблица версий:
 *** 1.1.3-1 500
500 http://ru.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
100 /var/lib/dpkg/status
alsaplayer-nas:
  Установлен: (отсутствует)
  Кандидат:   0.99.81-2
  Таблица версий:
 0.99.81-2 500
500 http://ru.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
alsaplayer-oss:
  Установлен: (отсутствует)
  Кандидат:   0.99.81-2
  Таблица версий:
 0.99.81-2 500
500 http://ru.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
alsaplayer-interface:
  Установлен: (отсутствует)
  Кандидат:   (отсутствует)
  Таблица версий:
alsaplayer-daemon:
  Установлен: (отсутствует)
  Кандидат:   0.99.81-2
  Таблица версий:
 0.99.81-2 500
500 http://ru.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
alsa-tools-gui:
  Установлен: 1.1.3-1
  Кандидат:   1.1.3-1
  Таблица версий:
 *** 1.1.3-1 500
500 http://ru.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
100 /var/lib/dpkg/status
alsa-oss:
  Установлен: (отсутствует)
  Кандидат:   1.0.28-1ubuntu1
  Таблица версий:
 1.0.28-1ubuntu1 500
500 http://ru.archive.ubuntu.com/ubuntu artful/universe amd64 Packages

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


** Tags: asus n55 sound

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

Title:
  Asus N55JM in 2.1 mode alsa SonicMaster subwoofer doesn't work

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I expect my subwoofer working when choosing ALSA 2.1 in VLC audio settings, 
but in fact 

[Touch-packages] [Bug 1732997] Re: bionic bash 4.4-5 failed to unpack

[shwn vntr]

its no wonder people don't report or fix bugs.. y'all make it so hard to do so..
i have no idea what url it wants.. but here is the file in problem..
https://launchpad.net/ubuntu/bionic/armhf/bash/4.4-5ubuntu1
it is also happening with the artful file.. seeing how they are the same file.


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

** Package changed: bash (Ubuntu) => armhf

** Project changed: armhf => bash (Ubuntu)

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

Title:
  bionic bash 4.4-5 failed to unpack

Status in bash package in Ubuntu:
  New

Bug description:
  Failure while unpacking required packages  In debootstrap
  bash_4.4-5ubuntu1_armhf.deb is at fault.
   my question is can i get an eta on when the file will be updated/fixed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1732997/+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 1733026] [NEW] Fatale IO Error 11

[Roberto Stagi]

Public bug reported:

I just reboot my system and found it in this way.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-38-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.12
Architecture: amd64
BootLog:
 
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
Date: Sat Nov 18 01:44:45 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics Controller 
[1043:124d]
   Subsystem: ASUSTeK Computer Inc. GeForce GT 720M [1043:124d]
InstallationDate: Installed on 2017-11-16 (2 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: ASUSTeK COMPUTER INC. X550CC
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-38-generic.efi.signed 
root=UUID=f8ce73cd-f4c0-4953-944a-a58b4b75917a ro quiet splash
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/24/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X550CC.300
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X550CC
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX550CC.300:bd03/24/2014:svnASUSTeKCOMPUTERINC.:pnX550CC:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550CC:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: X550CC
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
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: Sat Nov 18 01:37:23 2017
xserver.configfile: default
xserver.errors:
 dbus-core: error connecting to system bus: 
org.freedesktop.DBus.Error.FileNotFound (Failed to connect to socket 
/var/run/dbus/system_bus_socket: No such file or directory)
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
 NOUVEAU(G0): [XvMC] Failed to initialize extension.
 dbus-core: error connecting to system bus: 
org.freedesktop.DBus.Error.FileNotFound (Failed to connect to socket 
/var/run/dbus/system_bus_socket: No such file or directory)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1~16.04.4
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug ubuntu xenial

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

Title:
  Fatale IO Error 11

Status in xorg package in Ubuntu:
  New

Bug description:
  I just reboot my system and found it in this way.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.12
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Sat Nov 18 01:44:45 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 3rd Gen Core processor Graphics 
Controller [1043:124d]
 Subsystem: ASUSTeK Computer Inc. GeForce GT 720M [1043:124d]
  InstallationDate: Installed on 2017-11-16 (2 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: ASUSTeK COMPUTER INC. X550CC
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-38-generic.efi.signed 
root=UUID=f8ce73cd-f4c0-4953-944a-a58b4b75917a ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably 

[Touch-packages] [Bug 1732997] [NEW] bionic bash 4.4-5 failed to unpack

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Failure while unpacking required packages  In debootstrap
bash_4.4-5ubuntu1_armhf.deb is at fault.
 my question is can i get an eta on when the file will be updated/fixed.

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


** Tags: bot-comment
-- 
bionic bash 4.4-5 failed to unpack
https://bugs.launchpad.net/bugs/1732997
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to bash in Ubuntu.

-- 
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 1732997] [NEW] bionic bash 4.4-5 failed to unpack

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Failure while unpacking required packages  In debootstrap
bash_4.4-5ubuntu1_armhf.deb is at fault.
 my question is can i get an eta on when the file will be updated/fixed.

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


** Tags: bot-comment
-- 
bionic bash 4.4-5 failed to unpack
https://bugs.launchpad.net/bugs/1732997
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to bash in Ubuntu.

-- 
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 1717992] Re: Sound silently plays to "Dummy Output"

[isaac]

The same issue here, on Ubuntu 17.10. Only "Dummy Output" found in
Output window.

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

Title:
  Sound silently plays to "Dummy Output"

Status in linux package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Since upgrade to 4.10.0-35-generic in Ubuntu 17.04, the sound card is
  detected, but pavucontrol has only "Dummy Output". Bar animation shows
  audio is playing, but no sound is heard. alsamixer is working fine,
  but audio still can't be heard. Configuration tab says "No cards
  available for configuration".

  $ lspci -v
  0:1f.3 Audio device: Intel Corporation Device 9d71 (rev 21)
Subsystem: Dell Device 0781
Flags: bus master, fast devsel, latency 32, IRQ 283
Memory at d5328000 (64-bit, non-prefetchable) [size=16K]
Memory at d530 (64-bit, non-prefetchable) [size=64K]
Capabilities: 
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel, snd_soc_skl

  # aplay -L
  default
  Playback/recording through the PulseAudio sound server
  null
  Discard all samples (playback) or generate zero samples (capture)
  pulse
  PulseAudio Sound Server
  sysdefault:CARD=PCH
  HDA Intel PCH, ALC3246 Analog
  Default Audio Device
  front:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  Front speakers
  surround21:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  2.1 Surround output to Front and Subwoofer speakers
  surround40:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  4.0 Surround output to Front and Rear speakers
  surround41:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  4.1 Surround output to Front, Rear and Subwoofer speakers
  surround50:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  5.0 Surround output to Front, Center and Rear speakers
  surround51:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  5.1 Surround output to Front, Center, Rear and Subwoofer speakers
  surround71:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  7.1 Surround output to Front, Center, Side, Rear and Woofer speakers
  hdmi:CARD=PCH,DEV=0
  HDA Intel PCH, HDMI 0
  HDMI Audio Output
  hdmi:CARD=PCH,DEV=1
  HDA Intel PCH, HDMI 1
  HDMI Audio Output
  hdmi:CARD=PCH,DEV=2
  HDA Intel PCH, HDMI 2
  HDMI Audio Output
  dmix:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  Direct sample mixing device
  dmix:CARD=PCH,DEV=3
  HDA Intel PCH, HDMI 0
  Direct sample mixing device
  dmix:CARD=PCH,DEV=7
  HDA Intel PCH, HDMI 1
  Direct sample mixing device
  dmix:CARD=PCH,DEV=8
  HDA Intel PCH, HDMI 2
  Direct sample mixing device
  dsnoop:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  Direct sample snooping device
  dsnoop:CARD=PCH,DEV=3
  HDA Intel PCH, HDMI 0
  Direct sample snooping device
  dsnoop:CARD=PCH,DEV=7
  HDA Intel PCH, HDMI 1
  Direct sample snooping device
  dsnoop:CARD=PCH,DEV=8
  HDA Intel PCH, HDMI 2
  Direct sample snooping device
  hw:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  Direct hardware device without any conversions
  hw:CARD=PCH,DEV=3
  HDA Intel PCH, HDMI 0
  Direct hardware device without any conversions
  hw:CARD=PCH,DEV=7
  HDA Intel PCH, HDMI 1
  Direct hardware device without any conversions
  hw:CARD=PCH,DEV=8
  HDA Intel PCH, HDMI 2
  Direct hardware device without any conversions
  plughw:CARD=PCH,DEV=0
  HDA Intel PCH, ALC3246 Analog
  Hardware device with all software conversions
  plughw:CARD=PCH,DEV=3
  HDA Intel PCH, HDMI 0
  Hardware device with all software conversions
  plughw:CARD=PCH,DEV=7
  HDA Intel PCH, HDMI 1
  Hardware device with all software conversions
  plughw:CARD=PCH,DEV=8
  HDA Intel PCH, HDMI 2
  Hardware device with all software conversions
  --- 
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', 
'/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 17.04
  HibernationDevice: RESUME=UUID=0bcd17dc-d971-4048-8c1f-d2bb48e8a157
  InstallationDate: Installed on 2017-08-18 (31 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Dell Inc. Inspiron 7460
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-35-generic.efi.signed 
root=/dev/mapper/ubu-root ro quiet splash zswap.enabled=1 vt.handoff=7
  

[Touch-packages] [Bug 1727825] Re: networkd DHCP immediately drops lease ( on igbx cards )

[Dimitri John Ledkov]

I thought we have the above mentioned patch in 17.10. but let me
double check that.

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

Title:
  networkd DHCP immediately drops lease ( on igbx cards )

Status in systemd package in Ubuntu:
  New

Bug description:
  On new install of 17.10 systemd-networkd loops with:

  Oct 23 16:45:24 san-jose systemd[1]: Starting Network Service...
  Oct 23 16:45:24 san-jose systemd-networkd[1217]: enp129s0f0: Gained IPv6LL
  Oct 23 16:45:24 san-jose systemd-networkd[1217]: Enumeration completed
  Oct 23 16:45:24 san-jose systemd[1]: Started Network Service.
  Oct 23 16:45:25 san-jose systemd-networkd[1217]: enp129s0f0: Gained carrier
  Oct 23 16:45:27 san-jose systemd-networkd[1217]: enp129s0f0: DHCPv4 address 
10.30.3.94/24 via 12
  Oct 23 16:45:27 san-jose systemd-networkd[1217]: Could not set hostname: The 
name org.freedesktop
  Oct 23 16:45:27 san-jose systemd-networkd[1217]: enp129s0f0: Lost carrier
  Oct 23 16:45:27 san-jose systemd-networkd[1217]: enp129s0f0: DHCP lease lost
  Oct 23 16:45:29 san-jose systemd-networkd[1217]: enp129s0f0: Gained carrier
  Oct 23 16:45:29 san-jose systemd-networkd[1217]: enp129s0f0: DHCPv4 address 
10.30.3.94/24 via 12
  Oct 23 16:45:29 san-jose systemd-networkd[1217]: Could not set hostname: The 
name org.freedesktop
  Oct 23 16:45:29 san-jose systemd-networkd[1217]: enp129s0f0: Configured
  Oct 23 16:45:30 san-jose systemd-networkd[1217]: enp129s0f0: Lost carrier
  Oct 23 16:45:30 san-jose systemd-networkd[1217]: enp129s0f0: DHCP lease lost

  that is the correct interface and address.

  If I manually run 'dhclient nep129s0f0' the lease sticks and
  'journalctl -fu systemd-networkd' shows:

  Oct 23 16:45:34 san-jose systemd-networkd[1217]: enp129s0f0: Gained carrier
  Oct 23 16:45:34 san-jose systemd-networkd[1217]: enp129s0f0: DHCPv4 address 
10.30.3.94/24 via 12
  Oct 23 16:45:34 san-jose systemd-networkd[1217]: Could not set hostname: The 
name org.freedesktop
  Oct 23 16:45:34 san-jose systemd-networkd[1217]: enp129s0f0: Configured

  I have verified this is reproducible on other systems with ixgbe based
  add in cards.

  igb (1G) cards seem to behave properly as do a random assortment of
  onboard devices and virtio devices inside VMs.

  Based on a pseudo random selection of my available gear it does seem
  hardware specific but this is our only flavor of 10G nic (and we have
  kindof a lot of them). Since isc-dhcp-client can bring up the
  interface on the commandline I don't *think* it's a driver issue.

  root@host:~# lsb_release -rd;uname -r ; dpkg -l nplan systemd
  Description: Ubuntu 17.10
  Release: 17.10
  4.13.0-16-generic
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name Version Architecture Description
  
+++-==-==-==-=
  ii nplan 0.30 amd64 YAML network configuration abstraction fo
  ii systemd 234-2ubuntu12 amd64 system and service manager

  my current workaround:

  root@host:~# cat /etc/rc.local
  #!/bin/sh
  dhclient enp129s0f0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727825/+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 774071] Re: Indicator-datetime-service renders 100% CPU usage

[Anders Hall]

Last work-around didn't stick. Don't think this bug or #1731939 is about
indicator-datetime-service. It seems to be evolution calendar that is
the problem. See comment below:

https://bugs.launchpad.net/ubuntu/+source/indicator-
datetime/+bug/1731939/comments/4

Will test 17.10 now.

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

Title:
  Indicator-datetime-service renders 100% CPU usage

Status in Indicator Date and Time:
  Fix Released
Status in Unity Foundations:
  Fix Released
Status in indicator-datetime package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: indicator-datetime

  On my laptop "indicator-datetime-service" occasionally make my CPU to
  use 100% of its resources. It does not happen every time I log in to
  Ubuntu, but when it happens, it stays hogging 100% of CPU until I kill
  the process. If it helps, I've noticed in "System Monitor" that there
  are two instances of "indicator-datetime-service" running, but only
  one of them is hogging recourses. So far I was unable to determine
  after what actions/events this bug pups up.

  I'm using Ubuntu 11.04 64-bit.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: indicator-datetime 0.2.3-0ubuntu3
  ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
  Uname: Linux 2.6.38-8-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  Date: Sat Apr 30 15:27:58 2011
  ExecutablePath: /usr/lib/indicator-datetime/indicator-datetime-service
  InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to natty on 2011-04-28 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-datetime/+bug/774071/+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 1731939] Re: Indicator-datetime-service renders 25% CPU usage and 100% RAM

[Anders Hall]

Last work-around didn't stick. Did some test and can reproduce the error
now easily in 17.04. Ubuntu reports it is the Indicator-datetime-service
that crashes when its the evolution calendar that is the problem. During
the system overload the problem can be fixed by killing all evolution
processes and sub-processes indirectly.

Evolution is overloading the Indicator-datetime-service somehow with
lots of (factory?) sub-processes.

Attached screenshot of the processes active during the error. Resolved
by killing the evolution processes in the screenshot.

Also, this problem started after enabling Empathy on boot. However,
after disabling Empathy completely at startup the problem persisted.

Will update to 17.10 (KVM bug fixed) and see if the error is unresolved.


** Attachment added: "htop screenshot sorted by mem usage"
   
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1731939/+attachment/5010707/+files/Screenshot%20from%202017-11-17%2022-45-57.png

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

Title:
   Indicator-datetime-service renders 25% CPU usage and 100% RAM

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  Same as Bug #774071 but with 100% RAM instead. Collected info while
  the Indicator-datetime-service was acting up. I.e., writing this with
  a few hundred megabytes RAM available..

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: indicator-datetime 15.10+17.04.20170322-0ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-38.42-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Mon Nov 13 15:41:39 2017
  ExecutablePath: 
/usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service
  InstallationDate: Installed on 2015-07-18 (848 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to zesty on 2017-06-13 (153 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1731939/+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 1727825] Re: networkd DHCP immediately drops lease ( on igbx cards )

[Jon Proulx]

this is actually upstream bug
https://github.com/systemd/systemd/issues/6593 related to setting MTU.

If this isn't patched before 18.04 release please, please, please revert
to ifupdown as default

** Bug watch added: github.com/systemd/systemd/issues #6593
   https://github.com/systemd/systemd/issues/6593

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

Title:
  networkd DHCP immediately drops lease ( on igbx cards )

Status in systemd package in Ubuntu:
  New

Bug description:
  On new install of 17.10 systemd-networkd loops with:

  Oct 23 16:45:24 san-jose systemd[1]: Starting Network Service...
  Oct 23 16:45:24 san-jose systemd-networkd[1217]: enp129s0f0: Gained IPv6LL
  Oct 23 16:45:24 san-jose systemd-networkd[1217]: Enumeration completed
  Oct 23 16:45:24 san-jose systemd[1]: Started Network Service.
  Oct 23 16:45:25 san-jose systemd-networkd[1217]: enp129s0f0: Gained carrier
  Oct 23 16:45:27 san-jose systemd-networkd[1217]: enp129s0f0: DHCPv4 address 
10.30.3.94/24 via 12
  Oct 23 16:45:27 san-jose systemd-networkd[1217]: Could not set hostname: The 
name org.freedesktop
  Oct 23 16:45:27 san-jose systemd-networkd[1217]: enp129s0f0: Lost carrier
  Oct 23 16:45:27 san-jose systemd-networkd[1217]: enp129s0f0: DHCP lease lost
  Oct 23 16:45:29 san-jose systemd-networkd[1217]: enp129s0f0: Gained carrier
  Oct 23 16:45:29 san-jose systemd-networkd[1217]: enp129s0f0: DHCPv4 address 
10.30.3.94/24 via 12
  Oct 23 16:45:29 san-jose systemd-networkd[1217]: Could not set hostname: The 
name org.freedesktop
  Oct 23 16:45:29 san-jose systemd-networkd[1217]: enp129s0f0: Configured
  Oct 23 16:45:30 san-jose systemd-networkd[1217]: enp129s0f0: Lost carrier
  Oct 23 16:45:30 san-jose systemd-networkd[1217]: enp129s0f0: DHCP lease lost

  that is the correct interface and address.

  If I manually run 'dhclient nep129s0f0' the lease sticks and
  'journalctl -fu systemd-networkd' shows:

  Oct 23 16:45:34 san-jose systemd-networkd[1217]: enp129s0f0: Gained carrier
  Oct 23 16:45:34 san-jose systemd-networkd[1217]: enp129s0f0: DHCPv4 address 
10.30.3.94/24 via 12
  Oct 23 16:45:34 san-jose systemd-networkd[1217]: Could not set hostname: The 
name org.freedesktop
  Oct 23 16:45:34 san-jose systemd-networkd[1217]: enp129s0f0: Configured

  I have verified this is reproducible on other systems with ixgbe based
  add in cards.

  igb (1G) cards seem to behave properly as do a random assortment of
  onboard devices and virtio devices inside VMs.

  Based on a pseudo random selection of my available gear it does seem
  hardware specific but this is our only flavor of 10G nic (and we have
  kindof a lot of them). Since isc-dhcp-client can bring up the
  interface on the commandline I don't *think* it's a driver issue.

  root@host:~# lsb_release -rd;uname -r ; dpkg -l nplan systemd
  Description: Ubuntu 17.10
  Release: 17.10
  4.13.0-16-generic
  Desired=Unknown/Install/Remove/Purge/Hold
  | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
  |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
  ||/ Name Version Architecture Description
  
+++-==-==-==-=
  ii nplan 0.30 amd64 YAML network configuration abstraction fo
  ii systemd 234-2ubuntu12 amd64 system and service manager

  my current workaround:

  root@host:~# cat /etc/rc.local
  #!/bin/sh
  dhclient enp129s0f0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727825/+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 1186662] Re: isc-dhcp-server fails to renew lease file

[Gaétan QUENTIN]

ubuntu 17.10 32 bits: the same
Nov 17 22:02:45 nas dhclient[736]: can't create 
/var/lib/dhcp/dhclient.enp3s0.leases: Read-only file system

drwxr-xr-x 1 root root   44 déc.  13  2016 .
drwxr-xr-x 1 root root  738 juil. 16 18:11 ..
-rw-r--r-- 1 root root 1094 nov.  17 22:02 dhclient.enp3s0.leases

and there is no dhcp user account:

root@nas:/etc# grep -i dhcp /etc/passwd /etc/group
root@nas:/etc#

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

Title:
  isc-dhcp-server fails to renew lease file

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Trusty:
  Triaged

Bug description:
  After raring upgrade, the dhcp server fails to renew lease file when
  it tries to (about every hour).

  The syslog says:
  dhcpd: Can't create new lease file: Permission denied

  It looks like a permission problem, because

  # chown -R dhcpd:dhcpd /var/lib/dhcp

  the above command temporarily solves the issue, until dhcpd is
  restarted: at that time, the ownership of the directory and the lease
  file is set back to root:root.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1186662/+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 1717991] Re: file returns "name use count (30) exceeded"

[Eli Collins]

Testing on various systems, I'm seeing this on Debian Stretch using file
version 1:5.30-1+deb9u1.

But not on older ubuntu version like file 1:5.25-2ubuntu1.

(Both tested using above test.jpg)

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

Title:
  file returns "name use count (30) exceeded"

Status in file package in Ubuntu:
  Confirmed
Status in file package in Debian:
  New

Bug description:
  In Ubuntu 17.04 there seems to be a problem with "file":

  $ file test.jpg 
  test.jpg: ERROR: JPEG image data, JFIF standard 1.01, resolution (DPI), 
density 240x240, segment length 16, Exif Standard: [TIFF image data, 
big-endian, direntries=8, description=Picture saved with settings embedded., 
orientation=upper-left, xresolution=148, yresolution=156, resolutionunit=2, 
software=Adobe Photoshop Lightroom 6.1.1 (Windows), datetime=2017:08:17 
11:16:47] name use count (30) exceeded

  This problem was reported in Fedora a couple of years ago:
  https://bugzilla.redhat.com/show_bug.cgi?id=1201630

  I found out about the problem when the Astrometry program suddenly
  stopped working on jpegs that it was previously able to process. I
  cannot say how "file" is supposed to normally output the data. I only
  found out about this when the program suddenly broke without any
  obvious reason after the upgrade from Ubuntu 16.04 to 17.04. Since
  there is another case reported for Fedora I tend to believe that the
  problem is indeed caused by "file".

  The required data:

  $ lsb_release -rd
  Description:  Ubuntu 17.04
  Release:  17.04

  
  $ apt-cache policy file
  file:
Installed: 1:5.29-3ubuntu0.1
Candidate: 1:5.29-3ubuntu0.1
Version table:
   *** 1:5.29-3ubuntu0.1 500
  500 http://fi.archive.ubuntu.com/ubuntu zesty-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu zesty-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:5.29-3 500
  500 http://fi.archive.ubuntu.com/ubuntu zesty/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: file 1:5.29-3ubuntu0.1
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  NonfreeKernelModules: sep4_0 socperf2_0 pax
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Mon Sep 18 20:36:35 2017
  InstallationDate: Installed on 2016-01-18 (609 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: file
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file/+bug/1717991/+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 1717991] Re: file returns "name use count (30) exceeded"

[Launchpad Bug Tracker]

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

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

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

Title:
  file returns "name use count (30) exceeded"

Status in file package in Ubuntu:
  Confirmed
Status in file package in Debian:
  New

Bug description:
  In Ubuntu 17.04 there seems to be a problem with "file":

  $ file test.jpg 
  test.jpg: ERROR: JPEG image data, JFIF standard 1.01, resolution (DPI), 
density 240x240, segment length 16, Exif Standard: [TIFF image data, 
big-endian, direntries=8, description=Picture saved with settings embedded., 
orientation=upper-left, xresolution=148, yresolution=156, resolutionunit=2, 
software=Adobe Photoshop Lightroom 6.1.1 (Windows), datetime=2017:08:17 
11:16:47] name use count (30) exceeded

  This problem was reported in Fedora a couple of years ago:
  https://bugzilla.redhat.com/show_bug.cgi?id=1201630

  I found out about the problem when the Astrometry program suddenly
  stopped working on jpegs that it was previously able to process. I
  cannot say how "file" is supposed to normally output the data. I only
  found out about this when the program suddenly broke without any
  obvious reason after the upgrade from Ubuntu 16.04 to 17.04. Since
  there is another case reported for Fedora I tend to believe that the
  problem is indeed caused by "file".

  The required data:

  $ lsb_release -rd
  Description:  Ubuntu 17.04
  Release:  17.04

  
  $ apt-cache policy file
  file:
Installed: 1:5.29-3ubuntu0.1
Candidate: 1:5.29-3ubuntu0.1
Version table:
   *** 1:5.29-3ubuntu0.1 500
  500 http://fi.archive.ubuntu.com/ubuntu zesty-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu zesty-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:5.29-3 500
  500 http://fi.archive.ubuntu.com/ubuntu zesty/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: file 1:5.29-3ubuntu0.1
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  NonfreeKernelModules: sep4_0 socperf2_0 pax
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Mon Sep 18 20:36:35 2017
  InstallationDate: Installed on 2016-01-18 (609 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: file
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file/+bug/1717991/+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 1717991] Re: file returns "name use count (30) exceeded"

[Eli Collins]

** Also affects: file (Debian)
   Importance: Undecided
   Status: New

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

Title:
  file returns "name use count (30) exceeded"

Status in file package in Ubuntu:
  Confirmed
Status in file package in Debian:
  New

Bug description:
  In Ubuntu 17.04 there seems to be a problem with "file":

  $ file test.jpg 
  test.jpg: ERROR: JPEG image data, JFIF standard 1.01, resolution (DPI), 
density 240x240, segment length 16, Exif Standard: [TIFF image data, 
big-endian, direntries=8, description=Picture saved with settings embedded., 
orientation=upper-left, xresolution=148, yresolution=156, resolutionunit=2, 
software=Adobe Photoshop Lightroom 6.1.1 (Windows), datetime=2017:08:17 
11:16:47] name use count (30) exceeded

  This problem was reported in Fedora a couple of years ago:
  https://bugzilla.redhat.com/show_bug.cgi?id=1201630

  I found out about the problem when the Astrometry program suddenly
  stopped working on jpegs that it was previously able to process. I
  cannot say how "file" is supposed to normally output the data. I only
  found out about this when the program suddenly broke without any
  obvious reason after the upgrade from Ubuntu 16.04 to 17.04. Since
  there is another case reported for Fedora I tend to believe that the
  problem is indeed caused by "file".

  The required data:

  $ lsb_release -rd
  Description:  Ubuntu 17.04
  Release:  17.04

  
  $ apt-cache policy file
  file:
Installed: 1:5.29-3ubuntu0.1
Candidate: 1:5.29-3ubuntu0.1
Version table:
   *** 1:5.29-3ubuntu0.1 500
  500 http://fi.archive.ubuntu.com/ubuntu zesty-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu zesty-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:5.29-3 500
  500 http://fi.archive.ubuntu.com/ubuntu zesty/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: file 1:5.29-3ubuntu0.1
  ProcVersionSignature: Ubuntu 4.10.0-33.37-generic 4.10.17
  Uname: Linux 4.10.0-33-generic x86_64
  NonfreeKernelModules: sep4_0 socperf2_0 pax
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Mon Sep 18 20:36:35 2017
  InstallationDate: Installed on 2016-01-18 (609 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: file
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/file/+bug/1717991/+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 1731283] Re: network-manager 1.8.4-1ubuntu3 ADT test failure with linux 4.14.0-6.8

[Seth Forshee]

Seems that s390x ADT does now run in VMs, which explains the change.

Since we don't have wireless support in our s390x kernels, these
failures are expected. Seems the tests will need to be changed to skip
these tests or make them expected failures.

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

Title:
  network-manager 1.8.4-1ubuntu3 ADT test failure with linux 4.14.0-6.8

Status in network-manager package in Ubuntu:
  New

Bug description:
  Testing failed on:
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/s390x/n/network-manager/20171107_135937_02323@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1731283/+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 1713004] Re: Temporary files left under /var/tmp by mkinitramfs

[Brian Murray]

This was fixed in initramfs-tools version 0.123 which is available in
Zesty and later releases.  The fix should be SRU'ed to both Ubuntu 14.04
and Ubuntu 16.04 which are affected.  Here's a link to the commit which
fixed this:

https://anonscm.debian.org/cgit/kernel/initramfs-
tools.git/commit/?id=ac6d31fc2c707b72ff8af9944c9b4f8af303a6a3

** Also affects: initramfs-tools (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: initramfs-tools (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Changed in: initramfs-tools (Ubuntu)
   Status: Confirmed => Fix Released

** Changed in: initramfs-tools (Ubuntu Trusty)
   Importance: Undecided => High

** Changed in: initramfs-tools (Ubuntu Xenial)
   Importance: Undecided => High

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

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

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

Title:
  Temporary files left under /var/tmp by mkinitramfs

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Trusty:
  Triaged
Status in initramfs-tools source package in Xenial:
  Triaged
Status in initramfs-tools package in Debian:
  Fix Released

Bug description:
  I recently ran out of disk space on my / mount.  While looking for
  what consumed the disk I noticed a large number (130) of directories
  with names / paths beginning /var/tmp/mkinitramfs.  These directories
  seem to be either ~103 MB or ~927 MB in size.  Many of these files are
  months old, some are almost a year.

  Having had a quick look about for an explanation as to why these files
  are here and found Debian Bug #814345.  That explains that temporary
  files are left behind by the initramfs-tools if something fails in the
  process.  If this is the cause of my files then updating the Ubuntu
  package to version 0.123 should resolve this issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu8.8
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Aug 25 09:40:41 2017
  InstallationDate: Installed on 2015-03-12 (896 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  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/1713004/+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 1732970] [NEW] Remove cordova-ubuntu-3.4, qtfeedback-opensource-src, qtsystems-opensource-src from archive

[Dmitry Shachnev]

Public bug reported:

cordova-ubuntu is dead upstream (https://github.com/apache/cordova-
ubuntu had last commit in Oct 2016), Ubuntu packaging has no active
maintainer and has not been updated since 2014.

I have talked to Alberto Mardegan on IRC, he confirmed that it should be safe 
to remove it:
https://irclogs.ubuntu.com/2017/11/17/%23ubuntu-devel.html#t18:43

qtfeedback-opensource-src and qtsystems-opensource-src are libraries
which have never become part of official Qt releases, and their only
user in Ubuntu was cordova-ubuntu-3.4.

** Affects: cordova-ubuntu-3.4 (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: qtfeedback-opensource-src (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: qtsystems-opensource-src (Ubuntu)
 Importance: Undecided
 Status: New

** Also affects: qtfeedback-opensource-src (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: cordova-ubuntu-3.4 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Remove cordova-ubuntu-3.4, qtfeedback-opensource-src, qtsystems-
  opensource-src from archive

Status in cordova-ubuntu-3.4 package in Ubuntu:
  New
Status in qtfeedback-opensource-src package in Ubuntu:
  New
Status in qtsystems-opensource-src package in Ubuntu:
  New

Bug description:
  cordova-ubuntu is dead upstream (https://github.com/apache/cordova-
  ubuntu had last commit in Oct 2016), Ubuntu packaging has no active
  maintainer and has not been updated since 2014.

  I have talked to Alberto Mardegan on IRC, he confirmed that it should be safe 
to remove it:
  https://irclogs.ubuntu.com/2017/11/17/%23ubuntu-devel.html#t18:43

  qtfeedback-opensource-src and qtsystems-opensource-src are libraries
  which have never become part of official Qt releases, and their only
  user in Ubuntu was cordova-ubuntu-3.4.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cordova-ubuntu-3.4/+bug/1732970/+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 1732518] Re: Please re-enable container support in apport

[Brian Murray]

I'm good with these changes.

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

Title:
  Please re-enable container support in apport

Status in apport package in Ubuntu:
  Triaged
Status in apport source package in Xenial:
  Triaged
Status in apport source package in Zesty:
  Triaged
Status in apport source package in Artful:
  Triaged
Status in apport source package in Bionic:
  Triaged

Bug description:
  The latest security update for apport disabled container crash
  forwarding, this is a feature which users do rely on in production and
  while it may have been appropriate to turn it off to put a security
  update out, this needs to be re-enabled ASAP.

  I provided a patch which fixed the security issue before the security
  issue was publicly disclosed so pushing an SRU to all Ubuntu releases
  re-enabling this code should be pretty trivial.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1732518/+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 1722564] Re: apport question will not accept multi-character responses

[Brian Murray]

The artful upload was superseded by a security upload. I'll get this
SRU'ed shortly.

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

Title:
  apport question will not accept multi-character responses

Status in Apport:
  Confirmed
Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  New
Status in apport source package in Artful:
  Fix Committed

Bug description:
  === Begin SRU Template ===
  [Impact]
  Packages which provide apport integration with more than 9 options in a 
choice will not be able to select options numbered >= 10 on the commandline 
using 'ubuntu-bug '

  
  [Test Case]
  Overview:
   1. Update to proposed versions of cloud-init v. 17.1 and apport v. 
   2. Run 'ubuntu-bug cloud-init' attempt to report a bug on a cloud choice 
greater than 9
   3. View report and make sure the proper cloud is reported


  Script:
  if [ ! -f './lxc-proposed-snapshot' ]; then
wget 
https://raw.githubusercontent.com/cloud-init/ubuntu-sru/master/bin/lxc-proposed-snapshot;
chmod 755 lxc-proposed-snapshot;
  fi

  for release in xenial artful; do
  ref=$release-proposed;
  echo "$release START --";
  lxc-proposed-snapshot --proposed --publish $release $ref;
  lxc init $ref test-$release;
  lxc start test-$release;
  lxc exec test-$release -- apt install apport;
  lxc exec test-$release -- dpkg-query --show apport;
  lxc exec test-$release -- ubuntu-bug cloud-init;
  done

  [Regression Potential]
  Minimal. This bug only affects packages with >9 bug filing options for a 
given choice. Worst case, is bugs filed would incorrectly represent option 1 of 
a selection instead of option 1X.

  
  === End SRU Template ===

  === original description ===
  the newly added cloud-init apport support shows a list of cloud providers and 
asks the user to select one.  There are currently 18 options.  For any option > 
10, apport will just take the '1' that is typed as the answer.

  It should obviously wait for more than one character or a carriage
  return.

  *** Please select the cloud vendor or environment in which this
  instance is running

  Choices:
    1: Amazon - Ec2
    2: AliYun
    3: AltCloud
    4: Azure
    5: Bigstep
    6: CloudSigma
    7: CloudStack
    8: DigitalOcean
    9: GCE - Google Compute Engine
    10: MAAS
    11: NoCloud
    12: OpenNebula
    13: OpenStack
    14: OVF
    15: Scaleway
    16: SmartOS
    17: VMware
    18: Other
    C: Cancel
  Please choose (1/2/3/4/5/6/7/8/9/10/11/12/13/14/15/16/17/18/C): 1

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: apport 2.20.7-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  Date: Tue Oct 10 15:21:48 2017
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1722564/+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 941826] Re: dlopen(libGL.so) resolves to mesa rather than nvidia

[Tempuser]

Also there seems to be no interest in fixing this, for the record:

Problem and solution are still present/working in Ubuntu 17.10. and
Nvidia driver 384.

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

Title:
  dlopen(libGL.so) resolves to mesa rather than nvidia

Status in NVIDIA Drivers Ubuntu:
  New
Status in mesa package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  Confirmed
Status in nvidia-graphics-drivers-340 package in Ubuntu:
  Confirmed
Status in pyqt5 package in Ubuntu:
  Invalid
Status in python-qt4 package in Ubuntu:
  Invalid

Bug description:
  I'm having trouble with a combination of NVIDIA + Python + Qt +
  Opengl.

  I tried using a QGraphicsView on a QGLWidget. I'm getting a white window and 
errors like this these:
  QGLShader: could not create shader
  Vertex shader for simpleShaderProg (MainVertexShader 
) failed to compile

  This is an example application triggering the problem:
  http://pastebin.com/R0aa8ejs

  The 'same' program works flawlessly when using C++/Qt. I'm seeing the exact 
behavior when using PySide instead of PyQt4 by the way. I'm also seeing this 
error when trying the original demo application from python-qt4-doc. Also, 
calling
  QtGui.QApplication.setGraphicsSystem("opengl")
  produces the same errors.

  I'm experiencing this problems on 11.10 and 12.04 with the ubuntu-
  provided nvidia drivers (where 12.04 includes the most recent driver
  for now). After installing the driver using the original NVidia
  installer, the applications work as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/941826/+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 1731283] Re: network-manager 1.8.4-1ubuntu3 ADT test failure with linux 4.14.0-6.8

[Seth Forshee]

Tests were previously getting skipped for s390, due to "Restrictions:
... isolation-machine" in the test control file. Possibly some sort of
infrastructure problem detecting that the tests are running in a
container.

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

Title:
  network-manager 1.8.4-1ubuntu3 ADT test failure with linux 4.14.0-6.8

Status in network-manager package in Ubuntu:
  New

Bug description:
  Testing failed on:
  s390x: 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic-canonical-kernel-team-bootstrap/bionic/s390x/n/network-manager/20171107_135937_02323@/log.gz

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1731283/+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 1718435] Re: package apport-gtk 2.20.1-0ubuntu2.10 failed to install/upgrade: problemas de dependencias - se deja sin configurar

[Launchpad Bug Tracker]

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

Title:
  package apport-gtk 2.20.1-0ubuntu2.10 failed to install/upgrade:
  problemas de dependencias - se deja sin configurar

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  ,,

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport-gtk 2.20.1-0ubuntu2.10
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CrashReports:
   640:0:116:106174:2017-09-20 10:57:31.266966581 -0300:2017-09-20 
10:57:32.266966581 -0300:/var/crash/apport.0.crash
   644:0:116:0:2017-09-20 10:57:34.246948771 -0300:2017-09-20 
10:57:34.246948771 -0300:/var/crash/apport.0.upload
   600:109:116:0:2017-09-20 10:57:36.726927044 -0300:2017-09-20 
10:57:36.726927044 -0300:/var/crash/apport.0.uploaded
   600:0:116:89250:2017-09-20 10:56:25.335798501 -0300:2017-09-20 
10:57:45.018858231 -0300:/var/crash/apport-gtk.0.crash
  Date: Wed Sep 20 10:56:26 2017
  ErrorMessage: problemas de dependencias - se deja sin configurar
  InstallationDate: Installed on 2015-08-11 (770 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: apport
  Title: package apport-gtk 2.20.1-0ubuntu2.10 failed to install/upgrade: 
problemas de dependencias - se deja sin configurar
  UpgradeStatus: Upgraded to xenial on 2016-08-08 (408 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1718435/+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 1729357] Re: unprivileged user can drop supplementary groups

[Craig Furman]

Thanks for replying Eric, but I'm having trouble reproducing what you've
posted. I can't write the gid map until I've written deny to
/prod/$pid/setgroups, not the other way around. There might be some
nuance I've missed.

Also, newgidmap will allow a user to map their own GID to 0 in the user
namespace, even when there is no entry for that user in /etc/subgid.

What if newgidmap wrote "deny" to /proc/$pid/setgroups unless the user
is whitelisted in some config file, probably separate from /etc/subgid,
as Stéphane suggested?

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

Title:
  unprivileged user can drop supplementary groups

Status in shadow package in Ubuntu:
  Confirmed

Bug description:
  Distribution: Ubuntu 16.04.3 LTS
  Kernel: 4.4.0-97-generic
  uidmap package version: 1:4.2-3.1ubuntu5.3

  The newgidmap setuid executable allows any user to write a single
  mapping line to the gid_map of a process whose identity is the same as
  the calling process, as long as that mapping line maps the process's
  own GID outside of the user namespace to GID 0 inside the user
  namespace.

  Newgidmap will write the mapping regardless of the content of
  /proc/$process_being_mapped/setgroups, which will initially contain
  the string "allow". After this mapping is performed, and also after
  the process' uid_map is written with newuidmap, the process in the
  user namespace will be able to use the setgroups system call to drop
  supplementary groups.

  This is possible even if there is no entry for the user in
  /etc/subgid, because no subordinate GIDs are actually being used.

  This allows any user to circumvent the use of supplementary groups as
  blacklists, e.g. for some file owned by root:blacklist with permission
  bits 0604 (octal). Normally any process whose identity included the
  group "blacklist" in its supplementary groups would not be able to
  read that file. By performing this exploit using newgidmap, they can
  drop all supplementary groups and read that file.

  If newgidmap was not available, unprivileged users would not be able
  to write a process's gid_map until writing "deny" to
  /proc/$pid/setgroups. A fix for this might be for newgidmap to check
  the content of /proc/$process_being_mapped/setgroups is "deny", but we
  have not tried to patch this ourselves.

  An example using 2 login shells for a user named "someone" on Ubuntu
  Xenial, with the uidmap package installed:

  Shell 1

  someone@ubuntu-xenial:~$ id
  uid=1001(someone) gid=1001(someone) groups=1001(someone),1002(restricted)

  someone@ubuntu-xenial:~$ ls -al /tmp/should_restrict
  -rwr-- 1 root restricted 8 Nov  1 12:23 /tmp/should_restrict

  someone@ubuntu-xenial:~$ cat /tmp/should_restrict
  cat: /tmp/should_restrict: Permission denied

  someone@ubuntu-xenial:~$ unshare -U --setgroups allow #
  /proc/self/setgroups already contains 'allow', but let's be explicit

  nobody@ubuntu-xenial:~$ echo $$
  1878

  Shell 2

  someone@ubuntu-xenial:~$ cat /etc/subuid
  lxd:10:65536
  root:10:65536
  ubuntu:165536:65536

  someone@ubuntu-xenial:~$ cat /etc/subgid
  lxd:10:65536
  root:10:65536
  ubuntu:165536:65536

  # There are no entries in /etc/sub{u,g}id for someone, but this
  doesn't matter that much as subordinate IDs are not being requested.

  someone@ubuntu-xenial:~$ newuidmap 1878 0 1001 1

  someone@ubuntu-xenial:~$ newgidmap 1878 0 1001 1

  Back to shell 1

  nobody@ubuntu-xenial:~$ id
  uid=0(root) gid=0(root) groups=0(root),65534(nogroup)

  # The presence of the "nogroup" supplementary group indicates that
  some unmapped GIDs are present as supplementary GIDs. The kernel knows
  that this process still has "restricted" in its supplementary groups,
  so it can't read the restricted file yet.

  nobody@ubuntu-xenial:~$ cat /tmp/should_restrict
  cat: /tmp/should_restrict: Permission denied

  # The process has gained CAP_SETGID in its user namespace by becoming
  UID 0. /proc/$pid/setgroups contains "allow", so it can call
  setgroups(2). By su-ing to root (itself, in the user namespace), it
  can drop the supplementary groups. It can't read /root/.bashrc as that
  file is owned by UID 0 in the initial user namespace, which creates
  some distracting error output but doesn't matter in this case.

  nobody@ubuntu-xenial:~$ su root
  su: Authentication failure
  (Ignored)
  bash: /root/.bashrc: Permission denied

  # Supplementary groups have been dropped

  root@ubuntu-xenial:~# id
  uid=0(root) gid=0(root) groups=0(root)

  # It can read the restricted file

  root@ubuntu-xenial:~# cat /tmp/should_restrict
  content

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

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

[Touch-packages] [Bug 1732028] Re: transient boot fail with overlayroot

[Scott Moser]

Another fail log at
 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/o/open-iscsi/20171114_192057_17bf1@/log.gz

Basically if you look at bionic failures
 http://autopkgtest.ubuntu.com/packages/o/open-iscsi/bionic/amd64
if it took 11 hours and failed, this is why.


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

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

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

Title:
  transient boot fail with overlayroot

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  This issue keeps cropping up.  It shows itself in open-iscsi autopkg tests.
  I think it might just be "really slow system".  It seems the timeout is only
   1 minute 30 seconds for the disk to appear, and in a happy run you
  might see something very close:

  [K[   [0;31m*[0;1;31m*[0m[0;31m*[0m] A start job is running for 
dev-disk…-UEFI.device (1min 29s / 1min 32s)
  [K[  [0;31m*[0;1;31m*[0m[0;31m* [0m] A start job is running for 
dev-disk…-UEFI.device (1min 30s / 1min 32s)
  [K[[0;32m  OK  [0m] Found device VIRTUAL-DISK UEFI.
   Mounting /boot/efi...

  ---
  There is information on the open-iscsi tests at [1].
[1] 
https://git.launchpad.net/~usd-import-team/ubuntu/+source/open-iscsi/tree/debian/tests/README-boot-test.md

  The tests set up an iscsi target and boot a kvm guest off that read-
  only root with overlayroot.

  # get open-iscsi source
  $ apt-get source open-iscsi
  $ cd open-iscsi-2.0.874/

  $ sudo apt-get install -qy simplestreams tgt qemu-system-x86 \
   cloud-image-utils distro-info
  $ cd open-iscsi-2.0.874/

  ## we're now mostly following debian/tests/README-boot-test.md
  # download the image and get kernel/initrd
  $ PATH=$PWD/debian/tests:$PATH
  $ get-image bionic.d bionic 
  $ sudo `which patch-image` \
  --kernel=bionic.d/kernel --initrd=bionic.d/initrd bionic.d/disk.img

  $ tgt-boot-test -v bionic.d/disk.img bionic.d/kernel bionic.d/initrd
  

  Success is being able to log in with 'ubuntu' and 'passw0rd'.
  Failure as seen in the log is dropping into an emergency shell.

  Once inside (this was successful) you'll see a mostly sane system.
  Some things to note:
  a.) tgt-boot-test boots without kvm enabled.  This is because using
   kvm with qemu in nested virt would cause system lockups. Its slower
  but more reliable to go wtihout.
  b.) under bug 1723183 I  made overlayroot comment out the root filesystem
  from the rendered /etc/fstab.  That was because systemd got confused and
  assumed that /media/root-ro had to be on top of /.
  c.) you can enable or disable kvm by setting _USE_KVM=0 or _USE_KVM=1
 in your environment.

  $ grep -v "^# " /etc/fstab
  #
  #
  #LABEL=cloudimg-rootfs /media/root-ro/ ext4 ro,defaults,noauto 0 0
  /media/root-ro/ / overlay 
lowerdir=/media/root-ro/,upperdir=/media/root-rw/overl
  ay/,workdir=/media/root-rw/overlay-workdir/_ 0 0
  LABEL=UEFI /boot/efi vfat defaults 0 0 # overlayroot:fs-unsupported

  $ sudo blkid
  /dev/sda1: LABEL="cloudimg-rootfs" 
UUID="7b1980bd-9102-4356-8df0-ec7a0c062411" TYPE="ext4" 
PARTUUID="c0b5ace0-4703-4667-babb-3d38137cab88"
  /dev/sda15: LABEL="UEFI" UUID="B177-3CC9" TYPE="vfat" 
PARTUUID="0ab0b9fd-2c28-4724-857a-1559f0cf76ea"
  /dev/sda14: PARTUUID="221662d6-cab0-4290-ba1c-e72acf2bf193"

  $ cat /run/systemd/generator/local-fs.target.requires/boot-efi.mount
  # Automatically generated by systemd-fstab-generator

  [Unit]
  SourcePath=/etc/fstab
  Documentation=man:fstab(5) man:systemd-fstab-generator(8)
  Before=local-fs.target

  [Mount]
  Where=/boot/efi
  What=/dev/disk/by-label/UEFI
  Type=vfat

  Related bugs:
   * bug 1680197: Zesty deployments failing sporadically
   * bug 1723183: transient systemd ordering issue when using overlayroot

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 234-2ubuntu12
  ProcVersionSignature: User Name 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu4
  Architecture: amd64
  Date: Mon Nov 13 21:06:36 2017
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
  ProcEnviron:
   TERM=vt220
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: nomodeset iscsi_initiator=maas-enlist 
iscsi_target_name=tgt-boot-test-7xuhwl iscsi_target_ip=10.0.12.2 
iscsi_target_port=3260 iscsi_initiator=maas-enlist ip=maas-enlist:BOOTIF ro 
net.ifnames=0 BOOTIF_DEFAULT=eth0 
root=/dev/disk/by-path/ip-10.0.12.2:3260-iscsi-tgt-boot-test-7xuhwl-lun-1-part1 
overlayroot=tmpfs console=ttyS0 ds=nocloud-net;seedfrom=http://10.0.12.2:32600/
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  

[Touch-packages] [Bug 1732518] Re: Please re-enable container support in apport

[Tyler Hicks]

@Brian did you have any thoughts on the debdiff?

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

Title:
  Please re-enable container support in apport

Status in apport package in Ubuntu:
  Triaged
Status in apport source package in Xenial:
  Triaged
Status in apport source package in Zesty:
  Triaged
Status in apport source package in Artful:
  Triaged
Status in apport source package in Bionic:
  Triaged

Bug description:
  The latest security update for apport disabled container crash
  forwarding, this is a feature which users do rely on in production and
  while it may have been appropriate to turn it off to put a security
  update out, this needs to be re-enabled ASAP.

  I provided a patch which fixed the security issue before the security
  issue was publicly disclosed so pushing an SRU to all Ubuntu releases
  re-enabling this code should be pretty trivial.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1732518/+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 1731937] Re: [18.04 FEAT] upgrade util-linux >=2.32

[Dimitri John Ledkov]

** Information type changed from Private to Public

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

Title:
  [18.04 FEAT] upgrade util-linux >=2.32

Status in Ubuntu on IBM z Systems:
  In Progress
Status in util-linux package in Ubuntu:
  In Progress

Bug description:
  Upgrade to newest version including lsmem/chmen; add memory zone
  awareness .

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1731937/+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 1648183] Re: Crackling and popping sound when using headphones

[Théo Besnard]

I fixed it myself. Cron wasn't running on start. I fixed it this way :
# update-rc.d cron defaults

Thanks again to @robertjjoynt

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

Title:
  Crackling and popping sound when using headphones

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in alsa-driver package in Arch Linux:
  New

Bug description:
  Laptop is  HP Pavilion - 15-au118tx. The laptop has B and O play and
  the output from speakers are just fine, when using headphones there is
  some kind of crackling and popping sound in both ears but prominently
  in the left ear.

  The issue happens only when the sound is played, if i reduce the PCM
  way low using alsamixer, the effect is minimized but the volume is
  also reduced. Increasing the volume in the panel increases the PCM as
  well.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  antony 1719 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Dec  7 23:30:05 2016
  InstallationDate: Installed on 2016-11-20 (17 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [HP Pavilion Notebook, Realtek ALC295, Black Headphone Out, Left] 
Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/19/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.14
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8216
  dmi.board.vendor: HP
  dmi.board.version: 83.13
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.14:bd07/19/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8216:rvr83.13:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-12-07T23:12:52.939689

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1648183/+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 1623666] Re: iOS device contents not displayed in Ubuntu

[J. McDonald]

I am also using the martin-salbaba/ppa+libimobiledevice ppa

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

Title:
  iOS device contents not displayed in Ubuntu

Status in Libimobiledevice:
  Fix Released
Status in gnutls28 package in Ubuntu:
  Confirmed
Status in libimobiledevice package in Ubuntu:
  Confirmed

Bug description:
  Plug in iOS device, and it doesn't show the documents on it.

  Please package the recent fix in libimobiledevice*:

  Vauge discussion that mentions using the latest git HEAD*:
  https://github.com/libimobiledevice/libimobiledevice/issues/327

  *This discussion is quite vague. One comment points out "iOS 10
  devices don't allow SSLv3 anymore but require at least TLSv1", but not
  how or if that has been fixed in libimobiledevice git HEAD.

  This ppa packages the git version and may resolve the issue:
  
https://launchpad.net/~martin-salbaba/+archive/ubuntu/ppa+libimobiledevice/+packages

  There are several other upstream reports related to this problem.

  Partial success patch (idevicepair only) trying to keep GnuTLS:
  https://github.com/libimobiledevice/libimobiledevice/issues/413

  Failure with GnuTLS, Success with OpenSSL:
  https://gitlab.com/gnutls/gnutls/issues/145

  Ubuntu packages libimobiledevice with "--disable-openssl":
  https://github.com/libimobiledevice/ifuse/issues/32

  Duplicate bug 1638177 suggests to repackage libimobiledevice using
  OpenSSL to avoid this problem, as per comment 27 below.

To manage notifications about this bug go to:
https://bugs.launchpad.net/libimobiledevice/+bug/1623666/+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 1623666] Re: iOS device contents not displayed in Ubuntu

[J. McDonald]

More specifically, I was able to successfully pair the phone.  It took a
couple of iterations (entering password on phone, etc.).  The problem
seemed to be lockdownd when trying to mount:

$ ifuse /media/iPhone/
Failed to connect to lockdownd service on the device. Try again. If it still 
fails try rebooting your device.

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

Title:
  iOS device contents not displayed in Ubuntu

Status in Libimobiledevice:
  Fix Released
Status in gnutls28 package in Ubuntu:
  Confirmed
Status in libimobiledevice package in Ubuntu:
  Confirmed

Bug description:
  Plug in iOS device, and it doesn't show the documents on it.

  Please package the recent fix in libimobiledevice*:

  Vauge discussion that mentions using the latest git HEAD*:
  https://github.com/libimobiledevice/libimobiledevice/issues/327

  *This discussion is quite vague. One comment points out "iOS 10
  devices don't allow SSLv3 anymore but require at least TLSv1", but not
  how or if that has been fixed in libimobiledevice git HEAD.

  This ppa packages the git version and may resolve the issue:
  
https://launchpad.net/~martin-salbaba/+archive/ubuntu/ppa+libimobiledevice/+packages

  There are several other upstream reports related to this problem.

  Partial success patch (idevicepair only) trying to keep GnuTLS:
  https://github.com/libimobiledevice/libimobiledevice/issues/413

  Failure with GnuTLS, Success with OpenSSL:
  https://gitlab.com/gnutls/gnutls/issues/145

  Ubuntu packages libimobiledevice with "--disable-openssl":
  https://github.com/libimobiledevice/ifuse/issues/32

  Duplicate bug 1638177 suggests to repackage libimobiledevice using
  OpenSSL to avoid this problem, as per comment 27 below.

To manage notifications about this bug go to:
https://bugs.launchpad.net/libimobiledevice/+bug/1623666/+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 1623666] Re: iOS device contents not displayed in Ubuntu

[J. McDonald]

Update to #39 - iPhone 5C with iOS 10.3 replaced with iPhone SE/iOS
11.03.  I'm back where I started from - no connectivity.  I can mount
the phone but nothing is visible.

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

Title:
  iOS device contents not displayed in Ubuntu

Status in Libimobiledevice:
  Fix Released
Status in gnutls28 package in Ubuntu:
  Confirmed
Status in libimobiledevice package in Ubuntu:
  Confirmed

Bug description:
  Plug in iOS device, and it doesn't show the documents on it.

  Please package the recent fix in libimobiledevice*:

  Vauge discussion that mentions using the latest git HEAD*:
  https://github.com/libimobiledevice/libimobiledevice/issues/327

  *This discussion is quite vague. One comment points out "iOS 10
  devices don't allow SSLv3 anymore but require at least TLSv1", but not
  how or if that has been fixed in libimobiledevice git HEAD.

  This ppa packages the git version and may resolve the issue:
  
https://launchpad.net/~martin-salbaba/+archive/ubuntu/ppa+libimobiledevice/+packages

  There are several other upstream reports related to this problem.

  Partial success patch (idevicepair only) trying to keep GnuTLS:
  https://github.com/libimobiledevice/libimobiledevice/issues/413

  Failure with GnuTLS, Success with OpenSSL:
  https://gitlab.com/gnutls/gnutls/issues/145

  Ubuntu packages libimobiledevice with "--disable-openssl":
  https://github.com/libimobiledevice/ifuse/issues/32

  Duplicate bug 1638177 suggests to repackage libimobiledevice using
  OpenSSL to avoid this problem, as per comment 27 below.

To manage notifications about this bug go to:
https://bugs.launchpad.net/libimobiledevice/+bug/1623666/+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 1623666] Re: iOS device contents not displayed in Ubuntu

[J. McDonald]

I'm using Linux Mint 18.2 Cinnamon.

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

Title:
  iOS device contents not displayed in Ubuntu

Status in Libimobiledevice:
  Fix Released
Status in gnutls28 package in Ubuntu:
  Confirmed
Status in libimobiledevice package in Ubuntu:
  Confirmed

Bug description:
  Plug in iOS device, and it doesn't show the documents on it.

  Please package the recent fix in libimobiledevice*:

  Vauge discussion that mentions using the latest git HEAD*:
  https://github.com/libimobiledevice/libimobiledevice/issues/327

  *This discussion is quite vague. One comment points out "iOS 10
  devices don't allow SSLv3 anymore but require at least TLSv1", but not
  how or if that has been fixed in libimobiledevice git HEAD.

  This ppa packages the git version and may resolve the issue:
  
https://launchpad.net/~martin-salbaba/+archive/ubuntu/ppa+libimobiledevice/+packages

  There are several other upstream reports related to this problem.

  Partial success patch (idevicepair only) trying to keep GnuTLS:
  https://github.com/libimobiledevice/libimobiledevice/issues/413

  Failure with GnuTLS, Success with OpenSSL:
  https://gitlab.com/gnutls/gnutls/issues/145

  Ubuntu packages libimobiledevice with "--disable-openssl":
  https://github.com/libimobiledevice/ifuse/issues/32

  Duplicate bug 1638177 suggests to repackage libimobiledevice using
  OpenSSL to avoid this problem, as per comment 27 below.

To manage notifications about this bug go to:
https://bugs.launchpad.net/libimobiledevice/+bug/1623666/+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 1235245] Re: upstart-monitor cannot run without gtk libraries installed

[Ubuntu Foundations Team Bug Bot]

The attachment "upstart-monitor.cli.patch" seems to be a patch.  If it
isn't, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are a member of the ~ubuntu-reviewers,
unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  upstart-monitor cannot run without gtk libraries installed

Status in upstart :
  New
Status in upstart package in Ubuntu:
  Confirmed

Bug description:
  "upstart-monitor -n" should revert to cli operation. It attempts to do
  this, but then barfs on class UpstartEventsGui(Gtk.Window) since Gtk
  is not imported unless the required gtk libraries are installed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/upstart/+bug/1235245/+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 1732195] Re: [Dell Alienware Alpha R2] Mouse cursor flickering on primary monitor after second monitor HDMI connected to Startech USB32HD4K

[Christopher M. Penalver]

Wei Cai, please don't mark this a duplicate of another report, as it
doesn't have any debugging information to solve the issue.

Despite this, could you please advise to
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1732195/comments/2 ?

** This bug is no longer a duplicate of bug 1278223
   Mouse Flickering after adding 3rd Monitor

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

Title:
  [Dell Alienware Alpha R2] Mouse cursor flickering on primary monitor
  after second monitor HDMI connected to Startech USB32HD4K

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Alienware Alpha R2

  Primary monitor is connected to Nvidia GTX 960
  Secondary monitor is connected to Startech USB32HD4K (Displaylink Ubuntu 
Driver version 1.4.210, http://www.displaylink.com/downloads/ubuntu)

  If only one monitor is connected via Nvidia GTX 960, it is totally
  normal.

  If the second monitor is also connected via Startech USB32HD4K, mouse
  cursor flickers frequently and can even disappear on the PRIMARY
  monitor (the one that is connected to Nvidia GTX 960). On the second
  monitor, everything is fine.

  WORKAROUND: In the GUI go to All Settings > Screen Display > for the primary 
monitor change Rotation from Normal to any of the following:
  Clockwise
  Anti-clockwise
  180 degrees

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.10
  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
  Date: Tue Nov 14 23:59:01 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: evdi, 1.4.210, 4.10.0-38-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation Device [10de:1406] (rev a1) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:072b]
  InstallationDate: Installed on 2017-11-14 (0 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lsusb:
   Bus 002 Device 002: ID 17e9:4301 DisplayLink
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp.
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Alienware ASM201
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-38-generic.efi.signed 
root=UUID=7029fd1a-5743-4bca-b8f7-369a509fac07 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/07/2017
  dmi.bios.vendor: Alienware
  dmi.bios.version: 1.0.8
  dmi.board.name: 0GWM1Y
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: 00
  dmi.modalias: 
dmi:bvnAlienware:bvr1.0.8:bd07/07/2017:svnAlienware:pnASM201:pvr1.0.8:rvnAlienware:rn0GWM1Y:rvrA00:cvnAlienware:ct3:cvr00:
  dmi.product.name: ASM201
  dmi.product.version: 1.0.8
  dmi.sys.vendor: Alienware
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  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: Tue Nov 14 23:55:35 2017
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   modeset(G0): glamor initialization failed
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1~16.04.4
  xserver.video_driver: nouveau

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1732195/+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 1732889] [NEW] graphic bootloader

[Ali Yazdi]

Public bug reported:

i don't have graphical bootloader and i cant restart the PC.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-40-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.12
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME
Date: Fri Nov 17 14:33:06 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: Lenovo Skylake Integrated Graphics [17aa:3800]
InstallationDate: Installed on 2017-11-13 (3 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 005: ID 8087:0a2b Intel Corp. 
 Bus 001 Device 003: ID 13d3:5664 IMC Networks 
 Bus 001 Device 002: ID 09da:054f A4Tech Co., Ltd. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 80MK
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-40-generic.efi.signed 
root=UUID=b72bf002-0c4a-44dc-a065-ecaa2bbb864c ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/11/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: C6CN39WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: VIUU4
dmi.board.vendor: LENOVO
dmi.board.version: SDK0K45914 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo YOGA 900-13ISK
dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN39WW:bd10/11/2016:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0K45914WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
dmi.product.name: 80MK
dmi.product.version: Lenovo YOGA 900-13ISK
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
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: Thu Nov 16 07:06:50 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1~16.04.4
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug ubuntu xenial

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

Title:
  graphic bootloader

Status in xorg package in Ubuntu:
  New

Bug description:
  i don't have graphical bootloader and i cant restart the PC.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-40.44~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-40-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.12
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Fri Nov 17 14:33:06 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Skylake Integrated Graphics [17aa:3800]
  InstallationDate: Installed on 2017-11-13 (3 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 005: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 13d3:5664 IMC Networks 
   Bus 001 Device 002: ID 09da:054f A4Tech Co., Ltd. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80MK
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-40-generic.efi.signed 
root=UUID=b72bf002-0c4a-44dc-a065-ecaa2bbb864c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/11/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN39WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0K45914 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  

[Touch-packages] [Bug 1235245] Re: upstart-monitor cannot run without gtk libraries installed

[Jari Turkia]

Because systemd, apparently nobody ever bothered to fix this.

Here is my patch to make CLI working.

** Patch added: "upstart-monitor.cli.patch"
   
https://bugs.launchpad.net/upstart/+bug/1235245/+attachment/5010432/+files/upstart-monitor.cli.patch

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

Title:
  upstart-monitor cannot run without gtk libraries installed

Status in upstart :
  New
Status in upstart package in Ubuntu:
  Confirmed

Bug description:
  "upstart-monitor -n" should revert to cli operation. It attempts to do
  this, but then barfs on class UpstartEventsGui(Gtk.Window) since Gtk
  is not imported unless the required gtk libraries are installed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/upstart/+bug/1235245/+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 1713536] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From heinz-werner_se...@de.ibm.com 2017-11-17 04:55 EDT---
IBM buzgilla status-> closed, available within all distros in the field

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

Title:
  udev: boot script does not trigger subsystem coldplug

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released
Status in systemd source package in Zesty:
  Fix Released
Status in systemd source package in Artful:
  Fix Released

Bug description:
  [Impact]
  subsystems udev rules are not processed on boot, thus resulting in missing 
devices on boot / before rootfs is mounted.

  [Solution]
  trigger udev subsystems and devices, in the initramfs, in that order.

  [Testcase]
  Boot s390x system with chzdev configured devices, and cio_ignore=all kernel 
command line parameter. The chzdev configured devices should still be 
discovered on boot.

  [Original Bug report]

  The udev initramfs-tools boot script does not trigger subsystem "add"
  uevents. As a result, udev rules that listen to subsystem "add" events
  are never activated. This problem exists on at least Ubuntu 16.04 and
  17.10.

  On s390, this results in a boot failure if the kernel is configured to
  start with an active device black list (kernel parameter
  cio_ignore=all,!condev). An example for an affected udev rule looks
  like this:

  ACTION=="add", SUBSYSTEM=="subsystem", KERNEL=="ccw",
  RUN{program}+="/bin/sh -c 'echo free 0009,ec30,ec32,f5f0-f5f2 >
  /proc/cio_ignore'"

  A proposed fix would be:

  Modify /usr/share/initramfs-tools/scripts/init-top/udev:

  Replace line
  udevadm trigger --action=add
  with
  udevadm trigger --type=subsystems --action=add
  udevadm trigger --type=devices --action=add

  This would also be consistent with the steps that the systemd udev
  coldplug unit file performs (see /lib/systemd/system/systemd-udev-
  trigger.service).

  [Regression Potential]
  More udev rules will be now triggered, earlier, during initramfs stage of 
boot rather than post-pivot-root. However, this is inline with current rootfs 
behaviour and thus should not regress behaviour - simply some rules will get 
triggered earlier.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1713536/+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 1732876] Re: package apport 2.20.1-0ubuntu2.12 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package apport 2.20.1-0ubuntu2.12 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in apport package in Ubuntu:
  New

Bug description:
  I just see message box in time of start ubuntu.
  Yesterday I've installed packages:

  git (1:2.7.4-0ubuntu1.3)
  git-man (1:2.7.4-0ubuntu1.3)
  liberror-perl (0.17-1.2)

  libncurses5-dev (6.0+20160213-1ubuntu1)
  libtinfo-dev (6.0+20160213-1ubuntu1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.12
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.1-0ubuntu2.12
  Architecture: amd64
  CrashReports:
   600:0:117:417006:2017-11-17 11:58:01.743627786 +0300:2017-11-17 
11:58:02.743627786 +0300:/var/crash/apport.0.crash
   640:1000:117:134014:2017-11-15 16:38:53.322045564 +0300:2017-11-15 
16:38:54.322045564 
+0300:/var/crash/_opt_Qt5.6.3_Tools_QtCreator_bin_qtcreator.1000.crash
  Date: Fri Nov 17 11:58:02 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-11-10 (6 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: apport
  Title: package apport 2.20.1-0ubuntu2.12 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/apport/+bug/1732876/+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 1732876] [NEW] package apport 2.20.1-0ubuntu2.12 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Evgraphov Alexey]

Public bug reported:

I just see message box in time of start ubuntu.
Yesterday I've installed packages:

git (1:2.7.4-0ubuntu1.3)
git-man (1:2.7.4-0ubuntu1.3)
liberror-perl (0.17-1.2)

libncurses5-dev (6.0+20160213-1ubuntu1)
libtinfo-dev (6.0+20160213-1ubuntu1)

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: apport 2.20.1-0ubuntu2.12
ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
Uname: Linux 4.10.0-38-generic x86_64
ApportLog:
 
ApportVersion: 2.20.1-0ubuntu2.12
Architecture: amd64
CrashReports:
 600:0:117:417006:2017-11-17 11:58:01.743627786 +0300:2017-11-17 
11:58:02.743627786 +0300:/var/crash/apport.0.crash
 640:1000:117:134014:2017-11-15 16:38:53.322045564 +0300:2017-11-15 
16:38:54.322045564 
+0300:/var/crash/_opt_Qt5.6.3_Tools_QtCreator_bin_qtcreator.1000.crash
Date: Fri Nov 17 11:58:02 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2017-11-10 (6 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: apport
Title: package apport 2.20.1-0ubuntu2.12 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: apport (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 apport in Ubuntu.
https://bugs.launchpad.net/bugs/1732876

Title:
  package apport 2.20.1-0ubuntu2.12 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in apport package in Ubuntu:
  New

Bug description:
  I just see message box in time of start ubuntu.
  Yesterday I've installed packages:

  git (1:2.7.4-0ubuntu1.3)
  git-man (1:2.7.4-0ubuntu1.3)
  liberror-perl (0.17-1.2)

  libncurses5-dev (6.0+20160213-1ubuntu1)
  libtinfo-dev (6.0+20160213-1ubuntu1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.12
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.1-0ubuntu2.12
  Architecture: amd64
  CrashReports:
   600:0:117:417006:2017-11-17 11:58:01.743627786 +0300:2017-11-17 
11:58:02.743627786 +0300:/var/crash/apport.0.crash
   640:1000:117:134014:2017-11-15 16:38:53.322045564 +0300:2017-11-15 
16:38:54.322045564 
+0300:/var/crash/_opt_Qt5.6.3_Tools_QtCreator_bin_qtcreator.1000.crash
  Date: Fri Nov 17 11:58:02 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2017-11-10 (6 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: apport
  Title: package apport 2.20.1-0ubuntu2.12 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/apport/+bug/1732876/+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 1716203] Re: Backport packages for 16.04.4 HWE stack

[Adam Conrad]

Hello Timo, or anyone else affected,

Accepted wayland-protocols into xenial-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/wayland-
protocols/1.10-1~16.04.1 in a few hours, and then in the -proposed
repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

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

** Changed in: wayland-protocols (Ubuntu Xenial)
   Status: New => Fix Committed

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

Title:
  Backport packages for 16.04.4 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-5.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in wayland-protocols package in Ubuntu:
  Invalid
Status in xorg-hwe-16.04 package in Ubuntu:
  Invalid
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in libclc source package in Xenial:
  Fix Committed
Status in libdrm source package in Xenial:
  Fix Committed
Status in llvm-toolchain-5.0 source package in Xenial:
  Fix Committed
Status in mesa source package in Xenial:
  New
Status in wayland-protocols source package in Xenial:
  Fix Committed
Status in xorg-hwe-16.04 source package in Xenial:
  New
Status in xorg-server-hwe-16.04 source package in Xenial:
  New

Bug description:
  [Impact]

  *** hwe-16.04 refresh for 16.04.4 ***

  A minor update, only some driver updates plus a newer Mesa.

  Mesa needs llvm-toolchain-5.0 and libclc, libdrm, wayland-protocols
  updates.

  [Test case]

  upgrade from/to stock & old hwe stack, test desktop usage

  [Regression potential]

  libdrm:
  Slim to none, changes from 2.4.76 to 2.4.83
  - amdgpu: pci-id handling moved here, new pci-ids, bugfixes, tests
  - intel: new pci-ids
  - drm: leak fixes, manpage updates
  - exynos, etnaviv, freedreno, android: fixes, new stuff

  wayland-protocols:
  None, just adds a few protocol definitions (xml files)

  llvm-toolchain-5.0:
  None, a new package

  libclc:
  I'd say none, very little has changed, added support for llvm-5 is the main 
reason for this slightly newer snapshot

  xorg-server:
  Slim, it's an upstream bugfix release, changes from 1.19.3 to 1.19.5 include:
  - security fixes
  - backported bugfixes to glamor, modesetting driver, xwayland etc

  mesa:
  New major release plus a few bugfix updates after that. Regressions at this 
point are less likely. Upstream is tested by Intel CI system for instance. And 
we're already testing it via a ppa on OEM systems for 16.04.4. Tracking bug for 
the bugfix release (xenial & artful) is bug 1727390

  [Other information]

  build order: [libdrm, wayland-protocols, llvm-toolchain-5.0], [libclc,
  xorg-server], mesa

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1716203/+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 1732865] Re: [LTCTest][OPAL][FW860.20] lscpu failed to list cpu max and min frequencies

[Andrew Cloke]

** Also affects: ubuntu-power-systems
   Importance: Undecided
   Status: New

** Changed in: ubuntu-power-systems
   Importance: Undecided => High

** Changed in: ubuntu-power-systems
 Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team)

** Tags added: triage-g

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

Title:
  [LTCTest][OPAL][FW860.20] lscpu failed to list cpu max and min
  frequencies

Status in The Ubuntu-power-systems project:
  New
Status in util-linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Pridhiviraj Paidipeddi  - 2017-01-03 
05:34:32 ==
  ---Problem Description---
  After 3 CPU's are garded, lscpu failed to list CPU max and min frequencies
   
  Contact Information = ppaid...@in.ibm.com 
   
  ---uname output---
  Linux p8wookie 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 
UTC 2016 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = PowerNV 8284-22A 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Read lscpu output
  2. Inject HMI Non recoverable error three times
  3. Read lscpu output again
  compare the output cpu frequencies will list as NULL
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  Userspace tool common name: lscpu 

  Userspace rpm: util-linux 
   
  The userspace tool has the following bit modes: 64-bit 
   
  System Dump Info:
The system is not configured to capture a system dump.

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for ppaid...@in.ibm.com: 
  -Post a private note with access information to the machine that the bug is 
occuring on. 
  -Attach sysctl -a output output to the bug.
  -Attach ltrace and strace of userspace application.

  
  Before CPU's are garded:
  root@p8wookie:~# lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):112
  On-line CPU(s) list:   0-71,80-103,112-127
  Thread(s) per core:8
  Core(s) per socket:3
  Socket(s): 4
  NUMA node(s):  4
  Model: 2.1 (pvr 004b 0201)
  Model name:POWER8E (raw), altivec supported
  CPU max MHz:   4322.
  CPU min MHz:   2061.
  L1d cache: 64K
  L1i cache: 32K
  L2 cache:  512K
  L3 cache:  8192K
  NUMA node0 CPU(s): 0-31
  NUMA node1 CPU(s): 32-63
  NUMA node16 CPU(s):64-71,80-95
  NUMA node17 CPU(s):96-103,112-127

  
  After 4 cores are garded:
  root@p8wookie:~# lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):96
  On-line CPU(s) list:   8-55,64-71,80-103,112-127
  Thread(s) per core:8
  Core(s) per socket:3
  Socket(s): 4
  NUMA node(s):  4
  Model: 2.1 (pvr 004b 0201)
  Model name:POWER8E (raw), altivec supported
  CPU max MHz:   (null)
  CPU min MHz:   (null)
  L1d cache: 64K
  L1i cache: 32K
  L2 cache:  512K
  L3 cache:  8192K
  NUMA node0 CPU(s): 8-31
  NUMA node1 CPU(s): 32-55
  NUMA node16 CPU(s):64-71,80-95
  NUMA node17 CPU(s):96-103,112-127

  == Comment: #1 - Pridhiviraj Paidipeddi  - 2017-01-11 
07:06:59 ==
  root@p8wookie:~# dmesg |grep -i powernv
  [0.00] Using PowerNV machine description
  [0.331564] EEH: PowerNV platform initialized
  [0.907250] powernv-rng: Registering arch random hook.
  [1.504063] powernv-cpufreq: cpufreq pstate min -68 nominal -5 max 0
  [1.507167] powernv_idle_driver registered
  [   34.184048] powernv_rng: Registered powernv hwrng.
  [   34.185619] ipmi-powernv ibm,opal:ipmi: Unable to map irq from device tree
  [   34.210966] ipmi-powernv ibm,opal:ipmi: Found new BMC (man_id: 0x00, 
prod_id: 0x, dev_id: 0x00)
  root@p8wookie:~# cat /sys/firmware/opal/msglog | grep -i occ
  [   42.297825315,7]   OCC Common Area at 0x3b0 size 1MB
  [   42.297854780,7]   OCC Common Area at 0x200080 size 1MB
  [   42.297884305,7]   OCC Common Area at 0x200080 size 1MB
  [   42.297914258,7]   OCC Common Area at 0x200080 size 1MB
  [   42.310897465,7] HBRT: OCC common base 00200080 : 0080
  [   42.317109440,7] HBRT: OCC common base 00200080 : 0080
  [   42.323969570,7] HBRT: OCC common base 00200080 : 0080
  [   42.330941943,7] HBRT: OCC common base 00200080 : 0080
  [5.349544066,6] OCC: Got OCC Load message, scope=0x2 dbob=0x0 seq=0x29
  [6.017413373,7] HBRT: OCC Load requested
  [6.017414365,7] HBRT: Calling loadOCC() homer 00200140, 
occ_common_area 00200080, chip 
  [6.017553013,7] HBRT: Calling loadOCC() homer 3a00, 

[Touch-packages] [Bug 1716203] Re: Backport packages for 16.04.4 HWE stack

[Adam Conrad]

Hello Timo, or anyone else affected,

Accepted llvm-toolchain-5.0 into xenial-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/llvm-
toolchain-5.0/1:5.0-3~16.04.1 in a few hours, and then in the -proposed
repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

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

** Changed in: llvm-toolchain-5.0 (Ubuntu Xenial)
   Status: New => Fix Committed

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

Title:
  Backport packages for 16.04.4 HWE stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in llvm-toolchain-5.0 package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in wayland-protocols package in Ubuntu:
  Invalid
Status in xorg-hwe-16.04 package in Ubuntu:
  Invalid
Status in xorg-server-hwe-16.04 package in Ubuntu:
  Invalid
Status in libclc source package in Xenial:
  Fix Committed
Status in libdrm source package in Xenial:
  Fix Committed
Status in llvm-toolchain-5.0 source package in Xenial:
  Fix Committed
Status in mesa source package in Xenial:
  New
Status in wayland-protocols source package in Xenial:
  New
Status in xorg-hwe-16.04 source package in Xenial:
  New
Status in xorg-server-hwe-16.04 source package in Xenial:
  New

Bug description:
  [Impact]

  *** hwe-16.04 refresh for 16.04.4 ***

  A minor update, only some driver updates plus a newer Mesa.

  Mesa needs llvm-toolchain-5.0 and libclc, libdrm, wayland-protocols
  updates.

  [Test case]

  upgrade from/to stock & old hwe stack, test desktop usage

  [Regression potential]

  libdrm:
  Slim to none, changes from 2.4.76 to 2.4.83
  - amdgpu: pci-id handling moved here, new pci-ids, bugfixes, tests
  - intel: new pci-ids
  - drm: leak fixes, manpage updates
  - exynos, etnaviv, freedreno, android: fixes, new stuff

  wayland-protocols:
  None, just adds a few protocol definitions (xml files)

  llvm-toolchain-5.0:
  None, a new package

  libclc:
  I'd say none, very little has changed, added support for llvm-5 is the main 
reason for this slightly newer snapshot

  xorg-server:
  Slim, it's an upstream bugfix release, changes from 1.19.3 to 1.19.5 include:
  - security fixes
  - backported bugfixes to glamor, modesetting driver, xwayland etc

  mesa:
  New major release plus a few bugfix updates after that. Regressions at this 
point are less likely. Upstream is tested by Intel CI system for instance. And 
we're already testing it via a ppa on OEM systems for 16.04.4. Tracking bug for 
the bugfix release (xenial & artful) is bug 1727390

  [Other information]

  build order: [libdrm, wayland-protocols, llvm-toolchain-5.0], [libclc,
  xorg-server], mesa

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1716203/+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 1732865] lscpu patch

[bugproxy]

Default Comment by Bridge

** Attachment added: "lscpu patch"
   
https://bugs.launchpad.net/bugs/1732865/+attachment/5010377/+files/0001-This-patch-is-to-check-for-max-and-min-frequency-of-.patch

** Changed in: ubuntu
 Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage 
(ubuntu-power-triage)

** Package changed: ubuntu => util-linux (Ubuntu)

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

Title:
  [LTCTest][OPAL][FW860.20] lscpu failed to list cpu max and min
  frequencies

Status in util-linux package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Pridhiviraj Paidipeddi  - 2017-01-03 
05:34:32 ==
  ---Problem Description---
  After 3 CPU's are garded, lscpu failed to list CPU max and min frequencies
   
  Contact Information = ppaid...@in.ibm.com 
   
  ---uname output---
  Linux p8wookie 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 
UTC 2016 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = PowerNV 8284-22A 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   1. Read lscpu output
  2. Inject HMI Non recoverable error three times
  3. Read lscpu output again
  compare the output cpu frequencies will list as NULL
   
  Stack trace output:
   no
   
  Oops output:
   no
   
  Userspace tool common name: lscpu 

  Userspace rpm: util-linux 
   
  The userspace tool has the following bit modes: 64-bit 
   
  System Dump Info:
The system is not configured to capture a system dump.

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for ppaid...@in.ibm.com: 
  -Post a private note with access information to the machine that the bug is 
occuring on. 
  -Attach sysctl -a output output to the bug.
  -Attach ltrace and strace of userspace application.

  
  Before CPU's are garded:
  root@p8wookie:~# lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):112
  On-line CPU(s) list:   0-71,80-103,112-127
  Thread(s) per core:8
  Core(s) per socket:3
  Socket(s): 4
  NUMA node(s):  4
  Model: 2.1 (pvr 004b 0201)
  Model name:POWER8E (raw), altivec supported
  CPU max MHz:   4322.
  CPU min MHz:   2061.
  L1d cache: 64K
  L1i cache: 32K
  L2 cache:  512K
  L3 cache:  8192K
  NUMA node0 CPU(s): 0-31
  NUMA node1 CPU(s): 32-63
  NUMA node16 CPU(s):64-71,80-95
  NUMA node17 CPU(s):96-103,112-127

  
  After 4 cores are garded:
  root@p8wookie:~# lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):96
  On-line CPU(s) list:   8-55,64-71,80-103,112-127
  Thread(s) per core:8
  Core(s) per socket:3
  Socket(s): 4
  NUMA node(s):  4
  Model: 2.1 (pvr 004b 0201)
  Model name:POWER8E (raw), altivec supported
  CPU max MHz:   (null)
  CPU min MHz:   (null)
  L1d cache: 64K
  L1i cache: 32K
  L2 cache:  512K
  L3 cache:  8192K
  NUMA node0 CPU(s): 8-31
  NUMA node1 CPU(s): 32-55
  NUMA node16 CPU(s):64-71,80-95
  NUMA node17 CPU(s):96-103,112-127

  == Comment: #1 - Pridhiviraj Paidipeddi  - 2017-01-11 
07:06:59 ==
  root@p8wookie:~# dmesg |grep -i powernv
  [0.00] Using PowerNV machine description
  [0.331564] EEH: PowerNV platform initialized
  [0.907250] powernv-rng: Registering arch random hook.
  [1.504063] powernv-cpufreq: cpufreq pstate min -68 nominal -5 max 0
  [1.507167] powernv_idle_driver registered
  [   34.184048] powernv_rng: Registered powernv hwrng.
  [   34.185619] ipmi-powernv ibm,opal:ipmi: Unable to map irq from device tree
  [   34.210966] ipmi-powernv ibm,opal:ipmi: Found new BMC (man_id: 0x00, 
prod_id: 0x, dev_id: 0x00)
  root@p8wookie:~# cat /sys/firmware/opal/msglog | grep -i occ
  [   42.297825315,7]   OCC Common Area at 0x3b0 size 1MB
  [   42.297854780,7]   OCC Common Area at 0x200080 size 1MB
  [   42.297884305,7]   OCC Common Area at 0x200080 size 1MB
  [   42.297914258,7]   OCC Common Area at 0x200080 size 1MB
  [   42.310897465,7] HBRT: OCC common base 00200080 : 0080
  [   42.317109440,7] HBRT: OCC common base 00200080 : 0080
  [   42.323969570,7] HBRT: OCC common base 00200080 : 0080
  [   42.330941943,7] HBRT: OCC common base 00200080 : 0080
  [5.349544066,6] OCC: Got OCC Load message, scope=0x2 dbob=0x0 seq=0x29
  [6.017413373,7] HBRT: OCC Load requested
  [6.017414365,7] HBRT: Calling loadOCC() homer 00200140, 
occ_common_area 00200080, chip 
  [6.017553013,7] HBRT: Calling loadOCC() homer 

[Touch-packages] [Bug 1732865] [NEW] [LTCTest][OPAL][FW860.20] lscpu failed to list cpu max and min frequencies

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

== Comment: #0 - Pridhiviraj Paidipeddi  - 2017-01-03 
05:34:32 ==
---Problem Description---
After 3 CPU's are garded, lscpu failed to list CPU max and min frequencies
 
Contact Information = ppaid...@in.ibm.com 
 
---uname output---
Linux p8wookie 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 UTC 
2016 ppc64le ppc64le ppc64le GNU/Linux
 
Machine Type = PowerNV 8284-22A 
 
---Debugger---
A debugger is not configured
 
---Steps to Reproduce---
 1. Read lscpu output
2. Inject HMI Non recoverable error three times
3. Read lscpu output again
compare the output cpu frequencies will list as NULL
 
Stack trace output:
 no
 
Oops output:
 no
 
Userspace tool common name: lscpu 

Userspace rpm: util-linux 
 
The userspace tool has the following bit modes: 64-bit 
 
System Dump Info:
  The system is not configured to capture a system dump.

Userspace tool obtained from project website:  na 
 
*Additional Instructions for ppaid...@in.ibm.com: 
-Post a private note with access information to the machine that the bug is 
occuring on. 
-Attach sysctl -a output output to the bug.
-Attach ltrace and strace of userspace application.


Before CPU's are garded:
root@p8wookie:~# lscpu
Architecture:  ppc64le
Byte Order:Little Endian
CPU(s):112
On-line CPU(s) list:   0-71,80-103,112-127
Thread(s) per core:8
Core(s) per socket:3
Socket(s): 4
NUMA node(s):  4
Model: 2.1 (pvr 004b 0201)
Model name:POWER8E (raw), altivec supported
CPU max MHz:   4322.
CPU min MHz:   2061.
L1d cache: 64K
L1i cache: 32K
L2 cache:  512K
L3 cache:  8192K
NUMA node0 CPU(s): 0-31
NUMA node1 CPU(s): 32-63
NUMA node16 CPU(s):64-71,80-95
NUMA node17 CPU(s):96-103,112-127


After 4 cores are garded:
root@p8wookie:~# lscpu
Architecture:  ppc64le
Byte Order:Little Endian
CPU(s):96
On-line CPU(s) list:   8-55,64-71,80-103,112-127
Thread(s) per core:8
Core(s) per socket:3
Socket(s): 4
NUMA node(s):  4
Model: 2.1 (pvr 004b 0201)
Model name:POWER8E (raw), altivec supported
CPU max MHz:   (null)
CPU min MHz:   (null)
L1d cache: 64K
L1i cache: 32K
L2 cache:  512K
L3 cache:  8192K
NUMA node0 CPU(s): 8-31
NUMA node1 CPU(s): 32-55
NUMA node16 CPU(s):64-71,80-95
NUMA node17 CPU(s):96-103,112-127

== Comment: #1 - Pridhiviraj Paidipeddi  - 2017-01-11 
07:06:59 ==
root@p8wookie:~# dmesg |grep -i powernv
[0.00] Using PowerNV machine description
[0.331564] EEH: PowerNV platform initialized
[0.907250] powernv-rng: Registering arch random hook.
[1.504063] powernv-cpufreq: cpufreq pstate min -68 nominal -5 max 0
[1.507167] powernv_idle_driver registered
[   34.184048] powernv_rng: Registered powernv hwrng.
[   34.185619] ipmi-powernv ibm,opal:ipmi: Unable to map irq from device tree
[   34.210966] ipmi-powernv ibm,opal:ipmi: Found new BMC (man_id: 0x00, 
prod_id: 0x, dev_id: 0x00)
root@p8wookie:~# cat /sys/firmware/opal/msglog | grep -i occ
[   42.297825315,7]   OCC Common Area at 0x3b0 size 1MB
[   42.297854780,7]   OCC Common Area at 0x200080 size 1MB
[   42.297884305,7]   OCC Common Area at 0x200080 size 1MB
[   42.297914258,7]   OCC Common Area at 0x200080 size 1MB
[   42.310897465,7] HBRT: OCC common base 00200080 : 0080
[   42.317109440,7] HBRT: OCC common base 00200080 : 0080
[   42.323969570,7] HBRT: OCC common base 00200080 : 0080
[   42.330941943,7] HBRT: OCC common base 00200080 : 0080
[5.349544066,6] OCC: Got OCC Load message, scope=0x2 dbob=0x0 seq=0x29
[6.017413373,7] HBRT: OCC Load requested
[6.017414365,7] HBRT: Calling loadOCC() homer 00200140, 
occ_common_area 00200080, chip 
[6.017553013,7] HBRT: Calling loadOCC() homer 3a00, 
occ_common_area 00200080, chip 0001
[6.017666150,7] HBRT: Calling loadOCC() homer 00280040, 
occ_common_area 00200080, chip 0010
[6.017790110,7] HBRT: Calling loadOCC() homer 00100040, 
occ_common_area 00200080, chip 0011
[6.017929155,6] HBRT: OCC Start requested
[6.042511828,7] HBRT: startOCCs() rc  = 0
[   22.190466757,5] irq 11 name: psi:occ (7/8)
[   22.190474587,5] irq 20011 name: psi:occ (7/56)
[   22.193374475,7] OCC: Chip 00 Data (0020015f8000) = 010100bcfb00
[   22.193376434,7] OCC: Chip 01 Data (3a1f8000) = 010100bcfb00
[   22.193378259,7] OCC: Chip 10 Data (0028005f8000) = 010100bcfb00
[   22.193380201,7] OCC: Chip 11 Data (0010005f8000) = 010100bcfb00
[   22.193382038,5] OCC: All Chip Rdy after 0 ms
[   22.193415815,7] OCC: CPU pstate state device 

[Touch-packages] [Bug 1278223] Re: Mouse Flickering after adding 3rd Monitor

[Brad Cutshall]

Environment:
Fresh install 16.04
Razer Blade 14 2014
Intel GPU
Nvidia 870M
1x HDMI port

I originally had no video drivers installed and was using the Intel gpu
and this did not work with DisplayLink with 1.4x drivers installed until
i added xorg.conf.d/20-intel.conf. After this it worked as a third
display but I had disappearing mouse cursor issues constantly and only
with the DisplayLink hdmi usb adapter plugged in... there were times
when the mouse wouldn't come back for minutes. Most of the time the
behavior would be: on the top half of the screen the mouse would only
flicker and on the bottom half it would completely disappear. I
experimented with all permutations in the directory
/usr/share/xorg.conf.d/ between 20-nvidia.conf, 20-intel.conf one being
present vs both and all of the params in each scenario: TearingFree
false/true, TripleBuffering false/true, PageFlip false/true

Solution for me was to use the GNOME desktop, the 20-intel.conf with only:
Section "Device"
Identifier "Intel Graphics"
Driver "Intel"
EndSection

And using the Nvidia driver 340 proprietary in AdditionalDrivers while
setting it to be primary usage in Nvidia application with rendering
quality set to performance.

No more disappearing mouse, 3 monitors all plugged in at boot and only a 10 
second wait for the USB DisplayLink monitor to show up after login.
 
Cheers

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

Title:
  Mouse Flickering after adding 3rd Monitor

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  *PLEASE READ FIRST BEFORE CONSIDERING MAKING A COMMENT*
  If you are having an issue and want it addressed, it is most helpful to file 
a new report. If you were led here by DisplayLink's website, you were led here 
in error as no useful debugging information has been provided by the original 
reporter, which is necessary to root cause, and solve the issue he reported. 
Posting comments about how you think you have the same problem isn't helpful 
here.

  My issues is, after adding a 3rd monitor to Ubuntu 14.04, the mouse
  flickers (or blinks) when the cursor is on monitors one or two, but
  not 3.

  Monitor 1: 1440 x 900 - Laptop's Native Monitor
  Monitor 2: 1920 x 1080 - Laptop's HDMI Port's External Monitor
  Monitor 3: 1024 x 768 - SIIG USB 2.0 to VGA Pro Monitor

  Here's the video card that feeds my laptop's native monitor, monitor 2
  (hdmi).

  lspci | grep 'VGA\|Display'
  00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)
  00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)

  The 3rd Monitor is powered through a Display Link certified SIIG USB
  2.0 to VGA Pro adapter (A2H1320X1374 - not sure what this number, but
  it is a sticker on back of the device):

  lsusb -tv
  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  |__ Port 6: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
  |__ Port 6: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M

  dmesg
  [1.688343] usb 2-1: New USB device found, idVendor=17e9, idProduct=02ee
  [1.688348] usb 2-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [1.688351] usb 2-1: Product: VGA Display Adapter
  [1.688353] usb 2-1: Manufacturer: DisplayLink
  [1.688356] usb 2-1: SerialNumber: 119785

  Additionally, unity-control-center crashes sometimes after I "Restore
  previous settings", after selecting a resolution too high. This
  freezed my laptop, requiring a hard reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.1-0ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb  9 18:43:13 2014
  InstallationDate: Installed on 2014-02-02 (7 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140202)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1278223/+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 1732195] Re: [Dell Alienware Alpha R2] Mouse cursor flickering on primary monitor after second monitor HDMI connected to Startech USB32HD4K

[Wei Cai]

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

** This bug has been marked a duplicate of bug 1278223
   Mouse Flickering after adding 3rd Monitor

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

Title:
  [Dell Alienware Alpha R2] Mouse cursor flickering on primary monitor
  after second monitor HDMI connected to Startech USB32HD4K

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Alienware Alpha R2

  Primary monitor is connected to Nvidia GTX 960
  Secondary monitor is connected to Startech USB32HD4K (Displaylink Ubuntu 
Driver version 1.4.210, http://www.displaylink.com/downloads/ubuntu)

  If only one monitor is connected via Nvidia GTX 960, it is totally
  normal.

  If the second monitor is also connected via Startech USB32HD4K, mouse
  cursor flickers frequently and can even disappear on the PRIMARY
  monitor (the one that is connected to Nvidia GTX 960). On the second
  monitor, everything is fine.

  WORKAROUND: In the GUI go to All Settings > Screen Display > for the primary 
monitor change Rotation from Normal to any of the following:
  Clockwise
  Anti-clockwise
  180 degrees

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-38.42~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-38-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.10
  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
  Date: Tue Nov 14 23:59:01 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: evdi, 1.4.210, 4.10.0-38-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation Device [10de:1406] (rev a1) (prog-if 00 [VGA controller])
     Subsystem: Dell Device [1028:072b]
  InstallationDate: Installed on 2017-11-14 (0 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lsusb:
   Bus 002 Device 002: ID 17e9:4301 DisplayLink
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2b Intel Corp.
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Alienware ASM201
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-38-generic.efi.signed 
root=UUID=7029fd1a-5743-4bca-b8f7-369a509fac07 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/07/2017
  dmi.bios.vendor: Alienware
  dmi.bios.version: 1.0.8
  dmi.board.name: 0GWM1Y
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: 00
  dmi.modalias: 
dmi:bvnAlienware:bvr1.0.8:bd07/07/2017:svnAlienware:pnASM201:pvr1.0.8:rvnAlienware:rn0GWM1Y:rvrA00:cvnAlienware:ct3:cvr00:
  dmi.product.name: ASM201
  dmi.product.version: 1.0.8
  dmi.sys.vendor: Alienware
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.16.04.2
  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: Tue Nov 14 23:55:35 2017
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
   modeset(G0): glamor initialization failed
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1~16.04.4
  xserver.video_driver: nouveau

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1732195/+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 1686189] Re: External monitor connecting problem on Intel graphics card

[Kai-Heng Feng]

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

Title:
  External monitor connecting problem on Intel graphics card

Status in linux package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I am facing a problem with Intel Graphics driver. I have external
  monitor and in display settings the second monitor is detecting but
  it's not working, so could you email me a solution.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.4.25-040425-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  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
  Date: Tue Apr 25 21:45:16 2017
  DistUpgraded: 2017-04-25 21:07:40,819 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: i915-4.6.3-4.4.0, 1, 4.4.0-75-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:05e9]
  InstallationDate: Installed on 2017-04-25 (0 days ago)
  InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803)
  MachineType: Dell Inc. Inspiron 3537
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.25-040425-generic 
root=UUID=3914e6d5-5c87-4816-8043-776ef4184d29 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-04-25 (0 days ago)
  dmi.bios.date: 04/30/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: 03JPPR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd04/30/2014:svnDellInc.:pnInspiron3537:pvrA08:rvnDellInc.:rn03JPPR:rvrA00:cvnDellInc.:ct8:cvrA08:
  dmi.product.name: Inspiron 3537
  dmi.product.version: A08
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
  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
  xserver.bootTime: Tue Apr 25 21:37:24 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   17900 
   vendor AUO
  xserver.version: 2:1.18.4-0ubuntu0.2

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