[Touch-packages] [Bug 1727401] Re: Corruption on windowed 3D apps running on dGPU (Intel/AMD)

[ethan.hsieh]

** Tags added: verification-done-xenial

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

Title:
  Corruption on windowed 3D apps running on dGPU (Intel/AMD)

Status in Mesa:
  In Progress
Status in OEM Priority Project:
  Triaged
Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa source package in Xenial:
  Fix Committed
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  [Impact]

  Corruption is seen on windowed 3D apps running on dGPU

  [Test case]

  Get a certain Intel/AMD hybrid machine, run 'DRI_PRIME=1 glxgears',
  see how the window has corrupted gfx.

  The fix is to patch Intel i965_dri driver.

  [Regression potential]

  There could be a slight loss of performance, but corruption free
  behaviour.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1727401/+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 1727401] Re: Corruption on windowed 3D apps running on dGPU (Intel/AMD)

[Taihsiang Ho]

Test the same hardware as comment #15. This time I use proposed stack. I
could not reproduce the issue.

More information for reference (including the package information):

ubuntu@201507-18697:~$ DISPLAY=:0 glxgears
Running synchronized to the vertical refresh.  The framerate should be
approximately the same as the monitor refresh rate.
308 frames in 5.0 seconds = 61.559 FPS
299 frames in 5.0 seconds = 59.612 FPS
299 frames in 5.0 seconds = 59.598 FPS

ubuntu@201507-18697:~$ DISPLAY=:0 DRI_PRIME=1 glxgears
Running synchronized to the vertical refresh.  The framerate should be
approximately the same as the monitor refresh rate.
325 frames in 5.0 seconds = 64.859 FPS
300 frames in 5.0 seconds = 59.990 FPS
300 frames in 5.0 seconds = 59.792 FPS
297 frames in 5.0 seconds = 59.214 FPS
298 frames in 5.0 seconds = 59.584 FPS
301 frames in 5.0 seconds = 60.008 FPS
301 frames in 5.0 seconds = 60.000 FPS

ubuntu@201507-18697:~$ uname -a
Linux 201507-18697 4.13.0-25-generic #29-Ubuntu SMP Mon Jan 8 21:14:41 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

ubuntu@201507-18697:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 17.10
Release:17.10
Codename:   artful
ubuntu@201507-18697:~$

ubuntu@201507-18697:~$ dpkg -l libdrm-common libdrm2 libcapnp-0.5.3 
libdrm-amdgpu1 libwayland-egl1-mesa libwayland-client0 libwayland-server0  
libegl1-mesa libgbm1 libmircore1   libmircommon7 libmirprotobuf3  libmirclient9 
libllvm5.0 libgl1-mesa-dri
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name  Version 
ArchitectureDescription
+++-=-===-===-===
ii  libcapnp-0.5.3:amd64  0.5.3-2ubuntu2  
amd64   Cap'n Proto C++ library
ii  libdrm-amdgpu1:amd64  2.4.83-1
amd64   Userspace interface to amdgpu-specific kernel DRM 
services -- runtime
ii  libdrm-common 2.4.83-1
all Userspace interface to kernel DRM services -- 
common files
ii  libdrm2:amd64 2.4.83-1
amd64   Userspace interface to kernel DRM services -- 
runtime
ii  libegl1-mesa:amd6417.2.4-0ubuntu1~17.10.2 
amd64   free implementation of the EGL API -- runtime
ii  libgbm1:amd64 17.2.4-0ubuntu1~17.10.2 
amd64   generic buffer management API -- runtime
ii  libgl1-mesa-dri:amd64 17.2.4-0ubuntu1~17.10.2 
amd64   free implementation of the OpenGL API -- DRI modules
ii  libllvm5.0:amd64  1:5.0-3 
amd64   Modular compiler and toolchain technologies, 
runtime library
ii  libmirclient9:amd64   0.28.0+17.10.20171011.1-0ub 
amd64   Display server for Ubuntu - client library
ii  libmircommon7:amd64   0.28.0+17.10.20171011.1-0ub 
amd64   Display server for Ubuntu - shared library
ii  libmircore1:amd64 0.28.0+17.10.20171011.1-0ub 
amd64   Display server for Ubuntu - shared library
ii  libmirprotobuf3:amd64 0.28.0+17.10.20171011.1-0ub 
amd64   Display server for Ubuntu - RPC definitions
ii  libwayland-client0:amd64  1.14.0-1
amd64   wayland compositor infrastructure - client library
ii  libwayland-egl1-mesa:amd6417.2.4-0ubuntu1~17.10.2 
amd64   implementation of the Wayland EGL platform -- 
runtime
ii  libwayland-server0:amd64  1.14.0-1
amd64   wayland compositor infrastructure - server library


ubuntu@201507-18697:~$ lspci -nn
00:00.0 Host bridge [0600]: Intel Corporation Skylake Host Bridge/DRAM 
Registers [8086:1904] (rev 08)
00:02.0 VGA compatible controller [0300]: Intel Corporation HD Graphics 520 
[8086:1916] (rev 07)
00:04.0 Signal processing controller [1180]: Intel Corporation Skylake 
Processor Thermal Subsystem [8086:1903] (rev 08)
00:14.0 USB controller [0c03]: Intel Corporation Sunrise Point-LP USB 3.0 xHCI 
Controller [8086:9d2f] (rev 20)
00:14.2 Signal processing controller [1180]: Intel Corporation Sunrise Point-LP 
Thermal subsystem [8086:9d31] (rev 20)
00:16.0 Communication controller [0780]: Intel Corporation 

[Touch-packages] [Bug 1727401] Re: Corruption on windowed 3D apps running on dGPU (Intel/AMD)

[Taihsiang Ho]

Hi, I can't reproduce this issue with a fresh installed Artful on the I+A 
system[1] with gfx
  - Intel Corporation HD Graphics 520 [8086:1916] (rev 07)
  - Advanced Micro Devices, Inc. [AMD/ATI] Topaz XT [Radeon R7 M260/M265 / 
M340/M360 / M440/M445] [1002:6900] (rev 81)


I might need more information to reproduce and make sure this issue on Artful 
as well.

---


[1] Test machine -  CID 201507-18697 - Dell Latitude E5570

[2] More information for reference (including package information)


ubuntu@201507-18697:~$ DISPLAY=:0 glxgears
Running synchronized to the vertical refresh.  The framerate should be
approximately the same as the monitor refresh rate.
359 frames in 5.0 seconds = 71.667 FPS
300 frames in 5.0 seconds = 59.997 FPS
301 frames in 5.0 seconds = 60.002 FPS
300 frames in 5.0 seconds = 59.996 FPS
300 frames in 5.0 seconds = 60.000 FPS
301 frames in 5.0 seconds = 60.002 FPS
300 frames in 5.0 seconds = 59.996 FPS

ubuntu@201507-18697:~$ DISPLAY=:0 DRI_PRIME=1 glxgears
Running synchronized to the vertical refresh.  The framerate should be
approximately the same as the monitor refresh rate.
302 frames in 5.0 seconds = 60.321 FPS
301 frames in 5.0 seconds = 59.996 FPS
301 frames in 5.0 seconds = 60.005 FPS
301 frames in 5.0 seconds = 59.989 FPS
301 frames in 5.0 seconds = 60.008 FPS

ubuntu@201507-18697:~$ uname -a
Linux 201507-18697 4.13.0-16-generic #19-Ubuntu SMP Wed Oct 11 18:35:14 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux

ubuntu@201507-18697:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 17.10
Release:17.10
Codename:   artful
ubuntu@201507-18697:~$ apt-cache policy libdrm-amdgpu1
libdrm-amdgpu1:
  Installed: 2.4.83-1
  Candidate: 2.4.83-1
  Version table:
 *** 2.4.83-1 500
500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages
100 /var/lib/dpkg/status


ubuntu@201507-18697:~$ apt-cache policy libgl1-mesa-dri
libgl1-mesa-dri:
  Installed: 17.2.2-0ubuntu1
  Candidate: 17.2.2-0ubuntu1
  Version table:
 *** 17.2.2-0ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu artful/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu artful/main amd64 Packages
100 /var/lib/dpkg/status

ubuntu@201507-18697:~$ dpkg -l libdrm-common libdrm2 libcapnp-0.5.3 
libdrm-amdgpu1 libwayland-egl1-mesa libwayland-client0 libwayland-server0  
libegl1-mesa libgbm1 libmircore1   libmircommon7 libmirprotobuf3  libmirclient9 
libllvm5.0 libgl1-mesa-dri
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name  Version 
ArchitectureDescription
+++-=-===-===-===
ii  libcapnp-0.5.3:amd64  0.5.3-2ubuntu2  
amd64   Cap'n Proto C++ library
ii  libdrm-amdgpu1:amd64  2.4.83-1
amd64   Userspace interface to amdgpu-specific kernel DRM 
services -- runtime
ii  libdrm-common 2.4.83-1
all Userspace interface to kernel DRM services -- 
common files
ii  libdrm2:amd64 2.4.83-1
amd64   Userspace interface to kernel DRM services -- 
runtime
ii  libegl1-mesa:amd6417.2.2-0ubuntu1 
amd64   free implementation of the EGL API -- runtime
ii  libgbm1:amd64 17.2.2-0ubuntu1 
amd64   generic buffer management API -- runtime
ii  libgl1-mesa-dri:amd64 17.2.2-0ubuntu1 
amd64   free implementation of the OpenGL API -- DRI modules
ii  libllvm5.0:amd64  1:5.0-3 
amd64   Modular compiler and toolchain technologies, 
runtime library
ii  libmirclient9:amd64   0.28.0+17.10.20171011.1-0ub 
amd64   Display server for Ubuntu - client library
ii  libmircommon7:amd64   0.28.0+17.10.20171011.1-0ub 
amd64   Display server for Ubuntu - shared library
ii  libmircore1:amd64 0.28.0+17.10.20171011.1-0ub 
amd64   Display server for Ubuntu - shared library
ii  libmirprotobuf3:amd64 0.28.0+17.10.20171011.1-0ub 
amd64   Display server for Ubuntu - RPC definitions
ii  libwayland-client0:amd64  1.14.0-1

[Touch-packages] [Bug 1663157] Re: Guest session processes are not confined in 16.10 and newer releases

[Tyler Hicks]

@rbalint can you please open a new bug to track re-enabling the guest
session with proper confinement rather than piggy back on this bug?

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

Title:
  Guest session processes are not confined in 16.10 and newer releases

Status in Light Display Manager:
  New
Status in lightdm package in Ubuntu:
  Triaged
Status in lightdm source package in Yakkety:
  Fix Released
Status in lightdm source package in Zesty:
  Fix Released
Status in lightdm source package in Artful:
  Fix Released

Bug description:
  Processes launched under a lightdm guest session are not confined by
  the /usr/lib/lightdm/lightdm-guest-session AppArmor profile in Ubuntu
  16.10, Ubuntu 17.04, and Ubuntu Artful (current dev release). The
  processes are unconfined.

  The simple test case is to log into a guest session, launch a terminal
  with ctrl-alt-t, and run the following command:

   $ cat /proc/self/attr/current

  Expected output, as seen in Ubuntu 16.04 LTS, is:

   /usr/lib/lightdm/lightdm-guest-session (enforce)

  Running the command inside of an Ubuntu 16.10 and newer guest session
  results in:

   unconfined

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1663157/+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 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits

[Seyeong Kim]

** Description changed:

  [Impact]
  
  If PID is larger than 6 digits.
  
  apparmor denies process.
  
  this fix is committed, but not released. so all supporting version are
  affected.
  
  [Test Case]
  
  1. making pid over 6 digits
- - i used touch command to do it
- 2. snap install canonical-livepatch ( just picked this pkg )
+ #!/bin/bash
  
- you can see denied msg as original description
+ for i in {1..100}
+ do
+   touch t
+ done
+ 
+ 2. snap install --dangerous core_16-2.29.4.2_amd64.snap ( snap core
+ 16-2.30 avoids using /proc/PID/cmdline, so need to use older version
+ 
+ 3. you can see DENIED msgs in syslog
+ 
+ 4. change /etc/apparmor.d/tunables/kernelvars
+ 5. service apparmor restart
+ 6. service snapd restart
+ 7. DENIED is gone
+ 
+ This is one way, can't reproduce this issue again even if you change
+ back to original kernelvars, and restart snapd
  
  [Regression]
  this fix changes regex only, i don't think there is severe regression. also 
if there is regression, we can revert manually temporarily.
  denied services need to be restarted after fixing this.
  
  [Others]
  
  * Upstream commit:
   
https://gitlab.com/apparmor/apparmor/commit/630cb2a981cdc731847e8fdaafc45bcd337fe747
  
  * commit 630cb2a981cdc731847e8fdaafc45bcd337fe747
  Author: Vincas Dargis 
  Date:   Sat Sep 30 15:28:15 2017 +0300
  
  Allow seven digit pid
  
  * Affecting releases : TXZAB
  --
  $ git describe --contains 630cb2a9
  v2.11.95~5^2
  
  $ rmadison apparmor
   apparmor | 2.8.95~2430-0ubuntu5   | trusty
   apparmor | 2.10.95-0ubuntu2.6~14.04.1 | trusty-security
   apparmor | 2.10.95-0ubuntu2.6~14.04.1 | trusty-updates
   apparmor | 2.10.95-0ubuntu2   | xenial
   apparmor | 2.10.95-0ubuntu2.6 | xenial-security
   apparmor | 2.10.95-0ubuntu2.7 | xenial-updates
   apparmor | 2.11.0-2ubuntu4| zesty
   apparmor | 2.11.0-2ubuntu17   | artful
   apparmor | 2.11.0-2ubuntu18   | bionic
  
  $ rmadison -u debian apparmor
   apparmor   | 2.11.1-4 | unstable
  --
  
  * Revision :
  http://bazaar.launchpad.net/~apparmor-dev/apparmor/master/revision/3722
  
  [Original Description]
  
  If your kernel.pid_max sysctl is set higher than the default, say at 7
  digits, the @{pid} variable no longer matches all pids, causing some
  breakage in any profile using it.
  
  @{pid} is defined in /etc/apparmor.d/tunables:
  
@{pid}={[1-9],[1-9][0-9],[1-9][0-9][0-9],[1-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9],[1-9][0-9][0-9][0-9][0-9][0-9]}
  
  It only covers up to 6 digits.
  
  This Ubuntu 17.04 system has:
  kernel.pid_max = 4194303
  
  And is showing
  type=1400 audit(1505588857.828:792): apparmor="DENIED" operation="open" 
profile="libvirt-55e9e12c-e6dc-4f56-a547-8514cf7d9bf3" 
name="/proc/2168180/task/2769256/comm" pid=2168180 comm="qemu-system-x86" 
requested_mask="wr" denied_mask="wr" fsuid=111 ouid=111
  
  Which should be matched by
  @{PROC}/sys/vm/overcommit_memory r,
  in /etc/apparmor.d/abstractions/libvirt-qemu
  
  I'm seeing similar failures on 16.04 (2.10.95-0ubuntu2.7), 17.04
  (2.11.0-2ubuntu4) and 17.10 (2.11.0-2ubuntu17)
  
  I am aware this is a non-default configuration, but I think this should
  work.

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

Title:
  @{pid} variable broken on systems with pid_max more than 6 digits

Status in AppArmor:
  Fix Committed
Status in AppArmor 2.11 series:
  Fix Committed
Status in apparmor package in Ubuntu:
  Confirmed
Status in apparmor source package in Trusty:
  New
Status in apparmor source package in Xenial:
  New
Status in apparmor source package in Zesty:
  New
Status in apparmor source package in Artful:
  New
Status in apparmor source package in Bionic:
  Confirmed

Bug description:
  [Impact]

  If PID is larger than 6 digits.

  apparmor denies process.

  this fix is committed, but not released. so all supporting version are
  affected.

  [Test Case]

  1. making pid over 6 digits
  #!/bin/bash

  for i in {1..100}
  do
touch t
  done

  2. snap install --dangerous core_16-2.29.4.2_amd64.snap ( snap core
  16-2.30 avoids using /proc/PID/cmdline, so need to use older version

  3. you can see DENIED msgs in syslog

  4. change /etc/apparmor.d/tunables/kernelvars
  5. service apparmor restart
  6. service snapd restart
  7. DENIED is gone

  This is one way, can't reproduce this issue again even if you change
  back to original kernelvars, and restart snapd

  [Regression]
  this fix changes regex only, i don't think there is severe regression. also 
if there is regression, we can revert manually temporarily.
  denied services need to be restarted after fixing this.

  

[Touch-packages] [Bug 1727401] Re: Corruption on windowed 3D apps running on dGPU (Intel/AMD)

[ethan.hsieh]

@Timo

Here is the test result of mesa (xenial-proposed)

A. Test Result:
1. DRI_PRIME=1 glxgear: Pass
2. DRI_PRIME=1 glxgear -fulscreen: Pass
3. glxgear: Pass
4. glxgear -fulscreen: Pass
5. Unigine_Heaven-4.0.run (5mins): Pass
6. Unigine_Heaven-4.0.run (Fullscreen, 5mins): Pass
7. DRI_PRIME=1 Unigine_Heaven-4.0.run (5mins): Pass
8. DRI_PRIME=1 Unigine_Heaven-4.0.run (Fullscreen, 5mins): Pass

B. Test Environment:
1. Ubuntu: Xenial 16.04
2. Graphic Card:
 b. Intel [8086:5917] (rev 07) + AMD [1002:6900] (rev ff)
3.Installed package:
 a. Online Update
 b. Enable xenial-proposed and then upgrade mesa
libglapi-mesa_17.2.4-0ubuntu1~16.04.3~1_amd64.deb
libgl1-mesa-dri_17.2.4-0ubuntu1~16.04.3~1_amd64.deb
libxatracker2_17.2.4-0ubuntu1~16.04.3~1_amd64.deb
libwayland-egl1-mesa_17.2.4-0ubuntu1~16.04.3~1_amd64.deb
libgl1-mesa-glx_17.2.4-0ubuntu1~16.04.3~1_amd64.deb
libgbm1_17.2.4-0ubuntu1~16.04.3~1_amd64.deb
libegl1-mesa_17.2.4-0ubuntu1~16.04.3~1_amd64.deb

** Tags removed: verification-needed-xenial

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

Title:
  Corruption on windowed 3D apps running on dGPU (Intel/AMD)

Status in Mesa:
  In Progress
Status in OEM Priority Project:
  Triaged
Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa source package in Xenial:
  Fix Committed
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  [Impact]

  Corruption is seen on windowed 3D apps running on dGPU

  [Test case]

  Get a certain Intel/AMD hybrid machine, run 'DRI_PRIME=1 glxgears',
  see how the window has corrupted gfx.

  The fix is to patch Intel i965_dri driver.

  [Regression potential]

  There could be a slight loss of performance, but corruption free
  behaviour.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1727401/+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 1742867] Re: Screen blank, audio choppy, system locked

[clickwir]

I used "ubuntu-bug" to gather this info. I see it set
"ExtraDebuggingInterest: I just need to know a workaround" but that's
not what I selected when it asked. I chose the option that was something
like "Yes, but not if too technical".

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

Title:
  Screen blank, audio choppy, system locked

Status in xorg package in Ubuntu:
  New

Bug description:
  While watching a YouTube video, screen went blank. Audio cut out,
  after a few seconds the audio started playing normally for a few more
  seconds then kept repeating the last half a second of audio for a few
  more seconds. Then it stopped and nothing responded.

  It did this a few times over the course of an hour. Had to power off
  the PC to get a reboot. Last time it did this I ssh'd from another PC
  to get dmesg and syslog info as it happened. Attaching those captures.

  clickwir@mach:~$ uname -a
  Linux mach 4.13.0-25-generic #29-Ubuntu SMP Mon Jan 8 21:14:41 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  clickwir@mach:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 17.10
  Release:17.10
  Codename:   artful

  
   dmesg 

  [   10.136445] bond0: Enslaving enp7s0f1 as an active interface with an up 
link
  [   10.136497] IPv6: ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
  [   10.144317] e1000e :07:00.0 enp7s0f0: changing MTU from 1500 to 9000
  [   10.310070] e1000e :07:00.1 enp7s0f1: changing MTU from 1500 to 9000
  [   10.625965] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
  [   10.730200] r8169 :02:00.0 eth0: link down
  [   10.730246] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
  [   12.573052] e1000e: enp7s0f0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   12.633055] e1000e: enp7s0f1 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   16.875586] FS-Cache: Loaded
  [   16.896010] FS-Cache: Netfs 'nfs' registered for caching
  [   16.914353] NFS: Registering the id_resolver key type
  [   16.914364] Key type id_resolver registered
  [   16.914364] Key type id_legacy registered
  [   17.485539] ip6_tables: (C) 2000-2006 Netfilter Core Team
  [   17.513074] Ebtables v2.0 registered
  [   17.564084] radeon_dp_aux_transfer_native: 74 callbacks suppressed
  [   17.863232] bridge: filtering via arp/ip/ip6tables is no longer available 
by default. Update your scripts to load br_netfilter if you need this.
  [   17.864899] virbr0: port 1(virbr0-nic) entered blocking state
  [   17.864903] virbr0: port 1(virbr0-nic) entered disabled state
  [   17.864995] device virbr0-nic entered promiscuous mode
  [   17.960322] nf_conntrack version 0.5.0 (65536 buckets, 262144 max)
  [   18.038385] virbr0: port 1(virbr0-nic) entered blocking state
  [   18.038388] virbr0: port 1(virbr0-nic) entered listening state
  [   18.095412] virbr0: port 1(virbr0-nic) entered disabled state
  [   89.815180] radeon_dp_aux_transfer_native: 74 callbacks suppressed
  [   92.062606] show_signal_msg: 27 callbacks suppressed
  [   92.062608] xembedsniproxy[2507]: segfault at 2 ip 55ea4a6890d7 sp 
7fff6c7a7c30 error 4 in xembedsniproxy[55ea4a67d000+13000]
  [   95.955166] radeon_dp_aux_transfer_native: 74 callbacks suppressed

  ### abnormal begins here ###

  [ 1429.496584] sched: RT throttling activated
  [ 1429.706303] clocksource: timekeeping watchdog on CPU3: Marking clocksource 
'tsc' as unstable because the skew is too large:
  [ 1429.706305] clocksource:   'hpet' wd_now: c4741f2e 
wd_last: c3bcdb60 mask: 
  [ 1429.706306] clocksource:   'tsc' cs_now: 4acf553cc2d 
cs_last: 4ac71a54967 mask: 
  [ 1429.706309] tsc: Marking TSC unstable due to clocksource watchdog
  [ 1434.739539] nfs: server 10.1.0.4 not responding, still trying
  [ 1437.469449] nfs: server 10.1.0.4 OK
  [ 1439.143494] TSC found unstable after boot, most likely due to broken BIOS. 
Use 'tsc=unstable'.
  [ 1439.143498] sched_clock: Marking unstable (1439092126811, 
50992985)<-(1439477690212, -334199655)
  [ 1440.403916] clocksource: Switched to clocksource hpet
  [ 1443.553969] hrtimer: interrupt took 629117003 ns
  [ 1454.039245] INFO: NMI handler (nmi_cpu_backtrace_handler) took too long to 
run: 209.684 msecs
  [ 1454.454671] INFO: NMI handler (perf_event_nmi_handler) took too long to 
run: 44.646 msecs
  [ 1454.454673] perf: interrupt took too long (349007 > 2500), lowering 
kernel.perf_event_max_sample_rate to 500
  [ 1455.293492] INFO: NMI handler (perf_event_nmi_handler) took too long to 
run: 61.329 msecs
  [ 1455.293494] perf: interrupt took too long (479410 > 436258), lowering 
kernel.perf_event_max_sample_rate to 250
  [ 1463.284343] INFO: NMI handler (perf_event_nmi_handler) took too long to 
run: 172.103 msecs
  [ 1463.284345] perf: 

[Touch-packages] [Bug 1742867] Re: Screen blank, audio choppy, system locked

[clickwir]

Quick comment, before today I've never seen this happen on this PC. Now
it's happened 4 times in the past couple hours.

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

Title:
  Screen blank, audio choppy, system locked

Status in xorg package in Ubuntu:
  New

Bug description:
  While watching a YouTube video, screen went blank. Audio cut out,
  after a few seconds the audio started playing normally for a few more
  seconds then kept repeating the last half a second of audio for a few
  more seconds. Then it stopped and nothing responded.

  It did this a few times over the course of an hour. Had to power off
  the PC to get a reboot. Last time it did this I ssh'd from another PC
  to get dmesg and syslog info as it happened. Attaching those captures.

  clickwir@mach:~$ uname -a
  Linux mach 4.13.0-25-generic #29-Ubuntu SMP Mon Jan 8 21:14:41 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  clickwir@mach:~$ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 17.10
  Release:17.10
  Codename:   artful

  
   dmesg 

  [   10.136445] bond0: Enslaving enp7s0f1 as an active interface with an up 
link
  [   10.136497] IPv6: ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
  [   10.144317] e1000e :07:00.0 enp7s0f0: changing MTU from 1500 to 9000
  [   10.310070] e1000e :07:00.1 enp7s0f1: changing MTU from 1500 to 9000
  [   10.625965] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
  [   10.730200] r8169 :02:00.0 eth0: link down
  [   10.730246] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
  [   12.573052] e1000e: enp7s0f0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   12.633055] e1000e: enp7s0f1 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
  [   16.875586] FS-Cache: Loaded
  [   16.896010] FS-Cache: Netfs 'nfs' registered for caching
  [   16.914353] NFS: Registering the id_resolver key type
  [   16.914364] Key type id_resolver registered
  [   16.914364] Key type id_legacy registered
  [   17.485539] ip6_tables: (C) 2000-2006 Netfilter Core Team
  [   17.513074] Ebtables v2.0 registered
  [   17.564084] radeon_dp_aux_transfer_native: 74 callbacks suppressed
  [   17.863232] bridge: filtering via arp/ip/ip6tables is no longer available 
by default. Update your scripts to load br_netfilter if you need this.
  [   17.864899] virbr0: port 1(virbr0-nic) entered blocking state
  [   17.864903] virbr0: port 1(virbr0-nic) entered disabled state
  [   17.864995] device virbr0-nic entered promiscuous mode
  [   17.960322] nf_conntrack version 0.5.0 (65536 buckets, 262144 max)
  [   18.038385] virbr0: port 1(virbr0-nic) entered blocking state
  [   18.038388] virbr0: port 1(virbr0-nic) entered listening state
  [   18.095412] virbr0: port 1(virbr0-nic) entered disabled state
  [   89.815180] radeon_dp_aux_transfer_native: 74 callbacks suppressed
  [   92.062606] show_signal_msg: 27 callbacks suppressed
  [   92.062608] xembedsniproxy[2507]: segfault at 2 ip 55ea4a6890d7 sp 
7fff6c7a7c30 error 4 in xembedsniproxy[55ea4a67d000+13000]
  [   95.955166] radeon_dp_aux_transfer_native: 74 callbacks suppressed

  ### abnormal begins here ###

  [ 1429.496584] sched: RT throttling activated
  [ 1429.706303] clocksource: timekeeping watchdog on CPU3: Marking clocksource 
'tsc' as unstable because the skew is too large:
  [ 1429.706305] clocksource:   'hpet' wd_now: c4741f2e 
wd_last: c3bcdb60 mask: 
  [ 1429.706306] clocksource:   'tsc' cs_now: 4acf553cc2d 
cs_last: 4ac71a54967 mask: 
  [ 1429.706309] tsc: Marking TSC unstable due to clocksource watchdog
  [ 1434.739539] nfs: server 10.1.0.4 not responding, still trying
  [ 1437.469449] nfs: server 10.1.0.4 OK
  [ 1439.143494] TSC found unstable after boot, most likely due to broken BIOS. 
Use 'tsc=unstable'.
  [ 1439.143498] sched_clock: Marking unstable (1439092126811, 
50992985)<-(1439477690212, -334199655)
  [ 1440.403916] clocksource: Switched to clocksource hpet
  [ 1443.553969] hrtimer: interrupt took 629117003 ns
  [ 1454.039245] INFO: NMI handler (nmi_cpu_backtrace_handler) took too long to 
run: 209.684 msecs
  [ 1454.454671] INFO: NMI handler (perf_event_nmi_handler) took too long to 
run: 44.646 msecs
  [ 1454.454673] perf: interrupt took too long (349007 > 2500), lowering 
kernel.perf_event_max_sample_rate to 500
  [ 1455.293492] INFO: NMI handler (perf_event_nmi_handler) took too long to 
run: 61.329 msecs
  [ 1455.293494] perf: interrupt took too long (479410 > 436258), lowering 
kernel.perf_event_max_sample_rate to 250
  [ 1463.284343] INFO: NMI handler (perf_event_nmi_handler) took too long to 
run: 172.103 msecs
  [ 1463.284345] perf: interrupt took too long (1344829 > 599262), lowering 
kernel.perf_event_max_sample_rate to 250
  [ 1465.175694] INFO: 

[Touch-packages] [Bug 1742867] [NEW] Screen blank, audio choppy, system locked

[clickwir]

Public bug reported:

While watching a YouTube video, screen went blank. Audio cut out, after
a few seconds the audio started playing normally for a few more seconds
then kept repeating the last half a second of audio for a few more
seconds. Then it stopped and nothing responded.

It did this a few times over the course of an hour. Had to power off the
PC to get a reboot. Last time it did this I ssh'd from another PC to get
dmesg and syslog info as it happened. Attaching those captures.

clickwir@mach:~$ uname -a
Linux mach 4.13.0-25-generic #29-Ubuntu SMP Mon Jan 8 21:14:41 UTC 2018 x86_64 
x86_64 x86_64 GNU/Linux

clickwir@mach:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 17.10
Release:17.10
Codename:   artful


 dmesg 

[   10.136445] bond0: Enslaving enp7s0f1 as an active interface with an up link
[   10.136497] IPv6: ADDRCONF(NETDEV_CHANGE): bond0: link becomes ready
[   10.144317] e1000e :07:00.0 enp7s0f0: changing MTU from 1500 to 9000
[   10.310070] e1000e :07:00.1 enp7s0f1: changing MTU from 1500 to 9000
[   10.625965] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   10.730200] r8169 :02:00.0 eth0: link down
[   10.730246] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   12.573052] e1000e: enp7s0f0 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
[   12.633055] e1000e: enp7s0f1 NIC Link is Up 1000 Mbps Full Duplex, Flow 
Control: None
[   16.875586] FS-Cache: Loaded
[   16.896010] FS-Cache: Netfs 'nfs' registered for caching
[   16.914353] NFS: Registering the id_resolver key type
[   16.914364] Key type id_resolver registered
[   16.914364] Key type id_legacy registered
[   17.485539] ip6_tables: (C) 2000-2006 Netfilter Core Team
[   17.513074] Ebtables v2.0 registered
[   17.564084] radeon_dp_aux_transfer_native: 74 callbacks suppressed
[   17.863232] bridge: filtering via arp/ip/ip6tables is no longer available by 
default. Update your scripts to load br_netfilter if you need this.
[   17.864899] virbr0: port 1(virbr0-nic) entered blocking state
[   17.864903] virbr0: port 1(virbr0-nic) entered disabled state
[   17.864995] device virbr0-nic entered promiscuous mode
[   17.960322] nf_conntrack version 0.5.0 (65536 buckets, 262144 max)
[   18.038385] virbr0: port 1(virbr0-nic) entered blocking state
[   18.038388] virbr0: port 1(virbr0-nic) entered listening state
[   18.095412] virbr0: port 1(virbr0-nic) entered disabled state
[   89.815180] radeon_dp_aux_transfer_native: 74 callbacks suppressed
[   92.062606] show_signal_msg: 27 callbacks suppressed
[   92.062608] xembedsniproxy[2507]: segfault at 2 ip 55ea4a6890d7 sp 
7fff6c7a7c30 error 4 in xembedsniproxy[55ea4a67d000+13000]
[   95.955166] radeon_dp_aux_transfer_native: 74 callbacks suppressed

### abnormal begins here ###

[ 1429.496584] sched: RT throttling activated
[ 1429.706303] clocksource: timekeeping watchdog on CPU3: Marking clocksource 
'tsc' as unstable because the skew is too large:
[ 1429.706305] clocksource:   'hpet' wd_now: c4741f2e 
wd_last: c3bcdb60 mask: 
[ 1429.706306] clocksource:   'tsc' cs_now: 4acf553cc2d 
cs_last: 4ac71a54967 mask: 
[ 1429.706309] tsc: Marking TSC unstable due to clocksource watchdog
[ 1434.739539] nfs: server 10.1.0.4 not responding, still trying
[ 1437.469449] nfs: server 10.1.0.4 OK
[ 1439.143494] TSC found unstable after boot, most likely due to broken BIOS. 
Use 'tsc=unstable'.
[ 1439.143498] sched_clock: Marking unstable (1439092126811, 
50992985)<-(1439477690212, -334199655)
[ 1440.403916] clocksource: Switched to clocksource hpet
[ 1443.553969] hrtimer: interrupt took 629117003 ns
[ 1454.039245] INFO: NMI handler (nmi_cpu_backtrace_handler) took too long to 
run: 209.684 msecs
[ 1454.454671] INFO: NMI handler (perf_event_nmi_handler) took too long to run: 
44.646 msecs
[ 1454.454673] perf: interrupt took too long (349007 > 2500), lowering 
kernel.perf_event_max_sample_rate to 500
[ 1455.293492] INFO: NMI handler (perf_event_nmi_handler) took too long to run: 
61.329 msecs
[ 1455.293494] perf: interrupt took too long (479410 > 436258), lowering 
kernel.perf_event_max_sample_rate to 250
[ 1463.284343] INFO: NMI handler (perf_event_nmi_handler) took too long to run: 
172.103 msecs
[ 1463.284345] perf: interrupt took too long (1344829 > 599262), lowering 
kernel.perf_event_max_sample_rate to 250
[ 1465.175694] INFO: NMI handler (perf_event_nmi_handler) took too long to run: 
209.709 msecs
[ 1479.788229] perf: interrupt took too long (1849954 > 1681036), lowering 
kernel.perf_event_max_sample_rate to 250
[ 1481.889284] INFO: NMI handler (perf_event_nmi_handler) took too long to run: 
209.761 msecs
[ 1481.889284] perf: interrupt took too long (3252104 > 2312442), lowering 
kernel.perf_event_max_sample_rate to 250
[ 1491.745472] INFO: NMI handler (perf_event_nmi_handler) took too long to run: 
401.897 msecs
[ 1491.745472] perf: 

[Touch-packages] [Bug 1742865] [NEW] Fn Keys do not work, nvidia card not found

[marc]

Public bug reported:

Browsed and tried solutions over the past 2 years, nothing worked...

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-108.131-generic 4.4.98
Uname: Linux 4.4.0-108-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Fri Jan 12 06:43:48 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: Lenovo Skylake Integrated Graphics [17aa:3828]
   Subsystem: Lenovo GM108M [GeForce 940M] [17aa:3829]
InstallationDate: Installed on 2016-07-07 (553 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 04f3:208d Elan Microelectronics Corp. 
 Bus 001 Device 003: ID 174f:14e6 Syntek 
 Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 80R6
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-108-generic.efi.signed 
root=UUID=8fa7aafa-77cc-4651-b87f-4565439e7577 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/28/2015
dmi.bios.vendor: LENOVO
dmi.bios.version: D3CN27WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Lenovo Yoga 500-15ISK
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo Yoga 500-15ISK
dmi.modalias: 
dmi:bvnLENOVO:bvrD3CN27WW:bd10/28/2015:svnLENOVO:pn80R6:pvrLenovoYoga500-15ISK:rvnLENOVO:rnLenovoYoga500-15ISK:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYoga500-15ISK:
dmi.product.name: 80R6
dmi.product.version: Lenovo Yoga 500-15ISK
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Fri Jan 12 06:14:57 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   14162 
 vendor SDC
xserver.version: 2:1.18.4-0ubuntu0.7

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


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

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

Title:
  Fn Keys do not work, nvidia card not found

Status in xorg package in Ubuntu:
  New

Bug description:
  Browsed and tried solutions over the past 2 years, nothing worked...

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-108.131-generic 4.4.98
  Uname: Linux 4.4.0-108-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Jan 12 06:43:48 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Lenovo Skylake Integrated Graphics [17aa:3828]
 Subsystem: Lenovo GM108M [GeForce 940M] [17aa:3829]
  InstallationDate: Installed on 2016-07-07 (553 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 04f3:208d Elan Microelectronics Corp. 
   Bus 001 Device 003: ID 174f:14e6 Syntek 
   Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 

[Touch-packages] [Bug 1718824] Re: The analogue audio does not work on the Dell USB Dock

[Daniel van Vugt]

It's ready :)

https://launchpad.net/ubuntu/+source/pulseaudio/1:11.1-1ubuntu4

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

Title:
  The analogue audio does not work on the Dell USB Dock

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  Triaged
Status in pulseaudio package in Ubuntu:
  In Progress
Status in pulseaudio source package in Xenial:
  New
Status in pulseaudio source package in Artful:
  New

Bug description:
  SRU Document:

  [Impact]

  If users use the latest Dell USB Dock, e.g. TB16, they will found the
  analog audio (lineout jack) can't work under ubuntu linux

  [Test Case]

  After applying the fix, users can play sound via analog speaker or
  lineout freely. Without the fix, users can't play sound from lineout
  jack.

  [Regression Potential]

  No any possibility to introduce regression since this fix just adding
  a new dock's support, it does not change any existing code.

  [Other Info]

  No more info here

  Steps:
  1. Cold boot system with BME/IE connected
  2. Plug in a speaker to Line-out jack
  3. Set Analog Stereo Output from Sound settings

  Expected results: Line-out port can work

  Actual results: Line-out port not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1718824/+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 1742750] Re: [bionic-proposed] Pulseaudio 1:11.1-1ubuntu3 will not start due to invalid /etc/pulse/default.pa file

[Daniel van Vugt]

pulseaudio (1:11.1-1ubuntu4) bionic; urgency=high

  * 0030-load-module-switch-on-connect.patch: Correct typo in default.pa
causing pulseaudio startup failure. (LP: #1742750, LP: #1732629)
  * Refresh patches to apply more cleanly:
- 0802-alsa-mixer-Add-support-for-usb-audio-in-the-Dell-doc.patch
- 0803-build-sys-add-the-Dell-dock-TB16-configuration.patch

 -- Daniel van Vugt   Fri, 12 Jan 2018
10:23:11 +0800

** Changed in: pulseaudio (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  [bionic-proposed] Pulseaudio 1:11.1-1ubuntu3 will not start due to
  invalid /etc/pulse/default.pa file

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  Version 1:11.1-1ubuntu3 added 0030-load-module-switch-on-
  connect.patch, which changes line 38 of /etc/pulse/default.pa to read
  ".endif### Load audio drivers statically".  It appears that there are
  a couple of line feeds missing here, and having the comment on the
  same line as the endif causes pulseaudio not to start.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1742750/+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 1732629] Re: Selecting USB Amp/Dac audio output in gnome sound does nothing

[Daniel van Vugt]

Users of 18.04 can now test:

https://launchpad.net/ubuntu/+source/pulseaudio/1:11.1-1ubuntu4

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

Title:
  Selecting USB Amp/Dac audio output in gnome sound does nothing

Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  Running Ubuntu 17.10, when I plug an external USB Amp/Dac it is
  correctly recognized and I can play audio through it via aplay, but
  when I select it as my output sink from gnome sound, nothing happens:
  apps still output sound via the speakers.

  In order to fix it I have to restart pulseaudio.
  I've also found online that modifying /etc/pulse/default.pa, moving 
module-switch-on-connect.so loading before module-udev-detect.so, permanently 
fixes the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   sergio 1374 F...m pulseaudio
   /dev/snd/controlC1:  sergio 1374 F pulseaudio
   /dev/snd/controlC0:  sergio 1374 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 16 09:03:19 2017
  InstallationDate: Installed on 2017-10-24 (22 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.4
  dmi.board.name: 0X41RR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.4:bd06/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0X41RR:rvrA02:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5520
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2017-11-15T18:42:36.359190

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1732629/+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 1735594] Re: [regression] compiz crashes after Mesa upgrade

[Phil Norisez]

I got it to work, and it fixes my problem with the launcher resulting in
an unknown file error on /usr/bin/compiz.

Go to Software & Updates via command line
ubuntu-software &
and selecting it from a list of apt applications.

Use Developer Options to enable xenial-proposed.

Then run command line:
sudo apt-get install libgl1-mesa-dri/xenial-proposed

This installed it for me.

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

Title:
  [regression] compiz crashes after Mesa upgrade

Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa source package in Xenial:
  Fix Committed
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  When I use the Unity session I automatically get logged out under these 
conditions:

  When I hover with my mouse over any icon of the sidebar.
  When I press the alt key.
  When I press the super key.

  running dmesg after this unwanted logout happens I get following
  information:

  compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0
  error 4 in i965_dri.so[7fbca2af6000+7e4000]

  This is caused by a mesa upgrade, which added a patch for bug #1727401. The 
crasher is reproduced on:
  - gen4 / gen5 Intel
  - if using modesetting X driver, like when xserver-xorg-video-intel is not 
installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults 
to modesetting)

  [Test case]
  Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash.

  [Regression potential]
  The backported patches need to be tested, here for regressions and on 1727401 
that they fix the original bug (again).

  Best to test on a wide array of Intel HW:
  gen4 (965GM/GM45/G45)
  gen5 (Ironlake)
  gen6 (Sandy Bridge)
  gen7 (Bay Trail, Ivy Bridge, Haswell)
  gen8 (Braswell, Broadwell)
  gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594/+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 934291] Re: Deleting or stopping print jobs does not work

[Bug Watch Updater]

** Changed in: gnome-control-center
   Status: Incomplete => Unknown

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

Title:
  Deleting or stopping print jobs does not work

Status in gnome-control-center:
  Unknown
Status in cups package in Ubuntu:
  Invalid
Status in cups-pk-helper package in Ubuntu:
  In Progress
Status in gnome-control-center package in Ubuntu:
  Invalid

Bug description:
  Deleting or stopping print jobs through the "gnome-control-center -> 
printers" menu is not possible.
  (Black rectangle for stopping can be pressed, nothing happens.)

  Deleting with cups via webinterface does work. ( http://localhost:631/
  )

  Please let me know which information to provide.

  Cheers

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-control-center 1:3.2.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17
  Uname: Linux 3.0.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Fri Feb 17 16:47:32 2012
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to oneiric on 2011-12-17 (61 days ago)
  usr_lib_gnome-control-center:
   deja-dup   22.0~bzr1290.37~oneiric1
   gnome-bluetooth3.2.0-0ubuntu2
   indicator-datetime 0.3.1-0ubuntu1.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/934291/+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 1742852] [NEW] [hostname, Realtek ALC294, Speaker, Internal] No sound at all after windows update

[gabriel]

Public bug reported:

After a windows update I lost all the sound on my ubuntu machine. It's the 
second time that this happends.
My sound is unmuted and at a loud level and nothing is comming out of my 
speakers.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
Uname: Linux 4.13.0-26-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gbergeron   2408 F pulseaudio
  gbergeron   3656 F alsamixer
CurrentDesktop: Unity
Date: Thu Jan 11 22:21:23 2018
InstallationDate: Installed on 2017-11-29 (43 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0p:   gbergeron   2408 F...m pulseaudio
 /dev/snd/controlC0:  gbergeron   2408 F pulseaudio
  gbergeron   3656 F alsamixer
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [hostname, Realtek ALC294, Speaker, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/23/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX430UAR.203
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX430UAR
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX430UAR.203:bd08/23/2017:svnASUSTeKCOMPUTERINC.:pnUX430UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX430UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: UX
dmi.product.name: UX430UAR
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-bug xenial

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

Title:
  [hostname, Realtek ALC294, Speaker, Internal] No sound at all after
  windows update

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  After a windows update I lost all the sound on my ubuntu machine. It's the 
second time that this happends.
  My sound is unmuted and at a loud level and nothing is comming out of my 
speakers.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gbergeron   2408 F pulseaudio
gbergeron   3656 F alsamixer
  CurrentDesktop: Unity
  Date: Thu Jan 11 22:21:23 2018
  InstallationDate: Installed on 2017-11-29 (43 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   gbergeron   2408 F...m pulseaudio
   /dev/snd/controlC0:  gbergeron   2408 F pulseaudio
gbergeron   3656 F alsamixer
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [hostname, Realtek ALC294, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/23/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX430UAR.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX430UAR
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX430UAR.203:bd08/23/2017:svnASUSTeKCOMPUTERINC.:pnUX430UAR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX430UAR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX430UAR
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1742852/+subscriptions

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

[Touch-packages] [Bug 1742769] Re: Pulse Audio Won't Run After BionicBeaver Update

[Daniel van Vugt]

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

This one is a duplicate so effectively closed already.

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

Title:
  Pulse Audio Won't Run After BionicBeaver Update

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  As per the bug report, I've noticed that Pulse Audio is segfaulting.
  Happened after the large update to Bionic Beaver this morning
  (Thursday Jan 11/18).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu3
  ProcVersionSignature: Ubuntu 4.14.0-16.19-generic 4.14.12
  Uname: Linux 4.14.0-16-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D11p', 
'/dev/snd/pcmC1D10p', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', 
'/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: GNOME
  Date: Thu Jan 11 13:32:21 2018
  InstallationDate: Installed on 2017-12-20 (21 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1401
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97 LE R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1401:bd12/12/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97LER2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

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

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

Re: [Touch-packages] [Bug 1742769] Re: Pulse Audio Won't Run After BionicBeaver Update

[Stephen Allen]

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

OK Thanks for this - Did not see that one prior to filing. Should I close
mine or has that already been done?

On Thu, Jan 11, 2018 at 9:20 PM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:

> *** This bug is a duplicate of bug 1742750 ***
> https://bugs.launchpad.net/bugs/1742750
>
> Duplicate of bug 1742750, thanks.
>
> ** This bug has been marked a duplicate of bug 1742750
>Pulseaudio 1:11.1-1ubuntu3 will not start due to invalid /etc/pulse/
> default.pa file
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1742769
>
> Title:
>   Pulse Audio Won't Run After BionicBeaver Update
>
> Status in pulseaudio package in Ubuntu:
>   New
>
> Bug description:
>   As per the bug report, I've noticed that Pulse Audio is segfaulting.
>   Happened after the large update to Bionic Beaver this morning
>   (Thursday Jan 11/18).
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: pulseaudio 1:11.1-1ubuntu3
>   ProcVersionSignature: Ubuntu 4.14.0-16.19-generic 4.14.12
>   Uname: Linux 4.14.0-16-generic x86_64
>   ApportVersion: 2.20.8-0ubuntu6
>   Architecture: amd64
>   AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp',
> '/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c',
> '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p',
> '/dev/snd/controlC0', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D11p',
> '/dev/snd/pcmC1D10p', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p',
> '/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1',
> '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
>   CurrentDesktop: GNOME
>   Date: Thu Jan 11 13:32:21 2018
>   InstallationDate: Installed on 2017-12-20 (21 days ago)
>   InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64
> (20170920)
>   PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
> PulseAudio daemon running, or not running as session daemon.
>   SourcePackage: pulseaudio
>   Symptom: audio
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 12/12/2012
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: 1401
>   dmi.board.asset.tag: To be filled by O.E.M.
>   dmi.board.name: M5A97 LE R2.0
>   dmi.board.vendor: ASUSTeK COMPUTER INC.
>   dmi.board.version: Rev 1.xx
>   dmi.chassis.asset.tag: To Be Filled By O.E.M.
>   dmi.chassis.type: 3
>   dmi.chassis.vendor: To Be Filled By O.E.M.
>   dmi.chassis.version: To Be Filled By O.E.M.
>   dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvr1401:bd12/12/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97LER2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
>   dmi.product.family: To be filled by O.E.M.
>   dmi.product.name: To be filled by O.E.M.
>   dmi.product.version: To be filled by O.E.M.
>   dmi.sys.vendor: To be filled by O.E.M.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1742769/+subscriptions
>


-- 

This email is printed from 100% recycled electrons.

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

Title:
  Pulse Audio Won't Run After BionicBeaver Update

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  As per the bug report, I've noticed that Pulse Audio is segfaulting.
  Happened after the large update to Bionic Beaver this morning
  (Thursday Jan 11/18).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu3
  ProcVersionSignature: Ubuntu 4.14.0-16.19-generic 4.14.12
  Uname: Linux 4.14.0-16-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D11p', 
'/dev/snd/pcmC1D10p', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', 
'/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: GNOME
  Date: Thu Jan 11 13:32:21 2018
  InstallationDate: Installed on 2017-12-20 (21 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1401
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97 LE R2.0
  

[Touch-packages] [Bug 1718824] Re: The analogue audio does not work on the Dell USB Dock

[Hui Wang]

@Daniel,

Got it, waiting for 1:11.1-1ubuntu4 is ready. Then will do the test.

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

Title:
  The analogue audio does not work on the Dell USB Dock

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  Triaged
Status in pulseaudio package in Ubuntu:
  In Progress
Status in pulseaudio source package in Xenial:
  New
Status in pulseaudio source package in Artful:
  New

Bug description:
  SRU Document:

  [Impact]

  If users use the latest Dell USB Dock, e.g. TB16, they will found the
  analog audio (lineout jack) can't work under ubuntu linux

  [Test Case]

  After applying the fix, users can play sound via analog speaker or
  lineout freely. Without the fix, users can't play sound from lineout
  jack.

  [Regression Potential]

  No any possibility to introduce regression since this fix just adding
  a new dock's support, it does not change any existing code.

  [Other Info]

  No more info here

  Steps:
  1. Cold boot system with BME/IE connected
  2. Plug in a speaker to Line-out jack
  3. Set Analog Stereo Output from Sound settings

  Expected results: Line-out port can work

  Actual results: Line-out port not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1718824/+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 1742750] Re: [bionic-proposed] Pulseaudio 1:11.1-1ubuntu3 will not start due to invalid /etc/pulse/default.pa file

[Daniel van Vugt]

** Tags added: bionic regression-proposed

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

Title:
  [bionic-proposed] Pulseaudio 1:11.1-1ubuntu3 will not start due to
  invalid /etc/pulse/default.pa file

Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  Version 1:11.1-1ubuntu3 added 0030-load-module-switch-on-
  connect.patch, which changes line 38 of /etc/pulse/default.pa to read
  ".endif### Load audio drivers statically".  It appears that there are
  a couple of line feeds missing here, and having the comment on the
  same line as the endif causes pulseaudio not to start.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1742750/+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 1735594] Re: [regression] compiz crashes after Mesa upgrade

[Leo Pilachowski]

It appears that the mirror I contact to still has not synced.  How do I
use "archive.ubuntu.com" ?

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

Title:
  [regression] compiz crashes after Mesa upgrade

Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa source package in Xenial:
  Fix Committed
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  When I use the Unity session I automatically get logged out under these 
conditions:

  When I hover with my mouse over any icon of the sidebar.
  When I press the alt key.
  When I press the super key.

  running dmesg after this unwanted logout happens I get following
  information:

  compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0
  error 4 in i965_dri.so[7fbca2af6000+7e4000]

  This is caused by a mesa upgrade, which added a patch for bug #1727401. The 
crasher is reproduced on:
  - gen4 / gen5 Intel
  - if using modesetting X driver, like when xserver-xorg-video-intel is not 
installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults 
to modesetting)

  [Test case]
  Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash.

  [Regression potential]
  The backported patches need to be tested, here for regressions and on 1727401 
that they fix the original bug (again).

  Best to test on a wide array of Intel HW:
  gen4 (965GM/GM45/G45)
  gen5 (Ironlake)
  gen6 (Sandy Bridge)
  gen7 (Bay Trail, Ivy Bridge, Haswell)
  gen8 (Braswell, Broadwell)
  gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594/+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 1742750] Re: Pulseaudio 1:11.1-1ubuntu3 will not start due to invalid /etc/pulse/default.pa file

[Daniel van Vugt]

Fix for bionic.

** Patch added: "pulseaudio_11.1-1ubuntu4.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1742750/+attachment/5035556/+files/pulseaudio_11.1-1ubuntu4.debdiff

** Summary changed:

- Pulseaudio 1:11.1-1ubuntu3 will not start due to invalid 
/etc/pulse/default.pa file
+ [bionic-proposed] Pulseaudio 1:11.1-1ubuntu3 will not start due to invalid 
/etc/pulse/default.pa file

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

Title:
  [bionic-proposed] Pulseaudio 1:11.1-1ubuntu3 will not start due to
  invalid /etc/pulse/default.pa file

Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  Version 1:11.1-1ubuntu3 added 0030-load-module-switch-on-
  connect.patch, which changes line 38 of /etc/pulse/default.pa to read
  ".endif### Load audio drivers statically".  It appears that there are
  a couple of line feeds missing here, and having the comment on the
  same line as the endif causes pulseaudio not to start.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1742750/+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 1742769] Re: Pulse Audio Won't Run After BionicBeaver Update

[Daniel van Vugt]

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

Duplicate of bug 1742750, thanks.

** This bug has been marked a duplicate of bug 1742750
   Pulseaudio 1:11.1-1ubuntu3 will not start due to invalid 
/etc/pulse/default.pa file

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

Title:
  Pulse Audio Won't Run After BionicBeaver Update

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  As per the bug report, I've noticed that Pulse Audio is segfaulting.
  Happened after the large update to Bionic Beaver this morning
  (Thursday Jan 11/18).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu3
  ProcVersionSignature: Ubuntu 4.14.0-16.19-generic 4.14.12
  Uname: Linux 4.14.0-16-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D11p', 
'/dev/snd/pcmC1D10p', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', 
'/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: GNOME
  Date: Thu Jan 11 13:32:21 2018
  InstallationDate: Installed on 2017-12-20 (21 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1401
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97 LE R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1401:bd12/12/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97LER2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1742769/+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 1718824] Re: The analogue audio does not work on the Dell USB Dock

[Daniel van Vugt]

And verification failed. See bug 1742750 now.

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

Title:
  The analogue audio does not work on the Dell USB Dock

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  Triaged
Status in pulseaudio package in Ubuntu:
  In Progress
Status in pulseaudio source package in Xenial:
  New
Status in pulseaudio source package in Artful:
  New

Bug description:
  SRU Document:

  [Impact]

  If users use the latest Dell USB Dock, e.g. TB16, they will found the
  analog audio (lineout jack) can't work under ubuntu linux

  [Test Case]

  After applying the fix, users can play sound via analog speaker or
  lineout freely. Without the fix, users can't play sound from lineout
  jack.

  [Regression Potential]

  No any possibility to introduce regression since this fix just adding
  a new dock's support, it does not change any existing code.

  [Other Info]

  No more info here

  Steps:
  1. Cold boot system with BME/IE connected
  2. Plug in a speaker to Line-out jack
  3. Set Analog Stereo Output from Sound settings

  Expected results: Line-out port can work

  Actual results: Line-out port not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1718824/+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 1742750] Re: Pulseaudio 1:11.1-1ubuntu3 will not start due to invalid /etc/pulse/default.pa file

[Daniel van Vugt]

Thanks for that. I recall fixing that typo already but somehow that fix
got lost.

** Changed in: pulseaudio (Ubuntu)
   Importance: Undecided => Critical

** Changed in: pulseaudio (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

** Changed in: pulseaudio (Ubuntu)
   Status: New => In Progress

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

Title:
  Pulseaudio 1:11.1-1ubuntu3 will not start due to invalid
  /etc/pulse/default.pa file

Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  Version 1:11.1-1ubuntu3 added 0030-load-module-switch-on-
  connect.patch, which changes line 38 of /etc/pulse/default.pa to read
  ".endif### Load audio drivers statically".  It appears that there are
  a couple of line feeds missing here, and having the comment on the
  same line as the endif causes pulseaudio not to start.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1742750/+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 1732629] Re: Selecting USB Amp/Dac audio output in gnome sound does nothing

[Daniel van Vugt]

It has to be fixed in 18.04 first. And after that it may get backported
to 17.10 only if people can confirm the fix is helping them. I would
love to get feedback from more users on that -- it seemed to not make
any difference for me when I tried it.

Bionic users will have the fix soon at least:
https://launchpad.net/ubuntu/+source/pulseaudio/1:11.1-1ubuntu3

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

Title:
  Selecting USB Amp/Dac audio output in gnome sound does nothing

Status in pulseaudio package in Ubuntu:
  In Progress

Bug description:
  Running Ubuntu 17.10, when I plug an external USB Amp/Dac it is
  correctly recognized and I can play audio through it via aplay, but
  when I select it as my output sink from gnome sound, nothing happens:
  apps still output sound via the speakers.

  In order to fix it I have to restart pulseaudio.
  I've also found online that modifying /etc/pulse/default.pa, moving 
module-switch-on-connect.so loading before module-udev-detect.so, permanently 
fixes the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: pulseaudio 1:10.0-2ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC1D0p:   sergio 1374 F...m pulseaudio
   /dev/snd/controlC1:  sergio 1374 F pulseaudio
   /dev/snd/controlC0:  sergio 1374 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov 16 09:03:19 2017
  InstallationDate: Installed on 2017-10-24 (22 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170926)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.4
  dmi.board.name: 0X41RR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.4:bd06/08/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0X41RR:rvrA02:cvnDellInc.:ct10:cvr:
  dmi.product.family: Precision
  dmi.product.name: Precision 5520
  dmi.sys.vendor: Dell Inc.
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2017-11-15T18:42:36.359190

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1732629/+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 1739931] Re: Separator lines in shell popup menus are too faint to see

[Daniel van Vugt]

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

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Status: New => Confirmed

** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu)
   Importance: Undecided => Low

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

Title:
  Separator lines in shell popup menus are too faint to see

Status in Ubuntu theme:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Confirmed

Bug description:
  when I click on the dock icons, some of the lines in the popup menus
  are blank and some of them appear to be incorrect. see top left of
  attached screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nautilus 1:3.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Dec 23 22:24:40 2017
  InstallationDate: Installed on 2016-08-18 (492 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-themes/+bug/1739931/+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 1727401] Re: Corruption on windowed 3D apps running on dGPU (Intel/AMD)

[Yuan-Chen Cheng]

** Changed in: oem-priority
   Status: Fix Released => Triaged

** Changed in: oem-priority
 Assignee: (unassigned) => ethan.hsieh (ethan.hsieh)

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

Title:
  Corruption on windowed 3D apps running on dGPU (Intel/AMD)

Status in Mesa:
  In Progress
Status in OEM Priority Project:
  Triaged
Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa source package in Xenial:
  Fix Committed
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  [Impact]

  Corruption is seen on windowed 3D apps running on dGPU

  [Test case]

  Get a certain Intel/AMD hybrid machine, run 'DRI_PRIME=1 glxgears',
  see how the window has corrupted gfx.

  The fix is to patch Intel i965_dri driver.

  [Regression potential]

  There could be a slight loss of performance, but corruption free
  behaviour.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1727401/+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 1718824] Re: The analogue audio does not work on the Dell USB Dock

[Daniel van Vugt]

Thanks Timo.

Hui: It's now in bionic-proposed. Can you test it with the Dell dock?

https://launchpad.net/ubuntu/+source/pulseaudio/1:11.1-1ubuntu3

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

Title:
  The analogue audio does not work on the Dell USB Dock

Status in HWE Next:
  In Progress
Status in OEM Priority Project:
  Triaged
Status in pulseaudio package in Ubuntu:
  In Progress
Status in pulseaudio source package in Xenial:
  New
Status in pulseaudio source package in Artful:
  New

Bug description:
  SRU Document:

  [Impact]

  If users use the latest Dell USB Dock, e.g. TB16, they will found the
  analog audio (lineout jack) can't work under ubuntu linux

  [Test Case]

  After applying the fix, users can play sound via analog speaker or
  lineout freely. Without the fix, users can't play sound from lineout
  jack.

  [Regression Potential]

  No any possibility to introduce regression since this fix just adding
  a new dock's support, it does not change any existing code.

  [Other Info]

  No more info here

  Steps:
  1. Cold boot system with BME/IE connected
  2. Plug in a speaker to Line-out jack
  3. Set Analog Stereo Output from Sound settings

  Expected results: Line-out port can work

  Actual results: Line-out port not work

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1718824/+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 1735594] Re: [regression] compiz crashes after Mesa upgrade

[Timo Aaltonen]

you need to ppa-purge all extra ppa's, and then try again

or just run 'sudo apt update && apt upgrade' after enabling -proposed,
that should work on top of my ppa (but not padoka's, since it has 17.3)

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

Title:
  [regression] compiz crashes after Mesa upgrade

Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa source package in Xenial:
  Fix Committed
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  When I use the Unity session I automatically get logged out under these 
conditions:

  When I hover with my mouse over any icon of the sidebar.
  When I press the alt key.
  When I press the super key.

  running dmesg after this unwanted logout happens I get following
  information:

  compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0
  error 4 in i965_dri.so[7fbca2af6000+7e4000]

  This is caused by a mesa upgrade, which added a patch for bug #1727401. The 
crasher is reproduced on:
  - gen4 / gen5 Intel
  - if using modesetting X driver, like when xserver-xorg-video-intel is not 
installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults 
to modesetting)

  [Test case]
  Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash.

  [Regression potential]
  The backported patches need to be tested, here for regressions and on 1727401 
that they fix the original bug (again).

  Best to test on a wide array of Intel HW:
  gen4 (965GM/GM45/G45)
  gen5 (Ironlake)
  gen6 (Sandy Bridge)
  gen7 (Bay Trail, Ivy Bridge, Haswell)
  gen8 (Braswell, Broadwell)
  gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594/+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 1742815] [NEW] package libpng12-0 1.2.54-1ubuntu1 [modified: usr/share/doc/libpng12-0/ANNOUNCE usr/share/doc/libpng12-0/KNOWNBUG usr/share/doc/libpng12-0/README.gz usr/share/doc/

[Ceyhan Genc]

Public bug reported:

After booting and trying to manual search for updates. Quite before, had
troubles in installing radeongpu-pro drivers (17.50) and Vulkan SDK
1.0.65.0. They work now, but I don't know how many apps I looked and
installed getting DaVinci Resolve 14 and Tomb Raider (2013) work again.
All other games and stuff work (like CS Go and Black Mesa and other 3D-
Software).

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libpng12-0 1.2.54-1ubuntu1 [modified: 
usr/share/doc/libpng12-0/ANNOUNCE usr/share/doc/libpng12-0/KNOWNBUG 
usr/share/doc/libpng12-0/README.gz usr/share/doc/libpng12-0/changelog.Debian.gz]
ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
Uname: Linux 4.13.0-26-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
AptOrdering:
 libpng12-0: Install
 libpng12-0: Configure
 libpng12-0: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Fri Jan 12 00:09:25 2018
Dependencies:
 gcc-6-base 6.0.1-0ubuntu1
 libc6 2.23-0ubuntu9
 libgcc1 1:6.0.1-0ubuntu1
 zlib1g 1:1.2.8.dfsg-2ubuntu4.1
DpkgTerminalLog:
 Vorbereitung zum Entpacken von .../libpng12-0_1.2.54-1ubuntu1_i386.deb ...
 Entpacken von libpng12-0:i386 (1.2.54-1ubuntu1) über (1.2.50-2+deb8u3) ...
 dpkg: Fehler beim Bearbeiten des Archivs 
/var/cache/apt/archives/libpng12-0_1.2.54-1ubuntu1_i386.deb (--unpack):
  Versuch, gemeinsam benutztes »/usr/share/doc/libpng12-0/KNOWNBUG« zu 
überschreiben, welches verschieden von anderen Instanzen des Paketes 
libpng12-0:i386 ist
ErrorMessage: Versuch, gemeinsam benutztes »/usr/share/doc/libpng12-0/KNOWNBUG« 
zu überschreiben, welches verschieden von anderen Instanzen des Paketes 
libpng12-0:i386 ist
InstallationDate: Installed on 2017-11-24 (48 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.24
SourcePackage: libpng
Title: package libpng12-0 1.2.54-1ubuntu1 [modified: 
usr/share/doc/libpng12-0/ANNOUNCE usr/share/doc/libpng12-0/KNOWNBUG 
usr/share/doc/libpng12-0/README.gz 
usr/share/doc/libpng12-0/changelog.Debian.gz] failed to install/upgrade: 
Versuch, gemeinsam benutztes »/usr/share/doc/libpng12-0/KNOWNBUG« zu 
überschreiben, welches verschieden von anderen Instanzen des Paketes 
libpng12-0:i386 ist
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package libpng12-0 1.2.54-1ubuntu1 [modified:
  usr/share/doc/libpng12-0/ANNOUNCE usr/share/doc/libpng12-0/KNOWNBUG
  usr/share/doc/libpng12-0/README.gz
  usr/share/doc/libpng12-0/changelog.Debian.gz] failed to
  install/upgrade: Versuch, gemeinsam benutztes
  »/usr/share/doc/libpng12-0/KNOWNBUG« zu überschreiben, welches
  verschieden von anderen Instanzen des Paketes libpng12-0:i386 ist

Status in libpng package in Ubuntu:
  New

Bug description:
  After booting and trying to manual search for updates. Quite before,
  had troubles in installing radeongpu-pro drivers (17.50) and Vulkan
  SDK 1.0.65.0. They work now, but I don't know how many apps I looked
  and installed getting DaVinci Resolve 14 and Tomb Raider (2013) work
  again. All other games and stuff work (like CS Go and Black Mesa and
  other 3D-Software).

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libpng12-0 1.2.54-1ubuntu1 [modified: 
usr/share/doc/libpng12-0/ANNOUNCE usr/share/doc/libpng12-0/KNOWNBUG 
usr/share/doc/libpng12-0/README.gz usr/share/doc/libpng12-0/changelog.Debian.gz]
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  AptOrdering:
   libpng12-0: Install
   libpng12-0: Configure
   libpng12-0: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Fri Jan 12 00:09:25 2018
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu9
   libgcc1 1:6.0.1-0ubuntu1
   zlib1g 1:1.2.8.dfsg-2ubuntu4.1
  DpkgTerminalLog:
   Vorbereitung zum Entpacken von .../libpng12-0_1.2.54-1ubuntu1_i386.deb ...
   Entpacken von libpng12-0:i386 (1.2.54-1ubuntu1) über (1.2.50-2+deb8u3) ...
   dpkg: Fehler beim Bearbeiten des Archivs 
/var/cache/apt/archives/libpng12-0_1.2.54-1ubuntu1_i386.deb (--unpack):
Versuch, gemeinsam benutztes »/usr/share/doc/libpng12-0/KNOWNBUG« zu 
überschreiben, welches verschieden von anderen Instanzen des Paketes 
libpng12-0:i386 ist
  ErrorMessage: Versuch, gemeinsam benutztes 
»/usr/share/doc/libpng12-0/KNOWNBUG« zu überschreiben, welches verschieden von 
anderen Instanzen des Paketes libpng12-0:i386 ist
  InstallationDate: Installed on 2017-11-24 (48 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   

[Touch-packages] [Bug 1735594] Re: [regression] compiz crashes after Mesa upgrade

[MeanJim]

I'm affected by this bug as well.  I tried the -proposed package, but
I'm getting the same error as Emmanuel Grumbach pasted above.

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

Title:
  [regression] compiz crashes after Mesa upgrade

Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa source package in Xenial:
  Fix Committed
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  When I use the Unity session I automatically get logged out under these 
conditions:

  When I hover with my mouse over any icon of the sidebar.
  When I press the alt key.
  When I press the super key.

  running dmesg after this unwanted logout happens I get following
  information:

  compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0
  error 4 in i965_dri.so[7fbca2af6000+7e4000]

  This is caused by a mesa upgrade, which added a patch for bug #1727401. The 
crasher is reproduced on:
  - gen4 / gen5 Intel
  - if using modesetting X driver, like when xserver-xorg-video-intel is not 
installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults 
to modesetting)

  [Test case]
  Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash.

  [Regression potential]
  The backported patches need to be tested, here for regressions and on 1727401 
that they fix the original bug (again).

  Best to test on a wide array of Intel HW:
  gen4 (965GM/GM45/G45)
  gen5 (Ironlake)
  gen6 (Sandy Bridge)
  gen7 (Bay Trail, Ivy Bridge, Haswell)
  gen8 (Braswell, Broadwell)
  gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594/+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 1741447] Re: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04

[Leo Pilachowski]

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

Thanks.  I saw that and that the comment on the "fix" was entered 8
minutes after my post above. But, I see there may be dependency problems
installing that fix.

LP

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

Title:
  Unity / Compiz in a crash loop after login, after mesa updates of
  2018-01-04

Status in Mesa:
  New
Status in mesa package in Ubuntu:
  Confirmed
Status in mesa source package in Xenial:
  Confirmed
Status in mesa source package in Artful:
  Confirmed

Bug description:
  GUI is constantly crashing, can't start desktop

  Jan  5 11:21:29 1810 kernel: [  806.368754] compiz[10824]: segfault at 0 ip 
7f83c4f31c16 sp 7ffd48dfc2f0 error 4 in i965_dri.so[7f83c4954000+82d000]
  Jan  5 11:21:40 1810 kernel: [  817.279740] compiz[1]: segfault at 0 ip 
7fda21519c16 sp 7ffd7b40a150 error 4 in i965_dri.so[7fda20f3c000+82d000]
  Jan  5 11:22:30 1810 kernel: [  867.445137] compiz[11271]: segfault at 0 ip 
7f8462855c16 sp 7fff07c857f0 error 4 in i965_dri.so[7f8462278000+82d000]
  Jan  5 11:22:46 1810 kernel: [  883.319195] compiz[11458]: segfault at 0 ip 
7f72b7af0c16 sp 7ffc3b92d830 error 4 in i965_dri.so[7f72b7513000+82d000]
  Jan  5 11:23:01 1810 kernel: [  898.587610] compiz[11516]: segfault at 0 ip 
7fe25113dc16 sp 7ffcf79754c0 error 4 in i965_dri.so[7fe250b6+82d000]

  In /var/crash:
  _usr_bin_compiz.999.crash

  Did manage to start a GUI in Low graphics mode (lowgfx.conf) but this is not 
really usable.
  - dash not working
  - no window switching
  - sometimes all windows disappear for a few seconds

  So effectively my laptop is not usable after latest updates.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity 7.4.0+16.04.20160906-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  .tmp.unity_support_test.0:

  .tmp.unity_support_test.1:

  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Jan  5 11:16:53 2018
  DistUpgraded: 2016-04-22 18:36:32,349 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
     Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:029b]
     Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:029b]
  InstallationDate: Installed on 2014-04-18 (1357 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Acer Aspire 1810TZ
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic 
root=UUID=86d7d9a6-ffc3-47cb-adc4-68cfcbcadcef ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (622 days ago)
  dmi.bios.date: 08/31/2010
  dmi.bios.vendor: INSYDE
  dmi.bios.version: v1.3314
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JM11-MS
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 1
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvrv1.3314:bd08/31/2010:svnAcer:pnAspire1810TZ:pvrv1.3314:rvnAcer:rnJM11-MS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
  dmi.product.name: Aspire 1810TZ
  dmi.product.version: v1.3314
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Fri Jan  5 11:14:24 2018
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

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

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

[Touch-packages] [Bug 1742733] Re: Display Bug

[Timo Aaltonen]

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

** This bug has been marked a duplicate of bug 1735594
   [regression] compiz crashes after Mesa upgrade

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

Title:
  Display Bug

Status in xorg package in Ubuntu:
  New

Bug description:
  When I attempt to use the launcher it will disappear as well as
  everything else on the screen. It comes back after a few seconds, but
  I am unable to use the dash search at all. If I mouse over the icon
  for the search it immediately makes all windows, icons and launcher
  disappear. I am unable to power off my computer as well. When I click
  shut down it does the same thing as trying to click the search option.
  It never did this until the recent most recent updates.

  Ubuntu 16.04.3 LTS
  Panasonic Toughbook CF-52 Laptop

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Jan 11 11:09:31 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Matsushita Electric Industrial Co., Ltd. Mobile 4 Series 
Chipset Integrated Graphics Controller [10f7:8338]
 Subsystem: Matsushita Electric Industrial Co., Ltd. Mobile 4 Series 
Chipset Integrated Graphics Controller [10f7:8338]
  InstallationDate: Installed on 2017-12-03 (38 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Matsushita Electric Industrial Co.,Ltd. CF-52GCMBXAM
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-26-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/11/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.50L16
  dmi.board.name: CF52-2L
  dmi.board.vendor: Matsushita Electric Industrial Co.,Ltd.
  dmi.board.version: 1
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Matsushita Electric Industrial Co.,Ltd.
  dmi.chassis.version: 001
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.50L16:bd08/11/2008:svnMatsushitaElectricIndustrialCo.,Ltd.:pnCF-52GCMBXAM:pvr002:rvnMatsushitaElectricIndustrialCo.,Ltd.:rnCF52-2L:rvr1:cvnMatsushitaElectricIndustrialCo.,Ltd.:ct10:cvr001:
  dmi.product.family: CF52-2L
  dmi.product.name: CF-52GCMBXAM
  dmi.product.version: 002
  dmi.sys.vendor: Matsushita Electric Industrial Co.,Ltd.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Thu Jan 11 07:56:31 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1742733/+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 1693056] Re: do-release-upgrade hangs at The user 'syslog' is already a member of 'adm' every single time

[Benedikt Tröster]

Ok, I got it:
1. purge rsyslog with: "sudo apt purge rsyslog"
2. Install the new distro with either "sudo apt dist-upgrade" or 
"do-release-upgrade"
3. I had one error in the first run of do-release-upgrade, I just re-ran it and 
now it went through and I'm on 17.04...profit?

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

Title:
   do-release-upgrade hangs at The user 'syslog' is already a member of
  'adm' every single time

Status in rsyslog package in Ubuntu:
  New

Bug description:
  Uuntu 15.10

  > $ sudo apt-cache policy rsyslog

  > rsyslog:
  >   Installed: 8.12.0-1ubuntu2
  >   Candidate: 8.12.0-1ubuntu2
  >   Version table:
  >  *** 8.12.0-1ubuntu2 0
  > 500 http://ubuntu-archive.mirror.serveriai.lt/ubuntu/ wily/main 
amd64 Packages
  > 100 /var/lib/dpkg/status

  
  Whenever I try to run any command that is to reinstall/fix rsylog or try to 
upgrade my Ubuntu server (by running `do-release-upgrade`) it ends in:

  > Reading cache
  > 
  > Checking package manager
  > 
  > Setting up rsyslog (8.12.0-1ubuntu2)  ...

  > The user 'syslog' is already a member of 'adm'.

  Because of this I am locked on **Ubuntu 15.10**.

  **Note**: I started getting this error after I upgraded from `15.04`
  when system was setting up after upgrade to `15.10`. I was asked to
  choose version and it said `N` for default or existing version and I
  went for it.

  What I expect: To peacefully upgrade my VPS Ubuntu version to 16.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1693056/+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 1742804] [NEW] Kubuntu: Failed to add PIDs to scope's control group

[Peter Eszlari]

Public bug reported:

When I launch applications with flatpak, "journalctl -f" shows the
following:

Jan 11 22:44:13 localhost systemd[1244]: flatpak-org.kde.krita-8134.scope: 
Failed to add PIDs to scope's control group: Permission denied
Jan 11 22:44:13 localhost systemd[1244]: Failed to start 
flatpak-org.kde.krita-8134.scope.
Jan 11 22:44:13 localhost systemd[1244]: flatpak-org.kde.krita-8134.scope: Unit 
entered failed state.

I explicitly mentioned "Kubuntu" in the summary, because I experience
this only under Kubuntu (17.10 and 18.04), NOT under the regular Gnome-
based Ubuntu Desktop (17.10). At first this error message seemed
harmless, because it looked like it had no effect. But now I noticed
that with certain flatpak apps, the file open dialog would not pop up.
And I too experienced this only under Kubuntu, not Ubuntu or Fedora (all
tested). So there might be a connection.

I first reported this to flatpak:

https://github.com/flatpak/flatpak/issues/1216

There it was suggested to try the following command:

$ systemd-run --user --scope echo hello
Job for run-r150c7437bf8a4c5e919acbbc3de0b29c.scope failed.
See "systemctl status run-r150c7437bf8a4c5e919acbbc3de0b29c.scope" and 
"journalctl -xe" for details.

...and this one also fails.

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


** Tags: flatpak kubuntu systemd

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

Title:
  Kubuntu: Failed to add PIDs to scope's control group

Status in systemd package in Ubuntu:
  New

Bug description:
  When I launch applications with flatpak, "journalctl -f" shows the
  following:

  Jan 11 22:44:13 localhost systemd[1244]: flatpak-org.kde.krita-8134.scope: 
Failed to add PIDs to scope's control group: Permission denied
  Jan 11 22:44:13 localhost systemd[1244]: Failed to start 
flatpak-org.kde.krita-8134.scope.
  Jan 11 22:44:13 localhost systemd[1244]: flatpak-org.kde.krita-8134.scope: 
Unit entered failed state.

  I explicitly mentioned "Kubuntu" in the summary, because I experience
  this only under Kubuntu (17.10 and 18.04), NOT under the regular
  Gnome-based Ubuntu Desktop (17.10). At first this error message seemed
  harmless, because it looked like it had no effect. But now I noticed
  that with certain flatpak apps, the file open dialog would not pop up.
  And I too experienced this only under Kubuntu, not Ubuntu or Fedora
  (all tested). So there might be a connection.

  I first reported this to flatpak:

  https://github.com/flatpak/flatpak/issues/1216

  There it was suggested to try the following command:

  $ systemd-run --user --scope echo hello
  Job for run-r150c7437bf8a4c5e919acbbc3de0b29c.scope failed.
  See "systemctl status run-r150c7437bf8a4c5e919acbbc3de0b29c.scope" and 
"journalctl -xe" for details.

  ...and this one also fails.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1742804/+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 1693056] Re: do-release-upgrade hangs at The user 'syslog' is already a member of 'adm' every single time

[Benedikt Tröster]

I have the same issue, but instead of "N" I chose "Y" (to replace
rsyslog), which failed as well

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

Title:
   do-release-upgrade hangs at The user 'syslog' is already a member of
  'adm' every single time

Status in rsyslog package in Ubuntu:
  New

Bug description:
  Uuntu 15.10

  > $ sudo apt-cache policy rsyslog

  > rsyslog:
  >   Installed: 8.12.0-1ubuntu2
  >   Candidate: 8.12.0-1ubuntu2
  >   Version table:
  >  *** 8.12.0-1ubuntu2 0
  > 500 http://ubuntu-archive.mirror.serveriai.lt/ubuntu/ wily/main 
amd64 Packages
  > 100 /var/lib/dpkg/status

  
  Whenever I try to run any command that is to reinstall/fix rsylog or try to 
upgrade my Ubuntu server (by running `do-release-upgrade`) it ends in:

  > Reading cache
  > 
  > Checking package manager
  > 
  > Setting up rsyslog (8.12.0-1ubuntu2)  ...

  > The user 'syslog' is already a member of 'adm'.

  Because of this I am locked on **Ubuntu 15.10**.

  **Note**: I started getting this error after I upgraded from `15.04`
  when system was setting up after upgrade to `15.10`. I was asked to
  choose version and it said `N` for default or existing version and I
  went for it.

  What I expect: To peacefully upgrade my VPS Ubuntu version to 16.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1693056/+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 1742801] [NEW] [HDA-Intel - HDA NVidia, playback] No sound at all

[Salam]

Public bug reported:

the device is well connected and I am hearing the noise of the speakers
they do when they are connected but if open a youtube or a site to learn
a language that uses the sound ,there is no sound at all,even when I
open the system setting and make a test of the sound all it seems
function well but no sound

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
Uname: Linux 4.13.0-26-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  theseer9   2534 F pulseaudio
CurrentDesktop: Unity
Date: Thu Jan 11 22:45:44 2018
InstallationDate: Installed on 2018-01-05 (6 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed
Symptom_Card: Built-in Audio - HDA NVidia
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  theseer9   2534 F pulseaudio
Symptom_Type: No sound at all
Title: [HDA-Intel - HDA NVidia, playback] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/20/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: PBCBR00.P27
dmi.board.vendor: Packard Bell BV
dmi.board.version: 1.0
dmi.chassis.type: 3
dmi.chassis.vendor: Packard Bell BV
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrPBCBR00.P27:bd11/20/2008:svnPackardBellBV:pnIMEDIAA3507SP:pvrPTU080Y005:rvnPackardBellBV:rn:rvr1.0:cvnPackardBellBV:ct3:cvr1.0:
dmi.product.name: IMEDIA A3507 SP
dmi.product.version: PTU080Y005
dmi.sys.vendor: Packard Bell BV

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


** Tags: amd64 apport-bug xenial

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

Title:
  [HDA-Intel - HDA NVidia, playback] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  the device is well connected and I am hearing the noise of the
  speakers they do when they are connected but if open a youtube or a
  site to learn a language that uses the sound ,there is no sound at
  all,even when I open the system setting and make a test of the sound
  all it seems function well but no sound

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  theseer9   2534 F pulseaudio
  CurrentDesktop: Unity
  Date: Thu Jan 11 22:45:44 2018
  InstallationDate: Installed on 2018-01-05 (6 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed
  Symptom_Card: Built-in Audio - HDA NVidia
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  theseer9   2534 F pulseaudio
  Symptom_Type: No sound at all
  Title: [HDA-Intel - HDA NVidia, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/20/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: PBCBR00.P27
  dmi.board.vendor: Packard Bell BV
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.vendor: Packard Bell BV
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrPBCBR00.P27:bd11/20/2008:svnPackardBellBV:pnIMEDIAA3507SP:pvrPTU080Y005:rvnPackardBellBV:rn:rvr1.0:cvnPackardBellBV:ct3:cvr1.0:
  dmi.product.name: IMEDIA A3507 SP
  dmi.product.version: PTU080Y005
  dmi.sys.vendor: Packard Bell BV

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1742801/+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 1735594] Re: [regression] compiz crashes after Mesa upgrade

[Emmanuel Grumbach]

$ sudo apt-get install libgl1-mesa-dri/xenial-proposed
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Selected version '17.2.4-0ubuntu1~16.04.3' (Ubuntu:16.04/xenial-proposed 
[amd64]) for 'libgl1-mesa-dri'
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 indicator-bluetooth : Depends: unity-control-center but it is not going to be 
installed or
gnome-control-center but it is not going to be 
installed or
ubuntu-system-settings but it is not going to 
be installed
   Depends: gnome-bluetooth but it is not going to be 
installed or
ubuntu-system-settings but it is not going to 
be installed
 liboxideqt-qmlplugin : Depends: libqt5quick5 (>= 5.0.2) but it is not going to 
be installed or
 libqt5quick5-gles (>= 5.0.2) but it is not 
going to be installed
 liboxideqtcore0 : Depends: libqt5gui5 (>= 5.4.0) but it is not going to be 
installed or
libqt5gui5-gles (>= 5.4.0) but it is not going to 
be installed
 liboxideqtquick0 : Depends: libqt5gui5 (>= 5.0.2) but it is not going to be 
installed or
 libqt5gui5-gles (>= 5.0.2) but it is not going to 
be installed
Depends: libqt5quick5 (>= 5.2.0) but it is not going to be 
installed or
 libqt5quick5-gles (>= 5.2.0) but it is not going 
to be installed
 libqmenumodel0 : Depends: libqt5gui5 (>= 5.0.2) but it is not going to be 
installed or
   libqt5gui5-gles (>= 5.0.2) but it is not going to be 
installed
 libqt5multimedia5 : Depends: libqt5gui5 (>= 5.2.0) but it is not going to be 
installed or
  libqt5gui5-gles (>= 5.2.0) but it is not going to 
be installed
 libqt5multimediaquick-p5 : Depends: libqt5gui5 (>= 5.0.2) but it is not going 
to be installed or
 libqt5gui5-gles (>= 5.0.2) but it is not 
going to be installed
Depends: libqt5quick5 (>= 5.4.0) but it is not 
going to be installed or
 libqt5quick5-gles (>= 5.4.0) but it is not 
going to be installed
 libqt5widgets5 : Depends: libqt5gui5 (>= 5.5.0) but it is not going to be 
installed or
   libqt5gui5-gles (>= 5.5.0) but it is not going to be 
installed
 libubuntugestures5 : Depends: libqt5gui5 (>= 5.0.2) but it is not going to be 
installed or
   libqt5gui5-gles (>= 5.0.2) but it is not going 
to be installed
  Depends: libqt5quick5 (>= 5.0.2) but it is not going to 
be installed or
   libqt5quick5-gles (>= 5.0.2) but it is not going 
to be installed
 libubuntutoolkit5 : Depends: libqt5gui5 (>= 5.0.2) but it is not going to be 
installed or
  libqt5gui5-gles (>= 5.0.2) but it is not going to 
be installed
 qml-module-io-thp-pyotherside : Depends: libqt5gui5 (>= 5.0.2) but it is not 
going to be installed or
  libqt5gui5-gles (>= 5.0.2) but it is 
not going to be installed
 Depends: libqt5quick5 (>= 5.0.2) but it is not 
going to be installed or
  libqt5quick5-gles (>= 5.0.2) but it 
is not going to be installed
 qml-module-qtquick-layouts : Depends: libqt5gui5 (>= 5.5.0) but it is not 
going to be installed or
   libqt5gui5-gles (>= 5.5.0) but it is not 
going to be installed
  Depends: libqt5quick5 (>= 5.2.0) but it is not 
going to be installed or
   libqt5quick5-gles (>= 5.2.0) but it is 
not going to be installed
 qml-module-qtquick-window2 : Depends: libqt5quick5 (>= 5.0.2) but it is not 
going to be installed or
   libqt5quick5-gles (>= 5.0.2) but it is 
not going to be installed
 qml-module-ubuntu-layouts : Depends: libqt5quick5 (>= 5.0.2) but it is not 
going to be installed or
  libqt5quick5-gles (>= 5.0.2) but it is 
not going to be installed
 qml-module-ubuntu-performancemetrics : Depends: libqt5gui5 (>= 5.0.2) but it 
is not going to be installed or
 libqt5gui5-gles (>= 5.0.2) but 
it is not going to be installed
Depends: libqt5quick5 (>= 5.0.2) but it 
is not going to be installed or
 libqt5quick5-gles (>= 5.0.2) 
but it is 

[Touch-packages] [Bug 1735594] Re: [regression] compiz crashes after Mesa upgrade

[Timo Aaltonen]

your mirror hasn't been synced yet, use archive.ubuntu.com in the
meantime

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

Title:
  [regression] compiz crashes after Mesa upgrade

Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa source package in Xenial:
  Fix Committed
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  When I use the Unity session I automatically get logged out under these 
conditions:

  When I hover with my mouse over any icon of the sidebar.
  When I press the alt key.
  When I press the super key.

  running dmesg after this unwanted logout happens I get following
  information:

  compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0
  error 4 in i965_dri.so[7fbca2af6000+7e4000]

  This is caused by a mesa upgrade, which added a patch for bug #1727401. The 
crasher is reproduced on:
  - gen4 / gen5 Intel
  - if using modesetting X driver, like when xserver-xorg-video-intel is not 
installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults 
to modesetting)

  [Test case]
  Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash.

  [Regression potential]
  The backported patches need to be tested, here for regressions and on 1727401 
that they fix the original bug (again).

  Best to test on a wide array of Intel HW:
  gen4 (965GM/GM45/G45)
  gen5 (Ironlake)
  gen6 (Sandy Bridge)
  gen7 (Bay Trail, Ivy Bridge, Haswell)
  gen8 (Braswell, Broadwell)
  gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594/+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 1735594] Re: [regression] compiz crashes after Mesa upgrade

[Emmanuel Grumbach]

$ sudo apt-get install libgl1-mesa-dri/xenial-proposed
Reading package lists... Done
Building dependency tree   
Reading state information... Done
E: Release 'xenial-proposed' for 'libgl1-mesa-dri' was not found

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

Title:
  [regression] compiz crashes after Mesa upgrade

Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa source package in Xenial:
  Fix Committed
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  When I use the Unity session I automatically get logged out under these 
conditions:

  When I hover with my mouse over any icon of the sidebar.
  When I press the alt key.
  When I press the super key.

  running dmesg after this unwanted logout happens I get following
  information:

  compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0
  error 4 in i965_dri.so[7fbca2af6000+7e4000]

  This is caused by a mesa upgrade, which added a patch for bug #1727401. The 
crasher is reproduced on:
  - gen4 / gen5 Intel
  - if using modesetting X driver, like when xserver-xorg-video-intel is not 
installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults 
to modesetting)

  [Test case]
  Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash.

  [Regression potential]
  The backported patches need to be tested, here for regressions and on 1727401 
that they fix the original bug (again).

  Best to test on a wide array of Intel HW:
  gen4 (965GM/GM45/G45)
  gen5 (Ironlake)
  gen6 (Sandy Bridge)
  gen7 (Bay Trail, Ivy Bridge, Haswell)
  gen8 (Braswell, Broadwell)
  gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594/+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 1735594] Re: [regression] compiz crashes after Mesa upgrade

[Timo Aaltonen]

"mesa" is the source package, try "sudo apt install libgl1-mesa-dri"...
that should pull everything

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

Title:
  [regression] compiz crashes after Mesa upgrade

Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa source package in Xenial:
  Fix Committed
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  When I use the Unity session I automatically get logged out under these 
conditions:

  When I hover with my mouse over any icon of the sidebar.
  When I press the alt key.
  When I press the super key.

  running dmesg after this unwanted logout happens I get following
  information:

  compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0
  error 4 in i965_dri.so[7fbca2af6000+7e4000]

  This is caused by a mesa upgrade, which added a patch for bug #1727401. The 
crasher is reproduced on:
  - gen4 / gen5 Intel
  - if using modesetting X driver, like when xserver-xorg-video-intel is not 
installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults 
to modesetting)

  [Test case]
  Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash.

  [Regression potential]
  The backported patches need to be tested, here for regressions and on 1727401 
that they fix the original bug (again).

  Best to test on a wide array of Intel HW:
  gen4 (965GM/GM45/G45)
  gen5 (Ironlake)
  gen6 (Sandy Bridge)
  gen7 (Bay Trail, Ivy Bridge, Haswell)
  gen8 (Braswell, Broadwell)
  gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594/+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 1742790] Re: systemd-journald crashed with SIGABRT in journal_file_append_entry()

[Apport retracing service]

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

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1723134, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1742790/+attachment/5035334/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1742790/+attachment/5035337/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1742790/+attachment/5035345/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1742790/+attachment/5035347/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1742790/+attachment/5035348/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1742790/+attachment/5035349/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1742790/+attachment/5035351/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1723134

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  systemd-journald crashed with SIGABRT in journal_file_append_entry()

Status in systemd package in Ubuntu:
  New

Bug description:
  

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: systemd 235-3ubuntu3
  ProcVersionSignature: Ubuntu 4.14.0-13.15-generic 4.14.7
  Uname: Linux 4.14.0-13-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  Date: Thu Jan 11 21:32:06 2018
  ExecutablePath: /lib/systemd/systemd-journald
  InstallationDate: Installed on 2017-11-29 (43 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171124)
  MachineType: ASUSTeK COMPUTER INC. P552LA
  ProcCmdline: /lib/systemd/systemd-journald
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.14.0-13-generic.efi.signed 
root=UUID=3c54ed2a-0539-4cb2-8efd-1cea27d31b3c ro quiet splash
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   ?? () from /lib/systemd/libsystemd-shared-235.so
   ?? () from /lib/systemd/libsystemd-shared-235.so
   journal_file_append_entry () from /lib/systemd/libsystemd-shared-235.so
   ?? ()
   ?? ()
  Title: systemd-journald crashed with SIGABRT in journal_file_append_entry()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 01/11/2016
  dmi.bios.vendor: ASUSTeK COMPUTER INC.
  dmi.bios.version: P552LA.206
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: P552LA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnASUSTeKCOMPUTERINC.:bvrP552LA.206:bd01/11/2016:svnASUSTeKCOMPUTERINC.:pnP552LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnP552LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: P
  dmi.product.name: P552LA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1742790/+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 1742713] Re: Move mesa-vulkan-drivers from Univers to Main and install by default in Ubuntu 18.04

[Hans Joachim Desserud]

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

** This bug has been marked a duplicate of bug 1742714
   Move mesa-vulkan-drivers from Univers to Main and install by default in 
Ubuntu 18.04

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

Title:
  Move mesa-vulkan-drivers from Univers to Main and install by default
  in Ubuntu 18.04

Status in mesa package in Ubuntu:
  New

Bug description:
  A Vulkan related bug was filed at
  https://bugs.launchpad.net/ubuntu/+source/vulkan/+bug/1742711, but in
  a related note, having mesa-vulkan-drivers moved from Universe to Main
  and installed by default in Ubuntu 18.04 is crucial. Vulkan has gotten
  mature and since the OpenGL drivers are installed, it will very
  complimentary.

  Having this available will aid game developers and users who load up a
  Vulkan application and get errors. They may not know to enable
  Universe in their Software Manager and to manually install mesa-
  vulkan-drivers for their video card. They may just load up that Vulkan
  application, find out it doesn't work, and then give up on it. We
  cannot have that for future adoption of the API.

  Plus, GTK and Qt are adopting Vulkan and applications like Gnome MPV
  are implementing experimental support for Vulkan. For Ubuntu being a
  leader for the desktop and a base for GNU/Linux gaming, shouldn't it
  be painless for Ubuntu 18.04? Especially since it is a long term
  release for 5 years.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1742713/+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 1735594] Re: [regression] compiz crashes after Mesa upgrade

[Emmanuel Grumbach]

I am sorry, but I can't find how to install that package.

I did:

$ sudo apt-get update 
Hit:1 http://il.archive.ubuntu.com/ubuntu xenial InRelease
Hit:2 http://il.archive.ubuntu.com/ubuntu xenial-updates InRelease  

Hit:3 http://il.archive.ubuntu.com/ubuntu xenial-backports InRelease

Hit:4 http://il.archive.ubuntu.com/ubuntu xenial-proposed InRelease 
  
Hit:5 http://security.ubuntu.com/ubuntu xenial-security InRelease   
  
Ign:6 http://linux.dropbox.com/ubuntu xenial InRelease  
 
Ign:7 http://linux.dropbox.com/ubuntu wily InRelease
Hit:8 http://linux.dropbox.com/ubuntu xenial Release
Hit:9 http://linux.dropbox.com/ubuntu wily Release 
Reading package lists... Done  


So clearly, -proposed is there.

And then:
$ sudo apt-get install mesa/xenial-proposed
Reading package lists... Done
Building dependency tree   
Reading state information... Done
E: Unable to locate package mesa


What package exactly should I be looking for?

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

Title:
  [regression] compiz crashes after Mesa upgrade

Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa source package in Xenial:
  Fix Committed
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  When I use the Unity session I automatically get logged out under these 
conditions:

  When I hover with my mouse over any icon of the sidebar.
  When I press the alt key.
  When I press the super key.

  running dmesg after this unwanted logout happens I get following
  information:

  compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0
  error 4 in i965_dri.so[7fbca2af6000+7e4000]

  This is caused by a mesa upgrade, which added a patch for bug #1727401. The 
crasher is reproduced on:
  - gen4 / gen5 Intel
  - if using modesetting X driver, like when xserver-xorg-video-intel is not 
installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults 
to modesetting)

  [Test case]
  Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash.

  [Regression potential]
  The backported patches need to be tested, here for regressions and on 1727401 
that they fix the original bug (again).

  Best to test on a wide array of Intel HW:
  gen4 (965GM/GM45/G45)
  gen5 (Ironlake)
  gen6 (Sandy Bridge)
  gen7 (Bay Trail, Ivy Bridge, Haswell)
  gen8 (Braswell, Broadwell)
  gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594/+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 1741447] Re: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04

[Timo Aaltonen]

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

forget about those ppa's and follow the main bug, a fix has been
uploaded to xenial-proposed already

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

Title:
  Unity / Compiz in a crash loop after login, after mesa updates of
  2018-01-04

Status in Mesa:
  New
Status in mesa package in Ubuntu:
  Confirmed
Status in mesa source package in Xenial:
  Confirmed
Status in mesa source package in Artful:
  Confirmed

Bug description:
  GUI is constantly crashing, can't start desktop

  Jan  5 11:21:29 1810 kernel: [  806.368754] compiz[10824]: segfault at 0 ip 
7f83c4f31c16 sp 7ffd48dfc2f0 error 4 in i965_dri.so[7f83c4954000+82d000]
  Jan  5 11:21:40 1810 kernel: [  817.279740] compiz[1]: segfault at 0 ip 
7fda21519c16 sp 7ffd7b40a150 error 4 in i965_dri.so[7fda20f3c000+82d000]
  Jan  5 11:22:30 1810 kernel: [  867.445137] compiz[11271]: segfault at 0 ip 
7f8462855c16 sp 7fff07c857f0 error 4 in i965_dri.so[7f8462278000+82d000]
  Jan  5 11:22:46 1810 kernel: [  883.319195] compiz[11458]: segfault at 0 ip 
7f72b7af0c16 sp 7ffc3b92d830 error 4 in i965_dri.so[7f72b7513000+82d000]
  Jan  5 11:23:01 1810 kernel: [  898.587610] compiz[11516]: segfault at 0 ip 
7fe25113dc16 sp 7ffcf79754c0 error 4 in i965_dri.so[7fe250b6+82d000]

  In /var/crash:
  _usr_bin_compiz.999.crash

  Did manage to start a GUI in Low graphics mode (lowgfx.conf) but this is not 
really usable.
  - dash not working
  - no window switching
  - sometimes all windows disappear for a few seconds

  So effectively my laptop is not usable after latest updates.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity 7.4.0+16.04.20160906-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  .tmp.unity_support_test.0:

  .tmp.unity_support_test.1:

  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Jan  5 11:16:53 2018
  DistUpgraded: 2016-04-22 18:36:32,349 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
     Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:029b]
     Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:029b]
  InstallationDate: Installed on 2014-04-18 (1357 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Acer Aspire 1810TZ
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic 
root=UUID=86d7d9a6-ffc3-47cb-adc4-68cfcbcadcef ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (622 days ago)
  dmi.bios.date: 08/31/2010
  dmi.bios.vendor: INSYDE
  dmi.bios.version: v1.3314
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JM11-MS
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 1
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvrv1.3314:bd08/31/2010:svnAcer:pnAspire1810TZ:pvrv1.3314:rvnAcer:rnJM11-MS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
  dmi.product.name: Aspire 1810TZ
  dmi.product.version: v1.3314
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Fri Jan  5 11:14:24 2018
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

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

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

[Touch-packages] [Bug 1742714] Re: Move mesa-vulkan-drivers from Univers to Main and install by default in Ubuntu 18.04

[Launchpad Bug Tracker]

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

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

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

Title:
  Move mesa-vulkan-drivers from Univers to Main and install by default
  in Ubuntu 18.04

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  A Vulkan related bug was filed at
  https://bugs.launchpad.net/ubuntu/+source/vulkan/+bug/1742711, but in
  a related note, having mesa-vulkan-drivers moved from Universe to Main
  and installed by default in Ubuntu 18.04 is crucial. Vulkan has gotten
  mature and since the OpenGL drivers are installed, it will very
  complimentary.

  Having this available will aid game developers and users who load up a
  Vulkan application and get errors. They may not know to enable
  Universe in their Software Manager and to manually install mesa-
  vulkan-drivers for their video card. They may just load up that Vulkan
  application, find out it doesn't work, and then give up on it. We
  cannot have that for future adoption of the API.

  Plus, GTK and Qt are adopting Vulkan and applications like Gnome MPV
  are implementing experimental support for Vulkan. For Ubuntu being a
  leader for the desktop and a base for GNU/Linux gaming, shouldn't it
  be painless for Ubuntu 18.04? Especially since it is a long term
  release for 5 years.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1742714/+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 1742756] Re: [Xubuntu] 3/4 of XFCE and console screen is unreadable

[Pawel Por]

** Description changed:

  After upgrading to kernel 4.13.0-26-generic "3/4" part of screen is
  unreadable. It is both in xorg/xfce and console (ctrl+alt+F1).
  Everything works perfect when I reboot my laptop with older
  4.10.0-42-generic kernel. I'm not sure whether it is Xorg bug or kernel
  graphics driver bug. The unvisible 3/4 part of the screen seems to be
  fully operational. I may open an application window in it and drag it to
  the visible 1/4 part of the screen. Besides the screen display issue the
  system seems to run properly. I was able to report this bug while
- running the 4.13.0-26-generic kernel.
+ running the 4.13.0-26-generic kernel. The laptop is Samsung N130.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Thu Jan 11 18:29:04 2018
  InstallationDate: Installed on 2017-12-18 (24 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 
(20170801)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  [Xubuntu] 3/4 of XFCE and console screen is unreadable

Status in xorg package in Ubuntu:
  New

Bug description:
  After upgrading to kernel 4.13.0-26-generic "3/4" part of screen is
  unreadable. It is both in xorg/xfce and console (ctrl+alt+F1).
  Everything works perfect when I reboot my laptop with older
  4.10.0-42-generic kernel. I'm not sure whether it is Xorg bug or
  kernel graphics driver bug. The unvisible 3/4 part of the screen seems
  to be fully operational. I may open an application window in it and
  drag it to the visible 1/4 part of the screen. Besides the screen
  display issue the system seems to run properly. I was able to report
  this bug while running the 4.13.0-26-generic kernel. The laptop is
  Samsung N130.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Thu Jan 11 18:29:04 2018
  InstallationDate: Installed on 2017-12-18 (24 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 
(20170801)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1742756/+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 1089389] Re: juju bootstrap fail behind a proxy when a gpg key must be imported

[Nate Mara]

I noticed that this problem can be fixed for me if the
GPG_DEFAULT_OPTIONS variable on line 171 of ppa.py is changed. If I add
these two properties to the list, then the problem goes away completely:

"--keyserver-options", "http-proxy=" + os.environ['http_proxy']

Obviously, you would want to check for the existence of this variable
before you just went using it, but it looks like this is the problem.
The PPA library does not forward the HTTP proxy settings along to GPG,
so GPG tries and fails to make a direct connection to the keyserver. Am
I missing something about the way this works, or can we make a similar
change and resolve these proxy issues?

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

Title:
  juju bootstrap fail behind a proxy when a gpg key must be imported

Status in software-properties package in Ubuntu:
  Triaged

Bug description:
  This is related to a Maas environment hosted behind a proxy.

  I'm trying to use 
  juju 0.6.0.1+bzr603-0juju1~precise1

  ubuntu@maas:~$ cat .juju/environments.yaml 
  environments:
mymaas:
  type: maas
  maas-server: 'http://192.168.124.2:80/MAAS'
  maas-oauth: 
'UP5Qay8Nsku8K98fqn:LjhnStY2HjfCeKfvmg:BxA586DWVNPKrT9ASNj9QasMvSPdgavt'
  admin-secret: 'nothing'
  default-series: precise
  juju-origin: ppa

  When juju boostrap, things do not behave as expected on the zookeeper
  node.

  Excerpt from the cloud-init-output.log:

  W: GPG error: http://ppa.launchpad.net precise Release: The following
  signatures couldn't be verified because the public key is not
  available: NO_PUBKEY 376A290EC8068B11

  On the zookeeper node, if i try to apt-add-repository , the needed gpg
  key is not injected, but the scrpit does not return any error code:

  ubuntu@zookeeper:/var/log$ sudo mv 
/etc/apt/sources.list.d/juju-pkgs-precise.list /tmp/
  ubuntu@zookeeper:/var/log$ sudo ls /etc/apt/sources.list.d/
  ubuntu@zookeeper:/var/log$ sudo apt-add-repository ppa:juju/pkgs --yes
  gpg: keyring `/tmp/tmpmlP7VA/secring.gpg' created
  gpg: keyring `/tmp/tmpmlP7VA/pubring.gpg' created
  gpg: requesting key C8068B11 from hkp server keyserver.ubuntu.com
  gpgkeys: key A2EB2DEC0BD7519B7B38BE38376A290EC8068B11 not found on keyserver
  gpg: no valid OpenPGP data found.
  gpg: Total number processed: 0
  recv failed
  ubuntu@zookeeper:/var/log$ echo $?
  0

  Trying to inject key while setting the http_proxy environment variable works 
better:
  ubuntu@zookeeper:/var/log$ sudo http_proxy=http://91.189.90.174:3128/ 
apt-add-repository ppa:juju/pkgs --yes
  gpg: keyring `/tmp/tmp1pAd6X/secring.gpg' created
  gpg: keyring `/tmp/tmp1pAd6X/pubring.gpg' created
  gpg: requesting key C8068B11 from hkp server keyserver.ubuntu.com
  gpg: /tmp/tmp1pAd6X/trustdb.gpg: trustdb created
  gpg: key C8068B11: public key "Launchpad Ensemble PPA" imported
  gpg: Total number processed: 1
  gpg:   imported: 1  (RSA: 1)
  OK
  ubuntu@zookeeper:/var/log$ echo $?
  0

  
  On the zookeeper node,  python-software-properties  is version   0.82.7.3

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: python-software-properties 0.82.7.3
  ProcVersionSignature: Ubuntu 3.2.0-34.53-generic 3.2.33
  Uname: Linux 3.2.0-34-generic x86_64
  ApportVersion: 2.0.1-0ubuntu15
  Architecture: amd64
  Date: Wed Dec 12 14:40:21 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to precise on 2012-05-14 (212 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1089389/+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 1742756] Re: [Xubuntu] 3/4 of XFCE and console screen is unreadable

[Pawel Por]

** Attachment added: "lshw.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1742756/+attachment/5035304/+files/lshw.txt

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

Title:
  [Xubuntu] 3/4 of XFCE and console screen is unreadable

Status in xorg package in Ubuntu:
  New

Bug description:
  After upgrading to kernel 4.13.0-26-generic "3/4" part of screen is
  unreadable. It is both in xorg/xfce and console (ctrl+alt+F1).
  Everything works perfect when I reboot my laptop with older
  4.10.0-42-generic kernel. I'm not sure whether it is Xorg bug or
  kernel graphics driver bug. The unvisible 3/4 part of the screen seems
  to be fully operational. I may open an application window in it and
  drag it to the visible 1/4 part of the screen. Besides the screen
  display issue the system seems to run properly. I was able to report
  this bug while running the 4.13.0-26-generic kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Thu Jan 11 18:29:04 2018
  InstallationDate: Installed on 2017-12-18 (24 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 
(20170801)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1742756/+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 1742756] Re: [Xubuntu] 3/4 of XFCE and console screen is unreadable

[Pawel Por]

** Attachment added: "console.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1742756/+attachment/5035301/+files/console.jpg

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

Title:
  [Xubuntu] 3/4 of XFCE and console screen is unreadable

Status in xorg package in Ubuntu:
  New

Bug description:
  After upgrading to kernel 4.13.0-26-generic "3/4" part of screen is
  unreadable. It is both in xorg/xfce and console (ctrl+alt+F1).
  Everything works perfect when I reboot my laptop with older
  4.10.0-42-generic kernel. I'm not sure whether it is Xorg bug or
  kernel graphics driver bug. The unvisible 3/4 part of the screen seems
  to be fully operational. I may open an application window in it and
  drag it to the visible 1/4 part of the screen. Besides the screen
  display issue the system seems to run properly. I was able to report
  this bug while running the 4.13.0-26-generic kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Thu Jan 11 18:29:04 2018
  InstallationDate: Installed on 2017-12-18 (24 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 
(20170801)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1742756/+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 1742756] Re: [Xubuntu] 3/4 of XFCE and console screen is unreadable

[Pawel Por]

** Attachment added: "lspci-vvv.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1742756/+attachment/5035306/+files/lspci-vvv.txt

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

Title:
  [Xubuntu] 3/4 of XFCE and console screen is unreadable

Status in xorg package in Ubuntu:
  New

Bug description:
  After upgrading to kernel 4.13.0-26-generic "3/4" part of screen is
  unreadable. It is both in xorg/xfce and console (ctrl+alt+F1).
  Everything works perfect when I reboot my laptop with older
  4.10.0-42-generic kernel. I'm not sure whether it is Xorg bug or
  kernel graphics driver bug. The unvisible 3/4 part of the screen seems
  to be fully operational. I may open an application window in it and
  drag it to the visible 1/4 part of the screen. Besides the screen
  display issue the system seems to run properly. I was able to report
  this bug while running the 4.13.0-26-generic kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Thu Jan 11 18:29:04 2018
  InstallationDate: Installed on 2017-12-18 (24 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 
(20170801)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1742756/+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 1742756] Re: [Xubuntu] 3/4 of XFCE and console screen is unreadable

[Pawel Por]

** Attachment added: "lsmod.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1742756/+attachment/5035305/+files/lsmod.txt

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

Title:
  [Xubuntu] 3/4 of XFCE and console screen is unreadable

Status in xorg package in Ubuntu:
  New

Bug description:
  After upgrading to kernel 4.13.0-26-generic "3/4" part of screen is
  unreadable. It is both in xorg/xfce and console (ctrl+alt+F1).
  Everything works perfect when I reboot my laptop with older
  4.10.0-42-generic kernel. I'm not sure whether it is Xorg bug or
  kernel graphics driver bug. The unvisible 3/4 part of the screen seems
  to be fully operational. I may open an application window in it and
  drag it to the visible 1/4 part of the screen. Besides the screen
  display issue the system seems to run properly. I was able to report
  this bug while running the 4.13.0-26-generic kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Thu Jan 11 18:29:04 2018
  InstallationDate: Installed on 2017-12-18 (24 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 
(20170801)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1742756/+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 1742756] Re: [Xubuntu] 3/4 of XFCE and console screen is unreadable

[Pawel Por]

** Attachment added: "xfce.jpg"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1742756/+attachment/5035300/+files/xfce.jpg

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

Title:
  [Xubuntu] 3/4 of XFCE and console screen is unreadable

Status in xorg package in Ubuntu:
  New

Bug description:
  After upgrading to kernel 4.13.0-26-generic "3/4" part of screen is
  unreadable. It is both in xorg/xfce and console (ctrl+alt+F1).
  Everything works perfect when I reboot my laptop with older
  4.10.0-42-generic kernel. I'm not sure whether it is Xorg bug or
  kernel graphics driver bug. The unvisible 3/4 part of the screen seems
  to be fully operational. I may open an application window in it and
  drag it to the visible 1/4 part of the screen. Besides the screen
  display issue the system seems to run properly. I was able to report
  this bug while running the 4.13.0-26-generic kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Thu Jan 11 18:29:04 2018
  InstallationDate: Installed on 2017-12-18 (24 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 
(20170801)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1742756/+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 1742756] Re: [Xubuntu] 3/4 of XFCE and console screen is unreadable

[Pawel Por]

** Attachment added: "dmesg_linux_4.13.0-26-generic.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1742756/+attachment/5035303/+files/dmesg_linux_4.13.0-26-generic.txt

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

Title:
  [Xubuntu] 3/4 of XFCE and console screen is unreadable

Status in xorg package in Ubuntu:
  New

Bug description:
  After upgrading to kernel 4.13.0-26-generic "3/4" part of screen is
  unreadable. It is both in xorg/xfce and console (ctrl+alt+F1).
  Everything works perfect when I reboot my laptop with older
  4.10.0-42-generic kernel. I'm not sure whether it is Xorg bug or
  kernel graphics driver bug. The unvisible 3/4 part of the screen seems
  to be fully operational. I may open an application window in it and
  drag it to the visible 1/4 part of the screen. Besides the screen
  display issue the system seems to run properly. I was able to report
  this bug while running the 4.13.0-26-generic kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Thu Jan 11 18:29:04 2018
  InstallationDate: Installed on 2017-12-18 (24 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 
(20170801)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1742756/+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 1742756] Re: [Xubuntu] 3/4 of XFCE and console screen is unreadable

[Pawel Por]

** Attachment added: "dmesg_linux_4.10.0-42-generic.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1742756/+attachment/5035302/+files/dmesg_linux_4.10.0-42-generic.txt

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

Title:
  [Xubuntu] 3/4 of XFCE and console screen is unreadable

Status in xorg package in Ubuntu:
  New

Bug description:
  After upgrading to kernel 4.13.0-26-generic "3/4" part of screen is
  unreadable. It is both in xorg/xfce and console (ctrl+alt+F1).
  Everything works perfect when I reboot my laptop with older
  4.10.0-42-generic kernel. I'm not sure whether it is Xorg bug or
  kernel graphics driver bug. The unvisible 3/4 part of the screen seems
  to be fully operational. I may open an application window in it and
  drag it to the visible 1/4 part of the screen. Besides the screen
  display issue the system seems to run properly. I was able to report
  this bug while running the 4.13.0-26-generic kernel.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Thu Jan 11 18:29:04 2018
  InstallationDate: Installed on 2017-12-18 (24 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 
(20170801)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1742756/+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 1727401] Re: Corruption on windowed 3D apps running on dGPU (Intel/AMD)

[Łukasz Zemczak]

Hello Timo, or anyone else affected,

Accepted mesa into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/17.2.4-0ubuntu1~16.04.3 in a
few hours, and then in the -proposed repository.

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

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

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

** Changed in: mesa (Ubuntu Xenial)
   Status: Triaged => Fix Committed

** Tags removed: verification-done-xenial
** Tags added: verification-needed-xenial

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

Title:
  Corruption on windowed 3D apps running on dGPU (Intel/AMD)

Status in Mesa:
  In Progress
Status in OEM Priority Project:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa source package in Xenial:
  Fix Committed
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  [Impact]

  Corruption is seen on windowed 3D apps running on dGPU

  [Test case]

  Get a certain Intel/AMD hybrid machine, run 'DRI_PRIME=1 glxgears',
  see how the window has corrupted gfx.

  The fix is to patch Intel i965_dri driver.

  [Regression potential]

  There could be a slight loss of performance, but corruption free
  behaviour.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1727401/+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 1735594] Re: [regression] compiz crashes after Mesa upgrade

[Łukasz Zemczak]

Hello Falk, or anyone else affected,

Accepted mesa into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/17.2.4-0ubuntu1~16.04.3 in a
few hours, and then in the -proposed repository.

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

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

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

** Changed in: mesa (Ubuntu Xenial)
   Status: Confirmed => Fix Committed

** Tags added: verification-needed-xenial

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

Title:
  [regression] compiz crashes after Mesa upgrade

Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa source package in Xenial:
  Fix Committed
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  When I use the Unity session I automatically get logged out under these 
conditions:

  When I hover with my mouse over any icon of the sidebar.
  When I press the alt key.
  When I press the super key.

  running dmesg after this unwanted logout happens I get following
  information:

  compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0
  error 4 in i965_dri.so[7fbca2af6000+7e4000]

  This is caused by a mesa upgrade, which added a patch for bug #1727401. The 
crasher is reproduced on:
  - gen4 / gen5 Intel
  - if using modesetting X driver, like when xserver-xorg-video-intel is not 
installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults 
to modesetting)

  [Test case]
  Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash.

  [Regression potential]
  The backported patches need to be tested, here for regressions and on 1727401 
that they fix the original bug (again).

  Best to test on a wide array of Intel HW:
  gen4 (965GM/GM45/G45)
  gen5 (Ironlake)
  gen6 (Sandy Bridge)
  gen7 (Bay Trail, Ivy Bridge, Haswell)
  gen8 (Braswell, Broadwell)
  gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594/+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 1742756] Re: 3/4 of XFCE and console screen is unreadable

[Pawel Por]

** Description changed:

  After upgrading to kernel 4.13.0-26-generic 3/4 of screen is unreadable.
- It is both in xorg/xfce and terminal after pressing ctrl+alt+F1.
- Everything works perfect when I reboot my laptop with older
- 4.10.0-42-generic kernel. It may be also a kernel graphics driver bug
- rather than xorg bug. Now I'm wiritng this description on a 1/4 part of
- the screen that looks ok. Besides the screen display issue the system
- seems to run ok.
+ It is both in xorg/xfce and conole (ctrl+alt+F1). Everything works
+ perfect when I reboot my laptop with older 4.10.0-42-generic kernel. I'm
+ not sure whether it is Xorg bug or kernel graphics driver bug. The
+ unvisible 3/4 part of the screen seems to be fully operational. I may
+ open an application window in it and drag it to the visible 1/4 part of
+ the screen. Besides the screen display issue the system seems to run
+ properly.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Thu Jan 11 18:29:04 2018
  InstallationDate: Installed on 2017-12-18 (24 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 
(20170801)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  After upgrading to kernel 4.13.0-26-generic 3/4 of screen is unreadable.
- It is both in xorg/xfce and conole (ctrl+alt+F1). Everything works
+ It is both in xorg/xfce and console (ctrl+alt+F1). Everything works
  perfect when I reboot my laptop with older 4.10.0-42-generic kernel. I'm
  not sure whether it is Xorg bug or kernel graphics driver bug. The
  unvisible 3/4 part of the screen seems to be fully operational. I may
  open an application window in it and drag it to the visible 1/4 part of
  the screen. Besides the screen display issue the system seems to run
  properly.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Thu Jan 11 18:29:04 2018
  InstallationDate: Installed on 2017-12-18 (24 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 
(20170801)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

** Description changed:

  After upgrading to kernel 4.13.0-26-generic 3/4 of screen is unreadable.
  It is both in xorg/xfce and console (ctrl+alt+F1). Everything works
  perfect when I reboot my laptop with older 4.10.0-42-generic kernel. I'm
  not sure whether it is Xorg bug or kernel graphics driver bug. The
  unvisible 3/4 part of the screen seems to be fully operational. I may
  open an application window in it and drag it to the visible 1/4 part of
  the screen. Besides the screen display issue the system seems to run
- properly.
+ properly. I was able to report this bug while running the
+ 4.13.0-26-generic kernel.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Thu Jan 11 18:29:04 2018
  InstallationDate: Installed on 2017-12-18 (24 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 
(20170801)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

** Summary changed:

- 3/4 of XFCE and console screen is unreadable
+ [Xubuntu] 3/4 of XFCE and console screen is unreadable

** Description changed:

- After upgrading to kernel 4.13.0-26-generic 3/4 of screen is unreadable.
- It is both in xorg/xfce and console (ctrl+alt+F1). Everything works
- perfect when I reboot my laptop with older 4.10.0-42-generic kernel. I'm
- not sure whether it is Xorg bug or kernel graphics driver bug. The
- unvisible 3/4 part of the screen seems to be fully operational. I may
- open an application window in it and drag it to the visible 1/4 part of
- the screen. Besides the screen display issue the system seems to run
- properly. I was able to report this bug while running the
- 4.13.0-26-generic kernel.
+ After upgrading to kernel 4.13.0-26-generic "3/4" part of screen is
+ unreadable. It is both in xorg/xfce and console (ctrl+alt+F1).
+ Everything works perfect when I reboot my laptop with older
+ 4.10.0-42-generic kernel. I'm not sure whether it is Xorg bug or kernel
+ graphics driver bug. The unvisible 3/4 part of the screen seems to be
+ fully operational. I may open an application window in it and drag it to
+ the visible 1/4 part of the 

[Touch-packages] [Bug 1741447] Re: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04

[Leo Pilachowski]

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

There appear to be two ppa locations to get the fix for 16.04 i386:

ppa: paulo-miguel-dias / pkppa

ppa:tjaalton/ppa

Please tell us again how to get and try out the possible fix.  I am
experienced but new to Ubuntu but need to get a older system up and
running asap on 16.04.

Leo

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

Title:
  Unity / Compiz in a crash loop after login, after mesa updates of
  2018-01-04

Status in Mesa:
  New
Status in mesa package in Ubuntu:
  Confirmed
Status in mesa source package in Xenial:
  Confirmed
Status in mesa source package in Artful:
  Confirmed

Bug description:
  GUI is constantly crashing, can't start desktop

  Jan  5 11:21:29 1810 kernel: [  806.368754] compiz[10824]: segfault at 0 ip 
7f83c4f31c16 sp 7ffd48dfc2f0 error 4 in i965_dri.so[7f83c4954000+82d000]
  Jan  5 11:21:40 1810 kernel: [  817.279740] compiz[1]: segfault at 0 ip 
7fda21519c16 sp 7ffd7b40a150 error 4 in i965_dri.so[7fda20f3c000+82d000]
  Jan  5 11:22:30 1810 kernel: [  867.445137] compiz[11271]: segfault at 0 ip 
7f8462855c16 sp 7fff07c857f0 error 4 in i965_dri.so[7f8462278000+82d000]
  Jan  5 11:22:46 1810 kernel: [  883.319195] compiz[11458]: segfault at 0 ip 
7f72b7af0c16 sp 7ffc3b92d830 error 4 in i965_dri.so[7f72b7513000+82d000]
  Jan  5 11:23:01 1810 kernel: [  898.587610] compiz[11516]: segfault at 0 ip 
7fe25113dc16 sp 7ffcf79754c0 error 4 in i965_dri.so[7fe250b6+82d000]

  In /var/crash:
  _usr_bin_compiz.999.crash

  Did manage to start a GUI in Low graphics mode (lowgfx.conf) but this is not 
really usable.
  - dash not working
  - no window switching
  - sometimes all windows disappear for a few seconds

  So effectively my laptop is not usable after latest updates.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity 7.4.0+16.04.20160906-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  .tmp.unity_support_test.0:

  .tmp.unity_support_test.1:

  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Jan  5 11:16:53 2018
  DistUpgraded: 2016-04-22 18:36:32,349 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
     Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:029b]
     Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:029b]
  InstallationDate: Installed on 2014-04-18 (1357 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Acer Aspire 1810TZ
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic 
root=UUID=86d7d9a6-ffc3-47cb-adc4-68cfcbcadcef ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (622 days ago)
  dmi.bios.date: 08/31/2010
  dmi.bios.vendor: INSYDE
  dmi.bios.version: v1.3314
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JM11-MS
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 1
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvrv1.3314:bd08/31/2010:svnAcer:pnAspire1810TZ:pvrv1.3314:rvnAcer:rnJM11-MS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
  dmi.product.name: Aspire 1810TZ
  dmi.product.version: v1.3314
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Fri Jan  5 11:14:24 2018
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

To manage notifications about this bug go to:

[Touch-packages] [Bug 1742744] Re: machinectl import-tar hangs when the import file is multi-streamed

[Matthew Thode]

fixed in https://github.com/systemd/systemd/pull/7857 (tested)

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

Title:
  machinectl import-tar hangs when the import file is multi-streamed

Status in systemd package in Ubuntu:
  New

Bug description:
  When trying to use machinectl import-tar to import a compressed rootfs
  tarball, if the compression is multi-streamed then the import hangs
  after the first stream.

  Either the multi-stream import should work, or it should be detected
  and an error output.

  Environment:
  Ubuntu 17.10 (Artful Aardvark)
  systemd-container 234-2ubuntu12.1

  Steps to reproduce:

  # install systemd-container
  apt-get update && apt-get install systemd-container

  # fetch a multi-stream compressed rootfs
  wget 
http://rpc-repo.rackspace.com/lxc-images/ubuntu/xenial/amd64/default-r14.7.0/20180101/rootfs.tar.xz

  # verify that it has multiple streams
  xz -lvv rootfs.tar.xz

  # try to import it
  machinectl --verify=no import-tar rootfs.tar.xz test

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1742744/+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 1742769] [NEW] Pulse Audio Won't Run After BionicBeaver Update

[Stephen Allen]

Public bug reported:

As per the bug report, I've noticed that Pulse Audio is segfaulting.
Happened after the large update to Bionic Beaver this morning (Thursday
Jan 11/18).

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pulseaudio 1:11.1-1ubuntu3
ProcVersionSignature: Ubuntu 4.14.0-16.19-generic 4.14.12
Uname: Linux 4.14.0-16-generic x86_64
ApportVersion: 2.20.8-0ubuntu6
Architecture: amd64
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D11p', 
'/dev/snd/pcmC1D10p', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', 
'/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
CurrentDesktop: GNOME
Date: Thu Jan 11 13:32:21 2018
InstallationDate: Installed on 2017-12-20 (21 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
SourcePackage: pulseaudio
Symptom: audio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/12/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1401
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: M5A97 LE R2.0
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1401:bd12/12/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97LER2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: To be filled by O.E.M.
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: To be filled by O.E.M.

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


** Tags: amd64 bionic package-from-proposed pulseaudio sound wayland-session

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

Title:
  Pulse Audio Won't Run After BionicBeaver Update

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  As per the bug report, I've noticed that Pulse Audio is segfaulting.
  Happened after the large update to Bionic Beaver this morning
  (Thursday Jan 11/18).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu3
  ProcVersionSignature: Ubuntu 4.14.0-16.19-generic 4.14.12
  Uname: Linux 4.14.0-16-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/dsp', 
'/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D2c', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D11p', 
'/dev/snd/pcmC1D10p', '/dev/snd/pcmC1D9p', '/dev/snd/pcmC1D8p', 
'/dev/snd/pcmC1D7p', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: GNOME
  Date: Thu Jan 11 13:32:21 2018
  InstallationDate: Installed on 2017-12-20 (21 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170920)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1401
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: M5A97 LE R2.0
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1401:bd12/12/2012:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A97LER2.0:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: To be filled by O.E.M.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1742769/+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 1385292] Re: can't rename files in nautilus

[Dennis Baudys]

The problem still exists here (e.g. using nemo and trying to rename
files does not work in any way). I'm living with this very annoying bug
since years. Frustrating.

DistroRelease: Linux Mint 17.3 Rosa
Uname: Linux 4.4.0-109-generic #132~14.04.1-Ubuntu SMP
NonfreeKernelModules: nvidia
Architecture: amd64
CurrentDesktop: Cinnamon

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

Title:
  can't rename files in nautilus

Status in ibus:
  Unknown
Status in ibus package in Ubuntu:
  Triaged

Bug description:
  sometimes can't rename files with F2 button. It is higlight changing,
  but nothing gonna happen, it is not responding

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: nautilus 1:3.10.1-0ubuntu15
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 24 17:48:33 2014
  GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' 
b"['name', 'size', 'type', 'date_modified', 'date_accessed', 'owner', 'group', 
'permissions', 'mime_type', 'where']"
  InstallationDate: Installed on 2014-10-24 (0 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ibus/+bug/1385292/+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 1727390] Re: New bugfix release 17.2.4

[Łukasz Zemczak]

Hello Timo, or anyone else affected,

Accepted mesa into artful-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/17.2.4-0ubuntu1~17.10.2 in a
few hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-artful to verification-done-artful. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-artful. In either case, without details of
your testing we will not be able to proceed.

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

** Tags removed: verification-done-artful
** Tags added: verification-needed verification-needed-artful

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

Title:
  New bugfix release 17.2.4

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Xenial:
  Fix Released
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  [Impact]

  A new upstream bugfix release is available. Release note diff compared
  to 17.2.2:

  "Mesa 17.2.3 is now available.

  In this release we have:

  The Vulkan drivers ANV and RADV have multiple small fixes.

  The EGL code has improved handling of the new wl_dmabuf codepath.

  SWR no longer crashes when checking environment variables.

  Other gallium drivers have also seen updates - freedreno, nouveau and
  radeonsi. The gallivm module, used by llvmpipe et al. has gained little
  endian PPC64 fixes.

  The VA and VDPAU state-trackers have seems improvements handling
  interlaced videos.

  We're using python3 compatible constructs which gives us SCons 3.0
  support."

  "Mesa 17.2.4 is now available.

  In this release we have:

  In Mesa Core we have included a change to prevent KOTOR from breaking
  when in combination with the ATI fragment shader extension. 
  Additionally, NIR has also received a correction.

  Mesa's state tracker has gotten a patch to avoid leaks in certain
  situations like when resizing a window.

  Intel drivers have received several fixes.  The compiler has gotten a
  couple, while anv also received one.  i965 got a patch to avoid VA-
  API, Beignet and other contexts in the system to break when in
  combination with previous versions of Mesa 17.2.x.

  AMD's compiler has received a couple of fixes while radv has also
  received another couple, including one to avoid a hang due to an
  overflow on huge textures.

  Broadcom's vc4 has corrected a problem when compiling with Android's
  clang.

  clover has also seen fixed a problem compiling after a specific clang
  revision.

  Vulkan's WSI has gotten plugged a memory leak for X11."

  
  [Test case]

  Test typical use cases on the most common hw/driver combinations:
  intel/i965
  nvidia/nouveau
  radeon/radeonsi

  [Regression potential]

  These releases are tested against compliance, bugfix releases in
  particular have minimal risk of regressing anything major at least.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1727390/+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 1720890] Re: vulkan-smoketest segfaults steam vulkan games segfault

[Łukasz Zemczak]

Hello Lawrence, or anyone else affected,

Accepted mesa into artful-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/17.2.4-0ubuntu1~17.10.2 in a
few hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-artful to verification-done-artful. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-artful. In either case, without details of
your testing we will not be able to proceed.

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

** Tags removed: verification-done verification-done-artful
** Tags added: verification-needed verification-needed-artful

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

Title:
  vulkan-smoketest segfaults steam vulkan games segfault

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Xenial:
  Fix Released
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu Artful Aardvark (development branch)
  Release:  17.10

  $ apt-cache policy mesa-vulkan-drivers
  mesa-vulkan-drivers:
Installed: 17.2.1-0ubuntu1
Candidate: 17.2.1-0ubuntu1
Version table:
   *** 17.2.1-0ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu artful/universe amd64 Packages
  100 /var/lib/dpkg/status

  
  Easily reproducible : apt-get install mesa-vulkan-drivers apt-get install 
vulkan-utils

  Open a terminal type vulkan-smoketest instead of a glxgears type window it 
will segfault.
  message from kernel.log:
  Sep 29 16:23:53 Tardis-1 kernel: [17709.532915] vulkan-smoketes[11798]: 
segfault at 0 ip 7fed61a17914 sp 7ffedcb8f850 error 6 in 
libvulkan_radeon.so[7fed619ab000+18b000]
  syslog:
  Sep 28 10:38:13 Tardis-1 kernel: [18292.174313] vulkan-smoketes[13385]: 
segfault at 0 ip 7f62705a7914 sp 7ffd0edc6260 error 6 in 
libvulkan_radeon.so[7f627053b000+18b000]

  What should happen is a glxgears like window will open and render properly 
instead of segfaulting.
  It appears that the culprit is an old or broken libvulkan_radeon.so provided 
by mesa-vulkan-drivers.

  As a test I renamed the old lib and dropped in a newer version from
  oibaf's ppa. smoketest now passes steam's The Talos Princible and Mad
  Max now work properly in Vulkan mode as well instead of segfaulting.

  This issue is also present on Zesty and fixed in both Oibaf's and
  Padoka's ppa's since April back when they were rolling 17.2 mesa.

  I have no idea if libvulkan_intel.so also needs updating no hardware
  to check.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1720890/+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 1727401] Re: Corruption on windowed 3D apps running on dGPU (Intel/AMD)

[Łukasz Zemczak]

Hello Timo, or anyone else affected,

Accepted mesa into artful-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/17.2.4-0ubuntu1~17.10.2 in a
few hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-artful to verification-done-artful. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-artful. In either case, without details of
your testing we will not be able to proceed.

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

** Changed in: mesa (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  Corruption on windowed 3D apps running on dGPU (Intel/AMD)

Status in Mesa:
  In Progress
Status in OEM Priority Project:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa source package in Xenial:
  Triaged
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  [Impact]

  Corruption is seen on windowed 3D apps running on dGPU

  [Test case]

  Get a certain Intel/AMD hybrid machine, run 'DRI_PRIME=1 glxgears',
  see how the window has corrupted gfx.

  The fix is to patch Intel i965_dri driver.

  [Regression potential]

  There could be a slight loss of performance, but corruption free
  behaviour.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1727401/+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 1735594] Re: [regression] compiz crashes after Mesa upgrade

[Łukasz Zemczak]

Hello Falk, or anyone else affected,

Accepted mesa into artful-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/17.2.4-0ubuntu1~17.10.2 in a
few hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-artful to verification-done-artful. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-artful. In either case, without details of
your testing we will not be able to proceed.

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

** Changed in: mesa (Ubuntu)
   Status: Confirmed => Fix Committed

** Changed in: mesa (Ubuntu Artful)
   Status: Confirmed => Fix Committed

** Tags added: verification-needed verification-needed-artful

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

Title:
  [regression] compiz crashes after Mesa upgrade

Status in mesa package in Ubuntu:
  Fix Committed
Status in mesa source package in Xenial:
  Confirmed
Status in mesa source package in Artful:
  Fix Committed

Bug description:
  [Impact]
  When I use the Unity session I automatically get logged out under these 
conditions:

  When I hover with my mouse over any icon of the sidebar.
  When I press the alt key.
  When I press the super key.

  running dmesg after this unwanted logout happens I get following
  information:

  compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0
  error 4 in i965_dri.so[7fbca2af6000+7e4000]

  This is caused by a mesa upgrade, which added a patch for bug #1727401. The 
crasher is reproduced on:
  - gen4 / gen5 Intel
  - if using modesetting X driver, like when xserver-xorg-video-intel is not 
installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults 
to modesetting)

  [Test case]
  Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash.

  [Regression potential]
  The backported patches need to be tested, here for regressions and on 1727401 
that they fix the original bug (again).

  Best to test on a wide array of Intel HW:
  gen4 (965GM/GM45/G45)
  gen5 (Ironlake)
  gen6 (Sandy Bridge)
  gen7 (Bay Trail, Ivy Bridge, Haswell)
  gen8 (Braswell, Broadwell)
  gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594/+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 1726930] Re: System fails to start (boot) on battery due to read-only root file-system

[Martin]

Hi, I'm using Debian Stretch on a Thinkpad X220 and had the same issue.
The advice from Ritesh Raj Sarraf worked for me too and I just
registered to confirm this.

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

Title:
  System fails to start (boot) on battery due to read-only root file-
  system

Status in laptop-mode-tools package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed
Status in systemd package in Debian:
  Fix Released

Bug description:
  This report is to capture the extended diagnostic efforts done on IRC
  #ubuntu for user maszlo, who has a Lenovo T450 with SSD that was
  upgraded from 17.04 to 17.10 and since fails to complete start-up of
  services when powered on battery.

  We'd previously applied the "acpi=os=! 'acpi_osi=Windows 2015'"
  workaround in case this was an ACPI DSDT issue.

  This appears to be due to a read-only root file-system. What is not
  clear is how the rootfs goes read-only.

  The file-system (sda6, ext4) is fsck-ed successfully in the initrd
  according to the /run/initramfs/fsck.log.

  From the start-up logs (with "systemd.log_level=debug") we see the
  ext4 driver report a remount operation not once but five times.

  $ grep 'EXT4-fs.*sda6' systemd-debug.log
  Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): mounted filesystem with ordered 
data mode. Opts: (null)
  Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro
  Oct 23 18:10:46 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:47 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600
  Oct 23 18:10:49 T450s kernel: EXT4-fs (sda6): re-mounted. Opts: 
errors=remount-ro,data=ordered,commit=600

  Those last five appear to be carrying options generated by laptop-
  mode-tools.

  User has disabled laptop-mode.service and laptop-mode.timer, and lmt-
  poll.service, but the issue remains.

  We see several reports of "read-only file-system":

  $ grep 'Read-only' systemd-debug.log
  Oct 23 18:10:46 T450s grub-common[1792]: grub-editenv: error: cannot open 
`/boot/grub/grubenv': Read-only file system.
  Oct 23 18:10:46 T450s systemd[1]: colord.service: Failed to run 'start' task: 
Read-only file system
  Oct 23 18:10:46 T450s gpu-manager[1797]: Warning: writing to 
/var/log/gpu-manager.log failed (Read-only file system)
  Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 
'start' task: Read-only file system
  Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to run 
'start' task: Read-only file system
  Oct 23 18:10:46 T450s gdm3[1932]: Failed to create LogDir /var/log/gdm3: 
Read-only file system
  ...
  Oct 23 18:11:26 T450s cupsd[1461]: Unable to change ownership of 
"/var/log/cups" - Read-only file system
  Oct 23 18:11:26 T450s cupsd[1461]: Unable to open log file 
"/var/log/cups/access_log" - Read-only file system
  Oct 23 18:12:52 T450s login[9248]: pam_lastlog(login:session): unable to open 
/var/log/lastlog: Read-only file system

  We also see several problems with systemd's connection to Dbus:

  $ grep 'Transport endpoint' systemd-debug.log
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job change signal for 773: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: systemd-logind.service: Failed to send unit 
change signal for systemd-logind.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 156: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: lmt-poll.service: Failed to send unit 
change signal for lmt-poll.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 182: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 95: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: polkit.service: Failed to send unit change 
signal for polkit.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: cups-browsed.service: Failed to send unit 
change signal for cups-browsed.service: Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job change signal for 773: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for 161: 
Transport endpoint is not connected
  Oct 23 18:10:46 T450s systemd[1]: gdomap.service: Failed to send unit change 
signal for gdomap.service: Transport endpoint is not connected

  When the user purged 

[Touch-packages] [Bug 1742756] [NEW] 3/4 of XFCE and console screen is unreadable

[Pawel Por]

Public bug reported:

After upgrading to kernel 4.13.0-26-generic 3/4 of screen is unreadable.
It is both in xorg/xfce and terminal after pressing ctrl+alt+F1.
Everything works perfect when I reboot my laptop with older
4.10.0-42-generic kernel. It may be also a kernel graphics driver bug
rather than xorg bug. Now I'm wiritng this description on a 1/4 part of
the screen that looks ok. Besides the screen display issue the system
seems to run ok.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
Uname: Linux 4.13.0-26-generic i686
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: i386
CurrentDesktop: XFCE
Date: Thu Jan 11 18:29:04 2018
InstallationDate: Installed on 2017-12-18 (24 days ago)
InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801)
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: apport-bug corruption i386 xenial

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

Title:
  3/4 of XFCE and console screen is unreadable

Status in xorg package in Ubuntu:
  New

Bug description:
  After upgrading to kernel 4.13.0-26-generic 3/4 of screen is
  unreadable. It is both in xorg/xfce and terminal after pressing
  ctrl+alt+F1. Everything works perfect when I reboot my laptop with
  older 4.10.0-42-generic kernel. It may be also a kernel graphics
  driver bug rather than xorg bug. Now I'm wiritng this description on a
  1/4 part of the screen that looks ok. Besides the screen display issue
  the system seems to run ok.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic i686
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Thu Jan 11 18:29:04 2018
  InstallationDate: Installed on 2017-12-18 (24 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 
(20170801)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1742756/+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 1648107] Re: $XAUTHORITY should move into $XDG_RUNTIME_DIR

[Markus Kuhn]

While we are at it, we could probably also set

  ICEAUTHORITY=$XDG_RUNTIME_DIR/ICEauthority

in a similar fashion, as this is the equivalent cookie facility for X11
client-client communication.

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

Title:
  $XAUTHORITY should move into $XDG_RUNTIME_DIR

Status in lightdm package in Ubuntu:
  Triaged

Bug description:
  Historically, the X authority file was placed into $HOME/.Xauthority
  such that X11 clients on remote servers could access it in
  environments in which $HOME is located on a network file system.

  Today, this practice has become an anachronism that causes far more
  problems than it solves:

  a) Remote X11 clients are typically started today via "ssh -X", which
  emulates its own X11 server port $DISPLAY and therefore always creates
  its own X authority file entry on the remote server. Therefore, there
  is no longer any practical benefit from having the X authority file
  located in $HOME.

  b) If $HOME is on a network file system that implements "root squash",
  then commands such as "sudo xterm" or "sudo wireshark" won't work to
  start an X client with root privileges, as root is not able to read
  ~/.Xauthority via NFS. :-(

  c) If $HOME is on a network file system with Kerberos authentication,
  then users can easily get locked out by their screensavers once the
  Kerberos ticket expires. This is because some screen lockers (e.g.,
  gnome-screensaver) invoke a separate utility (e.g., /usr/lib/gnome-
  screensaver/gnome-screensaver-dialog) in order to ask the user of a
  locked screen for their password. Such a tool needs to access
  $XAUTHORITY right before it can display the password prompt, which
  will fail if the user's Kerberos ticket has expired (e.g. because a
  machine was suspended for 24 hours and therefore the ticket was not
  refreshed automatically on time). Without the ability to ask for a
  password, the screensaver then cannot call pam_krb5 to renew the
  user's Kerberos ticket, and the user remains locked out in a deadlock
  situation. :-(

  Both b) and c) are regular reasons for support requests in
  educational/corporate Linux environments with $HOME on Kerberized NFS.

  The solution is simple. Instead of $HOME/.Xauthority, just use in
  future $XDG_RUNTIME_DIR/xauthority as the location of the X authority
  file. (In case $XDG_RUNTIME_DIR/ does not exist, /tmp/xauthority-$USER
  might be a suitable fallback option.)

  According to https://standards.freedesktop.org/basedir-spec/basedir-
  spec-latest.html the $XDG_RUNTIME_DIR has all the right properties for
  holding the X authority file: it is always located in a local tmpfs
  filesystem, guaranteed to be accessible only to the current user, and
  will be wiped when the user has closed all sessions.

  On modern Linux systems, pam_systemd usually creates
  XDG_RUNTIME_DIR=/run/user/$UID, and wipes it in the end.

  (Note that according to https://standards.freedesktop.org/basedir-spec
  /basedir-spec-latest.html you should set the "sticky bit" on any files
  created in $XDG_RUNTIME_DIR whose timestamp is not updated regularly.)

  Feature request: please provide an option for LightDM to do the
  equivalent of

export XAUTHORITY=$XDG_RUNTIME_DIR/xauthority
chmod +t $XAUTHORITY

  and encourage Linux distribution maintainers to set this option by
  default, such that ~/.Xauthority is no longer used.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1648107/+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 1740033] Re: [Realtek ALC1220, Green Line Out, Rear] Background noise or low volume on left speaker only

[Joao]

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

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

Title:
  [Realtek ALC1220, Green Line Out, Rear] Background noise or low volume
  on left speaker only

Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  I've upgraded my computer to a new one with a Realtek ALC1220 from an
  ASUS crosshair VI hero and on my ubuntu 17.10 my 5.1 surround left
  audio is busted, I've configured the system audio to 5.1 and tested
  all speakers one by one and the only one that isn't working correctly
  is the left speaker, it emits the testing sound but is disturbed and
  very low, I've checked alsaconf and everything is alright there.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-22.25-generic 4.13.13
  Uname: Linux 4.13.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  biohazard   1481 F pulseaudio
   /dev/snd/controlC1:  biohazard   1481 F pulseaudio
  CurrentDesktop: GNOME
  Date: Mon Dec 25 15:39:30 2017
  InstallationDate: Installed on 2017-12-25 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: HD-Audio Generic - HD-Audio Generic
  Symptom_Jack: Green Line Out, Rear
  Symptom_Type: High background noise, or volume is too low
  Title: [System Product Name, Realtek ALC1220, Green Line Out, Rear] 
Background noise or low volume
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/29/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3008
  dmi.board.asset.tag: Default string
  dmi.board.name: ROG CROSSHAIR VI HERO (WI-FI AC)
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3008:bd11/29/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGCROSSHAIRVIHERO(WI-FIAC):rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1740033/+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 961679] Re: gtkrc is producing light menus from dark elements

[Norbert]

Scilab is still affected - see bug 1547561.

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

Title:
  gtkrc is producing light menus from dark elements

Status in ubuntu-themes package in Ubuntu:
  Fix Released
Status in ubuntu-themes source package in Xenial:
  Fix Released

Bug description:
  [Impact]

  Menu items for apps using gtk2 use a light color, which is
  inconsistent with all other system apps using gtk3 and that are using
  dark menus.

  [Test case]

  Right click on any window's title bar
  In app window menus of gtk 2 apps, examples -  synaptic, browsers where 
global menus aren't used, vlc with no global menu, ect.
  Right click in a browser's  menu bar
  Systray right click menus

  The in app window  context menu of gtk2 windows should be dark.

  [Regression potential]

  Menu items not usable or readable in some apps.

  ProblemType: BugDistroRelease: Ubuntu 12.04
  Package: light-themes 0.1.8.31-0ubuntu1 [modified: 
usr/share/themes/Ambiance/gtk-2.0/gtkrc 
usr/share/themes/Ambiance/gtk-3.0/apps/nautilus.css 
usr/share/themes/Ambiance/gtk-3.0/gtk-widgets.css 
usr/share/themes/Ambiance/gtk-3.0/gtk.css 
usr/share/themes/Ambiance/gtk-3.0/settings.ini 
usr/share/themes/Ambiance/metacity-1/close.png 
usr/share/themes/Ambiance/metacity-1/close_focused_normal.png 
usr/share/themes/Ambiance/metacity-1/close_focused_prelight.png 
usr/share/themes/Ambiance/metacity-1/close_focused_pressed.png 
usr/share/themes/Ambiance/metacity-1/metacity-theme-1.xml]
  ProcVersionSignature: Ubuntu 3.2.0-19.30-generic-pae 3.2.11
  Uname: Linux 3.2.0-19-generic-pae i686
  NonfreeKernelModules: nvidia
  ApportVersion: 1.94.1-0ubuntu2
  Architecture: i386
  Date: Wed Mar 21 17:42:27 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bashSourcePackage: light-themes
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/961679/+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 1547561] Re: Unable to use Scilab with default Ambiance theme because of low contrast in the menu

[Norbert]

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

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

Title:
  Unable to use Scilab with default Ambiance theme because of low
  contrast in the menu

Status in scilab package in Ubuntu:
  New
Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Install Ubuntu with all default settings (Ambiance theme)
  2. Install Scilab
  3. Launch Scilab
  4. Try to use Scilab menu on the top of its window
  5. This menu has low contrast (see screenshot from 14.04).

  Temporary solution:
  switch theme to light (Radiance) theme.

  Affected Ubuntu versions:
  12.04 LTS, 14.04 LTS, 16.04 LTS, 16.10, 17.04, 17.10, 18.04 LTS.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: scilab 5.5.0-2
  ProcVersionSignature: Ubuntu 3.19.0-49.55~14.04.1-generic 3.19.8-ckt12
  Uname: Linux 3.19.0-49-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  CurrentDesktop: Unity
  Date: Fri Feb 19 18:31:09 2016
  InstallationDate: Installed on 2015-12-12 (68 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta i386 (20150805)
  PackageArchitecture: all
  SourcePackage: scilab
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/scilab/+bug/1547561/+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 1742750] [NEW] Pulseaudio 1:11.1-1ubuntu3 will not start due to invalid /etc/pulse/default.pa file

[Michael Marley]

Public bug reported:

Version 1:11.1-1ubuntu3 added 0030-load-module-switch-on-connect.patch,
which changes line 38 of /etc/pulse/default.pa to read ".endif### Load
audio drivers statically".  It appears that there are a couple of line
feeds missing here, and having the comment on the same line as the endif
causes pulseaudio not to start.

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

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

Title:
  Pulseaudio 1:11.1-1ubuntu3 will not start due to invalid
  /etc/pulse/default.pa file

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Version 1:11.1-1ubuntu3 added 0030-load-module-switch-on-
  connect.patch, which changes line 38 of /etc/pulse/default.pa to read
  ".endif### Load audio drivers statically".  It appears that there are
  a couple of line feeds missing here, and having the comment on the
  same line as the endif causes pulseaudio not to start.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1742750/+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 1742695] Re: apt-get update silently fails fetching security updates

[Julian Andres Klode]

So, that's not a bug then. I eventually want to add a feature where you
can switch between a one-source-must-update and a all-sources-must-
update mode, but as mentioned before, that's way off - it probably
requires quite a few changes.


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

** Changed in: apt (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  apt-get update silently fails fetching security updates

Status in apt package in Ubuntu:
  Triaged

Bug description:
  On Ubuntu Xenial, apt-get fails silently when security update server
  cannot be reached. This state could be detected by scanning the apt-
  get output afterwards. But manually adding workarounds to each apt-get
  invocation in production automation is prone to error, thus leaving
  machines without security updates.

  Expected behaviour (e.g.):
  * 0 - all OK
  * 1 - temporary failure (e.g. network)
  * 2 - permanent failure

  
  Test:
  * Change your update server IP in /etc/hosts to something unreachable
  * Run apt-get update (might take a while)
  * Check exit status

  
  $ lsb_release -r -d
  Description:Ubuntu 16.04.3 LTS
  Release:16.04
  rfiedler@n3ahit1403:~$ 

  ii  apt 1.2.24
  amd64commandline package manager

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1742695/+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 1737034] Re: ubuntu-bug -w doesn't work in Wayland

[Jean-Baptiste Lallement]

** Tags removed: wayland-session
** Tags added: wayland

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

Title:
  ubuntu-bug -w doesn't work in Wayland

Status in apport package in Ubuntu:
  New

Bug description:
  `ubuntu-bug -w` doesn't work in the default Ubuntu 17.10 session
  (Ubuntu's GNOME session on Wayland)

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: apport 2.20.7-0ubuntu3.5
  ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8
  Uname: Linux 4.13.0-17-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu3.5
  Architecture: amd64
  CrashReports:
   640:126:122:21379961:2017-11-29 13:11:42.438395227 +:2017-11-29 
13:11:23.438264558 +:/var/crash/_usr_bin_gnome-shell.126.crash
   640:0:122:611910:2017-12-01 13:36:01.803494733 +:2017-12-01 
13:36:01.107494760 +:/var/crash/_sbin_plymouthd.0.crash
   640:1000:122:1888686:2017-11-30 19:30:21.850164677 +:2017-11-30 
19:30:19.606143881 +:/var/crash/_usr_lib_epiphany-search-provider.1000.crash
   640:1000:122:14379104:2017-12-07 19:30:06.836658346 +:2017-12-07 
19:29:55.528547234 +:/var/crash/_usr_bin_epiphany.1000.crash
   640:1000:122:52102597:2017-12-04 12:27:24.797221538 +:2017-12-04 
12:26:41.276351237 +:/var/crash/_usr_bin_gnome-shell.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Dec  7 21:00:32 2017
  InstallationDate: Installed on 2017-08-03 (126 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to artful on 2017-10-21 (47 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1737034/+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 1742744] [NEW] machinectl import-tar hangs when the import file is multi-streamed

[Jesse Pretorius]

Public bug reported:

When trying to use machinectl import-tar to import a compressed rootfs
tarball, if the compression is multi-streamed then the import hangs
after the first stream.

Either the multi-stream import should work, or it should be detected and
an error output.

Environment:
Ubuntu 17.10 (Artful Aardvark)
systemd-container 234-2ubuntu12.1

Steps to reproduce:

# install systemd-container
apt-get update && apt-get install systemd-container

# fetch a multi-stream compressed rootfs
wget 
http://rpc-repo.rackspace.com/lxc-images/ubuntu/xenial/amd64/default-r14.7.0/20180101/rootfs.tar.xz

# verify that it has multiple streams
xz -lvv rootfs.tar.xz

# try to import it
machinectl --verify=no import-tar rootfs.tar.xz test

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

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

Title:
  machinectl import-tar hangs when the import file is multi-streamed

Status in systemd package in Ubuntu:
  New

Bug description:
  When trying to use machinectl import-tar to import a compressed rootfs
  tarball, if the compression is multi-streamed then the import hangs
  after the first stream.

  Either the multi-stream import should work, or it should be detected
  and an error output.

  Environment:
  Ubuntu 17.10 (Artful Aardvark)
  systemd-container 234-2ubuntu12.1

  Steps to reproduce:

  # install systemd-container
  apt-get update && apt-get install systemd-container

  # fetch a multi-stream compressed rootfs
  wget 
http://rpc-repo.rackspace.com/lxc-images/ubuntu/xenial/amd64/default-r14.7.0/20180101/rootfs.tar.xz

  # verify that it has multiple streams
  xz -lvv rootfs.tar.xz

  # try to import it
  machinectl --verify=no import-tar rootfs.tar.xz test

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1742744/+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 1742695] Re: apt-get update silently fails fetching security updates

[Roman Fiedler]

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

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

Title:
  apt-get update silently fails fetching security updates

Status in apt package in Ubuntu:
  New

Bug description:
  On Ubuntu Xenial, apt-get fails silently when security update server
  cannot be reached. This state could be detected by scanning the apt-
  get output afterwards. But manually adding workarounds to each apt-get
  invocation in production automation is prone to error, thus leaving
  machines without security updates.

  Expected behaviour (e.g.):
  * 0 - all OK
  * 1 - temporary failure (e.g. network)
  * 2 - permanent failure

  
  Test:
  * Change your update server IP in /etc/hosts to something unreachable
  * Run apt-get update (might take a while)
  * Check exit status

  
  $ lsb_release -r -d
  Description:Ubuntu 16.04.3 LTS
  Release:16.04
  rfiedler@n3ahit1403:~$ 

  ii  apt 1.2.24
  amd64commandline package manager

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1742695/+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 934291] Re: Deleting or stopping print jobs does not work

[Mario Sánchez Prada]

Sorry for dropping the ball on this one, for some reason I completely
missed all notifications and I only happened to find this bug today
almost by chance :-)

Anyway, if you don't mind me asking... I understand that my workaround
of passing --with-system-groups='lpadmin root' to configure when
building CUPS would no longer be needed with the patches for cups-pk-
helper 0.2.6-1ubuntu2 and 0.2.6-1ubuntu3?

If so, one more question: would this be proposed to Debian? I can't see
them in https://packages.debian.org/sid/cups-pk-helper, but comments in
this thread seem to suggest the intention is to have them there as well.

Many thanks in any case

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

Title:
  Deleting or stopping print jobs does not work

Status in gnome-control-center:
  Incomplete
Status in cups package in Ubuntu:
  Invalid
Status in cups-pk-helper package in Ubuntu:
  In Progress
Status in gnome-control-center package in Ubuntu:
  Invalid

Bug description:
  Deleting or stopping print jobs through the "gnome-control-center -> 
printers" menu is not possible.
  (Black rectangle for stopping can be pressed, nothing happens.)

  Deleting with cups via webinterface does work. ( http://localhost:631/
  )

  Please let me know which information to provide.

  Cheers

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: gnome-control-center 1:3.2.2-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-16.28-generic 3.0.17
  Uname: Linux 3.0.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.23-0ubuntu4
  Architecture: amd64
  Date: Fri Feb 17 16:47:32 2012
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to oneiric on 2011-12-17 (61 days ago)
  usr_lib_gnome-control-center:
   deja-dup   22.0~bzr1290.37~oneiric1
   gnome-bluetooth3.2.0-0ubuntu2
   indicator-datetime 0.3.1-0ubuntu1.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-control-center/+bug/934291/+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 1728560] Re: Cannot resolve smtp-mail.outlook.com

[Jean-Baptiste Lallement]

** Tags removed: wayland-session

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

Title:
  Cannot resolve smtp-mail.outlook.com

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to 17.10, applications can no longer resolve smtp-
  mail.outlook.com, although host can:

  > mjg@payens:~/Projects/GNOME/geary$ telnet smtp-mail.outlook.com 25
  > telnet: could not resolve smtp-mail.outlook.com/25: Temporary failure in 
name resolution
  > mjg@payens:~/Projects/GNOME/geary$ telnet smtp-mail.outlook.com
  > telnet: could not resolve smtp-mail.outlook.com/telnet: Temporary failure 
in name resolution
  > mjg@payens:~/Projects/GNOME/geary$ host smtp-mail.outlook.com
  > smtp-mail.outlook.com is an alias for smtp.live.com.
  > smtp.live.com is an alias for smtp.glbdns2.microsoft.com.
  > smtp.glbdns2.microsoft.com is an alias for smtp.office365.com.
  > smtp.office365.com is an alias for smtp.outlook.office365.com.
  > smtp.outlook.office365.com is an alias for outlook.office365.com.
  > outlook.office365.com is an alias for lb.geo.office365.com.
  > lb.geo.office365.com is an alias for outlook.office365.com.g.office365.com.
  > outlook.office365.com.g.office365.com is an alias for 
outlook-au.office365.com.
  > outlook-au.office365.com has address 40.100.151.226
  > [many more replies snipped]

  Also reported on ask.ubuntu.com:
  https://askubuntu.com/questions/969689/dns-problem-trying-to-ping-or-
  send-email-using-smtp-mail-outlook-com-after-upgra

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12.1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Oct 30 21:07:17 2017
  InstallationDate: Installed on 2015-07-22 (831 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 05ac:0273 Apple, Inc. 
   Bus 001 Device 002: ID 05ac:8290 Apple, Inc. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Apple Inc. MacBookPro12,1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash acpi_backlight=vendor 
i915.fastboot=1 vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/24/2016
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP121.88Z.0167.B18.1610241407
  dmi.board.name: Mac-E43C1C25D4880AD6
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro12,1
  dmi.chassis.type: 9
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-E43C1C25D4880AD6
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP121.88Z.0167.B18.1610241407:bd10/24/2016:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:
  dmi.product.family: MacBook Pro
  dmi.product.name: MacBookPro12,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1728560/+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 1742733] [NEW] Display Bug

[ZMK]

Public bug reported:

When I attempt to use the launcher it will disappear as well as
everything else on the screen. It comes back after a few seconds, but I
am unable to use the dash search at all. If I mouse over the icon for
the search it immediately makes all windows, icons and launcher
disappear. I am unable to power off my computer as well. When I click
shut down it does the same thing as trying to click the search option.
It never did this until the recent most recent updates.

Ubuntu 16.04.3 LTS
Panasonic Toughbook CF-52 Laptop

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
Uname: Linux 4.13.0-26-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Thu Jan 11 11:09:31 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
   Subsystem: Matsushita Electric Industrial Co., Ltd. Mobile 4 Series Chipset 
Integrated Graphics Controller [10f7:8338]
   Subsystem: Matsushita Electric Industrial Co., Ltd. Mobile 4 Series Chipset 
Integrated Graphics Controller [10f7:8338]
InstallationDate: Installed on 2017-12-03 (38 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: Matsushita Electric Industrial Co.,Ltd. CF-52GCMBXAM
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-26-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/11/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: V2.50L16
dmi.board.name: CF52-2L
dmi.board.vendor: Matsushita Electric Industrial Co.,Ltd.
dmi.board.version: 1
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Matsushita Electric Industrial Co.,Ltd.
dmi.chassis.version: 001
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.50L16:bd08/11/2008:svnMatsushitaElectricIndustrialCo.,Ltd.:pnCF-52GCMBXAM:pvr002:rvnMatsushitaElectricIndustrialCo.,Ltd.:rnCF52-2L:rvr1:cvnMatsushitaElectricIndustrialCo.,Ltd.:ct10:cvr001:
dmi.product.family: CF52-2L
dmi.product.name: CF-52GCMBXAM
dmi.product.version: 002
dmi.sys.vendor: Matsushita Electric Industrial Co.,Ltd.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Thu Jan 11 07:56:31 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.5-0ubuntu2~16.04.1
xserver.video_driver: modeset

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


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

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

Title:
  Display Bug

Status in xorg package in Ubuntu:
  New

Bug description:
  When I attempt to use the launcher it will disappear as well as
  everything else on the screen. It comes back after a few seconds, but
  I am unable to use the dash search at all. If I mouse over the icon
  for the search it immediately makes all windows, icons and launcher
  disappear. I am unable to power off my computer as well. When I click
  shut down it does the same thing as trying to click the search option.
  It never did this until the recent most recent updates.

  Ubuntu 16.04.3 LTS
  Panasonic Toughbook CF-52 Laptop

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-26.29~16.04.2-generic 4.13.13
  Uname: Linux 4.13.0-26-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  

[Touch-packages] [Bug 1739531] Re: apport-collect SHOULD NOT collect gnome-shell command history and favorites

[Brian Murray]

** Tags removed: rls-bb-incoming

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

Title:
  apport-collect SHOULD NOT collect gnome-shell command history and
  favorites

Status in apport package in Ubuntu:
  Confirmed
Status in apport source package in Bionic:
  Confirmed

Bug description:
  In https://bugs.launchpad.net/ubuntu/+source/gnome-
  shell/+bug/1739525/comments/4, I ran apport-collect for that bug
  report.

  To my horror, it posted "org.gnome.shell command-history" and "favorites" in 
the "GsettingsChanges.txt"!
  https://launchpadlibrarian.net/349970997/GsettingsChanges.txt

  It's _completely_ reasonable to see:
   * enabled-extensions
   * org.gnome.shell.* diffs
   * org.gnome.desktop.* diffs

  But it is _NOT_ acceptable (privacy reasons) to automatically harvest
  a user's favorites in the gnome-shell, nor their command histories.

  _IF_ we must harvest for bug-data gathering, it MUST come in a secure
  mechanism that is private only to submitter + the assigned dev.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1739531/+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 1233466] Re: Hot-Add Memory failing for lack of udev rule

[Benjamin Drung]

Any updates on this?

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

Title:
  Hot-Add Memory failing for lack of udev rule

Status in udev:
  Unknown
Status in linux package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  It appears that the Hot-Add mechanism is not working because of lack
  of a udev rule. The required rule is attached to this bug. Please
  include it.

  Furthermore, please ensure that the following patches are included:

  https://git.kernel.org/cgit/linux/kernel/git/next/linux-
  next.git/commit/drivers/hv?id=20138d6cb838aa01bb1b382dcb5f3d3a119ff2cb

  https://git.kernel.org/cgit/linux/kernel/git/next/linux-
  next.git/commit/drivers/hv?id=c5e2254f8d63a6654149aa32ac5f2b7dd66a976d

  https://git.kernel.org/cgit/linux/kernel/git/next/linux-
  next.git/commit/drivers/hv?id=ed07ec93e83ec471d365ce084e43ad90fd205903

  The above patches should be in but just wanted to ensure that you guys
  got these.

  Thanks again for the great last minute help.
  Abhishek

To manage notifications about this bug go to:
https://bugs.launchpad.net/udev/+bug/1233466/+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 1663157] Re: Guest session processes are not confined in 16.10 and newer releases

[Balint Reczey]

Reopening, since the guest session is disabled by default but it is
still not confined.

** Changed in: lightdm (Ubuntu)
   Status: Fix Released => Triaged

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

Title:
  Guest session processes are not confined in 16.10 and newer releases

Status in Light Display Manager:
  New
Status in lightdm package in Ubuntu:
  Triaged
Status in lightdm source package in Yakkety:
  Fix Released
Status in lightdm source package in Zesty:
  Fix Released
Status in lightdm source package in Artful:
  Fix Released

Bug description:
  Processes launched under a lightdm guest session are not confined by
  the /usr/lib/lightdm/lightdm-guest-session AppArmor profile in Ubuntu
  16.10, Ubuntu 17.04, and Ubuntu Artful (current dev release). The
  processes are unconfined.

  The simple test case is to log into a guest session, launch a terminal
  with ctrl-alt-t, and run the following command:

   $ cat /proc/self/attr/current

  Expected output, as seen in Ubuntu 16.04 LTS, is:

   /usr/lib/lightdm/lightdm-guest-session (enforce)

  Running the command inside of an Ubuntu 16.10 and newer guest session
  results in:

   unconfined

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1663157/+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 1742714] [NEW] Move mesa-vulkan-drivers from Univers to Main and install by default in Ubuntu 18.04

[Teg]

Public bug reported:

A Vulkan related bug was filed at
https://bugs.launchpad.net/ubuntu/+source/vulkan/+bug/1742711, but in a
related note, having mesa-vulkan-drivers moved from Universe to Main and
installed by default in Ubuntu 18.04 is crucial. Vulkan has gotten
mature and since the OpenGL drivers are installed, it will very
complimentary.

Having this available will aid game developers and users who load up a
Vulkan application and get errors. They may not know to enable Universe
in their Software Manager and to manually install mesa-vulkan-drivers
for their video card. They may just load up that Vulkan application,
find out it doesn't work, and then give up on it. We cannot have that
for future adoption of the API.

Plus, GTK and Qt are adopting Vulkan and applications like Gnome MPV are
implementing experimental support for Vulkan. For Ubuntu being a leader
for the desktop and a base for GNU/Linux gaming, shouldn't it be
painless for Ubuntu 18.04? Especially since it is a long term release
for 5 years.

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


** Tags: mesa vulkan

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

Title:
  Move mesa-vulkan-drivers from Univers to Main and install by default
  in Ubuntu 18.04

Status in mesa package in Ubuntu:
  New

Bug description:
  A Vulkan related bug was filed at
  https://bugs.launchpad.net/ubuntu/+source/vulkan/+bug/1742711, but in
  a related note, having mesa-vulkan-drivers moved from Universe to Main
  and installed by default in Ubuntu 18.04 is crucial. Vulkan has gotten
  mature and since the OpenGL drivers are installed, it will very
  complimentary.

  Having this available will aid game developers and users who load up a
  Vulkan application and get errors. They may not know to enable
  Universe in their Software Manager and to manually install mesa-
  vulkan-drivers for their video card. They may just load up that Vulkan
  application, find out it doesn't work, and then give up on it. We
  cannot have that for future adoption of the API.

  Plus, GTK and Qt are adopting Vulkan and applications like Gnome MPV
  are implementing experimental support for Vulkan. For Ubuntu being a
  leader for the desktop and a base for GNU/Linux gaming, shouldn't it
  be painless for Ubuntu 18.04? Especially since it is a long term
  release for 5 years.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1742714/+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 1742713] [NEW] Move mesa-vulkan-drivers from Univers to Main and install by default in Ubuntu 18.04

[Teg]

Public bug reported:

A Vulkan related bug was filed at
https://bugs.launchpad.net/ubuntu/+source/vulkan/+bug/1742711, but in a
related note, having mesa-vulkan-drivers moved from Universe to Main and
installed by default in Ubuntu 18.04 is crucial. Vulkan has gotten
mature and since the OpenGL drivers are installed, it will very
complimentary.

Having this available will aid game developers and users who load up a
Vulkan application and get errors. They may not know to enable Universe
in their Software Manager and to manually install mesa-vulkan-drivers
for their video card. They may just load up that Vulkan application,
find out it doesn't work, and then give up on it. We cannot have that
for future adoption of the API.

Plus, GTK and Qt are adopting Vulkan and applications like Gnome MPV are
implementing experimental support for Vulkan. For Ubuntu being a leader
for the desktop and a base for GNU/Linux gaming, shouldn't it be
painless for Ubuntu 18.04? Especially since it is a long term release
for 5 years.

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


** Tags: mesa vulkan

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

Title:
  Move mesa-vulkan-drivers from Univers to Main and install by default
  in Ubuntu 18.04

Status in mesa package in Ubuntu:
  New

Bug description:
  A Vulkan related bug was filed at
  https://bugs.launchpad.net/ubuntu/+source/vulkan/+bug/1742711, but in
  a related note, having mesa-vulkan-drivers moved from Universe to Main
  and installed by default in Ubuntu 18.04 is crucial. Vulkan has gotten
  mature and since the OpenGL drivers are installed, it will very
  complimentary.

  Having this available will aid game developers and users who load up a
  Vulkan application and get errors. They may not know to enable
  Universe in their Software Manager and to manually install mesa-
  vulkan-drivers for their video card. They may just load up that Vulkan
  application, find out it doesn't work, and then give up on it. We
  cannot have that for future adoption of the API.

  Plus, GTK and Qt are adopting Vulkan and applications like Gnome MPV
  are implementing experimental support for Vulkan. For Ubuntu being a
  leader for the desktop and a base for GNU/Linux gaming, shouldn't it
  be painless for Ubuntu 18.04? Especially since it is a long term
  release for 5 years.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1742713/+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 1742695] Re: apt-get update silently fails fetching security updates

[Roman Fiedler]

See also
https://unix.stackexchange.com/questions/175146/apt-get-update-exit-status

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

Title:
  apt-get update silently fails fetching security updates

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  On Ubuntu Xenial, apt-get fails silently when security update server
  cannot be reached. This state could be detected by scanning the apt-
  get output afterwards. But manually adding workarounds to each apt-get
  invocation in production automation is prone to error, thus leaving
  machines without security updates.

  Expected behaviour (e.g.):
  * 0 - all OK
  * 1 - temporary failure (e.g. network)
  * 2 - permanent failure

  
  Test:
  * Change your update server IP in /etc/hosts to something unreachable
  * Run apt-get update (might take a while)
  * Check exit status

  
  $ lsb_release -r -d
  Description:Ubuntu 16.04.3 LTS
  Release:16.04
  rfiedler@n3ahit1403:~$ 

  ii  apt 1.2.24
  amd64commandline package manager

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1742695/+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 1742695] Re: apt-get update silently fails fetching security updates

[Roman Fiedler]

Here the output:

# apt-get update

Err:3 http://mirror.[domain]/ubuntu xenial-security InRelease
  Unable to connect to mirror.[domain]:80:
Reading package lists... Done
...
W: Failed to fetch 
http://mirror.[domain]/ubuntu/dists/xenial-security/InRelease  Unable to 
connect to mirror.[domain]:80:
W: Some index files failed to download. They have been ignored, or old ones 
used instead.
# echo $?
0

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

Title:
  apt-get update silently fails fetching security updates

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  On Ubuntu Xenial, apt-get fails silently when security update server
  cannot be reached. This state could be detected by scanning the apt-
  get output afterwards. But manually adding workarounds to each apt-get
  invocation in production automation is prone to error, thus leaving
  machines without security updates.

  Expected behaviour (e.g.):
  * 0 - all OK
  * 1 - temporary failure (e.g. network)
  * 2 - permanent failure

  
  Test:
  * Change your update server IP in /etc/hosts to something unreachable
  * Run apt-get update (might take a while)
  * Check exit status

  
  $ lsb_release -r -d
  Description:Ubuntu 16.04.3 LTS
  Release:16.04
  rfiedler@n3ahit1403:~$ 

  ii  apt 1.2.24
  amd64commandline package manager

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

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

Re: [Touch-packages] [Bug 1726930] Re: System fails to start (boot) on battery due to read-only root file-system

[Ritesh Raj Sarraf]

Okay. Thanks for the reports. It could very well be the flakiness in usb
devices that are causing this problem. Anyways, the best fix for this is to
contain usb execution to the runtime module only.

Note to self: per module activation was reported to not activating general
power savings. Check those before any conclusions

s3nt fr0m a $martph0ne, excuse typ0s

On 11-Jan-2018 15:56, "Douw Steyn" <1726...@bugs.launchpad.net> wrote:

> Works for me too with Ubuntu 17.10 on an Acer Extensa laptop (i5-6200U
> SkyLake). Same symptoms but changing 'force' to 'auto' as above results
> in successful booting from battery.
>
> --
> You received this bug notification because you are subscribed to laptop-
> mode-tools in Ubuntu.
> https://bugs.launchpad.net/bugs/1726930
>
> Title:
>   System fails to start (boot) on battery due to read-only root file-
>   system
>
> Status in laptop-mode-tools package in Ubuntu:
>   Confirmed
> Status in systemd package in Ubuntu:
>   Confirmed
> Status in systemd package in Debian:
>   Fix Released
>
> Bug description:
>   This report is to capture the extended diagnostic efforts done on IRC
>   #ubuntu for user maszlo, who has a Lenovo T450 with SSD that was
>   upgraded from 17.04 to 17.10 and since fails to complete start-up of
>   services when powered on battery.
>
>   We'd previously applied the "acpi=os=! 'acpi_osi=Windows 2015'"
>   workaround in case this was an ACPI DSDT issue.
>
>   This appears to be due to a read-only root file-system. What is not
>   clear is how the rootfs goes read-only.
>
>   The file-system (sda6, ext4) is fsck-ed successfully in the initrd
>   according to the /run/initramfs/fsck.log.
>
>   From the start-up logs (with "systemd.log_level=debug") we see the
>   ext4 driver report a remount operation not once but five times.
>
>   $ grep 'EXT4-fs.*sda6' systemd-debug.log
>   Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): mounted filesystem with
> ordered data mode. Opts: (null)
>   Oct 23 18:10:44 T450s kernel: EXT4-fs (sda6): re-mounted. Opts:
> errors=remount-ro
>   Oct 23 18:10:46 T450s kernel: EXT4-fs (sda6): re-mounted. Opts:
> errors=remount-ro,data=ordered,commit=600
>   Oct 23 18:10:47 T450s kernel: EXT4-fs (sda6): re-mounted. Opts:
> errors=remount-ro,data=ordered,commit=600
>   Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts:
> errors=remount-ro,data=ordered,commit=600
>   Oct 23 18:10:48 T450s kernel: EXT4-fs (sda6): re-mounted. Opts:
> errors=remount-ro,data=ordered,commit=600
>   Oct 23 18:10:49 T450s kernel: EXT4-fs (sda6): re-mounted. Opts:
> errors=remount-ro,data=ordered,commit=600
>
>   Those last five appear to be carrying options generated by laptop-
>   mode-tools.
>
>   User has disabled laptop-mode.service and laptop-mode.timer, and lmt-
>   poll.service, but the issue remains.
>
>   We see several reports of "read-only file-system":
>
>   $ grep 'Read-only' systemd-debug.log
>   Oct 23 18:10:46 T450s grub-common[1792]: grub-editenv: error: cannot
> open `/boot/grub/grubenv': Read-only file system.
>   Oct 23 18:10:46 T450s systemd[1]: colord.service: Failed to run 'start'
> task: Read-only file system
>   Oct 23 18:10:46 T450s gpu-manager[1797]: Warning: writing to
> /var/log/gpu-manager.log failed (Read-only file system)
>   Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to
> run 'start' task: Read-only file system
>   Oct 23 18:10:46 T450s systemd[1]: systemd-resolved.service: Failed to
> run 'start' task: Read-only file system
>   Oct 23 18:10:46 T450s gdm3[1932]: Failed to create LogDir /var/log/gdm3:
> Read-only file system
>   ...
>   Oct 23 18:11:26 T450s cupsd[1461]: Unable to change ownership of
> "/var/log/cups" - Read-only file system
>   Oct 23 18:11:26 T450s cupsd[1461]: Unable to open log file
> "/var/log/cups/access_log" - Read-only file system
>   Oct 23 18:12:52 T450s login[9248]: pam_lastlog(login:session): unable to
> open /var/log/lastlog: Read-only file system
>
>   We also see several problems with systemd's connection to Dbus:
>
>   $ grep 'Transport endpoint' systemd-debug.log
>   Oct 23 18:10:46 T450s systemd[1]: Failed to send job change signal for
> 773: Transport endpoint is not connected
>   Oct 23 18:10:46 T450s systemd[1]: systemd-logind.service: Failed to send
> unit change signal for systemd-logind.service: Transport endpoint is not
> connected
>   Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for
> 156: Transport endpoint is not connected
>   Oct 23 18:10:46 T450s systemd[1]: lmt-poll.service: Failed to send unit
> change signal for lmt-poll.service: Transport endpoint is not connected
>   Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for
> 182: Transport endpoint is not connected
>   Oct 23 18:10:46 T450s systemd[1]: Failed to send job remove signal for
> 95: Transport endpoint is not connected
>   Oct 23 18:10:46 T450s systemd[1]: polkit.service: Failed to send unit
> change signal for polkit.service: Transport 

[Touch-packages] [Bug 1735160] Re: [SRU] Please backport python3-macaroonbakery 0.0.6-1 [universe] from bionic

[Iain Lane]

Uploaded py-macaroon-bakery and pymacaroons to the queue (unapproved and
new respectively). I'll look at the 17.10 stuff after lunch.

** Changed in: pymacaroons (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: py-macaroon-bakery (Ubuntu Xenial)
   Status: New => In Progress

** Changed in: py-macaroon-bakery (Ubuntu Xenial)
 Assignee: (unassigned) => Andrea Azzarone (azzar1)

** Changed in: pymacaroons (Ubuntu Xenial)
 Assignee: (unassigned) => Andrea Azzarone (azzar1)

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

Title:
  [SRU] Please backport python3-macaroonbakery 0.0.6-1 [universe] from
  bionic

Status in httmock package in Ubuntu:
  Fix Released
Status in protobuf package in Ubuntu:
  Fix Released
Status in py-macaroon-bakery package in Ubuntu:
  Fix Released
Status in pymacaroons package in Ubuntu:
  Fix Released
Status in httmock source package in Xenial:
  In Progress
Status in protobuf source package in Xenial:
  In Progress
Status in py-macaroon-bakery source package in Xenial:
  In Progress
Status in pymacaroons source package in Xenial:
  In Progress

Bug description:
  [Impact]
  As part of allowing Ubuntu users to enable canonical-livepatch from 
software-properties GUI 
(https://wiki.ubuntu.com/SoftwareUpdates#Update_settings) we need to backport 
python3-macaroonbakery 0.0.6-1 [universe] from bionic. This will requires quite 
few changes:

  - backport httmock 1.2.6-1 [universe] from bionic - no httmock in xenial
  - backport pymacaroons 0.12.0-1 [universe] from bionic - xenial has 
0.9.2-0ubuntu1
  - SRU some changes in google-apputils-python - 
https://bugs.launchpad.net/ubuntu/+source/google-apputils-python/+bug/1735162
  - add python3-protobuf to python-protobuf 2.6.1-1.3 - Right now the python3 
package is not built.

  [Test case]
  - for protobuf: $ python3 -c "import google.protobuf"
  - for protobuf: $ python2 -c "import google.protobuf"
  - for python3-macaroonbakery: make sure all the tests pass
  - make sure "snapcraft login" works properly

  [Regression Potential]
  - httmock, none has it's not in xenial
  - protobuf, reduced considering that the code has been backported from master 
(small changes to make it compatabile py3 compatabile)
  - pymacaroons, none has 0.12 is backward compatible with 0.9.2
  - py-macaroon-bakery, none has it's not in xenial.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/httmock/+bug/1735160/+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 1742695] Re: apt-get update silently fails fetching security updates

[Julian Andres Klode]

Really? It should print that it could not reach the server. Transient
errors like that are ignored success-state wise so you don't end up with
tons of error messages when you are offline or your connection is
broken.  I want to rework this eventually to give more control on what
constitutes an error, but that's a long way off.

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

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

Title:
  apt-get update silently fails fetching security updates

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  On Ubuntu Xenial, apt-get fails silently when security update server
  cannot be reached. This state could be detected by scanning the apt-
  get output afterwards. But manually adding workarounds to each apt-get
  invocation in production automation is prone to error, thus leaving
  machines without security updates.

  Expected behaviour (e.g.):
  * 0 - all OK
  * 1 - temporary failure (e.g. network)
  * 2 - permanent failure

  
  Test:
  * Change your update server IP in /etc/hosts to something unreachable
  * Run apt-get update (might take a while)
  * Check exit status

  
  $ lsb_release -r -d
  Description:Ubuntu 16.04.3 LTS
  Release:16.04
  rfiedler@n3ahit1403:~$ 

  ii  apt 1.2.24
  amd64commandline package manager

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1742695/+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 1741447] Re: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04

[Timo Aaltonen]

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

this bug is already marked as a dupe of 1735594, and you should have
received further info on how to test fixed packages, no need to test
anything else now

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

Title:
  Unity / Compiz in a crash loop after login, after mesa updates of
  2018-01-04

Status in Mesa:
  New
Status in mesa package in Ubuntu:
  Confirmed
Status in mesa source package in Xenial:
  Confirmed
Status in mesa source package in Artful:
  Confirmed

Bug description:
  GUI is constantly crashing, can't start desktop

  Jan  5 11:21:29 1810 kernel: [  806.368754] compiz[10824]: segfault at 0 ip 
7f83c4f31c16 sp 7ffd48dfc2f0 error 4 in i965_dri.so[7f83c4954000+82d000]
  Jan  5 11:21:40 1810 kernel: [  817.279740] compiz[1]: segfault at 0 ip 
7fda21519c16 sp 7ffd7b40a150 error 4 in i965_dri.so[7fda20f3c000+82d000]
  Jan  5 11:22:30 1810 kernel: [  867.445137] compiz[11271]: segfault at 0 ip 
7f8462855c16 sp 7fff07c857f0 error 4 in i965_dri.so[7f8462278000+82d000]
  Jan  5 11:22:46 1810 kernel: [  883.319195] compiz[11458]: segfault at 0 ip 
7f72b7af0c16 sp 7ffc3b92d830 error 4 in i965_dri.so[7f72b7513000+82d000]
  Jan  5 11:23:01 1810 kernel: [  898.587610] compiz[11516]: segfault at 0 ip 
7fe25113dc16 sp 7ffcf79754c0 error 4 in i965_dri.so[7fe250b6+82d000]

  In /var/crash:
  _usr_bin_compiz.999.crash

  Did manage to start a GUI in Low graphics mode (lowgfx.conf) but this is not 
really usable.
  - dash not working
  - no window switching
  - sometimes all windows disappear for a few seconds

  So effectively my laptop is not usable after latest updates.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity 7.4.0+16.04.20160906-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  .tmp.unity_support_test.0:

  .tmp.unity_support_test.1:

  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Jan  5 11:16:53 2018
  DistUpgraded: 2016-04-22 18:36:32,349 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
     Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:029b]
     Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:029b]
  InstallationDate: Installed on 2014-04-18 (1357 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Acer Aspire 1810TZ
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic 
root=UUID=86d7d9a6-ffc3-47cb-adc4-68cfcbcadcef ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (622 days ago)
  dmi.bios.date: 08/31/2010
  dmi.bios.vendor: INSYDE
  dmi.bios.version: v1.3314
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JM11-MS
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 1
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvrv1.3314:bd08/31/2010:svnAcer:pnAspire1810TZ:pvrv1.3314:rvnAcer:rnJM11-MS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
  dmi.product.name: Aspire 1810TZ
  dmi.product.version: v1.3314
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Fri Jan  5 11:14:24 2018
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

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

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

[Touch-packages] [Bug 1742695] [NEW] apt-get update silently fails fetching security updates

[Roman Fiedler]

Public bug reported:

On Ubuntu Xenial, apt-get fails silently when security update server
cannot be reached. This state could be detected by scanning the apt-get
output afterwards. But manually adding workarounds to each apt-get
invocation in production automation is prone to error, thus leaving
machines without security updates.

Expected behaviour (e.g.):
* 0 - all OK
* 1 - temporary failure (e.g. network)
* 2 - permanent failure


Test:
* Change your update server IP in /etc/hosts to something unreachable
* Run apt-get update (might take a while)
* Check exit status


$ lsb_release -r -d
Description:Ubuntu 16.04.3 LTS
Release:16.04
rfiedler@n3ahit1403:~$ 

ii  apt 1.2.24
amd64commandline package manager

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

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

Title:
  apt-get update silently fails fetching security updates

Status in apt package in Ubuntu:
  New

Bug description:
  On Ubuntu Xenial, apt-get fails silently when security update server
  cannot be reached. This state could be detected by scanning the apt-
  get output afterwards. But manually adding workarounds to each apt-get
  invocation in production automation is prone to error, thus leaving
  machines without security updates.

  Expected behaviour (e.g.):
  * 0 - all OK
  * 1 - temporary failure (e.g. network)
  * 2 - permanent failure

  
  Test:
  * Change your update server IP in /etc/hosts to something unreachable
  * Run apt-get update (might take a while)
  * Check exit status

  
  $ lsb_release -r -d
  Description:Ubuntu 16.04.3 LTS
  Release:16.04
  rfiedler@n3ahit1403:~$ 

  ii  apt 1.2.24
  amd64commandline package manager

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1742695/+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 1741447] Re: Unity / Compiz in a crash loop after login, after mesa updates of 2018-01-04

[mirohe]

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

The ppa: paulo-miguel-dias / pkppa worked but you have freezing from the
desktop from time to time and recover by doing alt-tab or pkill compiz.

It does not work fine. nevertheless in gnme-shell if it works well. for
the moment I stay in this environment until your solution.

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

Title:
  Unity / Compiz in a crash loop after login, after mesa updates of
  2018-01-04

Status in Mesa:
  New
Status in mesa package in Ubuntu:
  Confirmed
Status in mesa source package in Xenial:
  Confirmed
Status in mesa source package in Artful:
  Confirmed

Bug description:
  GUI is constantly crashing, can't start desktop

  Jan  5 11:21:29 1810 kernel: [  806.368754] compiz[10824]: segfault at 0 ip 
7f83c4f31c16 sp 7ffd48dfc2f0 error 4 in i965_dri.so[7f83c4954000+82d000]
  Jan  5 11:21:40 1810 kernel: [  817.279740] compiz[1]: segfault at 0 ip 
7fda21519c16 sp 7ffd7b40a150 error 4 in i965_dri.so[7fda20f3c000+82d000]
  Jan  5 11:22:30 1810 kernel: [  867.445137] compiz[11271]: segfault at 0 ip 
7f8462855c16 sp 7fff07c857f0 error 4 in i965_dri.so[7f8462278000+82d000]
  Jan  5 11:22:46 1810 kernel: [  883.319195] compiz[11458]: segfault at 0 ip 
7f72b7af0c16 sp 7ffc3b92d830 error 4 in i965_dri.so[7f72b7513000+82d000]
  Jan  5 11:23:01 1810 kernel: [  898.587610] compiz[11516]: segfault at 0 ip 
7fe25113dc16 sp 7ffcf79754c0 error 4 in i965_dri.so[7fe250b6+82d000]

  In /var/crash:
  _usr_bin_compiz.999.crash

  Did manage to start a GUI in Low graphics mode (lowgfx.conf) but this is not 
really usable.
  - dash not working
  - no window switching
  - sometimes all windows disappear for a few seconds

  So effectively my laptop is not usable after latest updates.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity 7.4.0+16.04.20160906-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-42.46~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-42-generic x86_64
  .tmp.unity_support_test.0:

  .tmp.unity_support_test.1:

  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Jan  5 11:16:53 2018
  DistUpgraded: 2016-04-22 18:36:32,349 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
     Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:029b]
     Subsystem: Acer Incorporated [ALI] Mobile 4 Series Chipset Integrated 
Graphics Controller [1025:029b]
  InstallationDate: Installed on 2014-04-18 (1357 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Acer Aspire 1810TZ
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-42-generic 
root=UUID=86d7d9a6-ffc3-47cb-adc4-68cfcbcadcef ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (622 days ago)
  dmi.bios.date: 08/31/2010
  dmi.bios.vendor: INSYDE
  dmi.bios.version: v1.3314
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JM11-MS
  dmi.board.vendor: Acer
  dmi.board.version: Base Board Version
  dmi.chassis.type: 1
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvrv1.3314:bd08/31/2010:svnAcer:pnAspire1810TZ:pvrv1.3314:rvnAcer:rnJM11-MS:rvrBaseBoardVersion:cvnChassisManufacturer:ct1:cvrChassisVersion:
  dmi.product.name: Aspire 1810TZ
  dmi.product.version: v1.3314
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Fri Jan  5 11:14:24 2018
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

To manage notifications about this bug go to:

[Touch-packages] [Bug 1730993] Re: Bluetooth stops working shortly after connecting to WiFi

[Krisztian Poos]

Same Issue, 
Lenovo T470P, Thinkpad Laser Bluetooth Mouse, Ubuntu 17.10

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

Title:
  Bluetooth stops working shortly after connecting to WiFi

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  On a Lenovo T570 laptop with an Intel Dual Band Wireless-AC 8265, Wi-
  Fi, 2x2 802.11ac + BT4.2 chipset and a fresh install of Ubuntu 17.10,
  when using WiFi, bluetooth will stop working within a minute or two of
  connecting to WiFI.  Specifically a bluetooth mouse (Logitech
  MXAnywhere2) will stop working under these circumstances and will not
  work again until the laptop is restarted.  This does not happen when
  WiFi is not in use (no network or wired network).  This did not happen
  at all in Ubuntu 17.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  8 10:16:05 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-11-06 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  IpRoute:
   default via 192.168.18.1 dev enp0s31f6 proto static metric 100 
   169.254.0.0/16 dev enp0s31f6 scope link metric 1000 
   172.16.208.0/24 dev vmnet1 proto kernel scope link src 172.16.208.1 
   192.168.18.0/24 dev enp0s31f6 proto kernel scope link src 192.168.18.39 
metric 100 
   192.168.85.0/24 dev vmnet8 proto kernel scope link src 192.168.85.1
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1730993/+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 873712] Re: Lack of GstMiniObject means Gst.Message is broken, can't get EOS signal

[Bug Watch Updater]

** Changed in: pygobject
   Status: Confirmed => Expired

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

Title:
  Lack of GstMiniObject means Gst.Message is broken, can't get EOS
  signal

Status in Novacut:
  Won't Fix
Status in pygobject:
  Expired
Status in pygobject package in Ubuntu:
  Invalid

Bug description:
  It's almost possible to use GStreamer from PyGI.  The hang up is that
  currently you can't get EOS signals from a pipeline, and that the
  message bus is overall broken.

  As far as I know, this is because pygobject doesn't grok the
  GstMiniObject type, which mean Gst.Message is an unknown type.  There
  is an upstream bug with a patch (work in progress):

  https://bugzilla.gnome.org/show_bug.cgi?id=631901

  I'm not sure if this would be too invasive a change to deliver to
  Oneiric users through a SRU, but this would help smooth the transition
  to PyGI (and possibly only shipping Python3 on the CD) for Precise as
  app devs could be working with PyGI and GStreamer right now on
  Oneiric.

  For what it's worth, this would really help Novacut.  Either way, lets
  make sure PyGI + GStreamer rocks in Precise!

  (Side note: this also raises a question... GStreamer 0.10 or 1.0 in
  Precise?)

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: python3-gobject 3.0.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic x86_64
  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  Date: Thu Oct 13 15:24:09 2011
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110921.2)
  ProcEnviron:
   PATH=(custom, user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pygobject
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/novacut/+bug/873712/+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 1736757] Re: [PATCH] Avahi does not support local-only services via the loopback interface

[Sebastien Bacher]

** Changed in: avahi (Ubuntu)
   Status: In Progress => Fix Committed

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

Title:
  [PATCH] Avahi does not support local-only services via the loopback
  interface

Status in avahi package in Ubuntu:
  Fix Committed

Bug description:
  To allow the more sophisticated functionality of IPP network printers (web 
admin interface, query printer capabilities and job status from printer) also 
on USB printers, newer USB printers support the IPP-over-USB standard which is 
supported under Linux via the ippusbxd package from OpenPrinting. The ippusbxd 
daemon connects to the USB printer and mirrors it into a virtual IPP network 
printer on localhost, port 6.
  CUPS and cups-browsed find IPP printers by the printer's DNS-SD broadcasts. 
On Linux systems avahi-daemon is handling the registration of local services 
and also the discovery of remote services. This works well with local services 
shared to the network as Avahi does appropriate broadcasts on network 
interfaces (eth0, wlan0, ...) but Avahi does not handle the loopback device lo 
for local services ("localhost"). So the local-only IPP-over-USB printer on 
localhost:6, registered by ippusbxd does not get advertised, not even 
locally.
  The attached patchfor the Ubuntu package of Avahi adds support for such 
services.
  See also the upstream bug report https://github.com/lathiat/avahi/issues/125

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1736757/+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 1735160] Re: [SRU] Please backport python3-macaroonbakery 0.0.6-1 [universe] from bionic

[Andrea Azzarone]

Oh I removed the python3 patch from the series but the not actual file.

Regarding 17.10 sil2100 confirmed me that this is required. But at least
it's going to be easier considering that:

- python3-httmock is already in artful (1.2.6-1 universe)
- python3-protobuf is already in artful (3.0.0-9ubuntu5 universe) (so no need 
to apply the nacl patch in py-macaroon-bakery)
- python3-nacl's version of artful is 1.1.1-1build2 (so no need to apply the 
nacl patch in py-macaroon-bakery)

The only things to be done are:
- target 
https://bugs.launchpad.net/ubuntu/+source/google-apputils-python/+bug/1735162 
for 17.10 too
- relax python3-six deps in py-macaroon-bakery
- SRU python3-pymacaroons

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

Title:
  [SRU] Please backport python3-macaroonbakery 0.0.6-1 [universe] from
  bionic

Status in httmock package in Ubuntu:
  Fix Released
Status in protobuf package in Ubuntu:
  Fix Released
Status in py-macaroon-bakery package in Ubuntu:
  Fix Released
Status in pymacaroons package in Ubuntu:
  Fix Released
Status in httmock source package in Xenial:
  In Progress
Status in protobuf source package in Xenial:
  In Progress
Status in py-macaroon-bakery source package in Xenial:
  New
Status in pymacaroons source package in Xenial:
  New

Bug description:
  [Impact]
  As part of allowing Ubuntu users to enable canonical-livepatch from 
software-properties GUI 
(https://wiki.ubuntu.com/SoftwareUpdates#Update_settings) we need to backport 
python3-macaroonbakery 0.0.6-1 [universe] from bionic. This will requires quite 
few changes:

  - backport httmock 1.2.6-1 [universe] from bionic - no httmock in xenial
  - backport pymacaroons 0.12.0-1 [universe] from bionic - xenial has 
0.9.2-0ubuntu1
  - SRU some changes in google-apputils-python - 
https://bugs.launchpad.net/ubuntu/+source/google-apputils-python/+bug/1735162
  - add python3-protobuf to python-protobuf 2.6.1-1.3 - Right now the python3 
package is not built.

  [Test case]
  - for protobuf: $ python3 -c "import google.protobuf"
  - for protobuf: $ python2 -c "import google.protobuf"
  - for python3-macaroonbakery: make sure all the tests pass
  - make sure "snapcraft login" works properly

  [Regression Potential]
  - httmock, none has it's not in xenial
  - protobuf, reduced considering that the code has been backported from master 
(small changes to make it compatabile py3 compatabile)
  - pymacaroons, none has 0.12 is backward compatible with 0.9.2
  - py-macaroon-bakery, none has it's not in xenial.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/httmock/+bug/1735160/+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 1735160] Re: [SRU] Please backport python3-macaroonbakery 0.0.6-1 [universe] from bionic

[Andrea Azzarone]

** Description changed:

  [Impact]
  As part of allowing Ubuntu users to enable canonical-livepatch from 
software-properties GUI 
(https://wiki.ubuntu.com/SoftwareUpdates#Update_settings) we need to backport 
python3-macaroonbakery 0.0.6-1 [universe] from bionic. This will requires quite 
few changes:
  
  - backport httmock 1.2.6-1 [universe] from bionic - no httmock in xenial
  - backport pymacaroons 0.12.0-1 [universe] from bionic - xenial has 
0.9.2-0ubuntu1
  - SRU some changes in google-apputils-python - 
https://bugs.launchpad.net/ubuntu/+source/google-apputils-python/+bug/1735162
  - add python3-protobuf to python-protobuf 2.6.1-1.3 - Right now the python3 
package is not built.
  
  [Test case]
  - for python3-protobuf: $ python3 -c "import google.protobuf"
  - for python3-macaroonbakery: make sure all the tests pass
+ - make sure "snapcraft login" works properly
  
  [Regression Potential]
  - httmock, none has it's not in xenial
- - python3-protobuf, none has the python2 code was not edited
- TBC
+ - protobuf, reduced considering that the code has been backported from master 
(small changes to make it compatabile py3 compatabile)
  - pymacaroons, none has 0.12 is backward compatible with 0.9.2
- - python3-protobuf, none has it's not in xenial.
+ - py-macaroon-bakery, none has it's not in xenial.

** Description changed:

  [Impact]
  As part of allowing Ubuntu users to enable canonical-livepatch from 
software-properties GUI 
(https://wiki.ubuntu.com/SoftwareUpdates#Update_settings) we need to backport 
python3-macaroonbakery 0.0.6-1 [universe] from bionic. This will requires quite 
few changes:
  
  - backport httmock 1.2.6-1 [universe] from bionic - no httmock in xenial
  - backport pymacaroons 0.12.0-1 [universe] from bionic - xenial has 
0.9.2-0ubuntu1
  - SRU some changes in google-apputils-python - 
https://bugs.launchpad.net/ubuntu/+source/google-apputils-python/+bug/1735162
  - add python3-protobuf to python-protobuf 2.6.1-1.3 - Right now the python3 
package is not built.
  
  [Test case]
- - for python3-protobuf: $ python3 -c "import google.protobuf"
+ - for protobuf: $ python3 -c "import google.protobuf"
+ - for protobuf: $ python2 -c "import google.protobuf"
  - for python3-macaroonbakery: make sure all the tests pass
  - make sure "snapcraft login" works properly
  
  [Regression Potential]
  - httmock, none has it's not in xenial
  - protobuf, reduced considering that the code has been backported from master 
(small changes to make it compatabile py3 compatabile)
  - pymacaroons, none has 0.12 is backward compatible with 0.9.2
  - py-macaroon-bakery, none has it's not in xenial.

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

Title:
  [SRU] Please backport python3-macaroonbakery 0.0.6-1 [universe] from
  bionic

Status in httmock package in Ubuntu:
  Fix Released
Status in protobuf package in Ubuntu:
  Fix Released
Status in py-macaroon-bakery package in Ubuntu:
  Fix Released
Status in pymacaroons package in Ubuntu:
  Fix Released
Status in httmock source package in Xenial:
  In Progress
Status in protobuf source package in Xenial:
  In Progress
Status in py-macaroon-bakery source package in Xenial:
  New
Status in pymacaroons source package in Xenial:
  New

Bug description:
  [Impact]
  As part of allowing Ubuntu users to enable canonical-livepatch from 
software-properties GUI 
(https://wiki.ubuntu.com/SoftwareUpdates#Update_settings) we need to backport 
python3-macaroonbakery 0.0.6-1 [universe] from bionic. This will requires quite 
few changes:

  - backport httmock 1.2.6-1 [universe] from bionic - no httmock in xenial
  - backport pymacaroons 0.12.0-1 [universe] from bionic - xenial has 
0.9.2-0ubuntu1
  - SRU some changes in google-apputils-python - 
https://bugs.launchpad.net/ubuntu/+source/google-apputils-python/+bug/1735162
  - add python3-protobuf to python-protobuf 2.6.1-1.3 - Right now the python3 
package is not built.

  [Test case]
  - for protobuf: $ python3 -c "import google.protobuf"
  - for protobuf: $ python2 -c "import google.protobuf"
  - for python3-macaroonbakery: make sure all the tests pass
  - make sure "snapcraft login" works properly

  [Regression Potential]
  - httmock, none has it's not in xenial
  - protobuf, reduced considering that the code has been backported from master 
(small changes to make it compatabile py3 compatabile)
  - pymacaroons, none has 0.12 is backward compatible with 0.9.2
  - py-macaroon-bakery, none has it's not in xenial.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/httmock/+bug/1735160/+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 1735594] Re: [regression] compiz crashes after Mesa upgrade

[Chris Perry]

sudo apt-add-repository ppa:tjaalton/ppa seems to have worked for me.
Brief system details:

cpu:
   Intel(R) Core(TM)2 Duo CPU T7100  @ 1.80GHz, 1800 MHz
   Intel(R) Core(TM)2 Duo CPU T7100  @ 1.80GHz, 1800 MHz
keyboard:
  /dev/input/event3AT Translated Set 2 keyboard
graphics card:
   Lenovo ThinkPad T61/R61
   Lenovo ThinkPad T61/R61

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

Title:
  [regression] compiz crashes after Mesa upgrade

Status in mesa package in Ubuntu:
  Confirmed
Status in mesa source package in Xenial:
  Confirmed
Status in mesa source package in Artful:
  Confirmed

Bug description:
  [Impact]
  When I use the Unity session I automatically get logged out under these 
conditions:

  When I hover with my mouse over any icon of the sidebar.
  When I press the alt key.
  When I press the super key.

  running dmesg after this unwanted logout happens I get following
  information:

  compiz[10616]: segfault at 0 ip 7fbca309feeb sp 7fff5f59a4d0
  error 4 in i965_dri.so[7fbca2af6000+7e4000]

  This is caused by a mesa upgrade, which added a patch for bug #1727401. The 
crasher is reproduced on:
  - gen4 / gen5 Intel
  - if using modesetting X driver, like when xserver-xorg-video-intel is not 
installed, or the HWE stack is installed (xserver-xorg-core-hwe-16.04 defaults 
to modesetting)

  [Test case]
  Log in to Unity, open the dash or try to log out etc. Compiz shouldn't crash.

  [Regression potential]
  The backported patches need to be tested, here for regressions and on 1727401 
that they fix the original bug (again).

  Best to test on a wide array of Intel HW:
  gen4 (965GM/GM45/G45)
  gen5 (Ironlake)
  gen6 (Sandy Bridge)
  gen7 (Bay Trail, Ivy Bridge, Haswell)
  gen8 (Braswell, Broadwell)
  gen9 (Apollo Lake, Skylake, Gemini Lake, Kaby Lake, Coffee Lake)

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