[Touch-packages] [Bug 1438422] Re: Hybrid laptop's accelerometer tilt interpreted as WiFi hardware switch

[Adam Colligan]

I can confirm this behavior recurred in a fresh install of Ubuntu 16.04
on this same machine.

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

Title:
  Hybrid laptop's accelerometer tilt interpreted as WiFi hardware switch

Status in compiz package in Ubuntu:
  Invalid
Status in gnome-session package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New
Status in urfkill package in Ubuntu:
  New

Bug description:
  This bug appears to be a regression in Vivid sometime in the second
  half of March 2015.

  When the machine is tilted (e.g., onto its side), Syslog reports an
  "unknown" button being pressed. When tilted back to the normal laptop
  position, the machine's WiFi disconnects and is shown as disabled in
  the connection manager. Syslog indicates that urfkill registered a
  hardware switch cutoff for the WiFi.

  I know that the accelerometers do work in other contexts and can be
  read properly in Ubuntu. As an example, this "orient" script works for
  me: https://github.com/leszakk/orient .

  Hardware: HP Envy x360 15t -- this is a hybrid touch notebook
  OS: Ubuntu 15.04 Beta 2 -- Desktop version
  Kernel:  3.19.0-10-generic
  urfkill:
    Installed: 0.6.0~20150318.103828.5539c0d.1-0ubuntu1
    Candidate: 0.6.0~20150318.103828.5539c0d.1-0ubuntu1
    Version table:
   *** 0.6.0~20150318.103828.5539c0d.1-0ubuntu1 0
  500 http://mirrors.mit.edu/ubuntu/ vivid/universe amd64 Packages
  100 /var/lib/dpkg/status

  Below is a Syslog readout from a test event. The notebook starts in
  normal typing position, the hinge bent at a right angle. At 16:13:30,
  without moving the hinge, I tip the notebook 90 degrees to the left
  from my perspective. So the Unity launcher is now closest to the
  floor, for example. I hold it there for about 10 seconds until
  16:13:40.

  Mar 30 16:13:30 [my_hostname] kernel: [ 1327.717086] atkbd serio0: Unknown 
key pressed (translated set 2, code 0xd8 on isa0060/serio0).
  Mar 30 16:13:30 [my_hostname] kernel: [ 1327.717098] atkbd serio0: Use 
'setkeycodes e058 ' to make it known.
  Mar 30 16:13:30 [my_hostname] kernel: [ 1327.724168] atkbd serio0: Unknown 
key released (translated set 2, code 0xd8 on isa0060/serio0).
  Mar 30 16:13:30 [my_hostname] kernel: [ 1327.724180] atkbd serio0: Use 
'setkeycodes e058 ' to make it known.
  Mar 30 16:13:41 [my_hostname] URfkill[868]: Setting WLAN devices to blocked
  Mar 30 16:13:41 [my_hostname] URfkill[868]: set_soft: Setting WLAN to blocked
  Mar 30 16:13:41 [my_hostname] kernel: [ 1338.698934] wlan0: deauthenticating 
from [ma:ca:dd:re:ss] by local choice (Reason: 3=DEAUTH_LEAVING)
  Mar 30 16:13:41 [my_hostname] wpa_supplicant[1015]: wlan0: 
CTRL-EVENT-DISCONNECTED bssid=[ma:ca:dd:re:ss] reason=3 locally_generated=1
  Mar 30 16:13:41 [my_hostname] kernel: [ 1338.710906] cfg80211: Calling CRDA 
to update world regulatory domain
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Interface wlan0.IPv6 no 
longer relevant for mDNS.
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Leaving mDNS multicast group 
on interface wlan0.IPv6 with address fe80::8286:f2ff:fe32:def8.
  Mar 30 16:13:41 [my_hostname] dhclient: receive_packet failed on wlan0: 
Network is down
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Interface wlan0.IPv4 no 
longer relevant for mDNS.
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Leaving mDNS multicast group 
on interface wlan0.IPv4 with address 192.168.1.133.
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Withdrawing address record 
for fe80::8286:f2ff:fe32:def8 on wlan0.
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Withdrawing address record 
for 192.168.1.133 on wlan0.
  Mar 30 16:13:41 [my_hostname] URfkill[868]: device_changed_cb: phy0
  Mar 30 16:13:41 [my_hostname] NetworkManager[863]:  Connection 
disconnected (reason -3)
  Mar 30 16:13:41 [my_hostname] NetworkManager[863]:  
[1427746421.849186] [platform/nm-linux-platform.c:1714] add_object(): Netlink 
error adding 0.0.0.0/0 via 192.168.1.1 dev wlan0 metric 1024 mss 0 src user: 
Unspecific failure
  Mar 30 16:13:41 [my_hostname] NetworkManager[863]:  
[1427746421.849417] [platform/nm-linux-platform.c:1714] add_object(): Netlink 
error adding 192.168.1.1/32 via 0.0.0.0 dev wlan0 metric 1024 mss 0 src user: 
Unspecific failure
  Mar 30 16:13:41 [my_hostname] NetworkManager[863]:  
[1427746421.849591] [platform/nm-linux-platform.c:1714] add_object(): Netlink 
error adding 0.0.0.0/0 via 192.168.1.1 dev wlan0 metric 1024 mss 0 src user: 
Unspecific failure
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Joining mDNS multicast group 
on interface wlan0.IPv4 with address 192.168.1.133.
  Mar 30 16:13:41 [my_hostname] NetworkManager[863]:  
[1427746421.849679] [nm-policy.c:693] update_ip4_routing(): Failed to set 
default route.
  Mar 30 16:13:41 [my_hostname] 

[Touch-packages] [Bug 1575301] Re: GPU Hang [i915 / drm] crashes whole session; triggered by LibreOffice dialog boxes (regression)

[Adam Colligan]

I am re-marking this "confirmed" as I don't believe there is any
requested information outstanding.

** Changed in: xorg (Ubuntu)
   Status: Incomplete => 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/1575301

Title:
  GPU Hang [i915 / drm] crashes whole session; triggered by LibreOffice
  dialog boxes (regression)

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  This behavior began sometime in April 2016 (while using Ubuntu 16.04
  Beta 2, Unity) and has continued to the present.

  Dialog boxes in LibreOffice (including the automated recovery dialog
  on LO start) started displaying garbled text and garbled or missing
  button icons. Interacting with them -- or often even their appearance
  at all -- causes a rapid crash of the whole graphical session and a
  free trip back to the login screen.  Syslog shows a GPU hang (stuck on
  render ring).

  This is an Intel Core i7-4510U with Haswell-ULT Integrated Graphics
  Controller (HP Envy x360 convertible laptop).

  Before the upgrade from 15.10 to 16.04, I had the xorg-edgers
  repository enabled and then had used the installation tool from 01.org
  to install the Intel graphics stack.  As part of troubleshooting this,
  I have removed/purged the 01.org sources/packages/modules as best I
  could (16.04 not supported) and also disabled the edgers repository.
  This has not affected the bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Apr 26 14:04:07 2016
  DistUpgraded: 2016-03-26 18:47:13,658 DEBUG enabling apt cron job
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms, 16.03.00, 4.4.0-16-generic, x86_64: installed
   fwts-efi-runtime-dkms, 16.03.00, 4.4.0-18-generic, x86_64: installed
   fwts-efi-runtime-dkms, 16.03.00, 4.4.0-21-generic, x86_64: installed
   vboxhost, 5.0.18, 4.4.0-18-generic, x86_64: installed
   vboxhost, 5.0.18, 4.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics 
Controller [103c:22d6]
  InstallationDate: Installed on 2014-08-10 (625 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Hewlett-Packard HP ENVY 15 x360 PC
  PlymouthDebug: Error: [Errno 13] Permission denied: 
'/var/log/plymouth-debug.log'
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=5ad8035a-f2a4-4334-84d8-e2a8a7396bf8 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-03-26 (30 days ago)
  dmi.bios.date: 01/19/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.26
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 22D6
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 89.23
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.26:bd01/19/2015:svnHewlett-Packard:pnHPENVY15x360PC:pvr0974100022405F0420180:rvnHewlett-Packard:rn22D6:rvr89.23:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY 15 x360 PC
  dmi.product.version: 0974100022405F0420180
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Apr 26 14:02:01 2016
  xserver.configfile: default
  xserver.errors:
   Failed to load module "intel" (module does not exist, 0)
   Failed to load module "intel" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.3-1ubuntu2
  xserver.video_driver: modeset

To manage notifications about this bug go to:

[Touch-packages] [Bug 1575301] Re: GPU Hang [i915 / drm] crashes whole session; triggered by LibreOffice dialog boxes (regression)

[Adam Colligan]

Please let me know if there is any further information that can be
supplied to re-establish the bug as "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/1575301

Title:
  GPU Hang [i915 / drm] crashes whole session; triggered by LibreOffice
  dialog boxes (regression)

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  This behavior began sometime in April 2016 (while using Ubuntu 16.04
  Beta 2, Unity) and has continued to the present.

  Dialog boxes in LibreOffice (including the automated recovery dialog
  on LO start) started displaying garbled text and garbled or missing
  button icons. Interacting with them -- or often even their appearance
  at all -- causes a rapid crash of the whole graphical session and a
  free trip back to the login screen.  Syslog shows a GPU hang (stuck on
  render ring).

  This is an Intel Core i7-4510U with Haswell-ULT Integrated Graphics
  Controller (HP Envy x360 convertible laptop).

  Before the upgrade from 15.10 to 16.04, I had the xorg-edgers
  repository enabled and then had used the installation tool from 01.org
  to install the Intel graphics stack.  As part of troubleshooting this,
  I have removed/purged the 01.org sources/packages/modules as best I
  could (16.04 not supported) and also disabled the edgers repository.
  This has not affected the bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Apr 26 14:04:07 2016
  DistUpgraded: 2016-03-26 18:47:13,658 DEBUG enabling apt cron job
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms, 16.03.00, 4.4.0-16-generic, x86_64: installed
   fwts-efi-runtime-dkms, 16.03.00, 4.4.0-18-generic, x86_64: installed
   fwts-efi-runtime-dkms, 16.03.00, 4.4.0-21-generic, x86_64: installed
   vboxhost, 5.0.18, 4.4.0-18-generic, x86_64: installed
   vboxhost, 5.0.18, 4.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics 
Controller [103c:22d6]
  InstallationDate: Installed on 2014-08-10 (625 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Hewlett-Packard HP ENVY 15 x360 PC
  PlymouthDebug: Error: [Errno 13] Permission denied: 
'/var/log/plymouth-debug.log'
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=5ad8035a-f2a4-4334-84d8-e2a8a7396bf8 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-03-26 (30 days ago)
  dmi.bios.date: 01/19/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.26
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 22D6
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 89.23
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.26:bd01/19/2015:svnHewlett-Packard:pnHPENVY15x360PC:pvr0974100022405F0420180:rvnHewlett-Packard:rn22D6:rvr89.23:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY 15 x360 PC
  dmi.product.version: 0974100022405F0420180
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Apr 26 14:02:01 2016
  xserver.configfile: default
  xserver.errors:
   Failed to load module "intel" (module does not exist, 0)
   Failed to load module "intel" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.3-1ubuntu2
  xserver.video_driver: modeset

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

-- 
Mailing 

[Touch-packages] [Bug 1575301] Re: GPU Hang [i915 / drm] crashes whole session; triggered by LibreOffice dialog boxes (regression)

[Adam Colligan]

This is an HP Envy x360 15-u011dx .

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

Title:
  GPU Hang [i915 / drm] crashes whole session; triggered by LibreOffice
  dialog boxes (regression)

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  This behavior began sometime in April 2016 (while using Ubuntu 16.04
  Beta 2, Unity) and has continued to the present.

  Dialog boxes in LibreOffice (including the automated recovery dialog
  on LO start) started displaying garbled text and garbled or missing
  button icons. Interacting with them -- or often even their appearance
  at all -- causes a rapid crash of the whole graphical session and a
  free trip back to the login screen.  Syslog shows a GPU hang (stuck on
  render ring).

  This is an Intel Core i7-4510U with Haswell-ULT Integrated Graphics
  Controller (HP Envy x360 convertible laptop).

  Before the upgrade from 15.10 to 16.04, I had the xorg-edgers
  repository enabled and then had used the installation tool from 01.org
  to install the Intel graphics stack.  As part of troubleshooting this,
  I have removed/purged the 01.org sources/packages/modules as best I
  could (16.04 not supported) and also disabled the edgers repository.
  This has not affected the bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Apr 26 14:04:07 2016
  DistUpgraded: 2016-03-26 18:47:13,658 DEBUG enabling apt cron job
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms, 16.03.00, 4.4.0-16-generic, x86_64: installed
   fwts-efi-runtime-dkms, 16.03.00, 4.4.0-18-generic, x86_64: installed
   fwts-efi-runtime-dkms, 16.03.00, 4.4.0-21-generic, x86_64: installed
   vboxhost, 5.0.18, 4.4.0-18-generic, x86_64: installed
   vboxhost, 5.0.18, 4.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics 
Controller [103c:22d6]
  InstallationDate: Installed on 2014-08-10 (625 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Hewlett-Packard HP ENVY 15 x360 PC
  PlymouthDebug: Error: [Errno 13] Permission denied: 
'/var/log/plymouth-debug.log'
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=5ad8035a-f2a4-4334-84d8-e2a8a7396bf8 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-03-26 (30 days ago)
  dmi.bios.date: 01/19/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.26
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 22D6
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 89.23
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.26:bd01/19/2015:svnHewlett-Packard:pnHPENVY15x360PC:pvr0974100022405F0420180:rvnHewlett-Packard:rn22D6:rvr89.23:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY 15 x360 PC
  dmi.product.version: 0974100022405F0420180
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Apr 26 14:02:01 2016
  xserver.configfile: default
  xserver.errors:
   Failed to load module "intel" (module does not exist, 0)
   Failed to load module "intel" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.3-1ubuntu2
  xserver.video_driver: modeset

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

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

[Touch-packages] [Bug 1575301] Re: GPU Hang [i915 / drm] crashes whole session; triggered by LibreOffice dialog boxes (regression)

[Adam Colligan]

I have now installed kubuntu-desktop and am running LibreOffice (and
everything else) in KDE/Plasma. There is still some garbling in some
dialog window text, but the GPU hang has not recurred in this Desktop
Environment.

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

Title:
  GPU Hang [i915 / drm] crashes whole session; triggered by LibreOffice
  dialog boxes (regression)

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  This behavior began sometime in April 2016 (while using Ubuntu 16.04
  Beta 2, Unity) and has continued to the present.

  Dialog boxes in LibreOffice (including the automated recovery dialog
  on LO start) started displaying garbled text and garbled or missing
  button icons. Interacting with them -- or often even their appearance
  at all -- causes a rapid crash of the whole graphical session and a
  free trip back to the login screen.  Syslog shows a GPU hang (stuck on
  render ring).

  This is an Intel Core i7-4510U with Haswell-ULT Integrated Graphics
  Controller (HP Envy x360 convertible laptop).

  Before the upgrade from 15.10 to 16.04, I had the xorg-edgers
  repository enabled and then had used the installation tool from 01.org
  to install the Intel graphics stack.  As part of troubleshooting this,
  I have removed/purged the 01.org sources/packages/modules as best I
  could (16.04 not supported) and also disabled the edgers repository.
  This has not affected the bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Apr 26 14:04:07 2016
  DistUpgraded: 2016-03-26 18:47:13,658 DEBUG enabling apt cron job
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   fwts-efi-runtime-dkms, 16.03.00, 4.4.0-16-generic, x86_64: installed
   fwts-efi-runtime-dkms, 16.03.00, 4.4.0-18-generic, x86_64: installed
   fwts-efi-runtime-dkms, 16.03.00, 4.4.0-21-generic, x86_64: installed
   vboxhost, 5.0.18, 4.4.0-18-generic, x86_64: installed
   vboxhost, 5.0.18, 4.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics 
Controller [103c:22d6]
  InstallationDate: Installed on 2014-08-10 (625 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Hewlett-Packard HP ENVY 15 x360 PC
  PlymouthDebug: Error: [Errno 13] Permission denied: 
'/var/log/plymouth-debug.log'
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=5ad8035a-f2a4-4334-84d8-e2a8a7396bf8 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-03-26 (30 days ago)
  dmi.bios.date: 01/19/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.26
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 22D6
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 89.23
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.26:bd01/19/2015:svnHewlett-Packard:pnHPENVY15x360PC:pvr0974100022405F0420180:rvnHewlett-Packard:rn22D6:rvr89.23:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY 15 x360 PC
  dmi.product.version: 0974100022405F0420180
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Apr 26 14:02:01 2016
  xserver.configfile: default
  xserver.errors:
   Failed to load module "intel" (module does not exist, 0)
   Failed to load module "intel" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.3-1ubuntu2
  xserver.video_driver: modeset

To manage notifications about 

[Touch-packages] [Bug 1575301] Re: GPU Hang [i915 / drm] crashes whole session; triggered by LibreOffice dialog boxes (regression)

[Adam Colligan]

** Description changed:

  This behavior began sometime in April 2016 (while using Ubuntu 16.04
  Beta 2, Unity) and has continued to the present.
  
  Dialog boxes in LibreOffice (including the automated recovery dialog on
  LO start) started displaying garbled text and garbled or missing button
  icons. Interacting with them -- or often even their appearance at all --
  causes a rapid crash of the whole graphical session and a free trip back
- to the login screen.  Syslog shows a GPU hang.
+ to the login screen.  Syslog shows a GPU hang (stuck on render ring).
  
  This is an Intel Core i7-4510U with Haswell-ULT Integrated Graphics
  Controller (HP Envy x360 convertible laptop).
  
  Before the upgrade from 15.10 to 16.04, I had the xorg-edgers repository
  enabled and then had used the installation tool from 01.org to install
  the Intel graphics stack.  As part of troubleshooting this, I have
  removed/purged the 01.org sources/packages/modules as best I could
  (16.04 not supported) and also disabled the edgers repository. This has
  not affected the bug.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
-  
+ 
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Tue Apr 26 14:04:07 2016
  DistUpgraded: 2016-03-26 18:47:13,658 DEBUG enabling apt cron job
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
-  fwts-efi-runtime-dkms, 16.03.00, 4.4.0-16-generic, x86_64: installed
-  fwts-efi-runtime-dkms, 16.03.00, 4.4.0-18-generic, x86_64: installed
-  fwts-efi-runtime-dkms, 16.03.00, 4.4.0-21-generic, x86_64: installed
-  vboxhost, 5.0.18, 4.4.0-18-generic, x86_64: installed
-  vboxhost, 5.0.18, 4.4.0-21-generic, x86_64: installed
+  fwts-efi-runtime-dkms, 16.03.00, 4.4.0-16-generic, x86_64: installed
+  fwts-efi-runtime-dkms, 16.03.00, 4.4.0-18-generic, x86_64: installed
+  fwts-efi-runtime-dkms, 16.03.00, 4.4.0-21-generic, x86_64: installed
+  vboxhost, 5.0.18, 4.4.0-18-generic, x86_64: installed
+  vboxhost, 5.0.18, 4.4.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
-Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics 
Controller [103c:22d6]
+  Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
+    Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics 
Controller [103c:22d6]
  InstallationDate: Installed on 2014-08-10 (625 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Hewlett-Packard HP ENVY 15 x360 PC
  PlymouthDebug: Error: [Errno 13] Permission denied: 
'/var/log/plymouth-debug.log'
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=5ad8035a-f2a4-4334-84d8-e2a8a7396bf8 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-03-26 (30 days ago)
  dmi.bios.date: 01/19/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.26
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 22D6
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 89.23
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.26:bd01/19/2015:svnHewlett-Packard:pnHPENVY15x360PC:pvr0974100022405F0420180:rvnHewlett-Packard:rn22D6:rvr89.23:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY 15 x360 PC
  dmi.product.version: 0974100022405F0420180
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Apr 26 14:02:01 2016
  xserver.configfile: default
  xserver.errors:
-  Failed to load module "intel" (module does not exist, 0)
-  Failed to load module "intel" (module does not exist, 0)
+  Failed to load module "intel" (module does not exist, 0)
+  Failed to load 

[Touch-packages] [Bug 1575301] [NEW] GPU Hang [i915 / drm] crashes whole session; triggered by LibreOffice dialog boxes (regression)

[Adam Colligan]

Public bug reported:

This behavior began sometime in April 2016 (while using Ubuntu 16.04
Beta 2, Unity) and has continued to the present.

Dialog boxes in LibreOffice (including the automated recovery dialog on
LO start) started displaying garbled text and garbled or missing button
icons. Interacting with them -- or often even their appearance at all --
causes a rapid crash of the whole graphical session and a free trip back
to the login screen.  Syslog shows a GPU hang.

This is an Intel Core i7-4510U with Haswell-ULT Integrated Graphics
Controller (HP Envy x360 convertible laptop).

Before the upgrade from 15.10 to 16.04, I had the xorg-edgers repository
enabled and then had used the installation tool from 01.org to install
the Intel graphics stack.  As part of troubleshooting this, I have
removed/purged the 01.org sources/packages/modules as best I could
(16.04 not supported) and also disabled the edgers repository. This has
not affected the bug.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
Uname: Linux 4.4.0-21-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Tue Apr 26 14:04:07 2016
DistUpgraded: 2016-03-26 18:47:13,658 DEBUG enabling apt cron job
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 fwts-efi-runtime-dkms, 16.03.00, 4.4.0-16-generic, x86_64: installed
 fwts-efi-runtime-dkms, 16.03.00, 4.4.0-18-generic, x86_64: installed
 fwts-efi-runtime-dkms, 16.03.00, 4.4.0-21-generic, x86_64: installed
 vboxhost, 5.0.18, 4.4.0-18-generic, x86_64: installed
 vboxhost, 5.0.18, 4.4.0-21-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
0b) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics 
Controller [103c:22d6]
InstallationDate: Installed on 2014-08-10 (625 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: Hewlett-Packard HP ENVY 15 x360 PC
PlymouthDebug: Error: [Errno 13] Permission denied: 
'/var/log/plymouth-debug.log'
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=5ad8035a-f2a4-4334-84d8-e2a8a7396bf8 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2016-03-26 (30 days ago)
dmi.bios.date: 01/19/2015
dmi.bios.vendor: Insyde
dmi.bios.version: F.26
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 22D6
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 89.23
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.26:bd01/19/2015:svnHewlett-Packard:pnHPENVY15x360PC:pvr0974100022405F0420180:rvnHewlett-Packard:rn22D6:rvr89.23:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP ENVY 15 x360 PC
dmi.product.version: 0974100022405F0420180
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Tue Apr 26 14:02:01 2016
xserver.configfile: default
xserver.errors:
 Failed to load module "intel" (module does not exist, 0)
 Failed to load module "intel" (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.3-1ubuntu2
xserver.video_driver: modeset

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


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

** Attachment added: "copy of /sys/class/drm/card0/error"
   
https://bugs.launchpad.net/bugs/1575301/+attachment/4648182/+files/i915_hang_dump

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

Title:
  GPU Hang [i915 / drm] crashes whole session; triggered by LibreOffice
  dialog boxes (regression)

Status in xorg package in Ubuntu:
  New

Bug description:
  This behavior began sometime in April 2016 (while using Ubuntu 16.04
  Beta 2, Unity) and has continued to the present.

  Dialog boxes in LibreOffice 

[Touch-packages] [Bug 1539811] Re: Mir crashed with std::exception::what: Couldn't clear output eDP-1 (drmModeSetCrtc = -13)

[Adam Colligan]

I tried this yesterday with the latest daily 16.04 image and just wanted
to note that the user-facing behavior is the same. I didn't check the
logs to see if the same messages were appearing but could do more if it
would help.

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

Title:
  Mir crashed with std::exception::what: Couldn't clear output eDP-1
  (drmModeSetCrtc = -13)

Status in Mir:
  Confirmed
Status in Unity System Compositor:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in unity-system-compositor package in Ubuntu:
  Confirmed

Bug description:
  This is a live USB environment (16.04, 2016-01-29 image). HP Envy x360
  hybrid notebook. Package installed: 1.0.12+15.10.20150609-0ubuntu1 .

  After installing the mir desktop session package and choosing
  "logout", the greeter correctly shows Unity8 as a login option. After
  entering "ubuntu" and a blank password, the screen goes to black (with
  backight), the fan runs for a few seconds of high activity, and no
  graphical session ever actually starts.  The other tty screens remain
  available, and lightdm is eventually able to restart (though only
  after some time, and it is unclear if the commands to restart it are
  actually helping).

  Some selected error messages from the time of session login:

  *From lightdm.log*:
  [+158.12s] DEBUG: Session pid=6899: Greeter requests session unity8-mir
  [+158.12s] CRITICAL: g_dbus_connection_call_sync_internal: assertion 
'object_path != NULL && g_variant_is_object_path (object_path)' failed

  *From unity-system-compositor.log*:
  dm_connection_start
  ERROR: Throw location unknown (consider using BOOST_THROW_EXCEPTION)
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: write: Broken pipe
  ...
  Closing session GDK-Mir
  ERROR: 
/build/mir-UeyFew/mir-0.19.0+16.04.20160128/src/common/fatal/fatal.cpp(55): 
Throw in function void mir::fatal_error_except(const char*, ...)
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: Couldn't clear output eDP-1 (drmModeSetCrtc = -13)

  *From syslog*:
  Jan 29 22:40:41 ubuntu org.freedesktop.Notifications[7323]: Failed to connect 
to Mir: Failed to connect to server socket: No such file or directory
  Jan 29 22:40:41 ubuntu org.freedesktop.Notifications[7323]: Unable to init 
server: Could not connect: Connection refused
  Jan 29 22:40:41 ubuntu org.freedesktop.Notifications[7323]: 
(notify-osd:7672): Gtk-WARNING **: cannot open display:
  Jan 29 22:40:42 ubuntu dbus[1325]: [system] Activating service 
name='com.canonical.SystemImage' (using servicehelper)
  Jan 29 22:40:42 ubuntu com.canonical.SystemImage[1325]: usage: 
system-image-dbus [-h] [--version] [-C DIRECTORY] [-v]
  Jan 29 22:40:42 ubuntu com.canonical.SystemImage[1325]: system-image-dbus: 
error:
  Jan 29 22:40:42 ubuntu com.canonical.SystemImage[1325]: Configuration 
directory not found: .load() requires a directory: /etc/system-image/config.d
  Jan 29 22:40:42 ubuntu dbus[1325]: [system] Activated service 
'com.canonical.SystemImage' failed: Launcher could not run (out of memory)

  The Unity8.log and Unity8-dash.log files are just repetitions of:
  QXcbConnection: Could not connect to display .

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1539811/+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 1484587] Re: CPU frequency management fails to re-engage on resume from suspend

[Adam Colligan]

I have not noticed this problem on later kernels; I'm going to mark it
as "fix released" for Linux and "invalid" for pm-utils. I hope that's
the right course of action.

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

** Changed in: pm-utils (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  CPU frequency management fails to re-engage on resume from suspend

Status in linux package in Ubuntu:
  Fix Released
Status in pm-utils package in Ubuntu:
  Invalid

Bug description:
  Behavior:

  CPU frequency management fails to re-engage on resume from suspend. On
  resume, the CPUs are stuck around a single frequency (usually a low
  idle frequency).

  I use indicator-cpufreq for manual governor control. On resume,
  indicator-cpufreq indicates the low frequency state in its live cpu
  performance display in the icon. However, in its governor menu, it
  still shows as in use whichever governor was selected before suspend,
  even though that governor is not actually or properly controlling the
  CPU state.

  Upon manually switching to the unused governor in indicator-cpufreq,
  this behavior resolves, and the newly-chosen governor begins
  performing its duties. I can then immediately switch back to the
  desired (pre-suspend) governor with no issues.

  PM logs appear to show a successful resume of cpu frequency
  management, even though the modules did not actually gain effective
  control of the processor frequencies.

  
  Expected behavior:

  On resume, the CPU frequencies should continue being managed as they
  were before suspend without the need for manual user input.  Also, in
  the event that they do not, an error/warning should appear -- if not
  to the user, then in the pm suspend/resume logs.

  
  Other information that may or may not be relevant:

  On this system, the "powersave" governor is always automatically
  chosen at startup, although not until a minute or so after session
  login. The choice of an alternate governor "performance" from
  indicator-cpufreq is not persistent across reboots. Further, if I
  manually toggle the governors at the beginning of my first session
  after boot, and I settle on "performance", some automated script will
  force it back to "powersave" at the usual time about a minute after
  login. To use the "performance" governor, I must select it after
  waiting an interval following login, and I must always switch to
  powersave and back to performance after each resume from suspend.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-25-generic 3.19.0-25.26
  ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  adam   3887 F pulseaudio
   /dev/snd/controlC1:  adam   3887 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Aug 13 11:41:27 2015
  InstallationDate: Installed on 2014-08-10 (368 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Hewlett-Packard HP ENVY 15 x360 PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-25-generic.efi.signed 
root=UUID=5ad8035a-f2a4-4334-84d8-e2a8a7396bf8 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-25-generic N/A
   linux-backports-modules-3.19.0-25-generic  N/A
   linux-firmware 1.143.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/19/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.26
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 22D6
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 89.23
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.26:bd01/19/2015:svnHewlett-Packard:pnHPENVY15x360PC:pvr0974100022405F0420180:rvnHewlett-Packard:rn22D6:rvr89.23:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY 15 x360 PC
  dmi.product.version: 0974100022405F0420180
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1484587/+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 1546774] [NEW] network interfaces and network-manager fail to load on boot

[Adam Colligan]

Public bug reported:

This is a sporadic problem on boot of this system (an HP Envy x360).

After boot, both before and after login, there is no network
connectivity. The network-manager GUI indicator does not load, and I am
unable to bring "up" any interfaces manually. A full reboot is required,
which generally results in normal operation.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: network-manager 1.0.4-0ubuntu5.2
ProcVersionSignature: Ubuntu 4.2.0-29.34-generic 4.2.8-ckt3
Uname: Linux 4.2.0-29-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Feb 17 16:40:00 2016
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2014-08-10 (556 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
IpRoute:
 
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 
8: Error: NetworkManager is not running.
nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 
8: Error: NetworkManager is not running.
nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: 
Error: Object 'nm' is unknown, try 'nmcli help'.

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


** Tags: amd64 apport-bug third-party-packages wily

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

Title:
  network interfaces and network-manager fail to load on boot

Status in network-manager package in Ubuntu:
  New

Bug description:
  This is a sporadic problem on boot of this system (an HP Envy x360).

  After boot, both before and after login, there is no network
  connectivity. The network-manager GUI indicator does not load, and I
  am unable to bring "up" any interfaces manually. A full reboot is
  required, which generally results in normal operation.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: network-manager 1.0.4-0ubuntu5.2
  ProcVersionSignature: Ubuntu 4.2.0-29.34-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-29-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Feb 17 16:40:00 2016
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2014-08-10 (556 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  IpRoute:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con: Error: command ['nmcli', '-f', 'all', 'con'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-dev: Error: command ['nmcli', '-f', 'all', 'dev'] failed with exit code 
8: Error: NetworkManager is not running.
  nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 
2: Error: Object 'nm' is unknown, try 'nmcli help'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1546774/+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 1539811] Re: Mir crashed with std::exception::what: Couldn't clear output eDP-1 (drmModeSetCrtc = -13)

[Adam Colligan]

@Daniel, let me know if there's something I can test for you (or a
different log I can scrape) to check if something is turning the screen
off when I try to enter the Mir session.

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

Title:
  Mir crashed with std::exception::what: Couldn't clear output eDP-1
  (drmModeSetCrtc = -13)

Status in Mir:
  Confirmed
Status in Unity System Compositor:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in unity-system-compositor package in Ubuntu:
  Confirmed

Bug description:
  This is a live USB environment (16.04, 2016-01-29 image). HP Envy x360
  hybrid notebook. Package installed: 1.0.12+15.10.20150609-0ubuntu1 .

  After installing the mir desktop session package and choosing
  "logout", the greeter correctly shows Unity8 as a login option. After
  entering "ubuntu" and a blank password, the screen goes to black (with
  backight), the fan runs for a few seconds of high activity, and no
  graphical session ever actually starts.  The other tty screens remain
  available, and lightdm is eventually able to restart (though only
  after some time, and it is unclear if the commands to restart it are
  actually helping).

  Some selected error messages from the time of session login:

  *From lightdm.log*:
  [+158.12s] DEBUG: Session pid=6899: Greeter requests session unity8-mir
  [+158.12s] CRITICAL: g_dbus_connection_call_sync_internal: assertion 
'object_path != NULL && g_variant_is_object_path (object_path)' failed

  *From unity-system-compositor.log*:
  dm_connection_start
  ERROR: Throw location unknown (consider using BOOST_THROW_EXCEPTION)
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: write: Broken pipe
  ...
  Closing session GDK-Mir
  ERROR: 
/build/mir-UeyFew/mir-0.19.0+16.04.20160128/src/common/fatal/fatal.cpp(55): 
Throw in function void mir::fatal_error_except(const char*, ...)
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: Couldn't clear output eDP-1 (drmModeSetCrtc = -13)

  *From syslog*:
  Jan 29 22:40:41 ubuntu org.freedesktop.Notifications[7323]: Failed to connect 
to Mir: Failed to connect to server socket: No such file or directory
  Jan 29 22:40:41 ubuntu org.freedesktop.Notifications[7323]: Unable to init 
server: Could not connect: Connection refused
  Jan 29 22:40:41 ubuntu org.freedesktop.Notifications[7323]: 
(notify-osd:7672): Gtk-WARNING **: cannot open display:
  Jan 29 22:40:42 ubuntu dbus[1325]: [system] Activating service 
name='com.canonical.SystemImage' (using servicehelper)
  Jan 29 22:40:42 ubuntu com.canonical.SystemImage[1325]: usage: 
system-image-dbus [-h] [--version] [-C DIRECTORY] [-v]
  Jan 29 22:40:42 ubuntu com.canonical.SystemImage[1325]: system-image-dbus: 
error:
  Jan 29 22:40:42 ubuntu com.canonical.SystemImage[1325]: Configuration 
directory not found: .load() requires a directory: /etc/system-image/config.d
  Jan 29 22:40:42 ubuntu dbus[1325]: [system] Activated service 
'com.canonical.SystemImage' failed: Launcher could not run (out of memory)

  The Unity8.log and Unity8-dash.log files are just repetitions of:
  QXcbConnection: Could not connect to display .

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1539811/+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 1484587] Re: CPU frequency management fails to re-engage on resume from suspend

[Adam Colligan]

I have tried to recreate this with the following two mainline kernels:

v4.2-rc6-unstable
v4.2.0-999 (201508130157)

However, it is somewhat difficult to compare the behavior apples-to-
apples the way I normally do, as cpupower is not available for those
kernels (no linux-tools packages installed for them).  I would
appreciate any advice on the best way to show the problem's
presence/absence in an objective or definitive way across kernels.

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

Title:
  CPU frequency management fails to re-engage on resume from suspend

Status in linux package in Ubuntu:
  Confirmed
Status in pm-utils package in Ubuntu:
  New

Bug description:
  Behavior:

  CPU frequency management fails to re-engage on resume from suspend. On
  resume, the CPUs are stuck around a single frequency (usually a low
  idle frequency).

  I use indicator-cpufreq for manual governor control. On resume,
  indicator-cpufreq indicates the low frequency state in its live cpu
  performance display in the icon. However, in its governor menu, it
  still shows as in use whichever governor was selected before suspend,
  even though that governor is not actually or properly controlling the
  CPU state.

  Upon manually switching to the unused governor in indicator-cpufreq,
  this behavior resolves, and the newly-chosen governor begins
  performing its duties. I can then immediately switch back to the
  desired (pre-suspend) governor with no issues.

  PM logs appear to show a successful resume of cpu frequency
  management, even though the modules did not actually gain effective
  control of the processor frequencies.

  
  Expected behavior:

  On resume, the CPU frequencies should continue being managed as they
  were before suspend without the need for manual user input.  Also, in
  the event that they do not, an error/warning should appear -- if not
  to the user, then in the pm suspend/resume logs.

  
  Other information that may or may not be relevant:

  On this system, the powersave governor is always automatically
  chosen at startup, although not until a minute or so after session
  login. The choice of an alternate governor performance from
  indicator-cpufreq is not persistent across reboots. Further, if I
  manually toggle the governors at the beginning of my first session
  after boot, and I settle on performance, some automated script will
  force it back to powersave at the usual time about a minute after
  login. To use the performance governor, I must select it after
  waiting an interval following login, and I must always switch to
  powersave and back to performance after each resume from suspend.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-25-generic 3.19.0-25.26
  ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  adam   3887 F pulseaudio
   /dev/snd/controlC1:  adam   3887 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Aug 13 11:41:27 2015
  InstallationDate: Installed on 2014-08-10 (368 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: Hewlett-Packard HP ENVY 15 x360 PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-25-generic.efi.signed 
root=UUID=5ad8035a-f2a4-4334-84d8-e2a8a7396bf8 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-25-generic N/A
   linux-backports-modules-3.19.0-25-generic  N/A
   linux-firmware 1.143.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/19/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.26
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 22D6
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 89.23
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.26:bd01/19/2015:svnHewlett-Packard:pnHPENVY15x360PC:pvr0974100022405F0420180:rvnHewlett-Packard:rn22D6:rvr89.23:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY 15 x360 PC
  dmi.product.version: 0974100022405F0420180
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1484587/+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 1484587] Re: CPU frequency management fails to re-engage on resume from suspend

[Adam Colligan]

** Attachment added: kern.log from session in which cpu freq control failed on 
resume from suspend
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1484587/+attachment/227/+files/kern_log_cpu_resume_bug.txt

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

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

Title:
  CPU frequency management fails to re-engage on resume from suspend

Status in linux package in Ubuntu:
  Confirmed
Status in pm-utils package in Ubuntu:
  New

Bug description:
  Behavior:

  CPU frequency management fails to re-engage on resume from suspend. On
  resume, the CPUs are stuck around a single frequency (usually a low
  idle frequency).

  I use indicator-cpufreq for manual governor control. On resume,
  indicator-cpufreq indicates the low frequency state in its live cpu
  performance display in the icon. However, in its governor menu, it
  still shows as in use whichever governor was selected before suspend,
  even though that governor is not actually or properly controlling the
  CPU state.

  Upon manually switching to the unused governor in indicator-cpufreq,
  this behavior resolves, and the newly-chosen governor begins
  performing its duties. I can then immediately switch back to the
  desired (pre-suspend) governor with no issues.

  PM logs appear to show a successful resume of cpu frequency
  management, even though the modules did not actually gain effective
  control of the processor frequencies.

  
  Expected behavior:

  On resume, the CPU frequencies should continue being managed as they
  were before suspend without the need for manual user input.  Also, in
  the event that they do not, an error/warning should appear -- if not
  to the user, then in the pm suspend/resume logs.

  
  Other information that may or may not be relevant:

  On this system, the powersave governor is always automatically
  chosen at startup, although not until a minute or so after session
  login. The choice of an alternate governor performance from
  indicator-cpufreq is not persistent across reboots. Further, if I
  manually toggle the governors at the beginning of my first session
  after boot, and I settle on performance, some automated script will
  force it back to powersave at the usual time about a minute after
  login. To use the performance governor, I must select it after
  waiting an interval following login, and I must always switch to
  powersave and back to performance after each resume from suspend.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-3.19.0-25-generic 3.19.0-25.26
  ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
  Uname: Linux 3.19.0-25-generic x86_64
  ApportVersion: 2.17.2-0ubuntu1.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  adam   3887 F pulseaudio
   /dev/snd/controlC1:  adam   3887 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Aug 13 11:41:27 2015
  InstallationDate: Installed on 2014-08-10 (368 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  MachineType: Hewlett-Packard HP ENVY 15 x360 PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.19.0-25-generic.efi.signed 
root=UUID=5ad8035a-f2a4-4334-84d8-e2a8a7396bf8 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-25-generic N/A
   linux-backports-modules-3.19.0-25-generic  N/A
   linux-firmware 1.143.3
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/19/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.26
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 22D6
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 89.23
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.26:bd01/19/2015:svnHewlett-Packard:pnHPENVY15x360PC:pvr0974100022405F0420180:rvnHewlett-Packard:rn22D6:rvr89.23:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.name: HP ENVY 15 x360 PC
  dmi.product.version: 0974100022405F0420180
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1484587/+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 1438422] Re: Hybrid laptop's accelerometer tilt interpreted as WiFi hardware switch

[Adam Colligan]

Tested 3.16.0-29  . Bug behavior appeared to be the same.

It might also be worth noting that sometimes, even when I re-enable
WiFi, the network manager does not recognize available networks.
However, I can connect if I choose to connect to a hidden network and
then select from a list of potential hidden networks one that I know is
active and in range. After that successful connection, network manager
begins displaying that and other networks properly. I have assumed that
this is just to do with the messy way in which the OS thinks the WiFi
has been turned on or off by hardware switch, but maybe it's some kind
of clue by itself.

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

Title:
  Hybrid laptop's accelerometer tilt interpreted as WiFi hardware switch

Status in compiz package in Ubuntu:
  Invalid
Status in gnome-session package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New
Status in urfkill package in Ubuntu:
  New

Bug description:
  This bug appears to be a regression in Vivid sometime in the second
  half of March 2015.

  When the machine is tilted (e.g., onto its side), Syslog reports an
  unknown button being pressed. When tilted back to the normal laptop
  position, the machine's WiFi disconnects and is shown as disabled in
  the connection manager. Syslog indicates that urfkill registered a
  hardware switch cutoff for the WiFi.

  I know that the accelerometers do work in other contexts and can be
  read properly in Ubuntu. As an example, this orient script works for
  me: https://github.com/leszakk/orient .

  Hardware: HP Envy x360 15t -- this is a hybrid touch notebook
  OS: Ubuntu 15.04 Beta 2 -- Desktop version
  Kernel:  3.19.0-10-generic
  urfkill:
    Installed: 0.6.0~20150318.103828.5539c0d.1-0ubuntu1
    Candidate: 0.6.0~20150318.103828.5539c0d.1-0ubuntu1
    Version table:
   *** 0.6.0~20150318.103828.5539c0d.1-0ubuntu1 0
  500 http://mirrors.mit.edu/ubuntu/ vivid/universe amd64 Packages
  100 /var/lib/dpkg/status

  Below is a Syslog readout from a test event. The notebook starts in
  normal typing position, the hinge bent at a right angle. At 16:13:30,
  without moving the hinge, I tip the notebook 90 degrees to the left
  from my perspective. So the Unity launcher is now closest to the
  floor, for example. I hold it there for about 10 seconds until
  16:13:40.

  Mar 30 16:13:30 [my_hostname] kernel: [ 1327.717086] atkbd serio0: Unknown 
key pressed (translated set 2, code 0xd8 on isa0060/serio0).
  Mar 30 16:13:30 [my_hostname] kernel: [ 1327.717098] atkbd serio0: Use 
'setkeycodes e058 keycode' to make it known.
  Mar 30 16:13:30 [my_hostname] kernel: [ 1327.724168] atkbd serio0: Unknown 
key released (translated set 2, code 0xd8 on isa0060/serio0).
  Mar 30 16:13:30 [my_hostname] kernel: [ 1327.724180] atkbd serio0: Use 
'setkeycodes e058 keycode' to make it known.
  Mar 30 16:13:41 [my_hostname] URfkill[868]: Setting WLAN devices to blocked
  Mar 30 16:13:41 [my_hostname] URfkill[868]: set_soft: Setting WLAN to blocked
  Mar 30 16:13:41 [my_hostname] kernel: [ 1338.698934] wlan0: deauthenticating 
from [ma:ca:dd:re:ss] by local choice (Reason: 3=DEAUTH_LEAVING)
  Mar 30 16:13:41 [my_hostname] wpa_supplicant[1015]: wlan0: 
CTRL-EVENT-DISCONNECTED bssid=[ma:ca:dd:re:ss] reason=3 locally_generated=1
  Mar 30 16:13:41 [my_hostname] kernel: [ 1338.710906] cfg80211: Calling CRDA 
to update world regulatory domain
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Interface wlan0.IPv6 no 
longer relevant for mDNS.
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Leaving mDNS multicast group 
on interface wlan0.IPv6 with address fe80::8286:f2ff:fe32:def8.
  Mar 30 16:13:41 [my_hostname] dhclient: receive_packet failed on wlan0: 
Network is down
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Interface wlan0.IPv4 no 
longer relevant for mDNS.
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Leaving mDNS multicast group 
on interface wlan0.IPv4 with address 192.168.1.133.
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Withdrawing address record 
for fe80::8286:f2ff:fe32:def8 on wlan0.
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Withdrawing address record 
for 192.168.1.133 on wlan0.
  Mar 30 16:13:41 [my_hostname] URfkill[868]: device_changed_cb: phy0
  Mar 30 16:13:41 [my_hostname] NetworkManager[863]: warn Connection 
disconnected (reason -3)
  Mar 30 16:13:41 [my_hostname] NetworkManager[863]: error 
[1427746421.849186] [platform/nm-linux-platform.c:1714] add_object(): Netlink 
error adding 0.0.0.0/0 via 192.168.1.1 dev wlan0 metric 1024 mss 0 src user: 
Unspecific failure
  Mar 30 16:13:41 [my_hostname] NetworkManager[863]: error 
[1427746421.849417] [platform/nm-linux-platform.c:1714] add_object(): Netlink 
error adding 192.168.1.1/32 via 0.0.0.0 dev wlan0 metric 1024 mss 0 src user: 

[Touch-packages] [Bug 1438422] Re: Hybrid laptop's accelerometer tilt interpreted as WiFi hardware switch

[Adam Colligan]

I am currently working around the problem by setting key control to
false in /etc/urfkill/urfkill.conf .

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

Title:
  Hybrid laptop's accelerometer tilt interpreted as WiFi hardware switch

Status in compiz package in Ubuntu:
  Invalid
Status in gnome-session package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New
Status in urfkill package in Ubuntu:
  New

Bug description:
  This bug appears to be a regression in Vivid sometime in the second
  half of March 2015.

  When the machine is tilted (e.g., onto its side), Syslog reports an
  unknown button being pressed. When tilted back to the normal laptop
  position, the machine's WiFi disconnects and is shown as disabled in
  the connection manager. Syslog indicates that urfkill registered a
  hardware switch cutoff for the WiFi.

  I know that the accelerometers do work in other contexts and can be
  read properly in Ubuntu. As an example, this orient script works for
  me: https://github.com/leszakk/orient .

  Hardware: HP Envy x360 15t -- this is a hybrid touch notebook
  OS: Ubuntu 15.04 Beta 2 -- Desktop version
  Kernel:  3.19.0-10-generic
  urfkill:
    Installed: 0.6.0~20150318.103828.5539c0d.1-0ubuntu1
    Candidate: 0.6.0~20150318.103828.5539c0d.1-0ubuntu1
    Version table:
   *** 0.6.0~20150318.103828.5539c0d.1-0ubuntu1 0
  500 http://mirrors.mit.edu/ubuntu/ vivid/universe amd64 Packages
  100 /var/lib/dpkg/status

  Below is a Syslog readout from a test event. The notebook starts in
  normal typing position, the hinge bent at a right angle. At 16:13:30,
  without moving the hinge, I tip the notebook 90 degrees to the left
  from my perspective. So the Unity launcher is now closest to the
  floor, for example. I hold it there for about 10 seconds until
  16:13:40.

  Mar 30 16:13:30 [my_hostname] kernel: [ 1327.717086] atkbd serio0: Unknown 
key pressed (translated set 2, code 0xd8 on isa0060/serio0).
  Mar 30 16:13:30 [my_hostname] kernel: [ 1327.717098] atkbd serio0: Use 
'setkeycodes e058 keycode' to make it known.
  Mar 30 16:13:30 [my_hostname] kernel: [ 1327.724168] atkbd serio0: Unknown 
key released (translated set 2, code 0xd8 on isa0060/serio0).
  Mar 30 16:13:30 [my_hostname] kernel: [ 1327.724180] atkbd serio0: Use 
'setkeycodes e058 keycode' to make it known.
  Mar 30 16:13:41 [my_hostname] URfkill[868]: Setting WLAN devices to blocked
  Mar 30 16:13:41 [my_hostname] URfkill[868]: set_soft: Setting WLAN to blocked
  Mar 30 16:13:41 [my_hostname] kernel: [ 1338.698934] wlan0: deauthenticating 
from [ma:ca:dd:re:ss] by local choice (Reason: 3=DEAUTH_LEAVING)
  Mar 30 16:13:41 [my_hostname] wpa_supplicant[1015]: wlan0: 
CTRL-EVENT-DISCONNECTED bssid=[ma:ca:dd:re:ss] reason=3 locally_generated=1
  Mar 30 16:13:41 [my_hostname] kernel: [ 1338.710906] cfg80211: Calling CRDA 
to update world regulatory domain
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Interface wlan0.IPv6 no 
longer relevant for mDNS.
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Leaving mDNS multicast group 
on interface wlan0.IPv6 with address fe80::8286:f2ff:fe32:def8.
  Mar 30 16:13:41 [my_hostname] dhclient: receive_packet failed on wlan0: 
Network is down
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Interface wlan0.IPv4 no 
longer relevant for mDNS.
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Leaving mDNS multicast group 
on interface wlan0.IPv4 with address 192.168.1.133.
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Withdrawing address record 
for fe80::8286:f2ff:fe32:def8 on wlan0.
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Withdrawing address record 
for 192.168.1.133 on wlan0.
  Mar 30 16:13:41 [my_hostname] URfkill[868]: device_changed_cb: phy0
  Mar 30 16:13:41 [my_hostname] NetworkManager[863]: warn Connection 
disconnected (reason -3)
  Mar 30 16:13:41 [my_hostname] NetworkManager[863]: error 
[1427746421.849186] [platform/nm-linux-platform.c:1714] add_object(): Netlink 
error adding 0.0.0.0/0 via 192.168.1.1 dev wlan0 metric 1024 mss 0 src user: 
Unspecific failure
  Mar 30 16:13:41 [my_hostname] NetworkManager[863]: error 
[1427746421.849417] [platform/nm-linux-platform.c:1714] add_object(): Netlink 
error adding 192.168.1.1/32 via 0.0.0.0 dev wlan0 metric 1024 mss 0 src user: 
Unspecific failure
  Mar 30 16:13:41 [my_hostname] NetworkManager[863]: error 
[1427746421.849591] [platform/nm-linux-platform.c:1714] add_object(): Netlink 
error adding 0.0.0.0/0 via 192.168.1.1 dev wlan0 metric 1024 mss 0 src user: 
Unspecific failure
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Joining mDNS multicast group 
on interface wlan0.IPv4 with address 192.168.1.133.
  Mar 30 16:13:41 [my_hostname] NetworkManager[863]: error 
[1427746421.849679] [nm-policy.c:693] update_ip4_routing(): Failed to set 
default 

[Touch-packages] [Bug 1438422] Re: Hybrid laptop's accelerometer tilt interpreted as WiFi hardware switch

[Adam Colligan]

Update: this bug also appears if the screen is held level in a normal,
vertical position and the keyboard hinge is rotated around it. If I
swing the keyboard under and around the screen into tablet mode, then
swing it back into laptop mode, WiFi is disabled and has to be manually
re-enabled via Network Manager.

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

Title:
  Hybrid laptop's accelerometer tilt interpreted as WiFi hardware switch

Status in compiz package in Ubuntu:
  Invalid
Status in gnome-session package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New
Status in urfkill package in Ubuntu:
  New

Bug description:
  This bug appears to be a regression in Vivid sometime in the second
  half of March 2015.

  When the machine is tilted (e.g., onto its side), Syslog reports an
  unknown button being pressed. When tilted back to the normal laptop
  position, the machine's WiFi disconnects and is shown as disabled in
  the connection manager. Syslog indicates that urfkill registered a
  hardware switch cutoff for the WiFi.

  I know that the accelerometers do work in other contexts and can be
  read properly in Ubuntu. As an example, this orient script works for
  me: https://github.com/leszakk/orient .

  Hardware: HP Envy x360 15t -- this is a hybrid touch notebook
  OS: Ubuntu 15.04 Beta 2 -- Desktop version
  Kernel:  3.19.0-10-generic
  urfkill:
    Installed: 0.6.0~20150318.103828.5539c0d.1-0ubuntu1
    Candidate: 0.6.0~20150318.103828.5539c0d.1-0ubuntu1
    Version table:
   *** 0.6.0~20150318.103828.5539c0d.1-0ubuntu1 0
  500 http://mirrors.mit.edu/ubuntu/ vivid/universe amd64 Packages
  100 /var/lib/dpkg/status

  Below is a Syslog readout from a test event. The notebook starts in
  normal typing position, the hinge bent at a right angle. At 16:13:30,
  without moving the hinge, I tip the notebook 90 degrees to the left
  from my perspective. So the Unity launcher is now closest to the
  floor, for example. I hold it there for about 10 seconds until
  16:13:40.

  Mar 30 16:13:30 [my_hostname] kernel: [ 1327.717086] atkbd serio0: Unknown 
key pressed (translated set 2, code 0xd8 on isa0060/serio0).
  Mar 30 16:13:30 [my_hostname] kernel: [ 1327.717098] atkbd serio0: Use 
'setkeycodes e058 keycode' to make it known.
  Mar 30 16:13:30 [my_hostname] kernel: [ 1327.724168] atkbd serio0: Unknown 
key released (translated set 2, code 0xd8 on isa0060/serio0).
  Mar 30 16:13:30 [my_hostname] kernel: [ 1327.724180] atkbd serio0: Use 
'setkeycodes e058 keycode' to make it known.
  Mar 30 16:13:41 [my_hostname] URfkill[868]: Setting WLAN devices to blocked
  Mar 30 16:13:41 [my_hostname] URfkill[868]: set_soft: Setting WLAN to blocked
  Mar 30 16:13:41 [my_hostname] kernel: [ 1338.698934] wlan0: deauthenticating 
from [ma:ca:dd:re:ss] by local choice (Reason: 3=DEAUTH_LEAVING)
  Mar 30 16:13:41 [my_hostname] wpa_supplicant[1015]: wlan0: 
CTRL-EVENT-DISCONNECTED bssid=[ma:ca:dd:re:ss] reason=3 locally_generated=1
  Mar 30 16:13:41 [my_hostname] kernel: [ 1338.710906] cfg80211: Calling CRDA 
to update world regulatory domain
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Interface wlan0.IPv6 no 
longer relevant for mDNS.
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Leaving mDNS multicast group 
on interface wlan0.IPv6 with address fe80::8286:f2ff:fe32:def8.
  Mar 30 16:13:41 [my_hostname] dhclient: receive_packet failed on wlan0: 
Network is down
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Interface wlan0.IPv4 no 
longer relevant for mDNS.
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Leaving mDNS multicast group 
on interface wlan0.IPv4 with address 192.168.1.133.
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Withdrawing address record 
for fe80::8286:f2ff:fe32:def8 on wlan0.
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Withdrawing address record 
for 192.168.1.133 on wlan0.
  Mar 30 16:13:41 [my_hostname] URfkill[868]: device_changed_cb: phy0
  Mar 30 16:13:41 [my_hostname] NetworkManager[863]: warn Connection 
disconnected (reason -3)
  Mar 30 16:13:41 [my_hostname] NetworkManager[863]: error 
[1427746421.849186] [platform/nm-linux-platform.c:1714] add_object(): Netlink 
error adding 0.0.0.0/0 via 192.168.1.1 dev wlan0 metric 1024 mss 0 src user: 
Unspecific failure
  Mar 30 16:13:41 [my_hostname] NetworkManager[863]: error 
[1427746421.849417] [platform/nm-linux-platform.c:1714] add_object(): Netlink 
error adding 192.168.1.1/32 via 0.0.0.0 dev wlan0 metric 1024 mss 0 src user: 
Unspecific failure
  Mar 30 16:13:41 [my_hostname] NetworkManager[863]: error 
[1427746421.849591] [platform/nm-linux-platform.c:1714] add_object(): Netlink 
error adding 0.0.0.0/0 via 192.168.1.1 dev wlan0 metric 1024 mss 0 src user: 
Unspecific failure
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Joining mDNS 

[Touch-packages] [Bug 1438422] Re: Hybrid laptop's accelerometer tilt interpreted as WiFi hardware switch

[Adam Colligan]

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

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

Title:
  Hybrid laptop's accelerometer tilt interpreted as WiFi hardware switch

Status in compiz package in Ubuntu:
  New
Status in gnome-session package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New
Status in urfkill package in Ubuntu:
  New

Bug description:
  This bug appears to be a regression in Vivid sometime in the second
  half of March 2015.

  When the machine is tilted (e.g., onto its side), Syslog reports an
  unknown button being pressed. When tilted back to the normal laptop
  position, the machine's WiFi disconnects and is shown as disabled in
  the connection manager. Syslog indicates that urfkill registered a
  hardware switch cutoff for the WiFi.

  I know that the accelerometers do work in other contexts and can be
  read properly in Ubuntu. As an example, this orient script works for
  me: https://github.com/leszakk/orient .

  Hardware: HP Envy x360 15t -- this is a hybrid touch notebook
  OS: Ubuntu 15.04 Beta 2 -- Desktop version
  Kernel:  3.19.0-10-generic
  urfkill:
    Installed: 0.6.0~20150318.103828.5539c0d.1-0ubuntu1
    Candidate: 0.6.0~20150318.103828.5539c0d.1-0ubuntu1
    Version table:
   *** 0.6.0~20150318.103828.5539c0d.1-0ubuntu1 0
  500 http://mirrors.mit.edu/ubuntu/ vivid/universe amd64 Packages
  100 /var/lib/dpkg/status

  Below is a Syslog readout from a test event. The notebook starts in
  normal typing position, the hinge bent at a right angle. At 16:13:30,
  without moving the hinge, I tip the notebook 90 degrees to the left
  from my perspective. So the Unity launcher is now closest to the
  floor, for example. I hold it there for about 10 seconds until
  16:13:40.

  Mar 30 16:13:30 [my_hostname] kernel: [ 1327.717086] atkbd serio0: Unknown 
key pressed (translated set 2, code 0xd8 on isa0060/serio0).
  Mar 30 16:13:30 [my_hostname] kernel: [ 1327.717098] atkbd serio0: Use 
'setkeycodes e058 keycode' to make it known.
  Mar 30 16:13:30 [my_hostname] kernel: [ 1327.724168] atkbd serio0: Unknown 
key released (translated set 2, code 0xd8 on isa0060/serio0).
  Mar 30 16:13:30 [my_hostname] kernel: [ 1327.724180] atkbd serio0: Use 
'setkeycodes e058 keycode' to make it known.
  Mar 30 16:13:41 [my_hostname] URfkill[868]: Setting WLAN devices to blocked
  Mar 30 16:13:41 [my_hostname] URfkill[868]: set_soft: Setting WLAN to blocked
  Mar 30 16:13:41 [my_hostname] kernel: [ 1338.698934] wlan0: deauthenticating 
from [ma:ca:dd:re:ss] by local choice (Reason: 3=DEAUTH_LEAVING)
  Mar 30 16:13:41 [my_hostname] wpa_supplicant[1015]: wlan0: 
CTRL-EVENT-DISCONNECTED bssid=[ma:ca:dd:re:ss] reason=3 locally_generated=1
  Mar 30 16:13:41 [my_hostname] kernel: [ 1338.710906] cfg80211: Calling CRDA 
to update world regulatory domain
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Interface wlan0.IPv6 no 
longer relevant for mDNS.
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Leaving mDNS multicast group 
on interface wlan0.IPv6 with address fe80::8286:f2ff:fe32:def8.
  Mar 30 16:13:41 [my_hostname] dhclient: receive_packet failed on wlan0: 
Network is down
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Interface wlan0.IPv4 no 
longer relevant for mDNS.
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Leaving mDNS multicast group 
on interface wlan0.IPv4 with address 192.168.1.133.
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Withdrawing address record 
for fe80::8286:f2ff:fe32:def8 on wlan0.
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Withdrawing address record 
for 192.168.1.133 on wlan0.
  Mar 30 16:13:41 [my_hostname] URfkill[868]: device_changed_cb: phy0
  Mar 30 16:13:41 [my_hostname] NetworkManager[863]: warn Connection 
disconnected (reason -3)
  Mar 30 16:13:41 [my_hostname] NetworkManager[863]: error 
[1427746421.849186] [platform/nm-linux-platform.c:1714] add_object(): Netlink 
error adding 0.0.0.0/0 via 192.168.1.1 dev wlan0 metric 1024 mss 0 src user: 
Unspecific failure
  Mar 30 16:13:41 [my_hostname] NetworkManager[863]: error 
[1427746421.849417] [platform/nm-linux-platform.c:1714] add_object(): Netlink 
error adding 192.168.1.1/32 via 0.0.0.0 dev wlan0 metric 1024 mss 0 src user: 
Unspecific failure
  Mar 30 16:13:41 [my_hostname] NetworkManager[863]: error 
[1427746421.849591] [platform/nm-linux-platform.c:1714] add_object(): Netlink 
error adding 0.0.0.0/0 via 192.168.1.1 dev wlan0 metric 1024 mss 0 src user: 
Unspecific failure
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Joining mDNS multicast group 
on interface wlan0.IPv4 with address 192.168.1.133.
  Mar 30 16:13:41 [my_hostname] NetworkManager[863]: error 
[1427746421.849679] [nm-policy.c:693] update_ip4_routing(): Failed to set 
default route.
  Mar 30 16:13:41 

[Touch-packages] [Bug 1438422] Re: Hybrid laptop's accelerometer tilt interpreted as WiFi hardware switch

[Adam Colligan]

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

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

Title:
  Hybrid laptop's accelerometer tilt interpreted as WiFi hardware switch

Status in gnome-session package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  New
Status in urfkill package in Ubuntu:
  New

Bug description:
  This bug appears to be a regression in Vivid sometime in the second
  half of March 2015.

  When the machine is tilted (e.g., onto its side), Syslog reports an
  unknown button being pressed. When tilted back to the normal laptop
  position, the machine's WiFi disconnects and is shown as disabled in
  the connection manager. Syslog indicates that urfkill registered a
  hardware switch cutoff for the WiFi.

  I know that the accelerometers do work in other contexts and can be
  read properly in Ubuntu. As an example, this orient script works for
  me: https://github.com/leszakk/orient .

  Hardware: HP Envy x360 15t -- this is a hybrid touch notebook
  OS: Ubuntu 15.04 Beta 2 -- Desktop version
  Kernel:  3.19.0-10-generic
  urfkill:
    Installed: 0.6.0~20150318.103828.5539c0d.1-0ubuntu1
    Candidate: 0.6.0~20150318.103828.5539c0d.1-0ubuntu1
    Version table:
   *** 0.6.0~20150318.103828.5539c0d.1-0ubuntu1 0
  500 http://mirrors.mit.edu/ubuntu/ vivid/universe amd64 Packages
  100 /var/lib/dpkg/status

  Below is a Syslog readout from a test event. The notebook starts in
  normal typing position, the hinge bent at a right angle. At 16:13:30,
  without moving the hinge, I tip the notebook 90 degrees to the left
  from my perspective. So the Unity launcher is now closest to the
  floor, for example. I hold it there for about 10 seconds until
  16:13:40.

  Mar 30 16:13:30 [my_hostname] kernel: [ 1327.717086] atkbd serio0: Unknown 
key pressed (translated set 2, code 0xd8 on isa0060/serio0).
  Mar 30 16:13:30 [my_hostname] kernel: [ 1327.717098] atkbd serio0: Use 
'setkeycodes e058 keycode' to make it known.
  Mar 30 16:13:30 [my_hostname] kernel: [ 1327.724168] atkbd serio0: Unknown 
key released (translated set 2, code 0xd8 on isa0060/serio0).
  Mar 30 16:13:30 [my_hostname] kernel: [ 1327.724180] atkbd serio0: Use 
'setkeycodes e058 keycode' to make it known.
  Mar 30 16:13:41 [my_hostname] URfkill[868]: Setting WLAN devices to blocked
  Mar 30 16:13:41 [my_hostname] URfkill[868]: set_soft: Setting WLAN to blocked
  Mar 30 16:13:41 [my_hostname] kernel: [ 1338.698934] wlan0: deauthenticating 
from [ma:ca:dd:re:ss] by local choice (Reason: 3=DEAUTH_LEAVING)
  Mar 30 16:13:41 [my_hostname] wpa_supplicant[1015]: wlan0: 
CTRL-EVENT-DISCONNECTED bssid=[ma:ca:dd:re:ss] reason=3 locally_generated=1
  Mar 30 16:13:41 [my_hostname] kernel: [ 1338.710906] cfg80211: Calling CRDA 
to update world regulatory domain
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Interface wlan0.IPv6 no 
longer relevant for mDNS.
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Leaving mDNS multicast group 
on interface wlan0.IPv6 with address fe80::8286:f2ff:fe32:def8.
  Mar 30 16:13:41 [my_hostname] dhclient: receive_packet failed on wlan0: 
Network is down
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Interface wlan0.IPv4 no 
longer relevant for mDNS.
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Leaving mDNS multicast group 
on interface wlan0.IPv4 with address 192.168.1.133.
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Withdrawing address record 
for fe80::8286:f2ff:fe32:def8 on wlan0.
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Withdrawing address record 
for 192.168.1.133 on wlan0.
  Mar 30 16:13:41 [my_hostname] URfkill[868]: device_changed_cb: phy0
  Mar 30 16:13:41 [my_hostname] NetworkManager[863]: warn Connection 
disconnected (reason -3)
  Mar 30 16:13:41 [my_hostname] NetworkManager[863]: error 
[1427746421.849186] [platform/nm-linux-platform.c:1714] add_object(): Netlink 
error adding 0.0.0.0/0 via 192.168.1.1 dev wlan0 metric 1024 mss 0 src user: 
Unspecific failure
  Mar 30 16:13:41 [my_hostname] NetworkManager[863]: error 
[1427746421.849417] [platform/nm-linux-platform.c:1714] add_object(): Netlink 
error adding 192.168.1.1/32 via 0.0.0.0 dev wlan0 metric 1024 mss 0 src user: 
Unspecific failure
  Mar 30 16:13:41 [my_hostname] NetworkManager[863]: error 
[1427746421.849591] [platform/nm-linux-platform.c:1714] add_object(): Netlink 
error adding 0.0.0.0/0 via 192.168.1.1 dev wlan0 metric 1024 mss 0 src user: 
Unspecific failure
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Joining mDNS multicast group 
on interface wlan0.IPv4 with address 192.168.1.133.
  Mar 30 16:13:41 [my_hostname] NetworkManager[863]: error 
[1427746421.849679] [nm-policy.c:693] update_ip4_routing(): Failed to set 
default route.
  Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: New 

[Touch-packages] [Bug 1438422] [NEW] Hybrid laptop's accelerometer tilt interpreted as WiFi hardware switch

[Adam Colligan]

Public bug reported:

This bug appears to be a regression in Vivid sometime in the second half
of March 2015.

When the machine is tilted (e.g., onto its side), Syslog reports an
unknown button being pressed. When tilted back to the normal laptop
position, the machine's WiFi disconnects and is shown as disabled in the
connection manager. Syslog indicates that urfkill registered a hardware
switch cutoff for the WiFi.

I know that the accelerometers do work in other contexts and can be read
properly in Ubuntu. As an example, this orient script works for me:
https://github.com/leszakk/orient .

Hardware: HP Envy x360 15t -- this is a hybrid touch notebook
OS: Ubuntu 15.04 Beta 2 -- Desktop version
Kernel:  3.19.0-10-generic
urfkill:
  Installed: 0.6.0~20150318.103828.5539c0d.1-0ubuntu1
  Candidate: 0.6.0~20150318.103828.5539c0d.1-0ubuntu1
  Version table:
 *** 0.6.0~20150318.103828.5539c0d.1-0ubuntu1 0
500 http://mirrors.mit.edu/ubuntu/ vivid/universe amd64 Packages
100 /var/lib/dpkg/status

Below is a Syslog readout from a test event. The notebook starts in
normal typing position, the hinge bent at a right angle. At 16:13:30,
without moving the hinge, I tip the notebook 90 degrees to the left from
my perspective. So the Unity launcher is now closest to the floor, for
example. I hold it there for about 10 seconds until 16:13:40.

Mar 30 16:13:30 [my_hostname] kernel: [ 1327.717086] atkbd serio0: Unknown key 
pressed (translated set 2, code 0xd8 on isa0060/serio0).
Mar 30 16:13:30 [my_hostname] kernel: [ 1327.717098] atkbd serio0: Use 
'setkeycodes e058 keycode' to make it known.
Mar 30 16:13:30 [my_hostname] kernel: [ 1327.724168] atkbd serio0: Unknown key 
released (translated set 2, code 0xd8 on isa0060/serio0).
Mar 30 16:13:30 [my_hostname] kernel: [ 1327.724180] atkbd serio0: Use 
'setkeycodes e058 keycode' to make it known.
Mar 30 16:13:41 [my_hostname] URfkill[868]: Setting WLAN devices to blocked
Mar 30 16:13:41 [my_hostname] URfkill[868]: set_soft: Setting WLAN to blocked
Mar 30 16:13:41 [my_hostname] kernel: [ 1338.698934] wlan0: deauthenticating 
from [ma:ca:dd:re:ss] by local choice (Reason: 3=DEAUTH_LEAVING)
Mar 30 16:13:41 [my_hostname] wpa_supplicant[1015]: wlan0: 
CTRL-EVENT-DISCONNECTED bssid=[ma:ca:dd:re:ss] reason=3 locally_generated=1
Mar 30 16:13:41 [my_hostname] kernel: [ 1338.710906] cfg80211: Calling CRDA to 
update world regulatory domain
Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Interface wlan0.IPv6 no longer 
relevant for mDNS.
Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Leaving mDNS multicast group 
on interface wlan0.IPv6 with address fe80::8286:f2ff:fe32:def8.
Mar 30 16:13:41 [my_hostname] dhclient: receive_packet failed on wlan0: Network 
is down
Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Interface wlan0.IPv4 no longer 
relevant for mDNS.
Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Leaving mDNS multicast group 
on interface wlan0.IPv4 with address 192.168.1.133.
Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Withdrawing address record for 
fe80::8286:f2ff:fe32:def8 on wlan0.
Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Withdrawing address record for 
192.168.1.133 on wlan0.
Mar 30 16:13:41 [my_hostname] URfkill[868]: device_changed_cb: phy0
Mar 30 16:13:41 [my_hostname] NetworkManager[863]: warn Connection 
disconnected (reason -3)
Mar 30 16:13:41 [my_hostname] NetworkManager[863]: error [1427746421.849186] 
[platform/nm-linux-platform.c:1714] add_object(): Netlink error adding 
0.0.0.0/0 via 192.168.1.1 dev wlan0 metric 1024 mss 0 src user: Unspecific 
failure
Mar 30 16:13:41 [my_hostname] NetworkManager[863]: error [1427746421.849417] 
[platform/nm-linux-platform.c:1714] add_object(): Netlink error adding 
192.168.1.1/32 via 0.0.0.0 dev wlan0 metric 1024 mss 0 src user: Unspecific 
failure
Mar 30 16:13:41 [my_hostname] NetworkManager[863]: error [1427746421.849591] 
[platform/nm-linux-platform.c:1714] add_object(): Netlink error adding 
0.0.0.0/0 via 192.168.1.1 dev wlan0 metric 1024 mss 0 src user: Unspecific 
failure
Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Joining mDNS multicast group 
on interface wlan0.IPv4 with address 192.168.1.133.
Mar 30 16:13:41 [my_hostname] NetworkManager[863]: error [1427746421.849679] 
[nm-policy.c:693] update_ip4_routing(): Failed to set default route.
Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: New relevant interface 
wlan0.IPv4 for mDNS.
Mar 30 16:13:41 [my_hostname] avahi-daemon[876]: Registering new address record 
for 192.168.1.133 on wlan0.IPv4.
Mar 30 16:13:41 [my_hostname] wpa_supplicant[1015]: rfkill: WLAN soft blocked
Mar 30 16:13:41 [my_hostname] NetworkManager[863]: info WiFi now disabled by 
radio killswitch
Mar 30 16:13:41 [my_hostname] NetworkManager[863]: info (wlan0): device state 
change: activated - unavailable (reason 'none') [100 20 0]
Mar 30 16:13:41 [my_hostname] NetworkManager[863]: info (wlan0): deactivating 
device (reason 'none') [0]
Mar 30 16:13:41 

[Touch-packages] [Bug 1416897] Re: static image of desktop and windows displayed instead of lockscreen

[Adam Colligan]

** Description changed:

  This is a follow-on from bug 1375271(
  https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1375271 ), though
  it may actually implicate a different underlying problem.
  
  .
  
  Expectation --
  
  Given any one of the following actions:
   - (from active desktop session) choosing lock from the Unity Panel power 
menu;
   - (from locked session with screen turned off): using mouse movement, 
keystrokes, etc. to poke the screen awake; or
  - (from suspend) initiating a resume,
  
  ...the expected result is to display an interactive lockscreen where the
  active user's password can be entered to access the session. On this
  particular machine, which is a touch hybrid, the lockscreen also
  includes the Onboard soft keyboard.
  
  .
  
  Observed behavior --
  
  Instead of the lockscreen, each of these actions trigger the machine to
  display an image of the desktop/window session as it had been near the
  time of the lock or suspend.  The cursor is visible and can be moved.
  The Unity Panel and Launcher usually appear as normal, although
  sometimes they are missing.
  
  Nothing happens when the user attempts to interact with the visible
  session by mouse or keyboard input.  Keyboard input will actually be fed
  to the lockscreen's password entry window, however.  So blindly typing
  the password from the zombie GUI session image -- and then pressing
  enter -- will bring up an active, working session.
  
  TTY session logins are available by the keyboard shortcuts ctrl-
  alt-F[number].  After pulling up one of these login screens (without
  actually logging in), then returning with ctrl-alt-F7, the lockscreen
  appears as expected.
  
  .
  
  Regression timeframe:
  
  I believe this behavior began sometime during January 2015.
  
  .
  
  Replication:
  
  This unexpected behavior takes place almost every time one of the listed
  actions is taken.  During one period of testing on 2015-01-31, the bug
  disappeared for a few rounds of lock and unlock. However, it re-appeared
  shortly thereafter (I believe after the next restart or suspend-resume).
  
  .
  
  Video attachment:
  
  A 1-minute video (.webm, no audio) is attached showing one form of this
  bug (simple lock-unlock).  The main feed was taken from a smartphone,
  but the video also includes an inset of what SimpleScreenRecorder (SSR)
  saw during the process.
  
  On lock, the actual screen became fully black. SSR, by contrast, recorded a 
black screen that included a clock in the top-right.
  On mouse movement, the actual screen displayed the static image of the 
GUI/desktop session. SSR, by contrast, recorded a delayed but normal lockscreen 
appearing.
  
  .
  
  Security tag reasoning:
  
  This bug displays a snapshot of recent  screen contents from a user's
  GUI session even when the user has (actively or indirectly) locked the
  session.  It also prevents a user from turning on the screen to command
  a user switch, go into TTY, etc. without displaying an image of her
  private GUI session.
  
  .
  
  Current graphics-related system info:
  
  OEM: HP Envy x360 15t (convertible hybrid notebook)
  CPU/GPU: Intel(R) Core(TM) i7-4510U CPU @ 2.00GHz | Intel HD Graphics 4400
  OpenGL Core Profile version: 3.3 Mesa 10.5.0-devel
  OpenGL Extensions version: 3.0 Mesa 10.5.0-devel
  OS: Ubuntu 14.10 64-bit
  Kernel: 3.16.0-29 generic
  X Server: xorg-server 2:1.16.1.901-1ubuntu1~utopic1
- pixman version: 0.32.4
+ Pixman version: 0.32.4
+ Compiz version: 0.9.12
  
  Please let me know if there is further config information that would be
  helpful.
  
  .
  
  Upstream testing:
  
  This is a production machine. I am willing to test pre-release packages
  provided the testing configurations are easy to revert (such as upstream
  kernels).  I have been burned in the past with broken package systems
  and protracted  config repairs after testing experimental graphics and
  video driver software. But I would still be willing give it a shot if
  there is a simple and reliable process to roll back the changes.

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

Title:
  static image of desktop and windows displayed instead of lockscreen

Status in unity package in Ubuntu:
  New

Bug description:
  This is a follow-on from bug 1375271(
  https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1375271 ), though
  it may actually implicate a different underlying problem.

  .

  Expectation --

  Given any one of the following actions:
   - (from active desktop session) choosing lock from the Unity Panel power 
menu;
   - (from locked session with screen turned off): using mouse movement, 
keystrokes, etc. to poke the screen awake; or
  - (from suspend) initiating a resume,

  ...the expected result is to display an interactive lockscreen where
  the active user's password can be entered to 

[Touch-packages] [Bug 1375271] Re: desktop or other past screen contents visible before lockscreen on resume

[Adam Colligan]

Okay, new bug filed: bug #1416897 (
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1416897 ).

That report includes a more in-depth description.

There is also a 1-minute video of the bug in action (
https://launchpadlibrarian.net/196338738/lockscreen_bug_no_audio_20150201.webm
). It gives a synced, side-by-side comparison of what the user sees
(cameraphone) versus what the OS thinks is being displayed
(SimpleScreenRecorder).

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

Title:
  desktop or other past screen contents visible before lockscreen on
  resume

Status in GNOME Screensaver:
  Invalid
Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  On resume from suspend, screen contents are displayed for a brief time
  (perhaps 0.5 to 1 sec)  before the lock dialog appears.

  These screen contents are not always the desktop or open application
  beneath the lock screen. On at least one occasion, the screen showed
  content from a full-screen video that had been playing in Firefox some
  time before the computer had been suspended: neither the video nor its
  underlying tab were open anymore, so the image(s) was likely part of a
  buffer somewhere. (Needless to say, if the wrong full-screen video had
  been watched, depending on the setting, this could be a quite serious
  issue for some users).

  [Test Case]

  Suspend and resume the computer (closing the lid or using the session
  indicator).  Since this problem involves a race condition, it is not
  reliably reproducable at will.

  [Regression Potential]

  This fix unmaps windows when a suspend or shutdown event occurs:  it
  is possible that the window(s) do not get remapped when a wake event
  occurs, or the wake even does not get propagated.  This does not
  appear to occur in practice.

  [Other Info]

  The Ubuntu 14.04 LTS SRU was cherry-picked from upstream Unity where
  it has been released in the Ubuntu Vivid Vervet development release
  for a couple of months with no apparent regressions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-screensaver/+bug/1375271/+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 1416897] [NEW] static image of desktop and windows displayed instead of lockscreen

[Adam Colligan]

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

Public security bug reported:

This is a follow-on from bug 1375271(
https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1375271 ), though
it may actually implicate a different underlying problem.

.

Expectation --

Given any one of the following actions:
 - (from active desktop session) choosing lock from the Unity Panel power 
menu;
 - (from locked session with screen turned off): using mouse movement, 
keystrokes, etc. to poke the screen awake; or
- (from suspend) initiating a resume,

...the expected result is to display an interactive lockscreen where the
active user's password can be entered to access the session. On this
particular machine, which is a touch hybrid, the lockscreen also
includes the Onboard soft keyboard.

.

Observed behavior --

Instead of the lockscreen, each of these actions trigger the machine to
display an image of the desktop/window session as it had been near the
time of the lock or suspend.  The cursor is visible and can be moved.
The Unity Panel and Launcher usually appear as normal, although
sometimes they are missing.

Nothing happens when the user attempts to interact with the visible
session by mouse or keyboard input.  Keyboard input will actually be fed
to the lockscreen's password entry window, however.  So blindly typing
the password from the zombie GUI session image -- and then pressing
enter -- will bring up an active, working session.

TTY session logins are available by the keyboard shortcuts ctrl-
alt-F[number].  After pulling up one of these login screens (without
actually logging in), then returning with ctrl-alt-F7, the lockscreen
appears as expected.

.

Regression timeframe:

I believe this behavior began sometime during January 2015.

.

Replication:

This unexpected behavior takes place almost every time one of the listed
actions is taken.  During one period of testing on 2015-01-31, the bug
disappeared for a few rounds of lock and unlock. However, it re-appeared
shortly thereafter (I believe after the next restart or suspend-resume).

.

Video attachment:

A 1-minute video (.webm, no audio) is attached showing one form of this
bug (simple lock-unlock).  The main feed was taken from a smartphone,
but the video also includes an inset of what SimpleScreenRecorder (SSR)
saw during the process.

On lock, the actual screen became fully black. SSR, by contrast, recorded a 
black screen that included a clock in the top-right.
On mouse movement, the actual screen displayed the static image of the 
GUI/desktop session. SSR, by contrast, recorded a delayed but normal lockscreen 
appearing.

.

Security tag reasoning:

This bug displays a snapshot of recent  screen contents from a user's
GUI session even when the user has (actively or indirectly) locked the
session.  It also prevents a user from turning on the screen to command
a user switch, go into TTY, etc. without displaying an image of her
private GUI session.

.

Current graphics-related system info:

OEM: HP Envy x360 15t (convertible hybrid notebook)
CPU/GPU: Intel(R) Core(TM) i7-4510U CPU @ 2.00GHz | Intel HD Graphics 4400
OpenGL Core Profile version: 3.3 Mesa 10.5.0-devel
OpenGL Extensions version: 3.0 Mesa 10.5.0-devel
OS: Ubuntu 14.10 64-bit
Kernel: 3.16.0-29 generic
X Server: xorg-server 2:1.16.1.901-1ubuntu1~utopic1
pixman version: 0.32.4

Please let me know if there is further config information that would be
helpful.

.

Upstream testing:

This is a production machine. I am willing to test pre-release packages
provided the testing configurations are easy to revert (such as upstream
kernels).  I have been burned in the past with broken package systems
and protracted  config repairs after testing experimental graphics and
video driver software. But I would still be willing give it a shot if
there is a simple and reliable process to roll back the changes.

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


** Tags: amd64 lockscreen screensaver utopic

** Attachment added: (no audio) -- user experience of lockscreen bug plus 
contrasting SSR recording of same events
   
https://bugs.launchpad.net/bugs/1416897/+attachment/4309971/+files/lockscreen_bug_no_audio_20150201.webm

** Information type changed from Private Security to Public Security

** Description changed:

  This is a follow-on from bug 1375271(
  https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1375271 ), though
  it may actually implicate a different underlying problem.
  
  Expectation --
  
  Given any one of the following actions:
-  - (from active desktop session) choosing lock from the Unity Panel power 
menu;
-  - (from locked session with screen turned off): using mouse movement, 
keystrokes, etc. to poke the screen awake; or
+  - (from active desktop session) choosing lock from the Unity Panel power 
menu;
+  - (from locked session with screen turned off): using mouse movement, 
keystrokes, etc. to poke the screen awake; or
  - (from suspend) initiating a 

[Touch-packages] [Bug 1416897] Re: static image of desktop and windows displayed instead of lockscreen

[Adam Colligan]

** Description changed:

  This is a follow-on from bug 1375271(
  https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1375271 ), though
  it may actually implicate a different underlying problem.
  
  .
  
  Expectation --
  
  Given any one of the following actions:
   - (from active desktop session) choosing lock from the Unity Panel power 
menu;
   - (from locked session with screen turned off): using mouse movement, 
keystrokes, etc. to poke the screen awake; or
  - (from suspend) initiating a resume,
  
  ...the expected result is to display an interactive lockscreen where the
  active user's password can be entered to access the session. On this
  particular machine, which is a touch hybrid, the lockscreen also
  includes the Onboard soft keyboard.
  
  .
  
  Observed behavior --
  
- Instead of the lockscreen, each of these actions trigger the machine to
+ Instead of the lockscreen, each of these actions triggers the machine to
  display an image of the desktop/window session as it had been near the
  time of the lock or suspend.  The cursor is visible and can be moved.
  The Unity Panel and Launcher usually appear as normal, although
  sometimes they are missing.
  
  Nothing happens when the user attempts to interact with the visible
  session by mouse or keyboard input.  Keyboard input will actually be fed
  to the lockscreen's password entry window, however.  So blindly typing
  the password from the zombie GUI session image -- and then pressing
  enter -- will bring up an active, working session.
  
  TTY session logins are available by the keyboard shortcuts ctrl-
  alt-F[number].  After pulling up one of these login screens (without
  actually logging in), then returning with ctrl-alt-F7, the lockscreen
  appears as expected.
  
  .
  
  Regression timeframe:
  
  I believe this behavior began sometime during January 2015.
  
  .
  
  Replication:
  
  This unexpected behavior takes place almost every time one of the listed
  actions is taken.  During one period of testing on 2015-01-31, the bug
  disappeared for a few rounds of lock and unlock. However, it re-appeared
  shortly thereafter (I believe after the next restart or suspend-resume).
  
  .
  
  Video attachment:
  
  A 1-minute video (.webm, no audio) is attached showing one form of this
  bug (simple lock-unlock).  The main feed was taken from a smartphone,
  but the video also includes an inset of what SimpleScreenRecorder (SSR)
  saw during the process.
  
  On lock, the actual screen became fully black. SSR, by contrast, recorded a 
black screen that included a clock in the top-right.
  On mouse movement, the actual screen displayed the static image of the 
GUI/desktop session. SSR, by contrast, recorded a delayed but normal lockscreen 
appearing.
  
  .
  
  Security tag reasoning:
  
  This bug displays a snapshot of recent  screen contents from a user's
  GUI session even when the user has (actively or indirectly) locked the
  session.  It also prevents a user from turning on the screen to command
  a user switch, go into TTY, etc. without displaying an image of her
  private GUI session.
  
  .
  
  Current graphics-related system info:
  
  OEM: HP Envy x360 15t (convertible hybrid notebook)
  CPU/GPU: Intel(R) Core(TM) i7-4510U CPU @ 2.00GHz | Intel HD Graphics 4400
  OpenGL Core Profile version: 3.3 Mesa 10.5.0-devel
  OpenGL Extensions version: 3.0 Mesa 10.5.0-devel
  OS: Ubuntu 14.10 64-bit
  Kernel: 3.16.0-29 generic
  X Server: xorg-server 2:1.16.1.901-1ubuntu1~utopic1
  Pixman version: 0.32.4
  Compiz version: 0.9.12
  
  Please let me know if there is further config information that would be
  helpful.
  
  .
  
  Upstream testing:
  
  This is a production machine. I am willing to test pre-release packages
  provided the testing configurations are easy to revert (such as upstream
  kernels).  I have been burned in the past with broken package systems
  and protracted  config repairs after testing experimental graphics and
  video driver software. But I would still be willing give it a shot if
  there is a simple and reliable process to roll back the changes.

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

Title:
  static image of desktop and windows displayed instead of lockscreen

Status in unity package in Ubuntu:
  New

Bug description:
  This is a follow-on from bug 1375271(
  https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1375271 ), though
  it may actually implicate a different underlying problem.

  .

  Expectation --

  Given any one of the following actions:
   - (from active desktop session) choosing lock from the Unity Panel power 
menu;
   - (from locked session with screen turned off): using mouse movement, 
keystrokes, etc. to poke the screen awake; or
  - (from suspend) initiating a resume,

  ...the expected result is to display an interactive lockscreen where

[Touch-packages] [Bug 1375271] Re: desktop or other past screen contents visible before lockscreen on resume

[Adam Colligan]

I'll file a new bug report when I have a bit of time and put the link in
a comment here when it's done.

I've realized now that this new bug as I'm seeing it is actually not
contingent on Suspend taking place. If I simply go to menu Lock, I get
a black screen. Moving the mouse or otherwise triggering the unlock
screen instead gives an image of the Desktop with no interaction
possible except moving the cursor. Going to a different TTY and then
back brings up the lock screen.

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

Title:
  desktop or other past screen contents visible before lockscreen on
  resume

Status in GNOME Screensaver:
  Invalid
Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  On resume from suspend, screen contents are displayed for a brief time
  (perhaps 0.5 to 1 sec)  before the lock dialog appears.

  These screen contents are not always the desktop or open application
  beneath the lock screen. On at least one occasion, the screen showed
  content from a full-screen video that had been playing in Firefox some
  time before the computer had been suspended: neither the video nor its
  underlying tab were open anymore, so the image(s) was likely part of a
  buffer somewhere. (Needless to say, if the wrong full-screen video had
  been watched, depending on the setting, this could be a quite serious
  issue for some users).

  [Test Case]

  Suspend and resume the computer (closing the lid or using the session
  indicator).  Since this problem involves a race condition, it is not
  reliably reproducable at will.

  [Regression Potential]

  This fix unmaps windows when a suspend or shutdown event occurs:  it
  is possible that the window(s) do not get remapped when a wake event
  occurs, or the wake even does not get propagated.  This does not
  appear to occur in practice.

  [Other Info]

  The Ubuntu 14.04 LTS SRU was cherry-picked from upstream Unity where
  it has been released in the Ubuntu Vivid Vervet development release
  for a couple of months with no apparent regressions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-screensaver/+bug/1375271/+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 1375271] Re: desktop or other past screen contents visible before lockscreen on resume

[Adam Colligan]

A form of this regression has now returned with a vengeance; I'm not
sure whether to make it into a new bug report or simply to re-open this
one, though.

For the past couple of days, resume-from-suspend behavior has frequently
been this:

- the lock screen appears at first to have been completely bypassed, and
the session appears restored on wakeup

- the cursor is visible on the screen and moves, but the mouse and
keyboard cannot actually interact with any objects on the screen

- using ctrl-alt-F(x) to raise a new terminal, then using ctrl-alt-F7 to
return to the x session, bringis back the lock screen. Actually logging
in to the other session is not necessary, and everything proceeds
normally once the lockscreen is brought up.

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

Title:
  desktop or other past screen contents visible before lockscreen on
  resume

Status in GNOME Screensaver:
  New
Status in Unity:
  Fix Committed
Status in Unity 7.2 series:
  In Progress
Status in unity package in Ubuntu:
  Fix Released
Status in unity source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

  On resume from suspend, screen contents are displayed for a brief time
  (perhaps 0.5 to 1 sec)  before the lock dialog appears.

  These screen contents are not always the desktop or open application
  beneath the lock screen. On at least one occasion, the screen showed
  content from a full-screen video that had been playing in Firefox some
  time before the computer had been suspended: neither the video nor its
  underlying tab were open anymore, so the image(s) was likely part of a
  buffer somewhere. (Needless to say, if the wrong full-screen video had
  been watched, depending on the setting, this could be a quite serious
  issue for some users).

  [Test Case]

  Suspend and resume the computer (closing the lid or using the session
  indicator).  Since this problem involves a race condition, it is not
  reliably reproducable at will.

  [Regression Potential]

  This fix unmaps windows when a suspend or shutdown event occurs:  it
  is possible that the window(s) do not get remapped when a wake event
  occurs, or the wake even does not get propagated.  This does not
  appear to occur in practice.

  [Other Info]

  The Ubuntu 14.04 LTS SRU was cherry-picked from upstream Unity where
  it has been released in the Ubuntu Vivid Vervet development release
  for a couple of months with no apparent regressions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-screensaver/+bug/1375271/+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 1415039] Re: laptop unresponsive after suspend

[Adam Colligan]

You can also check /var/log/syslog , which often has more in-depth
details about what happened during a suspend.

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

Title:
  laptop unresponsive after suspend

Status in pm-utils package in Ubuntu:
  New

Bug description:
  After suspend, the system becomes unresponsive. Fan keeps running,
  full reboot needed.

  In /var/log/pm-suspend.log the only error is:

  Failed to connect to non-global ctrl_ifname: (null)  error: No such
  file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pm-utils 1.4.1-13ubuntu0.1
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jan 27 14:40:12 2015
  InstallationDate: Installed on 2015-01-26 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1415039/+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 1415039] Re: laptop unresponsive after suspend

[Adam Colligan]

Can you try something for me? I'm wondering whether you're getting the
same thing I reported here that may be a part of another, earlier bug
(https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1375271/comments/8).

When you resume from suspend and find the system non-responsive, press
ctrl-alt-f1. If you get a text login screen, don't do anything on it,
but press ctrl-alt F7.  This should bring you back to the visual
session. Do you then get an unlock screen or a working desktop? If so,
it's probably the same issue I'm having (waiting to see if it should be
a new bug or a continuation of that old one).  If not, let me know
anyway just so I can cross it off the list.

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

Title:
  laptop unresponsive after suspend

Status in pm-utils package in Ubuntu:
  New

Bug description:
  After suspend, the system becomes unresponsive. Fan keeps running,
  full reboot needed.

  In /var/log/pm-suspend.log the only error is:

  Failed to connect to non-global ctrl_ifname: (null)  error: No such
  file or directory

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pm-utils 1.4.1-13ubuntu0.1
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jan 27 14:40:12 2015
  InstallationDate: Installed on 2015-01-26 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1415039/+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 1369113] Re: Steam game began crashing 2014-09-12 (cross-post Source bugtracker)

[Adam Colligan]

I'm a little hesitant when it comes to the libxext installation from
Vivid; is there some way to figure out if this is going to break my
package dependencies?

I'm currently on Edgers.  When I try to install the new libxext6, the
version is higher than the one required by my current libxext-dev.  Now,
I can remove my current libxext-dev, but that would also entail removing
these packages:

libatk-bridge2.0-dev libatspi2.0-dev libcairo2-dev libcanberra-gtk3-dev
libgl1-mesa-dev libglu1-mesa-dev libgtk-3-dev libpango1.0-dev libqt4
-opengl-dev libxcomposite-dev libxext-dev libxi-dev libxinerama-dev
libxrandr-dev libxtst-dev .

My concern is that there might be a cascading problem if I put in the
new libxext6 and libxext-dev from Vivid and then try to reinstall all of
those other packages. I don't want to actually move off of Trusty right
now.

Is there either (1) a more surgical way to get the 1.3.3.1 fix for error
spamming; or (2) a way to check whether my whole package system will be
in tact if I do this big removal and replacement?

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

Title:
  Steam game began crashing 2014-09-12 (cross-post Source bugtracker)

Status in “steam” package in Ubuntu:
  Confirmed
Status in “xorg” package in Ubuntu:
  Confirmed

Bug description:
  I am cross-posting this issue, which I reported to Valve's Source GIT
  issue tracker, because it was suggested that the regression may be due
  to Ubuntu Xorg changes rather than changes on the Steam end.

  Link: https://github.com/ValveSoftware/Source-1-Games/issues/1822


  Symptom --
  DoD:Source loads normally. But after a few minutes of playing (not a specific 
time as far as I can tell), the game freezes in place. A short clip (maybe a 
quarter of a second) of the last audio that played then repeats over and over 
on a loop. The process has to be killed manually with a QUIT or HUP signal for 
good measure. This is a new issue that just arose today.

  I have included system info, kernel log, and output when game is run
  from terminal and crashes.

  X info --
  X.Org X Server 1.16.0
  Release Date: 2014-07-16
  X Protocol Version 11, Revision 0
  Build Operating System: Linux 3.2.0-61-generic x86_64 Ubuntu
  Current Operating System: Linux adam-x360-lin 3.16.0-14-generic #20-Ubuntu 
SMP Sat Sep 6 23:46:49 UTC 2014 x86_64
  Kernel command line: BOOT_IMAGE=/vmlinuz-3.16.0-14-generic.efi.signed 
root=UUID=5ad8035a-f2a4-4334-84d8-e2a8a7396bf8 ro drm.debug=0xe plymouth:debug
  Build Date: 10 September 2014  01:10:01PM
  xorg-server 2:1.16.0-1ubuntu1 (For technical support please see 
http://www.ubuntu.com/support) 
  Current version of pixman: 0.32.4
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.

  
  System --

  OS: Ubuntu 14.10 (latest updates)
  Kernel: 3.16.0-14-generic #20-Ubuntu SMP Sat Sep 6 23:46:49 UTC 2014 x86_64
  Model: HP Envy x360
  lspci:
  00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 0b)
  00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated 
Graphics Controller (rev 0b)
  00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 
0b)
  00:14.0 USB controller: Intel Corporation 8 Series USB xHCI HC (rev 04)
  00:16.0 Communication controller: Intel Corporation 8 Series HECI #0 (rev 04)
  00:1b.0 Audio device: Intel Corporation 8 Series HD Audio Controller (rev 04)
  00:1c.0 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 1 (rev 
e4)
  00:1c.1 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 2 (rev 
e4)
  00:1c.2 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 3 (rev 
e4)
  00:1c.3 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 4 (rev 
e4)
  00:1d.0 USB controller: Intel Corporation 8 Series USB EHCI #1 (rev 04)
  00:1f.0 ISA bridge: Intel Corporation 8 Series LPC Controller (rev 04)
  00:1f.2 SATA controller: Intel Corporation 8 Series SATA Controller 1 AHCI 
mode
  00:1f.3 SMBus: Intel Corporation 8 Series SMBus Controller (rev 04)
  02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5227 PCI 
Express Card Reader (rev 01)
  08:00.0 Network controller: Intel Corporation Wireless 7260 (rev 9b)
  09:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 10)


  Kernel log excerpt (from game start through crash end) --

  Sep 12 19:11:20 kernel: [ 4443.221907] [drm:i915_gem_open]
  Sep 12 19:11:20 kernel: [ 4443.266851] [drm:i915_gem_context_create_ioctl] HW 
context 1 created
  Sep 12 19:11:21 kernel: [ .169675] [drm:i915_gem_context_destroy_ioctl] 
HW context 1 destroyed
  Sep 12 19:11:21 kernel: [ .486704] [drm:i915_gem_open]
  Sep 12 19:11:21 kernel: [ .550210] [drm:i915_gem_context_create_ioctl] HW 
context 1 

[Touch-packages] [Bug 1369113] Re: Steam game began crashing 2014-09-12 (cross-post Source bugtracker)

[Adam Colligan]

I'm a little confused -- are you saing that upgrading libXext should
solve the crash or just the error spamming?

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

Title:
  Steam game began crashing 2014-09-12 (cross-post Source bugtracker)

Status in “steam” package in Ubuntu:
  Confirmed
Status in “xorg” package in Ubuntu:
  Confirmed

Bug description:
  I am cross-posting this issue, which I reported to Valve's Source GIT
  issue tracker, because it was suggested that the regression may be due
  to Ubuntu Xorg changes rather than changes on the Steam end.

  Link: https://github.com/ValveSoftware/Source-1-Games/issues/1822


  Symptom --
  DoD:Source loads normally. But after a few minutes of playing (not a specific 
time as far as I can tell), the game freezes in place. A short clip (maybe a 
quarter of a second) of the last audio that played then repeats over and over 
on a loop. The process has to be killed manually with a QUIT or HUP signal for 
good measure. This is a new issue that just arose today.

  I have included system info, kernel log, and output when game is run
  from terminal and crashes.

  X info --
  X.Org X Server 1.16.0
  Release Date: 2014-07-16
  X Protocol Version 11, Revision 0
  Build Operating System: Linux 3.2.0-61-generic x86_64 Ubuntu
  Current Operating System: Linux adam-x360-lin 3.16.0-14-generic #20-Ubuntu 
SMP Sat Sep 6 23:46:49 UTC 2014 x86_64
  Kernel command line: BOOT_IMAGE=/vmlinuz-3.16.0-14-generic.efi.signed 
root=UUID=5ad8035a-f2a4-4334-84d8-e2a8a7396bf8 ro drm.debug=0xe plymouth:debug
  Build Date: 10 September 2014  01:10:01PM
  xorg-server 2:1.16.0-1ubuntu1 (For technical support please see 
http://www.ubuntu.com/support) 
  Current version of pixman: 0.32.4
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.

  
  System --

  OS: Ubuntu 14.10 (latest updates)
  Kernel: 3.16.0-14-generic #20-Ubuntu SMP Sat Sep 6 23:46:49 UTC 2014 x86_64
  Model: HP Envy x360
  lspci:
  00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 0b)
  00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated 
Graphics Controller (rev 0b)
  00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 
0b)
  00:14.0 USB controller: Intel Corporation 8 Series USB xHCI HC (rev 04)
  00:16.0 Communication controller: Intel Corporation 8 Series HECI #0 (rev 04)
  00:1b.0 Audio device: Intel Corporation 8 Series HD Audio Controller (rev 04)
  00:1c.0 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 1 (rev 
e4)
  00:1c.1 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 2 (rev 
e4)
  00:1c.2 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 3 (rev 
e4)
  00:1c.3 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 4 (rev 
e4)
  00:1d.0 USB controller: Intel Corporation 8 Series USB EHCI #1 (rev 04)
  00:1f.0 ISA bridge: Intel Corporation 8 Series LPC Controller (rev 04)
  00:1f.2 SATA controller: Intel Corporation 8 Series SATA Controller 1 AHCI 
mode
  00:1f.3 SMBus: Intel Corporation 8 Series SMBus Controller (rev 04)
  02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5227 PCI 
Express Card Reader (rev 01)
  08:00.0 Network controller: Intel Corporation Wireless 7260 (rev 9b)
  09:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 10)


  Kernel log excerpt (from game start through crash end) --

  Sep 12 19:11:20 kernel: [ 4443.221907] [drm:i915_gem_open]
  Sep 12 19:11:20 kernel: [ 4443.266851] [drm:i915_gem_context_create_ioctl] HW 
context 1 created
  Sep 12 19:11:21 kernel: [ .169675] [drm:i915_gem_context_destroy_ioctl] 
HW context 1 destroyed
  Sep 12 19:11:21 kernel: [ .486704] [drm:i915_gem_open]
  Sep 12 19:11:21 kernel: [ .550210] [drm:i915_gem_context_create_ioctl] HW 
context 1 created
  Sep 12 19:11:25 kernel: [ 4447.852792] [drm:drm_mode_getconnector] 
[CONNECTOR:14:?]
  Sep 12 19:11:25 kernel: [ 4447.852796] 
[drm:drm_helper_probe_single_connector_modes_merge_bits] [CONNECTOR:14:eDP-1]
  Sep 12 19:11:25 kernel: [ 4447.852800] [drm:intel_dp_detect] 
[CONNECTOR:14:eDP-1]
  Sep 12 19:11:25 kernel: [ 4447.852804] [drm:_edp_panel_vdd_on] Turning eDP 
VDD on
  Sep 12 19:11:25 kernel: [ 4447.852809] [drm:_edp_panel_vdd_on] PP_STATUS: 
0x8008 PP_CONTROL: 0xabcd000f
  Sep 12 19:11:25 kernel: [ 4447.853257] [drm:intel_dp_probe_oui] Sink OUI: 
00e04c
  Sep 12 19:11:25 kernel: [ 4447.853695] [drm:intel_dp_probe_oui] Branch OUI: 
00e04c
  Sep 12 19:11:25 kernel: [ 4447.853708] [drm:drm_edid_to_eld] ELD: no CEA 
Extension found
  Sep 12 19:11:25 kernel: [ 4447.853711] 
[drm:drm_helper_probe_single_connector_modes_merge_bits] [CONNECTOR:14:eDP-1] 
probed modes :
  Sep 12 19:11:25 kernel: [ 4447.853715] 

[Touch-packages] [Bug 1369113] Re: Steam game began crashing 2014-09-12 (cross-post Source bugtracker)

[Adam Colligan]

Is there anything I might be able to do to support work on fixing 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/1369113

Title:
  Steam game began crashing 2014-09-12 (cross-post Source bugtracker)

Status in “steam” package in Ubuntu:
  Confirmed
Status in “xorg” package in Ubuntu:
  Confirmed

Bug description:
  I am cross-posting this issue, which I reported to Valve's Source GIT
  issue tracker, because it was suggested that the regression may be due
  to Ubuntu Xorg changes rather than changes on the Steam end.

  Link: https://github.com/ValveSoftware/Source-1-Games/issues/1822


  Symptom --
  DoD:Source loads normally. But after a few minutes of playing (not a specific 
time as far as I can tell), the game freezes in place. A short clip (maybe a 
quarter of a second) of the last audio that played then repeats over and over 
on a loop. The process has to be killed manually with a QUIT or HUP signal for 
good measure. This is a new issue that just arose today.

  I have included system info, kernel log, and output when game is run
  from terminal and crashes.

  X info --
  X.Org X Server 1.16.0
  Release Date: 2014-07-16
  X Protocol Version 11, Revision 0
  Build Operating System: Linux 3.2.0-61-generic x86_64 Ubuntu
  Current Operating System: Linux adam-x360-lin 3.16.0-14-generic #20-Ubuntu 
SMP Sat Sep 6 23:46:49 UTC 2014 x86_64
  Kernel command line: BOOT_IMAGE=/vmlinuz-3.16.0-14-generic.efi.signed 
root=UUID=5ad8035a-f2a4-4334-84d8-e2a8a7396bf8 ro drm.debug=0xe plymouth:debug
  Build Date: 10 September 2014  01:10:01PM
  xorg-server 2:1.16.0-1ubuntu1 (For technical support please see 
http://www.ubuntu.com/support) 
  Current version of pixman: 0.32.4
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.

  
  System --

  OS: Ubuntu 14.10 (latest updates)
  Kernel: 3.16.0-14-generic #20-Ubuntu SMP Sat Sep 6 23:46:49 UTC 2014 x86_64
  Model: HP Envy x360
  lspci:
  00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 0b)
  00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated 
Graphics Controller (rev 0b)
  00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 
0b)
  00:14.0 USB controller: Intel Corporation 8 Series USB xHCI HC (rev 04)
  00:16.0 Communication controller: Intel Corporation 8 Series HECI #0 (rev 04)
  00:1b.0 Audio device: Intel Corporation 8 Series HD Audio Controller (rev 04)
  00:1c.0 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 1 (rev 
e4)
  00:1c.1 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 2 (rev 
e4)
  00:1c.2 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 3 (rev 
e4)
  00:1c.3 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 4 (rev 
e4)
  00:1d.0 USB controller: Intel Corporation 8 Series USB EHCI #1 (rev 04)
  00:1f.0 ISA bridge: Intel Corporation 8 Series LPC Controller (rev 04)
  00:1f.2 SATA controller: Intel Corporation 8 Series SATA Controller 1 AHCI 
mode
  00:1f.3 SMBus: Intel Corporation 8 Series SMBus Controller (rev 04)
  02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5227 PCI 
Express Card Reader (rev 01)
  08:00.0 Network controller: Intel Corporation Wireless 7260 (rev 9b)
  09:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 10)


  Kernel log excerpt (from game start through crash end) --

  Sep 12 19:11:20 kernel: [ 4443.221907] [drm:i915_gem_open]
  Sep 12 19:11:20 kernel: [ 4443.266851] [drm:i915_gem_context_create_ioctl] HW 
context 1 created
  Sep 12 19:11:21 kernel: [ .169675] [drm:i915_gem_context_destroy_ioctl] 
HW context 1 destroyed
  Sep 12 19:11:21 kernel: [ .486704] [drm:i915_gem_open]
  Sep 12 19:11:21 kernel: [ .550210] [drm:i915_gem_context_create_ioctl] HW 
context 1 created
  Sep 12 19:11:25 kernel: [ 4447.852792] [drm:drm_mode_getconnector] 
[CONNECTOR:14:?]
  Sep 12 19:11:25 kernel: [ 4447.852796] 
[drm:drm_helper_probe_single_connector_modes_merge_bits] [CONNECTOR:14:eDP-1]
  Sep 12 19:11:25 kernel: [ 4447.852800] [drm:intel_dp_detect] 
[CONNECTOR:14:eDP-1]
  Sep 12 19:11:25 kernel: [ 4447.852804] [drm:_edp_panel_vdd_on] Turning eDP 
VDD on
  Sep 12 19:11:25 kernel: [ 4447.852809] [drm:_edp_panel_vdd_on] PP_STATUS: 
0x8008 PP_CONTROL: 0xabcd000f
  Sep 12 19:11:25 kernel: [ 4447.853257] [drm:intel_dp_probe_oui] Sink OUI: 
00e04c
  Sep 12 19:11:25 kernel: [ 4447.853695] [drm:intel_dp_probe_oui] Branch OUI: 
00e04c
  Sep 12 19:11:25 kernel: [ 4447.853708] [drm:drm_edid_to_eld] ELD: no CEA 
Extension found
  Sep 12 19:11:25 kernel: [ 4447.853711] 
[drm:drm_helper_probe_single_connector_modes_merge_bits] [CONNECTOR:14:eDP-1] 
probed modes :
  Sep 12 19:11:25 kernel: [ 4447.853715] [drm:drm_mode_debug_printmodeline] 

[Touch-packages] [Bug 1375271] Re: desktop or other past screen contents visible before lockscreen on resume

[Adam Colligan]

This is stock Ubuntu Unity.  Sorry if the gnome screensaver package was
a wrong one to add -- I had thought that it was used for lockscreen in
unity, and it was involved in the 2011 report.

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

Title:
  desktop or other past screen contents visible before lockscreen on
  resume

Status in Compiz:
  New
Status in GNOME Screensaver:
  New
Status in Unity:
  New
Status in “unity” package in Ubuntu:
  New

Bug description:
  This appears to be a regression in 14.10 sometime in September 2014.

  The behavior appears similar to this bug from 2011:
  https://bugs.launchpad.net/unity-2d/+bug/830348

  On resume from suspend, screen contents are displayed for a brief time
  (perhaps 0.5 to 1 sec)  before the lock dialog appears.

  These screen contents are not always the desktop or open application
  beneath the lock screen. On at least one occasion, the screen showed
  content from a full-screen video that had been playing in Firefox some
  time before the computer had been suspended: neither the video nor its
  underlying tab were open anymore, so the image(s) was likely part of a
  buffer somewhere. (Needless to say, if the wrong full-screen video had
  been watched, depending on the setting, this could be a quite serious
  issue for some users).

  I have not exhaustively tested conditions in which this appears.
  However, just now, the bug did not appear when keeping the lid open,
  suspending, and then resuming with the power button.

  But when suspending from menu, closing the lid, then opening the lid
  and moving the mouse, the screen displayed contents before showing the
  lock dialog.  The image displayed was of the desktop (with this bug
  reporting window) and showed the suspend item in the power menu
  being highlighted/clicked.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity 7.3.1+14.10.20140915-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3
  Uname: Linux 3.16.0-18-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Mon Sep 29 08:38:57 2014
  InstallationDate: Installed on 2014-08-10 (50 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  SourcePackage: unity
  UpgradeStatus: Upgraded to utopic on 2014-08-10 (50 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/1375271/+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 1375271] Re: desktop or other past screen contents visible before lockscreen on resume

[Adam Colligan]

Let me know if there is any specific testing pattern, video recording,
or config information I could provide that might help.

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

Title:
  desktop or other past screen contents visible before lockscreen on
  resume

Status in Compiz:
  New
Status in GNOME Screensaver:
  New
Status in Unity:
  New
Status in “unity” package in Ubuntu:
  New

Bug description:
  This appears to be a regression in 14.10 sometime in September 2014.

  The behavior appears similar to this bug from 2011:
  https://bugs.launchpad.net/unity-2d/+bug/830348

  On resume from suspend, screen contents are displayed for a brief time
  (perhaps 0.5 to 1 sec)  before the lock dialog appears.

  These screen contents are not always the desktop or open application
  beneath the lock screen. On at least one occasion, the screen showed
  content from a full-screen video that had been playing in Firefox some
  time before the computer had been suspended: neither the video nor its
  underlying tab were open anymore, so the image(s) was likely part of a
  buffer somewhere. (Needless to say, if the wrong full-screen video had
  been watched, depending on the setting, this could be a quite serious
  issue for some users).

  I have not exhaustively tested conditions in which this appears.
  However, just now, the bug did not appear when keeping the lid open,
  suspending, and then resuming with the power button.

  But when suspending from menu, closing the lid, then opening the lid
  and moving the mouse, the screen displayed contents before showing the
  lock dialog.  The image displayed was of the desktop (with this bug
  reporting window) and showed the suspend item in the power menu
  being highlighted/clicked.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: unity 7.3.1+14.10.20140915-0ubuntu1
  ProcVersionSignature: Ubuntu 3.16.0-18.25-generic 3.16.3
  Uname: Linux 3.16.0-18-generic x86_64
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Mon Sep 29 08:38:57 2014
  InstallationDate: Installed on 2014-08-10 (50 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS Trusty Tahr - Release amd64 
(20140722.2)
  SourcePackage: unity
  UpgradeStatus: Upgraded to utopic on 2014-08-10 (50 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/1375271/+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 1369113] Re: Steam game began crashing 2014-09-12 (cross-post Source bugtracker)

[Adam Colligan]

Just reconfirming: this problem persists today with the latest updates
to everything. Game is unplayable.

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

Title:
  Steam game began crashing 2014-09-12 (cross-post Source bugtracker)

Status in “steam” package in Ubuntu:
  Confirmed
Status in “xorg” package in Ubuntu:
  Confirmed

Bug description:
  I am cross-posting this issue, which I reported to Valve's Source GIT
  issue tracker, because it was suggested that the regression may be due
  to Ubuntu Xorg changes rather than changes on the Steam end.

  Link: https://github.com/ValveSoftware/Source-1-Games/issues/1822


  Symptom --
  DoD:Source loads normally. But after a few minutes of playing (not a specific 
time as far as I can tell), the game freezes in place. A short clip (maybe a 
quarter of a second) of the last audio that played then repeats over and over 
on a loop. The process has to be killed manually with a QUIT or HUP signal for 
good measure. This is a new issue that just arose today.

  I have included system info, kernel log, and output when game is run
  from terminal and crashes.

  X info --
  X.Org X Server 1.16.0
  Release Date: 2014-07-16
  X Protocol Version 11, Revision 0
  Build Operating System: Linux 3.2.0-61-generic x86_64 Ubuntu
  Current Operating System: Linux adam-x360-lin 3.16.0-14-generic #20-Ubuntu 
SMP Sat Sep 6 23:46:49 UTC 2014 x86_64
  Kernel command line: BOOT_IMAGE=/vmlinuz-3.16.0-14-generic.efi.signed 
root=UUID=5ad8035a-f2a4-4334-84d8-e2a8a7396bf8 ro drm.debug=0xe plymouth:debug
  Build Date: 10 September 2014  01:10:01PM
  xorg-server 2:1.16.0-1ubuntu1 (For technical support please see 
http://www.ubuntu.com/support) 
  Current version of pixman: 0.32.4
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.

  
  System --

  OS: Ubuntu 14.10 (latest updates)
  Kernel: 3.16.0-14-generic #20-Ubuntu SMP Sat Sep 6 23:46:49 UTC 2014 x86_64
  Model: HP Envy x360
  lspci:
  00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 0b)
  00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated 
Graphics Controller (rev 0b)
  00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 
0b)
  00:14.0 USB controller: Intel Corporation 8 Series USB xHCI HC (rev 04)
  00:16.0 Communication controller: Intel Corporation 8 Series HECI #0 (rev 04)
  00:1b.0 Audio device: Intel Corporation 8 Series HD Audio Controller (rev 04)
  00:1c.0 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 1 (rev 
e4)
  00:1c.1 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 2 (rev 
e4)
  00:1c.2 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 3 (rev 
e4)
  00:1c.3 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 4 (rev 
e4)
  00:1d.0 USB controller: Intel Corporation 8 Series USB EHCI #1 (rev 04)
  00:1f.0 ISA bridge: Intel Corporation 8 Series LPC Controller (rev 04)
  00:1f.2 SATA controller: Intel Corporation 8 Series SATA Controller 1 AHCI 
mode
  00:1f.3 SMBus: Intel Corporation 8 Series SMBus Controller (rev 04)
  02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5227 PCI 
Express Card Reader (rev 01)
  08:00.0 Network controller: Intel Corporation Wireless 7260 (rev 9b)
  09:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 10)


  Kernel log excerpt (from game start through crash end) --

  Sep 12 19:11:20 kernel: [ 4443.221907] [drm:i915_gem_open]
  Sep 12 19:11:20 kernel: [ 4443.266851] [drm:i915_gem_context_create_ioctl] HW 
context 1 created
  Sep 12 19:11:21 kernel: [ .169675] [drm:i915_gem_context_destroy_ioctl] 
HW context 1 destroyed
  Sep 12 19:11:21 kernel: [ .486704] [drm:i915_gem_open]
  Sep 12 19:11:21 kernel: [ .550210] [drm:i915_gem_context_create_ioctl] HW 
context 1 created
  Sep 12 19:11:25 kernel: [ 4447.852792] [drm:drm_mode_getconnector] 
[CONNECTOR:14:?]
  Sep 12 19:11:25 kernel: [ 4447.852796] 
[drm:drm_helper_probe_single_connector_modes_merge_bits] [CONNECTOR:14:eDP-1]
  Sep 12 19:11:25 kernel: [ 4447.852800] [drm:intel_dp_detect] 
[CONNECTOR:14:eDP-1]
  Sep 12 19:11:25 kernel: [ 4447.852804] [drm:_edp_panel_vdd_on] Turning eDP 
VDD on
  Sep 12 19:11:25 kernel: [ 4447.852809] [drm:_edp_panel_vdd_on] PP_STATUS: 
0x8008 PP_CONTROL: 0xabcd000f
  Sep 12 19:11:25 kernel: [ 4447.853257] [drm:intel_dp_probe_oui] Sink OUI: 
00e04c
  Sep 12 19:11:25 kernel: [ 4447.853695] [drm:intel_dp_probe_oui] Branch OUI: 
00e04c
  Sep 12 19:11:25 kernel: [ 4447.853708] [drm:drm_edid_to_eld] ELD: no CEA 
Extension found
  Sep 12 19:11:25 kernel: [ 4447.853711] 
[drm:drm_helper_probe_single_connector_modes_merge_bits] [CONNECTOR:14:eDP-1] 
probed modes :
  Sep 12 19:11:25 kernel: [ 4447.853715] 

[Touch-packages] [Bug 1369113] [NEW] Steam game began crashing 2014-09-12 (cross-post Source bugtracker)

[Adam Colligan]

Public bug reported:

I am cross-posting this issue, which I reported to Valve's Source GIT
issue tracker, because it was suggested that the regression may be due
to Ubuntu Xorg changes rather than changes on the Steam end.

Link: https://github.com/ValveSoftware/Source-1-Games/issues/1822


Symptom --
DoD:Source loads normally. But after a few minutes of playing (not a specific 
time as far as I can tell), the game freezes in place. A short clip (maybe a 
quarter of a second) of the last audio that played then repeats over and over 
on a loop. The process has to be killed manually with a QUIT or HUP signal for 
good measure. This is a new issue that just arose today.

I have included system info, kernel log, and output when game is run
from terminal and crashes.

X info --
X.Org X Server 1.16.0
Release Date: 2014-07-16
X Protocol Version 11, Revision 0
Build Operating System: Linux 3.2.0-61-generic x86_64 Ubuntu
Current Operating System: Linux adam-x360-lin 3.16.0-14-generic #20-Ubuntu SMP 
Sat Sep 6 23:46:49 UTC 2014 x86_64
Kernel command line: BOOT_IMAGE=/vmlinuz-3.16.0-14-generic.efi.signed 
root=UUID=5ad8035a-f2a4-4334-84d8-e2a8a7396bf8 ro drm.debug=0xe plymouth:debug
Build Date: 10 September 2014  01:10:01PM
xorg-server 2:1.16.0-1ubuntu1 (For technical support please see 
http://www.ubuntu.com/support) 
Current version of pixman: 0.32.4
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.


System --

OS: Ubuntu 14.10 (latest updates)
Kernel: 3.16.0-14-generic #20-Ubuntu SMP Sat Sep 6 23:46:49 UTC 2014 x86_64
Model: HP Envy x360
lspci:
00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 0b)
00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated 
Graphics Controller (rev 0b)
00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 0b)
00:14.0 USB controller: Intel Corporation 8 Series USB xHCI HC (rev 04)
00:16.0 Communication controller: Intel Corporation 8 Series HECI #0 (rev 04)
00:1b.0 Audio device: Intel Corporation 8 Series HD Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 1 (rev e4)
00:1c.1 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 2 (rev e4)
00:1c.2 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 3 (rev e4)
00:1c.3 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 4 (rev e4)
00:1d.0 USB controller: Intel Corporation 8 Series USB EHCI #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation 8 Series LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 8 Series SATA Controller 1 AHCI mode
00:1f.3 SMBus: Intel Corporation 8 Series SMBus Controller (rev 04)
02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5227 PCI 
Express Card Reader (rev 01)
08:00.0 Network controller: Intel Corporation Wireless 7260 (rev 9b)
09:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 
PCI Express Gigabit Ethernet Controller (rev 10)


Kernel log excerpt (from game start through crash end) --

Sep 12 19:11:20 kernel: [ 4443.221907] [drm:i915_gem_open]
Sep 12 19:11:20 kernel: [ 4443.266851] [drm:i915_gem_context_create_ioctl] HW 
context 1 created
Sep 12 19:11:21 kernel: [ .169675] [drm:i915_gem_context_destroy_ioctl] HW 
context 1 destroyed
Sep 12 19:11:21 kernel: [ .486704] [drm:i915_gem_open]
Sep 12 19:11:21 kernel: [ .550210] [drm:i915_gem_context_create_ioctl] HW 
context 1 created
Sep 12 19:11:25 kernel: [ 4447.852792] [drm:drm_mode_getconnector] 
[CONNECTOR:14:?]
Sep 12 19:11:25 kernel: [ 4447.852796] 
[drm:drm_helper_probe_single_connector_modes_merge_bits] [CONNECTOR:14:eDP-1]
Sep 12 19:11:25 kernel: [ 4447.852800] [drm:intel_dp_detect] 
[CONNECTOR:14:eDP-1]
Sep 12 19:11:25 kernel: [ 4447.852804] [drm:_edp_panel_vdd_on] Turning eDP VDD 
on
Sep 12 19:11:25 kernel: [ 4447.852809] [drm:_edp_panel_vdd_on] PP_STATUS: 
0x8008 PP_CONTROL: 0xabcd000f
Sep 12 19:11:25 kernel: [ 4447.853257] [drm:intel_dp_probe_oui] Sink OUI: 00e04c
Sep 12 19:11:25 kernel: [ 4447.853695] [drm:intel_dp_probe_oui] Branch OUI: 
00e04c
Sep 12 19:11:25 kernel: [ 4447.853708] [drm:drm_edid_to_eld] ELD: no CEA 
Extension found
Sep 12 19:11:25 kernel: [ 4447.853711] 
[drm:drm_helper_probe_single_connector_modes_merge_bits] [CONNECTOR:14:eDP-1] 
probed modes :
Sep 12 19:11:25 kernel: [ 4447.853715] [drm:drm_mode_debug_printmodeline] 
Modeline 15:1920x1080 60 141000 1920 1958 2018 2104 1080 1084 1090 1116 0x48 
0x9
Sep 12 19:11:25 kernel: [ 4447.853717] [drm:drm_mode_debug_printmodeline] 
Modeline 16:1920x1080 40 94000 1920 1958 2018 2104 1080 1084 1090 1116 0x40 
0x9
Sep 12 19:11:25 kernel: [ 4447.853720] [drm:drm_mode_getconnector] 
[CONNECTOR:14:?]
Sep 12 19:11:25 kernel: [ 4447.853840] [drm:drm_mode_getconnector] 
[CONNECTOR:23:?]
Sep 12 19:11:25 kernel: [ 4447.853841] 
[drm:drm_helper_probe_single_connector_modes_merge_bits] [CONNECTOR:23:HDMI-A-1]
Sep 12 19:11:25 

[Touch-packages] [Bug 1369113] Re: Steam game began crashing 2014-09-12 (cross-post Source bugtracker)

[Adam Colligan]

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

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

Title:
  Steam game began crashing 2014-09-12 (cross-post Source bugtracker)

Status in “steam” package in Ubuntu:
  New
Status in “xorg” package in Ubuntu:
  New

Bug description:
  I am cross-posting this issue, which I reported to Valve's Source GIT
  issue tracker, because it was suggested that the regression may be due
  to Ubuntu Xorg changes rather than changes on the Steam end.

  Link: https://github.com/ValveSoftware/Source-1-Games/issues/1822


  Symptom --
  DoD:Source loads normally. But after a few minutes of playing (not a specific 
time as far as I can tell), the game freezes in place. A short clip (maybe a 
quarter of a second) of the last audio that played then repeats over and over 
on a loop. The process has to be killed manually with a QUIT or HUP signal for 
good measure. This is a new issue that just arose today.

  I have included system info, kernel log, and output when game is run
  from terminal and crashes.

  X info --
  X.Org X Server 1.16.0
  Release Date: 2014-07-16
  X Protocol Version 11, Revision 0
  Build Operating System: Linux 3.2.0-61-generic x86_64 Ubuntu
  Current Operating System: Linux adam-x360-lin 3.16.0-14-generic #20-Ubuntu 
SMP Sat Sep 6 23:46:49 UTC 2014 x86_64
  Kernel command line: BOOT_IMAGE=/vmlinuz-3.16.0-14-generic.efi.signed 
root=UUID=5ad8035a-f2a4-4334-84d8-e2a8a7396bf8 ro drm.debug=0xe plymouth:debug
  Build Date: 10 September 2014  01:10:01PM
  xorg-server 2:1.16.0-1ubuntu1 (For technical support please see 
http://www.ubuntu.com/support) 
  Current version of pixman: 0.32.4
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.

  
  System --

  OS: Ubuntu 14.10 (latest updates)
  Kernel: 3.16.0-14-generic #20-Ubuntu SMP Sat Sep 6 23:46:49 UTC 2014 x86_64
  Model: HP Envy x360
  lspci:
  00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 0b)
  00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated 
Graphics Controller (rev 0b)
  00:03.0 Audio device: Intel Corporation Haswell-ULT HD Audio Controller (rev 
0b)
  00:14.0 USB controller: Intel Corporation 8 Series USB xHCI HC (rev 04)
  00:16.0 Communication controller: Intel Corporation 8 Series HECI #0 (rev 04)
  00:1b.0 Audio device: Intel Corporation 8 Series HD Audio Controller (rev 04)
  00:1c.0 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 1 (rev 
e4)
  00:1c.1 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 2 (rev 
e4)
  00:1c.2 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 3 (rev 
e4)
  00:1c.3 PCI bridge: Intel Corporation 8 Series PCI Express Root Port 4 (rev 
e4)
  00:1d.0 USB controller: Intel Corporation 8 Series USB EHCI #1 (rev 04)
  00:1f.0 ISA bridge: Intel Corporation 8 Series LPC Controller (rev 04)
  00:1f.2 SATA controller: Intel Corporation 8 Series SATA Controller 1 AHCI 
mode
  00:1f.3 SMBus: Intel Corporation 8 Series SMBus Controller (rev 04)
  02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS5227 PCI 
Express Card Reader (rev 01)
  08:00.0 Network controller: Intel Corporation Wireless 7260 (rev 9b)
  09:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 10)


  Kernel log excerpt (from game start through crash end) --

  Sep 12 19:11:20 kernel: [ 4443.221907] [drm:i915_gem_open]
  Sep 12 19:11:20 kernel: [ 4443.266851] [drm:i915_gem_context_create_ioctl] HW 
context 1 created
  Sep 12 19:11:21 kernel: [ .169675] [drm:i915_gem_context_destroy_ioctl] 
HW context 1 destroyed
  Sep 12 19:11:21 kernel: [ .486704] [drm:i915_gem_open]
  Sep 12 19:11:21 kernel: [ .550210] [drm:i915_gem_context_create_ioctl] HW 
context 1 created
  Sep 12 19:11:25 kernel: [ 4447.852792] [drm:drm_mode_getconnector] 
[CONNECTOR:14:?]
  Sep 12 19:11:25 kernel: [ 4447.852796] 
[drm:drm_helper_probe_single_connector_modes_merge_bits] [CONNECTOR:14:eDP-1]
  Sep 12 19:11:25 kernel: [ 4447.852800] [drm:intel_dp_detect] 
[CONNECTOR:14:eDP-1]
  Sep 12 19:11:25 kernel: [ 4447.852804] [drm:_edp_panel_vdd_on] Turning eDP 
VDD on
  Sep 12 19:11:25 kernel: [ 4447.852809] [drm:_edp_panel_vdd_on] PP_STATUS: 
0x8008 PP_CONTROL: 0xabcd000f
  Sep 12 19:11:25 kernel: [ 4447.853257] [drm:intel_dp_probe_oui] Sink OUI: 
00e04c
  Sep 12 19:11:25 kernel: [ 4447.853695] [drm:intel_dp_probe_oui] Branch OUI: 
00e04c
  Sep 12 19:11:25 kernel: [ 4447.853708] [drm:drm_edid_to_eld] ELD: no CEA 
Extension found
  Sep 12 19:11:25 kernel: [ 4447.853711] 
[drm:drm_helper_probe_single_connector_modes_merge_bits] [CONNECTOR:14:eDP-1] 
probed modes :
  Sep 12 19:11:25 kernel: [ 4447.853715] [drm:drm_mode_debug_printmodeline] 
Modeline