[Touch-packages] [Bug 1746342] Re: Boot hangs on passphrase prompt for encrypted root file system with NVidia proprietary driver

[Marc Deslauriers]

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

** Information type changed from Private Security to Public

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

Title:
  Boot hangs on passphrase prompt for encrypted root file system with
  NVidia proprietary driver

Status in xorg package in Ubuntu:
  New

Bug description:
  During installation of Ubuntu 17.10.1, I checked the box for installing 
proprietary drivers,
  but on the initial (successful) boot after installation it came up running 
the Nouveau driver,
  and then I was prompted to select the proprietary drivers I wanted: NVidia & 
AMD64 Microcode.
  I selected both.

  Rebooting to the default Ubuntu grub entry fails at the passphrase prompt for 
the root file system.
  There is a graphic prompt for the passphrase, but there appears to be no 
response to key strokes.
  But passphrase actually appears in clear text on virtual terminal 7 when 
switched to.
  Unsuspecting users may enter their passphrase and walk away with their 
computer on (e.g. to get help) and anyone else with physical access potentially 
could discover their passphrase in the meantime.

  This happened with the initial nvidia driver: nvidia-384:amd64 
384.111-0ubuntu0.17.10.1
  But continues to happen after upgrading to: nvidia-390:amd64 390.12-0ubuntu1
  Likewise it occurs with both kernels 4.13.0-21 & 4.13.0-31

  The following work around the bug:
  1. Boot in recovery mode.  Then select "Resume normal boot" twice.
 (Alternatively, open recovery shell and exit it to resume booting.)
  2. But I preferred to modify /etc/default/grub as follows:
  Replacing:
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
  with
GRUB_CMDLINE_LINUX_DEFAULT=""
  and adding:
GRUB_TERMINAL=console
GRUB_GFXPAYLOAD_LINUX=text

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..0e.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:0e:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.12  Wed Dec 20 07:19:16 
PST 2017
   GCC version:  gcc version 7.2.0 (Ubuntu 7.2.0-8ubuntu3)
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 30 13:18:33 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.13.0-21-generic, x86_64: installed
   bbswitch, 0.8, 4.13.0-31-generic, x86_64: installed
   nvidia-390, 390.12, 4.13.0-31-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] GP106 [GeForce GTX 
1060 6GB] [1462:3281]
  InstallationDate: Installed on 2018-01-22 (8 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=dumb
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-31-generic 
root=UUID=10f30b03-9566-4d46-997f-c80b29dd3589 ro rootflags=subvol=@
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P3.20
  dmi.board.name: X370 Taichi
  dmi.board.vendor: ASRock
  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.:bvrP3.20:bd09/08/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnX370Taichi:rvr: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.
  

[Touch-packages] [Bug 1745782] Re: package avahi-daemon 0.7-3ubuntu2 failed to install/upgrade: installed avahi-daemon package post-installation script subprocess returned error exit status 1

[Marc Deslauriers]

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

** Information type changed from Private Security to Public

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

Title:
  package avahi-daemon 0.7-3ubuntu2 failed to install/upgrade: installed
  avahi-daemon package post-installation script subprocess returned
  error exit status 1

Status in avahi package in Ubuntu:
  New

Bug description:
  will not load

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: avahi-daemon 0.7-3ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  Date: Sat Jan 27 16:31:32 2018
  ErrorMessage: installed avahi-daemon package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2018-01-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180127)
  Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
  RelatedPackageVersions:
   dpkg 1.19.0.4ubuntu1
   apt  1.6~alpha5
  SourcePackage: avahi
  Title: package avahi-daemon 0.7-3ubuntu2 failed to install/upgrade: installed 
avahi-daemon package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1745782/+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 1746070] Re: sometime screen automatically blink.

[Marc Deslauriers]

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

** Information type changed from Private Security to Public

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

Title:
  sometime screen automatically blink.

Status in xorg package in Ubuntu:
  New

Bug description:
  i dont know where is the bug..
  sometimes screen blink.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-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: Tue Jan 30 00:00:13 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Broadwell-U Integrated Graphics 
[1043:10d0]
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:57de Realtek Semiconductor Corp. 
   Bus 001 Device 004: ID 13d3:3423 IMC Networks 
   Bus 001 Device 006: ID 054c:05ba Sony Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X540LA
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=04c2bf43-a7a0-458c-bd06-895077380ad8 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/14/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X540LA.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X540LA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX540LA.204:bd03/14/2016:svnASUSTeKCOMPUTERINC.:pnX540LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX540LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X540LA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  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: Mon Jan 29 21:18:05 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/1746070/+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 1690336] Re: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Terminated)

[dino99]

That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml

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

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

Title:
  package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade:
  subprocess installed post-installation script was killed by signal
  (Terminated)

Status in gconf package in Ubuntu:
  Invalid

Bug description:
   bug

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Wed May 10 18:56:29 2017
  DuplicateSignature:
   package:gconf2-common:3.2.6-3ubuntu7
   Setting up gconf2-common (3.2.6-3ubuntu7) ...
   dpkg: error processing package gconf2-common (--configure):
subprocess installed post-installation script was killed by signal 
(Terminated)
  ErrorMessage: subprocess installed post-installation script was killed by 
signal (Terminated)
  InstallationDate: Installed on 2017-05-10 (1 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
subprocess installed post-installation script was killed by signal (Terminated)
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1690336/+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 1689774] Re: package sudo 1.8.19p1-1ubuntu1 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1

[dino99]

That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml

** Changed in: sudo (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  package sudo 1.8.19p1-1ubuntu1 failed to install/upgrade: subprocess
  installed pre-removal script returned error exit status 1

Status in sudo package in Ubuntu:
  Invalid

Bug description:
  Error found when install TeamViewer and Prey Project.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: sudo 1.8.19p1-1ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Wed May 10 16:12:30 2017
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 1
  InstallationDate: Installed on 2017-05-10 (0 days ago)
  InstallationMedia: Lubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: sudo
  Title: package sudo 1.8.19p1-1ubuntu1 failed to install/upgrade: subprocess 
installed pre-removal script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  VisudoCheck:
   /etc/sudoers: parsed OK
   /etc/sudoers.d/README: parsed OK

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1689774/+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 1689751] Re: lightdm takes 500 seconds to start

[dino99]

That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml

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

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

Title:
  lightdm takes 500 seconds to start

Status in lightdm package in Ubuntu:
  Invalid

Bug description:
  On ubuntu 17.04
  In the live CD and on an upgraded system (upgraded from 16.10).
  On boot and on logout or switch user.
  lightdm takes 500seconds (roughly) to start.
  This is on a fujitsu lifebook t-900 with i5 and 4GB RAM.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: lightdm 1.22.0-0ubuntu2
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic i686
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: i386
  CurrentDesktop: Unity:Unity7
  Date: Wed May 10 09:25:11 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-01-26 (103 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release i386 (20161012.2)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1689751/+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 1732865] Re: [LTCTest][OPAL][FW860.20] lscpu failed to list cpu max and min frequencies

[Julian Andres Klode]

I backported the patches from the upstream git rather than using the
patch in here in order to stay closer to upstream. It seems it's not
possible to test this in a QEMU VM and it sounds scary to try it on a
real productive machine, so I'll probably just go ahead and upload it
later, and then it hopefully can be verified in proposed by someone on a
real machine.

** Patch added: "util-linux-lp1732865.diff"
   
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1732865/+attachment/5047552/+files/util-linux-lp1732865.diff

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

Title:
  [LTCTest][OPAL][FW860.20] lscpu failed to list cpu max and min
  frequencies

Status in The Ubuntu-power-systems project:
  Triaged
Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Xenial:
  In Progress
Status in util-linux source package in Artful:
  Fix Released

Bug description:
  [Test case]
  1. Clone https://github.com/open-power/op-test-framework
  2. Run this command to GUARD the cpu.
  ./op-test --bmc-type FSP --bmc-ip $FSPIP --bmc-username dev --bmc-password 
FipSdev --host-ip $HOSTIP --host-user root --host-password passw0rd --ffdcdir 
test-reports/ --run testcases.OpTestHMIHandling.MalfunctionAlert
  3. Repeat again, so that multiple CPUs are guarded.
  4. Run lscpu
  5. Observe that no CPU frequencies are displayed:
  CPU max MHz: (null)
  CPU min MHz: (null)
  6. Install util-linux from -proposed.
  7. Run lscpu again
  8. Observe that max and min CPU frequencies are correctly displayed.

  == Comment: #0 - Pridhiviraj Paidipeddi  - 2017-01-03 
05:34:32 ==
  ---Problem Description---
  After 3 CPU's are garded, lscpu failed to list CPU max and min frequencies

  Contact Information = ppaid...@in.ibm.com

  ---uname output---
  Linux p8wookie 4.8.0-32-generic #34~16.04.1-Ubuntu SMP Tue Dec 13 17:01:57 
UTC 2016 ppc64le ppc64le ppc64le GNU/Linux

  Machine Type = PowerNV 8284-22A

  ---Debugger---
  A debugger is not configured

  ---Steps to Reproduce---
   1. Read lscpu output
  2. Inject HMI Non recoverable error three times
  3. Read lscpu output again
  compare the output cpu frequencies will list as NULL

  Stack trace output:
   no

  Oops output:
   no

  Userspace tool common name: lscpu

  Userspace rpm: util-linux

  The userspace tool has the following bit modes: 64-bit

  System Dump Info:
    The system is not configured to capture a system dump.

  Userspace tool obtained from project website:  na

  *Additional Instructions for ppaid...@in.ibm.com:
  -Post a private note with access information to the machine that the bug is 
occuring on.
  -Attach sysctl -a output output to the bug.
  -Attach ltrace and strace of userspace application.

  Before CPU's are garded:
  root@p8wookie:~# lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):112
  On-line CPU(s) list:   0-71,80-103,112-127
  Thread(s) per core:8
  Core(s) per socket:3
  Socket(s): 4
  NUMA node(s):  4
  Model: 2.1 (pvr 004b 0201)
  Model name:POWER8E (raw), altivec supported
  CPU max MHz:   4322.
  CPU min MHz:   2061.
  L1d cache: 64K
  L1i cache: 32K
  L2 cache:  512K
  L3 cache:  8192K
  NUMA node0 CPU(s): 0-31
  NUMA node1 CPU(s): 32-63
  NUMA node16 CPU(s):64-71,80-95
  NUMA node17 CPU(s):96-103,112-127

  After 4 cores are garded:
  root@p8wookie:~# lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):96
  On-line CPU(s) list:   8-55,64-71,80-103,112-127
  Thread(s) per core:8
  Core(s) per socket:3
  Socket(s): 4
  NUMA node(s):  4
  Model: 2.1 (pvr 004b 0201)
  Model name:POWER8E (raw), altivec supported
  CPU max MHz:   (null)
  CPU min MHz:   (null)
  L1d cache: 64K
  L1i cache: 32K
  L2 cache:  512K
  L3 cache:  8192K
  NUMA node0 CPU(s): 8-31
  NUMA node1 CPU(s): 32-55
  NUMA node16 CPU(s):64-71,80-95
  NUMA node17 CPU(s):96-103,112-127

  == Comment: #1 - Pridhiviraj Paidipeddi  - 2017-01-11 
07:06:59 ==
  root@p8wookie:~# dmesg |grep -i powernv
  [0.00] Using PowerNV machine description
  [0.331564] EEH: PowerNV platform initialized
  [0.907250] powernv-rng: Registering arch random hook.
  [1.504063] powernv-cpufreq: cpufreq pstate min -68 nominal -5 max 0
  [1.507167] powernv_idle_driver registered
  [   34.184048] powernv_rng: Registered powernv hwrng.
  [   34.185619] ipmi-powernv ibm,opal:ipmi: Unable to map irq from device tree
  [   34.210966] ipmi-powernv ibm,opal:ipmi: Found new BMC (man_id: 0x00, 

[Touch-packages] [Bug 1560804] Re: kscreen reports change of primary screen without apparent reason

[Lars Kollstedt]

Hello together,

this seems to affect me, too. On Ubuntu 16.4 LTS.

Lots off Syslog lines with:
Feb  2 12:44:01 ws-kollstedt org.kde.KScreen[1925]: kscreen: Primary output 
changed from KScreen::Output(Id: 638 , Name: "DVI-I-1" ) ( "DVI-I-1" ) to 
KScreen::Output(Id: 638 , Name: "DVI-I-1" ) ( "DVI-I-1" )
Feb  2 12:44:01 ws-kollstedt org.kde.KScreen[1925]: kscreen: Primary output 
changed from KScreen::Output(Id: 638 , Name: "DVI-I-1" ) ( "DVI-I-1" ) to 
KScreen::Output(Id: 638 , Name: "DVI-I-1" ) ( "DVI-I-1" )

Changes from and to seems to be the same.

Possible side effect, but Im not sure it correlates:
Sometimes the Screen freezes, and after appox 30 seconds the System reboots.


Usually it still works. The toggeling Screen was something i experienced on 
2016-11-07, I resolved this by switching to the nvidia-367 package.


root@ws-kollstedt:/home/kollstedt# lshw
[...]
product: GF119 [GeForce GT 610]
vendor: NVIDIA Corporation
[...]

root@ws-kollstedt:/home/kollstedt# aptitude search nvidia | egrep '^i'
i   nvidia-367  - Transitional package for nvidia-375   
i A nvidia-375  - Transitional package for nvidia-384   
i A nvidia-384  - NVIDIA binary driver - version 384.111
i   nvidia-modprobe - utility to load NVIDIA kernel modules and 
i A nvidia-opencl-icd-384   - NVIDIA OpenCL ICD 
i A nvidia-prime- Tools to enable NVIDIA's Prime
i   nvidia-settings - Tool for configuring the NVIDIA graphics d

root@ws-kollstedt:/home/kollstedt# uname -a
Linux ws-kollstedt 4.4.0-112-generic #135-Ubuntu SMP Fri Jan 19 11:48:36 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

Not sure obout the reasons, this looks for me only like the symptoms.
;-)

Kind regards,
Lars

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

Title:
  kscreen reports change of primary screen without apparent reason

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Screen blanks out to black frequently for no apparent reason no matter
  how short or long the session. Also, in the items attached below was
  created using "xdiagnose". It didn't include SDDM.log which I am using
  but instead LightDM which I am *not* using.

  =

  From Xorg.0.log:

  Mar 22 21:53:53 HINGE11 org.kde.KScreen[2724]: message repeated 15
  times: [ kscreen: Primary output changed from KScreen::Output(Id: 591
  , Name: "HDMI-0" ) ( "HDMI-0" ) to KScreen::Output(Id: 591 , Name:
  "HDMI-0" ) ( "HDMI-0" )]

  
  ==
  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4
  Uname: Linux 4.2.0-34-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.96  Sun Nov  8 22:33:28 
PST 2015
   GCC version:  gcc version 5.2.1 20151010 (Ubuntu 5.2.1-22ubuntu2)
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  Date: Tue Mar 22 21:52:10 2016
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GT216 [GeForce GT 220] [10de:0a20] (rev a2) (prog-if 00 
[VGA controller])
     Subsystem: Gigabyte Technology Co., Ltd Device [1458:34d6]
  InstallationDate: Installed on 2012-09-14 (1286 days ago)
  InstallationMedia: Kubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120820.1)
  LightdmGreeterLog:
   QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such 
file or directory
   QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus
   Bus::open: Can not get ibus-daemon's address.
   IBusInputContext::createInputContext: no connection to ibus-daemon
  LightdmGreeterLogOld:
   QInotifyFileSystemWatcherEngine::addPaths: inotify_add_watch failed: No such 
file or directory
   QFileSystemWatcher: failed to add paths: /var/lib/lightdm/.config/ibus/bus
   Bus::open: Can not get ibus-daemon's address.
   IBusInputContext::createInputContext: no connection to ibus-daemon
  MachineType: Gigabyte Technology Co., Ltd. GA-990XA-UD3
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.2.0-34-generic 
root=UUID=bfef49a0-28c1-480e-95b6-b010e6f905a8 ro quiet splash nomodeset 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/13/2011
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F9
  dmi.board.name: GA-990XA-UD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  

[Touch-packages] [Bug 1739469] Re: FTBFS in bionic

[Launchpad Bug Tracker]

This bug was fixed in the package pulseaudio - 1:11.1-1ubuntu5

---
pulseaudio (1:11.1-1ubuntu5) bionic; urgency=medium

  * Drop use of trust-store, which is unmaintained and fails to build.
LP: #1739469.

 -- Steve Langasek   Thu, 01 Feb 2018
16:12:47 -0800

** Changed in: pulseaudio (Ubuntu)
   Status: Fix Committed => 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/1739469

Title:
  FTBFS in bionic

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in trust-store package in Ubuntu:
  Fix Released

Bug description:
  A rebuild of trust-store for the new boost ABI fails in bionic:

  /usr/bin/cc -g -O2 
-fdebug-prefix-map=/<>/trust-store-2.0.0+16.04.20160119=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2 -Werror -Wall -pedantic -Wextra -fPIC -fvisibility=hidden 
-pthread -DCHECK_FUNCTION_EXISTS=pthread_create  -Wl,-Bsymbolic-functions 
-Wl,-z,relro  -rdynamic CMakeFiles/cmTC_75174.dir/CheckFunctionExists.c.o  -o 
cmTC_75174 -lpthreads 
  /usr/bin/ld: cannot find -lpthreads
  collect2: error: ld returned 1 exit status

  If anyone cares about this package for bionic, they will need to
  resolve this.  Otherwise, the build-dependency from pulseaudio to
  trust-store should be dropped and trust-store should be removed from
  the archive.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1739469/+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 1745810] Re: package systemd 235-3ubuntu3 failed to install/upgrade: triggers looping, abandoned

[Marc Deslauriers]

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

** Information type changed from Private Security to Public

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

Title:
  package systemd 235-3ubuntu3 failed to install/upgrade: triggers
  looping, abandoned

Status in systemd package in Ubuntu:
  New

Bug description:
  i dont know

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd 235-3ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  Date: Sun Jan 28 00:49:05 2018
  ErrorMessage: triggers looping, abandoned
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=5d3f26c9-f26e-4726-b062-a1cb855198e5 ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.19.0.4ubuntu1
   apt  1.6~alpha5
  SourcePackage: systemd
  SystemdDelta:
   [MASKED] /etc/systemd/system/samba-ad-dc.service → 
/lib/systemd/system/samba-ad-dc.service
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   3 overridden configuration files found.
  Title: package systemd 235-3ubuntu3 failed to install/upgrade: triggers 
looping, abandoned
  UpgradeStatus: Upgraded to bionic on 2018-01-27 (0 days ago)
  dmi.bios.date: 12/24/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A88XN-WIFI
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF6:bd12/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XN-WIFI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1745810/+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 1745810] Re: package systemd 235-3ubuntu3 failed to install/upgrade: triggers looping, abandoned

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package systemd 235-3ubuntu3 failed to install/upgrade: triggers
  looping, abandoned

Status in systemd package in Ubuntu:
  New

Bug description:
  i dont know

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd 235-3ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  Date: Sun Jan 28 00:49:05 2018
  ErrorMessage: triggers looping, abandoned
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=5d3f26c9-f26e-4726-b062-a1cb855198e5 ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 
2.7.14-2ubuntu1
  RelatedPackageVersions:
   dpkg 1.19.0.4ubuntu1
   apt  1.6~alpha5
  SourcePackage: systemd
  SystemdDelta:
   [MASKED] /etc/systemd/system/samba-ad-dc.service → 
/lib/systemd/system/samba-ad-dc.service
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   3 overridden configuration files found.
  Title: package systemd 235-3ubuntu3 failed to install/upgrade: triggers 
looping, abandoned
  UpgradeStatus: Upgraded to bionic on 2018-01-27 (0 days ago)
  dmi.bios.date: 12/24/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F6
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: F2A88XN-WIFI
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF6:bd12/24/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnF2A88XN-WIFI:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.: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: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1745810/+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 1745782] Re: package avahi-daemon 0.7-3ubuntu2 failed to install/upgrade: installed avahi-daemon package post-installation script subprocess returned error exit status 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package avahi-daemon 0.7-3ubuntu2 failed to install/upgrade: installed
  avahi-daemon package post-installation script subprocess returned
  error exit status 1

Status in avahi package in Ubuntu:
  New

Bug description:
  will not load

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: avahi-daemon 0.7-3ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  Date: Sat Jan 27 16:31:32 2018
  ErrorMessage: installed avahi-daemon package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2018-01-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180127)
  Python3Details: /usr/bin/python3.6, Python 3.6.4, python3-minimal, 
3.6.3-0ubuntu2
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
  RelatedPackageVersions:
   dpkg 1.19.0.4ubuntu1
   apt  1.6~alpha5
  SourcePackage: avahi
  Title: package avahi-daemon 0.7-3ubuntu2 failed to install/upgrade: installed 
avahi-daemon package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1745782/+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 1691503] Re: Sound Problem

[dino99]

That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml

** 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/1691503

Title:
  Sound Problem

Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  Some times sound volume isn't working

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D0', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity:Unity7
  Date: Wed May 17 20:12:51 2017
  InstallationDate: Installed on 2017-05-17 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: alsa-driver
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/19/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: C2CN17WW(V1.03)
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo Z51-70
  dmi.board.vendor: LENOVO
  dmi.board.version: No DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Z51-70
  dmi.modalias: 
dmi:bvnLENOVO:bvrC2CN17WW(V1.03):bd03/19/2015:svnLENOVO:pn80K6:pvrLenovoZ51-70:rvnLENOVO:rnLenovoZ51-70:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoZ51-70:
  dmi.product.name: 80K6
  dmi.product.version: Lenovo Z51-70
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1691503/+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 1745828] Re: [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices

[George Hunter]

I tried downloading these, bur got an errorr 404 - File not Found.

Supposing I had succeeded, how do I install them?  Is it just

install 

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

Title:
  [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices

Status in bluez package in Ubuntu:
  Incomplete
Status in linux package in Ubuntu:
  Incomplete
Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  It is ON and VISIBLE in the control panel.  My iPhone can see two
  other devices but it can't see the computer, and the computer  can't
  see anything, even if left searching for tens of minutes.

  The previous answers listed below suggest the following diagnostics

  Bluetooth not working after update
  How can I make my bluetooth works on Ubuntu 16.04?
  Ubuntu 16.04 bluetooth not working (Dell XPS13)
  Bluetooth (Atheros AR3012) not working on Ubuntu 16.04
  Bluetooth not working on Ubuntu 16.04 LTS
  Bluetooth cannot find any devices
  Stuck on a bluetooth problem

  The service seems to be running

  /home >sudo service bluetooth status
  ● bluetooth.service - Bluetooth service
 Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset
 Active: active (running) since Thu 2018-01-25 09:16:43 GMT; 1h 46min ago
   Docs: man:bluetoothd(8)
   Main PID: 790 (bluetoothd)
 Status: "Running"
 CGroup: /system.slice/bluetooth.service
 └─790 /usr/lib/bluetooth/bluetoothd

  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset 
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset 
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.

  and not blocked

  /home >rfkill list
  0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  1: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no

  I have edited /etc/bluetooth/main.conf to include

  AutoEnable=true

  but I noted that the entire file was commented out.

  The kernel seems reasonably up to date

   >uname -a
  Linux george-CM6330 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 
22:00:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  I wonder if I need a device driver, but I have no idea how to find
  out.  The following diagnostics may help some of you knowledgeable
  people find out.

   >hcitool dev
  Devices:
hci024:0A:64:F5:EE:86

  and the output of dmsg is

  >dmesg | grep Blue
  [2.030855] usb 1-1.4: Product: Bluetooth Radio 
  [   13.806355] Bluetooth: Core ver 2.22
  [   13.806369] Bluetooth: HCI device and connection manager initialized
  [   13.806372] Bluetooth: HCI socket layer initialized
  [   13.806373] Bluetooth: L2CAP socket layer initialized
  [   13.806377] Bluetooth: SCO socket layer initialized
  [   13.827384] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000a 
lmp_ver=06 lmp_subver=8821
  [   13.827386] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_config.bin
  [   13.865327] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_fw.bin
  [   13.877382] Bluetooth: hci0: rom_version status=0 version=1
  [   13.877387] Bluetooth: cfg_sz 0, total size 17428
  [   16.550280] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   16.550281] Bluetooth: BNEP filters: protocol multicast
  [   16.550284] Bluetooth: BNEP socket layer initialized
  [   27.868345] Bluetooth: RFCOMM TTY layer initialized
  [   27.868350] Bluetooth: RFCOMM socket layer initialized
  [   27.868354] Bluetooth: RFCOMM ver 1.11

  and of lsusb is

  >lsusb
  Bus 002 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver
  Bus 002 Device 006: ID 04b8:0849 Seiko Epson Corp. Stylus SX205
  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 002: ID 04e8:6123 Samsung Electronics Co., Ltd 
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 004: ID 13d3:3414 IMC Networks 
  Bus 001 Device 003: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 

[Touch-packages] [Bug 1741986] Re: Please merge lvm2 from Debian unstable for lvmlockd and sanlock support

[Julian Andres Klode]

Fixed in 2.02.176-4.1ubuntu2


lvm2 (2.02.176-4.1ubuntu2) bionic; urgency=medium

  * Demote Recommends: thin-provisioning-tools to Suggests, as it's not
in main.

lvm2 (2.02.176-4.1ubuntu1) bionic; urgency=low

  * Merge with Debian unstable. Remaining changes:
- Add and install clvmd resource agent
- Lower libdevmapper1.02.1's Depends: dmsetup to a Recommends:. This
  breaks the circular dependency that causes upgrade failures. As dmsetup
  is "Priority: required", this has no other practical consequences.
- debian/control: add dmsetup-udeb to libdevmapper1.02.1-udeb recommends.
- debian/dmsetup-udeb.install: install udev rules in udebs
  (Debian #504341).
- Add debian/initramfs-tools/lvm2/scripts/init-bottom/lvm2: We cannot
  properly synthesize LVM LV change events with udevadm trigger, so
  if we use LVM, we need to let it finish; otherwise we get missing LV
  symlinks.
- Add debian/initramfs-tools/lvm2/scripts/init-premount/lvm2: failure
  hooks to help fix bad boots (Debian #468115)
- Do not start lvmetad when inside a container.
- Add enable-issue-discards.patch: Enable "issue_discards" option by
  default to trim SSDs when changing PVs. This option has no effect if the
  kernel or the drive does not support trimming, so it's safe to enable by
  default. (Debian #717313)
- debian/rules:
  + Copy .po file to .pot file for Rosetta (Ubuntu specific).
- debian/initramfs-tools/lvm2/hooks/lvm2: depend on udev since
  we ship udev rules.
- debian/clvm.maintscripts: Drop the /etc/default/clvm conffile on
  upgrade.  This delta can be dropped after 18.04 release.
- Do not start lvm2-monitor in containers (LP #1576341)
  * Dropped, merged upstream:
- Add a patch to fix crashes on 32bit platforms:
  + 0013-fix-lvmetad-32bit.patch
- d/p/fix-strips-limit.patch: Fix regression limiting number of
  stripes to 8 (LP #1675770)

lvm2 (2.02.176-4.1) unstable; urgency=high

  * Non-maintainer upload.
  * Revert uncoordinated addition of udev rules/sync support in udebs
which breaks LVM support in debian-installer instead of getting
debian-installer and installed systems to agree on device names.
(closes: #883361, reopens: #504341)

lvm2 (2.02.176-4) unstable; urgency=medium

  * Don't try to add dropped udev rules to initramfs.

lvm2 (2.02.176-3) unstable; urgency=medium

  * Actually add newly installed udev rules to initramfs.
(closes: #881314)
  * Make initramfs hooks bail out if udev rules can't be found.
  * Copy complete lvm config into initramfs.

lvm2 (2.02.176-2) unstable; urgency=medium

  * Drop changes for upgrades from before Wheezy.
  * Drop deprecated python bindings.
  * Enable udev rules in udeb. (closes: #504341)
  * Drop some udev rules modifications.
- Pull in newer dmsetup for udev rules changes.

lvm2 (2.02.176-1) unstable; urgency=medium

  * New upstream release.
  * Drop obsolte build-depends on dh-systemd.
  * Drop extra priorities from packages.
  * Update Standards-Version to 4.1.1, no changes.
  * Make lvm2-dbusd depend manually on required modules. (closes: #880543)
  * Make lvm2 recommend thin-provisioning-tools. (closes: #857142)
  * Run pvscan as systemd background job.
  * Don't try to restart special systemd services.
  * Really use debhelper compat 11.

lvm2 (2.02.175-1) unstable; urgency=medium

  * New upstream release.
  * Enable sanlock support in lvmlockd.
  * Use debhelper compat 11 for dh_installsystemd.

lvm2 (2.02.173-2) unstable; urgency=medium

  * Use dh.
  * Install all lvm2 config files.
  * Install and enable blk-availability service.
  * Add lvm2-dbus package.
  * Add lvm2-lockd package (dlm only). (closes: #879780)

lvm2 (2.02.173-1) unstable; urgency=medium

  * New upstream release.

 -- Julian Andres Klode   Tue, 30 Jan 2018 08:31:47
+0100

** Changed in: lvm2 (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  Please merge lvm2 from Debian unstable for lvmlockd and sanlock
  support

Status in lvm2 package in Ubuntu:
  Fix Released

Bug description:
  I am extremely interesting in utilizing the following stack to host
  disks for KVM virtual machines:

  * lvm2
  * lvmlockd
  * sanlock

  I believe in order to use lvmlockd, the lvm2 sources will need to be
  merged from Debian and the lvm2-lockd binary package will need to be
  built. Please could I request that this merge happen prior to the
  release of Beaver.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1741986/+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 1690545] Re: After some time sceen garbled and system freezes

[dino99]

That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml

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

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

Title:
  After some time sceen garbled and system freezes

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  After login screen become garbled and system freezes. using intel
  chipset and intel inbuilt graphic card. Shows the same error in all
  ubuntu versions.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sat May 13 19:40:07 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0042] 
(rev 12) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation Core Processor Integrated Graphics Controller 
[8086:0042]
  InstallationDate: Installed on 2017-05-05 (8 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=6bc2414d-e69a-4c57-911c-4d82b9882607 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/25/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 080015
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: To be filled by O.E.M.
  dmi.board.vendor: INTEL
  dmi.board.version: To be filled by O.E.M.
  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.:bvr080015:bd02/25/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnINTEL:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.14-0ubuntu1
  xserver.bootTime: Sat May 13 19:39:20 2017
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputLogitech USB Optical Mouse MOUSE, id 8
   inputLogitech USB Keyboard KEYBOARD, id 9
   inputLogitech USB Keyboard KEYBOARD, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   19345 
   vendor GSM
  xserver.version: 2:1.19.3-1ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1690545/+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 1690497] Re: package liblocale-gettext-perl 1.07-3build1 failed to install/upgrade: pre-dependency problem - not installing liblocale-gettext-perl

[dino99]

That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml

** Changed in: liblocale-gettext-perl (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  package liblocale-gettext-perl 1.07-3build1 failed to install/upgrade:
  pre-dependency problem - not installing liblocale-gettext-perl

Status in liblocale-gettext-perl package in Ubuntu:
  Invalid

Bug description:
  when i am using Ubuntu ...my laptop hangs ...

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: liblocale-gettext-perl 1.07-3build1
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic i686
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: i386
  Date: Sat May 13 08:47:11 2017
  ErrorMessage: pre-dependency problem - not installing liblocale-gettext-perl
  InstallationDate: Installed on 2016-12-13 (150 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: liblocale-gettext-perl
  Title: package liblocale-gettext-perl 1.07-3build1 failed to install/upgrade: 
pre-dependency problem - not installing liblocale-gettext-perl
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/liblocale-gettext-perl/+bug/1690497/+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 1689945] Re: I have reported issues running 17.04

[dino99]

That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml

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

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

Title:
  I have reported issues running 17.04

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  1. Right now from the "gear" in the upper right corner I cannot
 open System Settings and About this computer. However Help
 Suspend, Lock and Shut Down all seem to work. This problem 
 started after applying a recent update a few days ago.

  2. I have tried to report what happens at PC Shut Down. I see
 5 [FAILED] Stopped (with error)... messages.  I don't know
 if these shut down errors matter while the PC is running. 
 They read as follows:

 .../dev/disk/by-id/dm-name-cryptswap1.
 .../dev/dm-0.
 .../sys/devices/virtual/block/dm-0.
 .../dev/disk/by-uuid/fb03698d9-7980-4eb4-90e8-673c146fdd30.
 .../dev/disk/by-id/dm-uuid-CRYPT-PLAIN-cryptswap1.

   I tried to capture the above lines by cellphone photo.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed May 10 13:35:05 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS480M [Mobility Radeon Xpress 200] 
[1002:5955] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company RS480M [Mobility Radeon Xpress 200] 
[103c:3085]
  InstallationDate: Installed on 2016-08-17 (266 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release i386 (20160420.1)
  Lsusb:
   Protocol spec without prior Class and Subclass spec at line 13605
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 002: ID 15ca:00c3 Textech International Ltd. Mini Optical 
Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Hewlett-Packard Presario R4000 (PN495AV)
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic 
root=UUID=f8380f61-e531-4d20-86e8-0e76c6c99841 ro drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/24/2006
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.1C
  dmi.board.name: 3085
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 42.3B
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.1C:bd08/24/2006:svnHewlett-Packard:pnPresarioR4000(PN495AV):pvrF.1C:rvnHewlett-Packard:rn3085:rvr42.3B:cvnHewlett-Packard:ct10:cvrN/A:
  dmi.product.name: Presario R4000 (PN495AV)
  dmi.product.version: F.1C
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
  version.libdrm2: libdrm2 2.4.76-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.14-0ubuntu1
  xserver.bootTime: Wed May 10 13:18:19 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1
  xserver.video_driver: radeon

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

[Dieter Maurer]

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1649566/+attachment/5047619/+files/JournalErrors.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/1649566

Title:
  xserver-xorg-video-nouveau: X freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Yesterday, I upgraded from Ubuntu 12.04 via 14.04 to 16.04 (LTS
  version in each case). From 14.04 on, I was unable to graphically log
  in. A few seconds after the login (varying between 1 and 10 s), the
  screen changed to a pattern with dense white stripes on the violet/red
  background, and X froze (no reaction to mouse or keyboard). The latest
  messages in "/var/log/syslog" each time showed varying "nouveau E"
  problems, e.g. "unrecognized interupt", "PFIFO", or "PBUS" problems
  such as e.g.: "nouveau E[PBUS][:00:0d.0] MMIO write of
  0x01f70001 FAULT at 0x00b010" (values and addresses varying).

  An internet search revealed that the problem is well known. It affects
  many NVidia graphic cards with the "nouveau" driver. Usually, the
  freeze happens when e.g. "firefox" is started (which happens in my
  context automatically after a graphical login). Most reports recommend
  to switch from "nouveau" to the proprietary NVidia driver. However,
  there seem to be problems with that driver for recent Ubuntu versions.
  I my case, the NVidia driver could not be started (I did not
  investigate why). One report suggested the boot parameter
  "nouveau.config=NvMSI=0" which in my case made the graphical login
  successful again.

  Today, I wanted to report the bug with "ubuntu-bug". However, during the 
collection of the system information, the error happened again (despite the 
"nouveau.config" boot parameter).
  Syslog gives:
  ...
  Dec 13 11:12:01 localhost CRON[5230]: (root) CMD (   test -x 
/etc/cron.daily/popularity-contest && /etc/cron.daily/popularity-contest 
--crond)
  Dec 13 11:14:16 localhost kernel: [ 6889.138599] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:16 localhost kernel: [ 6889.140532] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:59 localhost dbus[795]: [system] Activating service 
name='com.ubuntu.SoftwareProperties' (using servicehelper)
  Dec 13 11:14:59 localhost dbus[795]: [system] Successfully activated service 
'com.ubuntu.SoftwareProperties'
  Dec 13 11:15:01 localhost CRON[5285]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:17:01 localhost CRON[5303]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)
  Dec 13 11:20:01 localhost CRON[5327]: (smmsp) CMD (test -x 
/etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x 
/usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp)
  Dec 13 11:22:20 localhost kernel: [ 7372.621357] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x FAULT at 0x00b020
  Dec 13 11:25:01 localhost CRON[5580]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:35:01 localhost CRON[5651]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:38:02 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.
  Dec 13 11:39:01 localhost CRON[5723]: (root) CMD (  [ -x 
/usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d 
/var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 
$(/usr/lib/php5/maxlifetime))
  Dec 13 11:39:01 localhost CRON[5722]: (root) CMD (  [ -x 
/usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)
  Dec 13 11:39:46 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.

  At this point, I had to reset the computer.

  
  Detailed system information:
  lsdm: lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  xserver-xorg-video-nouveau 1:1.0.12-1build2

  root@lsdm:~# lspci
  00:00.0 RAM memory: NVIDIA Corporation MCP61 Host Bridge (rev a1)
  00:01.0 ISA bridge: NVIDIA Corporation MCP61 LPC Bridge (rev a2)
  00:01.1 SMBus: NVIDIA Corporation MCP61 SMBus (rev a2)
  00:01.2 RAM memory: NVIDIA Corporation MCP61 Memory Controller (rev a2)
  00:02.0 USB controller: NVIDIA Corporation MCP61 USB 1.1 Controller (rev a3)
  00:02.1 USB controller: NVIDIA Corporation MCP61 USB 2.0 Controller (rev a3)
  00:04.0 PCI bridge: NVIDIA Corporation MCP61 PCI bridge (rev a1)
  00:05.0 Audio device: NVIDIA Corporation MCP61 High Definition Audio (rev a2)
  00:06.0 IDE interface: NVIDIA Corporation MCP61 IDE (rev a2)
  00:07.0 Bridge: NVIDIA Corporation MCP61 Ethernet (rev a2)
  00:08.0 IDE interface: NVIDIA Corporation MCP61 SATA Controller (rev a2)
  00:08.1 IDE interface: NVIDIA Corporation MCP61 SATA Controller (rev a2)
  00:09.0 PCI 

[Touch-packages] [Bug 1745963] Re: no displaY

[Marc Deslauriers]

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

** Information type changed from Private Security to Public

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

Title:
  no displaY

Status in xorg package in Ubuntu:
  New

Bug description:
  DISPLAY fades out after standby mode

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic i686
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Jan 29 08:19:44 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Silicon Integrated Systems [SiS] 771/671 PCIE VGA Display Adapter 
[1039:6351] (rev 10) (prog-if 00 [VGA controller])
 Subsystem: Fujitsu Technology Solutions 771/671 PCIE VGA Display Adapter 
[1734:1125]
  InstallationDate: Installed on 2018-01-26 (2 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 002: ID 15d9:0a4d Trust International B.V. Optical Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: FUJITSU SIEMENS ESPRIMO Mobile V5535
  ProcEnviron:
   LANGUAGE=pt:pt_BR:en
   PATH=(custom, no user)
   LANG=pt_PT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=086e92bc-3d33-4968-a4b8-3a36e8a3e993 ro quiet plymouth:debug=1 splash
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/30/07
  dmi.bios.vendor: Phoenix
  dmi.bios.version: V1.03
  dmi.board.name: Z17M2.0
  dmi.board.vendor: FUJITSU SIEMENS
  dmi.board.version: V1.02
  dmi.chassis.asset.tag: User Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: FUJITSU SIEMENS
  dmi.chassis.version: V1.02
  dmi.modalias: 
dmi:bvnPhoenix:bvrV1.03:bd11/30/07:svnFUJITSUSIEMENS:pnESPRIMOMobileV5535:pvrV1.02:rvnFUJITSUSIEMENS:rnZ17M2.0:rvrV1.02:cvnFUJITSUSIEMENS:ct1:cvrV1.02:
  dmi.product.name: ESPRIMO Mobile V5535
  dmi.product.version: V1.02
  dmi.sys.vendor: FUJITSU SIEMENS
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sun Jan 28 23:35:43 2018
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1745963/+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 1691225] Re: hud-service trying to output error messages using ncurses colours to syslog

[dino99]

That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml

** Changed in: hud (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  hud-service trying to output error messages using ncurses colours to
  syslog

Status in hud package in Ubuntu:
  Invalid

Bug description:
  Wherever hud-service is failing, it's trying to print using ncurses
  colour tags (m#NNN[NN) where syslog is text-only.

  example error message:

  May 16 14:11:02 eva hud-service[1967]: #033[31mvoid
  DBusMenuImporter::slotGetLayoutFinished(QDBusPendingCallWatcher*)#033[0m:
  "No such interface 'com.canonical.dbusmenu' on object at path
  /org/ayatana/bamf/window/75498803"

  what this error message should probably be:
  May 16 14:11:02 eva hud-service[1967]: void 
DBusMenuImporter::slotGetLayoutFinished(QDBusPendingCallWatcher*): "No such 
interface 'com.canonical.dbusmenu' on object at path 
/org/ayatana/bamf/window/75498803"

  Ubuntu 17.04 zesty
  hud: 14.10+17.04.20170106.1-0ubuntu1

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: hud 14.10+17.04.20170106.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Tue May 16 14:10:55 2017
  InstallationDate: Installed on 2017-04-18 (27 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: hud
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hud/+bug/1691225/+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 1691262] Re: touchpad will cant be disabled

[dino99]

That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml

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

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

Title:
  touchpad will cant be disabled

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  i tried adjusting the touchpad via gnome settings and gpointing-
  device-settings but i cant disable it and it wont disable it self via
  shortcut or if i have my hand on the device...

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.39  Tue Jan 31 20:47:00 
PST 2017
   GCC version:  gcc version 6.3.0 20170406 (Ubuntu 6.3.0-12ubuntu2)
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Tue May 16 21:40:55 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.10.0-21-generic, x86_64: installed
   nvidia-375, 375.39, 4.10.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] 4th Gen Core Processor 
Integrated Graphics Controller [1462:1107]
 Subsystem: Micro-Star International Co., Ltd. [MSI] GM107M [GeForce GTX 
860M] [1462:1107]
  InstallationDate: Installed on 2016-11-03 (194 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Micro-Star International Co., Ltd. GE60 2PE
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-21-generic.efi.signed 
root=UUID=cb38e854-521c-4704-84a1-24508a542dd3 ro plymouth:debug drm.debug=0xe
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/01/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16GFIMS.51C
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-16GF
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:0.B
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16GFIMS.51C:bd07/01/2014:svnMicro-StarInternationalCo.,Ltd.:pnGE602PE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16GF:rvrREV0.B:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.name: GE60 2PE
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.14-0ubuntu1
  xserver.bootTime: Tue May 16 20:21:37 2017
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1

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

[dino99]

That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml

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

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

Title:
  bug

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Not sure run the program and sent reports

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.39  Tue Jan 31 20:47:00 
PST 2017
   GCC version:  gcc version 6.3.0 20170406 (Ubuntu 6.3.0-12ubuntu2)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Wed May 17 13:03:55 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.10.0-19-generic, x86_64: installed
   bbswitch, 0.8, 4.10.0-21-generic, x86_64: installed
   nvidia-375, 375.39, 4.10.0-19-generic, x86_64: installed
   nvidia-375, 375.39, 4.10.0-21-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller 
[1028:05a9]
   NVIDIA Corporation GK107M [GeForce GT 750M] [10de:0fe4] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell GK107M [GeForce GT 750M] [1028:05a9]
  InstallationDate: Installed on 2017-05-16 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Alienware Alienware 14
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-21-generic 
root=UUID=6a513eb6-2a19-471b-8f94-d3ebc49c0253 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/23/2014
  dmi.bios.vendor: Alienware
  dmi.bios.version: A09
  dmi.board.name: 07MJ2Y
  dmi.board.vendor: Alienware
  dmi.board.version: A01
  dmi.chassis.type: 8
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: A09
  dmi.modalias: 
dmi:bvnAlienware:bvrA09:bd04/23/2014:svnAlienware:pnAlienware14:pvrA09:rvnAlienware:rn07MJ2Y:rvrA01:cvnAlienware:ct8:cvrA09:
  dmi.product.name: Alienware 14
  dmi.product.version: A09
  dmi.sys.vendor: Alienware
  version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.14-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1691513/+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 1746413] Re: [Inspiron 14-3467, Realtek ALC3246, Speaker, Internal] No sound at all

[Marc Deslauriers]

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

** Information type changed from Private Security to Public

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

Title:
  [Inspiron 14-3467, Realtek ALC3246, Speaker, Internal] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  inbuilt speaker sound of my laptop is not working

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  himanshu   2244 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jan 31 11:14:02 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  InstallationDate: Installed on 2018-01-30 (0 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  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/controlC0:  himanshu   2244 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [Inspiron 14-3467, Realtek ALC3246, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/23/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.06.00
  dmi.board.name: 0WPN9K
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.06.00:bd03/23/2017:svnDellInc.:pnInspiron14-3467:pvr:rvnDellInc.:rn0WPN9K:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 14-3467
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1746413/+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 1743423] Re: frozen login window' unable to login; must reboot' cursor moves no mouse clicks

[Marc Deslauriers]

** Changed in: lightdm (Ubuntu)
   Status: New => 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/1743423

Title:
  frozen login window' unable to login; must reboot' cursor moves no
  mouse clicks

Status in lightdm package in Ubuntu:
  Triaged

Bug description:
  Denial o9f Service caused by holding a key that repeats for a long
  time.  eg.  cat takes nap on keyboard, cloting piled on keyboard

  Before submitting bug report I checked online and saw many other
  reports goin back about 15 months.  I saw no mention of  updates or
  how to reproduce.  In my case the cursor continues to move around, but
  unable to use cursor to reboot.  I can only use power off as none of
  they keys are working.

  Good thing the power button results are acceptable. and most
  applications fully recover.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.3-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  Uname: Linux 4.4.0-109-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Sun Jan 14 19:20:22 2018
  InstallationDate: Installed on 2016-02-22 (692 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1743423/+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 1691486] Re: Mouse cursor jumps to top left corner on click+drag

[dino99]

That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml

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

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

Title:
  Mouse cursor jumps to top left corner on click+drag

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Since the upgrade to 17.10, when I click and drag something (e.g.
  moving a file within a folder, or moving an email message within
  Thunderbird), the mouse pointer (and the dragged item) jumps to the
  top left corner of the screen. From there, movement is normal and no
  more jumping is observed (until the next click-drag).

  The issue does *not* manifest when using the paintbrush tool in GIMP
  or just selecting text (e.g. in Chromium), but if I then click and
  drag the selected text, the mouse cursor does jump.

  Here's an xinput --test log from an instance of clicking a file inside
  a folder and dragging it (moved the mouse slowly / just a few
  millimeters):

  motion a[0]=1326 a[1]=451 
  motion a[0]=1326 a[1]=451 
  motion a[0]=1327 a[1]=450 
  motion a[0]=1327 a[1]=449 
  motion a[1]=449 
  motion a[1]=449 
  motion a[1]=448 
  motion a[0]=1327 a[1]=448 
  motion a[1]=448 
  motion a[1]=447 
  motion a[0]=1327 a[1]=447 
  motion a[1]=447 
  motion a[0]=1328 a[1]=447 
  motion a[1]=446 
  motion a[0]=1328 
  motion a[1]=446 
  button press   1 
  motion a[0]=1328 
  motion a[0]=1328 
  motion a[0]=1328 
  motion a[0]=1328 a[1]=446 
  motion a[0]=1327 
  motion a[0]=1327 
  motion a[0]=1327 
  motion a[1]=446 
  motion a[0]=1327 
  motion a[0]=1327 
  motion a[0]=1326 
  motion a[0]=1326 
  motion a[1]=446 
  motion a[0]=1326 
  motion a[0]=1326 a[1]=445 
  motion a[0]=1326 
  motion a[0]=1325 
  motion a[0]=1325 
  motion a[1]=445 
  motion a[0]=1325 
  motion a[0]=1325 
  motion a[0]=1325 
  motion a[0]=1324 
  motion a[0]=1324 
  motion a[1]=445 
  motion a[0]=1324 
  motion a[0]=1324 
  motion a[0]=1324 
  motion a[1]=445 
  motion a[0]=1323 
  motion a[0]=1323 
  motion a[0]=1323 
  motion a[0]=1323 
  motion a[1]=445 
  motion a[0]=1322 
  motion a[0]=1322 
  motion a[0]=1322 
  motion a[0]=1322 
  motion a[0]=1322 
  motion a[0]=1321 
  motion a[1]=444 
  motion a[0]=1321 
  motion a[0]=1321 
  motion a[0]=1321 
  motion a[0]=1321 
  motion a[0]=1320 
  motion a[0]=1320 
  motion a[0]=1320 
  motion a[1]=444 
  motion a[0]=1320 
  motion a[0]=1320 
  motion a[0]=1319 
  motion a[1]=444 
  motion a[0]=1319 
  motion a[0]=1319 
  motion a[1]=444 
  motion a[0]=1319 
  motion a[0]=1319 
  motion a[1]=444 
  motion a[0]=1318 
  motion a[0]=1318 
  motion a[0]=1318 
  motion a[0]=1318 
  motion a[0]=1318 
  motion a[1]=443 
  motion a[0]=1317 
  motion a[0]=1317 
  motion a[0]=1317 a[1]=443 
  motion a[0]=1317 
  motion a[0]=1317 
  motion a[0]=1316 
  motion a[1]=443 
  motion a[0]=1316 
  motion a[0]=1316 
  motion a[0]=1316 
  motion a[1]=443 
  motion a[0]=1316 
  motion a[0]=1315 
  motion a[1]=443 
  motion a[0]=1315 
  motion a[0]=1315 
  motion a[0]=1315 a[1]=442 
  motion a[0]=1315 
  motion a[0]=1314 
  motion a[1]=442 
  motion a[0]=1314 
  motion a[0]=1314 
  motion a[0]=1314 a[1]=442 
  motion a[0]=261 
  motion a[0]=261 
  motion a[1]=87 
  motion a[0]=261 
  motion a[0]=261 
  motion a[0]=261 
  motion a[0]=260 
  motion a[0]=260 a[1]=87 
  motion a[1]=16 
  motion a[0]=51 
  motion a[0]=50 
  motion a[0]=50 
  motion a[0]=50 a[1]=16 
  motion a[0]=50 
  motion a[1]=16 
  motion a[0]=50 
  motion a[0]=49 
  motion a[0]=49 
  motion a[0]=49 
  motion a[1]=15 
  motion a[0]=49 
  motion a[0]=48 
  motion a[0]=48 
  motion a[0]=48 a[1]=15 
  motion a[1]=15 
  motion a[0]=48 
  motion a[0]=48 
  motion a[0]=47 
  motion a[1]=15 
  motion a[0]=47 
  motion a[0]=47 
  motion a[0]=47 
  motion a[1]=14 
  motion a[0]=47 
  motion a[0]=46 
  motion a[0]=46 
  motion a[1]=14 
  motion a[0]=46 
  button release 1

  
  Here are my xinput settings for the device (which I *do* customize with a 
script run at login to avert hypersensitivity):
  $ xinput --list-props "Razer Razer DeathAdder"
  Device 'Razer Razer DeathAdder':
Device Enabled (136):   1
Coordinate Transformation Matrix (138): 0.20, 0.00, 0.00, 
0.00, 0.20, 0.00, 0.00, 0.00, 1.00
libinput Accel Speed (275): 0.50
libinput Accel Speed Default (276): 0.00
libinput Accel Profiles Available (277):1, 1
libinput Accel Profile Enabled (278):   1, 0
libinput Accel Profile Enabled Default (279):   1, 0
libinput Natural Scrolling Enabled (271):   0
libinput Natural Scrolling Enabled Default (272):   0
libinput Send Events Modes Available (256): 1, 0
libinput Send Events Mode 

[Touch-packages] [Bug 1691125] Re: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 1

[dino99]

That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml

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

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

Title:
  package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: sub-
  processo script post-installation instalado retornou estado de saída
  de erro 1

Status in gconf package in Ubuntu:
  Invalid

Bug description:
  ...

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: gconf2-common 3.2.6-3ubuntu7
  ProcVersionSignature: Ubuntu 4.10.0-21.23-generic 4.10.11
  Uname: Linux 4.10.0-21-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.4-0ubuntu4.1
  Architecture: amd64
  Date: Mon May 15 08:29:29 2017
  ErrorMessage: sub-processo script post-installation instalado retornou estado 
de saída de erro 1
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gconf
  Title: package gconf2-common 3.2.6-3ubuntu7 failed to install/upgrade: 
sub-processo script post-installation instalado retornou estado de saída de 
erro 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1691125/+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 1649566] Lspci.txt

[Dieter Maurer]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1649566/+attachment/5047620/+files/Lspci.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/1649566

Title:
  xserver-xorg-video-nouveau: X freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Yesterday, I upgraded from Ubuntu 12.04 via 14.04 to 16.04 (LTS
  version in each case). From 14.04 on, I was unable to graphically log
  in. A few seconds after the login (varying between 1 and 10 s), the
  screen changed to a pattern with dense white stripes on the violet/red
  background, and X froze (no reaction to mouse or keyboard). The latest
  messages in "/var/log/syslog" each time showed varying "nouveau E"
  problems, e.g. "unrecognized interupt", "PFIFO", or "PBUS" problems
  such as e.g.: "nouveau E[PBUS][:00:0d.0] MMIO write of
  0x01f70001 FAULT at 0x00b010" (values and addresses varying).

  An internet search revealed that the problem is well known. It affects
  many NVidia graphic cards with the "nouveau" driver. Usually, the
  freeze happens when e.g. "firefox" is started (which happens in my
  context automatically after a graphical login). Most reports recommend
  to switch from "nouveau" to the proprietary NVidia driver. However,
  there seem to be problems with that driver for recent Ubuntu versions.
  I my case, the NVidia driver could not be started (I did not
  investigate why). One report suggested the boot parameter
  "nouveau.config=NvMSI=0" which in my case made the graphical login
  successful again.

  Today, I wanted to report the bug with "ubuntu-bug". However, during the 
collection of the system information, the error happened again (despite the 
"nouveau.config" boot parameter).
  Syslog gives:
  ...
  Dec 13 11:12:01 localhost CRON[5230]: (root) CMD (   test -x 
/etc/cron.daily/popularity-contest && /etc/cron.daily/popularity-contest 
--crond)
  Dec 13 11:14:16 localhost kernel: [ 6889.138599] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:16 localhost kernel: [ 6889.140532] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:59 localhost dbus[795]: [system] Activating service 
name='com.ubuntu.SoftwareProperties' (using servicehelper)
  Dec 13 11:14:59 localhost dbus[795]: [system] Successfully activated service 
'com.ubuntu.SoftwareProperties'
  Dec 13 11:15:01 localhost CRON[5285]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:17:01 localhost CRON[5303]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)
  Dec 13 11:20:01 localhost CRON[5327]: (smmsp) CMD (test -x 
/etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x 
/usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp)
  Dec 13 11:22:20 localhost kernel: [ 7372.621357] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x FAULT at 0x00b020
  Dec 13 11:25:01 localhost CRON[5580]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:35:01 localhost CRON[5651]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:38:02 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.
  Dec 13 11:39:01 localhost CRON[5723]: (root) CMD (  [ -x 
/usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d 
/var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 
$(/usr/lib/php5/maxlifetime))
  Dec 13 11:39:01 localhost CRON[5722]: (root) CMD (  [ -x 
/usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)
  Dec 13 11:39:46 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.

  At this point, I had to reset the computer.

  
  Detailed system information:
  lsdm: lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  xserver-xorg-video-nouveau 1:1.0.12-1build2

  root@lsdm:~# lspci
  00:00.0 RAM memory: NVIDIA Corporation MCP61 Host Bridge (rev a1)
  00:01.0 ISA bridge: NVIDIA Corporation MCP61 LPC Bridge (rev a2)
  00:01.1 SMBus: NVIDIA Corporation MCP61 SMBus (rev a2)
  00:01.2 RAM memory: NVIDIA Corporation MCP61 Memory Controller (rev a2)
  00:02.0 USB controller: NVIDIA Corporation MCP61 USB 1.1 Controller (rev a3)
  00:02.1 USB controller: NVIDIA Corporation MCP61 USB 2.0 Controller (rev a3)
  00:04.0 PCI bridge: NVIDIA Corporation MCP61 PCI bridge (rev a1)
  00:05.0 Audio device: NVIDIA Corporation MCP61 High Definition Audio (rev a2)
  00:06.0 IDE interface: NVIDIA Corporation MCP61 IDE (rev a2)
  00:07.0 Bridge: NVIDIA Corporation MCP61 Ethernet (rev a2)
  00:08.0 IDE interface: NVIDIA Corporation MCP61 SATA Controller (rev a2)
  00:08.1 IDE interface: NVIDIA Corporation MCP61 SATA Controller (rev a2)
  00:09.0 PCI bridge: NVIDIA 

[Touch-packages] [Bug 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits

[Eric Desrochers]

Hi Seyeong,

I did some verification this morning based on your comment #42.

After some digging... it turns out that the profiles in
"apparmor_src_pkg/profiles/" are not used. if you are attempting to
patch a profile, you must adjust it to patch
apparmor_src_pkg/profiles-14.04/ instead.

In this particular case "apparmor-src-
pkg/profiles-14.04/apparmor.d/tunables/kernelvars" instead of "apparmor-
pkg-src/profiles/apparmor.d/tunables/kernelvars".

You did the right thing by putting the bug to verification-failed-
trusty.

As of the next step ... I would recommend you re-do the patch
considering the above, and pay attention this time that the change is
taken into account in your pkg PPA build, then test your reproducer
against the package, make sure it works as expected.

Once everything is confirm on your side, I'll double-check one more time
before the proceeding the next upload.

- Eric

-- 
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:
  Fix Released
Status in apparmor source package in Trusty:
  Fix Committed
Status in apparmor source package in Xenial:
  Fix Committed
Status in apparmor source package in Artful:
  Fix Committed
Status in apparmor source package in Bionic:
  Fix Released
Status in apparmor package in Debian:
  Fix Released

Bug description:
  [Impact]

  If PID is larger than 6 digits apparmor denies process which only
  affect 64-bit systems[1] where the PID_MAX_LIMIT can be generated up
  to 7 digits at the maximum.

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

  [1] - man 5 proc

  --
  /proc/sys/kernel/pid_max (since Linux 2.5.34)
  This file specifies the value at which PIDs wrap around (i.e., the value in 
this file is one greater than the maximum PID).  PIDs greater than this value 
are not allocated;  thus,  the value  in this file also acts as a system-wide 
limit on the total number of processes and threads.  The default value for this 
file, 32768, results in the same range of PIDs as on ear‐lier kernels.  On 
32-bit platforms, 32768 is the maximum value for pid_max.  On 64-bit systems, 
pid_max can be set to any value up to 2^22 (PID_MAX_LIMIT, approximately 4 
million).
  --

  [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

  OR

  instead of Seyeong's touch approach, things can be manually change to
  7 digits range via sysctl as long as the values are below
  approximately 4 millions :

  Example:
  $ sysctl -w kernel.pid_max=300
  $ sysctl -w kernel.ns_last_pid=100

  [Regression]
  * This is a minor/trivial fix which changes the pid regex only, allowing 7 
digits PID instead of only 6 digits PID, we don't think there is any potential 
regression.

  * If a regression arise, which we highly doubt, one can quickly revert
  the change manually and restart the service by modifying
  "/etc/apparmor.d/tunables/kernelvars" file to its original state
  (before this SRU).

  [Others]

  * Upstream commit:
   
https://gitlab.com/apparmor/apparmor/commit/630cb2a981cdc731847e8fdaafc45bcd337fe747
  http://bazaar.launchpad.net/~apparmor-dev/apparmor/master/revision/3722

  * Debian bug:
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886732

  * 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 

[Touch-packages] [Bug 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable

[Steve Langasek]

** Changed in: aptdaemon (Ubuntu)
   Status: Fix Released => Invalid

** Changed in: debconf (Ubuntu)
   Status: Fix Released => Triaged

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

Title:
  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

Status in Aptdaemon:
  Fix Released
Status in Debconf:
  New
Status in aptdaemon package in Ubuntu:
  Invalid
Status in debconf package in Ubuntu:
  Triaged

Bug description:
  Upgrading packages that use debconf sometimes fail with the following
  error:

  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

To manage notifications about this bug go to:
https://bugs.launchpad.net/aptdaemon/+bug/349469/+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 1649566] XorgLogOld.txt

[Dieter Maurer]

apport information

** Attachment added: "XorgLogOld.txt"
   
https://bugs.launchpad.net/bugs/1649566/+attachment/5047627/+files/XorgLogOld.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/1649566

Title:
  xserver-xorg-video-nouveau: X freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Yesterday, I upgraded from Ubuntu 12.04 via 14.04 to 16.04 (LTS
  version in each case). From 14.04 on, I was unable to graphically log
  in. A few seconds after the login (varying between 1 and 10 s), the
  screen changed to a pattern with dense white stripes on the violet/red
  background, and X froze (no reaction to mouse or keyboard). The latest
  messages in "/var/log/syslog" each time showed varying "nouveau E"
  problems, e.g. "unrecognized interupt", "PFIFO", or "PBUS" problems
  such as e.g.: "nouveau E[PBUS][:00:0d.0] MMIO write of
  0x01f70001 FAULT at 0x00b010" (values and addresses varying).

  An internet search revealed that the problem is well known. It affects
  many NVidia graphic cards with the "nouveau" driver. Usually, the
  freeze happens when e.g. "firefox" is started (which happens in my
  context automatically after a graphical login). Most reports recommend
  to switch from "nouveau" to the proprietary NVidia driver. However,
  there seem to be problems with that driver for recent Ubuntu versions.
  I my case, the NVidia driver could not be started (I did not
  investigate why). One report suggested the boot parameter
  "nouveau.config=NvMSI=0" which in my case made the graphical login
  successful again.

  Today, I wanted to report the bug with "ubuntu-bug". However, during the 
collection of the system information, the error happened again (despite the 
"nouveau.config" boot parameter).
  Syslog gives:
  ...
  Dec 13 11:12:01 localhost CRON[5230]: (root) CMD (   test -x 
/etc/cron.daily/popularity-contest && /etc/cron.daily/popularity-contest 
--crond)
  Dec 13 11:14:16 localhost kernel: [ 6889.138599] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:16 localhost kernel: [ 6889.140532] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:59 localhost dbus[795]: [system] Activating service 
name='com.ubuntu.SoftwareProperties' (using servicehelper)
  Dec 13 11:14:59 localhost dbus[795]: [system] Successfully activated service 
'com.ubuntu.SoftwareProperties'
  Dec 13 11:15:01 localhost CRON[5285]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:17:01 localhost CRON[5303]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)
  Dec 13 11:20:01 localhost CRON[5327]: (smmsp) CMD (test -x 
/etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x 
/usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp)
  Dec 13 11:22:20 localhost kernel: [ 7372.621357] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x FAULT at 0x00b020
  Dec 13 11:25:01 localhost CRON[5580]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:35:01 localhost CRON[5651]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:38:02 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.
  Dec 13 11:39:01 localhost CRON[5723]: (root) CMD (  [ -x 
/usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d 
/var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 
$(/usr/lib/php5/maxlifetime))
  Dec 13 11:39:01 localhost CRON[5722]: (root) CMD (  [ -x 
/usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)
  Dec 13 11:39:46 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.

  At this point, I had to reset the computer.

  
  Detailed system information:
  lsdm: lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  xserver-xorg-video-nouveau 1:1.0.12-1build2

  root@lsdm:~# lspci
  00:00.0 RAM memory: NVIDIA Corporation MCP61 Host Bridge (rev a1)
  00:01.0 ISA bridge: NVIDIA Corporation MCP61 LPC Bridge (rev a2)
  00:01.1 SMBus: NVIDIA Corporation MCP61 SMBus (rev a2)
  00:01.2 RAM memory: NVIDIA Corporation MCP61 Memory Controller (rev a2)
  00:02.0 USB controller: NVIDIA Corporation MCP61 USB 1.1 Controller (rev a3)
  00:02.1 USB controller: NVIDIA Corporation MCP61 USB 2.0 Controller (rev a3)
  00:04.0 PCI bridge: NVIDIA Corporation MCP61 PCI bridge (rev a1)
  00:05.0 Audio device: NVIDIA Corporation MCP61 High Definition Audio (rev a2)
  00:06.0 IDE interface: NVIDIA Corporation MCP61 IDE (rev a2)
  00:07.0 Bridge: NVIDIA Corporation MCP61 Ethernet (rev a2)
  00:08.0 IDE interface: NVIDIA Corporation MCP61 SATA Controller (rev a2)
  00:08.1 IDE interface: NVIDIA Corporation MCP61 SATA Controller (rev a2)
  00:09.0 PCI bridge: 

[Touch-packages] [Bug 1649566] Dependencies.txt

[Dieter Maurer]

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1649566/+attachment/5047617/+files/Dependencies.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/1649566

Title:
  xserver-xorg-video-nouveau: X freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Yesterday, I upgraded from Ubuntu 12.04 via 14.04 to 16.04 (LTS
  version in each case). From 14.04 on, I was unable to graphically log
  in. A few seconds after the login (varying between 1 and 10 s), the
  screen changed to a pattern with dense white stripes on the violet/red
  background, and X froze (no reaction to mouse or keyboard). The latest
  messages in "/var/log/syslog" each time showed varying "nouveau E"
  problems, e.g. "unrecognized interupt", "PFIFO", or "PBUS" problems
  such as e.g.: "nouveau E[PBUS][:00:0d.0] MMIO write of
  0x01f70001 FAULT at 0x00b010" (values and addresses varying).

  An internet search revealed that the problem is well known. It affects
  many NVidia graphic cards with the "nouveau" driver. Usually, the
  freeze happens when e.g. "firefox" is started (which happens in my
  context automatically after a graphical login). Most reports recommend
  to switch from "nouveau" to the proprietary NVidia driver. However,
  there seem to be problems with that driver for recent Ubuntu versions.
  I my case, the NVidia driver could not be started (I did not
  investigate why). One report suggested the boot parameter
  "nouveau.config=NvMSI=0" which in my case made the graphical login
  successful again.

  Today, I wanted to report the bug with "ubuntu-bug". However, during the 
collection of the system information, the error happened again (despite the 
"nouveau.config" boot parameter).
  Syslog gives:
  ...
  Dec 13 11:12:01 localhost CRON[5230]: (root) CMD (   test -x 
/etc/cron.daily/popularity-contest && /etc/cron.daily/popularity-contest 
--crond)
  Dec 13 11:14:16 localhost kernel: [ 6889.138599] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:16 localhost kernel: [ 6889.140532] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:59 localhost dbus[795]: [system] Activating service 
name='com.ubuntu.SoftwareProperties' (using servicehelper)
  Dec 13 11:14:59 localhost dbus[795]: [system] Successfully activated service 
'com.ubuntu.SoftwareProperties'
  Dec 13 11:15:01 localhost CRON[5285]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:17:01 localhost CRON[5303]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)
  Dec 13 11:20:01 localhost CRON[5327]: (smmsp) CMD (test -x 
/etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x 
/usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp)
  Dec 13 11:22:20 localhost kernel: [ 7372.621357] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x FAULT at 0x00b020
  Dec 13 11:25:01 localhost CRON[5580]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:35:01 localhost CRON[5651]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:38:02 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.
  Dec 13 11:39:01 localhost CRON[5723]: (root) CMD (  [ -x 
/usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d 
/var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 
$(/usr/lib/php5/maxlifetime))
  Dec 13 11:39:01 localhost CRON[5722]: (root) CMD (  [ -x 
/usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)
  Dec 13 11:39:46 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.

  At this point, I had to reset the computer.

  
  Detailed system information:
  lsdm: lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  xserver-xorg-video-nouveau 1:1.0.12-1build2

  root@lsdm:~# lspci
  00:00.0 RAM memory: NVIDIA Corporation MCP61 Host Bridge (rev a1)
  00:01.0 ISA bridge: NVIDIA Corporation MCP61 LPC Bridge (rev a2)
  00:01.1 SMBus: NVIDIA Corporation MCP61 SMBus (rev a2)
  00:01.2 RAM memory: NVIDIA Corporation MCP61 Memory Controller (rev a2)
  00:02.0 USB controller: NVIDIA Corporation MCP61 USB 1.1 Controller (rev a3)
  00:02.1 USB controller: NVIDIA Corporation MCP61 USB 2.0 Controller (rev a3)
  00:04.0 PCI bridge: NVIDIA Corporation MCP61 PCI bridge (rev a1)
  00:05.0 Audio device: NVIDIA Corporation MCP61 High Definition Audio (rev a2)
  00:06.0 IDE interface: NVIDIA Corporation MCP61 IDE (rev a2)
  00:07.0 Bridge: NVIDIA Corporation MCP61 Ethernet (rev a2)
  00:08.0 IDE interface: NVIDIA Corporation MCP61 SATA Controller (rev a2)
  00:08.1 IDE interface: NVIDIA Corporation MCP61 SATA Controller (rev a2)
  00:09.0 PCI 

[Touch-packages] [Bug 1649566] CurrentDmesg.txt

[Dieter Maurer]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1649566/+attachment/5047616/+files/CurrentDmesg.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/1649566

Title:
  xserver-xorg-video-nouveau: X freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Yesterday, I upgraded from Ubuntu 12.04 via 14.04 to 16.04 (LTS
  version in each case). From 14.04 on, I was unable to graphically log
  in. A few seconds after the login (varying between 1 and 10 s), the
  screen changed to a pattern with dense white stripes on the violet/red
  background, and X froze (no reaction to mouse or keyboard). The latest
  messages in "/var/log/syslog" each time showed varying "nouveau E"
  problems, e.g. "unrecognized interupt", "PFIFO", or "PBUS" problems
  such as e.g.: "nouveau E[PBUS][:00:0d.0] MMIO write of
  0x01f70001 FAULT at 0x00b010" (values and addresses varying).

  An internet search revealed that the problem is well known. It affects
  many NVidia graphic cards with the "nouveau" driver. Usually, the
  freeze happens when e.g. "firefox" is started (which happens in my
  context automatically after a graphical login). Most reports recommend
  to switch from "nouveau" to the proprietary NVidia driver. However,
  there seem to be problems with that driver for recent Ubuntu versions.
  I my case, the NVidia driver could not be started (I did not
  investigate why). One report suggested the boot parameter
  "nouveau.config=NvMSI=0" which in my case made the graphical login
  successful again.

  Today, I wanted to report the bug with "ubuntu-bug". However, during the 
collection of the system information, the error happened again (despite the 
"nouveau.config" boot parameter).
  Syslog gives:
  ...
  Dec 13 11:12:01 localhost CRON[5230]: (root) CMD (   test -x 
/etc/cron.daily/popularity-contest && /etc/cron.daily/popularity-contest 
--crond)
  Dec 13 11:14:16 localhost kernel: [ 6889.138599] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:16 localhost kernel: [ 6889.140532] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:59 localhost dbus[795]: [system] Activating service 
name='com.ubuntu.SoftwareProperties' (using servicehelper)
  Dec 13 11:14:59 localhost dbus[795]: [system] Successfully activated service 
'com.ubuntu.SoftwareProperties'
  Dec 13 11:15:01 localhost CRON[5285]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:17:01 localhost CRON[5303]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)
  Dec 13 11:20:01 localhost CRON[5327]: (smmsp) CMD (test -x 
/etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x 
/usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp)
  Dec 13 11:22:20 localhost kernel: [ 7372.621357] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x FAULT at 0x00b020
  Dec 13 11:25:01 localhost CRON[5580]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:35:01 localhost CRON[5651]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:38:02 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.
  Dec 13 11:39:01 localhost CRON[5723]: (root) CMD (  [ -x 
/usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d 
/var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 
$(/usr/lib/php5/maxlifetime))
  Dec 13 11:39:01 localhost CRON[5722]: (root) CMD (  [ -x 
/usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)
  Dec 13 11:39:46 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.

  At this point, I had to reset the computer.

  
  Detailed system information:
  lsdm: lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  xserver-xorg-video-nouveau 1:1.0.12-1build2

  root@lsdm:~# lspci
  00:00.0 RAM memory: NVIDIA Corporation MCP61 Host Bridge (rev a1)
  00:01.0 ISA bridge: NVIDIA Corporation MCP61 LPC Bridge (rev a2)
  00:01.1 SMBus: NVIDIA Corporation MCP61 SMBus (rev a2)
  00:01.2 RAM memory: NVIDIA Corporation MCP61 Memory Controller (rev a2)
  00:02.0 USB controller: NVIDIA Corporation MCP61 USB 1.1 Controller (rev a3)
  00:02.1 USB controller: NVIDIA Corporation MCP61 USB 2.0 Controller (rev a3)
  00:04.0 PCI bridge: NVIDIA Corporation MCP61 PCI bridge (rev a1)
  00:05.0 Audio device: NVIDIA Corporation MCP61 High Definition Audio (rev a2)
  00:06.0 IDE interface: NVIDIA Corporation MCP61 IDE (rev a2)
  00:07.0 Bridge: NVIDIA Corporation MCP61 Ethernet (rev a2)
  00:08.0 IDE interface: NVIDIA Corporation MCP61 SATA Controller (rev a2)
  00:08.1 IDE interface: NVIDIA Corporation MCP61 SATA Controller (rev a2)
  00:09.0 PCI 

[Touch-packages] [Bug 1687206] Re: screen goes blank

[dino99]

That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml


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

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

Title:
  screen goes blank

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  4 try the charm!! the screen goes blank randomly. I have tried
  every variable,version,bios setting, and ubuntu version. can't even
  get through the istall without hard restart for screen.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Apr 29 10:38:36 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev c5) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Carrizo [103c:80b0]
  InstallationDate: Installed on 2017-04-29 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: HP HP Pavilion Notebook
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic 
root=UUID=0e65c208-5506-4e3a-b42c-13d6248c23e1 ro plymouth:debug drm.debug=0xe
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.41
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 80B0
  dmi.board.vendor: HP
  dmi.board.version: 81.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.41:bd09/19/2016:svnHP:pnHPPavilionNotebook:pvr:rvnHP:rn80B0:rvr81.32:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Notebook
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.14-0ubuntu1
  xserver.bootTime: Sat Apr 29 10:37:20 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1
  xserver.video_driver: amdgpu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1687206/+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 1687200] Re: [SOLVED] [X441SA, Realtek ALC3236, Speaker, Internal] Playback problem No Sound on internal Speaker, But Normal with Headphones Jack

[dino99]

That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml


** 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/1687200

Title:
  [SOLVED] [X441SA, Realtek ALC3236, Speaker, Internal] Playback problem
  No Sound on internal Speaker, But Normal with Headphones Jack

Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  how to Patch This https://patchwork.kernel.org/patch/9596699/ ?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ubuntu 1545 F pulseaudio
  CurrentDesktop: Unity:Unity7
  Date: Sat Apr 29 21:20:53 2017
  InstallationDate: Installed on 2017-04-23 (6 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  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_Jack: Speaker, Internal
  Symptom_Type: Only some of outputs are working
  Title: [X441SA, Realtek ALC3236, Speaker, Internal] Playback problem
  UpgradeStatus: Upgraded to zesty on 2017-04-29 (0 days ago)
  dmi.bios.date: 06/13/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X441SA.300
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X441SA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX441SA.300:bd06/13/2016:svnASUSTeKCOMPUTERINC.:pnX441SA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX441SA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: X441SA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-04-25T03:57:03.973122

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

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

[Touch-packages] [Bug 1726124] Re: DNS domain search paths not updated when VPN started

[Jeroen Hoek]

I hope something can be worked out before this lands in the next LTS-
release. This breaks one of the most common uses of a VPN (remote work).

Right now a workaround is using this script after connecting to a VPN-
server:

https://github.com/jonathanio/update-systemd-resolved

It calls systemd-resolved via DBus to add the proper settings after the
OpenVPN connection is established.

Of course this means abandoning NetworkManager for use with OpenVPN,
because there is also no way to specify --up and --down parameters.

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

Title:
  DNS domain search paths not updated when VPN started

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

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

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

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

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

search home

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

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

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

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

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

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Oct 22 15:08:57 2017
  InstallationDate: Installed on 2017-10-21 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=UUID=4384306c-5fed-4b48-97a6-a6d594c4f72b ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2101
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M5A78L-M/USB3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  

[Touch-packages] [Bug 1746544] Re: Please merge xkeyboard-config 2.23.1-1 (main) from Debian unstable (main)

[Launchpad Bug Tracker]

This bug was fixed in the package xkeyboard-config - 2.23.1-1ubuntu1

---
xkeyboard-config (2.23.1-1ubuntu1) bionic; urgency=medium

  * Merge with Debian (LP: #1659183, LP: #1685774, LP: #1689110,
LP: #1746544), remaining changes:
- control, rules, xkb-data-i18n.install, xkb-data.install: Split out
  xkb-data-i18n to be used by console-setup.
- xkb-data.postinst: Remove the xkb cache to make sure it gets
  regenerated.
  * Dropped patch, applied upstream:
- d/p/elfdalian-kb-layout.diff

 -- Gunnar Hjalmarsson   Fri, 02 Feb 2018 12:47:00
+0100

** Changed in: xkeyboard-config (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 xkeyboard-config in
Ubuntu.
https://bugs.launchpad.net/bugs/1746544

Title:
  Please merge xkeyboard-config 2.23.1-1 (main) from Debian unstable
  (main)

Status in xkeyboard-config package in Ubuntu:
  Fix Released

Bug description:
  Version 2.23 of xkeyboard-config has been released upstream:

  https://cgit.freedesktop.org/xkeyboard-config/commit/?id=963db158

  It's highly desirable that this makes it in Ubuntu 18.04 LTS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1746544/+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 1738448] Re: gnome-online-accounts should recommend dleyna-server for Media Server support

[Launchpad Bug Tracker]

This bug was fixed in the package gnome-online-accounts - 3.26.2-2

---
gnome-online-accounts (3.26.2-2) unstable; urgency=medium

  * Update Vcs fields for migration to https://salsa.debian.org/
  * Use dh_missing --fail-missing
  * Don't enable Media Server option and drop dleyna-server recommends.
It is an experimental untested feature that was only used in GNOME
Photos and the GNOME Photos maintainer recommended we disable it.
(LP: #1738448)

 -- Jeremy Bicha   Thu, 01 Feb 2018 20:29:48 -0500

** Changed in: gnome-online-accounts (Ubuntu)
   Status: New => Fix Released

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

Title:
  gnome-online-accounts should recommend dleyna-server for Media Server
  support

Status in gnome-online-accounts package in Ubuntu:
  Fix Released

Bug description:
  Because dleyna-server is in universe, Ubuntu's gnome-online-accounts cannot 
recommend it like the Debian package does. I have pushed a hack to Debian to 
allow us to sync gnome-online-accounts and for the dependencies to be handled 
correctly.
  
https://anonscm.debian.org/git/pkg-gnome/gnome-online-accounts.git/commit/?id=e544639

  I am filing this as an informational bug since this issue will now be
  less visible than if there was a persistent diff with Debian.

  I think this will make the Media Server option in Settings > Online
  Accounts not work, but I don't have a Media Server here to test right
  now. This issue affects Ubuntu 17.10 and newer.

  Ideally, the Media Server account type should be hidden if it doesn't
  work, or modified to allow a user to easily install dleyna-server via
  PackageKit.

  Or we could try to get dleyna-server in to Ubuntu main.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1738448/+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 1747033] [NEW] transitional package dependency shouldn't be auto-removable

[Jeremy Bicha]

Public bug reported:

Test Case
=
1. From Ubuntu 18.04, uninstall gnome-tweaks and gnome-tweak-tool if installed.

2. Download gnome-tweak-tool from 17.10

https://launchpad.net/ubuntu/+source/gnome-tweak-
tool/3.26.2.1-1ubuntu1/+build/13538022

3. sudo apt install ./gnome-tweak-tool_3.26.2.1-1ubuntu1_all.deb

4. sudo apt dist-upgrade

(gnome-tweak-tool is now a transitional package that depends on gnome-
tweaks).

5. sudo apt remove gnome-tweak-tool

6. sudo apt dist-upgrade

The following package was automatically installed and is no longer required:
  gnome-tweaks
Use 'sudo apt autoremove' to remove it.

Excerpts from apt show
==
$ apt show gnome-tweaks
Package: gnome-tweaks
Version: 3.27.4-1ubuntu1
Priority: optional
Breaks: gnome-tweak-tool (<= 3.27.4)
Replaces: gnome-tweak-tool (<= 3.27.4)
APT-Manual-Installed: no

$ apt show gnome-tweak-tool
Package: gnome-tweak-tool
Version: 3.27.4-1ubuntu1
Priority: optional
Section: universe/gnome
Source: gnome-tweaks
Depends: gnome-tweaks
Description: adjust advanced settings for GNOME - transitional package
 GNOME Tweak Tool allows the adjustment of several advanced GNOME
 options that can't be configured in gnome-control-center.
 .
 This package is here to ensure smooth upgrades. It can be removed when
 you see fit.

What's Wrong

I think that "APT-Manual-Installed: no" should not be set for gnome-tweaks.

Hmm, gnome-tweak-tool should be universe/oldlibs now. (Debian also
currently has it in 'gnome' instead of oldlibs.)

** 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/1747033

Title:
  transitional package dependency shouldn't be auto-removable

Status in apt package in Ubuntu:
  New

Bug description:
  Test Case
  =
  1. From Ubuntu 18.04, uninstall gnome-tweaks and gnome-tweak-tool if 
installed.

  2. Download gnome-tweak-tool from 17.10

  https://launchpad.net/ubuntu/+source/gnome-tweak-
  tool/3.26.2.1-1ubuntu1/+build/13538022

  3. sudo apt install ./gnome-tweak-tool_3.26.2.1-1ubuntu1_all.deb

  4. sudo apt dist-upgrade

  (gnome-tweak-tool is now a transitional package that depends on gnome-
  tweaks).

  5. sudo apt remove gnome-tweak-tool

  6. sudo apt dist-upgrade

  The following package was automatically installed and is no longer required:
gnome-tweaks
  Use 'sudo apt autoremove' to remove it.

  Excerpts from apt show
  ==
  $ apt show gnome-tweaks
  Package: gnome-tweaks
  Version: 3.27.4-1ubuntu1
  Priority: optional
  Breaks: gnome-tweak-tool (<= 3.27.4)
  Replaces: gnome-tweak-tool (<= 3.27.4)
  APT-Manual-Installed: no

  $ apt show gnome-tweak-tool
  Package: gnome-tweak-tool
  Version: 3.27.4-1ubuntu1
  Priority: optional
  Section: universe/gnome
  Source: gnome-tweaks
  Depends: gnome-tweaks
  Description: adjust advanced settings for GNOME - transitional package
   GNOME Tweak Tool allows the adjustment of several advanced GNOME
   options that can't be configured in gnome-control-center.
   .
   This package is here to ensure smooth upgrades. It can be removed when
   you see fit.

  What's Wrong
  
  I think that "APT-Manual-Installed: no" should not be set for gnome-tweaks.

  Hmm, gnome-tweak-tool should be universe/oldlibs now. (Debian also
  currently has it in 'gnome' instead of oldlibs.)

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

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

[Touch-packages] [Bug 1726124] Re: DNS domain search paths not updated when VPN started

[Launchpad Bug Tracker]

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

** Changed in: network-manager-openvpn (Ubuntu)
   Status: New => Confirmed

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

Title:
  DNS domain search paths not updated when VPN started

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

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

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

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

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

search home

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

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

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

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

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

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Oct 22 15:08:57 2017
  InstallationDate: Installed on 2017-10-21 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=UUID=4384306c-5fed-4b48-97a6-a6d594c4f72b ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2101
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M5A78L-M/USB3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2101:bd12/02/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-M/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  

[Touch-packages] [Bug 1687212] Re: ~16 GB written to disk from power on till lightdb login screen?

[dino99]

That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml


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

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

Title:
  ~16 GB written to disk from power on till lightdb login screen?

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  After each system boot, iostat -m shows that the kernel has written
  around 16 GB to SSD disk:

  avg-cpu:  %user   %nice %system %iowait  %steal   %idle
     9.100.00   10.062.380.00   78.47

  Device:tpsMB_read/sMB_wrtn/sMB_readMB_wrtn
  sda 702.3216.91  1495.65182  16108
  dm-0808.3615.64  1495.65168  16108
  dm-1786.8215.39 0.01165  0
  dm-2 10.21 0.21  1495.64  2  16107

  It's a fresh Ubuntu 17.04 installation with rootfs installed on
  encrypted LVM (selected during the installation).

  /proc/diskstats (https://www.kernel.org/doc/Documentation/ABI/testing
  /procfs-diskstats) seem to be matching the output of "iostat -m".

  Please note that dm-2 is 16 GB swap (the system has 16 GB RAM):

  $ ls /dev/mapper/ -l
  total 0
  crw--- 1 root root 10, 236 Apr 30 01:53 control
  lrwxrwxrwx 1 root root   7 Apr 30 01:53 sda3_crypt -> ../dm-0
  lrwxrwxrwx 1 root root   7 Apr 30 01:53 ubuntu--vg-root -> ../dm-1
  lrwxrwxrwx 1 root root   7 Apr 30 01:53 ubuntu--vg-swap_1 -> ../dm-2

  $ cat /proc/swaps
  FilenameTypeSizeUsed
Priority
  /dev/dm-2   partition   164945880 
  -1

  So what seems to happen, is that the OS overwrites the whole encrypted
  swap partition during bootup.

  This is very worrying, given that it's SSD disk!

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-21ubuntu3
  Uname: Linux 4.11.0-041100rc7-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  Date: Sun Apr 30 01:57:04 2017
  ExecutablePath: /lib/systemd/systemd
  InstallationDate: Installed on 2017-04-14 (15 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
   Bus 001 Device 003: ID 1bcf:2b95 Sunplus Innovation Technology Inc.
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Precision 5520
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-041100rc7-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/29/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.2.4
  dmi.board.name: 0GPNW9
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.2.4:bd03/29/2017:svnDellInc.:pnPrecision5520:pvr:rvnDellInc.:rn0GPNW9:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.name: Precision 5520
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1687212/+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 1746765] Re: systemd FTBFS on arm64

[Julian Andres Klode]

At least for now, so we don't block stuff.

** Changed in: gnu-efi (Ubuntu Bionic)
   Status: Invalid => 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/1746765

Title:
  systemd FTBFS on arm64

Status in binutils:
  Confirmed
Status in binutils package in Ubuntu:
  New
Status in gnu-efi package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Confirmed
Status in binutils source package in Bionic:
  New
Status in gnu-efi source package in Bionic:
  New
Status in systemd source package in Bionic:
  Confirmed

Bug description:
  Might be a bug in the toolchain, gnu-efi or systemd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/binutils/+bug/1746765/+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 349469] Re: debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by another process: Resource temporarily unavailable

[Chaitanya Ram]

** Changed in: aptdaemon (Ubuntu)
   Status: Invalid => Fix Released

** Changed in: debconf (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

Status in Aptdaemon:
  Fix Released
Status in Debconf:
  New
Status in aptdaemon package in Ubuntu:
  Fix Released
Status in debconf package in Ubuntu:
  Fix Released

Bug description:
  Upgrading packages that use debconf sometimes fail with the following
  error:

  debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by
  another process: Resource temporarily unavailable

To manage notifications about this bug go to:
https://bugs.launchpad.net/aptdaemon/+bug/349469/+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 1687352] Re: Graphics Corruption on Hardware Accelerated Softwares

[dino99]

That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml


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

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

Title:
  Graphics Corruption on Hardware Accelerated Softwares

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Applications like Blender (downloaded from blender website for linux) and 
SimCity 4 (running through Wine with Hardware Acceleration enabled) have their 
windows graphics corrupted as saw in the attachment's print screen image 
(Blender).
  Maybe this problem is OpenGL related, it's just a guess.
  It didn't occur on Ubuntu 16.10 Yakkety Yak.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sun Apr 30 23:43:40 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6290] [1002:9807] 
(prog-if 00 [VGA controller])
     Subsystem: Elitegroup Computer Systems Wrestler [Radeon HD 6290] 
[1019:3141]
  InstallationDate: Installed on 2017-01-14 (106 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic 
root=UUID=2db4e4b3-e99a-4d11-96af-5d10de0134c4 ro rootflags=sync splash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/09/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 4.6.4
  dmi.board.name: HDC-M
  dmi.board.version: 1.0
  dmi.chassis.type: 3
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr4.6.4:bd04/09/2012:svn:pnHDC-M:pvr1.0:rvn:rnHDC-M:rvr1.0:cvn:ct3:cvr1.0:
  dmi.product.name: HDC-M
  dmi.product.version: 1.0
  version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.14-0ubuntu1
  xserver.bootTime: Sun Apr 30 23:33:33 2017
  xserver.configfile: default
  xserver.errors:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1687352/+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 1688017] Re: Connection to bluetooth headsets fails

[dino99]

That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml

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

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

Title:
  Connection to bluetooth headsets fails

Status in bluez package in Ubuntu:
  Invalid

Bug description:
  Hi,

  since upgrading to 17.04 I can't connect to bluetooth headsets
  anymore. Headsets are found and listed as devices, but when trying to
  connect, there's an error

  blueman.bluez.errors.DBusFailedError: Protocol not available...

  
  syslog says:

  May  3 16:43:12 pcdanisch bluetoothd[2075]: a2dp-sink profile connect failed 
for 00:18:91:4F:E5:C6: Protocol not available
  May  3 16:47:18 pcdanisch bluetoothd[2075]: message repeated 8 times: [ 
a2dp-sink profile connect failed for 00:18:91:4F:E5:C6: Protocol not available]
  May  3 16:48:14 pcdanisch bluetoothd[2075]: EF:AC:86:08:6F:21: error updating 
services: Operation already in progress (114)
  May  3 16:50:56 pcdanisch bluetoothd[2075]: a2dp-sink profile connect failed 
for 00:18:91:4F:E5:C6: Protocol not available
  May  3 16:53:01 pcdanisch bluetoothd[2075]: Pair device timed out for hci0
  May  3 16:59:30 pcdanisch bluetoothd[2075]: a2dp-sink profile connect failed 
for 00:18:91:4F:E5:C6: Protocol not available
  May  3 17:04:11 pcdanisch bluetoothd[2075]: message repeated 3 times: [ 
a2dp-sink profile connect failed for 00:18:91:4F:E5:C6: Protocol not available]



  Here someone else reports the same observation:
  
http://www.1oo.club/bluetooth-unable-to-connect-to-headphones-after-ubuntu-17-04-upgrade/

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: bluez 5.43-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed May  3 17:12:51 2017
  InstallationDate: Installed on 2016-04-22 (376 days ago)
  InstallationMedia: Lubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420)
  InterestingModules: bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:0821 Realtek Semiconductor Corp. 
   Bus 001 Device 003: ID 046d:c31d Logitech, Inc. Media Keyboard K200
   Bus 001 Device 002: ID 046d:c05b Logitech, Inc. M-U0004 810-001317 [B110 
Optical USB Mouse]
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-20-generic 
root=UUID=d0b47754-d5ca-49ec-8190-92a24e58e373 ro rootflags=subvol=@ nosplash 
noplymouth nomodeset text
  SourcePackage: bluez
  UpgradeStatus: Upgraded to zesty on 2017-04-18 (15 days ago)
  dmi.bios.date: 03/16/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.50
  dmi.board.name: N3150-NUC
  dmi.board.vendor: ASRock
  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.:bvrP1.50:bd03/16/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN3150-NUC:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 4C:BB:58:C1:E9:FA  ACL MTU: 820:8  SCO MTU: 255:16
UP RUNNING PSCAN 
RX bytes:18751 acl:51 sco:0 events:1345 errors:0
TX bytes:27309 acl:48 sco:0 commands:1243 errors:0

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

[Eric Desrochers]

** Patch added: "profile-14.04-trusty-lp1717714_V2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1717714/+attachment/5047668/+files/profile-14.04-trusty-lp1717714_V2.debdiff

-- 
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:
  Fix Released
Status in apparmor source package in Trusty:
  Fix Committed
Status in apparmor source package in Xenial:
  Fix Committed
Status in apparmor source package in Artful:
  Fix Committed
Status in apparmor source package in Bionic:
  Fix Released
Status in apparmor package in Debian:
  Fix Released

Bug description:
  [Impact]

  If PID is larger than 6 digits apparmor denies process which only
  affect 64-bit systems[1] where the PID_MAX_LIMIT can be generated up
  to 7 digits at the maximum.

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

  [1] - man 5 proc

  --
  /proc/sys/kernel/pid_max (since Linux 2.5.34)
  This file specifies the value at which PIDs wrap around (i.e., the value in 
this file is one greater than the maximum PID).  PIDs greater than this value 
are not allocated;  thus,  the value  in this file also acts as a system-wide 
limit on the total number of processes and threads.  The default value for this 
file, 32768, results in the same range of PIDs as on ear‐lier kernels.  On 
32-bit platforms, 32768 is the maximum value for pid_max.  On 64-bit systems, 
pid_max can be set to any value up to 2^22 (PID_MAX_LIMIT, approximately 4 
million).
  --

  [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

  OR

  instead of Seyeong's touch approach, things can be manually change to
  7 digits range via sysctl as long as the values are below
  approximately 4 millions :

  Example:
  $ sysctl -w kernel.pid_max=300
  $ sysctl -w kernel.ns_last_pid=100

  [Regression]
  * This is a minor/trivial fix which changes the pid regex only, allowing 7 
digits PID instead of only 6 digits PID, we don't think there is any potential 
regression.

  * If a regression arise, which we highly doubt, one can quickly revert
  the change manually and restart the service by modifying
  "/etc/apparmor.d/tunables/kernelvars" file to its original state
  (before this SRU).

  [Others]

  * Upstream commit:
   
https://gitlab.com/apparmor/apparmor/commit/630cb2a981cdc731847e8fdaafc45bcd337fe747
  http://bazaar.launchpad.net/~apparmor-dev/apparmor/master/revision/3722

  * Debian bug:
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886732

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

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

[Touch-packages] [Bug 38694] A change has been merged

[OpenContrail Admin]

Reviewed:  https://review.opencontrail.org/39137
Committed: 
http://github.com/Juniper/contrail-fabric-utils/commit/e45f84e5a28728f7c1f65935d1f28490a2ef2d70
Submitter: Zuul (z...@lists.opencontrail.org)
Branch:R4.0

commit e45f84e5a28728f7c1f65935d1f28490a2ef2d70
Author: ankitja 
Date:   Mon Jan 15 15:12:41 2018 +0530

Fix attach_logs_cores issue

Closes-bug: #38694

Change-Id: I9aac6d913aa83f7ae94ebb406395b35c0eb0e6a9


** Changed in: juniperopenstack/r4.0
   Status: In Progress => Fix Committed

** Changed in: juniperopenstack/r4.0
Milestone: None => r4.0.3.0

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

Title:
  No XChat in Dapper

Status in Juniper Openstack:
  Fix Committed
Status in Juniper Openstack r4.0 series:
  Fix Committed
Status in Juniper Openstack r4.1 series:
  Fix Committed
Status in Juniper Openstack trunk series:
  Fix Committed
Status in ubuntu-meta package in Ubuntu:
  Invalid

Bug description:
  Apparently someone made the decision to remove XChat from the default
  installation for Dapper.  This is important because it is the means
  new users use to reach the various IRC channels on Freenode and all
  the support those have to offer.  I understand that Gaim is still
  included and supports IRC, but this has a few problems as an
  alternative.  First, new users are not going to thing that Gaim
  Internet Messenger in their Applications menu has anything to do with
  getting support.  Second, setting up, connecting to, and using IRC
  isn't entirely intuitive.  Third, many people simply don't like Gaim's
  IRC UI.  Fourth, it does not have the built-in setting like XChat had
  to automatically join #ubuntu when first started.  In short, a brand
  new user is significantly less likely to manage to find the support of
  the IRC channels on their first boot of Ubuntu without XChat included
  and not knowing the ropes pretty well already.  The IRC channels are
  an absolutely vital way of helping new users, and must be very easily
  accessible.  Inclusion of XChat is a big step towards that.  (Further
  UI setup for first boot are an issue as well, but that's a separate
  issue.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/juniperopenstack/+bug/38694/+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 1316970] Re: g_dbus memory leak in lrmd

[Dan Streetman]

Hi Seyeong,

first, I commend you for going to the trouble of fixing tests in
lp1316970_trusty_glib2.0.debdiff, but I think those are unrelated to
this actual bug and so the patch is not required for this.  I'll focus
only on the first patch.

In that patch, I did a quick review of the changes, and I'm not entirely
sure they are correct?  LP bug comments are not a great format for
reviewing patches, so please excuse formatting/line-wrapping:


> --- a/lib/services/upstart.c
> +++ b/lib/services/upstart.c
> @@ -70,6 +70,7 @@
>  if (error) {
>  crm_err("Can't connect obtain proxy to %s interface: %s", interface, 
> error->message);
>  g_error_free(error);
> +g_object_unref(proxy);

this doesn't seem right - if error is non-NULL, then proxy should be NULL, 
according to the docs:
https://developer.gnome.org/gio/stable/GDBusProxy.html#g-dbus-proxy-new-for-bus-sync

>  proxy = NULL;
>  }
>  return proxy;
> @@ -107,7 +108,9 @@
>  /*
>com.ubuntu.Upstart0_6.GetJobByName (in String name, out ObjectPath job)
>  */
> -GVariant *_ret = g_dbus_proxy_call_sync(proxy, "GetJobByName", 
> g_variant_new("(s)", arg_name),
> +GVariant *_ret = NULL;
> +
> +_ret = g_dbus_proxy_call_sync(proxy, "GetJobByName", 
> g_variant_new("(s)", arg_name),
>  G_DBUS_CALL_FLAGS_NONE, -1, 
> cancellable, error);

unless i'm missing something, there is no need for this change?

>  
>  if (_ret) {
> @@ -200,6 +203,7 @@
>  
>  g_variant_iter_free(iter);
>  g_variant_unref(_ret);
> +free(path);

this does not seem correct - per the docs, 'path' will be freed by each call in 
the while loop to g_variant_iter_loop(), and only needs to be manually freed 
after the while loop if the code breaks out of the loop manually.  That doesn't 
appear to be the case, so path should not need freeing here.
https://developer.gnome.org/glib/stable/glib-GVariant.html#g-variant-iter-loop

>  return units;
>  }
>  
> @@ -224,7 +228,7 @@
>  } else if (pass) {
>  crm_trace("Got %s", path);
>  }
> -/* free(path) */
> +free(path);

technically this should be freed only if !error - the freeing should go
into the else if (pass) block above, although free(NULL) will just do
nothing

however, i believe this should use g_free() instead of free()

>  return pass;
>  }
>  
> @@ -272,6 +276,8 @@
>  
>  g_object_unref(proxy);
>  g_variant_unref(_ret);
> +g_variant_unref(value);
> +g_variant_unref(asv);

asv is returned from g_variant_get_child_value, which does state in its docs 
that the returned value should be unref'ed, so this looks correct for 'asv'.
https://developer.gnome.org/glib/stable/glib-GVariant.html#g-variant-get-child-value

However value is returned from g_variant_lookup_value, which returns a value 
from a key-value pair in asv (as best i can tell from the docs for the 
function), and it does not indicate that the value is newly allocated or that 
it should be freed.  So it does not appear that 'value' should be unref'ed here.
https://developer.gnome.org/glib/stable/glib-GVariant.html#g-variant-lookup-value

>  return output;
>  }
>  
> @@ -299,11 +305,14 @@
>  GVariant *tmp2 = g_variant_get_child_value(tmp1, 0);
>  
>  instance = g_variant_dup_string(tmp2, NULL);
> +g_variant_unref(tmp2);
>  }
> +g_variant_unref(tmp1);

these look correct

>  }
>  
>  crm_info("Result: %s", instance);
>  g_variant_unref(_ret);
> +g_object_unref(proxy);

this looks correct

>  return instance;
>  }
>  
> @@ -338,6 +347,7 @@
>  }
>  
>  crm_info("%s is%s running", name, pass ? "" : " not");
> +free(job);

technically this is only needed in the else {} block, but as it should
still be NULL the free will do nothing

again this should be g_free() instead of free() i think

>  return pass;
>  }
>  
> @@ -400,6 +410,7 @@
>  crm_info("Call to %s passed: type '%s' %s", op->action, 
> g_variant_get_type_string(_ret),
>   path);
>  op->rc = PCMK_EXECRA_OK;
> +free(path);

looks good, but probably use g_free()

>  
>  } else {
>  crm_err("Call to %s passed but return type was '%s' not '(o)'", 
> op->action, g_variant_get_type_string(_ret));
> @@ -501,6 +512,7 @@
>  crm_info("Call to %s passed: type '%s' %s", op->action, 
> g_variant_get_type_string(_ret),
>   path);
>  op->rc = PCMK_EXECRA_OK;
> +free(path);

looks good, but probably use g_free()

>  
>  } else {
>  crm_err("Call to %s passed but return type was '%s' not '(o)'", 
> op->action, g_variant_get_type_string(_ret));

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

Title:
  g_dbus memory leak in lrmd

Status in glib2.0 package in Ubuntu:
  New

[Touch-packages] [Bug 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits

[Eric Desrochers]

Got a confirmation by SRU verification that the new debdiff was SRU'able.
I have uploaded V2 a few minutes ago. It is now waiting on SRU team for 
approval and then should land in trusty-proposed.

- Eric

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

** Changed in: apparmor (Ubuntu Trusty)
 Assignee: Seyeong Kim (xtrusia) => Eric Desrochers (slashd)

-- 
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:
  Fix Released
Status in apparmor source package in Trusty:
  In Progress
Status in apparmor source package in Xenial:
  Fix Committed
Status in apparmor source package in Artful:
  Fix Committed
Status in apparmor source package in Bionic:
  Fix Released
Status in apparmor package in Debian:
  Fix Released

Bug description:
  [Impact]

  If PID is larger than 6 digits apparmor denies process which only
  affect 64-bit systems[1] where the PID_MAX_LIMIT can be generated up
  to 7 digits at the maximum.

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

  [1] - man 5 proc

  --
  /proc/sys/kernel/pid_max (since Linux 2.5.34)
  This file specifies the value at which PIDs wrap around (i.e., the value in 
this file is one greater than the maximum PID).  PIDs greater than this value 
are not allocated;  thus,  the value  in this file also acts as a system-wide 
limit on the total number of processes and threads.  The default value for this 
file, 32768, results in the same range of PIDs as on ear‐lier kernels.  On 
32-bit platforms, 32768 is the maximum value for pid_max.  On 64-bit systems, 
pid_max can be set to any value up to 2^22 (PID_MAX_LIMIT, approximately 4 
million).
  --

  [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

  OR

  instead of Seyeong's touch approach, things can be manually change to
  7 digits range via sysctl as long as the values are below
  approximately 4 millions :

  Example:
  $ sysctl -w kernel.pid_max=300
  $ sysctl -w kernel.ns_last_pid=100

  [Regression]
  * This is a minor/trivial fix which changes the pid regex only, allowing 7 
digits PID instead of only 6 digits PID, we don't think there is any potential 
regression.

  * If a regression arise, which we highly doubt, one can quickly revert
  the change manually and restart the service by modifying
  "/etc/apparmor.d/tunables/kernelvars" file to its original state
  (before this SRU).

  [Others]

  * Upstream commit:
   
https://gitlab.com/apparmor/apparmor/commit/630cb2a981cdc731847e8fdaafc45bcd337fe747
  http://bazaar.launchpad.net/~apparmor-dev/apparmor/master/revision/3722

  * Debian bug:
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886732

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

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

[Touch-packages] [Bug 1649566] ProcInterrupts.txt

[Dieter Maurer]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1649566/+attachment/5047623/+files/ProcInterrupts.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/1649566

Title:
  xserver-xorg-video-nouveau: X freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Yesterday, I upgraded from Ubuntu 12.04 via 14.04 to 16.04 (LTS
  version in each case). From 14.04 on, I was unable to graphically log
  in. A few seconds after the login (varying between 1 and 10 s), the
  screen changed to a pattern with dense white stripes on the violet/red
  background, and X froze (no reaction to mouse or keyboard). The latest
  messages in "/var/log/syslog" each time showed varying "nouveau E"
  problems, e.g. "unrecognized interupt", "PFIFO", or "PBUS" problems
  such as e.g.: "nouveau E[PBUS][:00:0d.0] MMIO write of
  0x01f70001 FAULT at 0x00b010" (values and addresses varying).

  An internet search revealed that the problem is well known. It affects
  many NVidia graphic cards with the "nouveau" driver. Usually, the
  freeze happens when e.g. "firefox" is started (which happens in my
  context automatically after a graphical login). Most reports recommend
  to switch from "nouveau" to the proprietary NVidia driver. However,
  there seem to be problems with that driver for recent Ubuntu versions.
  I my case, the NVidia driver could not be started (I did not
  investigate why). One report suggested the boot parameter
  "nouveau.config=NvMSI=0" which in my case made the graphical login
  successful again.

  Today, I wanted to report the bug with "ubuntu-bug". However, during the 
collection of the system information, the error happened again (despite the 
"nouveau.config" boot parameter).
  Syslog gives:
  ...
  Dec 13 11:12:01 localhost CRON[5230]: (root) CMD (   test -x 
/etc/cron.daily/popularity-contest && /etc/cron.daily/popularity-contest 
--crond)
  Dec 13 11:14:16 localhost kernel: [ 6889.138599] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:16 localhost kernel: [ 6889.140532] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:59 localhost dbus[795]: [system] Activating service 
name='com.ubuntu.SoftwareProperties' (using servicehelper)
  Dec 13 11:14:59 localhost dbus[795]: [system] Successfully activated service 
'com.ubuntu.SoftwareProperties'
  Dec 13 11:15:01 localhost CRON[5285]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:17:01 localhost CRON[5303]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)
  Dec 13 11:20:01 localhost CRON[5327]: (smmsp) CMD (test -x 
/etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x 
/usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp)
  Dec 13 11:22:20 localhost kernel: [ 7372.621357] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x FAULT at 0x00b020
  Dec 13 11:25:01 localhost CRON[5580]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:35:01 localhost CRON[5651]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:38:02 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.
  Dec 13 11:39:01 localhost CRON[5723]: (root) CMD (  [ -x 
/usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d 
/var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 
$(/usr/lib/php5/maxlifetime))
  Dec 13 11:39:01 localhost CRON[5722]: (root) CMD (  [ -x 
/usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)
  Dec 13 11:39:46 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.

  At this point, I had to reset the computer.

  
  Detailed system information:
  lsdm: lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  xserver-xorg-video-nouveau 1:1.0.12-1build2

  root@lsdm:~# lspci
  00:00.0 RAM memory: NVIDIA Corporation MCP61 Host Bridge (rev a1)
  00:01.0 ISA bridge: NVIDIA Corporation MCP61 LPC Bridge (rev a2)
  00:01.1 SMBus: NVIDIA Corporation MCP61 SMBus (rev a2)
  00:01.2 RAM memory: NVIDIA Corporation MCP61 Memory Controller (rev a2)
  00:02.0 USB controller: NVIDIA Corporation MCP61 USB 1.1 Controller (rev a3)
  00:02.1 USB controller: NVIDIA Corporation MCP61 USB 2.0 Controller (rev a3)
  00:04.0 PCI bridge: NVIDIA Corporation MCP61 PCI bridge (rev a1)
  00:05.0 Audio device: NVIDIA Corporation MCP61 High Definition Audio (rev a2)
  00:06.0 IDE interface: NVIDIA Corporation MCP61 IDE (rev a2)
  00:07.0 Bridge: NVIDIA Corporation MCP61 Ethernet (rev a2)
  00:08.0 IDE interface: NVIDIA Corporation MCP61 SATA Controller (rev a2)
  00:08.1 IDE interface: NVIDIA Corporation MCP61 SATA Controller (rev a2)
  00:09.0 PCI 

[Touch-packages] [Bug 1649566] ProcCpuinfo.txt

[Dieter Maurer]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1649566/+attachment/5047621/+files/ProcCpuinfo.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/1649566

Title:
  xserver-xorg-video-nouveau: X freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Yesterday, I upgraded from Ubuntu 12.04 via 14.04 to 16.04 (LTS
  version in each case). From 14.04 on, I was unable to graphically log
  in. A few seconds after the login (varying between 1 and 10 s), the
  screen changed to a pattern with dense white stripes on the violet/red
  background, and X froze (no reaction to mouse or keyboard). The latest
  messages in "/var/log/syslog" each time showed varying "nouveau E"
  problems, e.g. "unrecognized interupt", "PFIFO", or "PBUS" problems
  such as e.g.: "nouveau E[PBUS][:00:0d.0] MMIO write of
  0x01f70001 FAULT at 0x00b010" (values and addresses varying).

  An internet search revealed that the problem is well known. It affects
  many NVidia graphic cards with the "nouveau" driver. Usually, the
  freeze happens when e.g. "firefox" is started (which happens in my
  context automatically after a graphical login). Most reports recommend
  to switch from "nouveau" to the proprietary NVidia driver. However,
  there seem to be problems with that driver for recent Ubuntu versions.
  I my case, the NVidia driver could not be started (I did not
  investigate why). One report suggested the boot parameter
  "nouveau.config=NvMSI=0" which in my case made the graphical login
  successful again.

  Today, I wanted to report the bug with "ubuntu-bug". However, during the 
collection of the system information, the error happened again (despite the 
"nouveau.config" boot parameter).
  Syslog gives:
  ...
  Dec 13 11:12:01 localhost CRON[5230]: (root) CMD (   test -x 
/etc/cron.daily/popularity-contest && /etc/cron.daily/popularity-contest 
--crond)
  Dec 13 11:14:16 localhost kernel: [ 6889.138599] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:16 localhost kernel: [ 6889.140532] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:59 localhost dbus[795]: [system] Activating service 
name='com.ubuntu.SoftwareProperties' (using servicehelper)
  Dec 13 11:14:59 localhost dbus[795]: [system] Successfully activated service 
'com.ubuntu.SoftwareProperties'
  Dec 13 11:15:01 localhost CRON[5285]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:17:01 localhost CRON[5303]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)
  Dec 13 11:20:01 localhost CRON[5327]: (smmsp) CMD (test -x 
/etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x 
/usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp)
  Dec 13 11:22:20 localhost kernel: [ 7372.621357] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x FAULT at 0x00b020
  Dec 13 11:25:01 localhost CRON[5580]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:35:01 localhost CRON[5651]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:38:02 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.
  Dec 13 11:39:01 localhost CRON[5723]: (root) CMD (  [ -x 
/usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d 
/var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 
$(/usr/lib/php5/maxlifetime))
  Dec 13 11:39:01 localhost CRON[5722]: (root) CMD (  [ -x 
/usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)
  Dec 13 11:39:46 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.

  At this point, I had to reset the computer.

  
  Detailed system information:
  lsdm: lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  xserver-xorg-video-nouveau 1:1.0.12-1build2

  root@lsdm:~# lspci
  00:00.0 RAM memory: NVIDIA Corporation MCP61 Host Bridge (rev a1)
  00:01.0 ISA bridge: NVIDIA Corporation MCP61 LPC Bridge (rev a2)
  00:01.1 SMBus: NVIDIA Corporation MCP61 SMBus (rev a2)
  00:01.2 RAM memory: NVIDIA Corporation MCP61 Memory Controller (rev a2)
  00:02.0 USB controller: NVIDIA Corporation MCP61 USB 1.1 Controller (rev a3)
  00:02.1 USB controller: NVIDIA Corporation MCP61 USB 2.0 Controller (rev a3)
  00:04.0 PCI bridge: NVIDIA Corporation MCP61 PCI bridge (rev a1)
  00:05.0 Audio device: NVIDIA Corporation MCP61 High Definition Audio (rev a2)
  00:06.0 IDE interface: NVIDIA Corporation MCP61 IDE (rev a2)
  00:07.0 Bridge: NVIDIA Corporation MCP61 Ethernet (rev a2)
  00:08.0 IDE interface: NVIDIA Corporation MCP61 SATA Controller (rev a2)
  00:08.1 IDE interface: NVIDIA Corporation MCP61 SATA Controller (rev a2)
  00:09.0 PCI 

[Touch-packages] [Bug 1735929] Re: security problems with incorrect permissions for ubuntu 17.10

[Marc Deslauriers]

Related bug in ubuntu-mate-welcome: bug 1745929

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

Title:
  security problems with incorrect permissions for ubuntu 17.10

Status in dconf:
  Confirmed
Status in gnome-session:
  Confirmed
Status in d-conf package in Ubuntu:
  Triaged
Status in dconf package in Ubuntu:
  Triaged
Status in gnome-session package in Ubuntu:
  Triaged
Status in session-migration package in Ubuntu:
  Fix Released

Bug description:
  The release of Ubuntu you are using (lsb_release -rd):
  Description:  Ubuntu 17.10
  Release:  17.10

  This is a fresh installation of Ubuntu 17.10 from the mini.iso.
  I select only default options + [Ubuntu Desktop] installation.

  What you expected to happen:
  My home folder contains the following folders with correct and safe 
permissions after the first login:
  drwx-- 11 user user 4096 Dec  2 17:40 .config
  drwx--  3 user user 4096 Dec  2 17:39 .local

  What happened instead:
  I received these folders after the first login:
  drwxr-xr-x 11 user user 4096 Dec  2 17:40 .config
  drwxr-xr-x  3 user user 4096 Dec  2 17:39 .local
  It is not safe. Any user can access to my .config folders and read for 
example my mail databases

  I'm trying to create a new user...:
  sudo useradd -m user2
  sudo passwd user2
  ... and login then.
  It has the same problem:
  drwxr-xr-x 10 user2 user2 4096 Dec  2 19:44 .config
  drwxr-xr-x  3 user2 user2 4096 Dec  2 19:44 .local

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

[Eric Desrochers]

I have re-did the SRU by renaming/modifying the existing patch to adapt
to the profile-14.04.


[VALIDATION PRE-UPLOAD]

# dpkg -l | grep -i apparmor
ii  apparmor 2.10.95-0ubuntu2.6~14.04.3 
amd64user-space parser utility for AppArmor
ii  libapparmor-perl 2.10.95-0ubuntu2.6~14.04.1 
amd64AppArmor library Perl bindings
ii  libapparmor1:amd64   2.10.95-0ubuntu2.6~14.04.1 
amd64changehat AppArmor library


# grep "@{pid}=" /etc/apparmor.d/tunables/kernelvars  | grep -v "#"
@{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],[1-4][0-9][0-9][0-9][0-9][0-9][0-9]}


# diff -u /tmp/kernelvars_2.10.95-0ubuntu2.6~14.04.2 
/tmp/kernelvars_2.10.95-0ubuntu2.6~14.04.3
--- /tmp/kernelvars_2.10.95-0ubuntu2.6~14.04.2  2018-02-02 16:13:34.391910246 
+
+++ /tmp/kernelvars_2.10.95-0ubuntu2.6~14.04.3  2018-02-02 16:14:25.880489983 
+
@@ -13,7 +13,7 @@
 # and until the parser supports nested groupings like
 #   @{pid}=[1-9]{[0-9]{[0-9]{[0-9]{[0-9]{[0-9],},},},},}
 # use
-@{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]}
+@{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],[1-4][0-9][0-9][0-9][0-9][0-9][0-9]}
 
 #same pattern as @{pid} for now
 @{tid}=@{pid}


The above confirm that the patch is now taking into account as it should.

- Eric

-- 
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:
  Fix Released
Status in apparmor source package in Trusty:
  Fix Committed
Status in apparmor source package in Xenial:
  Fix Committed
Status in apparmor source package in Artful:
  Fix Committed
Status in apparmor source package in Bionic:
  Fix Released
Status in apparmor package in Debian:
  Fix Released

Bug description:
  [Impact]

  If PID is larger than 6 digits apparmor denies process which only
  affect 64-bit systems[1] where the PID_MAX_LIMIT can be generated up
  to 7 digits at the maximum.

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

  [1] - man 5 proc

  --
  /proc/sys/kernel/pid_max (since Linux 2.5.34)
  This file specifies the value at which PIDs wrap around (i.e., the value in 
this file is one greater than the maximum PID).  PIDs greater than this value 
are not allocated;  thus,  the value  in this file also acts as a system-wide 
limit on the total number of processes and threads.  The default value for this 
file, 32768, results in the same range of PIDs as on ear‐lier kernels.  On 
32-bit platforms, 32768 is the maximum value for pid_max.  On 64-bit systems, 
pid_max can be set to any value up to 2^22 (PID_MAX_LIMIT, approximately 4 
million).
  --

  [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

  OR

  instead of Seyeong's touch approach, things can be manually change to
  7 digits range via sysctl as long as the values are below
  approximately 4 millions :

  Example:
  $ sysctl -w kernel.pid_max=300
  $ sysctl -w kernel.ns_last_pid=100

  [Regression]
  * This is a minor/trivial fix which changes the pid regex only, allowing 7 
digits PID instead of only 6 digits PID, we don't think there is any potential 
regression.

  * If a regression arise, which we highly doubt, one can quickly revert
  the change manually and restart the service by modifying
  "/etc/apparmor.d/tunables/kernelvars" file to its original state
  (before this SRU).

  [Others]

  * Upstream commit:
   
https://gitlab.com/apparmor/apparmor/commit/630cb2a981cdc731847e8fdaafc45bcd337fe747
  http://bazaar.launchpad.net/~apparmor-dev/apparmor/master/revision/3722

  * Debian bug:
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886732

  * commit 630cb2a981cdc731847e8fdaafc45bcd337fe747
  Author: Vincas Dargis 
  Date:   Sat Sep 30 15:28:15 2017 +0300

  Allow seven digit pid

  * Affecting releases 

[Touch-packages] [Bug 1689316] Re: Desktop freeze

[dino99]

That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml

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

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

Title:
  Desktop freeze

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  The desktop hangs/locks up/freezes randomly during use, the keyboard
  and cursor stop responding as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity:Unity7
  Date: Mon May  8 19:59:24 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0651]
  InstallationDate: Installed on 2017-04-14 (24 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: Dell Inc. Inspiron 3542
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic.efi.signed 
root=UUID=3fd29d97-25ad-421f-aed1-5261567fd0c1 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/27/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 0KHNVP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd05/27/2014:svnDellInc.:pnInspiron3542:pvrNotSpecified:rvnDellInc.:rn0KHNVP:rvrA03:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3542
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.14-0ubuntu1

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

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

[Touch-packages] [Bug 1726124] Re: DNS domain search paths not updated when VPN started

[Launchpad Bug Tracker]

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

** Changed in: network-manager (Ubuntu)
   Status: New => Confirmed

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

Title:
  DNS domain search paths not updated when VPN started

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

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

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

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

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

search home

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

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

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

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

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

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Oct 22 15:08:57 2017
  InstallationDate: Installed on 2017-10-21 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=UUID=4384306c-5fed-4b48-97a6-a6d594c4f72b ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2101
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M5A78L-M/USB3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2101:bd12/02/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-M/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  

[Touch-packages] [Bug 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits

[Eric Desrochers]

profile-14.04-trusty-lp1717714.debdiff

** Patch added: "profile-14.04-trusty-lp1717714.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1717714/+attachment/5047667/+files/profile-14.04-trusty-lp1717714.debdiff

-- 
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:
  Fix Released
Status in apparmor source package in Trusty:
  Fix Committed
Status in apparmor source package in Xenial:
  Fix Committed
Status in apparmor source package in Artful:
  Fix Committed
Status in apparmor source package in Bionic:
  Fix Released
Status in apparmor package in Debian:
  Fix Released

Bug description:
  [Impact]

  If PID is larger than 6 digits apparmor denies process which only
  affect 64-bit systems[1] where the PID_MAX_LIMIT can be generated up
  to 7 digits at the maximum.

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

  [1] - man 5 proc

  --
  /proc/sys/kernel/pid_max (since Linux 2.5.34)
  This file specifies the value at which PIDs wrap around (i.e., the value in 
this file is one greater than the maximum PID).  PIDs greater than this value 
are not allocated;  thus,  the value  in this file also acts as a system-wide 
limit on the total number of processes and threads.  The default value for this 
file, 32768, results in the same range of PIDs as on ear‐lier kernels.  On 
32-bit platforms, 32768 is the maximum value for pid_max.  On 64-bit systems, 
pid_max can be set to any value up to 2^22 (PID_MAX_LIMIT, approximately 4 
million).
  --

  [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

  OR

  instead of Seyeong's touch approach, things can be manually change to
  7 digits range via sysctl as long as the values are below
  approximately 4 millions :

  Example:
  $ sysctl -w kernel.pid_max=300
  $ sysctl -w kernel.ns_last_pid=100

  [Regression]
  * This is a minor/trivial fix which changes the pid regex only, allowing 7 
digits PID instead of only 6 digits PID, we don't think there is any potential 
regression.

  * If a regression arise, which we highly doubt, one can quickly revert
  the change manually and restart the service by modifying
  "/etc/apparmor.d/tunables/kernelvars" file to its original state
  (before this SRU).

  [Others]

  * Upstream commit:
   
https://gitlab.com/apparmor/apparmor/commit/630cb2a981cdc731847e8fdaafc45bcd337fe747
  http://bazaar.launchpad.net/~apparmor-dev/apparmor/master/revision/3722

  * Debian bug:
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886732

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

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

[Touch-packages] [Bug 1659183] Re: English (Canada) input source is missing the left backslash key

[Launchpad Bug Tracker]

This bug was fixed in the package xkeyboard-config - 2.23.1-1ubuntu1

---
xkeyboard-config (2.23.1-1ubuntu1) bionic; urgency=medium

  * Merge with Debian (LP: #1659183, LP: #1685774, LP: #1689110,
LP: #1746544), remaining changes:
- control, rules, xkb-data-i18n.install, xkb-data.install: Split out
  xkb-data-i18n to be used by console-setup.
- xkb-data.postinst: Remove the xkb cache to make sure it gets
  regenerated.
  * Dropped patch, applied upstream:
- d/p/elfdalian-kb-layout.diff

 -- Gunnar Hjalmarsson   Fri, 02 Feb 2018 12:47:00
+0100

** Changed in: xkeyboard-config (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  English (Canada) input source is missing the left backslash key

Status in xkeyboard-config:
  Fix Released
Status in xkeyboard-config package in Ubuntu:
  Fix Released

Bug description:
  In Canada, many keyboards are bilingual and have a slightly different
  layout from US keyboards. They have an additional backslash key next
  to the left shift key.

  In Text Entry, when I select English (Canada) as the input source, the
  layout is wrong. Instead of a backslash, the layout shows a less-than
  symbol, and that is what input when I press the key.

  Attached a screenshot of the incorrect layout.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: ibus 1.5.14-2ubuntu1
  ProcVersionSignature: Ubuntu 4.9.0-12.13-generic 4.9.2
  Uname: Linux 4.9.0-12-generic x86_64
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Jan 24 22:49:41 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-01-22 (3 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20170115)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xkeyboard-config/+bug/1659183/+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 1689110] Re: There are two keyboards for the Hausa language with the same name

[Launchpad Bug Tracker]

This bug was fixed in the package xkeyboard-config - 2.23.1-1ubuntu1

---
xkeyboard-config (2.23.1-1ubuntu1) bionic; urgency=medium

  * Merge with Debian (LP: #1659183, LP: #1685774, LP: #1689110,
LP: #1746544), remaining changes:
- control, rules, xkb-data-i18n.install, xkb-data.install: Split out
  xkb-data-i18n to be used by console-setup.
- xkb-data.postinst: Remove the xkb cache to make sure it gets
  regenerated.
  * Dropped patch, applied upstream:
- d/p/elfdalian-kb-layout.diff

 -- Gunnar Hjalmarsson   Fri, 02 Feb 2018 12:47:00
+0100

** Changed in: xkeyboard-config (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  There are two keyboards for the Hausa language with the same name

Status in xkeyboard-config:
  Fix Released
Status in xkeyboard-config package in Ubuntu:
  Fix Released

Bug description:
  The keyboard selection window has two entries for the Hausa language.

  To reproduce:
  * Click "Text Entry Settings".
  * Click the +
  * Scroll down to H

  There are two entries with the identical name "Hausa". They should
  have different names so that it would be clear what is the difference
  between them.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: unity-control-center 15.04.0+17.04.20170402.6-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Sun May  7 20:01:29 2017
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2015-02-26 (801 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
  SourcePackage: unity-control-center
  UpgradeStatus: Upgraded to zesty on 2017-04-19 (18 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xkeyboard-config/+bug/1689110/+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 1687409] Re: package click 0.4.45.1+16.10.20160916-0ubuntu1 failed to install/upgrade: subproces pre-removal script geïnstalleerd gaf een foutwaarde 1 terug

[dino99]

That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml


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

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

Title:
  package click 0.4.45.1+16.10.20160916-0ubuntu1 failed to
  install/upgrade: subproces pre-removal script geïnstalleerd gaf een
  foutwaarde 1 terug

Status in click package in Ubuntu:
  Invalid

Bug description:
  problems after upgrading from 16.10 to 17.04

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: click 0.4.45.1+16.10.20160916-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-51.54-generic 4.8.17
  Uname: Linux 4.8.0-51-generic i686
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: i386
  Date: Mon May  1 11:03:01 2017
  ErrorMessage: subproces pre-removal script geïnstalleerd gaf een foutwaarde 1 
terug
  InstallationDate: Installed on 2014-03-09 (1148 days ago)
  InstallationMedia: Ubuntu 12.04.4 LTS "Precise Pangolin" - Release i386 
(20140204)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: click
  Title: package click 0.4.45.1+16.10.20160916-0ubuntu1 failed to 
install/upgrade: subproces pre-removal script geïnstalleerd gaf een foutwaarde 
1 terug
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/click/+bug/1687409/+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 1735998] Re: Decouple unity related settings as unity-settings

[Jeremy Bicha]

> Is there any specific reason to carry unity specific gsettings
overrides in ubuntu-settings? Unity is not a default desktop anymore nor
it is installed in the default live iso.

Yes, by centralizing the settings, it makes it easier and faster to
change overrides for multiple flavors. It also allows for easier
comparisons between flavors.

I don't think there's a problem with review of Unity merge proposals for
ubuntu-settings taking too long. Currently, the Unity team doesn't have
any direct upload rights, right? So you'll need review anyway.

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

Title:
  Decouple unity related settings as unity-settings

Status in ubuntu-settings package in Ubuntu:
  Confirmed

Bug description:
  This is an attempt to resolve "* Shared GSettings keys" issue listed
  under https://wiki.ubuntu.com/Unity/NotDefaultIssues.

  Ubuntu so far is providing session related overrides for both ubuntu &
  unity sessions in a single package, i.e. ubuntu-settings. But now that
  Unity is not the default desktop it doesn't make any sense to carry
  unity related overrides in ubuntu-settings.

  For this purpose I have created a new project: unity-settings
  (https://code.launchpad.net/~khurshid-alam/unity-settings/trunk) and
  the binary would be unity-settings in universe.

  To make this happen in under 18.04 cycle, the work-flow should be:

  1) Have unity-settings in the universe
  2) Have ubuntu-unity-desktop in the universe
  3) Let ubuntu-unity-desktop depends on unity-settings
  4) Drop unity related settings in ubuntu-settings (merge request in-progress)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1735998/+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 1747023] [NEW] [P95_HR, Realtek ALC1220, Black Headphone Out, Right] No sound at all

[Casper]

Public bug reported:

External headphones don't work any more. Not sure if realted to the
internal speakers problem: https://bugs.launchpad.net/ubuntu/+source
/alsa-driver/+bug/1721074

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.13.0-31.34~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-31-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0:  cc16   2550 F pulseaudio
 /dev/snd/controlC1:  cc16   2550 F pulseaudio
CurrentDesktop: Unity
Date: Fri Feb  2 14:51:06 2018
InstallationDate: Installed on 2017-08-22 (164 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:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0:  cc16   2550 F pulseaudio
 /dev/snd/controlC1:  cc16   2550 F pulseaudio
Symptom_Jack: Black Headphone Out, Right
Symptom_Type: No sound at all
Title: [P95_HR, Realtek ALC1220, Black Headphone Out, Right] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/29/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.05.02
dmi.board.asset.tag: Tag 12345
dmi.board.name: P95_HR
dmi.board.vendor: CLEVO
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.02:bd06/29/2017:svnPCSpecialistLimited:pnP95_HR:pvrNotApplicable:rvnCLEVO:rnP95_HR:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: P95_HR
dmi.product.version: Not Applicable
dmi.sys.vendor: PC Specialist Limited

** 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/1747023

Title:
  [P95_HR, Realtek ALC1220, Black Headphone Out, Right] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  External headphones don't work any more. Not sure if realted to the
  internal speakers problem: https://bugs.launchpad.net/ubuntu/+source
  /alsa-driver/+bug/1721074

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-31.34~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  AudioDevicesInUse:
   USER PID ACCESS COMMAND
   /dev/snd/controlC0:  cc16   2550 F pulseaudio
   /dev/snd/controlC1:  cc16   2550 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Feb  2 14:51:06 2018
  InstallationDate: Installed on 2017-08-22 (164 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:
   USER PID ACCESS COMMAND
   /dev/snd/controlC0:  cc16   2550 F pulseaudio
   /dev/snd/controlC1:  cc16   2550 F pulseaudio
  Symptom_Jack: Black Headphone Out, Right
  Symptom_Type: No sound at all
  Title: [P95_HR, Realtek ALC1220, Black Headphone Out, Right] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/29/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.02
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: P95_HR
  dmi.board.vendor: CLEVO
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.02:bd06/29/2017:svnPCSpecialistLimited:pnP95_HR:pvrNotApplicable:rvnCLEVO:rnP95_HR:rvrNotApplicable:cvnNotebook:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: P95_HR
  dmi.product.version: Not Applicable
  dmi.sys.vendor: PC Specialist Limited

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1747023/+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 1735998] Re: Decouple unity related settings as unity-settings

[ventrical]

@khurshid

4) The idea is to have a separate ubuntu-unity-amd64.iso. But in the
default iso, both autologin and user-session names set to "ubuntu". If
we want to change that to "unity", we could do that by shipping a
override in "/usr/share/lightdm/lightdm.conf.d/51-autologin.conf".
unity-settings seems proper place to do that. Other option is to carry
similar settings in lightdm.

Khurshid,

I like this idea and I appreciate all the help jbicha is giving you but
with our current manpower resources we may have to settle for a
flattened and leaner unity7. I don't expect you to do all of this work
by yourself. It has been my contention that we try an use any and all of
the gnome components that we can, however, I trust your direction on
this. I will try and recruit more help.

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

Title:
  Decouple unity related settings as unity-settings

Status in ubuntu-settings package in Ubuntu:
  Confirmed

Bug description:
  This is an attempt to resolve "* Shared GSettings keys" issue listed
  under https://wiki.ubuntu.com/Unity/NotDefaultIssues.

  Ubuntu so far is providing session related overrides for both ubuntu &
  unity sessions in a single package, i.e. ubuntu-settings. But now that
  Unity is not the default desktop it doesn't make any sense to carry
  unity related overrides in ubuntu-settings.

  For this purpose I have created a new project: unity-settings
  (https://code.launchpad.net/~khurshid-alam/unity-settings/trunk) and
  the binary would be unity-settings in universe.

  To make this happen in under 18.04 cycle, the work-flow should be:

  1) Have unity-settings in the universe
  2) Have ubuntu-unity-desktop in the universe
  3) Let ubuntu-unity-desktop depends on unity-settings
  4) Drop unity related settings in ubuntu-settings (merge request in-progress)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1735998/+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 1649566] Re: xserver-xorg-video-nouveau: X freeze

[Christopher M. Penalver]

Dieter Maurer:

1) To see if this is already resolved in Ubuntu, could you please test 
http://cdimage.ubuntu.com/daily-live/current/ and advise to the results? If 
still reproducible, please post results following:
https://wiki.ubuntu.com/DebuggingKernelBoot
https://wiki.ubuntu.com/DebuggingSystemCrash

2) To clarify, when you were using 12.04, you didn't have any crashing
whatsoever when using nouveau without any kernel parameters?

3) Does the nvidia driver still not work for you in 16.04?

** Description changed:

- Yesterday, I upgraded from Ubuntu 12.04 via 14.04 to 16.04 (LTS version
- in each case). From 14.04 on, I was unable to graphically log in. A few
- seconds after the login (varying between 1 and 10 s), the screen changed
- to a pattern with dense white stripes on the violet/red background, and
- X froze (no reaction to mouse or keyboard). The latest messages in
- "/var/log/syslog" each time showed varying "nouveau E" problems, e.g.
- "unrecognized interupt", "PFIFO", or "PBUS" problems such as e.g.:
- "nouveau E[PBUS][:00:0d.0] MMIO write of 0x01f70001 FAULT at
- 0x00b010" (values and addresses varying).
+ Yesterday, I upgraded from Ubuntu 12.04 via 14.04 to 16.04. From 14.04
+ on, I was unable to graphically log in. A few seconds after the login
+ (varying between 1 and 10 s), the screen changed to a pattern with dense
+ white stripes on the violet/red background, and X froze (no reaction to
+ mouse or keyboard). The latest messages in "/var/log/syslog" each time
+ showed varying "nouveau E" problems, e.g. "unrecognized interupt",
+ "PFIFO", or "PBUS" problems such as e.g.: "nouveau E[
+ PBUS][:00:0d.0] MMIO write of 0x01f70001 FAULT at 0x00b010" (values
+ and addresses varying).
  
- An internet search revealed that the problem is well known. It affects
- many NVidia graphic cards with the "nouveau" driver. Usually, the freeze
- happens when e.g. "firefox" is started (which happens in my context
- automatically after a graphical login). Most reports recommend to switch
- from "nouveau" to the proprietary NVidia driver. However, there seem to
- be problems with that driver for recent Ubuntu versions. I my case, the
- NVidia driver could not be started (I did not investigate why). One
- report suggested the boot parameter "nouveau.config=NvMSI=0" which in my
- case made the graphical login successful again.
+ Usually, the freeze happens when e.g. "firefox" is started (which
+ happens in my context automatically after a graphical login). In my
+ case, the NVidia driver could not be started (I did not investigate
+ why). Using boot parameter "nouveau.config=NvMSI=0" made the graphical
+ login successful again.
  
- Today, I wanted to report the bug with "ubuntu-bug". However, during the 
collection of the system information, the error happened again (despite the 
"nouveau.config" boot parameter).
+ Today, I wanted to report the bug with "ubuntu-bug". However, during the
+ collection of the system information, the error happened again (despite
+ the "nouveau.config" boot parameter).
+ 
  Syslog gives:
  ...
  Dec 13 11:12:01 localhost CRON[5230]: (root) CMD (   test -x 
/etc/cron.daily/popularity-contest && /etc/cron.daily/popularity-contest 
--crond)
  Dec 13 11:14:16 localhost kernel: [ 6889.138599] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:16 localhost kernel: [ 6889.140532] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:59 localhost dbus[795]: [system] Activating service 
name='com.ubuntu.SoftwareProperties' (using servicehelper)
  Dec 13 11:14:59 localhost dbus[795]: [system] Successfully activated service 
'com.ubuntu.SoftwareProperties'
  Dec 13 11:15:01 localhost CRON[5285]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:17:01 localhost CRON[5303]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)
  Dec 13 11:20:01 localhost CRON[5327]: (smmsp) CMD (test -x 
/etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x 
/usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp)
  Dec 13 11:22:20 localhost kernel: [ 7372.621357] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x FAULT at 0x00b020
  Dec 13 11:25:01 localhost CRON[5580]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:35:01 localhost CRON[5651]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:38:02 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.
  Dec 13 11:39:01 localhost CRON[5723]: (root) CMD (  [ -x 
/usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d 
/var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 
$(/usr/lib/php5/maxlifetime))
  Dec 13 11:39:01 localhost CRON[5722]: (root) CMD (  [ -x 
/usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)
  Dec 13 11:39:46 localhost 

[Touch-packages] [Bug 1685774] Re: Turkish keyboard issues

[Launchpad Bug Tracker]

This bug was fixed in the package xkeyboard-config - 2.23.1-1ubuntu1

---
xkeyboard-config (2.23.1-1ubuntu1) bionic; urgency=medium

  * Merge with Debian (LP: #1659183, LP: #1685774, LP: #1689110,
LP: #1746544), remaining changes:
- control, rules, xkb-data-i18n.install, xkb-data.install: Split out
  xkb-data-i18n to be used by console-setup.
- xkb-data.postinst: Remove the xkb cache to make sure it gets
  regenerated.
  * Dropped patch, applied upstream:
- d/p/elfdalian-kb-layout.diff

 -- Gunnar Hjalmarsson   Fri, 02 Feb 2018 12:47:00
+0100

** Changed in: xkeyboard-config (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Turkish keyboard issues

Status in xkeyboard-config:
  Fix Released
Status in xkeyboard-config package in Ubuntu:
  Fix Released

Bug description:
  There are still some problems with Turkish keyboard in 17.04:

  * The currency is updated as ₺ at 17.04 but there is no way to type it by 
keyboard. By the standard, it should be Alt Gr + T key to type ₺:
  
https://thumb1.shutterstock.com/display_pic_with_logo/3175712/591962180/stock-photo-word-no-meaning-hayir-in-turkish-written-on-a-keyboard-in-a-row-with-red-keys-591962180.jpg

  

  Some keys' behaviors are different from Windows, so for those, it can
  be considered as any update or not, but for any case, I am also
  reporting:

  http://wiki.laptop.org/images/thumb/6/64/TR-MP-Qv1.png/800px-TR-MP-
  Qv1.png

  * For the letter ã, Alt Gr + Ü key should be pressed then a key should be 
pressed.
  * For the letter õ, Alt Gr + Ü key should be pressed then o key should be 
pressed.
  * For the character ~, Alt Gr + Ü should be pressed then space key should be 
pressed.
  * For the letter æ, Alt Gr + A should be pressed 
  * For the letter â, Shift + 3 then a should be pressed.
  * For the letter û, Shift + 3 then u should be pressed.
  * For the letter ô, Shift + 3 then o should be pressed.
  * For the letter î, Shift + 3 then ı or i should be pressed.
  * For the letter ê, Shift + 3 then e should be pressed.
  * For the character ^, Shift + 3 then space should be presssed.
  * For the letter é, Alt Gr + ş then e should be pressed.
  * For the letter á, Alt Gr + ş then a should be pressed.
  * For the letter ú, Alt Gr + ş then u should be pressed.
  * For the letter ó, Alt Gr + ş then o should be pressed.
  * For the letter í, Alt Gr + ş then ı or i should be pressed.
  * For the character ´, Alt Gr + ş then space should be pressed.
  * For the letter ò, Alt Gr + , then o should be pressed.
  * For the letter ù, Alt Gr + , then u should be pressed.
  * For the letter à, Alt Gr + , then a should be pressed.
  * For the character `, Alt Gr + , then space should be pressed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xkeyboard-config/+bug/1685774/+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 1649566] ProcCpuinfoMinimal.txt

[Dieter Maurer]

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1649566/+attachment/5047622/+files/ProcCpuinfoMinimal.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/1649566

Title:
  xserver-xorg-video-nouveau: X freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Yesterday, I upgraded from Ubuntu 12.04 via 14.04 to 16.04 (LTS
  version in each case). From 14.04 on, I was unable to graphically log
  in. A few seconds after the login (varying between 1 and 10 s), the
  screen changed to a pattern with dense white stripes on the violet/red
  background, and X froze (no reaction to mouse or keyboard). The latest
  messages in "/var/log/syslog" each time showed varying "nouveau E"
  problems, e.g. "unrecognized interupt", "PFIFO", or "PBUS" problems
  such as e.g.: "nouveau E[PBUS][:00:0d.0] MMIO write of
  0x01f70001 FAULT at 0x00b010" (values and addresses varying).

  An internet search revealed that the problem is well known. It affects
  many NVidia graphic cards with the "nouveau" driver. Usually, the
  freeze happens when e.g. "firefox" is started (which happens in my
  context automatically after a graphical login). Most reports recommend
  to switch from "nouveau" to the proprietary NVidia driver. However,
  there seem to be problems with that driver for recent Ubuntu versions.
  I my case, the NVidia driver could not be started (I did not
  investigate why). One report suggested the boot parameter
  "nouveau.config=NvMSI=0" which in my case made the graphical login
  successful again.

  Today, I wanted to report the bug with "ubuntu-bug". However, during the 
collection of the system information, the error happened again (despite the 
"nouveau.config" boot parameter).
  Syslog gives:
  ...
  Dec 13 11:12:01 localhost CRON[5230]: (root) CMD (   test -x 
/etc/cron.daily/popularity-contest && /etc/cron.daily/popularity-contest 
--crond)
  Dec 13 11:14:16 localhost kernel: [ 6889.138599] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:16 localhost kernel: [ 6889.140532] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:59 localhost dbus[795]: [system] Activating service 
name='com.ubuntu.SoftwareProperties' (using servicehelper)
  Dec 13 11:14:59 localhost dbus[795]: [system] Successfully activated service 
'com.ubuntu.SoftwareProperties'
  Dec 13 11:15:01 localhost CRON[5285]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:17:01 localhost CRON[5303]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)
  Dec 13 11:20:01 localhost CRON[5327]: (smmsp) CMD (test -x 
/etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x 
/usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp)
  Dec 13 11:22:20 localhost kernel: [ 7372.621357] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x FAULT at 0x00b020
  Dec 13 11:25:01 localhost CRON[5580]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:35:01 localhost CRON[5651]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:38:02 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.
  Dec 13 11:39:01 localhost CRON[5723]: (root) CMD (  [ -x 
/usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d 
/var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 
$(/usr/lib/php5/maxlifetime))
  Dec 13 11:39:01 localhost CRON[5722]: (root) CMD (  [ -x 
/usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)
  Dec 13 11:39:46 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.

  At this point, I had to reset the computer.

  
  Detailed system information:
  lsdm: lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  xserver-xorg-video-nouveau 1:1.0.12-1build2

  root@lsdm:~# lspci
  00:00.0 RAM memory: NVIDIA Corporation MCP61 Host Bridge (rev a1)
  00:01.0 ISA bridge: NVIDIA Corporation MCP61 LPC Bridge (rev a2)
  00:01.1 SMBus: NVIDIA Corporation MCP61 SMBus (rev a2)
  00:01.2 RAM memory: NVIDIA Corporation MCP61 Memory Controller (rev a2)
  00:02.0 USB controller: NVIDIA Corporation MCP61 USB 1.1 Controller (rev a3)
  00:02.1 USB controller: NVIDIA Corporation MCP61 USB 2.0 Controller (rev a3)
  00:04.0 PCI bridge: NVIDIA Corporation MCP61 PCI bridge (rev a1)
  00:05.0 Audio device: NVIDIA Corporation MCP61 High Definition Audio (rev a2)
  00:06.0 IDE interface: NVIDIA Corporation MCP61 IDE (rev a2)
  00:07.0 Bridge: NVIDIA Corporation MCP61 Ethernet (rev a2)
  00:08.0 IDE interface: NVIDIA Corporation MCP61 SATA Controller (rev a2)
  00:08.1 IDE interface: NVIDIA Corporation MCP61 SATA Controller (rev a2)
  

[Touch-packages] [Bug 1649566] GconfCompiz.txt

[Dieter Maurer]

apport information

** Attachment added: "GconfCompiz.txt"
   
https://bugs.launchpad.net/bugs/1649566/+attachment/5047618/+files/GconfCompiz.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/1649566

Title:
  xserver-xorg-video-nouveau: X freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Yesterday, I upgraded from Ubuntu 12.04 via 14.04 to 16.04 (LTS
  version in each case). From 14.04 on, I was unable to graphically log
  in. A few seconds after the login (varying between 1 and 10 s), the
  screen changed to a pattern with dense white stripes on the violet/red
  background, and X froze (no reaction to mouse or keyboard). The latest
  messages in "/var/log/syslog" each time showed varying "nouveau E"
  problems, e.g. "unrecognized interupt", "PFIFO", or "PBUS" problems
  such as e.g.: "nouveau E[PBUS][:00:0d.0] MMIO write of
  0x01f70001 FAULT at 0x00b010" (values and addresses varying).

  An internet search revealed that the problem is well known. It affects
  many NVidia graphic cards with the "nouveau" driver. Usually, the
  freeze happens when e.g. "firefox" is started (which happens in my
  context automatically after a graphical login). Most reports recommend
  to switch from "nouveau" to the proprietary NVidia driver. However,
  there seem to be problems with that driver for recent Ubuntu versions.
  I my case, the NVidia driver could not be started (I did not
  investigate why). One report suggested the boot parameter
  "nouveau.config=NvMSI=0" which in my case made the graphical login
  successful again.

  Today, I wanted to report the bug with "ubuntu-bug". However, during the 
collection of the system information, the error happened again (despite the 
"nouveau.config" boot parameter).
  Syslog gives:
  ...
  Dec 13 11:12:01 localhost CRON[5230]: (root) CMD (   test -x 
/etc/cron.daily/popularity-contest && /etc/cron.daily/popularity-contest 
--crond)
  Dec 13 11:14:16 localhost kernel: [ 6889.138599] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:16 localhost kernel: [ 6889.140532] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:59 localhost dbus[795]: [system] Activating service 
name='com.ubuntu.SoftwareProperties' (using servicehelper)
  Dec 13 11:14:59 localhost dbus[795]: [system] Successfully activated service 
'com.ubuntu.SoftwareProperties'
  Dec 13 11:15:01 localhost CRON[5285]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:17:01 localhost CRON[5303]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)
  Dec 13 11:20:01 localhost CRON[5327]: (smmsp) CMD (test -x 
/etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x 
/usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp)
  Dec 13 11:22:20 localhost kernel: [ 7372.621357] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x FAULT at 0x00b020
  Dec 13 11:25:01 localhost CRON[5580]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:35:01 localhost CRON[5651]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:38:02 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.
  Dec 13 11:39:01 localhost CRON[5723]: (root) CMD (  [ -x 
/usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d 
/var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 
$(/usr/lib/php5/maxlifetime))
  Dec 13 11:39:01 localhost CRON[5722]: (root) CMD (  [ -x 
/usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)
  Dec 13 11:39:46 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.

  At this point, I had to reset the computer.

  
  Detailed system information:
  lsdm: lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  xserver-xorg-video-nouveau 1:1.0.12-1build2

  root@lsdm:~# lspci
  00:00.0 RAM memory: NVIDIA Corporation MCP61 Host Bridge (rev a1)
  00:01.0 ISA bridge: NVIDIA Corporation MCP61 LPC Bridge (rev a2)
  00:01.1 SMBus: NVIDIA Corporation MCP61 SMBus (rev a2)
  00:01.2 RAM memory: NVIDIA Corporation MCP61 Memory Controller (rev a2)
  00:02.0 USB controller: NVIDIA Corporation MCP61 USB 1.1 Controller (rev a3)
  00:02.1 USB controller: NVIDIA Corporation MCP61 USB 2.0 Controller (rev a3)
  00:04.0 PCI bridge: NVIDIA Corporation MCP61 PCI bridge (rev a1)
  00:05.0 Audio device: NVIDIA Corporation MCP61 High Definition Audio (rev a2)
  00:06.0 IDE interface: NVIDIA Corporation MCP61 IDE (rev a2)
  00:07.0 Bridge: NVIDIA Corporation MCP61 Ethernet (rev a2)
  00:08.0 IDE interface: NVIDIA Corporation MCP61 SATA Controller (rev a2)
  00:08.1 IDE interface: NVIDIA Corporation MCP61 SATA Controller (rev a2)
  00:09.0 PCI 

[Touch-packages] [Bug 1746765] Re: systemd FTBFS on arm64

[Julian Andres Klode]

It also FTBFS with the current gnu-efi, so my suggestion is to just
disable the EFI integration on arm64.

** Changed in: gnu-efi (Ubuntu Bionic)
   Status: New => Invalid

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

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

Title:
  systemd FTBFS on arm64

Status in binutils:
  Confirmed
Status in binutils package in Ubuntu:
  New
Status in gnu-efi package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Confirmed
Status in binutils source package in Bionic:
  New
Status in gnu-efi source package in Bionic:
  New
Status in systemd source package in Bionic:
  Confirmed

Bug description:
  Might be a bug in the toolchain, gnu-efi or systemd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/binutils/+bug/1746765/+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 1649566] XorgLog.txt

[Dieter Maurer]

apport information

** Attachment added: "XorgLog.txt"
   
https://bugs.launchpad.net/bugs/1649566/+attachment/5047626/+files/XorgLog.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/1649566

Title:
  xserver-xorg-video-nouveau: X freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Yesterday, I upgraded from Ubuntu 12.04 via 14.04 to 16.04 (LTS
  version in each case). From 14.04 on, I was unable to graphically log
  in. A few seconds after the login (varying between 1 and 10 s), the
  screen changed to a pattern with dense white stripes on the violet/red
  background, and X froze (no reaction to mouse or keyboard). The latest
  messages in "/var/log/syslog" each time showed varying "nouveau E"
  problems, e.g. "unrecognized interupt", "PFIFO", or "PBUS" problems
  such as e.g.: "nouveau E[PBUS][:00:0d.0] MMIO write of
  0x01f70001 FAULT at 0x00b010" (values and addresses varying).

  An internet search revealed that the problem is well known. It affects
  many NVidia graphic cards with the "nouveau" driver. Usually, the
  freeze happens when e.g. "firefox" is started (which happens in my
  context automatically after a graphical login). Most reports recommend
  to switch from "nouveau" to the proprietary NVidia driver. However,
  there seem to be problems with that driver for recent Ubuntu versions.
  I my case, the NVidia driver could not be started (I did not
  investigate why). One report suggested the boot parameter
  "nouveau.config=NvMSI=0" which in my case made the graphical login
  successful again.

  Today, I wanted to report the bug with "ubuntu-bug". However, during the 
collection of the system information, the error happened again (despite the 
"nouveau.config" boot parameter).
  Syslog gives:
  ...
  Dec 13 11:12:01 localhost CRON[5230]: (root) CMD (   test -x 
/etc/cron.daily/popularity-contest && /etc/cron.daily/popularity-contest 
--crond)
  Dec 13 11:14:16 localhost kernel: [ 6889.138599] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:16 localhost kernel: [ 6889.140532] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:59 localhost dbus[795]: [system] Activating service 
name='com.ubuntu.SoftwareProperties' (using servicehelper)
  Dec 13 11:14:59 localhost dbus[795]: [system] Successfully activated service 
'com.ubuntu.SoftwareProperties'
  Dec 13 11:15:01 localhost CRON[5285]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:17:01 localhost CRON[5303]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)
  Dec 13 11:20:01 localhost CRON[5327]: (smmsp) CMD (test -x 
/etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x 
/usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp)
  Dec 13 11:22:20 localhost kernel: [ 7372.621357] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x FAULT at 0x00b020
  Dec 13 11:25:01 localhost CRON[5580]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:35:01 localhost CRON[5651]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:38:02 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.
  Dec 13 11:39:01 localhost CRON[5723]: (root) CMD (  [ -x 
/usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d 
/var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 
$(/usr/lib/php5/maxlifetime))
  Dec 13 11:39:01 localhost CRON[5722]: (root) CMD (  [ -x 
/usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)
  Dec 13 11:39:46 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.

  At this point, I had to reset the computer.

  
  Detailed system information:
  lsdm: lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  xserver-xorg-video-nouveau 1:1.0.12-1build2

  root@lsdm:~# lspci
  00:00.0 RAM memory: NVIDIA Corporation MCP61 Host Bridge (rev a1)
  00:01.0 ISA bridge: NVIDIA Corporation MCP61 LPC Bridge (rev a2)
  00:01.1 SMBus: NVIDIA Corporation MCP61 SMBus (rev a2)
  00:01.2 RAM memory: NVIDIA Corporation MCP61 Memory Controller (rev a2)
  00:02.0 USB controller: NVIDIA Corporation MCP61 USB 1.1 Controller (rev a3)
  00:02.1 USB controller: NVIDIA Corporation MCP61 USB 2.0 Controller (rev a3)
  00:04.0 PCI bridge: NVIDIA Corporation MCP61 PCI bridge (rev a1)
  00:05.0 Audio device: NVIDIA Corporation MCP61 High Definition Audio (rev a2)
  00:06.0 IDE interface: NVIDIA Corporation MCP61 IDE (rev a2)
  00:07.0 Bridge: NVIDIA Corporation MCP61 Ethernet (rev a2)
  00:08.0 IDE interface: NVIDIA Corporation MCP61 SATA Controller (rev a2)
  00:08.1 IDE interface: NVIDIA Corporation MCP61 SATA Controller (rev a2)
  00:09.0 PCI bridge: 

[Touch-packages] [Bug 1649566] Re: xserver-xorg-video-nouveau: X freeze

[Dieter Maurer]

apport information

** Tags added: apport-collected ubuntu xenial

** Description changed:

  Yesterday, I upgraded from Ubuntu 12.04 via 14.04 to 16.04 (LTS version
  in each case). From 14.04 on, I was unable to graphically log in. A few
  seconds after the login (varying between 1 and 10 s), the screen changed
  to a pattern with dense white stripes on the violet/red background, and
  X froze (no reaction to mouse or keyboard). The latest messages in
  "/var/log/syslog" each time showed varying "nouveau E" problems, e.g.
  "unrecognized interupt", "PFIFO", or "PBUS" problems such as e.g.:
  "nouveau E[PBUS][:00:0d.0] MMIO write of 0x01f70001 FAULT at
  0x00b010" (values and addresses varying).
  
  An internet search revealed that the problem is well known. It affects
  many NVidia graphic cards with the "nouveau" driver. Usually, the freeze
  happens when e.g. "firefox" is started (which happens in my context
  automatically after a graphical login). Most reports recommend to switch
  from "nouveau" to the proprietary NVidia driver. However, there seem to
  be problems with that driver for recent Ubuntu versions. I my case, the
  NVidia driver could not be started (I did not investigate why). One
  report suggested the boot parameter "nouveau.config=NvMSI=0" which in my
  case made the graphical login successful again.
  
  Today, I wanted to report the bug with "ubuntu-bug". However, during the 
collection of the system information, the error happened again (despite the 
"nouveau.config" boot parameter).
  Syslog gives:
  ...
  Dec 13 11:12:01 localhost CRON[5230]: (root) CMD (   test -x 
/etc/cron.daily/popularity-contest && /etc/cron.daily/popularity-contest 
--crond)
  Dec 13 11:14:16 localhost kernel: [ 6889.138599] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:16 localhost kernel: [ 6889.140532] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:59 localhost dbus[795]: [system] Activating service 
name='com.ubuntu.SoftwareProperties' (using servicehelper)
  Dec 13 11:14:59 localhost dbus[795]: [system] Successfully activated service 
'com.ubuntu.SoftwareProperties'
  Dec 13 11:15:01 localhost CRON[5285]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:17:01 localhost CRON[5303]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)
  Dec 13 11:20:01 localhost CRON[5327]: (smmsp) CMD (test -x 
/etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x 
/usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp)
  Dec 13 11:22:20 localhost kernel: [ 7372.621357] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x FAULT at 0x00b020
  Dec 13 11:25:01 localhost CRON[5580]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:35:01 localhost CRON[5651]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:38:02 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.
  Dec 13 11:39:01 localhost CRON[5723]: (root) CMD (  [ -x 
/usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d 
/var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 
$(/usr/lib/php5/maxlifetime))
  Dec 13 11:39:01 localhost CRON[5722]: (root) CMD (  [ -x 
/usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)
  Dec 13 11:39:46 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.
  
  At this point, I had to reset the computer.
  
  
  Detailed system information:
  lsdm: lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04
  
  xserver-xorg-video-nouveau 1:1.0.12-1build2
  
  root@lsdm:~# lspci
  00:00.0 RAM memory: NVIDIA Corporation MCP61 Host Bridge (rev a1)
  00:01.0 ISA bridge: NVIDIA Corporation MCP61 LPC Bridge (rev a2)
  00:01.1 SMBus: NVIDIA Corporation MCP61 SMBus (rev a2)
  00:01.2 RAM memory: NVIDIA Corporation MCP61 Memory Controller (rev a2)
  00:02.0 USB controller: NVIDIA Corporation MCP61 USB 1.1 Controller (rev a3)
  00:02.1 USB controller: NVIDIA Corporation MCP61 USB 2.0 Controller (rev a3)
  00:04.0 PCI bridge: NVIDIA Corporation MCP61 PCI bridge (rev a1)
  00:05.0 Audio device: NVIDIA Corporation MCP61 High Definition Audio (rev a2)
  00:06.0 IDE interface: NVIDIA Corporation MCP61 IDE (rev a2)
  00:07.0 Bridge: NVIDIA Corporation MCP61 Ethernet (rev a2)
  00:08.0 IDE interface: NVIDIA Corporation MCP61 SATA Controller (rev a2)
  00:08.1 IDE interface: NVIDIA Corporation MCP61 SATA Controller (rev a2)
  00:09.0 PCI bridge: NVIDIA Corporation MCP61 PCI Express bridge (rev a2)
  00:0b.0 PCI bridge: NVIDIA Corporation MCP61 PCI Express bridge (rev a2)
  00:0c.0 PCI bridge: NVIDIA Corporation MCP61 PCI Express bridge (rev a2)
  00:0d.0 VGA compatible controller: NVIDIA Corporation C61 [GeForce 7025 / 
nForce 630a] (rev a2)
  00:18.0 Host bridge: 

[Touch-packages] [Bug 1649566] Re: xserver-xorg-video-nouveau: X freeze

[Dieter Maurer]

In comment #6 I had reported that "apport-collect 1649566" reproduces
the freeze.

I was now able to successfully transfer the data by calling "apport-
collect" outside the X system. Because, it did not run under X, it might
not contail all information you would like. In this case, let me know
how to obtain the missing information.

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

Title:
  xserver-xorg-video-nouveau: X freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Yesterday, I upgraded from Ubuntu 12.04 via 14.04 to 16.04 (LTS
  version in each case). From 14.04 on, I was unable to graphically log
  in. A few seconds after the login (varying between 1 and 10 s), the
  screen changed to a pattern with dense white stripes on the violet/red
  background, and X froze (no reaction to mouse or keyboard). The latest
  messages in "/var/log/syslog" each time showed varying "nouveau E"
  problems, e.g. "unrecognized interupt", "PFIFO", or "PBUS" problems
  such as e.g.: "nouveau E[PBUS][:00:0d.0] MMIO write of
  0x01f70001 FAULT at 0x00b010" (values and addresses varying).

  An internet search revealed that the problem is well known. It affects
  many NVidia graphic cards with the "nouveau" driver. Usually, the
  freeze happens when e.g. "firefox" is started (which happens in my
  context automatically after a graphical login). Most reports recommend
  to switch from "nouveau" to the proprietary NVidia driver. However,
  there seem to be problems with that driver for recent Ubuntu versions.
  I my case, the NVidia driver could not be started (I did not
  investigate why). One report suggested the boot parameter
  "nouveau.config=NvMSI=0" which in my case made the graphical login
  successful again.

  Today, I wanted to report the bug with "ubuntu-bug". However, during the 
collection of the system information, the error happened again (despite the 
"nouveau.config" boot parameter).
  Syslog gives:
  ...
  Dec 13 11:12:01 localhost CRON[5230]: (root) CMD (   test -x 
/etc/cron.daily/popularity-contest && /etc/cron.daily/popularity-contest 
--crond)
  Dec 13 11:14:16 localhost kernel: [ 6889.138599] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:16 localhost kernel: [ 6889.140532] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:59 localhost dbus[795]: [system] Activating service 
name='com.ubuntu.SoftwareProperties' (using servicehelper)
  Dec 13 11:14:59 localhost dbus[795]: [system] Successfully activated service 
'com.ubuntu.SoftwareProperties'
  Dec 13 11:15:01 localhost CRON[5285]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:17:01 localhost CRON[5303]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)
  Dec 13 11:20:01 localhost CRON[5327]: (smmsp) CMD (test -x 
/etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x 
/usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp)
  Dec 13 11:22:20 localhost kernel: [ 7372.621357] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x FAULT at 0x00b020
  Dec 13 11:25:01 localhost CRON[5580]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:35:01 localhost CRON[5651]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:38:02 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.
  Dec 13 11:39:01 localhost CRON[5723]: (root) CMD (  [ -x 
/usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d 
/var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 
$(/usr/lib/php5/maxlifetime))
  Dec 13 11:39:01 localhost CRON[5722]: (root) CMD (  [ -x 
/usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)
  Dec 13 11:39:46 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.

  At this point, I had to reset the computer.

  
  Detailed system information:
  lsdm: lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  xserver-xorg-video-nouveau 1:1.0.12-1build2

  root@lsdm:~# lspci
  00:00.0 RAM memory: NVIDIA Corporation MCP61 Host Bridge (rev a1)
  00:01.0 ISA bridge: NVIDIA Corporation MCP61 LPC Bridge (rev a2)
  00:01.1 SMBus: NVIDIA Corporation MCP61 SMBus (rev a2)
  00:01.2 RAM memory: NVIDIA Corporation MCP61 Memory Controller (rev a2)
  00:02.0 USB controller: NVIDIA Corporation MCP61 USB 1.1 Controller (rev a3)
  00:02.1 USB controller: NVIDIA Corporation MCP61 USB 2.0 Controller (rev a3)
  00:04.0 PCI bridge: NVIDIA Corporation MCP61 PCI bridge (rev a1)
  00:05.0 Audio device: NVIDIA Corporation MCP61 High Definition Audio (rev a2)
  00:06.0 IDE interface: NVIDIA Corporation MCP61 IDE (rev a2)
  00:07.0 Bridge: NVIDIA Corporation MCP61 

[Touch-packages] [Bug 1687535] Re: PCI/internal sound card not detected

[dino99]

That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml


** 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/1687535

Title:
  PCI/internal sound card not detected

Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  Problem: My audio is not working. I'm getting that "Dummy Output" in
  the sound settings. I've been scouring the web, but nothing I try is
  working. I've tried

  sudo alsa force-reload

  sudo apt-get remove --purge alsa-utils

  sudo apt-get install alsa-utils

  I've tried about every single little thing, and it's driving me crazy.

  Ubuntu dist: Saucy Salamander (13.10, running GNOME-3 Desktop) Results of 
lspci:00:00.0 Host bridge: Intel Corporation 3rd Gen Core processor DRAM 
Controller (rev 09)
  00:02.0 VGA compatible controller: Intel Corporation 3rd Gen Core processor 
Graphics Controller (rev 09)
  00:14.0 USB controller: Intel Corporation 7 Series/C210 Series Chipset Family 
USB xHCI Host Controller (rev 04)
  00:16.0 Communication controller: Intel Corporation 7 Series/C216 Chipset 
Family MEI Controller #1 (rev 04)
  00:1a.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB 
Enhanced Host Controller #2 (rev 04)
  00:1b.0 Audio device: Intel Corporation 7 Series/C216 Chipset Family High 
Definition Audio Controller (rev 04)
  00:1c.0 PCI bridge: Intel Corporation 7 Series/C216 Chipset Family PCI 
Express Root Port 1 (rev c4)
  00:1c.1 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI 
Express Root Port 2 (rev c4)
  00:1c.2 PCI bridge: Intel Corporation 7 Series/C210 Series Chipset Family PCI 
Express Root Port 3 (rev c4)
  00:1c.3 PCI bridge: Intel Corporation 7 Series/C216 Chipset Family PCI 
Express Root Port 4 (rev c4)
  00:1d.0 USB controller: Intel Corporation 7 Series/C216 Chipset Family USB 
Enhanced Host Controller #1 (rev 04)
  00:1f.0 ISA bridge: Intel Corporation 7 Series Chipset Family LPC Controller 
(rev 04)
  00:1f.2 SATA controller: Intel Corporation 7 Series Chipset Family 6-port 
SATA Controller [AHCI mode] (rev 04)
  00:1f.3 SMBus: Intel Corporation 7 Series/C216 Chipset Family SMBus 
Controller (rev 04)
  00:1f.6 Signal processing controller: Intel Corporation 7 Series/C210 Series 
Chipset Family Thermal Management Controller (rev 04)
  01:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8188EE 
Wireless Network Adapter (rev 01)
  02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTL8411B PCI 
Express Card Reader (rev 01)
  02:00.1 Ethernet controller: Realtek Semiconductor Co., Ltd. 
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 12)
  (wasn't quite sure how much you guys needed) 
  For some reason, I don't have a .asoundrc file or /etc/asoundrc.conf file. I 
can't get into alsamixer either. I've uninstalled, reinstalled, uninstalled, 
and reinstalled alsa-base, alsa-utils, pulseaudio, and even Wine.
  I don't know what else to do at this point. Can you guys help me?

  EDIT: sudo alsa force-reload returns

   Unloading ALSA sound driver modules: (none loaded).
  Loading ALSA sound driver modules: (none to reload).
  Do I have to reinstall Ubuntu?

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic i686
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity:Unity7
  Date: Tue May  2 10:00:25 2017
  InstallationDate: Installed on 2016-10-20 (193 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: Upgraded to zesty on 2017-04-20 (11 days ago)
  dmi.bios.date: 07/06/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.03
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Gateway NE46Rs1
  dmi.board.vendor: Acer
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.03:bd07/06/2015:svnAcer:pnGatewayNE46Rs1:pvrTobefilledbyO.E.M.:rvnAcer:rnGatewayNE46Rs1:rvrTobefilledbyO.E.M.:cvnAcer:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: Gateway NE46Rs1
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Acer

To manage 

[Touch-packages] [Bug 1649566] ProcModules.txt

[Dieter Maurer]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1649566/+attachment/5047624/+files/ProcModules.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/1649566

Title:
  xserver-xorg-video-nouveau: X freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Yesterday, I upgraded from Ubuntu 12.04 via 14.04 to 16.04 (LTS
  version in each case). From 14.04 on, I was unable to graphically log
  in. A few seconds after the login (varying between 1 and 10 s), the
  screen changed to a pattern with dense white stripes on the violet/red
  background, and X froze (no reaction to mouse or keyboard). The latest
  messages in "/var/log/syslog" each time showed varying "nouveau E"
  problems, e.g. "unrecognized interupt", "PFIFO", or "PBUS" problems
  such as e.g.: "nouveau E[PBUS][:00:0d.0] MMIO write of
  0x01f70001 FAULT at 0x00b010" (values and addresses varying).

  An internet search revealed that the problem is well known. It affects
  many NVidia graphic cards with the "nouveau" driver. Usually, the
  freeze happens when e.g. "firefox" is started (which happens in my
  context automatically after a graphical login). Most reports recommend
  to switch from "nouveau" to the proprietary NVidia driver. However,
  there seem to be problems with that driver for recent Ubuntu versions.
  I my case, the NVidia driver could not be started (I did not
  investigate why). One report suggested the boot parameter
  "nouveau.config=NvMSI=0" which in my case made the graphical login
  successful again.

  Today, I wanted to report the bug with "ubuntu-bug". However, during the 
collection of the system information, the error happened again (despite the 
"nouveau.config" boot parameter).
  Syslog gives:
  ...
  Dec 13 11:12:01 localhost CRON[5230]: (root) CMD (   test -x 
/etc/cron.daily/popularity-contest && /etc/cron.daily/popularity-contest 
--crond)
  Dec 13 11:14:16 localhost kernel: [ 6889.138599] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:16 localhost kernel: [ 6889.140532] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:59 localhost dbus[795]: [system] Activating service 
name='com.ubuntu.SoftwareProperties' (using servicehelper)
  Dec 13 11:14:59 localhost dbus[795]: [system] Successfully activated service 
'com.ubuntu.SoftwareProperties'
  Dec 13 11:15:01 localhost CRON[5285]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:17:01 localhost CRON[5303]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)
  Dec 13 11:20:01 localhost CRON[5327]: (smmsp) CMD (test -x 
/etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x 
/usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp)
  Dec 13 11:22:20 localhost kernel: [ 7372.621357] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x FAULT at 0x00b020
  Dec 13 11:25:01 localhost CRON[5580]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:35:01 localhost CRON[5651]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:38:02 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.
  Dec 13 11:39:01 localhost CRON[5723]: (root) CMD (  [ -x 
/usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d 
/var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 
$(/usr/lib/php5/maxlifetime))
  Dec 13 11:39:01 localhost CRON[5722]: (root) CMD (  [ -x 
/usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)
  Dec 13 11:39:46 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.

  At this point, I had to reset the computer.

  
  Detailed system information:
  lsdm: lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  xserver-xorg-video-nouveau 1:1.0.12-1build2

  root@lsdm:~# lspci
  00:00.0 RAM memory: NVIDIA Corporation MCP61 Host Bridge (rev a1)
  00:01.0 ISA bridge: NVIDIA Corporation MCP61 LPC Bridge (rev a2)
  00:01.1 SMBus: NVIDIA Corporation MCP61 SMBus (rev a2)
  00:01.2 RAM memory: NVIDIA Corporation MCP61 Memory Controller (rev a2)
  00:02.0 USB controller: NVIDIA Corporation MCP61 USB 1.1 Controller (rev a3)
  00:02.1 USB controller: NVIDIA Corporation MCP61 USB 2.0 Controller (rev a3)
  00:04.0 PCI bridge: NVIDIA Corporation MCP61 PCI bridge (rev a1)
  00:05.0 Audio device: NVIDIA Corporation MCP61 High Definition Audio (rev a2)
  00:06.0 IDE interface: NVIDIA Corporation MCP61 IDE (rev a2)
  00:07.0 Bridge: NVIDIA Corporation MCP61 Ethernet (rev a2)
  00:08.0 IDE interface: NVIDIA Corporation MCP61 SATA Controller (rev a2)
  00:08.1 IDE interface: NVIDIA Corporation MCP61 SATA Controller (rev a2)
  00:09.0 PCI 

[Touch-packages] [Bug 1688747] Re: frequent unabity to connect to websites, frequent connection problem.

[dino99]

That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml

** Changed in: network-manager (Ubuntu)
   Status: New => Invalid

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

Title:
  frequent unabity to connect to websites, frequent connection problem.

Status in network-manager package in Ubuntu:
  Invalid

Bug description:
   Cabled conection to ADSL. frequently unable to connect to websites,
  restarting network manager resolves problem temporarily. Seems to be
  no problem when connected to VPN. After diconecting VPN connection,
  not able to connect to internet. Restart connection or network manager
  needed.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: network-manager 1.4.4-1ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: Unity:Unity7
  Date: Sat May  6 16:53:50 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-01-21 (105 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  IpRoute:
   default via 192.168.1.1 dev enp4s1 proto static metric 100 
   169.254.0.0/16 dev enp4s1 scope link metric 1000 
   192.168.1.0/24 dev enp4s1 proto kernel scope link src 192.168.1.3 metric 100
  IwConfig:
   lono wireless extensions.
   
   enp4s1no wireless extensions.
  NetworkManager.conf:
   [main]
   plugins=ifupdown,keyfile
   
   [ifupdown]
   managed=false
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to zesty on 2017-04-15 (21 days ago)
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   enp4s1  ethernet  connected  /org/freedesktop/NetworkManager/Devices/1  
Connessione via cavo 1  e6fa8c59-3af2-3ef5-9425-38f3b0ed6c60  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/0  --   
   ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.4.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/1688747/+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 1617905] Re: adb backup only creates 2GB file then hangs

[Tharrrk]

@Tom can you confirm no other version of adb is installed?
You might need to uninstall adb (different package providing the same binary) 
package and/or system-wide version of android-tools-adb prior to running dpkg -i

$ which adb
$ readlink -f `which adb`

$ dpkg -l \*adb
$ apt-cache policy android-tools-adb
$ dpkg -L android-tools-adb

What OS version, arch and kernel are you using?

$ lsb_release -rd || cat /etc/*release
$ arch
$ uname -ovr

What filesystem are you backing up to?

It certainly works here and this is the way to confirm adb is using
open64 calls:

# readelf -a `which adb`|grep open
08073040  0e07 R_386_JUMP_SLOT      open64@GLIBC_2.1
08073090  2407 R_386_JUMP_SLOT      fopen64@GLIBC_2.1
08073114  4707 R_386_JUMP_SLOT      opendir@GLIBC_2.0
0807319c  6907 R_386_JUMP_SLOT      __open64_2@GLIBC_2.7
14:  0 FUNCGLOBAL DEFAULT  UND open64@GLIBC_2.1 (3)
36:  0 FUNCGLOBAL DEFAULT  UND fopen64@GLIBC_2.1 (3)
71:  0 FUNCGLOBAL DEFAULT  UND opendir@GLIBC_2.0 (2)
   105:  0 FUNCGLOBAL DEFAULT  UND __open64_2@GLIBC_2.7 (7)

Hope it helps.
Tharrrk

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

Title:
  adb backup only creates 2GB file then hangs

Status in android-tools package in Ubuntu:
  New

Bug description:
  $ lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  $ arch
  i686

  $ apt-cache policy android-tools-adb
  android-tools-adb:
    Installed: 5.1.1r36+git20160322-0ubuntu3tharrrk1
    Candidate: 5.1.1r36+git20160322-0ubuntu3tharrrk1
    Version table:
   *** 5.1.1r36+git20160322-0ubuntu3tharrrk1 100
  100 /var/lib/dpkg/status
   5.1.1r36+git20160322-0ubuntu3 500
  500 http://mt.archive.ubuntu.com/ubuntu xenial/universe i386 Packages

  BUG DESCRIPTION:
  
  At least on i386 the files created by adb backup are limited to 2GB.
  It seems adb is not built with -D_FILE_OFFSET_BITS=64.
  This is basically a duplicate of bug in Debian # 700461 
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=700461) originally reported 
in ___2013___

  FIX:
  
  update makefile:

  $ diff -Nurp android-tools-5.1.1r36+git20160322.orig 
android-tools-5.1.1r36+git20160322
  diff -Nurp android-tools-5.1.1r36+git20160322.orig/debian/makefiles/adb.mk 
android-tools-5.1.1r36+git20160322/debian/makefiles/adb.mk
  --- android-tools-5.1.1r36+git20160322.orig/debian/makefiles/adb.mk 
2016-08-29 08:32:27.380451578 +0200
  +++ android-tools-5.1.1r36+git20160322/debian/makefiles/adb.mk  2016-08-26 
12:04:54.103221453 +0200
  @@ -34,6 +34,9 @@ CPPFLAGS+= -I.
   CPPFLAGS+= -I../adb
   CPPFLAGS+= -I../include
   CPPFLAGS+= -I../../../external/zlib
  +CPPFLAGS+= -D_FILE_OFFSET_BITS=64
  +
  +CFLAGS+= -D_FILE_OFFSET_BITS=64

   LIBS+= -lc -lpthread -lz -lcrypto

  ---
  RESULT:
  ===
  After I rebuilt the package and installed local version (as shown above) the 
process works and my data are ALL backed up.
  Anybody willing to go through the same process before the package is fixed in 
Ubuntu - good sources are:
  - https://help.ubuntu.com/community/UpdatingADeb
  - https://raphaelhertzog.com/2010/12/15/howto-to-rebuild-debian-packages/
  My package:
  
https://tharrrk.net/stuff/ubuntu/android-tools-adb_5.1.1r36+git20160322-0ubuntu3tharrrk1_i386.deb

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/android-tools/+bug/1617905/+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 1649566] UdevDb.txt

[Dieter Maurer]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1649566/+attachment/5047625/+files/UdevDb.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/1649566

Title:
  xserver-xorg-video-nouveau: X freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Yesterday, I upgraded from Ubuntu 12.04 via 14.04 to 16.04 (LTS
  version in each case). From 14.04 on, I was unable to graphically log
  in. A few seconds after the login (varying between 1 and 10 s), the
  screen changed to a pattern with dense white stripes on the violet/red
  background, and X froze (no reaction to mouse or keyboard). The latest
  messages in "/var/log/syslog" each time showed varying "nouveau E"
  problems, e.g. "unrecognized interupt", "PFIFO", or "PBUS" problems
  such as e.g.: "nouveau E[PBUS][:00:0d.0] MMIO write of
  0x01f70001 FAULT at 0x00b010" (values and addresses varying).

  An internet search revealed that the problem is well known. It affects
  many NVidia graphic cards with the "nouveau" driver. Usually, the
  freeze happens when e.g. "firefox" is started (which happens in my
  context automatically after a graphical login). Most reports recommend
  to switch from "nouveau" to the proprietary NVidia driver. However,
  there seem to be problems with that driver for recent Ubuntu versions.
  I my case, the NVidia driver could not be started (I did not
  investigate why). One report suggested the boot parameter
  "nouveau.config=NvMSI=0" which in my case made the graphical login
  successful again.

  Today, I wanted to report the bug with "ubuntu-bug". However, during the 
collection of the system information, the error happened again (despite the 
"nouveau.config" boot parameter).
  Syslog gives:
  ...
  Dec 13 11:12:01 localhost CRON[5230]: (root) CMD (   test -x 
/etc/cron.daily/popularity-contest && /etc/cron.daily/popularity-contest 
--crond)
  Dec 13 11:14:16 localhost kernel: [ 6889.138599] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:16 localhost kernel: [ 6889.140532] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:59 localhost dbus[795]: [system] Activating service 
name='com.ubuntu.SoftwareProperties' (using servicehelper)
  Dec 13 11:14:59 localhost dbus[795]: [system] Successfully activated service 
'com.ubuntu.SoftwareProperties'
  Dec 13 11:15:01 localhost CRON[5285]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:17:01 localhost CRON[5303]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)
  Dec 13 11:20:01 localhost CRON[5327]: (smmsp) CMD (test -x 
/etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x 
/usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp)
  Dec 13 11:22:20 localhost kernel: [ 7372.621357] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x FAULT at 0x00b020
  Dec 13 11:25:01 localhost CRON[5580]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:35:01 localhost CRON[5651]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:38:02 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.
  Dec 13 11:39:01 localhost CRON[5723]: (root) CMD (  [ -x 
/usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d 
/var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 
$(/usr/lib/php5/maxlifetime))
  Dec 13 11:39:01 localhost CRON[5722]: (root) CMD (  [ -x 
/usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)
  Dec 13 11:39:46 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.

  At this point, I had to reset the computer.

  
  Detailed system information:
  lsdm: lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  xserver-xorg-video-nouveau 1:1.0.12-1build2

  root@lsdm:~# lspci
  00:00.0 RAM memory: NVIDIA Corporation MCP61 Host Bridge (rev a1)
  00:01.0 ISA bridge: NVIDIA Corporation MCP61 LPC Bridge (rev a2)
  00:01.1 SMBus: NVIDIA Corporation MCP61 SMBus (rev a2)
  00:01.2 RAM memory: NVIDIA Corporation MCP61 Memory Controller (rev a2)
  00:02.0 USB controller: NVIDIA Corporation MCP61 USB 1.1 Controller (rev a3)
  00:02.1 USB controller: NVIDIA Corporation MCP61 USB 2.0 Controller (rev a3)
  00:04.0 PCI bridge: NVIDIA Corporation MCP61 PCI bridge (rev a1)
  00:05.0 Audio device: NVIDIA Corporation MCP61 High Definition Audio (rev a2)
  00:06.0 IDE interface: NVIDIA Corporation MCP61 IDE (rev a2)
  00:07.0 Bridge: NVIDIA Corporation MCP61 Ethernet (rev a2)
  00:08.0 IDE interface: NVIDIA Corporation MCP61 SATA Controller (rev a2)
  00:08.1 IDE interface: NVIDIA Corporation MCP61 SATA Controller (rev a2)
  00:09.0 PCI bridge: NVIDIA 

[Touch-packages] [Bug 1687208] Re: wont stay up long enough to post shit

[dino99]

That version is now dead
http://news.softpedia.com/news/ubuntu-17-04-zesty-zapus-has-reached-end-of-life-upgrade-to-ubuntu-17-10-now-519360.shtml


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

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

Title:
  wont stay up long enough to post shit

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  wont stay up long enough to post tried many times

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: xorg 1:7.7+16ubuntu3
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Apr 29 11:14:16 2017
  DistUpgraded: Fresh install
  DistroCodename: zesty
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Carrizo [1002:9874] (rev c5) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Carrizo [103c:80b0]
  InstallationDate: Installed on 2017-04-29 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  MachineType: HP HP Pavilion Notebook
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-20-generic 
root=UUID=0e65c208-5506-4e3a-b42c-13d6248c23e1 ro splash plymouth:debug=1 quiet
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/19/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F.41
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 80B0
  dmi.board.vendor: HP
  dmi.board.version: 81.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF.41:bd09/19/2016:svnHP:pnHPPavilionNotebook:pvr:rvnHP:rn80B0:rvr81.32:cvnHP:ct10:cvrChassisVersion:
  dmi.product.name: HP Pavilion Notebook
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.76-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.3-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.3-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.9.0-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.14-0ubuntu1
  xserver.bootTime: Sat Apr 29 11:12:39 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.3-1ubuntu1
  xserver.video_driver: amdgpu

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

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

[Touch-packages] [Bug 1726124] Re: DNS domain search paths not updated when VPN started

[Launchpad Bug Tracker]

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

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

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

Title:
  DNS domain search paths not updated when VPN started

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

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

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

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

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

search home

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

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

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

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

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

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Oct 22 15:08:57 2017
  InstallationDate: Installed on 2017-10-21 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=UUID=4384306c-5fed-4b48-97a6-a6d594c4f72b ro quiet splash vt.handoff=7
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/02/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2101
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M5A78L-M/USB3
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2101:bd12/02/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A78L-M/USB3:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: 

[Touch-packages] [Bug 1735998] Re: Decouple unity related settings as unity-settings

[Khurshid Alam]

@Jeremy

1)

I only removed unity specific gsettings overrides from ubuntu-settings.

Is there any specific reason to carry unity specific gsettings overrides
in ubuntu-settings? Unity is not a default desktop anymore  nor it is
installed in the default live iso.

2)

We carry unity specific gsettings overrides in unity-settings and make
unity-session depends on unity-settings. That way Ubuntu and Unity
remain separate without overlapping.

3)

And as you said we also want to decouple unity-session from gnome-
session so two pieces code remains separate.

It will easier for us to maintain unity if we keep these separated from
one another.

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

Title:
  Decouple unity related settings as unity-settings

Status in ubuntu-settings package in Ubuntu:
  Confirmed

Bug description:
  This is an attempt to resolve "* Shared GSettings keys" issue listed
  under https://wiki.ubuntu.com/Unity/NotDefaultIssues.

  Ubuntu so far is providing session related overrides for both ubuntu &
  unity sessions in a single package, i.e. ubuntu-settings. But now that
  Unity is not the default desktop it doesn't make any sense to carry
  unity related overrides in ubuntu-settings.

  For this purpose I have created a new project: unity-settings
  (https://code.launchpad.net/~khurshid-alam/unity-settings/trunk) and
  the binary would be unity-settings in universe.

  To make this happen in under 18.04 cycle, the work-flow should be:

  1) Have unity-settings in the universe
  2) Have ubuntu-unity-desktop in the universe
  3) Let ubuntu-unity-desktop depends on unity-settings
  4) Drop unity related settings in ubuntu-settings (merge request in-progress)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-settings/+bug/1735998/+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 38694] A change has been merged

[OpenContrail Admin]

Reviewed:  https://review.opencontrail.org/39137
Committed: 
http://github.com/Juniper/contrail-fabric-utils/commit/e45f84e5a28728f7c1f65935d1f28490a2ef2d70
Submitter: Zuul (z...@lists.opencontrail.org)
Branch:R4.0

commit e45f84e5a28728f7c1f65935d1f28490a2ef2d70
Author: ankitja 
Date:   Mon Jan 15 15:12:41 2018 +0530

Fix attach_logs_cores issue

Closes-bug: #38694

Change-Id: I9aac6d913aa83f7ae94ebb406395b35c0eb0e6a9

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

Title:
  No XChat in Dapper

Status in Juniper Openstack:
  Fix Committed
Status in Juniper Openstack r4.0 series:
  Fix Committed
Status in Juniper Openstack r4.1 series:
  Fix Committed
Status in Juniper Openstack trunk series:
  Fix Committed
Status in ubuntu-meta package in Ubuntu:
  Invalid

Bug description:
  Apparently someone made the decision to remove XChat from the default
  installation for Dapper.  This is important because it is the means
  new users use to reach the various IRC channels on Freenode and all
  the support those have to offer.  I understand that Gaim is still
  included and supports IRC, but this has a few problems as an
  alternative.  First, new users are not going to thing that Gaim
  Internet Messenger in their Applications menu has anything to do with
  getting support.  Second, setting up, connecting to, and using IRC
  isn't entirely intuitive.  Third, many people simply don't like Gaim's
  IRC UI.  Fourth, it does not have the built-in setting like XChat had
  to automatically join #ubuntu when first started.  In short, a brand
  new user is significantly less likely to manage to find the support of
  the IRC channels on their first boot of Ubuntu without XChat included
  and not knowing the ropes pretty well already.  The IRC channels are
  an absolutely vital way of helping new users, and must be very easily
  accessible.  Inclusion of XChat is a big step towards that.  (Further
  UI setup for first boot are an issue as well, but that's a separate
  issue.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/juniperopenstack/+bug/38694/+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 1746638] Re: [GeForce 6150SE nForce 430] PC freezes and crashes

[Christopher M. Penalver]

** Summary changed:

- Nouveau graphics driver freezes and crashes
+ [GeForce 6150SE nForce 430] PC freezes and crashes

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

Title:
  [GeForce 6150SE nForce 430] PC freezes and crashes

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When using the nouveau graphics driver my pc freezes and crashes.

  WORKAROUND: Use the proprietary nvidia driver.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Thu Feb  1 01:36:25 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) 
(prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. C61 [GeForce 6150SE nForce 430] 
[1043:8234]
  InstallationDate: Installed on 2017-11-23 (69 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 04b8:082f Seiko Epson Corp. PX-A620 [Stylus 
CX3900/DX4000/DX4050]
   Bus 002 Device 002: ID 1241:1166 Belkin MI-2150 Trust Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=d7ad7807-5ead-49f7-8978-2e035ab6dd15 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0602
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M2N-MX SE Plus
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev x.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0602:bd10/29/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N-MXSEPlus:rvrRevx.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  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
  version.compiz: compiz N/A
  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.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  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 Feb  1 01:34:53 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputHID 1241:1166MOUSE, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: nouveau

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1746638/+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 38694] A change has been merged

[OpenContrail Admin]

Reviewed:  https://review.opencontrail.org/39136
Committed: 
http://github.com/Juniper/contrail-fabric-utils/commit/e2ce2e05bf864f8c96750073fc35f98cff70c386
Submitter: Zuul v3 CI (zuu...@zuul.opencontrail.org)
Branch:master

commit e2ce2e05bf864f8c96750073fc35f98cff70c386
Author: ankitja 
Date:   Mon Jan 15 15:12:41 2018 +0530

Fix attach_logs_cores issue

Closes-bug: #38694

Change-Id: I9aac6d913aa83f7ae94ebb406395b35c0eb0e6a9


** Changed in: juniperopenstack/trunk
   Status: In Progress => Fix Committed

** Changed in: juniperopenstack/trunk
Milestone: None => r5.0.0

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

Title:
  No XChat in Dapper

Status in Juniper Openstack:
  Fix Committed
Status in Juniper Openstack r4.0 series:
  Fix Committed
Status in Juniper Openstack r4.1 series:
  Fix Committed
Status in Juniper Openstack trunk series:
  Fix Committed
Status in ubuntu-meta package in Ubuntu:
  Invalid

Bug description:
  Apparently someone made the decision to remove XChat from the default
  installation for Dapper.  This is important because it is the means
  new users use to reach the various IRC channels on Freenode and all
  the support those have to offer.  I understand that Gaim is still
  included and supports IRC, but this has a few problems as an
  alternative.  First, new users are not going to thing that Gaim
  Internet Messenger in their Applications menu has anything to do with
  getting support.  Second, setting up, connecting to, and using IRC
  isn't entirely intuitive.  Third, many people simply don't like Gaim's
  IRC UI.  Fourth, it does not have the built-in setting like XChat had
  to automatically join #ubuntu when first started.  In short, a brand
  new user is significantly less likely to manage to find the support of
  the IRC channels on their first boot of Ubuntu without XChat included
  and not knowing the ropes pretty well already.  The IRC channels are
  an absolutely vital way of helping new users, and must be very easily
  accessible.  Inclusion of XChat is a big step towards that.  (Further
  UI setup for first boot are an issue as well, but that's a separate
  issue.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/juniperopenstack/+bug/38694/+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 38694] A change has been merged

[OpenContrail Admin]

Reviewed:  https://review.opencontrail.org/39136
Committed: 
http://github.com/Juniper/contrail-fabric-utils/commit/e2ce2e05bf864f8c96750073fc35f98cff70c386
Submitter: Zuul v3 CI (zuu...@zuul.opencontrail.org)
Branch:master

commit e2ce2e05bf864f8c96750073fc35f98cff70c386
Author: ankitja 
Date:   Mon Jan 15 15:12:41 2018 +0530

Fix attach_logs_cores issue

Closes-bug: #38694

Change-Id: I9aac6d913aa83f7ae94ebb406395b35c0eb0e6a9

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

Title:
  No XChat in Dapper

Status in Juniper Openstack:
  Fix Committed
Status in Juniper Openstack r4.0 series:
  Fix Committed
Status in Juniper Openstack r4.1 series:
  Fix Committed
Status in Juniper Openstack trunk series:
  Fix Committed
Status in ubuntu-meta package in Ubuntu:
  Invalid

Bug description:
  Apparently someone made the decision to remove XChat from the default
  installation for Dapper.  This is important because it is the means
  new users use to reach the various IRC channels on Freenode and all
  the support those have to offer.  I understand that Gaim is still
  included and supports IRC, but this has a few problems as an
  alternative.  First, new users are not going to thing that Gaim
  Internet Messenger in their Applications menu has anything to do with
  getting support.  Second, setting up, connecting to, and using IRC
  isn't entirely intuitive.  Third, many people simply don't like Gaim's
  IRC UI.  Fourth, it does not have the built-in setting like XChat had
  to automatically join #ubuntu when first started.  In short, a brand
  new user is significantly less likely to manage to find the support of
  the IRC channels on their first boot of Ubuntu without XChat included
  and not knowing the ropes pretty well already.  The IRC channels are
  an absolutely vital way of helping new users, and must be very easily
  accessible.  Inclusion of XChat is a big step towards that.  (Further
  UI setup for first boot are an issue as well, but that's a separate
  issue.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/juniperopenstack/+bug/38694/+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 1746874] Re: gnome-shell and Xwayland sometimes leave $HOME/core files (should be /var/crash files)

[Launchpad Bug Tracker]

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

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

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

Title:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files)

Status in apport package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files).

  This is despite:

  $ grep . /proc/sys/kernel/core_*
  /proc/sys/kernel/core_pattern:|/usr/share/apport/apport %p %s %c %d %P
  /proc/sys/kernel/core_pipe_limit:0
  /proc/sys/kernel/core_uses_pid:0

  So really there are two problems:

  1. ~/core files are created but no /var/crash/ files
  2. Because they all have the same name (core_uses_pid == 0), when gnome-shell 
crashes as a result of an Xwayland crash, you can only get the core from one of 
them at most.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  Date: Fri Feb  2 15:13:52 2018
  DisplayManager:

  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  CrashReports:
   640:1000:118:3122469:2018-01-29 16:25:03.658845409 +0800:2018-02-02 
15:39:18.799970611 +0800:/var/crash/_usr_bin_Xwayland.1000.crash
   640:1000:118:24558024:2018-01-29 16:22:23.127058238 +0800:2018-02-02 
15:39:18.887970685 +0800:/var/crash/_usr_bin_gdb.1000.crash
   640:120:118:23982380:2018-01-29 15:52:09.799486456 +0800:2018-01-29 
15:51:51.467493515 +0800:/var/crash/_usr_bin_gnome-shell.120.crash
   640:1000:118:6315115:2018-01-29 16:18:12.723424671 +0800:2018-01-29 
16:18:10.555428082 +0800:/var/crash/_usr_bin_gnome-shell.1000.crash
   640:120:118:3103046:2018-01-29 15:52:12.923485257 +0800:2018-01-29 
15:52:09.859486433 +0800:/var/crash/_usr_bin_Xwayland.120.crash
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  Package: mutter
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Tags:  bionic
  Uname: Linux 4.13.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1746874/+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 1746874] Re: gnome-shell and Xwayland sometimes leave $HOME/core files (should be /var/crash files)

[Launchpad Bug Tracker]

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

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

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

Title:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files)

Status in apport package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files).

  This is despite:

  $ grep . /proc/sys/kernel/core_*
  /proc/sys/kernel/core_pattern:|/usr/share/apport/apport %p %s %c %d %P
  /proc/sys/kernel/core_pipe_limit:0
  /proc/sys/kernel/core_uses_pid:0

  So really there are two problems:

  1. ~/core files are created but no /var/crash/ files
  2. Because they all have the same name (core_uses_pid == 0), when gnome-shell 
crashes as a result of an Xwayland crash, you can only get the core from one of 
them at most.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  Date: Fri Feb  2 15:13:52 2018
  DisplayManager:

  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  CrashReports:
   640:1000:118:3122469:2018-01-29 16:25:03.658845409 +0800:2018-02-02 
15:39:18.799970611 +0800:/var/crash/_usr_bin_Xwayland.1000.crash
   640:1000:118:24558024:2018-01-29 16:22:23.127058238 +0800:2018-02-02 
15:39:18.887970685 +0800:/var/crash/_usr_bin_gdb.1000.crash
   640:120:118:23982380:2018-01-29 15:52:09.799486456 +0800:2018-01-29 
15:51:51.467493515 +0800:/var/crash/_usr_bin_gnome-shell.120.crash
   640:1000:118:6315115:2018-01-29 16:18:12.723424671 +0800:2018-01-29 
16:18:10.555428082 +0800:/var/crash/_usr_bin_gnome-shell.1000.crash
   640:120:118:3103046:2018-01-29 15:52:12.923485257 +0800:2018-01-29 
15:52:09.859486433 +0800:/var/crash/_usr_bin_Xwayland.120.crash
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  Package: mutter
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Tags:  bionic
  Uname: Linux 4.13.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1746874/+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 1746874] Re: gnome-shell and Xwayland sometimes leave $HOME/core files (should be /var/crash files)

[Launchpad Bug Tracker]

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

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

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

Title:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files)

Status in apport package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files).

  This is despite:

  $ grep . /proc/sys/kernel/core_*
  /proc/sys/kernel/core_pattern:|/usr/share/apport/apport %p %s %c %d %P
  /proc/sys/kernel/core_pipe_limit:0
  /proc/sys/kernel/core_uses_pid:0

  So really there are two problems:

  1. ~/core files are created but no /var/crash/ files
  2. Because they all have the same name (core_uses_pid == 0), when gnome-shell 
crashes as a result of an Xwayland crash, you can only get the core from one of 
them at most.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  Date: Fri Feb  2 15:13:52 2018
  DisplayManager:

  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  CrashReports:
   640:1000:118:3122469:2018-01-29 16:25:03.658845409 +0800:2018-02-02 
15:39:18.799970611 +0800:/var/crash/_usr_bin_Xwayland.1000.crash
   640:1000:118:24558024:2018-01-29 16:22:23.127058238 +0800:2018-02-02 
15:39:18.887970685 +0800:/var/crash/_usr_bin_gdb.1000.crash
   640:120:118:23982380:2018-01-29 15:52:09.799486456 +0800:2018-01-29 
15:51:51.467493515 +0800:/var/crash/_usr_bin_gnome-shell.120.crash
   640:1000:118:6315115:2018-01-29 16:18:12.723424671 +0800:2018-01-29 
16:18:10.555428082 +0800:/var/crash/_usr_bin_gnome-shell.1000.crash
   640:120:118:3103046:2018-01-29 15:52:12.923485257 +0800:2018-01-29 
15:52:09.859486433 +0800:/var/crash/_usr_bin_Xwayland.120.crash
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  Package: mutter
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Tags:  bionic
  Uname: Linux 4.13.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1746874/+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 1649566] Re: [GeForce 7025 / nForce 630a] System freeze

[Dieter Maurer]

Responses to your previous questions:
1) It may take a bit of time before I can make the tests with the current 
Ubuntu version. And, I fear that such tests might not be reliable: after the 
temporary use of the NVidia driver I could use the "nouveau" driver for some 
time even without the special boot parameter "nouveau.config=NvMSI=0" - only 
after some months, new freezes occurred. I have the feeling that the problem 
(now) arises non-deterministically -- likely dependent on environment factors 
such as temperature and/or humidity.
While freezes are now rather rare for me, I often observe that the top bars of 
my windows (usually black) are drawn in an irregular black/white pattern 
(similar to the freeze pattern) when I move the mouse pointer over the bar. I 
have the feeling that this is related to the freeze problem.

2) I had no crashes in Ubuntu 12.04 - without any kernel boot
parameters. But, I am not sure that under 12.04, I was already using the
"nouveau" driver. Earlier Ubuntu versions have been using another
standard driver for NVidia cards (likely "nv") and I can no longer
remember which Ubuntu version has switched to "nouveau". I myself did
not actively switch to "nouveau".

3) I could use the NVidia driver for some time under Ubuntu 16.04. But,
its use is unstable in the sense that an Ubuntu update can render it
dysfunctional (apparently, a post installation step has problems to
properly integrate the NVidia driver) and it is very nasty to fix things
up afterwards (I must use a different driver and then reinstall the
NVidia driver via "system administration"). I therefore switched back to
"nouveau".

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

Title:
  [GeForce 7025 / nForce 630a] System freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Yesterday, I upgraded from Ubuntu 12.04 via 14.04 to 16.04. From 14.04
  on, I was unable to graphically log in. A few seconds after the login
  (varying between 1 and 10 s), the screen changed to a pattern with
  dense white stripes on the violet/red background, and X froze (no
  reaction to mouse or keyboard). The latest messages in
  "/var/log/syslog" each time showed varying "nouveau E" problems, e.g.
  "unrecognized interupt", "PFIFO", or "PBUS" problems such as e.g.:
  "nouveau E[PBUS][:00:0d.0] MMIO write of 0x01f70001 FAULT at
  0x00b010" (values and addresses varying).

  Usually, the freeze happens when e.g. "firefox" is started (which
  happens in my context automatically after a graphical login). In my
  case, the NVidia driver could not be started (I did not investigate
  why). Using boot parameter "nouveau.config=NvMSI=0" made the graphical
  login successful again.

  Today, I wanted to report the bug with "ubuntu-bug". However, during
  the collection of the system information, the error happened again
  (despite the "nouveau.config" boot parameter).

  Syslog gives:
  ...
  Dec 13 11:12:01 localhost CRON[5230]: (root) CMD (   test -x 
/etc/cron.daily/popularity-contest && /etc/cron.daily/popularity-contest 
--crond)
  Dec 13 11:14:16 localhost kernel: [ 6889.138599] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:16 localhost kernel: [ 6889.140532] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:59 localhost dbus[795]: [system] Activating service 
name='com.ubuntu.SoftwareProperties' (using servicehelper)
  Dec 13 11:14:59 localhost dbus[795]: [system] Successfully activated service 
'com.ubuntu.SoftwareProperties'
  Dec 13 11:15:01 localhost CRON[5285]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:17:01 localhost CRON[5303]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)
  Dec 13 11:20:01 localhost CRON[5327]: (smmsp) CMD (test -x 
/etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x 
/usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp)
  Dec 13 11:22:20 localhost kernel: [ 7372.621357] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x FAULT at 0x00b020
  Dec 13 11:25:01 localhost CRON[5580]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:35:01 localhost CRON[5651]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:38:02 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.
  Dec 13 11:39:01 localhost CRON[5723]: (root) CMD (  [ -x 
/usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d 
/var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 
$(/usr/lib/php5/maxlifetime))
  Dec 13 11:39:01 localhost CRON[5722]: (root) CMD (  [ -x 
/usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)
  Dec 13 11:39:46 localhost gnome-session[2248]: Gtk-Message: GtkDialog 

[Touch-packages] [Bug 1649566] Re: [GeForce 7025 / nForce 630a] System freeze

[Christopher M. Penalver]

Dieter Maurer:
>"It may take a bit of time before I can make the tests with the current Ubuntu 
>version."

If the problem is reproducible in a live environment, then testing that
would be fine.

>"And, I fear that such tests might not be reliable: after the temporary
use of the NVidia driver I could use the "nouveau" driver for some time
even without the special boot parameter "nouveau.config=NvMSI=0" - only
after some months, new freezes occurred."

Such test is reliable, in that it provides additional data points with
later versions of various related packages. This is required in order to
upstream an issue for upstream developers to address.

Despite this, if one notices different environment behavior with nouveau
after such maneuvering, the proprietary driver may be twiddling some
bits that luckily improve stability after removal. It could also be a
coincedence.

>"I have the feeling that the problem (now) arises non-deterministically
-- likely dependent on environment factors such as temperature and/or
humidity."

Evidence and data are helpful, guesses/feelings/hunches aren't. One may
monitor internal temperatures via
https://help.ubuntu.com/community/SensorInstallHowto in order to prove a
correlation.

>"While freezes are now rather rare for me, I often observe that the top
bars of my windows (usually black) are drawn in an irregular black/white
pattern (similar to the freeze pattern) when I move the mouse pointer
over the bar."

This report is scoped to freezing/crashing. If you are having graphical
issues without freezing/crashing that's a different problem for a new
report. Feel free to file a new one scoped to that and subscribe me to
it.

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

Title:
  [GeForce 7025 / nForce 630a] System freeze

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Yesterday, I upgraded from Ubuntu 12.04 via 14.04 to 16.04. From 14.04
  on, I was unable to graphically log in. A few seconds after the login
  (varying between 1 and 10 s), the screen changed to a pattern with
  dense white stripes on the violet/red background, and X froze (no
  reaction to mouse or keyboard). The latest messages in
  "/var/log/syslog" each time showed varying "nouveau E" problems, e.g.
  "unrecognized interupt", "PFIFO", or "PBUS" problems such as e.g.:
  "nouveau E[PBUS][:00:0d.0] MMIO write of 0x01f70001 FAULT at
  0x00b010" (values and addresses varying).

  Usually, the freeze happens when e.g. "firefox" is started (which
  happens in my context automatically after a graphical login). In my
  case, the NVidia driver could not be started (I did not investigate
  why). Using boot parameter "nouveau.config=NvMSI=0" made the graphical
  login successful again.

  Today, I wanted to report the bug with "ubuntu-bug". However, during
  the collection of the system information, the error happened again
  (despite the "nouveau.config" boot parameter).

  Syslog gives:
  ...
  Dec 13 11:12:01 localhost CRON[5230]: (root) CMD (   test -x 
/etc/cron.daily/popularity-contest && /etc/cron.daily/popularity-contest 
--crond)
  Dec 13 11:14:16 localhost kernel: [ 6889.138599] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:16 localhost kernel: [ 6889.140532] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x07920001 FAULT at 0x00b020
  Dec 13 11:14:59 localhost dbus[795]: [system] Activating service 
name='com.ubuntu.SoftwareProperties' (using servicehelper)
  Dec 13 11:14:59 localhost dbus[795]: [system] Successfully activated service 
'com.ubuntu.SoftwareProperties'
  Dec 13 11:15:01 localhost CRON[5285]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:17:01 localhost CRON[5303]: (root) CMD (   cd / && run-parts 
--report /etc/cron.hourly)
  Dec 13 11:20:01 localhost CRON[5327]: (smmsp) CMD (test -x 
/etc/init.d/sendmail && test -x /usr/share/sendmail/sendmail && test -x 
/usr/lib/sm.bin/sendmail && /usr/share/sendmail/sendmail cron-msp)
  Dec 13 11:22:20 localhost kernel: [ 7372.621357] nouveau E[
PBUS][:00:0d.0] MMIO write of 0x FAULT at 0x00b020
  Dec 13 11:25:01 localhost CRON[5580]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:35:01 localhost CRON[5651]: (root) CMD (command -v debian-sa1 > 
/dev/null && debian-sa1 1 1)
  Dec 13 11:38:02 localhost gnome-session[2248]: Gtk-Message: GtkDialog mapped 
without a transient parent. This is discouraged.
  Dec 13 11:39:01 localhost CRON[5723]: (root) CMD (  [ -x 
/usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d 
/var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 
$(/usr/lib/php5/maxlifetime))
  Dec 13 11:39:01 localhost CRON[5722]: (root) CMD (  [ -x 
/usr/lib/php/sessionclean ] && /usr/lib/php/sessionclean)
  Dec 13 11:39:46 localhost 

[Touch-packages] [Bug 1578657] Re: spanish keyboard not accentuating vowels

[Gunnar Hjalmarsson]

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

Thanks for your report, Michael. The behavior you describe is apparently
not correct. There is a subtle issue regarding dead keys, and I mark
this bug  as a duplicate of that other bug report. You may want to study
it and try some of the workarounds mentioned.

** This bug has been marked a duplicate of bug 1573755
   Compose and dead keys stopped working with XIM after upgrade to 16.04

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

Title:
  spanish keyboard not accentuating vowels

Status in xkeyboard-config package in Ubuntu:
  New

Bug description:
  I've already added the Spanish language keyboard to unity and the keyboard 
indicator at the top indicates the Spanish keyboard and I do get Ñ and ñ
  however when I go to accentuate a vowel áéíóú it's not working

  the normal process is that I press the apostrophe key (in the us keyboard it 
would be two keys toward the right from "L") then select the vowel to be 
accentuated. 
  however you're not supposed to see anything until the vowel is selected.

  what is happening instead is that I'm getting an apostrophe right away
  when I press the tilde key.

  
  NOTE0:
  I've tested also other variants of the Spanish layout with similar success..

  NOTE1:
  I have installed cinnamon also and when I login to cinnamon it works, so I'm 
only experiencing the issue in unity.

  NOTE2:
  I'm very proficient with computers and have successfully done this many times.

  NOTE3: 
  I'm working on a fairly clean setup of Ubuntu 16.04 LTS
   I've only added Cinnamon and the Intel Drivers to the system and google 
chrome 
   system is also up to date.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1578657/+subscriptions

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

[Touch-packages] [Bug 1726124] Re: DNS domain search paths not updated when VPN started

[Paul Smith]

I'm not sure why it's being asserted that these two uses are mutually
incompatible, especially since I've been using them in a coordinated way
forever and can still do so (at the expense of junking systemd-resolve
and going back to using dnsmasq and a custom configuration, which is
obviously a big pain).  I've even, in the past, used MULTIPLE VPNs, even
at the same time, and it still just works.

If the resolver library (e.g., gethostbyname etc.) gets an unqualified
hostname, it uses the search path just as it always has including ndots
and all that stuff, to generate FQ hostnames.  No change there.

When the local resolver caching service (dnsmasq, systemd-resolv) gets a
FQ hostname it looks through the extensions provided by the VPN DHCP
information and if the hostname matches that extension it forwards the
lookup to the DNS server for that VPN.  If it doesn't match, it doesn't
forward the request.  If it doesn't match any of the VPN search paths,
it forwards the request to the default DNS servers.

I honestly don't understand why we're considering these uses
incompatible.  They seem to me to be exactly compatible and exactly what
you want to do, at least the vast majority of the time.

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

Title:
  DNS domain search paths not updated when VPN started

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

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

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

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

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

search home

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

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

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

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

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

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

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

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

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

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: systemd 234-2ubuntu12
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Oct 22 15:08:57 2017
  InstallationDate: Installed on 2017-10-21 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic 
root=UUID=4384306c-5fed-4b48-97a6-a6d594c4f72b 

[Touch-packages] [Bug 1717714] Re: @{pid} variable broken on systems with pid_max more than 6 digits

[Łukasz Zemczak]

Hello Andre, or anyone else affected,

Accepted apparmor into trusty-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/apparmor/2.10.95-0ubuntu2.6~14.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-trusty to verification-done-trusty. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-trusty. 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: apparmor (Ubuntu Trusty)
   Status: In Progress => Fix Committed

** Tags removed: verification-failed-trusty
** Tags added: verification-needed-trusty

-- 
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:
  Fix Released
Status in apparmor source package in Trusty:
  Fix Committed
Status in apparmor source package in Xenial:
  Fix Committed
Status in apparmor source package in Artful:
  Fix Committed
Status in apparmor source package in Bionic:
  Fix Released
Status in apparmor package in Debian:
  Fix Released

Bug description:
  [Impact]

  If PID is larger than 6 digits apparmor denies process which only
  affect 64-bit systems[1] where the PID_MAX_LIMIT can be generated up
  to 7 digits at the maximum.

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

  [1] - man 5 proc

  --
  /proc/sys/kernel/pid_max (since Linux 2.5.34)
  This file specifies the value at which PIDs wrap around (i.e., the value in 
this file is one greater than the maximum PID).  PIDs greater than this value 
are not allocated;  thus,  the value  in this file also acts as a system-wide 
limit on the total number of processes and threads.  The default value for this 
file, 32768, results in the same range of PIDs as on ear‐lier kernels.  On 
32-bit platforms, 32768 is the maximum value for pid_max.  On 64-bit systems, 
pid_max can be set to any value up to 2^22 (PID_MAX_LIMIT, approximately 4 
million).
  --

  [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

  OR

  instead of Seyeong's touch approach, things can be manually change to
  7 digits range via sysctl as long as the values are below
  approximately 4 millions :

  Example:
  $ sysctl -w kernel.pid_max=300
  $ sysctl -w kernel.ns_last_pid=100

  [Regression]
  * This is a minor/trivial fix which changes the pid regex only, allowing 7 
digits PID instead of only 6 digits PID, we don't think there is any potential 
regression.

  * If a regression arise, which we highly doubt, one can quickly revert
  the change manually and restart the service by modifying
  "/etc/apparmor.d/tunables/kernelvars" file to its original state
  (before this SRU).

  [Others]

  * Upstream commit:
   
https://gitlab.com/apparmor/apparmor/commit/630cb2a981cdc731847e8fdaafc45bcd337fe747
  http://bazaar.launchpad.net/~apparmor-dev/apparmor/master/revision/3722

  * Debian bug:
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886732

  * 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   

[Touch-packages] [Bug 1747085] [NEW] NetworkManager: setting wifi.cloned-mac-address from pre-up.d fails silently for new connections

[Paul M Furley]

Public bug reported:

network-manager 1.2.6-0ubuntu0.16.04.2

I'm using a script in /etc/NetworkManager/dispatcher.d/pre-up.d to
assign a pseudorandom mac address using the cloned-mac-address setting
(via this command):

> nmcli connection modify  wifi.cloned-mac-address


(Specifically, I'm using this script:
https://gist.github.com/paulfurley/46e0547ce5c5ea7eabeaef50dbacef3f)


This works a treat for existing connections - ifconfig shows that the MAC 
address has been assigned correctly (as denoted by the leading 02):

```
$ ifconfig wlp6s0
wlp6s0Link encap:Ethernet  HWaddr 02:2a:8b:4e:ca:ef
```

However if I delete that connection from Network Manager and add it
again, the interface comes, leaking its real hardware mac address:

```
$ ifconfig wlp6s0
wlp6s0Link encap:Ethernet  HWaddr b0:35:9f:XX:XX:XX
```

Theory 1: Maybe pre-up.d hooks don't run for new connections? Nope - I
can see from the logs that the script definitely runs when I connect to
the wifi for the first time.

Theory 2: Maybe the Network Manager connection doesn't exist yet, so the
script can't see it via its initial `nmcli connection show` command?
Nope - at the top of the log is the command `nmcli connection modify
 wifi.cloned-mac-address 02:34:ae:08:7d:5f`

So, in summary, setting wifi.cloned-mac-address from a pre-up.d hook
works great for *existing* connections but appears to fail silently for
*new* connections.

Thanks!

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

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

Title:
  NetworkManager: setting wifi.cloned-mac-address from pre-up.d fails
  silently for new connections

Status in network-manager package in Ubuntu:
  New

Bug description:
  network-manager 1.2.6-0ubuntu0.16.04.2

  I'm using a script in /etc/NetworkManager/dispatcher.d/pre-up.d to
  assign a pseudorandom mac address using the cloned-mac-address setting
  (via this command):

  > nmcli connection modify  wifi.cloned-mac-address
  

  (Specifically, I'm using this script:
  https://gist.github.com/paulfurley/46e0547ce5c5ea7eabeaef50dbacef3f)

  
  This works a treat for existing connections - ifconfig shows that the MAC 
address has been assigned correctly (as denoted by the leading 02):

  ```
  $ ifconfig wlp6s0
  wlp6s0Link encap:Ethernet  HWaddr 02:2a:8b:4e:ca:ef
  ```

  However if I delete that connection from Network Manager and add it
  again, the interface comes, leaking its real hardware mac address:

  ```
  $ ifconfig wlp6s0
  wlp6s0Link encap:Ethernet  HWaddr b0:35:9f:XX:XX:XX
  ```

  Theory 1: Maybe pre-up.d hooks don't run for new connections? Nope - I
  can see from the logs that the script definitely runs when I connect
  to the wifi for the first time.

  Theory 2: Maybe the Network Manager connection doesn't exist yet, so
  the script can't see it via its initial `nmcli connection show`
  command? Nope - at the top of the log is the command `nmcli connection
  modify  wifi.cloned-mac-address
  02:34:ae:08:7d:5f`

  So, in summary, setting wifi.cloned-mac-address from a pre-up.d hook
  works great for *existing* connections but appears to fail silently
  for *new* connections.

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1747085/+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 1635074] Re: Nepali Keyboard symbol should have zero width joiner and non joiner

[Sagar Chalise]

Reported bug upstream:
https://bugs.freedesktop.org/show_bug.cgi?id=104921

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

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

Title:
  Nepali Keyboard symbol should have zero width joiner and non joiner

Status in xkeyboard-config package in Ubuntu:
  Incomplete

Bug description:
  The symbols file located at '/usr/share/X11/xkb/symbols/np' doesnot
  seem to work for zero width joiner. The  'equal' key in line 22 should
  work as zero width joiner.

  'पर्=यो' is the output while it should be 'पर्‍यो' ।

  The workout seems to be replacing 'equal' in line 22 with '0x100200D'

  Also, the upper keys in numbers i.e. @,#,$,% etc are missing and
  should be available as is except for +,= where zero width joiner and
  non-joiner are used.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1635074/+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 1747085] Re: NetworkManager: setting wifi.cloned-mac-address from pre-up.d fails silently for new connections

[Launchpad Bug Tracker]

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

** Changed in: network-manager (Ubuntu)
   Status: New => Confirmed

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

Title:
  NetworkManager: setting wifi.cloned-mac-address from pre-up.d fails
  silently for new connections

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  network-manager 1.2.6-0ubuntu0.16.04.2

  I'm using a script in /etc/NetworkManager/dispatcher.d/pre-up.d to
  assign a pseudorandom mac address using the cloned-mac-address setting
  (via this command):

  > nmcli connection modify  wifi.cloned-mac-address
  

  (Specifically, I'm using this script:
  https://gist.github.com/paulfurley/46e0547ce5c5ea7eabeaef50dbacef3f)

  
  This works a treat for existing connections - ifconfig shows that the MAC 
address has been assigned correctly (as denoted by the leading 02):

  ```
  $ ifconfig wlp6s0
  wlp6s0Link encap:Ethernet  HWaddr 02:2a:8b:4e:ca:ef
  ```

  However if I delete that connection from Network Manager and add it
  again, the interface comes, leaking its real hardware mac address:

  ```
  $ ifconfig wlp6s0
  wlp6s0Link encap:Ethernet  HWaddr b0:35:9f:XX:XX:XX
  ```

  Theory 1: Maybe pre-up.d hooks don't run for new connections? Nope - I
  can see from the logs that the script definitely runs when I connect
  to the wifi for the first time.

  Theory 2: Maybe the Network Manager connection doesn't exist yet, so
  the script can't see it via its initial `nmcli connection show`
  command? Nope - at the top of the log is the command `nmcli connection
  modify  wifi.cloned-mac-address
  02:34:ae:08:7d:5f`

  So, in summary, setting wifi.cloned-mac-address from a pre-up.d hook
  works great for *existing* connections but appears to fail silently
  for *new* connections.

  Thanks!

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1747085/+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 1635074] Re: Nepali Keyboard symbol should have zero width joiner and non joiner

[Gunnar Hjalmarsson]

Thanks.

** Also affects: xkeyboard-config via
   https://bugs.freedesktop.org/show_bug.cgi?id=104921
   Importance: Unknown
   Status: Unknown

** Changed in: xkeyboard-config (Ubuntu)
   Status: Incomplete => New

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

Title:
  Nepali Keyboard symbol should have zero width joiner and non joiner

Status in xkeyboard-config:
  Unknown
Status in xkeyboard-config package in Ubuntu:
  New

Bug description:
  The symbols file located at '/usr/share/X11/xkb/symbols/np' doesnot
  seem to work for zero width joiner. The  'equal' key in line 22 should
  work as zero width joiner.

  'पर्=यो' is the output while it should be 'पर्‍यो' ।

  The workout seems to be replacing 'equal' in line 22 with '0x100200D'

  Also, the upper keys in numbers i.e. @,#,$,% etc are missing and
  should be available as is except for +,= where zero width joiner and
  non-joiner are used.

To manage notifications about this bug go to:
https://bugs.launchpad.net/xkeyboard-config/+bug/1635074/+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 1660072] Re: Missing depends on xkb-data-i18n

[Gunnar Hjalmarsson]

The ubiquity source package, which is used to build the installers,
depends on xkb-data-i18n for building.

https://packages.ubuntu.com/source/bionic/ubiquity

That's apparently the reason why xkb-data-i18n exists. Closing.

** Changed in: xkeyboard-config (Ubuntu)
   Status: New => Invalid

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

Title:
  Missing depends on xkb-data-i18n

Status in xkeyboard-config package in Ubuntu:
  Invalid

Bug description:
  A reverse depends for xkb-data-i18n shows that nothing depends on it.

  Surely xkb-data should depend or recommend it's installation?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1660072/+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 1746638] Re: [GeForce 6150SE nForce 430] PC freezes and crashes

[Diogo Gomes]

I had a full copy of kern.log, I attached it.

(Sorry for only post last 10min in other attachment)

** Attachment added: "kern.log"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1746638/+attachment/5047802/+files/kern.log

** Attachment removed: "kern.log (10 last min before crash)"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1746638/+attachment/5047048/+files/kern%20%2810m%20before%20crash%29.log

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

Title:
  [GeForce 6150SE nForce 430] PC freezes and crashes

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When using the nouveau graphics driver my pc freezes and crashes.

  WORKAROUND: Use the proprietary nvidia driver.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Thu Feb  1 01:36:25 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) 
(prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. C61 [GeForce 6150SE nForce 430] 
[1043:8234]
  InstallationDate: Installed on 2017-11-23 (69 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 04b8:082f Seiko Epson Corp. PX-A620 [Stylus 
CX3900/DX4000/DX4050]
   Bus 002 Device 002: ID 1241:1166 Belkin MI-2150 Trust Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=d7ad7807-5ead-49f7-8978-2e035ab6dd15 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0602
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M2N-MX SE Plus
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev x.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0602:bd10/29/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N-MXSEPlus:rvrRevx.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  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
  version.compiz: compiz N/A
  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.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  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 Feb  1 01:34:53 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputHID 1241:1166MOUSE, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: nouveau

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1746638/+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 1490738] Re: Lithuanian keyboard doesn't switch on

[Gunnar Hjalmarsson]

Thanks for your report.

This is not something I can reproduce; the Lithuanian keyboard layout
works as expected for me.

Do you still have the problem? If you have, can you please provide some
more details about the Ubuntu version and desktop environment where you
encounter the issue.

** Changed in: xkeyboard-config (Ubuntu)
   Status: New => Incomplete

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

Title:
  Lithuanian keyboard doesn't switch on

Status in xkeyboard-config package in Ubuntu:
  Incomplete

Bug description:
  Lithuanian keyboard gives no Lithuanian symbols. Using SUPER+SPACE it
  does change language indicator on the upper right corner of the
  desktop, but there's no Lt symbols where they are supposed to be.

  Lt symbols should be on the keyboard's upper number line. The symbol
  map still claims they are there. In matter of fact, when I switch to
  Lt keyboard, it still uses Finnish symbols. Finnish is my main
  keyboard at the moment.

  Before that, there were Russian symbols instead of Lt. So I
  uninstalled Rus keyboard. That caused Lt keyboard to show English
  symbols. After uninstalling Eng, now Lt keyboard is sticking with Fin.
  Adding new languages doesn't change behaviour (still Fi).

  Other languages on keyboard work fine. Uninstalling all keyboards
  except Lt, still makes no Lithuanian symbols.

  I tried uninstall Lithuanian keyboard (with reboot) and install again.
  Also tried different Lithuanian keyboards.

  Ubuntu 14.04.3 LTS 64-bit on MSI GE620DX laptop.

  (That's my first bug report, hope I'm doing it as it's supposed to be
  done.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1490738/+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 1746765] Re: systemd FTBFS on arm64

[Dimitri John Ledkov]

With new gnu-efi, the invalid relocation appears to be in side the gnu-
efi crt object code. It seems to me that possibly fixes in either
toolchain or gnu-efi, may resolve systemd build failure.

disabling gnu-efi feature of the systemd arm64 build.

** Changed in: systemd (Ubuntu Bionic)
   Status: Confirmed => In Progress

** Changed in: systemd (Ubuntu Bionic)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

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

Title:
  systemd FTBFS on arm64

Status in binutils:
  Confirmed
Status in binutils package in Ubuntu:
  New
Status in gnu-efi package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  In Progress
Status in binutils source package in Bionic:
  New
Status in gnu-efi source package in Bionic:
  New
Status in systemd source package in Bionic:
  In Progress

Bug description:
  Might be a bug in the toolchain, gnu-efi or systemd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/binutils/+bug/1746765/+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 1316970] Re: g_dbus memory leak in lrmd

[Seyeong Kim]

** Patch added: "lp1316970_trusty_pacemaker_v2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1316970/+attachment/5047782/+files/lp1316970_trusty_pacemaker_v2.debdiff

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

Title:
  g_dbus memory leak in lrmd

Status in glib2.0 package in Ubuntu:
  New
Status in pacemaker package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Trusty:
  New
Status in pacemaker source package in Trusty:
  In Progress

Bug description:
  [Impact]
  lrmd daemon with upstart resource has memory leak in Trusty

  affected to pacemaker 1.1.10.
  affected to glib2.0 2.40.2-0ubuntu1

  Please note that patch for pacemaker is created myself.

  [Test Case]

  1. deploy 3 trusty instance.
  2. install corosync, pacemaker, mysql.
  3. setting with below info
  3.1 corosync.conf, proper setting for 3 node
  3.2 crm configure < setup.crm ( which has upstart:mysql setting )
  3.3 monitor lrmd daemon's memory usage

  [Regression]
  Restarting daemon after upgrading this pkg will be needed. this patch added 
NULL check for several parts. prior commit[1] changed file structure. and This 
change makes user changes usage of upstart:mysql to lsb:mysql. So I added free 
function myself. This might affect to system.
  For glib2.0, commit [1] is critical, but [2],[3],[4] is needed for building 
it.

  [Others]

  Related commits.

  [1] commit a7b61e276120184c7586a3217ed3571a982f5017
  Author: Andrew Beekhof 
  Date:   Fri Aug 23 16:25:35 2013 +1000

  Refactor: attrd: Move to its own directory and create a stub for
  attrd-ng

  --
  $ git describe --contains a1a6922e43dfe80b23887a88401cbb93fe3645c0
  Pacemaker-1.1.11-rc3

  $ git describe --contains a7b61e276120184c7586a3217ed3571a982f5017
  Pacemaker-1.1.11-rc1~168

  $ rmadison pacemaker
   pacemaker | 1.1.10+git20130802-1ubuntu2   | trusty
   pacemaker | 1.1.10+git20130802-1ubuntu2.4 | trusty-security
   pacemaker | 1.1.10+git20130802-1ubuntu2.4 | trusty-updates

   pacemaker | 1.1.14-2ubuntu1   | xenial
   pacemaker | 1.1.14-2ubuntu1.3 | xenial-security
   pacemaker | 1.1.14-2ubuntu1.3 | xenial-update
   pacemaker | 1.1.16-1ubuntu1   | zesty
   pacemaker | 1.1.16-1ubuntu1   | artful
   pacemaker | 1.1.18~rc3-1ubuntu1   | bionic
  --

  For glib
  [1] 
https://github.com/GNOME/glib/commit/db641e32920ee8b553ab6f2d318aafa156e4390c
  [2] 
https://github.com/GNOME/glib/commit/8792609e15394967cab526838b83f90acb401663
  [3] 
https://github.com/GNOME/glib/commit/ec02a1875f29ecb8e46c0d8c1403cd00a0b3a9e4
  [4] 
https://github.com/GNOME/glib/commit/f10b6550ff2ce55d06b92d6dc3e443fc007b2f7a

  [Original Description]

  I'm running Pacemaker 1.1.10+git20130802-1ubuntu1 on Ubuntu Saucy
  (13.10) and have encountered a memory leak in lrmd.

  The details of the bug are covered here in this thread
  (http://oss.clusterlabs.org/pipermail/pacemaker/2014-May/021689.html)
  but to summarise, the Pacemaker developers believe the leak is caused
  by the g_dbus API, the use of which was removed in Pacemaker 1.11.

  I've also attached the Valgrind output from the run that exposed the
  issue.

  Given that this issue affects production stability (a periodic restart
  of Pacemaker is required), will a version of 1.11 be released for
  Trusty? (I'm happy to upgrade the OS to Trusty to get it).

  If not, can you advise which version of the OS will be the first to
  take 1.11 please?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1316970/+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 1746874] Re: gnome-shell and Xwayland sometimes leave $HOME/core files (should be /var/crash files)

[Brian Murray]

Information from 'journalctl -u apport' around the time of the core
file's creation would be useful or /var/log/apport.log if apport was
really running.

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

Title:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files)

Status in apport package in Ubuntu:
  Incomplete
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files).

  This is despite:

  $ grep . /proc/sys/kernel/core_*
  /proc/sys/kernel/core_pattern:|/usr/share/apport/apport %p %s %c %d %P
  /proc/sys/kernel/core_pipe_limit:0
  /proc/sys/kernel/core_uses_pid:0

  So really there are two problems:

  1. ~/core files are created but no /var/crash/ files
  2. Because they all have the same name (core_uses_pid == 0), when gnome-shell 
crashes as a result of an Xwayland crash, you can only get the core from one of 
them at most.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  Date: Fri Feb  2 15:13:52 2018
  DisplayManager:

  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  CrashReports:
   640:1000:118:3122469:2018-01-29 16:25:03.658845409 +0800:2018-02-02 
15:39:18.799970611 +0800:/var/crash/_usr_bin_Xwayland.1000.crash
   640:1000:118:24558024:2018-01-29 16:22:23.127058238 +0800:2018-02-02 
15:39:18.887970685 +0800:/var/crash/_usr_bin_gdb.1000.crash
   640:120:118:23982380:2018-01-29 15:52:09.799486456 +0800:2018-01-29 
15:51:51.467493515 +0800:/var/crash/_usr_bin_gnome-shell.120.crash
   640:1000:118:6315115:2018-01-29 16:18:12.723424671 +0800:2018-01-29 
16:18:10.555428082 +0800:/var/crash/_usr_bin_gnome-shell.1000.crash
   640:120:118:3103046:2018-01-29 15:52:12.923485257 +0800:2018-01-29 
15:52:09.859486433 +0800:/var/crash/_usr_bin_Xwayland.120.crash
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  Package: mutter
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Tags:  bionic
  Uname: Linux 4.13.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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