from:"Dan Kortschak"

[Touch-packages] [Bug 1722478] Re: Two-finger scrolling and click-and-drag no longer works after resuming from suspend

2020-01-24 Thread Dan Kortschak

Also on 18.04.3 with 5.3.0-26-generic on a clevo p650re.

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

Title:
  Two-finger scrolling and click-and-drag no longer works after resuming
  from suspend

Status in Linux:
  Confirmed
Status in kmod package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete

Bug description:
  I own a Thinkpad T440p onto which I have had Debian 9 running without
  hardware issues. I have recently installed Ubuntu 17.10 final beta to
  test it out, but two-finger scrolling does not work at the moment. It
  used to work out-of-the-box from the final beta iso, but a subsequent
  update broke it.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-12-generic 4.13.0-12.13 [modified: 
boot/vmlinuz-4.13.0-12-generic]
  ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
  Uname: Linux 4.13.0-12-generic x86_64
  ApportVersion: 2.20.7-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ghislain  10620 F pulseaudio
   /dev/snd/controlC0:  ghislain  10620 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 10 09:20:01 2017
  HibernationDevice: RESUME=UUID=ae4cca1e-80ef-4a1e-87e3-0a860b49492e
  InstallationDate: Installed on 2017-10-05 (4 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  MachineType: LENOVO 20AN00C1UK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-12-generic 
root=/dev/mapper/doc1485--lap--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-12-generic N/A
   linux-backports-modules-4.13.0-12-generic  N/A
   linux-firmware 1.169
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/31/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: GLET83WW (2.37 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20AN00C1UK
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0E50510 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrGLET83WW(2.37):bd03/31/2016:svnLENOVO:pn20AN00C1UK:pvrThinkPadT440p:rvnLENOVO:rn20AN00C1UK:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T440p
  dmi.product.name: 20AN00C1UK
  dmi.product.version: ThinkPad T440p
  dmi.sys.vendor: LENOVO

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

-- 
Mailing list: https://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 1834554] [NEW] Screen displays dynamic corruptions

2019-06-27 Thread Dan Kortschak

Public bug reported:

Regularly the screen displays corruptions that change depending on disk
i/o, keyboard/mouse and other system activity. The screen corruptions do
not appear on each session and can be removed by selecting an
alternative resolution and then changing back (or reverting without
accepting the change).

The location of the corruptions is stereotypical and always has the same
shape characteristics.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.18.0-24.25~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-24-generic x86_64
NonfreeKernelModules: nvidia
.proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.107  Thu May 24 21:54:01 
PDT 2018
 GCC version:  gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
.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.9-0ubuntu7.6
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
Date: Fri Jun 28 12:14:17 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 nvidia-340, 340.107, 4.18.0-15-generic, x86_64: installed
 nvidia-340, 340.107, 4.18.0-24-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 NVIDIA Corporation GT200b [GeForce GTX 275] [10de:05e6] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: CardExpert Technology GT200b [GeForce GTX 275] [10b0:0801]
 Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1002:67df] (rev e7) (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd Ellesmere [Radeon RX 
470/480/570/580] [1458:22fc]
InstallationDate: Installed on 2019-06-25 (2 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
MachineType: System manufacturer System Product Name
ProcEnviron:
 LANGUAGE=en_AU:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-24-generic 
root=UUID=b92b7098-365d-445a-b980-7fe3bc3b73da ro quiet splash vt.handoff=1
Renderer: Software
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/19/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0504
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P6T DELUXE V2
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.:bvr0504:bd05/19/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6TDELUXEV2:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug bionic corruption 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/1834554

Title:
  Screen displays dynamic corruptions

Status in xorg package in Ubuntu:
  New

Bug description:
  Regularly the screen displays corruptions that change depending on
  disk i/o, keyboard/mouse and other system activity. The screen
  corruptions do not appear on each session and can be removed by
  selecting an alternative resolution and then changing back (or
  reverting without accepting the change).

  The location of the corruptions is stereotypical and always has the
  same shape characteristics.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-24.25~18.04.1-generic 4.1

[Touch-packages] [Bug 1834554] Re: Screen displays dynamic corruptions

2019-06-27 Thread Dan Kortschak

Screen shots of the corruption do not work as the screen shot tool
appears to overwrite the corruption. Video capture does work.

** Attachment added: "Video capture of screen corruption"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1834554/+attachment/5273854/+files/screen-speckles.ogv

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

Title:
  Screen displays dynamic corruptions

Status in xorg package in Ubuntu:
  New

Bug description:
  Regularly the screen displays corruptions that change depending on
  disk i/o, keyboard/mouse and other system activity. The screen
  corruptions do not appear on each session and can be removed by
  selecting an alternative resolution and then changing back (or
  reverting without accepting the change).

  The location of the corruptions is stereotypical and always has the
  same shape characteristics.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-24.25~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus..02.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:02:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.107  Thu May 24 21:54:01 
PDT 2018
   GCC version:  gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
  .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.9-0ubuntu7.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Fri Jun 28 12:14:17 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-340, 340.107, 4.18.0-15-generic, x86_64: installed
   nvidia-340, 340.107, 4.18.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation GT200b [GeForce GTX 275] [10de:05e6] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: CardExpert Technology GT200b [GeForce GTX 275] [10b0:0801]
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 
470/480/570/570X/580/580X] [1002:67df] (rev e7) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Ellesmere [Radeon RX 
470/480/570/580] [1458:22fc]
  InstallationDate: Installed on 2019-06-25 (2 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-24-generic 
root=UUID=b92b7098-365d-445a-b980-7fe3bc3b73da ro quiet splash vt.handoff=1
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/19/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0504
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P6T DELUXE V2
  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.:bvr0504:bd05/19/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6TDELUXEV2:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Touch-packages] [Bug 1830531] Re: .local domain look ups do not trigger name publication

2019-06-01 Thread Dan Kortschak

I don't claim that the packets are not being sent, but rather that the
system does not work as expected out of the box when it did in a
previous LTR. I don't really care what package is the cause except to
help get the problem fixed. I have done as much debugging of this as I
am capable since networking is not my area. If additional specific
question need addressing, I can follow up.

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

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

Title:
  .local domain look ups do not trigger name publication

Status in avahi package in Ubuntu:
  New

Bug description:
  On my local network I find that with 18.04 network name lookups using
  .local domains no not work unless stimulated by a non-18.04 machine
  first. This is observed for ssh, http, https and ping, but probably
  not limited to those.

  To demonstrate this here is a ping example.

  ~ $ ping pi.local
  ping: pi.local: Name or service not known
  ~ $ ping pi.local
  ping: pi.local: Name or service not known

  # At this point head to another machine running 16.04.6 and execute ping 
pi.local.
  # This is immediately successful. Then head back to the 18.04 machine.

  ~ $ ping pi.local
  PING pi.local (192.168.108.28) 56(84) bytes of data.
  64 bytes from pi.this.domain (192.168.108.28): icmp_seq=1 ttl=64 time=4.43 ms
  64 bytes from pi.this.domain (192.168.108.28): icmp_seq=2 ttl=64 time=5.64 ms
  64 bytes from pi.this.domain (192.168.108.28): icmp_seq=3 ttl=64 time=5.98 ms
  64 bytes from pi.this.domain (192.168.108.28): icmp_seq=4 ttl=64 time=5.84 ms
  ^C
  --- pi.local ping statistics ---
  4 packets transmitted, 4 received, 0% packet loss, time 7018ms
  rtt min/avg/max/mdev = 4.435/5.476/5.986/0.613 ms

  After a couple of minutes, the name resolution fails again, but can be
  brought back again by following the procedure above.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: avahi-daemon 0.7-3.1ubuntu1.2
  ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 26 20:04:58 2019
  InstallationDate: Installed on 2019-05-22 (4 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: avahi
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1830531] Re: .local domain look ups do not trigger name publication

2019-05-27 Thread Dan Kortschak

I have checked iptables and there are no rules.

# iptables -L
Chain INPUT (policy ACCEPT)
target prot opt source   destination 

Chain FORWARD (policy ACCEPT)
target prot opt source   destination 

Chain OUTPUT (policy ACCEPT)
target prot opt source   destination 


Looking at the the network traffic leaves me bewildered. There is too much 
variability to be able to make any sense of what is going on. Sometimes ping 
works and sometimes not. Restarting avahi-daemon does not appear to make any 
difference to this apart from the obvious flurry of packets when it does.

avahi-resolve-host-name does not behave significantly differently to
ping (it does sometimes work, but then so does ping).

I'm lost with trying to sort this out though.

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

Title:
  .local domain look ups do not trigger name publication

Status in avahi package in Ubuntu:
  Incomplete

Bug description:
  On my local network I find that with 18.04 network name lookups using
  .local domains no not work unless stimulated by a non-18.04 machine
  first. This is observed for ssh, http, https and ping, but probably
  not limited to those.

  To demonstrate this here is a ping example.

  ~ $ ping pi.local
  ping: pi.local: Name or service not known
  ~ $ ping pi.local
  ping: pi.local: Name or service not known

  # At this point head to another machine running 16.04.6 and execute ping 
pi.local.
  # This is immediately successful. Then head back to the 18.04 machine.

  ~ $ ping pi.local
  PING pi.local (192.168.108.28) 56(84) bytes of data.
  64 bytes from pi.this.domain (192.168.108.28): icmp_seq=1 ttl=64 time=4.43 ms
  64 bytes from pi.this.domain (192.168.108.28): icmp_seq=2 ttl=64 time=5.64 ms
  64 bytes from pi.this.domain (192.168.108.28): icmp_seq=3 ttl=64 time=5.98 ms
  64 bytes from pi.this.domain (192.168.108.28): icmp_seq=4 ttl=64 time=5.84 ms
  ^C
  --- pi.local ping statistics ---
  4 packets transmitted, 4 received, 0% packet loss, time 7018ms
  rtt min/avg/max/mdev = 4.435/5.476/5.986/0.613 ms

  After a couple of minutes, the name resolution fails again, but can be
  brought back again by following the procedure above.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: avahi-daemon 0.7-3.1ubuntu1.2
  ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 26 20:04:58 2019
  InstallationDate: Installed on 2019-05-22 (4 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: avahi
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1830531] Re: .local domain look ups do not trigger name publication

2019-05-26 Thread Dan Kortschak

Before I get a chance to look into this later today, I'd like to note
that the network device is not firewalling those packets since a few
days ago before I installed 18.04 on this machine it was behaving as
expected and the 16.04 machine mentioned in the OP is not being blocked
(it is on a slightly more restrictive policy than this one, but neither
block that port). As for the possibility of blocking outbound packets
from the machine itself, this seems most likely, however, as mentioned,
this is a new install and I have not added any firewalling policy that
would block them, suggesting that it's an out of the box setting.

I'll report back on these and the other tests when I am at that
location.

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

Title:
  .local domain look ups do not trigger name publication

Status in avahi package in Ubuntu:
  Incomplete

Bug description:
  On my local network I find that with 18.04 network name lookups using
  .local domains no not work unless stimulated by a non-18.04 machine
  first. This is observed for ssh, http, https and ping, but probably
  not limited to those.

  To demonstrate this here is a ping example.

  ~ $ ping pi.local
  ping: pi.local: Name or service not known
  ~ $ ping pi.local
  ping: pi.local: Name or service not known

  # At this point head to another machine running 16.04.6 and execute ping 
pi.local.
  # This is immediately successful. Then head back to the 18.04 machine.

  ~ $ ping pi.local
  PING pi.local (192.168.108.28) 56(84) bytes of data.
  64 bytes from pi.this.domain (192.168.108.28): icmp_seq=1 ttl=64 time=4.43 ms
  64 bytes from pi.this.domain (192.168.108.28): icmp_seq=2 ttl=64 time=5.64 ms
  64 bytes from pi.this.domain (192.168.108.28): icmp_seq=3 ttl=64 time=5.98 ms
  64 bytes from pi.this.domain (192.168.108.28): icmp_seq=4 ttl=64 time=5.84 ms
  ^C
  --- pi.local ping statistics ---
  4 packets transmitted, 4 received, 0% packet loss, time 7018ms
  rtt min/avg/max/mdev = 4.435/5.476/5.986/0.613 ms

  After a couple of minutes, the name resolution fails again, but can be
  brought back again by following the procedure above.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: avahi-daemon 0.7-3.1ubuntu1.2
  ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 26 20:04:58 2019
  InstallationDate: Installed on 2019-05-22 (4 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: avahi
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1830531] [NEW] .local domain look ups do not trigger name publication

2019-05-26 Thread Dan Kortschak

Public bug reported:

On my local network I find that with 18.04 network name lookups using
.local domains no not work unless stimulated by a non-18.04 machine
first. This is observed for ssh, http, https and ping, but probably not
limited to those.

To demonstrate this here is a ping example.

~ $ ping pi.local
ping: pi.local: Name or service not known
~ $ ping pi.local
ping: pi.local: Name or service not known

# At this point head to another machine running 16.04.6 and execute ping 
pi.local.
# This is immediately successful. Then head back to the 18.04 machine.

~ $ ping pi.local
PING pi.local (192.168.108.28) 56(84) bytes of data.
64 bytes from pi.this.domain (192.168.108.28): icmp_seq=1 ttl=64 time=4.43 ms
64 bytes from pi.this.domain (192.168.108.28): icmp_seq=2 ttl=64 time=5.64 ms
64 bytes from pi.this.domain (192.168.108.28): icmp_seq=3 ttl=64 time=5.98 ms
64 bytes from pi.this.domain (192.168.108.28): icmp_seq=4 ttl=64 time=5.84 ms
^C
--- pi.local ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 7018ms
rtt min/avg/max/mdev = 4.435/5.476/5.986/0.613 ms

After a couple of minutes, the name resolution fails again, but can be
brought back again by following the procedure above.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: avahi-daemon 0.7-3.1ubuntu1.2
ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-20-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun May 26 20:04:58 2019
InstallationDate: Installed on 2019-05-22 (4 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
SourcePackage: avahi
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  .local domain look ups do not trigger name publication

Status in avahi package in Ubuntu:
  New

Bug description:
  On my local network I find that with 18.04 network name lookups using
  .local domains no not work unless stimulated by a non-18.04 machine
  first. This is observed for ssh, http, https and ping, but probably
  not limited to those.

  To demonstrate this here is a ping example.

  ~ $ ping pi.local
  ping: pi.local: Name or service not known
  ~ $ ping pi.local
  ping: pi.local: Name or service not known

  # At this point head to another machine running 16.04.6 and execute ping 
pi.local.
  # This is immediately successful. Then head back to the 18.04 machine.

  ~ $ ping pi.local
  PING pi.local (192.168.108.28) 56(84) bytes of data.
  64 bytes from pi.this.domain (192.168.108.28): icmp_seq=1 ttl=64 time=4.43 ms
  64 bytes from pi.this.domain (192.168.108.28): icmp_seq=2 ttl=64 time=5.64 ms
  64 bytes from pi.this.domain (192.168.108.28): icmp_seq=3 ttl=64 time=5.98 ms
  64 bytes from pi.this.domain (192.168.108.28): icmp_seq=4 ttl=64 time=5.84 ms
  ^C
  --- pi.local ping statistics ---
  4 packets transmitted, 4 received, 0% packet loss, time 7018ms
  rtt min/avg/max/mdev = 4.435/5.476/5.986/0.613 ms

  After a couple of minutes, the name resolution fails again, but can be
  brought back again by following the procedure above.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: avahi-daemon 0.7-3.1ubuntu1.2
  ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 26 20:04:58 2019
  InstallationDate: Installed on 2019-05-22 (4 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: avahi
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1830531] Re: .local domain look ups do not trigger name publication

2019-05-26 Thread Dan Kortschak

~ $ lsb_release -rd
Description:Ubuntu 18.04.2 LTS
Release:18.04

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

Title:
  .local domain look ups do not trigger name publication

Status in avahi package in Ubuntu:
  New

Bug description:
  On my local network I find that with 18.04 network name lookups using
  .local domains no not work unless stimulated by a non-18.04 machine
  first. This is observed for ssh, http, https and ping, but probably
  not limited to those.

  To demonstrate this here is a ping example.

  ~ $ ping pi.local
  ping: pi.local: Name or service not known
  ~ $ ping pi.local
  ping: pi.local: Name or service not known

  # At this point head to another machine running 16.04.6 and execute ping 
pi.local.
  # This is immediately successful. Then head back to the 18.04 machine.

  ~ $ ping pi.local
  PING pi.local (192.168.108.28) 56(84) bytes of data.
  64 bytes from pi.this.domain (192.168.108.28): icmp_seq=1 ttl=64 time=4.43 ms
  64 bytes from pi.this.domain (192.168.108.28): icmp_seq=2 ttl=64 time=5.64 ms
  64 bytes from pi.this.domain (192.168.108.28): icmp_seq=3 ttl=64 time=5.98 ms
  64 bytes from pi.this.domain (192.168.108.28): icmp_seq=4 ttl=64 time=5.84 ms
  ^C
  --- pi.local ping statistics ---
  4 packets transmitted, 4 received, 0% packet loss, time 7018ms
  rtt min/avg/max/mdev = 4.435/5.476/5.986/0.613 ms

  After a couple of minutes, the name resolution fails again, but can be
  brought back again by following the procedure above.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: avahi-daemon 0.7-3.1ubuntu1.2
  ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-20-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun May 26 20:04:58 2019
  InstallationDate: Installed on 2019-05-22 (4 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: avahi
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1830029] Re: nouveau driver for nvidia is sluggish on GTX970M to the point of unusability

2019-05-22 Thread Dan Kortschak

Removing the nomodeset kernel parameter makes GDM snappier, but it then
hangs on login (relevant portion of syslog attached).

** Attachment added: "syslog"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1830029/+attachment/5265713/+files/syslog

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

Title:
  nouveau driver for nvidia is sluggish on GTX970M to the point of
  unusability

Status in xorg package in Ubuntu:
  New

Bug description:
  I am trying to use the nouveau drivers on a recent (today) install of
  18.04 on a 2.5yo laptop. Unfortunately the nvidia drivers don't work
  at all.

  What I am finding is that the sluggishness of the display is
  comparable to the case when nouveau drivers are disabled. The only
  real difference is in the amount of noise coming from the fan because
  of a slightly reduced CPU load due to Xorg.

  I don't even know where to start looking into this intelligently, but
  I would have expected that the drivers would have gotten to a usable
  state in the past 2 1/2 years since I last tried them on this machine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 22 21:05:40 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: CLEVO/KAPOK Computer HD Graphics 530 [1558:6540]
   NVIDIA Corporation GM204M [GeForce GTX 970M] [10de:13d8] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer GM204M [GeForce GTX 970M] [1558:6540]
  InstallationDate: Installed on 2019-05-22 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 5986:066d Acer, Inc 
   Bus 001 Device 003: ID 0cf3:e300 Atheros Communications, Inc. 
   Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook P65_P67RGRERA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic 
root=UUID=d6da27fa-5d91-4240-b3c9-c7de06124a36 ro nomodeset quiet nosplash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/27/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.13
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_P67RGRERA
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.13:bd01/27/2016:svnNotebook:pnP65_P67RGRERA:pvrNotApplicable:rvnNotebook:rnP65_P67RGRERA:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P65_P67RGRERA
  dmi.product.sku: Not Applicable
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

-- 
Mailing list: https://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 1830029] [NEW] nouveau driver for nvidia is sluggish on GTX970M to the point of unusability

2019-05-22 Thread Dan Kortschak

Public bug reported:

I am trying to use the nouveau drivers on a recent (today) install of
18.04 on a 2.5yo laptop. Unfortunately the nvidia drivers don't work at
all.

What I am finding is that the sluggishness of the display is comparable
to the case when nouveau drivers are disabled. The only real difference
is in the amount of noise coming from the fan because of a slightly
reduced CPU load due to Xorg.

I don't even know where to start looking into this intelligently, but I
would have expected that the drivers would have gotten to a usable state
in the past 2 1/2 years since I last tried them on this machine.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed May 22 21:05:40 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
   Subsystem: CLEVO/KAPOK Computer HD Graphics 530 [1558:6540]
 NVIDIA Corporation GM204M [GeForce GTX 970M] [10de:13d8] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: CLEVO/KAPOK Computer GM204M [GeForce GTX 970M] [1558:6540]
InstallationDate: Installed on 2019-05-22 (0 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 5986:066d Acer, Inc 
 Bus 001 Device 003: ID 0cf3:e300 Atheros Communications, Inc. 
 Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Notebook P65_P67RGRERA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-20-generic 
root=UUID=d6da27fa-5d91-4240-b3c9-c7de06124a36 ro nomodeset quiet nosplash
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/27/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.05.13
dmi.board.asset.tag: Tag 12345
dmi.board.name: P65_P67RGRERA
dmi.board.vendor: Notebook
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.13:bd01/27/2016:svnNotebook:pnP65_P67RGRERA:pvrNotApplicable:rvnNotebook:rnP65_P67RGRERA:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: P65_P67RGRERA
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: Notebook
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug bionic performance 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/1830029

Title:
  nouveau driver for nvidia is sluggish on GTX970M to the point of
  unusability

Status in xorg package in Ubuntu:
  New

Bug description:
  I am trying to use the nouveau drivers on a recent (today) install of
  18.04 on a 2.5yo laptop. Unfortunately the nvidia drivers don't work
  at all.

  What I am finding is that the sluggishness of the display is
  comparable to the case when nouveau drivers are disabled. The only
  real difference is in the amount of noise coming from the fan because
  of a slightly reduced CPU load due to Xorg.

  I don't even know where to start looking into this intelligently, but
  I would have expected that the drivers would have gotten to a usable
  state in the past 2 1/2 years since I last tried them on this machine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 22 21:05:40 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (pr

[Touch-packages] [Bug 1830000] [NEW] NVIDIA driver (390) does not allow progress to login screen

2019-05-22 Thread Dan Kortschak

Public bug reported:

Installing the nvidia-driver-390 package and disabling (or not) the
nouveau drivers results in a system that superficially appears to busy
hang before reaching the login screen, leaving only the fsck
"/dev/sda1: clean,..." message on the screen.

The machine is alive, and logging in remotely gives a hint at what is
happening. The output of top shows that init and systemd are struggling
with something:

```
top - 17:24:00 up 1 min,  1 user,  load average: 2.76, 1.00, 0.36
Tasks: 188 total,   2 running, 106 sleeping,   0 stopped,   0 zombie
%Cpu(s): 17.0 us, 15.2 sy,  0.0 ni, 67.6 id,  0.0 wa,  0.0 hi,  0.1 si,  0.0 st
KiB Mem : 16238012 total, 15513832 free,   242248 used,   481932 buff/cache
KiB Swap: 16001020 total, 16001020 free,0 used. 15716900 avail Mem 

  PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND 
   
1 root  20   0  225600   9312   6672 S  60.4  0.1   0:51.63 /sbin/init 
nosplash
  797 root  20   0   71656   7180   5296 S  26.8  0.0   0:14.92 
/lib/systemd/systemd-logind
 1133 root  20   0   46368   3584   1976 R  13.9  0.0   0:12.01 
/lib/systemd/systemd-udevd 
  795 root  20   0 1773200  30772  12548 S  13.2  0.2   0:11.71 
/usr/lib/snapd/snapd   
  784 message+  20   0   51464   6036   3988 S  12.9  0.0   0:11.15 
/usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --s+ 
  308 root  19  -1  249904 120460 114260 S  10.7  0.7   0:10.60 
/lib/systemd/systemd-journald  
 1132 root  20   0   46368   3584   1976 S  10.0  0.0   0:08.71 
/lib/systemd/systemd-udevd 
 1134 root  20   0   46368   3260   1656 S  10.0  0.0   0:08.61 
/lib/systemd/systemd-udevd 
  333 root  20   0   46368   4684   3084 S   5.0  0.0   0:04.25 
/lib/systemd/systemd-udevd   
```

Eventually, Xorg does manage to get a word in, but falls over, to try
again repeatedly.

```
top - 16:52:36 up 2 min,  1 user,  load average: 1.69, 1.04, 0.43
Tasks: 187 total,   2 running, 106 sleeping,   0 stopped,   0 zombie
%Cpu(s):  9.5 us,  3.7 sy,  0.0 ni, 85.6 id,  0.0 wa,  0.0 hi,  1.2 si,  0.0 st
KiB Mem : 16238012 total, 15457080 free,   278152 used,   502780 buff/cache
KiB Swap: 16001020 total, 16001020 free,0 used. 15680684 avail Mem 

  PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND 
   
 1821 root  20   0  312908  61228  20584 R  65.2  0.4   0:01.97 
/usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/121/gdm/Xauthority -b+ 
  806 root  20   0   71656   7200   5320 S  18.5  0.0   0:24.83 
/lib/systemd/systemd-logind
```

A further hint comes from syslog which is spammed with systemd trying to
start nvidia-persistenced, which is then killed. This happens hundreds
of times while the machine is up. This except shows one instance.

```
May 22 16:34:52 cube systemd[1]: Starting NVIDIA Persistence Daemon...
May 22 16:34:52 cube nvidia-persistenced: Verbose syslog connection opened
May 22 16:34:52 cube nvidia-persistenced: Now running with user ID 123 and 
group ID 127
May 22 16:34:52 cube systemd[1]: Started NVIDIA Persistence Daemon.
May 22 16:34:52 cube nvidia-persistenced: Started (31927)
May 22 16:34:52 cube nvidia-persistenced: device :01:00.0 - registered
May 22 16:34:52 cube nvidia-persistenced: Local RPC service initialized
May 22 16:34:52 cube nvidia-persistenced: Received signal 15
May 22 16:34:52 cube systemd[1]: Stopping NVIDIA Persistence Daemon...
May 22 16:34:52 cube nvidia-persistenced: Socket closed.
May 22 16:34:52 cube nvidia-persistenced: PID file unlocked.
May 22 16:34:52 cube nvidia-persistenced: PID file closed.
May 22 16:34:52 cube nvidia-persistenced: The daemon no longer has permission 
to remove its runtime data directory /var/run/nvidia-persistenced
May 22 16:34:52 cube nvidia-persistenced: Shutdown (31927)
May 22 16:34:52 cube systemd[1]: Stopped NVIDIA Persistence Daemon.
```

This is a fresh install of 18.04.2 (less than an hour old). If apport
has not collected all the necessary details I'll post them after this.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-20-generic 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 UNI

[Touch-packages] [Bug 1624299] [NEW] SFTP protocol source cannot be found

2016-09-16 Thread Dan Kortschak

Public bug reported:

Trying to play a video over SFTP fails, with Totem giving a pop-up:

"""
Required plugin could not be found

Videos requires to install plugins to support the following multimedia feature: 
SFTP protocol source
"""

There does not seem to be any package that fits this description in the
apt repos. Trying from the command line with a local terminal I get the
following:

"""
/run/user/1000/gvfs/sftp:host=nas.local/Videos $ totem GOPR0210.MP4 
** Message: Missing plugin: gstreamer|1.0|totem|SFTP protocol 
source|urisource-sftp (SFTP protocol source)
/usr/lib/python3/dist-packages/sessioninstaller/core.py:47: PyGIWarning: Gst 
was imported without specifying a version first. Use gi.require_version('Gst', 
'1.0') before import to ensure that the right version gets loaded.
  from gi.repository import Gst
/usr/lib/python3/dist-packages/sessioninstaller/core.py:48: PyGIWarning: Gtk 
was imported without specifying a version first. Use gi.require_version('Gtk', 
'3.0') before import to ensure that the right version gets loaded.
  from gi.repository import Gtk
Falling back to package information
CRITICAL:Could not find any packages to operate on
"""

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: libgstreamer1.0-0 1.8.2-1~ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Sep 16 19:28:29 2016
InstallationDate: Installed on 2016-06-07 (100 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: gstreamer1.0
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  SFTP protocol source cannot be found

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  Trying to play a video over SFTP fails, with Totem giving a pop-up:

  """
  Required plugin could not be found

  Videos requires to install plugins to support the following multimedia 
feature: SFTP protocol source
  """

  There does not seem to be any package that fits this description in
  the apt repos. Trying from the command line with a local terminal I
  get the following:

  """
  /run/user/1000/gvfs/sftp:host=nas.local/Videos $ totem GOPR0210.MP4 
  ** Message: Missing plugin: gstreamer|1.0|totem|SFTP protocol 
source|urisource-sftp (SFTP protocol source)
  /usr/lib/python3/dist-packages/sessioninstaller/core.py:47: PyGIWarning: Gst 
was imported without specifying a version first. Use gi.require_version('Gst', 
'1.0') before import to ensure that the right version gets loaded.
from gi.repository import Gst
  /usr/lib/python3/dist-packages/sessioninstaller/core.py:48: PyGIWarning: Gtk 
was imported without specifying a version first. Use gi.require_version('Gtk', 
'3.0') before import to ensure that the right version gets loaded.
from gi.repository import Gtk
  Falling back to package information
  CRITICAL:Could not find any packages to operate on
  """

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libgstreamer1.0-0 1.8.2-1~ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Sep 16 19:28:29 2016
  InstallationDate: Installed on 2016-06-07 (100 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1624299/+subscriptions

-- 
Mailing list: https://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 1591472] Re: Xorg crashes immediately on login returning to greeter

2016-09-07 Thread Dan Kortschak

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

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

Title:
  Xorg crashes immediately on login returning to greeter

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  ~ $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  ~ $ apt-cache policy nvidia-361 xorg
  nvidia-361:
Installed: 361.42-0ubuntu2
Candidate: 361.42-0ubuntu2
Version table:
   *** 361.42-0ubuntu2 500
  500 http://mirror.internode.on.net/pub/ubuntu/ubuntu 
xenial/restricted amd64 Packages
  100 /var/lib/dpkg/status
  xorg:
Installed: 1:7.7+13ubuntu3
Candidate: 1:7.7+13ubuntu3
Version table:
   *** 1:7.7+13ubuntu3 500
  500 http://mirror.internode.on.net/pub/ubuntu/ubuntu xenial/main 
amd64 Packages
  100 /var/lib/dpkg/status

  
  Boot machine and login with correct credentials.

  Expect a functioning X session with gnome.

  Instead immediately returned to greeter.

  Attempted to do backtracing, but this did not work because
  (presumably) of absence of ../sysdeps/unix/syscall-template.S and an
  error returned after staring gdb, `"/usr/bin/Xorg": not in executable
  format: File format not recognised'. Went ahead any way and gdb sees:

  ```
  
  Reading symbols from /usr/lib/xorg/modules/input/evdev_drv.so...(no debugging 
symbols found)...done.
  Reading symbols from /usr/lib/x86_64-linux-gnu/libmtdev.so.1...(no debugging 
symbols found)...done.
  Reading symbols from /usr/lib/x86_64-linux-gnu/libevdev.so.2...(no debugging 
symbols found)...done.
  Reading symbols from /usr/lib/xorg/modules/input/synaptics_drv.so...(no 
debugging symbols found)...done.
  0x7fe59028acf3 in __select_nocancel ()
  at ../sysdeps/unix/syscall-template.S:84
  84  ../sysdeps/unix/syscall-template.S: No such file or directory.
  (gdb) cont
  Continuing.
  warning: Corrupted shared library list: 0x556edfb384d0 != 0x556edfba4c60
  warning: Corrupted shared library list: 0x556edfbc48c0 != 0x556edfb384d0

  Program received signal SIGTERM, Terminated.
  0x7fe59028acf3 in __select_nocancel ()
  at ../sysdeps/unix/syscall-template.S:84
  84  in ../sysdeps/unix/syscall-template.S
  (gdb) cont
  Continuing.

  Program terminated with signal SIGKILL, Killed.
  The program no longer exists.
  ```

  If given instructions on how to get backtracking to work, will happily
  reattempt.

  Using nvidia-304 (current) is worse, crashing in the greeter. Nouveau
  is unusable due to lag and sluggishness.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  NonfreeKernelModules: nvidia_uvm 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  361.42  Tue Mar 22 18:10:58 
PDT 2016
   GCC version:  gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2.1)
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Sat Jun 11 17:46:17 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 
00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer Skylake Integrated Graphics [1558:6540]
   NVIDIA Corporation GM204M [GeForce GTX 970M] [10de:13d8] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer GM204M [GeForce GTX 970M] [1558:6540]
  InstallationDate: Installed on 2016-06-07 (3 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 5986:066d Acer, Inc 
   Bus 001 Device 003: ID 0cf3:e300 Atheros Communications, Inc. 
   Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook P65_P67RGRERA
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic 
root=UUID=153d01ca-6817-4bd1-9ace-8a3a44586e7a ro nomodeset quiet splash
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/27/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.13
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_P67RGRERA
  dmi.board

[Touch-packages] [Bug 1591472] Re: Xorg crashes immediately on login returning to greeter

2016-09-06 Thread Dan Kortschak

When I started looking at this problem, the machine would not boot
without nomodeset. This is no longer the case - and removing that fixes
the problem.

Thank you for looking at this, Timo. Please mark as invalid.

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

Title:
  Xorg crashes immediately on login returning to greeter

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  ~ $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  ~ $ apt-cache policy nvidia-361 xorg
  nvidia-361:
Installed: 361.42-0ubuntu2
Candidate: 361.42-0ubuntu2
Version table:
   *** 361.42-0ubuntu2 500
  500 http://mirror.internode.on.net/pub/ubuntu/ubuntu 
xenial/restricted amd64 Packages
  100 /var/lib/dpkg/status
  xorg:
Installed: 1:7.7+13ubuntu3
Candidate: 1:7.7+13ubuntu3
Version table:
   *** 1:7.7+13ubuntu3 500
  500 http://mirror.internode.on.net/pub/ubuntu/ubuntu xenial/main 
amd64 Packages
  100 /var/lib/dpkg/status

  
  Boot machine and login with correct credentials.

  Expect a functioning X session with gnome.

  Instead immediately returned to greeter.

  Attempted to do backtracing, but this did not work because
  (presumably) of absence of ../sysdeps/unix/syscall-template.S and an
  error returned after staring gdb, `"/usr/bin/Xorg": not in executable
  format: File format not recognised'. Went ahead any way and gdb sees:

  ```
  
  Reading symbols from /usr/lib/xorg/modules/input/evdev_drv.so...(no debugging 
symbols found)...done.
  Reading symbols from /usr/lib/x86_64-linux-gnu/libmtdev.so.1...(no debugging 
symbols found)...done.
  Reading symbols from /usr/lib/x86_64-linux-gnu/libevdev.so.2...(no debugging 
symbols found)...done.
  Reading symbols from /usr/lib/xorg/modules/input/synaptics_drv.so...(no 
debugging symbols found)...done.
  0x7fe59028acf3 in __select_nocancel ()
  at ../sysdeps/unix/syscall-template.S:84
  84  ../sysdeps/unix/syscall-template.S: No such file or directory.
  (gdb) cont
  Continuing.
  warning: Corrupted shared library list: 0x556edfb384d0 != 0x556edfba4c60
  warning: Corrupted shared library list: 0x556edfbc48c0 != 0x556edfb384d0

  Program received signal SIGTERM, Terminated.
  0x7fe59028acf3 in __select_nocancel ()
  at ../sysdeps/unix/syscall-template.S:84
  84  in ../sysdeps/unix/syscall-template.S
  (gdb) cont
  Continuing.

  Program terminated with signal SIGKILL, Killed.
  The program no longer exists.
  ```

  If given instructions on how to get backtracking to work, will happily
  reattempt.

  Using nvidia-304 (current) is worse, crashing in the greeter. Nouveau
  is unusable due to lag and sluggishness.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  NonfreeKernelModules: nvidia_uvm 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  361.42  Tue Mar 22 18:10:58 
PDT 2016
   GCC version:  gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2.1)
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Sat Jun 11 17:46:17 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 
00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer Skylake Integrated Graphics [1558:6540]
   NVIDIA Corporation GM204M [GeForce GTX 970M] [10de:13d8] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer GM204M [GeForce GTX 970M] [1558:6540]
  InstallationDate: Installed on 2016-06-07 (3 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 5986:066d Acer, Inc 
   Bus 001 Device 003: ID 0cf3:e300 Atheros Communications, Inc. 
   Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook P65_P67RGRERA
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic 
root=UUID=153d01ca-6817-4bd1-9ace-8a3a44586e7a ro nomodeset quiet splash
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/27/20

[Touch-packages] [Bug 1610519] [NEW] apport-gtk crashes with segmentation fault

2016-08-06 Thread Dan Kortschak

Public bug reported:

apport-bug calling apport-gtk crashes with a segmentation fault.

~ $ lsb_release -rd
Description: Ubuntu 16.04.1 LTS
Release: 16.04
~ $ dpkg -l apport-gtk
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameVersion  Architecture 
Description
+++-===---
ii  apport-gtk  2.20.1-0ubuntu2.1all  
GTK+ frontend for the apport crash report system


This look related to #1610518.


The backtrace from the core:

~ $ apport-bug 
Segmentation fault (core dumped)
~ $ gdb64 /usr/bin/python3 core 
GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.04) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/python3...(no debugging symbols found)...done.

warning: core file may not match specified executable file.
[New LWP 4932]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

warning: the debug information found in "/lib64/ld-2.23.so" does not
match "/lib64/ld-linux-x86-64.so.2" (CRC mismatch).

Core was generated by `/usr/bin/python3 /usr/share/apport/apport-gtk'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  rawmemchr () at ../sysdeps/x86_64/rawmemchr.S:37

warning: Source file is more recent than executable.
37  movdqu  (%rdi), %xmm0
(gdb) backtrace full
#0  rawmemchr () at ../sysdeps/x86_64/rawmemchr.S:37
No locals.
#1  0x7f89cc55bf22 in _IO_str_init_static_internal 
(sf=sf@entry=0x7ffc1fa72690, ptr=ptr@entry=0x0, size=size@entry=0, 
pstart=pstart@entry=0x0)
at strops.c:41
fp = 0x7ffc1fa72690
end = 
#2  0x7f89cc54ab67 in __GI___isoc99_vsscanf (string=0x0, 
format=0x7f89c5e972f2 "%d.%d", args=args@entry=0x7ffc1fa727b8) at 
isoc99_vsscanf.c:41
ret = -863365216
sf = {_sbf = {_f = {_flags = -72515584, _IO_read_ptr = 0x0, 
_IO_read_end = 0x0, _IO_read_base = 0x0, _IO_write_base = 0x0, 
  _IO_write_ptr = 0x0, _IO_write_end = 0x0, _IO_buf_base = 0x0, 
_IO_buf_end = 0x0, _IO_save_base = 0x0, _IO_backup_base = 0x0, 
  _IO_save_end = 0x0, _markers = 0x0, _chain = 0x0, _fileno = 0, 
_flags2 = 0, _old_offset = 71776119061217280, _cur_column = 0, 
  _vtable_offset = 0 '\000', _shortbuf = "", _lock = 0x0, _offset = 
0, _codecvt = 0x0, _wide_data = 0x, 
  _freeres_list = 0x0, _freeres_buf = 0xff00ff00, __pad5 = 
18446462598732840960, _mode = -1, 
  _unused2 = '\000' }, vtable = 0x7f89cc8a17a0 
<_IO_str_jumps>}, _s = {_allocate_buffer = 0x0, _free_buffer = 0x0}}
#3  0x7f89cc54ab07 in __isoc99_sscanf (s=, format=) at isoc99_sscanf.c:31
arg = 
done = -863365216
#4  0x7f89c5e79d22 in epoxy_glx_version () from 
/usr/lib/x86_64-linux-gnu/libepoxy.so.0
No symbol table info available.
#5  0x7f89c8b18509 in gdk_x11_screen_init_gl (screen=screen@entry=0xdf6160)
at /build/gtk+3.0-6ZPWga/gtk+3.0-3.18.9/./gdk/x11/gdkglcontext-x11.c:774
display = 0xdf1020
display_x11 = 0xdf1020
dpy = 0xde3800
error_base = 172
event_base = 104
screen_num = 0
#6  0x7f89c8b1882a in _gdk_x11_screen_update_visuals_for_gl 
(screen=screen@entry=0xdf6160)
at /build/gtk+3.0-6ZPWga/gtk+3.0-3.18.9/./gdk/x11/gdkglcontext-x11.c:1114
x11_screen = 0xdf6160
display = 0xdf1020
display_x11 = 0xdf1020
dpy = 0xde3800
gl_info = 
i = 
system_visual_id = 
rgba_visual_id = 
#7  0x7f89c8b20f4e in _gdk_x11_screen_init_visuals 
(screen=screen@entry=0xdf6160)
at /build/gtk+3.0-6ZPWga/gtk+3.0-3.18.9/./gdk/x11/gdkvisual-x11.c:334
possible_depths = {32, 30, 24, 16, 15, 8, 4, 1}
---Type  to continue, or q  to quit---
possible_types = {GDK_VISUAL_DIRECT_COLOR, GDK_VISUAL_TRUE_COLOR, 
GDK_VISUAL_PSEUDO_COLOR, GDK_VISUAL_STATIC_COLOR, GDK_VISUAL_GRAYSCALE, 
  GDK_VISUAL_STATIC_GRAY}
x11_screen = 0xdf6160
visual_list = 
visual_template = {visual = 0x

[Touch-packages] [Bug 1591472] Re: Xorg crashes immediately on login returning to greeter

2016-08-06 Thread Dan Kortschak

OK, `gdb64 /usr/lib/xorg/Xorg 2>&1 | tee gdb-Xorg.txt' works. The
instructions for backtracing at
https://wiki.ubuntu.com/X/Backtracing#Backtrace_with_gdb obviously need
some love.

With all the complaints from gdb out of the way it seems that the issue
shows up as the corrupted shared library list seen above.


** Attachment added: "Two attempts at backtrace"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1591472/+attachment/4715387/+files/gdb-Xorg.txt

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

Title:
  Xorg crashes immediately on login returning to greeter

Status in xorg package in Ubuntu:
  New

Bug description:
  ~ $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  ~ $ apt-cache policy nvidia-361 xorg
  nvidia-361:
Installed: 361.42-0ubuntu2
Candidate: 361.42-0ubuntu2
Version table:
   *** 361.42-0ubuntu2 500
  500 http://mirror.internode.on.net/pub/ubuntu/ubuntu 
xenial/restricted amd64 Packages
  100 /var/lib/dpkg/status
  xorg:
Installed: 1:7.7+13ubuntu3
Candidate: 1:7.7+13ubuntu3
Version table:
   *** 1:7.7+13ubuntu3 500
  500 http://mirror.internode.on.net/pub/ubuntu/ubuntu xenial/main 
amd64 Packages
  100 /var/lib/dpkg/status

  
  Boot machine and login with correct credentials.

  Expect a functioning X session with gnome.

  Instead immediately returned to greeter.

  Attempted to do backtracing, but this did not work because
  (presumably) of absence of ../sysdeps/unix/syscall-template.S and an
  error returned after staring gdb, `"/usr/bin/Xorg": not in executable
  format: File format not recognised'. Went ahead any way and gdb sees:

  ```
  
  Reading symbols from /usr/lib/xorg/modules/input/evdev_drv.so...(no debugging 
symbols found)...done.
  Reading symbols from /usr/lib/x86_64-linux-gnu/libmtdev.so.1...(no debugging 
symbols found)...done.
  Reading symbols from /usr/lib/x86_64-linux-gnu/libevdev.so.2...(no debugging 
symbols found)...done.
  Reading symbols from /usr/lib/xorg/modules/input/synaptics_drv.so...(no 
debugging symbols found)...done.
  0x7fe59028acf3 in __select_nocancel ()
  at ../sysdeps/unix/syscall-template.S:84
  84  ../sysdeps/unix/syscall-template.S: No such file or directory.
  (gdb) cont
  Continuing.
  warning: Corrupted shared library list: 0x556edfb384d0 != 0x556edfba4c60
  warning: Corrupted shared library list: 0x556edfbc48c0 != 0x556edfb384d0

  Program received signal SIGTERM, Terminated.
  0x7fe59028acf3 in __select_nocancel ()
  at ../sysdeps/unix/syscall-template.S:84
  84  in ../sysdeps/unix/syscall-template.S
  (gdb) cont
  Continuing.

  Program terminated with signal SIGKILL, Killed.
  The program no longer exists.
  ```

  If given instructions on how to get backtracking to work, will happily
  reattempt.

  Using nvidia-304 (current) is worse, crashing in the greeter. Nouveau
  is unusable due to lag and sluggishness.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  NonfreeKernelModules: nvidia_uvm 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  361.42  Tue Mar 22 18:10:58 
PDT 2016
   GCC version:  gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2.1)
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Sat Jun 11 17:46:17 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 
00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer Skylake Integrated Graphics [1558:6540]
   NVIDIA Corporation GM204M [GeForce GTX 970M] [10de:13d8] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer GM204M [GeForce GTX 970M] [1558:6540]
  InstallationDate: Installed on 2016-06-07 (3 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 5986:066d Acer, Inc 
   Bus 001 Device 003: ID 0cf3:e300 Atheros Communications, Inc. 
   Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook P65_P67RGRERA
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmli

[Touch-packages] [Bug 1591472] Re: Xorg crashes immediately on login returning to greeter

2016-08-06 Thread Dan Kortschak

I have sorted out the syscall-template.S issue by getting the libc6
source.

I have found places saying that the cause of gdb not liking the binary
is because of arch incompatibility (32 v 64). I tried this with no
change.

~# gdb /usr/bin/Xorg 2>&1 | tee gdb-Xorg.txt
GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.04) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "i686-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
"/usr/bin/Xorg": not in executable format: File format not recognised
(gdb) attach 2920
Attaching to process 2920
"/usr/lib/xorg/Xorg": not in executable format: File format not recognised
(gdb) cont
Continuing.

Program received signal SIGPIPE, Broken pipe.
0xbdc85720 in ?? ()
(gdb) cont
Continuing.

Program received signal SIGTERM, Terminated.
0xbdc85cf3 in ?? ()
(gdb) cont
Continuing.

Program terminated with signal SIGKILL, Killed.
The program no longer exists.
(gdb) cont
The program is not being run.
(gdb) backtrace full
No stack.


Here we still have no capacity to get a backtrace. Once again, some indication 
of how to proceed to get more useful information would be greatly appreciated.

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

Title:
  Xorg crashes immediately on login returning to greeter

Status in xorg package in Ubuntu:
  New

Bug description:
  ~ $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  ~ $ apt-cache policy nvidia-361 xorg
  nvidia-361:
Installed: 361.42-0ubuntu2
Candidate: 361.42-0ubuntu2
Version table:
   *** 361.42-0ubuntu2 500
  500 http://mirror.internode.on.net/pub/ubuntu/ubuntu 
xenial/restricted amd64 Packages
  100 /var/lib/dpkg/status
  xorg:
Installed: 1:7.7+13ubuntu3
Candidate: 1:7.7+13ubuntu3
Version table:
   *** 1:7.7+13ubuntu3 500
  500 http://mirror.internode.on.net/pub/ubuntu/ubuntu xenial/main 
amd64 Packages
  100 /var/lib/dpkg/status

  
  Boot machine and login with correct credentials.

  Expect a functioning X session with gnome.

  Instead immediately returned to greeter.

  Attempted to do backtracing, but this did not work because
  (presumably) of absence of ../sysdeps/unix/syscall-template.S and an
  error returned after staring gdb, `"/usr/bin/Xorg": not in executable
  format: File format not recognised'. Went ahead any way and gdb sees:

  ```
  
  Reading symbols from /usr/lib/xorg/modules/input/evdev_drv.so...(no debugging 
symbols found)...done.
  Reading symbols from /usr/lib/x86_64-linux-gnu/libmtdev.so.1...(no debugging 
symbols found)...done.
  Reading symbols from /usr/lib/x86_64-linux-gnu/libevdev.so.2...(no debugging 
symbols found)...done.
  Reading symbols from /usr/lib/xorg/modules/input/synaptics_drv.so...(no 
debugging symbols found)...done.
  0x7fe59028acf3 in __select_nocancel ()
  at ../sysdeps/unix/syscall-template.S:84
  84  ../sysdeps/unix/syscall-template.S: No such file or directory.
  (gdb) cont
  Continuing.
  warning: Corrupted shared library list: 0x556edfb384d0 != 0x556edfba4c60
  warning: Corrupted shared library list: 0x556edfbc48c0 != 0x556edfb384d0

  Program received signal SIGTERM, Terminated.
  0x7fe59028acf3 in __select_nocancel ()
  at ../sysdeps/unix/syscall-template.S:84
  84  in ../sysdeps/unix/syscall-template.S
  (gdb) cont
  Continuing.

  Program terminated with signal SIGKILL, Killed.
  The program no longer exists.
  ```

  If given instructions on how to get backtracking to work, will happily
  reattempt.

  Using nvidia-304 (current) is worse, crashing in the greeter. Nouveau
  is unusable due to lag and sluggishness.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  NonfreeKernelModules: nvidia_uvm 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  361.42  Tue Mar 22 18:10:58 
PDT 2016
   GCC version:  gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2.1)
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/a

[Touch-packages] [Bug 1591472] Re: Xorg crashes immediately on login returning to greeter

2016-06-25 Thread Dan Kortschak

Yoo hoo! Is anyone home?

Some triage love would be greatly appreciated here.

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

Title:
  Xorg crashes immediately on login returning to greeter

Status in xorg package in Ubuntu:
  New

Bug description:
  ~ $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04
  ~ $ apt-cache policy nvidia-361 xorg
  nvidia-361:
Installed: 361.42-0ubuntu2
Candidate: 361.42-0ubuntu2
Version table:
   *** 361.42-0ubuntu2 500
  500 http://mirror.internode.on.net/pub/ubuntu/ubuntu 
xenial/restricted amd64 Packages
  100 /var/lib/dpkg/status
  xorg:
Installed: 1:7.7+13ubuntu3
Candidate: 1:7.7+13ubuntu3
Version table:
   *** 1:7.7+13ubuntu3 500
  500 http://mirror.internode.on.net/pub/ubuntu/ubuntu xenial/main 
amd64 Packages
  100 /var/lib/dpkg/status

  
  Boot machine and login with correct credentials.

  Expect a functioning X session with gnome.

  Instead immediately returned to greeter.

  Attempted to do backtracing, but this did not work because
  (presumably) of absence of ../sysdeps/unix/syscall-template.S and an
  error returned after staring gdb, `"/usr/bin/Xorg": not in executable
  format: File format not recognised'. Went ahead any way and gdb sees:

  ```
  
  Reading symbols from /usr/lib/xorg/modules/input/evdev_drv.so...(no debugging 
symbols found)...done.
  Reading symbols from /usr/lib/x86_64-linux-gnu/libmtdev.so.1...(no debugging 
symbols found)...done.
  Reading symbols from /usr/lib/x86_64-linux-gnu/libevdev.so.2...(no debugging 
symbols found)...done.
  Reading symbols from /usr/lib/xorg/modules/input/synaptics_drv.so...(no 
debugging symbols found)...done.
  0x7fe59028acf3 in __select_nocancel ()
  at ../sysdeps/unix/syscall-template.S:84
  84  ../sysdeps/unix/syscall-template.S: No such file or directory.
  (gdb) cont
  Continuing.
  warning: Corrupted shared library list: 0x556edfb384d0 != 0x556edfba4c60
  warning: Corrupted shared library list: 0x556edfbc48c0 != 0x556edfb384d0

  Program received signal SIGTERM, Terminated.
  0x7fe59028acf3 in __select_nocancel ()
  at ../sysdeps/unix/syscall-template.S:84
  84  in ../sysdeps/unix/syscall-template.S
  (gdb) cont
  Continuing.

  Program terminated with signal SIGKILL, Killed.
  The program no longer exists.
  ```

  If given instructions on how to get backtracking to work, will happily
  reattempt.

  Using nvidia-304 (current) is worse, crashing in the greeter. Nouveau
  is unusable due to lag and sluggishness.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  NonfreeKernelModules: nvidia_uvm 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  361.42  Tue Mar 22 18:10:58 
PDT 2016
   GCC version:  gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2.1)
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  Date: Sat Jun 11 17:46:17 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 
00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer Skylake Integrated Graphics [1558:6540]
   NVIDIA Corporation GM204M [GeForce GTX 970M] [10de:13d8] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer GM204M [GeForce GTX 970M] [1558:6540]
  InstallationDate: Installed on 2016-06-07 (3 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 5986:066d Acer, Inc 
   Bus 001 Device 003: ID 0cf3:e300 Atheros Communications, Inc. 
   Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Notebook P65_P67RGRERA
  ProcEnviron:
   LANGUAGE=en_AU:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic 
root=UUID=153d01ca-6817-4bd1-9ace-8a3a44586e7a ro nomodeset quiet splash
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/27/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.13
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P65_P67RGRERA
  d

[Touch-packages] [Bug 1591472] [NEW] Xorg crashes immediately on login returning to greeter

2016-06-11 Thread Dan Kortschak

Public bug reported:

~ $ lsb_release -rd
Description:Ubuntu 16.04 LTS
Release:16.04
~ $ apt-cache policy nvidia-361 xorg
nvidia-361:
  Installed: 361.42-0ubuntu2
  Candidate: 361.42-0ubuntu2
  Version table:
 *** 361.42-0ubuntu2 500
500 http://mirror.internode.on.net/pub/ubuntu/ubuntu xenial/restricted 
amd64 Packages
100 /var/lib/dpkg/status
xorg:
  Installed: 1:7.7+13ubuntu3
  Candidate: 1:7.7+13ubuntu3
  Version table:
 *** 1:7.7+13ubuntu3 500
500 http://mirror.internode.on.net/pub/ubuntu/ubuntu xenial/main amd64 
Packages
100 /var/lib/dpkg/status


Boot machine and login with correct credentials.

Expect a functioning X session with gnome.

Instead immediately returned to greeter.

Attempted to do backtracing, but this did not work because (presumably)
of absence of ../sysdeps/unix/syscall-template.S and an error returned
after staring gdb, `"/usr/bin/Xorg": not in executable format: File
format not recognised'. Went ahead any way and gdb sees:

```

Reading symbols from /usr/lib/xorg/modules/input/evdev_drv.so...(no debugging 
symbols found)...done.
Reading symbols from /usr/lib/x86_64-linux-gnu/libmtdev.so.1...(no debugging 
symbols found)...done.
Reading symbols from /usr/lib/x86_64-linux-gnu/libevdev.so.2...(no debugging 
symbols found)...done.
Reading symbols from /usr/lib/xorg/modules/input/synaptics_drv.so...(no 
debugging symbols found)...done.
0x7fe59028acf3 in __select_nocancel ()
at ../sysdeps/unix/syscall-template.S:84
84  ../sysdeps/unix/syscall-template.S: No such file or directory.
(gdb) cont
Continuing.
warning: Corrupted shared library list: 0x556edfb384d0 != 0x556edfba4c60
warning: Corrupted shared library list: 0x556edfbc48c0 != 0x556edfb384d0

Program received signal SIGTERM, Terminated.
0x7fe59028acf3 in __select_nocancel ()
at ../sysdeps/unix/syscall-template.S:84
84  in ../sysdeps/unix/syscall-template.S
(gdb) cont
Continuing.

Program terminated with signal SIGKILL, Killed.
The program no longer exists.
```

If given instructions on how to get backtracking to work, will happily
reattempt.

Using nvidia-304 (current) is worse, crashing in the greeter. Nouveau is
unusable due to lag and sluggishness.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
Uname: Linux 4.4.0-24-generic x86_64
NonfreeKernelModules: nvidia_uvm 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  361.42  Tue Mar 22 18:10:58 
PDT 2016
 GCC version:  gcc version 5.3.1 20160413 (Ubuntu 5.3.1-14ubuntu2.1)
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
Date: Sat Jun 11 17:46:17 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Skylake Integrated Graphics [8086:191b] (rev 06) (prog-if 00 
[VGA controller])
   Subsystem: CLEVO/KAPOK Computer Skylake Integrated Graphics [1558:6540]
 NVIDIA Corporation GM204M [GeForce GTX 970M] [10de:13d8] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: CLEVO/KAPOK Computer GM204M [GeForce GTX 970M] [1558:6540]
InstallationDate: Installed on 2016-06-07 (3 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 5986:066d Acer, Inc 
 Bus 001 Device 003: ID 0cf3:e300 Atheros Communications, Inc. 
 Bus 001 Device 002: ID 1c7a:0603 LighTuning Technology Inc. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Notebook P65_P67RGRERA
ProcEnviron:
 LANGUAGE=en_AU:en
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-24-generic 
root=UUID=153d01ca-6817-4bd1-9ace-8a3a44586e7a ro nomodeset quiet splash
SourcePackage: xorg
Symptom: display
Title: Xorg crash
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/27/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.05.13
dmi.board.asset.tag: Tag 12345
dmi.board.name: P65_P67RGRERA
dmi.board.vendor: Notebook
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.13:bd01/27/2016:svnNotebook:pnP65_P67RGRERA:pvrNotApplicable:rvnNotebook:rnP65_P67RGRERA:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
dmi.product.name: P65_P67RGRERA
dmi.product.version: Not Applicable
dmi.sys.vendor: Notebook
version.compiz: compiz 1:0.9.12.2+16.04.20160526-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: li

[Touch-packages] [Bug 1722478] Re: Two-finger scrolling and click-and-drag no longer works after resuming from suspend

[Touch-packages] [Bug 1834554] [NEW] Screen displays dynamic corruptions

[Touch-packages] [Bug 1834554] Re: Screen displays dynamic corruptions

[Touch-packages] [Bug 1830531] Re: .local domain look ups do not trigger name publication

[Touch-packages] [Bug 1830531] Re: .local domain look ups do not trigger name publication

[Touch-packages] [Bug 1830531] Re: .local domain look ups do not trigger name publication

[Touch-packages] [Bug 1830531] [NEW] .local domain look ups do not trigger name publication

[Touch-packages] [Bug 1830531] Re: .local domain look ups do not trigger name publication

[Touch-packages] [Bug 1830029] Re: nouveau driver for nvidia is sluggish on GTX970M to the point of unusability

[Touch-packages] [Bug 1830029] [NEW] nouveau driver for nvidia is sluggish on GTX970M to the point of unusability

[Touch-packages] [Bug 1830000] [NEW] NVIDIA driver (390) does not allow progress to login screen

[Touch-packages] [Bug 1624299] [NEW] SFTP protocol source cannot be found

[Touch-packages] [Bug 1591472] Re: Xorg crashes immediately on login returning to greeter

[Touch-packages] [Bug 1591472] Re: Xorg crashes immediately on login returning to greeter

[Touch-packages] [Bug 1610519] [NEW] apport-gtk crashes with segmentation fault

[Touch-packages] [Bug 1591472] Re: Xorg crashes immediately on login returning to greeter

[Touch-packages] [Bug 1591472] Re: Xorg crashes immediately on login returning to greeter

[Touch-packages] [Bug 1591472] Re: Xorg crashes immediately on login returning to greeter

[Touch-packages] [Bug 1591472] [NEW] Xorg crashes immediately on login returning to greeter

19 matches

Site Navigation

Mail list logo

Footer information