[Touch-packages] [Bug 1883644] Re: When I was installing video drivers for Intel this problem occurred

2020-06-15 Thread Daniel van Vugt
1. This machine does not have an Intel GPU so does not use "Intel"
graphics drivers. It's a virtual machine with a "vmwgfx" GPU. You do not
need to install any drivers at all.

2. Please tell us what the problem is.


** Package changed: xorg (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  When I was installing video drivers for Intel this problem occurred

Status in Ubuntu:
  Incomplete

Bug description:
  cheese drivers for Intel VGA 640

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Tue Jun 16 09:34:11 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2020-06-15 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: innotek GmbH VirtualBox
  ProcEnviron:
   LANGUAGE=en_IN:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=554760c3-2201-4ceb-86f3-9401a67f6a59 ro quiet splash acpi_osi
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1883644/+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 1882415] Re: Graphical artifact in top-right corner, owned by ibus-ui-gtk3

2020-06-15 Thread vasdi
$ env | grep -E 'XMOD|_IM'

XMODIFIERS=@im=ibus
QT_IM_MODULE=ibus

and the gray line is gone.

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

Title:
  Graphical artifact in top-right corner, owned by ibus-ui-gtk3

Status in gnome-shell package in Ubuntu:
  New
Status in ibus package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04, Gnome 3.36.2, Nvidia

  Small gray line in top-right corner.
  More precisely, it happens to be in the corner in 1920x1080 resolution. Not 
present in smaller resolutions. In panning mode it's fixed to panel, not screen.
  Present on the panel and on fullscreen windows but not in overview.
  Not clickable (prevents me from clicking button underneath it).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2014-11-12 (2037 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-37.41-lowlatency 5.4.41
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  Tags:  focal
  Uname: Linux 5.4.0-37-lowlatency x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-01 (40 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882415/+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 1883116] Re: SRU the current 3.36.3 stable update

2020-06-15 Thread Launchpad Bug Tracker
This bug was fixed in the package evolution-data-server - 3.36.3-1

---
evolution-data-server (3.36.3-1) unstable; urgency=medium

  * New stable version (lp: #1883116)

 -- Sebastien Bacher   Thu, 11 Jun 2020 23:09:07
+0200

** Changed in: evolution-data-server (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 evolution-data-server in
Ubuntu.
https://bugs.launchpad.net/bugs/1883116

Title:
  SRU the current 3.36.3 stable update

Status in evolution-data-server package in Ubuntu:
  Fix Released

Bug description:
  * Impact
  That's the current GNOME stable update, including some fixes and translation 
updates
  https://gitlab.gnome.org/GNOME/evolution-data-server/-/blob/gnome-3-36/NEWS

  * Test case

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Check that the calendar integration in GNOME and gnome-calendar is
  working, also test evolution with an email account.

  * Regression potential

  There is no specific change or feature to test in the upgrade

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1883116/+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 1267866] Re: usb audio: cannot get ctl value: req = 0x81, wValue = 0x0, wIndex = 0x1400, type = 3

2020-06-15 Thread Launchpad Bug Tracker
[Expired for alsa-driver (Ubuntu) because there has been no activity for
60 days.]

** Changed in: alsa-driver (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  usb audio: cannot get ctl value: req = 0x81, wValue = 0x0, wIndex =
  0x1400, type = 3

Status in alsa-driver package in Ubuntu:
  Expired

Bug description:
  I typed in terminal:

  alsamixer

  Then I wanted to change the sound card (I have connected an external
  sound card via USB).

  I pressed F6, selected the external sound card and pressed enter.

  alsamixer crashed and outputed:

  cannot load mixer controls: Broken pipe

  My ALSA information is located at http://www.alsa-
  project.org/db/?f=1871c086b58a2965d18cfb38483794788187edfb

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1267866/+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 1883483] Re: Xorg freeze and hang

2020-06-15 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1879234 ***
https://bugs.launchpad.net/bugs/1879234

Regarding comment #4, please open a new bug for that by running:

  ubuntu-bug chromium-browser

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

Title:
  Xorg freeze and hang

Status in xorg package in Ubuntu:
  New

Bug description:
  when i use my pc i check my activities but wheen i click on activities
  that time my pc going to freez.i can not to back to home page .i was
  really depressed.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-59.53~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-59-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 15 11:21:04 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000]
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-59-generic 
root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F23
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: A320M-S2H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  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/1883483/+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 1883483] Re: Xorg freeze and hang

2020-06-15 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1879234 ***
https://bugs.launchpad.net/bugs/1879234

Please also report the video from comment #3 in a new bug by running:

  ubuntu-bug chromium-browser

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

Title:
  Xorg freeze and hang

Status in xorg package in Ubuntu:
  New

Bug description:
  when i use my pc i check my activities but wheen i click on activities
  that time my pc going to freez.i can not to back to home page .i was
  really depressed.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-59.53~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-59-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 15 11:21:04 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000]
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-59-generic 
root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F23
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: A320M-S2H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  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/1883483/+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 1883483] Re: Xorg freeze and hang

2020-06-15 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1879234 ***
https://bugs.launchpad.net/bugs/1879234

The issue in comment #2 is bug 1879234 so please use that bug.

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

Title:
  Xorg freeze and hang

Status in xorg package in Ubuntu:
  New

Bug description:
  when i use my pc i check my activities but wheen i click on activities
  that time my pc going to freez.i can not to back to home page .i was
  really depressed.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-59.53~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-59-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 15 11:21:04 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000]
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-59-generic 
root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F23
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: A320M-S2H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  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/1883483/+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 1883483] Re: Xorg freeze and hang

2020-06-15 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1879234 ***
https://bugs.launchpad.net/bugs/1879234

** This bug has been marked a duplicate of bug 1879234
   [amdgpu] Xorg freeze

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

Title:
  Xorg freeze and hang

Status in xorg package in Ubuntu:
  New

Bug description:
  when i use my pc i check my activities but wheen i click on activities
  that time my pc going to freez.i can not to back to home page .i was
  really depressed.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-59.53~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-59-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 15 11:21:04 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000]
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-59-generic 
root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F23
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: A320M-S2H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  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/1883483/+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 1883644] [NEW] When I was installing video drivers for Intel this problem occurred

2020-06-15 Thread Pradeep
Public bug reported:

cheese drivers for Intel VGA 640

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
Uname: Linux 5.4.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
CasperMD5CheckResult: skip
CompositorRunning: None
Date: Tue Jun 16 09:34:11 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
GraphicsCard:
 VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
   Subsystem: VMware SVGA II Adapter [15ad:0405]
InstallationDate: Installed on 2020-06-15 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Lsusb:
 Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
 Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Lsusb-t:
 /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M
 |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
MachineType: innotek GmbH VirtualBox
ProcEnviron:
 LANGUAGE=en_IN:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=554760c3-2201-4ceb-86f3-9401a67f6a59 ro quiet splash acpi_osi
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu

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

Title:
  When I was installing video drivers for Intel this problem occurred

Status in xorg package in Ubuntu:
  New

Bug description:
  cheese drivers for Intel VGA 640

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Tue Jun 16 09:34:11 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  InstallationDate: Installed on 2020-06-15 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: innotek GmbH VirtualBox
  ProcEnviron:
   LANGUAGE=en_IN:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=554760c3-2201-4ceb-86f3-9401a67f6a59 ro quiet splash acpi_osi
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  

[Touch-packages] [Bug 1882484] Re: Firewall rule in before.rules for dhcp is wrong

2020-06-15 Thread Joshua Stark
Thanks Jamie,

Ah, cool, so that ufw config is when the install is a client.

I am having issues with the install as a DHCPv4 server.

I will revert the UFW changes I have made and add in a new
/etc/ufw/application.d/dhcpd config to allow the install to run a DHCPv4
server

Thanks
Josh


PS. isc-dhcp-server when setup, by default is using "raw" sockets and thus the 
ufw rules are bypassed

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

Title:
  Firewall rule in before.rules for dhcp is wrong

Status in ufw package in Ubuntu:
  Invalid

Bug description:
  The file delivered - /usr/share/ufw/iptables/before.rules
  which is then copied to - /etc/ufw/before.rules

  Delivered by Package:

  # allow dhcp client to work
  -A ufw-before-input -p udp --sport 67 --dport 68 -j ACCEPT

  The ports for
  --sport and --dport are swapped

  Should be:

  -A ufw-before-input -p udp --sport 68 --dport 67 -j ACCEPT

  
  Package version found in:
0.36-0ubuntu0.1

  
  Note: ISC DHCP uses RAW sockets, which bypasses iptables anyway and doesn't 
drop the packets with the incorrect configuration. This has had me stumped for 
the last hour.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1882484/+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 1882314] Re: Firewall rule in before6.rules for dhcp6 is wrong

2020-06-15 Thread Joshua Stark
Thanks Jamie,

Ah, cool, so that ufw config is when the install is a client.

I am having issues with the install as a DHCPv6 server.

I will revert the UFW changes I have made and add in a new
/etc/ufw/application.d/dhcpd config to allow the install to run a DHCPv6
server

Thanks
Josh

PS. isc-dhcp-server6 when setup, by default is not using "raw" sockets
and thus the ufw rules are enforced

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

Title:
  Firewall rule in before6.rules for dhcp6 is wrong

Status in ufw package in Ubuntu:
  Invalid

Bug description:
  When running DHCPv6, clients are not able get IP address.
  The firewall rule in ip6table is incorrect, and not allowing client requests 
in. The ports need to be swapped and the dst address needs to be removed, as 
it's a broadcast

  The file delivered - /usr/share/ufw/iptables/before6.rules
  which is then copied to - /etc/ufw/before6.rules

  Delivered by Package:

  # allow dhcp client to work
  -A ufw6-before-input -p udp -s fe80::/10 --sport 547 -d fe80::/10 --dport 546 
-j ACCEPT

  The ports for
  --sport and --dport are swapped
  -d fe80::/10 needs to be removed

  Should be:

  -A ufw6-before-input -p udp -s fe80::/10 --sport 546 --dport 547 -j
  ACCEPT

  Package version found in:
    0.36-0ubuntu0.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1882314/+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 1883483] Re: Xorg freeze and hang

2020-06-15 Thread Ubuntu Foundations Team Bug Bot
*** This bug is a duplicate of bug 1879234 ***
https://bugs.launchpad.net/bugs/1879234

** Package changed: ubuntu => xorg (Ubuntu)

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

Title:
  Xorg freeze and hang

Status in xorg package in Ubuntu:
  New

Bug description:
  when i use my pc i check my activities but wheen i click on activities
  that time my pc going to freez.i can not to back to home page .i was
  really depressed.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.3.0-59.53~18.04.1-generic 5.3.18
  Uname: Linux 5.3.0-59-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 15 11:21:04 2020
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000]
  MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-59-generic 
root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset 
vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F23
  dmi.board.asset.tag: Default string
  dmi.board.name: A320M-S2H-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: A320M-S2H
  dmi.product.sku: Default string
  dmi.product.version: Default string
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
  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/1883483/+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 1883483] [NEW] Xorg freeze and hang

2020-06-15 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

when i use my pc i check my activities but wheen i click on activities
that time my pc going to freez.i can not to back to home page .i was
really depressed.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.3.0-59.53~18.04.1-generic 5.3.18
Uname: Linux 5.3.0-59-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.15
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Jun 15 11:21:04 2020
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd Radeon RX Vega 11 [1458:d000]
MachineType: Gigabyte Technology Co., Ltd. A320M-S2H
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-59-generic 
root=UUID=38903ee5-fb7c-4faa-ac0c-0a499b16e531 ro quiet splash nomodeset 
vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/08/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F23
dmi.board.asset.tag: Default string
dmi.board.name: A320M-S2H-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF23:bd08/08/2018:svnGigabyteTechnologyCo.,Ltd.:pnA320M-S2H:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnA320M-S2H-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: A320M-S2H
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3
version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug bionic false-gpu-hang freeze ubuntu
-- 
Xorg freeze and hang
https://bugs.launchpad.net/bugs/1883483
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg 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 1883580] Re: frame drop issue

2020-06-15 Thread Daniel van Vugt
I can't see any obvious reason for the frame dropping yet.

1. When it happens, does 'top' report high CPU in any process?

2. When it happens, please run:

   journalctl -b0 > journal.txt

   and attach the resulting text file here.

3. Please run 'gnome-shell-extension-prefs' and disable some/all of the
extensions to see if that avoids the issue.

4. What exactly is dropping frames? Is it a specific app?


** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Summary changed:

- frame drop issue
+ [modeset+nvidia] frame drop issue

** Tags added: performance

** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

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

Title:
  [modeset+nvidia] frame drop issue

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  i have severe graphical drop frames however my hardware is nvidia gtx
  850 4 gigs and intel graphic card

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Mon Jun 15 21:30:09 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated 
Graphics Controller [1043:11cd]
 Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:11cd]
  InstallationDate: Installed on 2020-06-10 (5 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: ASUSTeK COMPUTER INC. N550JK
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=ebd465fe-6414-4b7d-a0c0-ec4fdbd2aaa5 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/23/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N550JK.204
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N550JK
  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.:bvrN550JK.204:bd01/23/2014:svnASUSTeKCOMPUTERINC.:pnN550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: N
  dmi.product.name: N550JK
  dmi.product.sku: ASUS-NotebookSKU
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1883580/+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 1883534] Re: Screen flickering

2020-06-15 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1853094 ***
https://bugs.launchpad.net/bugs/1853094

Oh, actually there is a solution... Just choose 'Ubuntu on Wayland' on
the login screen.

** This bug has been marked a duplicate of bug 1853094
   [modeset] Screen tearing when using multiple monitors

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

Title:
  Screen flickering

Status in xorg package in Ubuntu:
  New

Bug description:
  To whom it may concern,

  As stated I have screen flickerings (see lightning like flickering on photo 
attached for portrait screen, for horizontal screen I also have screen 
flickering on the upper part but hard to catch in a photo) on freshly installed 
Ubuntu 20.04 LTS.
  I have tried this:

  https://askubuntu.com/questions/1231441/ubuntu-screen-flickering

  and this:

  https://learnubuntumate.weebly.com/screen-tearing-on-intel-
  graphics.html

  without success. I have also seen some other people mentioning screen
  flickering on ubuntu 20.04 here:

  
https://www.reddit.com/r/Ubuntu/comments/fvk536/anyone_else_noticing_window_flickering_on_ubuntu/

  without solution.

  I also know that it is very unlikely hardware problem because my screens were 
displaying well on archlinux. I think my graphic card info are already included 
in the report but just in case: Intel Corporation UHD Graphics 630. Might be 
intel driver problems ?
  Could you help me on this please ?

  Best regards,
  Jeremy

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 15 15:05:27 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Desktop) [8086:3e92] (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. UHD Graphics 630 (Desktop) [1043:8694]
  InstallationDate: Installed on 2020-06-12 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046a:0023 Cherry GmbH Keyboard
   Bus 001 Device 003: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
   |__ Port 9: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
1.5M
   |__ Port 9: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 
1.5M
   |__ Port 10: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 
1.5M
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=81cee77a-b529-4dac-9834-dc6d5ab2dc16 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/11/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0615
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME Z370-P
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0615:bd04/11/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ370-P:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1883534] Re: Screen flickering

2020-06-15 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1853094 ***
https://bugs.launchpad.net/bugs/1853094

Thanks for the bug report.

It appears the tearing issue with the 'modesetting' driver is bug
1853094.

And you might also be experiencing extra flicker when you are using the
'intel' driver, which is bug 1867668.

So it seems you have to choose one bug or the other right now, sorry :(

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

Title:
  Screen flickering

Status in xorg package in Ubuntu:
  New

Bug description:
  To whom it may concern,

  As stated I have screen flickerings (see lightning like flickering on photo 
attached for portrait screen, for horizontal screen I also have screen 
flickering on the upper part but hard to catch in a photo) on freshly installed 
Ubuntu 20.04 LTS.
  I have tried this:

  https://askubuntu.com/questions/1231441/ubuntu-screen-flickering

  and this:

  https://learnubuntumate.weebly.com/screen-tearing-on-intel-
  graphics.html

  without success. I have also seen some other people mentioning screen
  flickering on ubuntu 20.04 here:

  
https://www.reddit.com/r/Ubuntu/comments/fvk536/anyone_else_noticing_window_flickering_on_ubuntu/

  without solution.

  I also know that it is very unlikely hardware problem because my screens were 
displaying well on archlinux. I think my graphic card info are already included 
in the report but just in case: Intel Corporation UHD Graphics 630. Might be 
intel driver problems ?
  Could you help me on this please ?

  Best regards,
  Jeremy

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 15 15:05:27 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Desktop) [8086:3e92] (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. UHD Graphics 630 (Desktop) [1043:8694]
  InstallationDate: Installed on 2020-06-12 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046a:0023 Cherry GmbH Keyboard
   Bus 001 Device 003: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
   |__ Port 9: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
1.5M
   |__ Port 9: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 
1.5M
   |__ Port 10: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 
1.5M
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=81cee77a-b529-4dac-9834-dc6d5ab2dc16 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/11/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0615
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME Z370-P
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0615:bd04/11/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ370-P:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1883516] Re: display is freezing randomly

2020-06-15 Thread Daniel van Vugt
When the problem is happening please:

1. Tell us if running 'top' in a Terminal reports any high CPU usage.

2. Run:

   journalctl -b0 > journal.txt

   and attach the resulting text file here.

3. Run 'gnome-shell-extension-prefs' and tell us if disabling any/all of
them avoids the problem.


** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

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

** Changed in: gnome-shell (Ubuntu)
   Status: New => Incomplete

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

Title:
  display is freezing randomly

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  My display is freezing randomly, while the system seems to be running,
  since music is playing.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 15 11:58:54 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 620 [17aa:505f]
  InstallationDate: Installed on 2020-04-24 (51 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 20J5S00C00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=47fb22f8-4f7e-4824-80f7-5db5105765e0 ro intel_idle.max_cstate=1 quiet 
splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/24/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0GET63W (1.63 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20J5S00C00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0GET63W(1.63):bd02/24/2018:svnLENOVO:pn20J5S00C00:pvrThinkPadL470:rvnLENOVO:rn20J5S00C00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad L470
  dmi.product.name: 20J5S00C00
  dmi.product.sku: LENOVO_MT_20J5_BU_Think_FM_ThinkPad L470
  dmi.product.version: ThinkPad L470
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1883516/+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 1576559] Re: Refused to switch profile to headset_head_unit: Not connected

2020-06-15 Thread Marcio
Same problem.
Ubuntu 20.04 LTS, JBL TUNE 120TWS (A2DP 1.3 AVRCP 1.5 HFP 1.6)

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

Title:
  Refused to switch profile to headset_head_unit: Not connected

Status in PulseAudio:
  Unknown
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I'm trying to connect a bluetooth-speaker-with-microphone (Mi
  Bluetooth Speaker) to Ubuntu. It works well as an A2DP sync, but can't
  use it as a headset with microphone.

  The device doesn't list in the "Input Devices" by default, and using
  the sound settings to change the profile of the device to HSP/HFP
  results in this log message:

  W: [pulseaudio] module-bluez5-device.c: Refused to switch profile to
  headset_head_unit: Not connected

  
  I'm running Ubuntu 16.04 LTS. I did an upgrade from Ubuntu 15.10.

  pulseaudio:
Installed: 1:8.0-0ubuntu3

  bluez:
Installed: 5.37-0ubuntu5

To manage notifications about this bug go to:
https://bugs.launchpad.net/pulseaudio/+bug/1576559/+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 1881982] Re: memory exhaustion in parse_report()

2020-06-15 Thread Seong-Joong Kim
** Description changed:

  Hi,
  
  I have found a security issue on whoopsie 0.2.69 and earlier.
  
  ## Vulnerability in whoopsie
- - whoopsie 0.2.69 and earlier have a memory leak vulnerability.
- - An attacker can cause a denial of service (application crash) via a crafted 
.crash file.
+ - It was discovered that whoopsie incorrectly handled certain malformed crash 
files. If a user using whoopsie were tricked into parsing and uploading a 
specially crafted crash file, an attacker could exploit this to cause a denial 
of service. 
  
  ## Basic
  When a program has been crashed, Linux system tries to create a '.crash' file 
on '/var/crash/' directory with python script located in 
'/usr/share/apport/apport'.
  The file contains a series of system crash information including core dump, 
syslog, stack trace, memory map info, etc.
  A user is given read and write permission to the file.
  After then, whoopsie parses key-value pairs in ‘.crash’ file and encodes it 
into binary json (bson) format.
  Lastly, whoopsie forwards the data to a remotely connected Ubuntu error 
report system.
  
  ## Vulnerability
  We have found a memory leak vulnerability during the parsing the crash file, 
when a collision occurs on GHashTable through g_hash_table_insert().
  According to [1], if the key already exists in the GHashTable, its current 
value is replaced with the new value.
  If 'key_destory_func' and 'value_destroy_func' are supplied when creating the 
table, the old value and the passed key are freed using that function.
  Unfortunately, whoopsie does not handle the old value and the passed key when 
collision happens.
  If a crash file contains same repetitive key-value pairs, it leads to memory 
leak as much as the amount of repetition and results in denial-of-service.
  
  ## Attack
- 1) Create a fake.crash file
- memory_leak_poc.py script measures an available memory and generates a 
malicious crash file that contains same repetitive key-value pairs as much as 
20% of the available memory size; 'ProblemType: Crash'.
- 20% indicates arbitrary amount of the memory leakage.
- 2) Before the attack, the script checks memory usage of whoopsie process with 
psutil
- 3) It triggers the whoopsie to read the fake.crash file
- 4) Then, it measures the memory usage of whoopsie process
- 5) It results in denial-of-service and then other users can no longer report 
crash to the Ubuntu error report system.
+ 1) Generates a certain malformed crash file that contains same repetitive 
key-value pairs.
+ 2) Trigger the whoopsie to read the generated crash file.
+ 3) After then, the whoopsie process has been killed.
  
  ## Mitigation
  We should use g_hash_table_new_full() with ‘key_destroy_func’ and 
‘value_destroy_func’ functions instead of g_hash_table_new().
  Otherwise, before g_hash_table_insert(), we should check the collision via 
g_hash_table_lookup_extended() and obtain pointer to the old value and remove 
it.
  
  Sincerely,
  
  [1] https://developer.gnome.org/glib/stable/glib-Hash-Tables.html#g
  -hash-table-insert

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

Title:
  memory exhaustion in parse_report()

Status in whoopsie package in Ubuntu:
  New

Bug description:
  Hi,

  I have found a security issue on whoopsie 0.2.69 and earlier.

  ## Vulnerability in whoopsie
  - It was discovered that whoopsie incorrectly handled certain malformed crash 
files. If a user using whoopsie were tricked into parsing and uploading a 
specially crafted crash file, an attacker could exploit this to cause a denial 
of service. 

  ## Basic
  When a program has been crashed, Linux system tries to create a '.crash' file 
on '/var/crash/' directory with python script located in 
'/usr/share/apport/apport'.
  The file contains a series of system crash information including core dump, 
syslog, stack trace, memory map info, etc.
  A user is given read and write permission to the file.
  After then, whoopsie parses key-value pairs in ‘.crash’ file and encodes it 
into binary json (bson) format.
  Lastly, whoopsie forwards the data to a remotely connected Ubuntu error 
report system.

  ## Vulnerability
  We have found a memory leak vulnerability during the parsing the crash file, 
when a collision occurs on GHashTable through g_hash_table_insert().
  According to [1], if the key already exists in the GHashTable, its current 
value is replaced with the new value.
  If 'key_destory_func' and 'value_destroy_func' are supplied when creating the 
table, the old value and the passed key are freed using that function.
  Unfortunately, whoopsie does not handle the old value and the passed key when 
collision happens.
  If a crash file contains same repetitive key-value pairs, it leads to memory 
leak as much as the amount of repetition and results in denial-of-service.

  ## Attack
  1) Generates a certain 

[Touch-packages] [Bug 1882525] Re: [amdgpu] MATE desktop is corrupted upon login on Ryzen APU

2020-06-15 Thread Daniel van Vugt
That's not surprising. Any bug in MATE, or bug experienced via Marco,
might be years old and also present in Ubuntu 19.10. But more likely
this bug is the combined result of MATE + AMD meaning it might have only
just become noticeable in 20.04.

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

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

Title:
  [amdgpu] MATE desktop is corrupted upon login on Ryzen APU

Status in marco package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  Today I upgraded from Ubuntu MATE 19.10 to 20.04. After doing so, Ubuntu 
boots normally to the display manager (login screen) as expected. But once I 
log in, everything on the screen is cut up into horizontal slices, with each 
slice offset farther right than the slice above, and squares of random colors 
running diagonally across the screen. I've attached a picture of my monitor 
showing the issue for reference.
  My hardware is a home-built PC with an ASUS Prime B450M motherboard, a Ryzen 
3 2200G APU, and using that APU's integrated graphics.
  In terms of software I'm running Ubuntu 20.04, which I just upgraded to and 
did a software update on. I have Linux 5.4.0-33-generic, X.Org 1.20.8, and Mesa 
20.0.4. Before I upgraded Ubuntu, I was affected by Bug #1880041 but it seems 
fixed in the new kernel. I don't believe they're related but I figure it's 
worth mentioning.
  I tried adding the nomodeset kernel option at boot, and it's an effective 
workaround. Also, I tried booting from an Ubuntu Mate 20.04 live USB to see if 
this was caused by some quirk of my particular software setup, and successfully 
reproduced the bug, proving it wasn't.
  If you'd like me to, I can provide log files, system information, etc. or 
help narrow it down by testing workarounds.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Mon Jun  8 06:41:47 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExecutablePath: /usr/lib/xorg/Xorg
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / 
Radeon Vega Mobile Series] [1002:15dd] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Raven Ridge [Radeon Vega Series / Radeon 
Vega Mobile Series] [1043:876b]
  InstallationDate: Installed on 2019-10-20 (231 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017)
  MachineType: System manufacturer System Product Name
  ProcEnviron: PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=43189257-cc94-4e98-ac1d-e16336dd152e ro quiet splash vt.handoff=7
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/13/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 2006
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B450M-A
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr2006:bd11/13/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450M-A:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/marco/+bug/1882525/+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 1881982] Re: memory exhaustion in parse_report()

2020-06-15 Thread Seong-Joong Kim
** Summary changed:

- Memory leak in parse_report()
+ memory exhaustion in parse_report()

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

Title:
  memory exhaustion in parse_report()

Status in whoopsie package in Ubuntu:
  New

Bug description:
  Hi,

  I have found a security issue on whoopsie 0.2.69 and earlier.

  ## Vulnerability in whoopsie
  - whoopsie 0.2.69 and earlier have a memory leak vulnerability.
  - An attacker can cause a denial of service (application crash) via a crafted 
.crash file.

  ## Basic
  When a program has been crashed, Linux system tries to create a '.crash' file 
on '/var/crash/' directory with python script located in 
'/usr/share/apport/apport'.
  The file contains a series of system crash information including core dump, 
syslog, stack trace, memory map info, etc.
  A user is given read and write permission to the file.
  After then, whoopsie parses key-value pairs in ‘.crash’ file and encodes it 
into binary json (bson) format.
  Lastly, whoopsie forwards the data to a remotely connected Ubuntu error 
report system.

  ## Vulnerability
  We have found a memory leak vulnerability during the parsing the crash file, 
when a collision occurs on GHashTable through g_hash_table_insert().
  According to [1], if the key already exists in the GHashTable, its current 
value is replaced with the new value.
  If 'key_destory_func' and 'value_destroy_func' are supplied when creating the 
table, the old value and the passed key are freed using that function.
  Unfortunately, whoopsie does not handle the old value and the passed key when 
collision happens.
  If a crash file contains same repetitive key-value pairs, it leads to memory 
leak as much as the amount of repetition and results in denial-of-service.

  ## Attack
  1) Create a fake.crash file
  memory_leak_poc.py script measures an available memory and generates a 
malicious crash file that contains same repetitive key-value pairs as much as 
20% of the available memory size; 'ProblemType: Crash'.
  20% indicates arbitrary amount of the memory leakage.
  2) Before the attack, the script checks memory usage of whoopsie process with 
psutil
  3) It triggers the whoopsie to read the fake.crash file
  4) Then, it measures the memory usage of whoopsie process
  5) It results in denial-of-service and then other users can no longer report 
crash to the Ubuntu error report system.

  ## Mitigation
  We should use g_hash_table_new_full() with ‘key_destroy_func’ and 
‘value_destroy_func’ functions instead of g_hash_table_new().
  Otherwise, before g_hash_table_insert(), we should check the collision via 
g_hash_table_lookup_extended() and obtain pointer to the old value and remove 
it.

  Sincerely,

  [1] https://developer.gnome.org/glib/stable/glib-Hash-Tables.html#g
  -hash-table-insert

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1881982/+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 1868520] Re: Wayland apps fail to run with zwp_linux_dmabuf error (failed to import supplied dmabufs: Unsupported buffer format 808669784 [DRM_FORMAT_XRGB2101010]) (or 808665665

2020-06-15 Thread Daniel van Vugt
** Changed in: mesa (Ubuntu Focal)
   Status: Confirmed => In Progress

** Changed in: mesa (Ubuntu Focal)
   Importance: Undecided => High

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

Title:
  Wayland apps fail to run with zwp_linux_dmabuf error (failed to import
  supplied dmabufs: Unsupported buffer format 808669784
  [DRM_FORMAT_XRGB2101010]) (or 808665665 [DRM_FORMAT_ABGR2101010])

Status in Mesa:
  Fix Released
Status in MPV:
  Unknown
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Focal:
  In Progress

Bug description:
  [Impact]

  Wayland apps fail to start in focal with:

  error 7: failed to import supplied dmabufs: Unsupported buffer format
  808669784

  [Test Case]

  Just run: es2gears_wayland

  [Regression Potential]

  Medium/unknown. The fix is quite new.

  [Other Info]

  When attempting to run es2gears_wayland against GNOME Shell, it fails
  with:

  EGL_VERSION = 1.5
  vertex shader info:
  fragment shader info:
  info:
  [destroyed object]: error 7: failed to import supplied dmabufs: Unsupported 
buffer format 808669784

  The full wayland protocol trace is:

  [3104432.914]  -> wl_display@1.get_registry(new id wl_registry@2)
  [3104432.972]  -> wl_disp...@1.sync(new id wl_callback@3)
  [3104433.139] wl_display@1.delete_id(3)
  [3104433.175] wl_registry@2.global(1, "wl_drm", 2)
  [3104433.207] wl_registry@2.global(2, "wl_compositor", 4)
  [3104433.240]  -> wl_regis...@2.bind(2, "wl_compositor", 1, new id 
[unknown]@4)
  [3104433.285] wl_registry@2.global(3, "wl_shm", 1)
  [3104433.316] wl_registry@2.global(4, "wl_output", 2)
  [3104433.347] wl_registry@2.global(5, "zxdg_output_manager_v1", 3)
  [3104433.376] wl_registry@2.global(6, "wl_data_device_manager", 3)
  [3104433.404] wl_registry@2.global(7, "gtk_primary_selection_device_manager", 
1)
  [3104433.432] wl_registry@2.global(8, "wl_subcompositor", 1)
  [3104433.459] wl_registry@2.global(9, "xdg_wm_base", 2)
  [3104433.485] wl_registry@2.global(10, "zxdg_shell_v6", 1)
  [3104433.513] wl_registry@2.global(11, "wl_shell", 1)
  [3104433.542]  -> wl_regis...@2.bind(11, "wl_shell", 1, new id [unknown]@5)
  [3104433.582] wl_registry@2.global(12, "gtk_shell1", 3)
  [3104433.611] wl_registry@2.global(13, "wp_viewporter", 1)
  [3104433.640] wl_registry@2.global(14, "zwp_pointer_gestures_v1", 1)
  [3104433.670] wl_registry@2.global(15, "zwp_tablet_manager_v2", 1)
  [3104433.699] wl_registry@2.global(16, "wl_seat", 5)
  [3104433.728] wl_registry@2.global(17, "zwp_relative_pointer_manager_v1", 1)
  [3104433.758] wl_registry@2.global(18, "zwp_pointer_constraints_v1", 1)
  [3104433.787] wl_registry@2.global(19, "zxdg_exporter_v1", 1)
  [3104433.816] wl_registry@2.global(20, "zxdg_importer_v1", 1)
  [3104433.846] wl_registry@2.global(21, "zwp_linux_dmabuf_v1", 3)
  [3104433.875] wl_registry@2.global(22, 
"zwp_keyboard_shortcuts_inhibit_manager_v1", 1)
  [3104433.904] wl_registry@2.global(23, "zwp_text_input_manager_v3", 1)
  [3104433.933] wl_registry@2.global(24, "gtk_text_input_manager", 1)
  [3104433.960] wl_registry@2.global(26, "wl_eglstream_controller", 1)
  [3104433.991] wl_callb...@3.done(3421)
  [3104436.266]  -> wl_display@1.get_registry(new id wl_registry@3)
  [3104436.279]  -> wl_disp...@1.sync(new id wl_callback@6)
  [3104436.647] wl_display@1.delete_id(6)
  [3104436.672] wl_registry@3.global(1, "wl_drm", 2)
  [3104436.726]  -> wl_regis...@3.bind(1, "wl_drm", 2, new id [unknown]@7)
  [3104436.744] wl_registry@3.global(2, "wl_compositor", 4)
  [3104436.780] wl_registry@3.global(3, "wl_shm", 1)
  [3104436.790] wl_registry@3.global(4, "wl_output", 2)
  [3104436.803] wl_registry@3.global(5, "zxdg_output_manager_v1", 3)
  [3104436.833] wl_registry@3.global(6, "wl_data_device_manager", 3)
  [3104436.868] wl_registry@3.global(7, "gtk_primary_selection_device_manager", 
1)
  [3104436.882] wl_registry@3.global(8, "wl_subcompositor", 1)
  [3104436.898] wl_registry@3.global(9, "xdg_wm_base", 2)
  [3104436.913] wl_registry@3.global(10, "zxdg_shell_v6", 1)
  [3104436.925] wl_registry@3.global(11, "wl_shell", 1)
  [3104436.937] wl_registry@3.global(12, "gtk_shell1", 3)
  [3104436.950] wl_registry@3.global(13, "wp_viewporter", 1)
  [3104436.963] wl_registry@3.global(14, "zwp_pointer_gestures_v1", 1)
  [3104436.976] wl_registry@3.global(15, "zwp_tablet_manager_v2", 1)
  [3104436.990] wl_registry@3.global(16, "wl_seat", 5)
  [3104437.001] wl_registry@3.global(17, "zwp_relative_pointer_manager_v1", 1)
  [3104437.013] wl_registry@3.global(18, "zwp_pointer_constraints_v1", 1)
  [3104437.026] wl_registry@3.global(19, "zxdg_exporter_v1", 1)
  [3104437.038] wl_registry@3.global(20, "zxdg_importer_v1", 1)
  [3104437.051] wl_registry@3.global(21, "zwp_linux_dmabuf_v1", 3)
  [3104437.066]  -> wl_regis...@3.bind(21, "zwp_linux_dmabuf_v1", 3, new id 
[unknown]@8)
  [3104437.083] 

[Touch-packages] [Bug 1559650] Re: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk()

2020-06-15 Thread Daniel van Vugt
** Description changed:

  [Impact]
  
- gnome-shell crashes a lot. Over 38000 times in bionic so far:
+ gnome-shell crashes a lot. Over 41000 times in bionic so far:
  https://errors.ubuntu.com/problem/00455200cd9fb890dacfe09b92c7bda2f6ad3af7
  
  [Test Case]
  
  None known yet. Just keeping an eye on the above link for regressions.
  
  [Regression Potential]
  
  Low. The same fix has been released to newer distros for the past 2
  years already.
  
  [Other Info]
  
  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gnome-shell 3.18.4-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5
  Uname: Linux 4.4.0-13-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Wed Mar 16 17:15:11 2016
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:
  
  InstallationDate: Installed on 2016-03-13 (6 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160311)
  ProcCmdline: gnome-shell --mode=gdm --wayland --display-server
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7f1ff33f46ab <___vsnprintf_chk+107>: movb   
$0x0,(%r12)
   PC (0x7f1ff33f46ab) ok
   source "$0x0" ok
   destination "(%r12)" (0x) not located in a known VMA region (needed 
writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ___vsnprintf_chk (s=0x0, maxlen=, flags=1, slen=, format=0x7f1fe54ccae5 "%s%s", args=args@entry=0x7f1fce502da8) at 
vsnprintf_chk.c:55
   ___snprintf_chk (s=, maxlen=, flags=, slen=, format=) at snprintf_chk.c:34
   XauFileName () from /usr/lib/x86_64-linux-gnu/libXau.so.6
   XauGetBestAuthByAddr () from /usr/lib/x86_64-linux-gnu/libXau.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
  Title: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

Title:
  gnome-shell crashed with SIGSEGV in ___vsnprintf_chk()

Status in libxau package in Ubuntu:
  Fix Released
Status in libxau source package in Bionic:
  In Progress
Status in libxau source package in Eoan:
  Fix Released
Status in libxau source package in Focal:
  Fix Released

Bug description:
  [Impact]

  gnome-shell crashes a lot. Over 41000 times in bionic so far:
  https://errors.ubuntu.com/problem/00455200cd9fb890dacfe09b92c7bda2f6ad3af7

  [Test Case]

  None known yet. Just keeping an eye on the above link for regressions.

  [Regression Potential]

  Low. The same fix has been released to newer distros for the past 2
  years already.

  [Other Info]

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gnome-shell 3.18.4-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5
  Uname: Linux 4.4.0-13-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Wed Mar 16 17:15:11 2016
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2016-03-13 (6 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160311)
  ProcCmdline: gnome-shell --mode=gdm --wayland --display-server
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7f1ff33f46ab <___vsnprintf_chk+107>: movb   
$0x0,(%r12)
   PC (0x7f1ff33f46ab) ok
   source "$0x0" ok
   destination "(%r12)" (0x) not located in a known VMA region (needed 
writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ___vsnprintf_chk (s=0x0, maxlen=, flags=1, slen=, format=0x7f1fe54ccae5 "%s%s", args=args@entry=0x7f1fce502da8) at 
vsnprintf_chk.c:55
   ___snprintf_chk (s=, maxlen=, flags=, slen=, format=) at snprintf_chk.c:34
   XauFileName () from /usr/lib/x86_64-linux-gnu/libXau.so.6
   XauGetBestAuthByAddr () from /usr/lib/x86_64-linux-gnu/libXau.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
  Title: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxau/+bug/1559650/+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 1871154] Re: Error message displayed during boot (mountroot hook, premount)

2020-06-15 Thread Launchpad Bug Tracker
This bug was fixed in the package initramfs-tools - 0.136ubuntu6.1

---
initramfs-tools (0.136ubuntu6.1) focal; urgency=medium

  * SRU changes from Dimitri John Ledkov into focal:
- Partially revert 0.133ubuntu12 upload:
  "* scripts/functions: Fix args in the add_mountroot_fail_check function."
  The arguments were correct, as used by lvm2 hook.
  LP: #1871154
- Fix copying libgcc_s when there is optimized pthreads installed.
  LP: #1880853

 -- Gianfranco Costamagna   Mon, 01 Jun 2020
11:03:12 +0200

** Changed in: initramfs-tools (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  Error message displayed during boot (mountroot hook, premount)

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in lvm2 package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Focal:
  Fix Released
Status in lvm2 source package in Focal:
  Invalid

Bug description:
  [Impact] 
  * People using lvm2 on ubuntu focal are getting a strange and weird message 
due to a wrong path

  [Test Case]
  * Install lvm2 on Ubuntu 20.04

  [Regression Potential] 
  * Low, the fix is already part of groovy

  [Other info]
  Hi,

  my Ubuntu system uses LVM2 for its root file system.  It boots
  correctly, but an ugly error message is displayed during boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: lvm2 2.03.07-1ubuntu1
  Uname: Linux 5.6.2-050602-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Apr  6 17:59:03 2020
  SourcePackage: lvm2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

2020-06-15 Thread Brian Murray
The verification of the Stable Release Update for initramfs-tools has
completed successfully and the package is now being 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 initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1880853

Title:
  libc6-lse lets update-initramfs fail on AWS m6g instances

Status in cloud-images:
  New
Status in btrfs-progs package in Ubuntu:
  Invalid
Status in glibc package in Ubuntu:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in btrfs-progs source package in Focal:
  Invalid
Status in glibc source package in Focal:
  Invalid
Status in initramfs-tools source package in Focal:
  Fix Released

Bug description:
  [Impact]

   * update-initramfs -u fails on arm64 m6g instances in AWS

  [Test Case]

   * launch m6g instance in AWS
   * install libc6-lse (if not installed)
   * run $ update-initramfs -u
   * It should suceed

  [Regression Potential]

   * Adding one more path to libgcc_s1 resolution. This will still fail
  if something compiles libc6 for _two_ optimisations like
  /lib/$arch/foo/bar/libpthread.

  [Other Info]

   * libphtread dlopens libgcc_s1, thus whenever libpthread is needed in
  the initrd libgcc_s1 must be copied in too. However the logic to find
  matching libgcc_s1 is broken for optimizied builds of libc6 without
  optimized build of libgcc_s1. I think libpthread should link against
  libgcc_s1 to prevent these issues.

   * Original bug report

  With Ubuntu 20.04 on AWS m6g.* instance family, installing libc6-lse
  lets update-initramfs always fail with the following error:

  ubuntu@ip-10-18-23-79:~$ sudo update-initramfs -u
  update-initramfs: Generating /boot/initrd.img-5.4.0-1011-aws
  E: /usr/share/initramfs-tools/hooks/btrfs failed with return 1.
  update-initramfs: failed for /boot/initrd.img-5.4.0-1011-aws with 1.

  ## Steps to reproduce (on AWS)

  ### With focal 20200423 AMI

  1. Find the following AMI and launch on m6g instance family

     ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200423

  2. Run: sudo apt update && sudo apt install libc6-lse
  3. Try: sudo update-initramfs -u

  ### With focal 20200522 AMI

  1. Find the following AMI and launch on m6g instance family

     ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200522

  2. Try: sudo update-initramfs -u

  ## Note

  - The entire log of the above steps performed on 20200423 AMI is attached.
  - Latest cloud-image AMI 
"ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200522" includes 
libc6-lse. On 20200522 AMI, this doesn't reproduce after removing libc6-lse 
manually.
  - This doesn't reproduce on EC2 a1.* instance family.

  ## Expected behavior

  Does not fail.

  ## Background to find this bug

  As the 20200522 AMI includes libc6-lse out-of-the-box & apt-get
  upgrade pulls newer package that triggers update-initramfs, apt-get
  upgrade always fail on 20200522 AMI.

  the following is an apport report on 20200423 AMI:

  

  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: arm64
  CasperMD5CheckResult: skip
  Date: Wed May 27 09:52:16 2020
  Dependencies:
   gcc-10-base 10-20200411-0ubuntu1
   libc6 2.31-0ubuntu9
   libcrypt1 1:4.4.10-10ubuntu4
   libgcc-s1 10-20200411-0ubuntu1
   libidn2-0 2.2.0-2
   libunistring2 0.9.10-2
  DistroRelease: Ubuntu 20.04
  Ec2AMI: ami-061102f51d47b1c24
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: ap-northeast-1c
  Ec2InstanceType: m6g.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  Package: libc6-lse 2.31-0ubuntu9
  PackageArchitecture: arm64
  ProcCpuinfoMinimal:
   processor  : 0
   BogoMIPS   : 243.75
   Features   : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp 
asimdhp cpuid asimdrdm lrcpc dcpop asimddp ssbs
   CPU implementer: 0x41
   CPU architecture: 8
   CPU variant: 0x3
   CPU part   : 0xd0c
   CPU revision   : 1
  ProcEnviron:
   LANG=C.UTF-8
   TERM=screen-256color
   PATH=(custom, no user)
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-1009.9-aws 5.4.30
  SourcePackage: glibc
  Tags:  focal ec2-images
  Uname: Linux 5.4.0-1009-aws aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1880853/+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 1871154] Update Released

2020-06-15 Thread Brian Murray
The verification of the Stable Release Update for initramfs-tools has
completed successfully and the package is now being 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 lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1871154

Title:
  Error message displayed during boot (mountroot hook, premount)

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in lvm2 package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Focal:
  Fix Released
Status in lvm2 source package in Focal:
  Invalid

Bug description:
  [Impact] 
  * People using lvm2 on ubuntu focal are getting a strange and weird message 
due to a wrong path

  [Test Case]
  * Install lvm2 on Ubuntu 20.04

  [Regression Potential] 
  * Low, the fix is already part of groovy

  [Other info]
  Hi,

  my Ubuntu system uses LVM2 for its root file system.  It boots
  correctly, but an ugly error message is displayed during boot.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: lvm2 2.03.07-1ubuntu1
  Uname: Linux 5.6.2-050602-generic x86_64
  ApportVersion: 2.20.11-0ubuntu22
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Mon Apr  6 17:59:03 2020
  SourcePackage: lvm2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1871154/+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 1880853] Re: libc6-lse lets update-initramfs fail on AWS m6g instances

2020-06-15 Thread Launchpad Bug Tracker
This bug was fixed in the package initramfs-tools - 0.136ubuntu6.1

---
initramfs-tools (0.136ubuntu6.1) focal; urgency=medium

  * SRU changes from Dimitri John Ledkov into focal:
- Partially revert 0.133ubuntu12 upload:
  "* scripts/functions: Fix args in the add_mountroot_fail_check function."
  The arguments were correct, as used by lvm2 hook.
  LP: #1871154
- Fix copying libgcc_s when there is optimized pthreads installed.
  LP: #1880853

 -- Gianfranco Costamagna   Mon, 01 Jun 2020
11:03:12 +0200

** Changed in: initramfs-tools (Ubuntu Focal)
   Status: Fix Committed => Fix Released

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

Title:
  libc6-lse lets update-initramfs fail on AWS m6g instances

Status in cloud-images:
  New
Status in btrfs-progs package in Ubuntu:
  Invalid
Status in glibc package in Ubuntu:
  Invalid
Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in btrfs-progs source package in Focal:
  Invalid
Status in glibc source package in Focal:
  Invalid
Status in initramfs-tools source package in Focal:
  Fix Released

Bug description:
  [Impact]

   * update-initramfs -u fails on arm64 m6g instances in AWS

  [Test Case]

   * launch m6g instance in AWS
   * install libc6-lse (if not installed)
   * run $ update-initramfs -u
   * It should suceed

  [Regression Potential]

   * Adding one more path to libgcc_s1 resolution. This will still fail
  if something compiles libc6 for _two_ optimisations like
  /lib/$arch/foo/bar/libpthread.

  [Other Info]

   * libphtread dlopens libgcc_s1, thus whenever libpthread is needed in
  the initrd libgcc_s1 must be copied in too. However the logic to find
  matching libgcc_s1 is broken for optimizied builds of libc6 without
  optimized build of libgcc_s1. I think libpthread should link against
  libgcc_s1 to prevent these issues.

   * Original bug report

  With Ubuntu 20.04 on AWS m6g.* instance family, installing libc6-lse
  lets update-initramfs always fail with the following error:

  ubuntu@ip-10-18-23-79:~$ sudo update-initramfs -u
  update-initramfs: Generating /boot/initrd.img-5.4.0-1011-aws
  E: /usr/share/initramfs-tools/hooks/btrfs failed with return 1.
  update-initramfs: failed for /boot/initrd.img-5.4.0-1011-aws with 1.

  ## Steps to reproduce (on AWS)

  ### With focal 20200423 AMI

  1. Find the following AMI and launch on m6g instance family

     ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200423

  2. Run: sudo apt update && sudo apt install libc6-lse
  3. Try: sudo update-initramfs -u

  ### With focal 20200522 AMI

  1. Find the following AMI and launch on m6g instance family

     ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200522

  2. Try: sudo update-initramfs -u

  ## Note

  - The entire log of the above steps performed on 20200423 AMI is attached.
  - Latest cloud-image AMI 
"ubuntu/images/hvm-ssd/ubuntu-focal-20.04-arm64-server-20200522" includes 
libc6-lse. On 20200522 AMI, this doesn't reproduce after removing libc6-lse 
manually.
  - This doesn't reproduce on EC2 a1.* instance family.

  ## Expected behavior

  Does not fail.

  ## Background to find this bug

  As the 20200522 AMI includes libc6-lse out-of-the-box & apt-get
  upgrade pulls newer package that triggers update-initramfs, apt-get
  upgrade always fail on 20200522 AMI.

  the following is an apport report on 20200423 AMI:

  

  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: arm64
  CasperMD5CheckResult: skip
  Date: Wed May 27 09:52:16 2020
  Dependencies:
   gcc-10-base 10-20200411-0ubuntu1
   libc6 2.31-0ubuntu9
   libcrypt1 1:4.4.10-10ubuntu4
   libgcc-s1 10-20200411-0ubuntu1
   libidn2-0 2.2.0-2
   libunistring2 0.9.10-2
  DistroRelease: Ubuntu 20.04
  Ec2AMI: ami-061102f51d47b1c24
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: ap-northeast-1c
  Ec2InstanceType: m6g.medium
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  Package: libc6-lse 2.31-0ubuntu9
  PackageArchitecture: arm64
  ProcCpuinfoMinimal:
   processor  : 0
   BogoMIPS   : 243.75
   Features   : fp asimd evtstrm aes pmull sha1 sha2 crc32 atomics fphp 
asimdhp cpuid asimdrdm lrcpc dcpop asimddp ssbs
   CPU implementer: 0x41
   CPU architecture: 8
   CPU variant: 0x3
   CPU part   : 0xd0c
   CPU revision   : 1
  ProcEnviron:
   LANG=C.UTF-8
   TERM=screen-256color
   PATH=(custom, no user)
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.4.0-1009.9-aws 5.4.30
  SourcePackage: glibc
  Tags:  focal ec2-images
  Uname: Linux 5.4.0-1009-aws aarch64
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-images/+bug/1880853/+subscriptions

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

[Touch-packages] [Bug 1879525] Update Released

2020-06-15 Thread Brian Murray
The verification of the Stable Release Update for busybox has completed
successfully and the package is now being 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 busybox in Ubuntu.
https://bugs.launchpad.net/bugs/1879525

Title:
  Add TLS support

Status in busybox package in Ubuntu:
  Fix Released
Status in busybox source package in Focal:
  Fix Released

Bug description:
  [Impact]

   * busybox in the initramfs provides wget applet that is used by casper for 
netboot support
   * It does not support https at the moment, but it is desirable that it does
   * There is built-in TLS code, or "fork & execute openssl"
   * Enable the later one, and optionally include /usr/bin/openssl & certs, 
when building casper-like initrds which should support netboot.

  [Test Case]

   * Boot casper created initrd, with break=bottom
   * Configure dhcp based networking
   * Attempt to wget https://start.ubuntu.com/connectivity-check
   * It should succeed

  [Regression Potential]

   * The openssl codepath is optional in busybox wget, and we only include 
openssl & certs for casper.
   * The casper based initrd will grow in size, due to inclusion of openssl & 
certs

  [Other Info]
   
   * Parity with d-i, which includes https support already

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1879525/+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 1879525] Re: Add TLS support

2020-06-15 Thread Launchpad Bug Tracker
This bug was fixed in the package busybox - 1:1.30.1-4ubuntu6.1

---
busybox (1:1.30.1-4ubuntu6.1) focal; urgency=medium

  * Enable TLS verification with OpenSSL. LP: #1879533
  * Enable TLS in initramfs flavour of wget applet, requires openssl. LP:
#1879525

 -- Dimitri John Ledkov   Tue, 19 May 2020 16:16:23
+0100

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

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

Title:
  Add TLS support

Status in busybox package in Ubuntu:
  Fix Released
Status in busybox source package in Focal:
  Fix Released

Bug description:
  [Impact]

   * busybox in the initramfs provides wget applet that is used by casper for 
netboot support
   * It does not support https at the moment, but it is desirable that it does
   * There is built-in TLS code, or "fork & execute openssl"
   * Enable the later one, and optionally include /usr/bin/openssl & certs, 
when building casper-like initrds which should support netboot.

  [Test Case]

   * Boot casper created initrd, with break=bottom
   * Configure dhcp based networking
   * Attempt to wget https://start.ubuntu.com/connectivity-check
   * It should succeed

  [Regression Potential]

   * The openssl codepath is optional in busybox wget, and we only include 
openssl & certs for casper.
   * The casper based initrd will grow in size, due to inclusion of openssl & 
certs

  [Other Info]
   
   * Parity with d-i, which includes https support already

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

2020-06-15 Thread Brian Murray
The verification of the Stable Release Update for busybox has completed
successfully and the package is now being 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 busybox in Ubuntu.
https://bugs.launchpad.net/bugs/1879533

Title:
  busybox does not verify TLS connections with
  CONFIG_FEATURE_WGET_OPENSSL=y and CONFIG_FEATURE_WGET_HTTPS unset, and
  doesn't warn either about it

Status in busybox package in Ubuntu:
  Fix Released
Status in busybox source package in Focal:
  Fix Released
Status in busybox source package in Groovy:
  Fix Released

Bug description:
  [Impact]

   * CONFIG_FEATURE_WGET_OPENSSL=y enables https support in wget busybox
  applet using openssl

   * CONFIG_FEATURE_WGET_HTTPS=y enables https support in wget busybox
  applet using internal TLS code

   * CVE-2018-1000500 ensured that when CONFIG_FEATURE_WGET_HTTPS=y is
  used, a message is printed to notify the users that TLS verification
  is not perfomed.

   * However, when one configures with CONFIG_FEATURE_WGET_OPENSSL=y and
  CONFIG_FEATURE_WGET_HTTPS unset - no such message is printed.

   * Also TLS verification is not performed under OPENSSL case.

   * When performing https requests, it works openssl s_client and communicates 
with it to perform https download
   * Whilst doing so, it does not pass `-verify_return_error` option, meaning 
any verification errors are ignored

   * There is no warning that TLS verification was not performed

  [Test Case]

   * Preparation: sudo apt install busybox; or build busybox with
  CONFIG_FEATURE_WGET_OPENSSL=y

   * Test case: /bin/busybox wget https://untrusted-root.badssl.com/

   * Expected: download failed, or download suceeds with warning printed
  that verification is disabled

   * Observed: download success without a warning that verification is
  disabled.

  $ /bin/busybox wget https://untrusted-root.badssl.com/
  Connecting to untrusted-root.badssl.com (104.154.89.105:443)
  index.html   100% 
|*|
   600  0:00:00 ETA

  $ cat index.html  | grep certificate
    The certificate for this site is signed using an untrusted root.

  [Regression Potential]

   * The fact that /bin/busybox wget https:// succeeds without TLS
  verification might be relied upon. If this issue is fixed, ensure that
  `--no-check-certificate` is honored.

  [Other Info]

   * Proposed fix

     pass `-verify_return_error` to s_client, unless `--no-check-
  certificate` is specified

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1879533/+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 1879533] Re: busybox does not verify TLS connections with CONFIG_FEATURE_WGET_OPENSSL=y and CONFIG_FEATURE_WGET_HTTPS unset, and doesn't warn either about it

2020-06-15 Thread Launchpad Bug Tracker
This bug was fixed in the package busybox - 1:1.30.1-4ubuntu6.1

---
busybox (1:1.30.1-4ubuntu6.1) focal; urgency=medium

  * Enable TLS verification with OpenSSL. LP: #1879533
  * Enable TLS in initramfs flavour of wget applet, requires openssl. LP:
#1879525

 -- Dimitri John Ledkov   Tue, 19 May 2020 16:16:23
+0100

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

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

Title:
  busybox does not verify TLS connections with
  CONFIG_FEATURE_WGET_OPENSSL=y and CONFIG_FEATURE_WGET_HTTPS unset, and
  doesn't warn either about it

Status in busybox package in Ubuntu:
  Fix Released
Status in busybox source package in Focal:
  Fix Released
Status in busybox source package in Groovy:
  Fix Released

Bug description:
  [Impact]

   * CONFIG_FEATURE_WGET_OPENSSL=y enables https support in wget busybox
  applet using openssl

   * CONFIG_FEATURE_WGET_HTTPS=y enables https support in wget busybox
  applet using internal TLS code

   * CVE-2018-1000500 ensured that when CONFIG_FEATURE_WGET_HTTPS=y is
  used, a message is printed to notify the users that TLS verification
  is not perfomed.

   * However, when one configures with CONFIG_FEATURE_WGET_OPENSSL=y and
  CONFIG_FEATURE_WGET_HTTPS unset - no such message is printed.

   * Also TLS verification is not performed under OPENSSL case.

   * When performing https requests, it works openssl s_client and communicates 
with it to perform https download
   * Whilst doing so, it does not pass `-verify_return_error` option, meaning 
any verification errors are ignored

   * There is no warning that TLS verification was not performed

  [Test Case]

   * Preparation: sudo apt install busybox; or build busybox with
  CONFIG_FEATURE_WGET_OPENSSL=y

   * Test case: /bin/busybox wget https://untrusted-root.badssl.com/

   * Expected: download failed, or download suceeds with warning printed
  that verification is disabled

   * Observed: download success without a warning that verification is
  disabled.

  $ /bin/busybox wget https://untrusted-root.badssl.com/
  Connecting to untrusted-root.badssl.com (104.154.89.105:443)
  index.html   100% 
|*|
   600  0:00:00 ETA

  $ cat index.html  | grep certificate
    The certificate for this site is signed using an untrusted root.

  [Regression Potential]

   * The fact that /bin/busybox wget https:// succeeds without TLS
  verification might be relied upon. If this issue is fixed, ensure that
  `--no-check-certificate` is honored.

  [Other Info]

   * Proposed fix

     pass `-verify_return_error` to s_client, unless `--no-check-
  certificate` is specified

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1879533/+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 1881982] Re: Memory leak in parse_report()

2020-06-15 Thread Seong-Joong Kim
This vulnerability may cause a memory exhaustion vulnerability in the
function parse_report() in whoopsie.c, which allows attackers to cause a
denial of service.

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

Title:
  Memory leak in parse_report()

Status in whoopsie package in Ubuntu:
  New

Bug description:
  Hi,

  I have found a security issue on whoopsie 0.2.69 and earlier.

  ## Vulnerability in whoopsie
  - whoopsie 0.2.69 and earlier have a memory leak vulnerability.
  - An attacker can cause a denial of service (application crash) via a crafted 
.crash file.

  ## Basic
  When a program has been crashed, Linux system tries to create a '.crash' file 
on '/var/crash/' directory with python script located in 
'/usr/share/apport/apport'.
  The file contains a series of system crash information including core dump, 
syslog, stack trace, memory map info, etc.
  A user is given read and write permission to the file.
  After then, whoopsie parses key-value pairs in ‘.crash’ file and encodes it 
into binary json (bson) format.
  Lastly, whoopsie forwards the data to a remotely connected Ubuntu error 
report system.

  ## Vulnerability
  We have found a memory leak vulnerability during the parsing the crash file, 
when a collision occurs on GHashTable through g_hash_table_insert().
  According to [1], if the key already exists in the GHashTable, its current 
value is replaced with the new value.
  If 'key_destory_func' and 'value_destroy_func' are supplied when creating the 
table, the old value and the passed key are freed using that function.
  Unfortunately, whoopsie does not handle the old value and the passed key when 
collision happens.
  If a crash file contains same repetitive key-value pairs, it leads to memory 
leak as much as the amount of repetition and results in denial-of-service.

  ## Attack
  1) Create a fake.crash file
  memory_leak_poc.py script measures an available memory and generates a 
malicious crash file that contains same repetitive key-value pairs as much as 
20% of the available memory size; 'ProblemType: Crash'.
  20% indicates arbitrary amount of the memory leakage.
  2) Before the attack, the script checks memory usage of whoopsie process with 
psutil
  3) It triggers the whoopsie to read the fake.crash file
  4) Then, it measures the memory usage of whoopsie process
  5) It results in denial-of-service and then other users can no longer report 
crash to the Ubuntu error report system.

  ## Mitigation
  We should use g_hash_table_new_full() with ‘key_destroy_func’ and 
‘value_destroy_func’ functions instead of g_hash_table_new().
  Otherwise, before g_hash_table_insert(), we should check the collision via 
g_hash_table_lookup_extended() and obtain pointer to the old value and remove 
it.

  Sincerely,

  [1] https://developer.gnome.org/glib/stable/glib-Hash-Tables.html#g
  -hash-table-insert

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1881982/+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 939702] An important information regarding my email address

2020-06-15 Thread Hao HU
Greetings,

I hope this email finds you well.

I am writing to you due to the discovery of several security issues of
the current email address hoping to be able to mitigate the potential
impacts.

In fact, the current email address (hao.hu.up...@gmail.com) has been the
victims of several data leakage on the Internet more than 10 times
during recent years, which includes

Affected ServiceDate   Verified 
Affected users   Password
Combolist   Jan. 2019   
1,247,433,080Affected
Unknown (Collection #1-#5)  Jan. 2019   
2,191,498,885Affected
myfitnesspal.comFeb. 2018   ✓   
143,425,495  Affected
Unknown (Anti-Public Combolist Jan. 2017)   Jan. 2017   
948,385,599  Affected
dailymotion.com Oct. 2016   ✓   
85,174,207
tumblr.com  May. 2013   ✓   
73,358,680   Affected
dropbox.com Sep. 2012   ✓   
68,658,165   Affected
linkedin.comJun. 2012   ✓   
160,144,040  Affected

and some more combo list recently published (less than a year) from unknown 
data sources.
This information could be found out from several websites specialized in the 
information security.

A such kind of data breach risked at disclosing my historical email
contents and contacts, which may have resulted in the followings without
my consent.

- private information used by third party to commit malicious actions
- identity stolen to make unauthorized actions on my behalf
- reaching out my historical contacts for one's own profit or play against 
myself
- other important confidential information disclosed to the third party

As the account itself was created in 2011, which covers a long period of
time and a variety of activities, the impact might be significant and
difficult to assess.

At this time, I would wish that you could revert back to me if any suspicious 
things may have been witnessed and related to me, which may include the things 
that make you feel
- astonished
- wrong
- emotionally negative

Additionally, please kindly update my contact email address to the
following new one in your contact list:

hao.hu...@gmail.com

Thank you very much,

Kind regards,

Hao Hu

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

Title:
  crashes due to API mismatch between apport-{kde,gtk} and python-apport

Status in apport package in Ubuntu:
  Fix Released

Bug description:
  I have installed Kubuntu after I have installed normal ubuntu

  ProblemType: Crash
  DistroRelease: Ubuntu 12.04
  Package: apport-kde 1.92-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-15.24-generic 3.2.5
  Uname: Linux 3.2.0-15-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 1.92-0ubuntu1
  Architecture: amd64
  Date: Thu Feb 23 16:13:45 2012
  ExecutablePath: /usr/share/apport/apport-kde
  ExecutableTimestamp: 1329752547
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 
(20120211)
  InterpreterPath: /usr/bin/python2.7
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python /usr/share/apport/apport-kde
  ProcCwd: /home/pptime/文档
  ProcEnviron:
   LANGUAGE=zh_CN:
   PATH=(custom, no user)
   LANG=zh_CN.UTF-8
   SHELL=/bin/bash
  PythonArgs: ['/usr/share/apport/apport-kde']
  SourcePackage: apport
  Title: apport-kde crashed with NotImplementedError in ui_present_crash(): 
this function must be overridden by subclasses
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/939702/+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 1883608] [NEW] [USB-Audio - UMC204HD 192k, playback] Playback problem

2020-06-15 Thread Angus
Public bug reported:

I want to split the 4.0 output into 2x2.0 outputs. This is my config for
/etc/pulse/default.pa

load-module module-remap-sink sink_name=behringera 
sink_properties="device.description='Behringer Output A (1 and 2)'" remix=no 
master=alsa_output.usb-BEHRINGER_UMC204HD_192k-00.analog-surround-40 channels=2 
master_channel_map=front-left,front-right channel_map=left,right
load-module module-remap-sink sink_name=behringerb 
sink_properties="device.description='Behringer Output B (3 and 4)'" remix=no 
master=alsa_output.usb-BEHRINGER_UMC204HD_192k-00.analog-surround-40 channels=2 
master_channel_map=rear-left,rear-right channel_map=left,right

I have tested this config on Ubuntu 18.04, Debian, Fedora 30, it works
on all of them. But does not work on Ubuntu 20.04, nor Fedora 32. Both
20.04 and f32 use version 13.99.1 of Pulseaudio, so I suspect the
problem to be with this version.

When I speak about A and B, I am referring to the device description
given in the 2 lines above, line 1 being A and line 2 being B.

What is happening on 20.04 and f32 is if I comment out A, then B will
work. If I comment out B, A will work, but both A and B are defined,
then only A will work. If B is defined first, and then A, something else
weird happens where A will work, but is sent out through B, and B will
work as expected.

A discussion on Reddit, another user has version 13.0 on NixOS and his
similar UMC404HD works fine. Here is a link to the info on Reddit:
https://www.reddit.com/r/linuxaudio/comments/fqmhbe/pulseaudio_and_multichannel_interfaces/ftkq7ov

I know this is probably a pulseaudio bug, but I could not figure out how
to submit a bug report to them.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  angus  5429 F pulseaudio
 /dev/snd/pcmC0D0p:   angus  5429 F...m pulseaudio
 /dev/snd/controlC3:  angus  5429 F pulseaudio
 /dev/snd/controlC2:  angus  5429 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Mon Jun 15 23:14:49 2020
InstallationDate: Installed on 2020-04-25 (51 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:U192k successful
Symptom_Card: Family 17h (Models 00h-0fh) HD Audio Controller - HD-Audio Generic
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: None of the above
Title: [USB-Audio - UMC204HD 192k, playback] Playback problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/21/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.H0
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: X370 KRAIT GAMING (MS-7A33)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.H0:bd01/21/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A33:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnX370KRAITGAMING(MS-7A33):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7A33
dmi.product.sku: To be filled by O.E.M.
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.

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


** Tags: amd64 apport-bug focal

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

Title:
  [USB-Audio - UMC204HD 192k, playback] Playback problem

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I want to split the 4.0 output into 2x2.0 outputs. This is my config
  for /etc/pulse/default.pa

  load-module module-remap-sink sink_name=behringera 
sink_properties="device.description='Behringer Output A (1 and 2)'" remix=no 
master=alsa_output.usb-BEHRINGER_UMC204HD_192k-00.analog-surround-40 channels=2 
master_channel_map=front-left,front-right channel_map=left,right
  load-module module-remap-sink sink_name=behringerb 
sink_properties="device.description='Behringer Output B (3 and 4)'" remix=no 
master=alsa_output.usb-BEHRINGER_UMC204HD_192k-00.analog-surround-40 channels=2 
master_channel_map=rear-left,rear-right channel_map=left,right

  I have tested this config on Ubuntu 18.04, Debian, Fedora 30, it works
  on all of them. But does not work on Ubuntu 20.04, nor Fedora 32. Both
  20.04 and f32 use version 

[Touch-packages] [Bug 1854403] Re: Need updated libimobiledevice and dependencies to access iOS 13 devices

2020-06-15 Thread Sebastien Bacher
Unsure if we want to switch to openssl, that would be a request to make
to Debian. There might have been a (license) reason to prefer gnutls
there

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

Title:
  Need updated libimobiledevice and dependencies to access iOS 13
  devices

Status in libimobiledevice package in Ubuntu:
  Incomplete
Status in libplist package in Ubuntu:
  Confirmed
Status in libusbmuxd package in Ubuntu:
  Confirmed
Status in usbmuxd package in Ubuntu:
  Confirmed

Bug description:
  iOS 13 devices require updated libimobiledevice, libusbmuxd and
  usbmuxd to work correctly. Without the updates, the device appears to
  be accessible but it's impossible to copy files to the devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1854403/+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 1883306] Re: package libjpeg-turbo8 2.0.3-0ubuntu1 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2

2020-06-15 Thread Sebastien Bacher
Thank you for your bug report, that seems rather a local corruption than
a bug though, closing

** Changed in: libjpeg-turbo (Ubuntu)
   Status: New => Invalid

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

Title:
  package libjpeg-turbo8 2.0.3-0ubuntu1 failed to install/upgrade: dpkg-
  deb --control subprocess returned error exit status 2

Status in libjpeg-turbo package in Ubuntu:
  Invalid

Bug description:
  Pl check, what is problem?

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libjpeg-turbo8 2.0.3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Fri Jun 12 10:19:54 2020
  DuplicateSignature:
   package:libjpeg-turbo8:2.0.3-0ubuntu1
   Unpacking libwinpr2-2:amd64 (2.1.1+dfsg1-0ubuntu0.20.04.1) over 
(2.0.0~git20190204.1.2693389a+dfsg1-2build2) ...
   dpkg-deb: error: 
'/tmp/apt-dpkg-install-E982TC/145-libfreerdp2-2_2.1.1+dfsg1-0ubuntu0.20.04.1_amd64.deb'
 is not a Debian format archive
   dpkg: error processing archive 
/tmp/apt-dpkg-install-E982TC/145-libfreerdp2-2_2.1.1+dfsg1-0ubuntu0.20.04.1_amd64.deb
 (--unpack):
dpkg-deb --control subprocess returned error exit status 2
  ErrorMessage: dpkg-deb --control subprocess returned error exit status 2
  InstallationDate: Installed on 2020-06-12 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: libjpeg-turbo
  Title: package libjpeg-turbo8 2.0.3-0ubuntu1 failed to install/upgrade: 
dpkg-deb --control subprocess returned error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1883306/+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 1834566] Re: Samsung Notebook 9 Pro - Internal Speaker Playback problem - HDA Intel - Realtek ALC298

2020-06-15 Thread Sebastien Bacher
** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu)

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

Title:
  Samsung Notebook 9 Pro - Internal Speaker Playback problem - HDA Intel
  - Realtek ALC298

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Unable to get system speakers working running 19.04.  At max volume,
  sound is barely perceptible through headphones.  Pavucontrol shows
  sounds is present, but no amount of adjustments makes a difference.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  robert 3355 F pulseaudio
  CurrentDesktop: KDE
  Date: Fri Jun 28 00:44:13 2019
  InstallationDate: Installed on 2019-06-05 (22 days ago)
  InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: None of the above
  Title: [930MBE, Intel Kabylake HDMI, Digital Out, HDMI] Playback problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/25/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02AHK.029.190425.PS
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP930MBE-K04US
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGL9872A0S-C01-G001-S0001+10.0.17763
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02AHK.029.190425.PS:bd04/25/2019:svnSAMSUNGELECTRONICSCO.,LTD.:pn930MBE:pvrP02AHK:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP930MBE-K04US:rvrSGL9872A0S-C01-G001-S0001+10.0.17763:cvnSAMSUNGELECTRONICSCO.,LTD.:ct31:cvrN/A:
  dmi.product.family: Notebook 9 Series
  dmi.product.name: 930MBE
  dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PAHK
  dmi.product.version: P02AHK
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834566/+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 1877590] Re: SRU the current 3.24.20 stable update

2020-06-15 Thread Sebastien Bacher
The autopkgtest error was a flacky builder and it worked after a retry

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

Title:
  SRU the current 3.24.20 stable update

Status in gtk+3.0 package in Ubuntu:
  Fix Committed
Status in gtk+3.0 source package in Focal:
  Fix Committed

Bug description:
  * Impact
  That's the current GNOME stable update, including some fixes and translation 
updates
  https://gitlab.gnome.org/GNOME/gtk/-/blob/gtk-3-24/NEWS

  * Test case

  The update is part of GNOME stable updates
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Check that GNOME Desktop and GTK software still work correctly

  * Regression potential

  The update has some fixes in the filechooser and the emoji picker,
  test those

  Check also that GUI elements in Adwaita and Yaru still look correct

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1877590/+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 1868520] Re: Wayland apps fail to run with zwp_linux_dmabuf error (failed to import supplied dmabufs: Unsupported buffer format 808669784 [DRM_FORMAT_XRGB2101010]) (or 808665665

2020-06-15 Thread Christian Rauch
Thanks @tjaalton. I see from https://launchpad.net/ubuntu/+source/mesa
that version 20.0.8-0ubuntu1 made it into Groovy proposed.

Is there a chance this will also make it into focal-proposed so that it
can be tested on the current LTS? Or do we have to wait until this gets
merged into groovy?

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

Title:
  Wayland apps fail to run with zwp_linux_dmabuf error (failed to import
  supplied dmabufs: Unsupported buffer format 808669784
  [DRM_FORMAT_XRGB2101010]) (or 808665665 [DRM_FORMAT_ABGR2101010])

Status in Mesa:
  Fix Released
Status in MPV:
  Unknown
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Focal:
  Confirmed

Bug description:
  [Impact]

  Wayland apps fail to start in focal with:

  error 7: failed to import supplied dmabufs: Unsupported buffer format
  808669784

  [Test Case]

  Just run: es2gears_wayland

  [Regression Potential]

  Medium/unknown. The fix is quite new.

  [Other Info]

  When attempting to run es2gears_wayland against GNOME Shell, it fails
  with:

  EGL_VERSION = 1.5
  vertex shader info:
  fragment shader info:
  info:
  [destroyed object]: error 7: failed to import supplied dmabufs: Unsupported 
buffer format 808669784

  The full wayland protocol trace is:

  [3104432.914]  -> wl_display@1.get_registry(new id wl_registry@2)
  [3104432.972]  -> wl_disp...@1.sync(new id wl_callback@3)
  [3104433.139] wl_display@1.delete_id(3)
  [3104433.175] wl_registry@2.global(1, "wl_drm", 2)
  [3104433.207] wl_registry@2.global(2, "wl_compositor", 4)
  [3104433.240]  -> wl_regis...@2.bind(2, "wl_compositor", 1, new id 
[unknown]@4)
  [3104433.285] wl_registry@2.global(3, "wl_shm", 1)
  [3104433.316] wl_registry@2.global(4, "wl_output", 2)
  [3104433.347] wl_registry@2.global(5, "zxdg_output_manager_v1", 3)
  [3104433.376] wl_registry@2.global(6, "wl_data_device_manager", 3)
  [3104433.404] wl_registry@2.global(7, "gtk_primary_selection_device_manager", 
1)
  [3104433.432] wl_registry@2.global(8, "wl_subcompositor", 1)
  [3104433.459] wl_registry@2.global(9, "xdg_wm_base", 2)
  [3104433.485] wl_registry@2.global(10, "zxdg_shell_v6", 1)
  [3104433.513] wl_registry@2.global(11, "wl_shell", 1)
  [3104433.542]  -> wl_regis...@2.bind(11, "wl_shell", 1, new id [unknown]@5)
  [3104433.582] wl_registry@2.global(12, "gtk_shell1", 3)
  [3104433.611] wl_registry@2.global(13, "wp_viewporter", 1)
  [3104433.640] wl_registry@2.global(14, "zwp_pointer_gestures_v1", 1)
  [3104433.670] wl_registry@2.global(15, "zwp_tablet_manager_v2", 1)
  [3104433.699] wl_registry@2.global(16, "wl_seat", 5)
  [3104433.728] wl_registry@2.global(17, "zwp_relative_pointer_manager_v1", 1)
  [3104433.758] wl_registry@2.global(18, "zwp_pointer_constraints_v1", 1)
  [3104433.787] wl_registry@2.global(19, "zxdg_exporter_v1", 1)
  [3104433.816] wl_registry@2.global(20, "zxdg_importer_v1", 1)
  [3104433.846] wl_registry@2.global(21, "zwp_linux_dmabuf_v1", 3)
  [3104433.875] wl_registry@2.global(22, 
"zwp_keyboard_shortcuts_inhibit_manager_v1", 1)
  [3104433.904] wl_registry@2.global(23, "zwp_text_input_manager_v3", 1)
  [3104433.933] wl_registry@2.global(24, "gtk_text_input_manager", 1)
  [3104433.960] wl_registry@2.global(26, "wl_eglstream_controller", 1)
  [3104433.991] wl_callb...@3.done(3421)
  [3104436.266]  -> wl_display@1.get_registry(new id wl_registry@3)
  [3104436.279]  -> wl_disp...@1.sync(new id wl_callback@6)
  [3104436.647] wl_display@1.delete_id(6)
  [3104436.672] wl_registry@3.global(1, "wl_drm", 2)
  [3104436.726]  -> wl_regis...@3.bind(1, "wl_drm", 2, new id [unknown]@7)
  [3104436.744] wl_registry@3.global(2, "wl_compositor", 4)
  [3104436.780] wl_registry@3.global(3, "wl_shm", 1)
  [3104436.790] wl_registry@3.global(4, "wl_output", 2)
  [3104436.803] wl_registry@3.global(5, "zxdg_output_manager_v1", 3)
  [3104436.833] wl_registry@3.global(6, "wl_data_device_manager", 3)
  [3104436.868] wl_registry@3.global(7, "gtk_primary_selection_device_manager", 
1)
  [3104436.882] wl_registry@3.global(8, "wl_subcompositor", 1)
  [3104436.898] wl_registry@3.global(9, "xdg_wm_base", 2)
  [3104436.913] wl_registry@3.global(10, "zxdg_shell_v6", 1)
  [3104436.925] wl_registry@3.global(11, "wl_shell", 1)
  [3104436.937] wl_registry@3.global(12, "gtk_shell1", 3)
  [3104436.950] wl_registry@3.global(13, "wp_viewporter", 1)
  [3104436.963] wl_registry@3.global(14, "zwp_pointer_gestures_v1", 1)
  [3104436.976] wl_registry@3.global(15, "zwp_tablet_manager_v2", 1)
  [3104436.990] wl_registry@3.global(16, "wl_seat", 5)
  [3104437.001] wl_registry@3.global(17, "zwp_relative_pointer_manager_v1", 1)
  [3104437.013] wl_registry@3.global(18, "zwp_pointer_constraints_v1", 1)
  [3104437.026] wl_registry@3.global(19, "zxdg_exporter_v1", 1)
  [3104437.038] wl_registry@3.global(20, "zxdg_importer_v1", 1)
  [3104437.051] 

[Touch-packages] [Bug 1559650] Re: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk()

2020-06-15 Thread Iain Lane
I've sponsored the debdiff to bionic's queue

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

Title:
  gnome-shell crashed with SIGSEGV in ___vsnprintf_chk()

Status in libxau package in Ubuntu:
  Fix Released
Status in libxau source package in Bionic:
  In Progress
Status in libxau source package in Eoan:
  Fix Released
Status in libxau source package in Focal:
  Fix Released

Bug description:
  [Impact]

  gnome-shell crashes a lot. Over 38000 times in bionic so far:
  https://errors.ubuntu.com/problem/00455200cd9fb890dacfe09b92c7bda2f6ad3af7

  [Test Case]

  None known yet. Just keeping an eye on the above link for regressions.

  [Regression Potential]

  Low. The same fix has been released to newer distros for the past 2
  years already.

  [Other Info]

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: gnome-shell 3.18.4-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-14.30-generic 4.4.5
  Uname: Linux 4.4.0-13-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Wed Mar 16 17:15:11 2016
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  GsettingsChanges:

  InstallationDate: Installed on 2016-03-13 (6 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Alpha amd64 
(20160311)
  ProcCmdline: gnome-shell --mode=gdm --wayland --display-server
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0x7f1ff33f46ab <___vsnprintf_chk+107>: movb   
$0x0,(%r12)
   PC (0x7f1ff33f46ab) ok
   source "$0x0" ok
   destination "(%r12)" (0x) not located in a known VMA region (needed 
writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: gnome-shell
  StacktraceTop:
   ___vsnprintf_chk (s=0x0, maxlen=, flags=1, slen=, format=0x7f1fe54ccae5 "%s%s", args=args@entry=0x7f1fce502da8) at 
vsnprintf_chk.c:55
   ___snprintf_chk (s=, maxlen=, flags=, slen=, format=) at snprintf_chk.c:34
   XauFileName () from /usr/lib/x86_64-linux-gnu/libXau.so.6
   XauGetBestAuthByAddr () from /usr/lib/x86_64-linux-gnu/libXau.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libxcb.so.1
  Title: gnome-shell crashed with SIGSEGV in ___vsnprintf_chk()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxau/+bug/1559650/+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 1883580] [NEW] frame drop issue

2020-06-15 Thread shahin honarmand
Public bug reported:

i have severe graphical drop frames however my hardware is nvidia gtx
850 4 gigs and intel graphic card

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
Uname: Linux 5.4.0-37-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
 GCC version:
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
CasperMD5CheckResult: skip
CompositorRunning: None
Date: Mon Jun 15 21:30:09 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated Graphics 
Controller [1043:11cd]
   Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:11cd]
InstallationDate: Installed on 2020-06-10 (5 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: ASUSTeK COMPUTER INC. N550JK
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=ebd465fe-6414-4b7d-a0c0-ec4fdbd2aaa5 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/23/2014
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: N550JK.204
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: N550JK
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.:bvrN550JK.204:bd01/23/2014:svnASUSTeKCOMPUTERINC.:pnN550JK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN550JK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: N
dmi.product.name: N550JK
dmi.product.sku: ASUS-NotebookSKU
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu

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

Title:
  frame drop issue

Status in xorg package in Ubuntu:
  New

Bug description:
  i have severe graphical drop frames however my hardware is nvidia gtx
  850 4 gigs and intel graphic card

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.64  Fri Feb 21 01:17:26 
UTC 2020
   GCC version:
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Mon Jun 15 21:30:09 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 4th Gen Core Processor Integrated 
Graphics Controller [1043:11cd]
 Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 850M] [1043:11cd]
  InstallationDate: Installed on 2020-06-10 (5 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: ASUSTeK COMPUTER INC. N550JK
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 

[Touch-packages] [Bug 1222356] Re: WARNING: Couldn't register with accessibility bus: Did not receive a reply.

2020-06-15 Thread ^rooker
I know this thread is ancient and marked as fixed, but I just ran into
the exact same error message on a recently installed Xubuntu 18.04.4,
opening Thunderbird (1:68.8.0+build2-0ubuntu0.18.04.2) after resuming
from suspend:

Quote from "~/.xsession-errors":

```
(nm-applet:26135): Gtk-WARNING **: 18:53:46.496: Can't set a parent on widget 
which has a parent

(wrapper-1.0:26197): GLib-CRITICAL **: 18:53:57.168: Source ID 174 was not 
found when attempting to remove it
Gtk-Message: 18:55:17.424: GtkDialog mapped without a transient parent. This is 
discouraged.

(exo-open:329): dbind-WARNING **: 18:55:21.445: Couldn't register with
accessibility bus: Did not receive a reply. Possible causes include: the
remote application did not send a reply, the message bus security policy
blocked the reply, the reply timeout expired, or the network connection
was broken.

(exo-helper-1:331): dbind-WARNING **: 18:55:21.459: Couldn't register with 
accessibility bus: Did not receive a reply. Possible causes include: the remote 
application did not send a reply, the message bus security policy blocked the 
reply, the reply timeout expired, or the network connection was broken.
JavaScript error: chrome://coloredfolders/content/coloredfolders.js, line 118: 
TypeError: elm is null
```

I haven't done anything fancy on this system that I'm aware of, so
someone else might also get this warning message on a recent setup?

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

Title:
  WARNING: Couldn't register with accessibility bus: Did not receive a
  reply.

Status in at-spi2-core package in Ubuntu:
  Fix Released
Status in at-spi2-core package in Debian:
  Fix Released

Bug description:
  The following warnings/errors appear after calling ubuntu-bug

  ** (apport-gtk:3020): WARNING **: Couldn't register with accessibility
  bus: Did not receive a reply. Possible causes include: the remote
  application did not send a reply, the message bus security policy
  blocked the reply, the reply timeout expired, or the network
  connection was broken.

  (process:4192): GLib-CRITICAL **: g_slice_set_config: assertion
  'sys_page_size == 0' failed

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: apport-gtk 2.12.1-0ubuntu3
  ProcVersionSignature: Ubuntu 3.11.0-4.9-generic 3.11.0-rc7
  Uname: Linux 3.11.0-4-generic x86_64
  ApportVersion: 2.12.1-0ubuntu3
  Architecture: amd64
  Date: Sun Sep  8 10:54:01 2013
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-09-01 (371 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to saucy on 2013-09-05 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1222356/+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 1883338] Re: unattended-upgrades blocks apt

2020-06-15 Thread ssducf
Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend),
is another process using it?

I run fuser /var/lib/dpkg  and the pid that shows up is unattended-
upgrades which is chewing cpu.

If I run ps -ef | grep dpkg
nothing is running.   I don't know what unattended-upgrades is doing other than 
blocking me from running apt full-upgrade, but it's not actually running 
updates.   If I kill it, it just restarts.  I have to kill it and immediately 
start apt full-upgrade or wait an extended period of time for 
unattended-upgrades to let go.

I can't replicate the problem at this time because I've now manually run all 
the updates.
I'm not really interested in whatever slowness is in unattended-upgrades, I 
just want it to abort when I run apt if it isn't actually actively installing 
something.

unattended-upgrades should be communicating and coordinating with apt,
not blocking it unconditionally.

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

Title:
  unattended-upgrades blocks apt

Status in unattended-upgrades package in Ubuntu:
  Incomplete

Bug description:
  Version: Ubuntu 18.04 and all prior versions that include unattended-
  upgrades

  Buggy behavior:

  I boot a laptop that has been off for a while with the intent to install 
linux updates.
  I type apt-get update; apt full-upgrade  and it fails, finding that 
unattended upgrades is running in the background for an extended period of 
time, but not actually running dpkg at all, just holding the lock, preventing 
me from running updates.

  
  Expected behavior:

  apt full-upgrade, the graphical update manager, and related commands
  should either

  1) Immediately (and silently?) abort whatever unattended-upgrades is
  doing and proceed with running updates in the foreground

  2) Display progress of updates currently running in the background,
  waiting for them to finish, and then proceed with running additional
  updates in the foreground

  Note that it may be necessary to implement both behaviors, depending
  if unattended-upgrades is just spinning or if it has actually started
  running upgrades.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1883338/+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 1880968] Re: fixrtc fails due to bad format of input to the date command

2020-06-15 Thread Launchpad Bug Tracker
This bug was fixed in the package initramfs-tools - 0.137ubuntu10

---
initramfs-tools (0.137ubuntu10) groovy; urgency=medium

  * Trim leading whitespaces in dumpe2fs output so date command
is happy in the fixrtc script (LP: #1880968)

 -- Alfonso Sanchez-Beato (email Canonical)   Wed, 27 May 2020 16:52:16 +0200

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Fix Released

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

Title:
  fixrtc fails due to bad format of input to the date command

Status in initramfs-tools package in Ubuntu:
  Fix Released

Bug description:
  The fixrtc script is failing with message:

  date: invalid date '  Wed Apr  1 17:23:44 2020'

  when calling the date command. It looks like it does not like the
  leading spaces for the input date. The date is taken from 'dumpe2fs
  -h' ouptput, and some clean-up on it happens, but it looks like it is
  not enough for BusyBox' date command, at least for the version in
  focal.

  Backporting this to focal is needed.

  [Impact]

  The system date shown on first boot is incorrect, which can be
  problematic on first boot if at that point in time there is no network
  connection. If fixrtc works correctly at least we get the date of the
  last time the rootfs was mounted, which is modern enough to avoid
  problems with snap assertions validation, etc.

  [Test case]

  Boot an image with fixrtc in the kernel command line in a system with
  no network. snap seeding will fail without the patch.

  [Regression Potential]

  Quite small, as the fix is small and targeted.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1880968/+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 1882415] Re: Graphical artifact in top-right corner, owned by ibus-ui-gtk3

2020-06-15 Thread Gunnar Hjalmarsson
@vasdi: Thanks. Then, as an experiment, can you please open Language
Support, select "none" as the "Keyboard input method system" instead if
"IBus", and reboot. That will make fewer of those variables being set -
most importantly GTK_IM_MODULE will be unset - which makes GNOME handle
IBus slightly different behind the scenes.

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

Title:
  Graphical artifact in top-right corner, owned by ibus-ui-gtk3

Status in gnome-shell package in Ubuntu:
  New
Status in ibus package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04, Gnome 3.36.2, Nvidia

  Small gray line in top-right corner.
  More precisely, it happens to be in the corner in 1920x1080 resolution. Not 
present in smaller resolutions. In panning mode it's fixed to panel, not screen.
  Present on the panel and on fullscreen windows but not in overview.
  Not clickable (prevents me from clicking button underneath it).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2014-11-12 (2037 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-37.41-lowlatency 5.4.41
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  Tags:  focal
  Uname: Linux 5.4.0-37-lowlatency x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-01 (40 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882415/+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 1557157] Re: apparmor profile denied for saslauthd: /run/saslauthd/mux

2020-06-15 Thread Sergio Durigan Junior
** Description changed:

+ [Impact]
+ 
+ When using openldap with sasl authentication, the slapd process will
+ communicate with the saslauthd daemon via a socket in
+ {,/var}/run/saslauthd/mux. Unfortunately, this will fail in every Ubuntu
+ release from trusty onwards, because slapd's apparmor profile doesn't
+ contain the necessary directive to allow it to read/write from/to the
+ socket specified above.
+ 
+ The fix is simple: just add the necessary directive to allow slapd to
+ read/write from/to the saslauthd socket.
+ 
+ [Test Case]
+ 
+ One can reproduce the problem by doing:
+ 
+ $ lxc launch ubuntu-daily:groovy openldap-bugbug1557157-groovy
+ $ lxc shell openldap-bugbug1557157-groovy
+ # apt install slapd sasl2-bin ldap-utils apparmor-utils
+ 
+ (As the domain name, use "example.com").
+ 
+ # sed -i -e 's/^START=.*/START=yes/' /etc/default/saslauthd
+ # cat > /etc/ldap/sasl2/slapd.conf << __EOF__
+ mech_list: PLAIN
+ pwcheck_method: saslauthd
+ __EOF__
+ # adduser openldap sasl
+ # aa-enforce /etc/apparmor.d/usr.sbin.slapd
+ # systemctl restart slapd.service
+ # systemctl restart saslauthd.service
+ # passwd root
+ 
+ (You can choose any password here. You will need to type it when running
+ the next command.)
+ 
+ # ldapsearch -H ldapi:/// -LLL -b 'dc=example,dc=com' -s base -U root -Y
+ PLAIN
+ 
+ The command will fail with something like:
+ 
+ ldap_sasl_interactive_bind_s: Other (e.g., implementation specific) error (80)
+ additional info: SASL(-1): generic failure: Password verification 
failed
+ 
+ [Regression Potential]
+ 
+ This is an extremely simple and well contained fix, so I don't envision
+ any possible regressions after applying it.  It is important noticing
+ that, since the problem affects older Ubuntu releases, the openldap
+ package will have to be rebuilt against possible newer versions of
+ libraries and other depencencies, which, albeit unlikely, may cause
+ issues.
+ 
+ [Original Description]
+ 
  When using slapd with saslauthd the processes communicate via the
  {,/var}/run/saslauthd/mux socket (this is the default location for the
  saslauthd server from the sasl2-bin package in the
  /etc/default/saslauthd config), but the apparmor profile for
  usr.sbin.slapd does not allow access to this socket/file.
  
  Syslog message:
  apparmor="DENIED" operation="connect" profile="/usr/sbin/slapd" 
name="/run/saslauthd/mux" pid=1880
  4 comm="slapd" requested_mask="r" denied_mask="r" fsuid=108 ouid=0
  
- 
  Please add the following line to  /etc/apparmor.d/usr.sbin.slapd:
  /{,var/}run/saslauthd/mux rw,
  
- 
  Ubuntu version: Ubuntu 14.04.4 LTS
  slapd version: 2.4.31-1+nmu2ubu

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

Title:
  apparmor profile denied for saslauthd: /run/saslauthd/mux

Status in openldap package in Ubuntu:
  Confirmed
Status in openldap source package in Trusty:
  Confirmed
Status in openldap source package in Xenial:
  Confirmed
Status in openldap source package in Bionic:
  Confirmed
Status in openldap source package in Focal:
  Confirmed
Status in openldap source package in Groovy:
  Confirmed

Bug description:
  [Impact]

  When using openldap with sasl authentication, the slapd process will
  communicate with the saslauthd daemon via a socket in
  {,/var}/run/saslauthd/mux. Unfortunately, this will fail in every
  Ubuntu release from trusty onwards, because slapd's apparmor profile
  doesn't contain the necessary directive to allow it to read/write
  from/to the socket specified above.

  The fix is simple: just add the necessary directive to allow slapd to
  read/write from/to the saslauthd socket.

  [Test Case]

  One can reproduce the problem by doing:

  $ lxc launch ubuntu-daily:groovy openldap-bugbug1557157-groovy
  $ lxc shell openldap-bugbug1557157-groovy
  # apt install slapd sasl2-bin ldap-utils apparmor-utils

  (As the domain name, use "example.com").

  # sed -i -e 's/^START=.*/START=yes/' /etc/default/saslauthd
  # cat > /etc/ldap/sasl2/slapd.conf << __EOF__
  mech_list: PLAIN
  pwcheck_method: saslauthd
  __EOF__
  # adduser openldap sasl
  # aa-enforce /etc/apparmor.d/usr.sbin.slapd
  # systemctl restart slapd.service
  # systemctl restart saslauthd.service
  # passwd root

  (You can choose any password here. You will need to type it when
  running the next command.)

  # ldapsearch -H ldapi:/// -LLL -b 'dc=example,dc=com' -s base -U root
  -Y PLAIN

  The command will fail with something like:

  ldap_sasl_interactive_bind_s: Other (e.g., implementation specific) error (80)
  additional info: SASL(-1): generic failure: Password verification 
failed

  [Regression Potential]

  This is an extremely simple and well contained fix, so I don't
  envision any possible regressions after applying it.  It is important
  noticing that, since the problem affects older Ubuntu releases, the
  

[Touch-packages] [Bug 1854403] Re: Need updated libimobiledevice and dependencies to access iOS 13 devices

2020-06-15 Thread Philip Langdale
Upstream fix for the openssl issue is in: f56a65f in libimobiledevice.

Taking advantage of that requires switching the ubuntu build from using
gnutls to openssl.

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

Title:
  Need updated libimobiledevice and dependencies to access iOS 13
  devices

Status in libimobiledevice package in Ubuntu:
  Incomplete
Status in libplist package in Ubuntu:
  Confirmed
Status in libusbmuxd package in Ubuntu:
  Confirmed
Status in usbmuxd package in Ubuntu:
  Confirmed

Bug description:
  iOS 13 devices require updated libimobiledevice, libusbmuxd and
  usbmuxd to work correctly. Without the updates, the device appears to
  be accessible but it's impossible to copy files to the devices.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1854403/+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 1557157] Re: apparmor profile denied for saslauthd: /run/saslauthd/mux

2020-06-15 Thread Launchpad Bug Tracker
** Merge proposal linked:
   
https://code.launchpad.net/~sergiodj/ubuntu/+source/openldap/+git/openldap/+merge/385760

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

Title:
  apparmor profile denied for saslauthd: /run/saslauthd/mux

Status in openldap package in Ubuntu:
  Confirmed
Status in openldap source package in Trusty:
  Confirmed
Status in openldap source package in Xenial:
  Confirmed
Status in openldap source package in Bionic:
  Confirmed
Status in openldap source package in Focal:
  Confirmed
Status in openldap source package in Groovy:
  Confirmed

Bug description:
  [Impact]

  When using openldap with sasl authentication, the slapd process will
  communicate with the saslauthd daemon via a socket in
  {,/var}/run/saslauthd/mux. Unfortunately, this will fail in every
  Ubuntu release from trusty onwards, because slapd's apparmor profile
  doesn't contain the necessary directive to allow it to read/write
  from/to the socket specified above.

  The fix is simple: just add the necessary directive to allow slapd to
  read/write from/to the saslauthd socket.

  [Test Case]

  One can reproduce the problem by doing:

  $ lxc launch ubuntu-daily:groovy openldap-bugbug1557157-groovy
  $ lxc shell openldap-bugbug1557157-groovy
  # apt install slapd sasl2-bin ldap-utils apparmor-utils

  (As the domain name, use "example.com").

  # sed -i -e 's/^START=.*/START=yes/' /etc/default/saslauthd
  # cat > /etc/ldap/sasl2/slapd.conf << __EOF__
  mech_list: PLAIN
  pwcheck_method: saslauthd
  __EOF__
  # adduser openldap sasl
  # aa-enforce /etc/apparmor.d/usr.sbin.slapd
  # systemctl restart slapd.service
  # systemctl restart saslauthd.service
  # passwd root

  (You can choose any password here. You will need to type it when
  running the next command.)

  # ldapsearch -H ldapi:/// -LLL -b 'dc=example,dc=com' -s base -U root
  -Y PLAIN

  The command will fail with something like:

  ldap_sasl_interactive_bind_s: Other (e.g., implementation specific) error (80)
  additional info: SASL(-1): generic failure: Password verification 
failed

  [Regression Potential]

  This is an extremely simple and well contained fix, so I don't
  envision any possible regressions after applying it.  It is important
  noticing that, since the problem affects older Ubuntu releases, the
  openldap package will have to be rebuilt against possible newer
  versions of libraries and other depencencies, which, albeit unlikely,
  may cause issues.

  [Original Description]

  When using slapd with saslauthd the processes communicate via the
  {,/var}/run/saslauthd/mux socket (this is the default location for the
  saslauthd server from the sasl2-bin package in the
  /etc/default/saslauthd config), but the apparmor profile for
  usr.sbin.slapd does not allow access to this socket/file.

  Syslog message:
  apparmor="DENIED" operation="connect" profile="/usr/sbin/slapd" 
name="/run/saslauthd/mux" pid=1880
  4 comm="slapd" requested_mask="r" denied_mask="r" fsuid=108 ouid=0

  Please add the following line to  /etc/apparmor.d/usr.sbin.slapd:
  /{,var/}run/saslauthd/mux rw,

  Ubuntu version: Ubuntu 14.04.4 LTS
  slapd version: 2.4.31-1+nmu2ubu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1557157/+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 1557157] Re: apparmor profile denied for saslauthd: /run/saslauthd/mux

2020-06-15 Thread Launchpad Bug Tracker
** Merge proposal linked:
   
https://code.launchpad.net/~sergiodj/ubuntu/+source/openldap/+git/openldap/+merge/385758

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

Title:
  apparmor profile denied for saslauthd: /run/saslauthd/mux

Status in openldap package in Ubuntu:
  Confirmed
Status in openldap source package in Trusty:
  Confirmed
Status in openldap source package in Xenial:
  Confirmed
Status in openldap source package in Bionic:
  Confirmed
Status in openldap source package in Focal:
  Confirmed
Status in openldap source package in Groovy:
  Confirmed

Bug description:
  When using slapd with saslauthd the processes communicate via the
  {,/var}/run/saslauthd/mux socket (this is the default location for the
  saslauthd server from the sasl2-bin package in the
  /etc/default/saslauthd config), but the apparmor profile for
  usr.sbin.slapd does not allow access to this socket/file.

  Syslog message:
  apparmor="DENIED" operation="connect" profile="/usr/sbin/slapd" 
name="/run/saslauthd/mux" pid=1880
  4 comm="slapd" requested_mask="r" denied_mask="r" fsuid=108 ouid=0

  
  Please add the following line to  /etc/apparmor.d/usr.sbin.slapd:
  /{,var/}run/saslauthd/mux rw,

  
  Ubuntu version: Ubuntu 14.04.4 LTS
  slapd version: 2.4.31-1+nmu2ubu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1557157/+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 1882415] Re: Graphical artifact in top-right corner, owned by ibus-ui-gtk3

2020-06-15 Thread vasdi
$ env | grep -E 'XMOD|_IM'

GTK_IM_MODULE=ibus
QT4_IM_MODULE=ibus
XMODIFIERS=@im=ibus
CLUTTER_IM_MODULE=ibus
QT_IM_MODULE=ibus

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

Title:
  Graphical artifact in top-right corner, owned by ibus-ui-gtk3

Status in gnome-shell package in Ubuntu:
  New
Status in ibus package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04, Gnome 3.36.2, Nvidia

  Small gray line in top-right corner.
  More precisely, it happens to be in the corner in 1920x1080 resolution. Not 
present in smaller resolutions. In panning mode it's fixed to panel, not screen.
  Present on the panel and on fullscreen windows but not in overview.
  Not clickable (prevents me from clicking button underneath it).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2014-11-12 (2037 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-37.41-lowlatency 5.4.41
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  Tags:  focal
  Uname: Linux 5.4.0-37-lowlatency x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-01 (40 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882415/+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 1883534] Re: Screen flickering

2020-06-15 Thread Ubuntu Foundations Team Bug Bot
** Package changed: ubuntu => xorg (Ubuntu)

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

Title:
  Screen flickering

Status in xorg package in Ubuntu:
  New

Bug description:
  To whom it may concern,

  As stated I have screen flickerings (see lightning like flickering on photo 
attached for portrait screen, for horizontal screen I also have screen 
flickering on the upper part but hard to catch in a photo) on freshly installed 
Ubuntu 20.04 LTS.
  I have tried this:

  https://askubuntu.com/questions/1231441/ubuntu-screen-flickering

  and this:

  https://learnubuntumate.weebly.com/screen-tearing-on-intel-
  graphics.html

  without success. I have also seen some other people mentioning screen
  flickering on ubuntu 20.04 here:

  
https://www.reddit.com/r/Ubuntu/comments/fvk536/anyone_else_noticing_window_flickering_on_ubuntu/

  without solution.

  I also know that it is very unlikely hardware problem because my screens were 
displaying well on archlinux. I think my graphic card info are already included 
in the report but just in case: Intel Corporation UHD Graphics 630. Might be 
intel driver problems ?
  Could you help me on this please ?

  Best regards,
  Jeremy

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 15 15:05:27 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Desktop) [8086:3e92] (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. UHD Graphics 630 (Desktop) [1043:8694]
  InstallationDate: Installed on 2020-06-12 (2 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 046a:0023 Cherry GmbH Keyboard
   Bus 001 Device 003: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Lsusb-t:
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 5000M
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
   |__ Port 9: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 
1.5M
   |__ Port 9: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 
1.5M
   |__ Port 10: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 
1.5M
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=81cee77a-b529-4dac-9834-dc6d5ab2dc16 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/11/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0615
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME Z370-P
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0615:bd04/11/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ370-P:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1883534/+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 1557157] Re: apparmor profile denied for saslauthd: /run/saslauthd/mux

2020-06-15 Thread Launchpad Bug Tracker
** Merge proposal linked:
   
https://code.launchpad.net/~sergiodj/ubuntu/+source/openldap/+git/openldap/+merge/385757

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

Title:
  apparmor profile denied for saslauthd: /run/saslauthd/mux

Status in openldap package in Ubuntu:
  Confirmed
Status in openldap source package in Trusty:
  Confirmed
Status in openldap source package in Xenial:
  Confirmed
Status in openldap source package in Bionic:
  Confirmed
Status in openldap source package in Focal:
  Confirmed
Status in openldap source package in Groovy:
  Confirmed

Bug description:
  When using slapd with saslauthd the processes communicate via the
  {,/var}/run/saslauthd/mux socket (this is the default location for the
  saslauthd server from the sasl2-bin package in the
  /etc/default/saslauthd config), but the apparmor profile for
  usr.sbin.slapd does not allow access to this socket/file.

  Syslog message:
  apparmor="DENIED" operation="connect" profile="/usr/sbin/slapd" 
name="/run/saslauthd/mux" pid=1880
  4 comm="slapd" requested_mask="r" denied_mask="r" fsuid=108 ouid=0

  
  Please add the following line to  /etc/apparmor.d/usr.sbin.slapd:
  /{,var/}run/saslauthd/mux rw,

  
  Ubuntu version: Ubuntu 14.04.4 LTS
  slapd version: 2.4.31-1+nmu2ubu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1557157/+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 1883534] [NEW] Screen flickering

2020-06-15 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

To whom it may concern,

As stated I have screen flickerings (see lightning like flickering on photo 
attached for portrait screen, for horizontal screen I also have screen 
flickering on the upper part but hard to catch in a photo) on freshly installed 
Ubuntu 20.04 LTS.
I have tried this:

https://askubuntu.com/questions/1231441/ubuntu-screen-flickering

and this:

https://learnubuntumate.weebly.com/screen-tearing-on-intel-graphics.html

without success. I have also seen some other people mentioning screen
flickering on ubuntu 20.04 here:

https://www.reddit.com/r/Ubuntu/comments/fvk536/anyone_else_noticing_window_flickering_on_ubuntu/

without solution.

I also know that it is very unlikely hardware problem because my screens were 
displaying well on archlinux. I think my graphic card info are already included 
in the report but just in case: Intel Corporation UHD Graphics 630. Might be 
intel driver problems ?
Could you help me on this please ?

Best regards,
Jeremy

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
Uname: Linux 5.4.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Jun 15 15:05:27 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation UHD Graphics 630 (Desktop) [8086:3e92] (prog-if 00 [VGA 
controller])
   Subsystem: ASUSTeK Computer Inc. UHD Graphics 630 (Desktop) [1043:8694]
InstallationDate: Installed on 2020-06-12 (2 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 046a:0023 Cherry GmbH Keyboard
 Bus 001 Device 003: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
 /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 5000M
 /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
 |__ Port 9: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
 |__ Port 9: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M
 |__ Port 10: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
MachineType: System manufacturer System Product Name
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=81cee77a-b529-4dac-9834-dc6d5ab2dc16 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/11/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0615
dmi.board.asset.tag: Default string
dmi.board.name: PRIME Z370-P
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0615:bd04/11/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ370-P:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: System Product Name
dmi.product.sku: SKU
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug corruption focal ubuntu
-- 
Screen flickering
https://bugs.launchpad.net/bugs/1883534
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to xorg 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 1557157] Re: apparmor profile denied for saslauthd: /run/saslauthd/mux

2020-06-15 Thread Launchpad Bug Tracker
** Merge proposal linked:
   
https://code.launchpad.net/~sergiodj/ubuntu/+source/openldap/+git/openldap/+merge/385753

** Merge proposal linked:
   
https://code.launchpad.net/~sergiodj/ubuntu/+source/openldap/+git/openldap/+merge/385755

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

Title:
  apparmor profile denied for saslauthd: /run/saslauthd/mux

Status in openldap package in Ubuntu:
  Confirmed
Status in openldap source package in Trusty:
  Confirmed
Status in openldap source package in Xenial:
  Confirmed
Status in openldap source package in Bionic:
  Confirmed
Status in openldap source package in Focal:
  Confirmed
Status in openldap source package in Groovy:
  Confirmed

Bug description:
  When using slapd with saslauthd the processes communicate via the
  {,/var}/run/saslauthd/mux socket (this is the default location for the
  saslauthd server from the sasl2-bin package in the
  /etc/default/saslauthd config), but the apparmor profile for
  usr.sbin.slapd does not allow access to this socket/file.

  Syslog message:
  apparmor="DENIED" operation="connect" profile="/usr/sbin/slapd" 
name="/run/saslauthd/mux" pid=1880
  4 comm="slapd" requested_mask="r" denied_mask="r" fsuid=108 ouid=0

  
  Please add the following line to  /etc/apparmor.d/usr.sbin.slapd:
  /{,var/}run/saslauthd/mux rw,

  
  Ubuntu version: Ubuntu 14.04.4 LTS
  slapd version: 2.4.31-1+nmu2ubu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1557157/+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 1882161] Re: module-switch-on-port-avaiable: switch the port on ucm devices based on the priority

2020-06-15 Thread Sebastien Bacher
@Hui, sorry I did upload what in the vcs to groovy before reading your
comment here, I will not upload to focal yet though

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

Title:
  module-switch-on-port-avaiable: switch the port on ucm devices based
  on the priority

Status in HWE Next:
  New
Status in pulseaudio package in Ubuntu:
  Fix Committed
Status in pulseaudio source package in Focal:
  In Progress
Status in pulseaudio source package in Groovy:
  Fix Committed

Bug description:
  This bug originates from an OEM private bug #1875597, then ubuntu
  users reported 2 public bugs #1871329 and #1881659. The 2nd issue of
  #1871329 and the 1st issue of #1881659 have the same root cause as
  #1875597

  [Impact]
  On the Dell machines with multi function audio jack, after installing the 
ubuntu 20.04 and if the audio driver is sof instead of legacy hda, the 
headphone/headset can't output sound automatically after users plug in a 
headphone/headset. This is different from ubuntu 18.04, on the 18.04, the 
headphone/headset could output sound automatically after plugging in the audio 
jack.

  [Fix]
  The root cause is the ucm2 conf defines 2 input devices: the Mic2 and Headset 
MIC, and the pulseaudio parse the input device Headset MIC first then Mic2, 
finally the audio jack is set to Mic2 mode, this make the audio jack can't 
output sound anymore. To fix it, let the audio jack set to Headset MIC mode by 
default (Headset MIC has higher priority than Mic2 in the ucm2 conf), to do so, 
let pulseaudio send the device event to module-switch-on-port-available by the 
order of priority in the umc2.

  [Test Case]
  applying the fix patch to pulseaudio, plug a headset/headphone to the multi 
function audio jack, play sound from headset/headphone, the sound could be 
heard from headset/headphone.

  [Regression Risk]
  Low, just do a small change to store the ucm devices by their priority. and 
upstream just merged this patch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1882161/+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 1872118] Re: DHCP Cluster crashes after a few hours

2020-06-15 Thread Brian Murray
** Tags added: focal rls-ff-incoming

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

Title:
  DHCP Cluster crashes after a few hours

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  
  I have a pair of DHCP serevrs running in a cluster on ubuntu 20.04, All 
worked perfectly until recently, when they started stopping with code=killed, 
status=6/ABRT.
  This is being fixed by 

  https://bugs.launchpad.net/bugs/1870729

  However now one stops after a few hours with the following errors. One
  can stay on line but not both.


  
  Syslog shows 
  Apr 10 17:20:15 dhcp-primary sh[6828]: 
../../../../lib/isc/unix/socket.c:3361: INSIST(!sock->pending_send) failed, 
back trace
  Apr 10 17:20:15 dhcp-primary sh[6828]: #0 0x7fbe78702a4a in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #1 0x7fbe78702980 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #2 0x7fbe7873e7e1 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #3 0x7fbe784e5609 in ??
  Apr 10 17:20:15 dhcp-primary sh[6828]: #4 0x7fbe78621103 in ??

  
  nothing in kern.log

  
  apport.log shows
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: called for pid 6828, 
signal 6, core limit 0, dump mode 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: not creating core for pid 
with dump mode of 2
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: executable: 
/usr/sbin/dhcpd (command line "dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf")
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: is_closing_session(): no 
DBUS_SESSION_BUS_ADDRESS in environment
  ERROR: apport (pid 6850) Fri Apr 10 17:20:15 2020: wrote report 
/var/crash/_usr_sbin_dhcpd.0.crash


  /var/crash/_usr_sbin_dhcpd.0.crash shows

  ProblemType: Crash
  Architecture: amd64
  CrashCounter: 1
  Date: Fri Apr 10 17:20:15 2020
  DistroRelease: Ubuntu 20.04
  ExecutablePath: /usr/sbin/dhcpd
  ExecutableTimestamp: 1586210315
  ProcCmdline: dhcpd -user dhcpd -group dhcpd -f -4 -pf 
/run/dhcp-server/dhcpd.pid -cf /etc/dhcp/dhcpd.conf
  ProcEnviron: Error: [Errno 13] Permission denied: 'environ'
  ProcMaps: Error: [Errno 13] Permission denied: 'maps'
  ProcStatus:
   Name:  dhcpd
   Umask: 0022
   State: D (disk sleep)
   Tgid:  6828
   Ngid:  0
   Pid:   6828
   PPid:  1
   TracerPid: 0
   Uid:   113 113 113 113
   Gid:   118 118 118 118
   FDSize:128
   Groups:
   NStgid:6828
   NSpid: 6828
   NSpgid:6828
   NSsid: 6828
   VmPeak:  236244 kB
   VmSize:  170764 kB
   VmLck:0 kB
   VmPin:0 kB
   VmHWM:12064 kB
   VmRSS:12064 kB
   RssAnon:   5940 kB
   RssFile:   6124 kB
   RssShmem: 0 kB
   VmData:   30792 kB
   VmStk:  132 kB
   VmExe:  592 kB
   VmLib: 5424 kB
   VmPTE:   76 kB
   VmSwap:   0 kB
   HugetlbPages: 0 kB
   CoreDumping:   1
   THP_enabled:   1
   Threads:   4
   SigQ:  0/7609
   SigPnd:
   ShdPnd:
   SigBlk:
   SigIgn:1000
   SigCgt:00018000
   CapInh:
   CapPrm:
   CapEff:
   CapBnd:003f
   CapAmb:
   NoNewPrivs:0
   Seccomp:   0
   Speculation_Store_Bypass:  thread vulnerable
   Cpus_allowed:  3
   Cpus_allowed_list: 0-1
   Mems_allowed:  
,,,,,,,,,,,,,,,,,,,,,,,,,,,,
  ,,,0001
   Mems_allowed_list: 0
   voluntary_ctxt_switches:   111
   nonvoluntary_ctxt_switches:144
  Signal: 6
  Uname: Linux 5.4.0-21-generic x86_64
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1872118/+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 1872106] Re: isc-dhcp-server crashing constantly [Ubuntu 20.04]

2020-06-15 Thread Brian Murray
** Tags added: focal rls-ff-incoming

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

Title:
  isc-dhcp-server crashing constantly [Ubuntu 20.04]

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  isc-dhcp-server crashing constantly (sometimes within seconds or minutes, 
sometimes within hours) with the following error messages:
  Apr 10 17:45:25 xxx dhcpd[140823]: Server starting service.
  Apr 10 17:45:25 xxx sh[140823]: ../../../../lib/isc/unix/socket.c:3361: 
INSIST(!sock->pending_send) failed, back trace
  Apr 10 17:45:25 xxx sh[140823]: #0 0x7f3362f59a4a in ??
  Apr 10 17:45:25 xxx sh[140823]: #1 0x7f3362f59980 in ??
  Apr 10 17:45:25 xxx sh[140823]: #2 0x7f3362f957e1 in ??
  Apr 10 17:45:25 xxx sh[140823]: #3 0x7f3362d3c609 in ??
  Apr 10 17:45:25 xxx sh[140823]: #4 0x7f3362e78103 in ??
  Apr 10 17:45:25 xxx systemd[1]: isc-dhcp-server.service: Main process exited, 
code=killed, status=6/ABRT
  Apr 10 17:45:25 xxx systemd[1]: isc-dhcp-server.service: Failed with result 
'signal'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1872106/+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 1872106] Re: isc-dhcp-server crashing constantly [Ubuntu 20.04]

2020-06-15 Thread Jamie Strandboge
@mm - that probably isn't the issue, but you can adjust
/etc/apparmor.d/local/usr.sbin.dhcpd to have:

@{PROC}/sys/net/ipv4/ip_local_port_range r,

and then do: sudo apparmor_parser -r /etc/apparmor.d/usr.sbin.dhcpd #
yes, without local/

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

Title:
  isc-dhcp-server crashing constantly [Ubuntu 20.04]

Status in isc-dhcp package in Ubuntu:
  Confirmed

Bug description:
  isc-dhcp-server crashing constantly (sometimes within seconds or minutes, 
sometimes within hours) with the following error messages:
  Apr 10 17:45:25 xxx dhcpd[140823]: Server starting service.
  Apr 10 17:45:25 xxx sh[140823]: ../../../../lib/isc/unix/socket.c:3361: 
INSIST(!sock->pending_send) failed, back trace
  Apr 10 17:45:25 xxx sh[140823]: #0 0x7f3362f59a4a in ??
  Apr 10 17:45:25 xxx sh[140823]: #1 0x7f3362f59980 in ??
  Apr 10 17:45:25 xxx sh[140823]: #2 0x7f3362f957e1 in ??
  Apr 10 17:45:25 xxx sh[140823]: #3 0x7f3362d3c609 in ??
  Apr 10 17:45:25 xxx sh[140823]: #4 0x7f3362e78103 in ??
  Apr 10 17:45:25 xxx systemd[1]: isc-dhcp-server.service: Main process exited, 
code=killed, status=6/ABRT
  Apr 10 17:45:25 xxx systemd[1]: isc-dhcp-server.service: Failed with result 
'signal'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1872106/+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 1882484] Re: Firewall rule in before.rules for dhcp is wrong

2020-06-15 Thread Jamie Strandboge
Marking as Invalid since the default firewall policy is working as
intended.

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

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

Title:
  Firewall rule in before.rules for dhcp is wrong

Status in ufw package in Ubuntu:
  Invalid

Bug description:
  The file delivered - /usr/share/ufw/iptables/before.rules
  which is then copied to - /etc/ufw/before.rules

  Delivered by Package:

  # allow dhcp client to work
  -A ufw-before-input -p udp --sport 67 --dport 68 -j ACCEPT

  The ports for
  --sport and --dport are swapped

  Should be:

  -A ufw-before-input -p udp --sport 68 --dport 67 -j ACCEPT

  
  Package version found in:
0.36-0ubuntu0.1

  
  Note: ISC DHCP uses RAW sockets, which bypasses iptables anyway and doesn't 
drop the packets with the incorrect configuration. This has had me stumped for 
the last hour.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1882484/+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 1882484] Re: Firewall rule in before.rules for dhcp is wrong

2020-06-15 Thread Jamie Strandboge
Thank you for filing a bug.

The firewall policy is a combination of the default policy for each of
'incoming', 'outgoing' and 'routed' (forward) along with the policies
shipped in before{,6}.rules, after{,6}.rules and whatever gets added to
user{,6}.rules. Specifically, what is in before{,6}.rules is designed
with default deny for incoming (and forward), default allow for outgoing
and default accept for established connections. Considering that dhcp
uses port 68/udp for the client and port 67/udp for the server, the
shipped default policy allows:

* outgoing from this host port 68/udp to any port 67/udp (via default allow 
outgoing; eg, for dhcp request)
* incoming for established connection (via before.rules RELATED,ESTABLISHED; 
eg, dhcp reply from the server we connected to on port 67/udp)
* incoming from port 67/udp (via the before.rules you mentioned; eg, for a 
server responding to the broadcast)

I suspect that you've updated your default policy to deny to perform
egress filtering so you need to add a corresponding 'ufw allow out to
any port 67 proto udp comment "dhcp discover"' rule or similar.

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

Title:
  Firewall rule in before.rules for dhcp is wrong

Status in ufw package in Ubuntu:
  Invalid

Bug description:
  The file delivered - /usr/share/ufw/iptables/before.rules
  which is then copied to - /etc/ufw/before.rules

  Delivered by Package:

  # allow dhcp client to work
  -A ufw-before-input -p udp --sport 67 --dport 68 -j ACCEPT

  The ports for
  --sport and --dport are swapped

  Should be:

  -A ufw-before-input -p udp --sport 68 --dport 67 -j ACCEPT

  
  Package version found in:
0.36-0ubuntu0.1

  
  Note: ISC DHCP uses RAW sockets, which bypasses iptables anyway and doesn't 
drop the packets with the incorrect configuration. This has had me stumped for 
the last hour.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1882484/+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 1882314] Re: Firewall rule in before6.rules for dhcp6 is wrong

2020-06-15 Thread Jamie Strandboge
Marking as Invalid since the default firewall policy is working as
intended.

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

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

Title:
  Firewall rule in before6.rules for dhcp6 is wrong

Status in ufw package in Ubuntu:
  Invalid

Bug description:
  When running DHCPv6, clients are not able get IP address.
  The firewall rule in ip6table is incorrect, and not allowing client requests 
in. The ports need to be swapped and the dst address needs to be removed, as 
it's a broadcast

  The file delivered - /usr/share/ufw/iptables/before6.rules
  which is then copied to - /etc/ufw/before6.rules

  Delivered by Package:

  # allow dhcp client to work
  -A ufw6-before-input -p udp -s fe80::/10 --sport 547 -d fe80::/10 --dport 546 
-j ACCEPT

  The ports for
  --sport and --dport are swapped
  -d fe80::/10 needs to be removed

  Should be:

  -A ufw6-before-input -p udp -s fe80::/10 --sport 546 --dport 547 -j
  ACCEPT

  Package version found in:
    0.36-0ubuntu0.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1882314/+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 1882314] Re: Firewall rule in before6.rules for dhcp6 is wrong

2020-06-15 Thread Jamie Strandboge
Thank you for filing a bug.

The firewall policy is a combination of the default policy for each of
'incoming', 'outgoing' and 'routed' (forward) along with the policies
shipped in before{,6}.rules, after{,6}.rules and whatever gets added to
user{,6}.rules. Specifically, what is in before{,6}.rules is designed
with default deny for incoming (and forward), default allow for outgoing
and default accept for established connections. Considering that dhcpv6
uses port 546/udp for the client and port 547/udp for the server, the
shipped default policy allows:

* outgoing from this host port 546/udp to any port 547/udp (via default allow 
outgoing; eg, for dhcp request)
* incoming for established connection (via before6.rules RELATED,ESTABLISHED; 
eg, dhcp reply from the server we connected to on port 547/udp)
* incoming from fe80::/10 port 547/udp (via the before6.rules you mentioned; 
eg, for a server responding to the broadcast)

I suspect that you've updated your default policy to deny to perform
egress filtering so you need to add a corresponding 'ufw allow out to
ff02::1:2 port 547 proto udp comment "dhcpv6 solicit"' rule or similar.

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

Title:
  Firewall rule in before6.rules for dhcp6 is wrong

Status in ufw package in Ubuntu:
  Invalid

Bug description:
  When running DHCPv6, clients are not able get IP address.
  The firewall rule in ip6table is incorrect, and not allowing client requests 
in. The ports need to be swapped and the dst address needs to be removed, as 
it's a broadcast

  The file delivered - /usr/share/ufw/iptables/before6.rules
  which is then copied to - /etc/ufw/before6.rules

  Delivered by Package:

  # allow dhcp client to work
  -A ufw6-before-input -p udp -s fe80::/10 --sport 547 -d fe80::/10 --dport 546 
-j ACCEPT

  The ports for
  --sport and --dport are swapped
  -d fe80::/10 needs to be removed

  Should be:

  -A ufw6-before-input -p udp -s fe80::/10 --sport 546 --dport 547 -j
  ACCEPT

  Package version found in:
    0.36-0ubuntu0.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1882314/+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 1883477] Re: When closing the lid of laptop, WiFi disconnects and doesn't reconnect afterwards

2020-06-15 Thread Markus1978
Forgot to mention Ubuntu Mate :-/

** Description changed:

- I am getting this issue since about a year on my Lenovo Thinkpad x240.
+ I am getting this issue since about a year on my Lenovo Thinkpad x240
+ with Ubuntu Mate
  
  I have configured the computer to stay awake and empty the screen
  (system settings > power management) when I close the lid with the power
  plugged in.
  
  What I expect to happen:
- Wifi network stays connected and network related programs (like bit-torrent 
or http downloads) continue to run.  
+ Wifi network stays connected and network related programs (like bit-torrent 
or http downloads) continue to run.
  
  What actually happens:
- Wifi always disconnects after closing the lid and doesn't come back upon 
opening it. 
+ Wifi always disconnects after closing the lid and doesn't come back upon 
opening it.
  I just see a "two arrows"-symbol on the top bar.
  
- When I try to reconnect manually, the wifi symbol is blinking, but the 
network manager eventually gives up. 
+ When I try to reconnect manually, the wifi symbol is blinking, but the 
network manager eventually gives up.
  I have to disable wifi (or network as a whole) for a second and enable it 
again, to then automatically reconnect to my home wifi network.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Mon Jun 15 06:09:25 2020
  IfupdownConfig:
-  # interfaces(5) file used by ifup(8) and ifdown(8)
-  # Include files from /etc/network/interfaces.d:
-  source-directory /etc/network/interfaces.d
+  # interfaces(5) file used by ifup(8) and ifdown(8)
+  # Include files from /etc/network/interfaces.d:
+  source-directory /etc/network/interfaces.d
  InstallationDate: Installed on 2019-12-06 (191 days ago)
  InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Release amd64 (20191017)
  IpRoute:
-  default via 192.168.2.1 dev wlp3s0 proto dhcp metric 600 
-  169.254.0.0/16 dev wlp3s0 scope link metric 1000 
-  192.168.2.0/24 dev wlp3s0 proto kernel scope link src 192.168.2.105 metric 
600 
-  192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
+  default via 192.168.2.1 dev wlp3s0 proto dhcp metric 600
+  169.254.0.0/16 dev wlp3s0 scope link metric 1000
+  192.168.2.0/24 dev wlp3s0 proto kernel scope link src 192.168.2.105 metric 
600
+  192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  ProcEnviron:
-  LANGUAGE=de_DE
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=de_DE.UTF-8
-  SHELL=/usr/bin/fish
+  LANGUAGE=de_DE
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=de_DE.UTF-8
+  SHELL=/usr/bin/fish
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to focal on 2020-05-07 (38 days ago)
  nmcli-nm:
-  RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN 
-  running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  disabled
+  RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
+  running  1.22.10  connected  started  full  enabled enabled  
enabled  enabled  disabled

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

Title:
  When closing the lid of laptop, WiFi disconnects and doesn't reconnect
  afterwards

Status in network-manager package in Ubuntu:
  New

Bug description:
  I am getting this issue since about a year on my Lenovo Thinkpad x240
  with Ubuntu Mate

  I have configured the computer to stay awake and empty the screen
  (system settings > power management) when I close the lid with the
  power plugged in.

  What I expect to happen:
  Wifi network stays connected and network related programs (like bit-torrent 
or http downloads) continue to run.

  What actually happens:
  Wifi always disconnects after closing the lid and doesn't come back upon 
opening it.
  I just see a "two arrows"-symbol on the top bar.

  When I try to reconnect manually, the wifi symbol is blinking, but the 
network manager eventually gives up.
  I have to disable wifi (or network as a whole) for a second and enable it 
again, to then automatically reconnect to my home wifi network.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.22.10-1ubuntu2.1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: MATE
  Date: Mon Jun 15 06:09:25 2020
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   # Include files from 

[Touch-packages] [Bug 1882415] Re: Graphical artifact in top-right corner, owned by ibus-ui-gtk3

2020-06-15 Thread Gunnar Hjalmarsson
@Daniel: I'm not sure either. Thought it could be wise to keep an open
mind until we are.

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

Title:
  Graphical artifact in top-right corner, owned by ibus-ui-gtk3

Status in gnome-shell package in Ubuntu:
  New
Status in ibus package in Ubuntu:
  New

Bug description:
  Ubuntu 20.04, Gnome 3.36.2, Nvidia

  Small gray line in top-right corner.
  More precisely, it happens to be in the corner in 1920x1080 resolution. Not 
present in smaller resolutions. In panning mode it's fixed to panel, not screen.
  Present on the panel and on fullscreen windows but not in overview.
  Not clickable (prevents me from clicking button underneath it).
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: GNOME
  DisplayManager: gdm3
  DistroRelease: Ubuntu 20.04
  InstallationDate: Installed on 2014-11-12 (2037 days ago)
  InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 
(20141022.1)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: gnome-shell 3.36.2-1ubuntu1~20.04.1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.4.0-37.41-lowlatency 5.4.41
  RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1~20.04.1
  Tags:  focal
  Uname: Linux 5.4.0-37-lowlatency x86_64
  UpgradeStatus: Upgraded to focal on 2020-05-01 (40 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882415/+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 1428020] Re: when running navit X Server crashes

2020-06-15 Thread Paul White
Ubuntu 14.04 (trusty) reached end-of-life on April 25,2019.
Bug report did not expire due to bug watch
Upstream report suggests issue *should* now be fixed

This issue has sat incomplete for over five years now without any
response so I'm going to close it as "Invalid".

Please feel free to re-open this report if this is still an issue when
using a currently supported release of Ubuntu.

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

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

Title:
  when running navit X Server crashes

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Description:  Ubuntu 14.04.2 LTS
  Release:  14.04
  xorg:
Installed: 1:7.7+1ubuntu8.1
Candidate: 1:7.7+1ubuntu8.1
Version table:
   *** 1:7.7+1ubuntu8.1 0
  500 http://archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   1:7.7+1ubuntu8 0
  500 http://archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
  ---
  grep EE Xorg.0.debug.log.old
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
  [ 8.193] Initializing built-in extension MIT-SCREEN-SAVER
  [ 8.202] (EE) Failed to load module "nvidia" (module does not exist, 0)
  [ 8.203] (EE) Failed to load module "nvidia" (module does not exist, 0)
  [10.214] (EE) NOUVEAU(G0): Failed to initialise context object: 2D_NVC0 
(0)
  [10.215] (EE) NOUVEAU(G0): Error initialising acceleration.  Falling back 
to NoAccel
  [20.954] (EE) 
  [20.954] (EE) Backtrace:
  [20.955] (EE) 0: /usr/bin/X (xorg_backtrace+0x48) [0x7fc32acd5848]
  [20.955] (EE) 1: /usr/bin/X (0x7fc32ab2c000+0x1ad539) [0x7fc32acd9539]
  [20.955] (EE) 2: /lib/x86_64-linux-gnu/libpthread.so.0 
(0x7fc329c29000+0x10340) [0x7fc329c39340]
  [20.955] (EE) 3: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fc324693000+0xd9168) [0x7fc32476c168]
  [20.955] (EE) 4: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fc324693000+0x2d540) [0x7fc3246c0540]
  [20.955] (EE) 5: /usr/bin/X (0x7fc32ab2c000+0x19ce55) [0x7fc32acc8e55]
  [20.955] (EE) 6: /usr/bin/X (0x7fc32ab2c000+0x19f281) [0x7fc32accb281]
  [20.955] (EE) 7: /usr/bin/X (miWideDash+0x142b) [0x7fc32acccf3b]
  [20.955] (EE) 8: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fc324693000+0x4c3de) [0x7fc3246df3de]
  [20.955] (EE) 9: /usr/bin/X (0x7fc32ab2c000+0x1361d8) [0x7fc32ac621d8]
  [20.955] (EE) 10: /usr/bin/X (0x7fc32ab2c000+0x5277f) [0x7fc32ab7e77f]
  [20.955] (EE) 11: /usr/bin/X (0x7fc32ab2c000+0x55f0e) [0x7fc32ab81f0e]
  [20.955] (EE) 12: /usr/bin/X (0x7fc32ab2c000+0x59d9a) [0x7fc32ab85d9a]
  [20.955] (EE) 13: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf5) [0x7fc328669ec5]
  [20.955] (EE) 14: /usr/bin/X (0x7fc32ab2c000+0x451ee) [0x7fc32ab711ee]
  [20.955] (EE) 
  [20.955] (EE) Segmentation fault at address 0x7fff1d6a3004
  [20.955] (EE) 
  [20.955] (EE) Caught signal 11 (Segmentation fault). Server aborting
  [20.955] (EE) 
  [20.955] (EE) 
  [20.955] (EE) Please also check the log file at "/var/log/Xorg.0.log" for 
additional information.
  [20.955] (EE) 
  [20.983] (EE) Server terminated with error (1). Closing log file.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-46.77-generic 3.13.11-ckt15
  Uname: Linux 3.13.0-46-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.7
  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 Mar  4 18:28:32 2015
  DistUpgraded: 2014-10-07 19:02:16,253 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer Device [1558:5281]
   NVIDIA Corporation GK104M [GeForce GTX 870M] [10de:1199] (rev a1) (prog-if 
00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer Device [1558:5281]
  InstallationDate: Installed on 2014-10-07 (147 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Notebook P15SM-A/SM1-A
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-46-generic 
root=/dev/mapper/ubuntu--vg-root ro plymouth:debug drm.debug=0xe 
pci-assign-busses=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to trusty on 2014-10-07 (147 days 

[Touch-packages] [Bug 1883441] Re: Fatal interaction between sfdisk and lsblk

2020-06-15 Thread Mauricio Faria de Oliveira
Hi Kevin,

I could not reproduce this on a Bionic VM with a loop device w/ two NTFS
partitions (type + filesystem).

Could you please provide a strace log of both default/-s cases from your
environment?

# strace -ffttTy -o strace.log b5.sh  
# tar cvf lp1883441-strace.tar strace.log.*

** Changed in: util-linux (Ubuntu)
   Status: New => Incomplete

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

Title:
  Fatal interaction between sfdisk and lsblk

Status in util-linux package in Ubuntu:
  Incomplete

Bug description:
  I'm posting this against util-linux because it's lsblk calls that
  fail, but the failure depends on a prior call to sfdisk which is part
  of the fdisk package.  Remove the sfdisk call, and the failure does
  not happen, at least in my test setup.

  A call to sfdisk in a script causes a failure of a later series of
  calls to lsblk, in which lsblk fails to return information.

  I know sfdisk is designed for humans, but I'm wanting to automate the
  operation of its --backup option, and don't know of another way.  In
  any event, this failure shoudl be addressed.

  I'm attaching a script with illustrates both the problem and a
  workaround.  The workaround is to introduce a "sleep 1" call in
  between the calls to lsblk.  I can't even imagine why this works, but
  it does in my configuration.  I call the script with the name of a
  device which contains two ntfs partitions, and the name of a directory
  where results are to be stored.  The directory must contain a
  "clone.log" file (it can be empty; it's just to make sure I'm naming
  the correct directory).

  If I call it so it fails:
 bash b5.sh sda /tmp
  because the final lsblk call does not return any information

  However, if I call is to, it succeeds:
 bash -s b5.sh sda /tmp
  because the "-s" switch introduces a "sleep 1" call between lsblk calls.

  This makes no sense, which is why I consider it a bug.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: util-linux 2.31.1-0.4ubuntu3.6
  ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18
  Uname: Linux 4.15.0-101-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.15
  Architecture: amd64
  Date: Sun Jun 14 09:36:17 2020
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1883441/+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 1883345] Re: package linux-image-5.4.0-37-generic 5.4.0-37.41 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

2020-06-15 Thread Kai Kasurinen
Processing triggers for linux-image-5.4.0-37-generic (5.4.0-37.41) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.4.0-37-generic
I: The initramfs will attempt to resume from /dev/sdb4
I: (UUID=88dc372a-433f-49a6-ac50-550ac780984f)
I: Set the RESUME variable to override this.
sicherboot: Installing 5.4.0-37-generic to ESP
cat: /etc/kernel/cmdline: No such file or directory
objcopy: cannot open: /etc/kernel/cmdline: No such file or directory
run-parts: /etc/initramfs/post-update.d//zz-sicherboot exited with return code 1
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

** Package changed: initramfs-tools (Ubuntu) => sicherboot (Ubuntu)

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

Title:
  package linux-image-5.4.0-37-generic 5.4.0-37.41 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in sicherboot package in Ubuntu:
  New

Bug description:
  Linux saturn 5.4.0-33-generic #37-Ubuntu SMP Thu May 21 12:53:59 UTC
  2020 x86_64 x86_64 x86_64 GNU/Linux

  I: Set the RESUME variable to override this.
  sicherboot: Installing 5.4.0-37-generic to ESP
  cat: /etc/kernel/cmdline: No such file or directory
  objcopy: cannot open: /etc/kernel/cmdline: No such file or directory
  run-parts: /etc/initramfs/post-update.d//zz-sicherboot exited with return 
code 1
  run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
  dpkg: error processing package linux-image-5.4.0-37-generic (--configure):
   installed linux-image-5.4.0-37-generic package post-installation script 
subproc
  ess returned error exit status 1
  Errors were encountered while processing:
   initramfs-tools
   linux-image-5.4.0-37-generic
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: linux-image-5.4.0-37-generic 5.4.0-37.41
  ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34
  Uname: Linux 5.4.0-33-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ford   2896 F pulseaudio
  CasperMD5CheckResult: skip
  Date: Fri Jun 12 23:10:44 2020
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2020-05-07 (36 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402)
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
   
   enp7s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic 
root=UUID=9add8ec4-19e1-4a98-87eb-c5c415fcf690 ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions: grub-pc 2.04-1ubuntu26
  RfKill:
   
  SourcePackage: initramfs-tools
  Title: package linux-image-5.4.0-37-generic 5.4.0-37.41 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/06/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F20e
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77X-UD3H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF20e:bd01/06/2014:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77X-UD3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sicherboot/+bug/1883345/+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 1883516] [NEW] display is freezing randomly

2020-06-15 Thread Hermann Gregor
Public bug reported:

My display is freezing randomly, while the system seems to be running,
since music is playing.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
Uname: Linux 5.4.0-37-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Jun 15 11:58:54 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo HD Graphics 620 [17aa:505f]
InstallationDate: Installed on 2020-04-24 (51 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: LENOVO 20J5S00C00
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=47fb22f8-4f7e-4824-80f7-5db5105765e0 ro intel_idle.max_cstate=1 quiet 
splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/24/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: R0GET63W (1.63 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20J5S00C00
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrR0GET63W(1.63):bd02/24/2018:svnLENOVO:pn20J5S00C00:pvrThinkPadL470:rvnLENOVO:rn20J5S00C00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad L470
dmi.product.name: 20J5S00C00
dmi.product.sku: LENOVO_MT_20J5_BU_Think_FM_ThinkPad L470
dmi.product.version: ThinkPad L470
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug focal ubuntu

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

Title:
  display is freezing randomly

Status in xorg package in Ubuntu:
  New

Bug description:
  My display is freezing randomly, while the system seems to be running,
  since music is playing.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun 15 11:58:54 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 620 [17aa:505f]
  InstallationDate: Installed on 2020-04-24 (51 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  MachineType: LENOVO 20J5S00C00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=47fb22f8-4f7e-4824-80f7-5db5105765e0 ro intel_idle.max_cstate=1 quiet 
splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/24/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: R0GET63W (1.63 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20J5S00C00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrR0GET63W(1.63):bd02/24/2018:svnLENOVO:pn20J5S00C00:pvrThinkPadL470:rvnLENOVO:rn20J5S00C00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad L470
  dmi.product.name: 20J5S00C00
  dmi.product.sku: LENOVO_MT_20J5_BU_Think_FM_ThinkPad L470
  dmi.product.version: ThinkPad L470
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1
  version.libdrm2: libdrm2 2.4.101-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1
  

[Touch-packages] [Bug 1876055] Re: SRU: Backport 2.4.3-1ubuntu3 from groovy to focal/eoan/bionic/xenial for newer syscalls for core20 base and test suite robustness

2020-06-15 Thread Alex Murray
@jdstrand - thanks but unfortunately that version FTBFS on arm64 - I've
uploaded an updated verion (ubuntu3.11 -
https://launchpadlibrarian.net/484321608/systemd_242-7ubuntu3.11_source.changes)
to the security-proposed PPA with an additional upstream fix for the
arm64 FTBFS - this is currently undergoing autopkgtests
(https://people.canonical.com/~platform/security-
britney/current/security_eoan_excuses.html#systemd) - will report back
with results once complete.

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

Title:
  SRU: Backport 2.4.3-1ubuntu3 from groovy to focal/eoan/bionic/xenial
  for newer syscalls for core20 base and test suite robustness

Status in libseccomp package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  New
Status in libseccomp source package in Xenial:
  Fix Committed
Status in libseccomp source package in Bionic:
  Fix Committed
Status in libseccomp source package in Eoan:
  Fix Committed
Status in systemd source package in Eoan:
  New
Status in libseccomp source package in Focal:
  Fix Committed
Status in libseccomp source package in Groovy:
  Fix Released

Bug description:
  [Impact]

  The combination of snap-confine and snap-seccomp from snapd uses
  libseccomp to filter various system calls for confinement. The current
  version in eoan/bionic/xenial (2.4.1) is missing knowledge of various
  system calls for various architectures. As such this causes strange
  issues like python snaps segfaulting
  (https://github.com/snapcore/core20/issues/48) or the inadvertent
  denial of system calls which should be permitted by the base policy
  (https://forum.snapcraft.io/t/getrlimit-blocked-by-seccomp-on-focal-
  arm64/17237).

  libseccomp in groovy is using the latest upstream base release (2.4.3)
  plus it includes a patch to add some missing aarch64 system calls
  (https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1877633).

  SRUing this version back to older stable releases allows libseccomp to
  operate correctly on all supported architectures.

  
  Included as part of this SRU are test-suite reliability improvements - 
currently the xenial libseccomp package overrides test-suite failures at build 
time to ignore failures. This masks the fact that on ppc64el and s390x there 
are currently test suite failures at build time for xenial - these failures 
occur since libseccomp now includes knowledge of system calls for these 
architectures but which the linux-libc-dev package for xenial does not actually 
define (since this is based of the 4.4 kernel in xenial whereas libseccomp 
2.4.1 in xenial has knowledge of all system calls up to 5.4). 

  In this SRU I have instead fixed the test suite failures for xenial by
  including a local (test-suite specific) set of architecture specific
  kernel headers from the linux-libc-dev in focal for all releases.
  These are just the headers which define the system call numbers for
  each architecture *and* these are added to tests/include/$ARCH in the
  source package (and tests/Makefile.am is then updated to include these
  new headers only).  As such this ensures the actual build of
  libseccomp or any of the tools does not reference these headers. This
  allows the test suite in libseccomp to then be aware of theses system
  calls and so all unit tests for all architectures now pass.

  In any future updates for libseccomp to add new system calls, we can
  then similarly update these local headers to ensure the unit tests
  continue to work as expected.

  
  [Test Case]

  libseccomp includes a significant unit test suite that is run during
  the build and as part of autopkgtests. To verify the new aarch64
  system calls are resolved as expected the scmp_sys_resolver command
  can be used as well:

  $ scmp_sys_resolver -a aarch64 getrlimit
  163

  (whereas in the current version in focal this returns -10180 as
  libseccomp was not aware of this system-call at compile-time).

  As part of this SRU, the test suite in libseccomp has been patched to
  include a local copy of the architecture-specific kernel headers from
  the 5.4 kernel in focal *for all releases*, so that all system calls
  which are defined for the 5.4 kernel are known about *for the
  libseccomp test suite*. This allows all unit tests to pass on older
  releases as well and defaults the build to fail on unit test failures
  (whereas currently in xenial this has been overridden to ignore
  failures).

  
  [Regression Potential]

  This has a low regression potential due to significant testing with
  many packages that depend on libseccomp (lxc, qemu, snapd, apt, man
  etc) and none have shown any regression using this new version. The
  re-enablement of build failure on test failure at build time also
  ensures that we can reliably detect FTBFS issues in the future.

  No symbols have been removed (or added) with this 

[Touch-packages] [Bug 1556409] Re: dhclient crashed with SIGABRT in isc_assertion_failed()

2020-06-15 Thread prathap
*** This bug is a duplicate of bug 1552695 ***
https://bugs.launchpad.net/bugs/1552695

is this issue fixed? i am also facing similar crash.

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

Title:
  dhclient crashed with SIGABRT in isc_assertion_failed()

Status in isc-dhcp package in Ubuntu:
  New

Bug description:
  Further information? Let me know.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: isc-dhcp-client 4.3.3-5ubuntu9
  ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4
  Uname: Linux 4.4.0-12-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Sat Mar 12 12:22:54 2016
  DhclientLeases:
   
  ExecutablePath: /sbin/dhclient
  InstallationDate: Installed on 2016-03-11 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160307)
  ProcAttrCurrent: /sbin/dhclient (enforce)
  ProcCmdline: BOOT_IMAGE=/@/boot/vmlinuz-4.4.0-12-generic 
root=UUID=6ecbcdf8-efca-481d-884b-9b2e2c58b854 ro rootflags=subvol=@ quiet 
splash vt.handoff=7
  Signal: 6
  SourcePackage: isc-dhcp
  StacktraceTop:
   isc_assertion_failed () from /usr/lib/x86_64-linux-gnu/libisc.so.160
   isc_timer_detach () from /usr/lib/x86_64-linux-gnu/libisc.so.160
   ?? ()
   ?? () from /usr/lib/x86_64-linux-gnu/libisc.so.160
   start_thread (arg=0x7fd021a78700) at pthread_create.c:333
  Title: dhclient crashed with SIGABRT in isc_assertion_failed()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1556409/+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 1883489] Re: Logrotate failed to start in LUbuntu 20.04

2020-06-15 Thread Ubuntu Foundations Team Bug Bot
The attachment "The corrected file in /etc/logrotate.d" seems to be a
patch.  If it isn't, please remove the "patch" flag from the attachment,
remove the "patch" tag, and if you are a member of the ~ubuntu-
reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  Logrotate failed to start in LUbuntu 20.04

Status in logrotate package in Ubuntu:
  Confirmed

Bug description:
  After fresh installation of LUbuntu 20.04, when I switched off
  Plymouth, failure of logrotate appeared on the screen during boot.

  (PIDs are replaced by ***)
  :~$ systemctl status logrotate
  ● logrotate.service - Rotate log files
   Loaded: loaded (/lib/systemd/system/logrotate.service; static; vendor 
preset: enabled)
   Active: failed (Result: exit-code) since Mon 2020-06-15 07:56:59 EEST; 
32s ago
  TriggeredBy: ● logrotate.timer
 Docs: man:logrotate(8)
   man:logrotate.conf(5)
  Process: *** ExecStart=/usr/sbin/logrotate /etc/logrotate.conf 
(code=exited, status=1/FAILURE)
 Main PID: *** (code=exited, status=1/FAILURE)

  Jun 15 07:56:55  systemd[***]: Starting Rotate log files...
  Jun 15 07:56:59  logrotate[***]: error: error running shared 
postrotate script for '/var/log/mysql.log /var/log/mysql/*log '
  Jun 15 07:56:59  systemd[***]: logrotate.service: Main process 
exited, code=exited, status=1/FAILURE
  Jun 15 07:56:59  systemd[***]: logrotate.service: Failed with result 
'exit-code'.
  Jun 15 07:56:59  systemd[***]: Failed to start Rotate log files.

  I compared /etc/logrotate.d/samba with the information at 
https://salsa.debian.org/samba-team/samba/commit/bed29aba47558252eacfe9453d23cc1ab29770aa
  Two different lines have been found:

  In /etc/logrotate.d/samba:

  line 6: [ ! -x /usr/bin/smbcontrol ] || [ ! -f /run/samba/smbd.pid ]
  || /usr/bin/smbcontrol smbd reload-config

  line 18: [ ! -x /usr/bin/smbcontrol ] || [ ! -f /run/samba/nmbd.pid ]
  || /usr/bin/smbcontrol nmbd reload-config

  at https://...

  line 6: [ ! -x /usr/bin/smbcontrol ] || [ ! -f /var/run/samba/nmbd.pid
  ] || /usr/bin/smbcontrol nmbd reload-config

  line 18: [ ! -x /usr/bin/smbcontrol ] || [ ! -f
  /var/run/samba/nmbd.pid ] || /usr/bin/smbcontrol nmbd reload-config

  There is a same difference: in LUbuntu 20.04 .pid files are searched
  in /run/samba/, but at https://... they are searched in
  /var/run/samba/. After boot, both are present and have the same PIDs.

  :~$ cat /var/run/samba/nmbd.pid
  abcd
  :~$ cat /run/samba/nmbd.pid
  abcd
  :~$ cat /var/run/samba/smbd.pid
  efgh
  :~$ cat /run/samba/smbd.pid
  efgh

  (digits are replaced by letters for security reasons)

  Changing the folders according to https://... and reboot solve the
  problem:

  :~$ systemctl status logrotate
  ● logrotate.service - Rotate log files
   Loaded: loaded (/lib/systemd/system/logrotate.service; static; vendor 
preset: enabled)
   Active: inactive (dead)
  TriggeredBy: ● logrotate.timer
 Docs: man:logrotate(8)
   man:logrotate.conf(5)

  After that, I tried to revert the changes and reboot. The bug cannot
  be reproduced anymore.

  Additional information:

  :~$ lsb_release -rd
  Description:Ubuntu 20.04 LTS
  Release:20.04
  :~$ apt-cache policy logrotate
  logrotate:
Installed: 3.14.0-4ubuntu3
Candidate: 3.14.0-4ubuntu3
Version Table:
   *** 3.14.0-4ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  Finally, the solution for me is:

  sudo  /etc/logrotate.d/samba

  Replace the following line (for me, line 6)

  [ ! -x /usr/bin/smbcontrol ] || [ ! -f /run/samba/smbd.pid ] ||
  /usr/bin/smbcontrol smbd reload-config

  by

  [ ! -x /usr/bin/smbcontrol ] || [ ! -f /var/run/samba/nmbd.pid ] ||
  /usr/bin/smbcontrol nmbd reload-config

  and the following line (for me, line 18)

  [ ! -x /usr/bin/smbcontrol ] || [ ! -f /run/samba/nmbd.pid ] ||
  /usr/bin/smbcontrol nmbd reload-config

  by

  [ ! -x /usr/bin/smbcontrol ] || [ ! -f /var/run/samba/nmbd.pid ] ||
  /usr/bin/smbcontrol nmbd reload-config

  Save and reboot.

  But there are two question.
  Is it necessary to check both .pid files (both are present after boot), if 
yes, what operator should be used, || or && ?

  Is it necessary to correct line 32: "elif [ -f /run/samba/samba.pid ];
  then"? I did not correct it.

  Because of a short time after installation, it is not tested, are the
  log files rotated or not.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: logrotate 3.14.0-4ubuntu3
  Uname: Linux 5.6.0-18.1-liquorix-amd64 x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  

[Touch-packages] [Bug 1878194] Re: [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting HSP/HFP audio profile in Focal Fossa

2020-06-15 Thread Michael Heller
*** This bug is a duplicate of bug 1871794 ***
https://bugs.launchpad.net/bugs/1871794

same issue here with a freeVoice headset.
as soon as I switch to hsp/hfp mode audio stops working.
funny enough the beeps while changing sound volume are hearable

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

Title:
  [Sennheiser HD 4.50 BTNC] Bluetooth headset not working when selecting
  HSP/HFP audio profile in Focal Fossa

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  After updating the release from Ubuntu 19.10 to 20.04, the bluetooth
  headset doesn't work anymore when HSP/HFP profile is selected.

  With Ubuntu 19.10 the headset was working, there was audio and the mic
  was perfect for video conferencing.

  [Steps to reproduce]
  1. Connect headset (used blueman to setup and connect)
  1.1. When connected the system automatically selects A2DP profile
  2. Start playing audio (browser or other)
  3. Change profile to HSP/HFP with pavucontrol (or blueman)
  4. The audio disappears and microphone is not working (no input)
  5. Optionally switch back to A2DP and the audio comes back

  [Expected]
  When switching to HSP/HFP the audio should keep playing and the microphone 
should start working

  [Notes]
  I tried with pavucontrol to switch between profiles while playing audio from 
a browser.
  As side note there's a led in the headset that still blinks when switching 
profile.

  I tried deleting the pulse folder under user's profile .config without
  success, also reinstalled packages and did a `sudo alsa force-reload`
  and rebooting several times.

  Note: not sure this is a duplicate of [Bug #1576559], it looks quite
  different since the profile changes but the headset stops working.

  [System info]
  Ubuntu: 20.04 - Linux 5.4.0-29-generic x86_64
  pulseaudio: 1:13.99.1-1ubuntu3
  bluez: 5.53-0ubuntu3

  Headset: Sennheiser HD 4.50 BTNC

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1878194/+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 1768625] Re: Bluetooth headset HSP/HFP mode not working in Bionic

2020-06-15 Thread Ion Ruiz
*** This bug is a duplicate of bug 1576559 ***
https://bugs.launchpad.net/bugs/1576559

Same error with 16.04 and JBL headset, I tried 20.04 in livecd and same
problem.

Name: JBL LIVE400BT
Alias: JBL LIVE400BT
Class: 0x240404
Icon: audio-card
Paired: yes
Trusted: yes
Blocked: no
Connected: no
LegacyPairing: no
UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
UUID: Handsfree (111e--1000-8000-00805f9b34fb)
UUID: Vendor specific   (81c2e72a-0591-443e-a1ff-05f988593351)
UUID: Vendor specific   (931c7e8a-540f-4686-b798-e8df0a2ad9f7)

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

Title:
  Bluetooth headset HSP/HFP mode not working in Bionic

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  There is a previous bug with almost the same title, but for Xenial
  (https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1549163). I
  have had this issue in Artful, and when commented on the old bug, I
  was asked to raise a new one instead. I waited to see if Bionic fixed
  it for me, but it does not seem to work still. So!

  Steps to reproduce:
  1. enable bluetooth on computer and switch on the headset.
  2. pair and connect the headset
  3. go to settings to switch headset to HSP/HFP mode to enable mic
  4. save and close window.

  Expected behaviour:
  1. mic should be enabled and headset should be usable to attend calls on 
laptop.

  Behaviour in error:
  1. Headset profile switches back to A2DP and mic is not enabled.

  I am using a generic bluetooth headset on a fresh updated Kubuntu
  18.04 bionic with plasma DE.

  Software versions:
  Kernel: 4.15.0-20-generic
  Bluez version: 5.48-0ubuntu3
  pulseaudio: 1:11.1-1ubuntu7
  pulseaudio-module-bluetooth: 1:11.1-1ubuntu7

  
  Additional information:
  Running "pacmd list-cards" says that HSF/HFP is 'not available' on the 
headset:

  Output from Headset section:
  profiles:
  a2dp_sink: High Fidelity Playback (A2DP Sink) (priority 40, 
available: unknown)
  headset_head_unit: Headset Head Unit (HSP/HFP) (priority 30, 
available: no)
  off: Off (priority 0, available: yes)
  active profile: 

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1768625/+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 1883491] Re: Sound is played through wrong Output Device

2020-06-15 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1866194 ***
https://bugs.launchpad.net/bugs/1866194

Actually we should probably just assume this is bug 1866194 until proven
otherwise. To resolve that please just remove .config/pulse/ from your
home directory.

** This bug has been marked a duplicate of bug 1866194
   External audio device shows up in the sound output options but the sound 
keeps being emitted from the internal laptop speaker, or none at all.

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

Title:
  Sound is played through wrong Output Device

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Since a few days my Ubuntu 20.04 systems shows the following behavior:

  The sound settings panel in part ignores the selected output device. I
  can switch between the devices and in turn all volume controls seem to
  affect that device (including the hotkeys etc.). But the sound is only
  every played through the Speakers port.

  The only way to temporarily fix this (until reboot or even suspend) is
  to open pavucontrol and manually change the port of the built in audio
  to "headphone". After this the sound is correctly played through the
  bluetooth headphones.

  
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  pulseaudio 13.99.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1883491/+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 1883491] Re: Sound is played through wrong Output Device

2020-06-15 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1866194 ***
https://bugs.launchpad.net/bugs/1866194

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

  apport-collect 1883491

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

** Tags added: focal

** Changed in: pulseaudio (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Sound is played through wrong Output Device

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Since a few days my Ubuntu 20.04 systems shows the following behavior:

  The sound settings panel in part ignores the selected output device. I
  can switch between the devices and in turn all volume controls seem to
  affect that device (including the hotkeys etc.). But the sound is only
  every played through the Speakers port.

  The only way to temporarily fix this (until reboot or even suspend) is
  to open pavucontrol and manually change the port of the built in audio
  to "headphone". After this the sound is correctly played through the
  bluetooth headphones.

  
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  pulseaudio 13.99.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1883491/+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 1883491] Re: Sound is played through wrong Output Device

2020-06-15 Thread Balint Harmath
*** This bug is a duplicate of bug 1866194 ***
https://bugs.launchpad.net/bugs/1866194

Investigatable error. The problem is with pulseaudio.

** Package changed: ubuntu => pulseaudio (Ubuntu)

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

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

Title:
  Sound is played through wrong Output Device

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Since a few days my Ubuntu 20.04 systems shows the following behavior:

  The sound settings panel in part ignores the selected output device. I
  can switch between the devices and in turn all volume controls seem to
  affect that device (including the hotkeys etc.). But the sound is only
  every played through the Speakers port.

  The only way to temporarily fix this (until reboot or even suspend) is
  to open pavucontrol and manually change the port of the built in audio
  to "headphone". After this the sound is correctly played through the
  bluetooth headphones.

  
  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  pulseaudio 13.99.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1883491/+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 1883489] Re: Logrotate failed to start in LUbuntu 20.04

2020-06-15 Thread Balint Harmath
Nice writing down of the problem. Solution is also provided. Details are
also provided for the bug fixer.

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

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

Title:
  Logrotate failed to start in LUbuntu 20.04

Status in logrotate package in Ubuntu:
  Confirmed

Bug description:
  After fresh installation of LUbuntu 20.04, when I switched off
  Plymouth, failure of logrotate appeared on the screen during boot.

  (PIDs are replaced by ***)
  :~$ systemctl status logrotate
  ● logrotate.service - Rotate log files
   Loaded: loaded (/lib/systemd/system/logrotate.service; static; vendor 
preset: enabled)
   Active: failed (Result: exit-code) since Mon 2020-06-15 07:56:59 EEST; 
32s ago
  TriggeredBy: ● logrotate.timer
 Docs: man:logrotate(8)
   man:logrotate.conf(5)
  Process: *** ExecStart=/usr/sbin/logrotate /etc/logrotate.conf 
(code=exited, status=1/FAILURE)
 Main PID: *** (code=exited, status=1/FAILURE)

  Jun 15 07:56:55  systemd[***]: Starting Rotate log files...
  Jun 15 07:56:59  logrotate[***]: error: error running shared 
postrotate script for '/var/log/mysql.log /var/log/mysql/*log '
  Jun 15 07:56:59  systemd[***]: logrotate.service: Main process 
exited, code=exited, status=1/FAILURE
  Jun 15 07:56:59  systemd[***]: logrotate.service: Failed with result 
'exit-code'.
  Jun 15 07:56:59  systemd[***]: Failed to start Rotate log files.

  I compared /etc/logrotate.d/samba with the information at 
https://salsa.debian.org/samba-team/samba/commit/bed29aba47558252eacfe9453d23cc1ab29770aa
  Two different lines have been found:

  In /etc/logrotate.d/samba:

  line 6: [ ! -x /usr/bin/smbcontrol ] || [ ! -f /run/samba/smbd.pid ]
  || /usr/bin/smbcontrol smbd reload-config

  line 18: [ ! -x /usr/bin/smbcontrol ] || [ ! -f /run/samba/nmbd.pid ]
  || /usr/bin/smbcontrol nmbd reload-config

  at https://...

  line 6: [ ! -x /usr/bin/smbcontrol ] || [ ! -f /var/run/samba/nmbd.pid
  ] || /usr/bin/smbcontrol nmbd reload-config

  line 18: [ ! -x /usr/bin/smbcontrol ] || [ ! -f
  /var/run/samba/nmbd.pid ] || /usr/bin/smbcontrol nmbd reload-config

  There is a same difference: in LUbuntu 20.04 .pid files are searched
  in /run/samba/, but at https://... they are searched in
  /var/run/samba/. After boot, both are present and have the same PIDs.

  :~$ cat /var/run/samba/nmbd.pid
  abcd
  :~$ cat /run/samba/nmbd.pid
  abcd
  :~$ cat /var/run/samba/smbd.pid
  efgh
  :~$ cat /run/samba/smbd.pid
  efgh

  (digits are replaced by letters for security reasons)

  Changing the folders according to https://... and reboot solve the
  problem:

  :~$ systemctl status logrotate
  ● logrotate.service - Rotate log files
   Loaded: loaded (/lib/systemd/system/logrotate.service; static; vendor 
preset: enabled)
   Active: inactive (dead)
  TriggeredBy: ● logrotate.timer
 Docs: man:logrotate(8)
   man:logrotate.conf(5)

  After that, I tried to revert the changes and reboot. The bug cannot
  be reproduced anymore.

  Additional information:

  :~$ lsb_release -rd
  Description:Ubuntu 20.04 LTS
  Release:20.04
  :~$ apt-cache policy logrotate
  logrotate:
Installed: 3.14.0-4ubuntu3
Candidate: 3.14.0-4ubuntu3
Version Table:
   *** 3.14.0-4ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  Finally, the solution for me is:

  sudo  /etc/logrotate.d/samba

  Replace the following line (for me, line 6)

  [ ! -x /usr/bin/smbcontrol ] || [ ! -f /run/samba/smbd.pid ] ||
  /usr/bin/smbcontrol smbd reload-config

  by

  [ ! -x /usr/bin/smbcontrol ] || [ ! -f /var/run/samba/nmbd.pid ] ||
  /usr/bin/smbcontrol nmbd reload-config

  and the following line (for me, line 18)

  [ ! -x /usr/bin/smbcontrol ] || [ ! -f /run/samba/nmbd.pid ] ||
  /usr/bin/smbcontrol nmbd reload-config

  by

  [ ! -x /usr/bin/smbcontrol ] || [ ! -f /var/run/samba/nmbd.pid ] ||
  /usr/bin/smbcontrol nmbd reload-config

  Save and reboot.

  But there are two question.
  Is it necessary to check both .pid files (both are present after boot), if 
yes, what operator should be used, || or && ?

  Is it necessary to correct line 32: "elif [ -f /run/samba/samba.pid ];
  then"? I did not correct it.

  Because of a short time after installation, it is not tested, are the
  log files rotated or not.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: logrotate 3.14.0-4ubuntu3
  Uname: Linux 5.6.0-18.1-liquorix-amd64 x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: LXQt
  Date: Mon Jun 15 08:43:08 2020
  InstallationDate: Installed on 2020-05-30 (15 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal 

[Touch-packages] [Bug 1883491] [NEW] Sound is played through wrong Output Device

2020-06-15 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Since a few days my Ubuntu 20.04 systems shows the following behavior:

The sound settings panel in part ignores the selected output device. I
can switch between the devices and in turn all volume controls seem to
affect that device (including the hotkeys etc.). But the sound is only
every played through the Speakers port.

The only way to temporarily fix this (until reboot or even suspend) is
to open pavucontrol and manually change the port of the built in audio
to "headphone". After this the sound is correctly played through the
bluetooth headphones.


Description:Ubuntu 20.04 LTS
Release:20.04

pulseaudio 13.99.1

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

-- 
Sound is played through wrong Output Device
https://bugs.launchpad.net/bugs/1883491
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to pulseaudio 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 1879206] Re: cups hplip not install printer

2020-06-15 Thread Bjornar-si
This bug also affects me -but it might be a separate bug? 
I have a HP Color Laser Jet PRO MFP M281fdw. After upgrading from Ubuntu 18.04 
LTS to 20.04 LTS the printer is not responding, scanning cannot start. I have 
tried with HPLIP ver.3.20.5 from HP. The installation stops after this section

(...)
DEPENDENCY AND CONFLICT RESOLUTION
--
Running 'sudo apt-get install --assume-yes gtk2-engines-pixbuf'
Please wait, this may take several minutes...
Running 'sudo apt-get install --assume-yes python-pyqt5'
Please wait, this may take several minutes...
error: Command failed. Re-try #1...
Running 'sudo apt-get install --assume-yes python-pyqt5'
Please wait, this may take several minutes...
error: Command failed. Re-try #2...
Running 'sudo apt-get install --assume-yes python-pyqt5'
Please wait, this may take several minutes...
error: Command failed. Re-try #3...
Running 'sudo apt-get install --assume-yes python-pyqt5'
Please wait, this may take several minutes...
error: Package install command failed with error code 100
Would you like to retry installing the missing package(s) (y=yes*, n=no, q=quit)
(...)

I'm attaching the installation log

** Attachment added: "Installation log-file"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1879206/+attachment/5383903/+files/hplip-install_Mon-15-Jun-2020_08%3A47%3A09.log

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

Title:
  cups hplip not install printer

Status in cups package in Ubuntu:
  Incomplete
Status in hplip package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to Ubuntu 20.04 I can't print anymore.

  Description:  Ubuntu 20.04 LTS
  Release:  20.04

  cups:
Installato: 2.3.1-9ubuntu1.1
Candidato:  2.3.1-9ubuntu1.1
Tabella versione:
   *** 2.3.1-9ubuntu1.1 500
  500 http://it.archive.ubuntu.com/ubuntu focal-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu focal-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   2.3.1-9ubuntu1 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages

  hplip:
Installato: 3.20.3+dfsg0-2
Candidato:  3.20.3+dfsg0-2
Tabella versione:
   *** 3.20.3+dfsg0-2 500
  500 http://it.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  
  I tried to reinstall the printer, but it is not being re-saved by cups / hplip

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: cups 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Mon May 18 02:24:07 2020
  InstallationDate: Installed on 2020-05-17 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lpstat: device for DeskJet_3630: 
hp:/usb/DeskJet_3630_series?serial=CN8AM7H3230658
  MachineType: LENOVO 80G0
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/DeskJet_3630.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/DeskJet_3630.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic 
root=UUID=6a8469e0-ecea-4a86-8040-b0caaa938fe4 ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/18/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: A7CN40WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lancer 5A6
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0F82993WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo G50-30
  dmi.modalias: 
dmi:bvnLENOVO:bvrA7CN40WW:bd07/18/2014:svnLENOVO:pn80G0:pvrLenovoG50-30:rvnLENOVO:rnLancer5A6:rvrSDK0F82993WIN:cvnLENOVO:ct10:cvrLenovoG50-30:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80G0
  dmi.product.sku: LENOVO_MT_80G0_BU_idea_FM_Lenovo G50-30
  dmi.product.version: Lenovo G50-30
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1879206/+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 1883489] Re: Logrotate failed to start in LUbuntu 20.04

2020-06-15 Thread Viktor Mileikovskyi
** Attachment added: "Original file "samba" in /etc/logrotate.d"
   
https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1883489/+attachment/5383901/+files/samba

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

Title:
  Logrotate failed to start in LUbuntu 20.04

Status in logrotate package in Ubuntu:
  New

Bug description:
  After fresh installation of LUbuntu 20.04, when I switched off
  Plymouth, failure of logrotate appeared on the screen during boot.

  (PIDs are replaced by ***)
  :~$ systemctl status logrotate
  ● logrotate.service - Rotate log files
   Loaded: loaded (/lib/systemd/system/logrotate.service; static; vendor 
preset: enabled)
   Active: failed (Result: exit-code) since Mon 2020-06-15 07:56:59 EEST; 
32s ago
  TriggeredBy: ● logrotate.timer
 Docs: man:logrotate(8)
   man:logrotate.conf(5)
  Process: *** ExecStart=/usr/sbin/logrotate /etc/logrotate.conf 
(code=exited, status=1/FAILURE)
 Main PID: *** (code=exited, status=1/FAILURE)

  Jun 15 07:56:55  systemd[***]: Starting Rotate log files...
  Jun 15 07:56:59  logrotate[***]: error: error running shared 
postrotate script for '/var/log/mysql.log /var/log/mysql/*log '
  Jun 15 07:56:59  systemd[***]: logrotate.service: Main process 
exited, code=exited, status=1/FAILURE
  Jun 15 07:56:59  systemd[***]: logrotate.service: Failed with result 
'exit-code'.
  Jun 15 07:56:59  systemd[***]: Failed to start Rotate log files.

  I compared /etc/logrotate.d/samba with the information at 
https://salsa.debian.org/samba-team/samba/commit/bed29aba47558252eacfe9453d23cc1ab29770aa
  Two different lines have been found:

  In /etc/logrotate.d/samba:

  line 6: [ ! -x /usr/bin/smbcontrol ] || [ ! -f /run/samba/smbd.pid ]
  || /usr/bin/smbcontrol smbd reload-config

  line 18: [ ! -x /usr/bin/smbcontrol ] || [ ! -f /run/samba/nmbd.pid ]
  || /usr/bin/smbcontrol nmbd reload-config

  at https://...

  line 6: [ ! -x /usr/bin/smbcontrol ] || [ ! -f /var/run/samba/nmbd.pid
  ] || /usr/bin/smbcontrol nmbd reload-config

  line 18: [ ! -x /usr/bin/smbcontrol ] || [ ! -f
  /var/run/samba/nmbd.pid ] || /usr/bin/smbcontrol nmbd reload-config

  There is a same difference: in LUbuntu 20.04 .pid files are searched
  in /run/samba/, but at https://... they are searched in
  /var/run/samba/. After boot, both are present and have the same PIDs.

  :~$ cat /var/run/samba/nmbd.pid
  abcd
  :~$ cat /run/samba/nmbd.pid
  abcd
  :~$ cat /var/run/samba/smbd.pid
  efgh
  :~$ cat /run/samba/smbd.pid
  efgh

  (digits are replaced by letters for security reasons)

  Changing the folders according to https://... and reboot solve the
  problem:

  :~$ systemctl status logrotate
  ● logrotate.service - Rotate log files
   Loaded: loaded (/lib/systemd/system/logrotate.service; static; vendor 
preset: enabled)
   Active: inactive (dead)
  TriggeredBy: ● logrotate.timer
 Docs: man:logrotate(8)
   man:logrotate.conf(5)

  After that, I tried to revert the changes and reboot. The bug cannot
  be reproduced anymore.

  Additional information:

  :~$ lsb_release -rd
  Description:Ubuntu 20.04 LTS
  Release:20.04
  :~$ apt-cache policy logrotate
  logrotate:
Installed: 3.14.0-4ubuntu3
Candidate: 3.14.0-4ubuntu3
Version Table:
   *** 3.14.0-4ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  Finally, the solution for me is:

  sudo  /etc/logrotate.d/samba

  Replace the following line (for me, line 6)

  [ ! -x /usr/bin/smbcontrol ] || [ ! -f /run/samba/smbd.pid ] ||
  /usr/bin/smbcontrol smbd reload-config

  by

  [ ! -x /usr/bin/smbcontrol ] || [ ! -f /var/run/samba/nmbd.pid ] ||
  /usr/bin/smbcontrol nmbd reload-config

  and the following line (for me, line 18)

  [ ! -x /usr/bin/smbcontrol ] || [ ! -f /run/samba/nmbd.pid ] ||
  /usr/bin/smbcontrol nmbd reload-config

  by

  [ ! -x /usr/bin/smbcontrol ] || [ ! -f /var/run/samba/nmbd.pid ] ||
  /usr/bin/smbcontrol nmbd reload-config

  Save and reboot.

  But there are two question.
  Is it necessary to check both .pid files (both are present after boot), if 
yes, what operator should be used, || or && ?

  Is it necessary to correct line 32: "elif [ -f /run/samba/samba.pid ];
  then"? I did not correct it.

  Because of a short time after installation, it is not tested, are the
  log files rotated or not.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: logrotate 3.14.0-4ubuntu3
  Uname: Linux 5.6.0-18.1-liquorix-amd64 x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: LXQt
  Date: Mon Jun 15 08:43:08 2020
  InstallationDate: Installed on 2020-05-30 (15 days ago)
  InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - 

[Touch-packages] [Bug 1883489] [NEW] Logrotate failed to start in LUbuntu 20.04

2020-06-15 Thread Viktor Mileikovskyi
Public bug reported:

After fresh installation of LUbuntu 20.04, when I switched off Plymouth,
failure of logrotate appeared on the screen during boot.

(PIDs are replaced by ***)
:~$ systemctl status logrotate
● logrotate.service - Rotate log files
 Loaded: loaded (/lib/systemd/system/logrotate.service; static; vendor 
preset: enabled)
 Active: failed (Result: exit-code) since Mon 2020-06-15 07:56:59 EEST; 32s 
ago
TriggeredBy: ● logrotate.timer
   Docs: man:logrotate(8)
 man:logrotate.conf(5)
Process: *** ExecStart=/usr/sbin/logrotate /etc/logrotate.conf 
(code=exited, status=1/FAILURE)
   Main PID: *** (code=exited, status=1/FAILURE)

Jun 15 07:56:55  systemd[***]: Starting Rotate log files...
Jun 15 07:56:59  logrotate[***]: error: error running shared postrotate 
script for '/var/log/mysql.log /var/log/mysql/*log '
Jun 15 07:56:59  systemd[***]: logrotate.service: Main process exited, 
code=exited, status=1/FAILURE
Jun 15 07:56:59  systemd[***]: logrotate.service: Failed with result 
'exit-code'.
Jun 15 07:56:59  systemd[***]: Failed to start Rotate log files.

I compared /etc/logrotate.d/samba with the information at 
https://salsa.debian.org/samba-team/samba/commit/bed29aba47558252eacfe9453d23cc1ab29770aa
Two different lines have been found:

In /etc/logrotate.d/samba:

line 6: [ ! -x /usr/bin/smbcontrol ] || [ ! -f /run/samba/smbd.pid ] ||
/usr/bin/smbcontrol smbd reload-config

line 18: [ ! -x /usr/bin/smbcontrol ] || [ ! -f /run/samba/nmbd.pid ] ||
/usr/bin/smbcontrol nmbd reload-config

at https://...

line 6: [ ! -x /usr/bin/smbcontrol ] || [ ! -f /var/run/samba/nmbd.pid ]
|| /usr/bin/smbcontrol nmbd reload-config

line 18: [ ! -x /usr/bin/smbcontrol ] || [ ! -f /var/run/samba/nmbd.pid
] || /usr/bin/smbcontrol nmbd reload-config

There is a same difference: in LUbuntu 20.04 .pid files are searched in
/run/samba/, but at https://... they are searched in /var/run/samba/.
After boot, both are present and have the same PIDs.

:~$ cat /var/run/samba/nmbd.pid
abcd
:~$ cat /run/samba/nmbd.pid
abcd
:~$ cat /var/run/samba/smbd.pid
efgh
:~$ cat /run/samba/smbd.pid
efgh

(digits are replaced by letters for security reasons)

Changing the folders according to https://... and reboot solve the
problem:

:~$ systemctl status logrotate
● logrotate.service - Rotate log files
 Loaded: loaded (/lib/systemd/system/logrotate.service; static; vendor 
preset: enabled)
 Active: inactive (dead)
TriggeredBy: ● logrotate.timer
   Docs: man:logrotate(8)
 man:logrotate.conf(5)

After that, I tried to revert the changes and reboot. The bug cannot be
reproduced anymore.

Additional information:

:~$ lsb_release -rd
Description:Ubuntu 20.04 LTS
Release:20.04
:~$ apt-cache policy logrotate
logrotate:
  Installed: 3.14.0-4ubuntu3
  Candidate: 3.14.0-4ubuntu3
  Version Table:
 *** 3.14.0-4ubuntu3 500
500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status

Finally, the solution for me is:

sudo  /etc/logrotate.d/samba

Replace the following line (for me, line 6)

[ ! -x /usr/bin/smbcontrol ] || [ ! -f /run/samba/smbd.pid ] ||
/usr/bin/smbcontrol smbd reload-config

by

[ ! -x /usr/bin/smbcontrol ] || [ ! -f /var/run/samba/nmbd.pid ] ||
/usr/bin/smbcontrol nmbd reload-config

and the following line (for me, line 18)

[ ! -x /usr/bin/smbcontrol ] || [ ! -f /run/samba/nmbd.pid ] ||
/usr/bin/smbcontrol nmbd reload-config

by

[ ! -x /usr/bin/smbcontrol ] || [ ! -f /var/run/samba/nmbd.pid ] ||
/usr/bin/smbcontrol nmbd reload-config

Save and reboot.

But there are two question.
Is it necessary to check both .pid files (both are present after boot), if yes, 
what operator should be used, || or && ?

Is it necessary to correct line 32: "elif [ -f /run/samba/samba.pid ];
then"? I did not correct it.

Because of a short time after installation, it is not tested, are the
log files rotated or not.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: logrotate 3.14.0-4ubuntu3
Uname: Linux 5.6.0-18.1-liquorix-amd64 x86_64
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: LXQt
Date: Mon Jun 15 08:43:08 2020
InstallationDate: Installed on 2020-05-30 (15 days ago)
InstallationMedia: Lubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
SourcePackage: logrotate
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug focal logrotate

** Patch added: "The corrected file in /etc/logrotate.d"
   https://bugs.launchpad.net/bugs/1883489/+attachment/5383897/+files/samba

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

Title:
  Logrotate failed to start in LUbuntu 20.04

Status in logrotate package in 

[Touch-packages] [Bug 1817955] Re: Getting new "DN is out of the realm subtree" error on adding principal

2020-06-15 Thread Rafael David Tinoco
** Also affects: krb5 (Ubuntu Trusty)
   Importance: Undecided
   Status: New

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

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

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

Title:
  Getting new "DN is out of the realm subtree" error on adding principal

Status in krb5 package in Ubuntu:
  Fix Released
Status in krb5 source package in Trusty:
  Triaged

Bug description:
  Recently applied security update to 14.04.5 LTS kerberos (1.12+dfsg-
  2ubuntu5.4), and started getting errors when adding new principals to
  LDAP.

  Obfuscated example:

  kadmin.local -q "ank -x
  dn=\"uid=testuser,ou=People,dc=example,dc=com\" -pw \"dummypass\"
  testuser"

  now gives:
  Authenticating as principal root/ad...@test.example.com with password.
  NOTICE: no policy specified for testu...@test.example.com; assigning "default"
  add_principal: DN is out of the realm subtree while creating 
"testu...@test.example.com".

  
  This worked up through 1.12+dfsg-2ubuntu5.3, and I think it now fails due to 
changes in src/plugins/kdb/ldap/libkdb_ldap/ldap_principal2.c in response to 
CVE-2018-5729 or CVE-2018-5730.

  I'm going to attempt a downgrade to 1.12+dfsg-2ubuntu5.3 to check.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/krb5/+bug/1817955/+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 1744155] Re: found while checking

2020-06-15 Thread Daniel van Vugt
Please explain in more detail what kind of problem you are encountering.

** Package changed: xorg (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  found while checking

Status in Ubuntu:
  Incomplete

Bug description:
  i can't give details

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  Uname: Linux 4.4.0-109-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Jan 18 23:15:30 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GT216GLM [Quadro FX 880M] [10de:0a3c] (rev a2) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company GT216GLM [Quadro FX 880M] [103c:1521]
  InstallationDate: Installed on 2016-10-01 (473 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Hewlett-Packard HP EliteBook 8540w
  PccardctlStatus:
   Socket 0:
 3.3V
16-bit
PC Card
 Subdevice 0 (function 0) bound to driver "pata_pcmcia"
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-109-generic 
root=UUID=825aca86-4595-48d6-84b4-ed29a6020695 ro splash quiet plymouth:debug=1 
vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/13/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68CVD Ver. F.24
  dmi.board.name: 1521
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 32.35
  dmi.chassis.asset.tag: CND1164H6Z
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68CVDVer.F.24:bd09/13/2013:svnHewlett-Packard:pnHPEliteBook8540w:pvr:rvnHewlett-Packard:rn1521:rvrKBCVersion32.35:cvnHewlett-Packard:ct10:cvr:
  dmi.product.name: HP EliteBook 8540w
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.4-0ubuntu1~16.04.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Jan 18 09:27:10 2018
  xserver.configfile: default
  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.18.4-0ubuntu0.7
  xserver.video_driver: nouveau

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