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

[Valentin Nechayev]

apport information

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

Title:
  Spontaneous single window freezing

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Sometimes a window stopped refreshing its contents. Different applications 
affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen.
  No way found to revive in-time refreshing except full window closing (or 
blind login, in case of KDE lock screen). Keyboard or mouse activity in a such 
window doesn't help.
  A one-shot refresh can be easily caused by switching to another virtual 
desktop and then back. After such switching, a window refresh is active for 
approximately 0.5 seconds, then stops again.
  No relation to host uptime or X session uptime is visible.

  Observed on two different hosts, both carrying Kubuntu 16.04 and
  running XWindow+KDE as desktop environment. KDE is standard Kubuntu
  one. Multiple virtual desktops are used on both hosts.

  The issue started to appear approximately 4-5 months ago but I can't
  specify exact package change that could have caused it. Both hosts are
  regularly updated (no more than 1 week delay).

  The first host has:
  video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller])
  Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670]
  Kernel driver in use: radeon
  Kernel modules: radeon
  CPU: AMD FX-8150
  RAM: 16GB
  Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade.
  current kernel: linux-image-4.4.0-112-generic
  video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active 
driver: radeon

  Issue rate on this host is rather tiny (~1 per week).

  The second one has:
  video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev 
a1) (prog-if 00 [VGA controller])
  Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93
  Kernel driver in use: nvidia
  Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384
  (really this is GeForce GT 740)
  CPU:Intel i3-4170
  RAM: 16GB
  Installed originally as Kubuntu 16.04
  current kernel: linux-image-4.13.0-32-generic (depended on by 
linux-generic-hwe-16.04)
  video packages: HWE series (e.g. 
xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia 
(proprietary), but the same issue observed with VESA driver.

  Issue rate on this host is 1-2 per day and was much higher with VESA
  driver in use.

  No respective messages are found in Xorg.*.log or ~/.xsession-errors,
  but the latter has got stream of messages like:

  at host with AMD and Radeon:
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )

  at host with Intel and Nvidia:
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )

  such messages started appearing approximately at the same time, plus-
  minus 1-2 months.

  Additional info can be provided on demand.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  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
  CurrentDesktop: KDE
  Date: Tue Feb 13 11:47:32 2018
  InstallationDate: Installed on 2014-12-16 (1154 days ago)
  InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago)
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, 

[Touch-packages] [Bug 1749150] XorgLogOld.txt

[Valentin Nechayev]

apport information

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

Title:
  Spontaneous single window freezing

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Sometimes a window stopped refreshing its contents. Different applications 
affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen.
  No way found to revive in-time refreshing except full window closing (or 
blind login, in case of KDE lock screen). Keyboard or mouse activity in a such 
window doesn't help.
  A one-shot refresh can be easily caused by switching to another virtual 
desktop and then back. After such switching, a window refresh is active for 
approximately 0.5 seconds, then stops again.
  No relation to host uptime or X session uptime is visible.

  Observed on two different hosts, both carrying Kubuntu 16.04 and
  running XWindow+KDE as desktop environment. KDE is standard Kubuntu
  one. Multiple virtual desktops are used on both hosts.

  The issue started to appear approximately 4-5 months ago but I can't
  specify exact package change that could have caused it. Both hosts are
  regularly updated (no more than 1 week delay).

  The first host has:
  video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller])
  Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670]
  Kernel driver in use: radeon
  Kernel modules: radeon
  CPU: AMD FX-8150
  RAM: 16GB
  Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade.
  current kernel: linux-image-4.4.0-112-generic
  video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active 
driver: radeon

  Issue rate on this host is rather tiny (~1 per week).

  The second one has:
  video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev 
a1) (prog-if 00 [VGA controller])
  Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93
  Kernel driver in use: nvidia
  Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384
  (really this is GeForce GT 740)
  CPU:Intel i3-4170
  RAM: 16GB
  Installed originally as Kubuntu 16.04
  current kernel: linux-image-4.13.0-32-generic (depended on by 
linux-generic-hwe-16.04)
  video packages: HWE series (e.g. 
xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia 
(proprietary), but the same issue observed with VESA driver.

  Issue rate on this host is 1-2 per day and was much higher with VESA
  driver in use.

  No respective messages are found in Xorg.*.log or ~/.xsession-errors,
  but the latter has got stream of messages like:

  at host with AMD and Radeon:
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )

  at host with Intel and Nvidia:
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )

  such messages started appearing approximately at the same time, plus-
  minus 1-2 months.

  Additional info can be provided on demand.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  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
  CurrentDesktop: KDE
  Date: Tue Feb 13 11:47:32 2018
  InstallationDate: Installed on 2014-12-16 (1154 days ago)
  InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago)
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and 

[Touch-packages] [Bug 1749381] [NEW] Graphical Problem

[Saurabh Rathi]

Public bug reported:

I am unable to play HD videos. HD videos are buffering.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 14 12:52:25 2018
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
ExtraDebuggingInterest: No
GraphicsCard:
 Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 
02) (prog-if 00 [VGA controller])
   Subsystem: Intel Corporation 82945G/GZ Integrated Graphics Controller 
[8086:2772]
InstallationDate: Installed on 2017-10-26 (110 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic 
root=UUID=2ef10e92-a428-42e0-853c-7020c65b6864 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/23/2013
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.chassis.type: 3
dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd08/23/2013:svn:pn:pvr:rvn:rn:rvr:cvn:ct3:cvr:
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.83-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug artful ubuntu wayland-session

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

Title:
  Graphical Problem

Status in xorg package in Ubuntu:
  New

Bug description:
  I am unable to play HD videos. HD videos are buffering.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 14 12:52:25 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 
02) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation 82945G/GZ Integrated Graphics Controller 
[8086:2772]
  InstallationDate: Installed on 2017-10-26 (110 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-32-generic 
root=UUID=2ef10e92-a428-42e0-853c-7020c65b6864 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/23/2013
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd08/23/2013:svn:pn:pvr:rvn:rn:rvr:cvn:ct3:cvr:
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.2-0ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.2-0ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

[Valentin Nechayev]

apport information

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

Title:
  Spontaneous single window freezing

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Sometimes a window stopped refreshing its contents. Different applications 
affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen.
  No way found to revive in-time refreshing except full window closing (or 
blind login, in case of KDE lock screen). Keyboard or mouse activity in a such 
window doesn't help.
  A one-shot refresh can be easily caused by switching to another virtual 
desktop and then back. After such switching, a window refresh is active for 
approximately 0.5 seconds, then stops again.
  No relation to host uptime or X session uptime is visible.

  Observed on two different hosts, both carrying Kubuntu 16.04 and
  running XWindow+KDE as desktop environment. KDE is standard Kubuntu
  one. Multiple virtual desktops are used on both hosts.

  The issue started to appear approximately 4-5 months ago but I can't
  specify exact package change that could have caused it. Both hosts are
  regularly updated (no more than 1 week delay).

  The first host has:
  video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller])
  Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670]
  Kernel driver in use: radeon
  Kernel modules: radeon
  CPU: AMD FX-8150
  RAM: 16GB
  Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade.
  current kernel: linux-image-4.4.0-112-generic
  video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active 
driver: radeon

  Issue rate on this host is rather tiny (~1 per week).

  The second one has:
  video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev 
a1) (prog-if 00 [VGA controller])
  Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93
  Kernel driver in use: nvidia
  Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384
  (really this is GeForce GT 740)
  CPU:Intel i3-4170
  RAM: 16GB
  Installed originally as Kubuntu 16.04
  current kernel: linux-image-4.13.0-32-generic (depended on by 
linux-generic-hwe-16.04)
  video packages: HWE series (e.g. 
xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia 
(proprietary), but the same issue observed with VESA driver.

  Issue rate on this host is 1-2 per day and was much higher with VESA
  driver in use.

  No respective messages are found in Xorg.*.log or ~/.xsession-errors,
  but the latter has got stream of messages like:

  at host with AMD and Radeon:
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )

  at host with Intel and Nvidia:
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )

  such messages started appearing approximately at the same time, plus-
  minus 1-2 months.

  Additional info can be provided on demand.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  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
  CurrentDesktop: KDE
  Date: Tue Feb 13 11:47:32 2018
  InstallationDate: Installed on 2014-12-16 (1154 days ago)
  InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago)
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supp

[Touch-packages] [Bug 1749150] NvidiaBugReportLog.txt

[Valentin Nechayev]

apport information

** Attachment added: "NvidiaBugReportLog.txt"
   
https://bugs.launchpad.net/bugs/1749150/+attachment/5054884/+files/NvidiaBugReportLog.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/1749150

Title:
  Spontaneous single window freezing

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Sometimes a window stopped refreshing its contents. Different applications 
affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen.
  No way found to revive in-time refreshing except full window closing (or 
blind login, in case of KDE lock screen). Keyboard or mouse activity in a such 
window doesn't help.
  A one-shot refresh can be easily caused by switching to another virtual 
desktop and then back. After such switching, a window refresh is active for 
approximately 0.5 seconds, then stops again.
  No relation to host uptime or X session uptime is visible.

  Observed on two different hosts, both carrying Kubuntu 16.04 and
  running XWindow+KDE as desktop environment. KDE is standard Kubuntu
  one. Multiple virtual desktops are used on both hosts.

  The issue started to appear approximately 4-5 months ago but I can't
  specify exact package change that could have caused it. Both hosts are
  regularly updated (no more than 1 week delay).

  The first host has:
  video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller])
  Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670]
  Kernel driver in use: radeon
  Kernel modules: radeon
  CPU: AMD FX-8150
  RAM: 16GB
  Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade.
  current kernel: linux-image-4.4.0-112-generic
  video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active 
driver: radeon

  Issue rate on this host is rather tiny (~1 per week).

  The second one has:
  video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev 
a1) (prog-if 00 [VGA controller])
  Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93
  Kernel driver in use: nvidia
  Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384
  (really this is GeForce GT 740)
  CPU:Intel i3-4170
  RAM: 16GB
  Installed originally as Kubuntu 16.04
  current kernel: linux-image-4.13.0-32-generic (depended on by 
linux-generic-hwe-16.04)
  video packages: HWE series (e.g. 
xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia 
(proprietary), but the same issue observed with VESA driver.

  Issue rate on this host is 1-2 per day and was much higher with VESA
  driver in use.

  No respective messages are found in Xorg.*.log or ~/.xsession-errors,
  but the latter has got stream of messages like:

  at host with AMD and Radeon:
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )

  at host with Intel and Nvidia:
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )

  such messages started appearing approximately at the same time, plus-
  minus 1-2 months.

  Additional info can be provided on demand.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  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
  CurrentDesktop: KDE
  Date: Tue Feb 13 11:47:32 2018
  InstallationDate: Installed on 2014-12-16 (1154 days ago)
  InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago)
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stabilit

[Touch-packages] [Bug 1749150] UdevDb.txt

[Valentin Nechayev]

apport information

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

Title:
  Spontaneous single window freezing

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Sometimes a window stopped refreshing its contents. Different applications 
affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen.
  No way found to revive in-time refreshing except full window closing (or 
blind login, in case of KDE lock screen). Keyboard or mouse activity in a such 
window doesn't help.
  A one-shot refresh can be easily caused by switching to another virtual 
desktop and then back. After such switching, a window refresh is active for 
approximately 0.5 seconds, then stops again.
  No relation to host uptime or X session uptime is visible.

  Observed on two different hosts, both carrying Kubuntu 16.04 and
  running XWindow+KDE as desktop environment. KDE is standard Kubuntu
  one. Multiple virtual desktops are used on both hosts.

  The issue started to appear approximately 4-5 months ago but I can't
  specify exact package change that could have caused it. Both hosts are
  regularly updated (no more than 1 week delay).

  The first host has:
  video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller])
  Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670]
  Kernel driver in use: radeon
  Kernel modules: radeon
  CPU: AMD FX-8150
  RAM: 16GB
  Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade.
  current kernel: linux-image-4.4.0-112-generic
  video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active 
driver: radeon

  Issue rate on this host is rather tiny (~1 per week).

  The second one has:
  video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev 
a1) (prog-if 00 [VGA controller])
  Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93
  Kernel driver in use: nvidia
  Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384
  (really this is GeForce GT 740)
  CPU:Intel i3-4170
  RAM: 16GB
  Installed originally as Kubuntu 16.04
  current kernel: linux-image-4.13.0-32-generic (depended on by 
linux-generic-hwe-16.04)
  video packages: HWE series (e.g. 
xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia 
(proprietary), but the same issue observed with VESA driver.

  Issue rate on this host is 1-2 per day and was much higher with VESA
  driver in use.

  No respective messages are found in Xorg.*.log or ~/.xsession-errors,
  but the latter has got stream of messages like:

  at host with AMD and Radeon:
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )

  at host with Intel and Nvidia:
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )

  such messages started appearing approximately at the same time, plus-
  minus 1-2 months.

  Additional info can be provided on demand.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  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
  CurrentDesktop: KDE
  Date: Tue Feb 13 11:47:32 2018
  InstallationDate: Installed on 2014-12-16 (1154 days ago)
  InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago)
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not su

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

[Valentin Nechayev]

apport information

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

Title:
  Spontaneous single window freezing

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Sometimes a window stopped refreshing its contents. Different applications 
affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen.
  No way found to revive in-time refreshing except full window closing (or 
blind login, in case of KDE lock screen). Keyboard or mouse activity in a such 
window doesn't help.
  A one-shot refresh can be easily caused by switching to another virtual 
desktop and then back. After such switching, a window refresh is active for 
approximately 0.5 seconds, then stops again.
  No relation to host uptime or X session uptime is visible.

  Observed on two different hosts, both carrying Kubuntu 16.04 and
  running XWindow+KDE as desktop environment. KDE is standard Kubuntu
  one. Multiple virtual desktops are used on both hosts.

  The issue started to appear approximately 4-5 months ago but I can't
  specify exact package change that could have caused it. Both hosts are
  regularly updated (no more than 1 week delay).

  The first host has:
  video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller])
  Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670]
  Kernel driver in use: radeon
  Kernel modules: radeon
  CPU: AMD FX-8150
  RAM: 16GB
  Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade.
  current kernel: linux-image-4.4.0-112-generic
  video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active 
driver: radeon

  Issue rate on this host is rather tiny (~1 per week).

  The second one has:
  video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev 
a1) (prog-if 00 [VGA controller])
  Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93
  Kernel driver in use: nvidia
  Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384
  (really this is GeForce GT 740)
  CPU:Intel i3-4170
  RAM: 16GB
  Installed originally as Kubuntu 16.04
  current kernel: linux-image-4.13.0-32-generic (depended on by 
linux-generic-hwe-16.04)
  video packages: HWE series (e.g. 
xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia 
(proprietary), but the same issue observed with VESA driver.

  Issue rate on this host is 1-2 per day and was much higher with VESA
  driver in use.

  No respective messages are found in Xorg.*.log or ~/.xsession-errors,
  but the latter has got stream of messages like:

  at host with AMD and Radeon:
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )

  at host with Intel and Nvidia:
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )

  such messages started appearing approximately at the same time, plus-
  minus 1-2 months.

  Additional info can be provided on demand.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  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
  CurrentDesktop: KDE
  Date: Tue Feb 13 11:47:32 2018
  InstallationDate: Installed on 2014-12-16 (1154 days ago)
  InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago)
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, an

[Touch-packages] [Bug 1749150] XorgLog.txt

[Valentin Nechayev]

apport information

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

Title:
  Spontaneous single window freezing

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Sometimes a window stopped refreshing its contents. Different applications 
affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen.
  No way found to revive in-time refreshing except full window closing (or 
blind login, in case of KDE lock screen). Keyboard or mouse activity in a such 
window doesn't help.
  A one-shot refresh can be easily caused by switching to another virtual 
desktop and then back. After such switching, a window refresh is active for 
approximately 0.5 seconds, then stops again.
  No relation to host uptime or X session uptime is visible.

  Observed on two different hosts, both carrying Kubuntu 16.04 and
  running XWindow+KDE as desktop environment. KDE is standard Kubuntu
  one. Multiple virtual desktops are used on both hosts.

  The issue started to appear approximately 4-5 months ago but I can't
  specify exact package change that could have caused it. Both hosts are
  regularly updated (no more than 1 week delay).

  The first host has:
  video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller])
  Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670]
  Kernel driver in use: radeon
  Kernel modules: radeon
  CPU: AMD FX-8150
  RAM: 16GB
  Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade.
  current kernel: linux-image-4.4.0-112-generic
  video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active 
driver: radeon

  Issue rate on this host is rather tiny (~1 per week).

  The second one has:
  video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev 
a1) (prog-if 00 [VGA controller])
  Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93
  Kernel driver in use: nvidia
  Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384
  (really this is GeForce GT 740)
  CPU:Intel i3-4170
  RAM: 16GB
  Installed originally as Kubuntu 16.04
  current kernel: linux-image-4.13.0-32-generic (depended on by 
linux-generic-hwe-16.04)
  video packages: HWE series (e.g. 
xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia 
(proprietary), but the same issue observed with VESA driver.

  Issue rate on this host is 1-2 per day and was much higher with VESA
  driver in use.

  No respective messages are found in Xorg.*.log or ~/.xsession-errors,
  but the latter has got stream of messages like:

  at host with AMD and Radeon:
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )

  at host with Intel and Nvidia:
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )

  such messages started appearing approximately at the same time, plus-
  minus 1-2 months.

  Additional info can be provided on demand.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  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
  CurrentDesktop: KDE
  Date: Tue Feb 13 11:47:32 2018
  InstallationDate: Installed on 2014-12-16 (1154 days ago)
  InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago)
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not

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

[Valentin Nechayev]

apport information

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

Title:
  Spontaneous single window freezing

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Sometimes a window stopped refreshing its contents. Different applications 
affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen.
  No way found to revive in-time refreshing except full window closing (or 
blind login, in case of KDE lock screen). Keyboard or mouse activity in a such 
window doesn't help.
  A one-shot refresh can be easily caused by switching to another virtual 
desktop and then back. After such switching, a window refresh is active for 
approximately 0.5 seconds, then stops again.
  No relation to host uptime or X session uptime is visible.

  Observed on two different hosts, both carrying Kubuntu 16.04 and
  running XWindow+KDE as desktop environment. KDE is standard Kubuntu
  one. Multiple virtual desktops are used on both hosts.

  The issue started to appear approximately 4-5 months ago but I can't
  specify exact package change that could have caused it. Both hosts are
  regularly updated (no more than 1 week delay).

  The first host has:
  video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller])
  Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670]
  Kernel driver in use: radeon
  Kernel modules: radeon
  CPU: AMD FX-8150
  RAM: 16GB
  Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade.
  current kernel: linux-image-4.4.0-112-generic
  video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active 
driver: radeon

  Issue rate on this host is rather tiny (~1 per week).

  The second one has:
  video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev 
a1) (prog-if 00 [VGA controller])
  Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93
  Kernel driver in use: nvidia
  Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384
  (really this is GeForce GT 740)
  CPU:Intel i3-4170
  RAM: 16GB
  Installed originally as Kubuntu 16.04
  current kernel: linux-image-4.13.0-32-generic (depended on by 
linux-generic-hwe-16.04)
  video packages: HWE series (e.g. 
xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia 
(proprietary), but the same issue observed with VESA driver.

  Issue rate on this host is 1-2 per day and was much higher with VESA
  driver in use.

  No respective messages are found in Xorg.*.log or ~/.xsession-errors,
  but the latter has got stream of messages like:

  at host with AMD and Radeon:
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )

  at host with Intel and Nvidia:
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )

  such messages started appearing approximately at the same time, plus-
  minus 1-2 months.

  Additional info can be provided on demand.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  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
  CurrentDesktop: KDE
  Date: Tue Feb 13 11:47:32 2018
  InstallationDate: Installed on 2014-12-16 (1154 days ago)
  InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago)
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, an

[Touch-packages] [Bug 1749150] JournalErrors.txt

[Valentin Nechayev]

apport information

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

Title:
  Spontaneous single window freezing

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Sometimes a window stopped refreshing its contents. Different applications 
affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen.
  No way found to revive in-time refreshing except full window closing (or 
blind login, in case of KDE lock screen). Keyboard or mouse activity in a such 
window doesn't help.
  A one-shot refresh can be easily caused by switching to another virtual 
desktop and then back. After such switching, a window refresh is active for 
approximately 0.5 seconds, then stops again.
  No relation to host uptime or X session uptime is visible.

  Observed on two different hosts, both carrying Kubuntu 16.04 and
  running XWindow+KDE as desktop environment. KDE is standard Kubuntu
  one. Multiple virtual desktops are used on both hosts.

  The issue started to appear approximately 4-5 months ago but I can't
  specify exact package change that could have caused it. Both hosts are
  regularly updated (no more than 1 week delay).

  The first host has:
  video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller])
  Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670]
  Kernel driver in use: radeon
  Kernel modules: radeon
  CPU: AMD FX-8150
  RAM: 16GB
  Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade.
  current kernel: linux-image-4.4.0-112-generic
  video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active 
driver: radeon

  Issue rate on this host is rather tiny (~1 per week).

  The second one has:
  video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev 
a1) (prog-if 00 [VGA controller])
  Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93
  Kernel driver in use: nvidia
  Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384
  (really this is GeForce GT 740)
  CPU:Intel i3-4170
  RAM: 16GB
  Installed originally as Kubuntu 16.04
  current kernel: linux-image-4.13.0-32-generic (depended on by 
linux-generic-hwe-16.04)
  video packages: HWE series (e.g. 
xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia 
(proprietary), but the same issue observed with VESA driver.

  Issue rate on this host is 1-2 per day and was much higher with VESA
  driver in use.

  No respective messages are found in Xorg.*.log or ~/.xsession-errors,
  but the latter has got stream of messages like:

  at host with AMD and Radeon:
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )

  at host with Intel and Nvidia:
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )

  such messages started appearing approximately at the same time, plus-
  minus 1-2 months.

  Additional info can be provided on demand.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  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
  CurrentDesktop: KDE
  Date: Tue Feb 13 11:47:32 2018
  InstallationDate: Installed on 2014-12-16 (1154 days ago)
  InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago)
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems

[Touch-packages] [Bug 1749150] DpkgLog.txt

[Valentin Nechayev]

apport information

** Attachment added: "DpkgLog.txt"
   
https://bugs.launchpad.net/bugs/1749150/+attachment/5054880/+files/DpkgLog.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/1749150

Title:
  Spontaneous single window freezing

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Sometimes a window stopped refreshing its contents. Different applications 
affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen.
  No way found to revive in-time refreshing except full window closing (or 
blind login, in case of KDE lock screen). Keyboard or mouse activity in a such 
window doesn't help.
  A one-shot refresh can be easily caused by switching to another virtual 
desktop and then back. After such switching, a window refresh is active for 
approximately 0.5 seconds, then stops again.
  No relation to host uptime or X session uptime is visible.

  Observed on two different hosts, both carrying Kubuntu 16.04 and
  running XWindow+KDE as desktop environment. KDE is standard Kubuntu
  one. Multiple virtual desktops are used on both hosts.

  The issue started to appear approximately 4-5 months ago but I can't
  specify exact package change that could have caused it. Both hosts are
  regularly updated (no more than 1 week delay).

  The first host has:
  video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller])
  Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670]
  Kernel driver in use: radeon
  Kernel modules: radeon
  CPU: AMD FX-8150
  RAM: 16GB
  Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade.
  current kernel: linux-image-4.4.0-112-generic
  video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active 
driver: radeon

  Issue rate on this host is rather tiny (~1 per week).

  The second one has:
  video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev 
a1) (prog-if 00 [VGA controller])
  Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93
  Kernel driver in use: nvidia
  Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384
  (really this is GeForce GT 740)
  CPU:Intel i3-4170
  RAM: 16GB
  Installed originally as Kubuntu 16.04
  current kernel: linux-image-4.13.0-32-generic (depended on by 
linux-generic-hwe-16.04)
  video packages: HWE series (e.g. 
xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia 
(proprietary), but the same issue observed with VESA driver.

  Issue rate on this host is 1-2 per day and was much higher with VESA
  driver in use.

  No respective messages are found in Xorg.*.log or ~/.xsession-errors,
  but the latter has got stream of messages like:

  at host with AMD and Radeon:
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )

  at host with Intel and Nvidia:
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )

  such messages started appearing approximately at the same time, plus-
  minus 1-2 months.

  Additional info can be provided on demand.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  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
  CurrentDesktop: KDE
  Date: Tue Feb 13 11:47:32 2018
  InstallationDate: Installed on 2014-12-16 (1154 days ago)
  InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago)
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not

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

[Valentin Nechayev]

apport information

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

Title:
  Spontaneous single window freezing

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Sometimes a window stopped refreshing its contents. Different applications 
affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen.
  No way found to revive in-time refreshing except full window closing (or 
blind login, in case of KDE lock screen). Keyboard or mouse activity in a such 
window doesn't help.
  A one-shot refresh can be easily caused by switching to another virtual 
desktop and then back. After such switching, a window refresh is active for 
approximately 0.5 seconds, then stops again.
  No relation to host uptime or X session uptime is visible.

  Observed on two different hosts, both carrying Kubuntu 16.04 and
  running XWindow+KDE as desktop environment. KDE is standard Kubuntu
  one. Multiple virtual desktops are used on both hosts.

  The issue started to appear approximately 4-5 months ago but I can't
  specify exact package change that could have caused it. Both hosts are
  regularly updated (no more than 1 week delay).

  The first host has:
  video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller])
  Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670]
  Kernel driver in use: radeon
  Kernel modules: radeon
  CPU: AMD FX-8150
  RAM: 16GB
  Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade.
  current kernel: linux-image-4.4.0-112-generic
  video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active 
driver: radeon

  Issue rate on this host is rather tiny (~1 per week).

  The second one has:
  video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev 
a1) (prog-if 00 [VGA controller])
  Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93
  Kernel driver in use: nvidia
  Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384
  (really this is GeForce GT 740)
  CPU:Intel i3-4170
  RAM: 16GB
  Installed originally as Kubuntu 16.04
  current kernel: linux-image-4.13.0-32-generic (depended on by 
linux-generic-hwe-16.04)
  video packages: HWE series (e.g. 
xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia 
(proprietary), but the same issue observed with VESA driver.

  Issue rate on this host is 1-2 per day and was much higher with VESA
  driver in use.

  No respective messages are found in Xorg.*.log or ~/.xsession-errors,
  but the latter has got stream of messages like:

  at host with AMD and Radeon:
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )

  at host with Intel and Nvidia:
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )

  such messages started appearing approximately at the same time, plus-
  minus 1-2 months.

  Additional info can be provided on demand.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  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
  CurrentDesktop: KDE
  Date: Tue Feb 13 11:47:32 2018
  InstallationDate: Installed on 2014-12-16 (1154 days ago)
  InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago)
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability proble

[Touch-packages] [Bug 1749150] Lsusb.txt

[Valentin Nechayev]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1749150/+attachment/5054883/+files/Lsusb.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/1749150

Title:
  Spontaneous single window freezing

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Sometimes a window stopped refreshing its contents. Different applications 
affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen.
  No way found to revive in-time refreshing except full window closing (or 
blind login, in case of KDE lock screen). Keyboard or mouse activity in a such 
window doesn't help.
  A one-shot refresh can be easily caused by switching to another virtual 
desktop and then back. After such switching, a window refresh is active for 
approximately 0.5 seconds, then stops again.
  No relation to host uptime or X session uptime is visible.

  Observed on two different hosts, both carrying Kubuntu 16.04 and
  running XWindow+KDE as desktop environment. KDE is standard Kubuntu
  one. Multiple virtual desktops are used on both hosts.

  The issue started to appear approximately 4-5 months ago but I can't
  specify exact package change that could have caused it. Both hosts are
  regularly updated (no more than 1 week delay).

  The first host has:
  video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller])
  Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670]
  Kernel driver in use: radeon
  Kernel modules: radeon
  CPU: AMD FX-8150
  RAM: 16GB
  Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade.
  current kernel: linux-image-4.4.0-112-generic
  video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active 
driver: radeon

  Issue rate on this host is rather tiny (~1 per week).

  The second one has:
  video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev 
a1) (prog-if 00 [VGA controller])
  Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93
  Kernel driver in use: nvidia
  Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384
  (really this is GeForce GT 740)
  CPU:Intel i3-4170
  RAM: 16GB
  Installed originally as Kubuntu 16.04
  current kernel: linux-image-4.13.0-32-generic (depended on by 
linux-generic-hwe-16.04)
  video packages: HWE series (e.g. 
xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia 
(proprietary), but the same issue observed with VESA driver.

  Issue rate on this host is 1-2 per day and was much higher with VESA
  driver in use.

  No respective messages are found in Xorg.*.log or ~/.xsession-errors,
  but the latter has got stream of messages like:

  at host with AMD and Radeon:
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )

  at host with Intel and Nvidia:
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )

  such messages started appearing approximately at the same time, plus-
  minus 1-2 months.

  Additional info can be provided on demand.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  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
  CurrentDesktop: KDE
  Date: Tue Feb 13 11:47:32 2018
  InstallationDate: Installed on 2014-12-16 (1154 days ago)
  InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago)
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supp

[Touch-packages] [Bug 1749150] ProcEnviron.txt

[Valentin Nechayev]

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1749150/+attachment/5054887/+files/ProcEnviron.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/1749150

Title:
  Spontaneous single window freezing

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Sometimes a window stopped refreshing its contents. Different applications 
affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen.
  No way found to revive in-time refreshing except full window closing (or 
blind login, in case of KDE lock screen). Keyboard or mouse activity in a such 
window doesn't help.
  A one-shot refresh can be easily caused by switching to another virtual 
desktop and then back. After such switching, a window refresh is active for 
approximately 0.5 seconds, then stops again.
  No relation to host uptime or X session uptime is visible.

  Observed on two different hosts, both carrying Kubuntu 16.04 and
  running XWindow+KDE as desktop environment. KDE is standard Kubuntu
  one. Multiple virtual desktops are used on both hosts.

  The issue started to appear approximately 4-5 months ago but I can't
  specify exact package change that could have caused it. Both hosts are
  regularly updated (no more than 1 week delay).

  The first host has:
  video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller])
  Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670]
  Kernel driver in use: radeon
  Kernel modules: radeon
  CPU: AMD FX-8150
  RAM: 16GB
  Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade.
  current kernel: linux-image-4.4.0-112-generic
  video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active 
driver: radeon

  Issue rate on this host is rather tiny (~1 per week).

  The second one has:
  video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev 
a1) (prog-if 00 [VGA controller])
  Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93
  Kernel driver in use: nvidia
  Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384
  (really this is GeForce GT 740)
  CPU:Intel i3-4170
  RAM: 16GB
  Installed originally as Kubuntu 16.04
  current kernel: linux-image-4.13.0-32-generic (depended on by 
linux-generic-hwe-16.04)
  video packages: HWE series (e.g. 
xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia 
(proprietary), but the same issue observed with VESA driver.

  Issue rate on this host is 1-2 per day and was much higher with VESA
  driver in use.

  No respective messages are found in Xorg.*.log or ~/.xsession-errors,
  but the latter has got stream of messages like:

  at host with AMD and Radeon:
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )

  at host with Intel and Nvidia:
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )

  such messages started appearing approximately at the same time, plus-
  minus 1-2 months.

  Additional info can be provided on demand.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  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
  CurrentDesktop: KDE
  Date: Tue Feb 13 11:47:32 2018
  InstallationDate: Installed on 2014-12-16 (1154 days ago)
  InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago)
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, an

[Touch-packages] [Bug 1749150] Xrandr.txt

[Valentin Nechayev]

apport information

** Attachment added: "Xrandr.txt"
   https://bugs.launchpad.net/bugs/1749150/+attachment/5054893/+files/Xrandr.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/1749150

Title:
  Spontaneous single window freezing

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Sometimes a window stopped refreshing its contents. Different applications 
affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen.
  No way found to revive in-time refreshing except full window closing (or 
blind login, in case of KDE lock screen). Keyboard or mouse activity in a such 
window doesn't help.
  A one-shot refresh can be easily caused by switching to another virtual 
desktop and then back. After such switching, a window refresh is active for 
approximately 0.5 seconds, then stops again.
  No relation to host uptime or X session uptime is visible.

  Observed on two different hosts, both carrying Kubuntu 16.04 and
  running XWindow+KDE as desktop environment. KDE is standard Kubuntu
  one. Multiple virtual desktops are used on both hosts.

  The issue started to appear approximately 4-5 months ago but I can't
  specify exact package change that could have caused it. Both hosts are
  regularly updated (no more than 1 week delay).

  The first host has:
  video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller])
  Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670]
  Kernel driver in use: radeon
  Kernel modules: radeon
  CPU: AMD FX-8150
  RAM: 16GB
  Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade.
  current kernel: linux-image-4.4.0-112-generic
  video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active 
driver: radeon

  Issue rate on this host is rather tiny (~1 per week).

  The second one has:
  video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev 
a1) (prog-if 00 [VGA controller])
  Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93
  Kernel driver in use: nvidia
  Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384
  (really this is GeForce GT 740)
  CPU:Intel i3-4170
  RAM: 16GB
  Installed originally as Kubuntu 16.04
  current kernel: linux-image-4.13.0-32-generic (depended on by 
linux-generic-hwe-16.04)
  video packages: HWE series (e.g. 
xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia 
(proprietary), but the same issue observed with VESA driver.

  Issue rate on this host is 1-2 per day and was much higher with VESA
  driver in use.

  No respective messages are found in Xorg.*.log or ~/.xsession-errors,
  but the latter has got stream of messages like:

  at host with AMD and Radeon:
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )

  at host with Intel and Nvidia:
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )

  such messages started appearing approximately at the same time, plus-
  minus 1-2 months.

  Additional info can be provided on demand.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  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
  CurrentDesktop: KDE
  Date: Tue Feb 13 11:47:32 2018
  InstallationDate: Installed on 2014-12-16 (1154 days ago)
  InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago)
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not su

[Touch-packages] [Bug 1749150] Re: Spontaneous single window freezing

[Valentin Nechayev]

Just have sent info from the second host (Intel+NVidia; more prone to
the issue). Will do it for the first host in a few hours.

Please notice that apport-collect is somewhat broken -
1) it didn't request dependence on python-qt5 but needs it for run time;
2) it just created a dialog window "Text. Yes? No?", i.e. without real 
question. I had to blindly answer "yes".

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

Title:
  Spontaneous single window freezing

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Sometimes a window stopped refreshing its contents. Different applications 
affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen.
  No way found to revive in-time refreshing except full window closing (or 
blind login, in case of KDE lock screen). Keyboard or mouse activity in a such 
window doesn't help.
  A one-shot refresh can be easily caused by switching to another virtual 
desktop and then back. After such switching, a window refresh is active for 
approximately 0.5 seconds, then stops again.
  No relation to host uptime or X session uptime is visible.

  Observed on two different hosts, both carrying Kubuntu 16.04 and
  running XWindow+KDE as desktop environment. KDE is standard Kubuntu
  one. Multiple virtual desktops are used on both hosts.

  The issue started to appear approximately 4-5 months ago but I can't
  specify exact package change that could have caused it. Both hosts are
  regularly updated (no more than 1 week delay).

  The first host has:
  video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller])
  Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670]
  Kernel driver in use: radeon
  Kernel modules: radeon
  CPU: AMD FX-8150
  RAM: 16GB
  Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade.
  current kernel: linux-image-4.4.0-112-generic
  video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active 
driver: radeon

  Issue rate on this host is rather tiny (~1 per week).

  The second one has:
  video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev 
a1) (prog-if 00 [VGA controller])
  Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93
  Kernel driver in use: nvidia
  Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384
  (really this is GeForce GT 740)
  CPU:Intel i3-4170
  RAM: 16GB
  Installed originally as Kubuntu 16.04
  current kernel: linux-image-4.13.0-32-generic (depended on by 
linux-generic-hwe-16.04)
  video packages: HWE series (e.g. 
xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia 
(proprietary), but the same issue observed with VESA driver.

  Issue rate on this host is 1-2 per day and was much higher with VESA
  driver in use.

  No respective messages are found in Xorg.*.log or ~/.xsession-errors,
  but the latter has got stream of messages like:

  at host with AMD and Radeon:
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )

  at host with Intel and Nvidia:
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )

  such messages started appearing approximately at the same time, plus-
  minus 1-2 months.

  Additional info can be provided on demand.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  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
  CurrentDesktop: KDE
  Date: Tue Feb 13 11:47:32 2018
  InstallationDate: Installed on 2014-12-16 (1154 days ago)
  InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago)
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the pr

[Touch-packages] [Bug 1749150] ProcCpuinfoMinimal.txt

[Valentin Nechayev]

apport information

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

Title:
  Spontaneous single window freezing

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Sometimes a window stopped refreshing its contents. Different applications 
affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen.
  No way found to revive in-time refreshing except full window closing (or 
blind login, in case of KDE lock screen). Keyboard or mouse activity in a such 
window doesn't help.
  A one-shot refresh can be easily caused by switching to another virtual 
desktop and then back. After such switching, a window refresh is active for 
approximately 0.5 seconds, then stops again.
  No relation to host uptime or X session uptime is visible.

  Observed on two different hosts, both carrying Kubuntu 16.04 and
  running XWindow+KDE as desktop environment. KDE is standard Kubuntu
  one. Multiple virtual desktops are used on both hosts.

  The issue started to appear approximately 4-5 months ago but I can't
  specify exact package change that could have caused it. Both hosts are
  regularly updated (no more than 1 week delay).

  The first host has:
  video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller])
  Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670]
  Kernel driver in use: radeon
  Kernel modules: radeon
  CPU: AMD FX-8150
  RAM: 16GB
  Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade.
  current kernel: linux-image-4.4.0-112-generic
  video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active 
driver: radeon

  Issue rate on this host is rather tiny (~1 per week).

  The second one has:
  video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev 
a1) (prog-if 00 [VGA controller])
  Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93
  Kernel driver in use: nvidia
  Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384
  (really this is GeForce GT 740)
  CPU:Intel i3-4170
  RAM: 16GB
  Installed originally as Kubuntu 16.04
  current kernel: linux-image-4.13.0-32-generic (depended on by 
linux-generic-hwe-16.04)
  video packages: HWE series (e.g. 
xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia 
(proprietary), but the same issue observed with VESA driver.

  Issue rate on this host is 1-2 per day and was much higher with VESA
  driver in use.

  No respective messages are found in Xorg.*.log or ~/.xsession-errors,
  but the latter has got stream of messages like:

  at host with AMD and Radeon:
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )

  at host with Intel and Nvidia:
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )

  such messages started appearing approximately at the same time, plus-
  minus 1-2 months.

  Additional info can be provided on demand.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  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
  CurrentDesktop: KDE
  Date: Tue Feb 13 11:47:32 2018
  InstallationDate: Installed on 2014-12-16 (1154 days ago)
  InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago)
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stabilit

[Touch-packages] [Bug 1749150] xdpyinfo.txt

[Valentin Nechayev]

apport information

** Attachment added: "xdpyinfo.txt"
   
https://bugs.launchpad.net/bugs/1749150/+attachment/5054895/+files/xdpyinfo.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/1749150

Title:
  Spontaneous single window freezing

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Sometimes a window stopped refreshing its contents. Different applications 
affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen.
  No way found to revive in-time refreshing except full window closing (or 
blind login, in case of KDE lock screen). Keyboard or mouse activity in a such 
window doesn't help.
  A one-shot refresh can be easily caused by switching to another virtual 
desktop and then back. After such switching, a window refresh is active for 
approximately 0.5 seconds, then stops again.
  No relation to host uptime or X session uptime is visible.

  Observed on two different hosts, both carrying Kubuntu 16.04 and
  running XWindow+KDE as desktop environment. KDE is standard Kubuntu
  one. Multiple virtual desktops are used on both hosts.

  The issue started to appear approximately 4-5 months ago but I can't
  specify exact package change that could have caused it. Both hosts are
  regularly updated (no more than 1 week delay).

  The first host has:
  video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller])
  Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670]
  Kernel driver in use: radeon
  Kernel modules: radeon
  CPU: AMD FX-8150
  RAM: 16GB
  Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade.
  current kernel: linux-image-4.4.0-112-generic
  video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active 
driver: radeon

  Issue rate on this host is rather tiny (~1 per week).

  The second one has:
  video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev 
a1) (prog-if 00 [VGA controller])
  Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93
  Kernel driver in use: nvidia
  Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384
  (really this is GeForce GT 740)
  CPU:Intel i3-4170
  RAM: 16GB
  Installed originally as Kubuntu 16.04
  current kernel: linux-image-4.13.0-32-generic (depended on by 
linux-generic-hwe-16.04)
  video packages: HWE series (e.g. 
xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia 
(proprietary), but the same issue observed with VESA driver.

  Issue rate on this host is 1-2 per day and was much higher with VESA
  driver in use.

  No respective messages are found in Xorg.*.log or ~/.xsession-errors,
  but the latter has got stream of messages like:

  at host with AMD and Radeon:
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )

  at host with Intel and Nvidia:
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )

  such messages started appearing approximately at the same time, plus-
  minus 1-2 months.

  Additional info can be provided on demand.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  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
  CurrentDesktop: KDE
  Date: Tue Feb 13 11:47:32 2018
  InstallationDate: Installed on 2014-12-16 (1154 days ago)
  InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago)
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is n

[Touch-packages] [Bug 1741227] Re: apparmor denial to several paths to binaries

[Tony]

Still happens with MAAS deployed Ubuntu 17.10.
And with update I get "ntp is already the newest version 
(1:4.2.8p10+dfsg-5ubuntu3.1)." How do I get the last part that's "3.1" into 
that "5" if that matters?

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

Title:
  apparmor denial to several paths to binaries

Status in ntp package in Ubuntu:
  Fix Released

Bug description:
  Issue shows up (non fatal) as:
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/sbin/" pid=23933 comm="ntpd" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/bin/" pid=23933 comm="ntpd" requested_mask="r" denied_mask="r" 
fsuid=0 ouid=0

  Since non crit this is mostyl about many of us being curious why it
  actually does do it :-)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1741227/+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 1749150] Dependencies.txt

[Valentin Nechayev]

apport information

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

Title:
  Spontaneous single window freezing

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Sometimes a window stopped refreshing its contents. Different applications 
affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen.
  No way found to revive in-time refreshing except full window closing (or 
blind login, in case of KDE lock screen). Keyboard or mouse activity in a such 
window doesn't help.
  A one-shot refresh can be easily caused by switching to another virtual 
desktop and then back. After such switching, a window refresh is active for 
approximately 0.5 seconds, then stops again.
  No relation to host uptime or X session uptime is visible.

  Observed on two different hosts, both carrying Kubuntu 16.04 and
  running XWindow+KDE as desktop environment. KDE is standard Kubuntu
  one. Multiple virtual desktops are used on both hosts.

  The issue started to appear approximately 4-5 months ago but I can't
  specify exact package change that could have caused it. Both hosts are
  regularly updated (no more than 1 week delay).

  The first host has:
  video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller])
  Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670]
  Kernel driver in use: radeon
  Kernel modules: radeon
  CPU: AMD FX-8150
  RAM: 16GB
  Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade.
  current kernel: linux-image-4.4.0-112-generic
  video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active 
driver: radeon

  Issue rate on this host is rather tiny (~1 per week).

  The second one has:
  video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev 
a1) (prog-if 00 [VGA controller])
  Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93
  Kernel driver in use: nvidia
  Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384
  (really this is GeForce GT 740)
  CPU:Intel i3-4170
  RAM: 16GB
  Installed originally as Kubuntu 16.04
  current kernel: linux-image-4.13.0-32-generic (depended on by 
linux-generic-hwe-16.04)
  video packages: HWE series (e.g. 
xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia 
(proprietary), but the same issue observed with VESA driver.

  Issue rate on this host is 1-2 per day and was much higher with VESA
  driver in use.

  No respective messages are found in Xorg.*.log or ~/.xsession-errors,
  but the latter has got stream of messages like:

  at host with AMD and Radeon:
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )

  at host with Intel and Nvidia:
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )

  such messages started appearing approximately at the same time, plus-
  minus 1-2 months.

  Additional info can be provided on demand.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  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
  CurrentDesktop: KDE
  Date: Tue Feb 13 11:47:32 2018
  InstallationDate: Installed on 2014-12-16 (1154 days ago)
  InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago)
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, 

[Touch-packages] [Bug 1749150] nvidia-settings.txt

[Valentin Nechayev]

apport information

** Attachment added: "nvidia-settings.txt"
   
https://bugs.launchpad.net/bugs/1749150/+attachment/5054894/+files/nvidia-settings.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/1749150

Title:
  Spontaneous single window freezing

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Sometimes a window stopped refreshing its contents. Different applications 
affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen.
  No way found to revive in-time refreshing except full window closing (or 
blind login, in case of KDE lock screen). Keyboard or mouse activity in a such 
window doesn't help.
  A one-shot refresh can be easily caused by switching to another virtual 
desktop and then back. After such switching, a window refresh is active for 
approximately 0.5 seconds, then stops again.
  No relation to host uptime or X session uptime is visible.

  Observed on two different hosts, both carrying Kubuntu 16.04 and
  running XWindow+KDE as desktop environment. KDE is standard Kubuntu
  one. Multiple virtual desktops are used on both hosts.

  The issue started to appear approximately 4-5 months ago but I can't
  specify exact package change that could have caused it. Both hosts are
  regularly updated (no more than 1 week delay).

  The first host has:
  video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller])
  Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670]
  Kernel driver in use: radeon
  Kernel modules: radeon
  CPU: AMD FX-8150
  RAM: 16GB
  Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade.
  current kernel: linux-image-4.4.0-112-generic
  video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active 
driver: radeon

  Issue rate on this host is rather tiny (~1 per week).

  The second one has:
  video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev 
a1) (prog-if 00 [VGA controller])
  Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93
  Kernel driver in use: nvidia
  Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384
  (really this is GeForce GT 740)
  CPU:Intel i3-4170
  RAM: 16GB
  Installed originally as Kubuntu 16.04
  current kernel: linux-image-4.13.0-32-generic (depended on by 
linux-generic-hwe-16.04)
  video packages: HWE series (e.g. 
xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia 
(proprietary), but the same issue observed with VESA driver.

  Issue rate on this host is 1-2 per day and was much higher with VESA
  driver in use.

  No respective messages are found in Xorg.*.log or ~/.xsession-errors,
  but the latter has got stream of messages like:

  at host with AMD and Radeon:
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )

  at host with Intel and Nvidia:
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )

  such messages started appearing approximately at the same time, plus-
  minus 1-2 months.

  Additional info can be provided on demand.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  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
  CurrentDesktop: KDE
  Date: Tue Feb 13 11:47:32 2018
  InstallationDate: Installed on 2014-12-16 (1154 days ago)
  InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago)
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability prob

[Touch-packages] [Bug 1749389] [NEW] ntpdate lock apparmor deny

[ChristianEhrhardt]

Public bug reported:

[Impact]

 * Apparmor denies access to lock it shares with ntpdate to ensure no 
   issues due to concurrent access

[Test Case]

 1. get a container of target release
 2. install ntp
apt install ntp
 3. watch dmesg on container-host
dmesg -w 
 4. restart ntp in container
systemctl restart ntp
 => see (or no more after fix) apparmor denie:
apparmor="DENIED" operation="file_inherit" profile="/usr/sbin/ntpd" 
name="/run/lock/ntpdate" pid=30113 comm="ntpd" requested_mask="w" 
denied_mask="w"

[Regression Potential]

 * we are only slightly opening up the apparmor profile, but none of the 
   changes poses a security risk so regression potential on it's own 
   should be close to zero.

 * There is a potential issue if the locking (that now can succeed) would 
   e.g. no more be freed up or the action behind the locking would cause 
   issues.

[Other Info]
 
 * n/a


On start/restart nto has an error in apparmor due to the locking it tries to 
avoid issues running concurrently with ntpdate.

That looks like:
apparmor="DENIED" operation="file_inherit" profile="/usr/sbin/ntpd" 
name="/run/lock/ntpdate" pid=30113 comm="ntpd" requested_mask="w" 
denied_mask="w"

The rule we need is:
/run/lock/ntpdate wk,

** Affects: ntp (Ubuntu)
 Importance: Medium
 Status: Triaged

** Affects: ntp (Ubuntu Xenial)
 Importance: Medium
 Status: Triaged

** Affects: ntp (Ubuntu Artful)
 Importance: Medium
 Status: Triaged

** Also affects: ntp (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Also affects: ntp (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

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

** Changed in: ntp (Ubuntu Xenial)
   Importance: Undecided => Medium

** Changed in: ntp (Ubuntu Artful)
   Importance: Undecided => Medium

** Changed in: ntp (Ubuntu)
   Importance: Undecided => Medium

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

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

Title:
  ntpdate lock apparmor deny

Status in ntp package in Ubuntu:
  Triaged
Status in ntp source package in Xenial:
  Triaged
Status in ntp source package in Artful:
  Triaged

Bug description:
  [Impact]

   * Apparmor denies access to lock it shares with ntpdate to ensure no 
 issues due to concurrent access

  [Test Case]

   1. get a container of target release
   2. install ntp
  apt install ntp
   3. watch dmesg on container-host
  dmesg -w 
   4. restart ntp in container
  systemctl restart ntp
   => see (or no more after fix) apparmor denie:
  apparmor="DENIED" operation="file_inherit" profile="/usr/sbin/ntpd" 
name="/run/lock/ntpdate" pid=30113 comm="ntpd" requested_mask="w" 
denied_mask="w"

  [Regression Potential]

   * we are only slightly opening up the apparmor profile, but none of the 
 changes poses a security risk so regression potential on it's own 
 should be close to zero.

   * There is a potential issue if the locking (that now can succeed) would 
 e.g. no more be freed up or the action behind the locking would cause 
 issues.

  [Other Info]
   
   * n/a

  
  On start/restart nto has an error in apparmor due to the locking it tries to 
avoid issues running concurrently with ntpdate.

  That looks like:
  apparmor="DENIED" operation="file_inherit" profile="/usr/sbin/ntpd" 
name="/run/lock/ntpdate" pid=30113 comm="ntpd" requested_mask="w" 
denied_mask="w"

  The rule we need is:
  /run/lock/ntpdate wk,

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1749389/+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 1741227] Re: apparmor denial to several paths to binaries

[ChristianEhrhardt]

I looked a bit around and found another apparmor change which I think
will open up a reasonable SRU for ntp on apparmor. And while we do it
anyway we can also add this rule.

So this now depends on bug 1749389 completing in Bionic and then can be
made one SRU together.

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

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

** Changed in: ntp (Ubuntu Xenial)
   Importance: Undecided => Low

** Changed in: ntp (Ubuntu Artful)
   Importance: Undecided => Low

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

Title:
  apparmor denial to several paths to binaries

Status in ntp package in Ubuntu:
  Fix Released
Status in ntp source package in Xenial:
  Triaged
Status in ntp source package in Artful:
  Triaged

Bug description:
  [Impact]

   * Apparmor denies access to bin directories which the option parsing code 
 of ntp touches.

  [Test Case]

   1. get a container of target release
   2. install ntp
  apt install ntp
   3. watch dmesg on container-host
  dmesg -w
   4. restart ntp in container
  systemctl restart ntp
   => see (or no more after fix) apparmor denie:
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/sbin/" pid=23933 comm="ntpd" requested_mask="r" denied_mask="r"
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/bin/" pid=23933 comm="ntpd" requested_mask="r" denied_mask="r"

  [Regression Potential]

   * we are only slightly opening up the apparmor profile, but none of the
 changes poses a security risk so regression potential on it's own
 should be close to zero.

   * we discussed if this would be a security risk but came to the 
 conclusion that r-only should be ok (the same content anyone can grab 
 from the archive by installing the packages)

  [Other Info]

   * n/a

  Issue shows up (non fatal) as:
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/sbin/" pid=23933 comm="ntpd" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/bin/" pid=23933 comm="ntpd" requested_mask="r" denied_mask="r" 
fsuid=0 ouid=0

  Since non crit this is mostyl about many of us being curious why it
  actually does do it :-)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1741227/+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 1741227] Re: apparmor denial to several paths to binaries

[ChristianEhrhardt]

Hi Tony,
yeah this is so far only fixed in Bionic (18.04) onwards.
It it not really an issue other than a log message itself (it is not needed for 
the opt parsing).
It occurs "only" on NTP start/restart (since it is arg parsing) so it is not 
that frequent that it would fill up the log or similar secondary issues.

All that makes it a hard case for the SRU policy [1] to make this change in 
releases.
Until then everybody who bothers about the log message can add:
   /usr/local/{,s}bin/  r,
to
   /etc/apparmor.d/usr.sbin.ntpd

I'm adding X/A bug tasks and set won't fix to mark that more explicitly.

I'm happy to discuss if one thinks this case would qualify fot the SRU
policy - the change itself is easy enough to be done.

[1]: https://wiki.ubuntu.com/StableReleaseUpdates

** Also affects: ntp (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: ntp (Ubuntu Artful)
   Importance: Undecided
   Status: New

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

Title:
  apparmor denial to several paths to binaries

Status in ntp package in Ubuntu:
  Fix Released
Status in ntp source package in Xenial:
  Triaged
Status in ntp source package in Artful:
  Triaged

Bug description:
  [Impact]

   * Apparmor denies access to bin directories which the option parsing code 
 of ntp touches.

  [Test Case]

   1. get a container of target release
   2. install ntp
  apt install ntp
   3. watch dmesg on container-host
  dmesg -w
   4. restart ntp in container
  systemctl restart ntp
   => see (or no more after fix) apparmor denie:
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/sbin/" pid=23933 comm="ntpd" requested_mask="r" denied_mask="r"
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/bin/" pid=23933 comm="ntpd" requested_mask="r" denied_mask="r"

  [Regression Potential]

   * we are only slightly opening up the apparmor profile, but none of the
 changes poses a security risk so regression potential on it's own
 should be close to zero.

   * we discussed if this would be a security risk but came to the 
 conclusion that r-only should be ok (the same content anyone can grab 
 from the archive by installing the packages)

  [Other Info]

   * n/a

  Issue shows up (non fatal) as:
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/sbin/" pid=23933 comm="ntpd" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/bin/" pid=23933 comm="ntpd" requested_mask="r" denied_mask="r" 
fsuid=0 ouid=0

  Since non crit this is mostyl about many of us being curious why it
  actually does do it :-)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1741227/+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 1506612] Re: pdfimages extracts black rectangles instead of the images

[madbiologist]

** Tags added: bionic

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

Title:
  pdfimages extracts black rectangles instead of the images

Status in poppler package in Ubuntu:
  Confirmed

Bug description:
  When I run pdfimages -f 1 -l 1 -png Z.pdf z-pdfimages, I get 5 images,
  two of which are black rectangles.

  If I run pdftocairo -png Z.pdf z-pdftocairo, I get one image that
  looks correct.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: poppler-utils 0.30.0-0ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-31.36-generic 3.19.8-ckt7
  Uname: Linux 3.19.0-31-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.2-0ubuntu1.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Oct 15 12:36:10 2015
  InstallationDate: Installed on 2013-05-02 (896 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: poppler
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1506612/+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 1741227] Re: apparmor denial to several paths to binaries

[ChristianEhrhardt]

** Description changed:

+ [Impact]
+ 
+  * Apparmor denies access to bin directories which the option parsing code 
+of ntp touches.
+ 
+ [Test Case]
+ 
+  1. get a container of target release
+  2. install ntp
+ apt install ntp
+  3. watch dmesg on container-host
+ dmesg -w
+  4. restart ntp in container
+ systemctl restart ntp
+  => see (or no more after fix) apparmor denie:
+  apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/sbin/" pid=23933 comm="ntpd" requested_mask="r" denied_mask="r"
+  apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/bin/" pid=23933 comm="ntpd" requested_mask="r" denied_mask="r"
+ 
+ [Regression Potential]
+ 
+  * we are only slightly opening up the apparmor profile, but none of the
+changes poses a security risk so regression potential on it's own
+should be close to zero.
+ 
+  * we discussed if this would be a security risk but came to the 
+conclusion that r-only should be ok (the same content anyone can grab 
+from the archive by installing the packages)
+ 
+ [Other Info]
+ 
+  * n/a
+ 
  Issue shows up (non fatal) as:
-  apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/sbin/" pid=23933 comm="ntpd" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
-  apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/bin/" pid=23933 comm="ntpd" requested_mask="r" denied_mask="r" 
fsuid=0 ouid=0
+  apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/sbin/" pid=23933 comm="ntpd" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
+  apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/bin/" pid=23933 comm="ntpd" requested_mask="r" denied_mask="r" 
fsuid=0 ouid=0
  
  Since non crit this is mostyl about many of us being curious why it
  actually does do it :-)

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

Title:
  apparmor denial to several paths to binaries

Status in ntp package in Ubuntu:
  Fix Released
Status in ntp source package in Xenial:
  Triaged
Status in ntp source package in Artful:
  Triaged

Bug description:
  [Impact]

   * Apparmor denies access to bin directories which the option parsing code 
 of ntp touches.

  [Test Case]

   1. get a container of target release
   2. install ntp
  apt install ntp
   3. watch dmesg on container-host
  dmesg -w
   4. restart ntp in container
  systemctl restart ntp
   => see (or no more after fix) apparmor denie:
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/sbin/" pid=23933 comm="ntpd" requested_mask="r" denied_mask="r"
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/bin/" pid=23933 comm="ntpd" requested_mask="r" denied_mask="r"

  [Regression Potential]

   * we are only slightly opening up the apparmor profile, but none of the
 changes poses a security risk so regression potential on it's own
 should be close to zero.

   * we discussed if this would be a security risk but came to the 
 conclusion that r-only should be ok (the same content anyone can grab 
 from the archive by installing the packages)

  [Other Info]

   * n/a

  Issue shows up (non fatal) as:
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/sbin/" pid=23933 comm="ntpd" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/bin/" pid=23933 comm="ntpd" requested_mask="r" denied_mask="r" 
fsuid=0 ouid=0

  Since non crit this is mostyl about many of us being curious why it
  actually does do it :-)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1741227/+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 1749389] Re: ntpdate lock apparmor deny

[ChristianEhrhardt]

Note: When we open up a SRU for ntp apparmor we should include the minot
(bot on its own not SRu worthy) fix of bug 1741227

** Description changed:

- On start/restart nto has an error in apparmor due to the locking it
- tries to avoid issues running concurrently with ntpdate.
+ [Impact]
+ 
+  * Apparmor denies access to lock it shares with ntpdate to ensure no 
+issues due to concurrent access
+ 
+ [Test Case]
+ 
+  1. get a container of target release
+  2. install ntp
+ apt install ntp
+  3. watch dmesg on container-host
+ dmesg -w 
+  4. restart ntp in container
+ systemctl restart ntp
+  => see (or no more after fix) apparmor denie:
+ apparmor="DENIED" operation="file_inherit" profile="/usr/sbin/ntpd" 
name="/run/lock/ntpdate" pid=30113 comm="ntpd" requested_mask="w" 
denied_mask="w"
+ 
+ [Regression Potential]
+ 
+  * we are only slightly opening up the apparmor profile, but none of the 
+changes poses a security risk so regression potential on it's own 
+should be close to zero.
+ 
+  * There is a potential issue if the locking (that now can succeed) would 
+e.g. no more be freed up or the action behind the locking would cause 
+issues.
+ 
+ [Other Info]
+  
+  * n/a
+ 
+ 
+ On start/restart nto has an error in apparmor due to the locking it tries to 
avoid issues running concurrently with ntpdate.
  
  That looks like:
  apparmor="DENIED" operation="file_inherit" profile="/usr/sbin/ntpd" 
name="/run/lock/ntpdate" pid=30113 comm="ntpd" requested_mask="w" 
denied_mask="w"
  
  The rule we need is:
  /run/lock/ntpdate wk,

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

Title:
  ntpdate lock apparmor deny

Status in ntp package in Ubuntu:
  Triaged
Status in ntp source package in Xenial:
  Triaged
Status in ntp source package in Artful:
  Triaged

Bug description:
  [Impact]

   * Apparmor denies access to lock it shares with ntpdate to ensure no 
 issues due to concurrent access

  [Test Case]

   1. get a container of target release
   2. install ntp
  apt install ntp
   3. watch dmesg on container-host
  dmesg -w 
   4. restart ntp in container
  systemctl restart ntp
   => see (or no more after fix) apparmor denie:
  apparmor="DENIED" operation="file_inherit" profile="/usr/sbin/ntpd" 
name="/run/lock/ntpdate" pid=30113 comm="ntpd" requested_mask="w" 
denied_mask="w"

  [Regression Potential]

   * we are only slightly opening up the apparmor profile, but none of the 
 changes poses a security risk so regression potential on it's own 
 should be close to zero.

   * There is a potential issue if the locking (that now can succeed) would 
 e.g. no more be freed up or the action behind the locking would cause 
 issues.

  [Other Info]
   
   * n/a

  
  On start/restart nto has an error in apparmor due to the locking it tries to 
avoid issues running concurrently with ntpdate.

  That looks like:
  apparmor="DENIED" operation="file_inherit" profile="/usr/sbin/ntpd" 
name="/run/lock/ntpdate" pid=30113 comm="ntpd" requested_mask="w" 
denied_mask="w"

  The rule we need is:
  /run/lock/ntpdate wk,

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1749389/+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 1749389] Re: ntpdate lock apparmor deny

[ChristianEhrhardt]

Fix is trivial, but you never know - tetsing the bionic change in
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3144

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

Title:
  ntpdate lock apparmor deny

Status in ntp package in Ubuntu:
  Triaged
Status in ntp source package in Xenial:
  Triaged
Status in ntp source package in Artful:
  Triaged

Bug description:
  [Impact]

   * Apparmor denies access to lock it shares with ntpdate to ensure no 
 issues due to concurrent access

  [Test Case]

   1. get a container of target release
   2. install ntp
  apt install ntp
   3. watch dmesg on container-host
  dmesg -w 
   4. restart ntp in container
  systemctl restart ntp
   => see (or no more after fix) apparmor denie:
  apparmor="DENIED" operation="file_inherit" profile="/usr/sbin/ntpd" 
name="/run/lock/ntpdate" pid=30113 comm="ntpd" requested_mask="w" 
denied_mask="w"

  [Regression Potential]

   * we are only slightly opening up the apparmor profile, but none of the 
 changes poses a security risk so regression potential on it's own 
 should be close to zero.

   * There is a potential issue if the locking (that now can succeed) would 
 e.g. no more be freed up or the action behind the locking would cause 
 issues.

  [Other Info]
   
   * n/a

  
  On start/restart nto has an error in apparmor due to the locking it tries to 
avoid issues running concurrently with ntpdate.

  That looks like:
  apparmor="DENIED" operation="file_inherit" profile="/usr/sbin/ntpd" 
name="/run/lock/ntpdate" pid=30113 comm="ntpd" requested_mask="w" 
denied_mask="w"

  The rule we need is:
  /run/lock/ntpdate wk,

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1749389/+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 1741189] Re: New bugfix release 17.2.8

[Launchpad Bug Tracker]

This bug was fixed in the package mesa - 17.2.8-0ubuntu0~16.04.1

---
mesa (17.2.8-0ubuntu0~16.04.1) xenial; urgency=medium

  * New upstream bugfix release. (LP: #1741189)

 -- Timo Aaltonen   Thu, 18 Jan 2018 16:19:31 +0200

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

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

Title:
  New bugfix release 17.2.8

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

Bug description:
  [Impact]

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

  Mesa 17.2.5 is now available.

  In this release we have:

  In Mesa Core a GL error related to the ARB_ES3_1_compatibility spec
  noticed with the GFXBench 5 Aztec Ruins has been corrected. 

  The GLSL compiler is not giving a linker error for mismatching uniform
  precision with GLSL ES 1.00 any more. This enables, specially, several
  Android applications which violate this rule, like Forge of Empires,
  for example.

  The SPIR-V compiler has corrected an assert triggered when support for
  the simple memory model was claimed.

  NIR has also received a correction related with
  gl_SubGroupG{e,t}MaskARB.

  The Intel drivers, specially i965, have received several fixes,
  including a plug for a memory leak and another one in the compiler to
  avoid GPU hangs on Broxton.

  The gallium i915g driver for Intel has also seen an important
  correction.

  AMD drivers, mostly radv, have also received several fixes, including a
  correction for a DCC corruption that was visible with Rust, breaking an
  endless loop in r600, avoiding a GPU hang with vulkan dota2 in VR mode
  and a plug for a memory leak.

  Broadcom's vc4 has gotten a fix to compile out some non-debug code that
  shouldn't be there for the release build.

  

  Mesa 17.2.6 is now available.

  In this release we have:

  In Mesa Core we have included a correction to keep a program alive when
  re-linking and prevent an use-after-free.

  The GLSL compiler has received several fixes, including one to prevent
  a SIGSEV when calling an undeclared subroutine in certain conditions
  and another to mark the xfb buffers as active only if a variable uses
  them.

  The SPIR-V compiler has corrected a couple of issues involving the
  usage of separate images and texture/samplers.

  The Intel drivers include many new fixes, specially for i965. Several 
  are focused on improving SIMD32 and little-core. It also includes a fix
  for a GPU hang which was detected while playing HW accelerated video
  with mpv.

  The AMD drivers have also received some care. radv has seen plugged 2
  memory leaks while r600 has gotten a fix through reversing the tess
  factor components for isolines.

  The swr driver has corrected two performance regressions, one for the
  avx512 platforms and the other for the avx/avx2 platforms.

  In the ddebug gallium driver we have a fix for an use-after-free.

  On the EGL side, the Wayland platform of the the DRI2 drivers has
  received a fix to prevent crashing in ancient systems.

  GLX has also received corrections to prevent a couple of errors when
  creating and binding a context in DRI3 and DRISW, respectively.

  From build and integration point of view, we have added some few more
  fixes, including one to allow building libglvnd when EGL is present but
  not GLX, another to enable building targets which don't need X11, such
  as omx and va, when XCB is not present, and another one to be able to
  specify the prefix installation for the OpenCL icd file.

  

  Mesa 17.2.7 is now available.

  In this release we have:

  The current queue consists of a variety of fixes, with a sizeable hunk in the
  shared GLSL codebase.

  Whereas for individual drivers - i965 has a crash fix for when playing various
  Valve games, r600 and nouveau have tweaks in their compiler backends. Fast
  clears on radeonsi and RADV are better now, while the VAAPI encoding is 
playing
  nicely with GStreamer.

  The WGL state tracker and SWR driver have also seen minor
  improvements.

  To top of up - Mesa should build fine with the latest glibc 2.17.

  

  Mesa 17.2.8 is now available.

  In this release we have:

  The SPIR-V compiler has seen corrected a possible SEGFAULT.

  The Intel i965 driver includes a correction for Haswell involving
  doubles management. 

  The AMD drivers have also received some fixes. A couple have gone for
  radv and radeon's VCE while r600 has seen corrected some glitches
  detected with This War of Mine.

  Gallium has also received a patch fixing a problem affecting the VMware
  driver and the st/nine state tracker.

  The endianness detection in Windows platform has been corrected to
  default to littl

[Touch-packages] [Bug 1749398] [NEW] Update libva: 2.0.0 --> 2.1.1 before release 18.04 bionic

[Mikhail N]

Public bug reported:

Libva 2.1.0 has been released: https://github.com/intel/libva/releases

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libva2 2.0.0-2
Uname: Linux 4.14.0-18.2-liquorix-amd64 x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
Date: Wed Feb 14 11:46:06 2018
InstallationDate: Installed on 2017-08-28 (169 days ago)
InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
SourcePackage: libva
UpgradeStatus: Upgraded to bionic on 2018-02-08 (5 days ago)

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


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

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

Title:
  Update libva: 2.0.0 --> 2.1.1 before release 18.04 bionic

Status in libva package in Ubuntu:
  New

Bug description:
  Libva 2.1.0 has been released: https://github.com/intel/libva/releases

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libva2 2.0.0-2
  Uname: Linux 4.14.0-18.2-liquorix-amd64 x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Wed Feb 14 11:46:06 2018
  InstallationDate: Installed on 2017-08-28 (169 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: libva
  UpgradeStatus: Upgraded to bionic on 2018-02-08 (5 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libva/+bug/1749398/+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 1749247] [NEW] Spurious SEGV running inside kvm

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

Running a continuous stream of operations against OpenLDAP slapd
eventually causes a SEGV in liblber, in a segment of code that cannot
fail:

 gdb /opt/symas/lib64/slapd CoreDump 
GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.5) 7.11.1
Copyright (C) 2016 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /opt/symas/lib64/slapd...done.
[New LWP 5472]
[New LWP 5468]
[New LWP 5524]
[New LWP 5471]
[New LWP 5469]
[New LWP 5507]
[New LWP 5510]
[New LWP 5470]
[New LWP 5506]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/opt/symas/lib64/slapd -u root -g root -h ldap:///'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x7f4e2c9f0160 in ber_dupbv_x (dst=0x196b268, src=0x7f25f8001070, 
ctx=0x0) at /home/build/git/sold-master/openldap/libraries/liblber/memory.c:513
513 new->bv_val[src->bv_len] = '\0';
[Current thread is 1 (Thread 0x7f260e242700 (LWP 5472))]
(gdb) l 500
495 if(( new = ber_memalloc_x( sizeof(struct berval), ctx 
)) == NULL ) {
496 return NULL;
497 }
498 }
499
500 if ( src->bv_val == NULL ) {
501 new->bv_val = NULL;
502 new->bv_len = 0;
503 return new;
504 }
(gdb) 
505
506 if(( new->bv_val = ber_memalloc_x( src->bv_len + 1, ctx )) == 
NULL ) {
507 if ( !dst )
508 ber_memfree_x( new, ctx );
509 return NULL;
510 }
511
512 AC_MEMCPY( new->bv_val, src->bv_val, src->bv_len );
513 new->bv_val[src->bv_len] = '\0';
514 new->bv_len = src->bv_len;
(gdb) p *new
$1 = {bv_len = 0, bv_val = 0x0}
(gdb) p *src
$2 = {bv_len = 36, bv_val = 0x7f268ccc7bee }
(gdb) 


At line 506 we allocate some memory and check for a failure (returning NULL) 
and leave the function at line 509 if there was a failure. The allocation is 
for 37 bytes of memory and a memcpy into that memory succeeds on line 512. The 
SEGV occurs at line 513 and the pointer that was just returned from the 
allocator is NULL at this point. There are no other active threads that could 
be stomping on memory, there's no stack overrun or any other misbehavior that 
can account for it. Also, the identical test sequence completes without 
incident when running on the host OS instead of under kvm.
(The src->bv_val pointer points to valid data at the time of the crash; it's 
just residing in a mmap'd file and that mapping isn't preserved in the 
coredump. So ignore gdb's error there.)

Something in kvm is writing zeroes over a field of memory after we
already checked that it was non-zero.

This is on 
Linux anvil1 4.4.0-112-generic #135-Ubuntu SMP Fri Jan 19 11:48:36 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

Both the host and the guest VM are on identical OS revision.

** Affects: openldap (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: bot-comment
-- 
Spurious SEGV running inside kvm
https://bugs.launchpad.net/bugs/1749247
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to openldap in Ubuntu.

-- 
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 1624644] Re: By default settings unattended-upgrade does not automatically remove packages that become unused in conjunction with updating by other software

[Balint Reczey]

** Changed in: unattended-upgrades (Ubuntu)
   Status: Opinion => In Progress

** Changed in: unattended-upgrades (Ubuntu Artful)
   Status: Opinion => In Progress

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

Title:
  By default settings unattended-upgrade does not automatically remove
  packages that become unused in conjunction with updating by other
  software

Status in apt package in Ubuntu:
  Confirmed
Status in gnome-software package in Ubuntu:
  Invalid
Status in unattended-upgrades package in Ubuntu:
  In Progress
Status in update-manager package in Ubuntu:
  In Progress
Status in apt source package in Artful:
  Confirmed
Status in gnome-software source package in Artful:
  Invalid
Status in unattended-upgrades source package in Artful:
  In Progress
Status in update-manager source package in Artful:
  In Progress

Bug description:
  When using default settings for unattended-upgrade i.e.
  Unattended-Upgrade::Remove-Unused-Dependencies "false";
  # default "false"
  Unattended-Upgrade::Remove-New-Unused-Dependencies "true";
  # default "true"
  in configuration file /etc/apt/apt.conf.d/50unattended-upgrades,
  unattended-upgrade is unable to remove packages that become unused in 
conjunction with updating by other software such as update-manager or apt 
full-upgrade. This is because unattended-upgrade compares the list of unneeded 
packages before and after it upgrades packages to detect which packages are new 
unused ones.

  Consequently, if user installs new kernels using e.g. update-manager,
  the excessive kernels will not be removed by unattended-upgrade, and
  eventually (small) /boot will become full.

  Expected behavior: handle removing of unused packages differently at
  least until other package management software installed by default can
  handle removing of new unused packages.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Sat Sep 17 11:28:44 2016
  InstallationDate: Installed on 2016-09-05 (11 days ago)
  InstallationMedia: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160719)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1624644/+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 1749247] Re: Spurious SEGV running inside kvm

[ChristianEhrhardt]

slapd is part of the openldap package - assigning this makes more sense
I think.

** Package changed: kvm (Ubuntu) => openldap (Ubuntu)

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

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

Title:
  Spurious SEGV running inside kvm

Status in openldap package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Incomplete

Bug description:
  Running a continuous stream of operations against OpenLDAP slapd
  eventually causes a SEGV in liblber, in a segment of code that cannot
  fail:

   gdb /opt/symas/lib64/slapd CoreDump 
  GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.5) 7.11.1
  Copyright (C) 2016 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .
  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from /opt/symas/lib64/slapd...done.
  [New LWP 5472]
  [New LWP 5468]
  [New LWP 5524]
  [New LWP 5471]
  [New LWP 5469]
  [New LWP 5507]
  [New LWP 5510]
  [New LWP 5470]
  [New LWP 5506]
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  Core was generated by `/opt/symas/lib64/slapd -u root -g root -h ldap:///'.
  Program terminated with signal SIGSEGV, Segmentation fault.
  #0  0x7f4e2c9f0160 in ber_dupbv_x (dst=0x196b268, src=0x7f25f8001070, 
ctx=0x0) at /home/build/git/sold-master/openldap/libraries/liblber/memory.c:513
  513 new->bv_val[src->bv_len] = '\0';
  [Current thread is 1 (Thread 0x7f260e242700 (LWP 5472))]
  (gdb) l 500
  495 if(( new = ber_memalloc_x( sizeof(struct berval), ctx 
)) == NULL ) {
  496 return NULL;
  497 }
  498 }
  499
  500 if ( src->bv_val == NULL ) {
  501 new->bv_val = NULL;
  502 new->bv_len = 0;
  503 return new;
  504 }
  (gdb) 
  505
  506 if(( new->bv_val = ber_memalloc_x( src->bv_len + 1, ctx )) == 
NULL ) {
  507 if ( !dst )
  508 ber_memfree_x( new, ctx );
  509 return NULL;
  510 }
  511
  512 AC_MEMCPY( new->bv_val, src->bv_val, src->bv_len );
  513 new->bv_val[src->bv_len] = '\0';
  514 new->bv_len = src->bv_len;
  (gdb) p *new
  $1 = {bv_len = 0, bv_val = 0x0}
  (gdb) p *src
  $2 = {bv_len = 36, bv_val = 0x7f268ccc7bee }
  (gdb) 

  
  At line 506 we allocate some memory and check for a failure (returning NULL) 
and leave the function at line 509 if there was a failure. The allocation is 
for 37 bytes of memory and a memcpy into that memory succeeds on line 512. The 
SEGV occurs at line 513 and the pointer that was just returned from the 
allocator is NULL at this point. There are no other active threads that could 
be stomping on memory, there's no stack overrun or any other misbehavior that 
can account for it. Also, the identical test sequence completes without 
incident when running on the host OS instead of under kvm.
  (The src->bv_val pointer points to valid data at the time of the crash; it's 
just residing in a mmap'd file and that mapping isn't preserved in the 
coredump. So ignore gdb's error there.)

  Something in kvm is writing zeroes over a field of memory after we
  already checked that it was non-zero.

  This is on 
  Linux anvil1 4.4.0-112-generic #135-Ubuntu SMP Fri Jan 19 11:48:36 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Both the host and the guest VM are on identical OS revision.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1749247/+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 1749247] Re: Spurious SEGV running inside kvm

[ChristianEhrhardt]

Setting qemu(Ubuntu) which is the right package for the question of "the
identical test sequence completes without incident when running on the
host OS instead of under kvm".

Although that could just be timing and doesn't "have to be" a kvm memory
clobbering.

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

Title:
  Spurious SEGV running inside kvm

Status in openldap package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Incomplete

Bug description:
  Running a continuous stream of operations against OpenLDAP slapd
  eventually causes a SEGV in liblber, in a segment of code that cannot
  fail:

   gdb /opt/symas/lib64/slapd CoreDump 
  GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.5) 7.11.1
  Copyright (C) 2016 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .
  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from /opt/symas/lib64/slapd...done.
  [New LWP 5472]
  [New LWP 5468]
  [New LWP 5524]
  [New LWP 5471]
  [New LWP 5469]
  [New LWP 5507]
  [New LWP 5510]
  [New LWP 5470]
  [New LWP 5506]
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  Core was generated by `/opt/symas/lib64/slapd -u root -g root -h ldap:///'.
  Program terminated with signal SIGSEGV, Segmentation fault.
  #0  0x7f4e2c9f0160 in ber_dupbv_x (dst=0x196b268, src=0x7f25f8001070, 
ctx=0x0) at /home/build/git/sold-master/openldap/libraries/liblber/memory.c:513
  513 new->bv_val[src->bv_len] = '\0';
  [Current thread is 1 (Thread 0x7f260e242700 (LWP 5472))]
  (gdb) l 500
  495 if(( new = ber_memalloc_x( sizeof(struct berval), ctx 
)) == NULL ) {
  496 return NULL;
  497 }
  498 }
  499
  500 if ( src->bv_val == NULL ) {
  501 new->bv_val = NULL;
  502 new->bv_len = 0;
  503 return new;
  504 }
  (gdb) 
  505
  506 if(( new->bv_val = ber_memalloc_x( src->bv_len + 1, ctx )) == 
NULL ) {
  507 if ( !dst )
  508 ber_memfree_x( new, ctx );
  509 return NULL;
  510 }
  511
  512 AC_MEMCPY( new->bv_val, src->bv_val, src->bv_len );
  513 new->bv_val[src->bv_len] = '\0';
  514 new->bv_len = src->bv_len;
  (gdb) p *new
  $1 = {bv_len = 0, bv_val = 0x0}
  (gdb) p *src
  $2 = {bv_len = 36, bv_val = 0x7f268ccc7bee }
  (gdb) 

  
  At line 506 we allocate some memory and check for a failure (returning NULL) 
and leave the function at line 509 if there was a failure. The allocation is 
for 37 bytes of memory and a memcpy into that memory succeeds on line 512. The 
SEGV occurs at line 513 and the pointer that was just returned from the 
allocator is NULL at this point. There are no other active threads that could 
be stomping on memory, there's no stack overrun or any other misbehavior that 
can account for it. Also, the identical test sequence completes without 
incident when running on the host OS instead of under kvm.
  (The src->bv_val pointer points to valid data at the time of the crash; it's 
just residing in a mmap'd file and that mapping isn't preserved in the 
coredump. So ignore gdb's error there.)

  Something in kvm is writing zeroes over a field of memory after we
  already checked that it was non-zero.

  This is on 
  Linux anvil1 4.4.0-112-generic #135-Ubuntu SMP Fri Jan 19 11:48:36 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Both the host and the guest VM are on identical OS revision.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1749247/+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 1749247] Re: Spurious SEGV running inside kvm

[ChristianEhrhardt]

How reproducible is this - everytime or just once in a number of retry loops?
Could you share the minimal simplified setup+loop code to retrigger this over 
here?


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

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

Title:
  Spurious SEGV running inside kvm

Status in openldap package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Incomplete

Bug description:
  Running a continuous stream of operations against OpenLDAP slapd
  eventually causes a SEGV in liblber, in a segment of code that cannot
  fail:

   gdb /opt/symas/lib64/slapd CoreDump 
  GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.5) 7.11.1
  Copyright (C) 2016 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .
  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from /opt/symas/lib64/slapd...done.
  [New LWP 5472]
  [New LWP 5468]
  [New LWP 5524]
  [New LWP 5471]
  [New LWP 5469]
  [New LWP 5507]
  [New LWP 5510]
  [New LWP 5470]
  [New LWP 5506]
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  Core was generated by `/opt/symas/lib64/slapd -u root -g root -h ldap:///'.
  Program terminated with signal SIGSEGV, Segmentation fault.
  #0  0x7f4e2c9f0160 in ber_dupbv_x (dst=0x196b268, src=0x7f25f8001070, 
ctx=0x0) at /home/build/git/sold-master/openldap/libraries/liblber/memory.c:513
  513 new->bv_val[src->bv_len] = '\0';
  [Current thread is 1 (Thread 0x7f260e242700 (LWP 5472))]
  (gdb) l 500
  495 if(( new = ber_memalloc_x( sizeof(struct berval), ctx 
)) == NULL ) {
  496 return NULL;
  497 }
  498 }
  499
  500 if ( src->bv_val == NULL ) {
  501 new->bv_val = NULL;
  502 new->bv_len = 0;
  503 return new;
  504 }
  (gdb) 
  505
  506 if(( new->bv_val = ber_memalloc_x( src->bv_len + 1, ctx )) == 
NULL ) {
  507 if ( !dst )
  508 ber_memfree_x( new, ctx );
  509 return NULL;
  510 }
  511
  512 AC_MEMCPY( new->bv_val, src->bv_val, src->bv_len );
  513 new->bv_val[src->bv_len] = '\0';
  514 new->bv_len = src->bv_len;
  (gdb) p *new
  $1 = {bv_len = 0, bv_val = 0x0}
  (gdb) p *src
  $2 = {bv_len = 36, bv_val = 0x7f268ccc7bee }
  (gdb) 

  
  At line 506 we allocate some memory and check for a failure (returning NULL) 
and leave the function at line 509 if there was a failure. The allocation is 
for 37 bytes of memory and a memcpy into that memory succeeds on line 512. The 
SEGV occurs at line 513 and the pointer that was just returned from the 
allocator is NULL at this point. There are no other active threads that could 
be stomping on memory, there's no stack overrun or any other misbehavior that 
can account for it. Also, the identical test sequence completes without 
incident when running on the host OS instead of under kvm.
  (The src->bv_val pointer points to valid data at the time of the crash; it's 
just residing in a mmap'd file and that mapping isn't preserved in the 
coredump. So ignore gdb's error there.)

  Something in kvm is writing zeroes over a field of memory after we
  already checked that it was non-zero.

  This is on 
  Linux anvil1 4.4.0-112-generic #135-Ubuntu SMP Fri Jan 19 11:48:36 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Both the host and the guest VM are on identical OS revision.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1749247/+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 1749247] Re: Spurious SEGV running inside kvm

[ChristianEhrhardt]

Eventually as you already found the question is how did bv_val get 0x0?

If the test can't be passed to me, but is reproducible, could you try to step 
live from line 506.
1. is new->bv_val really assigned some pointer (and which one)
2. when does that pointer get lost between 506 and 513

Also the memcopy seems to work (no crash on that line).
If you can modify and retest you could take a look to check if AC_MEMCPY in 
your case actually is memmove, bcopy or memcpy - maybe even iterate between 
those to be sure.

All of the copies return a pointer to dest which should still be what
was assigned to new->bv_val, so is it still the same or did it return
something else?

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

Title:
  Spurious SEGV running inside kvm

Status in openldap package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Incomplete

Bug description:
  Running a continuous stream of operations against OpenLDAP slapd
  eventually causes a SEGV in liblber, in a segment of code that cannot
  fail:

   gdb /opt/symas/lib64/slapd CoreDump 
  GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.5) 7.11.1
  Copyright (C) 2016 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .
  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from /opt/symas/lib64/slapd...done.
  [New LWP 5472]
  [New LWP 5468]
  [New LWP 5524]
  [New LWP 5471]
  [New LWP 5469]
  [New LWP 5507]
  [New LWP 5510]
  [New LWP 5470]
  [New LWP 5506]
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  Core was generated by `/opt/symas/lib64/slapd -u root -g root -h ldap:///'.
  Program terminated with signal SIGSEGV, Segmentation fault.
  #0  0x7f4e2c9f0160 in ber_dupbv_x (dst=0x196b268, src=0x7f25f8001070, 
ctx=0x0) at /home/build/git/sold-master/openldap/libraries/liblber/memory.c:513
  513 new->bv_val[src->bv_len] = '\0';
  [Current thread is 1 (Thread 0x7f260e242700 (LWP 5472))]
  (gdb) l 500
  495 if(( new = ber_memalloc_x( sizeof(struct berval), ctx 
)) == NULL ) {
  496 return NULL;
  497 }
  498 }
  499
  500 if ( src->bv_val == NULL ) {
  501 new->bv_val = NULL;
  502 new->bv_len = 0;
  503 return new;
  504 }
  (gdb) 
  505
  506 if(( new->bv_val = ber_memalloc_x( src->bv_len + 1, ctx )) == 
NULL ) {
  507 if ( !dst )
  508 ber_memfree_x( new, ctx );
  509 return NULL;
  510 }
  511
  512 AC_MEMCPY( new->bv_val, src->bv_val, src->bv_len );
  513 new->bv_val[src->bv_len] = '\0';
  514 new->bv_len = src->bv_len;
  (gdb) p *new
  $1 = {bv_len = 0, bv_val = 0x0}
  (gdb) p *src
  $2 = {bv_len = 36, bv_val = 0x7f268ccc7bee }
  (gdb) 

  
  At line 506 we allocate some memory and check for a failure (returning NULL) 
and leave the function at line 509 if there was a failure. The allocation is 
for 37 bytes of memory and a memcpy into that memory succeeds on line 512. The 
SEGV occurs at line 513 and the pointer that was just returned from the 
allocator is NULL at this point. There are no other active threads that could 
be stomping on memory, there's no stack overrun or any other misbehavior that 
can account for it. Also, the identical test sequence completes without 
incident when running on the host OS instead of under kvm.
  (The src->bv_val pointer points to valid data at the time of the crash; it's 
just residing in a mmap'd file and that mapping isn't preserved in the 
coredump. So ignore gdb's error there.)

  Something in kvm is writing zeroes over a field of memory after we
  already checked that it was non-zero.

  This is on 
  Linux anvil1 4.4.0-112-generic #135-Ubuntu SMP Fri Jan 19 11:48:36 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Both the host and the guest VM are on identical OS revision.

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

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

[Touch-packages] [Bug 1747354] Re: Update bluez to version 5.48 in bionic

[Daniel van Vugt]

We are blocked on this:

112 UserFailVerify that the paired device will reconnect
after the phone/tablet is rebooted.

So we need to retest that, firstly by finding a device on which it _did_
work in previous versions.

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

Title:
  Update bluez to version 5.48 in bionic

Status in bluez package in Ubuntu:
  In Progress

Bug description:
  Update bluez to version 5.48 in bionic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1747354/+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 1632772] Re: Login option 'GNOME on Wayland' does not start from LightDM

[monkeydri]

I can successfully login with lightdm after deleting every Xorg session
entries correpsonding to a wayland session entry (ex rm
/usr/share/xessions/gnome /usr/share/xessions/ubuntu and leave
/usr/share/wayland-sessions/gnome and /usr/share/wayland-
sessions/ubuntu).

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

Title:
  Login option 'GNOME on Wayland' does not start from LightDM

Status in Ubuntu GNOME:
  Triaged
Status in unity8-desktop-session:
  Won't Fix
Status in lightdm package in Ubuntu:
  Invalid
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in unity8-desktop-session package in Ubuntu:
  Triaged
Status in unity8-desktop-session source package in Yakkety:
  Triaged
Status in unity8-desktop-session source package in Zesty:
  Triaged

Bug description:
  When picking GNOME on Wayland as session and attempting to login from
  LightDM then it fails, all you see is a black screen with a blinking
  cursor.

  However, manually running:
  $ dbus-run-session gnome-shell --display-server --wayland
  from the console/vt1 (Ctrl+Alt+F1) seems to work.
  But from LightDM it does not work.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-session-wayland 3.20.2-1ubuntu7
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  Date: Wed Oct 12 18:06:13 2016
  InstallationDate: Installed on 2013-12-26 (1020 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1632772/+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 1747744] Re: [regression] Video playback in totem is corrupted in X11

[dino99]

Still pending publication  https://launchpad.net/ubuntu/+source/mesa

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

Title:
  [regression] Video playback in totem is corrupted in X11

Status in Mesa:
  In Progress
Status in mesa package in Ubuntu:
  Fix Committed
Status in totem package in Ubuntu:
  Confirmed

Bug description:
  Test case
  Log inti xorg session
  Install gstreamer1.0-vaapi plugin
  Play a supported video (- h.264/avc in .mp4, .mkv or .mov  would suffice

  Expected: hardware decoded playback
  What happens: totally corrupted screen, see screenshots

  Does work ok in a wayland session

  $ vainfo
  libva info: VA-API version 1.0.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_1_0
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 1.0 (libva 2.0.0)
  vainfo: Driver version: Intel i965 driver for Intel(R) Haswell Mobile - 2.0.0
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:   VAEntrypointVLD
VAProfileMPEG2Simple:   VAEntrypointEncSlice
VAProfileMPEG2Main  :   VAEntrypointVLD
VAProfileMPEG2Main  :   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
VAProfileH264Main   :   VAEntrypointVLD
VAProfileH264Main   :   VAEntrypointEncSlice
VAProfileH264High   :   VAEntrypointVLD
VAProfileH264High   :   VAEntrypointEncSlice
VAProfileH264MultiviewHigh  :   VAEntrypointVLD
VAProfileH264MultiviewHigh  :   VAEntrypointEncSlice
VAProfileH264StereoHigh :   VAEntrypointVLD
VAProfileH264StereoHigh :   VAEntrypointEncSlice
VAProfileVC1Simple  :   VAEntrypointVLD
VAProfileVC1Main:   VAEntrypointVLD
VAProfileVC1Advanced:   VAEntrypointVLD
VAProfileNone   :   VAEntrypointVideoProc
VAProfileJPEGBaseline   :   VAEntrypointVLD

  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gstreamer1.0-vaapi 1.12.4-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb  6 14:43:57 2018
  InstallationDate: Installed on 2018-02-06 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180204)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gstreamer-vaapi
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1747744/+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 1749398] Re: Update libva: 2.0.0 --> 2.1.1 before release 18.04 bionic

[dino99]

New features   https://github.com/intel/libva/releases

** Tags added: upgrade-software-version

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

Title:
  Update libva: 2.0.0 --> 2.1.1 before release 18.04 bionic

Status in libva package in Ubuntu:
  New

Bug description:
  Libva 2.1.0 has been released: https://github.com/intel/libva/releases

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libva2 2.0.0-2
  Uname: Linux 4.14.0-18.2-liquorix-amd64 x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Wed Feb 14 11:46:06 2018
  InstallationDate: Installed on 2017-08-28 (169 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  SourcePackage: libva
  UpgradeStatus: Upgraded to bionic on 2018-02-08 (5 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libva/+bug/1749398/+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 1747354] Re: Update bluez to version 5.48 in bionic

[Daniel van Vugt]

Test results for:
112 UserFailVerify that the paired device will reconnect after the 
phone/tablet is rebooted.

5.46
Logitech M337 mouse : PASS (move the mouse, wait a few seconds, works)
Sony SRS-XB2 .. : FAIL (need to reconnect manually via the Settings GUI)
HP KT-1281 keyboard : PARTIAL (hit keys, then reconnected according to 
indicator but input never works)

5.48
Logitech M337 mouse : PASS (move the mouse, wait a few seconds, works)
Sony SRS-XB2 .. : FAIL (need to reconnect manually via the Settings GUI)
HP KT-1281 keyboard : PARTIAL (hit keys, then reconnected according to 
indicator but input never works)

So overall PASS. There is no regression that I can see. Just note that
some device types will never reconnect. And many need to be touched
(e.g. mouse moved or key pressed) before it will wake and get auto-
reconnected.

Tip: You can view the Bluetooth indicator on the login screen to view
its (slow) progress in reconnecting things.

It appears my HP keyboard is just broken. For the above and other
reasons (trouble turning on and trouble pairing, even with new
batteries). I will omit it from future tests.

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

Title:
  Update bluez to version 5.48 in bionic

Status in bluez package in Ubuntu:
  In Progress

Bug description:
  Update bluez to version 5.48 in bionic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1747354/+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 1749389] Re: ntpdate lock apparmor deny

[ChristianEhrhardt]

auto profile replace on upgrade - ok
restart without apparmor issues - ok

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

Title:
  ntpdate lock apparmor deny

Status in ntp package in Ubuntu:
  Triaged
Status in ntp source package in Xenial:
  Triaged
Status in ntp source package in Artful:
  Triaged

Bug description:
  [Impact]

   * Apparmor denies access to lock it shares with ntpdate to ensure no 
 issues due to concurrent access

  [Test Case]

   1. get a container of target release
   2. install ntp
  apt install ntp
   3. watch dmesg on container-host
  dmesg -w 
   4. restart ntp in container
  systemctl restart ntp
   => see (or no more after fix) apparmor denie:
  apparmor="DENIED" operation="file_inherit" profile="/usr/sbin/ntpd" 
name="/run/lock/ntpdate" pid=30113 comm="ntpd" requested_mask="w" 
denied_mask="w"

  [Regression Potential]

   * we are only slightly opening up the apparmor profile, but none of the 
 changes poses a security risk so regression potential on it's own 
 should be close to zero.

   * There is a potential issue if the locking (that now can succeed) would 
 e.g. no more be freed up or the action behind the locking would cause 
 issues.

  [Other Info]
   
   * n/a

  
  On start/restart nto has an error in apparmor due to the locking it tries to 
avoid issues running concurrently with ntpdate.

  That looks like:
  apparmor="DENIED" operation="file_inherit" profile="/usr/sbin/ntpd" 
name="/run/lock/ntpdate" pid=30113 comm="ntpd" requested_mask="w" 
denied_mask="w"

  The rule we need is:
  /run/lock/ntpdate wk,

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1749389/+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 1749150] Re: Spontaneous single window freezing

[Valentin Nechayev]

On the first host, apport-collect crashed with:

Traceback (most recent call last):
  File "/usr/share/apport/apport-kde", line 530, in 
sys.exit(UserInterface.run_argv())
  File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 658, in run_argv
return self.run_update_report()
  File "/usr/lib/python2.7/dist-packages/apport/ui.py", line 574, in 
run_update_report
response = self.ui_present_report_details(allowed_to_report)
  File "/usr/share/apport/apport-kde", line 367, in ui_present_report_details
desktop_info)
  File "/usr/share/apport/apport-kde", line 184, in __init__
self.ui.ui_update_view(self)
  File "/usr/share/apport/apport-kde", line 358, in ui_update_view
QTreeWidgetItem(keyitem, [str(line)])
UnicodeEncodeError: 'ascii' codec can't encode characters in position 17-18: 
ordinal not in range(128)
Segmentation fault

I guess it needs more stabilization work :(

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

Title:
  Spontaneous single window freezing

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Sometimes a window stopped refreshing its contents. Different applications 
affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen.
  No way found to revive in-time refreshing except full window closing (or 
blind login, in case of KDE lock screen). Keyboard or mouse activity in a such 
window doesn't help.
  A one-shot refresh can be easily caused by switching to another virtual 
desktop and then back. After such switching, a window refresh is active for 
approximately 0.5 seconds, then stops again.
  No relation to host uptime or X session uptime is visible.

  Observed on two different hosts, both carrying Kubuntu 16.04 and
  running XWindow+KDE as desktop environment. KDE is standard Kubuntu
  one. Multiple virtual desktops are used on both hosts.

  The issue started to appear approximately 4-5 months ago but I can't
  specify exact package change that could have caused it. Both hosts are
  regularly updated (no more than 1 week delay).

  The first host has:
  video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller])
  Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670]
  Kernel driver in use: radeon
  Kernel modules: radeon
  CPU: AMD FX-8150
  RAM: 16GB
  Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade.
  current kernel: linux-image-4.4.0-112-generic
  video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active 
driver: radeon

  Issue rate on this host is rather tiny (~1 per week).

  The second one has:
  video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev 
a1) (prog-if 00 [VGA controller])
  Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93
  Kernel driver in use: nvidia
  Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384
  (really this is GeForce GT 740)
  CPU:Intel i3-4170
  RAM: 16GB
  Installed originally as Kubuntu 16.04
  current kernel: linux-image-4.13.0-32-generic (depended on by 
linux-generic-hwe-16.04)
  video packages: HWE series (e.g. 
xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia 
(proprietary), but the same issue observed with VESA driver.

  Issue rate on this host is 1-2 per day and was much higher with VESA
  driver in use.

  No respective messages are found in Xorg.*.log or ~/.xsession-errors,
  but the latter has got stream of messages like:

  at host with AMD and Radeon:
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )

  at host with Intel and Nvidia:
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )

  such messages started appearing approximately at the same time, plus-
  minus 1-2 months.

  Additional info can be provided on demand.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  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
  CurrentDesktop: KDE
  Date: Tue Feb 13 11:47:32 2018
  InstallationDate: Installed on 2014-12-16 (1154 days ago)
  InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: xorg
  Upg

[Touch-packages] [Bug 1746874] Re: gnome-shell and Xwayland sometimes leave $HOME/core files (should be /var/crash files)

[Julian Andres Klode]

So, what we're seeing is that 1657 ended, but 1941 and 1946 started at
the same time, roughly. hence 1941 got the lock and 1946 not. The run of
1657 took less than 20 seconds, so it seems to me 30 seconds are
probably fine, but we can go up to a minute.

-- 
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:
  Triaged
Status in apport source package in Bionic:
  Triaged

Bug description:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files). This issue was first mentioned in bug 1746653. But
  then I noticed my machine doing it too...

  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 1749432] [NEW] cryptsetup open hangs waiting for udev cookied

[Dimitri John Ledkov]

Public bug reported:

systemd has a testcase to setup, open and close a luks1 volume.

this test case has started to fail with udev 237 & cryptsetup2

this appears to be reproducible with straight up "cryptsetup open" call
which seems to hang in device mapper library, e.g.:

# cryptsetup open --type luks UUID=fd41c9ba-4286-415d-95e4-960fd28b5e>
# cryptsetup 2.0.1 processing "cryptsetup open --type luks 
UUID=fd41c9ba-4286-415d-95e4-960fd28b5e43 varcrypt --key-file /etc/varkey 
--debug --verbose"
# Running command open.
# Locking memory.
# Installing SIGINT/SIGTERM handler.
# Unblocking interruption on signal.
# Allocating context for crypt device 
/dev/disk/by-uuid/fd41c9ba-4286-415d-95e4-960fd28b5e43.
# Trying to open and read device 
/dev/disk/by-uuid/fd41c9ba-4286-415d-95e4-960fd28b5e43 with direct-io.
# Initialising device-mapper backend library.
# Trying to load any crypt type from device 
/dev/disk/by-uuid/fd41c9ba-4286-415d-95e4-960fd28b5e43.
# Crypto backend (gcrypt 1.8.1) initialized in cryptsetup library version 2.0.1.
# Detected kernel Linux 4.13.0-32-generic x86_64.
# PBKDF pbkdf2, hash sha256, time_ms 2000 (iterations 0), max_memory_kb 0, 
parallel_threads 0.
# Reading LUKS header of size 1024 from device 
/dev/disk/by-uuid/fd41c9ba-4286-415d-95e4-960fd28b5e43
# Key length 32, device size 18432 sectors, header size 2050 sectors.
# Activating volume varcrypt using token -1.
# File descriptor passphrase entry requested.
# Activating volume varcrypt [keyslot -1] using passphrase.
# dm version   [ opencount flush ]   [16384] (*1)
# dm versions   [ opencount flush ]   [16384] (*1)
# Detected dm-ioctl version 4.37.0.
# Detected dm-crypt version 1.18.0.
# Device-mapper backend running with UDEV support enabled.
# dm status varcrypt  [ opencount flush ]   [16384] (*1)
# Trying to open key slot 0 [ACTIVE_LAST].
# Reading key slot 0 area.
# Using userspace crypto wrapper to access keyslot area.
Key slot 0 unlocked.
# Calculated device size is 14336 sectors (RW), offset 4096.
# DM-UUID is CRYPT-LUKS1-fd41c9ba4286415d95e4960fd28b5e43-varcrypt
# Udev cookie 0xd4d4a7f (semid 65538) created
# Udev cookie 0xd4d4a7f (semid 65538) incremented to 1
# Udev cookie 0xd4d4a7f (semid 65538) incremented to 2
# Udev cookie 0xd4d4a7f (semid 65538) assigned to CREATE task(0) with flags 
DISABLE_LIBRARY_FALLBACK (0x20)
# dm create varcrypt CRYPT-LUKS1-fd41c9ba4286415d95e4960fd28b5e43-varcrypt [ 
opencount flush ]   [16384] (*1)
# dm reload varcrypt  [ opencount flush securedata ]   [16384] (*1)
# dm resume varcrypt  [ opencount flush securedata ]   [16384] (*1)
# varcrypt: Stacking NODE_ADD (253,0) 0:6 0660 [trust_udev]
# varcrypt: Stacking NODE_READ_AHEAD 256 (flags=1)
# Udev cookie 0xd4d4a7f (semid 65538) decremented to 1
# Udev cookie 0xd4d4a7f (semid 65538) waiting for zero

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

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

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

** Description changed:

  systemd has a testcase to setup, open and close a luks1 volume.
  
  this test case has started to fail with udev 237 & cryptsetup2
  
- this appears to be reproducible with straight up "cryptsetup open" call,
- e.g.:
+ this appears to be reproducible with straight up "cryptsetup open" call
+ which seems to hang in device mapper library, e.g.:
  
  # cryptsetup open --type luks UUID=fd41c9ba-4286-415d-95e4-960fd28b5e>
  # cryptsetup 2.0.1 processing "cryptsetup open --type luks 
UUID=fd41c9ba-4286-415d-95e4-960fd28b5e43 varcrypt --key-file /etc/varkey 
--debug --verbose"
  # Running command open.
  # Locking memory.
  # Installing SIGINT/SIGTERM handler.
  # Unblocking interruption on signal.
  # Allocating context for crypt device 
/dev/disk/by-uuid/fd41c9ba-4286-415d-95e4-960fd28b5e43.
  # Trying to open and read device 
/dev/disk/by-uuid/fd41c9ba-4286-415d-95e4-960fd28b5e43 with direct-io.
  # Initialising device-mapper backend library.
  # Trying to load any crypt type from device 
/dev/disk/by-uuid/fd41c9ba-4286-415d-95e4-960fd28b5e43.
  # Crypto backend (gcrypt 1.8.1) initialized in cryptsetup library version 
2.0.1.
  # Detected kernel Linux 4.13.0-32-generic x86_64.
  # PBKDF pbkdf2, hash sha256, time_ms 2000 (iterations 0), max_memory_kb 0, 
parallel_threads 0.
  # Reading LUKS header of size 1024 from device 
/dev/disk/by-uuid/fd41c9ba-4286-415d-95e4-960fd28b5e43
  # Key length 32, device size 18432 sectors, header size 2050 sectors.
  # Activating volume varcrypt using token -1.
  # File descriptor passphrase entry requested.
  # Activating volume varcrypt [keyslot -1] using passphrase.
  # dm version   [ opencount flush ]   [16384] (*1)
  # dm versions   [ opencount flush ]   [16384] (*1)
  # Detected dm-ioctl version 4.37.0.
  # Detected dm-crypt version 1.18.0.
  # Device-mapper backend running with UDEV support enabled.
  # dm status varcrypt  [ opencount flush ]   [16

[Touch-packages] [Bug 1316970] Re: g_dbus memory leak in lrmd

[Seyeong Kim]

Hello Eric, ddstreet

#1740892 seems starting to fix

Could you guys can sponsor this issue as well?

Thanks a lot

-- 
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 1749443] [NEW] ioctl FBIOPUT_VSCREENINFO: Invalid argument

[stsp]

Public bug reported:

$ fbset 768x576-75
ioctl FBIOPUT_VSCREENINFO: Invalid argument

And the same happens with all other modes
defined in /etc/fb.modes

The problem seems to be that KMS fbcon does
not accept the pixclock parameter, which is
the first parameter in a "timings" string.
Changing it to 0 for all modes makes them to
work, albeit w/o actual resizing. The image
then just occupies the upper-left corner of
the screen. But its still better than the
complete failure.
I suppose also other timing params are not
supported. At least if you run fbset w/o
parameters, it will display all timing params
set to zero.
So I think zeroing "timings" for all modes
in /etc/fb.modes will help with KMS.

Additionally, please add the 1920x1080 mode,
its currently missing.

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

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

Title:
  ioctl FBIOPUT_VSCREENINFO: Invalid argument

Status in fbset package in Ubuntu:
  New

Bug description:
  $ fbset 768x576-75
  ioctl FBIOPUT_VSCREENINFO: Invalid argument

  And the same happens with all other modes
  defined in /etc/fb.modes

  The problem seems to be that KMS fbcon does
  not accept the pixclock parameter, which is
  the first parameter in a "timings" string.
  Changing it to 0 for all modes makes them to
  work, albeit w/o actual resizing. The image
  then just occupies the upper-left corner of
  the screen. But its still better than the
  complete failure.
  I suppose also other timing params are not
  supported. At least if you run fbset w/o
  parameters, it will display all timing params
  set to zero.
  So I think zeroing "timings" for all modes
  in /etc/fb.modes will help with KMS.

  Additionally, please add the 1920x1080 mode,
  its currently missing.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fbset/+bug/1749443/+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 1733870] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From pedro...@br.ibm.com 2018-02-14 07:06 EDT---
(In reply to comment #26)
> Any updates on the upstream code status?

Sorry, I'm afraid there's nothing upstream yet, still working on it.

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

Title:
  [Ubuntu 18.10] Add GDB support to access/display POWER8 registers

Status in The Ubuntu-power-systems project:
  Incomplete
Status in gdb package in Ubuntu:
  Incomplete

Bug description:
  This feature request is for GDB support for access to Power registers
  that are currently not accessible: PPR, DSCR, TAR, EBB, PMU and HTM
  registers.

  The feature is currently being worked on, so no upstream code is
  available yet.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1733870/+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 1749389] Re: ntpdate lock apparmor deny

[ChristianEhrhardt]

Missed the right format in changelog :-/, but this is fixed in Bionic by
https://launchpad.net/ubuntu/+source/ntp/1:4.2.8p10+dfsg-5ubuntu7

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

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

Title:
  ntpdate lock apparmor deny

Status in ntp package in Ubuntu:
  Fix Released
Status in ntp source package in Xenial:
  Triaged
Status in ntp source package in Artful:
  Triaged

Bug description:
  [Impact]

   * Apparmor denies access to lock it shares with ntpdate to ensure no 
 issues due to concurrent access

  [Test Case]

   1. get a container of target release
   2. install ntp
  apt install ntp
   3. watch dmesg on container-host
  dmesg -w 
   4. restart ntp in container
  systemctl restart ntp
   => see (or no more after fix) apparmor denie:
  apparmor="DENIED" operation="file_inherit" profile="/usr/sbin/ntpd" 
name="/run/lock/ntpdate" pid=30113 comm="ntpd" requested_mask="w" 
denied_mask="w"

  [Regression Potential]

   * we are only slightly opening up the apparmor profile, but none of the 
 changes poses a security risk so regression potential on it's own 
 should be close to zero.

   * There is a potential issue if the locking (that now can succeed) would 
 e.g. no more be freed up or the action behind the locking would cause 
 issues.

  [Other Info]
   
   * n/a

  
  On start/restart nto has an error in apparmor due to the locking it tries to 
avoid issues running concurrently with ntpdate.

  That looks like:
  apparmor="DENIED" operation="file_inherit" profile="/usr/sbin/ntpd" 
name="/run/lock/ntpdate" pid=30113 comm="ntpd" requested_mask="w" 
denied_mask="w"

  The rule we need is:
  /run/lock/ntpdate wk,

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1749389/+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 1721294] Re: Unattended upgrade fails with "Error in function"

[Marius Gedminas]

The good news is the problem is reproducible.

The bad news is APT::Periodic::Verbose "1" doesn't make unattended-
upgrade produce any more output in its failure email:

Unattended upgrade returned: False

Packages that attempted to upgrade:
 dh-apparmor libapparmor1 python3-update-manager update-manager-core

Package installation log:
Error in function:


Unattended-upgrades log:
Initial blacklisted packages:
Starting unattended upgrades script
Allowed origins are: ['o=Ubuntu,a=trusty-security', 'o=UbuntuESM,a=trusty', 
'o=Ubuntu,a=trusty-security', 'o=Ubuntu,a=trusty-updates', 
'origin=LP-PPA-pov,suite=trusty']
Packages that will be upgraded: dh-apparmor libapparmor1 
python3-update-manager update-manager-core
Writing dpkg log to 
'/var/log/unattended-upgrades/unattended-upgrades-dpkg_2018-02-13_03:07:51.796037.log'
Installing the upgrades failed!
error message: 'installArchives() failed'
dpkg returned a error! See 
'/var/log/unattended-upgrades/unattended-upgrades-dpkg_2018-02-13_03:07:51.796037.log'
 for details
Packages that are auto removed: ''
Packages auto-removed

Which is exactly the same thing I saw yesterday.  I think I see my
mistake: I should've set APT::Periodic::Verbose to "3" to have the cron
script pass -d to unattended-upgrade!  D'oh!

On the other hand I got an extra email from cron.daily saying

/etc/cron.daily/apt:
verbose level 1
sleeping for 280 seconds
check_stamp: interval=86400, now=1518559200, stamp=1518472800, delta=86400 
(sec)
apt-key net-update (failure)
download updated metadata (success).
send dbus signal (success)
check_stamp: interval=0
download upgradable (not run)
check_stamp: interval=86400, now=1518559200, stamp=1518472800, delta=86400 
(sec)
unattended-upgrade (success)
check_stamp: interval=0
autoclean (not run)
aged: ctime <30 and mtime <30 and ctime>2 and mtime>2
end remove by archive size: size=24256 < 512000

The "apt-key net-update (failure)" line is intriguing, but seems to be
unrelated.

I've bumped APT::Periodic::Verbose to "3" now and will see what happens
next morning.

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

Title:
  Unattended upgrade fails with "Error in function"

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  This is the cron email I received today:

  From: root 
  To: r...@pov.lt
  Subject: unattended-upgrades result for 'iv-4.pov.lt': 'False'
  Date: Wed,  4 Oct 2017 03:40:19 +0300 (EEST)

  Unattended upgrade returned: False

  Packages that attempted to upgrade:
   ca-certificates libidn11 libnss3 libnss3-nssdb

  Package installation log:
  Error in function:

  
  Unattended-upgrades log:
  Initial blacklisted packages:
  Starting unattended upgrades script
  Allowed origins are: ['o=Ubuntu,a=trusty-security', 
'o=UbuntuESM,a=trusty', 'o=Ubuntu,a=trusty-security', 
'o=Ubuntu,a=trusty-updates', 'origin=LP-PPA-pov,suite=trusty']
  Packages that will be upgraded: ca-certificates libidn11 libnss3 
libnss3-nssdb
  Writing dpkg log to 
'/var/log/unattended-upgrades/unattended-upgrades-dpkg_2017-10-04_03:40:17.411277.log'
  Installing the upgrades failed!
  error message: 'installArchives() failed'
  dpkg returned a error! See 
'/var/log/unattended-upgrades/unattended-upgrades-dpkg_2017-10-04_03:40:17.411277.log'
 for details
  Packages that are auto removed: ''
  Packages auto-removed

  The named log file, var/log/unattended-upgrades/unattended-upgrades-
  dpkg_2017-10-04_03:40:17.411277.log contains only this:

  Error in function:

  That's it.

  Now given that ca-certificates is involved, I suspect this may be
  related to non-ASCII filenames (see bug 1554365), but unlike that bug,
  here the upgrade fails instead of succeeding, and the actual error is
  not shown anywhere.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unattended-upgrades 0.82.1ubuntu2.5
  Uname: Linux 2.6.32-042stab124.2 x86_64
  ApportVersion: 2.14.1-0ubuntu3.25
  Architecture: amd64
  Date: Wed Oct  4 18:54:54 2017
  PackageArchitecture: all
  ProcEnviron:
   LC_CTYPE=lt_LT.UTF-8
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=lt_LT.UTF-8
   SHELL=/bin/bash
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1721294/+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 1749432] Re: cryptsetup open hangs waiting for udev cookied

[Dimitri John Ledkov]

So i've tried various combinations of downgrading
systemd/cryptsetup/lvm.

At the moment latest cryptsetup2 and systemd from bionic-proposed, pass
the systemd test when downgrading lvm2 (devmapper et al) to the one in
artful 2.02.168-2ubuntu3

I am suspecting a regression in lvm2, specifically around udev cookies
synchronisation.

** Tags added: block-proposed

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

Title:
  cryptsetup open hangs waiting for udev cookied

Status in cryptsetup package in Ubuntu:
  New
Status in lvm2 package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  systemd has a testcase to setup, open and close a luks1 volume.

  this test case has started to fail with udev 237 & cryptsetup2

  this appears to be reproducible with straight up "cryptsetup open"
  call which seems to hang in device mapper library, e.g.:

  # cryptsetup open --type luks UUID=fd41c9ba-4286-415d-95e4-960fd28b5e>
  # cryptsetup 2.0.1 processing "cryptsetup open --type luks 
UUID=fd41c9ba-4286-415d-95e4-960fd28b5e43 varcrypt --key-file /etc/varkey 
--debug --verbose"
  # Running command open.
  # Locking memory.
  # Installing SIGINT/SIGTERM handler.
  # Unblocking interruption on signal.
  # Allocating context for crypt device 
/dev/disk/by-uuid/fd41c9ba-4286-415d-95e4-960fd28b5e43.
  # Trying to open and read device 
/dev/disk/by-uuid/fd41c9ba-4286-415d-95e4-960fd28b5e43 with direct-io.
  # Initialising device-mapper backend library.
  # Trying to load any crypt type from device 
/dev/disk/by-uuid/fd41c9ba-4286-415d-95e4-960fd28b5e43.
  # Crypto backend (gcrypt 1.8.1) initialized in cryptsetup library version 
2.0.1.
  # Detected kernel Linux 4.13.0-32-generic x86_64.
  # PBKDF pbkdf2, hash sha256, time_ms 2000 (iterations 0), max_memory_kb 0, 
parallel_threads 0.
  # Reading LUKS header of size 1024 from device 
/dev/disk/by-uuid/fd41c9ba-4286-415d-95e4-960fd28b5e43
  # Key length 32, device size 18432 sectors, header size 2050 sectors.
  # Activating volume varcrypt using token -1.
  # File descriptor passphrase entry requested.
  # Activating volume varcrypt [keyslot -1] using passphrase.
  # dm version   [ opencount flush ]   [16384] (*1)
  # dm versions   [ opencount flush ]   [16384] (*1)
  # Detected dm-ioctl version 4.37.0.
  # Detected dm-crypt version 1.18.0.
  # Device-mapper backend running with UDEV support enabled.
  # dm status varcrypt  [ opencount flush ]   [16384] (*1)
  # Trying to open key slot 0 [ACTIVE_LAST].
  # Reading key slot 0 area.
  # Using userspace crypto wrapper to access keyslot area.
  Key slot 0 unlocked.
  # Calculated device size is 14336 sectors (RW), offset 4096.
  # DM-UUID is CRYPT-LUKS1-fd41c9ba4286415d95e4960fd28b5e43-varcrypt
  # Udev cookie 0xd4d4a7f (semid 65538) created
  # Udev cookie 0xd4d4a7f (semid 65538) incremented to 1
  # Udev cookie 0xd4d4a7f (semid 65538) incremented to 2
  # Udev cookie 0xd4d4a7f (semid 65538) assigned to CREATE task(0) with flags 
DISABLE_LIBRARY_FALLBACK (0x20)
  # dm create varcrypt CRYPT-LUKS1-fd41c9ba4286415d95e4960fd28b5e43-varcrypt [ 
opencount flush ]   [16384] (*1)
  # dm reload varcrypt  [ opencount flush securedata ]   [16384] (*1)
  # dm resume varcrypt  [ opencount flush securedata ]   [16384] (*1)
  # varcrypt: Stacking NODE_ADD (253,0) 0:6 0660 [trust_udev]
  # varcrypt: Stacking NODE_READ_AHEAD 256 (flags=1)
  # Udev cookie 0xd4d4a7f (semid 65538) decremented to 1
  # Udev cookie 0xd4d4a7f (semid 65538) waiting for zero

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1749432/+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 1749086] Re: (X)Ubuntu 16.04.3 LTS: sleep on boot

[Steve Bainton]

Ok, I don't understand how come, but it seems to work fine now. Possibly
sth to do with kernel as same thing used to happen with OpenSUSE and
Mint, including during installation (only for a few seconds though).

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

Title:
  (X)Ubuntu 16.04.3 LTS: sleep on boot

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Newly installed xubuntu, kubuntu (other flavours I haven't tried, but
  probably the same), the screen turns off a few seconds after choosing
  ubuntu in grub2 menu, after about 5 minutes it comes back to life and
  login screen is presented and from that point on everything seems to
  work as normal. (Might have sth to do with Radeon drivers?) Please
  tell me what other info you need.

  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
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Feb 13 07:37:53 2018
  InstallationDate: Installed on 2018-02-11 (1 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  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
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Juniper XT [Radeon HD 5770] [1043:03b6]
  InstallationDate: Installed on 2018-02-11 (2 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=7529842e-d871-4641-89dc-3a4980dda2de ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Tags:  xenial ubuntu
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/18/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: 770 Extreme3
  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.80:bd10/18/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn770Extreme3: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.
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1749086/+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 1699033] Re: Two-finger right click does not work in gnome-shell

[Jeremy Bicha]

I forgot to close this bug in my gsettings-desktop-schemas upload
yesterday.

I included a bit of background about this change at
https://jeremy.bicha.net/2018/02/12/gnome-tweaks-3-28-progress-report-2/

** Changed in: gsettings-desktop-schemas (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 gsettings-desktop-schemas
in Ubuntu.
https://bugs.launchpad.net/bugs/1699033

Title:
  Two-finger right click does not work in gnome-shell

Status in GSettings Desktop Schemas:
  Fix Released
Status in gsettings-desktop-schemas package in Ubuntu:
  Fix Released

Bug description:
  Using two fingers on the clickpad to right click does not work in
  gnome-shell.

  It seems to be defaulting to the old-style single finger click in the
  bottom right corner to do a right click.

  Workaround:
  gnome-tweak-tool > Keyboard & Mouse > Touchpad > Click Method = Fingers

  Gsettings diff:
  < org.gnome.desktop.peripherals.touchpad click-method 'default'
  ---
  > org.gnome.desktop.peripherals.touchpad click-method 'fingers'

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu6
  ProcVersionSignature: Ubuntu 4.11.0-7.12-generic 4.11.6
  Uname: Linux 4.11.0-7-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Tue Jun 20 14:50:10 2017
  DisplayManager: lightdm
  GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' 
b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-06-20 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170613)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gsettings-desktop-schemas/+bug/1699033/+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 108366] Re: Totem unable to add to playlist after selecting unreadable location

[Bug Watch Updater]

** Changed in: gtk
   Status: Expired => Invalid

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

Title:
  Totem unable to add to playlist after selecting unreadable location

Status in GTK+:
  Invalid
Status in Totem:
  Invalid
Status in gtk+2.0 package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: totem

  When adding to the playlist using the sidebar interface, totem
  defaults to the directory of the last selected file when prompting for
  a new file.  When that directory is unreadable (e.g.
  http://www.gearwire.com/media/ (after adding
  http://www.gearwire.com/media/seymour-duncan-guitar-
  pickups-1-musikmesse.wmv by pasting into the location control in the
  last add)), totem presents the message "error accessing
  'http://www.gearwire.com/media': Access denied".  If this dialog is
  closed, totem is unable to add new files to the playlist (even when
  pasting the Location) until a readable base location (e.g. the home
  directory) is selected.

  In functional terms:

  Observed Behaviour:
  1)  Totem is open, sidebar is open in Playlist mode
  2)  Click "+" to add a file
  3)  Paste a location in the Location control (public location given above)
  4)  Click "Add" to add the location
  5)  Add interface closes, Totem shows the new file in the playlist
  6)  Click "+" to add another file
  7)  Totem presents dialog with "error accessing 
'http://www.gearwire.com/media': Access denied"
  8)  Close dialog
  9)  Paste another location in the Location control
  10)  Click "Add" to add the location
  11)  Nothing happens (no UI changes (except button blink), no message, etc.

  Expected Behaviour:
  1)  Totem is open, sidebar is open in Playlist mode
  2)  Click "+" to add a file
  3)  Paste a location in the Location control (public location given above)
  4)  Click "Add" to add the location
  5)  Add interface closes, Totem shows the new file in the playlist
  6)  Click "+" to add another file
  7)  Totem presents dialog with "error accessing 
'http://www.gearwire.com/media': Access denied"
  8)  Close dialog
  9)  Paste another location in the Location control
  10)  Click "Add" to add the location
  11)  Totem shows the new file in the playlist

  Alternate acceptable behaviour:
  1)  Totem is open, sidebar is open in Playlist mode
  2)  Click "+" to add a file
  3)  Paste a location in the Location control (public location given above)
  4)  Click "Add" to add the location
  5)  Add interface closes, Totem shows the new file in the playlist
  6)  Click "+" to add another file
  7)  Totem presents dialog with "error accessing 
'http://www.gearwire.com/media': Access denied"
  8)  Close dialog
  9)  Totem defauls to user home directory (or /media, or any known safe 
location)
  10)  Paste another location in the Location control
  11)  Click "Add" to add the location
  12)  Totem shows the new file in the playlist

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/108366/+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 1749449] [NEW] package libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz', which i

[Jaime Cruz]

Public bug reported:

Error occurred when running the software updater this morning.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
NonfreeKernelModules: wl
.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: Wed Feb 14 08:00:48 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.13.0-32-generic, x86_64: installed
DuplicateSignature:
 package:libgl1-mesa-dri:17.2.8-0ubuntu0~16.04.1
 Unpacking libgl1-mesa-dri:i386 (17.2.8-0ubuntu0~16.04.1) over 
(17.2.8-0ubuntu0~16.04.1) ...
 dpkg: error processing archive 
/var/cache/apt/archives/libgl1-mesa-dri_17.2.8-0ubuntu0~16.04.1_i386.deb 
(--unpack):
  trying to overwrite shared 
'/usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz', which is different from 
other instances of package libgl1-mesa-dri:i386
ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz', which is different from 
other instances of package libgl1-mesa-dri:i386
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Venus LE [Radeon HD 8830M] [1002:682b] 
(rev 87) (prog-if 00 [VGA controller])
   Subsystem: Pegatron Venus LE [Radeon HD 8830M] [1b0a:90f3]
InstallationDate: Installed on 2014-09-06 (1256 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: HP 510-p127c
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=3dd39524-3a29-4831-9f5a-6decde86d996 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.25
SourcePackage: mesa
Title: package libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 failed to 
install/upgrade: trying to overwrite shared 
'/usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz', which is different from 
other instances of package libgl1-mesa-dri:i386
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/07/2016
dmi.bios.vendor: AMI
dmi.bios.version: F.14
dmi.board.asset.tag: CNV64609PD
dmi.board.name: 822A
dmi.board.vendor: HP
dmi.board.version: 00
dmi.chassis.asset.tag: CNV64609PD
dmi.chassis.type: 3
dmi.chassis.vendor: HP
dmi.modalias: 
dmi:bvnAMI:bvrF.14:bd10/07/2016:svnHP:pn510-p127c:pvr:rvnHP:rn822A:rvr00:cvnHP:ct3:cvr:
dmi.product.family: 103C_53316J G=D
dmi.product.name: 510-p127c
dmi.sys.vendor: HP
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.8-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Sun Jan 28 01:00:43 2018
xserver.configfile: default
xserver.errors: RADEON(0): drmmode_do_crtc_dpms cannot get last vblank counter
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.5-0ubuntu2~16.04.1
xserver.video_driver: radeon

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


** Tags: amd64 apport-package compiz-0.9 package-conflict ubuntu xenial

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

Title:
  package libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 failed to
  install/upgrade: trying to overwrite shared '/usr/share/doc/libgl1
  -mesa-dri/changelog.Debian.gz', which is different from other
  instances of package libgl1-mesa-dri:i386

Status in mesa package in Ubuntu:
  New

Bug description:
  Error occurred when running the software updater this morning.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: wl
  .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: Wed Feb 14 08:00:48 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubun

[Touch-packages] [Bug 1749449] Re: package libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz', which is

[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 mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1749449

Title:
  package libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 failed to
  install/upgrade: trying to overwrite shared '/usr/share/doc/libgl1
  -mesa-dri/changelog.Debian.gz', which is different from other
  instances of package libgl1-mesa-dri:i386

Status in mesa package in Ubuntu:
  New

Bug description:
  Error occurred when running the software updater this morning.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: wl
  .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: Wed Feb 14 08:00:48 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: bcmwl, 6.30.223.271+bdcom, 4.13.0-32-generic, x86_64: installed
  DuplicateSignature:
   package:libgl1-mesa-dri:17.2.8-0ubuntu0~16.04.1
   Unpacking libgl1-mesa-dri:i386 (17.2.8-0ubuntu0~16.04.1) over 
(17.2.8-0ubuntu0~16.04.1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libgl1-mesa-dri_17.2.8-0ubuntu0~16.04.1_i386.deb 
(--unpack):
trying to overwrite shared 
'/usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz', which is different from 
other instances of package libgl1-mesa-dri:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz', which is different from 
other instances of package libgl1-mesa-dri:i386
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Venus LE [Radeon HD 8830M] 
[1002:682b] (rev 87) (prog-if 00 [VGA controller])
 Subsystem: Pegatron Venus LE [Radeon HD 8830M] [1b0a:90f3]
  InstallationDate: Installed on 2014-09-06 (1256 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: HP 510-p127c
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=3dd39524-3a29-4831-9f5a-6decde86d996 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.25
  SourcePackage: mesa
  Title: package libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 failed to 
install/upgrade: trying to overwrite shared 
'/usr/share/doc/libgl1-mesa-dri/changelog.Debian.gz', which is different from 
other instances of package libgl1-mesa-dri:i386
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/07/2016
  dmi.bios.vendor: AMI
  dmi.bios.version: F.14
  dmi.board.asset.tag: CNV64609PD
  dmi.board.name: 822A
  dmi.board.vendor: HP
  dmi.board.version: 00
  dmi.chassis.asset.tag: CNV64609PD
  dmi.chassis.type: 3
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnAMI:bvrF.14:bd10/07/2016:svnHP:pn510-p127c:pvr:rvnHP:rn822A:rvr00:cvnHP:ct3:cvr:
  dmi.product.family: 103C_53316J G=D
  dmi.product.name: 510-p127c
  dmi.sys.vendor: HP
  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.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sun Jan 28 01:00:43 2018
  xserver.configfile: default
  xserver.errors: RADEON(0): drmmode_do_crtc_dpms cannot get last vblank counter
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1749449/+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 1749451] [NEW] Ubuntu logs off after I try to switch application which has multiple instances

[Dambre]

Public bug reported:

I started getting this error after Ubuntu update.
Basically, when I try to switch to another instance of opened application I get 
logged off.

[  150.590975] compiz[3164]: segfault at 48 ip 7ff7704d3780 sp
7ffd5c7756e8 error 4 in libscale.so[7ff7704c1000+25000]

Other details:
Ubuntu 17.10
compiz:
  Installed: 1:0.9.13.1+17.10.20170901-0ubuntu1
  Candidate: 1:0.9.13.1+17.10.20170901-0ubuntu1
  Version table:
 *** 1:0.9.13.1+17.10.20170901-0ubuntu1 500
500 http://archive.ubuntu.com/ubuntu artful/universe amd64 Packages
500 http://archive.ubuntu.com/ubuntu artful/universe i386 Packages
100 /var/lib/dpkg/status

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


** Tags: compiz ubuntu17.10 unity

** Package changed: mesa (Ubuntu) => compiz (Ubuntu)

** Tags added: compiz

** Tags added: unity

** Tags added: ubuntu17.10

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

Title:
  Ubuntu logs off after I try to switch application which has multiple
  instances

Status in compiz package in Ubuntu:
  New

Bug description:
  I started getting this error after Ubuntu update.
  Basically, when I try to switch to another instance of opened application I 
get logged off.

  [  150.590975] compiz[3164]: segfault at 48 ip 7ff7704d3780 sp
  7ffd5c7756e8 error 4 in libscale.so[7ff7704c1000+25000]

  Other details:
  Ubuntu 17.10
  compiz:
Installed: 1:0.9.13.1+17.10.20170901-0ubuntu1
Candidate: 1:0.9.13.1+17.10.20170901-0ubuntu1
Version table:
   *** 1:0.9.13.1+17.10.20170901-0ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu artful/universe amd64 Packages
  500 http://archive.ubuntu.com/ubuntu artful/universe i386 Packages
  100 /var/lib/dpkg/status

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

[Eric Desrochers]

Seyeong,

The SRU for LP: #1740892 is not started yet, but base on nacc's comment, It 
should start soon :
https://bugs.launchpad.net/charm-hacluster/+bug/1740892/comments/47

I would suggest to wait for LP: #1740892 SRU to be completed first since
it affects package upgrade (corosync/pacemaker relation).

Additionally, IMHO, it may be "safer" to not introduce too much change
in one SRU, especially considering LP: #1740892 mark as Critical.

1) Please keep monitoring LP: #1740892 and let's wait for the SRU to turn "Fix 
Released" for Trusty.
2) Then let's start LP: #1316970 SRU right after using either "STS-Sponsor" or 
"Ubuntu Sponsors Team"

- Eric

-- 
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 1316970] Re: g_dbus memory leak in lrmd

[Seyeong Kim]

sure, no problem

Thanks eric

-- 
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 1749432] Re: cryptsetup open hangs waiting for udev cookied

[Peter Rajnoha]

Please, first check if "dmsetup udevcomplete" is called from within udev
rules.

To check that, you need to enable udevd debug mode (e.g. configure
udev_log="debug" in /etc/udev/udev.conf). Then watch systemd journal for
systemd-udevd messages:

   journalctl -f -u systemd-udevd

Then try to run the cryptsetup... You should see dmsetup "udevcomplete
call" - if not, something is wrong with udev rules so that that rule is
not executed.

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

Title:
  cryptsetup open hangs waiting for udev cookied

Status in cryptsetup package in Ubuntu:
  New
Status in lvm2 package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  systemd has a testcase to setup, open and close a luks1 volume.

  this test case has started to fail with udev 237 & cryptsetup2

  this appears to be reproducible with straight up "cryptsetup open"
  call which seems to hang in device mapper library, e.g.:

  # cryptsetup open --type luks UUID=fd41c9ba-4286-415d-95e4-960fd28b5e>
  # cryptsetup 2.0.1 processing "cryptsetup open --type luks 
UUID=fd41c9ba-4286-415d-95e4-960fd28b5e43 varcrypt --key-file /etc/varkey 
--debug --verbose"
  # Running command open.
  # Locking memory.
  # Installing SIGINT/SIGTERM handler.
  # Unblocking interruption on signal.
  # Allocating context for crypt device 
/dev/disk/by-uuid/fd41c9ba-4286-415d-95e4-960fd28b5e43.
  # Trying to open and read device 
/dev/disk/by-uuid/fd41c9ba-4286-415d-95e4-960fd28b5e43 with direct-io.
  # Initialising device-mapper backend library.
  # Trying to load any crypt type from device 
/dev/disk/by-uuid/fd41c9ba-4286-415d-95e4-960fd28b5e43.
  # Crypto backend (gcrypt 1.8.1) initialized in cryptsetup library version 
2.0.1.
  # Detected kernel Linux 4.13.0-32-generic x86_64.
  # PBKDF pbkdf2, hash sha256, time_ms 2000 (iterations 0), max_memory_kb 0, 
parallel_threads 0.
  # Reading LUKS header of size 1024 from device 
/dev/disk/by-uuid/fd41c9ba-4286-415d-95e4-960fd28b5e43
  # Key length 32, device size 18432 sectors, header size 2050 sectors.
  # Activating volume varcrypt using token -1.
  # File descriptor passphrase entry requested.
  # Activating volume varcrypt [keyslot -1] using passphrase.
  # dm version   [ opencount flush ]   [16384] (*1)
  # dm versions   [ opencount flush ]   [16384] (*1)
  # Detected dm-ioctl version 4.37.0.
  # Detected dm-crypt version 1.18.0.
  # Device-mapper backend running with UDEV support enabled.
  # dm status varcrypt  [ opencount flush ]   [16384] (*1)
  # Trying to open key slot 0 [ACTIVE_LAST].
  # Reading key slot 0 area.
  # Using userspace crypto wrapper to access keyslot area.
  Key slot 0 unlocked.
  # Calculated device size is 14336 sectors (RW), offset 4096.
  # DM-UUID is CRYPT-LUKS1-fd41c9ba4286415d95e4960fd28b5e43-varcrypt
  # Udev cookie 0xd4d4a7f (semid 65538) created
  # Udev cookie 0xd4d4a7f (semid 65538) incremented to 1
  # Udev cookie 0xd4d4a7f (semid 65538) incremented to 2
  # Udev cookie 0xd4d4a7f (semid 65538) assigned to CREATE task(0) with flags 
DISABLE_LIBRARY_FALLBACK (0x20)
  # dm create varcrypt CRYPT-LUKS1-fd41c9ba4286415d95e4960fd28b5e43-varcrypt [ 
opencount flush ]   [16384] (*1)
  # dm reload varcrypt  [ opencount flush securedata ]   [16384] (*1)
  # dm resume varcrypt  [ opencount flush securedata ]   [16384] (*1)
  # varcrypt: Stacking NODE_ADD (253,0) 0:6 0660 [trust_udev]
  # varcrypt: Stacking NODE_READ_AHEAD 256 (flags=1)
  # Udev cookie 0xd4d4a7f (semid 65538) decremented to 1
  # Udev cookie 0xd4d4a7f (semid 65538) waiting for zero

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

Seyeong, can you also clarify - are the glib2.0 patches also needed to
fix memory leaks?

-- 
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 1722313] Re: Enable auditing in util-linux.

[Launchpad Bug Tracker]

This bug was fixed in the package util-linux - 2.30.1-0ubuntu4.1

---
util-linux (2.30.1-0ubuntu4.1) artful; urgency=medium

  * Add --with-audit to rules file and libaudit-dev to build depenedencies.
The hwclock needs audit defined in order to create audit records when
time is changed. (LP: #1722313)

 -- Joy Latten   Sun, 05 Nov 2017 18:14:49
-0600

** Changed in: util-linux (Ubuntu Artful)
   Status: Fix Committed => Fix Released

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

Title:
  Enable auditing in util-linux.

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Xenial:
  Fix Released
Status in util-linux source package in Zesty:
  Fix Committed
Status in util-linux source package in Artful:
  Fix Released
Status in util-linux package in Debian:
  New

Bug description:
  [IMPACT]
  Enable auditing in util-linux. The config option, --with-audit enables 
auditing.

  Only the hwclock and the login commands within util-linux package have
  source code for auditing. But that source code is disabled by default
  and requires the config option, --with-audit to enable it. The login
  command is not built nor shipped in util-linux. Ubuntu uses the login
  command from shadow instead. Thus, only hwclock command would be
  affected by this change.

  The change would enable the hwclock command to generate an audit log
  message to /var/log/audit/audit.log whenever it changes the hardware
  clock. This message will only get logged to /var/log/audit/audit.log,
  if auditd daemon is running. Otherwise, if the auditd is not running,
  like most log messages, it will get logged to /var/log/kern.log and|or
  /var/log/syslog if these services are enabled.

  That the hwclock generates an audit message when hardware clock is
  changed is a requirement for Common Criteria EAL2 certification for
  Xenial.

  [TEST]

  This has been tested on both P8 and amd64 architectures. With the
  patch all the Common Criteria testcases pass for hwclock. Before this
  patch, the functional part of the testcase passed, but the check for
  the triggered audit records would fail. Attached the Common Criteria
  testcase below.

  Also, the util-linux package has testcases that get run during the
  build. All of these pass. Pointer to build log below.

  [REGRESSION POTENTIAL]
  The regression potential for this should be small. This change does not take 
away from any current functionality. It just adds the ability to generate an 
audit entry when system hardware clock is altered.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1722313/+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 1670408] Re: Missing apparmor rules cause tor to fail to start

[ChristianEhrhardt]

Correctly added a bug task for ntp to also be affected.
Dropping Artful (EOL)

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

** No longer affects: apparmor (Ubuntu Yakkety)

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

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

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

Title:
  apparmor base abstraction needs backport of rev 3658 to fix several
  denies (tor, ntp, ...)

Status in apparmor package in Ubuntu:
  Fix Released
Status in ntp package in Ubuntu:
  Confirmed
Status in tor package in Ubuntu:
  Invalid
Status in apparmor source package in Xenial:
  Triaged

Bug description:
  Using tor 0.2.9.9-1ubuntu1 with Linux 4.10.0-9-generic on Zesty, tor
  fails to start after installing the tor package. "systemctl status
  tor@default" reports:

  Mar 06 16:04:00 zesty systemd[1]: tor@default.service: Main process exited, 
code=killed, status=11/SEGV
  Mar 06 16:04:00 zesty systemd[1]: Failed to start Anonymizing overlay network 
for TCP.
  Mar 06 16:04:00 zesty systemd[1]: tor@default.service: Unit entered failed 
state.
  Mar 06 16:04:00 zesty systemd[1]: tor@default.service: Failed with result 
'signal'.

  There are two AppArmor denials in the kernel log:

  Mar  6 15:53:12 zesty-test kernel: [  102.699647] audit: type=1400
  audit(1488815592.268:35): apparmor="DENIED" operation="file_inherit"
  namespace="root//lxd-zesty_" profile="system_tor"
  name="/run/systemd/journal/stdout" pid=3520 comm="tor"
  requested_mask="wr" denied_mask="wr" fsuid=10 ouid=10

  Mar  6 15:53:12 zesty-test kernel: [  102.702418] audit: type=1400
  audit(1488815592.272:37): apparmor="DENIED" operation="file_mmap"
  namespace="root//lxd-zesty_" profile="system_tor"
  name="/usr/bin/tor" pid=3520 comm="tor" requested_mask="m"
  denied_mask="m" fsuid=10 ouid=10

  Workaround: add the following two lines to /etc/apparmor.d/system_tor:

  /usr/bin/tor m,
  /run/systemd/journal/stdout rw,

  I couldn't remember how to that that profile reloaded, so I rebooted,
  and after the reboot tor does start up successfully. "systemctl
  tor@default" reports it as running.

  I haven't checked to see if only one or other rule is actually
  required.

  Importance -> High since this bug makes the package unusable in its
  default configuration on Zesty. Since the AppArmor profile comes from
  Debian's 0.2.9.9-1, this should probably be fixed in Debian.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1670408/+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 1722313] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for util-linux has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Enable auditing in util-linux.

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Xenial:
  Fix Released
Status in util-linux source package in Zesty:
  Fix Committed
Status in util-linux source package in Artful:
  Fix Released
Status in util-linux package in Debian:
  New

Bug description:
  [IMPACT]
  Enable auditing in util-linux. The config option, --with-audit enables 
auditing.

  Only the hwclock and the login commands within util-linux package have
  source code for auditing. But that source code is disabled by default
  and requires the config option, --with-audit to enable it. The login
  command is not built nor shipped in util-linux. Ubuntu uses the login
  command from shadow instead. Thus, only hwclock command would be
  affected by this change.

  The change would enable the hwclock command to generate an audit log
  message to /var/log/audit/audit.log whenever it changes the hardware
  clock. This message will only get logged to /var/log/audit/audit.log,
  if auditd daemon is running. Otherwise, if the auditd is not running,
  like most log messages, it will get logged to /var/log/kern.log and|or
  /var/log/syslog if these services are enabled.

  That the hwclock generates an audit message when hardware clock is
  changed is a requirement for Common Criteria EAL2 certification for
  Xenial.

  [TEST]

  This has been tested on both P8 and amd64 architectures. With the
  patch all the Common Criteria testcases pass for hwclock. Before this
  patch, the functional part of the testcase passed, but the check for
  the triggered audit records would fail. Attached the Common Criteria
  testcase below.

  Also, the util-linux package has testcases that get run during the
  build. All of these pass. Pointer to build log below.

  [REGRESSION POTENTIAL]
  The regression potential for this should be small. This change does not take 
away from any current functionality. It just adds the ability to generate an 
audit entry when system hardware clock is altered.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1722313/+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 1722313] Re: Enable auditing in util-linux.

[Launchpad Bug Tracker]

This bug was fixed in the package util-linux - 2.27.1-6ubuntu3.4

---
util-linux (2.27.1-6ubuntu3.4) xenial; urgency=medium

  * Add --with-audit to rules file and libaudit-dev to build depenedencies.
The hwclock needs audit defined in order to create audit records when
time is changed. (LP: #1722313)

 -- Joy Latten   Fri, 03 Nov 2017 17:46:07
-0500

** Changed in: util-linux (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  Enable auditing in util-linux.

Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Xenial:
  Fix Released
Status in util-linux source package in Zesty:
  Fix Committed
Status in util-linux source package in Artful:
  Fix Released
Status in util-linux package in Debian:
  New

Bug description:
  [IMPACT]
  Enable auditing in util-linux. The config option, --with-audit enables 
auditing.

  Only the hwclock and the login commands within util-linux package have
  source code for auditing. But that source code is disabled by default
  and requires the config option, --with-audit to enable it. The login
  command is not built nor shipped in util-linux. Ubuntu uses the login
  command from shadow instead. Thus, only hwclock command would be
  affected by this change.

  The change would enable the hwclock command to generate an audit log
  message to /var/log/audit/audit.log whenever it changes the hardware
  clock. This message will only get logged to /var/log/audit/audit.log,
  if auditd daemon is running. Otherwise, if the auditd is not running,
  like most log messages, it will get logged to /var/log/kern.log and|or
  /var/log/syslog if these services are enabled.

  That the hwclock generates an audit message when hardware clock is
  changed is a requirement for Common Criteria EAL2 certification for
  Xenial.

  [TEST]

  This has been tested on both P8 and amd64 architectures. With the
  patch all the Common Criteria testcases pass for hwclock. Before this
  patch, the functional part of the testcase passed, but the check for
  the triggered audit records would fail. Attached the Common Criteria
  testcase below.

  Also, the util-linux package has testcases that get run during the
  build. All of these pass. Pointer to build log below.

  [REGRESSION POTENTIAL]
  The regression potential for this should be small. This change does not take 
away from any current functionality. It just adds the ability to generate an 
audit entry when system hardware clock is altered.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1722313/+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 1749472] [NEW] mesa 18.0.0 will cause rendering errors in Qt applications

[Rik Mills]

Public bug reported:

From: https://bugreports.qt.io/browse/QTBUG-66348

** extract **

The `QOpenGLShaderProgram` class in Qt can be used to compile and link
OpenGL shaders. If the `GL_ARB_get_program_binary` OpenGL extension is
available, it can cache those shaders on disk (~/.cache/qtshadercache).
The i965 driver in Mesa supports this extension since version 18.0.0.

When the shader is loaded using the `glProgramBinary` function, OpenGL
can refuse it if for example some hardware or software component
changed. Mesa refuses binaries that were created by any other build of
Mesa (using among other things the build_id of the library).

If the shader is refused, Qt should fallback to compiling it from
sources, but it incorrectly calls glLinkProgram first. The glLinkProgram
succeeds, because it actually links 0 shaders together. That is allowed
in OpenGL compatibility profile and the resulting program works as a
fixed pipeline. Which of course does not render as expected.

This causes rendering errors in Qt applications every time Mesa is
updated since version 18.0.0. For example white screen in sddm.

This issue was originally reported in openSUSE
(https://bugzilla.opensuse.org/show_bug.cgi?id=1080578).

** end extract **

As this potentially effects Qt applications, and could even render
display manager login unusable, this should be a blocking bug in mesa
and Qt until Qt mitigations patches pass codereview and can be included
in Qtbase for 18.04.

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

** Affects: qtbase-opensource-src (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: mesa (Ubuntu Bionic)
 Importance: Undecided
 Status: New

** Affects: qtbase-opensource-src (Ubuntu Bionic)
 Importance: Undecided
 Status: New


** Tags: block-proposed

** Also affects: qtbase-opensource-src (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: mesa (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: qtbase-opensource-src (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Tags added: block-proposed

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

Title:
  mesa 18.0.0 will cause rendering errors in Qt applications

Status in mesa package in Ubuntu:
  New
Status in qtbase-opensource-src package in Ubuntu:
  New
Status in mesa source package in Bionic:
  New
Status in qtbase-opensource-src source package in Bionic:
  New

Bug description:
  From: https://bugreports.qt.io/browse/QTBUG-66348

  ** extract **

  The `QOpenGLShaderProgram` class in Qt can be used to compile and link
  OpenGL shaders. If the `GL_ARB_get_program_binary` OpenGL extension is
  available, it can cache those shaders on disk
  (~/.cache/qtshadercache). The i965 driver in Mesa supports this
  extension since version 18.0.0.

  When the shader is loaded using the `glProgramBinary` function, OpenGL
  can refuse it if for example some hardware or software component
  changed. Mesa refuses binaries that were created by any other build of
  Mesa (using among other things the build_id of the library).

  If the shader is refused, Qt should fallback to compiling it from
  sources, but it incorrectly calls glLinkProgram first. The
  glLinkProgram succeeds, because it actually links 0 shaders together.
  That is allowed in OpenGL compatibility profile and the resulting
  program works as a fixed pipeline. Which of course does not render as
  expected.

  This causes rendering errors in Qt applications every time Mesa is
  updated since version 18.0.0. For example white screen in sddm.

  This issue was originally reported in openSUSE
  (https://bugzilla.opensuse.org/show_bug.cgi?id=1080578).

  ** end extract **

  As this potentially effects Qt applications, and could even render
  display manager login unusable, this should be a blocking bug in mesa
  and Qt until Qt mitigations patches pass codereview and can be
  included in Qtbase for 18.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1749472/+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 1749389] Re: ntpdate lock apparmor deny

[ChristianEhrhardt]

Bionic - ok
SRU Template - ok
Debdiff for X/T checked - ok
Tested X/A upload from ppa - ok.

I Identified another issue in the log as bug 1670408 which needs a fix in 
apparmor - not ntp.
That means this is ok to be uploaded (not gated by that finding).

** Description changed:

  [Impact]
  
-  * Apparmor denies access to lock it shares with ntpdate to ensure no 
-issues due to concurrent access
+  * Apparmor denies access to lock it shares with ntpdate to ensure no
+    issues due to concurrent access
  
  [Test Case]
  
-  1. get a container of target release
-  2. install ntp
- apt install ntp
-  3. watch dmesg on container-host
- dmesg -w 
-  4. restart ntp in container
- systemctl restart ntp
-  => see (or no more after fix) apparmor denie:
- apparmor="DENIED" operation="file_inherit" profile="/usr/sbin/ntpd" 
name="/run/lock/ntpdate" pid=30113 comm="ntpd" requested_mask="w" 
denied_mask="w"
+  1. get a container of target release
+  2. install ntp
+ apt install ntp
+  3. watch dmesg on container-host
+ dmesg -w
+  4. restart ntp in container
+ systemctl restart ntp
+  => see (or no more after fix) apparmor denie:
+ apparmor="DENIED" operation="file_inherit" profile="/usr/sbin/ntpd" 
name="/run/lock/ntpdate" pid=30113 comm="ntpd" requested_mask="w" 
denied_mask="w"
+ Note: to not be mislead, on xenial there is a remaining stdout appamor 
+ issue which is bug 1670408
  
  [Regression Potential]
  
-  * we are only slightly opening up the apparmor profile, but none of the 
-changes poses a security risk so regression potential on it's own 
-should be close to zero.
+  * we are only slightly opening up the apparmor profile, but none of the
+    changes poses a security risk so regression potential on it's own
+    should be close to zero.
  
-  * There is a potential issue if the locking (that now can succeed) would 
-e.g. no more be freed up or the action behind the locking would cause 
-issues.
+  * There is a potential issue if the locking (that now can succeed) would
+    e.g. no more be freed up or the action behind the locking would cause
+    issues.
  
  [Other Info]
-  
-  * n/a
  
+  * n/a
  
- On start/restart nto has an error in apparmor due to the locking it tries to 
avoid issues running concurrently with ntpdate.
+ On start/restart nto has an error in apparmor due to the locking it
+ tries to avoid issues running concurrently with ntpdate.
  
  That looks like:
  apparmor="DENIED" operation="file_inherit" profile="/usr/sbin/ntpd" 
name="/run/lock/ntpdate" pid=30113 comm="ntpd" requested_mask="w" 
denied_mask="w"
  
  The rule we need is:
  /run/lock/ntpdate wk,

** Changed in: ntp (Ubuntu Xenial)
   Status: Triaged => In Progress

** Changed in: ntp (Ubuntu Artful)
   Status: Triaged => In Progress

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

Title:
  ntpdate lock apparmor deny

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

Bug description:
  [Impact]

   * Apparmor denies access to lock it shares with ntpdate to ensure no
     issues due to concurrent access

  [Test Case]

   1. get a container of target release
   2. install ntp
  apt install ntp
   3. watch dmesg on container-host
  dmesg -w
   4. restart ntp in container
  systemctl restart ntp
   => see (or no more after fix) apparmor denie:
  apparmor="DENIED" operation="file_inherit" profile="/usr/sbin/ntpd" 
name="/run/lock/ntpdate" pid=30113 comm="ntpd" requested_mask="w" 
denied_mask="w"
  Note: to not be mislead, on xenial there is a remaining stdout appamor 
  issue which is bug 1670408

  [Regression Potential]

   * we are only slightly opening up the apparmor profile, but none of the
     changes poses a security risk so regression potential on it's own
     should be close to zero.

   * There is a potential issue if the locking (that now can succeed) would
     e.g. no more be freed up or the action behind the locking would cause
     issues.

  [Other Info]

   * n/a

  On start/restart nto has an error in apparmor due to the locking it
  tries to avoid issues running concurrently with ntpdate.

  That looks like:
  apparmor="DENIED" operation="file_inherit" profile="/usr/sbin/ntpd" 
name="/run/lock/ntpdate" pid=30113 comm="ntpd" requested_mask="w" 
denied_mask="w"

  The rule we need is:
  /run/lock/ntpdate wk,

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1749389/+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 1749389] Re: ntpdate lock apparmor deny

[ChristianEhrhardt]

fix in SRU queue (Atrful/Xenial) for review by the SRU Team

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

Title:
  ntpdate lock apparmor deny

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

Bug description:
  [Impact]

   * Apparmor denies access to lock it shares with ntpdate to ensure no
     issues due to concurrent access

  [Test Case]

   1. get a container of target release
   2. install ntp
  apt install ntp
   3. watch dmesg on container-host
  dmesg -w
   4. restart ntp in container
  systemctl restart ntp
   => see (or no more after fix) apparmor denie:
  apparmor="DENIED" operation="file_inherit" profile="/usr/sbin/ntpd" 
name="/run/lock/ntpdate" pid=30113 comm="ntpd" requested_mask="w" 
denied_mask="w"
  Note: to not be mislead, on xenial there is a remaining stdout appamor 
  issue which is bug 1670408

  [Regression Potential]

   * we are only slightly opening up the apparmor profile, but none of the
     changes poses a security risk so regression potential on it's own
     should be close to zero.

   * There is a potential issue if the locking (that now can succeed) would
     e.g. no more be freed up or the action behind the locking would cause
     issues.

  [Other Info]

   * n/a

  On start/restart nto has an error in apparmor due to the locking it
  tries to avoid issues running concurrently with ntpdate.

  That looks like:
  apparmor="DENIED" operation="file_inherit" profile="/usr/sbin/ntpd" 
name="/run/lock/ntpdate" pid=30113 comm="ntpd" requested_mask="w" 
denied_mask="w"

  The rule we need is:
  /run/lock/ntpdate wk,

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1749389/+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 1749247] Re: Spurious SEGV running inside kvm

[Howard Chu]

Will try to come up with a minimal reproducer. Currently it takes
several hours to run the complete test, and a few hours before the SEGV
occurs. But the stack trace is always identical when it happens. In
multiple runs, it always succeeds on the host and always fails in the
VM.

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

Title:
  Spurious SEGV running inside kvm

Status in openldap package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Incomplete

Bug description:
  Running a continuous stream of operations against OpenLDAP slapd
  eventually causes a SEGV in liblber, in a segment of code that cannot
  fail:

   gdb /opt/symas/lib64/slapd CoreDump 
  GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.5) 7.11.1
  Copyright (C) 2016 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .
  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from /opt/symas/lib64/slapd...done.
  [New LWP 5472]
  [New LWP 5468]
  [New LWP 5524]
  [New LWP 5471]
  [New LWP 5469]
  [New LWP 5507]
  [New LWP 5510]
  [New LWP 5470]
  [New LWP 5506]
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  Core was generated by `/opt/symas/lib64/slapd -u root -g root -h ldap:///'.
  Program terminated with signal SIGSEGV, Segmentation fault.
  #0  0x7f4e2c9f0160 in ber_dupbv_x (dst=0x196b268, src=0x7f25f8001070, 
ctx=0x0) at /home/build/git/sold-master/openldap/libraries/liblber/memory.c:513
  513 new->bv_val[src->bv_len] = '\0';
  [Current thread is 1 (Thread 0x7f260e242700 (LWP 5472))]
  (gdb) l 500
  495 if(( new = ber_memalloc_x( sizeof(struct berval), ctx 
)) == NULL ) {
  496 return NULL;
  497 }
  498 }
  499
  500 if ( src->bv_val == NULL ) {
  501 new->bv_val = NULL;
  502 new->bv_len = 0;
  503 return new;
  504 }
  (gdb) 
  505
  506 if(( new->bv_val = ber_memalloc_x( src->bv_len + 1, ctx )) == 
NULL ) {
  507 if ( !dst )
  508 ber_memfree_x( new, ctx );
  509 return NULL;
  510 }
  511
  512 AC_MEMCPY( new->bv_val, src->bv_val, src->bv_len );
  513 new->bv_val[src->bv_len] = '\0';
  514 new->bv_len = src->bv_len;
  (gdb) p *new
  $1 = {bv_len = 0, bv_val = 0x0}
  (gdb) p *src
  $2 = {bv_len = 36, bv_val = 0x7f268ccc7bee }
  (gdb) 

  
  At line 506 we allocate some memory and check for a failure (returning NULL) 
and leave the function at line 509 if there was a failure. The allocation is 
for 37 bytes of memory and a memcpy into that memory succeeds on line 512. The 
SEGV occurs at line 513 and the pointer that was just returned from the 
allocator is NULL at this point. There are no other active threads that could 
be stomping on memory, there's no stack overrun or any other misbehavior that 
can account for it. Also, the identical test sequence completes without 
incident when running on the host OS instead of under kvm.
  (The src->bv_val pointer points to valid data at the time of the crash; it's 
just residing in a mmap'd file and that mapping isn't preserved in the 
coredump. So ignore gdb's error there.)

  Something in kvm is writing zeroes over a field of memory after we
  already checked that it was non-zero.

  This is on 
  Linux anvil1 4.4.0-112-generic #135-Ubuntu SMP Fri Jan 19 11:48:36 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Both the host and the guest VM are on identical OS revision.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1749247/+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 1741227] Re: apparmor denial to several paths to binaries

[ChristianEhrhardt]

fix in SRU queue (Artful) for review by the SRU Team

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

Title:
  apparmor denial to several paths to binaries

Status in ntp package in Ubuntu:
  Fix Released
Status in ntp source package in Artful:
  Fix Committed

Bug description:
  [Impact]

   * Apparmor denies access to bin directories which the option parsing code 
 of ntp touches.

  [Test Case]

   1. get a container of target release
   2. install ntp
  apt install ntp
   3. watch dmesg on container-host
  dmesg -w
   4. restart ntp in container
  systemctl restart ntp
   => see (or no more after fix) apparmor denie:
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/sbin/" pid=23933 comm="ntpd" requested_mask="r" denied_mask="r"
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/bin/" pid=23933 comm="ntpd" requested_mask="r" denied_mask="r"

  [Regression Potential]

   * we are only slightly opening up the apparmor profile, but none of the
 changes poses a security risk so regression potential on it's own
 should be close to zero.

   * we discussed if this would be a security risk but came to the 
 conclusion that r-only should be ok (the same content anyone can grab 
 from the archive by installing the packages)

  [Other Info]

   * n/a

  Issue shows up (non fatal) as:
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/sbin/" pid=23933 comm="ntpd" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/bin/" pid=23933 comm="ntpd" requested_mask="r" denied_mask="r" 
fsuid=0 ouid=0

  Since non crit this is mostyl about many of us being curious why it
  actually does do it :-)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1741227/+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 1670408] Re: Missing apparmor rules cause tor to fail to start

[ChristianEhrhardt]

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

** Summary changed:

- Missing apparmor rules cause tor to fail to start
+ apparmor base abstraction needs backport of rev 3658 to fix several denies 
(tor, ntp, ...)

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

Title:
  apparmor base abstraction needs backport of rev 3658 to fix several
  denies (tor, ntp, ...)

Status in apparmor package in Ubuntu:
  Fix Released
Status in ntp package in Ubuntu:
  Confirmed
Status in tor package in Ubuntu:
  Invalid
Status in apparmor source package in Xenial:
  Triaged

Bug description:
  Using tor 0.2.9.9-1ubuntu1 with Linux 4.10.0-9-generic on Zesty, tor
  fails to start after installing the tor package. "systemctl status
  tor@default" reports:

  Mar 06 16:04:00 zesty systemd[1]: tor@default.service: Main process exited, 
code=killed, status=11/SEGV
  Mar 06 16:04:00 zesty systemd[1]: Failed to start Anonymizing overlay network 
for TCP.
  Mar 06 16:04:00 zesty systemd[1]: tor@default.service: Unit entered failed 
state.
  Mar 06 16:04:00 zesty systemd[1]: tor@default.service: Failed with result 
'signal'.

  There are two AppArmor denials in the kernel log:

  Mar  6 15:53:12 zesty-test kernel: [  102.699647] audit: type=1400
  audit(1488815592.268:35): apparmor="DENIED" operation="file_inherit"
  namespace="root//lxd-zesty_" profile="system_tor"
  name="/run/systemd/journal/stdout" pid=3520 comm="tor"
  requested_mask="wr" denied_mask="wr" fsuid=10 ouid=10

  Mar  6 15:53:12 zesty-test kernel: [  102.702418] audit: type=1400
  audit(1488815592.272:37): apparmor="DENIED" operation="file_mmap"
  namespace="root//lxd-zesty_" profile="system_tor"
  name="/usr/bin/tor" pid=3520 comm="tor" requested_mask="m"
  denied_mask="m" fsuid=10 ouid=10

  Workaround: add the following two lines to /etc/apparmor.d/system_tor:

  /usr/bin/tor m,
  /run/systemd/journal/stdout rw,

  I couldn't remember how to that that profile reloaded, so I rebooted,
  and after the reboot tor does start up successfully. "systemctl
  tor@default" reports it as running.

  I haven't checked to see if only one or other rule is actually
  required.

  Importance -> High since this bug makes the package unusable in its
  default configuration on Zesty. Since the AppArmor profile comes from
  Debian's 0.2.9.9-1, this should probably be fixed in Debian.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1670408/+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 1741227] Re: apparmor denial to several paths to binaries

[ChristianEhrhardt]

Bionic - ok
SRU Template - ok
Debdiff for X/T checked - ok
Tested A upload from ppa - ok.
(This issue in particular doesn't apply to Xenial, so dropping this task)

** No longer affects: ntp (Ubuntu Xenial)

** Changed in: ntp (Ubuntu Artful)
   Status: Triaged => In Progress

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

Title:
  apparmor denial to several paths to binaries

Status in ntp package in Ubuntu:
  Fix Released
Status in ntp source package in Artful:
  Fix Committed

Bug description:
  [Impact]

   * Apparmor denies access to bin directories which the option parsing code 
 of ntp touches.

  [Test Case]

   1. get a container of target release
   2. install ntp
  apt install ntp
   3. watch dmesg on container-host
  dmesg -w
   4. restart ntp in container
  systemctl restart ntp
   => see (or no more after fix) apparmor denie:
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/sbin/" pid=23933 comm="ntpd" requested_mask="r" denied_mask="r"
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/bin/" pid=23933 comm="ntpd" requested_mask="r" denied_mask="r"

  [Regression Potential]

   * we are only slightly opening up the apparmor profile, but none of the
 changes poses a security risk so regression potential on it's own
 should be close to zero.

   * we discussed if this would be a security risk but came to the 
 conclusion that r-only should be ok (the same content anyone can grab 
 from the archive by installing the packages)

  [Other Info]

   * n/a

  Issue shows up (non fatal) as:
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/sbin/" pid=23933 comm="ntpd" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/bin/" pid=23933 comm="ntpd" requested_mask="r" denied_mask="r" 
fsuid=0 ouid=0

  Since non crit this is mostyl about many of us being curious why it
  actually does do it :-)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1741227/+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 1616651] Re: gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell': free(): invalid pointer: 0x00000000082dcf30 *** in g_strfreev() from g_themed_icon_finalize() from g

[chris pollock]

Gnome shell crashed while updating these packages:

Start-Date: 2018-02-14  08:14:44
Commandline: apt-get -y install libegl1-mesa libegl1-mesa-dev libgbm-dev 
libgbm1 libgl1-mesa-dev libgl1-mesa-dri libgl1-mesa-glx libglapi-mesa 
libgles2-mesa libgles2-mesa-dev libosmesa6 libwayland-egl1-mesa libxatracker2 
mesa-common-dev mesa-vdpau-drivers
Upgrade: libgles2-mesa:amd64 (17.2.4-0ubuntu1~16.04.4, 
17.2.8-0ubuntu0~16.04.1), libegl1-mesa-dev:amd64 (17.2.4-0ubuntu1~16.04.4, 
17.2.8-0ubuntu0~16.04.1), libglapi-mesa:amd64 (17.2.4-0ubuntu1~16.04.4, 
17.2.8-0ubuntu0~16.04.1), libglapi-mesa:i386 (17.2.4-0ubuntu1~16.04.4, 
17.2.8-0ubuntu0~16.04.1), mesa-common-dev:amd64 (17.2.4-0ubuntu1~16.04.4, 
17.2.8-0ubuntu0~16.04.1), libxatracker2:amd64 (17.2.4-0ubuntu1~16.04.4, 
17.2.8-0ubuntu0~16.04.1), libegl1-mesa:amd64 (17.2.4-0ubuntu1~16.04.4, 
17.2.8-0ubuntu0~16.04.1), libgbm1:amd64 (17.2.4-0ubuntu1~16.04.4, 
17.2.8-0ubuntu0~16.04.1), libwayland-egl1-mesa:amd64 (17.2.4-0ubuntu1~16.04.4, 
17.2.8-0ubuntu0~16.04.1), libgles2-mesa-dev:amd64 (17.2.4-0ubuntu1~16.04.4, 
17.2.8-0ubuntu0~16.04.1), libgl1-mesa-dev:amd64 (17.2.4-0ubuntu1~16.04.4, 
17.2.8-0ubuntu0~16.04.1), libgl1-mesa-dri:amd64 (17.2.4-0ubuntu1~16.04.4, 
17.2.8-0ubuntu0~16.04.1), libgl1-mesa-dri:i386 (17.2.4-0ubuntu1~16.04.4, 
17.2.8-0ubuntu0~16.04.1), libosmesa6:amd64 (17.2.4-0ubuntu1~16.04.4, 
17.2.8-0ubuntu0~16.04.1), libosmesa6:i386 (17.2.4-0ubuntu1~16.04.4, 
17.2.8-0ubuntu0~16.04.1), libgl1-mesa-glx:amd64 (17.2.4-0ubuntu1~16.04.4, 
17.2.8-0ubuntu0~16.04.1), libgl1-mesa-glx:i386 (17.2.4-0ubuntu1~16.04.4, 
17.2.8-0ubuntu0~16.04.1), libgbm-dev:amd64 (17.2.4-0ubuntu1~16.04.4, 
17.2.8-0ubuntu0~16.04.1), mesa-vdpau-drivers:amd64 (17.2.4-0ubuntu1~16.04.4, 
17.2.8-0ubuntu0~16.04.1), mesa-vdpau-drivers:i386 (17.2.4-0ubuntu1~16.04.4, 
17.2.8-0ubuntu0~16.04.1)
End-Date: 2018-02-14  08:19:10

Here is a link to output of /var/log/syslog on PasteBin -
https://pastebin.com/q7qsWCKq

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

Title:
  gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell':
  free(): invalid pointer: 0x082dcf30 *** in g_strfreev() from
  g_themed_icon_finalize() from g_object_unref() from
  desktop_entry_unref()

Status in libgweather:
  Fix Released
Status in Ubuntu GNOME:
  Fix Committed
Status in gnome-shell package in Ubuntu:
  Invalid
Status in libgweather package in Ubuntu:
  Fix Released
Status in libgweather source package in Zesty:
  In Progress

Bug description:
  
  [Impact] 
  Backport git patch that fixes memory corruption in libgweather that is 
causing gnome-shell to crash. This is particularly bad on wayland as it causes 
the user to lose their sessions

  I believe this should also fix bug 1688208 and potentially a couple of
  other high ranking crashes on errors.ubuntu.com. I have not however
  found reliable reproducers for those other bugs.

  [Test Case]
  After update of libgweather
  1. Ensure org.gnome.Weather.Application locations is not set (as per default 
setting)
  2. Disable Location Services
  3. gnome-shell should not crash

  [Regression Potential]
  Low, the patch merely fixes a refcounting bug. Given the high impact of this 
bug, this is an important fix.
   
  === original bug report 
  This happened while installing Xfce with Synaptic.

  chris@localhost:~$ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  chris@localhost:~$ apt-cache policy gnome-shell
  gnome-shell:
    Installed: 3.18.5-0ubuntu0.1
    Candidate: 3.18.5-0ubuntu0.1
    Version table:
   *** 3.18.5-0ubuntu0.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   3.18.4-0ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  ProblemType: CrashDistroRelease: Ubuntu 16.04
  Package: gnome-shell 3.18.5-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AssertionMessage: *** Error in `/usr/bin/gnome-shell': free(): invalid 
pointer: 0x082dcf30 ***
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Wed Aug 24 16:21:37 2016
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2014-10-24 (670 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6SourcePackage: gnome-shell
  StacktraceTop:
   __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7fabad1e06b0 "*** 
Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175
   malloc_printerr (ar_ptr=, ptr=, 
str=0x7fabad1dd48f "free(): invalid p

[Touch-packages] [Bug 1749389] Re: ntpdate lock apparmor deny

[Chris J Arges]

Hello ChristianEhrhardt, or anyone else affected,

Accepted ntp into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/ntp/1:4.2.8p4+dfsg-
3ubuntu5.8 in a few hours, and then in the -proposed repository.

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

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

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

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

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

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

** Tags added: verification-needed-artful

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

Title:
  ntpdate lock apparmor deny

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

Bug description:
  [Impact]

   * Apparmor denies access to lock it shares with ntpdate to ensure no
     issues due to concurrent access

  [Test Case]

   1. get a container of target release
   2. install ntp
  apt install ntp
   3. watch dmesg on container-host
  dmesg -w
   4. restart ntp in container
  systemctl restart ntp
   => see (or no more after fix) apparmor denie:
  apparmor="DENIED" operation="file_inherit" profile="/usr/sbin/ntpd" 
name="/run/lock/ntpdate" pid=30113 comm="ntpd" requested_mask="w" 
denied_mask="w"
  Note: to not be mislead, on xenial there is a remaining stdout appamor 
  issue which is bug 1670408

  [Regression Potential]

   * we are only slightly opening up the apparmor profile, but none of the
     changes poses a security risk so regression potential on it's own
     should be close to zero.

   * There is a potential issue if the locking (that now can succeed) would
     e.g. no more be freed up or the action behind the locking would cause
     issues.

  [Other Info]

   * n/a

  On start/restart nto has an error in apparmor due to the locking it
  tries to avoid issues running concurrently with ntpdate.

  That looks like:
  apparmor="DENIED" operation="file_inherit" profile="/usr/sbin/ntpd" 
name="/run/lock/ntpdate" pid=30113 comm="ntpd" requested_mask="w" 
denied_mask="w"

  The rule we need is:
  /run/lock/ntpdate wk,

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1749389/+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 1741227] Re: apparmor denial to several paths to binaries

[Chris J Arges]

Hello ChristianEhrhardt, or anyone else affected,

Accepted ntp into artful-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/ntp/1:4.2.8p10+dfsg-
5ubuntu3.2 in a few hours, and then in the -proposed repository.

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

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

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

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

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

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

Title:
  apparmor denial to several paths to binaries

Status in ntp package in Ubuntu:
  Fix Released
Status in ntp source package in Artful:
  Fix Committed

Bug description:
  [Impact]

   * Apparmor denies access to bin directories which the option parsing code 
 of ntp touches.

  [Test Case]

   1. get a container of target release
   2. install ntp
  apt install ntp
   3. watch dmesg on container-host
  dmesg -w
   4. restart ntp in container
  systemctl restart ntp
   => see (or no more after fix) apparmor denie:
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/sbin/" pid=23933 comm="ntpd" requested_mask="r" denied_mask="r"
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/bin/" pid=23933 comm="ntpd" requested_mask="r" denied_mask="r"

  [Regression Potential]

   * we are only slightly opening up the apparmor profile, but none of the
 changes poses a security risk so regression potential on it's own
 should be close to zero.

   * we discussed if this would be a security risk but came to the 
 conclusion that r-only should be ok (the same content anyone can grab 
 from the archive by installing the packages)

  [Other Info]

   * n/a

  Issue shows up (non fatal) as:
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/sbin/" pid=23933 comm="ntpd" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/bin/" pid=23933 comm="ntpd" requested_mask="r" denied_mask="r" 
fsuid=0 ouid=0

  Since non crit this is mostyl about many of us being curious why it
  actually does do it :-)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1741227/+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 1749389] Please test proposed package

[Chris J Arges]

Hello ChristianEhrhardt, or anyone else affected,

Accepted ntp into artful-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/ntp/1:4.2.8p10+dfsg-
5ubuntu3.2 in a few hours, and then in the -proposed repository.

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

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

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

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

Title:
  ntpdate lock apparmor deny

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

Bug description:
  [Impact]

   * Apparmor denies access to lock it shares with ntpdate to ensure no
     issues due to concurrent access

  [Test Case]

   1. get a container of target release
   2. install ntp
  apt install ntp
   3. watch dmesg on container-host
  dmesg -w
   4. restart ntp in container
  systemctl restart ntp
   => see (or no more after fix) apparmor denie:
  apparmor="DENIED" operation="file_inherit" profile="/usr/sbin/ntpd" 
name="/run/lock/ntpdate" pid=30113 comm="ntpd" requested_mask="w" 
denied_mask="w"
  Note: to not be mislead, on xenial there is a remaining stdout appamor 
  issue which is bug 1670408

  [Regression Potential]

   * we are only slightly opening up the apparmor profile, but none of the
     changes poses a security risk so regression potential on it's own
     should be close to zero.

   * There is a potential issue if the locking (that now can succeed) would
     e.g. no more be freed up or the action behind the locking would cause
     issues.

  [Other Info]

   * n/a

  On start/restart nto has an error in apparmor due to the locking it
  tries to avoid issues running concurrently with ntpdate.

  That looks like:
  apparmor="DENIED" operation="file_inherit" profile="/usr/sbin/ntpd" 
name="/run/lock/ntpdate" pid=30113 comm="ntpd" requested_mask="w" 
denied_mask="w"

  The rule we need is:
  /run/lock/ntpdate wk,

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1749389/+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 1661295] Re: [vmware] mir 0.26 failing with nested server in protobuf when bringing up NestedDisplay [CHECK failed: (index) >= (0)]

[Gerry Boland]

Problem is that the "real" KMS platform is unable to determine the
current mode when running on VMware, leaving the current_mode_index at
an invalid value of UINTMAX, which is being passed through to the nested
platform.

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

Title:
  [vmware] mir 0.26 failing with nested server in protobuf when bringing
  up NestedDisplay [CHECK failed: (index) >= (0)]

Status in Mir:
  New
Status in mir package in Ubuntu:
  New

Bug description:
  Setup:
  1. VMWare 12, with the following line added to ~/.vmware/preferences:
    mks.gl.allowBlacklistedDrivers = "TRUE"
  2. Created a VM with Xenial + Overlay PPA
  3. Installed unity8-desktop-session-mir, rebooted
  4. Tried to log in to a Unity8 session

  Problem: Unity8 fails to start, but is exiting cleanly as opposed to
  crashing. The following is all that is printed of the log:

  [2017-02-02:07:18:21.137] qtmir.screens: ScreensModel::ScreensModel
  [2017-02-02 07:18:21.143261] mirplatform: Found graphics driver: mir:mesa-kms 
(version 0.26.0)
  [2017-02-02 07:18:21.143413] mirplatform: Found graphics driver: mir:mesa-x11 
(version 0.26.0)
  [2017-02-02 07:18:21.144063] mirserver: Starting
  [libprotobuf FATAL /usr/include/google/protobuf/repeated_field.h:885] CHECK 
failed: (index) >= (0):
  [2017-02-02:07:18:21.165] CHECK failed: (index) >= (0):
  initctl: No such variable: UNITY_MIR_SOCKET

  USC is coming up correctly however.

  If I try to launch miral-shell manually, I get similar error:

  MIR_SOCKET=$XDG_RUNTIME_DIR/mir_socket MIR_SERVER_PROMPT_FILE=1 
MIR_SERVER_HOST_SOCKET=/run/mir_socket 
MIR_SERVER_FILE=$XDG_RUNTIME_DIR/mir_socket MIR_SERVER_NAME=session-0 
miral-shell
  [2017-02-02 07:55:56.686669] mirplatform: Found graphics driver: mir:mesa-kms 
(version 0.26.0)
  [2017-02-02 07:55:56.687395] mirplatform: Found graphics driver: mir:mesa-x11 
(version 0.26.0)
  [2017-02-02 07:55:56.689036] mirserver: Starting
  [libprotobuf FATAL /usr/include/google/protobuf/repeated_field.h:885] CHECK 
failed: (index) >= (0):
  ERROR: Dynamic exception type: google::protobuf::FatalException
  std::exception::what: CHECK failed: (index) >= (0):

  I tried to grab a backtrace at the location of the last call to
  /usr/include/google/protobuf/repeated_field.h:885 which might print
  the error:

  http://pastebin.ubuntu.com/23911595/

  Thread 4 "MirServerThread" hit Breakpoint 1, 
mir::protobuf::DisplayOutput::SerializeWithCachedSizes(google::protobuf::io::CodedOutputStream*)
 const (this=0x7fffd804f7a0, output=0x7fffe0848280) at 
/build/mir-Hd65rv/mir-0.26.0+16.04.20170126.3/obj-x86_64-linux-gnu/src/protobuf/mir_protobuf.pb.cc:8417
  8417  in 
/build/mir-Hd65rv/mir-0.26.0+16.04.20170126.3/obj-x86_64-linux-gnu/src/protobuf/mir_protobuf.pb.cc
  #0  
mir::protobuf::DisplayOutput::SerializeWithCachedSizes(google::protobuf::io::CodedOutputStream*)
 const (this=0x7fffd804f7a0, output=0x7fffe0848280) at 
/build/mir-Hd65rv/mir-0.26.0+16.04.20170126.3/obj-x86_64-linux-gnu/src/protobuf/mir_protobuf.pb.cc:8417
  #1  0x7fffeba5c3e8 in 
mir::protobuf::DisplayConfiguration::SerializeWithCachedSizes(google::protobuf::io::CodedOutputStream*)
 const (this=0x7fffd804b830, output=0x7fffe0848280) at 
/build/mir-Hd65rv/mir-0.26.0+16.04.20170126.3/obj-x86_64-linux-gnu/src/protobuf/mir_protobuf.pb.cc:11436
  #2  0x7fffeb38a615 in 
google::protobuf::MessageLite::SerializeWithCachedSizesToArray(unsigned char*) 
const () from /usr/lib/x86_64-linux-gnu/libprotobuf-lite.so.9
  #3  0x7fffed696798 in mir_blob_from_display_config () from 
/usr/lib/x86_64-linux-gnu/libmirclient.so.9
  #4  0x7fffed1d7ec6 in copy_config (conf=) at 
/build/mir-Hd65rv/mir-0.26.0+16.04.20170126.3/src/server/graphics/nested/nested_display_configuration.cpp:44
  #5  __base_ctor  (other=warning: RTTI symbol not found for class 
'mir::graphics::nested::NestedDisplayConfiguration'
  ..., this=0x7fffd8047300) at 
/build/mir-Hd65rv/mir-0.26.0+16.04.20170126.3/src/server/graphics/nested/nested_display_configuration.cpp:61

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1661295/+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 108366] Re: Totem unable to add to playlist after selecting unreadable location

[Sebastien Bacher]

** Bug watch added: GNOME Bug Tracker #382479
   https://bugzilla.gnome.org/show_bug.cgi?id=382479

** Changed in: gtk
   Importance: Low => Unknown

** Changed in: gtk
   Status: Invalid => Unknown

** Changed in: gtk
 Remote watch: GNOME Bug Tracker #432904 => GNOME Bug Tracker #382479

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

Title:
  Totem unable to add to playlist after selecting unreadable location

Status in GTK+:
  Unknown
Status in Totem:
  Invalid
Status in gtk+2.0 package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: totem

  When adding to the playlist using the sidebar interface, totem
  defaults to the directory of the last selected file when prompting for
  a new file.  When that directory is unreadable (e.g.
  http://www.gearwire.com/media/ (after adding
  http://www.gearwire.com/media/seymour-duncan-guitar-
  pickups-1-musikmesse.wmv by pasting into the location control in the
  last add)), totem presents the message "error accessing
  'http://www.gearwire.com/media': Access denied".  If this dialog is
  closed, totem is unable to add new files to the playlist (even when
  pasting the Location) until a readable base location (e.g. the home
  directory) is selected.

  In functional terms:

  Observed Behaviour:
  1)  Totem is open, sidebar is open in Playlist mode
  2)  Click "+" to add a file
  3)  Paste a location in the Location control (public location given above)
  4)  Click "Add" to add the location
  5)  Add interface closes, Totem shows the new file in the playlist
  6)  Click "+" to add another file
  7)  Totem presents dialog with "error accessing 
'http://www.gearwire.com/media': Access denied"
  8)  Close dialog
  9)  Paste another location in the Location control
  10)  Click "Add" to add the location
  11)  Nothing happens (no UI changes (except button blink), no message, etc.

  Expected Behaviour:
  1)  Totem is open, sidebar is open in Playlist mode
  2)  Click "+" to add a file
  3)  Paste a location in the Location control (public location given above)
  4)  Click "Add" to add the location
  5)  Add interface closes, Totem shows the new file in the playlist
  6)  Click "+" to add another file
  7)  Totem presents dialog with "error accessing 
'http://www.gearwire.com/media': Access denied"
  8)  Close dialog
  9)  Paste another location in the Location control
  10)  Click "Add" to add the location
  11)  Totem shows the new file in the playlist

  Alternate acceptable behaviour:
  1)  Totem is open, sidebar is open in Playlist mode
  2)  Click "+" to add a file
  3)  Paste a location in the Location control (public location given above)
  4)  Click "Add" to add the location
  5)  Add interface closes, Totem shows the new file in the playlist
  6)  Click "+" to add another file
  7)  Totem presents dialog with "error accessing 
'http://www.gearwire.com/media': Access denied"
  8)  Close dialog
  9)  Totem defauls to user home directory (or /media, or any known safe 
location)
  10)  Paste another location in the Location control
  11)  Click "Add" to add the location
  12)  Totem shows the new file in the playlist

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/108366/+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 1747744] Re: [regression] Video playback in totem is corrupted in X11

[dino99]

Packages landed now, and upgrade is ok (if purging previous shemgp ppa
first, in case of use)

mesa (18.0.0~rc4-1ubuntu1) bionic; urgency=medium

  * Merge with Debian experimental.
  * Stop using alternatives, not needed anymore with libglvnd.
  * patches: Mir patches updated.
  * dri3-reinstate-get_dri_screen-callback.diff: Fix a regression in
accelerated video playback. (LP: #1747744)
  * control: Add nvidia-304/340/384 to libegl-mesa0, libgles2-mesa and
libglx-mesa0 Breaks.

 -- Timo Aaltonen   Tue, 13 Feb 2018 17:56:35 +0200

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

Title:
  [regression] Video playback in totem is corrupted in X11

Status in Mesa:
  In Progress
Status in mesa package in Ubuntu:
  Fix Released
Status in totem package in Ubuntu:
  Confirmed

Bug description:
  Test case
  Log inti xorg session
  Install gstreamer1.0-vaapi plugin
  Play a supported video (- h.264/avc in .mp4, .mkv or .mov  would suffice

  Expected: hardware decoded playback
  What happens: totally corrupted screen, see screenshots

  Does work ok in a wayland session

  $ vainfo
  libva info: VA-API version 1.0.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_1_0
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 1.0 (libva 2.0.0)
  vainfo: Driver version: Intel i965 driver for Intel(R) Haswell Mobile - 2.0.0
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:   VAEntrypointVLD
VAProfileMPEG2Simple:   VAEntrypointEncSlice
VAProfileMPEG2Main  :   VAEntrypointVLD
VAProfileMPEG2Main  :   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
VAProfileH264Main   :   VAEntrypointVLD
VAProfileH264Main   :   VAEntrypointEncSlice
VAProfileH264High   :   VAEntrypointVLD
VAProfileH264High   :   VAEntrypointEncSlice
VAProfileH264MultiviewHigh  :   VAEntrypointVLD
VAProfileH264MultiviewHigh  :   VAEntrypointEncSlice
VAProfileH264StereoHigh :   VAEntrypointVLD
VAProfileH264StereoHigh :   VAEntrypointEncSlice
VAProfileVC1Simple  :   VAEntrypointVLD
VAProfileVC1Main:   VAEntrypointVLD
VAProfileVC1Advanced:   VAEntrypointVLD
VAProfileNone   :   VAEntrypointVideoProc
VAProfileJPEGBaseline   :   VAEntrypointVLD

  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gstreamer1.0-vaapi 1.12.4-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb  6 14:43:57 2018
  InstallationDate: Installed on 2018-02-06 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180204)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gstreamer-vaapi
  UpgradeStatus: No upgrade log present (probably fresh install)

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

[Sebastien Bacher]

the glib change seems buggy, the upstream bug corresponding to the first
patch https://bugzilla.gnome.org/show_bug.cgi?id=758641 states that the
issue was in code commited in 2.45 or trusty has 2.40 so it seems wrong
to try to use it on that codebase (unsure about the other ones)

** Bug watch added: GNOME Bug Tracker #758641
   https://bugzilla.gnome.org/show_bug.cgi?id=758641

-- 
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 1749480] [NEW] Totem black screen with Sparks

[corrado venturini]

Public bug reported:

Try play a video in Ubuntu 18.04 x11, i see a black screen with sparks. Same 
video is played correctly in wayland session.
corrado@corrado-p9-bb-1221:~$ inxi -SCGx
System:Host: corrado-p9-bb-1221 Kernel: 4.15.0-9-generic x86_64
   bits: 64 gcc: 7.3.0
   Desktop: Gnome 3.26.2 (Gtk 3.22.26-2ubuntu1)
   Distro: Ubuntu Bionic Beaver (development branch)
CPU:   Dual core Intel Core i3-7100 (-MT-MCP-) 
   arch: Skylake rev.9 cache: 3072 KB
   flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 15648
   clock speeds: max: 3900 MHz 1: 800 MHz 2: 800 MHz 3: 804 MHz
   4: 811 MHz
Graphics:  Card: Intel HD Graphics 630 bus-ID: 00:02.0
   Display Server: x11 (X.Org 1.19.6 ) driver: i915
   Resolution: 1920x1080@60.00hz
   OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2)
   version: 4.5 Mesa 17.3.3 Direct Render: Yes
corrado@corrado-p9-bb-1221:~$ apt policy totem
totem:
  Installed: 3.26.0-0ubuntu3
  Candidate: 3.26.0-0ubuntu3
  Version table:
 *** 3.26.0-0ubuntu3 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
corrado@corrado-p9-bb-1221:~$

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libgstreamer1.0-0 1.12.4-1
ProcVersionSignature: Ubuntu 4.15.0-9.10-generic 4.15.2
Uname: Linux 4.15.0-9-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 14 15:58:07 2018
InstallationDate: Installed on 2017-12-23 (53 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171221)
SourcePackage: gstreamer1.0
UpgradeStatus: No upgrade log present (probably fresh install)
XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

** Affects: gstreamer1.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: bionic totem x11

** Attachment added: "Screenshot from 2018-02-14 15-54-29.png"
   
https://bugs.launchpad.net/bugs/1749480/+attachment/5055178/+files/Screenshot%20from%202018-02-14%2015-54-29.png

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

Title:
  Totem black screen with Sparks

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  Try play a video in Ubuntu 18.04 x11, i see a black screen with sparks. Same 
video is played correctly in wayland session.
  corrado@corrado-p9-bb-1221:~$ inxi -SCGx
  System:Host: corrado-p9-bb-1221 Kernel: 4.15.0-9-generic x86_64
 bits: 64 gcc: 7.3.0
 Desktop: Gnome 3.26.2 (Gtk 3.22.26-2ubuntu1)
 Distro: Ubuntu Bionic Beaver (development branch)
  CPU:   Dual core Intel Core i3-7100 (-MT-MCP-) 
 arch: Skylake rev.9 cache: 3072 KB
 flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 15648
 clock speeds: max: 3900 MHz 1: 800 MHz 2: 800 MHz 3: 804 MHz
 4: 811 MHz
  Graphics:  Card: Intel HD Graphics 630 bus-ID: 00:02.0
 Display Server: x11 (X.Org 1.19.6 ) driver: i915
 Resolution: 1920x1080@60.00hz
 OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2)
 version: 4.5 Mesa 17.3.3 Direct Render: Yes
  corrado@corrado-p9-bb-1221:~$ apt policy totem
  totem:
Installed: 3.26.0-0ubuntu3
Candidate: 3.26.0-0ubuntu3
Version table:
   *** 3.26.0-0ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-p9-bb-1221:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libgstreamer1.0-0 1.12.4-1
  ProcVersionSignature: Ubuntu 4.15.0-9.10-generic 4.15.2
  Uname: Linux 4.15.0-9-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 14 15:58:07 2018
  InstallationDate: Installed on 2017-12-23 (53 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171221)
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1749480/+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 1747744] Re: [regression] Video playback in totem is corrupted in X11

[dino99]

And totem reads video without problem with mesa 18

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

Title:
  [regression] Video playback in totem is corrupted in X11

Status in Mesa:
  In Progress
Status in mesa package in Ubuntu:
  Fix Released
Status in totem package in Ubuntu:
  Confirmed

Bug description:
  Test case
  Log inti xorg session
  Install gstreamer1.0-vaapi plugin
  Play a supported video (- h.264/avc in .mp4, .mkv or .mov  would suffice

  Expected: hardware decoded playback
  What happens: totally corrupted screen, see screenshots

  Does work ok in a wayland session

  $ vainfo
  libva info: VA-API version 1.0.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_1_0
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 1.0 (libva 2.0.0)
  vainfo: Driver version: Intel i965 driver for Intel(R) Haswell Mobile - 2.0.0
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:   VAEntrypointVLD
VAProfileMPEG2Simple:   VAEntrypointEncSlice
VAProfileMPEG2Main  :   VAEntrypointVLD
VAProfileMPEG2Main  :   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
VAProfileH264Main   :   VAEntrypointVLD
VAProfileH264Main   :   VAEntrypointEncSlice
VAProfileH264High   :   VAEntrypointVLD
VAProfileH264High   :   VAEntrypointEncSlice
VAProfileH264MultiviewHigh  :   VAEntrypointVLD
VAProfileH264MultiviewHigh  :   VAEntrypointEncSlice
VAProfileH264StereoHigh :   VAEntrypointVLD
VAProfileH264StereoHigh :   VAEntrypointEncSlice
VAProfileVC1Simple  :   VAEntrypointVLD
VAProfileVC1Main:   VAEntrypointVLD
VAProfileVC1Advanced:   VAEntrypointVLD
VAProfileNone   :   VAEntrypointVideoProc
VAProfileJPEGBaseline   :   VAEntrypointVLD

  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gstreamer1.0-vaapi 1.12.4-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb  6 14:43:57 2018
  InstallationDate: Installed on 2018-02-06 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180204)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gstreamer-vaapi
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1747744/+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 108366] Re: Totem unable to add to playlist after selecting unreadable location

[Bug Watch Updater]

** Changed in: gtk
   Status: Unknown => Confirmed

** Changed in: gtk
   Importance: Unknown => Medium

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

Title:
  Totem unable to add to playlist after selecting unreadable location

Status in GTK+:
  Confirmed
Status in Totem:
  Invalid
Status in gtk+2.0 package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: totem

  When adding to the playlist using the sidebar interface, totem
  defaults to the directory of the last selected file when prompting for
  a new file.  When that directory is unreadable (e.g.
  http://www.gearwire.com/media/ (after adding
  http://www.gearwire.com/media/seymour-duncan-guitar-
  pickups-1-musikmesse.wmv by pasting into the location control in the
  last add)), totem presents the message "error accessing
  'http://www.gearwire.com/media': Access denied".  If this dialog is
  closed, totem is unable to add new files to the playlist (even when
  pasting the Location) until a readable base location (e.g. the home
  directory) is selected.

  In functional terms:

  Observed Behaviour:
  1)  Totem is open, sidebar is open in Playlist mode
  2)  Click "+" to add a file
  3)  Paste a location in the Location control (public location given above)
  4)  Click "Add" to add the location
  5)  Add interface closes, Totem shows the new file in the playlist
  6)  Click "+" to add another file
  7)  Totem presents dialog with "error accessing 
'http://www.gearwire.com/media': Access denied"
  8)  Close dialog
  9)  Paste another location in the Location control
  10)  Click "Add" to add the location
  11)  Nothing happens (no UI changes (except button blink), no message, etc.

  Expected Behaviour:
  1)  Totem is open, sidebar is open in Playlist mode
  2)  Click "+" to add a file
  3)  Paste a location in the Location control (public location given above)
  4)  Click "Add" to add the location
  5)  Add interface closes, Totem shows the new file in the playlist
  6)  Click "+" to add another file
  7)  Totem presents dialog with "error accessing 
'http://www.gearwire.com/media': Access denied"
  8)  Close dialog
  9)  Paste another location in the Location control
  10)  Click "Add" to add the location
  11)  Totem shows the new file in the playlist

  Alternate acceptable behaviour:
  1)  Totem is open, sidebar is open in Playlist mode
  2)  Click "+" to add a file
  3)  Paste a location in the Location control (public location given above)
  4)  Click "Add" to add the location
  5)  Add interface closes, Totem shows the new file in the playlist
  6)  Click "+" to add another file
  7)  Totem presents dialog with "error accessing 
'http://www.gearwire.com/media': Access denied"
  8)  Close dialog
  9)  Totem defauls to user home directory (or /media, or any known safe 
location)
  10)  Paste another location in the Location control
  11)  Click "Add" to add the location
  12)  Totem shows the new file in the playlist

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/108366/+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 1747744] Re: [regression] Video playback in totem is corrupted in X11

[dino99]

Clearly cant blame totem.

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

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

Title:
  [regression] Video playback in totem is corrupted in X11

Status in Mesa:
  In Progress
Status in mesa package in Ubuntu:
  Fix Released
Status in totem package in Ubuntu:
  Invalid

Bug description:
  Test case
  Log inti xorg session
  Install gstreamer1.0-vaapi plugin
  Play a supported video (- h.264/avc in .mp4, .mkv or .mov  would suffice

  Expected: hardware decoded playback
  What happens: totally corrupted screen, see screenshots

  Does work ok in a wayland session

  $ vainfo
  libva info: VA-API version 1.0.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_1_0
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 1.0 (libva 2.0.0)
  vainfo: Driver version: Intel i965 driver for Intel(R) Haswell Mobile - 2.0.0
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:   VAEntrypointVLD
VAProfileMPEG2Simple:   VAEntrypointEncSlice
VAProfileMPEG2Main  :   VAEntrypointVLD
VAProfileMPEG2Main  :   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
VAProfileH264Main   :   VAEntrypointVLD
VAProfileH264Main   :   VAEntrypointEncSlice
VAProfileH264High   :   VAEntrypointVLD
VAProfileH264High   :   VAEntrypointEncSlice
VAProfileH264MultiviewHigh  :   VAEntrypointVLD
VAProfileH264MultiviewHigh  :   VAEntrypointEncSlice
VAProfileH264StereoHigh :   VAEntrypointVLD
VAProfileH264StereoHigh :   VAEntrypointEncSlice
VAProfileVC1Simple  :   VAEntrypointVLD
VAProfileVC1Main:   VAEntrypointVLD
VAProfileVC1Advanced:   VAEntrypointVLD
VAProfileNone   :   VAEntrypointVideoProc
VAProfileJPEGBaseline   :   VAEntrypointVLD

  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gstreamer1.0-vaapi 1.12.4-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb  6 14:43:57 2018
  InstallationDate: Installed on 2018-02-06 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180204)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gstreamer-vaapi
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1747744/+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 1749480] Re: Totem black screen with Sparks

[dino99]

i suppose you hit that lp:1747744 dont you; which is solved by upgrading
to mesa 18 (proposed)

** Changed in: gstreamer1.0 (Ubuntu)
   Status: New => Incomplete

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

Title:
  Totem black screen with Sparks

Status in gstreamer1.0 package in Ubuntu:
  Incomplete

Bug description:
  Try play a video in Ubuntu 18.04 x11, i see a black screen with sparks. Same 
video is played correctly in wayland session.
  corrado@corrado-p9-bb-1221:~$ inxi -SCGx
  System:Host: corrado-p9-bb-1221 Kernel: 4.15.0-9-generic x86_64
 bits: 64 gcc: 7.3.0
 Desktop: Gnome 3.26.2 (Gtk 3.22.26-2ubuntu1)
 Distro: Ubuntu Bionic Beaver (development branch)
  CPU:   Dual core Intel Core i3-7100 (-MT-MCP-) 
 arch: Skylake rev.9 cache: 3072 KB
 flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 15648
 clock speeds: max: 3900 MHz 1: 800 MHz 2: 800 MHz 3: 804 MHz
 4: 811 MHz
  Graphics:  Card: Intel HD Graphics 630 bus-ID: 00:02.0
 Display Server: x11 (X.Org 1.19.6 ) driver: i915
 Resolution: 1920x1080@60.00hz
 OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2)
 version: 4.5 Mesa 17.3.3 Direct Render: Yes
  corrado@corrado-p9-bb-1221:~$ apt policy totem
  totem:
Installed: 3.26.0-0ubuntu3
Candidate: 3.26.0-0ubuntu3
Version table:
   *** 3.26.0-0ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-p9-bb-1221:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libgstreamer1.0-0 1.12.4-1
  ProcVersionSignature: Ubuntu 4.15.0-9.10-generic 4.15.2
  Uname: Linux 4.15.0-9-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 14 15:58:07 2018
  InstallationDate: Installed on 2017-12-23 (53 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171221)
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1749480/+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 1749101] Re: package openssh-server 1:7.2p2-4ubuntu2.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Joshua Powers]

Thanks for filing a bug.

>From your terminal log:
Feb 13 08:32:25 jb2-System-Product-Name sshd[3943]: /etc/ssh/sshd_config: lin...
Feb 13 08:32:25 jb2-System-Product-Name sshd[3943]: /etc/ssh/sshd_config: ter...

I'm willing to bet there is something wrong with your
/etc/ssh/sshd_config.

Try running `sudo /usr/sbin/sshd -t`

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

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

Title:
  package openssh-server 1:7.2p2-4ubuntu2.4 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  package openssh-server 1:7.2p2-4ubuntu2.4 failed

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: openssh-server 1:7.2p2-4ubuntu2.4
  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
  Date: Tue Feb 13 08:32:25 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-09-27 (503 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SSHDConfig:
   Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: 
/etc/ssh/sshd_config: line 89: Bad configuration option: OD
   /etc/ssh/sshd_config: terminating, 1 bad configuration options
  SourcePackage: openssh
  Title: package openssh-server 1:7.2p2-4ubuntu2.4 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1749101/+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 1749540] [NEW] qemu tests should run on more architectures

[Dimitri John Ledkov]

Public bug reported:

qemu tests should be able to run on more architectures.

adt tests are missing dependencies, to e.g. excercise qemu-only tests on
non-amd64 arches.

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

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

Title:
  qemu tests should run on more architectures

Status in systemd package in Ubuntu:
  New

Bug description:
  qemu tests should be able to run on more architectures.

  adt tests are missing dependencies, to e.g. excercise qemu-only tests
  on non-amd64 arches.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1749540/+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 1749086] Re: (X)Ubuntu 16.04.3 LTS: sleep on boot

[Christopher M. Penalver]

** Tags added: bios-outdated-1.90

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

Title:
  (X)Ubuntu 16.04.3 LTS: sleep on boot

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Newly installed xubuntu, kubuntu (other flavours I haven't tried, but
  probably the same), the screen turns off a few seconds after choosing
  ubuntu in grub2 menu, after about 5 minutes it comes back to life and
  login screen is presented and from that point on everything seems to
  work as normal. (Might have sth to do with Radeon drivers?) Please
  tell me what other info you need.

  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
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Feb 13 07:37:53 2018
  InstallationDate: Installed on 2018-02-11 (1 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  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
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Juniper XT [Radeon HD 5770] [1043:03b6]
  InstallationDate: Installed on 2018-02-11 (2 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=7529842e-d871-4641-89dc-3a4980dda2de ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Tags:  xenial ubuntu
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/18/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: 770 Extreme3
  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.80:bd10/18/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn770Extreme3: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.
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1749086/+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 1749150] Re: Spontaneous single window freezing

[Christopher M. Penalver]

** Tags added: bios-outdated-2.50

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

Title:
  Spontaneous single window freezing

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Sometimes a window stopped refreshing its contents. Different applications 
affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen.
  No way found to revive in-time refreshing except full window closing (or 
blind login, in case of KDE lock screen). Keyboard or mouse activity in a such 
window doesn't help.
  A one-shot refresh can be easily caused by switching to another virtual 
desktop and then back. After such switching, a window refresh is active for 
approximately 0.5 seconds, then stops again.
  No relation to host uptime or X session uptime is visible.

  Observed on two different hosts, both carrying Kubuntu 16.04 and
  running XWindow+KDE as desktop environment. KDE is standard Kubuntu
  one. Multiple virtual desktops are used on both hosts.

  The issue started to appear approximately 4-5 months ago but I can't
  specify exact package change that could have caused it. Both hosts are
  regularly updated (no more than 1 week delay).

  The first host has:
  video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller])
  Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670]
  Kernel driver in use: radeon
  Kernel modules: radeon
  CPU: AMD FX-8150
  RAM: 16GB
  Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade.
  current kernel: linux-image-4.4.0-112-generic
  video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active 
driver: radeon

  Issue rate on this host is rather tiny (~1 per week).

  The second one has:
  video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev 
a1) (prog-if 00 [VGA controller])
  Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93
  Kernel driver in use: nvidia
  Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384
  (really this is GeForce GT 740)
  CPU:Intel i3-4170
  RAM: 16GB
  Installed originally as Kubuntu 16.04
  current kernel: linux-image-4.13.0-32-generic (depended on by 
linux-generic-hwe-16.04)
  video packages: HWE series (e.g. 
xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia 
(proprietary), but the same issue observed with VESA driver.

  Issue rate on this host is 1-2 per day and was much higher with VESA
  driver in use.

  No respective messages are found in Xorg.*.log or ~/.xsession-errors,
  but the latter has got stream of messages like:

  at host with AMD and Radeon:
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )

  at host with Intel and Nvidia:
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )

  such messages started appearing approximately at the same time, plus-
  minus 1-2 months.

  Additional info can be provided on demand.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  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
  CurrentDesktop: KDE
  Date: Tue Feb 13 11:47:32 2018
  InstallationDate: Installed on 2014-12-16 (1154 days ago)
  InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago)
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 

[Touch-packages] [Bug 1746638] Re: [GeForce 6150SE nForce 430] PC freezes and crashes

[Diogo Gomes]

Christopher M. Penalver,

I have not had availability to test version 18.04 on a new disc but I
have more information:

- After updating the packages xorg-serverhwe... I decided to test
the Open Source drivers again and got improvements.

- Due to these improvements and to the system crashing less, I detected
a pattern in the crashes. It may not be related but crashes usually
happen when I adjust the size of a window manually.

I'll let you know as soon as I have more 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/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 1749150] Re: Spontaneous single window freezing

[Christopher M. Penalver]

Valentin Nechayev, please don't apport-collect from different machines. If you 
have an issue with different hardware, it is most helpful to file a new report 
instead via a terminal:
ubuntu-bug xorg

Despite this, this appears correlated to a KDE'ism. Is the issue
reproducible if you use GNOME? One may test a live environment via
http://cdimage.ubuntu.com/daily-live/current/ to confirm.

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

Title:
  Spontaneous single window freezing

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Sometimes a window stopped refreshing its contents. Different applications 
affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen.
  No way found to revive in-time refreshing except full window closing (or 
blind login, in case of KDE lock screen). Keyboard or mouse activity in a such 
window doesn't help.
  A one-shot refresh can be easily caused by switching to another virtual 
desktop and then back. After such switching, a window refresh is active for 
approximately 0.5 seconds, then stops again.
  No relation to host uptime or X session uptime is visible.

  Observed on two different hosts, both carrying Kubuntu 16.04 and
  running XWindow+KDE as desktop environment. KDE is standard Kubuntu
  one. Multiple virtual desktops are used on both hosts.

  The issue started to appear approximately 4-5 months ago but I can't
  specify exact package change that could have caused it. Both hosts are
  regularly updated (no more than 1 week delay).

  The first host has:
  video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller])
  Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670]
  Kernel driver in use: radeon
  Kernel modules: radeon
  CPU: AMD FX-8150
  RAM: 16GB
  Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade.
  current kernel: linux-image-4.4.0-112-generic
  video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active 
driver: radeon

  Issue rate on this host is rather tiny (~1 per week).

  The second one has:
  video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev 
a1) (prog-if 00 [VGA controller])
  Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93
  Kernel driver in use: nvidia
  Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384
  (really this is GeForce GT 740)
  CPU:Intel i3-4170
  RAM: 16GB
  Installed originally as Kubuntu 16.04
  current kernel: linux-image-4.13.0-32-generic (depended on by 
linux-generic-hwe-16.04)
  video packages: HWE series (e.g. 
xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia 
(proprietary), but the same issue observed with VESA driver.

  Issue rate on this host is 1-2 per day and was much higher with VESA
  driver in use.

  No respective messages are found in Xorg.*.log or ~/.xsession-errors,
  but the latter has got stream of messages like:

  at host with AMD and Radeon:
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )

  at host with Intel and Nvidia:
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )

  such messages started appearing approximately at the same time, plus-
  minus 1-2 months.

  Additional info can be provided on demand.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  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
  CurrentDesktop: KDE
  Date: Tue Feb 13 11:47:32 2018
  InstallationDate: Installed on 2014-12-16 (1154 days ago)
  InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago)
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA

[Touch-packages] [Bug 1749389] Re: ntpdate lock apparmor deny

[ChristianEhrhardt]

Verification of proposed:
xenial/artful as is on restart:
[2020349.483870] audit: type=1400 audit(1518622585.386:4875): apparmor="DENIED" 
operation="file_inherit" 
namespace="root//lxd-xenial-test_" 
profile="/usr/sbin/ntpd" name="/run/lock/ntpdate" pid=16784 comm="ntpd" 
requested_mask="w" denied_mask="w" fsuid=0 ouid=0
[2020342.768379] audit: type=1400 audit(1518622578.674:4870): apparmor="DENIED" 
operation="file_inherit" 
namespace="root//lxd-artful-test_" 
profile="/usr/sbin/ntpd" name="/run/lock/ntpdate" pid=16638 comm="ntpd" 
requested_mask="w" denied_mask="w" fsuid=0 ouid=0

After upgrade from proposed:
- 1:4.2.8p4+dfsg-3ubuntu5.8
- 1:4.2.8p10+dfsg-5ubuntu3.2

The messages above are gone - so verified

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

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

Title:
  ntpdate lock apparmor deny

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

Bug description:
  [Impact]

   * Apparmor denies access to lock it shares with ntpdate to ensure no
     issues due to concurrent access

  [Test Case]

   1. get a container of target release
   2. install ntp
  apt install ntp
   3. watch dmesg on container-host
  dmesg -w
   4. restart ntp in container
  systemctl restart ntp
   => see (or no more after fix) apparmor denie:
  apparmor="DENIED" operation="file_inherit" profile="/usr/sbin/ntpd" 
name="/run/lock/ntpdate" pid=30113 comm="ntpd" requested_mask="w" 
denied_mask="w"
  Note: to not be mislead, on xenial there is a remaining stdout appamor 
  issue which is bug 1670408

  [Regression Potential]

   * we are only slightly opening up the apparmor profile, but none of the
     changes poses a security risk so regression potential on it's own
     should be close to zero.

   * There is a potential issue if the locking (that now can succeed) would
     e.g. no more be freed up or the action behind the locking would cause
     issues.

  [Other Info]

   * n/a

  On start/restart nto has an error in apparmor due to the locking it
  tries to avoid issues running concurrently with ntpdate.

  That looks like:
  apparmor="DENIED" operation="file_inherit" profile="/usr/sbin/ntpd" 
name="/run/lock/ntpdate" pid=30113 comm="ntpd" requested_mask="w" 
denied_mask="w"

  The rule we need is:
  /run/lock/ntpdate wk,

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1749389/+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 1741227] Re: apparmor denial to several paths to binaries

[ChristianEhrhardt]

Verification of Proposed:
[2020342.769272] audit: type=1400 audit(1518622578.674:4871): apparmor="DENIED" 
operation="open" namespace="root//lxd-artful-test_" 
profile="/usr/sbin/ntpd" name="/usr/local/sbin/" pid=16638 comm="ntpd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[2020342.769282] audit: type=1400 audit(1518622578.674:4872): apparmor="DENIED" 
operation="open" namespace="root//lxd-artful-test_" 
profile="/usr/sbin/ntpd" name="/usr/local/bin/" pid=16638 comm="ntpd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0


After upgrade from proposed:
- 1:4.2.8p10+dfsg-5ubuntu3.2

The messages above are gone - so verified

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

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

Title:
  apparmor denial to several paths to binaries

Status in ntp package in Ubuntu:
  Fix Released
Status in ntp source package in Artful:
  Fix Committed

Bug description:
  [Impact]

   * Apparmor denies access to bin directories which the option parsing code 
 of ntp touches.

  [Test Case]

   1. get a container of target release
   2. install ntp
  apt install ntp
   3. watch dmesg on container-host
  dmesg -w
   4. restart ntp in container
  systemctl restart ntp
   => see (or no more after fix) apparmor denie:
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/sbin/" pid=23933 comm="ntpd" requested_mask="r" denied_mask="r"
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/bin/" pid=23933 comm="ntpd" requested_mask="r" denied_mask="r"

  [Regression Potential]

   * we are only slightly opening up the apparmor profile, but none of the
 changes poses a security risk so regression potential on it's own
 should be close to zero.

   * we discussed if this would be a security risk but came to the 
 conclusion that r-only should be ok (the same content anyone can grab 
 from the archive by installing the packages)

  [Other Info]

   * n/a

  Issue shows up (non fatal) as:
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/sbin/" pid=23933 comm="ntpd" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/bin/" pid=23933 comm="ntpd" requested_mask="r" denied_mask="r" 
fsuid=0 ouid=0

  Since non crit this is mostyl about many of us being curious why it
  actually does do it :-)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1741227/+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 1747744] Re: [regression] Video playback in totem is corrupted in X11

[Timo Aaltonen]

don't jump the gun, mesa hasn't landed in bionic yet and won't land
before nvidia is fixed to work with libglvnd..

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

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

Title:
  [regression] Video playback in totem is corrupted in X11

Status in Mesa:
  In Progress
Status in mesa package in Ubuntu:
  Fix Committed
Status in totem package in Ubuntu:
  Invalid

Bug description:
  Test case
  Log inti xorg session
  Install gstreamer1.0-vaapi plugin
  Play a supported video (- h.264/avc in .mp4, .mkv or .mov  would suffice

  Expected: hardware decoded playback
  What happens: totally corrupted screen, see screenshots

  Does work ok in a wayland session

  $ vainfo
  libva info: VA-API version 1.0.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_1_0
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 1.0 (libva 2.0.0)
  vainfo: Driver version: Intel i965 driver for Intel(R) Haswell Mobile - 2.0.0
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:   VAEntrypointVLD
VAProfileMPEG2Simple:   VAEntrypointEncSlice
VAProfileMPEG2Main  :   VAEntrypointVLD
VAProfileMPEG2Main  :   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
VAProfileH264Main   :   VAEntrypointVLD
VAProfileH264Main   :   VAEntrypointEncSlice
VAProfileH264High   :   VAEntrypointVLD
VAProfileH264High   :   VAEntrypointEncSlice
VAProfileH264MultiviewHigh  :   VAEntrypointVLD
VAProfileH264MultiviewHigh  :   VAEntrypointEncSlice
VAProfileH264StereoHigh :   VAEntrypointVLD
VAProfileH264StereoHigh :   VAEntrypointEncSlice
VAProfileVC1Simple  :   VAEntrypointVLD
VAProfileVC1Main:   VAEntrypointVLD
VAProfileVC1Advanced:   VAEntrypointVLD
VAProfileNone   :   VAEntrypointVideoProc
VAProfileJPEGBaseline   :   VAEntrypointVLD

  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gstreamer1.0-vaapi 1.12.4-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb  6 14:43:57 2018
  InstallationDate: Installed on 2018-02-06 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180204)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gstreamer-vaapi
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Got it, I missed the difference between 1941 and 1946. Thanks for the
clarification.

-- 
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:
  Triaged
Status in apport source package in Bionic:
  Triaged

Bug description:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files). This issue was first mentioned in bug 1746653. But
  then I noticed my machine doing it too...

  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 1749472] Re: mesa 18.0.0 will cause rendering errors in Qt applications

[Timo Aaltonen]

sigh, is this filed upstream?

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

Title:
  mesa 18.0.0 will cause rendering errors in Qt applications

Status in mesa package in Ubuntu:
  New
Status in qtbase-opensource-src package in Ubuntu:
  New
Status in mesa source package in Bionic:
  New
Status in qtbase-opensource-src source package in Bionic:
  New

Bug description:
  From: https://bugreports.qt.io/browse/QTBUG-66348

  ** extract **

  The `QOpenGLShaderProgram` class in Qt can be used to compile and link
  OpenGL shaders. If the `GL_ARB_get_program_binary` OpenGL extension is
  available, it can cache those shaders on disk
  (~/.cache/qtshadercache). The i965 driver in Mesa supports this
  extension since version 18.0.0.

  When the shader is loaded using the `glProgramBinary` function, OpenGL
  can refuse it if for example some hardware or software component
  changed. Mesa refuses binaries that were created by any other build of
  Mesa (using among other things the build_id of the library).

  If the shader is refused, Qt should fallback to compiling it from
  sources, but it incorrectly calls glLinkProgram first. The
  glLinkProgram succeeds, because it actually links 0 shaders together.
  That is allowed in OpenGL compatibility profile and the resulting
  program works as a fixed pipeline. Which of course does not render as
  expected.

  This causes rendering errors in Qt applications every time Mesa is
  updated since version 18.0.0. For example white screen in sddm.

  This issue was originally reported in openSUSE
  (https://bugzilla.opensuse.org/show_bug.cgi?id=1080578).

  ** end extract **

  As this potentially effects Qt applications, and could even render
  display manager login unusable, this should be a blocking bug in mesa
  and Qt until Qt mitigations patches pass codereview and can be
  included in Qtbase for 18.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1749472/+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 1749279] Re: Still using problematic adobe-flashplayer

[Brian Murray]

I don't see how this is an apport issue, that's likely just a message
from your browser.

** Package changed: apport (Ubuntu) => ubuntu

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

Title:
  Still using problematic adobe-flashplayer

Status in Ubuntu:
  New

Bug description:
  Output when running apport-collect:

   apport-collect ***
  The authorization page:
   
(https://launchpad.net/+authorize-token?oauth_token=LqxC5SPg3jmN2S9BJVKl&allow_permission=DESKTOP_INTEGRATION)
  should be opening in your browser. Use your browser to authorize
  this program to access Launchpad on your behalf.
  Waiting to hear from Launchpad about your decision...
  Using PPAPI flash.
   --ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so 
--ppapi-flash-version=

  

  What is the need to still use that closed/deprecated player, when this
  is now very rarely installed on systems due to the endless problems
  met. Nowadays browser use html5 instead (if only required by apport-
  collect !!!)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.8-0ubuntu10
  ProcVersionSignature: Ubuntu 4.15.0-9.10-generic 4.15.2
  Uname: Linux 4.15.0-9-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Feb 13 20:28:49 2018
  EcryptfsInUse: Yes
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1749279/+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 1749472] Re: mesa 18.0.0 will cause rendering errors in Qt applications

[Timo Aaltonen]

oh it's a qt bug not mesa, got it

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

Title:
  mesa 18.0.0 will cause rendering errors in Qt applications

Status in mesa package in Ubuntu:
  New
Status in qtbase-opensource-src package in Ubuntu:
  New
Status in mesa source package in Bionic:
  New
Status in qtbase-opensource-src source package in Bionic:
  New

Bug description:
  From: https://bugreports.qt.io/browse/QTBUG-66348

  ** extract **

  The `QOpenGLShaderProgram` class in Qt can be used to compile and link
  OpenGL shaders. If the `GL_ARB_get_program_binary` OpenGL extension is
  available, it can cache those shaders on disk
  (~/.cache/qtshadercache). The i965 driver in Mesa supports this
  extension since version 18.0.0.

  When the shader is loaded using the `glProgramBinary` function, OpenGL
  can refuse it if for example some hardware or software component
  changed. Mesa refuses binaries that were created by any other build of
  Mesa (using among other things the build_id of the library).

  If the shader is refused, Qt should fallback to compiling it from
  sources, but it incorrectly calls glLinkProgram first. The
  glLinkProgram succeeds, because it actually links 0 shaders together.
  That is allowed in OpenGL compatibility profile and the resulting
  program works as a fixed pipeline. Which of course does not render as
  expected.

  This causes rendering errors in Qt applications every time Mesa is
  updated since version 18.0.0. For example white screen in sddm.

  This issue was originally reported in openSUSE
  (https://bugzilla.opensuse.org/show_bug.cgi?id=1080578).

  ** end extract **

  As this potentially effects Qt applications, and could even render
  display manager login unusable, this should be a blocking bug in mesa
  and Qt until Qt mitigations patches pass codereview and can be
  included in Qtbase for 18.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1749472/+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 1619258] Re: netplan should allow NICs to be disconnected and not stall the boot

[Mathieu Trudel-Lapierre]

In progress; we got optional: true for that and systemd has a
corresponding "RequiredForOnline=false".

** Changed in: nplan (Ubuntu)
   Status: Confirmed => In Progress

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

** Changed in: nplan (Ubuntu)
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)

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

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

Title:
  netplan should allow NICs to be disconnected and not stall the boot

Status in Snappy:
  Confirmed
Status in nplan package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  in older snappy image we used to set "allow-hotplug" in
  /etc/network/interfaces.d/ when configuring a NIC to avoid the boot to
  completely stall or to be stuck for 5min when trying to find an
  internet connection.

  with recent versions of netplan the configuration seems to be back to
  require a network to be up before moving on with them boot so that
  booting takes forever until the network connection times out.

  netplan should make the system check the physical link status when
  trying to bring up a network device instead of stalling the boot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1619258/+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 1377653] Re: HDMI sound output not detected / NVIDIA optimus laptop

[Pete]

I can confirm that #19 works, as well. Also applied the suggestions in #24.
Ubuntu 17.10 on a Lenovo Ideapad Y910-17ISK with a GTX 1070.
I don't notice any flicker or any problem. The audio device has just appeared, 
and everything works fine now :-) 
Thanks a lot!!

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

Title:
  HDMI sound output not detected / NVIDIA optimus laptop

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  not sure if this is an alsa or nvidia/nouveau bug.
  HDMI audio output doesn't appear in sound settings output panel.
  Audio works well on internal speakers, but it seems there is no way to make 
it output to hdmi...

  The laptop has optimus NVIDIA+Intel.
  The behaviour is the same with nouveau or nvidia proprietary driver.

  Please let me know if further testing is required

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Uname: Linux 3.13.0-36-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sam2295 F pulseaudio
  CurrentDesktop: Unity
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Sun Oct  5 17:05:35 2014
  InstallationDate: Installed on 2014-04-21 (166 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/02/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N56VZ.215
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N56VZ
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN56VZ.215:bd11/02/2012:svnASUSTeKCOMPUTERINC.:pnN56VZ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN56VZ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N56VZ
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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