[Touch-packages] [Bug 1581160] Re: Switch to Noto Sans as default font for Japanese and/or Korean?

[Jung-Kyu Park]

It seems package fonts-nanum* have been removed correctly though, fonts-
unfonts* seems still exist on bionic, tested in daily cdimage of today.


** Attachment added: "스크린샷, 2017-11-23 16-36-46.png"
   
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1581160/+attachment/5013302/+files/%EC%8A%A4%ED%81%AC%EB%A6%B0%EC%83%B7%2C%202017-11-23%2016-36-46.png

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

Title:
  Switch to Noto Sans as default font for Japanese and/or Korean?

Status in language-selector package in Ubuntu:
  In Progress
Status in lubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-budgie-meta package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntukylin-meta package in Ubuntu:
  Fix Released
Status in ubuntustudio-meta package in Ubuntu:
  Fix Released

Bug description:
  In Ubuntu 16.04 Noto Sans CJK is the default font for rendering
  Chinese. After having struggled with a few issues, I believe that we
  finally achieved the desired improvement of the rendering experience.

  So now I ask: Is there an interest from Japanese and Korean users to
  consider a switch to Noto Sans? (The fonts are already installed for
  all users on Ubuntu 16.04.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1581160/+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 1636578] Re: [HP Notebook, Realtek ALC3227, Speaker, Internal] Sound occasionally skips, sort of like a scratched CD

[Launchpad Bug Tracker]

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

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

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

Title:
  [HP Notebook, Realtek ALC3227, Speaker, Internal] Sound occasionally
  skips, sort of like a scratched CD

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  When playing a youtube video, I occasionally get these skips in the
  audio, and sometimes they are quite severe, meaning I have to go back
  and play the section again in order to hear it properly.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21
  Uname: Linux 4.4.0-45-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jack   1723 F pulseaudio
   /dev/snd/controlC0:  jack   1723 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Oct 25 18:12:21 2016
  InstallationDate: Installed on 2016-10-24 (1 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic successful
  Symptom_Card: Built-in Audio - HD-Audio Generic
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: Digital clip or distortion, or "overdriven" sound
  Title: [HP Notebook, Realtek ALC3227, Speaker, Internal] Sound is distorted
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/19/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.09
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 81F5
  dmi.board.vendor: HP
  dmi.board.version: 66.25
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.09:bd05/19/2016:svnHP:pnHPNotebook:pvrType1ProductConfigId:rvnHP:rn81F5:rvr66.25:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1636578/+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 1734041] [NEW] openssh: The concurrency of settimeofday and ssh connect would lead to coredump

[wang]

Public bug reported:

Hi, pals:
we found a coredump when we do ssh connection. the basic information as follow:
the stack trace in coredump:
(gdb) bt
#0 0x20007510 in raise () from /lib/libc.so.6
#1 0x2000c718 in abort () from /lib/libc.so.6
#2 0x2053d42c in __mulvsi3 (a=, b=) at 
/home/l00194794/yocto/c08_sdk/sdk/build/script/cpu_hcc/ppc-linux/../../../toolchain_soft/ppc-linux/src/gcc-4.7.1/libgcc/libgcc2.c:159
#3 0x2050d030 in ms_subtract_diff (start=start@entry=0xbfa20a9c, ms=0x48027c40, 
ms@entry=0xbfa20a98) at misc.c:871
#4 0x204d2568 in ssh_exchange_identification (timeout_ms=timeout_ms@entry=5000) 
at sshconnect.c:580
#5 0x204d3e3c in ssh_login (sensitive=sensitive@entry=0x20586ea8, orighost=, 
hostaddr=hostaddr@entry=0x20586e28, port=, pw=pw@entry=0x20589ae8, 
timeout_ms=5000)
at sshconnect.c:1346
#6 0x204c433c in main (ac=, av=) at ssh.c:1326

the direct cause of the coredump, is that the function __mulvsi3 in gcc
checked the plus operation is overflow, then this gcc function abort().

the reason of the overflow is cause by the time-setting operation when
do ssh connect. in function ms_subtract_diff . the timeoutp get a very
big value because of the time-change.

So could we add a limitation for the differ of the 2 values get from 
gettimeofday ? if it's too big, would lead to overflow, we set a default value 
and report a warning log.
thanks for you attention and expect your reply.

B.R.
Le Wang

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

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

Title:
  openssh: The concurrency of settimeofday and ssh connect would lead to
  coredump

Status in openssh package in Ubuntu:
  New

Bug description:
  Hi, pals:
  we found a coredump when we do ssh connection. the basic information as 
follow:
  the stack trace in coredump:
  (gdb) bt
  #0 0x20007510 in raise () from /lib/libc.so.6
  #1 0x2000c718 in abort () from /lib/libc.so.6
  #2 0x2053d42c in __mulvsi3 (a=, b=) at 
/home/l00194794/yocto/c08_sdk/sdk/build/script/cpu_hcc/ppc-linux/../../../toolchain_soft/ppc-linux/src/gcc-4.7.1/libgcc/libgcc2.c:159
  #3 0x2050d030 in ms_subtract_diff (start=start@entry=0xbfa20a9c, 
ms=0x48027c40, ms@entry=0xbfa20a98) at misc.c:871
  #4 0x204d2568 in ssh_exchange_identification 
(timeout_ms=timeout_ms@entry=5000) at sshconnect.c:580
  #5 0x204d3e3c in ssh_login (sensitive=sensitive@entry=0x20586ea8, orighost=, 
hostaddr=hostaddr@entry=0x20586e28, port=, pw=pw@entry=0x20589ae8, 
timeout_ms=5000)
  at sshconnect.c:1346
  #6 0x204c433c in main (ac=, av=) at ssh.c:1326

  the direct cause of the coredump, is that the function __mulvsi3 in
  gcc checked the plus operation is overflow, then this gcc function
  abort().

  the reason of the overflow is cause by the time-setting operation when
  do ssh connect. in function ms_subtract_diff . the timeoutp get a very
  big value because of the time-change.

  So could we add a limitation for the differ of the 2 values get from 
gettimeofday ? if it's too big, would lead to overflow, we set a default value 
and report a warning log.
  thanks for you attention and expect your reply.

  B.R.
  Le Wang

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1734041/+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 1734040] [NEW] openssh: The concurrency of settimeofday and ssh connect would lead to coredump

[wang]

Public bug reported:

Hi, pals:
we found a coredump when we do ssh connection. the basic information as follow:
the stack trace in coredump:
(gdb) bt
#0 0x20007510 in raise () from /lib/libc.so.6
#1 0x2000c718 in abort () from /lib/libc.so.6
#2 0x2053d42c in __mulvsi3 (a=, b=) at 
/home/l00194794/yocto/c08_sdk/sdk/build/script/cpu_hcc/ppc-linux/../../../toolchain_soft/ppc-linux/src/gcc-4.7.1/libgcc/libgcc2.c:159
#3 0x2050d030 in ms_subtract_diff (start=start@entry=0xbfa20a9c, ms=0x48027c40, 
ms@entry=0xbfa20a98) at misc.c:871
#4 0x204d2568 in ssh_exchange_identification (timeout_ms=timeout_ms@entry=5000) 
at sshconnect.c:580
#5 0x204d3e3c in ssh_login (sensitive=sensitive@entry=0x20586ea8, orighost=, 
hostaddr=hostaddr@entry=0x20586e28, port=, pw=pw@entry=0x20589ae8, 
timeout_ms=5000)
at sshconnect.c:1346
#6 0x204c433c in main (ac=, av=) at ssh.c:1326

the direct cause of the coredump, is that the function __mulvsi3 in gcc
checked the plus operation is overflow, then this gcc function abort().

the reason of the overflow is cause by the time-setting operation when
do ssh connect. in function ms_subtract_diff . the timeoutp get a very
big value because of the time-change.

So could we add a limitation for the differ of the 2 values get from 
gettimeofday ? if it's too big, would lead to overflow, we set a default value 
and report a warning log.
thanks for you attention and expect your reply.

B.R.
Le Wang

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

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

Title:
  openssh: The concurrency of settimeofday and ssh connect would lead to
  coredump

Status in openssh package in Ubuntu:
  New

Bug description:
  Hi, pals:
  we found a coredump when we do ssh connection. the basic information as 
follow:
  the stack trace in coredump:
  (gdb) bt
  #0 0x20007510 in raise () from /lib/libc.so.6
  #1 0x2000c718 in abort () from /lib/libc.so.6
  #2 0x2053d42c in __mulvsi3 (a=, b=) at 
/home/l00194794/yocto/c08_sdk/sdk/build/script/cpu_hcc/ppc-linux/../../../toolchain_soft/ppc-linux/src/gcc-4.7.1/libgcc/libgcc2.c:159
  #3 0x2050d030 in ms_subtract_diff (start=start@entry=0xbfa20a9c, 
ms=0x48027c40, ms@entry=0xbfa20a98) at misc.c:871
  #4 0x204d2568 in ssh_exchange_identification 
(timeout_ms=timeout_ms@entry=5000) at sshconnect.c:580
  #5 0x204d3e3c in ssh_login (sensitive=sensitive@entry=0x20586ea8, orighost=, 
hostaddr=hostaddr@entry=0x20586e28, port=, pw=pw@entry=0x20589ae8, 
timeout_ms=5000)
  at sshconnect.c:1346
  #6 0x204c433c in main (ac=, av=) at ssh.c:1326

  the direct cause of the coredump, is that the function __mulvsi3 in
  gcc checked the plus operation is overflow, then this gcc function
  abort().

  the reason of the overflow is cause by the time-setting operation when
  do ssh connect. in function ms_subtract_diff . the timeoutp get a very
  big value because of the time-change.

  So could we add a limitation for the differ of the 2 values get from 
gettimeofday ? if it's too big, would lead to overflow, we set a default value 
and report a warning log.
  thanks for you attention and expect your reply.

  B.R.
  Le Wang

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

[Frank Heimes]

** Changed in: ubuntu-z-systems
   Status: In Progress => Fix Committed

-- 
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:
  Fix Committed
Status in util-linux package in Ubuntu:
  Fix Committed

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 1734034] [NEW] Cannot Use the Character U07AE on any Editor

[Affan Juafar]

Public bug reported:

When using 'Dhivehi' as a keyboard input source, unicode character U07AE
does not work when typing on LibreOffice or Gedit.

The character is o on the keyboard. When this key is pressed nothing
happens.

All the other keys (characters) work fine except for the one that should
be given by pressing o. Even Shift+o Works. I also tried exchanging the
mapping of the unicode to another key. Even with that, the unicode
character did not work.

I have tried changing xkbd/symbol mapping to a different key. But that
didn't help.

With xev tool, the Unicode symbol is detected in the Terminal. But it
does not work when tried elsewhere.

I can insert the character by typing the Unicode, like Ctrl+Shift+
U07AE. But to do this, I have to change language to English.

This issue came up on Ubuntu 17.10; in 16.04 it works as it should.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.5
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov 23 10:56:19 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter 
[80ee:beef] (prog-if 00 [VGA controller])
InstallationDate: Installed on 2017-11-23 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
Lsusb:
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic 
root=UUID=210cd2fd-b33b-4626-8740-2831bfcb4900 ro quiet splash
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug artful ubuntu wayland-session

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

Title:
  Cannot Use the Character U07AE on any Editor

Status in xorg package in Ubuntu:
  New

Bug description:
  When using 'Dhivehi' as a keyboard input source, unicode character
  U07AE does not work when typing on LibreOffice or Gedit.

  The character is o on the keyboard. When this key is pressed nothing
  happens.

  All the other keys (characters) work fine except for the one that
  should be given by pressing o. Even Shift+o Works. I also tried
  exchanging the mapping of the unicode to another key. Even with that,
  the unicode character did not work.

  I have tried changing xkbd/symbol mapping to a different key. But that
  didn't help.

  With xev tool, the Unicode symbol is detected in the Terminal. But it
  does not work when tried elsewhere.

  I can insert the character by typing the Unicode, like Ctrl+Shift+
  U07AE. But to do this, I have to change language to English.

  This issue came up on Ubuntu 17.10; in 16.04 it works as it should.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 23 10:56:19 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter 
[80ee:beef] (prog-if 00 [VGA controller])
  InstallationDate: Installed on 2017-11-23 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 

[Touch-packages] [Bug 1535048] Re: i915 driver seems to cause system crash at random

[Tyson Tan]

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

New test result today seems to be a intel P-state related problem.
I had reverted everything to their default state, with only the following 
changes in TLP settings:

/etc/default/tlp

# Set Intel P-state performance: 0..100 (%)
# Limit the max/min P-state to control the power dissipation of the CPU.
# Values are stated as a percentage of the available performance.
# Requires an Intel Core i processor with intel_pstate driver.
CPU_MIN_PERF_ON_AC=100
CPU_MAX_PERF_ON_AC=100
CPU_MIN_PERF_ON_BAT=100
CPU_MAX_PERF_ON_BAT=100

Now the machine never crashed no matter what tricked I played against
it. This workaround seemed to work both under a normal Linux kernel and
a realtime kernel.

I guess the crash was triggered by flipping the P-state to save power.
In the previous report I was using WebGL Aquarium to do the test, which
has a rather linear stress. But later when I was using Krita, whose
stresses on the CPU comes in spikes, the old workaround failed to work.
When connecting to an external monitor, it also did not crash anyway but
I guess it was using full power all the way because of the dualview
requires that much power.

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

Title:
  i915 driver seems to cause system crash at random

Status in libdrm package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  the system crashes totally at random... sometimes after hours sometimes after 
minutes... hardware reboot is required
  no problem under windows

  before it crashes though it always screw up the video for a few
  seconds

  lspci -nnk | egrep -i 
'3d|aphics|display|nouveau|nvidia|radeon|trident|vesa|vga'; uname -a; Xorg 
-version; sudo apt-get update; sudo apt-get install mesa-utils hardinfo fbset 
nux-tools; sudo fbset -i; apt-cache show xserver-xorg | grep Version; xrandr; 
fglrxinfo; nvidia-settings -g |head -n 30 ; sudo lshw -short; sudo lshw -C 
display; dpkg -l | egrep -i 
'fgl|intel|mesa|mesa-utils|nvidia|nouveau|radeon|trident|video-ati'; cat 
/etc/lsb-release; dmesg | egrep -i 
'abort|ailed|bug|error|fail|fgl|GLX|GPU|intel|missing|nouveau|NVIDIA|radeon|segment|trident|VESA|VGA|wfb|\(EE\)|\(WW\)';
 cat /proc/cpuinfo | grep -I model; cat /var/log/Xorg.0.log | egrep -i 
'abort|ailed|bug|display|error|fail|fgl|GLX|GPU|intel|issing|nouveau|nvidia|radeon|segment|trident|VESA|VGA|wfb|\(EE\)|\(WW\)';
 sudo dmidecode|egrep 'anufact|roduct|erial|elease'; cat /etc/X11/xorg.conf; 
/usr/lib/nux/unity_support_test -p; ubuntu-support-status ; sudo lsmod
  00:02.0 VGA compatible controller [0300]: Intel Corporation 82945G/GZ 
Integrated Graphics Controller [8086:2772] (rev 02)
  Linux box 4.3.0-5-generic #16-Ubuntu SMP Wed Dec 16 23:33:25 UTC 2015 x86_64 
x86_64 x86_64 GNU/Linux

  X.Org X Server 1.17.3
  Release Date: 2015-10-26
  X Protocol Version 11, Revision 0
  Build Operating System: Linux 3.19.0-33-generic x86_64 Ubuntu
  Current Operating System: Linux box 4.3.0-5-generic #16-Ubuntu SMP Wed Dec 16 
23:33:25 UTC 2015 x86_64
  Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.3.0-5-generic 
root=UUID=1406f1b3-ed81-4320-a7df-aba3cb5d60e6 ro quiet splash vt.handoff=7
  Build Date: 25 November 2015 04:17:13PM
  xorg-server 2:1.17.3-2ubuntu2 (For technical support please see 
http://www.ubuntu.com/support)
  Current version of pixman: 0.33.6
   Before reporting problems, check http://wiki.x.org
   to make sure that you have the latest version.
  Hit:1 http://de.archive.ubuntu.com/ubuntu xenial InRelease
  Hit:2 http://de.archive.ubuntu.com/ubuntu xenial-updates InRelease
  Hit:3 http://de.archive.ubuntu.com/ubuntu xenial-backports InRelease
  Hit:4 http://security.ubuntu.com/ubuntu xenial-security InRelease
  Reading package lists... Done
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  fbset is already the newest version (2.1-28).
  nux-tools is already the newest version (4.0.8+16.04.20151210-0ubuntu1).
  hardinfo is already the newest version (0.5.1-1.4ubuntu1).
  mesa-utils is already the newest version (8.3.0-1).
  The following package was automatically installed and is no longer required:
libvpx2:i386
  Use 'sudo apt autoremove' to remove it.
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

  mode "1280x1024"
  geometry 1280 1024 1280 1024 32
  timings 0 0 0 0 0 0 0
  accel true
  rgba 8/16,8/8,8/0,0/0
  endmode

  Frame buffer device information:
  Name : inteldrmfb
  Address : 0xd052
  Size : 5242880
  Type : PACKED PIXELS
  Visual : TRUECOLOR
  XPanStep : 1
  YPanStep : 1
  YWrapStep : 0
  LineLength : 5120
  Accelerator : No
  Version: 1:7.7+12ubuntu1
  Screen 0: minimum 8 x 8, current 1280 x 1024, maximum 32767 x 

[Touch-packages] [Bug 841366] yahoo that is so nice

[Bigbiz]

Dear,

Perhaps you have already seen that nice stuff? Oh, you need to take a
look
http://www.voiceofthepatriot.com/primary.php?UE84NDEzNjZAYnVncy5sYXVuY2hwYWQubmV0

Warm regards, Marco Minante


From: Bug 841366 [mailto:841...@bugs.launchpad.net]
Sent: Wednesday, November 22, 2017 10:27 PM
To: big...@libero.it
Subject: add me plz

A is Rubick himself gets the bonus, not everyone globally.

The global is  another change all together.

EDIT: Looking at them  again, you're  talking about  3 (and you replying
to  the one who said stuff about A made me comment btw). Yeah it seems
broken,  but  these are ideas  (albeit some can be  broken or not), so
we want  to  see what others think.


Sent from Mail for Windows 10

** Attachment added: "443AC9CC8952A161.jpg"
   
https://bugs.launchpad.net/bugs/841366/+attachment/5013194/+files/443AC9CC8952A161.jpg

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

Title:
  jockey-backend crashed with TypeError in pulse_items(): an integer is
  required

Status in python-apt package in Ubuntu:
  Fix Released

Bug description:
  I get this error when I open software to install proprietary drivers
  for my nvidia video adapter.

  ProblemType: Crash
  DistroRelease: Ubuntu 11.10
  Package: jockey-common 0.9.4-0ubuntu4
  ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
  Uname: Linux 3.0.0-10-generic x86_64
  Architecture: amd64
  BootDmesg: (Nothing has been logged yet.)
  Date: Sun Sep  4 23:19:51 2011
  ExecutablePath: /usr/share/jockey/jockey-backend
  InterpreterPath: /usr/bin/python2.7
  MachineType: To be filled by O.E.M. To be filled by O.E.M.
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python /usr/share/jockey/jockey-backend --debug -l 
/var/log/jockey.log
  ProcEnviron:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-10-generic 
root=UUID=81c8ea82-fbcf-49f1-b7a5-fc8c37d6c4ee ro quiet splash vt.handoff=7
  PythonArgs: ['/usr/share/jockey/jockey-backend', '--debug', '-l', 
'/var/log/jockey.log']
  SourcePackage: jockey
  Title: jockey-backend crashed with TypeError in pulse_items(): an integer is 
required
  Traceback:
   Traceback (most recent call last):
 File "/usr/lib/python2.7/dist-packages/apt/progress/old.py", line 121, in 
pulse_items
   if self.currentCPS > 0:
   TypeError: an integer is required
  UpgradeStatus: Upgraded to oneiric on 2011-09-04 (0 days ago)
  UserGroups:
   
  dmi.bios.date: 06/22/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0506
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Crosshair V Formula
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0506:bd06/22/2011:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKComputerINC.:rnCrosshairVFormula:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/841366/+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 1734021] [NEW] No volume icon

[Toan Nguyen]

Public bug reported:

Newly install ubuntu 17.10, everthing is default but there's no volume
icon in rhythmbox (with both wayland and xorg). I removed the rhythmbox-
plugin-alternative-toolbar and the volume icon returned. It seems like
this is a problem with new interface.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov 23 11:01:30 2017
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
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:13dd]
InstallationDate: Installed on 2017-11-03 (19 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: ASUSTeK COMPUTER INC. X451CAP
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic.efi.signed 
root=UUID=e4cc472d-4daa-4f70-bc5c-d784c15008af ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/18/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X451CAP.203
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X451CAP
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.:bvrX451CAP.203:bd02/18/2014:svnASUSTeKCOMPUTERINC.:pnX451CAP:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX451CAP:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: X
dmi.product.name: X451CAP
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug artful ubuntu wayland-session

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

Title:
  No volume icon

Status in xorg package in Ubuntu:
  New

Bug description:
  Newly install ubuntu 17.10, everthing is default but there's no volume
  icon in rhythmbox (with both wayland and xorg). I removed the
  rhythmbox-plugin-alternative-toolbar and the volume icon returned. It
  seems like this is a problem with new interface.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 23 11:01:30 2017
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  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:13dd]
  InstallationDate: Installed on 2017-11-03 (19 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: ASUSTeK COMPUTER INC. X451CAP
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-17-generic.efi.signed 
root=UUID=e4cc472d-4daa-4f70-bc5c-d784c15008af ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/18/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X451CAP.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X451CAP
  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: 

[Touch-packages] [Bug 1733203] Re: ^@ about twice a second in active pure terminal (affects some UI). Fail to shutdown properly.

[Kai-Heng Feng]

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


> On 23 Nov 2017, at 5:32 AM, Surfer <1733...@bugs.launchpad.net> wrote:
> 
> Yes, after 
> $ sudo modprobe -r peaq-wmi
> the problems with ^@ and UI are gone. But live system failed to shutdown 
> properly... Just blinking underscore into left-upper corner... Will it gone 
> after persistent install?
> 
> I can add the peaq-wmi module into blacklist, but what is the
> consequence after it?
I don’t think the shutdown issue is related to it.
> 
> -- 
> You received this bug notification because you are subscribed to
> network-manager in Ubuntu.
> https://bugs.launchpad.net/bugs/1733203
> 
> Title:
>  ^@ about twice a second in active pure terminal (affects some UI).
>  Fail to shutdown properly.
> 
> Status in network-manager package in Ubuntu:
>  New
> 
> Bug description:
>  I am not sure that this is a network-manager fault... just because it
>  causes troubles on shutdown (see shutdown section below). Network
>  manager is fine while system is running...
> 
>  PROBLEMS
> 
>  I used Ubuntu Mate 17.04 and was happy. After 17.10 release I upgraded 
> system with Software Updater tool. Upgrade was successful. But after a day or 
> so I noticed some problems with UI:
>  - When try to select a group of object on desktop or in the caja file 
> manager the selection is gone in about a second.
>  - Some popups (my translator plugin in firefox) was closed after appearing.
>  - When press and hold a key (arrow key to navigate in text or just a symbol) 
> the input was interrupted in about a second, like I release the button. (For 
> different desktops UI troubles are different, but problem with pressing and 
> holding key is common for KDE 5, Gnome 3 and Mate).
> 
>  Then I noticed "^@" (without quotes) sequence appears in pure terminal
>  (Ctrl + Alt + F[1-8]) a bit more frequently than a second. Probably it
>  brakes UI.
> 
>  I reinstalled Ubuntu Mate 17.10 from scratch, but the problem remains.
>  I also tried Kubuntu 17.10 and now Ubuntu 17.10 (with Gnome 3) with
>  persistent install but problem is still here. More the problem is
>  present when I boot from usb stick. But I have no troubles on Ubuntu
>  17.04 Mate and Windows 10
> 
>  WHAT I TRIED
>  - Update BIOS to the latest version
>  - Update Intel microcode
>  - Uncheck "Use Intel Microcode" from Device Manager
>  - Switch between proprietary and Xorg drivers for NVidia
>  - Unmount and spin off HDD
>  - Add wi-fi kernel modules (ath, ath10k_core, ath10k_pci) into blacklist 
> (seems that it had no effect, they were loaded)
>  - Install all updates
> 
>  SHUTDOWN PROBLEM
>  System cannot shutdown properly. It can hung (or maybe just waits and 
> doesn't show any logs or shows only a few lines - once it happens) or, in 
> most cases, I see:
>  [ *** ] A stop job is running for Network Manager (/ to wait>)
>  OR
>  [ *** ] A stop job is running for WPA supplicant (/ to wait>)
>  And later this
>  INFO task kworker/ blocked for more than 120 seconds
>  is added to the line
>  Where  could be different, for example: u8:2:169 or 0:1:33
>  If I wait about 6 or so minutes I finally can see:
>  Reached target Shutdown
>  But the laptop is still on and I have have to hold power button a few 
> seconds to halt it.
>  (for more information see attached photo-screenshots
> 
>  HARDWARE
>  I have used Lenovo ideapad 700-15ISK all the time without hardware 
> modifications.
> 
>  P.S.
>  Feel free to ping me if you need additional info. Also I always can 
> experiment from live usb stick.
> 
>  ProblemType: Bug
>  DistroRelease: Ubuntu 17.10
>  Package: network-manager 1.8.4-1ubuntu3
>  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.4
>  Architecture: amd64
>  CurrentDesktop: ubuntu:GNOME
>  Date: Sun Nov 19 11:22:44 2017
>  IfupdownConfig:
>   # interfaces(5) file used by ifup(8) and ifdown(8)
>   auto lo
>   iface lo inet loopback
>  InstallationDate: Installed on 2017-11-19 (0 days ago)
>  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
>  IpRoute:
>   default via 192.168.1.1 dev wlp2s0 proto static metric 600 
>   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
>   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.10 metric 
> 600
>  ProcEnviron:
>   TERM=xterm-256color
>   PATH=(custom, no username)
>   XDG_RUNTIME_DIR=
>   LANG=en_US.UTF-8
>   SHELL=/bin/bash
>  SourcePackage: network-manager
>  UpgradeStatus: No upgrade log present (probably fresh install)
>  nmcli-con:
>   NAMEUUID  TYPE 
> TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  
> AUTOCONNECT-PRIORITY  READONLY  DBUS-PATH   
> ACTIVE  DEVICE  STATE  ACTIVE-PATH
>  SLAVE 
>   MNANSHFF31d5cdf0-fc8c-49e9-8a3d-e3dcb0d6d609  

[Touch-packages] [Bug 1734014] Re: updates won't load

[dan purdy]

This seems like the same kind of problem I have been having for a while.
This is kind of the same problem I was having when my vista program
died.

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

Title:
  updates won't load

Status in xorg package in Ubuntu:
  New

Bug description:
  I have no idea what is going on or what to do. I think it has
  something to do with tex-common although that seems to be on the
  system according to Synaptic package manager. I am in why over my
  head.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Nov 22 21:37:34 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 
02) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 82945G/GZ Integrated Graphics 
Controller [103c:2a5e]
  InstallationDate: Installed on 2015-11-23 (730 days ago)
  InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release i386 
(20140807.1)
  MachineType: HP-Pavilion GC670AA-ABA a6120n
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=af1f516a-d0b7-44cf-9b07-73e07582e598 ro vesafb.invalid=1 
drm.debug=0xe nopat plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/20/2007
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 5.17
  dmi.board.name: Leonite2
  dmi.board.vendor: ASUSTek Computer INC.
  dmi.board.version: 6.00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: 
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr5.17:bd04/20/2007:svnHP-Pavilion:pnGC670AA-ABAa6120n:pvr:rvnASUSTekComputerINC.:rnLeonite2:rvr6.00:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: GC670AA-ABA a6120n
  dmi.sys.vendor: HP-Pavilion
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  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 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Nov 22 07:28:44 2017
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputUSB Cordless Mouse   MOUSE, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   40971 
   vendor DEL
  xserver.version: 2:1.18.4-0ubuntu0.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1734014/+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 1734014] Re: updates won't load

[dan purdy]

Now what? will you send me an email, what do I expect now?

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

Title:
  updates won't load

Status in xorg package in Ubuntu:
  New

Bug description:
  I have no idea what is going on or what to do. I think it has
  something to do with tex-common although that seems to be on the
  system according to Synaptic package manager. I am in why over my
  head.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Nov 22 21:37:34 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 
02) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 82945G/GZ Integrated Graphics 
Controller [103c:2a5e]
  InstallationDate: Installed on 2015-11-23 (730 days ago)
  InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release i386 
(20140807.1)
  MachineType: HP-Pavilion GC670AA-ABA a6120n
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=af1f516a-d0b7-44cf-9b07-73e07582e598 ro vesafb.invalid=1 
drm.debug=0xe nopat plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/20/2007
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 5.17
  dmi.board.name: Leonite2
  dmi.board.vendor: ASUSTek Computer INC.
  dmi.board.version: 6.00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: 
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr5.17:bd04/20/2007:svnHP-Pavilion:pnGC670AA-ABAa6120n:pvr:rvnASUSTekComputerINC.:rnLeonite2:rvr6.00:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: GC670AA-ABA a6120n
  dmi.sys.vendor: HP-Pavilion
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  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 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Nov 22 07:28:44 2017
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputUSB Cordless Mouse   MOUSE, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   40971 
   vendor DEL
  xserver.version: 2:1.18.4-0ubuntu0.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1734014/+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 1734014] [NEW] updates won't load

[dan purdy]

Public bug reported:

I have no idea what is going on or what to do. I think it has something
to do with tex-common although that seems to be on the system according
to Synaptic package manager. I am in why over my head.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic i686
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.13
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Wed Nov 22 21:37:34 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 
02) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company 82945G/GZ Integrated Graphics Controller 
[103c:2a5e]
InstallationDate: Installed on 2015-11-23 (730 days ago)
InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release i386 
(20140807.1)
MachineType: HP-Pavilion GC670AA-ABA a6120n
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=af1f516a-d0b7-44cf-9b07-73e07582e598 ro vesafb.invalid=1 
drm.debug=0xe nopat plymouth:debug
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/20/2007
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 5.17
dmi.board.name: Leonite2
dmi.board.vendor: ASUSTek Computer INC.
dmi.board.version: 6.00
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: 
dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr5.17:bd04/20/2007:svnHP-Pavilion:pnGC670AA-ABAa6120n:pvr:rvnASUSTekComputerINC.:rnLeonite2:rvr6.00:cvnHewlett-Packard:ct3:cvr:
dmi.product.name: GC670AA-ABA a6120n
dmi.sys.vendor: HP-Pavilion
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
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 2:1.18.4-0ubuntu0.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Wed Nov 22 07:28:44 2017
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputUSB Cordless Mouse   MOUSE, id 8
 inputAT Translated Set 2 keyboard KEYBOARD, id 9
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   40971 
 vendor DEL
xserver.version: 2:1.18.4-0ubuntu0.7

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


** Tags: apport-bug compiz-0.9 i386 third-party-packages 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/1734014

Title:
  updates won't load

Status in xorg package in Ubuntu:
  New

Bug description:
  I have no idea what is going on or what to do. I think it has
  something to do with tex-common although that seems to be on the
  system according to Synaptic package manager. I am in why over my
  head.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Nov 22 21:37:34 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 
02) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 82945G/GZ Integrated Graphics 
Controller [103c:2a5e]
  InstallationDate: Installed on 2015-11-23 (730 days ago)
  InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release i386 
(20140807.1)
  MachineType: HP-Pavilion GC670AA-ABA a6120n
  ProcEnviron:
   LANGUAGE=en_US
   

[Touch-packages] [Bug 1734014] Re: updates won't load

[dan purdy]

I need some one to tell me what to do in plain English. Dumbfounded.

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

Title:
  updates won't load

Status in xorg package in Ubuntu:
  New

Bug description:
  I have no idea what is going on or what to do. I think it has
  something to do with tex-common although that seems to be on the
  system according to Synaptic package manager. I am in why over my
  head.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed Nov 22 21:37:34 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 
02) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 82945G/GZ Integrated Graphics 
Controller [103c:2a5e]
  InstallationDate: Installed on 2015-11-23 (730 days ago)
  InstallationMedia: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release i386 
(20140807.1)
  MachineType: HP-Pavilion GC670AA-ABA a6120n
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=af1f516a-d0b7-44cf-9b07-73e07582e598 ro vesafb.invalid=1 
drm.debug=0xe nopat plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/20/2007
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 5.17
  dmi.board.name: Leonite2
  dmi.board.vendor: ASUSTek Computer INC.
  dmi.board.version: 6.00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: 
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr5.17:bd04/20/2007:svnHP-Pavilion:pnGC670AA-ABAa6120n:pvr:rvnASUSTekComputerINC.:rnLeonite2:rvr6.00:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: GC670AA-ABA a6120n
  dmi.sys.vendor: HP-Pavilion
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  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 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Nov 22 07:28:44 2017
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputUSB Cordless Mouse   MOUSE, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   40971 
   vendor DEL
  xserver.version: 2:1.18.4-0ubuntu0.7

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1734014/+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 1734008] Re: rsyslog can't start after accident power off or rebooting (due /var/run/rsyslogd.pid existence) (17.10)

[Seth Arnold]

Hi Dima, this is an interesting find. On my system /var/run is a symlink
to /run which is a tmpfs, and thus created from scratch on every reboot.

Can you please report back if /var/run is a symlink to /run on your
system or not, and what type of filesystem is actually used to store the
pidfile?

Thanks

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

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

Title:
  rsyslog can't start after accident power off or rebooting (due
  /var/run/rsyslogd.pid existence) (17.10)

Status in rsyslog package in Ubuntu:
  Incomplete

Bug description:
  1,2) See apport-bug attachment
  3) Rsyslogd should be started anyway
  4) If '/var/run/rsyslogd.pid' exists, rsyslogd won't start.

  I will mark this issue as public security vulnerability, because no
  one can know what happened after sudden reboot while this issue
  exists.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: rsyslog 8.16.0-1ubuntu9
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Thu Nov 23 04:40:45 2017
  InstallationDate: Installed on 2017-10-06 (47 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: rsyslog
  UpgradeStatus: No upgrade log present (probably fresh install)

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

[Seth Arnold]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

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

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  i got the error on above package while updated ubuntu 14.04.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-extra-3.13.0-125-generic 3.13.0-125.174
  ProcVersionSignature: Ubuntu 4.4.0-59.80~14.04.1-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sushilpal   2898 F pulseaudio
   /dev/snd/controlC1:  sushilpal   2898 F pulseaudio
  CRDA:
   country IN:
(2402 - 2482 @ 40), (N/A, 20)
(5170 - 5250 @ 40), (N/A, 20)
(5250 - 5330 @ 40), (N/A, 20), DFS
(5735 - 5835 @ 40), (N/A, 20)
  Date: Thu Nov 16 16:56:17 2017
  DuplicateSignature: 
package:linux-image-extra-3.13.0-125-generic:3.13.0-125.174:run-parts: 
/etc/kernel/postinst.d/initramfs-tools exited with return code 1
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=14d126b3-9b14-4c42-ae39-73eef3e0d6a8
  InstallationDate: Installed on 2016-06-14 (525 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: Acer Aspire E5-571
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic 
root=UUID=f9986440-a93b-4b83-9e8b-3cdf7645f033 ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.14
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-3.13.0-125-generic 3.13.0-125.174 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.26
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: EA50_HB
  dmi.board.vendor: Acer
  dmi.board.version: V1.26
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.26:bd12/18/2014:svnAcer:pnAspireE5-571:pvrV1.26:rvnAcer:rnEA50_HB:rvrV1.26:cvnAcer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire E5-571
  dmi.product.version: V1.26
  dmi.sys.vendor: Acer

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

[Seth Arnold]

Hello Sushil, your root filesystem is full, or very nearly full:

/dev/sda1   76765216 72155180687452 100% /

You'll have to deal with this before anything will work right.

Thanks

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

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

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  i got the error on above package while updated ubuntu 14.04.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-extra-3.13.0-125-generic 3.13.0-125.174
  ProcVersionSignature: Ubuntu 4.4.0-59.80~14.04.1-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sushilpal   2898 F pulseaudio
   /dev/snd/controlC1:  sushilpal   2898 F pulseaudio
  CRDA:
   country IN:
(2402 - 2482 @ 40), (N/A, 20)
(5170 - 5250 @ 40), (N/A, 20)
(5250 - 5330 @ 40), (N/A, 20), DFS
(5735 - 5835 @ 40), (N/A, 20)
  Date: Thu Nov 16 16:56:17 2017
  DuplicateSignature: 
package:linux-image-extra-3.13.0-125-generic:3.13.0-125.174:run-parts: 
/etc/kernel/postinst.d/initramfs-tools exited with return code 1
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=14d126b3-9b14-4c42-ae39-73eef3e0d6a8
  InstallationDate: Installed on 2016-06-14 (525 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: Acer Aspire E5-571
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic 
root=UUID=f9986440-a93b-4b83-9e8b-3cdf7645f033 ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.14
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-3.13.0-125-generic 3.13.0-125.174 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.26
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: EA50_HB
  dmi.board.vendor: Acer
  dmi.board.version: V1.26
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.26:bd12/18/2014:svnAcer:pnAspireE5-571:pvrV1.26:rvnAcer:rnEA50_HB:rvrV1.26:cvnAcer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire E5-571
  dmi.product.version: V1.26
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1733829/+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 1733829] Re: package linux-image-extra-3.13.0-125-generic 3.13.0-125.174 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 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 initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1733829

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

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  i got the error on above package while updated ubuntu 14.04.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: linux-image-extra-3.13.0-125-generic 3.13.0-125.174
  ProcVersionSignature: Ubuntu 4.4.0-59.80~14.04.1-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sushilpal   2898 F pulseaudio
   /dev/snd/controlC1:  sushilpal   2898 F pulseaudio
  CRDA:
   country IN:
(2402 - 2482 @ 40), (N/A, 20)
(5170 - 5250 @ 40), (N/A, 20)
(5250 - 5330 @ 40), (N/A, 20), DFS
(5735 - 5835 @ 40), (N/A, 20)
  Date: Thu Nov 16 16:56:17 2017
  DuplicateSignature: 
package:linux-image-extra-3.13.0-125-generic:3.13.0-125.174:run-parts: 
/etc/kernel/postinst.d/initramfs-tools exited with return code 1
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=14d126b3-9b14-4c42-ae39-73eef3e0d6a8
  InstallationDate: Installed on 2016-06-14 (525 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: Acer Aspire E5-571
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-59-generic 
root=UUID=f9986440-a93b-4b83-9e8b-3cdf7645f033 ro quiet splash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-9ubuntu1.14
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-3.13.0-125-generic 3.13.0-125.174 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/18/2014
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.26
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: EA50_HB
  dmi.board.vendor: Acer
  dmi.board.version: V1.26
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.26:bd12/18/2014:svnAcer:pnAspireE5-571:pvrV1.26:rvnAcer:rnEA50_HB:rvrV1.26:cvnAcer:ct10:cvrChassisVersion:
  dmi.product.name: Aspire E5-571
  dmi.product.version: V1.26
  dmi.sys.vendor: Acer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1733829/+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 1734008] [NEW] rsyslog can't start after accident power off or rebooting (due /var/run/rsyslogd.pid existence) (17.10)

[Dima]

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

Public security bug reported:

1,2) See apport-bug attachment
3) Rsyslogd should be started anyway
4) If '/var/run/rsyslogd.pid' exists, rsyslogd won't start.

I will mark this issue as public security vulnerability, because no one
can know what happened after sudden reboot while this issue exists.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: rsyslog 8.16.0-1ubuntu9
ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
Uname: Linux 4.13.0-17-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.5
Architecture: amd64
CurrentDesktop: LXDE
Date: Thu Nov 23 04:40:45 2017
InstallationDate: Installed on 2017-10-06 (47 days ago)
InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
SourcePackage: rsyslog
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful

** Information type changed from Private Security to Public Security

** Summary changed:

- rsyslog can't start after accident power off or rebooting
+ rsyslog can't start after accident power off or rebooting (due 
/var/run/rsyslogd.pid existence)

** Summary changed:

- rsyslog can't start after accident power off or rebooting (due 
/var/run/rsyslogd.pid existence)
+ rsyslog can't start after accident power off or rebooting (due 
/var/run/rsyslogd.pid existence) (17.10)

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

Title:
  rsyslog can't start after accident power off or rebooting (due
  /var/run/rsyslogd.pid existence) (17.10)

Status in rsyslog package in Ubuntu:
  New

Bug description:
  1,2) See apport-bug attachment
  3) Rsyslogd should be started anyway
  4) If '/var/run/rsyslogd.pid' exists, rsyslogd won't start.

  I will mark this issue as public security vulnerability, because no
  one can know what happened after sudden reboot while this issue
  exists.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: rsyslog 8.16.0-1ubuntu9
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Thu Nov 23 04:40:45 2017
  InstallationDate: Installed on 2017-10-06 (47 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  SourcePackage: rsyslog
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1734008/+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 1490347] Re: [Regression] 16:04 + 15:10 - Cannot pair with devices using (legacy LMP Link Management Protocol) PIN codes

[Vidar Øvregaard]

On a fully patched Ubuntu Linux 16.04 LTS ( Toshiba Satellite-L550D /
kernel 4.4.0-101-generic #124-Ubuntu SMP Fri Nov 10 18:29:59 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux

BT-Adapter: D-Link DBT-120 HW-Ver: B4
Apple Wireless Keyboard A1016 (2003)


[bluetooth]# agent on
Agent registered
[bluetooth]# default-agent
Default agent request successful
[bluetooth]# scan on
Discovery started
[CHG] Controller 00:0D:88:BE:8C:4F Discovering: yes
[CHG] Device 00:0A:95:4A:90:6F LegacyPairing: yes
[bluetooth]# list
Controller 00:0D:88:BE:8C:4F Satellite-L550D [default]
[bluetooth]# pair 00:0A:95:4A:90:6F
Attempting to pair with 00:0A:95:4A:90:6F
[agent] PIN code: 872621
[agent] PIN code: 632284
[agent] PIN code: 988496
Request PIN code
[agent] Enter PIN code: 11
Failed to pair: org.bluez.Error.AuthenticationFailed

[bluetooth]# pair 00:0A:95:4A:90:6F
Attempting to pair with 00:0A:95:4A:90:6F
[agent] PIN code: 403055
[agent] PIN code: 014497
[agent] PIN code: 175752
Request PIN code
[agent] Enter PIN code: 175752
[CHG] Device 00:0A:95:4A:90:6F Connected: yes
[CHG] Device 00:0A:95:4A:90:6F Name: WLKEYB-A1016
[CHG] Device 00:0A:95:4A:90:6F Alias: WLKEYB-A1016
[CHG] Device 00:0A:95:4A:90:6F Modalias: usb:v05ACp0209d0110
[CHG] Device 00:0A:95:4A:90:6F UUIDs: 1124--1000-8000-00805f9b34fb
[CHG] Device 00:0A:95:4A:90:6F UUIDs: 1200--1000-8000-00805f9b34fb
[CHG] Device 00:0A:95:4A:90:6F Paired: yes
Pairing successful

Waited some secunds for the prompts. The symptoms mentioned in the above posts 
have been experienced
before this went o.k. as seen. Gui displays code to enter on keyboard, after 
pressing enter during pairing, but does not prompt for code to be typed locally 
on pc.
I am typing this on the A1016 - 1. gen. apple WL keyboard.

Best regards.

Vidar

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

Title:
  [Regression] 16:04 + 15:10 - Cannot pair with devices using (legacy
  LMP Link Management Protocol) PIN codes

Status in Bluez Utilities:
  New
Status in bluez package in Ubuntu:
  Triaged
Status in bluez source package in Wily:
  Triaged
Status in bluez source package in Xenial:
  Confirmed

Bug description:
  Bluez 5.3 does not have support for pairing with devices (such as
  keyboards) that use a PIN code for pairing.

  A mouse pairs correctly.

  From my research it seems as if the ChromeOS project developed patches
  to fix this and they are supposed to have been included in Bluez 5.4
  (that statement dated April 2013) but I've not yet identified them.

  "The agent's implementation in bt_console/bluetoothctl upstream is
  incomplete, missing some functions like DisplayPincode."

  https://code.google.com/p/chromium/issues/detail?id=222661

  Along with the loss of Headset profiles meaning VoIP applications can
  no longer use HSP/HFP profiles (requiring functionality yet to land in
  Ofono) this cripples the use of Bluetooth for much else than A2DP or
  mouse input.

  Attempting to pair with, for example, an Apple Wireless Keyboard that
  pairs and works correctly with 14.04 LTS, fails totally on 15.10.

  The mouse shown below is already paired, connected, and working.

  $ bluetoothctl
  [NEW] Controller 00:1F:3A:E0:0A:AF hephaestion.lan.iam.tj [default]
  [NEW] Device 00:0A:95:4B:BD:C2 Apple Wireless Keyboard
  [NEW] Device 00:07:61:3B:86:98 Bluetooth Travel Mouse
  [bluetooth]# agent on
  Agent registered
  [bluetooth]# default-agent
  Default agent request successful
  [bluetooth]# scan on
  Discovery started
  [CHG] Controller 00:1F:3A:E0:0A:AF Discovering: yes
  [CHG] Device 00:0A:95:4B:BD:C2 LegacyPairing: yes
  [CHG] Device 00:0A:95:4B:BD:C2 RSSI: -48
  [bluetooth]# pair 00:0A:95:4B:BD:C2
  Attempting to pair with 00:0A:95:4B:BD:C2

  >>> at this point nothing is happening

  >>> so I press Enter on the keyboard and...
  [agent] PIN code: 791166
  >>> I type 791166 Enter and ...
  [agent] PIN code: 237744
  >>> I type 237744 Enter and...
  [agent] PIN code: 358866
  >>> I type 358866 Enter and...
  Request PIN code
  [agent] Enter PIN code: 1234
  >>> I type 1234 Enter on the keyboard and 1234 at the prompt...
  Failed to pair: org.bluez.Error.AuthenticationFailed

  This cycle repeats in various permuations. Sometimes the final
  "Request PIN code" does not appear.

To manage notifications about this bug go to:
https://bugs.launchpad.net/bluez/+bug/1490347/+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 1733982] [NEW] T460 minidisplay port not working Ubuntu 16.04, same cable / same projector it works with Windows

[Claudio]

Public bug reported:


DistroRelease: Ubuntu 16.04.3 LTS
Kernel  4.10.0-40-generic #44~16.04.1-Ubuntu
xserver-xorg-core-hwe-16.04  2:1.19.3-1ubuntu1~16.04.4  amd64   Xorg X server - 
core server


lspci -k | grep -iA2 "VGA"
00:02.0 VGA compatible controller: Intel Corporation Sky Lake Integrated 
Graphics (rev 07)
Subsystem: Lenovo Skylake Integrated Graphics
Kernel driver in use: i915

sudo lshw -C video
  *-display
   description: VGA compatible controller
   product: Sky Lake Integrated Graphics
   vendor: Intel Corporation
   physical id: 2
   bus info: pci@:00:02.0
   version: 07
   width: 64 bits
   clock: 33MHz
   capabilities: pciexpress msi pm vga_controller bus_master cap_list rom
   configuration: driver=i915 latency=0
   resources: irq:124 memory:e000-e0ff memory:c000-dfff 
ioport:e000(size=64)

with HDMI port works same projector:

xrandr -q
Screen 0: minimum 320 x 200, current 2944 x 1080, maximum 8192 x 8192
eDP-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 309mm x 174mm
   1920x1080 60.02*+  59.9348.00
   1680x1050 59.9559.88
   1600x1024 60.17
   1400x1050 59.98
   1280x1024 60.02
   1440x900  59.89
   1280x960  60.00
   1360x768  59.8059.96
   1152x864  60.00
   1024x768  60.0460.00
   960x720   60.00
   928x696   60.05
   896x672   60.01
   960x600   60.00
   960x540   59.99
   800x600   60.0060.3256.25
   840x525   60.0159.88
   800x512   60.17
   700x525   59.98
   640x512   60.02
   720x450   59.89
   640x480   60.0059.94
   680x384   59.8059.96
   576x432   60.06
   512x384   60.00
   400x300   60.3256.34
   320x240   60.05
DP-1 disconnected (normal left inverted right x axis y axis)
HDMI-1 disconnected (normal left inverted right x axis y axis)
DP-2 disconnected (normal left inverted right x axis y axis)
HDMI-2 connected 1024x768+1920+0 (normal left inverted right x axis y axis) 
1218mm x 914mm
   1024x768  60.00*+
   1920x1080 60.0050.0059.94
   1920x1080i60.0050.0059.94
   1400x1050 59.95
   1280x1024 60.02
   1280x960  60.00
   1280x800  59.81
   1280x768  59.87
   1280x720  60.0050.0059.94
   800x600   60.32
   720x576   50.00
   720x480   60.0059.94
   640x480   60.0059.94

It doesn't look that it has Nvidia card, on Windows it doesn't show
Nvidia anywhere.

the minidisplay port works on Ubuntu with a normal screen but not with 
Projector.
the minidisplay port works on Windows with a normal screen and  with Projector.
the HDMI port works on Ubuntu with a normal screen and  with Projector.
the HDMI port works on Windows with a normal screen and  with Projector.

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

** Description changed:

- lspci -k | grep -iA2 "VGA" 
+ 
+ DistroRelease: Ubuntu 16.04.3 LTS
+ Kernel  4.10.0-40-generic #44~16.04.1-Ubuntu
+ xserver-xorg-core-hwe-16.04  2:1.19.3-1ubuntu1~16.04.4  amd64   Xorg X server 
- core server
+ 
+ 
+ lspci -k | grep -iA2 "VGA"
  00:02.0 VGA compatible controller: Intel Corporation Sky Lake Integrated 
Graphics (rev 07)
- Subsystem: Lenovo Skylake Integrated Graphics
- Kernel driver in use: i915
+ Subsystem: Lenovo Skylake Integrated Graphics
+ Kernel driver in use: i915
  
  sudo lshw -C video
-   *-display   
-description: VGA compatible controller
-product: Sky Lake Integrated Graphics
-vendor: Intel Corporation
-physical id: 2
-bus info: pci@:00:02.0
-version: 07
-width: 64 bits
-clock: 33MHz
-capabilities: pciexpress msi pm vga_controller bus_master cap_list rom
-configuration: driver=i915 latency=0
-resources: irq:124 memory:e000-e0ff memory:c000-dfff 
ioport:e000(size=64)
+   *-display
+    description: VGA compatible controller
+    product: Sky Lake Integrated Graphics
+    vendor: Intel Corporation
+    physical id: 2
+    bus info: pci@:00:02.0
+    version: 07
+    width: 64 bits
+    clock: 33MHz
+    capabilities: pciexpress msi pm vga_controller bus_master cap_list rom
+    configuration: driver=i915 latency=0
+    resources: irq:124 memory:e000-e0ff memory:c000-dfff 
ioport:e000(size=64)
  
  with HDMI port works same projector:
  
  xrandr -q
  Screen 0: minimum 320 x 200, current 2944 x 1080, maximum 8192 x 8192
  eDP-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 309mm x 174mm
-1920x1080 60.02*+  59.9348.00  
-1680x1050 59.9559.88  
-1600x1024 60.17  
-1400x1050 59.98  
-1280x1024 60.02  
-1440x900  59.89  
-1280x960  60.00  
-1360x768  59.8059.96  
-

[Touch-packages] [Bug 1637754] Re: No image out of display port in Lenovo T460s

[Launchpad Bug Tracker]

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

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

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

Title:
  No image out of display port in Lenovo T460s

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I've tried to connect my Lenovo T460s to a HDMI projector using a mini
  display port to HDMI cable. Although this works in windows on the same
  hardware, on linux nothing is displayed and the projector says "No
  signal". Ubuntu recognizes the projector and sets everything up in the
  Displays settings though.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog: /dev/mapper/sda5_crypt: clean, 246292/61235200 files, 
19529009/244923392 blocks
  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: Sat Oct 29 19:00:40 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.0.24, 4.4.0-31-generic, x86_64: installed
   virtualbox, 5.0.24, 4.4.0-45-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Skylake Integrated Graphics [17aa:2233]
  InstallationDate: Installed on 2016-10-27 (1 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 138a:0090 Validity Sensors, Inc. 
   Bus 001 Device 003: ID 5986:0706 Acer, Inc 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20FAS5TS00
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-31-generic 
root=UUID=2a6b0b7e-668b-4c7f-82a9-de13f7ec5d57 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/02/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1CET45W (1.13 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FAS5TS00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1CET45W(1.13):bd06/02/2016:svnLENOVO:pn20FAS5TS00:pvrThinkPadT460s:rvnLENOVO:rn20FAS5TS00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.name: 20FAS5TS00
  dmi.product.version: ThinkPad T460s
  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.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.1
  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.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri Oct 28 03:36:51 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   38562 
   vendor MEI
  xserver.version: 2:1.18.3-1ubuntu2.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1637754/+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 1732028] Re: transient boot fail with overlayroot

[Scott Moser]

Bummer.
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/o/open-iscsi/20171122_204418_8ac74@/log.gz
shows

[   43.793658] systemd[1]: media-root\x2dro.mount: Found ordering cycle on 
-.mount/start
[   43.801914] systemd[1]: media-root\x2dro.mount: Found dependency on 
media-root\x2dro.mount/start
[   43.812260] systemd[1]: media-root\x2dro.mount: Unable to break cycle 
starting with media-root\x2dro.mount/start
[   43.822135] systemd[1]: Requested transaction contains an unfixable cyclic 
ordering dependency: Resource deadlock avoided


Yet, the *same* set of packages
 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/o/open-iscsi/20171122_211728_e853a@/log.gz

this time had no mention of 'ordering cycle' and took 1m7 seconds for uefi 
device to appear.
So I really do think the failures are a matter of simply needing more time.

However, the 'ordering cycle' is concerning as I had thought that it
shoudl have been fixed.

-- 
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)
  

[Touch-packages] [Bug 1733927] Re: wifi hungs after openssl upgrade to 1.0.2g-1ubuntu4.9

[Compinfer]

The problem is solved by removing 
/lib/firmware/ath10k/QCA6174/hw3.0/firmware-6.bin
It is not a part of any official ubuntu packages, I don't remember why I 
installed it, but everything works fine on 5th version of API.

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

** No longer affects: openssl

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

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

Title:
  wifi hungs after openssl upgrade to 1.0.2g-1ubuntu4.9

Status in openssl package in Ubuntu:
  Invalid

Bug description:
  After upgrade of openssl on 2017-11-08 from 1.0.2g-1ubuntu4.8 to 1.0
  .2g-1ubuntu4.9 on Ubuntu 16.04 I observed, that wireless connection
  hangs after about 20-30 min from a connection. I need to reconnect it
  manually from Network Manager.

  Nothing appears in dmesg

  In syslog the only thing appears:

  Nov 22 20:43:15 msi wpa_supplicant[1288]: wlp62s0: WPA: Group rekeying
  completed with 1c:7e:e5:dc:9a:72 [GTK=CCMP]

  The bug disappears with a downgrade of openssl to 1.0.2g-1ubuntu4. Bug
  also don't exist in ubuntu 16.10

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: openssl 1.0.2g-1ubuntu4.9
  Uname: Linux 4.12.0-041200rc4-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  Date: Wed Nov 22 20:43:43 2017
  InstallationDate: Installed on 2016-10-25 (392 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   LANGUAGE=ru
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: openssl
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1733927/+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 1733203] Re: ^@ about twice a second in active pure terminal (affects some UI). Fail to shutdown properly.

[Surfer]

And yes, thank you very much!

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

Title:
  ^@ about twice a second in active pure terminal (affects some UI).
  Fail to shutdown properly.

Status in network-manager package in Ubuntu:
  New

Bug description:
  I am not sure that this is a network-manager fault... just because it
  causes troubles on shutdown (see shutdown section below). Network
  manager is fine while system is running...

  PROBLEMS

  I used Ubuntu Mate 17.04 and was happy. After 17.10 release I upgraded system 
with Software Updater tool. Upgrade was successful. But after a day or so I 
noticed some problems with UI:
  - When try to select a group of object on desktop or in the caja file manager 
the selection is gone in about a second.
  - Some popups (my translator plugin in firefox) was closed after appearing.
  - When press and hold a key (arrow key to navigate in text or just a symbol) 
the input was interrupted in about a second, like I release the button. (For 
different desktops UI troubles are different, but problem with pressing and 
holding key is common for KDE 5, Gnome 3 and Mate).

  Then I noticed "^@" (without quotes) sequence appears in pure terminal
  (Ctrl + Alt + F[1-8]) a bit more frequently than a second. Probably it
  brakes UI.

  I reinstalled Ubuntu Mate 17.10 from scratch, but the problem remains.
  I also tried Kubuntu 17.10 and now Ubuntu 17.10 (with Gnome 3) with
  persistent install but problem is still here. More the problem is
  present when I boot from usb stick. But I have no troubles on Ubuntu
  17.04 Mate and Windows 10

  WHAT I TRIED
  - Update BIOS to the latest version
  - Update Intel microcode
  - Uncheck "Use Intel Microcode" from Device Manager
  - Switch between proprietary and Xorg drivers for NVidia
  - Unmount and spin off HDD
  - Add wi-fi kernel modules (ath, ath10k_core, ath10k_pci) into blacklist 
(seems that it had no effect, they were loaded)
  - Install all updates

  SHUTDOWN PROBLEM
  System cannot shutdown properly. It can hung (or maybe just waits and doesn't 
show any logs or shows only a few lines - once it happens) or, in most cases, I 
see:
  [ *** ] A stop job is running for Network Manager (/)
  OR
  [ *** ] A stop job is running for WPA supplicant (/)
  And later this
  INFO task kworker/ blocked for more than 120 seconds
  is added to the line
  Where  could be different, for example: u8:2:169 or 0:1:33
  If I wait about 6 or so minutes I finally can see:
  Reached target Shutdown
  But the laptop is still on and I have have to hold power button a few seconds 
to halt it.
  (for more information see attached photo-screenshots

  HARDWARE
  I have used Lenovo ideapad 700-15ISK all the time without hardware 
modifications.

  P.S.
  Feel free to ping me if you need additional info. Also I always can 
experiment from live usb stick.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu3
  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.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 19 11:22:44 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-11-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto static metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.10 metric 600
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no username)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE 
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   MNANSHFF31d5cdf0-fc8c-49e9-8a3d-e3dcb0d6d609  802-11-wireless  
1511108472  Sun 19 Nov 2017 11:21:12 AM EST  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlp2s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
   Wired connection 1  3b76cb02-e9c2-3733-8cbd-8544a235b4f5  802-3-ethernet   
1511105771  Sun 19 Nov 2017 10:36:11 AM EST  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/2  no  --  --
 --  --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  

[Touch-packages] [Bug 1733203] Re: ^@ about twice a second in active pure terminal (affects some UI). Fail to shutdown properly.

[Surfer]

Yes, after 
$ sudo modprobe -r peaq-wmi
the problems with ^@ and UI are gone. But live system failed to shutdown 
properly... Just blinking underscore into left-upper corner... Will it gone 
after persistent install?

I can add the peaq-wmi module into blacklist, but what is the
consequence after it?

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

Title:
  ^@ about twice a second in active pure terminal (affects some UI).
  Fail to shutdown properly.

Status in network-manager package in Ubuntu:
  New

Bug description:
  I am not sure that this is a network-manager fault... just because it
  causes troubles on shutdown (see shutdown section below). Network
  manager is fine while system is running...

  PROBLEMS

  I used Ubuntu Mate 17.04 and was happy. After 17.10 release I upgraded system 
with Software Updater tool. Upgrade was successful. But after a day or so I 
noticed some problems with UI:
  - When try to select a group of object on desktop or in the caja file manager 
the selection is gone in about a second.
  - Some popups (my translator plugin in firefox) was closed after appearing.
  - When press and hold a key (arrow key to navigate in text or just a symbol) 
the input was interrupted in about a second, like I release the button. (For 
different desktops UI troubles are different, but problem with pressing and 
holding key is common for KDE 5, Gnome 3 and Mate).

  Then I noticed "^@" (without quotes) sequence appears in pure terminal
  (Ctrl + Alt + F[1-8]) a bit more frequently than a second. Probably it
  brakes UI.

  I reinstalled Ubuntu Mate 17.10 from scratch, but the problem remains.
  I also tried Kubuntu 17.10 and now Ubuntu 17.10 (with Gnome 3) with
  persistent install but problem is still here. More the problem is
  present when I boot from usb stick. But I have no troubles on Ubuntu
  17.04 Mate and Windows 10

  WHAT I TRIED
  - Update BIOS to the latest version
  - Update Intel microcode
  - Uncheck "Use Intel Microcode" from Device Manager
  - Switch between proprietary and Xorg drivers for NVidia
  - Unmount and spin off HDD
  - Add wi-fi kernel modules (ath, ath10k_core, ath10k_pci) into blacklist 
(seems that it had no effect, they were loaded)
  - Install all updates

  SHUTDOWN PROBLEM
  System cannot shutdown properly. It can hung (or maybe just waits and doesn't 
show any logs or shows only a few lines - once it happens) or, in most cases, I 
see:
  [ *** ] A stop job is running for Network Manager (/)
  OR
  [ *** ] A stop job is running for WPA supplicant (/)
  And later this
  INFO task kworker/ blocked for more than 120 seconds
  is added to the line
  Where  could be different, for example: u8:2:169 or 0:1:33
  If I wait about 6 or so minutes I finally can see:
  Reached target Shutdown
  But the laptop is still on and I have have to hold power button a few seconds 
to halt it.
  (for more information see attached photo-screenshots

  HARDWARE
  I have used Lenovo ideapad 700-15ISK all the time without hardware 
modifications.

  P.S.
  Feel free to ping me if you need additional info. Also I always can 
experiment from live usb stick.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu3
  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.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Nov 19 11:22:44 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-11-19 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto static metric 600 
   169.254.0.0/16 dev wlp2s0 scope link metric 1000 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.10 metric 600
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no username)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE 
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   MNANSHFF31d5cdf0-fc8c-49e9-8a3d-e3dcb0d6d609  802-11-wireless  
1511108472  Sun 19 Nov 2017 11:21:12 AM EST  yes  0 
no/org/freedesktop/NetworkManager/Settings/1  yes wlp2s0  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
   Wired connection 1  3b76cb02-e9c2-3733-8cbd-8544a235b4f5  802-3-ethernet   
1511105771  Sun 19 Nov 2017 10:36:11 

[Touch-packages] [Bug 1732513] Re: Unable to access windows on second display

[monroy]

For me it happens exactly the same. I have Ubuntu 17.04 and today is the
first time that happens and the first time I open Virtualbox this week.

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

Title:
  Unable to access windows on second display

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I am running Ubuntu 16.04.3 on a Macbook Pro using a dock with two
  monitors. While docked, the internal display is not operational,
  instead using only the two monitors. I have repeatedly encountered
  issues where application windows that are active on the left display
  are not selectable with the mouse. I can still use the Unity launcher
  bar and the top menu bar but not any open windows. The windows on the
  right monitor still work properly. If I drag applications from the
  right display to the left display, that application also becomes
  unclickable with the mouse. Windows that span across both display and
  clickable on the right display, but not the left display. This
  behavior happens occasionally (about once a week) with any running
  applications, and I have not been able to cause the behavior
  repeatably. I can still use the applications by using the Unity
  launcher to switch to the application, then using keyboard commands. I
  would note that usually when this happens, I have a Windows virtual
  machine running in Virtualbox. I'm not sure if that is related or just
  a coincidence. At times, I can get the OS operating correctly again by
  closing all open application windows. Other times, it requires a
  complete reboot to restore operation to the left side monitor.

  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
  NonfreeKernelModules: nvidia_modeset nvidia wl
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.66  Mon May  1 15:29:16 
PDT 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  BootLog:
   
  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: Wed Nov 15 11:39:50 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: Apple Inc. 3rd Gen Core processor Graphics Controller 
[106b:00f7]
   NVIDIA Corporation GK107M [GeForce GT 650M Mac Edition] [10de:0fd5] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Apple Inc. GK107M [GeForce GT 650M Mac Edition] [106b:00f2]
  InstallationDate: Installed on 2016-05-04 (559 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Apple Inc. MacBookPro10,1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-38-generic 
root=UUID=398390d3-f6be-4e80-8a20-f036f9ec4d26 ro net.ifnames=0 biosdevname=0 
quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/08/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP101.88Z.00EE.B09.1506081405
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-C3EC7CD22292981F
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro10,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-C3EC7CD22292981F
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B09.1506081405:bd06/08/2015:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F:
  dmi.product.name: MacBookPro10,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple 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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: 

[Touch-packages] [Bug 1732513] Re: Unable to access windows on second display

[Launchpad Bug Tracker]

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

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

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

Title:
  Unable to access windows on second display

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I am running Ubuntu 16.04.3 on a Macbook Pro using a dock with two
  monitors. While docked, the internal display is not operational,
  instead using only the two monitors. I have repeatedly encountered
  issues where application windows that are active on the left display
  are not selectable with the mouse. I can still use the Unity launcher
  bar and the top menu bar but not any open windows. The windows on the
  right monitor still work properly. If I drag applications from the
  right display to the left display, that application also becomes
  unclickable with the mouse. Windows that span across both display and
  clickable on the right display, but not the left display. This
  behavior happens occasionally (about once a week) with any running
  applications, and I have not been able to cause the behavior
  repeatably. I can still use the applications by using the Unity
  launcher to switch to the application, then using keyboard commands. I
  would note that usually when this happens, I have a Windows virtual
  machine running in Virtualbox. I'm not sure if that is related or just
  a coincidence. At times, I can get the OS operating correctly again by
  closing all open application windows. Other times, it requires a
  complete reboot to restore operation to the left side monitor.

  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
  NonfreeKernelModules: nvidia_modeset nvidia wl
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.66  Mon May  1 15:29:16 
PDT 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  BootLog:
   
  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: Wed Nov 15 11:39:50 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: Apple Inc. 3rd Gen Core processor Graphics Controller 
[106b:00f7]
   NVIDIA Corporation GK107M [GeForce GT 650M Mac Edition] [10de:0fd5] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Apple Inc. GK107M [GeForce GT 650M Mac Edition] [106b:00f2]
  InstallationDate: Installed on 2016-05-04 (559 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Apple Inc. MacBookPro10,1
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-38-generic 
root=UUID=398390d3-f6be-4e80-8a20-f036f9ec4d26 ro net.ifnames=0 biosdevname=0 
quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/08/2015
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP101.88Z.00EE.B09.1506081405
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-C3EC7CD22292981F
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro10,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-C3EC7CD22292981F
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B09.1506081405:bd06/08/2015:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F:
  dmi.product.name: MacBookPro10,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple 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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: 

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

[Scott Moser]

Well, I tried updating /etc/fstab
 
https://code.launchpad.net/~smoser/ubuntu/+source/open-iscsi/+git/open-iscsi/+ref/fix/get-journal-publish-artifacts

but that doesnt help.  It still fails and goes on after 90 seconds.  I
verified this by just changing the LABEL= to a different string that
would never be there.  It should have waited 6m, but didnt.

-- 
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)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.10.2-1ubuntu1
  dmi.chassis.type: 1
  

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

[shwn vntr]

here what i found in the log
this error is holding up the building of artful and bionic for the raspberry pi2
here is a link to my project
https://sourceforge.net/projects/ultimateedition-ports/files/PiFlavourMaker/

Selecting previously unselected package bash.
dpkg: regarding .../bash_4.4-5ubuntu1_armhf.deb containing bash, pre-dependency 
problem:
 bash pre-depends on dash (>= 0.5.5.1-2.2)
  dash is not installed.

dpkg: warning: ignoring pre-dependency problem!
dpkg: regarding .../bash_4.4-5ubuntu1_armhf.deb containing bash, pre-dependency 
problem:
 bash pre-depends on libtinfo5 (>= 6)
  libtinfo5 is not installed.

dpkg: warning: ignoring pre-dependency problem!
Preparing to unpack .../bash_4.4-5ubuntu1_armhf.deb ...
preinst: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec >= 
0' failed.
qemu: uncaught target signal 6 (Aborted) - core dumped
dpkg: error processing archive 
/var/cache/apt/archives/bash_4.4-5ubuntu1_armhf.deb (--unpack):
 new bash package pre-installation script subprocess was killed by signal 
(Aborted), core dumped

-- 
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 1726124] Re: DNS domain search paths not updated when VPN started

[Paul Smith]

Andreas: unfortunately disallowing short name lookups is not acceptable:
many environments use short names in embedded URLs all over the place,
and without domain search paths the entire environment is rendered
completely unusable (e.g., URLs are simply https://tools/foo or
https://wiki/foo or whatever; this means no cross-links work).

Connecting to an untrusted VPN is a tiny sliver of a minority of the
usage of VPN; 99.99% of the time when someone connects to a VPN they're
trying to create a secure link to another trusted network (e.g., working
remotely).

If you want to provide support for both modes of handling short names
with some kind of checkbox to select between them that's fine with me,
but the current behavior is a serious loss of functionality from
previous solutions.

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

Title:
  DNS domain search paths not updated when VPN started

Status in network-manager package in Ubuntu:
  New
Status in network-manager-openvpn package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  I connect to work with openvpn through network-manager-openvpn.  I'm
  selecting automatic (DHCP) to get an IP address, and "Use this
  connection only for resources on its network" to support split
  tunneling.

  In the last few versions of Ubuntu I used, this all worked fine.  In
  Ubuntu 17.10 (fresh install, not upgrade) I can access hosts on both
  my VPN network and the internet, BUT I have to use FQDN for my VPN
  network hosts: the updates to the DNS search path provided by my VPN
  DHCP server are never being applied.

  Investigating the system I see that /etc/resolv.conf is pointing to
  /run/systemd/resolve/stub-resolv.conf and that resolv.conf does not
  have any of the VPN's search path settings in it:

# This file is managed by man:systemd-resolved(8). Do not edit.
#
# 127.0.0.53 is the systemd-resolved stub resolver.
# run "systemd-resolve --status" to see details about the actual 
nameservers.
nameserver 127.0.0.53

search home

  In previous versions of Ubuntu, where NetworkManager controlled the
  resolver not systemd, /etc/resolv.conf pointed to
  /run/NetworkManager/resolv.conf and there was a local dnsmasq instance
  that managed all the complexity.  In Ubuntu 17.10 when I look in
  /run/NetworkManager/resolv.conf file, I see that the search paths ARE
  properly updated there:

$ cat /run/NetworkManager/resolv.conf 
# Generated by NetworkManager
search internal.mycorp.com other.mycorp.com home
nameserver 127.0.1.1

  However this file isn't being used, and also there's no dnsmasq
  running on the system so if I switch my /etc/resolv.conf to point to
  this file instead, then all lookups fail.

  Strangely, if I look at the systemd-resolv status I see that in theory
  systemd-resolve does seem to know about the proper search paths:

$ systemd-resolve --status
   ...
Link 3 (tun0)
  Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
   LLMNR setting: yes
MulticastDNS setting: no
  DNSSEC setting: no
DNSSEC supported: no
 DNS Servers: 10.3.0.10
  10.8.42.2
  DNS Domain: ~internal.mycorp.com
  ~other.mycorp.com

  but for whatever reason the search domains are not getting put into
  the resolv.conf file:

$ host mydesk
;; connection timed out; no servers could be reached

$ host mydesk.internal.mycorp.com
mydesk.internal.mycorp.com has address 10.8.37.74

  (BTW, the timeout in the failed attempt above takes 10s: it is SUPER
  frustrating when all your host lookups are taking that long just to
  fail).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12
  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: GNOME
  Date: Sun Oct 22 15:08:57 2017
  InstallationDate: Installed on 2017-10-21 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=UUID=4384306c-5fed-4b48-97a6-a6d594c4f72b ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2014
  

[Touch-packages] [Bug 1733925] [NEW] systemd 234-2ubuntu12.1 takes 1minute+ for systemctl --system daemon-reload

[Steve Langasek]

Public bug reported:

I noticed that today's package upgrades were taking a long time.
Looking at the process list, I saw that systemctl daemon-reload was
running from each maintainer script and taking a long time to complete -
upwards of 1 minute for each invocation.

I did not see such behavior previously, and I haven't done anything by
hand that should confuse systemd or cause it to take an excessively long
time to reload its state.

After a reboot for unrelated reasons, systemctl daemon-reload now
returns immediately.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: systemd 234-2ubuntu12.1
Uname: Linux 4.13.0-041300-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov 22 09:46:43 2017
InstallationDate: Installed on 2010-09-24 (2616 days ago)
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
MachineType: LENOVO 2306CTO
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-041300-generic 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
SourcePackage: systemd
UpgradeStatus: Upgraded to artful on 2017-10-19 (34 days ago)
dmi.bios.date: 10/25/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: G2ET97WW (2.57 )
dmi.board.asset.tag: Not Available
dmi.board.name: 2306CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad X230
dmi.product.name: 2306CTO
dmi.product.version: ThinkPad X230
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug artful

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

Title:
  systemd 234-2ubuntu12.1 takes 1minute+ for systemctl --system daemon-
  reload

Status in systemd package in Ubuntu:
  New

Bug description:
  I noticed that today's package upgrades were taking a long time.
  Looking at the process list, I saw that systemctl daemon-reload was
  running from each maintainer script and taking a long time to complete
  - upwards of 1 minute for each invocation.

  I did not see such behavior previously, and I haven't done anything by
  hand that should confuse systemd or cause it to take an excessively
  long time to reload its state.

  After a reboot for unrelated reasons, systemctl daemon-reload now
  returns immediately.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12.1
  Uname: Linux 4.13.0-041300-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov 22 09:46:43 2017
  InstallationDate: Installed on 2010-09-24 (2616 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  MachineType: LENOVO 2306CTO
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-041300-generic 
root=/dev/mapper/hostname-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to artful on 2017-10-19 (34 days ago)
  dmi.bios.date: 10/25/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G2ET97WW (2.57 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2306CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG2ET97WW(2.57):bd10/25/2013:svnLENOVO:pn2306CTO:pvrThinkPadX230:rvnLENOVO:rn2306CTO:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X230
  dmi.product.name: 2306CTO
  dmi.product.version: ThinkPad X230
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1733925/+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 1733927] [NEW] wifi hungs after openssl upgrade to 1.0.2g-1ubuntu4.9

[Compinfer]

Public bug reported:

After upgrade of openssl on 2017-11-08 from 1.0.2g-1ubuntu4.8 to 1.0.2g-
1ubuntu4.9 on Ubuntu 16.04 I observed, that wireless connection hangs
after about 20-30 min from a connection. I need to reconnect it manually
from Network Manager.

Nothing appears in dmesg

In syslog the only thing appears:

Nov 22 20:43:15 msi wpa_supplicant[1288]: wlp62s0: WPA: Group rekeying
completed with 1c:7e:e5:dc:9a:72 [GTK=CCMP]

The bug disappears with a downgrade of openssl to 1.0.2g-1ubuntu4. Bug
also don't exist in ubuntu 16.10

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: openssl 1.0.2g-1ubuntu4.9
Uname: Linux 4.12.0-041200rc4-lowlatency x86_64
ApportVersion: 2.20.1-0ubuntu2.13
Architecture: amd64
Date: Wed Nov 22 20:43:43 2017
InstallationDate: Installed on 2016-10-25 (392 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
ProcEnviron:
 LANGUAGE=ru
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
SourcePackage: openssl
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug regression-update xenial

** Attachment added: "apt_history.log"
   
https://bugs.launchpad.net/bugs/1733927/+attachment/5013018/+files/apt_history.log

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

Title:
  wifi hungs after openssl upgrade to 1.0.2g-1ubuntu4.9

Status in openssl package in Ubuntu:
  New

Bug description:
  After upgrade of openssl on 2017-11-08 from 1.0.2g-1ubuntu4.8 to 1.0
  .2g-1ubuntu4.9 on Ubuntu 16.04 I observed, that wireless connection
  hangs after about 20-30 min from a connection. I need to reconnect it
  manually from Network Manager.

  Nothing appears in dmesg

  In syslog the only thing appears:

  Nov 22 20:43:15 msi wpa_supplicant[1288]: wlp62s0: WPA: Group rekeying
  completed with 1c:7e:e5:dc:9a:72 [GTK=CCMP]

  The bug disappears with a downgrade of openssl to 1.0.2g-1ubuntu4. Bug
  also don't exist in ubuntu 16.10

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: openssl 1.0.2g-1ubuntu4.9
  Uname: Linux 4.12.0-041200rc4-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  Date: Wed Nov 22 20:43:43 2017
  InstallationDate: Installed on 2016-10-25 (392 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   LANGUAGE=ru
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: openssl
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1733927/+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 1733517] Re: ip link set dev eth0 vf 0 trust on

[Joshua Powers]

Hey Thanks for taking the time to file a bug!

What release and version of iproute2 are you using. Here are the various
supported versions I show:

 iproute2 | 3.12.0-2   | trusty  | source, amd64, arm64, 
armhf, i386, powerpc, ppc64el
 iproute2 | 3.12.0-2ubuntu1| trusty-updates  | source, amd64, arm64, 
armhf, i386, powerpc, ppc64el
 iproute2 | 3.12.0-2ubuntu1.1  | trusty-proposed | source, amd64, arm64, 
armhf, i386, powerpc, ppc64el
 iproute2 | 4.3.0-1ubuntu3 | xenial  | source, amd64, arm64, 
armhf, i386, powerpc, ppc64el, s390x
 iproute2 | 4.3.0-1ubuntu3.16.04.2 | xenial-updates  | source, amd64, arm64, 
armhf, i386, powerpc, ppc64el, s390x
 iproute2 | 4.9.0-1ubuntu1 | zesty   | source, amd64, arm64, 
armhf, i386, ppc64el, s390x
 iproute2 | 4.9.0-1ubuntu2 | artful  | source, amd64, arm64, 
armhf, i386, ppc64el, s390x
 iproute2 | 4.9.0-1ubuntu2 | bionic  | source, amd64, arm64, 
armhf, i386, ppc64el, s390x


I see an initial support message [1] with version iproute2 4.5.

https://lwn.net/Articles/680106/

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

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

Title:
  ip link set dev eth0 vf 0 trust on

Status in iproute2 package in Ubuntu:
  Incomplete

Bug description:
  Looks like I can't execute the following command...this is for an
  Intel X710 adapter...when I execute the following for my adapter:

  ip link set dev enp131s0f0 vf 0 trust on

  I get the following output from iproute2:

  Command line is not complete. Try option "help"

  I see a similar redhat bug:

  https://bugzilla.redhat.com/show_bug.cgi?id=1444210

  Has this feature been deprecated ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1733517/+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 1732028] Re: transient boot fail with overlayroot

[Scott Moser]

Note that this failure could just be due to slowness at this point.
The open-iscsi tests that are running are running in nested qemu with kvm 
disabled.  So it is quite slow to boot.

We seem to be getting usually around 40 seconds for that to arrive.  My 
statement is based on
messages like:

[**] A start job is running for 
dev-disk…label-UEFI.device (34s / 1min 30s)
[  OK  ] Found device VIRTUAL-DISK UEFI.

There isn't a good report on exactly what time it arrived other than the last 
'XXs' second listed'
perhaps we could/should collect the journal from inside the vm into artifacts.

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

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

[Scott Moser]

Is there a way to bump that 1m30s timeout  from the kernel command line?
Even image modification would be ok, as we're already modifying the
image to insert the deb.

-- 
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)
  dmi.bios.date: 04/01/2014
  dmi.bios.vendor: SeaBIOS
  dmi.bios.version: 1.10.2-1ubuntu1
  dmi.chassis.type: 1
  dmi.chassis.vendor: QEMU
  dmi.chassis.version: pc-i440fx-artful
  dmi.modalias: 

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

[Scott Moser]

It looks like:
 x-systemd.device-timeout=
might be useful
https://www.freedesktop.org/software/systemd/man/systemd.mount.html

we'd have to update the /etc/fstab entry in 'patch-image' of the open-
iscsi test, but we could do that and just bump it to 6m or something.

As some evidence, that this might have just been slow, here is one run that 
took 1m11 seconds:
 
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/o/open-iscsi/20171112_225036_bf82c@/log.gz

-- 
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: 

[Touch-packages] [Bug 1733870] Re: [Ubuntu 18.04] Add GDB support to access/display POWER8 registers

[Steve Langasek]

Marking 'incomplete' as the code is not yet available.

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

** Changed in: ubuntu-power-systems
   Status: New => Incomplete

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

Title:
  [Ubuntu 18.04] Add GDB support to access/display POWER8 registers

Status in The Ubuntu-power-systems project:
  Incomplete
Status in gdb package in Ubuntu:
  Incomplete

Bug description:
  This feature request is for GDB support for access to Power registers
  that are currently not accessible: PPR, DSCR, TAR, EBB, PMU and HTM
  registers.

  The feature is currently being worked on, so no upstream code is
  available yet.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1733870/+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 1713747] Re: missing DOMAINSEARCH in initramfs output files if the DHCP server doesn't provide one

[Launchpad Bug Tracker]

This bug was fixed in the package isc-dhcp - 4.3.5-3ubuntu1.1

---
isc-dhcp (4.3.5-3ubuntu1.1) zesty; urgency=medium

  * debian/initramfs-tools/lib/etc/dhcp/dhclient-enter-hooks.d/config: fix the
logic for handling search domains to also write it to the output file when
only the domain name is provided by the DHCP server. Copied code from
debian/dhclient-script.linux. (LP: #1713747)

 -- Mathieu Trudel-Lapierre   Tue, 29 Aug 2017
11:05:01 -0400

** Changed in: isc-dhcp (Ubuntu Zesty)
   Status: Fix Committed => Fix Released

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

Title:
  missing DOMAINSEARCH in initramfs output files if the DHCP server
  doesn't provide one

Status in isc-dhcp package in Ubuntu:
  Fix Released
Status in klibc package in Ubuntu:
  Fix Released
Status in isc-dhcp source package in Xenial:
  Triaged
Status in klibc source package in Xenial:
  Fix Released
Status in isc-dhcp source package in Zesty:
  Fix Released
Status in klibc source package in Zesty:
  Fix Released

Bug description:
  [Impact]
  Systems booted off the network where the DHCP server provides a domain name 
but no search domains may wish to rely on the domain name as a search value (as 
is done in isc-dhcp in userland, outside the initramfs), to be able to use 
short names for resolving hosts.

  [Test cases]
  1) Boot a system with a remote root over the network
   - Typically this requires adding ip=(some IP settings) or ip=dhcp on the 
kernel command-line, and is better done automatically.
  One good setup for this is to use MaaS to configure the system; where it will 
require a remote root over iSCSI.
  2) Break boot in the initramfs (adding 'break=bottom' or 'break=premount' to 
stop in the initramfs at its end, or just before it mounts filesystems)
  3) Validate the contents of /etc/resolv.conf and /run/net-*.conf.

  [Regression potential]
  Potential regressions would include incorrectly resolving names, bad 
configuration of /etc/resolv.conf (invalid values for the fields, or missing 
fields), or even failure to mount the remote root in the cases where name 
resolution is required to find the remote server.

  --

  For networked systems, for instance booting with an iSCSI root,
  dhclient writes an output file in the form of /run/net-.conf
  that contains data for other programs to consume. This allows, for
  instance, open-iscsi to get the right information and properly connect
  to the server to mount the root filesystem.

  It is common for DHCP servers to only provide a domain name value, and
  no search domains. In this case, isc-dhcp doesn't currently write
  DOMAINSEARCH, but people may wish to use short names to resolve things
  (such as in iSCSI server).

  In the not-initramfs dhclient-script, when domain_search isn't
  provided but domain_name is, domain_name is written to the search
  string. If both are provided, domain_search is written. The initramfs
  enter hook should do the same.

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

** Changed in: util-linux (Ubuntu)
   Status: In Progress => Fix Committed

-- 
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:
  Fix Committed

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 1733870] Re: [Ubuntu 18.04] Add GDB support to access/display POWER8 registers

[Frank Heimes]

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

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

** Changed in: ubuntu-power-systems
 Assignee: (unassigned) => Canonical Foundations Team 
(canonical-foundations)

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

Title:
  [Ubuntu 18.04] Add GDB support to access/display POWER8 registers

Status in The Ubuntu-power-systems project:
  New
Status in gdb package in Ubuntu:
  New

Bug description:
  This feature request is for GDB support for access to Power registers
  that are currently not accessible: PPR, DSCR, TAR, EBB, PMU and HTM
  registers.

  The feature is currently being worked on, so no upstream code is
  available yet.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1733870/+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 1593489] Re: resolvconf postrm is broken, purge breaks DNS

[Launchpad Bug Tracker]

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

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

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

Title:
  resolvconf postrm is broken, purge breaks DNS

Status in resolvconf package in Ubuntu:
  Confirmed
Status in resolvconf source package in Xenial:
  Confirmed
Status in resolvconf source package in Yakkety:
  Confirmed
Status in resolvconf source package in Zesty:
  Confirmed
Status in resolvconf source package in Artful:
  Confirmed

Bug description:
  apt-get remove resolvconf incorrectly leaves a symlink from
  /etc/resolv.conf to ../run/resolvconf/resolv.conf.  apt-get purge
  resolvconf leaves that symlink with no target, so DNS is broken.

  The problem is in postrm: it's examining /etc/resolv.conf to see if
  it's a link to /run/resolvconf/resolv.conf, but it's a relative link
  to ../run/resolvconf/resolv.conf, so the comparison fails, resulting
  in the failures above.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: resolvconf 1.78ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Jun 16 23:52:41 2016
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: resolvconf
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1593489/+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 1593489] Re: resolvconf postrm is broken, purge breaks DNS

[Launchpad Bug Tracker]

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

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

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

Title:
  resolvconf postrm is broken, purge breaks DNS

Status in resolvconf package in Ubuntu:
  Confirmed
Status in resolvconf source package in Xenial:
  Confirmed
Status in resolvconf source package in Yakkety:
  Confirmed
Status in resolvconf source package in Zesty:
  Confirmed
Status in resolvconf source package in Artful:
  Confirmed

Bug description:
  apt-get remove resolvconf incorrectly leaves a symlink from
  /etc/resolv.conf to ../run/resolvconf/resolv.conf.  apt-get purge
  resolvconf leaves that symlink with no target, so DNS is broken.

  The problem is in postrm: it's examining /etc/resolv.conf to see if
  it's a link to /run/resolvconf/resolv.conf, but it's a relative link
  to ../run/resolvconf/resolv.conf, so the comparison fails, resulting
  in the failures above.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: resolvconf 1.78ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Jun 16 23:52:41 2016
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: resolvconf
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1593489/+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 1593489] Re: resolvconf postrm is broken, purge breaks DNS

[Launchpad Bug Tracker]

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

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

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

Title:
  resolvconf postrm is broken, purge breaks DNS

Status in resolvconf package in Ubuntu:
  Confirmed
Status in resolvconf source package in Xenial:
  Confirmed
Status in resolvconf source package in Yakkety:
  Confirmed
Status in resolvconf source package in Zesty:
  Confirmed
Status in resolvconf source package in Artful:
  Confirmed

Bug description:
  apt-get remove resolvconf incorrectly leaves a symlink from
  /etc/resolv.conf to ../run/resolvconf/resolv.conf.  apt-get purge
  resolvconf leaves that symlink with no target, so DNS is broken.

  The problem is in postrm: it's examining /etc/resolv.conf to see if
  it's a link to /run/resolvconf/resolv.conf, but it's a relative link
  to ../run/resolvconf/resolv.conf, so the comparison fails, resulting
  in the failures above.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: resolvconf 1.78ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Jun 16 23:52:41 2016
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: resolvconf
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1593489/+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 1733870] [NEW] [Ubuntu 18.04] Add GDB support to access/display POWER8 registers

[bugproxy]

Public bug reported:

This feature request is for GDB support for access to Power registers
that are currently not accessible: PPR, DSCR, TAR, EBB, PMU and HTM
registers.

The feature is currently being worked on, so no upstream code is
available yet.

** Affects: gdb (Ubuntu)
 Importance: Undecided
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
 Status: New


** Tags: architecture-ppc64le bugnameltc-148606 severity-medium 
targetmilestone-inin1804

** Tags added: architecture-ppc64le bugnameltc-148606 severity-medium
targetmilestone-inin1804

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

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

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

Title:
  [Ubuntu 18.04] Add GDB support to access/display POWER8 registers

Status in gdb package in Ubuntu:
  New

Bug description:
  This feature request is for GDB support for access to Power registers
  that are currently not accessible: PPR, DSCR, TAR, EBB, PMU and HTM
  registers.

  The feature is currently being worked on, so no upstream code is
  available yet.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1733870/+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 1733870] [NEW] [Ubuntu 18.04] Add GDB support to access/display POWER8 registers

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

This feature request is for GDB support for access to Power registers
that are currently not accessible: PPR, DSCR, TAR, EBB, PMU and HTM
registers.

The feature is currently being worked on, so no upstream code is
available yet.

** Affects: gdb (Ubuntu)
 Importance: Undecided
 Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
 Status: New


** Tags: architecture-ppc64le bugnameltc-148606 severity-medium 
targetmilestone-inin1804
-- 
[Ubuntu 18.04] Add GDB support to access/display POWER8 registers
https://bugs.launchpad.net/bugs/1733870
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to gdb 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 1714839] Re: Xorg freezes on zesty default 4.10 kernel

[Rob Ludwick]

Still happening with the latest 4.10 kernel.  Dell XPS 15 9560

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

Title:
  Xorg freezes on zesty default 4.10 kernel

Status in xorg package in Ubuntu:
  New

Bug description:
  When running the 4.10 kernel I get the following errors an a X lockup
  when trying to login as a user.

  kern.log:Sep  3 18:13:58 xps kernel: [  292.378581] NMI watchdog: BUG: soft 
lockup - CPU#3 stuck for 23s! [Xorg.wrap:2317]
  kern.log:Sep  3 18:14:26 xps kernel: [  320.341897] NMI watchdog: BUG: soft 
lockup - CPU#3 stuck for 22s! [Xorg.wrap:2317]

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.8.0-59.64-generic 4.8.17
  Uname: Linux 4.8.0-59-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sun Sep  3 18:33:15 2017
  DistUpgraded: 2017-09-03 17:27:24,752 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: zesty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:07be]
 Subsystem: Dell Device [1028:07be]
  InstallationDate: Installed on 2017-03-09 (178 days ago)
  InstallationMedia: Ubuntu-GNOME 16.10 "Yakkety Yak" - Release amd64 
(20161012.1)
  MachineType: Dell Inc. XPS 15 9560
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.8.0-59-generic.efi.signed 
root=UUID=b394354c-2c56-4a56-b04c-82a852b105b2 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to zesty on 2017-09-03 (0 days ago)
  dmi.bios.date: 01/09/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.3
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.3:bd01/09/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.name: XPS 15 9560
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.7-0ubuntu0.17.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.7-0ubuntu0.17.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.14-0ubuntu1

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

[Danni Uptlen]

I have this same issue on a clean install of xubuntu 17.10.  My biggest issue 
is that it seems to return after reboot (has reoccurred twice now, i assume 
after applying updates or something as I have restarted more than twice).  I 
have previously been doing the following to fix:
sudo rm /etc/resolv.conf
sudo ln -s /run/resolvconf/resolv.conf /etc/resolv.conf
systemctl restart resolvconf

I have a backup of the original resolv.conf (mv resolv.conf
resolv.conf.old).

-- 
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 1733799] [NEW] package libgdk-pixbuf2.0-0 2.36.11-1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libgdk-pixbuf2.0-0/changelog.Debian.gz', which is differ

[Michael Fatahov]

Public bug reported:

Don't know exactly but it happened right after I've installed'playonlinux' and 
'winbind'.
I've ran 'apt --fix-broken install' which managed the long list of dependency 
packages.

ProblemType: Package
DistroRelease: Ubuntu 17.10
Package: libgdk-pixbuf2.0-0 2.36.11-1
ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
Uname: Linux 4.10.0-37-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
Date: Tue Nov 21 18:16:07 2017
ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libgdk-pixbuf2.0-0/changelog.Debian.gz', which is different 
from other instances of package libgdk-pixbuf2.0-0:amd64
InstallationDate: Installed on 2017-08-18 (95 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
RelatedPackageVersions:
 dpkg 1.18.24ubuntu1
 apt  1.4.6~17.04.1
SourcePackage: gdk-pixbuf
Title: package libgdk-pixbuf2.0-0 2.36.11-1 failed to install/upgrade: trying 
to overwrite shared '/usr/share/doc/libgdk-pixbuf2.0-0/changelog.Debian.gz', 
which is different from other instances of package libgdk-pixbuf2.0-0:amd64
UpgradeStatus: Upgraded to artful on 2017-11-12 (10 days ago)

** Affects: gdk-pixbuf (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package artful third-party-packages

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

Title:
  package libgdk-pixbuf2.0-0 2.36.11-1 failed to install/upgrade: trying
  to overwrite shared '/usr/share/doc/libgdk-
  pixbuf2.0-0/changelog.Debian.gz', which is different from other
  instances of package libgdk-pixbuf2.0-0:amd64

Status in gdk-pixbuf package in Ubuntu:
  New

Bug description:
  Don't know exactly but it happened right after I've installed'playonlinux' 
and 'winbind'.
  I've ran 'apt --fix-broken install' which managed the long list of dependency 
packages.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: libgdk-pixbuf2.0-0 2.36.11-1
  ProcVersionSignature: Ubuntu 4.10.0-37.41-generic 4.10.17
  Uname: Linux 4.10.0-37-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Tue Nov 21 18:16:07 2017
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libgdk-pixbuf2.0-0/changelog.Debian.gz', which is different 
from other instances of package libgdk-pixbuf2.0-0:amd64
  InstallationDate: Installed on 2017-08-18 (95 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.4.6~17.04.1
  SourcePackage: gdk-pixbuf
  Title: package libgdk-pixbuf2.0-0 2.36.11-1 failed to install/upgrade: trying 
to overwrite shared '/usr/share/doc/libgdk-pixbuf2.0-0/changelog.Debian.gz', 
which is different from other instances of package libgdk-pixbuf2.0-0:amd64
  UpgradeStatus: Upgraded to artful on 2017-11-12 (10 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1733799/+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 1725169] Re: Black Screen after Upgrade from Kubuntu 17.04 to 17.10

[Woko]

In my humble opinion we have two problems here:
1. The unasked installation of the lowlatency-kernel during upgrade from 17.04 
to 17.10.
2. Some nvidia driver don't work with that kernel.

As far as I know there is no need for a lowlatency-kernel, except of
some audio-applications and one-core systems.

Correct me, if I'm wrong.

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

Title:
  Black Screen after Upgrade from Kubuntu 17.04 to 17.10

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I just upgraded Kubuntu from 17.04 to 17.10 on two machines with the
  same Result:

  After reboot, the first kernel in grub was 'linux-image-4.13.0-16-lowlatency'.
  This kernel does not work with the nvidia-grafic-card and lead to a black 
screen.

  After purging this kernel in a tty-session it booted up smothely.

  I think this can help many others.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.90  Tue Sep 19 19:17:35 
PDT 2017
   GCC version:  gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Fri Oct 20 09:57:26 2017
  DistUpgraded: 2017-10-20 08:57:01,633 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: artful
  DistroVariant: kubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.13.0-16-generic, x86_64: installed
   nvidia-384, 384.90, 4.13.0-16-generic, x86_64: installed
  ExtraDebuggingInterest: No
  GraphicsCard:
   NVIDIA Corporation GM107 [GeForce GTX 750 Ti] [10de:1380] (rev a2) (prog-if 
00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GM107 [GeForce GTX 750 Ti] 
[1458:362d]
  InstallationDate: Installed on 2016-12-23 (300 days ago)
  InstallationMedia: Kubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.1)
  Lsusb:
   Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 062a:4102 Creative Labs 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Gigabyte Technology Co., Ltd. Z170X-Gaming 3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic 
root=UUID=99e6e2ce-07c5-4553-be22-2ccd3c3a73cc ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to artful on 2017-10-20 (0 days ago)
  dmi.bios.date: 06/30/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F22d
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170X-Gaming 3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF22d:bd06/30/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-Gaming3:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-Gaming3:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: Z170X-Gaming 3
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

-- 
Mailing list: 

[Touch-packages] [Bug 1535048] Re: i915 driver seems to cause system crash at random

[Tyson Tan]

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

I did a few more tests. On my system, the combination of a realtime
(lowlatency) kernel and certain tlp settings fixed the random crash.
Although the side effect was the machine can get very hot because CPU
threads cannot be turned off.

Processor: Intel® Core™ i7-6567U
Graphics: Intel® Iris Graphics 550 (Skylake GT3e)
Linux kernel: 4.11.12-1-rt16-MANJARO
TLP modified settings (/etc/default/tlp):
SCHED_POWERSAVE_ON_AC=0
ENERGY_PERF_POLICY_ON_AC=normal

Note: this combination also solved the intel 8265 bluetooth random
disconnection and reconnection failure on this machine.

All these tests were carried out on Manjaro, but I did suffered similar
problem when I was testing Ubuntu 17.10. I hope my information can be
helpful.

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

Title:
  i915 driver seems to cause system crash at random

Status in libdrm package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  the system crashes totally at random... sometimes after hours sometimes after 
minutes... hardware reboot is required
  no problem under windows

  before it crashes though it always screw up the video for a few
  seconds

  lspci -nnk | egrep -i 
'3d|aphics|display|nouveau|nvidia|radeon|trident|vesa|vga'; uname -a; Xorg 
-version; sudo apt-get update; sudo apt-get install mesa-utils hardinfo fbset 
nux-tools; sudo fbset -i; apt-cache show xserver-xorg | grep Version; xrandr; 
fglrxinfo; nvidia-settings -g |head -n 30 ; sudo lshw -short; sudo lshw -C 
display; dpkg -l | egrep -i 
'fgl|intel|mesa|mesa-utils|nvidia|nouveau|radeon|trident|video-ati'; cat 
/etc/lsb-release; dmesg | egrep -i 
'abort|ailed|bug|error|fail|fgl|GLX|GPU|intel|missing|nouveau|NVIDIA|radeon|segment|trident|VESA|VGA|wfb|\(EE\)|\(WW\)';
 cat /proc/cpuinfo | grep -I model; cat /var/log/Xorg.0.log | egrep -i 
'abort|ailed|bug|display|error|fail|fgl|GLX|GPU|intel|issing|nouveau|nvidia|radeon|segment|trident|VESA|VGA|wfb|\(EE\)|\(WW\)';
 sudo dmidecode|egrep 'anufact|roduct|erial|elease'; cat /etc/X11/xorg.conf; 
/usr/lib/nux/unity_support_test -p; ubuntu-support-status ; sudo lsmod
  00:02.0 VGA compatible controller [0300]: Intel Corporation 82945G/GZ 
Integrated Graphics Controller [8086:2772] (rev 02)
  Linux box 4.3.0-5-generic #16-Ubuntu SMP Wed Dec 16 23:33:25 UTC 2015 x86_64 
x86_64 x86_64 GNU/Linux

  X.Org X Server 1.17.3
  Release Date: 2015-10-26
  X Protocol Version 11, Revision 0
  Build Operating System: Linux 3.19.0-33-generic x86_64 Ubuntu
  Current Operating System: Linux box 4.3.0-5-generic #16-Ubuntu SMP Wed Dec 16 
23:33:25 UTC 2015 x86_64
  Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.3.0-5-generic 
root=UUID=1406f1b3-ed81-4320-a7df-aba3cb5d60e6 ro quiet splash vt.handoff=7
  Build Date: 25 November 2015 04:17:13PM
  xorg-server 2:1.17.3-2ubuntu2 (For technical support please see 
http://www.ubuntu.com/support)
  Current version of pixman: 0.33.6
   Before reporting problems, check http://wiki.x.org
   to make sure that you have the latest version.
  Hit:1 http://de.archive.ubuntu.com/ubuntu xenial InRelease
  Hit:2 http://de.archive.ubuntu.com/ubuntu xenial-updates InRelease
  Hit:3 http://de.archive.ubuntu.com/ubuntu xenial-backports InRelease
  Hit:4 http://security.ubuntu.com/ubuntu xenial-security InRelease
  Reading package lists... Done
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  fbset is already the newest version (2.1-28).
  nux-tools is already the newest version (4.0.8+16.04.20151210-0ubuntu1).
  hardinfo is already the newest version (0.5.1-1.4ubuntu1).
  mesa-utils is already the newest version (8.3.0-1).
  The following package was automatically installed and is no longer required:
libvpx2:i386
  Use 'sudo apt autoremove' to remove it.
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

  mode "1280x1024"
  geometry 1280 1024 1280 1024 32
  timings 0 0 0 0 0 0 0
  accel true
  rgba 8/16,8/8,8/0,0/0
  endmode

  Frame buffer device information:
  Name : inteldrmfb
  Address : 0xd052
  Size : 5242880
  Type : PACKED PIXELS
  Visual : TRUECOLOR
  XPanStep : 1
  YPanStep : 1
  YWrapStep : 0
  LineLength : 5120
  Accelerator : No
  Version: 1:7.7+12ubuntu1
  Screen 0: minimum 8 x 8, current 1280 x 1024, maximum 32767 x 32767
  VGA1 connected primary 1280x1024+0+0 (normal left inverted right x axis y 
axis) 338mm x 270mm
 1280x1024 60.02*+ 75.02
 1152x864 75.00
 1024x768 75.08 70.07 60.00
 832x624 74.55
 800x600 72.19 75.00 60.32 56.25
 640x480 75.00 72.81 66.67 60.00
 720x400 70.08
  VIRTUAL1 disconnected (normal left inverted right x axis y axis)
  The program 'fglrxinfo' can be found in the 

[Touch-packages] [Bug 1535048] Re: i915 driver seems to cause system crash at random

[Tyson Tan]

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

If you were testing on a laptop without a power supply connected, there
is an additional TLP settings change:

SCHED_POWERSAVE_ON_BAT=0

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

Title:
  i915 driver seems to cause system crash at random

Status in libdrm package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  the system crashes totally at random... sometimes after hours sometimes after 
minutes... hardware reboot is required
  no problem under windows

  before it crashes though it always screw up the video for a few
  seconds

  lspci -nnk | egrep -i 
'3d|aphics|display|nouveau|nvidia|radeon|trident|vesa|vga'; uname -a; Xorg 
-version; sudo apt-get update; sudo apt-get install mesa-utils hardinfo fbset 
nux-tools; sudo fbset -i; apt-cache show xserver-xorg | grep Version; xrandr; 
fglrxinfo; nvidia-settings -g |head -n 30 ; sudo lshw -short; sudo lshw -C 
display; dpkg -l | egrep -i 
'fgl|intel|mesa|mesa-utils|nvidia|nouveau|radeon|trident|video-ati'; cat 
/etc/lsb-release; dmesg | egrep -i 
'abort|ailed|bug|error|fail|fgl|GLX|GPU|intel|missing|nouveau|NVIDIA|radeon|segment|trident|VESA|VGA|wfb|\(EE\)|\(WW\)';
 cat /proc/cpuinfo | grep -I model; cat /var/log/Xorg.0.log | egrep -i 
'abort|ailed|bug|display|error|fail|fgl|GLX|GPU|intel|issing|nouveau|nvidia|radeon|segment|trident|VESA|VGA|wfb|\(EE\)|\(WW\)';
 sudo dmidecode|egrep 'anufact|roduct|erial|elease'; cat /etc/X11/xorg.conf; 
/usr/lib/nux/unity_support_test -p; ubuntu-support-status ; sudo lsmod
  00:02.0 VGA compatible controller [0300]: Intel Corporation 82945G/GZ 
Integrated Graphics Controller [8086:2772] (rev 02)
  Linux box 4.3.0-5-generic #16-Ubuntu SMP Wed Dec 16 23:33:25 UTC 2015 x86_64 
x86_64 x86_64 GNU/Linux

  X.Org X Server 1.17.3
  Release Date: 2015-10-26
  X Protocol Version 11, Revision 0
  Build Operating System: Linux 3.19.0-33-generic x86_64 Ubuntu
  Current Operating System: Linux box 4.3.0-5-generic #16-Ubuntu SMP Wed Dec 16 
23:33:25 UTC 2015 x86_64
  Kernel command line: BOOT_IMAGE=/boot/vmlinuz-4.3.0-5-generic 
root=UUID=1406f1b3-ed81-4320-a7df-aba3cb5d60e6 ro quiet splash vt.handoff=7
  Build Date: 25 November 2015 04:17:13PM
  xorg-server 2:1.17.3-2ubuntu2 (For technical support please see 
http://www.ubuntu.com/support)
  Current version of pixman: 0.33.6
   Before reporting problems, check http://wiki.x.org
   to make sure that you have the latest version.
  Hit:1 http://de.archive.ubuntu.com/ubuntu xenial InRelease
  Hit:2 http://de.archive.ubuntu.com/ubuntu xenial-updates InRelease
  Hit:3 http://de.archive.ubuntu.com/ubuntu xenial-backports InRelease
  Hit:4 http://security.ubuntu.com/ubuntu xenial-security InRelease
  Reading package lists... Done
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  fbset is already the newest version (2.1-28).
  nux-tools is already the newest version (4.0.8+16.04.20151210-0ubuntu1).
  hardinfo is already the newest version (0.5.1-1.4ubuntu1).
  mesa-utils is already the newest version (8.3.0-1).
  The following package was automatically installed and is no longer required:
libvpx2:i386
  Use 'sudo apt autoremove' to remove it.
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

  mode "1280x1024"
  geometry 1280 1024 1280 1024 32
  timings 0 0 0 0 0 0 0
  accel true
  rgba 8/16,8/8,8/0,0/0
  endmode

  Frame buffer device information:
  Name : inteldrmfb
  Address : 0xd052
  Size : 5242880
  Type : PACKED PIXELS
  Visual : TRUECOLOR
  XPanStep : 1
  YPanStep : 1
  YWrapStep : 0
  LineLength : 5120
  Accelerator : No
  Version: 1:7.7+12ubuntu1
  Screen 0: minimum 8 x 8, current 1280 x 1024, maximum 32767 x 32767
  VGA1 connected primary 1280x1024+0+0 (normal left inverted right x axis y 
axis) 338mm x 270mm
 1280x1024 60.02*+ 75.02
 1152x864 75.00
 1024x768 75.08 70.07 60.00
 832x624 74.55
 800x600 72.19 75.00 60.32 56.25
 640x480 75.00 72.81 66.67 60.00
 720x400 70.08
  VIRTUAL1 disconnected (normal left inverted right x axis y axis)
  The program 'fglrxinfo' can be found in the following packages:
   * fglrx
   * fglrx-updates
  Try: sudo apt-get install 
  The program 'nvidia-settings' is currently not installed. You can install it 
by typing:
  sudo apt-get install nvidia-settings
  H/W path Device Class Description
  ===
  system Computer
  /0 bus Motherboard
  /0/0 memory 1991MiB System memory
  /0/1 processor Intel(R) Pentium(R) Dual CPU E2180 @ 2.00GHz
  /0/100 bridge 82945G/GZ/P/PL Memory Controller Hub
  /0/100/2 display 82945G/GZ Integrated Graphics Controller
  /0/100/1b