[Touch-packages] [Bug 1753576] Re: GDM freeze

[Launchpad Bug Tracker]

[Expired for gdm3 (Ubuntu) because there has been no activity for 60
days.]

** Changed in: gdm3 (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  GDM freeze

Status in gdm3 package in Ubuntu:
  Expired
Status in gnome-shell package in Ubuntu:
  Expired
Status in xorg package in Ubuntu:
  Expired

Bug description:
  Here is what I know so far:

  After rebooting this morning on Bionic (after receiving the gnome
  theme updates, I think), upon reboot the CPU pegs and the greeter is
  never displayed (there is a graphics system running, but I'm not sure
  what it's doing). My num lock / caps lock keys work, but the touchpad
  on the laptop does nothing to the mouse.

  If I boot with nomodeset, greeter does not freeze.

  Finally, in either case, I am now unable to use my external monitor,
  which worked fine before (connected over a USB-C to HDMI dongle).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Mon Mar  5 11:47:53 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: This is the first time
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:3800]
  InstallationDate: Installed on 2015-12-17 (809 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  MachineType: LENOVO 80MK
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic 
root=UUID=c0742e7a-578f-4be5-bd9e-05b9e92f5b00 ro noprompt persistent quiet 
splash nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN34WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0K45914 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 900-13ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN34WW:bd10/29/2015:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0K45914WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80MK
  dmi.product.version: Lenovo YOGA 900-13ISK
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  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+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Mar  5 11:17:58 2018
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1753576/+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 1753576] Re: GDM freeze

[Launchpad Bug Tracker]

[Expired for gnome-shell (Ubuntu) because there has been no activity for
60 days.]

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  GDM freeze

Status in gdm3 package in Ubuntu:
  Expired
Status in gnome-shell package in Ubuntu:
  Expired
Status in xorg package in Ubuntu:
  Expired

Bug description:
  Here is what I know so far:

  After rebooting this morning on Bionic (after receiving the gnome
  theme updates, I think), upon reboot the CPU pegs and the greeter is
  never displayed (there is a graphics system running, but I'm not sure
  what it's doing). My num lock / caps lock keys work, but the touchpad
  on the laptop does nothing to the mouse.

  If I boot with nomodeset, greeter does not freeze.

  Finally, in either case, I am now unable to use my external monitor,
  which worked fine before (connected over a USB-C to HDMI dongle).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Mon Mar  5 11:47:53 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: This is the first time
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:3800]
  InstallationDate: Installed on 2015-12-17 (809 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  MachineType: LENOVO 80MK
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic 
root=UUID=c0742e7a-578f-4be5-bd9e-05b9e92f5b00 ro noprompt persistent quiet 
splash nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN34WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0K45914 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 900-13ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN34WW:bd10/29/2015:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0K45914WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80MK
  dmi.product.version: Lenovo YOGA 900-13ISK
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  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+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Mar  5 11:17:58 2018
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1753576/+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 1753059] Re: package ntp 1:4.2.8p10+dfsg-5ubuntu3.2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139

[Launchpad Bug Tracker]

[Expired for ntp (Ubuntu) because there has been no activity for 60
days.]

** Changed in: ntp (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  package ntp 1:4.2.8p10+dfsg-5ubuntu3.2 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 139

Status in ntp package in Ubuntu:
  Expired

Bug description:
  Issue with package install was reported by system after using Software
  Updater to install new updates on Lubuntu 17.10.  Equipment is a Dell
  Optiplex GX620.

  ProblemType: Package
  DistroRelease: Ubuntu 17.10
  Package: ntp 1:4.2.8p10+dfsg-5ubuntu3.2
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Sat Mar  3 02:32:57 2018
  DuplicateSignature:
   package:ntp:1:4.2.8p10+dfsg-5ubuntu3.2
   Installing new version of config file /etc/apparmor.d/usr.sbin.ntpd ...
   Segmentation fault (core dumped)
   dpkg: error processing package ntp (--configure):
subprocess installed post-installation script returned error exit status 139
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 139
  InstallationDate: Installed on 2017-12-30 (62 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic 
root=UUID=f42c87eb-f326-4389-a256-d2a9d596508e ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.18.24ubuntu1
   apt  1.5.1
  SourcePackage: ntp
  Title: package ntp 1:4.2.8p10+dfsg-5ubuntu3.2 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 139
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1753059/+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 1753576] Re: GDM freeze

[Launchpad Bug Tracker]

[Expired for xorg (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  GDM freeze

Status in gdm3 package in Ubuntu:
  Expired
Status in gnome-shell package in Ubuntu:
  Expired
Status in xorg package in Ubuntu:
  Expired

Bug description:
  Here is what I know so far:

  After rebooting this morning on Bionic (after receiving the gnome
  theme updates, I think), upon reboot the CPU pegs and the greeter is
  never displayed (there is a graphics system running, but I'm not sure
  what it's doing). My num lock / caps lock keys work, but the touchpad
  on the laptop does nothing to the mouse.

  If I boot with nomodeset, greeter does not freeze.

  Finally, in either case, I am now unable to use my external monitor,
  which worked fine before (connected over a USB-C to HDMI dongle).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Mon Mar  5 11:47:53 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: This is the first time
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo Skylake GT2 [HD Graphics 520] [17aa:3800]
  InstallationDate: Installed on 2015-12-17 (809 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 
(20151021)
  MachineType: LENOVO 80MK
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-10-generic 
root=UUID=c0742e7a-578f-4be5-bd9e-05b9e92f5b00 ro noprompt persistent quiet 
splash nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C6CN34WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: VIUU4
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0K45914 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo YOGA 900-13ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrC6CN34WW:bd10/29/2015:svnLENOVO:pn80MK:pvrLenovoYOGA900-13ISK:rvnLENOVO:rnVIUU4:rvrSDK0K45914WIN:cvnLENOVO:ct10:cvrLenovoYOGA900-13ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80MK
  dmi.product.version: Lenovo YOGA 900-13ISK
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.90-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2
  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+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Mar  5 11:17:58 2018
  xserver.configfile: default
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1753576/+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 1768970] Re: Bionic: ubuntu-bug / apport not present

[Walter Lapchynski]

Lubuntu Next was never officially released, even though we had
beta/alpha versions. Additionally, the idea of having both a LXDE and
LXQt image is something we will not be continuing for the Cosmic cycle.
Instead, we will be switching over to LXQt entirely. It will most
certainly have apport in it, though we will need to do some packaging
work on the Qt frontend (apport-kde) as it's a little less Qt and a
little more KDE. That said, I've co-opted this bug for that purpose.

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

** Changed in: apport (Ubuntu)
   Importance: Undecided => High

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

** Changed in: apport (Ubuntu)
 Assignee: (unassigned) => Simon Quigley (tsimonq2)

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

Title:
  Bionic: ubuntu-bug / apport not present

Status in Lubuntu Next:
  Won't Fix
Status in apport package in Ubuntu:
  Triaged

Bug description:
  [I am not sure if apport was present in the previous (17.10) Lubuntu
  Next, or that as now, I had to install it...]

  I wished to report a bug, as I have often done before, and used the terminal 
to invoke ubuntu-bug.
  I was informed that I needed to install apport to gain that command.

  I did so, but then wondered if apport's absence was a mistake, or an
  intentional decision to omit the  package...

  The ability to report crashes/bugs seems like such an obvious and
  necessary thing to include, for any distro...

To manage notifications about this bug go to:
https://bugs.launchpad.net/lubuntu-next/+bug/1768970/+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 1572061] Re: login sessions hangs in lxc

[Stanislav Sinyagin]

looks like rsyslogd is the solution:
https://lists.linuxcontainers.org/pipermail/lxc-users/2015-March/008657.html

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

Title:
  login sessions hangs in lxc

Status in lxc package in Ubuntu:
  Expired

Bug description:
  login to lxc container hangs after login prompt. This happends to randomly 
lxc container while other containers on same host work as expected. 
  Several protocols affected,  ssh, dovecot & smtp for example. DNS config is 
ok. lxc-attach -n name works and I'm able to reach outside network, do 
resolving etc.
  if I do a lxc-stop and start the container works again. after a day or two  
samething occurs again to a random container on the same host.
   Could it be some kind of apparmor blocking ?

  
  HostOs 
  Description:Ubuntu 16.04 LTS
  Release:16.04

  network mode

  iface br0 inet static
  bridge_ports eno1
   address x.x.x.x
  netmask 255.255.255.0
  network x.x.x.x
  broadcast x.x.x.x
  gateway x.x.x.x
  dns-nameservers x.x.x.x
  dns-search domain.com

  lxc-os ubuntu xenial &  debian jessie

  configured with static ip

  best regards
  Bjorn

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1572061/+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 1572061] Re: login sessions hangs in lxc

[Stanislav Sinyagin]

I have exactly the same problem on my host. Host OS: Debian 8.10.
Container OS: Debian 9.4

I started "/usr/sbin/sshd -d  -p 8022", and when I connected to it from
another host, the process has hung with the latest log message:

debug1: rexec start in 5 out 5 newsock 5 pipe -1 sock 8

Also strace shows a similar line:

# strace -p 12014
strace: Process 12014 attached
sendto(3, "<39>May  6 02:42:08 sshd[12014]:"..., 94, MSG_NOSIGNAL, NULL, 0

Then while this was hanging, I did "apt-get remove inetutils-syslogd",
and the SSH session immediately went through.

But RDP client still cannot connect to xrdp running in this container.
I'll keep watching it after a reboot.

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

Title:
  login sessions hangs in lxc

Status in lxc package in Ubuntu:
  Expired

Bug description:
  login to lxc container hangs after login prompt. This happends to randomly 
lxc container while other containers on same host work as expected. 
  Several protocols affected,  ssh, dovecot & smtp for example. DNS config is 
ok. lxc-attach -n name works and I'm able to reach outside network, do 
resolving etc.
  if I do a lxc-stop and start the container works again. after a day or two  
samething occurs again to a random container on the same host.
   Could it be some kind of apparmor blocking ?

  
  HostOs 
  Description:Ubuntu 16.04 LTS
  Release:16.04

  network mode

  iface br0 inet static
  bridge_ports eno1
   address x.x.x.x
  netmask 255.255.255.0
  network x.x.x.x
  broadcast x.x.x.x
  gateway x.x.x.x
  dns-nameservers x.x.x.x
  dns-search domain.com

  lxc-os ubuntu xenial &  debian jessie

  configured with static ip

  best regards
  Bjorn

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1572061/+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 1765911] Re: Major performance regression from Ubuntu 17.10 with i915

[Jacob Zimmermann]

UPDATE: I installed kernel 4.16.7 from http://kernel.ubuntu.com/~kernel-
ppa/mainline/ and things get much better. Not as good as it was on 17.10
but largely usable. Some regression in the i915 driver must have
occurred in 4.15 and now it's catching up again apparently.

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

Title:
  Major performance regression from Ubuntu 17.10 with i915

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Desktop performance on my laptop (Intel HD 520, driver: i915) used to
  be generally good on previous Ubuntu releases but on 18.04, there is a
  VERY noticeable regression. Moving windows around in GNOME is choppy
  and tearing. It gets dramatic after the laptop resumes from suspend,
  GNOME drops to literally ~1-2 FPS. Logging out and restarting the
  session usually fixes the problem in that it restores the barely
  acceptable performance level prior to suspend.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-15.16-lowlatency 4.15.15
  Uname: Linux 4.15.0-15-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 21 16:04:38 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] 
[103c:8079]
   Advanced Micro Devices, Inc. [AMD/ATI] Opal XT [Radeon R7 M265] [1002:6604] 
(rev 81) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Opal XT [Radeon R7 M265] [103c:814f]
  InstallationDate: Installed on 2018-04-03 (18 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180402)
  MachineType: HP HP EliteBook 850 G3
  ProcKernelCmdLine: BOOT_IMAGE=/bionic/vmlinuz-4.15.0-15-lowlatency.efi.signed 
root=UUID=b6480aee-7c63-4ce4-9e8d-cdbef768b982 ro 
rootflags=subvol=@,relatime,autodefrag,space_cache quiet splash 
module.sig_enforce=1 intel_pstate=skylake_hwp vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/31/2016
  dmi.bios.vendor: HP
  dmi.bios.version: N75 Ver. 01.10
  dmi.board.name: 8079
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 85.6F
  dmi.chassis.asset.tag: 5CG6351LQL
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN75Ver.01.10:bd07/31/2016:svnHP:pnHPEliteBook850G3:pvr:rvnHP:rn8079:rvrKBCVersion85.6F:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook 850 G3
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1765911/+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 1768906] Re: Xorg crash

[Cyrus Harmon]

** Package changed: xorg (Ubuntu) => gdm (Ubuntu)

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

Title:
  Xorg crash

Status in gdm package in Ubuntu:
  Confirmed

Bug description:
  When attempting to log in to a newly updated bionic beaver via the
  display manager (I think this is the right term), I immediately see a
  crash, a return to the user selection/login screen and a no-longer
  functioning keyboard and mouse. This happens both with the proprietary
  driver installed drivers and with the apt installed nvidia-driver-396.

  some interesting tidbits from the syslog file are:

  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) NVIDIA(GPU-0): 
Failed to acquire modesetting permission.
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) NVIDIA(0): 
Failing initialization of X screen 0
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) UnloadModule: 
"nvidia"
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) 
UnloadSubModule: "wfb"
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) 
UnloadSubModule: "fb"
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) Screen(s) 
found, but none have a usable configuration.
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE)
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: Fatal server error:
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) no screens 
found(EE)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17
  Uname: Linux 4.15.0-20-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .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  396.24  Thu Apr 26 00:10:09 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu May  3 09:28:59 2018
  DistUpgraded: 2018-05-02 07:25:10,524 DEBUG failed to SystemUnLock() (E:Not 
locked)
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 396.24, 4.15.0-20-lowlatency, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GK104 [GeForce GTX 770] [10de:1184] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. GK104 [GeForce GTX 770] [3842:2774]
  MachineType: ASUS All Series
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-lowlatency 
root=UUID=f308f075-bd97-4230-9d24-3ab727b0036b ro splash quiet nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to bionic on 2018-05-02 (1 days ago)
  dmi.bios.date: 08/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1603
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MAXIMUS VI GENE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1603:bd08/15/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIGENE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Thu May  3 09:20:03 2018
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu4

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

-- 
Mailing list: 

[Touch-packages] [Bug 1769403] [NEW] USB devices (trackball and PS2-to-usb keyboard) freeze in Ubuntu Mate 16.04.4 , and DELL latitude

[KP]

Public bug reported:

Hi,

I am facing the problem that is similar to the one described in the
thread: https://ubuntuforums.org/showthread.php?t=2342985

Laptop (Dell Latitude 6420) randomly stops responding to the usb
Trackball and Keyboard. Unplugging & plugging them back into a different
port does not fix the problem. Sometimes the problem is fixed after
rebooting or suspending the laptopo, then turning it on; but the problem
re-appears almost immediately - after 10".

The problem is related to the Logitech trackman wheel & Mircosoft PS2
Keyboard, both are old.

Command "lsusb" for the 2 devices gives:
Bus 002 Device 005: ID 046d:c404 Logitech, Inc. TrackMan Wheel
Bus 002 Device 006: ID 0a81:0205 Chesen Electronics Corp. PS/2 Keyboard+Mouse 
Adapter

Command "tlp-stat -u" for the 2 devices gives:
Bus 002 Device 005 ID 046d:c404 control = on,   autosuspend_delay_ms = -1000 -- 
Logitech, Inc. TrackMan Wheel (usbhid)
Bus 002 Device 006 ID 0a81:0205 control = on,   autosuspend_delay_ms = -1000 -- 
Chesen Electronics Corp. PS/2 Keyboard+Mouse Adapter (usbhid)

Command "uname -ra" gives:
Linux dell 4.13.0-39-generic #44~16.04.1-Ubuntu SMP Thu Apr 5 16:43:10 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

This problem tends to be very frustrating.

note: I think this is not related with autosuspend, but rather with
buffer overflow for the specific devices due to that they are not
supported in the kernel code.

Regards

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


** Tags: 16.04.4 autosuspend buffer freeze polling ubuntu usb

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

Title:
  USB devices (trackball and PS2-to-usb keyboard) freeze in Ubuntu Mate
  16.04.4 , and DELL latitude

Status in xorg package in Ubuntu:
  New

Bug description:
  Hi,

  I am facing the problem that is similar to the one described in the
  thread: https://ubuntuforums.org/showthread.php?t=2342985

  Laptop (Dell Latitude 6420) randomly stops responding to the usb
  Trackball and Keyboard. Unplugging & plugging them back into a
  different port does not fix the problem. Sometimes the problem is
  fixed after rebooting or suspending the laptopo, then turning it on;
  but the problem re-appears almost immediately - after 10".

  The problem is related to the Logitech trackman wheel & Mircosoft PS2
  Keyboard, both are old.

  Command "lsusb" for the 2 devices gives:
  Bus 002 Device 005: ID 046d:c404 Logitech, Inc. TrackMan Wheel
  Bus 002 Device 006: ID 0a81:0205 Chesen Electronics Corp. PS/2 Keyboard+Mouse 
Adapter

  Command "tlp-stat -u" for the 2 devices gives:
  Bus 002 Device 005 ID 046d:c404 control = on,   autosuspend_delay_ms = -1000 
-- Logitech, Inc. TrackMan Wheel (usbhid)
  Bus 002 Device 006 ID 0a81:0205 control = on,   autosuspend_delay_ms = -1000 
-- Chesen Electronics Corp. PS/2 Keyboard+Mouse Adapter (usbhid)

  Command "uname -ra" gives:
  Linux dell 4.13.0-39-generic #44~16.04.1-Ubuntu SMP Thu Apr 5 16:43:10 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

  This problem tends to be very frustrating.

  note: I think this is not related with autosuspend, but rather with
  buffer overflow for the specific devices due to that they are not
  supported in the kernel code.

  Regards

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1769403/+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 1752053] Re: nvidia-390 fails to boot graphical display

[Kirill Romanov]

Why this have "Fix released" status? I cannot login after "prime-select
intel", I see only a black screen

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1768906] Re: Xorg crash

[Cyrus Harmon]

Switching to lightdm instead of gdm3 gets around the problem. Should I
change the component to gdm3?

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  When attempting to log in to a newly updated bionic beaver via the
  display manager (I think this is the right term), I immediately see a
  crash, a return to the user selection/login screen and a no-longer
  functioning keyboard and mouse. This happens both with the proprietary
  driver installed drivers and with the apt installed nvidia-driver-396.

  some interesting tidbits from the syslog file are:

  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) NVIDIA(GPU-0): 
Failed to acquire modesetting permission.
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) NVIDIA(0): 
Failing initialization of X screen 0
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) UnloadModule: 
"nvidia"
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) 
UnloadSubModule: "wfb"
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) 
UnloadSubModule: "fb"
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) Screen(s) 
found, but none have a usable configuration.
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE)
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: Fatal server error:
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) no screens 
found(EE)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17
  Uname: Linux 4.15.0-20-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .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  396.24  Thu Apr 26 00:10:09 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu May  3 09:28:59 2018
  DistUpgraded: 2018-05-02 07:25:10,524 DEBUG failed to SystemUnLock() (E:Not 
locked)
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 396.24, 4.15.0-20-lowlatency, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GK104 [GeForce GTX 770] [10de:1184] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. GK104 [GeForce GTX 770] [3842:2774]
  MachineType: ASUS All Series
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-lowlatency 
root=UUID=f308f075-bd97-4230-9d24-3ab727b0036b ro splash quiet nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to bionic on 2018-05-02 (1 days ago)
  dmi.bios.date: 08/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1603
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MAXIMUS VI GENE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1603:bd08/15/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIGENE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Thu May  3 09:20:03 2018
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu4

To manage notifications about this bug go to:

[Touch-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

[Emiliano]

I tried #116 by @minterior, and I now have a working desktop, but it
feels substantially more sluggish than it was under 17.10.

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1769400] [NEW] suspend no longer functions after update to 18.04

[James]

Public bug reported:

Suspend does not complete. The system stops in an unknown state without
fully suspending and without ability to wake.

Problem began on upgrade to Ubuntu 18.04 LTS.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pm-utils 1.4.1-17
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: Unity:Unity7:ubuntu
Date: Sat May  5 13:31:03 2018
InstallationDate: Installed on 2015-03-25 (1137 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
PackageArchitecture: all
SourcePackage: pm-utils
UpgradeStatus: Upgraded to bionic on 2018-05-04 (1 days ago)

** Affects: pm-utils (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic

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

Title:
  suspend no longer functions after update to 18.04

Status in pm-utils package in Ubuntu:
  New

Bug description:
  Suspend does not complete. The system stops in an unknown state
  without fully suspending and without ability to wake.

  Problem began on upgrade to Ubuntu 18.04 LTS.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pm-utils 1.4.1-17
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sat May  5 13:31:03 2018
  InstallationDate: Installed on 2015-03-25 (1137 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  PackageArchitecture: all
  SourcePackage: pm-utils
  UpgradeStatus: Upgraded to bionic on 2018-05-04 (1 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1769400/+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 1752053] Re: nvidia-390 fails to boot graphical display

[Emiliano]

I've just ran do-release-upgrade on a Lenovo P51, and the systems hangs
just after "Starting Session c1 of user gdm". I get a little further by
purging nvidia-* (I get the GDM greeter again) but after logging in
there, the screen freezes and a little later I'm kicked back to the
greeter.

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1728238] Re: update-initramfs not adding i915 GuC firmware, firmware fails to load

[mtvoid]

This is the commit that is responsible for the Kabylake GuC firmware
file not being registered in the i915 module on Ubuntu kernels:
http://kernel.ubuntu.com/git/ubuntu/ubuntu-
bionic.git/commit/drivers/gpu/drm/i915/intel_guc_fw.c?id=dc0f16f9b5084e6be2b8c79f8c6cd499a3451791

This is the accompanying bug report:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1626740

I've also commented there to bring the issue to their attention. The
change should be reverted now that the formerly missing firmware files
are present in linux-firmware.

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

Title:
  update-initramfs not adding i915 GuC firmware, firmware fails to load

Status in initramfs-tools:
  New
Status in initramfs-tools package in Ubuntu:
  Confirmed

Bug description:
  The i915 Kabylake GuC firmware is failing to load on boot, and
  generating dmesg errors.  The Kabylake HuC firmware succeeds.  All
  files exist.  I've also verified the Kabylake GuC firmware matches the
  correct file size and md5 listed on 01.org.

  I then ran update-initramfs verbosely, and see that only
  /lib/firmware/i915/skl_guc_ver6_1.bin is being added.
  /lib/firmware/i915/bxt_guc_ver8_7.bin and
  /lib/firmware/i915/kbl_guc_ver9_14.bin seem to be ignored.

  I'm running a Dell XPS 13 9360 w/ Kabylake on Ubuntu 17.10 and
  initramfs-tools 0.125ubuntu12.  Perhaps Broxton systems might have the
  same issue?

  Output and logs:
  -

  ls -al /lib/firmware/i915/kbl_*

  -rw-r--r-- 1 root root   8616 Aug 17 11:08 
/lib/firmware/i915/kbl_dmc_ver1_01.bin
  lrwxrwxrwx 1 root root 19 Aug 17 11:08 
/lib/firmware/i915/kbl_dmc_ver1.bin -> kbl_dmc_ver1_01.bin
  -rw-r--r-- 1 root root 142656 Oct 20 21:12 
/lib/firmware/i915/kbl_guc_ver9_14.bin
  -rw-r--r-- 1 root root 218688 Aug 17 11:09 
/lib/firmware/i915/kbl_huc_ver02_00_1810.bin

  sudo cat /sys/kernel/debug/dri/0/i915_guc_load_status

  GuC firmware status:
  path: i915/kbl_guc_ver9_14.bin
  fetch: FAIL
  load: NONE
  version wanted: 9.14
  version found: 0.0
  header: offset is 0; size = 0
  uCode: offset is 0; size = 0
  RSA: offset is 0; size = 0

  GuC status 0x0001:
  Bootrom status = 0x0
  uKernel status = 0x0
  MIA Core status = 0x0

  Scratch registers:
  0: 0x0
  1: 0x0
  2: 0x0
  3: 0x0
  4: 0x0
  5: 0x0
  6: 0x0
  7: 0x0
  8: 0x0
  9: 0x0
  10: 0x0
  11: 0x0
  12: 0x0
  13: 0x0
  14: 0x0
  15: 0x0

  sudo cat /sys/kernel/debug/dri/0/i915_huc_load_status

  HuC firmware status:
  path: i915/kbl_huc_ver02_00_1810.bin
  fetch: SUCCESS
  load: SUCCESS
  version wanted: 2.0
  version found: 2.0
  header: offset is 0; size = 128
  uCode: offset is 128; size = 218304
  RSA: offset is 218432; size = 256

  HuC status 0x6000:

  dmesg

  [1.052879] hidraw: raw HID events driver (C) Jiri Kosina
  [1.056426] wmi_bus wmi_bus-PNP0C14:01: WQBC data block query control 
method not found
  [1.080320] rtsx_pci :3b:00.0: enabling device ( -> 0002)
  [1.082308] nvme nvme0: pci function :3c:00.0
  [1.095073] Setting dangerous option enable_guc_loading - tainting kernel
  [1.095075] Setting dangerous option enable_guc_submission - tainting 
kernel
  [1.097867] [drm] Memory usable by graphics device = 4078M
  [1.097869] checking generic (9000 1fb) vs hw (9000 1000)
  [1.097869] fb: switching to inteldrmfb from EFI VGA
  [1.097899] Console: switching to colour dummy device 80x25
  [1.098049] [drm] Replacing VGA console driver
  [1.104157] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
  [1.104157] [drm] Driver supports precise vblank timestamp query.
  [1.112506] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_01.bin 
(v1.1)
  [1.113055] i915 :00:02.0: vgaarb: changed VGA decodes: 
olddecodes=io+mem,decodes=io+mem:owns=io+mem
  [1.284194] usb 1-1: new low-speed USB device number 2 using xhci_hcd
  [1.298572]  nvme0n1: p1 p2
  [1.433241] usb 1-1: New USB device found, idVendor=0d62, idProduct=001c
  [1.433242] usb 1-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
  [1.433243] usb 1-1: Product: USB+PS2 Keyboard
  [1.433244] usb 1-1: Manufacturer: Generic
  [1.446460] usbcore: registered new interface driver usbhid
  [1.446461] usbhid: USB HID core driver
  [1.448067] input: Generic USB+PS2 Keyboard as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.0/0003:0D62:001C.0001/input/input7
  [1.508451] hid-generic 0003:0D62:001C.0001: input,hidraw0: USB HID v1.10 
Keyboard [Generic USB+PS2 Keyboard] on usb-:00:14.0-1/input0
  [1.508541] input: Generic USB+PS2 Keyboard as 
/devices/pci:00/:00:14.0/usb1/1-1/1-1:1.1/0003:0D62:001C.0002/input/input8
  [1.552213] usb 1-2: new full-speed USB device number 3 using xhci_hcd
  [1.568448] hid-generic 

[Touch-packages] [Bug 1752053] Re: nvidia-390 fails to boot graphical display

[Cédric]

@Thijs Kaper: I have the exact same problem.

My alternative workaround:
Like you I authenticate, black screen after typing the password and hitting 
enter. Then I go to tty2, authenticate in the terminal, and type 'startx' (and 
4 times Ctrl+C). And finally KDE starts without problem on tty2. This is crazy.


Like @Bernadette Addison I had huge icons. It was impossible to set a higher 
resolution with the KDE display manager. So I used xrandr:
xrandr --output eDP-1-1 --mode 1920x1200 --scale 1x1
for example.
The resolution is fine even after a reboot.


I also want to add that I am actually using the nvidia driver 396.24. Because I 
had so much problems before... I tried to add the graphics-driver ppa as 
advised by @Chris McDonough. I do not know if finally this helped me a little. 
Maybe I should switch back to 390.


My graphical interface is really a mess since the upgrade to 18.04 :-(

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1748656] Re: Black Screen of Death after logging into Ubuntu Bionic: "Failed to acquire modesetting permission"

[Cyrus Harmon]

I'm wondering if this could be related to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1768906

Might it make sense to unexpire this bug?

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

Title:
  Black Screen of Death after logging into Ubuntu Bionic: "Failed to
  acquire modesetting permission"

Status in xorg package in Ubuntu:
  Expired

Bug description:
  **Specs:** Ubuntu Bionic; NVidia GTX 1070 w/`nvidia-387` drivers.

  **Problem:** After installing a new GTX 1070 and installing
  `nvidia-387`, I get a black screen of death AFTER logging into Ubuntu
  (i.e., the login screen shows up just fine). I'm not even able to
  access other TTYs (the error logs below were retrieved via SSH).

  **/var/log/Xorg.0.log** There doesn't seem to be anything problematic
  in this file.

  **/var/log/Xorg.1.log** The problematic message seems to be:

  [26.455] (EE) NVIDIA(GPU-0): Failed to acquire modesetting permission.
  [26.455] (EE) NVIDIA(0): Failing initialization of X screen 0
  [26.455] (II) UnloadModule: "nvidia"
  [26.455] (II) UnloadSubModule: "wfb"
  [26.455] (II) UnloadSubModule: "fb"
  [26.455] (EE) Screen(s) found, but none have a usable configuration.
  [26.455] (EE) 
  Fatal server error:
  [26.455] (EE) no screens found(EE) 
  [26.455] (EE) 
  Please consult the The X.Org Foundation support 
  at http://wiki.x.org
  for help. 
  [26.455] (EE) Please also check the log file at "/var/log/Xorg.1.log" 
for additional information.
  [26.455] (EE) 
  [26.457] (EE) Server terminated with error (1). Closing log file.

  **Conf files.** Here are my conf files:

  $ cd /usr/share/X11
  $ find . -name "*.conf"
  ./xorg.conf.d/glamoregl.conf
  ./xorg.conf.d/10-amdgpu.conf
  ./xorg.conf.d/40-libinput.conf
  ./xorg.conf.d/50-nvidia-drm-outputclass.conf
  ./xorg.conf.d/50-nvidia-drm-outputclass.conf/nvidia-drm-outputclass.conf
  ./xorg.conf.d/10-quirks.conf
  ./xorg.conf.d/10-radeon.conf
  ./xorg.conf.d/70-wacom.conf

  I tried deleting all of these except for the nvidia one and rebooting,
  and the error persists. In addition, I tried deleting all of them and
  generating a new one via `sudo X -configure` but get

  $ cd /usr/share/X11$ 
  $ sudo pkill X && sudo X -configure  
  _XSERVTransSocketUNIXCreateListener: ...SocketCreateListener() failed
  _XSERVTransMakeAllCOTSServerListeners: server already running
  (EE) 
  Fatal server error:
  (EE) Cannot establish any listening sockets - Make sure an X server isn't 
already running(EE) 
  (EE) 
  Please consult the The X.Org Foundation support 
  at http://wiki.x.org
  for help. 
  (EE) Please also check the log file at "/var/log/Xorg.0.log" for 
additional information.
  (EE) 
  (EE) Server terminated with error (1). Closing log file.

  **kms.** Finally, in case relevant:

  $ lsmod | grep kms
  drm_kms_helper167936  1 nvidia_drm
  syscopyarea16384  1 drm_kms_helper
  sysfillrect16384  1 drm_kms_helper
  sysimgblt  16384  1 drm_kms_helper
  fb_sys_fops16384  1 drm_kms_helper
  drm   356352  6 nvidia_drm,drm_kms_helper

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .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  387.34  Tue Nov 21 03:09:00 
PST 2017
   GCC version:  gcc version 7.2.0 (Ubuntu 7.2.0-18ubuntu2)
  .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.8-0ubuntu6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Sat Feb 10 13:14:48 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.13.0-25-generic, x86_64: installed
   nvidia-387, 387.34, 4.13.0-25-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) 

[Touch-packages] [Bug 1765911] Re: Major performance regression from Ubuntu 17.10 with i915

[Max Bowsher]

Similar/same issue observed on HP Spectre 13 (2017 model) which has
exactly the same Intel HD 520 graphics. Bad enough that I had to
reinstall 17.10.

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

Title:
  Major performance regression from Ubuntu 17.10 with i915

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Desktop performance on my laptop (Intel HD 520, driver: i915) used to
  be generally good on previous Ubuntu releases but on 18.04, there is a
  VERY noticeable regression. Moving windows around in GNOME is choppy
  and tearing. It gets dramatic after the laptop resumes from suspend,
  GNOME drops to literally ~1-2 FPS. Logging out and restarting the
  session usually fixes the problem in that it restores the barely
  acceptable performance level prior to suspend.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-15.16-lowlatency 4.15.15
  Uname: Linux 4.15.0-15-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 21 16:04:38 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] 
[103c:8079]
   Advanced Micro Devices, Inc. [AMD/ATI] Opal XT [Radeon R7 M265] [1002:6604] 
(rev 81) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Opal XT [Radeon R7 M265] [103c:814f]
  InstallationDate: Installed on 2018-04-03 (18 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180402)
  MachineType: HP HP EliteBook 850 G3
  ProcKernelCmdLine: BOOT_IMAGE=/bionic/vmlinuz-4.15.0-15-lowlatency.efi.signed 
root=UUID=b6480aee-7c63-4ce4-9e8d-cdbef768b982 ro 
rootflags=subvol=@,relatime,autodefrag,space_cache quiet splash 
module.sig_enforce=1 intel_pstate=skylake_hwp vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/31/2016
  dmi.bios.vendor: HP
  dmi.bios.version: N75 Ver. 01.10
  dmi.board.name: 8079
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 85.6F
  dmi.chassis.asset.tag: 5CG6351LQL
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN75Ver.01.10:bd07/31/2016:svnHP:pnHPEliteBook850G3:pvr:rvnHP:rn8079:rvrKBCVersion85.6F:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook 850 G3
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1765911/+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 1769395] [NEW] screen fade out

[serkan türkkolu]

Public bug reported:

screen fade out

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity:Unity7:ubuntu
Date: Sat May  5 22:44:15 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.2.10, 4.13.0-39-generic, x86_64: installed
 virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed
GraphicsCard:
 Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo HD Graphics 620 [17aa:505b]
InstallationDate: Installed on 2018-04-07 (28 days ago)
InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 138a:0011 Validity Sensors, Inc. VFS5011 Fingerprint 
Reader
 Bus 001 Device 003: ID 5986:2109 Acer, Inc 
 Bus 001 Device 002: ID 0cf3:e500 Atheros Communications, Inc. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 20H1006MTX
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=5fcf40ca-beff-4360-9559-5c878a16f54b ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/09/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: R0DET83W (1.83 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20H1006MTX
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrR0DET83W(1.83):bd06/09/2017:svnLENOVO:pn20H1006MTX:pvrThinkPadE470:rvnLENOVO:rn20H1006MTX:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad E470
dmi.product.name: 20H1006MTX
dmi.product.version: ThinkPad E470
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Sat May  5 22:36:58 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug bionic compiz-0.9 ubuntu

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

Title:
  screen fade out

Status in xorg package in Ubuntu:
  New

Bug description:
  screen fade out

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sat May  5 22:44:15 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.10, 4.13.0-39-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 620 [17aa:505b]
  InstallationDate: Installed on 2018-04-07 (28 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 138a:0011 Validity Sensors, Inc. VFS5011 Fingerprint 
Reader
   Bus 001 Device 003: ID 5986:2109 Acer, Inc 
   Bus 001 Device 002: ID 0cf3:e500 Atheros Communications, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 20H1006MTX
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=5fcf40ca-beff-4360-9559-5c878a16f54b ro quiet splash 

[Touch-packages] [Bug 1765911] Re: Major performance regression from Ubuntu 17.10 with i915

[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/1765911

Title:
  Major performance regression from Ubuntu 17.10 with i915

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Desktop performance on my laptop (Intel HD 520, driver: i915) used to
  be generally good on previous Ubuntu releases but on 18.04, there is a
  VERY noticeable regression. Moving windows around in GNOME is choppy
  and tearing. It gets dramatic after the laptop resumes from suspend,
  GNOME drops to literally ~1-2 FPS. Logging out and restarting the
  session usually fixes the problem in that it restores the barely
  acceptable performance level prior to suspend.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-15.16-lowlatency 4.15.15
  Uname: Linux 4.15.0-15-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 21 16:04:38 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] 
[103c:8079]
   Advanced Micro Devices, Inc. [AMD/ATI] Opal XT [Radeon R7 M265] [1002:6604] 
(rev 81) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Opal XT [Radeon R7 M265] [103c:814f]
  InstallationDate: Installed on 2018-04-03 (18 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180402)
  MachineType: HP HP EliteBook 850 G3
  ProcKernelCmdLine: BOOT_IMAGE=/bionic/vmlinuz-4.15.0-15-lowlatency.efi.signed 
root=UUID=b6480aee-7c63-4ce4-9e8d-cdbef768b982 ro 
rootflags=subvol=@,relatime,autodefrag,space_cache quiet splash 
module.sig_enforce=1 intel_pstate=skylake_hwp vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/31/2016
  dmi.bios.vendor: HP
  dmi.bios.version: N75 Ver. 01.10
  dmi.board.name: 8079
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 85.6F
  dmi.chassis.asset.tag: 5CG6351LQL
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN75Ver.01.10:bd07/31/2016:svnHP:pnHPEliteBook850G3:pvr:rvnHP:rn8079:rvrKBCVersion85.6F:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=ELI
  dmi.product.name: HP EliteBook 850 G3
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1765911/+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 1718658] Re: ecryptfs-mount-private fails to initialize ecryptfs keys

[Hadmut Danisch]

ecryptfs (private mount) still does not work under 18.04.


That's a complete showstopper for the upgrade 16.04->18.04 because access to 
encrypted files becomes impossible or at least troublesome.

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

Title:
  ecryptfs-mount-private fails to initialize ecryptfs keys

Status in ecryptfs-utils package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  ecryptfs-mount-private fails to mount the ecryptfs after the 1st
  reboot after creating the ecryptfs by ecryptfs-setup-private.

  After the unsucessful attempt dmesg contains:

  [ 1265.695388] Could not find key with description: []
  [ 1265.695393] process_request_key_err: No key
  [ 1265.695394] Could not find valid key in user session keyring for sig 
specified in mount option: []
  [ 1265.695395] One or more global auth toks could not properly register; rc = 
[-2]
  [ 1265.695396] Error parsing options; rc = [-2]

  Note: The correct key ID has been replaced in the "".

  I also accidentally found an workaround - just running ecrytpfs-
  manager and then the ecryptfs-mount-private (it does not ask for
  password for the second time and mounts the ecryptfs correctly):

  host:~$ ecryptfs-manager

  eCryptfs key management menu
  ---
1. Add passphrase key to keyring
2. Add public key to keyring
3. Generate new public/private keypair
4. Exit

  Make selection: 4
  host:~$ ls Private/
  Access-Your-Private-Data.desktop  README.txt
  host:~$ ecryptfs-mount-private 
  host:~$ ls Private/
  

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ecryptfs-utils/+bug/1718658/+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 1752053] Re: nvidia-390 fails to boot graphical display

[Thijs Kaper]

I'm using a Dell m4800, with "NVIDIA GK107GLM Quadro K1100M" (3840x2160
pixels). Symptom; gdm login screen shows normally, but after typing
password and hitting enter, I end up on black screen. This is after
upgrade from 17.10 to 18.04.

I found a silly workaround (after trying many many other suggestions /
driver re-installs), now using nvidia-driver-396 or nvidia-driver-390;
create (if not exists) a file /etc/rc.local, with this content:

#!/bin/bash

sleep 1

exit 0


And make it executable: chmod 755 /etc/rc.local

What also worked for me, is start laptop, wait for login screen, and use 
another machine to ssh into the laptop, and execute "sudo service gdm stop ; 
sleep 5 ; sudo service gdm start".
After that, I could normally log on.

For me this seems to indicate some sort of timing or initialization
issue...

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1769386] Re: Cable network does not get recognized anymore, wifi works

[lotuspsychje]

*-network   
   description: Ethernet interface
   product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
   vendor: Realtek Semiconductor Co., Ltd.
   physical id: 0.1
   bus info: pci@:02:00.1
   logical name: enp2s0f1
   version: 12
   serial: 80:fa:5b:3e:45:e2
   size: 1Gbit/s
   capacity: 1Gbit/s
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
   configuration: autonegotiation=on broadcast=yes driver=r8169 
driverversion=2.3LK-NAPI duplex=full firmware=rtl8411-2_0.0.1 07/08/13 
latency=0 link=yes multicast=yes port=MII speed=1Gbit/s
   resources: irq:124 ioport:e000(size=256) memory:df114000-df114fff 
memory:df11-df113fff
  *-network
   description: Wireless interface
   product: Intel Corporation
   vendor: Intel Corporation
   physical id: 0
   bus info: pci@:03:00.0
   logical name: wlp3s0
   version: 78
   serial: 00:28:f8:81:66:ef
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
   configuration: broadcast=yes driver=iwlwifi 
driverversion=4.13.0-39-generic firmware=31.560484.0 ip=192.168.1.2 latency=0 
link=yes multicast=yes wireless=IEEE 802.11
   resources: irq:127 memory:df00-df001fff
maj@maj-N750BU:~$

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

Title:
  Cable network does not get recognized anymore, wifi works

Status in network-manager package in Ubuntu:
  New

Bug description:
  ubuntu 16.04 LTS cable does not connect anymore, wifi working

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat May  5 19:27:18 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-09-30 (217 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  IpRoute:
   default via 192.168.1.1 dev wlp3s0  proto static  metric 600 
   169.254.0.0/16 dev wlp3s0  scope link  metric 1000 
   192.168.1.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.1.2  metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICETYPE  STATE DBUS-PATH  
CONNECTION CON-UUID  CON-PATH   

   wlp3s0wifi  connected /org/freedesktop/NetworkManager/Devices/1  
WiFi-2.4-3569  7103236e-31c4-43d6-871d-14f3cda4b657  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp2s0f1  ethernet  disconnected  /org/freedesktop/NetworkManager/Devices/2  
-- ---- 

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1769386/+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 1769386] [NEW] Cable network does not get recognized anymore, wifi works

[lotuspsychje]

Public bug reported:

ubuntu 16.04 LTS cable does not connect anymore, wifi working

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: network-manager 1.2.6-0ubuntu0.16.04.2
ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-39-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
CurrentDesktop: Unity
Date: Sat May  5 19:27:18 2018
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2017-09-30 (217 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
IpRoute:
 default via 192.168.1.1 dev wlp3s0  proto static  metric 600 
 169.254.0.0/16 dev wlp3s0  scope link  metric 1000 
 192.168.1.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.1.2  metric 
600
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
 DEVICETYPE  STATE DBUS-PATH  
CONNECTION CON-UUID  CON-PATH   

 wlp3s0wifi  connected /org/freedesktop/NetworkManager/Devices/1  
WiFi-2.4-3569  7103236e-31c4-43d6-871d-14f3cda4b657  
/org/freedesktop/NetworkManager/ActiveConnection/1 
 enp2s0f1  ethernet  disconnected  /org/freedesktop/NetworkManager/Devices/2  
-- ---- 

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

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


** Tags: amd64 apport-bug xenial

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

Title:
  Cable network does not get recognized anymore, wifi works

Status in network-manager package in Ubuntu:
  New

Bug description:
  ubuntu 16.04 LTS cable does not connect anymore, wifi working

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.6-0ubuntu0.16.04.2
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat May  5 19:27:18 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-09-30 (217 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  IpRoute:
   default via 192.168.1.1 dev wlp3s0  proto static  metric 600 
   169.254.0.0/16 dev wlp3s0  scope link  metric 1000 
   192.168.1.0/24 dev wlp3s0  proto kernel  scope link  src 192.168.1.2  metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICETYPE  STATE DBUS-PATH  
CONNECTION CON-UUID  CON-PATH   

   wlp3s0wifi  connected /org/freedesktop/NetworkManager/Devices/1  
WiFi-2.4-3569  7103236e-31c4-43d6-871d-14f3cda4b657  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   enp2s0f1  ethernet  disconnected  /org/freedesktop/NetworkManager/Devices/2  
-- ---- 

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1769386/+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 1769385] Re: "text" errors when running Apport

[Lastique]

This error dialog box appeared twice - first, when Apport was collecting
information and second right after I pressed Yes on the first one.

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

Title:
  "text" errors when running Apport

Status in apport package in Ubuntu:
  New

Bug description:
  When reporting a bug against SDDM (ubuntu-bug sddm) Apport displayed
  an error dialog box with only "text" message. See the screenshot.

  The error should be more descriptive.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.9-0ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportLog:
   ERROR: apport (pid 5672) Sat May  5 16:51:48 2018: host pid 1566 crashed in 
a separate mount namespace, ignoring
   ERROR: apport (pid 30302) Sat May  5 17:41:20 2018: called for pid 3084, 
signal 6, core limit 0, dump mode 1
   ERROR: apport (pid 30302) Sat May  5 17:41:20 2018: executable was modified 
after program start, ignoring
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat May  5 20:23:29 2018
  InstallationDate: Installed on 2015-05-01 (1099 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to bionic on 2018-05-05 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1769385/+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 1769385] [NEW] "text" errors when running Apport

[Lastique]

Public bug reported:

When reporting a bug against SDDM (ubuntu-bug sddm) Apport displayed an
error dialog box with only "text" message. See the screenshot.

The error should be more descriptive.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: apport 2.20.9-0ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportLog:
 ERROR: apport (pid 5672) Sat May  5 16:51:48 2018: host pid 1566 crashed in a 
separate mount namespace, ignoring
 ERROR: apport (pid 30302) Sat May  5 17:41:20 2018: called for pid 3084, 
signal 6, core limit 0, dump mode 1
 ERROR: apport (pid 30302) Sat May  5 17:41:20 2018: executable was modified 
after program start, ignoring
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: KDE
Date: Sat May  5 20:23:29 2018
InstallationDate: Installed on 2015-05-01 (1099 days ago)
InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: Upgraded to bionic on 2018-05-05 (0 days ago)

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


** Tags: amd64 apport-bug bionic

** Attachment added: "Screenshot of an unknown error"
   
https://bugs.launchpad.net/bugs/1769385/+attachment/5134476/+files/apport_error.png

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

Title:
  "text" errors when running Apport

Status in apport package in Ubuntu:
  New

Bug description:
  When reporting a bug against SDDM (ubuntu-bug sddm) Apport displayed
  an error dialog box with only "text" message. See the screenshot.

  The error should be more descriptive.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.9-0ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportLog:
   ERROR: apport (pid 5672) Sat May  5 16:51:48 2018: host pid 1566 crashed in 
a separate mount namespace, ignoring
   ERROR: apport (pid 30302) Sat May  5 17:41:20 2018: called for pid 3084, 
signal 6, core limit 0, dump mode 1
   ERROR: apport (pid 30302) Sat May  5 17:41:20 2018: executable was modified 
after program start, ignoring
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat May  5 20:23:29 2018
  InstallationDate: Installed on 2015-05-01 (1099 days ago)
  InstallationMedia: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to bionic on 2018-05-05 (0 days ago)

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

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

Re: [Touch-packages] [Bug 1768661] Re: can't make WIFI work

[Richard Schneider]

Thank you Dave,

I did get it working by some sort of magic that I cant quite explain. It 
works and I'm happy.

Thank you for the suggestion though.

Best regards,

Rich S.


On 05/05/2018 03:08 AM, Dave Goldsbrough wrote:
> At a terminal screen have you tried entering the command?
>
> sudo service network-manager restart
>

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

Title:
  can't make WIFI work

Status in xorg package in Ubuntu:
  New

Bug description:
  I can't make the WIfFI operate Compact Presario V2000

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.2.0-42.49~14.04.1-generic 4.2.8-ckt12
  Uname: Linux 4.2.0-42-generic i686
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.27
  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 May  2 17:05:59 2018
  DistUpgraded: 2018-05-01 16:52:36,093 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: ndiswrapper, 1.59: added
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS480M [Mobility Radeon Xpress 200] 
[1002:5955] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:3091]
  InstallationDate: Installed on 2018-05-01 (1 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 
(20160217.1)
  Lsusb:
   Bus 001 Device 011: ID 0bda:8179 Realtek Semiconductor Corp. RTL8188EUS 
802.11n Wireless Network Adapter
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Hewlett-Packard Presario V2000 (EP377UA#ABA)
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-42-generic 
root=UUID=3698752e-32a7-443e-959d-c4578e3e85a3 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to trusty on 2018-05-01 (1 days ago)
  dmi.bios.date: 01/02/2006
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.22
  dmi.board.name: 3097
  dmi.board.vendor: Quanta
  dmi.board.version: 47.0F
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.22:bd01/02/2006:svnHewlett-Packard:pnPresarioV2000(EP377UA#ABA):pvrRev1:rvnQuanta:rn3097:rvr47.0F:cvnQuanta:ct10:cvrN/A:
  dmi.product.name: Presario V2000 (EP377UA#ABA)
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed May  2 12:26:46 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.2-1ubuntu9.1~trusty1
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1768661/+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 1769372] Re: Ubuntu 18.04 LTS does not ask for action when I press ACPI Power button/key - immediately shutdowns

[Jeremy Bicha]

** No longer affects: gnome-power-manager (Ubuntu)

** No longer affects: gnome-session (Ubuntu)

** No longer affects: policykit-1 (Ubuntu)

** No longer affects: policykit-gnome (Ubuntu)

** No longer affects: ubuntu-meta (Ubuntu)

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

Title:
  Ubuntu 18.04 LTS does not ask for action when I press ACPI Power
  button/key - immediately shutdowns

Status in gnome-settings-daemon package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New
Status in upower package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Install Ubuntu 18.04 LTS
  2. Login to session
  3. Press ACPI Power button/key

  
  Expected behavior:
  * Ubuntu asks user about action

  Actual behavior:
  * Ubuntu immediately shutdowns

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-desktop 1.417
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  5 18:32:06 2018
  InstallationDate: Installed on 2018-04-28 (7 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1769372/+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 1750051] Re: cron doesn't support MAILFROM

[Ubuntu Foundations Team Bug Bot]

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

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

** Tags added: patch

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

Title:
  cron doesn't support MAILFROM

Status in cron package in Ubuntu:
  Triaged
Status in cron package in Debian:
  New

Bug description:
  Ubuntu's cron version doesn't support setting MAILFROM to set the
  "From:" header of cron generated emails. This feature would be nice to
  have and bring parity with RHEL/CentOS which has it since RHEL 6:

  $ cat /etc/redhat-release 
  CentOS release 6.6 (Final)

  $ man 5 crontab | grep -1 FROM
 doesn´t do aliasing, and UUCP usually doesn´t read its mail.  If  MAIL-
 FROM is defined (and non-empty), it will be used as the envelope sender
 address, otherwise, ‘‘root’’ will be used.

  $ apt-cache policy cron
  cron:
Installed: 3.0pl1-128ubuntu2
Candidate: 3.0pl1-128ubuntu2
Version table:
   *** 3.0pl1-128ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cron 3.0pl1-128ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 16 15:52:54 2018
  InstallationDate: Installed on 2016-12-06 (436 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Beta amd64 
(20161206)
  SourcePackage: cron
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1750051/+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 1769372] [NEW] Ubuntu 18.04 LTS does not ask for action when I press ACPI Power button/key - immediately shutdowns

[Norbert]

Public bug reported:

Steps to reproduce:
1. Install Ubuntu 18.04 LTS
2. Login to session
3. Press ACPI Power button/key


Expected behavior:
* Ubuntu asks user about action

Actual behavior:
* Ubuntu immediately shutdowns

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubuntu-desktop 1.417
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sat May  5 18:32:06 2018
InstallationDate: Installed on 2018-04-28 (7 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: ubuntu-meta
UpgradeStatus: No upgrade log present (probably fresh install)

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

** Affects: gnome-session (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: gnome-settings-daemon (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: policykit-1 (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: policykit-gnome (Ubuntu)
 Importance: Undecided
 Status: New

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

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

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


** Tags: apport-bug bionic

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

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

** Also affects: policykit-1 (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: policykit-gnome (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: gnome-settings-daemon (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: gnome-power-manager (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: gnome-session (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: gnome-shell (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Ubuntu 18.04 LTS does not ask for action when I press ACPI Power
  button/key - immediately shutdowns

Status in gnome-power-manager package in Ubuntu:
  New
Status in gnome-session package in Ubuntu:
  New
Status in gnome-settings-daemon package in Ubuntu:
  New
Status in gnome-shell package in Ubuntu:
  New
Status in policykit-1 package in Ubuntu:
  New
Status in policykit-gnome package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New
Status in upower package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Install Ubuntu 18.04 LTS
  2. Login to session
  3. Press ACPI Power button/key

  
  Expected behavior:
  * Ubuntu asks user about action

  Actual behavior:
  * Ubuntu immediately shutdowns

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ubuntu-desktop 1.417
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  5 18:32:06 2018
  InstallationDate: Installed on 2018-04-28 (7 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1769372/+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 1769371] Re: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package ca-certificates 20180409 failed to install/upgrade: installed
  ca-certificates package post-installation script subprocess returned
  error exit status 1

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  I upgrade to 18.04 LTS then I start face this issue which cause of
  late os start and somehow makes Ubuntu so slow and stuck in start up.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: ca-certificates 20180409
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Fri Apr 27 18:06:36 2018
  ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2017-08-14 (264 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: ca-certificates
  Title: package ca-certificates 20180409 failed to install/upgrade: installed 
ca-certificates package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (7 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1769371/+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 1769371] [NEW] package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1

[Murad Bougarne]

Public bug reported:

I upgrade to 18.04 LTS then I start face this issue which cause of late
os start and somehow makes Ubuntu so slow and stuck in start up.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: ca-certificates 20180409
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Fri Apr 27 18:06:36 2018
ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2017-08-14 (264 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: ca-certificates
Title: package ca-certificates 20180409 failed to install/upgrade: installed 
ca-certificates package post-installation script subprocess returned error exit 
status 1
UpgradeStatus: Upgraded to bionic on 2018-04-27 (7 days ago)

** Affects: ca-certificates (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  package ca-certificates 20180409 failed to install/upgrade: installed
  ca-certificates package post-installation script subprocess returned
  error exit status 1

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  I upgrade to 18.04 LTS then I start face this issue which cause of
  late os start and somehow makes Ubuntu so slow and stuck in start up.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: ca-certificates 20180409
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Fri Apr 27 18:06:36 2018
  ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2017-08-14 (264 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: ca-certificates
  Title: package ca-certificates 20180409 failed to install/upgrade: installed 
ca-certificates package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (7 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1769371/+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 1750051] Re: cron doesn't support MAILFROM

[niconil]

submit a patch to add the feature.

Heavily inspired from cronie project :
https://github.com/cronie-crond/cronie/blob/master/src/do_command.c

** Attachment added: "patch.txt"
   
https://bugs.launchpad.net/debian/+source/cron/+bug/1750051/+attachment/5134394/+files/patch.txt

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

Title:
  cron doesn't support MAILFROM

Status in cron package in Ubuntu:
  Triaged
Status in cron package in Debian:
  New

Bug description:
  Ubuntu's cron version doesn't support setting MAILFROM to set the
  "From:" header of cron generated emails. This feature would be nice to
  have and bring parity with RHEL/CentOS which has it since RHEL 6:

  $ cat /etc/redhat-release 
  CentOS release 6.6 (Final)

  $ man 5 crontab | grep -1 FROM
 doesn´t do aliasing, and UUCP usually doesn´t read its mail.  If  MAIL-
 FROM is defined (and non-empty), it will be used as the envelope sender
 address, otherwise, ‘‘root’’ will be used.

  $ apt-cache policy cron
  cron:
Installed: 3.0pl1-128ubuntu2
Candidate: 3.0pl1-128ubuntu2
Version table:
   *** 3.0pl1-128ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cron 3.0pl1-128ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 16 15:52:54 2018
  InstallationDate: Installed on 2016-12-06 (436 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Beta amd64 
(20161206)
  SourcePackage: cron
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1750051/+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 1768906] Re: Xorg crash

[Cyrus Harmon]

I am able to reproduce this following a reinstall of 18.04 from the ISO
image, but only on the same box. No problems on two other computers.
Will try reverting to 17.10 to see if that fixes the problem.

As for the component, can I test with alternative session managers, or
is gdm3 the only game in town? thanks!

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  When attempting to log in to a newly updated bionic beaver via the
  display manager (I think this is the right term), I immediately see a
  crash, a return to the user selection/login screen and a no-longer
  functioning keyboard and mouse. This happens both with the proprietary
  driver installed drivers and with the apt installed nvidia-driver-396.

  some interesting tidbits from the syslog file are:

  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) NVIDIA(GPU-0): 
Failed to acquire modesetting permission.
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) NVIDIA(0): 
Failing initialization of X screen 0
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) UnloadModule: 
"nvidia"
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) 
UnloadSubModule: "wfb"
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) 
UnloadSubModule: "fb"
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) Screen(s) 
found, but none have a usable configuration.
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE)
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: Fatal server error:
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) no screens 
found(EE)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17
  Uname: Linux 4.15.0-20-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .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  396.24  Thu Apr 26 00:10:09 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu May  3 09:28:59 2018
  DistUpgraded: 2018-05-02 07:25:10,524 DEBUG failed to SystemUnLock() (E:Not 
locked)
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 396.24, 4.15.0-20-lowlatency, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GK104 [GeForce GTX 770] [10de:1184] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. GK104 [GeForce GTX 770] [3842:2774]
  MachineType: ASUS All Series
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-lowlatency 
root=UUID=f308f075-bd97-4230-9d24-3ab727b0036b ro splash quiet nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to bionic on 2018-05-02 (1 days ago)
  dmi.bios.date: 08/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1603
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MAXIMUS VI GENE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1603:bd08/15/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIGENE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Thu May  3 09:20:03 2018
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
  

[Touch-packages] [Bug 1750051] Re: cron doesn't support MAILFROM

[niconil]

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

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

Title:
  cron doesn't support MAILFROM

Status in cron package in Ubuntu:
  Triaged
Status in cron package in Debian:
  New

Bug description:
  Ubuntu's cron version doesn't support setting MAILFROM to set the
  "From:" header of cron generated emails. This feature would be nice to
  have and bring parity with RHEL/CentOS which has it since RHEL 6:

  $ cat /etc/redhat-release 
  CentOS release 6.6 (Final)

  $ man 5 crontab | grep -1 FROM
 doesn´t do aliasing, and UUCP usually doesn´t read its mail.  If  MAIL-
 FROM is defined (and non-empty), it will be used as the envelope sender
 address, otherwise, ‘‘root’’ will be used.

  $ apt-cache policy cron
  cron:
Installed: 3.0pl1-128ubuntu2
Candidate: 3.0pl1-128ubuntu2
Version table:
   *** 3.0pl1-128ubuntu2 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: cron 3.0pl1-128ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98
  Uname: Linux 4.4.0-116-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Feb 16 15:52:54 2018
  InstallationDate: Installed on 2016-12-06 (436 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Beta amd64 
(20161206)
  SourcePackage: cron
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1750051/+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 1769316] Re: Notification of Live patch sign-in is inconsistent depending on how Software & Updates is started

[Launchpad Bug Tracker]

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

** Changed in: software-properties (Ubuntu)
   Status: New => Confirmed

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

Title:
  Notification of Live patch sign-in is inconsistent depending on how
  Software & Updates is started

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  This issue has I think been partly covered in other bug reports that
  are currently marked incomplete but none describe my exact issue with
  Livepatch signing in..

  I'm creating this report in the hope that it does provide enough
  information with regards to what I am seeing here and have been doing
  so since before the release of Ubuntu 18.04.

  Last night I enabled Livepatch by signing into the appropriate tab of
  Software & Updates. As a result of briefly discussing this elsewhere I
  decided to check whether I was still logged in or not.

  1) I started synaptic and pulled up "Software & Updates" from the
  Settings menu. The Updates tab shows the Livepatch box as being
  checked but a message of "To use Livepatch you need to sign in" and a
  Sign-in button is displayed. If I attempt to sign in I see a "Choose
  an account" dialog. Clicking on "Sign in.." displays an empty panel
  with "Devices" in the top left corner. This is obviously the Settings
  application with no text being displayed.

  2) I then started "Software & Updates" as a stand alone application.
  The Updates tab shows that I am signed in, my email address is shown
  along with a "Sign out" button and the message "Use Canonical
  Livepatch to increase security between restarts is displayed
  immediately above.

  Restarting "Software & Updates" alternately through synaptic and as a
  stand alone application shows either an unsuccessful login or a
  successful log-in as described in points 1) and 2).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: software-properties-gtk 0.96.24.32.1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat May  5 08:38:38 2018
  InstallationDate: Installed on 2017-11-07 (178 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to bionic on 2018-02-21 (72 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1769316/+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 1752053] Re: nvidia-390 fails to boot graphical display

[Bernadette Addison]

@Tom - getting closer! I can now login...but icons are HUGE!!!  Lol.
Need to fix resolution

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

Title:
  nvidia-390 fails to boot graphical display

Status in mesa package in Ubuntu:
  Fix Released
Status in nvidia-graphics-drivers-390 package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Invalid

Bug description:
  I'm using Bionic with the new 4.15 kernel. I've been using the
  nvidia-384 driver with no problem for a while.  Today I issued "sudo
  apt-get upgrade" and I was prompted to upgrade the nvidia driver to
  the nvidia-390.  After installing the driver and rebooting, I was only
  able to boot in to the tty terminal.  The graphical display failed to
  boot.  I have had similar problems with nvidia driver version 390 with
  Arch Linux and with Open Suse Tumbleweed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752053/+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 1769346] Re: Unable to install 18.04 server AMD64 with targeted kernel: initramfs-tools

[Alessandro Tiberti]

If I run the "install the system" process a second time immediately
afterwards, it passes without errors/warnings but after installation
when system restarts:

error: file '/boot/grub/i386-pc/normal.mod' not found.
Entering rescue mode...
grub rescue>

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

Title:
  Unable to install 18.04 server AMD64 with targeted kernel: initramfs-
  tools

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Trying to install from: ubuntu-18.04-server-amd64.iso

  at boot: F6->expert mode and F4->minimal VM

  I go through the usual steps but when it comes to the "install the
  system" phase, if I select normal (not live) and then "targeted", the
  installation stops with an error on initramfs.

  The error doesn't occur if I use a generic kernel instead of the
  targeted one.

  at that phase I'm not yet able to install reportbug so below you'll
  find what I found in syslog. VM running under ESXi 6.7.

  Thanks!

  May  5 12:52:58 in-target: (Reading database ... 100%^M(Reading database ... 
11077 files and directories currently installed.)^M
  May  5 12:52:58 in-target: Preparing to unpack 
.../0-linux-headers-4.15.0-20_4.15.0-20.21_all.deb ...^M
  May  5 12:52:58 in-target: Unpacking linux-headers-4.15.0-20 (4.15.0-20.21) 
...^M
  May  5 12:53:03 in-target: Selecting previously unselected package 
linux-headers-4.15.0-20-generic.^M
  May  5 12:53:03 in-target: Preparing to unpack 
.../1-linux-headers-4.15.0-20-generic_4.15.0-20.21_amd64.deb ...^M
  May  5 12:53:03 in-target: Unpacking linux-headers-4.15.0-20-generic 
(4.15.0-20.21) ...^M
  May  5 12:53:05 in-target: Selecting previously unselected package 
linux-headers-generic.^M
  May  5 12:53:05 in-target: Preparing to unpack 
.../2-linux-headers-generic_4.15.0.20.23_amd64.deb ...^M
  May  5 12:53:05 in-target: Unpacking linux-headers-generic (4.15.0.20.23) 
...^M
  May  5 12:53:05 in-target: Selecting previously unselected package 
linux-headers-virtual.^M
  May  5 12:53:05 in-target: Preparing to unpack 
.../3-linux-headers-virtual_4.15.0.20.23_amd64.deb ...^M
  May  5 12:53:05 in-target: Unpacking linux-headers-virtual (4.15.0.20.23) 
...^M
  May  5 12:53:05 in-target: Selecting previously unselected package 
linux-modules-4.15.0-20-generic.^M
  May  5 12:53:05 in-target: Preparing to unpack 
.../4-linux-modules-4.15.0-20-generic_4.15.0-20.21_amd64.deb ...^M
  May  5 12:53:05 in-target: Unpacking linux-modules-4.15.0-20-generic 
(4.15.0-20.21) ...^M
  May  5 12:53:08 in-target: Selecting previously unselected package 
linux-image-4.15.0-20-generic.^M
  May  5 12:53:08 in-target: Preparing to unpack 
.../5-linux-image-4.15.0-20-generic_4.15.0-20.21_amd64.deb ...^M
  May  5 12:53:08 in-target: Unpacking linux-image-4.15.0-20-generic 
(4.15.0-20.21) ...^M
  May  5 12:53:08 in-target: Selecting previously unselected package 
linux-image-virtual.^M
  May  5 12:53:08 in-target: Preparing to unpack 
.../6-linux-image-virtual_4.15.0.20.23_amd64.deb ...^M
  May  5 12:53:08 in-target: Unpacking linux-image-virtual (4.15.0.20.23) ...^M
  May  5 12:53:08 in-target: Selecting previously unselected package 
linux-virtual.^M
  May  5 12:53:08 in-target: Preparing to unpack 
.../7-linux-virtual_4.15.0.20.23_amd64.deb ...^M
  May  5 12:53:08 in-target: Unpacking linux-virtual (4.15.0.20.23) ...^M
  May  5 12:53:09 in-target: Setting up linux-modules-4.15.0-20-generic 
(4.15.0-20.21) ...^M
  May  5 12:53:09 in-target: Setting up linux-image-4.15.0-20-generic 
(4.15.0-20.21) ...^M
  May  5 12:53:09 in-target: I: /vmlinuz.old is now a symlink to 
boot/vmlinuz-4.15.0-20-generic^M
  May  5 12:53:09 in-target: I: /initrd.img.old is now a symlink to 
boot/initrd.img-4.15.0-20-generic^M
  May  5 12:53:09 in-target: I: /vmlinuz is now a symlink to 
boot/vmlinuz-4.15.0-20-generic^M
  May  5 12:53:09 in-target: I: /initrd.img is now a symlink to 
boot/initrd.img-4.15.0-20-generic^M
  May  5 12:53:09 in-target: Setting up linux-image-virtual (4.15.0.20.23) ...^M
  May  5 12:53:10 in-target: Setting up linux-headers-4.15.0-20 (4.15.0-20.21) 
...^M
  May  5 12:53:10 in-target: Setting up linux-headers-4.15.0-20-generic 
(4.15.0-20.21) ...^M
  May  5 12:53:10 in-target: Setting up linux-headers-generic (4.15.0.20.23) 
...^M
  May  5 12:53:10 in-target: Setting up linux-headers-virtual (4.15.0.20.23) 
...^M
  May  5 12:53:10 in-target: Setting up linux-virtual (4.15.0.20.23) ...^M
  May  5 12:53:10 in-target: Processing triggers for 
linux-image-4.15.0-20-generic (4.15.0-20.21) ...^M
  May  5 12:53:10 in-target: /etc/kernel/postinst.d/initramfs-tools:^M
  May  5 12:53:10 in-target: update-initramfs: Generating 
/boot/initrd.img-4.15.0-20-generic^M
  May  5 12:53:10 in-target: mkinitramfs: failed to determine device for /^M
  May  5 12:53:10 in-target: mkinitramfs: workaround is MODULES=most, 

[Touch-packages] [Bug 1769346] [NEW] Unable to install 18.04 server AMD64 with targeted kernel: initramfs-tools

[Alessandro Tiberti]

Public bug reported:

Trying to install from: ubuntu-18.04-server-amd64.iso

at boot: F6->expert mode and F4->minimal VM

I go through the usual steps but when it comes to the "install the
system" phase, if I select normal (not live) and then "targeted", the
installation stops with an error on initramfs.

The error doesn't occur if I use a generic kernel instead of the
targeted one.

at that phase I'm not yet able to install reportbug so below you'll find
what I found in syslog. VM running under ESXi 6.7.

Thanks!

May  5 12:52:58 in-target: (Reading database ... 100%^M(Reading database ... 
11077 files and directories currently installed.)^M
May  5 12:52:58 in-target: Preparing to unpack 
.../0-linux-headers-4.15.0-20_4.15.0-20.21_all.deb ...^M
May  5 12:52:58 in-target: Unpacking linux-headers-4.15.0-20 (4.15.0-20.21) 
...^M
May  5 12:53:03 in-target: Selecting previously unselected package 
linux-headers-4.15.0-20-generic.^M
May  5 12:53:03 in-target: Preparing to unpack 
.../1-linux-headers-4.15.0-20-generic_4.15.0-20.21_amd64.deb ...^M
May  5 12:53:03 in-target: Unpacking linux-headers-4.15.0-20-generic 
(4.15.0-20.21) ...^M
May  5 12:53:05 in-target: Selecting previously unselected package 
linux-headers-generic.^M
May  5 12:53:05 in-target: Preparing to unpack 
.../2-linux-headers-generic_4.15.0.20.23_amd64.deb ...^M
May  5 12:53:05 in-target: Unpacking linux-headers-generic (4.15.0.20.23) ...^M
May  5 12:53:05 in-target: Selecting previously unselected package 
linux-headers-virtual.^M
May  5 12:53:05 in-target: Preparing to unpack 
.../3-linux-headers-virtual_4.15.0.20.23_amd64.deb ...^M
May  5 12:53:05 in-target: Unpacking linux-headers-virtual (4.15.0.20.23) ...^M
May  5 12:53:05 in-target: Selecting previously unselected package 
linux-modules-4.15.0-20-generic.^M
May  5 12:53:05 in-target: Preparing to unpack 
.../4-linux-modules-4.15.0-20-generic_4.15.0-20.21_amd64.deb ...^M
May  5 12:53:05 in-target: Unpacking linux-modules-4.15.0-20-generic 
(4.15.0-20.21) ...^M
May  5 12:53:08 in-target: Selecting previously unselected package 
linux-image-4.15.0-20-generic.^M
May  5 12:53:08 in-target: Preparing to unpack 
.../5-linux-image-4.15.0-20-generic_4.15.0-20.21_amd64.deb ...^M
May  5 12:53:08 in-target: Unpacking linux-image-4.15.0-20-generic 
(4.15.0-20.21) ...^M
May  5 12:53:08 in-target: Selecting previously unselected package 
linux-image-virtual.^M
May  5 12:53:08 in-target: Preparing to unpack 
.../6-linux-image-virtual_4.15.0.20.23_amd64.deb ...^M
May  5 12:53:08 in-target: Unpacking linux-image-virtual (4.15.0.20.23) ...^M
May  5 12:53:08 in-target: Selecting previously unselected package 
linux-virtual.^M
May  5 12:53:08 in-target: Preparing to unpack 
.../7-linux-virtual_4.15.0.20.23_amd64.deb ...^M
May  5 12:53:08 in-target: Unpacking linux-virtual (4.15.0.20.23) ...^M
May  5 12:53:09 in-target: Setting up linux-modules-4.15.0-20-generic 
(4.15.0-20.21) ...^M
May  5 12:53:09 in-target: Setting up linux-image-4.15.0-20-generic 
(4.15.0-20.21) ...^M
May  5 12:53:09 in-target: I: /vmlinuz.old is now a symlink to 
boot/vmlinuz-4.15.0-20-generic^M
May  5 12:53:09 in-target: I: /initrd.img.old is now a symlink to 
boot/initrd.img-4.15.0-20-generic^M
May  5 12:53:09 in-target: I: /vmlinuz is now a symlink to 
boot/vmlinuz-4.15.0-20-generic^M
May  5 12:53:09 in-target: I: /initrd.img is now a symlink to 
boot/initrd.img-4.15.0-20-generic^M
May  5 12:53:09 in-target: Setting up linux-image-virtual (4.15.0.20.23) ...^M
May  5 12:53:10 in-target: Setting up linux-headers-4.15.0-20 (4.15.0-20.21) 
...^M
May  5 12:53:10 in-target: Setting up linux-headers-4.15.0-20-generic 
(4.15.0-20.21) ...^M
May  5 12:53:10 in-target: Setting up linux-headers-generic (4.15.0.20.23) ...^M
May  5 12:53:10 in-target: Setting up linux-headers-virtual (4.15.0.20.23) ...^M
May  5 12:53:10 in-target: Setting up linux-virtual (4.15.0.20.23) ...^M
May  5 12:53:10 in-target: Processing triggers for 
linux-image-4.15.0-20-generic (4.15.0-20.21) ...^M
May  5 12:53:10 in-target: /etc/kernel/postinst.d/initramfs-tools:^M
May  5 12:53:10 in-target: update-initramfs: Generating 
/boot/initrd.img-4.15.0-20-generic^M
May  5 12:53:10 in-target: mkinitramfs: failed to determine device for /^M
May  5 12:53:10 in-target: mkinitramfs: workaround is MODULES=most, check:^M
May  5 12:53:10 in-target: grep -r MODULES /etc/initramfs-tools/^M
May  5 12:53:10 in-target: ^M
May  5 12:53:10 in-target: Error please report bug on initramfs-tools^M
May  5 12:53:10 in-target: Include the output of 'mount' and 'cat 
/proc/mounts'^M
May  5 12:53:10 in-target: update-initramfs: failed for 
/boot/initrd.img-4.15.0-20-generic with 1.^M
May  5 12:53:10 in-target: run-parts: /etc/kernel/postinst.d/initramfs-tools 
exited with return code 1^M
May  5 12:53:10 in-target: dpkg: error processing package 
linux-image-4.15.0-20-generic (--configure):^M
May  5 12:53:10 in-target:  installed linux-image-4.15.0-20-generic package 
post-installation script 

[Touch-packages] [Bug 1769288] Re: indicator-datetime displays the date unnaturally in Japanese

[Joe Carey]

So, it seems the root is that Japan uses ISO dating typically, even
handwritten, and the new default uses not ISO, and there's no GUI option
to set it as such.  Not so much a bug as a design choice.

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

Title:
  indicator-datetime displays the date unnaturally in Japanese

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  The date should be (and has been in previous Ubuntu versions)
  displayed as follows (for YMD):

  2018年5月4日 (the symbols clearly mean year, month, day).

  Instead, they're displayed weirdly as "5月 4 2018" This is not the way
  a date would ever be written in Japanese. In gnome this happens on the
  lock screen as well.

  If you were writing a date without the year it would be:

  5月4日

  it doesn't make sense to leave off the 日.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1769288/+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 1769288] Re: indicator-datetime displays the date unnaturally in Japanese

[Joe Carey]

Hey, from https://askubuntu.com/questions/237941/how-to-configure-the-
clock-date-format-to-iso-8601-in-unity

I was able to sort this manually:

There's no easy way to do it in the GUI. One can either use dconf-editor
(which is GUI-ish), and edit two keys in
/com/canonical/indicator/datetime (time-format to custom, and custom-
time-format to the desired strftime directives, in your case %F %R (or,
equivalently, %Y-%m-%d %H:%M)), or do it directly from the terminal with
the following two commands (which, just to be clear, change the same
keys):

dconf write /com/canonical/indicator/datetime/time-format "'custom'"
dconf write /com/canonical/indicator/datetime/custom-time-format "'%F %R

I replaced %Y-%m-%d %H:%M with %Y年%m月%d日 %H:%M

However, the default remains not sane :)

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

Title:
  indicator-datetime displays the date unnaturally in Japanese

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  The date should be (and has been in previous Ubuntu versions)
  displayed as follows (for YMD):

  2018年5月4日 (the symbols clearly mean year, month, day).

  Instead, they're displayed weirdly as "5月 4 2018" This is not the way
  a date would ever be written in Japanese. In gnome this happens on the
  lock screen as well.

  If you were writing a date without the year it would be:

  5月4日

  it doesn't make sense to leave off the 日.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1769288/+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 1769343] Re: package util-linux 2.27.1-6ubuntu3.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package util-linux 2.27.1-6ubuntu3.4 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in util-linux package in Ubuntu:
  New

Bug description:
  i dont'know

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.27.1-6ubuntu3.4
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  Uname: Linux 4.4.0-109-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  Date: Sat May  5 15:43:53 2018
  DpkgHistoryLog:
   Start-Date: 2018-05-05  15:43:49
   Commandline: apt-get install xrdp
   Requested-By: sv2hrt (1000)
   Install: vnc4server:i386 (4.1.1+xorg4.3.0-37.3ubuntu2, automatic), 
xbase-clients:i386 (1:7.7+13ubuntu3, automatic), xrdp:i386 (0.6.1-2)
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-10-03 (945 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.25
  SourcePackage: util-linux
  Title: package util-linux 2.27.1-6ubuntu3.4 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1769343/+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 1769343] [NEW] package util-linux 2.27.1-6ubuntu3.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Paul]

Public bug reported:

i dont'know

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: util-linux 2.27.1-6ubuntu3.4
ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
Uname: Linux 4.4.0-109-generic i686
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: i386
Date: Sat May  5 15:43:53 2018
DpkgHistoryLog:
 Start-Date: 2018-05-05  15:43:49
 Commandline: apt-get install xrdp
 Requested-By: sv2hrt (1000)
 Install: vnc4server:i386 (4.1.1+xorg4.3.0-37.3ubuntu2, automatic), 
xbase-clients:i386 (1:7.7+13ubuntu3, automatic), xrdp:i386 (0.6.1-2)
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2015-10-03 (945 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.25
SourcePackage: util-linux
Title: package util-linux 2.27.1-6ubuntu3.4 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: util-linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 xenial

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

Title:
  package util-linux 2.27.1-6ubuntu3.4 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in util-linux package in Ubuntu:
  New

Bug description:
  i dont'know

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: util-linux 2.27.1-6ubuntu3.4
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  Uname: Linux 4.4.0-109-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  Date: Sat May  5 15:43:53 2018
  DpkgHistoryLog:
   Start-Date: 2018-05-05  15:43:49
   Commandline: apt-get install xrdp
   Requested-By: sv2hrt (1000)
   Install: vnc4server:i386 (4.1.1+xorg4.3.0-37.3ubuntu2, automatic), 
xbase-clients:i386 (1:7.7+13ubuntu3, automatic), xrdp:i386 (0.6.1-2)
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-10-03 (945 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.25
  SourcePackage: util-linux
  Title: package util-linux 2.27.1-6ubuntu3.4 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1769343/+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 1769297] Re: resume from hibernation broken when resume image is autodetected

[Ubuntu Foundations Team Bug Bot]

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

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

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

Title:
  resume from hibernation broken when resume image is autodetected

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I found a reason of non-functioning resume from hibernation when
  resume partition/file is autodetected by intiramfs hook /usr/share
  /initramfs-tools/hooks/resume.

  Here is the scenario:
  1) hook /usr/share/initramfs-tools/hooks/resume creates config 
conf/conf.d/zz-resume-auto saved in initrd image, containing one variable: 
RESUME=UUID=106238b0-707d-4422-866d-a7534da50702 in my case

  2) during boot init script sets 'resume' variable to 'RESUME' value
  from conf/conf.d/zz-resume-auto, then it executes local-premount
  scripts including local-premount/resume

  3) resuming script local-premount/resume 
(/usr/share/initramfs-tools/scripts/local-premount/resume) tries to get resume 
device major-minor numbers by these lines:
  DEV=$(readlink ${resume})
  DEV=/sys/class/block/${DEV##*/}/dev
  if [ -r "$DEV" ]; then
  read MAJMIN < "$DEV"
  fi

  4) next check fails and resume process silently aborts:
  if [ -z "$MAJMIN" ]; then
  exit 1
  fi

  Resuming script fails to get device major-minor because
  resume=UUID=106238b0-707d-4422-866d-a7534da50702 -- it's not resolved
  into device path in init script.

  Commonly mentioned workaround is to explicitly specify kernel
  parameter resume=UUID=106238b0-707d-4422-866d-a7534da50702 -- only in
  this case init script resolves it to device path.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: initramfs-tools 0.130ubuntu3
  Uname: Linux 4.16.6-041606-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  5 11:32:31 2018
  InstallationDate: Installed on 2018-03-27 (38 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1769297/+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 1769341] [NEW] Can't find HDMI

[Sigurd Holmen]

Public bug reported:

The machine cannot find the HDMI port of the computer. It was working
fine in version 17.10, but not after upgrading to 18.04. When looking at
the graphics part of inxi, it is reporting that modesetting has failed.

command: inxi -G

Graphics:  Card: Intel HD Graphics 520
   Display Server: x11 (X.Org 1.19.6 ) driver: FAILED: modesetting
   Resolution: 1920x1080@60.00hz
   OpenGL: renderer: Mesa DRI Intel HD Graphics 520 (Skylake GT2)
   version: 4.5 Mesa 18.0.0-rc5

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat May  5 14:27:56 2018
DistUpgraded: 2018-05-05 12:31:36,611 DEBUG icon theme changed, re-reading
DistroCodename: bionic
DistroVariant: ubuntu
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Acer Incorporated [ALI] Skylake GT2 [HD Graphics 520] [1025:1094]
InstallationDate: Installed on 2017-10-31 (186 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 0bda:57f3 Realtek Semiconductor Corp. 
 Bus 001 Device 003: ID 0489:e0a3 Foxconn / Hon Hai 
 Bus 001 Device 002: ID 062a:4101 Creative Labs Wireless Keyboard/Mouse
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer Aspire E5-575
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=98508690-a9ad-4456-9e28-f3d867db01e9 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2018-05-05 (0 days ago)
dmi.bios.date: 04/26/2016
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.04
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: Ironman_SK
dmi.board.vendor: Acer
dmi.board.version: V1.04
dmi.chassis.type: 10
dmi.chassis.vendor: Chassis Manufacturer
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.04:bd04/26/2016:svnAcer:pnAspireE5-575:pvrV1.04:rvnAcer:rnIronman_SK:rvrV1.04:cvnChassisManufacturer:ct10:cvrChassisVersion:
dmi.product.family: SKL
dmi.product.name: Aspire E5-575
dmi.product.version: V1.04
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Tue Oct 31 16:01:19 2017
xserver.configfile: default
xserver.errors:
 Failed to load module "fbdev" (module does not exist, 0)
 Failed to load module "vesa" (module does not exist, 0)
 Failed to load module "fbdev" (module does not exist, 0)
 Failed to load module "vesa" (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1.3
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  Can't find HDMI

Status in xorg package in Ubuntu:
  New

Bug description:
  The machine cannot find the HDMI port of the computer. It was working
  fine in version 17.10, but not after upgrading to 18.04. When looking
  at the graphics part of inxi, it is reporting that modesetting has
  failed.

  command: inxi -G

  Graphics:  Card: Intel HD Graphics 520
 Display Server: x11 (X.Org 1.19.6 ) driver: FAILED: modesetting
 Resolution: 1920x1080@60.00hz
 OpenGL: renderer: Mesa DRI Intel HD Graphics 520 (Skylake GT2)
 version: 4.5 Mesa 18.0.0-rc5

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  5 14:27:56 2018
  DistUpgraded: 2018-05-05 12:31:36,611 DEBUG icon theme changed, re-reading
  DistroCodename: 

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

[Francis Ginther]

** Tags added: id-5ae35ea55ac10e9203cade8d

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

Title:
  PythonDetails contains an error message if python not installed

Status in apport package in Ubuntu:
  New

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

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

  PythonDetails: N/A

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

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

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

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

[Touch-packages] [Bug 1769338] Re: software-properties-gtk gets stuck when switching from nvidia to nouveau

[Bump]

root@ubuntu:~# ubuntu-drivers list
nvidia-driver-390
root@ubuntu:~#

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

Title:
  software-properties-gtk  gets stuck when switching from nvidia to
  nouveau and vice-versa

Status in software-properties package in Ubuntu:
  New

Bug description:
  Switching from nvidia to nouveau makes the gui to get stuck at
  "Applying changes..."

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1769338/+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 1769338] Re: software-properties-gtk gets stuck when switching from nvidia to nouveau

[Bump]

** Attachment added: "software-properties-gtk_halts-when-changing.png"
   
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1769338/+attachment/5134299/+files/software-properties-gtk_halts-when-changing.png

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

Title:
  software-properties-gtk  gets stuck when switching from nvidia to
  nouveau and vice-versa

Status in software-properties package in Ubuntu:
  New

Bug description:
  Switching from nvidia to nouveau makes the gui to get stuck at
  "Applying changes..."

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

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

Re: [Touch-packages] [Bug 1769022] Re: ubuntu 18.04 freezes after the login

[Ghassan Mina]

Thank you for your support but I was able to resolve the issue. The problem
was due to the extensions that I had before upgrading. I wiped all the
extensions and everything worked as a charm

On 5 May 2018 at 03:00, Dave Goldsbrough  wrote:

> Many bugs are now accumulating with this and similar issues surrounding
> Xorg. This is just one example https://bugs.launchpad.net/
> ubuntu/+source/xorg/+bug/1764087
> There are others. Some are related to Lenovo laptops but not all.
> Shame that 18.04 LTS has been allowed to be released without this inherent
> bug being fixed. It is damaging Ubuntu reputation.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1769022
>
> Title:
>   ubuntu 18.04 freezes after the login
>
> Status in xorg package in Ubuntu:
>   Confirmed
>
> Bug description:
>   I am not able to log to ubuntu 18.04 after the upgrade. When I login I
>   get setup screen with the word "Welcome" and the system freezes
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: xorg 1:7.7+19ubuntu7
>   ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
>   Uname: Linux 4.15.0-20-generic x86_64
>   .tmp.unity_support_test.0:
>
>   ApportVersion: 2.20.9-0ubuntu7
>   Architecture: amd64
>   CompizPlugins: No value set for `/apps/compiz-1/general/
> screen0/options/active_plugins'
>   CompositorRunning: None
>   Date: Thu May  3 23:29:56 2018
>   DistUpgraded: 2018-05-03 01:59:32,397 ERROR got error from
> PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to
> execute child process “./xorg_fix_proprietary.py” (No such file or
> directory) (8))
>   DistroCodename: bionic
>   DistroVariant: ubuntu
>   GraphicsCard:
>Advanced Micro Devices, Inc. [AMD/ATI] BeaverCreek [Radeon HD 6520G]
> [1002:9647] (prog-if 00 [VGA controller])
>  Subsystem: Lenovo BeaverCreek [Radeon HD 6520G] [17aa:3971]
>   InstallationDate: Installed on 2016-11-19 (530 days ago)
>   InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64
> (20160719)
>   MachineType: LENOVO 129925U
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic
> root=UUID=91dffd26-787f-4656-94b0-9568086633ac ro radeon.dpm=1
>   SourcePackage: xorg
>   UpgradeStatus: Upgraded to bionic on 2018-05-03 (0 days ago)
>   dmi.bios.date: 07/20/2011
>   dmi.bios.vendor: LENOVO
>   dmi.bios.version: 54CN18WW
>   dmi.board.asset.tag: Base Board Asset Tag Unknown
>   dmi.board.name: Torpedo
>   dmi.board.vendor: LENOVO
>   dmi.board.version: 109-C06210-00B
>   dmi.chassis.asset.tag: Chassis Asset Tag Unknown
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: LENOVO
>   dmi.chassis.version: Chassis Version Unknown
>   dmi.modalias: dmi:bvnLENOVO:bvr54CN18WW:bd07/20/2011:svnLENOVO:
> pn129925U:pvrIdeapadZ575:rvnLENOVO:rnTorpedo:rvr109-
> C06210-00B:cvnLENOVO:ct10:cvrChassisVersionUnknown:
>   dmi.product.family: IDEAPAD
>   dmi.product.name: 129925U
>   dmi.product.version: Ideapad Z575
>   dmi.sys.vendor: LENOVO
>   version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
>   version.libdrm2: libdrm2 2.4.91-2
>   version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
>   version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
>   version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev
> 1:2.10.5-1ubuntu1
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel
> 2:2.99.917+git20171229-1
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau
> 1:1.0.15-2
>   xserver.bootTime: Thu May  3 22:52:41 2018
>   xserver.configfile: default
>   xserver.errors:
>
>   xserver.logfile: /var/log/Xorg.0.log
>   xserver.version: 2:1.19.6-1ubuntu4
>   xserver.video_driver: radeon
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1769022/+subscriptions
>


-- 
Ghassan Mina
IT/GIS Specialist

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

Title:
  ubuntu 18.04 freezes after the login

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I am not able to log to ubuntu 18.04 after the upgrade. When I login I
  get setup screen with the word "Welcome" and the system freezes

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu May  3 23:29:56 2018
  DistUpgraded: 2018-05-03 01:59:32,397 ERROR got error from PostInstallScript 

[Touch-packages] [Bug 1769338] Re: software-properties-gtk gets stuck when switching from nvidia to nouveau

[Bump]

If I click Cancel and select nvidia and apply same problem, stays there
forever.

** Summary changed:

- software-properties-gtk  gets stuck when switching from nvidia to nouveau
+ software-properties-gtk  gets stuck when switching from nvidia to nouveau and 
vice-versa

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

Title:
  software-properties-gtk  gets stuck when switching from nvidia to
  nouveau and vice-versa

Status in software-properties package in Ubuntu:
  New

Bug description:
  Switching from nvidia to nouveau makes the gui to get stuck at
  "Applying changes..."

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1769338/+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 1769338] [NEW] software-properties-gtk gets stuck when switching from nvidia to nouveau and vice-versa

[Bump]

Public bug reported:

Switching from nvidia to nouveau makes the gui to get stuck at "Applying
changes..."

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

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

Title:
  software-properties-gtk  gets stuck when switching from nvidia to
  nouveau and vice-versa

Status in software-properties package in Ubuntu:
  New

Bug description:
  Switching from nvidia to nouveau makes the gui to get stuck at
  "Applying changes..."

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1769338/+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 1769056] Re: driverless printing generates wrong language/encoding PPD

[Naruhiko Ogasawara]

CUPS generate non-globalized PPD in this context, so I believe it should
put LanguageVersion/LanguageEncoding as follows the locale of strings,
not hard-code to English/ISOLatin1.

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

Title:
  driverless printing generates wrong language/encoding PPD

Status in cups package in Ubuntu:
  New

Bug description:
  The printing option dialog (see attached PNG file) is broken with Bionic 
Japanese environment.
  This issue seems to be coming from the generated PPD file with wrong 
language/encoding.

  I tried with Epson EP-879AW.

  Steps to reproduce:

  1) generate a print queue by driverless feature with ja-JP locale:

  $ LANG-ja_JP.UTF-8 lpadmin -p driverlesstest-ja -E -v `driverless` -m
  everywhere

  2) check the generated PPD (attached driverlesstest-ja.ppd)

  $ sudo less /etc/cups/ppd/driverlesstest-ja.ppd

  Expected: PPD have same language/encoding with content (if the content
  have Japanese, language/encoding should be Japanese/UTF-8)

  Actual: PPD has Japanese strings, but language/encoding is
  English/ISOLatin1

  
  
  Attached files:
   
  EPSON_EP_879A_Series_007.png: screenshot of printing option dialog of 
EP-879AW driverless print queue
  driverless-ja.ppd: PPD generated with ja_JP.UTF-8 locale
  driverless-en.ppd: PPD generated with C locale
  ipptool.txt: output of ipptool, by following command:

  $ ipptool -tv `driverless` get-printer-attributes.test > ipptool.txt

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1769056/+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 1769329] [NEW] package hostapd 2:2.6-15ubuntu2 failed to install/upgrade: installed hostapd package post-installation script subprocess returned error exit status 1

[noufal]

Public bug reported:

nothing just prompted me to do so

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: hostapd 2:2.6-15ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
AptOrdering:
 hostapd:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Sat May  5 14:05:44 2018
ErrorMessage: installed hostapd package post-installation script subprocess 
returned error exit status 1
InstallationDate: Installed on 2017-12-18 (137 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: wpa
Title: package hostapd 2:2.6-15ubuntu2 failed to install/upgrade: installed 
hostapd package post-installation script subprocess returned error exit status 1
UpgradeStatus: Upgraded to bionic on 2018-05-05 (0 days ago)

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


** Tags: amd64 apport-package bionic

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

Title:
  package hostapd 2:2.6-15ubuntu2 failed to install/upgrade: installed
  hostapd package post-installation script subprocess returned error
  exit status 1

Status in wpa package in Ubuntu:
  New

Bug description:
  nothing just prompted me to do so

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: hostapd 2:2.6-15ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  AptOrdering:
   hostapd:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat May  5 14:05:44 2018
  ErrorMessage: installed hostapd package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2017-12-18 (137 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: wpa
  Title: package hostapd 2:2.6-15ubuntu2 failed to install/upgrade: installed 
hostapd package post-installation script subprocess returned error exit status 1
  UpgradeStatus: Upgraded to bionic on 2018-05-05 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wpa/+bug/1769329/+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 1769325] Re: canonical-livepatch: unable to enable it through software-properties-gtk

[Hans Joachim Desserud]

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

** This bug has been marked a duplicate of bug 1769324
   canonical-livepatch: unable to enable it through software-properties-gtk

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

Title:
  canonical-livepatch: unable to enable it through software-properties-
  gtk

Status in software-properties package in Ubuntu:
  New

Bug description:
  Trying to enable canonical-livepatch through software-properties-gtk, the 
application itself gets stuck on access window.
  Nothing happens.

  Even when trying to enable canonical-livepatch through a terminal,
  running: sudo canonical-livepatch enable  I receive the message:
  "canonical-livepatch command not found"

  I succeded running the command through gksu

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: software-properties-gtk 0.96.24.32.1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat May  5 11:06:30 2018
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1769325/+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 1764087] Re: Wrongly boots into low graphics mode

[Dave Goldsbrough]

Cross reference now to a lightdm bug which has been raised as a consequence of 
https://bugs.freedesktop.org/show_bug.cgi?id=106407
saying it is not a xorg bug

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

Title:
  Wrongly boots into low graphics mode

Status in X.Org X server:
  Won't Fix
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  Lenovo T410 with VGA compatible controller [0300]: Intel Corporation
  Core Processor Integrated Graphics Controller [8086:0046] (rev 02)

  Booting from latest kernel ThinkPad-T410 4.13.0-38-generic
  #43~16.04.1-Ubuntu SMP Wed Mar 14 17:48:43 UTC 2018 x86_64 x86_64
  x86_64 GNU/Linux goes into low graphics mode and also effects wi-fi
  connection insofar as it does not connect to my router.

  Whereas booting from 4.13.0-37-generic #42~16.04.1-Ubuntu SMP Wed Mar
  7 16:03:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux works most of the
  time but occasionally has the same effects.

  I have had to submit this report after booting from 4.13.0.37 in order
  to submit bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun Apr 15 10:40:31 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Core Processor Integrated Graphics Controller [17aa:215a]
  InstallationDate: Installed on 2016-09-24 (567 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 2519Y11
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic 
root=UUID=58d362c2-ed1e-479b-84f5-e5d8a782b08f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/14/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6IET85WW (1.45 )
  dmi.board.name: 2519Y11
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6IET85WW(1.45):bd02/14/2013:svnLENOVO:pn2519Y11:pvrThinkPadT410:rvnLENOVO:rn2519Y11:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T410
  dmi.product.name: 2519Y11
  dmi.product.version: ThinkPad T410
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sun Apr 15 08:52:27 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1764087/+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 1769324] [NEW] canonical-livepatch: unable to enable it through software-properties-gtk

[vimo]

Public bug reported:

Trying to enable canonical-livepatch through software-properties-gtk, the 
application itself gets stuck on access window.
Nothing happens.

Even when trying to enable canonical-livepatch through a terminal,
running: sudo canonical-livepatch enable  I receive the message:
"canonical-livepatch command not found"

I succeded running the command through gksu

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: software-properties-gtk 0.96.24.32.1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: XFCE
Date: Sat May  5 11:06:30 2018
PackageArchitecture: all
SourcePackage: software-properties
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

** Attachment added: "screenshot showing the described issue"
   
https://bugs.launchpad.net/bugs/1769324/+attachment/5134261/+files/Istantanea_2018-05-05_11-12-42.png

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

Title:
  canonical-livepatch: unable to enable it through software-properties-
  gtk

Status in software-properties package in Ubuntu:
  New

Bug description:
  Trying to enable canonical-livepatch through software-properties-gtk, the 
application itself gets stuck on access window.
  Nothing happens.

  Even when trying to enable canonical-livepatch through a terminal,
  running: sudo canonical-livepatch enable  I receive the message:
  "canonical-livepatch command not found"

  I succeded running the command through gksu

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: software-properties-gtk 0.96.24.32.1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat May  5 11:06:30 2018
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1769324/+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 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.

[MasterCATZ]

slimjet is another victim

root@aio:/home/aio/Downloads# dpkg -i slimjet_amd64.deb 
Selecting previously unselected package slimjet.
(Reading database ... 682186 files and directories currently installed.)
Preparing to unpack slimjet_amd64.deb ...
Unpacking slimjet (18.0.5.0) ...
dpkg: dependency problems prevent configuration of slimjet:
 slimjet depends on libcurl3; however:
  Package libcurl3 is not installed.

dpkg: error processing package slimjet (--install):
 dependency problems - leaving unconfigured
Processing triggers for menu (2.1.47ubuntu2) ...
Processing triggers for gnome-menus (3.13.3-11ubuntu1) ...
Processing triggers for bamfdaemon (0.5.3+18.04.20180207.2-0ubuntu1) ...
Rebuilding /usr/share/applications/bamf-2.index...
Processing triggers for desktop-file-utils (0.23-1ubuntu3) ...
Processing triggers for mime-support (3.60ubuntu1) ...
Processing triggers for man-db (2.8.3-2) ...
Errors were encountered while processing:
 slimjet
root@aio:/home/aio/Downloads# apt install -f
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Correcting dependencies... Done
The following packages will be REMOVED:
  slimjet
0 to upgrade, 0 to newly install, 1 to remove and 20 not to upgrade.
1 not fully installed or removed.
After this operation, 260 MB disk space will be freed.
Do you want to continue? [Y/n] n
Abort.
root@aio:/home/aio/Downloads# apt install libcurl3
Reading package lists... Done
Building dependency tree   
Reading state information... Done
You might want to run 'apt --fix-broken install' to correct these.
The following packages have unmet dependencies:
 libcurl3 : Conflicts: libcurl4 but 7.58.0-2ubuntu3 is to be installed
 libcurl4 : Conflicts: libcurl3 but 7.58.0-2ubuntu2 is to be installed
E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or 
specify a solution).
root@aio:/home/aio/Downloads# apt --fix-broken install
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Correcting dependencies... Done
The following packages will be REMOVED:
  slimjet
0 to upgrade, 0 to newly install, 1 to remove and 20 not to upgrade.
1 not fully installed or removed.
After this operation, 260 MB disk space will be freed.
Do you want to continue? [Y/n] n
Abort.
root@aio:/home/aio/Downloads# uname -a
Linux aio 4.15.10-041510-generic #201803152130 SMP Thu Mar 15 21:32:57 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux
root@aio:/home/aio/Downloads#

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

Title:
  After last updated libcurl3 on libcurl4, some apps are removed.

Status in curl package in Ubuntu:
  Confirmed

Bug description:
  Hi!

  After last updated libcurl3 on libcurl4, system (Kubuntu 18.04 bionic) 
deleted such applications as:
  virtualbox-5.2
  opera-stable
  slack-desktop

  I really need these applications, I installed them with broken
  dependencies, but they are deleted after each update. Is it possible
  to make the dependence of the libcurl3 in libcurl4, and not remove it
  altogether from system?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1754294/+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 1769325] [NEW] canonical-livepatch: unable to enable it through software-properties-gtk

[vimo]

Public bug reported:

Trying to enable canonical-livepatch through software-properties-gtk, the 
application itself gets stuck on access window.
Nothing happens.

Even when trying to enable canonical-livepatch through a terminal,
running: sudo canonical-livepatch enable  I receive the message:
"canonical-livepatch command not found"

I succeded running the command through gksu

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: software-properties-gtk 0.96.24.32.1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: XFCE
Date: Sat May  5 11:06:30 2018
PackageArchitecture: all
SourcePackage: software-properties
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

** Attachment added: "screenshot showing the described issue"
   
https://bugs.launchpad.net/bugs/1769325/+attachment/5134265/+files/Istantanea_2018-05-05_11-12-42.png

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

Title:
  canonical-livepatch: unable to enable it through software-properties-
  gtk

Status in software-properties package in Ubuntu:
  New

Bug description:
  Trying to enable canonical-livepatch through software-properties-gtk, the 
application itself gets stuck on access window.
  Nothing happens.

  Even when trying to enable canonical-livepatch through a terminal,
  running: sudo canonical-livepatch enable  I receive the message:
  "canonical-livepatch command not found"

  I succeded running the command through gksu

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: software-properties-gtk 0.96.24.32.1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat May  5 11:06:30 2018
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1769325/+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 1769297] Re: resume from hibernation broken when resume image is autodetected

[Ubuntu Foundations Team Bug Bot]

** Tags added: patch

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

Title:
  resume from hibernation broken when resume image is autodetected

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  I found a reason of non-functioning resume from hibernation when
  resume partition/file is autodetected by intiramfs hook /usr/share
  /initramfs-tools/hooks/resume.

  Here is the scenario:
  1) hook /usr/share/initramfs-tools/hooks/resume creates config 
conf/conf.d/zz-resume-auto saved in initrd image, containing one variable: 
RESUME=UUID=106238b0-707d-4422-866d-a7534da50702 in my case

  2) during boot init script sets 'resume' variable to 'RESUME' value
  from conf/conf.d/zz-resume-auto, then it executes local-premount
  scripts including local-premount/resume

  3) resuming script local-premount/resume 
(/usr/share/initramfs-tools/scripts/local-premount/resume) tries to get resume 
device major-minor numbers by these lines:
  DEV=$(readlink ${resume})
  DEV=/sys/class/block/${DEV##*/}/dev
  if [ -r "$DEV" ]; then
  read MAJMIN < "$DEV"
  fi

  4) next check fails and resume process silently aborts:
  if [ -z "$MAJMIN" ]; then
  exit 1
  fi

  Resuming script fails to get device major-minor because
  resume=UUID=106238b0-707d-4422-866d-a7534da50702 -- it's not resolved
  into device path in init script.

  Commonly mentioned workaround is to explicitly specify kernel
  parameter resume=UUID=106238b0-707d-4422-866d-a7534da50702 -- only in
  this case init script resolves it to device path.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: initramfs-tools 0.130ubuntu3
  Uname: Linux 4.16.6-041606-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  5 11:32:31 2018
  InstallationDate: Installed on 2018-03-27 (38 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327)
  PackageArchitecture: all
  SourcePackage: initramfs-tools
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1769297/+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 1764087] Re: Wrongly boots into low graphics mode

[Bug Watch Updater]

** Changed in: xorg-server
   Status: Unknown => Won't Fix

** Changed in: xorg-server
   Importance: Unknown => High

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

Title:
  Wrongly boots into low graphics mode

Status in X.Org X server:
  Won't Fix
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  Lenovo T410 with VGA compatible controller [0300]: Intel Corporation
  Core Processor Integrated Graphics Controller [8086:0046] (rev 02)

  Booting from latest kernel ThinkPad-T410 4.13.0-38-generic
  #43~16.04.1-Ubuntu SMP Wed Mar 14 17:48:43 UTC 2018 x86_64 x86_64
  x86_64 GNU/Linux goes into low graphics mode and also effects wi-fi
  connection insofar as it does not connect to my router.

  Whereas booting from 4.13.0-37-generic #42~16.04.1-Ubuntu SMP Wed Mar
  7 16:03:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux works most of the
  time but occasionally has the same effects.

  I have had to submit this report after booting from 4.13.0.37 in order
  to submit bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun Apr 15 10:40:31 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Core Processor Integrated Graphics Controller [17aa:215a]
  InstallationDate: Installed on 2016-09-24 (567 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 2519Y11
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic 
root=UUID=58d362c2-ed1e-479b-84f5-e5d8a782b08f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/14/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6IET85WW (1.45 )
  dmi.board.name: 2519Y11
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6IET85WW(1.45):bd02/14/2013:svnLENOVO:pn2519Y11:pvrThinkPadT410:rvnLENOVO:rn2519Y11:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T410
  dmi.product.name: 2519Y11
  dmi.product.version: ThinkPad T410
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sun Apr 15 08:52:27 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1764087/+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 1769301] Re: useradd fails when selinux is set to permissive

[Andreas Florath]

In libselinux the setfscreatecon() function is implemented - which might
be the root cause of the problem.

** Package changed: shadow (Ubuntu) => libselinux (Ubuntu)

** Summary changed:

- useradd fails when selinux is set to permissive
+ resetting /proc/thread-self/attr/fscreate results in 'Invalid Argument'

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

Title:
  resetting /proc/thread-self/attr/fscreate results in 'Invalid
  Argument'

Status in libselinux package in Ubuntu:
  New

Bug description:
  root@ubuntu:~# useradd -g 100 tst003
  useradd: failure while writing changes to /etc/passwd

  root@ubuntu:~# sestatus 
  SELinux status: enabled
  SELinuxfs mount:/sys/fs/selinux
  SELinux root directory: /etc/selinux
  Loaded policy name: default
  Current mode:   permissive
  Mode from config file:  permissive
  Policy MLS status:  enabled
  Policy deny_unknown status: allowed
  Memory protection checking: requested (insecure)
  Max kernel policy version:  31

  
  The problem does not occur when SELinux is complete disabled.

  Please note that a very similar problem occurs using groupadd:

  root@ubuntu:~# groupadd tstgrp001
  groupadd: failure while writing changes to /etc/group

  
  = journal = 
  (Please note that there is *no* AVC!)

  May 05 05:11:44 ubuntu useradd[756]: new user: name=tst003, UID=1004, 
GID=100, home=/home/tst003, shell=/bin/sh
  May 05 05:11:44 ubuntu audit[756]: ADD_USER pid=756 uid=0 auid=1002 ses=1 
subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=adding user 
id=1004 exe="/usr/sbin/useradd" hostname=ubuntu addr=? terminal=pts/0 
res=success'
  May 05 05:11:44 ubuntu useradd[756]: failure while writing changes to 
/etc/passwd
  May 05 05:11:44 ubuntu audit[756]: ADD_USER pid=756 uid=0 auid=1002 ses=1 
subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=adding user 
acct="tst003" exe="/usr/sbin/useradd" hostname=ubuntu addr=? terminal=pts/0 
res=failed'
  May 05 05:11:44 ubuntu useradd[756]: failed adding user 'tst003', data deleted

  = ltrace =

  [pid 1074] SYS_write(12, "root:x:"..., 1360) = 1360
  [pid 1074] <... fflush resumed> )= 0
  [pid 1074] fileno(0x5595b21c6200)= 12
  [pid 1074] fsync(12, 0x5595b21c62e0, 0, 0x7ff933d5c154 
  [pid 1074] SYS_fsync(12) = 0
  [pid 1074] <... fsync resumed> ) = 0
  [pid 1074] fclose(0x5595b21c6200 
  [pid 1074] SYS_close(12) = 0
  [pid 1074] <... fclose resumed> )= 0
  [pid 1074] utime(0x7ffee34207e0, 0x7ffee34206b0, 0x5595b21af010, 1 

  [pid 1074] SYS_utime("/etc/passwd-", 0x7ffee34206b0) = 0
  [pid 1074] <... utime resumed> ) = 0
  [pid 1074] fclose(0x5595b21af2a0 
  [pid 1074] SYS_close(5)  = 0
  [pid 1074] <... fclose resumed> )= 0
  [pid 1074] setfscreatecon(0, 0x5595b21af118, 1, 2 
  [pid 1074] SYS_openat(0xff9c, 0x5595b21cebc0, 0x80002, 0) = 5
  [pid 1074] SYS_write(5, nil, 0)  = -22
  [pid 1074] SYS_close(5)  = 0
  [pid 1074] <... setfscreatecon resumed> )= 0x
  [pid 1074] free(0x5595b21b9dc0)  = 
  [pid 1074] free(0x5595b21b8a00)  = 
  [pid 1074] strlen("x")   = 1
  [pid 1074] memset(0x5595b21b7560, '\0', 1)   = 0x5595b21b7560
  [pid 1074] free(0x5595b21b7560)  = 
  [pid 1074] free(0x5595b21b94e0)  = 
  [pid 1074] free(0x5595b21b9000)  = 
  [pid 1074] free(0x5595b21b8fc0)  = 

  = strace =

  write(12, "root:x:"..., 1360) = 1360
  fsync(12)   = 0
  close(12)   = 0
  utime("/etc/passwd-", {actime=1525497034 /* 2018-05-05T05:10:34+ */, 
modtime=1525496803 /* 2018-05-05T05:06:43+ */}) = 0
  close(5)= 0
  openat(AT_FDCWD, "/proc/thread-self/attr/fscreate", O_RDWR|O_CLOEXEC) = 5
  write(5, NULL, 0)   = -1 EINVAL (Invalid argument)
  close(5)= 0

  = Version Information =
  root@ubuntu:~# lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  root@ubuntu:~# dpkg -l | grep passwd | grep -v base-pa
  ii  passwd1:4.5-1ubuntu1
amd64change and administer password and group data

  root@ubuntu:~# dpkg -l | grep selinux
  ii  libselinux1:amd64 2.7-2build2   
amd64SELinux runtime shared libraries
  ii  python3-selinux   2.7-2build2   
amd64Python3 bindings to SELinux shared libraries
  ii  selinux-basics   

[Touch-packages] [Bug 1769301] Re: useradd fails when selinux is set to permissive

[Andreas Florath]

It looks that the root cause affects multiple packages.

Observations: programs like lvchange have a similar problem:

# lvresize -L +1M /dev/mapper/vg-home
  SELinux context reset: setfscreatecon failed: Invalid argument
  SELinux context reset: setfscreatecon failed: Invalid argument
...

It looks that the problem might be in the libselinux (procattr.c
setprocattrcon_raw):

ret = write(fd, NULL, 0);   /* clear */

This always returns 'Invalid argument'.

I was not able to reproduce this with standard system tools (echo, cat, tee, 
...).
Therefore I wrote some lines of C (attached):

root@ubuntu:~# strace -f ./w2 
...
openat(AT_FDCWD, "/proc/thread-self/attr/fscreate", O_RDWR|O_CLOEXEC) = 3
write(3, NULL, 0)   = -1 EINVAL (Invalid argument)
dup(2)  = 4
fcntl(4, F_GETFL)   = 0x2 (flags O_RDWR)
brk(NULL)   = 0x55af7b32a000
brk(0x55af7b34b000) = 0x55af7b34b000
fstat(4, {st_mode=S_IFCHR|0600, st_rdev=makedev(136, 0), ...}) = 0
write(4, "write: Invalid argument\n", 24write: Invalid argument
) = 24
close(4)= 0
rt_sigprocmask(SIG_UNBLOCK, [ABRT], NULL, 8) = 0
rt_sigprocmask(SIG_BLOCK, ~[RTMIN RT_1], [], 8) = 0
getpid()= 10408
gettid()= 10408
tgkill(10408, 10408, SIGABRT)   = 0
rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
--- SIGABRT {si_signo=SIGABRT, si_code=SI_TKILL, si_pid=10408, si_uid=0} ---
+++ killed by SIGABRT +++
Aborted

I have no idea if this write(fd, NULL, 0) should work to reset the
attribute (then it might be a kernel /proc problem) or if the library
needs to use another mechanism to reset the content.


** Attachment added: "w2.c"
   
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1769301/+attachment/5134236/+files/w2.c

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

Title:
  resetting /proc/thread-self/attr/fscreate results in 'Invalid
  Argument'

Status in libselinux package in Ubuntu:
  New

Bug description:
  root@ubuntu:~# useradd -g 100 tst003
  useradd: failure while writing changes to /etc/passwd

  root@ubuntu:~# sestatus 
  SELinux status: enabled
  SELinuxfs mount:/sys/fs/selinux
  SELinux root directory: /etc/selinux
  Loaded policy name: default
  Current mode:   permissive
  Mode from config file:  permissive
  Policy MLS status:  enabled
  Policy deny_unknown status: allowed
  Memory protection checking: requested (insecure)
  Max kernel policy version:  31

  
  The problem does not occur when SELinux is complete disabled.

  Please note that a very similar problem occurs using groupadd:

  root@ubuntu:~# groupadd tstgrp001
  groupadd: failure while writing changes to /etc/group

  
  = journal = 
  (Please note that there is *no* AVC!)

  May 05 05:11:44 ubuntu useradd[756]: new user: name=tst003, UID=1004, 
GID=100, home=/home/tst003, shell=/bin/sh
  May 05 05:11:44 ubuntu audit[756]: ADD_USER pid=756 uid=0 auid=1002 ses=1 
subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=adding user 
id=1004 exe="/usr/sbin/useradd" hostname=ubuntu addr=? terminal=pts/0 
res=success'
  May 05 05:11:44 ubuntu useradd[756]: failure while writing changes to 
/etc/passwd
  May 05 05:11:44 ubuntu audit[756]: ADD_USER pid=756 uid=0 auid=1002 ses=1 
subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=adding user 
acct="tst003" exe="/usr/sbin/useradd" hostname=ubuntu addr=? terminal=pts/0 
res=failed'
  May 05 05:11:44 ubuntu useradd[756]: failed adding user 'tst003', data deleted

  = ltrace =

  [pid 1074] SYS_write(12, "root:x:"..., 1360) = 1360
  [pid 1074] <... fflush resumed> )= 0
  [pid 1074] fileno(0x5595b21c6200)= 12
  [pid 1074] fsync(12, 0x5595b21c62e0, 0, 0x7ff933d5c154 
  [pid 1074] SYS_fsync(12) = 0
  [pid 1074] <... fsync resumed> ) = 0
  [pid 1074] fclose(0x5595b21c6200 
  [pid 1074] SYS_close(12) = 0
  [pid 1074] <... fclose resumed> )= 0
  [pid 1074] utime(0x7ffee34207e0, 0x7ffee34206b0, 0x5595b21af010, 1 

  [pid 1074] SYS_utime("/etc/passwd-", 0x7ffee34206b0) = 0
  [pid 1074] <... utime resumed> ) = 0
  [pid 1074] fclose(0x5595b21af2a0 
  [pid 1074] SYS_close(5)  = 0
  [pid 1074] <... fclose resumed> )= 0
  [pid 1074] setfscreatecon(0, 0x5595b21af118, 1, 2 
  [pid 1074] SYS_openat(0xff9c, 0x5595b21cebc0, 0x80002, 0) = 5
  [pid 1074] SYS_write(5, nil, 0)  = -22
  [pid 1074] SYS_close(5)  = 0
  [pid 1074] <... setfscreatecon resumed> )= 0x
  [pid 1074] 

[Touch-packages] [Bug 1769299] Re: universal access zoom unusable

[whitis]

Problem reproduced on separate (virtual) machine, unmodified ubuntu live image.
   - Host system AMD Phenom II X6 1090T with 16GB RAM Ubuntu 14.04.4 LTS
   - virtualbox 14.3.36-dfsg-...
   - SATA 0: 8GB VMDK drive (new)
   - SATA 1: CD/ROM: ubuntu-18.04-desktop-amd64.iso
   - Base memory: 4GB (important, if you use 1GB, ubuntu will boot to 
desktop but nothing works)
 must have enough ram on host machine to permit this
   - Specific Virtual machine -> System -> Motherboard: Enable EFI: On
 otherwise it will not boot 
- Boot menu: TRY ubuntu without installing
- Show Applications (dash)-> Terminal
- Show Applications -> Settings-> Universal Access -> Always Show Universal 
Access Menu: On
- don't dismiss settings, we will use it about 8 steps below.
- Universal Access menu (round man in circle on top panel) -> Zoom: on
- Move pointer to upper left corner of desktop: note left panel (launcher) 
icons 
  cut in hafl, note top panel cut in half
- move to top right
- click on whats left of universal access menu icon to pull down menu, note 
it is drawn incorrectly
- move mouse down and to the left and notice how these panels/pull down 
menus scroll independently and incorrectly.
- try to turn off the zoom in the univeral access pull down menu.  Try to 
read the word zoom, now you cant see the control, move to see the control now 
you can't see the word.  But in this case, you can actually get there.  
 - turn zoom back on
 - move mouse pointer to upper right hand corner.  Make sure either the 
universal access or the system menu is pulled down
 - move mouse down and left to the words "sound keys" in the settings menu 
(control panel,
 not the pull down menu) for universal access.  Leave the mouse pointer 
there for a 
 few seconds.   Display will pan to upper right hand corner without 
permission.
  - If you repeat this without either of the two pull down menus activated, 
it will jump
to the highlighted "Universal Access" on the left side of the settings 
window.
 This jumping action severely interfered with issuing screenshot commands 
in terminal and
 it will interfere with many other operations as well.   


  


Behavior of program suggests that the screen is being composited of the 
following elements:
   - desktop background
   - application window 1
   - application window 2
   - application window 3 ...
   - top panel
   - left panel (launcher)
   - pull down menu
The first four items appear to be correctly composited together before applying 
the zoom and pan operation but the last three appear to not be composited onto 
the desktop+applications before zoom and pan is applied.  The size of their 
windows has not been enlarged, only the contents.

Add to paragraph about obfuscating the identity of the programs the user
is interacting with: Universal Pull down menu also doesn't have "Help"
or report bug menu items.

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

Title:
  universal access zoom unusable

Status in xorg package in Ubuntu:
  New

Bug description:
  
  Filed by mark on behalf of low vision user Ken.   Ken is able to read 56 
point type without magnification at normal reading distance and can barely read 
the universal access "large text" from a distance of about 2.5 inches from a 
26inch monitor at 1360x768.   So he really needs magnification and a lot more 
than the 2x default I used here for testing.   We do not live in the same town 
so providing additional details would be slow.

  Turned on zoom from the universal access button on top panel.
  Default settings were used including Zoom = 2.0, screen part = full

  Several areas are corrupted.  These zoom and scroll separately from
  the rest of the screen and in a way that severely impairs use as
  portions may not ever be visible.   Portions of these subwindows
  cannot be used because you have to move the mouse off them to be able
  see them so you can either see or click but not both.

  These areas are:
- The top panel
- The left panel (launcher)  (intermittently)
- pull down menus, particularly the universal access pull down from the top 
panel

  
  Also, the zoom randomly every couple seconds. jumps to a different position 
without the user's consent.   This appeared to be because text was printed by a 
program running in the terminal window (long apt-get install) but continued to 
happen even when that window was minimized and even when that program stopped 
printing.

  These problems persisted with all the other zoom modes.   One mode,
  however, created new bugs.  With "magnifier extends outside of
  screen", you lose the ability to see the top and left panels at all;
  you can pan over where they would be but they are not drawn.   Can't
  open the pulldown menu since 

[Touch-packages] [Bug 1769316] [NEW] Notification of Live patch sign-in is inconsistent depending on how Software & Updates is started

[Paul White]

Public bug reported:

This issue has I think been partly covered in other bug reports that are
currently marked incomplete but none describe my exact issue with
Livepatch signing in..

I'm creating this report in the hope that it does provide enough
information with regards to what I am seeing here and have been doing so
since before the release of Ubuntu 18.04.

Last night I enabled Livepatch by signing into the appropriate tab of
Software & Updates. As a result of briefly discussing this elsewhere I
decided to check whether I was still logged in or not.

1) I started synaptic and pulled up "Software & Updates" from the
Settings menu. The Updates tab shows the Livepatch box as being checked
but a message of "To use Livepatch you need to sign in" and a Sign-in
button is displayed. If I attempt to sign in I see a "Choose an account"
dialog. Clicking on "Sign in.." displays an empty panel with "Devices"
in the top left corner. This is obviously the Settings application with
no text being displayed.

2) I then started "Software & Updates" as a stand alone application. The
Updates tab shows that I am signed in, my email address is shown along
with a "Sign out" button and the message "Use Canonical Livepatch to
increase security between restarts is displayed immediately above.

Restarting "Software & Updates" alternately through synaptic and as a
stand alone application shows either an unsuccessful login or a
successful log-in as described in points 1) and 2).

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: software-properties-gtk 0.96.24.32.1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: GNOME
Date: Sat May  5 08:38:38 2018
InstallationDate: Installed on 2017-11-07 (178 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
PackageArchitecture: all
SourcePackage: software-properties
UpgradeStatus: Upgraded to bionic on 2018-02-21 (72 days ago)

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


** Tags: amd64 apport-bug bionic livepatch

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

Title:
  Notification of Live patch sign-in is inconsistent depending on how
  Software & Updates is started

Status in software-properties package in Ubuntu:
  New

Bug description:
  This issue has I think been partly covered in other bug reports that
  are currently marked incomplete but none describe my exact issue with
  Livepatch signing in..

  I'm creating this report in the hope that it does provide enough
  information with regards to what I am seeing here and have been doing
  so since before the release of Ubuntu 18.04.

  Last night I enabled Livepatch by signing into the appropriate tab of
  Software & Updates. As a result of briefly discussing this elsewhere I
  decided to check whether I was still logged in or not.

  1) I started synaptic and pulled up "Software & Updates" from the
  Settings menu. The Updates tab shows the Livepatch box as being
  checked but a message of "To use Livepatch you need to sign in" and a
  Sign-in button is displayed. If I attempt to sign in I see a "Choose
  an account" dialog. Clicking on "Sign in.." displays an empty panel
  with "Devices" in the top left corner. This is obviously the Settings
  application with no text being displayed.

  2) I then started "Software & Updates" as a stand alone application.
  The Updates tab shows that I am signed in, my email address is shown
  along with a "Sign out" button and the message "Use Canonical
  Livepatch to increase security between restarts is displayed
  immediately above.

  Restarting "Software & Updates" alternately through synaptic and as a
  stand alone application shows either an unsuccessful login or a
  successful log-in as described in points 1) and 2).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: software-properties-gtk 0.96.24.32.1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat May  5 08:38:38 2018
  InstallationDate: Installed on 2017-11-07 (178 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to bionic on 2018-02-21 (72 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1769316/+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 1764087] Re: Wrongly boots into low graphics mode

[Dave Goldsbrough]

** Bug watch added: freedesktop.org Bugzilla #106407
   https://bugs.freedesktop.org/show_bug.cgi?id=106407

** Also affects: xorg-server via
   https://bugs.freedesktop.org/show_bug.cgi?id=106407
   Importance: Unknown
   Status: Unknown

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

Title:
  Wrongly boots into low graphics mode

Status in X.Org X server:
  Unknown
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  Lenovo T410 with VGA compatible controller [0300]: Intel Corporation
  Core Processor Integrated Graphics Controller [8086:0046] (rev 02)

  Booting from latest kernel ThinkPad-T410 4.13.0-38-generic
  #43~16.04.1-Ubuntu SMP Wed Mar 14 17:48:43 UTC 2018 x86_64 x86_64
  x86_64 GNU/Linux goes into low graphics mode and also effects wi-fi
  connection insofar as it does not connect to my router.

  Whereas booting from 4.13.0-37-generic #42~16.04.1-Ubuntu SMP Wed Mar
  7 16:03:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux works most of the
  time but occasionally has the same effects.

  I have had to submit this report after booting from 4.13.0.37 in order
  to submit bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sun Apr 15 10:40:31 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Core Processor Integrated Graphics Controller [17aa:215a]
  InstallationDate: Installed on 2016-09-24 (567 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 2519Y11
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic 
root=UUID=58d362c2-ed1e-479b-84f5-e5d8a782b08f ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/14/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6IET85WW (1.45 )
  dmi.board.name: 2519Y11
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6IET85WW(1.45):bd02/14/2013:svnLENOVO:pn2519Y11:pvrThinkPadT410:rvnLENOVO:rn2519Y11:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T410
  dmi.product.name: 2519Y11
  dmi.product.version: ThinkPad T410
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sun Apr 15 08:52:27 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1764087/+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 1768906] Re: Xorg crash

[dino99]

Difference between remove & purge:
- 'remove' uninstall the package, but does not remove the package settings, 
which can disturb the system and conflict with an other driver choice.
- 'purge' remove both package & its settings; that is way recommended.

About /etc/X11/xorg.conf, this is no more used since a couple releases.
so your system should not finf such a path anyway.

Your real problem is not about 'xorg' as you have reported but 'gdm' and/or 
'gnome-session'
**
May 3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) NVIDIA(GPU-0): 
Failed to acquire modesetting permission.
May 3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) NVIDIA(0): 
Failing initialization of X screen 0
**

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  When attempting to log in to a newly updated bionic beaver via the
  display manager (I think this is the right term), I immediately see a
  crash, a return to the user selection/login screen and a no-longer
  functioning keyboard and mouse. This happens both with the proprietary
  driver installed drivers and with the apt installed nvidia-driver-396.

  some interesting tidbits from the syslog file are:

  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) NVIDIA(GPU-0): 
Failed to acquire modesetting permission.
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) NVIDIA(0): 
Failing initialization of X screen 0
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) UnloadModule: 
"nvidia"
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) 
UnloadSubModule: "wfb"
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) 
UnloadSubModule: "fb"
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) Screen(s) 
found, but none have a usable configuration.
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE)
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: Fatal server error:
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) no screens 
found(EE)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17
  Uname: Linux 4.15.0-20-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .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  396.24  Thu Apr 26 00:10:09 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu May  3 09:28:59 2018
  DistUpgraded: 2018-05-02 07:25:10,524 DEBUG failed to SystemUnLock() (E:Not 
locked)
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 396.24, 4.15.0-20-lowlatency, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GK104 [GeForce GTX 770] [10de:1184] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. GK104 [GeForce GTX 770] [3842:2774]
  MachineType: ASUS All Series
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-lowlatency 
root=UUID=f308f075-bd97-4230-9d24-3ab727b0036b ro splash quiet nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to bionic on 2018-05-02 (1 days ago)
  dmi.bios.date: 08/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1603
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MAXIMUS VI GENE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1603:bd08/15/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIGENE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 

[Touch-packages] [Bug 1768661] Re: can't make WIFI work

[Dave Goldsbrough]

At a terminal screen have you tried entering the command?

sudo service network-manager restart

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

Title:
  can't make WIFI work

Status in xorg package in Ubuntu:
  New

Bug description:
  I can't make the WIfFI operate Compact Presario V2000

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 4.2.0-42.49~14.04.1-generic 4.2.8-ckt12
  Uname: Linux 4.2.0-42-generic i686
  NonfreeKernelModules: wl
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.27
  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 May  2 17:05:59 2018
  DistUpgraded: 2018-05-01 16:52:36,093 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus: ndiswrapper, 1.59: added
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS480M [Mobility Radeon Xpress 200] 
[1002:5955] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:3091]
  InstallationDate: Installed on 2018-05-01 (1 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 
(20160217.1)
  Lsusb:
   Bus 001 Device 011: ID 0bda:8179 Realtek Semiconductor Corp. RTL8188EUS 
802.11n Wireless Network Adapter
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Hewlett-Packard Presario V2000 (EP377UA#ABA)
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-42-generic 
root=UUID=3698752e-32a7-443e-959d-c4578e3e85a3 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to trusty on 2018-05-01 (1 days ago)
  dmi.bios.date: 01/02/2006
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.22
  dmi.board.name: 3097
  dmi.board.vendor: Quanta
  dmi.board.version: 47.0F
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.22:bd01/02/2006:svnHewlett-Packard:pnPresarioV2000(EP377UA#ABA):pvrRev1:rvnQuanta:rn3097:rvr47.0F:cvnQuanta:ct10:cvrN/A:
  dmi.product.name: Presario V2000 (EP377UA#ABA)
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri N/A
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Wed May  2 12:26:46 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.2-1ubuntu9.1~trusty1
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1768661/+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 1768906] Re: Xorg crash

[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/1768906

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  When attempting to log in to a newly updated bionic beaver via the
  display manager (I think this is the right term), I immediately see a
  crash, a return to the user selection/login screen and a no-longer
  functioning keyboard and mouse. This happens both with the proprietary
  driver installed drivers and with the apt installed nvidia-driver-396.

  some interesting tidbits from the syslog file are:

  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) NVIDIA(GPU-0): 
Failed to acquire modesetting permission.
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) NVIDIA(0): 
Failing initialization of X screen 0
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) UnloadModule: 
"nvidia"
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) 
UnloadSubModule: "wfb"
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (II) 
UnloadSubModule: "fb"
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) Screen(s) 
found, but none have a usable configuration.
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE)
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: Fatal server error:
  May  3 09:20:18 madbox /usr/lib/gdm3/gdm-x-session[2748]: (EE) no screens 
found(EE)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17
  Uname: Linux 4.15.0-20-lowlatency x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .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  396.24  Thu Apr 26 00:10:09 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu May  3 09:28:59 2018
  DistUpgraded: 2018-05-02 07:25:10,524 DEBUG failed to SystemUnLock() (E:Not 
locked)
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 396.24, 4.15.0-20-lowlatency, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation GK104 [GeForce GTX 770] [10de:1184] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: eVga.com. Corp. GK104 [GeForce GTX 770] [3842:2774]
  MachineType: ASUS All Series
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-lowlatency 
root=UUID=f308f075-bd97-4230-9d24-3ab727b0036b ro splash quiet nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to bionic on 2018-05-02 (1 days ago)
  dmi.bios.date: 08/15/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1603
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MAXIMUS VI GENE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1603:bd08/15/2014:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIGENE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: ASUS MB
  dmi.product.name: All Series
  dmi.product.version: System Version
  dmi.sys.vendor: ASUS
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Thu May  3 09:20:03 2018
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu4

To manage notifications about this bug go to:

[Touch-packages] [Bug 1769029] Re: Display on Dell 1440x900 is not available

[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/1769029

Title:
  Display on Dell 1440x900 is not available

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Monitor resolution is limited to 1024x768 with no option for higher
  resolution

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May  4 09:44:54 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  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: Gigabyte Technology Co., Ltd 82945G/GZ Integrated Graphics 
Controller [1458:d000]
  InstallationDate: Installed on 2018-05-03 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Gigabyte Technology Co., Ltd. 945GZM-S2
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=2429ce45-7592-4cb5-974d-7446cb495a5b ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/26/2007
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FG
  dmi.board.name: 945GZM-S2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFG:bd04/26/2007:svnGigabyteTechnologyCo.,Ltd.:pn945GZM-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rn945GZM-S2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: 945GZM-S2
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1769029/+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 1769029] Re: Display on Dell 1440x900 is not available

[Dave Goldsbrough]

Many bugs are now accumulating with this and similar issues surrounding Xorg. 
This is just one example 
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1764087
There are others. Some are related to Lenovo laptops but not all.
Shame that 18.04 LTS has been allowed to be released without this inherent bug 
being fixed. It is damaging Ubuntu reputation.

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

Title:
  Display on Dell 1440x900 is not available

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Monitor resolution is limited to 1024x768 with no option for higher
  resolution

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May  4 09:44:54 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  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: Gigabyte Technology Co., Ltd 82945G/GZ Integrated Graphics 
Controller [1458:d000]
  InstallationDate: Installed on 2018-05-03 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Gigabyte Technology Co., Ltd. 945GZM-S2
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=2429ce45-7592-4cb5-974d-7446cb495a5b ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/26/2007
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FG
  dmi.board.name: 945GZM-S2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFG:bd04/26/2007:svnGigabyteTechnologyCo.,Ltd.:pn945GZM-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rn945GZM-S2:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: 945GZM-S2
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1769029/+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 1769022] Re: ubuntu 18.04 freezes after the login

[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/1769022

Title:
  ubuntu 18.04 freezes after the login

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I am not able to log to ubuntu 18.04 after the upgrade. When I login I
  get setup screen with the word "Welcome" and the system freezes

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu May  3 23:29:56 2018
  DistUpgraded: 2018-05-03 01:59:32,397 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] BeaverCreek [Radeon HD 6520G] 
[1002:9647] (prog-if 00 [VGA controller])
 Subsystem: Lenovo BeaverCreek [Radeon HD 6520G] [17aa:3971]
  InstallationDate: Installed on 2016-11-19 (530 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 129925U
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=91dffd26-787f-4656-94b0-9568086633ac ro radeon.dpm=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-05-03 (0 days ago)
  dmi.bios.date: 07/20/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 54CN18WW
  dmi.board.asset.tag: Base Board Asset Tag Unknown
  dmi.board.name: Torpedo
  dmi.board.vendor: LENOVO
  dmi.board.version: 109-C06210-00B
  dmi.chassis.asset.tag: Chassis Asset Tag Unknown
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Chassis Version Unknown
  dmi.modalias: 
dmi:bvnLENOVO:bvr54CN18WW:bd07/20/2011:svnLENOVO:pn129925U:pvrIdeapadZ575:rvnLENOVO:rnTorpedo:rvr109-C06210-00B:cvnLENOVO:ct10:cvrChassisVersionUnknown:
  dmi.product.family: IDEAPAD
  dmi.product.name: 129925U
  dmi.product.version: Ideapad Z575
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Thu May  3 22:52:41 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1769022/+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 1769058] Re: Xorg freeze

[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/1769058

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I have upgraded ubuntu form 17.10 to 18.04, but after login in Gnome or 
Ubuntu desktop environment, UI is not responding. No mouse no keyboard, every 
thing is frozen, even i can't logout from screen. i have to manually turnoff 
the laptop.
  Currently i am using deepin desktop environment.
  Please do the needful.

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: Deepin
  Date: Fri May  4 12:02:20 2018
  DistUpgraded: 2018-04-28 03:31:09,905 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:5002]
  InstallationDate: Installed on 2017-03-30 (399 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  MachineType: LENOVO 20140
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=871acc38-6b5a-4871-8105-c9af13662669 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (6 days ago)
  dmi.bios.date: 04/10/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: H1ET73WW(1.16)
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20140
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrH1ET73WW(1.16):bd04/10/2013:svnLENOVO:pn20140:pvrLenovoB480:rvnLENOVO:rn20140:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: Lenovo B480
  dmi.product.name: 20140
  dmi.product.version: Lenovo B480
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1769058/+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 1769022] Re: ubuntu 18.04 freezes after the login

[Dave Goldsbrough]

Many bugs are now accumulating with this and similar issues surrounding Xorg. 
This is just one example 
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1764087
There are others. Some are related to Lenovo laptops but not all.
Shame that 18.04 LTS has been allowed to be released without this inherent bug 
being fixed. It is damaging Ubuntu reputation.

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

Title:
  ubuntu 18.04 freezes after the login

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I am not able to log to ubuntu 18.04 after the upgrade. When I login I
  get setup screen with the word "Welcome" and the system freezes

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu May  3 23:29:56 2018
  DistUpgraded: 2018-05-03 01:59:32,397 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] BeaverCreek [Radeon HD 6520G] 
[1002:9647] (prog-if 00 [VGA controller])
 Subsystem: Lenovo BeaverCreek [Radeon HD 6520G] [17aa:3971]
  InstallationDate: Installed on 2016-11-19 (530 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: LENOVO 129925U
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=91dffd26-787f-4656-94b0-9568086633ac ro radeon.dpm=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-05-03 (0 days ago)
  dmi.bios.date: 07/20/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 54CN18WW
  dmi.board.asset.tag: Base Board Asset Tag Unknown
  dmi.board.name: Torpedo
  dmi.board.vendor: LENOVO
  dmi.board.version: 109-C06210-00B
  dmi.chassis.asset.tag: Chassis Asset Tag Unknown
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Chassis Version Unknown
  dmi.modalias: 
dmi:bvnLENOVO:bvr54CN18WW:bd07/20/2011:svnLENOVO:pn129925U:pvrIdeapadZ575:rvnLENOVO:rnTorpedo:rvr109-C06210-00B:cvnLENOVO:ct10:cvrChassisVersionUnknown:
  dmi.product.family: IDEAPAD
  dmi.product.name: 129925U
  dmi.product.version: Ideapad Z575
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Thu May  3 22:52:41 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1769022/+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 1769091] Re: Xorg freeze on login

[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/1769091

Title:
  Xorg freeze on login

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 18.04.
  If I give a wrong password during the login, it of course fails, and write an 
error message.
  But after I give the correct passord, the display freezes, I have to stop the 
PC, and start again.
  If after the giving the wrong password, I push the cancel and then I give the 
correct passord, everything is fine.
  This behavior occurs either on my real laptop either on vitualbox gest.

  Other problem:
  On virtualbox many thime (50%) freeses during the startup with the splash 
image, but this only happened on virtualbox gest, but not on the real laptop.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May  4 10:05:01 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GpuHangFrequency: I don't know
  GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter 
[80ee:beef] (prog-if 00 [VGA controller])
  InstallationDate: Installed on 2018-04-27 (6 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  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.15.0-20-generic 
root=UUID=03a9742e-c894-4b5a-9000-099248693bf6 ro quiet splash
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  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.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1769091/+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 1769270] Re: Xorg freeze

[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/1769270

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I have a Lenovo T430.
  When I reboot the screen will freeze (requires reboot) before the login 
prompt if I have both my digital display port and vga plugged in while my 
laptop is open. If I unplug the external monitors it boots fine. If I boot then 
quickly close the laptop screen it boots fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May  4 14:14:56 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f3]
  InstallationDate: Installed on 2018-05-04 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LENOVO 23472P2
  ProcEnviron:
   PATH=(custom, no User Name)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/08/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ET93WW (2.53 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 23472P2
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 Pro DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG1ET93WW(2.53):bd03/08/2013:svnLENOVO:pn23472P2:pvrThinkPadT430:rvnLENOVO:rn23472P2:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430
  dmi.product.name: 23472P2
  dmi.product.version: ThinkPad T430
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1769270/+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 1769091] Re: Xorg freeze on login

[Dave Goldsbrough]

Many bugs are now accumulating with this and similar issues surrounding Xorg. 
This is just one example 
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1764087
There are others. Some are related to Lenovo laptops but not all.
Shame that 18.04 LTS has been allowed to be released without this inherent bug 
being fixed. It is damaging Ubuntu reputation.

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

Title:
  Xorg freeze on login

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 18.04.
  If I give a wrong password during the login, it of course fails, and write an 
error message.
  But after I give the correct passord, the display freezes, I have to stop the 
PC, and start again.
  If after the giving the wrong password, I push the cancel and then I give the 
correct passord, everything is fine.
  This behavior occurs either on my real laptop either on vitualbox gest.

  Other problem:
  On virtualbox many thime (50%) freeses during the startup with the splash 
image, but this only happened on virtualbox gest, but not on the real laptop.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May  4 10:05:01 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GpuHangFrequency: I don't know
  GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter 
[80ee:beef] (prog-if 00 [VGA controller])
  InstallationDate: Installed on 2018-04-27 (6 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  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.15.0-20-generic 
root=UUID=03a9742e-c894-4b5a-9000-099248693bf6 ro quiet splash
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  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.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1769091/+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 1769270] Re: Xorg freeze

[Dave Goldsbrough]

Many bugs are now accumulating with this and similar issues surrounding Xorg.  
This is just one example 
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1764087
There are others.  Some are related to Lenovo laptops but not all.
Shame that 18.04 LTS has been allowed to be released without this inherent bug 
being fixed.  It is damaging Ubuntu reputation.

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I have a Lenovo T430.
  When I reboot the screen will freeze (requires reboot) before the login 
prompt if I have both my digital display port and vga plugged in while my 
laptop is open. If I unplug the external monitors it boots fine. If I boot then 
quickly close the laptop screen it boots fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May  4 14:14:56 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f3]
  InstallationDate: Installed on 2018-05-04 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LENOVO 23472P2
  ProcEnviron:
   PATH=(custom, no User Name)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/08/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ET93WW (2.53 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 23472P2
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 Pro DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG1ET93WW(2.53):bd03/08/2013:svnLENOVO:pn23472P2:pvrThinkPadT430:rvnLENOVO:rn23472P2:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430
  dmi.product.name: 23472P2
  dmi.product.version: ThinkPad T430
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1769270/+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 1769301] [NEW] useradd fails when selinux is set to permissive

[Andreas Florath]

Public bug reported:

root@ubuntu:~# useradd -g 100 tst003
useradd: failure while writing changes to /etc/passwd

root@ubuntu:~# sestatus 
SELinux status: enabled
SELinuxfs mount:/sys/fs/selinux
SELinux root directory: /etc/selinux
Loaded policy name: default
Current mode:   permissive
Mode from config file:  permissive
Policy MLS status:  enabled
Policy deny_unknown status: allowed
Memory protection checking: requested (insecure)
Max kernel policy version:  31


The problem does not occur when SELinux is complete disabled.

Please note that a very similar problem occurs using groupadd:

root@ubuntu:~# groupadd tstgrp001
groupadd: failure while writing changes to /etc/group


= journal = 
(Please note that there is *no* AVC!)

May 05 05:11:44 ubuntu useradd[756]: new user: name=tst003, UID=1004, GID=100, 
home=/home/tst003, shell=/bin/sh
May 05 05:11:44 ubuntu audit[756]: ADD_USER pid=756 uid=0 auid=1002 ses=1 
subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=adding user 
id=1004 exe="/usr/sbin/useradd" hostname=ubuntu addr=? terminal=pts/0 
res=success'
May 05 05:11:44 ubuntu useradd[756]: failure while writing changes to 
/etc/passwd
May 05 05:11:44 ubuntu audit[756]: ADD_USER pid=756 uid=0 auid=1002 ses=1 
subj=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 msg='op=adding user 
acct="tst003" exe="/usr/sbin/useradd" hostname=ubuntu addr=? terminal=pts/0 
res=failed'
May 05 05:11:44 ubuntu useradd[756]: failed adding user 'tst003', data deleted

= ltrace =

[pid 1074] SYS_write(12, "root:x:"..., 1360) = 1360
[pid 1074] <... fflush resumed> )= 0
[pid 1074] fileno(0x5595b21c6200)= 12
[pid 1074] fsync(12, 0x5595b21c62e0, 0, 0x7ff933d5c154 
[pid 1074] SYS_fsync(12) = 0
[pid 1074] <... fsync resumed> ) = 0
[pid 1074] fclose(0x5595b21c6200 
[pid 1074] SYS_close(12) = 0
[pid 1074] <... fclose resumed> )= 0
[pid 1074] utime(0x7ffee34207e0, 0x7ffee34206b0, 0x5595b21af010, 1 
[pid 1074] SYS_utime("/etc/passwd-", 0x7ffee34206b0) = 0
[pid 1074] <... utime resumed> ) = 0
[pid 1074] fclose(0x5595b21af2a0 
[pid 1074] SYS_close(5)  = 0
[pid 1074] <... fclose resumed> )= 0
[pid 1074] setfscreatecon(0, 0x5595b21af118, 1, 2 
[pid 1074] SYS_openat(0xff9c, 0x5595b21cebc0, 0x80002, 0) = 5
[pid 1074] SYS_write(5, nil, 0)  = -22
[pid 1074] SYS_close(5)  = 0
[pid 1074] <... setfscreatecon resumed> )= 0x
[pid 1074] free(0x5595b21b9dc0)  = 
[pid 1074] free(0x5595b21b8a00)  = 
[pid 1074] strlen("x")   = 1
[pid 1074] memset(0x5595b21b7560, '\0', 1)   = 0x5595b21b7560
[pid 1074] free(0x5595b21b7560)  = 
[pid 1074] free(0x5595b21b94e0)  = 
[pid 1074] free(0x5595b21b9000)  = 
[pid 1074] free(0x5595b21b8fc0)  = 

= strace =

write(12, "root:x:"..., 1360) = 1360
fsync(12)   = 0
close(12)   = 0
utime("/etc/passwd-", {actime=1525497034 /* 2018-05-05T05:10:34+ */, 
modtime=1525496803 /* 2018-05-05T05:06:43+ */}) = 0
close(5)= 0
openat(AT_FDCWD, "/proc/thread-self/attr/fscreate", O_RDWR|O_CLOEXEC) = 5
write(5, NULL, 0)   = -1 EINVAL (Invalid argument)
close(5)= 0

= Version Information =
root@ubuntu:~# lsb_release -rd
Description:Ubuntu 18.04 LTS
Release:18.04

root@ubuntu:~# dpkg -l | grep passwd | grep -v base-pa
ii  passwd1:4.5-1ubuntu1
amd64change and administer password and group data

root@ubuntu:~# dpkg -l | grep selinux
ii  libselinux1:amd64 2.7-2build2   
amd64SELinux runtime shared libraries
ii  python3-selinux   2.7-2build2   
amd64Python3 bindings to SELinux shared libraries
ii  selinux-basics0.5.6 all 
 SELinux basic support
ii  selinux-policy-default2:2.20180114-1all 
 Strict and Targeted variants of the SELinux policy
ii  selinux-policy-dev2:2.20180114-1all 
 Headers from the SELinux reference policy for building modules
ii  selinux-utils 2.7-2build2   
amd64SELinux utility programs

root@ubuntu:~# uname -a
Linux ubuntu 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

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

-- 
You received this bug notification because you are a